diff --git a/zh_TW.Big5/books/Makefile b/zh_TW.Big5/books/Makefile
index a86cac71e9..3918e85f5f 100644
--- a/zh_TW.Big5/books/Makefile
+++ b/zh_TW.Big5/books/Makefile
@@ -1,11 +1,12 @@
 # $FreeBSD$
 
 SUBDIR = faq
-#SUBDIR+= handbook
-#SUBDIR+= porters-handbook
+SUBDIR+= fdp-primer
+SUBDIR+= handbook
+SUBDIR+= porters-handbook
 #SUBDIR+= zh-tut
 
 ROOT_SYMLINKS = faq
 
 DOC_PREFIX?= ${.CURDIR}/../..
 .include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/zh_TW.Big5/books/faq/book.sgml b/zh_TW.Big5/books/faq/book.sgml
index 06dfa40db3..129e7f6153 100644
--- a/zh_TW.Big5/books/faq/book.sgml
+++ b/zh_TW.Big5/books/faq/book.sgml
@@ -1,11285 +1,11157 @@
 <!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
 <!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
 %man;
 <!ENTITY % freebsd PUBLIC "-//FreeBSD//ENTITIES DocBook Miscellaneous FreeBSD Entities//EN">
 %freebsd;
 <!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
 %authors;
 <!ENTITY % teams PUBLIC "-//FreeBSD//ENTITIES DocBook Team Entities//EN">
 %teams;
 
 <!ENTITY % bookinfo PUBLIC "-//FreeBSD//ENTITIES DocBook BookInfo Entities//EN">
 %bookinfo;
 
 <!ENTITY % mailing-lists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
 %mailing-lists;
 
 <!ENTITY % books.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Books Entity Set//EN">
 %books.ent;
 
 <!ENTITY bibliography SYSTEM "../../../share/sgml/bibliography.sgml">
 ]>
 
 <book>
   <bookinfo>
     <title>FreeBSD 4.X¡A5.X ¤Î 6.X ±`¨£°Ýµª¶°</title>
 
     <corpauthor>FreeBSD ¤å¥ó­pµe</corpauthor>
 
     <pubdate>$FreeBSD$</pubdate>
 
     <copyright>
       <year>1995</year>
       <year>1996</year>
       <year>1997</year>
       <year>1998</year>
       <year>1999</year>
       <year>2000</year>
       <year>2001</year>
       <year>2002</year>
       <year>2003</year>
       <year>2004</year>
       <year>2005</year>
+      <year>2006</year>
       <holder>FreeBSD ¤å¥ó­pµe</holder>
     </copyright>
 
     &bookinfo.legalnotice;
 
     <legalnotice id="trademarks" role="trademarks">
       &tm-attrib.freebsd;
       &tm-attrib.3com;
       &tm-attrib.adobe;
       &tm-attrib.creative;
       &tm-attrib.cvsup;
       &tm-attrib.ibm;
       &tm-attrib.ieee;
       &tm-attrib.intel;
       &tm-attrib.iomega;
       &tm-attrib.linux;
       &tm-attrib.microsoft;
       &tm-attrib.mips;
       &tm-attrib.netscape;
       &tm-attrib.opengroup;
       &tm-attrib.oracle;
       &tm-attrib.sgi;
       &tm-attrib.sparc;
       &tm-attrib.sun;
       &tm-attrib.usrobotics;
       &tm-attrib.xfree86;
       &tm-attrib.general;
     </legalnotice>
 
     <abstract>
       <para>³o¥÷¤å¥ó¬O FreeBSD 4.X¡A5.X ¤Î 6.X ªº±`¨£°Ýµª¶°¡C
         °£«D¦³¯S§O¥[µù¡A§_«h³o¨Ç¶µ¥Ø³£¾A¥Î©ó FreeBSD 4.0 ¤Î¥H«áªºª©¥»¡C
 	(¦pªG±ø¥Ø¤º®e¤¤¦³ &lt;XXX&gt; «h¬O©|¥¼§¹¦¨¤¤Ä¶ªº³¡¥÷¡C) ¦pªG±z¹ï¨ó§U¥»­pµe
 	ªº¶i¦æ¦³¿³½ìªº¸Ü¡A½Ð±H e-mail ¨ì
 	&a.doc;¡C¦¹¥~¡AÀH®É¥i±q <ulink URL="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/index.html">
 	FreeBSD ºô¯¸</ulink> ®³¨ì³o¥÷¤å¥óªº³Ì·sª©¥»¡C
 	¤]¥i¥H§Q¥Î HTTP ¨Ó¤U¸ü¤@¥÷Ãe¤jªº <ulink URL="book.html">HTML</ulink>
 	¤å¥ó¡A©Î¬O¸g¥Ñ <ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">
 	FreeBSD FTP ¯¸</ulink> ¤U¸ü¯Â¤å¦r¡B&postscript;¡B©Î PDF ª©¥»ªºÀɮסC
 	±z¤]¥i¥H¦b³o¸Ì¨Ï¥Î
 	<ulink URL="&url.base;/search/search.html">·j´M¸ê®Æ</ulink>
 	ªº¥\¯à¡C</para>
     </abstract>
   </bookinfo>
 
   <chapter id="introduction">
     <chapterinfo>
       <author>
 	<firstname>Ying-Chieh</firstname>
 	<surname>Liao</surname>
 	<affiliation>
 	  <address><email>ijliao@FreeBSD.org</email></address>
 	</affiliation>
       </author>
     </chapterinfo>
 
     <title>«e¨¥</title>
 
     <para>Åwªï¨Ï¥Î FreeBSD 4.X-6.X FAQ!</para>
 
     <para>¸ò¨ä¥L Usenet ¤Wªº FAQ ¤@¼Ë¡A³o¥÷¤å¥ó²[»\¤F¦³Ãö FreeBSD ³o®M§@·~
       ¨t²Î³Ì±`³Q°Ý¨ìªº°ÝÃD (·íµM¥]¬A¤F¦^µª¡I)¡CÁöµM»¡§Ú­Ì¥»¨Óªº¥Øªº¬O¬°¤F
       ´î¤Öºô¸ôÀW¼eªº®ö¶O¥H¤ÎÁקK¦P¼Ëªº°ÝÃD¤@¦A¥X²{¡A¦ý¨Æ¹ê¤W FAQ ¤w¸g³Qµø
       ¬°¬O¤@ºØ­È±o¾\Ūªº¤å¥ó¸ê·½¡C</para>
 
-    <para>§Ú­Ì¤w¸g¾¨¥i¯à¦a¨Ï³o¥÷ FAQ §óÂ×´I¤F¡C¦pªG±z¹ï¦p¦ó¨Ï¨ä§ó¶i¨B¦³¥ô
+    <para>§Ú­Ì¤w¸g¾¨¥i¯à¦a¨Ï³o¥÷ FAQ §óÂ×´I¤F¡C¦pªG±z¹ï¦p¦ó§ïµ½¡B¶i¨B¤è­±¦³¥ô
       ¦ó«Øij¡A½ÐÀH®É±H¹q¤l¶l¥óµ¹ &a.doc;¡C</para>
 
     <qandaset>
       <qandaentry>
         <question id="what-is-FreeBSD">
           <para>¤°»ò¬O FreeBSD¡H</para>
         </question>
 
         <answer>
          <para>²³æ¦a¨Ó»¡¡AFreeBSD ¬O¤@®M¥i¥H¦b Alpha/AXP, AMD64 ¤Î 
 	   &intel; EM64T, &i386; IA-64, PC-98, &ultrasparc; ¤W°õ¦æªº
            UN*X-like §@·~¨t²Î¡A¥¦¬O®Ú¾Ú U.C. Berkeley ©Ò¶}µo¥X¨Óªº
            <quote>4.4BSD-Lite</quote>¡A¨Ã¥[¤W¤F³\¦h <quote>4.4BSD-Lite2</quote>
 	   ªº¼W±j¥\¯à¡C¥¦¦P®É¤]¶¡±µ¨Ï¥Î¤F U.C. Berkeley ©Ò¶}µo¥X¨Ó¨Ã¥Ñ
 	   William Jolitz ²¾´Ó¨ì i386 ªº <quote>Net/2</quote>¡A¤]´N¬O
 	   <quote>386BSD</quote>¡A¤£¹L²{¦b 386BSD ªºµ{¦¡½X¥u³Ñ¤U·¥¤Ö¼ÆÁÙ¯d
 	   ¦s¦b FreeBSD ¤¤¡C±z¥i¥H¦b
 	   <ulink URL="&url.base;/index.html">FreeBSD ­º­¶</ulink>§ä¨ì¦³Ãö
            ¤°»ò¬O FreeBSD ¥H¤Î¥¦¥i¥HÀ°±z°µ¨Ç¤°»òªº¬ÛÃö¸ê°T¡C</para>
 
          <para>FreeBSD ¤w³Q¼sªx¦a³Q¥@¬É¦U¦aªº¤½¥q¦æ¸¹¡BISP¡B¬ã¨s¤H­û¡B¹q¸£
 	  ±M®a¡B¾Ç¥Í¡A¥H¤Î®a®x¥Î¤á©Ò¨Ï¥Î¡A¥Î¦b¤u§@¡B±Ð¨|¥H¤Î®T¼Ö¤W¡C</para>
 
          <para>¦pªG·Q¬ÝÃö©ó FreeBSD §ó²`¤Jªº¸ê®Æ¡A½Ð¬Ý
            <ulink URL="&url.books.handbook;/index.html">FreeBSD ¨Ï¥Î¤â¥U</ulink>¡C</para>
        </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="FreeBSD-goals">
           <para>µo®i FreeBSD ªº¥Øªº¬O¤°»ò¡H</para>
         </question>
 
         <answer>
           <para>FreeBSD ­pµeªº¥Øªº¬O´£¨Ñ¥i¥H¥ô·N¨Ï¥Î¥B¨S¦³­­¨îªº³nÅé¡C§Ú­Ì¦b
             µ{¦¡½X (¥H¤Î­p±Þ¥»¨­) ¤W¥I¥X¤F¤j¶q¤ß¦å¡A·íµM¤£·|¤¶·N¨ÓÂIª÷¿ú¤Wªº
             ¦^õX¡A¤£¹L§Ú­Ìµ´¹ï¤£·|¦p¦¹°í«ù¡C§Ú­Ì¬Û«H§Ú­Ì­º­nªº
 	    <quote>¥ô°È</quote> ´N¬O´£¨Ñµ{¦¡½Xµ¹¨C¤@­Ó¨Ï¥ÎªÌ¡A¤£ºÞ¥L­Ì¥´ºâ¥Î
             ¨Ó·F¹À¡F³o»ò¤@¨Ó¡A³o¨Çµ{¦¡½X¤~¯à³Q¥Î¦b³Ì¦h¦a¤è¡A¤]¤~¯àµo´§¥¦­Ì³Ì
             ¤jªº§Q¯q¡C§Ú­Ì¬Û«H³o´N¬O¦Û¥Ñ³nÅé³Ì°ò¥»ªº¥Ø¼Ð¤§¤@¡A¦Ó¥B§Ú­Ì·|ºÉ¥þ
             ¤O¥h¤ä«ù¥¦¡C</para>
 
           <para>¦b§Ú­Ì source tree ¤¤¦³³¡¥÷ªºµ{¦¡½X¬O±Ä¥Î©Ò¿×ªº<ulink
             url="http://www.FreeBSD.org/copyright/COPYING">GPL</ulink>©Î¬O
             <ulink url="http://www.FreeBSD.org/copyright/COPYING.LIB">LGPL
             </ulink>ª©Åv«Å§i¡AÁöµM³o¨Çª©Åv«Å§i¬O¥Î¨Ó«O»Ù¦Ó«D­­¨î¨Ï¥ÎªÌªºÅv
             §Q¡A²¦³º¬O¤£¨º»ò¦Û¥Ñ¤F¨Ç¡C¥Ñ©ó³o¨Ç GPL ªº³nÅé¦b°Ó·~¨Ï¥Î¤W·|¤Þ°_
             «D±`½ÆÂøªºª©Åv°ÝÃD¡A¦]¦¹¥u­n¦³¾÷·|¡A§Ú­Ì·|ºÉ¶q¥H±Ä¥Î¤ñ¸ûÃPªº
             <ulink url="http://www.FreeBSD.org/copyright/freebsd-license.html">
             FreeBSD ª©Åv</ulink>ªº³nÅé¨Ó¨ú¥N³o¨Ç GPL ª©Åv«Å§iªº³nÅé¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="bsd-license-restrictions">
           <para>FreeBSD ª©Åv¦³¥ô¦ó­­¨î¶Ü¡H</para>
         </question>
 
         <answer>
           <para>¦³ªº¡C¦ý¬O³o¨Ã¤£¬O­­¨î§A«ç»ò¥h¨Ï¥Î³o¨Çµ{¦¡½X¡A¦Ó¬O§A«ç»ò¬Ý«Ý
             FreeBSD ³o­Ó­pµe¡C¦pªG§A¦³ª©ÅvµJ¼{¯gªº¸Ü¡A½Ð¾\Ū<ulink
             url="http://www.FreeBSD.org/copyright/freebsd-license.html">
             ª©Åv¥»¤å</ulink>¡C²³æ¦a¨Ó»¡¡A³o¥÷ª©Åvªº­«ÂI¥i¥H±ø¦C¦p¤U¡C</para>
 
           <itemizedlist>
             <listitem>
               <para>½Ð¤Å«ÅºÙ¬O±z¼g¤F³o­Óµ{¦¡¡C</para>
             </listitem>
 
             <listitem>
               <para>¦pªG¥¦¥X°ÝÃD¤F¡A¤£­n±±§i§Ú­Ì¡C</para>
             </listitem>
           </itemizedlist>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="replace-current-OS">
           <para>FreeBSD ¥i¥H¨ú¥N§Ú²{¦b¦b¥Îªº§@·~¨t²Î¶Ü¡H</para>
         </question>
 
         <answer>
           <para>¹ï¤j³¡¥÷ªº¤H¨Ó»¡¬O³o¼Ë¨S¿ù¡A¦ý¨Æ¹ê¤W³o°ÝÃD¨Ã¨S¦³³o»ò¦n¦^
             榭C</para>
 
           <para>¤j³¡¥÷ªº¤H¨Ã¤£¬O¯u¥¿¦b¨Ï¥Î¤@­Ó§@·~¨t²Î¡C¥L­Ì¨Ï¥Îªº¬OÀ³¥Îµ{¦¡
             ¡F¦Ó¨º¨ÇÀ³¥Îµ{¦¡¤~¬O¯u¥¿¥Î¨ì§@·~¨t²ÎªºªF¦è¡CFreeBSD ¬O³]­p¥Î¨Ó´£
 	    ¨Ñ¤@­Ó±j¶´¥B¥\¯à§¹¾ãªº§@·~Àô¹Òµ¹À³¥Îµ{¦¡¨Ó°õ¦æ¡C¥¦¤ä´©¤F¦hºØÂsÄý
             ¾¹¡A¿ì¤½«Ç®M¥ó³nÅé¡A¹q¤l¶l¥ó¾\Ū³nÅé¡Aø¹Ïµ{¦¡¡Aµ{¦¡³]­pÀô¹Ò¡Aºô
             ¸ô¦øªA¾¹³nÅé¡A¥H¤Î´X¥G©Ò¦³§A·Q­nªºªF¦è¡C¤j³¡¥÷ªºµ{¦¡³£¥i¥H¾a<ulink
             url="http://www.freebsd.org/ports/">Ports Collection</ulink>¨ÓºÞ
             ²z¡C</para>
 
           <para>¦ý¬O¦pªG§A·Q­n¨Ï¥ÎªºÀ³¥Îµ{¦¡¥u¯à¦b¬Y­Ó¯S©wªº§@·~¨t²Î¤W­±°õ¦æ
             ªº¸Ü¡A§A´N¤£¯à»´©ö¦a§â¥¦´«±¼¡A©ÎªÌ«ü±æ¦b FreeBSD ¤W¦³«Ü¬Û¦üªºÀ³¥Î
 	    µ{¦¡¤~¦³¾÷·|¡C¦pªG§A·Q­nªº¬O¤@­Ó±j°·ªº¿ì¤½«Ç©Î¬Oºô¸ô¦øªA¾¹¡A©Î¬O
 	    ¤@³¡Ã­©wªº¤u§@¯¸¡A©Î¬O·Q¦b¤£³Q¤¤Â_ªºÀô¹Ò¤U¤u§@ªº¸Ü¡AFreeBSD µLºÃ
 	    ¬O±zªº³Ì¨Î¿ï¾Ü¡C¥@¬É¦U¦a¦³«Ü¦h¨Ï¥ÎªÌ¡A¥]¬Aªì¾Ç©Î¸ê²`ªº &unix; ºÞ²z
 	    ¤H­û³£¿ï¥Î FreeBSD ·í¥L­Ì°ß¤@ªº®à¤W§@·~¨t²Î¡C</para>
 
           <para>¦pªG§A¬O±q¨ä¥Lªº &unix; Àô¹ÒÂà´«¨ì FreeBSD ªº¸Ü¡A°ò¥»¤W¬O¤j¦P¤p
             ²§ªº¡C¦ý¬O¦pªG§A¤§«e¥Îªº¬O¹Ï§Î¬É­±ªº§@·~¨t²Î¡A¨Ò¦p»¡¬O &windows; ©Î¬O
             ¤ñ¸û¥j¦Ñªº &macos; ªº¸Ü¡A¥i¯à´N­n¦hªá¤@ÂI®É¶¡¨Ó¾Ç²ß«ç»ò¥Î &unix; ªº
             ¤èªk¨Ó°µ¨Æ¡C§A¥i¥H±q³o¥÷ FAQ ©M <ulink
             url="&url.books.handbook;/index.html">FreeBSD ¨Ï¥Î¤â¥U</ulink> ¨Ó¤Jªù¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="why-called-FreeBSD">
           <para>¬°¤°»ò­n¥s°µ FreeBSD¡H</para>
         </question>
 
         <answer>
           <itemizedlist>
             <listitem>
               <para>±z¥i¥H§K¶O¨Ï¥Î¥¦¡A§Y¨Ï¬O¥Î©ó°Ó·~¥Î³~¡C</para>
             </listitem>
 
             <listitem>
               <para>¾ã­Ó FreeBSD §@·~¨t²Î§¹¾ãªº­ì©lµ{¦¡³£¥i¥H§K¶O¨ú±o¡A¦Ó¥B¤£
                 ºÞ¬O¦b¨Ï¥Î¡A´²§G©Î¬O¾ã¦X¶i¨ä¥Lµ{¦¡µ¥¦U¤è­±¤]¥u¨ü¨ì³Ì¤pªº­­
                 ¨î (¤£½×¬O§_¥Î©ó°Ó·~¥Î³~)¡C</para>
             </listitem>
 
             <listitem>
               <para>¥ô¦ó¤H³£¥i¥H¦Û¥Ñ¦a§â¥L¹ï¨t²Îªº§ï¨}©Î¿ù»~­×¥¿ªºµ{¦¡½X¥[¤J
                 source tree ¤§¤¤ (·íµM­n²Å¦X´X­Ó¥ý¨M±ø¥ó)¡C</para>
             </listitem>
           </itemizedlist>
 
           <para>¯S§O­È±oª`·Nªº¬O³o¸Ìªº <quote>free</quote> ¥X²{¤F¨â¦¸¡A¦Ó¥B¥¦­Ì
             ªº·N«ä¬O¤£¤@¼Ëªº¡G¤@ºØ¥Nªí <quote>§K¶O</quote>¡A¥t¤@ºØ¥Nªí
 	    <quote>¦Û¥Ñ</quote>¡C±z¥i¥H®³ FreeBSD ¥h°µ¥ô¦ó±z·Q­n°µªº¨Æ¡A°£¤F¤@¨Ç
             <emphasis>¨Ò¥~</emphasis>¡A¨Ò¦p±z«ÅºÙ FreeBSD ¬O±z¼gªº¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
 	<question id="differences-to-other-bsds">
 	  <para>FreeBSD ¤Î NetBSD, OpenBSD ¥H¤Î¨ä¥L
 	    open source BSD §@·~¨t²Î¤§¶¡¦³¦ó¤£¦P¤§³B©O¡H</para>
 	</question>
 
 	<answer>
 	  <para>James Howard ¦b <ulink url="http://www.daemonnews.org/">DaemonNews</ulink>
 	    ¤W¼g¤F <ulink url="http://ezine.daemonnews.org/200104/bsd_family.html">
 	    The BSD Family Tree</ulink> ªº¤å¥ó¡A¸Ì­±»¡©ú¤F³o¨Ç¾ú¥v²W·½¤Î³o¨Ç *BSD 
 	    ®a±Ú­pµe¤§¶¡ªº®t²§¡C</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
         <question id="latest-version">
           <para>³Ì·sª©ªº FreeBSD ¬O¨º¤@ª©¡H</para>
         </question>
 
 <!--
   This answer is a hack to deal with the fact that for now there are
   multiple "latest" versions of FreeBSD.
   ³o­Ó¦³ÂIÃø¥H¦^µª¡A¨Æ¹ê¤W FreeBSD ¦³³\¦hºØÃþªº¡y³Ì·sª©¡z¡C
 -->
 
 	<answer>
 	  <para>´N FreeBSD ¥Ø«eªºµo®i¦Ó¨¥¡A¦³¥|­Ó¥D­nµo®i¤À¤ä(¨ä¤¤¤T­Ó¤w¦³ RELEASE)¡G
 	    ¥Ñ <emphasis>4-STABLE</emphasis> ©Òµo¦æ(release)ªº 4.X ¨t¦C¡B
 	    ¥Ñ <emphasis>5-STABLE</emphasis> ©Òµo¦æ(release)ªº 5.X ¨t¦C¡B
 	    ¥Ñ <emphasis>6-STABLE</emphasis> ©Òµo¦æ(release)ªº 6.X ¨t¦C¡A
 	    ¥H¤Î <emphasis>7-CURRENT</emphasis> ¤À¤ä¡C</para>
 
-	  <para>¦b 5.3 release ¤§«e¡A4.X ¨t¦C¤´³Qµø¬°¬O <emphasis>-STABLE</emphasis> ¤§¤@¡C
-	    ¦Û±q 5.3 ¶}©l¡A5.X ¶}©l³W¹º·sªº <emphasis>-STABLE</emphasis> µo®i­«ÂI¡A
+	  <para>¦b 5.3 release ¤§«e¡A4.X ¨t¦C¤´ÄÝ <emphasis>-STABLE</emphasis> ¤À¤ä¡C
+	    ¦Û±q 5.3 ¶}©l¡A5.X ¨t¦C¶}©l³W¹º·sªº <emphasis>-STABLE</emphasis> ¤À¤äµo®i­«ÂI¡A
 	    ¦Ó 4.X ±N¥uµÛ­«¦b­«¤j°ÝÃD¤W(¤ñ¦p¡Gº|¬}­×¸É¡B¦w¥þºûÅ@)¥H¤Î &quot;extended support&quot;
 	    ¡A¤£¦A·|¦³·sªº¬ð¯}©Êµo®i¡C</para>
 
 <!-- note: the entity definitions are out of date -->
-	  <para>©ó &rel.current.date; ©Òµo¦æªº<ulink
+	  <para>©ó &rel.current.date; ©Òµo¦æªº <ulink
 	    url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE">&rel.current;</ulink>
-	    ª©¬O¥Ø«e³Ì·sªº <emphasis>6-STABLE</emphasis> ª©¡F
-	    ¦Ó©ó &rel2.current.date; ©Òµo¦æªº<ulink
+	    ª©¬O¥Ø«e³Ì·sªº <emphasis>6-STABLE</emphasis> ¤À¤ä¡F
+	    ¦Ó©ó &rel2.current.date; ©Òµo¦æªº <ulink
 	    url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel2.current;-RELEASE/">&rel2.current;</ulink>
-	    ª©«h¬O¥Ø«e³Ì·sªº <emphasis>5-STABLE</emphasis> ª©¡C</para>
+	    ª©«h¬O¥Ø«e³Ì·sªº <emphasis>5-STABLE</emphasis> ¤À¤ä¡C</para>
 
           <para>²³æªº»¡¡A<emphasis>-STABLE</emphasis> ªº¥D­n¶D¨D¹ï¶H¬O¹ï©ó
             í©w©Ê¤Î§CÅܲ§©Êªº»Ý¨D»·³Ó¹L¹ï³Ì·s <emphasis>-CURRENT</emphasis>
             snapshot ¤¤¯S§O·s¥\¯àªº»Ý¨D¡A¨Ò¦p ISP ©Î¤½¥q¦æ¸¹ªº¨Ï¥ÎªÌ¡C³o¨â­Ó
             branch ³£¦³¥i¯à·|²£¥Í release ª©¡A¦ý¥u¦³·í§A¯à±µ¨ü
             <emphasis>-CURRENT</emphasis> »·¤ñ <emphasis>-STABLE</emphasis>
             ®e©ö§ó°Ê³o¤@ÂI¡A¤~À³¸Ó¥Î <emphasis>-CURRENT</emphasis>¡C</para>
 
           <para>Release ª©<link linkend="release-freq">¨C´X­Ó¤ë</link>¤~·|µo
             ¦æ¤@¦¸¡CÁöµM¦p¦¹¡A¦³«Ü¦h¤H©M FreeBSD ­ì©l½X¦P¨B§ó·s¡]¸Ô¨£
             <link linkend="current">FreeBSD-CURRENT</link> ©M <link
             linkend="stable">FreeBSD-STABLE</link> ªº¬ÛÃö°ÝÃD)¡A¦ý¦]¬°­ì©l½X
             ¬O¤@ª½¤£Â_¦a¦bÅܰʪº¡A©Ò¥H¦pªG­n³o»ò°µªº¸Ü±o­nªá¤W§ó¦hªººë
             ¤O¡C</para>
 
 	  <para>¨ä¥L§ó¦h¬ÛÃö FreeBSD µo¦æ±¡³ø¡A¥i¥Ñ FreeBSD ºô¯¸¤Wªº <ulink
 	    url="http://www.FreeBSD.org/releng/index.html"> Release Engineering</ulink> ±oª¾</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="current">
           <para>¤°»ò¬O FreeBSD-CURRENT¡H</para>
         </question>
 
         <answer>
           <para><ulink
             url="&url.books.handbook;/cutting-edge.html#CURRENT">FreeBSD-CURRENT</ulink>
             «üªº¬O¥¿¦bµo®i¤¤ªº§@·~¨t²Îª©¥»¡A¥¦²×±N¦b¾A·íªº®É¾÷¦¨¬°
 	    &os.stable; ¤À¤ä¡C¥¦¹ê¦b¬O¥u¾A¦Xµ¹¨t²Îµo®iªÌ¥H¤Î¦³¼Ý¤Oªº·~¾l·R¦nªÌ¨Ï¥Î
 	    ¡C¦pªG·Q­n±o¨ì¦³Ãö¦p¦ó¨Ï¥Î -CURRENT ªº²`¤J¸ê°T¡A½Ð°Ñ¦Ò <ulink
             url="&url.books.handbook;/index.html">¨Ï¥Î¤â¥U</ulink> ªº <ulink
             url="&url.books.handbook;/cutting-edge.html#CURRENT">¬ÛÃö³¡¥÷</ulink>¡C
             </para>
 
           <para>¦pªG±z¹ï§@·~¨t²Î¥»¨­¨Ã¤£¬O«Ü¼ô±x¡A©Î¬O±z¨S¿ìªk¤À¿ë±z¹J¨ìªº°Ý
             ÃD¬O¯uªºµo¥Í¤F°ÝÃD¥ç©Î¬O¼È®É©Êªº¤pª¬ªp¡A¨º»ò±z´N¤£À³¸Ó¨Ï¥Î
             FreeBSD-CURRENT¡C³o­Ó¤À¤äªºµ{¦¡½X¦³®É­ÔÅܰʱo«Ü§Ö¡A¦Ó¥B¥i¯à·|¦]¦¹
             ¦Ó¨Ï±z¦³¦n´X¤Ñªº®É¶¡µLªk§ó·s±zªº¨t²Î¡C§Ú­Ì°²³]¨Ï¥Î
             FreeBSD-CURRENT ªº¨Ï¥ÎªÌ³£¦³¯à¤O¥h¤ÀªR¥L­Ì©Ò¹J¨ìªº°ÝÃD¨Ã¥B¥u¦^³ø
             ¯u¥¿ªº°ÝÃD¦Ó«D<quote>¤pª¬ªp</quote>¡C¦pªG±z¦b -CURRENT mailing
             list ¤¤´£¨ìÃþ¦ü<quote>make world ³y¦¨¤@¨Ç¦³Ãö groups ªº¿ù
             »~</quote>¤§Ãþªº°ÝÃDªº¸Ü¡A¤]³\·|³Q¨ä¥L¤H»´µø¡C</para>
 
           <para>§Ú­Ì¨C¤Ñ³£·|®Ú¾Ú¥Ø«e -CURRENT ©M -STABLE ªºª¬ªp¹ï³o¨â­Ó¤À¤ä¦U
             µo¦æ¤@­Ó<ulink URL="&url.base;/releases/snapshots.html">snapshot
             </ulink> ª©¡C¦³ªº®É­Ô¬Æ¦ÜÁÙ·|µo¦æ¥i¨Ñ¨ú±oªºª©¥»¡Cµoªí³o¨Ç snapshot
             ªº¥Øªº¦b©ó¡G</para>
 
           <itemizedlist>
             <listitem>
               <para>´ú¸Õ³Ì·sª©ªº¦w¸Ëµ{¦¡¡C</para>
             </listitem>
 
             <listitem>
               <para>´£¨Ñ¤@­Ó²³æªº¤èªkµ¹¨º¨Ç³ßÅw¨Ï¥Î -CURRENT ©Î¬O -STABLE ¦ý
                 ¬O¨S¦³®É¶¡©MÀW¼e¥h¨C¤Ñª@¯Åªº¨Ï¥ÎªÌ¡C</para>
             </listitem>
 
             <listitem>
               <para>¬°¤F´À§Ú­Ìµo®i¤¤ªºµ{¦¡«O¯d¤@­Ó©T©wªº°Ñ¦ÒÂI¡A¥H¨¾¤î§Ú­Ì¥¼
                 ¨Ó³y¦¨¤£©¯¡C(ÁöµM¤@¯ë¦Ó¨¥ CVS ¥i¥H¨¾¤îÃþ¦ü³oºØªº¥i©È¨Æ¥ó :)
                 </para>
             </listitem>
 
             <listitem>
               <para>¬°¤F½T«O©Ò¦³»Ý­n´ú¸Õªº·s¥\¯à³£¥i¥H±o¨ì³Ì¦hªº´ú¸Õ¡C</para>
             </listitem>
           </itemizedlist>
 
           <para>§Ú­Ì¤£¹ï -CURRENT snapshot °µ¥ô¦ó§Î¦¡ªº<quote>«~½è«O
             ÃÒ</quote>¡C¦pªG§A·Q­nªº¬O¤@­Óí©w¥B¸g¹L¥R¤À´ú¸Õ¹Lªº¨t²Îªº¸Ü¡A
             ³Ì¦n¿ï¾Ü¨Ï¥Î§¹¾ã release ªºª©¥»¡A©Î¬O¨Ï¥Î -STABLE snapshots¡C</para>
 
           <para>±z¥i¥Hª½±µ±q <ulink
             URL="ftp://current.FreeBSD.org/pub/FreeBSD/snapshots/">
             ftp://current.FreeBSD.org/pub/FreeBSD/snapshots/</ulink> ¨ú±o -CURRENT ªº
             snapshot release</para>
 
           <para>¹ï¨C­Ó¦³¦b¬¡°Êªº¤À¤ä¦Ó¨¥¡A¥­§¡¨C¤Ñ³£·|²£¥Í¤@¦¸ snapshots¡C
             </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="stable">
           <para>¤°»ò¬O FreeBSD-STABLE¡H</para>
         </question>
 
         <answer>
           <para>¦^·¹¨ì FreeBSD 2.0.5 ­èµoªíªº®É­Ô¡A§Ú­Ì¨M©w§â FreeBSD ªºµo®i
             ¤À¦¨¨â¤ä¡C¤@¤ä¥s°µ <ulink url="&url.books.handbook;/current-stable.html#STABLE">-STABLE</ulink>
 	    ¡A§Ú­Ì¥u¹ï¥¦°µ¿ù»~­×¥¿¤Î¤p´T«×ªº­×§ï (³o¬Oµ¹ ISP ©M°Ó·~¤½¥qµ¥¡A¹ï¹êÅ礤¥\¯à¤£·P¿³½ìªº³æ¦ì©Ò¨Ï¥Îªº)¡C
 	    ¥t¥~¤@¤ä¥s°µ <ulink url="&url.books.handbook;/current-stable.html#CURRENT">-CURRENT</ulink>¡A±q
             2.0 ª©µo¦æ¥H«á¡A´N¤£Â_¦a´ÂµÛ 6.0-RELEASE (§t«áÄòªºª©¥»)«e¶iµÛ¡C</para>
 
 	  <para>6-STABLE ¤À¤ä¬O±q 6.0-RELEASE ¶}©l(5-STABLE ¤À¤äºâ¬O 5.3-RELEASE ¤§«á¤~¶}©lªº)¡A
 	    µM«á­ì¥»ªº &os.current; ´N·|¦¨¬° 7-CURRENT¡C
 	    </para>
 
 
 	  <para>¤U­±´N¬Oª©¥»ºt¶iªº¥Ü·N¹Ï¡G</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 ends]
                   |                            (Mar 1997)
                   |
                   |
                   |  [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 [end]
                   |       (Mar 1997)    (Oct 97) (Apr 98) (Jul 98) (Dec 98)
                   |
                   |
                3.0-SNAPs  (started Q1 1997)
                   |
                   |
                3.0-RELEASE (Oct 1998)
                   |
                   |  [3.0-STABLE]
  *BRANCH*      3.1-RELEASE  (Feb 1999) -&gt; 3.2 -&gt; 3.3 -&gt; 3.4 -&gt; 3.5 -&gt; 3.5.1
                   |                     (May 1999) (Sep 1999) (Dec 1999) (June 2000) (July 2000)
                   |
                   |  [4.0-STABLE]
  *BRANCH*        4.0  (Mar 2000) -&gt; 4.1 -&gt; 4.1.1 -&gt; 4.2 -&gt; 4.3 -&gt; 4.4 -&gt; ... -&gt; 4.11
                   |
                   |              (July 2000)   (Sep 2000)   (Nov 2000)          (Jan 2005)
                   |
                   |  [5.0-STABLE]
  *BRANCH*        5.0  (2001) -&gt; 5.1 -&gt; 5.2 -&gt; 5.3 -&gt; 5.4 -&gt; ... future 5.x releases...
                   |
                   |              ( 2001)               (Nov 2004) (May 2005)
                   |
                   |  [6.0-STABLE]
  *BRANCH*        6.0  (Nov 2005) ... future 6.x releases...
                   |
                  \|/
                   +
           [7.0-CURRENT continues]</programlisting>
 
           <para>2.2-STABLE ³o­Ó¤À¤äÀHµÛ 2.2.8 ªºµoªí¦Ó¥\¦¨¨­°h¡C3-STABLE ³o­Ó
             ¤À¤ä«h¬Oµ²§ô¦b 3.5.1 µoªí¤§«á¡A¥¦¤]¬O 3.X ªº³Ì«á¤@¦¸µoªí¡C¤§«á°£¤F
             ¦w¥þ¬ÛÃöªº­×¥¿¤§¥~¡A³o¨â­Ó¤À¤ä´N´X¥G¨S¦³¦A§ó°Ê¹L¡C4-STABLE ¤À¤äªº¤ä´©
 	    ·|«ùÄò¨ì 2007/01/31¡A¦ý¥D­nµJÂI¦b©ó¦w¥þ¤è­±ªºº|¬}¡B¯äÂΤΨä¥LÄY­«°ÝÃDªº­×¸É¡C</para>
 
 	  <para>5-STABLE ¬O¥Ø«e¥¿¦bµo®i¤¤ªº -STABLE ¤À¤ä¡C5-STABLE ªº³Ì·sªº¤@
 	  ¦¸µoªí¬O¦b &rel2.current.date; µo¦æªº &rel2.current;-RELEASE¡C</para>
 
 	  <para>6-STABLE ¬O¥Ø«e¥¿¦bµo®i¤¤ªº -STABLE ¤À¤ä¡C6-STABLE ªº³Ì·sªº¤@
 	  ¦¸µoªí¬O¦b &rel.current.date; µo¦æªº &rel.current;-RELEASE¡C</para>
 
           <para>7-CURRENT ³o­Ó¤À¤ä¬O &os; ªº -CURRENT ¤À¤ä¡A¤´µM¤£Â_¦a¦bµo®i·í¤¤¡C
 	    ¦pªG·Q­nª¾¹D§ó¦hÃö©ó³o­Ó¤À¤äªº¸ê°Tªº¸Ü¡A½Ð°Ñ¦Ò <link
             linkend="current">¤°»ò¬O &os;-CURRENT¡H</link>¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="release-freq">
           <para>¨C¦¸·sªº FreeBSD ±N©ó¤°»ò®É­Ô±À¥X¡H</para>
         </question>
 
         <answer>
           <para>¤@¯ë¦Ó¨¥¡A&a.re; ¥­§¡¨C¥|­Ó¤ëµo¦æ¤@¦¸ release¡A¨C¦¸·sª©¥»ªºµoªí®Éµ{³£·|¨Æ¥ý¤½§i¡A
 	    ¬ÛÃöªº¶}µo¤H­û´N·|ª¾¹D¡A¤°»ò®É­Ô¸Ó¥ý§â¤âÃ䪺­p¹º§¹¦¨¨Ã¥B´ú¸Õ¹L¡A
 	    ¦¹¥~¡A³o¨Ç§ó°Ê³£¤w¸g§¹¾ã¦a´ú¸Õ¹L¡A¥B¤£·|¼vÅT¨t²Îí©w«×¡C
 	    ÁöµM¡Aµ¥³o¨Ç¦nªF¦è¶i¤J -STABLE ªº®É¶¡¥O¤Hµ¥±o¦³¨Ç¤£­@·Ð¡A
 	    ¦ý¬O¤j¦h¼Æªº¨Ï¥ÎªÌ³£»{¬°³oºØÂÔ·VªººA«×¬O FreeBSD ³Ì¦nªºÀuÂI¤§¤@¡C</para>
 
 	  <para>¦³Ãöµo¦æ±¡³øªº§ó¦h²Ó¸`³¡¤À(¥]¬A release ªº¦æµ{ªí¡B¶i«×)¡A³£¥i¦b FreeBSD ºô¯¸¤Wªº
 	    <ulink url="http://www.FreeBSD.org/releng/index.html">µo¦æ±¡³ø</ulink> ¤W­±Àò±o¡C</para>
 
           <para>¬°¤Fº¡¨¬¨º¨Ç»Ý­n (©Î·Q­n) ·sÂA¨ë¿E·Pªº¨Ï¥ÎªÌ¡A
 	    ¤W­±(-CURRENTªº³¡¤À)¤w¸g´£¨ì§Ú­Ì¨C¤Ñ³£·|µo¦æ snapshots ª©¥i¨Ñ¨Ï¥Î¡C</para>
          </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="responsible">
           <para>½Ö­t³d FreeBSD ªºµo®i¡H</para>
         </question>
 
         <answer>
           <para>¦pªG¬O¤@¨Ç¦³Ãö FreeBSD ­pµeªºÃöÁä©Ê¨M©w¡A¹³¬O¾ã­Ó­pµeªº¨«¦V
             ©Î¬O¨M©w½Ö¥i¥H§ï source tree ¸Ìªºµ{¦¡½X³oÃþªº¨Æ¡A¬O¥Ñ¤@­Ó¥Ñ 9 ­Ó
             ¤H©Ò²Õ¦¨ªº <ulink 
 	    url="&url.articles.contributors;/article.html#STAFF-CORE">core
             team</ulink> ¨Ó¨M©w¡C¦Ó¦³¥t¤@¸s¶W¹L 300 ­Ó¤Hªº <ulink
             url="&url.articles.contributors;/article.html#STAFF-COMMITTERS">
             commiters</ulink> ¦³Åv§Q¥i¥Hª½±µ­×§ï FreeBSD ªº source tree¡C
             </para>
 
           <para>µL½×¦p¦ó¡A¤j¦h¼Æªº§ïÅܳ£·|¨Æ«e¦b <link linkend="mailing">
             mailing lists</link> ¥ý°Q½×¹L¡A¦Ó¥B¤£¤À¨¤¦â¡A¨C­Ó¤H³£¥i¥H°Ñ»P°Q½×¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="where-get">
           <para>§Ú­n¦p¦ó¨ú±o FreeBSD¡H</para>
         </question>
 
         <answer>
           <para>¨C­Ó FreeBSD ªº­«­nª©¥»³£¥i¥H¸g¥Ñ°Î¦W ftp ±q <ulink
             url="ftp://ftp.FreeBSD.org/pub/FreeBSD/">FreeBSD FTP ¯¸</ulink>¨ú±o¡G</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>¦pªG»Ý­n 6-STABLE ªº³Ì·sª©¡A¤]´N¬O &rel.current;-RELEASE¡A½Ð¨ì <ulink
 	        url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/">&rel.current;-RELEASE </ulink>³o­Ó¥Ø¿ý</para>
 	    </listitem>
 
 	    <listitem>
 	      <para><ulink url="ftp://current.FreeBSD.org/pub/FreeBSD/">7-CURRENT Snapshot</ulink> 
 	        ³q±`¤]¬O¨C¤Ñ³£·|°µ¤@¥÷¡A³o¬O±q <link linkend="current">-CURRENT</link> ¤À¤ä°µ¥X¨Óªº¡A
 	        ¥D­n¬O¬°¤F´£¨Ñµ¹¨º¨Ç¼ö¤ßªº´ú¸ÕªÌ©M¶}µo¤H­û¡C</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>¦pªG»Ý­n 5-STABLE ªº³Ì·sª©¡A¤]´N¬O &rel2.current;-RELEASE¡A½Ð¨ì <ulink
 	        url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel2.current;-RELEASE/">&rel2.current;-RELEASE </ulink>³o­Ó¥Ø¿ý</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>¦pªG»Ý­n 4-STABLE ªº³Ì·sª©¡A¤]´N¬O 4.11-RELEASE¡A½Ð¨ì <ulink
 	        url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/4.11-RELEASE/">4.11-RELEASE </ulink>³o­Ó¥Ø¿ý</para>
 	    </listitem>
 
 	    <listitem>
 	      <para><ulink
 	        url="ftp://current.FreeBSD.org/pub/FreeBSD/snapshots/">4.X¡B5.X¡B6X snapshots</ulink> 
 	        ³q±`¨C¤Ñ³£·|°µ¤@¥÷¡C</para>
 	    </listitem>
           </itemizedlist>
 
 	  <para>FreeBSD ªº CD¡BDVD¡AÁÙ¦³¨ä¥L¨ú±o¤è¦¡¥i¥H¦b <ulink url="&url.books.handbook;/mirrors.html">¨Ï¥Î¤â¥U</ulink> ¤¤§ä¨ì¸Ñµª¡C</para>
         </answer>
       </qandaentry>
 
-      <qandaentry>
-	<question id="howto-mirror">
-	  <para>«ç»ò«Ø¥ß FreeBSD ªº¬M®g(mirror)¯¸¥x¡H</para>
-	</question>
-
-	<answer>
-	  <para>¦³Ãö¦p¦ó«Ø¥ß FreeBSD ¬M®g¯¸(mirror)ªº¸ê®Æ¡A¥i¥H°Ñ¦Ò <ulink 
-	    url="&url.articles.hubs;/">Mirroring FreeBSD</ulink> ¤å³¹</para>
-	</answer>
-      </qandaentry>
-
       <qandaentry>
         <question id="access-pr">
           <para>§Ú­n¦p¦ó¥h¬d¸ß¡B´£¥æ°ÝÃD¦^³ø(Problem Report¡A²ºÙPR)¸ê®Æ®w©O¡H</para>
         </question>
 
         <answer>
           <para>©Ò¦³¨Ï¥ÎªÌªºÅܧó­n¨D³£¥i¥H¸g¥Ñºô­¶¤¶­±ªº
             <ulink URL="http://www.FreeBSD.org/cgi/query-pr-summary.cgi?query">
             PR¬d¸ß¤¶­±</ulink> ¨Ó¹î¬Ý (©Î¬O¦^³ø) §Ú­Ìªº¿ù»~¦^³ø¸ê®Æ®w¡C</para>
 
 	  <para>¤]¥i¥H¨Ï¥Î &man.send-pr.1; ³o­Ó«ü¥O³z¹L¹q¤l¶l¥ó¨Ó¦^³ø°ÝÃD¡B­n¨DÅܧó¡C
 	  ©ÎªÌ¬O¸g¥Ñ <ulink url="http://www.FreeBSD.org/send-pr.html">ºô­¶¤¶­±ªº PR</ulink> ¨Ó°e¥X°ÝÃD¦^³ø¡C</para>
 
           <para>µM¦Ó¡A¦b±z¦^³ø°ÝÃD¤§«e¡A½Ð¥ý¾\Ū <ulink
             URL="&url.articles.problem-reports;/article.html">¦p¦ó¼¶¼g
             FreeBSD ªº°ÝÃD¦^³ø³æ</ulink>¡A³o¬O¤@½g§i¶D§A«ç¼Ë¤~¯à¼g¥X¤@½g¯u¥¿¦³¥Îªº
             °ÝÃD¦^³ø³æ¡C</para>
         </answer>
       </qandaentry>
 
-      <qandaentry>
-        <question id="become-web-mirror">
-          <para>­n«ç¼Ë¤~¯à¦¨¬° FreeBSD ªººô­¶¬M®g(mirror)¯¸¥x¡H</para>
-        </question>
-
-        <answer>
-          <para>¦³«Ü¦h¤èªk¥i¥H¬M®g(mirror)§Ú­Ìªººô­¶¡C</para>
-
-          <itemizedlist>
-            <listitem>
-              <para>±z¥i¥H§Q¥Î <filename role="package">net/cvsup</filename>
-                ±q cvsup.FreeBSD.org ¨ú±o®æ¦¡¤Æ¹LªºÀɮסC
-                <filename>/usr/share/examples/cvsup/www-supfile</filename>
-	        ³oÀÉ´N¬O¤@­Ó±Ð§A«ç¼Ë°µºô­¶¬M®gªº CVSup ³]©w½d¨Ò¡C
-              </para>
-            </listitem>
-
-            <listitem>
-              <para>±z¥i¥H§Q¥Î±z³ßÅwªº ftp mirror ¤u¨ã±q FreeBSD ªº FTP ¯¸»O
-                ¤¤¨ú±oºô­¶ªº­ì©l½X¡C¦ý¬O­nª`·Nªº¬O¦b§A¥´ºâ´£¨Ñ¤½¶}ªA°È¤§«e¡A
-                °O±o­n¥ý§Q¥Î³o¨Ç­ì©l½X§âºô­¶­««Ø°_¨Ó¡C½Ð±q <ulink
-                url="ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/www"></ulink> ¶}©l§ì¨ú¡C</para>
-            </listitem>
-          </itemizedlist>
-        </answer>
-      </qandaentry>
-
       <qandaentry>
         <question id="other-info-sources">
           <para>ÁÙ¦³¨ä¥L¦³Ãö FreeBSD ªº¸ê°T¶Ü¡H</para>
         </question>
 
         <answer>
           <para>¸Ô¨£ <ulink
             url="http://www.FreeBSD.org">FreeBSD</ulink> ºô¯¸¤Wªº <ulink
             url="http://www.FreeBSD.org/docs.html">¤å¥ó</ulink> ¦Cªí¡C</para>
         </answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter id="support">
     <chapterinfo>
       <author>
 	<firstname>Chin-San</firstname>
 	<surname>Huang</surname>
 	<affiliation>
 	  <address><email>chinsan.tw@gmail.com</email></address>
 	</affiliation>
       </author>
     </chapterinfo>
 
     <title>¤å¥ó»P¤ä´©</title>
     
     <qandaset>
       <qandaentry>
 	<question id="books">
 	  <para>Ãö©ó FreeBSD ¦³­þ¨Ç¦n®Ñ¥i¥H±ÀÂ˾\Ūªº¶Ü¡H</para>
 	</question>
 	
 	<answer>
 	  <para>FreeBSD ¤å¥ó­pµe¤w³°Äòµoªí¤F¬Û·í¼sªx½d³òªº¤å¥ó¡A¥i¦b <ulink
 	    url="http://www.FreeBSD.org/docs.html"></ulink> ¨ú±o¡C¥t¥~¡A
 	    FreeBSD ¥»¨­ªº manual(¤@¯ë³qºÙªºman)¡Bdoc¤]¦p¦P®M¥ó³nÅé¤@¼Ë¡A¥i¥H»´ÃP¦a¸Ë¦b±z¨t²Î¤W¡C
 	    </para>
 	    
 	    <para>¦¹¥~¡A¤]«Øij°Ñ¾\¥»¥÷ FAQ ³Ì«á©Ò¦Cªº°Ñ¦Ò®Ñ¥Øªí(Bibliography)»P FreeBSD ¨Ï¥Î¤â¥U¡C
 	    </para>
 	</answer>
       </qandaentry>
       
       <qandaentry>
         <question id="doc-formats">
           <para>³o¨Ç¤å¥ó¦³¨ä¥L®æ¦¡ªº¶Ü¡H¹³¬O¡G¯Â¤å¦r(ASCII)©Î &postscript; ¤§Ãþªº®æ¦¡¡H</para>
         </question>
 
         <answer>
           <para>¦³ªº¡C³o¨Ç¤å¥ó³£¤À§O¥H¤£¦P®æ¦¡Àx¦s¥H¤ÎÀ£ÁY³B²z¡A©ñ¦b
             FTP ¤W­±¡A¥i¥H±q¦U FreeBSD FTP ¯¸ªº <ulink
             url="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">/pub/FreeBSD/doc/</ulink>
             ¥Ø¿ý¤º§ä¨ì§A­nªº¡C</para>
 
           <para>¤å¥óªº¤ÀÃþ¤è­±¥D­n¬O¤@¨Ç¤£¦P©Ê½è©Ò²Õ¦¨¡G</para>
 
           <itemizedlist>
             <listitem>
 	      <para>¤å¥ó¦WºÙ¡A¤ñ¦p¡G<literal>faq(±`¨£°Ýµª¶°)</literal>©Î¬O
                 <literal>handbook(FreeBSD ¨Ï¥Î¤â¥U)</literal>µ¥µ¥¡C</para>
             </listitem>
 
             <listitem>
               <para>¦U°ê½Ķªºªº¤å¥ó¡G³o¥D­n¬O¥Ñ locale ¦WºÙ¨Ó¨M©wªº
 	        (¤£²M·¡ªº¸Ü¡A¥i°Ñ¦Ò±zªº FreeBSD §@·~¨t²Î¤Wªº <filename>/usr/share/locale</filename>)
 	        ¥Ø«e¤å¥óÁ`¦@¦³¤U¦C´XºØ»y¨¥(¤Î½s½X)¦³Â½Ä¶¡G</para>
 
               <informaltable frame="none" pgwide="1">
                 <tgroup cols="2">
                   <thead>
                     <row>
                       <entry>Locale ¦WºÙ</entry>
 
                       <entry>»¡©ú(©Ò¥Nªíªº»y¨t¡B½s½X)</entry>
                     </row>
                   </thead>
 
                   <tbody>
                     <row>
                       <entry><literal>en_US.ISO8859-1</literal></entry>
 
                       <entry>¬ü¦¡­^¤å(US English)</entry>
                     </row>
 
                     <row>
                       <entry><literal>de_DE.ISO8859-1</literal></entry>
 
                       <entry>¼w¤å(German)</entry>
                     </row>
 
                     <row>
                       <entry><literal>es_ES.ISO8859-1</literal></entry>
 
                       <entry>¦è¯Z¤ú¤å(Spanish)</entry>
                     </row>
 
                     <row>
                       <entry><literal>fr_FR.ISO8859-1</literal></entry>
 
                       <entry>ªk¤å(French)</entry>
                     </row>
 
 		    <row>
 		      <entry><literal>it_IT.ISO8859-15</literal></entry>
 
 		      <entry>¸q¤j§Q¤å(Italian)</entry>
 		    </row>
 
                     <row>
                       <entry><literal>ja_JP.eucJP</literal></entry>
 
                       <entry>¤é¤å(Japanese¡A½s½X¤è¦¡¡GEUC)</entry>
                     </row>
 
                     <row>
                       <entry><literal>ru_RU.KOI8-R</literal></entry>
 
                       <entry>«X¤å(Russian¡A½s½X¤è¦¡¡GKOI8-R)</entry>
                     </row>
 
                     <row>
                       <entry><literal>zh_TW.Big5</literal></entry>
 
                       <entry>¥¿Å餤¤å(Chinese¡A½s½X¤è¦¡¡GBig5)</entry>
                     </row>
                   </tbody>
                 </tgroup>
               </informaltable>
 
               <note>
                 <para>¤W¦Cªº¦U°ê½Ķ»y¨t¤å¥ó¤¤¡A¨Ã«D©Ò¦³¤å¥ó³£¦³Â½Ä¶¡C</para>
               </note>
             </listitem>
 
             <listitem>
 	      <para>¤å¥óªº®æ¦¡¡G¨C¥÷¤å¥ó³£¥H¦UºØ¤£¦P®æ¦¡Àx¦s¡A¨CºØ®æ¦¡³£¦U¦³¦nÃa¡A
 	        ¦³¨Ç®æ¦¡¾A¦X½u¤W¾\Ū¡A¦Ó¦³¨Ç«h¾A¦X¦C¦L¥X¬üÆ[ªº¤å¥ó¡C
 	        §Ú­Ì³£´£¨Ñ³o¨Ç¤£¦P®æ¦¡ªº¤å¥ó¡A¨Ó½T«OµL½×¬O¿Ã¹õ¤W¡B¦C¦L¯È¥»¡A¨C­Ó¤H³£¥i¥H¥¿±`¦a¾\Ū¤º®e¡A
                 ¥Ø«e¥i¨Ñ¨Ï¥Îªº®æ¦¡¦p¤U:</para>
 
               <informaltable frame="none" pgwide="1">
                 <tgroup cols="2">
                   <thead>
                     <row>
                       <entry>®æ¦¡</entry>
 
                       <entry>»¡©ú</entry>
                     </row>
                   </thead>
 
                   <tbody>
                     <row>
                       <entry><literal>html-split</literal></entry>
 
                       <entry>³¹¸`¼Ò¦¡</entry>
                     </row>
 
                     <row>
                       <entry><literal>html</literal></entry>
 
                       <entry>§¹¾ã¼Ò¦¡</entry>
                     </row>
 
                     <row>
                       <entry><literal>pdb</literal></entry>
 
                       <entry>Palm Pilot ¸ê®Æ®æ¦¡¡A¨Ï¥Î
                         <ulink url="http://www.iSilo.com/">iSilo</ulink>
                         µ{¦¡¨Ó¾\Ū</entry>
                     </row>
 
                     <row>
                       <entry><literal>pdf</literal></entry>
 
                       <entry>Adobe's PDF ®æ¦¡</entry>
                     </row>
 
                     <row>
                       <entry><literal>ps</literal></entry>
 
                       <entry>&postscript; ®æ¦¡</entry>
                     </row>
 
                     <row>
                       <entry><literal>rtf</literal></entry>
 
                       <entry>Microsoft's RTF®æ¦¡<footnote>
                           <para>·í¨Ï¥Î MS Word ¨Ó¶}±Ò RTF ®æ¦¡ªº¸Ü¡A­¶¼ÆÅã¥Ü¨Ã¤£·|¦Û°Ê§ó·s¡C
                           (¦b¶}±Ò¤å¥ó«á¡A­n«ö <keycombo
                           action="simul"><keycap>CTRL</keycap><keycap>A</keycap></keycombo>,
                           <keycombo
                           action="simul"><keycap>CTRL</keycap><keycap>END</keycap></keycombo>,
                           <keycap>F9</keycap>¡A³o¼Ë¤l¤~·|§ó·s­¶¼ÆªºÅã¥Ü¡C)</para>
                         </footnote>
                       </entry>
                     </row>
 
                     <row>
                       <entry><literal>txt</literal></entry>
 
                       <entry>¯Â¤å¦r(ASCII)</entry>
                     </row>
                   </tbody>
                 </tgroup>
               </informaltable>
             </listitem>
 
             <listitem>
               <para>¤å¥óªºÀ£ÁY¡B¥´¥]¤è¦¡¡G¥Ø«e¦³¤TºØ¤è¦¡¡G</para>
 
               <orderedlist>
                 <listitem>
                   <para>·í±Ä¥Î
                     <literal>³¹¸`¼Ò¦¡(html-split)</literal>¡A³¹¸`¼Ò¦¡©Ò²£¥Íªº¦UÀÉ®×·|¥ý¨Ï¥Î 
 	              &man.tar.1; ¨ÓÀ£ÁY¡CÀɦWµ²§À¦³ <filename>.tar</filename> ªºÀÉ®×´N¬O tar ®æ¦¡¡C
 		      ±µµÛ¡A·|¦A¥H¤U¦C¤è¦¡¦AÀ£ÁY¡C
 	          </para>
                 </listitem>
 
                 <listitem>
                   <para>¨ä¥L®æ¦¡ªºÀɮ׳£·|¬O³æ¤@ÀɮסAÀɦW³q±`·|¬O¡G
                     <filename>book.<replaceable>®æ¦¡</replaceable></filename>
                     (Á|¨Ò¡G <filename>book.pdb</filename>¡A
                     <filename>book.html</filename> µ¥µ¥..«á­±³q±`¥[¤W¡y.®æ¦¡¡z).</para>
 		  <para>¦Ó³o¨ÇÀÉ®×·|¤À§O¥H¨âºØÀ£ÁY«¬ºA¶i¦æÀ£ÁY¡A¦Ó¦s¦¨¨âºØÀ£ÁY«¬ºA¡C</para>
 
                   <informaltable frame="none" pgwide="1">
                     <tgroup cols="2">
                       <thead>
                         <row>
                           <entry>®æ¦¡</entry>
 
                           <entry>»¡©ú</entry>
                         </row>
                       </thead>
 
                       <tbody>
                         <row>
                           <entry><literal>zip</literal></entry>
 
                           <entry>Zip ®æ¦¡¡A­Y­n¦b FreeBSD ¤W¸ÑÀ£ zip ÀÉ¡A«h¥²¶·¥ý¦w¸Ë 
 	                    <filename role="package">chinese/unzip</filename> ©Î
 		            <filename role="package">archivers/unzip</filename>¡C
                             </entry>
                         </row>
 
                         <row>
                           <entry><literal>bz2</literal></entry>
 
                           <entry>BZip2 ®æ¦¡¡AÁöµM¤£¦p zip ®æ¦¡ªº¼sªx¨Ï¥Î¡A¦ý¬O¦n³B¦b©ó¥iÀ£ÁY¦¨§ó¤pªºÀɮסC
 	                    ­n¸ÑÀ£ bz2 ®æ¦¡ªº¸Ü¡A»Ý¥ý¦w¸Ë <filename role="package">archivers/bzip2
 	                    </filename>¡C</entry>
                         </row>
                       </tbody>
                     </tgroup>
                   </informaltable>
 
                   <para>©Ò¥H¹³¬O Handbook ªº &postscript; ª©®æ¦¡¡A·|¥H BZip2 ®æ¦¡À£ÁY¡A
 	             ¦s©ñ¦b <filename>handbook/</filename> ¥Ø¿ý¤º¡A
 	             ÀɦW´N¬O<filename>book.ps.bz2</filename>¡C</para>
                 </listitem>
               </orderedlist>
             </listitem>
           </itemizedlist>
 
           <para>¿ï¾Ü·Q­n¤U¸üªº¤å¥ó®æ¦¡»PÀ£ÁY«¬ºA¤§«á¡A«h­n¨M©w¬O§_¥H FreeBSD <emphasis>®M¥ó(package)</emphasis>
 	    «¬ºA¨Ó¤U¸ü¡C</para>
 
           <para>¤U¸ü¡B¦w¸Ë¡ypackage¡zªº¦n³B¦b©ó¡G¥i¥H³z¹L¤@¯ë FreeBSD
 	    ®M¥óºÞ²z¤è¦¡¨Ó¶i¦æºÞ²z¡A¤ñ¦p &man.pkg.add.1; ¤Î
             &man.pkg.delete.1;¡C</para>
 
 
 	  <para>­Y¨M©w¦n­n¤U¸ü¡B¦w¸Ë¡ypackage¡zªº¸Ü¡A¥²¶·­n½T»{©Ò­n¤U¸üªºÀɦW¡C
 	    ¤å¥ó­pµeªº®M¥ó(package)³q±`¬O©ñ¦b¬O <filename>packages</filename> ªº¥Ø¿ý¤º¡A
             ¨C­Ó¤å¥ó­pµeªº®M¥óÀɦW³q±`¬O¡G
 	    <filename><replaceable>¤å¥ó¦WºÙ</replaceable>.<replaceable>»y¨t</replaceable>.<replaceable>½s½X</replaceable>.<replaceable>®æ¦¡</replaceable>.tgz</filename>
 	    ¡C</para>
 
           <para>Á|­Ó¨Ò¤l¡A­^¤åª©ªº FAQ (®æ¦¡¿ï¾Ü PDF)¦b package ´N¥s°µ
             <filename>faq.en_US.ISO8859-1.pdf.tgz</filename>¡C</para>
 
           <para>¦AÁ|­Ó¨Ò¤l¡A¤¤¤åª©ªº FAQ (®æ¦¡¿ï¾Ü PDF)¦b package ´N¥s°µ
             <filename>faq.zh_TW.Big5.pdf.tgz</filename>¡C</para>
 
           <para>ª¾¹D³oÂI¤§«á¡A´N¥i¥H¥Î¤U­±«ü¥O¨Ó¦w¸Ë¤¤¤åª© FAQ ®M¥ó¡G</para>
 
           <screen>&prompt.root; <userinput>pkg_add ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/packages/faq.zh_TW.Big5.pdf.tgz</userinput></screen>
 
           <para>§¹¦¨¤§«á¡A¥i¥H¥Î &man.pkg.info.1; ¨Ó§ä¥XÀɮ׸˦b­þÃä¡G</para>
 
           <screen>&prompt.root; <userinput>pkg_info -f faq.zh_TW.Big5.pdf</userinput>
 Information for faq.zh_TW.Big5.pdf:
 
 Packing list:
         Package name: faq.zh_TW.Big5.pdf
         CWD to /usr/share/doc/zh_TW.Big5/books/faq
 File: book.pdf
         CWD to .
 File: +COMMENT (ignored)
 File: +DESC (ignored)</screen>
 
           <para>¦p¦P±z©Ò¬Ý¨ìªº <filename>book.pdf</filename> ·|³Q¦w¸Ë¨ì
             <filename>/usr/share/doc/zh_TW.Big5/books/faq</filename> ¤º¡C</para>
 
           <para>­Y¤£·Q¥Î package ¤è¦¡¦w¸Ë¡A¨º»ò´N»Ý¤â°Ê¤U¸ü¡B¸ÑÀ£ÁY¡B½Æ»s¨ì§A·Q­nÂ\©ñªº¦ì¸m¥h¡C</para>
 
           <para>Á|¨Ò¡A³¹¸`¼Ò¦¡(split HTML)ª©ªº­^¤å FAQ (À£ÁY¬° &man.bzip2.1;)·|©ñ¦b
             <filename>doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2</filename>
             ­n¤U¸ü¡B¸ÑÀ£ªº¸Ü¡A«h­n¥´¡G</para>
 
           <screen>&prompt.root; <userinput>fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2</userinput>
 &prompt.root; <userinput>bzip2 -d book.html-split.tar.bz2</userinput>
 &prompt.root; <userinput>tar xvf book.html-split.tar</userinput></screen>
 
           <para>³o®É§A·|¬Ý¨ì¤@°ï <filename>.html</filename> ªºÀɮסA
 	    ¥D­nªº¥Ø¿ýÀɬ° <filename>index.html</filename>
 	    ¤º§t¥D¥Ø¿ý¤Î³sµ²¨ì¨ä¥L¤å¥ó¡C(­Y¦³»Ý­nªº¸Ü¡A¤]¥i¥H½Æ»s©Î·h²¾³o¨ÇÀɮרì¦P¤@¥Ø¿ý¤U)</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="mailing">
           <para>­þ¸Ì¦³Ãö©ó FreeBSD ªº¶l»¼½×¾Â(mailing lists)©O¡H</para>
         </question>
 
         <answer>
           <para>³o­Ó°ÝÃD¡A¥i¥H±q FreeBSD ¨Ï¥Î¤â¥U¤W­±ªº <ulink 
 	  url="&url.books.handbook;/eresources.html#ERESOURCES-MAIL">¶l»¼½×¾Â(mailing-lists)</ulink>
 	  ³¡¤ÀÀò±oµª®×¡C</para>
         </answer>
       </qandaentry>
 
-      <qandaentry>
-        <question id="y2k">
-          <para>§Ú¸Ó±q­þÃä±o¨ì¦³Ãö FreeBSD ¦b¤dÁHÂÎ(Y2K)¤è­±ªº¸ê®Æ©O?</para>
-        </question>
-
-        <answer>
-          <para>³oµª®×¥i¥H¦b <ulink
-            url="&url.base;/y2kbug.html">FreeBSD ¤dÁHÂÎ(Y2K)</ulink>¤W­±Àò±o</para>
-        </answer>
-      </qandaentry>
-
       <qandaentry>
         <question id="newsgroups">
           <para>¦³­þ¨Ç¥i¥H¨Ï¥Îªº FreeBSD ·s»D¸s²Õ(news groups)©O?</para>
         </question>
 
         <answer>
           <para>³oµª®×¥i¥H±q FreeBSD ¨Ï¥Î¤â¥U¤W­±ªº  <ulink
             url="&url.books.handbook;/eresources-news.html">·s»D¸s²Õ(newsgroups)</ulink>
 	    ³¡¤ÀÀò±oµª®×¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="irc">
           <para>¦³­þ¨Ç FreeBSD IRC (Internet Relay Chat)ÀW¹D©O¡H</para>
         </question>
 
         <answer>
           <para>¦³ªº¡A¤j³¡¤Àªº IRC ¥D¾÷³£¦³ FreeBSD ²á¤ÑÀW¹D¡G</para>
 
           <itemizedlist>
             <listitem>
               <para><ulink url="http://www.efnet.org/index.php">EFNet</ulink> ªº
-		<literal>#FreeBSD</literal> ÀW¹D
-                is a FreeBSD forum, but do not go there for tech
-                support or try to get folks there to help you avoid
-                the pain of reading manual pages or doing your own research.
-                It is a chat channel, first and foremost, and topics there
-                are just as likely to involve sex, sports or nuclear
-                weapons as they are FreeBSD.  You Have Been Warned!
-                Available at server <hostid>irc.chat.org</hostid>.</para>
+		<literal>#FreeBSD</literal> ÀW¹D¬O­Ó FreeBSD ½×¾Â¡A
+	        ¦ý¥i¤£¾A¦X¨º¨Ç·Q¤£³Ò¦ÓÀò©ÎªÌ·h±Ï§L¥Îªº¡C
+	        ³o¸Ì¬O²á¤Ñ¥ÎªºÀW¹D¡A¸ÜÃD½d³ò¬Æ¦Ü¯A¤Î¡y©Ê¡B¹B°Ê¡B®ÖªZ¡zµ¥¡A
+	        ½Ðª`·N¡G§Ú­Ì¤w¸gĵ§i¹L§A¤F¡I¥»ÀW¹D¥i¸g¥Ñ <hostid>irc.chat.org</hostid> ¶i¤J¡C</para>
             </listitem>
 
             <listitem>
-              <para>Channel <literal>#FreeBSDhelp</literal> on
-                <ulink url="http://www.efnet.org/index.php">EFNet</ulink>
-                is a channel dedicated to helping FreeBSD users. They
-                are much more sympathetic to questions than
-                <literal>#FreeBSD</literal> is.</para>
+              <para><ulink url="http://www.efnet.org/index.php">EFNet</ulink> ªº
+	        <literal>#FreeBSDhelp</literal> ÀW¹D ¤D¬Oµ¹ FreeBSD ¨Ï¥ÎªÌ¤§¶¡¥æ¬yªº¡A
+	        ¨Ó³o¸Ì´£°Ý·|¤ñ <literal>#FreeBSD</literal> ¦n¤@¨Ç¡A·íµM½Ð¤£­n¤@ªÑ¸£ÀH«K¶Ã°Ý¡C</para>
             </listitem>
 
             <listitem>
-              <para>Channel <literal>#FreeBSD</literal> on
-                <ulink url="http://www.dal.net/">DALNET</ulink>
-                is available at <hostid>irc.dal.net</hostid> in the
-                US and  <hostid>irc.eu.dal.net</hostid> in Europe.</para>
+              <para><ulink url="http://www.dal.net/">DALNET</ulink> ªº 
+	        <literal>#FreeBSD</literal> ÀW¹D¡A¥i¥Ñ <hostid>irc.dal.net</hostid>(¦ì©ó¬ü°ê)¤Î
+                <hostid>irc.eu.dal.net</hostid>(¦ì©ó¼Ú¬w)¶i¤J¡C</para>
             </listitem>
 
             <listitem>
-              <para>Channel <literal>#FreeBSDHelp</literal> on
-                <ulink url="http://www.dal.net/">DALNET</ulink>
-                is available at <hostid>irc.dal.net</hostid> in the
-                US and <hostid>irc.eu.dal.net</hostid> in Europe.
-		The channel owners also have a web page with useful
-		information about the channel and &os;, available at
+              <para><ulink url="http://www.dal.net/">DALNET</ulink> ªº
+	        <literal>#FreeBSDHelp</literal> ÀW¹D¡A¥i¥Ñ <hostid>irc.dal.net</hostid>(¦ì©ó¬ü°ê)¤Î
+	        <hostid>irc.eu.dal.net</hostid>(¦ì©ó¼Ú¬w)¶i¤J¡C
+	        ¥»ÀW¹Dªº¥D«ùªÌ¦³«Ø¥ß¦³Ãö¸ÓÀW¹D»P &os; ªººô­¶¡A¦b
 		<ulink url="http://www.freebsdhelp.net/"></ulink>.</para>
             </listitem>
 
             <listitem>
-              <para>Channel <literal>#FreeBSD</literal> on
-                <ulink url="http://www.undernet.org/">UNDERNET</ulink>
-                is available at <hostid>us.undernet.org</hostid>
-                in the US and  <hostid>eu.undernet.org</hostid> in Europe.
-                Since it is a help channel, be prepared to read the
-                documents you are referred to.</para>
+              <para><ulink url="http://www.undernet.org/">UNDERNET</ulink> ªº
+	        <literal>#FreeBSD</literal> ÀW¹D¡A¥i¥Ñ <hostid>us.undernet.org</hostid>(¦ì©ó¬ü°ê)¤Î
+	        <hostid>eu.undernet.org</hostid>(¦ì©ó¼Ú¬w)¶i¤J¡C¥Ñ©ó³o¬O­Ó»²§U·s¤â¥ÎªºÀW¹D¡A
+	        ½Ð°O±o¾\Ū§O¤H¦V§A´£¤Îªº³sµ²©ÎÀɮסC</para>
             </listitem>
 
 	    <listitem>
-	      <para>Channel <literal>#FreeBSD</literal> on
-		<ulink url="http://www.rusnet.org.ru/">RUSNET</ulink>
-		is a russian-language oriented channel dedicated
-		to helping &os; users.  This is also good place
-		for non-technical discussions.</para>
+	      <para><ulink url="http://www.rusnet.org.ru/">RUSNET</ulink> ªº
+		<literal>#FreeBSD</literal> ÀW¹D¬O«X»y°ê®aªº &os; ¨Ï¥ÎªÌÀW¹D¡C
+		³o¸Ì¦P®É¤]¬O¤@¯ë¥æ¬yªº°Q½×¦n¥h³B¡C</para>
+	    </listitem>
+
+	    <listitem>
+	      <para><ulink url="http://freenode.net/irc_servers.shtml">freebsd-gnome</ulink> ªº
+		<literal>#FreeBSD</literal> ÀW¹D¡A¥i¥Ñ <hostid>irc.freenode.net</hostid> ¶i¤J¡A
+	        ³o¬O Gnome ªº &os; ¨Ï¥ÎªÌÀW¹D¡C</para>
+	    </listitem>
+
+	    <listitem>
+	      <para><ulink url="http://bsdchat.com/">IRCNet</ulink> ªº
+		<literal>#BSDChat</literal> ÀW¹D¡A¥i¥Ñ <hostid>irc.seed.net.tw</hostid> ©Î
+		<hostid>irc.csie.nctu.edu.tw</hostid> ©Î <hostid>irc.tw.freebsd.org</hostid> ¶i¤J
+	        ³o¬O¥xÆWªº &os; ¨Ï¥ÎªÌÀW¹D¡C</para>
 	    </listitem>
           </itemizedlist>
 
-          <para>Each of these channels are distinct and are not
-            connected to each other.  Their chat styles also differ,
-            so you may need to try each to find one suited to your
-            chat style.  As with <emphasis>all</emphasis> types of IRC
-            traffic, if you are easily offended or cannot deal with
-            lots of young people (and more than a few older ones)
-            doing the verbal equivalent of jello wrestling, do not
-            even bother with it.</para>
+          <para>¤W­z¨C­ÓÀW¹D³£¤£¤@¼Ë¡A­·®æ­~²§¦Ó¦U¨ã¯S¦â¡A¥B¨Ã¨S¦³¬Û³s¡A
+	    ¦]¦¹¡A§A±o¦h¤è¹Á¸Õ¤~¯à§ä¨ì¾A¦X¦Û¤vªºÀW¹D¡C¦Ó¦³¨Ç¦a¤è»P©Ò¦³ªº IRC ¤å¤ÆÃþ¦ü¡A
+	    ´N¬O½Ðª`·N¦Û¤v¨¥¦æ¬O§_«ê·í¡A¥t¥~¥i¯à¸òÀW¹D¤º¤@¨Ç¦~»´/¦Ñ¤@½úªº¡A·|¦³¨Ç¥N·¾»Ý­n¾AÀ³¡C
         </answer>
       </qandaentry>
 
       <qandaentry>
 	<question id="training">
 	  <para>¥i¥H±q­þÃäÀò±o FreeBSD ªº°Ó·~½Òµ{°V½m¤Î§Þ³N¤ä´©©O¡H</para>
 	</question>
 
 	<answer>
 	  <para>DaemonNews ¦³±Mªù´£¨Ñ FreeBSD ªº°Ó·~½Òµ{°V½m¤Î§Þ³N¤ä´©¡C
 	    ¸Ô±¡½Ð¨ì <ulink url="http://www.bsdmall.com/">BSD Mall</ulink> 
 	    ¹î¬Ý¡AÁÂÁ¡C</para>
 
           <para>FreeBSD Mall ¦³´£¨Ñ°Ó·~¤Æªº BSD §Þ³N¤ä´©¡A
             ¸Ô±¡½Ð¨ì <ulink
             url="http://www.freebsdmall.com/">FreeBSD Mall</ulink> ¹î¬Ý¡AÁÂÁ¡C</para>
 
 
 	  <para>¨ä¥L¥ô¦ó¦³´£¨Ñ½Òµ{°V½m¤Î§Þ³N¤ä´©ªº²Õ´¡B³æ¦ì¡A­Y¤]·Q¦Cªí©ó¦¹ªº¸Ü¡A
 	    ½Ð»P &a.doc; Ápµ¸¡AÁÂÁ¡C</para>
 	</answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter
     id="install">
     <chapterinfo>
       <author>
 	<firstname>Nik</firstname>
 	<surname>Clayton</surname>
 	<affiliation>
 	  <address><email>nik@FreeBSD.org</email></address>
 	</affiliation>
       </author>
     </chapterinfo>
     
     <title>¦w¸Ë</title>
 
     <qandaset>
       <qandaentry>
         <question id="floppy-download">
           <para>­Y­n¥Î³nºÐ¤ù¶}¾÷¨Ó¦w¸Ë FreeBSD ªº¸Ü¡A­n¤U¸ü­þ¨ÇÀɮשO¡H</para>
         </question>
 
         <answer>
           <para>&os; 4.X ªº¸Ü¡A»Ý­n¨â­Ó image ÀÉ¡G
             <filename>floppies/kernel.flp</filename> ¤Î
             <filename>floppies/mfsroot.flp</filename>¡Cimage ÀÉ¥²¶·¥Î¤u¨ã¹³¬O 
 	    <command>fdimage</command> ©Î &man.dd.1; ¨Ó¶Ç°e¨ìºÏ¤ù¤W¡C
             ­Y¬O¦b &os; 5.3 (¤Î¤§«áª©¥»)¦³­«·s³W¹º¶}¾÷¤ù¬[ºc¡A©Ò¥H­n§ìªº¬O
             <filename>floppies/boot.flp</filename> ¥H¤Î <filename>floppies/kern<replaceable>X</replaceable></filename> 
             ÀÉ®×(¥Ø«e X ¬° 1 ¸ò 2 ¨â­Ó¡A¥[¤W <filename>floppies/boot.flp</filename>¡AÁ`¦@¬O 3 ­ÓÀÉ®×)¡C</para>
 
           <para>­Y·Q¦Û¤v¤U¸ü distributions ªº¸Ü(¤ñ¦p¥H &ms-dos; Àɮרt²Î®æ¦¡¦w¸Ë)¡A
             ¥H¤U¬O«Øij­n§ìªº distributions ¡G</para>
 
 
           <itemizedlist>
             <listitem>
               <para>base/ (4.X ª©¥»«h¬° bin/)</para>
             </listitem>
 
             <listitem>
               <para>manpages/</para>
             </listitem>
 
             <listitem>
               <para>compat*/</para>
             </listitem>
 
             <listitem>
               <para>doc/</para>
             </listitem>
 
             <listitem>
               <para>src/ssys.*</para>
             </listitem>
           </itemizedlist>
 
 
           <para>§¹¾ã¦w¸Ë¨BÆJ¥H¤Î¤j³¡¤Àªº¦w¸Ë°ÝÃD¡A½Ð°Ñ¾\ FreeBSD ¨Ï¥Î¤â¥Uªº
             <ulink url="&url.books.handbook;/install.html">¦w¸Ë FreeBSD</ulink> ³¹¸`</para>
 
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="floppy-image-too-large">
           <para>­YºÏ¤ù¸Ë¤£¤U image Àɪº¸Ü¡A¸Ó«ç»ò¿ì©O¡H</para>
         </question>
 
         <answer>
           <para>¤@±i 3.5 ­^¦T(1.44MB) ªººÏºÐ¤ù¬O¥i¥H¸Ë¤W 1474560 bytes ªº¸ê®Æ
             ¡A¦Ó¶}¾÷¤ùªº image Àɮפj¤p¹ê»Ú¤W¤]¬O 1474560 bytes¡C</para>
 
           <para>¦b»s§@¶}¾÷¤ù®É¡A±`¨£¿ù»~¦³¡G</para>
 
           <itemizedlist>
             <listitem>
               <para>¨Ï¥Î <acronym>FTP</acronym> ¨Ó¤U¸üÀɮ׮ɡA
 	        ¥¼¿ï¾Ü <emphasis>binary</emphasis> ¶Ç¿é¼Ò¦¡¨Ó¤U¸ü¡C</para>
 
 
               <para>¦³¨Ç FTP clientºÝµ{¦¡¡A¬O¹w³]±N¶Ç¿é¼Ò¦¡³]©w¬°
                 <emphasis>ascii</emphasis> ¼Ò¦¡¡A¦Ó¥B·|­×§ï±µ¦¬¨ìªºÀɮצæ§À¦r¦ê¬° client ºÝªº§@·~¨t²Î¤è¦¡
 		¡A¤ñ¦p newline(&unix;®æ¦¡) ¨ì¤F§@·~¨t²Î¬° &windows; ªº client ºÝ·|³Q§ï¬° CR-LF(&ms-dos;®æ¦¡)¡A
 		³o·|¨Ï±o image ÀÉ¥»¨­¾D¨ì­×§ï¦ÓµLªk¥¿±`¨Ï¥Î¡C¦]¦¹¡A¦pªG¤U¸üªº image 
 	        Àɮפj¤p­Y»P FTP ¥D¾÷¤W­±ªºÀɮסy<emphasis>¤£¤@­P</emphasis>¡z
 	        ªº¸Ü¡A½Ð­«·s¨Ï¥Î binary ¶Ç¿é¼Ò¦¡¤U¸ü§Y¥i¡C</para>
 
               <para>FTP «ü¥O: ¶i¤J FTP ¤§«á¡A¥´ <emphasis>binary</emphasis>
 	        «ü¥O¡A§Y¥i¤Á´«¨ì binary ¶Ç¿é¼Ò¦¡¡AµM«á¦A¤U¸ü¬ÛÃö image ÀɮסC</para>
             </listitem>
 
             <listitem>
               <para>ª½±µ¥Î &ms-dos; ªº <command>copy</command> «ü¥O(©ÎÃþ¦ü
                 ªº GUI µ{¦¡¡B©Î¬Oµøµ¡¤Wª½±µ½Æ»s)¨Ó½Æ»s¶}¾÷¥Îªº image ÀɨìºÏ¤ù¤W¡C
                 </para>
 
               <para>¤£¥i¥H¥Î¹³¬O <command>copy</command> ³oÃþµ{¦¡ª½±µ±N image
 	        Àɽƻs¨ìºÏ¤ù¤W¡A¦]¬° image ÀÉ¥»¨­¥]§t¤F§¹¾ãªººÏ­y¸ê®Æ¡A©Ò¥H¤£¯à³æ¯Â¥Î½Æ»s¤è¦¡¡A
 	        ¦Ó¥²¶·¨Ï¥Î§C¶¥¤u¨ãµ{¦¡(¹³¬O <command>fdimage</command> ©Î <command>rawrite</command>)¡A
 	        ¥H <quote>raw</quote> ¤è¦¡¶Ç°e¨ìºÏ¤ù¤W¡C(³o³¡¤À¥i°Ñ¾\ FreeBSD ¨Ï¥Î¤â¥U¤Wªº <ulink
 	        url="&url.books.handbook;/install.html">¦w¸Ë FreeBSD</ulink>)</para>
             </listitem>
           </itemizedlist>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="install-instructions-location">
           <para>¥i¥H¦b­þÃä§ä¨ì¦w¸Ë FreeBSD ªº¸Ñ»¡¨BÆJ©O¡H</para>
         </question>
 
         <answer>
           <para>¦w¸Ë¨BÆJªº¸Ñ»¡¡A½Ð°Ñ¾\ FreeBSD ¨Ï¥Î¤â¥U¤Wªº
             <ulink url="&url.books.handbook;/install.html">¦w¸Ë FreeBSD</ulink> ³¹¸`³¡¤À¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="need-to-run">
           <para>­n¶] FreeBSD »Ý­n¤°»òªº°t³Æ©O¡H</para>
         </question>
 
         <answer>
           <para>&os; 4.X ¤§«eªºª©¥»¡AµwÅé»Ý¨D¬° 386 ©Î§ó°ª¯Åªº PC
             ¡A°O¾ÐÅé(RAM)¦Ü¤Ö­n 5 MB ©Î§ó¦h¡AµwºÐªÅ¶¡¦Ü¤Ö­n 60 MB ©Î§ó¦h¡C
             ¤£¹L¡A&os; ¡y¨t²Î¦w¸Ëµ{¦¡¡zªº°O¾ÐÅé(RAM)»Ý¨D¬°¦Ü¤Ö 16 MB¡C</para>
 
 	  <para>±q &os; 5.X °_¡AµwÅé»Ý¨D¬° 486 ©Î§ó°ª¯Åªº PC
 	    ¡A°O¾ÐÅé(RAM)¦Ü¤Ö­n 24 MB ©Î§ó¦h¡AµwºÐªÅ¶¡¦Ü¤Ö­n 150 MB ©Î§ó¦h¡C
             </para>
 
 	  <para>&os; ªº©Ò¦³ª©¥»³£¥i¥H¥u¥Î§C¶¥ªº MDA ³W®æÅã¥Ü¥d¡A¤£¹L...­n¶] X11R6 µøµ¡ªº¸Ü¡A
 	    ÁÙ¬O¦Ü¤Ö¥Î VGA ©Î§ó¦n³W®æªºÅã¥Ü¥d¨Ó¥Î§a¡C</para>
 
           <para>³o³¡¤À¤]¥i°Ñ¾\ <xref linkend="hardware">¡C</para>
 
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="four-meg-ram-install">
           <para>§Ú¹q¸£ RAM ¥u¦³ 4MB ¦Ó¤w¡A¥i¥H¸Ë FreeBSD ¶Ü¡H</para>
         </question>
 
         <answer>
           <para>¦w¸Ë &os; 4.X ªº°O¾ÐÅé»Ý¨D¬°¦Ü¤Ö 5 MB ¡A¦Ó
             ¦w¸Ë &os; 5.X (§t¤§«áª©¥») «h¬O¦Ü¤Ö­n 8 MB ¡C</para>
 
           <para>¦b 5.X ¤§«eªº©Ò¦³ &os; ª©¥»¡A³£¥i¥H¥u¥Î 4 MB ªº°O¾ÐÅé¨Ó
 	    <emphasis>¡y¹B§@¡z</emphasis>¡A¤£¹L¡A«e­±¨º¸`§Ú­Ì»¡¹L¤F¡y¨t²Î¦w¸Ëµ{¦¡¡zªº¸Ü¡A
 	    «hµLªk¥u¥Î 4 MB ªº°O¾ÐÅé¨Ó°õ¦æ¡C¦]¦¹¡A§A¥i¥H¥ý¦b¡y¨t²Î¦w¸Ëµ{¦¡¡z³o¨BÆJ¤§«e¡A
 	    ¥ý±N°O¾ÐÅé¥[¨ì 16 MB ¥H¤W¡A¦w¸Ë§¹ FreeBSD ¤§«á¡A´N¥i¥H§â¦h¾lªº°O¾ÐÅ鮳¤U¨Ó¡C
 	    ©ÎªÌ¬O¡A¥ý§â­n¦w¸ËªºµwºÐ®³¨ì¦³¨¬°÷°O¾ÐÅ骺¾÷¾¹¤W¥ý¸Ë¦n¡A
 	    µM«á¦A§âµwºÐ©ñ¦^­ì¾÷¾¹¡C</para>
 
           <para>¦¹¥~¡A¥u¥Î 4 MB ªº°O¾ÐÅé¨Ó¹B§@ªº¸Ü¡A¥²¶·­n¦Û»s kernel(®³±¼¤£¥²­nªº¥H¤ÎÄ묹¤@¨ÇªF¦è)¡C
 	    ¤]¦³¤H¦¨¥\¥u¥Î 2 MB ªº°O¾ÐÅé¥H &os; ¶}¾÷(ÁöµM³o¼Ëªº¨t²Î´X¥Gµ¥©ó¼o¤F..)</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="custom-boot-floppy">
           <para>­n«ç¼Ë¤~¯à¦Û¦æ¥´³y±M¥Îªº¶}¾÷¡B¦w¸ËºÏ¤ù©O¡H</para>
         </question>
 
         <answer>
 	  <para>¥Ø«e¡AÁÙ¨S¦³¿ìªk<emphasis>¡y¥u¡z</emphasis>¦Û»s±M¥Îªº¶}¾÷¡B¦w¸ËºÏ¤ù¡C
             ¥²¶·³z¹L¦Û¦æ¥´³y§¹¾ã§@·~¨t²Îªº release(µo¦æ)¡A³o¼Ë¸Ì­±¤~·|¥]¬A¦Û¤vªº¶}¾÷¡B¦w¸ËºÏ¤ù¡C</para>
 
           <para>­Y·Q¦Û¦æ¥´³y¡Bµo¦æ(release)¤@­Ó§¹¾ãªº§@·~¨t²Î¡A½Ð°Ñ¾\³o½g
             <ulink url="&url.articles.releng;/article.html">Release Engineering</ulink> ¤å³¹¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="multiboot">
           <para>§Ú¹q¸£¤W¥i¥H¦³¦h­«§@·~¨t²Î¶Ü¡H</para>
         </question>
 
         <answer>
           <para>¥i¥H§r¡A½Ð°Ñ¾\
             <ulink url="&url.articles.multi-os;/index.html">
             ¦h­«§@·~¨t²Î</ulink> ³o½g¤å³¹¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="windows-coexist">
           <para>&windows; ¥i¥H»P FreeBSD ¦@¦s©ó¹q¸£¤W¶Ü¡H</para>
         </question>
 
         <answer>
           <para>¥ý¸Ë &windows; ¦A¸Ë FreeBSD¡C
             ¨º»ò FreeBSD ¦h­«¶}¾÷ºÞ²z­û(boot manager)´N·|¥X²{¿ï³æÅý§A¿ï¾Ü­n¥H &windows; ©Î
             FreeBSD ¨Ó¶}¾÷¡C¤£¹L¡A­Y§A¬O¥ý¸Ë FreeBSD ¦A¸Ë &windows; ªº¸Ü¡A
 	    ¨º»ò  &windows; ±N·|¤£°Ý¥ý®_¡A§â  FreeBSD ªº¦h­«¶}¾÷ºÞ²z­û(boot manager)»\±¼¡A
 	    ·í§A¹J¤W³oºØ±¡ªp®É¡A½Ð°Ñ¦Ò¤U¤@¸`»¡©ú¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="win95-damaged-boot-manager">
           <para>¶ã.. &windows; §â§Úªº¦h­«¶}¾÷ºÞ²z­û(boot manager)®³±¼¤F¡I­n«ç»ò±Ï¦^¨Ó©O¡H</para>
         </question>
 
         <answer>
           <para>¥i¥H¥Î¥H¤U¤TºØ¤è¦¡¤§¤@¡A¨Ó±Ï¦^§Aªº FreeBSD ¦h­«¶}¾÷ºÞ²z­û(boot manager)¡G</para>
 
           <itemizedlist>
             <listitem>
               <para>¥i¥H±q¦U FreeBSD FTP ¯¸ªº <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">/pub/FreeBSD/tools/</ulink>
 	         §ä¨ì <filename>bootinst.exe</filename> ¤Î <filename>boot.bin</filename> ³o¨â­ÓÀÉ¡A
 		 ¥H binary ¶Ç¿é¼Ò¦¡¤U¸ü«á¡A½Æ»s¨ìºÏ¤ù¤W¡A¦A¥Î DOS ¶}¾÷¤ù¶}¾÷¡A
                 ±µµÛ¥´Ãþ¦ü¤U­±ªº«ü¥O¡G</para>
 
               <screen><prompt>&gt;</prompt> <userinput>bootinst.exe boot.bin</userinput></screen>
 
               <para>³o¼Ë¡A¦h­«¶}¾÷ºÞ²z­û(boot manager)´N·|­«¸Ë§¹²¦¤F¡C</para>
             </listitem>
 
             <listitem>
               <para>¥Î FreeBSD ¶}¾÷¤ù¶}¾÷¡AµM«á¿ï³æ¨ºÃä¿ï Custom installation(¦Û­q¦w¸Ë)¡A
 	         ¦A¿ï Partition¡A±µµÛ¿ï¾Ü§A­n¸Ë¦h­«¶}¾÷ºÞ²z­û(boot manager)ªºµwºÐ(³q±`¬O²Ä¤@Áû)¡A
 		 µM«á·|¥X²{ partition editor ªºµe­±¡A³o®É½Ð¤£­n°µ¥ô¦ó­×§ï¡Aª½±µ«ö W Àx¦s¡A
 	         ³o®Éµ{¦¡´N·|°Ý¬O§_­n½T©w Write ¡A³Ì«á¥X²{ Boot Manager ¿ï¾Üµe­±¡A
 	         °O±o­n¿ï <quote>Boot Manager</quote> ¡A³o¼Ë´N·|­«·s±N¦h­«¶}¾÷ºÞ²z­û(boot manager)
 	         ¦w¸Ë¨ìµwºÐ¤W¡C²{¦b¡A´N¤j¥\§i¦¨¥i¥HÂ÷¶}¦w¸Ë¿ï³æ¨Ã­«¶}¾÷¤F¡C</para>
             </listitem>
 
             <listitem>
               <para>¥Î FreeBSD ¶}¾÷¤ù©Î¬O¶}¾÷¥úºÐ¶}¾÷¡AµM«á¿ï³æ¨ºÃä¿ï <quote>Fixit</quote>
                 ¡A©Î¬O¥H Fixit ¶}¾÷¤ù©Î¬O¥úºÐ¦w¸Ëªº²Ä¤G¤ù(¿ï¾Ü <quote>live</quote> filesystem
                 ¿ï¶µ)µM«á´N·|¶i¤J fixit shell ¤F¡A±µµÛ¥´¤U¦C«ü¥O¡G</para>
 
               <screen><prompt>Fixit#</prompt> <userinput>fdisk -B -b /boot/boot0 <replaceable>bootdevice</replaceable></userinput></screen>
 
               <para>½Ð±N¤W­±ªº <replaceable>bootdevice</replaceable> ­×§ï¬°±z¹ê»Úªº¶}¾÷µwºÐ¥N¸¹
                 ¤ñ¦p <devicename>ad0</devicename> (²Ä¤@Áû IDE µwºÐ)
                 ¡A©Î¬O<devicename>ad4</devicename> (first IDE disk on
                 auxiliary controller), <devicename>da0</devicename> (²Ä¤@Áû
                 SCSI µwºÐ)µ¥µ¥¡C</para>
             </listitem>
           </itemizedlist>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="boot-on-thinkpad">
           <para>IBM Thinkpad A¨t¦C¡BT¨t¦C©Î X¨t¦Cªºµ§°O«¬¹q¸£¸Ë§¹ FreeBSD ¤§«á­«¶}¾÷¡A´N·í¤F¡A¸Ó«ç»ò¿ì©O¡H</para>
         </question>
 
         <answer>
           <para>(¥»°ÝÃD¥D­n¬Oµo¥Í¦b 2000 ~ 2001 ¥|¤ë¶¡®É)³o¨Ç IBM ¾÷¾¹¤Wªº BIOS ¦­´Áª©¥»¦³­Ó¯äÂÎ(bug)·|§â
 	    FreeBSD ¤À³Î°Ï»~»{¬°¬O FAT ®æ¦¡¤À³Î°Ï¡AµM«á·í BIOS ¸ÕµÛ°»´ú FreeBSD ¤À³Î°Ï®É¡A´N·|·í¤F¡C</para>
 
           <para>®Ú¾Ú IBM ¤è­±ªº»¡ªk<footnote><para>¤@«Ê¨Ó¦Û Keith
                 Frechette ªº e-mail <email>kfrechet@us.ibm.com</email>¡C</para></footnote>
 	    ¡A¥H¤U«¬¸¹/BIOSª©¥»ªº¾÷ºØ¡A¤w¸g³£¦³­×¥¿¡G</para>
 
           <informaltable frame="none" pgwide="1">
             <tgroup cols="2">
               <thead>
                 <row>
                   <entry>«¬¸¹</entry>
                   <entry>BIOS ª©¥»</entry>
                 </row>
               </thead>
 
               <tbody>
                 <row>
                   <entry>T20</entry>
                   <entry>IYET49WW(§t¤§«á)</entry>
                 </row>
 
                 <row>
                   <entry>T21</entry>
                   <entry>KZET22WW(§t¤§«á)</entry>
                 </row>
 
                 <row>
                   <entry>A20p</entry>
                   <entry>IVET62WW(§t¤§«á)</entry>
                 </row>
 
                 <row>
                   <entry>A20m</entry>
                   <entry>IWET54WW(§t¤§«á)</entry>
                 </row>
 
                 <row>
                   <entry>A21p</entry>
                   <entry>KYET27WW(§t¤§«á)</entry>
                 </row>
 
                 <row>
                   <entry>A21m</entry>
                   <entry>KXET24WW(§t¤§«á)</entry>
                 </row>
 
                 <row>
                   <entry>A21e</entry>
                   <entry>KUET30WW</entry>
                 </row>
               </tbody>
             </tgroup>
           </informaltable>
 
 	  <para>³o¨Ç«á´Áªº IBM BIOS ­×­qª©¤j¦h¤w¸g­×¥¿¦¹¤@¯äÂΡCJacques Vidrine ¼gµ¹ &a.mobile; ªº
 	    <ulink url="http://docs.FreeBSD.org/cgi/mid.cgi?20010427133759.A71732">³o«Ê«H
 	    </ulink> ¤W­±»¡©ú¤F­Y§A·sªº IBM µ§°O«¬¹q¸£µLªk¶¶§Q¥H FreeBSD ¶}¾÷ªº¸Ñªk¨BÆJ
 	    (°²³]¥i¥H¤É¯Å©Î­°¯Å BIOS ª©¥»ªº¸Ü)¡C
 	
           <para>¦pªG¾÷¾¹¥Îªº¬O¸û¥j¦­ª©¥»ªº BIOS¡A¦Ó¥B¤£¾A¦X§ó·s BIOS ªº¸Ü¡A¨º»ò¥H¤U§Ú­Ì·|¤¶²Ð¼È®É¸Ñªk¡A
 	    ±Ð§A¦p¦ó­×§ï FreeBSD ¤À³Î°Ï©Ò¨Ï¥Îªº ID ¡A¨Ã¦w¸Ë¬ÛÃö­×¸Éµ{¦¡¡C</para>
 
           <para>First, you will need to restore the machine to a state where
             it can get through its self-test screen.  Doing this requires
             powering up the machine without letting it find a FreeBSD
             partition on its primary disk.  One way is to remove the hard disk
             and temporarily move it to an older ThinkPad (such as a ThinkPad
             600) or a desktop PC with an appropriate conversion cable.  Once
             it is there, you can delete the FreeBSD partition and move the hard
             disk back.  The ThinkPad should now be in a bootable state
             again.</para>
 
           <para>With the machine functional again, you can use the workaround
             procedure described here to get a working FreeBSD
             installation.</para>
 
           <procedure>
             <step>
               <para>±q <ulink url="http://people.FreeBSD.org/~bmah/ThinkPad/"></ulink>
 	        ¨Ó¤U¸ü <filename>boot1</filename> ¤Î <filename>boot2</filename> ³o¨â­ÓÀÉ¡C
                 §â³o¨â­ÓÀɮשñ¦bºÏ¤ù¡B¥úºÐ©Î¨ä¥LµwºÐ¤W¡C</para>
             </step>
 
             <step>
               <para>¥H¤@¯ë¦w¸Ë FreeBSD ¸Ë¨ì ThinkPad ¤W¡A°O±o
                 <emphasis>¡y¤£­n¥Î¡z</emphasis> <literal>Dangerously
                   Dedicated</literal> ¼Ò¦¡¡C  ¦¹¥~¡A<emphasis>¡y¤£­n¡z</emphasis>
                 ¦b§¹¦¨¦w¸Ë¤§«á´N­«¶}¾÷¡C</para>
             </step>
 
             <step>
               <para>¶i¤J shell¡G(«ö <keycombo action="simul"><keycap>ALT</keycap><keycap>F4</keycap></keycombo>)
 	        ¤Á´«¨ì<quote>Emergency Holographic Shell</quote> ©Î¬O¿ï³æ¤W­±¿ï¾Ü
                 <quote>fixit</quote> shell¡C</para>
             </step>
 
             <step>
               <para>¥Î &man.fdisk.8; §â FreeBSD ¤À³Î°Ï ID ¥Ñ <literal>165</literal> §ï¬°
 	        <literal>166</literal>(OpenBSD©Ò¨Ï¥ÎªºID)¡C</para>
             </step>
 
             <step>
               <para>§â­è­è´£ªº <filename>boot1</filename> ¸ò
                 <filename>boot2</filename> ³o¨â­ÓÀɮשñ¨ì¥Ø«eªºµwºÐÀɮרt²Î¤W¡C</para>
             </step>
 
             <step>
               <para>¥H &man.disklabel.8; §â <filename>boot1</filename> ¤Î
                 <filename>boot2</filename> ¦s¨ì§Aªº FreeBSD slice ¤W­±¡C</para>
 
               <screen>&prompt.root; <userinput>disklabel -B -b boot1 -s boot2 ad0s<replaceable>n</replaceable></userinput></screen>
 
               <para><replaceable>¡un¡v</replaceable> ¬O§A¸Ë FreeBSD ªº slice¡A
 	        ½Ð±N <replaceable>¡un¡v</replaceable> §ï¬°²Å¦X§A¨t²Î²{ªpªº slice¡C</para>
             </step>
 
             <step>
               <para>­«¶}¾÷¡A¦b boot prompt ·|¬Ý¨ì¦³ <literal>OpenBSD</literal> ªº¿ï¶µ¡A
 	        ¿ï¥¦¡A³o¼Ë´N·|¥H FreeBSD ¶}¾÷¡C</para>
             </step>
           </procedure>
 
           <para>¥t¥~¡A¦Ü©ó¦p¦óÅý OpenBSD ¤Î FreeBSD ¨Ã¦s¦b¦P¤@¥x IBM ThinkPad ¤W...
 	    ³o­Ó°ÝÃD´N¥æµ¹¦U¦ì¬Ý­¾­Ì¥h¹Á¸Õ¤F :p</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="install-bad-blocks">
           <para>¦³Ãa­yªºµwºÐ¥i¥H®³¨Ó¸Ë FreeBSD ¹À¡H</para>
         </question>
 
         <answer>
           <para>(¦pªG«Ü°í«ùªº¸Ü)¤]¬O¥i¥H¡A¤£¹L³o·QªkÅãµM¤£¤Ó©ú´¼¡C:(</para>
 
 	  <para>¦pªG¦b¤@¯ë¸û·sªº IDE µwºÐ¤W¬Ý¨ì¦³Ãa­y¡A«Ü¦³¥i¯à¥Nªí¡G³oÁûµwºÐ§Y±N±¾ÂI¤F¡C
 	    (¦]¬°¥Ø«e©Ò¦³¸û·sªº IDE µwºÐ¡A¤º³¡³£¦³¦Û°Ê remapping Ãa­yªº¯à¤O¡C
 	    ¦pªG¬Ý¨ì¦³Ãa­y¡A«hªí¥Ü¥¦¤º³¡¦Û°Ê remapping ¥\¯à¥¢®Ä¡AµLªk³B²zÃa­y¡A
 	    ¤]´N¬O»¡³oÁûµwºÐ¤w¸g¬OÄY­«·lÃaµ{«×¤F¡C)§Ú­Ì«Øij¶RÁû·sµwºÐ¤ñ¸û°®¯Ü¨Ç­ò¡C</para>
 
           <para>¦pªG¬O SCSI µwºÐ¦³Ãa­yªº¸Ü¡A½Ð¸ÕµÛ°Ñ¦Ò³o­Ó
             <link linkend="awre">¸Ñªk</link>¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="boot-floppy-strangeness">
           <para>¥Î¦w¸ËºÏ¤ù¶}¾÷®É¡A«o¦³¨Ç©Ç²{¶Hµo¥Í¡I³o¬O¤°»ò±¡ªp©O¡H</para>
         </question>
 
         <answer>
           <para>­Y¬Ý¨ì¤@¨Ç©Ç²§²{¶H¡A¹³¬O¶}¾÷¤ù¶}¾÷¶}¨ì¤@¥b´N·í¤F¡AºÏºÐ¾÷§¹¥þ¨S¥ô¦ó°Ê§@¡B
 	    ©Î¬O¤£Â_¤ÏÂЭ«¶}¾÷¡A½Ð¥ýÀˬd¥H¤U´X­Ó½u¯Á¡G</para>
 
           <orderedlist>
             <listitem>
               <para>½Ð½T©w¬O§_¬°¥þ·s¡B¨S¦³ºÏ­y¿ù»~ªººÏ¤ù¡H
 	        (³Ì¦n¨Ï¥Î·s¶Rªº¡A¦Ó«DÂø»x¡B®Ñ¥»ªþÃتº¡A¬Æ¦ÜÁÙ©ñ¦b§É©³¤U¤T¦~¤F...=_="")</para>
             </listitem>
 
             <listitem>
               <para>½Ð½T©w¬O§_¦³¥Î binary(©Îimage)¶Ç¿é¼Ò¦¡¨Ó¤U¸ü image ÀÉ¡H
 	        (¤£¥Îı±o¤£¦n·N«ä¡A§Y¨Ï¬O§Ú­Ì¤]´¿·N¥~¥H ASCII ¶Ç¿é¼Ò¦¡¨Ó¤U¸ü binary ÀɮסI)</para>
             </listitem>
 
             <listitem>
               <para>­Y§A¬O &windows; 95/98/ME/NT/2000/XP/2003 ¨Ó¤U¸ü¡B»s§@¶}¾÷ºÏ¤ùªº¸Ü¡A
 	        ½Ð½T©w¬O§_¦³¦b DOS ¼Ò¦¡¨Ï¥Î <command>fdimage</command> ©Î
                 <command>rawrite</command> ³o¨â­Ó¤u¨ãµ{¦¡¡H­èÁ¿ªº³o¨Ç§@·~¨t²Î¡A
 	        ³£·|¼vÅTµ{¦¡¥hª½±µ¼g¤JµwÅé¡A¹³¬O»s§@¶}¾÷¤ù¤§Ãþªº°Ê§@¡C
 	        ¦³®É­Ô¡A¦b GUI ¤¶­±¤Wªº DOS shell ¤]¥i¯à·|µo¥Í³o¼Ëªº°ÝÃD¡C
                 </para>
             </listitem>
           </orderedlist>
 
           <para>¦¹¥~¡Aª½±µ³z¹L &netscape; ÂsÄý¾¹¤U¸ü image Àɪº¸Ü¡A¤]¦³Ãþ¦ü²{¶H¡C
 	    ©Ò¥H¡A¦pªG¥i¥Hªº¸Ü¡A½Ð§ï¥Î¨ä¥L¥i¥H½Õ¾ã³]©wªº FTP clientºÝµ{¦¡¨Ó¶i¦æ¤U¸ü¡C
 	    (·íµM¡A­n°O±o½Õ binary ¶Ç¿é¼Ò¦¡)</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="no-install-cdrom">
           <para>¥Î¥úºÐ¶}¾÷¤ù¨Ó¦w¸Ë¡A¦ý¥úºÐ¶}¾÷«á¡A¦w¸Ëµ{¦¡»¡§ä¤£¨ì¥úºÐ...³o¬O«ç»ò¤F¡H</para>
         </question>
 
         <answer>
 	  <para>³q±`°ÝÃD¦b©ó¥úºÐ¾÷³]©w¿ù»~¡C¥Ø«e«Ü¦h¹q¸£ªº¥X¼t¼Ð·Ç°t³Æ³£¦³¥úºÐ¾÷¡A¨Ã¥B
 	    ·|¹w¥ý³]©w¬° IDE ³q¹D¤W­± Secondary ªº Slave ³]³Æ¡A¦Ó Secondary ¤W­±ªº
 	    «o¨S¦³ Master ³]³Æ¡C¥H ATAPI ªº³W®æ¦Ó¨¥¡A³o¬O¿ù»~ªº³]©w¡AµM¦Ó &windows; ªº§@ªk
 	    ¬O¤£²z·|³o¨Ç³W®æ¤Wªº³]©w°ÝÃD¡A¦Ó¥B¶}¾÷®É BIOS °»´ú¤]·|²¤¹L³oÂI¡C
 	    ³o¤]´N¬O¬°¤°»ò BIOS ¥i¥H¬Ý¨ì¥úºÐ¡A¨Ã¥B¥i¥Î¥úºÐ¶}¾÷¡A¦ý FreeBSD 
 	    µLªk¥¿±`§ì¨ì¥úºÐ¥H¶¶§Q¶i¦æ¦w¸Ë¡C</para>
 
           <para>¸Ñªk¡G­«·s³]©w¨t²Î¡AÅý¥úºÐ¦¨¬°¥¦©Ò³s±µ¨º±ø IDE ³q¹Dªº Master¡A
 	    ©ÎªÌ¥u¦³¤@±ø IDE ³q¹Dªº¸Ü¡A¨º´NÅý¥úºÐ¾÷¦¨¬° Slave
 	    ¡A·íµM¸Ó IDE ³q¹D¤W¦Ü¤Ö­n¦³ Master ³]³Æ¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="install-PLIP">
           <para>§Ú¥i¥H¥Î PLIP(Parallel Line IP)¤è¦¡¨Ó¦w¸Ë FreeBSD ¨ìµ§°O«¬¹q¸£¤W¶Ü¡H</para>
         </question>
 
         <answer>
           <para>¥i¥H¡A¥Î¤@±ø´¶³qªº Laplink ½u´N¥i¥HÅo¡C­Y¦³³o¤è­±»Ý¨Dªº¸Ü¡A½Ð°Ñ¾\ FreeBSD ¨Ï¥Î¤â¥U¤¤ªº
             <ulink url="&url.books.handbook;/network-plip.html">PLIP
             ³¹¸`</ulink> ªº²Ó³¡³]©w</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="geometry">
           <para>¸Ó¥Î­þ¤@ºØµwºÐ³]©w°Ñ¼Æ(geometry)©O¡H</para>
         </question>
 
         <answer>
             <note>
               <para>³o¸Ìªº¡yµwºÐ³]©w°Ñ¼Æ(geometry)¡z¡A«üªº¬OµwºÐ¤Wªº
               ¡ucylinders¡v¡B¡uheads¡v¡B¡usectors/track¡v ³o¤T­Ó³]©w°Ñ¼Æ¡C
 	      ±µ¤U¨Óªº¤å³¹¤º¡A¬°¤F¤è«K¤¶²Ð¡A±N²ºÙ¬°¡yC/H/S¡z¡C
 	      ³o¨Ç³]©w°Ñ¼Æ¬OÅý PC ¤Wªº BIOS ¯à¶¶§Q¦a¥¿±`§P§OµwºÐ¡A
 	      »PµwºÐ¥»¨­Åª¼gªº­«­n¦]¯À¡C</para>
             </note>
 
           <para>¹ï­è±µ¤âªº¨t²ÎºÞ²zªÌ·s¤â¦Ó¨¥¡A³o¨Ç³]©w°Ñ¼Æ±`³y¦¨¤@¨Ç§xÂZ¡C
 	    ­º¥ý¡ASCSI µwºÐ¤Wªº <emphasis>physical</emphasis> geometry
 	    ¸ò FreeBSD ¤Wªº disk blocks ¬O§¹¥þµLÃöªº¡C¨Æ¹ê¤W¡A
 	    ´NµwºÐ¤WºÏ°Ï±K«×ªºÅܤƦӨ¥¡A¨Ã¨S¦³©Ò¿×¡yphysical geometry¡z³oºØªF¦è¡C
 	    µwºÐ»s³y°Ó©Ò»¡ªº¡yphysical geometry¡z³q±`¬O«ü¡G
 	    µwºÐ¤W©Ò¨Ï¥Î³Ì¤pªÅ¶¡¨Ó¦s©ñ¸ê®Æªº³]©w°Ñ¼Æ(geometry)¡C
 	    ¥H IDE µwºÐ¦Ó¨¥¡AFreeBSD ¥Î¥H¦s¨úµwºÐ³]©wªº¤è¦¡¬O C/H/S ¡A
 	    µM¦Ó¡A¥Ø«e¥«­±¤WªºµwºÐ¦­´N¦b¤º³¡¹B§@®É¡A´N¦Û°ÊÂà´«¬° block ¤è¦¡
 	    ¤F¡C</para>
 
           <para>¯u¥¿ÃöÁ䪺¦a¤è¡A¨ä¹ê¬O¦b©ó ¡y<emphasis>logical</emphasis>
             geometry¡z¡X ³o¬O BIOS °»´úµwºÐ®É©Ò±o¨ìªº³]©w¡A¨Ã¥B¥Î¨Ó¨M©wµwºÐ¦s¨ú¤è¦¡¡C
             ¥Ñ©ó FreeBSD ¬O±Ä¥Î BIOS ªº°»´ú³]©w­È¡A©Ò¥H¦p¦ó¨ÓÅý BIOS °»´ú¨ìªº³]©w­È«O«ù¥¿½T¡A
 	    ¬O¤Q¤À­«­n¡C¤×¨ä¬O¦P¤@ÁûµwºÐ¤W¦³¦h­Ó§@·~¨t²Îªº±¡ªp¡A
 	    ¥¦­Ì³£¥²¶·±Ä¥Î¤@­PªºµwºÐ³]©w°Ñ¼Æ(geometry)¡A
 	    §_«h´N·|¦³¶}¾÷¶i¤£¥h§@·~¨t²ÎªºÄY­«°ÝÃD¤F¡C</para>
 
           <para>¥H SCSI µwºÐ¦Ó¨¥¡AµwºÐ³]©w°Ñ¼Æ(geometry)¬O¥Ñ SCSI ¥d¤Wªº
 	   extended translation(³q±`«üªº¬O¦³¼Ð¥Ü <quote>support &gt;1GB</quote>(¤ä´© 1GB ¥H¤W®e¶q¡A©ÎÃþ¦ü¦Wµü)
 	   ¤ä´©»P§_¨Ó§@¨M©w¡C
            ¦pªG¤£¤ä´©¡A¨º»ò´N·|±Ä¥Î <replaceable>N</replaceable> cylinders¡B
 	   64 heads¡B 32 sectors/track §@¬°µwºÐ³]©w°Ñ¼Æ(geometry)¡A³o¸ÌÁ¿ªº¡y<replaceable>N</replaceable>¡z
 	   ¬O«üµwºÐªº®e¶q(³æ¦ì¡GMB)¡CÁ|­Ó¨Ò¤l¨Ó»¡¡A¤@Áû 2GB µwºÐÀ³¸Ó¬O 
 	   2048 cylinders¡B64 heads¡B32 sectors/track¡C</para>
 
           <para>¦pªG¸Ó SCSI ¦³¤ä´©¨Ï¥Î extended translation ªº¸Ü¡A
 	    (³q±`³o­Ó¤è¦¡¦b &ms-dos; ¨Ï¥Î¤W¦³¬Y¨Ç­­¨î)¡A¨Ã¥BµwºÐ®e¶q¤j©ó 1GB¡A
 	    ¨º»òµwºÐ³]©w°Ñ¼Æ(geometry)´N·|¨Ï¥Î¹³¬O¡G
 	    M cylinders¡B255 heads¡B¨CºÏ­y 63 sectors(½Ðª`·N¡G¤£¬O¡y64¡z®@)¡A
 	    ³o¸ÌÁ¿ªº¡y<literal>M</literal>¡z¬O«üµwºÐªº®e¶q(³æ¦ì¡GMB)¦A°£¥H
 	    7.844238 ©Ò±o¥Xªº¼Æ­È³á¡I©Ò¥H¡A³o­Ó¨Ò¤lªº¸Ü¡A¦P¼Ë¬O 2GB µwºÐÀ³¸Ó¬O
 	    261 cylinders¡B255 heads¡B¨CºÏ­y 63 sectors¡C</para>
 
           <para>­Y¹ï¤W­±Á¿ªº¤£ÁA¸Ñ¡A©Î¬O FreeBSD ¦b¦w¸Ë®É©Ò°»´ú¨ìªºµwºÐ³]©w°Ñ¼Æ(geometry)
 	    ¦³°ÝÃDªº¸Ü¡A³Ì²³æªº¸Ñªk³q±`¬O¦bµwºÐ¤W«Ø¥ß¤@¶ô¤p¤pªº DOS ¤À³Î°Ï(partition)¡C
 	    ³o¼Ë¤@¨Ó¡A´N¥i¥H°»´ú¨ì¥¿½TªºµwºÐ³]©w°Ñ¼Æ¤F¡A¦Ó¥B¡A
 	    ¦pªG¤£·QÄ~Äò¯dµÛ¨º¤p¶ô DOS ¤À³Î°Ïªº¸Ü¡A¥i¥HÀH®É¥Î partition editor
 	   ¨Ó®³±¼¥¦¡C©ÎªÌ§â¥¦¯dµÛ·í§@ºô¸ô¥dÅX°Êµ{¦¡¨Ï¥Î¡A©ÎÀH§A°ª¿³«ç»ò¥Î¥¦¡C</para>
 
 	  <para>¦¹¥~©O¡A¦³­Ó§K¶O¦n¥Îªº¤u¨ãµ{¦¡¥s°µ¡y<filename>pfdisk.exe</filename>¡z¡A
 	    ³o­Óµ{¦¡©ñ¦b¦U FreeBSD FTP ¯¸©Î¥úºÐªº <filename>tools</filename> ¥Ø¿ý¤U¡A
 	    ¥¦¥i¥H¥Î¨Ó§ä¥XµwºÐ¤W¨ä¥L§@·~¨t²Î©Ò¨Ï¥ÎªºµwºÐ³]©w°Ñ¼Æ¡A
 	    µM«á´N¥i¥H¦b partition editor ¤º¿é¤J­è­è§ä¨ìªº¨º¨Ç³]©w°Ñ¼Æ´N¥i¥H¤F¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="disk-divide-restrictions">
           <para>¤À³ÎºÏºÐ¾÷®É¦³¥ô¦ó­­¨î¶Ü¡S</para>
         </question>
 
         <answer>
           <para>¦³¡A§A¥²¶·½T»{§Aªº root ¤À³Î°Ï¬O¦b 1024 cylinders ¤§¤º¡AÅý
 	    BIOS ¥i¥H±q¨ä¤¤±Ò°Ê®Ö¤ß¡C(ª`·N¡G³o¬O PC ªº BIOS ¥\¯à­­¨î¡A¦Ó¤£
 	    ¬O FreeBSD ªº)</para>
 
           <para>¥H SCSI µwºÐ¦Ó¨¥¡A³q±`¬O§â <literal>root</literal> (<filename>/</filename>)
 	    ¤À³Î°Ï©ñ¨ìµwºÐ³Ì«e­±ªº 1024MB (¦pªG¦³¤ä´© extended translation ªº¸Ü¡A
 	    ¨º»ò¬O³Ì«e­±ªº 4096MB ¡X ³oÂI½Ð°Ñ¦Ò¤W¤@¤p¸`)¡C¦Ó IDE µwºÐªº¸Ü¡A¬Û¹ïÀ³ªº«h¬O 504MB¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="disk-manager">
           <para>¥i¥H¨Ï¥Î­þ¨ÇºÏºÐºÞ²zµ{¦¡(disk managers)©O¡H</para>
         </question>
 
         <answer>
           <para>FreeBSD ¥i¥H¥Î Ontrack Disk Manager ¨Ã¥B¹B§@¥¿±`¡A
             ¦Ü©ó¨ä¥Lªº disk manager «h¤£¦b¥¿¦¡¤ä´©¤§¦C¡C</para>
 
           <para>­Y¾ãÁûµwºÐ¥u¸Ë FreeBSD ¡A¨º»ò´N¤£¥Î¦A¸Ë  disk manager ¤F¡C
             ¥u­n§âµwºÐ³]©w¬° BIOS ©Ò¯à§ì¨ìªº³Ì¤jªÅ¶¡¡A¨º»ò FreeBSD ´N¥iºâ¥X¹ê»Ú¤W¥i¨Ï¥ÎªºªÅ¶¡¤F¡C
 	    ¦pªG¡A¥¿¦b¨Ï¥Îªº¬O¥j¦­ MFM ±±¨î¥dªºÂ¦¡µwºÐ¡A
 	    ¨º»ò´N»Ý­n¦b FreeBSD¤º§@ cylinders ¬ÛÃö³]©w¤F¡C</para>
 
           <para>¦pªG·Q¦bºÏºÐ¤W¨Ï¥Î FreeBSD ©M¥t¥~ªº§@·~¨t²Î¡A¤]¥i¥H¤£¸Ë disk manager¡A
 	    ¥u­n½T©w FreeBSD ªº±Ò°Ê¤À³Î°Ï¸ò¨ä¥L§@·~¨t²Îªº slice ³£¦ì©ó¶}©lªº 1024 cylinders 
 	    ¤º´N¥i¥H¤F¡C¦pªG§A¬Û·í¦a°ª©úªº¸Ü¡A¤@­Ó 20MB ªº±Ò°Ê¤À³Î°ÏÀ³¸Ó´N°÷¥Î¤F¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="missing-os">
           <para>FreeBSD ¦w¸Ë§¹²¦«á­«¶}¾÷¡A¦ý¬O¹q¸£«o»¡ <errorname>Missing Operating
             System</errorname>³o¬O«ç»ò¤F¡H</para>
         </question>
 
         <answer>
           <para>³q±`­ì¦]¥X¦b FreeBSD ¤Î DOS ©Î¨ä¥L§@·~¨t²Î¦bµwºÐªº <link
 	    linkend="geometry">³]©w°Ñ¼Æ(geometry)</link>¤Wªº³W¹º¦³¬Û½Ä¡C¸Ñªk¬O­«¸Ë¡A¦ý¬O½Ð·Ó
 	    ¤W­zªº¬ÛÃö³¹¸`¨BÆJ¨Ó°µ¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="stop-at-boot-manager">
           <para>¬°¤°»ò¾÷¾¹¤W¦h­«¶}¾÷ºÞ²z­û(boot manager)¥X²{¤F <prompt>F?</prompt> ³o­Ó¿ï³æµe­±¡A
 	        ¦ý«o¤£·|¦Û°Ê¸õ¹L¦ÓÄ~Äò¶}¾÷©O¡H</para>
         </question>
 
         <answer>
           <para>³o­Ó¯gª¬¬O¥»¤å¤W­±©Ò´£ªº¥t¥~¤@­Ó°ÝÃD¤F¡A­ì¦]¦b©ó BIOS ¤W¸ò FreeBSD 
 	    ¤W­±¨âÃ䪺µwºÐªº <link linkend="geometry">³]©w°Ñ¼Æ(geometry)</link> ¨Ã¤£¤@­P¡C
             ­Y§AµwºÐ©Î BIOS ¤ä´© cylinder translation
 	    (³q±`·|³Q¼Ð¬° <quote>support &gt;1GB(¤ä´© 1 GB¥H¤W®e¶q)</quote>ªº¸Ü¡A
 	    ¸Õ¸Õ¬Ý§ó§ï¬ÛÃö³]©w¡A¨Ã­«¸Ë FreeBSD¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="need-complete-sources">
           <para>¦w¸Ë FreeBSD ®É¡A»Ý­n¦w¸Ë§¹¾ãªº sources ¶Ü¡H</para>
         </question>
 
         <answer>
           <para>¤@¯ë¨Ó»¡¡A³o¬O¥Î¤£µÛªº¡CµM¦Ó¡A§Ú­Ì±j¯P«Øij±zªº source ¦Ü¤Ö­n¸Ë 
 	    <literal>base</literal>(¥]§t¤F¥»¤å¤¤©Ò´£ªº¤@¨ÇÀÉ®×)¡B¥H¤Î
 	    <literal>sys</literal> (kernel ªº source ÀÉ)¡C
             ÁöµM¡A§@·~¨t²Î¥»¨­¹B¬O¤£»Ý­n¸Ë source ÀÉ¡A¦ý¬O &man.config.8; ³o­Ó kernel³]©wµ{¦¡«h»Ý­n src ¡C
 	    ­Y¨S¸Ë kernel ªº source ÀÉ¡A¤´µM¥i¥H¥Î¨ä¥L¦a¤è³z¹L NFS ±¾¸üªº°ßŪÀɮרt²Î¡A
 	    ¨Ó½sĶµ{¦¡¡C
             ¦ý¥Ñ©ó kernel-source ¥»¨­ªº­­¨î¡A§Ú­Ì«Øij¤£­nª½±µ mount ¦b <filename>/usr/src</filename>¡A
 	    ³Ì¦n¬O¥Î symbolic link(°Ñ¾\ &man.ln.1;) ±N±¾¸üªº¸ô®|¡A³]©w³sµ²¨ì<filename>/usr/src</filename>
 	    ¥Ø¿ý¡C</para>
 
           <para>¦b¾÷¾¹¤Wª½±µ¸Ë¦³ source ¨Ã¥BÁA¸Ñ¬ÛÃö½sĶ¹Lµ{¡A³o¼Ë¤l¤é«á¤É¯Å 
 	    FreeBSD ·|¨Ó±o¤è«K¦h¡C</para>
 
           <para>­Y§Ñ¤F¸Ë¬ÛÃö source ªº¸Ü¡A¥i¥H¨Æ«á¥Î <command>sysinstalll</command> 
 	    (&os; 6.X ¤§«e¬° <command>/stand/sysinstall</command>) ¨Ó¸É¸Ë¡A¿ï³æ¡GConfigure ¡÷ Distributions ¡÷ src¡C
 	    </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="need-kernel">
           <para>»Ý­n­«·s build kernel ¶Ü¡H</para>
         </question>
 
         <answer>
           <para>¦b«Ü¤[«Ü¤[¥H«e¡A­ì¥»­«·s build kernel ¦b FreeBSD ¦w¸Ë¹Lµ{¤¤¡A
 	    ¬Oµ´¹ï¥²»Ýªº¨BÆJ¤§¤@¡C¦ý¥Ø«e¦­´N¤£¥Î³o»ò³Â·Ð¤F¡A
 	    ¥Ø«e¥D­n±`¨£ªºª©¥»³£¨Ï¥Î§ó¤Íµ½ªº kernel ³]©w«ü¥O¡C
 	    &os; 4.X(§t¤§«eª©¥»)¡A¦b FreeBSD ±Ò°Ê´£¥Ü¸¹(boot:)®É¡A¨Ï¥Î <option>"-c"</option> flag
 	    ´N·|¶i¤J³]©wµe­±¡A¨Ó¹ï kernel §@±`¨£ªº ISA ¥d²Ó¸`³]©w¡C
 	    ¦Ó &os; 5.X(§t¤§«áª©¥»)ªº¸Ü¡A«h¬O¥H§ó¨ã¼u©Êªº "hints" ³]©w¤è¦¡¡C</para>
 
           <para>¦pªG·Q§ó¸`¬Ù RAM ªº¨Ï¥Î¡BÁYµu¶}¾÷¬yµ{¡A¨º»ò«Øij¡G·sªº kernel ³]©wÀÉ¥u­n¥]§t§A»Ý­nªºÅX°Êµ{¦¡¡A
 	    µM«á­«·s½sĶ¡B¦w¸Ë kernel ¨Ã­«¶}¾÷¡CµM¦Ó©O¡A³oÂI¹ï¤j¦h¼Æªº¨t²Î¨Ó»¡¡A
 	    ³o¤£¤@©w¬O¥²­nªº¡C</para>
 
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="password-encryption">
           <para>±K½X½s½X¸Ó±Ä¥Î DES¡BBlowfish ©Î MD5 ªº­þ¤@ºØ¡H¸Ó«ç»ò³]©w©O¡H</para>
         </question>
 
         <answer>
           <para>FreeBSD ¹w³]ªº±K½X½s½X¤è¦¡¬O±Ä <emphasis>MD5</emphasis>¡C
 	    ´N±K½X½s½X¤è¦¡¦Ó¨¥¡AMD5 ¤è¦¡¤@¯ë³Qµø¬°¤ñ¶Ç²Î &unix; ªº <emphasis>DES</emphasis> ¤è¦¡¸û¬°¦w¥þ¡C
             µM¦Ó¡A­Y¦³»Ý­n¦b¨Ï¥ÎÂÂÀô¹Ò(¸û¤£¦w¥þªº±K½X½s½X¤è¦¡ªº)¡ADES ±K½X½s½X¤è¦¡¤@¼Ë¥i¥H¨Ï¥Î¡C
 	    (­Y¨Ï¥Î sysinstall ®É¦³¿ï¾Ü <quote>crypto</quote> ®M¥ó¡A©Î¬O±q source ¤º½sĶ¦w¸Ë)
             ¦³¸Ë crypto ªº¸Ü¡Acrypto libraries ¤]¤ä´©§ó¦w¥þªº Blowfish ½s½X¤è¦¡¡C</para>
 	    
 	  <para>±K½X½s½Xªº¤è¦¡¬O¥Ñ <filename>/etc/login.conf</filename> ¤ºªº 
 	    <quote>passwd_format</quote> Äæ¦ì¨Ó¨M©wªº¡C¸ÓÄæ³]©w­È¡A(­Y¦³¸Ë crypto ªº¸Ü)¥i¥H¬O
 	    <quote>des</quote> ©Î <quote>blf</quote> ©Î¬O­ì¥»ªº <quote>md5</quote>¡C
             ¸Ô±¡½Ð°Ñ¾\ &man.login.conf.5; »¡©ú¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="boot-floppy-hangs">
           <para>¬°¤°»ò¶}¾÷ºÏ¤ù¶}¨ì¤@¥b¡A´N¥X²{
             <literal>Probing Devices...</literal> ªºµe­±°T®§¡AµM«á´N°±¦í¤F¡H</para>
         </question>
 
         <answer>
 
           <para>­Y¾÷¾¹¤W¦³¸Ë IDE ¤¶­±ªº Iomega &iomegazip; ©Î¬O &jaz; ªº¸Ü¡A
 	    ¦]¬°³o¨Ç³]³Æ¥i¯à¸ò¶}¾÷¤ù¦³¬Û½Ä¡A½Ð¥ý®³±¼³o¨Ç³]³Æ¦A­«¸Õ¡C
 	    ·í¾ã­Ó§@·~¨t²Î¸Ë¦n«á¡A´N¥i¥H§â³o¨Ç³]³Æ±µ¦^¥h¨Ï¥Î¤F¡C
 	    §Æ±æ³oÂI¦b¤é«á release ªº FreeBSD ¥i¥HÀò±o¹ý©³¸Ñ¨M¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="panic-on-install-reboot">
           <para>¨t²Î¸Ë§¹¨Ã­«¶}¾÷«á¡A¬°¤°»ò«o¥X²{ <errorname>panic: can't mount root</errorname>¡H</para>
         </question>
 
         <answer>
           <para>³o­Ó¿ù»~¬O¦]¬°±Ò°ÊºÏ°Ï¸ò kernel ¨âªÌ¹ïºÏºÐ¸Ë¸mªº»{ª¾¤£¬Û¦P¡C
 	    ³q±`³o°ÝÃD·|µo¥Í¦b¦³¨âÁû IDE µwºÐªº¨t²Î¡A¤ñ¦p¡GµwºÐ Jumper ³]©w¬° Master¡B
 	    ©Î¬O¨â±ø IDE ±Æ½u¦U¥u³s±µ¤@ÁûµwºÐ¡A¦ý¬O¸Ë FreeBSD ¨ºÁû¶}¾÷µwºÐ¡A
 	    «o±µ¦b Secondary IDE ±Æ½u¤W¡C
 	    ¦p¦¹¤@¨Ó¡A¦b¶}¾÷®É·í kernel «ü©w²Ä¤G­Ó IDE ±±¨î¾¹ªº²Ä¤@­ÓºÏºÐ¾÷ ad2¡A
 	    ±Ò°ÊºÏ°Ï«o»{¬°¨t²Î¬O¸Ë¦b ad0(BIOS°»´úªº²Ä¤GÁûµwºÐ)¡I
 	    °»´ú§¹¸Ë¸m«á¡Akernel ¸ÕµÛ§â±Ò°ÊºÏ°Ï©Ò»{¬°ªº¶}¾÷µwºÐ(ad0) mount 
 	    °_¨Ó¡A¨Æ¹ê¤WÀ³¸Ó¬O ad2 ¤~¹ï¡A©Ò¥H´N·|¥X²{¤W­±ªº¿ù»~°T®§¤F¡C</para>
 
           <para>¸Ñªk¦p¤U¡A½Ð¿ï¾Ü¨ä¤¤¤@ºØ¤è¦¡´N¦n¡G</para>
 
             <orderedlist>
               <listitem>
                 <para>­«¶}¾÷¨Ã¦b¥X²{¡y<literal>Booting kernel in 10 seconds; hit [Enter] to interrupt</literal>¡z
 		  ´£¥Üªº®É­Ô¡A«ö¤U <keycap>Enter</keycap>Áä¡C
 	          ³o¼Ë¤l´N·|¶i¤J boot loader µe­±¡G</para>
 
                 <para>½Ð¿é¤J
                   <literal>
                   set
                   root_disk_unit="<replaceable>disk_number</replaceable>"
                   </literal> ³o¸Ìªº¡y<replaceable>disk_number</replaceable>¡z½Ð¨Ì¾Ú±¡ªp´«¦¨¬ÛÃö¥N¸¹¡G
 		  ­Y FreeBSD µwºÐ¬O³]©w¸Ë¦b Primary IDE ±µ½uªº Master¡A´N³]¬° 0 ¡F
 	          ­Y¬O Primary IDE ±µ½uªº Slave¡A´N³]¬° 1¡F
 	          ­Y¬O Secondary IDE ±µ½uªº Master¡A´N³]¬° 2¡F
 	          ­Y¬O Secondary IDE ±µ½uªº Slave¡A´N³]¬° 3¡C</para>
 
                 <para>±µµÛ½Ð¦A¿é¤J <literal>boot</literal>¡AµM«á¨t²ÎÀ³¸Ó´N¥i¥H¥¿±`¶}¾÷¤F¡C</para>
 
                 <para>­Y­n¨C¦¸¶}¾÷³£¦Û°Ê³]©w¡A¦Ó¤£¥²¨C¦¸³£¥´¤@¦¸¡A¨º»ò´N¦b <filename>/boot/loader.conf.local</filename>
 	          Àɮפº¥[¤W <literal>root_disk_unit="<replaceable>disk_number</replaceable>"</literal> 
 	          ³o¦æ
 		  (·íµM¡A¡y<replaceable>disk_number</replaceable>¡z­n§ï¦¨¬ÛÃö¥N¸¹)</para>
               </listitem>
 
               <listitem>
                 <para>§â FreeBSD µwºÐ§ï±µ¨ì Primary IDE ±µ½u¤W¡A¦p¦¹¤@¨Ó´N¥i¶¶§Q¨Ï¥Î¡C</para>
               </listitem>
             </orderedlist>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="memory-limits">
           <para>°O¾ÐÅé³Ì¤j­­¨î¬°¦h¤Ö¡H</para>
         </question>
 
         <answer>
           <para>¤@¯ë &i386; ¾÷¾¹¤W³Ì¦h¥i¤ä´©¨ì 4 GB(gigabytes)¡C
             ¦Ó¦Û &os; 4.9 ¤Î 5.1 ¥i¥H¶}©l¨Ï¥Î &man.pae.4; ¨Ó¤ä´©§ó¦hªº°O¾ÐÅé¡C
             ¦³Ãö³oÂI¡A»Ý­n¦b kernel ³]©wÀɤº¥[¤J¤U¦C¤º®e¨Ã­«·s½sĶ kernel¡A¤~¯à¨Ï¥Î PAE¡C</para>
 
             <programlisting>options       PAE</programlisting>
 
           <para>&os; ¦b pc98 ¾÷¾¹¤W³Ì¦h«h¥u¤ä´© 4 GB ¡A¦Ó¥B¤£¯à¨Ï¥Î PAE¡C
             ¦b Alpha ¾÷¾¹¤W¡A°O¾ÐÅé­­¨î¤è­±­nµø©Ò¨Ï¥Îªº«¬¸¹¤ä´©µ{«×¦Ó©w¡A³oÂI½Ð°Ñ¾\
 	    ©Ò¨Ï¥Îªº Alpha µwÅé³W®æªí¡C¦Ü©ó¨ä¥L¬[ºcªº &os; ²z½×¤W³Ì¦h¥i¨Ï¥Îªº°O¾ÐÅé¡A¦³¸û¦hªº­­¨î¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ffs-limits">
           <para>Àɮרt²Î³Ì¤j­­¨î¬°¦h¤Ö¡H</para>
         </question>
 
         <answer>
           <para>´NÀɮרt²Î¤è­±¡A²z½×¤Wªº­­¨î¬O³Ì¦h¨ì 8TB(2G blocks)¡A
 	    ©Î¬O¨Ï¥Î¤º©w 8K block ¤j¤p®É¡A­­¨î¬O 16TB¡C
 	    ¹ê»Ú¤W¡A¥Ø«e³nÅé¨Ï¥Î¤W­­¨î¥u¯à¥Î¨ì 1 TB¡A
 	    µM¦Ó¦pªG¬O¦³¥t¦æ§ï³y¹LÀɮרt²Î¡A¨º»ò¹F¨ì 4TB ªº¥Ø¼Ð¬O¥i¦æªº
 	    (¤]¦³¤H¦¨¥\¹L)¡C</para>
 
           <para>³æ¤@Àɮתº¤j¤p¤è­±¡A°²¦p block ¥H 4K §@³W¹ºªº¸Ü¡A
 	    «h³Ì¤j¬OÁͪñ 1G blocks(4TB)¡C</para>
 
           <table>
             <title>Àɮפj¤pªº³Ì¤j­­¨î</title>
 
             <tgroup cols="3">
               <thead>
                 <row>
                   <entry>Àɮרt²Î block ¤j¤p</entry>
 
                   <entry>works</entry>
 
                   <entry>should work</entry>
                 </row>
               </thead>
 
               <tbody>
                 <row>
                   <entry>4K</entry>
 
                   <entry>4T-1</entry>
 
                   <entry>&gt;4T</entry>
                 </row>
 
                 <row>
                   <entry>8K</entry>
 
                   <entry>&gt;32G</entry>
 
                   <entry>32T-1</entry>
                 </row>
 
                 <row>
                   <entry>16K</entry>
 
                   <entry>&gt;128G</entry>
 
                   <entry>32T-1</entry>
                 </row>
 
                 <row>
                   <entry>32K</entry>
 
                   <entry>&gt;512G</entry>
 
                   <entry>64T-1</entry>
                 </row>
 
                 <row>
                   <entry>64K</entry>
 
                   <entry>&gt;2048G</entry>
 
                   <entry>128T-1</entry>
                 </row>
               </tbody>
             </tgroup>
           </table>
 
           <para>When the fs block size is 4K, triple indirect blocks work
             and everything should be limited by the maximum fs block number
             that can be represented using triple indirect blocks (approx.
             1K^3 + 1K^2 + 1K), but everything is limited by a (wrong) limit
             of 1G-1 on fs block numbers. The limit on fs block numbers
             should be 2G-1. There are some bugs for fs block numbers near
             2G-1, but such block numbers are unreachable when the fs block
             size is 4K.</para>
 
           <para>block ¤j¤p¦pªG¬O 8K ©Î§ó¤j¡AÀɮרt²Î block ¼Æ¥Ø·|³Q­­¨î¦b 2G-1
 	    ¡A¦ý¹ê»Ú¤WÀ³¸Ó»¡­­¨î¬O 1G-1 ¤~¹ï¡A¦]¬°±Ä¥Î 2G-1 block ªºÀɮרt²Î·|¾É­P¤@¨Ç°ÝÃD¡C
 	    </para>
 
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="archsw-readin-failed-error">
           <para>¬°¦ó¦b±Ò°Ê·sªº kernel ®É¡A¬Ý¨ì 
 	    <errorname>archsw.readin.failed</errorname> ¿ù»~°T®§¡H</para>
         </question>
 
         <answer>
           <para>­ì¦]¥X¦b§Aªº world ¥H¤Î kernel ¨Ã¤£¦P¨B¡AÁ|¨Ò¡Gkernel ¥Î 4.11¡A
 	    ¦Ó world «o¬O 4.8¡A³o¼Ë¬O·|¦³°ÝÃDªº¡C
 	    ½Ð¦A¦¸½T»{¡A¬O§_¦³¥H <command>make buildworld</command> ¤Î
 	    <command>make buildkernel</command> ¨Ó¥¿±`§ó·s kernel¡C</para>
 
 	  <para>¦b±Ò°Ê loader ¤§«e¡A·|¬Ý¨ì "|" ³o­Ó²Å¸¹¦bÂà°Ê¡A³o®É¥i¥H«ö¥ô¦óÁ䤤Â_¡A
 	    µM«á¦A«ü©w­n¸ü¤J­þ­Ó kernel ¨Ó¶}¾÷¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="security-profiles">
           <para><quote>security profiles</quote> ¬O«ü¤°»ò¡H</para>
         </question>
 
         <answer>
           <para>A <quote>security profile</quote> is a set of configuration
             options that attempts to achieve the desired ratio of security
             to convenience by enabling and disabling certain programs and
             other settings.  For full details, see the <ulink
             url="&url.books.handbook;/install-post.html#SECURITYPROFILE">Security
             Profile</ulink> section of the Handbook's <ulink
             url="&url.books.handbook;/install-post.html">post-install
             chapter</ulink>.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
 	<question id="boot-acpi">
 	  <para>¦b¶}¾÷®É¡A¿ï¾Ü¨Ï¥Î ACPI «h¦b¦w¸Ë¹Lµ{´N±¾¤F¡A¸Ó«ç»ò¿ì¡H</para>
 	</question>
 
 	<answer>
 	  <para>¸Õ¸Õ¬ÝÃö³¬ ACPI support¡C ·í¦b¸ü¤J bootloader®É¡A«ö¤UªÅ¥ÕÁä¡C
 	    ¨t²Î·|Åã¥Ü <screen>OK</screen> ³o®É¿é¤J
 	    <screen><userinput>unset acpi_load</userinput></screen> ±µµÛ¥´
 	    <screen><userinput>boot</userinput></screen>
 	    ¥HÄ~Äò¶}¾÷¡A³o¼Ë¤lÀ³¸Ó´N¥i¥H¤F¡C</para>
 	</answer>
       </qandaentry>
 
     </qandaset>
   </chapter>
 
   <chapter
     id="hardware">
     <title>µwÅé¤ä´©¤è­±</title>
 
       <sect1 id="compatibility-general">
 	<title>¤@¯ë°ÝÃD</title>
 
     <qandaset>
       <qandaentry>
         <question id="which-hardware-to-get">
           <para>§Ú·Q²Õ¸Ë¦Û¤vªº FreeBSD ¾÷¾¹¡A¦³­þ¨Ç«¬¸¹¡B«~µP¡B³W®æ¬O¤ä´©µ{«×³Ì¦nªº©O¡H</para>
         </question>
 
         <answer>
           <para>¦³Ãö³oÂI¡A¦b FreeBSD °Q½×°Ï¤W®É±`¦³¤H°Q½×¡CÁöµMµwÅé¨O´«³t«×«Ü§Ö¡A
 	    ¥i¯àÀH®É¦³·s³W®æ¡B·s²£«~¥X²{¡AµM¦Ó³o¨Ç³£¦b§Ú­Ì·N®Æ¤§¤¤¡A
 	    §Ú­Ì <emphasis>¤´µM</emphasis> ±j¯P«Øij¡G¦b¸ß°Ý¦³Ãö³Ì·s³W®æµwÅ骺¤ä´©°ÝÃD¤§«e¡A
 	    ½Ð¥ý°Ñ¾\ &os 
 	    <ulink url="&rel.current.hardware;">&rel.current;</ulink>
 	    ©Î
 	    <ulink url="&rel2.current.hardware;">&rel2.current;</ulink>ªº¤ä´©µwÅé¦Cªí¡A
 	    ©Î¬O·j´M<ulink url="http://www.FreeBSD.org/search/#mailinglists">°Q½×°ÏªºÂ¤峹</ulink>¡A
             ¤]³\¡A¤W¶g¤~­è«ê¥©¦³¤H°Q½×¹L§A©Ò­n°ÝªºµwÅé¡C</para>
 
           <para>¦pªG­n§ä¦³Ãöµ§°O«¬¹q¸£¤è­±¡A½Ð¨ì FreeBSD-mobile µ§°O«¬¹q¸£°Q½×°Ï¡C
             ¤£µM¡A´N¨ì FreeBSD-questions °Q½×°Ï¡A©Î¬O¯S©wµwÅé³W®æ(¤ñ¦p pc98, Alpha)ªº±MÄÝ°Q½×°Ï§a¡C
             </para>
         </answer>
       </qandaentry>
 
     </qandaset>
       </sect1>
 
       <sect1 id="compatibility-processors">
 	<title>µwÅé¬[ºc¤Î CPU</title>
 
     <qandaset>
       <qandaentry>
         <question id="architectures">
           <para>FreeBSD ¦³¤ä´© x86 ¤§¥~ªºµwÅé¬[ºc¥­¥x¶Ü¡H</para>
         </question>
 
         <answer>
 
           <para>¦³ªº¡AFreeBSD ¥Ø«e¥i¥H¦b Intel x86 and DEC
             (²{¦bªº HP-Compaq) Alpha ¬[ºc¤W­±¹B§@¡C¦Û FreeBSD 5.0 ¤§«áªºª©¥»¡A«h
             ¥i¤ä´© AMD64 ¤Î Intel EM64T, IA-64 ¥H¤Î &sparc64; ¬[ºc¡C
             ¥¼¨Ó¥­¥x¤ä´©¤WÁÙ·|¦³ &mips; ¤Î
             &powerpc;¡A²Ó¸`½Ð¤À§O°Ñ¾\ &a.mips; ©Î &a.ppc;¡C
             ¤@¯ë¦Ó¨¥¡A·sªºµwÅé¬[ºc¥­¥x¤è­±¡A³£¬O¨ì &a.platforms; °Q½×¡C</para>
 
           <para>­Y§A¾÷¾¹¤£¬O¥H¤W¬[ºc©Î¬O¤ñ¸û©_¯Sªº¡A¦Ó·Q¥ß¨è¸Õ¸Õ¬Ý BSD ªºÅ]¤O¡A
 	    §Ú­Ì«Øij§A¥i¥H¦Ò¼{¨Ï¥Î <ulink
             url="http://www.netbsd.org/">NetBSD</ulink> ©Î <ulink
             url="http://www.openbsd.org/">OpenBSD</ulink>¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="smp-support">
           <para>FreeBSD ¤ä´© CPU ¹ïºÙ¦h¤u³B²z(SMP, Symmetric Multiprocessing)¶Ü¡H</para>
         </question>
 
         <answer>
           <para>¦³ªº¡C SMP ¦b &os; 5.2 ¹w³]ªº kernel(<emphasis>GENERIC</emphasis>)¤w¦³±Ò°Ê¡C
 	    </para>
 
           <para>¦b &os; 5.3 ­n release ®É¡ASMP¬ÛÃö³]©w¤]¬O¹w³]´N¦³±Ò°Ê¡C
 	    µM¦Ó¡A¦b¤@¨Ç¸û·s«¬ªº¾÷¾¹(¹³¬O emt64)¤W«o¤S¦³¨Ç°ÝÃD¡A
 	    ©Ò¥HÁÙ¬O¨M©w¦b¬ÛÃö°ÝÃD¡B¦w¥þijÃD¥¼Àò¸Ñ¨M«e¡A¥ýÃö³¬ SMP ªº¬ÛÃö±Ò°Ê¡C
 	    ³oÂI¡A¥¿¬O &os; 5.4 ©ÒÀu¥ý¦Ò¼{ªº¤è¦V¡C</para>
 
           <para>&os; 4.X ªº¸Ü¡A¹w³]ªº kernel ¨Ã¨S¦³±Ò°Ê SMP¡A
             ¦]¦¹¡A¥²¶·­n§â options SMP ¥[¤J kernel ³]©wÀɨí«·s½sĶ¤~¯à±Ò°Ê¡C
 	    ¦Ü©óÁÙ¦³­þ¨Ç¬ÛÃö³]©w­n©ñ¤J kernel ³]©wÀÉ¡A½Ð°Ñ¾\<filename>/sys/i386/conf/LINT</filename>¡C
 	   </para>
         </answer>
       </qandaentry>
         </qandaset>
       </sect1>
 
       <sect1 id="compatibility-drives">
 	<title>µwºÐ¡BºÏ±a¾÷¥H¤Î¥úºÐ¡BDVD¡B¿N¿ý¾÷</title>
 
 	<qandaset>
 
       <qandaentry>
         <question id="supported-hard-drives">
           <para>FreeBSD ¥i¤ä´©­þ¨ÇºØÃþªºµwºÐ©O¡H</para>
         </question>
 
         <answer>
           <para>FreeBSD ³£¤ä´© EIDE ¤Î SCSI ¤¶­±ªºµwºÐ(¥H¤Î SCSI ¥d¡A½Ð¬Ý¤U¤@¸`»¡©ú)
             ¥H¤Î <quote>Western Digital</quote> ¤¶­±ªºµwºÐ (MFM¡B RLL¡B
             ESDI¡A·íµM¥]§t IDE)¡A¤£¹L¦³¤@¨Ç¤Ö¼Æªº ESDI ´¹¤ù²Õªº(«¬¸¹¡GWD1002/3/6/7)
 	    ¥i¯àµLªk¥¿±`¹B§@¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="supported-scsi-controllers">
           <para>¤ä´©­þ¨Ç SCSI ¥d¡B³]³Æ©O¡H</para>
         </question>
 
         <answer>
           <para>½Ð°Ñ¾\ &os; ªºµwÅé¤ä´©ªí(
 	    <ulink url="&rel.current.hardware;">&rel.current;</ulink> ©Î
 	    <ulink url="&rel2.current.hardware;">&rel2.current;</ulink>)</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="tape-support">
           <para>¤ä´©­þ¨ÇºÏ±a¾÷©O¡H</para>
         </question>
 
         <answer>
 
           <para>FreeBSD ¤ä´© SCSI ¤Î QIC-36 (QIC-02 ¤¶­±) ³W®æªººÏ±a¾÷¡C
             ¦P®É¥]§t¤F 8-mm (¤]´N¬O Exabyte) ¤Î DAT ºÏ±a¾÷¡C</para>
 
           <para>¦³¨Ç¦­´Áª©¥»ªº 8-mm ºÏ±a¾÷¨Ã¤£¬O§¹¥þ¬Û®e©ó SCSI-2 ³W®æ¡A
 	    ©Ò¥H¥i¯à¦b FreeBSD ¤Wªí²{¤£¬O«Ü¦n¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="tape-changer-support">
           <para>FreeBSD ¤ä´©ºÏ±a¦Û°Ê´«±a¾÷¶Ü¡H</para>
         </question>
 
         <answer>
           <para>FreeBSD ¥i¥H¥Î &man.ch.4; ¤W­±©Ò¦Cªº¾÷ºØ¡A·f°t &man.chio.1; «ü¥O¡A
 	    ¨Ó¨Ï¥Î SCSI ºØÃþªº¦Û°Ê´«±a¾÷¡A²Ó¸`³¡¤À½Ð°Ñ¾\ &man.chio.1; »¡©ú¡C</para>
 
           <para>If you are not using <application>AMANDA</application>
             or some other product that already understands changers,
             remember that they only know how to move a tape from one
             point to another, so you need to keep track of which slot a
             tape is in, and which slot the tape currently in the drive
             needs to go back to.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="supported-cdrom-drives">
           <para>FreeBSD ¥i¤ä´©­þ¨ÇºØÃþªº¥úºÐ¾÷©O¡H</para>
         </question>
 
         <answer>
           <para>¥u­n¬O¦³¤ä´©ªº SCSI ¥d¤W©Ò±µªº¥ô¤@  SCSI ¥úºÐ¾÷³£¦³¤ä´©¡C</para>
 
           <para>¦¹¥~¡A¤]¤ä´©¤U¦Cªº¥úºÐ¾÷¡G</para>
 
             <itemizedlist>
               <listitem>
                 <para>Mitsumi LU002 (8bit), LU005 (16bit) ¤Î FX001D
                   (16bit 2x Speed)</para>
               </listitem>
 
               <listitem>
                 <para>Sony CDU 31/33A</para>
               </listitem>
 
               <listitem>
                 <para>Sound Blaster «D SCSI ¤¶­±ªº¥úºÐ¾÷</para>
               </listitem>
 
               <listitem>
                 <para>Matsushita/Panasonic ¥úºÐ¾÷</para>
               </listitem>
 
               <listitem>
                 <para>¬Û®e ATAPI ³W®æªº IDE CDROMs</para>
               </listitem>
             </itemizedlist>
 
           <para>¬Û¹ï©ó SCSI ¾÷ºØ¦Ó¨¥¡A¨ä¥L«D SCSI ªº¥úºÐ¾÷³£¬O¤ñ¸ûºC¡A
 	    ¦¹¥~¡A¦³¨Ç ATAPI ºØÃþªº¥úºÐ¾÷¥i¯àµLªk¶¶§Q¹B§@</para>
 
           <para>Daemon News ¥H¤Î FreeBSD Mall ©Òµo¦æªº¥¿¦¡ FreeBSD ¥úºÐ¥H¤Î¿N¿ý¥Îªº¼v¹³ÀÉ(ISO)¡A
 	    ³£¥i¥Hª½±µ¥Î©ó¶}¾÷¥úºÐ¨Ï¥Î¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="supported-cdrw-drives">
           <para>FreeBSD ¤ä´©­þ¨Ç¥úºÐ¿N¿ý¾÷ªºÅX°Êµ{¦¡©O¡H</para>
         </question>
 
 	<answer>
 	  <para>FreeBSD ¤ä´©¥ô¦ó¬Û®e ATAPI ¼Ð·Çªº IDE CD-R ©Î CD-RW ¥úºÐ¿N¿ý¾÷¡A
 	    ²Ó¸`½Ð°Ñ¾\ &man.burncd.8; »¡©ú¡C</para>
 
 	  <para>FreeBSD ¤]¤ä´©¥ô¦ó SCSI CD-R ©Î CD-RW ¥úºÐ¿N¿ý¾÷¡C
 	    ½Ð¥Î port ©Î packag ¾÷¨î¨Ó¦w¸Ë¡B¨Ï¥Î <command>cdrecord</command> ¡A
 	    ¨Ã½T©w±zªº kernel ¤º¦³±N <devicename>pass</devicename>³]³Æ¤@¨Ö½sĶ¦b¤º¡C
 	    (¹w³]ªº kernel.GENERIC ³£·|¦³ device pass ³o¬q)</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
         <question id="zip-support">
           <para>FreeBSD ¤ä´© Iomega &iomegazip; ¶Ü?</para>
         </question>
 
         <answer>
           <para>FreeBSD ¤ä´©¥~±µ¦¡ªº SCSI ¤Î ATAPI(IDE) ¤¶­±ªº Iomega &iomegazip;¡C
 	    ¤£¹L SCSI ZIP ¥u¯à³Q³]¬° SCSI ID 5 ©Î¬O 6 ¤~¥i¥H¹B§@¡A¦ý¦pªG 
 	    SCSI ¥d¤Wªº BIOS ¤ä´©¥¦¡A§A¬Æ¦Ü¥i¥H¥Î¥¦¨Ó¶}¾÷¡C
 	    §Ú­Ì¤£¾å±o­þ¤@¶ô¥d¥i¥H§â¥dªº ID ³]¦b°£¤F 0 ©Î 1 ¥H¥~ªº¦a¤è¦Ó¶}¾÷¦¨¥\¡A
 	    ¦]¦¹¡A¦pªG·Q§ï SCSI ID ªº¸Ü¡A½Ð°È¥²°Ñ¾\¸Ó«¬¸¹ªº»¡©ú¤â¥U¡C</para>
 
           <para>FreeBSD ¦P®É¤]¤ä´© Parallel Port ZipºÏºÐ¾÷¡C½ÐÀˬd kernel 
 	    ³]©wÀɬO§_¦³¡G
             <devicename>scbus0</devicename>¡B
             <devicename>da0</devicename>¡B
             <devicename>ppbus0</devicename>¡A¥H¤Î
             <devicename>vp0</devicename> ³o¨ÇÅX°Êµ{¦¡ (¹w³]ªº GENERIC kernel
             °£¤F <devicename>vp0</devicename> ¨S¥]¶i¥h¡A¨ä¥L¤TªÌ³£·|¦³)¡C
 	    ¥[¤F³o´X­ÓÅX°Êµ{¦¡¤§«á¡AParallel Port Zip ´N·|¦¨¬°
 	    <devicename>/dev/da0s4</devicename>¡C</para>
 
 	  <para>³o®É¡A´N¥i¥H¥Î¹³¬O <command>mount /dev/da0s4 /mnt</command> ©Î
 	    (DOS Àɮרt²Î)<command>mount_msdos /dev/da0s4 /mnt</command> 
 	    ¤§Ãþªº«ü¥O¨Ó±¾¸ü¡BŪ¼g¡C</para>
 
           <para>¤]¥i¥H°Ñ¾\¤U­±¦³Ãö<link linkend="media-change">ÀH¨­ºÏ¤ù
             </link>³¡¤À¡A¥H¤Î<link
             linkend="removable-drives">©â¨úºÐ¡BÀH¨­ºÐªº¡y®æ¦¡¤Æ¡z°Q½×</link>
             ªº³¡¤À</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="jaz-zip-removable-support">
           <para>FreeBSD ¦³¤ä´© &jaz;¡BEZ ¤Î¨ä¥LÃþ¦üªºÀH¨­ºÏ¤ù¶Ü¡H</para>
         </question>
 
         <answer>
           <para>¥i¥H°Ú¡A°£¤F IDE ªº EZ drive ¥~¡A¨ä¥LªºÀ³¸Ó³£¬O SCSI ¤¶­±¡A
 	    ©Ò¥H¦b FreeBSD ¤W³£·|¥H SCSI µwºÐ¨Ó³B²z¡C</para>
 
 	  <para>·íµM¡A§A¥²¶·½T©w¦b¶}¾÷®É¡A³o¨Ç³]³Æªº¹q·½¬O¥´¶}ªº¡A
 	    ¥H«KÅý FreeBSD ¥i¥H°»´ú¨ì¡C</para>
 
           <para><anchor id="media-change">¦pªG¦bºÏºÐ¹B¤¤ª¬ºA¤¤¡A­n§ó´«ºÏ¤ùªº¸Ü¡A
 	    °O±o¥ý¬Ý¤@¤U &man.mount.8;¡B&man.umount.8;¡B
 	    ¥H¤Î(SCSIªº¸Ü)&man.camcontrol.8; ©Î &man.atacontrol.8; ÁÙ¦³ FAQ «á­±¦³Ãö
 	    <link linkend="removable-drives">¨Ï¥Î©â¨úºÐ¡BÀH¨­ºÐªº°Q½×
             </link>¡C</para>
         </answer>
       </qandaentry>
 
 	</qandaset>
 
       </sect1>
 
       <sect1 id="compatibility-kbd-mice">
 	<title>Áä½L¡B·Æ¹«</title>
 
 	<qandaset>
 
       <qandaentry>
         <question id="usbkbd">
           <para>FreeBSD ¦³¤ä´© USB Áä½L¶Ü¡H</para>
         </question>
 
         <answer>
           <para>FreeBSD (¤×¨ä¬O¦³¤ä´© USB keyboards¡C  Enable USB support in
             <filename>/etc/rc.conf</filename>.</para>
 
           <para>­Y¦³¶} USB Áä½L¤ä´©¦Ó¥B¦P®É±µ¤W AT ¸ò USB Áä½Lªº¸Ü¡A¨º»ò AT Áä½L·|Åܦ¨ 
 	    <devicename>/dev/kbd0</devicename>¡A¦Ó USB Áä½L«h¬O
 	    <devicename>/dev/kbd1</devicename>¡C¦pªG¥u±µ USB Áä½L¡A¨º»ò¥¦´N¬O
 	    <devicename>/dev/ukbd0</devicename> Åo¡C</para>
 
           <para>¦pªG·Q¦b console ¤W¨Ï¥Î USB Áä½Lªº¸Ü¡A¨º»ò¥²¶·³]©w console «ü©w¥Î USB Áä½L¡C
 	    ¥i¥H¦b¨t²Î¶}¾÷µ{§Ç®É¡A¥[¤W¤U¦C«ü¥O¡G</para>
 
           <screen>&prompt.root; <userinput>kbdcontrol -k /dev/kbd1 &lt; /dev/ttyv0 &gt; /dev/null</userinput></screen>
 
           <para>ª`·N¡G­Y¥u¦³ USB Áä½Lªº¸Ü¡A¤]´N¬O <devicename>/dev/ukbd0</devicename>¡A
 	    ¨º»ò½Ð§ï¥Î¤U¦C«ü¥O¡G</para>
 
           <screen>&prompt.root; <userinput>kbdcontrol -k /dev/ukbd0 &lt; /dev/ttyv0 &gt; /dev/null</userinput></screen>
 
           <para>«Øij¡G¥i¥H§â¤W­z«ü¥O©ñ¤J <filename>/etc/rc.i386</filename> ¡C</para>
 
           <para>³]©w¦¨¥\¤§«á¡AUSB Áä½L¤£¥Î§@¥ô¦ó¯S§O³]©w¡A´N¥i¥H¦b X µøµ¡Àô¹Ò¤W¥¿±`¹B§@Åo¡C</para>
 
           <para>USB Áä½Lªº¼ö´¡©Þ(Hot-plugging and unplugging)¦b &os; ¥i¯àÁÙµLªk§¹¥þ¥¿±`¹B§@¡A
 	    «Øij¡G¦b¨t²Î¶}¾÷«e´N¥ý±µ¤WÁä½L¡Aª½¨ìÃö¾÷¬°¤î¡A¥HÁקK¤£¥²­nªº§xÂZ¡C</para>
 
           <para>¬ÛÃö²Ó¸`½Ð°Ñ¾\ &man.ukbd.4; ªº»¡©ú¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="busmouse">
           <para>¥j¦­ªº bus ·Æ¹«¡A­n«ç»ò³]©w©O¡H</para>
         </question>
 
         <answer>
           <para>FreeBSD ¤ä´©¤@¨Ç¼t°Ó(¹³¬O¡GMicrosoft¡BLogitech¡BATI)©Ò°µªº bus ¤Î InPort bus ¤¶­±ªº·Æ¹«¡C
             µM¦Ó¡A¹w³]ªº kernel(GENERIC)¤w¸g¤£¤º§t¥¦­ÌªºÅX°Êµ{¦¡¡C
 	    ¦]¦¹¡A­n¥[¤J¤U¦C¨ì kernel ³]©wÀɨí«·s½sĶ¡B¦w¸Ë¡A¤~¯à±Ò¥Î¡G</para>
 
           <programlisting>device mse0 at isa? port 0x23c irq5</programlisting>
 
           <para>Bus ·Æ¹«³q±`­n·f°t±M¥Îªº¤¶­±¥d¤~¯à¨Ï¥Î¡C
             ³o¨Ç¥d¥i¥H³]©w port address ¤Î IRQ ­È¡A³o¨Ç²Ó¸`½Ð°Ñ¾\§Aªº·Æ¹«»¡©ú¤â¥U¤Î
             &man.mse.4; »¡©ú¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ps2mouse">
           <para>PS/2 (<quote>mouse port</quote> ©Î
             <quote>keyboard</quote>)ªº·Æ¹«­n«ç»ò³]©w¤~¦n©O¡H</para>
         </question>
 
         <answer>
           <para>PS/2 ·Æ¹«³£¦³¤ä´©¡A©Ò»Ý­n¥Î¨ìªºÅX°Êµ{¦¡ <devicename>psm</devicename> 
 	     ¦b¹w³]ªº kernel(GENERIC)¤w¦³¤º§t¤F¡C</para>
 
           <para>­Y§A¦Û­qªº kernel ¤ºº|¤F psm ªº¸Ü¡A¨º»ò´N¦A§â¤U¦C¤º®e¥[¨ì kernel 
 		³]©wÀɨí«·s½sĶ¡B¦w¸Ë¡G</para>
 
           <programlisting>device psm0 at atkbdc? irq 12</programlisting>
 
           <para>·í¶}¾÷®É kernel ¦³¥¿½T°»´ú¨ì <devicename>psm0</devicename>
             ¡A½Ð°È¥²½T»{¦b <filename>/dev</filename> ¤º¦³
             <devicename>psm0</devicename> ¡C
 	    ¦pªG¨S¦³ªº¸Ü¡A¨º»ò´N¥Î <username>root</username> ¨Ó¥´¤U¦C«ü¥O¨Ó«Ø¥ß§a¡G</para>
 
           <screen>&prompt.root; <userinput>cd /dev; sh MAKEDEV psm0</userinput></screen>
 
           <note>
 	    <para>¦pªG¬O &os; 5.0-RELEASE(§t¤§«áª©¥»)ªº¸Ü¡A¦]¬°±Ä¥Î &man.devfs.5; ¾÷¨îªº¦]¯À¡A
 	      ©Ò¥H·|¦Û°Ê¦b <filename>/dev</filename> ¤U«Ø¥ß¬ÛÃö³]³Æªº¸`ÂI¡A¦]¦¹´N¥i¥H²¤¹L¤W­±³o¤@¨B¡C</para>
 	  </note>
 	</answer>
       </qandaentry>
 
       <qandaentry>
         <question id="moused">
           <para>¦pªG¤£¥Î X Window Àô¹Òªº¸Ü¡A¤]¥i¥H¥Î·Æ¹«¶Ü¡H</para>
         </question>
 
         <answer>
           <para>­Y¨Ï¥Î console ªº¹w³]ÅX°Êµ{¦¡(¤]´N¬O &man.syscons.4;)¡A
 	    ¨º»ò´N¥i¥H¦b¤å¦r¤¶­±ªº console ¤W­±¥Î·Æ¹«¨Ó°Å¶K¤å¦r¤F¡C
 	    ¨º»ò­n±Ò°Ê &man.moused.8; ¨Ã¶}±Ò´å¼ÐÅã¥Ü¡A
 	    ½Ð¥´¤U¦C«ü¥O¡G</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>¨ä¤¤¡y<replaceable>xxxx</replaceable>¡z¬O·Æ¹«ªº³]³Æ¦WºÙ¡A¦Ó
             ¡y<replaceable>yyyy</replaceable>¡z«h¬O·Æ¹«©Ò¨Ï¥Îªº protocol ºØÃþ¡C
             ¥Ø«eªº moused ¥i¥H¦Û°Ê°»´ú(°£¤F¦¡ªº serial
 	    ·Æ¹«¤§¥~)¤j¦h¼Æ·Æ¹«©Ò¨Ï¥Îªº protocol ºØÃþ¡A¦Ó¤£¥Î¨è·N¥h«ü©w¡C
             ¡yprotocol ºØÃþ¡z³]©w¥Î
             <literal>auto</literal> ´N·|¦Û°Ê°»´ú¤F¡C­Y¦Û°Ê°»´ú¥¢±Ñªº¸Ü¡A½Ð°Ñ¾\ &man.moused.8; 
 	    ¸Ì­±ªº type ¨º¬q»¡©ú¡C</para>
 
           <para>¦pªG¥Îªº¬O PS/2 ·Æ¹«¡A¥u­n§â
             <literal>moused_enable="YES"</literal> ¥[¨ì
             <filename>/etc/rc.conf</filename> ¡A³o¼Ë¨C¦¸¶}¾÷´N·|¦Û°Ê±Ò°Ê¤F¡C
             ¦¹¥~¡A¦pªG­n¦b©Ò¦³ virtual terminals ¤W¤]¯à¨Ï¥Î·Æ¹«¡A
 	    ¦Ó¤£­­©w¥u¦³ console ªº¸Ü¡A¨º»ò½Ð¦A§â
             <literal>allscreens_flags="-m on"</literal> ¥[¨ì <filename>/etc/rc.conf</filename> ¸Ì­±§Y¥i¡C</para>
 
           <para>moused ¦b°õ¦æ¤¤ªº®É­Ô¡A¦pªG­n¨Ï¥Î·Æ¹«¬ÛÃö¥\¯à¡A³£¥²¶·³z¹L moused 
 	    ©Î¨ä¥Lµ{¦¡¹³¬O X µøµ¡¨Ó¶i¦æ¡C½Ð°Ñ¾\ FAQ ¤¤¦³Ãö<link
             linkend="x-and-moused">¡y¬°¤°»ò¤£¯à¦b X µøµ¡¸Ì¨Ï¥Î·Æ¹«¡H¡z</link>¥HÁA¸Ñ¬ÛÃö²Ó¸`¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="text-mode-cut-paste">
           <para>¦b¤å¦r¼Ò¦¡ªº console Àô¹Ò­n«ç»ò¥Î·Æ¹«¨Ó°Å¶K¤å¦r©O¡H</para>
         </question>
 
         <answer>
           <para>·í°õ¦æ moused «á¡A(°Ñ¾\<link linkend="moused">«e¤@¸`</link>)
 	    «ö¦í¥ªÁä¡A±µµÛ²¾°Ê·Æ¹«¨Ó¿ï¾Ü¤@­Ó°Ï°ì¤§«á©ñ¶}¡A³o¼Ë´N§¹¦¨¡y½Æ»s¡z¡C
 	    ­n¡y¶K¤W¡zªº¸Ü¡A«ö·Æ¹«¤¤Áä´N¥i¥H¤F¡C
 	    ­n¡y©µ¦ù¿ï¨ú°Ï¡zªº¸Ü¡A«ö·Æ¹«¥kÁä</para>
 
 
 	  <para>¦pªG§Aªº·Æ¹«¨S¦³¤¤Áä¡A§A¥i¥H¥Î¼ÒÀÀªº¤è¦¡¡A©Î¬O­«·s©w¸q·Æ¹««öÁ䪺¤è¦¡¡A
 	    ¨Ó¹F¦¨¡u©µ¦ù¡vªº¥\¯à¡C¸Ô±¡½Ð°Ñ¾\ &man.moused.8; »¡©ú¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="mouse-wheel-buttons">
           <para>§Ú·Æ¹«¤W­±ªººu½ü¡Bºu½ü«ö¶s¡A¥i¥H¦b console ¤W¨Ï¥Î¶Ü¡H</para>
         </question>
 
         <answer>
 	  <para>³o­Óµª®×¹À...¡A«Ü¤£©¯¦a¡A¦b¤j¦h¼Æªº±¡ªp¤U¤£¦æ¡C
 	    ³o¨Ç¦³ºu½üªº·Æ¹«»Ý­n¥Î¯S®íÅX°Êµ{¦¡¤~¦æ¡A
 	    °£«D¡A·Æ¹«ÅX°Êµ{¦¡©Î¨Ï¥ÎªÌ¦Û¤vªºÀ³¥Îµ{¦¡¦³¤ä´©¡A
 	    ¤£µM¡A³o¨Ç·Æ¹«¥u¯à°÷·í¦¨¬O´¶³qªº¨âÁä©Î¤TÁ䪺·Æ¹«¨Ó¥Î¦Ó¤w¡C
             </para>
 
           <para>¦pªG­n¦b X µøµ¡Àô¹Ò¤W¨Ï¥Îºu½üªº¸Ü¡A½Ð°Ñ¾\
             <link linkend="x-and-wheel"> X µøµ¡¤Wªººu½ü¨Ï¥Î
             </link>»¡©ú¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="laptop-mouse-trackball">
           <para>­n«ç»ò¦bµ§°O«¬¹q¸£¤W¨Ï¥Î·Æ¹«¡B­y¸ñ²y¡BIJ±±ªO©O¡H</para>
         </question>
 
         <answer>
           <para>½Ð°Ñ¾\<link linkend="ps2mouse">«e­±ªº PS/2 ·Æ¹«ªº°Ýµª
             </link>¡C</para>
         </answer>
       </qandaentry>
 
 	</qandaset>
 
       </sect1>
 
       <sect1 id="compatibility-networking">
 	<title>ºô¸ô¸ò serial ³]³Æ</title>
 
 	<qandaset>
 
       <qandaentry>
         <question id="network-cards">
           <para>FreeBSD ¤ä´©­þ¨Çºô¸ô¥d©O¡H</para>
         </question>
 
         <answer>
           <para>½Ð°Ñ¦Ò &os; ¦Uª©¥»ªºµwÅé¤ä´©¦Cªí¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="internal-plugnplay-modem">
           <para>¬°¤°»ò FreeBSD §ä¤£¨ì PnP(ÀH´¡ÀH¥Î¡APlug &amp; Play)³W®æªº modem?</para>
         </question>
 
         <answer>
           <para>­ì¦]¦b©ó¡G»Ý­n§â modem ªº PnP ID ¥[¨ì serial ÅX°Êµ{¦¡ªº PnP ID ªí¡A§@ªk¦p¤U¡G
 	    <orderedlist>
 	      <listitem>
 	        <para>­º¥ý¡A¦b kernel ³]©wÀɤº¥[¤J <literal>controller pnp0</literal>¡A
 	           ¨Ã­«·s½sĶ¡B¦w¸Ë kernel¡A³Ì«á­«¶}¾÷´N·|±Ò°Ê PnP ¤ä´©¡C</para>
 	      </listitem>
 
 	      <listitem>
 	        <para>µM«á¡Akernel ·|§â°»´ú¨ì©Ò¦³³]³Æ¤Wªº PnP ID ³£¦C¥X¡C
 	          ³o®É¡A­×§ï <filename>/usr/src/sys/isa/sio.c</filename>(¤j¬ù²Ä752¦æ¥ª¥kªº¦a¤è)¡A
 	          ¥i¥H·j´M <literal>SUP1310</literal> ·íÃöÁä¦r(¦ì©ó <literal>sio_ids[]</literal> ªí¤º)¡A
 	          ½Ð±N­è¤~ kernel Åã¥Üªº modem ªº PnP ID ½Æ»s¨ì¬ÛÃö¦ì¸m¡C</para>
 	      </listitem>
 
 	      <listitem>
 	        <para>³o®É¡A¦A­«·s½sĶ¡B¦w¸Ë kernel¡A³Ì«á­«¶}¾÷À³¸Ó´N·|¥¿½T°»´ú¨ì modem ¤F¡C</para>
 	      </listitem>
 	    </orderedlist>
 
           <para>¦¹¥~¡A¤]¥i¥H¦b¶}¾÷®É¥H <literal>pnp</literal> «ü¥O¨Ó¤â°Ê³]©w PnP ³]³Æ¡A
 	     ¨ÓÅý kernel ±o¥H¥¿½T°»´ú¡AÁ|¨Ò¡G</para>
 
           <programlisting>pnp 1 0 enable os irq0 3 drq0 0 port0 0x2f8</programlisting>
 
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="support-winmodem">
           <para>FreeBSD ¤ä´©¹³¬O Winmodems ¤§Ãþªº³nÅé modem ¶Ü¡H</para>
         </question>
 
         <answer>
           <para>FreeBSD ¥i¥H¦w¸ËÃB¥~ªº³nÅé¨Ó¤ä´©³nÅé modem¡C
             ¹³¬O <filename role="package">comms/ltmdm</filename> ¥i¤ä´©±`¨£ªº Lucent LT ´¹¤ù¡A
 	    <filename role="package">comms/mwavem</filename> «h¥i¤ä´© IBM Thinkpad 600 ¤Î 700
 	    µ§°O«¬¹q¸£¤W­±ªº modem¡C</para>
 
           <para>µM¦Ó¡A¨Ã¤£¯à¥Î³nÅé modem ¨Ó¦w¸Ë FreeBSD¡A
 	    ¦]¬°¡G³oÃþ³nÅ饲¶·¦b§@·~¨t²Î¦w¸Ë§¹²¦¤§«á¡A¤~¯à¦w¸Ë¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
 	<question id="support-broadcom">
 	  <para>¦³ Broadcom 43xx µL½uºô¥dªº­ì¥ÍÅX°Êµ{¦¡(Native driver)¶Ü¡H</para>
 	</question>
 
 	<answer>
 	  <para>¨S¦³¡A¦Ó¥B¤]¤£¤Ó¥i¯à·|¦³¡C</para>
 
 	  <para>Broadcom ©Úµ´¤½¶}¦³ÃöµL½uºô¥d´¹¤ùªºÅX°Êµ{¦¡¬ÛÃö»¡©ú¡A
 	    ¥D¦]¤j·§¬O¥L­Ì¥Î³nÅé¨Ó±±¨îµL½u¶Ç¿é¤è¦¡¡C
 	    ¨Æ¹ê¤W¡A¦]¬°­n¯à³q¹L¬ü°êÁp¨¹¹q«H©e­û·|(FCC)À˺Ϧw³Wªº¸Ü¡A
 	    ¥²¶·½T«O²£«~¤£¯àÅý¨Ï¥ÎªÌ¤£¯àÀH·N§ó°Ê¬ÛÃö³]©w¡A¤ñ¦p¡G¹qºÏªiÀW²v¡B¬ÛÃö¼Ò²Õ°Ñ¼Æ¡B¿é¥X¹q·½µ¥¡C
 	    ¦ý¬O¡A¦pªG§Ú­Ì¤£ª¾¹D¦p¦ó¥h±±¨î´¹¤ùªº¸Ü¡A¨º»ò¼¶¼gÅX°Êµ{¦¡¤§¸ô®£©È¤£¤Ó¥i¦æ¡C</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
         <question id="multiport-serial-support">
           <para>FreeBSD ¤ä´©­þ¨Ç multi-port serial¥d©O¡H</para>
         </question>
 
         <answer>
           <para>½Ð°Ñ¾\¨Ï¥Î¤â¥U¤Wªº <ulink
 	    url="&url.books.handbook;/install.html#INSTALL-MISC">¦w¸Ë½g¡X¨ä¥LµwÅé
             </ulink> ¦Cªí¡C</para>
 
           <para>ÁöµM¦³¨Ç¥d¬O¨SµPªº(¤×¨ä¬O¦³¼Ð©ú¡G¬Û®e AST ³W®æ)¦ý¤]¥i¥H¥¿±`¨Ï¥Î¡C</para>
 
           <para>¦Ü©ó¥dªº³]©w¤è­±¡A½Ð°Ñ¾\ &man.sio.4; ªº»¡©ú¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="serial-console-prompt">
           <para>¦b serial console ¤W­n¦p¦ó¤~·|¥X²{ boot: ´£¥Ü©O¡H</para>
         </question>
 
         <answer>
             <orderedlist>
               <listitem>
                 <para>kernel ³]©wÀÉ¥[¤J
                   <literal>options COMCONSOLE</literal></para>
               </listitem>
 
               <listitem>
                 <para>«Ø¥ß /boot.config ÀÉ¡A¨Ã¥B¸ÓÀɸ̭±¤º®e¥u¶ñ¤W <option>-P</option></para>
               </listitem>
 
               <listitem>
                 <para>§âÁä½L±q¾÷¾¹¤W©Þ±¼</para>
               </listitem>
             </orderedlist>
 
           <para>²Ó¸`½Ð¬Ý
             <filename>/usr/src/sys/i386/boot/biosboot/README.serial</filename>
             </para>
         </answer>
       </qandaentry>
 
 	</qandaset>
 
       </sect1>
 
       <sect1 id="compatibility-sound">
 	<title>­µ®Ä¥d</title>
 
 	<qandaset>
 
       <qandaentry>
         <question id="sound-card-support">
           <para>FreeBSD ¤ä´©­þ¨Ç­µ®Ä¥d¡H</para>
         </question>
 
         <answer>
           <para>&os; ¤ä´©¦UºØ­µ®Ä¥d¡A¥]¬A¤F &soundblaster;¡B
 	    &soundblaster; Pro¡B&soundblaster; 16¡BPro Audio Spectrum 16¡B
             AdLib¡B¤Î Gravis UltraSound sound cards (²Ó¸`½Ð°Ñ¾\
             <ulink url="&url.base;/releases/">&os; µo¦æ±¡³ø</ulink>
             ¥H¤Î &man.snd.4; ªº»¡©ú)¡C
             ¦¹¥~¡A¹ï MPU-401 ¤Î MIDI ¬Û®e³W®æªº¤]¦³¤@©wµ{«×ªº¤ä´©¡A¦Ó
             &microsoft; Sound System ³W®æ¤]¦³¤ä´©¡C</para>
 
             <note>
               <para>ÅX°Êµ{¦¡¶È¾A¥Î©ó¡y­µ®Ä¡z³¡¤À¡I °£¤F &soundblaster; ¤§¥~¡A
 	        ¥Ø«e­µ®ÄÅX°Êµ{¦¡¨Ã¤£¤ä´©³o¨Ç­µ®Ä¥d¤Wªº¥úºÐ¾÷, SCSI³]³Æ©Î·n±ì¡C
 	        &soundblaster; ªº SCSI ¤¶­±¤Î¬Y¨Ç«D SCSI ªº¥úºÐ¾÷¬O¦³¤ä´©¡A¦ýµLªk¥Î¨Ó¶}¾÷¡C
 		</para>
              </note>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="es1370-silent-pcm">
           <para>&man.pcm.4; ©Ò¤ä´©ªº­µ®Ä¥d¨S¦³Án­µ¡A¦³¤°»ò¼È®É¸Ñ¨M¤è¦¡¶Ü¡H</para>
         </question>
 
         <answer>
           <para>¦]¬°¦³¨Ç¹³¬O es1370 ´¹¤ùªº­µ®Ä¥d·|¦b¨C¦¸¶}¾÷®É§â­µ¶q½Õ¬°¹s¡C
 	    ¼È®É¸Ñªk¬O¦b¨C¦¸¶}¾÷®É°õ¦æ¤U­±«ü¥O¡A©Î¬O¥[¨ì /etc/rc.local ¤º¡G</para>
 
           <screen>&prompt.root; <userinput>mixer pcm 100 vol 100 cd 100</userinput></screen>
         </answer>
       </qandaentry>
 
 	</qandaset>
 
       </sect1>
 
       <sect1 id="compatibility-other">
 	<title>¨ä¥LµwÅé</title>
 
 	<qandaset>
 
       <qandaentry>
         <question id="other-device-support">
           <para>FreeBSD Á٤䴩¨ä¥L­þ¨ÇµwÅé©O¡H</para>
         </question>
 
         <answer>
           <para>½Ð°Ñ¾\¨Ï¥Î¤â¥U¤Wªº <ulink 
 	    url="&url.books.handbook;/install.html#INSTALL-MISC">¦w¸Ë½g¡X¨ä¥LµwÅé</ulink>
             ¡C</para>
 
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="power-management-support">
           <para>FreeBSD ¤ä´©µ§°O«¬¹q¸£ªº¬Ù¹qºÞ²z¥\¯à¶Ü¡H</para>
         </question>
 
         <answer>
           <para>FreeBSD 4.X(§t¤§«áª©¥»)¦b¬Y¨Ç¾÷ºØ¤W³£¦³¤ä´© <acronym>APM</acronym>¡C
             ²Ó¸`½Ð°Ñ¾\ &man.apm.4; ªº»¡©ú¡C</para>
 
 	  <para>FreeBSD 5.X(§t¤§«áª©¥»)¤ä´©¦b¥Ø«e¤j³¡¤À¾÷ºØ¤W³£¦³ªº
 	    <acronym>ACPI</acronym> ¥\¯à¡C
 	    ²Ó¸`½Ð°Ñ¾\ &man.acpi.4; ªº»¡©ú¡C­Y¾÷¾¹¤W¦P®É³£¦³ <acronym>APM</acronym> 
 	    ¤Î <acronym>ACPI</acronym> ¥\¯àªº¸Ü¡A§Ú­Ì«Øij§A¥i¥H¨âªÌ³£¸Õ¸Õ¬Ý¡A
 	    ¬Ý¬Ý­þ¤@ºØ¤ñ¸û²Å¦X§Aªº»Ý¨D¡C</para>
 
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="disable-acpi">
           <para>¸Ó¦p¦óÃö³¬ ACPI¡H</para>
         </question>
 
         <answer>
           <para>§â <screen>hint.acpi.0.disabled="1"</screen>
 		³o¬q¥[¨ì <filename>/boot/device.hints</filename> §Y¥i¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="micron-hang-boot">
           <para>Micron ¹q¸£Á`¬O¦b &os; ±Ò°Ê®É´N±¾±¼¡A¸Ó«ç»ò¿ì©O¡H</para>
         </question>
 
         <answer>
           <para>¦³¨Ç Micron ¥D¾÷ªO¤Wªº BIOS ¦b PCI ¤è­±·|¦³°ÝÃD¡A
 	    ³o·|¾É­P PCI ³]³Æ·|³Q BIOS °»´ú¬°¤£¥¿½T³]©w¡A¦Ó¶i¤J FreeBSD ´N±¾±¼¡C</para>
 
           <para>¼È®É¸Ñ¨M¤è¦¡¡GÃö³¬ BIOS ¤º <quote>Plug and Play Operating System</quote>
             ªº³]©w¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="micron-3comnic-failure">
           <para>&tm.3com; PCI ¤¶­±ºô¸ô¥dµLªk¦b Micron ¹q¸£¤W¨Ï¥Î¡A¸Ó«ç»ò¿ì¡H</para>
         </question>
 
         <answer>
           <para>³o°ÝÃD¸ò«e­±ªº°ÝÃD¦]¯À¤@¼Ë¡AÁ`¤§¡A´N¬OÃö³¬ BIOS ¤¤¦³Ãö OS PnP ªº³]©w¡C</para>
 
           <para>¼È®É¸Ñ¨M¤è¦¡¡GÃö³¬ BIOS ¤º <quote>Plug and Play Operating System</quote>
             ªº³]©w¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="asusk7v-boot-failure">
           <para>¥D¾÷ªO¬O¥ÎµØºÓ(ASUS) K7V¡A¥i¬O¥Î¶}¾÷¤ù¶}¨ì¤@¥b´N·í¤F¡A«ç»ò¿ì©O¡H</para>
         </question>
 
         <answer>
           <para>¶i¤J BIOS ³]©w¡A¨ÃÃö³¬ <quote>boot virus protection</quote> ³]©w§Y¥i¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
 	<question id="newcard-does-not-work">
-	  <para>My PCMCIA card does not work. I have a message:
+	  <para>PCMCIA ¥dµLªk¨Ï¥Î¡A¨Ã¥X²{¿ù»~°T®§
 	    <quote>cbb0: unsupported card type detected.</quote>
-	    What can I do?</para>
+	    ¸Ó«ç»ò¿ì¡H</para>
 	</question>
 
 	<answer>
-	  <para>You can try to use the original OLDCARD implementation.  Edit
-	    your kernel configuration file and remove the following lines:
+	  <para>¥i¥H¸Õ¸Õ¬Ý§ï¥Îªº¤è¦¡¡A½Ð¥ý­×§ï kernel ³]©wÀÉ¡A®³±¼¤U­±³o´X¦æ¡G
 	    <programlisting>device cbb
 device pccard
 device cardbus</programlisting>
-	    Then add:
+	    µM«á¥[¤W¡G
 	    <programlisting>device pcic
 device card 1</programlisting>
-	    Rebuild and install the new kernel as described in
-	    <ulink url="&url.books.handbook;/kernelconfig.html">Configuring
-	    the FreeBSD Kernel</ulink>.</para>
+	    ³Ì«á½Ð°Ñ¾\ Handbook ¤¤
+	    <ulink url="&url.books.handbook;/kernelconfig.html">½Õ¾ã FreeBSD Kernel</ulink> 
+	    ³¹¸`¡A¥H­«·s½sĶ¡B¦w¸Ë·sªº kernel¡C</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
         <question id="dell-poweredge-failure">
           <para>¬°¤°»ò &dell; &poweredge; 2850 ¸Ë§¹ FreeBSD ¤§«á¡A­«¶}¾÷±µµÛÁä½L´N±¾¤F¡H</para>
         </question>
 
         <answer>
           <para>(¥»ÃD¥Ñ cdsheen ´£¨Ñ)À|¸Õ¦b &dell; &poweredge; 2850 ¤W­±¦w¸Ë &os; 6.0¡A
 	    ¤£¹L¦w¸Ë§¹¦¨¡B¨Ã­«·s¶}¾÷¤§«á¡Aµo²{ console ªºÁä½L¤£¯à°Ê¤F¡A
 	    ¦P¼Ëªº±¡ªp¦ü¥G¤]¦s¦b©ó &os; 5.3 ¤Î &os; 5.4¡A
 	    ¸g¹L¤@µf·j´M¡Aµoı¬O¦]¬°³o¥x¾÷¾¹¤W­±¦³¤@­Ó <quote>Dell Remote Access Controller (DRAC)</quote>¡A
 	    ³o­Ó¸Ë¸m·|³Q¨t²Î¿ëÃѦ¨¤@­Ó USB Keyboard¡A©Ò¥H¾É­P¶}§¹¾÷¤§«á¡A¥¿±`ªº PS/2 Áä½L¤Ï¦Ó¤£¯à°Ê¤F¡I</para>
 
 	  <para>¼È®É¸Ñ¨M¤è¦¡¦p¤U¡G</para>
 
             <orderedlist>
               <listitem>
                 <para>¥ý¥H Single User Mode ¶i¤J¨t²Î</para>
               </listitem>
 
               <listitem>
                 <para>¦b©R¥O¦C¼Ò¦¡¤U¡A¥ý°õ¦æ¤U¦C©R¥O¡G</para>
 		  <screen>&prompt.root; <userinput>fsck -y <filename>/</filename></userinput></screen>
 	          <screen>&prompt.root; <userinput>mount -u <filename>/</filename></userinput></screen>
               </listitem>
 
               <listitem>
                 <para>µM«á½s¿è <filename>/etc/devd.conf</filename>¡A§â¹ï©ó USB Keyboard ªº¤ä´©¼È®É®³±¼¡A
 	          ¤]´N¬O§â¤U­±´X¦æ¶}ÀY¥[¤W #</para>
 	        <programlisting>
 # When a USB keyboard arrives, attach it as the console keyboard.
 #attach 100 {
 #       device-name "ukbd0";
 #       action "kbdcontrol -k /dev/ukbd0 < /dev/console && /etc/rc.d/syscons restart";
 #};
 #detach 100 {
 #       device-name "ukbd0";
 #       action "kbdcontrol -k /dev/kbd0 < /dev/console";
 #};
 </programlisting>
               </listitem>
 
               <listitem>
                 <para>µM«á¿é¤J <command>exit</command>Â÷¶} Single User Mode ¤§«á¡A
 	          ´N¥i¥H¶¶§Q¶i¤J¨t²Î¡B¦Ó¥BÁä½L¤]¥i¥H¥¿±`¹B§@¡A¤U¦¸¶}¾÷¤]¤£·|¦³°ÝÃD¡I</para>
               </listitem>
             </orderedlist>
 
           <para>¥t¥~¡A&dell; ªº DRAC/BMC ¬Ý°_¨Ó¦³ÆZ¦h¤£¿ùªº»·ºÝ¦s¨ú¥\¯à¡A¦³¿³½ìªº¤H¥i¥Hª±ª±¬Ý...</para>
         </answer>
       </qandaentry>
     </qandaset>
 
       </sect1>
 
   </chapter>
 
   <chapter id="troubleshoot">
     <chapterinfo>
       <author>
 	<firstname>William</firstname>
         <surname>Liao</surname>
         <affiliation>
           <address><email>chliao@tpts4.seed.net.tw</email></address>
         </affiliation>
       </author>
     </chapterinfo>
 
     <title>±`¨£°ÝÃD¸Ñ¨M</title>
 
     <qandaset>
       <qandaentry>
         <question id="awre">
-          <para>§ÚªºµwºÐ¦³Ãa­y®É¸Ó«ç»ò¿ì?</para>
+          <para>µwºÐ¦³Ãa­y®É¸Ó«ç»ò¿ì?</para>
         </question>
 
         <answer>
           <para>­Y¬O SCSI µwºÐªº¸Ü¡A¨º»òºÏºÐ¾÷À³¸Ó¦³¯à¤O¦Û°Ê§@ re-mapping 
             ªº°Ê§@¡CµM¦Ó¡A¦]¬°¤@¨Ç¥¼ª¾ªº¦]¯À¡A¦b¥X¼t®É¡A«Ü¦hµwºÐªº³o¶µ
             ¥\¯à¬OÃö³¬ªº...</para>
 
           <para>­n±N¨ä­«·s¶}±Ò¡A±z»Ý­n½s¿è¸Ë¸mªº²Ä¤@­Ó page ¼Ò¦¡
             ¡]first device page mode¡^¡A¦b FreeBSD ¤W¥i¥H¥Î¤U­±ªº«ü¥O¿ì¨ì
             ¡]¥H <username>root</username>¨­¤À°õ¦æ¡^</para>
 
           <screen>&prompt.root; <userinput>scsi -f /dev/rsd0c -m 1 -e -P 3</userinput></screen>
 
           <para>µM«á±N AWRE ©M ARRE ªº¼Æ­È±q 0 Åܦ¨ 1:-</para>
 
           <programlisting>AWRE¡]Auto Write Reallocation Enbld¡^¡G 1
 ARRE¡]Auto Read Reallocation Enbld¡^¡G 1</programlisting>
 
           <para>¥H¤U³o¬q¬O¥Ñ Ted Mittelstaedt
             <email>tedm@toybox.placo.com</email>©Ò´£¨Ñ¡G</para>
 
           <para>­Y¬° IDE µwºÐ¡A¥ô¦óªºÃa­y³q±`³£¬O³Â·Ðªº¹w¥ü¡C¥Ø«e©Ò¦³¸û·sªº
             IDE µwºÐ¡A¤º³¡³£¦³¦Û°Ê remapping Ãa­yªº¯à¤O¡C¥Ø«e©Ò¦³ IDE µwºÐ
             »s³y°Ó¡A³£´£¨Ñ¤F§ó¤[ªº«OÃÒ¡A¦Ó¥B·|À°±z§ó´«¥X²{Ãa­yªºµwºÐ¡C</para>
 
           <para>¦pªG±z¤´·Q­n­×´_²£¥ÍÃa­yªº IDE µwºÐ¡A±z¤´¥i¥H¸ÕµÛ¥h¤U¸ü IDE 
             µwºÐ»s³y°Ó©Ò´£¨ÑªºÀË´úµ{¦¡¡A¨Ã¥Î¥¦¨ÓÀˬd±zªºµwºÐ¡C¦³®É³o¨Ç³nÅé¥i
             ¥H±j­¢­«·sÀˬdµwºÐªºÃa­y¡A¨Ã±N¥¦­Ì¼Ð¥Ü¥X¨Ó¡C</para>
 
           <para>¹ï ESDI¡ARLL ¤Î MFM ªºµwºÐ¨Ó»¡¡A³q±`Ãa­y¬O¥¿±`²{¶H¡A¤]¤£¬O¤°
             »ò³Â·Ðªº«e¥ü¡C¦b PC ¤W¡AºÏºÐ±±¨î¥d©M BIOS ­t³d¼Ð¥ÜÃa­yªº¥ô°È¡C³o
             ¹ï¤@¨Ç¨Ï¥Î BIOS¨Ó¦s¨úºÏºÐªº§@·~Àô¹Ò¡]¦p DOS¡^¬O¨S¦³°ÝÃDªº¡CµM¦Ó¡A
             FreeBSD ªººÏºÐÅX°Êµ{¦¡¨Ã¤£¸g¹L BIOS ¨Ó¦s¨úºÏºÐ¡A©Ò¥H¡A¦³­Ó bad144 
             ªº¾÷¨î¥Î¨Ó¨ú¥N³o¶µ¥\¯à¡Cbad144 ¥u¯à¥Î¦b wd ³o­ÓºÏºÐÅX°Êµ{¦¡¤W¡]³o
             ­Ó¥Nªí¤F FreeBSD 4.0 ¨Ã¤£¤ä´©¥¦¡^¡A¥¦¤]µLªk¥Î¦b SCSI µwºÐ¤W¡C
             bad144ªº¤u§@¤èªk¬O±N©Ò¦³§ä¨ìªºÃa­y¸ê®Æ¦s¨ì¤@­Ó¯S§OªºÀÉ®×ùØ¡C</para>
 
           <para>¨Ï¥Î bad144 ªºÄµ§i - ¦sµÛÃa­y¸ê®Æªº¯S§OÀɮ׬O©ñ¦bµwºÐªº³Ì«á
             ¤@­y¤W¡C¦]¬°³o­ÓÀÉ®×Àx¦sªºÃa­y¸ê®Æ¤¤¡A¦³¥i¯à¦³¨Ç¸ê®Æ¬O«ü¦VµwºÐ³Ì
             «eºÝ©Òµo¥ÍªºÃa­y±¡§Î¡A´N¬O¥i¯àÀx¦s /kernel ³o­ÓÀɪº¦a¤è¡A©Ò¥H¥¦
             ¤@©w­n¯à³Q¶}¾÷µ{¦¡©ÒŪ¨ú¡A¦Ó¶}¾÷µ{¦¡¬O³z¹L BIOS ¨ÓŪ¨ú kernel 
             ÀÉ¡C³oªí¥Ü¤F¨Ï¥Î bad144 ªºµwºÐµ´¤£¯à¾Ö¦³¶W¹L 1024 ­Ó cylinder¡A
             16 ­Ó head ¤Î 63 ­Ó sector¡C¦Ó³o¨Ï±o±ý¨Ï¥Î bad144 ªºµwºÐªº¤j¤p¤£
             ¯à¤j©ó 500 MB¡C</para>
 
           <para>­n¨Ï¥Î bad144 «Ü²³æ¡A¥u­n¦b¶}©l¦w¸Ë®É¡A¦b FreeBSD fdisk µe­±
             §â<quote>Bad Block</quote> ±½ºË³]¬° ON §Y¥i¡C¦b FreeBSD 2.2.7 ¥H
             «á³£¥i¥H¨Ï¥Î¦¹¤èªk¡C¦ý³o­ÓµwºÐªº cylinder ¤@©w­n¦b 1024 ¥H¤U¡C¨Ï
             ¥Î«e¡A§Ú­Ì«Øij³o­ÓµwºÐ­n¦Ü¤Ö¥ý¨Ï¥Î¥|­Ó¤p®É¡A¥H«K¼ö¿±µÈ»PºÏ­y°¾²¾
             ¹F¤@¯ëª¬ºA¡C</para>
 
           <para>¦pªG³o­ÓµwºÐ¾Ö¦³¶W¹L 1024 ­Ó cylinder¡]¹³¤j®e¶qªº ESDI µwºÐ¡^
             ¡AESDI ±±¨î¥d§Q¥Î¤@­Ó¯S§OªºÂà´«¼Ò¦¡¨Ï¥¦¯à¦b DOS ¤U¤u§@¡C¦Ó¦pªG±z
             ¦b fdisk ùتº <quote>set geometry</quote> ¤¤¿é¤J
 	    <quote>Âà´«¹L</quote> ªº geometry¡Awd ³o­ÓÅX°Êµ{¦¡¯à¤F¸Ñ³o¨ÇÂà´«
 	    ¼Ò¦¡¡C±z¤]µ´¹ï¤£¯à¨Ï¥Î dangerously dedicated ¼Ò¦¡¨Ó«Ø¥ß FreeBSD
 	    ªº¤À³Î°Ï¡A¦]¬°¥¦·|©¿²¤ geometry ³o­Ó°Ñ¼Æ¡C¦¹¥~¡A´Nºâ fdisk ¨Ï¥Î
 	    ±z©Ò¿é¤Jªº geometry °Ñ¼Æ¡A¥¦¨ÌµM·|¥hŪ¨ú³oµwºÐªº¯u¥¿¸ê®Æ¡A¦Ó·|¹Á
 	    ¸Õ¥h«Ø¥ß¤@­Ó¹L¤jªº FreeBSD ¤À³Î°Ï¡C¦pªGºÏºÐªº geometry ¤w¸g³Q
 	    <quote>Âà´«</quote> ¹L¤F¡A¨º»ò ³o­Ó¤À³Î°Ï <quote>¥²¶·</quote>
 	    ¥H¤â°Ê¿é¤J block ¼Æ¥Øªº¤èªk¨Ó«Ø¥ß¡C</para>
   
           <para>¤@­Ó§Ö³tªº¤p§Þ¥©¬O§Q¥Î ESDI ±±¨î¥d¨Ó³]©w¤j®e¶qªº ESDI µwºÐ¡A
             ¥Î DOS ¶}¾÷¤ù¶}¾÷¡A¦A±N¥¦ format ¬° DOS ªº¤À³Î°Ï¡CµM«á­«¶}¾÷¶i¤J
             FreeBSD ¦w¸Ëµ{§Ç¡A¦b fdisk µe­±¡A§âDOS ¤À³Î°Ïªº blocksize ©M 
             block number §Û¤U¨Ó¡CµM«á­«·s³]©w geometry ¨Ï¨ä¸ò DOS ¨Ï¥Îªº¤@¼Ë¡C
             §R°£ DOS ¤À³Î°Ï¡AµM«á¨Ï¥Î±z­è­è§Û¤Uªº blocksize ¨Ó«Ø¥ß¤@­Ó
             <quote>cooperative</quote> FreeBSD ¤À³Î°Ï¡CµM«á³]©w³o­Ó¤À³Î°Ï¬°¥i
             ¶}¾÷¡A¦A¥´¶}Ãa­y±½ºË¡C¦b¯u¥¿ªº¦w¸Ë¹Lµ{¤¤¡Abad144 ·|¦b¥ô¦óÀɮרt²Î
             ³Q«Ø¥ß«e¥ý³Q°õ¦æ¡C¡]±z¥i¥H«ö Alt-F2 ¨ÓºÊ¬Ý³o¤@¤Á¡^¦pªG¦b«Ø¥ßÃa­y¸ê
             ®ÆÀɮɵo¥Í¤F°ÝÃD¡A±z·|»Ý­n³]©w¤@­Ó¸û¤jªººÏºÐ geometry - ³oªí¥Ü±z
             »Ý­n­«¶}¾÷¡AµM«á¥þ³¡¦A­«·s¶}©l¡]¥]¬A­«·s¤À³Î¥H¤Î¦b DOS ¤U­«·s
             format¡^¡C</para>
 
           <para>¦pªG remapping ªº¥\¯à¤w¸g±Ò°Ê¤F¡A¦Ó±z¨ÌµM¤@ª½¬Ý¨ìÃa­y²£¥Í¡A
             ¨º»ò¦Ò¼{´«¤@¥xµwºÐ§a¡CÃa­yªº±¡§Î¥u·|ÀH®É¶¡¼W¥[¦Ó§ó¬°ÄY­«¡C</para>
         </answer>
       </qandaentry>
 
-      <qandaentry>
-        <question id="bustek742a-eisa-scsi">
-          <para>¬°¤°»ò FreeBSD §ì¤£¨ì§Úªº Bustek 742a EISA SCSI ¥d¡H</para>
-        </question>
-
-        <answer>
-          <para>¤U­±ªº¸ê°T¬Oµ¹ 742a ³o±i¥d¥Îªº¡A¦ý¬O¨ä¥L Buslogic ªº¥d©Î³\¤]
-            ¥i¥H¾A¥Î¡C¡]Bustek ´N¬O Buslogic¡^</para>
-
-          <para>742a ³o±i¥d¦³¨â­Ó¥D­nªº<quote>ª©¥»</quote>¡C¤@­Ó¬Oª©¥» A-G¡A
-            ¥t¤@­Ó¬Oª©¥» H ¤Î¨ä¥H«á¡Cª©¥»¸ê°T¥i¥H±q¤¶­±¥dÃä½tªº¬y¤ô¸¹³Ì«á­±
-            ±oª¾¡C742a ³o±i¥d¦³¨â­Ó°ßŪ´¹¤ù¦b¥¦¤W­±¡A¤@­Ó¬O BIOS ´¹¤ù¡A¦Ó¥t
-            ¤@­Ó¬O¶´Åé´¹¤ù¡C FreeBSD ¨Ã¤£¦b¥G±z¥d¤Wªº BIOS ª©¥»¡A¦ý¬O¶´Å骺
-            ª©¥»´N«Ü­«­n¤F¡C¦pªG§A¥´¹q¸Üµ¹¥L­Ì§Þ³N¤ä´©±M½uªº¸Ü¡A¥L­Ì·|±Hµ¹
-            ±z³Ì·sªºª©¥»¨Ñ±z¤É¯Å¡C BIOS ©M¶´Åé´¹¤ù¬O¤@°_°e¨Óªº¡C ±z»Ý­n±N¥d
-            ¤W BIOS ©M¶´Å骩¥»¡A¨Ì±z¥dª©¥»ªº¤£¦P¡A¤É¯Å¨ì³Ì·sªº¤@ª©¡C</para>
-
-          <para>ª©¥» A-G ªº¥d³Ì°ª¥u¯à±N BIOS/¶´Åé ¤É¯Å¨ì 2.41/2.21 ª©¡A¦Ó H
-	    ¤Î¨ä¤§«áªºª©¥»¡A¥Ø«e BIOS/¶´Å骺³Ì·sª©¥»¬O 4.70/3.37¡C³o¨â­Ó¶´Åé
-	    ª©¥»¶¡ªº®t²§¦b©ó¡A3.37 ³oª©¤ä´© <quote>round robin</quote></para>
-
-          <para>Buslogic ªº¥d¤W­±¤]³£¦³§Ç¸¹¡C¦pªG±z¥dªºª©¥»¸û¡A±z¥i¥H¸ÕµÛ¥´
-            ¹q¸Üµ¹ Buslogic ªºRMA ³¡ªù¡AµM«áµ¹¥L­Ì±zªº§Ç¸¹¡A¬Ý¯à¤£¯à¸ò¥L­Ì¥æ
-            ´«¤@±i¸û·sª©¥»ªº¥d¡C¦pªG¨º±i¥d°÷ªº¸Ü¡A¥L­Ì·|´«µ¹§A¡C</para>
-
-          <para>FreeBSD 2.1 ¥u¤ä´©¶´Åé 2.21 ª©¥H«áªºª©¥»¡C¦pªG±z¶´Å骩¥»¤ñ³o
-            ­ÓÁÙªº¸Ü¡A¨º»ò±zªº¥d´N¤£¯à³Q¿ëÃÑ¥X¬O Buslogic ªº¥d¡C¥¦¦³¥i¯à·|
-            ³Q¿ëÃѦ¨ Adaptec 1540¡C¸û¦­ªº Buslogic ¥d¤Wªº¶´Å馳¤@­Ó AHA1540 
-            <quote>¼ÒÀÀ</quote> ¼Ò¦¡¡A³o¹ï¤@±i EISA ¥d¨Ó»¡¨Ã¤£¬O¥ó¦n¨Æ¡C</para>
-
-          <para>¦pªG±z¦³¤@±i¸ûª©¥»ªº¥d¡A¦Ó±z¨ú±o 2.21 ª©¶´Å骺¸Ü¡A±z»Ý­nÀË
-            ¬d¤@¤U jumper W1 ªº¦ì¸m¡A±N¥¦½Õ¦Ü B-C¡A­ì©l³]©w¬O A-B¡C</para>
-        </answer>
-      </qandaentry>
-
       <qandaentry>
         <question id="hpnetserver-scsi-failure">
-          <para>¬°¤°»ò FreeBSD §ì¤£¨ì§Úªº HP Netserver ªº SCSI ±±¨î¥d¡H</para>
+          <para>¬°¤°»ò FreeBSD §ì¤£¨ì HP Netserver ªº SCSI ±±¨î¥d¡H</para>
         </question>
 
         <answer>
           <para>°ò¥»¤W³o­Ó¬O¤@­Ó¤wª¾ªº°ÝÃD¡C¦b HP Netserver ¾÷¾¹¤Wªº on-board
             EISA ¤¶­± SCSI ±±¨î¥d¥e¾Ú¤F©w§}¬°²Ä 11 ªº EISA ¼Ñ¡A¦]¦¹©Ò¦³ªº 
             <quote>¯u¹ê</quote> EISA ¼Ñ³£¦b¥¦¤§«e¡C¥i¬O¡A¦b EISA ©w§}ªÅ¶¡ 
             &gt;= 10 ®É¡A·|»P«ü©wµ¹ PCI ¥Îªº©w§}ªÅ¶¡¬Û½Ä¬ð¡A¥B FreeBSD ªº 
             auto-configuration µLªk¥¿½Tªº³B²z³o­Ó±¡§Î¡C</para>
 
           <para>¦]¦¹¡A²{¦b§A¯à°µªº³Ì¦n¨Æ±¡´N¬O¦b kernel ùس]©w
 	    <literal>EISA_SLOTS</literal> ³o­Ó¿ï¶µ¬° 12 ¡AµM«á·í§@¨S¦³³o­Ó
 	    °ÝÃD :)¡C½Ð¨Ì·Ó <ulink URL="../../handbook/kernelconfig.html">
 	    Handbook ¤¤¦³Ãö kernel ªº³]©w</ulink> ùØ©Ò»¡ªº¤èªk¨Ó³]©w»P½sĶ
 	    ±zªº kernel¡C</para>
 
           <para>·íµM¡A¦b¦w¸Ë FreeBSD ¨ì³oºØ¾÷¾¹¤W®É¡A³o¬O¤@­ÓÂû¥Í³J³J¥ÍÂûªº
             °ÝÃD¡C¬°¤F¸Ñ¨M³o­Ó°ÝÃD¡A¦b <emphasis>UserConfig</emphasis> ¤¤¦³
             ¤@­Ó¯S§Oªº¤èªk¡A¦w¸Ë®É¤£­n¶i¤J <quote>visual</quote> ¤¶­±¡A¬Û¤Ï
             ªº¡A¦b©R¥O¦C¼Ò¦¡¤¤¡AÁä¤J</para>
 
           <programlisting>eisa 12
 quit</programlisting>
 
           <para>µM«á´N¦p¥H©¹¤@¼Ë¦w¸Ë±zªº¨t²Î¡C¤£¹L§Ú­Ì«Øij±z½sĶ»P¦w¸Ë¤@­Ó
             ÄÝ©ó¦Û¤vªº kernel¡A¦ý</para>
 
           <para>§Æ±æ¦b¥¼¨Óªºª©¥»¤¤¯à¹ï³o­Ó°ÝÃD¦³¤@­Ó¦nªº¸Ñ¨M¤èªk¡C</para>
 
             <note>
               <para>±zµLªk¦b HP Netserver ¤W¨Ï¥Î
 	        <literal>dangerously dedicated</literal> ºÏºÐ¼Ò¦¡¡C±z¥i¥H°Ñ¦Ò
 		<link linkend="dedicate">³o¥÷µù¸Ñ</link> ¥HÀò±o§ó¦h¸ê°T¡C</para>
             </note>
         </answer>
       </qandaentry>
 
-      <qandaentry>
-        <question id="cmd640-ide">
-          <para>CMD640 IDE ±±¨î´¹¤ù¥X¤F¤°»ò°ÝÃD¡H</para>
-        </question>
-
-        <answer>
-          <para>¥¦ªº°ÝÃD¦b©óµLªk¦P®É³B²z¨â­Ó channel ªº«ü¥O¡C</para>
-
-          <para>²{¦b¤w¸g¦³­Ó¸Ñ¨M¤èªk¤F¡A¦Ó¥B¦b±zªº¨t²Î¤¤¦³³o¶ô´¹¤ù®É·|¦Û°Ê
-            ±Ò°Ê¡C¦pªG»Ý­n§ó¸ÔºÉªº¸ê°T¡A½Ð¬d¾\¦³ÃöºÏºÐÅX°Êµ{¦¡ªº»¡©ú
-	    ¡]man 4 wd¡^¡C</para>
-
-          <para>¦pªG±z¥Ø«e¬O¨Ï¥Î CMD640 IDE ±±¨î´¹¤ù¡A¥[¤W FreeBSD 2.2.1 ©Î
-            2.2.2¡A¦Ó¥B±z¤S·Q­n¨Ï¥Î¨ì²Ä¤G­Ó channel ®É¡A½Ð¦b±zªº kernel ³]
-            ©w¤¤¥[¤J <literal>options "CMD640"</literal> µM«á­«·s½sĶ¤@­Ó·s
-            ªº kernel¡C³o­Ó option ¦b 2.2.5 ª©¥H«á¬O¤º©w±Ò°Êªº¡C</para>
-        </answer>
-      </qandaentry>
-
       <qandaentry>
         <question id="ed1-timeout">
-          <para>§Ú¤@ª½¬Ý¨ìÃþ¦ü
+          <para>¤@ª½¬Ý¨ìÃþ¦ü
             <errorname>ed1: timeout</errorname> ªº°T®§¡C¥¦­Ì¬O¤°»ò·N«ä©O¡H
 	  </para>
         </question>
 
         <answer>
           <para>³o­Ó³q±`¬O¥Ñ©ó¤¤Â_½Ä¬ð¡]interrupt conflict¡^©Ò³y¦¨ªº¡]¨Ò¦p¡A
             ¨â¶ô¥d¨Ï¥Î¨ì¤F¬Û¦Pªº IRQ¡^¡C FreeBSD ¦b 2.0.5 ª©¥H«e³£®e³\³o­Ó
             ±¡§Î¡A´Nºâ¦³ IRQ ½Ä¬ð±¡§Î¡Aºô¸ô¥d¤]À³¸Ó¤´¥i¥¿±`¹B§@¡CµM¦Ó¡A¦b
             2.0.5 ª©¤Î¨ä¥H«á¡A¤w¤£¦A®e³\¦³ IRQ ½Ä¬ðªº±¡§Î¤F¡C½Ð©ó¶}¾÷®É¨Ï
             ¥Î -c ³o­Ó¿ï¶µ¡AµM«á§ó§ï ed0/de0/..¡Cµ¥ªº³]©w¡A¨Ï¨ä©M±zºô¸ô¥d
             ¥»¨­ªº³]©w¤@­P¡C</para>
 
           <para>¦pªG±z¬O¨Ï¥Î±zºô¸ô¥d¤Wªº BNC ±µÀY¡A±z©Î³\¤]·|¦]¤£¨}ªº²×ºÝ¹q
             ªý³]©w¡A¦Óµo¥Í¸Ë¸m (device) timeout ªº±¡§Î¡C­nÀˬd¬O§_¦³³oºØ±¡
             §Î¡A±z¥i¥H¦bºô¸ô¥d¤Wª½±µ±µ¤W²×ºÝ¹qªý¡]¤£­n±µºô¸ô½u¡^¡AµM«á¬Ý¬Ý³o
             ­Ó¿ù»~°T®§¬O¤£¬O´N®ø¥¢¤F¡C</para>
 
           <para>¦³¨Ç NE2000 ªº¬Û®e¥d¡A¦pªG¥¦ªº UTP °ð¨S¦³±µºô¸ô½u¡A©Î¬O¸Óºô
             ¸ô½u¨Ã¨S³Q¨Ï¥Îªº¸Ü¡A¤]·|¥X²{³o­Ó¿ù»~°T®§¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="bad-3c509">
-          <para>¬°¤°»ò§Úªº 3COM 3C509 ³o¶ôºô¸ô¥d¦b¨S¦³¥ô¦ó©úÅã­ì¦]¤U°±¤î¤u§@
+          <para>&tm.3com; 3C509 ºô¸ô¥d¦b¨S¦³¥ô¦ó©úÅã­ì¦]¤U°±¤î¤u§@
             ¤F©O¡H</para>
         </question>
 
         <answer>
           <para>³o¶ô¥d¦³­Ó¤£¦nªº¦a¤è¦b©ó¥¦±`±`·|¿ò¥¢¥»¨­ªº³]©w¸ê®Æ¡C½Ð¨Ï¥Î¸Ó
             ¥dªº DOS ¤u¨ã <command>3c5x9.exe</command> ¨Ó§ó·s¥d¤W³]©w¡C
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="printer-slow">
-          <para>§Úªº¥­¦æ°ð¦Lªí³t«×¯}¤Ñ¯îªººC¡C§Ú¸Ó«ç»ò°µ¡H</para>
+          <para>¥­¦æ°ð¦Lªí³t«×¯}¤Ñ¯îªººC¡A§Ú¸Ó«ç»ò°µ¡H</para>
         </question>
 
         <answer>
           <para>¦pªG°ß¤@ªº°ÝÃD´N¬O³t«×«ÜºCªº¸Ü¡A¸ÕµÛ§ïÅܱzªº <ulink
             url="../handbook/printing-intro-setup.html#PRINTING-PARALLEL-PORT-MODE">
             ¦Lªí¾÷³s±µ°ð³]©w</ulink> ³o­Ó¦b¤â¥U¤¤ªº
             <ulink url="../handbook/printing-intro-setup.html">¦Lªí¾÷³]©w
             </ulink> ³o­Ó³¹¸`¦³¥[¥H°Q½×¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="signal11">
-          <para>§Úªºµ{¦¡¦³®É·|¦]
+          <para>µ{¦¡¦³®É·|¦]
             <errorname>Signal 11</errorname> ³o­Ó¿ù»~¦Ó°±¤î¡H</para>
         </question>
 
         <answer>
           <para>Signal 11 ³o­Ó¿ù»~¬O¦]¬°§Aªº process ¹Á¸Õ­n¦s¨ú¤@¶ô°O¾ÐÅé¡A
             ¦Ó§Aªº§@·~¨t²Î¨Ã¤£¤¹³\¥¦°µ³o­Ó°Ê§@¦Óµo¥Íªº¡C¦pªG³oºØ±¡§Î±`±`¤£
             ©w®Éµo¥Í¡A¨º»ò§AÀ³¸Ó­n¶}©l¬Ý¬Ý¬O¤£¬O­þ¸Ì¥X°ÝÃD¤F¡C</para>
 
           <para>³o¨Ç°ÝÃD¥i¯à¬O»P¤U¦C±¡§Î¦³Ãö¡G</para>
 
           <orderedlist>
             <listitem>
               <para>¦pªG³o­Ó°ÝÃD¥u¦b¬Y¤@­Ó±z¦Û¤v¼gªº¬Y­Ó¯S©wµ{¦¡µo¥Í¡A¨º
                 »ò«Ü¦³¥i¯à¬O±zªºµ{¦¡½X¦³°ÝÃD¡C</para>
             </listitem>
 
             <listitem>
               <para>¦pªG³o­Ó°ÝÃD¬O¦b FreeBSD ªº¬Y¨Ç¨t²ÎÀÉ®×µo¥Í¡A¦³¥i¯à¬O
                 ¦]¬°µ{¦¡¦³°ÝÃD¡A¦ý³q±`¦b§Ú­Ì³o¸sŪ FAQ ªº¨Ï¥ÎªÌ¥h¶]³o¨Ç¦³
                 °ÝÃDªºµ{¦¡½X«e¡A¥¦­Ì¦­´N´N¤w¸g³Q¸Ñ¨M¤F¡]³o¬O -current ¦b°µ
                 ªº¨Æ¡^¡C</para>
             </listitem>
           </orderedlist>
 
           <para>¤×¨ä¦pªG§A¦b½sĶ¤@­Óµ{¦¡¡A¦ý¬O¨C¦¸½sĶ¾¹¶]¥X¨Óªºµ²ªG³£¤£¤@¼Ë
 	    ªº¸Ü¡A³o¬O¤@­ÓµL¸Ñªº°ÝÃD¡A¦Ó<emphasis>¤£¬O</emphasis>
 	    FreeBSD ¯äÂΡC</para>
 
           <para>Á|¨Ò¨Ó»¡¡A°²³]±z¥¿¦b¶] <quote>make buildworld</quote>¡A
 	    ¦Ó compiler ¦b±N <filename>ls.c</filename> ½sĶ¦¨
 	    <filename>ls.o</filename> ®Éµo¥Í¿ù»~¡A³o®É½Ð¦A¶]¤@¦¸
 	    <quote>make buildworld</quote>¡A¦pªG compiler ¨ÌµM¦b¦P¼Ëªº¦a¤èµo
 	    ¥Í°ÝÃD¡A¨º»ò´N¬Oµ{¦¡½X¦³°ÝÃD¡Ð¡Ð½Ð§ó·s­ì©l½XµM«á¦A¸Õ¸Õ¬Ý¡C¦Ó¦pªG
 	    compiler ¬O¦b¨ä¥Lªº¦a¤èµo¥Í¿ù»~¡A¨º»ò´X¥G¥i¥H½T©w¬OµwÅ骺°ÝÃD¤F¡C
           </para>
 
           <para>±z³o®ÉÀ³¸Ó°µ¤°»ò¡G</para>
 
           <para>¦pªG¬O²Ä¤@ºØ±¡§Î¡A¥i¥H¨Ï¥Î¤@¨Ç debugger¡A¦p¡Ggdb¡A¨Ó§ä¥Xµ{¦¡
 	    ¬O¦b¨º¨à·|¥h¹Á¸Õ¦s¨ú¿ù»~ªº°O¾ÐÅé¦ì§}¡AµM«á¦A­×¥¿¥¦¡C</para>
 
           <para>¦pªG¬O²Ä¤GºØ±¡§Î¡A´N»Ý­nÀˬd¬Ý¬Ý¬O¤£¬OµwÅ骺°ÝÃD¤F¡C</para>
 
           <para>¤@¨Ç³y¦¨µwÅ餣íªº­ì¦]¥]¬A¡G</para>
 
           <orderedlist>
             <listitem>
               <para>¥i¯à¬OµwºÐ¹L¼ö¡G½ÐÀˬd¾÷´ß¤ºªº­·®°¬O§_¹B§@¥¿±`¡A¦]¬°±z
 	        ªºµwºÐ¡]©ÎªÌÁÙ¦³¨ä¥LªºµwÅé¸Ë¸m¡^¹L¼ö¤F¡C</para>
             </listitem>
 
             <listitem>
               <para>³B²z¾¹¹L¼ö¡G³o­Ó¦³¥i¯à¬O¦]¬°¶WÀW¡A©ÎªÌ¬O³B²z¾¹ªº­·®°±¾¤F¡C
 	        ¤£½×¬O­þºØ­ì¦]¡A±z³£»Ý­n±N©Ò¦³ªº¤¸¥ó¦^´_¨ì¥¦­Ì­ì¥ý³]©wªº¤u§@ª¬
 		ºA¡A³o¼Ë¤~¯à¸Ñ¨M³o­Ó°ÝÃD¡CÁ|­Ó¨Ò¤l¨Ó»¡¡G±N³B²z¾¹½Õ¦^­ì¥ýªº¤u§@
 		ÀW²v¡C</para>
 
               <para>¦pªG±zÁÙ¬O°í«ù­n¶WÀWªº¸Ü¡A½ÐÂÔ°O¡A»P¨ä¿NÃa¦Ó»Ý­n´«·sªº¤@¥x
 	        ¥D¾÷¡A¤£¦p±N³t«×½ÕºC¤@ÂI¡I°£¦¹¤§¥~¡A¤£ºÞ§Aı±o¥¦¦w¤£¦w¥þ¡A¤@¯ë
 		¤H¹ï©ó±z¦]¬°¶WÀW¦Óµo¥Íªº°ÝÃD¡A¬O¤£·|¦³¤°»ò¦P±¡¤ßªº¡C</para>
             </listitem>
 
             <listitem>
               <para>¤£Ã­©wªº°O¾ÐÅé¡G¦pªG¥D¾÷¤W¦³¦w¸Ë¼Æ®Ú SIMM/DIMM °O¾ÐÅé¡A
 	        ¸ÕµÛ§â¥¦­Ì¥þ©î¤U¨Ó¡AµM«á¤@®Ú¤@®Ú´¡¤W¥h°µ´ú¸Õ¡AÂǦ¹ÁY¤p½d³ò¡A
 		¥H«K§ä¥X¦³°ÝÃDªº¬Y®Ú°O¾ÐÅé©Î¬O¬YºØ°O¾ÐÅé²Õ¦X¡C</para>
             </listitem>
 
             <listitem>
               <para>³Ì¨Î¤Æ¹LÀYªº¥D¾÷ªO³]©w¡G¦b BIOS ùةάO¦³¨Ç¥D¾÷ªOªº jumper
 	        ¤W¡A¦³®É¥i¥H§ó§ï¤@¨Ç timing¡A¦ý¦b¤j¦h¼Æªº±¡§ÎùØ¡A¨Ï¥Î¹w³]­È´N
 		¤w¸g¨¬°÷¤F¡Cªp¥B¦³®É­Ô§â RAM ªº wait states ³]¤Ó¤p¡A©Î¬O¦b
 		BIOS ùØ¡A§â <quote>RAM Speed: Turbo</quote> ³o­Ó©Î¬O¨ä¥LÃþ¦ü
 		ªº¿ï¶µ¥´¶}³£¦³¥i¯à·|³y¦¨¤@¨Ç¤£¥¿±`ªº²{¶H¡C¤@­Ó¸Ñ¨Mªº¤èªk¬O§â
 		BIOS ³]¦^¹w³]­È¡A¤£¹L¦b³o¤§«e°O±o¥ý°O¤U¥Ø«eªº³]©w¡I</para>
             </listitem>
 
             <listitem>
               <para>¨Ñµ¹¥D¾÷ªOªº¹q¤O¤£°®²b©Î¬O¤£¨¬¡C¸ÕµÛ§â¨t²Î¤º¨S¦³¥Î¨ìªº
 	        I/O ¥d¡DµwºÐ©Î¬O CDROM ¼È®É©î±¼©Î¬O©Þ±¼¹q·½½u¡A¬Ý¬Ý§Aªº¹q·½
 		¨ÑÀ³¾¹¬O¤£¬O¯à°÷¦b¤p¤@ÂIªº­t²ü¤U¥¿±`¤u§@¡C¤£µM´N¬O´«¤W¥t¤@
 		­Ó·sªº¹q·½¨ÑÀ³¾¹¡A³Ì¦n¬O¥Ë¼Æ°ª¤@ÂIªº¡]¥´­Ó¤ñ¤è¨Ó»¡¡A¦pªG­ì
 		¥ýªº¹q·½¨ÑÀ³¾¹¬O 250 ¥Ëªº¡A¨º»ò´N´«¤W 300 ¥Ëªº¸Õ¸Õ¡^¡C</para>
             </listitem>
 
           </orderedlist>
 
           <para>½Ð¶¶«K°Ñ¾\ SIG11 FAQ¡]³sµ²¦b¤U­±¡^¡AÁöµM¥¦¬O¯¸¦b Linux ªº¨¤
 	    «×¼gªº¡A¥i¬O¸Ì­±¹ï³o¨Ç°ÝÃD¦³³\¦h«Ü´Îªº¸Ñ»¡¡C¥¦¸Ì­±¤]¦³°Q½×¬°¤°»ò
 	    ¦³°ÝÃDªº°O¾ÐÅé¯à³q¹L³nÅé©ÎµwÅ骺´ú¸Õªº­ì¦]¡C</para>
 
           <para>³Ì«á¡A¦pªG¤W­±³o¨Ç­ì¦]³£±Æ°£¤F¡A¨º»ò¦³¥i¯à¬O¹J¨ì¤F FreeBSD
 	    ùتº¤@°¦¯äÂΡA½Ð°Ñ¾\«ü¥Ü°µ¤@­Ó°ÝÃD¦^³ø¡C</para>
 
           <para>³o¨à¦³¤@­Ó§ó¸Ô²Óªº FAQ ¡Ð <ulink
 	    URL="http://www.bitwizard.nl/sig11/">
 	    the SIG11 problem FAQ</ulink></para>
           </answer>
         </qandaentry>
 
         <qandaentry>
           <question id="trap-12-panic">
-            <para>§Úªº¨t²Î·í¾÷®É¥X²{¡G<errorname>Fatal
+            <para>·í¾÷®É¥X²{¡G<errorname>Fatal
               trap 12: page fault in kernel mode</errorname>¡A©Î¬O
-              <errorname>panic:</errorname>¡A¦A¥[¤W¤@°ï¿ù»~°T®§¡A
-              §Ú¸Ó«ç»ò¿ì¡H</para>
+              <errorname>panic:</errorname>¦A¥[¤W¤@°ï¿ù»~°T®§¡A
+              ¸Ó«ç»ò¿ì¡H</para>
           </question>
 
           <answer>
             <para>FreeBSD ªº¶}µoªÌ¹ï©ó³o¨Ç¿ù»~°T®§¬Û·íªº¦³¿³½ì¡A¦ý¬O¥L­Ì»Ý­n
               §ó¸Ô²Óªº¤@¨Ç²Ó¸`¡C½Ð§â±zªº·í¾÷ªº°T®§¥þ³¡½Æ»s¤U¨Ó¡A±µµÛ¬d¾\ FAQ
               ùØ <link linkend="KERNEL-PANIC-TROUBLESHOOTING">kernel
 	      panics</link> ³o¸`¡A¨Ì»¡©ú½sĶ¤@­Ó§t°£¿ù½Xªº kernel¡A¥H¨ú±o¨ç¦¡
 	      ©I¥s¶¶§Ç¡]backtrace¡^¡C³o­ÓÅ¥°_¨Ó«ÜÃø¡A¦ý¹ê»Ú¤W¨Ã¤£»Ý­n¥ô¦óµ{¦¡
 	      ³]­pªº¯à¤O¡A±z¥u»Ý­n¨Ì·Ó«ü¥Ü°µ§Y¥i¡C</para>
           </answer>
         </qandaentry>
 
         <qandaentry>
           <question id="screen-loses-sync">
             <para>¬°¤°»ò·í§Ú¶}¾÷®É¡A¿Ã¹õÅܶ¡A¥B¤£°±°{°Ê¡H</para>
           </question>
 
           <answer>
             <para>³o­Ó°ÝÃD¡A¤wª¾¬O¥Ñ ATI Mach 64 Åã¥Ü¥d©Ò¤Þ°_ªº¡C¦]¬°³o¶ô¥d
               ¨Ï¥Î¨ì <literal>2e8</literal> ³o­Ó¦ì§}¡A¦Ó³o»P²Ä¥|­Ó§Ç¦C°ð
 	      ¡]serial port¡^©Ò¨Ï¥Îªº¦ì§}¬Û¦P¡C¦Ó¦b &man.sio.4; ³o­ÓÅX°Ê
 	      µ{¦¡ùØ¡A¤£ª¾¹D¬O bug ©Î¬O¥\¯à¡]feature¡^¡A´Nºâ±z¨S¦³²Ä¥|­Ó§Ç
 	      ¦C°ð¡A©Î¬O¤w¸g±N sio3¡]²Ä¥|­Ó§Ç¦C°ð¡^¨ú®ø¤F¡A¥¦
 	      <emphasis>¨ÌµM</emphasis>·|¥h¹Á¸ÕÅX°Ê¥¦¡C</para>
 
             <para>ª½¨ì³o­Ó°ÝÃD³Q¸Ñ¨M¥H«e¡A±z¥i¥H¨Ï¥Î³o­Ó¤èªk¡G</para>
 
               <orderedlist>
                 <listitem>
                   <para>¦b¬Ý¨ì¶}¾÷´£¥Ü®É¿é¤J <option>-c</option>
                     ¡]³o·|Åý kernel ¶i¤J³]©w¼Ò¦¡¡^¡C</para>
                 </listitem>
 
                 <listitem>
                   <para>¨ú®ø <devicename>sio0</devicename> ¡A
                     <devicename>sio1</devicename> ¡A
                     <devicename>sio2</devicename> ©M
                     <devicename>sio3</devicename>¡]¥þ³¡¡^¡C  
                     ³o¥i¥HÅý sio ÅX°Êµ{¦¡¤£°Ê§@ -&gt; ©ó¬O°ÝÃD¸Ñ¨M¡C</para>
                 </listitem>
 
                 <listitem>
                   <para>¿é¤J exit ¥HÄ~Äò±Ò°Êµ{§Ç¡C</para>
                 </listitem>
               </orderedlist>
 
           <para>¦pªG±z·Q­n¨Ï¥Î±zªº§Ç¦C°ð¡A±z»Ý­n­×§ï
             <filename>/usr/src/sys/i386/isa/sio.c</filename>¡A¦b¸ÓÀɤ¤§ä¥X
             <literal>0x2e8</literal> ³o­Ó¦r¦ê¡A²¾°£³o­Ó¦r¦ê¤Î¥¦«e­±ªº³r¸¹
            ¡]«O¯d«á­±ªº¡^¡AµM«á­«·s½sĶ¤@­Ó·sªº kernel¡C</para>
 
           <para>´Nºâ¨Ï¥Î¤F¤W­±³o¨Ç¤èªk¡AX Window ¤´µM¦³¥i¯àµLªk¶¶§Q°õ¦æ¡C
             ¦pªGµo¥Í¤F³oºØ±¡§Î¡A½Ð½T©w§A¥Îªº XFree86 ªºª©¥»¬O³Ì·sªº XFree86
             3.3.3 ©Î¬O¨ä«áªºª©¥»¡C¥¦­Ì¦³¤º«Ø¤ä´© Mach 64 ³o±i¥d¡A¬Æ¦Ü¬°¤F³o
             ¨Ç¥dÁÙªþ¦³¤@­Ó¯S§Oªº X Server</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="reallybigram">
           <para>¬°¤°»ò§Úªº¨t²Î¸Ë¦³ 128 MB ªº RAM¡A¦Ó FreeBSD ¥u¥Î¤F¨ä¤¤ªº
 	    64MB¡H</para>
         </question>
 
         <answer>
           <para>¦]¬° FreeBSD ¬O¨Ï¥Î©I¥s BIOS ¨Ó¨ú±o°O¾ÐÅé¤j¤pªº¤èªk¡A¦]¦¹¥¦
             ¥u¯à°»´ú¨ì 16 bits ¦ì¤¸ªø«×ªº KByte ¤j¤p¡]65535 KBytes = 64MB¡^
             ¡]©ÎªÌ§ó¤Ö..¡C¦³¨Ç BIOS ±N³Ì°ª°O¾ÐÅé¤j¤p­­¬°¥u¦³ 16MB¡^
             ¦pªG±z¾Ö¦³ 64MB ¥H¤Wªº RAM¡AFreeBSD ·|¹Á¸Õ¥h°»´ú¥X¥¦¡A¦ý¬O¦³¥i¯à
             ·|¥¢±Ñ¡C</para>
 
           <para>­n¸Ñ¨M³o­Ó°ÝÃD¡A±z»Ý­n¨Ï¥Î¤U­±©Ò´£ªº kernel ³]©w¿ï¶µ¡CÁöµM¦³
 	    ¤èªk¥i¥H±q BIOS ¤¤¨ú±o°O¾ÐÅ骺§¹¾ã¸ê°T¡A¦ý¬O¥Ø«e§Ú­Ì¦b¶}¾÷°Ï¤¤¨Ã
 	    ¨S¦³¦h¾lªºªÅ¶¡¨Ó°µ³o¥ó¨Æ¡C·í¬Y¤Ñ¶}¾÷°ÏªÅ¶¡¤£¨¬ªº±¡§ÎÀò±o¸Ñ¨M®É¡A
 	    §Ú­Ì±N·|¨Ï¥Î BIOS ªº©µ¦ù¥\¯à¨Ó¨ú±o°O¾ÐÅ骺§¹¾ã¸ê°T...¦ý²{¦b§Ú­Ì
 	    ±N¥¦©ñ¦b kernel ³]©w¿ï¶µ¤¤¡C</para>
 
           <para><literal>options "MAXMEM=<replaceable>n</replaceable>"</literal></para>
 
           <para><replaceable>n</replaceable> ¬O«ü±zªº°O¾ÐÅé¤j¤p¡A¥H KB 
             ¬°³æ¦ì¡C¥H¤@¥x¦³ 128MB RAM ªº¾÷¾¹¨Ó»¡¡A±z¥i¨Ï¥Î
             <literal>131072</literal>³o­Ó¼Æ¦r¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
-        <question id="panic-kmemmap-too-small">
-          <para>¬°¤°»ò FreeBSD 2.0 ¦]¬° 
-            <errorname>kmem_map too small!</errorname>³o­Ó­ì¦]¦Óµo¥Í
-	    panic ¡H</para>
-        </question>
+	<question id="kmem-map-too-small">
+	  <para>¾÷¾¹¤Wªº RAM ¦³ 1GB ¥H¤W¡A¥i¬O¬°¦ó«o¦¬¨ì <quote>kmem_map too small</quote> 
+	        ªº panic ¿ù»~°T®§¡H
+	    </para>
+	</question>
+
+	<answer>
+	  <para>³q±` FreeBSD ·|¨Ì¾Ú¾÷¾¹ª¬ªp¨Ó¦Û°Ê½Õ¾ã kernel ¬ÛÃö°Ñ¼Æ³]©w¡A¤ñ¦p¡G
+	    ®Ú¾Ú¾÷¾¹©Ò¸Ëªº RAM ¤j¤p¨Ó¨M©w¦P®É¥i¶}±ÒªºÀɮ׼ƶq¦h¹è¡C
+	    µM¦Ó¡A¦b 1GB RAM(§t¥H¤W) ªº¾÷¾¹¤W¡A³o­Ó¡y¦Û°Ê½Õ¾ã¡zªº¾÷¨î¥i¯à¦³®É·|°ª¦ô¡G
+	    ¤ñ¤è»¡..¶}¾÷®É¡Akernel ·|¥ý°t¸m¦UºØ¤£¦P¥Î³~ªºªí®æ¤Î¨ä¥L¬[ºc©ñ¨ì°O¾ÐÅé¤W¡A
+	    µM«á¡A·í¾ã­Ó§@·~¨t²Î³£¶}©l¹B§@¤§«á¡Akernel ´N·|¶}©l¤£°÷ªÅ¶¡¨Ó°µ°O¾ÐÅé°t¸mªº°ÊºA½Õ¾ã¡A
+	    ©ó¬O´N panic ±¾¤F¡C</para>
+
+	  <para>¸Ñªk¬O¡G§â <option>VM_KMEM_SIZE_MAX</option> ¥[¨ì kernel ³]©wÀɤº¡A
+	    ¨Ã­«·s½sĶ kernel¡A¤ñ¦p¡G</para>
+
+	  <para><literal><option>options VM_KMEM_SIZE_MAX=419430400</option></literal></para>
+
+	  <para>
+	    ³o¼Ë·|³]©w 400&nbsp;MB ¨Óµ¹ kernel ¨Ï¥Î¡A¦Ó¥B±Ä¥Î 400&nbsp;MB ªº¸Ü¡A
+	    ¥Ø«e¦b 6GB RAM ªº¾÷¾¹¤W³£¥i³Q¦³®Ä¹B¥Î¡C</para>
+	</answer>
+      </qandaentry>
+      
+      <qandaentry>
+	<question id="panic-kmemmap-too-small">
+	  <para>¾÷¾¹¤W RAM ¤£¨ì 1GB ¡A¦ý¤´·|¥X²{
+	    <errorname>kmem_map too small!</errorname> ªº panic ¿ù»~°T®§
+	    </para>
+	</question>
 
         <answer>
-            <note>
-              <para>³o­Ó°T®§¤]¦³¥i¯à¬O
-                <literal>mb_map too small!</literal></para>
-            </note>
+          <para>¤§©Ò¥H panic ªº­ì¦]¦b©ó¨t²Î¥Î¥ú¤Fµ¹ network buffer ¥Î³~ªº virtual memory
+	    (¤×¨ä¬O mbuf clusters)¡C¸Ñªk¬O¼W¥[µ¹ mbuf clusters ¥Îªº virtual memory 
+	    ¼Æ¶q¡A³o¨BÆJ½Ð°Ñ¾\ FreeBSD ¨Ï¥Î¤â¥Uªº 
+	    <ulink 
+	    url="&url.books.handbook;/configtuning-kernel-limits.html#NMBCLUSTERS">ºô¸ô­­¨î½g</ulink>
+	    ¡C</para>
+        </answer>
+      </qandaentry>
 
+<!--
+¥H¤U¬°Âª© faq ¤º®e
           <para>³o­Ó panic ªº­ì¦]¬Oªí¥Ü¨t²Î¥Î¥ú¤Fµ¹ºô¸ô½w½Ä°Ïªº©Ò¦³ªºµê
             ÀÀ°O¾ÐÅé¡]¯S§O¬O mbuf clusters¡^¡C±z¥i¥H¼W¥[µ¹ mbuf clusters 
             ªº VM ªº¼Æ¶q¡A¥u­n¥[¤J:</para>
 
           <para><literal>options "NMBCLUSTERS=<replaceable>n</replaceable>"</literal></para>
 
           <para>¦b±zªº kernel ³]©wÀɤ¤¡A<replaceable>n</replaceable>
 	    ¬O¤@­Ó¦b 512-4096 ¶¡ªº¼Æ¦r¡A¨Ì±z·Q´£¨Ñ¦h¤Ö¦P®Éªº TCP ³s±µ¼Æ¥Ø
 	    ¦h¹è¦Ó©w¡C§Ú·|«Øij¸Õ¸Õ 2048 - ³o¼Æ¦rÀ³¸Ó¥i¥H§¹¥þÁקK³o­Ó panic
 	    ¤F¡C±z¥i¥H°õ¦æ: <command>netstat -m</command>
 	    ¡]see &man.netstat.1;¡^¨ÓºÊ¬Ý¦³¦h¤Ö mbuf clusters ¦b¨t²Î¤W¥¿³Q
 	    °t¸m/¨Ï¥Î¡CNMBCLUSTERS ªº¼Æ­È¤º©w¬° <literal>512 + MAXUSERS * 16
 	    </literal>¡C</para>
-        </answer>
-      </qandaentry>
+-->
 
       <qandaentry>
         <question id="proc-table-full">
           <para>¬°¤°»ò§Ú¤@ª½¬Ý¨ì <errorname>/kernel: proc: table
             is full</errorname> ³o­Ó¿ù»~°T®§¡H</para>
         </question>
 
         <answer>
-          <para>FreeBSD ªº kernel ¥u·|¤¹³\¤@©w¼Æ¶qªº process ¦b¦P¤@®É¶¡¸Ì¦P
+          <para>FreeBSD kernel ¥u¤¹³\¤@©w¼Æ¶qªº process ¦b¦P¤@®É¶¡¸Ì¦P
 	    ®É¹B§@¡C¦Ó³o­Ó¼Æ¥Ø¬O®Ú¾Ú kernel ³]©wÀɸ̭±ªº
 	    <literal>MAXUSERS</literal> ­È¨Ó¨M©wªº¡C<literal>MAXUSERS</literal>
-	    ³o­Ó­È¤]·|¼vÅT¨ä¥Lªº kernel ¤º©w­È¡A¤ñ¦p»¡ºô¸ô½w½Ä°Ï
-	    ¡]½Ð°Ñ¾\<link linkend="panic-kmemmap-too-small">³o­Ó</link>¤§«e°Q
-	    ½×¹Lªº°ÝÃD¡^¡C¦pªG¾÷¾¹­t²ü¡]load¡^«Ü­«¡A±z¥i¯à»Ý­n¼W¥[
+	    ³o­Ó­È¤]·|¼vÅT¨ä¥Lªº kernel ¤º©w­È¡A¤ñ¦p»¡ network buffer
+	    (½Ð°Ñ¾\<link linkend="panic-kmemmap-too-small">³o­Ó</link>¤§«e°Q
+	    ½×¹Lªº°ÝÃD)¡C¦pªG¾÷¾¹­t²ü(load)«Ü­«¡A±z¥i¯à»Ý­n¼W¥[
 	    <literal>MAXUSERS</literal> ³o­Ó­È¡C³o»ò§@·|¤@¨Ö´£°ª¨t²Îªº¨ä¥L¤º
 	    ©w­È¡A¥]¬A³Ì¤j¥i¾Ö¦³ªº process ¼Æµ¥¡C</para>
 
+	  <para>­Y­n½Õ¾ã <literal>MAXUSERS</literal>¡A½Ð°Ñ¾\ FreeBSD ¨Ï¥Î¤â¥U¤¤ªº <ulink
+	    url="&url.books.handbook;/configtuning-kernel-limits.html#KERN-MAXFILES">
+	    ÀÉ®×/Processªº­­¨î</ulink> ³¹¸`¡C
+	    (ÁöµM¸Ó³B«üªº¬O¡yÀɮתº¶}±Ò¼Æ¶q­­¨î¡z¡A¦ý¤]¾A¥Î©ó process³¡¤À¡C)</para>
+
           <para>¦b FreeBSD 4.4 ¤§«á¡A<literal>MAXUSERS</literal> ¤w¸gÅܦ¨¥i
 	    ¥H¾aµÛ§ó§ï <filename>/boot/loader.conf</filename> ùتº
 	    <varname>kern.maxusers</varname> ³o­Ó­È¦Ó½Õ¾ãªºÅܼƤF¡C¦Ó¦b¤§«e
 	    ªº FreeBSD ª©¥»¤¤¡A³o­Ó­È¥u¯à¦b kernel ³]©wÀÉùؽվã¡C</para>
 
           <para>¦pªG¾÷¾¹­t²ü¨Ã¤£­«¡A¦Ó±z¥u¬O»Ý­n¦P®É¶]«Ü¦h«Ü¦h process¡A
-	    ¨º»ò¤]¥i¥Hª½±µ¥Î sysctl ½Õ¾ã <varname>kern.maxproc</varname>
-	    ³o­Ó­È¡C°²¦p³o¨Ç process ³£¬OÄÝ©ó¬Y­Ó¨Ï¥ÎªÌªº¡A¨º»ò±zÁٻݭn¥t
+	    ¨º»ò¤]¥i¥Hª½±µ¥Î sysctl ½Õ¾ã <varname>kern.maxproc</varname> ­È¡C
+	    °²¦p³o¨Ç process ³£¬OÄÝ©ó¬Y­Ó¨Ï¥ÎªÌªº¡A¨º»ò±zÁٻݭn¥t
 	    ¥~½Õ¾ã <varname>kern.maxprocperuid</varname> ³o­Ó­È¡A¨Ï¥¦¤ñ·s
-	    ªº <varname>kern.maxproc</varname> ³o­Ó­È¤Ö¤@¡]¤@©w­n¤Ö¤@¡A
-	    ¦]¬° &man.init.8; ³o­Ó¨t²Îµ{¦¡µ´¹ï­n«O«ù¦b¹B§@ª¬ºA¡^¡C</para>
+	    ªº <varname>kern.maxproc</varname> ³o­Ó­È¤Ö 1 (¤@©w­n¤Ö 1 ¡A
+	    ¦]¬° &man.init.8; ³o­Ó¨t²Îµ{¦¡µ´¹ï­n«O«ù¦b¹B§@ª¬ºA)¡C</para>
 
           <para>¦pªG·Q¦b¨C¦¸¶}¾÷³£­n§ó§ï sysctl ªº­È¡A¦Ó¥B±zªº FreeBSD ¬O
 	    ³Ìªñªºª©¥»ªº¸Ü¡A½Ð¦b <filename>/etc/sysctl.conf</filename> ³o
 	    ­ÓÀɤ¤³]©w¡A¦Ó¦pªG¬Oªºª©¥»¡A¥i¥H¦b
 	    <filename>/etc/rc.local</filename> ¤¤§@³]©w¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="cmap-busy-panic">
           <para>¬°¤°»ò¥Î·s kernel ¶}¾÷®É¡A¥X²{ <errorname>CMAP
               busy</errorname> ³o­Ó¿ù»~°T®§¡H</para>
         </question>
 
         <answer>
           <para>¥Î¨Ó°»´ú¹L®É
             <filename>/var/db/kvm_*.db</filename> Àɮתº¾÷¨î°¸º¸·|
             µo¥Í°ÝÃD¡A¦Ó¨Ï¥Î¨ì¤F¤@­Ó¤£¨ó½Õ¡]mismatch¡^ªºÀɮצ³®É´N·|¾É­P
 	    panic¡C</para>
 
           <para>¦pªGµo¥Í¤F³o­Ó°ÝÃD¡A½Ð­«·s¶}¾÷¡A¶i¤J³æ¨Ï¥ÎªÌ¼Ò¦¡¡AµM«á°õ
 	    ¦æ¡G</para>
 
           <screen>&prompt.root; <userinput>rm /var/db/kvm_*.db</userinput></screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="brkadrint-illegal-host-access">
           <para>½Ð°Ý³o­Ó°T®§¡G<errorname>ahc0: brkadrint,
               Illegal Host Access at seqaddr 0x0</errorname>
             ¬O¤°»ò·N«ä¡H</para>
         </question>
 
         <answer>
           <para>³o¬O¤@­Ó©M Ultrastor SCSI ±±¨î¥d¦³Ãöªº½Ä¬ð¡]conflict¡^¡C</para>
 
           <para>¦b¶}¾÷®É¡A¶i¤J kernel ³]©w¿ï³æ¨ú®ø
             <devicename>uha0</devicename>¡A¥¦¬O³y¦¨³o­Ó°ÝÃDªº­ì¦]¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="aci0-illegal-cable">
           <para>¦b¶}¾÷®É¡A§Ú¬Ý¨ì³o­Ó¿ù»~°T®§
             <errorname>ahc0: illegal cable configuration</errorname>¡C
             §Úªº±Æ½u½T©w¦³±µ¹ï¡C ¬O¥X¤F¤°»ò°ÝÃD©O¡H</para>
         </question>
 
         <answer>
            <para>±zªº¥D¾÷ªO¥i¯à¤£¤ä´©¦Û°Ê²×ºÝ¹qªý³]©w¡C½Ð¶i¨ì SCSI ªº BIOS 
              ¸Ì­±¤â°Ê«ü©w¥¿½Tªº²×ºÝ¹qªý¶¶§Ç¡A¦Ó¤£­n¨Ï¥Î¦Û°Ê³]©w¡CAIC7XXX ªº
              ÅX°Êµ{¦¡¨ÃµLªkª¾¹D¦³¨S¦³³o¨Ç±Æ½u°»´ú¡]¥H¤Î¦Û°Ê²×ºÝ¹qªý³]©w¡^ªº
 	     ¹q¸ô¡]external logic¡^¦s¦b¡C¦pªG EEPROM ¸Ì­±ªº³]©w¬O
 	     "automatic termination" ®É¡A¥¦¥u·|³æ¯Â°²©w³o¨Ç¹q¸ô·íµM¬O¦s¦bªº¡C
 	     ­Y¯Ê¤Ö¤F³o­Ó¹q¸ô¡AÅX°Êµ{¦¡¦b³]©w²×ºÝ¹qªý®É´N±`±`¥X°ÝÃD¡C
              ¦Ó³oºØ°ÝÃD±N¾É­P SCSI ¶×¬y±Æªº¥i¾a©Ê­°§C¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="mail-loopback">
           <para>¬°¤°»ò Sendmail ¤@ª½¥X²{
 	    <quote><errorname>mail loops back to myself</errorname></quote>
 	    ³o­Ó¿ù»~°T®§¡H</para>
         </question>
 
         <answer>
           <para>³o­Ó°ÝÃD¦b sendmail ªº FAQ ¤¤¬O³o¼Ë¦^µªªº:-</para>
 
 <literallayout>        * §Ú¤@ª½¦¬¨ì¦³Ãö "Local configuration error" ªº«H¥ó¡A¨Ò¦p¡G
 
         553 relay.domain.net config error: mail loops back to myself
         554 &lt;user@domain.net&gt;... Local configuration error
 
         §Ú­n¦p¦ó¸Ñ¨M³o­Ó°ÝÃD¡H
 
         ±z§Q¥Î MX ³]©w¡AÅý­n±H¨ì¬Y domain¡]¦p: domain.net¡^ªº«H¥ó¡A
         ±H¨ì±z©Ò«ü©wªº¾÷¾¹¡]¦b³o­Ó¨Ò¤l¤¤¬° relay.domain.net¡^¡A¦ý¬O³o
         ³¡¾÷¾¹¨Ã¥¼³Q³]©w±µ¨ü domain.net ªº«H¥ó¡C½Ð§â domain.net ¥[¨ì
         /etc/sendmail.cw ¤¤¡]¦pªG±z¦³¨Ï¥Î FEATURE(use_cw_file)) ©Î¬O
         ¦b sendmail.cf ¤¤¥[¤J "Cw domain.net"
             </literallayout>
 
           <para>³Ì·sª©¥»ªº <ulink  URL="ftp://rtfm.mit.edu/pub/usenet/news.answers/mail/sendmail-faq">sendmail
             FAQ</ulink> ²{¦b¤w¤£¦AÀHµÛ sendmail <quote>¥X³f</quote>¡C
             ¥¦¥Ø«e¬O³Q©w´Áªºµoªí¦b <ulink
             URL="news:comp.mail.sendmail">comp.mail.sendmail</ulink>¡A
             <ulink URL="news:comp.mail.misc">comp.mail.misc</ulink>¡A<ulink
             URL="news:comp.mail.smail">comp.mail.smail</ulink>¡A<ulink
             URL="news:comp.answers">comp.answers</ulink>¡A©M <ulink
             URL="news:news.answers">news.answers</ulink>. ±z¤]¥i¥H±H¤@«Ê
 	    Email ¨ì <email>mail-server@rtfm.mit.edu</email>¡AµM«á¦b«H¥ó¤º¤å
 	    ¤¤¼g¤W
             <literal>send usenet/news.answers/mail/sendmail-faq</literal>
             ¥H¨ú±o³o¥÷ FAQ ¤å¥ó¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="remote-fullscreen">
           <para>¬°¤°»ò°õ¦æ»·ºÝ¾÷¾¹¡]remote machine¡^ªº¥þ¿Ã¹õªº³nÅé®É¡A
 	    ¦³¤£¥¿±`ªº±¡§Î¡H</para>
         </question>
 
         <answer>
           <para>©Î³\»·ºÝ¾÷¾¹¨Ã«D±N±zªº²×ºÝ¾÷¼Ò¦¡³]¬° FreeBSD console ©Ò¥Îªº
 	    <literal>cons25</literal>¡A¦Ó¬O³]¬°¨ä¥¦¼Ò¦¡¡C</para>
 
           <para>³o¨à¦³´X­Ó¸Ñ¨M³o­Ó°ÝÃDªº¤èªk¡G</para>
             <itemizedlist>
               <listitem>
                 <para>¦b logging ¶i»·ºÝ¾÷¾¹«á¡A§ó§ï±zªº shell ÅÜ¼Æ TERM ¬°
 		  <literal>ansi</literal> ©Î¬O <literal>sco</literal>
 		  ¡}¦pªG»·ºÝ¾÷¾¹¤ä´©³o¨Ç¼Ò¦¡ªº¸Ü¡^¡C</para>
               </listitem>
 
               <listitem>
                 <para>¨Ï¥Î¤ä´© VT100 ªº¼ÒÀÀ³nÅé¡A¦p FreeBSD console ¤Uªº
                   <application>screen</application> ³nÅé¡C
                   <application>screen</application> ´£¨Ñ±z¦b¤@­Ó terminal
 		  ùئP®É¶]¦n´X­Ó session ªº¯à¤O¡A¦Ó¥B¥¦¥»¨­¤]¬O¤@­Ó¬Û·í¦n
 		  ªº³nÅé¡C¨C­Ó <application>screen</application> ³£¹³¬O¤@­Ó
 		  VT100 ªº²×ºÝ¾÷¡A©Ò¥H»·ºÝ¾÷¾¹ªº TERM ÅܼÆÀ³¸Ó³]¬°
 		  <literal>vt100</literal>¡C</para>
               </listitem>
 
               <listitem>
                 <para>¦b»·ºÝ¾÷¾¹ªº²×ºÝ¾÷¸ê®Æ®w¡]terminal database¡^¤¤¥[¤J
 		  <literal>cons25</literal> ªº¸ê®Æ¡C¥[¤Jªº¤èªkµø»·ºÝ¾÷¾¹ªº
 		  §@·~¨t²Î¤£¦P¦Ó¦³©Ò®t²§¡C½Ð°Ñ¾\»·ºÝ¾÷¾¹µ¹¨t²ÎºÞ²z­ûªº»¡©ú
 		  ®Ñ¡AÀ³¸Ó·|¦³©ÒÀ°§U¡C</para>
               </listitem>
 
               <listitem>
                 <para>±Ò°Ê FreeBSD ªº X ¦øªA¾¹¡AµM«á¨Ï¥Î¤@¨Ç X Window ¤Uªº
 		  ²×ºÝ¾÷¼ÒÀÀ¾¹¨Óµn¤J»·ºÝ¾÷¾¹¡A¨Ò¦p <command>xterm</command>
 		  ©Î <command>rxvt</command>¡C¦Ó»·ºÝ¾÷¾¹ªº TERM ÅܼÆÀ³¸Ó­n
 		  ³]¬° <literal>xterm</literal> ©Î <literal>vt100</literal>¡C
 		  </para>
               </listitem>
             </itemizedlist>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="calcru-negative">
           <para>¬°¤°»ò§Úªº¾÷¾¹¤@ª½Åã¥Ü 
             <errorname>calcru: negative time...</errorname>¡H</para>
         </question>
 
         <answer>
           <para>¸ò¤¤Â_¡]interrupt¡^¦³Ãöªº¤£¦PµwÅé »P/©Î ³nÅ骺·f°t³£¦³¥i¯à³y¦¨
             ³o­Ó°ÝÃD¡C³o¦³¥i¯à¬O bug ©Î¬O¬Y­Ó¸Ë¸m¥»¨­ªº°ÝÃD¡C¦b¥­¦æ°ð¤W¨Ï¥Î
             ¤jªº MTU ¨Ó§@ TCP/IP ¶Ç¿é¥i¥H­«²{³o­Ó°ÝÃD¡C­Y¬O¹Ï§Î¥[³t¥d³y¦¨³o­Ó
             °ÝÃDªº¸Ü¡A±zÀ³¸Ó¥ýÀˬd¥dªº¤¤Â_³]©w¡C</para>
 
           <para>³o­Ó°ÝÃDªºÃä»Ú®ÄÀ³¬O·|³y¦¨¦³¨Ç process ¥X²{
             <quote>SIGXCPU exceeded cpu time limit</quote> ªº°T®§¡A¦Ó¤£¥¿±`
 	    °±¤î¡C</para>
 
           <para>­Y¬O FreeBSD 3.0 ©Î¬O 1998 ¦~ 11 ¤ë 29 ¤é¥H«á¨ä¥Lª©¥»¡A¸U¤@
 	    ³o­Ó°ÝÃD¤@ª½µLªk¥H¨ä¥L¤èªk¸Ñ¨M¡A´N¥u¯à³]©w sysctl ÅܼơG</para>
 
           <screen>&prompt.root; <userinput>sysctl -w kern.timecounter.method=1</userinput></screen>
 
           <para>³o¼Ë·|¹ï®Ä¯à¦³¨Ç¼vÅT¡A¦ý¬O­Y¦Ò¼{¨ì³o­Ó°ÝÃD±a¨Óªº«áªG¡A³o¼Ë°µ
 	    ¬O­È±oªº¡C¦pªG³o­Ó°ÝÃDÁÙ¬O¦s¦bªº¸Ü¡AÅý sysctl ¨º­Ó­È¨ÌµM³]¬° 1¡A
 	    µM«á¼W¥[ kernel ³]©wÀɤ¤ <literal>NTIMECOUNTER</literal> ³o­Ó¿ï
 	    ¶µªº¼Æ­È¡C¦pªG±z±N <literal>NTIMECOUNTER</literal> ¼W¥[¨ì 20 ¨Ì
 	    µMµLªk¸Ñ¨M³o­Ó°ÝÃD¡A¨º»ò±z¾÷¾¹¤Wªº¤¤Â_¤w¸g¦h¨ìµLªkÅý­p¼Æ¾¹ºû«ù¦b
 	    ¥i¾aªºª¬ºA¤F¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="pcm0-not-found">
           <para>¥X²{ <errorname>pcm0 not found</errorname> ³o­Ó°T®§¡A©ÎªÌ¬O
 	    §Úªº­µ®Ä¥dÅܦ¨¤F <devicename>pcm1</devicename>¡A¦ý¦b kernel ³]©w
 	    ÀÉùاڬO³] <literal>device pcm0</literal> °Ú¡C³o¬O«ç»ò¦^¨Æ©O¡H
 	  </para>
 	</question>
 
         <answer>
           <para>¦pªG±z¦b FreeBSD 3.x ¤W¨Ï¥Î PCI ­µ®Ä¥d´N·|µo¥Í³oºØ°ÝÃD¡C
 	    ¦]¬°<devicename>pcm0</devicename> ³o­Ó device ¬O¤º©w«O¯dµ¹ ISA
 	    ªº­µ®Ä¥dªº¡A©Ò¥H¦pªG±z¦³¤@±i PCI ªº­µ®Ä¥d¡A±z´N·|¹J¨ì³o­Ó°ÝÃD¡A
 	    ¦Ó±zªº¥d·|Åܦ¨ <devicename>pcm1</devicename>¡C</para>
 
             <note>
               <para>¦pªG±z¥u§â kernel ³]©wÀɤ¤ªº³]©w§ï¦¨
 	        <literal>device pcm1</literal> ¬OµLªk°£¥h³o­Óĵ§i°T®§ªº¡A
 		³o¼Ë·|³y¦¨ <devicename>pcm1</devicename> ³Q«O¯dµ¹ ISA ­µ®Ä¥d¡A
 		¦Ó PCI ­µ®Ä¥d«h·|Åܦ¨ <devicename>pcm2</devicename>
 		¡]¥~¥[ <errorname>pcm1 not found</errorname> ªºÄµ§i°T®§¡^¡C
               </para>
             </note>
 
             <para>¦pªG±z¦³¤@±i PCI ªº­µ®Ä¥d¡A±z»Ý­n make 
             <devicename>snd1</devicename> ³o­Ó device¡A¦Ó¤£¬O
             <devicename>snd0</devicename>¡G</para>
 
           <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>./MAKEDEV snd1</userinput></screen>
 
           <para>³o­Ó°ÝÃD¦b FreeBSD 4.x ¤W¨Ã¤£·|µo¥Í¡A¦]¬°«Ü¦h¤H§ë¤U¤F³\¦h¤ß
 	    ¤OÅý¥¦§ó<emphasis>PnP ¾É¦V</emphasis>¡A¦Ó¥B
 	    <devicename>pcm0</devicename> ³o­Ó device ¤]¤£¦A¬O¥u«O¯dµ¹ ISA
 	    ªº­µ®Ä¥d¤F¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="pnp-not-found">
           <para>¬°¤°»ò¦b§ó·s¨ì FreeBSD 4.X «á·|§ì¤£¨ì§Úªº PnP ¥d
 	  ¡]©ÎªÌ¬O§ì¦¨ <literal>unknown</literal>¡^¡H</para>
         </question>
 
         <answer>
           <para>FreeBSD 4.X ²{¦b¤w¸g§ó <emphasis>PnP ¾É¦V</emphasis>¤F¡A
 	    ¦ÓÃä»Ú®ÄÀ³´N¬O·|µo¥Í¦³¨Ç¦b FreeBSD 3.X ¥i¥H¥Îªº PnP ¸Ë¸m
 	    ¡]¦p­µ®Ä¥d©Î¬O¤º´¡¦¡¼Æ¾Ú¾÷¡^Åܦ¨µLªk¨Ï¥Î¡C</para>
 
           <para>³o­Ó­ì¦]¥i¥H¥Î¤@«Ê¥Ñ Peter Wemm µo¨ì freebsd-questions
 	    ³o­Ó mailing list ¤Wªº«H¨Ó¸ÑÄÀ¡A¥¦­ì¥»¬O¸ÑÄÀ¬°¤°»ò¦³¤@­Ó¤º
 	    ´¡¦¡¼Æ¾Ú¾÷¡A¦b¨t²Î¤É¯Å¨ì FreeBSD 4.x «á¡A´N¨Sªk³Q§ì¨ì¤F
 	    ¡]¦b <literal>[]</literal> ùتº¬O¥t¥~¥[ªºµù¸Ñ¡AÅý¤º®e§ó©öÀ´¡^¡C
           </para>
 
           <blockquote>
             <para>The PNP bios preconfigured it [the modem] and left it
               laying around in port space¡Aso [in 3.x] the old-style ISA
               probes <quote>found</quote> it there.</para>
 
             <para>Under 4.0¡Athe ISA code is much more PnP-centric. It was
               possible [in 3.x] for an ISA probe to find a
               <quote>stray</quote> device and then for the PNP device id to
               match and then fail due to resource conflicts. So¡Ait
               disables the programmable cards first so this double probing
               cannot happen. It also means that it needs to know the PnP
               id's for supported PnP hardware. Making this more user
               tweakable is on the TODO list.</para>
           </blockquote>
 
           <para>¦pªG­nÅý¸Ë¸m¯à¦A«×¹B§@¡A§Ú­Ì»Ý­n§ä¥X¥¦ªº PnP id¡AµM«á¦A±N¥¦
 	    ¥[¤J¤@¥÷¦b°»´ú ISA ¸Ë¸m®É·|¨Ï¥Îªºªí¤¤¡C¥i¥H°õ¦æ &man.pnpinfo.8;
 	    ¨Ó°»´ú³o­Ó¸Ë¸m¡AÁ|¨Ò¨Ó»¡¡A¤U­±¬O &man.pnpinfo.8; §ì¨ìªº¤@­Ó¤º´¡
 	    ¦¡¼Æ¾Ú¾÷ªº¸ê®Æ¡G</para>
 
           <screen>&prompt.root; <userinput>pnpinfo</userinput>
 Checking for Plug-n-Play devices...
 
 Card assigned CSN #1
 Vendor ID PMC2430 (0x3024a341)¡ASerial Number 0xffffffff
 PnP Version 1.0¡AVendor Version 0
 Device Description: Pace 56 Voice Internal Plug & Play Modem
 
 Logical Device ID: PMC2430 0x3024a341 #0
         Device supports I/O Range Check
 TAG Start DF
     I/O Range 0x3f8 .. 0x3f8¡Aalignment 0x8¡Alen 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¡A1 logical fdevs
 -- card select # 0x0001
 
 CSN PMC2430 (0x3024a341)¡ASerial 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>±z©Ò»Ý­nªº¸ê°T¬O¤@¶}©l¬Ý¨ìªº <quote>Vendor ID</quote>
 	    ³o¤@¦æ¡C¬A¸¹¤¤ªº¤Q¤»¦ì¤¸½X¡]³o­Ó¨Ò¤l¤¤¬O 0x3024a341¡^´N¬O
 	    PnP id¡A¦Ó¦b³o¤§«eªº¦r¦ê¡]PMC2430¡^«h¬O¤@­Ó¿W¤@µL¤Gªº ASCII id¡C
 	    ¦Ó³o¨Ç¸ê®Æ»Ý­n³Q¥[¨ì <filename>/usr/src/sys/isa/sio.c</filename>
 	    ³o­ÓÀÉ®×ùØ¡C</para>
 
           <para>¬°¤F¨¾¤î¥ô¦óªF¦è¥X¿ù¡A±zÀ³¸Ó­n¥ý³Æ¥÷¥Ø«eªº
 	    <filename>sio.c</filename>¡C¦Ó¥B±z­n submit PR ®É¤]»Ý­n³o­Ó
 	    ­ì©lÀɮרӰµ¥X patch¡]±zÀ³¸Ó·|±N¥¦ submit PR §a..¡G¡^..¡^¡C
 	    ±µµÛ´N½s¿è <filename>sio.c</filename> §ä´M¤U­±³o¦æ</para>
 
           <programlisting>static struct isa_pnp_id sio_ids[] = {</programlisting>
 
           <para>±µµÛ©¹¤U±²°Ê¡A§ä­Ó¥¿½Tªº¦ì¸m¨Ó´¡¤J±zªº¸Ë¸m¸ê°T¡C±z¬Ý¨ìªº´N
 	    ¤U­±³o­Ó¼Ë¤l¡A¥¦­Ì¬O·Ó¥kÃäµù¸Ñ¸Ì­±ªº ASCII ³o­Ó Vender ID °µ±Æ
 	    §Çªº¡A©Î¬O &man.pnpinfo.8; ©Ò§ä¨ìªº¤@³¡¤À
 	    <emphasis>¸Ë¸m´y­z</emphasis>¡G</para>
 
           <programlisting>{0x0f804f3f¡ANULL}¡A    /* OZO800f - Zoom 2812 (56k Modem) */
 {0x39804f3f¡ANULL}¡A    /* OZO8039 - Zoom 56k flex */
 {0x3024a341¡ANULL}¡A    /* PMC2430 - Pace 56 Voice Internal Modem */
 {0x1000eb49¡ANULL}¡A    /* ROK0010 - Rockwell ? */
 {0x5002734a¡ANULL}¡A    /* RSS0250 - 5614Jx3(G) Internal Modem */</programlisting>
 
           <para>§â±z³o­Ó¸Ë¸mªº¤Q¤»¶i¦ìªº Vender ID ¥[¨ì¥¿½Tªº¦a¤è¡A¦sÀÉ¡A
 	    µM«á­«·s½s¤@­Ó kernel¡A¦A­«¶}¾÷¡C¤§«á³o­Ó¸Ë¸mÀ³¸Ó´N·|¹³¦b
 	    FreeBSD 3.X ¤U¡A³Q°»´ú¬° <literal>sio</literal> ¸Ë¸m¤F¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="nlist-failed">
           <para>¬°¤°»ò§Ú±`±`¦b¶]¤@¨Çµ{¦¡¡]¨Ò¦p <command>top</command> ©Î
 	    <command>systat</command>¡^ªº®É­Ô¥X²{
 	    <errorname>nlist failed</errorname> ³o­Ó¿ù»~°T®§¡H</para>
         </question>
 
         <answer>
           <para>³o­Ó°ÝÃD¬O¦]¬°±z¶]ªºµ{¦¡»Ý­n¤@­Ó¯S§Oªº kernel symbol¡A¥i¬O
 	    ¤£ª¾¹D¤°»ò­ì¦]¦Ó§ä¤£¨ì¡Q¦Ó·|µo¥Í³o­Ó°ÝÃD¥i¯à¬O¦]¬°¤U­±¨â­Ó­ì¦]¡G
           </para>
 
           <itemizedlist>
             <listitem>
               <para>±zªº kernel ©M userland ªºÀɮת©¥»¨Ã¤£¤@­P¡]¨Ò¦p»¡¡A±z
 	        ½s¤F¤@­Ó·sªº kernel¡A¦ý¬O¨Ã¨S¦³°õ¦æ¹ïÀ³ªº
 		<maketarget>installworld</maketarget>¡A©Î¬O¨ä¥LÃþ¦ü±¡§Î¡^¡A
 		¦]¦¹ symbol table ªº¤º®e´N©MÀ³¥Îµ{¦¡½sĶ®Éªº¤£¤Ó¤@¼Ë¤F¡C¦p
 		ªG¬O³oºØ±¡§Î¡A½Ð°õ¦æ§¹¾ãªº¤É¯Å¨BÆJ¡]½Ð°Ñ¾\
 		<filename>/usr/src/UPDATING</filename> ¥H±oª¾¥¿½Tªº¬y
 		µ{¡^¡C</para>
             </listitem>
 
             <listitem>
               <para>±z¨S¦³¥Î <command>/boot/loader</command> ¨Ó¸ü¤J±zªº
 	        kernel¡A¦Ó¬Oª½±µ¥Ñ boot2 ¶}¾÷¡]½Ð°Ñ¾\ &man.boot.8;¡^¡C
 		ÁöµM»¡¸õ¹L <command>/boot/loader</command> ¨Ã¨S¦³¤°»ò¿ù¡A
 		¦ý¬O¥¦¦b kernel symbols ¸òÀ³¥Îµ{¦¡ªº·¾³q¤è­±¦û¤F«Ü­«ªº¥÷¶q¡C
               </para>
             </listitem>
           </itemizedlist>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="connection-delay">
           <para>¬°¤°»ò§Ú¥Î  <command>ssh</command> ©Î <command>telnet</command>
 	    ³s¨ì§Úªº¹q¸£®É¡A·|µ¥«Ý«Üªøªº¤@¬q®É¶¡¤~¯à³s¤W¡H</para>
         </question>
 
         <answer>
           <para>¯gª¬¡GTCP ³s½u«Ø¥ß¤§«á©M¸ß°Ý±K½X¤§«e¡]¦pªG¬O¦b»¡ &man.telnet.1;
 	    ªº¸Ü¡A«h¬O login ´£¥Ü²Å¸¹¸õ¥X¨Ó¤§«e¡^¡A­nµ¥«Ý«Üªøªº¤@¬q®É
 	    ¶¡¡C</para>
 
           <para>°ÝÃD©Ò¦b¡G³oºØ©µ¿ð±¡§Î±`±`¬O¦]¬°¦øªA³nÅé¡]server software¡^
 	    ¹Á¸Õ­n±N«È¤áºÝ¡]client¡^ªº IP ¦ì§}Âà´«¦¨¥D¾÷¦WºÙ¡C¦]¬°«Ü¦h¦øªA
 	    ³nÅé¡A¥]¬A FreeBSD ¤º«Øªº Telnet ©M SSH¡A¬°¤F±N¥D¾÷¦WºÙ¼g¤J¬ö
 	    ¿ýÀɤ¤¥H¨ÑºÞ²zªÌ§@°Ñ¦Ò¡A¦Ó·|°µ³o¶µ°Ê§@¡C</para>
 
           <para>¸Ñ¨M¤èªk¡G¦pªG³o­Ó°ÝÃD¦b±z³s±µ¤£¦Pªº¦øªA¾¹®É³£·|µo¥Í¡A¨º»ò
 	    °ÝÃD¬O¦b±z«È¤áºÝ³o¤@¤è¡Q¦P¼Ëªº¡A¦pªG§O¤H¥u¦³¦b³s¨ì±zªº¦øªA¾¹¤W
 	    ¤~·|µo¥Í³o­Ó±¡§Î¡A¨º»ò°ÝÃD´N¬O¦b¦øªA¾¹³oÃä¤F¡C</para>
 
           <para>¦pªG¬O«È¤áºÝ³o¤è¦³°ÝÃD¡A°ß¤@ªº¤èªk´N¬O±N DNS ¦øªA¾¹­×¦n¡A
 	    ³o¼Ë¹ï¤è¦øªA¾¹¤~¯à¥¿½TªºÂà´«¦WºÙ¡C¦pªG°ÝÃD¬O¦b¤º³¡°Ï°ìºô¸ôµo
 	    ¥Íªº¡A³oÀ³¸Ó¬O¦øªA¾¹¦³°ÝÃD¡A½Ð¸Ô²ÓÀˬd¤@¤U¡Q¬Û¤Ïªº¡A¦pªG¬O±z
 	    ¦b¤W Internet ®Éµo¥Íªº¡A¨º»ò±z»Ý­n¸ò±zªº ISP Ápµ¸¡A½Ð¥L­Ì¸Ñ¨M
 	    ³o­Ó°ÝÃD¡C</para>
 
           <para>¦pªG¬O¦øªA¾¹³oÃ䪺°ÝÃD¡A¦Ó¥B¬Oµo¥Í¦b¤º³¡°Ï°ìºô¸ô¡A¨º»ò±z»Ý
 	    ­n³]©w³o­Ó¦øªA¾¹¡A¨Ï¥¦¯à¥¿½T±N¤º³¡ºô¸ôªº IP ¦ì§}Âà´«¬°¥D¾÷¦WºÙ¡C
 	    ½Ð°Ñ¾\ &man.hosts.5; ©M &man.named.8; ªº»¡©ú¥HÀò±o§ó¦h¸ê°T¡C¦p
 	    ªG¬O¦b Internet ¤Wªº¦øªA¾¹µo¥Í³o­Ó°ÝÃD¡A¨º»ò¦³¥i¯à¬O±z¦øªA¾¹ªº
 	    Âà´«¥\¯à¥X°ÝÃD¡C±z¥i¥H¸Õ¸Õ¬d¸ß¥t¤@­Ó¥D¾÷¦WºÙ¡A¤ñ¦p¡G
 	    <hostid>www.yahoo.com</hostid>¡C¦pªG¬d¤£¨ì¡A¨º»ò¥i¥H½T©w¬O±z³o
 	    Ãä¥X°ÝÃD¤F¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="stray-irq">
           <para><errorname>stray IRQ</errorname> ³o­Ó¿ù»~°T®§¬O¤°»ò·N«ä¡H</para>
         </question>
 	<answer>
           <para>Stray IRQs ¬OµwÅé IRQ ¦³ÂI¤p°ÝÃDªº²{¶H¡A¤j¦h¬O¦]¬°µwÅ饻¨­
 	    ¦bµo¥X¤¤Â_»Ý¨D«á¡A¤S¨ú®ø¤F¥¦¦Û¤vªº¤¤Â_­n¨D¡C</para>
           <para>¦³¤T­Ó¤èªk¥i¥HÀ³¥I³o­Ó°ÝÃD¡G</para>
 	  <itemizedlist>
 	    <listitem>
               <para>¤£²z·|³o­Óĵ§i¡C¤Ï¥¿¤@­Ó irq ¥X²{¤­¦¸Äµ§i«á¨t²Î´N¤£·|
 	        ¦AÅã¥Ü¤F¡C</para>
 	    </listitem>
 	    <listitem>
               <para>§â <function>isa_strayintr()</function> ùتº­È¡A¥Ñ 5
 	        §ï¦¨ 0¡A³o¼Ë©Ò¦³ªºÄµ§i°T®§³£¤£·|¥X²{¡C</para>
 	    </listitem>
 	    <listitem>
               <para>¦w¸Ë¨Ï¥Î irq 7 ªº¥­¦æ°ðµwÅé³]³Æ¡A¥H¤Î¥¦ªº PPP ÅX°Êµ{¦¡
 	        ¡]³o­Ó¤j³¡¤À¨t²Î³£¦³°µ¡^¡A±µµÛ¦w¸Ë ide µwºÐ©Î¬O¨ä¥L·|¨Ï¥Î
 	        irq 15 ªºµwÅé³]³Æ¥H¤Î¥¦ªºÅX°Êµ{¦¡¡C</para>
 	    </listitem>
 	  </itemizedlist>
 	</answer>
       </qandaentry>
 
       <qandaentry>
         <question id="file-table-full">
           <para>¬°¤°»ò <errorname>file: table is full</errorname> ³o­Ó°T®§
 	    ¤@ª½¦b dmesg ùØ­«½Æ¥X²{¡H</para>
         </question>
         <answer>
           <para>³o­Ó¿ù»~°T®§¥Nªí¤F±z¨t²Îªº file descriptors ¤w¸g¨Ï¥Î¥ú¤F¡C
 	    ½Ð°Ñ¾\¤â¥U¤º <ulink url="../handbook/configtuning-kernel-limits.html">
 	    Tuning  Kernel Limits</ulink> ¸Ì­±ªº <ulink
 	    url="../handbook/configtuning-kernel-limits.html#KERN-MAXFILES">
 	    kern.maxfiles</ulink> ³o­Ó³¹¸`¡A¸Ì­±¦³¤@¨Ç°Q½×¤Î¸Ñ¨M¤èªk¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
 	<question id="laptop-clock-skew">
           <para>¬°¤°»ò§Úµ§°O«¬¹q¸£¤Wªº®ÉÄÁ¤@ª½Åã¥Ü¿ù»~ªº®É¶¡¡H</para>
 	</question>
 
 	<answer>
           <para>±zªºµ§°O«¬¹q¸£¸Ì¦³¨â­Ó¥H¤Wªº®ÉÄÁ¡A¦Ó FreeBSD ¿ï¨ì¤F¿ùªº
 	    ¨º­Ó¡C</para>
 
            <para>°õ¦æ &man.dmesg.8;¡AÀˬd¤@¤U¦³ <literal>Timecounter</literal>
 	     ¦r¦êªº¨º´X¦æ¡C³Ì«á¤@¦æ¬O FreeBSD ¿ï¥Îªº¡A³q±`¬O
 	     <literal>TSC</literal>¡C</para>
 
 	  <screen>&prompt.root; <userinput>dmesg | grep Timecounter</userinput>
 Timecounter "i8254"  frequency 1193182 Hz
 Timecounter "TSC"  frequency 595573479 Hz</screen>
 
           <para>±z¥i¥H°õ¦æ &man.sysctl.3; ¬Ý¤@¤U
 	    <varname>kern.timecounter.hardware</varname> ³o­Ó­È°µ½T»{¡C</para>
 
 	  <screen>&prompt.root; <userinput>sysctl kern.timecounter.hardware</userinput>
 kern.timecounter.hardware: TSC</screen>
 
           <para>BIOS ¥i¯à¦b¤@¨Ç±¡§Î¤U·|§ó§ï TSC ªº®É¯ß&mdash;¦³®É­Ô¬O¦]¬°
 	    ¦b¨Ï¥Î¹q¦À¤u§@®É·|§ó§ï³B²z¾¹ªº³t«×¡A¥t¥~¤]¦³¥i¯à¬O¶i¤J¤F¬Ù¹q¼Ò
 	    ¦¡¡A¥i¬O FreeBSD ¨Ã¤£·|¹îı¨ì³o¨Ç½Õ¾ã¡A¦Ó·|µo¥Í®É¶¡¼W¥[©Î¬O´î
 	    ¤Öªº±¡§Î¡C</para>
 
           <para>¦b¤W­±ªº¨Ò¤l·í¤¤¡A§Ú­Ì¬Ý¨ìÁÙ¦³ <literal>i8254</literal>
 	    ³o­Ó®ÉÄÁ¥i¥H¿ï¾Ü¡A°õ¦æ &man.sysctl.3; ¥Î¤â°Êªº¤è¦¡±N³o­Ó­È¼g¤J
 	    <varname>kern.timecounter.hardware</varname> ¤¤¡C</para>
 
 	  <screen>&prompt.root; <userinput>sysctl -w kern.timecounter.hardware=i8254</userinput>
 kern.timecounter.hardware: TSC -&gt; i8254</screen>
 
           <para>³o¼Ë±zªºµ§°O«¬¹q¸£À³¸Ó´N¥i¥H«O«ù¥¿½Tªº®É¶¡¤F¡C</para>
 
           <para>¦pªG­nÅý³o­Ó§ó§ïªº°Ê§@¦A¨C¦¸¶}¾÷®É¦Û°Ê°õ¦æ¡A¦b
 	    <filename>/etc/sysctl.conf</filename> ùØ¥[¤J¤U­±³o¦æ¡C</para>
 
 	  <programlisting>kern.timecounter.hardware=i8254</programlisting>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question id="null-null">
           <para>¬°¤°»ò§Úªºµ§°O«¬¹q¸£µLªk¥¿½Tªº°»´ú¨ì PC card ¡H</para>
 	</question>
 
 	<answer>
           <para>³o­Ó°ÝÃD±`±`µo¥Í¦bÄé¤F¦h­Ó§@·~¨t²Îªºµ§°O«¬¹q¸£¤W¡C¦³¨Ç«D
 	    BSD ªº§@·~¨t²Î·|Åý PC card ªºµwÅé¸Ë¸m³B¦b¤@­Ó¤£¤@­Pªºª¬ºA¤U
 	    ¡]inconsistent state¡^¡C¨Ï±o <command>pccardd</command> ¦b°»
 	    ´ú³o¤ù¥d®É¡AµLªk§ì¨ì¥¿½Tªº«¬¸¹¡A¦Ó¬O
 	    <errorname>"(null)""(null)"</errorname>¡C</para>
 
           <para>±z»Ý­n²¾°£ PC card ´¡¼Ñªº¹q·½¥H­«¸m³o­ÓµwÅé¸Ë¸m¡C¤@­Ó¤èªk¬O
 	    ±N±zªºµ§°O«¬¹q¸£Ãö¾÷¡]¤£¬O¥ð¯v¼Ò¦¡¡A¤]¤£¬O«Ý©R¼Ò¦¡¡Q­n§¹¥þªºÃö
 	    ¾÷¡^¡Cµ¥­Ó´X¬íÄÁ¦A­«¶}¾÷¡C³o¼Ë±zªº PC card À³¸Ó´N¥¿±`¤F¡C</para>
 
           <para>¦³®É¦³¨Çµ§°O«¬¹q¸£ÁöµM¬Ý°_¨Ó¤w¸gÃö¾÷¤F¡A¦ý¹ê»Ú¤W¨Ã¨S¦³¡C
 	    ¦pªG±zµo²{¤W­±¨º­Ó¤èªk¨S¦³¥Î¡A½ÐÃö¾÷¡A²¾°£¹q¦À¡Aµ¥­Ó´X¬íÄÁ¡A
 	    §â¹q¦À¸Ë¤W¥hµM«á­«¶}¾÷¡C</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
         <question id="boot-read-error">
           <para>¬°¤°»ò¦b BIOS µe­±¤§«á¡AFreeBSD ªº boot loader Åã¥Ü
 	    <errorname>Read error</errorname> µM«á´N°±¤î¤£°Ê¤F¡H</para>
         </question>
 
         <answer>
           <para>³o¬O¦]¬°FreeBSD ªº boot loader µLªk¥¿½Tªº§ä¥XµwºÐªº
 	    geometry¡C³o¼Ëªº¸Ü¡A´N»Ý­n¦b¥Î fdisk ¤À³Î©Î¬O­×§ï FreeBSD
 	    ªº slice ®É¡A¤â°Ê±N¥¿½Tªº­È¿é¤J¶i¥h¤F¡C</para>
           <para>¥¿½TªºµwºÐ geometry ­È¦b BIOS ¸Ì­±¥i¥H¬dªº¨ì¡Cª`·N¸ÓµwºÐªº
 	    cylinders¡Aheads ¥H¤Î sectors ³o¨Ç¼Æ­È¡C</para>
           <para>¦b°õ¦æ &man.sysinstall.8;ªº fdisk ®É¡A«ö¤U <keycap>G</keycap>
 	    ¥H«K¤â°Ê³]©wµwºÐªº geometry¡C</para>
           <para>³o®É·|¦³¤@­Ó¹ï¸Ü®Ø¸õ¥X¨Ó¡A¸ß°Ý±z¦³Ãö cylinders¡Aheads ¥H¤Î
 	    sectors ³o¨ÇªF¦èªº­È¡C½Ð±N­è­è¦b BIOS ¬d¨ìªº¼Æ¦r¡A¥H / §@¤À¹j¿é
 	    ¤J¶i¥h¡C</para>
           <para>Á|¨Ò¨Ó»¡¡A¦pªG¬O 5000 cylinders¡A250 sectors ©M 60 sectors
 	    ´N¿é¤J <userinput>5000/250/60</userinput></para>
           <para>¿é¤J§¹«á½Ð«ö enter Áä½T»{¡A³Ì«á«ö¤U <keycap>W</keycap> Áä§â
 	    ·sªº¤À³Î°Ïªí¼g¤JµwºÐ·í¤¤¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="bootmanager-restore">
           <para>¥t¤@­Ó§@·~¨t²ÎºR·´¤F§Úªº Boot Manager¡C§Ú­n«ç»ò¼Ë¤~¯à§â¥¦ÁÙ
 	    ­ì¦^¨Ó¡H</para>
         </question>
 
         <answer>
           <para>°õ¦æ &man.sysinstall.8; ±µµÛ¿ï Configure¡AµM«á¿ï Fdisk¡C
 	    ¦A¨Ó¥Î<keycap>ªÅ¥Õ</keycap>Áä¿ï¾Ü­ì¥ý Boot Manager ©Ò¦bªºµwºÐ¡C
 	    «ö¤U <keycap>W</keycap> Áä¨Ó§@¼g¤Jªº°Ê§@¡C³o®É·|¸õ¥X¤@­Ó´£¥Ü
 	    °T®§¡A¸ß°Ý±z­n¦w¸Ë­þ¤@­Ó boot loader¡C½Ð¿ï¾Ü Boot Manager¡A
 	    ³o¼Ë´N¥i¥H±N¥¦ÁÙ­ì¤F¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="indefinite-wait-buffer">
           <para>³o­Ó¿ù»~°T®§¡G<errorname>swap_pager: indefinite
             wait buffer:</errorname> ¬O¤°»ò·N«ä©O¡H</para>
         </question>
 
         <answer>
           <para>³o­Ó°T®§¬O»¡¦³¤@­Ó°õ¦æµ{§Ç¥¿¦b¹Á¸Õ±N¤À­¶°O¾ÐÅé¡]page memory¡^
 	  ¼g¤JµwºÐ¤¤¡A¦Ó³o­Ó°Ê§@¹Á¸Õ¤F 20 ¬íÄÁ¤´µMµLªk¦¨¥\¡C³o­Ó¦³¥i¯à¬O¦]¬°
 	  µwºÐ¦³Ãa­y¡B¹q¸ô©Î±Æ½u¦³°ÝÃD¡B¥H¤Î¨ä¥L¸òµwºÐŪ¥X¼g¤J¦³ÃöªºµwÅé³]³Æ¡C
 	  ¦pªG¯uªº¬OµwºÐÃa­yªº°ÝÃD¡A±zÀ³¸Ó·|¦b
 	  <filename>/var/log/messages</filename>³o­ÓÀɮפ¤¡A©Î¬O¦b°õ¦æ
 	  <command>dmesg</command>³o­Ó«ü¥O«á¡A¬Ý¨ì¦³ÃöºÏºÐ¿ù»~ªº°T®§¡C
 	  ¦pªG¨S¦³¡A¨º»ò½ÐÀˬd±zªº±Æ½uÁÙ¦³±µÀY³s±µ¬O§_¨}¦n¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="touch-not-found">
-	  <para>Why does buildworld/installworld die with the message
-	    <errorname>touch: not found</errorname>?</para>
+	  <para>¬°¦ó¦b buildworld/installworld ®É¡A·|­w¦b
+	    <errorname>touch: not found</errorname> ªº¿ù»~°T®§?</para>
         </question>
 
 	<answer>
-	  <para>This error does not mean that the &man.touch.1; utility is
-	      missing. The error is instead propably due to the dates of the
-	      files being set sometime in the future. If your CMOS-clock is
-	      set to local time you need to run the command
-	      <command>adjkerntz&nbsp;-i</command> to adjust the kernel clock
-	      when booting into single user mode.</para>
+	  <para>³o¿ù»~°T®§¨Ã¤£¬O«ü &man.touch.1; µ{¦¡¤£¨£¤F¡A¨Æ¹ê¤W¥i¯à¬O¸ÓÀÉÀɮ׮ɶ¡³Q³]¬°¥¼¨Óªº®É¶¡¡C
+	      ­Y¾÷¾¹¤Wªº CMOS-clock ®ÉÄÁ³]©w¬°·í¦a®É¶¡
+	      («D®æªL«Âªv®É¶¡¡A¤ñ¦p¥xÆW®É¶¡¬° GMT +08:00 ¡A¤]´N¬O CST ¤¤­ì¼Ð·Ç®É¶¡)¡A
+	      ¨º»ò½Ð¦b¶}¾÷®É¡A¥ý¿ï single user ¼Ò¦¡¶i¤J¡AµM«á¥´ 
+	      <command>adjkerntz&nbsp;-i</command> 
+	      ¨Ó½Õ¾ã kernel clock »P¾÷¾¹¤Wªº CMOS-clock ¨Ó¦P¨B¡C</para>
 	</answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter id="commercial">
     <chapterinfo>
       <author>
 	<firstname>Vanilla</firstname>
 	<surname>Shu</surname>
 	<affiliation>
 	  <address><email>vanilla@FreeBSD.org</email></address>
 	</affiliation>
       </author>
     </chapterinfo>
 
     <title>°Ó·~³nÅé</title>
 
       <note>
         <para>³o¤@¸`ªº¤º®eÁÙ¬O¬Û·í¤Ö¡A¤£¹L§Ú­Ì·íµM§Æ±æ¦U­Ó¤½¥q¯à¬°¥¦¥[
 	  ÂI¤º®e :) FreeBSD ²Õ´©M¦C¦b³o¸Ìªº¥ô¦ó¤@®a¤½¥q³£¨S¦³ª÷¿ú¤Wªº§Q®`
 	  Ãö«Y¡A¦C¥X¨Ó¥u¬O¹ï¤j²³ªº¤½¶}ªA°È¡]¦P®É¤]»{¬°¦b FreeBSD ¤Wªº°Ó·~¿³
 	  ½ì¡A·|¹ï FreeBSD ªø¤[¥Í¾÷¦³·¥¥¿­±ªº®Ä¯q¡^¡C§Ú­Ì¹ªÀy°Ó·~³nÅ骺¼t°Ó
 	  §â¥L­Ìªº²£«~¥]¬A¦b¤U­±ªº¦W³æ¤¤¡A¦b
 	  <ulink URL="../../../../commercial/index.html">Vendors page</ulink>
 	  ¥i¥H¬Ý¨ì¸ûªø¦Cªí¡C</para>
       </note>
 
     <qandaset>
       <qandaentry>
         <question id="officesuite">
           <para>¦b­þÃä§ä¨ìµ¹ FreeBSD ¥Îªº Office ®M¥ó©O¡H</para>
         </question>
         <answer>
 	  <itemizedlist>
   	    <listitem>
 	      <para><ulink url="http://www.freebsdmall.com/">FreeBSD Mall</ulink>
                 ´£¨Ñ¤F <ulink url="http://www.vistasource.com/">VistaSource</ulink>
 		ªº ApplixWare 5 ªº FreeBSD ª©¥»¡C</para>
 	
 	      <para>ApplixWare ¬O¤@®M°Ó·~ª©¥»ªº Office ®M¥ó¡A¥L´£¨Ñ¤F
 	        ¤å¥ó³B²z¡B¸Õºâªí¡B¦V¶qø¹Ïµ¥¬ÛÃöµ{¦¡¡C</para>
 
 	      <para>ApplixWare ¦P®É¤]¬O FreeBSD Mall's BSD Desktop Edition
 	        ªº¤@³¡¥÷¡C</para>
 
   	    </listitem>
 	    <listitem>
 	      <para>Linux ª©¥»ªº <ulink url="http://www.sun.com/staroffice/">StarOffice</ulink>
 	        ¥i¥H«Ü¥¿±`ªº¦b FreeBSD ¤U°õ¦æ¡A¥i¥H³z¹L <ulink 
 	        url="../handbook/ports.html">FreeBSD Ports collection</ulink>
 		¨Ó¦w¸Ë Linux ª©¥»ªº StarOffice¡C¦Ó open-source <ulink
 	        url="http://www.openoffice.org/">OpenOffice</ulink> «Ü§Ö±o
 		¤]¥i¥H¦b FreeBSD ¤W¥¿±`ªº°õ¦æ¡C</para>
 	    </listitem>
 	  </itemizedlist>
         </answer>
       </qandaentry>
       <qandaentry>
         <question id="motif">
           <para>¦b­þÃä§ä¨ìµ¹ FreeBSD ¥Îªº Motif¡H</para>
         </question>
 
         <answer>
 	  <para>Open Group ÄÀ¥X¤F Motif 2.1.30 ªº­ì©l½X¡A¥i¥H³z¹L
 	    <literal>open-motif</literal> package ¦w¸Ë¡A©Î¬O¥Ñ ports ¦Û¦æ
 	    ½sĶ¡C¬ÛÃöªº¸ê°T¡A½Ð°Ñ¦Ò handbook ¤¤ªº <ulink
 	    url="../handbook/ports.html">ports</ulink> ³¹¸`¡C
 
 	    <note>
 	      <para>Open Motif ¥u¯à¦b¦P¼Ë¤]¬O <ulink
 	        url="http://www.opensource.org/">open source</ulink>
 		ªº§@·~¨t²Î©Î­p¹º¤¤¨Ï¥Î¡C</para>
 	    </note>
 	  </para>
 
           <para>¥t¥~¡A¤]¬O¦³°Ó·~ª©¥»ªº Motif ¦s¦b¡C¤]³\³oºØª©¥»ªº Motif
 	    ¤£¬O§K¶Oªº¡A¦ý¬Oµ´¹ï¤¹³\¥Î¦b closed-source ªºÀô¹Ò¤U¡C
 	    <link linkend="apps2go">Apps2go</link> ´£¨Ñ¤F³Ì«K©yªº FreeBSD
 	    (¥]¬A i386 ¸ò alpha)ª©¥»ªº ELF Motif 2.1.20 ®M¥ó¡C
 	    <anchor id="apps2go"></para>
 
           <para>¥Ø«e´£¨Ñ¨âºØ¤£¦PÀô¹Òªºª©¥»¡A <quote>µo®i¥Îª©¥»</quote> ¤Î
 	    <quote>runtime ª©¥»</quote> ¡C³o¨âºØ®M¥ó³£¥]¬A¡G</para>
 
             <itemizedlist>
               <listitem>
                 <para>OSF/Motif manager, xmbind, panner, wsm.</para>
               </listitem>
 
               <listitem>
                 <para>Development kit with uil, mrm, xm, xmcxx, include
                   and Imake files.</para>
               </listitem>
 
               <listitem>
                 <para>Static and dynamic ELF libraries (for use with
                   FreeBSD 3.0 and above).</para>
               </listitem>
 
               <listitem>
                 <para>Demonstration applets.</para>
               </listitem>
             </itemizedlist>
 
           <para>¦]¬° <emphasis>Apps2go</emphasis> ¤]¦³´£¨Ñ NetBSD ©M OpenBSD
 	    ªºª©¥»¡A©Ò¥H¦b­qÁʮɽЯS§O«ü©w¬O­n FreeBSD ª©¥»ªº Motif¡I
 	    ¥L­Ì¥Ø«e¥u´£¨Ñ¥H FTP ªº¤è¦¡¨ú±o³o¥÷®M¥ó¡C</para>
 
             <variablelist>
               <varlistentry>
                 <term>§ó¦h¸ê°T</term>
                 <listitem>
                   <para><ulink URL="http://www.apps2go.com/">
                     Apps2go WWW page</ulink></para>
                 </listitem>
               </varlistentry>
 
               <varlistentry>
                 <term>©Î</term>
                   <listitem>
                     <para>
                       <email>sales@apps2go.com</email> ©Î
                       <email>support@apps2go.com</email>
                       </para>
                   </listitem>
                 </varlistentry>
 
                 <varlistentry>
                   <term>©Î</term>
                   <listitem>
                     <para>phone (817) 431 8775  or +1 817 431-8775</para>
                   </listitem>
                 </varlistentry>
               </variablelist>
 
           <para>¤]¥i¥HÁpµ¸ <link linkend="metrox">Metro Link</link>
             ¨ú±oµ¹ FreeBSD ELF©Î a.out ª©¥»ªº Motif 2.1 ®M¥ó¡C</para>
 
           <para>³o¥÷®M¥ó¥]¬A¡G</para>
             <itemizedlist>
               <listitem>
                 <para>OSF/Motif manager, xmbind, panner, wsm.</para>
               </listitem>
 
               <listitem>
                 <para>Development kit with uil, mrm, xm, xmcxx, include
                   and Imake files.</para>
               </listitem>
 
               <listitem>
                 <para>Static and dynamic libraries (specify ELF for use
                   with FreeBSD 3.0 and later; or a.out for use with FreeBSD
                   2.2.8 and earlier).</para>
               </listitem>
 
               <listitem>
                 <para>Demonstration applets.</para>
               </listitem>
 
               <listitem>
               <para>Preformatted man pages.</para>
               </listitem>
 
               </itemizedlist>
 
           <para>¥Ñ©ó <emphasis>Metro Link</emphasis> ¤]¦³´£¨Ñ Linux ªºª©¥»¡A
 	    ©Ò¥H­qÁʮɭn¯S§O«ü©ú¬O FreeBSD ª©¥»ªº Motif¡I ¥i¥H¥Ñ¥úºÐ©Î±q FTP
 	    ¨Ó¨ú±o³o­Ó®M¥ó¡C</para>
 
           <para>Ápµ¸ <link linkend="xig">Xi Graphics</link> ¡A¥L­Ì´£¨Ñ¤F¤@­Ó
 	    FreeBSD a.out ®æ¦¡ªº Motif 2.0 ®M¥ó¡C</para>
 
           <para>¦b³o®M¥ó¤¤¥]¬A¤F¡G</para>
             <itemizedlist>
               <listitem>
                 <para>OSF/Motif manager, xmbind, panner, wsm.</para>
               </listitem>
 
               <listitem>
                 <para>Development kit with uil, mrm, xm, xmcxx, include
                   and Imake files.</para>
               </listitem>
 
               <listitem>
                 <para>Static and dynamic libraries (for use with FreeBSD
                   2.2.8 and earlier).</para>
               </listitem>
 
               <listitem>
                 <para>Demonstration applets.</para>
               </listitem>
 
               <listitem>
                 <para>Preformatted man pages.</para>
               </listitem>
             </itemizedlist>
 
           <para>¦b§A¸ò¥L­Ì­qÁÊ Motif ®É¡A½Ð¤@©wµù©ú§A­nªº¬O FreeBSD ªºª©¥»¡I
 	    ¦]¬° <emphasis>Xi Graphics</emphasis> ¤]¦P®É´£¨Ñ¤F BSDI ¸ò Linux
 	    ª©¥»ªº Motif¡C¥Ø«eµo¦æªºª©¥»¬O©ñ¦b¥|¶ôºÏ¤ù¤¤¡A±N¨Ó¥L­Ì·|±N©Ò¦³ªº
 	    ªF¦è³£©ñ¨ì¥úºÐ¸Ì¡A´N¹³¥L­Ì©Òµo¦æªº CDE ¤@¼Ë¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="cde">
           <para>¦b­þÃä§ä¨ìµ¹ FreeBSD ¥Îªº CDE¡H</para>
         </question>
 
         <answer>
           <para><link linkend="xig">Xi Graphics</link> ¥H«e¦³½æ FreeBSD ¥Îªº
 	   CDE¡A¤£¹L²{¦b¤w¸g°±¤îµo°â¤F¡C</para>
 
           <para><ulink URL="http://www.kde.org/">KDE</ulink> is an open
             source X11 desktop which is similar to CDE in many respects.
             You might also like the look and feel of <ulink
             URL="http://www.xfce.org/">xfce</ulink>. KDE and xfce are both
             in the <ulink URL="../../../../ports/index.html">ports
             system</ulink>.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="commercial-xserver">
           <para>¦³¨S¦³­n¿ú¡A¦ý¬O°ª®Ä²vªº X servers¡H</para>
         </question>
 
         <answer>
           <para>¦³¡A <ulink URL="http://www.xig.com/">Xi Graphics</ulink>
             ©M <ulink URL="http://www.metrolink.com/">Metro Link</ulink>
             ³£¦³´£¨Ñµ¹ FreeBSD¡]©Î¨ä¥L Intel ¥­¥x¤W¡^¥Îªº X µøµ¡¥[³t²£«~¡C
 	  </para>
 
           <para>Metro Link °ª®Ä¯à X Server ¨Ï¥Î¤F FreeBSD ¤º«Øªº package
 	    ¥]¸Ë¤è¦¡, ¦]¦¹³]©w¤Q¤À®e©ö¡A¤ä´©¥Ø«e¥«­±¤W¦U¤j¼tµPªºÅã¥Ü¥d¡C
 	    ¥Ø«e¥u´£¨Ñ binary ®æ¦¡ÀɮסA¥i¥H±q FTP ¯¸¬Û·í¤è«K¦aª½±µ¤U¸ü¡A
 	    ¨Ã¥B Metro Link ³o®M²£«~ªº»ù®æ¬O«D±`¦X²zªº $39¡C
 	    <anchor id="metrox"></para>
 
           <para>Metro Link ¦P®É´£¨Ñ FreeBSD ¤Wªº ELF ©M a.out ®æ¦¡ªº Motif
 	    ¡]©¹¤W­±¬Ý¬Ý¡^¡C</para>
 
             <variablelist>
               <varlistentry>
                 <term>§ó¦hªº¸ê°T</term>
                 <listitem>
                   <para><ulink URL="http://www.metrolink.com/">
                     Metro Link WWW page</ulink></para>
                 </listitem>
               </varlistentry>
 
               <varlistentry>
                 <term>©Î</term>
                 <listitem>
                   <para><email>sales@metrolink.com</email>
                    ©Î <email>tech@metrolink.com</email>
                     </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 Server ¦³«D±`²³æªº³]©w¤è¦¡¡A
 	    ¨Ã¥B¤ä´©¤F¥Ø«e¥«­±¤W·í¬õªº¦U¤j¼tµPªºÅã¥Ü¥d¡C¥¦¥uµ¹§A Binary ÀɮסA
 	    ¬O¥ÎºÏ¤ùªº¤è¦¡µo¦æ¡AFreeBSD ¸ò Linux ª©¥»³£¬Û¦P¡CXi Graphics ¦P®É
 	    ¤]´£¨Ñ¤F±Mªùµ¹ laptop ¥Îªº°ª®Ä¯à X Server¡C<anchor id="xig"></para>
 
           <para>5.0 ª©¦³´£¨Ñ§K¶Oªº <quote>compatibility demo</quote> ª©¥»</para>
 
           <para>Xi Graphics ¤]¦³¦b½æ FreeBSD ¥Îªº Motif ¸ò CDE¡]©¹¤W­±¬Ý¬Ý¡^¡C
 	    </para>
 
             <variablelist>
               <varlistentry>
                 <term>§ó¦hªº¸ê°T</term>
                 <listitem>
                   <para><ulink URL="http://www.xig.com/">
                     Xi Graphics WWW page</ulink></para>
                 </listitem>
               </varlistentry>
 
               <varlistentry>
                 <term>©Î</term>
                   <listitem>
                     <para><email>sales@xig.com</email>
                       ©Î <email>support@xig.com</email>
                       </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>¦b FreeBSD ¤W¦³¥ô¦óªº¸ê®Æ®w¶Ü¡H</para>
         </question>
 
         <answer>
           <para>¦³! ½Ð¬Ý FreeBSD ºô¯¸¤W <ulink
             URL="../../../../commercial/software_bycat.html#CATEGORY_DATABASE">
             °Ó·~³nÅ餽¥q </ulink> ³o¤@³¡¥÷¡C</para>
 
           <para>ÁÙ¦³½Ð°Ñ¦Ò ports ¤¤ <ulink
             URL="../../../../ports/databases.html">
             Databases</ulink> ¬ÛÃöªº¦¬¶°¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="oracle-support">
           <para>¥i¥H¦b FreeBSD ¤W°õ¦æ Oracle ¶Ü¡H</para>
         </question>
 
         <answer>
           <para>¥i¥H¡A¤U­±³o­Óºô­¶·|»¡©ú¦p¦ó¦b FreeBSD ¤W°õ¦æ Linux
 	    ª©ªº Oracle¡G</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">
     <chapterinfo>
       <author>
 	<firstname>Kang-min</firstname>
 	<surname>Liu</surname>
 	<affiliation>
 	  <address><email>gugod@gugod.org</email></address>
 	</affiliation>
       </author>
     </chapterinfo>
 
     <title>¤@¯ëÀ³¥Îµ{¦¡</title>
 
     <qandaset>
       <qandaentry>
         <question id="user-apps">
 	  <para>¶â..§Ú­n¦b­þ§ä¨ì§Ú­nªºµ{¦¡©O?</para>
 	</question>
 
 	<answer>
 	  <para>½Ð¬Ý¬Ý <ulink URL="../../../../ports/index.html">ports 
 	    ¥Ø¿ý</ulink> §a¡C³oÃ䦳¥÷¤w¸g port ¨ì FreeBSD ªº³nÅé¦Cªí¡C
 	    ¥Ø«e¦³¶W¹L &os.numports; ­Ó³nÅé¤w¸g³Qport ¨ì FreeBSD ¤W¡A¨Ã¥B¨C¤Ñ
 	    ³£¦b¼W¥[¤¤¡C©Ò¥H¦³ªÅ´N¦h¬Ý¬Ý³o¥÷¦Cªí¡A¤£µM§A¤]¥i¥H­q¾\ 
 	    <literal>freebsd-announce</literal> <link linkend="mailing">
 	    ³o¥÷ mailing list</link>¡A·|¦³¤H±N¨C­Ó¬P´Á³Ì·sªº³nÅé¦Cªí¶K¦b
 	    ¤W­±¡C</para>
   
 	  <para>¤j³¡¥÷ªº ports À³¸Ó³£¥i¥H¦b 2.2¡A3.0 ¸ò 4.0 ªº¨t²Î¤W¨Ï
             ¥Î¡A¨Ã¥BÁÙ¦³³¡¥÷ªº ports ¥i¥H¦b 2.1.x ªº¨t²Î¤W¹B§@¡C¨C¦¸
             ·í FreeBSD release ®É¡A³£·|¦³¤@¥÷ ports tree ³Q©ñ¦b³o¤@­Ó
             release cd ¸Ì­±ªº <filename>ports/</filename> ¥Ø¿ý¸Ì¡C</para>
   
           <para>§Ú­Ì¤]¤ä´©¤@ºØ¥s <quote>package</quote> ªº·§©À¡A°ò¥»¤W
             ´N¬O gzip À£ÁY¡B¥i¥Î¨Óµo¦æªº binary ÀɮסA¦ý¬O¸Ì­±ÂäF¤@
             ¨Ç¬Û·í¦³¥Îªº¸ê°T¡A¥i¥Hµ¹¦UºØ¦Û­q¦w¸Ë¨Ó¨Ï¥Î¡C¨Ï¥ÎªÌ¤£¥²ª¾
             ¹D¬Y­Ó package ¸Ì¨s³º¦³¥]¬A­þ¨ÇÀɮסA´N¥i`¥H«Ü¤è«K¦a­«½Æ±N
             ¥¦¦w¸Ë/¤Ï¦w¸Ë¡C</para>
   
           <para>§A¥i¥H°õ¦æ <filename>/stand/sysinstall</filename> «á¡A
             ¦b post-configuration ¿ï³æ¤U¿ï¾Ü package ³o­Ó¦w¸Ë¿ï¶µ¡F©Î
             ¬O¹ï¬Y­Ó¦³¿³½ìªº package ÀÉ®×°õ¦æ &man.pkg.add.1;
 	    §â¥¦¸Ë°_¨Ó¡CPackage Àɮ׳q±`¥H <filename>.tgz</filename>
 	    §@¬°©µ¦ùÀɦW¡A¤â¤W¦³ FreeBSD CDROM ªº¤H¥i¥H¦b
 	    <filename>packages/All</filename> ³o­Ó¥Ø¿ý¤U§ä¨ì³oÃþÀɮסC
 	    ¹ï¤£¦Pªº FreeBSD ª©¥»¡A¤]¥i¥H±q¤U¦C¦ì§}¥Ñºô¸ô¤W¨ú±o¡G</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.2-release/3.2-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-current/">
                    ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-current/</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>©Î¬OÂ÷§A³Ìªñªº mirror ¯¸¡C</para>
   
           <para>­nª`·Nªº¬O¡A¦]¬°·sªº port ¤@ª½¦b¼W¥[¤¤¡A©Ò¥H¨Ã¤£¬O©Ò¦³ port
 	    ³£¦³¬Û¹ïÀ³ªº package¡C³Ì¦n©w®ÉÀˬd<ulink
             URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/">ftp.FreeBSD.org</ulink>
             ¡A¬Ý¬Ý¦³­þ¨Ç package ¥i¥H¥Î¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="missing-libcso30">
           <para>§Ú¥i¥H¦b­þÃä§ä¨ì libc.so.3.0?</para>
         </question>
 
         <answer>
           <para>§A¥i¯à¦b¤@¥x 2.1.x ªº¾÷¾¹¤W¡A¶]µÛµ¹ 2.2/3.x/4.0 ªº³nÅé¡C
             ½Ð¦A©¹¤W­±¤@­Ó³¹¸`¬Ý¡A¥¿½Tªº¨ú±oµ¹§A¾÷¾¹¥Îªº port/package¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="missing-libcso40">
           <para>¬°¦ó§Ú±o¨ì¤F³o­Ó°T®§ ?<errorname>Error: can't find
             libc.so.4.0</errorname>?</para>
         </question>
 
         <answer>
 	  <para>§A¤£¤p¤ß§ì¤Fµ¹ 4.X ¤Î 5.X ¨t²Î¥Îªº package¡A¨Ã¥B¹Á¸ÕµÛ
             ¥h¸Ë¦b§Aªº 2.X ©Î 3.X ªº¨t²Î¤W­±¡C½Ð¤U¸ü¥¿½Tª©¥»ªº package¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="emul">
           <para> ghostscript ¦b§Úªº 386/486SX ¤W¦³ÂI°ÝÃD©O¡I</para>
         </question>
 
         <answer>
           <para>§A¨S¦³¯BÂI¹Bºâ¾¹¡A¹ï§a¡H§A¥²¶·¦b§Aªº kernel ¤¤¥[¤J¼Æ¾Ç
             ¹Bºâ¼ÒÀÀ¾¹¡A§A¥i¥H¸òµÛ¤U­±ªº¨BÆJ°µ¡A¨Ã¦b§ó§ï¹L§Aªº kernel ³]©w
 	    ÀÉ«á¡A­«·s½sĶ¹L¤@¦¸¡C</para>
 
           <programlisting>options GPL_MATH_EMULATE</programlisting>
 	  
             <note>
 	      <para>·í§A¥[¤J¤W¤@¦æªº¦P®É¡A§A¥²¶·±N
 	        <literal>MATH_EMULATE</literal> ²¾°£±¼¡C</para>
             </note>
         </answer>
       </qandaentry>
       
       <qandaentry>
         <question id="sco-socksys">
           <para>¬°¤°»ò·í§Ú°õ¦æ SCO/iBCS2 ªºµ{¦¡®É¡A¥¦¦b
 	    <errorname>socksys</errorname> ³o­Ó¦a¤è¥X¤F°ÝÃD¡H
 	    (FreeBSD 3.0 ¥H¤Î§ó¦­ªºª©¥»¤~¦³¦¹°ÝÃD¡C)</para></question>
       
         <answer>
           <para>§A¥²¶·¥ý­×§ï <filename>/etc/sysconfig</filename> (©Î¬O
             <filename>/etc/rc.conf</filename>, ½ÐŪ &man.rc.conf.5;)
             ³oÀɮ׳̫á¤@­Ó³¹¸`¡A±N¤U­±©ÒÁ¿¨ìªºÅܼƳ]¦¨
 	    <literal>YES</literal>¡G</para>
 
           <programlisting># Set to YES if you want ibcs2 (SCO) emulation
 	    loaded at startup ibcs2=NO</programlisting>
         
           <para>³o·|¦b¶}¾÷®É±N ibcs2 ³o¤@­Ó kernel ¼Ò²Õ¸ü¤J¡C</para>
         
           <para>§AÁÙ­n±N§Aªº /compat/ibcs2/dev §ï¦¨¤U­±³o¼Ë¡G</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>§A¥u»Ý­n±N socksys Âà¦V¨ì <devicename>/dev/null</devicename>
             (½ÐŪ &man.null.4;) ¥hÄF¹L open &amp; close ªº°Ê§@¡C¦b -current
 	    ¸Ì­±ªº ibcs2 ¬ÛÃöµ{¦¡½X±N·|³B²z¨ä¾lªº³¡¥÷¡A³oºØ§@ªk¤ñ¥H«eªº¤è¦¡
 	    °®²b¤Ó¦h¤F¡C°²¦p§A·Q­n¨Ï¥Î <devicename>spx</devicename> ¤è­±ªº
 	    µ{¦¡¡A¦b§Aªº®Ö¤ß³]©wÀɸ̭± ¥[¤W<literal>SPX_HACK</literal>¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="configure-inn">
           <para>§Ú­n¦p¦ó¦b§Úªº¾÷¾¹¤W³]©w INN (Internet News)¡H</para>
 	</question>
       
         <answer>
           <para>¦b§A¨Ï¥Î package ©ÎªÌ¬O port ¦w¸Ë§¹ inn ¤§«á¡A<ulink
            URL="http://www.cis.ohio-state.edu/~barr/INN.html">Dave Barr's
            INN Page</ulink> ¬O­Ó«D±`¦nªº¶}©l¡A§A¥i¥H¦b¨ºÃä§ä¨ìINN ªº FAQ¡C
            </para>
         </answer>
       </qandaentry>
       
       <qandaentry>
         <question id="ms-frontpage">
 	  <para>§Ú¸Ó¨Ï¥Î¨º­Óª©¥»ªº Microsoft FrontPage¡H</para>
 	</question>
 	
 	<answer>
           <para>Use the Port, Luke¡I¦b ports tree ¤¤¤w¸g¦³¤@­Ó¥]§t FrontPage
 	    ªº Apache ª©¥»¤F¡C</para>
         </answer>
       </qandaentry>
       
       <qandaentry>
         <question id="java">
 	  <para>FreeBSD ¤ä´© Java ¶Ü¡H</para>
 	</question>
 	
 	<answer>
 	  <para>¦³¡A½Ð¬Ý <ulink URL="../../../../java/index.html">
 	    http://www.FreeBSD.org/java</ulink>.</para>
         </answer>
       </qandaentry>
       
       <qandaentry>
         <question id="ports-3x">
           <para>¬°¤°»ò§ÚµLªk¦b 3.X-STABLE ¾÷¾¹¤W¶¶§Q½s¦n³o­Ó port?</para>
         </question>
 
         <answer>
       	  <para>¦pªG§Aªº FreeBSD ª©¥»¬Û¸û -CURRENT ©Î -STABLE ¤§¤U¬O«Ü¥j
 	    ¦­ªº¸Ü¡A©Î³\§A·|»Ý­n¤@­Ó¤É¯Å ports ªº¤u¨ã¡A¦b
 	    <ulink URL="../../../../ports/index.html">
 	    http://www.FreeBSD.org/ports/</ulink>¡C¦pªG§A¥H±N¨ä§ó·s«o¤´µL¥Î¡A
 	    ¨º»ò¤@©w¬O¬Y¤H§ó°Ê¤§«á³y¦¨ -CURRENT ¤~¯à¥Î¡A-STABLE µLªk¥Îªº±¡ªp¡C
 	    ¥Ñ©ó ports ¤º©Ò¦¬¶°ªº³nÅé¦b -CURRENT ©Î¬O -STABLE ¤W³£­n¯à¥Î¡A
 	    ©Ò¥H½Ð¾¨³t°e¥XÃö©ó¦¹°ÝÃDªºÂγø§i¡F½Ð¨Ï¥Î &man.send-pr.1; ³o­Ó«ü
 	    ¥O¨Ó°eÂγø§i¡C</para>
         </answer>
       </qandaentry>
       
       <qandaentry>
         <question id="find-ldso">
           <para>¨º¸Ì¥i¥H§ä±o¨ì ld.so¡H</para>
 	</question>
 	
 	<answer>
           <para>¦³¨Ç a.out ®æ¦¡ªºÀ³¥Îµ{¦¡·|»Ý­n a.out ®æ¦¡ªº¨ç¦¡®w¡A
 	    Netscape Navigator ´N¬O¤@­Ó¨Ò¤l¡C¤£¹L¥Î ELF ¨ç¦¡®w½s°_¨Ó
 	    ªº FreeBSD ¹w³]¨Ã¤£·|¦w¸Ëªº a.out ¨ç¦¡®w¡A©Ò¥H±z¥i¯à·|±o
 	    ¨ìÃþ¦ü§ä¤£¨ì <filename>/usr/libexec/ld.so</filename> ªº©ê«è°T
             ®§¡C¦pªG»¡±zªº¨t²Î¦³³o¦w¸Ë a.out ¨ç¦¡®wªº¥²­n¡A³o¨Ç¨ç¦¡®w
 	    (compat22) ¤]¯à°÷§Q¥Î &man.sysinstall.8; ¨Ó¦w¸Ë¡C©ÎªÌ§Q¥Î
 	    FreeBSD ­ì©l½X¨Ó¦w¸Ë¡G</para>
 
           <screen>&prompt.root; <userinput>cd /usr/src/lib/compat/compat22</userinput>&prompt.root; <userinput>make install clean</userinput></screen>
 
 	  <para>¦pªG§A§Æ±æ¨C¦¸ <command>make world</command> ®É·|¦Û°Ê§ó·s
             compat22 ¨ç¦¡®w¡A¨º»ò­×§ï <filename>/etc/make.conf</filename>¡A
             ¥[¤J <varname>COMPAT22=YES</varname>¡C³o¨Ç¬Û®e©ó¥j¦Ñª©¥»ªº¨ç¦¡®w
             ¤w¸g¨S¤°»ò¦b§ó·s¤F¡A©Ò¥H¤@¯ë»¡¨Ó¬O¤£»Ý­n³o¼Ëªº¡C</para>
         
           <para>¦P®É¤]½Ð±z¬Ý¤@¤U 3.1-RELEASE ©M 3.2-RELEASE ªº°É»~ªí(ERRATA)¡C</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ports-update">
           <para>§Ú§ó·s¤F¨t²Î­ì©l½X¡A²{¦b§Ú­n«ç¼Ë¤É¯Å¬Y­Ó¤w¸g¦w¸Ë¤W
 	    ªº ports ?</para>
         </question>
 
         <answer>
           <para>FreeBSD ¥»¨­¨Ã¨S¦³¦Û°Ê¤É¯Å ports ªº¤u¨ã¡A¦ý¦³¤@¨Ç¥i¥HÅý¤É¯Å
             ²¤Æ¤@¨Çªº¤pµ{¦¡¡C§A¤]¥i¥H¦Û¤v¸Ë¤WÃB¥~ªº¤u¨ã¨Ó³B²z¡C</para>
       
           <para>&man.pkg.version.1; «ü¥O¥i¥H¦Û°Ê²£¥Í¥Î¨Ó¹F¨ì¦Û°Ê¤É¯Å¨ì
 	    ports tree ³Ì·sª©¥»ªº script¡C</para>
       
           <screen>&prompt.root; <userinput>pkg_version <option>-c</option> > <replaceable>/tmp/myscript</replaceable></userinput></screen>
       
           <para><emphasis>¤@©w­n</emphasis>¦b¤â°Ê­×§ï¤@¤U²£¥Í¥X¨Óªº script¡C
             ¥Ø«eªº &man.pkg.version.1; ¦b script ³Ì«e­±¥[¤J &man.exit.1; ±j
             ­¢§A¥h­×§ï¥¦¡C</para>
       
           <para>§AÀ³±N°õ¦æ script ©Ò²£¥Íªº¿é¥X°O¿ý¤U¨Ó¡A¦]¬°¸Ì­±·|¦³°O¸ü¬Y¨Ç
             ©|¥¼¤É¯Å¦ý¤w¸g§ó·sªº ports¡C¤£¹L§A¤£¤@©w­n¥h¤É¯Å¥¦­Ì¡C³q±`¬O¦]¬°
             ¦³¬Y­Ó¦@¥Îªº¨ç¦¡®w¤w¸g§ïÅܪ©¥»¸¹¤F¡A¤~­n¥h­«½s¤@¦¸¨º¨Ç¨Ï¥Î¨ì¸Ó¨ç
             ¦¡®wªº ports¡C</para>
       
           <para>¦pªG§AªºµwºÐªÅ¶¡«Ü°÷¡A¨º»ò¥i¥H¥Î <command>portupgrade</command>
 	    ³o­Ó¤u¨ã¨Ó°µ¥þ¦Û°Ê³B¸Ì¡C<command>portupgrade</command> ¸Ì­±¤]¦³
 	    ¤@¨Ç¤pµ{¦¡¨Ó²¤Æ package ¤É¯Å¡A¥¦¦b
 	    <filename role="package">sysutils/portupgrade</filename>¡C
 	    ³o­Ó¤u¨ã¬O¥Î Ruby ³o­Ó»y¨¥¼gªº¡A©Ò¥H¨Ã¤£¾A¦X¥[¤J¨ì FreeBSD ªº­ì
 	    ©l½X¤¤¡A¤£¹L¨Ã¤£·|¦]¦¹Åý¬Y¨Ç¤H¤£¥Î¥¦¡C</para>
       
           <para>¦pªG§Aªº¨t²Î¤@ª½³£³B©ó¶}¾÷ª¬ºA¡A¥i§Q¥Î &man.periodic.8; ¨t²Î¡A
             ¨C­Ó¬P´Á²£¥Í¤@±i»Ý­n¤É¯Åªº²M³æ¡C¥u­n¦b
             <filename>/etc/periodic.conf</filename> ¥[¤J
             <literal>weekly_status_pkg_enable="YES"</literal> ´N¥i¥H¤F¡C</para>
         </answer>
       </qandaentry>
       
       <qandaentry>
         <question id="minima-sh">
           <para>¬°¤°»ò <command>/bin/sh</command>³o»òªº¤p¡H¬°¤°»ò FreeBSD
             ¤£§ï¥Î <command>bash</command> ©ÎªÌ¬O¨ä¥L¤ñ¸û±j®«ªº shell¡H</para>
         </question>
       
         <answer>
           <para>¦]¬° POSIX »¡¡A¸Ó­n¦³³o»ò¼Ëªº¤@­Ó shell ¦b¤~¦æ¡C</para>
       
           <para>¤ñ¸ûÁcº¾ªºµª®×¡G³\¦h¤H»Ý­n¼g¥i¥H¸ó«Ü¦h¥­¥xªº shell script ¡C
             ³o¤]¬O¬°¦ó POSIX ±N shell ¥H¤Î¤u¨ã©RºÙ³£©w¸qªº«D±`¸Ô²Óªº½t¬G¡C
             ¤j³¡¥÷ªº script ³£¾A¥Î©ó Bourne shell¡A¤S¦]¬°¦³´X­Ó­«­nªº
             ¼gµ{¦¡©Ò¥Î¨ìªºµ{¦¡©ÎªÌ¨ç¦¡ (&man.make.1; , &man.system.3;,
             &man.popen.3;, ÁÙ¦³¦b Perl ©ÎªÌ Tcl ¸Ì­±©I¥s¨t²Îµ{¦¡ªº¦a¤è)
             ³£«ü©w¥Î Bourne shell ¡C¨º»ò¦]¬° Bourne Shell ¦p¦¹ªº¼sªx±`¥Î¡A
             ¨º»ò¥¦ªº°õ¦æ®Ä²v«K«Ü­«­n¡A§Ö³t¬O¥¦¨M©w©Êªº­nÂI¤§¤@¡AÁÙ­n¤£¦û¤Ó¦h
             °O¾ÐÅé¡C</para>
       
           <para>¥Ø«eªº <command>/bin/sh</command> ¤w¬O§Ú­Ì¹Ã¤ßÃw¦å¤§§@¡A¥¦¤w
             ¸gºÉ¶q¦a²Å¦X¼Ð·Ç³W©w¡C¬°¤FÅý¥¦«D±`¤p¡A§Ú­Ì®³±¼¤F¤@¨Ç¨ä¥L shell
             ¦³ªº¤è«K¥\¯à¡C³o¤]¬O¬°¤°»ò ports ¸Ì­±ÁÙ¦³«Ü¦h±j®«ªº shell ¡A¹³¬O
             bash, scsh, tcsh ¥H¤Î zsh ¡C (§A¥i¥H¦Û¤v¤ñ¸û¤@¤U³o¨Ç shell °õ¦æ
             ®É©Ò¦ûªº°O¾ÐÅé¤j¤p¡A¥h¬Ý¬Ý <command>ps -u</command> ¦C¥X¨Óªº
             <quote>VSZ</quote> ©M <quote>RSS</quote> ³o¨â­ÓÄæ¦ì´Nª¾¹D¤F¡C)
             </para>
          </answer>
       </qandaentry>
       
       <qandaentry>
         <question id="netscape-slow-startup">
           <para>¬°¤°»ò Netscape ©M Opera ­nªá¦n¤[ªº®É¶¡¤~¯à±Ò°Ê¡H</para>
       </question>
       
       <answer>
         <para>³q±`¬O¦]¬°§Aªº DNS ¨S¦³³]©w¦n¡C Netscape ¸ò Opera ¦b±Ò°Êªº®É­Ô
 	  ³£·|¥hÀˬd¤@¤U DNS¡Cª½¨ì DNS ¦³¦^À³¡A©ÎªÌ¬OÂ_©wºô¸ô¥Ø«e¬OÂ_½u¤§«á¡A
 	  ¥¦­Ì¤~·|Åã¥Üµe­±¥X¨Ó¡C</para>
         </answer>
       </qandaentry>
     </qandaset>
   </chapter>
       
   <chapter id="kernelconfig">
     <chapterinfo>
       <author>
 	<firstname>Kang-min</firstname>
 	<surname>Liu</surname>
 	<affiliation>
 	  <address><email>gugod@gugod.org</email></address>
 	</affiliation>
       </author>
     </chapterinfo>
 
     <title>®Ö¤ß³]©w</title>
 
     <qandaset>
       <qandaentry>
         <question id="make-kernel">
           <para>§Ú·Q¦Û­q®Ö¤ßµ{¦¡¡A³o·|«Ü§xÃø¶Ü¡H</para>
         </question>
 
         <answer>
           <para>¤£·|¡I½Ð¬d¾\ <ulink URL="../../handbook/kernelconfig.html">
             ¨Ï¥Î¤â¥U¤¤ªº®Ö¤ß³]©w¤@¸`</ulink>¡C</para>
 
             <note>
               <para>§Ú·|«Øij§A¦b§AÅý®Ö¤ß¯à¥¿±`¤u§@«á¡A°µ¤@­Ó
 	        <filename>kernel.YYMMDD</filename> ¤é´Á§Î¦¡ªº³Æ¥÷¡A¦P®É¤]³Æ¥÷
 		<filename>/module</filename>³o­Ó¥Ø¿ý¦Ü
 		<filename>/modules.YYMMDD</filename>¡C³o¼Ë¤U¦¸¦pªG§A«Ü¤£©¯ªºª±
 		Ãa¤F³]©w¡A¦Ü¤Ö¥i¥H¤£»Ý­n¨Ï¥Î³Ì­ì©lªº
 		<filename>kernel.GENERIC</filename>¡C¦p§A¥¿±q¤@­Ó GENERIC
 		kernel ¸Ì­±¤£¤ä´©ªº±±¨î¾¹¸Ì±Ò°Ê®É¡A³o´NÅã±o¯S§O­«­n¡C</para>
             </note>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="missing-hw-float">
           <para>§Úªº®Ö¤ß¦]¬° <literal>_hw_float</literal>¿ò¥¢¦Ó½sĶ¥¢±Ñ¡C
 	    ¸Ó«ç»ò­×¥¿©O¡H</para>
 	</question>
 
         <answer>
           <para>Åý§Ú²q¬Ý¬Ý¡A§A§â <devicename>npx0</devicename>
 	    (¸Ô¨£ &man.npx.4;) ±q§Aªº®Ö¤ß³]©wÀɲ¾°£¤F¡A¦]¬°§A¨S¦³¼Æ¾Ç¹Bºâ¾¹¡A
 	    ¹ï¶Ü¡H¿ù¤F¡I:-) ³o­Ó <devicename>npx0</devicename>¬O
 	    <emphasis>¥²¶·­n¦³ªº</emphasis>¡C´Nºâ§A¨S¦³¼Æ¾Ç¹Bºâ¾¹¡A§AÁÙ¬O
 	    <emphasis>¥²¶·</emphasis> ¤Þ¤J <devicename>npx0</devicename> ¸Ë¸m¡C
 	    </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="why-kernel-big">
           <para>¬°¤°»ò³y¥X¨Óªº kernel ³o»ò¤j (10MB ¥H¤W) ¡H</para>
         </question>
 
         <answer>
           <para>³o«Ü¦³¥i¯à¬O¦]¬°¡A§A§â kernel ½s¦¨ <emphasis>°»¿ù¼Ò¦¡</emphasis>
 	    ¤F¡C°»¿ù¼Ò¦¡¤§¤Uªº kernel ¸Ì­±·|¦sµÛ°»¿ù¥Îªº³\¦h²Å¸¹¡A¦]¦¹·|¤j´T
 	    ¼W¥[ kernel ªº¤j¤p¡C¦pªG»¡§Aªº FreeBSD ¬O 3.0 ¥H«áªºª©¥»¡A³o¹ï©ó
 	    ®Ä¯à¨Ó»¡¼vÅT¨Ã¤£¤j¡A´X¥G¬O¨S¦³¡C¦Ó¦b¨t²Î·|¦]¬Y¨Ç­ì¦] panic ®É¡A
 	    ¦³­Ó°»¿ù¼Ò¦¡ªº kernel ¦b¤]®¼¦³¥Îªº¡C</para>
 
           <para>¤£¹L©O¡A¦pªG§AªººÏºÐªÅ¶¡«Ü¤p¡A©ÎªÌ§A´N¬O¤£·Q¥Î°»¿ù¼Ò¦¡ªº
 	    kernel ªº¸Ü¡A½Ð½T»{¥H¤U¨Æ±¡¡G</para>
 
           <itemizedlist>
             <listitem>
               <para>kernel ³]©wÀɸ̭±¨S¦³³o¤@¦æ¡G</para>
 
               <programlisting>makeoptions DEBUGS=-g </programlisting>
             </listitem>
 
             <listitem>
               <para>°õ¦æ &man.config.8; ®É¨S¦³¥[¤W <option>-g</option>
 	        ³o­Ó¿ï¶µ¡C</para>
             </listitem>
           </itemizedlist>
 
           <para>¥H¤W¨â¥ó¨Æ±¡³£·|Åý§A½s¥X¤@­Ó°»¿ù¼Ò¦¡ªº kernel¡C¦ý¥u­nÁקK¤§¡A
 	    ´N¥i¥H½s¥X¤@­Ó¥¿±`ªº kernel¡A¦Ó§A¤]·|ª`·N¨ì¡Akernel ©úÅ㪺Åܤp¤F¡F
 	    ¤j³¡¥÷ªº kernel ³£®t¤£¦h¦b 1.5MB ¨ì 2MB ¤§¶¡¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="multiport-serial-interrupts">
           <para>¬°¦ó¥X²{¤F multi-port serial code ªº¤¤Â_½Ä¬ð¡H</para>
         </question>
 
         <answer>
           <para>·í§Ú½sĶ¤@­Ó multi-port serial code ªº®Ö¤ß®É¡A¥¦§i¶D§Ú¥u¦³
 	    ²Ä¤@­Ó³Q°»´ú¨ì¡A¨ä¥Lªº«h¦]¤¤Â_½Ä¬ð¦Ó¸õ¹L¤F¡A§Ú¸Ó«ç»ò­×¥¿¥¦¡H</para>
 
           <para>³o­Ó°ÝÃD¬O¦]¬° FreeBSD ¨Ï¥Î¤º«Øµ{¦¡½XÁקK¦]¬°µwÅé©Î³nÅé½Ä¬ð
 	    ¾É­P®Ö¤ßµ{¦¡¹L©óªÎ¤j©ÎµL¥Î¡C­n­×¥¿³oºØ±¡§Îªº¤èªk¬O°£¤F¤@­Ó port
 	    ¥~§â¨ä¥L©Ò¦³ªº IRQ ³]©w³£°µ«O¯d¡C³o¸Ì¦³¤@­Ó½d¨Ò¡G</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>¬°¤°»ò§Ú¤@­Ó kernel ³£½s¤£°_¨Ó¡H¬Æ¦Ü GENERIC ¤]¤£¦æ¡H</para>
 	</question>
 
         <answer>
           <para>³o¦³«Ü¦hºØ¥i¯àªº­ì¦]¡G</para>
 
           <itemizedlist>
             <listitem>
               <para>§A¨S¦³¥Î·sªº <command>make buildkernel</command> »P
 	        <command>make installkernel</command> ³o¨â­Ó¤èªk¨Ó½s¡A¦Ó¥¿¦n
 		§Aªº¨t²Î­ì©l½Xªºª©¥»©M¥¿¦b°õ¦æªº¨t²Î®Ö¤ßª©¥»¤£¤@¼Ë (¹³¬O¡A
 		¦b¶] 4.0-RELEASE ªº¨t²Î¤W¹Á¸ÕµÛ½s 4.3-RELEASE)¡C¦pªG»¡§A­n¤É
 		¯Å¨t²Îªº¸Ü¡A½Ð°È¥²¥h¬Ý¬Ý <filename>/usr/src/UPDATING</filename>
 		³o­ÓÀɮסA¯S§Oª`·N³Ì«á­±ªº <quote>COMMON ITEMS</quote>
 		³o­Ó¤p¸`¡C</para>
             </listitem>
 
             <listitem>
               <para>§A¤w¸g¥Î¤W <command>make buildkernel</command> ¥H¤Î
 	        <command>make installkernel</command> ¤F¡A¦ý¬O¦b
 		<command>make buildworld</command> ®É¥¢±Ñ¤F¡C¥i±¤ªº¬O¡A
 		<command>make buildkernel</command> ­n¦¨¥\¡A»Ý­n¨Ì¿à
 		<command>make buildworld</command> «á³y¥X¨Óªº¤@¨ÇÀɮסC</para>
             </listitem>
 
             <listitem>
               <para>´Nºâ¬O§A¦b½s <link linkend="stable">FreeBSD-STABLE</link>¡A
 	        ÁÙ¬O¦³¥i¯à§A§ì¨ì¤F¥¿¦b­×§ï¤¤¡A©ÎµÛ¦]¬°¬Y¨Ç½t¬G¦Ó®Ú¥»ÁÙ¨S§ï¦n
 		ªº­ì©l½X¡FÁöµM»¡ <link linkend="stable">FreeBSD-STABLE</link>
 		¤j³¡¥÷ªº®É­Ô³£¬O¥i¥H½sªº¡A¦ý¥u¦³ RELEASE ¤~¬O«OÃÒ¥i¥H½sªº¡C¸I
 		¨ì³o­Ó°ÝÃD®É¡A¦A¦¸§ó·s­ì©l½X¨Ã¥B¦A¸Õ¸Õ¬Ý¡C¤]¦³¥i¯à¬O©ñ­ì©l½Xªº
 		¦øªA¾¹¥X²{¬Y¨Ç°ÝÃD¡A©Ò¥H§ó·s­ì©l½X®É¤]¸Õ¸Õ±q¤£¦P¦øªA¾¹¨Ó§ó·s¬Ý
 		¬Ý¡C</para>
             </listitem>
           </itemizedlist>
         </answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter id="disks">
     <title>Disks, Filesystems, and Boot Loaders</title>
 
     <qandaset>
       <qandaentry>
         <question id="adding-disks">
           <para>How can I add my new hard disk to my FreeBSD system?</para>
         </question>
 
         <answer>
           <para>See the Disk Formatting Tutorial at <ulink
             URL="../../articles/formatting-media/index.html">
             www.FreeBSD.org</ulink>.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="new-huge-disk">
           <para>How do I move my system over to my huge new disk?</para>
         </question>
 
         <answer>
           <para>The best way is to reinstall the OS on the new
             disk, then move the user data over.  This is highly
             recommended if you have been tracking -stable for more
             than one release, or have updated a release instead of
             installing a new one.  You can install booteasy on both
             disks with &man.boot0cfg.8;, and dual boot them until
             you are happy with the new configuration.  Skip the
             next paragraph to find out how to move the data after
             doing this.</para>
 
           <para>Should you decide not to do a fresh install, you
             need to partition and label the new disk with either
             <filename>/stand/sysinstall</filename>, or &man.fdisk.8;
             and &man.disklabel.8;.  You should also install booteasy
             on both disks with &man.boot0cfg.8;, so that you can
             dual boot to the old or new system after the copying
             is done.  See the <ulink
             url="../../articles/formatting-media/index.html">
             formatting-media article</ulink> for details on this
             process.</para>
 
           <para>Now you have the new disk set up, and are ready
             to move the data.  Unfortunately, you cannot just blindly
             copy the data.  Things like device files (in
 	    <filename>/dev</filename>), flags, and links tend to
             screw that up.  You need to use tools that understand
             these things, which means &man.dump.8;.
             Although it is suggested that you move the data in single user
             mode, it is not required.</para>
 
           <para>You should never use anything but &man.dump.8; and
             &man.restore.8; to move the root file system.  The
             &man.tar.1; command may work - then again, it may not.
             You should also use &man.dump.8; and &man.restore.8;
             if you are moving a single partition to another empty
             partition.  The sequence of steps to use dump to move
             a partitions data to a new partition is:</para>
 
           <procedure>
             <step>
               <para>newfs the new partition.</para>
             </step>
 
             <step>
               <para>mount it on a temporary mount point.</para>
             </step>
 
             <step>
               <para>cd to that directory.</para>
             </step>
 
             <step>
               <para>dump the old partition, piping output to the
                 new one.</para>
             </step>
           </procedure>
 
           <para>For example, if you are going to move root to
             <devicename>/dev/ad1s1a</devicename>, with
             <filename>/mnt</filename> as the temporary mount point,
             it is:</para>
 
           <screen>&prompt.root; <userinput>newfs /dev/ad1s1a</userinput>
 &prompt.root; <userinput>mount /dev/ad1s1a /mnt</userinput>
 &prompt.root; <userinput>cd /mnt</userinput>
 &prompt.root; <userinput>dump 0af - / | restore xf -</userinput></screen>
 
           <para>Rearranging your partitions with dump takes a bit more
             work. To merge a partition like <filename>/var</filename>
             into its parent, create the new partition large enough
             for both, move the parent partition as described above,
             then move the child partition into the empty directory
             that the first move created:</para>
 	  
           <screen>&prompt.root; <userinput>newfs /dev/ad1s1a</userinput>
 &prompt.root; <userinput>mount /dev/ad1s1a /mnt</userinput>
 &prompt.root; <userinput>cd /mnt</userinput>
 &prompt.root; <userinput>dump 0af - / | restore xf -</userinput>
 &prompt.root; <userinput>cd var</userinput>
 &prompt.root; <userinput>dump 0af - /var | restore xf -</userinput></screen>
 
 	  <para>To split a directory from its parent, say putting
 	    <filename>/var</filename> on its own partition when it was not
 	    before, create both partitions, then mount the child partition
 	    on the appropriate directory in the temporary mount point, then
 	    move the old single partition:</para>
 
           <screen>&prompt.root; <userinput>newfs /dev/ad1s1a</userinput>
 &prompt.root; <userinput>newfs /dev/ad1s1d</userinput>
 &prompt.root; <userinput>mount /dev/ad1s1a /mnt</userinput>
 &prompt.root; <userinput>mkdir /mnt/var</userinput>
 &prompt.root; <userinput>mount /dev/ad1s1d /mnt/var</userinput>
 &prompt.root; <userinput>cd /mnt</userinput>
 &prompt.root; <userinput>dump 0af - / | restore xf -</userinput></screen>
 
           <para>You might prefer &man.cpio.1;, &man.pax.1;,
             &man.tar.1; to &man.dump.8; for user data. At the time of
             this writing, these are known to lose file flag information,
             so use them with caution.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="dangerously-dedicated">
           <para>Will a <quote>dangerously dedicated</quote> disk endanger
             my health?</para>
         </question>
 
         <answer>
 
           <para><anchor id="dedicate">The installation procedure allows
             you to chose two different methods in partitioning your
             hard disk(s). The default way makes it compatible with other
             operating systems on the same machine, by using fdisk table
             entries (called <quote>slices</quote> in FreeBSD), with a
             FreeBSD slice that employs partitions of its own. Optionally,
             one can chose to install a boot-selector to switch between the
             possible operating systems on the disk(s). The alternative uses
             the entire disk for FreeBSD, and makes no attempt to be
             compatible with other operating systems.</para>
 
           <para>So why it is called <quote>dangerous</quote>?  A disk in
             this mode does not contain what normal PC utilities would
             consider a valid fdisk table. Depending on how well they have
             been designed, they might complain at you once they are getting
             in contact with such a disk, or even worse, they might damage
             the BSD bootstrap without even asking or notifying you. In
             addition, the <quote>dangerously dedicated</quote> disk's
             layout is known to confuse many BIOSes, including those from
             AWARD (e.g. as found in HP Netserver and Micronics systems as
             well as many others) and Symbios/NCR (for the popular 53C8xx
             range of SCSI controllers). This is not a complete list, there
             are more. Symptoms of this confusion include the <errorname>read
             error</errorname> message printed by the FreeBSD bootstrap when it
             cannot find itself, as well as system lockups when
             booting.</para>
 
           <para>Why have this mode at all then?  It only saves a few kbytes
             of disk space, and it can cause real problems for a new
             installation. <quote>Dangerously dedicated</quote> mode's
             origins lie in a desire to avoid one of the most common
             problems plaguing new FreeBSD installers - matching the BIOS
             <quote>geometry</quote> numbers for a disk to the disk
             itself.</para>
 
           <para><quote>Geometry</quote> is an outdated concept, but one
             still at the heart of the PC's BIOS and its interaction with
             disks. When the FreeBSD installer creates slices, it has to
             record the location of these slices on the disk in a fashion
             that corresponds with the way the BIOS expects to find them. If
             it gets it wrong, you will not be able to boot.</para>
 
           <para><quote>Dangerously dedicated</quote> mode tries to work
             around this by making the problem simpler. In some cases, it
             gets it right. But it is meant to be used as a last-ditch
             alternative - there are better ways to solve the problem 99
             times out of 100.</para>
 
           <para>So, how do you avoid the need for <quote>DD</quote> mode
             when you are installing? Start by making a note of the geometry
             that your BIOS claims to be using for your disks. You can
             arrange to have the kernel print this as it boots by specifying
             <option>-v</option> at the <literal>boot:</literal> prompt, or
             using <command>boot -v</command> in the loader. Just before the
             installer starts, the kernel will print a list of BIOS
             geometries. Do not panic - wait for the installer to start and
             then use scrollback to read the numbers. Typically the BIOS
             disk units will be in the same order that FreeBSD lists your
             disks, first IDE, then SCSI.</para>
 
           <para>When you are slicing up your disk, check that the disk
             geometry displayed in the FDISK screen is correct (ie. it
             matches the BIOS numbers); if it is wrong, use the
             <literal>g</literal> key to fix it. You may have to do this if
             there is absolutely nothing on the disk, or if the disk has been
             moved from another system. Note that this is only an issue with
             the disk that you are going to boot from; FreeBSD will sort
             itself out just fine with any other disks you may have.</para>
 
           <para>Once you have got the BIOS and FreeBSD agreeing about the
             geometry of the disk, your problems are almost guaranteed to be
             over, and with no need for <quote>DD</quote> mode at all. If,
             however, you are still greeted with the dreaded <errorname>read
             error</errorname> message when you try to boot, it is time to cross
             your fingers and go for it - there is nothing left to
             lose.</para>
 
           <para>To return a <quote>dangerously dedicated</quote> disk
             for normal PC use, there are basically two options. The first
             is, you write enough NULL bytes over the MBR to make any
             subsequent installation believe this to be a blank disk. You
             can do this for example with</para>
 
           <screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/rda0 count=15</userinput></screen>
 
           <para>Alternatively, the undocumented DOS
             <quote>feature</quote></para>
 
           <screen><prompt>C:\&gt;</prompt> <userinput>fdisk /mbr</userinput></screen>
 
           <para>will to install a new master boot record as well, thus
             clobbering the BSD bootstrap.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="safe-softupdates">
           <para>Which partitions can safely use softupdates?  I have
             heard that softupdates on <filename>/</filename> can cause
             problems.</para>
         </question>
 
         <answer>
           <para>Short answer: you can usually use softupdates safely
             on all partitions.</para>
 
           <para>Long answer: There used to be some concern over using
             softupdates on the root partition.  Softupdates has two
             characteristics that caused this.  First, a softupdates
             partition has a small chance of losing data during a
             system crash.  (The partition will not be corrupted; the
             data will simply be lost.)  Also, softupdates can cause
             temporary space shortages.</para>
 
           <para>When using softupdates, the kernel can take up to
             thirty seconds to actually write changes to the physical
             disk.  If you delete a large file, the file still resides
             on disk until the kernel actually performs the deletion.
             This can cause a very simple race condition.  Suppose you
             delete one large file and immediately create another large
             file.  The first large file is not yet actually removed
             from the physical disk, so the disk might not have enough
             room for the second large file.  You get an error that the
             partition does not have enough space, although you know
             perfectly well that you just released a large chunk of
             space!  When you try again mere seconds later, the file
             creation works as you expect.  This has left more than one
             user scratching his head and doubting his sanity, the
             FreeBSD filesystem, or both.</para>
 
           <para>If a system should crash after the kernel accepts a
             chunk of data for writing to disk, but before that data is
             actually written out, data could be lost or corrupted.
             This risk is extremely small, but generally manageable.
             Use of IDE write caching greatly increases this risk; it
             is strongly recommended that you disable IDE write caching
             when using softupdates.</para>
 
           <para>These issues affect all partitions using softupdates.
             So, what does this mean for the root partition?</para>
 
           <para>Vital information on the root partition changes very
             rarely.  Files such as <filename>/kernel</filename> and
             the contents of <filename>/etc</filename> only change
             during system maintenance, or when users change their
             passwords.  If the system crashed during the
             thirty-second window after such a change is made, it is
             possible that data could be lost.  This risk is negligible
             for most applications, but you should be aware that it
             exists.  If your system cannot tolerate this much risk,
             do not use softupdates on the root filesystem!</para>
 
           <para><filename>/</filename> is traditionally one of the
             smallest partitions.  By default, FreeBSD puts the
             <filename>/tmp</filename> directory on
             <filename>/</filename>.  If you have a busy
             <filename>/tmp</filename>, you might see intermittent
             space problems.  Symlinking <filename>/tmp</filename> to
             <filename>/var/tmp</filename> will solve this
             problem.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="inappropriate-ccd">
           <para>What is inappropriate about my ccd?</para>
         </question>
 
         <answer>
           <para>The symptom of this is:</para>
 
           <screen>&prompt.root; <userinput>ccdconfig -C</userinput>
 ccdconfig: ioctl (CCDIOCSET): /dev/ccd0c: Inappropriate file type or format</screen>
 
           <para>This usually happens when you are trying to concatenate
             the <literal>c</literal> partitions, which default to type
             <literal>unused</literal>. The ccd driver requires the
             underlying partition type to be FS_BSDFFS. Edit the disklabel
             of the disks you are trying to concatenate and change the types
             of partitions to <literal>4.2BSD</literal>.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ccd-disklabel">
           <para>Why can I not edit the disklabel on my ccd?</para>
         </question>
 
         <answer>
           <para>The symptom of this is:</para>
 
           <screen>&prompt.root; <userinput>disklabel ccd0</userinput>
 (it prints something sensible here, so let us 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>This is because the disklabel returned by ccd is actually
             a <quote>fake</quote> one that is not really on the disk.
             You can solve this problem by writing it back explicitly,
             as in:</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="mount-foreign-fs">
           <para>Can I mount other foreign filesystems under FreeBSD?</para>
         </question>
 
         <answer>
           <variablelist>
             <varlistentry>
               <term>Digital UNIX</term>
 
               <listitem>
                 <para>UFS CDROMs can be mounted directly on FreeBSD.
                   Mounting disk partitions from Digital UNIX and other
                   systems that support UFS may be more complex, depending
                   on the details of the disk partitioning for the operating
                   system in question.</para>
               </listitem>
             </varlistentry>
 
             <varlistentry>
               <term>Linux</term>
 
               <listitem>
                 <para>As of 2.2, FreeBSD supports <literal>ext2fs</literal>
                   partitions.  See &man.mount.ext2fs.8; for more
                   information.</para>
               </listitem>
             </varlistentry>
 
             <varlistentry>
               <term>NT</term>
 
               <listitem>
                 <para>A read-only NTFS driver exists for FreeBSD. For more
                   information, see this tutorial by Mark Ovens at <ulink
                   URL="http://ukug.uk.FreeBSD.org/~mark/ntfs_install.html">
                   http://ukug.uk.FreeBSD.org/~mark/ntfs_install.html</ulink>.
                   </para>
               </listitem>
             </varlistentry>
           </variablelist>
 
           <para>Any other information on this subject would be
             appreciated.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="mount-dos">
           <para>How do I mount a secondary DOS partition?</para>
         </question>
 
         <answer>
 
         <para>The secondary DOS partitions are found after ALL the primary
           partitions. For example, if you have an <quote>E</quote>
           partition as the second DOS partition on the second SCSI drive,
           you need to create the special files for <quote>slice 5</quote>
           in /dev, then mount /dev/da1s5:</para>
 
         <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>sh MAKEDEV da1s5</userinput>
 &prompt.root; <userinput>mount -t msdos /dev/da1s5 /dos/e</userinput></screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="crypto-filesystem">
           <para>Is there a cryptographic filesystem for &os;?</para>
         </question>
 
         <answer>
           <para>Yes; see the <filename role="package">security/cfs</filename> port.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="nt-bootloader">
           <para>How can I use the NT loader to boot FreeBSD?</para>
         </question>
 
         <answer>
           <para>This procedure is slightly different for 2.2.x and 3.x
             (with the 3-stage boot) systems.</para>
 
           <para>The general idea is that you copy the first sector of your
             native root FreeBSD partition into a file in the DOS/NT
             partition. Assuming you name that file something like
             <filename>c:\bootsect.bsd</filename> (inspired by
             <filename>c:\bootsect.dos</filename>), you can then edit the
             <filename>c:\boot.ini</filename> file to come up with something
             like this:</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>For 2.2.x systems this procedure assumes that DOS, NT,
             FreeBSD, or whatever have been installed into their respective
             fdisk partitions on the <emphasis>same</emphasis>
             disk.  This example was tested on a system where DOS &amp; NT
             were on the first fdisk partition, and FreeBSD on the second.
             FreeBSD was also set up to boot from its native partition, not
             the disk's MBR.</para>
 
           <para>Mount a DOS-formatted floppy (if you have converted to NTFS)
             or the FAT partition, under, say,
             <filename>/mnt</filename>.</para>
 
           <screen>&prompt.root; <userinput>dd if=/dev/rda0a of=/mnt/bootsect.bsd bs=512 count=1</userinput></screen>
 
           <para>Reboot into DOS or NT.  NTFS users copy the
             <filename>bootsect.bsd</filename> and/or the
             <filename>bootsect.lnx</filename> file from the floppy to
             <filename>C:\</filename>. Modify the attributes (permissions)
             on <filename>boot.ini</filename> with:</para>
 
           <screen><prompt>C:\&gt;</prompt> <userinput>attrib -s -r c:\boot.ini</userinput></screen>
 
           <para>Edit to add the appropriate entries from the example
             <filename>boot.ini</filename> above, and restore the
             attributes:</para>
 
           <screen><prompt>C:\&gt;</prompt> <userinput>attrib +s +r c:\boot.ini</userinput></screen>
 
           <para>If FreeBSD is booting from the MBR, restore it with the DOS
             <command>fdisk</command> command after you reconfigure them to
             boot from their native partitions.</para>
 
           <para>For FreeBSD 3.x systems the procedure is somewhat
             simpler.</para>
 
           <para>If FreeBSD is installed on the same disk as the NT boot
             partition simply copy <filename>/boot/boot1</filename> to
             <filename>C:\BOOTSECT.BSD</filename> However, if FreeBSD is
             installed on a different disk <filename>/boot/boot1</filename>
             will not work, <filename>/boot/boot0</filename> is needed.
 
             <warning>
               <para>DO NOT SIMPLY COPY <filename>/boot/boot0</filename>
                 INSTEAD OF <filename>/boot/boot1</filename>, YOU WILL
                 OVERWRITE YOUR PARTITION TABLE AND RENDER YOUR COMPUTER
                 UN-BOOTABLE!</para>
             </warning>
 
             <filename>/boot/boot0</filename> needs to be installed using
               sysinstall by selecting the FreeBSD boot manager on the
               screen which asks if you wish to use a boot manager. This is
               because <filename>/boot/boot0</filename> has the partition
               table area filled with NULL characters but sysinstall copies
               the partition table before copying
               <filename>/boot/boot0</filename> to the MBR.</para>
 
           <para>When the FreeBSD boot manager runs it records the last
             OS booted by setting the active flag on the partition table
             entry for that OS and then writes the whole 512-bytes of itself
             back to the MBR so if you just copy
             <filename>/boot/boot0</filename> to
             <filename>C:\BOOTSECT.BSD</filename> then it writes an empty
             partition table, with the active flag set on one entry, to the
             MBR.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="lilo-bootloader">
           <para>How do I boot FreeBSD and Linux from LILO?</para>
         </question>
 
         <answer>
           <para>If you have FreeBSD and Linux on the same disk, just follow
             LILO's installation instructions for booting a non-Linux
             operating system.  Very briefly, these are:</para>
 
           <para>Boot Linux, and add the following lines to
             <filename>/etc/lilo.conf</filename>:</para>
 
             <programlisting>other=/dev/hda2
         table=/dev/hda
         label=FreeBSD</programlisting>
 
           <para>(the above assumes that your FreeBSD slice is known to Linux
             as <devicename>/dev/hda2</devicename>; tailor to suit your setup).
             Then, run <command>lilo</command> as <username>root</username> and you should be
             done.</para>
 
           <para>If FreeBSD resides on another disk, you need to add
             <literal>loader=/boot/chain.b</literal> to the LILO entry.
             For example:</para>
 
           <programlisting>other=/dev/dab4
         table=/dev/dab
         loader=/boot/chain.b
         label=FreeBSD</programlisting>
 
           <para>In some cases you may need to specify the BIOS drive number
             to the FreeBSD boot loader to successfully boot off the second
             disk.  For example, if your FreeBSD SCSI disk is probed by BIOS
             as BIOS disk 1, at the FreeBSD boot loader prompt you need to
             specify:</para>
 
           <screen>Boot: <userinput>1:da(0,a)/kernel</userinput></screen>
 
           <para>On FreeBSD 2.2.5 and later, you can configure
             &man.boot.8;
             to automatically do this for you at boot time.</para>
 
           <para>The <ulink
             URL="http://sunsite.unc.edu/LDP/HOWTO/mini/Linux+FreeBSD.html">
             Linux+FreeBSD mini-HOWTO</ulink> is a good reference for
             FreeBSD and Linux interoperability issues.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="booteasy-loader">
           <para>How do I boot FreeBSD and Linux using BootEasy?</para>
         </question>
 
         <answer>
           <para>Install LILO at the start of your Linux boot partition
             instead of in the Master Boot Record.   You can then boot LILO
             from BootEasy.</para>
 
           <para>If you are running Windows-95 and Linux this is recommended
             anyway, to make it simpler to get Linux booting again if you
             should need to reinstall Windows95 (which is a Jealous
             Operating System, and will bear no other Operating Systems in
             the Master Boot Record).</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="changing-bootprompt">
           <para>How do I change the boot prompt from <literal>???</literal> to
             something more meaningful?</para>
         </question>
 
         <answer>
           <para>You can not do that with the standard boot manager without
             rewriting it. There are a number of other boot managers
             in the <filename>sysutils</filename> ports category that
             provide this functionality.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="removable-drives">
           <para>I have a new removable drive, how do I use it?</para>
         </question>
 
         <answer>
 
           <para>Whether it is a removable drive like a ZIP or an EZ drive
             (or even a floppy, if you want to use it that way), or a new
             hard disk, once it is installed and recognized by the system,
             and you have your cartridge/floppy/whatever slotted in, things
             are pretty much the same for all devices.</para>
 
           <para><anchor id="disklabel">(this section is based on <ulink
             URL="http://www.vmunix.com/mark/FreeBSD/ZIP-FAQ.html">
             Mark Mayo's ZIP FAQ</ulink>)</para>
 
           <para>If it is a ZIP drive or a floppy, you have already got a DOS
             filesystem on it, you can use a command like this:</para>
 
           <screen>&prompt.root; <userinput>mount -t msdos /dev/fd0c /floppy</userinput></screen>
 
           <para>if it is a floppy, or this:</para>
 
           <screen>&prompt.root; <userinput>mount -t msdos /dev/da2s4 /zip</userinput></screen>
 
           <para>for a ZIP disk with the factory configuration.</para>
 
           <para>For other disks, see how they are laid out using
             &man.fdisk.8; or
             &man.sysinstall.8;.</para>
 
           <para>The rest of the examples will be for a ZIP drive on da2,
             the third SCSI disk.</para>
 
           <para>Unless it is a floppy, or a removable you plan on sharing
             with other people, it is probably a better idea to stick a BSD
             file system on it. You will get long filename support, at least a
             2X improvement in performance, and a lot more stability. First,
             you need to redo the DOS-level partitions/filesystems. You can
             either use &man.fdisk.8; or
             <filename>/stand/sysinstall</filename>, or for a small drive
             that you do not want to bother with multiple operating system
             support on, just blow away the whole FAT partition table
             (slices) and just use the BSD partitioning:</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>You can use disklabel or
             <filename>/stand/sysinstall</filename> to create multiple BSD
             partitions. You will certainly want to do this if you are adding
             swap space on a fixed disk, but it is probably irrelevant on a
             removable drive like a ZIP.</para>
 
           <para>Finally, create a new file system, this one is on our ZIP
             drive using the whole disk:</para>
 
           <screen>&prompt.root; <userinput>newfs /dev/rda2c</userinput></screen>
 
           <para>and mount it:</para>
 
           <screen>&prompt.root; <userinput>mount /dev/da2c /zip</userinput></screen>
 
           <para>and it is probably a good idea to add a line like this to
             <filename>/etc/fstab</filename> (see &man.fstab.5;) so you can just type
             <command>mount /zip</command> in the future:</para>
 
           <programlisting>/dev/da2c /zip ffs rw,noauto 0 0</programlisting>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="mount-cd-superblock">
           <para>Why do I get <errorname>Incorrect super block</errorname> when
             mounting a CDROM?</para>
         </question>
 
         <answer>
           <para>You have to tell &man.mount.8; the type of the device
             that you want to mount.  This is described in the <ulink
             URL="../handbook/creating-cds.html"> Handbook section on
             optical media</ulink>, specifically the section <ulink
             URL="../handbook/creating-cds.html#MOUNTING-CD">Using Data
             CDs</ulink>.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="cdrom-not-configured">
           <para>Why do I get <errorname>Device not configured</errorname> when
             mounting a CDROM?</para>
         </question>
 
         <answer>
           <para>This generally means that there is no CDROM in the
             CDROM drive, or the drive is not visible on the
             bus. Please see the <ulink
             URL="../handbook/creating-cds.html#MOUNTING-CD">Using Data
             CDs</ulink> section of the Handbook for a detailed
             discussion of this issue.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="cdrom-unicode-filenames">
           <para>Why do all non-English characters in filenames show up as
             <quote>?</quote> on my CDs when mounted in FreeBSD?</para>
         </question>
 
         <answer>
           <para>Your CDROM probably uses the <quote>Joliet</quote>
             extension for storing information about files and
             directories.  This is discussed in the Handbook chapter on
             <ulink URL="../handbook/creating-cds.html">creating and
             using CDROMs</ulink>, specifically the section on <ulink
             URL="../handbook/creating-cds.html#MOUNTING-CD">Using Data
             CDROMs</ulink>.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="burncd-isofs">
           <para>I burned a CD under FreeBSD and now I can not read it
             under any other operating system. Why?</para>
         </question>
   
         <answer>
           <para>You most likely burned a raw file to your CD, rather
             than creating an ISO 9660 filesystem.  Take a look at the
             <ulink URL="../handbook/creating-cds.html">Handbook
             chapter on creating CDROMs</ulink>, particularly the
             section on <ulink
             URL="../handbook/creating-cds.html#RAWDATA-CD">burning raw
             data CDs</ulink>.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
         <question id="copy-cd">
           <para>How can I create an image of a data CD?</para>
         </question>
 
         <answer>
           <para>This is discussed in the Handbook section on <ulink
             url="../handbook/creating-cds.html#IMAGING-CD">duplicating
             data CDs</ulink>. For more on working with CDROMs, see the
             <ulink url="../handbook/creating-cds.html">Creating CDs
             Section</ulink> in the Storage chapter in the
             Handbook.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="mount-audio-CD">
           <para>Why can I not <command>mount</command> an audio
           CD?</para>
          </question>
 
         <answer>
           <para>If you try to mount an audio CD, you will get an error
             like <errorname>cd9660: /dev/acd0c: Invalid
             argument</errorname>.  This is because
             <command>mount</command> only works on filesystems.  Audio
             CDs do not have filesystems; they just have data.  You
             need a program that reads audio CDs, such as the
             <filename role="package">audio/xmcd</filename> port.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="multi-session-CD">
           <para>How do I <command>mount</command> a multi-session CD?</para>
         </question>
 
         <answer>
           <para>By default, &man.mount.8; will attempt to mount the
             last data track (session) of a CD.  If you would like to
             load an earlier session, you must use the
             <option>-s</option> command line argument.  Please see
             &man.mount.cd9660.8; for specific examples.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="user-floppymount">
           <para>How do I let ordinary users mount floppies, CDROMs and
             other removable media?</para>
         </question>
 
         <answer>
           <para>Ordinary users can be permitted to mount devices. Here is
             how:</para>
 
           <procedure>
             <step>
               <para>As <username>root</username> set the sysctl variable
                 <varname>vfs.usermount</varname> to
                 <literal>1</literal>.</para>
 
               <screen>&prompt.root; <userinput>sysctl -w vfs.usermount=1</userinput></screen>
             </step>
 
             <step>
               <para>As <username>root</username> assign the appropriate
                 permissions to the block device associated with the
                 removable media.</para>
 
               <para>For example, to allow users to mount the first floppy
                 drive, use:</para>
 
               <screen>&prompt.root; <userinput>chmod 666 /dev/fd0</userinput></screen>
 
               <para>To allow users in the group
                 <groupname>operator</groupname> to mount the CDROM drive,
                 use:</para>
 
               <screen>&prompt.root; <userinput>chgrp operator /dev/cd0c</userinput>
 &prompt.root; <userinput>chmod 640 /dev/cd0c</userinput></screen>
             </step>
 
             <step>
               <para>Finally, add the line
                 <literal><varname>vfs.usermount</varname>=1</literal> to the file
                 <filename>/etc/sysctl.conf</filename> so that it is reset
                 at system boot time.</para>
             </step>
           </procedure>
 
           <para>All users can now mount the floppy
             <devicename>/dev/fd0</devicename> onto a directory that they
             own:</para>
 
           <screen>&prompt.user; <userinput>mkdir ~/my-mount-point</userinput>
 &prompt.user; <userinput>mount -t msdos /dev/fd0 ~/my-mount-point</userinput></screen>
 
           <para>Users in group <groupname>operator</groupname> can now
             mount the CDROM <devicename>/dev/cd0c</devicename> onto a
             directory that they own:</para>
 
           <screen>&prompt.user; <userinput>mkdir ~/my-mount-point</userinput>
 &prompt.user; <userinput>mount -t msdos /dev/cd0c ~/my-mount-point</userinput></screen>
 
           <para>Unmounting the device is simple:</para>
 
           <screen>&prompt.user; <userinput>umount <filename>~/my-mount-point</filename></userinput></screen>
 
           <para>Enabling <varname>vfs.usermount</varname>, however, has
             negative security implications.  A better way to access MSDOS
             formatted media is to use the <ulink
             URL="http://www.FreeBSD.org/cgi/ports.cgi?query=%5Emtools-&amp;stype=name">mtools</ulink> package in the ports collection.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="du-vs-df">
           <para>The <command>du</command> and <command>df</command>
             commands show different amounts of disk space available.
             What is going on?</para>
         </question>
 
         <answer>
           <para>You need to understand what <command>du</command> and
             <command>df</command> really do.  <command>du</command>
             goes through the directory tree, measures how large each
             file is, and presents the totals.  <command>df</command>
             just asks the filesystem how much space it has left.  They
             seem to be the same thing, but a file without a directory
             entry will affect <command>df</command> but not
             <command>du</command>.</para>
 
           <para>When a program is using a file, and you delete the
             file, the file is not really removed from the filesystem
             until the program stops using it.  The file is immediately
             deleted from the directory listing, however.  You can see
             this easily enough with a program such as
             <command>more</command>.  Assume you have a file large
             enough that its presence affects the output of
             <command>du</command> and <command>df</command>.  (Since
             disks can be so large today, this might be a
             <emphasis>very</emphasis> large file!)  If you delete this
             file while using <command>more</command> on it,
             <command>more</command> does not immediately choke and
             complain that it cannot view the file.  The entry is
             simply removed from the directory so no other program or
             user can access it.  <command>du</command> shows that it
             is gone &mdash; it has walked the directory tree and the file
             is not listed.  <command>df</command> shows that it is
             still there, as the filesystem knows that
             <command>more</command> is still using that space.  Once
             you end the <command>more</command> session,
             <command>du</command> and <command>df</command> will
             agree.</para>
 
           <para>Note that softupdates can delay the freeing of disk
             space; you might need to wait up to 30 seconds for the
             change to be visible!</para>
 
           <para>This situation is common on web servers.  Many people
             set up a FreeBSD web server and forget to rotate the log
             files.  The access log fills up <filename>/var</filename>.
             The new administrator deletes the file, but the system
             still complains that the partition is full.  Stopping and
             restarting the web server program would free the file,
             allowing the system to release the disk space.  To prevent
             this from happening, set up &man.newsyslog.8;.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="add-swap-space">
           <para>How can I add more swap space?</para>
         </question>
 
         <answer>
           <para>In the <ulink
           url="../handbook/config-tuning.html">Configuration and
           Tuning</ulink> section of the Handbook, you will find a
           <ulink
           url="../handbook/adding-swap-space.html">section</ulink>
           describing how to do this.</para>
         </answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter id="admin">
     <chapterinfo>
       <author>
 	<firstname>Wei-Hon</firstname>
 	<surname>Chen</surname>
 	<affiliation>
 	  <address><email>plasmaball@pchome.com.tw</email></address>
 	</affiliation>
       </author>
     </chapterinfo>
 
     <title>¨t²ÎºÞ²z</title>
 
     <qandaset>
       <qandaentry>
         <question id="startup-config-files">
           <para>¨t²Î°_©l³]©wÀɦb­þ¡H</para>
         </question>
 
         <answer>
 
           <para>±q 2.0.5R ¨ì 2.2.1R¡A¥D­nªº³]©wÀɬO
 	    <filename>/etc/sysconfig</filename>¡C©Ò¦³ªº¿ï¶µ³£³Q«ü©w¦b³o­ÓÀÉ¡A
 	    ¦Ó¨ä¥L¹³ <filename>/etc/rc</filename> (°Ñ¨£ &man.rc.8;)
             ©M <filename>/etc/netstart</filename> ¥u¬O¤Þ¥Î¥¦¡C</para>
 
           <para>Æ[¹î <filename>/etc/sysconfig</filename> ³o­ÓÀɨíץ¿¨ä­È¥H
 	    ¾A¦X§Aªº¨t²Î¡C³o­ÓÀɥεù¸Ñ¶ñº¡¥Hªí¥Ü¦ó³B¸Ó©ñ¸m¤°»ò³]©w¡C</para>
 
           <para>¦b post-2.2.1 ¥H«á¤Î 3.0¡A<filename>/etc/sysconfig</filename>
             ¥ç§ó¦W¬°¤@­Ó§ó®e©ö´y­zªºÀɦW¥s &man.rc.conf.5; ¡A¨Ã¥B»yªk²¤Æ¤F¨Ç¡C
             <filename>/etc/netstart</filename> ¥ç§ó¦W¬°
             <filename>/etc/rc.network</filename> ¦]¦¹©Ò¦³ªºÀɮ׳£¥i¥H¥Î
             <command>cp /usr/src/etc/rc* /etc</command> ¨Ó«þ¨©¡C</para>
 
           <para>¦b 3.1 ¥H¤Î¡A<filename>/etc/rc.conf</filename> ³Q²¾¨ì
 	    <filename>/etc/defaults/rc.conf</filename>¡C
             <emphasis>¤d¸U¤£­n½s¿è³o­ÓÀÉ¡I</emphasis> ¦pªG
             <filename>/etc/defaults/rc.conf</filename> ¤º¦³·Q­n§ó°Êªº¶µ¥Ø¡A
 	    §AÀ³¸Ó±N¨º¤@¦æªº¤º®e«þ¨©¨ì <filename>/etc/rc.conf</filename>¡A
 	    µM«á¦A­×§ï¥¦¡C</para>
 
           <para>¨Ò¦p FreeBSD 3.1 ¤Î¥H«áªºª©¥»¤º¡A¦³¤@­Ó DNS ¦øªA¾¹ named¡A
 	    ¦Ó§A·Q­n±Ò°Ê¥¦¡C§A©Ò»Ý­n§@ªº¨Æ´N¬O¡G</para>
           <screen>&prompt.root; <userinput>echo named_enable="YES" &gt;&gt; /etc/rc.conf</userinput></screen>
 
           <para>·Q­n¦b FreeBSD 3.1 ¤Î¥H«áªºª©¥»¤¤¡A±Ò°Ê¥»¦aºÝªA°Èªº¸Ü¡A±N
 	    shell script ¸m©ó <filename>/usr/local/etc/rc.d</filename> ¥Ø¿ý
 	    ¤U¡C³o¨Ç shell script À³¸Ó³]©w¦¨¥i°õ¦æ¡A¨Ã¥BÀɦW¥H .sh µ²§ô¡C
             ¦b FreeBSD 3.0 ¤Î§ó¦­ªºª©¥»¤¤¡A§AÀ³¸Óª½±µ½s¿è
             <filename>/etc/rc.local</filename> ÀÉ¡C</para>
 
           <para><filename>/etc/rc.serial</filename>¥Î¨Óªì©l¤Æ§Ç¦C°ð
 	    ¡]¹³¬OÂê©w°ðªº¯S©Êµ¥¡^¡C</para>
 
           <para><filename>/etc/rc.i386</filename> ¬O Intel ±M¥Î³]©w¡A
 	    ¹³¬O iBCS2 ¼ÒÀÀ©Î¬O PC ¨t²Î¥D±±¥x³]©w¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="adding-users">
           <para>§Ú¸Ó¦p¦ó²³æ¦a¥[¤J¨Ï¥ÎªÌ¡H</para>
         </question>
 
         <answer>
           <para>¨Ï¥Î &man.adduser.8; «ü¥O¡C¦pªG»Ý­n§ó½ÆÂøªº¨Ï¥Î¤è¦¡¡A
 	    ½Ð¥Î &man.pw.8; ³o­Ó«ü¥O¡C</para>
 
           <para>­n¦A¦¸²¾°£¨Ï¥ÎªÌ¡A¨Ï¥Î &man.rmuser.8; «ü¥O¡CÁÙ¦³¡A
 	    &man.pw.8; ¤]¥i¥H¨Ï¥Î¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="root-not-found-cron-errors">
           <para>¦b§Ú½s¿è crontab Àɮפ§«á¡A¬°¤°»ò§Ú¦Ñ¬O¦¬¨ì³o¼Ëªº°T®§¡G
             <errorname>root: not found</errorname>¡H</para>
         </question>
 
         <answer>
           <para>³q±`³£¬O¦]¬°½s¿è¤F¨t²Îªº crontab
 	    (<filename>/etc/crontab</filename>) µM«á´N¥Î &man.crontab.1;
 	    ¥h¦w¸Ë¥¦¡G</para>
 
           <screen>&prompt.root; <userinput>crontab /etc/crontab</userinput></screen>
 
           <para>³o¼Ë§@¬O¤£¹ïªº¡C¨t²Îªº crontab ©M &man.crontab.1;
             ©Ò§ó·sªº¨Ï¥ÎªÌªº crontab ®æ¦¡¨Ã¤£¤@¼Ë (&man.crontab.5;
             »¡©ú¤å¥ó°w¹ï®t²§³B¦³¸Ô²Óªº»¡©ú)¡C</para>
 
           <para>¦pªG§A¤w¸g¥Î³oºØ¤èªk¡AÃB¥~¦h¥Xªº crontab ¥u´N¬O
             <filename>/etc/crontab</filename> ªº«þ¨©¡A¥u¬O®æ¦¡¬O¿ù»~ªº¡C
             ¥i¥Î¥H¤Uªº©R¥O§R°£¡G</para>
 
           <screen>&prompt.root; <userinput>crontab -r</userinput></screen>
 
           <para>¤U¦¸§A½s¿è <filename>/etc/crontab</filename> Àɮתº®É­Ô¡A
             §A¤£¥Î§@¥ô¦ó°Ê§@¥h³qª¾ &man.cron.8; ¡A¥¦¦Û°Ê·|¥h°»´ú¬O§_¦³§ó°Ê¡C
           </para>
 
           <para>¦pªG§A·Q­n¨C¤Ñ¡B¨C¶g¡B©Î¬O¨C¤ë©T©w°õ¦æ¬Y¨Ç°Ê§@¤@¦¸¡A¤]³\¥[­Ó
             shell script ¦b <filename>/usr/local/etc/periodic</filename>
             ¥Ø¿ý¤U·|§ó¦n¡A¨t²Îªº cron ·|©T©w°õ¦æ &man.periodic.8; ©R¥O¡A
             ¥¦¥i±N§Aªºµ{¦¡©M¨ä¥¦ªº¨t²Î¶g´Á©Ê¤u§@¤@°_°õ¦æ¡C</para>
 
           <para>³o­Ó¿ù»~ªº¯u¥¿­ì¦]¡A¬O¦]¬°¨t²Îªº crontab ¦³¤@­ÓÃB¥~ªºÄæ¦ì¡A
             »¡©ú¸Ó©R¥O­n¥H¤°»ò¨Ï¥ÎªÌ¨­¥÷°õ¦æ¡C¦b FreeBSD ªº¹w³]¨t²Î crontab
             ¤¤¡A©Ò¦³ªº¶µ¥Ø³£¬O <username>root</username>¡C ·í³o­Ó crontab
             ³Q·í§@¬O <username>root</username> ªº¨Ï¥ÎªÌ crontab (¥¦©M¨t²Îªº
             crontab ¬O <emphasis>¤£</emphasis> ¤@¼Ëªº)¡A&man.cron.8; ·|¥H¬°
             <literal>root</literal> ¦r¦ê¬O±ý°õ¦æªº©R¥Oªº²Ä¤@­Ó¦r¡A¦ý¬O¹ê»Ú¤W
             ¨Ã¨S¦³³o¼Ëªº©R¥O¦s¦b¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
 	<question id="su-wheel-group">
 	  <para>¬°¤°»ò§Ú·Q­n¥Î su ¦¨¬° <username>root</username> ®É¡A·|±o¨ì
             <errorname>you are not in the correct group to su root</errorname>
             ªº¿ù»~°T®§¡H</para>
 	</question>
 
 	<answer>
 	  <para>³o¬O¤@­Ó¦w¥þ¯S©Ê¡C·Q­n§Q¥Î su ¦¨¬° <username>root</username>
             (©Î¨ä¥¦¦³ superuser Åv­­ªº±b¸¹)¡A§A¤@©w­n¦b
 	    <groupname>wheel</groupname> ¸s²Õ¤º¡C¦pªG¨S¦³³o­Ó¯S©Êªº¸Ü¡A
 	    ¥ô¦ó¤H¥u­n¦b¨t²Î¸Ì¦³±b¸¹¡A¨Ã¥B«ê¥©ª¾¹D <username>root</username>
 	    ªº±K½X¡A´N¥i¥H¨ú±o superuser µ¥¯ÅªºÅv­­¥H¦s¨ú¨t²Î¡C¦³¤F³o­Ó¯S©Ê¡A
 	    ³o¼Ëªº±¡ªp´N¤£·|µo¥Í¡F¦pªG¨Ï¥ÎªÌ¤£¦b <groupname>wheel</groupname>
 	    ¸s²Õ¤ºªº¸Ü¡A&man.su.1; ·|Åý¥L­Ì³s¸ÕµÛÁä¤J±K½Xªº¾÷·|³£¨S¦³¡C</para>
 
 	  <para>­nÅý¬Y¤H¥i¥H§Q¥Î su ¦¨¬° <username>root</username> ªº¸Ü¡A
             ¥u­n§â¥L­Ì©ñ¤J <groupname>wheel</groupname> ¸s²Õ¤º§Y¥i¡C</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
         <question id="rcconf-readonly">
           <para>§Ú¦b <filename>rc.conf</filename> ÁÙ¬O¬Y­Ó°_°ÊÀɮ׸̥ǤF¿ù»~¡A
             ¦]¬°Àɮרt²ÎÅܦ¨°ßŪªº¡A§ÚµLªk¥h½s¿è¥¦¡C§Ú¸Ó«ç»ò¿ì¡H</para>
         </question>
 
         <answer>
           <para>·í¹q¸£°Ý§A shell §¹¾ã¸ô®|¦W®É¡A¥u­n«ö <literal>ENTER
             </literal>¡AµM«á°õ¦æ <command>mount /</command> ¥HŪ¼g¼Ò¦¡
             ­«·s±¾¸ü®ÚÀɮרt²Î¡C§A¤]³\»Ý­n°õ¦æ <command>mount -a -t ufs
             </command>¡A±N§AºD¥Îªº¤å¦r½s¿è¾¹©Ò¦bªºÀɮרt²Î±¾¸ü¤W¨Ó¡C¦pªG
             §AºD¥Îªº¤å¦r½s¿è¾¹¦bºô¸ôÀɮרt²Î¤Wªº¸Ü¡A§A¥²¶·¥ý¤â°Ê±Nºô¸ô³]©w
             °_¨Ó¡A¥H«K±Nºô¸ôÀɮרt²Î±¾¸ü¤W¨Ó¡A©Î¬O¨Ï¥Î¥»¦aºÝÀɮרt²Î¤Wªº
             ½s¿è¾¹¡A¨Ò¦p &man.ed.1;¡C</para>
 
           <para>¦pªG§A·Q­n¨Ï¥Î¹³ &man.vi.1; ©Î¬O &man.emacs.1; µ¥ªº¥þ¿Ã¹õ
             ¤å¦r½s¿è¾¹ªº¸Ü¡A§A¤]»Ý­n°õ¦æ
 	    <command>export TERM=cons25 </command>¡A¥H«KÅý³o¨Ç½s¿è¾¹¯à°÷±q
 	    &man.termcap.5; ¸ê®Æ®w¸ÌŪ¨ú¥¿½Tªº¸ê®Æ¡C</para>
 
           <para>·í§A¤w¸g§¹¦¨¤F³o¨Ç¨BÆJ«á¡A§A¥i¥H·Ó§A¥­±`­×§ï¤åªk¿ù»~ªº¤è¦¡
             ¥h½s¿è <filename>/etc/rc.conf</filename> ÀɮסC¦b®Ö¤ß (kernel)
             ±Ò°Ê®É©ÒÅã¥Üªº¿ù»~°T®§¡A¯à°÷§i¶D§AÀɮפ¤­þ¤@¦æ¦³¿ù»~¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="printer-setup">
           <para>¬°¤°»ò§Ú¨S¿ìªk³]©w§Úªº¦Lªí¾÷¡H</para>
         </question>
 
         <answer>
           <para>½Ð°Ñ¦Ò¤@¤U Handbook ¤¤¡A¦³Ãö¦C¦Lªº³¡¥÷¡C¥¦À³¸Ó¯à°÷¸Ñ¨M
             §A¤j³¡¥÷ªº°ÝÃD¡C½Ð°Ñ¦Ò <ulink URL="../handbook/printing.html">
             Handbook ¤¤ªº¦C¦L³¡¥÷</ulink>¡C</para>
 
 	  <para>¦³¨Ç¦Lªí¾÷»Ý­n¥D¾÷¤ä´©ªºÅX°Êµ{¦¡ (host-based driver) ¤~¯à
             °õ¦æ¥ô¦ó¦C¦L¥\¯à¡CFreeBSD ¥»¨­¨Ã¤£¤ä´©³o¨Ç©Ò¿×ªº
             <quote>WinPrinters</quote>¡C ¦pªG§Aªº¦Lªí¾÷µLªk¦b DOS ©Î
             Windows NT 4.0 ¤U°õ¦æ¡A¨º¥¦¤j·§´N¬O¤@¥x WinPrinter¡C§A°ß¤@¯à¨Ï¥Î
             ³o¼Ëªº¦Lªí¾÷ªº§Æ±æ¡A´N¬O¸Õ¸Õ <filename role="package">
             print/pnm2ppa</filename> ¤ä¤£¤ä´©¥¦¤F¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="keyboard-mappings">
           <para>§Ú­n«ç»ò¼Ë­×¥¿§Úªº¨t²Î©Ò¨Ï¥ÎªºÁä½L¹ï¬M (keyboard mapping)¡H
             </para>
         </question>
 
         <answer>
           <para>½Ð°Ñ¦Ò Handbook ¤¤ªº <ulink
             url="../handbook/using-localization.html">using localization
             </ulink> ³¹¸`¡A¤×¨ä¬O <ulink
             url="../handbook/using-localization.html#SETTING-CONSOLE">console
             setup</ulink> ³¹¸`¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="pnp-resources">
           <para>¬°¤°»ò§Ú¦b¨t²Î±Ò°Ê®É¡A±o¨ì <errorname>unknown: &lt;PNP0303&gt;
             can't assign resources</errorname> ªº°T®§¡H</para>
         </question>
 
         <answer>
 	  <para>¥H¤U¬O±q freebsd-current ³q«H½×¾Âªº¤@½g¤å³¹¤¤¸`¿ý¥X¨Óªº¡C</para>
 
 	  <blockquote>
 	    <attribution>&a.wollman;, 2001 ¦~¥|¤ë 24 ¤é</attribution>
 
 	    <para><quote>µLªk«ü¬£¸ê·½ (can't assign resources)</quote> °T®§ªí¥Ü
               ¨º¨Ç¸Ë¸m¬O¶Ç²Îªº ISA ¸Ë¸m¡A¦Ó®Ö¤ß¤¤¤w¸g½s¤J¤£»{±o PNP ªºÅX°Êµ{
 	      ¦¡¡C³o¨Ç¸Ë¸m¥]¬AÁä½L±±¨î¾¹¡A¥iµ{¦¡¤Æ§ÃÂ_±±¨î´¹¤ù¡AÁÙ¦³´X­Ó¼Ð·Ç
 	      ³]³Æ¡C¸ê·½µLªk«ü¬£µ¹³o¨Ç¸Ë¸m¡A¬O¦]¬°¦­¤w¦³ÅX°Êµ{¦¡¨Ï¥Î¨º¨Ç¦ì§}
 	      ¤F¡C</para>
 	  </blockquote>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="user-quotas">
           <para>¬°¤°»ò§ÚµLªkÅý user quotas ¥¿±`¤u§@¡H</para>
         </question>
 
         <answer>
 
             <orderedlist>
               <listitem>
                 <para>¤£­n¦b <filename>/</filename> ¥´¶} quotas¡A</para>
               </listitem>
 
               <listitem>
                 <para>§â quotas ÀÉ©ñ¦b¥¦¥²¶·±j­¢¸m¤JªºÀɮרt²Î¤º¡AÁ|¨Ò¡G</para>
 
                 <informaltable frame="none">
                   <tgroup cols="2">
                     <thead>
                       <row>
                         <entry>Àɮרt²Î</entry>
                         <entry>Quota ÀÉ</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="sysv-ipc">
           <para>FreeBSD ¤ä´© System V IPC ®æ¦¡«ü¥O¶°¡H</para>
         </question>
 
         <answer>
           <para>¬Oªº¡AFreeBSD ¤ä´© System V-style IPC¡C³o¥]¬A¦@¨É°O¾ÐÅé¡A
 	    °T®§¸ò«H¸¹¡C§A»Ý­n¦b§Aªº®Ö¤ß³]©wÀɤº¥[¤J¤U¦C´X¦æ¥H±Ò°Ê¥¦­Ì¡C</para>
 
           <programlisting>options    SYSVSHM          # enable shared memory
 options    SYSVSEM          # enable for semaphores
 options    SYSVMSG          # enable for messaging</programlisting>
 
             <note>
               <para>¦b  FreeBSD 3.2 ¥H¤Î¤§«áªºª©¥»¡A³o¨Ç¿ï¶µ¤w¸g¬O
                 <emphasis>GENERIC</emphasis> ®Ö¤ßªº¤@³¡¥÷¡A¤]´N¬O»¡¥¦­Ì¤w
 		¸g½s¶i¤F§Aªº¨t²Î¤¤¡C</para>
             </note>
 
           <para>­«·s½sĶ¨Ã¦w¸Ë¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="uucpmail">
           <para>§Ú¸Ó¦p¦óÅý sendmail ³z¹L UUCP ¨Ó»¼°e¶l¥ó¡H</para>
         </question>
 
         <answer>
           <para>¸òÀH FreeBSD ®M¸Ë¦Ó¨Óªº sendmail ³]©w¬O¾A¦X¨º¨Çª½±µ³s¤Wºô»Úºô¸ô
             ªº¯¸¥x¡C·Q³z¹L UUCP ¥æ´«¶l¥óªº¯¸¥x¥²¶·¥t¥~¦w¸Ë sendmail ªº³]©wÀɮסC
           </para>
 
           <para>¤â°Ê­×§ï <filename>/etc/sendmail.cf</filename> ¬Oµ´¹ï¥²­nªº¡C
             ²Ä 8 ª©ªº sendmail ´£¨Ñ¤@­Ó¥þ·sªº¤J¤f¥H³z¹L¤@¨Ç¹³ &man.m4.1;
             ªº³B²z´N¯à²£¥Í³]©wÀÉ¡A³o¨Æ¹ê¤W¬O¤@­Ó°ª¼h·§©Àµ¥¯Åªº§Þ¥©©Ê³]©w¡C
 	    §AÀ³¸Ó¥i¥H¦b <filename>/usr/src/usr.sbin/sendmail/cf</filename>
 	    ¥H¤U¸Ì¨Ï¥Î¥¦¡G</para>
 
           <para>°²¦p§A¤£¬O¥Î full sources ¤è¦¡¦w¸Ë¨t²Î¡A¨º»ò sendmail
             ³]©w¶µ¥Ø¥i¯à¤w¸g¤À´²¦¨¦n´X­Ó¨Ó·½¤À¥¬Àɦbµ¥µÛ§A¡A°²³]§A¤w¸g
             mount ¥úºÐ¾÷¡A°µ¥H¤U°Ê§@¡G</para>
 
           <screen>&prompt.root; <userinput>cd /cdrom/src</userinput>
 &prompt.root; <userinput>cat scontrib.?? | tar xzf - -C /usr/src contrib/sendmail</userinput></screen>
 
           <para>§OÅå·W¡A³o¥u¦³¼Æ¤Q¸U­Ó¦ì¤¸²Õªº¤j¤p¡C¦b <filename>cf</filename>
 	    ¥Ø¿ý¸Ìªº <filename>README</filename> ¥i¥H´£¨Ñ¤@­Ó m4 ³]©wªkªº°ò
 	    ¥»¤¶²Ð¡C</para>
 
           <para>¥H UUCP »¼°e¨Ó»¡¡A«Øij§A³Ì¦n¨Ï¥Î <literal>mailertable</literal>
             ¯SÂI¡C«Øºc¤@­Ó¸ê®Æ®wÅý sendmail ¥i¥H¨Ï¥Î¥¦¦Û¤vªº¸ô®|¨Mµ¦¡C</para>
 
           <para>­º¥ý¡A§A¥²¶·«Ø¥ß¦Û¤vªº <filename>.mc</filename> ÀÉ¡C
             <filename>/usr/src/usr.sbin/sendmail/cf/cf</filename> ¥Ø¿ý¬O³o¨Ç
 	    Àɮתº®a¡C¬d¬Ý¤@¤U¡A¤w¸g¦³¦n´X­Ó½d¨ÒÀÉ¡A°²³]§A¤w¸g©R¦W¦Û¤vªºÀÉ¥s 
             <filename>foo.mc</filename>¡A§A­n°µªº¥u¬O§â¥¦Âà´«¦¨¤@­Ó¦³®Äªº
             <filename>sendmail.cf</filename>¡G</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/mail/sendmail.cf</userinput></screen>
 
           <para>¤@­Ó¨å«¬ªº <filename>.mc</filename> Àɬݰ_¨Ó¥i¯à¹³³o¼Ë¡G</para>
 
           <programlisting>VERSIONID(`<replaceable>Your version number</replaceable>')
 OSTYPE(bsd4.4)
 
 FEATURE(accept_unresolvable_domains)
 FEATURE(nocanonify)
 FEATURE(mailertable, `hash -o /etc/mail/mailertable')
 
 define(`UUCP_RELAY', <replaceable>your.uucp.relay</replaceable>)
 define(`UUCP_MAX_SIZE', 200000)
 define(`confDONT_PROBE_INTERFACES')
 
 MAILER(local)
 MAILER(smtp)
 MAILER(uucp)
 
 Cw    <replaceable>your.alias.host.name</replaceable>
 Cw    <replaceable>youruucpnodename.UUCP</replaceable></programlisting>
 
           <para><literal>accept_unresolvable_domains</literal>¡A
             <literal>nocanonify</literal>¡A ©M
 	    <literal>confDONT_PROBE_INTERFACES</literal> ¯S©Ê±NÁקK¥ô¦ó¦b
 	    »¼°e¶l¥ó®É·|¥Î¨ì DNS ªº¾÷·|¡C<literal>UUCP_RELAY</literal>
 	    ¶µ¥Øªº¥X²{²z¥Ñ«Ü©_©Ç¡A´N¤£­n°Ý¬°¦ó¤F¡C²³æªº©ñ¤J¤@­Óºô»Úºô¸ô
 	    ¤W¥i¥H³B²z .UUCP µêÀÀºô°ì¦ì§}ªº¥D¾÷¦WºÙ¡F³q±`¡A§A¥u»Ý­n¦b³o
 	    ¸Ì¶ñ¤J§A ISP ªº«H¥ó¦^ÂгB (mail replay)¡C</para>
 
           <para>§A¤w¸g°µ¨ì³o¸Ì¤F¡A§AÁٻݭn³o­Ó¥s
 	    <filename>/etc/mail/mailertable</filename>¡C¦pªG§A¥u¦³¤@­Ó¥Î
 	    ¨Ó¶Ç»¼©Ò¦³¶l¥óªº¹ï¥~³q¹Dªº¸Ü¡A¥H¤UªºÀÉ®×´N¨¬°÷¤F¡G</para>
 
           <programlisting>#
 # makemap hash /etc/mail/mailertable.db &lt; /etc/mail/mailertable
                               uucp-dom:<replaceable>your.uucp.relay</replaceable></programlisting>
 
           <para>¥t¤@­Ó§ó½ÆÂøªº¨Ò¤l¬Ý°_¨Ó¹³³o¼Ë¡G</para>
 
           <programlisting>#
 # makemap hash /etc/mail/mailertable.db &lt; /etc/mail/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>¦p§A©Ò¨£¡A³o¬O¬Y­Ó¯u¹êÀɮ׸̪º¤@³¡¥÷¡C­º¤T¦æ³B²zºô°ì©w§}«H¥ó
             ¤£À³¸Ó³Q°e¥X¨ì¤º©w¸ô®|¡A¦Ó¥Ñ¬Y¨Ç UUCP ¾F©~(UUCP neighbor)¨ú¥N
             ªº¯S®í±¡§Î¡A³o¬O¬°¤F <quote>ÁYµu</quote>»¼°eªº¸ô®|¡C¤U¤@¦æ³B²z¨ì
 	    ¥»¦a¤A¤Óºô¸ôºô°ìªº«H¥óÅý¥¦¥i¥H¨Ï¥Î SMTP ¨Ó»¼°e¡C³Ì«á¡AUUCP ¾F©~´£¨ì 
             .UUCP µêÀÀºô°ìªº°O¸ü¡A¤¹³\¤@­Ó <literal><replaceable>uucp-neighbor
             </replaceable>!<replaceable>recipient</replaceable></literal> ±À½
 	    ¤º©w³W«h¡C³Ì«á¤@¦æ«h¥H¤@­Ó³æ¿Wªº¥yÂI°µµ²§ô¡A¥H UUCP »¼°e¨ì´£¨Ñ·í
 	    §A¥þ¥@¬É©Ê¶l¥ó¹hªùªºUUCP ¾F©~¡C©Ò¦³¦b <literal>uucp-dom:</literal>
 	    ÃöÁä¦r¸Ìªº¸`ÂI¦WºÙ¥²¶·³£¬O¦³®Äªº UUCP ¾F©~¡A§A¥i¥H¥Î
 	    <literal>uuname</literal> ©R¥O¥h½T»{¡C
           </para>
 
           <para>´£¿ô§A³o­ÓÀɮצb¨Ï¥Î«e¥²¶·³QÂà´«¦¨ DBM ¸ê®Æ®wÀɮסA³Ì¦n¦b
             mailertable ³Ì¤W­±¥Îµù¸Ñ¼g¥X©R¥O¦C¨Ó§¹¦¨³o­Ó¤u§@¡C·í§A¨C¦¸§ó´«§A
             ªº mailertable «á§AÁ`¬O»Ý­n°õ¦æ³o­Ó©R¥O¡C</para>
 
           <para>³Ì«á´£¥Ü¡G¦pªG§A¤£½T©w¬Y¨Ç¯S©wªº«H¥ó¸ô®|¥i¥Î¡A°O±o§â
             <option>-bt</option> ¿ï¶µ¥[¨ì sendmail¡C³o·|±N sendmail ±Ò°Ê¦b
             <emphasis>address test mode</emphasis>¡F¥u­n«ö¤U
             <literal>0</literal>¡A±µµÛ¿é¤J§A§Æ±æ´ú¸Õªº«H¥ó¸ô®|¦ì§}¡C
             ³Ì«á¤@¦æ§i¶D§A¨Ï¥Î¤º³¡ªº«H¥ó¥N²zµ{¦¡¡A¥N²zµ{¦¡ªº·|³qª¾¥Øªº¥D¾÷¡A
             ¥H¤Î(¥i¯àÂà´«ªº)¦ì§}¡C­nÂ÷¶}¦¹¼Ò¦¡½Ð«ö Control-D¡C</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>3,0 foo@example.com</userinput>
 canonify           input: foo @ example . com
 ..
 parse            returns: $# uucp-dom $@ <replaceable>your.uucp.relay</replaceable> $: foo &lt; @ example . com . &gt;
 <prompt>&gt;</prompt> <userinput>^D</userinput></screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ispmail">
           <para>·í§Ú¥Î¼·±µ³s¤Wºô¸ô®É¸Ó«ç»ò³]©w«H¥ó»¼°e¡H</para>
         </question>
 
         <answer>
           <para>¦pªG§A¤w¸g¦³¤@­Ó©T©wªº IP ¼Æ¦r¡A§A¤£»Ý­n½Õ¾ã¥ô¦ó¤º©w­È¡C³]¦n
             §A­n«ü©wªººô¸ô¦WºÙ¡A¨ä¥Lªº sendmail ³£·|À°§A°µ§¹¡C</para>
 
           <para>¦pªG§A®³¨ìªº¬O°ÊºA°t¸mªº IP ¼Æ¦r¦Ó¨Ï¥Î¼·±µ ppp ³s±µ¨ìºô»Úºô
 	    ¸ô¡A§A¥i¯à¤w¸g¦b§Aªº ISP «H¥ó¥D¾÷¤W¦³¤@­Ó«H½c¡C°²³]§Aªº ISP ºô°ì
 	    ¬O <hostid role="domainname">example.net</hostid>¡A§Aªº¨Ï¥ÎªÌ¦W
 	    ºÙ¬O <username>user</username>¡C¥ç°²³]§AºÙ¦Û¤vªº¥D¾÷¦WºÙ¬O
             <hostid role="fqdn">bsd.home</hostid> ¦Ó§Aªº ISP §i¶D§A¥i¥H¨Ï¥Î
             <hostid role="fqdn">relay.example.net</hostid> ·í§@«H¥ó¦^ÂгB¡C
           </para>
 
           <para>¬°¤F±q§Aªº«H½c±µ¦¬«H¥ó¡A§A±N»Ý­n¦w¸Ë¨ú«Hµ{¦¡¥H«K±q«H½c¨ú¦^«H¥ó¡C
             <application>Fetchmail</application> ¬O¤@­Ó¤£¿ùªº¿ï¾Ü¡A¦]¬°¥¦¤ä
 	    ´©³\¦h¤£¦Pªº³q°T¨ó©w¡A³q±`§Aªº ISP ·|´£¨Ñ POP3¡C¦pªG§A¿ï¾Ü¨Ï¥Î
 	    user-ppp¡A§A¥i¥H¦b³s½u¨ìºô¸ô¦¨¥\«á¦Û°Ê§ì¨ú§Aªº«H¥ó¡A¥u­n¦b
 	    <filename>/etc/ppp/ppp.linkup</filename>¸Ì­±³]©w¥H¤U³o¶µ¡G</para>
 
           <programlisting>MYADDR:
   !bg su user -c fetchmail</programlisting>
 
           <para>°²¨Ï§A¥¿¨Ï¥Î <application>sendmail</application> (¦p¤U©Ò¥Ü)
 	    ¶Ç°e«H¥ó¨ì«D¥»¦a±b¸¹¡A¸m¤J¥H¤U©R¥O¡G</para>
 
           <programlisting>  !bg su user -c "sendmail -q"</programlisting>
 
           <para>¦b¤W­±¨º¶µ©R¥O¤§«á¡C³o·|±j­¢ <application>sendmail</application>
 	    ¦b³s±µ¤Wºô¸ô«á°¨¤W¶}©l³B²z mailqueue¡C</para>
 
           <para>§Ú°²³]§A¦b <hostid role="fqdn">bsd.home</hostid> ¾÷¾¹¤W¦³¤@­Ó
             <username>user</username> ªº±b¸¹¡C¦b <hostid
 	    role="fqdn">bsd.home</hostid> ¾÷¾¹¤W <username>user</username>
 	    ªº®a¥Ø¿ý¸Ì«Ø¥ß¤@­Ó <filename>.fetchmailrc</filename> ªºÀɮסG</para>
 
           <programlisting>poll example.net protocol pop3 fetchall pass MySecret</programlisting>
 
           <para>µL¶·Âب¥¡A³o­ÓÀÉ°£¤F <username>user</username> ¥~¤£À³¸Ó³Q¥ô
 	    ¦ó¤HŪ¨ú¡A¦]¬°¥¦¥]§t <literal>MySecret</literal> ³o­Ó±K½X¡C</para>
 
           <para>¬°¤F¦b±H«H®É¦³¥¿½Tªº©ïÀY <literal>from:</literal>¡A§A¥²¶·§i¶D
 	    <application>sendmail</application> ¨Ï¥Î
 	    <literal>user@example.net</literal> ¦Ó«D
 	    <literal>user@bsd.home</literal>¡C§A¥i¯à·|§Æ±æ§i¶D
             <application>sendmail</application> ±q
             <hostid role="fqdn">relay.example.net</hostid> °e¥X©Ò¦³«H¥ó¡A
             ¥[§Ö«H¥ó¶Ç°e¡C</para>
 
           <para>¥H¤Uªº <filename>.mc</filename> ÀÉÀ³¯àº¡¨¬§Aªº­n¨D¡G</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(`example.net')dnl
 FEATURE(allmasquerade)dnl
 FEATURE(masquerade_envelope)dnl
 FEATURE(nocanonify)dnl
 FEATURE(nodns)dnl
 define(`SMART_HOST', `relay.example.net')
 Dmbsd.home
 define(`confDOMAIN_NAME',`bsd.home')dnl
 define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
 
           <para>¦p¦óÂà´«³o­Ó <filename>.mc</filename> Àɮרì
             <filename>sendmail.cf</filename> Àɪº¸Ô²Ó²Ó¸`¡A½Ð°Ñ¦Ò¤W¤@¸`¡C
             ¥t¥~¡A¦b§ó·s <filename>sendmail.cf</filename> ¥H«á¤£­n§Ñ°O­«·s±Ò°Ê
             <application>sendmail</application>¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="sendmail-alternative">
           <para>°£¤F Sendmail ¥~¡AÁÙ¦³­þ¨Ç¶l¥ó¦øªA¾¹¥i¥H¨Ï¥Î©O¡H</para>
         </question>
 
         <answer>
           <para><ulink url="http://www.sendmail.org/">Sendmail</ulink>
             ¬O FreeBSD ¹w³]¨Ï¥Îªº¶l¥ó¦øªA¾¹¡A¦ý¬O§AÁÙ¬O¥i¥H«Ü®e©ö¦a¥H¨ä¥¦
             ¶l¥ó¦øªA¾¹ (¨Ò¦p¡A±q port ¦w¸Ëªº¶l¥ó¦øªA¾¹) ¨ú¥N¤§¡C</para>
 
           <para>port ¸Ì¦³«Ü¦h¥i¨Ñ¿ï¾Üªº¶l¥ó¦øªA¾¹¡A¹³
             <filename role="package">mail/exim</filename>¡B
             <filename role="package">mail/postfix</filename>¡B
             <filename role="package">mail/qmail</filename>¡B
             <filename role="package">mail/zmailer</filename> 杭A
             ´N¬O´X­Ó«Ü¨üÅwªïªº¿ï¾Ü¡C</para>
 
           <para>¦h¼Ë¿ï¾Ü¬O¦n¨Æ¡A¦Ó¥B¤j®a¦³³\¦h¶l¥ó¦øªA¾¹¥i¥H¨Ï¥Î¤]³Q»{¬°¬O
             ¦n¨Æ¡F©Ò¥H½ÐÁקK¦b³q«H½×¾Â¸Ì°Ý¹³ <quote>Sendmail ¦³¤ñ Qmail
             ¦n¶Ü¡H</quote> ³o¼Ëªº°ÝÃD¡C¦pªG§A¯uªº«Ü·Q°Ýªº¸Ü¡A½Ð¥ý¨ì³q«H½×¾Â
             archive ¸Ì§ä¤@¤U¡C¨C¤@­Ó¶l¥ó¦øªA¾¹ªºÀuÂI»P¯ÊÂI¡A¥H«e¤j·§´N¤w¸g
             °Q½×¦n´X¦¸¤F¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="forgot-root-pw">
           <para>§Ú§Ñ¤F <username>root</username> ±K½X¤F¡I«ç»ò¿ì¡H</para>
         </question>
 	
 	<answer>
           <para>¤£­nÅå·W¡I¥u­n­«·s±Ò°Ê¨t²Î¡A¦b¬Ý¨ì Boot: ®É¿é¤J
             <userinput>boot -s</userinput> §Y¥i¶i¤J³æ¨Ï¥ÎªÌ¼Ò¦¡
             (¦b 3.2-RELEASE ¤§«eªºª©¥»½Ð§ï¥Î <userinput>-s</userinput>)¡C
             ¦b°Ý­n¨Ï¥Î­þ­Ó shell ®É¡A«ö¤U ENTER¡C§A·|¬Ý¨ì¤@­Ó &prompt.root;
             ªº´£¥Ü¸¹¡A¿é¤J <command>mount -u /</command> ¥H­«·s±¾¤W(mount)
             §Aªº®ÚÀɮרt²Î¥i¨ÑŪ/¼g¡C°õ¦æ <command>passwd root</command>
             ¥H§ó´« <username>root</username> ±K½X¡AµM«á°õ¦æ &man.exit.1;
 	    Ä~Äò±Ò°Êµ{§Ç¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="CAD-reboot">
           <para>§Ú¸Ó«ç»òÅý Control-Alt-Delete ¤£·|­«·s±Ò°Ê¨t²Î¡H</para>
         </question>
 
         <answer>
           <para>¦pªG§A¬O¨Ï¥Î FreeBSD 2.2.7-RELEASE ©Î¤§«áª©¥»ªº
             syscons(¨t²Î¤º©wªº¥D±±¥xÅX°Êµ{¦¡)¡A§â¤U¦C³o¦æ©ñ¨ì®Ö¤ß³]©wÀɤº¡A
             µM«á­«°µ¤@­Ó·sªº®Ö¤ß¡G</para>
 
           <programlisting>options SC_DISABLE_REBOOT</programlisting>
 
           <para>­Y¬O¨Ï¥Î FreeBSD 2.2.5-RELEASE ©Î¤§«áª©¥»ªº PCVT ¥D±±¥xÅX°Ê
 	    µ{¦¡¡A«h¥H¤U¦C¿ï¶µ¥N´À¡G</para>
 
           <programlisting>options PCVT_CTRL_ALT_DEL</programlisting>
 
           <para>¨ä¥L§ó¦­´Áªº FreeBSD ª©¥»¡A½Ð­×§ï§A¥¿¦b¨Ï¥Îªº¥D±±¥xÁä½L¹ïÀ³¡A
             ¨Ã±N©Ò¦³ <literal>boot</literal> ÃöÁä¦r¥H <literal>nop</literal>
             ¨ú¥N¡C¤º©wªºÁä½L¹ïÀ³¬O¦b
             <filename>/usr/share/syscons/keymaps/us.iso.kbd</filename>¡C
             §A¥i¯à»Ý­n©ú¥Õªº§h©J <filename>/etc/rc.conf</filename> ¥hŪ¨ú
             ³o­ÓÁä½L¹ïÀ³¥H½T«O§ó°Ê¥Í®Ä¡C·íµM¦pªG§A¥¿¦b¥Î¾A¦X§A°êÄyªºÁä½L¹ïÀ³¡A
             §AÀ³¸Ó½s¿è¨º¤@­Ó¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="dos-to-unix-txt">
           <para>§Ú¸Ó«ç»ò§â DOS ¤å¦rÀÉ®×­«·s®æ¦¡¤Æ¦¨ UNIX ªº¡H</para>
         </question>
 
         <answer>
           <para>¥u­n¨Ï¥Î³o­Ó perl ©R¥O¡G</para>
 
           <screen>&prompt.user; <userinput>perl -i.bak -npe 's/\r\n/\n/g' file ...</userinput></screen>
 
           <para>file ´N¬O­n³B²zªºÀɮסC³o­Ó­×§ï¬O¦b¤º³¡§¹¦¨¡A­ì©lªºÀÉ®×·|Àx¦s¦¨
             °ÆÀɦW¬° .bak ªºÀɮסC</para>
 
           <para>©ÎªÌ§A¥i¥H¨Ï¥Î &man.tr.1; ³o­Ó©R¥O¡G</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> ¬O¥]§t DOS ¤å¦rªº
 	    ÀɮסA¦Ó <replaceable>unix-text-file</replaceable> «h¬O¥]§tÂà´«
 	    ªº¿é¥Xµ²ªG¡C³o¤ñ¨Ï¥Î perl ÁÙ­n§Ö¤W¤@ÂIÂI¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="kill-by-name">
           <para>§Ú¸Ó«ç»ò¥Î¦WºÙ¬å±¼ process¡H</para>
         </question><answer>
 
           <para>¨Ï¥Î &man.killall.1; ¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="root-acl">
           <para>¬°¦ó¦b su ¤@ª½»¡§Ú¤£¦b <username>root</username> ªº ACL ¸Ì¡H
             </para>
         </question>
 
         <answer>
           <para>³o­Ó¿ù»~¬O¦]¬° Kerberos ¤À´²»{ÃÒ¨t²Î¡C³o­Ó°ÝÃD¨Ã¤£¬O«ÜÄY­«
             ¦ý¬O¥O¤H¹½·Ð¡C§A¥i¥H¥Î -K ¿ï¶µ¥h°õ¦æ su¡A©Î¬O¹³¤U­Ó°ÝÃD©Ò´y­zªº
             ²¾°£ Kerberos¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="uninstall-kerberos">
           <para>§Ú¸Ó«ç»ò²¾°£ Kerberos¡H</para>
         </question>
 
         <answer>
           <para>­n±q¨t²Î¸Ì²¾°£ Kerberos¡A­«¸Ë§A¥¿¦b°õ¦æªº release ª©¥»ªº
 	    bin distribution¡C¦pªG§A¦³ CDROM¡A§A¥i¥H mount cd(°²³]¦b /cdrom)
 	    ¨Ã°õ¦æ¡G</para>
 
           <screen>&prompt.root; <userinput>cd /cdrom/bin</userinput>
 &prompt.root; <userinput>./install.sh</userinput></screen>
 
           <para>©ÎªÌ§A¤]¥i¥H±N <filename>/etc/make.conf</filename> ¸Ìªº
             "MAKE_KERBEROS" ¿ï¶µ¥þ³£®³±¼¡AµM«á¦A build world.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="add-pty">
           <para>§Ú¸Ó«ç»ò¼W¥[¨t²ÎªºµêÀÀ²×ºÝ¾÷¡H</para>
         </question>
 
         <answer>
           <para>¦pªG§A¦³³\¦h telnet¡Assh¡AX ©Î¬O screen ¨Ï¥ÎªÌ¡A§A©Î³\·|¥Î§¹
             µêÀÀ²×ºÝ¾÷¡A³o¯à±Ð§A«ç»ò¥[§ó¦h¡G</para>
 
             <procedure>
               <step>
                 <para>«Ø¥ß¨Ã¦w¸Ë¤@­Ó·sªº®Ö¤ßµ{¦¡¨Ã¥B§â³o¤@¦æ</para>
 
                 <programlisting>pseudo-device pty 256</programlisting>
 
                 <para>¥[¤J¨ì³]©wÀɸ̡C</para>
               </step>
 
               <step>
                 <para>°õ¦æ³o­Ó©R¥O¡G</para>
 
                 <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>sh MAKEDEV pty{1,2,3,4,5,6,7}</userinput></screen>
 
                 <para>·|³y¥X 256 ­ÓµêÀÀ²×ºÝ¾÷ªº¸Ë¸m¸`ÂI¡C</para>
 
               </step>
 
               <step>
                 <para>½s¿è <filename>/etc/ttys</filename> ¨Ã¥[¤J²Å¦X 256
                   ­Ó²×ºÝ¾÷ªº¦æ¼Æ¡C¥¦­ÌÀ³¸Ó²Å¦X¤w¸g¦s¦b³æ¶µªº®æ¦¡¡AÁ|¨Ò¨Ó»¡¡A
                   ¥¦­Ì¬Ý°_¨Ó¹³¡G</para>
 
                 <programlisting>ttyqc none network</programlisting>
 
                 <para>¦r¥À³]­pªº¶¶§Ç¬O
                   <literal>tty[pqrsPQRS][0-9a-v]</literal>¡A¨Ï¥Î¥¿³Wªí¥Ü¦¡¡C
                 </para>
               </step>
 
               <step>
                 <para>¥Î·sªº®Ö¤ßµ{¦¡­«·s±Ò°Ê¹q¸£´N¥i¥H¤F¡C</para>
               </step>
             </procedure>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="create-snd0">
           <para>/dev/snd0 ³o­Ó¸Ë¸m°µ¤£¥X¨Ó¡I</para>
         </question>
 
         <answer>
           <para>¨Ã¨S <devicename>snd</devicename> ³o­Ó¸Ë¸mªº¦s¦b¡C³o­Ó¦W¦r
             ¬O¥Î¨Ó·í§@¦U­Ó²Õ¦¨ FreeBSD Án­µÅX°Êµ{¦¡²Õ¡A½Ñ¦p
             <devicename>mixer</devicename>¡A
 	    <devicename>sequencer</devicename>¡A¥H¤Î
             <devicename>dsp</devicename> ªºÂ²ºÙ¡C</para>
 
           <para>¥i¥H¥Î¥H¤Uªº©R¥O§@¥X³o¨Ç¸Ë¸m¡G</para>
 
           <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>sh MAKEDEV snd0</userinput></screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="reread-rc">
           <para>¥i¥H¤£¥Î¶}¾÷¡A­«·sŪ¨ú <filename>/etc/rc.conf</filename>¡B
             ¦A¦¸±Ò°Ê <filename>/etc/rc</filename> ¶Ü?</para>
         </question>
 
         <answer>
           <para>¥ý¶i¤J³æ¤H¨Ï¥ÎªÌ¼Ò¦¡¡AµM«á¦A¦^¨ì¦h¨Ï¥ÎªÌ¼Ò¦¡¡C</para>
 
           <para>¦b¥D±±¥x°õ¦æ¡G</para>
 
           <screen>&prompt.root; <userinput>shutdown now</userinput>
 (Note: without -r or -h)
 
 &prompt.root; <userinput>return</userinput>
 &prompt.root; <userinput>exit</userinput></screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="sandbox">
           <para>¤°»ò¬O sandbox¡H</para>
         </question><answer>
 
           <para><quote>Sandbox</quote> ¬O¨t²Î¦w¥þ¥Îªº³N»y¡A¦³¨â­Ó·N¸q¡G</para>
 
             <itemizedlist>
               <listitem>
 
                 <para>©ñ¦b¬Y¨ÇµêÀÀ¨¾Å@Àð¸Ìªº°õ¦æµ{§Ç¡A³o¨Ç¨¾Å@Àð¬O¥Î¨Óªý¤î
                   ¬Y¨Ç¤H«I¤J³o¹Dµ{§Ç¡A¶i¦Ó¥X¤J©ó§ó¤jªº¨t²Î¤¤¡C</para>
 
                 <para>³o¹Dµ{§Ç¥i¥H§¹¥þ¦b¨¾Å@Àð¸Ì <quote>°Ê§@</quote>¡C¤]´N
 		  ¬O»¡¡A¥¦©Ò°õ¦æªº¥ô¦óµ{¦¡¤£¥i¯à·|º¯³z¨ìÀ𪺥~­±¡C©Ò¥H¦pªG
 		  ±z¹ï¥¦¦³¦w¥þ¤WªºÅU¼{¡A¨Ã¤£»Ý­n¯S§O¥hºÊÅ¥¥¦ªº¤@Á|¤@°Ê¡A¤Ï
 		  ¥¿¥¦¥u¯à¦bÀ𤺬¡°Ê¡C</para>
 
                 <para>Á|¨Ò¨Ó»¡¡A¥i¥H¥Î userid ¨Ó°µ³o¹D¨¾Å@Àð¡A³o¥¿¬O security
                   ©M named »¡©ú¤å¥ó¤¤ªº©w¸q¡C</para>
 
                 <para>²{¦b´N¥Î <literal>ntalk</literal> ³o­ÓªA°È§@»¡©ú¡]¨£
                   /etc/inetd.conf¡^¡C³o­ÓªA°È¥H«eªº userid ¬O
                   <username>root</username>¡A²{¦b°õ¦æ®É«h¬O¥Î
                   <username>tty</username>¡C<username>tty</username>
                   ³o­Ó¨Ï¥ÎªÌ´N¬O¤@­Ó sandbox¡A¦pªG¦³¤H¯à°÷¶¶§Q¥Î ntalk
                   «I¤J¨t²Î¡A²{¦b¥L´Nºâ¶i±o¨Ó¤]¥u¯à¥Î³o­Ó userid¡C</para>
               </listitem>
 
               <listitem>
                 <para>©ñ¦b¬Y­Ó¼ÒÀÀ¾÷¾¹¸Ìªºµ{¦¡¡A³o¤ñ¤W­z¨Ó±o§óÄY±K¡C°ò¥»¤W
                   ³oªí¥Ü¯à«I¤J¸Óµ{¦¡ªº¤H¬Û«H¥L¯à¦A¶i¤J©ÒÄݪº¾÷¾¹¡A¦ý¨Æ¹ê¤W
                   ¥u·|¶i¤J¼ÒÀÀ¥X¨Óªº¾÷¾¹¡AµLªk¶i¤@¨B­×§ï¥ô¦ó¯u¹êªº¸ê®Æ¡C</para>
 
                 <para>¹F¨ì³o­Ó¥Øªº³Ì±`¥Îªº¤èªk¡A´N¬O¦b¬Y­Ó¤l¥Ø¿ý¤U°µ¥X¼ÒÀÀªº
                   Àô¹Ò¡AµM«á¥Î chroot °õ¦æ¸Óµ{¦¡¡A³o¼Ë¸Óµ{¦¡ªº®Ú¥Ø¿ý«K¬O³o­Ó
                   ¤l¥Ø¿ý¡A¦Ó«D¨t²Î¯u¥¿ªº®Ú¥Ø¿ý¡C</para>
 
                 <para>¥t¤@­Ó±`¨£§@ªk¬O±N¬Y­ÓÀɮרt²Î mount ¦¨°ßŪ¡A¦ý¦b¥¦
                   ¤W­±¥t¥~»s³y¥Xµ{¦¡¥H¬°¥i¥H¼g¤JªºÀɮרt²Î¡C³o­Óµ{¦¡·|¬Û«H
                   ¥¦¥i¥H¹ï¨ä¥LÀÉ®×Ū¼g¡A¦ý¥u¦³¥¦¬Ý¤£¨ì³o­Ó°ßŪ®ÄÀ³ - ¨t²Î
                   °õ¦æªº¤@¯ëµ{¦¡³£¬Ý±o¨ì¡C</para>
 
                 <para>§Ú­Ì¸Õ¹Ï±N³oÃþ sandbox ºÉ¶q³z©ú¤Æ¡AÅý¨Ï¥ÎªÌ©Î«I¤JªÌ
                   µLªk¬Ý¨ì¥L¬O§_¦b¬Y­Ó sandbox ¸Ì­±¡C</para>
               </listitem>
             </itemizedlist>
 
           <para>UNIX ¹ê§@¨âºØ sandbox¡A¤@­Ó¦bµ{¦¡¼h­±¡A¥t¤@­Ó«h¬O¥Ñ userid
             ¨Ó¹F¦¨¡C</para>
 
           <para>¨C­Ó UNIX °õ¦æµ{§Ç·|¥Î¨¾¤õÀð±N¥¦©M©Ò¦³¨ä¥Lµ{§Ç¹j¶}¡A¬Y­Óµ{§Ç
             ¤£¥i¥HÀH·N­×§ï¨ä¥Lµ{§Ç¦ì§}ªº¸ê®Æ¡C³o©M Windows ¤¤¡Aµ{¦¡¥i¥H»´©ö
             ­×§ï¨ä¥L¦ì§}¸ê®Æ¡Aµ²ªG¾É­P·í¾÷ªº±¡§Î¤j¤£¬Û¦P¡C</para>
 
           <para>¨C­Ó UNIX µ{§Ç³£ÄÝ©ó¬Y­Ó¯S©wªº userid¡C¦pªG¸Ó userid ¤£¬O
             <username>root</username>¡A´N·|±N¥¦©M¨ä¥L¨Ï¥ÎªÌªºµ{§Ç¹j¶}¡C
             Userid ¦P®É¤]¥Î©óµwºÐ¸ê®Æªº¦s¨úÅv¤W¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="securelevel">
           <para>¤°»ò¬O securelevel?</para>
         </question>
 
         <answer>
           <para>securelevel ¬O®Ö¤ß¤¤©Ò¹ê§@ªº¤@­Ó¦w¥þ¾÷¨î¡C°ò¥»¤W·í
             securelevel ¬O¥¿­È®É¡A®Ö¤ß·|­­¨î¬Y¨Ç¤u§@¡F§Y¨Ï¬O superuser
             (¤]´N¬O <username>root</username>) ¤]µLªk§¹¦¨¨º¨Ç¤u§@¡C¦b¼¶¼g
             ¥»¤å®É¡Asecurelevel ¾÷¨î¦b¤@¯ëªº­­¨î¥~¡AÁÙ¯à°÷­­¨î¥H¤Uªº¥\¯à¡G
           </para>
 
           <itemizedlist>
             <listitem>
               <para>²M°£¬Y¨Ç¯S©wªºÀɮ׺X¼Ð¡A¨Ò¦p <literal>schg</literal>
                 (¨t²Î°ßŪ¼ÐºX, the system immutable flag)</para>
             </listitem>
 
             <listitem>
               <para>¸g¥Ñ <devicename>/dev/mem</devicename> »P
                 <devicename>/dev/kmem</devicename>¡A ±N¸ê®Æ¼g¤J¦Ü®Ö¤ß°O¾ÐÅ餤
               </para>
             </listitem>
 
             <listitem>
               <para>¸ü¤J®Ö¤ß¼Ò²Õ</para>
             </listitem>
 
             <listitem>
               <para>§ó°Ê &man.ipfirewall.4; ³W«h¡C</para>
             </listitem>
           </itemizedlist>
 
           <para>·Q­nÀˬd¦b¬Y­Ó¹B§@¤¤ªº¨t²Îªº securelevel ª¬ºA¡A¥u­n°õ¦æ¥H¤U
             ©R¥O§Y¥i¡G</para>
 
           <screen>&prompt.root; <userinput>sysctl kern.securelevel</userinput></screen>
 
           <para>¿é¥Xªºµ²ªG·|¥]§t¤@­Ó &man.sysctl.8; ÅܼƦWºÙ (¦b³o­Ó¨Ò¤l¤¤¡A
             ¥¦¬O <varname>kern.securelevel</varname>) ¥H¤Î¤@­Ó¼Æ¦r¡C«áªÌ§Y¬O
             ¥Ø«eªº securelevel ­È¡C¦pªG¥¦¬O¤@­Ó¥¿­È (¤]´N¬O¤j©ó 0)¡Aªí¥Ü¦Ü¤Ö
             ¦³¤@¨Ç securelevel ªº«OÅ@¾÷¨î¤w¸g¶}±Ò¤F¡C</para>
 
           <para>§A¨S¦³¿ìªk­°§C¤@­Ó¹B§@¤¤ªº¨t²Îªº securelevel¡F¦pªG¥i¥Hªº¸Ü¡A
             ´N¥¢¥h¤F³o­Ó¾÷¨îªº·N¸q¤F¡C¦pªG§A­n§@¤@¨Ç»Ý­n securelevel ¬°
             «D¥¿­È¤~¥i¥Hªº°Ê§@ªº¸Ü (¨Ò¦p <maketarget>installworld</maketarget>
             ©Î§ó°Ê¤é´Á)¡A§A»Ý­n­×§ï <filename>/etc/rc.conf</filename> ¤ºªº
             securelevel ³]©w (§ä§ä <varname>kern_securelevel</varname> ©M
             <varname>kern_securelevel_enable</varname> ÅܼÆ)¡AµM«á­«·s¶}¾÷¡C
           </para>
 
           <para>·Q­nª¾¹D§ó¦h¦³Ãö©ó securelevel »P¦U­Ó¤£¦Pµ¥¯Å¼vÅTªº²Ó¸`¡A
             ½Ð°Ñ¦Ò &man.init.8; »¡©ú¤å¥ó¡C</para>
 
             <warning>
               <para>securelevel ¥i¤£¬O¸UÆF¤¦¡F¥¦¦³³\¦h¤wª¾ªº¯Ê³´¡A©¹©¹³y¦¨
                 ¤@ºØ¦w¥þªº°²¶H¡C</para>
 
               <para>¥¦¤@­Ó³Ì¤jªº°ÝÃD¡A´N¬O­nÅý³o­Ó¥\¯à§¹¥þ¦³®Äªº¸Ü¡A¦b
                 securelevel µo´§§@¥Î«eªº±Ò°Ê¹Lµ{¤¤¡A©Ò¦³¨Ï¥Î¨ìªºÀɮ׳£
                 ¥²¶·³Q«OÅ@°_¨Ó¡C¦pªG¤@­Ó§ðÀ»ªÌ¦b securelevel ¦³®Ä«e (¥Ñ©ó
                 ¦³¨Ç¨t²Î¦b±Ò°Ê¤¤©Ò§@ªº¨Æ±¡¡AµLªk¦b¸û°ªªº securelevel ¤¤
                 ¥¿±`¹B§@¡A©Ò¥H³o·|¦b±Ò°Ê¹Lµ{¤¤«á´Á¤~·|¹B§@)¡A¯àÅý¥L­Ìªºµ{¦¡
                 ³Q°õ¦æªº¸Ü¡Asecurelevel ªº«OÅ@´N§¹¥þµL®Ä¤F¡C«OÅ@±Ò°Êµ{§Ç
                 ¤¤©Ò¦³ªºÀɮצb§Þ³N¤W¬O¥i¦æªº¡A¦ý¬O¦pªG¯uªº³o¼Ë§@ªº¸Ü¡A¨t²Î
                 ºûÅ@±N·|Åܦ¨¤@³õ¹ÚÆL¡C§Y¨Ï¥u¬O­×§ï¤@­Ó³]©wÀÉ¡A¤]¥²¶·±N¾ã­Ó
                 ¨t²ÎÃö³¬¡A¦Ü¤Ö¤]±o¨ì³æ¤H¼Ò¦¡¡C</para>
 
               <para>°£¤F³oÂI¡AÁÙ¦³³\¦h¨ä¥¦ªºªF¦è³£¦b³q«H½×¾Â¤W°Q½×¡A¤×¨ä¬O
 	        freebsd-security¡C½Ð¨ì <ulink
 		url="../../../../search/index.html">³o¸Ì</ulink> ·j´M¥H«eªº
                 °Q½×¡C¦³¨Ç¤H§Æ±æ securelevel ¯à°÷¾¨§Ö®ø¥¢¡A¥Ñ¥t¤@­Ó§óÀu¨qªº
                 ¾÷¨î¨ú¥N¡A¤£¹L¾÷·|¦³ÂI´ù¯í¡C</para>
 
               <para>­·ÀI¦Û¦æ©Ó¾á¡C</para>
             </warning>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="release-candidate">
           <para>§Ú·Q­n§â§Úªº¨t²Îª@¯Å¨ì³Ì·sªº -STABLE¡A¦ý¬O±o¨ìªº¬O -RC ©Î
             -PRERELEASE¡I«ç»ò¤F¡H</para>
         </question>
 
         <answer>
           <para>²³æ¦a»¡¡G¨º¥u¬O¦W¦r¦Ó¤w¡CRC ªº·N«ä¬O <quote>Release Candiate¡A
             µo¦æ­Ô¿ïª©¥»</quote>¡A¥¦ªí¥Ü·sª©¥»§Ö­nµo¦æ¤F¡C¦b FreeBSD ¤¤¡A
             -PRERELEASE ³q±`¬Oµo¦æ«eªºµ{¦¡½X­áµ²ªº¥N¦Wµü¡C(¦³¨Çµo¦æª©¥»¤¤¡A
             -BETA ¼ÐÅÒ¸ò -PRERELEASE ¬O¬Û¦P·N«äªº¡C)</para>
 
           <para>¸Ô²Ó¦a»¡¡GFreeBSD ±q¨â­Ó¦a¤è¤À¤ä¥X¥¦ªºµo¦æª©¥»¡C¥Dª©¸¹¡B
             ÂI¹s¡Brelease (¨Ò¦p 3.0-RELEASE ¤Î 4.0-RELEASE) ªº¡A¬O±qµo®i¹Lµ{
             ¶}©l®É¤À¤ä¥X¨Óªº¡A³q±`ºÙ¬° <link linkend="current">-CURRENT
             </link>¡C¦³°Æª©¸¹ªºª©¥» (¨Ò¦p 3.1-RELEASE ©Î 4.2-RELEASE)¡A¬O
             ¬¡ÅDªº <link linkend="stable">-STABLE</link> ¤À¤ä¤¤ªºµo¦æª©¥»
             §Ö·Ó¡C±q 4.3-RELEASE ¶}©l¡A¨C¤@­Óµo¦æª©¥»¦³¥¦¦Û¤vªº¤À¤ä¡A¥i¬°
             °¾¦n·¥«×«O¦uªºµo®i³t«× (³q±`¥u·|§@¦w¥þ¤è­±ªº§ó·s) ªº¤H©Ò¥Î¡C</para>
 
           <para>·Ç³Æ­n»s§@µo¦æª©¥»®É¡A¨ä©Ò¦bªº¤À¤ä·|¸g¹L¤@©wªºµ{§Ç¡C¦³¤@­Ó¬O
             µ{¦¡½X­áµ²¡C·íµ{¦¡½X­áµ²¶}©l®É¡A¤À¤ä¦WºÙ·|§ó¦W¡A¥H¤Ï¬M¥¦§Ö­n¦¨¬°
             ¤@­Óµo¦æª©¥»¤F¡CÁ|­Ó¨Ò¤l¡A¦pªG­ì¨Óªº¤À¤ä¥s 4.5-STABLE¡A¥¦ªº¦W¦r
             ·|Åܦ¨ 4.6-PRERELEASE ¥Hªí¥Üµ{¦¡½X¤w­áµ²¡A¨Ã¥BÃB¥~ªºµo¦æ«e´ú¸Õ
             ±N­n¶}©l¤F¡C¯äÂΧ󥿤´¥i¦^³ø¡A¥H¦¨¬°µo¦æª©¥»ªº¤@³¡¥÷¡C·íµ{¦¡½X
             ¦³¤F¥i¦¨¬°µo¦æª©¥»ªºÂú§Î®É¡A¥¦ªº¦W¦r´N·|Åܦ¨ 4.6-RC¡A¥Hªí¥Üµo¦æ
             ª©¥»§Ö¦n¤F¡C¶i¤J RC ¶¥¬q«á¡A¥u¦³§ä¨ìªº³Ì¦³¼vÅTªº¯äÂΤ~·|³Q­×¥¿¡C
             ·íµo¦æª©¥» (¥»¨Ò¤¤¬° 4.6-RELEASE) ²£¥Í«á¡Aµo¦æª©¥»·|¦³¦Û¤vªº¤À¤ä¡A
             ­ì¤À¤ä·|³Q§ó¦W¬° 4.6-STABLE¡C</para>
 
           <para>·Q­n±oª¾§ó¦h¦³Ãöª©¥»¸¹½X»P¦U CVS ¤À¤äªº¸ê°T¡A½Ð°Ñ¦Ò
             <ulink url="../../articles/releng/article.html">Release
             Engineering</ulink> ¤@¤å¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="kernel-chflag-failure">
           <para>§Ú¸ÕµÛ­n¦w¸Ë¤@­Ó·sªº®Ö¤ß¡A¦ý¬OµLªk chflags¡C§Ú¸Ó«ç»ò¸Ñ¨M¡H
           </para>
         </question>
 
         <answer>
           <para>²³æ¦a»¡¡G§Aªº securelevel ¥i¯à¤j©ó¹s¡Cª½±µ­«·s¶}¾÷¨ì
             ³æ¤H¼Ò¦¡¡A¦A¦w¸Ë®Ö¤ß¡C</para>
 
           <para>¸Ô²Ó¦a»¡¡GFreeBSD ¦b securelevel ¤j©ó¹s±¡ªp¤U¡A¤£¤¹³\
             Åܧó¨t²ÎºX¼Ð (system flags)¡C§A¥i¥H¥Î³o­Ó«ü¥OÀˬd§Aªº
             securelevel¡G</para>
 
           <screen>&prompt.root; <userinput>sysctl kern.securelevel</userinput></screen>
 
            <para>§A¨S¦³¿ìªk­°§C securelevel¡F§A¥²¶·±Ò°Ê¨t²Î¨ì³æ¤H¼Ò¦¡¥H
             ¦w¸Ë®Ö¤ß¡A©Î¬O­×§ï <filename>/etc/rc.conf</filename> ¤ºªº
             securelevel ¦A­«·s¶}¾÷¡C½Ð°Ñ¦Ò &man.init.8; »¡©ú¤å¥ó¡A¥H¨ú±o
             §ó¦h¦³Ãö securelevel ªº¸ê°T¡AÁÙ¦³ <filename>/etc/defaults/rc.conf
             </filename> ©M &man.rc.conf.5; »¡©ú¤å¥ó¡A¥H¨ú±o§ó¦h¦³Ãö rc.conf
             ªº¸ê°T¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="kernel-securelevel-time">
           <para>¦b§Úªº¨t²Î¤W¡A§ÚµLªkÅܧó®É¶¡¶W¹L¤@¬í¥H¤Wªº½d³ò¡I
             §Ú¸Ó«ç»ò¿ì¡H</para>
         </question>
 
         <answer>
           <para>²³æ¦aÁ¿¡G§A¨t²Îªº securelevel ¤]³\¤j©ó 1¡Cª½±µ­«·s¶}¾÷¦Ü
             ³æ¤H¼Ò¦¡¡AµM«á¦A­×§ï®É¶¡¡C</para>
 
           <para>¸Ô²Ó¦a»¡¡G¦b securelevel ¤j©ó 1 ªº±¡ªp¤U¡AFreeBSD ¤£¤¹³\®É¶¡
             Åܰʤj©ó¤@¬í¡C§A¥i¥H¥Î¥H¤Uªº©R¥O¨ÓÀˬd¥Ø«eªº securelevel¡G</para>
 
           <screen>&prompt.root; <userinput>sysctl kern.securelevel</userinput></screen>
 
            <para>§AµLªk­°§C securelevel¡F§A¥²¶·±Ò°Ê¹q¸£¦Ü³æ¤H¼Ò¦¡¤U¥H­×§ï®É¶¡¡A
              ©Î¬O­×§ï <filename>/etc/rc.conf</filename> ¦A­«·s¶}¾÷¡C½Ð°Ñ¦Ò
              &man.init.8; »¡©ú¤å¥ó¡A¥H¨ú±o§ó¦h¦³Ãö securelevel ªº¸ê°T¡AÁÙ¦³
              <filename>/etc/defaults/rc.conf</filename> ©M &man.rc.conf.5;
              »¡©ú¤å¥ó¡A¥H¨ú±o§ó¦h¦³Ãö rc.conf ªº¸ê°T¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="statd-mem-leak">
           <para>¬°¤°»ò <command>rpc.statd</command> ¥Î¤F 256 megabytes
             ªº°O¾ÐÅé¡H</para>
         </question>
 
         <answer>
           <para>¤£¡A¨º¤£¬O memory leak¡A¦Ó¥B¥¦¤]¤£¬O¯uªº¥Î¤F 256 Mbyte
             ªº°O¾ÐÅé¡C¥¦¥u¬O³ßÅw (·N«ä´N¬OÁ`·|³o¼Ë§@) ±N¤@ª¯²¼ªº°O¾ÐÅé
             ¬MÁ¨쥦¦Û¤vªº¦ì§}ªÅ¶¡¡A¥H¤è«K§@¨Æ¡C´N§Þ³N¦Ó¨¥¡A³o¼Ë¨Ã¨S¦³
             ¤°»ò¤£¹ï¡F³o¼Ë¥u¬O·|Åý &man.top.1; ©M &man.ps.1; À~¤@¤j¸õ¦Ó¤w¡C
           </para>
 
           <para>&man.rpc.statd.8; ·|±N¥¦ªºª¬ºAÀÉ®× (¦ì©ó <filename>/var
             </filename>) ¬M®g¦Ü¥¦ªº¦ì§}ªÅ¶¡¸Ì¡F¬°¤F¨¾¤î»Ý­nªº®É­Ô¦A¼W¤j©Ò
             ¾É­Pªº­«·s¬M®g¡A¥¦¤@¦¸·|¨Ï¥Î¬Û·í¤jªº¤j¤p¡C±qµ{¦¡½X¨Ó¬Ýªº¸Ü´N
             §ó©úÅã¤F¡A¥i¥H¬Ý¨ì &man.mmap.2; ªºªø«×°Ñ¼Æ¬° <literal>0x10000000
             </literal>¡A¥¦¬O IA32 ¬[ºc¤Wªº¤Q¤»¤À¤§¤@ªº©w§}ªÅ¶¡¡A¤]´N¬O
             256MB¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="unsetting-schg">
           <para>¬°¤°»ò§Ú¨S¿ìªk¨ú®ø <literal>schg</literal> Àɮ׺X¼Ð¡H</para>
         </question>
 
         <answer>
           <para>§A¥¿¦b¤@­Ó´£°ª¤F securelevel (¤]´N¬O¤j©ó 0) ªº¨t²Î¹B§@¡C
             ­°§C securelevel ¦A¸Õ¸Õ¬Ý¡C½Ð°Ñ¦Ò <link linkend="securelevel">
             FAQ ¤¤¹ï securelevel ªº»¡©ú</link> ©M &man.init.8; »¡©ú¤å¥ó¡C
           </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ssh-shosts">
 	  <para>¬°¤°»òªñ¨Óªº·sª© FreeBSD ¹w³]µLªk§Q¥Î <filename>.shosts
             </filename> §¹¦¨ SSH »{ÃÒ¡H</para>
 	</question>
 
 	<answer>
 	  <para>¬°¤°»òªñ¨Ó·sª© FreeBSD <filename>.shosts</filename> »{ÃÒ¹w³]
             ¬°¨ú®øªº­ì¦]¡A¬O¦]¬° &man.ssh.1; ¹w³]¤£¦w¸Ë¬° suid ¦¨ <username>
             root</username>¡C­n <quote>­×¥¿</quote> ³oÂI¡A§A¥i¥H§@¤U¦Cªº
             ¥ô¦ó¤@¥ó¨Æ¡G</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>­n¤@³Ò¥Ã¶h¸Ñ¨M¡A½Ð±N <filename>/etc/make.conf</filename>
                 ¸Ìªº <makevar>ENABLE_SUID_SSH</makevar> ³]¦¨ <literal>true
                 </literal>¡AµM«á¦A­«·s build ssh (©Î¬O°õ¦æ <command>make
                 world</command>)¡C</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>¥u§@¤@®Éªº­×¥¿ªº¸Ü¡A¥i¥H <username>root</username> ¨­¥÷
                 °õ¦æ <command>chmod 4755 /usr/bin/ssh</command> ±N
                 <filename>/usr/bin/ssh</filename> ³]¦¨ <literal>4555
                 </literal>¡CµM«á±N <makevar>ENABLE_SUID_SSH= true</makevar>
                 ¥[¤J <filename>/etc/make.conf</filename> ¸Ì¡A³o¼Ë¤U¦¸
                 <command>make world</command> °õ¦æ´N·|¥Í®Ä¤F¡C</para>
 	    </listitem>
 	  </itemizedlist>
 	</answer>
       </qandaentry>
 
       <qandaentry>
         <question id="vnlru">
           <para>¤°»ò¬O <literal>vnlru</literal>?</para>
         </question>
 
         <answer>
           <para>·í¨t²Î¹F¨ì¤W­­ <varname>kern.maxvnodes</varname> ®É¡A
             <literal>vnlru</literal> ·|²M°£¨ÃÄÀ©ñ vnode¡C³o­Ó®Ö¤ß
             °õ¦æºü¤j³¡¥÷ªº®É¶¡³£¨S¨Æ§@¡A¥u¦³·í§A¦³«Ü¤jªº°O¾ÐÅé¡A¦Ó¥B
             ¥¿¦b¦s¨ú¤W¸U­Ó¤pÀɮ׮ɡA¤~·|³Q±Ò°Ê¡C</para>
         </answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter id="x">
     <chapterinfo>
       <author>
 	<firstname>Wei-Hon</firstname>
 	<surname>Chen</surname>
 	<affiliation>
 	  <address><email>plasmaball@pchome.com.tw</email></address>
 	</affiliation>
       </author>
     </chapterinfo>
 
     <title>X Window System ¤Î Virtual Consoles</title>
 
     <qandaset>
       <qandaentry>
         <question id="running-X">
           <para>§Ú·Q­n°õ¦æ X ¡A§Ú¸Ó«ç»ò°µ¡H</para>
         </question>
 
         <answer>
 
           <para>³Ì²³æªº¤èªk´N¬O¦b¦w¸Ë¨t²Îªº®É­Ô¤@¨Ö¦w¸Ë¡C</para>
 
           <para>µM«á¬Ý¬Ý <command>xf86config</command> ªº¤å¥ó¡A³o­Óµ{¦¡¥i¥H
             À°±z³]©w XFree86(tm) ¨Ï¥¦¯à°÷¨Ï¥Î±zªºÅã¥Ü¥d/·Æ¹«µ¥¶gÃä¡C</para>
 
           <para>±z©Î³\¤]·Q¸Õ¸Õ¬Ý Xaccel server¡C¸Ô±¡½Ð¬Ý <link linkend="xig">
             Xi Graphics</link> ©Î¬O <link linkend="metrox">Metro Link</link>
             ³o¤@¬q¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="running-X-securelevels">
           <para>§Ú <emphasis>¸ÕµÛ</emphasis> ­n°õ¦æ X, ¦ý¬O·í§ÚÁä¤J
             <command>startx</command> ®É¡A±o¨ì
             <errorname>KDENABIO failed (Operation not permitted)</errorname>
             ¿ù»~¡C§Ú¸Ó«ç»ò¿ì¡H</para>
         </question>
 
         <answer>
           <para>§Aªº¨t²Î¤@©w´£°ª¤F securelevel¡A¹ï¤£¹ï¡H¦b¤@­Ó´£°ª¤F
             securelevel ªº¨t²Î¤W¡A¬Oµ´¹ïµLªk°_°Ê X ªº¡C·Qª¾¹D¬°¤°»ò¡A
             ½Ð°Ñ¦Ò &man.init.8; »¡©ú¤å¥ó¡C</para>
 
           <para>©Ò¥H³o­Ó°ÝÃDÅܦ¨¡G§AÁÙ¯à«ç»ò¿ì¡C°ò¥»¤W§A¦³¨âºØ¿ï¾Ü¡G
             ±N§Aªº securelevel ³]¦^¹s (³q±`¦b <filename>/etc/rc.conf
             </filename> ¸Ì­±³]©w)¡A©Î¬O¦b±Ò°Ê®É°õ¦æ &man.xdm.1; (¦b
             securelevel ³Qª@°ª«e)¡C</para>
 
           <para>½Ð°Ñ¦Ò <xref linkend="xdm-boot"> ¥H¨ú±o§ó¦h¦³Ãö±Ò°Ê®É
             °õ¦æ &man.xdm.1; ªº¸ê°T¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="x-and-moused">
           <para>¬°¤°»ò§Ú¤£¯à¦b X ¸Ì¨Ï¥Î·Æ¹«¡H</para>
         </question>
 
         <answer>
           <para>¦pªG±z¥Îªº¬O syscons (¤º©wªº console ÅX°Êµ{¦¡) ªº¸Ü¡A±z¥i¥H
             ¸g¥Ñ³]©w FreeBSD ¨ÓÅý¥¦¤ä´©¦b¨C­Ó virtual console ¨Ï¥Î·Æ¹«¡C¬°¤F
             ÁקK©M X ²£¥Í½Ä¬ð¡Asyscons ¨Ï¥Î¤F¤@­Ó¥s°µ
             <devicename>/dev/sysmouse</devicename> ªºµêÀÀ¸Ë¸m¡C©Ò¦³·Æ¹«²£¥Íªº
             event ³£·|§Q¥Î moused ¨Ó¼g¨ì sysmouse ³o­Ó¸Ë¸m¡C¦pªG±z§Æ±æ¦b¤@­Ó
             ©Î¥H¤Wªº virtual console ¤W¨Ï¥Î·Æ¹«¡A<emphasis>¨Ã¥B</emphasis>
             ¯à°÷¨Ï¥Î X ªº¸Ü¡A½Ð°Ñ¦Ò
             <xref linkend="moused" remap="another section"> ¨Ã¥B³]©w¦n
             moused¡C</para>
 
           <para>µM«á½s¿è <filename>/etc/XF86Config</filename> ³o­ÓÀɮסA
             ¨Ã¥B½T»{§A¦³¥H¤U³o´X¦æªº³]©w¡C</para>
 
           <programlisting>Section         Pointer
 Protocol        "SysMouse"
 Device          "/dev/sysmouse"
 ....</programlisting>
 
           <para>¥H¤Wªº¨Ò¤l¡A¾A¥Î©ó XFree86 3.3.2 ¤Î¨ä«áªºª©¥»¡C¥Î©ó§ó¦­ªº
             ª©¥»ªº¡A¨ä <emphasis>Protocol</emphasis> À³¬°
             <emphasis>MouseSystems</emphasis>¡C</para>
 
           <para>¦³¨Ç¤H¤ñ¸û³ßÅw¦b³]©w X ªº®É­Ô¥Î
             <devicename>/dev/mouse</devicename> ³o­Ó¸Ë¸m¡C¦pªG±z­nÅý¥¦¯à°÷
             ¥¿±`¤u§@ªº¸Ü¡A±z´N¥²¶·§â <devicename>/dev/mouse</devicename>
             ³sµ²¨ì <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>§Úªº·Æ¹«¦³­Ó«Ü¬¯ªººu½ü¡C§Ú¯à¦b X ¸Ì­±¨Ï¥Î¶Ü¡H</para>
         </question>
 
         <answer>
           <para>¥i¥H¡C¤£¹L§A»Ý­n³]©w X ¥Î¤áºÝµ{¦¡¡C ½Ð°Ñ¦Ò <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>¦pªG§A­n¨Ï¥Î <application>imwheel</application> µ{¦¡¡A
             ¥u­n¸òµÛ¤U¦C¨BÆJ§@§Y¥i¡C</para>
 
           <orderedlist>
             <listitem>
               <para>Âà´«ºu½ü event
 Translate the Wheel Events</para>
 
               <para><application>imwheel</application> µ{¦¡ªº¹B§@­ì²z¡A
                 ¬O±N·Æ¹«ªº²Ä¥|Áä»P²Ä¤­ÁäÂà´«¦¨«öÁä event¡C¦]¬°¦p¦¹¡A©Ò¥H
                 §A¥²¶·Åý·Æ¹«ÅX°Êµ{¦¡±N·Æ½ü¨Æ¥óÂà´«¦¨²Ä¥|Áä»P²Ä¤­Áä event¡C
                 ¦³¨âºØ¤èªk¥i¥H¹F¨ì¥Øªº¡A¤@¬OÅý &man.moused.8; §@Âà´«¡A¤G¬O
                 Åý X ¥»¨­¥h§@ event Âà´«¡C</para>
 
               <orderedlist>
                 <listitem>
                   <para>¨Ï¥Î &man.moused.8; ¨ÓÂà´«ºu½ü Event</para>
 
                   <para>­nÅý &man.moused.8; ¨Ó§@ event Âà´«¡A¥u­n¦b
                     °õ¦æ &man.moused.8; ªº©R¥O¦C¤¤¥[¤W <option>-z 4</option>
                     §Y¥i¡CÁ|­Ó¨Ò¤l¡A¦pªG§A¤@¯ë³£¬O¥H
                     <command>moused -p /dev/psm0</command> ¨Ó°_°Ê
                     &man.moused.8; ªº¸Ü¡A¥u­n§ï¦¨ <command>moused -p
                     /dev/psm0 -z 4</command> §Y¥i¡C¦pªG§A¬O¦b¶}¾÷¹Lµ{¤¤§Q¥Î
                     <filename>/etc/rc.conf</filename> ¨Ó°_°Ê &man.moused.8;¡A
                     §A¥i¥H¦b <filename>/etc/rc.conf</filename> ¤¤±N
                     <varname>moused_flags</varname> ¤W¥[ <option>-z 4
                     </option> §Y¥i¡C</para>
 
                   <para>§A²{¦b»Ý­nÅý X ª¾¹D§Aªº·Æ¹«¦³¤­­Ó«öÁä¡A¥u­n¦b
                     <filename>/etc/XF86Config</filename> ¤¤ªº
                     <quote>Pointer</quote> °Ï¶ô¤¤¥[¤W
                     <literal>Buttons 5</literal> ³o¤@¦æ§Y¥i¡C¨Ò¦p¡A
                     §A¥i¯à¦b <filename>/etc/XF86Config</filename> ¤¤¦³
                     ¥H¤Uªº <quote>Pointer</quote> °Ï¶ô¡G</para>
 
                   <example>
 
                     <title>¦b XFree86 3.3.x ¨t¦Cªº XF86Config ³]©wÀɪº 
                       <quote>Pointer</quote> °Ï¶ô¤¤¡A¥H moused §@Âà´«
                       ªººu½ü¹«ªº³]©w½d¨Ò</title>
                       
                     <programlisting>Section "Pointer"
    Protocol        "SysMouse"
    Device          "/dev/sysmouse"
    Buttons         5
 EndSection</programlisting>
                   </example>
 
                   <example>
                     <title>¦b XFree86 4.x ¨t¦Cªº XF86Config ³]©wÀɪº 
                       <quote>InputDevice</quote> °Ï¶ô¤¤¡A¥H X Server §@Âà´«
                       ªººu½ü¹«ªº³]©w½d¨Ò</title>
 
                     <programlisting>Section "InputDevice"
    Identifier      "Mouse1"
    Driver          "mouse"
    Option          "Protocol" "auto"
    Option          "Device" "/dev/sysmouse"
    Option          "Buttons" "5"
 EndSection</programlisting>
                   </example>
 
                   <example>
                     <title>¦b <quote>.emacs</quote> ¤¤¡A³]©wºu½ü¹«ªº­ì¥Í
                       ­¶­±ºu°Ê¤ä´©½d¨Ò</title>
                     <programlisting>;; wheel mouse
 (global-set-key [mouse-4] 'scroll-down)
 (global-set-key [mouse-5] 'scroll-up)</programlisting>
                   </example>
 
                 </listitem>
 
                 <listitem>
                   <para>§Q¥Î§Aªº X Server ¨Ó§@ºu½ü Event Âà´«</para>
 
                   <para>¦pªG§A¨S¦³°õ¦æ &man.moused.8;¡A©Î¬O§A¤£·Q§Q¥Î
                     &man.moused.8; ¥h§@ºu½ü event Âà´«¡A§A¥i¥H§ï¥Î
                     X server ¨Ó§@³o¼Ëªº event Âà´«¡C§A±o¦b <filename>
                     /etc/XF86Config</filename> Àɮפ¤§@´X­Ó§ó°Ê¡C²Ä¤@¡A
                     §A­n¬°§Aªº·Æ¹«¿ï¾Ü¾A·íªº³q°T¨ó©w¡C¤j¦h¼Æªººu½ü¹«³£
                     ¨Ï¥Î <quote>IntelliMouse</quote> ¨ó©w¡A¤£¹L XFree86
                     ¤]¤ä´©¨ä¥¦ªº³q°T¨ó©w¡A¨Ò¦pù§Þªº MouseMan+ ·Æ¹«©Ò¥Îªº
                     <quote>MouseManPlusPS/2</quote>¡C·í§A¿ï¦n¤§«á¡A¥u­n
                     ¥[¶i¤@¦æ <quote>Pointer</quote> °Ï¶ôªº <varname>
                     Protocol</varname> ÅܼƧY¥i¡C</para>
 
                   <para>²Ä¤G¡A§A­n§i¶D X server ±N±²°Ê¨Æ¥ó­«·s¹ï¬M¦Ü·Æ¹«ªº
                     ²Ä¥|©M²Ä¤­Áä¡C³o¥i¥H§Q¥Î <varname>ZAxisMapping</varname>
                     ¿ï¶µ¿ì¨ì¡C</para>
 
                   <para>Á|­Ó¨Ò¤l¡A¦pªG§A¨S¦³¨Ï¥Î &man.moused.8;¡A¦Ó§A¦³¤@­Ó
                     IntelliMouse ¦w¸Ë¦b PS/2 ·Æ¹«°ðªº¸Ü¡A§A¥i¥H¦b
                     <filename>/etc/XF86Config</filename> ¸Ì¨Ï¥Î¥H¤Uªº³]©w¡C
                   </para>
 
                   <example>
                     <title>¦b XF86Config ³]©wÀɪº <quote>Pointer</quote>
                       °Ï¶ô¤¤¡A¥H X Server §@Âà´«ªººu½ü¹«ªº³]©w½d¨Ò</title>
 
                     <programlisting>Section "Pointer"
    Protocol        "IntelliMouse"
    Device          "/dev/psm0"
    ZAxisMapping    4 5
 EndSection</programlisting>
                   </example>
 
                   <example>
                     <title>¦b XFree86 4.x ¨t¦Cªº XF86Config ³]©wÀɪº 
                       <quote>InputDevice</quote> °Ï¶ô¤¤¡A¥H X Server §@Âà´«
                       ªººu½ü¹«ªº³]©w½d¨Ò</title>
 
                     <programlisting>Section "InputDevice"
    Identifier      "Mouse1"
    Driver          "mouse"
    Option          "Protocol" "auto"
    Option          "Device" "/dev/psm0"
    Option          "ZAxisMapping" "4 5"
 EndSection</programlisting>
                   </example>
 
                   <example>
                     <title>¦b <quote>.emacs</quote> ¤¤¡A³]©wºu½ü¹«ªº­ì¥Í
                       ­¶­±ºu°Ê¤ä´©½d¨Ò</title>
                     <programlisting>;; wheel mouse
 (global-set-key [mouse-4] 'scroll-down)
 (global-set-key [mouse-5] 'scroll-up)</programlisting>
                   </example>
 
                 </listitem>
               </orderedlist>
             </listitem>
 
             <listitem>
               <para>¦w¸Ë <application>imwheel</application></para>
 
               <para>±µ¤U¨Ó¡A±q Ports ¸Ì¦w¸Ë <application>imwheel
                 </application>¡C¦b x11 Ãþ§O¸Ì¥i¥H§ä¨ì¥¦¡A¥¦¥i¥H±N
                 ºu½ü event ¹ï¬M¨ìÁä½L event¡CÁ|­Ó¨Ò¤l¡A¥¦¥i¥H¦b§A
                 ±Nºu½ü©¹«e±À®É¡A°e¥X¤@­Ó <keycap>Page Up</keycap>
                 ¨ì§AªºÀ³¥Îµ{¦¡¥h¡C<application>Imwheel</application>
                 §Q¥Î¤@­Ó³]©wÀÉ¡A¥H«K¹ïÀ³ºu½ü event ¦ÜÁä½L event¡A³o¼Ë
                 ¥¦´N¥i¥H¦b¤£¦PªºÀ³¥Îµ{¦¡¤¤¡A°e¥X¤£¦PªºÁä½L«öÁä¡C¹w³]ªº
                 <application>imwheel</application> ³]©wÀɬO¦b
                 <filename>/usr/X11R6/etc/imwheelrc</filename>¡A¦pªG§A·Q
                 ½s¿è¦Û­qªº³]©wÀɪº¸Ü¡A¥i¥H±N¥¦½Æ»s¨ì
                 <filename>~/.imwheelrc</filename>¡AµM«á¨Ì§Aªº»Ý­n­×§ï¥¦¡C
                 ³]©wÀɪº®æ¦¡¦b &man.imwheel.1; ¸Ì­±¦³¸Ô²Óªº»¡©ú¡C</para>
             </listitem>
 
             <listitem>
               <para>³]©w <application>Emacs</application> »P
                 <application>Imwheel</application> ¨ó¦P¤u§@
                 (<emphasis>¿ï¾Ü©Ê</emphasis>)</para>
 
               <para>¦pªG§A¨Ï¥Î <application>emacs</application> ©Î¬O
                 <application>Xemacs</application> ªº¸Ü¡A¨º§A»Ý­n¦b§Aªº
                 <filename>~/.emacs</filename> Àɮ׸̥[¤W¤@¤p¬q³]©w¡C
                 <application>emacs</application> ½Ð¥[¤W³o¤@¬q¡G</para>
 
               <example>
                 <title><application>Imwheel</application> ªº
                 <application>Emacs</application> ³]©w</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> «h¦b
                 <filename>~/.emacs</filename> Àɸ̥[¤W³o¤@¬q¡G</para>
 
               <example>
                 <title><application>Imwheel</application> ªº
                 <application>Xemacs</application> ³]©w</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>¦w¸Ë¤§«á¡A§A¥i¥Hª½±µ¦b xterm ¸ÌÁä¤J <command>imwheel
                 </command> ©R¥O¥H°_°Ê¥¦¡C¥¦·|¥H­I´º°õ¦æ¡A¨Ã¥B°¨¤Wµo´§®Ä¥Î¡C
                 ¦pªG§A½T©w­nª½±µ¨Ï¥Î <application>imwheel</application>¡A
                 ¥u­n§â¥¦¥[¶i§A¦Û¤vªº <filename>.xinitrc</filename> ©Î
                 <filename>.xsession</filename> ¤ºÀɮקY¥i¡C§A¥i¥H¤£ºÞ
                 <application>imwheel</application> ©Ò°e¥X¨Ó¦³Ãö PID ÀÉ®×
                 ĵ§i¡C¨º¨Çĵ§i¥u¹ï Linux ª©ªº <application>imwheel
                 </application> ¦³®Ä¦Ó¤w¡C</para>
             </listitem>
           </orderedlist>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="window-menu-weird">
           <para>¬°¤°»ò X Window ªº¿ï³æ©M¹ï¸Ü®Ø¤£¯à¥¿±`¹B§@¡H</para>
         </question>
 
         <answer>
           <para>§â Num Lock Ãö±¼¸Õ¸Õ¡C</para>
 
           <para>¦pªG±zªº Num Lock ¦b¶}¾÷®Éªº¹w³]­È¬O¶}µÛªº¸Ü¡A±z¥²¶·§â¤U¦C
             ³o¦æ©ñ¨ì <filename>XF86Config</filename> ³]©wÀɤ¤ªº
             <literal>Keyboard</literal> ³¡¥÷¡C</para>
 
           <programlisting># Let the server do the NumLock processing.  This should only be
 # required when using pre-R6 clients
     ServerNumLock</programlisting>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="virtual-console">
           <para>¤°»ò¬O virtual console¡H§Ú­n«ç»ò°µ¤~¯à¥Î¦h¤@ÂI¡H</para>
         </question>
 
         <answer>
           <para>²³æ¨Ó»¡¡Avirtual console ´N¬O¥i¥HÅý±z¤£¥²°µ¤Ó¦h½ÆÂøªº³]©w
             ¦p¨Ï¥Îºô¸ô©Î°õ¦æ X ¡A¦Ó¦b¦P¤@»O¾÷¾¹¤W¦P®É°µ¦n´X¥ó¨Æªº¤èªk¡C</para>
 
           <para>·í±Ò°Ê¨t²Î¨ÃÅã¥Ü§¹©Ò¦³¶}¾÷°T®§¤§«á¡A±z´N·|¦b¿Ã¹õ¤W¬Ý¨ì¤@­Ó
              login ªº´£¥Ü²Å¸¹¡C¦b³o­Ó®É­Ô±z´N¥i¥H¿é¤J±zªº login name ¥H¤Î
              password ¡AµM«á´N¥i¥H¦b²Ä¤@­Ó virtual console ¤W¶}©l¤u§@¤F
              (©ÎªÌ¶}©lª±¡I) ¡C</para>
 
           <para>¦b¬Y¨Ç±¡ªp¤U¡A±z¥i¯à·|·Q­n§@¨ä¥Lªº¤u§@¡A¨Ò¦p»¡¬O¬Ý¬Ý±z¥¿¦b
             °õ¦æªºµ{¦¡ªº»¡©ú¤å¥ó¡A©Î¬O·í±z¦b FTP ¶Ç¿éªºµ¥«Ý®É¶¡¤¤¬Ý¬Ý±zªº
             ¶l¥ó¡C±z¥u»Ý­n«ö Alt-F2 («ö¦í Alt Á䤣©ñ¡A¨Ã«ö¤U F2 Áä) ¡AµM«á
             ±z´N·|¦b²Ä¤G­Ó <quote>virtual console</quote> ¤W¬Ý¨ì¤@­Ó login
             ´£¥Ü²Å¸¹¡I·í±z·Q­n¦^¨ì­ì¨Óªº¤u§@®É¡A½Ð«ö Alt-F1¡C</para>
 
           <para>FreeBSD ¦b¦w¸Ë®Éªº¹w³]­È¬O¨Ï¥Î¤T­Ó virtual console
             (3.3-RELEASE «á¬°¤K­Ó)¡A±z¥i¥H¥Î Alt-F1¡AAlt-F2¡A¥H¤Î Alt-F3
             ¦b¥¦­Ì¤§¶¡°µ¤Á´«¡C</para>
 
           <para>¦pªG±z·Q­n¦h¤@ÂI virtual console ªº¸Ü¡A±z¥u»Ý­n½s¿è
             <filename>/etc/ttys</filename> ³o­ÓÀÉ (½Ð°Ñ¦Ò &man.ttys.5;)¡A
             ¦b <quote>Virtual terminals</quote> ³o­Óµù¸Ñ«á­±¥[¤J
             <devicename>ttyv4</devicename> ¨ì <devicename>ttyvc</devicename>
             ªºÄæ¦ì¡G</para>
 
           <programlisting># Edit the existing entry for ttyv3 in /etc/ttys and change
 # "off" to "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>±z·Q¥Î´X­Ó´N³]´X­Ó¡C±z³]¶V¦h virtual terminal ¡A¥¦­Ì´N¥Î±¼
             ¶V¦h¨t²Î¸ê·½¡F¦pªG±z¥u¦³¤£¨ì 8MB ªº°O¾ÐÅ骺¸Ü¡A³o¼vÅT´N¤j¤F¡C
             ±z¥i¯à¤]·|·Q§â <literal>secure</literal> ´«¦¨
             <literal>insecure</literal>¡C</para>
 
             <important>
               <para>¦pªG±z·Q­n°õ¦æ X ªº¸Ü¡A±z <emphasis>¥²¶·</emphasis>
                 ¬°¥¦«O¯d (©ÎÃö±¼) ¦Ü¤Ö¤@­Ó virtual terminal ¡C³o´N¬O»¡¡A¦pªG
                 ±z·Q¦b«ö¤Q¤G­Ó Alt ¥\¯àÁä®É³£¦³ login ´£¥Ü²Å¸¹¡A¦Ó¥B¤S¦b¦P¤@
                 ³¡¹q¸£¤W¤]·Q°õ¦æ X ªº¸Ü¡A¨º»ò³o¯u¬O¤Ó¤£©¯¤F - ±z¥u¯à¥Î¤Q¤@­Ó¡C
               </para>
             </important>
 
           <para>¨ú®ø¤@­Ó console ³Ì²³æªº¤èªk´N¬O§â¥¦Ãö±¼¡CÁ|¨Ò¨Ó»¡¡A¦pªG
             ±z¹³¤W­±Á¿ªº¤@¼Ë³]©w¤F¥þ³¡ªº 12 ­Ó terminal ¨Ã¥B·Q­n°õ¦æ X ¡A
             ±z¥²»Ý§â virtual terminal 12 ±q¡G</para>
 
           <programlisting>ttyvb   "/usr/libexec/getty Pc"         cons25  on  secure</programlisting>
 
           <para>³]¦¨¡G</para>
 
           <programlisting>ttyvb   "/usr/libexec/getty Pc"         cons25  off secure</programlisting>
 
           <para>¦pªG±zªºÁä½L¥u¦³ 10 ­Ó¥\¯àÁ䪺¸Ü¡A±z´N­n§ï¦¨³o¼Ë¡G</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>(±z¤]¥i¥Hª½±µ§â³o´X¦æ¬å±¼¡C)</para>
 
           <para>¤@¥¹±z§ï¤F <filename>/etc/ttys</filename>¡A¤U¤@­Ó¨BÆJ´N¬O­n
             ½T©w±z¦³¨¬°÷ªº virtual terminal ¸Ë¸m¡C³Ì²³æªº¤èªk´N¬O¡G</para>
 
           <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>sh MAKEDEV vty12</userinput></screen>
 
           <para>¦A¹L¨Ó¡A·Q­n±Ò°Ê³o¨Ç virtual console ³Ì²³æ (¤]¬O³Ì°®²b)
             ªº°µªk´N¬O­«¶}¾÷¡CµM«á¡A¦pªG±z¤£·Q­«¶}¾÷ªº¸Ü¡A±z¥i¥H§â X Window
             Ãö±¼¡AµM«á¥Î <username>root</username> ªº¨­¥÷°õ¦æ¤U¦C«ü¥O¡G</para>
 
           <screen>&prompt.root; <userinput>kill -HUP 1</userinput></screen>
 
           <para>·í±z°õ¦æ³o­Ó©R¥O«e¡A±z¤@©w­n§¹¥þ§â X Window Ãö±¼¡C¦pªG
             ±z¤£³o»ò°µªº¸Ü¡A±zªº¨t²Î¥i¯à·|¦b±z°õ¦æ kill ©R¥O«á¥X²{·í±¼©Î
             Âꦺªº±¡ªp¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="vty-from-x">
           <para>§Ú­n«ç»ò±q X ¤Á´«¨ì virtual console¡H</para>
         </question>
 
         <answer>
           <para>½Ð¥Î <keycombo action="simul">
               <keycap>Ctrl</keycap>
               <keycap>Alt</keycap>
               <keycap>F<replaceable>n</replaceable></keycap>
             </keycombo> ¥H¤Á¦^¦Ü virtual console¡C
             <keycombo action="simul">
               <keycap>Ctrl</keycap>
               <keycap>Alt</keycap>
               <keycap>F1</keycap>
             </keycombo> ¥i¥H¤Á¦^¦Ü²Ä¤@­Ó virtual console¡C</para>
 
           <para>·í§A¤Á¦^¦Ü¤å¦r console «á¡A§A´N¥i¥H¨Ï¥Î¤@¯ë
             <keycombo action="simul">
               <keycap>Alt</keycap>
               <keycap>F<replaceable>n</replaceable></keycap>
             </keycombo> «öÁä²Õ¦X¡A¦b¦U console ¤§¶¡¤Á´«¡C</para>
 
           <para>­n¦^¨ì X ªº¸Ü¡A§A¥²¶·¤Á¦^¦Ü°õ¦æ X ªº virtual console¡C
             ¦pªG§A¬O±q©R¥O¦C¸Ì°_°Ê X ªº¸Ü (¨Ò¦p¨Ï¥Î <command>startx</command>
             «ü¥O)¡A¨º»ò X ·|¨Ìªþ¦b¤U¤@­Ó¥¼¨Ï¥Îªº virtual console¡A¦Ó¤£¬O¥¦³Q
             °_°Êªº¤å¦r console¡C¦pªG§A¦³¤K­Ó¨Ï¥Î¤¤ªº virtual terminal¡A¨º»ò
             X ´N·|¦b²Ä¤E­Ó¤W°õ¦æ¡A§A´N¥i¥H¨Ï¥Î
             <keycombo action="simul">
               <keycap>Alt</keycap>
               <keycap>F9</keycap>
             </keycombo> ¥Hªð¦^¦Ü X ¤¤¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="xdm-boot">
           <para>§Ú­n«ç»ò°µ¤~¯à¦b¶}¾÷®É±Ò°Ê XDM¡H</para>
         </question><answer>
 
           <para>¦³¨âºØ¤èªk¥i¥H±Ò°Ê <ulink
             URL="http://www.FreeBSD.org/cgi/man.cgi?manpath=xfree86&amp;query=xdm">
             xdm</ulink>¡C¤@ºØ¤èªk¬O±q <filename>/etc/ttys</filename> ¨Ó±Ò°Ê¡A
             ¥i¥H°Ñ¦Ò &man.ttys.5; »¡©ú¤å¥ó¤¤ªº½d¨Ò¡F¥t¤@ºØ¤èªk¬O¦b
             <filename>rc.local</filename> (½Ð°Ñ¦Ò &man.rc.8;) °õ¦æ xdm¡A©Î¬O
             ¦b <filename>/usr/local/etc/rc.d</filename> ©ñ¤@­Ó
             <filename>X.sh</filename>¡C³o¨âºØ¤èªk³£¬O¦Xªkªº¡A¦pªG±z¸Õ¬Y¤@ºØ
             ¤èªkµL®Äªº¸Ü¡A±z¥i¥H¸Õ¸Õ¥t¥~¤@ºØ¡C³o¨âºØ¤èªkªºµ²ªG¬O¤@¼Ëªº¡GX
             ·|Åã¥Ü¤@­Ó¹Ï§Î¤Æªº login: ´£¥Ü¡C</para>
 
           <para>¥Î ttys ªº¤èªkªºÀuÂI¡A¦b©ó«ü©ú¤F X ¦b±Ò°Ê®É¨ì©³¬O¥Î¨º­Ó vty¡A
             ¨Ã¥B±N logout ®É­«·s±Ò°Ê X server ªº³d¥ô¥áµ¹ init¡C rc.local
             ªº¤èªk«h¬O¦b·í±Ò°Ê X ¥X¤F°ÝÃD®É¡A¥i¥H«Ü»´ÃP¦a§â xdm ±þ±¼¨Ó¸Ñ¨M
             °ÝÃD¡C</para>
 
           <para>¦pªG¬O¥Î rc.local ªº¤èªk¡A¦b°õ¦æ <command>xdm</command>
             ®É±z¤£¯à¥[¥ô¦ó°Ñ¼Æ¡]¤]´N¬O¶]¦¨ daemon¡^¡C¥²¶·¦b getty °õ¦æ«á
             ¤~¯à±Ò°Ê xdm¡A§_«h getty ©M xdm ·|¤¬¬Û½Ä¬ð¦ÓÂê¦í console¡C³Ì¦nªº
             ¤è¦¡¬O¦b script ¤¤¥[­Ó sleep¡AÅý¥¦¼È°± 10 ¬íÄÁ¥ª¥k¡A±µµÛ¤~°õ¦æ
              xdm¡C</para>
 
           <para>¦pªG§A¬O±q <filename>/etc/ttys</filename> ±Ò°Ê
             <command>xdm</command>¡A<command>xdm</command> »P &man.getty.8;
             ¤´¦³¾÷·|¤¬¬Û½Ä¬ð¡C¤@­ÓÁקK¥¦ªº¤èªk¡A´N¬O¦b
             <filename>/usr/X11R6/lib/X11/xdm/Xservers</filename> Àɮפ¤¥[¤J
             <literal>vt</literal> ¼Æ¦r¡C</para>
 
           <programlisting>:0 local /usr/X11R6/bin/X vt4</programlisting>
 
           <para>¤W­±ªº¨Ò¤l¤¤¡A·|«ü¥Ü X server ¦b <devicename>/dev/ttyv3
             </devicename> ¤¤°õ¦æ¡C½Ðª`·N¼Æ¦r¬O®t¤@ªº¡CX server ±q¤@¶}©l¼Æ
             vty¡A¦Ó FreeBSD ®Ö¤ß«h¬O±q¹s¶}©l¼Æ vty ªº¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="xconsole-failure">
           <para>¬°¤°»ò·í§Ú°õ¦æ xconsole ®É¡Aµo¥Í¤F
             <errorname>Couldn't open console</errorname> ªº¿ù»~¡H</para>
         </question>
 
         <answer>
           <para>¦pªG§A¬O¥Î <command>startx</command> ¨Ó±Ò°Ê <command>startx
             </command> ªº¸Ü¡A<devicename>/dev/console</devicename> ªºÅv­­¨Ã
             <emphasis>¤£·|</emphasis> §ïÅÜ¡Aµ²ªG´N¬O <command>xterm -C
             </command> ©M <command>xconsole</command> ³oÃþªºµ{¦¡µLªk
             ¥¿±`°õ¦æ¡C</para>
 
           <para>³o¤@¤Áªº°ÝÃD¡A³£¬O¦]¬° console ªºÅv­­¬O±Ä¥Î¨t²Î¹w³]­È¡C
             ¦b¤@­Ó¦h¨Ï¥ÎªÌªº¨t²Î¸Ì¡A§Ú­Ì¤£§Æ±æ¨C­Ó¨Ï¥ÎªÌ³£¥i¥Hª½±µ¼g¤J¨t²Î
             console ¡C¦pªG¨Ï¥ÎªÌ¬O±q¾÷¾¹ªº VTY ª½±µ login ªº¸Ü¡A¨º»ò
             &man.fbtab.5; ¥i¥H¸Ñ¨M³oÃþªº°ÝÃD¡C</para>
 
           <para>²³æ¦a»¡¡A½Ð½T«O <filename>/etc/fbtab</filename> (½Ð°Ñ¦Ò
             &man.fbtab.5;) ³o­ÓÀɮפ¤ªº³o¤@¦æ¨S¦³³Qµù¸Ñ±¼¡G</para>
 
           <programlisting>/dev/ttyv0 0600 /dev/console</programlisting>
 
           <para>³o¤@¦æ³]©wªº¦s¦b¥i¥H½T«O±q <devicename>/dev/ttyv0</devicename>
             µn¤Jªº¨Ï¥ÎªÌ¥i¥H±±¨î console¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="xfree86-root">
           <para>¥H«e§Ú¥i¥H¥H¤@¯ë¨Ï¥ÎªÌ°õ¦æ XFree86¡A¬°¤°»ò²{¦b¥¦»¡§Ú¤@©w­n
             ¥H <username>root</username> ¤~¯à°õ¦æ¡H</para>
         </question>
 
         <answer>
           <para>©Ò¦³ªº X server ³£»Ý­n¥H <username>root</username> ¨Ó°õ¦æ¡A
             ¤~¯àª½±µ¦s¨ú§Aªºµø°TµwÅé¡Cª©¥»ªº XFree86 (&lt;= 3.3.6) ·|¦Û°Ê
             ±N©Òªþªº server ¥H§Q¥Î <username>root</username> ¨­¥÷°õ¦æªº¤è¦¡
             ¦w¸Ë°_¨Ó  (setuid ¬° <username>root</username>)¡C¥Ñ©ó X server
             ³£¬OÅé¿nÃe¤j¤S½ÆÂøªºµ{¦¡¡AÅã¦Ó©ö¨£¦a¡A³o¬O¤@­Ó¦w¥þ¤Wªº¨aÃø¡C
             ¦]¬°³o­Ó­ì¦]¡A·sª©ªº XFree86 ´N¤£±N³o¨Ç server ¥H setuid ¬°
             <username>root</username> ªº¤è¦¡¦w¸Ë¡C
 
           <para>«Ü©úÅã¦a¡A§Ú­Ì§¹¥þµLªk±µ¨ü±N X server ¥H
             <username>root</username> ªº¨­¥÷°õ¦æ¡C°_½X´N¦w¥þ¤W¤£¬O­Ó¦n¥D·N¡C
             ¦³¨âºØ¤èªk¥i¥H¥H¤@¯ë¨Ï¥ÎªÌªº¨­¥÷¨Ï¥Î X¡C²Ä¤@¬O§Q¥Î
             <command>xdm</command> ©Î¬O¨ä¥¦ªº display manager (¨Ò¦p
             <command>kdm</command>)¡F²Ä¤G¬O§Q¥Î <command>Xwrapper</command>¡C
           </para>
 
           <para><command>xdm</command> ¬O¤@­Ó³B²z¹Ï§Î¬É­±µn¤Jªº daemon¡C
             ¥¦³q±`¦b¶}¾÷®É°õ¦æ°_¨Ó¡A¦Ó¥B­t³d¹ï¨Ï¥ÎªÌ§@¨­¥÷»{ÃÒ¡A¥H¤Î°_°Ê
             ¨Ï¥ÎªÌªº¤u§@Àô¹Ò¡F¥¦¥i»¡¬O¹Ï§ÎÀô¹Ò¤Uªº &man.getty.8; »P
             &man.login.1; ªº¹ïÀ³µ{¦¡¡C·Q±oª¾§ó¦h¦³Ãö <command>xdm</command>
             ªº¸ê°T¡A½Ð°Ñ¦Ò <ulink url="http://www.xfree86.org/support.html">
             XFree86 ¤å¥ó</ulink>¡A¥H¤Î¨ä <link linkend="xdm-boot">FAQ
             ¶µ¥Ø</link>¡C</para>
 
           <para><command>Xwrapper</command> ¬O X server ªº¥]¸Ëµ{¦¡¡F¥¦¥i¥H
             Åý¤@¯ë¨Ï¥ÎªÌ¥i¥H¤â°Ê°_°Ê X server ªº¤p¤u¨ã¡A¦ÓÁÙ¯àºû«ù¤@©wªº¦w¥þ
             Àô¹Ò¡C¥¦·|Àˬd¶Ç¤Jªº©R¥O¦C°Ñ¼Æ¡A¦pªG¨S°ÝÃDªº¸Ü¡A´N°_°Ê¾A·íªº
             X server¡C¦pªG§A¦]¬°¬YºØ²z¥Ñ¦Ó¤£·Q°õ¦æ display manager ªº¸Ü¡A
             ¥¦¬O¬°§A¦Ó³]©wªº¡C¦pªG§A¦w¸Ë¤F§¹¾ãªº ports¡A§A¥i¥H¦b
             <filename>/usr/ports/x11/wrapper</filename> ¤¤§ä¨ì¥¦¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ps2-x">
           <para>§Úªº PS/2 ·Æ¹«¦b X ¤¤¦³ÂI¤£¥¿±`¡H</para>
         </question>
 
         <answer>
           <para>±zªº·Æ¹«©M±zªº·Æ¹«ÅX°Êµ{¦¡¥i¯à¦s¦b¦³¤£¦P¨Bªº²{¶H¡C</para>
 
           <para>¦b 2.2.5 ¥H¤Î§ó¦­ªº¨t²Î¸Ì¡A±q X ¤Á¨ì virtual terminal µM«á
             ¦A¤Á¦^¨Ó´N¥i¥H¨Ï¥¦­Ì­«·s°µ¦P¨Bªº°Ê§@¡C¦pªG³o­Ó°ÝÃD±`±`µo¥Íªº¸Ü¡A
             ±z¥i¥H¦b±zªº®Ö¤ß³]©wÀɤ¤¥[¤J¤U­±³o­Ó¿ï¶µµM«á­«·s½sĶ¡G</para>
 
           <programlisting>options PSM_CHECKSYNC</programlisting>
 
           <para>¦pªG±z¨S¦³«Ø¥ß®Ö¤ßµ{¦¡ªº¸gÅç¡A½Ð¬Ý
              <link linkend="make-kernel">¦Û­q®Ö¤ß</link> ³o¤@¸`¡C</para>
 
           <para>¥[¤W³o­Ó¿ï¶µ¥H«á¡A·Æ¹«©M·Æ¹«ÅX°Êµ{¦¡¶¡ªº¦P¨B°ÝÃDÀ³¸Ó´N¤ñ¸û
             ¤£·|¥X²{¤F¡C¦pªG³o­Ó°ÝÃD¤´µM¦s¦bªº¸Ü¡A¦b²¾°Ê·Æ¹«®É«ö«ö·Æ¹««öÁä
             ¥i¥H¨Ï·Æ¹«©M·Æ¹«ÅX°Êµ{¦¡­«·s°µ¦P¨Bªº°Ê§@¡C</para>
 
           <para>¸Óª`·Nªº¬O³o­Ó¿ï¶µ¨Ã¤£¬O¹ï¨C¤@­Ó¨t²Î³£¦³®Ä¡A¥¦¥i¯à·|Åý±µ¦b
              PS/2 ·Æ¹«¦ì¸mªº ALPS GlidePoint ¸Ë¸m¥¢¥h <quote>tap</quote>
              ³o¶µ¥\¯à¡C</para>
 
           <para>¦b 2.2.6 ¤Î¨ä«áªºª©¥»¡A¦P¨Bªº½T»{¤w¸g¦³¤F¸û¦nªº¸Ñ¨M¿ìªk¡A
             ¦Ó¥B³o¨Ç³£¤w¸g¬O PS/2 ·Æ¹«ÅX°Êµ{¦¡ªº¼Ð·Ç¤F¡C³o­Ó¤èªk¤]¥i¥H¦b
             GlidePoint ¤W¥¿±`¤u§@¡C (¦]¬°½T»{ªºµ{¦¡½X¤w¸g¦¨¬°¤@­Ó¼Ð·Ç¥\¯à¡A
             ©Ò¥H¦b³o¨Çª©¥»¤¤§Ú­Ì¤£¦b´£¨Ñ PSM_CHECKSYNC ªº¿ï¶µ¤F¡C) ¤£¹L¦b
             ·¥¤Ö¼Æªº®×¨Ò¤¤¡A³o¨ÇÅX°Êµ{¦¡·|»~³ø¦P¨B©Ê¿ù»~¡AµM«á±z´N·|¬Ý¨ì
             ³o¼Ëªº®Ö¤ß°T®§¡G</para>
 
           <programlisting>psmintr: out of sync (xxxx != yyyy)</programlisting>
 
           <para>µM«á±z´N·|µo²{±zªº·Æ¹«¤£¯à¥¿±`¹B§@¤F¡C</para>
 
           <para>¦pªG±zµo¥Í¤F³o¼Ëªºª¬ªp¡A±z¥²¶·Âǥѧâ PS/2 ·Æ¹«ÅX°Êµ{¦¡ªº flag
             ³]¦¨ 0x100 ¨Ó§â¦P¨B½T»{ªºµ{¦¡½Xµ¹¨ú®ø±¼¡CµM«á¦b¶}¾÷´£¥Ü²Å¸¹®É¥Î
             <option>-c</option> ¿ï¶µ¨Ó¶i¤J <emphasis>UserConfig</emphasis>¡G
           </para>
 
           <screen>boot: <userinput>-c</userinput></screen>
 
           <para>µM«á¡A¦b <emphasis>UserConfig</emphasis> ©R¥O¦C¤¤Áä¤J¡G</para>
 
           <screen>UserConfig&gt; <userinput>flags psm0 0x100</userinput>
 UserConfig&gt; <userinput>quit</userinput></screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ps2-mousesystems">
           <para>§Úªº PS/2 ·Æ¹«¤£¯à³z¹L MouseSystem ¨Ó¹B§@¡H</para>
         </question>
 
         <answer>
           <para>¦³¤@¨Ç³ø§i«ü¥X¬Y¨Ç¼tµPªº PS/2 ·Æ¹«¥u¯à¦b
             <quote>°ª¸ÑªR«×</quote> ª¬ºA¤U¤~¯à¹B§@¡C¦pªG¤£¬Oªº¸Ü¡A·Æ¹«´å¼Ð
             ·|±`±`¶]¨ì¿Ã¹õªº¥ª¤W¨¤¥h¡C</para>
 
           <para>«D±`¤£©¯ªº¡A³o­Ó°ÝÃD¦b 2.0.X ©M 2.1.X ¤U¬OµL¸Ñªº¡C¦b 2.2
             ¨ì 2.2.5 ª©¡A±z¥i¥H¹ï <filename>/sys/i386/isa/psm.c</filename>
             ¨Ï¥Î¤U¦C patch µM«á­««Ø±zªº®Ö¤ß¡C¦pªG±z¨S¦³«Ø¥ß®Ö¤ßµ{¦¡ªº¸gÅç¡A
             ½Ð¬Ý <link linkend="make-kernel">¦Û­q®Ö¤ß</link> ³o¸`¡C</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>¦b 2.2.6 ¤Î¥H«áªºª©¥»¡A¦b PS/2 ·Æ¹«ÅX°Êµ{¦¡¤¤³]©w 0x04 ªº
              flag ·|§â·Æ¹«³]¦¨°ª¸ÑªR«×¼Ò¦¡¡C¦b¶}¾÷´£¥Ü²Å¸¹®É¥Î
              <option>-c</option> ¿ï¶µ¨Ó¶i¤J <emphasis>UserConfig</emphasis>¡G
           </para>
 
           <screen>boot: <userinput>-c</userinput></screen>
 
           <para>µM«á¡A¦b <emphasis>UserConfig</emphasis> ªº©R¥O¦C¤¤Áä¤J¡G
             </para>
 
           <screen>UserConfig&gt; <userinput>flags psm0 0x04</userinput>
 UserConfig&gt; <userinput>quit</userinput></screen>
 
           <para>«e¤@¸`¦³´£¨ì¥t¤@­Ó¥i¯à¾É­P·Æ¹«°ÝÃDªº­ì¦]¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="imake-tmpl">
           <para>·í§Ú«Ø¥ß X µ{¦¡®É¡A<command>imake</command> »¡¥¦§ä¤£¨ì
             <filename>Imake.tmpl</filename>¡C¥¦¦b­þ¨à¡H</para>
         </question>
 
         <answer>
 
           <para><filename>Imake.tmpl</filename> ¬O Imake ®M¥óªº¤@³¡¥÷¡AImake
             ¬O¼Ð·Çªº«Ø¥ß X µ{¦¡ªº¤u¨ã¡C <filename>Imake.tmpl</filename>
             ©M¨ä¥L¼Æ­Ó header file ¤@¼Ë¬O«Ø¥ß X µ{¦¡ªº¥²­nÀɮסA±z¥i¥H¦b
             X prog distribution ¤¤§ä¨ì¥¦­Ì¡C±z¥i¥H¥Î sysinstall ¨Ó¦w¸Ë©Î¬O
             ª½±µ±q X distribution ¤¤¤â°Ê¦w¸Ë¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="xfree86-version">
           <para>§Ú¦b build ¤@­Ó X À³¥Îµ{¦¡¡A¥¦»Ý­n XFree86 3.3.x¡A¦ý¬O
             §Ú¤w¸g¦w¸Ë XFree86 4.x ¤F¡C§Ú¸Ó«ç»ò¿ì¡H</para>
         </question>
 
         <answer>
           <para>­n§i¶D port ¦b½sĶµ{¦¡®É¡A¨Ï¥Î XFree86 4.x ¨ç¦¡®w¡A§A¥i¥H
             ¦b <filename>/etc/make.conf</filename> ¸Ì (¦pªG§A¨S¦³³o­ÓÀÉ¡A
             ½Ð«Ø¥ß¥¦) ¥[¤W¤U­±³o¤@¦æ¡G</para>
 
 	  <programlisting>XFREE86_VERSION=        4</programlisting>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="mouse-button-reverse">
           <para>§Ú­n«ç»ò°µ¤~¯à³]©w¥ªºJ¤l¥Îªº·Æ¹«¡H</para>
         </question>
 
         <answer>
           <para>¦b±zªº <filename>.xinitrc</filename> ©Î¬O
             <filename>.xsession</filename> ¤¤°õ¦æ
             <literal>xmodmap -e "pointer = 3 2 1"</literal> ªº«ü¥O¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="install-splash">
           <para>­n¦p¦ó¦w¸Ë splash ¹Ï§ÎÅã¥Üµ{¦¡¡H¨º¸Ì¥i¥H§ä±o¨ì©O¡H</para>
         </question>
 
         <answer>
 
           <para>´N¦bµo¦æ FreeBSD 3.1 ¤§«e¡A§Ú­Ì¥[¶i¤F¦b¶}¾÷®ÉÅã¥Ü
             <quote>splash</quote> ¹Ï§Îªº·s¥\¯à¡C¥Ø«e¥Î¨ÓÅã¥Ü¦b¿Ã¹õ¤WªºÀÉ®×
             ¥²¶·¬O 256 ¦âªºÂI¯x°}¹Ï§Î (<filename>*.BMP</filename>) ©Î ZSoft
             PCX(<filename>*.PCX</filename>) ªº®æ¦¡¡C°£¦¹¤§¥~¡A¸ÑªR«×¤]¥²¶·¦b
             320x200 ¥H¤U¡A¤~¯à©M¼Ð·Ç VGA Åã¥Ü¥d·f°t¨Ï¥Î¡C¦pªG±z½sĶ kernel
             ®É¦³¥[¤J VESA ¤ä´©¡A¨º»ò³Ì¤j¸ÑªR«×¥i¥H¨ì 1024x768¡Cª`·N VESA ªº
             ¤ä´©»Ý­n¥[¤J <literal>VM86</literal> ³o­Ó kernel ¿ï¶µ¡CVESA
             ¤ä´©¹ê»Ú¤W¥i¥H¦b½sĶ kernel ®É¥[¤J <literal>VESA</literal> ¿ï¶µ¡B
             ©Î¸ü¤J VESA ªº kld module ¨Ó¹F¦¨¡C</para>
 
           <para>±z­n­×§ï±±¨î FreeBSD ¶}¾÷¨BÆJªº³]©wÀÉ¡A¤~¯à¨Ï¥Î splash
             Åã¥Ü¹Ï§Îªº¥\¯à¡C³]©wÀɦbµo¦æ FreeBSD 3.2 «e¦³¨Ç§ó°Ê¡A©Ò¥H²{¦b
             ¦³¨â­Ó¤èªk¥i¥H¸ü¤J splash ªº¥\¯à¡G</para>
 
             <itemizedlist>
               <listitem>
                 <para>FreeBSD 3.1</para>
 
                 <para>¥ý¿ï¥X¥Î¨ÓÅã¥Ü¦b¿Ã¹õ¤Wªº¹Ï§Î¡A3.1 ª©¥u¤ä´© Windows
                   ªºÂI¯x°}®æ¦¡¡C¿ï¦n¤F±z­nªº¹ÏÀÉ«á¡A±N¥¦«þ¨ì <filename>
                   /boot/splash.bmp</filename>¡C±µµÛ§â¤U­±´X¦æ¥[¤J
                   <filename>/boot/loader.rc</filename> ¤¤¡G</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>°£¤F¥[¤J¹ï PCX Àɮתº¤ä´©¥~¡AFreeBSD 3.2 ¤]§ï¶i¤F
                   ¶}¾÷µ{§Çªº³]©w¤è¦¡¡C¦pªG±zÄ@·Nªº¸Ü¡A¥i¥H¥Î¤W­z FreeBSD 3.1
                   ªº¤èªk¡A±N <literal>splash_bmp</literal> ´«¦¨
                   <literal>splash_pcx</literal> ¨Ó¸ü¤J PCX ÀɮקY¥i¡C
                   ¦pªG·Q¥Î·sªº³]©w¤è¦¡¡A±zªº <filename>/boot/loader.rc
                   </filename> ¥²¶·¥]¬A³o´X¦æ¡G</para>
 
                 <programlisting>include /boot/loader.4th
 start</programlisting>
 
                 <para>Áٻݭn¤@­Ó¥]§t¥H¤U´X¦æªº <filename>/boot/loader.conf
                   </filename>¡G</para>
 
                 <programlisting>splash_bmp_load="YES"
 bitmap_load="YES"</programlisting>
 
                 <para>³o¬O°²³]±z¥Î <filename>/boot/splash.bmp</filename>
                   ¨Ó·í§@ splash ªº¿Ã¹õÅã¥Ü¡C¦pªG·Q¥Î PCX ªºÀɮסA§â¥¦«þ¦¨
                   <filename>/boot/splash.pcx</filename>¡A¦p¤W­z°µ¥X
                   <filename>/boot/loader.rc</filename>¡A¦A±N³o´X¦æ¥[¨ì
                   <filename>/boot/loader.conf</filename> ¤¤¡G</para>
 
                 <programlisting>splash_pcx_load="YES"
 bitmap_load="YES"
 bitmap_name="/boot/splash.pcx"</programlisting>
 
               </listitem>
             </itemizedlist>
 
           <para>²{¦b´N¥u³Ñ¤U splash ¥Î¨ÓÅã¥Üªº¹ÏÀÉ¡A±z¥i¥H¦b
             <ulink URL="http://www.baldwin.cx/splash/">http://www.baldwin.cx/splash/</ulink> §ä¨ì¦UºØ¼Ë«~¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="windows-keys">
           <para>§Ú¯à¦b X ¸Ì¨Ï¥ÎÁä½L¤Wªº <trademark class="registered">Windows
             </trademark> ¶Ü¡H</para>
         </question>
 
         <answer>
           <para>¥i¥H¡C§A©Ò­n§@ªº¡A´N¬O§Q¥Î &man.xmodmap.1; ¥h©w¸q§A·Q¨Ï¥Î
             ªº¥\¯à¡C</para>
 
           <para>°²³]©Ò¦³ªº <quote><trademark class="registered">Windows</trademark></quote> ³£¬O¼Ð·Çªº¡A
             ¨º¥¦­Ìªº keycode ¤À§O¬°¡G</para>
 
           <itemizedlist>
             <listitem>
               <para>115 - <trademark class="registered">Windows</trademark> Áä¡A
 		¦b¥ª¤âªº Ctrl »P Alt Á䤧¶¡</para>
             </listitem>
 
             <listitem>
               <para>116 - <trademark class="registered">Windows</trademark> Áä¡A
 		¦b Alt-Gr Áä¥kÃä</para>
             </listitem>
 
             <listitem>
               <para>117 - ¿ï³æÁä¡A¥k¤âªº Ctrl Á䥪Ãä</para>
             </listitem>
           </itemizedlist>
 
           <para>­nÅý¥ªÃ䪺 <trademark class="registered">Windows</trademark>
             Áä¦L¥X¤@­Ó³rÂI¡A¸Õ¸Õ³o­Ó¡G</para>
 
           <screen>&prompt.root; <userinput>xmodmap -e "keycode 115 = comma"</userinput></screen>
 
           <para>§A¥i¯à­n­«¶]§Aªº windows manager¡A¤~·|¦³°Ê§@¡C</para>
 
           <para>­nÅý <trademark class="registered">Windows</trademark> Áä
             ªº¹ï¬M¦b¨C¦¸ X °_°Ê®É¦Û°Ê³]©w¦n¡A§A¥i¥H¦b§Aªº
             <filename>~/.xinitrc</filename> ¸Ì¥[¤W <command>xmodmap</command>¡A
             ©Î¬O³Ì¦n«Ø¥ß¤@­Ó <filename>~/.xmodmaprc</filename> ÀɮסA¸Ì­±
             ¨C¤@¦æ´N¬O¤@­Ó <command>xmodmap</command> ªº¿ï¶µ¡AµM«á¦b§Aªº
             <filename>~/.xinitrc</filename> ¸Ì¥[¤W¡G</para>
 
 
           <programlisting>xmodmap $HOME/.xmodmaprc</programlisting>
 
           <para>³o¤@¦æ¡C</para>
 
 	  <para>¨Ò¦p¡A§A·Q­n±N³o¤T­ÓÁä¦U¹ï¬M¨ì F13¡BF14 ©M F15¡C³oÅý§A¯à
             ¦b§Aªºµ{¦¡©Î¬O window manager ¤º±N¨ä¹ïÀ³¨ì«K§Qªº¥\¯à¤W¡Aµ¥¤@¤U
             §Ú­Ì·|¥Ü½d¡C</para>
 
           <para>§â³o¨Ç©ñ¶i <filename>~/.xmodmaprc</filename> ¸Ì¡G</para>
 
           <programlisting>keycode 115 = F13
 keycode 116 = F14
 keycode 117 = F15</programlisting>
 
 	  <para>°²¦p§A¥Î <command>fvwm2</command> ªº¸Ü¡A§A¥i¥H§@³o¼Ëªº¹ï¬M¡A
             Åý F13 ¯à°÷Åý´å¼Ð©Ò¦bªºµøµ¡ÁY¦¨¤p¹Ï¥Ü (©Î¬O¤Ï¹L¨Ó)¡CF14 Åý´å¼Ð
             ©Ò¦bªºµøµ¡Åܦ¨³Ì¤W¼hªºµøµ¡¡A©Î¬O°h¨ì¤U¼h¥h (¦pªG¥¦¤w¸g¬O³Ì¤W¼h
             ¤Fªº¸Ü)¡CF15 «h±N Workplace (application) ¿ï³æ¥s¥X¨Ó¡A§Y¨Ï´å¼Ð
             ¤£¦b®à­±¤W¡C·í§A¨S¦³¥i¨£ªº®à­±°Ï°ì®É¡A³o­Ó¥\¯à´N¬Û·í¦a¤è«K (¦Ó¥B
             «öÁä¤Wªº¹Ï®×©M³o­Ó¥\¯à¬Û§k¦X)¡C</para>
 
 	  <para>¥H¤Uªº <filename>~/.fvwmrc</filename> ³]©w¥i§@¥X«e­zªº¥\¯à¡C
           </para>
 
           <programlisting>Key F13        FTIWS    A        Iconify
 Key F14        FTIWS    A        RaiseLower
 Key F15        A        A        Menu Workplace Nop</programlisting>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="x-3d-acceleration">
           <para>§Ú­n«ç»ò¼Ë¤~¯à±o¨ì OpenGL ªº 3D µwÅé¥[³t¥\¯à¡H</para>
         </question>
 
         <answer>
           <para>3D ¥[³t¥\¯àªº¦³µL¡Aµø§A©Ò¨Ï¥Îªº XFree86 ª©¥»»PÅã¥Ü´¹¤ù
             ªº«¬¸¹¦Ó©w¡C¦pªG§Aªº¬O NVIDIA ´¹¤ùªº¸Ü¡A½Ð¥h
             <ulink url="http://nvidia.netexplorer.org/">FreeBSD NVIDIA
             Driver Initiative </ulink> ºô­¶¬Ý¬Ý¡A¨º¸Ì¦³¦b XFree86-4 ¤W¨Ï¥Î
             NVIDIA ´¹¤ùªº 3D ¥[³t¥\¯àªº°Q½×¡CXFree86-4 ¤Wªº¨ä¥¦Åã¥Ü¥d¼tµP
             µwÅé¥[³t¥\¯àªº¸ê°T¡A ¥]¬A Matrox G200/G400, ATI Rage 128/Radeon,
             3dfx Voodoo 3, 4, 5, ¥H¤Î Banshee¡A¥i¦b <ulink
             url="http://gladstone.uoregon.edu/~eanholt/dri/">XFree86-4
             Direct Rendering on FreeBSD</ulink> ºô­¶¤W§ä¨ì¡CXFree 3.3 ªº
             ¨Ï¥ÎªÌ¥i¥H¨Ï¥Î Utah-GLX port¡A¥¦¥i¥H¦b
             <filename role="package">graphics/utah-glx</filename> §ä¨ì¡C
             ¨Ï¥Î¥¦¥i¥H¦b Matrox Gx00, ATI Rage Pro, SiS 6326, i810,
             Savage, ¥H¤Îªº NVIDIA ¤W±o¨ì¦³­­ªº OpenGL ¥[³t¡C</para>
           </answer>
         </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter id="networking">
     <chapterinfo>
       <author>
 	<firstname>Biing Jong</firstname>
 	<surname>Lin</surname>
 	<affiliation>
 	  <address><email>bjlin@stic.gov.tw</email></address>
         </affiliation>
       </author>
     </chapterinfo>
 
     <title>Networking</title>
 
     <qandaset>
       <qandaentry>
         <question id="diskless-booting">
           <para>§ÚÀ³¸Ó¨ì­þÃä§ä¦³ÃöµLºÏºÐ¶}¾÷
 	    <quote>diskless booting</quote> ªº¸ê®Æ¡H</para>
           </question>
 
           <answer>
             <para><quote>Diskless booting</quote> ´N¬OÅý FreeBSD ¥D¾÷±qºô¸ô
 	      ¤W¶}¾÷¡A¨Ã¥B±qºô¸ô¤Wªº server ¤WŪ¨ú¨ä¥L¥²­nªºÀɮסA¦Ó«D¥Ñ¥D¾÷
 	      ªºµwºÐ¤W¨ú±o³o¨ÇÀɮסC¸Ô²Óªº¸ê®Æ¥i¥H°Ñ¦Ò <ulink
 	      URL="../handbook/diskless.html"> FreeBSD ¤â¥UªºµLºÏºÐ¶}¾÷½g
 	      </ulink>¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="router">
           <para>FreeBSD ªº¥D¾÷¥i¥H·í§@¬Y­Óºô¸ô¤Wªº¸ô¥Ñ¾¹(router)¶Ü¡H</para>
         </question>
 
         <answer>
           <para>¬Oªº¡C½Ð°Ñ¦Ò FreeBSD ¤â¥Uªººô¸ô¶i¶¥½g <ulink
             url="../handbook/routing.html"> advanced
             networking</ulink>¡A¤×¨ä¬O¸ô¥Ñ»P¹h¹D¾¹ <ulink
             url="../handbook/routing.html#DEDICATED-ROUTER">routing
             and gateways</ulink>ªº³¡¤À¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="win95-connection">
           <para>§Ú¥i¥H³z¹L FreeBSD ±N§Úªº Win95 ¾÷¾¹³s¤W Internet ¶Ü¡H</para>
         </question>
 
         <answer>
           <para>°ò¥»¤W¡A·|°Ý³oºØ°ÝÃDªº¤H¦b®a¸Ì¦Ü¤Ö¦³¨â¥x¹q¸£¡A¤@¥x¶] FreeBSD
             ¥t¥~¤@¥x¶] Win95¡F³o­Ó·Qªk¬O±N FreeBSD ¥D¾÷³s¤W Internet¡AµM«á³z
 	    ¹L³o¥x FreeBSD ¥D¾÷¡AÅý¶] Win95 ªº¹q¸£¯à°÷¤Wºô¡C³o­Ó°ÝÃDºâ¬O«e¤@
 	    ­Ó°ÝÃDªº¤@­Ó¯S¨Ò</para> <para>... µª®×¬O¡G¥i¥Hªº¡I¦b FreeBSD 3.x
 	    ª©¤¤¡A¨Ï¥ÎªÌ¼Ò¦¡(user-mode)ªº &man.ppp.8; ¥]§t¤F
 	    <option>-nat</option> ¿ï¶µ¡C¦pªG§A¦b
 	    <filename>/etc/rc.conf</filename> ¨Ï¥Î<option>-nat</option>¿ï¶µ¨Ã
 	    ³]©w <literal>gateway_enable</literal> ¬° <emphasis>YES</emphasis>
 	    ¡A¥H³oºØ³]©w±Ò°Ê &man.ppp.8; ¡A¨Ã¥B¥¿½Tªº³]©w§Aªº Windows ¥D¾÷ªº
 	    ¸Ü¡A³o­Ó°µªkÀ³¸Ó¬O¥i¥H¥¿±`¨Ï¥Îªº¡C
 
           <para>Ãö©ó¥»¥DÃD§ó¸Ô²Óªº¸ê®Æ¥i¥H°Ñ¦Ò Steve Sims ©Ò¼¶¼gªº <ulink
 	    URL="../ppp-primer/index.html"> Pedantic PPP Primer</ulink> ¤@¤å¡C
 	    </para>
 
           <para>¦pªG§A¨Ï¥Îªº¬O®Ö¤ß¼Ò¦¡ (kernel-mode) PPP¡A©ÎªÌ§A¦³°Ï°ì³s½u
 	    (Ethernet connection) ¥i³q¹F Internet ªº¸Ü¡A§A±N»Ý­n¨Ï¥Î
 	    &man.natd.8;¡C½Ð¬d¾\ FAQ ¤¤Ãö©ó <link linkend="natd">natd</link>
 	    ªº³¡¤À¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="slip-ppp-support">
           <para>FreeBSD ¤ä´© SLIP ©M PPP ¶Ü¡H</para>
         </question>
 
         <answer>
           <para>¬Oªº¡C§A¥i¥H¬d¬d man pages ¤¤Ãö©ó &man.slattach.8;¡A
             &man.sliplogin.8;¡A&man.ppp.8;¡A¥H¤Î &man.pppd.8; ªº³¡¤À¡C
 	    &man.ppp.8; ¤Î &man.pppd.8; ´£¨Ñ¶i¥XÂù¦V³s½uªº¤ä´©¡A¥t¥~
 	    &man.sliplogin.8; ±Mªù´£¨Ñ¶i¤J³s½uªº¤ä´©¡A¦Ó &man.slattach.8;
 	    ±Mªù´£¨Ñ¦V¥~³s½uªº¤ä´©¡C</para>
 
           <para>¦pªG§A»Ý­n§ó¶i¤@¨Bªº¸ê®Æªº¸Ü,½Ð¬d¾\ <ulink
 	    url="../handbook/ppp-and-slip.html">FreeBSD ¤â¥U¤¤Ãö©ó PPP »P SLIP
 	    ªº»¡©ú</ulink>¡C</para>
 
           <para>¦pªG§A¥u¯à°÷¹L <quote>shell account</quote> ³s½u¨ì Internet
 	    ªº¸Ü¡A§A¤]³\¥i¥H¸Õ¸Õ <filename role="package">net/slirp</filename>
 	    ³o­Ó®M¥óµ{¦¡¡C³o­Ó®M¥óµ{¦¡¥i¥H´£¨Ñ§Aªº¹q¸£ª½±µ³s¤W¬Y¨Ç(­­©wªº)ªA°È
 	    ³s½u¡A¦p ftp ¤Î http µ¥µ¥¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="natd">
           <para>FreeBSD ¤ä´© NAT ©Î Masquerading ¶Ü¡H</para>
         </question>
 
         <answer>
           <para>¦pªG§A¦³¤@­ÓªñºÝªº¤lºô¸ô(¦³¤@¥x¥H¤Wªº¾÷¾¹)¡A¦ý¬O§Aªº
 	    Internet provider «o¥u¤À°t¤@­Ó IP number µ¹§A(©ÎªÌ§A¥u¤À°t¨ì¤@­Ó
 	    °ÊºAªº IP number)¡A§A¥i¥H°Ñ¦Ò &man.natd.8; ³o­Óµ{¦¡¡C &man.natd.8;
 	    Åý§A¥i¥H³z¹L³o¤@­Ó IP number Åý¾ã­Ó¤lºô¸ôªº¹q¸£³£¯à³s¤W internet¡C
 	    </para>
 
           <para>&man.ppp.8; ³o­Óµ{¦¡¤]´£¨ÑÃþ¦üªº¥\¯à¡A¦pªG§A«ü©w
 	    <option>-nat</option> ¿ï¶µ¡Calias library (&man.libalias.3;)
 	    ¦b³o¨â­Ó³B²z¤è¦¡¤¤³£·|³Q¨Ï¥Î¨ì¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="parallel-connect">
           <para>§Ú¦p¦ó±N¨â¥x FreeBSD ¥D¾÷¥Î¥­¦æ°ð (parallel line) ³z¹L PLIP
 	    ³s½u¡H</para>
         </question>
 
         <answer>
           <para>½Ð°Ñ¦Ò¤â¥U¤¤Ãö©ó <ulink url="../handbook/plip.html">PLIP
             section</ulink> ªº³¡¤À¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="create-dev-net">
           <para>§Ú¨S¦³¿ìªk«Ø¥ß <filename>/dev/ed0</filename> ³o­Ó device¡A
 	    ¬°¤°»ò¡H</para>
         </question>
 
         <answer>
           <para>¦]¬°¤£»Ý­n¡I¦b Berkeley ºô¸ô¬[ºc¤¤¡A¥u¦³ kernel µ{¦¡½X¥i¥Hª½
 	    ±µ¦s¨úºô¸ô¬É­±¥d¡C½Ð°Ñ¦Ò <filename>/etc/rc.network</filename> ³o
 	    ­ÓÀɮשM manual pages ¨ú±o»P¨ä¥L¤£¦Pºô¸ôµ{¦¡¡C§ó¶i¤@¨Bªº¸ê°T¡G¦p
 	    ªG§Aı±o§A§¹¥þ·d²V¤Fªº¸Ü¡A±zÀ³¸Ó§ä¤@¥»»P¨ä¥L BSD ¬ÛÃö§@·~¨t²Îºô¸ô
 	    ºÞ²z¦³Ãö®Ñ¨Ó°Ñ¦Ò¡F°£¤F¤Ö¼ÆÅãµÛªº¤£¦P¥~¡AFreeBSD ªººô¸ôºÞ²z°ò¥»¤W©M
 	    SunOS 4.0 ©M Ultrix ¬O¤@¼Ëªº¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ethernet-aliases">
           <para>§Ú¦p¦ó«Ø¥ß Ethernet aliases¡H</para>
         </question>
 
 	<answer>
 	  <para>¦pªG§Aªº alias ¦ì§}¸ò§A¥Ø«eºô¸ô¤¶­±ªº¦ì§}¦b¦P¤@­Ó¤lºô¸ô¤Uªº
 	    ¸Ü¡A¥[¤J¤@­Ó <literal>netmask 0xffffffff</literal> ¦b§Aªº 
 	    &man.ifconfig.8; command-line¡A½d¨Ò¦p¤U¡G</para>
 	  <screen>&prompt.root; <userinput>ifconfig ed0 alias 192.0.2.2 netmask 0xffffffff</userinput></screen>
 	  <para>¤£µMªº¸Ü¡A´N¦p¦P¥[¤J¤@­Ó·sªººô¸ô¦ì§}¤@¼Ë¿é¤J§Aªººô¸ô¦ì§}»P¤l
 	    ºô¸ô¾B¸n¡G</para>
 	  <screen>&prompt.root; <userinput>ifconfig ed0 alias 172.16.141.5 netmask 0xffffff00</userinput></screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="port-3c503">
           <para>§Ú¦p¦ó«ü©w§Úªº 3C503 ¨Ï¥Î¨ä¥L¤£¦Pªºªº network port¡H</para>
         </question>
 
         <answer>
           <para>¦pªG±z·Q¨Ï¥Î¨ä¥Lªº port¡A§A¥²¶·¦b &man.ifconfig.8; ªº©R¥O¤¤
 	    «ü©wÃB¥~ªº°Ñ¼Æ¡C¤º©wªº port ¬O <literal>link0</literal>¡C­n¨Ï¥Î
 	    AUI port ¥N´À BNC port ªº¸Ü¡A§ï¥Î <literal>link2</literal>¡C³o¨Ç
 	    flags À³¸Ó§ïÅÜifconfig_* ªºÅܼƨӫü©w¡A §A¥i¥H¦b
 	    <filename>/etc/rc.conf</filename> ³o­ÓÀɮ׸̭±§ä¨ì (½Ð°Ñ¦Ò
 	    &man.rc.conf.5;)¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="nfs">
           <para>¬°¤°»ò§Ú¦b¨Ï¥Î FreeBSD ªº NFS ®É¥X²{°ÝÃD¡H</para>
         </question>
 
         <answer>
           <para>§Ú­Ì¥Î§t»W¤@ÂIªº»¡ªk¡A¬Y¨Ç PC ªººô¸ô¥d¤ñ¨ä¥Lªº¦n¡A³oºØª¬ªp¦b
 	    ³y¦¨ NFS ³oºØ¹ïºô¸ô±Ó·Pªºµ{¦¡¦³®É·|¥X²{°ÝÃD¡C</para>
 
           <para>°Ñ¦Ò <ulink URL="../handbook/nfs.html">
 	    the Handbook entry on NFS</ulink> ¥HÀò±o³o­Ó¥DÃDªº§ó¦h¸ê°T¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="nfs-linux">
           <para>¬°¤°»ò§Ú¤£¯à NFS-mount Linux ªº¾÷¾¹¡H</para>
         </question>
 
         <answer>
           <para>¬Y¨Çª©¥»ªº Linux NFS µ{¦¡½X¥u±µ¨ü privileged port ªº
 	    mount request¡F¸Õ¥Î³o¦æ«ü¥O¬Ý¬Ý</para>
 
           <screen>&prompt.root; <userinput>mount -o -P linuxbox:/blah /mnt</userinput></screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="nfs-sun">
           <para>¬°¤°»ò§Ú¤£¯à NFS-mount Sun ªº¾÷¾¹¡H</para>
         </question>
 
         <answer>
           <para>¶] SunOS 4.X ªº Sun ¤u§@¯¸¥u±µ¨ü¨Ó¦Û privileged port ªº
 	    mount request¡F¸Õ¥Î³o¦æ«ü¥O¬Ý¬Ý</para>
 
           <screen>&prompt.root; <userinput>mount -o -P sunbox:/blah /mnt</userinput></screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="exports-errors">
           <para>¬°¤°»ò <command>mountd</command> ¤@ª½°­¥s»¡
             <errorname>can't change attributes</errorname> ¦Ó¥B§Ú¤@ª½¬Ý¨ì
             <errorname>bad exports list</errorname> ³o­Ó°T®§¦b§Úªº FreeBSD NFS
             ¦øªA¾¹¤W¡H</para>
         </question>
 
         <answer>
           <para>³o­Ó°ÝÃD³Ì±`µo¥Íªº­ì¦]¬O¦b©ó¤£¤F¸Ñ
 	    <filename>/etc/exports</filename> ªº¥¿½T®æ¦¡¡C½Ð¸ÔŪ
 	    &man.exports.5; ¥H¤Î¤â¥U¤¤Ãö©ó <ulink
             url="../handbook/nfs.html">NFS</ulink> ªº³¡¤À¡A¯S§O¬O<ulink
             url="../handbook/nfs.html#CONFIGURING-NFS">configuring
             NFS</ulink>³o¤@¬q¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-nextstep">
           <para>¬°¤°»ò§Ú¦b¨Ï¥Î PPP ³s½u¨ì NeXTStep ¾÷¾¹®É¦³°ÝÃD¡H</para>
         </question>
 
         <answer>
 
           <para>§â TCP extensions ¨ú®ø¡A³o­Ó³]©w¦b
 	    <filename>/etc/rc.conf</filename> ¸Ì­±(°Ñ¦Ò &man.rc.conf.5;) §â
 	    ¥H¤U³o­Ó­È³]¦¨ NO¡G</para>
 
           <programlisting>tcp_extensions=NO</programlisting>
 
           <para>Xylogic ªº Annex ¥D¾÷¤]¦³¬Û¦Pªº°ÝÃD¡A±z­n°µ¬Û¦Pªº­×§ï¤~¯à³s
 	    ¤W³o¨Ç¥D¾÷¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ip-multicast">
           <para>§Ú­n«ç¼Ë¤~¯à§â IP multicast support ¥´¶}¡H</para>
         </question>
 
         <answer>
           <para>FreeBSD 2.0 ¥H«áªºª©¥»¤º©w³£¦³ ¤ä´© Multicast host ¾Þ§@¡C¦pªG
 	    ±z·Q±N±zªº¥D¾÷³]©w¦¨ multicast router ªº¸Ü¡A±z¥²¶·­«·s compile ±z
 	    ªº kernel¡A¥[¤J <literal>MROUTING</literal> ªº¿ï¶µ¡A¨Ã¥B°õ¦æ
 	    &man.mrouted.8; FreeBSD 2.2 ¤Î¤§«áªºª©¥»·|¦b¶}¾÷®É°õ¦æ
 	    &man.mrouted.8; ¦pªG¦b <filename>/etc/rc.conf</filename> ¤¤
             <literal>mrouted_enable</literal> ³]©w¬° <literal>"YES"</literal>
 	    </para>
 
           <para>MBONE ªº¦UºØ¤u¨ã¥i¥H¦b¥L­Ì ports ¤U©ÒÄÝ¥s°µ <ulink
 	    url="http://www.FreeBSD.org/ports/mbone.html">mbone</ulink> ¥Ø¿ý
 	    ¤¤§ä¨ì¡C¦pªG±z¦b§äµø°T·|ijªº¤u¨ã¦p <command>vic</command> ¥H¤Î
 	    <command>vat</command>ªº¸Ü¡A¨ì¨ºÃä§ä§ä§a¡I</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="dec-pci-chipset">
           <para>­þ¨Çºô¸ô¥d¬O¨Ï¥Î DEC PCI chipset¡H</para>
         </question><answer>
 
           <para>¥H¤U¬O Glen Foster <email>gfoster@driver.nsta.org</email>
 	    ´£¨Ñªº²M³æ¡G</para>
 
           <table>
             <title>Network cards based on the DEC PCI chipset</title>
 
             <tgroup cols=2>
               <thead>
                 <row>
                   <entry>Vendor</entry>
                   <entry>Model</entry>
                 </row>
               </thead>
 
               <tbody>
                 <row>
                   <entry>ASUS</entry>
                   <entry>PCI-L101-TB</entry>
                 </row>
                 <row>
                   <entry>Accton</entry>
                   <entry>ENI1203</entry>
                 </row>
                 <row>
                   <entry>Cogent</entry>
                   <entry>EM960PCI</entry>
                 </row>
                 <row>
                   <entry>Compex</entry>
                   <entry>ENET32-PCI</entry>
                 </row>
                 <row>
                   <entry>D-Link</entry>
                   <entry>DE-530</entry>
                 </row>
                 <row>
                   <entry>Dayna</entry>
                   <entry>DP1203, DP2100</entry>
                 </row>
                 <row>
                   <entry>DEC</entry>
                   <entry>DE435, DE450</entry>
                 </row>
                 <row>
                   <entry>Danpex</entry>
                   <entry>EN-9400P3</entry>
                 </row>
                 <row>
                   <entry>JCIS</entry>
                   <entry>Condor JC1260</entry>
                 </row>
                 <row>
                   <entry>Linksys</entry>
                   <entry>EtherPCI</entry>
                 </row>
                 <row>
                   <entry>Mylex</entry>
                   <entry>LNP101</entry>
                 </row>
                 <row>
                   <entry>SMC</entry>
                   <entry>EtherPower 10/100 (Model 9332)</entry>
                 </row>
                 <row>
                   <entry>SMC</entry>
                   <entry>EtherPower (Model 8432)</entry>
                 </row>
                 <row>
                   <entry>TopWare</entry>
                   <entry>TE-3500P</entry>
                 </row>
                 <row>
                   <entry>Znyx (2.2.x)</entry>
                   <entry>ZX312, ZX314, ZX342, ZX345, ZX346, ZX348</entry>
                 </row>
                 <row>
                   <entry>Znyx (3.x)</entry>
                   <entry>ZX345Q, ZX346Q, ZX348Q, ZX412Q, ZX414, ZX442, ZX444,
                     ZX474, ZX478, ZX212, ZX214 (10mbps/hd)</entry>
                 </row>
               </tbody>
             </tgroup>
           </table>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="fqdn-hosts">
           <para>¬°¤°»ò­n¥Î FQDN ¤~¯à³s¨ì¨ä¥L¾÷¾¹¡H</para>
         </question>
 
         <answer>
           <para>§A¤]³\·|µo²{­n³sªº¾÷¾¹¨ä¹ê¬O¦b¥t¤@­Óºô°ì¡CÁ|­Ó¨Ò¤l¡A°²³]§A¬O¦b
 	    foo.bar.edu ³o­Óºô°ì¤¤¡A·Q­n³s¨ì¦b¤@¥x¥s <hostid>mumble</hostid>
 	    ªº¥D¾÷¡A¥L¦b <hostid role="domainname">example.org</hostid> ºô°ì¤U¡A
 	    §A¥²¶·¥Î Fully-Qualified Domain Name <hostid
             role="fqdn">mumble.example.org</hostid>¡A¦Ó¤£¬O¥u¥Î
             <hostid>mumble</hostid>¡C</para>
 
           <para>¶Ç²Îªº BSD BIND resolver ¤¹³\¥Î³oºØ¤è¦¡¸Ñ¥X¾÷¾¹ªº¦ì§}¡A¦ý¬O
 	    FreeBSD ¤ºªþ <application>bind</application> (see &man.named.8;)
 	    ª©¥»¤º©w¤è¦¡¡A«h¬O°£¤F§A©Ò¦bªººô°ì¥H¥~¡A¤£¤ä´©¨ä¥L«D FQDN ªºÁY¼g¡C
 	    ©Ò¥H¦p <hostid>mumble</hostid> ¥²¶·¦b <hostid
 	    role="fqdn">mumble.foo.example.org</hostid>¡A§_«h´N·|±qºô°ìªº³Ì©³
 	    ¼h¶}©l§ä¡C</para>
 
           <para>³o©M¥ý«eªº°µªk¤£¦P¡A¤]´N¬O¤£¥Î
             <hostid role="domainname">mumble.example.org</hostid>¡A©M
             <hostid role="domainname">mumble.edu</hostid> Ä~Äò·j´M¡C
             ¬Ý¤@¤U RFC 1535¡A¸Ì­±¦³´£¨ì¬°¤°»ò¤§«eªº°µªk¤£¦n¡A¬Æ¦Üºâ¬O­Ó¦w¥þ
 	    º|¬}¡C</para>
 
           <para>³o¸Ì¦³­Ó¤£¿ùªº¸Ñªk, §A¥i¥H¥[¤J¤@¦æ</para>
 
           <programlisting>search foo.example.org example.org</programlisting>
 
           <para>instead of the previous</para>
 
           <programlisting>domain foo.example.org</programlisting>
 
           <para>¦b§Aªº <filename>/etc/resolv.conf</filename> Àɮפ¤ (½Ð°Ñ¦Ò
 	    &man.resolv.conf.5;)¡C¦ý¬O­n½T©w·j´M¶¶§Ç¤£·|¹H¤Ï RFC 1535 ©Ò¿×ªº
             <quote>boundary between local and public administration</quote>¡C
 	    </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="network-permission-denied">
           <para>¬°¤°»ò§Ú¦b³s½u®É¤@ª½¥X²{
 	    <errorname>Permission denied</errorname> ªº¿ù»~°T®§¡H</para>
         </question>
 
         <answer>
           <para> ¦pªG¦b½sĶ kernel ®É¥[¤J <literal>IPFIREWALL</literal> ¿ï¶µ¡A
             ½Ðª`·N 2.1.7R ¤º©w¬O©Úµ´©Ò¦³¥¼¸g®Ö­ãªººô¸ô«Ê¥](¦ý¦b¶}µo
 	    2.1-STABLE ®É§ï±¼¤F)¡C</para>
 
           <para>I¦pªG¤£¤p¤ß§Ë¿ù¤F firewall ªº³]©w¡A§A¥i¥H¥H
 	    <username>root</username> °õ¦æ¥H¤U©R¥Oºô¸ô¥\¯à´N·|«ì´_¥¿±`¡G</para>
 
           <screen>&prompt.root; <userinput>ipfw add 65534 allow all from any to any</userinput></screen>
 
           <para>¤]¥i¥H¦b <filename>/etc/rc.conf</filename> ¥[¤J
 	    <literal>firewall_type="open"</literal> ªº¿ï¶µ¡C</para>
 
           <para>¦pªG·Qª¾¹D¦p¦ó³]©w FreeBSD firewall¡A½Ð°Ñ¦Ò <ulink
 	    URL="../handbook/firewalls.html">¤â¥U¤¤¬ÛÃö³¹¸`</ulink>¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ipfw-overhead">
           <para>IPFW ·|³y¦¨¦h¤jªººô¸ô©µ¿ð¡H</para>
         </question>
 
         <answer>
           <para>½Ð°Ñ¦Ò¤â¥U¤¤ <ulink
             url="../handbook/firewalls.html">Firewalls</ulink> ³¹¸`¡A¯S§O¬O
 	    <ulink url="../handbook/firewalls.html#IPFW-OVERHEAD">IPFW
             Overhead & Optimization</ulink> ³o¤@¬q¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ipfw-fwd">
           <para>¬°¤°»ò§Úªº <command>ipfw</command> <quote>fwd</quote>
 	    redirect ³W«h±NªA°ÈÂà¦V¨ä¥L¾÷¾¹®ÉµLªk¥¿±`¹B§@¡H</para>
         </question>
 
         <answer>
           <para>¥i¯à¬O§A°£¤FÂà°e«Ê¥]¥H¥~ÁÙÃB¥~·Q¶i¦æ¦ì§}ÂàĶ
 	    (network address translation, NAT)¡A<quote>fwd</quote> ³W«h©Ò¶i
 	    ¦æªº°Ê§@´N¦p¦P¦r­±©Ò¥Ü¡F¶ÈÂà°e«Ê¥]¡A¥¦¨Ã¤£·|¥h­×§ï«Ê¥]¤¤ªº¸ê®Æ¡C
             °²³]§Ú­Ì¦³¦p¤Uªº³W«h¡G</para>
 
           <screen>01000 fwd <replaceable>10.0.0.1</replaceable> from any to <replaceable>foo 21</replaceable></screen>
 
           <para>·í¤@­Ó³q©¹¯S©w¥Ø¼Ð¦ì§} <replaceable>foo</replaceable> ªº«Ê¥]
 	    °e¹F¥D¾÷®É¡A®Ú¾Ú³o±ø³W«h¡A«Ê¥]±N³QÂà°e¦Ü
 	    <replaceable>10.0.0.1</replaceable>¡A¦ý¬O¥¦ªº¥Ø¼Ð¦ì§}«o¤´µM¬O
 	    <replaceable>foo</replaceable>¡I«Ê¥]ªº¥Ø¼Ð¦ì§}¨Ã
 	    <emphasis>¨S¦³</emphasis> §ó§ï¬°
 	    <replaceable>10.0.0.1</replaceable>¡C¤j³¡¤Àªº¥D¾÷·|±N«Ê¥]¥á±ó¡A
 	    ¦]¬°¥L­Ì¨Ã¤£¬O³o­Ó¥Ø¼Ð¦ì§}¡C¦]¦¹¡A¨Ï¥Î <quote>fwd</quote> ³W«h
 	    ®É©¹©¹¤£¦p¨Ï¥ÎªÌ©Ò¹w´Áªº¨º¯ë¶¶§Q¡C³oºØ¦æ¬°¬O¨t²Î¯S©Ê¡A¦Ó«D¿ù»~¡C
 	    </para>
 
           <para>°Ñ¦Ò <link linkend="service-redirect">Ãö©óªA°ÈÂà¦Vªº±`¨£°Ý
 	    µª¶°</link>¡A &man.natd.8; ¤â¥U¡A©ÎªÌ¬O¨Ï¥Î <ulink
 	    url="../../../../ports/index.html">ports collection</ulink> ¤¤³\
 	    ¦hªA°ÈÂà¦Vªº¤u¨ã¨Ó¥¿½Tªº§¹¦¨§A·Q¶i¦æªº¤u§@¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="service-redirect">
           <para>­n¦p¦ó§â¹ï¬Y¥x¾÷¾¹ªººô¸ôªA°È­n¨D(service request)Âà¦V¨ì¥t¤@¥x¡H
 	    </para>
         </question>
 
         <answer>
           <para>¦b ports ¥Ø¿ýªº<quote>sysutils</quote>¤ÀÃþ¤¤¦³­Ó¥s
 	    <literal>socket</literal> ªº®M¥ó¡A¥i¥HÀ°§AÂà¦V FTP ©Î¨ä¥LÃþ¦üªº
 	    ºô¸ôªA°È¡C¥u­n§â¸Óºô¸ôªA°Èªº©R¥O§ï¦¨©I¥s socket §Y¥i¡A¦p¤U©Ò¥Ü¡G
 	    </para>
 
           <programlisting>ftp stream tcp nowait nobody /usr/local/bin/socket socket <replaceable>ftp.example.com</replaceable> <replaceable>ftp</replaceable></programlisting>
 
           <para>¨ä¤¤ <replaceable>ftp.example.com</replaceable> »P 
             <replaceable>ftp</replaceable> ¤À§O¬O³QÂà¨ìªº¾÷¾¹©M port ¦WºÙ¡C
 	    </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="bandwidth-mgr-tool">
           <para>¨º¸Ì¥i¥H§ä¨ìºÞ²zÀW¼eªº¤u¨ã¡H</para>
         </question>
 
         <answer>
           <para>FreeBSD ¤W¦³¤T®MÀW¼eºÞ²z¤u¨ã¡G &man.dummynet.4; ¤w¸g¾ã¦X¶i¤J
 	    FreeBSD ¨t²Î(§ó¸Ô²Óªº¥Î³~, &man.ipfw.4;); <ulink
 	    URL="http://www.csl.sony.co.jp/person/kjc/programs.html">ALTQ</ulink>
 	    ¥i¥H§K¶O¨Ï¥Î¡A<ulink
 	    URL="http://www.etinc.com/">Emerging Technologies</ulink>
 	    ±À¥Xªº Bandwidth Manager «h¬O°Ó¥Î³nÅé¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="bpf-not-configured">
           <para>«ç»ò·|¶]¥X
 	    <errorname>/dev/bpf0: device not configured</errorname>³o­Ó°T®§¡H
 	    </para>
         </question>
 
         <answer>
           <para>§A°õ¦æ¤F¤@­Ó»Ý­n¬f§JµÜ«Ê¥]¹LÂo¾¹ (Berkeley Packet Filter) ªº
 	    µ{¦¡ (&man.bpf.4;)¡A¦ý¬O§A¦b kernel ¤¤¨S¦³±Ò°Ê¥¦¡C§â¤U­±³o¤@¦æ¥[
 	    ¤J kernel ³]©wÀɤ¤¡A½sĶ¤@­Ó·sªº kernel¡G</para>
 
           <programlisting>pseudo-device bpf        # Berkeley Packet Filter</programlisting>
 
           <para>¦b­«·s¶}¾÷¤§«á¡AÁÙ­n°µ¥X device node¡A¦b
 	    <filename>/dev</filename> ¤U°õ¦æ¡G</para>
 
           <screen>&prompt.root; <userinput>sh MAKEDEV bpf0</userinput></screen>
 
           <para>¦pªG·Q­n§ó¶i¤@¨Bª¾¹D¦p¦ó°µ¥X¦UºØ device node¡A½Ð°Ñ¾\ <ulink
             URL="../handbook/kernelconfig-nodes.html">Handbook Ãö©ó¶gÃä¸`ÂIªº»¡©ú</ulink>
 	    ¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="mount-smb-share">
           <para>§Ú­n«ç¼Ë¤~¯à±N Windows ¾÷¾¹¤¤ªººÏºÐ±¾¤J¨t²Î, ´N¹³ Linux ´£¨Ñ
 	    ªº smbmount ¨º¼Ë¡H</para>
         </question>
 
         <answer>
           <para>¨Ï¥Î <application>SMBFS</application> ¤u¨ã²Õ¡C³o®M¤u¨ã²Õ¤¤ 
             ¥]§t¤F¤@¨t¦Cªº kernel ­×§ïÁÙ¦³¨Ï¥ÎªÌªº¤u¨ãµ{¦¡(userland programs)¡C
 	    ³o¨Çµ{¦¡©M¸ê°T¦b ports ¦¬Âä¤
 	    <filename role="package">net/smbfs</filename> ¤U¥i¥H§ä¨ì¡C¦b
 	    4.5-RELEASE ¤§«áªºª©¥»«h¬O¨t²Î¤¤¤º«Ø¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="icmp-response-bw-limit">
           <para>§Ú¦b¨t²Î¤é»x¤¤µo²{¥H¤U°T®§¡G
 	    <quote>icmp-response bandwidth limit 300/200 pps</quote>¡A³o¬O
 	    ½¼¦Ì¸J¿|¡H</para>
         </question>
 
         <answer>
           <para>³o¬O¨t²Î®Ö¤ß§i¶D§A¦³¬Y¨Ç¬¡°Ê¤Þµo¥¦°e¥X¤ñ¥¦©Ò»{¬°À³¸Ó°e¥X§ó
 	    ¦hªº ICMP ©Î TCP ­«¸m°T®§ (RST)¡CICMP ¦^À³°T®§±`±`¬O¦]¬°¦³¤H¹Á
 	    ¸Õ³s±µ¥¼³Q¨Ï¥Îªº UDP ³q°T°ð¡CTCP ­«¸m°T®§«h¬O¦³¤H¹Á¸Õ³s±µ¥¼¶}
 	    ©ñ TCP ³q°T°ð³y¦¨ªºµ²ªG¡C¥H¤U³o¨Ç¬¡°Ê¥i¯à´N¬O³y¦¨³o¨Ç°T®§ªº­ì¦]¡G
 	    </para>
 
           <itemizedlist>
             <listitem>
               <para>¼É¤OªkªºªA°È²Õµ´§ðÀ»(DoS)¤è¦¡
 	        (¬Û¸û©ó°w¹ï¯S®í®zÂI¨Ï¥Î³æ¤@«Ê¥]ªº§ðÀ»¤è¦¡)¡C</para>
             </listitem>
 
             <listitem>
               <para>¤j¶qªº³q°T°ð±½´y(¬Û¸û©ó¶È¹Á¸Õ¤Ö¼Æªº±`¨£ªA°È³q°T°ð)¡C</para>
             </listitem>
           </itemizedlist>
 
           <para>¥X²{ªº¼Æ¦r¤¤²Ä¤@­Ó¥Nªí®Ú¾Ú³o¨Ç¬y¶q kernel À³¸Ó°e¥Xªº«Ê¥]¼Æ¡A
             ²Ä¤G­Ó¼Æ¦r«h¬O kernel ¥Ø«e­­¨î³Ì¤jµo°e¼Æ¡C§A¥i¥H§Q¥Î sysctl ­×§ï
 	    <varname>net.inet.icmp.icmplim</varname> ÅܼƭȨӧó§ï³Ì¤j­È¡CÁ|
 	    ¨Ò¨Ó»¡,¦pªG§Æ±æ­×§ï­­¨î¬° <literal>300</literal> packets per
 	    second¡G</para>
 
           <screen>&prompt.root; <userinput>sysctl -w net.inet.icmp.icmplim=300</userinput></screen>
 
           <para>¦pªG§A¤£·Q¦b¨t²Î¬ö¿ý¤¤¬Ý¨ì³o¨Ç°T®§¡A¦ý¬O¤´µM§Æ±æ«O«ù¦^À³ªº­­
 	    ¨îªº¸Ü¡A§A¥i¥H§Q¥Î sysctl ­×§ï
 	    <varname>net.inet.icmp.icmplim_output</varname> ÅܼƨӨú®ø³o¨Ç°T
 	    ®§¡G</para>
 
           <screen>&prompt.root; <userinput>sysctl -w net.inet.icmp.icmplim_output=0</userinput></screen>
 
           <para>³Ì«á¡A¦pªG§A·Q¨ú®ø³o¨Ç­­¨îªº¸Ü¡A§A¥i¥H³]©w
 	    <varname>net.inet.icmp.icmplim</varname> (¦p¤W¨Ò©Ò¥Ü) ¬°
 	    <literal>0</literal>¡C°ò©ó¤W­z²z¥Ñ¡A§Ú­Ì¤£«Øij§A¨ú®ø³o¨Ç­­¨î¡C
 	    </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="unknown-hw-addr-format">
           <para>³o­Ó¿ù»~°T®§
 	    <errorname>arp: unknown hardware address format</errorname>
 	    ¬O¤°»ò·N«ä¡H</para>
         </question>
 
         <answer>
           <para>³o¥Nªí§Aªº°Ï°ìºô¸ô³s½u¤W¦³¤@¨Ç³]³Æ¨Ï¥Î FreeBSD ¬Ý¤£À´±o MAC
 	    ®æ¦¡¡C³o³q±`¬O¥Nªí¦³¤H¦b§Aªº°Ï°ìºô¸ô¤W¶i¦æ¹êÅç¡A³Ì±`¨£ªº´N¬O
 	    cable modem ªº³s½u¡C³o°T®§µL®`¡A¦Ó¥BÀ³¸Ó¤£¦Ü©ó¼vÅT¨ì FreeBSD ¥D
 	    ¾÷ªº®Ä¯à¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="cvsup-missing-libs">
           <para>§Ú­è­è¸Ë¦n CVSup ®M¥ó¡A¦ý¬O¦b¹Á¸Õ°õ¦æ®Éµo¥Í¤F¿ù»~¡A­n«ç»ò¿ì¡H
 	    </para>
         </question>
 
         <answer>
           <para>­º¥ý¡A¬Ý¬Ý¿ù»~ªº°T®§¬O§_¦p¤U¡G</para>
 
           <programlisting>/usr/libexec/ld-elf.so.1: Shared object "libXaw.so.6" not found</programlisting>
 
           <para>³oºØ¿ù»~°T®§¥Nªí§A¥D¾÷¤W¦w¸Ëªº
 	    <filename role="package">net/cvsup</filename> ¨S¦³¥]§t
 	    <application>XFree86</application> ®M¥ó¡C¦pªG§A·Q­n¨Ï¥Î
 	    <application>CVSup</application> ¤º«Øªº¹Ï§Î¤¶­±
 	    <acronym>GUI</acronym> ªº¸Ü¡A§A»Ý­n¦w¸Ë
 	    <application>XFree86</application>¡C¦¹¥~¡A¦pªG§A¥u·Q¥H©R¥O¦C¤è
 	    ¦¡¨Ï¥Î <application>CVSup</application> ªº¸Ü¡A§AÀ³¸Ó¥ý²¾°£¤§«e
 	    ¦w¸Ëªº®M¥ó¡C¨Ã¦w¸Ë
 	    <filename role="package">net/cvsup-without-gui</filename> ³o®M
 	    ³nÅé¡C¦b FreeBSD ¤â¥U¤¤ <ulink
 	    url="http://www.freebsd.org/handbook/cvsup.html">CVSup</ulink>
 	    ¬q¸¨¤¤¦³§ó¸Ô²Óªº»¡©ú¡C</para>
         </answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter id="security">
     <chapterinfo>
       <author>
 	<firstname>Biing Jong</firstname>
 	<surname>Lin</surname>
 	<affiliation>
 	  <address><email>bjlin@stic.gov.tw</email></address>
 	</affiliation>
       </author>
     </chapterinfo>
 
     <title>Security</title>
     <qandaset>
       <qandaentry>
         <question id="extra-named-port">
 	  <para>BIND (<command>named</command>) °£¤F¦b³q°T°ð 53 ¥H¥~¤]¦b
 	    ¨ä¥L°ª½s¸¹³q°T°ð (high-numbered port) ²âÅ¥ (Listen)¡C
 	    ³o¬O«ç»ò¦^¨Æ¡H</para>
 	</question>
 
 	<answer>
 	  <para>FreeBSD 3.0 «áªºª©¥»¨Ï¥Î¤@­Ó¯S®íªº BIND ª©¥»¡A³o­Óª©¥»·|¨Ï
 	    ¥ÎÀH¾÷ªº°ª½s¸¹³q°T°ð¨Ó¦^À³¥~³¡ªº¬d¸ß¡C¦pªG§A¦]¬°­n¾A¦X¨¾¤õÀðªº
 	    ³]©w©Î¬O³æ¯Âªº·QÅý¦Û¤v¬Ý¨ÓµÎªA¤@ÂI¦Ó·Q¥Î 53 ³q°T°ð¦^À³¥~³¡¬d¸ß¡A
 	    ¨º»ò§A¥i¥H¹Á¸Õ§ó§ï¥H¤UÀɮ׬ÛÃö¤º®e 
 	    <filename>/etc/namedb/named.conf</filename>¡G</para>
 
 	  <programlisting>options {
         query-source address * port 53;
 };</programlisting>
 
 	  <para>§A¤]¥i¥H±N <literal>*</literal> §ó§ï¬°¯S©w IP address¡A
 	    ÂÇ¥H¥[±j±±¨î±ø¥ó¡C</para>
 
 	  <para>¶¶«K®¥³ß§A¡C¯à°÷Ū¨ú§A¨t²Î¤Wªº &man.sockstat.1; ³ø§i¨Ã¥Bª`·N
 	    ¤£¥¿±`ª¬ªp¬O¤@¥ó¦n¨Æ¡I</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
         <question id="sendmail-port-587">
           <para>Sendmail °£¤F¦b¼Ð·Çªº³q°T°ð 25 ¥~¤]¦b³q°T°ð 587 ²âÅ¥¡I³o¬O«ç
 	    »ò¦^¨Æ¡H</para>
         </question>
 
         <answer>
           <para>¸û·sª©¥»ªº Sendmail ¤ä´© mail submission ³o¶µ¥\¯à¡A¨Ã¥B¨Ï
 	    ¥Î³q°T°ð 587¡C³o¶µ¥\¯àÁÙ¨S¦³³Q¼sªx¤ä´©¦ý¬O¤ä´©ªº¼Æ¥Ø¥¿¦b¼Wªø
 	    ¤¤¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="toor-account">
           <para>§Úµo²{¤F³o­Ó UID 0 <username>toor</username> ±b¸¹¡A³o¬O¤°»ò
 	    ¸J¿|¡H§Ú³Q¶Â±¼¤F¶Ü¡H</para>
         </question>
 
         <answer>
           <para>©ñ¤ß¡C<username>toor</username> ¬O¤@­Ó 
             <quote>alternative</quote> ºÞ²zªÌ±b¸¹ (toor ¬O root ªºÂà¦V«÷ªk)¡C
 	    ¥H©¹¬O¸òÀH &man.bash.1; ¦w¸Ë¦Ó«Ø¨îªº¡A«á¨Ó«h¦¨¬°¨t²Î¤º©w«Ø¨îªº¤@
 	    ­Ó±b¸¹¡C³o­Ó±b¸¹±N¦ñÀH¤@­Ó«D¼Ð·Çªº shell ´ú¸Õ¨Ï¥Î¡A Åý§A¤£»Ý­n¥h
 	    §ó§ï¨ì <username>root</username> ªº¤º«Ø shell¡C¦]¬°³o¨Ç¨ä¥Lªº shell
 	    ¨Ã¨S¦³¸òÀH¨t²Î¹w³]­È¦w¸Ë (Á|¨Ò¨Ó»¡¡A¬Y¨Ç¥Ñ ports ¦w¸Ëªº
 	    shell package)¡A¦Ó³Q¤º©w¦w¸Ë¦b <filename>/usr/local/bin</filename>
 	    ¥Ø¿ý¤U¡A¦³¥i¯à¦s¦b¤£¦PªºÀɮרt²Î¤¤¡C ­Õ­Y <username>root</username>
 	    ªº shell ³Q©ñ¦b <filename>/usr/local/bin</filename>¡A¥B
 	    <filename>/usr</filename> (©Î¬O¨ä¥L¥]§tµÛ
 	    <filename>/usr/local/bin</filename> ³o­Ó¤l¥Ø¿ýªºÀɮרt²Î)
             ¦]¬°¬Y¨Ç­ì¦]¨Ã¨S¦³³Q¥¿±`ªº mount °_¨Óªº¸Ü¡A<username>root</username>
             ±NµLªk¥¿±`ªºµn¤J¨t²Î¶i¦æºû­× (ÁöµM»¡§A­«¶}¾÷¦¨³æ¤H¼Ò¦¡´N·|°Ý§A­n
 	    ¸ü¤J­þ­Ó shell)¡C</para>
 
           <para>¦³¨Ç¤H¨Ï¥Î <username>toor</username> ±b¸¹¶i¦æ¨C¤éªº
             <username>root</username> ºûÅ@¤u§@¡A¦p¦¹¥i¥H¨Ï¥Î«D¼Ð·Çªº
 	    shell¡A¦Ó <username>root</username> ¥i¥H«O¯d¼Ð·Ç shell¡A
 	    ¥H¦]À³³æ¤@¨Ï¥ÎªÌ¼Ò¦¡ (single user mode) ©Îºò«æª¬ªp³B²z¡C
 	    ¨Ì·Ó¨t²Î¤º©w­È¡A§A±NµLªk¨Ï¥Î <username>toor</username> µn¤J¡A
 	    ¦]¬°³o­Ó±b¸¹©|¥¼§ó§ï±K½X³]©w¡C¦]¦¹§A¦pªG§A·Q±Ò°Ê³o­Ó±b¸¹¡A§A»Ý­n
 	    ¨Ï¥Î <username>root</username> µn¤J¨t²Î¨Ã¥B­×§ï
 	    <username>toor</username> ªº±K½X¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="suidperl">
           <para>¬°¤°»ò <command>suidperl</command> µLªk¥¿±`¹B§@¡H</para>
         </question>
 
         <answer>
           <para>¦]¬°¬Y¨Ç¦w¥þªº¦Ò¡A<command>suidperl</command> ¤º©wªº¦w¸Ë 
             ¨Ã¨S¦³³]©w suid bit¡C¨t²ÎºÞ²zªÌ¥i¥H¨Ì·Ó¥H¤U©R¥O±Ò°Ê suid ³]©w¡C
 	    </para>
 
 	    <screen>&prompt.root; <userinput>chmod u+s /usr/bin/suidperl</userinput></screen>
 
           <para>¦pªG§A·Q­n¦b¥Ñ source ¤É¯Å®É <command>suidperl</command> ¤º©w
 	    ±Ò°Ê suid ¥\¯àªº¸Ü¡A½s¿è <filename>/etc/make.conf</filename> ¥[¤J 
             <varname>ENABLE_SUIDPERL=true</varname> µM«á°õ¦æ 
             <command>make buildworld</command>¡C</para>
         </answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter id="ppp">
     <title>PPP</title>
 
     <qandaset>
       <qandaentry>
         <question id="userppp">
           <para>I cannot make &man.ppp.8; work.  What am I doing wrong?</para>
         </question>
 
         <answer>
           <para>You should first read the
             &man.ppp.8;
             man page and the <ulink
             URL="../handbook/ppp-and-slip.html#USERPPP">
             PPP section of the handbook</ulink>.  Enable logging with
             the command</para>
 
           <programlisting>set log Phase Chat Connect Carrier lcp ipcp ccp command</programlisting>
 
           <para>This command may be typed at the
             &man.ppp.8; command prompt or it may be
             entered in the <filename>/etc/ppp/ppp.conf</filename>
             configuration file (the start of the
             <literal>default</literal> section is the best
             place to put it).  Make sure that
             <filename>/etc/syslog.conf</filename> (see &man.syslog.conf.5;) contains the lines</para>
 
           <programlisting>!ppp
 *.*        /var/log/ppp.log</programlisting>
 
           <para>and that the file <filename>/var/log/ppp.log</filename>
             exists.  You can now find out a lot about what is going on
             from the log file.  Do not worry if it does not all make sense.
             If you need to get help from someone, it may make sense to
             them.</para>
 
           <para>If your version of &man.ppp.8; does not understand the
             <command>set log</command> command, you should download the
             <ulink URL="http://people.FreeBSD.org/~brian/">
             latest version</ulink>. It will build on FreeBSD version
             2.1.5 and higher.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-hangs">
           <para>Why does &man.ppp.8; hang when I run it?</para>
         </question>
 
         <answer>
           <para>This is usually because your hostname will not resolve.
             The best way to fix this is to make sure that
             <filename>/etc/hosts</filename> is consulted by your
             resolver first by editing <filename>/etc/host.conf</filename>
             and putting the <literal>hosts</literal> line first.  Then,
             simply put an entry in <filename>/etc/hosts</filename> for
             your local machine.  If you have no local network, change your
             <hostid>localhost</hostid> line:</para>
 
           <programlisting>127.0.0.1        foo.bar.com foo localhost</programlisting>
 
           <para>Otherwise, simply add another entry for your host.
             Consult the relevant man pages for more details.</para>
 
           <para>You should be able to successfully
             <command>ping -c1 `hostname`</command> when you are done.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-nodial-auto">
           <para>Why will &man.ppp.8; not dial in <literal>-auto</literal>
             mode?</para>
         </question>
 
         <answer>
           <para>First, check that you have got a default route.  By running
             <command>netstat -rn</command> (see &man.netstat.1;), you should see two entries like this:</para>
 
           <programlisting>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</programlisting>
 
           <para>This is assuming that you have used the addresses from the
             handbook, the man page or from the ppp.conf.sample file.
             If you do not have a default route, it may be because you are
             running an old version of &man.ppp.8;
             that does not understand the word <literal>HISADDR</literal>
             in the ppp.conf file.  If your version of
             &man.ppp.8; is from before FreeBSD
             2.2.5, change the</para>
 
           <programlisting>add 0 0 HISADDR</programlisting>
 
           <para>line to one saying</para>
 
 
           <programlisting>add 0 0 10.0.0.2</programlisting>
 
           <para>Another reason for the default route line being missing
             is that you have mistakenly set up a default router in your
             <filename>/etc/rc.conf</filename> (see &man.rc.conf.5;) file (this file was called
             <filename>/etc/sysconfig</filename> prior to release 2.2.2),
             and you have omitted the line saying</para>
 
           <programlisting>delete ALL</programlisting>
 
           <para>from <filename>ppp.conf</filename>.  If this is the case,
             go back to the <ulink
             URL="../handbook/ppp-and-slip.html#USERPPP-FINAL">
             Final system configuration</ulink> section of the
             handbook.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="no-route-to-host">
           <para>What does <errorname>No route to host</errorname> mean?</para>
         </question>
 
         <answer>
           <para>This error is usually due to a missing</para>
 
           <programlisting>MYADDR:
   delete ALL
   add 0 0 HISADDR</programlisting>
 
           <para>section in your <filename>/etc/ppp/ppp.linkup</filename>
             file.  This is only necessary if you have a dynamic IP address
             or do not know the address of your gateway.  If you are using
             interactive mode, you can type the following after entering
             <literal>packet mode</literal> (packet mode is
             indicated by the capitalized <acronym>PPP</acronym> in the
             prompt):</para>
 
          <programlisting>delete ALL
 add 0 0 HISADDR</programlisting>
 
           <para>Refer to the <ulink
             URL="../handbook/ppp-and-slip.html#USERPPP-DYNAMICIP">
             PPP and Dynamic IP addresses</ulink> section of the handbook
             for further details.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="connection-threeminutedrop">
           <para>Why does my connection drop after about 3 minutes?</para>
         </question>
 
         <answer>
           <para>The default PPP timeout is 3 minutes.  This can be
             adjusted with the line</para>
 
           <programlisting>set timeout <replaceable>NNN</replaceable></programlisting>
 
           <para>where <replaceable>NNN</replaceable> is the number of
             seconds of inactivity before the connection is closed.  If
             <replaceable>NNN</replaceable> is zero, the connection is never
             closed due to a timeout. It is possible to put this command in
             the <filename>ppp.conf</filename> file, or to type it at the
             prompt in interactive mode. It is also possible to adjust it on
             the fly while the line is active by connecting to
             <application>ppp</application>s server socket using
             &man.telnet.1; or &man.pppctl.8;.
             Refer to the
             &man.ppp.8; man
             page for further details.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-drop-heavy-load">
           <para>Why does my connection drop under heavy load?</para>
         </question>
 
         <answer>
           <para>If you have Link Quality Reporting (LQR) configured,
             it is possible that too many LQR packets are lost between
             your machine and the peer.  Ppp deduces that the line must
             therefore be bad, and disconnects.  Prior to FreeBSD version
             2.2.5, LQR was enabled by default.  It is now disabled by
             default. LQR can be disabled with the line</para>
 
           <programlisting>disable lqr</programlisting>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-drop-random">
           <para>Why does my connection drop after a random amount of
             time?</para>
         </question>
 
         <answer>
           <para>Sometimes, on a noisy phone line or even on a line with
             call waiting enabled, your modem may hang up because it
             thinks (incorrectly) that it lost carrier.</para>
 
           <para>There is a setting on most modems for determining how
             tolerant it should be to temporary losses of carrier.  On a
             USR Sportster for example, this is measured by the S10
             register in tenths of a second.  To make your modem more
             forgiving, you could add the following send-expect sequence
             to your dial string:</para>
 
           <programlisting>set dial "...... ATS10=10 OK ......"</programlisting>
 
           <para>Refer to your modem manual for details.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-hangs-random">
           <para>Why does my connection hang after a random amount of
             time?</para>
         </question><answer>
 
           <para>Many people experience hung connections with no apparent
             explanation.  The first thing to establish is which side of
             the link is hung.</para>
 
           <para>If you are using an external modem, you can simply try
             using &man.ping.8; to see if the
             <acronym>TD</acronym> light is flashing when you transmit data.
             If it flashes (and the <acronym>RD</acronym> light does not),
             the problem is with the remote end. If <acronym>TD</acronym>
             does not flash, the problem is local. With an internal modem,
             you will need to use the <literal>set server</literal> command in
             your <filename>ppp.conf</filename> file. When the hang occurs,
             connect to &man.ppp.8; using &man.pppctl.8;. If your network connection
             suddenly revives (PPP was revived due to the activity on the
             diagnostic socket) or if you cannot connect (assuming the
             <literal>set socket</literal> command succeeded at startup
             time), the problem is local. If you can connect and things are
             still hung, enable local async logging with <literal>set log
             local async</literal> and use &man.ping.8; from
             another window or terminal to make use of the link. The async
             logging will show you the data being transmitted and received
             on the link. If data is going out and not coming back, the
             problem is remote.</para>
 
           <para>Having established whether the problem is local or remote,
             you now have two possibilities:</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-remote-not-responding">
           <para>The remote end is not responding.  What can I do?</para>
         </question>
 
         <answer>
           <para>There is very little you can do about this.  Most ISPs
             will refuse to help if you are not running a Microsoft OS.
             You can <literal>enable lqr</literal> in your
             <filename>ppp.conf</filename> file, allowing &man.ppp.8; to detect
             the remote failure and hang up, but this detection is
             relatively slow and therefore not that useful.  You may want to
             avoid telling your ISP that you are running user-PPP...</para>
 
           <para>First, try disabling all local compression by adding the
             following to your configuration:</para>
 
           <programlisting>disable pred1 deflate deflate24 protocomp acfcomp shortseq vj
 deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
 
           <para>Then reconnect to ensure that this makes no difference.
             If things improve or if the problem is solved completely,
             determine which setting makes the difference through trial
             and error.  This will provide good ammunition when you contact
             your ISP (although it may make it apparent that you are not
             running a Microsoft product).</para>
 
           <para>Before contacting your ISP, enable async logging locally
             and wait until the connection hangs again.  This may use up
             quite a bit of disk space.  The last data read from the port
             may be of interest.  It is usually ascii data, and may even
             describe the problem
             (<quote>Memory fault, core dumped</quote>?).</para>
 
           <para>If your ISP is helpful, they should be able to enable
             logging on their end, then when the next link drop occurs,
             they may be able to tell you why their side is having a
             problem.  Feel free to send the details to &a.brian;, or
             even to ask your ISP to contact me directly.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-hung">
           <para>&man.ppp.8; has hung.  What can I do?</para>
         </question>
 
         <answer>
           <para>Your best bet here is to rebuild &man.ppp.8; by adding
             <literal>CFLAGS+=-g</literal> and <literal>STRIP=</literal>
             to the end of the Makefile, then doing a
             <command>make clean &amp;&amp; make &amp;&amp; make
             install</command>.  When &man.ppp.8; hangs, find the &man.ppp.8; process id
             with <command>ps ajxww | fgrep ppp</command> and run
             <command>gdb ppp <replaceable>PID</replaceable></command>.
             From the gdb prompt, you can then use <command>bt</command>
             to get a stack trace.</para>
 
           <para>Send the results to <email>brian@Awfulhak.org</email>.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-loginok-thennothing">
           <para>Why does nothing happen after the <quote>Login OK!</quote>
             message?</para>
         </question>
 
         <answer>
           <para>Prior to FreeBSD version 2.2.5, once the link was
             established, &man.ppp.8;
             would wait for the peer to initiate the Line Control Protocol
             (LCP).  Many ISPs will not initiate negotiations and expect
             the client to do so.  To force
             &man.ppp.8; to initiate the LCP, use the
             following line:</para>
 
           <programlisting>set openmode active</programlisting>
 
             <note>
               <para>It usually does no
             harm if both sides initiate negotiation, so openmode is now
             active by default.  However, the next section explains when
             it <emphasis>does</emphasis> do some harm.</para>
             </note>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-same-magic">
           <para>I keep seeing errors about magic being the same.  What does
             it mean?</para>
         </question>
 
         <answer>
           <para>Occasionally, just after connecting, you may see messages
             in the log that say <quote>magic is the same</quote>.
             Sometimes, these messages are harmless, and sometimes one side
             or the other exits.  Most PPP implementations cannot survive
             this problem, and even if the link seems to come up, you will see
             repeated configure requests and configure acknowledgments in
             the log file until &man.ppp.8; eventually gives up and closes the
             connection.</para>
 
           <para>This normally happens on server machines with slow disks
             that are spawning a getty on the port, and executing &man.ppp.8; from
             a login script or program after login.  I have also heard reports
             of it happening consistently when using slirp.  The reason is
             that in the time taken between &man.getty.8; exiting and &man.ppp.8; starting,
             the client-side &man.ppp.8; starts sending Line Control Protocol (LCP)
             packets.  Because ECHO is still switched on for the port on
             the server, the client &man.ppp.8; sees these packets
             <quote>reflect</quote> back.</para>
 
           <para>One part of the LCP negotiation is to establish a magic
             number for each side of the link so that
             <quote>reflections</quote> can be detected. The protocol says
             that when the peer tries to negotiate the same magic number, a
             NAK should be sent and a new magic number should be chosen.
             During the period that the server port has ECHO turned on, the
             client &man.ppp.8; sends LCP packets, sees the same magic in the
             reflected packet and NAKs it. It also sees the NAK reflect
             (which also means &man.ppp.8; must change its magic). This produces a
             potentially enormous number of magic number changes, all of
             which are happily piling into the server's tty buffer. As soon
             as &man.ppp.8; starts on the server, it is flooded with magic number
             changes and almost immediately decides it has tried enough to
             negotiate LCP and gives up. Meanwhile, the client, who no
             longer sees the reflections, becomes happy just in time to see
             a hangup from the server.</para>
 
           <para>This can be avoided by allowing the peer to start
             negotiating with the following line in your ppp.conf
             file:</para>
 
           <programlisting>set openmode passive</programlisting>
 
           <para>This tells &man.ppp.8; to wait for the server to initiate LCP
             negotiations.  Some servers however may never initiate
             negotiations.  If this is the case, you can do something
             like:</para>
 
           <programlisting>set openmode active 3</programlisting>
 
           <para>This tells &man.ppp.8; to be passive for 3 seconds, and then to
             start sending LCP requests.  If the peer starts sending
             requests during this period, &man.ppp.8; will immediately respond
             rather than waiting for the full 3 second period.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-lcp-constant">
           <para>LCP negotiations continue until the connection is
             closed.  What is wrong?</para>
         </question>
 
         <answer>
           <para>There is currently an implementation mis-feature in
             &man.ppp.8; where it does not associate
             LCP, CCP &amp; IPCP responses with their original requests. As
             a result, if one PPP
             implementation is more than 6 seconds slower than the other
             side, the other side will send two additional LCP configuration
             requests. This is fatal.</para>
 
           <para>Consider two implementations,
             <hostid>A</hostid> and
             <hostid>B</hostid>. <hostid>A</hostid> starts
             sending LCP requests immediately after connecting and
             <hostid>B</hostid> takes 7 seconds to start. When
             <hostid>B</hostid> starts, <hostid>A</hostid>
             has sent 3 LCP REQs. We are assuming the line has ECHO switched
             off, otherwise we would see magic number problems as described in
             the previous section. <hostid>B</hostid> sends a
             REQ, then an ACK to the first of
             <hostid>A</hostid>'s REQs. This results in
             <hostid>A</hostid> entering the <acronym>OPENED</acronym>
             state and sending and ACK (the first) back to
             <hostid>B</hostid>. In the meantime,
             <hostid>B</hostid> sends back two more ACKs in response to
             the two additional REQs sent by <hostid>A</hostid>
             before <hostid>B</hostid> started up.
             <hostid>B</hostid> then receives the first ACK from
             <hostid>A</hostid> and enters the
             <acronym>OPENED</acronym> state.
             <hostid>A</hostid> receives the second ACK from
             <hostid>B</hostid> and goes back to the
             <acronym>REQ-SENT</acronym> state, sending another (forth) REQ
             as per the RFC. It then receives the third ACK and enters the
             <acronym>OPENED</acronym> state. In the meantime,
             <hostid>B</hostid> receives the forth REQ from
             <hostid>A</hostid>, resulting in it reverting to the
             <acronym>ACK-SENT</acronym> state and sending
             another (second) REQ and (forth) ACK as per the RFC.
             <hostid>A</hostid> gets the REQ, goes into
             <acronym>REQ-SENT</acronym> and sends another REQ. It
             immediately receives the following ACK and enters
             <acronym>OPENED</acronym>.</para>
 
           <para>This goes on until one side figures out that they are
             getting nowhere and gives up.</para>
 
           <para>The best way to avoid this is to configure one side to be
             <literal>passive</literal> - that is, make one side
             wait for the other to start negotiating.  This can be done
             with the</para>
 
           <programlisting>set openmode passive</programlisting>
 
           <para>command.  Care should be taken with this option.  You
             should also use the</para>
 
           <programlisting>set stopped N</programlisting>
 
           <para>command to limit the amount of time that
             &man.ppp.8; waits for the peer to begin
             negotiations.  Alternatively, the</para>
 
           <programlisting>set openmode active N</programlisting>
 
           <para>command (where <replaceable>N</replaceable> is the
             number of seconds to wait before starting negotiations) can be
             used.  Check the manual page for details.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-lockups">
           <para>Why does &man.ppp.8; lock up shortly after connection?</para>
         </question>
 
         <answer>
           <para>Prior to version 2.2.5 of FreeBSD, it was possible that
             your link was disabled shortly after connection due to
             &man.ppp.8; mis-handling Predictor1
             compression negotiation. This would only happen if both sides
             tried to negotiate different Compression Control Protocols
             (CCP). This problem is now corrected, but if you are still
             running an old version of &man.ppp.8;
             the problem can be circumvented with the line</para>
 
           <programlisting>disable pred1</programlisting>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-shell-test-lockup">
           <para>Why does &man.ppp.8; lock up when I shell out to test it?</para>
         </question>
 
         <answer>
           <para>When you execute the <command>shell</command> or
             <command>!</command> command, &man.ppp.8; executes a
             shell (or if you have passed any arguments,
             &man.ppp.8; will execute those arguments). Ppp will
             wait for the command to complete before continuing. If you
             attempt to use the PPP link while running the command, the link
             will appear to have frozen. This is because
             &man.ppp.8; is waiting for the command to
             complete.</para>
 
           <para>If you wish to execute commands like this, use the
             <command>!bg</command> command instead.  This will execute
             the given command in the background, and &man.ppp.8; can continue to
             service the link.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-nullmodem">
           <para>Why does &man.ppp.8; over a null-modem cable never exit?</para>
         </question>
 
         <answer>
           <para>There is no way for &man.ppp.8; to
             automatically determine that a direct connection has been
             dropped.  This is due to the lines that are used in a
             null-modem serial cable.  When using this sort of connection,
             LQR should always be enabled with the line</para>
 
           <programlisting>enable lqr</programlisting>
 
           <para>LQR is accepted by default if negotiated by the peer.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-auto-noreasondial">
           <para>Why does &man.ppp.8; dial for no reason in -auto mode?</para>
         </question><answer>
 
           <para>If &man.ppp.8; is dialing
             unexpectedly, you must determine the cause, and set up Dial
             filters (dfilters) to prevent such dialing.</para>
 
           <para>To determine the cause, use the following line:</para>
 
           <programlisting>set log +tcp/ip</programlisting>
 
           <para>This will log all traffic through the connection.  The
             next time the line comes up unexpectedly, you will see the
             reason logged with a convenient timestamp next to it.</para>
 
           <para>You can now disable dialing under these circumstances.
             Usually, this sort of problem arises due to DNS lookups.  To
             prevent DNS lookups from establishing a connection (this will
             <emphasis>not</emphasis> prevent
             &man.ppp.8; from passing the packets
             through an established connection), use the following:</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>This is not always suitable, as it will effectively break
             your demand-dial capabilities - most programs will need a DNS
             lookup before doing any other network related things.</para>
 
           <para>In the DNS case, you should try to determine what is
             actually trying to resolve a host name.  A lot of the time,
             &man.sendmail.8; is the culprit.  You should make sure that
             you tell sendmail not to do any DNS lookups in its
             configuration file.  See the section on
             <link linkend="ispmail">Mail Configuration</link> for details
             on how to create your own configuration file and what should
             go into it.  You may also want to add the following line to
             your <filename>.mc</filename> file:</para>
 
           <programlisting>define(`confDELIVERY_MODE', `d')dnl</programlisting>
 
           <para>This will make sendmail queue everything until the queue
             is run (usually, sendmail is invoked with
             <option>-bd -q30m</option>, telling it to run the queue every
             30 minutes) or until a <command>sendmail -q</command> is done
             (perhaps from your ppp.linkup file).</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ccp-errors">
           <para>What do these CCP errors mean?</para>
         </question>
 
         <answer>
           <para>I keep seeing the following errors in my log file:</para>
 
           <programlisting>CCP: CcpSendConfigReq
 CCP: Received Terminate Ack (1) state = Req-Sent (6)</programlisting>
 
           <para>This is because &man.ppp.8; is trying to negotiate Predictor1
             compression, and the peer does not want to negotiate any
             compression at all.  The messages are harmless, but if you
             wish to remove them, you can disable Predictor1 compression
             locally too:</para>
 
           <programlisting>disable pred1</programlisting>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-lockup-ioerrors">
           <para>Why does &man.ppp.8; lock up during file transfers with IO
             errors?</para>
         </question>
 
         <answer>
           <para>Under FreeBSD 2.2.2 and before, there was a bug in the
             tun driver that prevents incoming packets of a size larger
             than the tun interface's MTU size.  Receipt of a packet
             greater than the MTU size results in an IO error being logged
             via syslogd.</para>
 
           <para>The PPP specification says that an MRU of 1500 should
             <emphasis>always</emphasis> be accepted as a minimum,
             despite any LCP negotiations, therefore it is possible that
             should you decrease the MTU to less than 1500, your ISP will
             transmit packets of 1500 regardless, and you will tickle this
             non-feature - locking up your link.</para>
 
           <para>The problem can be circumvented by never setting an MTU of
             less than 1500 under FreeBSD 2.2.2 or before.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-connectionspeed">
           <para>Why does &man.ppp.8; not log my connection speed?</para>
         </question>
 
         <answer>
 
           <para>In order to log all lines of your modem
             <quote>conversation</quote>, you must enable the
             following:</para>
 
           <programlisting>set log +connect</programlisting>
 
           <para>This will make &man.ppp.8; log
             everything up until the last requested <quote>expect</quote>
             string.</para>
 
           <para>If you wish to see your connect speed and are using PAP
             or CHAP (and therefore do not have anything to
             <quote>chat</quote> after the CONNECT in the dial script - no
             <literal>set login</literal> script), you must make sure that
             you instruct &man.ppp.8; to <quote>expect</quote> the whole CONNECT
             line, something like this:</para>
 
           <programlisting>set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 4 \
   \"\" ATZ OK-ATZ-OK ATDT\\T TIMEOUT 60 CONNECT \\c \\n"</programlisting>
 
           <para>Here, we get our CONNECT, send nothing, then expect a
             line-feed, forcing &man.ppp.8; to read
             the whole CONNECT response.</para>
 
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-ignores-backslash">
           <para>Why does &man.ppp.8; ignore the <literal>\</literal> character
             in my chat script?</para>
         </question><answer>
 
           <para>Ppp parses each line in your config files so that it can
             interpret strings such as
             <literal>set phone "123 456 789"</literal> correctly (and
             realize that the number is actually only
             <emphasis>one</emphasis> argument. In order to specify a
             <literal>&quot;</literal> character, you must escape it
             using a backslash (<literal>\</literal>).</para>
 
           <para>When the chat interpreter parses each argument, it
             re-interprets the argument in order to find any special
             escape sequences such as <literal>\P</literal> or
             <literal>\T</literal> (see the man page).  As a result of this
             double-parsing, you must remember to use the correct number of
             escapes.</para>
 
           <para>If you wish to actually send a <literal>\</literal>
             character to (say) your modem, you would need something
             like:</para>
 
           <programlisting>set dial "\"\" ATZ OK-ATZ-OK AT\\\\X OK"</programlisting>
 
           <para>resulting in the following sequence:</para>
 
           <programlisting>ATZ
 OK
 AT\X
 OK</programlisting>
 
           <para>or</para>
 
           <programlisting>set phone 1234567
 set dial "\"\" ATZ OK ATDT\\T"</programlisting>
 
           <para>resulting in the following sequence:</para>
 
           <programlisting>ATZ
 OK
 ATDT1234567</programlisting>
 
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-segfault-nocore">
           <para>Why does &man.ppp.8; get a seg-fault, but I see no
             <filename>ppp.core</filename> file?</para>
         </question>
 
         <answer>
           <para>Ppp (or any other program for that matter) should never
             dump core.  Because &man.ppp.8; runs with an effective user id of 0,
             the operating system will not write &man.ppp.8;'s core image to disk
             before terminating it.  If, however &man.ppp.8;
             is actually terminating due to a
             segmentation violation or some other signal that normally
             causes core to be dumped, <emphasis>and</emphasis>
             you are sure you are using the latest version (see the start of
             this section), then you should do the following:</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>You will now have a debuggable version of &man.ppp.8; installed.
             You will have to be <username>root</username> to run &man.ppp.8; as all of its privileges
             have been revoked.  When you start &man.ppp.8;, take a careful note
             of what your current directory was at the time.</para>
 
           <para>Now, if and when &man.ppp.8; receives the segmentation violation,
             it will dump a core file called <filename>ppp.core</filename>.  You should then do
             the following:</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>All of this information should be given alongside your
             question, making it possible to diagnose the problem.</para>
 
           <para>If you are familiar with gdb, you may wish to find out some
             other bits and pieces such as what actually caused the dump and
             the addresses &amp; values of the relevant variables.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-autodialprocess-noconnect">
           <para>Why does the process that forces a dial in auto mode never
             connect?</para>
         </question>
 
         <answer>
           <para>This was a known problem with
             &man.ppp.8; set up to negotiate a
             dynamic local IP number with the peer in auto mode.  It is
             fixed in the latest version - search the man page for
             <literal>iface</literal>.</para>
 
           <para>The problem was that when that initial program calls
             &man.connect.2;, the IP number of the tun interface is assigned
             to the socket endpoint. The kernel creates the first outgoing
             packet and writes it to the tun device.
             &man.ppp.8; then reads the packet and
             establishes a connection. If, as a result of
             &man.ppp.8;'s dynamic IP assignment, the
             interface address is changed, the original socket endpoint will
             be invalid. Any subsequent packets sent to the peer will
             usually be dropped. Even if they are not, any responses will
             not route back to the originating machine as the IP number is
             no longer owned by that machine.</para>
 
           <para>There are several theoretical ways to approach this
             problem. It would be nicest if the peer would re-assign the
             same IP number if possible <literal>:-)</literal>
             The current version of &man.ppp.8; does
             this, but most other implementations do not.</para>
 
           <para>The easiest method from our side would be to never change
             the tun interface IP number, but instead to change all outgoing
             packets so that the source IP number is changed from the
             interface IP to the negotiated IP on the fly. This is
             essentially what the <literal>iface-alias</literal> option in
             the latest version of &man.ppp.8; is
             doing (with the help of
             &man.libalias.3; and &man.ppp.8;'s <option>-nat</option> switch) -
             it is maintaining all previous interface addresses and NATing
             them to the last negotiated address.</para>
 
           <para>Another alternative (and probably the most reliable) would
             be to implement a system call that changes all bound sockets
             from one IP to another.  &man.ppp.8; would
             use this call to modify the sockets of all existing programs
             when a new IP number is negotiated. The same system call could
             be used by dhcp clients when they are forced to re-bind() their
             sockets.</para>
 
           <para>Yet another possibility is to allow an interface to be
             brought up without an IP number. Outgoing packets would be
             given an IP number of 255.255.255.255 up until the first
             SIOCAIFADDR ioctl is done. This would result in fully binding
             the socket. It would be up to &man.ppp.8;
             to change the source IP number, but only if it is set to
             255.255.255.255, and only the IP number and IP checksum would
             need to change. This, however is a bit of a hack as the kernel
             would be sending bad packets to an improperly configured
             interface, on the assumption that some other mechanism is
             capable of fixing things retrospectively.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ppp-nat-games">
           <para>Why do most games not work with the -nat switch?</para>
         </question>
 
         <answer>
           <para>The reason games and the like do not work when libalias
             is in use is that the machine on the outside will try to open a
             connection or send (unsolicited) UDP packets to the machine on
             the inside. The NAT software does not know that it should send
             these packets to the interior machine.</para>
 
           <para>To make things work, make sure that the only thing
             running is the software that you are having problems with, then
             either run tcpdump on the tun interface of the gateway or
             enable &man.ppp.8; tcp/ip logging (<literal>set log +tcp/ip</literal>)
             on the gateway.</para>
 
           <para>When you start the offending software, you should see
             packets passing through the gateway machine. When something
             comes back from the outside, it will be dropped (that is the
             problem). Note the port number of these packets then shut down
             the offending software. Do this a few times to see if the port
             numbers are consistent. If they are, then the following line in
             the relevant section of <filename>/etc/ppp/ppp.conf</filename> will make the
             software functional:</para>
 
           <programlisting>nat port <replaceable>proto</replaceable> <replaceable>internalmachine</replaceable>:<replaceable>port</replaceable> <replaceable>port</replaceable></programlisting>
 
           <para>where <replaceable>proto</replaceable> is either
             <literal>tcp</literal> or <literal>udp</literal>,
             <replaceable>internalmachine</replaceable> is the machine that
             you want the packets to be sent to and
             <replaceable>port</replaceable> is the destination port number
             of the packets.</para>
 
           <para>You will not be able to use the software on other machines
             without changing the above command, and running the software
             on two internal machines at the same time is out of the question
             - after all, the outside world is seeing your entire internal
             network as being just a single machine.</para>
 
           <para>If the port numbers are not consistent, there are three
             more options:</para>
 
           <orderedlist>
             <listitem>
           <para>Submit support in
             libalias. Examples of <quote>special cases</quote> can be found
             in <filename>/usr/src/lib/libalias/alias_*.c</filename>
             (<filename>alias_ftp.c</filename> is a good prototype). This
             usually involves reading certain recognised outgoing packets,
             identifying the instruction that tells the outside machine to
             initiate a connection back to the internal machine on a
             specific (random) port and setting up a <quote>route</quote> in
             the alias table so that the subsequent packets know where to
             go.</para>
 
           <para>This is the most difficult solution, but it is the best
             and will make the software work with multiple machines.</para>
             </listitem>
 
             <listitem>
               <para>Use a proxy.  The
             application may support socks5 for example, or (as in the
             <quote>cvsup</quote> case) may have a <quote>passive</quote>
             option that avoids ever requesting that the peer open
             connections back to the local machine.</para>
             </listitem>
 
             <listitem>
           <para>Redirect everything to
             the internal machine using <literal>nat addr</literal>.  This
             is the sledge-hammer approach.</para>
             </listitem>
           </orderedlist>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="useful-port-numbers">
           <para>Has anybody made a list of useful port numbers?</para>
         </question><answer>
 
           <para>Not yet, but this is intended to grow into such a list
             (if any interest is shown).  In each example,
             <replaceable>internal</replaceable> should be replaced with
             the IP number of the machine playing the game.</para>
 
           <itemizedlist>
             <listitem>
               <para><application>Asheron's Call</application></para>
 
               <para><literal>nat port udp
                 <replaceable>internal</replaceable>
                 :65000 65000</literal></para>
 
               <para>Manually change the port number within the game to
                 65000. If you have got a number of machines that you wish
                 to play on assign a unique port number for each (i.e.
                 65001, 65002, etc) and add a <literal>nat port</literal>
                 line for each one.</para>
             </listitem>
 
             <listitem>
               <para><application>Half Life</application></para>
 
               <para><literal>nat port udp
                 <replaceable>internal</replaceable>:27005
                 27015</literal></para>
             </listitem>
 
             <listitem>
               <para><application>PCAnywhere 8.0</application></para>
 
               <para><literal>nat port udp
                 <replaceable>internal</replaceable>:5632
                 5632</literal></para>
 
               <para><literal>nat port tcp
                 <replaceable>internal</replaceable>:5631
                 5631</literal></para>
             </listitem>
 
             <listitem>
               <para><application>Quake</application></para>
 
               <para><literal>nat port udp
                 <replaceable>internal</replaceable>:6112
                 6112</literal></para>
 
               <para>Alternatively, you may want to take a look at <ulink
                 URL="http://www.battle.net/support/proxy/">
                 www.battle.net</ulink> for Quake proxy support.</para>
             </listitem>
 
             <listitem>
               <para><application>Quake 2</application></para>
 
               <para><literal>nat port udp
                 <replaceable>internal</replaceable>:27901
                 27910</literal></para>
               <para><literal>nat port udp
                 <replaceable>internal</replaceable>:60021
                 60021</literal></para>
               <para><literal>nat port udp
                 <replaceable>internal</replaceable>:60040
                 60040</literal></para>
             </listitem>
 
             <listitem>
               <para><application>Red Alert</application></para>
 
               <para><literal>nat port udp
                 <replaceable>internal</replaceable>:8675
                 8675</literal></para>
 
               <para><literal>nat port udp
                 <replaceable>internal</replaceable>:5009
                 5009</literal></para>
             </listitem>
           </itemizedlist>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="fcs-errors">
           <para>What are FCS errors?</para>
         </question>
 
         <answer>
           <para>FCS stands for <literal>F</literal>rame
             <literal>C</literal>heck
             <literal>S</literal>equence.  Each PPP packet
             has a checksum attached to ensure that the data being
             received is the data being sent.  If the FCS of an incoming
             packet is incorrect, the packet is dropped and the HDLC FCS
             count is increased.  The HDLC error values can be displayed
             using the <literal>show hdlc</literal> command.</para>
 
           <para>If your link is bad (or if your serial driver is dropping
             packets), you will see the occasional FCS error.  This is not
             usually worth worrying about although it does slow down the
             compression protocols substantially.  If you have an external
             modem, make sure your cable is properly shielded from
             interference - this may eradicate the problem.</para>
 
           <para>If your link freezes as soon as you have connected and you
             see a large number of FCS errors, this may be because your link
             is not 8 bit clean. Make sure your modem is not using software
             flow control (XON/XOFF). If your datalink
             <emphasis>must</emphasis> use software flow control, use the
             command <literal>set accmap 0x000a0000</literal> to tell
             &man.ppp.8; to escape the <literal>^Q</literal> and
             <literal>^S</literal> characters.</para>
 
           <para>Another reason for seeing too many FCS errors may be that
             the remote end has stopped talking <acronym>PPP</acronym>. You
             may want to enable <literal>async</literal> logging at this
             point to determine if the incoming data is actually a login or
             shell prompt. If you have a shell prompt at the remote end,
             it is possible to terminate &man.ppp.8; without dropping the line by
             using the <literal>close lcp</literal> command (a following
             <literal>term</literal> command will reconnect you to the shell
             on the remote machine.</para>
 
           <para>If nothing in your log file indicates why the link might
             have been terminated, you should ask the remote administrator
             (your ISP?) why the session was terminated.</para>
         </answer>
       </qandaentry>
 
       <qandaentry id=PPPoEwithNAT>
         <question id="macos-win98-pppoe-freeze">
           <para>Why do MacOS and Windows 98 connections freeze when
             running PPPoE on the gateway?</para>
         </question>
 
         <answer>
           <para>Thanks to Michael Wozniak
             <email>mwozniak@netcom.ca</email> for figuring this out and
             Dan Flemming <email>danflemming@mac.com</email> for the Mac
             solution:</para>
 
           <para>This is due to what is called a <quote>Black Hole</quote>
             router.  MacOS and Windows 98 (and maybe other Microsoft OSs)
             send TCP packets with a requested segment size too big to fit
             into a PPPoE frame (MTU is 1500 by default for Ethernet)
             <emphasis>and</emphasis> have the <quote>do not
             fragment</quote> bit set (default of TCP) and the Telco router
             is not sending ICMP <quote>must fragment</quote> back to the
             www site you are trying to load.  (Alternatively, the router is
             sending the ICMP packet correctly, but the firewall at the www
             site is dropping it.)  When the www server is sending
             you frames that do not fit into the PPPoE pipe the Telco router
             drops them on the floor and your page does not load (some
             pages/graphics do as they are smaller than a MSS.) This seems
             to be the default of most Telco PPPoE configurations (if only
             they knew how to program a router... sigh...)</para>
 
           <para>One fix is to use regedit on your 95/98 boxes to add the
             following registry entry...</para>
 
           <programlisting>HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\NetTrans\0000\MaxMTU</programlisting>
 
           <para>It should be a string with a value <quote>1436</quote>, as
             some ADSL routers are reported to be unable to deal with packets
             larger than this.  This registry key has been changed to
             <literal>Tcpip\Parameters\Interfaces\<replaceable>ID for adapter</replaceable>\MTU</literal>
             in Windows 2000 and becomes a DWORD.</para>
 
           <para>Refer to the Microsoft Knowledge Base documents <ulink
             url="http://support.microsoft.com/support/kb/articles/Q158/4/74.asp">Q158474
             - Windows TCPIP Registry Entries</ulink> and <ulink
             url="http://support.microsoft.com/support/kb/articles/Q120/6/42.asp">Q120642
             - TCPIP & NBT Configuration Parameters for Windows
             NT</ulink> for more information on changing Windows MTU to
             work with a NAT router.</para>
 
           <para>Another regedit possibility under Windows 2000 is to
             set the
             <literal>Tcpip\Parameters\Interfaces\<replaceable>ID for
             adapter</replaceable>\EnablePMTUBHDetect</literal> DWORD
             to 1 as mentioned in the Microsoft document 120642
             mentioned above.</para>
 
           <para>Unfortunately, MacOS does not provide an interface for
             changing TCP/IP settings. However, there is commercial software
             available, such as OTAdvancedTuner (OT for OpenTransport, the
             MacOS TCP/IP stack) by <ulink
             URL="http://www.softworks.com/">Sustainable Softworks</ulink>,
             that will allow users to customize TCP/IP settings. MacOS NAT
             users should select <literal>ip_interface_MTU</literal> from
             the drop-down menu, enter <literal>1450</literal> instead of
             <literal>1500</literal> in the box, click the box next to
             <literal>Save as Auto Configure</literal>, and click
             <literal>Make Active</literal>.</para>
 
           <para>The latest version of &man.ppp.8;
             (2.3 or greater) has an <command>enable tcpmssfixup</command>
             command that will automatically adjust the MSS to an appropriate
             value.  This facility is enabled by default.  If you are stuck
             with an older version of &man.ppp.8;, you
             may want to look at the <application>tcpmssd</application>
             port.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="desperation">
           <para>None of this helps - I am desperate!  What can I do?</para>
         </question>
 
         <answer>
           <para>If all else fails, send as much information as you can,
             including your config files, how you are starting
             &man.ppp.8;, the relevant parts of your
             log file and the output of the <command>netstat -rn</command>
             command (before and after connecting) to the &a.questions; or
             the <ulink URL="news:comp.unix.bsd.freebsd.misc">
             comp.unix.bsd.freebsd.misc</ulink> news group, and someone
             should point you in the right direction.</para>
         </answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter id="serial">
     <title>Serial Communications</title>
 
     <para>This section answers common questions about serial
       communications with FreeBSD.  PPP and SLIP are covered in the
       <xref linkend="networking" remap="Networking"> section.</para>
 
 
     <qandaset>
       <qandaentry>
         <question id="found-serial">
           <para>How do I tell if FreeBSD found my serial ports?</para>
         </question>
 
         <answer>
           <para>As the FreeBSD kernel boots, it will probe for the serial
             ports in your system for which the kernel was configured.
             You can either watch your system closely for the messages it
             prints or run the command</para>
 
           <screen>&prompt.user; <userinput>dmesg | grep sio</userinput></screen>
 
           <para>after your system is up and running.</para>
 
           <para>Here is some example output from the above command:</para>
 
           <programlisting>sio0 at 0x3f8-0x3ff irq 4 on isa
 sio0: type 16550A
 sio1 at 0x2f8-0x2ff irq 3 on isa
 sio1: type 16550A</programlisting>
 
           <para>This shows two serial ports.  The first is on irq 4, is
             using port address <literal>0x3f8</literal>, and has a
             16550A-type UART chip.  The second uses the same kind of chip
             but is on irq 3 and is at port address <literal>0x2f8</literal>.
             Internal modem cards are treated just like serial ports---except
             that they always have a modem <quote>attached</quote> to the
             port.</para>
 
           <para>The <filename>GENERIC</filename> kernel includes support
             for two serial ports using the same irq and port address
             settings in the above example.  If these settings are not
             right for your system, or if you have added modem cards or have
             more serial ports than your kernel is configured for, just
             reconfigure your kernel.  See section
             <link linkend="make-kernel">about building a kernel</link> for
             more details.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="found-modem">
           <para>How do I tell if FreeBSD found my modem cards?</para>
         </question>
 
         <answer>
           <para>Refer to the answer to the previous question.</para>
 
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="missing-tty0X">
           <para>I just upgraded to 2.0.5 and my
             <devicename>tty0<replaceable>X</replaceable></devicename>
             are missing!  How do I solve this problem?</para>
         </question>
 
         <answer>
           <para>Do not worry, they have been merged with the
             <devicename>ttyd<replaceable>X</replaceable></devicename> devices. You will have to change
             any old configuration files you have, though.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="access-serial-ports">
           <para>How do I access the serial ports on FreeBSD?</para>
         </question>
 
         <answer>
           <para>The third serial port,
             <devicename>sio2</devicename>
             (see &man.sio.4;, known as COM3 in DOS), is on <devicename>/dev/cuaa2</devicename>
             for dial-out devices, and on <devicename>/dev/ttyd2</devicename>
             for dial-in devices.  What is the difference between these two
             classes of devices?</para>
 
           <para>You use <devicename>ttyd<replaceable>X</replaceable></devicename> for dial-ins.  When
             opening <devicename>/dev/ttyd<replaceable>X</replaceable></devicename> in blocking mode, a
             process will wait for the corresponding
             <devicename>cuaa<replaceable>X</replaceable></devicename> device to become inactive, and then
             wait for the carrier detect line to go active.  When you open
             the <devicename>cuaa<replaceable>X</replaceable></devicename> device, it makes sure the serial
             port is not already in use by the <devicename>ttyd<replaceable>X</replaceable></devicename>
             device. If the port is available, it <quote>steals</quote> it
             from the <devicename>ttyd<replaceable>X</replaceable></devicename> device. Also, the
             <devicename>cuaa<replaceable>X</replaceable></devicename> device does not care about carrier
             detect. With this scheme and an auto-answer modem, you can have
             remote users log in and you can still dial out with the same
             modem and the system will take care of all the
             conflicts.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="enable-multiport-serial">
           <para>How do I enable support for a multiport serial
             card?</para>
         </question>
 
         <answer>
           <para>Again, the section on kernel configuration provides
             information about configuring your kernel. For a multiport
             serial card, place an &man.sio.4; line
             for each serial port on the card in the kernel configuration
             file. But place the irq and vector specifiers on only one of
             the entries. All of the ports on the card should share one irq.
             For consistency, use the last serial port to specify the irq.
             Also, specify the <literal>COM_MULTIPORT</literal>
             option.</para>
 
           <para>The following example is for an AST 4-port serial card on
             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>The flags indicate that the master port has minor number 7
             (<literal>0x700</literal>), diagnostics enabled during probe
             (<literal>0x080</literal>), and all the ports share an irq
             (<literal>0x001</literal>).</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="multiport-serial-share-irq">
           <para>Can FreeBSD handle multiport serial cards sharing
             irqs?</para>
         </question>
 
         <answer>
           <para>Not yet. You will have to use a different irq for each
             card.</para>
 
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="default-serial-params">
           <para>Can I set the default serial parameters for a
             port?</para>
         </question>
 
         <answer>
           <para>The <devicename>ttyd<replaceable>X</replaceable></devicename> (or
             <devicename>cuaa<replaceable>X</replaceable></devicename>) device is the regular device
             you will want to open for your applications.  When a process
             opens the device, it will have a default set of terminal I/O
             settings. You can see these settings with the command</para>
 
           <screen>&prompt.root; <userinput>stty -a -f /dev/ttyd1</userinput></screen>
 
           <para>When you change the settings to this device, the settings
             are in effect until the device is closed.  When it is reopened,
             it goes back to the default set.  To make changes to the
             default set, you can open and adjust the settings of the
             <quote>initial state</quote> device. For example, to turn on
             <acronym>CLOCAL</acronym> mode, 8 bits, and
             <acronym>XON/XOFF</acronym> flow control by default for
             ttyd5, do:</para>
 
           <screen>&prompt.root; <userinput>stty -f /dev/ttyid5 clocal cs8 ixon ixoff</userinput></screen>
 
           <para>A good place to do this is in
             <filename>/etc/rc.serial</filename>. Now, an application will
             have these settings by default when it opens
             <filename>ttyd5</filename>.  It can still change these settings
             to its liking, though.</para>
 
           <para>You can also prevent certain settings from being changed
             by an application by making adjustments to the
             <quote>lock state</quote> device.  For example, to lock the
             speed of <devicename>ttyd5</devicename> to 57600 bps, do</para>
 
           <screen>&prompt.root; <userinput>stty -f /dev/ttyld5 57600</userinput></screen>
 
           <para>Now, an application that opens <devicename>ttyd5</devicename>
             and tries to change the speed of the port will be stuck with
           57600 bps.</para>
 
           <para>Naturally, you should make the initial state and lock state
             devices writable only by <username>root</username>. The
             &man.MAKEDEV.8;
             script does <emphasis>NOT</emphasis> do this when it creates the
             device entries.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="enable-dialup">
           <para>How can I enable dialup logins on my modem?</para>
         </question>
 
         <answer>
           <para>So you want to become an Internet service provider, eh?
             First, you will need one or more modems that can auto-answer.
             Your modem will need to assert carrier-detect when it detects a
             carrier and not assert it all the time. It will need to hang up
             the phone and reset itself when the data terminal ready
             (<acronym>DTR</acronym>) line goes from on to off. It should
             probably use <filename>RTS/CTS</filename> flow control or no
             local flow control at all. Finally, it must use a constant
             speed between the computer and itself, but (to be nice to your
             callers) it should negotiate a speed between itself and the
             remote modem.</para>
 
           <para>For many Hayes command-set--compatible modems, this
             command will make these settings and store them in
             nonvolatile memory:</para>
 
           <programlisting>AT &amp;C1 &amp;D3 &amp;K3 &amp;Q6 S0=1 &amp;W</programlisting>
 
           <para>See the section <link linkend="direct-at">on sending AT
             commands</link> below for information on how to make these
             settings without resorting to an MS-DOS terminal program.</para>
 
           <para>Next, make an entry in
             <filename>/etc/ttys</filename> (see &man.ttys.5;) for the modem.  This file lists all the ports
             on which the operating system will await logins.  Add a line
             that looks something like this:</para>
 
           <programlisting>ttyd1 "/usr/libexec/getty std.57600" dialup on insecure</programlisting>
 
           <para>This line indicates that the second serial port
             (<devicename>/dev/ttyd1</devicename>) has a modem connected
             running at 57600 bps and no parity
             (<literal>std.57600</literal>, which comes from the file
             <filename>/etc/gettytab</filename>, see &man.gettytab.5;).
             The terminal type for this port is <literal>dialup</literal>.
             The port is <literal>on</literal> and is
             <literal>insecure</literal>---meaning <username>root</username>
 	    logins on the port are not allowed. For dialin ports like this one,
 	    use the <devicename>ttyd<replaceable>X</replaceable></devicename>
 	    entry.</para>
 
           <para>It is common practice to use <literal>dialup</literal> as
             the terminal type. Many users set up in their <filename>.profile</filename> or
             <filename>.login</filename> files a prompt for the actual terminal type if the
             starting type is dialup. The example shows the port as
             insecure. To become <username>root</username> on this port, you
 	    have to login as a regular user, then &man.su.1; to become
             <username>root</username>. If you use <literal>secure</literal>
             then <username>root</username> can login in directly.</para>
 
           <para>After making modifications to
             <filename>/etc/ttys</filename>, you need to send a hangup or
             <acronym>HUP</acronym> signal to the
             &man.init.8; process:</para>
 
           <screen>&prompt.root; <userinput>kill -HUP 1</userinput></screen>
 
           <para>This forces the &man.init.8; process to reread
             <filename>/etc/ttys</filename>.  The init process will then start getty
             processes on all <literal>on</literal> ports.  You can find
             out if logins are available for your port by typing</para>
 
           <screen>&prompt.user; <userinput>ps -ax | grep '[t]tyd1'</userinput></screen>
 
           <para>You should see something like:</para>
 
           <programlisting>747 ??  I      0:00.04 /usr/libexec/getty std.57600 ttyd1</programlisting>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="dumb-terminal">
           <para>How can I connect a dumb terminal to my FreeBSD
             box?</para>
         </question>
 
         <answer>
           <para>If you are using another computer as a terminal into your
             FreeBSD system, get a null modem cable to go between the two
             serial ports.  If you are using an actual terminal, see its
             accompanying instructions.</para>
 
           <para>Then, modify
             <filename>/etc/ttys</filename> (see &man.ttys.5;), like above.  For example, if you are
             hooking up a WYSE-50 terminal to the fifth serial port,
             use an entry like this:</para>
 
           <programlisting>ttyd4 "/usr/libexec/getty std.38400" wyse50 on secure</programlisting>
 
           <para>This example shows that the port on
             <devicename>/dev/ttyd4</devicename> has a wyse50 terminal
             connected at 38400 bps with no parity
             (<literal>std.38400</literal> from
             <filename>/etc/gettytab</filename>, see &man.gettytab.5;) and <username>root</username> logins are
             allowed (<literal>secure</literal>).</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="cannot-tip">
           <para>Why can I not run <command>tip</command> or
             <command>cu</command>?</para>
         </question>
 
         <answer>
           <para>On your system, the programs &man.tip.1;
             and &man.cu.1;
             are probably executable only by
             <username>uucp</username>
             and group <groupname>dialer</groupname>.  You can use the group
             <groupname>dialer</groupname> to control who has access to your
             modem or remote systems.  Just add yourself to group
             dialer.</para>
 
           <para>Alternatively, you can let everyone on your system
             run &man.tip.1; and &man.cu.1; by
             typing:</para>
 
           <screen>&prompt.root; <userinput>chmod 4511 /usr/bin/cu</userinput>
 &prompt.root; <userinput>chmod 4511 /usr/bin/tip</userinput></screen>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="hayes-unsupported">
           <para>My stock Hayes modem is not supported---what
             can I do?</para>
         </question>
 
         <answer>
           <para>Actually, the man page for &man.tip.1; is
             out of date.  There is a generic Hayes dialer already built in.
             Just use <literal>at=hayes</literal> in your
             <filename>/etc/remote</filename> (see &man.remote.5;) file.</para>
 
           <para>The Hayes driver is not smart enough to recognize some of
             the advanced features of newer modems---messages like
             <literal>BUSY</literal>, <literal>NO DIALTONE</literal>, or
             <literal>CONNECT 115200</literal> will just confuse it. You
             should turn those messages off when you use &man.tip.1;
             (using <literal>ATX0&amp;W</literal>).</para>
 
           <para>Also, the dial timeout for &man.tip.1; is 60
             seconds.  Your modem should use something less, or else tip
             will think there is a communication problem.  Try
             <literal>ATS7=45&amp;W</literal>.</para>
 
           <para>Actually, as shipped &man.tip.1; does not yet
             support it fully. The solution is to edit the file
             <filename>tipconf.h</filename> in the directory
             <filename>/usr/src/usr.bin/tip/tip</filename>.  Obviously you
             need the source distribution to do this.</para>
 
           <para>Edit the line <literal>#define HAYES 0</literal>
             to <literal>#define HAYES 1</literal>. Then
             <command>make</command> and <command>make install</command>.
             Everything works nicely after that.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="direct-at">
           <para>How am I expected to enter these AT commands?</para>
         </question>
 
         <answer>
           <para>Make what is called a <quote>direct</quote> entry in your
             <filename>/etc/remote</filename> file (see &man.remote.5;).  For example, if your modem is hooked
             up to the first serial port, <devicename>/dev/cuaa0</devicename>,
             then put in the following line:</para>
 
           <programlisting>cuaa0:dv=/dev/cuaa0:br#19200:pa=none</programlisting>
 
           <para>Use the highest bps rate your modem supports in the br
             capability.  Then, type
             <command>tip <devicename>cuaa0</devicename></command> (see &man.tip.1;)
             and you will be connected to your modem.</para>
 
           <para>If there is no <devicename>/dev/cuaa0</devicename> on your
             system, do this:</para>
 
           <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>sh MAKEDEV cuaa0</userinput></screen>
 
           <para>Or use cu as <username>root</username> with the following command:</para>
 
           <screen>&prompt.root; <userinput>cu -l<replaceable>line</replaceable> -s<replaceable>speed</replaceable></userinput></screen>
 
           <para>with <replaceable>line</replaceable> being the serial port (e.g.
             <devicename>/dev/cuaa0</devicename>) and <replaceable>speed</replaceable> being the speed
             (e.g.<literal>57600</literal>).  When you are done entering
             the AT commands hit <literal>~.</literal> to exit.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="gt-failure">
           <para>Why does the <literal>&lt;@&gt;</literal> sign for the pn
             capability not work?</para></question><answer>
 
           <para>The <literal>&lt;@&gt;</literal> sign in the phone number
             capability tells tip to look in
             <filename>/etc/phones</filename> for a phone number.  But the
             <literal>&lt;@&gt;</literal> sign is also a special character
             in capability files like <filename>/etc/remote</filename>.
             Escape it with a backslash:</para>
 
           <programlisting>pn=\@</programlisting>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="dial-command-line">
           <para>How can I dial a phone number on the command
             line?</para>
         </question><answer>
 
           <para>Put what is called a <quote>generic</quote> entry in your
             <filename>/etc/remote</filename> file (see &man.remote.5;).  For example:</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>Then you can do something like <command>tip -115200
             5551234</command>.  If you prefer &man.cu.1;
             over
             &man.tip.1;, use a generic cu entry:</para>
 
           <programlisting>cu115200|Use cu to dial any number at 115200bps:\
         :dv=/dev/cuaa1:br#57600:at=hayes:pa=none:du:</programlisting>
 
           <para>and type <command>cu 5551234 -s 115200</command>.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="set-bps">
           <para>Do I have to type in the bps rate every time I do
             that?</para>
         </question><answer>
 
           <para>Put in an entry for <literal>tip1200</literal> or
             <literal>cu1200</literal>, but go ahead and use whatever bps
             rate is appropriate with the br capability.
             &man.tip.1;
             thinks a good default is 1200 bps which is why it looks for
             a <literal>tip1200</literal> entry. You do not have to use 1200
             bps, though.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="terminal-server">
           <para>How can I more easily access a number of hosts through a
             terminal server?</para>
         </question>
 
         <answer>
           <para>Rather than waiting until you are connected and typing
             <literal>CONNECT <replaceable>host</replaceable></literal>
             each time, use tip's <literal>cm</literal> capability. For
             example, these entries in
             <filename>/etc/remote</filename> (see &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>will let you type <command>tip pain</command> or
             <command>tip muffin</command> to connect to the hosts
             <hostid>pain</hostid> or <hostid>muffin</hostid>; and
             <command>tip deep13</command> to get to the terminal
             server.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="tip-multiline">
           <para>Can tip try more than one line for each site?</para>
         </question>
 
         <answer>
           <para>This is often a problem where a university has several
             modem lines and several thousand students trying to use
             them...</para>
 
           <para>Make an entry for your university in
             <filename>/etc/remote</filename> (see &man.remote.5;) and use <literal>&lt;\@&gt;</literal> for
             the <literal>pn</literal> capability:</para>
 
           <programlisting>big-university:\
         :pn=\@:tc=dialout
 dialout:\
         :dv=/dev/cuaa3:br#9600:at=courier:du:pa=none:</programlisting>
 
           <para>Then, list the phone numbers for the university in
             <filename>/etc/phones</filename> (see &man.phones.5;):</para>
 
           <programlisting>big-university 5551111
 big-university 5551112
 big-university 5551113
 big-university 5551114</programlisting>
 
           <para>&man.tip.1;
             will try each one in the listed order, then give
             up.  If you want to keep retrying, run &man.tip.1;
             in a while loop.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="multi-controlp">
           <para>Why do I have to hit CTRL+P twice to send CTRL+P
             once?</para>
         </question>
 
         <answer>
           <para>CTRL+P is the default <quote>force</quote> character,
             used to tell &man.tip.1;
             that the next character is literal data.  You can set the
             force character to any other character with the
             <literal>~s</literal> escape, which means <quote>set a
             variable</quote>.</para>
 
           <para>Type <literal>~sforce=<replaceable>single-char
             </replaceable></literal> followed by a newline.
             <replaceable>single-char</replaceable> is any single character.
             If you leave out <replaceable>single-char</replaceable>,
             then the force character is the nul character, which you can
             get by typing CTRL+2 or CTRL+SPACE.  A pretty good value for
             <replaceable>single-char</replaceable> is SHIFT+CTRL+6, which
             I have seen only used on some terminal servers.</para>
 
           <para>You can have the force character be whatever you want by
             specifying the following in your
             <filename>$HOME/.tiprc</filename> file:</para>
 
           <programlisting>force=<replaceable>single-char</replaceable></programlisting>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="uppercase">
           <para>Why is everything I type suddenly in UPPER CASE?</para>
         </question>
 
         <answer>
           <para>You must have pressed CTRL+A, &man.tip.1;
             <quote>raise character</quote>, specially
             designed for people with broken caps-lock keys. Use
             <literal>~s</literal> as above and set the variable
             <quote>raisechar</quote> to something reasonable.  In fact,
             you can set it to the same as the force character, if you
             never expect to use either of these features.</para>
 
           <para>Here is a sample .tiprc file perfect for Emacs users who
             need to type CTRL+2 and CTRL+A a lot:</para>
 
           <programlisting>force=^^
 raisechar=^^</programlisting>
 
 <para>The ^^ is SHIFT+CTRL+6.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="tip-filetransfer">
           <para>How can I do file transfers with
             <command>tip</command>?</para>
         </question>
 
         <answer>
           <para>If you are talking to another Unix system, you can send
             and receive files with <literal>~p</literal> (put) and
             <literal>~t</literal> (take).  These commands run
             &man.cat.1; and
             &man.echo.1; on the remote system to accept and send files.
             The syntax is:</para>
 
           <programlisting>~p &lt;local-file&gt; [&lt;remote-file&gt;]
 ~t &lt;remote-file&gt; [&lt;local-file&gt;]</programlisting>
 
           <para>There is no error checking, so you probably should use
             another protocol, like zmodem.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="zmodem-tip">
           <para>How can I run zmodem with
             <application>tip</application>?</para>
         </question>
 
         <answer>
           <para>First, install one of the zmodem programs from the
             ports collection (such as one of the two from the comms
             category, <application>lrzsz</application> or
             <application>rzsz</application>.</para>
 
           <para>To receive files, start the sending program on the
             remote end.  Then, press enter and type
             <literal>~C rz</literal> (or <literal>~C lrz</literal> if you
             installed <application>lrzsz</application>) to begin
             receiving them locally.</para>
 
           <para>To send files, start the receiving program on the remote
             end.  Then, press enter and type
             <literal>~C sz <replaceable>files</replaceable></literal>
             (or <literal>~C lsz <replaceable>files</replaceable></literal>)
             to send them to the remote system.</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="cannot-find-serial">
           <para>Why does FreeBSD not find my serial ports, even
             when the settings are correct?</para>
         </question>
 
         <answer>
           <para>Motherboards and cards with Acer UARTs do not probe
             properly under the FreeBSD sio probe.  Obtain a patch from
             <ulink URL="http://www.lemis.com/serial-port-patch.html">
             www.lemis.com</ulink> to fix your problem.</para>
         </answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter id="misc">
     <title>¨ä¥¦¦U¦¡¦U¼Ëªº°ÝÃD</title>
 
     <qandaset>
       <qandaentry>
         <question id="more-swap">
           <para>¬°¬Æ»ò FreeBSD ¥Îªº¸m´«(swap)ªÅ¶¡¤ñ Linux ¦h¡H</para>
         </question>
 
         <answer>
           <para>FreeBSD¶È¬O¬Ý°_¨Ó¸m´«ªÅ¶¡(swap)¥Îªº¤ñLinux¦h¦Ó¤w¡C¦b¨Æ¹ê¤W¡A
             ¨Ã¤£µM¡C¥D­nªº®t²§¬O¦b©ó¡AFreeBSD¿n·¥ªº±N¶¢¸mµL¥Îªº¥D°O¾ÐÅ餺®e
             ±À¤J¸m´«ªÅ¶¡(swap)¤¤¡A¥H¨Ï±o¥D°O¾ÐÅé¥i¥H§ó¬°¦³®Ä²vªº³Q¨Ï¥Î¡C¦Ó
             Linuxªºµ¦²¤¬O±N¸m´«ªÅ¶¡(swap)¥Î¨Ó§@¬°¸Ñ¨M°O¾ÐÅé°ÝÃDªº³Ì²×¤â¬q¡C
             ¸ûÀWÁcªº¨Ï¥Î¸m´«ªÅ¶¡(swap)¡C¬O¤@ºØ§ó¦³®Ä²vªº¨Ï¥Î¥D°O¾ÐÅ骺¤â¬q¡C
 	    </para>
 
           <para>µù¡G·í¤@¤è­±FreeBSD¿n·¥ªº¨Ï¥Î¸m´«ªÅ¶¡(swap)ªº¦P®É¡A§A¥²»Ýª`
             ·N¨ì¡AFreeBSD¨Ã¤£·|¥ô·Nªº±N©Ò¦³ªºªF¦è³£±À¤J¸m´«ªÅ¶¡(swap)¤¤¡C¦p¦¹¡A
             §A¤~¤£·|¦b¤@©]±J¾K°_§É«áµo²{¡A¾ã­Ó¨t²Î³£³Q­Ë¶i¤F¸m´«ªÅ¶¡(swap)¤§¤¤¡C
 	    </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="top-freemem">
           <para>§Y¨Ï§Ú¥u¦³¹B¦æ¤Ö¼Æµ{¦¡¡A¬°¤°»ò <command>top</command> Åã¥Ü¥X
 	    ¨Óªº³Ñ¾l°O¾ÐÅéÁÙ¬O«Ü¤Ö¡H</para>
         </question>
 
         <answer>
           <para>²³æªºµª®×¬O¡A©Ò¦³¥¼¨Ï¥Î¨ìªº¶¢¸m°O¾ÐÅé³£¬O³Q®ö¶Oªº°O¾ÐÅé¡A
             ¥ô¦ó¥¼³Q§Aªºµ{¦¡©Ò§Q¥Î¨ìªº°O¾ÐÅé±N³Q®Ö¤ß(kernel)¥Î¨Ó·í
             §@ºÏºÐ§Ö¨ú(disk cache)¡C¦Ó³oºØ°O¾ÐÅé³Q &man.top.1; ¼Ð°O¬°
             <literal>¶¢¸mªº(Inact)</literal>¡A<literal>§Ö¨ú(Cache)</literal>¡A
             ¥H¤Î <literal>½w½Ä°Ï(Buf)</literal>¡A¨Ã­t³d¦b¦U­Ó¤£¦Pªº¦ì¸m­t³d
             ¼È¦s¸ê®Æ¡C³Q¼È¦s(cached)ªº¸ê®Æ¥Nªí¨t²Î¤£»Ý­n¥h¦s¨ú¸ûºCªººÏºÐ¸Ë¸m
             ´N¥i¥H±o¨ì¸ê®Æ¡A¦p¦¹¡A¥i¥H´£¤É¨t²Îªº®Ä¯à¡CÁ`¦Ó¨¥¤§¡A&man.top.1;
             Åã¥Ü¥X¸û¤Öªº <literal>¶¢¸m(Free)</literal> °O¾ÐÅé¬O¦nªº¡A¥u­nÅã¥Ü
             ¥X¨Óªº­È¤£¬O <literal>«D±`</literal> ªº§C¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="aout-elf">
           <para>¬°¬Æ»ò­n¥Î(¬Æ»ò¬O) a.out ©M ELF °õ¦æÀɮ榡¡H</para>
         </question>
 
         <answer>
           <para>­n¤F¸Ñ¬°¤°»òFreebsd¨Ï¥Î <filename>ELF</filename> ®æ¦¡¡A§A¦³¥²
 	    ­n¥ý»{ÃѤ@¤U¤TºØ¦b¥Ø«e Unix ¨t²Î¤¤³Ì³Q¼sªxÀ³¥Î¨ìªº°õ¦æÀɮ榡¡G
 	    </para>
 
             <note>
               <para>¦b FreeBSD 3.x ¤§«e¡AFreeBSD ¨Ï¥Î a.out ®æ¦¡¡C</para>
             </note>
 
             <itemizedlist>
               <listitem>
                 <para>&man.a.out.5;</para>
 
                 <para>³o¬O³Ì¦­¡A¦P¬O¤]¬O <quote>³Ì¨å«¬</quote> ªºUnix¥ØªºÀÉ
 		  ®æ¦¡¡C³oºØ®æ¦¡ªºÀɮרϥΤ@ºØµu¥Bºò±KªºÀÉÀY¡A¦P®É¡A¦ñÀHµÛ¤@
 		  ­ÓÅ]³N¼Æ¦r¥Î¨Ó¿ëÃѮ榡¡C(°Ñ¦Ò &man.a.out.5; ¦³§ó¦h¸Ô²Óªº»¡
 		  ©ú)¡C¥¦¥]§t¦³¤T­Ó¸`°Ï¡G .text .data ¤Î .bss ¥[¤W¤@­Ó²Å¸¹ªí
                   ¤Î¦r¦êªí¡C</para>
               </listitem>
 
               <listitem>
                 <para><acronym>COFF</acronym></para>
 
                 <para>SVR3¥ØªºÀɮ榡¡CÀÉÀY¥]§t¤F¤@­Ó¸`°Ïªí¡A©Ò¥H¥i¥H¨ã³Æ¤ñ
                       .text .data .bss ÁÙ¦hªº¸`°Ï¡C</para>
               </listitem>
 
               <listitem>
                 <para><acronym>ELF</acronym></para>
 
                 <para>ELF¬° <acronym>COFF</acronym> ®æ¦¡ªº«áÄ~ªÌ¡A¥D­nªº¯S¼x¬°
                   ¥i¥H¨ã¦³½Æ¼Æ¸`°Ï¬q¡A¨Ã¥i¥H¨Ï¥Î32-bits©Î¬O64-bitsªº¼Æ­È¡C
                   ¥D­nªº¯ÊÂI¬°¡G <acronym>ELF</acronym> ®æ¦¡¬O¦b¨C­Ó¨t²Î¤¤¥u
                   ·|¦³¤@ºØ ABI ªº°²³]¬°«eÃD³Q³]­p¥X¨Óªº¡C¦ý¬O¡A¦b¨Æ¹ê¤W¡A³o­Ó
                   °²³]¿ùªºÂ÷ÃСC¦]¬°¡AÁa¨Ï¦b°Ó¥Îªº SYSV ¥@¬É¸Ì¡A¤]¦Ü¤Ö¦³ SVR4¡A
                   Solaris ©M SCO ¤TºØ ABI¡C</para>
 
                 <para>Ķµù¡GABI(Application Binary Interface)¡C¦pªG¤@©w­n½Ķ¡A
                  ´N¥s¥¦ <emphasis>À³¥Îµ{¦¡¤G¶i¦ì¤¶­±</emphasis> ¦n¤F¡C ABI³Qµo
 		 ®i¥X¨Óªº¥Î·N¡A¬O¬°¤F«P¨Ï¦b¬Û¦PCPU©Òµo®i¥X¨ÓªºÀ³¥Îµ{¦¡¡A¯à°÷
 		 ¦b¤£¦Pªº¨t²Î¤W¡A§@¨ì¤G¤¸ÀÉ(Binary Code)¬Û®e¡C¤ñ¤è»¡¡A
                  <acronym>Sun</acronym> ©Ò´£¥Xªº <acronym>Solaris ABI</acronym>
 		 ¡A«OÃÒ°õ¦æÀɯà°÷¦b¬Û¦P CPU ªº Solaris ¨t²Î¤W°õ¦æ¡A¥t¤@­Ó¨Ò¤l¬O
                  Windows ¨t²Î¡C¦PÄÝ©ó Intel x86 ª©¥»ªº°õ¦æÀɯà°÷¦Û¥Ñªº¦bWindows
                  9x/me¤ÎWindows NT/2k/XP¤§¶¡°õ¦æ¡C</para>
 
                 <para>FreeBSD´£¨Ñ¤@­Ó¤½¥Îµ{¦¡±Nµ{¦¡©Ò»ÝªºABI¸ê°T¯O¤W¡AÂǦ¹¸ÕµÛ
 		  ¥h¸Ñ¨M³o­Ó°ÝÃD¡C½Ð°Ñ¦Ò &man.brandelf.1; ¥H¨ú±o§ó¦h¸ê°T¡Ci
 		  </para>
               </listitem>
             </itemizedlist>
 
           <para>FreeBSD ¨Ó¦Û <quote>¶Ç²Î</quote> ªº°}Àç¡C¦b¶Ç²Î¤W¡AFreeBSD³£
 	    ¨Ï¥Î &man.a.out.5; ®æ¦¡¡A³o¼Ëªº§Þ³N¦b¦n´X¥Nªº BSD ³£³QÃÒ©ú¬O¥i¾aªº¡C
             ÁöµM¡A¦bFreeBSD¤W¥i¥H«Ø¥ß¥H¤Î¥¿½Tªº°õ¦æ­ì¥Í <acronym>ELF</acronym>
             ®æ¦¡ÀÉ®×(¥]§t®Ö¤ß)¡CµM¦Ó, FreeBSD¦b¤@¶}©l¤Ï¹ï±N¹w³]®æ¦¡Âà´«¬° ELF¡A
             ¬°¤°»ò©O¡H·íLinux¶}©lµh­WªºÂà´«¦Ü <acronym>ELF</acronym> ®æ¦¡®É¡A
             ¨Ã«D¬O¬°¤F­n°kÂ÷ <filename>a.out</filename> ®æ¦¡¡C¬Û¤Ïªº¡A³o¬O¦]
 	    ¬°¤§«e Linuxªº¦@¨É¨ç¦¡®w(shared libraries)±Ä¥Î¥H¸õÅDªí®æ
 	    (jump-table)¬°°ò¦ªº§Þ³N¥h³]­p¡C³o¬O¤@ºØÅýµo®iªÌ·P¨ì§xÂZ¡A¥B«D±`
 	    Ãø¥H¨Ï¥Î¡A¤£¨ã¨¬°÷¼u©Êªº¤èªk¡C¬JµM¡A¤w¸g¦s¦bªº
 	    <acronym>ELF</acronym> ¤u¨ã´£¨Ñ¤F¦@¨É¨ç¦¡®w(shared libraries)ªº¸Ñ
 	    ¨M¤è®×¡A¦Ó¥B¡A¨º¬Ý°_¨Ó¬O­Ó <quote>«e½Ãªº¤èªk</quote>¡A¦]¦¹¡A©Ò»Ý
 	    ªºÂà´«¥N»ù´N¥i±µ¨ü¦]¦ÓÂà´«¡C</para>
 
           <para>¦bFreeBSDªºª¬ªp¤¤¡A§Ú­Ìªº¦@¨É¨ç¦¡®w(shared libraries)¾÷¨î©M
             <application>SunOS</application> ªº«¬¦¡«D±`¬Ûªñ¡A¥B©ö©ó¨Ï¥Î¡CµM¦Ó¡A
             ±q 3.0 ¶}©l¡AFreeBSD ¥¿¦¡±N <acronym>ELF</acronym> §ï¬°¹w³]®æ¦¡¡C
             ÁöµM¡A<filename>a.out</filename> ®æ¦¡¨Ì¦p¥H©¹¯ëªº¦n¡A¦ý¬O¡A§Ú­Ì
 	    ½sĶ¤u¨ãªº¼¶¼gªÌ¡AGNU ªº¦¨­û¡A¥L­Ì¤¤¤î¤F¹ï
 	    <filename>a.out</filename> ®æ¦¡ªº¤ä´©»PºûÅ@¡C¦b³oºØª¬ªp¤U¡A­¢¨Ï
 	    §Ú­Ì¥²¶·¦Û¦æºûÅ@¥t¤@¥÷ª©¥»ªº compiler ©M linker¡A¤]¨Ï±o§Ú­ÌµLªk
 	    ±q³Ì·sªº GNU µo®i¦¨ªG¤¤Àò±o¦n³B¡C¦¹¥~¡A¹ï ISO-C++ ªº»Ý¨D¡A¤×¨ä¬O
 	    «Øºc¤l(constructors)©M¸Ñºc¤l(destructors)¡A¤]±a°Ê¥¼¨Óª©¥»¤¤¹ï
 	    <acronym>ELF</acronym> ªº­ì¥Í¤ä´©¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="binary-formats">
           <para>¬Oªº, ¦ý¬O, ¬°¤°»ò·|¦³³o»ò¦h¤£¦P®æ¦¡ªº°õ¦æÀɦs¦b©O?</para>
         </question>
 
         <answer>
           <para>¦b¶Â·t¦Ó»»»·ªº¹L¥h¡A¶È¦³Â²­®ªºµwÅé¦s¦b¡C¦Ó¦]¬°µwÅé²­®¡A·íµM¤]
             ¥u¯à°õ¦æ¤p¦Ó²³æªº¨t²Î¡Ca.out ®æ¦¡¬O°ò©ó¨º­Ó®É¥N©Ò»Ý­n¡A¦Ó³Q³Ð³y
 	    ¥X¨Óªº(¨Ò¦p¹³PDP-11)¡C¦b³o¤§«á¡A³\¦h¤H¸ÕµÛ±N Unix ²¾´Ó¨ì¨ä¥L¥­¥x
 	    ®É¡A¥L­Ì¤]«O¯d¤F a.out ®æ¦¡ªº°õ¦æÀÉ¡C¦]¬°¡A³o¹ï¦­´Áªº Motorola 68k¡A
 	    VAXen ¤§Ãþªº¨t²Î¤w¸g¨¬°÷¨Ï¥Î¤F¡C</para>
 
           <para>µM¦Ó¡A¤H¨Ã¤£·|º¡¨¬©ó²{ª¬¡C¤@¨ÇÁo©úªºµwÅé¤uµ{®v·Q¨ì¤F¡A¦pªG¯à
 	    Åý³nÅé¦h³B²z¤@¨Ç¨Æ¡A¨º CPU ªº¹q´¹Åé¼Æ´N¯à¤Ö¤@ÂI¡A¨Ã¥B¶]±o§ó§Ö¡C­n
 	    ¦b³oºØ·s¦¡ªºµwÅé¤W¤u§@(²{¦bºÙ¬°RISC)¡A<filename>a.out</filename>
 	    ³oºØ®æ¦¡´N¤£¦X¾A¤F¡C°ò©ó³o¼Ëªº²{¹ê©Ò»Ý¡A§ó¦hªº°õ¦æÀɮ榡³Qµo®i¥X
 	    ¨Ó¡A¥H´£¨Ñ¤ñ²³æ¥B¨ü¨ì³\¦h­­¨îªº <filename>a.out</filename> ®æ¦¡
 	    §ó¦nªº®Ä¯à¡C¤ñ¤è¹³¬O <acronym>COFF</acronym>¡A
 	    <acronym>ECOFF</acronym>¡A¤w¤Î¤@¨Ç¸û¤£¬°¤H©Ò©Pª¾ªº®æ¦¡¯É¯É³Q³Ð³y
 	    ¥X¨Ó¡C¦ý¬O¡A³o¨Ç®æ¦¡³£¤w¹F¨ì¦U¦Ûªº·¥­­¡Aª½¨ì¦³¤@¤Ñ
 	    <acronym>ELF</acronym> ªº¥X²{¡C</para>
 
           <para>¦¹¥~¡A·íµ{¦¡ªºÅé¿n¶V¨Ó¶V¤j¡A¦ÓºÏºÐªÅ¶¡©M¥D°O¾ÐÅé¬Û¹ï¨Ó»¡³£¸û
 	    ¤p®É¡A¦@¨É¨ç¦¡®w(shared libraries)ªºÆ[©À³Qµo®i¥X¨Ó¤F¡C¦b³o¦P®É¡A
 	    µêÀÀ°O¾ÐÅé¨t²Î(VM System)¤]Åܱo¶V¨Ó¶Vºë¥©¡C·í¨C¤@ºØ¶i¨B³£¦b
 	    <filename>a.out</filename>®æ¦¡¤W³Qµo®i¥X¨Ó®É¡A¥¦ªº¥i¥Î©Ê¤]¦P®ÉÅÜ
 	    ±o¶V¨Ó¶V§C¡C¥t¥~¡A¤H­ÌÁ٧Ʊæµ{¦¡¯à¦b°õ¦æ´Á¶¡°ÊºA¸ü¤J¡A©Î¬O±N¤w¸g
 	    °õ¦æ¹L¥B¨S¦³¥Îªºªì©l¤Æµ{¦¡½X¥á±ó¡AÂÇ¥H¸`¬Ù§ó¦hªº°O¾Ð¡Cµ{¦¡»y¨¥¦b
 	    ³o­Ó®É´Á¤]«K±o§óºë¥©¡A¤H­Ì¤]§Æ±æ¦b main ¤§«e¦Û°Êªº°õ¦æ§ó¦hªºªF¦è¡C
 	    ¦]¦¹¡A³\¦hÁcÂø¥B¥t¤H¹Ä¬°Æ[¤îªº§Þ¥©³Q¥Î¦b <filename>a.out</filename>
             ®æ¦¡¤W¥h¸Ñ¨M³o¨Ç°ÝÃD¡C¦ý¬O¡A¥Ñ©ó <filename>a.out</filename> ®æ¦¡
 	    ¥ý¤Ñªº­­¨î¡A­n¸Ñ¨M³o¨Ç°ÝÃD¥²»Ý¥I¥X§ó¦hªº¥N»ù¤Î®É¶¡¦¨¥»¡A¨ÃÅýµ{¦¡
 	    ªº½ÆÂø«×¤j¬°´£¤É¡C¦Ó <acronym>ELF</acronym> ®æ¦¡¥i¥H¤@Á|¸Ñ¨M³o¤@
 	    ¤Á°ÝÃD¡C¦ý¬O¡A­n±N¾ã­Ó¨t²Î±q®Ú¥»Âà´«¹L¥h¡A±N·|¦³¤£µuªº°}µh´Á¡A¦]
 	    ¦¹¡A <acronym>ELF</acronym>®æ¦¡±N·|¦³¤@°}¤l»P
 	    <filename>a.out</filename> ¨Ã¦s¡C</para>
 
           <para>µM¦Ó¡AÀHµÛ®É¶¡ªº¹L¥h¡AFreeBSDªº build tools ºt¤Æ¦¨¥­¦æªº¨â­Ó
 	    ¤ä½u(¤×¨ä¬O²ÕĶ¾¹©M¸ü¤J¾¹)¡CFreeBSD³o±ø¸ô¥[¶i¤F¦@¨É¨ç¦¡®w
 	    (shared libraries)¨Ã­×¥¿¤F¤@¨Ç¿ù»~¡C¦Ó­ì¨Óµo®i³o¨Çµ{¦¡ªº GNU ¦¨­û
 	    «h¬°¤F¦]À³²{ªp¡A­«¼g¤F³o¨Çµ{¦¡¡A¥H§ó²³æªº¤è¦¡¹ï¸ó¥­¥x½sĶ
 	    (building cross compilers)¡A¥H¤Î¦hºØ®æ¦¡
 	    (plugging in different formats) §@¥X¤F¤ä´©¡C³\¦h¤H·Q§@¥X¥H FreeBSD
 	    ¬°¥Øªº¥­¥xªº¸ó¥­¥x½sĶ¾¹¡C¦ý¤£©¯ªº¬O¡AFreeBSD ªº as ©M ld ¤£¯à§@
 	    ³o¶µ¤u§@¡C·sªº GNU ¤u¨ãµ{¦¡¥[¤J¤F¸ó¥­¥x½sĶ (Cross Compiler)¡A
             <acronym>ELF</acronym>®æ¦¡¤ä´©¡A¦@¨É¨ç¦¡®w(shared libraries)¡A
             C++ ªºÂX¥R... µ¥µ¥¡C¦¹¥~¡A³\¦h¼t°Ó¥H <acronym>ELF</acronym> ®æ¦¡
 	    µo¦æ¨ä²£«~¡A¦pªG³o¨ÇªF¦è¯à¦b FreeBSD ¤W°õ¦æªº¸Ü·íµM¬O³Ì¦nªº¡C¬JµM¡A
 	    ¯à°÷°õ¦æ <acronym>ELF</acronym> ®æ¦¡ªº°õ¦æÀɤF¡A¬°¤°»òÁÙ¶·­n
 	    <filename>a.out</filename> ©O¡H¥¦¤w¸g¬O¤@¤Ç««««¦Ñ¨oªº°¨¤F¡A¦bºÜ¤O
 	    ºÉ©¾ªº©^Äm³o»ò¦h¦~¤§«á¡A¸Ó¬OÅý¥¦¦bªª³õªÎ¨Uªº¯ó¦a¤W¦n¦n¥ð®§ªº®É­Ô
 	    ¤F¡C</para>
 
           <para><acronym>ELF</acronym> ®æ¦¡¤ñ a.out ¨ã¦³§ó¨}¦nªº®i²{¯à¤O¡A¨Ã
 	    ¥B¦b©³¼h¨t²Î¤¤¨ã¦³§ó¦hªº¥iÂX®i©Ê¡C<acronym>ELF</acronym> ¤u¨ãµ{¦¡
 	    §ó®e©ö³QºûÅ@¡A¥B´£¨Ñ¸ó¥­¥x½sĶªº¤ä´©¡A³o¤@ÂI¹ï«Ü¦h¤H¨Ó»¡¬O«Ü­«­n
 	    ªº¡C<acronym>ELF</acronym> ®æ¦¡¥i¯à¤ñ a.out ºC¤@ÂI¡A¦ý¬O¨ä®t²§«D
 	    ±`Ãø´ú¶q¥X¨Ó¡C³o¨âªÌ¶¡ÁÙ¦³³\¦h²Ó¸`¤Wªº¤£¦P¡A¤ñ¤è»¡¤À­¶¹ïÀ³ªº¤è¦¡¡A
 	    µ{¦¡½Xªì©l¤Æªº¤èªk...µ¥µ¥¡C³o¨Ç¨Ã¤£¬O«Ü­«­n¡A¦ý¬O¡A¨âªÌ´N¬O¤£¦P¡C
 	    ¥H«á¡AGENERIC ®Ö¤ß(kernel)±N·|²¾°£¹ï <filename>a.out</filename>
             ®æ¦¡¡C·í¤£¦b¦³°õ¦æ¶Ç²Î <filename>a.out</filename> µ{¦¡ªº¶·­n®É¡A
 	    ±N·|±q®Ö¤ß(kernel)¤¤²¾°£¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="chmod-symlinks">
           <para>¬°¬Æ»òchmod¤£·|§ïÅܲŸ¹³sµ²(symlink)ªº¦s¨úÅv­­¡H</para>
         </question>
 
         <answer>
           <para>Symlinks ¥»¨­¨Ã¨S¦³¦s¨úÅv­­¡A¦P®É¡A¦b¹w³]ªºª¬ªp¤U¡A
 	    &man.chmod.1; ±N¤£·|¸òÀHµÛ symlinks ¥h§ï«K¥Ø¼ÐÀɮתº¦s¨úÅv­­¡C¦]¦¹¡A
 	    ¦pªG§A¦³¤@­ÓÀÉ®× <filename>foo</filename>¡A¦P®É¡A¦³¤@­Ó symlink
 	    <filename>bar</filename> «ü¦V³o­ÓÀɮסA¥H¤U³o­Ó©R¥O±N¥Ã»··|¦¨¥\
 	    ªº³Q°õ¦æ¡C</para>
 
           <screen>&prompt.user; <userinput>chmod g-w bar</userinput></screen>
 
           <para>µM¦Ó¡A¦b <filename>foo</filename> ¤Wªº¦s¨úÅv­­±N¤£·|³Q§ï
 	    ÅÜ¡C</para>
 
           <para>§A¥²»Ý¨Ï¥Î <option>-H</option> ©Î¬O±N <option>-L</option>
 	    »P <option>-R</option> ¿ï¶µ¤@°_¨Ï¥Î¡A°Ñ¦Ò &man.chmod.1; ¥H¤Î
 	    &man.symlink.7; ¥H¨ú±o§ó¦hªº¸ê°T¡C</para>
 
             <warning>
               <para>¨Ï¥Î¿ï¶µ <option>-R</option> ·|Åý &man.chmod.1; ¥H
 	        <acronym>»¼°j(RECURSIVE)</acronym> ªº¤è¦¡¤u§@¡C·í§A§â
 		&man.chmod.1; ¥Î¦b¥Ø¿ý©Î¬O³sµ²¨ì¥Ø¿ýªº²Å¸¹³sµ²®É§ó­n¤p¤ß¡C
                 ¦pªG§A­n§ïÅܤ@­Ó²Å¸¹³sµ²°Ñ¦Ò¨ìªº¥Ø¿ý¤§¦s¨úÅv­­ &man.chmod.1; ¡A
 		¥Bª`·N¤£­n¥[¤W¥ô¦ó¿ï¶µ¡A¨Ã¥B¦b symlink ªºµ²§À¥[¤W±×½u
 		(<filename>/</filename>)¡CÁ|¨Ò¨Ó»¡¡A¦pªG
 		<filename>foo</filename> ³sµ²¨ì¥Ø¿ý <filename>bar</filename>¡A
 		¦Ó§A­n§ó§ï <filename>foo</filename> (¹ê»Ú¤W¬O
 		<filename>bar</filename>)¡A¨º´N¨Ï¥Î¡G</para>
 
               <screen>&prompt.user; <userinput>chmod 555 foo/</userinput></screen>
 
               <para>µ²§Àªº±×½u·|¨Ï±o &man.chmod.1; §ïÅÜ 
 	        <filename>foo</filename> ©Ò«ü¦Vªº¥Ø¿ý <filename>bar</filename>
 		ªºÅv­­¡C</para>
             </warning>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="login-8char">
           <para>¬°¤°»ò¦b FreeBSD 2.2.x ¤Î§ó¦­ªºª©¥»¤¤¡Aµn¤J¦WºÙ(login names)
 	    ³Q­­¨î¦b¤K­Ó¦r¤¸¥H¤U©O¡H</para>
         </question>
 
         <answer>
           <para>§A¥i¯à»{¬°­×§ï <literal>UT_NAMESIZE</literal> «á¦b­«·s½sĶ¾ã­Ó
             ¨t²Î¬O«Ü®e©öªº¨Æ¡C¦Ó¥B¦b³o¤§«á¡A¨C¥ó¨Æ³£¥i¥H¹B§@ªº«Ü¦n¡C¤£©¯ªº¬O¡A
 	    ¦³³\¦hªºµ{¦¡©M¤u¨ã(¥]§t¨t²Î¤u¨ã)§â¼Æ¦r¼g¦º¦bµ{¦¡¸ÌÀY(¨Ã«DÁ`¬O
 	    <literal>8</literal> ©Î <literal>9</literal>¡A¦³®É¥i¯à¬O¥j©Çªº
             <literal>15</literal> ©Î <literal>20</literal>)¡C³o¤£¶È¶È¬O·|±N
 	    §Aªº¨t²Î°O¿ýÀɧËÃa¦Ó¤w(¨Ó¦Û©óÅܰʪø«×©M©T©wªø«×°O¿ýªº®t²§)¡A¦P®É
 	    ¤]·|¯}Ãa Sun ªº NIS Client ªº¹B§@¡C¦P®É¡A©M¨ä¥LªºUnix¨t²Î¤§¶¡¤]
 	    ¦³¥i¯à·|²£¥Í¥¼ª¾ªº°ÝÃD¡C</para>
 
           <para>¦bFreeBSD 3.0 ¤Î¤§«áªºª©¥»¡A±b¸¹ªº³Ì¤jªø«×¼W¥[¨ì16­Ó¦r¤¸¡A
 	    ¦P®É¡A¨º¨Ç±Nªø«×¼g¦ºªºµ{¦¡¤]³Q§ä¥X¨Ó¨Ã§@¤F¾A·íªº­×¥¿¡C¥¿¦]¬°¼vÅT
 	    ¨t²Îªº½d³ò«Ü¼s¡A©Ò¥Hª½¨ì3.0ª©¤§«á¤~ºâ¤j­P­×¥¿§¹¦¨¡C</para>
 
           <para>¦pªG§A¦³¦Û«H¦b¥X°ÝÃDªº®É«á¯à¦Û¦æ¸Ñ¨M¡A§A¥i¥H§Q¥Î¤U­±ªº¤èªkÅý
 	    ¸û¦­´Áªºª©¥»¤ä´©¸ûªøªº±b¸¹¡C­º¥ý¡A­×§ï
 	    <filename>/usr/include/utmp.h</filename> ¤¤ªºUT_NAMESIZE¡C
             µM«á¡A§A¥²¶·§â <filename>/usr/include/sys/param.h</filename>
 	    ¤¤ªº MAXLOGNAME §ï¦¨¸ò UT_NAMESIZE ¬Û¦P¡C³Ì«á¡A¦pªG§A¬O±q­ì©lµ{
 	    ¦¡«Ø¥ß¨t²Î, §O§Ñ¤F /usr/include ¨C¦¸³£·|³Q§ó·s¡C
 	    ­×§ï /usr/src/.. ¤¤¾A·íªºÀɮסC</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="dos-binaries">
           <para>§Ú¯à¦bFreeBSD¤U°õ¦æDOSµ{¦¡¶Ü¡H</para>
         </question>
 
         <answer>
           <para>¬Oªº¡A¦Û3.0ª©°_§A¥i¥H¨Ï¥ÎBSDIªº 
 	    <application>doscmd</application> DOS ¼ÒÀÀ¾¹¡A¦pªG§A¹ï³o­ÓªF¦è
 	    ¦³¿³½ì¡A©Î¬O·Q¥[¤Jµo®i¦æ¦C¡A½Ð±H¤@«Ê¹q¤l¶l¥ó¨ì &a.emulation; ¡C
 	    </para>
 
           <para>¹ï©ó3.0¤§«eªº¨t²Î¡A¦b ports ¤¤¦³¤@®M³nÅé¥i¥H¼Òèö 8088¡A¨Ã´£
 	    ¨Ñ¨¬°÷ªºBIOS¤¤Â_ªA°È¥H°õ¦æDOS¤å¦r¼Ò¦¡ªºµ{¦¡¡A³o®M³nÅé¥s°µ
 	    <application>pcemu</application>¡A¦P®É¡A¹B¦æ¥¦¶·­n
 	    X Windows(¥ÑXFree86´£¨Ñ)¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="translation">
           <para>¦pªG­n§âFreeBSD¤å¥ó½Ķ¦¨§Úªº¥À»y¡A§Ú»Ý­n§@¤°»ò¡H</para>
         </question>
 
         <answer>
           <para>°Ñ¾\FreeBSD¤å¥ó¤¤ªº <ulink
 	    url="../fdp-primer/translations.html">½Ķ±`¨£°Ýµª</ulink>¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="freebsd-mail-bounces">
 	  <para>¬°¤°»ò§Ú±H¨ì FreeBSD.org ¬ÛÃö¦a§}ªº¹q¤l¶l¥ó³£³Q°h¦^¤F©O¡H</para>
         </question>
 
         <answer>
 	  <para>FreeBSD.org ªº¶l¥ó¨t²Î¹ï©ó¶i¨Óªº¶l¥ó±Ä¨úÄY®æªºÀˬd¡A¨Ã¥B°h¦^
 	    ©Ò¦³³]©w¤£¥¿½T¡A©Î¬O¼ç¦bªº©U§£¶l¥ó¡C§Aªº¶l¥ó³Q°h¦^¥i¯à¬O¦]¬°¤U¦C
 	    ­ì¦]©Ò¤Þ°_¡G</para>
 
 	  <itemizedlist>
 	    <listitem>
               <para>³o«Ê¹q¤l¶l¥ó¨Ó¦Û¤wª¾ªº©U§£¶l¥ó°Ï°ì©Î¬OIP¤¤¡C</para>
 
               <para>FreeBSD¶l¥ó¦øªA¾¹±N©Úµ´±µ¦¬¤wª¾ªº©U§£¶l¥ó¨Ó·½ªº¹q¤l¶l¥ó¡C
 	        ¦pªG´£¨Ñ§Aºô¸ôªA°Èªº¤½¥q©Î¬Oºô°ì¤¤¦³²£¥Í¹L©U§£¶l¥ó©Î¬O¦³©U§£
 		¶l¥óÂ༽¯¸¡A½Ð§A´«¤@­ÓªA°È´£¨ÑªÌ¡A©Î¬O°®¯Ü©ñ±ó¡C</para>
             </listitem>
 
             <listitem>
               <para>¹q¤l¶l¥óªº¥»¤å¶È¦³HTML¡C</para>
 
               <para>¶l¥óÀ³¸Ó¤w¯Â¤å¦r®æ¦¡µo°e¡A½Ð³]©w§Aªº¹q¤l¶l¥ó³nÅé°e¥X¯Â¤å
 	        ¦r®æ¦¡¡C</para>
             </listitem>
 
             <listitem>
               <para>FreeBSDªº¶l¥ó³B²zµ{¦¡µLªk¥ÑIP¤Ï¬d°e¥ó¥D¾÷ªºIP¡C</para>
 
               <para>³]¸m DNS ¤Ï¬d¬O±µ¨ü¤@¥x¥D¾÷¶l¥óªº¤@­Ó¼Ð·Ç­n¨D¡A½Ð¬°±zªº¶l¥ó
 	        ¥D¾÷³]¸m DNS ¤Ï¬d¡C³\¦h´£¨Ñ®a®xºô¸ôªA°È (DSL¡Acable¡Adialup µ¥)
 		ªº¤½¥q¨Ã¤£´£¨Ñ³o¼ËªºªA°È¡C¦b³oºØ±¡ªp¤U¡A½Ð³z¹Lºô¸ôªA°È´£¨ÑªÌªº
 		¶l¥ó¦øªA¾¹°e¥X±zªº¹q¤l¶l¥ó¡C</para>
             </listitem>
 
 	    <listitem>
 	      <para>¦b SMTP ¨Ï¥Î EHLO/HELO ©R¥O®É©Òµ¹¤©ªº hostname µLªk³Q¸ÑªR¨ì
 	        ¤@­Ó IP ¦ì¸m¡C</para>
 
 	      <para>¦b¶l¥ó³Q±µ¨ü¥H«e¡A¤@­Ó¥R¤À¦X®æ¡A¥B¥i³Q¸ÑªRªº¥D¾÷¦WºÙ¦b
 	        SMTP ¨ó©wªº¹ï½Í¤¤¬O¥²­nªº¡C¦pªG§A¨S¦³¦b DNS ¦øªA¾¹¤¤µn°O§A
 		ªº¥D¾÷¦WºÙ¡A½Ð³z¹Lºô¸ôªA°È´£¨ÑªÌªº¶l¥ó¦øªA¾¹°e¥X±zªº¹q¤l¶l
 		¥ó¡C</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>§Aªº°T®§¤¤§¨±aµÛ¤@­Ó message ID ¥H <quote>localhost</quote>
 	        ¦r¦êµ²§ô¡C</para>
 
 	      <para>¬Y¨Ç¶l¥ó³nÅé²£¥Í¬Y¨Ç¤£¥¿½Tªº message ID¡A³o±N¤£³Q±µ¨ü¡C
 	        §A¥²»Ý§ó§ï³]©wÅý§Aªº¶l¥ó³nÅé²£¥Í¥¿½Tªº message ID¡A¦pªG³oµL
 		ªk¸Ñ¨M¡A¦Ò¼{»¡ªA§Aªº¶l¥ó³nÅé§@ªÌ§ó·sµ{¦¡¥H³B²z³o­Ó°ÝÃD¡C</para>
 	    </listitem>
           </itemizedlist>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="free-account">
           <para>§Ú¥i¥H¦b­þ¸Ì§ä¨ì¤@­Ó§K¶OªºFreeBSD±b¸¹¡H</para>
         </question>
 
         <answer>
           <para>FreeBSDªº¦øªA¾¹¥»¨­¤£´£¨Ñ¥ô¦ó¹ï¥~ªºªA°È¡A¨ä¥Lªº³æ¦ì¤¤¡A
             ¦³¤H´£¨Ñ¶}©ñªº Unix ¨t²ÎªA°È¡C¨ä¤¤¦³¨Ç¥i¯à­n¦¬¨ú¨Ç³\¶O¥Î¡C</para>
 
           <para><ulink URL="http://www.arbornet.org/">Arbornet, Inc</ulink>¡A
 	    ¤]³QºÙ¬° M-Net¡A¦Û 1983 ¦~°_´N¶}©l´£¨Ñ Unix ¨t²ÎªA°È¡C¤@¶}©l¡A
 	    ¥L­Ì¨Ï¥Î Altos ¨Ã°õ¦æ System III¡C¥L­Ì¦b 1991 ¦~Âà´«¨t²Î¦¨¬°
 	    BSD/OS¡C¦b 2000 ¦~¤»¤ë¡A¥L­Ì¦A«×§ó´«¦¨¬° FreeBSD¡CM-Net ¯àÅý¨Ï
             ¥ÎªÌ³z¹L SSH ¤Î telnet ³s½u¨ì¥D¾÷¡A¨Ã´£¨Ñ§¹¾ãªº FreeBSD ³nÅé¥H
 	    ¨Ñ¨Ï¥Î¡CµM¦Ó¡AM-Net §@¬°¤@­Ó«D¬Õ§Q²Õ´¹B¦æ¡A¦s¨úÅv¥u­­©ó¦¨­û©M
 	    ÃÙ§UªÌ¡AM-Net ¤]´£¨Ñ BBS ¨t²Î©Mºô¸ô²á¤ÑªA°È¡C</para>
 
           <para><ulink URL="http://www.grex.org/">Grex</ulink> ´£¨Ñ¤F«D±`
             Ãþ¦ü M-Net ªºªA°È¡A¥]¬A¤F BBS ¨t²Î©Mºô¸ô²á¤Ñ¡CµM¦Ó¡A¾÷¾¹¬O¨Ï¥Î
             Sun 4M¡A¨Ã°õ¦æ SunOS¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="sup-define">
           <para>¤°»ò¬O <command>sup</command>¡A§Ú¸Ó¦p¦ó¨Ï¥Î¥¦¡H</para>
         </question>
 
         <answer>
           <para><ulink URL="http://www.FreeBSD.org/cgi/ports.cgi?^sup">
             SUP</ulink> ªº·N«ä¬O Software Update Protocol¡A¥Ñ CMU µo®i¡A
             ¥Î¨Óºû«ù¾ã­Óµo®iªº¦P¨B¡C§Ú­Ì§Q¥Î¥¦«O«ù»·ºÝªº¯¸¥x©M­ì©l¯¸¥x¤§¶¡
             ªº¦P¨B¤u§@¡C</para>
 
           <para>µM¦Ó¡ASUP ¦bÀW¼eªº¨Ï¥Î¤W¨Ã¤£¤Ó¤Íµ½¡A¦P®É¡A¥Ø«e¤]¤£¦A¨Ï¥Î¤F¡C
             ¥Ø«e«Øijºû«ù­ì©l½X¦P¨B§ó·sªº¤èªk¬O
 	    <ulink URL="../handbook/synching.html#CVSUP">CVSup</ulink>¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="daemon-name">
           <para>³o­Ó¥i·Rªº¤p¬õ¤Hªº¦W¦r¬O¤°»ò¡H</para>
         </question>
 
         <answer>
           <para>¦ü¥G¡A¥L¨Ã¨S¦³¤@­Ó¥¿¦¡ªº¦W¦r¡A©h¥B´NºÙ¨ä¬°
 	    <quote>BSD ¤p´cÅ]</quote> §a¡C¦pªG§A°õ·N­n¨Ï¥Î¤@­Ó¦W¦r¡C¨º´N¥s¥L
 	    <quote>¤p°Êª«(beastie)</quote> §a¡Cµù¡G<quote>beastie</quote>
 	    ¦bŪ­µ¤W¸ò <quote>BSD</quote> «Ü±µªñ¡C</para>
 
           <para>§A¥i¥H¦bBSD¤p´cÅ]ªº <ulink
 	    url="http://www.mckusick.com/beastie/index.html">¥D­¶</ulink>
 	    ¤W¨ú±o§ó¦hªº¸ê°T¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="use-beastie">
           <para>§Ú¯à¨Ï¥ÎBSDªº¤p´cÅ]¹Ï®×¶Ü¡H</para>
         </question>
 
         <answer>
           <para>¤]³\§a¡A§Ú¤]¤£½T©w¡CBSD¤p´cÅ]¹Ï®×ªºª©Åv¬OÄÝ©ó°¨·²º¸Ä¬®æÄõ±Ð·|
 	    (Marshall Kirk McKusick)©Ò¾Ö¦³¡C§A¥i¥H¸ÕµÛ¥h¬d¬Ýºô­¶<ulink
             url="http://www.mckusick.com/beastie/mainpage/copyright.html">±Ô­zÃö©óBSD¤p´cÅ]¨v¹³</ulink>
 	    ¥H¨ú±o§ó¸Ô²ÓÃö©ó¨Ï¥Î¥Lªº¸ê°T¡C</para>
 
           <para>Á`Âkªº¨Ó»¡¡A¦pªG§A¯Âºé¬°¤F¦Û¤v·Q­nŲ½à¡A¨º»ò¡A§A¥i¥H¦Û¥Ñªº¨Ï
 	    ¥Î¨v¹³¡C¦pªG§A¬O­Ó¤H¨Ï¥Î¡A¥u­n±¡ªp¾A·í¡AÀ³¸Ó³£·|³Q³\¥i¡C¦pªG§A·Q
 	    ¦b°Ó·~¤W¨Ï¥Î¡A«h§A¥²»ÝÁpôĬ®æÄõ±Ð·|(Kirk McKusick)¥H¨ú±o³\¥i¡C
 	    ¦pªG§A»Ý­n§ó¶i¤@¨B¸Ô²Óªº¸ê°T¡A½Ð°Ñ¦Ò <ulink
 	    url="http://www.mckusick.com/beastie/index.html">BSD¤p´cÅ]ªº­º­¶</ulink>¡C
 	    </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="daemon-images">
           <para>§A¦³¥ô¦óªº BSD ¤p´cÅ]¹Ï®×¥i¥HÅý§Ú¨Ï¥Î¶Ü¡H</para>
         </question>
 
         <answer>
           <para>§A¥i¥H¦b <filename>/usr/share/examples/BSD_daemon/</filename>
             µo²{ eps ¤Î Xfig ¨âºØ®æ¦¡ªº¹ÏÀÉ¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
-        <question id="define-MFC">
-          <para><acronym>MFC</acronym> ¥Nªí¤°»ò·N«ä¡H</para>
-        </question>
-
-        <answer>
-          <para>MFC ¬O¤@­ÓÁY¼g¡A¥¦¥Nªí¤F <quote>Merged From -CURRENT</quote>¡C
-            ¥¦³Q¨Ï¥Î¦b CVS logs ¤¤¡A¥Hªí¥Ü±q CURRENT ¤¤¾ã¦X¶i STABLE ¤À¤ä
-            ªº§ïÅÜ¡C</para>
-        </answer>
-      </qandaentry>
-
-      <qandaentry>
-        <question id="define-BSD">
-          <para><acronym>BSD</acronym> ¨s³º¥Nªí¤°»ò·N«ä¡H</para>
-        </question>
-
-        <answer>
-          <para>¥¦¬O¤@ºØ©Ó¶Ç¦Û¶Â·t®É¥Nªº¥j¦Ñ¯µ±K»y¨¥¡A¶È¶È¦b¤º³¡¦¨­û¤§¤¤¡A
-	    ¥H¤f¦Õ¬Û¶Çªº¤è¦¡®¨®¨ªº¬y¶ÇµÛ¡C¥¦¥Î¨Ó¥Nªí¬Y¨Ç¯«¯¦ªºªF¦è¡A¦ý¬O¡A
-	    §Ú­ÌµLªk¹ï³o¨ÇªF¦è¥H½T¹êªº¤å¦r¥[¥H±Ô­z¨Ã¨ã¹³¤Æ¡A¥¦´X¥G¤£§@¥ô¦ó
-	    ªºÂ½Ä¶»P¸ÑÄÀ¡C¦pªGµw¬O­n¥H¤HÃþ²{¦³ªº»y¨¥¥[¥H»¡©ú¡A¥u¯à»¡¥¦ªº·N
-	    «ä¤j·§¤¶©ó <quote>¤@¯Å¤èµ{¦¡Áɨ®(Formula-1 Racing Team)</quote>¡A
-	    <quote>¥øÃZ¬O¬ü¨ýªºÂI¤ß(Penguins are tasty snacks)</quote>¡A¥H¤Î
-	    <quote>§Ú­Ì¤ñLinux§ó¨ã¦³«ÕÀq·P(We have a better sense of humor than Linux)</quote>
-	    ³o¤TªÌ¤§¶¡¡C:-)</para>
-
-          <para>¦n¤F¡A¤£¸ò§A¶}ª±¯º¤F¡C¥¿½Tªº»¡¡ABSD ¬O
-	  <quote>Berkeley Software Distribution</quote> ªºÁY¼g¡A³o¬O¥Ñ Berkeley
-	    <acronym>CSRG</acronym> (Computer Systems Research Group)
-	    ¿ï¨Ó·í§@¥L­Ì©Òµo¦æªº Unix ¦WºÙ¡C</para>
-        </answer>
-      </qandaentry>
-
-      <qandaentry>
-	<question id="define-pola">
-	  <para><acronym>POLA</acronym> ¥Nªí¤°»ò·N«ä¡H</para>
-	</question>
-
-	<answer>
-	  <para>³Ì¤ÖÅå³Y­ì«h¡C³o¥Nªí¤F FreeBSD ªºµo®i¹Lµ{¡A¥ô¦óªº§ïÅܨì¤F¨Ï
-	    ¥ÎªÌºÝÀ³¸Ó«O«ù¤£Åý¨Ï¥ÎªÌ·P¨ìÅå³Y¡C¤ñ¤è»¡¡A±N
-	    <filename>/etc/defaults/rc.conf</filename> ¤¤ªº¨t²Î±Ò°Ê¶¶§Ç¥ô·N
-	    ªº§ó§ï±N¹H¤Ï³o­Ó­ì«h¡C</para>
-	</answer>
-      </qandaentry>
-
-      <qandaentry>
-        <question id="define-repocopy">
-          <para>¤°»ò¬O repo-copy¡H</para>
+        <question id="glossary">
+	  <para>§Ú¦b¤å¥ó¡B¶l»¼½×¾Â¤W¡A±`·|¬Ý¨ì¤@¨ÇÁY¼g¦r¡B§Þ³N¦r·J¡A³o¨Ç¥i¥H¥h­þÃä¬d©O¡H</para>
         </question>
 
         <answer>
-          <para>¤@¥÷ repo-copy (¥¦¬O <quote>repository copy</quote> ªºµuªí®æ)
-            ª½±µ°Ñ¦Ò¨ìCVS­Ü®w¤¤ªºÀɮסC</para>
-
-          <para>¨S¦³¤F¤@¥÷ repo-copy¡A¦pªG¤@­ÓÀɮ׶·­n³Q½Æ»s©Î¬O³Q·h²¾¨ì­Ü®w
-	    ¤¤ªº¨ä¥L¦a¤è¡A½T»{ªÌ±N·|°õ¦æ <command>cvs add</command> ¥H§âÀÉ®×
-	    ©ñ¨ì·sªº¦a¤è¡A¦P®É¡A¹ïÂÂÀÉ®×°õ¦æ <command>cvs rm</command>¡AÂÂÀÉ
-	    ®×±N³Q²¾°£¡C</para>
-
-          <para>³o­Ó¤èªk¤£§Qªº¦a¤è¬O¡A¾ú¥vÀÉ®×(§Y¦b CVS °O¿ý¤¤)±N¤£·|³Q½Æ»s
-	    ¨ì·sªº¦aÂI¡C¦b FreeBSD Project ¤¤¦Ò¼{¨ì¡A³o­Ó¾ú¥v°O¿ý¬O«Ü¦³¥Î³Bªº¡A
-	    ¤@­Ó repository copy ¬O¸g±`³Q¥Î¨ìªº¡C³o¬O repository meisters
-	    ¤@ª½¨Ï¥Î¨Ó±NÀɮ׽ƻs¶i­Ü®wªº¬yµ{¡A¦Ó«D¨Ï¥Î &man.cvs.1;¡C</para>
+          <para>½Ð°Ñ¾\ <ulink
+	     url="&url.books.handbook;/freebsd-glossary.html">
+	     &os; ¦r·Jªí</ulink>¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="bikeshed-painting">
           <para>¬°¤°»ò§Ú¸Ó¦b·N¸}½ñ¨®´×ªºÃC¦â¡H</para>
         </question>
 
         <answer>
           <para>¤@­Ó³Ìµu³Ìµuªºµª®×¬O¡A§A¤£¸Ó¦b·N¡Cµy·Lªø¤@ÂIªºµª®×¬O¡AÁöµM
             §A¦³¯à¤O¦Û¤v¥h«Ø³y¤@®y¸}½ñ¨®´×¡A¦ý¬O¡A³o¤£¥Nªí¦]¬°§A¤£³ßÅw²{¦b³o
             ­Ó¸}½ñ¨®´×ªºÃC¦â¡A´N¤¤¤î¥Lªº«Ø¿v¡C³o­Ó¤ñ³ëªº·N«ä¬O¡A§A¤£»Ý­n¥hª§½×
             ¨C¤@­Ó²Ó¶µ¯S¼x¡A¥u¦]¬°§A¦³¿ìªk¥h§@¥¦¡C¬Y¨Ç¤Hªºµû½×¬O¡AÂø­µªº²£¥Í«×
             ¹ïÅܤƪº½ÆÂø©Ê¬Û¤Ï¦a¤ñ¨Ò¡C</para>
             
           <para>§óªø¥B¸û§¹¾ãªºµª®×¬O¡A¦b¸g¹Lªø®É¶¡ª§½×Ãö©ó¬O§_¸Ó±N &man.sleep.1;
             ªº¬í°Ñ¼Æ²¾°£¡A&a.phk;µoªí¤F¤@½gªø½× <quote><ulink
             url="http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=506636+517178+/usr/local/www/db/text/1999/freebsd-hackers/19991003.freebsd-hackers">¤@®y¦Û¦æ¨®½´ (¥ô¦óÃC¦âªº)¦b«C¯Üªº¯ó¦a¤W...</ulink></quote>¡C
 	    ¨º«h°T®§³Q¾A·íªº³¡¤À³Q¤Þ¥Î¦b¤U­±¡C</para>
 
           <blockquote>
             <attribution>&a.phk; on freebsd-hackers, October
               2, 1999</attribution>
 
             <para><quote>¤°»ò¬OÃö©ó³o­Ó¸}½ñ¨®´×?</quote> ³¡¤Àªº¤H³o¼Ëªº¸ß
 	      °Ý§Ú¡C</para>
 
             <para>³o¬O¤@­Ó«D±`ªø»·ªº¬G¨Æ¡A§_«h´N¬O¤@­Ó¥j¦Ñªº¬G¨Æ¡C¦ý¬O¨Æ¹ê¤W¡A
               ³o­Ó¬G¨Æ«D±`ªºµu¡CC. Northcote Parkinson ¦b1960¦~¥Nªì´Á¼g¤F¤@¥»
 	      ®Ñ¡A®Ñ¦W¬° <quote>Parkinson's Law</quote>¡A¦b³o¥»®Ñ¤¤¥]§t¤F«Ü¦h
 	      ¨ã¦³¨ô¨£ªº°ÊºAºÞ²z¾Ç¡C</para>
 
             <para>[¤Þ­z¤@ÂI¦b³o¥»®Ñ¤Wªºµû½×]</para>
 
             <para>¦b³o­Ó³Q±²¤J¸}½ñ¨®´×®×ªº¯S®í¨Ò¤l¡A¥D­nªº­n¯À¬O®Ö¯àµo¹q³õ¡A
 	      §Ú·Q¡A³o¨¬¥H»¡©ú³o¥»®Ñªº¦~ÄÖ¡C</para>
 
             <para>Parkinson ®i¥Ü¤F§A¸Ó¦p¦ó¦b¸³¨Æ·|¤¤Ä¹±oÃÙ¦P¥h«Ø³y¤@®y¼Æ¦Ê¸U
 	      ©Î¬Æ¦Ü¤Q»õ¬ü¤¸ªº®Ö¯àµo¹q³õ¡A¦ý¬O¡A¦pªG§A·Q­n¥h«Ø³y¤@®y¸}½ñ¨®´×¡A
 	      §A±N·|³QªÈÄñ¦bµL½aµLºÉªº°Q½×¤§¤¤¡C</para>
 
             <para>Parkinson ¸ÑÄÀ¡A³o¬O¦]¬°¤@­Ó®Ö¯àµo¹q³õ¬O³o¼Ëªº¼sÁï¡A³o¼Ëªº
 	      ©ù¶Q¡A¨Ã¥B³o¼Ëªº½ÆÂø¡A¥H¦Ü©ó¤H­ÌµLªk´x´¤¥¦¡A¦Ó¨Ã«D¹Á¸Õ¡A¥L­Ì«æ
 	      ¤Áªº§Æ±æ¦³¤H¯à°÷À°¥L­Ì³B²z¨Ã¸Ñ¨M©Ò¦³º¾¸Hªº²Ó¶µ¡C
 	      Richard P. Feynmann µ¹¤F¤@¨Ç¦³½ì¡A¥B«D±`¤@°w¨£¦åªº½×ÂI¡A¦b¥Lªº
 	      ®Ñ´£¨ì¤F Los Alamos ªº¨Ò¤l¡C</para>
 
             <para>¥t¤@¤è­±¡A¥ô¦ó¤H³£¯à¦Û¤v¦b¶g¥½²Õ¸Ë¤@®y¸}½ñ¨®´×¥X¨Ó¡A¨Ã¥B¤´
 	      ¦³¶¢²á¥i¥HÆ[½à¹qµø¤Îª±¹CÀ¸¡C¦]¦¹¡AµL½×§A§@¤F¦h»ò§¹µ½ªº·Ç³Æ¡A¤]
 	      ¤£ºÞ§A´£¥Xªº¤è®×¬O¦h»òªº¦X©y¡A¬Y¨Ç¤H¤´±N§ì¦í¾÷·|¶]¥X¨Ó§i¶D§A¡A
 	      ¥L¥¿¦b§@¦P¼Ëªº¨Æ¡A¥¿¦b¥I¥X§V¤O¡A¥L´N¦b
               <emphasis>³o¸Ì</emphasis>¡C</para>
               
             <para>¦b¤¦³Á¡A§Ú­ÌºÙ³o­Ó¥s§@
 	      <quote>ªê¦º¯d¥Ö(setting your fingerprint)</quote>¡C¥¦Ãö«Y¨ì§A
 	      ­Ó¤HªºÅº¶Æ©MÁn±æ¡A³oÃö«Y¨ì§A¬O§_¥i¥H«üµÛ¬Y¦a«á¹ïµÛ§O¤H»¡
 	      <quote>³o¸Ì! ³o¬O<emphasis>§Ú</emphasis>§@ªº¡C</quote>
 	      ³o¬O¬Fªv¤Hª««Ü­«­nªº¤@­Ó¯S¼x¡C¦ý¬O¡A®É¾÷¬O¤j¦h¼Æ¤H¥Á©Ò½á»Pªº¡C
 	      ·Q·Q¨º¨Ç¯d¦b¤ôªd¦a¤Wªº¸}¦L§a¡C</para>
           </blockquote>
         </answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter id="funnies">
     <chapterinfo>
       <author>
 	<firstname>Edward</firstname>
 	<surname>Chuang</surname>
 	<affiliation>
 	  <address><email>edwardc@firebird.org.tw</email></address>
 	</affiliation>
       </author>
     </chapterinfo>
 
     <title>The FreeBSD Funnies</title>
 
     <qandaset>
       <qandaentry>
         <question id="very-very-cool">
           <para>How cool is FreeBSD¡H</para>
         </question>
 
         <answer>
           <para>°Ý¡G¦³¤H°µ¹L FreeBSD °õ¦æ®Éªº·Å«×´ú¸Õ¶Ü¡H §Úª¾¹D Linux
 	    ¤ñ DOS ²D¡A¦ý¨SÅ¥¤H´£¹L FreeBSD¡A¦ü¥G«Ü¼ö¡C</para>
 
           <para>µª¡G¨S¦³¡A¦ý¬O¦b¨ýı¤W¦³°µ¹LµL¼Æ¦¸´ú¸Õ¡C§Ú­Ìé¤W¦ÛÄ@¨ü¸ÕªÌªº
 	    ²´·ú¡A¨Æ¥ý¦Aµ¹¥L­ÌªA¥Î 250 ²@§Jªº LSD-25 °g¤ÛÃÄ¡C35% ªº¨ü¸ÕªÌ»¡
 	    FreeBSD ¹Á°_¨Ó¹³¾ï¤l¡A¦Ó Linux «h¬Oµµ¦âªººd¾ðªG¹ê¡C¾Ú§Ú©Òª¾¡A¨S
 	    ¦³¤@²Õ´£¨ì·Å«×¤W¯S§Oªº®t²§¡C«á¨Óµo²{¡A¦³¤Ó¦h¨ü¸ÕªÌ¦b´ú¸Õ®É¹Ú¹C¨«
 	    ¥X©Ð¶¡¼vÅT¨ì¼Æ¾Ú¡A³Ì«á¥u±o©ñ±ó¾ã­Ó½Õ¬d¡C§Ú·Q¤j³¡¥÷ªº¨ü¸ÕªÌ²{¦b¦b
 	    Apple ¤u§@¡AÄ~ Drag and Drop ¤§«á¡A¬ã¨s¥þ·sªº <quote>Scratch and
 	    Sniff</quote> ¹Ï§Î¬É­±¡CIt's a funny old business we're in¡I</para>
 
           <para>¤£¶}ª±¯º¤F¡AFreeBSD ©M Linux ³£¨Ï¥Î <acronym>HLT</acronym>
 	    (halt) «ü¥O¥H¦b¨t²Î¶¢¸m®É­°§C¹q¤Oªº¨Ï¥Î¤]´î¤Ö¤F¼öªº²£¥Í¡C¦pªG¦³
 	    ³]©w APM (automatic power management)¡AFreeBSD ¤]¥i¥HÅý CPU ¶i
 	    ¤J§C¹q¤O¼Ò¦¡¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="letmeoutofhere">
           <para>½Ö¦b§Úªº°O¾ÐÅé´¡¼Ñ¤¤¨F¨F§@ÅT¡H¡H</para>
         </question>
 
         <answer>
           <para>°Ý¡GFreeBSD ½sĶ®Ö¤ß®É¦³°µ¬Æ»ò <quote>©_¯S</quote> ªº¨Æ
 	    Åý°O¾ÐÅé¨F¨F§@ÅT¶Ü¡H·í½sĶ®É(ÁÙ¦³¶}¾÷®É½T»{³nºÐ«áªºµu¼È®É¶¡)¡A
 	    ¤]ºØ¦ü¥G¨Ó¦Û°O¾ÐÅé´¡¼Ñªº©_©ÇÁn­µ¡C</para>
 
           <para>µª¡G¬Oªº¡I¦b BSD ªº¤å¥ó¤¤§A·|±`±`¬Ý¨ì <quote>­I«áÆF</quote>¡A
 	    ¤j³¡¥÷ªº¤H³£¤£ª¾¹D¨º¬O¤@ºØ¹ê»Ú¦s¦bªººë¯«Åé --- ´x±±µÛ§Aªº¹q¸£¡C
 	    §AÅ¥¨ìªºÁn­µ¬O³o¨Ç­I«áÆF¥H°ª­µ¤f­ï¦b·¾³q«ç¼Ë°µ³\¦hªº¨t²ÎºÞ²z¤u
 	    §@¡C</para>
 
           <para>¦pªG³o¨ÇÁn­µ«Ü§xÂZ§A¡A¨Ó¦Û DOS ªº
 	    <command>fdisk /mbr</command> ´N¯àÂ\²æ¡A¦ý¦pªG¦³¬Û¤Ïªº®ÄªG
 	    ¤]¤£­nÅå³Y¡C¨Æ¹ê¤W¡A¦pªG¦b»ö¦¡¤¤Å¥¨ì Bill Gates ®£©ÆªºÁn­µ±q¤º
 	    «Øªº³â¥z¶Ç¨Ó¡A°¨¤W°k¦Ó¥B¤£­n¦^ÀY¡I ±q BSD ­I«áÆF¤£¥­¿Åªº¼vÅT¤¤
 	    ¸Ñ©ñ¡ADOS ©M Windows ­I«áÆF³q±`³£¯à­«·s±±¨î¾ã¥x¾÷¾¹¨Ã¹ï§AªºÆF
 	    »î¶A©G¡C¦pªG¦³¿ï¾Ü¡A§Ú·Q§Ú¹çÄ@²ßºD©_©ÇªºÁn­µ¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="changing-lightbulbs">
           <para>­n´X­Ó FreeBSD hacker ¤~¯à´«±¼¤@­Ó¹q¿Oªw¡H</para>
         </question>
 
         <answer>
           <para>¤@¤d¤@¦Ê¤C¤Q¤G­Ó¡G</para>
 
           <para>¤G¤Q¤T­Ó¦b -current ¤W©ê«è¬Ý¤£¨ì¥ú¤F¡F</para>
 
           <para>¥|­Ó«ÅºÙ³o¬O³]©w¤Wªº°ÝÃD¡A©Ò¥H¹³³o¼Ëªº email À³¸Ó©ñ¦b
 	    -questions¡F</para>
 
           <para>¤T­Ó submit PR¡A¨ä¤¤¤@­Ó°e¿ù¨ì doc ¤U¡A¨Ã¥B¤º®e¥u
 	    ¦³¡¨³o¸Ì¦n·t¡¨¡F</para>
 
           <para>¤@­Ó commit ©|¥¼´ú¸Õªº¹q¿Oªw¡A³y¦¨¤£¯à buildworld¡A
 	    ¤­¤ÀÄÁ«á¥L§â­ì¨Óªº¿Oªw´«¦^¨Ó¡F</para>
 
           <para>¤K­Óº´°_ flame war¡A³d©Ç°e¥X PR ªº¤H¨S¦³¥]¬A patch¡F</para>
 
           <para>¤­­Ó®I«è buildworld Äê±¼¤F¡F</para>
 
           <para>¤T¤Q¤@­Ó»¡ buildworld ¥i¥H¥Î¡A¤£¯à¥Îªº¤H¤@©w¬O cvsup ªº
 	    ®É¾÷¤£¹ï¡F</para>
 
           <para>¤@­Ó§â´«¦¨·s¿Oªwªº patch ¥á¨ì -hackers ¤W¡F</para>
 
           <para>¤@­Ó»¡¥L¤T¦~«e´N°µ¥X¤F patch¡A¦ý°e¨ì -current «á«o³Q©¿²¤±¼¡A
 	    ©Ò¥H¥L¹ï¾ã­Ó PR ¨t²Î¦³«Ü¤£¦nªº¦L¶H¡C¦¹¥~¡A¥L¤]»{¬°®³¥Xªº·s¿OªwµL
 	    ªk¤Ï¥ú¡F</para>
 
           <para>¤T¤Q¤C­Ó©H­ý»¡¹q¿Oªw¤£ÄÝ©ó°ò¥»¨t²Îªº¤@³¡¥÷¡A©Ò¥H committer
 	    ¤£¯à¤£¥ý¿Ô¸ß¾ã­Ó Community ªº·N¨£´N³o¼Ë°µ¤U¥h¡CÁÙ¦³¡A-core
 	    ¨ì©³©M³o¥ó¨Æ¦³¤°»òÃö«Y¡H¡I</para>
 
           <para>¨â¦Ê¤H©ê«è´«¿Oªw¤§«á¡A¸}½ñ¨®´×ªºÃC¦âÅܱo¦n©_©Ç¡F</para>
 
           <para>¤T­Ó«ü¥X¡A¥Î¨Ó´«¿Oªwªº patch ¤£²Å¦X &man.style.9; ªº³W©w¡F</para>
 
           <para>¤Q¤C­Ó®I«è®³¥X¨Óªº·s¿Oªw¬°¤°»ò¬O¥Î GPL¡F</para>
 
           <para>¤­¦Ê¤K¤Q¤»¤H³´¤J¤@³õ flame war¡A¦b GPL¡BBSD¡BMIT¡BNPL
 	    ¦U­Ó license ©M FSF ¬Y¦ì¤£¨ã¦W³Ð¿ì¤H¤h­Ó¤H½Ã¥Í¤§¶¡¡A¤ñ¸û©¼¦¹
 	    ªºÀu¶Õ¡F</para>
 
           <para>¤C­Ó±N³o¤@¦ê°Q½×ªº¤£¦P³¡¥÷¤À§O²¾¨ì -chat ©M -advocacy¡F</para>
 
           <para>´Nºâ´£¥Xªº·s¿Oªw¤ñªº·t¡AÁÙ¬O¦³¤@­Ó§â¥¦ commit ¶i¨Ó¡F</para>
 
           <para>¨â­Ó´«¦^­ì¥ýªº¿Oªw¡A¨Ã¥B¯d¤U·¥¬°¼««ãªº commit °T®§¡C¥L­Ì»{¬°
 	    »P¨äÅý FreeBSD ¥Î·t¿Oªw¡AÁÙ¤£¦p°®¯Ü«Ý¦b¶Â·t¤¤ºâ¤F¡F</para>
 
           <para>¥|¤Q¤»¤H¹ï¨ú®ø¤£¥Î·t¿Oªw³o¥ó¨Æ¤jÁn¯e©I¡A­n¨D -core 
 	    ¥ß¨è´£¥X¼á²M¡F</para>
 
           <para>¤Q¤@­Ó­n¨D´«¦¨¤p¤@ÂIªº¹q¿Oªw¡A¥H«K¥¼¨Ó FreeBSD ¦pªG²¾´Ó¨ì
 	    ¹q¤lÂû¤W«á·|§ó¬°¤è«K¡F</para>
 
           <para>¤C¤Q¤T¤H©ê«è -hackers ©M -chat ¤Wªº SNR¡AÂÇ unsubscribe
 	    ¨Óªí¥Ü§Üij¡F</para>
 
           <para>¤Q¤T­Ó°e¥X¡¨unsubscribe¡¨¡B¡¨§Ú­n¦p¦ó unsubscribe¡¨©Î¡¨«ô°U§â
 	    §Ú±q list ¦W³æ¤¤§R±¼¡¨¡A«Hªº³Ì«á­±«h¬O¤@¯ë¥Ñ majordomo ¥[¤W¥h
 	    ªº footer¡F</para>
 
           <para>·í¨C­Ó¤H¦£©ó©¼¦¹¥s½|®É¡A¦³­Ó³Ã¥ë¶X¨S¤Hª`·N¡A§â¥i¥H¥Îªº¿Oªw°½
 	    °½´«¤W¥h¡F</para>
 
           <para>¤T¤Q¤@­Ó«ü¥X¦pªG¥Î TenDRA ½sĶ·sªº¿Oªw¡A·|¤ñªº¨Ó±o«G
 	    0.364%¡]ÁöµM¿Oªw·|³Q½sĶ¦¨¥¿¤»­±Åé¡^¡A©Ò¥H FreeBSD ¤º©wªº½sĶ¾¹
 	    À³¸Ó¬O TenDRA¡A¦Ó¤£¬O EGCS¡F</para>
 
           <para>¦³­Ó¤H»¡·s¿Oªw¯Ê¥F¬ü·P¡F</para>
 
           <para>¤E­Ó¤H¡]¥]¬A­ì¥ý°e PR ªº¤H¡^°Ý¡¨¤°»ò¬O MFC¡H¡¨¡F</para>
 
           <para>¤­¤Q¤C­Ó©ê«è¦Û±q´«¤F¿Oªw«á¡A¨â­Ó¬P´Á³£¨S¦³¥ú¥X²{¡C</para>
 
           <para><emphasis>&a.nik; ¸Éª`¡G</emphasis></para>
 
           <para><emphasis>­è¬Ý¨ì®É¡A§Ú§Ö¯ºÂ½¤F¡C</emphasis></para>
 
           <para><emphasis>µM«á·Q¨ì¡A¡¨µ¥¤@¤U¡A¤£¬OÀ³¸ÓÁÙ¦³¤@­Ó­n±N³o¨Ç°O¦b
 	    list ¤W¶Ü¡H¡¨</emphasis></para>
 
           <para><emphasis>±µµÛ²×©ó¤F¸Ñ§Úªº¨Ï©R :-)</emphasis></para>
         </answer>
       </qandaentry>
       
       <qandaentry>
         <question id="dev-null">
           <para>¼g¤J <filename>/dev/null</filename> ªº¸ê®Æ¶]¨ì­þ¸Ì¥h¤F¡H</para>
         </question>
         <answer>
           <para>¦b CPU ¤¤¦³¤@ºØ¯S§Oªº¸ê®Æ´²¼ö¾¹¡A§Q¥Î±Æ¥X´²¼ö¤ù/­·®°²Õ¦X®É¡A
 	    Âà´«¦¨¼ö¯à¡D³o´N¬O¬°¤°»ò CPU §N«o¤éÁÍ­«­nªº­ì¦]¡F·í¤H­Ì¨Ï¥Î§ó§Ö
 	    ªº³B²z¾¹®É¡A¥L­ÌÅܦ¨¤£¦b¥G¦³¶V¨Ó¶V¦h¥L­Ìªº¸ê®Æ³£°e¶i¤F
 	    <filename>/dev/null</filename> ¡A¦Ó¨Ïªº¥L­Ìªº CPU ¹L¼ö¡D
 	    ¦pªG§A§R°£¤F <filename>/dev/null</filename> (¨º±N·|¦³®ÄªºÃö³¬
 	    CPU ªº¸ê®Æ´²¼ö¾¹) §Aªº CPU ¤]³\·|­°§C¤u§@·Å«×¡A¦ý¬O§Aªº¨t²Î±N
 	    ·|«Ü§Öªº¹³¬O¿©±w¤F«K¯µ¦ñÀHµÛ©Ò¦³¶W¥Xªº¸ê®Æ¶}©lÅܦ¨¦æ¬°¤£¥¿±`¡C
 	    ¦pªG§A¦³§Ö³tªººô¸ô³s½u¡A§A¥i¥H§Q¥ÎŪ¨ú
 	    <filename>/dev/random</filename> ¨Ã±N¥LÀH·N¶Ç°e¦Ü¦U³B¡A
 	    ¨Ó­°§C§A CPU ªº·Å«×¡FµM¦Ó§A±N³´¤J¨Ï§Aºô¸ô³s½u©Î
 	    <filename>/</filename> ¦³¹L¼öªº­·ÀI©Î¬O·S´o§Aªº ISP¡A
 	    ¤j³¡¤Àªº¸ê®Æ³Ì²×±N·|¦b¥L­Ìªº³]³Æ¤WÂà´«¦¨¼ö¡A¤£¹L¥L­Ì³q±`³£¾Ö¦³
 	    ¦nªº´²¼ö¡A©Ò¥H¦pªG§A°µªº¤£¤Ó¹L¤À¡AÀ³¸Ó¬O¨S¤°»ò¤j¤£¤Fªº¡C</para>
 
 	  <para><emphasis>Paul Robinson ¸É¥R¡G</emphasis></para>
 
 	  <para>¤¤¤åª© FAQ ª`¡G¥H¤Uµu¤åÄÝ©ó¬ü¦¡«ÕÀq¡A®£Â½Ä¶«á³y¦¨»y²j¤£¸Ô¡A
 	    »y·N¤£³qªº±¡§Î¡A©T«O¯d­ì¥Ä­ì¨ýÅýŪªÌ¦Û¦æ«~À|¡C</para>
 	
 	  <para>There are other methods. As every good sysadmin knows,
             it is part of standard practise to send data to the screen
             of interesting variety to keep all the pixies that make up
             your picture happy. Screen pixies (commonly mis-typed or
             re-named as 'pixels') are categorised by the type of hat
             they wear (red, green or blue) and will hide or appear
             (thereby showing the colour of their hat) whenever they
             receive a little piece of food. Video cards turn data into
             pixie-food, and then send them to the pixies - the more
             expensive the card, the better the food, so the better
             behaved the pixies are. They also need constant simulation
             - this is why screen savers exist.</para>
 
           <para>To take your suggestions further, you could just throw
             the random data to console, thereby letting the pixies
             consume it. This causes no heat to be produced at all,
             keeps the pixies happy and gets rid of your data quite
             quickly, even if it does make things look a bit messy on
             your screen.</para>
 
           <para>Incidentally, as an ex-admin of a large ISP who
             experienced many problems attempting to maintain a stable
             temperature in a server room, I would strongly discourage
             people sending the data they do not want out to the
             network. The fairies who do the packet switching and
             routing get annoyed by it as well.</para>
 	</answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter id="advanced">
     <chapterinfo>
       <author>
 	<firstname>En-Ran</firstname>
 	<surname>Zhou</surname>
 	<affiliation>
 	  <address><email>zhouer@tfcis.org</email></address>
 	</affiliation>
       </author>
     </chapterinfo>
 
     <title>¶i¶¥¥DÃD</title>
 
     <qandaset>
       <qandaentry>
         <question id="learn-advanced">
           <para>¦p¦ó¯à¾Ç²ß§ó¦h¦³Ãö FreeBSD ¤º³¡ªºªF¦è¡H</para>
         </question>
 
         <answer>
           <para>¥Ø«e¥«­±¤WÁÙ¨S¦³±´°Q§@·~¨t²Î¤º³¡ªº®Ñ¬O±M¬° FreeBSD ¦Ó¼g
 	    ªº¡CµM¦Ó¡A³\¦h¤@¯ëªº UNIX ª¾Ãѳ£¥i¥Hª½±µÀ³¥Î¦b FreeBSD ¤W¡Cªþ
 	    ¥[¤@ÂI¡A¤´µM¦³¬ÛÃöªº®Ñ¬O±M¬° BSD ©Ò¼gªº¡C</para>
 
           <para>½Ð°Ñ¦Ò Handbook ªº<ulink
 	    URL="../handbook/bibliography-osinternals.html">§@·~¨t²Î¤º³¡¤§°Ñ¦Ò®Ñ¥Ø</ulink>
 	    ¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
 	<question id="how-to-contribute">
 	  <para>¦p¦ó¯à¬° FreeBSD ¥X¤@¥÷¤O¡H</para>
 	</question>
 
 	<answer>
 	  <para>½Ð°Ñ¦Ò³o½g¤å³¹ <ulink
 	    url="../../articles/contributing/article.html">Contributing
 	    to FreeBSD</ulink> ¨Ó´£¨Ñ±zªº«Øij¡C¦pªG±z¯àÀ°¦£¨º´N§óÅwªï¤F¡I</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
         <question id="define-snap-release">
           <para>SNAP ©M RELEASE ¬O¤°»ò¡H</para>
         </question>
 
         <answer>
           <para>¥Ø«e¦³¤T­Ó¬¡ÅD/¥b¬¡ÅDªº¤À¤ä¦b FreeBSD ªº <ulink
 	    URL="http://www.FreeBSD.org/cgi/cvsweb.cgi">CVS Repository</ulink>
 	    (RELENG_2 ¤À¤ä¤@¦~¤j·§§ó°Ê¨â¦¸¡A¥¿¬O¬°¦ó¥u¦³¤T­Ó¬¡ÅDªºµo®i¤¤¤À¤ä)¡G
 	    </para>
 
             <itemizedlist>
               <listitem>
                 <para><literal>RELENG_2_2</literal> §Y
                   <emphasis>2.2-STABLE</emphasis></para>
               </listitem>
 
               <listitem>
                 <para><literal>RELENG_3</literal> §Y
                   <emphasis>3.X-STABLE</emphasis></para>
               </listitem>
 
               <listitem>
                 <para><literal>RELENG_4</literal> §Y
                   <emphasis>4-STABLE</emphasis></para>
               </listitem>
 
               <listitem>
                 <para><literal>HEAD</literal> §Y
                   <emphasis>-CURRENT</emphasis> §Y
                   <emphasis>5.0-CURRENT</emphasis></para>
               </listitem>
 
             </itemizedlist>
 
           <para>¦p¦P¨ä¥L¨â­Ó¡A<literal>HEAD</literal> ¨Ã¤£¬O¯u¥¿
 	    ªº branch tag¡A¥¦¥u¬O¤@­Ó²Å¸¹±`¼Æ¡A«ü¦V <quote><emphasis>current
 	    (©|¥¼¤À¤äªºµo®i¤¤ª©¥»)</emphasis></quote> ²°O¬°
 	    <quote>-CURRENT</quote>¡C</para>
 
           <para>¥H²{¦b¨Ó»¡¡A<quote>-CURRENT</quote> ´Â¦V 5.0 µo®i¡A¦Ó
 	    <literal>4-STABLE</literal> ¤À¤ä¡A¤]´N¬O
 	    <symbol>RELENG_4</symbol>¡A¦b 2000 ¦~¤T¤ë±q
 	    <quote>-CURRENT</quote> ¤À¤ä¥X¨Ó¡C</para>
 
           <para><literal>2.2-STABLE</literal> ³o­Ó¤À¤ä¡A¤]´N¬O
 	    <symbol>RELENG_2_2</symbol>¡A¦b 1996 ¦~¤Q¤@¤ë±q -CURRENT ¤À¤ä¥X
 	    ¨Ó¡A³o­Ó¤À¤ä¥Ø«e¤w¸g§¹¥þ°h¥ð¤F¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="custrel">
           <para>­n«ç»ò§@¥X¦Û¤vªº release¡H</para>
         </question>
 
         <answer>
           <para>½Ð°Ñ·Ó <ulink
             url="../../articles/releng/article.html">Release ¤uµ{</ulink>
 	    ¤å³¹»¡©ú¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="makeworld-clobbers">
           <para>¬°¤°»ò <command>make world</command> §â­ì¨Ó¸Ëªº binary ÀÉ
 	    ³£´«±¼¤F¡H</para>
         </question>
 
         <answer>
           <para>¨S¿ù¡A´N¬O³o¼Ë¤l¡C¦p¦W¦r©Ò¥Ü¡A<command>make world</command>
 	    ·|­«·s½sĶ¨t²Î¤º«Øªº¨C­Ó binary ÀÉ¡A³o¼Ë¦bµ²§ô®É´N¥i½T©w¦³­Ó¤@­P
 	    ¥B°®²bªºÀô¹Ò(©Ò¥H­nªá¤W¦n¤@¬q®É¶¡)¡C</para>
 
           <para>¦b°õ¦æ <command>make world</command> ©Î
 	    <command>make install</command> ®É¡A¦pªG¦³³]
 	    <literal>DESTDIR</literal> ³o­ÓÀô¹ÒÅܼơA·s²£¥Íªº binary ±N·|¸Ë¦b
 	    <literal>${DESTDIR}</literal> ¤U¦P¼Ëªº¥Ø¿ý¾ð¤¤¡C¦ý¦b¬Y¨Ç­×§ï
 	    shared library ©M­««Ø binary ªºµL¯S©w±¡ªp¤U¡A³o¼Ë°µ¥i¯à·|¨Ï
 	    <command>make world</command> ¥¢±Ñ¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="bus-speed-defaulted">
           <para>¦b¨t²Î¶}¾÷®É¡A¥X²{ <quote>(bus speed defaulted)</quote>¡C</para>
         </question>
 
         <answer>
 
           <para>Adaptec 1542 SCSI ¥d¤¹³\¨Ï¥ÎªÌ¥Î³nÅé½Õ¾ã¶×¬y±Æªº¦s¨ú³t«×¡C
 	    ¦­´Áªº 1542 ÅX°Êµ{¦¡¸Õ¹Ï±N¥¦³]¦¨¥i¥Îªº³Ì§Ö³t«×¡A¦ý«á¨Óµo²{¦b¤@
 	    ¨Ç¾÷¾¹¤W¤£¯à¥Î¡A©Ò¥H²{¦b­n¦b kernel ³]©w¤¤¥[
 	    <symbol>TUNE_1542</symbol> ³o­Ó¿ï¶µ¨Ó±Ò°Ê³o­Ó¥\¯à¡C¦b¤ä´©ªº¾÷¾¹
 	    ¤W¥Î³o­Ó¿ï¶µ·|¨ÏµwºÐ¦s¨ú§ó§Ö¡A¦ý¦b¤£¤ä´©ªº¾÷¾¹¤W¦³¥i¯à·|·´±¼¸ê®Æ¡C
 	    </para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="ctm">
           <para>¦bºô¸ôÀW¼e¦³­­ªº±¡ªp¤U¡A§Ú¤]¥i¥H¸ò¤W current ªºµo®i¶Ü¡H</para>
         </question>
 
         <answer>
           <para>¬Oªº¡AÂÇµÛ <ulink URL="../handbook/synching.html#CTM">CTM
 	  </ulink> ±z´N¥i¥H<literal>¤£¥Î</literal>¤U¸ü¥þ³¡ªºµ{¦¡½X¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="split-240k">
           <para>¬O«ç»ò§âµo¦æª©¥»¤¤ªºÀɮפÁ¦¨¤@­Ó­Ó 240k ªº¤pÀɮתº¡H</para>
         </question>
 
         <answer>
           <para>¥H BSD ¬°°ò¦ªº¸û·s¨t²Î¦³­Ó <option>-b</option> ¿ï¶µ
 	  ¥i¥H§âÀÉ®×¥H¥ô·N¼Æ¥Ø byte ¤Á¶}¡C</para>
 
           <para>³o¸Ì¬O <filename>/usr/src/Makefile</filename> ¤¤ªº¤@­Ó
 	  ¨Ò¤l¡G</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>§Ú¦b kernel ¤¤¥[¤F·s¥\¯à¡A§Ú­n§â¥¦±Hµ¹½Ö¡H</para>
         </question>
 
         <answer>
           <para>½Ð°Ñ¦Ò <ulink
 	    URL="../../articles/contributing/article.html">Contributing
             to FreeBSD</ulink> ¤¤ªº¤å³¹¡A¥H¤F¸Ñ­n¦p¦ó´£¨Ñ±zªºµ{¦¡½X¡C</para>
 
           <para>¦P®É¤]ÁÂÁ±zªºÃö¤ß¡I</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="pnp-initialize">
           <para>ISA ªºÀH´¡§Y¥Î¥d¬O¦p¦ó°»´ú¤Îªì©l¤Æªº¡H</para>
         </question>
 
         <answer>
           <para>¥Ñ Frank Durda IV ©Ò¼g¡G
             <email>uhclem@nemesis.lonestar.org</email></para>
 
           <para>²³æªº»¡¡A·í¥D¾÷µo¥X¬O§_¦³ PnP ¥dªº¸ß°Ý°T¸¹®É¡A©Ò¦³ªº PnP ¥d
 	    ·|¦b´X­Ó©T©wªº I/O port §@¦^À³¡C©Ò¥H·í°»´ú PnP ªºµ{¦¡¶}©l®É¡A¥¦
 	    ·|¥ý°Ý¦³¨S¦³ PnP ¥d¦b¡A±µµÛ©Ò¦³ PnP ¥d·|¦b¥¦Åªªº port ¥H¦Û¤vªº
 	    «¬¸¹ # §@¦^µª¡A³o¼Ë°»´úµ{¦¡´N·|±o¨ì¤@­Ó wired-OR <quote>yes</quote>
 	    ªº¼Æ¦r¡A¨ä¤¤¦Ü¤Ö·|¦³¤@­Ó bit ¬O¥´¶}ªº¡CµM«á°»´úµ{¦¡·|­n¨D«¬¸¹
 	    (¥Ñ Microsoft/Intel«ü©w)¤p©ó X ªº¥d<quote>Â÷½u</quote>¡C¦A¥h¬Ý¬O
 	    §_ÁÙ¦³¥d¦^µª¦P¼Ëªº¸ß°Ý¡A¦pªG±o¨ì <literal>0</literal>¡A´Nªí¥Ü¨S
 	    ¦³«¬¸¹¤j©ó X ªº¥d¡C ²{¦bµ{¦¡·|°Ý¬O§_¦³«¬¸¹¤p©ó <literal>X</literal>
 	    ªº¥d¡A¦pªG¦³ªº¸Ü¡Aµ{¦¡¦A­n«¬¸¹¤j©ó X-(limit/4) ªº¥dÂ÷½u¡AµM«á­«ÂÐ
 	    ¤W­±ªº°Ê§@¡C¥Î­«½Æ³oºØÃþ¦ü semi-binary search ªº¤èªk¡A¦b¬Y½d³ò¤º
 	    §ä­Ó´X¦¸«á¡A´úµ{¦¡³Ì«á·|¦b¾÷¾¹¤¤°Ï¤À¥X©Ò¦³ªº PnP ¥d¡A·j´M¦¸¼Æ¤]
 	    »·§C©ó¤@­Ó­Ó§äªº 2^64 ¦¸¡C</para>
 
           <para>¤@±i¥dªº ID ¥Ñ¨â­Ó 32-bit(©Ò¥H¤W­±¬O 2&circ;64) + 8bit °»¿ù½X
 	    ²Õ¦¨¡A²Ä¤@­Ó 32 bits ¬O¥Î¨Ó°Ï¤À¦U®a¼t°Óªº¡C³o¨Ç¼t°Ó±q¨Ó¨S¦³¥X¨Ó¼á
 	    ²M¹L¡A¦ý¬Ý¨ÓÀ³°²³]¦P¤@®a¥Xªº¤£¦PºØÃþªº¥dªº¼t°Ó ID ¦³¥i¯à¤£¦P¡C¥Î
 	    32 bits ¥u¨Óªí¥Ü¤£¦P¼t°Óªº·Qªk¹ê¦b¦³ÂI¹LÀY¤F¡C</para>
 
           <para>²Ä¤G­Ó 32 bits «h¬O«¬¸¹ #¡B¤A¤Óºô¸ô¦ì§}¡B©Î¤@¨Ç¨Ï³o±i¥d¿W¯Sªº
 	    ¸ê®Æ¡C°£«D²Ä¤@­Ó 32 bits ¤£¦P¡A§_«h¼t°Ó¤£¥i¯à§@¥X²Ä¤G­Ó 32 bit ¬Û
 	    ¦Pªº¨â±i¥d¡C©Ò¥H¦b¤@¥x¾÷¾¹¤¤¥i¥H¦³¦P¼Ëªº¦n´X±i¥d¡AµM¦Ó¥L­Ì¾ã­Ó
 	    64 bits ÁÙ¬O·|³£¤£¤@¼Ë¡C</para>
 
           <para>³o¨â­Ó 32 bit µ´¹ï¤£¥i¥H¥þ¬°¹s¡A³o¤~¯à¨Ï±o³Ì¶}©l binary search
 	    ¤¤ªº wired-OR ·|±o¨ì¤@­Ó«D¹s¼Æ¦r¡C</para>
 
           <para>¤@¥¹¨t²Î°Ï¤À¥X©Ò¦³¥dªº ID¡A±µµÛ·|¸g¥Ñ¦P¼Ëªº I/O port ¤@­Ó­Ó­«
 	    ·s±Ò°Ê¨C±i¥d¡A±µµÛ§ä¥X¤wª¾¤¶­±¥d©Ò»Ýªº¸ê·½¡B¦³­þ¨Ç¤¤Â_¥i¥H¨Ï¥Îµ¥
 	    µ¥¡C©Ò¦³¥d³£·|³Q±½´y¤@¦¸¡A¨Ó¦¬¶°³o¨Ç¸ê®Æ¡C</para>
 
           <para>³o¨Ç¸ê°T±µµÛ©MµwºÐ¤Wªº ECU ÀɮסB©Î MLB BIOS ¸Ìªº¸ê®Æµ²¦X¦b¤@
 	    °_¡A³q±`¬Oºî¦X ECU ©M MLB ¸Ìªº BIOS PnP ¸ê®Æ¡A³o¨Ç¶gÃä¨Ã¤£¤ä´©¯u¥¿
 	    ªº PnP¡AµM¦Ó°»´úµ{¦¡¦bÀˬd BIOS ©M ECU ¸ê®Æ«á¡A¥¦¥i¥HÁקK PnP ¶gÃä
 	    ©M¨º¨Ç°»´ú¤£¨ìªº¬Û½Ä¬ð¡C</para>
 
           <para>±µµÛ¦A«×«ô³X³o¨Ç PnP ¶gÃä¡A³o¦¸·|§â¥i¥Îªº I/O¡BDMA¡BIRQ ©M°O¾Ð
 	    Åé¬M®gªº¦ì§}³£«ü©wµ¹¥¦­Ì¡C³o¨Ç¶gÃä´N·|¥X²{¦b©Ò«ü©wªº¦a¤è¡Aª½¨ì¤U¤@
 	    ¦¸­«·s¶}¾÷¬°¤î¡A¤£¹L¤]¨S¦³¤H»¡¤£¯à§â¥¦­ÌÀH®É²¾¨Ó²¾¥h¡C</para>
 
           <para>¤W­±¦³¬Û·í¦hªºÂ²¤Æ¡A¦ý§AÀ³¸Ó¤w¸g¤F¸Ñ¤j­Pªº¹Lµ{¡C</para>
 
           <para>Microsoft §âªí¥Ü¦Lªí¾÷ª¬ºAªº´X­Ó¥D­n port ®³¨Ó§@ PnP¡A¥L­Ìªº
 	    ÅÞ¿è¬O¨S¦³¤@±i¥d·|¦b³o¨Ç¦a¤è¸Ñ½X§@¬Û¤Ïªº I/O cycles¡C¦ý¬O§Ú§ä¨ì
 	    ¤@´Ú¦­´Á¤´¦bµû¦ô PnP ´£®×®Éªº IBM ­ì¼t printer board¡A¥¦ªº½T¥h¸Ñ
 	    ¹ï³o¨Çª¬ºA port ªº¼g¤J¸ê®Æ¡A¦ý¬O MS <quote>»¡¤F´Nºâ</quote>¡C©Ò¥H
 	    ¥¦­Ìªº½T¦³¹ï¦Lªí¾÷ª¬ºA port ¼g¤J¡AÁÙ¦³Åª¨ú¸Ó¦ì§} +
 	    <literal>0x800</literal>¡B©M¥t¤@­Ó¦b <literal>0x200</literal> ¤Î
 	    <literal>0x3ff</literal> ¤§¶¡ªº port¡C</para>
 
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="major-numbers">
           <para>§Ú¬°¬Y³]³Æ¼g¤FÅX°Êµ{¦¡¡A¯à¤£¯àµ¹¥¦¤@­Ó major number¡H</para>
         </question>
 
         <answer>
           <para>³o­n¬Ý§A¬O§_¥´ºâ±N³o­ÓÅX°Êµ{¦¡¤½¶}¨Ï¥Î¡A¦pªG¬Oªº¸Ü¡A½Ð§â¥¦ªº
 	    ­ì©l½X°e¤@¥÷µ¹§Ú­Ì¡AÁÙ¦³ <filename>files.i386</filename> ­×§ïªº
 	    ³¡¥÷¡Bkernel ³]©wÀɼ˥»¡B¥H¤Î¥Î¨Ó²£¥Í³]³ÆÀɪº &man.MAKEDEV.8;¡C
 	    ¦pªG§A¤£¥´ºâ¤½¶}¡B©Î¦]¬°ª©Åv°ÝÃD¦Ó¤£¯à¤½¶}ªº¸Ü¡A§Ú­Ì¦³¯S¦a«O¯d
 	    character major number 32 ©M block major number 8 µ¹³o¤è­±ªº¨Ï¥Î¡A
 	    ª½±µ¥Î³o¨â­Ó´N¦n¤F¡C¤£½×¦p¦ó¡A§Ú­Ì³£·|«Ü·P¿E§A¯à¦b &a.hackers;
 	    µoªíÅX°Êµ{¦¡ªº®ø®§¡C</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="alternate-directory-layout">
           <para>Ãö©ó§ó°Ê¥Ø¿ý©ñ¸mªº­ì«h¡H</para>
         </question>
 
         <answer>
           <para>¦b¦^µªÃö©ó§ó°Ê¥Ø¿ý©ñ¸mªº­ì«h¤è­±¡A§Ú¦b 1983 ¦~¼g¦n¥Ø«eªº§@ªk
 	    «á´N¨S¦³¦A§ïÅܹL¡A³oºØ¤è¦¡¬O°w¹ï­ì¥ýªº FFS Àɮרt²Î¡A«á¨Ó¤]¨S¦³
 	    ¹ï¥¦§@¥ô¦ó§ó°Ê¡C¥¦¦bÁקK cylinder group ³Q¶ñº¡³o¤è­±°µ±o¬Û·í¦¨¥\¡A
 	    ¦ý¬O´N¹³¦³¨Ç¤H¤w¸gª`·N¨ì¡A¥¦©M find ´N°t¦X±o¤£¤j¦n¡C¤j³¡¥÷ªºÀÉ®×
 	    ¨t²Î¬O¥Ñ¨º¨Ç¥Î depth first search(aka ftw) ²£¥Íªº archive »s³y¥X
 	    ¨Ó¡A¸Ñ¥X¨Óªº¥Ø¿ý inode ·|¾î¸ó¦n´X­Ó cylinder group¡A¦pªG¥H«á­n°µ
 	    depth first search ªº¸Ü¡A³o¬O³ÌÁV¿|ªº±¡ªp¤§¤@¡C¦pªG§Ú­Ìª¾¹DÁ`¦@
 	    ·|²£¥Í¦h¤Ö¥Ø¿ýªº¸Ü¡A¸Ñªk¬O¦b°µ¥ô¦ó¦s¨ú/¼g¤J°Ê§@¤§«e¡A¦b¨C­Ó
 	    cylinder group ¤W¥ý³y¥X(©Ò¦³¥Ø¿ý¼Æ/cylinder greoup ªº¼Æ¥Ø)³o»ò¦h
 	    ªº¥Ø¿ý¡C«Ü©úÅ㪺¡A§Ú­Ì¥²¶·­n¦³®Ú¾Ú¦a¥h²q³o ­Ó¼Æ¦r¡A´Nºâ¤@­Ó¹³ 10
 	    ªº«Ü¤p©T©w¼Æ¥Ø¤]·|¨Ï®Ä²v¥H¯Å¼Æ¦¨ªø¡C°Ï¤À restore (§Y¸Ñ¶}¤W­zªº
 	    archive) ©M¤@¯ëÀÉ®×¾Þ§@ªº¤èªk¥i¥H¬O(²{¦b¥Îªººtºâªk¥i¯à­n§ó±Ó·P)¡G
 	    ¦pªG¤@¨Ç¥Ø¿ý(³Ì¦h 10 ­Ó)³£¦b 10 ¬í¤º²£ ¥Íªº¸Ü¡A¨º»ò´N§â³o¨Ç¥Ø¿ý
 	    »E¶°¦b¦P¤@­Ó cylinder group¡C¤£ºÞ«ç¼Ë¡A §Úªº¸gÅç«ü¥X³o¬O¤@­Ó¤w¸g
 	    ¥R¥÷¹êÅç¹Lªº³¡¥÷¡C</para>
 
           <para>Kirk McKusick, September 1998</para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="kernel-panic-troubleshooting">
           <para>¦p¦ó¦b kernel panics ®É±o¨ì³Ì¦hªº¸ê°T¡H</para>
         </question>
 
         <answer>
           <para><emphasis>[³o¸`¬O±q &a.wpaul; ¦b freebsd-current <link
 	    linkend="mailing">mailing list</link> ¤Wµoªíªº«H¤¤¸`¿ý¡A
 	    &a.des; ­×¥¿¤F¥´¦r¿ù»~¡B¦A¥[¤W¬A©·¸Ìªºª`¸Ñ¡C]</emphasis></para>
 
           <programlisting>From: Bill Paul &lt;wpaul@skynet.ctr.columbia.edu&gt;
 Subject: Re: the fs fun never stops
 To: Ben Rosengart
 Date: Sun, 20 Sep 1998 15:22:50 -0400 (EDT)
 Cc: current@FreeBSD.org</programlisting>
 
           <para><emphasis>[Ben µoªí¤F¤U­±ªº panic °T®§]</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>·í§A¬Ý¨ì¹³³o¼Ëªº°T®§®É¡A¥u§â¥¦«þ¤@¥÷°e¤W¨Ó¬O¤£°÷ªº¡C§Ú¦b¤W­±
 	    ¯S¦a¼Ð©úªº instruction pointer ­È¬Û·í­«­n¡A¤£©¯ªº¬O¥¦·|¦]³]©w¦Ó
 	    ¤£¦P¡C´«¥y¸Ü»¡¡A³o­Ó­È·|¸ò§A¥Îªº kernel image ÀɦÓÅÜ°Ê¡C¦pªG¬O¥Î
 	    ¬Y­Ó snapshot ª©¥»ªº GENERIC kernel¡A¤]³\¨ä¥L¤H¥i¥H°lÂܨì¥X°ÝÃD
 	    ªº¨ç¦¡¡A¦ý¦pªG§A¬O¥Î¦Û­qªº kernel¡A¨º»ò¥u¦³ 
 	    <emphasis>§A</emphasis>¤~¯à§i¶D§Ú­Ì°ÝÃD¥X¦b¨º¸Ì¡C</para>
 
           <para>­n°µªº¨Æ¥]¬A³o¨Ç¡G</para>
 
             <procedure>
               <step>
                 <para>§â instruction pointer ªº­È°O¤U¨Ó¡Cª`·N¦b«e­±ªº
 		  <literal>0x8:</literal> ¦b³o­Ó±¡ªp¤¤¨Ã¤£­«­n¡A§Ú­Ì­nªº¬O
 		  <literal>0xf0xxxxxx</literal>¡C</para>
               </step>
 
               <step>
                 <para>·í¨t²Î­«·s¶}¾÷«á¡A°õ¦æ³o¹D©R¥O¡G
 
                   <screen>&prompt.user; <userinput>nm -n /(³y¦¨ panic ªº kernel ÀÉ®×) | grep f0xxxxxx</userinput></screen>
 
 		  ¨ä¤¤ <literal>f0xxxxxx</literal> ´N¬O°O¤U¨Óªº
 		  instruction pointer ­È¡C¦³¥i¯à¤£·|­è¦n§ä¨ì§¹¾ãªº³o­Ó¦r¦ê¡A
 		  ³o¬O¦]¬° kernel symbol table ¸Ìªº¦U­Ó symbol ¥u¬O¨ç¦¡ªº¶i
 		  ¤JÂI¡A¦ý instruction pointer ©Ò«üªº¦ì§}¦³¥i¯à¬O¦b¨ç¦¡¤ºªº
 		  ¬Y¤@³B¡A¦Ó¤£¤@©w¦b¶}ÀY¡C©Ò¥H¦pªG§ä¤£¨ì¾ã­Ó¦r¦ê¡A¨º»ò§â
 		  instruction pointer ­Èªº³Ì«á¤@­Ó¼Æ¦r®³±¼¡A¦A¸Õ¤@¦¸¡G
 
                   <screen>&prompt.user; <userinput>nm -n /(³y¦¨ panic ªº kernel ÀÉ®×) | grep f0xxxxx</userinput></screen>
 
                   ¦pªG³o¼Ë¤]§ä¤£¨ì¡A¨º´N§â¥t¤@­Ó¼Æ¦r¥h±¼¦A§ä¡A¤@ª½­«½Æ¨ì§ä¨ì
 		  ¬°¤î¡A µ²ªG¬O¤@¦ê¥i¯à³y¦¨ panic ªº¨ç¦¡¦Cªí¡C³o¼Ë¤ñª½±µ§ä¨ì
 		  ¥X°ÝÃDªº¨ç¦¡¨Ó±o®t¡A¦ý¦Ü¤Ö¦n¹L¤°»ò³£¨S¦³¡C</para>
 
               </step>
             </procedure>
 
           <para>§Ú±`±`¬Ý¨ì¤H­ÌÅã¥Ü¤@¤j¤ù panic °T®§¡A¦ý«Ü¤Ö¬Ý¨ì¦³¤Hªá¤@ÂI®É¶¡
 	    §â instruction pointer ©M kernel symbol table ¤¤ªº¨ç¦¡¤ñ¸û¤@¤U¡C
 	    </para>
 
           <para>­n°lÂÜ¥X³y¦¨ panic ­ì¦]ªº³Ì¦n¤èªk¬O¥ý°µ¥X crash dump¡AµM«á¥Î
 	    &man.gdb.1; ¦b¤W­±°µ stack trace¡C</para>
 
           <para>¤£ºÞ¬O¨º¤@ºØ¡A§Ú³q±`¬O¥Î³o­Ó¤èªk¡G</para>
 
             <procedure>
               <step>
                 <para>¼g¦n kernel ³]©wÀÉ¡C¦pªG§A»Ý­n¥Î kernel debugger¡A¦b³]
 		  ©wÀɤ¤¥[¤W <literal>options DDB</literal> ³o­Ó¿ï¶µ¡C
 		  (·í§ÚÃhºÃ¦³¥X²{µL½a°j°é®É¡A³q±`·|¥Î³o­Ó¨Ó³]©w¤¤Â_ÂI¡C)
 		  </para>
               </step>
 
               <step>
                 <para>¥Î <command>config -g
 		  <replaceable>KERNELCONFIG</replaceable></command>
 		  °µ¥X¥Î¨Ó½sĶªº¥Ø¿ý¡C</para>
               </step>
 
               <step>
                 <para><command>cd /sys/compile/
                   <replaceable>KERNELCONFIG</replaceable>; make
                   </command></para>
               </step>
 
               <step>
                 <para>µ¥«Ý kernel ½sĶµ²§ô¡C</para>
               </step>
 
               <step>
                 <para><command>make install</command></para>
               </step>
 
               <step>
                 <para>­«·s¶}¾÷</para>
               </step>
             </procedure>
 
           <para>&man.make.1; ±N·|»s³y¥X¨â­Ó kernel¡C<filename>kernel</filename>
 	    ÁÙ¦³ <filename>kernel.debug</filename>¡C
 	    <filename>kernel</filename> ±N·|³Q¦w¸Ë¨ì
 	    <filename>/kernel</filename>¡A¦Ó <filename>kernel.debug</filename>
 	    ¥i¥Î¨Óµ¹ &man.gdb.1; ·í§@ debugging symbols ªº¨Ó·½¡C</para>
 
           <para>­n½T©w¯à§ì¨ì crash dump¡A¥ý½s¿è
 	    <filename>/etc/rc.conf</filename> ±N <literal>dumpdev</literal> «ü
 	    ¨ì swap ¤À³Î°Ï¡C³o¼Ë &man.rc.8; ·|¥Î &man.dumpon.8; ¨Ó±Ò°Ê
 	    crash dump¡A§A¤]¥i¥H¤â°Ê°õ¦æ &man.dumpon.8; ¦b panic ¤§«á¡A
 	    crash dump ¥i¥H¥Î &man.savecore.8; ¦s°_¨Ó¡F¦pªG
 	    <filename>/etc/rc.conf</filename> ¸Ì¦³³] <literal>dumpdev</literal>
 	    ¨º»ò­«·s¶}¾÷«á &man.rc.8; ·|¦Û°Ê°õ¦æ &man.savecore.8; §â
 	    crash dump ¦s¦b <filename>/var/crash</filename>¡C</para>
 
             <note>
               <para>FreeBSD ªº crash dump ³q±`©M¾÷¾¹¸Ìªº¹ê»Ú°O¾ÐÅé¤@¼Ë¤j¡A´N
 	        ¹³¦pªG¦³ 64MB °O¾ÐÅé¡Acrash dump ¤j¤p´N¬O 64MB¡C©Ò¥H­n½T©w
 		<filename>/var/crash</filename> ¤U¦³¨¬°÷ªºªÅ¶¡¡A©Î¬O¥i¥H¤â
 		°Ê°õ¦æ &man.savecore.8; §â crash dump ©ñ¨ì¥t¤@­ÓªÅ¶¡¸û°÷ªº
 		¥Ø¿ý¤U¡C¥t¤@ºØ¤]³\¥i¥H­­¨î crash dump ªº¤èªk¡A¬O¦b kernel
 		³]©wÀɤ¤¥Î <literal>options MAXMEM=(foo)</literal>¡A±N kernel
 		¥i¥Îªº°O¾ÐÅé­­¨î¦b¦X²zªº¤j¤p¡CÁ|¨Ò¨Ó»¡¡A¦pªG§A¦³ 128MB ªº°O¾Ð
 		Åé¡A¦ý¬O¥i¥H­­¨î kernel ¥u¯à¥Î 16MB ªº°O¾ÐÅé¡A³o¼Ë crash dump
 		´N¬O 16MB ¦Ó¤£¬O 128MB ¤F¡C</para>
             </note>
 
           <para>¤@¥¹µo²{¦³¤F crash dump¡A´N¥i¥H¥Î &man.gdb.1; ¨Ó°µ
 	    stack trace ¡A¦p¤U©Ò¥Ü¡G</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>­nª`·N¥i¯à·|¥X²{¦n´X­Ó¿Ã¹õªº¥i¥Î¸ê°T¡A§A¥i¥H¥Î &man.script.1;
 	    §â©Ò¦³¿é¥X³£¦s°_¨Ó¡C¥Î¥]¬A©Ò¦³ debug symbol ªº kernel ¨Ó°£¿ù¡A³o
 	    ¼ËÀ³¸Ó¥i¥Hª½±µÅã¥Ü panic ¬Oµo¥Í¦b¨º¤@¦æ¡C³q±`¬O¥Ñ¤U©¹¤WŪ
 	    stack strace¡A³o¼Ë¤~¯à¤@­Ó­Ó°lÂÜ¥X¦³­þ¨Ç°Ê§@¤Þ¨ì crash¡C¤]¥i¥H¥Î
 	    &man.gdb.1; §â¦UºØÅܼƩε²ºcªº¤º®e¦L¥X¨Ó¡A¥HÀˬd¨t²Î crash ®Éªº
 	    ¹ê»Úª¬ºA¡C</para>
 
           <para>¦n°Õ¡A¦pªG§A¦³²Ä¤G¥x¹q¸£¦Ó¥B¦³°÷ºÆ¨g¡A¥i¥H±N &man.gdb.1; ³]©w
 	    ¦¨»·ºÝ°£¿ù¡C³o¼Ë§A¥i¥H¦b¤@¥x¾÷¾¹¤¤¥Î &man.gdb.1; ¥h°£¿ù¥t¤@¥x¸Ìªº
 	    kernel¡A¥i¥H°õ¦æªº¥]¬A³]©w¤¤Â_ÂI¡B¦b kernel ­ì©l½X¤¤¤@¨B¨B°õ¦æµ¥
 	    µ¥¡A´N¹³¦b¤@¯ë¨Ï¥ÎªÌµ{¦¡¤W°£¿ù¤@¼Ë¡C¥Ñ©ó¨S¦³¤°»ò¾÷·|¬°°£¿ù¦Ó³]¸m
 	    ¨â¥x¨Ã¾F¹q¸£¡A©Ò¥H§ÚÁÙ¨S¦³³o¼Ëª±¹L¡C</para>
 
           <para><emphasis>[Bill ¸É¥R¡G"§Ú§Ñ¤F´£¨ì¤@ÂI¡G¦pªG§A¦³±Ò°Ê DDB ¦Ó
 	    kernel ¤]¤w¸g¶i¤J°£¿ù¾¹¡A¥i¥H¦b DDB ©R¥O¦C¤U¥´ 'panic'¡A±j­¢²£¥Í
 	    panic (ÁÙ¦³ crash dump)¡C¤]¦³¥i¯à¦b panic ¶¥¬q®É¦A¶i¤J°£¿ù¾¹¡A
 	    ¦pªG³o¼Ëªº¸Ü¡A¿é¤J 'continue'¡A±µµÛ¥¦´N·|§¹¦¨ crash dump¡C" -ed]
 	    </emphasis></para>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="dlsym-failure">
           <para>¬°¤°»ò dlsym() ¤£¯à¾Þ§@ ELF °õ¦æÀÉ¡H</para>
         </question>
 
         <answer>
           <para>¦b ELF ¤@¨t¦Cªº¤u¨ã¤¤¡A¤º©w¬O¤£·|Åý dynamic linker ¬Ý¨ì°õ¦æ
 	    Àɸ̩w¸q¤F­þ¨Ç symbol¡C©Ò¥H <function>dlsym()</function> ¨S¦³¿ì
 	    ªk¥ÎÂǥѩI¥s <function>dlopen(NULL, flags)</function> ¨ú±oªº
 	    handle¡A¥Î¥¦¥h·j´M¦³¨º¨Ç symbol ¤@©w·|¥¢±Ñ¡C</para>
 	  
           <para>¦pªG§A·Q­n¥Î <function>dlsym()</function> §ä¥X¬Y­Ó process
 	    ªº¥D°õ¦æÀɤ¤¦³­þ¨Ç symbol¡A«h­n¦b link ®É¹ï ELF linker (&man.ld.1;)
 	    ¥[¤W <option>-export-dynamic</option> ³o­Ó°Ñ¼Æ¡C</para>
 
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question id="change-kernel-address-space">
           <para>§Ú­n¦p¦ó¼W¥[©Î´î¤Ö kernel ¯à©w§}ªºªÅ¶¡¡H</para>
         </question>
 
         <answer>
           <para>¹w³]­È¬O¡AFreeBSD 3.x ªº kernel ¥i¥H©w§}ªºªÅ¶¡¬O 256 MB ¦Ó
 	    FreeBSD 4.x ¥i¥H¨ì 1 GB¡C¦pªG¬Oºô¸ô­t²ü¬Û·í­«ªº¦øªA¾¹
 	    (¨Ò¦p¤j«¬ FTP ©Î HTTP ¦øªA¾¹)¡A§A¤]³\·|µo²{ 256 MB ¥i¯à¤£¤j°÷¡C
 	    </para>
 
           <para>©Ò¥H¡A­n¦p¦ó¼W¥[©w§}ªÅ¶¡©O¡H­n±q¨â¤è­±µÛ¤â¡C­º¥ý­º¥ý§i¶D
 	    kernel ¥»¨­­n«O¯d¸û¤jªÅ¶¡µ¹¦Û¤v¡C¨ä¦¸¡A¬JµM¬O¦b©w§}ªÅ¶¡ªº³Ì¤W
 	    ­±¸ü¤J kernel¡A©Ò¥HÁÙ­n½Õ§C¸ü¤Jªº¦ì§}¡A¤~¤£·|©M«e­±©w§}ªº½d³ò
 	    ­«Å|¡C</para>
 
           <para>¼W¥[ <filename>src/sys/i386/include/pmap.h</filename> ¸Ìªº
 	    <literal>NKPDE</literal> ´N¥i¥H¹F¦¨²Ä¤@­Ó¥Ø¼Ð¡C1 GB ªº©w§}ªÅ¶¡·|
 	    ¹³³o¼Ë¡G</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>­nºâ¥X <literal>NKPDE</literal> ªº¥¿½T­È¡A±N·Q­nªºªÅ¶¡¤j¤p
 	    (¥H megabyte ¬°³æ¦ì)°£¥H 4¡A±µµÛ³æ CPU ¾÷¾¹´î 1¡A
 	    Âù CPU «h¬O´î 2¡C</para>
 
           <para>­n¸Ñ¨M²Ä¤G­Ó°ÝÃD¡A¥²¶·¦Û¦æºâ¥X kernel ³Q¸ü¤Jªº¦ì§}¡G¨D¥X
 	    0x100100000 ´î±¼©w§}ªÅ¶¡¤j¤pªº­È(¥H byte ¬°³æ¦ì)¡A¦p 1 GB ¤j¤p´N¬O
 	    0xc0100000¡C§â<filename>src/sys/i386/conf/Makefile.i386</filename>
 	    ¸Ìªº <symbol>LOAD_ADDRESS</symbol> ³]¦¨³o­Ó­È¡Q±µµÛ¦b
 	    <filename>src/sys/i386/conf/kernel.script</filename> ¤¤¡A±N
 	    section ¦Cªí³Ì«e­±ªº location counter ³]¦¨¬Û¦Pªº­È¡A¦p¤U¡G</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>µM«á­«·s½sĶ±zªº kernel¡C±z¥i¯à·|¦b°õ¦æ &man.ps.1;¡B&man.top.1;
 	    ³oÃþªºµ{¦¡®É¸I¨ì°ÝÃD¡Q<command>make world</command> À³¸Ó´N¥i¥H¸Ñ¨M
 	    (©Î§â§ï¹Lªº <filename>pmap.h</filename> ½Æ»s¨ì
 	    <filename>/usr/include/vm/</filename> ¤U¡A¦A¤â°Ê½sĶ
 	    <filename>libkvm</filename>¡A&man.ps.1; ÁÙ¦³ &man.top.1;)¡C</para>
 
           <para>ª`·N¡Gkernel ©Ò¯à©w§}ªºªÅ¶¡¤j¤p¥²¶·¬O 4 megabytes ªº­¿¼Æ¡C
 	    </para>
 
           <para>[&a.dg; ¸É¥R¡G<emphasis>§Ú»{¬° kernel ©w§}ªÅ¶¡¤j¤pÀ³¸Ó­n¬O 2
 	    ªº­¼¾­¡A¦ý¤£¤j½T©w³o¤@ÂI¡Cªº±Ò°Êµ{¦¡·|°Ê¨ì
 	    high order address bits¡A°O±o¥¦°²³]¦Ü¤Ö¦³ 256 MB¡C]</emphasis>
 	    </para>
         </answer>
       </qandaentry>
     </qandaset>
   </chapter>
 
   <chapter id="acknowledgments">
     <chapterinfo>
       <author>
 	<firstname>Vanilla</firstname>
 	<surname>Shu</surname>
 	<affiliation>
 	  <address><email>vanilla@FreeBSD.org</email></address>
 	</affiliation>
       </author>
     </chapterinfo>
 
     <title>·PÁÂ</title>
 
     <blockquote>
        <attribution>FreeBSD Core Team</attribution>
 
        <para>°²¦p±z¦b³o¥÷ FAQ ¤¤§ä¨ì¿ù»~ªº¦a¤è¡A©Î¬O±z·Q¼W¥[¨Ç¬Æ»ò¡A
          ½Ð¼g«Ê«H¨ì &a.faq; ¡C§Ú­Ì«D±`·PÁ±zªº«Øij¡A
 	 ¦]¬°±zªº«ØijÅý³o¥÷¤å¥óÅܱo§ó¦n¡I</para>
     </blockquote>
 
       <variablelist>
         <varlistentry>
           <term>&a.jkh;</term>
             <listitem>
               <para>¤£°±ªº§ó·s¹L®Éªº FAQ</para>
             </listitem>
           </varlistentry>
 
           <varlistentry>
             <term>&a.dwhite;</term>
 
             <listitem>
               <para>¸g±`¦b freebsd-questions ¤W¦^µª°ÝÃD</para>
             </listitem>
           </varlistentry>
 
           <varlistentry>
             <term>&a.joerg;</term>
 
             <listitem>
               <para>¸g±`¦b Usenet ¤W¦^µª°ÝÃD</para>
             </listitem>
           </varlistentry>
 
           <varlistentry>
             <term>&a.wollman;</term>
 
             <listitem>
               <para>Networking and formatting</para>
             </listitem>
           </varlistentry>
 
           <varlistentry>
             <term>Jim Lowe</term>
 
             <listitem>
               <para>Multicast information</para>
             </listitem>
           </varlistentry>
 
           <varlistentry>
             <term>&a.pds;</term>
 
             <listitem>
               <para>FreeBSD FAQ ³o¥÷¤å¥óªº¥´¦r­W¤u</para>
             </listitem>
           </varlistentry>
 
           <varlistentry>
             <term>The FreeBSD Team</term>
 
             <listitem>
               <para>Kvetching, moaning, submitting data</para>
 
             </listitem>
           </varlistentry>
         </variablelist>
 
     <para>¹ï©ó¨º¨Ç´¿¸g¹ï³o¥÷ FAQ ´£¨ÑÀ°§U¡A¦Ó§Ú­Ì¨S´£¨ìªº¤H­Ì¡A
       §Ú­Ì¥Ñ°Jªº·PÁ±z¡I</para>
   </chapter>
 
   &bibliography;
 </book>
diff --git a/zh_TW.Big5/books/fdp-primer/Makefile b/zh_TW.Big5/books/fdp-primer/Makefile
new file mode 100644
index 0000000000..ecc7ebc217
--- /dev/null
+++ b/zh_TW.Big5/books/fdp-primer/Makefile
@@ -0,0 +1,51 @@
+# 
+# $FreeBSD$
+#
+# Build the FreeBSD Documentation Project Primer.
+#
+
+MAINTAINER=doc@FreeBSD.org
+
+DOC?= book
+
+FORMATS?= html-split html
+
+INSTALL_COMPRESSED?= gz
+INSTALL_ONLY_COMPRESSED?=
+
+# 
+# SRCS lists the individual SGML files that make up the document. Changes
+# to any of these files will force a rebuild
+#
+
+# SGML content
+SRCS=  book.sgml 
+SRCS+= overview/chapter.sgml 
+SRCS+= psgml-mode/chapter.sgml 
+SRCS+= see-also/chapter.sgml 
+SRCS+= sgml-markup/chapter.sgml 
+SRCS+= sgml-primer/chapter.sgml 
+SRCS+= stylesheets/chapter.sgml 
+SRCS+= structure/chapter.sgml
+SRCS+= doc-build/chapter.sgml
+SRCS+= the-website/chapter.sgml 
+SRCS+= tools/chapter.sgml 
+SRCS+= translations/chapter.sgml
+SRCS+= writing-style/chapter.sgml 
+
+SRCS+= examples/appendix.sgml
+
+# Images from the cross-document image library
+IMAGES_LIB=	callouts/1.png
+IMAGES_LIB+=	callouts/2.png
+IMAGES_LIB+=	callouts/3.png
+IMAGES_LIB+=	callouts/4.png
+IMAGES_LIB+=	callouts/5.png
+
+# Entities
+SRCS+= chapters.ent 
+
+URL_RELPREFIX?=	../../../..
+DOC_PREFIX?=	${.CURDIR}/../../..
+
+.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/zh_TW.Big5/books/fdp-primer/book.sgml b/zh_TW.Big5/books/fdp-primer/book.sgml
new file mode 100644
index 0000000000..02437e4b30
--- /dev/null
+++ b/zh_TW.Big5/books/fdp-primer/book.sgml
@@ -0,0 +1,251 @@
+<!-- Copyright (c) 1998, 1999 Nik Clayton, All rights reserved.
+
+     Redistribution and use in source (SGML DocBook) and 'compiled' forms
+     (SGML, HTML, PDF, PostScript, RTF and so forth) with or without
+     modification, are permitted provided that the following conditions
+     are met:
+
+      1. Redistributions of source code (SGML DocBook) must retain the above
+         copyright notice, this list of conditions and the following
+         disclaimer as the first lines of this file unmodified.
+
+      2. Redistributions in compiled form (transformed to other DTDs,
+         converted to PDF, PostScript, RTF and other formats) must reproduce
+         the above copyright notice, this list of conditions and the
+         following disclaimer in the documentation and/or other materials
+         provided with the distribution.
+
+     THIS DOCUMENTATION IS PROVIDED BY NIK CLAYTON "AS IS" AND ANY EXPRESS OR
+     IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+     OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+     DISCLAIMED. IN NO EVENT SHALL NIK CLAYTON BE LIABLE FOR ANY DIRECT,
+     INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+     (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+     SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+     HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+     STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
+     ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
+     POSSIBILITY OF SUCH DAMAGE.
+-->
+
+<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
+<!ENTITY % books.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Books Entity Set//EN">
+%books.ent;
+<!ENTITY % chapters SYSTEM "chapters.ent"> %chapters;
+<!ENTITY % not.published "INCLUDE">
+<!-- ENTITY index SYSTEM "index.sgml" -->
+]>
+
+<book>
+  <bookinfo>
+    <title>FreeBSD Documentation Project Primer for New Contributors</title>
+   
+    <corpauthor>FreeBSD ¤å¥ó­p¹º</corpauthor>
+ 
+    <copyright>
+      <year>1998</year>
+      <year>1999</year>
+      <year>2000</year>
+      <year>2001</year>
+      <year>2002</year>
+      <year>2003</year>
+      <year>2004</year>
+      <year>2005</year>
+      <year>2006</year>
+      <holder role="mailto:doceng@FreeBSD.org">DocEng</holder>
+    </copyright>
+
+    <pubdate role="rcs">$FreeBSD$</pubdate>
+
+    <releaseinfo>$FreeBSD$</releaseinfo>
+
+    &bookinfo.legalnotice;
+ 
+    <abstract>
+      <para>·PÁ±z°Ñ»P FreeBSD ¤å¥ó­p¹º¡A±zªºÂIºw°^Äm¡A³£¬Û·íÄ_¶Q¡C</para>
+
+      <para>This primer covers everything you will need to know in order
+        to start contributing to the FreeBSD Documentation Project, from
+        the tools and software you will be using (both mandatory and
+        recommended) to the philosophy behind the Documentation 
+        Project.</para>
+
+      <para>¥»¤å¥óÁÙ¦b¯ó½Z¡A©|¥¼§¹½Z¡C¥¼§¹¦¨ªº³¹¸`¡A§Ú­Ì·|¦b³¹¸`¦WºÙ®ÇÃä¥[µù¡y
+	<literal>*</literal> ¡z¥H§@ÃѧO¡C</para>
+    </abstract>
+  </bookinfo>
+
+  <preface id="preface">
+    <title>§Ç¨¥</title>
+
+    <sect1 id="preface-prompts">
+      <title>Shell ´£¥Ü²Å¸¹(Prompts)</title>
+      
+      <para>¤UªíÅã¥Ü¥X¤@¯ë±b¸¹»P root ªº´£¥Ü²Å¸¹¡A¦b©Ò¦³ªº¤å¥ó¨Ò¤l¤¤·|¥Î´£¥Ü²Å¸¹(prompt)
+	¡A¨Ó´£¿ô±z¸Ó¥Î­þºØ±b¸¹¤~¹ï¡C</para>
+
+      <informaltable frame="none" pgwide="1">
+	<tgroup cols="2">
+	  <thead>
+	    <row>
+	      <entry>±b¸¹</entry>
+	      <entry>´£¥Ü²Å¸¹(Prompt)</entry>
+	    </row>
+	  </thead>
+	  
+	  <tbody>
+	    <row>
+	      <entry>´¶³q±b¸¹</entry>
+	      <entry>&prompt.user;</entry>
+	    </row>
+
+	    <row>
+	      <entry><username>root</username></entry>
+	      <entry>&prompt.root;</entry>
+	    </row>
+	  </tbody>
+	</tgroup>
+      </informaltable>
+    </sect1>
+    
+    <sect1 id="preface-conventions">
+      <title>®Ñ¤¤©Ò¥Îªº½s±Æ­·®æ</title>
+
+      <para>¤Uªí¬°¥»®Ñ¤¤©Ò¨Ï¥Î½s±Æ­·®æ¤è¦¡¡G</para>
+
+      <informaltable frame="none" pgwide="1">
+	<tgroup cols="2">
+	  <thead>
+	    <row>
+	      <entry>¥Nªí·N¸q</entry>
+	      <entry>Á|¨Ò</entry>
+	    </row>
+	  </thead>
+	  
+	  <tbody>
+	    <row>
+	      <entry>The name of commands, files, and directories. On screen
+		computer output.</entry>
+	      <entry><para>Edit your <filename>.login</filename>
+		  file.</para><para>Use <command>ls -a</command> to list all
+		  files.</para><para><screen>You have mail.</screen>
+		</para></entry>
+	    </row>
+
+	    <row>
+	      <entry>¦b¿é¤J«ü¥O«á¡A¿Ã¹õ¤W·|¥X²{ªº¹ïÀ³¤º®e¡G</entry>
+
+	      <entry><screen>&prompt.user; <userinput>su</userinput>
+Password:</screen></entry>
+	    </row>
+
+	    <row>
+	      <entry>Á¿¨ì­n°Ñ¦Òªº Manual ®É...</entry>
+
+	      <entry>Use <citerefentry>
+		  <refentrytitle>su</refentrytitle>
+		  <manvolnum>1</manvolnum>
+		</citerefentry> to change user names.</entry>
+	    </row>
+
+	    <row>
+	      <entry>¦bÁ¿¨ì±b¸¹(user)¡B¸s²Õ(group)ªº¦WºÙªº®É­Ô...</entry>
+
+	      <entry>Only <username>root</username> can do this.</entry>
+	    </row>
+
+	    <row>
+	      <entry>»y®ðªº±j½Õ¡C</entry>
+
+	      <entry>You <emphasis>must</emphasis> do this.</entry>
+	    </row>
+
+	    <row>
+	      <entry>¥´«ü¥O®É¥i´À´«ªº³¡¥÷(¥i§ï¬°²Å¦X¦Û¤v¾÷¾¹¤WªºÀɦW¡B³]³Æ©Î¨ä¥LÃþ¦ü³¡¥÷)¡C</entry>
+
+	      <entry>To delete a file, type <command>rm <filename><replaceable>filename</replaceable></filename></command></entry>
+	    </row>
+
+	    <row>
+	      <entry>Àô¹ÒÅܼƳ]©w</entry>
+
+	      <entry><envar>$HOME</envar> is your home directory.</entry>
+	    </row>
+	  </tbody>
+	</tgroup>
+      </informaltable>
+    </sect1>
+
+    <sect1 id="preface-notes">
+      <title>¡yNote¡BTip¡BImportant¡BWarning¡BExample¡zªº¹B¥Î</title>
+
+      <para>¥H¤U¤å¦r¬O¡yª`·N(Note)¡z¡B¡y§Þ¥©(Tip)¡z¡B¡y­«­n°T®§(Important)¡z¡B¡yĵ§i(Warning)¡z¡B¡y½d¨Ò(Example)¡zªº¹B¥Î¡C</para>
+
+      <note>
+	<para>Notes are represented like this, and contain information that
+	  you should take note of, as it may affect what you do.</para>
+      </note>
+
+      <tip>
+	<para>Tips are represented like this, and contain information that you 
+	  might find useful, or lead to an easier way to do something.</para>
+      </tip>
+
+      <important>
+	<para>Important information is represented like this.  Typically they
+	  flag extra steps you may need to carry out.</para>
+      </important>
+
+      <warning>
+	<para>Warnings are represented like this, and contain information
+	  warning you about possible damage if you do not follow the
+	  instructions. This damage may be physical, to your hardware or to
+	  you, or it may be non-physical, such as the inadvertent deletion of
+	  important files.</para>
+      </warning>
+
+      <example>
+	<title>³o¬OÁ|¨Ò»¡©ú</title>
+
+	<para>Examples are represented like this, and typically contain
+	  examples you should walk through, or show you what the results of a
+	  particular action should be.</para>
+      </example>
+    </sect1>
+
+    <sect1 id="preface-acknowledgements">
+      <title>·PÁÂ</title>
+
+      <para>¦b¦¹­n·PÁ Sue Blake, Patrick Durusau, Jon Hamilton, Peter
+	Flynn,  Christopher Maden ³o¨Ç¤Hªº¨ó§U»P¾\Ūªì´Á¯ó½Z¡A¨Ã´£¨Ñ³\¦hÄ_¶Qªº¼í½Z·N¨£»Pµû½×¡C</para>
+    </sect1>
+  </preface>
+  
+  &chap.overview;
+  &chap.tools;
+  &chap.sgml-primer;
+  &chap.sgml-markup;
+  &chap.stylesheets;
+  &chap.structure;
+  &chap.doc-build;
+  &chap.the-website;
+  &chap.translations;
+  &chap.writing-style;
+  &chap.psgml-mode;
+  &chap.see-also;
+
+  &app.examples;
+
+<!--
+  &index;  
+-->
+</book>
+
+<!--
+     Local Variables:
+     mode: sgml
+     sgml-indent-data: t
+     sgml-omittag: nil
+     sgml-always-quote-attributes: t
+     End:
+-->
diff --git a/zh_TW.Big5/books/fdp-primer/chapter.decl b/zh_TW.Big5/books/fdp-primer/chapter.decl
new file mode 100644
index 0000000000..3e187a32ee
--- /dev/null
+++ b/zh_TW.Big5/books/fdp-primer/chapter.decl
@@ -0,0 +1,2 @@
+<!-- $FreeBSD$ -->
+<!DOCTYPE chapter PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN">
diff --git a/zh_TW.Big5/books/fdp-primer/chapters.ent b/zh_TW.Big5/books/fdp-primer/chapters.ent
new file mode 100644
index 0000000000..7329e4a05a
--- /dev/null
+++ b/zh_TW.Big5/books/fdp-primer/chapters.ent
@@ -0,0 +1,25 @@
+<!-- 
+     Creates entities for each chapter in the Documentation Project Primer.
+     Each entity is named chap.foo, where foo is the value of the id 
+     attribute on that chapter, and corresponds to the name of the 
+      directory in which that chapter's .sgml file is stored.
+   
+     Chapters should be listed in the order in which they are referenced.
+ 
+     $FreeBSD$
+-->
+
+<!ENTITY chap.overview		SYSTEM "overview/chapter.sgml">
+<!ENTITY chap.sgml-primer	SYSTEM "sgml-primer/chapter.sgml">
+<!ENTITY chap.tools		SYSTEM "tools/chapter.sgml">
+<!ENTITY chap.sgml-markup       SYSTEM "sgml-markup/chapter.sgml">
+<!ENTITY chap.stylesheets	SYSTEM "stylesheets/chapter.sgml">
+<!ENTITY chap.structure         SYSTEM "structure/chapter.sgml">
+<!ENTITY chap.the-website	SYSTEM "the-website/chapter.sgml">
+<!ENTITY chap.translations	SYSTEM "translations/chapter.sgml">
+<!ENTITY chap.writing-style	SYSTEM "writing-style/chapter.sgml">
+<!ENTITY chap.psgml-mode	SYSTEM "psgml-mode/chapter.sgml">
+<!ENTITY chap.see-also		SYSTEM "see-also/chapter.sgml">	
+<!ENTITY chap.doc-build		SYSTEM "doc-build/chapter.sgml">
+
+<!ENTITY app.examples		SYSTEM "examples/appendix.sgml">
diff --git a/zh_TW.Big5/books/fdp-primer/doc-build/chapter.sgml b/zh_TW.Big5/books/fdp-primer/doc-build/chapter.sgml
new file mode 100644
index 0000000000..38b62abc46
--- /dev/null
+++ b/zh_TW.Big5/books/fdp-primer/doc-build/chapter.sgml
@@ -0,0 +1,498 @@
+<!-- Copyright (c) 1999 Neil Blakey-Milner, All rights reserved.
+
+     Redistribution and use in source (SGML DocBook) and 'compiled' forms
+     (SGML HTML, PDF, PostScript, RTF and so forth) with or without
+     modification, are permitted provided that the following conditions
+     are met:
+
+      1. Redistributions of source code (SGML DocBook) must retain the above
+         copyright notice, this list of conditions and the following
+         disclaimer as the first lines of this file unmodified.
+
+      2. Redistributions in compiled form (transformed to other DTDs,
+         converted to PDF, PostScript, RTF and other formats) must reproduce
+         the above copyright notice, this list of conditions and the
+         following disclaimer in the documentation and/or other materials
+         provided with the distribution.
+
+     THIS DOCUMENTATION IS PROVIDED BY THE AUTHOR "AS IS" AND ANY EXPRESS OR
+     IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+     OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+     DISCLAIMED. IN NO EVENT SHALL NIK CLAYTON BE LIABLE FOR ANY DIRECT,
+     INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+     (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+     SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+     HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+     STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
+     ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
+     POSSIBILITY OF SUCH DAMAGE.
+
+     $FreeBSD$
+-->
+
+<chapter id="doc-build">
+  <title>The Documentation Build Process</title>
+
+  <para>This chapter's main purpose is to clearly explain <emphasis>how
+    the documentation build process is organized</emphasis>, and
+    <emphasis>how to affect modifications to this process</emphasis>.
+    </para>
+
+  <para>After you have finished reading this chapter you should:</para>
+
+  <itemizedlist>
+    <listitem>
+      <para>Know what you need to build the FDP documentation, in
+	addition to those mentioned in the <link
+	linkend="tools">SGML tools chapter</link>.</para>
+    </listitem>
+
+    <listitem>
+      <para>Be able to read and understand the
+	<application>make</application> instructions that are present in
+	each document's <filename>Makefile</filename>s, as well as an
+	overview of the <filename>doc.project.mk</filename> includes.</para>
+    </listitem>
+ 
+    <listitem>
+      <para>Be able to customize the build process by using
+	<application>make</application> variables and
+	<application>make</application> targets.</para>
+    </listitem>
+  </itemizedlist>
+
+  <sect1 id="doc-build-toolset">
+    <title>The FreeBSD Documentation Build Toolset</title>
+
+    <para>Here are your tools.  Use them every way you can.</para>
+
+    <itemizedlist>
+      <listitem>
+	<para>The primary build tool you will need is
+	  <application>make</application>, but specifically
+	  <application>Berkeley Make</application>.</para>
+      </listitem>
+
+      <listitem>
+	<para>Package building is handled by FreeBSD's
+	  <application>pkg_create</application>.  If you are not using
+	  FreeBSD, you will either have to live without packages, or
+	  compile the source yourself.</para>
+      </listitem>
+
+      <listitem>
+	<para><application>gzip</application> is needed to create
+	  compressed versions of the document.
+	  <application>bzip2</application> compression and
+	  <application>zip</application> archives are also supported.
+	  <application>tar</application> is supported, but package
+	  building demands it.</para>
+      </listitem>
+
+      <listitem>
+	<para><application>install</application> is the default method
+	  to install the documentation.  There are alternatives,
+	  however.</para>
+      </listitem>
+    </itemizedlist>
+
+    <note>
+      <para>It is unlikely you will have any trouble finding these last two, they
+	are mentioned for completeness only.</para>
+    </note>
+  </sect1>
+
+  <sect1 id="doc-build-makefiles">
+    <title>Understanding Makefiles in the Documentation tree</title>
+
+    <para>There are three main types of <filename>Makefile</filename>s 
+      in the FreeBSD Documentation Project tree.</para>
+
+    <itemizedlist>
+      <listitem>
+	<para><link linkend="sub-make">Subdirectory
+	  <filename>Makefile</filename>s</link> simply pass
+	  commands to those directories below them.</para>
+      </listitem>
+
+      <listitem>
+	<para><link linkend="doc-make">Documentation
+	  <filename>Makefile</filename>s</link> describe the
+	  document(s) that should be produced from this directory.</para>
+      </listitem>
+
+      <listitem>
+	<para><link linkend="make-includes"><application>Make</application>
+	  includes</link> are the glue that perform the document production,
+	  and are usually of the form
+	  <filename>doc.<replaceable>xxx</replaceable>.mk</filename>.</para>
+      </listitem>
+    </itemizedlist>
+
+    <sect2 id="sub-make">
+      <title>Subdirectory Makefiles</title>
+
+      <para>These <filename>Makefile</filename>s usually take the form of:</para>
+
+      <programlisting>SUBDIR =articles
+SUBDIR+=books
+
+COMPAT_SYMLINK = en
+
+DOC_PREFIX?= ${.CURDIR}/..
+.include "${DOC_PREFIX}/share/mk/doc.project.mk"</programlisting>
+
+      <para>In quick summary, the first four non-empty lines define the
+	<application>make</application> variables,
+	<makevar>SUBDIR</makevar>, <makevar>COMPAT_SYMLINK</makevar>,
+	and <makevar>DOC_PREFIX</makevar>.</para>
+
+      <para>The first <makevar>SUBDIR</makevar> statement, as well as
+	the <makevar>COMPAT_SYMLINK</makevar> statement, shows how to
+	assign a value to a variable, overriding any previous
+	value.</para>
+
+      <para>The second <makevar>SUBDIR</makevar> statement shows how a
+	value is appended to the current value of a variable.  The
+	<makevar>SUBDIR</makevar> variable is now <literal>articles
+	books</literal>.</para>
+
+      <para>The <makevar>DOC_PREFIX</makevar> assignment shows how a
+	value is assigned to the variable, but only if it is not already
+	defined.  This is useful if <makevar>DOC_PREFIX</makevar> is not
+	where this <filename>Makefile</filename> thinks it is - the user
+	can override this and provide the correct value.</para>
+
+      <para>Now what does it all mean?  <makevar>SUBDIR</makevar>
+	mentions which subdirectories below this one the build process
+	should pass any work on to.</para>
+
+      <para><makevar>COMPAT_SYMLINK</makevar> is specific to
+	compatibility symlinks (amazingly enough) for languages to their
+	official encoding (<filename>doc/en</filename> would point to
+	<filename>en_US.ISO-8859-1</filename>).</para>
+
+      <para><makevar>DOC_PREFIX</makevar> is the path to the root of the
+	FreeBSD Document Project tree.  This is not always that easy to
+	find, and is also easily overridden, to allow for flexibility.
+	<makevar>.CURDIR</makevar> is a <application>make</application>
+	builtin variable with the path to the current directory.</para>
+
+      <para>The final line includes the FreeBSD Documentation Project's
+	project-wide <application>make</application> system file
+	<filename>doc.project.mk</filename> which is the glue which
+	converts these variables into build instructions.</para>
+
+    </sect2>
+    <sect2 id="doc-make">
+      <title>Documentation Makefiles</title>
+
+      <para>These <filename>Makefile</filename>s set a bunch of
+	<application>make</application> variables that describe how to
+	build the documentation contained in that directory.</para>
+
+      <para>Here is an example:</para>
+
+      <programlisting>MAINTAINER=nik@FreeBSD.org
+
+DOC?= book
+
+FORMATS?= html-split html
+
+INSTALL_COMPRESSED?= gz
+INSTALL_ONLY_COMPRESSED?=
+
+# SGML content
+SRCS=  book.sgml
+
+DOC_PREFIX?= ${.CURDIR}/../../..
+
+.include "$(DOC_PREFIX)/share/mk/docproj.docbook.mk"</programlisting>
+
+      <para>The <makevar>MAINTAINER</makevar> variable is a very 
+	important one.  This variable provides the ability to claim
+	ownership over a document in the FreeBSD Documentation
+	Project, whereby you gain the responsibility for maintaining 
+	it.</para>
+
+      <para><makevar>DOC</makevar> is the name (sans the
+	<filename>.sgml</filename> extension) of the main document
+	created by this directory.  <makevar>SRCS</makevar> lists all
+	the individual files that make up the document.  This should
+	also include important files in which a change should result
+	in a rebuild.</para>
+
+      <para><makevar>FORMATS</makevar> indicates the default formats
+	that should be built for this document.
+	<makevar>INSTALL_COMPRESSED</makevar> is the default list of
+	compression techniques that should be used in the document
+	build.  <makevar>INSTALL_ONLY_COMPRESS</makevar>, empty by
+	default, should be non-empty if only compressed documents are
+	desired in the build.</para>
+
+      <note>
+	<para>We covered optional variable assignments in the 
+	  <link linkend="sub-make">previous section</link>.</para>
+      </note>
+
+      <para>The <makevar>DOC_PREFIX</makevar> and include statements
+	should be familiar already.</para>
+    </sect2>
+  </sect1>
+
+  <sect1 id="make-includes">
+    <title>FreeBSD Documentation Project make includes</title>
+
+    <para>This is best explained by inspection of the code.  Here are
+      the system include files:</para>
+
+    <itemizedlist>
+      <listitem>
+	<para><filename>doc.project.mk</filename> is the main project
+	  include file, which includes all the following include files, as
+	  necessary.</para>
+      </listitem>
+
+      <listitem>
+	<para><filename>doc.subdir.mk</filename> handles traversing of
+	  the document tree during the build and install processes.</para>
+      </listitem>
+
+      <listitem>
+	<para><filename>doc.install.mk</filename> provides variables
+	  that affect ownership and installation of documents.</para>
+      </listitem>
+
+      <listitem>
+	<para><filename>doc.docbook.mk</filename> is included if
+	  <makevar>DOCFORMAT</makevar> is <literal>docbook</literal>
+	  and <makevar>DOC</makevar> is set.</para>
+      </listitem>
+    </itemizedlist>
+
+    <sect2>
+      <title>doc.project.mk</title>
+
+      <para>By inspection:</para>
+
+      <programlisting>DOCFORMAT?=	docbook
+MAINTAINER?=	doc@FreeBSD.org
+
+PREFIX?=	/usr/local
+PRI_LANG?=	en_US.ISO8859-1
+
+.if defined(DOC)
+.if ${DOCFORMAT} == "docbook"
+.include "doc.docbook.mk"
+.endif
+.endif
+
+.include "doc.subdir.mk"
+.include "doc.install.mk"</programlisting>
+
+      <sect3>
+
+	<title>Variables</title>
+
+	<para><makevar>DOCFORMAT</makevar> and <makevar>MAINTAINER</makevar>
+	  are assigned default values, if these are not set by the
+	  document make file.</para>
+
+	<para><makevar>PREFIX</makevar> is the prefix under which the
+	  <link linkend="tools">documentation building tools</link> are
+	  installed.  For normal package and port installation, this is
+	  <filename>/usr/local</filename>.</para>
+
+	<para><makevar>PRI_LANG</makevar> should be set to whatever
+	  language and encoding is natural amongst users these documents are
+	  being built for.  US English is the default.</para>
+
+	<note>
+	  <para><makevar>PRI_LANG</makevar> in no way affects what documents
+	    can, or even will, be built.  Its main use is creating links to
+	    commonly referenced documents into the FreeBSD documentation
+	    install root.</para>
+	</note>
+      </sect3>
+
+      <sect3>
+	<title>Conditionals</title>
+       
+	<para>The <literal>.if defined(DOC)</literal> line is an example of
+	  a <application>make</application> conditional which, like in
+	  other programs, defines behavior if some condition is true or
+	  if it is false.  <literal>defined</literal> is a function which
+	  returns whether the variable given is defined or not.</para>
+
+	<para><literal>.if ${DOCFORMAT} == "docbook"</literal>, next,
+	  tests whether the <makevar>DOCFORMAT</makevar> variable is
+	  <literal>"docbook"</literal>, and in this case, includes
+	  <filename>doc.docbook.mk</filename>.</para>
+
+	<para>The two <literal>.endif</literal>s close the two above
+	  conditionals, marking the end of their application.</para>
+      </sect3>
+    </sect2>
+
+    <sect2>
+      <title>doc.subdir.mk</title>
+
+      <para>This is too long to explain by inspection, you should be
+	able to work it out with the knowledge gained from the previous
+	chapters, and a little help given here.</para>
+
+      <sect3>
+	<title>Variables</title>
+
+	<itemizedlist>
+	  <listitem>
+	    <para><makevar>SUBDIR</makevar> is a list of subdirectories 
+	      that the build process should go further down
+	      into.</para>
+	  </listitem>
+
+	  <listitem>
+	    <para><makevar>ROOT_SYMLINKS</makevar> is the name of
+	      directories that should be linked to the document
+	      install root from their actual locations, if the current
+	      language is the primary language (specified by
+	      <makevar>PRI_LANG</makevar>).</para>
+	  </listitem>
+
+	  <listitem>
+	    <para><makevar>COMPAT_SYMLINK</makevar> is described in the
+	      <link linkend="sub-make">Subdirectory Makefile</link>
+	      section.</para>
+	  </listitem>
+	</itemizedlist>
+      </sect3>
+
+      <sect3>
+	<title>Targets and macros</title>
+
+	<para>Dependencies are described by 
+	  <literal><replaceable>target</replaceable>:
+	  <replaceable>dependency1 dependency2 ...</replaceable></literal>
+	  tuples, where to build <literal>target</literal>, you need to build
+	  the given dependencies first.</para>
+
+	<para>After that descriptive tuple, instructions on how to build
+	  the target may be given, if the conversion process between the
+	  target and its dependencies are not previously defined, or if
+	  this particular conversion is not the same as the default
+	  conversion method.</para>
+
+	<para>A special dependency <literal>.USE</literal> defines
+	  the equivalent of a macro.</para>
+
+<programlisting>_SUBDIRUSE: .USE
+.for entry in ${SUBDIR}
+	@${ECHO} "===&gt; ${DIRPRFX}${entry}"
+	@(cd ${.CURDIR}/${entry} &amp;&amp; \
+	${MAKE} ${.TARGET:S/realpackage/package/:S/realinstall/install/} DIRPRFX=${DIRPRFX}${entry}/ )
+.endfor</programlisting>
+
+	<para>In the above, <maketarget>_SUBDIRUSE</maketarget> is now a
+	  macro which will execute the given commands when it is listed
+	  as a dependency.</para>
+
+	<para>What sets this macro apart from other targets?  Basically,
+	  it is executed <emphasis>after</emphasis> the instructions
+	  given in the build procedure it is listed as a dependency to,
+	  and it does not adjust <makevar>.TARGET</makevar>, which is the
+	  variable which contains the name of the target currently
+	  being built.</para>
+
+<programlisting>clean: _SUBDIRUSE
+	rm -f ${CLEANFILES}</programlisting>
+
+	<para>In the above, <maketarget>clean</maketarget> will use the
+	  <maketarget>_SUBDIRUSE</maketarget> macro after it has
+	  executed the instruction 
+	  <command>rm -f ${CLEANFILES}</command>.  In effect, this causes
+	  <maketarget>clean</maketarget> to go further and further down
+	  the directory tree, deleting built files as it goes
+	  <emphasis>down</emphasis>, not on the way back up.</para>
+
+	<sect4>
+	  <title>Provided targets</title>
+
+	  <itemizedlist>
+	    <listitem>
+	      <para><maketarget>install</maketarget> and
+		<maketarget>package</maketarget> both go down the
+		directory tree calling the real versions of themselves
+		in the subdirectories
+		(<maketarget>realinstall</maketarget> and
+		<maketarget>realpackage</maketarget>
+		 respectively).</para>
+	    </listitem>
+
+	    <listitem>
+	      <para><maketarget>clean</maketarget> removes files created
+		by the build process (and goes down the directory tree
+		too).  <maketarget>cleandir</maketarget> does the same,
+		and also removes the object directory, if any.</para>
+	    </listitem>
+	  </itemizedlist>
+	</sect4>
+      </sect3>
+
+      <sect3>
+	<title>More on conditionals</title>
+
+	<itemizedlist>
+	  <listitem>
+	    <para><literal>exists</literal> is another condition
+	      function which returns true if the given file exists.</para>
+	  </listitem>
+
+	  <listitem>
+	    <para><literal>empty</literal> returns true if the given
+	      variable is empty.</para>
+	  </listitem>
+
+	  <listitem>
+	    <para><literal>target</literal> returns true if the given
+	      target does not already exist.</para>
+	  </listitem>
+	</itemizedlist>
+      </sect3>
+
+      <sect3>
+	<title>Looping constructs in make (.for)</title>
+
+	<para><literal>.for</literal> provides a way to repeat a set of
+	  instructions for each space-separated element in a variable.
+	  It does this by assigning a variable to contain the current
+	  element in the list being examined.</para>
+
+<programlisting>_SUBDIRUSE: .USE
+.for entry in ${SUBDIR}
+	@${ECHO} "===&gt; ${DIRPRFX}${entry}"
+	@(cd ${.CURDIR}/${entry} &amp;&amp; \
+	${MAKE} ${.TARGET:S/realpackage/package/:S/realinstall/install/} DIRPRFX=${DIRPRFX}${entry}/ )
+.endfor</programlisting>
+
+	<para>In the above, if <makevar>SUBDIR</makevar> is empty, no
+	  action is taken; if it has one or more elements, the
+	  instructions between <literal>.for</literal> and
+	  <literal>.endfor</literal> would repeat for every element,
+	  with <makevar>entry</makevar> being replaced with the value of
+	  the current element.</para>
+      </sect3>
+    </sect2>
+  </sect1>
+</chapter>
+
+<!--
+     Local Variables:
+     mode: sgml
+     sgml-declaration: "../chapter.decl"
+     sgml-indent-data: t
+     sgml-omittag: nil
+     sgml-always-quote-attributes: t
+     sgml-parent-document: ("../book.sgml" "part" "chapter")
+     End:
+-->
+
diff --git a/zh_TW.Big5/books/fdp-primer/examples/appendix.sgml b/zh_TW.Big5/books/fdp-primer/examples/appendix.sgml
new file mode 100644
index 0000000000..4e4196b78a
--- /dev/null
+++ b/zh_TW.Big5/books/fdp-primer/examples/appendix.sgml
@@ -0,0 +1,355 @@
+<!-- Copyright (c) 2000 Nik Clayton, All rights reserved.
+
+     Redistribution and use in source (SGML DocBook) and 'compiled' forms
+     (SGML HTML, PDF, PostScript, RTF and so forth) with or without
+     modification, are permitted provided that the following conditions
+     are met:
+
+      1. Redistributions of source code (SGML DocBook) must retain the above
+         copyright notice, this list of conditions and the following
+         disclaimer as the first lines of this file unmodified.
+
+      2. Redistributions in compiled form (transformed to other DTDs,
+         converted to PDF, PostScript, RTF and other formats) must reproduce
+         the above copyright notice, this list of conditions and the
+         following disclaimer in the documentation and/or other materials
+         provided with the distribution.
+
+     THIS DOCUMENTATION IS PROVIDED BY NIK CLAYTON "AS IS" AND ANY EXPRESS OR
+     IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+     OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+     DISCLAIMED. IN NO EVENT SHALL NIK CLAYTON BE LIABLE FOR ANY DIRECT,
+     INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+     (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+     SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+     HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+     STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
+     ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
+     POSSIBILITY OF SUCH DAMAGE.
+
+     $FreeBSD$
+-->
+
+<appendix id="examples">
+  <title>Examples</title>
+
+  <para>This appendix contains example SGML files and command lines you can
+    use to convert them from one output format to another.  If you have
+    successfully installed the Documentation Project tools then you should
+    be able to use these examples directly.</para>
+
+  <para>These examples are not exhaustive&mdash;they do not contain all the
+    elements you might want to use, particularly in your document's front
+    matter.  For more examples of DocBook markup you should examine the SGML
+    source for this and other documents, available in the
+    <application>CVSup</application> <literal>doc</literal> collection, or
+    available online starting at
+    <ulink url="http://www.FreeBSD.org/cgi/cvsweb.cgi/doc/"></ulink>.</para>
+
+  <para>To avoid confusion, these examples use the standard DocBook 4.1 DTD
+    rather than the FreeBSD extension.  They also use the stock stylesheets
+    distributed by Norm Walsh, rather than any customizations made to those
+    stylesheets by the FreeBSD Documentation Project.  This makes them more
+    useful as generic DocBook examples.</para>
+
+  <sect1 id="examples-docbook-book">
+    <title>DocBook <sgmltag>book</sgmltag></title>
+
+    <example>
+      <title>DocBook <sgmltag>book</sgmltag></title>
+
+      <programlisting><![ CDATA [<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
+
+<book>
+  <bookinfo>
+    <title>An Example Book</title>
+    
+    <author>
+      <firstname>Your first name</firstname>
+      <surname>Your surname</surname>
+      <affiliation>
+        <address><email>foo@example.com</email></address>
+      </affiliation>
+    </author>
+
+    <copyright>
+      <year>2000</year>
+      <holder>Copyright string here</holder>
+    </copyright>
+
+    <abstract>
+      <para>If your book has an abstract then it should go here.</para>
+    </abstract>
+  </bookinfo>
+
+  <preface>
+    <title>Preface</title>
+
+    <para>Your book may have a preface, in which case it should be placed
+      here.</para>
+  </preface>
+      
+  <chapter>
+    <title>My first chapter</title>
+
+    <para>This is the first chapter in my book.</para>
+
+    <sect1>
+      <title>My first section</title>
+
+      <para>This is the first section in my book.</para>
+    </sect1>
+  </chapter>
+</book>]]></programlisting>
+    </example>
+  </sect1>
+
+  <sect1 id="examples-docbook-article">
+    <title>DocBook <sgmltag>article</sgmltag></title>
+
+    <example>
+      <title>DocBook <sgmltag>article</sgmltag></title>
+
+      <programlisting><![ CDATA [<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
+
+<article>
+  <articleinfo>
+    <title>An example article</title>
+
+    <author>
+      <firstname>Your first name</firstname>
+      <surname>Your surname</surname>
+      <affiliation>
+        <address><email>foo@example.com</email></address>
+      </affiliation>
+    </author>
+
+    <copyright>
+      <year>2000</year>
+      <holder>Copyright string here</holder>
+    </copyright>
+
+    <abstract>
+      <para>If your article has an abstract then it should go here.</para>
+    </abstract>
+  </articleinfo>
+
+  <sect1>
+    <title>My first section</title>
+
+    <para>This is the first section in my article.</para>
+
+    <sect2>
+      <title>My first sub-section</title>
+
+      <para>This is the first sub-section in my article.</para>
+    </sect2>	
+  </sect1>
+</article>]]></programlisting>
+    </example>
+  </sect1>
+
+  <sect1 id="examples-formatted">
+    <title>Producing formatted output</title>
+
+    <para>This section assumes that you have installed the software listed in
+      the <filename role="package">textproc/docproj</filename> port, either by hand, or by
+      using the port.  Further, it is assumed that your software is installed
+      in subdirectories under <filename>/usr/local/</filename>, and the
+      directory where binaries have been installed is in your
+      <envar>PATH</envar>.  Adjust the paths as necessary for your
+      system.</para>
+
+    <sect2>
+      <title>Using Jade</title>
+
+      <example>
+	<title>Converting DocBook to HTML (one large file)</title>
+	
+	<screen>&prompt.user; <userinput>jade -V nochunks \  <co id="examples-co-jade-1-nochunks">
+    -c /usr/local/share/sgml/docbook/dsssl/modular/catalog \ <co id="examples-co-jade-1-catalog">
+    -c /usr/local/share/sgml/docbook/catalog \
+    -c /usr/local/share/sgml/jade/catalog \
+    -d /usr/local/share/sgml/docbook/dsssl/modular/html/docbook.dsl \<co id="examples-co-jade-1-dsssl">
+    -t sgml <co id="examples-co-jade-1-transform"> file.sgml &gt; file.html <co id="examples-co-jade-1-filename"></userinput></screen>
+
+	<calloutlist>
+	  <callout arearefs="examples-co-jade-1-nochunks">
+	    <para>Specifies the <literal>nochunks</literal> parameter to the
+	      stylesheets, forcing all output to be written to
+	      <abbrev>STDOUT</abbrev> (using Norm Walsh's stylesheets).</para>
+	  </callout>
+
+	  <callout arearefs="examples-co-jade-1-catalog">
+	    <para>Specifies the catalogs that Jade will need to process.
+	      Three catalogs are required.  The first is a catalog that
+	      contains information about the DSSSL stylesheets.  The second
+	      contains information about the DocBook DTD.  The third contains
+	      information specific to Jade.</para>
+	  </callout>
+
+	  <callout arearefs="examples-co-jade-1-dsssl">
+	    <para>Specifies the full path to the DSSSL stylesheet that Jade
+	      will use when processing the document.</para>
+	  </callout>
+
+	  <callout arearefs="examples-co-jade-1-transform">
+	    <para>Instructs Jade to perform a
+	      <emphasis>transformation</emphasis> from one DTD to another.  In 
+	      this case, the input is being transformed from the DocBook DTD
+	      to the HTML DTD.</para>
+	  </callout>
+
+	  <callout arearefs="examples-co-jade-1-filename">
+	    <para>Specifies the file that Jade should process, and redirects
+	      output to the specified <filename>.html</filename> file.</para>
+	  </callout>
+	</calloutlist>
+      </example>
+
+      <example>
+	<title>Converting DocBook to HTML (several small files)</title>
+	
+	<screen>&prompt.user; <userinput>jade \
+    -c /usr/local/share/sgml/docbook/dsssl/modular/catalog \ <co id="examples-co-jade-2-catalog">
+    -c /usr/local/share/sgml/docbook/catalog \
+    -c /usr/local/share/sgml/jade/catalog \
+    -d /usr/local/share/sgml/docbook/dsssl/modular/html/docbook.dsl \<co id="examples-co-jade-2-dsssl">
+    -t sgml <co id="examples-co-jade-2-transform"> <replaceable>file</replaceable>.sgml <co id="examples-co-jade-2-filename"></userinput></screen>
+
+	<calloutlist>
+	  <callout arearefs="examples-co-jade-2-catalog">
+	    <para>Specifies the catalogs that Jade will need to process.
+	      Three catalogs are required.  The first is a catalog that
+	      contains information about the DSSSL stylesheets.  The second
+	      contains information about the DocBook DTD.  The third contains
+	      information specific to Jade.</para>
+	  </callout>
+
+	  <callout arearefs="examples-co-jade-2-dsssl">
+	    <para>Specifies the full path to the DSSSL stylesheet that Jade
+	      will use when processing the document.</para>
+	  </callout>
+
+	  <callout arearefs="examples-co-jade-2-transform">
+	    <para>Instructs Jade to perform a
+	      <emphasis>transformation</emphasis> from one DTD to another.  In 
+	      this case, the input is being transformed from the DocBook DTD
+	      to the HTML DTD.</para>
+	  </callout>
+
+	  <callout arearefs="examples-co-jade-2-filename">
+	    <para>Specifies the file that Jade should process.  The
+	      stylesheets determine how the individual HTML files will be
+	      named, and the name of the <quote>root</quote> file (i.e., the 
+	      one that contains the start of the document.</para>
+	  </callout>
+	</calloutlist>
+
+	<para>This example may still only generate one HTML file, depending on 
+	  the structure of the document you are processing, and the
+	  stylesheet's rules for splitting output.</para>
+      </example>
+
+      <example id="examples-docbook-postscript">
+	<title>Converting DocBook to Postscript</title>
+
+	<para>The source SGML file must be converted to a &tex; file.</para>
+
+	<screen>&prompt.user; <userinput>jade -Vtex-backend \ <co id="examples-co-jade-3-tex-backend">
+    -c /usr/local/share/sgml/docbook/dsssl/modular/catalog \ <co id="examples-co-jade-3-catalog">
+    -c /usr/local/share/sgml/docbook/catalog \
+    -c /usr/local/share/sgml/jade/catalog \
+    -d /usr/local/share/sgml/docbook/dsssl/modular/print/docbook.dsl \<co id="examples-co-jade-3-dsssl">
+    -t tex <co id="examples-co-jade-3-tex"> <replaceable>file</replaceable>.sgml</userinput></screen>
+
+	<calloutlist>
+	  <callout arearefs="examples-co-jade-3-tex-backend">
+	    <para>Customizes the stylesheets to use various options
+	      specific to producing output for &tex;.</para>
+	  </callout>
+	  
+	  <callout arearefs="examples-co-jade-3-catalog">
+	    <para>Specifies the catalogs that Jade will need to process. Three
+	      catalogs are required.  The first is a catalog that contains
+	      information about the DSSSL stylesheets.  The second contains
+	      information about the DocBook DTD.  The third contains
+	      information specific to Jade.</para>
+	  </callout>
+
+	  <callout arearefs="examples-co-jade-3-dsssl">
+	    <para>Specifies the full path to the DSSSL stylesheet that
+	      Jade will use when processing the document.</para>
+	  </callout>
+
+	  <callout arearefs="examples-co-jade-3-tex">
+	    <para>Instructs Jade to convert the output to &tex;.</para>
+	  </callout>
+	</calloutlist>
+
+	<para>The generated <filename>.tex</filename> file must now be run 
+	  through <command>tex</command>, specifying the
+	  <literal>&amp;jadetex</literal> macro package.</para>
+	    
+	<screen>&prompt.user; <userinput>tex "&amp;jadetex" <replaceable>file</replaceable>.tex</userinput></screen>
+
+	<para>You have to run <command>tex</command> <emphasis>at
+	  least</emphasis> three times.  The first run processes the
+	  document, and determines areas of the document which are referenced
+	  from other parts of the document, for use in indexing, and so
+	  on.</para>
+
+	<para>Do not be alarmed if you see warning messages such as
+	  <literal>LaTeX Warning: Reference `136' on page 5 undefined on input
+	  line 728.</literal> at this point.</para>
+	
+	<para>The second run reprocesses the document now that certain pieces
+	  of information are known (such as the document's page length).  This
+	  allows index entries and other cross-references to be fixed
+	  up.</para>
+
+	<para>The third pass performs any final cleanup necessary.</para>
+	
+	<para>The output from this stage will be
+	  <filename><replaceable>file</replaceable>.dvi</filename>.</para>
+	
+	<para>Finally, run <command>dvips</command> to convert the
+	  <filename>.dvi</filename> file to Postscript.</para>
+
+	<screen>&prompt.user; <userinput>dvips -o <replaceable>file</replaceable>.ps <replaceable>file.dvi</replaceable></userinput></screen>
+      </example>
+
+      <example>
+	<title>Converting DocBook to PDF</title>
+
+	<para>The first part of this process is identical to that when
+	  converting DocBook to Postscript, using the same
+	  <command>jade</command> command line (<xref
+	    linkend="examples-docbook-postscript">).</para>
+
+	<para>When the <filename>.tex</filename> file has been generated you
+	  run pdfTeX.  However, use the &amp;pdfjadetex macro package
+	  instead.</para>
+
+	<screen>&prompt.user; <userinput>pdftex "&amp;pdfjadetex" <replaceable>file</replaceable>.tex</userinput></screen>
+
+	<para>Again, run this command three times.</para>
+
+	<para>This will generate
+	  <filename><replaceable>file</replaceable>.pdf</filename>, which does 
+	  not need to be processed any further.</para>
+      </example>
+    </sect2>
+  </sect1>
+</appendix>
+
+<!--
+     Local Variables:
+     mode: sgml
+     sgml-declaration: "../appendix.decl"
+     sgml-indent-data: t
+     sgml-omittag: nil
+     sgml-always-quote-attributes: t
+     sgml-parent-document: ("../book.sgml" "part" "appendix")
+     End:
+-->
diff --git a/zh_TW.Big5/books/fdp-primer/overview/chapter.sgml b/zh_TW.Big5/books/fdp-primer/overview/chapter.sgml
new file mode 100644
index 0000000000..bac205dd03
--- /dev/null
+++ b/zh_TW.Big5/books/fdp-primer/overview/chapter.sgml
@@ -0,0 +1,270 @@
+<!-- Copyright (c) 1998, 1999 Nik Clayton, All rights reserved.
+
+     Redistribution and use in source (SGML DocBook) and 'compiled' forms
+     (SGML HTML, PDF, PostScript, RTF and so forth) with or without
+     modification, are permitted provided that the following conditions
+     are met:
+
+      1. Redistributions of source code (SGML DocBook) must retain the above
+         copyright notice, this list of conditions and the following
+         disclaimer as the first lines of this file unmodified.
+
+      2. Redistributions in compiled form (transformed to other DTDs,
+         converted to PDF, PostScript, RTF and other formats) must reproduce
+         the above copyright notice, this list of conditions and the
+         following disclaimer in the documentation and/or other materials
+         provided with the distribution.
+
+     THIS DOCUMENTATION IS PROVIDED BY NIK CLAYTON "AS IS" AND ANY EXPRESS OR
+     IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+     OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+     DISCLAIMED. IN NO EVENT SHALL NIK CLAYTON BE LIABLE FOR ANY DIRECT,
+     INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+     (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+     SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+     HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+     STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
+     ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
+     POSSIBILITY OF SUCH DAMAGE.
+
+     $FreeBSD$
+-->
+
+<chapter id="overview">
+  <title>·§½×</title>
+  
+  <para>Åwªï°Ñ»P FreeBSD ¤å¥ó­p¹º¡Cºû«ùÀu¨q½è¶qªº¤å¥ó¹ï FreeBSD ªº¦¨¥\¨Ó»¡¤Q¤À­«­n¡A
+	¦Ó FreeBSD ¤å¥ó­p¹º(¥H¤U¬Ò¥H FDP ¨Ó¥Nªí FreeBSD Documentation Project 
+	ªºÁY¼g) «h»P³o¨Ç¤å¥ó¼¶¼g¡B§ó·s®§®§¬ÛÃö¡A¦]¦¹±zªºÂIºw°^Äm³£¬O¤Q¤ÀÄ_¶Qªº¡C</para>
+  
+  <para>¥»¤å¥ó³Ì¥D­nªº¥Øªº¡A´N¬O²M·¡§i¶D±z¡G¡yFDP ªº¬[ºc¦³­þ¨Ç¡z¡B¡y¦p¦ó¼¶¼g¨Ã´£¥æ¤å¥óµ¹ FDP¡z¡B
+	¡y¦p¦ó¦³®Ä¹B¥Î¤u¨ã¨Ó¨ó§U¼¶½Z¡z¡C</para>
+  
+  <para><indexterm>
+      <primary>Membership</primary>
+    </indexterm>
+    §Ú­ÌÅwªï¨C­Ó¼ö¤ßªº§Ó¤h¨Ó¥[¤J FDP ¦æ¦C¡CFDP ¨Ã¤£­­©w¨C¤ë¥²¶·¥æ¥X¦h¤Ö½Z¶q¡A¤~¯à¥[¤J¡C
+    ±z°ß¤@¶·­n§@ªº´N¬O­q¾\ &a.doc; ¡C</para>
+
+  <para>Ū§¹¥»¥÷¤å¥ó¡A±z±N·|¡G</para>
+  
+  <itemizedlist>
+    <listitem> 
+      <para>ÁA¸Ñ¦³­þ¨Ç¤å¥ó¬O¥Ñ FDP ©ÒºûÅ@ªº¡C</para>
+    </listitem>
+    
+    <listitem>
+      <para>¥i¥H¬ÝÀ´ FDP ©ÒºûÅ@ªº SGML ­ì©l¤å¥ó¡C</para>
+    </listitem>
+    
+    <listitem> 
+      <para>ª¾¹D¦p¦ó¨Ó¹ï¤å¥ó§@­×§ï¡C</para>
+    </listitem>
+    
+    <listitem>
+      <para>ª¾¹D¦p¦ó§ë½Z¦Û¤vªº­×§ï³¡¥÷¡A¨Ã³Ì«á¥¿¦¡¶i¤J FreeBSD ¤å¥ó¤º¡C</para>
+    </listitem> 
+  </itemizedlist>
+
+  <sect1 id="overview-doc">
+    <title>The FreeBSD Documentation Set</title>
+
+    <para>FDP Á`¦@­t³d FreeBSD ªº 4 ºØÃþ§Oªº¤å¥ó¡G</para>
+    
+    <variablelist>
+      <varlistentry>
+        <term>Manual pages</term>
+
+        <listitem>
+          <para>­^¤åª©ªº¨t²Î manual ¨Ã¤£¬O¥Ñ FDP ©Ò¼¶¼gªº¡A¦]¬°¥¦­Ì¬OÄÝ©ó base system ªº³¡¥÷¡C
+		µM¦Ó¡AFDP ¥i¥H(¤]´¿³o»ò°µ¹L)­×§ï³o¨Ç¤å¥ó¡A¨ÓÅý³o¨Ç¤å¥ó¼g±o§ó²M·¡¡A¬Æ¦Ü¬O°É¥¿¿ù»~ªº¦a¤è¡C</para>
+
+          <para>The translation teams are responsible for translating the
+	    system manual pages into different languages.  These translations
+	    are kept within the FDP.</para>
+        </listitem>
+      </varlistentry>
+
+      <varlistentry>
+        <term>FAQ</term>
+	
+        <listitem>
+          <para>FAQ ¥D­n¬O¦¬¶°¦b¦U½×¾Â©Î newsgroup ·|±`°Ý¨ì©Î¦³¥i¯à·|°Ý¨ìªº FreeBSD ¬ÛÃö°ÝÃD»Pµª®× ¡C
+		(²³æÁ¿¡A´N¬O¡y°Ýµª¶°¡z®æ¦¡) ³q±`·|Â\¦b³o¸Ì­±ªº°Ýµª®æ¦¡¡A¤£·|©ñ¤Óªøªº¸Ô²Ó¤º®e¡C</para>
+        </listitem>
+      </varlistentry>
+
+      <varlistentry>
+        <term>Handbook</term>
+
+        <listitem>
+          <para>The Handbook aims to be the comprehensive on-line resource and
+	    reference for FreeBSD users.</para>
+        </listitem>
+      </varlistentry>
+ 
+      <varlistentry>
+         <term>Web site</term>
+	
+         <listitem>
+           <para>FreeBSD ¥D­n¦U¶µ¤¶²Ð¤è­±ªº WWW ³¡¥÷¡AÅwªï³}³} <ulink
+	      url="&url.base;/index.html">http://www.FreeBSD.org/</ulink>
+	    ¥H¤Î³\¦h¨ä¥L mirror ¯¸¡C³oºô¯¸¬O³\¦h¤H²Ä¤@¦¸±µÄ² FreeBSD ªº¦a¤è¡C</para>
+	</listitem>
+      </varlistentry>
+    </variablelist>
+    
+    <para>These four groups of documentation are all available in the
+      FreeBSD CVS tree.  This means that the logs of changes to these
+      files are visible to anyone, and anyone can use a program such as
+      <application>CVSup</application> or
+      <application>CTM</application> to keep local copies of
+      this documentation.</para>
+    
+    <para>In addition, many people have written tutorials or other web
+      sites relating to FreeBSD.  Some of these are stored in the CVS
+      repository as well (where the author has agreed to this).  In
+      other cases the author has decided to keep his documentation
+      separate from the main FreeBSD repository.  The FDP endeavors to
+      provide links to as much of this documentation as
+      possible.</para>
+  </sect1>                                                                     
+  
+  <sect1 id="overview-before">
+    <title>¦b¶}¤u¤§«e...</title>                                            
+    
+    <para>¥»¤å°²³]±z¤w¸gÁA¸Ñ¡G</para>                  
+    
+    <itemizedlist>                                                             
+      <listitem>                                                               
+	<para>¦p¦ó±q FreeBSD CVS repository §ó·s¦Û¤v¹q¸£¤Wªº FreeBSD ¤å¥ó ³¡¥÷(¥H <application>CVS</application>
+	  ©Î <application>CVSup</application> ©Î¬O
+	  <application>CTM</application>) ©Î¬O¥Î
+	  <application>CVSup</application> ¨Ó¤U¸ü <emphasis>checked-out</emphasis> ªº°Æ¥»</para>
+      </listitem>
+      
+      <listitem>                                                               
+	<para>¦p¦ó¥Î FreeBSD Ports ®M¥óºÞ²z¾÷¨î©Î &man.pkg.add.1; ¨Ó¤U¸ü¡B¦w¸Ë³nÅé¡C</para>
+      </listitem>                                                              
+    </itemizedlist>                                                            
+  </sect1>
+
+  <sect1 id="overview-quick-start">
+    <title>§Ö³t¤W¤â½g</title>
+
+    <para>­Y·Q¥ý¦Û¦æ¸Õ¸Õ¬Ý¡A¨Ã¦³«H¤ß¥i¥H§@±o¨ì¡A¨º»ò´N·Ó¤U­±¨BÆJ§a¡C</para>
+
+    <procedure>
+      <step>
+	<para>¦w¸Ë <filename role="package">textproc/docproj</filename> ³o­Ó²Õ¦X«¬ port(meta-port).</para>
+
+	<screen>&prompt.root; <userinput>cd /usr/ports/textproc/docproj</userinput>
+&prompt.root; <userinput>make JADETEX=no install</userinput></screen>
+      </step>
+
+      <step>
+	<para>Get a local copy of the FreeBSD <filename>doc</filename> tree.
+	  Either use CVSup in <literal>checkout</literal> mode to do this, or
+	  get a full copy of the CVS repository locally.</para>
+
+	<para>If you have the CVS repository locally then as a minimum you
+	  will need to checkout the <filename>doc/share</filename>, and
+	  <filename>doc/en_US.ISO8859-1/share</filename>
+	  directories.</para>
+
+	<screen>&prompt.user; <userinput>cvs checkout doc/share</userinput>
+&prompt.user; <userinput>cvs checkout doc/en_US.ISO8859-1/share</userinput></screen>
+
+	<para>­YµwºÐªÅ¶¡°÷¤jªº¸Ü¡A¨º¥i¥H§â©Ò¦³ doc ³£ check out ¥X¨Ó¡G</para>
+
+	<screen>&prompt.user; <userinput>cvs checkout doc</userinput></screen>
+      </step>
+
+      <step>
+	<para>If you are preparing a change to an existing book or article,
+	  check it out of the repository as necessary.  If you are planning on
+	  contributing a new book or article then use an existing one as a
+	  guide.</para>
+
+	<para>Á|¨Ò¨Ó»¡¡A­Y·Q¼g½g·s¤å³¹¡A¤º®e¬O¦³Ãö¦b FreeBSD »P Windows 2000 ¤§¶¡«Ø¥ß VPN ³s½u¡A
+	¨º»ò¥i¥H·ÓÃþ¦ü¤U­±³o¼Ëªº§@ªk¡G</para>
+
+	<procedure>
+	  <step>
+	    <para>Check out the <filename>articles</filename>
+	      directory.</para>
+
+	    <screen>&prompt.user; <userinput>cvs checkout doc/en_US.ISO8859-1/articles</userinput></screen>
+	  </step>
+
+	  <step>
+	    <para>½Æ»s²{¦³ªº¤å³¹§@¬°½d¥»¡C¦b³o­Ó¨Ò¤l¤¤¡A±z¥´ºâ¨M©w§â·s¤å³¹©ñ¦b 
+		<filename>vpn-w2k</filename> ªº¥Ø¿ý¤U¡C</para>
+
+	    <screen>&prompt.user; <userinput>cd doc/en_US.ISO8859-1/articles</userinput>
+&prompt.user; <userinput>cp -R committers-guide vpn-w2k</userinput></screen>
+	  </step>
+	</procedure>
+
+	<para>­Y¬O­n­×§ï²{¦³¤å³¹¡A¹³¬O FAQ(Â\¦b <filename>doc/en_US.ISO8859-1/books/faq</filename>)
+	¡A¨º»ò­n±q repository ¤¤¨ú¥X¨Ó(check out)¡G</para>
+
+	<screen>&prompt.user; <userinput>cvs checkout doc/en_US.ISO8859-1/books/faq</userinput></screen>
+      </step>
+
+      <step>
+	<para>¥H½s¿è¾¹¨Ó½s¼g <filename>.sgml</filename> ÀÉ¡C</para>
+      </step>
+
+      <step>
+	<para>¥H <maketarget>lint</maketarget> ·í»²§U°Ñ¼Æ¡A¨Ó§Ö³tÀË´ú¤å¥óµ²ºc¤Î³sµ²¦³µL¿ù»~¡A 
+	¥H¤U³o­Ó«ü¥O¡A¹ê»Ú¤W¤£·|¶i¦æ¯Ó®Éªº½s®Ñ¹Lµ{¡A¥u¬O¥ý´ú¸Õ¤å¥ó¦³µL¿ù»~¡C</para>
+
+	<screen>&prompt.user; <userinput>make lint</userinput></screen>
+
+	<para>When you are ready to actually build the document, you
+  	  may specify a single format or a list of formats in the
+  	  <varname>FORMATS</varname> variable.  ¥Ø«e¤ä´©ªº®æ¦¡¦@¦³¡G
+  	  <literal>html</literal>, <literal>html-split</literal>,
+  	  <literal>txt</literal>, <literal>ps</literal>,
+  	  <literal>pdf</literal>, <literal>rtf</literal> ¡C
+	 The most up to date list of supported formats is
+  	  listed at the top of the
+  	  <filename>doc/share/mk/doc.docbook.mk</filename> file.  Make
+  	  sure to use quotes around the list of formats when you build
+  	  more than one format with a single command.</para>
+
+        <para>Á|¨Ò¨Ó»¡¡A­Y¥u­n
+          <literal>html</literal> ®æ¦¡´N¦n¡A¨º»ò´N¥´¡G</para>
+
+	<screen>&prompt.user; <userinput>make FORMATS=html</userinput></screen>
+
+        <para>¦ý­Y§Æ±æ¦³ <literal>html</literal> ¤Î <literal>txt</literal> ®æ¦¡ªº¸Ü¡A
+          §A¥i¯à­n¥´¨â¦¸ &man.make.1; «ü¥O¤~¯à§¹¦¨¡G</para>
+
+	<screen>&prompt.user; <userinput>make FORMATS=html</userinput>
+&prompt.user; <userinput>make FORMATS=txt</userinput></screen>
+
+        <para>¨ä¹ê¡A¤]¥i¥H¥Î³æ¤@«ü¥O¨Ó§¹¦¨¡G</para>
+
+	<screen>&prompt.user; <userinput>make FORMATS="html txt"</userinput></screen>
+      </step>
+
+      <step>
+	<para>³Ì«á¡A¥H &man.send-pr.1; ¨Ó´£¥æ­×§ïªº³¡¥÷¡C</para>
+      </step>
+    </procedure>
+  </sect1>
+</chapter>
+
+<!--
+     Local Variables:
+     mode: sgml
+     sgml-declaration: "../chapter.decl"
+     sgml-indent-data: t
+     sgml-omittag: nil
+     sgml-always-quote-attributes: t
+     sgml-parent-document: ("../book.sgml" "part" "chapter")
+     End:
+-->
+
diff --git a/zh_TW.Big5/books/fdp-primer/psgml-mode/chapter.sgml b/zh_TW.Big5/books/fdp-primer/psgml-mode/chapter.sgml
new file mode 100644
index 0000000000..afbb1c9175
--- /dev/null
+++ b/zh_TW.Big5/books/fdp-primer/psgml-mode/chapter.sgml
@@ -0,0 +1,177 @@
+<!-- Copyright (c) 1998, 1999 Nik Clayton, All rights reserved.
+
+     Redistribution and use in source (SGML DocBook) and 'compiled' forms
+     (SGML HTML, PDF, PostScript, RTF and so forth) with or without
+     modification, are permitted provided that the following conditions
+     are met:
+
+      1. Redistributions of source code (SGML DocBook) must retain the above
+         copyright notice, this list of conditions and the following
+         disclaimer as the first lines of this file unmodified.
+
+      2. Redistributions in compiled form (transformed to other DTDs,
+         converted to PDF, PostScript, RTF and other formats) must reproduce
+         the above copyright notice, this list of conditions and the
+         following disclaimer in the documentation and/or other materials
+         provided with the distribution.
+
+     THIS DOCUMENTATION IS PROVIDED BY NIK CLAYTON "AS IS" AND ANY EXPRESS OR
+     IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+     OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+     DISCLAIMED. IN NO EVENT SHALL NIK CLAYTON BE LIABLE FOR ANY DIRECT,
+     INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+     (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+     SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+     HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+     STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
+     ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
+     POSSIBILITY OF SUCH DAMAGE.
+
+     $FreeBSD$
+-->
+
+<chapter id="psgml-mode">
+  <title>Using <literal>sgml-mode</literal> with
+    <application>Emacs</application></title>
+  
+  <para>Recent versions of <application>Emacs</application> or <application>XEmacs</application> (available from the ports
+    collection) contain a very useful package called PSGML. Automatically
+    invoked when a file with the <filename>.sgml</filename> extension is loaded,
+    or by typing <command>M-x sgml-mode</command>, it is a major mode for
+    dealing with SGML files, elements and attributes.</para>
+
+  <para>An understanding of some of the commands provided by this mode can
+    make working with SGML documents such as the Handbook much easier.</para>
+
+  <variablelist>
+    <varlistentry>
+      <term><command>C-c C-e</command></term>
+      
+      <listitem>
+	<para>Runs <literal>sgml-insert-element</literal>. You will be
+	  prompted for the name of the element to insert at the current point.
+	  You can use the TAB key to complete the element. Elements that are
+	  not valid at the current point will be disallowed.</para>
+
+	<para>The start and end tags for the element will be inserted. If the
+	  element contains other, mandatory, elements then these will be
+	  inserted as well.</para>
+      </listitem>
+    </varlistentry>
+    
+    <varlistentry>
+      <term><command>C-c =</command></term>
+      
+      <listitem>
+	<para>Runs <literal>sgml-change-element-name</literal>. Place the
+	  point within an element and run this command. You will be prompted
+	  for the name of the element to change to. Both the start and end
+	  tags of the current element will be changed to the new
+	  element.</para>
+      </listitem>
+    </varlistentry>
+    
+    <varlistentry>
+      <term><command>C-c C-r</command></term>
+      
+      <listitem>
+	<para>Runs <literal>sgml-tag-region</literal>. Select some text (move
+	  to start of text, C-space, move to end of text, C-space) and then
+	  run this command. You will be prompted for the element to use. This
+	  element will then be inserted immediately before and after your
+	  marked region.</para>
+      </listitem>
+    </varlistentry>
+
+    <varlistentry>
+      <term><command>C-c -</command></term>
+      
+      <listitem>
+	<para>Runs <literal>sgml-untag-element</literal>. Place the point
+	  within the start or end tag of an element you want to remove, and
+	  run this command. The element's start and end tags will be
+	  removed.</para>
+      </listitem>
+    </varlistentry>
+    
+    <varlistentry>
+      <term><command>C-c C-q</command></term>
+      
+      <listitem>
+	<para>Runs <literal>sgml-fill-element</literal>. Will recursively fill
+	  (i.e., reformat) content from the current element in. The filling
+	  <emphasis>will</emphasis> affect content in which whitespace is
+	  significant, such as within <sgmltag>programlisting</sgmltag>
+	  elements, so run this command with care.</para>
+      </listitem>
+    </varlistentry>
+    
+    <varlistentry>
+      <term><command>C-c C-a</command></term>
+      
+      <listitem>
+	<para>Runs <literal>sgml-edit-attributes</literal>. Opens a second
+	  buffer containing a list of all the attributes for the closest
+	  enclosing element, and their current values. Use TAB to navigate
+	  between attributes, <command>C-k</command> to remove an existing
+	  value and replace it with a new one, <command>C-c C-c</command>
+	  to close this buffer and return to the main document.</para>
+      </listitem>
+    </varlistentry>
+    
+    <varlistentry>
+      <term><command>C-c C-v</command></term>
+      
+      <listitem>
+	<para>Runs <literal>sgml-validate</literal>. Prompts you to save the
+	  current document (if necessary) and then runs an SGML validator. The
+	  output from the validator is captured into a new buffer, and you can
+	  then navigate from one troublespot to the next, fixing markup errors
+	  as you go.</para>
+      </listitem>
+    </varlistentry>
+
+    <varlistentry>
+      <term><command>C-c /</command></term>
+
+      <listitem>
+        <para>Runs <literal>sgml-insert-end-tag</literal>. Inserts the
+	  end tag for the current open element.</para>
+      </listitem>
+    </varlistentry>
+  </variablelist>
+  
+  <para>Doubtless there are other useful functions of this mode, but those are
+    the ones I use most often.</para>
+
+  <para>You can also use the following entries in
+    <filename>.emacs</filename> to set proper spacing, indentation,
+    and column width for working with the Documentation Project.</para>
+
+  <programlisting>
+    (defun local-sgml-mode-hook
+      (setq fill-column 70
+            indent-tabs-mode nil
+            next-line-add-newlines nil
+            standard-indent 4
+            sgml-indent-data t)
+      (auto-fill-mode t)
+      (setq sgml-catalog-files '("/usr/local/share/sgml/catalog")))
+    (add-hook 'psgml-mode-hook
+      '(lambda () (local-psgml-mode-hook)))
+  </programlisting>
+
+</chapter>
+
+
+<!--
+     Local Variables:
+     mode: sgml
+     sgml-declaration: "../chapter.decl"
+     sgml-indent-data: t
+     sgml-omittag: nil
+     sgml-always-quote-attributes: t
+     sgml-parent-document: ("../book.sgml" "part" "chapter")
+     End:
+-->
+
diff --git a/zh_TW.Big5/books/fdp-primer/see-also/chapter.sgml b/zh_TW.Big5/books/fdp-primer/see-also/chapter.sgml
new file mode 100644
index 0000000000..0ce1e28bd8
--- /dev/null
+++ b/zh_TW.Big5/books/fdp-primer/see-also/chapter.sgml
@@ -0,0 +1,134 @@
+<!-- Copyright (c) 1998, 1999 Nik Clayton, All rights reserved.
+
+     Redistribution and use in source (SGML DocBook) and 'compiled' forms
+     (SGML HTML, PDF, PostScript, RTF and so forth) with or without
+     modification, are permitted provided that the following conditions
+     are met:
+
+      1. Redistributions of source code (SGML DocBook) must retain the above
+         copyright notice, this list of conditions and the following
+         disclaimer as the first lines of this file unmodified.
+
+      2. Redistributions in compiled form (transformed to other DTDs,
+         converted to PDF, PostScript, RTF and other formats) must reproduce
+         the above copyright notice, this list of conditions and the
+         following disclaimer in the documentation and/or other materials
+         provided with the distribution.
+
+     THIS DOCUMENTATION IS PROVIDED BY NIK CLAYTON "AS IS" AND ANY EXPRESS OR
+     IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+     OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+     DISCLAIMED. IN NO EVENT SHALL NIK CLAYTON BE LIABLE FOR ANY DIRECT,
+     INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+     (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+     SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+     HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+     STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
+     ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
+     POSSIBILITY OF SUCH DAMAGE.
+
+     $FreeBSD$
+-->
+
+<chapter id="see-also">
+  <title>See Also</title>
+
+  <para>This document is deliberately not an exhaustive discussion of SGML,
+    the DTDs listed, and the FreeBSD Documentation Project. For more
+    information about these, you are encouraged to see the following web
+    sites.</para>
+
+  <sect1 id="see-also-fdp">
+    <title>The FreeBSD Documentation Project</title>
+
+    <itemizedlist>
+      <listitem>
+	<para><ulink url="&url.base;/docproj/index.html">The FreeBSD
+	    Documentation Project web pages</ulink></para>
+      </listitem>
+
+      <listitem>
+	<para><ulink url="&url.books.handbook;/index.html">The FreeBSD Handbook</ulink></para>
+      </listitem>
+    </itemizedlist>
+  </sect1>
+
+  <sect1 id="see-also-sgml">
+    <title>SGML</title>
+
+    <itemizedlist>
+      <listitem>
+	<para><ulink url="http://www.oasis-open.org/cover/">The SGML/XML web
+	    page</ulink>, a comprehensive SGML resource</para>
+      </listitem>
+      
+      <listitem>
+	<para><ulink
+	    url="http://etext.virginia.edu/bin/tei-tocs?div=DIV1&amp;id=SG">Gentle introduction to SGML</ulink></para>
+      </listitem>
+    </itemizedlist>
+  </sect1>
+
+  <sect1 id="see-also-html">
+    <title>HTML</title>
+
+    <itemizedlist>
+      <listitem>
+	<para><ulink url="http://www.w3.org/">The World Wide Web
+	    Consortium</ulink></para>
+      </listitem>
+
+      <listitem>
+	<para><ulink url="http://www.w3.org/TR/REC-html40/">The HTML 4.0
+	    specification</ulink></para>
+      </listitem>
+    </itemizedlist>
+  </sect1>
+
+  <sect1 id="see-also-docbook">
+    <title>DocBook</title>
+
+    <itemizedlist>
+      <listitem>
+	<para><ulink url="http://www.oasis-open.org/docbook/">The DocBook
+	    Technical Committee</ulink>, maintainers of the DocBook DTD</para>
+      </listitem>
+
+      <listitem>
+	<para><ulink url="http://www.docbook.org/">DocBook: The Definitive
+	    Guide</ulink>, the online documentation for the DocBook
+	  DTD.</para>
+	
+      </listitem>
+
+      <listitem>
+	<para><ulink url="http://docbook.sourceforge.net/">The DocBook Open
+	    Repository</ulink> contains DSSSL stylesheets and other resources
+	  for people using DocBook.</para>
+      </listitem>
+    </itemizedlist>
+  </sect1>
+
+  <sect1 id="see-also-linuxdoc">
+    <title>The Linux Documentation Project</title>
+
+    <itemizedlist>
+      <listitem>
+	<para><ulink url="http://www.linuxdoc.org/">The Linux Documentation
+	  Project web pages</ulink></para>
+      </listitem>
+    </itemizedlist>
+  </sect1>
+</chapter>
+
+<!--
+     Local Variables:
+     mode: sgml
+     sgml-declaration: "../chapter.decl"
+     sgml-indent-data: t
+     sgml-omittag: nil
+     sgml-always-quote-attributes: t
+     sgml-parent-document: ("../book.sgml" "part" "chapter")
+     End:
+-->
+
diff --git a/zh_TW.Big5/books/fdp-primer/sgml-markup/chapter.sgml b/zh_TW.Big5/books/fdp-primer/sgml-markup/chapter.sgml
new file mode 100644
index 0000000000..8a73062eb7
--- /dev/null
+++ b/zh_TW.Big5/books/fdp-primer/sgml-markup/chapter.sgml
@@ -0,0 +1,2708 @@
+<!-- Copyright (c) 1998, 1999 Nik Clayton, All rights reserved.
+
+     Redistribution and use in source (SGML DocBook) and 'compiled' forms
+     (SGML HTML, PDF, PostScript, RTF and so forth) with or without
+     modification, are permitted provided that the following conditions
+     are met:
+
+      1. Redistributions of source code (SGML DocBook) must retain the above
+         copyright notice, this list of conditions and the following
+         disclaimer as the first lines of this file unmodified.
+
+      2. Redistributions in compiled form (transformed to other DTDs,
+         converted to PDF, PostScript, RTF and other formats) must reproduce
+         the above copyright notice, this list of conditions and the
+         following disclaimer in the documentation and/or other materials
+         provided with the distribution.
+
+     THIS DOCUMENTATION IS PROVIDED BY NIK CLAYTON "AS IS" AND ANY EXPRESS OR
+     IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+     OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+     DISCLAIMED. IN NO EVENT SHALL NIK CLAYTON BE LIABLE FOR ANY DIRECT,
+     INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+     (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+     SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+     HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+     STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
+     ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
+     POSSIBILITY OF SUCH DAMAGE.
+
+     $FreeBSD$
+-->
+
+<chapter id="sgml-markup">
+  <title>SGML Markup</title>
+
+  <para>This chapter describes the two markup languages you will encounter
+    when you contribute to the FreeBSD documentation project.  Each section
+    describes the markup language, and details the markup that you are likely
+    to want to use, or that is already in use.</para>
+
+  <para>These markup languages contain a large number of elements, and it can
+    be confusing sometimes to know which element to use for a particular
+    situation.  This section goes through the elements you are most likely to
+    need, and gives examples of how you would use them.</para>
+  
+  <para>This is <emphasis>not</emphasis> an exhaustive list of elements, since
+    that would just reiterate the documentation for each language.  The aim of
+    this section is to list those elements more likely to be useful to you.
+    If you have a question about how best to markup a particular piece of
+    content, please post it to the &a.doc;.</para>
+
+  <note>
+    <title>Inline vs. block</title>
+    
+    <para>In the remainder of this document, when describing elements,
+      <emphasis>inline</emphasis> means that the element can occur within a
+      block element, and does not cause a line break.  A
+      <emphasis>block</emphasis> element, by comparison, will cause a line
+      break (and other processing) when it is encountered.</para>
+  </note>
+  
+  <sect1 id="sgml-markup-html">
+    <title>HTML</title>
+    
+    <para>HTML, the HyperText Markup Language, is the markup language of
+      choice on the World Wide Web.  More information can be found at
+      &lt;URL:<ulink url="http://www.w3.org/"></ulink>&gt;.</para>
+
+    <para>HTML is used to markup pages on the FreeBSD web site.  It should not
+      (generally) be used to mark up other documentation, 
+      since DocBook offers a
+      far richer set of elements to choose from.  Consequently, you will
+      normally only encounter HTML pages if you are writing for the web
+      site.</para>
+
+    <para>HTML has gone through a number of versions, 1, 2, 3.0, 3.2, and the
+      latest, 4.0 (available in both <emphasis>strict</emphasis> and
+      <emphasis>loose</emphasis> variants).</para>
+	  
+    <para>The HTML DTDs are available from the ports collection in the
+      <filename role="package">textproc/html</filename> port.  They are automatically
+      installed as part of the <filename role="package">textproc/docproj</filename>
+      port.</para>
+
+    <sect2>
+      <title>Formal Public Identifier (FPI)</title>
+
+      <para>There are a number of HTML FPIs, depending upon the version (also
+	known as the level) of HTML that you want to declare your document to
+	be compliant with.</para>
+
+      <para>The majority of HTML documents on the FreeBSD web site comply with
+	the loose version of HTML 4.0.</para>
+
+      <programlisting>PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"</programlisting>
+    </sect2>
+
+    <sect2>
+      <title>Sectional elements</title>
+
+      <para>An HTML document is normally split into two sections.  The first
+	section, called the <emphasis>head</emphasis>, contains
+	meta-information about the document, such as its title, the name of
+	the author, the parent document, and so on.  The second section, the
+	<emphasis>body</emphasis>, contains the content that will be displayed
+	to the user.</para>
+
+      <para>These sections are indicated with <sgmltag>head</sgmltag> and
+	<sgmltag>body</sgmltag> elements respectively.  These elements are
+	contained within the top-level <sgmltag>html</sgmltag> element.</para>
+
+      <example>
+	<title>Normal HTML document structure</title>
+
+	<programlisting>&lt;html>
+  &lt;head>
+	  &lt;title><replaceable>The document's title</replaceable>&lt;/title>
+  &lt;/head>
+
+  &lt;body>
+
+    &hellip;
+
+  &lt;/body>
+&lt;/html></programlisting>
+      </example>
+    </sect2>
+    
+    <sect2>
+      <title>Block elements</title>
+
+      <sect3>
+	<title>Headings</title>
+
+	<para>HTML allows you to denote headings in your document, at up to
+	  six different levels.</para>
+
+	<para>The largest and most prominent heading is <sgmltag>h1</sgmltag>,
+	  then <sgmltag>h2</sgmltag>, continuing down to
+	  <sgmltag>h6</sgmltag>.</para>
+
+	<para>The element's content is the text of the heading.</para>
+
+	<example>
+	  <title><sgmltag>h1</sgmltag>, <sgmltag>h2</sgmltag>, etc.</title>
+
+	  <para>Use:</para>
+
+	  <programlisting><![ CDATA [<h1>First section</h1>
+
+<!-- Document introduction goes here -->
+
+<h2>This is the heading for the first section</h2>
+
+<!-- Content for the first section goes here -->
+
+<h3>This is the heading for the first sub-section</h3>
+
+<!-- Content for the first sub-section goes here -->
+
+<h2>This is the heading for the second section</h2>
+
+<!-- Content for the second section goes here -->]]></programlisting>	    
+	</example>
+	
+	<para>Generally, an HTML page should have one first level heading
+	  (<sgmltag>h1</sgmltag>).  This can contain many second level
+	  headings (<sgmltag>h2</sgmltag>), which can in turn contain many
+	  third level headings.  Each
+	  <sgmltag>h<replaceable>n</replaceable></sgmltag> element should have
+	  the same element, but one further up the hierarchy, preceding it.
+	  Leaving gaps in the numbering is to be avoided.</para>
+
+	<example>
+	  <title>Bad ordering of
+	    <sgmltag>h<replaceable>n</replaceable></sgmltag> elements</title>
+
+	  <para>Use:</para>
+
+	  <programlisting><![ CDATA [<h1>First section</h1>
+
+<!-- Document introduction -->
+
+<h3>Sub-section</h3>
+
+<!-- This is bad, <h2> has been left out -->]]></programlisting>
+	</example>
+      </sect3>
+      
+      <sect3>
+	<title>Paragraphs</title>
+
+	<para>HTML supports a single paragraph element,
+	  <sgmltag>p</sgmltag>.</para>
+
+	<example>
+	  <title><sgmltag>p</sgmltag></title>
+
+	  <para>Use:</para>
+
+	  <programlisting><![ CDATA [<p>This is a paragraph.  It can contain just about any
+  other element.</p>]]></programlisting>
+	</example>
+      </sect3>
+
+      <sect3>
+	<title>Block quotations</title>
+
+	<para>A block quotation is an extended quotation from another document
+	  that should not appear within the current paragraph.</para>
+
+	<example>
+	  <title><sgmltag>blockquote</sgmltag></title>
+
+	  <para>Use:</para>
+
+	  <programlisting><![ CDATA [<p>A small excerpt from the US Constitution:</p>
+
+<blockquote>We the People of the United States, in Order to form
+  a more perfect Union, establish Justice, insure domestic
+  Tranquility, provide for the common defence, promote the general
+  Welfare, and secure the Blessings of Liberty to ourselves and our
+  Posterity, do ordain and establish this Constitution for the
+  United States of America.</blockquote>]]></programlisting>
+	</example>
+      </sect3>
+
+      <sect3>
+	<title>Lists</title>
+
+	<para>You can present the user with three types of lists, ordered,
+	  unordered, and definition.</para>
+
+	<para>Typically, each entry in an ordered list will be numbered, while
+	  each entry in an unordered list will be preceded by a bullet point.
+	  Definition lists are composed of two sections for each entry.  The
+	  first section is the term being defined, and the second section is
+	  the definition of the term.</para>
+
+	<para>Ordered lists are indicated by the <sgmltag>ol</sgmltag>
+	  element, unordered lists by the <sgmltag>ul</sgmltag> element, and
+	  definition lists by the <sgmltag>dl</sgmltag> element.</para>
+
+	<para>Ordered and unordered lists contain listitems, indicated by the
+	  <sgmltag>li</sgmltag> element.  A listitem can contain textual
+	  content, or it may be further wrapped in one or more
+	  <sgmltag>p</sgmltag> elements.</para>
+
+	<para>Definition lists contain definition terms
+	  (<sgmltag>dt</sgmltag>) and definition descriptions
+	  (<sgmltag>dd</sgmltag>).  A definition term can only contain inline
+	  elements.  A definition description can contain other block
+	  elements.</para>
+
+	<example>
+	  <title><sgmltag>ul</sgmltag> and <sgmltag>ol</sgmltag></title>
+
+	  <para>Use:</para>
+
+	  <programlisting><![ CDATA [<p>An unordered list.  Listitems will probably be
+  preceded by bullets.</p>
+
+<ul>
+  <li>First item</li>
+
+  <li>Second item</li>
+
+  <li>Third item</li>
+</ul>
+
+<p>An ordered list, with list items consisting of multiple
+  paragraphs.  Each item (note: not each paragraph) will be
+  numbered.</p>
+
+<ol>
+  <li><p>This is the first item.  It only has one paragraph.</p></li>
+
+  <li><p>This is the first paragraph of the second item.</p>
+
+    <p>This is the second paragraph of the second item.</p></li>
+
+  <li><p>This is the first and only paragraph of the third
+    item.</p></li>
+</ol>]]></programlisting>
+	</example>
+
+	<example>
+	  <title>Definition lists with <sgmltag>dl</sgmltag></title>
+
+	  <para>Use:</para>
+
+	  <programlisting><![ CDATA [<dl>
+  <dt>Term 1</dt>
+
+  <dd><p>Paragraph 1 of definition 1.</p>
+
+    <p>Paragraph 2 of definition 1.</p></dd>
+
+  <dt>Term 2</dt>
+
+  <dd><p>Paragraph 1 of definition 2.</p></dd>
+
+  <dt>Term 3</dt>
+
+  <dd><p>Paragraph 1 of definition 3.</p></dd>
+</dl>]]></programlisting>
+	</example>
+      </sect3>
+
+      <sect3>
+	<title>Pre-formatted text</title>
+
+	<para>You can indicate that text should be shown to the user exactly
+	  as it is in the file.  Typically, this means that the text is shown
+	  in a fixed font, multiple spaces are not merged into one, and line
+	  breaks in the text are significant.</para>
+
+	<para>In order to do this, wrap the content in the
+	  <sgmltag>pre</sgmltag> element.</para>
+
+	<example>
+	  <title><sgmltag>pre</sgmltag></title>
+
+	  <para>You could use <sgmltag>pre</sgmltag> to mark up an email
+	    message:</para>
+
+	  <programlisting><![ CDATA [<pre>  From: nik@FreeBSD.org
+  To: freebsd-doc@FreeBSD.org
+  Subject: New documentation available
+
+  There is a new copy of my primer for contributors to the FreeBSD
+  Documentation Project available at
+
+    &lt;URL:http://people.FreeBSD.org/~nik/primer/index.html&gt;
+
+  Comments appreciated.
+
+  N</pre>]]></programlisting>
+
+	  <para>Keep in mind that <literal>&lt;</literal> and
+	    <literal>&amp;</literal> still are recognized as special
+	    characters in pre-formatted text.  This is why the example
+	    shown had to use <literal>&amp;lt;</literal> instead of
+	    <literal>&lt;</literal>.  For consistency,
+	    <literal>&amp;gt;</literal> was used in place of
+	    <literal>&gt;</literal>, too.  Watch out for the special characters
+	    that may appear in text copied from a plain-text source,
+	    e.g., an email message or program code.</para>
+
+	</example>
+      </sect3>
+
+      <sect3>
+	<title>Tables</title>
+
+	<note>
+	  <para>Most text-mode browsers (such as Lynx) do not render tables
+	    particularly effectively.  If you are relying on the tabular
+	    display of your content, you should consider using alternative
+	    markup to prevent confusion.</para>
+	</note>
+
+	<para>Mark up tabular information using the <sgmltag>table</sgmltag>
+	  element.  A table consists of one or more table rows
+	  (<sgmltag>tr</sgmltag>), each containing one or more cells of table
+	  data (<sgmltag>td</sgmltag>).  Each cell can contain other block
+	  elements, such as paragraphs or lists.  It can also contain another
+	  table (this nesting can repeat indefinitely).  If the cell only
+	  contains one paragraph then you do not need to include the
+	  <sgmltag>p</sgmltag> element.</para>
+
+	<example>
+	  <title>Simple use of <sgmltag>table</sgmltag></title>
+
+	  <para>Use:</para>
+
+	  <programlisting><![ CDATA [<p>This is a simple 2x2 table.</p>
+
+<table>
+  <tr>
+    <td>Top left cell</td>
+
+    <td>Top right cell</td>
+  </tr>
+
+  <tr>
+    <td>Bottom left cell</td>
+
+    <td>Bottom right cell</td>
+  </tr>
+</table>]]></programlisting></example>
+
+	<para>A cell can span multiple rows and columns.  To indicate this,
+	  add the <literal>rowspan</literal> and/or <literal>colspan</literal>
+	  attributes, with values indicating the number of rows of columns
+	  that should be spanned.</para>
+
+	<example>
+	  <title>Using <literal>rowspan</literal></title>
+
+	  <para>Use:</para>
+
+	  <programlisting><![ CDATA [<p>One tall thin cell on the left, two short cells next to
+  it on the right.</p>
+
+<table>
+  <tr>
+    <td rowspan="2">Long and thin</td>
+  </tr>
+
+  <tr>
+    <td>Top cell</td>
+
+    <td>Bottom cell</td>
+  </tr>
+</table>]]></programlisting>
+	</example>
+
+	<example>
+	  <title>Using <literal>colspan</literal></title>
+
+	  <para>Use:</para>
+
+	  <programlisting><![ CDATA [<p>One long cell on top, two short cells below it.</p>
+
+<table>
+  <tr>
+    <td colspan="2">Top cell</td>
+  </tr>
+
+  <tr>
+    <td>Bottom left cell</td>
+
+    <td>Bottom right cell</td>
+  </tr>
+</table>]]></programlisting>
+	</example>
+
+	<example>
+	  <title>Using <literal>rowspan</literal> and
+	    <literal>colspan</literal> together</title>
+
+	  <para>Use:</para>
+
+	  <programlisting><![ CDATA [<p>On a 3x3 grid, the top left block is a 2x2 set of
+  cells merged into one.  The other cells are normal.</p>
+
+<table>
+  <tr>
+    <td colspan="2" rowspan="2">Top left large cell</td>
+
+    <td>Top right cell</td>
+  </tr>
+
+  <tr>
+    <!-- Because the large cell on the left merges into
+         this row, the first <td> will occur on its
+         right -->
+	    
+    <td>Middle right cell</td>
+  </tr>
+
+  <tr>
+    <td>Bottom left cell</td>
+
+    <td>Bottom middle cell</td>
+
+    <td>Bottom right cell</td>
+  </tr>
+</table>]]></programlisting>
+	</example>
+      </sect3>
+    </sect2>
+
+    <sect2>
+      <title>In-line elements</title>
+
+      <sect3>
+	<title>Emphasizing information</title>
+
+	<para>You have two levels of emphasis available in HTML,
+	  <sgmltag>em</sgmltag> and <sgmltag>strong</sgmltag>.
+	  <sgmltag>em</sgmltag> is for a normal level of emphasis and
+	  <sgmltag>strong</sgmltag> indicates stronger emphasis.</para>
+
+	<para>Typically, <sgmltag>em</sgmltag> is rendered in italic and
+	  <sgmltag>strong</sgmltag> is rendered in bold.  This is not always
+	  the case, however, and you should not rely on it.</para>
+
+	<example>
+	  <title><sgmltag>em</sgmltag> and <sgmltag>strong</sgmltag></title>
+
+	  <para>Use:</para>
+
+	  <programlisting><![ CDATA [<p><em>This</em> has been emphasized, while
+  <strong>this</strong> has been strongly emphasized.</p>]]></programlisting>
+	</example>
+      </sect3>
+
+      <sect3>
+	<title>Bold and italics</title>
+
+	<para>Because HTML includes presentational markup, you can also
+	  indicate that particular content should be rendered in bold or
+	  italic.  The elements are <sgmltag>b</sgmltag> and
+	  <sgmltag>i</sgmltag> respectively.</para>
+
+	<example>
+	  <title><sgmltag>b</sgmltag> and <sgmltag>i</sgmltag></title>
+
+	  <programlisting><![ CDATA [<p><b>This</b> is in bold, while <i>this</i> is
+  in italics.</p>]]></programlisting>
+	</example>
+      </sect3>
+
+      <sect3>
+	<title>Indicating fixed pitch text</title>
+
+	<para>If you have content that should be rendered in a fixed pitch
+	  (typewriter) typeface, use <sgmltag>tt</sgmltag> (for
+	  <quote>teletype</quote>).</para>
+
+	<example>
+	  <title><sgmltag>tt</sgmltag></title>
+
+	  <para>Use:</para>
+
+	  <programlisting><![ CDATA [<p>This document was originally written by
+  Nik Clayton, who can be reached by email as
+  <tt>nik@FreeBSD.org</tt>.</p>]]></programlisting>
+	</example>
+      </sect3>
+
+      <sect3>
+	<title>Content size</title>
+
+	<para>You can indicate that content should be shown in a larger or
+	  smaller font.  There are three ways of doing this.</para>
+
+	<orderedlist>
+	  <listitem>
+	    <para>Use <sgmltag>big</sgmltag> and <sgmltag>small</sgmltag>
+	      around the content you wish to change size.  These tags can be
+	      nested, so <literal>&lt;big&gt;&lt;big&gt;This is much
+		bigger&lt;/big&gt;&lt;/big&gt;</literal> is possible.</para>
+	  </listitem>
+
+	  <listitem>
+	    <para>Use <sgmltag>font</sgmltag> with the <literal>size</literal>
+	      attribute set to <literal>+1</literal> or <literal>-1</literal>
+	      respectively.  This has the same effect as using
+	      <sgmltag>big</sgmltag> or <sgmltag>small</sgmltag>.  However,
+	      the use of this approach is deprecated.</para>
+	  </listitem>
+
+	  <listitem>
+	    <para>Use <sgmltag>font</sgmltag> with the <literal>size</literal>
+	      attribute set to a number between 1 and 7.  The default font size
+	      is <literal>3</literal>.  This approach is deprecated.</para>
+	  </listitem>
+	</orderedlist>
+
+	<example>
+	  <title><sgmltag>big</sgmltag>, <sgmltag>small</sgmltag>, and
+	    <sgmltag>font</sgmltag></title>
+
+	  <para>The following fragments all do the same thing.</para>
+
+	  <programlisting><![ CDATA [<p>This text is <small>slightly smaller</small>.  But
+  this text is <big>slightly bigger</big>.</p>
+
+<p>This text is <font size="-1">slightly smaller</font>.  But
+  this text is <font size="+1">slightly bigger</font.</p>
+
+<p>This text is <font size="2">slightly smaller</font>.  But
+  this text is <font size="4">slightly bigger</font>.</p>]]></programlisting>
+	</example>
+      </sect3>
+    </sect2>
+
+    <sect2>
+      <title>Links</title>
+
+      <note>
+	<para>Links are also in-line elements.</para>
+      </note>
+
+      <sect3>
+	<title>Linking to other documents on the WWW</title>
+
+	<para>In order to include a link to another document on the WWW you
+	  must know the URL of the document you want to link to.</para>
+
+	<para>The link is indicated with <sgmltag>a</sgmltag>, and the
+	  <literal>href</literal> attribute contains the URL of the target
+	  document.  The content of the element becomes the link, and is
+	  normally indicated to the user in some way (underlining, change of
+	  color, different mouse cursor when over the link, and so
+	  on).</para>
+
+	<example>
+	  <title>Using <literal>&lt;a href="..."&gt;</literal></title>
+
+	  <para>Use:</para>
+
+	  <programlisting><![ CDATA [<p>More information is available at the
+  <a href="http://www.FreeBSD.org/">FreeBSD web site</a>.</p>]]></programlisting>
+	</example>
+
+	<para>These links will take the user to the top of the chosen
+	  document.</para>
+      </sect3>
+      
+      <sect3>
+	<title>Linking to other parts of documents</title>
+
+	<para>Linking to a point within another document (or within the same
+	  document) requires that the document author include anchors that you
+	  can link to.</para>
+
+	<para>Anchors are indicated with <sgmltag>a</sgmltag> and the
+	  <literal>name</literal> attribute instead of
+	  <literal>href</literal>.</para>
+
+	<example>
+	  <title>Using <literal>&lt;a name="..."&gt;</literal></title>
+
+	  <para>Use:</para>
+
+	  <programlisting><![ CDATA [<p><a name="para1">This</a> paragraph can be referenced
+  in other links with the name <tt>para1</tt>.</p>]]></programlisting>
+	</example>
+
+	<para>To link to a named part of a document, write a normal link to
+	  that document, but include the name of the anchor after a
+	  <literal>#</literal> symbol.</para>
+
+	<example>
+	  <title>Linking to a named part of another document</title>
+
+	  <para>Assume that the <literal>para1</literal> example resides in a
+	    document called <filename>foo.html</filename>.</para>
+
+	  <programlisting><![ CDATA [<p>More information can be found in the
+  <a href="foo.html#para1">first paragraph</a> of
+  <tt>foo.html</tt>.</p>]]></programlisting>
+	</example>
+
+	<para>If you are linking to a named anchor within the same document
+	  then you can omit the document's URL, and just include the name of
+	  the anchor (with the preceding <literal>#</literal>).</para>
+
+	<example>
+	  <title>Linking to a named part of the same document</title>
+
+	  <para>Assume that the <literal>para1</literal> example resides in
+	    this document:</para>
+
+	  <programlisting><![ CDATA [<p>More information can be found in the
+  <a href="#para1">first paragraph</a> of this
+  document.</p>]]></programlisting>
+	</example>
+      </sect3>
+    </sect2>
+  </sect1>
+  
+  <sect1 id="sgml-markup-docbook">
+    <title>DocBook</title>
+
+    <para>DocBook was originally developed by HaL Computer Systems and O'Reilly
+      &amp; Associates to be a DTD for writing technical documentation
+      <footnote><para>A short history can be found under <ulink
+      url="http://www.oasis-open.org/committees/docbook/intro.shtml">
+      http://www.oasis-open.org/committees/docbook/intro.shtml</ulink>.
+      </para></footnote>. Since 1998 it is maintained by the <ulink
+      url="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=docbook">
+      DocBook Technical Committee</ulink>.   As such, and unlike LinuxDoc
+      and HTML, DocBook is very heavily oriented towards markup that
+      describes <emphasis>what</emphasis> something is, rather than describing
+      <emphasis>how</emphasis> it should be presented.</para>
+
+    <note>
+      <title><literal>formal</literal> vs. <literal>informal</literal></title>
+
+      <para>Some elements may exist in two forms, <emphasis>formal</emphasis>
+	and <emphasis>informal</emphasis>.  Typically, the formal version of
+	the element will consist of a title followed by the informal
+	version of the element.  The informal version will not have a
+	title.</para>
+    </note>
+    
+    <para>The DocBook DTD is available from the ports collection in the
+      <filename role="package">textproc/docbook</filename> port.  It is automatically
+      installed as part of the <filename role="package">textproc/docproj</filename>
+      port.</para>
+    
+    <sect2>
+      <title>FreeBSD extensions</title>
+
+      <para>The FreeBSD Documentation Project has extended the DocBook DTD by
+	adding some new elements.  These elements serve to make some of the
+	markup more precise.</para>
+
+      <para>Where a FreeBSD specific element is listed below it is clearly
+	marked.</para>
+
+      <para>Throughout the rest of this document, the term
+	<quote>DocBook</quote> is used to mean the FreeBSD extended DocBook
+	DTD.</para>
+      
+      <note>
+	<para>There is nothing about these extensions that is FreeBSD
+	  specific, it was just felt that they were useful enhancements for
+	  this particular project.  Should anyone from any of the other *nix
+	  camps (NetBSD, OpenBSD, Linux, &hellip;) be interested in
+	  collaborating on a standard DocBook extension set, please get in
+	  touch with &a.doceng;.</para>
+      </note>
+
+      <para>The FreeBSD extensions are not (currently) in the ports
+	collection.  They are stored in the FreeBSD CVS tree, as <ulink
+	url="http://www.FreeBSD.org/cgi/cvsweb.cgi/doc/share/sgml/freebsd.dtd">doc/share/sgml/freebsd.dtd</ulink>.</para>
+    </sect2>
+
+    <sect2>
+      <title>Formal Public Identifier (FPI)</title>
+
+      <para>In compliance with the DocBook guidelines for writing FPIs for
+	  DocBook customizations, the FPI for the FreeBSD extended DocBook DTD
+	  is:</para>
+
+	<programlisting>PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN"</programlisting>
+    </sect2>
+
+    <sect2>
+      <title>Document structure</title>
+
+      <para>DocBook allows you to structure your documentation in several
+	ways.  In the FreeBSD Documentation Project we are using two primary
+	types of DocBook document: the book and the article.</para>
+
+      <para>A book is organized into <sgmltag>chapter</sgmltag>s.  This is a
+	mandatory requirement.  There may be <sgmltag>part</sgmltag>s between
+	the book and the chapter to provide another layer of organization.
+	The Handbook is arranged in this way.</para>
+
+      <para>A chapter may (or may not) contain one or more sections.  These
+	are indicated with the <sgmltag>sect1</sgmltag> element.  If a section
+	contains another section then use the <sgmltag>sect2</sgmltag>
+	element, and so on, up to <sgmltag>sect5</sgmltag>.</para>
+
+      <para>Chapters and sections contain the remainder of the content.</para>
+
+      <para>An article is simpler than a book, and does not use chapters.
+	Instead, the content of an article is organized into one or more
+	sections, using the same <sgmltag>sect1</sgmltag> (and
+	<sgmltag>sect2</sgmltag> and so on) elements that are used in
+	books.</para>
+
+      <para>Obviously, you should consider the nature of the documentation you 
+	are writing in order to decide whether it is best marked up as a book
+	or an article.  Articles are well suited to information that does not
+	need to be broken down into several chapters, and that is, relatively 
+	speaking, quite short, at up to 20-25 pages of content.  Books are
+	best suited to information that can be broken up into several
+	chapters, possibly with appendices and similar content as well.</para>
+
+      <para>The <ulink url="&url.base;/docs.html">FreeBSD
+	  tutorials</ulink> are all marked up as articles, while this
+	document, the <ulink url="&url.books.faq;/index.html">FreeBSD
+	  FAQ</ulink>, and the <ulink
+	  url="&url.books.handbook;/index.html">FreeBSD Handbook</ulink> are
+	all marked up as books.</para>
+
+      <sect3>
+	<title>Starting a book</title>
+
+	<para>The content of the book is contained within the
+	  <sgmltag>book</sgmltag> element.  As well as containing structural
+	  markup, this element can contain elements that include additional
+	  information about the book.  This is either meta-information, used
+	  for reference purposes, or additional content used to produce a
+	  title page.</para>
+
+	<para>This additional information should be contained within
+	  <sgmltag>bookinfo</sgmltag>.</para>
+
+	<example>
+	  <title>Boilerplate <sgmltag>book</sgmltag> with
+	    <sgmltag>bookinfo</sgmltag></title>
+
+	  <!-- Can't put this in a marked section because of the
+               replaceable elements -->
+	  <programlisting>&lt;book>
+  &lt;bookinfo>
+    &lt;title><replaceable>Your title here</replaceable>&lt;/title>
+    
+    &lt;author>
+      &lt;firstname><replaceable>Your first name</replaceable>&lt;/firstname>
+      &lt;surname><replaceable>Your surname</replaceable>&lt;/surname>
+      &lt;affiliation>
+        &lt;address>&lt;email><replaceable>Your email address</replaceable>&lt;/email>&lt;/address>
+      &lt;/affiliation>
+    &lt;/author>
+
+    &lt;copyright>
+      &lt;year><replaceable>1998</replaceable>&lt;/year>
+      &lt;holder role="mailto:<replaceable>your email address</replaceable>"><replaceable>Your name</replaceable>&lt;/holder>
+    &lt;/copyright>
+
+    &lt;releaseinfo>&#36;FreeBSD&#36;&lt;/releaseinfo>
+
+    &lt;abstract>
+      &lt;para><replaceable>Include an abstract of the book's contents here.</replaceable>&lt;/para>
+    &lt;/abstract>
+  &lt;/bookinfo>
+
+  &hellip;
+
+&lt;/book></programlisting>
+	</example>
+      </sect3>
+
+      <sect3>
+	<title>Starting an article</title>
+
+	<para>The content of the article is contained within the
+	  <sgmltag>article</sgmltag> element.  As well as containing
+	  structural markup, this element can contain elements that include
+	  additional information about the article.  This is either
+	  meta-information, used for reference purposes, or additional content
+	  used to produce a title page.</para>
+
+	<para>This additional information should be contained within
+	  <sgmltag>articleinfo</sgmltag>.</para>
+
+	<example>
+	  <title>Boilerplate <sgmltag>article</sgmltag> with
+	    <sgmltag>articleinfo</sgmltag></title>
+
+	  <!-- Can't put this in a marked section because of the
+               replaceable elements -->
+	  <programlisting>&lt;article>
+  &lt;articleinfo>
+    &lt;title><replaceable>Your title here</replaceable>&lt;/title>
+    
+    &lt;author>
+      &lt;firstname><replaceable>Your first name</replaceable>&lt;/firstname>
+      &lt;surname><replaceable>Your surname</replaceable>&lt;/surname>
+      &lt;affiliation>
+        &lt;address>&lt;email><replaceable>Your email address</replaceable>&lt;/email>&lt;/address>
+      &lt;/affiliation>
+    &lt;/author>
+
+    &lt;copyright>
+      &lt;year><replaceable>1998</replaceable>&lt;/year>
+      &lt;holder role="mailto:<replaceable>your email address</replaceable>"><replaceable>Your name</replaceable>&lt;/holder>
+    &lt;/copyright>
+
+    &lt;releaseinfo>&#36;FreeBSD&#36;&lt;/releaseinfo>
+
+    &lt;abstract>
+      &lt;para><replaceable>Include an abstract of the article's contents here.</replaceable>&lt;/para>
+    &lt;/abstract>
+  &lt;/articleinfo>
+
+  &hellip;
+
+&lt;/article></programlisting>
+	</example>	
+      </sect3>
+      <sect3>
+	<title>Indicating chapters</title>
+
+	<para>Use <sgmltag>chapter</sgmltag> to mark up your chapters.  Each
+	  chapter has a mandatory <sgmltag>title</sgmltag>.  Articles do not
+	  contain chapters, they are reserved for books.</para>
+
+	<example>
+	  <title>A simple chapter</title>
+
+	  <programlisting><![ CDATA [<chapter>
+  <title>The chapter's title</title>
+
+  ...
+</chapter>]]></programlisting>
+	</example>
+
+	<para>A chapter cannot be empty; it must contain elements in addition
+	  to <sgmltag>title</sgmltag>.  If you need to include an empty
+	  chapter then just use an empty paragraph.</para>
+
+	<example>
+	  <title>Empty chapters</title>
+
+	  <programlisting><![ CDATA [<chapter>
+  <title>This is an empty chapter</title>
+
+  <para></para>
+</chapter>]]></programlisting>	    
+	</example>
+      </sect3>
+
+      <sect3>
+	<title>Sections below chapters</title>
+
+	<para>In books, chapters may (but do not need to) be broken up into
+	  sections, subsections, and so on.  In articles, sections are the
+	  main structural element, and each  article must contain at least one
+	  section.  Use the
+	  <sgmltag>sect<replaceable>n</replaceable></sgmltag> element.  The
+	  <replaceable>n</replaceable> indicates the section number, which
+	  identifies the section level.</para>
+
+	<para>The first <sgmltag>sect<replaceable>n</replaceable></sgmltag> is
+	  <sgmltag>sect1</sgmltag>.  You can have one or more of these in a
+	  chapter.  They can contain one or more <sgmltag>sect2</sgmltag>
+	  elements, and so on, down to <sgmltag>sect5</sgmltag>.</para>
+
+	<example>
+	  <title>Sections in chapters</title>
+
+	  <programlisting><![ RCDATA [<chapter>
+  <title>A sample chapter</title>
+
+  <para>Some text in the chapter.</para>
+
+  <sect1>
+    <title>First section (1.1)</title>
+
+    &hellip;
+  </sect1>
+
+  <sect1>
+    <title>Second section (1.2)</title>
+
+    <sect2>
+      <title>First sub-section (1.2.1)</title>
+
+      <sect3>
+        <title>First sub-sub-section (1.2.1.1)</title>
+
+        &hellip;
+      </sect3>
+    </sect2>
+
+    <sect2>
+      <title>Second sub-section (1.2.2)</title>
+
+      &hellip;
+    </sect2>
+  </sect1>
+</chapter>]]></programlisting>
+	</example>
+	
+	<note>
+	  <para>This example includes section numbers in the section titles.
+	    You should not do this in your documents.  Adding the section
+	    numbers is carried out by the stylesheets (of which more
+	    later), and you do not need to manage them yourself.</para>
+	</note>
+      </sect3>
+      
+      <sect3>
+	<title>Subdividing using <sgmltag>part</sgmltag>s</title>
+
+	<para>You can introduce another layer of organization between
+	  <sgmltag>book</sgmltag> and <sgmltag>chapter</sgmltag> with one or
+	  more <sgmltag>part</sgmltag>s.  This cannot be done in an
+	  <sgmltag>article</sgmltag>.</para>
+
+	<programlisting><![ CDATA [<part>
+  <title>Introduction</title>
+
+  <chapter>
+    <title>Overview</title>
+
+    ...
+  </chapter>
+
+  <chapter>
+    <title>What is FreeBSD?</title>
+
+    ...
+  </chapter>
+
+  <chapter>
+    <title>History</title>
+
+    ...
+  </chapter>
+</part>]]></programlisting>
+      </sect3>
+    </sect2>
+    
+    <sect2>
+      <title>Block elements</title>
+      
+      <sect3>
+	<title>Paragraphs</title>
+	
+	<para>DocBook supports three types of paragraphs:
+	  <sgmltag>formalpara</sgmltag>, <sgmltag>para</sgmltag>, and
+	  <sgmltag>simpara</sgmltag>.</para>
+	
+	<para>Most of the time you will only need to use
+	  <sgmltag>para</sgmltag>.  <sgmltag>formalpara</sgmltag> includes a
+	  <sgmltag>title</sgmltag> element, and <sgmltag>simpara</sgmltag>
+	  disallows some elements from within <sgmltag>para</sgmltag>.  Stick
+	  with <sgmltag>para</sgmltag>.</para>
+	  
+	<example>
+	  <title><sgmltag>para</sgmltag></title>
+	  
+	  <para>Use:</para>
+	  
+	  <programlisting><![ CDATA [<para>This is a paragraph.  It can contain just about any
+  other element.</para> ]]></programlisting>
+
+	  <para>Appearance:</para>
+	  
+	  <para>This is a paragraph.  It can contain just about any other
+	    element.</para>
+	</example>
+      </sect3>
+      
+      <sect3>
+	<title>Block quotations</title>
+	
+	<para>A block quotation is an extended quotation from another document
+	  that should not appear within the current paragraph.  You will
+	  probably only need it infrequently.</para>
+	
+	<para>Blockquotes can optionally contain a title and an attribution
+	  (or they can be left untitled and unattributed).</para>
+
+	<example>
+	  <title><sgmltag>blockquote</sgmltag></title>
+	  
+	  <para>Use:</para>
+	  
+	  <programlisting><![ CDATA [<para>A small excerpt from the US Constitution:</para>
+	      
+<blockquote>
+  <title>Preamble to the Constitution of the United States</title>
+
+  <attribution>Copied from a web site somewhere</attribution>
+	    
+  <para>We the People of the United States, in Order to form a more perfect
+    Union, establish Justice, insure domestic Tranquility, provide for the
+    common defence, promote the general Welfare, and secure the Blessings
+    of Liberty to ourselves and our Posterity, do ordain and establish this
+    Constitution for the United States of America.</para>
+</blockquote>]]></programlisting>
+
+	  <para>Appearance:</para>
+	  
+	  <blockquote>
+	    <title>Preamble to the Constitution of the United States</title>
+	    
+	    <attribution>Copied from a web site somewhere</attribution>
+	    
+	    <para>We the People of the United States, in Order to form a more
+	      perfect Union, establish Justice, insure domestic Tranquility,
+	      provide for the common defence, promote the general Welfare, and
+	      secure the Blessings of Liberty to ourselves and our Posterity,
+	      do ordain and establish this Constitution for the United States
+	      of America.</para>
+	  </blockquote>	  
+	</example>
+      </sect3>
+      
+      <sect3>
+	<title>Tips, notes, warnings, cautions, important information and
+	  sidebars.</title>
+	  
+	<para>You may need to include extra information separate from the
+	  main body of the text.  Typically this is <quote>meta</quote>
+	  information that the user should be aware of.</para>
+	
+	<para>Depending on the nature of the information, one of
+	  <sgmltag>tip</sgmltag>, <sgmltag>note</sgmltag>,
+	  <sgmltag>warning</sgmltag>, <sgmltag>caution</sgmltag>, and
+	  <sgmltag>important</sgmltag> should be used.  Alternatively, if the
+	  information is related to the main text but is not one of the above,
+	  use <sgmltag>sidebar</sgmltag>.</para>
+
+	<para>The circumstances in which to choose one of these elements over
+	  another is unclear.  The DocBook documentation suggests:</para>
+	
+	<itemizedlist>
+	  <listitem>
+	    <para>A Note is for information that should be heeded by all
+	      readers.</para>
+	  </listitem>
+	  
+	  <listitem>
+	    <para>An Important element is a variation on Note.</para>
+	  </listitem>
+	  
+	  <listitem>
+	    <para>A Caution is for information regarding possible data loss
+	      or software damage.</para>
+	  </listitem>
+	  
+	  <listitem>
+	    <para>A Warning is for information regarding possible hardware
+	      damage or injury to life or limb.</para>
+	  </listitem>
+	</itemizedlist>
+	
+	<example>
+	  <title><sgmltag>warning</sgmltag></title>
+	  
+	  <para>Use:</para>
+	  
+	  <programlisting><![ CDATA [<warning>
+  <para>Installing FreeBSD may make you want to delete Windows from your
+    hard disk.</para>
+</warning>]]></programlisting>
+	  </example>
+	  
+	<!-- Need to do this outside of the example -->
+	<warning>
+	  <para>Installing FreeBSD may make you want to delete Windows from
+	    your hard disk.</para>
+	</warning>	  
+      </sect3>
+      
+      <sect3>
+	<title>Lists and procedures</title>
+	
+	<para>You will often need to list pieces of information to the user,
+	  or present them with a number of steps that must be carried out in
+	  order to accomplish a particular goal.</para>
+	
+	<para>In order to do this, use <sgmltag>itemizedlist</sgmltag>,
+	  <sgmltag>orderedlist</sgmltag>, or
+	  <sgmltag>procedure</sgmltag><footnote><para>There are other types of
+	      list element in DocBook, but we are not concerned with those at
+	      the moment.</para>
+	  </footnote>
+	</para>
+	  
+	<para><sgmltag>itemizedlist</sgmltag> and
+	  <sgmltag>orderedlist</sgmltag> are similar to their counterparts in
+	  HTML, <sgmltag>ul</sgmltag> and <sgmltag>ol</sgmltag>.  Each one
+	  consists of one or more <sgmltag>listitem</sgmltag> elements, and
+	  each <sgmltag>listitem</sgmltag> contains one or more block
+	  elements.  The <sgmltag>listitem</sgmltag> elements are analogous to
+	  HTML's <sgmltag>li</sgmltag> tags.  However, unlike HTML, they are
+	  required.</para>
+	
+	<para><sgmltag>procedure</sgmltag> is slightly different.  It consists
+	  of <sgmltag>step</sgmltag>s, which may in turn consists of more
+	  <sgmltag>step</sgmltag>s or <sgmltag>substep</sgmltag>s.  Each
+	  <sgmltag>step</sgmltag> contains block elements.</para>
+
+	<example>
+	  <title><sgmltag>itemizedlist</sgmltag>,
+	    <sgmltag>orderedlist</sgmltag>, and
+	    <sgmltag>procedure</sgmltag></title>
+	  
+	  <para>Use:</para>
+	    
+	  <programlisting><![ CDATA [<itemizedlist>
+  <listitem>
+    <para>This is the first itemized item.</para>
+  </listitem>
+
+  <listitem>
+    <para>This is the second itemized item.</para>
+  </listitem>
+</itemizedlist>
+
+<orderedlist>
+  <listitem>
+    <para>This is the first ordered item.</para>
+  </listitem>
+
+  <listitem>
+    <para>This is the second ordered item.</para>
+  </listitem>
+</orderedlist>
+
+<procedure>
+  <step>
+    <para>Do this.</para>
+  </step>
+
+  <step>
+    <para>Then do this.</para>
+  </step>
+
+  <step>
+    <para>And now do this.</para>
+  </step>
+</procedure>]]></programlisting>
+	  
+	  <para>Appearance:</para>
+	  
+	  <itemizedlist>
+	    <listitem>
+	      <para>This is the first itemized item.</para>
+	    </listitem>
+	    
+	    <listitem>
+	      <para>This is the second itemized item.</para>
+	    </listitem>
+	  </itemizedlist>
+	  
+	  <orderedlist>
+	    <listitem>
+	      <para>This is the first ordered item.</para>
+	    </listitem>
+	    
+	    <listitem>
+	      <para>This is the second ordered item.</para>
+	    </listitem>
+	  </orderedlist>
+	</example>
+
+	<!-- Can't have <procedure> inside <example>, so this is a cheat -->
+	
+	<procedure>
+	  <step>
+	    <para>Do this.</para>
+	  </step>
+	  
+	  <step>
+	    <para>Then do this.</para>
+	  </step>
+	  
+	  <step>
+	    <para>And now do this.</para>
+	  </step>
+	</procedure>	  
+      </sect3>
+      
+      <sect3>
+	<title>Showing file samples</title>
+	
+	<para>If you want to show a fragment of a file (or perhaps a complete
+	  file) to the user, wrap it in the <sgmltag>programlisting</sgmltag>
+	  element.</para>
+	  
+	<para>White space and line breaks within
+	  <sgmltag>programlisting</sgmltag> <emphasis>are</emphasis>
+	  significant.  In particular, this means that the opening tag should
+	  appear on the same line as the first line of the output, and the
+	  closing tag should appear on the same line as the last line of the
+	  output, otherwise spurious blank lines may be included.</para>
+	  
+	<example>
+	  <title><sgmltag>programlisting</sgmltag></title>
+	    
+	  <para>Use:</para>
+	    
+	  <programlisting><![ CDATA[<para>When you have finished, your program should look like
+  this:</para>
+
+<programlisting>#include &lt;stdio.h&gt;
+
+int
+main(void)
+{
+    printf("hello, world\n");
+}</programlisting>]]></programlisting>
+
+	  <para>Notice how the angle brackets in the
+	    <literal>#include</literal> line need to be referenced by their
+	    entities instead of being included literally.</para>
+	    
+	  <para>Appearance:</para>
+	    
+	  <para>When you have finished, your program should look like
+	    this:</para>
+	    
+	  <programlisting>#include &lt;stdio.h&gt;
+
+int
+main(void)
+{
+    printf("hello, world\n");
+}</programlisting>	    
+	</example>
+      </sect3>
+
+      <sect3>
+	<title>Callouts</title>
+
+	<para>A callout is a mechanism for referring back to an earlier piece
+	  of text or specific position within an earlier example without
+	  linking to it within the text.</para>
+
+	<para>To do this, mark areas of interest in your example
+	  (<sgmltag>programlisting</sgmltag>,
+	  <sgmltag>literallayout</sgmltag>, or whatever) with the
+	  <sgmltag>co</sgmltag> element.  Each element must have a unique
+	  <literal>id</literal> assigned to it.  After the example include a
+	  <sgmltag>calloutlist</sgmltag> that refers back to the example and
+	  provides additional commentary.</para>
+	
+	<example>
+	  <title><sgmltag>co</sgmltag> and
+	    <sgmltag>calloutlist</sgmltag></title>
+
+	  <programlisting><![ CDATA[<para>When you have finished, your program should look like
+  this:</para>
+
+<programlisting>#include &lt;stdio.h&gt; <co id="co-ex-include">
+
+int <co id="co-ex-return">
+main(void)
+{
+    printf("hello, world\n"); <co id="co-ex-printf">
+}</programlisting>
+
+<calloutlist>
+  <callout arearefs="co-ex-include">
+    <para>Includes the standard IO header file.</para>
+  </callout>
+
+  <callout arearefs="co-ex-return">
+    <para>Specifies that <function>main()</function> returns an
+      int.</para>
+  </callout>
+
+  <callout arearefs="co-ex-printf">
+    <para>The <function>printf()</function> call that writes
+      <literal>hello, world</literal> to standard output.</para>
+  </callout>
+</calloutlist>]]></programlisting>
+
+	  <para>Appearance:</para>
+
+	  <para>When you have finished, your program should look like
+	    this:</para>
+
+	  <programlisting>#include &lt;stdio.h&gt; <co id="co-ex-include">
+
+int <co id="co-ex-return">
+main(void)
+{
+    printf("hello, world\n"); <co id="co-ex-printf">
+}</programlisting>
+
+	  <calloutlist>
+	    <callout arearefs="co-ex-include">
+	      <para>Includes the standard IO header file.</para>
+	    </callout>
+	    
+	    <callout arearefs="co-ex-return">
+	      <para>Specifies that <function>main()</function> returns an
+		int.</para>
+	    </callout>
+	    
+	    <callout arearefs="co-ex-printf">
+	      <para>The <function>printf()</function> call that writes
+		<literal>hello, world</literal> to standard output.</para>
+	    </callout>
+	  </calloutlist>	  
+	</example>
+      </sect3>
+      
+      <sect3>
+	<title>Tables</title>
+	
+	<para>Unlike HTML, you do not need to use tables for layout purposes,
+	  as the stylesheet handles those issues for you.  Instead, just use
+	  tables for marking up tabular data.</para>
+
+	<para>In general terms (and see the DocBook documentation for more
+	  detail) a table (which can be either formal or informal) consists of
+	  a <sgmltag>table</sgmltag> element.  This contains at least one
+	  <sgmltag>tgroup</sgmltag> element, which specifies (as an attribute)
+	  the number of columns in this table group.  Within the tablegroup
+	  you can then have one <sgmltag>thead</sgmltag> element, which
+	  contains elements for the table headings (column headings), and one
+	  <sgmltag>tbody</sgmltag> which contains the body of the
+	  table.</para>
+
+	<para>Both <sgmltag>tgroup</sgmltag> and <sgmltag>thead</sgmltag>
+	  contain <sgmltag>row</sgmltag> elements, which in turn contain
+	  <sgmltag>entry</sgmltag> elements.  Each <sgmltag>entry</sgmltag>
+	  element specifies one cell in the table.</para>
+	  
+	<example>
+	  <title><sgmltag>informaltable</sgmltag></title>
+	  
+	  <para>Use:</para>
+	  
+	  <programlisting><![ CDATA [<informaltable frame="none" pgwide="1">
+  <tgroup cols="2">
+    <thead>
+      <row>
+        <entry>This is column head 1</entry>
+        <entry>This is column head 2</entry>
+      </row>
+    </thead>
+
+    <tbody>
+      <row>
+        <entry>Row 1, column 1</entry>
+        <entry>Row 1, column 2</entry>
+      </row>
+
+      <row>
+        <entry>Row 2, column 1</entry>
+        <entry>Row 2, column 2</entry>
+      </row>
+    </tbody>
+  </tgroup>
+</informaltable>]]></programlisting>
+	  
+	  <para>Appearance:</para>
+	  
+	  <informaltable frame="none" pgwide="1">
+	    <tgroup cols="2">
+	      <thead>
+		<row>
+		  <entry>This is column head 1</entry>
+		  <entry>This is column head 2</entry>
+		</row>
+	      </thead>
+	      
+	      <tbody>
+		<row>
+		  <entry>Row 1, column 1</entry>
+		  <entry>Row 1, column 2</entry>
+		</row>
+		
+		<row>
+		  <entry>Row 2, column 1</entry>
+		  <entry>Row 2, column 2</entry>
+		</row>
+	      </tbody>
+	    </tgroup>
+	  </informaltable>
+	</example>
+	
+	<para>Always use the <literal>pgwide</literal> attribute with
+	  a value of <literal>1</literal> with the
+	  <sgmltag>informaltable</sgmltag> element.  A bug in Internet
+	  Explorer can cause the table to render incorrectly if this
+	  is omitted.</para>
+
+	<para>If you do not want a border around the table the
+	  <literal>frame</literal> attribute can be added to the
+	  <sgmltag>informaltable</sgmltag> element with a value of
+	  <literal>none</literal> (i.e., <literal>&lt;informaltable
+	    frame="none"&gt;</literal>).</para>
+
+	<example>
+	  <title>Tables where <literal>frame="none"</literal></title>
+	  
+	  <para>Appearance:</para>
+	
+	  <informaltable frame="none" pgwide="1">
+	    <tgroup cols="2">
+	      <thead>
+		<row>
+		  <entry>This is column head 1</entry>
+		  <entry>This is column head 2</entry>
+		</row>
+	      </thead>
+	      
+	      <tbody>
+		<row>
+		  <entry>Row 1, column 1</entry>
+		  <entry>Row 1, column 2</entry>
+		</row>
+		
+		<row>
+		  <entry>Row 2, column 1</entry>
+		  <entry>Row 2, column 2</entry>
+		</row>
+	      </tbody>
+	    </tgroup>
+	  </informaltable>
+	</example>
+      </sect3>
+      
+      <sect3>
+	<title>Examples for the user to follow</title>
+	
+	<para>A lot of the time you need to show examples for the user to
+	  follow.  Typically, these will consist of dialogs with the computer;
+	  the user types in a command, the user gets a response back, they
+	  type in another command, and so on.</para>
+	  
+	<para>A number of distinct elements and entities come into play
+	  here.</para>
+	
+	<variablelist>
+	  <varlistentry>
+	    <term><sgmltag>screen</sgmltag></term>
+	    
+	    <listitem>
+	      <para>Everything the user sees in this example will be on the
+		computer screen, so the next element is
+		<sgmltag>screen</sgmltag>.</para>
+		
+	      <para>Within <sgmltag>screen</sgmltag>, white space is
+		significant.</para>
+	    </listitem>
+	  </varlistentry>
+	  
+	  <varlistentry>
+	    <term><sgmltag>prompt</sgmltag>,
+	      <literal>&amp;prompt.root;</literal> and
+	      <literal>&amp;prompt.user;</literal></term>
+	    
+	    <listitem>
+	      <para>Some of the things the user will be seeing on the screen
+		are prompts from the computer (either from the operating system, command
+		shell, or application).  These should be marked up using
+		<sgmltag>prompt</sgmltag>.</para>
+
+	      <para>As a special case, the two shell prompts for the normal
+		user and the root user have been provided as entities.  Every
+		time you want to indicate the user is at a shell prompt, use
+		one of <literal>&amp;prompt.root;</literal> and
+		<literal>&amp;prompt.user;</literal> as necessary.  They do
+		not need to be inside <sgmltag>prompt</sgmltag>.</para>
+
+	      <note>
+		<para><literal>&amp;prompt.root;</literal> and
+		  <literal>&amp;prompt.user;</literal> are FreeBSD
+		  extensions to DocBook, and are not part of the original
+		  DTD.</para>
+	      </note>
+	    </listitem>
+	  </varlistentry>
+	  
+	  <varlistentry>
+	    <term><sgmltag>userinput</sgmltag></term>
+	    
+	    <listitem>
+	      <para>When displaying text that the user should type in, wrap it
+		in <sgmltag>userinput</sgmltag> tags.  It will probably be
+		displayed differently to the user.</para>
+	    </listitem>
+	  </varlistentry>
+	</variablelist>
+	  
+	<example>
+	  <title><sgmltag>screen</sgmltag>, <sgmltag>prompt</sgmltag>, and
+	    <sgmltag>userinput</sgmltag></title>
+	  
+	  <para>Use:</para>
+	  
+	  <programlisting><![ CDATA [<screen>&prompt.user; <userinput>ls -1</userinput>
+foo1
+foo2
+foo3
+&prompt.user; <userinput>ls -1 | grep foo2</userinput>
+foo2
+&prompt.user; <userinput>su</userinput>
+<prompt>Password: </prompt>
+&prompt.root; <userinput>cat foo2</userinput>
+This is the file called 'foo2'</screen>]]></programlisting>
+	  
+	  <para>Appearance:</para>
+	
+	  <screen>&prompt.user; <userinput>ls -1</userinput>
+foo1
+foo2
+foo3
+&prompt.user; <userinput>ls -1 | grep foo2</userinput>
+foo2
+&prompt.user; <userinput>su</userinput>
+<prompt>Password: </prompt>
+&prompt.root; <userinput>cat foo2</userinput>
+This is the file called 'foo2'</screen>
+	</example>
+	
+	<note>
+	  <para>Even though we are displaying the contents of the file
+	    <filename>foo2</filename>, it is <emphasis>not</emphasis> marked
+	    up as <sgmltag>programlisting</sgmltag>.  Reserve
+	    <sgmltag>programlisting</sgmltag> for showing fragments of files
+	    outside the context of user actions.</para>
+	</note>
+      </sect3>
+    </sect2>
+    
+    <sect2>
+      <title>In-line elements</title>
+      
+      <sect3>
+	<title>Emphasizing information</title>
+	
+	<para>When you want to emphasize a particular word or phrase, use
+	  <sgmltag>emphasis</sgmltag>.  This may be presented as italic, or
+	  bold, or might be spoken differently with a text-to-speech
+	  system.</para>
+	
+	<para>There is no way to change the presentation of the emphasis
+	  within your document, no equivalent of HTML's <sgmltag>b</sgmltag>
+	  and <sgmltag>i</sgmltag>.  If the information you are presenting is
+	  important then consider presenting it in
+	  <sgmltag>important</sgmltag> rather than
+	  <sgmltag>emphasis</sgmltag>.</para>
+	  
+	<example>
+	  <title><sgmltag>emphasis</sgmltag></title>
+	  
+	  <para>Use:</para>
+	  
+	  <programlisting><![ CDATA [<para>FreeBSD is without doubt <emphasis>the</emphasis>
+  premiere Unix like operating system for the Intel architecture.</para>]]></programlisting>
+	  
+	  <para>Appearance:</para>
+	
+	  <para>FreeBSD is without doubt <emphasis>the</emphasis> premiere Unix
+	    like operating system for the Intel architecture.</para>
+	</example>
+      </sect3>
+
+      <sect3>
+	<title>Quotations</title>
+
+	<para>To quote text from another document or source, or to denote
+	  a phrase that is used figuratively, use <sgmltag>quote</sgmltag>.
+	  Within a <sgmltag>quote</sgmltag> tag, you may use most of the
+	  markup tags available for normal text.</para>
+
+	<example>
+	  <title>Quotations</title>
+
+	  <para>Use:</para>
+
+	  <programlisting><![ CDATA [<para>However, make sure that the search does not go beyond the
+  <quote>boundary between local and public administration</quote>,
+  as RFC 1535 calls it.</para>]]></programlisting>
+
+	  <para>Appearance:</para>
+
+	  <para>However, make sure that the search does not go beyond the
+	    <quote>boundary between local and public administration</quote>,
+	    as RFC 1535 calls it.</para>
+	</example>
+      </sect3>
+      
+      <sect3>
+	<title>Keys, mouse buttons, and combinations</title>
+
+	<para>To refer to a specific key on the keyboard, use
+	  <sgmltag>keycap</sgmltag>.  To refer to a mouse button, use
+	  <sgmltag>mousebutton</sgmltag>.  And to refer to combinations of key
+	  presses or mouse clicks, wrap them all in
+	  <sgmltag>keycombo</sgmltag>.</para>
+
+	<para><sgmltag>keycombo</sgmltag> has an attribute called
+	  <literal>action</literal>, which may be one of
+	  <literal>click</literal>, <literal>double-click</literal>,
+	  <literal>other</literal>, <literal>press</literal>,
+	  <literal>seq</literal>, or <literal>simul</literal>.  The last two
+	  values denote whether the keys or buttons should be pressed in
+	  sequence, or simultaneously.</para>
+
+	<para>The stylesheets automatically add any connecting symbols, such
+	  as <literal>+</literal>, between the key names, when wrapped in
+	  <sgmltag>keycombo</sgmltag>.</para>
+	
+	<example>
+	  <title>Keys, mouse buttons, and combinations</title>
+	  
+	  <para>Use:</para>
+	  
+	  <programlisting><![ CDATA [<para>To switch to the second virtual terminal, press 
+  <keycombo action="simul"><keycap>Alt</keycap>
+    <keycap>F1</keycap></keycombo>.</para>
+
+<para>To exit <command>vi</command> without saving your work, type
+  <keycombo action="seq"><keycap>Esc</keycap><keycap>:</keycap>
+    <keycap>q</keycap><keycap>!</keycap></keycombo>.</para>
+
+<para>My window manager is configured so that
+  <keycombo action="simul"><keycap>Alt</keycap>
+    <mousebutton>right</mousebutton>
+  </keycombo> mouse button is used to move windows.</para>]]></programlisting>
+
+	  <para>Appearance:</para>
+	  
+	  <para>To switch to the second virtual terminal, press 
+	    <keycombo action="simul"><keycap>Alt</keycap>
+	      <keycap>F1</keycap></keycombo>.</para>
+
+	  <para>To exit <command>vi</command> without saving your work, type
+	    <keycombo action="seq"><keycap>Esc</keycap><keycap>:</keycap>
+	      <keycap>q</keycap><keycap>!</keycap></keycombo>.</para>
+
+	  <para>My window manager is configured so that
+	    <keycombo action="simul"><keycap>Alt</keycap>
+	      <mousebutton>right</mousebutton>
+	    </keycombo> mouse button is used to move windows.</para>
+	</example>
+      </sect3>
+      
+      <sect3>
+	<title>Applications, commands, options, and cites</title>
+	
+	<para>You will frequently want to refer to both applications and
+	  commands when writing for the Handbook.  The distinction between
+	  them is simple: an application is the name for a suite (or possibly
+	  just 1) of programs that fulfil a particular task.  A command is the
+	  name of a program that the user can run.</para>
+
+	<para>In addition, you will occasionally need to list one or more of
+	  the options that a command might take.</para>
+	
+	<para>Finally, you will often want to list a command with its manual
+	  section number, in the <quote>command(number)</quote> format so
+	  common in Unix manuals.</para>
+	
+	<para>Mark up application names with
+	  <sgmltag>application</sgmltag>.</para>
+	
+	<para>When you want to list a command with its manual section number
+	  (which should be most of the time) the DocBook element is 
+	  <sgmltag>citerefentry</sgmltag>.  This will contain a further two
+	  elements, <sgmltag>refentrytitle</sgmltag> and
+	  <sgmltag>manvolnum</sgmltag>.  The content of
+	  <sgmltag>refentrytitle</sgmltag> is the name of the command, and the
+	  content of <sgmltag>manvolnum</sgmltag> is the manual page
+	  section.</para>
+
+	<para>This can be cumbersome to write, and so a series of <link
+	    linkend="sgml-primer-general-entities">general entities</link>
+	  have been created to make this easier.  Each entity takes the form
+	  <literal>&amp;man.<replaceable>manual-page</replaceable>.<replaceable>manual-section</replaceable>;</literal>.</para>
+
+	<para>The file that contains these entities is in
+	  <filename>doc/share/sgml/man-refs.ent</filename>, and can be
+	  referred to using this FPI:</para>
+
+	<programlisting>PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN"</programlisting>
+
+	<para>Therefore, the introduction to your documentation will probably
+	  look like this:</para>
+
+	<programlisting>&lt;!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
+
+&lt;!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN"&gt;
+%man;
+
+&hellip;
+
+]&gt;</programlisting>
+
+	<para>Use <sgmltag>command</sgmltag> when you want to include a
+	  command name <quote>in-line</quote> but present it as something the
+	  user should type in.</para>
+
+	<para>Use <sgmltag>option</sgmltag> to mark up the options
+	  which will be passed to a command.</para>
+
+	<para>When referring to the same command multiple times in
+	  close proximity it is preferred to use the
+	  <literal>&amp;man.<replaceable>command</replaceable>.<replaceable>section</replaceable>;</literal>
+	  notation to markup the first reference and use
+	  <sgmltag>command</sgmltag> to markup subsequent references.
+	  This makes the generated output, especially HTML, appear
+	  visually better.</para>
+
+	<para>This can be confusing, and sometimes the choice is not always
+	  clear.  Hopefully this example makes it clearer.</para>
+
+	<example>
+	  <title>Applications, commands, and options.</title>
+	  
+	  <para>Use:</para>
+	  
+	  <programlisting><![ CDATA [<para><application>Sendmail</application> is the most
+  widely used Unix mail application.</para>
+
+<para><application>Sendmail</application> includes the
+  <citerefentry>
+    <refentrytitle>sendmail</refentrytitle>
+    <manvolnum>8</manvolnum>
+  </citerefentry>, &man.mailq.8;, and &man.newaliases.8;
+  programs.</para>
+
+<para>One of the command line parameters to <citerefentry>
+    <refentrytitle>sendmail</refentrytitle>
+    <manvolnum>8</manvolnum>
+  </citerefentry>, <option>-bp</option>, will display the current
+  status of messages in the mail queue.  Check this on the command
+  line by running <command>sendmail -bp</command>.</para>]]></programlisting>
+
+	  <para>Appearance:</para>
+	  
+	  <para><application>Sendmail</application> is the most widely used
+	    Unix mail application.</para>
+	  
+	  <para><application>Sendmail</application> includes the
+	    <citerefentry>
+	      <refentrytitle>sendmail</refentrytitle>
+	      <manvolnum>8</manvolnum>
+	    </citerefentry>, <citerefentry>
+	      <refentrytitle>mailq</refentrytitle>
+	      <manvolnum>8</manvolnum>
+	    </citerefentry>, and <citerefentry>
+	      <refentrytitle>newaliases</refentrytitle>
+	      <manvolnum>8</manvolnum>
+	    </citerefentry> programs.</para>
+	  
+	  <para>One of the command line parameters to <citerefentry>
+	      <refentrytitle>sendmail</refentrytitle>
+	      <manvolnum>8</manvolnum>
+	    </citerefentry>, <option>-bp</option>, will display the current
+	    status of messages in the mail queue.  Check this on the command
+	    line by running <command>sendmail -bp</command>.</para>
+	</example>
+
+	<note>
+	  <para>Notice how the
+	    <literal>&amp;man.<replaceable>command</replaceable>.<replaceable>section</replaceable>;</literal> notation is easier to follow.</para>
+	</note>
+      </sect3>
+      
+      <sect3>
+	<title>Files, directories, extensions</title>
+	
+	<para>Whenever you wish to refer to the name of a file, a directory,
+	  or a file extension, use <sgmltag>filename</sgmltag>.</para>
+	  
+	<example>
+	  <title><sgmltag>filename</sgmltag></title>
+	  
+	  <para>Use:</para>
+	  
+	  <programlisting><![ CDATA [<para>The SGML source for the Handbook in English can be
+  found in <filename>/usr/doc/en/handbook/</filename>.  The first
+  file is called <filename>handbook.sgml</filename> in that
+  directory.  You should also see a <filename>Makefile</filename>
+  and a number of files with a <filename>.ent</filename>
+  extension.</para>]]></programlisting>
+
+	  <para>Appearance:</para>
+	  
+	  <para>The SGML source for the Handbook in English can be found in
+	    <filename>/usr/doc/en/handbook/</filename>.  The first file is
+	    called <filename>handbook.sgml</filename> in that directory.  You
+	    should also see a <filename>Makefile</filename> and a number of
+	    files with a <filename>.ent</filename> extension.</para>
+	</example>
+      </sect3>
+      
+      <sect3>
+        <title>The name of ports</title>
+	
+	<note>
+	  <title>FreeBSD extension</title>
+	  
+	  <para>These elements are part of the FreeBSD extension to DocBook,
+	    and do not exist in the original DocBook DTD.</para>
+	</note>
+	
+        <para>You might need to include the name of a program from the
+          FreeBSD Ports Collection in the documentation.  Use the
+          <sgmltag>filename</sgmltag> tag with the <literal>role</literal>
+          attribute set to <literal>package</literal> to identify these.
+          Since ports
+          can be installed in any number of locations, only include
+          the category and the port name; do not include
+          <filename>/usr/ports</filename>.</para>
+
+        <example>
+          <title><sgmltag>filename</sgmltag> tag with
+            <literal>package</literal> role</title>
+
+          <para>Use:</para>
+
+          <programlisting><![ CDATA [<para>Install the <filename role="package">net/ethereal</filename> port to view network traffic.</para>]]></programlisting>
+
+          <para>Appearance:</para>
+	  
+          <para>Install the <filename role="package">net/ethereal</filename>
+            port to view network traffic.</para>
+        </example>
+      </sect3>
+
+      <sect3>
+	<title>Devices</title>
+	
+	<note>
+	  <title>FreeBSD extension</title>
+	  
+	  <para>These elements are part of the FreeBSD extension to DocBook,
+	    and do not exist in the original DocBook DTD.</para>
+	</note>
+	
+	<para>When referring to devices you have two choices.  You can either
+	  refer to the device as it appears in <filename>/dev</filename>, or
+	  you can use the name of the device as it appears in the kernel.  For
+	  this latter course, use <sgmltag>devicename</sgmltag>.</para>
+	  
+	<para>Sometimes you will not have a choice.  Some devices, such as
+	  networking cards, do not have entries in <filename>/dev</filename>,
+	  or the entries are markedly different from those entries.</para>
+	  
+	<example>
+	  <title><sgmltag>devicename</sgmltag></title>
+	  
+	  <para>Use:</para>
+	  
+	  <programlisting><![ CDATA [<para><devicename>sio</devicename> is used for serial
+  communication in FreeBSD.  <devicename>sio</devicename> manifests
+  through a number of entries in <filename>/dev</filename>, including
+  <filename>/dev/ttyd0</filename> and <filename>/dev/cuaa0</filename>.</para>
+
+<para>By contrast, the networking devices, such as
+  <devicename>ed0</devicename> do not appear in <filename>/dev</filename>.</para>
+
+<para>In MS-DOS, the first floppy drive is referred to as
+  <devicename>a:</devicename>.  In FreeBSD it is
+  <filename>/dev/fd0</filename>.</para>]]></programlisting>
+
+	  <para>Appearance:</para>
+	    
+	  <para><devicename>sio</devicename> is used for serial communication
+	    in FreeBSD.  <devicename>sio</devicename> manifests through a
+	    number of entries in <filename>/dev</filename>, including
+	    <filename>/dev/ttyd0</filename> and
+	    <filename>/dev/cuaa0</filename>.</para>
+	  
+	  <para>By contrast, the networking devices, such as
+	    <devicename>ed0</devicename> do not appear in
+	    <filename>/dev</filename>.</para>
+	    
+	  <para>In MS-DOS, the first floppy drive is referred to as
+	    <devicename>a:</devicename>.  In FreeBSD it is
+	    <filename>/dev/fd0</filename>.</para>	  
+	</example>
+      </sect3>
+	
+      <sect3>
+	<title>Hosts, domains, IP addresses, and so forth</title>
+	
+	<note>
+	  <title>FreeBSD extension</title>
+	  
+	  <para>These elements are part of the FreeBSD extension to DocBook,
+	    and do not exist in the original DocBook DTD.</para>
+	</note>
+	
+	<para>You can markup identification information for networked
+	  computers (hosts) in several ways, depending on the nature of the
+	  information.  All of them use <sgmltag>hostid</sgmltag> as the
+	  element, with the <literal>role</literal> attribute selecting the
+	  type of the marked up information.</para>
+	  
+	<variablelist>
+	  <varlistentry>
+	    <term>No role attribute, or
+	      <literal>role="hostname"</literal></term>
+	    
+	    <listitem>
+	      <para>With no role attribute (i.e.,
+		<sgmltag>hostid</sgmltag>...<sgmltag>/hostid</sgmltag>) the
+		marked up information is the simple hostname, such as
+		<literal>freefall</literal> or <literal>wcarchive</literal>.
+		You can explicitly specify this with
+		<literal>role="hostname"</literal>.</para>
+	    </listitem>
+	  </varlistentry>
+	    
+	  <varlistentry>
+	    <term><literal>role="domainname"</literal></term>
+	    
+	    <listitem>
+	      <para>The text is a domain name, such as
+		<literal>FreeBSD.org</literal> or
+		<literal>ngo.org.uk</literal>.  There is no hostname
+		component.</para>
+	    </listitem>
+	  </varlistentry>
+	  
+	  <varlistentry>
+	    <term><literal>role="fqdn"</literal></term>
+	    
+	    <listitem>
+	      <para>The text is a Fully Qualified Domain Name, with both
+		hostname and domain name parts.</para>
+	    </listitem>
+	  </varlistentry>
+
+	  <varlistentry>
+	    <term><literal>role="ipaddr"</literal></term>
+	    
+	    <listitem>
+	      <para>The text is an IP address, probably expressed as a dotted
+		quad.</para>
+	    </listitem>
+	  </varlistentry>
+
+          <varlistentry>
+            <term><literal>role="ip6addr"</literal></term>
+
+            <listitem>
+              <para>The text is an IPv6 address.</para>
+            </listitem>
+          </varlistentry>
+	  
+	  <varlistentry>
+	    <term><literal>role="netmask"</literal></term>
+	    
+	    <listitem>
+	      <para>The text is a network mask, which might be expressed as a
+		dotted quad, a hexadecimal string, or as a
+		<literal>/</literal> followed by a number.</para>
+	    </listitem>
+	  </varlistentry>
+	  
+	  <varlistentry>
+	    <term><literal>role="mac"</literal></term>
+	    
+	    <listitem>
+	      <para>The text is an Ethernet MAC address, expressed as a series
+		of 2 digit hexadecimal numbers separated by colons.</para>
+	    </listitem>
+	  </varlistentry>
+	</variablelist>
+	  
+	<example>
+	  <title><sgmltag>hostid</sgmltag> and roles</title>
+	    
+	  <para>Use:</para>
+	    
+	  <programlisting><![ CDATA [<para>The local machine can always be referred to by the
+  name <hostid>localhost</hostid>, which will have the IP address
+  <hostid role="ipaddr">127.0.0.1</hostid>.</para>
+
+<para>The <hostid role="domainname">FreeBSD.org</hostid> domain
+  contains a number of different hosts, including
+  <hostid role="fqdn">freefall.FreeBSD.org</hostid> and
+  <hostid role="fqdn">bento.FreeBSD.org</hostid>.</para>
+
+<para>When adding an IP alias to an interface (using
+  <command>ifconfig</command>) <emphasis>always</emphasis> use a
+  netmask of <hostid role="netmask">255.255.255.255</hostid>
+  (which can also be expressed as <hostid
+    role="netmask">0xffffffff</hostid>.</para>
+
+<para>The MAC address uniquely identifies every network card
+  in existence.  A typical MAC address looks like <hostid
+    role="mac">08:00:20:87:ef:d0</hostid>.</para>]]></programlisting>
+
+	  <para>Appearance:</para>
+	  
+	  <para>The local machine can always be referred to by the name
+	    <hostid>localhost</hostid>, which will have the IP address <hostid
+	      role="ipaddr">127.0.0.1</hostid>.</para>
+
+	  <para>The <hostid role="domainname">FreeBSD.org</hostid> domain
+	    contains a number of different hosts, including <hostid
+	      role="fqdn">freefall.FreeBSD.org</hostid> and <hostid
+	      role="fqdn">bento.FreeBSD.org</hostid>.</para>
+
+	  <para>When adding an IP alias to an interface (using
+	    <command>ifconfig</command>) <emphasis>always</emphasis> use a
+	    netmask of <hostid role="netmask">255.255.255.255</hostid> (which
+	    can also be expressed as <hostid
+	      role="netmask">0xffffffff</hostid>.</para>
+
+	  <para>The MAC address uniquely identifies every network card in
+	    existence.  A typical MAC address looks like <hostid
+	      role="mac">08:00:20:87:ef:d0</hostid>.</para>	  
+	</example>
+      </sect3>
+      
+      <sect3>
+	<title>Usernames</title>
+	
+	<note>
+	  <title>FreeBSD extension</title>
+	  
+	  <para>These elements are part of the FreeBSD extension to DocBook,
+	    and do not exist in the original DocBook DTD.</para>
+	</note>
+	
+	<para>When you need to refer to a specific username, such as
+	  <literal>root</literal> or <literal>bin</literal>, use
+	  <sgmltag>username</sgmltag>.</para>
+	
+	<example>
+	  <title><sgmltag>username</sgmltag></title>
+	  
+	  <para>Use:</para>
+	  
+	  <programlisting><![ CDATA [<para>To carry out most system administration functions you
+  will need to be <username>root</username>.</para>]]></programlisting>
+
+	  <para>Appearance:</para>
+	  
+	  <para>To carry out most system administration functions you will
+	    need to be <username>root</username>.</para>
+	</example>
+      </sect3>
+      
+      <sect3>
+	<title>Describing <filename>Makefile</filename>s</title>
+	
+	<note>
+	  <title>FreeBSD extension</title>
+	  
+	  <para>These elements are part of the FreeBSD extension to DocBook,
+	    and do not exist in the original DocBook DTD.</para>
+	</note>
+	
+	<para>Two elements exist to describe parts of
+	  <filename>Makefile</filename>s, <sgmltag>maketarget</sgmltag> and
+	  <sgmltag>makevar</sgmltag>.</para>
+	  
+	<para><sgmltag>maketarget</sgmltag> identifies a build target exported
+	  by a <filename>Makefile</filename> that can be given as a parameter
+	  to <command>make</command>.  <sgmltag>makevar</sgmltag> identifies a
+	  variable that can be set (in the environment, on the
+	  <command>make</command> command line, or within the
+	  <filename>Makefile</filename>) to influence the process.</para>
+
+	<example>
+	  <title><sgmltag>maketarget</sgmltag> and
+	    <sgmltag>makevar</sgmltag></title>
+	  
+	  <para>Use:</para>
+	  
+	  <programlisting><![ CDATA [<para>Two common targets in a <filename>Makefile</filename>
+  are <maketarget>all</maketarget> and <maketarget>clean</maketarget>.</para>
+
+<para>Typically, invoking <maketarget>all</maketarget> will rebuild the
+  application, and invoking <maketarget>clean</maketarget> will remove
+  the temporary files (<filename>.o</filename> for example) created by
+  the build process.</para>
+
+<para><maketarget>clean</maketarget> may be controlled by a number of
+  variables, including <makevar>CLOBBER</makevar> and
+  <makevar>RECURSE</makevar>.</para>]]></programlisting>
+
+	  <para>Appearance:</para>
+	  
+	  <para>Two common targets in a <filename>Makefile</filename> are
+	    <maketarget>all</maketarget> and
+	    <maketarget>clean</maketarget>.</para>
+	    
+	  <para>Typically, invoking <maketarget>all</maketarget> will rebuild
+	    the application, and invoking <maketarget>clean</maketarget> will
+	    remove the temporary files (<filename>.o</filename> for example)
+	    created by the build process.</para>
+	    
+	  <para><maketarget>clean</maketarget> may be controlled by a number
+	    of variables, including <makevar>CLOBBER</makevar> and
+	    <makevar>RECURSE</makevar>.</para>	  
+	</example>
+      </sect3>
+      
+      <sect3>
+	<title>Literal text</title>
+	
+	<para>You will often need to include <quote>literal</quote> text in the
+	  Handbook.  This is text that is excerpted from another file, or
+	  which should be copied from the Handbook into another file
+	  verbatim.</para>
+
+	<para>Some of the time, <sgmltag>programlisting</sgmltag> will be
+	  sufficient to denote this text.  <sgmltag>programlisting</sgmltag>
+	  is not always appropriate, particularly when you want to include a
+	  portion of a file <quote>in-line</quote> with the rest of the
+	  paragraph.</para>
+
+	<para>On these occasions, use <sgmltag>literal</sgmltag>.</para>
+	
+	<example>
+	  <title><sgmltag>literal</sgmltag></title>
+	  
+	  <para>Use:</para>
+	  
+	  <programlisting><![ CDATA [<para>The <literal>maxusers 10</literal> line in the kernel
+  configuration file determines the size of many system tables, and is
+  a rough guide to how many simultaneous logins the system will
+  support.</para>]]></programlisting>
+
+	  <para>Appearance:</para>
+	  
+	  <para>The <literal>maxusers 10</literal> line in the kernel
+	    configuration file determines the size of many system tables, and
+	    is a rough guide to how many simultaneous logins the system will
+	    support.</para>
+	</example>
+      </sect3>
+	
+      <sect3>
+	<title>Showing items that the user <emphasis>must</emphasis> fill
+	  in</title>
+	
+	<para>There will often be times when you want to show the user what to
+	  do, or refer to a file, or command line, or similar, where the user
+	  cannot simply copy the examples that you provide, but must instead
+	  include some information themselves.</para>
+	
+	<para><sgmltag>replaceable</sgmltag> is designed for this eventuality.
+	  Use it <emphasis>inside</emphasis> other elements to indicate parts
+	  of that element's content that the user must replace.</para>
+	
+	<example>
+	  <title><sgmltag>replaceable</sgmltag></title>
+	  
+	  <para>Use:</para>
+	  
+	  <programlisting><![ CDATA [<informalexample>
+  <screen>&prompt.user; <userinput>man <replaceable>command</replaceable></userinput></screen>
+</informalexample>]]></programlisting>
+
+	  <para>Appearance:</para>
+	  
+	  <informalexample>
+	    <screen>&prompt.user; <userinput>man <replaceable>command</replaceable></userinput></screen>
+	  </informalexample>
+	  
+	  <para><sgmltag>replaceable</sgmltag> can be used in many different
+	    elements, including <sgmltag>literal</sgmltag>.  This example also
+	    shows that <sgmltag>replaceable</sgmltag> should only be wrapped
+	    around the content that the user <emphasis>is</emphasis> meant to
+	    provide.  The other content should be left alone.</para>
+	    
+	  <para>Use:</para>
+	    
+	  <programlisting><![ CDATA [<para>The <literal>maxusers <replaceable>n</replaceable></literal>
+  line in the kernel configuration file determines the size of many system
+  tables, and is a rough guide to how many simultaneous logins the system will
+  support.</para>
+
+<para>For a desktop workstation, <literal>32</literal> is a good value
+  for <replaceable>n</replaceable>.</para>]]></programlisting>
+
+	  <para>Appearance:</para>
+	  
+	  <para>The <literal>maxusers <replaceable>n</replaceable></literal>
+	    line in the kernel configuration file determines the size of many
+	    system tables, and is a rough guide to how many simultaneous
+	    logins the system will support.</para>
+
+	  <para>For a desktop workstation, <literal>32</literal> is a good
+	    value for <replaceable>n</replaceable>.</para>	  
+	</example>
+      </sect3>
+
+      <sect3>
+        <title>Quoting system errors</title>
+
+        <para>You might want to show errors generated by FreeBSD.
+          Mark these with <sgmltag>errorname</sgmltag>.  This
+          indicates the exact error that appears.</para>
+
+        <example>
+          <title><sgmltag>errorname</sgmltag></title>
+
+          <para>Use:</para>
+
+	  <programlisting><![ CDATA [ 
+<screen><errorname>Panic: cannot mount root</errorname></screen> ]]>
+</programlisting>
+
+
+          <para>Appearance:</para>
+
+          <informalexample>
+            <screen><errorname>Panic: cannot mount root</errorname></screen>
+          </informalexample>
+        </example>
+      </sect3>
+    </sect2>
+
+    <sect2>
+      <title>Images</title>
+
+      <important>
+	<para>Image support in the documentation is currently extremely
+	  experimental.  I think the mechanisms described here are unlikely to
+	  change, but that is not guaranteed.</para>
+
+	<para>You will also need to install the
+	  <filename role="package">graphics/ImageMagick</filename> port, which is used to
+	  convert between the different image formats.  This is a big port,
+	  and most of it is not required.  However, while we are working on the
+	  <filename>Makefile</filename>s and other infrastructure it makes
+	  things easier.  This port is <emphasis>not</emphasis> in the
+	  <filename role="package">textproc/docproj</filename> meta port, you must install it
+	  by hand.</para>
+
+	<para>The best example of what follows in practice is the
+	  <filename>doc/en_US.ISO8859-1/articles/vm-design/</filename> document.
+	  If you are unsure of the description that follows, take a look at the
+	  files in that directory to see how everything hangs together.
+	  Experiment with creating different formatted versions of the
+	  document to see how the image markup appears in the formatted
+	  output.</para>
+      </important>
+
+      <sect3>
+	<title>Image formats</title>
+
+	<para>We currently support two formats for images.  The format you
+	  should use will depend on the nature of your image.</para>
+
+	<para>For images that are primarily vector based, such as network
+	  diagrams, time lines, and similar, use Encapsulated Postscript, and
+	  make sure that your images have the <filename>.eps</filename>
+	  extension.</para>
+
+	<para>For bitmaps, such as screen captures, use the Portable Network
+	  Graphic format, and make sure that your images have the
+	  <filename>.png</filename> extension.</para>
+
+	<para>These are the <emphasis>only</emphasis> formats in which images
+	  should be committed to the CVS repository.</para>
+
+	<para>Use the right format for the right image.  It is to be expected
+	  that your documentation will have a mix of EPS and PNG images.  The
+	  <filename>Makefile</filename>s ensure that the correct format image
+	  is chosen depending on the output format that you use for your
+	  documentation.  <emphasis>Do not commit the same image to the
+	    repository in two different formats</emphasis>.</para>
+
+	<important>
+	  <para>It is anticipated that the Documentation Project will switch to
+	    using the Scalable Vector Graphic (SVG) format for vector images.
+	    However, the current state of SVG capable editing tools makes this
+	    impractical.</para>
+	</important>
+      </sect3>
+
+      <sect3>
+	<title>Markup</title>
+
+	<para>The markup for an image is relatively simple.  First, markup a
+	  <sgmltag>mediaobject</sgmltag>.  The <sgmltag>mediaobject</sgmltag>
+	  can contain other, more specific objects.  We are concerned with
+	  two, the <sgmltag>imageobject</sgmltag> and the
+	  <sgmltag>textobject</sgmltag>.</para>
+
+	<para>You should include one <sgmltag>imageobject</sgmltag>, and two
+	  <sgmltag>textobject</sgmltag> elements.  The
+	  <sgmltag>imageobject</sgmltag> will point to the name of the image
+	  file that will be used (without the extension).  The
+	  <sgmltag>textobject</sgmltag> elements contain information that will
+	  be presented to the user as well as, or instead of, the
+	  image.</para>
+
+	<para>There are two circumstances where this can happen.</para>
+
+	<itemizedlist>
+	  <listitem>
+	    <para>When the reader is viewing the documentation in HTML.  In
+	      this case, each image will need to have associated alternate
+	      text to show the user, typically whilst the image is loading, or
+	      if they hover the mouse pointer over the image.</para>
+	  </listitem>
+
+	  <listitem>
+	    <para>When the reader is viewing the documentation in plain text.
+	      In this case, each image should have an ASCII art equivalent to
+	      show the user.</para>
+	  </listitem>
+	</itemizedlist>
+
+	<para>An example will probably make things easier to understand.
+	  Suppose you have an image, called <filename>fig1</filename>, that
+	  you want to include in the document.  This image is of a rectangle
+	  with an A inside it.  The markup for this would be as
+	  follows.</para>
+
+	<programlisting>&lt;mediaobject>
+  &lt;imageobject>
+    &lt;imagedata fileref="fig1"> <co id="co-image-ext">
+  &lt;/imageobject>
+
+  &lt;textobject>
+    &lt;literallayout class="monospaced">+---------------+ <co id="co-image-literal">
+|       A       |
++---------------+&lt;/literallayout>
+  &lt;/textobject>
+
+  &lt;textobject>
+    &lt;phrase>A picture&lt;/phrase> <co id="co-image-phrase">
+  &lt;/textobject>
+&lt;/mediaobject></programlisting>
+
+	<calloutlist>
+	  <callout arearefs="co-image-ext">
+	    <para>Include an <sgmltag>imagedata</sgmltag> element inside the
+	      <sgmltag>imageobject</sgmltag> element.  The
+	      <literal>fileref</literal> attribute should contain the filename
+	      of the image to include, without the extension.  The stylesheets
+	      will work out which extension should be added to the filename
+	      automatically.</para>
+	  </callout>
+
+	  <callout arearefs="co-image-literal">
+	    <para>The first <sgmltag>textobject</sgmltag> should contain a
+	      <sgmltag>literallayout</sgmltag> element, where the
+	      <literal>class</literal> attribute is set to
+	      <literal>monospaced</literal>.  This is your opportunity to
+	      demonstrate your ASCII art skills.  This content will be used if
+	      the document is converted to plain text.</para>
+
+	    <para>Notice how the first and last lines of the content of the
+	      <sgmltag>literallayout</sgmltag> element butt up next to the
+	      element's tags.  This ensures no extraneous white space is
+	      included.</para>
+	  </callout>
+
+	  <callout arearefs="co-image-phrase">
+	    <para>The second <sgmltag>textobject</sgmltag> should contain a
+	      single <sgmltag>phrase</sgmltag> element.  The contents of this
+	      will become the <literal>alt</literal> attribute for the image
+	      when this document is converted to HTML.</para>
+	  </callout>
+	</calloutlist>
+      </sect3>
+
+      <sect3>
+	<title><filename>Makefile</filename> entries</title>
+
+	<para>Your images must be listed in the
+	  <filename>Makefile</filename> in the <makevar>IMAGES</makevar>
+	  variable.  This variable should contain the name of all your
+	  <emphasis>source</emphasis> images.  For example, if you have
+	  created three figures, <filename>fig1.eps</filename>,
+	  <filename>fig2.png</filename>, <filename>fig3.png</filename>, then
+	  your <filename>Makefile</filename> should have lines like this in
+	  it.</para>
+
+	<programlisting>&hellip;
+IMAGES= fig1.eps fig2.png fig3.png
+&hellip;</programlisting>
+
+	<para>or</para>
+
+	<programlisting>&hellip;
+IMAGES=  fig1.eps
+IMAGES+= fig2.png
+IMAGES+= fig3.png
+&hellip;</programlisting>
+
+	<para>Again, the <filename>Makefile</filename> will work out the
+	  complete list of images it needs to build your source document, you
+	  only need to list the image files <emphasis>you</emphasis>
+	  provided.</para>
+      </sect3>
+
+      <sect3>
+	<title>Images and chapters in subdirectories</title>
+
+	<para>You must be careful when you separate your documentation into
+	  smaller files (see <xref linkend="sgml-primer-include-using-gen-entities">) in
+	  different directories.</para>
+	  
+	<para>Suppose you have a book with three chapters, and the chapters
+	  are stored in their own directories, called
+	  <filename>chapter1/chapter.sgml</filename>,
+	  <filename>chapter2/chapter.sgml</filename>, and
+	  <filename>chapter3/chapter.sgml</filename>.  If each chapter has
+	  images associated with it, I suggest you place those images in each
+	  chapter's subdirectory (<filename>chapter1/</filename>,
+	  <filename>chapter2/</filename>, and
+	  <filename>chapter3/</filename>).</para>
+
+	<para>However, if you do this you must include the directory names in
+	  the <makevar>IMAGES</makevar> variable in the
+	  <filename>Makefile</filename>, <emphasis>and</emphasis> you must
+	  include the directory name in the <sgmltag>imagedata</sgmltag>
+	  element in your document.</para>
+
+	<para>For example, if you have <filename>chapter1/fig1.png</filename>,
+	  then <filename>chapter1/chapter.sgml</filename> should
+	  contain:</para>
+
+	<programlisting>&lt;mediaobject>
+  &lt;imageobject>
+    &lt;imagedata fileref="chapter1/fig1"> <co id="co-image-dir">
+  &lt;/imageobject>
+
+  &hellip;
+
+&lt;/mediaobject></programlisting>
+	
+	<calloutlist>
+	  <callout arearefs="co-image-dir">
+	    <para>The directory name must be included in the
+	      <literal>fileref</literal> attribute.</para>
+	  </callout>
+	</calloutlist>
+
+	<para>The <filename>Makefile</filename> must contain:</para>
+
+	<programlisting>&hellip;
+IMAGES=  chapter1/fig1.png
+&hellip;</programlisting>
+
+	<para>Then everything should just work.</para>
+      </sect3>
+    </sect2>
+    
+    <sect2>
+      <title>Links</title>
+
+      <note>
+	<para>Links are also in-line elements.</para>
+      </note>
+
+      <sect3>
+	<title>Linking to other parts of the same document</title>
+
+	<para>Linking within the same document requires you to specify
+	  where you are linking from (i.e., the text the user will click, or
+	  otherwise indicate, as the source of the link) and where you are
+	  linking to (the link's destination).</para>
+
+	<para>Each element within DocBook has an attribute called
+	  <literal>id</literal>.  You can place text in this attribute to
+	  uniquely name the element it is attached to.</para>
+
+	  <para>This value will be used when you specify the link
+	  source.</para>
+
+	<para>Normally, you will only be linking to chapters or sections, so
+	  you would add the <literal>id</literal> attribute to these
+	  elements.</para>
+
+	<example>
+	  <title><literal>id on chapters and sections</literal></title>
+
+	  <programlisting><![ CDATA [<chapter id="chapter1">
+  <title>Introduction</title>
+
+  <para>This is the introduction.  It contains a subsection,
+    which is identified as well.</para>
+
+  <sect1 id="chapter1-sect1">
+    <title>Sub-sect 1</title>
+
+    <para>This is the subsection.</para>
+  </sect1>
+</chapter>]]></programlisting>
+	</example>
+	
+	<para>Obviously, you should use more descriptive values.  The values
+	  must be unique within the document (i.e., not just the file, but the
+	  document the file might be included in as well).  Notice how the
+	  <literal>id</literal> for the subsection is constructed by appending
+	  text to the <literal>id</literal> of the chapter.  This helps to
+	  ensure that they are unique.</para>
+
+	<para>If you want to allow the user to jump into a specific portion of
+	  the document (possibly in the middle of a paragraph or an example),
+	  use <sgmltag>anchor</sgmltag>.  This element has no content, but
+	  takes an <literal>id</literal> attribute.</para>
+
+	<example>
+	  <title><sgmltag>anchor</sgmltag></title>
+
+	  <programlisting><![ CDATA [<para>This paragraph has an embedded
+  <anchor id="para1">link target in it.  It will not show up in
+  the document.</para>]]></programlisting>
+	</example>
+	
+	<para>When you want to provide the user with a link they can activate
+	  (probably by clicking) to go to a section of the document that has
+	  an <literal>id</literal> attribute, you can use either
+	  <sgmltag>xref</sgmltag> or <sgmltag>link</sgmltag>.</para>
+
+	<para>Both of these elements have a <literal>linkend</literal>
+	  attribute.  The value of this attribute should be the value that you
+	  have used in a <literal>id</literal> attribute (it does not matter
+	  if that value has not yet occurred in your document; this will work
+	  for forward links as well as backward links).</para>
+	
+	<para>If you use <sgmltag>xref</sgmltag> then you have no control over
+	  the text of the link.  It will be generated for you.</para>
+	
+	<example>
+	  <title>Using <sgmltag>xref</sgmltag></title>
+
+	  <para>Assume that this fragment appears somewhere in a document that
+	    includes the <literal>id</literal> example:</para>
+	  
+	  <programlisting><![ CDATA [<para>More information can be found
+  in <xref linkend="chapter1">.</para>
+
+<para>More specific information can be found
+  in <xref linkend="chapter1-sect1">.</para>]]></programlisting>
+
+	  <para>The text of the link will be generated automatically, and will
+	    look like (<emphasis>emphasized</emphasis> text indicates the text
+	    that will be the link):</para>
+
+	  <blockquote>
+	    <para>More information can be found in <emphasis>Chapter
+		One</emphasis>.</para>
+
+	    <para>More specific information can be found in <emphasis>the
+		section called Sub-sect 1</emphasis>.</para>
+	  </blockquote>
+	</example>
+	
+	<para>Notice how the text from the link is derived from the section
+	  title or the chapter number.</para>
+
+	<note>
+	  <para>This means that you <emphasis>cannot</emphasis> use
+	    <sgmltag>xref</sgmltag> to link to an <literal>id</literal>
+	    attribute on an <sgmltag>anchor</sgmltag> element.  The
+	    <sgmltag>anchor</sgmltag> has no content, so the
+	    <sgmltag>xref</sgmltag> cannot generate the text for the
+	    link.</para>
+	</note>
+	
+	<para>If you want to control the text of the link then use
+	  <sgmltag>link</sgmltag>.  This element wraps content, and the
+	  content will be used for the link.</para>
+
+	<example>
+	  <title>Using <sgmltag>link</sgmltag></title>
+
+	  <para>Assume that this fragment appears somewhere in a document that
+	    includes the <literal>id</literal> example.</para>
+
+	  <programlisting><![ CDATA [<para>More information can be found in
+  <link linkend="chapter1">the first chapter</link>.</para>
+
+<para>More specific information can be found in
+  <link linkend="chapter1-sect1">this</link> section.</para>]]></programlisting>
+	  
+	  <para>This will generate the following
+	    (<emphasis>emphasized</emphasis> text indicates the text that will
+	    be the link):</para>
+	  
+	  <blockquote>
+	    <para>More information can be found in <emphasis>the first
+		chapter</emphasis>.</para>
+	    
+	    <para>More specific information can be found in
+	      <emphasis>this</emphasis> section.</para>
+	  </blockquote>
+	</example>
+	
+	<note>
+	  <para>That last one is a bad example.  Never use words like
+	    <quote>this</quote> or <quote>here</quote> as the source for the
+	    link.  The reader will need to hunt around the surrounding context
+	    to see where the link is actually taking them.</para>
+	</note>
+
+	<note>
+	  <para>You <emphasis>can</emphasis> use <sgmltag>link</sgmltag> to
+	    include a link to an <literal>id</literal> on an
+	    <sgmltag>anchor</sgmltag> element, since the
+	    <sgmltag>link</sgmltag> content defines the text that will be used
+	    for the link.</para>
+	</note>
+      </sect3>
+
+      <sect3>
+	<title>Linking to documents on the WWW</title>
+
+	<para>Linking to external documents is much simpler, as long as you
+	  know the URL of the document you want to link to.  Use
+	  <sgmltag>ulink</sgmltag>.  The <literal>url</literal> attribute is
+	  the URL of the page that the link points to, and the content of the
+	  element is the text that will be displayed for the user to
+	  activate.</para>
+
+	<example>
+	  <title><sgmltag>ulink</sgmltag></title>
+
+	  <para>Use:</para>
+
+	  <programlisting><![ CDATA [<para>Of course, you could stop reading this document and
+  go to the <ulink url="&url.base;/index.html">FreeBSD
+  home page</ulink> instead.</para>]]></programlisting>
+
+	  <para>Appearance:</para>
+
+	  <para>Of course, you could stop reading this document and go to the
+	    <ulink url="&url.base;/index.html">FreeBSD home page</ulink>
+	    instead.</para>
+	</example>
+      </sect3>
+    </sect2>
+  </sect1>
+</chapter>
+
+
+<!--
+     Local Variables:
+     mode: sgml
+     sgml-declaration: "../chapter.decl"
+     sgml-indent-data: t
+     sgml-omittag: nil
+     sgml-always-quote-attributes: t
+     sgml-parent-document: ("../book.sgml" "part" "chapter")
+     End:
+-->
+
diff --git a/zh_TW.Big5/books/fdp-primer/sgml-primer/chapter.sgml b/zh_TW.Big5/books/fdp-primer/sgml-primer/chapter.sgml
new file mode 100644
index 0000000000..c90154b62a
--- /dev/null
+++ b/zh_TW.Big5/books/fdp-primer/sgml-primer/chapter.sgml
@@ -0,0 +1,1591 @@
+<!-- Copyright (c) 1998, 1999 Nik Clayton, All rights reserved.
+
+     Redistribution and use in source (SGML DocBook) and 'compiled' forms
+     (SGML, HTML, PDF, PostScript, RTF and so forth) with or without
+     modification, are permitted provided that the following conditions
+     are met:
+
+      1. Redistributions of source code (SGML DocBook) must retain the above
+         copyright notice, this list of conditions and the following
+         disclaimer as the first lines of this file unmodified.
+
+      2. Redistributions in compiled form (transformed to other DTDs,
+         converted to PDF, PostScript, RTF and other formats) must reproduce
+         the above copyright notice, this list of conditions and the
+         following disclaimer in the documentation and/or other materials
+         provided with the distribution.
+
+     THIS DOCUMENTATION IS PROVIDED BY NIK CLAYTON "AS IS" AND ANY EXPRESS OR
+     IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+     OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+     DISCLAIMED. IN NO EVENT SHALL NIK CLAYTON BE LIABLE FOR ANY DIRECT,
+     INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+     (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+     SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+     HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+     STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
+     ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
+     POSSIBILITY OF SUCH DAMAGE.
+
+     $FreeBSD$
+-->
+
+<chapter id="sgml-primer">
+  <title>SGML Primer</title>
+
+  <para>The majority of FDP documentation is written in applications of
+    SGML.  This chapter explains exactly what that means, how to read
+    and understand the source to the documentation, and the sort of SGML
+    tricks you will see used in the documentation.</para>
+
+  <para>Portions of this section were inspired by Mark Galassi's <ulink
+      url="http://nis-www.lanl.gov/~rosalia/mydocs/docbook-intro/docbook-intro.html">Get Going With DocBook</ulink>.</para>
+  
+  <sect1 id="sgml-primer-overview">
+    <title>Overview</title>
+
+    <para>Way back when, electronic text was simple to deal with.  Admittedly, 
+      you had to know which character set your document was written in (ASCII, 
+      EBCDIC, or one of a number of others) but that was about it.  Text was
+      text, and what you saw really was what you got.  No frills, no
+      formatting, no intelligence.</para>
+
+    <para>Inevitably, this was not enough.  Once you have text in a
+      machine-usable format, you expect machines to be able to use it and
+      manipulate it intelligently.  You would like to indicate that certain
+      phrases should be emphasized, or added to a glossary, or be hyperlinks.
+      You might want filenames to be shown in a <quote>typewriter</quote> style 
+      font for viewing on screen, but as <quote>italics</quote> when printed,
+      or any of a myriad of other options for presentation.</para>
+
+    <para>It was once hoped that Artificial Intelligence (AI) would make this
+      easy.  Your computer would read in the document and automatically
+      identify key phrases, filenames, text that the reader should type in,
+      examples, and more.  Unfortunately, real life has not happened quite
+      like that, and our computers require some assistance before they can
+      meaningfully process our text.</para>
+
+    <para>More precisely, they need help identifying what is what.  You or I
+      can look at
+
+      <blockquote>
+	<para>To remove <filename>/tmp/foo</filename> use &man.rm.1;.</para>
+
+	<screen>&prompt.user; <userinput>rm /tmp/foo</userinput></screen>
+      </blockquote>
+
+      and easily see which parts are filenames, which are commands to be typed
+      in, which parts are references to manual pages, and so on.  But the
+      computer processing the document cannot.  For this we need
+      markup.</para>
+    
+    <para><quote>Markup</quote> is commonly used to describe <quote>adding
+      value</quote> or <quote>increasing cost</quote>.  The term takes on both
+      these meanings when applied to text.  Markup is additional text included 
+      in the document, distinguished from the document's content in some way,
+      so that programs that process the document can read the markup and use
+      it when making decisions about the document.  Editors can hide the
+      markup from the user, so the user is not distracted by it.</para>
+
+    <para>The extra information stored in the markup <emphasis>adds
+      value</emphasis> to the document.  Adding the markup to the document
+      must typically be done by a person&mdash;after all, if computers could
+      recognize the text sufficiently well to add the markup then there would
+      be no need to add it in the first place.  This <emphasis>increases the
+      cost</emphasis> (i.e., the effort required) to create the
+      document.</para>
+
+    <para>The previous example is actually represented in this document like
+      this:</para>
+
+    <programlisting><![ CDATA [
+<para>To remove <filename>/tmp/foo</filename> use &man.rm.1;.</para>
+
+<screen>&prompt.user; <userinput>rm /tmp/foo</userinput></screen>]]></programlisting>
+
+    <para>As you can see, the markup is clearly separate from the
+      content.</para>
+
+    <para>Obviously, if you are going to use markup you need to define what
+      your markup means, and how it should be interpreted.  You will need a
+      markup language that you can follow when marking up your
+      documents.</para>
+    
+   <para>Of course, one markup language might not be enough.  A markup
+      language for technical documentation has very different requirements
+      than a markup language that was to be used for cookery recipes.  This,
+      in turn, would be very different from a markup language used to describe
+      poetry.  What you really need is a first language that you use to write
+      these other markup languages.  A <emphasis>meta markup
+      language</emphasis>.</para>
+    
+    <para>This is exactly what the Standard Generalized Markup Language (SGML)
+      is.  Many markup languages have been written in SGML, including the two
+      most used by the FDP, HTML and DocBook.</para>
+    
+    <para>Each language definition is more properly called a Document Type
+      Definition (DTD).  The DTD specifies the name of the elements that can
+      be used, what order they appear in (and whether some markup can be used
+      inside other markup) and related information.  A DTD is sometimes
+      referred to as an <emphasis>application</emphasis> of SGML.</para>
+
+    <para id="sgml-primer-validating">A DTD is a <emphasis>complete</emphasis>
+      specification of all the elements that are allowed to appear, the order
+      in which they should appear, which elements are mandatory, which are
+      optional, and so forth. This makes it possible to write an SGML
+      <emphasis>parser</emphasis> which reads in both the DTD and a document
+      which claims to conform to the DTD.  The parser can then confirm whether
+      or not all the elements required by the DTD are in the document in the
+      right order, and whether there are any errors in the markup.  This is
+      normally referred to as <quote>validating  the document</quote>.</para>
+
+    <note>
+      <para>This processing simply confirms that the choice of elements, their 
+	ordering, and so on, conforms to that listed in the DTD.  It does
+	<emphasis>not</emphasis> check that you have used
+	<emphasis>appropriate</emphasis> markup for the content.  If you
+	tried to mark up all the filenames in your document as function
+	names, the parser would not flag this as an error (assuming, of
+	course, that your DTD defines elements for filenames and functions,
+	and that they are allowed to appear in the same place).</para>
+    </note>
+    
+    <para>It is likely that most of your contributions to the Documentation
+      Project will consist of content marked up in either HTML or DocBook,
+      rather than alterations to the DTDs.  For this reason this book will
+      not touch on how to write a DTD.</para>
+  </sect1>
+  
+  <sect1 id="sgml-primer-elements">
+    <title>Elements, tags, and attributes</title>
+
+    <para>All the DTDs written in SGML share certain characteristics.  This is
+      hardly surprising, as the philosophy behind SGML will inevitably show
+      through. One of the most obvious manifestations of this philosophy is
+      that of <emphasis>content</emphasis> and
+      <emphasis>elements</emphasis>.</para>
+
+    <para>Your documentation (whether it is a single web page, or a lengthy
+      book) is considered to consist of content.  This content is then divided
+      (and further subdivided) into elements.  The purpose of adding markup is
+      to name and identify the boundaries of these elements for further
+      processing.</para>
+
+    <para>For example, consider a typical book.  At the very top level, the
+      book is itself an element.  This <quote>book</quote> element obviously
+      contains chapters, which can be considered to be elements in their own
+      right.  Each chapter will contain more elements, such as paragraphs,
+      quotations, and footnotes.  Each paragraph might contain further
+      elements, identifying content that was direct speech, or the name of a
+      character in the story.</para>
+
+    <para>You might like to think of this as <quote>chunking</quote> content.
+      At the very top level you have one chunk, the book.  Look a little
+      deeper, and you have more chunks, the individual chapters.  These are
+      chunked further into paragraphs, footnotes, character names, and so
+      on.</para>
+
+    <para>Notice how you can make this differentiation between different
+      elements of the content without resorting to any SGML terms.  It really
+      is surprisingly straightforward.  You could do this with a highlighter
+      pen and a printout of the book, using different colors to indicate
+      different chunks of content.</para>
+
+    <para>Of course, we do not have an electronic highlighter pen, so we need
+      some other way of indicating which element each piece of content belongs
+      to.  In languages written in SGML (HTML, DocBook, et al) this is done by
+      means of <emphasis>tags</emphasis>.</para>
+
+    <para>A tag is used to identify where a particular element starts, and
+      where the element ends.  <emphasis>The tag is not part of the element
+      itself</emphasis>. Because each DTD was normally written to mark up
+      specific types of information, each one will recognize different
+      elements, and will therefore have different names for the tags.</para>
+
+    <para>For an element called <replaceable>element-name</replaceable> the
+      start tag will normally look like
+      <literal>&lt;<replaceable>element-name</replaceable>&gt;</literal>.  The
+      corresponding closing tag for this element is
+      <literal>&lt;/<replaceable>element-name</replaceable>&gt;</literal>.</para>
+
+    <example>
+      <title>Using an element (start and end tags)</title>
+
+      <para>HTML has an element for indicating that the content enclosed by
+	the element is a paragraph, called <literal>p</literal>.  This
+	element has both start and end tags.</para>
+      
+      <programlisting><![ CDATA [<p>This is a paragraph.  It starts with the start tag for
+  the 'p' element, and it will end with the end tag for the 'p'
+  element.</p>
+
+<p>This is another paragraph.  But this one is much shorter.</p>]]></programlisting>	  
+    </example>
+
+    <para>Not all elements require an end tag.  Some elements have no content.
+      For example, in HTML you can indicate that you want a horizontal line to
+      appear in the document.  Obviously, this line has no content, so just
+      the start tag is required for this element.</para>
+
+    <example>
+      <title>Using an element (start tag only)</title>
+
+      <para>HTML has an element for indicating a horizontal rule, called
+	<literal>hr</literal>.  This element does not wrap content, so only
+	has a start tag.</para>
+
+      <programlisting><![ CDATA [<p>This is a paragraph.</p>
+
+<hr>
+
+<p>This is another paragraph.  A horizontal rule separates this
+  from the previous paragraph.</p>]]></programlisting>
+    </example>
+    
+    <para>If it is not obvious by now, elements can contain other elements.
+      In the book example earlier, the book element contained all the chapter
+      elements, which in turn contained all the paragraph elements, and so
+      on.</para>
+
+    <example>
+      <title>Elements within elements; <sgmltag>em</sgmltag></title>
+      
+      <programlisting><![ CDATA [<p>This is a simple <em>paragraph</em> where some
+  of the <em>words</em> have been <em>emphasized</em>.</p>]]></programlisting>
+    </example>
+    
+    <para>The DTD will specify the rules detailing which elements can contain
+      other elements, and exactly what they can contain.</para>
+
+    <important>
+      <para>People often confuse the terms tags and elements, and use the
+	terms as if they were interchangeable.  They are not.</para>
+
+      <para>An element is a conceptual part of your document.  An element has
+	a defined start and end.  The tags mark where the element starts and
+	end.</para>
+
+      <para>When this document (or anyone else knowledgeable about SGML) refers
+	to <quote>the &lt;p&gt; tag</quote> they mean the literal text
+	consisting of the three characters <literal>&lt;</literal>,
+	<literal>p</literal>, and <literal>&gt;</literal>.  But the phrase
+	<quote>the &lt;p&gt; element</quote> refers to the whole
+	element.</para>
+
+      <para>This distinction <emphasis>is</emphasis> very subtle.  But keep it 
+	in mind.</para>
+    </important>
+      
+    <para>Elements can have attributes.  An attribute has a name and a value,
+      and is used for adding extra information to the element.  This might be
+      information that indicates how the content should be rendered, or might
+      be something that uniquely identifies that occurrence of the element, or
+      it might be something else.</para>
+
+    <para>An element's attributes are written <emphasis>inside</emphasis> the
+      start tag for that element, and take the form
+      <literal><replaceable>attribute-name</replaceable>="<replaceable>attribute-value</replaceable>"</literal>.</para>
+
+    <para>In sufficiently recent versions of HTML, the <sgmltag>p</sgmltag>
+      element has an attribute called <literal>align</literal>, which suggests
+      an alignment (justification) for the paragraph to the program displaying
+      the HTML.</para>
+
+    <para>The <literal>align</literal> attribute can take one of four defined
+      values, <literal>left</literal>, <literal>center</literal>,
+      <literal>right</literal> and <literal>justify</literal>.  If the
+      attribute is not specified then the default is
+      <literal>left</literal>.</para>
+
+    <example>
+      <title>Using an element with an attribute</title>
+      
+      <programlisting><![ CDATA [<p align="left">The inclusion of the align attribute
+  on this paragraph was superfluous, since the default is left.</p>
+
+<p align="center">This may appear in the center.</p>]]></programlisting>
+    </example>
+    
+    <para>Some attributes will only take specific values, such as
+      <literal>left</literal> or <literal>justify</literal>.  Others will
+      allow you to enter anything you want.  If you need to include quotes
+      (<literal>"</literal>) within an attribute then use single quotes around
+      the attribute value.</para>
+
+    <example>
+      <title>Single quotes around attributes</title>
+      
+      <programlisting><![ CDATA [<p align='right'>I am on the right!</p>]]></programlisting>
+    </example>
+
+    <para>Sometimes you do not need to use quotes around attribute values at
+      all.  However, the rules for doing this are subtle, and it is far
+      simpler just to <emphasis>always</emphasis> quote your attribute
+      values.</para>
+
+    <para>The information on attributes, elements, and tags is stored
+      in SGML catalogs.  The various Documentation Project tools use
+      these catalog files to validate your work.  The tools in
+      <filename role="package">textproc/docproj</filename> include a variety of SGML catalog
+      files.  The FreeBSD Documentation Project includes its own set
+      of catalog files.  Your tools need to know about both sorts of
+      catalog files.</para>
+
+    <sect2>
+      <title>For you to do&hellip;</title>
+
+      <para>In order to run the examples in this document you will need to
+        install some software on your system and ensure that an environment
+        variable is set correctly.</para>
+    
+      <procedure>
+	<step>
+	  <para>Download and install <filename role="package">textproc/docproj</filename>
+	    from the FreeBSD ports system.  This is a
+            <emphasis>meta-port</emphasis> that should download and install
+            all of the programs and supporting files that are used by the
+            Documentation Project.</para>
+	</step>
+	
+        <step>
+          <para>Add lines to your shell startup files to set
+            <envar>SGML_CATALOG_FILES</envar>. (If you are not working
+            on the English version of the documentation, you will want
+            to substitute the correct directory for your
+            language.)</para>
+    
+	  <example id="sgml-primer-envars">
+	    <title><filename>.profile</filename>, for &man.sh.1; and
+	      &man.bash.1; users</title>
+	    
+	    <programlisting>SGML_ROOT=/usr/local/share/sgml	    
+SGML_CATALOG_FILES=${SGML_ROOT}/jade/catalog
+SGML_CATALOG_FILES=${SGML_ROOT}/iso8879/catalog:$SGML_CATALOG_FILES
+SGML_CATALOG_FILES=${SGML_ROOT}/html/catalog:$SGML_CATALOG_FILES
+SGML_CATALOG_FILES=${SGML_ROOT}/docbook/4.1/catalog:$SGML_CATALOG_FILES
+SGML_CATALOG_FILES=/usr/doc/share/sgml/catalog:$SGML_CATALOG_FILES
+SGML_CATALOG_FILES=/usr/doc/en_US.ISO8859-1/share/sgml/catalog:$SGML_CATALOG_FILES
+export SGML_CATALOG_FILES</programlisting>
+	  </example>
+
+	  <example>
+	    <title><filename>.cshrc</filename>, for &man.csh.1; and
+	      &man.tcsh.1; users</title>
+	    
+	    <programlisting>setenv SGML_ROOT /usr/local/share/sgml
+setenv SGML_CATALOG_FILES ${SGML_ROOT}/jade/catalog
+setenv SGML_CATALOG_FILES ${SGML_ROOT}/iso8879/catalog:$SGML_CATALOG_FILES
+setenv SGML_CATALOG_FILES ${SGML_ROOT}/html/catalog:$SGML_CATALOG_FILES
+setenv SGML_CATALOG_FILES ${SGML_ROOT}/docbook/4.1/catalog:$SGML_CATALOG_FILES
+setenv SGML_CATALOG_FILES /usr/doc/share/sgml/catalog:$SGML_CATALOG_FILES
+setenv SGML_CATALOG_FILES /usr/doc/en_US.ISO8859-1/share/sgml/catalog:$SGML_CATALOG_FILES</programlisting>
+          </example>
+    
+          <para>Then either log out, and log back in again, or run those
+            commands from the command line to set the variable values.</para>
+	</step>
+      </procedure>
+    
+      <procedure>
+	<step>
+	  <para>Create <filename>example.sgml</filename>, and enter the
+            following text:</para>
+
+	  <programlisting><![ CDATA [<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+
+<html>
+  <head>	     
+    <title>An example HTML file</title>
+  </head>
+
+  <body>	    
+    <p>This is a paragraph containing some text.</p>
+
+    <p>This paragraph contains some more text.</p>
+
+    <p align="right">This paragraph might be right-justified.</p>
+  </body>	    
+</html>]]></programlisting>
+	</step>
+
+	<step>
+	  <para>Try to validate this file using an SGML parser.</para>
+
+	  <para>Part of <filename role="package">textproc/docproj</filename> is the
+	    <command>nsgmls</command> <link linkend="sgml-primer-validating">validating
+	    parser</link>.  Normally, <command>nsgmls</command> reads in a document
+	    marked up according to an SGML DTD and returns a copy of the
+	    document's Element Structure Information Set (ESIS, but that is
+	    not important right now).</para>
+
+	  <para>However, when <command>nsgmls</command> is given the <option>-s</option>
+	    parameter, <command>nsgmls</command> will suppress its normal output, and
+	    just print error messages.  This makes it a useful way to check to
+	    see if your document is valid or not.</para>
+
+	  <para>Use <command>nsgmls</command> to check that your document is
+	    valid:</para>
+
+          <screen>&prompt.user; <userinput>nsgmls -s example.sgml</userinput></screen>
+
+	  <para>As you will see, <command>nsgmls</command> returns without displaying any
+	    output.  This means that your document validated
+	    successfully.</para>
+	</step>
+
+	<step>
+	  <para>See what happens when required elements are omitted.  Try
+	    removing the <sgmltag>title</sgmltag> and
+	    <sgmltag>/title</sgmltag> tags, and re-run the validation.</para>
+
+          <screen>&prompt.user; <userinput>nsgmls -s example.sgml</userinput>
+nsgmls:example.sgml:5:4:E: character data is not allowed here
+nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
+
+	  <para>The error output from <command>nsgmls</command> is organized into
+	    colon-separated groups, or columns.</para>
+
+	  <informaltable frame="none" pgwide="1">
+	    <tgroup cols="2">
+	      <thead>
+		<row>
+		  <entry>Column</entry>
+		  <entry>Meaning</entry>
+		</row>
+	      </thead>
+	      
+	      <tbody>
+		<row>
+		  <entry>1</entry>
+		  <entry>The name of the program generating the error.  This
+		    will always be <literal>nsgmls</literal>.</entry>
+		</row>
+
+		<row>
+		  <entry>2</entry>
+		  <entry>The name of the file that contains the error.</entry>
+		</row>
+
+		<row>
+		  <entry>3</entry>
+		  <entry>Line number where the error appears.</entry>
+		</row>
+
+		<row>
+		  <entry>4</entry>
+		  <entry>Column number where the error appears.</entry>
+		</row>
+
+		<row>
+		  <entry>5</entry>
+		  <entry>A one letter code indicating the nature of the
+		    message.  <literal>I</literal> indicates an informational
+		    message, <literal>W</literal> is for warnings, and
+		    <literal>E</literal> is for errors<footnote>
+		      <para>It is not always the fifth column either.
+			<command>nsgmls -sv</command> displays
+			<literal>nsgmls:I: SP version "1.3"</literal>
+			(depending on the installed version).  As you can see,
+			this is an informational message.</para>
+		    </footnote>, and <literal>X</literal> is for
+		    cross-references.  As you can see, these messages are
+		    errors.</entry>
+		</row>
+
+		<row>
+		  <entry>6</entry>
+		  <entry>The text of the error message.</entry>
+		</row>
+	      </tbody>
+	    </tgroup>
+	  </informaltable>
+
+	  <para>Simply omitting the <sgmltag>title</sgmltag> tags has
+	    generated 2 different errors.</para>
+
+	  <para>The first error indicates that content (in this case,
+	    characters, rather than the start tag for an element) has occurred
+	    where the SGML parser was expecting something else.  In this case,
+	    the parser was expecting to see one of the start tags for elements
+	    that are valid inside <sgmltag>head</sgmltag> (such as
+	    <sgmltag>title</sgmltag>).</para>
+
+	  <para>The second error is because <sgmltag>head</sgmltag> elements
+	    <emphasis>must</emphasis> contain a <sgmltag>title</sgmltag>
+	    element.  Because it does not <command>nsgmls</command> considers that the
+	    element has not been properly finished.  However, the closing tag
+	    indicates that the element has been closed before it has been
+	    finished.</para>
+	</step>
+
+	<step>
+	  <para>Put the <literal>title</literal> element back in.</para>
+	</step>
+      </procedure>
+    </sect2>
+  </sect1>
+
+  <sect1 id="sgml-primer-doctype-declaration">
+    <title>The DOCTYPE declaration</title>
+
+    <para>The beginning of each document that you write must specify the name
+      of the DTD that the document conforms to.  This is so that SGML parsers
+      can determine the DTD and ensure that the document does conform to 
+      it.</para>
+
+    <para>This information is generally expressed on one line, in the DOCTYPE
+      declaration.</para>
+
+    <para>A typical declaration for a document written to conform with version
+      4.0 of the HTML DTD looks like this:</para>
+
+    <programlisting><![ CDATA [<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN">]]></programlisting>
+
+    <para>That line contains a number of different components.</para>
+
+    <variablelist>
+      <varlistentry>
+	<term><literal>&lt;!</literal></term>
+	
+	<listitem>
+	  <para>Is the <emphasis>indicator</emphasis> that indicates that this
+	    is an SGML declaration.  This line is declaring the document type.
+	  </para>
+	</listitem>
+      </varlistentry>
+
+      <varlistentry>
+	<term><literal>DOCTYPE</literal></term>
+	
+	<listitem>
+	  <para>Shows that this is an SGML declaration for the document
+	    type.</para>
+	</listitem>
+      </varlistentry>
+      
+      <varlistentry>
+	<term><literal>html</literal></term>
+	
+	<listitem>
+	  <para>Names the first <link linkend="sgml-primer-elements">element</link> that
+	    will appear in the document.</para>
+	</listitem>
+      </varlistentry>
+
+      <varlistentry>
+	<term><literal>PUBLIC "-//W3C//DTD HTML 4.0//EN"</literal></term>
+
+	<listitem>
+	  <para>Lists the Formal Public Identifier (FPI)<indexterm>
+	      <primary>Formal Public Identifier</primary>
+	    </indexterm>
+	    for the DTD that this
+	    document conforms to.  Your SGML parser will use this to find the
+	    correct DTD when processing this document.</para>
+
+	  <para><literal>PUBLIC</literal> is not a part of the FPI, but
+	    indicates to the SGML processor how to find the DTD referenced in
+	    the FPI.  Other ways of telling the SGML parser how to find the
+	    DTD are shown <link
+	      linkend="sgml-primer-fpi-alternatives">later</link>.</para>
+	</listitem>
+      </varlistentry>
+
+      <varlistentry>
+	<term><literal>&gt;</literal></term>
+	
+	<listitem>
+	  <para>Returns to the document.</para>
+	</listitem>
+      </varlistentry>
+    </variablelist>
+    
+    <sect2>
+      <title>Formal Public Identifiers (FPIs)<indexterm significance="preferred">
+	  <primary>Formal Public Identifier</primary>
+	</indexterm>
+</title>
+
+      <note>
+	<para>You do not need to know this, but it is useful background, and
+	  might help you debug problems when your SGML processor can not locate
+	  the DTD you are using.</para>
+      </note>
+      
+      <para>FPIs must follow a specific syntax.  This syntax is as
+	follows:</para>
+
+      <programlisting>"<replaceable>Owner</replaceable>//<replaceable>Keyword</replaceable> <replaceable>Description</replaceable>//<replaceable>Language</replaceable>"</programlisting>
+
+      <variablelist>
+	<varlistentry>
+	  <term><replaceable>Owner</replaceable></term>
+	  
+	  <listitem>
+	    <para>This indicates the owner of the FPI.</para>
+
+	    <para>If this string starts with <quote>ISO</quote> then this is an
+	      ISO owned FPI.  For example, the FPI <literal>"ISO
+		8879:1986//ENTITIES Greek Symbols//EN"</literal> lists
+	      <literal>ISO 8879:1986</literal> as being the owner for the set
+	      of entities for Greek symbols.  ISO 8879:1986 is the ISO number
+	      for the SGML standard.</para>
+
+	    <para>Otherwise, this string will either look like
+	      <literal>-//<replaceable>Owner</replaceable></literal> or
+	      <literal>+//<replaceable>Owner</replaceable></literal> (notice
+	      the only difference is the leading <literal>+</literal> or
+	      <literal>-</literal>).</para>
+
+	    <para>If the string starts with <literal>-</literal> then the
+	      owner information is unregistered, with a <literal>+</literal>
+	      it identifies it as being registered.</para>
+
+	    <para>ISO 9070:1991 defines how registered names are generated; it
+	      might be derived from the number of an ISO publication, an ISBN
+	      code, or an organization code assigned according to ISO 6523.
+	      In addition, a registration authority could be created in order
+	      to assign registered names.  The ISO council delegated this to
+	      the American National Standards Institute (ANSI).</para>
+
+	    <para>Because the FreeBSD Project has not been registered the
+	      owner string is <literal>-//FreeBSD</literal>.  And as you can
+	      see, the W3C are not a registered owner either.</para>
+	  </listitem>
+	</varlistentry>
+	
+	<varlistentry>
+	  <term><replaceable>Keyword</replaceable></term>
+	  
+	  <listitem>
+	    <para>There are several keywords that indicate the type of
+	      information in the file.  Some of the most common keywords are
+	      <literal>DTD</literal>, <literal>ELEMENT</literal>,
+	      <literal>ENTITIES</literal>, and <literal>TEXT</literal>.
+	      <literal>DTD</literal> is used only for DTD files,
+	      <literal>ELEMENT</literal> is usually used for DTD fragments
+	      that contain only entity or element declarations.
+	      <literal>TEXT</literal> is used for SGML content (text and
+	      tags).</para>
+	  </listitem>
+	</varlistentry>
+	
+	<varlistentry>
+	  <term><replaceable>Description</replaceable></term>
+	  
+	  <listitem>
+	    <para>Any description you want to supply for the contents of this
+	      file.  This may include version numbers or any short text that
+	      is meaningful to you and unique for the SGML system.</para>
+	  </listitem>
+	</varlistentry>
+	
+	<varlistentry>
+	  <term><replaceable>Language</replaceable></term>
+	  
+	  <listitem>
+	    <para>This is an ISO two-character code that identifies the native
+	      language for the file.  <literal>EN</literal> is used for
+	      English.</para>
+	  </listitem>
+	</varlistentry>
+      </variablelist>
+      
+      <sect3>
+	<title><filename>catalog</filename> files</title>
+	
+	<para>If you use the syntax above and process this document
+	  using an SGML processor, the processor will need to have some way of
+	  turning the FPI into the name of the file on your computer that
+	  contains the DTD.</para>
+	
+	<para>In order to do this it can use a catalog file.  A catalog file
+	  (typically called <filename>catalog</filename>) contains lines that
+	  map FPIs to filenames.  For example, if the catalog file contained
+	  the line:</para>
+	
+	<programlisting>PUBLIC "-//W3C//DTD HTML 4.0//EN"             "4.0/strict.dtd"</programlisting>
+
+	<para>The SGML processor would know to look up the DTD from
+	  <filename>strict.dtd</filename> in the <filename>4.0</filename>
+	  subdirectory of whichever directory held the
+	  <filename>catalog</filename> file that contained that line.</para>
+
+	<para>Look at the contents of
+	  <filename>/usr/local/share/sgml/html/catalog</filename>.  This is
+	  the catalog file for the HTML DTDs that will have been installed as
+	  part of the <filename role="package">textproc/docproj</filename> port.</para>
+      </sect3>
+
+      <sect3>
+	<title><envar>SGML_CATALOG_FILES</envar></title>
+
+	<para>In order to locate a <filename>catalog</filename> file, your
+	  SGML processor will need to know where to look.  Many of them
+	  feature command line parameters for specifying the path to one or
+	  more catalogs.</para>
+
+	<para>In addition, you can set <envar>SGML_CATALOG_FILES</envar> to
+	  point to the files.  This environment variable should consist of a
+	  colon-separated list of catalog files (including their full
+	  path).</para>
+
+	<para>Typically, you will want to include the following files:</para>
+
+	<itemizedlist>
+	  <listitem>
+	    <para><filename>/usr/local/share/sgml/docbook/4.1/catalog</filename></para>
+	  </listitem>
+
+	  <listitem>
+	    <para><filename>/usr/local/share/sgml/html/catalog</filename></para>
+	  </listitem>
+
+	  <listitem>
+	    <para><filename>/usr/local/share/sgml/iso8879/catalog</filename></para>
+	  </listitem>
+
+	  <listitem>
+	    <para><filename>/usr/local/share/sgml/jade/catalog</filename></para>
+	  </listitem>
+	</itemizedlist>
+
+	<para>You should <link linkend="sgml-primer-envars">already have done
+	    this</link>.</para>
+      </sect3>
+    </sect2>
+    
+    <sect2 id="sgml-primer-fpi-alternatives">
+      <title>Alternatives to FPIs</title>
+      
+      <para>Instead of using an FPI to indicate the DTD that the document
+	conforms to (and therefore, which file on the system contains the DTD)
+	you can explicitly specify the name of the file.</para>
+      
+      <para>The syntax for this is slightly different:</para>
+      
+      <programlisting><![ CDATA [<!DOCTYPE html SYSTEM "/path/to/file.dtd">]]></programlisting>
+      
+      <para>The <literal>SYSTEM</literal> keyword indicates that the SGML
+	processor should locate the DTD in a system specific fashion.  This
+	typically (but not always) means the DTD will be provided as a
+	filename.</para>
+      
+      <para>Using FPIs is preferred for reasons of portability.  You do not
+	want to have to ship a copy of the DTD around with your document, and
+	if you used the <literal>SYSTEM</literal> identifier then everyone
+	would need to keep their DTDs in the same place.</para>
+    </sect2>
+  </sect1>
+  
+  <sect1 id="sgml-primer-sgml-escape">
+    <title>Escaping back to SGML</title>
+
+    <para>Earlier in this primer I said that SGML is only used when writing a
+      DTD.  This is not strictly true.  There is certain SGML syntax that you
+      will want to be able to use within your documents.  For example,
+      comments can be included in your document, and will be ignored by the
+      parser.  Comments are entered using SGML syntax.  Other uses for SGML
+      syntax in your document will be shown later too.</para>
+      
+    <para>Obviously, you need some way of indicating to the SGML processor
+      that the following content is not elements within the document, but is
+      SGML that the parser should act upon.</para>
+
+    <para>These sections are marked by <literal>&lt;! ...  &gt;</literal> in
+      your document.  Everything between these delimiters is SGML syntax as
+      you might find within a DTD.</para>
+
+    <para>As you may just have realized, the <link
+	linkend="sgml-primer-doctype-declaration">DOCTYPE declaration</link>
+      is an example of SGML syntax that you need to include in your
+      document&hellip;</para>
+  </sect1>
+  
+  <sect1 id="sgml-primer-comments">
+    <title>Comments</title>
+    
+    <para>Comments are an SGML construction, and are normally only valid
+      inside a DTD.  However, as <xref linkend="sgml-primer-sgml-escape">
+      shows, it is possible to use SGML syntax within your document.</para>
+
+    <para>The delimiter for SGML comments is the string
+      <quote><literal>--</literal></quote>.  The first occurrence of this string
+      opens a comment, and the second closes it.</para>
+
+    <example>
+      <title>SGML generic comment</title>
+
+      <programlisting>&lt;!-- test comment --></programlisting>
+      
+      <programlisting><![ CDATA [
+<!-- This is inside the comment -->
+
+<!-- This is another comment    -->
+
+<!-- This is one way
+     of doing multiline comments -->
+
+<!-- This is another way of   --
+  -- doing multiline comments -->]]></programlisting>
+    </example>
+
+    <![ %output.print; [
+    <important>
+      <title>Use 2 dashes</title>
+
+      <para>There is a problem with producing the Postscript and PDF versions
+	of this document.  The above example probably shows just one hyphen
+	symbol, <literal>-</literal> after the <literal>&lt;!</literal> and
+	before the <literal>&gt;</literal>.</para>
+
+      <para>You <emphasis>must</emphasis> use two <literal>-</literal>,
+	<emphasis>not</emphasis> one.  The Postscript and PDF versions have
+	translated the two <literal>-</literal> in the original to a longer,
+	more professional <emphasis>em-dash</emphasis>, and broken this
+	example in the process.</para>
+
+      <para>The HTML, plain text, and RTF versions of this document are not
+	affected.</para>
+    </important>
+    ]]>
+    
+    <para>If you have used HTML before you may have been shown different rules
+      for comments.  In particular, you may think that the string
+      <literal>&lt;!--</literal> opens a comment, and it is only closed by
+      <literal>--&gt;</literal>.</para>
+
+    <para>This is <emphasis>not</emphasis> the case.  A lot of web browsers
+      have broken HTML parsers, and will accept that as valid.  However, the
+      SGML parsers used by the Documentation Project are much stricter, and
+      will reject documents that make that error.</para>
+
+    <example>
+      <title>Erroneous SGML comments</title>
+
+      <programlisting><![ CDATA [
+<!-- This is in the comment --
+
+     THIS IS OUTSIDE THE COMMENT!
+
+  -- back inside the comment -->]]></programlisting>
+
+      <para>The SGML parser will treat this as though it were actually:</para>
+
+      <programlisting>&lt;!THIS IS OUTSIDE THE COMMENT&gt;</programlisting>
+
+      <para>This is not valid SGML, and may give confusing error
+	messages.</para>
+
+      <programlisting><![ CDATA [<!--------------- This is a very bad idea --------------->]]></programlisting>
+
+      <para>As the example suggests, <emphasis>do not</emphasis> write
+	comments like that.</para>
+
+      <programlisting><![ CDATA [<!--===================================================-->]]></programlisting>
+
+      <para>That is a (slightly) better approach, but it still potentially
+	confusing to people new to SGML.</para>
+    </example>
+
+    <sect2>
+      <title>For you to do&hellip;</title>
+
+      <procedure>
+	<step>
+	  <para>Add some comments to <filename>example.sgml</filename>, and
+	    check that the file still validates using <command>nsgmls</command>.</para>
+	</step>
+
+	<step>
+	  <para>Add some invalid comments to
+	    <filename>example.sgml</filename>, and see the error messages that
+	    <command>nsgmls</command> gives when it encounters an invalid comment.</para>
+	</step>
+      </procedure>
+    </sect2>
+  </sect1>
+    
+  <sect1 id="sgml-primer-entities">
+    <title>Entities</title>
+
+    <para>Entities are a mechanism for assigning names to chunks of content.
+      As an SGML parser processes your document, any entities it finds are
+      replaced by the content of the entity.</para>
+    
+    <para>This is a good way to have re-usable, easily changeable chunks of
+      content in your SGML documents.  It is also the only way to include one
+      marked up file inside another using SGML.</para>
+    
+    <para>There are two types of entities which can be used in two different
+      situations; <emphasis>general entities</emphasis> and
+      <emphasis>parameter entities</emphasis>.</para>
+    
+    <sect2 id="sgml-primer-general-entities">
+      <title>General Entities</title>
+      
+      <para>You cannot use general entities in an SGML context (although you
+	define them in one).  They can only be used in your document.
+	Contrast this with <link
+	  linkend="sgml-primer-parameter-entities">parameter
+	  entities</link>.</para>
+
+      <para>Each general entity has a name.  When you want to reference a
+	general entity (and therefore include whatever text it represents in
+	your document), you write
+	<literal>&amp;<replaceable>entity-name</replaceable>;</literal>.  For
+	example, suppose you had an entity called
+	<literal>current.version</literal> which expanded to the current
+	version number of your product.  You could write:</para>
+
+      <programlisting><![ CDATA [<para>The current version of our product is
+  &current.version;.</para>]]></programlisting>
+
+      <para>When the version number changes you can simply change the
+	definition of the value of the general entity and reprocess your
+	document.</para>
+
+      <para>You can also use general entities to enter characters that you
+	could not otherwise include in an SGML document.  For example,
+	<literal>&lt;</literal> and <literal>&amp;</literal> cannot
+	normally appear in an SGML document.  When the SGML
+	parser sees the <literal>&lt;</literal>
+	symbol it assumes that a tag (either a start tag
+	or an end tag) is about to appear, and when it sees the
+	<literal>&amp;</literal> symbol
+	it assumes the next text will be the name of an entity.</para>
+
+      <para>Fortunately, you can use the two general entities
+	<literal>&amp;lt;</literal> and <literal>&amp;amp;</literal>
+	whenever you need to include one or other of these.</para>
+	
+      <para>A general entity can only be defined within an SGML context.
+	Typically, this is done immediately after the DOCTYPE
+	declaration.</para>
+
+      <example>
+	<title>Defining general entities</title>
+
+	<programlisting><![ CDATA [<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN" [
+<!ENTITY current.version    "3.0-RELEASE">
+<!ENTITY last.version       "2.2.7-RELEASE">
+]>]]></programlisting>
+	  
+	<para>Notice how the DOCTYPE declaration has been extended by adding a
+	  square bracket at the end of the first line.  The two entities are
+	  then defined over the next two lines, before the square bracket is
+	  closed, and then the DOCTYPE declaration is closed.</para>
+
+	<para>The square brackets are necessary to indicate that we are
+	  extending the DTD indicated by the DOCTYPE declaration.</para>
+      </example>
+    </sect2>
+    
+    <sect2 id="sgml-primer-parameter-entities">
+      <title>Parameter entities</title>
+
+      <para>Like <link linkend="sgml-primer-general-entities">general
+	  entities</link>, parameter entities are used to assign names to
+	reusable chunks of text.  However, where as general entities can only
+	be used within your document, parameter entities can only be used
+	within an <link linkend="sgml-primer-sgml-escape">SGML
+	  context</link>.</para>
+
+      <para>Parameter entities are defined in a similar way to general
+	entities.  However, instead of using
+	<literal>&amp;<replaceable>entity-name</replaceable>;</literal> to
+	refer to them, use
+	<literal>%<replaceable>entity-name</replaceable>;</literal><footnote>
+	  <para><emphasis>P</emphasis>arameter entities use the
+	    <emphasis>P</emphasis>ercent symbol.</para>
+	</footnote>.  The definition also includes the <literal>%</literal>
+	between the <literal>ENTITY</literal> keyword and the name of the
+	entity.</para>
+      
+      <example>
+	<title>Defining parameter entities</title>
+	
+	<programlisting><![ CDATA [<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN" [
+<!ENTITY % param.some "some">
+<!ENTITY % param.text "text">
+<!ENTITY % param.new  "%param.some more %param.text">
+
+<!-- %param.new now contains "some more text" -->
+]>]]></programlisting>
+      </example>
+	
+      <para>This may not seem particularly useful.  It will be.</para>
+    </sect2>
+
+    <sect2>
+      <title>For you to do&hellip;</title>
+
+      <procedure>
+	<step>
+	  <para>Add a general entity to
+	    <filename>example.sgml</filename>.</para>
+
+	  <programlisting><![ CDATA [<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
+<!ENTITY version "1.1">
+]>	  
+
+<html>
+  <head>	     
+    <title>An example HTML file</title>
+  </head>
+
+  <!-- You might well have some comments in here as well -->
+	  
+  <body>	    
+    <p>This is a paragraph containing some text.</p>
+
+    <p>This paragraph contains some more text.</p>
+
+    <p align="right">This paragraph might be right-justified.</p>
+
+    <p>The current version of this document is: &version;</p>	  
+  </body>	    
+</html>]]></programlisting>	  
+	</step>
+
+	<step>
+	  <para>Validate the document using <command>nsgmls</command>.</para>
+	</step>
+
+	<step>
+	  <para>Load <filename>example.sgml</filename> into your web browser
+	    (you may need to copy it to <filename>example.html</filename>
+	    before your browser recognizes it as an HTML document).</para>
+
+	  <para>Unless your browser is very advanced, you will not see the entity
+	    reference <literal>&amp;version;</literal> replaced with the
+	    version number.  Most web browsers have very simplistic parsers
+	    which do not handle proper SGML<footnote>
+	      <para>This is a shame.  Imagine all the problems and hacks (such
+		as Server Side Includes) that could be avoided if they
+		did.</para>
+	    </footnote>.</para>
+	</step>
+
+	<step>
+	  <para>The solution is to <emphasis>normalize</emphasis> your
+	    document using an SGML normalizer.  The normalizer reads in valid
+	    SGML and outputs equally valid SGML which has been transformed in
+	    some way.  One of the ways in which the normalizer transforms the
+	    SGML is to expand all the entity references in the document,
+	    replacing the entities with the text that they represent.</para>
+
+	  <para>You can use <command>sgmlnorm</command> to do this.</para>
+
+          <screen>&prompt.user; <userinput>sgmlnorm example.sgml &gt; example.html</userinput></screen>
+
+	  <para>You should find a normalized (i.e., entity references
+	    expanded) copy of your document in
+	    <filename>example.html</filename>, ready to load into your web
+	    browser.</para>
+	</step>
+
+	<step>
+	  <para>If you look at the output from <command>sgmlnorm</command>
+	    you will see that it does not include a DOCTYPE declaration at
+	    the start.  To include this you need to use the <option>-d</option>
+	    option:</para>
+
+          <screen>&prompt.user; <userinput>sgmlnorm -d example.sgml &gt; example.html</userinput></screen>
+	</step>
+      </procedure>
+    </sect2>
+  </sect1>
+  
+  <sect1 id="sgml-primer-include">
+    <title>Using entities to include files</title>
+    
+    <para>Entities (both <link
+	linkend="sgml-primer-general-entities">general</link> and <link
+	linkend="sgml-primer-parameter-entities">parameter</link>) are
+      particularly useful when used to include one file inside another.</para>
+
+    <sect2 id="sgml-primer-include-using-gen-entities">
+      <title>Using general entities to include files</title>
+      
+      <para>Suppose you have some content for an SGML book organized into
+	files, one file per chapter, called
+	<filename>chapter1.sgml</filename>,
+	<filename>chapter2.sgml</filename>, and so forth, with a
+	<filename>book.sgml</filename> file that will contain these
+	chapters.</para>
+
+      <para>In order to use the contents of these files as the values for your
+	entities, you declare them with the <literal>SYSTEM</literal> keyword.
+	This directs the SGML parser to use the contents of the named file as
+	the value of the entity.</para>
+
+      <example>
+	<title>Using general entities to include files</title>
+	
+	<programlisting><![ CDATA [<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN" [
+<!ENTITY chapter.1 SYSTEM "chapter1.sgml">
+<!ENTITY chapter.2 SYSTEM "chapter2.sgml">
+<!ENTITY chapter.3 SYSTEM "chapter3.sgml">
+<!-- And so forth -->
+]>
+
+<html>
+  <!-- Use the entities to load in the chapters -->
+
+  &chapter.1;
+  &chapter.2;
+  &chapter.3;
+</html>]]></programlisting>
+      </example>
+      
+      <warning>
+	<para>When using general entities to include other files within a
+	  document, the files being included
+	  (<filename>chapter1.sgml</filename>,
+	  <filename>chapter2.sgml</filename>, and so on) <emphasis>must
+	    not</emphasis> start with a DOCTYPE declaration.  This is a syntax
+	  error.</para>
+      </warning>
+    </sect2>
+    
+    <sect2>
+      <title>Using parameter entities to include files</title>
+      
+      <para>Recall that parameter entities can only be used inside an SGML
+	context.  Why then would you want to include a file within an SGML
+	context?</para>
+
+      <para>You can use this to ensure that you can reuse your general
+	entities.</para>
+
+      <para>Suppose that you had many chapters in your document, and you
+	reused these chapters in two different books, each book organizing the
+	chapters in a different fashion.</para>
+
+      <para>You could list the entities at the top of each book, but this
+	quickly becomes cumbersome to manage.</para>
+
+      <para>Instead, place the general entity definitions inside one file,
+	and use a parameter entity to include that file within your
+	document.</para>
+
+      <example>
+	<title>Using parameter entities to include files</title>
+
+	<para>First, place your entity definitions in a separate file, called
+	  <filename>chapters.ent</filename>.  This file contains the
+	  following:</para>
+	  
+	<programlisting><![ CDATA [<!ENTITY chapter.1 SYSTEM "chapter1.sgml">
+<!ENTITY chapter.2 SYSTEM "chapter2.sgml">
+<!ENTITY chapter.3 SYSTEM "chapter3.sgml">]]></programlisting>
+
+	<para>Now create a parameter entity to refer to the contents of the
+	  file.  Then use the parameter entity to load the file into the
+	  document, which will then make all the general entities available
+	  for use.  Then use the general entities as before:</para>
+
+	<programlisting><![ CDATA [<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN" [
+<!-- Define a parameter entity to load in the chapter general entities -->
+<!ENTITY % chapters SYSTEM "chapters.ent">
+
+<!-- Now use the parameter entity to load in this file -->
+%chapters;
+]>
+
+<html>
+  &chapter.1;
+  &chapter.2;
+  &chapter.3;
+</html>]]></programlisting>
+      </example>
+    </sect2>
+
+    <sect2>
+      <title>For you to do&hellip;</title>
+
+      <sect3>
+	<title>Use general entities to include files</title>
+
+	<procedure>
+	  <step>
+	    <para>Create three files, <filename>para1.sgml</filename>,
+	      <filename>para2.sgml</filename>, and
+	      <filename>para3.sgml</filename>.</para>
+
+	    <para>Put content similar to the following in each file:</para>
+
+	    <programlisting><![ CDATA [<p>This is the first paragraph.</p>]]></programlisting>
+	  </step>
+
+	  <step>
+	    <para>Edit <filename>example.sgml</filename> so that it looks like
+	      this:</para>
+
+	    <programlisting><![ CDATA [<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN" [
+<!ENTITY version "1.1">
+<!ENTITY para1 SYSTEM "para1.sgml">
+<!ENTITY para2 SYSTEM "para2.sgml">
+<!ENTITY para3 SYSTEM "para3.sgml">
+]>
+
+<html>
+  <head>
+    <title>An example HTML file</title>
+  </head>
+
+  <body>
+    <p>The current version of this document is: &version;</p>
+
+    &para1;
+    &para2;
+    &para3;
+  </body>
+</html>]]></programlisting>
+	  </step>
+
+	  <step>
+	    <para>Produce <filename>example.html</filename> by normalizing
+	      <filename>example.sgml</filename>.</para>
+
+            <screen>&prompt.user; <userinput>sgmlnorm -d example.sgml &gt; example.html</userinput></screen>
+	  </step>
+
+	  <step>
+	    <para>Load <filename>example.html</filename> into your web
+	      browser, and confirm that the
+	      <filename>para<replaceable>n</replaceable>.sgml</filename> files
+	      have been included in <filename>example.html</filename>.</para>
+	  </step>
+	</procedure>
+      </sect3>
+
+      <sect3>
+	<title>Use parameter entities to include files</title>
+
+	<note>
+	  <para>You must have taken the previous steps first.</para>
+	</note>
+	
+	<procedure>
+	  <step>
+	    <para>Edit <filename>example.sgml</filename> so that it looks like
+	      this:</para>
+	    
+	    <programlisting><![ CDATA [<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN" [
+<!ENTITY % entities SYSTEM "entities.sgml"> %entities;
+]>
+
+<html>
+  <head>
+    <title>An example HTML file</title>
+  </head>
+
+  <body>
+    <p>The current version of this document is: &version;</p>
+
+    &para1;
+    &para2;
+    &para3;
+  </body>
+</html>]]></programlisting>
+	  </step>
+
+	  <step>
+	    <para>Create a new file, <filename>entities.sgml</filename>, with
+	      this content:</para>
+
+	    <programlisting><![ CDATA [<!ENTITY version "1.1">
+<!ENTITY para1 SYSTEM "para1.sgml">
+<!ENTITY para2 SYSTEM "para2.sgml">
+<!ENTITY para3 SYSTEM "para3.sgml">]]></programlisting>
+	  </step>
+
+	  <step>
+	    <para>Produce <filename>example.html</filename> by normalizing
+	      <filename>example.sgml</filename>.</para>
+
+            <screen>&prompt.user; <userinput>sgmlnorm -d example.sgml &gt; example.html</userinput></screen>
+	  </step>
+
+	  <step>
+	    <para>Load <filename>example.html</filename> into your web
+	      browser, and confirm that the
+	      <filename>para<replaceable>n</replaceable>.sgml</filename> files
+	      have been included in <filename>example.html</filename>.</para>
+	  </step>
+	</procedure>
+      </sect3>
+    </sect2>
+  </sect1>
+  
+  <sect1 id="sgml-primer-marked-sections">
+    <title>Marked sections</title>
+    
+    <para>SGML provides a mechanism to indicate that particular pieces of the
+      document should be processed in a special way.  These are termed
+      <quote>marked sections</quote>.</para>
+
+    <example>
+      <title>Structure of a marked section</title>
+
+      <programlisting>&lt;![ <replaceable>KEYWORD</replaceable> [
+  Contents of marked section
+]]&gt;</programlisting>
+    </example>
+
+    <para>As you would expect, being an SGML construct, a marked section
+      starts with <literal>&lt!</literal>.</para>
+
+    <para>The first square bracket begins to delimit the marked
+      section.</para>
+
+    <para><replaceable>KEYWORD</replaceable> describes how this marked
+      section should be processed by the parser.</para>
+
+    <para>The second square bracket indicates that the content of the marked
+      section starts here.</para>
+    
+    <para>The marked section is finished by closing the two square brackets,
+      and then returning to the document context from the SGML context with
+      <literal>&gt;</literal>.</para>
+    
+    <sect2>
+      <title>Marked section keywords</title>
+      
+      <sect3>
+	<title><literal>CDATA</literal>, <literal>RCDATA</literal></title>
+	
+	<para>These keywords denote the marked sections <emphasis>content
+	    model</emphasis>, and allow you to change it from the
+	  default.</para>
+	
+	<para>When an SGML parser is processing a document it keeps track
+	  of what is called the <quote>content model</quote>.</para>
+	
+	<para>Briefly, the content model describes what sort of content the
+	  parser is expecting to see, and what it will do with it when it
+	  finds it.</para>
+
+	<para>The two content models you will probably find most useful are
+	  <literal>CDATA</literal> and <literal>RCDATA</literal>.</para>
+	
+	<para><literal>CDATA</literal> is for <quote>Character Data</quote>.
+	  If the parser is in this content model then it is expecting to see
+	  characters, and characters only.  In this model the
+	  <literal>&lt;</literal> and <literal>&amp;</literal>
+	  symbols lose their special status, and will be treated as ordinary
+	  characters.</para>
+	
+	<para><literal>RCDATA</literal> is for <quote>Entity references and
+	  character data</quote> If the parser is in this content model then it
+	  is expecting to see characters <emphasis>and</emphasis> entities.
+	  <literal>&lt;</literal> loses its special status, but
+	  <literal>&amp;</literal> will still be treated as
+	  starting the beginning of a general entity.</para>
+	
+	<para>This is particularly useful if you are including some verbatim
+	  text that contains lots of <literal>&lt;</literal> and
+	  <literal>&amp;</literal> characters.  While you
+	  could go through the text ensuring that every
+	  <literal>&lt;</literal> is converted to a
+	  <literal>&amp;lt;</literal> and every <literal>&amp;</literal>
+	  is converted to a <literal>&amp;amp;</literal>, it can be
+	  easier to mark the section as only containing CDATA.  When the SGML
+	  parser encounters this it will ignore the
+	  <literal>&lt;</literal> and <literal>&amp;</literal> symbols
+	  embedded in the content.</para>
+
+        <note>
+          <para>When you use <literal>CDATA</literal> or
+            <literal>RCDATA</literal> in examples of text marked up in SGML,
+            keep in mind that the content of <literal>CDATA</literal> is not
+            validated.  You have to check the included SGML text using other
+            means.  You could, for example, write the example in another
+            document, validate the example code, and then paste it to your
+            <literal>CDATA</literal> content.</para>
+        </note>
+	<!-- The nesting of CDATA within the next example is disgusting -->
+	  
+	<example>
+	  <title>Using a CDATA marked section</title>
+	  
+	  <programlisting>&lt;para>Here is an example of how you would include some text
+  that contained many &lt;literal>&amp;lt;&lt;/literal>
+  and &lt;literal>&amp;amp;&lt;/literal> symbols.  The sample
+  text is a fragment of HTML.  The surrounding text (&lt;para> and
+  &lt;programlisting>) are from DocBook.&lt;/para>
+
+&lt;programlisting>
+  &lt;![ CDATA [  <![ CDATA [
+    <p>This is a sample that shows you some of the elements within
+      HTML.  Since the angle brackets are used so many times, it is
+      simpler to say the whole example is a CDATA marked section
+      than to use the entity names for the left and right angle
+      brackets throughout.</p>
+
+    <ul>
+      <li>This is a listitem</li>
+      <li>This is a second listitem</li>
+      <li>This is a third listitem</li>
+    </ul>
+
+    <p>This is the end of the example.</p>]]>
+  ]]&gt;
+&lt;/programlisting></programlisting>
+
+	  <para>If you look at the source for this document you will see this
+	    technique used throughout.</para>
+	</example>
+      </sect3>
+      
+      <sect3>
+	<title><literal>INCLUDE</literal> and
+	  <literal>IGNORE</literal></title>
+	
+	<para>If the keyword is <literal>INCLUDE</literal> then the contents
+	  of the marked section will be processed.  If the keyword is
+	  <literal>IGNORE</literal> then the marked section is ignored and
+	  will not be processed.  It will not appear in the output.</para>
+
+	<example>
+	  <title>Using <literal>INCLUDE</literal> and
+	    <literal>IGNORE</literal> in marked sections</title>
+
+	  <programlisting>&lt;![ INCLUDE [
+  This text will be processed and included.
+]]&gt;
+
+&lt;![ IGNORE [
+  This text will not be processed or included.
+]]&gt;</programlisting>
+	</example>
+	
+	<para>By itself, this is not too useful.  If you wanted to remove text
+	  from your document you could cut it out, or wrap it in
+	  comments.</para>
+	  
+	<para>It becomes more useful when you realize you can use <link
+	    linkend="sgml-primer-parameter-entities">parameter entities</link>
+	  to control this.  Remember that parameter entities can only be used
+	  in SGML contexts, and the keyword of a marked section
+	  <emphasis>is</emphasis> an SGML context.</para>
+
+	<para>For example, suppose that you produced a hard-copy version of
+	  some documentation and an electronic version.  In the electronic
+	  version you wanted to include some extra content that was not to
+	  appear in the hard-copy.</para>
+
+	<para>Create a parameter entity, and set its value to
+	  <literal>INCLUDE</literal>.  Write your document, using marked
+	  sections to delimit content that should only appear in the
+	  electronic version.  In these marked sections use the parameter
+	  entity in place of the keyword.</para>
+
+	<para>When you want to produce the hard-copy version of the document,
+	  change the parameter entity's value to <literal>IGNORE</literal> and
+	  reprocess the document.</para>
+
+	<example>
+	  <title>Using a parameter entity to control a marked
+	    section</title>
+	  
+	  <programlisting>&lt;!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN" [
+&lt;!ENTITY % electronic.copy "INCLUDE">	     
+]]&gt;
+
+...
+
+&lt;![ %electronic.copy [
+  This content should only appear in the electronic
+  version of the document.
+]]&gt;</programlisting>
+
+	  <para>When producing the hard-copy version, change the entity's
+	    definition to:</para>
+	  
+	  <programlisting>&lt;!ENTITY % electronic.copy "IGNORE"></programlisting>
+
+	  <para>On reprocessing the document, the marked sections that use
+	    <literal>%electronic.copy</literal> as their keyword will be
+	    ignored.</para>
+	</example>
+      </sect3>
+    </sect2>
+
+    <sect2>
+      <title>For you to do&hellip;</title>
+
+      <procedure>
+	<step>
+	  <para>Create a new file, <filename>section.sgml</filename>, that
+	    contains the following:</para>
+
+	  <programlisting>&lt;!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0//EN" [
+&lt;!ENTITY % text.output "INCLUDE">
+]&gt;
+
+&lt;html>
+  &lt;head>
+    &lt;title>An example using marked sections&lt;/title>
+  &lt;/head>
+
+  &lt;body>	    
+    &lt;p>This paragraph &lt;![ CDATA [contains many &lt;
+      characters (&lt; &lt; &lt; &lt; &lt;) so it is easier
+      to wrap it in a CDATA marked section ]]&gt;&lt;/p>
+
+    &lt;![ IGNORE [
+    &lt;p>This paragraph will definitely not be included in the
+      output.&lt;/p>
+    ]]&gt;
+
+    &lt;![ <![ CDATA [%text.output]]> [
+    &lt;p>This paragraph might appear in the output, or it
+      might not.&lt;/p>
+
+    &lt;p>Its appearance is controlled by the <![CDATA[%text.output]]>
+      parameter entity.&lt;/p>	    
+    ]]&gt;
+  &lt;/body>
+&lt;/html></programlisting>	    
+	</step>
+
+	<step>
+	  <para>Normalize this file using &man.sgmlnorm.1; and examine the
+	    output.  Notice which paragraphs have appeared, which have
+	    disappeared, and what has happened to the content of the CDATA
+	    marked section.</para>
+	</step>
+
+	<step>
+	  <para>Change the definition of the <literal>text.output</literal>
+	    entity from <literal>INCLUDE</literal> to
+	    <literal>IGNORE</literal>.  Re-normalize the file, and examine the
+	    output to see what has changed.</para>
+	</step>
+      </procedure>
+    </sect2>
+  </sect1>
+  
+  <sect1 id="sgml-primer-conclusion">
+    <title>Conclusion</title>
+    
+    <para>That is the conclusion of this SGML primer.  For reasons of space
+      and complexity several things have not been covered in depth (or at
+      all).  However, the previous sections cover enough SGML for you to be
+      able to follow the organization of the FDP documentation.</para>
+  </sect1>
+</chapter>
+
+<!--
+     Local Variables:
+     mode: sgml
+     sgml-declaration: "../chapter.decl"
+     sgml-indent-data: t
+     sgml-omittag: nil
+     sgml-always-quote-attributes: t
+     sgml-parent-document: ("../book.sgml" "part" "chapter")
+     End:
+-->
diff --git a/zh_TW.Big5/books/fdp-primer/structure/chapter.sgml b/zh_TW.Big5/books/fdp-primer/structure/chapter.sgml
new file mode 100644
index 0000000000..6c0953a65c
--- /dev/null
+++ b/zh_TW.Big5/books/fdp-primer/structure/chapter.sgml
@@ -0,0 +1,294 @@
+<!-- Copyright (c) 1998, 1999 Nik Clayton, All rights reserved.
+
+     Redistribution and use in source (SGML DocBook) and 'compiled' forms
+     (SGML HTML, PDF, PostScript, RTF and so forth) with or without
+     modification, are permitted provided that the following conditions
+     are met:
+
+      1. Redistributions of source code (SGML DocBook) must retain the above
+         copyright notice, this list of conditions and the following
+         disclaimer as the first lines of this file unmodified.
+
+      2. Redistributions in compiled form (transformed to other DTDs,
+         converted to PDF, PostScript, RTF and other formats) must reproduce
+         the above copyright notice, this list of conditions and the
+         following disclaimer in the documentation and/or other materials
+         provided with the distribution.
+
+     THIS DOCUMENTATION IS PROVIDED BY NIK CLAYTON "AS IS" AND ANY EXPRESS OR
+     IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+     OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+     DISCLAIMED. IN NO EVENT SHALL NIK CLAYTON BE LIABLE FOR ANY DIRECT,
+     INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+     (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+     SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+     HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+     STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
+     ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
+     POSSIBILITY OF SUCH DAMAGE.
+
+     $FreeBSD$
+-->
+
+<chapter id="structure">
+  <title>Structuring documents under <filename>doc/</filename></title>
+
+  <para>The <filename>doc/</filename> tree is organized in a particular
+    fashion, and the documents that are part of the FDP are in turn organized
+    in a particular fashion.  The aim is to make it simple to add new
+    documentation into the tree and:</para>
+
+  <orderedlist>
+    <listitem>
+      <para>make it easy to automate converting the document to other formats;</para>
+    </listitem>
+
+    <listitem>
+      <para>promote consistency between the different documentation
+	organizations, to make it easier to switch between working on
+	different documents;</para>
+    </listitem>
+
+    <listitem>
+      <para>make it easy to decide where in the tree new documentation should
+	be placed.</para>
+    </listitem>
+  </orderedlist>
+
+  <para>In addition, the documentation tree has to accommodate documentation
+    that could be in many different languages and in many different
+    encodings.  It is important that the structure of the documentation tree
+    does not enforce any particular defaults or cultural preferences.</para>
+
+  <sect1 id="structure-top">
+    <title>The top level, <filename>doc/</filename></title>
+
+    <para>There are two types of directory under <filename>doc/</filename>,
+      each with very specific directory names and meanings.</para>
+
+    <segmentedlist>
+      <segtitle>Directory</segtitle>
+
+      <segtitle>Meaning</segtitle>
+
+      <seglistitem>
+	<seg><filename>share/</filename></seg>
+	
+	<seg>Contains files that are not specific to the various translations
+	  and encodings of the documentation.  Contains subdirectories to
+	  further categorize the information.  For example, the files that
+	  comprise the &man.make.1; infrastructure are in
+	  <filename>share/mk</filename>, while the additional SGML support
+	  files (such as the FreeBSD extended DocBook DTD) are in
+	  <filename>share/sgml</filename>.</seg>
+      </seglistitem>
+
+      <seglistitem>
+	<seg><filename><replaceable>lang</replaceable>.<replaceable>encoding</replaceable>/</filename></seg>
+	
+	<seg>One directory exists for each available translation and encoding
+	  of the documentation, for example
+	  <filename>en_US.ISO8859-1/</filename> and
+	  <filename>zh_TW.Big5/</filename>.  The names are long, but by fully
+	  specifying the language and encoding we prevent any future headaches 
+	  should a translation team want to provide the documentation in the
+	  same language but in more than one encoding.  This also completely
+	  isolates us from any problems that might be caused by a switch to
+	  Unicode.</seg>
+      </seglistitem>
+    </segmentedlist>
+  </sect1>
+
+  <sect1 id="structure-locale">
+    <title>The
+      <filename><replaceable>lang</replaceable>.<replaceable>encoding</replaceable>/</filename> directories</title>
+
+    <para>These directories contain the documents themselves.  The
+	documentation is split into up to three more categories at this
+	level, indicated by the different directory names.</para>
+
+    <segmentedlist>
+      <segtitle>Directory</segtitle>
+
+      <segtitle>Contents</segtitle>
+
+      <seglistitem>
+	<seg><filename>articles</filename></seg>
+	
+	<seg>Documentation marked up as a DocBook <sgmltag>article</sgmltag> 
+	  (or equivalent).  Reasonably short, and broken up into sections.
+	  Normally only available as one HTML file.</seg>
+      </seglistitem>
+	
+      <seglistitem>
+	<seg><filename>books</filename></seg>
+	
+	<seg>Documentation marked up as a DocBook <sgmltag>book</sgmltag> (or
+	  equivalent).  Book length, and broken up into chapters.  Normally
+	  available as both one large HTML file (for people with fast
+	  connections, or who want to print it easily from a browser) and
+	  as a collection of linked, smaller files.</seg>
+      </seglistitem>
+
+      <seglistitem>
+	<seg><filename>man</filename></seg>
+	
+	<seg>For translations of the system manual pages.  This directory will 
+	  contain one or more
+	  <filename>man<replaceable>n</replaceable></filename> directories,
+	  corresponding to the sections that have been translated.</seg>
+      </seglistitem>
+    </segmentedlist>
+
+    <para>Not every
+      <filename><replaceable>lang</replaceable>.<replaceable>encoding</replaceable></filename> directory will contain all of these directories.  It depends
+      on how much translation has been accomplished by that translation
+      team.</para>
+  </sect1>
+  
+  <sect1 id="structure-document">
+    <title>Document specific information</title>
+
+    <para>This section contains specific notes about particular documents
+      managed by the FDP.</para>
+
+    <sect2>
+      <title>The Handbook</title>
+
+      <subtitle><filename>books/handbook/</filename></subtitle>
+
+      <para>The Handbook is written to comply with the FreeBSD DocBook
+	extended DTD.</para>
+    
+      <para>The Handbook is organized as a DocBook <sgmltag>book</sgmltag>.
+	It is then divided into <sgmltag>part</sgmltag>s, each of which may
+	contain several <sgmltag>chapter</sgmltag>s.
+	<sgmltag>chapter</sgmltag>s are further subdivided into sections
+	(<sgmltag>sect1</sgmltag>) and subsections (<sgmltag>sect2</sgmltag>,
+	<sgmltag>sect3</sgmltag>) and so on.</para>
+  
+      <sect3>
+	<title>Physical organization</title>
+	
+	<para>There are a number of files and directories within the
+	  <filename>handbook</filename> directory.</para>
+
+	<note>
+	  <para>The Handbook's organization may change over time, and this
+	    document may lag in detailing the organizational changes.  If you
+	    have any questions about how the Handbook is organized, please
+	    contact the &a.doc;.</para>
+	</note>
+	
+	<sect4>
+	  <title><filename>Makefile</filename></title>
+	  
+	  <para>The <filename>Makefile</filename> defines some variables that
+	    affect how the SGML source is converted to other formats, and
+	    lists the various source files that make up the Handbook.  It then 
+	    includes the standard <filename>doc.project.mk</filename> file, to 
+	    bring in the rest of the code that handles converting documents
+	    from one format to another.</para>
+	</sect4>
+
+	<sect4>
+	  <title><filename>book.sgml</filename></title>
+	  
+	  <para>This is the top level document in the Handbook.  It contains
+	    the Handbook's <link
+	      linkend="sgml-primer-doctype-declaration">DOCTYPE
+	      declaration</link>, as well as the elements that describe the
+	    Handbook's structure.</para>
+
+	  <para><filename>book.sgml</filename> uses <link
+	      linkend="sgml-primer-parameter-entities">parameter
+	      entities</link> to load in the files with the
+	    <filename>.ent</filename> extension. These files (described later)
+	    then define <link linkend="sgml-primer-general-entities">general
+	      entities</link> that are used throughout the rest of the
+	    Handbook.</para>
+	</sect4>
+
+	<sect4>
+	  <title><filename><replaceable>directory</replaceable>/chapter.sgml</filename></title>
+
+	  <para>Each chapter in the Handbook is stored in a file called
+	    <filename>chapter.sgml</filename> in a separate directory from the
+	    other chapters.  Each directory is named after the value of the
+	    <literal>id</literal> attribute on the <sgmltag>chapter</sgmltag>
+	    element.</para>
+
+	  <para>For example, if one of the chapter files contains:</para>
+	  
+	  <programlisting><![ CDATA [
+<chapter id="kernelconfiguration">
+...
+</chapter>]]></programlisting>
+
+	  <para>then it will be called <filename>chapter.sgml</filename> in
+	    the <filename>kernelconfiguration</filename> directory.  In
+	    general, the entire contents of the chapter will be held in this
+	    file.</para>
+      
+	  <para>When the HTML version of the Handbook is produced, this will
+	    yield <filename>kernelconfiguration.html</filename>.  This is
+	    because of the <literal>id</literal> value, and is not related to
+	    the name of the directory.</para>
+
+	  <para>In earlier versions of the Handbook the files were stored in
+	    the same directory as <filename>book.sgml</filename>, and named
+	    after the value of the <literal>id</literal> attribute on the
+	    file's <sgmltag>chapter</sgmltag> element.  Moving them into
+	    separate directories prepares for future plans for the Handbook.
+	    Specifically, it will soon be possible to include images in each
+	    chapter.  It makes more sense for each image to be stored in a
+	    directory with the text for the chapter than to try to keep the
+	    text for all the chapters, and all the images, in one large
+	    directory.  Namespace collisions would be inevitable, and it is
+	    easier to work with several directories with a few files in them
+	    than it is to work with one directory that has many files in
+	    it.</para>
+
+	  <para>A brief look will show that there are many directories with
+	    individual <filename>chapter.sgml</filename> files, including
+	    <filename>basics/chapter.sgml</filename>,
+	    <filename>introduction/chapter.sgml</filename>, and
+	    <filename>printing/chapter.sgml</filename>.</para>
+	  
+	  <important>
+	    <para>Chapters and/or directories should not be named in a fashion
+	      that reflects their ordering within the Handbook.  This ordering
+	      might change as the content within the Handbook is reorganized;
+	      this sort of reorganization should not (generally) include the
+	      need to rename files (unless entire chapters are being promoted
+	      or demoted within the hierarchy).</para>
+	  </important>
+	  
+	  <para>Each <filename>chapter.sgml</filename> file will not be a
+	    complete SGML document.  In particular, they will not have their
+	    own DOCTYPE lines at the start of the files.</para>
+      
+	  <para>This is unfortunate as
+	    it makes it impossible to treat these as generic SGML
+	    files and simply convert them to HTML, RTF, PS, and other
+	    formats in the same way the main Handbook is generated.  This
+	    <emphasis>would</emphasis> force you to rebuild the Handbook
+	    every time you want to see the effect a change has had on just
+	    one chapter.</para>
+	</sect4>
+      </sect3>
+    </sect2>
+  </sect1>
+</chapter>
+
+<!--
+     Local Variables:
+     mode: sgml
+     sgml-declaration: "../chapter.decl"
+     sgml-indent-data: t
+     sgml-omittag: nil
+     sgml-always-quote-attributes: t
+     sgml-parent-document: ("../book.sgml" "part" "chapter")
+     End:
+-->
+
diff --git a/zh_TW.Big5/books/fdp-primer/stylesheets/chapter.sgml b/zh_TW.Big5/books/fdp-primer/stylesheets/chapter.sgml
new file mode 100644
index 0000000000..3b7626e5df
--- /dev/null
+++ b/zh_TW.Big5/books/fdp-primer/stylesheets/chapter.sgml
@@ -0,0 +1,102 @@
+<!-- Copyright (c) 1998, 1999 Nik Clayton, All rights reserved.
+
+     Redistribution and use in source (SGML DocBook) and 'compiled' forms
+     (SGML HTML, PDF, PostScript, RTF and so forth) with or without
+     modification, are permitted provided that the following conditions
+     are met:
+
+      1. Redistributions of source code (SGML DocBook) must retain the above
+         copyright notice, this list of conditions and the following
+         disclaimer as the first lines of this file unmodified.
+
+      2. Redistributions in compiled form (transformed to other DTDs,
+         converted to PDF, PostScript, RTF and other formats) must reproduce
+         the above copyright notice, this list of conditions and the
+         following disclaimer in the documentation and/or other materials
+         provided with the distribution.
+
+     THIS DOCUMENTATION IS PROVIDED BY NIK CLAYTON "AS IS" AND ANY EXPRESS OR
+     IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+     OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+     DISCLAIMED. IN NO EVENT SHALL NIK CLAYTON BE LIABLE FOR ANY DIRECT,
+     INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+     (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+     SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+     HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+     STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
+     ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
+     POSSIBILITY OF SUCH DAMAGE.
+
+     $FreeBSD$
+-->
+
+<chapter id="stylesheets">
+  <title>* Stylesheets</title>
+    
+  <para>SGML says nothing about how a document should be displayed to the
+    user, or rendered on paper.  To do that, various languages have been
+    developed to describe stylesheets, including DynaText, Panorama, SPICE,
+    JSSS, FOSI, CSS, and DSSSL.</para>
+  
+  <para>For DocBook, we are using stylesheets written in DSSSL.  For HTML we
+    are using CSS.</para>
+
+  <sect1 id="stylesheets-dsssl">
+    <title>* DSSSL</title>
+    
+    <para>The Documentation Project uses a slightly customized version of
+      Norm Walsh's modular DocBook stylesheets.</para>
+    
+    <para>These can be found in
+      <filename role="package">textproc/dsssl-docbook-modular</filename>.</para>
+
+    <para>The modified stylesheets are not in the ports system.  Instead they
+      are part of the Documentation Project source repository, and can be
+      found in <filename>doc/share/sgml/freebsd.dsl</filename>.  It is well
+      commented, and pending completion of this section you are encouraged to
+      examine that file to see how some of the available options in the
+      standard stylesheets have been configured in order to customize the
+      output for the FreeBSD Documentation Project.  That file also contains
+      examples showing how to extend the elements that the stylesheet
+      understands, which is how the FreeBSD specific elements have been
+      formatted.</para>
+  </sect1>
+
+  <sect1 id="stylesheets-css">
+    <title>CSS</title>
+
+    <para>Cascading Stylesheets (CSS) are a mechanism for attaching style
+      information (font, weight, size, color, and so forth) to elements in an
+      HTML document without abusing HTML to do so.</para>
+
+    <sect2>
+      <title>The Web site (HTML documents)</title>
+
+      <para>The FreeBSD web site does not currently use CSS.  Unfortunately,
+	the look and feel is constructed using abuses of HTML of varying
+	degrees.  This should be fixed, and would be a good project for
+	someone looking to contribute to the documentation project.</para>
+    </sect2>
+
+    <sect2>
+      <title>The DocBook documents</title>
+
+      <para>The FreeBSD DSSSL stylesheets include a reference to a stylesheet,
+	<filename>docbook.css</filename>, which is expected to appear in the
+	same directory as the HTML files.  The project-wide CSS file is copied
+	from <filename>doc/share/misc/docbook.css</filename> when documents
+	are converted to HTML, and is installed automatically.</para>
+    </sect2>
+  </sect1>
+</chapter>
+
+<!--
+     Local Variables:
+     mode: sgml
+     sgml-declaration: "../chapter.decl"
+     sgml-indent-data: t
+     sgml-omittag: nil
+     sgml-always-quote-attributes: t
+     sgml-parent-document: ("../book.sgml" "part" "chapter")
+     End:
+-->
diff --git a/zh_TW.Big5/books/fdp-primer/the-website/chapter.sgml b/zh_TW.Big5/books/fdp-primer/the-website/chapter.sgml
new file mode 100644
index 0000000000..f1f5ab7a7d
--- /dev/null
+++ b/zh_TW.Big5/books/fdp-primer/the-website/chapter.sgml
@@ -0,0 +1,207 @@
+<!-- Copyright (c) 1998, 1999 Nik Clayton, All rights reserved.
+
+     Redistribution and use in source (SGML DocBook) and 'compiled' forms
+     (SGML HTML, PDF, PostScript, RTF and so forth) with or without
+     modification, are permitted provided that the following conditions
+     are met:
+
+      1. Redistributions of source code (SGML DocBook) must retain the above
+         copyright notice, this list of conditions and the following
+         disclaimer as the first lines of this file unmodified.
+
+      2. Redistributions in compiled form (transformed to other DTDs,
+         converted to PDF, PostScript, RTF and other formats) must reproduce
+         the above copyright notice, this list of conditions and the
+         following disclaimer in the documentation and/or other materials
+         provided with the distribution.
+
+     THIS DOCUMENTATION IS PROVIDED BY NIK CLAYTON "AS IS" AND ANY EXPRESS OR
+     IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+     OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+     DISCLAIMED. IN NO EVENT SHALL NIK CLAYTON BE LIABLE FOR ANY DIRECT,
+     INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+     (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+     SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+     HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+     STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
+     ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
+     POSSIBILITY OF SUCH DAMAGE.
+
+     $FreeBSD$
+-->
+
+<chapter id="the-website">
+  <title>The Website</title>
+  
+  <sect1 id="the-website-prep">
+    <title>Preparation</title>
+    
+    <para>Get 200MB free disk space. You will need the disk space for the
+      SGML tools, a subset of the CVS tree, temporary build space and the
+      installed web pages. If you already have installed the SGML tools and
+      the CVS tree, you need only ~100MB free disk space.</para>
+    
+    <note>
+      <para>Make sure your documentation ports are up to date!  When in
+	doubt, remove the old ports using &man.pkg.delete.1; command before
+	installing the port.  For example, we currently depend on
+	jade-1.2 and if you have installed jade-1.1, please do:</para>
+
+      <screen>&prompt.root; <userinput>pkg_delete jade-1.1</userinput></screen>
+    </note>
+
+    <para>Set up a CVS repository. You need the directories www, doc and
+      ports in the CVS tree (plus the CVSROOT of course).  Please read the
+      <ulink url="&url.books.handbook;/synching.html#CVSUP">CVSup introduction</ulink>
+      on how to mirror a CVS tree or parts of a CVS tree.</para>
+    
+    <para>The essential cvsup collections are: <literal>www</literal>,
+      <literal>doc-all</literal>, <literal>cvs-base</literal>, and
+      <literal>ports-base</literal>.</para>
+    
+    <para>These collections require ~105MB free disk space.</para>
+    
+    <para>A full CVS tree - including <literal>src</literal>,
+      <literal>doc</literal>, <literal>www</literal>, and
+      <literal>ports</literal> - is currently 940MB.</para>
+  </sect1>
+  
+  <sect1 id="the-website-build">
+    <title>Build the web pages from scratch</title>
+    
+    <procedure> 
+      <step>
+	<para>Create and change directory into a build directory with at least 60MB of free
+	  space.</para>
+	
+	<screen>&prompt.root; <userinput>mkdir /var/tmp/webbuild</userinput>
+&prompt.root; <userinput>cd /var/tmp/webbuild</userinput></screen>
+      </step>
+
+      <step>
+	<para>Checkout the SGML files from the CVS tree.</para>
+	
+	<screen>&prompt.root; <userinput>cvs -R co www doc</userinput></screen>
+      </step>
+
+      <step>
+	<para>Change into the <filename role="directory">www/en</filename> directory, and run
+	  the &man.make.1; <maketarget>all</maketarget> target, to create
+	  the web pages.</para>
+	
+	<screen>&prompt.root; <userinput>cd en</userinput>
+&prompt.root; <userinput>make all</userinput></screen>
+      </step>
+    </procedure>
+  </sect1>
+  
+  <sect1 id="the-website-install">
+    <title>Install the web pages into your web server</title>
+    
+    <procedure>
+      <step>
+	<para>If you have moved out of the <filename>en</filename>
+	  directory, change back to it.</para>
+	
+	  <screen>&prompt.root; <userinput>cd <replaceable>path</replaceable>/www/en</userinput></screen>
+      </step>
+
+      <step>
+	<para>Run the &man.make.1; <maketarget>install</maketarget> target,
+	  setting the <makevar>DESTDIR</makevar> variable to the name of the 
+	  directory you want to install the files to.</para>
+	
+	<screen>&prompt.root; <userinput>make DESTDIR=<replaceable>/usr/local/www</replaceable> install</userinput></screen>
+      </step>
+
+      <step>
+	<para>If you have previously installed the web pages into the same
+	  directory the install process will not have deleted any old or
+	  outdated pages.  For example, if you build and install a new copy
+	  of the site every day, this command will find and delete all
+	  files that have not been updated in three days.</para>
+	
+	<screen>&prompt.root; <userinput>find <replaceable>/usr/local/www</replaceable> -ctime 3 -print0 | xargs -0 rm</userinput></screen>
+      </step>
+    </procedure>
+  </sect1>
+  
+  <sect1 id="the-website-env">
+    <title>Environment variables</title>
+    
+    <variablelist>
+      <varlistentry>
+	<term><envar>CVSROOT</envar></term>
+	
+	<listitem>
+	  <para>Location of the CVS tree. Essential.</para>
+	  
+	  <screen><userinput>&prompt.root; CVSROOT=/home/ncvs; export CVSROOT</userinput></screen>
+	</listitem>
+      </varlistentry>
+	
+      <varlistentry>
+	<term><makevar>ENGLISH_ONLY</makevar></term>
+	
+	<listitem>
+	  <para>If set and not empty, the makefiles will build and
+	    install only the English documents. All translations will be
+	    ignored. E.g.:</para>
+	  
+	  <screen>&prompt.root; <userinput>make ENGLISH_ONLY=YES all install</userinput></screen>
+
+	  <para>If you want to unset the variable
+	    <makevar>ENGLISH_ONLY</makevar> and build all pages, including
+	    translations, set the variable <makevar>ENGLISH_ONLY</makevar>
+	    to an empty value:</para>
+	  
+	  <screen>&prompt.root; <userinput>make ENGLISH_ONLY="" all install clean</userinput></screen>
+	</listitem>
+      </varlistentry>
+      
+      <varlistentry>
+	<term><makevar>WEB_ONLY</makevar></term>
+	
+	<listitem>
+	  <para>If set and not empty, the makefiles will build and install
+	    only the HTML pages from the www directory. All documents from
+	    the doc directory (Handbook, FAQ, Tutorials) will be ignored.
+	    E.g.:</para>
+	  
+	  <screen>&prompt.root; <userinput>make WEB_ONLY=YES all install</userinput></screen>
+	</listitem>
+      </varlistentry>
+	
+      <varlistentry>
+	<term><makevar>NOPORTSCVS</makevar></term>
+	
+	<listitem>
+	  <para>If set, the makefiles will not checkout files from the ports
+	    cvs repository. Instead, it will copy the files from
+	    <filename>/usr/ports</filename> (or where the variable
+	    <envar>PORTSBASE</envar> points to).</para>
+	</listitem>
+      </varlistentry>
+    </variablelist>
+    
+    <para><envar>CVSROOT</envar> is an environment variable. You must set it
+      on the command line or in your dot files (e.g., ~/.profile).</para>
+    
+    <para><makevar>WEB_ONLY</makevar>, <makevar>ENGLISH_ONLY</makevar> and
+      <makevar>NOPORTSCVS</makevar> are makefile variables. You can set the
+      variables in <filename>/etc/make.conf</filename>,
+      <filename>Makefile.inc</filename>, as environment variables on the
+      command line, or in your dot files.</para>
+  </sect1>
+</chapter>
+  
+<!--
+     Local Variables:
+     mode: sgml
+     sgml-declaration: "../chapter.decl"
+     sgml-indent-data: t
+     sgml-omittag: nil
+     sgml-always-quote-attributes: t
+     sgml-parent-document: ("../book.sgml" "part" "chapter")
+     End:
+-->
diff --git a/zh_TW.Big5/books/fdp-primer/tools/chapter.sgml b/zh_TW.Big5/books/fdp-primer/tools/chapter.sgml
new file mode 100644
index 0000000000..2b1275d1af
--- /dev/null
+++ b/zh_TW.Big5/books/fdp-primer/tools/chapter.sgml
@@ -0,0 +1,276 @@
+<!-- Copyright (c) 1998, 1999 Nik Clayton, All rights reserved.
+
+     Redistribution and use in source (SGML DocBook) and 'compiled' forms
+     (SGML, HTML, PDF, PostScript, RTF and so forth) with or without
+     modification, are permitted provided that the following conditions
+     are met:
+
+      1. Redistributions of source code (SGML DocBook) must retain the above
+         copyright notice, this list of conditions and the following
+         disclaimer as the first lines of this file unmodified.
+
+      2. Redistributions in compiled form (transformed to other DTDs,
+         converted to PDF, PostScript, RTF and other formats) must reproduce
+         the above copyright notice, this list of conditions and the
+         following disclaimer in the documentation and/or other materials
+         provided with the distribution.
+
+     THIS DOCUMENTATION IS PROVIDED BY NIK CLAYTON "AS IS" AND ANY EXPRESS OR
+     IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+     OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+     DISCLAIMED. IN NO EVENT SHALL NIK CLAYTON BE LIABLE FOR ANY DIRECT,
+     INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+     (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+     SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+     HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+     STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
+     ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
+     POSSIBILITY OF SUCH DAMAGE.
+
+     Sync with en_US.ISO8859-1 v1.32
+     $FreeBSD$
+-->
+
+<chapter id="tools">
+  <title>¤u¨ã</title>
+  
+  <para>FDP ¨Ï¥Î¤@°ï¤u¨ã¨Ó¨ó§UºÞ²z FreeBSD ¤å¥ó¡BÂà´«¤å¥ó®æ¦¡µ¥µ¥¡C
+	¦]¦¹¡A­Y­n¶i¦æ FDP ¤u§@ªº¸Ü¡A¥i¯à¥²¶·­n¾Ç·|³o¨Ç¤u¨ã¤~¦æ¡C</para>                    
+
+  <para>³o¨Ç¤u¨ã³£¥i¥H¥Î Ports ©Î Packages ¨Ó¦w¸Ë¡A¥H¸`¬Ù³\¦h¦w¸Ëªº¤u¤Ò¡C</para>                                                              
+  
+  <para>±z¥²¶·¦w¸Ë³o¨Ç¤u¨ã¡A¤~¯à¨Ï¥Î±µ¤U¨Ó¦U³¹¸`·|¤¶²Ð¨ìªº¨Ò¤l¡C ³o¨Ç¤u¨ãªº¥Îªk¡A·|¦b«áÄò¬ÛÃö³¹¸`½Í¨ì¡C </para>     
+
+  <tip>
+    <title>Use <filename role="package">textproc/docproj</filename> if possible</title>
+
+    <para>You can save yourself a lot of time if you install the
+      <filename role="package">textproc/docproj</filename> port.  This is a
+      <emphasis>meta-port</emphasis> which does not contain any software
+      itself.  Instead, it depends on various other ports being installed
+      correctly.  Installing this port <emphasis>should</emphasis>
+      automatically download and install all of the packages listed in this
+      chapter that you need.</para>
+
+    <para>One of the packages that you might need is the JadeTeX macro set.
+      In turn, this macro set requires &tex; to be installed.  &tex; is a large
+      package, and you only need it if you want to produce Postscript or PDF
+      output.</para>
+
+    <para>To save yourself time and space you must specify whether or not you
+      want JadeTeX (and therefore &tex;) installed when you install this port.
+      Either do:</para>
+
+      <screen>&prompt.root; <userinput>make JADETEX=yes install</userinput></screen>
+
+    <para>or</para>
+
+      <screen>&prompt.root; <userinput>make JADETEX=no install</userinput></screen>
+
+    <para>as necessary.  Alternatively you may install <filename
+      role="package">textproc/docproj-jadetex</filename> or <filename
+      role="package">textproc/docproj-nojadetex</filename>.  These slave ports
+      define the <makevar>JADETEX</makevar> variable for you, therefore they
+      will install the same suite of applications on your machine.
+      Note that you can produce only HTML or ASCII
+      text output if you do not install <application>JadeTeX</application>.
+      PostScript or PDF output require &tex;.</para>
+  </tip>
+
+  <sect1 id="tools-mandatory">
+    <title>¥²³Æ¤u¨ã</title>
+
+    <sect2>
+      <title>³nÅé</title>
+      
+      <para>These programs are required before you can usefully work with the
+	FreeBSD documentation, and they will allow you to convert the
+	documentation to HTML, plain text, and RTF formats.  They are all
+	included in <filename role="package">textproc/docproj</filename>.</para>
+      
+      <variablelist>
+	<varlistentry>
+	  <term><application>Jade</application>
+	    (<filename role="package">textproc/jade</filename>)</term>
+	  
+	  <listitem>
+	    <para>A DSSSL implementation.  Used for converting marked up
+	      documents to other formats, including HTML and &tex;.</para>
+	  </listitem>
+	</varlistentry>
+	
+	<varlistentry>
+	  <term><application>Tidy</application>
+	    (<filename role="package">www/tidy</filename>)</term>
+	  
+	  <listitem>
+	    <para>An HTML <quote>pretty printer</quote>, used to reformat some of the
+	      automatically generated HTML so that it is easier to
+	      follow.</para>
+	  </listitem>
+	</varlistentry>
+	
+	<varlistentry>
+	  <term><application>Links</application>
+	    (<filename role="package">www/links</filename>)</term>
+	  
+	  <listitem>
+	    <para>A text-mode WWW browser that can also convert
+	      HTML files to plain text.</para>
+	  </listitem>
+	</varlistentry>
+
+	<varlistentry>
+	  <term><application>peps</application>
+	    (<filename role="package">graphics/peps</filename>)</term>
+	  
+	  <listitem>
+	    <para>Some of the documentation includes images, some of which are
+	      stored as EPS files.  These must be converted to PNG before most
+	      web browsers will display them.</para>
+	  </listitem>
+	</varlistentry>
+      </variablelist>
+    </sect2>
+
+    <sect2>
+      <title>DTDs ¤Î Entities</title>
+
+      <para>These are the DTDs and entity sets used by the FDP.  They need to
+	be installed before you can work with any of the documentation.</para>
+      
+      <variablelist>
+	<varlistentry>
+	  <term>HTML DTD (<filename role="package">textproc/html</filename>)</term>
+	  
+	  <listitem>
+	    <para>HTML is the markup language of choice for the World Wide
+	      Web, and is used throughout the FreeBSD web site.</para>
+	  </listitem>
+	</varlistentry>
+	
+	<varlistentry>
+	  <term>DocBook DTD (<filename role="package">textproc/docbook</filename>)</term>
+	  
+	  <listitem>
+	    <para>DocBook is designed for marking up technical documentation.
+	      All the FreeBSD documentation is written in DocBook.</para>
+	  </listitem>
+	</varlistentry>
+	
+	<varlistentry>
+	  <term>ISO 8879 entities
+	    (<filename role="package">textproc/iso8879</filename>)</term>
+	  
+	  <listitem>
+	    <para>19 of the ISO 8879:1986 character entity sets used by many
+	      DTDs.  Includes named mathematical symbols, additional
+	      characters in the Latin character set (accents, diacriticals,
+	      and so on), and Greek symbols.</para>
+	  </listitem>
+	</varlistentry>
+      </variablelist>
+    </sect2>
+
+    <sect2>
+      <title>¼Ë¦¡ªí(Stylesheets)</title>
+
+      <para>The stylesheets are used when converting and formatting the
+	documentation for display on screen, printing, and so on.</para>
+      
+      <variablelist>
+	<varlistentry>
+	  <term>Modular DocBook Stylesheets
+	    (<filename role="package">textproc/dsssl-docbook-modular</filename>)</term>
+	  
+	  <listitem>
+	    <para>The Modular DocBook Stylesheets are used when converting
+	      documentation marked up in DocBook to other formats, such as
+	      HTML or RTF.</para>
+	  </listitem>
+	</varlistentry>
+      </variablelist>
+    </sect2>
+  </sect1>
+
+  <sect1 id="tools-optional">
+    <title>Optional tools</title>
+
+    <para>You do not need to have any of the following installed.  However,
+      you may find it easier to work with the documentation if you do, and
+      they may give you more flexibility in the output formats that can be
+      generated.</para>
+
+    <sect2>
+      <title>Software</title>
+      
+      <variablelist>
+	<varlistentry>
+	  <term><application>JadeTeX</application> and
+	    <application>teTeX</application>
+	    (<filename role="package">print/jadetex</filename> and
+	    <filename role="package">print/teTeX</filename>)</term>
+	  
+	  <listitem>
+	    <para><application>Jade</application> and
+	      <application>teTeX</application> are used to convert DocBook
+	      documents to DVI, Postscript, and PDF formats.  The
+	      <application>JadeTeX</application> macros are needed in order to
+	      do this.</para>
+
+	    <para>If you do not intend to convert your documentation to one of
+	      these formats (i.e., HTML, plain text, and RTF are sufficient)
+	      then you do not need to install
+	      <application>JadeTeX</application> and
+	      <application>teTeX</application>.  This can be a significant
+	      space and time saver, as <application>teTeX</application> is
+	      over 30MB in size.</para>
+
+	    <important>
+	      <para>If you decide to install
+		<application>JadeTeX</application> and
+		<application>teTeX</application> then you will need to
+		configure <application>teTeX</application> after
+		<application>JadeTeX</application> has been installed.
+		<filename>print/jadetex/pkg-message</filename> contains
+		detailed instructions explaining what you need to do.</para>
+	    </important>
+	  </listitem>
+	</varlistentry>
+	
+	<varlistentry>
+	  <term><application>Emacs</application> or
+	    <application>XEmacs</application> 
+	    (<filename role="package">editors/emacs</filename> or
+	    <filename role="package">editors/xemacs</filename>)</term>
+	  
+	  <listitem>
+	    <para>Both these editors include a special mode for editing
+	      documents marked up according to an SGML DTD.  This mode
+	      includes commands to reduce the amount of typing you need, and
+	      help reduce the possibility of errors.</para>
+
+	    <para>You do not need to use them; any text editor can be used to
+	      edit marked up documents.  You may find they make you more
+	      efficient.</para>
+	  </listitem>
+	</varlistentry>
+      </variablelist>
+      
+      <para>If anyone has recommendations for other software that is useful
+	when manipulating SGML documents, please let &a.doceng; know, so they
+	can be added to this list.</para>
+    </sect2>
+  </sect1>
+</chapter>
+
+<!--
+     Local Variables:
+     mode: sgml
+     sgml-declaration: "../chapter.decl"
+     sgml-indent-data: t
+     sgml-omittag: nil
+     sgml-always-quote-attributes: t
+     sgml-parent-document: ("../book.sgml" "part" "chapter")
+     End:
+-->
diff --git a/zh_TW.Big5/books/fdp-primer/translations/chapter.sgml b/zh_TW.Big5/books/fdp-primer/translations/chapter.sgml
new file mode 100644
index 0000000000..bc31238a92
--- /dev/null
+++ b/zh_TW.Big5/books/fdp-primer/translations/chapter.sgml
@@ -0,0 +1,458 @@
+<!-- Copyright (c) 1999 Nik Clayton, All rights reserved.
+
+     Redistribution and use in source (SGML DocBook) and 'compiled' forms
+     (SGML HTML, PDF, PostScript, RTF and so forth) with or without
+     modification, are permitted provided that the following conditions
+     are met:
+
+      1. Redistributions of source code (SGML DocBook) must retain the above
+         copyright notice, this list of conditions and the following
+         disclaimer as the first lines of this file unmodified.
+
+      2. Redistributions in compiled form (transformed to other DTDs,
+         converted to PDF, PostScript, RTF and other formats) must reproduce
+         the above copyright notice, this list of conditions and the
+         following disclaimer in the documentation and/or other materials
+         provided with the distribution.
+
+     THIS DOCUMENTATION IS PROVIDED BY NIK CLAYTON "AS IS" AND ANY EXPRESS OR
+     IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+     OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+     DISCLAIMED. IN NO EVENT SHALL NIK CLAYTON BE LIABLE FOR ANY DIRECT,
+     INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+     (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+     SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+     HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+     STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
+     ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
+     POSSIBILITY OF SUCH DAMAGE.
+
+     Sync with en_US.ISO8859-1 v1.29
+     $FreeBSD$
+-->
+
+<chapter id="translations">
+  <title>Translations</title>
+
+  <para>This is the FAQ for people translating the FreeBSD documentation
+    (FAQ, Handbook, tutorials, manual pages, and others) to different
+    languages.</para>
+  
+  <para>It is <emphasis>very</emphasis> heavily based on the translation FAQ
+    from the FreeBSD German Documentation Project, originally written by Frank
+    Gr&uuml;nder <email>elwood@mc5sys.in-berlin.de</email> and translated back to
+    English by Bernd Warken <email>bwarken@mayn.de</email>.</para>
+
+  <para>The FAQ is maintained by the &a.doceng;.</para>
+
+  <qandaset>
+    <qandaentry>
+      <question>
+	<para>Why a FAQ?</para>
+      </question>
+
+      <answer>
+	<para>More and more people are approaching the freebsd-doc mailing
+	  list and volunteering to translate FreeBSD documentation to other
+	  languages. This FAQ aims to answer their questions so they can start
+	  translating documentation as quickly as possible.</para>
+      </answer>
+    </qandaentry>
+
+    <qandaentry>
+      <question>
+	<para>What do <phrase>i18n</phrase> and <phrase>l10n</phrase>
+	  mean?</para>
+      </question>
+      
+      <answer>
+	<para><phrase>i18n</phrase> means
+	  <phrase>internationalization</phrase> and <phrase>l10n</phrase>
+	  means <phrase>localization</phrase>. They are just a convenient
+	  shorthand.</para>
+
+	<para><phrase>i18n</phrase> can be read as <quote>i</quote> followed by
+	  18 letters, followed by <quote>n</quote>. Similarly,
+	  <phrase>l10n</phrase> is <quote>l</quote> followed by 10 letters,
+	  followed by <quote>n</quote>.</para>
+      </answer>
+    </qandaentry>
+
+    <qandaentry>
+      <question>
+	<para>Is there a mailing list for translators?</para>
+      </question>
+
+      <answer>
+	<para>Yes.  Different translation groups have their own mailing
+          lists.  The <ulink url="http://www.freebsd.org/docproj/translations.html">list
+            of translation projects</ulink> has more information about the
+          mailing lists and web sites run by each translation project.</para>
+      </answer>
+    </qandaentry>
+
+    <qandaentry>
+      <question>
+	<para>Are more translators needed?</para>
+      </question>
+
+      <answer>
+	<para>Yes. The more people work on translation the faster it gets
+	  done, and the faster changes to the English documentation are
+	  mirrored in the translated documents.</para>
+
+	<para>You do not have to be a professional translator to be able to
+	  help.</para>
+      </answer>
+    </qandaentry>
+
+    <qandaentry>
+      <question>
+	<para>What languages do I need to know?</para>
+      </question>
+
+      <answer>
+	<para>Ideally, you will have a good knowledge of written English, and
+	  obviously you will need to be fluent in the language you are
+	  translating to.</para>
+
+	<para>English is not strictly necessary. For example, you could do a
+	  Hungarian translation of the FAQ from the Spanish
+	  translation.</para>
+      </answer>
+    </qandaentry>
+    
+    <qandaentry>
+      <question>
+	<para>What software do I need to know?</para>
+      </question>
+
+      <answer>
+	<para>It is strongly recommended that you maintain a local copy of the
+	  FreeBSD CVS repository (at least the documentation part) either
+	  using <application>CTM</application> or
+	  <application>CVSup</application>. The "Staying current with FreeBSD"
+	  chapter in the Handbook explains how to use these
+	  applications.</para>
+
+	<para>You should be comfortable using <application>CVS</application>.
+	  This will allow you to see what has changed between different
+	  versions of the files that make up the documentation.</para>
+
+	<para>[XXX To Do -- write a tutorial that shows how to use CVSup to
+	  get just the documentation, check it out, and see what has changed
+	  between two arbitrary revisions]</para>
+      </answer>
+    </qandaentry>
+
+    <qandaentry>
+      <question>
+	<para>How do I find out who else might be translating to the same
+	  language?</para>
+      </question>
+
+      <answer>
+	<para>The <ulink
+	    url="http://www.FreeBSD.org/docproj/translations.html">Documentation
+	    Project translations page</ulink> lists the translation efforts
+	  that are currently known about. If others are already working
+	  on translating documentation to your language, please do not
+	  duplicate their efforts. Instead, contact them to see how you can
+	  help.</para>
+
+	<para>If no one is listed on that page as translating for your
+	  language, then send a message to the &a.doc; in case someone else
+	  is thinking of doing a translation, but has not announced it yet.
+	  </para>
+      </answer>
+    </qandaentry>
+      
+    <qandaentry>
+      <question>
+	<para>No one else is translating to my language.  What do I do?</para>
+      </question>
+
+      <answer>
+	<para>Congratulations, you have just started the <quote>FreeBSD
+	  <replaceable>your-language-here</replaceable> Documentation
+          Translation Project</quote>. Welcome aboard.</para>
+
+	<para>First, decide whether or not you have got the time to spare. Since
+	  you are the only person working on your language at the moment it is
+	  going to be your responsibility to publicize your work and
+	  coordinate any volunteers that might want to help you.</para>
+
+	<para>Write an email to the Documentation Project mailing list,
+	  announcing that you are going to translate the documentation, so the
+	  Documentation Project translations page can be maintained.</para>
+
+	<para>If there is already someone in your country providing FreeBSD
+	  mirroring services you should contact them and ask if you can
+	  have some webspace for your project, and possibly an email
+	  address or mailing list services.</para>
+	
+	<para>Then pick a document and start translating. It is best to start
+	  with something fairly small&mdash;either the FAQ, or one of the
+	  tutorials.</para>
+      </answer>
+    </qandaentry>
+
+    <qandaentry>
+      <question>
+	<para>I have translated some documentation, where do I send it?</para>
+      </question>
+
+      <answer>
+	<para>That depends. If you are already working with a translation team
+	  (such as the Japanese team, or the German team) then they will have
+	  their own procedures for handling submitted documentation, and these
+	  will be outlined on their web pages.</para>
+
+	<para>If you are the only person working on a particular language (or
+	  you are responsible for a translation project and want to submit
+	  your changes back to the FreeBSD project) then you should send your
+	  translation to the FreeBSD project (see the next question).</para>
+      </answer>
+    </qandaentry>
+
+    <qandaentry>
+      <question>
+	<para>I am the only person working on translating to this language, how
+	  do I submit my translation?</para>
+
+	<para>or</para>
+
+	<para>We are a translation team, and want to submit documentation that
+	  our members have translated for us?</para>
+      </question>
+
+      <answer>
+	<para>First, make sure your translation is organized properly. This
+	  means that it should drop into the existing documentation tree and
+	  build straight away.</para>
+
+	<para>Currently, the FreeBSD documentation is stored in a top level
+	  directory called <filename>doc/</filename>. Directories below this
+	  are named according to the language code they are written in, as
+	  defined in ISO639 (<filename>/usr/share/misc/iso639</filename> on a
+	  version of FreeBSD newer than 20th January 1999).</para>
+
+	<para>If your language can be encoded in different ways (for example,
+	  Chinese) then there should be directories below this, one for each
+	  encoding format you have provided.</para>
+
+	<para>Finally, you should have directories for each document.</para>
+
+	<para>For example, a hypothetical Swedish translation might look
+	  like:</para>
+
+	<programlisting>doc/
+    sv_SE.ISO8859-1/
+                     Makefile 
+                     books/
+                           faq/
+                               Makefile
+                               book.sgml</programlisting>
+
+	<para><literal>sv_SE.ISO8859-1</literal> is the name of the
+	  translation, in
+	  <filename><replaceable>lang</replaceable>.<replaceable>encoding</replaceable></filename>
+	  form.  Note the
+	  two Makefiles, which will be used to build the documentation.</para>
+
+	<para>Use &man.tar.1; and &man.gzip.1; to compress up your
+	  documentation, and send it to the project.</para>
+
+	<screen>&prompt.user; <userinput>cd doc</userinput>
+&prompt.user; <userinput>tar cf swedish-docs.tar sv</userinput>
+&prompt.user; <userinput>gzip -9 swedish-docs.tar</userinput></screen>
+
+	<para>Put <filename>swedish-docs.tar.gz</filename> somewhere.  If you
+	  do not have access to your own webspace (perhaps your ISP does not
+	  let you have any) then you can email &a.doceng;, and arrange to email
+	  the files when it is convenient.</para>
+
+	<para>Either way, you should use &man.send-pr.1; to submit a report
+	  indicating that you have submitted the documentation. It would be
+	  very helpful if you could get other people to look over your
+	  translation and double check it first, since it is unlikely that the
+	  person committing it will be fluent in the language.</para>
+
+	<para>Someone (probably the Documentation Project Manager, currently
+	  &a.doceng;) will then take your translation and confirm that it builds.
+	  In particular, the following things will be looked at:</para>
+
+	<orderedlist>
+	  <listitem>
+	    <para>Do all your files use RCS strings (such as "ID")?</para>
+	  </listitem>
+
+	  <listitem>
+	    <para>Does <command>make all</command> in the
+	      <filename>sv_SE.ISO8859-1</filename> directory work correctly?</para>
+	  </listitem>
+	  
+	  <listitem>
+	    <para>Does <command>make install</command> work correctly?</para>
+	  </listitem>
+        </orderedlist>
+	  
+	<para>If there are any problems then whoever is looking at the
+	  submission will get back to you to work them out.</para>
+
+	<para>If there are no problems your translation will be committed
+	  as soon as possible.</para>
+      </answer>
+    </qandaentry>
+
+    <qandaentry>
+      <question>
+	<para>Can I include language or country specific text in my
+	  translation?</para>
+      </question>
+
+      <answer>
+	<para>We would prefer that you did not.</para>
+
+	<para>For example, suppose that you are translating the Handbook to
+	  Korean, and want to include a section about retailers in Korea in
+	  your Handbook.</para>
+
+	<para>There is no real reason why that information should not be in the
+	  English (or German, or Spanish, or Japanese, or &hellip;) versions
+	  as well. It is feasible that an English speaker in Korea might try
+	  and pick up a copy of FreeBSD whilst over there. It also helps
+	  increase FreeBSD's perceived presence around the globe, which is not
+	  a bad thing.</para>
+
+	<para>If you have country specific information, please submit it as a
+	  change to the English Handbook (using &man.send-pr.1;) and then
+	  translate the change back to your language in the translated
+	  Handbook.</para>
+
+	<para>Thanks.</para>
+      </answer>
+    </qandaentry>
+
+    <qandaentry>
+      <question>
+	<para>How should language specific characters be included?</para>
+      </question>
+
+      <answer>
+	<para>Non-ASCII characters in the documentation should be included
+	  using SGML entities.</para>
+
+	<para>Briefly, these look like an ampersand (&amp;), the name of the
+	  entity, and a semi-colon (;).</para>
+
+	<para>The entity names are defined in ISO8879, which is in the ports
+	  tree as <filename role="package">textproc/iso8879</filename>.</para>
+
+	<para>A few examples include:</para>
+
+	<segmentedlist>
+          <segtitle>Entity</segtitle>
+
+          <segtitle>Appearance</segtitle>
+
+          <segtitle>Description</segtitle>
+
+	  <seglistitem>
+	    <seg>&amp;eacute;</seg>
+	    <seg>&eacute;</seg>
+	    <seg>Small <quote>e</quote> with an acute accent</seg>
+	  </seglistitem>
+
+	  <seglistitem>
+	    <seg>&amp;Eacute;</seg>
+	    <seg>&Eacute;</seg>
+	    <seg>Large <quote>E</quote> with an acute accent</seg>
+	  </seglistitem>
+
+	  <seglistitem>
+	    <seg>&amp;uuml;</seg>
+	    <seg>&uuml;</seg>
+	    <seg>Small <quote>u</quote> with an umlaut</seg>
+	  </seglistitem>
+	</segmentedlist>
+
+	<para>After you have installed the iso8879 port, the files in
+	  <filename>/usr/local/share/sgml/iso8879</filename> contain the
+	  complete list.</para>
+      </answer>
+    </qandaentry>
+
+    <qandaentry>
+      <question>
+	<para>Addressing the reader</para>
+      </question>
+
+      <answer>
+	<para>In the English documents, the reader is addressed as
+	  <quote>you</quote>, there is no formal/informal distinction as there
+	  is in some languages.</para>
+
+	<para>If you are translating to a language which does distinguish, use
+	  whichever form is typically used in other technical documentation in
+	  your language. If in doubt, use a mildly polite form.</para>
+      </answer>
+    </qandaentry>
+
+    <qandaentry>
+      <question>
+	<para>Do I need to include any additional information in my
+	  translations?</para>
+      </question>
+
+      <answer>
+	<para>Yes.</para>
+
+	<para>The header of the English version of each document will look
+	  something like this:</para>
+
+	<programlisting>&lt;!--
+     The FreeBSD Documentation Project
+
+     &dollar;FreeBSD: doc/en_US.ISO8859-1/books/fdp-primer/translations/chapter.sgml,v 1.5 2000/07/07 18:38:38 dannyboy Exp &dollar;
+--&gt;</programlisting>
+
+	<para>The exact boilerplate may change, but it will always include a
+	  &dollar;FreeBSD&dollar; line and the phrase <literal>The FreeBSD Documentation
+	    Project</literal>.
+	  Note that the &dollar;FreeBSD part is expanded automatically by
+	  CVS, so it should be empty (just
+	  <literal>&dollar;FreeBSD&dollar;</literal>) for new files.</para>
+
+	<para>Your translated documents should include their own
+	  &dollar;FreeBSD&dollar; line, and change the
+	  <literal>FreeBSD Documentation Project</literal> line to
+	  <literal>The FreeBSD <replaceable>language</replaceable>
+	    Documentation Project</literal>.</para>
+
+	<para>In addition, you should add a third line which indicates which
+	  revision of the English text this is based on.</para>
+	
+	<para>So, the Spanish version of this file might start:</para>
+
+	<programlisting>&lt;!--
+     The FreeBSD Spanish Documentation Project
+
+     &dollar;FreeBSD: doc/es_ES.ISO8859-1/books/fdp-primer/translations/chapter.sgml,v 1.3 1999/06/24 19:12:32 jesusr Exp &dollar;
+     Original revision: 1.11
+--&gt;</programlisting>
+      </answer>
+    </qandaentry>
+  </qandaset>
+</chapter>
+
+<!--
+     Local Variables:
+     mode: sgml
+     sgml-declaration: "../chapter.decl"
+     sgml-indent-data: t
+     sgml-omittag: nil
+     sgml-always-quote-attributes: t
+     sgml-parent-document: ("../book.sgml" "part" "chapter")
+     End:
+-->
diff --git a/zh_TW.Big5/books/fdp-primer/writing-style/chapter.sgml b/zh_TW.Big5/books/fdp-primer/writing-style/chapter.sgml
new file mode 100644
index 0000000000..af0e4c0572
--- /dev/null
+++ b/zh_TW.Big5/books/fdp-primer/writing-style/chapter.sgml
@@ -0,0 +1,489 @@
+<!-- Copyright (c) 1998 Nik Clayton, All rights reserved.
+
+     Redistribution and use in source (SGML DocBook) and 'compiled' forms
+     (SGML HTML, PDF, PostScript, RTF and so forth) with or without
+     modification, are permitted provided that the following conditions
+     are met:
+
+      1. Redistributions of source code (SGML DocBook) must retain the above
+         copyright notice, this list of conditions and the following
+         disclaimer as the first lines of this file unmodified.
+
+      2. Redistributions in compiled form (transformed to other DTDs,
+         converted to PDF, PostScript, RTF and other formats) must reproduce
+         the above copyright notice, this list of conditions and the
+         following disclaimer in the documentation and/or other materials
+         provided with the distribution.
+
+     THIS DOCUMENTATION IS PROVIDED BY NIK CLAYTON "AS IS" AND ANY EXPRESS OR
+     IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+     OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+     DISCLAIMED. IN NO EVENT SHALL NIK CLAYTON BE LIABLE FOR ANY DIRECT,
+     INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+     (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+     SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+     HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+     STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
+     ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
+     POSSIBILITY OF SUCH DAMAGE.
+
+     Sync with en_US.ISO8859-1 v1.48
+     $FreeBSD$
+-->
+
+<chapter id="writing-style">
+  <title>¤å¥óªº¼¶¼g­·®æ</title>
+  
+  <para>In order to promote consistency between the myriad authors of the
+    FreeBSD documentation, some guidelines have been drawn up for authors to
+    follow.</para>
+  
+  <variablelist>
+    <varlistentry>
+      <term>Use American English spelling</term>
+
+      <listitem>
+	<para>There are several variants of English, with different spellings
+	  for the same word.  Where spellings differ, use the American English
+	  variant. <quote>color</quote>, not <quote>colour</quote>,
+	  <quote>rationalize</quote>, not <quote>rationalise</quote>, and so
+	  on.</para>
+
+	<note>
+	  <para>The use of British English may be accepted in the case
+	    of a contributed article, however the spelling must be
+	    consistent within the whole document.  The other documents
+	    such as books, web site, manual pages, etc. will have to use
+	    American English.</para>
+	</note>
+      </listitem>
+    </varlistentry>
+
+    <varlistentry>
+      <term>Do not use contractions</term>
+      
+      <listitem>
+	<para>Do not use contractions.  Always spell the phrase out in full.
+	  <quote>Don't use contractions</quote> would be wrong.</para>
+
+	<para>Avoiding contractions makes for a more formal tone, is more
+	  precise, and is slightly easier for translators.</para>
+      </listitem>
+    </varlistentry>
+    
+    <varlistentry>
+      <term>Use the serial comma</term>
+      
+      <listitem>
+	<para>In a list of items within a paragraph, separate each item from
+	  the others with a comma.  Separate the last item from the others with
+	  a comma and the word <quote>and</quote>.</para>
+
+	<para>For example, look at the following:</para>
+	
+	<blockquote>
+	  <para>This is a list of one, two and three items.</para>
+	</blockquote>
+	
+	<para>Is this a list of three items, <quote>one</quote>,
+	  <quote>two</quote>, and <quote>three</quote>, or a list of two items,
+	  <quote>one</quote> and <quote>two and three</quote>?</para>
+	
+	<para>It is better to be explicit and include a serial comma:</para>
+	
+	<blockquote>
+	  <para>This is a list of one, two, and three items.</para>
+	</blockquote>
+      </listitem>
+    </varlistentry>
+    
+    <varlistentry>
+      <term>Avoid redundant phrases</term>
+      
+      <listitem>
+	<para>Try not to use redundant phrases.  In particular, <quote>the
+	  command</quote>, <quote>the file</quote>, and <quote>man
+	  command</quote> are probably redundant.</para>
+
+	<para>These two examples show this for commands.  The second example
+	  is preferred.</para>
+	
+	<informalexample>
+	  <para>Use the command <command>cvsup</command> to update your
+	    sources.</para>
+	</informalexample>
+      
+	<informalexample>
+	  <para>Use <command>cvsup</command> to update your sources.</para>
+	</informalexample>
+	
+	<para>These two examples show this for filenames.  The second example
+	  is preferred.</para>
+	
+	<informalexample>
+	  <para>&hellip; in the filename
+	    <filename>/etc/rc.local</filename>&hellip;</para>
+	</informalexample>
+	
+	<informalexample>
+	  <para>&hellip; in
+	    <filename>/etc/rc.local</filename>&hellip;</para>
+	</informalexample>
+	
+	<para>These two examples show this for manual references.  The second
+	  example is preferred (the second example uses
+	  <sgmltag>citerefentry</sgmltag>).</para>
+	
+	<informalexample>
+	  <para>See <command>man csh</command> for more
+	    information.</para>
+	</informalexample>
+	
+	<informalexample>
+	  <para>See &man.csh.1;.</para>
+	</informalexample>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term>Two spaces at the end of sentences</term>
+
+      <listitem>
+	<para>Always use two spaces at the end of sentences, as this
+	  improves readability, and eases use of tools such as
+	  <application>Emacs</application>.</para>
+
+	<para>While it may be argued that a capital letter following
+	  a period denotes a new sentence, this is not the case, especially
+	  in name usage.  <quote>Jordan K. Hubbard</quote> is a good
+	  example; it has a capital <literal>H</literal> following a
+	  period and a space, and there certainly is not a new sentence
+	  there.</para>
+      </listitem>
+    </varlistentry>
+  </variablelist>
+
+  <para>For more information about writing style, see <ulink
+      url="http://www.bartleby.com/141/">Elements of
+      Style</ulink>, by William Strunk.</para>
+
+  <sect1 id="writing-style-guide">
+    <title>Style guide</title>
+
+    <para>To keep the source for the Handbook consistent when many different
+      people are editing it, please follow these style conventions.</para>
+
+    <sect2>
+      <title>Letter case</title>
+
+      <para>Tags are entered in lower case, <literal>&lt;para&gt;</literal>,
+	<emphasis>not</emphasis> <literal>&lt;PARA&gt;</literal>.</para>
+
+      <para>Text that appears in SGML contexts is generally written in upper
+	case, <literal>&lt!ENTITY&hellip;&gt;</literal>, and
+	<literal>&lt;!DOCTYPE&hellip;&gt;</literal>, <emphasis>not</emphasis>
+	<literal>&lt;!entity&hellip;&gt;</literal> and
+	<literal>&lt;!doctype&hellip;&gt;</literal>.</para>
+    </sect2>
+
+    <sect2>
+      <title>Acronyms</title>
+
+      <para>Acronyms should generally be spelled out the first time
+	they appear in a book, as in: "Network Time Protocol (<acronym
+	role="Network Time Protocol">NTP</acronym>)." After the
+	acronym has been defined, you should generally use the acronym
+	only (not the whole term, unless it makes more sense
+	contextually to use the whole term). Usually, acronyms are
+	defined only one per book. But if you prefer, you can also
+	define them the first time they appear in each chapter.</para>
+
+      <para>The first three uses of an acronym should be enclosed in
+        &lt;acronym&gt; tags, with a <literal>role</literal> attribute
+        with the full term defined.  This allows a link to the
+        glossary to be created, and for mouseovers to be rendered with
+        the fully expanded term.</para>
+    </sect2>
+
+    <sect2>
+      <title>Indentation</title>
+
+      <para>Each file starts with indentation set at column 0,
+	<emphasis>regardless</emphasis> of the indentation level of the file
+	which might contain this one.</para>
+
+      <para>Opening tags increase the indentation level by 2 spaces.
+	Closing tags decrease the indentation level by 2 spaces.  Blocks
+	of 8 spaces at the start of a line should be replaced with a tab.
+	Do not use
+	spaces in front of tabs, and do not add extraneous whitespace at the
+	end of a line.  Content
+	within elements should be indented by two spaces if the content runs
+	over more than one line.</para>
+
+      <para>For example, the source for this section looks something
+	like:</para>
+
+      <programlisting><![ CDATA [+--- This is column 0
+V
+<chapter>
+  <title>...</title>
+
+  <sect1>
+    <title>...</title>
+
+    <sect2>
+      <title>Indentation</title>
+
+      <para>Each file starts with indentation set at column 0,
+        <emphasis>regardless</emphasis> of the indentation level of the file
+        which might contain this one.</para>
+
+      ...	
+    </sect2>
+  </sect1>
+</chapter>]]></programlisting>
+
+      <para>If you use <application>Emacs</application> or
+	<application>XEmacs</application> to edit the files then
+	<literal>sgml-mode</literal> should be loaded automatically, and the
+	<application>Emacs</application> local variables at the bottom of each file should enforce these
+	styles.</para>
+
+      <para><application>Vim</application> users might want to configure
+	their editor with:</para>
+
+      <programlisting>augroup sgmledit
+  autocmd FileType sgml set formatoptions=cq2l " Special formatting options
+  autocmd FileType sgml set textwidth=70       " Wrap lines at 70 columns
+  autocmd FileType sgml set shiftwidth=2       " Automatically indent
+  autocmd FileType sgml set softtabstop=2      " Tab key indents 2 spaces
+  autocmd FileType sgml set tabstop=8          " Replace 8 spaces with a tab
+  autocmd FileType sgml set autoindent         " Automatic indentation
+augroup END</programlisting>
+
+    </sect2>
+
+    <sect2>
+      <title>Tag style</title>
+
+      <sect3>
+	<title>Tag spacing</title>
+	
+	<para>Tags that start at the same indent as a previous tag
+	  should be separated by a blank line, and those that are not
+	  at the same indent as a previous tag should not:</para>
+
+	<informalexample>
+	  <programlisting><![ CDATA [<article>
+  <articleinfo>
+    <title>NIS</title>
+
+    <pubdate>October 1999</pubdate>
+
+    <abstract>
+      <para>...
+	...
+	...</para>
+    </abstract>
+  </articleinfo>
+
+  <sect1>
+    <title>...</title>
+
+    <para>...</para>
+  </sect1>
+
+  <sect1>
+    <title>...</title>
+
+    <para>...</para>
+  </sect1>
+</article>]]></programlisting>
+	</informalexample>
+      </sect3>
+
+      <sect3>
+	<title>Separating tags</title>
+
+	<para>Tags like <sgmltag>itemizedlist</sgmltag> which will
+	  always have further tags inside them, and in fact do not take
+	  character data themselves, are always on a line by
+	  themselves.</para>
+
+	<para>Tags like <sgmltag>para</sgmltag> and
+	  <sgmltag>term</sgmltag> do not need other tags to contain
+	  normal character data, and their contents begin immediately
+	  after the tag, <emphasis>on the same line</emphasis>.</para>
+
+	<para>The same applies to when these two types of tags
+	  close.</para>
+
+	<para>This leads to an obvious problem when mixing these
+	  tags.</para>
+
+	<para>When a starting tag which cannot contain character data
+	  directly follows a tag of the type that requires other tags
+	  within it to use character data, they are on separate lines.
+	  The second tag should be properly indented.</para>
+
+	<para>When a tag which can contain character data closes
+	  directly after a tag which cannot contain character data
+	  closes, they co-exist on the same line.</para>
+      </sect3>
+    </sect2>
+
+    <sect2>
+      <title>White space changes</title>
+
+      <para>When committing changes, <emphasis>do not commit changes to the
+	  content at the same time as changes to the
+	  formatting</emphasis>.</para>
+      
+      <para>This is so that the teams that convert the Handbook to other
+	languages can quickly see what content has actually changed in your
+	commit, without having to decide whether a line has changed because of
+	the content, or just because it has been refilled.</para>
+
+      <para>For example, if you have added two sentences to a paragraph, such
+	that the line lengths on the paragraph now go over 80 columns, first
+	commit your change with the too-long line lengths.  Then fix the line
+	wrapping, and commit this second change.  In the commit message for
+	the second change, be sure to indicate that this is a whitespace-only
+	change, and that the translation team can ignore it.</para>
+    </sect2>
+
+    <sect2>
+      <title>Nonbreaking space</title>
+
+      <para>Avoid line breaks in places where they look ugly
+	or make it difficult to follow a sentence.  Line breaks depend
+	on the width of the chosen output medium.  In particular, viewing
+	the HTML documentation with a text browser can lead to badly
+	formatted paragraphs like the next one:</para>
+
+      <literallayout class="monospaced">Data capacity ranges from 40 MB to 15
+GB.  Hardware compression &hellip;</literallayout>
+
+      <para>The general entity <literal>&amp;nbsp;</literal> prohibits
+	line breaks between parts belonging together.  Use nonbreaking
+	spaces in the following places:</para>
+
+      <itemizedlist>
+	<listitem>
+	  <para>between numbers and units:</para>
+	  <programlisting><![ CDATA [57600&nbsp;bps]]></programlisting>
+	</listitem>
+
+	<listitem>
+	  <para>between program names and version numbers:</para>
+	  <programlisting><![ CDATA [FreeBSD&nbsp;4.7]]></programlisting>
+	</listitem>
+
+	<listitem>
+	  <para>between multiword names (use with caution when applying this
+	    to more than 3-4 word names like <quote>The FreeBSD Brazilian
+	      Portuguese Documentation Project</quote>):</para>
+	  <programlisting><![ CDATA [Sun&nbsp;Microsystems]]></programlisting>  
+	</listitem>
+      </itemizedlist>
+    </sect2>
+  </sect1>
+
+  <sect1 id="writing-style-word-list">
+    <title>Word list</title>
+
+    <para>The following is a small list of words spelled the way they
+      should be used in the FreeBSD Documentation Project.  If the
+      word you are looking for is not in this list, then please
+      consult the <ulink
+      url="http://www.oreilly.com/oreilly/author/stylesheet.html">O'Reilly
+      word list</ulink>.</para>
+
+    <itemizedlist>
+      <listitem>
+	<para>2.2.X</para>
+      </listitem>
+
+      <listitem>
+	<para>4.X-STABLE</para>
+      </listitem>
+
+      <listitem>
+	<para>CD-ROM</para>
+      </listitem>
+
+      <listitem>
+	<para>DoS <emphasis>(Denial of Service)</emphasis> </para>
+      </listitem>
+
+      <listitem>
+	<para>Ports Collection</para>
+      </listitem>
+
+      <listitem>
+	<para>IPsec</para>
+      </listitem>
+
+      <listitem>
+	<para>Internet</para>
+      </listitem>
+
+      <listitem>
+	<para>MHz</para>
+      </listitem>
+
+      <listitem>
+	<para>Soft Updates</para>
+      </listitem>
+
+      <listitem>
+	<para>Unix</para>
+      </listitem>
+
+      <listitem>
+	<para>disk label</para>
+      </listitem>
+
+      <listitem>
+	<para>email</para>
+      </listitem>
+
+      <listitem>
+	<para>file system</para>
+      </listitem>
+
+      <listitem>
+	<para>manual page</para>
+      </listitem>
+
+      <listitem>
+	<para>mail server</para>
+      </listitem>
+
+      <listitem>
+	<para>name server</para>
+      </listitem>
+
+      <listitem>
+	<para>null-modem</para>
+      </listitem>
+
+      <listitem>
+	<para>web server</para>
+      </listitem>
+    </itemizedlist>
+
+  </sect1>
+</chapter>
+
+<!--
+     Local Variables:
+     mode: sgml
+     sgml-declaration: "../chapter.decl"
+     sgml-indent-data: t
+     sgml-omittag: nil
+     sgml-always-quote-attributes: t
+     sgml-parent-document: ("../book.sgml" "part" "chapter")
+     End:
+-->
+
diff --git a/zh_TW.Big5/books/handbook/book.sgml b/zh_TW.Big5/books/handbook/book.sgml
index 8e11e673be..0b65cad6ea 100644
--- a/zh_TW.Big5/books/handbook/book.sgml
+++ b/zh_TW.Big5/books/handbook/book.sgml
@@ -1,315 +1,316 @@
 <!--
      The FreeBSD Documentation Project
 
      $FreeBSD$
 -->
 
 <!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
 <!ENTITY % books.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Books Entity Set//EN">
 %books.ent;
 <!ENTITY % chapters SYSTEM "chapters.ent">
 %chapters;
 <!ENTITY % txtfiles SYSTEM "txtfiles.ent">
 %txtfiles;
 
 <!ENTITY % not.published "INCLUDE">
 
 <!ENTITY % chap.introduction "IGNORE">
 <!ENTITY % chap.install "IGNORE">
 <!ENTITY % chap.basics "IGNORE">
 <!ENTITY % chap.ports "IGNORE">
 <!ENTITY % chap.config "IGNORE">
 <!ENTITY % chap.boot "IGNORE">
 <!ENTITY % chap.users "IGNORE">
 <!ENTITY % chap.kernelconfig "IGNORE">
 <!ENTITY % chap.security "IGNORE">
 <!ENTITY % chap.printing "IGNORE">
 <!ENTITY % chap.disks "IGNORE">
 <!ENTITY % chap.geom "IGNORE">
 <!ENTITY % chap.vinum "IGNORE">
 <!ENTITY % chap.x11 "IGNORE">
 <!ENTITY % chap.l10n "IGNORE">
 <!ENTITY % chap.multimedia "IGNORE">
 <!ENTITY % chap.desktop "IGNORE">
 <!ENTITY % chap.serialcomms "IGNORE">
 <!ENTITY % chap.ppp-and-slip "IGNORE">
 <!ENTITY % chap.advanced-networking "IGNORE">
 <!ENTITY % chap.firewalls "IGNORE">
 <!ENTITY % chap.network-servers "IGNORE">
 <!ENTITY % chap.mail "IGNORE">
 <!ENTITY % chap.cutting-edge "IGNORE">
 <!ENTITY % chap.linuxemu "IGNORE">
 <!ENTITY % chap.mirrors "IGNORE">
 <!ENTITY % chap.bibliography "IGNORE">
 <!ENTITY % chap.eresources "IGNORE">
 <!ENTITY % chap.pgpkeys "IGNORE">
 <!ENTITY % chap.index "IGNORE">
 <!ENTITY % chap.freebsd-glossary "IGNORE">
 <!ENTITY % chap.mac "IGNORE">
 
 <!ENTITY % pgpkeys SYSTEM "../../../share/pgpkeys/pgpkeys.ent"> %pgpkeys;
 ]>
 
 <book>
   <bookinfo>
     <title>FreeBSD ¨Ï¥Î¤â¥U</title>
     
     <corpauthor>FreeBSD ¤å¥ó­pµe</corpauthor>
     
     <pubdate>February 1999</pubdate>
     
     <copyright>
       <year>1995</year>
       <year>1996</year>
       <year>1997</year>
       <year>1998</year>
       <year>1999</year>
       <year>2000</year>
       <year>2001</year>
       <year>2002</year>
       <year>2003</year>
       <year>2004</year>
       <year>2005</year>
+      <year>2006</year>
       <holder>FreeBSD ¤å¥ó­pµe</holder>
     </copyright>
 
     &bookinfo.legalnotice;
 
     <legalnotice id="trademarks" role="trademarks">
       &tm-attrib.freebsd;
       &tm-attrib.3com;
       &tm-attrib.3ware;
       &tm-attrib.arm;
       &tm-attrib.adaptec;
       &tm-attrib.adobe;
       &tm-attrib.apple;
       &tm-attrib.corel;
       &tm-attrib.creative;
       &tm-attrib.cvsup;
       &tm-attrib.heidelberger;
       &tm-attrib.ibm;
       &tm-attrib.ieee;
       &tm-attrib.intel;
       &tm-attrib.intuit;
       &tm-attrib.linux;
       &tm-attrib.lsilogic;
       &tm-attrib.m-systems;
       &tm-attrib.macromedia;
       &tm-attrib.microsoft;
       &tm-attrib.netscape;
       &tm-attrib.nexthop;
       &tm-attrib.opengroup;
       &tm-attrib.oracle;
       &tm-attrib.powerquest;
       &tm-attrib.realnetworks;
       &tm-attrib.redhat;
       &tm-attrib.sap;
       &tm-attrib.sun;
       &tm-attrib.symantec;
       &tm-attrib.themathworks;
       &tm-attrib.thomson;
       &tm-attrib.usrobotics;
       &tm-attrib.vmware;
       &tm-attrib.waterloomaple;
       &tm-attrib.wolframresearch;
       &tm-attrib.xfree86;
       &tm-attrib.xiph;
       &tm-attrib.general;
     </legalnotice>
     
     <abstract>
       <para>Åwªï¨Ï¥ÎFreeBSD¡I ¥»¨Ï¥Î¤â¥U²[»\½d³ò¥]¬A¤F 
 	<emphasis>FreeBSD &rel2.current;-RELEASE</emphasis> ©M 
 	<emphasis>FreeBSD &rel.current;-RELEASE</emphasis> ªº¦w¸Ë©M¤é±`¨Ï¥Î¡C
 	³o¥÷¨Ï¥Î¤â¥U¬O«Ü¦h¤Hªº¶°Åé³Ð§@¡A¦Ó¥B¤´µM¡y«ùÄò¤£Â_¡zªº¶i¦æ¤¤¡C
 	³\¦h³¹¸`¤´¥¼§¹¦¨¡A¤w§¹¦¨ªº³¡¥÷¤]¦³¨Ç»Ý­n§ó·s¡C 
         ¦pªG±z¹ï¨ó§U¥»­pµeªº¶i¦æ¦³¿³½ìªº¸Ü¡A½Ð±H e-mail ¨ì &a.doc;¡C 
         ¦b <ulink url="http://www.FreeBSD.org/">FreeBSD ºô¯¸</ulink>
 	¥i¥H§ä¨ì³o¥÷¤å¥óªº³Ì·sª©¥»(ª©¤å¥ó¥i±q <ulink
 	url="http://docs.FreeBSD.org/doc/"></ulink> ¨ú±o)¡A¤]¥i¥H±q <ulink 
 	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">FreeBSD FTP ¦øªA¾¹</ulink>
 	©Î¬O²³¦h <link linkend="mirrors-ftp">mirror ¯¸»O</link> 
 	¤U¸ü¤£¦P®æ¦¡¤Î¤£¦PÀ£ÁY¿ï¶µªº¸ê®Æ¡C
 	¦pªG¤ñ¸û°¾¦n¾Ö¦³¹êÅé®Ñ­±¸ê®Æ¡A¨º¥i¥H¦b
 	<ulink url="http://www.freebsdmall.com/">FreeBSD Mall</ulink> ÁʶR¡C
 	¦¹¥~¡A¤]¥i¥H¦b <ulink url="&url.base;/search/index.html">¨Ï¥Î¤â¥U</ulink>
 	¤¤·j´M¸ê®Æ¡C
       </para>
     </abstract>
   </bookinfo>
 
   &chap.preface;
 
   <part id="getting-started">
     <title>¶}©l¨Ï¥Î FreeBSD </title>
     
     <partintro>
       <para>³o³¡¥÷¬O´£¨Ñµ¹ªì¦¸¨Ï¥Î FreeBSD ªº¨Ï¥ÎªÌ©M¨t²ÎºÞ²zªÌ¡C
         ³o¨Ç³¹¸`¥]¬A¡G</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>¤¶²Ð FreeBSD µ¹±z¡C </para>
 	</listitem>
 
 	<listitem>
 	  <para>¦b¦w¸Ë¹Lµ{µ¹±z«ü¤Þ¡C </para>
 	</listitem>
 
 	<listitem>
 	  <para>±Ð±z &unix; ªº°ò¦¤Î­ì²z¡C </para>
 	</listitem>
 
 	<listitem>
 	  <para>®i¥Üµ¹±z¬Ý¦p¦ó¦w¸ËÂ×´Iªº FreeBSD ªºÀ³¥Î³nÅé</para>
 	</listitem>
 
 	<listitem>
 	  <para>¦V±z¤¶²Ð X¡A &unix; ªºµøµ¡¨t²Î¥H¤Î¸Ô²Óªº®à­±Àô¹Ò³]©w¡AÅý±z§ó¦³¥Í²£¤O¡C
 	  </para>
 	</listitem>
       </itemizedlist>
 
       <para>§Ú­Ì¸ÕµÛ¾¨¥i¯àªºÅý³o¬q¤å¦rªº°Ñ¦Ò³sµ²¼Æ¥Ø­°¨ì³Ì§C¡AÅý±z¦bŪ¨Ï¥Î¤â¥Uªº³o³¡¥÷®É¥i¥H¤£¤Ó»Ý­n±`±`«e«á½­¶¡C
       </para>
     </partintro>
 
     <![ %chap.introduction;             [ &chap.introduction;         ]]>
     <![ %chap.install;                  [ &chap.install;              ]]>
     <![ %chap.basics;                   [ &chap.basics;               ]]>
     <![ %chap.ports;                    [ &chap.ports;                ]]>
     <![ %chap.x11;                      [ &chap.x11;                  ]]>
   </part>
   
   <part id="common-tasks">
     <title>¤@¯ë©Ê¤u§@</title>
     
     <partintro>
 	    <para>¬JµM°ò¦ªº³¡¤À¤w¸g´£¹L¤F¡A±µ¤U¨Óªº³o­Ó³¡¤À±N·|°Q½×¤@¨Ç±`·|¥Î¨ìªº FreeBSD
 	    ªº¯S¦â¡A³o¨Ç³¹¸`¥]¬A¡G</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>¤¶²Ðµ¹±z±`¨£¥B¹ê¥Îªº®à­±À³¥Î³nÅé¡Gºô­¶ÂsÄý¾¹¡B¥Í²£¤O¤u¨ã¡B¤å¥óÀ˵øµ{¦¡µ¥¡C</para>
 	</listitem>
 
 	<listitem>
 	  <para>¤¶²Ðµ¹±z²³¦h FreeBSD ¤W¥i¥Îªº¦h´CÅé¤u¨ã¡C</para>
 	</listitem>
 
 	<listitem>
 	  <para>¸ÑÄÀ¦p¦ó½sĶ¦Û­q FreeBSD ®Ö¤ß¥H¼W¥[ÃB¥~¨t²Î¥\¯àªº¬yµ{¡C</para>
 	</listitem>
 
         <listitem>
           <para>¸Ô²Ó´y­z¦C¦L¨t²Î¡A¥]§t®à¤W«¬¦Lªí¾÷¤Îºô¸ô¦Lªí¾÷ªº³]©w¡C</para>
         </listitem>
 
         <listitem>
 	  <para>®i¥Üµ¹±z¬Ý¦p¦ó¦b±zªº FreeBSD ¨t²Î¤¤°õ¦æ Linux À³¥Î³nÅé¡C</para>
         </listitem>
 
       </itemizedlist>
 
       <para>³o¨Ç³¹¸`¤¤¦³¨Ç»Ý­n±z¹w¥ý¾\Ū¨Ç¬ÛÃö¤å¥ó¡A¦b¦U³¹¸`¶}ÀYªº·§­n¤º·|´£¤Î¡C</para>
 
     </partintro>
 
     <![ %chap.desktop;                  [ &chap.desktop;              ]]>
     <![ %chap.multimedia;               [ &chap.multimedia;           ]]>
     <![ %chap.kernelconfig;             [ &chap.kernelconfig;         ]]>
     <![ %chap.printing;                 [ &chap.printing;             ]]>
     <![ %chap.linuxemu;                 [ &chap.linuxemu;             ]]>
   </part>
 
   <part id="system-administration">
     <title>¨t²ÎºÞ²z</title>
 
     <partintro>
       <para>FreeBSD ¨Ï¥Î¤â¥U³Ñ¤Uªº³o¨Ç³¹¸`²[»\¤F¥þ¤è¦ìªº FreeBSD ¨t²ÎºÞ²z¡C
       ¨C­Ó³¹¸`ªº¶}ÀY·|¥ý´y­z¦b¸Ó±zŪ§¹¸Ó³¹¸`«á±z·|¾Ç¨ì¤°»ò¡A¤]·|¸Ô­z¦b±z¦b¬Ý³o¨Ç¸ê®Æ®ÉÀ³¸Ó­n¦³ªº¤@¨Ç­I´ºª¾ÃÑ¡C
       </para>
 
       <para>³o¨Ç³¹¸`¬OÅý±z¦b»Ý­n¬d¸ê®Æªº®É­Ô½¾\¥Îªº¡C 
       ±z¤£»Ý­n¨Ì·Ó¯S©wªº¶¶§Ç¨ÓŪ¡A¤]¤£»Ý­n±N³o¨Ç³¹¸`¥þ³¡¹LŪ¤§«á¤~¶}©l¥Î FreeBSD¡C
       </para>
     </partintro>
 
     <![ %chap.config;                   [ &chap.config;               ]]>
     <![ %chap.boot;                     [ &chap.boot;                 ]]>
     <![ %chap.users;                    [ &chap.users;                ]]>
     <![ %chap.security;                 [ &chap.security;             ]]>
     <![ %chap.mac;			[ &chap.mac;		      ]]>
     <![ %chap.disks;                    [ &chap.disks;                ]]>
     <![ %chap.geom;			[ &chap.geom;		      ]]>
     <![ %chap.vinum;                    [ &chap.vinum;                ]]>
     <![ %chap.l10n;                     [ &chap.l10n;                 ]]>
     <![ %chap.cutting-edge;             [ &chap.cutting-edge;         ]]>
   </part>
 
   <part id="network-communication">
     <title>ºô¸ô³q°T</title>
 
     <partintro>
       <para>FreeBSD ¬O¤@ºØ¼sªxªº³Q¨Ï¥Î¦b°ª®Ä¯àªººô¸ô¦øªA¾¹¤¤ªº§@·~¨t²Î¡A³o¨Ç³¹¸`¥]§t¤F¡G</para>
 
       <itemizedlist>
         <listitem>
           <para>§Ç¦C°ð³q°T</para>
         </listitem>
 
         <listitem>
           <para>PPP ©M PPPoE</para>
         </listitem>
 
         <listitem>
           <para>¹q¤l¶l¥ó</para>
         </listitem>
 
         <listitem>
           <para>°õ¦æºô¸ô¦øªAµ{¦¡</para>
         </listitem>
 
         <listitem>
           <para>¨¾¤õÀð</para>
         </listitem>
 
         <listitem>
           <para>¨ä¥Lªº¶i¶¥ºô¸ô¥DÃD</para>
         </listitem>
       </itemizedlist>
 
       <para>³o¨Ç³¹¸`¬OÅý±z¦b»Ý­n¬d¸ê®Æªº®É­Ô½¾\¥Îªº¡C
       ±z¤£»Ý­n¨Ì·Ó¯S©wªº¶¶§Ç¨ÓŪ¡A¤]¤£»Ý­n±N³o¨Ç³¹¸`¥þ³¡Åª¹L¤§«á¤~±N FreeBSD ¥Î¦bºô¸ôÀô¹Ò¤U¡C</para>
     </partintro>
 
     <![ %chap.serialcomms;              [ &chap.serialcomms;          ]]>
     <![ %chap.ppp-and-slip;             [ &chap.ppp-and-slip;         ]]>
     <![ %chap.mail;                     [ &chap.mail;                 ]]>
     <![ %chap.network-servers;          [ &chap.network-servers;      ]]>
     <![ %chap.firewalls;                [ &chap.firewalls;            ]]>
     <![ %chap.advanced-networking;      [ &chap.advanced-networking;  ]]>
 
   </part>
   
   <part id="appendices">
     <title>ªþ¿ý</title>
     
     <![ %chap.mirrors;                  [ &chap.mirrors;              ]]>
     <![ %chap.bibliography;             [ &chap.bibliography;         ]]>
     <![ %chap.eresources;               [ &chap.eresources;           ]]>
     <![ %chap.pgpkeys;                  [ &chap.pgpkeys;              ]]>
   </part>
   <![ %chap.freebsd-glossary;         [ &bookinfo.freebsd-glossary; ]]>
   <![ %chap.index;                    [ &chap.index;                ]]>
   &chap.colophon;
 </book>
 
 <!-- 
      Local Variables:
      mode: sgml
      sgml-indent-data: t
      sgml-omittag: nil
      sgml-always-quote-attributes: t
      End:
 -->
diff --git a/zh_TW.Big5/books/handbook/boot/chapter.sgml b/zh_TW.Big5/books/handbook/boot/chapter.sgml
index 557c013b29..79441aa5dc 100644
--- a/zh_TW.Big5/books/handbook/boot/chapter.sgml
+++ b/zh_TW.Big5/books/handbook/boot/chapter.sgml
@@ -1,821 +1,821 @@
 <!--
      The FreeBSD Documentation Project
 
      $FreeBSD$
 -->
 
 <chapter id="boot">
-  <title>The FreeBSD Booting Process</title>
+  <title>FreeBSD ¶}¾÷µ{§Ç</title>
 
   <sect1 id="boot-synopsis">
-    <title>Synopsis</title>
+    <title>·§­z</title>
     <indexterm><primary>booting</primary></indexterm>
     <indexterm><primary>bootstrap</primary></indexterm>
 
     <para>The process of starting a computer and loading the operating system
       is referred to as <quote>the bootstrap process</quote>, or simply
       <quote>booting</quote>.  FreeBSD's boot process provides a great deal of
       flexibility in customizing what happens when you start the system,
       allowing you to select from different operating systems installed on the
       same computer, or even different versions of the same operating system
       or installed kernel.</para>
 
     <para>This chapter details the configuration options you can set and how
       to customize the FreeBSD boot process.  This includes everything that
       happens until the FreeBSD kernel has started, probed for devices, and
       started &man.init.8;.  If you are not quite sure when this happens, it
       occurs when the text color changes from bright white to grey.</para>
 
-    <para>After reading this chapter, you will know:</para>
+    <para>Ū§¹³o³¹¡A±z±N¤F¸Ñ¡G</para>
 
     <itemizedlist>
       <listitem>
 	<para>What the components of the FreeBSD bootstrap system are, and how
 	  they interact.</para>
       </listitem>
 
       <listitem>
 	<para>The options you can give to the components in the FreeBSD
 	  bootstrap to control the boot process.</para>
       </listitem>
       
       <listitem>
-        <para>The basics of &man.device.hints.5;.</para>
+        <para>&man.device.hints.5; ªº°ò¥»·§©À¡C</para>
       </listitem>
     </itemizedlist>
 
     <note>
       <title>x86 Only</title>
 
       <para>This chapter only describes the boot process for FreeBSD running
 	on Intel x86 systems.</para>
     </note>
   </sect1>
 
   <sect1 id="boot-introduction">
-    <title>The Booting Problem</title>
+    <title>Booting °ÝÃD</title>
 
     <para>Turning on a computer and starting the operating system poses an
       interesting dilemma.  By definition, the computer does not know how to
       do anything until the operating system is started.  This includes
       running programs from the disk.  So if the computer can not run a
       program from the disk without the operating system, and the operating
       system programs are on the disk, how is the operating system
       started?</para>
 
     <para>This problem parallels one in the book <citetitle>The Adventures of
       Baron Munchausen</citetitle>.  A character had fallen part way down a
       manhole, and pulled himself out by grabbing his bootstraps, and
       lifting.  In the early days of computing the term
       <firstterm>bootstrap</firstterm> was applied to the mechanism used to
       load the operating system, which has become shortened to
       <quote>booting</quote>.</para>
 
     <indexterm><primary>BIOS</primary></indexterm>
 
     <indexterm><primary>Basic Input/Output System</primary><see>BIOS</see></indexterm>
 
     <para>On x86 hardware the Basic Input/Output System (BIOS) is responsible
       for loading the operating system.  To do this, the BIOS looks on the
       hard disk for the Master Boot Record (MBR), which must be located on a
       specific place on the disk.  The BIOS has enough knowledge to load and
       run the MBR, and assumes that the MBR can then carry out the rest of the
       tasks involved in loading the operating system,
       possibly with the help of the BIOS.</para>
 
     <indexterm><primary>Master Boot Record (MBR)</primary></indexterm>
 
     <indexterm><primary>Boot Manager</primary></indexterm>
 
     <indexterm><primary>Boot Loader</primary></indexterm>
 
     <para>The code within the MBR is usually referred to as a <emphasis>boot
       manager</emphasis>, especially when it interacts with the user.  In this case
       the boot manager usually has more code in the first
       <emphasis>track</emphasis> of the disk or within some OS's file system.  (A
       boot manager is sometimes also called a <emphasis>boot loader</emphasis>,
       but FreeBSD uses that term for a later stage of booting.) Popular boot
       managers include <application>boot0</application> (a.k.a. <application>Boot
       Easy</application>, the standard &os; boot manager),
       <application>Grub</application>, <application>GAG</application>, and
       <application>LILO</application>.
       (Only <application>boot0</application> fits within the MBR.)</para>
 
     <para>If you have only one operating system installed on your disks then
       a standard PC MBR will suffice.  This MBR searches for the first bootable
       (a.k.a. active) slice on the disk, and then runs the code on that slice to
       load the remainder of the operating system.  The MBR installed by
       &man.fdisk.8;, by default, is such an MBR.  It is based on
       <filename>/boot/mbr</filename>.</para>
 
     <para>If you have installed multiple operating systems on your disks then
       you can install a different boot manager, one that can display a list of
       different operating systems, and allows you to choose the one to boot
       from.  Two of these are discussed in the next subsection.</para>
 
     <para>The remainder of the FreeBSD bootstrap system is divided into three
       stages.  The first stage is run by the MBR, which knows just enough to
       get the computer into a specific state and run the second stage.  The
       second stage can do a little bit more, before running the third stage.
       The third stage finishes the task of loading the operating system.  The
       work is split into these three stages because the PC standards put
       limits on the size of the programs that can be run at stages one and
       two.  Chaining the tasks together allows FreeBSD to provide a more
       flexible loader.</para>
 
     <indexterm><primary>kernel</primary></indexterm>
     <indexterm><primary><command>init</command></primary></indexterm>
 
     <para>The kernel is then started and it begins to probe for devices
       and initialize them for use.  Once the kernel boot
       process is finished, the kernel passes control to the user process
       &man.init.8;, which then makes sure the disks are in a usable state.
       &man.init.8; then starts the user-level resource configuration which
       mounts file systems, sets up network cards to communicate on the
       network, and generally starts all the processes that usually
       are run on a FreeBSD system at startup.</para>
   </sect1>
 
   <sect1 id="boot-blocks">
     <title>The Boot Manager and Boot Stages</title>
 
     <indexterm><primary>Boot Manager</primary></indexterm>
 
     <sect2 id="boot-boot0">
       <title>The Boot Manager</title>
       <indexterm><primary>Master Boot Record (MBR)</primary></indexterm>
 
       <para>The code in the MBR or boot manager is sometimes referred to as
         <emphasis>stage zero</emphasis> of the boot process.  This subsection
         discusses two of the boot managers previously mentioned:
         <application>boot0</application> and <application>LILO</application>.</para>
 
       <formalpara><title>The <application>boot0</application> Boot Manager:</title>
         <para>The MBR installed by FreeBSD's installer or &man.boot0cfg.8;, by
           default, is based on <filename>/boot/boot0</filename>.
           (The <application>boot0</application> program is very simple, since the
           program in the <abbrev>MBR</abbrev> can only be 446 bytes long because of the slice
           table and 0x55AA identifier at the end of the MBR.)
           If you have installed <application>boot0</application> and
           multiple operating systems on your hard disks, then you will see a
           display similar to this one at boot time:</para></formalpara>
 
       <example id="boot-boot0-example">
 	<title><filename>boot0</filename> Screenshot</title>
 
 	<screen>F1 DOS
 F2 FreeBSD
 F3 Linux
 F4 ??
 F5 Drive 1
 
 Default: F2</screen>
       </example>
 
       <para>Other operating systems, in particular &windows;, have been known
 	to overwrite an existing MBR with their own.  If this happens to you,
 	or you want to replace your existing MBR with the FreeBSD MBR then use
 	the following command:</para>
 
       <screen>&prompt.root; <userinput>fdisk -B -b /boot/boot0 <replaceable>device</replaceable></userinput></screen>
 
       <para>where <replaceable>device</replaceable> is the device that you
 	boot from, such as <devicename>ad0</devicename> for the first IDE
 	disk, <devicename>ad2</devicename> for the first IDE disk on a second
 	IDE controller, <devicename>da0</devicename> for the first SCSI disk,
 	and so on.  Or, if you want a custom configuration of the MBR,
 	use &man.boot0cfg.8;.</para>
 
       <formalpara><title>The LILO Boot Manager:</title>
 
 	<para>To install this boot manager so it will also boot FreeBSD, first
 	  start Linux and add the following to your existing
 	  <filename>/etc/lilo.conf</filename> configuration file:</para></formalpara>
 
       <programlisting>other=/dev/hdXY
 table=/dev/hdX
 loader=/boot/chain.b
 label=FreeBSD</programlisting>
 
       <para>In the above, specify FreeBSD's primary partition and drive using
 	Linux specifiers, replacing <replaceable>X</replaceable> with the Linux
 	drive letter and <replaceable>Y</replaceable> with the Linux primary
 	partition number.  If you are using a <acronym>SCSI</acronym> drive, you
 	will need to change <replaceable>/dev/hd</replaceable> to read something
 	similar to <replaceable>/dev/sd</replaceable>.  The
 	<option>loader=/boot/chain.b</option> line can be omitted if you have
 	both operating systems on the same drive.  Now run
 	<command>/sbin/lilo&nbsp;-v</command> to commit your new changes to the
 	system; this should be verified by checking its screen messages.</para>
     </sect2>
   
     <sect2 id="boot-boot1">
       <title>Stage One, <filename>/boot/boot1</filename>, and Stage Two,
 	<filename>/boot/boot2</filename></title>
       
       <para>Conceptually the first and second stages are part of the same
 	program, on the same area of the disk.  Because of space constraints
 	they have been split into two, but you would always install them
 	together.  They are copied from the combined file
 	<filename>/boot/boot</filename> by the installer or
 	<application>disklabel</application> (see below).</para>
 
       <para>They are located outside file systems, in the first track of
 	the boot slice, starting with the first sector.  This is where <link
 	linkend="boot-boot0">boot0</link>, or any other boot manager,
 	expects to find a program to run which will
 	continue the boot process.  The number of sectors used is easily
 	determined from the size of <filename>/boot/boot</filename>.</para>
 
       <para><filename>boot1</filename> is very simple, since it
 	can only be 512 bytes
 	in size, and knows just enough about the FreeBSD
 	<firstterm>disklabel</firstterm>, which stores information
 	about the slice, to find and execute <filename>boot2</filename>.</para>
       
       <para><filename>boot2</filename> is slightly more sophisticated, and understands
 	the FreeBSD file system enough to find files on it, and can
 	provide a simple interface to choose the kernel or loader to
 	run.</para>
 
       <para>Since the <link linkend="boot-loader">loader</link> is
 	much more sophisticated, and provides a nice easy-to-use
 	boot configuration, <filename>boot2</filename> usually runs
 	it, but previously it
 	was tasked to run the kernel directly.</para>
 
       <example id="boot-boot2-example">
 	<title><filename>boot2</filename> Screenshot</title>
 
 	<screen>&gt;&gt; FreeBSD/i386 BOOT
 Default: 0:ad(0,a)/kernel
 boot:</screen>
       </example>
 
       <para>If you ever need to replace the installed
 	<filename>boot1</filename> and <filename>boot2</filename> use
 	&man.disklabel.8;:</para>
       
       <screen>&prompt.root; <userinput>disklabel -B <replaceable>diskslice</replaceable></userinput></screen>
 
       <para>where <replaceable>diskslice</replaceable> is the disk and slice
 	you boot from, such as <devicename>ad0s1</devicename> for the first
 	slice on the first IDE disk.</para>
 
       <warning>
 	<title>Dangerously Dedicated Mode</title>
 
 	<para>If you use just the disk name, such as
 	  <devicename>ad0</devicename>, in the &man.disklabel.8; command you
 	  will create a dangerously dedicated disk, without slices.  This is
 	  almost certainly not what you want to do, so make sure you double
 	  check the &man.disklabel.8; command before you press
 	  <keycap>Return</keycap>.</para>
       </warning>
     </sect2>
 
   <sect2 id="boot-loader">
     <title>Stage Three, <filename>/boot/loader</filename></title>
 
     <indexterm><primary>boot-loader</primary></indexterm>
     <para>The loader is the final stage of the three-stage
       bootstrap, and is located on the file system, usually as
       <filename>/boot/loader</filename>.</para>
       
     <para>The loader is intended as a user-friendly method for
       configuration, using an easy-to-use built-in command set,
       backed up by a more powerful interpreter, with a more complex
       command set.</para> 
 
     <sect3 id="boot-loader-flow">
       <title>Loader Program Flow</title>
       
       <para>During initialization, the loader will probe for a
 	console and for disks, and figure out what disk it is
 	booting from.  It will set variables accordingly, and an
 	interpreter is started where user commands can be passed from
 	a script or interactively.</para>
       <indexterm><primary>loader</primary></indexterm>
       <indexterm><primary>loader configuration</primary></indexterm>
 
       <para>The loader will then read
 	<filename>/boot/loader.rc</filename>, which by default reads
 	in <filename>/boot/defaults/loader.conf</filename> which
 	sets reasonable defaults for variables and reads
 	<filename>/boot/loader.conf</filename> for local changes to
 	those variables.  <filename>loader.rc</filename> then acts
 	on these variables, loading whichever modules and kernel are
 	selected.</para>
 
       <para>Finally, by default, the loader issues a 10 second wait
 	for key presses, and boots the kernel if it is not interrupted.
 	If interrupted, the user is presented with a prompt which
 	understands the easy-to-use command set, where the user may
 	adjust variables, unload all modules, load modules, and then
 	finally boot or reboot.</para>
 
     </sect3>
     
     <sect3 id="boot-loader-commands">
       <title>Loader Built-In Commands</title>
       
       <para>These are the most commonly used loader commands.  For a
         complete discussion of all available commands, please see
         &man.loader.8;.</para>
 
       <variablelist>
 	<varlistentry>
 	  <term>autoboot <replaceable>seconds</replaceable></term>
 
 	  <listitem>
 	    <para>Proceeds to boot the kernel if not interrupted
 	      within the time span given, in seconds.  It displays a
 	      countdown, and the default time span is 10
 	      seconds.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>boot
 	    <optional><replaceable>-options</replaceable></optional>
 	    <optional><replaceable>kernelname</replaceable></optional></term>
 
 	  <listitem>
 	    <para>Immediately proceeds to boot the kernel, with the
 	      given options, if any, and with the kernel name given,
 	      if it is.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>boot-conf</term>
 
 	  <listitem>
 	    <para>Goes through the same automatic configuration of
 	      modules based on variables as what happens at boot.
 	      This only makes sense if you use
 	      <command>unload</command> first, and change some
 	      variables, most commonly <envar>kernel</envar>.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>help
 	    <optional><replaceable>topic</replaceable></optional></term>
 
 	  <listitem>
 	    <para>Shows help messages read from
 	      <filename>/boot/loader.help</filename>.  If the topic
 	      given is <literal>index</literal>, then the list of
 	      available topics is given.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>include <replaceable>filename</replaceable>
 	    &hellip;</term>
 
 	  <listitem>
 	    <para>Processes the file with the given filename.  The
 	      file is read in, and interpreted line by line.  An
 	      error immediately stops the include command.</para>
 	  </listitem>
 	</varlistentry>
 	<varlistentry>
 	  <term>load <optional><option>-t</option>
 	    <replaceable>type</replaceable></optional>
 	    <replaceable>filename</replaceable></term>
 
 	  <listitem>
 	    <para>Loads the kernel, kernel module, or file of the
 	      type given, with the filename given.  Any arguments
 	      after filename are passed to the file.</para>
 	  </listitem>
 	</varlistentry>
 	<varlistentry>
 	  <term>ls <optional><option>-l</option></optional>
 	    <optional><replaceable>path</replaceable></optional></term>
 
 	  <listitem>
 	    <para>Displays a listing of files in the given path, or
 	      the root directory, if the path is not specified.  If
 	      <option>-l</option> is specified, file sizes will be
 	      shown too.</para>
 	  </listitem>
 	</varlistentry>
 	<varlistentry>
 	  <term>lsdev <optional><option>-v</option></optional></term>
 
 	  <listitem>
 	    <para>Lists all of the devices from which it may be
 	      possible to load modules. If <option>-v</option> is
 	      specified, more details are printed.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>lsmod <optional><option>-v</option></optional></term>
 
 	  <listitem>
 	    <para>Displays loaded modules. If <option>-v</option> is
 	      specified, more details are shown.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>more <replaceable>filename</replaceable></term>
 
 	  <listitem>
 	    <para>Displays the files specified, with a pause at each
 	      <varname>LINES</varname> displayed.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>reboot</term>
 
 	  <listitem>
 	    <para>Immediately reboots the system.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>set <replaceable>variable</replaceable></term>
 	  <term>set
 	    <replaceable>variable</replaceable>=<replaceable>value</replaceable></term>
 
 	  <listitem>
 	    <para>Sets the loader's environment variables.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>unload</term>
 
 	  <listitem>
 	    <para>Removes all loaded modules.</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
     </sect3>
 
     <sect3 id="boot-loader-examples">
       <title>Loader Examples</title>
 
       <para>Here are some practical examples of loader usage:</para>
 
       <itemizedlist>
 	<indexterm><primary>single-user mode</primary></indexterm>
 	<listitem>
 	  <para>To simply boot your usual kernel, but in single-user
 	    mode:</para>
 
 	  <screen><userinput>boot -s</userinput></screen>
 	</listitem>
 
 	<listitem>
 	  <para>To unload your usual kernel and modules, and then
 	    load just your old (or another) kernel:</para>
     <indexterm>
       <primary><filename>kernel.old</filename></primary>
     </indexterm>
 
 	  <screen><userinput>unload</userinput>
 <userinput>load <replaceable>kernel.old</replaceable></userinput></screen>
 
 	  <para>You can use <filename>kernel.GENERIC</filename> to
 	    refer to the generic kernel that comes on the install
 	    disk, or <filename>kernel.old</filename> to refer to
 	    your previously installed kernel (when you have upgraded
 	    or configured your own kernel, for example).</para>
 
 	  <note>
 	    <para>Use the following to load your usual modules with
 	      another kernel:</para>
 
 	    <screen><userinput>unload</userinput>
 <userinput>set kernel="<replaceable>kernel.old</replaceable>"</userinput>
 <userinput>boot-conf</userinput></screen></note>
 	</listitem>
 
 	<listitem>
 	  <para>To load a kernel configuration script (an automated
 	    script which does the things you would normally do in the
 	    kernel boot-time configurator):</para>
 
 	  <screen><userinput>load -t userconfig_script <replaceable>/boot/kernel.conf</replaceable></userinput></screen>
 	</listitem>
       </itemizedlist>
   </sect3>
     </sect2>
   </sect1>
 
   <sect1 id="boot-kernel">
     <title>Kernel Interaction During Boot</title>
     <indexterm>
       <primary>kernel</primary>
       <secondary>boot interaction</secondary>
     </indexterm>
     
     <para>Once the kernel is loaded by either <link
 	linkend="boot-loader">loader</link> (as usual) or <link
 	linkend="boot-boot1">boot2</link> (bypassing the loader), it
       examines its boot flags, if any, and adjusts its behavior as
       necessary.</para>
 
     <sect2 id="boot-kernel-bootflags">
       <indexterm>
         <primary>kernel</primary>
         <secondary>bootflags</secondary>
       </indexterm>
       <title>Kernel Boot Flags</title>
 
       <para>Here are the more common boot flags:</para>
 
       <variablelist id="boot-kernel-bootflags-list">
 	<varlistentry>
 	  <term><option>-a</option></term>
 
 	  <listitem>
 	    <para>during kernel initialization, ask for the device
 	      to mount as the root file system.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><option>-C</option></term>
 
 	  <listitem>
 	    <para>boot from CDROM.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><option>-c</option></term>
 
 	  <listitem>
 	    <para>run UserConfig, the boot-time kernel
 	      configurator</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><option>-s</option></term>
 
 	  <listitem>
 	    <para>boot into single-user mode</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><option>-v</option></term>
 
 	  <listitem>
 	    <para>be more verbose during kernel startup</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
 
       <note>
 	<para>There are other boot flags, read &man.boot.8; for more
 	  information on them.</para></note>
     </sect2>
 
 <!--    <sect2 id="boot-kernel-userconfig">
       <title>UserConfig: the Boot-time Kernel Configurator</title>
       
       <para> </para>
     </sect2> -->
   </sect1>
   
   <sect1 id="device-hints">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Tom</firstname>
 	  <surname>Rhodes</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
       <!-- 18 OCT 2002 -->
     </sect1info>
     <indexterm>
       <primary>device.hints</primary>
     </indexterm>
     <title>Device Hints</title>
 
     <note><para>This is a FreeBSD&nbsp;5.0 and later feature which does not
       exist in earlier versions.</para></note>
 
     <para>During initial system startup, the boot &man.loader.8; will read the
       &man.device.hints.5; file.  This file stores kernel boot information
       known as variables, sometimes referred to as <quote>device hints</quote>.
       These <quote>device hints</quote> are used by device drivers for device
       configuration.</para>
       
     <para>Device hints may also be specified at the <link linkend="boot-loader">
       Stage 3 boot loader</link> prompt.  Variables can be added using
       <command>set</command>, removed with <command>unset</command>, and viewed
       with the <command>show</command> commands.  Variables set in the
       <filename>/boot/device.hints</filename> file can be overridden here also.  Device hints entered at
       the boot loader are not permanent and will be forgotten on the next
       reboot.</para>
 
     <para>Once the system is booted, the &man.kenv.1; command can be used to
       dump all of the variables.</para>
 
     <para>The syntax for the <filename>/boot/device.hints</filename> file is one variable per line, using
       the standard hash <quote>#</quote> as comment markers.  Lines are
       constructed as follows:</para>
 
     <screen><userinput>hint.driver.unit.keyword="<replaceable>value</replaceable>"</userinput></screen>
 
     <para>The syntax for the Stage 3 boot loader is:</para>
     <screen><userinput>set hint.driver.unit.keyword=<replaceable>value</replaceable></userinput></screen>
 
     <para><literal>driver</literal> is the device driver name, <literal>unit</literal>
       is the device driver unit number, and <literal>keyword</literal> is the hint
       keyword.  The keyword may consist of the following options:</para>
 
     <itemizedlist>
       <listitem>
 	<para><literal>at</literal>: specifies the bus which the device is attached to.</para>
       </listitem>
 
       <listitem>
 	<para><literal>port</literal>: specifies the start address of the <acronym>I/O</acronym>
 	  to be used.</para>
       </listitem>
 
       <listitem>
 	<para><literal>irq</literal>: specifies the interrupt request number to be used.</para>
       </listitem>
 
       <listitem>
 	<para><literal>drq</literal>: specifies the DMA channel number.</para>
       </listitem>
 
       <listitem>
 	<para><literal>maddr</literal>: specifies the physical memory address occupied by the
 	  device.</para>
       </listitem>
 
       <listitem>
 	<para><literal>flags</literal>: sets various flag bits for the device.</para>
       </listitem>
 
       <listitem>
 	<para><literal>disabled</literal>: if set to <literal>1</literal> the device is disabled.</para>
       </listitem>
     </itemizedlist>
 
     <para>Device drivers may accept (or require) more hints not listed here, viewing
       their manual page is recommended.  For more information, consult the
       &man.device.hints.5;, &man.kenv.1;, &man.loader.conf.5;, and &man.loader.8;
       manual pages.</para>
   </sect1>
 
   <sect1 id="boot-init">
     <indexterm>
       <primary><command>init</command></primary>
     </indexterm>
     <title>Init: Process Control Initialization</title>
 	
     <para>Once the kernel has finished booting, it passes control to
       the user process &man.init.8;, which is located at
       <filename>/sbin/init</filename>, or the program path specified
       in the <envar>init_path</envar> variable in
       <command>loader</command>.</para>
 
     <sect2 id="boot-autoreboot">
       <title>Automatic Reboot Sequence</title>
       
       <para>The automatic reboot sequence makes sure that the
 	file systems available on the system are consistent.  If they
 	are not, and &man.fsck.8; cannot fix the
 	inconsistencies, &man.init.8; drops the system
 	into <link linkend="boot-singleuser">single-user mode</link>
 	for the system administrator to take care of the problems
 	directly.</para>
     </sect2>
 
     <sect2 id="boot-singleuser">
       <title>Single-User Mode</title>
       <indexterm><primary>single-user mode</primary></indexterm>
       <indexterm><primary>console</primary></indexterm>
       
       <para>This mode can be reached through the <link
 	  linkend="boot-autoreboot">automatic reboot
 	  sequence</link>, or by the user booting with the
 	<option>-s</option> option or setting the
 	<envar>boot_single</envar> variable in
 	<command>loader</command>.</para>
 
       <para>It can also be reached by calling
 	&man.shutdown.8; without the reboot
 	(<option>-r</option>) or halt (<option>-h</option>) options,
 	from <link linkend="boot-multiuser">multi-user
 	  mode</link>.</para>
 
       <para>If the system <literal>console</literal> is set
 	to <literal>insecure</literal> in <filename>/etc/ttys</filename>,
 	then the system prompts for the <username>root</username> password
 	before initiating single-user mode.</para>
 
       <example id="boot-insecure-console">
 	<title>An Insecure Console in <filename>/etc/ttys</filename></title>
 
 	<programlisting># name  getty                           type    status          comments
 #
 # If console is marked "insecure", then init will ask for the root password
 # when going to single-user mode.
 console none                            unknown off insecure</programlisting>
       </example>
 
       <note>
 	<para>An <literal>insecure</literal> console means that you
 	  consider your physical security to the console to be
 	  insecure, and want to make sure only someone who knows the
 	  <username>root</username> password may use single-user mode, and it
 	  does not mean that you want to run your console insecurely.  Thus,
 	  if you want security, choose <literal>insecure</literal>,
 	  not <literal>secure</literal>.</para>
       </note>
     </sect2>
     
     <sect2 id="boot-multiuser">
       <title>Multi-User Mode</title>
       <indexterm><primary>multi-user mode</primary></indexterm>
       
       <para>If &man.init.8; finds your file systems to be
 	in order, or once the user has finished in <link
 	  linkend="boot-singleuser">single-user mode</link>, the
 	system enters multi-user mode, in which it starts the
 	resource configuration of the system.</para>
 
       <sect3 id="boot-rc">
       <indexterm><primary>rc files</primary></indexterm>
 	<title>Resource Configuration (rc)</title>
 
 	<para>The resource configuration system reads in
 	  configuration defaults from
 	  <filename>/etc/defaults/rc.conf</filename>, and
 	  system-specific details from
 	  <filename>/etc/rc.conf</filename>, and then proceeds to
 	  mount the system file systems mentioned in
 	  <filename>/etc/fstab</filename>, start up networking
 	  services, start up miscellaneous system daemons, and
 	  finally runs the startup scripts of locally installed
 	  packages.</para>
 
 	<para>The &man.rc.8; manual page is a good reference to the resource
 	  configuration system, as is examining the scripts
 	  themselves.</para>
       </sect3>
     </sect2>
   </sect1>
 
   <sect1 id="boot-shutdown">
     <title>Shutdown Sequence</title>
     <indexterm>
       <primary><command>shutdown</command></primary>
     </indexterm>
 
     <para>Upon controlled shutdown, via &man.shutdown.8;,
       &man.init.8; will attempt to run the script
       <filename>/etc/rc.shutdown</filename>, and then proceed to send
       all processes the <literal>TERM</literal> signal, and subsequently 
       the <literal>KILL</literal> signal to any that do not terminate 
       timely.</para>
 
     <para>To power down a FreeBSD machine on architectures and systems
       that support power management, simply use the command
       <command>shutdown -p now</command> to turn the power off
       immediately.  To just reboot a FreeBSD system, just use
       <command>shutdown -r now</command>.  You need to be
       <username>root</username> or a member of
       <groupname>operator</groupname> group to run &man.shutdown.8;.
       The &man.halt.8; and &man.reboot.8; commands can also be used,
       please refer to their manual pages and to &man.shutdown.8;'s one
       for more information.</para>
 
     <note>
       <para>Power management requires &man.acpi.4; support in the kernel
 	or loaded as module for FreeBSD&nbsp;5.X and &man.apm.4;
 	support for FreeBSD&nbsp;4.X.</para>
     </note>
 
   </sect1>
 </chapter>
 
 <!-- 
      Local Variables:
      mode: sgml
      sgml-declaration: "../chapter.decl"
      sgml-indent-data: t
      sgml-omittag: nil
      sgml-always-quote-attributes: t
      sgml-parent-document: ("../book.sgml" "part" "chapter")
      End:
 -->
 
diff --git a/zh_TW.Big5/books/handbook/config/chapter.sgml b/zh_TW.Big5/books/handbook/config/chapter.sgml
index f2411afab5..e44551db7a 100644
--- a/zh_TW.Big5/books/handbook/config/chapter.sgml
+++ b/zh_TW.Big5/books/handbook/config/chapter.sgml
@@ -1,3173 +1,3143 @@
 <!--
      The FreeBSD Documentation Project
 
      $FreeBSD$
 -->
 
 <chapter id="config-tuning">
   <chapterinfo>
     <authorgroup>
       <author>
         <firstname>Chern</firstname>
 	<surname>Lee</surname>
 	<contrib>Written by </contrib>
       </author>
     </authorgroup>
     <authorgroup>
       <author>
         <firstname>Mike</firstname>
 	<surname>Smith</surname>
 	<contrib>Based on a tutorial written by </contrib>
       </author>
     </authorgroup>
     <authorgroup>
       <author>
         <firstname>Matt</firstname>
 	<surname>Dillon</surname>
 	<contrib>Also based on tuning(7) written by </contrib>
       </author>
     </authorgroup>
   </chapterinfo>
 
-  <title>Configuration and Tuning</title>
+  <title>³]©w»P®Ä¯à½Õ®Õ(Tuning)</title>
 
   <sect1 id="config-synopsis">
-    <title>Synopsis</title>
+    <title>·§­z</title>
 
     <indexterm><primary>system configuration</primary></indexterm>
     <indexterm><primary>system optimization</primary></indexterm>
 
     <para>One of the important aspects of &os; is system configuration.
       Correct system configuration will help prevent headaches during future upgrades.
       This chapter will explain much of the &os; configuration process,
       including some of the parameters which
       can be set to tune a &os; system.
       </para>
 
-    <para>After reading this chapter, you will know:</para>
+    <para>Ū§¹³o³¹¡A±z±N¤F¸Ñ¡G</para>
 
     <itemizedlist>
       <listitem>
 	<para>How to efficiently work with
 	  file systems and swap partitions.</para>
       </listitem>
       <listitem>
-	<para>The basics of <filename>rc.conf</filename> configuration and
-	  <filename>/usr/local/etc/rc.d</filename> startup systems.</para>
+	<para><filename>rc.conf</filename> ªº³]©w»P <filename>/usr/local/etc/rc.d</filename> ªº±Ò°Ê¬[ºc¡F</para>
       </listitem>
       <listitem>
-	<para>How to configure and test a network card.</para>
+	<para>¦p¦ó³]©w¡B´ú¸Õºô¸ô¥d¡F</para>
       </listitem>
       <listitem>
 	<para>How to configure virtual hosts on your network devices.</para>
       </listitem>
       <listitem>
-	<para>How to use the various configuration files in
-	  <filename>/etc</filename>.</para>
+	<para>¦p¦ó³]©w <filename>/etc</filename> ¤ºªº¦UºØ³]©wÀÉ¡C</para>
       </listitem>
       <listitem>
-        <para>How to tune &os; using <command>sysctl</command>
-          variables.</para>
+        <para>¦p¦ó¥H <command>sysctl</command> ¨Ó½Õ¾ã &os; ªº¨t²Î®Ä¯à¡F</para>
       </listitem>
       <listitem>
-	<para>How to tune disk performance and modify kernel
-	  limitations.</para>
+	<para>¦p¦ó½Õ¾ãµwºÐ®Ä¯à¡A¥H¤Î§ó§ï kernel ­­¨î¡C</para>
       </listitem>
     </itemizedlist>
 
-    <para>Before reading this chapter, you should:</para>
+    <para>¦b¾\Ū³o³¹¤§«e¡A±zÀ³·í¤F¸Ñ¡G</para>
 
     <itemizedlist>
       <listitem>
 	<para>Understand &unix; and &os; basics (<xref
 	    linkend="basics">).</para>
       </listitem>
       <listitem>
 	<para>Be familiar with the basics of kernel configuration/compilation
 	  (<xref linkend="kernelconfig">).</para>
       </listitem>
     </itemizedlist>
   </sect1>
 
   <sect1 id="configtuning-initial">
-    <title>Initial Configuration</title>
+    <title>¤@¶}©lªº³W¹º</title>
 
     <sect2>
-      <title>Partition Layout</title>
+      <title>³W¹º¤À³Î°Ï(Partition)</title>
 
       <indexterm><primary>partition layout</primary></indexterm>
       <indexterm>
         <primary><filename>/etc</filename></primary>
       </indexterm>
       <indexterm>
         <primary><filename>/var</filename></primary>
       </indexterm>
       <indexterm>
         <primary><filename>/usr</filename></primary>
       </indexterm>
 
       <sect3>
 	<title>Base Partitions</title>
 
 	<para>When laying out file systems with &man.disklabel.8;
 	  or &man.sysinstall.8;, remember that hard
 	  drives transfer data faster from the outer
 	  tracks to the inner.
 	  Thus smaller and heavier-accessed file systems
 	  should be closer to the outside of the drive, while
 	  larger partitions like <filename>/usr</filename> should be placed
 	  toward the inner.  It is a good idea to create
 	  partitions in a similar order to: root, swap,
 	  <filename>/var</filename>, <filename>/usr</filename>.</para>
 
 	<para>The size of <filename>/var</filename>
 	  reflects the intended machine usage.
 	  <filename>/var</filename> is used to hold
 	  mailboxes, log files, and printer spools.  Mailboxes and log
 	  files can grow to unexpected sizes depending
 	  on how many users exist and how long log
 	  files are kept.  Most users would never require a gigabyte,
 	  but remember that <filename>/var/tmp</filename>
 	  must be large enough to contain packages.
 	  </para>
 
 	<para>The <filename>/usr</filename> partition holds much
 	  of the files required to support the system, the &man.ports.7;
 	  collection (recommended) and the source code (optional).  Both
 	  of which are optional at install time.
 	  At least 2 gigabytes would be recommended for this partition.</para>
 
 	<para>When selecting partition sizes, keep the space
 	  requirements in mind.  Running out of space in
 	  one partition while barely using another can be a
 	  hassle.</para>
 
 	<note><para>Some users have found that &man.sysinstall.8;'s
 	    <literal>Auto-defaults</literal> partition sizer will
 	    sometimes select smaller than adequate <filename>/var</filename>
 	    and <filename>/</filename> partitions.  Partition wisely and
 	    generously.</para></note>
 
       </sect3>
 
       <sect3 id="swap-design">
 	<title>Swap Partition</title>
 
 	<indexterm><primary>swap sizing</primary></indexterm>
 	<indexterm><primary>swap partition</primary></indexterm>
 
 	<para>As a rule of thumb, the swap partition should be
 	  about double the size of system memory (RAM).  For example,
 	  if the machine has 128&nbsp;megabytes of memory,
 	  the swap file should be 256&nbsp;megabytes.  Systems with
 	  less memory may perform better with more swap.
 	  Less than 256&nbsp;megabytes of swap is not recommended and
 	  memory expansion should be considered.
 	  The kernel's VM paging algorithms are tuned to
 	  perform best when the swap partition is at least two times the
 	  size of main memory.  Configuring too little swap can lead to
 	  inefficiencies in the VM page scanning code and might create
 	  issues later if more memory is added.</para>
 
 	<para>On larger systems with multiple SCSI disks (or
 	  multiple IDE disks operating on different controllers), it is
 	  recommend that a swap is configured on each drive (up
 	  to four drives).  The swap partitions should be
 	  approximately the same size.  The kernel can handle arbitrary
 	  sizes but internal data structures scale to 4 times the
 	  largest swap partition.  Keeping the swap partitions near the
 	  same size will allow the kernel to optimally stripe swap space
 	  across disks.
 	  Large swap sizes are fine, even if swap is not
 	  used much.  It might be easier to recover
 	  from a runaway program before being forced to reboot.</para>
       </sect3>
 
       <sect3>
-	<title>Why Partition?</title>
+	<title>¬°¦ó­n³W¹º Partition¡H</title>
 
 	<para>Several users think a single large partition will be fine,
 	  but there are several reasons why this is a bad idea.
 	  First, each partition has different operational
 	  characteristics and separating them allows the file system to
 	  tune accordingly.  For example, the root
 	  and <filename>/usr</filename> partitions are read-mostly, without
 	  much writing.  While a lot of reading and writing could
 	  occur in <filename>/var</filename> and
 	  <filename>/var/tmp</filename>.</para>
 
 	<para>By properly partitioning a system, fragmentation
 	  introduced in the smaller write heavy partitions
 	  will not bleed over into the mostly-read partitions.
 	  Keeping the write-loaded partitions closer to
 	  the disk's edge,
 	  will
 	  increase I/O performance in the partitions where it occurs
 	  the most.  Now while I/O
 	  performance in the larger partitions may be needed,
 	  shifting them more toward the edge of the disk will not
 	  lead to a significant performance improvement over moving
 	  <filename>/var</filename> to the edge.
 	  Finally, there are safety concerns.  A smaller, neater root
 	  partition which is mostly read-only has a greater
 	  chance of surviving a bad crash.</para>
       </sect3>
     </sect2>
 
   </sect1>
 
   <sect1 id="configtuning-core-configuration">
-    <title>Core Configuration</title>
+    <title>³Ì¥D­nªº³]©wÀÉ</title>
 
     <indexterm>
       <primary>rc files</primary>
       <secondary><filename>rc.conf</filename></secondary>
     </indexterm>
 
     <para>The principal location for system configuration information
       is within <filename>/etc/rc.conf</filename>.  This file
       contains a wide range of configuration information, principally
       used at system startup to configure the system.  Its name
       directly implies this; it is configuration information for the
       <filename>rc*</filename> files.</para>
 
     <para>An administrator should make entries in the
       <filename>rc.conf</filename> file to
       override the default settings from
       <filename>/etc/defaults/rc.conf</filename>.  The defaults file
       should not be copied verbatim to <filename>/etc</filename> - it
       contains default values, not examples.  All system-specific
       changes should be made in the <filename>rc.conf</filename>
       file itself.</para>
 
     <para>A number of strategies may be applied in clustered
       applications to separate site-wide configuration from
       system-specific configuration in order to keep administration
       overhead down.  The recommended approach is to place site-wide
       configuration into another file,
       such as <filename>/etc/rc.conf.site</filename>, and then include
       this file into <filename>/etc/rc.conf</filename>, which will
       contain only system-specific information.</para>
 
     <para>As <filename>rc.conf</filename> is read by &man.sh.1; it is
       trivial to achieve this.  For example:</para>
 
     <itemizedlist>
       <listitem><para>rc.conf:</para>
 <programlisting>	. /etc/rc.conf.site
 	hostname="node15.example.com"
 	network_interfaces="fxp0 lo0"
 	ifconfig_fxp0="inet 10.1.1.1"</programlisting></listitem>
       <listitem><para>rc.conf.site:</para>
 <programlisting>	defaultrouter="10.1.1.254"
 	saver="daemon"
 	blanktime="100"</programlisting></listitem>
     </itemizedlist>
 
     <para>The <filename>rc.conf.site</filename> file can then be
       distributed to every system using <command>rsync</command> or a
       similar program, while the <filename>rc.conf</filename> file
       remains unique.</para>
 
     <para>Upgrading the system using &man.sysinstall.8;
       or <command>make world</command> will not overwrite the
       <filename>rc.conf</filename>
       file, so system configuration information will not be lost.</para>
 
   </sect1>
 
   <sect1 id="configtuning-appconfig">
-    <title>Application Configuration</title>
+    <title>¦U¦¡À³¥Îµ{¦¡ªº³]©wÀÉ</title>
 
     <para>Typically, installed applications have their own
       configuration files, with their own syntax, etc.  It is
       important that these files be kept separate from the base
       system, so that they may be easily located and managed by the
       package management tools.</para>
 
     <indexterm><primary>/usr/local/etc</primary></indexterm>
 
     <para>Typically, these files are installed in
       <filename>/usr/local/etc</filename>.  In the case where an
       application has a large number of configuration files, a
       subdirectory will be created to hold them.</para>
 
     <para>Normally, when a port or package is installed, sample
       configuration files are also installed.  These are usually
       identified with a <filename>.default</filename> suffix.  If there
       are no existing
       configuration files for the application, they will be created by
       copying the <filename>.default</filename> files.</para>
 
     <para>For example, consider the contents of the directory
     <filename>/usr/local/etc/apache</filename>:</para>
 
 <literallayout class="monospaced">-rw-r--r--  1 root  wheel   2184 May 20  1998 access.conf
 -rw-r--r--  1 root  wheel   2184 May 20  1998 access.conf.default
 -rw-r--r--  1 root  wheel   9555 May 20  1998 httpd.conf
 -rw-r--r--  1 root  wheel   9555 May 20  1998 httpd.conf.default
 -rw-r--r--  1 root  wheel  12205 May 20  1998 magic
 -rw-r--r--  1 root  wheel  12205 May 20  1998 magic.default
 -rw-r--r--  1 root  wheel   2700 May 20  1998 mime.types
 -rw-r--r--  1 root  wheel   2700 May 20  1998 mime.types.default
 -rw-r--r--  1 root  wheel   7980 May 20  1998 srm.conf
 -rw-r--r--  1 root  wheel   7933 May 20  1998 srm.conf.default</literallayout>
 
     <para>The file sizes show that only the <filename>srm.conf</filename>
       file has been changed.  A later update of the <application>Apache</application> port would not
       overwrite this changed file.</para>
 
   </sect1>
 
   <sect1 id="configtuning-starting-services">
     <sect1info>
       <authorgroup>
         <author>
 	<firstname>Tom</firstname>
 	<surname>Rhodes</surname>
 	<contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
     </sect1info>
 
-    <title>Starting Services</title>
+    <title>¦UºØ Services ªº±Ò°Ê¤è¦¡</title>
 
     <indexterm><primary>services</primary></indexterm>
 
     <para>Many users choose to install third party software on &os;
       from the Ports Collection.  In many of these situations it
       may be necessary to configure the software in a manner which
       will allow it to be started upon system initialization.  Services,
       such as <filename role="package">mail/postfix</filename> or
       <filename role="package">www/apache13</filename> are just two
       of the many software packages which may be started during system
       initialization.  This section explains the procedures available
       for starting third party software.</para>
 
     <para>In &os;, most included services, such as &man.cron.8;, are
       started through the system start up scripts.  These scripts may
       differ depending on &os; or vendor version; however, the most
       important aspect to consider is that their start up configuration
       can be handled through simple startup scripts.</para>
 
-    <para>Before the advent of rcNG, applications would drop a
+    <para>Before the advent of <filename>rc.d</filename>, applications would drop a
       simple start up script into the
       <filename class="directory">/usr/local/etc/rc.d</filename>
       directory which would be read by the system initialization
       scripts.  These scripts would then be executed during the latter
       stages of system start up.</para>
 
     <para>While many individuals have spent hours trying to merge the
       old configuration style into the new system, the fact remains
       that some third party utilities still require a script simply
       dropped into the aforementioned directory.  The subtle differences
-      in the scripts depend whether or not rcNG is being used.  Prior
+      in the scripts depend whether or not <filename>rc.d</filename> is being used.  Prior
       to &os;&nbsp;5.1 the old configuration style is used and in
       almost all cases a new style script would do just fine.</para>
 
     <para>While every script must meet some minimal requirements, most
       of the time these requirements are &os; version
       agnostic.  Each script must have a <filename>.sh</filename>
       extension appended to the end and every script must be
       executable by the system.  The latter may be achieved by using
       the <command>chmod</command> command and setting the unique permissions
       of <literal>755</literal>.  There should also be, at minimal,
       an option to <literal>start</literal> the application and an
       option to <literal>stop</literal> the application.</para>
 
     <para>The simplest start up script would probably look a little
       bit like this one:</para>
 
     <programlisting>#!/bin/sh
 echo -n ' utility'
 
 case "$1" in
 start)
         /usr/local/bin/utility
         ;;
 stop)
         kill -9 `cat /var/run/utility.pid`
         ;;
 *)
         echo "Usage: `basename $0` {start|stop}" >&2
         exit 64
         ;;
 esac
 
 exit 0</programlisting>
 
     <para>This script provides for a <literal>stop</literal> and
       <literal>start</literal> option for
       the application hereto referred simply as
       <literal>utility</literal>.</para>
 
     <para>Could be started manually with:</para>
 
     <screen>&prompt.root; <userinput><filename>/usr/local/etc/rc.d/utility.sh</filename> start</userinput></screen>
 
     <para>While not all third party software requires the line in
       <filename>rc.conf</filename>, almost every day a new port will
       be modified to accept this configuration.  Check the final output
       of the installation for more information on a specific
       application.  Some third party software will provide start up
       scripts which permit the application to be used with
-      rcNG; although, this will be discussed in the next section.</para>
+      <filename>rc.d</filename>; although, this will be discussed in the next section.</para>
 
     <sect2>
       <title>Extended Application Configuration</title>
 
-      <para>Now that &os; includes rcNG, configuration of application
-	start up has become more optimal; indeed, it has become a bit
-	more in depth.  Using the key words discussed in the
-	<link linkend="configtuning-rcNG">rcNG</link> section,
+      <para>Now that &os; includes <filename>rc.d</filename>, configuration
+	of application startup has become easier, and more
+	featureful.  Using the key words discussed in the
+	<link linkend="configtuning-rcd">rc.d</link> section,
 	applications may now be set to start after certain other
 	services for example <acronym>DNS</acronym>; may permit extra
 	flags to be passed through <filename>rc.conf</filename> in
 	place of hard coded flags in the start up script, etc.  A
 	basic script may look similar to the following:</para>
 
       <programlisting>#!/bin/sh
 #
 # PROVIDE: utility
 # REQUIRE: DAEMON
-# BEFORE: LOGIN
-# KEYWORD: FreeBSD shutdown
+# KEYWORD: shutdown
 
 #
 # DO NOT CHANGE THESE DEFAULT VALUES HERE
 # SET THEM IN THE /etc/rc.conf FILE
 #
 utility_enable=${utility_enable-"NO"}
 utility_flags=${utility_flags-""}
 utility_pidfile=${utility_pidfile-"/var/run/utility.pid"}
 
 . /etc/rc.subr
 
 name="utility"
 rcvar=`set_rcvar`
 command="/usr/local/sbin/utility"
 
 load_rc_config $name
 
 pidfile="${utility_pidfile}"
 
 start_cmd="echo \"Starting ${name}.\"; /usr/bin/nice -5 ${command} ${utility_flags} ${command_args}"
 
 run_rc_command "$1"</programlisting>
 
       <para>This script will ensure that the provided
-	<application>utility</application> will be started before the
-	<literal>login</literal> service but after the
+	<application>utility</application> will be started after the
 	<literal>daemon</literal> service.  It also provides a method
 	for setting and tracking the <acronym>PID</acronym>, or process
 	<acronym>ID</acronym> file.</para>
 
       <para>This application could then have the following line placed
 	in <filename>/etc/rc.conf</filename>:</para>
 
       <programlisting>utility_enable="YES"</programlisting>
 
       <para>This new method also allows for easier manipulation of the
 	command line arguments, inclusion of the default functions
 	provided in <filename>/etc/rc.subr</filename>, compatibility
-	with the &man.rcorder.8; utility and provide for easier
-	configuration via the <filename>rc.conf</filename> file.  In
-	essence, this script could even be placed in
-	<filename class="directory">/etc/rc.d</filename> directory.
-	Yet, that has the potential to upset the &man.mergemaster.8;
-	utility when used in conjunction with software upgrades.</para>
+	with the &man.rcorder.8; utility and provides for easier
+	configuration via the <filename>rc.conf</filename> file.</para>
     </sect2>
 
     <sect2>
-      <title>Using Services to Start Services</title>
+      <title>¥H Services ¨Ó±Ò°Ê¦U¦¡ Services</title>
 
       <para>Other services, such as <acronym>POP</acronym>3 server
 	daemons, <acronym>IMAP</acronym>, etc. could be started using
 	the &man.inetd.8;.  This involves installing the service
 	utility from the Ports Collection with a configuration line
 	appended to the <filename>/etc/inetd.conf</filename> file,
 	or uncommenting one of the current configuration lines.  Working
 	with <application>inetd</application> and its configuration is
 	described in depth in the
 	<link linkend="network-inetd">inetd</link> section.</para>
 
       <para>In some cases, it may be more plausible to use the
 	&man.cron.8; daemon to start system services.  This approach
 	has a number of advantages because <command>cron</command> runs
 	these processes as the <filename>crontab</filename>'s file
 	owner.  This allows regular users to start and maintain some
 	applications.</para>
 
       <para>The <command>cron</command> utility provides a unique
 	feature, <literal>@reboot</literal>, which may be used in place
 	of the time specification.  This will cause the job to be run
 	when &man.cron.8; is started, normally during system
 	initialization.</para>
 
     </sect2>
   </sect1>
 
   <sect1 id="configtuning-cron">
     <sect1info>
       <authorgroup>
         <author>
 	<firstname>Tom</firstname>
 	<surname>Rhodes</surname>
 	<contrib>Contributed by </contrib>
 	<!-- 20 May 2003 -->
 	</author>
       </authorgroup>
     </sect1info>
-    <title>Configuring the <command>cron</command> Utility</title>
+    <title>³]©w <command>cron</command></title>
 
     <indexterm><primary>cron</primary>
       <secondary>configuration</secondary></indexterm>
 
-    <para>One of the most useful utilities in &os; is &man.cron.8;.  The
-      <command>cron</command> utility runs in the background and constantly
-      checks the <filename>/etc/crontab</filename> file.  The <command>cron</command>
-      utility also checks the <filename>/var/cron/tabs</filename> directory, in
-      search of new <filename>crontab</filename> files.  These
-      <filename>crontab</filename> files store information about specific
-      functions which <command>cron</command> is supposed to perform at
-      certain times.</para>
-
-    <para>The <command>cron</command> utility uses two different
-      types of configuration files, the system crontab and user crontabs. The
-      only difference between these two formats is the sixth field.  In the
+    <para>&os; ³Ì¦n¥Îªº¤u¨ã¤§¤@´N¬O &man.cron.8;¡C
+      <command>cron</command> ·|¦b­I´º¤U¹B§@¡A¨Ã¤£Â_Àˬd 
+      <filename>/etc/crontab</filename> ÀÉ¥H¤Î <filename>/var/cron/tabs</filename> ¥Ø¿ý¡A¨Ó·j´M¬O§_¦³·s <filename>crontab</filename> ÀɮסC
+      ³o¨Ç <filename>crontab</filename> ÀÉ·|¦s©ñ¤@¨Ç±Æµ{¤u§@ªº³]©w¡A¨Óµ¹ <command>cron</command> °õ¦æ¡C</para>
+
+    <para><command>cron</command> µ{¦¡¡A¥i¦P®É±Ä¥Î¨âºØ¤£¦PÃþ«¬ªº³]©wÀÉ¡G¨t²Î¥»¨­ªº crontab 
+    	¤Î¨Ï¥ÎªÌ¥»¨­ªº crontab¡C¦Ó¨âºØ®æ¦¡°ß¤@®t§O¦b©ó²Ä¤»Ä檺¤£¦P¡FIn the
       system crontab, the sixth field is the name of a user for the command
       to run as. This gives the system crontab the ability to run commands
       as any user. In a user crontab, the sixth field is the command to run,
       and all commands run as the user who created the crontab; this is an
       important security feature.</para>
 
     <note>
       <para>User crontabs allow individual users to schedule tasks without the 
         need for <username>root</username> privileges. Commands in a user's crontab run with the 
         permissions of the user who owns the crontab.</para>
 
       <para>The <username>root</username> user can have a user crontab just like
         any other user. This one is different from
         <filename>/etc/crontab</filename> (the system crontab). Because of the
         system crontab, there is usually no need to create a user crontab
         for <username>root</username>.</para>
     </note>
 
     <para>Let us take a look at the <filename>/etc/crontab</filename> file
       (the system crontab):</para>
 
 
     <programlisting># /etc/crontab - root's crontab for &os;
 #
 # &dollar;&os;: src/etc/crontab,v 1.32 2002/11/22 16:13:39 tom Exp &dollar;
 # <co id="co-comments">
 #
 SHELL=/bin/sh
 PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin <co id="co-env">
 HOME=/var/log
 #
 #
 #minute	hour	mday	month	wday	who	command <co id="co-field-descr">
 #
 #
 */5	*	*	*	*	root	/usr/libexec/atrun <co id="co-main">
 </programlisting>
 
     <calloutlist>
       <callout arearefs="co-comments">
 	<para>Like most &os; configuration files, the <literal>#</literal>
 	  character represents a comment.  A comment can be placed in
 	  the file as a reminder of what and why a desired action is performed.
 	  Comments cannot be on the same line as a command or else they will
 	  be interpreted as part of the command; they must be on a new line.
 	  Blank lines are ignored.</para>
       </callout>
 
       <callout arearefs="co-env">
 	<para>First, the environment must be defined.  The equals
 	  (<literal>=</literal>) character is used to define any environment
 	  settings, as with this example where it is used for the <envar>SHELL</envar>,
 	  <envar>PATH</envar>, and <envar>HOME</envar> options.  If the shell line is
 	  omitted, <command>cron</command> will use the default, which is
 	  <command>sh</command>.  If the <envar>PATH</envar> variable is
 	  omitted, no default will be used and file locations will need to
 	  be absolute.  If <envar>HOME</envar> is omitted, <command>cron</command>
 	  will use the invoking users home directory.</para>
       </callout>
 
       <callout arearefs="co-field-descr">
 	<para>This line defines a total of seven fields.  Listed here are the
 	  values <literal>minute</literal>, <literal>hour</literal>,
 	  <literal>mday</literal>, <literal>month</literal>, <literal>wday</literal>,
 	  <literal>who</literal>, and <literal>command</literal>.  These
 	  are almost all self explanatory.  <literal>minute</literal> is the time in minutes the
 	  command will be run.  <literal>hour</literal> is similar to the <literal>minute</literal> option, just in
 	  hours.  <literal>mday</literal> stands for day of the month.  <literal>month</literal> is similar to <literal>hour</literal>
 	  and <literal>minute</literal>, as it designates the month.  The <literal>wday</literal> option stands for
 	  day of the week.  All these fields must be numeric values, and follow
 	  the twenty-four hour clock.  The <literal>who</literal> field is special,
 	  and only exists in the <filename>/etc/crontab</filename> file.
 	  This field specifies which user the command should be run as.
 	  When a user installs his or her <filename>crontab</filename> file, they
 	  will not have this option. Finally, the <literal>command</literal> option is listed.
 	  This is the last field, so naturally it should designate the command
 	  to be executed.</para>
       </callout>
 
       <callout arearefs="co-main">
 	<para>This last line will define the values discussed above.  Notice here
 	  we have a <literal>*/5</literal> listing, followed by several more
 	  <literal>*</literal> characters.  These <literal>*</literal> characters
 	  mean <quote>first-last</quote>, and can be interpreted as
 	  <emphasis>every</emphasis> time.  So, judging by this line,
 	  it is apparent that the <command>atrun</command> command is to be invoked by
 	  <username>root</username> every five minutes regardless of what
 	  day or month it is.  For more information on the <command>atrun</command> command,
 	  see the &man.atrun.8; manual page.</para>
 
 	<para>Commands can have any number of flags passed to them; however,
 	  commands which extend to multiple lines need to be broken with the backslash
 	  <quote>\</quote> continuation character.</para>
       </callout>
     </calloutlist>
 
     <para>This is the basic set up for every
       <filename>crontab</filename> file, although there is one thing
       different about this one.  Field number six, where we specified
       the username, only exists in the system
       <filename>/etc/crontab</filename> file.  This field should be
       omitted for individual user <filename>crontab</filename>
       files.</para>
 
 
     <sect2 id="configtuning-installcrontab">
-      <title>Installing a Crontab</title>
+      <title>¤u§@±Æµ{(Crontab)ªº±Æ©w»PºÞ²z</title>
 
       <important>
       <para>You must not use the procedure described here to
         edit/install the system crontab. Simply use your favorite
         editor: the <command>cron</command> utility will notice that the file
         has changed and immediately begin using the updated version. 
         See
         <ulink url="&url.books.faq;/admin.html#ROOT-NOT-FOUND-CRON-ERRORS">
         this FAQ entry </ulink> for more information.</para>
       </important>
 
       <para>To install a freshly written user
 	<filename>crontab</filename>, first use your favorite editor to create
 	a file in the proper format, and then use the
 	<command>crontab</command> utility.  The most common usage
 	is:</para>
 
       <screen>&prompt.user; <userinput>crontab crontab-file</userinput></screen>
       
       <para>In this example, <filename>crontab-file</filename> is the filename
     of a <filename>crontab</filename> that was previously created.</para>
 
       <para>There is also an option to list installed
 	<filename>crontab</filename> files: just pass the
 	<option>-l</option> option to <command>crontab</command> and look
 	over the output.</para>
 
       <para>For users who wish to begin their own crontab file from scratch,
 	without the use of a template, the <command>crontab -e</command>
 	option is available.  This will invoke the selected editor
 	with an empty file.  When the file is saved, it will be
 	automatically installed by the <command>crontab</command> command.
       </para>
       
       <para>If you later want to remove your user <filename>crontab</filename>
 	completely, use <command>crontab</command> with the <option>-r</option>
 	option.
       </para>
 
     </sect2>
   </sect1>
 
-  <sect1 id="configtuning-rcNG">
+  <sect1 id="configtuning-rcd">
     <sect1info>
       <authorgroup>
         <author>
 	 <firstname>Tom</firstname>
 	 <surname>Rhodes</surname>
 	 <contrib>Contributed by </contrib>
 	 <!-- 16 May 2003 -->
         </author>
       </authorgroup>
     </sect1info>
 
-    <title>Using rc under &os; 5.X and newer</title>
+    <title>¦b &os; 5.X (§t¤§«á) ¨Ï¥Î rc</title>
 
-    <para>&os; has recently integrated the NetBSD
-      <filename>rc.d</filename> system for system initialization.
-      Users should notice the files listed in the
-      <filename>/etc/rc.d</filename> directory.  Many of these files
-      are for basic services which can be controlled with the
-      <option>start</option>, <option>stop</option>,
-      and <option>restart</option> options.
-      For instance, &man.sshd.8; can be restarted with the following
-      command:</para>
+    <para>±q 2002 ¦~°_¡A&os; ¾ã¦X¤F NetBSD ªº <filename>rc.d</filename> ¾÷¨î¨Ó§@¬°¨t²ÎªA°È±Ò°Ê¾÷¨î¡C
+      ¥i¥H¨ì <filename>/etc/rc.d</filename> ¥Ø¿ý¤U¥h¬Ý¡A«Ü¦hÀɮ׳£¬O°ò¥»ªA°È¡A¥i¥H¥Î <option>start</option>, <option>stop</option> 
+      ¤Î <option>restart</option> §@¬°¨Ï¥Î®Éªº¿ï¶µ¡C
+      Á|­Ó¨Ò¤l¡A¥i¥H¥Î¤U¦C«ü¥O¨Ó­«·s±Ò°Ê &man.sshd.8;¡G</para>
 
     <screen>&prompt.root; <userinput>/etc/rc.d/sshd restart</userinput></screen>
 
-    <para>This procedure is similar for other services.  Of course,
-      services are usually started automatically as specified in
-      &man.rc.conf.5;.  For example, enabling the Network Address
-      Translation daemon at startup is as simple as adding the
-      following line to <filename>/etc/rc.conf</filename>:</para>
+    <para>¨ä¥LªA°È¤]¬OÃþ¦ü§@ªk¡C·íµM¡A
+      ªA°È³q±`¥u­n¦b &man.rc.conf.5; ¤º¦³«ü©wªº¸Ü¡A³£·|¦b¶}¾÷®É´N¦Û°Ê±Ò°Ê¡CÁ|¨Ò¨Ó»¡¡A­Y­n¶}¾÷®É±Ò°Ê NAT(Network Address
+      Translation) daemon ªº¸Ü¡A¥u­n¦b <filename>/etc/rc.conf</filename> ¤º¥[¤W¤U¦C³o¦æ§Y¥i¡G</para>
 
     <programlisting>natd_enable="YES"</programlisting>
 
-    <para>If a <option>natd_enable="NO"</option> line is already
-       present, then simply change the <option>NO</option> to
-       <option>YES</option>.  The rc scripts will automatically load
-       any other dependent services during the next reboot, as
-       described below.</para>
+    <para>­Y­ì¥»¼gªº¬O <option>natd_enable="NO"</option> ¨º»ò¥u­n§â <option>NO</option> §ï¬°
+       <option>YES</option> ´N¦n¤F¡Crc scripts ·|¦b¤U¦¸­«¶}¾÷®É¡A¦Û°Ê¸ü¤J¬ÛÃö(¦³¬Û¨Ì)ªºªA°È¡A¥H¤U§Ú­Ì·|Á¿¨ì³o³¡¤À¡C</para>
 
     <para>Since the <filename>rc.d</filename> system is primarily
       intended to start/stop services at system startup/shutdown time,
       the standard <option>start</option>,
       <option>stop</option> and <option>restart</option> options will only
       perform their action if the appropriate
       <filename>/etc/rc.conf</filename> variables are set.  For
       instance the above <command>sshd restart</command> command will
       only work if <varname>sshd_enable</varname> is set to
       <option>YES</option> in <filename>/etc/rc.conf</filename>.  To
       <option>start</option>, <option>stop</option> or
       <option>restart</option> a service regardless of the settings in
       <filename>/etc/rc.conf</filename>, the commands should be
       prefixed with <quote>force</quote>.  For instance to restart
       <command>sshd</command> regardless of the current
       <filename>/etc/rc.conf</filename> setting, execute the following
       command:</para>
 
     <screen>&prompt.root; <userinput>/etc/rc.d/sshd forcerestart</userinput></screen>
 
     <para>It is easy to check if a service is enabled in
       <filename>/etc/rc.conf</filename> by running the appropriate
       <filename>rc.d</filename> script with the option
       <option>rcvar</option>.  Thus, an administrator can check that
       <command>sshd</command> is in fact enabled in
       <filename>/etc/rc.conf</filename> by running:</para>
 
     <screen>&prompt.root; <userinput>/etc/rc.d/sshd rcvar</userinput>
 # sshd
 $sshd_enable=YES</screen>
 
     <note>
       <para>The second line (<literal># sshd</literal>) is the output
         from the <command>sshd</command> command, not a <username>root</username>
         console.</para>
     </note>
 
-    <para>To determine if a service is running, a
-      <option>status</option> option is available.  For instance to
-      verify that <command>sshd</command> is actually started:</para>
+    <para>­Y­nÀˬdªA°È¬O§_¦³¦b¹B§@¡A¥i¥H¥Î <option>status</option> ¿ï¶µ¨Ó¬d¸ß¡C¤ñ¦p¡G­Y­n½T»{ 
+    	<command>sshd</command> ¬O§_¯uªº¦³±Ò°Êªº¸Ü¡A¨º»ò¥´¡G</para>
 
     <screen>&prompt.root; <userinput>/etc/rc.d/sshd status</userinput>
 sshd is running as pid 433.</screen>
 
-    <para>It is also possible to <option>reload</option> a service.
+    <para>In some cases it is also possible to <option>reload</option> a service.
       This will attempt to send a signal to an individual service, forcing the
       service to reload its configuration files.  In most cases this
       means sending the service a <literal>SIGHUP</literal>
-      signal.</para>
+      signal. Support for this feature is not included for every service.</para>
 
     <para>The <filename>rc.d</filename> system is not only used for network services, it also
       contributes to most of the system initialization.  For
       instance, consider the <filename>bgfsck</filename> file.  When
       this script is executed, it will print out the following
       message:</para>
 
     <screen>Starting background file system checks in 60 seconds.</screen>
 
     <para>Therefore this file is used for background file system
       checks, which are done only during system initialization.</para>
 
     <para>Many system services depend on other services to function
       properly.  For example, NIS and other RPC-based services may
       fail to start until after the <command>rpcbind</command>
       (portmapper) service has started.  To resolve this issue,
       information about dependencies and other meta-data is included
       in the comments at the top of each startup script.  The
       &man.rcorder.8; program is then used to parse these comments
       during system initialization to determine the order in which
       system services should be invoked to satisfy the dependencies.
       The following words may be included at the top of each startup
       file:</para>
 
     <itemizedlist>
       <listitem>
 	<para><literal>PROVIDE</literal>: Specifies the services this file provides.</para>
       </listitem>
 
       <listitem>
 	<para><literal>REQUIRE</literal>: Lists services which are required for this
 	  service.  This file will run <emphasis>after</emphasis>
 	  the specified services.</para>
       </listitem>
 
       <listitem>
 	<para><literal>BEFORE</literal>: Lists services which depend on this service.
 	  This file will run <emphasis>before</emphasis>
 	  the specified services.</para>
       </listitem>
-
-      <listitem>
-	<para>KEYWORD: &os; or NetBSD.  This is used for *BSD dependent features.</para>
-      </listitem>
     </itemizedlist>
 
     <para>By using this method, an administrator can easily control system
       services without the hassle of <quote>runlevels</quote> like
       some other &unix; operating systems.</para>
 
     <para>Additional information about the
       <filename>rc.d</filename> system can be found in the &man.rc.8;
       and &man.rc.subr.8; manual pages.</para>
   </sect1>
 
   <sect1 id="config-network-setup">
     <sect1info>
       <authorgroup>
         <author>
 	 <firstname>Marc</firstname>
 	 <surname>Fonvieille</surname>
 	 <contrib>Contributed by </contrib>
 	 <!-- 6 October 2002 -->
         </author>
       </authorgroup>
     </sect1info>
 
-    <title>Setting Up Network Interface Cards</title>
+    <title>³]©wºô¸ô¥d</title>
 
     <indexterm>
       <primary>network cards</primary>
       <secondary>configuration</secondary>
     </indexterm>
 
     <para>Nowadays we can not think about a computer without thinking
       about a network connection.  Adding and configuring a network
       card is a common task for any &os; administrator.</para>
 
     <sect2>
-      <title>Locating the Correct Driver</title>
+      <title>¿ï¾Ü¥¿½T¡B¥i¥ÎªºÅX°Êµ{¦¡(Driver)</title>
 
       <indexterm>
 	<primary>network cards</primary>
 	<secondary>driver</secondary>
       </indexterm>
 
       <para>Before you begin, you should know the model of the card
 	you have, the chip it uses, and whether it is a PCI or ISA card.
 	&os; supports a wide variety of both PCI and ISA cards.
 	Check the Hardware Compatibility List for your release to see
 	if your card is supported.</para>
 
       <para>Once you are sure your card is supported, you need
 	to determine the proper driver for the card.
 	<filename>/usr/src/sys/conf/NOTES</filename> and
 	<filename>/usr/src/sys/<replaceable>arch</replaceable>/conf/NOTES</filename> will give you
 	the list of network interface drivers with some information
 	about the supported chipsets/cards.  If you have doubts about
 	which driver is the correct one, read the manual page of the
 	driver.  The manual page will give you more information about
 	the supported hardware and even the possible problems that
 	could occur.</para>
 
       <note>
 	<para><filename>NOTES</filename> does not exist on
 	  &os;&nbsp;4.X.  Instead, check the <filename>LINT</filename>
 	  file for information about various network interfaces.  See
 	  <xref linkend="kernelconfig-config"> for a more detailed
 	  summary of <filename>NOTES</filename> versus
 	<filename>LINT</filename>.</para>
       </note>
 
       <para>If you own a common card, most of the time you will not
 	have to look very hard for a driver.  Drivers for common
 	network cards are present in the <filename>GENERIC</filename>
 	kernel, so your card should show up during boot, like so:</para>
 
 <screen>dc0: &lt;82c169 PNIC 10/100BaseTX&gt; port 0xa000-0xa0ff mem 0xd3800000-0xd38
 000ff irq 15 at device 11.0 on pci0
 dc0: Ethernet address: 00:a0:cc:da:da:da
 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
 dc1: &lt;82c169 PNIC 10/100BaseTX&gt; port 0x9800-0x98ff mem 0xd3000000-0xd30
 000ff irq 11 at device 12.0 on pci0
 dc1: Ethernet address: 00:a0:cc:da:da:db
 miibus1: &lt;MII bus&gt; on dc1
 ukphy1: &lt;Generic IEEE 802.3u media interface&gt; on miibus1
 ukphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto</screen>
 
       <para>In this example, we see that two cards using the &man.dc.4;
 	driver are present on the system.</para>
 
       <para>If the driver for your NIC is not present in
 	<filename>GENERIC</filename>, you will need to load the proper
 	driver to use your NIC.  This may be accomplished in one of
 	two ways:</para>
 
       <itemizedlist>
         <listitem>
 	  <para>The easiest way is to simply load a kernel module for
 	    your network card with &man.kldload.8;.  Not all NIC
 	    drivers are available as modules; notable examples of
 	    devices for which modules do not exist are ISA cards.</para>
 	</listitem>
 
 	<listitem>
 	  <para>Alternatively, you may statically compile the support
 	    for your card into your kernel.  Check
 	    <filename>/usr/src/sys/conf/NOTES</filename>,
 	    <filename>/usr/src/sys/<replaceable>arch</replaceable>/conf/NOTES</filename>
 	    and the manual page of the driver to know what to add in
 	    your kernel configuration file.  For more information
 	    about recompiling your kernel, please see <xref
 	    linkend="kernelconfig">.  If your card was detected at
 	    boot by your kernel (<filename>GENERIC</filename>) you do
 	    not have to build a new kernel.</para>
 	</listitem>
       </itemizedlist>
     </sect2>
 
     <sect2>
-      <title>Configuring the Network Card</title>
+      <title>³]©wºô¸ô¥d</title>
 
       <indexterm>
 	<primary>network cards</primary>
 	<secondary>configuration</secondary>
       </indexterm>
 
       <para>Once the right driver is loaded for the network card, the
 	card needs to be configured.  As with many other things, the
 	network card may have been configured at installation time by
 	<application>sysinstall</application>.</para>
 
       <para>To display the configuration for the network interfaces on
 	your system, enter the following command:</para>
 
 <screen>&prompt.user; <userinput>ifconfig</userinput>
 dc0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
         inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255
         ether 00:a0:cc:da:da:da
         media: Ethernet autoselect (100baseTX &lt;full-duplex&gt;)
         status: active
 dc1: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
         inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255
         ether 00:a0:cc:da:da:db
         media: Ethernet 10baseT/UTP
         status: no carrier
 lp0: flags=8810&lt;POINTOPOINT,SIMPLEX,MULTICAST&gt; mtu 1500
 lo0: flags=8049&lt;UP,LOOPBACK,RUNNING,MULTICAST&gt; mtu 16384
         inet 127.0.0.1 netmask 0xff000000
 tun0: flags=8010&lt;POINTOPOINT,MULTICAST&gt; mtu 1500</screen>
 
       <note>
 	<para>Old versions of &os; may require the <option>-a</option>
 	  option following &man.ifconfig.8;, for more details about the
 	  correct syntax of &man.ifconfig.8;, please refer to the manual
 	  page.  Note also that entries concerning IPv6
 	  (<literal>inet6</literal> etc.) were omitted in this
 	  example.</para>
       </note>
 
       <para>In this example, the following devices were
 	displayed:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><devicename>dc0</devicename>: The first Ethernet
 	    interface</para>
 	</listitem>
 
 	<listitem>
 	  <para><devicename>dc1</devicename>: The second Ethernet
 	    interface</para>
 	</listitem>
 
 	<listitem>
 	  <para><devicename>lp0</devicename>: The parallel port
 	    interface</para>
 	</listitem>
 
 	<listitem>
 	  <para><devicename>lo0</devicename>: The loopback device</para>
 	</listitem>
 
 	<listitem>
 	  <para><devicename>tun0</devicename>: The tunnel device used by
 	    <application>ppp</application></para>
 	</listitem>
       </itemizedlist>
 
       <para>&os; uses the driver name followed by the order in
 	which one the card is detected at the kernel boot to name the
 	network card.  For example <devicename>sis2</devicename> would
 	be the third network card on the system using the &man.sis.4;
 	driver.</para>
 
       <para>In this example, the <devicename>dc0</devicename> device is
 	up and running.  The key indicators are:</para>
 
       <orderedlist>
 	<listitem>
 	  <para><literal>UP</literal> means that the card is configured
 	    and ready.</para>
 	</listitem>
 
 	<listitem>
 	  <para>The card has an Internet (<literal>inet</literal>)
 	    address (in this case
 	    <hostid role="ipaddr">192.168.1.3</hostid>).</para>
 	</listitem>
 
 	<listitem>
 	  <para>It has a valid subnet mask (<literal>netmask</literal>;
 	    <hostid role="netmask">0xffffff00</hostid> is the same as
 	    <hostid role="netmask">255.255.255.0</hostid>).</para>
 	</listitem>
 
 	<listitem>
 	  <para>It has a valid broadcast address (in this case,
 	    <hostid role="ipaddr">192.168.1.255</hostid>).</para>
 	</listitem>
 
 	<listitem>
 	  <para>The MAC address of the card (<literal>ether</literal>)
 	    is <hostid role="mac">00:a0:cc:da:da:da</hostid></para>
 	</listitem>
 
 	<listitem>
 	  <para>The physical media selection is on autoselection mode
 	    (<literal>media: Ethernet autoselect (100baseTX
 	    &lt;full-duplex&gt;)</literal>).  We see that
 	    <devicename>dc1</devicename> was configured to run with
 	    <literal>10baseT/UTP</literal> media.  For more
 	    information on available media types for a driver, please
 	    refer to its manual page.</para>
 	</listitem>
 
 	<listitem>
 	  <para>The status of the link (<literal>status</literal>)
 	    is <literal>active</literal>, i.e. the carrier is detected.
 	    For <devicename>dc1</devicename>, we see
 	    <literal>status: no carrier</literal>.  This is normal when
 	    an Ethernet cable is not plugged into the card.</para>
 	</listitem>
       </orderedlist>
 
       <para>If the &man.ifconfig.8; output had shown something similar
 	to:</para>
 
 <screen>dc0: flags=8843&lt;BROADCAST,SIMPLEX,MULTICAST&gt; mtu 1500
 	        ether 00:a0:cc:da:da:da</screen>
 
       <para>it would indicate the card has not been configured.</para>
 
       <para>To configure your card, you need <username>root</username>
 	privileges.  The network card configuration can be done from the
 	command line with &man.ifconfig.8; but you would have to do it
 	after each reboot of the system.  The file
 	<filename>/etc/rc.conf</filename> is where to add the network
 	card's configuration.</para>
 
       <para>Open <filename>/etc/rc.conf</filename> in your favorite
 	editor.  You need to add a line for each network card present on
 	the system, for example in our case, we added these lines:</para>
 
 <programlisting>ifconfig_dc0="inet 192.168.1.3 netmask 255.255.255.0"
 ifconfig_dc1="inet 10.0.0.1 netmask 255.255.255.0 media 10baseT/UTP"</programlisting>
 
       <para>You have to replace <devicename>dc0</devicename>,
 	<devicename>dc1</devicename>, and so on, with
 	the correct device for your cards, and the addresses with the
 	proper ones.  You should read the card driver and
 	&man.ifconfig.8; manual pages for more details about the allowed
 	options and also &man.rc.conf.5; manual page for more
 	information on the syntax of
 	<filename>/etc/rc.conf</filename>.</para>
 
       <para>If you configured the network during installation, some
 	lines about the network card(s) may be already present.  Double
 	check <filename>/etc/rc.conf</filename> before adding any
 	lines.</para>
 
       <para>You will also have to edit the file
 	<filename>/etc/hosts</filename> to add the names and the IP
 	addresses of various machines of the LAN, if they are not already
 	there.  For more information please refer to &man.hosts.5;
 	and to <filename>/usr/share/examples/etc/hosts</filename>.</para>
     </sect2>
 
     <sect2>
-      <title>Testing and Troubleshooting</title>
+      <title>´ú¸Õ»PºÃÃø±Æ°£</title>
 
       <para>Once you have made the necessary changes in
 	<filename>/etc/rc.conf</filename>, you should reboot your
 	system.  This will allow the change(s) to the interface(s) to
 	be applied, and verify that the system restarts without any
 	configuration errors.</para>
 
       <para>Once the system has been rebooted, you should test the
 	network interfaces.</para>
 
       <sect3>
-	<title>Testing the Ethernet Card</title>
+	<title>´ú¸Õ¤A¤Óºô¸ô¥d(Ethernet Card)</title>
 
 	<indexterm>
 	  <primary>network cards</primary>
 	  <secondary>testing</secondary>
 	</indexterm>
 
 	<para>To verify that an Ethernet card is configured correctly,
 	  you have to try two things.  First, ping the interface itself,
 	  and then ping another machine on the LAN.</para>
 
 	<para>First test the local interface:</para>
 
 <screen>&prompt.user; <userinput>ping -c5 192.168.1.3</userinput>
 PING 192.168.1.3 (192.168.1.3): 56 data bytes
 64 bytes from 192.168.1.3: icmp_seq=0 ttl=64 time=0.082 ms
 64 bytes from 192.168.1.3: icmp_seq=1 ttl=64 time=0.074 ms
 64 bytes from 192.168.1.3: icmp_seq=2 ttl=64 time=0.076 ms
 64 bytes from 192.168.1.3: icmp_seq=3 ttl=64 time=0.108 ms
 64 bytes from 192.168.1.3: icmp_seq=4 ttl=64 time=0.076 ms
 
 --- 192.168.1.3 ping statistics ---
 5 packets transmitted, 5 packets received, 0% packet loss
 round-trip min/avg/max/stddev = 0.074/0.083/0.108/0.013 ms</screen>
 
 	<para>Now we have to ping another machine on the LAN:</para>
 
 <screen>&prompt.user; <userinput>ping -c5 192.168.1.2</userinput>
 PING 192.168.1.2 (192.168.1.2): 56 data bytes
 64 bytes from 192.168.1.2: icmp_seq=0 ttl=64 time=0.726 ms
 64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=0.766 ms
 64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=0.700 ms
 64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=0.747 ms
 64 bytes from 192.168.1.2: icmp_seq=4 ttl=64 time=0.704 ms
 
 --- 192.168.1.2 ping statistics ---
 5 packets transmitted, 5 packets received, 0% packet loss
 round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms</screen>
 
 	<para>You could also use the machine name instead of
 	  <hostid role="ipaddr">192.168.1.2</hostid> if you have set up the
 	  <filename>/etc/hosts</filename> file.</para>
       </sect3>
 
       <sect3>
-	<title>Troubleshooting</title>
+	<title>ºÃÃø±Æ°£</title>
 
       <indexterm>
 	<primary>network cards</primary>
 	<secondary>troubleshooting</secondary>
       </indexterm>
 
       <para>Troubleshooting hardware and software configurations is always
 	a pain, and a pain which can be alleviated by checking the simple
 	things first.  Is your network cable plugged in?  Have you properly
 	configured the network services?  Did you configure the firewall
 	correctly?  Is the card you are using supported by &os;?  Always
 	check the hardware notes before sending off a bug report.  Update
 	your version of &os; to the latest STABLE version.  Check the
 	mailing list archives, or perhaps search the Internet.</para>
 
       <para>If the card works, yet performance is poor, it would be
 	worthwhile to read over the &man.tuning.7; manual page.  You
 	can also check the network configuration as incorrect network
 	settings can cause slow connections.</para>
 
       <para>Some users experience one or two <errorname>device
 	timeout</errorname> messages, which is normal for some cards.  If they
 	continue, or are bothersome, you may wish to be sure the
 	device is not conflicting with another device.  Double check
 	the cable connections.  Perhaps you may just need to get
 	another card.</para>
 
       <para>At times, users see a few <errorname>watchdog timeout</errorname>
 	errors.  The first thing to do here is to check your network
 	cable. Many cards require a PCI slot which supports Bus
 	Mastering. On some old motherboards, only one PCI slot allows
 	it (usually slot 0). Check the network card and the
 	motherboard documentation to determine if that may be the
 	problem.</para>
 
       <para><errorname>No route to host</errorname> messages occur if the
 	system is unable to route a packet to the destination host.
 	This can happen if no default route is specified, or if a
 	cable is unplugged.  Check the output of <command>netstat
 	-rn</command> and make sure there is a valid route to the host
 	you are trying to reach.  If there is not, read on to <xref
 	linkend="advanced-networking">.</para>
 
       <para><errorname>ping: sendto: Permission denied</errorname> error
 	messages are often caused by a misconfigured firewall.  If
 	<command>ipfw</command> is enabled in the kernel but no rules
 	have been defined, then the default policy is to deny all
 	traffic, even ping requests!  Read on to <xref
 	linkend="firewalls"> for more information.</para>
 
       <para>Sometimes performance of the card is poor, or below average.
 	In these cases it is best to set the media selection mode
 	from <literal>autoselect</literal> to the correct media selection.
 	While this usually works for most hardware, it may not resolve
 	this issue for everyone.  Again, check all the network settings,
 	and read over the &man.tuning.7; manual page.</para>
 
       </sect3>
     </sect2>
   </sect1>
 
   <sect1 id="configtuning-virtual-hosts">
-    <title>Virtual Hosts</title>
+    <title>µêÀÀ¥D¾÷(Virtual Hosts)</title>
 
     <indexterm><primary>virtual hosts</primary></indexterm>
     <indexterm><primary>IP aliases</primary></indexterm>
 
     <para>A very common use of &os; is virtual site hosting, where
       one server appears to the network as many servers.  This is
       achieved by assigning multiple network addresses to a single
       interface.</para>
 
     <para>A given network interface has one <quote>real</quote> address,
       and may have any number of <quote>alias</quote> addresses.
       These aliases are
       normally added by placing alias entries in
       <filename>/etc/rc.conf</filename>.</para>
 
     <para>An alias entry for the interface <devicename>fxp0</devicename>
       looks like:</para>
 
 <programlisting>ifconfig_fxp0_alias0="inet xxx.xxx.xxx.xxx netmask xxx.xxx.xxx.xxx"</programlisting>
 
     <para>Note that alias entries must start with <literal>alias0</literal> and proceed
       upwards in order, (for example, <literal>_alias1</literal>, <literal>_alias2</literal>, and so on).
       The configuration process will stop at the first missing number.
     </para>
 
     <para>The calculation of alias netmasks is important, but
       fortunately quite simple.  For a given interface, there must be
       one address which correctly represents the network's netmask.
       Any other addresses which fall within this network must have a
       netmask of all <literal>1</literal>s (expressed as either
       <hostid role="netmask">255.255.255.255</hostid> or <hostid role="netmask">0xffffffff</hostid>).
       </para>
 
     <para>For example, consider the case where the
       <devicename>fxp0</devicename> interface is
       connected to two networks, the <hostid role="ipaddr">10.1.1.0</hostid>
       network with a netmask of <hostid role="netmask">255.255.255.0</hostid>
       and the <hostid role="ipaddr">202.0.75.16</hostid> network with
       a netmask of <hostid role="netmask">255.255.255.240</hostid>.
       We want the system to appear at <hostid role="ipaddr">10.1.1.1</hostid>
       through <hostid role="ipaddr">10.1.1.5</hostid> and at
       <hostid role="ipaddr">202.0.75.17</hostid> through
       <hostid role="ipaddr">202.0.75.20</hostid>.  As noted above, only the
       first address in a given network range (in this case,
       <hostid role="ipaddr">10.0.1.1</hostid> and
       <hostid role="ipaddr">202.0.75.17</hostid>) should have a real
       netmask; all the rest (<hostid role="ipaddr">10.1.1.2</hostid>
       through <hostid role="ipaddr">10.1.1.5</hostid> and
       <hostid role="ipaddr">202.0.75.18</hostid> through
       <hostid role="ipaddr">202.0.75.20</hostid>) must be configured with a
       netmask of <hostid role="netmask">255.255.255.255</hostid>.</para>
 
     <para>The following <filename>/etc/rc.conf</filename> entries
       configure the adapter correctly for this arrangement:</para>
 
     <programlisting>ifconfig_fxp0="inet 10.1.1.1 netmask 255.255.255.0"
 ifconfig_fxp0_alias0="inet 10.1.1.2 netmask 255.255.255.255"
 ifconfig_fxp0_alias1="inet 10.1.1.3 netmask 255.255.255.255"
 ifconfig_fxp0_alias2="inet 10.1.1.4 netmask 255.255.255.255"
 ifconfig_fxp0_alias3="inet 10.1.1.5 netmask 255.255.255.255"
 ifconfig_fxp0_alias4="inet 202.0.75.17 netmask 255.255.255.240"
 ifconfig_fxp0_alias5="inet 202.0.75.18 netmask 255.255.255.255"
 ifconfig_fxp0_alias6="inet 202.0.75.19 netmask 255.255.255.255"
 ifconfig_fxp0_alias7="inet 202.0.75.20 netmask 255.255.255.255"</programlisting>
 
   </sect1>
 
   <sect1 id="configtuning-configfiles">
-    <title>Configuration Files</title>
+    <title>ÁÙ¦³­þ¨Ç¥D­n³]©wÀÉ©O¡H</title>
 
     <sect2>
       <title><filename>/etc</filename> Layout</title>
       <para>There are a number of directories in which configuration
 	information is kept.  These include:</para>
 
       <informaltable frame="none" pgwide="1">
 	<tgroup cols="2">
 	  <colspec colwidth="1*">
 	  <colspec colwidth="2*">
 
 	  <tbody>
 	    <row>
 	      <entry><filename>/etc</filename></entry>
 	      <entry>Generic system configuration information; data here is
 		system-specific.</entry>
 	    </row>
 	    <row>
 	      <entry><filename>/etc/defaults</filename></entry>
 	      <entry>Default versions of system configuration files.</entry>
 	    </row>
 	    <row>
 	      <entry><filename>/etc/mail</filename></entry>
 	      <entry>Extra &man.sendmail.8; configuration, other
 		MTA configuration files.
 	      </entry>
 	    </row>
 	    <row>
 	      <entry><filename>/etc/ppp</filename></entry>
 	      <entry>Configuration for both user- and kernel-ppp programs.
 	      </entry>
 	    </row>
 	    <row>
 	      <entry><filename>/etc/namedb</filename></entry>
 	      <entry>Default location for &man.named.8; data.  Normally
 		<filename>named.conf</filename> and zone files are stored
                 here.</entry>
 	    </row>
 	    <row>
 	      <entry><filename>/usr/local/etc</filename></entry>
 	      <entry>Configuration files for installed applications.
 		May contain per-application subdirectories.</entry>
 	    </row>
 	    <row>
 	      <entry><filename>/usr/local/etc/rc.d</filename></entry>
 	      <entry>Start/stop scripts for installed applications.</entry>
 	    </row>
 	    <row>
 	      <entry><filename>/var/db</filename></entry>
 	      <entry>Automatically generated system-specific database files,
                  such as the package database, the locate database, and so
                  on</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
     </sect2>
 
     <sect2>
       <title>Hostnames</title>
 
       <indexterm><primary>hostname</primary></indexterm>
       <indexterm><primary>DNS</primary></indexterm>
 
       <sect3>
 	<title><filename>/etc/resolv.conf</filename></title>
 
 	<indexterm>
 	  <primary><filename>resolv.conf</filename></primary>
 	</indexterm>
 
 	<para><filename>/etc/resolv.conf</filename> dictates how &os;'s
 	  resolver accesses the Internet Domain Name System (DNS).</para>
 
 	<para>The most common entries to <filename>resolv.conf</filename> are:
 	</para>
 
 	<informaltable frame="none" pgwide="1">
 	  <tgroup cols="2">
 	  <colspec colwidth="1*">
 	  <colspec colwidth="2*">
 
 	    <tbody>
 	      <row>
 		<entry><literal>nameserver</literal></entry>
 		<entry>The IP address of a name server the resolver
 		  should query.  The servers are queried in the order
 		  listed with a maximum of three.</entry>
 	      </row>
 	      <row>
 		<entry><literal>search</literal></entry>
 		<entry>Search list for hostname lookup.  This is normally
 		  determined by the domain of the local hostname.</entry>
 	      </row>
 	      <row>
 		<entry><literal>domain</literal></entry>
 		<entry>The local domain name.</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</informaltable>
 
 	<para>A typical <filename>resolv.conf</filename>:</para>
 
 	<programlisting>search example.com
 nameserver 147.11.1.11
 nameserver 147.11.100.30</programlisting>
 
 	<note><para>Only one of the <literal>search</literal> and
 	  <literal>domain</literal> options should be used.</para></note>
 
 	<para>If you are using DHCP, &man.dhclient.8; usually rewrites
 	  <filename>resolv.conf</filename> with information received from the
 	  DHCP server.</para>
       </sect3>
 
       <sect3>
 	<title><filename>/etc/hosts</filename></title>
 
 	<indexterm><primary>hosts</primary></indexterm>
 
 	<para><filename>/etc/hosts</filename> is a simple text
 	  database reminiscent of the old Internet.  It works in
 	  conjunction with DNS and NIS providing name to IP address
 	  mappings.  Local computers connected via a LAN can be placed
 	  in here for simplistic naming purposes instead of setting up
 	  a &man.named.8; server.  Additionally,
 	  <filename>/etc/hosts</filename> can be used to provide a
 	  local record of Internet names, reducing the need to query
 	  externally for commonly accessed names.</para>
 
 	<programlisting># &dollar;&os;&dollar;
 #
 # Host Database
 # This file should contain the addresses and aliases
 # for local hosts that share this file.
 # In the presence of the domain name service or NIS, this file may
 # not be consulted at all; see /etc/nsswitch.conf for the resolution order.
 #
 #
 ::1                     localhost localhost.my.domain myname.my.domain
 127.0.0.1               localhost localhost.my.domain myname.my.domain
 
 #
 # Imaginary network.
 #10.0.0.2               myname.my.domain myname
 #10.0.0.3               myfriend.my.domain myfriend
 #
 # According to RFC 1918, you can use the following IP networks for
 # private nets which will never be connected to the Internet:
 #
 #       10.0.0.0        -   10.255.255.255
 #       172.16.0.0      -   172.31.255.255
 #       192.168.0.0     -   192.168.255.255
 #
 # In case you want to be able to connect to the Internet, you need
 # real official assigned numbers.  PLEASE PLEASE PLEASE do not try
 # to invent your own network numbers but instead get one from your
 # network provider (if any) or from the Internet Registry (ftp to
 # rs.internic.net, directory `/templates').
 #</programlisting>
 
 	<para><filename>/etc/hosts</filename> takes on the simple format
 	  of:</para>
 
 	<programlisting>[Internet address] [official hostname] [alias1] [alias2] ...</programlisting>
 
 	<para>For example:</para>
 
 	<programlisting>10.0.0.1 myRealHostname.example.com myRealHostname foobar1 foobar2</programlisting>
 
 	<para>Consult &man.hosts.5; for more information.</para>
       </sect3>
     </sect2>
 
     <sect2>
       <title>Log File Configuration</title>
 
       <indexterm><primary>log files</primary></indexterm>
 
       <sect3>
 	<title><filename>syslog.conf</filename></title>
 
 	<indexterm><primary>syslog.conf</primary></indexterm>
 
 	<para><filename>syslog.conf</filename> is the configuration file
 	  for the &man.syslogd.8; program.  It indicates which types
 	  of <command>syslog</command> messages are logged to particular
 	  log files.</para>
 
 	<programlisting># &dollar;&os;&dollar;
 #
 #       Spaces ARE valid field separators in this file. However,
 #       other *nix-like systems still insist on using tabs as field
 #       separators. If you are sharing this file between systems, you
 #       may want to use only tabs as field separators here.
 #       Consult the syslog.conf(5) manual page.
 *.err;kern.debug;auth.notice;mail.crit          /dev/console
 *.notice;kern.debug;lpr.info;mail.crit;news.err /var/log/messages
 security.*                                      /var/log/security
 mail.info                                       /var/log/maillog
 lpr.info                                        /var/log/lpd-errs
 cron.*                                          /var/log/cron
 *.err                                           root
 *.notice;news.err                               root
 *.alert                                         root
 *.emerg                                         *
 # uncomment this to log all writes to /dev/console to /var/log/console.log
 #console.info                                   /var/log/console.log
 # uncomment this to enable logging of all log messages to /var/log/all.log
 #*.*                                            /var/log/all.log
 # uncomment this to enable logging to a remote log host named loghost
 #*.*                                            @loghost
 # uncomment these if you're running inn
 # news.crit                                     /var/log/news/news.crit
 # news.err                                      /var/log/news/news.err
 # news.notice                                   /var/log/news/news.notice
 !startslip
 *.*                                             /var/log/slip.log
 !ppp
 *.*                                             /var/log/ppp.log</programlisting>
 
 	<para>Consult the &man.syslog.conf.5; manual page for more
 	  information.</para>
       </sect3>
 
       <sect3>
 	<title><filename>newsyslog.conf</filename></title>
 
 	<indexterm><primary>newsyslog.conf</primary></indexterm>
 
 	<para><filename>newsyslog.conf</filename> is the configuration
 	  file for &man.newsyslog.8;, a program that is normally scheduled
 	  to run by &man.cron.8;.  &man.newsyslog.8; determines when log
 	  files require archiving or rearranging.
 	  <filename>logfile</filename> is moved to
 	  <filename>logfile.0</filename>, <filename>logfile.0</filename>
 	  is moved to <filename>logfile.1</filename>, and so on.
 	  Alternatively, the log files may be archived in &man.gzip.1; format
 	  causing them to be named: <filename>logfile.0.gz</filename>,
 	  <filename>logfile.1.gz</filename>, and so on.</para>
 
 	<para><filename>newsyslog.conf</filename> indicates which log
 	  files are to be managed, how many are to be kept, and when
 	  they are to be touched.  Log files can be rearranged and/or
 	  archived when they have either reached a certain size, or at a
 	  certain periodic time/date.</para>
 
 	<programlisting># configuration file for newsyslog
 # &dollar;&os;&dollar;
 #
 # filename          [owner:group]    mode count size when [ZB] [/pid_file] [sig_num]
 /var/log/cron                           600  3     100  *     Z
 /var/log/amd.log                        644  7     100  *     Z
 /var/log/kerberos.log                   644  7     100  *     Z
 /var/log/lpd-errs                       644  7     100  *     Z
 /var/log/maillog                        644  7     *    @T00  Z
 /var/log/sendmail.st                    644  10    *    168   B
 /var/log/messages                       644  5     100  *     Z
 /var/log/all.log                        600  7     *    @T00  Z
 /var/log/slip.log                       600  3     100  *     Z
 /var/log/ppp.log                        600  3     100  *     Z
 /var/log/security                       600  10    100  *     Z
 /var/log/wtmp                           644  3     *    @01T05 B
 /var/log/daily.log                      640  7     *    @T00  Z
 /var/log/weekly.log                     640  5     1    $W6D0 Z
 /var/log/monthly.log                    640  12    *    $M1D0 Z
 /var/log/console.log                    640  5     100  *     Z</programlisting>
 
 	<para>Consult the &man.newsyslog.8; manual page for more
 	  information.</para>
       </sect3>
     </sect2>
 
     <sect2 id="configtuning-sysctlconf">
       <title><filename>sysctl.conf</filename></title>
 
       <indexterm><primary>sysctl.conf</primary></indexterm>
       <indexterm><primary>sysctl</primary></indexterm>
 
       <para><filename>sysctl.conf</filename> looks much like
 	<filename>rc.conf</filename>.  Values are set in a
 	<literal>variable=value</literal>
 	form.  The specified values are set after the system goes into
 	multi-user mode.  Not all variables are settable in this mode.</para>
 
       <para>A sample <filename>sysctl.conf</filename> turning off logging
 	of fatal signal exits and letting Linux programs know they are really
 	running under &os;:</para>
 
       <programlisting>kern.logsigexit=0       # Do not log fatal signal exits (e.g. sig 11)
 compat.linux.osname=&os;
 compat.linux.osrelease=4.3-STABLE</programlisting>
     </sect2>
   </sect1>
 
   <sect1 id="configtuning-sysctl">
     <title>Tuning with sysctl</title>
 
     <indexterm><primary>sysctl</primary></indexterm>
     <indexterm>
       <primary>tuning</primary>
       <secondary>with sysctl</secondary>
     </indexterm>
 
     <para>&man.sysctl.8; is an interface that allows you to make changes
       to a running &os; system.  This includes many advanced
       options of the TCP/IP stack and virtual memory system that can
       dramatically improve performance for an experienced system
       administrator.  Over five hundred system variables can be read
       and set using &man.sysctl.8;.</para>
 
     <para>At its core, &man.sysctl.8; serves two functions: to read and
       to modify system settings.</para>
 
     <para>To view all readable variables:</para>
 
     <screen>&prompt.user; <userinput>sysctl -a</userinput></screen>
 
     <para>To read a particular variable, for example,
       <varname>kern.maxproc</varname>:</para>
 
     <screen>&prompt.user; <userinput>sysctl kern.maxproc</userinput>
 kern.maxproc: 1044</screen>
 
     <para>To set a particular variable, use the intuitive
       <replaceable>variable</replaceable>=<replaceable>value</replaceable>
       syntax:</para>
 
     <screen>&prompt.root; <userinput>sysctl kern.maxfiles=5000</userinput>
 kern.maxfiles: 2088 -> 5000</screen>
 
     <para>Settings of sysctl variables are usually either strings,
       numbers, or booleans (a  boolean being <literal>1</literal> for yes
       or a <literal>0</literal> for no).</para>
 
     <para>If you want to set automatically some variables each time
       the machine boots, add them to the
       <filename>/etc/sysctl.conf</filename> file.  For more information
       see the &man.sysctl.conf.5; manual page and the
       <xref linkend="configtuning-sysctlconf">.</para>
 
   <sect2 id="sysctl-readonly">
     <sect2info>
       <authorgroup>
         <author>
 	 <firstname>Tom</firstname>
 	 <surname>Rhodes</surname>
 	 <contrib>Contributed by </contrib>
 	 <!-- 31 January 2003 -->
         </author>
       </authorgroup>
     </sect2info>
     <title>&man.sysctl.8; Read-only</title>
 
     <para>In some cases it may be desirable to modify read-only &man.sysctl.8;
       values.  While this is sometimes unavoidable, it can only be done
       on (re)boot.</para>
 
     <para>For instance on some laptop models the &man.cardbus.4; device will
       not probe memory ranges, and fail with errors which look similar to:</para>
 
     <screen>cbb0: Could not map register memory
 device_probe_and_attach: cbb0 attach returned 12</screen>
 
     <para>Cases like the one above usually require the modification of some
       default &man.sysctl.8; settings which are set read only.  To overcome
       these situations a user can put &man.sysctl.8; <quote>OIDs</quote>
       in their local <filename>/boot/loader.conf</filename>.  Default
       settings are located in the <filename>/boot/defaults/loader.conf</filename>
       file.</para>
 
     <para>Fixing the problem mentioned above would require a user to set
       <option>hw.pci.allow_unsupported_io_range=1</option> in the aforementioned
       file.  Now &man.cardbus.4; will work properly.</para>
 
     </sect2>
   </sect1>
 
   <sect1 id="configtuning-disk">
     <title>Tuning Disks</title>
 
     <sect2>
       <title>Sysctl Variables</title>
 
       <sect3>
 	<title><varname>vfs.vmiodirenable</varname></title>
 
 	<indexterm>
 	  <primary><varname>vfs.vmiodirenable</varname></primary>
 	</indexterm>
 
 	<para>The <varname>vfs.vmiodirenable</varname> sysctl variable
 	  may be set to either 0 (off) or 1 (on); it is 1 by default.
 	  This variable controls how directories are cached by the
 	  system.  Most directories are small, using just a single
 	  fragment (typically 1&nbsp;K) in the file system and less
 	  (typically 512&nbsp;bytes) in the buffer cache.
 	  With this variable turned off (to 0), the buffer
 	  cache will only cache a fixed number of directories even if
 	  you have a huge amount of memory.  When turned on (to 1), this sysctl
 	  allows the buffer cache to use the VM Page Cache to cache the
 	  directories, making all the memory available for caching
 	  directories.  However,
 	  the minimum in-core memory used to cache a directory is the
 	  physical page size (typically 4&nbsp;K) rather than 512&nbsp;
 	  bytes.  We recommend keeping this option on if you are running
 	  any services which manipulate large numbers of files.  Such
 	  services can include web caches, large mail systems, and news
 	  systems.  Keeping this option on will generally not reduce
 	  performance even with the wasted memory but you should
 	  experiment to find out.</para>
       </sect3>
 
      <sect3>
  	<title><varname>vfs.write_behind</varname></title>
 
  	<indexterm>
  	  <primary><varname>vfs.write_behind</varname></primary>
  	</indexterm>
 
  	<para>The <varname>vfs.write_behind</varname> sysctl variable
  	  defaults to <literal>1</literal> (on).  This tells the file system
  	  to issue media writes as full clusters are collected, which
  	  typically occurs when writing large sequential files.  The idea
  	  is to avoid saturating the buffer cache with dirty buffers when
  	  it would not benefit I/O performance.  However, this may stall
  	  processes and under certain circumstances you may wish to turn it
  	  off.</para>
        </sect3>
 
        <sect3>
  	<title><varname>vfs.hirunningspace</varname></title>
 
  	<indexterm>
  	  <primary><varname>vfs.hirunningspace</varname></primary>
  	</indexterm>
 
  	<para>The <varname>vfs.hirunningspace</varname> sysctl variable
  	  determines how much outstanding write I/O may be queued to disk
  	  controllers system-wide at any given instance.  The default is
  	  usually sufficient but on machines with lots of disks you may
  	  want to bump it up to four or five <emphasis>megabytes</emphasis>.
  	  Note that setting too high a value (exceeding the buffer cache's
  	  write threshold) can lead to extremely bad clustering
  	  performance.  Do not set this value arbitrarily high!  Higher
  	  write values may add latency to reads occurring at the same time.
  	</para>
 
  	<para>There are various other buffer-cache and VM page cache
  	  related sysctls.  We do not recommend modifying these values.  As
  	  of &os;&nbsp;4.3, the VM system does an extremely good job of
  	  automatically tuning itself.</para>
        </sect3>
 
        <sect3>
  	<title><varname>vm.swap_idle_enabled</varname></title>
 
  	<indexterm>
  	  <primary><varname>vm.swap_idle_enabled</varname></primary>
  	</indexterm>
 
  	<para>The <varname>vm.swap_idle_enabled</varname> sysctl variable
  	  is useful in large multi-user systems where you have lots of
  	  users entering and leaving the system and lots of idle processes.
  	  Such systems tend to generate a great deal of continuous pressure
  	  on free memory reserves.  Turning this feature on and tweaking
  	  the swapout hysteresis (in idle seconds) via
  	  <varname>vm.swap_idle_threshold1</varname> and
  	  <varname>vm.swap_idle_threshold2</varname> allows you to depress
  	  the priority of memory pages associated with idle processes more
  	  quickly then the normal pageout algorithm.  This gives a helping
  	  hand to the pageout daemon.  Do not turn this option on unless
  	  you need it, because the tradeoff you are making is essentially
  	  pre-page memory sooner rather than later; thus eating more swap
  	  and disk bandwidth.  In a small system this option will have a
  	  determinable effect but in a large system that is already doing
  	  moderate paging this option allows the VM system to stage whole
  	  processes into and out of memory easily.</para>
        </sect3>
 
       <sect3>
 	<title><varname>hw.ata.wc</varname></title>
 
 	<indexterm>
 	  <primary><varname>hw.ata.wc</varname></primary>
 	</indexterm>
 
 	<para>&os;&nbsp;4.3 flirted with turning off IDE write caching.
 	  This reduced write bandwidth to IDE disks but was considered
 	  necessary due to serious data consistency issues introduced
 	  by hard drive vendors.  The problem is that IDE
 	  drives lie about when a write completes.  With IDE write
 	  caching turned on, IDE hard drives not only write data
 	  to disk out of order, but will sometimes delay writing some
 	  blocks indefinitely when under heavy disk loads.  A crash or
 	  power failure may cause serious file system corruption.
 	  &os;'s default was changed to be safe.  Unfortunately, the
 	  result was such a huge performance loss that we changed
 	  write caching back to on by default after the release.  You
 	  should check the default on your system by observing the
 	  <varname>hw.ata.wc</varname> sysctl variable.  If IDE write
 	  caching is turned off, you can turn it back on by setting
 	  the kernel variable back to 1.  This must be done from the
 	  boot loader at boot time.  Attempting to do it after the
 	  kernel boots will have no effect.</para>
 
 	<para>For more information, please see &man.ata.4;.</para>
       </sect3>
 
       <sect3>
 	<title><literal>SCSI_DELAY</literal>
 	(<varname>kern.cam.scsi_delay</varname>)</title>
 
 	<indexterm>
 	  <primary><varname>kern.cam.scsi_delay</varname></primary>
 	</indexterm>
 
 	<indexterm>
 	  <primary>kernel options</primary>
 	  <secondary><literal>SCSI_DELAY</literal></secondary>
 	</indexterm>
 
 	<para>The <literal>SCSI_DELAY</literal> kernel config may be used to
 	  reduce system boot times.  The defaults are fairly high and can be
 	  responsible for <literal>15</literal> seconds of delay in the
 	  boot process.  Reducing it to <literal>5</literal> seconds usually
 	  works (especially with modern drives).  Newer versions of &os;
 	  (5.0 and higher) should use the <varname>kern.cam.scsi_delay</varname>
 	  boot time tunable.  The tunable, and kernel config option accept
 	  values in terms of <emphasis>milliseconds</emphasis> and
 	  <emphasis>not</emphasis> <emphasis>seconds</emphasis>.</para>
       </sect3>
     </sect2>
 
     <sect2 id="soft-updates">
       <title>Soft Updates</title>
 
       <indexterm><primary>Soft Updates</primary></indexterm>
       <indexterm><primary>tunefs</primary></indexterm>
 
       <para>The &man.tunefs.8; program can be used to fine-tune a
 	file system.  This program has many different options, but for
 	now we are only concerned with toggling Soft Updates on and
 	off, which is done by:</para>
 
       <screen>&prompt.root; <userinput>tunefs -n enable /filesystem</userinput>
 &prompt.root; <userinput>tunefs -n disable /filesystem</userinput></screen>
 
       <para>A filesystem cannot be modified with &man.tunefs.8; while
 	it is mounted.  A good time to enable Soft Updates is before any
 	partitions have been mounted, in single-user mode.</para>
 
       <note><para>As of &os;&nbsp;4.5, it is possible to enable Soft Updates
 	at filesystem creation time, through use of the <literal>-U</literal>
 	option to &man.newfs.8;.</para></note>
 
       <para>Soft Updates drastically improves meta-data performance, mainly
         file creation and deletion, through the use of a memory cache.  We
         recommend to use Soft Updates on all of your file systems.  There
         are two downsides to Soft Updates that you should be aware of:  First,
         Soft Updates guarantees filesystem consistency in the case of a crash
         but could very easily be several seconds (even a minute!) behind
         updating the physical disk.  If your system crashes you may lose more
         work than otherwise.  Secondly, Soft Updates delays the freeing of
         filesystem blocks.  If you have a filesystem (such as the root
 	filesystem) which is almost full, performing a major update, such as
         <command>make installworld</command>, can cause the filesystem to run
 	out of space and the update to fail.</para>
 
       <sect3>
 	<title>More Details about Soft Updates</title>
 
 	<indexterm>
 	  <primary>Soft Updates</primary>
 	  <secondary>details</secondary>
 	</indexterm>
 
 	<para>There are two traditional approaches to writing a file
 	  systems meta-data back to disk.  (Meta-data updates are
 	  updates to non-content data like inodes or
 	  directories.)</para>
 
 	<para>Historically, the default behavior was to write out
 	  meta-data updates synchronously.  If a directory had been
 	  changed, the system waited until the change was actually
 	  written to disk.  The file data buffers (file contents) were
 	  passed through the buffer cache and backed up
 	  to disk later on asynchronously.  The advantage of this
 	  implementation is that it operates safely.  If there is
 	  a failure during an update, the meta-data are always in a
 	  consistent state.  A file is either created completely
 	  or not at all.  If the data blocks of a file did not find
 	  their way out of the buffer cache onto the disk by the time
 	  of the crash, &man.fsck.8; is able to recognize this and
 	  repair the filesystem by setting the file length to
 	  0.  Additionally, the implementation is clear and simple.
 	  The disadvantage is that meta-data changes are slow.  An
 	  <command>rm -r</command>, for instance, touches all the files
 	  in a directory sequentially, but each directory
 	  change (deletion of a file) will be written synchronously
 	  to the disk.  This includes updates to the directory itself,
 	  to the inode table, and possibly to indirect blocks
 	  allocated by the file.  Similar considerations apply for
 	  unrolling large hierarchies (<command>tar -x</command>).</para>
 
 	<para>The second case is asynchronous meta-data updates.  This
   	  is the default for Linux/ext2fs and
   	  <command>mount -o async</command> for *BSD ufs.  All
   	  meta-data updates are simply being passed through the buffer
   	  cache too, that is, they will be intermixed with the updates
   	  of the file content data.  The advantage of this
   	  implementation is there is no need to wait until each
   	  meta-data update has been written to disk, so all operations
   	  which cause huge amounts of meta-data updates work much
   	  faster than in the synchronous case.  Also, the
   	  implementation is still clear and simple, so there is a low
   	  risk for bugs creeping into the code.  The disadvantage is
   	  that there is no guarantee at all for a consistent state of
   	  the filesystem.  If there is a failure during an operation
   	  that updated large amounts of meta-data (like a power
   	  failure, or someone pressing the reset button),
 	  the filesystem
   	  will be left in an unpredictable state.  There is no opportunity
   	  to examine the state of the filesystem when the system
   	  comes up again; the data blocks of a file could already have
   	  been written to the disk while the updates of the inode
   	  table or the associated directory were not.  It is actually
   	  impossible to implement a <command>fsck</command> which is
   	  able to clean up the resulting chaos (because the necessary
   	  information is not available on the disk).  If the
 	  filesystem has been damaged beyond repair, the only choice
 	  is to use &man.newfs.8; on it and restore it from backup.
 	  </para>
 
 	<para>The usual solution for this problem was to implement
 	  <emphasis>dirty region logging</emphasis>, which is also
 	  referred to as <emphasis>journaling</emphasis>, although that
 	  term is not used consistently and is occasionally applied
 	  to other forms of transaction logging as well.  Meta-data
 	  updates are still written synchronously, but only into a
 	  small region of the disk.  Later on they will be moved
 	  to their proper location.  Because the logging
 	  area is a small, contiguous region on the disk, there
 	  are no long distances for the disk heads to move, even
 	  during heavy operations, so these operations are quicker
 	  than synchronous updates.
 	  Additionally the complexity of the implementation is fairly
 	  limited, so the risk of bugs being present is low.  A disadvantage
 	  is that all meta-data are written twice (once into the
 	  logging region and once to the proper location) so for
 	  normal work, a performance <quote>pessimization</quote>
 	  might result.  On the other hand, in case of a crash, all
 	  pending meta-data operations can be quickly either rolled-back
 	  or completed from the logging area after the system comes
 	  up again, resulting in a fast filesystem startup.</para>
 
 	<para>Kirk McKusick, the developer of Berkeley FFS,
 	   solved this problem with Soft Updates: all pending
 	   meta-data updates are kept in memory and written out to disk
 	   in a sorted sequence (<quote>ordered meta-data
 	   updates</quote>).  This has the effect that, in case of
 	   heavy meta-data operations, later updates to an item
 	   <quote>catch</quote> the earlier ones if the earlier ones are still in
 	   memory and have not already been written to disk.  So all
 	   operations on, say, a directory are generally performed in
 	   memory before the update is written to disk (the data
 	   blocks are sorted according to their position so
 	   that they will not be on the disk ahead of their meta-data).
 	   If the system crashes, this causes an implicit <quote>log
 	   rewind</quote>: all operations which did not find their way
 	   to the disk appear as if they had never happened.  A
 	   consistent filesystem state is maintained that appears to
 	   be the one of 30 to 60 seconds earlier.  The
 	   algorithm used guarantees that all resources in use
 	   are marked as such in their appropriate bitmaps: blocks and inodes.
 	   After a crash, the only resource allocation error
 	   that occurs is that resources are
 	   marked as <quote>used</quote> which are actually <quote>free</quote>.
 	   &man.fsck.8; recognizes this situation,
 	   and frees the resources that are no longer used.  It is safe to
 	   ignore the dirty state of the filesystem after a crash by
 	   forcibly mounting it with <command>mount -f</command>.  In
 	   order to free resources that may be unused, &man.fsck.8;
 	   needs to be run at a later time.  This is the idea behind
 	   the <emphasis>background fsck</emphasis>: at system startup
 	   time, only a <emphasis>snapshot</emphasis> of the
 	   filesystem is recorded.  The <command>fsck</command> can be
 	   run later on.  All file systems can then be mounted
 	   <quote>dirty</quote>, so the system startup proceeds in
 	   multiuser mode.  Then, background <command>fsck</command>s
 	   will be scheduled for all file systems where this is required, to free
 	   resources that may be unused.  (File systems that do not use
 	   Soft Updates still need the usual foreground
 	   <command>fsck</command> though.)</para>
 
 	 <para>The advantage is that meta-data operations are nearly as
 	   fast as asynchronous updates (i.e. faster than with
 	   <emphasis>logging</emphasis>, which has to write the
 	   meta-data twice).  The disadvantages are the complexity of
 	   the code (implying a higher risk for bugs in an area that
 	   is highly sensitive regarding loss of user data), and a
 	   higher memory consumption.  Additionally there are some
 	   idiosyncrasies one has to get used to.
 	   After a crash, the state of the filesystem appears to be
 	   somewhat <quote>older</quote>.  In situations where
 	   the standard synchronous approach would have caused some
 	   zero-length files to remain after the
 	   <command>fsck</command>, these files do not exist at all
 	   with a Soft Updates filesystem because neither the meta-data
 	   nor the file contents have ever been written to disk.
 	   Disk space is not released until the updates have been
 	   written to disk, which may take place some time after
 	   running <command>rm</command>.  This may cause problems
 	   when installing large amounts of data on a filesystem
 	   that does not have enough free space to hold all the files
 	   twice.</para>
       </sect3>
     </sect2>
   </sect1>
 
   <sect1 id="configtuning-kernel-limits">
     <title>Tuning Kernel Limits</title>
 
     <indexterm>
       <primary>tuning</primary>
       <secondary>kernel limits</secondary>
     </indexterm>
 
     <sect2 id="file-process-limits">
       <title>File/Process Limits</title>
 
       <sect3 id="kern-maxfiles">
 	<title><varname>kern.maxfiles</varname></title>
 
 	<indexterm>
 	  <primary><varname>kern.maxfiles</varname></primary>
 	</indexterm>
 
 	<para><varname>kern.maxfiles</varname> can be raised or
 	  lowered based upon your system requirements.  This variable
 	  indicates the maximum number of file descriptors on your
 	  system.  When the file descriptor table is full,
 	  <errorname>file: table is full</errorname> will show up repeatedly
 	  in the system message buffer, which can be viewed with the
 	  <command>dmesg</command> command.</para>
 
 	<para>Each open file, socket, or fifo uses one file
 	  descriptor.  A large-scale production server may easily
 	  require many thousands of file descriptors, depending on the
 	  kind and number of services running concurrently.</para>
 
 	<para><varname>kern.maxfile</varname>'s default value is
 	  dictated by the <option>maxusers</option> option in your
           kernel configuration file.  <varname>kern.maxfiles</varname> grows
           proportionally to the value of <option>maxusers</option>.  When
           compiling a custom kernel, it is a good idea to set this kernel
           configuration option according to the uses of your system.  From
           this number, the kernel is given most of its pre-defined limits.
           Even though a production machine may not actually have 256 users
           connected at once, the resources needed may be similar to a
           high-scale web server.</para>
 
 	<para>Starting with &os;&nbsp;4.5, the system will auto-tune
 	  <literal>maxusers</literal> for you if you explicitly set it to
 	  <literal>0</literal><footnote>
 	    <para>The auto-tuning algorithm sets
 	      <literal>maxusers</literal> equal to the amount of memory in the
 	      system, with a minimum of 32, and a maximum of 384.</para>
 	  </footnote>.  In &os;&nbsp;5.X and above, <literal>maxusers</literal>
 	  will default to <literal>0</literal> if not specified.  If you
 	  are using an version of &os; earlier than 4.5, or you want to
 	  manage it yourself you will want to set
 	  <literal>maxusers</literal> to at least 4, especially if you are
 	  using the X Window System or compiling software.  The reason is that
 	  the most important table set by <literal>maxusers</literal> is the
 	  maximum number of processes,  which is set to <literal>20 + 16 *
 	  maxusers</literal>, so if you set <literal>maxusers</literal> to 1,
 	  then you can only have 36 simultaneous processes, including the 18
 	  or so that the system starts up at boot time and the 15 or so you
 	  will probably create when you start the X Window System.  Even a
 	  simple task like reading a manual page will start up nine
 	  processes to filter, decompress, and view it.  Setting
 	  <literal>maxusers</literal> to 64 will allow you to have up to 1044
 	  simultaneous processes, which should be enough for nearly all uses.
 	  If, however, you see the dreaded <errortype>proc table
 	  full</errortype> error when trying to start another program, or are
 	  running a server with a large number of simultaneous users (like
 	  <hostid role="fqdn">ftp.FreeBSD.org</hostid>), you can always
 	  increase the number and rebuild.</para>
 
 	<note>
 	  <para><literal>maxusers</literal> does <emphasis>not</emphasis>
 	    limit the number of users which can log into your machine.  It
 	    simply sets various table sizes to reasonable values considering
 	    the maximum number of users you will likely have on your system
 	    and how many processes each of them will be running.  One keyword
 	    which <emphasis>does</emphasis> limit the number of simultaneous
 	    remote logins and X terminal windows is <link
 	    linkend="kernelconfig-ptys"><literal>pseudo-device pty
 	    16</literal></link>.  With &os;&nbsp;5.X, you do not have to
 	    worry about this number since the &man.pty.4; driver is
 	    <quote>auto-cloning</quote>; you simply use the line
 	    <literal>device pty</literal> in your configuration file.</para>
 	</note>
 
       </sect3>
 
       <sect3>
 	<title><varname>kern.ipc.somaxconn</varname></title>
 
 	<indexterm>
 	  <primary><varname>kern.ipc.somaxconn</varname></primary>
 	</indexterm>
 
 	<para>The <varname>kern.ipc.somaxconn</varname> sysctl variable
 	  limits the size of the listen queue for accepting new TCP
 	  connections.  The default value of <literal>128</literal> is
 	  typically too low for robust handling of new connections in a
 	  heavily loaded web server environment.  For such environments, it
 	  is recommended to increase this value to <literal>1024</literal> or
 	  higher.  The service daemon may itself limit the listen queue size
 	  (e.g. &man.sendmail.8;, or <application>Apache</application>) but
 	  will often have a directive in its configuration file to adjust
 	  the queue size.  Large listen queues also do a better job of
 	  avoiding Denial of Service (<abbrev>DoS</abbrev>) attacks.</para>
       </sect3>
 
     </sect2>
     <sect2 id="nmbclusters">
       <title>Network Limits</title>
 
       <para>The <literal>NMBCLUSTERS</literal> kernel configuration
 	option dictates the amount of network Mbufs available to the
 	system.  A heavily-trafficked server with a low number of Mbufs
 	will hinder &os;'s ability.  Each cluster represents
 	approximately 2&nbsp;K of memory, so a value of 1024 represents 2
 	megabytes of kernel memory reserved for network buffers.  A
 	simple calculation can be done to figure out how many are
 	needed.  If you have a web server which maxes out at 1000
 	simultaneous connections, and each connection eats a 16&nbsp;K receive
 	and 16&nbsp;K send buffer, you need approximately 32&nbsp;MB worth of
 	network buffers to cover the web server.  A good rule of thumb is
 	to multiply by 2, so 2x32&nbsp;MB&nbsp;/&nbsp;2&nbsp;KB&nbsp;=
 	64&nbsp;MB&nbsp;/&nbsp;2&nbsp;kB&nbsp;= 32768.  We recommend
 	values between 4096 and 32768 for machines with greater amounts
 	of memory.  Under no circumstances should you specify an
 	arbitrarily high value for this parameter as it could lead to a
 	boot time crash.  The <option>-m</option> option to
 	&man.netstat.1; may be used to observe network cluster
 	use.</para>
 
       <para><varname>kern.ipc.nmbclusters</varname> loader tunable should
         be used to tune this at boot time.  Only older versions of &os;
         will require you to use the <literal>NMBCLUSTERS</literal> kernel
         &man.config.8; option.</para>
 
       <para>For busy servers that make extensive use of the
 	&man.sendfile.2; system call, it may be necessary to increase
 	the number of &man.sendfile.2; buffers via the
 	<literal>NSFBUFS</literal> kernel configuration option or by
 	setting its value in <filename>/boot/loader.conf</filename>
 	(see &man.loader.8; for details).  A common indicator that
 	this parameter needs to be adjusted is when processes are seen
 	in the <literal>sfbufa</literal> state.  The sysctl
 	variable <varname>kern.ipc.nsfbufs</varname> is a read-only
 	glimpse at the kernel configured variable.  This parameter
 	nominally scales with <varname>kern.maxusers</varname>,
 	however it may be necessary to tune accordingly.</para>
 
       <important>
 	<para>Even though a socket has been marked as non-blocking,
 	  calling &man.sendfile.2; on the non-blocking socket may
 	  result in the &man.sendfile.2; call blocking until enough
 	  <literal>struct sf_buf</literal>'s are made
 	  available.</para>
       </important>
 
       <sect3>
 	<title><varname>net.inet.ip.portrange.*</varname></title>
 
 	<indexterm>
 	  <primary>net.inet.ip.portrange.*</primary>
 	</indexterm>
 
 	<para>The <varname>net.inet.ip.portrange.*</varname> sysctl
 	  variables control the port number ranges automatically bound to TCP
 	  and UDP sockets.  There are three ranges: a low range, a default
 	  range, and a high range.  Most network programs use the default
 	  range which is controlled by the
 	  <varname>net.inet.ip.portrange.first</varname> and
 	  <varname>net.inet.ip.portrange.last</varname>, which default to
 	  1024 and 5000, respectively.  Bound port ranges are used  for
 	  outgoing connections, and it is possible to run the system out of
 	  ports under certain circumstances.  This most commonly occurs
 	  when you are running a heavily loaded web proxy.  The port range
 	  is not an issue when running servers which handle mainly incoming
 	  connections, such as a normal web server, or has a limited number
 	  of outgoing connections, such as a mail relay.  For situations
 	  where you may run yourself out of ports, it is recommended to
 	  increase <varname>net.inet.ip.portrange.last</varname> modestly.
 	  A value of <literal>10000</literal>, <literal>20000</literal> or
 	  <literal>30000</literal> may be reasonable.  You should also
 	  consider firewall effects when changing the port range.  Some
 	  firewalls may block large ranges of ports (usually low-numbered
 	  ports) and expect systems to use higher ranges of ports for
 	  outgoing connections &mdash; for this reason it is not recommended that
 	  <varname>net.inet.ip.portrange.first</varname> be lowered.</para>
       </sect3>
 
       <sect3>
 	<title>TCP Bandwidth Delay Product</title>
 
 	<indexterm>
 	  <primary>TCP Bandwidth Delay Product Limiting</primary>
 	  <secondary><varname>net.inet.tcp.inflight.enable</varname></secondary>
 	</indexterm>
 
 	<para>The TCP Bandwidth Delay Product Limiting is similar to
 	  TCP/Vegas in NetBSD.  It can be
 	  enabled by setting <varname>net.inet.tcp.inflight.enable</varname>
 	  sysctl variable to <literal>1</literal>.  The system will attempt
 	  to calculate the bandwidth delay product for each connection and
 	  limit the amount of data queued to the network to just the amount
 	  required to maintain optimum throughput.</para>
 
 	<para>This feature is useful if you are serving data over modems,
 	  Gigabit Ethernet, or even high speed WAN links (or any other link
 	  with a high bandwidth delay product), especially if you are also
 	  using window scaling or have configured a large send window.  If
 	  you enable this option, you should also be sure to set
 	  <varname>net.inet.tcp.inflight.debug</varname> to
 	  <literal>0</literal> (disable debugging), and for production use
 	  setting <varname>net.inet.tcp.inflight.min</varname> to at least
 	  <literal>6144</literal> may be beneficial.  However, note that
 	  setting high minimums may effectively disable bandwidth limiting
 	  depending on the link.  The limiting feature reduces the amount of
 	  data built up in intermediate route and switch packet queues as
 	  well as reduces the amount of data built up in the local host's
 	  interface queue.  With fewer packets queued up, interactive
 	  connections, especially over slow modems, will also be able to
 	  operate with lower <emphasis>Round Trip Times</emphasis>.  However,
 	  note that this feature only effects data transmission (uploading
 	  / server side).  It has no effect on data reception (downloading).
 	</para>
 
 	<para>Adjusting <varname>net.inet.tcp.inflight.stab</varname> is
 	  <emphasis>not</emphasis> recommended.  This parameter defaults to
 	  20, representing 2 maximal packets added to the bandwidth delay
 	  product window calculation.  The additional window is required to
 	  stabilize the algorithm and improve responsiveness to changing
 	  conditions, but it can also result in higher ping times over slow
 	  links (though still much lower than you would get without the
 	  inflight algorithm).  In such cases, you may wish to try reducing
 	  this parameter to 15, 10, or 5; and may also have to reduce
 	  <varname>net.inet.tcp.inflight.min</varname> (for example, to
 	  3500) to get the desired effect.  Reducing these parameters
 	  should be done as a last resort only.</para>
 
 	<note>
 	  <para>In 4.X and earlier releases of &os; the
 	    <literal>inflight</literal> sysctl variables are directly under
 	    <varname>net.inet.tcp</varname>.  Their names were
 	    (in alphabetic order):
 	    <varname>net.inet.tcp.inflight_debug</varname>,
 	    <varname>net.inet.tcp.inflight_enable</varname>,
 	    <varname>net.inet.tcp.inflight_max</varname>,
 	    <varname>net.inet.tcp.inflight_min</varname>,
 	    <varname>net.inet.tcp.inflight_stab</varname>.</para>
 	</note>
       </sect3>
     </sect2>
 
     <sect2>
       <title>Virtual Memory</title>
 
       <sect3>
         <title><varname>kern.maxvnodes</varname></title>
 
         <para>A vnode is the internal representation of a file or
           directory.  So increasing the number of vnodes available to
           the operating system cuts down on disk I/O.  Normally this
           is handled by the operating system and does not need to be
           changed.  In some cases where disk I/O is a bottleneck and
           the system is running out of vnodes, this setting will need
           to be increased.  The amount of inactive and free RAM will
           need to be taken into account.</para>
 
         <para>To see the current number of vnodes in use:</para>
 
         <programlisting>&prompt.root; sysctl vfs.numvnodes
 vfs.numvnodes: 91349</programlisting>
 
         <para>To see the maximum vnodes:</para>
 
         <programlisting>&prompt.root; sysctl kern.maxvnodes
 kern.maxvnodes: 100000</programlisting>
 
         <para>If the current vnode usage is near the maximum, increasing
           <varname>kern.maxvnodes</varname> by a value of 1,000 is
           probably a good idea.  Keep an eye on the number of
           <varname>vfs.numvnodes</varname>.  If it climbs up to the
           maximum again, <varname>kern.maxvnodes</varname> will need to
           be increased further.  A shift in your memory usage as
           reported by &man.top.1; should be visible.  More memory should
           be active.</para>
       </sect3>
     </sect2>
   </sect1>
 
   <sect1 id="adding-swap-space">
     <title>Adding Swap Space</title>
 
     <para>No matter how well you plan, sometimes a system does not run
       as you expect.  If you find you need more swap space, it is
       simple enough to add.  You have three ways to increase swap
       space: adding a new hard drive, enabling swap over NFS, and
       creating a swap file on an existing partition.</para>
 
     <sect2 id="new-drive-swap">
       <title>Swap on a New Hard Drive</title>
 
       <para>The best way to add swap, of course, is to use this as an
 	excuse to add another hard drive.  You can always use another
 	hard drive, after all.  If you can do this, go reread the
 	discussion of swap space
 	in <xref linkend="configtuning-initial">
 	of the Handbook for some suggestions on how to best
 	arrange your swap.</para>
     </sect2>
 
     <sect2 id="nfs-swap">
       <title>Swapping over NFS</title>
 
       <para>Swapping over NFS is only recommended if you do not have a
 	local hard disk to swap to.  Swapping over NFS is slow and
 	inefficient in versions of &os; prior to 4.X.  It is
 	reasonably fast and efficient in 4.0-RELEASE and newer.  Even
 	with newer versions of &os;, NFS swapping will be limited
 	by the available network bandwidth and puts an additional
 	burden on the NFS server.</para>
     </sect2>
 
     <sect2 id="create-swapfile">
       <title>Swapfiles</title>
 
       <para>You can create a file of a specified size to use as a swap
 	file.  In our example here we will use a 64MB file called
 	<filename>/usr/swap0</filename>.  You can use any name you
 	want, of course.</para>
 
       <example>
         <title>Creating a Swapfile on &os; 4.X</title>
 
       <orderedlist>
         <listitem>
           <para>Be certain that your kernel configuration includes
             the vnode driver.  It is <emphasis>not</emphasis> in recent versions of
             <filename>GENERIC</filename>.</para>
 
           <programlisting>pseudo-device   vn 1   #Vnode driver (turns a file into a device)</programlisting>
         </listitem>
 
 	<listitem>
 	  <para>Create a vn-device:</para>
 	  <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>sh MAKEDEV vn0</userinput></screen>
 	</listitem>
 
 	<listitem>
 	  <para>Create a swapfile (<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>Set proper permissions on (<filename>/usr/swap0</filename>):</para>
 
 	  <screen>&prompt.root; <userinput>chmod 0600 /usr/swap0</userinput></screen>
 	</listitem>
 
 	<listitem>
 	  <para>Enable the swap file in <filename>/etc/rc.conf</filename>:</para>
 
 	  <programlisting>swapfile="/usr/swap0"   # Set to name of swapfile if aux swapfile desired.</programlisting>
 	</listitem>
 
 	<listitem>
 
           <para>Reboot the machine or to enable the swap file immediately,
             type:</para>
 
           <screen>&prompt.root; <userinput>vnconfig -e /dev/vn0b /usr/swap0 swap</userinput></screen>
         </listitem>
       </orderedlist>
 
       </example>
       <example>
 	<title>Creating a Swapfile on &os; 5.X</title>
 
       <orderedlist>
 	<listitem>
 	  <para>Be certain that your kernel configuration includes
 	    the memory disk driver (&man.md.4;).  It is default in
 	    <filename>GENERIC</filename> kernel.</para>
 
 	  <programlisting>device   md   # Memory "disks"</programlisting>
 	</listitem>
 
 	<listitem>
 	  <para>Create a swapfile (<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>Set proper permissions on (<filename>/usr/swap0</filename>):</para>
 
 	  <screen>&prompt.root; <userinput>chmod 0600 /usr/swap0</userinput></screen>
 	</listitem>
 
 	<listitem>
 	  <para>Enable the swap file in <filename>/etc/rc.conf</filename>:</para>
 
 	  <programlisting>swapfile="/usr/swap0"   # Set to name of swapfile if aux swapfile desired.</programlisting>
 	</listitem>
 
 	<listitem>
 
 	  <para>Reboot the machine or to enable the swap file immediately,
             type:</para>
 
 	  <screen>&prompt.root; <userinput>mdconfig -a -t vnode -f /usr/swap0 -u 0 && swapon /dev/md0</userinput></screen>
         </listitem>
       </orderedlist>
 
       </example>
     </sect2>
   </sect1>
 
   <sect1 id="acpi-overview">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Hiten</firstname>
 	  <surname>Pandya</surname>
 	  <contrib>Written by </contrib>
 	</author>
 	<author>
 	  <firstname>Tom</firstname>
 	  <surname>Rhodes</surname>
 	</author>
       </authorgroup>
     </sect1info>
 
     <title>Power and Resource Management</title>
 
     <para>It is very important to utilize hardware resources in an
       efficient manner.  Before <acronym>ACPI</acronym> was introduced,
       it was very difficult and inflexible for operating systems to manage
       the power usage and thermal properties of a system.  The hardware was
       controlled by some sort of <acronym>BIOS</acronym> embedded
       interface, such as <emphasis>Plug and Play BIOS (PNPBIOS)</emphasis>, or
       <emphasis>Advanced Power Management (APM)</emphasis> and so on.
       Power and Resource Management is one of the key components of a modern
       operating system.  For example, you may want an operating system to
       monitor system limits (and possibly alert you) in case your system
       temperature increased unexpectedly.</para>
 
     <para>In this section of the &os; Handbook, we will provide
       comprehensive information about <acronym>ACPI</acronym>.  References
       will be provided for further reading at the end.  Please be aware
       that <acronym>ACPI</acronym> is available on &os;&nbsp;5.X and
       above systems as a default kernel module.  For &os;&nbsp;4.9,
       <acronym>ACPI</acronym> can be enabled by adding the line
       <literal>device acpica</literal> to a kernel configuration and
       rebuilding.</para>
 
     <sect2 id="acpi-intro">
       <title>What Is ACPI?</title>
 
       <indexterm>
 	<primary>ACPI</primary>
       </indexterm>
 
       <indexterm>
 	<primary>APM</primary>
       </indexterm>
 
       <para>Advanced Configuration and Power Interface
 	(<acronym>ACPI</acronym>) is a standard written by
 	an alliance of vendors to provide a standard interface for
 	hardware resources and power management (hence the name).
 	It is a key element in <emphasis>Operating System-directed
 	configuration and Power Management</emphasis>, i.e.: it provides
 	more control and flexibility to the operating system
 	(<acronym>OS</acronym>).
 	Modern systems <quote>stretched</quote> the limits of the
 	current Plug and Play interfaces (such as APM, which is used in
 	&os;&nbsp;4.X), prior to the introduction of
 	<acronym>ACPI</acronym>.  <acronym>ACPI</acronym> is the direct
 	successor to <acronym>APM</acronym>
 	(Advanced Power Management).</para>
     </sect2>
 
     <sect2 id="acpi-old-spec">
       <title>Shortcomings of Advanced Power Management (APM)</title>
 
       <para>The <emphasis>Advanced Power Management (APM)</emphasis>
       facility controls the power usage of a system based on its
       activity.  The APM BIOS is supplied by the (system) vendor and
       it is specific to the hardware platform.  An APM driver in the
       OS mediates access to the <emphasis>APM Software Interface</emphasis>,
       which allows management of power levels.</para>
 
       <para>There are four major problems in APM.  Firstly, power
       management is done by the (vendor-specific) BIOS, and the OS
       does not have any knowledge of it.  One example of this, is when
       the user sets idle-time values for a hard drive in the APM BIOS,
       that when exceeded, it (BIOS) would spin down the hard drive,
       without the consent of the OS.  Secondly, the APM logic is
       embedded in the BIOS, and it operates outside the scope of the
       OS.  This means users can only fix problems in their APM BIOS by
       flashing a new one into the ROM; which is a very dangerous
       procedure with the potential to leave the system in an
       unrecoverable state if it fails. Thirdly, APM is a vendor-specific
       technology, which means that there is a lot of parity
       (duplication of efforts) and bugs found in one vendor's BIOS,
       may not be solved in others.  Last but not the least, the APM
       BIOS did not have enough room to implement a sophisticated power
       policy, or one that can adapt very well to the purpose of the
       machine.</para>
 
       <para><emphasis>Plug and Play BIOS (PNPBIOS)</emphasis> was
       unreliable in many situations.  PNPBIOS is 16-bit technology,
       so the OS has to use 16-bit emulation in order to
       <quote>interface</quote> with PNPBIOS methods.</para>
 
       <para>The &os; <acronym>APM</acronym> driver is documented in
       the &man.apm.4; manual page.</para>
     </sect2>
 
     <sect2 id="acpi-config">
       <title>Configuring <acronym>ACPI</acronym></title>
 
       <para>The <filename>acpi.ko</filename> driver is loaded by default
 	at start up by the &man.loader.8; and should <emphasis>not</emphasis>
 	be compiled into the kernel.  The reasoning behind this is that modules
 	are easier to work with, say if switching to another <filename>acpi.ko</filename>
 	without doing a kernel rebuild.  This has the advantage of making testing easier.
 	Another reason is that starting <acronym>ACPI</acronym> after a system has been
 	brought up is not too useful, and in some cases can be fatal.  In doubt, just
 	disable <acronym>ACPI</acronym> all together. This driver should not and can not
 	be unloaded because the system bus uses it for various hardware interactions.
 	<acronym>ACPI</acronym> can be disabled with the &man.acpiconf.8; utility.
 	In fact most of the interaction with <acronym>ACPI</acronym> can be done via
 	&man.acpiconf.8;.  Basically this means, if anything about <acronym>ACPI</acronym>
 	is in the &man.dmesg.8; output, then most likely it is already running.</para>
 
       <note><para><acronym>ACPI</acronym> and <acronym>APM</acronym> cannot coexist and
 	should be used separately.  The last one to load will terminate if the driver
 	notices the other running.</para></note>
 
       <para>In the simplest form, <acronym>ACPI</acronym> can be used to put the
 	system into a sleep mode with &man.acpiconf.8;, the <option>-s</option>
 	flag, and a <literal>1-5</literal> option.  Most users will only need
 	<literal>1</literal>.  Option <literal>5</literal> will do a soft-off
 	which is the same action as:</para>
 
       <screen>&prompt.root; <userinput>halt -p</userinput></screen>
 
       <para>The other options are available.  Check out the &man.acpiconf.8;
 	manual page for more information.</para>
     </sect2>
   </sect1>
 
   <sect1 id="ACPI-debug">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Nate</firstname>
           <surname>Lawson</surname>
           <contrib>Written by </contrib>
         </author>
       </authorgroup>
       <authorgroup>
         <author>
           <firstname>Peter</firstname>
           <surname>Schultz</surname>
           <contrib>With contributions from </contrib>
         </author>
         <author>
           <firstname>Tom</firstname>
           <surname>Rhodes</surname>
         </author>
       </authorgroup>
     </sect1info>
 
     <title>Using and Debugging &os; <acronym>ACPI</acronym></title>
 
     <indexterm>
       <primary>ACPI</primary>
       <secondary>problems</secondary>
     </indexterm>
 
     <para><acronym>ACPI</acronym> is a fundamentally new way of
       discovering devices, managing power usage, and providing
       standardized access to various hardware previously managed
       by the <acronym>BIOS</acronym>.  Progress is being made toward
       <acronym>ACPI</acronym> working on all systems, but bugs in some
       motherboards' <firstterm><acronym>ACPI</acronym> Machine
       Language</firstterm> (<acronym>AML</acronym>) bytecode,
       incompleteness in &os;'s kernel subsystems, and bugs in the &intel;
       <acronym>ACPI-CA</acronym> interpreter continue to appear.</para>
 
     <para>This document is intended to help you assist the &os;
       <acronym>ACPI</acronym> maintainers in identifying the root cause
       of problems you observe and debugging and developing a solution.
       Thanks for reading this and we hope we can solve your system's
       problems.</para>
 
     <sect2 id="ACPI-submitdebug">
       <title>Submitting Debugging Information</title>
 
       <note>
 	<para>Before submitting a problem, be sure you are running the latest
 	  <acronym>BIOS</acronym> version and, if available, embedded
 	  controller firmware version.</para>
       </note>
 
       <para>For those of you that want to submit a problem right away,
 	please send the following information to
 	<ulink url="mailto:freebsd-acpi@FreeBSD.org">
 	freebsd-acpi@FreeBSD.org</ulink>:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>Description of the buggy behavior, including system type
 	    and model and anything that causes the bug to appear.  Also,
 	    please note as accurately as possible when the bug began
 	    occurring if it is new for you.</para>
 	</listitem>
 
 	<listitem>
 	  <para>The &man.dmesg.8; output after <command>boot
 	    -v</command>, including any error messages
 	    generated by you exercising the bug.</para>
 	</listitem>
 
 	<listitem>
 	  <para>The &man.dmesg.8; output from <command>boot
 	    -v</command> with <acronym>ACPI</acronym>
 	    disabled, if disabling it helps fix the problem.</para>
 	</listitem>
 
 	<listitem>
 	  <para>Output from <command>sysctl hw.acpi</command>.  This is also
 	    a good way of figuring out what features your system
 	    offers.</para>
 	</listitem>
 
 	<listitem>
 	  <para><acronym>URL</acronym> where your
 	    <firstterm><acronym>ACPI</acronym> Source Language</firstterm>
 	    (<acronym>ASL</acronym>)
 	    can be found.  Do <emphasis>not</emphasis> send the
 	    <acronym>ASL</acronym> directly to the list as it can be
 	    very large.  Generate a copy of your <acronym>ASL</acronym>
 	    by running this command:</para>
 
 	  <screen>&prompt.root; <userinput>acpidump -t -d &gt; <replaceable>name</replaceable>-<replaceable>system</replaceable>.asl</userinput></screen>
 
 	  <para>(Substitute your login name for
 	    <replaceable>name</replaceable> and manufacturer/model for
 	    <replaceable>system</replaceable>.  Example:
 	    <filename>njl-FooCo6000.asl</filename>)</para>
 	</listitem>
       </itemizedlist>
 
       <para>Most of the developers watch the &a.current;
         but please submit problems to &a.acpi.name; to be sure it is
 	seen.  Please be patient, all of us have full-time jobs
 	elsewhere.  If your bug is not immediately apparent, we will
 	probably ask you to submit a <acronym>PR</acronym> via
 	&man.send-pr.1;.  When entering a <acronym>PR</acronym>, please
 	include the same information as requested above.  This will help
 	us track the problem and resolve it.  Do not send a
 	<acronym>PR</acronym> without emailing &a.acpi.name; first as we use
 	<acronym>PR</acronym>s as reminders of existing problems, not a
 	reporting mechanism.  It is likely that your problem has been
 	reported by someone before.</para>
     </sect2>
 
     <sect2 id="ACPI-background">
       <title>Background</title>
 
       <indexterm>
 	<primary>ACPI</primary>
       </indexterm>
 
       <para><acronym>ACPI</acronym> is present in all modern computers
 	that conform to the ia32 (x86), ia64 (Itanium), and amd64 (AMD)
 	architectures.  The full standard has many features including
 	<acronym>CPU</acronym> performance management, power planes
 	control, thermal zones, various battery systems, embedded
 	controllers, and bus enumeration.  Most systems implement less
 	than the full standard.  For instance, a desktop system usually
 	only implements the bus enumeration parts while a laptop might
 	have cooling and battery management support as well.  Laptops
 	also have suspend and resume, with their own associated
 	complexity.</para>
 
       <para>An <acronym>ACPI</acronym>-compliant system has various
 	components.  The <acronym>BIOS</acronym> and chipset vendors
 	provide various fixed tables (e.g., <acronym>FADT</acronym>)
 	in memory that specify things like the <acronym>APIC</acronym>
 	map (used for <acronym>SMP</acronym>), config registers, and
 	simple configuration values.  Additionally, a table of bytecode
 	(the <firstterm>Differentiated System Description Table</firstterm>
 	<acronym>DSDT</acronym>) is provided that specifies a
 	tree-like name space of devices and methods.</para>
 
       <para>The <acronym>ACPI</acronym> driver must parse the fixed
 	tables, implement an interpreter for the bytecode, and modify
 	device drivers and the kernel to accept information from the
 	<acronym>ACPI</acronym> subsystem.  For &os;, &intel; has
 	provided an interpreter (<acronym>ACPI-CA</acronym>) that is
 	shared with Linux and NetBSD.  The path to the
 	<acronym>ACPI-CA</acronym> source code is
 	<filename class="directory">src/sys/contrib/dev/acpica</filename>.
 	The glue code that allows <acronym>ACPI-CA</acronym> to work on
 	&os; is in
 	<filename>src/sys/dev/acpica/Osd</filename>.  Finally, drivers
 	that implement various <acronym>ACPI</acronym> devices are found
 	in
 	<filename class="directory">src/sys/dev/acpica</filename>.</para>
     </sect2>
 
     <sect2 id="ACPI-comprob">
       <title>Common Problems</title>
 
       <indexterm>
 	<primary>ACPI</primary>
 	<secondary>problems</secondary>
       </indexterm>
 
       <para>For <acronym>ACPI</acronym> to work correctly, all the parts
 	have to work correctly.  Here are some common problems, in order
 	of frequency of appearance, and some possible workarounds or
 	fixes.</para>
 
       <sect3>
 	<title>Mouse Issues</title>
 
 	<para>In some cases, resuming from a suspend operation will
 	  cause the mouse to fail.  A known work around is to add
 	  <literal>hint.psm.0.flags="0x3000"</literal> to the
 	  <filename>/boot/loader.conf</filename> file.  If this
 	  does not work then please consider sending a bug report
 	  as described above.</para>
       </sect3>
 
       <sect3>
 	<title>Suspend/Resume</title>
 
 	<para><acronym>ACPI</acronym> has three suspend to
 	  <acronym>RAM</acronym> (<acronym>STR</acronym>) states,
 	  <literal>S1</literal>-<literal>S3</literal>, and one suspend
 	  to disk state (<literal>STD</literal>), called
 	  <literal>S4</literal>.  <literal>S5</literal> is
 	  <quote>soft off</quote> and is the normal state your system
 	  is in when plugged in but not powered up.
 	  <literal>S4</literal> can actually be implemented two separate
 	  ways.  <literal>S4</literal><acronym>BIOS</acronym> is a
 	  <acronym>BIOS</acronym>-assisted suspend to disk.
 	  <literal>S4</literal><acronym>OS</acronym> is implemented
 	  entirely by the operating system.</para>
 
 	<para>Start by checking <command>sysctl hw.acpi</command>
 	  for the suspend-related items.  Here
 	  are the results for a Thinkpad:</para>
 
 	<screen>hw.acpi.supported_sleep_state: S3 S4 S5
 hw.acpi.s4bios: 0</screen>
 
 	<para>This means that we can use <command>acpiconf -s</command>
 	  to test <literal>S3</literal>,
 	  <literal>S4</literal><acronym>OS</acronym>, and
 	  <literal>S5</literal>.  If <option>s4bios</option> was one
 	  (<literal>1</literal>), we would have
 	  <literal>S4</literal><acronym>BIOS</acronym>
 	  support instead of <literal>S4</literal>
 	  <acronym>OS</acronym>.</para>
 
 	<para>When testing suspend/resume, start with
 	  <literal>S1</literal>, if supported.  This state is most
 	  likely to work since it does not require much driver support.
 	  No one has implemented <literal>S2</literal> but if you have
 	  it, it is similar to <literal>S1</literal>.  The next thing
 	  to try is <literal>S3</literal>.  This is the deepest
 	  <acronym>STR</acronym> state and requires a lot of driver
 	  support to properly reinitialize your hardware.  If you have
 	  problems resuming, feel free to email the &a.acpi.name; list but
 	  do not expect the problem to be resolved since there are a lot
 	  of drivers/hardware that need more testing and work.</para>
 
 	<para>To help isolate the problem, remove as many drivers from
 	  your kernel as possible.  If it works, you can narrow down
 	  which driver is the problem by loading drivers until it fails
 	  again.  Typically binary drivers like
 	  <filename>nvidia.ko</filename>, X11
 	  display drivers, and <acronym>USB</acronym> will have the most
 	  problems while Ethernet interfaces usually work fine.  If you
 	  can properly load/unload the drivers, you can automate this by
 	  putting the appropriate commands in
 	  <filename>/etc/rc.suspend</filename> and
 	  <filename>/etc/rc.resume</filename>.  There is a
 	  commented-out example for unloading and loading a driver.  Try
 	  setting <option>hw.acpi.reset_video</option> to zero (<literal>0</literal>) if
 	  your display is messed up after resume.  Try setting longer or
 	  shorter values for <option>hw.acpi.sleep_delay</option> to see
 	  if that helps.</para>
 
 	<para>Another thing to try is load a recent Linux distribution
 	  with <acronym>ACPI</acronym> support and test their
 	  suspend/resume support on the same hardware.  If it works
 	  on Linux, it is likely a &os; driver problem and narrowing down
 	  which driver causes the problems will help us fix the problem.
 	  Note that the <acronym>ACPI</acronym> maintainers do not
 	  usually maintain other drivers (e.g sound,
 	  <acronym>ATA</acronym>, etc.) so any work done on tracking
 	  down a driver problem should probably eventually be posted
 	  to the &a.current.name; list and mailed to the driver
 	  maintainer.  If you are feeling adventurous, go ahead and
 	  start putting some debugging &man.printf.3;s in a problematic
 	  driver to track down where in its resume function it
 	  hangs.</para>
 
 	<para>Finally, try disabling <acronym>ACPI</acronym> and
 	  enabling <acronym>APM</acronym> instead.  If suspend/resume
 	  works with <acronym>APM</acronym>, you may be better off
 	  sticking with <acronym>APM</acronym>, especially on older
 	  hardware (pre-2000).  It took vendors a while to get
 	  <acronym>ACPI</acronym> support correct and older hardware is
 	  more likely to have <acronym>BIOS</acronym> problems with
 	  <acronym>ACPI</acronym>.</para>
       </sect3>
 
       <sect3>
 	<title>System Hangs (temporary or permanent)</title>
 
 	<para>Most system hangs are a result of lost interrupts or an
 	  interrupt storm.  Chipsets have a lot of problems based on how
 	  the <acronym>BIOS</acronym> configures interrupts before boot,
 	  correctness of the <acronym>APIC</acronym>
 	  (<acronym>MADT</acronym>) table, and routing of the
 	  <firstterm>System Control Interrupt</firstterm>
 	  (<acronym>SCI</acronym>).</para>
 
 	<indexterm>
 	  <primary>interrupt storms</primary>
 	</indexterm>
 
 	<para>Interrupt storms can be distinguished from lost interrupts
 	  by checking the output of <command>vmstat -i</command>
 	  and looking at the line that has
 	  <literal>acpi0</literal>.  If the counter is increasing at more
 	  than a couple per second, you have an interrupt storm.  If the
 	  system appears hung, try breaking to <acronym>DDB</acronym>
 	  (<keycombo action="simul"><keycap>CTRL</keycap>
 	  <keycap>ALT</keycap><keycap>ESC</keycap></keycombo> on
 	  console) and type <literal>show interrupts</literal>.</para>
 
 	<indexterm>
 	  <primary>APIC</primary>
 	  <secondary>disabling</secondary>
 	</indexterm>
 
 	<para>Your best hope when dealing with interrupt problems is to
 	  try disabling <acronym>APIC</acronym> support with
 	  <literal>hint.apic.0.disabled="1"</literal> in
 	  <filename>loader.conf</filename>.</para>
       </sect3>
 
       <sect3>
 	<title>Panics</title>
 
 	<para>Panics are relatively rare for <acronym>ACPI</acronym> and
 	  are the top priority to be fixed.  The first step is to
 	  isolate the steps to reproduce the panic (if possible)
 	  and get a backtrace.  Follow the advice for enabling
 	  <literal>options DDB</literal> and setting up a serial console
 	  (see <xref linkend="serialconsole-ddb">)
 	  or setting up a &man.dump.8; partition.  You can get a
 	  backtrace in <acronym>DDB</acronym> with
 	  <literal>tr</literal>.  If you have to handwrite the
 	  backtrace, be sure to at least get the lowest five (5) and top
 	  five (5) lines in the trace.</para>
 
 	<para>Then, try to isolate the problem by booting with
 	  <acronym>ACPI</acronym> disabled.  If that works, you can
 	  isolate the <acronym>ACPI</acronym> subsystem by using various
 	  values of <option>debug.acpi.disable</option>.  See the
 	  &man.acpi.4; manual page for some examples.</para>
       </sect3>
 
       <sect3>
 	<title>System Powers Up After Suspend or Shutdown</title>
 	<para>First, try setting
 	  <literal>hw.acpi.disable_on_poweroff="0"</literal>
 	  in &man.loader.conf.5;.  This keeps <acronym>ACPI</acronym>
 	  from disabling various events during the shutdown process.
 	  Some systems need this value set to <literal>1</literal> (the
 	  default) for the same reason.  This usually fixes
 	  the problem of a system powering up spontaneously after a
 	  suspend or poweroff.</para>
       </sect3>
 
       <sect3>
 	<title>Other Problems</title>
 
 	<para>If you have other problems with <acronym>ACPI</acronym>
 	  (working with a docking station, devices not detected, etc.),
 	  please email a description to the mailing list as well;
 	  however, some of these issues may be related to unfinished
 	  parts of the <acronym>ACPI</acronym> subsystem so they might
 	  take a while to be implemented.  Please be patient and
 	  prepared to test patches we may send you.</para>
       </sect3>
     </sect2>
 
     <sect2 id="ACPI-aslanddump">
       <title><acronym>ASL</acronym>, <command>acpidump</command>, and
         <acronym>IASL</acronym></title>
 
       <indexterm>
 	<primary>ACPI</primary>
 	<secondary>ASL</secondary>
       </indexterm>
 
       <para>The most common problem is the <acronym>BIOS</acronym>
 	vendors providing incorrect (or outright buggy!) bytecode.  This
 	is usually manifested by kernel console messages like
 	this:</para>
 
       <screen>ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.LPC0.FIGD._STA] \\
 (Node 0xc3f6d160), AE_NOT_FOUND</screen>
 
       <para>Often, you can resolve these problems by updating your
 	<acronym>BIOS</acronym> to the latest revision.  Most console
 	messages are harmless but if you have other problems like
 	battery status not working, they are a good place to start
 	looking for problems in the <acronym>AML</acronym>.  The
 	bytecode, known as <acronym>AML</acronym>, is compiled from a
 	source language called <acronym>ASL</acronym>.  The
 	<acronym>AML</acronym> is found in the table known as the
 	<acronym>DSDT</acronym>.  To get a copy of your
 	<acronym>ASL</acronym>, use &man.acpidump.8;.  You should use
 	both the <option>-t</option> (show contents of the fixed tables)
 	and <option>-d</option> (disassemble <acronym>AML</acronym> to
 	<acronym>ASL</acronym>) options.  See the
 	<link linkend="ACPI-submitdebug">Submitting Debugging
 	Information</link> section for an example syntax.</para>
 
       <para>The simplest first check you can do is to recompile your
 	<acronym>ASL</acronym> to check for errors.  Warnings can
 	usually be ignored but errors are bugs that will usually prevent
 	<acronym>ACPI</acronym> from working correctly.  To recompile
 	your <acronym>ASL</acronym>, issue the following command:</para>
 
       <screen>&prompt.root; <userinput>iasl your.asl</userinput></screen>
     </sect2>
 
     <sect2 id="ACPI-fixasl">
       <title>Fixing Your <acronym>ASL</acronym></title>
 
       <indexterm>
 	<primary>ACPI</primary>
 	<secondary>ASL</secondary>
       </indexterm>
 
       <para>In the long run, our goal is for almost everyone to have
 	<acronym>ACPI</acronym> work without any user intervention.  At
 	this point, however, we are still developing workarounds for
 	common mistakes made by the <acronym>BIOS</acronym> vendors.
 	The &microsoft; interpreter (<filename>acpi.sys</filename> and
 	<filename>acpiec.sys</filename>) does not strictly check for
 	adherence to the standard, and thus many <acronym>BIOS</acronym>
 	vendors who only test <acronym>ACPI</acronym> under &windows;
 	never fix their <acronym>ASL</acronym>.  We hope to continue to
 	identify and document exactly what non-standard behavior is
 	allowed by &microsoft;'s interpreter and replicate it so &os; can
 	work without forcing users to fix the <acronym>ASL</acronym>.
 	As a workaround and to help us identify behavior, you can fix
 	the <acronym>ASL</acronym> manually.  If this works for you,
 	please send a &man.diff.1; of the old and new
 	<acronym>ASL</acronym> so we can possibly work around the buggy
 	behavior in <acronym>ACPI-CA</acronym> and thus make your fix
 	unnecessary.</para>
 
       <indexterm>
 	<primary>ACPI</primary>
 	<secondary>error messages</secondary>
       </indexterm>
 
       <para>Here is a list of common error messages, their cause, and
 	how to fix them:</para>
 
       <sect3>
 	<title>_OS dependencies</title>
 
 	<para>Some <acronym>AML</acronym> assumes the world consists of
 	  various &windows; versions.  You can tell &os; to claim it is
 	  any <acronym>OS</acronym> to see if this fixes problems you
 	  may have.  An easy way to override this is to set
 	  <literal>hw.acpi.osname="Windows 2001"</literal>
 	  in <filename>/boot/loader.conf</filename> or other similar
 	  strings you find in the <acronym>ASL</acronym>.</para>
       </sect3>
 
       <sect3>
 	<title>Missing Return statements</title>
 
 	<para>Some methods do not explicitly return a value as the
 	  standard requires.  While <acronym>ACPI-CA</acronym>
 	  does not handle this, &os; has a workaround that allows it to
 	  return the value implicitly.  You can also add explicit
 	  Return statements where required if you know what value should
 	  be returned.  To force <command>iasl</command> to compile the
 	  <acronym>ASL</acronym>, use the <option>-f</option>
 	  flag.</para>
       </sect3>
 
       <sect3>
 	<title>Overriding the Default <acronym>AML</acronym></title>
 
 	<para>After you customize <filename>your.asl</filename>, you
 	  will want to compile it, run:</para>
 
 	<screen>&prompt.root; <userinput>iasl your.asl</userinput></screen>
 
 	<para>You can add the <option>-f</option> flag to force creation
 	  of the <acronym>AML</acronym>, even if there are errors during
 	  compilation.  Remember that some errors (e.g., missing Return
 	  statements) are automatically worked around by the
 	  interpreter.</para>
 
 	<para><filename>DSDT.aml</filename> is the default output
 	  filename for <command>iasl</command>.  You can load this
 	  instead of your <acronym>BIOS</acronym>'s buggy copy (which
 	  is still present in flash memory) by editing
 	  <filename>/boot/loader.conf</filename> as
 	  follows:</para>
 
 	<programlisting>acpi_dsdt_load="YES"
 acpi_dsdt_name="/boot/DSDT.aml"</programlisting>
 
 	<para>Be sure to copy your <filename>DSDT.aml</filename> to the
 	  <filename class="directory">/boot</filename> directory.</para>
       </sect3>
     </sect2>
 
     <sect2 id="ACPI-debugoutput">
       <title>Getting Debugging Output From
 	<acronym>ACPI</acronym></title>
 
       <indexterm>
 	<primary>ACPI</primary>
 	<secondary>problems</secondary>
       </indexterm>
 
       <indexterm>
 	<primary>ACPI</primary>
 	<secondary>debugging</secondary>
       </indexterm>
 
       <para>The <acronym>ACPI</acronym> driver has a very flexible
 	debugging facility.  It allows you to specify a set of subsystems
 	as well as the level of verbosity.  The subsystems you wish to
 	debug are specified as <quote>layers</quote> and are broken down
 	into <acronym>ACPI-CA</acronym> components (ACPI_ALL_COMPONENTS)
 	and <acronym>ACPI</acronym> hardware support (ACPI_ALL_DRIVERS).
 	The verbosity of debugging output is specified as the
 	<quote>level</quote> and ranges from ACPI_LV_ERROR (just report
 	errors) to ACPI_LV_VERBOSE (everything).  The
 	<quote>level</quote> is a bitmask so multiple options can be set
 	at once, separated by spaces.  In practice, you will want to use
 	a serial console to log the output if it is so long
 	it flushes the console message buffer.  A full list of the
 	individual layers and levels is found in the &man.acpi.4; manual
 	page.</para>
 
       <para>Debugging output is not enabled by default.  To enable it,
 	add <literal>options ACPI_DEBUG</literal> to your kernel configuration file
 	if <acronym>ACPI</acronym> is compiled into the kernel.  You can
 	add <literal>ACPI_DEBUG=1</literal> to your
 	<filename>/etc/make.conf</filename> to enable it globally.  If
 	it is a module, you can recompile just your
 	<filename>acpi.ko</filename> module as follows:</para>
 
       <screen>&prompt.root; <userinput>cd /sys/modules/acpi/acpi
 &amp;&amp; make clean &amp;&amp;
 make ACPI_DEBUG=1</userinput></screen>
 
       <para>Install <filename>acpi.ko</filename> in
 	<filename class="directory">/boot/kernel</filename> and add your
 	desired level and layer to <filename>loader.conf</filename>.
 	This example enables debug messages for all
 	<acronym>ACPI-CA</acronym> components and all
 	<acronym>ACPI</acronym> hardware drivers
 	(<acronym>CPU</acronym>, <acronym>LID</acronym>, etc.)  It will
 	only output error messages, the least verbose level.</para>
 
       <programlisting>debug.acpi.layer="ACPI_ALL_COMPONENTS ACPI_ALL_DRIVERS"
 debug.acpi.level="ACPI_LV_ERROR"</programlisting>
 
       <para>If the information you want is triggered by a specific event
 	(say, a suspend and then resume), you can leave out changes to
 	<filename>loader.conf</filename> and instead use
 	<command>sysctl</command> to specify the layer and level after
 	booting and preparing your system for the specific event.  The
 	<command>sysctl</command>s are named the same as the tunables
 	in <filename>loader.conf</filename>.</para>
     </sect2>
 
     <sect2 id="ACPI-References">
       <title>References</title>
 
       <para>More information about <acronym>ACPI</acronym> may be found
 	in the following locations:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>The &a.acpi;</para>
 	</listitem>
 
 	<listitem>
 	  <para>The <acronym>ACPI</acronym> Mailing List Archives
 	    <ulink url="http://lists.freebsd.org/pipermail/freebsd-acpi/"></ulink></para>
 	</listitem>
 
         <listitem>
           <para>The old <acronym>ACPI</acronym> Mailing List Archives
             <ulink url="http://home.jp.FreeBSD.org/mail-list/acpi-jp/"></ulink></para>
         </listitem>
 
 	<listitem>
 	  <para>The <acronym>ACPI</acronym> 2.0 Specification
 	    <ulink url="http://acpi.info/spec.htm"></ulink></para>
 	</listitem>
 
 	<listitem>
 	  <para>&os; Manual pages: &man.acpi.4;,
 	    &man.acpi.thermal.4;, &man.acpidump.8;, &man.iasl.8;,
 	    &man.acpidb.8;</para>
 	</listitem>
 
 	<listitem>
 	  <para><ulink
 	    url="http://www.cpqlinux.com/acpi-howto.html#fix_broken_dsdt">
 	    <acronym>DSDT</acronym> debugging resource</ulink>.
 	    (Uses Compaq as an example but generally useful.)</para>
 	</listitem>
       </itemizedlist>
     </sect2>
   </sect1>
 </chapter>
 
 <!--
      Local Variables:
      mode: sgml
      sgml-declaration: "../chapter.decl"
      sgml-indent-data: t
      sgml-omittag: nil
      sgml-always-quote-attributes: t
      sgml-parent-document: ("../book.sgml" "part" "chapter")
      End:
 -->
diff --git a/zh_TW.Big5/books/handbook/disks/chapter.sgml b/zh_TW.Big5/books/handbook/disks/chapter.sgml
index 0ee4475317..d767f4a0d1 100644
--- a/zh_TW.Big5/books/handbook/disks/chapter.sgml
+++ b/zh_TW.Big5/books/handbook/disks/chapter.sgml
@@ -1,3904 +1,4130 @@
 <!--
      The FreeBSD Documentation Project
 
      $FreeBSD$
 -->
 
 <chapter id="disks">
-  <title>Storage</title>
+  <title>Àx¦s´CÅé</title>
 
   <sect1 id="disks-synopsis">
-    <title>Synopsis</title>
+    <title>·§­z</title>
 
 
-    <para>This chapter covers the use of disks in FreeBSD.  This
-      includes memory-backed disks, network-attached disks,
-      standard SCSI/IDE storage devices, and devices using the USB
-      interface.</para>
+    <para>¥»³¹²[»\¦p¦ó¦b FreeBSD ¤U¨Ï¥ÎºÐ¤ù¸Ë¸m¡A¥]§t 
+	memory-backed disk (¥Î°O¾ÐÅé§@¬°µwºÐ¨Ï¥Î)¡B¸óºô¸ô¨Ï¥ÎªºµwºÐ¡B
+	¼Ð·Ç SCSI/IDE µwºÐ¡BUSB ¤¶­±ªº³]³Æµ¥¡C</para>
 
-    <para>After reading this chapter, you will know:</para>
+    <para>¾\Ū¥»³¹«á¡A±z¸Ë¾Ç·|¡G</para>
     <itemizedlist>
-      <listitem><para>The terminology FreeBSD uses to describe the
-      organization of data on a physical disk (partitions and slices).</para>
+      <listitem><para>FreeBSD ¦p¦ó´y­z¸ê®Æ¦bµwºÐ¤Wªº¹º¤À±¡§Î
+	  (partition ©M slices)¡C</para>
       </listitem>
-      <listitem><para>How to add additional hard disks to your system.</para>
+      <listitem><para>¦p¦ó¦b¨t²Î¤W¥[¤JµwºÐ</para>
       </listitem>
       <listitem>
-	<para>How to configure &os; to use USB storage devices.</para>
+	<para>¦p¦ó³]©w &os; ¨Ó¨Ï¥Î USB ¸Ë¸m¡C</para>
       </listitem>
-      <listitem><para>How to set up virtual file systems, such as memory
-      disks.</para></listitem>
+      <listitem><para>¦p¦ó³]©wµêÀÀÀɮרt²Î (virtual file systems), 
+	  ¨Ò¦p memory disks (¥Î°O¾ÐÅé§@¬°µwºÐ¨Ï¥Î)¡C</para></listitem>
       <listitem>
-	<para>How to use quotas to limit disk space usage.</para>
+	<para>¦p¦ó¥Î quota ¨Ó­­¨îµwºÐªÅ¶¡ªº¨Ï¥Î¡C</para>
       </listitem>
       <listitem>
-	<para>How to encrypt disks to secure them against attackers.</para>
+	<para>¦p¦ó¹ïµwºÐ¥[±K¥HÀ³¥I§ðÀ»¡C</para>
       </listitem>
       <listitem>
-	<para>How to create and burn CDs and DVDs on FreeBSD.</para>
+	<para>¦p¦ó¦b FreeBSD ¤U«Ø¥ß¡B¿N¿ý CD ©M DVD¡C</para>
       </listitem>
       <listitem>
-        <para>The various storage media options for backups.</para>
+        <para>¦UºØ¤£¦Pªº³Æ¥÷³]³Æ¡C</para>
       </listitem>
       <listitem>
-        <para>How to use backup programs available under FreeBSD.</para>
+        <para>¦p¦ó¨Ï¥Î FreeBSD ´£¨Ñªº³Æ¥÷¤u¨ã¡C</para>
       </listitem>
       <listitem>
-        <para>How to backup to floppy disks.</para>
+        <para>¦p¦ó³Æ¥÷¨ì³nºÐ¡C</para>
       </listitem>
       <listitem>
-        <para>What snapshots are and how to use them efficiently.</para>
+        <para>¤°»ò¬O snapshots ¡A¥B¦p¦ó¦³®Ä²v¦a¨Ï¥Î¤§¡C</para>
       </listitem>
     </itemizedlist>
 
-    <para>Before reading this chapter, you should:</para>
+    <para>¦b¾\Ū¤§«e¡A±zÀ³¸Ó¡G</para>
 
     <itemizedlist>
       <listitem>
-        <para>Know how to configure and install a new FreeBSD kernel
+        <para>ª¾¹D¦p¦ó°t¸m¡B¦w¸Ë·sªº FreeBSD ®Ö¤ß¡C
           (<xref linkend="kernelconfig">).</para>
       </listitem>
     </itemizedlist>
 
   </sect1>
 
   <sect1 id="disks-naming">
-    <title>Device Names</title>
+    <title>¸Ë¸m¦WºÙ</title>
 
-    <para>The following is a list of physical storage devices
-      supported in FreeBSD, and the device names associated with
-      them.</para>
+    <para>¤U­±¬O FreeBSD ¤ä´©ªºÀx¦s´CÅé¦Cªí¡A¤Î¥¦­Ì¹ïÀ³ªº¸Ë¸m¦WºÙ¡C</para>
 
     <table id="disk-naming-physical-table" frame="none">
-      <title>Physical Disk Naming Conventions</title>
+      <title>©R¦W³W«h</title>
 
       <tgroup cols="2">
 	<thead>
 	  <row>
-	    <entry>Drive type</entry>
-	    <entry>Drive device name</entry>
+	    <entry>¸Ë¸mÃþ«¬</entry>
+	    <entry>¸Ë¸m¦WºÙ</entry>
 	  </row>
 	</thead>
 	<tbody>
 	  <row>
-	    <entry>IDE hard drives</entry>
+	    <entry>IDE µwºÐ¾÷</entry>
 	    <entry><literal>ad</literal></entry>
 	  </row>
 	  <row>
-	    <entry>IDE CDROM drives</entry>
+	    <entry>IDE ¥úºÐ¾÷</entry>
 	    <entry><literal>acd</literal></entry>
 	  </row>
 	  <row>
-	    <entry>SCSI hard drives and USB Mass storage devices</entry>
+	    <entry>SCSI µwºÐ¾÷©M USB ºÐ</entry>
 	    <entry><literal>da</literal></entry>
 	  </row>
 	  <row>
-	    <entry>SCSI CDROM drives</entry>
+	    <entry>SCSI ¥úºÐ¾÷</entry>
 	    <entry><literal>cd</literal></entry>
 	  </row>
 	  <row>
-	    <entry>Assorted non-standard CDROM drives</entry>
-	    <entry><literal>mcd</literal> for Mitsumi CD-ROM,
-	      <literal>scd</literal> for Sony CD-ROM,
-	      <literal>matcd</literal> for Matsushita/Panasonic CD-ROM
+	    <entry>«D¼Ð·Ç³W®æ¥úºÐ¾÷</entry>
+	    <entry>Mitsumi ¥úºÐ¾÷¥Î <literal>mcd</literal>¡A
+	      Sony ¥úºÐ¾÷¥Î <literal>scd</literal>¡A
+	      Matsushita/Pansonic ¥úºÐ¾÷¥Î <literal>matcd</literal> 
 		<footnote>
-		  <para>The &man.matcd.4; driver has been removed
-		    in FreeBSD&nbsp;4.X branch since October 5th,
-		    2002 and does not exist in FreeBSD&nbsp;5.0 and
-		    later releases.</para>
+		  <para>2002 ¦~ 10 ¤ë 5 ¤é FreeBSD 4.X ²¾°£¤F &man.matcd.4; ÅX°Êµ{¦¡¡A
+		  ¦]¦¹ FreeBSD 5.0 ¤Î¥H«áªºª©¥»¤£¦A¤ä´©¡C</para>
 		</footnote>
 	    </entry>
 	  </row>
 	  <row>
-	    <entry>Floppy drives</entry>
+	    <entry>³nºÐ¾÷</entry>
 	    <entry><literal>fd</literal></entry>
 	  </row>
 	  <row>
-	    <entry>SCSI tape drives</entry>
+	    <entry>SCSI ºÐ±a¾÷</entry>
 	    <entry><literal>sa</literal></entry>
             </row>
 	  <row>
-	    <entry>IDE tape drives</entry>
+	    <entry>IDE ºÐ±a¾÷</entry>
 	    <entry><literal>ast</literal></entry>
 	  </row>
 	  <row>
-	    <entry>Flash drives</entry>
-	    <entry><literal>fla</literal> for &diskonchip; Flash device</entry>
+	    <entry>Flash ºÏºÐ¾÷</entry>
+	    <entry>&diskonchip; Flash ºÏºÐ¾÷¥Î <literal>fla</literal></entry>
 	  </row>
 	  <row>
-	    <entry>RAID drives</entry>
-	    <entry><literal>aacd</literal> for &adaptec; AdvancedRAID,
-	      <literal>mlxd</literal> and <literal>mlyd</literal>
-	      for &mylex;,
-	      <literal>amrd</literal> for AMI &megaraid;,
-	      <literal>idad</literal> for Compaq Smart RAID,
-	      <literal>twed</literal> for &tm.3ware; RAID.</entry>
+	    <entry>RAID ºÏºÐ¾÷</entry>
+	    <entry>&adaptec; AdvancedRAID ¥Î<literal>aacd</literal>¡A
+	      &mylex; ¥Î <literal>mlxd</literal> ©M <literal>mlyd</literal>¡A
+	      AMI &megaraid; ¥Î <literal>amrd</literal>¡A
+	      Compaq Smart RAID ¥Î <literal>idad</literal>¡A
+	      &tm.3ware; RAID ¥Î <literal>twed</literal>¡C</entry>
 	  </row>
 	</tbody>
       </tgroup>
     </table>
   </sect1>
 
   <sect1 id="disks-adding">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>David</firstname>
 	  <surname>O'Brien</surname>
 	  <contrib>Originally contributed by </contrib>
 	</author>
       </authorgroup>
       <!-- 26 Apr 1998 -->
     </sect1info>
 
-    <title>Adding Disks</title>
+    <title>·s¼WµwºÐ</title>
 
     <indexterm>
-      <primary>disks</primary>
+      <primary>disk</primary>
       <secondary>adding</secondary>
     </indexterm>
 
-    <para>Lets say we want to add a new SCSI disk to a machine that
-      currently only has a single drive.  First turn off the computer
-      and install the drive in the computer following the instructions
-      of the computer, controller, and drive manufacturer.  Due to the
-      wide variations of procedures to do this, the details are beyond
-      the scope of this document.</para>
-
-    <para>Login as user <username>root</username>.  After you have installed the
-      drive, inspect <filename>/var/run/dmesg.boot</filename> to ensure the new
-      disk was found.  Continuing with our example, the newly added drive will
-      be <devicename>da1</devicename> and we want to mount it on
-      <filename>/1</filename> (if you are adding an IDE drive, the device name
-      will be <devicename>wd1</devicename> in pre-4.0 systems, or
-      <devicename>ad1</devicename> in 4.X and 5.X systems).</para>
+    <para>°²³]§Ú­Ì·Q·s¼W SCSI µwºÐ¨ì¤@»O­ì¥ý¥u¦³¤@ÁûµwºÐªº¾÷¾¹¤W¡A
+	­º¥ý±N¹q¸£Ãö¾÷¡A¨Ì»s³y°Óªº«ü¥Ü±NµwºÐ¸Ë¤W¥h¡A
+	¸Ô²Óªº¾Þ§@¤è¦¡½Ð°Ñ¦Ò»s³y°Óªº»¡©ú¤å¥ó¡C</para>
+
+    <para>¦w¸Ë¦nµwºÐ«á¡A¥Î <username>root</username> µn¤J¨t²Î¡A
+	¬Ý¤@¤U <filename>/var/run/dmesg.boot</filename> ¥H½T»{¨t²Î¬O§_§ì¨ì·sµwºÐ¡C
+	Ä~Äò­è¤~ªº½d¨Ò¡A·s¼WªºµwºÐ·|¬O <devicename>da1</devicename>¡A
+	°²³]§Ú­Ì·Q±N¥¦±¾¸ü¨ì <filename>/1</filename> ³o­Ó¦ì¸m
+	(¦pªG±z·s¼Wªº¬O IDE µwºÐªº¸Ü¡A4.0 ¤§«eªº¨t²Î¬O 
+	 <devicename>wd1</devicename>¡A4.X ¤Î¤§«áªº¨t²Î«h¬O
+	 <devicename>ad1</devicename>)¡C</para>
 
     <indexterm><primary>partitions</primary></indexterm>
     <indexterm><primary>slices</primary></indexterm>
     <indexterm>
       <primary><command>fdisk</command></primary>
     </indexterm>
 
-    <para>FreeBSD runs on IBM-PC compatible computers, therefore it must
-      take into account the PC BIOS partitions.  These are different
-      from the traditional BSD partitions.  A PC disk has up to four
-      BIOS partition entries.  If the disk is going to be truly
-      dedicated to FreeBSD, you can use the
-      <emphasis>dedicated</emphasis> mode.  Otherwise, FreeBSD will
-      have to live within one of the PC BIOS partitions.  FreeBSD
-      calls the PC BIOS partitions <emphasis>slices</emphasis> so as
-      not to confuse them with traditional BSD partitions.  You may
-      also use slices on a disk that is dedicated to FreeBSD, but used
-      in a computer that also has another operating system installed.
-      This is a good way to avoid confusing the <command>fdisk</command> utility of
-      other, non-FreeBSD operating systems.</para>
-
-    <para>In the slice case the drive will be added as
-      <filename>/dev/da1s1e</filename>.  This is read as: SCSI disk,
-      unit number 1 (second SCSI disk), slice 1 (PC BIOS partition 1),
-      and <filename>e</filename> BSD partition.  In the dedicated
-      case, the drive will be added simply as
-      <filename>/dev/da1e</filename>.</para>
-
-    <para>Due to the use of 32-bit integers to store the number of sectors,
-      &man.bsdlabel.8; (called &man.disklabel.8; in &os;&nbsp;4.X) is
-      limited to 2^32-1 sectors per disk or 2TB in most cases.  The
-      &man.fdisk.8; format allows a starting sector of no more than
-      2^32-1 and a length of no more than 2^32-1, limiting partitions to
-      2TB and disks to 4TB in most cases.  The &man.sunlabel.8; format
-      is limited to 2^32-1 sectors per partition and 8 partitions for
-      a total of 16TB. For larger disks, &man.gpt.8; partitions may be
-      used.</para>
+    <para>FreeBSD ¬°¤F¦b IBM-PC ¬Û®e¹q¸£¤W°õ¦æ¡A
+	¥²¶·°t¦X PC BIOS partition¡A¦]¦¹©M¶Ç²Îªº BSD partition ¦³«Ü¤jªº¤£¦P¡C
+	¦b PC ¸ÌµwºÐ³Ì¦h¥i¥H¦³¥|µ§ BIOS partition ¸ê°T(¥ç§Y³Ì¦h¥i¤À³Î¦¨¥|­Ó 
+	partition)¡C¦pªG³o­ÓµwºÐ¥´ºâ¥þ³¡Åý FreeBSD ¨Ï¥Î¡A¥i¿ï¾Ü
+	<emphasis>dedicated</emphasis> ¼Ò¦¡¡A
+	¤£µMªº¸Ü FreeBSD ¥²¶·¸m¨­©ó¨ä¤¤¤@­Ó PC BIOS partition ¤¤¡C
+	¦b FreeBSD ¸Ì¡APC BIOS partition ºÙ¬° <emphasis>slice</emphasis>¡A
+	³o¬O¬°¤F¤£­n©M¶Ç²Îªº BSD partition ·d²V¤F¡C
+	¤£½×¬O§¹¥þ¥Ñ FreeBSD ¨Ï¥ÎªºµwºÐ¡AÁÙ¬O¦w¸Ë¤F¨ä¥¦§@·~¨t²ÎªºµwºÐ¡A
+	±z³£¥i¥H¨Ï¥Î slice¡C³o¼Ëªº¦n³B¬O¡A¨ä¥¦«D FreeBSD §@·~¨t²Îªº
+	<command>fdisk</command> ¤u¨ã¥i¥H¶¶§Q¾Þ§@¡C</para>
+
+    <para>¦pªG¨Ï¥Î slice¡A³o­Ó·s¼WªºµwºÐ·|¬O 
+	<filename>/dev/da1s1e</filename>¡C¥i¥H³o¼Ë¨Ó¸ÑŪ¥¦¡GSCSI µwºÐ¡B
+	unit number 1(²Ä¤G­Ó SCSI µwºÐ)¡Bslice 1(²Ä¤@­Ó PC BIOS partition)¡B
+	¤Î <filename>e</filename> BSD partition¡C¦b dedicated ¼Ò¦¡ªº¸Ü¡A
+	·sµwºÐ«h¬O <filename>/dev/da1e</filename>¡C</para>
+
+    <para>¦]¬° &man.bsdlabel.8;(¦b &os;&nbsp;4.X ºÙ¬° &man.disklabel.8;)
+	¥Î 32-bit ¾ã¼Æ¨ÓÀx¦s sector(ºÏ°Ï) ¼Æ¡A
+	¦]¦¹­­¨î¤@­ÓµwºÐ³Ì¤j¥u¯à¦³ 2^32-1 ­Ó sector¡A¥ç§Y 2TB ªºªÅ¶¡¡C
+	¦Ó &man.fdisk.8; ªº®æ¦¡®e³\°_©l sector ½s¸¹¤£¶W¹L 2^32-1¡A
+	ªø«×¤]¤£¶W¹L 2^32-1¡A¦]¦¹ partition ³Ì¤jªÅ¶¡¬O 2TB¡A¦ÓµwºÐ³Ì¤j¬O 4TB¡C
+	&man.sunlabel.8; «h­­¨î partition ³Ì¤j¬O 2TB¡AµwºÐ³Ì¦h¥i¦³ 8 ­Ó partition¡A
+	¦]¦¹³Ì¤j¬O 16TB¡C¦pªG­n¨Ï¥Î§ó¤jªºµwºÐ¡A½Ð¨Ï¥Î &man.gpt.8;¡C</para>
 
     <sect2>
       <title>Using &man.sysinstall.8;</title>
       <indexterm>
         <primary><application>sysinstall</application></primary>
         <secondary>adding disks</secondary>
       </indexterm>
       <indexterm>
 	<primary>su</primary>
       </indexterm>
       <procedure>
 	<step>
 	  <title>Navigating <application>Sysinstall</application></title>
 
 	  <para>You may use <command>sysinstall</command>
 	    (<command>/stand/sysinstall</command> in &os; versions older
 	    than 5.2) to
 	    partition and label a new disk using its easy to use menus.
 	    Either login as user <username>root</username> or use the
 	    <command>su</command> command.  Run
 	    <command>sysinstall</command> and enter the
 	    <literal>Configure</literal> menu.  Within the
 	    <literal>FreeBSD Configuration Menu</literal>, scroll down and
 	    select the <literal>Fdisk</literal> option.</para>
 	</step>
 
 	<step>
 	  <title><application>fdisk</application> Partition Editor</title>
 	  <para>Once inside <application>fdisk</application>, typing <userinput>A</userinput> will
 	    use the entire disk for FreeBSD.  When asked if you want to
 	    <quote>remain cooperative with any future possible operating
 	      systems</quote>, answer <literal>YES</literal>.  Write the
 	    changes to the disk using <userinput>W</userinput>.  Now exit the
 	    FDISK editor by typing <userinput>q</userinput>.  Next you will be
 	    asked about the <quote>Master Boot Record</quote>.  Since you are adding a
 	    disk to an already running system, choose
 	    <literal>None</literal>.</para>
 	</step>
 
 	<step>
 	  <title>Disk Label Editor</title>
 	  <indexterm><primary>BSD partitions</primary></indexterm>
 
 	  <para>Next, you need to exit <application>sysinstall</application>
             and start it again.  Follow the directions above, although this
             time choose the <literal>Label</literal> option. This will
 	    enter the <literal>Disk Label Editor</literal>.  This
 	    is where you will create the traditional BSD partitions.  A
 	    disk can have up to eight partitions, labeled
 	    <literal>a-h</literal>.
 	    A few of the partition labels have special uses.  The
 	    <literal>a</literal> partition is used for the root partition
 	    (<filename>/</filename>).  Thus only your system disk (e.g,
 	    the disk you boot from) should have an <literal>a</literal>
 	    partition.  The <literal>b</literal> partition is used for
 	    swap partitions, and you may have many disks with swap
 	    partitions.  The <literal>c</literal> partition addresses the
 	    entire disk in dedicated mode, or the entire FreeBSD slice in
 	    slice mode.  The other partitions are for general use.</para>
 
 	  <para><application>sysinstall</application>'s Label editor
 	    favors the <literal>e</literal>
 	    partition for non-root, non-swap partitions.  Within the
 	    Label editor, create a single file system by typing
 	    <userinput>C</userinput>.  When prompted if this will be a FS
 	    (file system) or swap, choose <literal>FS</literal> and type in a
 	    mount point (e.g, <filename>/mnt</filename>).  When adding a
 	    disk in post-install mode, <application>sysinstall</application>
 	    will not create entries
 	    in <filename>/etc/fstab</filename> for you, so the mount point
 	    you specify is not important.</para>
 
 	  <para>You are now ready to write the new label to the disk and
 	    create a file system on it.  Do this by typing
 	    <userinput>W</userinput>.  Ignore any errors from
 	    <application>sysinstall</application> that
 	    it could not mount the new partition.  Exit the Label Editor
 	    and <application>sysinstall</application> completely.</para>
 	</step>
 
 	<step>
 	  <title>Finish</title>
 
 	  <para>The last step is to edit <filename>/etc/fstab</filename>
 	    to add an entry for your new disk.</para>
 	</step>
       </procedure>
     </sect2>
 
     <sect2>
       <title>Using Command Line Utilities</title>
 
       <sect3>
 	<title>Using Slices</title>
 
 	<para>This setup will allow your disk to work correctly with
 	  other operating systems that might be installed on your
 	  computer and will not confuse other operating systems'
 	  <command>fdisk</command> utilities.  It is recommended
 	  to use this method for new disk installs.  Only use
 	  <literal>dedicated</literal> mode if you have a good reason
 	  to do so!</para>
 
 	<screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/da1 bs=1k count=1</userinput>
 &prompt.root; <userinput>fdisk -BI da1</userinput> #Initialize your new disk
 &prompt.root; <userinput>disklabel -B -w -r da1s1 auto</userinput> #Label it.
 &prompt.root; <userinput>disklabel -e da1s1</userinput> # Edit the disklabel just created and add any partitions.
 &prompt.root; <userinput>mkdir -p /1</userinput>
 &prompt.root; <userinput>newfs /dev/da1s1e</userinput> # Repeat this for every partition you created.
 &prompt.root; <userinput>mount /dev/da1s1e /1</userinput> # Mount the partition(s)
 &prompt.root; <userinput>vi /etc/fstab</userinput> # Add the appropriate entry/entries to your <filename>/etc/fstab</filename>.</screen>
 
 	<para>If you have an IDE disk, substitute <filename>ad</filename>
 	  for <filename>da</filename>.  On pre-4.X systems use
 	  <filename>wd</filename>.</para>
       </sect3>
 
       <sect3>
 	<title>Dedicated</title>
 	<indexterm><primary>OS/2</primary></indexterm>
 
 	<para>If you will not be sharing the new drive with another operating
 	  system, you may use the <literal>dedicated</literal> mode.  Remember
 	  this mode can confuse Microsoft operating systems; however, no damage
 	  will be done by them.  IBM's &os2; however, will
 	  <quote>appropriate</quote> any partition it finds which it does not
 	  understand.</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>				# create the `e' partition
 &prompt.root; <userinput>newfs -d0 /dev/da1e</userinput>
 &prompt.root; <userinput>mkdir -p /1</userinput>
 &prompt.root; <userinput>vi /etc/fstab</userinput>				# add an entry for /dev/da1e
 &prompt.root; <userinput>mount /1</userinput></screen>
 
 	<para>An alternate method is:</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>					# add an entry for /dev/da1e
 &prompt.root; <userinput>mount /1</userinput></screen>
 
 	<note><para>Since &os;&nbsp;5.1-RELEASE, the &man.bsdlabel.8;
 	  utility replaces the old &man.disklabel.8; program.  With
 	  &man.bsdlabel.8; a number of obsolete options and parameters
 	  have been retired; in the examples above the option
 	  <option>-r</option> should be removed with &man.bsdlabel.8;.
 	  For more information, please refer to the &man.bsdlabel.8;
 	  manual page.</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>Original work by </contrib>
 	    </author>
 	  </authorgroup>
 	  <authorgroup>
 	    <author>
 	      <firstname>Jim</firstname>
 	      <surname>Brown</surname>
 	      <contrib>Revised by </contrib>
 	    </author>
 	  </authorgroup>
 	</sect3info>
 
 <indexterm><primary>RAID</primary><secondary>software</secondary></indexterm>
 <indexterm>
   <primary>RAID</primary><secondary>CCD</secondary>
 </indexterm>
 
 	<title>Concatenated Disk Driver (CCD) Configuration</title>
 	<para>When choosing a mass storage solution the most important
 	  factors to consider are speed, reliability, and cost.  It is
 	  rare to have all three in balance; normally a fast, reliable mass
 	  storage device is expensive, and to cut back on cost either speed
 	  or reliability must be sacrificed.</para>
 
           <para>In designing the system described below, cost was chosen
           as  the most important factor, followed by speed, then reliability.
           Data transfer speed for this system is ultimately
           constrained by the network.  And while reliability is very important,
           the CCD drive described below serves online data that is already
           fully backed up on CD-R's and can easily be replaced.</para>
 
           <para>Defining your own requirements is the first step
           in choosing a mass storage solution.  If your requirements prefer
           speed or reliability over cost, your solution will differ from
           the system described in this section.</para>
 
 
 	<sect4 id="ccd-installhw">
 	  <title>Installing the Hardware</title>
 
 	  <para>In addition to the IDE system disk, three Western
             Digital 30GB, 5400 RPM IDE disks form the core
             of the CCD disk described below providing approximately
 	    90GB of online storage.  Ideally,
 	    each IDE disk would have its own IDE controller
 	    and cable, but to minimize cost, additional
 	    IDE controllers were not used.  Instead the disks were
 	    configured with jumpers so that each IDE controller has
             one master, and one slave.</para>
 
 	  <para>Upon reboot, the system BIOS was configured to
 	    automatically detect the disks attached.  More importantly,
 	    FreeBSD detected them on reboot:</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>If FreeBSD does not detect all the disks, ensure
  	    that you have jumpered them correctly.  Most IDE drives
  	    also have a <quote>Cable Select</quote> jumper.  This is
  	    <emphasis>not</emphasis> the jumper for the master/slave
  	    relationship.  Consult the drive documentation for help in
  	    identifying the correct jumper.</para></note>
 
  	  <para>Next, consider how to attach them as part of the file
  	    system.  You should research both &man.vinum.8; (<xref
  	    linkend="vinum-vinum">) and &man.ccd.4;.  In this
  	    particular configuration, &man.ccd.4; was chosen.</para>
 	</sect4>
 
 	<sect4 id="ccd-setup">
 	  <title>Setting Up the CCD</title>
 
  	  <para>The &man.ccd.4; driver allows you to take
   	    several identical disks and concatenate them into one
   	    logical file system.  In order to use
  	    &man.ccd.4;, you need a kernel with
  	    &man.ccd.4; support built in.
  	    Add this line to your kernel configuration file, rebuild, and
  	    reinstall the kernel:</para>
 
 	  <programlisting>pseudo-device   ccd     4</programlisting>
 
 	  <para>On 5.X systems, you have to use instead the following
 	    line:</para>
 
 	  <programlisting>device   ccd</programlisting>
 
 	  <note><para>In FreeBSD&nbsp;5.X, it is not necessary to specify
 	    a number of &man.ccd.4; devices, as the &man.ccd.4; device driver is now
 	    self-cloning &mdash; new device instances will automatically be
 	    created on demand.</para></note>
 
 	  <para>The &man.ccd.4; support can also be
 	    loaded as a kernel loadable module in FreeBSD 3.0 or
 	    later.</para>
 
  	  <para>To set up &man.ccd.4;, you must first use
  	    &man.disklabel.8; to label the disks:</para>
 
 	  <programlisting>disklabel -r -w ad1 auto
 disklabel -r -w ad2 auto
 disklabel -r -w ad3 auto</programlisting>
 
  	  <para>This creates a disklabel for <devicename>ad1c</devicename>, <devicename>ad2c</devicename> and <devicename>ad3c</devicename> that
   	    spans the entire disk.</para>
 
 	  <note><para>Since &os;&nbsp;5.1-RELEASE, the &man.bsdlabel.8;
 	    utility replaces the old &man.disklabel.8; program.  With
 	    &man.bsdlabel.8; a number of obsolete options and parameters
 	    have been retired; in the examples above the option
 	    <option>-r</option> should be removed.  For more
 	    information, please refer to the &man.bsdlabel.8;
 	    manual page.</para></note>
 
  	  <para>The next step is to change the disk label type.  You
  	    can use &man.disklabel.8; to edit the
  	    disks:</para>
 
 	  <programlisting>disklabel -e ad1
 disklabel -e ad2
 disklabel -e ad3</programlisting>
 
  	  <para>This opens up the current disk label on each disk with
  	    the editor specified by the <envar>EDITOR</envar>
  	    environment variable, typically &man.vi.1;.</para>
 
 	  <para>An unmodified disk label will look something like
 	    this:</para>
 
 	  <programlisting>8 partitions:
 #        size   offset    fstype   [fsize bsize bps/cpg]
   c: 60074784        0    unused        0     0     0   # (Cyl.    0 - 59597)</programlisting>
 
  	  <para>Add a new <literal>e</literal> partition for &man.ccd.4; to use. This
  	    can usually be copied from the <literal>c</literal> partition,
  	    but the <option>fstype</option> <emphasis>must</emphasis>
  	    be <userinput>4.2BSD</userinput>.  The disk label should
  	    now look something like this:</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>Building the File System</title>
 
             <para>The device node for
 	    <devicename>ccd0c</devicename> may not exist yet, so to
 	    create it, perform the following commands:</para>
 
 	  <programlisting>cd /dev
 sh MAKEDEV ccd0</programlisting>
 
 	  <note><para>In FreeBSD 5.0, &man.devfs.5; will automatically
 	    manage device nodes in <filename>/dev</filename>, so use of
 	    <command>MAKEDEV</command> is not necessary.</para></note>
 
 	  <para>Now that you have all the disks labeled, you must
 	    build the &man.ccd.4;.  To do that,
 	    use  &man.ccdconfig.8;, with options similar to the following:</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>The use and meaning of each option is shown below:</para>
 
           <calloutlist>
             <callout arearefs="co-ccd-dev">
 	    <para>The first argument is the device to configure, in this case,
 	    <filename>/dev/ccd0c</filename>. The <filename>/dev/</filename>
             portion is optional.</para>
             </callout>
 
             <callout arearefs="co-ccd-interleave">
 
 	    <para>The interleave for the file system.  The interleave
 	    defines the size of a stripe in disk blocks, each normally 512 bytes.
 	    So, an interleave of 32 would be 16,384 bytes.</para>
             </callout>
 
             <callout arearefs="co-ccd-flags">
 	    <para>Flags for &man.ccdconfig.8;.  If you want to enable drive
 	    mirroring, you can specify a flag here. This
 	    configuration does not provide mirroring for
 	    &man.ccd.4;, so it is set at 0 (zero).</para>
             </callout>
 
             <callout arearefs="co-ccd-devs">
 	    <para>The final arguments to &man.ccdconfig.8;
 	    are the devices to place into the array.  Use the complete pathname
 	    for each device.</para>
             </callout>
           </calloutlist>
 
 
 	  <para>After running &man.ccdconfig.8; the &man.ccd.4;
           is configured. A file system can be installed. Refer to &man.newfs.8;
           for options, or simply run: </para>
 
 	  <programlisting>newfs /dev/ccd0c</programlisting>
 
 
 	</sect4>
 
 	<sect4 id="ccd-auto">
 	  <title>Making it All Automatic</title>
 
 	  <para>Generally, you will want to mount the
 	    &man.ccd.4; upon each reboot. To do this, you must
 	    configure it first.  Write out your current configuration to
 	    <filename>/etc/ccd.conf</filename> using the following command:</para>
 
 	  <programlisting>ccdconfig -g &gt; /etc/ccd.conf</programlisting>
 
 	  <para>During reboot, the script <command>/etc/rc</command>
 	    runs <command>ccdconfig -C</command> if <filename>/etc/ccd.conf</filename>
 	    exists. This automatically configures the
 	    &man.ccd.4; so it can be mounted.</para>
 
 	  <note><para>If you are booting into single user mode, before you can
 	    &man.mount.8; the &man.ccd.4;, you
 	    need to issue the following command to configure the
 	    array:</para>
 
 	  <programlisting>ccdconfig -C</programlisting>
           </note>
 
 	  <para>To automatically mount the &man.ccd.4;,
             place an entry for the &man.ccd.4; in
 	    <filename>/etc/fstab</filename> so it will be mounted at
 	    boot time:</para>
 
 	  <programlisting>/dev/ccd0c              /media       ufs     rw      2       2</programlisting>
 	</sect4>
       </sect3>
 
       <sect3 id="vinum">
 	<title>The Vinum Volume Manager</title>
 
 <indexterm><primary>RAID</primary><secondary>software</secondary></indexterm>
 <indexterm>
   <primary>RAID</primary>
   <secondary>Vinum</secondary>
 </indexterm>
 
 	<para>The Vinum Volume Manager is a block device driver which
 	  implements virtual disk drives.  It isolates disk hardware
 	  from the block device interface and maps data in ways which
 	  result in an increase in flexibility, performance and
 	  reliability compared to the traditional slice view of disk
 	  storage.  &man.vinum.8; implements the RAID-0, RAID-1 and
 	  RAID-5 models, both individually and in combination.</para>
 
 	<para>See <xref linkend="vinum-vinum"> for more
 	  information about &man.vinum.8;.</para>
       </sect3>
     </sect2>
 
     <sect2 id="raid-hard">
       <title>Hardware RAID</title>
 
       <indexterm>
 	<primary>RAID</primary>
 	<secondary>hardware</secondary>
       </indexterm>
 
       <para>FreeBSD also supports a variety of hardware <acronym>RAID</acronym>
         controllers.  These devices control a <acronym>RAID</acronym> subsystem
         without the need for FreeBSD specific software to manage the
         array.</para>
 
       <para>Using an on-card <acronym>BIOS</acronym>, the card controls most  of the disk operations
 	itself.  The following is a brief setup description using a Promise <acronym>IDE</acronym> <acronym>RAID</acronym>
 	controller.  When this card is installed and the system is started up, it
 	displays a prompt requesting information.  Follow the instructions
 	to enter the card's setup screen.  From here, you have the ability to
 	combine all the attached drives.  After doing so, the disk(s) will look like
 	a single drive to FreeBSD.  Other <acronym>RAID</acronym> levels can be set up
 	accordingly.
       </para>
     </sect2>
 
     <sect2>
       <title>Rebuilding ATA RAID1 Arrays</title>
 
       <para>FreeBSD allows you to hot-replace a failed disk in an array. This requires
 	that you catch it before you reboot.</para>
 
       <para>You will probably see something like the following in <filename>/var/log/messages</filename> or in the &man.dmesg.8;
 	output:</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>Using &man.atacontrol.8;, check for further information:</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>You will first need to detach the ata channel with the failed
 	    disk so you can safely remove it:</para>
 
 	  <screen>&prompt.root; <userinput>atacontrol detach ata3</userinput></screen>
 	</step>
 
 	<step>
 	  <para>Replace the disk.</para>
 	</step>
 
 	<step>
 	  <para>Reattach the ata channel:</para>
 
 	  <screen>&prompt.root; <userinput>atacontrol attach ata3</userinput>
 Master:  ad6 &lt;MAXTOR 6L080J4/A93.0500&gt; ATA/ATAPI rev 5
 Slave:   no device present</screen>
 	</step>
 
 	<step>
 	  <para>Add the new disk to the array as a spare:</para>
 
 	  <screen>&prompt.root; <userinput>atacontrol addspare ar0 ad6</userinput></screen>
 	</step>
 
 	<step>
 	  <para>Rebuild the array:</para>
 
 	  <screen>&prompt.root; <userinput>atacontrol rebuild ar0</userinput></screen>
 	</step>
 
 	<step>
 	  <para>It is possible to check on the progress by issuing the
 	    following command:</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>Wait until this operation completes.</para>
 	</step>
       </procedure>
     </sect2>
   </sect1>
 
   <sect1 id="usb-disks">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Marc</firstname>
 	  <surname>Fonvieille</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
       <!-- Jul 2004 -->
     </sect1info>
 
     <title>USB Storage Devices</title>
     <indexterm>
       <primary>USB</primary>
       <secondary>disks</secondary>
     </indexterm>
 
     <para>A lot of external storage solutions, nowadays, use the
       Universal Serial Bus (USB): hard drives, USB thumbdrives, CD-R
       burners, etc.  &os; provides support for these devices.</para>
 
     <sect2>
       <title>Configuration</title>
 
       <para>The USB mass storage devices driver, &man.umass.4;,
 	provides the support for USB storage devices.  If you use the
 	<filename>GENERIC</filename> kernel, you do not have to change
 	anything in your configuration.  If you use a custom kernel,
 	be sure that the following lines are present in your kernel
 	configuration file:</para>
 
       <programlisting>device scbus
 device da
 device pass
 device uhci
 device ohci
 device usb
 device umass</programlisting>
 
       <para>The &man.umass.4; driver uses the SCSI subsystem to access
 	to the USB storage devices, your USB device will be seen as a
 	SCSI device by the system.  Depending on the USB chipset on
 	your motherboard, you only need either <literal>device
 	uhci</literal> or <literal>device ohci</literal>, however
 	having both in the kernel configuration file is harmless.  Do
 	not forget to compile and install the new kernel if you added
 	any lines.</para>
 
       <note>
 	<para>If your USB device is a CD-R or DVD burner, the SCSI CD-ROM
 	  driver, &man.cd.4;, must be added to the kernel via the
 	  line:</para>
 
 	<programlisting>device cd</programlisting>
 
 	<para>Since the burner is seen as a SCSI drive, the driver
 	  &man.atapicam.4; should not be used in the kernel
 	  configuration.</para>
       </note>
 
       <para>Support for USB 2.0 controllers is provided on
 	&os;&nbsp;5.X, and on the 4.X branch since &os;&nbsp;4.10-RELEASE.
 	You have to add:</para>
 
       <programlisting>device ehci</programlisting>
 
       <para>to your configuration file for USB 2.0 support.  Note
 	&man.uhci.4; and &man.ohci.4; drivers are still needed if you
 	want USB 1.X support.</para>
 
       <note>
 	<para>On &os;&nbsp;4.X, the USB daemon (&man.usbd.8;) must be
 	  running to be able to see some USB devices.   To enable it,
 	  add <literal>usbd_enable="YES"</literal> to your
 	  <filename>/etc/rc.conf</filename> file and reboot the
 	  machine.</para>
       </note>
     </sect2>
 
     <sect2>
       <title>Testing the Configuration</title>
 
       <para>The configuration is ready to be tested: plug in your USB
 	device, and in the system message buffer (&man.dmesg.8;), the
 	drive should appear as something like:</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>Of course, the brand, the device node
 	(<devicename>da0</devicename>) and other details can differ
 	according to your configuration.</para>
 
       <para>Since the USB device is seen as a SCSI one, the
 	<command>camcontrol</command> command can be used to list the
 	USB storage devices attached to the system:</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>If the drive comes with a file system, you should be able
 	to mount it.  The <xref linkend="disks-adding"> will help you
 	to format and create partitions on the USB drive if
 	needed.</para>
 
       <para>If you unplug the device (the disk must be unmounted
 	before), you should see, in the system message buffer,
 	something like the following:</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>Further Reading</title>
 
       <para>Beside the <link linkend="disks-adding">Adding
 	Disks</link> and <link linkend="mount-unmount">Mounting and
 	Unmounting File Systems</link> sections, reading various
 	manual pages may be also useful: &man.umass.4;,
 	&man.camcontrol.8;, and &man.usbdevs.8;.</para>
     </sect2>
   </sect1>
 
   <sect1 id="creating-cds">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Mike</firstname>
 	  <surname>Meyer</surname>
 	  <contrib>Contributed by </contrib>
 	  <!-- mwm@mired.org -->
 	</author>
       </authorgroup>
       <!-- Apr 2001 -->
     </sect1info>
 
     <title>Creating and Using Optical Media (CDs)</title>
     <indexterm>
       <primary>CDROMs</primary>
       <secondary>creating</secondary>
     </indexterm>
 
     <sect2>
       <title>Introduction</title>
 
       <para>CDs have a number of features that differentiate them from
 	conventional disks. Initially, they were not writable by the
 	user. They are designed so that they can be read continuously without
 	delays to move the head between tracks. They are also much easier
 	to transport between systems than similarly sized media were at the
 	time.</para>
 
       <para>CDs do have tracks, but this refers to a section of data to
 	be read continuously and not a physical property of the disk. To
 	produce a CD on FreeBSD, you prepare the data files that are going
 	to make up the tracks on the CD, then write the tracks to the
 	CD.</para>
 
       <indexterm><primary>ISO 9660</primary></indexterm>
       <indexterm>
         <primary>file systems</primary>
         <secondary>ISO 9660</secondary>
       </indexterm>
       <para>The ISO 9660 file system was designed to deal with these
 	differences. It unfortunately codifies file system limits that were
 	common then. Fortunately, it provides an extension mechanism that
 	allows properly written CDs to exceed those limits while still
 	working with systems that do not support those extensions.</para>
 
       <indexterm>
         <primary><filename role="package">sysutils/cdrtools</filename></primary>
       </indexterm>
       <para>The <filename role="package">sysutils/cdrtools</filename>
 	port includes &man.mkisofs.8;, a program that you can use to
 	produce a data file containing an ISO 9660 file
 	system. It has options that support various extensions, and is
 	described below.</para>
 
       <indexterm>
         <primary>CD burner</primary>
         <secondary>ATAPI</secondary>
       </indexterm>
       <para>Which tool to use to burn the CD depends on whether your CD burner
 	is ATAPI or something else. ATAPI CD burners use the <command><link
 	linkend="burncd">burncd</link></command> program that is part of
 	the base system. SCSI and USB CD burners should use
 	<command><link linkend="cdrecord">cdrecord</link></command> from
 	the <filename role="package">sysutils/cdrtools</filename> port.</para>
 
       <para><command>burncd</command> has a limited number of
 	supported drives. To find out if a drive is supported, see the
 	<ulink url="http://www.freebsd.dk/ata/">CD-R/RW supported
 	  drives</ulink> list.</para>
 
       <note>
       <indexterm>
 	<primary>CD burner</primary>
 	<secondary>ATAPI/CAM driver</secondary>
       </indexterm>
 	<para>If you run &os;&nbsp;5.X, &os;&nbsp;4.8-RELEASE version or
 	  higher, it will be possible to use <command><link
 	  linkend="cdrecord">cdrecord</link></command> and other tools
 	  for SCSI drives on an ATAPI hardware with the <link
 	  linkend="atapicam">ATAPI/CAM module</link>.</para>
       </note>
 
       <para>If you want a CD burning software with a graphical user
 	interface, you should have a look to
 	<application>X-CD-Roast</application> or
 	<application>K3b</application>.  These tools are available as
 	packages or from the <filename
 	role="package">sysutils/xcdroast</filename> and <filename
 	role="package">sysutils/k3b</filename> ports.
 	<application>X-CD-Roast</application> and
 	<application>K3b</application> require the <link
 	linkend="atapicam">ATAPI/CAM module</link> with ATAPI
 	hardware.</para>
     </sect2>
 
     <sect2 id="mkisofs">
       <title>mkisofs</title>
 
       <para>The &man.mkisofs.8; program, which is part of the
 	<filename role="package">sysutils/cdrtools</filename> port,
         produces an ISO 9660 file system
 	that is an image of a directory tree in the &unix; file system name
 	space. The simplest usage is:</para>
 
       <screen>&prompt.root; <userinput>mkisofs -o <replaceable>imagefile.iso</replaceable> <replaceable>/path/to/tree</replaceable></userinput></screen>
 
       <indexterm>
         <primary>file systems</primary>
         <secondary>ISO 9660</secondary>
       </indexterm>
       <para>This command will create an <replaceable>imagefile.iso</replaceable>
 	containing an ISO 9660 file system that is a copy of the tree at
 	<replaceable>/path/to/tree</replaceable>. In the process, it will
 	map the file names to names that fit the limitations of the
 	standard ISO 9660 file system, and will exclude files that have
 	names uncharacteristic of ISO file systems.</para>
 
       <indexterm>
         <primary>file systems</primary>
         <secondary>HFS</secondary>
       </indexterm>
       <indexterm>
         <primary>file systems</primary>
         <secondary>Joliet</secondary>
       </indexterm>
       <para>A number of options are available to overcome those
 	restrictions. In particular, <option>-R</option> enables the
 	Rock Ridge extensions common to &unix; systems, <option>-J</option>
 	enables Joliet extensions used by Microsoft systems, and
 	<option>-hfs</option> can be used to create HFS file systems used
 	by &macos;.</para>
 
       <para>For CDs that are going to be used only on FreeBSD systems,
 	<option>-U</option> can be used to disable all filename
 	restrictions. When used with <option>-R</option>, it produces a
 	file system image that is identical to the FreeBSD tree you started
 	from, though it may violate the ISO 9660 standard in a number of
 	ways.</para>
 
       <indexterm>
         <primary>CDROMs</primary>
         <secondary>creating bootable</secondary>
       </indexterm>
       <para>The last option of general use is <option>-b</option>. This is
 	used to specify the location of the boot image for use in producing an
 	<quote>El Torito</quote> bootable CD. This option takes an
 	argument which is the path to a boot image from the top of the
 	tree being written to the CD. By default, &man.mkisofs.8; creates an
 	ISO image in the so-called <quote>floppy disk emulation</quote> mode,
 	and thus expects the boot image to be exactly 1200, 1440 or
 	2880&nbsp;KB in size. Some boot loaders, like the one used by the
 	FreeBSD distribution disks, do not use emulation mode; in this case,
 	the <option>-no-emul-boot</option> option should be used. So, if
 	<filename>/tmp/myboot</filename> holds a bootable FreeBSD system
 	with the boot image in
 	<filename>/tmp/myboot/boot/cdboot</filename>, you could produce the
 	image of an ISO 9660 file system in
 	<filename>/tmp/bootable.iso</filename> like so:</para>
 
       <screen>&prompt.root; <userinput>mkisofs -R -no-emul-boot -b boot/cdboot -o /tmp/bootable.iso /tmp/myboot</userinput></screen>
 
       <para>Having done that, if you have <devicename>vn</devicename>
 	(FreeBSD&nbsp;4.X), or <devicename>md</devicename>
 	(FreeBSD&nbsp;5.X)
 	configured in your kernel, you can mount the file system with:</para>
 
       <screen>&prompt.root; <userinput>vnconfig -e vn0c /tmp/bootable.iso</userinput>
 &prompt.root; <userinput>mount -t cd9660 /dev/vn0c /mnt</userinput></screen>
 
       <para>for FreeBSD&nbsp;4.X, and for 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>At which point you can verify that <filename>/mnt</filename>
 	and <filename>/tmp/myboot</filename> are identical.</para>
 
       <para>There are many other options you can use with
 	&man.mkisofs.8; to fine-tune its behavior.  In particular:
 	modifications to an ISO 9660 layout and the creation of Joliet
 	and HFS discs.  See the	&man.mkisofs.8; manual page for details.</para>
     </sect2>
 
     <sect2 id="burncd">
       <title>burncd</title>
       <indexterm>
         <primary>CDROMs</primary>
         <secondary>burning</secondary>
       </indexterm>
       <para>If you have an ATAPI CD burner, you can use the
 	<command>burncd</command> command to burn an ISO image onto a
 	CD. <command>burncd</command> is part of the base system, installed
 	as <filename>/usr/sbin/burncd</filename>.  Usage is very simple, as
 	it has few options:</para>
 
       <screen>&prompt.root; <userinput>burncd -f <replaceable>cddevice</replaceable> data <replaceable>imagefile.iso</replaceable> fixate</userinput></screen>
 
       <para>Will burn a copy of <replaceable>imagefile.iso</replaceable> on
 	<replaceable>cddevice</replaceable>. The default device is
 	<filename>/dev/acd0</filename> (or <filename>/dev/acd0c</filename> under &os;&nbsp;4.X). See &man.burncd.8; for options to
 	set the write speed, eject the CD after burning, and write audio
 	data.</para>
     </sect2>
 
     <sect2 id="cdrecord">
       <title>cdrecord</title>
 
       <para>If you do not have an ATAPI CD burner, you will have to use
 	<command>cdrecord</command> to burn your
 	CDs. <command>cdrecord</command> is not part of the base system;
 	you must install it from either the port at <filename role="package">sysutils/cdrtools</filename>
 	or the appropriate
 	package. Changes to the base system can cause binary versions of
 	this program to fail, possibly resulting in a
 	<quote>coaster</quote>. You should therefore either upgrade the
 	port when you upgrade your system, or if you are <link
 	linkend="stable">tracking -STABLE</link>, upgrade the port when a
 	new version becomes available.</para>
 
       <para>While <command>cdrecord</command> has many options, basic usage
 	is even simpler than <command>burncd</command>. Burning an ISO 9660
 	image is done with:</para>
 
       <screen>&prompt.root; <userinput>cdrecord dev=<replaceable>device</replaceable> <replaceable>imagefile.iso</replaceable></userinput></screen>
 
       <para>The tricky part of using <command>cdrecord</command> is finding
 	the <option>dev</option> to use. To find the proper setting, use
 	the <option>-scanbus</option> flag of <command>cdrecord</command>,
 	which might produce results like this:</para>
       <indexterm>
         <primary>CDROMs</primary>
         <secondary>burning</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>This lists the appropriate <option>dev</option> value for the
 	devices on the list. Locate your CD burner, and use the three
 	numbers separated by commas as the value for
 	<option>dev</option>. In this case, the CRW device is 1,5,0, so the
 	appropriate input would be
 	<option>dev=1,5,0</option>. There are easier
 	ways to specify this value; see &man.cdrecord.1; for
 	details. That is also the place to look for information on writing
 	audio tracks, controlling the speed, and other things.</para>
     </sect2>
 
     <sect2 id="duplicating-audiocds">
       <title>Duplicating Audio CDs</title>
 
       <para>You can duplicate an audio CD by extracting the audio data from
 	the CD to a series of files, and then writing these files to a blank
 	CD.  The process is slightly different for ATAPI and SCSI
 	drives.</para>
 
       <procedure>
 	<title>SCSI Drives</title>
 
 	<step>
 	  <para>Use <command>cdda2wav</command> to extract the audio.</para>
 
 	  <screen>&prompt.user; <userinput>cdda2wav -v255 -D2,0 -B -Owav</userinput></screen>
 	</step>
 
 	<step>
 	  <para>Use <command>cdrecord</command> to write the
 	    <filename>.wav</filename> files.</para>
 
 	  <screen>&prompt.user; <userinput>cdrecord -v dev=<replaceable>2,0</replaceable> -dao -useinfo  *.wav</userinput></screen>
 
 	  <para>Make sure that <replaceable>2,0</replaceable> is set
 	    appropriately, as described in <xref linkend="cdrecord">.</para>
 	</step>
       </procedure>
 
       <procedure>
 	<title>ATAPI Drives</title>
 
 	<step>
 	  <para>The ATAPI CD driver makes each track available as
 	    <filename>/dev/acd<replaceable>d</replaceable>t<replaceable>nn</replaceable></filename>,
 	    where <replaceable>d</replaceable> is the drive number, and
 	    <replaceable>nn</replaceable> is the track number written with two
 	    decimal digits, prefixed with zero as needed.
 	    So the first track on the first disk is
 	    <filename>/dev/acd0t01</filename>, the second is
 	    <filename>/dev/acd0t02</filename>, the third is
 	    <filename>/dev/acd0t03</filename>, and so on.</para>
 
 	  <para>Make sure the appropriate files exist in
-	    <filename>/dev</filename>.</para>
+	    <filename>/dev</filename>.  If the entries are missing,
+	    force the system to retaste the media:</para>
+
+	  <screen>&prompt.root; <userinput>dd if=/dev/acd0 of=/dev/null count=1</userinput></screen>
+
+	  <note><para>In &os; 4.X, the entries are not prefixed with
+	    zero.  If the necessary entries in <filename>/dev</filename>
+	    are missing, use <command>MAKEDEV</command> to create
+	    them:</para>
 
 	  <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>sh MAKEDEV acd0t99</userinput></screen>
+	  </note>
 
-	  <note><para>In FreeBSD 5.0, &man.devfs.5; will automatically
-	    create and manage entries in <filename>/dev</filename>
-	    for you, so it is not necessary to use
-	    <command>MAKEDEV</command>.</para></note>
 	</step>
 
 	<step>
 	  <para>Extract each track using &man.dd.1;.  You must also use a
 	    specific block size when extracting the files.</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>Burn the extracted files to disk using
 	    <command>burncd</command>.  You must specify that these are audio
 	    files, and that <command>burncd</command> should fixate the disk
 	    when finished.</para>
 
 	  <screen>&prompt.root; <userinput>burncd -f <replaceable>/dev/acd0</replaceable> audio track1.cdr track2.cdr <replaceable>...</replaceable> fixate</userinput></screen>
 	</step>
       </procedure>
     </sect2>
 
     <sect2 id="imaging-cd">
       <title>Duplicating Data CDs</title>
 
       <para>You can copy a data CD to a image file that is
 	functionally equivalent to the image file created with
         &man.mkisofs.8;, and you can use it to duplicate
 	any data CD.  The example given here assumes that your CDROM
 	device is <devicename>acd0</devicename>.  Substitute your
 	correct CDROM device.  Under &os;&nbsp;4.X, a <literal>c</literal> must be appended
 	to the end of the device name to indicate the entire partition
 	or, in the case of CDROMs, the entire disc.</para>
 
       <screen>&prompt.root; <userinput>dd if=/dev/acd0 of=file.iso bs=2048</userinput></screen>
 
       <para>Now that you have an image, you can burn it to CD as
 	described above.</para>
     </sect2>
 
     <sect2 id="mounting-cd">
       <title>Using Data CDs</title>
 
       <para>Now that you have created a standard data CDROM, you
 	probably want to mount it and read the data on it.  By
 	default, &man.mount.8; assumes that a file system is of type
 	<literal>ufs</literal>.  If you try something like:</para>
 
       <screen>&prompt.root; <userinput>mount /dev/cd0 /mnt</userinput></screen>
 
       <para>you will get a complaint about <errorname>Incorrect super
 	  block</errorname>, and no mount. The CDROM is not a
 	  <literal>UFS</literal> file system, so attempts to mount it
 	  as such will fail.  You just need to tell &man.mount.8; that
 	  the file system is of type <literal>ISO9660</literal>, and
 	  everything will work.  You do this by specifying the
 	  <option>-t cd9660</option> option &man.mount.8;. For
 	  example, if you want to mount the CDROM device,
 	  <filename>/dev/cd0</filename>, under
 	  <filename>/mnt</filename>, you would execute:</para>
 
           <screen>&prompt.root; <userinput>mount -t cd9660 /dev/cd0 /mnt</userinput></screen>
 
       <para>Note that your device name
 	(<filename>/dev/cd0</filename> in this example) could be
 	different, depending on the interface your CDROM uses. Also,
 	the <option>-t cd9660</option> option just executes
 	&man.mount.cd9660.8;. The above example could be shortened
 	to:</para>
 
 <screen>&prompt.root; <userinput>mount_cd9660 /dev/cd0 /mnt</userinput></screen>
 
       <para>You can generally use data CDROMs from any vendor in this
 	way.  Disks with certain ISO 9660 extensions might behave
 	oddly, however.  For example, Joliet disks store all filenames
 	in two-byte Unicode characters.  The FreeBSD kernel does not
 	speak Unicode (yet!), so non-English characters show up as
 	question marks.  (If you are running FreeBSD 4.3 or later, the
 	CD9660 driver includes hooks to load an appropriate Unicode
 	conversion table on the fly.  Modules for some of the common
 	encodings are available via the
 	<filename role="package">sysutils/cd9660_unicode</filename> port.)</para>
 
       <para>Occasionally, you might get <errorname>Device not
 	configured</errorname> when trying to mount a CDROM.  This
 	usually means that the CDROM drive thinks that there is no
 	disk in the tray, or that the drive is not visible on the bus.
 	It can take a couple of seconds for a CDROM drive to realize
 	that it has been fed, so be patient.</para>
 
       <para>Sometimes, a SCSI CDROM may be missed because it did not
 	have enough time to answer the bus reset.  If you have a SCSI
 	CDROM please add the following option to your kernel
 	configuration and <link linkend="kernelconfig-building">rebuild your kernel</link>.</para>
 
       <programlisting>options SCSI_DELAY=15000</programlisting>
 
       <para>This tells your SCSI bus to pause 15 seconds during boot,
 	to give your CDROM drive every possible chance to answer the
 	bus reset.</para>
     </sect2>
 
     <sect2 id="rawdata-cd">
       <title>Burning Raw Data CDs</title>
 
       <para>You can choose to burn a file directly to CD, without
 	creating an ISO 9660 file system.  Some people do this for
 	backup purposes.  This runs more quickly than burning a
 	standard CD:</para>
 
       <screen>&prompt.root; <userinput>burncd -f /dev/acd1 -s 12 data archive.tar.gz fixate</userinput></screen>
 
       <para>In order to retrieve the data burned to such a CD, you
 	  must read data from the raw device node:</para>
 
       <screen>&prompt.root; <userinput>tar xzvf /dev/acd1</userinput></screen>
 
       <para>You cannot mount this disk as you would a normal CDROM.
 	  Such a CDROM cannot be read under any operating system
 	  except FreeBSD.  If you want to be able to mount the CD, or
 	  share data with another operating system, you must use
 	  &man.mkisofs.8; as described above.</para>
     </sect2>
 
     <sect2 id="atapicam">
       <sect2info>
 	<authorgroup>
 	  <author>
 	    <firstname>Marc</firstname>
 	    <surname>Fonvieille</surname>
 	    <contrib>Contributed by </contrib>
 	  </author>
 	</authorgroup>
       </sect2info>
 
       <indexterm>
 	<primary>CD burner</primary>
 	<secondary>ATAPI/CAM driver</secondary>
       </indexterm>
       <title>Using the ATAPI/CAM Driver</title>
 
       <para>This driver allows ATAPI devices (CD-ROM, CD-RW, DVD
 	drives etc...) to be accessed through the SCSI subsystem, and
 	so allows the use of applications like <filename
 	role="package">sysutils/cdrdao</filename> or
 	&man.cdrecord.1;.</para>
 
       <para>To use this driver, you will need to add the following
 	line to your kernel configuration file:</para>
 
       <programlisting>device atapicam</programlisting>
 
       <para>You also need the following lines in your kernel
 	configuration file:</para>
 
       <programlisting>device ata
 device scbus
 device cd
 device pass</programlisting>
 
       <para>which should already be present.</para>
 
       <para>Then rebuild, install your new kernel, and reboot your
 	machine.  During the boot process, your burner should show up,
 	like so:</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>The drive could now be accessed via the
 	<filename>/dev/cd0</filename> device name, for example to
 	mount a CD-ROM on <filename>/mnt</filename>, just type the
 	following:</para>
 
       <screen>&prompt.root; <userinput>mount -t cd9660 <replaceable>/dev/cd0</replaceable> /mnt</userinput></screen>
 
       <para>As <username>root</username>, you can run the following
 	command to get the SCSI address of the burner:</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>So <literal>1,0,0</literal> will be the SCSI address to
 	use with &man.cdrecord.1; and other SCSI application.</para>
 
       <para>For more information about ATAPI/CAM and SCSI system,
 	refer to the &man.atapicam.4; and &man.cam.4; manual
 	pages.</para>
     </sect2>
   </sect1>
 
   <sect1 id="creating-dvds">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Marc</firstname>
 	  <surname>Fonvieille</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
       <authorgroup>
 	<author>
 	  <firstname>Andy</firstname>
 	  <surname>Polyakov</surname>
 	  <contrib>With inputs from </contrib>
 	</author>
       </authorgroup>
       <!-- Feb 2004 -->
     </sect1info>
 
     <title>Creating and Using Optical Media (DVDs)</title>
     <indexterm>
       <primary>DVD</primary>
       <secondary>burning</secondary>
     </indexterm>
 
     <sect2>
       <title>Introduction</title>
 
       <para>Compared to the CD, the DVD is the next generation of
 	optical media storage technology.  The DVD can hold more data
 	than any CD and is nowadays the standard for video
 	publishing.</para>
 
       <para>Five physical recordable formats can be defined for what
 	we will call a recordable DVD:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>DVD-R: This was the first DVD recordable format
 	    available.  The DVD-R standard is defined by the <ulink
 	    url="http://www.dvdforum.com/forum.shtml">DVD Forum</ulink>.
 	    This format is write once.</para>
 	</listitem>
 
 	<listitem>
 	  <para>DVD-RW: This is the rewriteable version of
 	    the DVD-R standard.  A DVD-RW can be rewritten about 1000
 	    times.</para>
 	</listitem>
 
 	<listitem>
 	  <para>DVD-RAM: This is also a rewriteable format
 	    supported by the DVD Forum.  A DVD-RAM can be seen as a
 	    removable hard drive.  However, this media is not
 	    compatible with most DVD-ROM drives and DVD-Video players;
 	    only a few DVD writers support the DVD-RAM format.</para>
 	</listitem>
 
 	<listitem>
 	  <para>DVD+RW: This is a rewriteable format defined by
 	    the <ulink url="http://www.dvdrw.com/">DVD+RW
 	    Alliance</ulink>.  A DVD+RW can be rewritten about 1000
 	    times.</para>
 	</listitem>
 
 	<listitem>
 	  <para>DVD+R: This format is the write once variation
 	    of the DVD+RW format.</para>
 	</listitem>
       </itemizedlist>
 
       <para>A single layer recordable DVD can hold up to
 	4,700,000,000&nbsp;bytes which is actually 4.38&nbsp;GB or
 	4485&nbsp;MB (1 kilobyte is 1024 bytes).</para>
 
       <note>
 	<para>A distinction must be made between the physical media and
 	  the application.   For example, a DVD-Video is a specific
 	  file layout that can be written on any recordable DVD
 	  physical media: DVD-R, DVD+R, DVD-RW etc.  Before choosing
 	  the type of media, you must be sure that both the burner and the
 	  DVD-Video player (a standalone player or a DVD-ROM drive on
 	  a computer) are compatible with the media under consideration.</para></note>
     </sect2>
 
     <sect2>
       <title>Configuration</title>
 
       <para>The program &man.growisofs.1; will be used to perform DVD
 	recording.  This command is part of the
 	<application>dvd+rw-tools</application> utilities (<filename
 	role="package">sysutils/dvd+rw-tools</filename>).  The
 	<application>dvd+rw-tools</application> support all DVD media
 	types.</para>
 
       <para>These tools use the SCSI subsystem to access to the
 	devices, therefore the <link linkend="atapicam">ATAPI/CAM
 	support</link> must be added to your kernel.  If your burner
 	uses the USB interface this addition is useless, and you should
 	read the <xref linkend="usb-disks"> for more details on USB
 	devices configuration.</para>
 
       <para>You also have to enable DMA access for ATAPI devices, this
 	can be done in adding the following line to the
 	<filename>/boot/loader.conf</filename> file:</para>
 
       <programlisting>hw.ata.atapi_dma="1"</programlisting>
 
       <para>Before attempting to use the
 	<application>dvd+rw-tools</application> you should consult the
 	<ulink
 	url="http://fy.chalmers.se/~appro/linux/DVD+RW/hcn.html">dvd+rw-tools'
 	hardware compatibility notes</ulink> for any information
 	related to your DVD burner.</para>
 
       <note>
 	<para>If you want a graphical user interface, you should have
 	  a look to <application>K3b</application> (<filename
 	  role="package">sysutils/k3b</filename>) which provides a
 	  user friendly interface to &man.growisofs.1; and many others
 	  burning tools.</para>
       </note>
     </sect2>
 
     <sect2>
       <title>Burning Data DVDs</title>
 
       <para>The &man.growisofs.1; command is a frontend to <link
 	linkend="mkisofs">mkisofs</link>, it will invoke
 	&man.mkisofs.8; to create the file system layout and will
 	perform the write on the DVD.  This means you do not need to
 	create an image of the data before the burning process.</para>
 
       <para>To burn onto a DVD+R or a DVD-R the data from the <filename
 	class="directory">/path/to/data</filename> directory, use the
 	following command:</para>
 
       <screen>&prompt.root; <userinput>growisofs -dvd-compat -Z <replaceable>/dev/cd0</replaceable> -J -R <replaceable>/path/to/data</replaceable></userinput></screen>
 
       <para>The options <option>-J -R</option> are passed to
 	&man.mkisofs.8; for the file system creation (in this case: an
 	ISO 9660 file system with Joliet and Rock Ridge extensions),
 	consult the &man.mkisofs.8; manual page for more
 	details.</para>
 
       <para>The option <option>-Z</option> is used for the initial
 	session recording in any case: multiple sessions or not.  The
 	DVD device, <replaceable>/dev/cd0</replaceable>, must be
 	changed according to your configuration.  The
 	<option>-dvd-compat</option> parameter will close the disk,
 	the recording will be unappendable.  In return this should provide better
 	media compatibility with DVD-ROM drives.</para>
 
       <para>It is also possible to burn a pre-mastered image, for
 	example to burn the image
 	<replaceable>imagefile.iso</replaceable>, we will run:</para>
 
       <screen>&prompt.root; <userinput>growisofs -dvd-compat -Z <replaceable>/dev/cd0</replaceable>=<replaceable>imagefile.iso</replaceable></userinput></screen>
 
       <para>The write speed should be detected and automatically set
 	according to the media and the drive being used.  If you want
 	to force the write speed, use the <option>-speed=</option>
 	parameter.  For more information, read the &man.growisofs.1;
 	manual page.</para>
     </sect2>
 
     <indexterm>
       <primary>DVD</primary>
       <secondary>DVD-Video</secondary>
     </indexterm>
 
     <sect2>
       <title>Burning a DVD-Video</title>
 
       <para>A DVD-Video is a specific file layout based on ISO 9660
 	and the micro-UDF (M-UDF) specifications.  The DVD-Video also
 	presents a specific data structure hierarchy, it is the reason
 	why you need a particular program such as <filename
 	role="package">multimedia/dvdauthor</filename> to author the
 	DVD.</para>
 
       <para>If you already have an image of the DVD-Video file system,
 	just burn it in the same way as for any image, see the
 	previous section for an example.  If you have made the DVD
 	authoring and the result is in, for example, the directory
 	<filename class="directory">/path/to/video</filename>, the
 	following command should be used to burn the DVD-Video:</para>
 
       <screen>&prompt.root; <userinput>growisofs -Z <replaceable>/dev/cd0</replaceable> -dvd-video <replaceable>/path/to/video</replaceable></userinput></screen>
 
       <para>The <option>-dvd-video</option> option will be passed down to
 	&man.mkisofs.8; and will instruct it to create a DVD-Video file system
 	layout.  Beside this, the <option>-dvd-video</option> option
 	implies <option>-dvd-compat</option> &man.growisofs.1;
 	option.</para>
     </sect2>
 
     <indexterm>
       <primary>DVD</primary>
       <secondary>DVD+RW</secondary>
     </indexterm>
 
     <sect2>
       <title>Using a DVD+RW</title>
 
       <para>Unlike CD-RW, a virgin DVD+RW needs to be formatted before
 	first use.  The &man.growisofs.1; program will take care of it
 	automatically whenever appropriate, which is the
 	<emphasis>recommended</emphasis> way.  However you can use the
 	<command>dvd+rw-format</command> command to format the
 	DVD+RW:</para>
 
       <screen>&prompt.root; <userinput>dvd+rw-format <replaceable>/dev/cd0</replaceable></userinput></screen>
 
       <para>You need to perform this operation just once, keep in mind
 	that only virgin DVD+RW medias need to be formatted.  Then you
 	can burn the DVD+RW in the way seen in previous
 	sections.</para>
 
       <para>If you want to burn new data (burn a totally new file
 	system not append some data) onto a DVD+RW, you do not need to
 	blank it, you just have to write over the previous recording
 	(in performing a new initial session), like this:</para>
 
       <screen>&prompt.root; <userinput>growisofs -Z <replaceable>/dev/cd0</replaceable> -J -R <replaceable>/path/to/newdata</replaceable></userinput></screen>
 
       <para>DVD+RW format offers the possibility to easily append data
 	to a previous recording.  The operation consists in merging a
 	new session to the existing one, it is not multisession
 	writing, &man.growisofs.1; will <emphasis>grow</emphasis> the
 	ISO 9660 file system present on the media.</para>
 
       <para>For example, if we want to append data to our previous
 	DVD+RW, we have to use the following:</para>
 
       <screen>&prompt.root; <userinput>growisofs -M <replaceable>/dev/cd0</replaceable> -J -R <replaceable>/path/to/nextdata</replaceable></userinput></screen>
 
       <para>The same &man.mkisofs.8; options we used to burn the
 	initial session should be used during next writes.</para>
 
       <note>
 	<para>You may want to use the <option>-dvd-compat</option>
 	  option if you want better media compatibility with DVD-ROM
 	  drives.  In the DVD+RW case, this will not prevent you from
 	  adding data.</para>
       </note>
 
       <para>If for any reason you really want to blank the media, do
 	the following:</para>
 
       <screen>&prompt.root; <userinput>growisofs -Z <replaceable>/dev/cd0</replaceable>=<replaceable>/dev/zero</replaceable></userinput></screen>
     </sect2>
 
     <indexterm>
       <primary>DVD</primary>
       <secondary>DVD-RW</secondary>
     </indexterm>
 
     <sect2>
       <title>Using a DVD-RW</title>
 
       <para>A DVD-RW accepts two disc formats: the incremental
 	sequential one and the restricted overwrite.  By default
 	DVD-RW discs are in sequential format.</para>
 
       <para>A virgin DVD-RW can be directly written without the need
 	of a formatting operation, however a non-virgin DVD-RW in
 	sequential format needs to be blanked before to be able to
 	write a new initial session.</para>
 
       <para>To blank a DVD-RW in sequential mode, run:</para>
 
       <screen>&prompt.root; <userinput>dvd+rw-format -blank=full <replaceable>/dev/cd0</replaceable></userinput></screen>
 
       <note>
 	<para>A full blanking (<option>-blank=full</option>) will take
 	  about one hour on a 1x media.  A fast blanking can be
 	  performed using the <option>-blank</option> option if the
 	  DVD-RW will be recorded in Disk-At-Once (DAO) mode.  To burn
 	  the DVD-RW in DAO mode, use the command:</para>
 
 	<screen>&prompt.root; <userinput>growisofs -use-the-force-luke=dao -Z <replaceable>/dev/cd0</replaceable>=<replaceable>imagefile.iso</replaceable></userinput></screen>
 
 	<para>The <option>-use-the-force-luke=dao</option> option
 	  should not be required since &man.growisofs.1; attempts to
 	  detect minimally (fast blanked) media and engage DAO
 	  write.</para>
 
 	<para>In fact one should use restricted overwrite mode with
 	  any DVD-RW, this format is more flexible than the default
 	  incremental sequential one.</para>
       </note>
 
       <para>To write data on a sequential DVD-RW, use the same
 	instructions as for the other DVD formats:</para>
 
       <screen>&prompt.root; <userinput>growisofs -Z <replaceable>/dev/cd0</replaceable> -J -R <replaceable>/path/to/data</replaceable></userinput></screen>
 
       <para>If you want to append some data to your previous
 	recording, you will have to use the &man.growisofs.1;
 	<option>-M</option> option.  However, if you perform data
 	addition on a DVD-RW in incremental sequential mode, a new
 	session will be created on the disc and the result will be a
 	multi-session disc.</para>
 
       <para>A DVD-RW in restricted overwrite format does not need to
 	be blanked before a new initial session, you just have to
 	overwrite the disc with the <option>-Z</option> option, this
 	is similar to the DVD+RW case.  It is also possible to grow an
 	existing ISO 9660 file system written on the disc in a same
 	way as for a DVD+RW with the <option>-M</option> option.  The
 	result will be a one-session DVD.</para>
 
       <para>To put a DVD-RW in the restricted overwrite format, the
 	following command must be used:</para>
 
       <screen>&prompt.root; <userinput>dvd+rw-format <replaceable>/dev/cd0</replaceable></userinput></screen>
 
       <para>To change back to the sequential format use:</para>
 
       <screen>&prompt.root; <userinput>dvd+rw-format -blank=full <replaceable>/dev/cd0</replaceable></userinput></screen>
     </sect2>
 
     <sect2>
       <title>Multisession</title>
 
       <para>Very few DVD-ROM drives support
 	multisession DVDs, they will most of time, hopefully, only read
 	the first session.  DVD+R, DVD-R and DVD-RW in sequential
 	format can accept multiple sessions, the notion of multiple
 	sessions does not exist for the DVD+RW and the DVD-RW
 	restricted overwrite formats.</para>
 
       <para>Using the following command after an initial (non-closed)
 	session on a DVD+R, DVD-R, or DVD-RW in sequential format,
 	will add a new session to the disc:</para>
 
       <screen>&prompt.root; <userinput>growisofs -M <replaceable>/dev/cd0</replaceable> -J -R <replaceable>/path/to/nextdata</replaceable></userinput></screen>
 
       <para>Using this command line with a DVD+RW or a DVD-RW in restricted
 	overwrite mode, will append data in merging the new session to
 	the existing one.  The result will be a single-session disc.
 	This is the way used to add data after an initial write on these
 	medias.</para>
 
       <note>
 	<para>Some space on the media is used between each session for
 	  end and start of sessions.  Therefore, one should add
 	  sessions with large amount of data to optimize media space.
 	  The number of sessions is limited to 154 for a DVD+R,
 	  about 2000 for a DVD-R, and 127 for a DVD+R Double
 	  Layer.</para>
       </note>
     </sect2>
 
     <sect2>
       <title>For More Information</title>
 
       <para>To obtain more information about a DVD, the
 	<command>dvd+rw-mediainfo
 	<replaceable>/dev/cd0</replaceable></command> command can be
 	ran with the disc in the drive.</para>
 
       <para>More information about the
 	<application>dvd+rw-tools</application> can be found in
 	the &man.growisofs.1; manual page, on the <ulink
 	url="http://fy.chalmers.se/~appro/linux/DVD+RW/">dvd+rw-tools
 	web site</ulink> and in the <ulink
 	url="http://lists.debian.org/cdwrite/">cdwrite mailing
 	list</ulink> archives.</para>
 
       <note>
 	<para>The <command>dvd+rw-mediainfo</command> output of the
 	  resulting recording or the media with issues is mandatory
 	  for any problem report.  Without this output, it will be
 	  quite impossible to help you.</para>
       </note>
     </sect2>
   </sect1>
 
   <sect1 id="floppies">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Julio</firstname>
 	  <surname>Merino</surname>
 	  <contrib>Original work by </contrib>
 	</author>
       </authorgroup>
       <!-- 24 Dec 2001 -->
       <authorgroup>
 	<author>
 	  <firstname>Martin</firstname>
 	  <surname>Karlsson</surname>
 	  <contrib>Rewritten by </contrib>
 	</author>
       </authorgroup>
       <!-- 27 Apr 2003 -->
     </sect1info>
 
     <title>Creating and Using Floppy Disks</title>
 
     <para>Storing data on floppy disks is sometimes useful, for
       example when one does not have any other removable storage media
       or when one needs to transfer small amounts of data to another
       computer.</para>
 
     <para>This section will explain how to use floppy disks in
       FreeBSD.  It will primarily cover formatting and usage of
       3.5inch DOS floppies, but the concepts are similar for other
       floppy disk formats.</para>
 
     <sect2>
       <title>Formatting Floppies</title>
 
       <sect3>
 	<title>The Device</title>
 
 	<para>Floppy disks are accessed through entries in
 	  <filename>/dev</filename>, just like other devices.  To
 	  access the raw floppy disk in 4.X and earlier releases, one
 	  uses
 	  <filename>/dev/fd<replaceable>N</replaceable></filename>,
 	  where <replaceable>N</replaceable> stands for the drive
 	  number, usually 0, or
 	  <filename>/dev/fd<replaceable>NX</replaceable></filename>,
 	  where <replaceable>X</replaceable> stands for a
 	  letter.</para>
 
 	<para>In 5.0 or newer releases, simply use
 	  <filename>/dev/fd<replaceable>N</replaceable></filename>.</para>
 
 	<sect4>
 	  <title>The Disk Size in 4.X and Earlier Releases</title>
 
 	  <para>There are also <filename>/dev/fd<replaceable>N</replaceable>.<replaceable>size</replaceable></filename>
 	    devices, where <replaceable>size</replaceable> is a floppy disk
 	    size in kilobytes.  These entries are used at low-level format
 	    time to determine the disk size.  1440kB is the size that will be
 	    used in the following examples.</para>
 
 	  <para>Sometimes the entries under <filename>/dev</filename> will
 	    have to be (re)created.  To do that, issue:</para>
 
-	  <screen>&prompt.root; <userinput>cd /dev && ./MAKEDEV "fd*"</userinput></screen>
+	  <screen>&prompt.root; <userinput>cd /dev &amp;&amp; ./MAKEDEV "fd*"</userinput></screen>
 	</sect4>
 
 	<sect4>
 	  <title>The Disk Size in 5.0 and Newer Releases</title>
 
 	  <para>In 5.0, &man.devfs.5; will automatically
 	    manage device nodes in <filename>/dev</filename>, so use of
 	    <command>MAKEDEV</command> is not necessary.</para>
 
 	  <para>The desired disk size is passed to &man.fdformat.1; through
 	    the <option>-f</option> flag.  Supported sizes are listed in
 	  &man.fdcontrol.8;, but be advised that 1440kB is what works best.</para>
 	</sect4>
       </sect3>
 
       <sect3>
 	<title>Formatting</title>
 
 	<para>A floppy disk needs to be low-level formated before it
 	  can be used.  This is usually done by the vendor, but
 	  formatting is a good way to check media integrity.  Although
 	  it is possible to force larger (or smaller) disk sizes,
 	  1440kB is what most floppy disks are designed for.</para>
 
 	<para>To low-level format the floppy disk you need to use
 	  &man.fdformat.1;.  This utility expects the device name as an
 	  argument.</para>
 
 	  <para>Make note of any error messages, as these can help
 	    determine if the disk is good or bad.</para>
 
 	<sect4>
 	  <title>Formatting in 4.X and Earlier Releases</title>
 
 	  <para>Use the
 	    <filename>/dev/fd<replaceable>N</replaceable>.<replaceable>size</replaceable></filename>
 	    devices to format the floppy.  Insert a new 3.5inch floppy
 	    disk in your drive and issue:</para>
 
 	  <screen>&prompt.root; <userinput>/usr/sbin/fdformat /dev/fd0.1440</userinput></screen>
 
 	</sect4>
 
 	<sect4>
 	  <title>Formatting in 5.0 and Newer Releases</title>
 
 	  <para>Use the
 	    <filename>/dev/fd<replaceable>N</replaceable></filename>
 	    devices to format the floppy.  Insert a new 3.5inch floppy
 	    disk in your drive and issue:</para>
 
 	  <screen>&prompt.root; <userinput>/usr/sbin/fdformat -f 1440 /dev/fd0</userinput></screen>
 
 	</sect4>
       </sect3>
     </sect2>
 
 
 
     <sect2>
       <title>The Disk Label</title>
 
       <para>After low-level formatting the disk, you will need to
 	place a disk label on it.  This disk label will be destroyed
 	later, but it is needed by the system to determine the size of
 	the disk and its geometry later.</para>
 
       <para>The new disk label will take over the whole disk, and will
 	contain all the proper information about the geometry of the
 	floppy.  The geometry values for the disk label are listed in
 	<filename>/etc/disktab</filename>.</para>
 
       <para>You can run now &man.disklabel.8; like so:</para>
 
       <screen>&prompt.root; <userinput>/sbin/disklabel -B -r -w /dev/fd0 fd1440</userinput></screen>
 
       <note><para>Since &os;&nbsp;5.1-RELEASE, the &man.bsdlabel.8;
 	utility replaces the old &man.disklabel.8; program.  With
 	&man.bsdlabel.8; a number of obsolete options and parameters
 	have been retired; in the example above the option
 	<option>-r</option> should be removed.  For more
 	information, please refer to the &man.bsdlabel.8;
 	manual page.</para></note>
 
     </sect2>
 
     <sect2>
       <title>The File System</title>
 
       <para>Now the floppy is ready to be high-level formated. This
 	will place a new file system on it, which will let FreeBSD read
 	and write to the disk.  After creating the new file system, the
 	disk label is destroyed, so if you want to reformat the disk, you
 	will have to recreate the disk label.</para>
 
       <para>The floppy's file system can be either UFS or FAT.
 	 FAT is generally a better choice for floppies.</para>
 
       <para>To put a new file system on the floppy, issue:</para>
 
       <screen>&prompt.root; <userinput>/sbin/newfs_msdos /dev/fd0</userinput></screen>
 
       <para>The disk is now ready for use.</para>
     </sect2>
 
 
     <sect2>
       <title>Using the Floppy</title>
 
       <para>To use the floppy, mount it with &man.mount.msdos.8; (in
 	4.X and earlier releases) or &man.mount.msdosfs.8; (in 5.0 or
 	newer releases).  One can also use
 	<filename role="package">emulators/mtools</filename> from the ports
 	collection.</para>
     </sect2>
   </sect1>
 
   <sect1 id="backups-tapebackups">
     <title>Creating and Using Data Tapes</title>
 
     <indexterm><primary>tape media</primary></indexterm>
     <para>The major tape media are the 4mm, 8mm, QIC, mini-cartridge and
       DLT.</para>
 
     <sect2 id="backups-tapebackups-4mm">
       <title>4mm (DDS: Digital Data Storage)</title>
 
       <indexterm>
         <primary>tape media</primary>
 	<secondary>DDS (4mm) tapes</secondary>
       </indexterm>
       <indexterm>
         <primary>tape media</primary>
 	<secondary>QIC tapes</secondary>
       </indexterm>
       <para>4mm tapes are replacing QIC as the workstation backup media of
 	choice.  This trend accelerated greatly when Conner purchased Archive,
 	a leading manufacturer of QIC drives, and then stopped production of
 	QIC drives.  4mm drives are small and quiet but do not have the
 	reputation for reliability that is enjoyed by 8mm drives.  The
 	cartridges are less expensive and smaller (3 x 2 x 0.5 inches, 76 x 51
 	x 12 mm) than 8mm cartridges.  4mm, like 8mm, has comparatively short
 	head life for the same reason, both use helical scan.</para>
 
       <para>Data throughput on these drives starts ~150&nbsp;kB/s, peaking at ~500&nbsp;kB/s.
 	Data capacity starts at 1.3&nbsp;GB and ends at 2.0&nbsp;GB.  Hardware
 	compression, available with most of these drives, approximately
 	doubles the capacity.  Multi-drive tape library units can have 6
 	drives in a single cabinet with automatic tape changing.  Library
 	capacities reach 240&nbsp;GB.</para>
 
       <para>The DDS-3 standard now supports tape capacities up to 12&nbsp;GB (or
 	24&nbsp;GB compressed).</para>
 
       <para>4mm drives, like 8mm drives, use helical-scan.  All the benefits
 	and drawbacks of helical-scan apply to both 4mm and 8mm drives.</para>
 
       <para>Tapes should be retired from use after 2,000 passes or 100 full
 	backups.</para>
     </sect2>
 
     <sect2 id="backups-tapebackups-8mm">
       <title>8mm (Exabyte)</title>
       <indexterm>
         <primary>tape media</primary>
 	<secondary>Exabyte (8mm) tapes</secondary>
       </indexterm>
 
       <para>8mm tapes are the most common SCSI tape drives; they are the best
 	choice of exchanging tapes.  Nearly every site has an Exabyte 2&nbsp;GB 8mm
 	tape drive.  8mm drives are reliable, convenient and quiet. Cartridges
 	are inexpensive and small (4.8 x 3.3 x 0.6 inches; 122 x 84 x 15 mm).
 	One downside of 8mm tape is relatively short head and tape life due to
 	the high rate of relative motion of the tape across the heads.</para>
 
       <para>Data throughput ranges from ~250&nbsp;kB/s to ~500&nbsp;kB/s.  Data sizes start
 	at 300&nbsp;MB and go up to 7&nbsp;GB.  Hardware compression, available with
 	most of these drives, approximately doubles the capacity.  These
 	drives are available as single units or multi-drive tape libraries
 	with 6 drives and 120 tapes in a single cabinet.  Tapes are changed
 	automatically by the unit.  Library capacities reach 840+&nbsp;GB.</para>
 
       <para>The Exabyte <quote>Mammoth</quote> model supports 12&nbsp;GB on one tape
 	(24&nbsp;GB with compression) and costs approximately twice as much as
 	conventional tape drives.</para>
 
       <para>Data is recorded onto the tape using helical-scan, the heads are
 	positioned at an angle to the media (approximately 6 degrees).  The
 	tape wraps around 270 degrees of the spool that holds the heads.  The
 	spool spins while the tape slides over the spool.  The result is a
 	high density of data and closely packed tracks that angle across the
 	tape from one edge to the other.</para>
     </sect2>
 
     <sect2 id="backups-tapebackups-qic">
       <title>QIC</title>
       <indexterm>
         <primary>tape media</primary>
 	<secondary>QIC-150</secondary>
       </indexterm>
 
       <para>QIC-150 tapes and drives are, perhaps, the most common tape drive
 	and media around.  QIC tape drives are the least expensive <quote>serious</quote>
 	backup drives.  The downside is the cost of media.  QIC tapes are
 	expensive compared to 8mm or 4mm tapes, up to 5 times the price per GB
 	data storage.  But, if your needs can be satisfied with a half-dozen
 	tapes, QIC may be the correct choice.  QIC is the
 	<emphasis>most</emphasis> common tape drive.  Every site has a QIC
 	drive of some density or another.  Therein lies the rub, QIC has a
 	large number of densities on physically similar (sometimes identical)
 	tapes.  QIC drives are not quiet.  These drives audibly seek before
 	they begin to record data and are clearly audible whenever reading,
 	writing or seeking.  QIC tapes measure (6 x 4 x 0.7 inches; 152 x
 	102 x 17 mm).</para>
 
       <para>Data throughput ranges from ~150&nbsp;kB/s to ~500&nbsp;kB/s.  Data capacity
 	ranges from 40&nbsp;MB to 15&nbsp;GB.  Hardware compression is available on many
 	of the newer QIC drives.  QIC drives are less frequently installed;
 	they are being supplanted by DAT drives.</para>
 
       <para>Data is recorded onto the tape in tracks.  The tracks run along
 	the long axis of the tape media from one end to the other.  The number
 	of tracks, and therefore the width of a track, varies with the tape's
 	capacity.  Most if not all newer drives provide backward-compatibility
 	at least for reading (but often also for writing).  QIC has a good
 	reputation regarding the safety of the data (the mechanics are simpler
 	and more robust than for helical scan drives).</para>
 
       <para>Tapes should be retired from use after 5,000 backups.</para>
     </sect2>
 
     <sect2 id="backups-tapebackups-dlt">
       <title>DLT</title>
       <indexterm>
         <primary>tape media</primary>
 	<secondary>DLT</secondary>
       </indexterm>
 
       <para>DLT has the fastest data transfer rate of all the drive types
 	listed here.  The 1/2" (12.5mm) tape is contained in a single spool
 	cartridge (4 x 4 x 1 inches; 100 x 100 x 25 mm).  The cartridge has a
 	swinging gate along one entire side of the cartridge.  The drive
 	mechanism opens this gate to extract the tape leader.  The tape leader
 	has an oval hole in it which the drive uses to <quote>hook</quote> the tape.  The
 	take-up spool is located inside the tape drive.  All the other tape
 	cartridges listed here (9 track tapes are the only exception) have
 	both the supply and take-up spools located inside the tape cartridge
 	itself.</para>
 
       <para>Data throughput is approximately 1.5&nbsp;MB/s, three times the throughput of
 	4mm, 8mm, or QIC tape drives.  Data capacities range from 10&nbsp;GB to 20&nbsp;GB
 	for a single drive.  Drives are available in both multi-tape changers
 	and multi-tape, multi-drive tape libraries containing from 5 to 900
 	tapes over 1 to 20 drives, providing from 50&nbsp;GB to 9&nbsp;TB of
 	storage.</para>
 
       <para>With compression, DLT Type IV format supports up to 70&nbsp;GB
 	capacity.</para>
 
       <para>Data is recorded onto the tape in tracks parallel to the direction
 	of travel (just like QIC tapes).  Two tracks are written at once.
 	Read/write head lifetimes are relatively long; once the tape stops
 	moving, there is no relative motion between the heads and the
 	tape.</para>
     </sect2>
 
     <sect2>
       <title id="backups-tapebackups-ait">AIT</title>
       <indexterm>
         <primary>tape media</primary>
 	<secondary>AIT</secondary>
       </indexterm>
 
       <para>AIT is a new format from Sony, and can hold up to 50&nbsp;GB (with
 	compression) per tape.  The tapes contain memory chips which retain an
 	index of the tape's contents.  This index can be rapidly read by the
 	tape drive to determine the position of files on the tape, instead of
 	the several minutes that would be required for other tapes.  Software
 	such as <application>SAMS:Alexandria</application> can operate forty or more AIT tape libraries,
 	communicating directly with the tape's memory chip to display the
 	contents on screen, determine what files were backed up to which
 	tape, locate the correct tape, load it, and restore the data from the
 	tape.</para>
 
       <para>Libraries like this cost in the region of $20,000, pricing them a
 	little out of the hobbyist market.</para>
     </sect2>
 
     <sect2>
       <title>Using a New Tape for the First Time</title>
 
       <para>The first time that you try to read or write a new, completely
 	blank tape, the operation will fail.  The console messages should be
 	similar to:</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>The tape does not contain an Identifier Block (block number 0).
 	All QIC tape drives since the adoption of QIC-525 standard write an
 	Identifier Block to the tape.  There are two solutions:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><command>mt fsf 1</command> causes the tape drive to write an
 	  Identifier Block to the tape.</para>
 	</listitem>
 
 	<listitem>
 	  <para>Use the front panel button to eject the tape.</para>
 
 	  <para>Re-insert the tape and <command>dump</command> data to
 	    the tape.</para>
 
 	  <para><command>dump</command> will report <errorname>DUMP: End of tape
 	    detected</errorname> and the console will show: <errorname>HARDWARE
 	    FAILURE info:280 asc:80,96</errorname>.</para>
 
 	  <para>rewind the tape using: <command>mt rewind</command>.</para>
 
 	  <para>Subsequent tape operations are successful.</para>
 	</listitem>
       </itemizedlist>
 
     </sect2>
   </sect1>
 
   <sect1 id="backups-floppybackups">
     <title>Backups to Floppies</title>
 
     <sect2 id="floppies-using">
       <title>Can I Use Floppies for Backing Up My Data?</title>
       <indexterm><primary>backup floppies</primary></indexterm>
       <indexterm><primary>floppy disks</primary></indexterm>
 
       <para>Floppy disks are not really a suitable media for
         making backups as:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>The media is unreliable, especially over long periods of
 	    time.</para>
 	</listitem>
 
 	<listitem>
 	  <para>Backing up and restoring is very slow.</para>
 	</listitem>
 
 	<listitem>
 	  <para>They have a very limited capacity (the days of backing up
 	    an entire hard disk onto a dozen or so floppies has long since
 	    passed).</para>
 	</listitem>
       </itemizedlist>
 
       <para>However, if you have no other method of backing up your data then
 	floppy disks are better than no backup at all.</para>
 
       <para>If you do have to use floppy disks then ensure that you use good
 	quality ones. Floppies that have been lying around the office for a
 	couple of years are a bad choice. Ideally use new ones from a
 	reputable manufacturer.</para>
     </sect2>
 
     <sect2 id="floppies-creating">
       <title>So How Do I Backup My Data to Floppies?</title>
 
       <para>The best way to backup to floppy disk is to use
 	&man.tar.1; with the <option>-M</option> (multi
 	volume) option, which allows backups to span multiple
 	floppies.</para>
 
       <para>To backup all the files in the current directory and sub-directory
 	use this (as <username>root</username>):</para>
 
       <screen>&prompt.root; <userinput>tar Mcvf /dev/fd0 *</userinput></screen>
 
       <para>When the first floppy is full &man.tar.1; will prompt you to
 	insert the next volume (because &man.tar.1; is media independent it
 	refers to volumes; in this context it means floppy disk).</para>
 
       <screen>Prepare volume #2 for /dev/fd0 and hit return:</screen>
 
       <para>This is repeated (with the volume number incrementing) until all
 	the specified files have been archived.</para>
     </sect2>
 
     <sect2 id="floppies-compress">
       <title>Can I Compress My Backups?</title>
       <indexterm>
         <primary><command>tar</command></primary>
       </indexterm>
       <indexterm>
         <primary><command>gzip</command></primary>
       </indexterm>
       <indexterm><primary>compression</primary></indexterm>
 
       <para>Unfortunately, &man.tar.1; will not allow the
 	<option>-z</option> option to be used for multi-volume archives.
 	You could, of course, &man.gzip.1; all the files,
 	&man.tar.1; them to the floppies, then
 	&man.gunzip.1; the files again!</para>
     </sect2>
 
     <sect2 id="floppies-restoring">
       <title>How Do I Restore My Backups?</title>
 
       <para>To restore the entire archive use:</para>
 
       <screen>&prompt.root; <userinput>tar Mxvf /dev/fd0</userinput></screen>
 
       <para>There are two ways that you can use to restore only
 	specific files.  First, you can start with the first floppy
 	and use:</para>
 
       <screen>&prompt.root; <userinput>tar Mxvf /dev/fd0 <replaceable>filename</replaceable></userinput></screen>
 
       <para>The utility &man.tar.1; will prompt you to insert subsequent floppies until it
 	finds the required file.</para>
 
       <para>Alternatively, if you know which floppy the file is on then you
 	can simply insert that floppy and use the same command as above. Note
 	that if the first file on the floppy is a continuation from the
 	previous one then &man.tar.1; will warn you that it cannot
 	restore it, even if you have not asked it to!</para>
     </sect2>
   </sect1>
 
   <sect1 id="backup-strategies">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Lowell</firstname>
 	  <surname>Gilbert</surname>
 	  <contrib>Original work by </contrib>
 	</author>
       </authorgroup>
       <!-- 3 Dec 2005 -->
     </sect1info>
 
     <title>Backup Strategies</title>
 
     <para>The first requirement in devising a backup plan is to make sure that
       all of the following problems are covered:</para>
 
     <itemizedlist>
       <listitem>
 	<para>Disk failure</para>
       </listitem>
       <listitem>
 	<para>Accidental file deletion</para>
       </listitem>
       <listitem>
 	<para>Random file corruption</para>
       </listitem>
       <listitem>
 	<para>Complete machine destruction (e.g. fire), including destruction
 	  of any on-site backups.</para>
       </listitem>
     </itemizedlist>
 
     <para>It is perfectly possible that some systems will be best served by
       having each of these problems covered by a completely different
       technique.  Except for strictly personal systems with very low-value
       data, it is unlikely that one technique would cover all of them.</para>
 
     <para>Some of the techniques in the toolbox are:</para>
 
     <itemizedlist>
       <listitem>
 	<para>Archives of the whole system, backed up onto permanent media
 	  offsite.  This actually provides protection against all of the
 	  possible problems listed above, but is slow and inconvenient to
 	  restore from.  You can keep copies of the backups onsite and/or
 	  online, but there will still be inconveniences in restoring files,
 	  especially for non-privileged users.</para>
       </listitem>
 
       <listitem>
 	<para>Filesystem snapshots.  This is really only helpful in the
 	  accidental file deletion scenario, but it can be
 	  <emphasis>very</emphasis> helpful in that case, and is quick and
 	  easy to deal with.</para>
       </listitem>
 
       <listitem>
 	<para>Copies of whole filesystems and/or disks (e.g. periodic rsync of
 	  the whole machine).  This is generally most useful in networks with
 	  unique requirements.  For general protection against disk failure,
 	  it is usually inferior to <acronym>RAID</acronym>.  For restoring
 	  accidentally deleted files, it can be comparable to
 	  <acronym>UFS</acronym> snapshots, but that depends on your
 	  preferences.</para>
       </listitem>
 
       <listitem>
 	<para><acronym>RAID</acronym>.  Minimizes or avoids downtime when a
 	  disk fails.  At the expense of having to deal with disk failures
 	  more often (because you have more disks), albeit at a much lower
 	  urgency.</para>
       </listitem>
 
       <listitem>
 	<para>Checking fingerprints of files.  The &man.mtree.8; utility is
 	  very useful for this.  Although it is not a backup technique, it
 	  helps guarantee that you will notice when you need to resort to your
 	  backups.  This is particularly important for offline backups, and
 	  should be checked periodically.</para>
       </listitem>
     </itemizedlist>
 
     <para>It is quite easy to come up with even more techniques, many of them
       variations on the ones listed above.  Specialized requirements will
       usually lead to specialized techniques (for example, backing up a live
       database usually requires a method particular to the database software
       as an intermediate step).  The important thing is to know what dangers
       you want to protect against, and how you will handle each.</para>
   </sect1>
 
   <sect1 id="backup-basics">
     <title>Backup Basics</title>
 
     <para>The three major backup programs are
 	&man.dump.8;,
 	&man.tar.1;,
       and
 	&man.cpio.1;.</para>
 
     <sect2>
       <title>Dump and 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>The traditional &unix; backup programs are
 	<command>dump</command> and <command>restore</command>.  They
 	operate on the drive as a collection of disk blocks, below the
 	abstractions of files, links and directories that are created by
 	the file systems. <command>dump</command> backs up an entire
 	file system on a device.  It is unable to backup only part of a
 	file system or a directory tree that spans more than one
 	file system.  <command>dump</command> does not write files and
 	directories to tape, but rather writes the raw data blocks that
 	comprise files and directories.</para>
 
       <note><para>If you use <command>dump</command> on your root directory, you
         would not back up <filename>/home</filename>,
         <filename>/usr</filename> or many other directories since
         these are typically mount points for other file systems or
         symbolic links into those file systems.</para></note>
 
       <para><command>dump</command> has quirks that remain from its early days in
 	Version 6 of AT&amp;T UNIX (circa 1975).  The default
 	parameters are suitable for 9-track tapes (6250 bpi), not the
 	high-density media available today (up to 62,182 ftpi).  These
 	defaults must be overridden on the command line to utilize the
 	capacity of current tape drives.</para>
 
       <indexterm><primary><filename>.rhosts</filename></primary></indexterm>
       <para>It is also possible to backup data across the network to a
         tape drive attached to another computer with <command>rdump</command> and
         <command>rrestore</command>.  Both programs rely upon &man.rcmd.3; and
         &man.ruserok.3; to access the remote tape drive.  Therefore,
 	the user performing the backup must be listed in the
 	<filename>.rhosts</filename> file on the remote computer.  The
         arguments to <command>rdump</command> and <command>rrestore</command> must be suitable
         to use on the remote computer.  When
         <command>rdump</command>ing from a FreeBSD computer to an
         Exabyte tape drive connected to a Sun called
         <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>Beware: there are security implications to
         allowing <filename>.rhosts</filename> authentication.  Evaluate your
         situation carefully.</para>
 
       <para>It is also possible to use <command>dump</command> and
         <command>restore</command> in a more secure fashion over
         <command>ssh</command>.</para>
 
       <example>
 	<title>Using <command>dump</command> over <application>ssh</application></title>
 
 	<screen>&prompt.root; <userinput>/sbin/dump -0uan -f - /usr | gzip -2 | ssh -c blowfish \
           targetuser@targetmachine.example.com dd of=/mybigfiles/dump-usr-l0.gz</userinput></screen>
 
       </example>
 
       <para>Or using <command>dump</command>'s built-in method,
         setting the environment variable <envar>RSH</envar>:</para>
 
       <example>
 	<title>Using <command>dump</command> over <application>ssh</application> with <envar>RSH</envar> set</title>
 
 	<screen>&prompt.root; <userinput>RSH=/usr/bin/ssh /sbin/dump -0uan -f targetuser@targetmachine.example.com:/dev/sa0 /usr</userinput></screen>
 
       </example>
 
     </sect2>
 
     <sect2>
       <title><command>tar</command></title>
       <indexterm>
         <primary>backup software</primary>
         <secondary><command>tar</command></secondary>
       </indexterm>
 
       <para>&man.tar.1; also dates back to Version 6 of AT&amp;T UNIX
 	(circa 1975).  <command>tar</command> operates in cooperation
 	with the file system; it writes files and
 	directories to tape. <command>tar</command> does not support the
 	full range of options that are available from &man.cpio.1;, but
 	it does not require the unusual command
 	pipeline that <command>cpio</command> uses.</para>
 
       <indexterm><primary><command>tar</command></primary></indexterm>
 
       <para>On FreeBSD 5.3 and later, both GNU <command>tar</command>
         and the default <command>bsdtar</command> are available.  The
         GNU version can be invoked with <command>gtar</command>.  It
         supports remote devices using the same syntax as
         <command>rdump</command>.  To <command>tar</command> to an
         Exabyte tape drive connected to a Sun called
         <hostid>komodo</hostid>, use:</para>
 
       <screen>&prompt.root; <userinput>/usr/bin/gtar cf komodo:/dev/nsa8 . 2>&amp;1</userinput></screen>
 
       <para>The same could be accomplished with
 	<command>bsdtar</command> by using a pipeline and
 	<command>rsh</command> to send the data to a remote tape
 	drive.</para>
 
       <screen>&prompt.root; <userinput>tar cf - . | rsh <replaceable>hostname</replaceable> dd of=<replaceable>tape-device</replaceable> obs=20b</userinput></screen>
 
       <para>If you are worried about the security of backing up over a
 	network you should use the <command>ssh</command> command
 	instead of <command>rsh</command>.</para>
     </sect2>
 
     <sect2>
       <title><command>cpio</command></title>
       <indexterm>
         <primary>backup software</primary>
         <secondary><command>cpio</command></secondary>
       </indexterm>
 
       <para>&man.cpio.1; is the original &unix; file interchange tape
 	program for magnetic media.  <command>cpio</command> has options
 	(among many others) to perform byte-swapping, write a number of
 	different archive formats, and pipe the data to other programs.
 	This last feature makes <command>cpio</command> an excellent
 	choice for installation media.  <command>cpio</command> does not
 	know how to walk the directory tree and a list of files must be
 	provided through <filename>stdin</filename>.</para>
       <indexterm><primary><command>cpio</command></primary></indexterm>
 
       <para><command>cpio</command> does not support backups across
 	the network.  You can use a pipeline and <command>rsh</command>
 	to send the data to a remote tape drive.</para>
 
       <screen>&prompt.root; <userinput>for f in <replaceable>directory_list; do</replaceable></userinput>
-<userinput>find $f >> backup.list</userinput>
+<userinput>find $f &gt;&gt; backup.list</userinput>
 <userinput>done</userinput>
-&prompt.root; <userinput>cpio -v -o --format=newc < backup.list | ssh <replaceable>user</replaceable>@<replaceable>host</replaceable> "cat > <replaceable>backup_device</replaceable>"</userinput></screen>
+&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>Where <replaceable>directory_list</replaceable> is the list of
 	directories you want to back up,
 	<replaceable>user</replaceable>@<replaceable>host</replaceable> is the
 	user/hostname combination that will be performing the backups, and
 	<replaceable>backup_device</replaceable> is where the backups should
 	be written to (e.g., <filename>/dev/nsa0</filename>).</para>
     </sect2>
 
     <sect2>
       <title><command>pax</command></title>
       <indexterm>
         <primary>backup software</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; is IEEE/&posix;'s answer to
 	<command>tar</command> and <command>cpio</command>.  Over the
 	years the various versions of <command>tar</command> and
 	<command>cpio</command> have gotten slightly incompatible.  So
 	rather than fight it out to fully standardize them, &posix;
 	created a new archive utility. <command>pax</command> attempts
 	to read and write many of the various <command>cpio</command>
 	and <command>tar</command> formats, plus new formats of its own.
 	Its command set more resembles <command>cpio</command> than
 	<command>tar</command>.</para>
     </sect2>
 
     <sect2 id="backups-programs-amanda">
       <title><application>Amanda</application></title>
       <indexterm>
         <primary>backup software</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) is a client/server backup system,
         rather than a single program.  An <application>Amanda</application> server will backup to
         a single tape drive any number of computers that have <application>Amanda</application>
         clients and a network connection to the <application>Amanda</application> server.  A
         common problem at sites with a number of large disks is
         that the length of time required to backup to data directly to tape
         exceeds the amount of time available for the task.  <application>Amanda</application>
         solves this problem.  <application>Amanda</application> can use a <quote>holding disk</quote> to
         backup several file systems at the same time.  <application>Amanda</application> creates
         <quote>archive sets</quote>: a group of tapes used over a period of time to
         create full backups of all the file systems listed in <application>Amanda</application>'s
         configuration file.  The <quote>archive set</quote> also contains nightly
         incremental (or differential) backups of all the file systems.
         Restoring a damaged file system requires the most recent full
         backup and the incremental backups.</para>
 
       <para>The configuration file provides fine control of backups and the
 	network traffic that <application>Amanda</application> generates.  <application>Amanda</application> will use any of the
 	above backup programs to write the data to tape.  <application>Amanda</application> is available
 	as either a port or a package, it is not installed by default.</para>
       </sect2>
 
     <sect2>
       <title>Do Nothing</title>
 
       <para><quote>Do nothing</quote> is not a computer program, but it is the
 	most widely used backup strategy.  There are no initial costs.  There
 	is no backup schedule to follow.  Just say no.  If something happens
 	to your data, grin and bear it!</para>
 
       <para>If your time and your data is worth little to nothing, then
 	<quote>Do nothing</quote> is the most suitable backup program for your
 	computer.  But beware, &unix; is a useful tool, you may find that within
 	six months you have a collection of files that are valuable to
 	you.</para>
 
       <para><quote>Do nothing</quote> is the correct backup method for
 	<filename>/usr/obj</filename> and other directory trees that can be
 	exactly recreated by your computer.  An example is the files that
 	comprise the HTML or &postscript; version of this Handbook.
 	These document formats have been created from SGML input
 	files.  Creating backups of the HTML or &postscript; files is
 	not necessary.  The SGML files are backed up regularly.</para>
     </sect2>
 
     <sect2>
       <title>Which Backup Program Is Best?</title>
       <indexterm>
         <primary>LISA</primary>
       </indexterm>
 
       <para>&man.dump.8; <emphasis>Period.</emphasis> Elizabeth D. Zwicky
 	torture tested all the backup programs discussed here.  The clear
 	choice for preserving all your data and all the peculiarities of &unix;
 	file systems is <command>dump</command>.  Elizabeth created file systems containing
 	a large variety of unusual conditions (and some not so unusual ones)
 	and tested each program by doing a backup and restore of those
 	file systems.  The peculiarities included: files with holes, files with
 	holes and a block of nulls, files with funny characters in their
 	names, unreadable and unwritable files, devices, files that change
 	size during the backup, files that are created/deleted during the
 	backup and more.  She presented the results at LISA V in Oct. 1991.
 	See <ulink
 	  url="http://berdmann.dyndns.org/zwicky/testdump.doc.html">torture-testing
 	  Backup and Archive Programs</ulink>.</para>
     </sect2>
 
     <sect2>
       <title>Emergency Restore Procedure</title>
 
       <sect3>
 	<title>Before the Disaster</title>
 
 	<para>There are only four steps that you need to perform in
 	  preparation for any disaster that may occur.</para>
 	<indexterm>
     <primary><command>disklabel</command></primary>
   </indexterm>
 
 	<para>First, print the disklabel from each of your disks
 	  (e.g. <command>disklabel da0 | lpr</command>), your file system table
 	  (<filename>/etc/fstab</filename>) and all boot messages,
 	  two copies of
 	  each.</para>
 
 	<indexterm><primary>fix-it floppies</primary></indexterm>
 	<para>Second, determine that the boot and fix-it floppies
 	  (<filename>boot.flp</filename> and <filename>fixit.flp</filename>)
 	  have all your devices.  The easiest way to check is to reboot your
 	  machine with the boot floppy in the floppy drive and check the boot
 	  messages.  If all your devices are listed and functional, skip on to
 	  step three.</para>
 
 	<para>Otherwise, you have to create two custom bootable
 	  floppies which have a kernel that can mount all of your disks
 	  and access your tape drive.  These floppies must contain:
 	  <command>fdisk</command>, <command>disklabel</command>,
 	  <command>newfs</command>, <command>mount</command>, and
 	  whichever backup program you use.  These programs must be
 	  statically linked.  If you use <command>dump</command>, the
 	  floppy must contain <command>restore</command>.</para>
 
 	<para>Third, create backup tapes regularly.  Any changes that you make
 	  after your last backup may be irretrievably lost.  Write-protect the
 	  backup tapes.</para>
 
 	<para>Fourth, test the floppies (either <filename>boot.flp</filename>
 	  and <filename>fixit.flp</filename> or the two custom bootable
 	  floppies you made in step two.) and backup tapes.  Make notes of the
 	  procedure.  Store these notes with the bootable floppy, the
 	  printouts and the backup tapes.  You will be so distraught when
 	  restoring that the notes may prevent you from destroying your backup
 	  tapes (How? In place of <command>tar xvf /dev/sa0</command>, you
 	  might accidentally type <command>tar cvf /dev/sa0</command> and
 	  over-write your backup tape).</para>
 
 	<para>For an added measure of security, make bootable floppies and two
 	  backup tapes each time.  Store one of each at a remote location.  A
 	  remote location is NOT the basement of the same office building.  A
 	  number of firms in the World Trade Center learned this lesson the
 	  hard way.  A remote location should be physically separated from
 	  your computers and disk drives by a significant distance.</para>
 
 	<example>
 	  <title>A Script for Creating a Bootable Floppy</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
+	 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 /sbin/init &gt; /mnt/sbin/init
+gzip -c -best /sbin/fsck &gt; /mnt/sbin/fsck
+gzip -c -best /sbin/mount &gt; /mnt/sbin/mount
+gzip -c -best /sbin/halt &gt; /mnt/sbin/halt
+gzip -c -best /sbin/restore &gt; /mnt/sbin/restore
 
-gzip -c -best /bin/sh > /mnt/bin/sh
-gzip -c -best /bin/sync > /mnt/bin/sync
+gzip -c -best /bin/sh &gt; /mnt/bin/sh
+gzip -c -best /bin/sync &gt; /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 <<EOM
+cat &gt; /mnt/etc/fstab &lt;&lt;EOM
 /dev/fd0a    /    ufs    rw  1  1
 EOM
 
 #
 # create minimum passwd file
 #
-cat > /mnt/etc/passwd <<EOM
+cat &gt; /mnt/etc/passwd &lt;&lt;EOM
 root:*:0:0:Charlie &:/root:/bin/sh
 EOM
 
-cat > /mnt/etc/master.passwd <<EOM
+cat &gt; /mnt/etc/master.passwd &lt;&lt;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>After the Disaster</title>
 
 	<para>The key question is: did your hardware survive?  You have been
 	  doing regular backups so there is no need to worry about the
 	  software.</para>
 
 	<para>If the hardware has been damaged, the parts should be replaced
 	  before attempting to use the computer.</para>
 
 	<para>If your hardware is okay, check your floppies.  If you are using
 	  a custom boot floppy, boot single-user (type <literal>-s</literal>
 	  at the <prompt>boot:</prompt> prompt).  Skip the following
 	  paragraph.</para>
 
 	<para>If you are using the <filename>boot.flp</filename> and
 	  <filename>fixit.flp</filename> floppies, keep reading.  Insert the
 	  <filename>boot.flp</filename> floppy in the first floppy drive and
 	  boot the computer.  The original install menu will be displayed on
 	  the screen.  Select the <literal>Fixit--Repair mode with CDROM or
 	    floppy.</literal> option.  Insert the
 	  <filename>fixit.flp</filename> when prompted.
 	  <command>restore</command> and the other programs that you need are
 	  located in <filename class="directory">/mnt2/rescue</filename>
 	  (<filename class="directory">/mnt2/stand</filename> for
 	  &os; versions older than 5.2).</para>
 
 	<para>Recover each file system separately.</para>
 
 	<indexterm>
     <primary><command>mount</command></primary>
   </indexterm>
 	<indexterm><primary>root partition</primary></indexterm>
 	<indexterm>
     <primary><command>disklabel</command></primary>
   </indexterm>
 	<indexterm>
     <primary><command>newfs</command></primary>
   </indexterm>
 	<para>Try to <command>mount</command> (e.g. <command>mount /dev/da0a
 	    /mnt</command>)  the root partition of your first disk.  If the
 	  disklabel was damaged, use <command>disklabel</command> to re-partition and
 	  label the disk to match the label that you printed and saved.  Use
 	    <command>newfs</command> to re-create the file systems.  Re-mount the root
 	  partition of the floppy read-write (<command>mount -u -o rw
 	    /mnt</command>).  Use your backup program and backup tapes to
 	  recover the data for this file system (e.g. <command>restore vrf
 	    /dev/sa0</command>).  Unmount the file system (e.g. <command>umount
 	    /mnt</command>). Repeat for each file system that was
 	  damaged.</para>
 
 	<para>Once your system is running, backup your data onto new tapes.
 	  Whatever caused the crash or data loss may strike again.  Another
 	  hour spent now may save you from further distress later.</para>
       </sect3>
 
 <![ %not.published; [
 
       <sect3>
 	<title>* I Did Not Prepare for the Disaster, What Now?</title>
 
 	<para></para>
       </sect3>
 ]]>
 
     </sect2>
   </sect1>
 
   <sect1 id="disks-virtual">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Marc</firstname>
 	  <surname>Fonvieille</surname>
 	  <contrib>Reorganized and enhanced by </contrib>
 	</author>
       </authorgroup>
     </sect1info>
     <title>Network, Memory, and File-Backed File Systems</title>
     <indexterm><primary>virtual disks</primary></indexterm>
     <indexterm>
       <primary>disks</primary>
       <secondary>virtual</secondary>
     </indexterm>
 
     <para>Aside from the disks you physically insert into your computer:
       floppies, CDs, hard drives, and so forth; other forms of disks
       are understood by FreeBSD - the <firstterm>virtual
       disks</firstterm>.</para>
 
     <indexterm><primary>NFS</primary></indexterm>
     <indexterm><primary>Coda</primary></indexterm>
     <indexterm>
       <primary>disks</primary>
       <secondary>memory</secondary>
     </indexterm>
     <para>These include network file systems such as the <link
 	linkend="network-nfs">Network File System</link> and Coda, memory-based
       file systems and
       file-backed file systems.</para>
 
     <para>According to the FreeBSD version you run, you will have to use
       different tools for creation and use of file-backed and
       memory-based file systems.</para>
 
     <note>
       <para>The FreeBSD&nbsp;4.X users will have to use &man.MAKEDEV.8;
 	to create the required devices.  FreeBSD&nbsp;5.0 and later use
 	&man.devfs.5; to allocate device nodes transparently for the
 	user.</para>
     </note>
 
     <sect2 id="disks-vnconfig">
       <title>File-Backed File System under FreeBSD&nbsp;4.X</title>
       <indexterm>
         <primary>disks</primary>
         <secondary>file-backed (4.X)</secondary>
       </indexterm>
 
       <para>The utility &man.vnconfig.8; configures and enables vnode pseudo-disk
 	devices.  A <firstterm>vnode</firstterm> is a representation
 	of a file, and is the focus of file activity.  This means that
 	&man.vnconfig.8; uses files to create and operate a
 	file system.  One possible use is the mounting of floppy or CD
 	images kept in files.</para>
 
       <para>To use &man.vnconfig.8;, you need &man.vn.4; support in your
 	kernel configuration file:</para>
 
       <programlisting>pseudo-device vn</programlisting>
 
       <para>To mount an existing file system image:</para>
 
       <example>
 	<title>Using vnconfig to Mount an Existing File System
 	  Image under FreeBSD&nbsp;4.X</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>To create a new file system image with &man.vnconfig.8;:</para>
 
       <example>
 	<title>Creating a New File-Backed Disk with <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>File-Backed File System under FreeBSD&nbsp;5.X</title>
       <indexterm>
         <primary>disks</primary>
         <secondary>file-backed (5.X)</secondary>
       </indexterm>
 
       <para>The utility &man.mdconfig.8; is used to configure and enable
 	memory disks, &man.md.4;, under FreeBSD&nbsp;5.X.  To use
 	&man.mdconfig.8;, you have to load &man.md.4; module or to add
 	the support in your kernel configuration file:</para>
 
       <programlisting>device md</programlisting>
 
       <para>The &man.mdconfig.8; command supports three kinds of
 	memory backed virtual disks: memory disks allocated with
 	&man.malloc.9;, memory disks using a file or swap space as
 	backing.  One possible use is the mounting of floppy
 	or CD images kept in files.</para>
 
       <para>To mount an existing file system image:</para>
 
       <example>
 	<title>Using <command>mdconfig</command> to Mount an Existing File System
 	  Image under FreeBSD&nbsp;5.X</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> <replaceable>/mnt</replaceable></userinput></screen>
       </example>
 
       <para>To create a new file system image with &man.mdconfig.8;:</para>
 
       <example>
 	<title>Creating a New File-Backed Disk with <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>If you do not specify the unit number with the
 	<option>-u</option> option, &man.mdconfig.8; will use the
 	&man.md.4; automatic allocation to select an unused device.
 	The name of the allocated unit will be output on stdout like
 	<devicename>md4</devicename>.  For more details about
 	&man.mdconfig.8;, please refer to the manual page.</para>
 
       <note><para>Since &os;&nbsp;5.1-RELEASE, the &man.bsdlabel.8;
 	utility replaces the old &man.disklabel.8; program.  With
 	&man.bsdlabel.8; a number of obsolete options and parameters
 	have been retired; in the example above the option
 	<option>-r</option> should be removed.  For more
 	information, please refer to the &man.bsdlabel.8;
 	manual page.</para></note>
 
       <para>The utility &man.mdconfig.8; is very useful, however it
 	asks many command lines to create a file-backed file system.
 	FreeBSD&nbsp;5.0 also comes with a tool called &man.mdmfs.8;,
 	this program configures a &man.md.4; disk using
 	&man.mdconfig.8;, puts a UFS file system on it using
 	&man.newfs.8;, and mounts it using &man.mount.8;.  For example,
 	if you want to create and mount the same file system image as
 	above, simply type the following:</para>
 
       <example>
 	<title>Configure and Mount a File-Backed Disk with <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>If you use the option <option>md</option> without unit
 	number, &man.mdmfs.8; will use &man.md.4; auto-unit feature to
 	automatically select an unused device.  For more details
 	about &man.mdmfs.8;, please refer to the manual page.</para>
 
     </sect2>
 
     <sect2 id="disks-md-freebsd4">
       <title>Memory-Based File System under FreeBSD&nbsp;4.X</title>
       <indexterm>
         <primary>disks</primary>
         <secondary>memory file system (4.X)</secondary>
       </indexterm>
 
       <para>The &man.md.4; driver is a simple, efficient means to create memory
 	file systems under FreeBSD&nbsp;4.X. &man.malloc.9; is used
 	to allocate the memory.</para>
 
       <para>Simply take a file system you have prepared with, for
 	example, &man.vnconfig.8;, and:</para>
 
       <example>
 	<title>md Memory Disk under FreeBSD&nbsp;4.X</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>For more details, please refer to &man.md.4; manual
 	page.</para>
     </sect2>
 
     <sect2 id="disks-md-freebsd5">
       <title>Memory-Based File System under FreeBSD&nbsp;5.X</title>
       <indexterm>
         <primary>disks</primary>
         <secondary>memory file system (5.X)</secondary>
       </indexterm>
 
       <para>The same tools are used for memory-based and file-backed
 	file systems: &man.mdconfig.8; or &man.mdmfs.8;.  The storage
 	for memory-based file system is allocated with
 	&man.malloc.9;.</para>
 
       <example>
 	<title>Creating a New Memory-Based Disk with
 	  <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>Creating a New Memory-Based Disk with
 	  <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>Instead of using a &man.malloc.9; backed file system, it is
 	possible to use swap, for that just replace
 	<option>malloc</option> with <option>swap</option> in the
 	command line of &man.mdconfig.8;.  The &man.mdmfs.8; utility
 	by default (without <option>-M</option>) creates a swap-based
 	disk.  For more details, please refer to &man.mdconfig.8;
 	and &man.mdmfs.8; manual pages.</para>
     </sect2>
 
     <sect2>
       <title>Detaching a Memory Disk from the System</title>
       <indexterm>
         <primary>disks</primary>
         <secondary>detaching a memory disk</secondary>
       </indexterm>
 
       <para>When a memory-based or file-based file system
 	is not used, you should release all resources to the system.
 	The first thing to do is to unmount the file system, then use
 	&man.mdconfig.8; to detach the disk from the system and release
 	the resources.</para>
 
       <para>For example to detach and free all resources used by
 	<filename>/dev/md4</filename>:</para>
 
       <screen>&prompt.root; <userinput>mdconfig -d -u <replaceable>4</replaceable></userinput></screen>
 
       <para>It is possible to list information about configured
 	&man.md.4; devices in using the command <command>mdconfig
 	-l</command>.</para>
 
       <para>For FreeBSD&nbsp;4.X, &man.vnconfig.8; is used to detach
 	the device.  For example to detach and free all resources
 	used by <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>Contributed by </contrib>
 	</author>
       </authorgroup>
       <!-- 15 JUL 2002 -->
     </sect1info>
 
     <title>File System Snapshots</title>
 
     <indexterm>
       <primary>file systems</primary>
       <secondary>snapshots</secondary>
     </indexterm>
 
       <para>FreeBSD&nbsp;5.0 offers a new feature in conjunction with
 	<link linkend="soft-updates">Soft Updates</link>: File system snapshots.</para>
 
       <para>Snapshots allow a user to create images of specified file
 	systems, and treat them as a file.
 	Snapshot files must be created in the file system that the
 	action is performed on, and a user may create no more than 20
 	snapshots per file system.  Active snapshots are recorded
 	in the superblock so they are persistent across unmount and
 	remount operations along with system reboots.  When a snapshot
 	is no longer required, it can be removed with the standard &man.rm.1;
 	command.  Snapshots may be removed in any order,
 	however all the used space may not be acquired because another snapshot will
 	possibly claim some of the released blocks.</para>
 
       <para>The un-alterable <option>snapshot</option> file flag is set
       by &man.mksnap.ffs.8; after initial creation of a snapshot file.
 	The &man.unlink.1; command makes an exception for snapshot files
 	since it allows them to be removed.</para>
 
       <para>Snapshots are created with the &man.mount.8; command.  To place
 	a snapshot of <filename>/var</filename> in the file
 	<filename>/var/snapshot/snap</filename> use the following
 	command:</para>
 
 <screen>&prompt.root; <userinput>mount -u -o snapshot /var/snapshot/snap /var</userinput></screen>
 
       <para>Alternatively, you can use &man.mksnap.ffs.8; to create
 	a snapshot:</para>
 <screen>&prompt.root; <userinput>mksnap_ffs /var /var/snapshot/snap</userinput></screen>
 
       <para>One can find snapshot files on a file system (e.g. <filename>/var</filename>)
         by using the &man.find.1; command:</para>
 <screen>&prompt.root; <userinput>find /var -flags snapshot</userinput></screen>
 
       <para>Once a snapshot has been created, it has several
 	uses:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>Some administrators will use a snapshot file for backup purposes,
 	    because the snapshot can be transfered to CDs or tape.</para>
 	</listitem>
 
 	<listitem>
 	  <para>File integrity, &man.fsck.8; may be ran on the snapshot.
 	    Assuming that the file system was clean when it was mounted, you
 	    should always get a clean (and unchanging) result.
 	    This is essentially what the
 	    background &man.fsck.8; process does.</para>
 	</listitem>
 
 	<listitem>
 	  <para>Run the &man.dump.8; utility on the snapshot.
 	    A dump will be returned that is consistent with the
 	    file system and the timestamp of the snapshot.  &man.dump.8;
 	    can also take a snapshot, create a dump image and then
 	    remove the snapshot in one command using the
 	    <option>-L</option> flag.</para>
 	</listitem>
 
 	<listitem>
 	  <para>&man.mount.8; the snapshot as a frozen image of the file system.
 	    To &man.mount.8; the snapshot
 	    <filename>/var/snapshot/snap</filename> run:</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>You can now walk the hierarchy of your frozen <filename>/var</filename>
 	file system mounted at <filename>/mnt</filename>.  Everything will
 	initially be in the same state it was during the snapshot creation time.
 	The only exception is that any earlier snapshots will appear
 	as zero length files.  When the use of a snapshot has delimited,
 	it can be unmounted with:</para>
 
 <screen>&prompt.root; <userinput>umount /mnt</userinput>
 &prompt.root; <userinput>mdconfig -d -u 4</userinput></screen>
 
       <para>For more information about <option>softupdates</option> and
 	file system snapshots, including technical papers, you can visit
 	Marshall Kirk McKusick's website at
 	<ulink url="http://www.mckusick.com/"></ulink>.</para>
   </sect1>
 
   <sect1 id="quotas">
     <title>File System Quotas</title>
     <indexterm>
       <primary>accounting</primary>
       <secondary>disk space</secondary>
     </indexterm>
     <indexterm><primary>disk quotas</primary></indexterm>
 
     <para>Quotas are an optional feature of the operating system that
       allow you to limit the amount of disk space and/or the number of
       files a user or members of a group may allocate on a per-file
       system basis. This is used most often on timesharing systems where
       it is desirable to limit the amount of resources any one user or
       group of users may allocate.  This will prevent one user or group
       of users from consuming all of the available disk space.</para>
 
     <sect2>
       <title>Configuring Your System to Enable Disk Quotas</title>
 
       <para>Before attempting to use disk quotas, it is necessary to make
 	sure that quotas are configured in your kernel.  This is done by
 	adding the following line to your kernel configuration
 	file:</para>
 
       <programlisting>options QUOTA</programlisting>
 
       <para>The stock <filename>GENERIC</filename> kernel does not have
 	this enabled by default, so you will have to configure, build and
 	install a custom kernel in order to use disk quotas.  Please refer
 	to <xref linkend="kernelconfig"> for more information on kernel
 	configuration.</para>
 
       <para>Next you will need to enable disk quotas in
 	<filename>/etc/rc.conf</filename>.  This is done by adding the
 	line:</para>
 
       <programlisting>enable_quotas="YES"</programlisting>
       <indexterm>
         <primary>disk quotas</primary>
         <secondary>checking</secondary>
       </indexterm>
       <para>For finer control over your quota startup, there is an
 	additional configuration variable available. Normally on bootup,
 	the quota integrity of each file system is checked by the
 	&man.quotacheck.8; program.  The
 	&man.quotacheck.8; facility insures that the data in
 	the quota database properly reflects the data on the file system.
 	This is a very time consuming process that will significantly
 	affect the time your system takes to boot. If you would like to
 	skip this step, a variable in <filename>/etc/rc.conf</filename>
 	is made available for the purpose:</para>
 
       <programlisting>check_quotas="NO"</programlisting>
 
       <para>Finally you will need to edit <filename>/etc/fstab</filename>
 	to enable disk quotas on a per-file system basis.  This is where
 	you can either enable user or group quotas or both for all of your
 	file systems.</para>
 
       <para>To enable per-user quotas on a file system, add the
 	<option>userquota</option> option to the options field in the
 	<filename>/etc/fstab</filename> entry for the file system you want
 	to enable quotas on.  For example:</para>
 
       <programlisting>/dev/da1s2g   /home    ufs rw,userquota 1 2</programlisting>
 
       <para>Similarly, to enable group quotas, use the
 	<option>groupquota</option> option instead of
 	<option>userquota</option>.  To enable both user and
 	group quotas, change the entry as follows:</para>
 
       <programlisting>/dev/da1s2g    /home    ufs rw,userquota,groupquota 1 2</programlisting>
 
       <para>By default, the quota files are stored in the root directory of
 	the file system with the names <filename>quota.user</filename> and
 	<filename>quota.group</filename> for user and group quotas
 	respectively.  See &man.fstab.5; for more
 	information.  Even though the &man.fstab.5; manual page says that
 	you can specify
 	an alternate location for the quota files, this is not recommended
 	because the various quota utilities do not seem to handle this
 	properly.</para>
 
       <para>At this point you should reboot your system with your new
 	kernel.  <filename>/etc/rc</filename> will automatically run the
 	appropriate commands to  create the initial quota files for all of
 	the quotas you enabled in <filename>/etc/fstab</filename>, so
 	there is no need to manually create any zero length quota
 	files.</para>
 
       <para>In the normal course of operations you should not be required
 	to run the &man.quotacheck.8;,
 	&man.quotaon.8;, or &man.quotaoff.8;
 	commands manually.  However, you may want to read their manual pages
 	just to be familiar with their operation.</para>
     </sect2>
 
     <sect2>
       <title>Setting Quota Limits</title>
       <indexterm>
         <primary>disk quotas</primary>
         <secondary>limits</secondary>
       </indexterm>
 
       <para>Once you have configured your system to enable quotas, verify
 	that they really are enabled.  An easy way to do this is to
 	run:</para>
 
       <screen>&prompt.root; <userinput>quota -v</userinput></screen>
 
       <para>You should see a one line summary of disk usage and current
 	quota limits for each file system that quotas are enabled
 	on.</para>
 
       <para>You are now ready to start assigning quota limits with the
 	&man.edquota.8; command.</para>
 
       <para>You have several options on how to enforce limits on the
 	amount of disk space a user or group may allocate, and how many
 	files they may create.  You may limit allocations based on disk
 	space (block quotas) or number of files (inode quotas) or a
 	combination of both.  Each of these limits are further broken down
 	into two categories: hard and soft limits.</para>
 
       <indexterm><primary>hard limit</primary></indexterm>
       <para>A hard limit may not be exceeded.  Once a user reaches his
 	hard limit he may not make any further allocations on the file
 	system in question.  For example, if the user has a hard limit of
 	500 kbytes on a file system and is currently using 490 kbytes, the
 	user can only allocate an additional 10 kbytes.  Attempting to
 	allocate an additional 11 kbytes will fail.</para>
 
       <indexterm><primary>soft limit</primary></indexterm>
       <para>Soft limits, on the other hand, can be exceeded for a limited
 	amount of time.  This period of time is known as the grace period,
 	which is one week by default.  If a user stays over his or her
 	soft limit longer than the grace period, the soft limit will
 	turn into a hard limit and no further allocations will be allowed.
 	When the user drops back below the soft limit, the grace period
 	will be reset.</para>
 
       <para>The following is an example of what you might see when you run
 	the &man.edquota.8; command.  When the
 	&man.edquota.8; command is invoked, you are placed into
 	the editor specified by the <envar>EDITOR</envar> environment
 	variable, or in the <application>vi</application> editor if the
 	<envar>EDITOR</envar> variable is not set, to allow you to edit
 	the quota limits.</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>You will normally see two lines for each file system that has
 	quotas enabled.  One line for the block limits, and one line for
 	inode limits.  Simply change the value you want updated to modify
 	the quota limit.  For example, to raise this user's block limit
 	from a soft limit of 50 and a hard limit of 75 to a soft limit of
 	500 and a hard limit of 600, change:</para>
 
       <programlisting>/usr: kbytes in use: 65, limits (soft = 50, hard = 75)</programlisting>
 
       <para>to:</para>
 
       <programlisting>/usr: kbytes in use: 65, limits (soft = 500, hard = 600)</programlisting>
 
       <para>The new quota limits will be in place when you exit the
 	editor.</para>
 
       <para>Sometimes it is desirable to set quota limits on a range of
 	UIDs.  This can be done by use of the <option>-p</option> option
 	on the &man.edquota.8; command.  First, assign the
 	desired quota limit to a user, and then run
 	<command>edquota -p protouser startuid-enduid</command>.  For
 	example, if user <username>test</username> has the desired quota
 	limits, the following command can be used to duplicate those quota
 	limits for UIDs 10,000 through 19,999:</para>
 
       <screen>&prompt.root; <userinput>edquota -p test 10000-19999</userinput></screen>
 
       <para>For more information see &man.edquota.8; manual page.</para>
     </sect2>
 
     <sect2>
       <title>Checking Quota Limits and Disk Usage</title>
       <indexterm>
         <primary>disk quotas</primary>
         <secondary>checking</secondary>
       </indexterm>
 
       <para>You can use either the &man.quota.1; or the
 	&man.repquota.8; commands to check quota limits and
 	disk usage.  The &man.quota.1; command can be used to
 	check individual user or group quotas and disk usage.  A user
 	may only examine his own quota, and the quota of a group he
 	is a member of. Only the super-user may view all user and group
 	quotas.  The
 	&man.repquota.8; command can be used to get a summary
 	of all quotas and disk usage for file systems with quotas
 	enabled.</para>
 
       <para>The following is some sample output from the
 	<command>quota -v</command> command for a user that has quota
 	limits on two file systems.</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>grace period</primary></indexterm>
       <para>On the <filename>/usr</filename> file system in the above
 	example, this user is currently 15 kbytes over the soft limit of
 	50 kbytes and has 5 days of the grace period left.  Note the
 	asterisk <literal>*</literal> which indicates that the user is
 	currently over his quota limit.</para>
 
       <para>Normally file systems that the user is not using any disk
 	space on will not show up in the output from the
 	&man.quota.1; command, even if he has a quota limit
 	assigned for that file system.  The <option>-v</option> option
 	will display those file systems, such as the
 	<filename>/usr/var</filename> file system in the above
 	example.</para>
     </sect2>
 
     <sect2>
       <title>Quotas over NFS</title>
       <indexterm><primary>NFS</primary></indexterm>
 
       <para>Quotas are enforced by the quota subsystem on the NFS server.
 	The &man.rpc.rquotad.8; daemon makes quota information available
 	to the &man.quota.1; command on NFS clients, allowing users on
 	those machines to see their quota statistics.</para>
 
       <para>Enable <command>rpc.rquotad</command> in
 	<filename>/etc/inetd.conf</filename> like so:</para>
 
       <programlisting>rquotad/1      dgram rpc/udp wait root /usr/libexec/rpc.rquotad rpc.rquotad</programlisting>
 
       <para>Now restart <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>Contributed by </contrib>
 	  <affiliation>
 	    <address><email>shamrock@cypherpunks.to</email></address>
 	  </affiliation>
 	</author>
       </authorgroup>
       <!-- 11 MARCH 2003 -->
     </sect1info>
 
     <title>Encrypting Disk Partitions</title>
     <indexterm>
       <primary>disks</primary>
       <secondary>encrypting</secondary></indexterm>
 
     <para>FreeBSD offers excellent online protections against
       unauthorized data access.  File permissions and Mandatory
       Access Control (MAC) (see <xref linkend="mac">) help prevent
       unauthorized third-parties from accessing data while the operating
       system is active and the computer is powered up. However,
       the permissions enforced by the operating system are irrelevant if an
       attacker has physical access to a computer and can simply move
       the computer's hard drive to another system to copy and analyze
       the sensitive data.</para>
 
     <para>Regardless of how an attacker may have come into possession of
-      a hard drive or powered-down computer, <application>GEOM Based Disk
-      Encryption (gbde)</application> can protect the data on the
-      computer's file systems against even highly-motivated attackers
-      with significant resources. Unlike cumbersome encryption methods
-      that encrypt only individual files, <application>gbde</application>
-      transparently encrypts entire file systems. No cleartext ever
-      touches the hard drive's platter.</para>
+      a hard drive or powered-down computer, both <application>GEOM
+      Based Disk Encryption (gbde)</application> and
+      <command>geli</command> cryptographic subsystems in &os; are able
+      to protect the data on the computer's file systems against even
+      highly-motivated attackers with significant resources. Unlike
+      cumbersome encryption methods that encrypt only individual files,
+      <command>gbde</command> and <command>geli</command> transparently
+      encrypt entire file systems. No cleartext ever touches the hard
+      drive's platter.</para>
 
     <sect2>
-      <title>Enabling gbde in the Kernel</title>
+      <title>Disk Encryption with <application>gbde</application></title>
 
       <procedure>
 	<step>
 	  <title>Become <username>root</username></title>
 
 	  <para>Configuring <application>gbde</application> requires
 	    super-user privileges.</para>
 
 	  <screen>&prompt.user; <userinput>su -</userinput>
 Password:</screen>
 	</step>
 
 	<step>
 	  <title>Verify the Operating System Version</title>
 
 	  <para>&man.gbde.4; requires FreeBSD 5.0 or higher.</para>
 
 	  <screen>&prompt.root; <userinput>uname -r</userinput>
 5.0-RELEASE</screen>
 	</step>
 
 	<step>
 	  <title>Add &man.gbde.4; Support to the Kernel Configuration File</title>
 
-	  <para>Using your favorite text editor, add the following
-	    line to your kernel configuration file:</para>
+	  <para>Add the following line to the kernel configuration
+	    file:</para>
 
 	  <para><literal>options GEOM_BDE</literal></para>
 
-	  <para>Configure, recompile, and install the FreeBSD kernel.
-	    This process is described in <xref
+	  <para>Rebuild the kernel as described in <xref
 	    linkend="kernelconfig">.</para>
 
 	  <para>Reboot into the new kernel.</para>
 	</step>
       </procedure>
-    </sect2>
 
-
-    <sect2>
+    <sect3>
       <title>Preparing the Encrypted Hard Drive</title>
 
       <para>The following example assumes that you are adding a new hard
 	drive to your system that will hold a single encrypted partition.
 	This partition will be mounted as <filename>/private</filename>.
 	<application>gbde</application> can also be used to encrypt
 	<filename>/home</filename> and <filename>/var/mail</filename>, but
 	this requires more complex instructions which exceed the scope of
 	this introduction.</para>
 
       <procedure>
 	<step>
 	  <title>Add the New Hard Drive</title>
 
 	  <para>Install the new drive to the system as explained in <xref
 	    linkend="disks-adding">. For the purposes of this example,
 	    a new hard drive partition has been added as
 	    <filename>/dev/ad4s1c</filename>. The
 	    <filename>/dev/ad0s1<replaceable>*</replaceable></filename>
 	    devices represent existing standard FreeBSD partitions on
 	    the example system.</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>Create a Directory to Hold gbde Lock Files</title>
 
 	  <screen>&prompt.root; <userinput>mkdir /etc/gbde</userinput></screen>
 
 	  <para>The <application>gbde</application> lock file contains
 	    information that <application>gbde</application> requires to
 	    access encrypted partitions. Without access to the lock file,
 	    <application>gbde</application> will not be able to decrypt
 	    the data contained in the encrypted partition without
 	    significant manual intervention which is not supported by the
 	    software. Each encrypted partition uses a separate lock
 	    file.</para>
 	</step>
 
 	<step>
 	  <title>Initialize the gbde Partition</title>
 
 	  <para>A <application>gbde</application> partition must be
 	    initialized before it can be used. This initialization needs to
 	    be performed only once:</para>
 
 	  <screen>&prompt.root; <userinput>gbde init /dev/ad4s1c -i -L /etc/gbde/ad4s1c</userinput></screen>
 
 	  <para>&man.gbde.8; will open your editor, permitting you to set
 	    various configuration options in a template. For use with UFS1
 	    or UFS2, set the sector_size to 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; will ask you twice to type the passphrase that
 	    should be used to secure the data. The passphrase must be the
 	    same both times. <application>gbde</application>'s ability to
 	    protect your data depends entirely on the quality of the
 	    passphrase that you choose.
 	  <footnote>
           <para>For tips on how to select a secure passphrase that is easy
 	    to remember, see the <ulink
 	    url="http://world.std.com/~reinhold/diceware.html">Diceware
 	    Passphrase</ulink> website.</para></footnote></para>
 
 	  <para>The <command>gbde init</command> command creates a lock
 	    file for your <application>gbde</application> partition that in
 	    this example is stored as
 	    <filename>/etc/gbde/ad4s1c</filename>.</para>
 
 	  <caution>
 	    <para><application>gbde</application> lock files
 	      <emphasis>must</emphasis> be backed up together with the
 	      contents of any encrypted partitions. While deleting a lock
 	      file alone cannot prevent a determined attacker from
 	      decrypting a <application>gbde</application> partition,
 	      without the lock file, the legitimate owner will be unable
 	      to access the data on the encrypted partition without a
 	      significant amount of work that is totally unsupported by
 	      &man.gbde.8; and its designer.</para>
 	  </caution>
 	</step>
 
 	<step>
 	  <title>Attach the Encrypted Partition to the Kernel</title>
 
 	  <screen>&prompt.root; <userinput>gbde attach /dev/ad4s1c -l /etc/gbde/ad4s1c</userinput></screen>
 
 	  <para> You will be asked to provide the passphrase that you
 	    selected during the initialization of the encrypted partition.
 	    The new encrypted device will show up in
 	    <filename>/dev</filename> as
 	    <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>Create a File System on the Encrypted Device</title>
 
 	  <para>Once the encrypted device has been attached to the kernel,
 	    you can create a file system on the device. To create a file
 	    system on the encrypted device, use &man.newfs.8;. Since it is
 	    much faster to initialize a new UFS2 file system than it is to
 	    initialize the old UFS1 file system, using &man.newfs.8; with
 	    the <option>-O2</option> option is recommended.</para>
 
 	  <note><para>The <option>-O2</option> option is the default
 	  with &os;&nbsp;5.1-RELEASE and later.</para></note>
 
 	  <screen>&prompt.root; <userinput>newfs -U -O2 /dev/ad4s1c.bde</userinput></screen>
 
 	  <note>
 	    <para>The &man.newfs.8; command must be performed on an
 	      attached <application>gbde</application> partition which
 	      is identified by a
 	      <filename><replaceable>*</replaceable>.bde</filename>
 	      extension to the device name.</para>
 	  </note>
 	</step>
 
 	<step>
 	  <title>Mount the Encrypted Partition</title>
 
 	  <para>Create a mount point for the encrypted file system.</para>
 
 	  <screen>&prompt.root; <userinput>mkdir /private</userinput></screen>
 
 	  <para>Mount the encrypted file system.</para>
 
 	  <screen>&prompt.root; <userinput>mount /dev/ad4s1c.bde /private</userinput></screen>
 	</step>
 
 	<step>
 	  <title>Verify That the Encrypted File System is Available</title>
 
 	  <para>The encrypted file system should now be visible to
 	    &man.df.1; and be available for use.</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>
+    </sect3>
 
-    <sect2>
+    <sect3>
       <title>Mounting Existing Encrypted File Systems</title>
 
       <para>After each boot, any encrypted file systems must be
 	re-attached to the kernel, checked for errors, and mounted, before
 	the file systems can be used. The required commands must be
 	executed as user <username>root</username>.</para>
 
       <procedure>
 	<step>
 	  <title>Attach the gbde Partition to the Kernel</title>
 
 	  <screen>&prompt.root; <userinput>gbde attach /dev/ad4s1c -l /etc/gbde/ad4s1c</userinput></screen>
 
 	  <para>You will be asked to provide the passphrase that you
-	    selected during initialization of the encrypted gbde
-	    partition.</para>
+	    selected during initialization of the encrypted
+	    <application>gbde</application> partition.</para>
 	</step>
 
 	<step>
 	  <title>Check the File System for Errors</title>
 
 	  <para>Since encrypted file systems cannot yet be listed in
 	    <filename>/etc/fstab</filename> for automatic mounting, the
 	    file systems must be checked for errors by running &man.fsck.8;
 	    manually before mounting.</para>
 
 	  <screen>&prompt.root; <userinput>fsck -p -t ffs /dev/ad4s1c.bde</userinput></screen>
 	</step>
 
 	<step>
 	  <title>Mount the Encrypted File System</title>
 
 	  <screen>&prompt.root; <userinput>mount /dev/ad4s1c.bde /private</userinput></screen>
 
 	  <para>The encrypted file system is now available for use.</para>
 	</step>
       </procedure>
 
-      <sect3>
+      <sect4>
 	<title>Automatically Mounting Encrypted Partitions</title>
 
 	<para>It is possible to create a script to automatically attach,
 	  check, and mount an encrypted partition, but for security reasons
 	  the script should not contain the &man.gbde.8; password. Instead,
 	  it is recommended that such scripts be run manually while
 	  providing the password via the console or &man.ssh.1;.</para>
-      </sect3>
-    </sect2>
 
-      <sect2>
+	<para>As of &os; 5.2-RELEASE, there is a new <filename>rc.d</filename> script
+	  provided.  Arguments for this script can be passed via
+	  &man.rc.conf.5;, for example:</para>
+
+	<screen>gbde_autoattach_all="YES"
+gbde_devices="ad4s1c"</screen>
+
+	<para>This will require that the <application>gbde</application>
+	  passphrase be entered at boot time.  After typing the correct
+	  passphrase, the <application>gbde</application> encrypted
+	  partition will be mounted automatically.  This can be very
+	  useful when using <application>gbde</application> on
+	  notebooks.</para>
+      </sect4>
+    </sect3>
+
+      <sect3>
 	<title>Cryptographic Protections Employed by gbde</title>
 
 	<para>&man.gbde.8; encrypts the sector payload using 128-bit AES in
 	  CBC mode.  Each sector on the disk is encrypted with a different
 	  AES key. For more information on <application>gbde</application>'s
 	  cryptographic design, including how the sector keys are derived
 	  from the user-supplied passphrase, see &man.gbde.4;.</para>
-      </sect2>
+      </sect3>
 
-      <sect2>
+      <sect3>
 	<title>Compatibility Issues</title>
 
 	<para>&man.sysinstall.8; is incompatible with
 	  <application>gbde</application>-encrypted devices. All
 	  <devicename><replaceable>*</replaceable>.bde</devicename> devices must be detached from the
 	  kernel before starting &man.sysinstall.8; or it will crash during
 	  its initial probing for devices. To detach the encrypted device
 	  used in our example, use the following command:</para>
 	<screen>&prompt.root; <userinput>gbde detach /dev/ad4s1c</userinput></screen>
 
       <para>Also note that, as &man.vinum.4; does not use the
 	&man.geom.4; subsystem, you cannot use
 	<application>gbde</application> with
 	<application>vinum</application> volumes.</para>
-      </sect2>
+      </sect3>
+
+    </sect2>
+
+    <sect2>
+      <sect2info>
+	<authorgroup>
+	  <author>
+	    <firstname>Daniel</firstname>
+	    <surname>Gerzo</surname>
+	    <contrib>Contributed by </contrib>
+	  </author>
+	</authorgroup>
+	<!-- Date of writing: 28 November 2005 -->
+      </sect2info>
+
+      <title>Disk Encryption with <command>geli</command></title>
+
+      <para>A new cryptographic GEOM class is available as of &os; 6.0 -
+	<command>geli</command>.  It is currently being developed by
+	&a.pjd;.  <command>Geli</command> is different to
+	<command>gbde</command>; it offers different features and uses
+	a different scheme for doing cryptographic work.</para>
+
+      <para>The most important features of &man.geli.8; are:</para>
+
+      <itemizedlist>
+	<listitem>
+	  <para>Utilizes the &man.crypto.9; framework &mdash; when
+	    cryptographic hardware is available, <command>geli</command>
+	    will use it automatically.</para>
+	</listitem>
+	<listitem>
+	  <para>Supports multiple cryptographic algorithms (currently
+	     AES, Blowfish, and 3DES).</para>
+	</listitem>
+	<listitem>
+	  <para>Allows the root partition to be encrypted.  The
+	    passphrase used to access the encrypted root partition will
+	    be requested during the system boot.</para>
+	</listitem>
+	<listitem>
+	  <para>Allows the use of two independent keys (e.g. a
+	    <quote>key</quote> and a <quote>company key</quote>).</para>
+	</listitem>
+	<listitem>
+	  <para><command>geli</command> is fast - performs simple
+	    sector-to-sector encryption.</para>
+	</listitem>
+	<listitem>
+	  <para>Allows backup and restore of Master Keys.  When a user
+	    has to destroy his keys, it will be possible to get access
+	    to the data again by restoring keys from the backup.</para>
+	</listitem>
+	<listitem>
+	  <para>Allows to attach a disk with a random, one-time key
+	    &mdash; useful for swap partitions and temporary file
+	    systems.</para>
+	</listitem>
+      </itemizedlist>
+
+      <para>More <command>geli</command> features can be found in the
+	&man.geli.8; manual page.</para>
+
+      <para>The next steps will describe how to enable support for
+	<command>geli</command> in the &os; kernel and will explain how
+	to create a new <command>geli</command> encryption provider.  At
+	the end it will be demonstrated how to create an encrypted swap
+	partition using features provided by <command>geli</command>.</para>
+
+      <para>In order to use <command>geli</command>, you must be running
+	&os; 6.0-RELEASE or later.  Super-user privileges will be
+	required since modifications to the kernel are necessary.</para>
+
+      <procedure>
+	<step>
+	  <title>Adding <command>geli</command> Support to the Kernel
+	    Configuration File</title>
+
+	  <para>Add the following lines to the kernel configuration
+	    file:</para>
+
+	  <screen>options GEOM_ELI
+device crypto</screen>
+
+	  <para>Rebuild the kernel as described in <xref
+	    linkend="kernelconfig">.</para>
+
+	  <para>Alternatively, the <command>geli</command> module can
+	    be loaded at boot time.  Add the following line to the
+	    <filename>/boot/loader.conf</filename>:</para>
+
+	  <para><literal>geom_eli_load="YES"</literal></para>
+
+	  <para>&man.geli.8; should now be supported by the kernel.</para>
+	</step>
+
+	<step>
+	  <title>Generating the Master Key</title>
+
+	  <para>The following example will describe how to generate a
+	    key file, which will be used as part of the Master Key for
+	    the encrypted provider mounted under
+	    <filename role="directory">/private</filename>.  The key
+	    file will provide some random data used to encrypt the
+	    Master Key.  The Master Key will be protected by a
+	    passphrase as well.  Provider's sector size will be 4kB big.
+	    Furthermore, the discussion will describe how to attach the
+	    <command>geli</command> provider, create a file system on
+	    it, how to mount it, how to work with it, and finally how to
+	    detach it.</para>
+
+	  <para>It is recommended to use a bigger sector size (like 4kB) for
+	    better performance.</para>
+
+	  <para>The Master Key will be protected with a passphrase and
+	    the data source for key file will be
+	    <filename>/dev/random</filename>.  The sector size of
+	    <filename>/dev/da2.eli</filename>, which we call provider,
+	    will be 4kB.</para> 
+
+	  <screen>&prompt.root; <userinput>dd if=/dev/random of=/root/da2.key bs=64 count=1</userinput>
+&prompt.root; <userinput>geli init -s 4096 -K /root/da2.key /dev/da2</userinput>
+Enter new passphrase:
+Reenter new passphrase:</screen>
+
+	  <para>It is not mandatory that both a passphrase and a key
+	    file are used; either method of securing the Master Key can
+	    be used in isolation.</para>
+
+	  <para>If key file is given as <quote>-</quote>, standard
+	    input will be used.  This example shows how more than one
+	    key file can be used.</para>
+
+	  <screen>&prompt.root; <userinput>cat keyfile1 keyfile2 keyfile3 | geli init -K - /dev/da2</userinput></screen>
+	</step>
+
+	<step>
+	  <title>Attaching the Provider with the generated Key</title>
+
+	  <screen>&prompt.root; <userinput>geli attach -k /root/da2.key /dev/da2</userinput>
+Enter passphrase:</screen>
 
+	  <para>The new plaintext device will be named
+	    <filename>/dev/<replaceable>da2</replaceable>.eli</filename>.</para>
+
+	  <screen>&prompt.root; <userinput>ls /dev/da2*</userinput>
+/dev/da2  /dev/da2.eli</screen>
+	</step>
+
+	<step>
+	  <title>Creating the new File System</title>
+
+	  <screen>&prompt.root; <userinput>dd if=/dev/random of=/dev/da2.eli bs=1m</userinput>
+&prompt.root; <userinput>newfs /dev/da2.eli</userinput>
+&prompt.root; <userinput>mount /dev/da2.eli /private</userinput></screen>
+
+	<para>The encrypted file system should be visible to &man.df.1;
+	  and be available for use now.</para>
+
+	  <screen>&prompt.root; <userinput>df -H</userinput>
+Filesystem     Size   Used  Avail Capacity  Mounted on
+/dev/ad0s1a    248M    89M   139M    38%    /
+/devfs         1.0K   1.0K     0B   100%    /dev
+/dev/ad0s1f    7.7G   2.3G   4.9G    32%    /usr
+/dev/ad0s1d    989M   1.5M   909M     0%    /tmp
+/dev/ad0s1e    3.9G   1.3G   2.3G    35%    /var
+/dev/da2.eli   150G   4.1K   138G     0%    /private</screen>
+
+	</step>
+
+	<step>
+	  <title>Unmounting and Detaching the Provider</title>
+
+	  <para>Once the work on the encrypted partition is done, and
+	    the <filename role="directory">/private</filename> partition
+	    is no longer needed, it is prudent to consider unmounting
+	    and detaching the <command>geli</command> encrypted
+	    partition from the kernel.</para>
+
+	  <screen>&prompt.root; <userinput>umount /private</userinput>
+&prompt.root; <userinput>geli detach da2.eli</userinput></screen>
+	</step>
+      </procedure>
+
+      <para>More information about the use of &man.geli.8; can be
+        found in the manual page.</para>
+
+      <sect3>
+	<title>Encrypting a Swap Partition</title>
+
+	<para>The following example demonstrates how to create a
+	  <command>geli</command> encrypted swap partition.</para>
+
+	<screen>&prompt.root; <userinput>dd if=/dev/random of=/dev/ad0s1b bs=1m</userinput>
+&prompt.root; <userinput>geli onetime -d -a 3des ad0s1b</userinput>
+&prompt.root; <userinput>swapon /dev/ad0s1b.eli</userinput></screen>
+      </sect3>
+
+      <sect3>
+	<title>Using the <filename>geli</filename> <filename>rc.d</filename> Script</title>
+
+	<para><command>geli</command> comes with a <filename>rc.d</filename> script which
+	  can be used to simplify the usage of <command>geli</command>.
+	  An example of configuring <command>geli</command> through
+	  &man.rc.conf.5; follows:</para>
+
+	<screen>geli_devices="da2"
+geli_da2_flags="-p -k /root/da2.key"</screen>
+
+	<para>This will configure <filename>/dev/da2</filename> as a
+	  <command>geli</command> provider of which the Master Key file
+	  is located in <filename>/root/da2.key</filename>, and
+	  <command>geli</command> will not use a passphrase when
+	  attaching the provider (note that this can only be used if -P
+	  was given during the <command>geli</command> init phase).  The
+	  system will detach the <command>geli</command> provider from
+	  the kernel before the system shuts down.</para>
+
+	<para>More information about configuring <filename>rc.d</filename> is provided in the
+	  <link linkend="configtuning-rcd">rc.d</link> section of the
+	  Handbook.</para>
+      </sect3>
+    </sect2>	
   </sect1>
 </chapter>
 
 <!--
      Local Variables:
      mode: sgml
      sgml-declaration: "../chapter.decl"
      sgml-indent-data: t
      sgml-omittag: nil
      sgml-always-quote-attributes: t
      sgml-parent-document: ("../book.sgml" "part" "chapter")
      End:
 -->
diff --git a/zh_TW.Big5/books/handbook/geom/chapter.sgml b/zh_TW.Big5/books/handbook/geom/chapter.sgml
index b8909b3eb9..1e6d087bde 100644
--- a/zh_TW.Big5/books/handbook/geom/chapter.sgml
+++ b/zh_TW.Big5/books/handbook/geom/chapter.sgml
@@ -1,402 +1,378 @@
 <!--
      The FreeBSD Documentation Project
      $FreeBSD$
 
 -->
 
 <chapter id="GEOM">
   <chapterinfo>
     <authorgroup>
       <author>
 	<firstname>Tom</firstname>
 	<surname>Rhodes</surname>
 	<contrib>Written by </contrib>
       </author>
     </authorgroup>
   </chapterinfo>
 
   <title>GEOM: Modular Disk Transformation Framework</title>
 
   <sect1 id="GEOM-synopsis">
-    <title>Synopsis</title>
+    <title>·§­z</title>
 
     <indexterm>
       <primary>GEOM</primary>
     </indexterm>
     <indexterm>
       <primary>GEOM Disk Framework</primary>
       <see>GEOM</see>
     </indexterm>
 
 	  <para>¥»³¹²[»\¦p¦ó¦b &os; ªº GEOM ¬[ºc¤U¨Ï¥ÎºÏºÐ¡A
 	  ¥]§t¥Î¨Ó³]©w´XºØ±`¥Îªº <acronym 
 	  role="Redundant Array of Inexpensive Disks¡AºÏºÐ°}¦C¨t²Î">RAID</acronym>
 	  ªº±±¨î¤u¨ã¡C¥»³¹¤£·|²`¤J±´°Q GEOM ¦p¦ó³B²z©³¼hªº I/O¡A³oÃþ¸ê°T½Ð°Ñ¦Ò 
 	  &man.geom.4; ¤Î¬ÛÃöªº SEE ALSO ³¡¥÷¡C¥»³¹¤]«D <acronym>RAID</acronym>
 	  ³]©w«ü«n¡A¦b³o¸Ì¥u·|°Q½×¥Ø«e GEOM ¤ä´©ªº <acronym>RAID</acronym> ¼Ò¦¡¡C
 	  </para>
 
-	  <para>¾\Ū¥»³¹«á¡A±z·|ª¾¹D³o¨Ç¸ê°T¡G</para>
+	  <para>Ū§¹³o³¹¡A±z±N¤F¸Ñ¡J</para>
 	  <itemizedlist>
 	  <listitem>
 	  <para>³z¹L GEOM ¥i¤ä´©­þ¨Ç¼Ò¦¡ªº <acronym>RAID</acronym>¡C</para>
 	  </listitem>
 
 	  <listitem>
 	  <para>¦p¦ó¨Ï¥Î°ò¥»¤u¨ã¨Ó°t¸m¡B¾Þ§@¡BºûÅ@¤£¦P¼Ò¦¡ªº
 	  <acronym>RAID</acronym>¡C</para>
 	  </listitem>
 
 	  <listitem>
-	  <para>¦p¦ó³z¹L GEOM ¨Ó§¹¦¨Ãè®g (mirror)¡B¤À´²³sµ² (stripe)¡B¥[±K (encryp) 
+	  <para>¦p¦ó³z¹L GEOM ¨Ó§¹¦¨Ãè®g(mirror)¡B¤À´²³sµ²(stripe)¡B¥[±K(encrypt) 
 		¡B»·ºÝ³s±µºÏºÐµ¥¡C</para>
 	  </listitem>
 
 	  <listitem>
 	  <para>·í GEOM ¬[ºc¤UªººÏºÐµo¥Í°ÝÃD¡A¦p¦ó±Æ°£¡C</para>
 	  </listitem>
 
 	  </itemizedlist>
 
-    <para>Before reading this chapter, you should:</para>
-	<para>¦b¶}©l¤§«e¡A½Ð±z½T¥ô¤U¦C­I´ºª¾ÃÑ¡G</para>
+	<para>¦b¶}©l¾\Ū³o³¹¤§«e¡A±z»Ý­n¡J</para>
 
 
     <itemizedlist>
       <listitem>
-		<para>¤F¸Ñ &os; ¦p¦ó¬Ý«ÝºÏºÐ (<xref linkend="disks">) ¡C</para>
+		<para>¤F¸Ñ &os; ¦p¦ó¬Ý«ÝºÏºÐ(<xref linkend="disks">) ¡C</para>
 	  </listitem>
 
       <listitem>
 	<para>ª¾¹D¦p¦ó³]©w¡B¦w¸Ë·sªº &os; ®Ö¤ß 
 		(<xref linkend="kernelconfig">) ¡C</para>
       </listitem>
     </itemizedlist>
   </sect1>
 
   <sect1 id="GEOM-intro">
     <title>GEOM ¾É½×</title>
 
-	<para>GEOM ³z¹L privoder (§Y <dilename role="directory">/dev/</filename>
-	¤Uªº¯S®í¸Ë¸mÀÉ®×) ¨Ó¾Þ±± classes (¦p Master Boot Records¡B
+	<para>GEOM ³z¹L privoder(§Y <filename role="directory">/dev/</filename>
+	¤Uªº¯S®í¸Ë¸mÀÉ®×) ¨Ó¾Þ±± classes(¦p Master Boot Records¡B
 	<acronym>BSD</acronym> labels µ¥) ¡CGEOM ¤ä´©¦hºØ³nÅé 
 	<acronym>RAID</acronym> °t¸m¡A³z¹L GEOM ¦s¨ú®É¡A
 	§@·~¨t²Î©MÀ³¥Îµ{¦¡¤£·|·NÃѨì GEOM ¦s¦b¡C</para>
   </sect1>
 
   <sect1 id="GEOM-striping">
   <sect1info>
     <authorgroup>
       <author>
 	<firstname>Tom</firstname>
 	<surname>Rhodes</surname>
 	<contrib>Written by </contrib>
       </author>
       <author>
 	<firstname>Murray</firstname>
 	<surname>Stokely</surname>
       </author>
     </authorgroup>
   </sect1info>
 
-    <title>RAID0 - ¤À´²³sµ² (striping)</title>
+    <title>RAID0 - ¤À´²³sµ²(striping)</title>
 
     <indexterm>
       <primary>GEOM</primary>
     </indexterm>
     <indexterm>
-      <primary>¤À´²³sµ² (Striping)</primary>
+      <primary>¤À´²³sµ²(Striping)</primary>
     </indexterm>
 
-	<para>¤À´²³sµ² (striping) ¥i¥Î¨Ó³sµ²¦h­ÓºÏºÐ¦¨¬°¤@¤j¶ôªÅ¶¡¡C
+	<para>¤À´²³sµ²(striping) ¥i¥Î¨Ó³sµ²¦h­ÓºÏºÐ¦¨¬°¤@¤j¶ôªÅ¶¡¡C
 	«Ü¦h®É­ÔµwÅé±±¨î¾¹¥i¥H§¹¦¨³o¥ó¨Æ¡A¤£¹L GEOM ¤]´£¨Ñ¤F³nÅ骩¥»ªº 
-	<acronym>RAID</acronym>0¡A¤]´N¬O¤À´²³sµ² (striping)¡C</para>
+	<acronym>RAID</acronym>0¡A¤]´N¬O¤À´²³sµ²(striping)¡C</para>
 
 	<para>¦b <acronym>RAID</acronym>0 ¸Ì¡A¸ê®Æ·|³Q¤Á¤À¦¨«Ü¦h¶ô¡A
 	¦A¤À´²¼g¤J¥þ³¡ªººÏºÐ¡C¨Ò¦p­n¼g¤J 256k ªº¸ê®Æ¨ì³æ¤@ºÏºÐ¡A¦b
 	¥|­ÓºÏºÐªº <acronym>RAID</acronym>0 ¤¤¥i¦P®É¼g¤J 64k ¨ì¥|­ÓºÏºÐ¸Ì¡A
 	¦]¦¹¥i¤j´T´£¤É I/O ®Ä¯à¡C¦pªG¨Ï¥Î§ó¦hªººÏºÐ±±¨î¾¹¡A
 	I/O ®Ä¯à¥i¦A´£¤É¡C</para>
 
 	<para>¥Ñ©óŪ©Î¼g®É·|¦P¨B¥æ¿ù¹ï³\¦hºÏºÐ¶i¦æ I/O ³B²z¡A¦]¦¹ 
-	<acronym>RAID</acronym>0 ªº¨C­ÓºÏºÐ¥²»Ý¤j¤p¤@¼Ë¡C
+	<acronym>RAID</acronym>0 ªº¨C­ÓºÏºÐ¥²¶·¤j¤p¤@¼Ë¡C
 
       <mediaobject>
         <imageobject>
           <imagedata fileref="geom/striping" align="center">
         </imageobject>
 
         <textobject>
           <phrase>Disk Striping Illustration</phrase>
         </textobject>
       </mediaobject>
 
     <procedure>
-      <title>¥Î¥¼®æ¦¡¤Æªº ATA ºÏºÐ¨Ó«Ø¥ß¤À´²³sµ²</title>
+      <title>¥Î¥¼®æ¦¡¤Æªº ATA ºÏºÐ¨Ó«Ø¥ß¤À´²³sµ²(striping)</title>
 
       <step><para>¸ü¤J <filename>geom_stripe</filename>
-        ®Ö¤ß¼Ò²Õ¡G</para>
+         kernel module¡G</para>
 
     <screen>&prompt.root; <userinput>kldload geom_stripe.ko</userinput></screen>
 	</step>
 
-      <step><para>½T©w±¾¸üÂI (mount point) ¦s¦b¡C
-	  ¦pªG·Q¥Î¤À´²³sµ²ªºªÅ¶¡°µ¬°®Ú¥Ø¿ý (root partition¡A§Y /)¡A
+      <step><para>½T©w±¾¸üÂI(mount point)¦s¦b¡C
+	  ¦pªG·Q¥Î¤À´²³sµ²(striping)ªºªÅ¶¡°µ¬°®Ú¥Ø¿ý(root partition¡A§Y <filename role="directory">/</filename> )¡A
 	  «h¥ý¥Î­Ó¼È®Éªº±¾¸üÂI¡A¦p 
 	  <filename role="directory">/mnt</filename>¡G</para>
 
         <screen>&prompt.root; <userinput>mkdir /mnt</userinput></screen>
       </step>
 
-      <step><para>½T»{­n¥Î¨Ó¤À´²³sµ²ªº¸Ë¸m¦WºÙ¡A±µµÛ«Ø·s·sªº¤À´²³sµ²¸Ë¸m¡C
-	  ¨Ò¦p¤U­±ªº«ü¥O·|¤À´²³sµ²¨â­Ó¥¼¨Ï¥Î¡B©|¥¼¤À°Ïªº <acronym>ATA</acronym>
-	  ºÏºÐ (<filename>/dev/ad2</filename> ©M 
+
+<step><para>½T»{­n¥Î¨Ó¤À´²³sµ²(striping)ªº¸Ë¸m¦WºÙ¡A±µµÛ«Ø¥ß·sªº¤À´²³sµ²(striping)¡C
+	  ¨Ò¦p¤U­±ªº«ü¥O·|¤À´²³sµ²(striping)¨â­Ó¥¼¨Ï¥Î¡B©|¥¼¤À³Î°Ïªº <acronym>ATA</acronym>
+	  ºÏºÐ(<filename>/dev/ad2</filename> ©M 
 	  <filename>/dev/ad3</filename>) ¡G</para>
         <screen>&prompt.root; <userinput>
 		gstripe label -v st0 /dev/ad2 /dev/ad3</userinput></screen>
 
         <screen>&prompt.root; <userinput>gstripe label -v st0 /dev/ad2 /dev/ad3</userinput></screen>
 
 <!-- 
     <para>A message should be returned explaining that meta data has
       been stored on the devices.
 XXX: What message?  Put it inside the screen output above.
 -->
       </step>
 
-      <step><para>¥Î¤U­±ªº«ü¥O¨Ó«Ø¥ß¤À°Ïªí (partition table)¡G</para>
+      <step><para>¥Î¤U­±ªº«ü¥O¨Ó«Ø¥ß¤À³Î°Ïªí(partition table)¡G</para>
 
         <screen>&prompt.root; <userinput>bsdlabel -wB /dev/stripe/st0</userinput></screen>
 
       </step>
 
-      <step><para>°£¤F¥ý«e«Ø¥ßªº <devicename>st0</devices> ¡A³o­Ó¨BÆJÁÙ·|¦b
+      <step><para>°£¤F¥ý«e«Ø¥ßªº <devicename>st0</devicename> ¡A³o­Ó¨BÆJÁÙ·|¦b
 	  <filename role="directory">/dev/stripe</filename> ¤U·s¼W¨â­Ó¸Ë¸m¡G
 	  <devicename>st0a</devicename> ©M <devicename>st0c</devicename>¡C
 	  §Q¥Î <command>newfs</command> «ü¥O¥i¥H¦b 
 	  <devicename>st0a</devicename> «Ø¥ßÀɮרt²Î¡G
 
       <screen>&prompt.root; <userinput>newfs -U /dev/stripe/st0a</userinput></screen>
 
       <para>¿Ã¹õ¤W·|¦³¤@°ï¼Æ¦r¶ÉÂm¦Ó¹L¡A´X¬íÄÁ«á´N·|§¹¦¨¡C¦¹®ÉªÅ¶¡¤w«Ø¥ß¡A
 	  ¥i¥Î¨Ó±¾¸ü¨Ï¥Î¤F¡C</para>
     </step>
   </procedure>
 
-  <para>¤U­±«ü¥O¥i¥Î¨Ó¤â°Ê±¾¸ü¤À´²³sµ²ªÅ¶¡¡G</para>
+  <para>¤U­±«ü¥O¥i¥Î¨Ó¤â°Ê±¾¸ü¤À´²³sµ²(striping)ªÅ¶¡¡G</para>
 
   <screen>&prompt.root; <userinput>mount /dev/stripe/st0a /mnt</userinput></screen>
 
   <para>¦pªG­n¦b¶}¾÷®É¦Û°Ê±¾¸ü¡A¦b <filename>/etc/fstab</filename> 
   ¥[¤J³o¶ôªÅ¶¡ªº¸ê°T¡G</para>
 
   <screen>&prompt.root; <userinput>echo "/dev/stripe/st0a /mnt ufs rw 2 2" \</userinput>
     <userinput>&gt;&gt; /etc/fstab</userinput></screen>
 
-  <para>¦Ó <filename>geom</filename> ®Ö¤ß¼Ò²Õ¥²»Ý¦b¨t²Îªì©l¤Æ®É¦Û°Ê¸ü¤J¡A
-  ¦]¦¹¦b </filename>/boot/lodaer.conf</filename> ¥[¤J¤@¦æ¡G</para>
+  <para>¦Ó <filename>geom</filename>  kernel module ¥²¶·¦b¨t²Îªì©l¤Æ®É¦Û°Ê¸ü¤J¡A
+  ¦]¦¹¦b <filename>/boot/lodaer.conf</filename> ¥[¤J¤@¦æ¡G</para>
 
   <screen>&prompt.root; <userinput>echo 'geom_stripe_load="YES"' &gt;&gt; /boot/loader.conf</userinput></screen>
 
   </sect1>
 
   <sect1 id="GEOM-mirror">
-    <title>RAID1 - Mirroring</title>
+    <title>RAID1 - Ãè®g(Mirroring)</title>
 
     <indexterm>
       <primary>GEOM</primary>
     </indexterm>
     <indexterm>
-      <primary>Disk Mirroring</primary>
+      <primary>ºÏºÐÃè®g(Disk Mirroring)</primary>
     </indexterm>
 
-    <para>Mirroring is a technology used by many corporations and home
-      users to back up data without interruption.  When a mirror exists,
-      it simply means that diskB replicates diskA.  Or, perhaps diskC+D
-      replicates diskA+B.  Regardless of the disk configuration, the
-      important aspect is that information on one disk or partition is
-      being replicated.  Later, that information could be more easily
-      restored, backed up without causing service or access
-      interruption, and even be physically stored in a data
-      safe.</para>
-
-    <para>To begin, ensure the system has two disk drives of equal size,
-      this exercise assumes they are direct access (&man.da.4;)
-      <acronym>SCSI</acronym> disks.</para>
-
-    <para>Begin by installing &os; on the first disk with only two
-      partitions.  One should be a swap partition, double the
-      <acronym>RAM</acronym> size and all remaining space devoted to
-      the root (<filename role="directory">/</filename>) file system.
-      It is possible to have separate partitions for other mount points;
-      however, this will increase the difficulty level ten fold due to
-      manual alteration of the &man.bsdlabel.8; and &man.fdisk.8;
-      settings.</para>
-
-    <para>Reboot and wait for the system to fully initialize.  Once this
-      process has completed, log in as the <username>root</username>
-      user.</para>
-
-    <para>Create the <filename>/dev/mirror/gm</filename> device and link
-      it with <filename>/dev/da1</filename>:</para>
+    <para>³\¦h¥ø·~©Î­Ó¤H¥Î¤á¥ÎÃè®g(mirroring) ¨Ó¤£¤¤Â_¨t²Î¶i¦æ³Æ¥÷¡C
+	Ãè®g²³æ¨Ó»¡´N¬O¦b B ºÏºÐ¤W­«ÂФ@¥÷ A ºÏºÐªº¸ê®Æ¡A
+	©ÎªÌ C+D ºÏºÐ­«ÂÐ A+B ºÏºÐªº¸ê®Æ¡C¤£½×³]©w¦p¦ó¡A
+	³Ì­«­nªº¬O©Ò¦³ºÏºÐ©Î¤À³Î°Ï(partition) ¤Wªº¸ê®Æ³£·|³Q½Æ»s¡A
+	¤§«á¥i¦b¤£¤¤Â_ªA°Èªº±¡ªp¤U´_­ì¡B³Æ¥÷¸ê®Æ¡A¨ÏÀx¦sªº¸ê®Æ§ó¦w¥þ¡C
+
+    <para>¶}©l¤§«e¡A½Ð¥ý½T©w¨t²Î¤W¦³¨â­Ó®e¶q¬Û¦PªººÏºÐ¡A
+	«á­±ªº½d¨Ò°²³]³o¨âÁûºÏºÐ¬O direct access(&man.da.4;)
+      <acronym>SCSI</acronym> ºÏºÐ¡C</para>
+
+    <para>­º¥ý§Ú­Ì°²³] &os; ¦w¸Ë¦b²Ä¤@­ÓºÏºÐ¤W¡A¥B¥u¦³¨â­Ó¤À³Î°Ï(partition)¡C
+	¨ä¤¤¤@­Ó¬O¥æ´«¤À³Î°Ï(swap partition¡A¤j¤p¬° <acronym>RAM</acronym>
+	ªº¨â­¿)¡A¦Ó³Ñ¤Uªº¥þ¥Î©ó®Ú¥Ø¿ý(§Y <filename role="directory">/</filename>¡A
+	root file system)¡C·íµM­n¦b¤£¦P±¾¸üÂI(mount point) ¤Á¥X§ó¦h¤À³Î°Ï
+	(partition) ¤]¥i¥H¡A¤£¹LÃø«×·|¤j´T´£¤É¡A¦]¬°¥²¶·¤â°Ê¾Þ§@ &man.bsdlabel.8;
+	©M &man.fdisk.8; ¤u¨ã¡C
+
+    <para>­«¶}¾÷¨Ãµ¥¨ì¨t²Î§¹¥þªì©l¤Æ§¹²¦¡A¥Î <username>root</username>
+	µn¤J¡C</para>
+
+    <para>«Ø¥ß <filename>/dev/mirror/gm</filename> ¸Ë¸m¨Ã¥H
+       <filename>/dev/da1</filename> ³sµ²¡G</para>
 
     <screen>&prompt.root; <userinput>gmirror label -vnb round-robin gm0 /dev/da1</userinput></screen>
 
-    <para>The system should respond with:</para>
+    <para>³o®É¨t²ÎÀ³¸Ó·|¦^À³¡G</para>
     <screen>
 Metadata value stored on /dev/da1.
 Done.</screen>
 
-    <para>Initialize GEOM, this will load the
-      <filename>/boot/kernel/geom_mirror.ko</filename> kernel
-      module:</para>
+    <para>ªì©l¤Æ GEOM¡A³o°Ê§@·|¦Û°Ê¸ü¤J
+      <filename>/boot/kernel/geom_mirror.ko</filename>  kernel module¡G</para>
 
     <screen>&prompt.root; <userinput>gmirror load</userinput></screen>
 
     <note>
-      <para>This command should have created the
-	<devicename>gm0</devicename>, device node under the
-	<filename role="directory">/dev/mirror</filename>
-	directory.</para>
+      <para>³o°Ê§@À³¸Ó·|¦b <filename role="directory">/dev/mirror</filename>
+	  ¤U«Ø¥ß <devicename>gm0</devicename> ¸Ë¸mµ²ÂI(device node)¡C</para>
     </note>
 
-    <para>Install a generic <command>fdisk</command> label and boot code
-      to newly created <devicename>gm0</devicename> device:</para>
+	<para>¦b³o­Ó·s«Øªº <devicename>gm0</devicename> ¸Ë¸m¤W¦w¸m¤@¯ëªº
+	<command>fdisk</command> label ©M¶}¾÷ºÏ°Ï¡G</para>
 
     <screen>&prompt.root; <userinput>fdisk -vBI /dev/mirror/gm0</userinput></screen>
 
-    <para>Now install generic <command>bsdlabel</command>
-      information:</para>
+    <para>±µµÛ¦w¸m <command>bsdlabel</command> ¸ê°T¡G</para>
 
     <screen>&prompt.root; <userinput>bsdlabel -wB /dev/mirror/gm0s1</userinput></screen>
 
     <note>
-      <para>If multiple slices and partitions exist, the flags for the
-	previous two commands will require alteration.  They must match
-	the slice and partition size of the other disk.</para>
+      <para>¦pªG¦s¦b¦h­Ó slice ©M¤À³Î°Ï(partition)¡A
+	  °O±o­×§ï¤W¨â«ü¥Oªº°Ñ¼Æ¡A¥B¥t¤@­ÓºÏºÐ¤Wªº slice ©M¤À³Î°Ï(partition)
+	  ¤j¤p¥²¶·¬Û¦P¡C</para>
     </note>
 
-    <para>Use the &man.newfs.8; utility to create a default file
-      system on the <devicename>gm0s1a</devicename> device node:</para>
+    <para>¥Î &man.newfs.8; ¤u¨ã¦b <devicename>gm0s1a</devicename> 
+	¸Ë¸mµ²ÂI«Ø¥ß¹w³]ªºÀɮרt²Î¡G</para>
 
     <screen>&prompt.root; <userinput>newfs -U /dev/mirror/gm0s1a</userinput></screen>
 
-    <para>This should have caused the system to spit out some
-      information and a bunch of numbers.  This is good.  Examine the
-      screen for any error messages and mount the device to the
-      <filename role="directory">/mnt</filename> mount point:</para>
+    <para>¨t²Î·|¦L¥X³\¦h¸ê°T©M¤@¤j°ï¼Æ¦r¡A³o¬O¥¿±`ªº¡C
+	½T»{¬O§_¦³»{¦ó¿ù»~¡A±µµÛ´N¥i¥H±N³o­Ó¸Ë¸m±¾¸ü¨ì
+      <filename role="directory">/mnt</filename> ±¾¸üÂI(mount mount)¡G</para>
 
     <screen>&prompt.root; <userinput>mount /dev/mirror/gm0s1a /mnt</userinput></screen>
 
-    <para>Now move all data from the boot disk over to this new file
-      system.  This example uses the &man.dump.8; and &man.restore.8;
-      commands; however, &man.dd.1; would also work with this
-      scenario.</para>
+    <para>±µµÛ±N­ì¥»¶}¾÷ºÏºÐªº¸ê®Æ·h²¾¨ì·sªºÀɮרt²Î
+	 (<filename role="directory">/mnt</filename>)¡C½d¨Ò¬O¥Î
+      &man.dump.8; ©M &man.restore.8; ¡A¤£¹L¥Î &man.dd.1; ¤]¥i¥H¡C</para>
 
-    <screen>&prompt.root; <userinput>dump -L -0 -f- / |(cd /mnt && restore -r -v -f-)</userinput></screen>
+	<screen>&prompt.root; <userinput>dump -L -0 -f- / |(cd /mnt &amp;&amp; restore -r -v -f-)</userinput></screen>
 
-    <para>This must be done for each file system.  Simply place the
-      appropriate file system in the correct location when running the
-      aforementioned command.</para>
+    <para>°õ¦æ¤W­z«ü¥O®É¡A¥u­n±N«ê·íªºÀɮרt²Î±¾¦b¥¿½Tªº¦ì¸m¡AÀ³¸Ó´N¯à¦¨¥\¡C
+	</para>
 
-    <para>Now edit the replicated <filename>/mnt/etc/fstab</filename>
-      file and remove or comment out the swap file
+    <para>±µµÛ½s¿è <filename>/mnt/etc/fstab</filename>
+	ÀɱN swap file ¨º¦æ²¾°£©Îµù¸Ñ°_¨Ó¡C
       <footnote>
-	<para>It should be noted that commenting out the swap file entry
-	in <filename>fstab</filename> will most likely require you to
-	re-establish a different way of enabling swap space.  Please
-	refer to <xref linkend="adding-swap-space"> for more
-	information.</para>
-      </footnote>.  Change the other file system information to use the
-      new disk.  See the following example:</para>
+	<para>½Ðª`·N¡A±N <filename>fstab</filename> ªº swap file 
+	¨º¦æµù¸Ñ°_¨Ó¡A³q±`ªí¥Ü¡G±z±o¥Î§Oªº¤èªk¨Ó­««Ø swap¡C¸Ô±¡½Ð°Ñ¦Ò
+	<xref linkend="adding-swap-space">¡C</para>
+      </footnote>½Ð°Ñ¦Ò¤U­±½d¨Ò¡A¨Ã®Ú¾Ú·sºÏºÐ­×§ï¨ä¥¦ªºÀɮרt²Î¸ê°T¡G</para>
 
     <programlisting># Device                Mountpoint      FStype  Options         Dump    Pass#
 #/dev/da0s2b             none            swap    sw              0       0
 /dev/mirror/gm0s1a       /               ufs     rw              1       1</programlisting>
 
-    <para>Now create a <filename>boot.conf</filename> file on both the
-      current and new root partitions.  This file will
-      <quote>help</quote> the system <acronym>BIOS</acronym>
-      boot the correct drive:</para>
+    <para>¦b¥Ø«eªº®Ú¥Ø¿ý¤Î·sªº®Ú¥Ø¿ý«Ø¥ß <filename>boot.conf</filename> ÀɮסA
+	³o­ÓÀÉ®×¥i¥H¡yÀ°§U¡z¨t²Î <acronym>BIOS</acronym> ¶}¾÷¡G</para>
 
     <screen>&prompt.root; <userinput>echo "1:da(1,a)/boot/loader" &gt; /boot.config</userinput></screen>
 
     <screen>&prompt.root; <userinput>echo "1:da(1,a)/boot/loader" &gt; /mnt/boot.config</userinput></screen>
 
     <note>
-      <para>We have placed it on both root partitions to ensure proper
-        boot up.  If for some reason the system cannot read from the
-	new root partition, a failsafe is available.</para>
+      <para>¦b¨â­Ó®Ú¥Ø¿ý¤W³£·s¼WÀɮ׬O¬°¤F¦w¥þ°_¨£¡A
+	  ¦pªG¦]¬°¬Y¨Ç­ì¦]·sªº®Ú¥Ø¿ýµLªk¶}¾÷¡A¦Ü¤ÖÁÙ¥i¥Î­ì¥»ªº®Ú¥Ø¿ý¡C</para>
     </note>
 
-    <para>Now add the following line to the new
-      <filename>/boot/loader.conf</filename>:</para>
+    <para>±µµÛ¦b <filename>/boot/loader.conf</filename> ·s¼W¨â¦æ¡G</para> 
 
     <screen>&prompt.root; <userinput>echo 'geom_mirror_load="YES"' &gt;&gt; /mnt/boot/loader.conf</userinput></screen>
 
-    <para>This will instruct &man.loader.8; utility to load the
-      <filename>geom_mirror.ko</filename> module during system
-      initialization.</para>
+    <para>³o·|«ü¥Ü &man.loader.8; ¦b¶}¾÷®É¸ü¤J 
+  	<filename>geom_mirror.ko</filename>  kernel module¡C</para>
 
-    <para>Reboot the system:</para>
+    <para>­«¶}¾÷¡G</para>
 
     <screen>&prompt.root; <userinput>shutdown -r now</userinput></screen>
 
-    <para>If all has gone well, the system should have booted from the
-      <devicename>gm0s1a</devicename> device and a <command>login</command>
-      prompt should be waiting.  If something went wrong, see review
-      the forthcoming troubleshooting section.  Now add the
-      <devicename>da0</devicename> disk to <devicename>gm0</devicename>
-      device:</para>
+    <para>¦pªG¤@¤Á¶¶§Q¡A¨t²ÎÀ³¸Ó·|±q <devicename>gm0s1a</devicename> ¸Ë¸m¶}¾÷¡A
+	±µ¤U¨Ó¥X²{ <command>login</command> ´£¥Üµe­±¡C¦pªG¥X¿ù¤F¡A
+	½Ð°Ñ¾\¤U­± Troubleshooting ¨º¤@¸`¡C ²{¦b¥i¥H±N 
+	<devicename>da0</devicename> ºÏºÐ¥[¤J <devicename>gm0</devicename>
+	¸Ë¸m¡G</para>
 
     <screen>&prompt.root; <userinput>gmirror configure -a gm0</userinput>
 &prompt.root; <userinput>gmirror insert gm0 /dev/da0</userinput></screen>
 
-    <para>The <option>-a</option> flag tells &man.gmirror.8; to use
-      automatic synchronization; i.e., mirror the disk writes
-      automatically.  The manual page explains how to rebuild and
-      replace disks, although it uses <devicename>data</devicename>
-      in place of <devicename>gm0</devicename>.</para>
+    <para>¨ä¤¤ <option>-a</option> ºX¼Ð§i¶D &man.gmirror.8; 
+	  ¨Ï¥Î¡u¦Û°Ê¦P¨B(automatic synchronization)¡v¡A¨Ò¦p¦Û°Ê¦P¨B¼g¤JºÏºÐªº°Ê§@¡C
+	  manual »¡©ú¤F¦p¦ó­««Ø¡B¨ú¥NºÏºÐµ¥¡A¤£¹L manual ¸Ìªº½d¨Ò¬O¥Î
+      <devicename>data</devicename> ¦Ó¤£¬O <devicename>gm0</devicename>¡C</para>
 
     <sect2>
       <title>Troubleshooting</title>
 
       <sect3>
-	<title>System refuses to boot</title>
+	<title>¨t²ÎµLªk¶}¾÷</title>
 
-	<para>If the system boots up to a prompt similar to:</para>
+	<para>¦pªG¶}¾÷´£¥ÜÃþ¦ü³o¼Ë¡G</para>
 
 	<programlisting>ffs_mountroot: can't find rootvp
 Root mount failed: 6
 mountroot></programlisting>
 
-	<para>Reboot the machine using the power or reset button.  At
-	  the boot menu, select option six (6).  This will drop the
-	  system to a &man.loader.8; prompt.  Load the kernel module
-	  manually:</para>
+	<para>½Ð¥Î¾÷¾¹­±ªO¤Wªº Power «ö¶s©Î reset «ö¶s¨Ó­«¶}¾÷¡A¨Ã¦b¶}¾÷¿ï³æ¿ï (6)¡A
+	³o¼Ë¤l¡A¨t²Î´N·|¶i¤J &man.loader.8; 
+	¥æ½Í¼Ò¦¡¡C³o®É­Ô¡A½Ð·Ó¤U­±«ü¥O¨Ó¤â°Ê¸ü¤J©Ò»Ýªº kernel module
+	¡A¤]´N¬O <filename>geom_mirror.ko</filename>¡G</para>
 
 	<screen>OK? <userinput>load geom_mirror.ko</userinput>
 OK? <userinput>boot</userinput></screen>
 
-	<para>If this works then for whatever reason the module was not
-	  being loaded properly.  Place:</para>
+	<para>¦pªG³o¼Ë¦¨¥\¤Fªº¸Ü¡Aªí¥Ü¦]¬°¬Y¨Ç­ì¦]µLªk¦Û°Ê¸ü¤J kernel module¡C
+	½Ð±N¡G</para>
 
 	<programlisting>options	GEOM_MIRROR</programlisting>
 
-	<para>in the kernel configuration file, rebuild and reinstall.
-	  That should remedy this issue.</para>
+	<para>¥[¤J¨ì®Ö¤ß³]©wÀÉ(kernel configuration file)¡A­«½s¨Ã¦w¸Ë®Ö¤ß¡C
+	  ³oÀ³¸Ó¯à¸Ñ¨M³o­Ó°ÝÃD¡C</para>
       </sect3>
     </sect2>
   </sect1>
 </chapter>
 
 <!--
      Local Variables:
      mode: sgml
      sgml-declaration: "../chapter.decl"
      sgml-indent-data: t
      sgml-omittag: nil
      sgml-always-quote-attributes: t
-     sgml-parent-document: ("../book.sgml" "part" "chapter")
+     sgml-parent-document:("../book.sgml" "part" "chapter")
      End:
 -->
diff --git a/zh_TW.Big5/books/handbook/install/chapter.sgml b/zh_TW.Big5/books/handbook/install/chapter.sgml
index 3304ba6ab3..4938e607c1 100644
--- a/zh_TW.Big5/books/handbook/install/chapter.sgml
+++ b/zh_TW.Big5/books/handbook/install/chapter.sgml
@@ -1,5683 +1,5522 @@
 <!--
      The FreeBSD Documentation Project
 
      $FreeBSD$
 -->
 
 <chapter id="install">
   <chapterinfo>
     <authorgroup>
       <author>
         <firstname>Jim</firstname>
 	<surname>Mock</surname>
 	<contrib>Restructured, reorganized, and parts
 	  rewritten by </contrib>
       </author>
     </authorgroup>
 
     <authorgroup>
       <author>
 	<firstname>Randy</firstname>
 	<surname>Pratt</surname>
 	<contrib>The sysinstall walkthrough, screenshots, and general
 	  copy by </contrib>
       </author>
     </authorgroup>
     <!-- January 2000 -->
   </chapterinfo>
 
   <title>¦w¸Ë FreeBSD</title>
 
   <sect1 id="install-synopsis">
-    <title>Synopsis</title>
+    <title>·§­z</title>
 
     <indexterm><primary>installation</primary></indexterm>
 
-    <para>FreeBSD is provided with a text-based, easy to use installation
-      program called <application>sysinstall</application>.  This is the
-      default installation program for FreeBSD, although vendors are free to
-      provide their own installation suite if they wish.  This chapter
-      describes how to use <application>sysinstall</application> to install
-      FreeBSD.</para>
+    <para>FreeBSD ´£¨Ñ¤@­Ó²³æ¦n¥Îªº¤å¦r¤¶­±¦w¸Ëµ{¦¡¡A¥s°µ <application>sysinstall</application>¡C
+	  ³o¬O FreeBSD ¹w³]¨Ï¥Îªº¦w¸Ëµ{¦¡¡C¨ó¤O¼t°Ó¦pªG·Q¡A¤]¥i¥H§ï¥Î¦Û¤vªº¦w¸Ëµ{¦¡¡C
+	¥»³¹±N»¡©ú¦p¦ó¨Ï¥Î <application>sysinstall</application> ¨Ó¦w¸Ë FreeBSD¡C</para>
 
-    <para>After reading this chapter, you will know:</para>
+    <para>Ū§¹³o³¹¡A±z±N¤F¸Ñ¡J</para>
 
     <itemizedlist>
       <listitem>
-	<para>How to create the FreeBSD installation disks.</para>
+	<para>¦p¦ó»s§@ FreeBSD ¦w¸Ë¤ù</para>
       </listitem>
       
       <listitem>
-	<para>How FreeBSD refers to, and subdivides, your hard disks.</para>
+	<para>FreeBSD ¹ïµwºÐªº¨Ï¥Î¤Î°t¸m¡C</para>
       </listitem>
 
       <listitem>
-	<para>How to start <application>sysinstall</application>.</para>
+	<para>¦p¦ó±Ò°Ê <application>sysinstall</application> µ{¦¡¡C</para>
       </listitem>
 
       <listitem>
-	<para>The questions <application>sysinstall</application> will ask
-	  you, what they mean, and how to answer them.</para>
+	<para>¦b°õ¦æ <application>sysinstall</application> ®É·|°Ýªº¬ÛÃö°ÝÃD¦³­þ¨Ç¡B
+	³o¨Ç°ÝÃDªº·N«ä¬°¦ó¡B¥H¤Î¸Ó¦p¦ó¦^µª¡C</para>
       </listitem>
     </itemizedlist>
 
-    <para>Before reading this chapter, you should:</para>
+    <para>¦b¶}©l¾\Ū³o³¹¤§«e¡A±z»Ý­n¡J</para>
 
     <itemizedlist>
       <listitem>
-	<para>Read the supported hardware list that shipped with the version
-	  of FreeBSD you are installing, and verify that your hardware is
-	  supported.</para>
+	<para>¾\Ū­n¦w¸Ëªº FreeBSD ª©¥»©Òªþ¤§µwÅé¤ä´©ªí¡A¥H½T©w±zªºµwÅ馳¨S¦³³Q¤ä´©¡C</para>
       </listitem>
     </itemizedlist>
 
     <note>
-      <para>In general, these installation instructions are written
-        for &i386; (<quote>PC compatible</quote>) architecture
-        computers.  Where applicable, instructions specific to other
-        platforms (for example, Alpha) will be listed.  Although this
-	guide is kept as up to date as possible, you may find minor
-	differences between the installer and what is shown here.  It is
-	suggested that you use this chapter as a general guide rather 
-	than a literal installation manual.</para>
+      <para>¤@¯ë¨Ó»¡¡A¦¹¦w¸Ë»¡©ú¬O°w¹ï &i386; (¬Û®eªº PC ¾÷ºØ) 
+	¬[ºcªº¹q¸£¡C ¦pªG¦³¨ä¥L¬[ºc(¤ñ¦p Alpha)ªº¦w¸Ë»¡©ú¡A§Ú­Ì·|¤@¨Ö¦C¥X¡C
+	ÁöµM¥»¤å¥ó·|±`±`§ó·s¡A¦ý¦³¥i¯à»P±z¦w¸Ëª©¥»¤W©Òªþªº»¡©ú¤å¥ó¦³¨Ç³\¥X¤J¡C
+	¦b¦¹¡A§Ú­Ì«Øij±z§â¥»»¡©ú¤å³¹·í§@¤@¯ëªº¦w¸Ë°Ñ¦Ò­ì«h´N¦n¡C</para>
     </note>
 
   </sect1>
 
   <sect1 id="install-pre">
-    <title>Pre-installation Tasks</title>
+    <title>¦w¸Ë«eªº·Ç³Æ¤u§@</title>
 
     <sect2 id="install-inventory">
-      <title>Inventory Your Computer</title>
-
-      <para>Before installing FreeBSD you should attempt to inventory the
-	components in your computer.  The FreeBSD installation routines will
-	show you the components (hard disks, network cards, CDROM drives, and
-	so forth) with their model number and manufacturer.  FreeBSD will also
-	attempt to determine the correct configuration for these devices,
-	which includes information about IRQ and IO port usage.  Due to the
-	vagaries of PC hardware this process is not always completely
-	successful, and you may need to correct FreeBSD's determination of
-	your configuration.</para>
-
-      <para>If you already have another operating system installed, such as
-	&windows; or Linux, it is a good idea to use the facilities provided
-	by those operating systems to see how your hardware is already
-	configured.  If you are not sure what settings an expansion
-	card is using, you may find it printed on the card itself.  Popular IRQ
-	numbers are 3, 5, and 7, and IO port addresses are normally written as
-	hexadecimal numbers, such as 0x330.</para>
-
-      <para>We recommend you print or write down this information before
-	installing FreeBSD.  It may help to use a table, like this:</para>
+      <title>¦C¥X±z¹q¸£ªºµwÅé²M³æ</title>
+
+      <para>¦b¦w¸Ë FreeBSD ¤§«e¡A±zÀ³¸Ó¸ÕµÛ±N±z¹q¸£¤¤ªºµwÅé²M³æ¦C¥X¨Ó¡C
+	FreeBSD ¦w¸Ëµ{¦¡·|±N³o¨ÇµwÅé(µwºÐ¡Bºô¸ô¥d¡B¥úºÐ¾÷µ¥µ¥)¥H«¬¸¹¤Î»s³y¼t°Ó¦C¥X¨Ó¡C
+	FreeBSD ¤]·|¹Á¸Õ¬°³o¨ÇµwÅé§ä¥X³Ì¾A·íªº IRQ ¤Î IO port ªº³]©w¡C
+	¦ý¬O¦]¬° PC ªºµwÅéºØÃþ¹ê¦b¤Ó¹L½ÆÂø¡A³o­Ó¨BÆJ¤£¤@©w«OÃÒµ´¹ï¦¨¥\¡C
+	³o®É¡A±z´N¥i¯à»Ý­n¤â°Ê§ó§ï¦³°ÝÃDªº³]©w­È­ù¡C</para>
+
+      <para>¦pªG±z¤w¸Ë¤F¨ä¥¦ªº§@·~¨t²Î¡A¦p¡G
+	&windows; ©Î Linux¡A¨º»ò¥i¥ý¥Ñ³o¨Ç¨t²Î©Ò´£¨Ñªº¤u¨ã¡A¨Ó¬d¬Ý³o¨ÇµwÅé³]©w­È¬O«ç»ò³]©wªº¡C
+	­Y¯uªº¨S¿ìªk½T©w¬Y¨Ç¥d¥Î¤°»ò³]©w­È¡A¨º»ò¥i¥HÀˬd¬Ý¬Ý¥d¤W­±©Ò¼Ð¥ÜªºªF¦è¡A»¡¤£©w¥¦ªº³]©w¤w¦³¼Ð¥Ü¦b¥d¤W¡C
+	±`¥Îªº IRQ ¸¹½X¬° 3¡B5 ¥H¤Î 7¡F¦Ó IO °ðªº­È³q±`¥H 16 ¶i¦ìªí¥Ü¡A¨Ò¦p 0x330¡C</para>
+
+      <para>«Øij±z¦b¦w¸Ë FreeBSD ¤§«e¡A§â³o¨Ç¸ê®Æ¦C¦L©Î§Û¿ý¤U¨Ó¡A°µ¦¨ªí®æªº¼Ë¤l¤]³\·|¸û¦³¥Î³á¡A¨Ò¦p¡G</para>
 
       <table pgwide="1" frame="none">
-	<title>Sample Device Inventory</title>
+	<title>µwÅé²M³æ(Á|¨Ò)</title>
 
 	<tgroup cols="4">
           <colspec colwidth="2*">
           <colspec colwidth="1*">
           <colspec colwidth="1*">
           <colspec colwidth="4*">
 	  <thead>
 	    <row>
-	      <entry>Device Name</entry>
+	      <entry>µwÅé¦WºÙ</entry>
 
 	      <entry>IRQ</entry>
 
 	      <entry>IO port(s)</entry>
 
-	      <entry>Notes</entry>
+	      <entry>³Æµù</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
-	      <entry>First hard disk</entry>
+	      <entry>²Ä¤@Áû IDE µwºÐ</entry>
 
 	      <entry>N/A</entry>
 
 	      <entry>N/A</entry>
 
-	      <entry>40&nbsp;GB, made by Seagate, first IDE master</entry>
+	      <entry>40&nbsp;GB¡ASeagate »s³y¡Afirst IDE master</entry>
 	    </row>
 
 	    <row>
 	      <entry>CDROM</entry>
 
 	      <entry>N/A</entry>
 
 	      <entry>N/A</entry>
 
 	      <entry>First IDE slave</entry>
 	    </row>
 
 	    <row>
-	      <entry>Second hard disk</entry>
+	      <entry>²Ä¤GÁûµwºÐ</entry>
 
 	      <entry>N/A</entry>
 
 	      <entry>N/A</entry>
 
-	      <entry>20&nbsp;GB, made by IBM, second IDE master</entry>
+	      <entry>20&nbsp;GB¡AIBM »s³y¡A second IDE master</entry>
 	    </row>
 
 	    <row>
-	      <entry>First IDE controller</entry>
+	      <entry>²Ä¤@­Ó IDE controller</entry>
 
 	      <entry>14</entry>
 
 	      <entry>0x1f0</entry>
 
 	      <entry></entry>
 	    </row>
 
 	    <row>
-	      <entry>Network card</entry>
+	      <entry>ºô¸ô¥d</entry>
 
 	      <entry>N/A</entry>
 
 	      <entry>N/A</entry>
 
 	      <entry>&intel; 10/100</entry>
 	    </row>
 
 	    <row>
-	      <entry>Modem</entry>
+	      <entry>¼Æ¾Ú¾÷</entry>
 
 	      <entry>N/A</entry>
 
 	      <entry>N/A</entry>
 
-	      <entry>&tm.3com; 56K faxmodem, on COM1</entry>
+	      <entry>&tm.3com; 56K faxmodem¡A±µ¦b COM1</entry>
 	    </row>
 
 	    <row>
 	      <entry>&hellip;</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </table>
     </sect2>
 
     <sect2>
-      <title>Backup Your Data</title>
+      <title>³Æ¥÷±zªº¸ê®Æ</title>
       
-      <para>If the computer you will be installing FreeBSD on contains
-	valuable data, then ensure you have it backed up, and that you have
-	tested the backups before installing FreeBSD.  The FreeBSD
-	installation routine will prompt you before writing any
-	data to your disk, but once that process has started it cannot be
-	undone.</para>
+      <para>¦pªG­n¸Ëªº¹q¸£¤W­±¦s¦³­«­n¸ê®Æ¡A¨º»ò¦b¦w¸Ë FreeBSD «e¡A
+	½Ð½T©w±z¤w¸g±N³o¨Ç¸ê®Æ³Æ¥÷¤F¡A¨Ã¥B¥ý´ú¸Õ¹L³o¨Ç³Æ¥÷ÀɬO§_¨S¦³°ÝÃD¡C
+	FreeBSD ¦w¸Ëµ{¦¡¦b­n¼g¤J¥ô¦ó¸ê®Æ¨ì±zªºµwºÐ«e¡A³£·|¥ý´£¿ô±z½T»{¡A
+	¤@¥¹±z½T©w­n¼g¤J¡A¨º»ò¤§«á´N¦A¤]¨S¦³¤Ï®¬ªº¾÷·|Åo¡C</para>
     </sect2>
 
     <sect2 id="install-where">
-      <title>Decide Where to Install FreeBSD</title>
+      <title>¨M©w­n±N FreeBSD ¦w¸Ë¨ì­þ¸Ì</title>
 
-      <para>If you want FreeBSD to use your entire hard disk, then there is nothing
-	more to concern yourself with at this point &mdash; you can skip this
-	section.</para>
+      <para>¦pªG±z·QÅý FreeBSD ª½±µ¨Ï¥Î¾ãÁûµwºÐ¡A¨º»ò½Ðª½±µ¸õ¨ì¤U¤@¸`¡C</para>
 
-      <para>However, if you need FreeBSD to co-exist with other operating
-	systems then you need to have a rough understanding of how data is
-	laid out on the disk, and how this affects you.</para>
+      <para>µM¦Ó¡A¦pªG±z·Q­n FreeBSD ¸ò¬J¦³ªº¨t²Î¨Ã¦s¡A¨º»ò¡A±z¥²¶·¹ïµwºÐªº¸ê®Æ¤À§G¤è¦¡¦³²`¤Jªº¤F¸Ñ¡A
+		¥H¤Î¨ä©Ò³y¦¨ªº¼vÅT¡C</para>
 
       <sect3 id="install-where-i386">
-	<title>Disk Layouts for the &i386;</title>
-
-      <para>A PC disk can be divided into discrete chunks.  These chunks are
-	called <firstterm>partitions</firstterm>.  By design, the PC only
-	supports four partitions per disk.  These partitions are called
-	<firstterm>primary partitions</firstterm>.  To work around this
-	limitation and allow more than four partitions, a new partition type
-	was created, the <firstterm>extended partition</firstterm>.  A disk
-	may contain only one extended partition.  Special partitions, called
-	<firstterm>logical partitions</firstterm>, can be created inside this
-	extended partition.</para>
-
-      <para>Each partition has a <firstterm>partition ID</firstterm>, which is
-	a number used to identify the type of data on the partition.  FreeBSD
-	partitions have the partition ID of <literal>165</literal>.</para>
-
-      <para>In general, each operating system that you use will identify
-	partitions in a particular way.  For example, DOS, and its
-	descendants, like &windows;, assign each primary and logical partition a
-	<firstterm>drive letter</firstterm>, starting with
-	<devicename>C:</devicename>.</para>
-
-      <para>FreeBSD must be installed into a primary partition.  FreeBSD can
-	keep all its data, including any files that you create, on this one
-	partition.  However, if you have multiple disks, then you can create a
-	FreeBSD partition on all, or some, of them.  When you install FreeBSD,
-	you must have one partition available.  This might be a blank
-	partition that you have prepared, or it might be an existing partition
-	that contains data that you no longer care about.</para>
-
-      <para>If you are already using all the partitions on all your disks, then
-	you will have to free one of them for FreeBSD using the tools
-	provided by the other operating systems you use (e.g.,
-	<command>fdisk</command> on DOS or &windows;).</para>
-
-      <para>If you have a spare partition then you can use that.  However, you
-	may need to shrink one or more of your existing partitions
-	first.</para>
-
-      <para>A minimal installation of FreeBSD takes as little as 100&nbsp;MB of disk
-	space.  However, that is a <emphasis>very</emphasis> minimal install,
-	leaving almost no space for your own files.  A more realistic minimum
-	is 250&nbsp;MB without a graphical environment, and 350&nbsp;MB or more if you
-	want a graphical user interface.  If you intend to install a lot of
-	third party software as well, then you will need more space.</para>
-
-      <para>You can use a commercial tool such as <application>&partitionmagic;</application>
-	to resize your partitions to make space for
-	FreeBSD.  The <filename>tools</filename> directory on the CDROM
-	contains two free software tools which can carry out this task, namely
-	<application>FIPS</application> and
-	<application>PResizer</application>.  Documentation for both
-	of these is available in the same directory.
+	<title>&i386; ¬[ºcªºµwºÐ°t¸m¼Ò¦¡</title>
+
+      <para>PC ¤WªºµwºÐ¥i¥H³Q²Ó¤À¬°³\¦h¤À´²ªº°Ï°ì¡C³o¨Ç°Ï°ì¥s°µ <firstterm>¤À³Î°Ï(Partitions)</firstterm>¡C
+	¦]¬°³]­pªº¤è¦¡¡A¨C­ÓµwºÐ³Ì¦h¥i¥H¦³ 4 ­Ó¤À³Î°Ï¡A¦Ó³o¨Ç¤À³Î¥s°µ 
+	<firstterm>¥D­n¤À³Î°Ï(Primary Partitions)</firstterm>¡C
+	¬°¤F¬ð¯}³o­Ó­­¨î¡A¥H«K¯à¨Ï¥Î§ó¦hªº¤À³Î°Ï¡A´N¦³¤F·sªº¤À³Î°ÏÃþ«¬¡A¥s§@¡G 
+	<firstterm>©µ¦ù¤À³Î°Ï(Extended Partition)</firstterm>¡C
+	¨C­ÓµwºÐ´N¥u¯à¦³¤@­Ó©µ¦ù¤À³Î°Ï¡CµM¦Ó¡A¦b©µ¦ù¤À³Î°Ï¸Ì­±¥i¥H«Ø¥ß³\¦h­Ó¯S®í¤À³Î°Ï¡A¥s§@ 
+	<firstterm>ÅÞ¿è¤À³Î°Ï(Logical Partitions)</firstterm>¡C</para>
+
+      <para>¨CºØ¤À³Î°Ï³£¦³¨ä <firstterm>¤À³Î°Ï¥N¸¹(Partition ID)</firstterm>
+	¥Î¥H°Ï§O¨CºØ¤À³Î°Ïªº¸ê®ÆÃþ«¬¡C¦Ó FreeBSD ¤À³Î°Ï¥N¸¹¬O <literal>165</literal>¡C</para>
+
+      <para>¤@¯ë¨ÓÁ¿¡A¨CºØ§@·~¨t²Î³£·|¦³¦Û¤v¿W¯Sªº¤è¦¡¨Ó°Ï§O¤À³Î°Ï¡CÁ|¨Ò¡G DOS ¤Î¨ä¤§«áªº§@·~¨t²Î¡A¤ñ¦p
+	 &windows; ¡A·|¤À°tµ¹¨C­Ó¥D­n¤À³Î°Ï¤ÎÅÞ¿è¤À³Î°Ï 1 ­Ó 
+	<firstterm>ºÏºÐ¥N¸¹(drive letter)</firstterm>¡A±q	<devicename>C:</devicename> ¶}©l¡C</para>
+
+      <para>FreeBSD ¥²¶·¦w¸Ë¦b¥D­n¤À³Î°Ï¡CFreeBSD ¥i¥H¦b³o­Ó¤À³Î°Ï¤W­±¦s©ñ¸ê®Æ©Î¬O±z«Ø¥ßªº¥ô¦óÀɮסC
+	µM¦Ó¡A¦pªG±z¦³«Ü¦hÁûµwºÐ¡A¤]¥i¥H¦b³o¨Ç(©Î³¡¥÷)µwºÐ«Ø¥ß FreeBSD ¤À³Î°Ï¡C
+	¦w¸Ë FreeBSD ªº®É­Ô¡A¥²¶·¦Ü¤Ö­n¦³ 1 ­Ó¤À³Î°Ïµ¹ FreeBSD ¨Ï¥Î¡A
+	³o­Ó¤À³Î°Ï¥i¥H¬O©|¥¼¨Ï¥Îªº¤À³Î°Ï¡A©Î¬O²{¦sªº¤À³Î°Ï¡C(¦ý¤W­±ªº¸ê®Æ¤£¥´ºâÄ~Äò¨Ï¥Î)</para>
+
+      <para>¦pªG±z¤w¸g¥Î§¹¤F±zºÏºÐ¤W©Ò¦³ªº¤À³Î°Ï¡A¨º»ò±z¥²¶·¨Ï¥Î¨ä¥L§@·~¨t²Î©Ò´£¨Ñªº¤u¨ã
+	(¹³¬O DOS or &windows; ¤Wªº <command>fdisk</command>)¨ÓÄË¥X¤@­Ó¤À³Î°Ïµ¹ FreeBSD ¥Î¡C</para>
+
+      <para>¦pªG¦³¦h¾lªº¤À³Î°Ï¡A¤]¥i¥H¨Ï¥Î¥¦¡C¦ý¨Ï¥Î«e¡A±z¥i¯à»Ý­n¥ý¾ã²z¤@¤U³o¨Ç¤À³Î°Ï¡C</para>
+
+      <para>FreeBSD³Ì¤p¦w¸Ë»Ý­n¬ù 100&nbsp;MB ªºªÅ¶¡¡A¦ý¬O³o¥u¬O¡y³Ì¤p¦w¸Ë¡z¡A
+	´X¥G¨S³Ñ¤U¦h¤ÖªÅ¶¡¨Ó¦s©ñ±z¦Û¤vªºÀɮסC  ¸û²z·Qªº(¤£§t¹Ï§Î¤¶­±)³Ì¤p¦w¸Ë¬O¬ù
+	250&nbsp;MB¡A©ÎªÌ¬O 350&nbsp;MB ¥ª¥k(¥]§t¹Ï§Î¤¶­±)¡C
+	Áٻݭn¦w¸Ë¨ä¥Lªº®M¥ó³nÅé¡A¨º»ò±N»Ý­n§ó¦hªºµwºÐªÅ¶¡¡C</para>
+
+      <para>±z¥i¥H¨Ï¥Î°Ó·~³nÅé¡A¨Ò¦p <application>&partitionmagic;</application>
+	¨Ó­«·s½Õ¾ã¤À³Î°ÏªÅ¶¡¡A¨Óµ¹ FreeBSD ¥ÎªºªÅ¶¡¡CFreeBSD ¥úºÐ¡BFTP ¤W­±ªº <filename>tools</filename> 
+	¥Ø¿ý¥]§t¨â­Ó§K¶Oªº¤u¨ã¡A¤]¥i¥H¹F¦¨³o­Ó¤u§@¡A¥s§@¡G
+	<application>FIPS</application> ¤Î
+	<application>PResizer</application>¡C³o¨Ç¤u¨ãªº»¡©ú¤å¥ó¥i¥H¦b¦P­Ó¥Ø¿ý¤º§ä¨ì¡C
 	<application>FIPS</application>,
-	<application>PResizer</application>, and
-	<application>&partitionmagic;</application> can resize
-	<acronym>FAT16</acronym> and <acronym>FAT32</acronym>
-	partitions &mdash; used in &ms-dos; through &windows; ME.
-	<application>&partitionmagic;</application> is the only one of
-	the above applications that can resize <acronym>NTFS</acronym>
-	partitions.</para>
+	<application>PResizer</application> ©M
+	<application>&partitionmagic;</application> ¥i¥H­«·s½Õ¾ã¦b &ms-dos; ¨ì &windows; ME ©Ò¨Ï¥Îªº
+	<acronym>FAT16</acronym> ¤Î <acronym>FAT32</acronym>
+	¤À³Î°Ï¤j¤p¡C¥t¥~¡A
+	<application>&partitionmagic;</application> «h¬O¤W­z³nÅ餤°ß¤@¥i¥H­«·s½Õ¾ã
+	<acronym>NTFS</acronym> ¤À³Î°Ï¤j¤p¡C</para>
 
       <warning>
-	<para>Incorrect use of these tools can delete the data on your disk.
-	  Be sure that you have recent, working backups before using
-	  them.</para>
+	<para>¤£·íªº¨Ï¥Î³o¨Ç¤u¨ã¡A¥i¯à·|§R°£©Ò¦³µwºÐ¤Wªº¸ê®Æ¡C
+	  ¦b¨Ï¥Î³o¨Ç¤u¨ã«e¡A½Ð½T©w±z¤w¦³¥ý³Æ¥÷¦n¸ê®Æ¡C</para>
       </warning>
 
       <example>
-	<title>Using an Existing Partition Unchanged</title>
-
-	<para>Suppose that you have a computer with a single 4&nbsp;GB disk that
-	  already has a version of &windows; installed, and you have split the
-	  disk into two drive letters, <devicename>C:</devicename> and
-	  <devicename>D:</devicename>, each of which is 2&nbsp;GB in size.  You have
-	  1&nbsp;GB of data on <devicename>C:</devicename>, and 0.5&nbsp;GB of data on
-	  <devicename>D:</devicename>.</para>
-
-	<para>This means that your disk has two partitions on it, one per
-	  drive letter.  You can copy all your existing data from
-	  <devicename>D:</devicename> to <devicename>C:</devicename>, which
-	  will free up the second partition, ready for FreeBSD.</para>
+	<title>¨Ï¥Î²{¦³ªº¤À³Î°Ï</title>
+
+	<para>°²³]±z¥u¦³¤@­Ó 4&nbsp;GB ªºµwºÐ¡A¦Ó¥B¤w¸g¸Ë¤F &windows; 
+	¡AµM«á±N³oÁûµwºÐ¤À¦¨¨â­ÓºÏºÐ¥N¸¹¡G<devicename>C:</devicename> ¤Î
+	  <devicename>D:</devicename>¡A¨C­Ó¤j¤p¬° 2&nbsp;GB ¡C
+	<devicename>C:</devicename> ¼Ñ¤W©ñ¤F 1&nbsp;GB ªº¸ê®Æ¡A¦Ó <devicename>D:</devicename> 
+	¼Ñ¤W©ñ¤F 0.5&nbsp;GB ªº¸ê®Æ¡C</para>
+
+	<para>³oªí¥ÜµwºÐ¤W¦³¨â­Ó¤À³Î°Ï¡A¨C­ÓºÏºÐ¥N¸¹¼Ñ³£¬O¤À³Î°Ï¡C±z¥i¥H§â©Ò¦³©ñ¦b 
+		<devicename>D:</devicename> ªº¸ê®Æ¡A³£²¾°Ê¨ì <devicename>C:</devicename>
+		¡A³o¼Ë´NªÅ¥X¤F²Ä¤G­Ó¤À³Î°Ï¥i¥Hµ¹ FreeBSD ¨Ï¥Î¡C</para>
       </example>
 
       <example>
-	<title>Shrinking an Existing Partition</title>
+	<title>ÁY´î²{¦³ªº¤À³Î°Ï</title>
 
-	<para>Suppose that you have a computer with a single 4&nbsp;GB disk that
-	  already has a version of &windows; installed.  When you installed
-	  &windows; you created one large partition, giving you a
-	  <devicename>C:</devicename> drive that is 4&nbsp;GB in size.  You are
-	  currently using 1.5&nbsp;GB of space, and want FreeBSD to have 2&nbsp;GB of
-	  space.</para>
+	<para>°²³]±z¥u¦³¤@­Ó 4&nbsp;GB µwºÐ¡A¦Ó¥B¤w¸g¸Ë¤F &windows; ¡C¦b¦w¸Ë
+	  &windows; ®É§â 4&nbsp;GB ³£µ¹ <devicename>C:</devicename> ¼Ñ¡A¨Ã¥B²{¦b¤w¸g¥Î¤F 1.5&nbsp;GB 
+	ªÅ¶¡¡A¦Ó§A·Q±N³Ñ¤UªÅ¶¡ªº 2&nbsp;GB µ¹ FreeBSD ¨Ï¥Î¡C</para>
 
-	<para>In order to install FreeBSD you will need to either:</para>
+	<para>¦p¦¹¤@¨Ó¡A¬°¤F¸Ë FreeBSD ¡A§A¥²¶·¦b¥H¤U¨âºØ¤è¦¡¤G¿ï¤@¡G</para>
 
 	<orderedlist>
 	  <listitem>
-	    <para>Backup your &windows; data, and then reinstall &windows;,
-	      asking for a 2&nbsp;GB partition at install time.</para>
+	    <para>³Æ¥÷ &windows; ¸ê®Æ¡AµM«á­«¸Ë &windows;¡A¨Ã¦b¦w¸Ë &windows; ®Éµ¹ 2&nbsp;GB ªº¤À³ÎªÅ¶¡¡C</para>
 	  </listitem>
 
 	  <listitem>
-	    <para>Use one of the tools such as <application>&partitionmagic;</application>,
-	      described above, to shrink your &windows;
-		partition.</para>
+	    <para>¨Ï¥Î¤W­zªº¤u¨ã¡A¹³¬O <application>&partitionmagic;</application>¡A¨Ó­«·s½Õ¾ã &windows;
+		©Ò¥Îªº¤À³Î°Ï¤j¤p¡C</para>
 	  </listitem>
 	</orderedlist>
       </example>
 
       </sect3>
 
       <sect3>
-	<title>Disk Layouts for the Alpha</title>
+	<title>Alpha ¬[ºcªººÏºÐ°t¸m¼Ò¦¡</title>
 
 	<indexterm><primary>Alpha</primary></indexterm>
 
-	<para>You will need a dedicated disk for FreeBSD on the
-	  Alpha.  It is not possible to share a disk with another
-	  operating system at this time.  Depending on the specific
-	  Alpha machine you have, this disk can either be a SCSI disk
-	  or an IDE disk, as long as your machine is capable of
-	  booting from it.</para>
+	<para>¦b Alpha ¤W¡A±z¥²¶·¨Ï¥Î¤@¾ãÁûµwºÐµ¹ FreeBSD
+	¡A¨S¦³¿ìªk¦b¦PÁûµwºÐ¤W¸ò¨ä¥L§@·~¨t²Î¦@¦s¡C®Ú¾Ú¤£¦P«¬¸¹ªº Alpha
+	 ¾÷¾¹¡A±zªºµwºÐ¥i¥H¬O SCSI ©Î IDE µwºÐ¡A¥u­n±zªº¾÷¾¹¥i¥H±q³o¨ÇµwºÐ¶}¾÷´N¥i¥H¡C</para>
 
-	<para>Following the conventions of the Digital / Compaq
-	  manuals all SRM input is shown in uppercase.  SRM is case
-	  insensitive.</para>
+	<para>«ö·Ó Digital / Compaq ¨Ï¥Î¤â¥Uªº½s±Æ­·®æ¡A©Ò¦³ SRM ¿é¤Jªº³¡¤À³£¥Î¤j¼gªí¥Ü¡C
+	ª`·N¡ASRM ¤j¤p¼g¦³§O¡C</para>
 
-	<para>To find the names and types of disks in your machine, use
-	  the <literal>SHOW DEVICE</literal> command from the SRM
-	  console prompt:</para>
+	<para>­n±oª¾±zºÏºÐªº¦WºÙ¥H¤Î«¬¸¹¡A¥i¥H¦b SRM console ´£¥Ü¤U¨Ï¥Î
+	 <literal>SHOW DEVICE</literal> ©R¥O¡G</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>This example is from a Digital Personal Workstation
-	  433au and shows three disks attached to the machine.  The
-	  first is a CDROM drive called <devicename>DKA0</devicename> and
-	  the other two are disks and are called
-	  <devicename>DKC0</devicename> and
-	  <devicename>DKC100</devicename> respectively.</para>
-
-	<para>Disks with names of the form <devicename>DKx</devicename>
-	  are SCSI disks.  For example <devicename>DKA100</devicename>
-	  refers to a SCSI disk with SCSI target ID 1 on the first SCSI bus (A), 
-	  whereas <devicename>DKC300</devicename> refers to a SCSI disk
-	  with SCSI ID 3 on the third SCSI bus (C).  Devicename <devicename>
-	  PKx</devicename> refers to the SCSI host bus adapter.  As
-	  seen in the <literal>SHOW DEVICE</literal> output SCSI
-	  CDROM drives are treated as any other SCSI hard disk drive.</para>
-
-	<para>IDE disks have names similar to <devicename>DQx</devicename>,
-	  while <devicename>PQx</devicename> is the associated IDE
-	  controller.</para>
+	<para>¨Ò¤l¤¤¾÷¾¹¬° Digital Personal Workstation 
+	433au ¨Ã¥BÅã¥Ü¥X¦¹¾÷¾¹¦³³s±µ¤T­ÓºÏºÐ¾÷¡C²Ä¤@­Ó¬O CDROM¡A¥s°µ <devicename>DKA0</devicename> 
+	¡F¥t¥~¨â­Ó¬OºÏºÐ¾÷¡A ¤À§O¥s°µ¡G
+	  <devicename>DKC0</devicename> ¤Î
+	  <devicename>DKC100</devicename> ¡C</para>
+
+	<para>ºÏºÐ¾÷ªº¦WºÙ¤¤¦³ <devicename>DKx</devicename>
+	  ¦r¼Ëªº¬O SCSI µwºÐ¡C¨Ò¦p¡G <devicename>DKA100</devicename>
+	  ªí¥Ü¬O SCSI µwºÐ¡A¨ä SCSI ID ¬° 1¡A ¦ì¦b²Ä¤@­Ó SCSI ¶×¬y±Æ(A)¡F
+	  ¦Ó <devicename>DKC300</devicename> ªí¥Ü¬O SCSI µwºÐ¡A¨ä SCSI ID ¬° 3
+	¡A¦ì©ó²Ä¤T­Ó SCSI ¶×¬y±Æ(C)¡C¸Ë¸m¦WºÙ <devicename>
+	  PKx</devicename> ªí¥Ü SCSI ±±¨î¥d¡C¥Ñ¤W­z <literal>SHOW DEVICE</literal> ªºµ²ªG¬Ý¨Ó¡A
+	SCSI ¥úºÐ¾÷¤]³Qµø¬°¬O SCSI µwºÐªº¤@ºØ¡C</para>
+
+	<para>­Y¬° IDE µwºÐªº¸Ü¡A¦WºÙ·|¦³ <devicename>DQx</devicename> ¦r¼Ë¡A¦Ó
+	 <devicename>PQx</devicename> «hªí¥Ü¬Û¹ïÀ³ªº IDE ºÏºÐ±±¨î¾¹¡C</para>
 
       </sect3>
     </sect2>
 
     <sect2>
-      <title>Collect Your Network Configuration Details</title>
+      <title>¾ã²z§Aªººô¸ô³]©w¸ê®Æ</title>
 
-      <para>If you intend to connect to a network as part of your FreeBSD
-	installation (for example, if you will be installing from an FTP
-	site or an
-	NFS server), then you need to know your network configuration.  You
-	will be prompted for this information during the installation so that
-	FreeBSD can connect to the network to complete the install.</para>
+      <para>¦pªG·Q³z¹Lºô¸ô( FTP ¯¸©Î NFS)¦w¸Ë FreeBSD¡A¨º»ò´N¥²¶·ª¾¹D±zªººô¸ô²ÕºA¡C
+	¦b¦w¸Ë FreeBSD ªº¹Lµ{¤¤±N·|´£¥Ü±z¿é¤J³o¨Ç¸ê°T¡A¥H¶¶§Q§¹¦¨¦w¸Ë¹Lµ{¡C</para>
 
       <sect3>
-	<title>Connecting to an Ethernet Network or Cable/DSL Modem</title>
+	<title>¨Ï¥Î¤A¤Óºô¸ô(Ethernet)©Î Cable/DSL ¼Æ¾Ú¾÷¤Wºô</title>
 
-	<para>If you connect to an Ethernet network, or you have an Internet
-	  connection using an Ethernet adapter via cable or DSL, then you will need the following
-	  information:</para>
+	<para>­Y¨Ï¥Î¤A¤Óºô¸ô¡A©Î¬O­n³z¹L Cable/DSL ¼Æ¾Ú¾÷¤Wºô¡A¨º»ò±z¥²¶··Ç³Æ ¤U­±ªº¸ê°T¡G</para>
 
 	<orderedlist>
 	  <listitem>
-	    <para>IP address</para>
+	    <para>IP ¦ì§}</para>
 	  </listitem>
 
 	  <listitem>
-	    <para>IP address of the default gateway</para>
+	    <para>¹w³] Gateway(¹h¹D) ªº IP ¦ì§}</para>
 	  </listitem>
 
 	  <listitem>
-	    <para>Hostname</para>
+	    <para>Hostname(¾÷¾¹¦WºÙ)</para>
 	  </listitem>
 
 	  <listitem>
-	    <para>DNS server IP addresses</para>
+	    <para>DNS ¦øªA¾¹ªº IP ¦ì§}</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>Subnet Mask</para>
 	  </listitem>
 	</orderedlist>
 
-	<para>If you do not know this information, then ask your system
-	  administrator or service provider.  They may say that this
-	  information is assigned automatically, using
-	  <firstterm>DHCP</firstterm>.  If so, make a note of this.</para>
+	<para>­Y¤£ª¾¹D³o¨Ç¸ê°T¡A±z¥i¥H¸ß°Ý¨t²ÎºÞ²zªÌ©Î¬O±zªº ISP ·~ªÌ¡C
+	¥L­Ì¥i¯à·|»¡³o¨Ç¸ê°T·|¥Ñ <firstterm>DHCP</firstterm> ¦Û°Ê«ü¬£¡F¦pªG¬O³o¼Ëªº¸Ü¡A ½Ð°O¦í³o¤@ÂI´N¥i¥H¤F¡C</para>
       </sect3>
 
       <sect3>
-	<title>Connecting Using a Modem</title>
+	<title>¨Ï¥Î¼Æ¾Ú¾÷¤Wºô</title>
 
-	<para>If you dial up to an ISP using a regular modem then you can
-	  still install FreeBSD over the Internet, it will just take a very
-	  long time.</para>
+	<para>­Y¥Ñ¤@¯ëªº¼Æ¾Ú¾÷¼·±µ¤Wºô¡A±z¤´µM¥i¥H¦w¸Ë FreeBSD¡A¥u¬O·|»Ý­n«Üªøªº®É¶¡¡C</para>
 
-	<para>You will need to know:</para>
+	<para>±z¥²¶·ª¾¹D¡G</para>
 
 	<orderedlist>
 	  <listitem>
-	    <para>The phone number to dial for your ISP</para>
+	    <para>¼·±µ¨ì ISP ªº¹q¸Ü¸¹½X¡C</para>
 	  </listitem>
 
 	  <listitem>
-	    <para>The COM: port your modem is connected to</para>
+	    <para>±zªº¼Æ¾Ú¾÷¬O³s¨ì­þ­Ó COM °ð¡C</para>
 	  </listitem>
 
 	  <listitem>
-	    <para>The username and password for your ISP account</para>
+	    <para>±z¼·±µ¨ì ISP ©Ò¥Îªº±b¸¹¸ò±K½X¡C</para>
 	  </listitem>
 	</orderedlist>
       </sect3>
     </sect2>
     <sect2>
-      <title>Check for FreeBSD Errata</title>
+      <title>¬d¾\ FreeBSD °É»~ªí(Errata)</title>
       
-      <para>Although the FreeBSD project strives to ensure that each release
-	of FreeBSD is as stable as possible, bugs do occasionally creep into
-	the process.  On very rare occasions those bugs affect the
-	installation process.  As these problems are discovered and fixed, they
-	are noted in the <ulink url="http://www.FreeBSD.org/releases/&rel.current;R/errata.html">FreeBSD Errata</ulink>, which is found on the FreeBSD web site.  You
-	should check the errata before installing to make sure that there are
-	no late-breaking problems which you should be aware of.</para>
-
-      <para>Information about all the releases, including the errata for each
-	release, can be found on the 
-	<ulink
-	url="&url.base;/releases/index.html">release
-	information</ulink> section of the 
+      <para>ÁöµM§Ú­ÌºÉ¤O¨Ï±o¨C­Ó FreeBSD  µo¦æª©¥»³£«Üí©w¡A¦ý¬O¹Lµ{¤¤¤´µM¤£§K¦³®É·|µo¥Í¿ù»~¡C
+	¦b«Ü¨u¨£ªº±¡§Î¤U¡A³o¨Ç¿ù»~·|¼vÅT¨ì¦w¸Ëªº¹Lµ{¡C·íµo²{³o¨Ç¿ù»~¥B­×¥¿«á¡A·|±N¥¦­Ì¦C¦b
+	<ulink url="http://www.FreeBSD.org/releases/&rel.current;R/errata.html">
+	FreeBSD °É»~ªí(Errata)</ulink> ¤¤¡C¦b±z¦w¸Ë FreeBSD 
+	«e¡AÀ³¸Ó¥ý¬Ý¬Ý°É»~ªí¤¤¦³¨S¦³¤°»ò°ÝÃD·|¼vÅT¨ì±zªº¦w¸Ë¡C</para>
+
+      <para>Ãö©ó©Ò¦³µo¦æª©¥»ªº¸ê°T¡A¥]¬A°É»~ªí¡A¥i¥H¦b <ulink
+	  url="&url.base;/index.html">FreeBSD ºô¯¸</ulink> ªº
 	<ulink
-	  url="&url.base;/index.html">FreeBSD web site</ulink>.</para>
+	url="&url.base;/releases/index.html">µo¦æ±¡³ø(release information)</ulink> §ä¨ì¡C</para>
     </sect2>
 
     <sect2>
-      <title>Obtain the FreeBSD Installation Files</title>
+      <title>·Ç³Æ¦n FreeBSD ¦w¸ËÀÉ®×</title>
 
-      <para>The FreeBSD installation process can install FreeBSD from files
-	located in any of the following places:</para>
+      <para>FreeBSD ¥i¥H³z¹L¤U­±¥ô¦ó¤@ºØ¦w¸Ë¨Ó·½¶i¦æ¦w¸Ë¡J</para>
 
       <itemizedlist>
 	<title>Local Media</title>
 	
 	<listitem>
-	  <para>A CDROM or DVD</para>
+	  <para>CDROM ©Î DVD</para>
 	</listitem>
 
 	<listitem>
-	  <para>A DOS partition on the same computer</para>
+	  <para>²{¦³ªº DOS ¤À³Î°Ï</para>
 	</listitem>
 
 	<listitem>
-	  <para>A SCSI or QIC tape</para>
+	  <para>SCSI ©Î QIC ºÏ±a¡C</para>
 	</listitem>
 
 	<listitem>
-	  <para>Floppy disks</para>
+	  <para>³nºÐºÏ¤ù</para>
 	</listitem>
       </itemizedlist>
 
       <itemizedlist>
 	<title>Network</title>
 
 	<listitem>
-	  <para>An FTP site, going through a firewall, or using an HTTP proxy,
-	    as necessary</para>
+	  <para>FTP ¯¸¡B¤ä´© Passvie ¼Ò¦¡ªº FTP ¯¸(­Y±z¾÷¾¹¦b NAT ¤º)¡B¬Æ¦Ü HTTP proxy ³£¥i¥H¡C</para>
 	</listitem>
 
 	<listitem>
-	  <para>An NFS server</para>
+	  <para>NFS ¦øªA¾¹</para>
 	</listitem>
 
 	<listitem>
-	  <para>A dedicated parallel or serial connection</para>
+	  <para>±M¥Î(dedicated)ªº parallel ©Î serial ³s½u</para>
 	</listitem>
       </itemizedlist>
 
-      <para>If you have purchased FreeBSD on CD or DVD then you already have
-	everything you need, and should proceed to the next section 
-	(<xref linkend="install-floppies">).</para>
+      <para>­Y¤w¸g¦³ FreeBSD ªº CD ©Î DVD¡A¦ý¾÷¾¹¤£¤ä´©±q¥úºÐ¶}¾÷ªº¸Ü¡A¨º»ò½Ðª½±µ¶i¤U¤@¸` 
+	(<xref linkend="install-floppies">)¡C</para>
 
-      <para>If you have not obtained the FreeBSD installation files you should
-	skip ahead to <xref linkend="install-diff-media"> which explains how
-	to prepare to install FreeBSD from any of the above.  After reading
-	that section, you should come back here, and read on to 
-	<xref linkend="install-floppies">.</para>
+      <para>­Y¨S¦³ FreeBSD ¦w¸Ë¤ùªº¸Ü¡A¨º»ò½Ð¥ý¬Ý <xref linkend="install-diff-media"> 
+	³o¸Ì·|¤¶²Ð¦p¦ó·Ç³Æ©Ò»Ý­nªº¦w¸Ë¤ù¡A·Ó¸Ó¸`¨BÆJ§Ë¦n«á¡A´N¥i¥HÄ~Äò¤U¤@¨B 
+	<xref linkend="install-start">¡C</para>
     </sect2>
 
     <sect2 id="install-floppies">
-      <title>Prepare the Boot Media</title>
+      <title>·Ç³Æ¦n¶}¾÷ºÏ¤ù</title>
       
-      <para>The FreeBSD installation process is started by booting your
-	computer into the FreeBSD installer&mdash;it is not a program you run
-	within another operating system.  Your computer normally boots using
-	the operating system installed on your hard disk, but it can also be
-	configured to use a <quote>bootable</quote> floppy disk.
-	Most modern computers can also
-	boot from a CDROM in the CDROM drive.</para>
+      <para>FreeBSD ¦w¸Ë¬yµ{¬O­n±q¹q¸£¶}¾÷«á¡A¶i¤J FreeBSD ¦w¸Ëµe­± ¡X¡X ¦Ó¤£¬O¦b¨ä¥L§@·~¨t²Î¤W°õ¦æµ{¦¡¡C
+      	¤@¯ë¨ÓÁ¿¡A¹q¸£³£¬O¥Î¸Ë¦bµwºÐ¤Wªº§@·~¨t²Î¨Ó¶}¾÷¡A¤]¥i¥H¥Î¶}¾÷ºÏ¤ù¨Ó¶}¾÷¡F
+      	¦¹¥~¡A²{¦b¤j¦h¼Æ¹q¸£³£¥i¥H±q¥úºÐ¶}¾÷¡C</para>
 
       <tip>
-	<para>If you have FreeBSD on CDROM or DVD (either one you purchased
-	  or you prepared yourself), and your computer allows you to boot from
-	  the CDROM or DVD (typically a BIOS option called <quote>Boot
-	    Order</quote> or similar), then you can skip this section.  The
-	  FreeBSD CDROM and DVD images are bootable and can be used to install
-	  FreeBSD without any other special preparation.</para>
+	<para>¦pªG±z¦³ FreeBSD ªº CDROM ©Î DVD(µL½×¬O¥Î¶Rªº©Î¬O¦Û¤v¿N¿ýªº)¡A ¥B±zªº¹q¸£¥i¤ä´©¥Ñ¥úºÐ¶}¾÷¡A
+		(³q±`¦b BIOS ¤¤·|¦³ <quote>Boot
+	    Order</quote> ©ÎÃþ¦ü¿ï¶µ)¡A¨º»ò±z´N¥i¥H¸õ¹L¦¹¤p¸`¡C¦]¬° FreeBSD CDROM ©Î DVD ³£¥i¥H¥Î¨Ó¶}¾÷¡C</para>
       </tip>
     
-      <para>To create boot floppy images, follow these steps:</para>
+      <para>½Ð«ö·Ó¤U­±¨BÆJ¡A¥H»s§@¶}¾÷¤ù¡G</para>
 
       <procedure>
 	<step>
-	  <title>Acquire the Boot Floppy Images</title>
+	  <title>¨ú±o¶}¾÷¤ùªº¬M¹³ÀÉ(images)</title>
 	  
-	  <para>The boot disks are available on your installation media
-	    in the <filename>floppies/</filename> directory, and
-	    can also be downloaded from the floppies directory, <literal>ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<replaceable>&lt;arch&gt;</replaceable>/<replaceable>&lt;version&gt;</replaceable>-RELEASE/floppies/</literal>.
-	    Replace <replaceable>&lt;arch&gt;</replaceable> and
-	    <replaceable>&lt;version&gt;</replaceable>
-	    with the architecture and the version number
-	    which you want to install, respectively.
-	    For example, the boot floppy images for
-	    &os;&nbsp;&rel.current;-RELEASE for &i386; are available
-	    from <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/floppies/"></ulink>.</para>
-
-	  <para>The floppy images have a <filename>.flp</filename> extension.
-	    The <filename>floppies/</filename> directory contains a number of
-	    different images, and the ones you will need to use depends on the
-	    version of FreeBSD you are installing, and in some cases, the
-	    hardware you are installing to.  If you are installing
-	    FreeBSD&nbsp;4.X in most cases you will just need
-	    two files, <filename>kern.flp</filename> and
-	    <filename>mfsroot.flp</filename>.  If you are
-	    installing FreeBSD&nbsp;5.X in most cases you will need three
-	    floppies, <filename>boot.flp</filename>,
-	    <filename>kern1.flp</filename>, and
-	    <filename>kern2.flp</filename>.  Check
-	    <filename>README.TXT</filename> in the same directory for the
-	    most up to date information about these floppy images.</para>
-
-	  <note><para>Additional device drivers may
-	    be necessary for 5.X systems older than &os;&nbsp;5.3.
-	    These drivers are provided on the
-	    <filename>drivers.flp</filename> image.</para></note>
+	  <para>¶}¾÷ºÏ¤ù¥Îªº¬M¹³ÀÉ(images)³q±`·|©ñ¦b¥úºÐ¤ù¤Wªº <filename>floppies/</filename> ¥Ø¿ý¤º¡A¥t¥~¤]¥i¥H±q¹³¬O¤U­± FTP ¯¸ªº floppies
+	   ¥Ø¿ý¤U¸ü¡G 
+	   <literal>ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<replaceable>&lt;arch&gt;</replaceable>/<replaceable>&lt;version&gt;</replaceable>-RELEASE/floppies/</literal> 
+	   ¡C½Ð±N¡yarch¡z¡B¡yversion¡z´À´«¬°¥´ºâ¦w¸Ëªº¹q¸£¬[ºc¡BOS ª©¥»¡C¨Ò¦p¡G­n¸Ëªº¹q¸£ÄÝ &i386 ¬[ºc¡A¦Ó­n¸Ëªº¬O 
+	   &os;&nbsp;&rel.current;-RELEASE ¡A¨º»ò¥i¥H¨ì <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/floppies/"></ulink> ¤U¸ü¡C</para>
+
+	  <para>¬M¹³ÀÉ(images)ªºªþÀɦW³£¬O <filename>.flp</filename> ¡C¦Ó
+	    <filename>floppies/</filename> ¥Ø¿ý¤º¥]§t¤@¨Ç¤£¦P¥Î³~ªº¬M¹³ÀÉ(images)¡A³o¨ú¨M©ó±z­n¸Ëªº FreeBSD ª©¥»¡B»Ý¨D¡BµwÅé°t³Æ¬°¦ó¡C
+	    ­Y­n¸Ëªº¬O
+	    FreeBSD&nbsp;4.X ¨º»ò³q±`¥u»Ý­n 2 ­Ó¬M¹³ÀÉ¡A¤]´N¬O <filename>kern.flp</filename> »P
+	    <filename>mfsroot.flp</filename>¡C¦Ó­Y­n¸Ëªº¬O FreeBSD&nbsp;5.X
+	    ¡A¨º»ò³q±`­n 3 ­Ó¬M¹³ÀÉ¡A¤]´N¬O¡G <filename>boot.flp</filename>¡B
+	    <filename>kern1.flp</filename>¡B
+	    <filename>kern2.flp</filename>¡C­Y¦³ºÃ°Ýªº¸Ü¡A½Ð½¾\¦P¤@¥Ø¿ý¤Uªº 
+	    <filename>README.TXT</filename> ¤å¥óÀÉ¡A¥HÁA¸Ñ¬ÛÃö³Ì·sª`·N¨Æ¶µ¡C</para>
+
+	  <note><para>¦w¸Ë &os;&nbsp;5.3 ¤§«eªº 5.X ¨t²Î®É¡A¦³¨ÇµwÅé³]³Æ¥i¯à»Ý­nÃB¥~ªºÅX°Êµ{¦¡¤~¯à¨Ï¥Î¡C
+	  	³o¨ÇÅX°Êµ{¦¡³£·|©ñ¦b <filename>drivers.flp</filename> ³o­Ó¬M¹³Àɤº¡C</para></note>
 
 	  <important>
-	    <para>Your FTP program must use <emphasis>binary mode</emphasis>
-	      to download these disk images.  Some web browsers have been
-	      known to use <emphasis>text</emphasis> (or
-	      <emphasis>ASCII</emphasis>) mode, which will be apparent if you
-	      cannot boot from the disks.</para>
+	    <para>¦b¨Ï¥Î FTP ¤U¸ü®É¡A¥²¶·¨Ï¥Î <emphasis>binary ¼Ò¦¡</emphasis> ¶i¦æ¶Ç¿é¡C¦³¨ÇÂsÄý¾¹¹w³]¬O¥H <emphasis>text</emphasis> (©Î
+	      <emphasis>ASCII</emphasis>) ¼Ò¦¡¨Ó¶Ç¿é¸ê®Æ¡A©Ò¥H³o¨Ç¿ù»~¶Ç¿é¼Ò¦¡¤U¸üªº¬M¹³ÀÉ©Ò°µ¦¨ªººÏ¤ù¡A·|µLªk¨Ï¥Î¡C</para>
 	  </important>
 	</step>
 
 	<step>
-	  <title>Prepare the Floppy Disks</title>
+	  <title>·Ç³Æ¶}¾÷ºÏ¤ù</title>
 	  
-	  <para>You must prepare one floppy disk per image file you had to
-	    download.  It is imperative that these disks are free from
-	    defects.  The easiest way to test this is to format the disks
-	    for yourself.  Do not trust pre-formatted floppies.  The format
-	    utility in &windows; will not tell about the presence of
-	    bad blocks, it simply marks them as <quote>bad</quote>
-	    and ignores them.  It is advised that you use brand new
-	    floppies if choosing this installation route.</para>
+	  <para>¨C­Ó¬M¹³Àɳ£»Ý­n¤@±iºÏ¤ù¡A¨Ã¥B½ÐÁקK¨Ï¥Î¨ìÃaªººÏ¤ù¡C³Ì²³æªºÀË´ú¤è¦¡´N¬O¦Û¤v¥ý§â³o¨ÇºÏ¤ù¦A­«·s®æ¦¡¤Æ(format)
+	  	¦Ó¤£­n¬Û«H©Ò¿×ªº¤w®æ¦¡¤ÆªººÏ¤ù¡A&windows; ¤ºªº format 
+	  	¦b®æ¦¡¤Æ®É¡A¨Ã¤£·|§i¶D§A¬O§_¦³Ãa­y¡A¦Ó¥u·|ª½±µ±N¥¦­Ì¼Ð¥ÜÃa­y¦Ó¤£¨Ï¥ÎÃa­y³¡¤À¦Ó¤w¡C
+	  	¦¹¥~¡A«Øij±Ä¥Î¥þ·sªººÏ¤ù¨Ó»s§@¦w¸Ë¤ù¤ñ¸û«OÀI¡C</para>
 
 	  <important>
-	    <para>If you try to install FreeBSD and the installation
-	      program crashes, freezes, or otherwise misbehaves, one of
-	      the first things to suspect is the floppies.  Try writing
-	      the floppy image files to new disks and try
-	      again.</para>
+	    <para>­Y¦b¦w¸Ë FreeBSD ªº¹Lµ{¤¤µo¥Í·í¾÷¡Bµe­±­áµ²©Î¬O¨ä¥L©Ç²§ªº²{¶H¡A­º¥ý­nÃhºÃªº´N¬O¶}¾÷ºÏ¤ù¬O§_Ãa±¼¡C
+	    	½Ð¥Î¨ä¥LªººÏ¤ù»s§@¬M¹³ÀɦA¸Õ¸Õ¬Ý¡C</para>
 	  </important>
 	</step>
 
 	<step>
-	  <title>Write the Image Files to the Floppy Disks</title>
+	  <title>±N¬M¹³ÀÉ(images)¼g¤J¨ìºÏ¤ù¤º</title>
 
-	  <para>The <filename>.flp</filename> files are
-	    <emphasis>not</emphasis> regular files you copy to the disk.
-	    They are images of the complete contents of the
-	    disk.  This means that you <emphasis>cannot</emphasis> simply
-	    copy files from one disk to another.
-	    Instead, you must use specific tools to write the
-	    images directly to the disk.</para>
+	  <para><filename>.flp</filename> ÀɨëD¤@¯ëÀɮסA¤£¯àª½±µ§â¥¦½Æ»s¨ìºÏ¤ù¤W¡C
+	    ¨Æ¹ê¤W¥¦¬O¥]§t¾ã±iºÏ¤ù©Ò¦³¤º®eªº¬M¹³ÀÉ(image)¡C¤]´N¬O»¡¡A¤£¯à¯Âºé½Æ»sÀɮרìºÏ¤ù¤W¡A
+	    ¦Ó¥²¶·¨Ï¥Î¯S§Oªº¤u¨ãµ{¦¡¡A¨Ó±N¬M¹³Àɪ½±µ¼g¨ìºÏ¤ù¤W¡C</para>
 
 	  <indexterm><primary>DOS</primary></indexterm>
-	  <para>If you are creating the floppies on a computer running
-      &ms-dos;/&windows;, then we provide a tool to do
-      this called <command>fdimage</command>.</para>
+	  <para>­Y­n¥Î &ms-dos;/&windows; ¨Ó§@¦w¸Ë¤ùªº¸Ü¡A¨º»ò¥i¥H¥Î <command>fdimage</command> 
+	  	¤u¨ãµ{¦¡¨Ó±N¬M¹³ÀÉ¡A¼g¨ìºÏ¤ù¤W¡C</para>
 
-	  <para>If you are using the floppies from the CDROM, and your
-	    CDROM is the <devicename>E:</devicename> drive, then you would 
-	    run this:</para>
+	  <para>­Y±z¥Îªº¬O FreeBSD ¥úºÐªº¸Ü(°²³]¥úºÐ¾÷¥N¸¹¬° <devicename>E:</devicename> ¡A¨º»ò½Ð°õ¦æÃþ¦ü¤U­±ªº«ü¥O¡G</para>
 
 	  <screen><prompt>E:\&gt;</prompt> <userinput>tools\fdimage floppies\kern.flp A:</userinput></screen>
 
-	  <para>Repeat this command for each <filename>.flp</filename>
-	    file, replacing the floppy disk each time, being sure to label
-	    the disks with the name of the file that you copied to them.
-	    Adjust the command line as necessary, depending on where you have
-	    placed the <filename>.flp</filename> files.  If you do not have
-	    the CDROM, then <command>fdimage</command> can be downloaded from
-	    the <ulink
+	  <para>½Ð°w¹ï¨C­Ó»Ý­n¥Î¨ìªº <filename>.flp</filename> ¬M¹³ÀÉ¡A­«½Æ¤W­zªº«ü¥O(°O±o§ó§ï¬ÛÃöÀɦW)¡A¨C¦¸ªº¬M¹³Àɧ¹¦¨«á¡A
+	  	³£»Ý­n´«¥t¥~¤@¤ù¨Ó¸Ë·sªº¬M¹³ÀÉ¡F½Ð°O±o¡A¦b§@¦nªººÏ¤ù¤Wµù©ú¬O¨Ï¥Î­þ­Ó¬M¹³Àɧ@ªº¡C­Y <filename>.flp</filename> 
+	  	¬M¹³ÀÉ©ñ¦b¤£¦P¦a¤è¡A½Ð¦Û¦æ­×§ï¤W­z«ü¥O¡C­Y¨S¦³ FreeBSD ¥úºÐªº¸Ü¡A¥i¥H¨ì FTP ¤W­±ªº <ulink
 	    url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/"><filename class="directory">tools</filename>
-	    directory</ulink> on the FreeBSD FTP site.</para>
+	    ¥Ø¿ý</ulink> ¤U¸ü <command>fdimage</command> ¨Ï¥Î¡C</para>
 	  
-	  <para>If you are writing the floppies on a &unix; system (such as
-	    another FreeBSD system) you can use the &man.dd.1; command to
-	    write the image files directly to disk.  On FreeBSD, you would
-	    run:</para>
+	  <para>¦pªG­n¥Î &unix; ¨t²Î(¤ñ¦p¨ä¥L¥x FreeBSD ¾÷¾¹)¨Ó»s§@¶}¾÷¤ùªº¸Ü¡A¥i¥H¥Î &man.dd.1; 
+	  	«ü¥O¨Ó§â¬M¹³Àɪ½±µ¼g¤J¨ìºÏ¤ù¤W¡C¦b FreeBSD¤Wªº¸Ü¡A¥i¥H¥´Ãþ¦ü¤U­±ªº«ü¥O¡G</para>
 	  
 	  <screen>&prompt.root; <userinput>dd if=kern.flp of=/dev/fd0</userinput></screen>
 
-	  <para>On FreeBSD, <filename>/dev/fd0</filename> refers to the
-	    first floppy disk (the <devicename>A:</devicename> drive).
-	    <filename>/dev/fd1</filename> would be the
-	    <devicename>B:</devicename> drive, and so on.  Other &unix;
-	    variants might have different names for the floppy disk
-	    devices, and you will need to check the documentation for the
-	    system as necessary.</para>
+	  <para>¦b FreeBSD ¤¤¡A<filename>/dev/fd0</filename> ´N¬O«ü²Ä¤@¥x³nºÐ¾÷(§Y¤@¯ë &ms-dos;/&windows; 
+	  	¤Wªº <devicename>A:</devicename> ºÏºÐ¾÷)¡F¦Ó <filename>/dev/fd1</filename> «ü
+	    <devicename>B:</devicename> ºÏºÐ¾÷¡A¨ä¾lªº¨Ì¦¹Ãþ±À¡C¤£¹L¨ä¥Lªº &unix; 
+	    ¨t²Î¥i¯à·|¥Î¤£¦Pªº¦WºÙ¡A³o®É´N­n¬d¾\¸Ó¨t²Îªº»¡©ú¤å¥ó¤F¡C</para>
 	</step>
       </procedure>
 
-      <para>You are now ready to start installing FreeBSD.</para>
+      <para>²{¦b°_¡A§Ú­Ì¥i¥H¶}©l¦w¸Ë FreeBSD Åo¡I</para>
     </sect2>
   </sect1>
 
   <sect1 id="install-start">
-    <title>Starting the Installation</title>
+    <title>¶}©l¦w¸Ë</title>
 
     <important>
-      <para>By default, the installation will not make any changes to your
-	disk(s) until you see the following message:</para>
+      <para>¹w³]ªº±¡ªp¤U¡A¦w¸Ë¹Lµ{¨Ã¤£·|§ïÅܱzºÏºÐ¾÷¤¤ªº¥ô¦ó¸ê®Æ¡A°£«D±z¬Ý¨ì¤U­±ªº°T®§¡G</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>The install can be exited at any time prior to the final
-	warning without changing the contents of the hard drive.  If you are
-	concerned that you have configured something incorrectly you can just
-	turn the computer off before this point, and no damage will be
-	done.</para>
+      <para>¦b¬Ý¨ì³o³Ì«áªºÄµ§i°T®§«e¡A±z³£¥i¥HÀH®ÉÂ÷¶}¦w¸Ëµ{¦¡¦Ó¤£·|Åܧó±zªºµwºÐ¡C
+      	¦pªG±zµo²{¦³¥ô¦ó³]©w¿ù»~¡A³o®É±z¥i¥Hª½±µ±N¹q·½Ãö±¼¦Ó¤£·|³y¦¨¥ô¦ó¶Ë®`¡C</para>
     </important>
 
     <sect2 id="install-starting">
-      <title>Booting</title>
+      <title>¶}¾÷±Ò°Ê¬yµ{½g</title>
 
       <sect3 id="install-starting-i386">
-        <title>Booting for the &i386;</title>
+        <title>&i386; ¥­¥xªº¶}¾÷¬yµ{</title>
 
       <procedure>
 	<step>
-	  <para>Start with your computer turned off.</para>
+	  <para>¦b¤@¶}©l¡A¹q¸£¹q·½¶}Ãö¬OÃö³¬ªº¡C</para>
 	</step>
 
 	<step>
-	  <para>Turn on the computer.  As it starts it should display an
-	    option to enter the system set up menu, or BIOS, commonly reached
-	    by keys like <keycap>F2</keycap>, <keycap>F10</keycap>,
-	    <keycap>Del</keycap>, or
+	  <para>¥´¶}¹q¸£¹q·½¶}Ãö¡C­è¶}©lªº®É­Ô¡A¥¦À³¸Ó·|Åã¥Ü¶i¤J¨t²Î³]©w¿ï³æ©Î BIOS ­n«ö­þ­ÓÁä¡A±`¨£ªº¦³¡G <keycap>F2</keycap>, <keycap>F10</keycap>,
+	    <keycap>Del</keycap> ©Î
 	    <keycombo action="simul">
 	      <keycap>Alt</keycap>
 	      <keycap>S</keycap>
-	    </keycombo>.  Use whichever keystroke is indicated on screen.  In
-	    some cases your computer may display a graphic while it starts.
-	    Typically, pressing <keycap>Esc</keycap> will dismiss the graphic
-	    and allow you to see the necessary messages.</para>
+	    </keycombo>¡C(«öÁä½Ð¨Ì¾Ú¹ê»Ú±¡ªp¨M©w)¤£½×¬O­n«ö­þ­ÓÁä¡A½Ð«ö¥¦¶i¤J BIOS 
+	    	³]©wµe­±¡C¦³®É±zªº¹q¸£¥i¯à·|Åã¥Ü¤@­Ó¹Ï§Îµe­±¡A³q±`°µªk¬O«ö <keycap>Esc</keycap> 
+	    	Áä±NÂ÷¶}³o­Ó¹Ï§Îµe­±¡A¥H¨Ï±z¯à°÷¬Ý¨ì¥²­nªº³]©w°T®§¡C</para>
 	</step>
 
 	<step>
-	  <para>Find the setting that controls which devices the system boots
-	    from.  This is usually labeled as the <quote>Boot Order</quote>
-            and commonly shown as a list of devices, such as
+	  <para>§ä¥X¥i¥H³]©w¡y¶}¾÷¶¶§Ç(Boot Order)¡zªº¿ï¶µ¡A³q±`¸Ó¿ï¶µ·|¦C¥X¤@¨Ç³]³ÆÅý±z¿ï¾Ü¡A¨Ò¦p¡J
 	    <literal>Floppy</literal>, <literal>CDROM</literal>,
-	    <literal>First Hard Disk</literal>, and so on.</para>
+	    <literal>First Hard Disk</literal> µ¥µ¥¡C</para>
 
-	  <para>If you needed to prepare boot floppies, then make sure that the
-	    floppy disk is selected.  If you are booting from the CDROM then
-	    make sure that that is selected instead.  In case of doubt, you
-	    should consult the manual that came with your computer, and/or its
-	    motherboard.</para>
+	  <para>¦pªG­n¥Î³nºÐ¦w¸Ë¡A½Ð½T©w floppy disk ­n¦C¬°¶}¾÷¶¶§Çªº²Ä¤@­Ó¡F­Y­n¥Î¥úºÐ¦w¸Ë¡A°O±o CDROM 
+	  	­n¦C¬°¶}¾÷¶¶§Çªº²Ä¤@­Ó¡C¬°¤FÁקKºÃ´b¡A½Ð°Ñ¦Ò¾÷¾¹¡B¥D¾÷ªO»¡©ú¤â¥U¡C</para>
 
-	  <para>Make the change, then save and exit.  The computer should now
-	    restart.</para>
+	  <para>Àx¦s³]©w¨ÃÂ÷¶}¡A¨t²ÎÀ³¸Ó·|­«·s±Ò°Ê¡C</para>
 	</step>
 
 	<step>
-	  <para>If you needed to prepare boot floppies, as described in 
-	    <xref linkend="install-floppies">, then one of them will be the
-	    first boot disc, probably the one containing
-	    <filename>kern.flp</filename>.  Put this disc in your floppy
-	    drive.</para>
+	  <para>¥ÎºÏ¤ù¦w¸Ë¡A½Ð§â¦b 
+	    <xref linkend="install-floppies">¤@¸`¤¤»s§@¦nªº <filename>kern.flp</filename> ¨º±i¦w¸ËºÏ¤ù©ñ¨ì²Ä¤@¥x³nºÐ¾÷¤¤¡C</para>
 
-	  <para>If you are booting from CDROM, then you will need to turn on
-	    the computer, and insert the CDROM at the first
-	    opportunity.</para>
+	  <para>¦pªG¬O±q¥úºÐ¦w¸Ë¡A¨º»ò¶}¾÷«á½Ð±N FreeBSD ¥úºÐ©ñ¤J¥úºÐ¾÷¤¤¡C</para>
 
-	  <para>If your computer starts up as normal and loads your existing
-	    operating system, then either:</para>
+	  <para>¦pªG¡A¶}¾÷«á¦p©¹±`¤@¼Ë¦Ó¨S¦³±q³nºÐ©Î¥úºÐ¶}¾÷¡A½ÐÀˬd¡J</para>
 
 	  <orderedlist>
 	    <listitem>
-	      <para>The disks were not inserted early enough in the boot
-		process.  Leave them in, and try restarting your
-		computer.</para>
+	      <para>¬O¤£¬OºÏ¤ù©Î¥úºÐ¤Ó±ß©ñ¤J¦Ó¿ù¥¢¶}¾÷®É¶¡¡C¦pªG¬O¡A½Ð±N¥¦­Ì©ñ¤J¡AµM«á­«·s¶}¾÷¡C</para>
 	    </listitem>
 
 	    <listitem>
-	      <para>The BIOS changes earlier did not work correctly.  You
-		should redo that step until you get the right option.</para>
+	      <para>BIOS ³]©w¤£¹ï©Î§Ñ¤FÀx¦s³]©w¡A½Ð­«·sÀˬd BIOS ªº³]©w¡C</para>
 	    </listitem>
 
 	    <listitem>
-	      <para>Your particular BIOS does not support booting from
-		the desired media.</para>
+	      <para>±zªº¹q¸£ BIOS ¤£¤ä´©±q¥úºÐ¶}¾÷¡C</para>
 	    </listitem>
 	</orderedlist>
 	</step>
     
 	<step>
-	  <para>FreeBSD will start to boot.  If you are booting from CDROM you
-	    will see a display similar to this (version information omitted):</para>
+	  <para>¦¹®É¡AFreeBSD ´N¶}©l±Ò°Ê¤F¡C¦pªG¬O±q¥úºÐ¶}¾÷¡A·|¨£¨ìÃþ¦ü¤U­±ªºµe­±(ª©¥»³¡¤À¬Ù²¤)¡G:</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>If you are booting from floppy disc, you will see a display
-	    similar to this (version information omitted):</para>
+	  <para>¦pªG±z±q³nºÐ¶}¾÷¡A·|¬Ý¨ìÃþ¦ü¤U­±ªºµe­±(ª©¥»³¡¤À¬Ù²¤)¡G</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>Follow these instructions by removing the
-	    <filename>kern.flp</filename> disc, insert the
-	    <filename>mfsroot.flp</filename> disc, and press
-	    <keycap>Enter</keycap>.  &os;&nbsp;5.3
-	    and above provide other floppy disks set, as described
-	    in <link linkend="install-floppies">previous
-	    section</link>.  Boot from first floppy;
-	    when prompted, insert the other disks as required.</para>
+	  <para>½Ð®Ú¾Ú´£¥Ü±N <filename>kern.flp</filename>  ºÏ¤ù¨ú¥X¡A ¨Ã©ñ¤J <filename>mfsroot.flp</filename> 
+	  	³o±iºÏ¤ù¡AµM«á«ö <keycap>Enter</keycap> Áä¡C­Y¬O &os;&nbsp;5.3 
+		(§t¤§«á)ªº¸Ü¡AÁÙ¦³¥t¥~¤@±iºÏ¤ù(¦b<link linkend="install-floppies">«e¤@¸`</link>¤w¸g¤¶²Ð¹L¤F)¡C
+		Á`¤§¡A±z¥u»Ý±q²Ä¤@±iºÏ¤ù±Ò°Ê¡A µM«á®Ú¾Ú´£¥Ü¡A¦A©ñ¤J¬ÛÃöºÏ¤ù§Y¥i¡C</para>
 	</step>
 
 	<step>
-	  <para>Whether you booted from floppy or CDROM, the
-	    boot process will then get to this point:</para>
+	  <para>¤£½×±q³nºÐ©Î¥úºÐ¶}¾÷¡A±z³£·|¬Ý¨ì¤U­±³o¬q°T®§¡G</para>
 
 	  <screen>Hit [Enter] to boot immediately, or any other key for command prompt. 
 Booting [kernel] in 9 seconds... _</screen>
 
-	  <para>Either wait ten seconds, or press <keycap>Enter</keycap>
-	    (for &os;&nbsp;4.X this
-	    will then launch the kernel configuration menu).</para>
+	  <para>±z¥i¥Hµ¥«Ý 10 ¬í¡A©Î¬O«ö <keycap>Enter</keycap> Áä¡C
+	    (­Y¬O &os;&nbsp;4.X ªº¸Ü¡A«h±N¥X²{ kernel configuration ¿ï³æµe­±)</para>
 	</step>
       </procedure>
 
       </sect3>
       <sect3>
-        <title>Booting for the Alpha</title>
+        <title>Alpha ¥­¥xªº¶}¾÷¬yµ{</title>
 
 	<indexterm><primary>Alpha</primary></indexterm>
 
       <procedure>
 	<step>
 	  <para>Start with your computer turned off.</para>
 	</step>
 
 	<step>
 	  <para>Turn on the computer and wait for a boot monitor
 	    prompt.</para>
         </step>
 
 	<step>
 	  <para>If you needed to prepare boot floppies, as described in 
 	    <xref linkend="install-floppies"> then one of them will be the
 	    first boot disc, probably the one containing
 	    <filename>kern.flp</filename>.  Put this disc in your floppy
 	    drive and type the following command to boot the disk
 	    (substituting the name of your floppy drive if
 	    necessary):</para>
 
 	  <screen>&gt;&gt;&gt;<userinput>BOOT DVA0 -FLAGS '' -FILE ''</userinput></screen>
 
 	  <para>If you are booting from CDROM, insert the CDROM into
 	    the drive and type the following command to start the
 	    installation (substituting the name of the appropriate
 	    CDROM drive if necessary):</para>
 
           <screen>&gt;&gt;&gt;<userinput>BOOT DKA0 -FLAGS '' -FILE ''</userinput></screen>
 	</step>
     
 	<step>
 	  <para>FreeBSD will start to boot.  If you are booting from a
 	    floppy disc, at some point you will see the message:</para>
 
 	  <screen>Please insert MFS root floppy and press enter:</screen>
 
 	  <para>Follow these instructions by removing the
 	    <filename>kern.flp</filename> disc, insert the
 	    <filename>mfsroot.flp</filename> disc, and press
 	    <keycap>Enter</keycap>.</para>
 	</step>
 
 	<step>
 	  <para>Whether you booted from floppy or CDROM, the
 	    boot process will then get to this point:</para>
 
 	  <screen>Hit [Enter] to boot immediately, or any other key for command prompt. 
 Booting [kernel] in 9 seconds... _</screen>
 
 	  <para>Either wait ten seconds, or press <keycap>Enter</keycap>.  This
 	    will then launch the kernel configuration menu.</para>
 	</step>
       </procedure>
 
       </sect3>
 
     </sect2>
 
     <sect2 id="start-userconfig">
-      <title>Kernel Configuration</title>
+      <title>Kernel ªº³]©w</title>
 
-      <note><para>From FreeBSD versions 5.0 and later, userconfig has been deprecated
-	in favor of the new &man.device.hints.5; method.  For more information
-	on &man.device.hints.5; please visit <xref linkend="device-hints"></para></note>
+      <note><para>±q FreeBSD 5.0 ª©¶}©l¡A§ï¥Î·sªº &man.device.hints.5; ¤è¦¡¡A¦Ó²^¨Oªº userconfig ¤è¦¡¡C
+	Ãö©ó &man.device.hints.5; ¾÷¨îªº²Ó¸`¤¶²Ð¡A½Ð°Ñ¾\ <xref linkend="device-hints">¡C</para></note>
 
       <para>The <firstterm>kernel</firstterm> is the core of the operating
 	system.  It is responsible for many things, including access to all
 	the devices you may have on your system, such as hard disks, network
 	cards, sound cards, and so on.  Each piece of hardware supported by
 	the FreeBSD kernel has a driver associated with it.  Each driver has a
 	two or three letter name, such as <devicename>sa</devicename> for the
 	SCSI sequential access driver, or <devicename>sio</devicename> for the
 	Serial I/O driver (which manages COM ports).</para>
 
       <para>When the kernel starts, each driver checks the system to see
 	whether or not the hardware it supports exists on your system.  If it
 	does, then the driver configures the hardware and makes it available
 	to the rest of the kernel.</para>
 
       <para>This checking is commonly referred to as <firstterm>device
 	  probing</firstterm>.  Unfortunately, it is not always possible to do
 	this in a safe way.  Some hardware drivers do not co-exist well,
 	and probing for one piece of hardware can sometimes leave
 	another in an inconsistent state.  This is a basic
 	limitation of the <acronym>PC</acronym> design.</para>
 
       <para>Many older devices are called ISA devices&mdash;as opposed
 	to PCI devices.  The ISA specification requires each device to have
 	some information hard coded into it, typically the Interrupt Request
 	Line number (IRQ) and IO port address that the driver uses.  This
 	information is commonly set by using physical
 	<firstterm>jumpers</firstterm> on the card, or by using a DOS based
 	utility.</para>
 
       <para>This was often a source of problems, because it was not possible
 	to have two devices that shared the same IRQ or port address.</para>
 
       <para>Newer devices follow the PCI specification, which does not require
 	this, as the devices are supposed to cooperate with the BIOS, and are
 	told which IRQ and IO port addresses to use.</para>
 
       <para>If you have any ISA devices in your computer then FreeBSD's
 	driver for that device will need to be configured with the IRQ and
 	port address that you have set the card to.  This is why carrying out
 	an inventory of	your hardware (see <xref
 	linkend="install-inventory">) can be useful.</para>
 
       <para>Unfortunately, the default IRQs and memory ports used by some
 	drivers clash.  This is because some ISA devices are shipped with IRQs
 	or memory ports that clash.  The defaults in FreeBSD's drivers are
 	deliberately set to mirror the manufacturer's defaults, so that, out
 	of the box, as many devices as possible will work.</para>
 
       <para>This is almost never an issue when running FreeBSD day-to-day.
 	Your computer will not normally contain two pieces of hardware that
 	clash, because one of them would not work (irrespective of the
 	operating system you are using).</para>
 
       <para>It becomes an issue when you are installing FreeBSD for the first
 	time because the kernel used to carry out the install has to contain
 	as many drivers as possible, so that many different hardware
 	configurations can be supported.  This means that some of
 	those drivers will have conflicting configurations.  The devices are
 	probed in a strict order, and if you own a device that is probed late
 	in the process, but conflicted with an earlier probe, then your
 	hardware might not function or be probed correctly when you install
 	FreeBSD.</para>
 
       <para>Because of this, the first thing you have the opportunity to do
 	when installing FreeBSD is look at the list of drivers that are
 	configured into the kernel, and either disable some of them, if you
 	do not own that device, or confirm (and alter) the driver's
 	configuration if you do own the device but the defaults are
 	wrong.</para>
 
       <para>This probably sounds much more complicated than it actually
 	is.</para>
 
       <para><xref linkend="kernel-config"> shows the first kernel
 	configuration menu.  We recommend that you choose the
 	<guimenuitem>Start kernel configuration in full-screen visual
 	  mode</guimenuitem> option, as it presents the easiest interface for
 	the new user.</para>
 
       <figure id="kernel-config">
-	<title>Kernel Configuration Menu</title>
+	<title>Kernel ³]©wµe­±</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/userconfig" format="PNG">
 	  </imageobject>
 
 	  <textobject>
 	    <screen>&txt.install.userconfig;</screen>
 	  </textobject>
 	</mediaobject>
       </figure>
 
       <para>The kernel configuration screen (<xref linkend="fig-userconfig">)
 	is then divided into four sections:</para>
 
       <orderedlist>
 	<listitem>
 	  <para>A collapsible list of all the drivers that are currently
 	    marked as <quote>active</quote>, subdivided into groups such as
 	    <literal>Storage</literal>, and <literal>Network</literal>.  Each
 	    driver is shown as a description, its two or three letter driver
 	    name, and the IRQ and memory port used by that driver.  In
 	    addition, if an active driver conflicts with another active driver
 	    then <literal>CONF</literal> is shown next to the driver name.
 	    This section also shows the total number of conflicting drivers
 	    that are currently active.</para>
 	</listitem>
 
 	<listitem>
 	  <para>Drivers that have been marked inactive.  They remain in the
 	    kernel, but they will not probe for their device when the kernel
 	    starts.  These are subdivided into groups in the same way as the
 	    active driver list.</para>
 	</listitem>
 
 	<listitem>
 	  <para>More detail about the currently selected driver, including its
 	    IRQ and memory port address.</para>
 	</listitem>
 
 	<listitem>
 	  <para>Information about the keystrokes that are valid at this point
 	    in time.</para>
 	</listitem>
       </orderedlist>
 
       <figure id="fig-userconfig">
-	<title>The Kernel Device Configuration Visual Interface</title>
+	<title>Kernel Device ªº³]©wµe­±</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/userconfig2" format="PNG">
 	  </imageobject>
 
           <textobject>
             <screen>&txt.install.userconfig2;</screen>
           </textobject>
         </mediaobject>
       </figure>
 
       <para>Do not worry if any conflicts are listed,
 	it is to be expected; all the drivers are enabled, and
 	as has already been explained, some of them will conflict with one
 	another.</para>
 
       <para>You now have to work through the list of drivers, resolving the
 	conflicts.</para>
 
       <procedure>
-	<title>Resolving Driver Conflicts</title>
+	<title>¸Ñ°£¬Û½ÄªºÅX°Êµ{¦¡</title>
 
 	<step>
 	  <para>Press <keycap>X</keycap>.  This will completely expand the
 	    list of drivers, so you can see all of them.  You will need to use
 	    the arrow keys to scroll back and forth through the active driver
 	    list.</para>
 
 	  <para><xref linkend="hardware-conflicts"> shows the result of
 	    pressing <keycap>X</keycap>.</para>
 
 	  <figure id="hardware-conflicts">
-	    <title>Expanded Driver List</title>
+	    <title>®i¶}ÅX°Êµ{¦¡¤@Äýªí</title>
 
 	    <mediaobject>
 	      <imageobject>
 		<imagedata fileref="install/hdwrconf" format="PNG">
 	      </imageobject>
 	    </mediaobject>
 	  </figure>
 	</step>
 
 	<step>
 	  <para>Disable all the drivers for devices that you do not have.  To
 	    disable a driver, highlight it with the arrow keys and press
 	    <keycap>Del</keycap>.  The driver will be moved to the
 	    <literal>Inactive Drivers</literal> list.</para>
 
 	  <para>If you inadvertently disable a device that you need then press
 	    <keycap>Tab</keycap> to switch to the <literal>Inactive
 	    Drivers</literal> list, select the driver that you disabled, and
 	    press <keycap>Enter</keycap> to move it back to the active
 	    list.</para>
 
 	  <warning>
 	    <para>Do not disable <devicename>sc0</devicename>.  This controls
 	      the screen, and you will need this unless you are installing
 	      over a serial cable.</para>
 	  </warning>
 
 	  <warning>
 	    <para>Only disable <devicename>atkbd0</devicename> if you are
 	      using a USB keyboard.  If you have a normal keyboard then you
 	      must keep <devicename>atkbd0</devicename>.</para>
 	  </warning>
 	</step>
 
 	<step>
 	  <para>If there are no conflicts listed then you can skip this step.
 	    Otherwise, the remaining conflicts need to be examined.  If they
 	    do not have the indication of an <quote>allowed conflict</quote>
 	    in the message area, then either the IRQ/address for device probe
 	    will need to be changed, <emphasis>or</emphasis> the IRQ/address
 	    on the hardware will need to be changed.</para>
 
 	  <para>To change the driver's configuration for IRQ and IO port
 	    address, select the device and press <keycap>Enter</keycap>.  The
 	    cursor will move to the third section of the screen, and you can
 	    change the values.  You should enter the values for IRQ and port
 	    address that you discovered when you made your hardware inventory.
 	    Press <keycap>Q</keycap> to finish editing the device's
 	    configuration and return to the active driver list.</para>
 	  
 	  <para>If you are not sure what these figures should be then you can
 	    try using <literal>-1</literal>.  Some FreeBSD drivers can safely
 	    probe the hardware to discover what the correct value should be,
 	    and a value of <literal>-1</literal> configures them to do
 	    this.</para>
 
 	  <para>The procedure for changing the address on the hardware varies
 	    from device to device.  For some devices you may need to
 	    physically remove the card from your computer and adjust jumper
 	    settings or DIP switches.  Other cards may have come with a DOS
 	    floppy that contains the programs used to reconfigure the card.
 	    In any case, you should refer to the documentation that came with
 	    the device.  This will obviously entail restarting your computer,
 	    so you will need to boot back into the FreeBSD installation
 	    routine when you have reconfigured the card.</para>
 	</step>
 
 	<step>
 	  <para>When all the conflicts have been resolved the screen will look
 	    similar to <xref linkend="userconfig-done">.</para>
 
 	  <figure id="userconfig-done">
-	    <title>Driver Configuration With No Conflicts</title>
+	    <title>¨S¦³½Ä¬ðªºÅX°Êµ{¦¡³]©w</title>
 
 	    <mediaobject>
 	      <imageobject>
 		<imagedata fileref="install/probstart" format="PNG">
 	      </imageobject>
 	    </mediaobject>
 	  </figure>
 
 	  <para>As you can see, the active driver list is now much smaller,
 	    with only drivers for the hardware that actually exists being
 	    listed.</para>
 	  
 	  <para>You can now save these changes, and move on to the next step
 	    of the install.  Press <keycap>Q</keycap> to quit the device
 	    configuration interface.  This message will appear:</para>
 
 	  <screen>Save these parameters before exiting? ([Y]es/[N]o/[C]ancel)</screen>
 
 	  <para>Answer <keycap>Y</keycap> to save the parameters to memory
 	    (it will be saved to disk if you finish the install) and the
 	    probing will start.  After displaying the probe results in white
 	    on black text <application>sysinstall</application> will start
 	    and display its main menu 
 	    (<xref linkend="sysinstall-main">).</para>
 
 	  <figure id="sysinstall-main">
-	    <title>Sysinstall Main Menu</title>
+	    <title>Sysinstall ¥D¿ï³æ</title>
 	    
 	    <mediaobject>
 	      <imageobject>
 		<imagedata fileref="install/main1" format="PNG">
 	      </imageobject>
 	    </mediaobject>
 	  </figure>
 	</step>
       </procedure>
     </sect2>
 
     <sect2 id="view-probe">
-      <title>Reviewing the Device Probe Results</title>
+      <title>¨º­n«ç»ò¥h½¾\°»´úµwÅ骺µ²ªG©O¡H</title>
 
-      <para>The last few hundred lines that have been displayed on screen are
-	stored and can be reviewed.</para>
+      <para>¥ý«e¦b¿Ã¹õ¤W©ÒÅã¥Üªº³Ì«á´X¦Ê¦æ¦r¡A·|¦s¦b¼È¦s°Ï(buffer)¥H«K±z½¾\¡C</para>
 
-      <para>To review the buffer, press <keycap>Scroll Lock</keycap>.  This
-	turns on scrolling in the display.  You can then use the arrow keys, or
-	<keycap>PageUp</keycap> and <keycap>PageDown</keycap> to view the
-	results.  Press <keycap>Scroll Lock</keycap> again to stop
-	scrolling.</para>
+      <para>­Y­n½¾\¼È¦s°Ï¡A½Ð«ö <keycap>Scroll Lock</keycap> Áä¡A³o·|¶}±Ò±²°Êµe­±¥\¯à¡C
+	µM«á´N¥i¥H¨Ï¥Î¤è¦VÁä¡A©Î¬O <keycap>PageUp</keycap>¡B<keycap>PageDown</keycap>
+	Áä¨Ó¤W¤U½¾\¡C¦A«ö¤@¦¸ <keycap>Scroll Lock</keycap> Áä¡A´N·|°±¤îµe­±±²°Ê¡C</para>
 
       <para>Do this now, to review the text that scrolled off the screen when
 	the kernel was carrying out the device probes.  You will see text
 	similar to <xref linkend="install-dev-probe">, although the precise
 	text will differ depending on the devices that you have in your
 	computer.</para>
 
       <figure id="install-dev-probe">
-	<title>Typical Device Probe Results</title>
+	<title>°»´úµwÅ骺¨Ò¤l</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>Check the probe results carefully to make sure that FreeBSD found
 	all the devices you expected.  If a device was not found, then it will
 	not be listed.  If the device's driver required configuring
 	with the IRQ and port address then you should check that you entered
 	them correctly.</para>
 
       <para>If you need to make changes to the UserConfig device probing,
 	it is easy to exit the <application>sysinstall</application> program
 	and start over again.  It is also a good way to become more familiar
 	with the process.</para>
 
       <figure id="sysinstall-exit">
-	<title>Select Sysinstall Exit</title>
+	<title>Â÷¶} Sysinstall µ{¦¡</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/sysinstall-exit" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Use the arrow keys to select 
 	<guimenuitem>Exit Install</guimenuitem> from the Main
 	Install Screen menu.  The following message will display:</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>The install program will start again if the CDROM is left
 	in the drive and &gui.yes; is selected.</para>
 
       <para>If you are booting from floppies it will be necessary to remove
 	the <filename>mfsroot.flp</filename> floppy and replace it with
 	<filename>kern.flp</filename> before rebooting.</para>
     </sect2>
   </sect1>
 
   <sect1 id="using-sysinstall">
-    <title>Introducing Sysinstall</title>
+    <title>¤¶²Ð Sysinstall</title>
 
     <para>The <application>sysinstall</application> utility is the installation
       application provided by the FreeBSD Project.  It is console based and is
       divided into a number of menus and screens that you can use to
       configure and control the installation process.</para>
 
     <para>The <application>sysinstall</application> menu system is controlled
       by the arrow keys, <keycap>Enter</keycap>, <keycap>Space</keycap>, and
       other keys.  A detailed description of these keys and what they do is
       contained in <application>sysinstall</application>'s usage 
       information.</para>
 
     <para>To review this information, ensure that the
       <guimenuitem>Usage</guimenuitem> entry is highlighted and that the
       <guibutton>[Select]</guibutton> button is selected, as shown in <xref
       linkend="sysinstall-main3">, then press <keycap>Enter</keycap>.</para>
 
     <para>The instructions for using the menu system will be displayed.  After
       reviewing them, press <keycap>Enter</keycap> to return to the Main
       Menu.</para>
 
     <figure id="sysinstall-main3">
-      <title>Selecting Usage from Sysinstall Main Menu</title>
+      <title>¿ï¾Ü Sysinstall ¥D¿ï³æªº¡yUsage(§Ö³t»¡©ú)¡z</title>
 
       <mediaobject>
 	<imageobject>
 	  <imagedata fileref="install/main1" format="PNG">
 	</imageobject>
       </mediaobject>
     </figure>
 
     <sect2 id="select-doc">
-      <title>Selecting the Documentation Menu</title>
+      <title>¿ï¾Ü¡y Documentation(»¡©ú¤å¥ó)¡z¿ï³æ</title>
 
       <para>From the Main Menu, select <guimenuitem>Doc</guimenuitem> with
 	the arrow keys and
 	press <keycap>Enter</keycap>.</para>
 
       <figure id="main-doc">
-	<title>Selecting Documentation Menu</title>
+	<title>¿ï¾Ü¡yDocumentation(»¡©ú¤å¥ó)¡z¿ï³æ</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/main-doc" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>This will display the Documentation Menu.</para>
 
       <figure id="docmenu1">
-	<title>Sysinstall Documentation Menu</title>
+	<title>Sysinstall ªº»¡©ú¤å¥ó(Documentation)¿ï³æ</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/docmenu1" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>It is important to read the documents provided.</para>
 
       <para>To view a document, select it with the arrow keys and
 	press <keycap>Enter</keycap>.  When finished reading a document,
 	pressing <keycap>Enter</keycap> will return to the Documentation
 	Menu.</para>
 
       <para>To return to the Main Installation Menu, select
 	<guimenuitem>Exit</guimenuitem> with the 
 	arrow keys and press <keycap>Enter</keycap>.</para>
     </sect2>
 
     <sect2 id="keymap">
-      <title>Selecting the Keymap Menu</title>
+      <title>¿ï¾Ü¡yÁä½L¹ïÀ³¡z¿ï³æ</title>
 
       <para>To change the keyboard mapping, use the arrow keys to select
 	<guimenuitem>Keymap</guimenuitem> from the menu and press
 	<keycap>Enter</keycap>.  This is only required if you are
 	using a non-standard or non-US keyboard.</para>
 
       <figure id="sysinstall-keymap">
-	<title>Sysinstall Main Menu</title>
+	<title>Sysinstall ¥D¿ï³æ</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/main-keymap" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>A different keyboard mapping may be chosen by selecting the
 	menu item using up/down arrow keys and pressing <keycap>Space</keycap>.
 	Pressing <keycap>Space</keycap> again will unselect the item.
 	When finished, choose the &gui.ok; using the arrow keys and press
 	<keycap>Enter</keycap>.</para>
 
       <para>Only a partial list is shown in this screen representation.
 	Selecting &gui.cancel; by pressing <keycap>Tab</keycap> will use the default
 	keymap and return to the Main Install Menu.</para>
 
       <figure id="sysinstall-keymap-menu">
-	<title>Sysinstall Keymap Menu</title>
+	<title>Sysinstall Áä½L¹ïÀ³¿ï³æ</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/keymap" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
     </sect2>
 
     <sect2 id="viewsetoptions">
-      <title>Installation Options Screen</title>
+      <title>¦w¸Ë¿ï¶µªº³]©wµe­±</title>
 
     <para>Select <guimenuitem>Options</guimenuitem> and press
 	<keycap>Enter</keycap>.</para>
 
     <figure id="sysinstall-options">
-      <title>Sysinstall Main Menu</title>
+      <title>Sysinstall ¥D¿ï³æ</title>
 
       <mediaobject>
         <imageobject>
 	  <imagedata fileref="install/main-options" format="PNG">
 	</imageobject>
       </mediaobject>
     </figure>
 
       <figure id="options">
-	<title>Sysinstall Options</title>
+	<title>Sysinstall ¿ï¶µ³]©w</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/options" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>The default values are usually fine for most users and do
 	not need to be changed.  The release name will vary according
 	to the version being installed.</para>
 
       <para>The description of the selected item will appear at the
 	bottom of the screen highlighted in blue.  Notice that one of the
 	options is <guimenuitem>Use Defaults</guimenuitem> to reset all
 	values to startup defaults.</para>
 
       <para>Press <keycap>F1</keycap> to read the help screen about the
 	various options.</para>
 
       <para>Pressing <keycap>Q</keycap> will return to the Main Install
 	menu.</para>
     </sect2>
 
     <sect2 id="start-install">
-      <title>Begin a Standard Installation</title>
+      <title>¶}©l¶i¦æ¼Ð·Ç¦w¸Ë</title>
 
-      <para>The <guimenuitem>Standard</guimenuitem> installation is the
-	option recommended for those new to &unix; or FreeBSD.  Use the arrow
-	keys to select <guimenuitem>Standard</guimenuitem> and
-	then press <keycap>Enter</keycap> to start the installation.</para>
+      <para><guimenuitem>Standard(¼Ð·Ç)</guimenuitem>¦w¸Ë¾A¥Î©ó¨º¨Çªì±´ &unix;
+	©Î FreeBSD ªº¨Ï¥ÎªÌ¡C¥Î¤è¦VÁä¿ï¾Ü <guimenuitem>Standard</guimenuitem>
+	µM«á«ö <keycap>Enter</keycap> §Y¥i¶}©l¶i¤J¼Ð·Ç¦w¸Ë¡C</para>
 
       <figure id="sysinstall-standard">
-	<title>Begin Standard Installation</title>
+	<title>¶}©l¶i¦æ¼Ð·Ç¦w¸Ë</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/main-std" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
     </sect2>
   </sect1>
 
   <sect1 id="install-steps">
-    <title>Allocating Disk Space</title>
+    <title>µwºÐªÅ¶¡ªº¤À°t</title>
 
     <para>Your first task is to allocate disk space for FreeBSD, and label
       that space so that <application>sysinstall</application> can prepare
       it.  In order to do this you need to know how FreeBSD expects to find
       information on the disk.</para>
 
     <sect2 id="install-drive-bios-numbering">
-      <title>BIOS Drive Numbering</title>
+      <title>BIOS ºÏºÐ¾÷½s¸¹</title>
 
       <para>Before you install and configure FreeBSD on your system, there is an
 	important subject that you should be aware of, especially if you have
 	multiple hard drives.</para>
 
       <indexterm><primary>DOS</primary></indexterm>
       <indexterm><primary>Microsoft Windows</primary></indexterm>
       <para>In a PC running a BIOS-dependent operating system such as
 	&ms-dos; or &microsoft.windows;, the BIOS is able to abstract the
 	normal disk drive order, and
 	the operating system goes along with the change.  This allows the user
 	to boot from a disk drive other than the so-called <quote>primary
 	  master</quote>.  This is especially convenient for some users who have
 	found that the simplest and cheapest way to keep a system backup is to
 	buy an identical second hard drive, and perform routine copies of the
 	first drive to the second drive using 
 	<application><trademark class="registered">Ghost</trademark></application> or <application>XCOPY</application>
 	.  Then, if the
 	first drive fails, or is attacked by a virus, or is scribbled upon by an
 	operating system defect, he can easily recover by instructing the BIOS
 	to logically swap the drives.  It is like switching the cables on the
 	drives, but without having to open the case.</para>
 
       <indexterm><primary>SCSI</primary></indexterm>
       <indexterm><primary>BIOS</primary></indexterm>
       <para>More expensive systems with SCSI controllers often include BIOS
 	extensions which allow the SCSI drives to be re-ordered in a similar
 	fashion for up to seven drives.</para>
 
       <para>A user who is accustomed to taking advantage of these features may
 	become surprised when the results with FreeBSD are not as expected.
 	FreeBSD does not use the BIOS, and does not know the <quote>logical BIOS
 	  drive mapping</quote>.  This can lead to very perplexing situations,
 	especially when drives are physically identical in geometry, and have
 	also been made as data clones of one another.</para>
 
       <para>When using FreeBSD, always restore the BIOS to natural drive
 	numbering before installing FreeBSD, and then leave it that way.  If you
 	need to switch drives around, then do so, but do it the hard way, and
 	open the case and move the jumpers and cables.</para>
 
       <sidebar>
-	<title>An Illustration from the Files of Bill and Fred's Exceptional
-	  Adventures:</title>
+	<title>½d¨Ò¡GBill ¤Î Fred ªº¦w¸Ë¾úÀI</title>
       
 	<para>Bill breaks-down an older Wintel box to make another FreeBSD box
 	  for Fred.  Bill installs a single SCSI drive as SCSI unit zero and
 	  installs FreeBSD on it.</para>
 
 	<para>Fred begins using the system, but after several days notices that
 	  the older SCSI drive is reporting numerous soft errors and reports
 	  this fact to Bill.</para>
 
 	<para>After several more days, Bill decides it is time to address the
 	  situation, so he grabs an identical SCSI drive from the disk drive
 	  <quote>archive</quote> in the back room.  An initial surface scan
 	  indicates that
 	  this drive is functioning well, so Bill installs this drive as SCSI
 	  unit four and makes an image copy from drive zero to drive four.  Now
 	  that the new drive is installed and functioning nicely, Bill decides
 	  that it is a good idea to start using it, so he uses features in the
 	  SCSI BIOS to re-order the disk drives so that the system boots from
 	  SCSI unit four.  FreeBSD boots and runs just fine.</para>
 
 	<para>Fred continues his work for several days, and soon Bill and Fred
 	  decide that it is time for a new adventure &mdash; time to upgrade to a
 	  newer version of FreeBSD.  Bill removes SCSI unit zero because it was
 	  a bit flaky and replaces it with another identical disk drive from
 	  the <quote>archive</quote>.  Bill then installs the new version of
 	  FreeBSD onto the new SCSI unit zero using Fred's magic Internet FTP
 	  floppies.  The installation goes well.</para>
 
 	<para>Fred uses the new version of FreeBSD for a few days, and certifies
 	  that it is good enough for use in the engineering department.  It is
 	  time to copy all of his work from the old version.  So Fred mounts
 	  SCSI unit four (the latest copy of the older FreeBSD version).  Fred
 	  is dismayed to find that none of his precious work is present on SCSI
 	  unit four.</para>
 
 	<para>Where did the data go?</para>
 
 	<para>When Bill made an image copy of the original SCSI unit zero onto
 	  SCSI unit four, unit four became the <quote>new clone</quote>.
 	  When Bill re-ordered the SCSI BIOS so that he could boot from
 	  SCSI unit four, he was only fooling himself.
 	  FreeBSD was still running on SCSI unit zero.
 	  Making this kind of BIOS change will cause some or all of the Boot and
 	  Loader code to be fetched from the selected BIOS drive, but when the
 	  FreeBSD kernel drivers take-over, the BIOS drive numbering will be
 	  ignored, and FreeBSD will transition back to normal drive numbering.
 	  In the illustration at hand, the system continued to operate on the
 	  original SCSI unit zero, and all of Fred's data was there, not on SCSI
 	  unit four.  The fact that the system appeared to be running on SCSI
 	  unit four was simply an artifact of human expectations.</para>
 
 	<para>We are delighted to mention that no data bytes were killed or
 	  harmed in any way by our discovery of this phenomenon.  The older SCSI
 	  unit zero was retrieved from the bone pile, and all of Fred's work was
 	  returned to him, (and now Bill knows that he can count as high as
 	  zero).</para>
 
 	<para>Although SCSI drives were used in this illustration, the concepts
 	  apply equally to IDE drives.</para>
       </sidebar>
     </sect2>
 
     <sect2 id="main-fdisk">
-      <title>Creating Slices Using FDisk</title>
+      <title>¥H FDisk ¨Ó«Ø¥ß¤À³ÎºÏ°Ï(Slices)</title>
 
       <note>
 	<para>No changes you make at this point will be written to the disk.
 	  If you think you have made a mistake and want to start again you can
 	  use the menus to exit <application>sysinstall</application> and try
 	  again or press <keycap>U</keycap> to use the <guimenuitem>Undo</guimenuitem> option.
 	  If you get confused and can not see how to exit you can
 	  always turn your computer off.</para>
       </note>
 
       <para>After choosing to begin a standard installation in
 	<application>sysinstall</application> you will be shown this
 	message:</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>Press <keycap>Enter</keycap> as instructed.  You will then be
 	shown a list of all the hard drives that the kernel found when it
 	carried out the device probes.  
 	<xref linkend="sysinstall-fdisk-drive1"> shows an example from a
 	system with two IDE disks.  They have been called
 	<devicename>ad0</devicename> and <devicename>ad2</devicename>.</para>
 
       <figure id="sysinstall-fdisk-drive1">
-	<title>Select Drive for FDisk</title>
+	<title>¿ï¾Ü FDisk ­n¤À³ÎªºµwºÐ</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/fdisk-drive1" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>You might be wondering why <devicename>ad1</devicename> is not
 	listed here.  Why has it been missed?</para>
 
       <para>Consider what would happen if you had two IDE hard disks, one
 	as the master on the first IDE controller, and one as the master on
 	the second IDE controller.  If FreeBSD numbered these as it found
 	them, as <devicename>ad0</devicename> and
 	<devicename>ad1</devicename> then everything would work.</para>
 
       <para>But if you then added a third disk, as the slave device on the
 	first IDE controller, it would now be <devicename>ad1</devicename>,
 	and the previous <devicename>ad1</devicename> would become
 	<devicename>ad2</devicename>.  Because device names (such as
 	<devicename>ad1s1a</devicename>) are used to find filesystems, you
 	may suddenly discover that some of your filesystems no longer
 	appear correctly, and you would need to change your FreeBSD
 	configuration.</para>
       
       <para>To work around this, the kernel can be configured to name IDE
 	disks based on where they are, and not the order in which they were
 	found.  With this scheme the master disk on the second IDE
 	controller will <emphasis>always</emphasis> be
 	<devicename>ad2</devicename>, even if there are no
 	<devicename>ad0</devicename> or <devicename>ad1</devicename>
 	devices.</para>
 
       <para>This configuration is the default for the FreeBSD kernel, which
 	is why this display shows <devicename>ad0</devicename> and
 	<devicename>ad2</devicename>.  The machine on which this screenshot
 	was taken had IDE disks on both master channels of the IDE
 	controllers, and no disks on the slave channels.</para>
 
       <para>You should select the disk on which you want to install FreeBSD,
 	and then press &gui.ok;.
 	<application>FDisk</application> will start, with a display similar to
 	that shown in <xref linkend="sysinstall-fdisk1">.</para>
 
       <para>The <application>FDisk</application> display is broken into three
 	sections.</para>
 
       <para>The first section, covering the first two lines of the display,
 	shows details about the currently selected disk, including its FreeBSD
 	name, the disk geometry, and the total size of the disk.</para>
 
       <para>The second section shows the slices that are currently on the
 	disk, where they start and end, how large they are, the name FreeBSD
 	gives them, and their description and sub-type.  This example shows two
 	small unused slices, which are artifacts of disk layout schemes on the
 	PC.  It also shows one large <acronym>FAT</acronym> slice, which almost certainly appears
 	as <devicename>C:</devicename> in &ms-dos; / &windows;, and an extended
 	slice, which may contain other drive letters for &ms-dos; / &windows;.</para>
 
       <para>The third section shows the commands that are available in
 	<application>FDisk</application>.</para>
 
       <figure id="sysinstall-fdisk1">
-	<title>Typical Fdisk Partitions before Editing</title>
+	<title>(Á|¨Ò)¥¼½s¿è«eªº Fdisk ¤À³Î°Ï(Partition)</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/fdisk-edit1" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>What you do now will depend on how you want to slice up your
 	disk.</para>
 
       <para>If you want to use FreeBSD for the entire disk (which will delete
 	all the other data on this disk when you confirm that you want
 	<application>sysinstall</application> to continue later in the
 	installation process) then you can press <keycap>A</keycap>, which
 	corresponds to the <guimenuitem>Use Entire Disk</guimenuitem> option.
 	The existing slices will be removed, and replaced with a small area
 	flagged as <literal>unused</literal> (again, an artifact of PC disk
 	layout), and then one large slice for FreeBSD.  If you do this, then
 	you should select the newly created FreeBSD slice using the arrow
 	keys, and press <keycap>S</keycap> to mark the slice as being
 	bootable.  The screen will then look very similar to 
 	<xref linkend="sysinstall-fdisk2">.  Note the
 	<literal>A</literal> in the <literal>Flags</literal> column, which
 	indicates that this slice is <emphasis>active</emphasis>, and will be
 	booted from.</para>
 
       <para>If you will be deleting an existing slice to make space for
 	FreeBSD then you should select the slice using the arrow keys, and
 	then press <keycap>D</keycap>.  You can then press <keycap>C</keycap>,
 	and be prompted for size of slice you want to create.  Enter the
 	appropriate figure and press <keycap>Enter</keycap>.  The default
         value in this box represents the largest possible slice you can
 	make, which could be the largest contiguous block of unallocated
 	space or the size of the entire hard disk.</para>
       
       <para>If you have already made space for FreeBSD (perhaps by using a
 	tool such as <application>&partitionmagic;</application>) then you can
 	press <keycap>C</keycap> to create a new slice.  Again, you will be
 	prompted for the size of slice you would like to create.</para>
 
       <figure id="sysinstall-fdisk2">
-	<title>Fdisk Partition Using Entire Disk</title>
+	<title>Fdisk ±Ä¥Î¾ãÁûµwºÐ§@¤À³Î°Ï(Partition)</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/fdisk-edit2" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>When finished, press <keycap>Q</keycap>.  Your changes will be
 	saved in <application>sysinstall</application>, but will not yet be
 	written to disk.</para>
     </sect2>
 
     <sect2 id="bootmgr">
-      <title>Install a Boot Manager</title>
+      <title>¦w¸Ë Boot Manager</title>
 
       <para>You now have the option to install a boot manager.  In general,
 	you should choose to install the FreeBSD boot manager if:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>You have more than one drive, and have installed FreeBSD onto
 	    a drive other than the first one.</para>
 	</listitem>
 
 	<listitem>
 	  <para>You have installed FreeBSD alongside another operating system
 	    on the same disk, and you want to choose whether to start FreeBSD
 	    or the other operating system when you start the computer.</para>
 	</listitem>
       </itemizedlist>
 
       <para>If FreeBSD is going to be the only operating system on
 	this machine, installed on the first hard disk, then the
 	<guimenuitem>Standard</guimenuitem> boot manager will suffice.
 	Choose <guimenuitem>None</guimenuitem> if you are using a
 	third-party boot manager capable of booting FreeBSD.</para>
 
       <para>Make your choice and press <keycap>Enter</keycap>.</para>
 
       <figure id="sysinstall-bootmgr">
-	<title>Sysinstall Boot Manager Menu</title>
+	<title>Sysinstall ªº Boot Manager ¿ï³æ</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/boot-mgr" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>The help screen, reached by pressing <keycap>F1</keycap>,
 	discusses the problems that can be encountered when trying to share
 	the hard disk between operating systems.</para>
     </sect2>
 
     <sect2>
-      <title>Creating Slices on Another Drive</title>
+      <title>¦b¨ä¥LµwºÐ¤W«Ø¥ß¤À³ÎºÏ°Ï(Slices)</title>
 
       <para>If there is more than one drive, it will return to the
 	Select Drives screen after the boot manager selection.  If you wish to
 	install FreeBSD on to more than one disk, then you can select another
 	disk here and repeat the slice process using
 	<application>FDisk</application>.</para>
 
       <important>
 	<para>If you are installing FreeBSD on a drive other than your
 	  first, then the FreeBSD boot manager needs to be installed on
 	  both drives.</para>
       </important>
 
       <figure id="sysinstall-fdisk-drive2">
-	<title>Exit Select Drive</title>
+	<title>Â÷¶}¡y¿ï¾ÜµwºÐ¡zµe­±</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/fdisk-drive2" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>The <keycap>Tab</keycap> key toggles between the last drive
 	selected, &gui.ok;, and 
 	&gui.cancel;.</para>
 
       <para>Press the <keycap>Tab</keycap> once to toggle to the
 	&gui.ok;, then
 	press <keycap>Enter</keycap>
 	to continue with the installation.</para>
     </sect2>
 
     <sect2 id="disklabeleditor">
-      <title>Creating Partitions Using
-	<application>Disklabel</application></title>
+      <title>¥H <application>Disklabel</application> ¨Ó«Ø¥ß¤À³Î°Ï(Partitions)
+	</title>
       
       <para>You must now create some partitions inside each slice that you
 	have just created.  Remember that each partition is lettered, from
 	<literal>a</literal> through to <literal>h</literal>, and that
 	partitions <literal>b</literal>, <literal>c</literal>, and
 	<literal>d</literal> have conventional meanings that you should adhere
 	to.</para>
 
       <para>Certain applications can benefit from particular partition
 	schemes, especially if you are laying out partitions across more than
 	one disk.  However, for this, your first FreeBSD installation, you do
 	not need to give too much thought to how you partition the disk.  It
 	is more important that you install FreeBSD and start learning how to
 	use it.  You can always re-install FreeBSD to change your partition
 	scheme when you are more familiar with the operating system.</para>
 
       <para>This scheme features four partitions&mdash;one for swap space, and
 	three for filesystems.</para>
 
       <table frame="none" pgwide="1">
-	<title>Partition Layout for First Disk</title>
+	<title>²Ä¤@ÁûµwºÐªº¤À³Î°Ï(Partition)°t¸m</title>
 
 	<tgroup cols="4">
           <colspec colwidth="1*">
           <colspec colwidth="1*">
           <colspec colwidth="1*">
           <colspec colwidth="4*">
 
 	  <thead>
 	    <row>
 	      <entry>Partition</entry>
 	      
 	      <entry>Filesystem</entry>
 
 	      <entry>Size</entry>
 
 	      <entry>Description</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry><literal>a</literal></entry>
 
 	      <entry><filename>/</filename></entry>
 
 	      <entry>100&nbsp;MB</entry>
 
 	      <entry>This is the root filesystem.  Every other filesystem
 		will be mounted somewhere under this one.  100&nbsp;MB is a
 		reasonable size for this filesystem.  You will not be storing
 		too much data on it, as a regular FreeBSD install will put
 		about 40&nbsp;MB of data here.  The remaining space is for temporary
 		data, and also leaves expansion space if future versions of
 		FreeBSD need more space in <filename>/</filename>.</entry>
 	    </row>
 
 	    <row>
 	      <entry><literal>b</literal></entry>
 
 	      <entry>N/A</entry>
 
 	      <entry>2-3 x RAM</entry>
 
 	      <entry><para>The system's swap space is kept on this partition.
 		  Choosing the right amount of swap space can be a bit of an
 		  art.  A good rule of thumb is that your swap
 		  space should be two or three times as much as the
 		  available physical memory (RAM).
 		  You should also have at least 64&nbsp;MB of swap, so if you have
 		  less than 32&nbsp;MB of RAM in your computer then set the swap
 		  amount to 64&nbsp;MB.</para><para>
 
 		  If you have more than one disk then you can put swap
 		  space on each disk.  FreeBSD will then use each disk for 
 		  swap, which effectively speeds up the act of swapping.  In
 		  this case, calculate the total amount of swap you need
 		  (e.g., 128&nbsp;MB), and then divide this by the number of disks
 		  you have (e.g., two disks) to give the amount of swap you
 		  should put on each disk, in this example, 64&nbsp;MB of swap per
 		  disk.</para></entry>
 	    </row>
 
 	    <row>
 	      <entry><literal>e</literal></entry>
 
 	      <entry><filename>/var</filename></entry>
 
 	      <entry>50&nbsp;MB</entry>
 
 	      <entry>The <filename>/var</filename> directory contains
 		files that are constantly varying;
 		log files, and other administrative files.  Many
 		of these files are read-from or written-to extensively during
 		FreeBSD's day-to-day running.  Putting these files on another
 		filesystem allows FreeBSD to optimize the access of these
 		files without affecting other files in other directories that
 		do not have the same access pattern.</entry>
 	    </row>
 
 	    <row>
 	      <entry><literal>f</literal></entry>
 
 	      <entry><filename>/usr</filename></entry>
 
 	      <entry>Rest of disk</entry>
 
 	      <entry>All your other files will typically be stored in
 		<filename>/usr</filename> and its subdirectories.</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </table>
       
       <para>If you will be installing FreeBSD on to more than one disk then
 	you must also create partitions in the other slices that you
 	configured.  The easiest way to do this is to create two partitions on
 	each disk, one for the swap space, and one for a filesystem.</para>
 
       <table frame="none" pgwide="1">
-	<title>Partition Layout for Subsequent Disks</title>
+	<title>¨ä¥LµwºÐªº¤À³Î°Ï(Partition)°t¸m</title>
 
 	<tgroup cols="4">
           <colspec colwidth="1*">
           <colspec colwidth="1*">
           <colspec colwidth="2*">
           <colspec colwidth="3*">
 
 	  <thead>
 	    <row>
 	      <entry>Partition</entry>
 	      
 	      <entry>Filesystem</entry>
 
 	      <entry>Size</entry>
 
 	      <entry>Description</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry><literal>b</literal></entry>
 
 	      <entry>N/A</entry>
 
 	      <entry>See description</entry>
 
 	      <entry>As already discussed, you can split swap space across
 		each disk.  Even though the <literal>a</literal> partition is
 		free, convention dictates that swap space stays on the
 		<literal>b</literal> partition.</entry>
 	    </row>
 
 	    <row>
 	      <entry><literal>e</literal></entry>
 
 	      <entry>/disk<replaceable>n</replaceable></entry>
 
 	      <entry>Rest of disk</entry>
 
 	      <entry>The rest of the disk is taken up with one big partition.
 		This could easily be put on the <literal>a</literal>
 		partition, instead of the <literal>e</literal> partition.
 		However, convention says that the <literal>a</literal>
 		partition on a slice is reserved for the filesystem that will
 		be the root (<filename>/</filename>) filesystem.  You do not
 		have to follow this convention, but
 		<application>sysinstall</application> does, so following it
 		yourself makes the installation slightly cleaner.  You can
 		choose to mount this filesystem anywhere; this example
 		suggests that you mount them as directories
 		<filename>/disk<replaceable>n</replaceable></filename>, where
 		<replaceable>n</replaceable> is a number that changes for each
 		disk.  But you can use another scheme if you prefer.</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </table>
 
       <para>Having chosen your partition layout you can now create it using
 	<application>sysinstall</application>.  You will see this
 	message:</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>Press <keycap>Enter</keycap> to start the FreeBSD partition
 	editor, called <application>Disklabel</application>.</para>
 
       <para><xref linkend="sysinstall-label"> shows the display when you first
 	start <application>Disklabel</application>.  The display is divided in
 	to three sections.</para>
 
       <para>The first few lines show the name of the disk you are currently
 	working on, and the slice that contains the partitions you are
 	creating (at this point <application>Disklabel</application> calls
 	this the <literal>Partition name</literal> rather than slice name).
 	This display also shows the amount of free space within the slice;
 	that is, space that was set aside in the slice, but that has not yet
 	been assigned to a partition.</para>
 
       <para>The middle of the display shows the partitions that have been
 	created, the name of the filesystem that each partition contains,
 	their size, and some options pertaining to the creation of the
 	filesystem.</para>
 
       <para>The bottom third of the screen shows the keystrokes that are valid
 	in <application>Disklabel</application>.</para>
 
       <figure id="sysinstall-label">
-	<title>Sysinstall Disklabel Editor</title>
+	<title>Sysinstall ªº Disklabel ½s¿è¾¹</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/disklabel-ed1" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para><application>Disklabel</application> can automatically create
 	partitions for you and assign them default sizes.  Try this now, by
 	Pressing <keycap>A</keycap>.  You will see a display similar to that
 	shown in <xref linkend="sysinstall-label2">.  Depending on the size of
 	the disk you are using, the defaults may or may not be appropriate.
 	This does not matter, as you do not have to accept the
 	defaults.</para>
 
 	<note>
 	  <para>Beginning with FreeBSD&nbsp;4.5, the default partitioning assigns
 	    the <filename>/tmp</filename> directory its own partition instead
 	    of being part of the <filename>/</filename> partition.  This
 	    helps avoid filling the <filename>/</filename> partition with
 	    temporary files.</para>
 	</note>
 
       <figure id="sysinstall-label2">
-	<title>Sysinstall Disklabel Editor with Auto Defaults</title>
+	<title>Sysinstall ªº Disklabel ½s¿è¾¹ ¡X ¨Ï¥Î¦Û°Ê¤À°t</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/disklabel-auto" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>If you choose to not use the default partitions and wish to
 	replace them with your
 	own, use the arrow keys to select the first partition, and press
 	<keycap>D</keycap> to delete it.  Repeat this to delete all the
 	suggested partitions.</para>
 
       <para>To create the first partition (<literal>a</literal>, mounted as
 	<filename>/</filename> &mdash; root), make sure the proper disk slice at the top of
 	the screen is selected and press <keycap>C</keycap>.  A dialog box
 	will appear prompting you for the size of the new partition (as shown
 	in <xref linkend="sysinstall-label-add">).  You can enter the size as
 	the number of disk blocks you want to use, or as a
 	number followed by either <literal>M</literal> for megabytes,
 	<literal>G</literal> for gigabytes, or <literal>C</literal> for
 	cylinders.</para>
 
       <note><para>Beginning with FreeBSD&nbsp;5.X, users can: select
 	<acronym>UFS2</acronym> (which is default on &os;&nbsp;5.1 and
 	above) using the <literal>Custom Newfs</literal>
 	(<keycap>Z</keycap>) option, create labels with
 	<literal>Auto Defaults</literal> and modify them with the <literal>Custom Newfs</literal> option or
 	add <option>-O 2</option> during the regular creation period.
 	Do not forget to add <option>-U</option> for SoftUpdates if you use the <literal>Custom Newfs</literal>
 	option!</para></note>
 
       <figure id="sysinstall-label-add">
 	<title>Free Space for Root Partition</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/disklabel-root1" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>The default size shown will create a partition that takes up the
 	rest of the slice.  If you are using the partition sizes described
 	in the earlier example, then delete the existing figure using
 	<keycap>Backspace</keycap>, and then type in
 	<userinput>64M</userinput>, as shown in 
 	<xref linkend="sysinstall-label-add2">.  Then press
 	&gui.ok;.</para>
       
       <figure id="sysinstall-label-add2">
 	<title>Edit Root Partition Size</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/disklabel-root2" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Having chosen the partition's size you will then be asked whether
 	this partition will contain a filesystem or swap space.  The dialog
 	box is shown in <xref linkend="sysinstall-label-type">.  This first
 	partition will contain a filesystem, so check that
 	<guimenuitem>FS</guimenuitem> is selected and press
 	<keycap>Enter</keycap>.</para>
 
       <figure id="sysinstall-label-type">
 	<title>Choose the Root Partition Type</title>
 	
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/disklabel-fs" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
       
       <para>Finally, because you are creating a filesystem, you must tell
 	<application>Disklabel</application> where the filesystem is to be
 	mounted.  The dialog box is shown in 
 	<xref linkend="sysinstall-label-mount">.  The root filesystem's mount
 	point is <filename>/</filename>, so type <userinput>/</userinput>, and
 	then press <keycap>Enter</keycap>.</para>
 
       <figure id="sysinstall-label-mount">
 	<title>Choose the Root Mount Point</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/disklabel-root3" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>The display will then update to show you the newly created
 	partition.  You should repeat this procedure for the other
 	partitions.  When you create the swap partition, you will not be
 	prompted for the filesystem mount point, as swap partitions are never
 	mounted.  When you create the final partition,
 	<filename>/usr</filename>, you can leave the suggested size as is, to
 	use the rest of the slice.</para>
 
       <para>Your final FreeBSD DiskLabel Editor screen will appear similar to
 	<xref linkend="sysinstall-label4">, although your values chosen may
 	be different.  Press <keycap>Q</keycap> to finish.</para>
 
       <figure id="sysinstall-label4">
 	<title>Sysinstall Disklabel Editor</title>
 	
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/disklabel-ed2" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
     </sect2>
   </sect1>
 
   <sect1 id="install-choosing">
-    <title>Choosing What to Install</title>
+    <title>¿ï¾Ü·Q­n¦w¸Ëªº</title>
 
     <sect2 id="distset">
-      <title>Select the Distribution Set</title>
+      <title>¿ï¾Ü­n¦w¸Ëªº®M¥ó¶°(Distribution Set)</title>
 
       <para>Deciding which distribution set to install will depend largely
 	on the intended use of the system and the amount of disk space
 	available.  The predefined options range from installing the
 	smallest possible configuration to everything.  Those who are
 	new to &unix; and/or FreeBSD should almost certainly select one
 	of these canned options.  Customizing a distribution set is
 	typically for the more experienced user.</para>
 
       <para>Press <keycap>F1</keycap> for more information on the 
 	distribution set options and what they contain.  When finished
 	reviewing the help, pressing <keycap>Enter</keycap> will return
 	to the Select Distributions Menu.</para>
 
       <para>If a graphical user interface is desired then a distribution
 	set that is preceded by an <literal>X</literal> should be
 	chosen.  The configuration of the X server and selection of a default
 	desktop must be done after the installation of &os;.  More
 	information regarding the configuration of a X server can be
 	found in <xref linkend="x11">.</para>
 
       <para>The default version of X11 that is installed depends on the
 	version of FreeBSD that you are installing.  For FreeBSD versions
 	prior to 5.3, <application>&xfree86;&nbsp;4.X</application> is installed.  For &os;&nbsp;5.3 and later,
 	<application>&xorg;</application> is the default.</para>
 
       <para>If compiling a custom kernel is anticipated, select an option
 	which includes the source code.  For more information on why a
 	custom kernel should be built or how to build a custom kernel, see
 	<xref linkend="kernelconfig">.</para>
 
       <para>Obviously, the most versatile system is one that includes
 	everything.  If there is adequate disk space, select 
 	<guimenuitem>All</guimenuitem> as shown in
 	<xref linkend="distribution-set1"> by using the arrow keys and
 	press <keycap>Enter</keycap>.  If there is a concern about disk
 	space consider using an option that is more suitable for the
 	situation.
 	Do not fret over the perfect choice, as other distributions can be
 	added after installation.</para>
 
       <figure id="distribution-set1">
-	<title>Choose Distributions</title>
+	<title>¿ï¾Ü®M¥ó(Distributions)</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/dist-set" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
     </sect2>
 
     <sect2 id="portscol">
-      <title>Installing the Ports Collection</title>
+      <title>¦w¸Ë Ports Collection</title>
 
       <para>After selecting the desired distribution, an opportunity to
 	install the FreeBSD Ports Collection is presented.  The ports
 	collection is an easy and convenient way to install software.
 	The Ports Collection does not contain the source code necessary
 	to compile the software.  Instead, it is a collection of files which
 	automates the downloading, compiling and installation
 	of third-party software packages.
 	<xref linkend="ports"> discusses how to use the ports
 	collection.</para>
 
       <para>The installation program does not check to see if you have
 	adequate space.  Select this option only if you have
 	adequate hard disk space. As of FreeBSD &rel.current;, the FreeBSD
 	Ports Collection takes up about &ports.size; of disk space.
 	You can safely assume a larger value for more recent versions
 	of FreeBSD.</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 & the latest ports,
  visit: 
      http://www.FreeBSD.org/ports  
 
                               [ Yes ]     No</screen>
 
       <para>Select &gui.yes; with the arrow keys to
 	install the Ports Collection or &gui.no; to
 	skip this option.  Press <keycap>Enter</keycap> to continue.
 	The Choose Distributions menu will redisplay.</para>
 
       <figure id="distribution-set2">
 	<title>Confirm Distributions</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/dist-set2" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>If satisfied with the options, select
 	<guimenuitem>Exit</guimenuitem> with the arrow keys, ensure that
 	&gui.ok; is highlighted, and pressing
 	<keycap>Enter</keycap> to continue.</para>
 
     </sect2>
   </sect1>
 
   <sect1 id="install-media">
-    <title>Choosing Your Installation Media</title>
+    <title>¿ï¾Ü¦w¸Ë¨Ó·½</title>
 
     <para>If Installing from a CDROM or DVD, use the arrow keys to highlight 
       <guimenuitem>Install from a FreeBSD CD/DVD</guimenuitem>.  Ensure
       that &gui.ok; is highlighted, then press
       <keycap>Enter</keycap> to proceed with the installation.</para>
     
     <para>For other methods of installation, select the appropriate
       option and follow the instructions.</para>
 
     <para>Press <keycap>F1</keycap> to display the Online Help for
       installation media.  Press <keycap>Enter</keycap> to return
       to the media selection menu.</para>
 
     <figure id="choose-media">
-      <title>Choose Installation Media</title>
+      <title>¿ï¾Ü¦w¸Ë¨Ó·½</title>
 
       <mediaobject>
 	<imageobject>
 	  <imagedata fileref="install/media" format="PNG">
 	</imageobject>
       </mediaobject>
     </figure>
 
     <note>
-      <title>FTP Installation Modes</title>
+      <title>FTP ¦w¸Ë¼Ò¦¡</title>
 
       <indexterm>
 	<primary>installation</primary>
 	<secondary>network</secondary>
 	<tertiary>FTP</tertiary>
       </indexterm>
       
       <para>There are three FTP installation modes you can choose from:
 	active FTP, passive FTP, or via a HTTP proxy.</para>
 
       <variablelist>
 	<varlistentry>
 	  <term>FTP Active: <guimenuitem>Install from an FTP
 	      server</guimenuitem></term>
 	  
 	  <listitem>
 	    <para>This option will make all FTP transfers 
 	      use <quote>Active</quote>
 	      mode.  This will not work through firewalls, but will
 	      often work with older FTP servers that do not support
 	      passive mode.  If your connection hangs with passive
 	      mode (the default), try active!</para>
 	  </listitem>
 	</varlistentry>
 	
 	<varlistentry>
 	  <term>FTP Passive: <guimenuitem>Install from an FTP server through a
 	      firewall</guimenuitem></term>
 	  
 	  <listitem>
 	    <indexterm>
 	      <primary>FTP</primary>
 	      <secondary>passive mode</secondary>
 	    </indexterm>
 
 	    <para>This option instructs <application>sysinstall</application> to use 
 	      <quote>Passive</quote> mode for all FTP operations.  
 	      This allows the user to pass through firewalls
 	      that do not allow incoming connections on random TCP ports.
 	    </para>
 	  </listitem>
 	</varlistentry>
 	
 	<varlistentry>
 	  <term>FTP via a HTTP proxy: <guimenuitem>Install from an FTP server
 	      through a http proxy</guimenuitem></term>
 	    
 	  <listitem>
 	    <indexterm>
 	      <primary>FTP</primary>
 	      <secondary>via a HTTP proxy</secondary>
 	    </indexterm>
 	    
 	    <para>This option instructs <application>sysinstall</application> to use the HTTP
 	      protocol (like a web browser) to connect to a proxy
 	      for all FTP operations.  The proxy will translate
 	      the requests and send them to the FTP server.
 	      This allows the user to pass through firewalls
 	      that do not allow FTP at all, but offer a HTTP
 	      proxy.
 	      In this case, you have to specify the proxy in
 	      addition to the FTP server.</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
       
       <para>For a proxy FTP server, you should usually give the name of the
 	server you really want as a part of the username, after an
 	<quote>@</quote> sign.  The proxy server then <quote>fakes</quote>
 	the real server.  For example, assuming you want to install from
 	<hostid role="fqdn">ftp.FreeBSD.org</hostid>, using the proxy FTP
 	server <hostid role="fqdn">foo.example.com</hostid>, listening on port
 	1024.</para>
       
       <para>In this case, you go to the options menu, set the FTP username
 	to <literal>ftp@ftp.FreeBSD.org</literal>, and the password to your
 	email address.  As your installation media, you specify FTP (or
 	passive FTP, if the proxy supports it), and the URL
 	<literal>ftp://foo.example.com:1234/pub/FreeBSD</literal>.</para>
 
       <para>Since <filename>/pub/FreeBSD</filename> from 
 	<hostid role="fqdn">ftp.FreeBSD.org</hostid> is proxied under 
 	<hostid role="fqdn">foo.example.com</hostid>, you are able to install
 	from <emphasis>that</emphasis> machine (which will fetch the files
 	from <hostid role="fqdn">ftp.FreeBSD.org</hostid> as your 
 	installation requests them).</para>
     </note>
   </sect1>
 
   <sect1 id="install-final-warning">
-    <title>Committing to the Installation</title>
+    <title>¶}©l¶i¦æ¦w¸Ë</title>
+
 
-    <para>The installation can now proceed if desired.  This is also
-      the last chance for aborting the installation to prevent changes
-      to the hard drive.</para>
+    <para>¨ì¦¹¬°¤î¡A¥i¥H¶}©l¶i¦æ¦w¸Ë¤F¡A³o¤]¬O±zÁקK§ó°Ê¨ìµwºÐªº³Ì«á¾÷·|¡C</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>Select &gui.yes; and press 
-      <keycap>Enter</keycap> to proceed.</para>
+    <para>¿ï¾Ü &gui.yes; ¨Ã«ö¤U 
+      <keycap>Enter</keycap>¥H½T»{¯uªº­n¶}©l¦w¸Ë</para>
 
-    <para>The installation time will vary according to the distribution
-      chosen, installation media, and the speed of the computer.
-      There will be a series of
-      messages displayed indicating the status.</para>
+    <para>¦w¸Ë©Ò»Ý®É¶¡·|¨Ì¾Ú©Ò¿ï¾Ü¦w¸Ëªº®M¥ó¶°(distribution)
+      ¡B¦w¸Ë¨Ó·½¥H¤Î¹q¸£³t«×¦Ó¦³©Ò¤£¦P¡C
+      ¦b¦w¸Ëªº¹Lµ{¤¤¡A·|¦³¤@¨Ç°T®§Åã¥Ü¥Ø«eªº¦w¸Ë¶i«×¡C</para>
     
-    <para>The installation is complete when the following message is
-      displayed:</para>
+    <para>·í±z¬Ý¨ì¤U­±ªº°T®§ªí¥Ü¤w¸g¦w¸Ë§¹¦¨¤F¡J</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>Press <keycap>Enter</keycap> to proceed with post-installation
       configurations.</para>
 
     <para>Selecting &gui.no; and pressing
       <keycap>Enter</keycap> will abort
       the installation so no changes will be made to your system.  The
       following message will appear:</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>This message is generated because nothing was installed.
       Pressing <keycap>Enter</keycap> will return to the
       Main Installation Menu to exit the installation.</para>
   </sect1>
 
   <sect1 id="install-post">
     <title>«áÄò¦w¸Ë</title>
 
     <para>¦w¸Ë¨t²Î¦¨¥\¤§«á¡A¥i¥H¦b·s¸Ë¦nªº FreeBSD 
       ­«¶}¾÷¤§«e¡A©ÎªÌ¬O¨Æ«á¦A³z¹L <command>sysinstall</command>
       (&os; 5.2 ¤§«eª©¥»«h¬O <command>/stand/sysinstall</command>) µM«á¿ï¾Ü
       <guimenuitem>Configure</guimenuitem> ¿ï¶µ¥H¶i¦æ«áÄò³]©w¡C</para>
 
     <sect2 id="inst-network-dev">
       <title>Network Device Configuration</title>
 
       <para>If you previously configured PPP for an FTP install, this screen
 	will not display and can be configured later as described
 	above.</para>
 
       <para>For detailed information on Local Area Networks and
 	configuring FreeBSD as a gateway/router refer to the
 	<link linkend="advanced-networking">Advanced Networking</link>
 	chapter.</para>
 
       <screen>                      User Confirmation Requested 
    Would you like to configure any Ethernet or SLIP/PPP network devices?
 
                              [ Yes ]   No</screen>
 
       <para>To configure a network device, select
 	&gui.yes; and press <keycap>Enter</keycap>.
       Otherwise, select &gui.no; to continue.</para>
 
       <figure id="ed-config1">
 	<title>Selecting an Ethernet Device</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/ed0-conf" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Select the interface to be configured with the arrow keys and press
 	<keycap>Enter</keycap>.</para>
 
       <screen>                      User Confirmation Requested 
        Do you want to try IPv6 configuration of the interface?
 
                               Yes   [ No ]</screen>
 
       <para>In this private local area network, the current Internet
 	type protocol (<acronym>IPv4</acronym>) was sufficient and &gui.no;
 	was selected with the arrow keys and <keycap>Enter</keycap>
 	pressed.</para>
 
       <para>If you are connected to an existing <acronym>IPv6</acronym> network
 	with an <acronym>RA</acronym> server, then choose
 	&gui.yes; and press <keycap>Enter</keycap>.
 	It will take several seconds to scan for RA servers.</para>
 
       <screen>                             User Confirmation Requested 
         Do you want to try DHCP configuration of the interface?
 
                               Yes   [ No ]</screen>
 
       <para>If DHCP (Dynamic Host Configuration Protocol) is not required
 	select &gui.no; with the arrow keys and press
 	<keycap>Enter</keycap>.</para>
 
       <para>Selecting &gui.yes; will execute
 	<application>dhclient</application>, and if successful, will fill
 	in the network configuration information automatically.  Refer to
 	<xref linkend="network-dhcp"> for more information.</para>
 
       <para>The following Network Configuration screen shows the
 	configuration of the Ethernet device for a system that will act
 	as the gateway for a Local Area Network.</para>
 
       <figure id="ed-config2">
 	<title>Set Network Configuration for ed0</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/ed0-conf2" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Use <keycap>Tab</keycap> to select the information fields and
 	fill in appropriate information:</para>
 
       <variablelist>
 	<varlistentry>
 	  <term>Host</term>
 
 	  <listitem>
 	    <para>The fully-qualified hostname, such as <hostid role="fqdn">k6-2.example.com</hostid> in
 	      this case.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Domain</term>
 
 	  <listitem>
 	    <para>The name of the domain that your machine is
 	      in, such as <hostid role="domainname">example.com</hostid> for this case.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>IPv4 Gateway</term>
 
 	  <listitem>
 	    <para>IP address of host forwarding packets to non-local
 	      destinations.  You must fill this in if the machine is a node
 	      on the network.  <emphasis>Leave this field blank</emphasis>
 	      if the machine is the gateway to the Internet for the
 	      network.  The IPv4 Gateway is also known as the default
 	      gateway or default route.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Name server</term>
 
 	  <listitem>
 	    <para>IP address of your local DNS server.  There is no local
 	      DNS server on this private local area network so the IP
 	      address of the provider's DNS server
 	      (<hostid role="ipaddr">208.163.10.2</hostid>) was used.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>IPv4 address</term>
 
 	  <listitem>
 	    <para>The IP address to be used for this interface was
 	      <hostid role="ipaddr">192.168.0.1</hostid></para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Netmask</term>
 
 	  <listitem>
 	    <para>The address block being used for this local area
 	      network is a Class C block
 	      (<hostid role="ipaddr">192.168.0.0</hostid> -
 	      <hostid role="ipaddr">192.168.255.255</hostid>).
 	      The default netmask is for a Class C network
 	      (<hostid role="netmask">255.255.255.0</hostid>).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Extra options to ifconfig</term>
 
 	  <listitem>
 	    <para>Any interface-specific options to <command>ifconfig</command>
 	      you would like to add.  There were none in this case.</para>
 	  </listitem>
 	</varlistentry>
 
       </variablelist>
 
       <para>Use <keycap>Tab</keycap> to select &gui.ok;
 	when finished and press <keycap>Enter</keycap>.</para>
 
 
       <screen>                      User Confirmation Requested 
         Would you like to Bring Up the ed0 interface right now?
 
                              [ Yes ]   No</screen>
 
       <para>Choosing &gui.yes; and pressing
 	<keycap>Enter</keycap> will bring
 	the machine up on the network and be ready for use.  However,
 	this does not accomplish much during installation, since
 	the machine still needs to be rebooted.</para>
     </sect2>
 
     <sect2 id="gateway">
       <title>Configure Gateway</title>
 
       <screen>                       User Confirmation Requested 
        Do you want this machine to function as a network gateway?
 
                               [ Yes ]    No</screen>
 
       <para>If the machine will be acting as the gateway for a local area
 	network and forwarding packets between other machines then select
 	&gui.yes; and press <keycap>Enter</keycap>.
 	If the machine is a node on a network then 
 	select &gui.no; and press
 	<keycap>Enter</keycap> to continue.</para>
     </sect2>
 
     <sect2 id="inetd-services">
       <title>Configure Internet Services</title>
 
       <screen>                      User Confirmation Requested
 Do you want to configure inetd and the network services that it provides?
 
                                Yes   [ No ]</screen>
 
       <para>If &gui.no; is selected, various services
 	such <application>telnetd</application> will not be enabled.  This
 	means that remote users will not be able to
 	<application>telnet</application> into this machine.  Local users
 	will be still be able to access remote machines with
 	<application>telnet</application>.</para>
 
       <para>These services can be enabled after installation by editing
 	<filename>/etc/inetd.conf</filename> with your favorite text editor.
 	See <xref linkend="network-inetd-overview"> for more information.</para>
 
       <para>Select &gui.yes; if you wish to
 	configure these services during install.  An additional
 	confirmation will display:</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>Select &gui.yes; to continue.</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>Selecting &gui.yes; will allow adding
 	services by deleting the <literal>#</literal> at the beginning
 	of a line.</para>
 
       <figure id="inetd-edit">
 	<title>Editing <filename>inetd.conf</filename></title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/edit-inetd-conf" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>After adding the desired services, pressing <keycap>Esc</keycap>
 	will display a menu which will allow exiting and saving 
 	the changes.</para>
 
     </sect2>
 
     <sect2 id="ftpanon">
       <title>Anonymous FTP</title>
 
       <indexterm>
 	<primary>FTP</primary>
 	<secondary>anonymous</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>Deny Anonymous FTP</title>
       
 	<para>Selecting the default &gui.no; and pressing
 	  <keycap>Enter</keycap> will still allow users who have accounts
 	  with passwords to use FTP to access the machine.</para>
       </sect3>
 
       <sect3 id="ftpallow">
 	<title>Allow Anonymous FTP</title>
 
 	<para>Anyone can access your machine if you elect to allow
 	  anonymous FTP connections.  The security implications should be
 	  considered before enabling this option.  For more information
 	  about security see <xref linkend="security">.</para>
 
 	<para>To allow anonymous FTP, use the arrow keys to select
 	  &gui.yes; and press <keycap>Enter</keycap>.
 	  The following screen (or similar) will display:</para>
 
 	<figure id="anon-ftp2">
 	  <title>Default Anonymous FTP Configuration</title>
 
 	  <mediaobject>
 	    <imageobject>
 	      <imagedata fileref="install/ftp-anon1" format="PNG">
 	    </imageobject>
 	  </mediaobject>
 	</figure>
 
 	<para>Pressing <keycap>F1</keycap> will display the help:</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>The ftp root directory will be put in <filename>/var</filename>
 	  by default.  If you do not have enough room there for the
 	  anticipated FTP needs, the <filename>/usr</filename> directory
 	  could be used by setting the FTP Root Directory to
 	  <filename>/usr/ftp</filename>.</para>
 
 	<para>When you are satisfied with the values, press 
 	  <keycap>Enter</keycap> to continue.</para>
 
 	<screen>                          User Confirmation Requested 
          Create a welcome message file for anonymous FTP users?
 
                               [ Yes ]    No</screen>
 
 	<para>If you select &gui.yes; and press
 	  <keycap>Enter</keycap>, an editor will automatically start
 	  allowing you to edit the message.</para>
 
 	<figure id="anon-ftp4">
 	  <title>Edit the FTP Welcome Message</title>
 
 	  <mediaobject>
 	    <imageobject>
 	      <imagedata fileref="install/ftp-anon2" format="PNG">
 	    </imageobject>
 	  </mediaobject>
 	</figure>
 
 	<para>This is a text editor called <command>ee</command>.  Use the
 	  instructions to change the message or change the message later
 	  using a text editor of your choice.  Note the file name/location
 	  at the bottom of the editor screen.</para>
 
 	<para>Press <keycap>Esc</keycap> and a pop-up menu will default
 	  to <guimenuitem>a) leave editor</guimenuitem>.  Press
 	  <keycap>Enter</keycap> to exit and continue.  Press
 	  <keycap>Enter</keycap> again to save changes if you made
 	  any.</para>
       </sect3>
     </sect2>
 
     <sect2 id="nfsconf">
       <title>Configure Network File System</title>
 
       <para>Network File System (NFS) allows sharing of files across a
 	network.  A machine can be configured as a server, a client, or
 	both.  Refer to <xref linkend="network-nfs"> for a more information.</para>
 
       <sect3 id="nsf-server-options">
 	<title>NFS Server</title>
 
 	<screen>                       User Confirmation Requested
  Do you want to configure this machine as an NFS server? 
 
                               Yes    [ No ]</screen>
 
 	<para>If there is no need for a Network File System server,
 	  select &gui.no; and press
 	  <keycap>Enter</keycap>.</para>
 
 	<para>If &gui.yes; is chosen, a message will
 	  pop-up indicating that the <filename>exports</filename> file must be
 	  created.</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>Press <keycap>Enter</keycap> to continue.  A text editor will
 	  start allowing the <filename>exports</filename> file to be created
 	  and edited.</para>
 
 	<figure id="nfs-server-edit">
 	  <title>Editing <filename>exports</filename></title>
 
 	  <mediaobject>
 	    <imageobject>
 	      <imagedata fileref="install/nfs-server-edit" format="PNG">
 	    </imageobject>
 	  </mediaobject>
 	</figure>
 
 	<para>Use the instructions to add the actual exported filesystems
 	  now or later using a text editor of your choice.  Note the
 	  file name/location at the bottom of the editor screen.</para>
 
 	<para>Press <keycap>Esc</keycap> and a pop-up menu will default to
 	  <guimenuitem>a) leave editor</guimenuitem>.  Press
 	  <keycap>Enter</keycap> to exit and continue.</para>
       </sect3>
 
       <sect3 id="nfs-client-options">
 	<title>NFS Client</title>
 
 	<para>The NFS client allows your machine to access NFS servers.</para>
 
 	<screen>                       User Confirmation Requested
  Do you want to configure this machine as an NFS client? 
 
                               Yes   [ No ]</screen>
 
 	<para>With the arrow keys, select &gui.yes;
 	  or &gui.no; as appropriate and
 	  press <keycap>Enter</keycap>.</para>
       </sect3>
     </sect2>
 
     <sect2 id="securityprofile">
       <title>Security Profile</title>
 
       <para>A <quote>security profile</quote> is a set of
 	configuration options that attempts to achieve the desired
 	ratio of security to convenience by enabling and disabling
 	certain programs and other settings.  The more severe the
 	security profile, the fewer programs will be enabled by
 	default.  This is one of the basic principles of security: do
 	not run anything except what you must.</para>
 
       <para>Please note that the security profile is just a default
 	setting.  All programs can be enabled and disabled after you
 	have installed FreeBSD by editing or adding the appropriate
 	line(s) to <filename>/etc/rc.conf</filename>.  For more
 	information, please see the &man.rc.conf.5; manual
 	page.</para>
 
       <para>The following table describes what each of the security
 	profiles does.  The columns are the choices you have for a
 	security profile, and the rows are the program or feature that
 	the profile enables or disables.</para>
 
       <table>
 	<title>Possible Security Profiles</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>YES</entry>
 	    </row>
 
 	    <row>
 	      <entry>&man.sshd.8;</entry>
 
 	      <entry>NO</entry>
 
 	      <entry>YES</entry>
 	    </row>
 
 	    <row>
 	      <entry>&man.portmap.8;</entry>
 
 	      <entry>NO</entry>
 
 	      <entry>MAYBE
 		<footnote>
 		  <para>The portmapper is enabled if the machine has
 		    been configured as an NFS client or server earlier
 		    in the installation.</para>
 		</footnote>
 	      </entry>
 	    </row>
 
 	    <row>
 	      <entry>NFS server</entry>
 
 	      <entry>NO</entry>
 
 	      <entry>YES</entry>
 	    </row>
 
 	    <row>
 	      <entry>&man.securelevel.8;</entry>
 
 	      <entry>YES
 		<footnote>
 		  <para>If you choose a security profile that sets the
 		    securelevel to <quote>Extreme</quote> or
 		    <quote>High</quote>, you must be aware of the
 		    implications.  Please read the &man.init.8;
 		    manual page and pay particular attention to the
 		    meanings of the security levels, or you may have
 		    significant trouble later!</para>
 		</footnote>
 	      </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>Selecting &gui.no; and pressing
 	<keycap>Enter</keycap> will set the security profile to medium.</para>
 
       <para>Selecting &gui.yes; and pressing
 	<keycap>Enter</keycap> will allow selecting a different security
 	profile.</para>
 
       <figure id="security-profile">
 	<title>Security Profile Options</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/security" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Press <keycap>F1</keycap> to display the help.  Press
 	<keycap>Enter</keycap> to return to selection menu.</para>
 
       <para>Use the arrow keys to choose <guimenuitem>Medium</guimenuitem>
 	unless your are sure that another level is required for your needs.
 	With &gui.ok; highlighted, press
 	<keycap>Enter</keycap>.</para>
 
       <para>An appropriate confirmation message will display depending on
 	which security setting was chosen.</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>Press <keycap>Enter</keycap> to continue with the
 	post-installation configuration.</para>
 
       <warning>
 	<para>The security profile is not a silver bullet!  Even if
 	  you use the extreme setting, you need to keep up with
 	  security issues by reading an appropriate mailing
 	  list (<xref linkend="eresources-mail">),
 	  using good passwords and passphrases, and
 	  generally adhering to good security practices.  It simply
 	  sets up the desired security to convenience ratio out of the
 	  box.</para>
       </warning>
 
     </sect2>
 
     <sect2 id="console">
       <title>System Console Settings</title>
 
       <para>There are several options available to customize the system
 	console.</para>
 
       <screen>                      User Confirmation Requested 
        Would you like to customize your system console settings?
 
                               [ Yes ]  No</screen>
 
       <para>To view and configure the options, select
 	&gui.yes; and press
 	<keycap>Enter</keycap>.</para>
 
       <figure id="saver-options">
 	<title>System Console Configuration Options</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/console-saver1" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>A commonly used option is the screen saver.  Use the arrow keys
 	to select <guimenuitem>Saver</guimenuitem> and then press
 	<keycap>Enter</keycap>.</para>
 
       <figure id="saver-select">
 	<title>Screen Saver Options</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/console-saver2" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Select the desired screen saver using the arrow keys
 	and then press <keycap>Enter</keycap>.  The System Console
 	Configuration menu will redisplay.</para>
 
       <para>The default time interval is 300 seconds.  To change the time
 	interval, select <guimenuitem>Saver</guimenuitem> again.  At the
 	Screen Saver Options menu, select <guimenuitem>Timeout</guimenuitem>
 	using the arrow keys and press <keycap>Enter</keycap>.  A pop-up
 	menu will appear:</para>
 
       <figure id="saver-timeout">
 	<title>Screen Saver Timeout</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/console-saver3" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>The value can be changed, then select &gui.ok;
 	and press <keycap>Enter</keycap> to return to the System Console
 	Configuration menu.</para>
 
       <figure id="saver-exit">
 	<title>System Console Configuration Exit</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/console-saver4" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Selecting <guimenuitem>Exit</guimenuitem> and pressing
 	<keycap>Enter</keycap> will continue with the post-installation
 	configurations.</para>
     </sect2>
 
     <sect2 id="timezone">
       <title>Setting the Time Zone</title>
 
       <para>Setting the time zone for your machine will allow it to
 	automatically correct for any regional time changes and perform
 	other time zone related functions properly.</para>
 
       <para>The example shown is for a machine located in the Eastern
 	time zone of the United States.  Your selections will vary according
 	to your geographical location.</para>
 
       <screen>                      User Confirmation Requested 
           Would you like to set this machine's time zone now?
 
                             [ Yes ]   No</screen>
 
       <para>Select &gui.yes; and press
 	<keycap>Enter</keycap> to set the time zone.</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>Select &gui.yes; 
 	or &gui.no; according to how the machine's
 	clock is configured and press <keycap>Enter</keycap>.</para>
 
       <figure id="set-timezone-region">
 	<title>Select Your Region</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/timezone1" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>The appropriate region is selected using the arrow keys
 	and then pressing <keycap>Enter</keycap>.</para>
 
       <figure id="set-timezone-country">
 	<title>Select Your Country</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/timezone2" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Select the appropriate country using the arrow keys
 	and press <keycap>Enter</keycap>.</para>
 
       <figure id="set-timezone-locality">
 	<title>Select Your Time Zone</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/timezone3" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>The appropriate time zone is selected using the arrow
 	keys and pressing <keycap>Enter</keycap>.</para>
 
       <screen>                            Confirmation 
             Does the abbreviation 'EDT' look reasonable?
 
                             [ Yes ]   No</screen>
 
       <para>Confirm the abbreviation for the time zone is correct.
 	If it looks okay, press <keycap>Enter</keycap> to continue with
 	the post-installation configuration.</para>
     </sect2>
 
     <sect2 id="linuxcomp">
       <title>Linux Compatibility</title>
 
       <screen>                      User Confirmation Requested 
           Would you like to enable Linux binary compatibility?
 
                             [ Yes ]   No</screen>
 
       <para>Selecting &gui.yes; and pressing
 	<keycap>Enter</keycap> will allow
 	running Linux software on FreeBSD.  The install will add
 	the appropriate packages for Linux compatibility.</para>
 
       <para>If installing by FTP, the machine will need to be connected to
 	the Internet.  Sometimes a remote ftp site will not have all the
 	distributions like the Linux binary compatibility.  This can
 	be installed later if necessary.</para>
     </sect2>
 
     <sect2 id="mouse">
       <title>Mouse Settings</title>
 
       <para>This option will allow you to cut and paste text in the
 	console and user programs with a 3-button mouse.  If using a 2-button
 	mouse, refer to manual page, &man.moused.8;, after installation for
 	details on emulating the 3-button style.  This example depicts a
 	non-USB mouse configuration (such as a PS/2 or COM port mouse):</para>
 
       <screen>                      User Confirmation Requested 
          Does this system have a non-USB mouse attached to it?
 
                             [ Yes ]    No </screen>
 
       <para>Select &gui.yes; for a non-USB mouse or
 	&gui.no; for a USB mouse and press
 	<keycap>Enter</keycap>.</para>
 
       <figure id="mouse-protocol">
 	<title>Select Mouse Protocol Type</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/mouse1" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Use the arrow keys to select <guimenuitem>Type</guimenuitem> and
 	press <keycap>Enter</keycap>.</para>
 
       <figure id="set-mouse-protocol">
 	<title>Set Mouse Protocol</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/mouse2" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>The mouse used in this example is a PS/2 type, so the default
 	<guimenuitem>Auto</guimenuitem> was appropriate.  To change protocol,
 	use the arrow keys to select another option.  Ensure that &gui.ok; is
 	highlighted and press <keycap>Enter</keycap> to exit this menu.</para>
 
       <figure id="config-mouse-port">
 	<title>Configure Mouse Port</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/mouse3" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Use the arrow keys to select <guimenuitem>Port</guimenuitem> and
 	press <keycap>Enter</keycap>.</para>
 
       <figure id="set-mouse-port">
 	<title>Setting the Mouse Port</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/mouse4" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>This system had a PS/2 mouse, so the default
 	<guimenuitem>PS/2</guimenuitem> was appropriate.  To change the port,
 	use the arrow keys and then press <keycap>Enter</keycap>.</para>
 
       <figure id="test-daemon">
 	<title>Enable the Mouse Daemon</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/mouse5" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Last, use the arrow keys to select
 	<guimenuitem>Enable</guimenuitem>, and press
 	<keycap>Enter</keycap> to enable and test the mouse
 	daemon.</para>
 
 
       <figure id="test-mouse-daemon">
 	<title>Test the Mouse Daemon</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/mouse6" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Move the mouse around the screen and verify the cursor
 	shown responds properly.  If it does, select
 	&gui.yes; and press <keycap>Enter</keycap>.  If
 	not, the mouse has not been configured correctly &mdash; select
 	&gui.no; and try using different configuration
 	options.</para>
 
       <para>Select <guimenuitem>Exit</guimenuitem> with the arrow keys
 	and press <keycap>Enter</keycap> to return to continue with the
 	post-installation configuration.</para>
     </sect2>
 
     <sect2 id="network-services">
       <sect2info>
         <authorgroup>
           <author>
             <firstname>Tom</firstname>
             <surname>Rhodes</surname>
             <contrib>Contributed by </contrib>
           </author>
         </authorgroup>
       </sect2info>
       <title>Configure Additional Network Services</title>
 
       <para>Configuring network services can be a daunting
 	task for new users if they lack previous
 	knowledge in this area.  Networking, including the Internet,
 	is critical to all modern operating systems including &os;;
 	as a result, it is very useful to have some understanding
 	&os;'s extensive networking capabilities.  Doing this
 	during the installation will ensure users have some
 	understanding of the various services available to them.</para>
 
       <para>Network services are programs that accept input from
 	anywhere on the network.  Every effort is made to make sure
 	these programs will not do anything <quote>harmful</quote>.
 	Unfortunately, programmers are not perfect and through time
 	there have been cases where bugs in network services have been
 	exploited by attackers to do bad things.  It is important that
 	you only enable the network services you know that you need.  If
 	in doubt it is best if you do not enable a network service until
 	you find out that you do need it.  You can always enable it
 	later by re-running <application>sysinstall</application> or by
 	using the features provided by the
 	<filename>/etc/rc.conf</filename> file.</para>
 
       <para>Selecting the <guimenu>Networking</guimenu> option will display
 	a menu similar to the one below:</para>
 
       <figure id="network-configuration">
 	<title>Network Configuration Upper-level</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/net-config-menu1" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>The first option, <guimenuitem>Interfaces</guimenuitem>, was previously covered during
 	the <xref linkend="inst-network-dev">, thus this option can
 	safely be ignored.</para>
 
       <para>Selecting the <guimenuitem>AMD</guimenuitem> option adds
 	support for the <acronym>BSD</acronym> automatic mount utility.
 	This is usually used in conjunction with the
 	<acronym>NFS</acronym> protocol (see below)
 	for automatically mounting remote file systems.
 	No special configuration is required here.</para>
 
       <para>Next in line is the <guimenuitem>AMD Flags</guimenuitem>
 	option.  When selected, a menu will pop up for you
 	to enter specific <acronym>AMD</acronym> flags.
 	The menu already contains a set of default options:</para>
 
       <screen>-a /.amd_mnt -l syslog /host /etc/amd.map /net /etc/amd.map</screen>
 
       <para>The <option>-a</option> option sets the default mount
 	location which is specified here as
 	<filename>/.amd_mnt</filename>.  The <option>-l</option>
 	option specifies the default <filename>log</filename> file;
 	however, when <literal>syslogd</literal> is used all log
 	activity will be sent to the system log daemon.  The
 	<filename class="directory">/host</filename> directory is used
 	to mount an exported file system from a remote
 	host, while <filename class="directory">/net</filename>
 	directory is used to mount an exported file system from an
 	<acronym>IP</acronym> address.  The
 	<filename>/etc/amd.map</filename> file defines the default
 	options for <acronym>AMD</acronym> exports.</para>
 
       <indexterm>
 	<primary>FTP</primary>
 	<secondary>anonymous</secondary>
       </indexterm>
 
       <para>The <guimenuitem>Anon FTP</guimenuitem> option permits anonymous
 	<acronym>FTP</acronym> connections.  Select this option to
 	make this machine an anonymous <acronym>FTP</acronym> server.
 	Be aware of the security risks involved with this option.
 	Another menu will be displayed to explain the security risks
 	and configuration in depth.</para>
 
       <para>The <guimenuitem>Gateway</guimenuitem> configuration menu will set
 	the machine up to be a gateway as explained previously.  This
 	can be used to unset the <guimenuitem>Gateway</guimenuitem> option if you accidentally
 	selected it during the installation process.</para>
 
       <para>The <guimenuitem>Inetd</guimenuitem> option can be used to configure
 	or completely disable the &man.inetd.8; daemon as discussed
 	above.</para>
 
       <para>The <guimenuitem>Mail</guimenuitem> option is used to configure the system's
 	default <acronym>MTA</acronym> or Mail Transfer Agent.
 	Selecting this option will bring up the following menu:</para>
 
       <figure id="mta-selection">
 	<title>Select a default MTA</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/mta-main" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Here you are offered a choice as to which
 	<acronym>MTA</acronym> to install
 	and set as the default.  An <acronym>MTA</acronym> is nothing
 	more than a mail server which delivers email to users on the
 	system or the Internet.</para>
 
       <para>Selecting <guimenuitem>Sendmail</guimenuitem> will install
 	the popular <application>sendmail</application> server which
 	is the &os; default.  The <guimenuitem>Sendmail local</guimenuitem> option
 	will set <application>sendmail</application> to be the default
 	<acronym>MTA</acronym>, but disable its ability to receive
 	incoming email from the Internet.  The other options here,
 	<guimenuitem>Postfix</guimenuitem> and
 	<guimenuitem>Exim</guimenuitem> act similar to
 	<guimenuitem>Sendmail</guimenuitem>.  They both deliver
 	email; however, some users prefer these alternatives to the
 	<application>sendmail</application>
 	<acronym>MTA</acronym>.</para>
 
       <para>After selecting an <acronym>MTA</acronym>, or choosing
 	not to select an MTA, the network configuration menu will appear
 	with the next option being <guimenuitem>NFS client</guimenuitem>.</para>
 
       <para>The <guimenuitem>NFS client</guimenuitem> option will
 	configure the system to communicate with a server via
 	<acronym>NFS</acronym>.  An <acronym>NFS</acronym> server
 	makes file systems available to other machines on the
 	network via the <acronym>NFS</acronym> protocol.  If this is
 	a stand alone machine, this option can remain unselected.
 	The system may require more configuration later; see
 	<xref linkend="network-nfs"> for more
 	information about client and server configuration.</para>
 
       <para>Below that option is the <guimenuitem>NFS server</guimenuitem>
 	option, permitting you to set the system up as an
 	<acronym>NFS</acronym> server.  This adds the required
 	information to start up the <acronym>RPC</acronym> remote
 	procedure call services.  <acronym>RPC</acronym> is used to
 	coordinate connections between hosts and programs.</para>
 
       <para>Next in line is the <guimenuitem>Ntpdate</guimenuitem> option,
 	which deals with time synchronization.  When selected, a menu
 	like the one below shows up:</para>
 
       <figure id="Ntpdate-config">
 	<title>Ntpdate Configuration</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/ntp-config" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>From this menu, select the server which is the closest
 	to your location.  Selecting a close one will make the time
 	synchronization more accurate as a server further from your
 	location may have more connection latency.</para>
 
       <para>The next option is the <acronym>PCNFSD</acronym> selection.
 	This option will install the
 	<filename role="package">net/pcnfsd</filename> package from
 	the Ports Collection.  This is a useful utility which provides
 	<acronym>NFS</acronym> authentication services for systems which
 	are unable to provide their own, such as Microsoft's
 	&ms-dos; operating system.</para>
 
       <para>Now you must scroll down a bit to see the other
 	options:</para>
 
       <figure id="Network-configuration-cont">
 	<title>Network Configuration Lower-level</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/net-config-menu2" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>The &man.rpcbind.8;, &man.rpc.statd.8;, and
 	&man.rpc.lockd.8; utilities are all used for Remote Procedure
 	Calls (<acronym>RPC</acronym>).
 	The <command>rpcbind</command> utility manages communication
 	between <acronym>NFS</acronym> servers and clients, and is
 	required for <acronym>NFS</acronym> servers to operate
 	correctly.  The <application>rpc.statd</application> daemon interacts
 	with the <application>rpc.statd</application> daemon on other hosts to
 	provide status monitoring.  The reported status is usually held
 	in the <filename>/var/db/statd.status</filename> file.  The
 	next option listed here is the <guimenuitem>rpc.lockd</guimenuitem>
 	option, which, when selected, will provide file locking
 	services.  This is usually used with
 	<application>rpc.statd</application> to monitor what hosts are
 	requesting locks and how frequently they request them.
 	While these last two options are marvelous for debugging, they
 	are not required for <acronym>NFS</acronym> servers and clients
 	to operate correctly.</para>
 
       <para>As you progress down the list the next item here is
 	<guimenuitem>Routed</guimenuitem>, which is the routing daemon.  The
 	&man.routed.8; utility manages network routing tables,
 	discovers multicast routers, and supplies a copy of the routing
 	tables to any physically connected host on the network upon
 	request.  This is mainly used for machines which act as a
 	gateway for the local network.  When selected, a menu will be
 	presented requesting the default location of the utility.
 	The default location is already defined for you and can be
 	selected with the <keycap>Enter</keycap> key.  You will then
 	be presented with yet another menu, this time asking for the
 	flags you wish to pass on to <application>routed</application>.  The
 	default is <option>-q</option> and it should already appear
 	on the screen.</para>
 
       <para>Next in line is the <guimenuitem>Rwhod</guimenuitem> option which,
 	when selected, will start the &man.rwhod.8; daemon
 	during system initialization.  The <command>rwhod</command>
 	utility broadcasts system messages across the network
 	periodically, or collects them when in <quote>consumer</quote>
 	mode.  More information can be found in the &man.ruptime.1; and
 	&man.rwho.1; manual pages.</para>
 
       <para>The next to the last option in the list is for the
 	&man.sshd.8; daemon.  This is the secure shell server for
 	<application>OpenSSH</application> and it is highly recommended
 	over the standard <application>telnet</application> and
 	<acronym>FTP</acronym> servers.  The <application>sshd</application>
 	server is used to create a secure connection from one host to
 	another by using encrypted connections.</para>
 
       <para>Finally there is the <guimenuitem>TCP Extensions</guimenuitem>
 	option.  This enables the <acronym>TCP</acronym> Extensions
 	defined in <acronym>RFC</acronym>&nbsp;1323 and
 	<acronym>RFC</acronym>&nbsp;1644.  While on many hosts this can
 	speed up connections, it can also cause some connections to be
 	dropped.  It is not recommended for servers, but may be
 	beneficial for stand alone machines.</para>
 
       <para>Now that you have configured the network services, you can
 	scroll up to the very top item which is <guimenuitem>Exit</guimenuitem>
 	and continue on to the next configuration section.</para>
 
     </sect2>
 
     <sect2 id="x-server">
       <title>Configure X Server</title>
 
       <note>
 	<para>As of &os;&nbsp;5.3-RELEASE, the X server configuration
 	  facility has been removed from
 	  <application>sysinstall</application>, you have to install
 	  and configure the X server after the installation of &os;.
 	  More information regarding the installation and the
 	  configuration of a X server can be found in <xref
 	  linkend="x11">.  You can skip this section if you are not
 	  installing a &os; version prior to 5.3-RELEASE.</para>
       </note>
 
       <para>In order to use a graphical user interface such as 
 	<application>KDE</application>, <application>GNOME</application>,
 	or others, the X server will need to be configured.</para>
 
       <note>
 	<para>In order to run <application>&xfree86;</application> as a
 	  non <username>root</username> user you will need to
 	  have <filename role="package">x11/wrapper</filename> installed.
 	  This is installed by default beginning with FreeBSD 4.7.  For
 	  earlier versions this can be added
 	  from the Package Selection menu.</para>
       </note>
 
       <para>To see whether your video card is supported, check the
 	<ulink url="http://www.xfree86.org/">&xfree86;</ulink> web site.</para>
 
       <screen>                      User Confirmation Requested 
         Would you like to configure your X server at this time?
 
                             [ Yes ]   No</screen>
 
       <warning>
 	<para>It is necessary to know your monitor specifications and
 	  video card information.  Equipment damage can occur if settings
 	  are incorrect.  If you do not have this information, select
 	  &gui.no; and perform the configuration
 	  after installation when you have the information using 
 	  <command>sysinstall</command> (<command>/stand/sysinstall</command>
 	  in &os; versions older than 5.2), selecting
 	  <guimenuitem>Configure</guimenuitem> and then 
 	  <guimenuitem>XFree86</guimenuitem>.  Improper configuration
 	  of the X server at this time can leave the machine in a
 	  frozen state.  It is often advised to configure the X server
 	  once the installation has completed.
 	</para>
       </warning>
 
       <para>If you have graphics card and monitor information, select
 	&gui.yes; and press <keycap>Enter</keycap>
 	to proceed with configuring the X server.</para>
 
       <figure id="xserver2">
 	<title>Select Configuration Method Menu</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/xf86setup" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>There are several ways to configure the X server.
 	Use the arrow keys to select one of the methods  and press
 	<keycap>Enter</keycap>.  Be sure to read all instructions
 	carefully.</para>
 
       <para>The <application>xf86cfg</application> and 
 	<application>xf86cfg -textmode</application> methods may make the screen
 	go dark and take a few seconds to start.  Be patient.</para>
 
 
       <para>The following will illustrate the use of the
 	<application>xf86config</application> configuration tool.  The
 	configuration choices you make will depend on the hardware in the
 	system so your choices will probably be different than those
 	shown:</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>This indicates that the mouse daemon previously configured has been
 	detected.
 	Press <keycap>Enter</keycap> to continue.</para>
 
       <para>Starting <application>xf86config</application> will display
 	a brief introduction:</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>Pressing <keycap>Enter</keycap> will start the mouse
 	configuration.  Be sure to follow the instructions and use
 	<quote>Mouse Systems</quote> as the mouse protocol and
 	<filename>/dev/sysmouse</filename> as the mouse port even if
 	using a PS/2 mouse is shown as an illustration.</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) & 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>The keyboard is the next item to be configured. A generic
 	101-key model is shown for illustration.  Any name may be used
 	for the variant or simply press <keycap>Enter</keycap> to accept
 	the default value.</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>Next, we proceed to the configuration for the monitor.  Do not
 	exceed the ratings of your monitor. Damage could occur.  If you
 	have any doubts, do the configuration after you have the
 	information.</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>The selection of a video card driver from a list is
 	next.  If you pass your card on the list, continue to press
 	<keycap>Enter</keycap> and the list will repeat.  Only an
 	excerpt from the list is shown:</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>Next, the video modes are set for the resolutions
 	desired.  Typically, useful ranges are 640x480, 800x600, and 1024x768
 	but those are a function of video card capability, monitor size,
 	and eye comfort.  When selecting a color depth, select the highest
 	mode that your card will support.</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>Finally, the configuration needs to be saved.  Be sure
 	to enter <filename>/etc/X11/XF86Config</filename> as the location
 	for saving the configuration.</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>If the configuration fails, you can try the configuration again
 	by selecting &gui.yes; when the following
 	message appears:</para>
 
       <screen>          User Confirmation Requested
 The XFree86 configuration process seems to have
 failed.  Would you like to try again?
 
              [ Yes ]         No</screen>
 
       <para>If you have trouble configuring <application>&xfree86;</application>, select
 	&gui.no; and press <keycap>Enter</keycap>
 	and continue with the installation process.  After installation
 	you can use <command>xf86cfg -textmode</command> or
 	<command>xf86config</command> to access the command line
 	configuration utilities as <username>root</username>.  There is
 	an additional method for configuring <application>&xfree86;</application> described in
 	<xref linkend="x11">.   If you choose not to configure
 	<application>&xfree86;</application> at this time the next menu will be for package
 	selection.</para>
 
       <para>The default setting which allows the server to be killed
 	is the hotkey sequence <keycombo action='simul'>
 	<keycap>Ctrl</keycap><keycap>Alt</keycap>
 	<keycap>Backspace</keycap></keycombo>.  This
 	can be executed if something is wrong with the server settings and
 	prevent hardware damage.</para>
 
       <para>The default setting that allows video mode switching will
 	permit changing of the mode while running X with the hotkey
 	sequence
 	<keycombo action='simul'>
 	  <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>+</keycap>
 	</keycombo> or
 	<keycombo action='simul'>
 	  <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>-</keycap>
 	</keycombo>.   
       </para>
 
       <para>After you have <application>&xfree86;</application>
 	running, the display can be adjusted for height, width,
 	or centering by using <application>xvidtune</application>.</para>
 
       <para>There are warnings that improper settings can
 	damage your equipment.  Heed them.  If in doubt, do not do
 	it.  Instead, use the monitor controls to adjust the display for
 	X Window.  There may be some display differences when switching
 	back to text mode, but it is better than damaging equipment.</para>
 
       <para>Read the &man.xvidtune.1; manual page before making
 	any adjustments.</para>
 
       <para>Following a successful <application>&xfree86;</application> configuration, it will proceed
 	to the selection of a default desktop.</para>
     </sect2>
 
     <sect2 id="default-desktop">
       <title>Select Default X Desktop</title>
 
       <note>
 	<para>As of &os;&nbsp;5.3-RELEASE, the X desktop selection
 	  facility has been removed from
 	  <application>sysinstall</application>, you have to configure
 	  the X desktop after the installation of &os;.  More
 	  information regarding the installation and the configuration
 	  of a X desktop can be found in <xref linkend="x11">.  You
 	  can skip this section if you are not installing a &os;
 	  version prior to 5.3-RELEASE.</para>
       </note>
 
       <para>There are a variety of window managers available.  They range
 	from very basic environments to full desktop environments with a
 	large suite of software.  Some require only minimal disk space and
 	low memory while others with more features require much more.  The
 	best way to determine which is most suitable for you is to try a few
 	different ones.  Those are available from the Ports Collection or as
 	packages and can be added after installation.</para>
 
       <para>You can select one of the popular desktops to be installed
 	and configured as the default desktop.  This will allow you
 	to start it right after installation.</para>
 
       <figure id="x-desktop">
 	<title>Select Default Desktop</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/desktop" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Use the arrow keys to select a desktop and press
 	<keycap>Enter</keycap>.  Installation of the selected desktop will
 	proceed.</para>
     </sect2>
 
     <sect2 id="packages">
     <title>Install Packages</title>
 
       <para>Packages are pre-compiled binaries and are a convenient
 	way to install software.</para>
 
       <para>Installation of one package is shown for purposes of
 	illustration.  Additional packages can also be added at this
 	time if desired.  After installation
 	<command>sysinstall</command> (<command>/stand/sysinstall</command>
 	in &os; versions older than 5.2) can be used to add additional
 	packages.</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>Selecting &gui.yes; and pressing
 	<keycap>Enter</keycap> will be
 	followed by the Package Selection screens:</para>
 
       <figure id="package-category">
 	<title>Select Package Category</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/pkg-cat" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Only packages on the current installation media are
 	available for installation at any given time.</para>
 
       <para>All packages available will be displayed if 
 	<guimenuitem>All</guimenuitem> is selected or you can select a
 	particular category.  Highlight your selection with the arrow
 	keys and press <keycap>Enter</keycap>.</para>
 
       <para>A menu will display showing all the packages available for
 	the selection made:</para>
 
       <figure id="package-select">
 	<title>Select Packages</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/pkg-sel" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>The <application>bash</application> shell is shown selected.
 	Select as many as desired by highlighting the package and pressing the
 	<keycap>Space</keycap> key.  A short description of each package will
 	appear in the lower left corner of the screen.</para>
 
       <para>Pressing the <keycap>Tab</keycap> key will toggle between the last
 	selected package, &gui.ok;, and &gui.cancel;.</para>
 
       <para>When you have finished marking the packages for installation,
 	press <keycap>Tab</keycap> once to toggle to the &gui.ok; and press
 	<keycap>Enter</keycap> to return to the Package Selection menu.</para>
 
       <para>The left and right arrow keys will also toggle between &gui.ok;
 	and &gui.cancel;.  This method can also be used to select &gui.ok; and
 	press <keycap>Enter</keycap> to return to the Package Selection
 	menu.</para>
 
       <figure id="package-install">
 	<title>Install Packages</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/pkg-install" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Use the <keycap>Tab</keycap> and arrow keys to select <guibutton>[&nbsp;Install&nbsp;]</guibutton>
 	and press <keycap>Enter</keycap>.  You will then need to confirm
 	that you want to install the packages:</para>
 
       <figure id="package-install-confirm">
 	<title>Confirm Package Installation</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/pkg-confirm" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Selecting &gui.ok; and pressing <keycap>Enter</keycap> will start
 	the package installation.  Installing messages will appear until
 	completed.  Make note if there are any error messages.</para>
 
       <para>The final configuration continues after packages are
 	installed.  If you end up not selecting any packages, and wish
 	to return to the final configuration, select
 	<guibutton>Install</guibutton> anyways.</para>
     </sect2>
 
     <sect2 id="addusers">
       <title>Add Users/Groups</title>
 
       <para>You should add at least one user during the installation so
 	that you can use the system without being logged in as
 	<username>root</username>.  The root partition is generally small
 	and running applications as <username>root</username> can quickly
 	fill it.  A bigger danger is noted below:</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>Select &gui.yes; and press
 	<keycap>Enter</keycap> to continue with adding a user.</para>
 
       <figure id="add-user2">
 	<title>Select User</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/adduser1" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Select <guimenuitem>User</guimenuitem> with the arrow keys
 	and press <keycap>Enter</keycap>.</para>
 
       <figure id="add-user3">
 	<title>Add User Information</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/adduser2" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>The following descriptions will appear in the lower part of
 	the screen as the items are selected with <keycap>Tab</keycap>
 	to assist with entering the required information:</para>
 
       <variablelist>
 	<varlistentry>
 	  <term>Login ID</term>
 
 	  <listitem>
 	    <para>The login name of the new user (mandatory).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>UID</term>
 	
 	  <listitem>
 	    <para>The numerical ID for this user (leave blank for
 	      automatic choice).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Group</term>
 
 	  <listitem>
 	    <para>The login group name for this user (leave blank for
 	      automatic choice).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Password</term>
 
 	  <listitem>
 	    <para>The password for this user (enter this field with
 	      care!).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Full name</term>
 
 	  <listitem>
 	    <para>The user's full name (comment).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Member groups</term>
 
 	  <listitem>
 	    <para>The groups this user belongs to (i.e. gets access
 	      rights for).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Home directory</term>
 
 	  <listitem>
 	    <para>The user's home directory (leave blank for
 	      default).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>Login shell</term>
 	  <listitem>
 	    <para>The user's login shell (leave blank for
 	      default, e.g. <filename>/bin/sh</filename>).</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
 
       <para>The login shell was changed from <filename>/bin/sh</filename> to
 	<filename>/usr/local/bin/bash</filename> to use the
 	<application>bash</application> shell that was previously installed as
 	a package.  Do not try to use a shell that does not exist or you will
 	not be able to login.  The most common shell used in the
 	BSD-world is the C shell, which can be indicated as
 	<filename>/bin/tcsh</filename>.</para>
 
       <para>The user was also added to the <groupname>wheel</groupname> group
 	to be able to become a superuser with <username>root</username>
 	privileges.</para>
 
       <para>When you are satisfied, press &gui.ok; and
 	the User and Group Management menu will redisplay:</para>
 
       <figure id="add-user4">
 	<title>Exit User and Group Management</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/adduser3" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Groups can also be added at this time if specific needs
 	are known.  Otherwise, this may be accessed through using
 	<command>sysinstall</command> (<command>/stand/sysinstall</command>
 	in &os; versions older than 5.2) after installation is
 	completed.</para>
 
       <para>When you are finished adding users, select 
 	<guimenuitem>Exit</guimenuitem> with the arrow keys and press
 	<keycap>Enter</keycap> to continue the installation.</para>
     </sect2>
 
     <sect2 id="rootpass">
       <title>Set the <username>root</username> Password</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>Press <keycap>Enter</keycap> to set the <username>root</username>
 	password.</para>
 
       <para>The password will need to be typed in twice correctly.  Needless to
 	say, make sure you have a way of finding the password if you
 	forget.  Notice that the password you type in is not echoed, nor
 	are asterisks displayed.</para>
 
       <screen>Changing local password for root. 
 New password : 
 Retype new password :</screen>
 
       <para>The installation will continue after the password is
 	successfully entered.</para>
     </sect2>
 
     <sect2 id="exit-inst">
       <title>Exiting Install</title>
 
       <para>If you need to configure additional network devices or
 	any other configuration, you can do it at this point or
 	after installation with <command>sysinstall</command>
 	(<command>/stand/sysinstall</command> in &os; versions older
 	than 5.2).</para>
 
       <screen>                     User Confirmation Requested
  Visit the general configuration menu for a chance to set any last
  options? 
 
                               Yes   [ No ]</screen>
 
       <para>Select &gui.no; with the arrow keys
 	and press <keycap>Enter</keycap> to return to the Main
 	Installation Menu.</para>
 
       <figure id="final-main">
 	<title>Exit Install</title>
 
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="install/mainexit" format="PNG">
 	  </imageobject>
 	</mediaobject>
       </figure>
 
       <para>Select <guibutton>[X Exit Install]</guibutton> with the arrow
 	keys and press <keycap>Enter</keycap>.  You will be asked to
 	confirm exiting the installation:</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>Select &gui.yes; and remove the floppy if
 	booting from the floppy.  The CDROM drive is locked until the machine
 	starts to reboot.  The CDROM drive is then unlocked and the disk can
 	be removed from drive (quickly).</para>
 
       <para>The system will reboot so watch for any error messages that
 	may appear.</para>
     </sect2>
 
     <sect2 id="freebsdboot">
       <title>FreeBSD Bootup</title>
 
       <sect3 id="freebsdboot-i386">
         <title>FreeBSD Bootup on the &i386;</title>
 
       <para>If everything went well, you will see messages scroll
 	off the screen and you will arrive at a login prompt.  You can view
 	the content of the messages by pressing <keycap>Scroll-Lock</keycap>
 	and using <keycap>PgUp</keycap> and <keycap>PgDn</keycap>.
 	Pressing <keycap>Scroll-Lock</keycap> again will return
 	to the prompt.</para>
 
       <para>The entire message may not display (buffer limitation) but
 	it can be viewed from the command line after logging in by typing
 	<command>dmesg</command> at the prompt.</para>
 
       <para>Login using the username/password you set during installation
 	(<username>rpratt</username>, in this example).  Avoid logging in as
 	<username>root</username> except when necessary.</para>
 
       <para>Typical boot messages (version information omitted):</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>Generating the RSA and DSA keys may take some time on slower
 	machines.  This happens only on the initial boot-up of a new
 	installation.  Subsequent boots will be faster.</para>
 
       <para>If the X server has been configured and a Default Desktop
 	chosen, it can be started by typing <command>startx</command> at
 	the command line.</para>
 
       </sect3>
 
       <sect3>
         <title>Bootup of FreeBSD on the Alpha</title>
 
 	<indexterm><primary>Alpha</primary></indexterm>
 
         <para>Once the install procedure has finished, you will be
           able to start FreeBSD by typing something like this to the
           SRM prompt:</para>
 
 	<screen>&gt;&gt;&gt;<userinput>BOOT DKC0</userinput></screen>
 
 	<para>This instructs the firmware to boot the specified
 	  disk.  To make FreeBSD boot automatically in the future, use
 	  these commands:</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>The boot messages will be similar (but not identical) to
 	those produced by FreeBSD booting on the &i386;.</para>
       </sect3>
     </sect2>
 
     <sect2 id="shutdown">
       <title>FreeBSD Shutdown</title>
 
       <para>It is important to properly shutdown the operating
 	system.  Do not just turn off power.  First, become a superuser by
 	typing <command>su</command> at the command line and entering the
 	<username>root</username> password.  This will work only if the user
 	is a member of the <groupname>wheel</groupname> group.
 	Otherwise, login as <username>root</username> and use
 	<command>shutdown -h now</command>.</para>
 
       <screen>The operating system has halted. 
 Please press any key to reboot.</screen>
 
       <para>It is safe to turn off the power after the shutdown command
 	has been issued and the message <quote>Please press any key to reboot</quote>
 	appears.  If any key is pressed instead of turning off the power
 	switch, the system will reboot.</para>
 
       <para>You could also use the
         <keycombo action="simul">
 	  <keycap>Ctrl</keycap>
 	  <keycap>Alt</keycap>
 	  <keycap>Del</keycap>
 	</keycombo>
 	key combination to reboot the system, however this is not recommended
 	during normal operation.</para>
 
     </sect2>
   </sect1>
 
   <sect1 id="install-supported-hardware">
-    <title>Supported Hardware</title>
+    <title>¤ä´©ªºµwÅé</title>
 
     <indexterm><primary>hardware</primary></indexterm>
     <para>FreeBSD currently runs on a wide variety of ISA, VLB, EISA, and PCI
       bus-based PCs with Intel, AMD, Cyrix, or NexGen <quote>x86</quote>
       processors, as well as a number of machines based on the Compaq Alpha
       processor.  Support for generic IDE or ESDI drive configurations,
       various SCSI controllers, PCMCIA cards, USB devices, and network and
       serial cards is also provided.  FreeBSD also supports IBM's microchannel
       (MCA) bus.</para>
 
     <para>A list of supported hardware is provided with each FreeBSD release
       in the FreeBSD Hardware Notes.  This document can usually be found in a
       file named <filename>HARDWARE.TXT</filename>, in the top-level directory
       of a CDROM or FTP distribution or in
       <application>sysinstall</application>'s documentation menu.  It lists,
       for a given architecture, what hardware devices are known to be
       supported by each release of FreeBSD.  Copies of the supported
       hardware list for various releases and architectures can also be
       found on the <ulink
       url="http://www.FreeBSD.org/releases/index.html">Release
       Information</ulink> page of the FreeBSD Web site.</para>
   </sect1>
 
   <sect1 id="install-trouble">
-    <title>Troubleshooting</title>
+    <title>¦w¸ËªººÃÃøÂø¯g¸Ñ¨M</title>
 
     <indexterm>
       <primary>installation</primary>
       <secondary>troubleshooting</secondary>
     </indexterm>
     <para>The following section covers basic installation troubleshooting,
       such as common problems people have reported.  There are also a few
       questions and answers for people wishing to dual-boot FreeBSD with
       &ms-dos;.</para>
 
     <sect2>
       <title>What to Do If Something Goes Wrong</title>
 
       <para>Due to various limitations of the PC architecture, it is
         impossible for probing to be 100% reliable, however, there are a
         few things you can do if it fails.</para>
 
       <para>Check the Hardware Notes document for your version of
         FreeBSD to make sure your hardware is
         supported.</para>
 
       <para>If your hardware is supported and you still experience
         lock-ups or other problems, reset your computer, and when the
         visual kernel configuration option is given, choose it.  This will
         allow you to go through your hardware and supply information to the
         system about it.  The kernel on the boot disks is configured
         assuming that most hardware devices are in their factory default
         configuration in terms of IRQs, IO addresses, and DMA channels.  If
         your hardware has been reconfigured, you will most likely need to
         use the configuration editor to tell FreeBSD where to find
         things.</para>
 
       <para>It is also possible that a probe for a device not present will
         cause a later probe for another device that is present to fail.  In
         that case, the probes for the conflicting driver(s) should be
         disabled.</para>
 
       <note>
         <para>Some installation problems can be avoided or alleviated
           by updating the firmware on various hardware components, most notably
           the motherboard.  The motherboard firmware may also be referred to
           as <acronym>BIOS</acronym> and most of the motherboard or computer
           manufactures have a website where the upgrades and upgrade information
           may be located.</para>
 
         <para>Most manufacturers strongly advise against upgrading the motherboard
           <acronym>BIOS</acronym> unless there is a good reason for doing so, which
           could possibly be a critical update of sorts.  The upgrade process
           <emphasis>can</emphasis> go wrong, causing permanent damage to the
           <acronym>BIOS</acronym> chip.</para>
         </note>
 
       <warning>
         <para>Do not disable any drivers you will need during the
           installation, such as your screen (<devicename>sc0</devicename>).
 	  If the installation wedges or fails mysteriously after leaving
 	  the configuration editor, you have probably removed or changed
 	  something you should not have.  Reboot and try again.</para>
       </warning>
 
       <para>In configuration mode, you can:</para>
 
       <itemizedlist>
         <listitem>
           <para>List the device drivers installed in the kernel.</para>
         </listitem>
 
         <listitem>
           <para>Disable device drivers for hardware that is not present in
 	    your system.</para>
         </listitem>
 
         <listitem>
           <para>Change IRQs, DRQs, and IO port addresses used by a device
 	    driver.</para>
         </listitem>
       </itemizedlist>
 
       <para>After adjusting the kernel to match your hardware
         configuration, type <command>Q</command> to boot with the new
         settings.  Once the installation has completed, any changes you
         made in the configuration mode will be permanent so you do not have
         to reconfigure every time you boot.  It is still highly likely that
         you will eventually want to build a <link
         linkend="kernelconfig">custom kernel</link>.</para>
     </sect2>
     
     <sect2>
       <title>Dealing with Existing &ms-dos; Partitions</title>
 
       <indexterm><primary>DOS</primary></indexterm>
       <para>Many users wish to install &os; on <acronym>PC</acronym>s inhabited by
 	&microsoft; based operating systems.  For those instances, &os; has a
 	utility known as <application>FIPS</application>.  This utility can be found
 	in the <filename>tools</filename> directory on the install CD-ROM, or downloaded
 	from one of various <link linkend="mirrors">&os; mirrors</link>.</para>
 
       <para>The <application>FIPS</application> utility allows you to split an
 	existing &ms-dos; partition into two pieces, preserving the original
 	partition and allowing you to install onto the second free piece.
 	You first need to defragment your &ms-dos; partition using the &windows;
 	<application>Disk Defragmenter</application> utility (go into Explorer, right-click on
 	the hard drive, and choose to defrag your hard drive), or use
 	<application>Norton Disk Tools</application>.  Now you can run the
 	<application>FIPS</application> utility.  It will prompt you for the rest of
 	the information, just follow the on screen instructions.  Afterwards, you can
 	reboot and install &os; on the new free slice.  See the <guimenuitem>Distributions</guimenuitem> menu
 	for an estimate of how much free space you will need for the kind of
 	installation you want.</para>
 
       <para>There is also a very useful product from PowerQuest
 	(<ulink url="http://www.powerquest.com/">http://www.powerquest.com</ulink>) called
 	<application>&partitionmagic;</application>.  This application has far more
 	functionality than <application>FIPS</application>, and is highly recommended
 	if you plan to add/remove operating systems often.  It does cost money, so if you
 	plan to install &os; and keep it installed, <application>FIPS</application>
 	will probably be fine for you.</para>
     </sect2>
 
     <sect2>
       <title>Using &ms-dos; and &windows; File Systems</title>
 
       <para>At this time, &os; does not support file systems compressed with the
 	<application>Double Space&trade;</application> application.  Therefore the file
 	system will need to be uncompressed before &os; can access the data.  This
 	can be done by running the <application>Compression Agent</application>
 	located in the <guimenuitem>Start</guimenuitem>&gt; <guimenuitem>Programs</guimenuitem> &gt;
 	<guimenuitem>System Tools</guimenuitem> menu.</para>
 
       <para>&os; can support &ms-dos; based file systems.  This requires you use
 	the &man.mount.msdos.8; command (in &os; 5.X, the command is &man.mount.msdosfs.8;)
 	with the required parameters.  The utilities most common usage is:</para>
 
       <screen>&prompt.root; <userinput>mount_msdos /dev/ad0s1 /mnt</userinput></screen>
 
       <para>In this example, the &ms-dos; file system is located on the first partition of
 	the primary hard disk.  Your situation may be different, check the output from
 	the <command>dmesg</command>, and <command>mount</command> commands.  They should
 	produce enough information to give an idea of the partition layout.</para>
 
       <note><para>Extended &ms-dos; file systems are usually mapped after the &os;
 	partitions.  In other words, the slice number may be higher than the ones
 	&os; is using.  For instance, the first &ms-dos; partition may be
 	<filename>/dev/ad0s1</filename>, the &os; partition may be
 	<filename>/dev/ad0s2</filename>, with the extended &ms-dos; partition being
 	located on <filename>/dev/ad0s3</filename>.  To some, this can be confusing
 	at first.</para></note>
 
       <para>NTFS partitions can also be mounted in a similar manner
 	using the &man.mount.ntfs.8; command.</para>
     </sect2>
 
     <sect2>
       <title>Alpha User's Questions and Answers</title>
 
       <indexterm><primary>Alpha</primary></indexterm>
 
       <para>This section answers some commonly asked questions about
         installing FreeBSD on Alpha systems.</para>
 
       <qandaset>
 	<qandaentry>
 	  <question>
 	    <para>Can I boot from the ARC or Alpha BIOS Console?</para>
 	  </question>
 
 	  <indexterm><primary>ARC</primary></indexterm>
 	  <indexterm><primary>Alpha BIOS</primary></indexterm>
 	  <indexterm><primary>SRM</primary></indexterm>
 
 	  <answer>
 	    <para>No.  &os;, like Compaq Tru64 and VMS, will only boot
 	    from the SRM console.</para>
 	  </answer>
 	</qandaentry>
 
 	<qandaentry>
 	  <question>
 	    <para>Help, I have no space!  Do I need to delete
 	    everything first?</para>
 	  </question>
 
 	  <answer>
 	    <para>Unfortunately, yes.</para>
 	  </answer>
 	</qandaentry>
 
 	<qandaentry>
 	  <question>
 	    <para>Can I mount my Compaq Tru64 or VMS filesystems?</para>
 	  </question>
 
 	  <answer>
 	    <para>No, not at this time.</para>
 	  </answer>
 	</qandaentry>
       </qandaset>
     </sect2>
   </sect1>
 
   <sect1 id="install-advanced">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Valentino</firstname>
 	  <surname>Vaschetto</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
 	<!-- May 2001 -->
       </authorgroup>
     </sect1info>
 
-    <title>Advanced Installation Guide</title>
+    <title>¶i¶¥¦w¸Ë«ü«n</title>
 
     <para>This section describes how to install FreeBSD in exceptional
        cases.</para>
 
     <sect2 id="headless-install">
       <title>Installing FreeBSD on a System without a Monitor or
         Keyboard</title>
 
       <indexterm>
         <primary>installation</primary>
         <secondary>headless (serial console)</secondary>
       </indexterm>
       <indexterm><primary>serial console</primary></indexterm>
       <para>This type of installation is called a <quote>headless
 	install</quote>, because the machine that you are trying to install
 	FreeBSD on either does not have a monitor attached to it, or does not
 	even have a VGA output.  How is this possible you ask? Using a
         serial console.  A serial console is basically using another
         machine to act as the main display and keyboard for a
         system.  To do this, just follow the steps to create
         installation floppies, explained in <xref
         linkend="install-floppies">.</para>
 
       <para>To modify these floppies to boot into a serial console, follow
 	these steps:</para>
 
       <procedure>
 	<step>
 	  <title>Enabling the Boot Floppies to Boot into a Serial Console</title>
   	    <indexterm>
 	      <primary><command>mount</command></primary>
 	    </indexterm>
 	    <para>If you were to boot into the floppies that you just
 	      made, FreeBSD would boot into its normal install mode.  We
 	      want FreeBSD to boot into a serial console for our
 	      install.  To do this, you have to mount the
 	      <filename>kern.flp</filename> floppy onto your FreeBSD
 	      system using the &man.mount.8; command.</para>
 
             <screen>&prompt.root; <userinput>mount /dev/fd0 /mnt</userinput></screen>
 
 	    <para>Now that you have the floppy mounted, you must
 	      change into the <filename class="directory">/mnt</filename> directory:</para>
 
 	    <screen>&prompt.root; <userinput>cd /mnt</userinput></screen>
 
 	    <para>Here is where you must set the floppy to boot into a
 	      serial console.  You have to make a file called
 	      <filename>boot.config</filename> containing 
 	      <literal>/boot/loader -h</literal>.  All this does is pass a flag to the bootloader to
 	      boot into a serial console.</para>
 
 	    <screen>&prompt.root; <userinput>echo "/boot/loader -h" > boot.config</userinput></screen>
 
 	    <para>Now that you have your floppy configured correctly,
 	      you must unmount the floppy using the &man.umount.8;
 	      command:</para>
 
             <screen>&prompt.root; <userinput>cd /</userinput>
 &prompt.root; <userinput>umount /mnt</userinput></screen>
 
 	    <para>Now you can remove the floppy from the floppy
 	      drive.</para>
 	  </step>
 
 	  <step>
 	    <title>Connecting Your Null-modem Cable</title>
 
   	    <indexterm><primary>null-modem cable</primary></indexterm>
 	    <para>You now need to connect a
 	      <link linkend="term-cables-null">null-modem cable</link> between
 	      the two machines.  Just connect the cable to the serial
 	      ports of the 2 machines.  <emphasis>A normal serial cable
 	      will not work here</emphasis>, you need a null-modem
 	      cable because it has some of the wires inside crossed
 	      over.</para>
 	  </step>
 
 	  <step>
 	    <title>Booting Up for the Install</title>
 
 	    <para>It is now time to go ahead and start the install.  Put
 	      the <filename>kern.flp</filename> floppy in the floppy
 	      drive of the machine you are doing the headless install
 	      on, and power on the machine.</para>
 	  </step>
 
 	  <step>
 	    <title>Connecting to Your Headless Machine</title>
 	    <indexterm>
 	      <primary><command>cu</command></primary>
 	    </indexterm>
 	    <para>Now you have to connect to that machine with
 	      &man.cu.1;:</para> 
 
 	    <screen>&prompt.root; <userinput>cu -l /dev/cuaa0</userinput></screen>
 	  </step>
       </procedure>
 
       <para>That's it! You should now be able to control the headless machine
 	through your <command>cu</command> session.  It will ask you to
 	put in the <filename>mfsroot.flp</filename>, and then it will come up
 	with a selection of what kind of terminal to use.  Select the
 	FreeBSD color console and proceed with your install!</para>
 
     </sect2>
   </sect1>
 
   <sect1 id="install-diff-media">
-    <title>Preparing Your Own Installation Media</title>
+    <title>»s§@¦w¸Ë¤ù</title>
 
     <note>
-      <para>To prevent repetition, <quote>FreeBSD disc</quote> in this context
-	means a FreeBSD CDROM or DVD that you have purchased or produced
-	yourself.</para>
+      <para>¬°ÁקK­«Âл¡©ú¡A¦b¤å¤¤©Ò´£¨ìªº¡uFreeBSD ¥úºÐ¡v¡A
+	  ¦b³o¸Ì«üªº¬O±z©ÒÁʶR©Î¦Û¦æ¿N¿ýªº FreeBSD CDROM ©Î DVD¡C</para>
     </note>
 
     <para>There may be some situations in which you need to create your own
       FreeBSD installation media and/or source.  This might be physical media,
       such as a tape, or a source that <application>sysinstall</application>
       can use to retrieve the files, such as a local FTP site, or an &ms-dos;
       partition.</para>
 
     <para>For example:</para>
 
     <itemizedlist>
       <listitem>
 	<para>You have many machines connected to your local network, and one
 	  FreeBSD disc.  You want to create a local FTP site using the
 	  contents of the FreeBSD disc, and then have your machines use this
 	  local FTP site instead of needing to connect to the Internet.</para>
       </listitem>
 
       <listitem>
 	<para>You have a FreeBSD disc, and FreeBSD does not recognize your CD/DVD
 	  drive, but &ms-dos;/&windows; does.  You want to copy the FreeBSD
 	  installation files to a DOS partition on the same computer, and
 	  then install FreeBSD using those files.</para>
       </listitem>
 
       <listitem>
 	<para>The computer you want to install on does not have a CD/DVD
 	  drive or a network card, but you can connect a
 	  <quote>Laplink-style</quote> serial or parallel cable to a computer
 	  that does.</para>
       </listitem>
 
       <listitem>
 	<para>You want to create a tape that can be used to install
 	  FreeBSD.</para>
       </listitem>
     </itemizedlist>
 
     <sect2 id="install-cdrom">
       <title>Creating an Installation CDROM</title>
 
       <para>As part of each release, the FreeBSD project makes available two
 	CDROM images (<quote>ISO images</quote>).  These images can be written
 	(<quote>burned</quote>) to CDs if you have a CD writer, and then used
 	to install FreeBSD.  If you have a CD writer, and bandwidth is cheap,
 	then this is the easiest way to install FreeBSD.</para>
 
       <procedure>
 	<step>
 	  <title>Download the Correct ISO Images</title>
 
 	  <para>The ISO images for each release can be downloaded from <filename>ftp://ftp.FreeBSD.org/pub/FreeBSD/ISO-IMAGES-<replaceable>arch</replaceable>/<replaceable>version</replaceable></filename> or the closest mirror.  
 	    Substitute <replaceable>arch</replaceable> and 
 	    <replaceable>version</replaceable> as appropriate.</para>
 
 	  <para>That directory will normally contain the following images:</para>
 
 	  <table frame="none">
 	    <title>FreeBSD 4.<replaceable>X</replaceable> ISO Image Names and Meanings</title>
 
 	    <tgroup cols="2">
 	      <thead>
 		<row>
 		  <entry>Filename</entry>
 
 		  <entry>Contains</entry>
 		</row>
 	      </thead>
 
 	      <tbody>
 		<row>
 		  <entry><filename><replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-miniinst.iso</filename></entry>
 		  
 		  <entry>Everything you need to install FreeBSD.</entry>
 		</row>
 
 		<row>
 		  <entry><filename><replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-disc1.iso</filename></entry>
 
 		  <entry>Everything you need to install FreeBSD, and as many
 		    additional third party packages as would fit on the
 		    disc.</entry>
 		</row>
 
 		<row>
 		  <entry><filename><replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-disc2.iso</filename></entry>
 
 		  <entry>A <quote>live filesystem</quote>, which is used in
 		    conjunction with the <quote>Repair</quote> facility in
 		    <application>sysinstall</application>.  A copy of the
 		    FreeBSD CVS tree.  As many additional third party packages
 		    as would fit on the disc.</entry>
 		</row>
 	      </tbody>
 	    </tgroup>
 	  </table>
 
 	  <table frame="none">
 	    <title>FreeBSD 5.<replaceable>X</replaceable> ISO Image Names and Meanings</title>
 
 	    <tgroup cols="2">
 	      <thead>
 		<row>
 		  <entry>Filename</entry>
 
 		  <entry>Contains</entry>
 		</row>
 	      </thead>
 
 	      <tbody>
 		<row>
 		  <entry><filename><replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-bootonly.iso</filename></entry>
 
 		  <entry>Everything you need to boot into a FreeBSD
 		    kernel and start the installation interface.
 		    The installable files have to be pulled over FTP
 		    or some other supported source.</entry>
 		</row>
 
 		<row>
 		  <entry><filename><replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-miniinst.iso</filename></entry>
 		  
 		  <entry>Everything you need to install FreeBSD.</entry>
 		</row>
 
 		<row>
 		  <entry><filename><replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-disc1.iso</filename></entry>
 
 		  <entry>Everything you need to install &os; and a
 		    <quote>live filesystem</quote>, which is used in
 		    conjunction with the <quote>Repair</quote> facility
 		    in <application>sysinstall</application>.</entry>
 		</row>
 
 		<row>
 		  <entry><filename><replaceable>version</replaceable>-RELEASE-<replaceable>arch</replaceable>-disc2.iso</filename></entry>
 
 		  <entry>&os; documentation and as many third party packages as
 		    would fit on the disc.</entry>
 		</row>
 	      </tbody>
 	    </tgroup>
 	  </table>
 
 	  <para>You <emphasis>must</emphasis> download one of either the miniinst
 	    ISO image, or the image of disc one.  Do not download both of them,
 	    since the disc one image contains everything that the miniinst ISO
 	    image contains.</para>
 
 	  <note>
 	    <para>The miniinst ISO image is only available for releases prior
 	      to 5.4-RELEASE.</para>
 	  </note>
 
 	  <para>Use the miniinst ISO if Internet access is cheap for you.  It will
 	    let you install FreeBSD, and you can then install third party
 	    packages by downloading them using the ports/packages system (see
 	    <xref linkend="ports">) as
 	    necessary.</para>
 
 	  <para>Use the image of disc one if you want to install a
 	    &os;&nbsp;4.<replaceable>X</replaceable> release and want
 	    a reasonable selection of third party packages on the disc
 	    as well.</para>
 
 	  <para>The additional disc images are useful, but not essential,
 	    especially if you have high-speed access to the Internet.</para>
 	</step>
 
 	<step>
 	  <title>Write the CDs</title>
 
 	  <para>You must then write the CD images to disc.  If you will be
 	    doing this on another FreeBSD system then see 
 	    <xref linkend="creating-cds"> for more information (in 
 	    particular, <xref linkend="burncd"> and 
 	    <xref linkend="cdrecord">).</para>
 
 	  <para>If you will be doing this on another platform then you will
 	    need to use whatever utilities exist to control your CD writer on
 	    that platform.  The images provided are in the standard ISO format,
 	    which many CD writing applications support.</para>
 	</step>
       </procedure>
 
       <note><para>If you are interested in building a customized
         release of FreeBSD, please see the <ulink
         url="&url.articles.releng;">Release Engineering
         Article</ulink>.</para></note>
 
     </sect2>
 
     <sect2 id="install-ftp">
       <title>Creating a Local FTP Site with a FreeBSD Disc</title>
 	
       <indexterm>
 	<primary>installation</primary>
 	<secondary>network</secondary>
 	<tertiary>FTP</tertiary>
       </indexterm>
 
       <para>FreeBSD discs are laid out in the same way as the FTP site.  This
 	makes it very easy for you to create a local FTP site that can be used
 	by other machines on your network when installing FreeBSD.</para>
 
       <procedure>
 	<step>
 	  <para>On the FreeBSD computer that will host the FTP site, ensure
 	    that the CDROM is in the drive, and mounted on
 	    <filename>/cdrom</filename>.</para>
 
 	  <screen>&prompt.root; <userinput>mount /cdrom</userinput></screen>
 	</step>
 
 	<step>
 	  <para>Create an account for anonymous FTP in
 	    <filename>/etc/passwd</filename>.  Do this by editing
 	    <filename>/etc/passwd</filename> using &man.vipw.8; and adding
 	    this line:</para>
 
 	  <programlisting>ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
 	</step>
 
 	<step>
 	  <para>Ensure that the FTP service is enabled in
 	    <filename>/etc/inetd.conf</filename>.</para>
 	</step>
       </procedure>
 
       <para>Anyone with network connectivity to your machine can now
 	chose a media type of FTP and type in
 	<userinput>ftp://<replaceable>your machine</replaceable></userinput>
 	after picking <quote>Other</quote> in the FTP sites menu during
 	the install.</para>
 
       <note>
 	<para>If the boot media (floppy disks, usually) for your FTP
 	  clients is not precisely the same version as that provided
 	  by the local FTP site, then <application>sysinstall</application> will not let you
 	  complete the installation.  If the versions are not similar and
 	  you want to override this, you must go into the <guimenu>Options</guimenu> menu
 	  and change distribution name to
 	  <guimenuitem>any</guimenuitem>.</para>
       </note>
 
       <warning>
 	<para>This approach is OK for a machine that is on your local network,
 	  and that is protected by your firewall.  Offering up FTP services to
 	  other machines over the Internet (and not your local network)
 	  exposes your computer to the attention of crackers and other
 	  undesirables.  We strongly recommend that you follow good security
 	  practices if you do this.</para>
       </warning>
     </sect2>
 
       <sect2>
         <title>Creating Installation Floppies</title>
 
       <indexterm>
 	<primary>installation</primary>
 	<secondary>floppies</secondary>
       </indexterm>
 
       <para>If you must install from floppy disk (which we suggest you
 	do <emphasis>not</emphasis> do), either due to unsupported
 	hardware or simply because you insist on doing things the hard
 	way, you must first prepare some floppies for the installation.</para>
 
 	<para>At a minimum, you will need as many 1.44&nbsp;MB or 1.2&nbsp;MB floppies
 	  as it takes to hold all the files in the
 	  <filename>bin</filename> (binary distribution) directory.  If
 	  you are preparing the floppies from DOS, then they
 	  <emphasis>must</emphasis> be formatted using the &ms-dos;
 	  <command>FORMAT</command> command.  If you are using &windows;,
 	  use Explorer to format the disks (right-click on the
 	  <devicename>A:</devicename> drive, and select <quote>Format</quote>).</para>
 
 	<para>Do <emphasis>not</emphasis> trust factory pre-formatted
 	  floppies.  Format them again yourself, just to be sure.  Many
 	  problems reported by our users in the past have resulted from
 	  the use of improperly formatted media, which is why we are
 	  making a point of it now.</para>
 
 	<para>If you are creating the floppies on another FreeBSD machine,
 	  a format is still not a bad idea, though you do not need to put
 	  a DOS filesystem on each floppy.  You can use the
 	  <command>disklabel</command> and <command>newfs</command>
 	  commands to put a UFS filesystem on them instead, as the
 	  following sequence of commands (for a 3.5" 1.44&nbsp;MB floppy)
 	  illustrates:</para>
 
 	<screen>&prompt.root; <userinput>fdformat -f 1440 fd0.1440</userinput>
 &prompt.root; <userinput>disklabel -w -r fd0.1440 floppy3</userinput>
 &prompt.root; <userinput>newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0</userinput></screen>
 
 	<note>
 	  <para>Use <literal>fd0.1200</literal> and
 	    <literal>floppy5</literal> for 5.25" 1.2&nbsp;MB disks.</para>
 	</note>
 
 	<para>Then you can mount and write to them like any other
 	  filesystem.</para>
 
 	<para>After you have formatted the floppies, you will need to copy
 	  the files to them.  The distribution files are split into chunks
 	  conveniently sized so that five of them will fit on a conventional
 	  1.44&nbsp;MB floppy.  Go through all your floppies, packing as many
 	  files as will fit on each one, until you have all of the
 	  distributions you want packed up in this fashion.  Each
 	  distribution should go into a subdirectory on the floppy, e.g.:
 	  <filename>a:\bin\bin.aa</filename>,
 	  <filename>a:\bin\bin.ab</filename>, and so on.</para>
 
 	<para>Once you come to the Media screen during the install
 	  process, select <guimenuitem>Floppy</guimenuitem> and you
 	  will be prompted for the rest.</para>
       </sect2>
 
       <sect2 id="install-msdos">
         <title>Installing from an &ms-dos; Partition</title>
 
 	<indexterm>
 	  <primary>installation</primary>
 	  <secondary>from MS-DOS</secondary>
 	</indexterm>
 	<para>To prepare for an installation from an &ms-dos; partition,
 	  copy the files from the distribution into a directory
           called <filename>freebsd</filename> in the root directory of the
 	  partition.  For example, <filename>c:\freebsd</filename>.  The
 	  directory structure of the CDROM or FTP site must be partially
 	  reproduced within this directory, so we suggest using the DOS
 	  <command>xcopy</command> command if you are copying it from a CD.
 	  For example, to prepare for a minimal installation of
 	  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>Assuming that <devicename>C:</devicename> is where you have
 	  free space and <devicename>E:</devicename> is where your CDROM
 	  is mounted.</para>
 	
 	<para>If you do not have a CDROM drive, you can download the
 	  distribution from <ulink
 	  url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/">ftp.FreeBSD.org</ulink>.
 	  Each distribution is in its own directory; for example, the
 	  <emphasis>base</emphasis> distribution can be found in the <ulink
 	  url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/base/">&rel.current;/base/</ulink>
 	  directory.</para>
 
 	<note>
 	  <para>In the 4.X and older releases of &os; the <quote>base</quote>
 	    distribution is called <quote>bin</quote>.  Adjust the sample
 	    commands and URLs above accordingly, if you are using one of these
 	    versions.</para>
 	</note>
     
 	<para>For as many distributions you wish to install from an &ms-dos;
 	  partition (and you have the free space for), install each one
 	  under <filename>c:\freebsd</filename> &mdash; the
 	  <literal>BIN</literal> distribution is the only one required for
 	  a minimum installation.</para>
       </sect2>
 
       <sect2>
         <title>Creating an Installation Tape</title>
 
 	<indexterm>
 	  <primary>installation</primary>
 	  <secondary>from QIC/SCSI Tape</secondary>
 	</indexterm>
 	<para>Installing from tape is probably the easiest method, short
 	  of an online FTP install or CDROM install.  The installation
 	  program expects the files to be simply tarred onto the tape.
 	  After getting all of the distribution files you are interested
 	  in, simply tar them onto the tape:</para>
 
 	<screen>&prompt.root; <userinput>cd /freebsd/distdir</userinput>
 &prompt.root; <userinput>tar cvf /dev/rwt0 dist1 ... dist2</userinput></screen>
 
 	<para>When you perform the installation, you should make
 	  sure that you leave enough room in some temporary directory
 	  (which you will be allowed to choose) to accommodate the
 	  <emphasis>full</emphasis> contents of the tape you have created.
 	  Due to the non-random access nature of tapes, this method of
 	  installation requires quite a bit of temporary storage.</para>
 
 	<note>
 	  <para>When starting the installation, the tape must be in the
 	    drive <emphasis>before</emphasis> booting from the boot
 	    floppy.  The installation probe may otherwise fail to find
 	    it.</para>
 	</note>
       </sect2>
 
       <sect2>
         <title>Before Installing over a Network</title>
 
 	<indexterm>
 	  <primary>installation</primary>
 	  <secondary>network</secondary>
 	  <tertiary>serial (SLIP or PPP)</tertiary>
 	</indexterm>
 	<indexterm>
 	  <primary>installation</primary>
 	  <secondary>network</secondary>
 	  <tertiary>parallel (PLIP)</tertiary>
 	</indexterm>
 	<indexterm>
 	  <primary>installation</primary>
 	  <secondary>network</secondary>
 	  <tertiary>Ethernet</tertiary>
 	</indexterm>
 	<para>There are three types of network installations available.
 	  Serial port (SLIP or PPP), Parallel port (PLIP (laplink cable)),
 	  or Ethernet (a standard Ethernet controller (includes some
 	  PCMCIA)).</para>
 
 	<para>The SLIP support is rather primitive, and limited primarily
 	  to hard-wired links, such as a serial cable running between a
 	  laptop computer and another computer.  The link should be
 	  hard-wired as the SLIP installation does not currently offer a
 	  dialing capability; that facility is provided with the PPP
 	  utility, which should be used in preference to SLIP whenever
 	  possible.</para>
 
 	<para>If you are using a modem, then PPP is almost certainly
 	  your only choice.  Make sure that you have your service
 	  provider's information handy as you will need to know it fairly
 	  early in the installation process.</para>  
 
 	<para>If you use PAP or CHAP to connect your ISP (in other words, if
 	  you can connect to the ISP in &windows; without using a script), then
 	  all you will need to do is type in <command>dial</command> at the
 	  <application>ppp</application> prompt.  Otherwise, you will need to
 	  know how to dial your ISP using the <quote>AT commands</quote>
 	  specific to your modem, as the PPP dialer provides only a very
 	  simple terminal emulator.  Please refer to the user-ppp <link
 	  linkend="userppp">handbook</link> and <ulink
 	  url="&url.books.faq;/ppp.html">FAQ</ulink> entries for further information.
 	  If you have problems, logging can be directed to the screen using
 	  the command <command>set log local ...</command>.</para>
 
 	<para>If a hard-wired connection to another FreeBSD (2.0-R or
 	  later) machine is available, you might also consider installing
 	  over a <quote>laplink</quote> parallel port cable.  The data rate
 	  over the parallel port is much higher than what is typically
 	  possible over a serial line (up to 50&nbsp;kbytes/sec), thus resulting
 	  in a quicker installation.</para>
 
 	<para>Finally, for the fastest possible network installation, an
 	  Ethernet adapter is always a good choice!  FreeBSD supports most
 	  common PC Ethernet cards; a table of supported cards (and their
 	  required settings) is provided in the Hardware Notes for each
 	  release of FreeBSD.  If you are using one of the supported PCMCIA
 	  Ethernet cards, also be sure that it is plugged in
 	  <emphasis>before</emphasis> the laptop is powered on!  FreeBSD does
 	  not, unfortunately, currently support hot insertion of PCMCIA cards
 	  during installation.</para>
 
 	<para>You will also need to know your IP address on the network,
 	  the netmask value for your address class, and the name of your
 	  machine.  If you are installing over a PPP connection and do not
 	  have a static IP, fear not, the IP address can be dynamically
 	  assigned by your ISP.  Your system administrator can tell you
 	  which values to use for your particular network setup.  If you
 	  will be referring to other hosts by name rather than IP address,
 	  you will also need a name server and possibly the address of a
 	  gateway (if you are using PPP, it is your provider's IP address)
 	  to use in talking to it.  If you want to install by FTP via a
 	  HTTP proxy, you will also need the proxy's address.
 	  If you do not know the answers to all or most of these questions,
 	  then you should really probably talk to your system administrator
 	  or ISP <emphasis>before</emphasis> trying this type of
 	  installation.</para>
 
 	<sect3>
 	  <title>Before Installing via NFS</title>
 
 	  <indexterm>
 	    <primary>installation</primary>
 	    <secondary>network</secondary>
 	    <tertiary>NFS</tertiary>
 	  </indexterm>
 	  <para>The NFS installation is fairly straight-forward.  Simply
 	    copy the FreeBSD distribution files you want onto an NFS server
 	    and then point the NFS media selection at it.</para>
 
 	  <para>If this server supports only <quote>privileged port</quote>
 	    (as is generally the default for Sun workstations), you will
 	    need to set the option <literal>NFS Secure</literal> in the
 	    <guimenu>Options</guimenu> menu before installation can proceed.</para>
 
 	  <para>If you have a poor quality Ethernet card which suffers
 	    from very slow transfer rates, you may also wish to toggle the
 	    <literal>NFS Slow</literal> flag.</para>
 
 	  <para>In order for NFS installation to work, the server must
 	    support subdir mounts, for example, if your FreeBSD&nbsp;&rel.current; distribution
 	    directory lives on:
 	    <filename>ziggy:/usr/archive/stuff/FreeBSD</filename>, then
 	    <hostid>ziggy</hostid> will have to allow the direct mounting
 	    of <filename>/usr/archive/stuff/FreeBSD</filename>, not just
 	    <filename>/usr</filename> or
 	    <filename>/usr/archive/stuff</filename>.</para>
 
 	  <para>In FreeBSD's <filename>/etc/exports</filename> file, this
 	    is controlled by the <option>-alldirs</option> options.  Other NFS
 	    servers may have different conventions.  If you are getting
 	    <errorname>permission denied</errorname> messages from the
 	    server, then it is likely that you do not have this enabled
 	    properly.</para>
 	</sect3>
 
       </sect2>
   </sect1>
 </chapter>
 
 <!-- 
      Local Variables:
      mode: sgml
      sgml-declaration: "../chapter.decl"
      sgml-indent-data: t
      sgml-omittag: nil
      sgml-always-quote-attributes: t
      sgml-parent-document: ("../book.sgml" "part" "chapter")
      End:
 -->
diff --git a/zh_TW.Big5/books/handbook/introduction/chapter.sgml b/zh_TW.Big5/books/handbook/introduction/chapter.sgml
index c408fb0685..1b3e731eac 100644
--- a/zh_TW.Big5/books/handbook/introduction/chapter.sgml
+++ b/zh_TW.Big5/books/handbook/introduction/chapter.sgml
@@ -1,951 +1,824 @@
 <!--
      The FreeBSD Documentation Project
 
      $FreeBSD$
 -->
 
 <chapter id="introduction">
   <chapterinfo>
     <authorgroup>
       <author>
         <firstname>Jim</firstname>
 	<surname>Mock</surname>
 	<contrib>Restructured, reorganized, and parts
 	  rewritten by </contrib>
       </author>
     </authorgroup>
   </chapterinfo>
 
   <title>²¤¶</title>
 
   <sect1 id="introduction-synopsis">
     <title>·§­z</title>
 
     <para>«D±`·PÁ±z¹ï FreeBSD ·P¿³½ì¡I¥H¤U³¹¸`²[»\ FreeBSD
-      ­pµeªº¦U¤è­±¡G¤ñ¦p¥¦ªº¾ú¥v¡B¥Ø¼Ð¡B¶}µo¼Ò¦¡µ¥µ¥¡C</para>
+      ­p¹ºªº¦U¤è­±¡G¤ñ¦p¥¦ªº¾ú¥v¡B¥Ø¼Ð¡B¶}µo¼Ò¦¡µ¥µ¥¡C</para>
 
-    <para>Ū§¹³o³¹¡A¥i¥HÁA¸Ñ¡G</para>
+    <para>Ū§¹³o³¹¡A±z±N¤F¸Ñ¡J</para>
 
     <itemizedlist>
       <listitem>
 	<para>FreeBSD »P¨ä¥L OS ¤§¶¡ªºÃö«Y¡F</para>
       </listitem>
       <listitem>
-	<para>FreeBSD ­pµeªº¾ú¥v²W·½¡F</para>
+	<para>FreeBSD ­p¹ºªº¾ú¥v²W·½¡F</para>
       </listitem>
       <listitem>
-	<para>FreeBSD ­pµeªº¥Ø¼Ð¡F</para>
+	<para>FreeBSD ­p¹ºªº¥Ø¼Ð¡F</para>
       </listitem>
       <listitem>
 	<para>FreeBSD open-source ¶}µo¼Ò¦¡ªº°ò¦·§©À¡F</para>
       </listitem>
       <listitem>
 	<para>·íµMÅo¡AÁÙ¦³ <quote>FreeBSD</quote> ³o¦W¦rªº½t¬G¡C</para>
       </listitem>
     </itemizedlist>
 
   </sect1>
 
   <sect1 id="nutshell">
     <title>Welcome to FreeBSD!</title>
     <indexterm><primary>4.4BSD-Lite</primary></indexterm> 
 
     <para>FreeBSD ¬O¤@­Ó±q 4.4BSD-Lite ­l¥Í¥X¦Ó¯à¦b¥H Intel (x86 and &itanium;),
       AMD64, <trademark>Alpha</trademark>, Sun &ultrasparc; 
       ¬°°ò¦ªº¹q¸£¤W°õ¦æªº§@·~¨t²Î¡C¦P®É¡A²¾´Ó¨ì¨ä¥L¥­¥xªº¤u§@¤]¦b¶i¦æ¤¤¡C
-      ¹ï©ó¥»­p¹º¾ú¥vªº¤¶²Ð¡A½Ð¬Ý <link linkend="history">FreeBSD ªºÂ²µu¾ú¥v</link>¡A
-      ¹ï©ó FreeBSD ªº³Ì·sª©¥»¤¶²Ð¡A½Ð¬Ý <link linkend="relnotes"> current release
-      </link> 
-
-is a 4.4BSD-Lite based operating system for
-      Intel (x86 and &itanium;), AMD64, <trademark>Alpha</trademark>, Sun
-      &ultrasparc; computers.  Ports to other
-      architectures are also underway. 
-      You can also
-      read about <link linkend="history">the history of FreeBSD</link>,
-      or the <link linkend="relnotes">current release</link>.  If you
-      are interested in contributing something to the Project (code,
-      hardware, unmarked bills), see the <ulink
-	url="&url.articles.contributing;/index.html">Contributing to FreeBSD</ulink> article.</para>
+      ¹ï©ó¥»­p¹º¾ú¥vªº¤¶²Ð¡A½Ð¬Ý <link linkend="history">FreeBSD ¾ú¥v²W·½</link>¡A
+      ¹ï©ó FreeBSD ªº³Ì·sª©¥»¤¶²Ð¡A½Ð¬Ý <link linkend="relnotes">current release
+      </link>¡C­Y¥´ºâ¹ï©ó FreeBSD ­p¹º¦³©Ò°^Ämªº¸Ü(¹³¬Oµ{¦¡½XµwÅé³]³Æ¡A¸êª÷)¡A
+      ½Ð¬Ý <ulink url="&url.articles.contributing;/index.html">¦p¦ó¹ï FreeBSD 
+      ¦³°^Äm</ulink>¡C</para>
 
     <sect2 id="os-overview">
-      <title>What Can FreeBSD Do?</title>
+      <title>FreeBSD ¯à°µ¤°»ò¡H</title>
 
-      <para>FreeBSD has many noteworthy features.  Some of these
-        are:</para>
+      <para>FreeBSD ´£¨Ñµ¹§A³\¦h¥ý¶i¥\¯à¡C³o¨Ç¥\¯à¥]¬A¡G</para>
 
       <itemizedlist>
-        <indexterm><primary>preemptive multitasking</primary></indexterm>
+        <indexterm><primary>¥ý¦û¦¡¦h¤u(preemptive multitasking)</primary></indexterm>
 	<listitem>
-	  <para><emphasis>Preemptive multitasking</emphasis> with
-	    dynamic priority adjustment to ensure smooth and fair
-	    sharing of the computer between applications and users, even
-	    under the heaviest of loads.</para>
+	  <para>°ÊºAÀu¥ýÅv½Õ¾ãªº¡y¥ý¦û¦¡¦h¤u¡z¯à°÷½T«O¡A§Y¨Ï¦b¨t²Î­t¾á«Ü­«ªº±¡ªp¤U¡A
+	    µ{¦¡°õ¦æ¥­¶¶¨Ã¥BÀ³¥Îµ{¦¡»P¨Ï¥ÎªÌ¤½¥­¦a¦@¨É¸ê·½¡C</para>
 	</listitem>
 
-	<indexterm><primary>multi-user facilities</primary></indexterm>
+	<indexterm><primary>¤ä´©¦h¤H¦@¥Î</primary></indexterm>
 	<listitem>
-	  <para><emphasis>Multi-user facilities</emphasis> which allow many
-	    people to use a FreeBSD system simultaneously for a variety
-	    of things.  This means, for example, that system peripherals
-	    such as printers and tape drives are properly shared between
-	    all users on the system or the network and that individual
-	    resource limits can be placed on users or groups of users,
-	    protecting critical system resources from over-use.</para>
+	  <para>¡y¦h¤H¦@¥Î(multi-user)¡z¥NªíµÛ³\¦h¤H¥i¥H¦P®É¨Ï¥Î¤@­Ó FreeBSD ¨t²Î¨Ó³B²z¦U¦Ûªº¨Æ°È¡C
+	    ¨t²ÎªºµwÅé©PÃä(¦p¦Lªí¾÷¤ÎºÏ±a¾÷)¤]¥i¥HÅý©Ò¦³ªº¨Ï¥ÎªÌ¾A·í¦a¤À¨É¡C
+	    ¤]¥i¥H°w¹ï¦U§O¨Ï¥ÎªÌ©Î¤@¸s¨Ï¥ÎªÌªº¨t²Î¸ê·½¡A¤©¥H³]­­¡A
+	    ¥H«OÅ@¨t²Î¤£­P³Q¹L«×¨Ï¥Î¡C</para>
 	</listitem>
       
-	<indexterm><primary>TCP/IP networking</primary></indexterm>
+	<indexterm><primary>TCP/IP ºô¸ô¥\¯à</primary></indexterm>
 	<listitem>
-	  <para>Strong <emphasis>TCP/IP networking</emphasis> with
-	    support for industry standards such as SLIP, PPP, NFS, DHCP,
-	    and NIS.  This means that your FreeBSD machine can
-	    interoperate easily with other systems as well as act as an
-	    enterprise server, providing vital functions such as NFS
-	    (remote file access) and email services or putting your
-	    organization on the Internet with WWW, FTP, routing and
-	    firewall (security) services.</para>
+	  <para>¦n¥Îªº¡yTCP/IP ºô¸ô¥\¯à¡z¥i¤ä´©³\¦h·~¬É¼Ð·Ç¡A¤ñ¦p¡GSLIP¡BPPP¡BNFS¡BDHCP
+	    ©M NIS ªº¤ä´©¡A¤]´N¬O»¡  FreeBSD ¥i¥H®e©ö¦a¸ò¨ä¥L§@·~¨t²Î³z¹Lºô¸ô¦@¦P¹B§@¡A
+	    ©Î¬O·í§@¥ø·~ªº¦øªA¾¹¥Î³~¡A¨Ò¦p´£¨Ñ»·ºÝÀɮצ@¨É(NFS)¤Î¹q¤l¶l¥ó(email)µ¥ªA°È¡A
+	    ©Î¬OÅý±zªº¥ø·~³s¤Wºô»Úºô¸ô(Internet)¨Ã´£¨Ñ WWW¡BFTP¡B¸ô¥Ñ(routing)
+	    ¡B¤Î¨¾¤õÀð(firewall¡Bsecurity) µ¥¥²³ÆªA°È¡C</para>
 	</listitem>
 
-	<indexterm><primary>memory protection</primary></indexterm>      
+	<indexterm><primary>°O¾ÐÅé«OÅ@</primary></indexterm>
 	<listitem>
-	  <para><emphasis>Memory protection</emphasis> ensures that
-	    applications (or users) cannot interfere with each other. One
-	    application crashing will not affect others in any way.</para>
+	  <para>¡y°O¾ÐÅé«OÅ@(Memory protection)¡z¯à½T«Oµ{¦¡(©Î¬O¨Ï¥ÎªÌ)¤£·|¤¬¬Û¤zÂZ¡A
+	    §Y¨Ï¥ô¦óµ{¦¡¦³¤£¥¿±`ªº¹B§@¡A³£¤£·|¼vÅT¨ä¥Lµ{¦¡ªº°õ¦æ¡C</para>
 	</listitem>
       
 	<listitem>
-	  <para>FreeBSD is a <emphasis>32-bit</emphasis> operating
-	    system (<emphasis>64-bit</emphasis> on the Alpha, &itanium;, AMD64, and &ultrasparc;) and was
-	    designed as such from the ground up.</para>
+	  <para>FreeBSD ¬O¡y32¦ì¤¸(32-bit)¡zªº§@·~¨t²Î
+	    (¦b Alpha¡B&itanium;¡B AMD64 ¤Î &ultrasparc; ¤W«h¬O¡y64¦ì¤¸(64-bit)¡z) 
+	    ¡X ¥´±q¤@¶}©l«K¬O³o¼Ë³]­pªº¡C</para>
 	</listitem>
 
 	<indexterm>
     <primary>X Window System</primary>
     <seealso>XFree86</seealso>
   </indexterm>
 
 	<listitem>
-	  <para>The industry standard <emphasis>X Window System</emphasis>
-	    (X11R6) provides a graphical user interface (GUI) for the cost
-	    of a common VGA card and monitor and comes with full
-	    sources.</para>
+	  <para>·~¬É¼Ð·Çªº¡yX Window ¨t²Î¡z(X11R6)¥i¥H¦b±`¨£ªº«K©y VGA Åã¥Ü¥d/¿Ã¹õ¡A
+	    ´£¨Ñ¤F¹Ï§Î¤Æªº¨Ï¥ÎªÌ¤¶­±(GUI)¡A¨Ã¥B¥]¬A¤F§¹¾ãªº­ì©lµ{¦¡½X¡C</para>
 	</listitem>
 
 	<indexterm>
 	  <primary>binary compatibility</primary>
 	  <secondary>Linux</secondary>
 	</indexterm>
 	<indexterm>
 	  <primary>binary compatibility</primary>
 	  <secondary>SCO</secondary>
 	</indexterm>
 	<indexterm>
 	  <primary>binary compatibility</primary>
 	  <secondary>SVR4</secondary>
 	</indexterm>
 	<indexterm>
 	  <primary>binary compatibility</primary>
 	  <secondary>BSD/OS</secondary>
 	</indexterm>
 	<indexterm>
 	  <primary>binary compatibility</primary>
 	  <secondary>NetBSD</secondary>
 	</indexterm>
 	<listitem>
-	  <para><emphasis>Binary compatibility</emphasis> with many
-	    programs built for Linux, SCO, SVR4, BSDI and NetBSD.</para>
+	  <para>¯à¡yª½±µ°õ¦æ¡z³\¦h¨ä¥L§@·~¨t²Î(¤ñ¦p¡G Linux¡BSCO¡BSVR4¡BBSDI ©M NetBSD)
+	    ªº¥i°õ¦æÀÉ¡C</para>
 	</listitem>
 	
 	<listitem>
-	  <para>Thousands of <emphasis>ready-to-run</emphasis>
-	    applications are available from the FreeBSD
-	    <emphasis>ports</emphasis> and <emphasis>packages</emphasis>
-	    collection.  Why search the net when you can find it all right
-	    here?</para>
+	  <para>¼Æ¥H¸U­pªº¥ß§Y¥i¥H°õ¦æªºÀ³¥Îµ{¦¡¡A³o¨Ç³£¥i³z¹L FreeBSD 
+	    ªº¡yports¡z¤Î¡ypackages¡z³nÅéºÞ²z¾÷¨î¨Ó¨ú±o¡C
+	    ¤£¦A»Ý­n¶O¤ß¨ìºô¸ô¤W¨ì³B·j´M©Ò»Ý­nªº³nÅé¡C</para>
 	</listitem>
       
 	<listitem>
-	  <para>Thousands of additional and
-	    <emphasis>easy-to-port</emphasis> applications are available
-	    on the Internet.  FreeBSD is source code compatible with most
-	    popular commercial &unix; systems and thus most applications
-	    require few, if any, changes to compile.</para>
+	  <para>¦¹¥~¡Aºô¸ô¤W©|¦³¥i«D±`®e©ö²¾´Óªº¼Æ¥H¸U­pÀ³¥Îµ{¦¡¡C
+	    FreeBSD ªº­ì©lµ{¦¡½X»P³\¦h±`¨£ªº°Ó·~ª© &unix; ¨t²Î³£¬Û®e¡A
+	    ©Ò¥H¤j³¡¤Àªºµ{¦¡³£¥u»Ý­n«Ü¤Öªº­×§ï(©Î®Ú¥»¤£¥Î­×§ï)
+	    ¡A´N¥i¥H½sĶ°õ¦æ¡C</para>
 	</listitem>
       
 	<indexterm><primary>virtual memory</primary></indexterm>
 	<listitem>
-	  <para>Demand paged <emphasis>virtual memory</emphasis> and
-	    <quote>merged VM/buffer cache</quote> design efficiently
-	    satisfies applications with large appetites for memory while
-	    still maintaining interactive response to other users.</para>
+	  <para>»Ý­n®É¤~¸m´«(demand paged) <emphasis>virtual memory</emphasis> ¤Î
+	    <quote>merged VM/buffer cache</quote> ªº³]­p¡A
+	    ³oÂI¦b¨t²Î¤¤¦³¥Î¥h¤j¶q°O¾ÐÅ骺µ{¦¡°õ¦æ®É¡A¤´µM¦³¤£¿ùªº®Ä²vªí²{¡C</para>
 	</listitem>
       
         <indexterm>
 	  <primary>Symmetric Multi-Processing (SMP)</primary>
 	</indexterm>
 	<listitem>
-	  <para><emphasis>SMP</emphasis> support for machines with
-	    multiple CPUs.</para>
+	  <para>¤ä´© CPU ªº¹ïºÙ¦h¤u³B²z(SMP)¡G¥i¥H¤ä´©¦h CPU
+	    ªº¹q¸£¨t²Î¡C</para>
 	</listitem>
 
 	<indexterm>
 	  <primary>compilers</primary>
 	  <secondary>C</secondary>
 	</indexterm>
 	<indexterm>
 	  <primary>compilers</primary>
 	  <secondary>C++</secondary>
 	</indexterm>
 	<indexterm>
 	  <primary>compilers</primary>
 	  <secondary>FORTRAN</secondary>
 	</indexterm>
 	<listitem>
-	  <para>A full complement of <emphasis>C</emphasis>,
-	    <emphasis>C++</emphasis>, <emphasis>Fortran</emphasis>, and
-	    <emphasis>Perl</emphasis> development tools.
-	    Many additional languages for advanced research
-	    and development are also available in the ports and packages
-	    collection.</para>
+	  <para>§¹¥þ¬Û®eªº <emphasis>C</emphasis>¡B<emphasis>C++</emphasis>¡B
+	    <emphasis>Fortran</emphasis> ©M <emphasis>Perl</emphasis> ¶}µo¤u¨ã¤ÎÀô¹Ò¡C
+	    ¥H¤Î¨ä¥L³\¦h¥i¨Ñ¶i¶¥¬ãµoªºµ{¦¡»y¨¥¤]¦¬¶°¦b ports ©M packages¡C
+	    </para>
 	</listitem>
 
 	<indexterm><primary>source code</primary></indexterm>
 	<listitem>
-	  <para><emphasis>Source code</emphasis> for the entire system
-	    means you have the greatest degree of control over your
-	    environment.  Why be locked into a proprietary solution
-	    at the mercy of your vendor when you can have a truly open
-	    system?</para>
+	  <para>¾ã­Ó¨t²Î³£¦³¡y­ì©lµ{¦¡½X¡z¡A
+	    ³oÅý§A¹ï§@·~Àô¹Ò¾Ö¦³³Ì§¹¥þªº´x´¤«×¡C
+	    ¬JµM¯à¾Ö¦³§¹¥þ¶}©ñªº¨t²Î¡A¦ó­W³Q¯S©w«Ê³¬³nÅé©Ò¬ù§ô¡A¥ô¼t°ÓÂ\§G©O¡H
+	    </para>
 	</listitem>
       
 	<listitem>
-	  <para>Extensive <emphasis>online
-	    documentation</emphasis>.</para>
+	  <para>¼sªx¥BÂ×´Iªº¡y½u¤W¤å¥ó¡z¡C</para>
 	</listitem>
       
 	<listitem>
-	  <para><emphasis>And many more!</emphasis></para>
+	  <para><emphasis>·íµMÅo¡AÁÙ¤£¤î¦p¦¹¡I</emphasis></para>
 	</listitem>
       </itemizedlist>
-    
+
       <indexterm><primary>4.4BSD-Lite</primary></indexterm>
       <indexterm>
         <primary>Computer Systems Research Group (CSRG)</primary>
       </indexterm>
       <indexterm><primary>U.C. Berkeley</primary></indexterm>
-      <para>FreeBSD is based on the 4.4BSD-Lite release from Computer
-        Systems Research Group (CSRG) at the University of California at
-	Berkeley, and carries on the distinguished tradition of BSD
-	systems development.  In addition to the fine work provided by
-	CSRG, the FreeBSD Project has put in many thousands of hours in
-	fine tuning the system for maximum performance and reliability in
-	real-life load situations.  As many of the commercial giants
-	struggle to field PC operating systems with such features,
-	performance and reliability, FreeBSD can offer them
-	<emphasis>now</emphasis>!</para>
-
-      <para>The applications to which FreeBSD can be put are truly
-        limited only by your own imagination.  From software development
-	to factory automation, inventory control to azimuth correction of
-	remote satellite antennae; if it can be done with a commercial
-	&unix; product then it is more than likely that you can do it with
-	FreeBSD too!  FreeBSD also benefits significantly from
-	literally thousands of high quality applications developed by
-	research centers and universities around the world, often
-	available at little to no cost. Commercial applications are also
-	available and appearing in greater numbers every day.</para>
-
-      <para>Because the source code for FreeBSD itself is generally
-        available, the system can also be customized to an almost unheard
-	of degree for special applications or projects, and in ways not
-	generally possible with operating systems from most major
-	commercial vendors.  Here is just a sampling of some of the
-	applications in which people are currently using FreeBSD:</para>
-    
+      <para>FreeBSD ¨t²Î¤D¬O°ò©ó¬ü°ê¥[¦{¤j¾Ç¬f§JµÜ¤À®Õªº¹q¸£¨t²Î¬ã¨s¸s
+        (Computer Systems Research Group ¤]´N¬O CSRG) ©Òµo¦æªº
+        4.4BSD-Lite¡A¥H¤Î°ò©ó BSD ¨t²Î¶}µoªºÀu¨}¶Ç²Î¡C
+        °£¤F¥Ñ CSRG ©Ò´£¨Ñªº°ª«~½èªº¦¨ªG¡A
+        ¬°¤F´£¨Ñ¥i³B²z¯u¥¿¨ã­t²üªº¤u§@¡A
+        FreeBSD ­p¹º¤]§ë¤J¤F¼Æ¤d¤p®É¥H¤Wªº²Ó³¡½Õ¾ã¡A
+        ¥H¯àÀò±o³Ì¦nªº°õ¦æ®Ä²v¥H¤Î¨t²ÎªºÃ­©w«×¡C
+        ¥¿·í³\¦h°Ó·~¤Wªº¥¨¤H¥¿§V¤O¦a§Æ±æ¯à´£¨Ñ®Ä¯à¤Îí©w®É¡A
+        FreeBSD ¤w¸g¨ã³Æ³o¼Ëªº¯S½è -- <emphasis>´N¬O²{¦b</emphasis>¡I
+	</para>
+
+      <para>FreeBSD ªº¹B¥Î½d³òµL­­¡A¨ä¹ê§¹¥þ­­¨î¦b§Aªº·Q¹³¤O¤W¡C
+        ±q³nÅ骺¶}µo¨ì¤u¼t¦Û°Ê¤Æ¡A©Î¬O¤H³y½Ã¬P¤W­±ªº¤Ñ½uªº¤è¦ì¨¤«×ªº»·ºÝ±±¨î¡F
+        ³o¨Ç¥\¯à­Y¥i¥H¥Î°Ó¥Îªº Unix ²£«~¨Ó¹F¦¨¡A
+        ¨º»ò·¥¦³¥i¯à¨Ï¥Î FreeBSD ¤]¯à¿ì¨ì¡I
+        FreeBSD ¤]¨ü¯q©ó¨Ó¦Û©ó¥þ²y¦U¬ã¨s¤¤¤ß¤Î¤j¾Ç©Ò¶}µoªº¼Æ¤d­Ó°ª«~½èªº³nÅé
+        ¡A³o¨Ç³q±`¥u»Ý­nªá¶O«Ü¤Öªº¶O¥Î©Î®Ú¥»´N¬O§K¶Oªº¡C
+        ·íµM¤]¦³°Ó·~³nÅé¡A¦Ó¥B¥X²{ªº¼Æ¥Ø¬O»P¤é­Ñ¼W¡C</para>
+
+      <para>¥Ñ©ó¨C­Ó¤H³£¥i¥H¨ú±o FreeBSD ªº­ì©lµ{¦¡½X¡A
+        ³o­Ó¨t²Î¥i¥H³Q½Õ¾ã¦Ó¯à°õ¦æ¥ô¦ó­ì¥»§¹¥þµLªk·Q¹³ªº¥\¯à©Î­p¹º¡A
+        ¦Ó¹ï©ó±q¦U¼t°Ó¨ú±oªº§@·~¨t²Î³q±`¨S¦³¿ìªk³o¼Ë¦a³Q­×§ï¡C
+        ¥H¤U´£¨Ñ¤@¨Ç¤H­Ì¨Ï¥Î FreeBSD ªº¨Ò¤l¡G</para>
+
       <itemizedlist>
 	<listitem>
-	  <para><emphasis>Internet Services:</emphasis> The robust TCP/IP
-	    networking built into FreeBSD makes it an ideal platform for a
-	    variety of Internet services such as:</para>
+	  <para><emphasis>ºô¸ôªA°È¡G</emphasis> FreeBSD
+            ¤º«Ø±j«lªººô¸ô¥\¯à¨Ï¥¦¦¨¬°ºô¸ôªA°È(¦p¤U¨Ò)ªº²z·Q¥­¥x¡G</para>
 
 	  <itemizedlist>
 	    <indexterm><primary>FTP servers</primary></indexterm>
 	    <listitem>
-	      <para>FTP servers</para>
+	      <para>ÀɮצøªA¾¹(FTP servers)</para>
 	    </listitem>
 	  
 	    <indexterm><primary>web servers</primary></indexterm>
 	    <listitem>
-	      <para>World Wide Web servers (standard or secure
-	        [SSL])</para>
+	      <para>¥þ²y¸ê°Tºô¦øªA¾¹(WWW servers)
+	        (¼Ð·Çªº©Î§ó¦w¥þªº SSL ³s½u)</para>
 	    </listitem>
-
+	  
 	    <indexterm><primary>firewall</primary></indexterm>
-	    <indexterm><primary>NAT</primary></indexterm>
+	    <indexterm><primary>IP masquerading</primary></indexterm>
 	    <listitem>
-	      <para>Firewalls and NAT (<quote>IP masquerading</quote>)
-	        gateways</para>
+	      <para>¨¾¤õÀð¥H¤Î NAT (<quote>IP masquerading</quote>) 
+		gateways¡C</para>
 	    </listitem>
 	  
-	    <indexterm>
-	      <primary>electronic mail</primary>
-	      <see>email</see>
-	    </indexterm>
-	    <indexterm>
-	      <primary>email</primary>
-	    </indexterm>
+	    <indexterm><primary>electronic mail</primary></indexterm>
 	    <listitem>
-	      <para>Electronic Mail servers</para>
+	      <para>¹q¤l¶l¥ó¦øªA¾¹(Electronic Mail servers)</para>
 	    </listitem>
 	  
 	    <indexterm><primary>USENET</primary></indexterm>
 	    <listitem>
-	      <para>USENET News or Bulletin Board Systems</para>
+	      <para>ºô¸ô·s»D¦øªA¾¹(USENET News)
+		©Î¬O¹q¤l§G§iÄæ¨t²Î(BBS)</para>
 	    </listitem>
 	  
 	    <listitem>
-	      <para>And more...</para>
+	      <para>ÁÙ¦³§ó¦h...</para>
 	    </listitem>
 	  </itemizedlist>
 
-	  <para>With FreeBSD, you can easily start out small with an
-	    inexpensive 386 class PC and upgrade all the way up to a
-	    quad-processor Xeon with RAID storage as your enterprise
-	    grows.</para>
+	  <para>¦³¤F FreeBSD¡A±z¥i¥H®e©ö¦a¥ý¥Î«K©yªº 386 PC¡A
+            ¦A³v¨B¤É¯Å±zªº¾÷¾¹¨ì¥|­Ó CPU ªº Xeon
+            ¨Ã¨Ï¥ÎºÏºÐ°}¦C(RAID)¨Óº¡¨¬±z¥ø·~¹B¥Î¤Wªº»Ý¨D¡C</para>
 	</listitem>
       
 	<listitem>
-	  <para><emphasis>Education:</emphasis>  Are you a student of
-	    computer science or a related engineering field?  There is no
-	    better way of learning about operating systems, computer
-	    architecture and networking than the hands on, under the hood
-	    experience that FreeBSD can provide.  A number of freely
-	    available CAD, mathematical and graphic design packages also
-	    make it highly useful to those whose primary interest in a
-	    computer is to get <emphasis>other</emphasis> work
-	    done!</para>
+	  <para><emphasis>±Ð¨|¡G</emphasis>
+            ¦pªG§A¬O¸ê°T©Î¬ÛÃö¤uµ{»â°ìªº¾Ç¥Í¡A¦A¤]¨S¦³¤ñ¨Ï¥Î FreeBSD
+            ¯à¾Ç¨ì§ó¦h§@·~¨t²Î¡B­pºâ¾÷µ²ºc¡B¤Îºô¸ôªº¤èªk¤F¡C
+            ¥t¥~¦pªG§A·Q§Q¥Î¹q¸£¨Ó³B²z¤@¨Ç<emphasis>¨ä¥Lªº</emphasis>
+            ¤u§@¡AÁÙ¦³¤@¨Ç¦p CAD¡B
+            ¼Æ¾Ç¹Bºâ¥H¤Î¹Ï§Î³B²z³nÅéµ¥¥i¥H§K¶O¦a¨ú±o¨Ï¥Î¡C</para>
 	</listitem>
       
 	<listitem>
-	  <para><emphasis>Research:</emphasis>  With source code for the
-	    entire system available, FreeBSD is an excellent platform for
-	    research in operating systems as well as other branches of
-	    computer science.  FreeBSD's freely available nature also makes
-	    it possible for remote groups to collaborate on ideas or
-	    shared development without having to worry about special
-	    licensing agreements or limitations on what may be discussed
-	    in open forums.</para>
+	  <para><emphasis>¬ã¨s¡G</emphasis>¦³¤F§¹¾ãªº­ì©lµ{¦¡½X¡AFreeBSD
+            ¬O¬ã¨s§@·~¨t²Î¤Î¹q¸£¬ì¾Çªº·¥¨ÎÀô¹Ò¡C
+            ¨ã¦³§K¶O¥B¦Û¥Ñ¨ú±o¯S©Êªº FreeBSD
+            ¤]¨Ï±o¤@­Ó¤À¸m¨â¦aªº¦X§@­p¹º¡A¤£¥²¾á¤ßª©Åv¤Î¨t²Î¶}©ñ©Êªº°ÝÃD¡A
+            ¦Ó¯à¦Û¦bªº¥æ¬y¡C</para>
 	</listitem>
       
 	<indexterm><primary>router</primary></indexterm>
 	<indexterm><primary>DNS Server</primary></indexterm>
 	<listitem>
-	  <para><emphasis>Networking:</emphasis>  Need a new router?  A
-	    name server (DNS)? A firewall to keep people out of your
-	    internal network?  FreeBSD can easily turn that unused 386 or
-	    486 PC sitting in the corner into an advanced router with
-	    sophisticated packet-filtering capabilities.</para>
-	</listitem>
+	  <para><emphasis>ºô¸ô¡G</emphasis>
+            §A¦pªG»Ý­n router¡BName Server (DNS) ©Î¦w¥þªº¨¾¤õÀð(Firewall)¡A
+            FreeBSD ¥i¥H»´©öªº±N§A¨S¦³¥Î¨ìªº 386 ©Î 486 PC
+            Åܨ­¦¨¬°µ´¨Îªº¦øªA¾¹¡A¬Æ¦Ü¨ã¦³¹LÂo«Ê¥](packet-filter) ªº¥\¯à¡C
+	    </para>
+	</listitem>    
       
 	<indexterm>
 	  <primary>X Window System</primary>
 	  <secondary>XFree86</secondary>
 	</indexterm>
 	<indexterm>
 	  <primary>X Window System</primary>
 	  <secondary>Accelerated-X</secondary>
 	</indexterm>
 	<listitem>
-	  <para><emphasis>X Window workstation:</emphasis> FreeBSD is a
-	    fine choice for an inexpensive X terminal solution, either
-	    using the freely available X11 server or one of the
-	    excellent commercial servers provided by <ulink
-	    url="http://www.xig.com">Xi Graphics</ulink>.  Unlike an
-	    X terminal, FreeBSD allows many applications to be run
-	    locally if desired, thus relieving the burden on a central
-	    server.  FreeBSD can even boot <quote>diskless</quote>, making
-	    individual workstations even cheaper and easier to
-	    administer.</para>
+	  <para><emphasis>X µøµ¡¤u§@¯¸¡G</emphasis> FreeBSD ¬O X
+            ²×ºÝ¾÷ªº¨}µ¦¡A§A¥i¥H¨Ï¥Î§K¶Oªº X11 Server ©Î¬O¥Ñ
+            <ulink url="http://www.xig.com">Xi Graphics</ulink> ©Ò´£¨Ñªº°Ó·~ª© X Server¡C
+            FreeBSD ¤£¦ý¥i¥H¥R·í»·ºÝ X µ{¦¡²×ºÝ¾÷¡A
+            ¤]¥i¥H°õ¦æ¥»¦aªº X µ{¦¡¦Ó´î»´¤j«¬¤u§@¯¸ªº­t²ü¡C
+            ¦pªG¦³¤@¥x¤¤¥¡¦øªA¾¹ªº¸Ü¡AFreeBSD ¬Æ¦Ü¥i¥H¸g¥Ñºô¸ô¶}¾÷
+            (¤£»ÝµwºÐ¡A¤]´N¬O<quote>diskless</quote>)
+	    ¡A¦ÓÅܦ¨§ó«K©y¥B©ö©óºÞ²zªº¤u§@¯¸¡C</para>
 	</listitem>
       
 	<indexterm><primary>GNU Compiler Collection</primary></indexterm>
 	<listitem>
-	  <para><emphasis>Software Development:</emphasis>  The basic
-	    FreeBSD system comes with a full complement of development
-	    tools including the renowned GNU C/C++ compiler and
-	    debugger.</para>
+	  <para><emphasis>³nÅé¶}µo¡G</emphasis>
+            °ò¥»¦w¸Ëªº FreeBSD ´N¥]§t¤F§¹¾ãªºµ{¦¡¶}µo¤u¨ã¡A¦p GNU C/C++ 
+            ½sĶ¾¹¤Î°£¿ù¾¹¡C</para>
 	</listitem>
       </itemizedlist>
     
-      <para>FreeBSD is available in both source and binary form on CDROM,
-	DVD,
-        and via anonymous FTP.  Please see <xref linkend="mirrors">
-        for more information about obtaining FreeBSD.</para>
+      <para>§A¥i¥H¸g¥Ñ¿N¿ý CDROM¡BDVD ©Î¬O±q FTP ¯¸¤W§ì¦^ FreeBSD --
+        ¥]¬A¥ß§Y¥i°õ¦æªº¨t²Î¥H¤Î¨t²Îªº§¹¾ãµ{¦¡½X¡C
+        ¸Ô±¡½Ð°Ñ¾\ <xref linkend="mirrors"> ¨ú±o FreeBSD¡C</para>
     </sect2>
 
     <sect2>
-      <title>Who Uses FreeBSD?</title>
+      <title>½Ö¦b¥Î FreeBSD¡H</title>
 
       <indexterm>
 	<primary>users</primary>
 	<secondary>large sites running FreeBSD</secondary>
       </indexterm>
-
-      <para>FreeBSD is used to power some of the biggest sites on the
-        Internet, including:</para>
+      <para>³\¦h Internet ¤Wªº¤j«¬ºô¯¸³£¬O¥H FreeBSD §@¬°¥¦ªº§@·~¨t²Î¡A¨Ò¦p¡G</para>
 
       <itemizedlist>
         <indexterm><primary>Yahoo!</primary></indexterm>
         <listitem>
 	  <para><ulink url="http://www.yahoo.com/">Yahoo!</ulink></para>
 	</listitem>
 
 	<indexterm><primary>Apache</primary></indexterm>
 	<listitem>
 	  <para><ulink url="http://www.apache.org/">Apache</ulink></para>
 	</listitem>
 
 	<indexterm><primary>Blue Mountain Arts</primary></indexterm>
 	<listitem>
 	  <para><ulink url="http://www.bluemountain.com/">Blue Mountain
 	    Arts</ulink></para>
 	</listitem>
 
 	<indexterm><primary>Pair Networks</primary></indexterm>
 	<listitem>
 	  <para><ulink url="http://www.pair.com/">Pair
 	    Networks</ulink></para>
 	</listitem>
 
 	<indexterm><primary>Sony Japan</primary></indexterm>
 	<listitem>
 	  <para><ulink url="http://www.sony.co.jp/">Sony
 	    Japan</ulink></para>
 	</listitem>
 
 	<indexterm><primary>Netcraft</primary></indexterm>
 	<listitem>
 	  <para><ulink url="http://www.netcraft.com/">Netcraft</ulink>
 	    </para>
 	</listitem>
 
 	<indexterm><primary>Weathernews</primary></indexterm>
 	<listitem>
 	  <para><ulink url="http://www.wni.com/">Weathernews</ulink>
 	</para></listitem>
 
 	<indexterm><primary>Supervalu</primary></indexterm>
 	<listitem>
 	  <para><ulink
 	    url="http://www.supervalu.com/">Supervalu</ulink></para>
 	</listitem>
 
 	<indexterm><primary>TELEHOUSE America</primary></indexterm>
 	<listitem>
 	  <para><ulink url="http://www.telehouse.com/">TELEHOUSE
 	    America</ulink></para>
 	</listitem>
 
 	<indexterm><primary>Sophos Anti-Virus</primary></indexterm>
 	<listitem>
 	  <para><ulink url="http://www.sophos.com/">Sophos
 	    Anti-Virus</ulink></para>
 	</listitem>
 
 	<indexterm><primary>JMA Wired</primary></indexterm>
 	<listitem>
 	  <para><ulink
 	    url="http://www.jmawired.com/">JMA Wired</ulink></para>
 	</listitem>
       </itemizedlist>
 
-      <para>and many more.</para>
+      <para>¥H¤Î³\¦h¨ä¥Lªººô¯¸¡C</para>
     </sect2>
 
   </sect1>
   
   <sect1 id="history">
-    <title>About the FreeBSD Project</title>
+    <title>Ãö©ó FreeBSD ­p¹º</title>
 
-    <para>The following section provides some background information on
-      the project, including a brief history, project goals, and the
-      development model of the project.</para>
+    <para>±µ¤U¨ÓÁ¿ªº¬O FreeBSD ­p¹ºªº­I´º¡A¥]§t¾ú¥v²W·½ªºÂ²¤¶¡B­p¹ºªº¥Ø¼Ð¡A¥H¤Î¶}µoªº¼Ò¦¡¡C</para>
 
     <sect2 id="intro-history">
       <sect2info role="firstperson">
 	<authorgroup>
 	  <author>
 	    <firstname>Jordan</firstname>
 	    <surname>Hubbard</surname>
 	    <contrib>Contributed by </contrib>
 	  </author>
 	</authorgroup>
       </sect2info>
 
-      <title>A Brief History of FreeBSD</title>
+      <title>FreeBSD ¾ú¥v²W·½ªºÂ²¤¶</title>
 
       <indexterm><primary>386BSD Patchkit</primary></indexterm>
       <indexterm><primary>Hubbard, Jordan</primary></indexterm>
       <indexterm><primary>Williams, Nate</primary></indexterm>
       <indexterm><primary>Grimes, Rod</primary></indexterm>
       <indexterm>
         <primary>FreeBSD Project</primary>
         <secondary>history</secondary>
       </indexterm>
-      <para>The FreeBSD project had its genesis in the early part of 1993,
-	partially as an outgrowth of the <quote>Unofficial 386BSD
-        Patchkit</quote> by the patchkit's last 3 coordinators: Nate
-	Williams, Rod Grimes and myself.</para>
+      <para>FreeBSD ­pµeªº·Qªk¬O¦b 1993 ¦~ªì©Ò§Î¦¨ªº¡A
+	¨º¬O·½¦Û©óºûÅ@¤@²Õ ¡y«D©x¤è 386BSD ªº patchkit(­×¥¿¤u¨ã)¡z­p¹ºªº¤T­Ó¨ó½ÕºûÅ@¤H 
+	Nate Williams¡ARod Grimes ©M§Ú(Jordan Hubbard)¡C</para>
     
       <indexterm><primary>386BSD</primary></indexterm>
-      <para>Our original goal was to produce an intermediate snapshot of
-	386BSD in order to fix a number of problems with it that the
-	patchkit mechanism just was not capable of solving.  Some of you
-	may remember the early working title for the project being
-	<quote>386BSD 0.5</quote> or <quote>386BSD Interim</quote> in
-	reference to that fact.</para>
+      <para>§Ú­Ì³Ìªìªº¥Ø¼Ð¬O°µ¥X¤@¥÷ 386BSD ºî¦X­×¥¿ªº snapshot ª©¡A¥H«K­×¥¿·í®É¤@°ï
+	patchkit ³£¤£®e©ö¸Ñ¨Mªº°ÝÃD¡C¦³¨Ç¤H¥i¯àÁÙ°O±o¦­´Áªº­p¹º¦WºÙ¥s°µ 
+	<quote>386BSD 0.5</quote> ©Î <quote>386BSD Interim</quote> ´N¬O³o­Ó­ì¦]¡C</para>
     
       <indexterm><primary>Jolitz, Bill</primary></indexterm>
-      <para>386BSD was Bill Jolitz's operating system, which had been up
-	to that point suffering rather severely from almost a year's worth
-	of neglect.  As the patchkit swelled ever more uncomfortably with
-	each passing day, we were in unanimous agreement that something
-	had to be done and decided to assist Bill by providing
-	this interim <quote>cleanup</quote> snapshot.  Those plans came to
-	a rude halt when Bill Jolitz suddenly decided to withdraw his
-	sanction from the project without any clear indication of what
-	would be done instead.</para>
+      <para>386BSD ¬O Bill Jolitz ªº§@·~¨t²Î¡A¦b·í®É´N¤w¦³¬ù¤@¦~ªº¤Àµõ°Q½×¡C
+	·í¸Ó­×¥¿¤u¨ã (patchkit) ¤éº¥ÃeÂø±o¥O¤H¤£µÎªA¡A§Ú­ÌµL²§Ä³¦a¦P·N­n§@¤@¨Ç¨Æ¤F¡A
+ 	¨Ã¨M©w´£¨Ñ¤@¥÷Á{®É©Êªº <quote>²b¤Æª©(cleanup)</quote> ¨ÓÀ°§U Bill¡C
+ 	µM¦Ó¡A¥Ñ©ó Bill Jolitz ©¿µM¨M©w¨ú®ø¨ä¹ï¸Ó­p¹ºªº»{¥i¡A¥B¨S¦³©ú½T«ü¥X¥¼¨Óªº¥´ºâ¡A
+	©Ò¥H¸Ó­p¹º«K¬ðµM­±Á{Â_ª¤¦M¾÷¡C</para>
 
       <indexterm><primary>Greenman, David</primary></indexterm>
       <indexterm><primary>Walnut Creek CDROM</primary></indexterm>
-      <para>It did not take us long to decide that the goal remained
-	worthwhile, even without Bill's support, and so we adopted the
-	name <quote>FreeBSD</quote>, coined by David Greenman.  Our initial
-	objectives were set after consulting with the system's current
-	users and, once it became clear that the project was on the road
-	to perhaps even becoming a reality, I contacted Walnut Creek CDROM
-	with an eye toward improving FreeBSD's distribution channels for
-	those many unfortunates without easy access to the Internet.
-	Walnut Creek CDROM not only supported the idea of distributing
-	FreeBSD on CD but also went so far as to provide the project with a
-	machine to work on and a fast Internet connection.  Without Walnut
-	Creek CDROM's almost unprecedented degree of faith in what was, at
-	the time, a completely unknown project, it is quite unlikely that
-        FreeBSD would have gotten as far, as fast, as it has today.</para>
+      <para>¤£¤[§Ú­Ì«K¨M©w¦b§Y¨Ï¨S¦³ Bill ªº¤ä«ù¤U¡AÅý¸Ó­p¹º¤´µMÄ~Äò¤U¥h¡A
+	³Ì«á§Ú­Ì±Ä¥Î David Greenman ¥á»ÉªO¨M©wªº¦W¦r¡A¤]´N¬O¡yFreeBSD¡z¡C
+	¦b¸ß°Ý¤F·í®Éªº¤@¨Ç¨Ï¥ÎªÌ·N¨£¤§«á¡A´N¶}©l¨M©w¤F³Ìªìªº¥Ø¼Ð¡A
+	·í¸Ó­p¹º¶}©l¹ê¬I¤@¤Á´N­n¦¨¯u®É¡A¤@¤Á´NÅܱo§ó²M·¡¤F¡C
+	§Ú¸ò Walnut Creek CDROM °Q½×µo¦æ CDROM 
+	³o¼Ë¤l¤£«K¤Wºôªº¤H´N¥i¥H¥Î¤ñ¸û²³æªº¤è¦¡¨ú±o FreeBSD¡C
+	Walnut Creek CDROM ¤£¥uÃÙ¦¨¥H CDROM ¨Óµo¦æ FreeBSD 
+	ªº·Qªk¡A¦P®É´£¨Ñ¤F¤@¥x¾÷¾¹¥H¤Î§Ö³tªººô»Úºô¸ôªºÀW¼e¡C
+	¦pªG¤£¬O Walnut Creek CDROM ´X¥G¬OªÅ«eªº«H¥ô³o­Ó­è¶}©lÁÙ¬O§¹¥þÀqÀqµL»Dªº­p¹º¡A
+	¨º»ò«Ü¥i¯à FreeBSD ¤£·|¦p¦¹§Ö³tªº¦¨ªø¨ì¤µ¤é³o¼Ëªº³W¼Ò¡C</para>
 
       <indexterm><primary>4.3BSD-Lite</primary></indexterm>
       <indexterm><primary>Net/2</primary></indexterm>
       <indexterm><primary>U.C. Berkeley</primary></indexterm>
       <indexterm><primary>386BSD</primary></indexterm>
       <indexterm><primary>Free Software Foundation</primary></indexterm>
-      <para>The first CDROM (and general net-wide) distribution was
-	FreeBSD&nbsp;1.0, released in December of 1993.  This was based on the
-	4.3BSD-Lite (<quote>Net/2</quote>) tape from U.C. Berkeley, with
-	many components also provided by 386BSD and the Free Software
-	Foundation.  It was a fairly reasonable success for a first
-	offering, and we followed it with the highly successful FreeBSD
-	1.1 release in May of 1994.</para>
+      <para>²Ä¤@±i¥H CDROM (¤Îºô¸ô)µo¦æªº FreeBSD&nbsp;1.0 ¬O¦b 1993 ¦~¤Q¤G¤ë¡C
+        ¸Óª©¥»¬O°ò©ó¥Ñ U.C. Berkeley ¥HºÏ±a¤è¦¡µo¦æªº
+        4.3BSD-Lite (<quote>Net/2</quote>)¥H¤Î³\¦h¨Ó¦Û©ó 386BSD
+        ©M¦Û¥Ñ³nÅé°òª÷·|ªº³nÅé¡C¹ï©ó²Ä¤@¦¸µo¦æ¦Ó¨¥Áٺ⦨¥\¡A
+        §Ú­Ì¤S±µµÛ©ó 1994 ¦~ 5 ¤ëµo¦æ¤F¬Û·í¦¨¥\ªº FreeBSD 1.1¡C</para>
 
       <indexterm><primary>Novell</primary></indexterm>
       <indexterm><primary>U.C. Berkeley</primary></indexterm>
       <indexterm><primary>Net/2</primary></indexterm>
       <indexterm><primary>AT&amp;T</primary></indexterm>
-      <para>Around this time, some rather unexpected storm clouds formed
-	on the horizon as Novell and U.C. Berkeley settled their
-	long-running lawsuit over the legal status of the Berkeley Net/2
-	tape.  A condition of that settlement was U.C. Berkeley's
-	concession that large parts of Net/2 were <quote>encumbered</quote>
-	code and the property of Novell, who had in turn acquired it from
-	AT&amp;T some time previously.  What Berkeley got in return was
-	Novell's <quote>blessing</quote> that the 4.4BSD-Lite release, when
-	it was finally released, would be declared unencumbered and all
-	existing Net/2 users would be strongly encouraged to switch.  This
-	included FreeBSD, and the project was given until the end of July
-	1994 to stop shipping its own Net/2 based product.  Under the
-	terms of that agreement, the project was allowed one last release
-	before the deadline, that release being FreeBSD&nbsp;1.1.5.1.</para>
-
-      <para>FreeBSD then set about the arduous task of literally
-	re-inventing itself from a completely new and rather incomplete
-	set of 4.4BSD-Lite bits.  The <quote>Lite</quote> releases were
-	light in part because Berkeley's CSRG had removed large chunks of
-	code required for actually constructing a bootable running system
-	(due to various legal requirements) and the fact that the Intel
-	port of 4.4 was highly incomplete.  It took the project until
-	November of 1994 to make this transition, at which point it
-	released FreeBSD&nbsp;2.0 to the net and on CDROM (in late December).
-	Despite being still more than a little rough around the edges,
-	the release was a significant success and was followed by the
-	more robust and easier to install FreeBSD&nbsp;2.0.5 release in June of
-	1995.</para>
-
-      <para>We released FreeBSD&nbsp;2.1.5 in August of 1996, and it appeared
-	to be popular enough among the ISP and commercial communities that
-	another release along the 2.1-STABLE branch was merited.  This was
-	FreeBSD&nbsp;2.1.7.1, released in February 1997 and capping the end of
-	mainstream development on 2.1-STABLE.  Now in maintenance mode,
-	only security enhancements and other critical bug fixes will be
-	done on this branch (RELENG_2_1_0).</para>
-
-      <para>FreeBSD&nbsp;2.2 was branched from the development mainline
-	(<quote>-CURRENT</quote>) in November 1996 as the RELENG_2_2
-	branch, and the first full release (2.2.1) was released in April
-	1997.  Further releases along the 2.2 branch were done in the
-	summer and fall of '97, the last of which (2.2.8) appeared in
-	November 1998. The first official 3.0 release appeared in
-	October 1998 and spelled the beginning of the end for the 2.2
-	branch.</para>
-
-      <para>The tree branched again on Jan 20, 1999, leading to the
-	4.0-CURRENT and 3.X-STABLE branches.  From 3.X-STABLE, 3.1 was
-	released on February 15, 1999, 3.2 on May 15, 1999, 3.3 on
-	September 16, 1999, 3.4 on December 20, 1999, and 3.5 on
-	June 24, 2000, which was followed a few days later by a minor
-	point release update to 3.5.1, to incorporate some last-minute
-	security fixes to Kerberos. This will be the final release in the
-	3.X branch.</para>
-
-      <para>There was another branch on March 13, 2000, which saw the
-	emergence of the 4.X-STABLE branch.  There have been several releases
-	from it so far: 4.0-RELEASE was introduced in March 2000, and
-	the last &rel2.current;-RELEASE came out in
-	&rel2.current.date;.</para>
-
-      <para>The long-awaited 5.0-RELEASE was announced on January 19,
-      2003.  The culmination of nearly three years of work, this
-      release started FreeBSD on the path of advanced multiprocessor
-      and application thread support and introduced support for the
-      &ultrasparc; and <literal>ia64</literal> platforms.  This release
-      was followed by 5.1 in June of 2003.  The last 5.X release from
-      -CURRENT branch was 5.2.1-RELEASE, introduced in February 2004.</para>
-
-      <para>RELENG_5 branch created in August 2004, followed by 5.3-RELEASE,
-	that marks beginning of the 5-STABLE branch releases.  The most
-	recent &rel.current;-RELEASE came out in &rel.current.date;.
-	There will be additional releases from the RELENG_5 branch.</para>
-
-      <para>For now, long-term development projects continue to take place in the
-	6.X-CURRENT (trunk) branch, and SNAPshot releases of 6.X on
-	CDROM (and, of course, on the net) are continually made available
-	from <ulink url="ftp://current.FreeBSD.org/pub/FreeBSD/snapshots/">
-	the snapshot server</ulink> as work progresses.</para>
+      <para>µM¦Ó¦¹«á¤£¤[¡A¥t¤@­Ó·N¥~ªº­·¼É¦b Novell ©M U.C. Berkeley Ãö©ó
+	Berkeley Net/2 ºÏ±a¤§ªk«ß¦a¦ìªº¶D³^½T©w¤§«á§Î¦¨¡C
+	U.C. Berkeley ±µ¨ü¤j³¡¥÷ªº Net/2 ªºµ{¦¡½X³£¬O¡y«I¦û¨Óªº¡z¥B¬OÄÝ©ó Novell ªº°]²£
+	-- ¨Æ¹ê¤W¬O·í®É¤£¤[«e±q AT&amp;T ¨ú±oªº¡C
+	Berkeley ±o¨ìªº¬O Novell ¹ï©ó 4.4BSD-Lite ªº¡y¯¬ºÖ¡z¡A³Ì«á·í 4.4BSD-Lite 
+	²×©óµo¦æ¤§«á¡A«K¤£¦A¬O«I¦û¦æ¬°¡C
+	¦Ó©Ò¦³²{¦³ Net/2 ¨Ï¥ÎªÌ³£³Q±j¯P«Øij§ó´«·sª©¥»¡A³o¥]¬A¤F FreeBSD¡C
+	©ó¬O¡A§Ú­Ì³Q­n¨D©ó 1994 ¦~ 6 ¤ë©³«e°±¤î´²§G°ò©ó Net/2 
+	ªº²£«~¡C¦b¦¹«e´£¤§¤U¡A¥»­p¹º³Q¤¹³\¦b´Á­­¥H«e§@³Ì«á¤@¦¸µo¦æ¡A¤]´N¬O 
+	FreeBSD&nbsp;1.1.5.1¡C</para>
+
+      <para>FreeBSD «K¶}©l¤F³o©{¦p¡y­«·sµo©ú½ü¤l¡zªºÁ}¹d¤u§@ -- ±q¥þ·sªº¥B¤£§¹¾ãªº 
+	4.4BSD-Lite ­«·s¾ã¦X¡C
+	³o­Ó <quote>Lite</quote> ª©¥»¬O¤£§¹¾ãªº¡A¦]¬°
+	Berkeley ªº CSRG  ¤w¸g§R°£¤F¤j¶q¦b«Ø¥ß¤@­Ó¥i¥H¶}¾÷°õ¦æªº¨t²Î©Ò»Ý­nªºµ{¦¡½X
+        (°ò©ó­Y¤zªk«ß¤Wªº­n¨D)¡A¥B¸Óª©¥»¦b Intel ¥­¥xªº²¾´Ó¬O«D±`¤£§¹¾ãªº¡C
+        ª½¨ì 1994 ¦~ 11 ¤ë¥»­p¹º¤~§¹¦¨¤F³o­ÓÂಾ¡A
+        ¦P®É¦b¸Ó¦~ 12 ¤ë©³¥H CDROM ¥H¤Îºô¸ôªº§Î¦¡µo¦æ¤F FreeBSD&nbsp;2.0¡C
+        ÁöµM¸Ó¥÷ª©¥»¦b·í®É¦³ÂI¥^«P²ÊÁW¡A¦ý¤´¬O´I¦³·N¸qªº¦¨¥\¡C
+        ÀH¤§©ó 1995 ¦~ 6 ¤ë¤Sµo¦æ¤F§ó®e©ö¦w¸Ë¡A§ó¦nªº FreeBSD&nbsp;2.0.5¡C</para>
+
+      <para>§Ú­Ì¦b 1996 ¦~ 8 ¤ëµo¦æ¤F FreeBSD&nbsp;2.1.5¡A¦b ISP ©M°Ó·~¹ÎÅ餤«D±`¬y¦æ¡C
+	ÀH«á¡A 2.1-STABLE ¤À¤äªº¥t¤@­Óª©¥»À³¹B¦Ó¥Í¡A¥¦´N¬O¦b 1997 ¦~ 2 ¤ëµo¦æ FreeBSD 2.1.7.1
+	¡A¦P®É¤]¬O 2.1-STABLE ¤À¤äªº³Ì«áª©¡C¤§«á¦¹¤À¤ä«K¶i¤JºûÅ@ª¬ºA¡A
+	¶È¶È´£¨Ñ¦w¥þ©Êªº¥[±j©M¨ä¥LÄY­«¿ù»~­×¸ÉªººûÅ@(RELENG_2_1_0)¡C</para>
+
+      <para>1996 ¦~ 11 ¤ë FreeBSD&nbsp;2.2 ±q¶}µo¥D¶b¤À¤ä (<quote>-CURRENT</quote>)
+	¥X¨Ó¦¨¬° RELENG_2_2 ¤À¤ä¡C¥¦ªº²Ä¤@­Ó§¹¾ãª©(2.2.1)©ó 1997 ¦~ 4 ¤ëµo¦æ¡C
+	2.2 ¤À¤äªº©µÄòª©¥»¦b 97 ¦~®L¬î¤§¶¡µo¦æªº¡A¨ä³Ì«áª©¬O¦b 1998 ¦~ 11 ¤ëµo¦æªº 2.2.8 ª©¡C
+	²Ä¤@­Ó¥¿¦¡ªº 3.0 ª©¥»¦b 1998 ¦~ 10 ¤ëµo¦æ¡A¥ç§Y«Å§i 2.2 ¤À¤äªº¸¨¹õ¡C</para>
+
+      <para>1999/01/20 ¤é¦A«×¤À¤ä¡A³o²£¥Í¤F 4.0-CURRENT ¥H¤Î 3.X-STABLE ¨â­Ó¤À¤ä¡C
+	3.X-STABLE ¤è­±¡A3.1 µo¦æ©ó 1999/02/15¡A3.2 µo¦æ©ó1999/05/15¡A3.3 µo¦æ©ó 1999/09/16¡A
+	3.4 µo¦æ©ó 1999/12/20¡A3.5 µo¦æ©ó 2000/06/24
+	¡A±µ¤U¨Ó´X¤Ñ«áµo§G¤F¤@¨Çªº­×¸ÉÀÉ(¹ï Kerberos ¦w¥þ©Ê¤è­±ªº­×¥¿)¡A´N¤É¯Å¦Ü 3.5.1
+	¡A³o¬O 3.X ¤À¤ä³Ì«á¤@­Óµo¦æª©¥»¡C</para>
+
+      <para>¦b 2000/03/13 ¤S¦³¤F¤@­Ó·sªº¤À¤ä¡A ¤]´N¬O 4.X-STABLE
+	¡C³o­Ó¤À¤ä¤§«áµo§G¤F³\¦hªºµo¦æª©¥»¡J 4.0-RELEASE ¦b 2000 ¦~ 3 ¤ëµo¦æ¡A
+	¦Ó³Ì«áªº 4.11-RELEASE «h¦b 2005 ¦~ 1 ¤ëµo¦æ¡C4-STABLE ¤À¤äªº¤ä´©·|«ùÄò¨ì 2007/01/31
+	¡A¦ý¥D­nµJÂI¦b©ó¦w¥þ¤è­±ªºº|¬}¡B¯äÂΤΨä¥LÄY­«°ÝÃDªº­×¸É¡C</para>
+
+      <para>´Á«Ý¤w¤[ªº 5.0-RELEASE ¦b 2003/01/19 ¥¿¦¡µo¦æ¡C³o¬O±Nªñ¶}µo¤T¦~ªºÅq®p¤§§@¡A¦P®É
+	¤]¶}©l¥[±j¦hÁûCPU(SMPng)ªº¤ä´©¡Bkernel thread(KSE) ªº¤ä´©¡BÀɮרt²Î±Ä¥Î UFS2 ¥H¤Î¤ä´© snapshot 
+	µ¥¡A ¨Ã¤ä´© &ultrasparc; ©M
+	 <literal>ia64</literal> ¥­¥x¡B¤ä´©ÂŪޡB32 bit ªº PCMCIA µ¥¡C¤§«á©ó 2003 ¦~ 6 ¤ëµo¦æ¤F 5.1¡C
+	¦Ó -CURRENT ³o­Óµo®i¥D¶b¤À¤äªº³Ì«á  5.X ª©¥»¬O¦b 2004 ¦~ 2 ¤ë¥¿¦¡µo¦æªº 5.2.1-RELEASE¡A¦b 5.X
+	¨t¦C¶i¤J -STABLE (RELENG_5¤À¤ä)¤§«á¡A-CURRENT ´NÂಾ¬° 6.X ¨t¦C¡C</para>
+
+      <para>RELENG_5 ¤À¤ä©ó 2004 ¦~ 8 ¤ë¥¿¦¡¶}¶]¡A¤§«á¬O 5.3-RELEASE
+	¡A¥¦¬O 5-STABLE ¤À¤äªº²Ä¤@­Óµo¦æª©¥»¡C5-STABLE ªº³Ì·sµoªí¬O¦b &rel2.current.date; µo¦æªº &rel2.current;-RELEASE¡A·íµMÅo¡ARELENG_5 ¤À¤äÁÙ±N¦³«áÄòªºµo¦æª©¡C</para>
+
+<!-- chinsan: 6.X ªº¯S¦â¤¶²Ð³¡¥÷µ¥ Offical Handbook ¥X¨Ó·sª©¦A½Ķ§a XD -->
+      <para>RELENG_6 ¤À¤ä©ó 2005 ¦~ 11 ¤ë¶}¶]¡A³Ì·sªº &rel.current;-RELEASE ¬O¦b &rel.current.date; µo¦æ¡C</para>
+
+      <para>¥Ø«e¡Aªø´Áªº¶}µo­pµeÄ~Äò¦b 7.X-CURRENT (trunk) ¤À¤ä¤¤¶i¦æ¡A¦Ó 7.X ªº CDROM 
+	(·íµM¡A¤]¥i¥H¥Îºô¸ô§ì) snapshot ª©¥»¥i¥H¦b <ulink 
+	url="ftp://current.FreeBSD.org/pub/FreeBSD/snapshots/">FreeBSD snapshot server</ulink>
+	 ¨ú±o¡C</para>
     </sect2>
       
     <sect2 id="goals">
       <sect2info>
         <authorgroup>
           <author>
             <firstname>Jordan</firstname>
 	    <surname>Hubbard</surname>
    	    <contrib>Contributed by </contrib>
 	  </author>
         </authorgroup>
       </sect2info>
 
-      <title>FreeBSD Project Goals</title>
+      <title>FreeBSD ­p¹ºªº¥Ø¼Ð</title>
     
       <indexterm>
         <primary>FreeBSD Project</primary>
         <secondary>goals</secondary>
       </indexterm>
-      <para>The goals of the FreeBSD Project are to provide software that
-	may be used for any purpose and without strings attached.  Many of
-	us have a significant investment in the code (and project) and
-	would certainly not mind a little financial compensation now and
-	then, but we are definitely not prepared to insist on it.  We
-	believe that our first and foremost <quote>mission</quote> is to
-	provide code to any and all comers, and for whatever purpose, so
-	that the code gets the widest possible use and provides the widest
-	possible benefit.  This is, I believe, one of the most fundamental
-	goals of Free Software and one that we enthusiastically
-	support.</para>
+      <para>FreeBSD ­p¹ºªº¥Ø¼Ð¦b©ó´£¨Ñ¥i§@¥ô·N¥Î³~ªº³nÅé¦Ó¤£ªþ±a¥ô¦ó­­¨î±ø¤å¡C
+	§Ú­Ì¤§¤¤³\¦h¤H¹ïµ{¦¡½X (¥H¤Î­pµe¥»¨­) ³£¦³«D±`¤jªº§ë¤J¡A 
+	¦]¦¹¡A·íµM¤£¤¶·N°¸º¸¦³¤@¨Ç¸êª÷¤Wªº¸ÉÀv¡A¦ý§Ú­Ì¨Ã¨S¥´ºâ°í¨M¦a­n¨D±o¨ì³oÃþ¸ê§U¡C
+	§Ú­Ì»{¬°§Ú­Ìªº­º­n¡y¨Ï©R(mission)¡z¬O¬°¥ô¦ó¤H´£¨Ñµ{¦¡½X¡A
+	¤£ºÞ¥L­Ì¥´ºâ¥Î³o¨Çµ{¦¡½X°µ¤°»ò¡A ¦]¬°³o¼Ëµ{¦¡½X±N¯à°÷³Q§ó¼sªx¦a¨Ï¥Î¡A±q¦Óµo´§¨ä»ù­È¡C
+	§Ú»{¬°³o¬O¦Û¥Ñ³nÅé³Ì°ò¥»ªº¡A¦P®É¤]¬O§Ú­Ì©Ò­Ò¾Éªº¤@­Ó¥Ø¼Ð¡C</para>
 
       <indexterm>
         <primary>GNU General Public License (GPL)</primary>
       </indexterm>
       <indexterm>
         <primary>GNU Lesser General Public License (LGPL)</primary>
       </indexterm>
       <indexterm><primary>BSD Copyright</primary></indexterm>
-      <para>That code in our source tree which falls under the GNU
-        General Public License (GPL) or Library General Public License
-        (LGPL) comes with slightly more strings attached, though at
-        least on the side of enforced access rather than the usual
-        opposite.  Due to the additional complexities that can evolve
-        in the commercial use of GPL software we do, however, prefer
-        software submitted under the more relaxed BSD copyright when
-        it is a reasonable option to do so.</para>
+      <para>§Ú­Ìµ{¦¡½X¾ð¤¤¡A¦³­Y¤z¬O¥H GNU GPL ©ÎªÌ LGPL
+	µo§Gªº¨º¨Çµ{¦¡½X±a¦³¤Ö³\ªºªþ¥[­­¨î¡AÁÙ¦n¥u¬O±j¨î©Êªº­n¨D¶}©ñµ{¦¡½X¦Ó¤£¬O§Oªº¡C
+	¥Ñ©ó¨Ï¥Î GPL ªº³nÅé¦b°Ó·~¥Î³~¤W·|¼W¥[­Y¤z½ÆÂø©Ê¡A¦]¦¹¡A¦pªG¥i¥H¿ï¾Üªº¸Ü¡A
+	§Ú­Ì·|¤ñ¸û³ßÅw¨Ï¥Î­­¨î¬Û¹ï§ó¼eÃPªº BSD ª©Åv¨Óµo§G³nÅé¡C</para>
     </sect2>
   
     <sect2 id="development">
       <sect2info>
         <authorgroup>
           <author>
             <firstname>Satoshi</firstname>
 	    <surname>Asami</surname>
    	    <contrib>Contributed by </contrib>
 	  </author>
         </authorgroup>
       </sect2info>
 
-      <title>The FreeBSD Development Model</title>
+      <title>FreeBSD ªº¶}µo¼Ò¦¡</title>
     
       <indexterm>
         <primary>FreeBSD Project</primary>
         <secondary>development model</secondary>
       </indexterm>
-      <para>The development of FreeBSD is a very open and flexible
-	process, being literally built from the contributions
-	of hundreds of people around the world, as can be seen from
-	our <ulink
-	url="&url.articles.contributors;/article.html">list of
-	contributors</ulink>.  FreeBSD's development infrastructure allow
-	these hundreds of developers to collaborate over the Internet.
-	We are constantly on the lookout for
-	new developers and ideas, and those interested in becoming
-	more closely involved with the project need simply contact us
-	at the &a.hackers;.  The &a.announce; is also available to
-	those wishing to make other FreeBSD users aware of major areas
-	of work.</para>
-
-      <para>Useful things to know about the FreeBSD project and its
-	development process, whether working independently or in close
-	cooperation:</para>
+      <para>FreeBSD ªº¶}µo¬O¤@­Ó«D±`¶}©ñ¥B¨ã¼u©Êªº¹Lµ{¡A´N¹³±q <ulink
+	url="&url.articles.contributors;/article.html">°^ÄmªÌ¦W³æ</ulink>
+	©Ò¬Ý¨ìªº¡A¬O¥Ñ¥þ¥@¬É¤W¤d¤W¸Uªº°^ÄmªÌµo®i°_¨Óªº¡C
+	FreeBSD ªº¶}µo°ò¦¬[ºc¤¹³\¼Æ¥H¦Ê­pªº¶}µoªÌ³z¹Lºô»Úºô¸ô¨ó¦P¤u§@¡C
+	§Ú­Ì¤]¸g±`Ãöª`µÛ¨º¨Ç¹ï§Ú­Ìªº­pµe·P¿³½ìªº·s¶}µoªÌ©M·sªº³Ð·N¡A
+	¨º¨Ç¦³¿³½ì§ó¶i¤@¨B°Ñ»P­p¹ºªº¤H¥u»Ý­n¦b &a.hackers; ³sô§Ú­Ì¡C
+	&a.announce; ¹ï¨º¨Ç§Æ±æ¤F¸Ñ§Ú­Ì¶i«×ªº¤H¤]¬O¬Û·í¦³¥Îªº¡C</para>
+
+      <para>µL½×¬O³æ¿W¶}µoªÌ©ÎªÌ«Ê³¬¦¡ªº¹Î¶¤¦X§@¡A­Y¯à¤F¸Ñ FreeBSD ­p¹º©M¥¦ªº¶}µo¹Lµ{³£¬O¦³¥Îªº¡J</para>
 
       <variablelist>
 	<varlistentry>
 	  <term>The CVS repository<anchor
 	    id="development-cvs-repository"></term>
 
 	  <indexterm>
       <primary>CVS</primary>
       <secondary>repository</secondary>
     </indexterm>
 	  <indexterm>
 	    <primary>Concurrent Versions System</primary>
       <see>CVS</see>
 	  </indexterm>
 	  <listitem>
 	    <para>The central source tree for FreeBSD is maintained by
 	      <ulink url="http://www.cvshome.org/">CVS</ulink>
 	      (Concurrent Versions System), a freely available source code
 	      control tool that comes bundled with FreeBSD.  The primary
 	      <ulink url="http://www.FreeBSD.org/cgi/cvsweb.cgi">CVS
 	      repository</ulink> resides on a machine in Santa Clara CA, USA
 	      from where it is replicated to numerous mirror machines
 	      throughout the world.  The CVS tree, which contains the <link
 	      linkend="current">-CURRENT</link> and <link
 	      linkend="stable">-STABLE</link> trees,
 	      can all be easily replicated to your own machine as well.
 	      Please refer to the <link linkend="synching">Synchronizing
 	      your source tree</link> section for more information on
 	      doing this.</para>
 	  </listitem>
 	</varlistentry>
       
 	<varlistentry>
 	  <term>The committers list<anchor
 	    id="development-committers"></term>
 	      
 	  <indexterm><primary>committers</primary></indexterm>
 	  <listitem>
 	    <para>The <firstterm>committers</firstterm>
 	      are the people who have <emphasis>write</emphasis> access to
 	      the CVS tree, and are authorized to make modifications
 	      to the FreeBSD source (the term <quote>committer</quote>
 	      comes from the &man.cvs.1; <command>commit</command>
 	      command, which is used to bring new changes into the CVS
 	      repository).  The best way of making submissions for review
 	      by the committers list is to use the &man.send-pr.1;
 	      command. If something appears to be jammed in the
 	      system, then you may also reach them by sending mail to
 	      the &a.committers;.</para>
 	  </listitem>
 	</varlistentry>
       
 	<varlistentry>
 	  <term>The FreeBSD core team<anchor id="development-core"></term>
 
 	  <indexterm><primary>core team</primary></indexterm>
 	  <listitem>
-	    <para>The <firstterm>FreeBSD core team</firstterm>
-	      would be equivalent to the board of directors if the FreeBSD
-	      Project were a company.  The primary task of the core team
-	      is to make sure the project, as a whole, is in good shape
-	      and is heading in the right directions.  Inviting dedicated
-	      and responsible developers to join our group of committers
-	      is one of the functions of the core team, as is the
-	      recruitment of new core team members as others move on.
-	      The current core team was elected from a pool of committer
-	      candidates in July 2004.  Elections are held every 2 years.
-	      </para>
+	    <para><firstterm>FreeBSD core team</firstterm>
+	      ´Nµ¥©ó¸³¨Æ·| -- ¦pªG§â FreeBSD ¬Ý¦¨¬O¤@®a¤½¥qªº¸Ü¡C
+	      core team ªº¥D­n¾³d¦b©ó½T«O¦¹­p¹º¦³¨}¦nªº¬[ºc¡A¥H´ÂµÛ¥¿½Tªº¤è¦Vµo®i¡C
+              ¦¹¥~¡AÁܽмö¦å¥B­t³dªº³nÅé¶}µoªÌ¥[¤J committers ¦æ¦C¡A¥H¦b­Y¤z¦¨­ûÂ÷¥h®É±o¥H¸É¥R·s¦å¡C
+              ¥Ø«eªº core team ¬O¦b 2004 ¦~ 6 ¤ë committers ­Ô¿ï¤H¤¤¿ï¥X¨Óªº¡A¨C¨â¦~·|Á|¿ì¤@¦¸¿ïÁ|</para>
 
 	    <para>Some core team members also have specific areas of
 	      responsibility, meaning that they are committed to
 	      ensuring that some large portion of the system works as
 	      advertised.  For a complete list of FreeBSD developers
 	      and their areas of responsibility, please see the <ulink
 	      url="&url.articles.contributors;/article.html">Contributors
 	      List</ulink></para>
 
 	    <note>
 	      <para>Most members of the core team are volunteers when it
 	        comes to FreeBSD development and do not benefit from the
 		project financially, so <quote>commitment</quote> should
 		also not be misconstrued as meaning <quote>guaranteed
 		support.</quote>  The <quote>board of directors</quote>
 		analogy above is not very accurate, and it may be
 		more suitable to say that these are the people who gave up
 		their lives in favor of FreeBSD against their better
 		judgment!</para>
 	    </note>
 	  </listitem>
 	</varlistentry>
       
 	<varlistentry>
 	  <term>Outside contributors</term>
 
 	  <indexterm><primary>contributors</primary></indexterm>
 	  <listitem>
 	    <para>Last, but definitely not least, the largest group of
 	      developers are the users themselves who provide feedback and
 	      bug fixes to us on an almost constant basis.  The primary
 	      way of keeping in touch with FreeBSD's more non-centralized
 	      development is to subscribe to the &a.hackers; where such
               things are discussed.  See <xref
               linkend="eresources"> for more information about
               the various FreeBSD mailing lists.</para>
 	  
 	    <para><citetitle><ulink
 	      url="&url.articles.contributors;/article.html">The
 	      FreeBSD Contributors List</ulink></citetitle> is a long
 	      and growing one, so why not join it by contributing
 	      something back to FreeBSD today?</para>
 
 	    <para>Providing code is not the only way of contributing to
 	      the project; for a more complete list of things that need
 	      doing, please refer to the <ulink
 	      url="&url.base;/index.html">FreeBSD Project web
 	      site</ulink>.</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
     
       <para>In summary, our development model is organized as a loose set
         of concentric circles.  The centralized model is designed for the
         convenience of the <emphasis>users</emphasis> of FreeBSD, who are
         provided with an easy way of tracking one central code
 	base, not to keep potential contributors out! Our desire is to
 	present a stable operating system with a large set of coherent
 	<link linkend="ports">application programs</link> that the users
 	can easily install and use &mdash; this model works very well in
 	accomplishing that.</para>
     
       <para>All we ask of those who would join us as FreeBSD developers is
         some of the same dedication its current people have to its
 	continued success!</para>
     </sect2>
 
     <sect2 id="relnotes">
-      <title>The Current FreeBSD Release</title>
+      <title>³Ì·sªº FreeBSD µo¦æª©¥»</title>
 
       <indexterm><primary>NetBSD</primary></indexterm>
       <indexterm><primary>OpenBSD</primary></indexterm>
       <indexterm><primary>386BSD</primary></indexterm>
       <indexterm><primary>Free Software Foundation</primary></indexterm>
       <indexterm><primary>U.C. Berkeley</primary></indexterm>
       <indexterm>
         <primary>Computer Systems Research Group (CSRG)</primary>
       </indexterm>
-      <para>FreeBSD is a freely available, full source 4.4BSD-Lite based
-        release for Intel &i386;, &i486;, &pentium;,
+      <para>FreeBSD ¬O§K¶O¨Ï¥Î¥B±a¦³§¹¾ã­ì©lµ{¦¡½Xªº¥H 4.4BSD-Lite ¬°°ò¦ªº¨t²Î¡A¥i¥H¦b
+	Intel &i386;, &i486;, &pentium;,
         &pentium;&nbsp;Pro,
         &celeron;,
         &pentium;&nbsp;II,
         &pentium;&nbsp;III,
-        &pentium;&nbsp;4 (or compatible),
+        &pentium;&nbsp;4 (©ÎªÌ¬Û®e«¬¸¹),
         &xeon;, DEC <trademark>Alpha</trademark>
-        and Sun &ultrasparc; based computer
-        systems.  It is based primarily on software from U.C. Berkeley's
-        CSRG group, with some enhancements from NetBSD, OpenBSD, 386BSD, and
-        the Free Software Foundation.</para>
+ 	©M Sun &ultrasparc; ¬°°ò¦ªº¹q¸£¤W°õ¦æªº§@·~¨t²Î¡C
+	¥¦¥D­n¥H¥[¦{¤j¾Ç¤Úº¸§J§Q¤À®Õ ªº CSRG ¬ã¨s¤p²Õªº³nÅ鬰°ò¦¡A¨Ã¥[¤J¤F 
+	NetBSD¡BOpenBSD¡B386BSD ¥H¤Î¦Û¥Ñ³nÅé°òª÷·|ªº¤@¨ÇªF¦è¡C</para>
 
-      <para>Since our release of FreeBSD&nbsp;2.0 in late 94, the performance,
-        feature set, and stability of FreeBSD has improved dramatically.
+      <para>¦Û±q 1994 ¦~¥½¡A§Ú­Ìµo§G¤F FreeBSD&nbsp;2.0 ¤§«á¡A¨t²Îªº°õ¦æ®Ä²v¡B
+        ¥\¯à¡Bí©w©Ê³£¦³¤F¥O¤Hª`¥Øªº´£¤É¡C
 	<!-- XXX is the rest of this paragraph still true ? -->
-        The largest change is a revamped virtual memory system with a merged
-        VM/file buffer cache that not only increases performance, but also
-        reduces FreeBSD's memory footprint, making a 5&nbsp;MB configuration a
-        more acceptable minimum.  Other enhancements include full NIS client
-        and server support, transaction TCP support, dial-on-demand PPP,
-        integrated DHCP support, an improved SCSI subsystem, ISDN support,
-        support for ATM, FDDI, Fast and Gigabit Ethernet (1000&nbsp;Mbit)
-        adapters, improved support for the latest Adaptec controllers, and
-        many thousands of bug fixes.</para>
-
-      <para>In addition to the base distributions, FreeBSD offers a
-        ported software collection with thousands of commonly
-        sought-after programs.  At the time of this printing, there
-        were over &os.numports; ports!  The list of ports ranges from
-        http (WWW) servers, to games, languages, editors, and almost
-        everything in between.  The entire Ports Collection requires
-        approximately &ports.size; of storage, all ports being expressed as
-        <quote>deltas</quote> to their original sources.  This makes
-        it much easier for us to update ports, and greatly reduces the
-        disk space demands made by the older 1.0 Ports Collection.  To
-        compile a port, you simply change to the directory of the
-        program you wish to install, type <command>make
-        install</command>, and let the system do the rest.  The full
-        original distribution for each port you build is retrieved
-        dynamically off the CDROM or a local FTP site, so you need
-        only enough disk space to build the ports you want.  Almost
-        every port is also provided as a pre-compiled
-        <quote>package</quote>, which can be installed with a simple
-        command (<command>pkg_add</command>) by those who do not wish
-        to compile their own ports from source.  More information on
-	packages and ports can be found in <xref linkend="ports">.</para>
-
-      <para>A number of additional documents which you may find very helpful
-        in the process of installing and using FreeBSD may now also be found
-        in the <filename>/usr/share/doc</filename> directory on any recent
-        FreeBSD machine.  You may view the locally installed
-        manuals with any HTML capable browser using the following
-        URLs:</para>
+        ³Ì¤jªº§ïÅÜ´N¬O§Ú­Ì±N°O¾ÐÅé»PÀɮרt²Îªº cache ¾÷¨îµ²¦X¦b¤@°_¡C
+        ³o¤£¥u¨Ï±o¨t²Îªºªí²{Åܱo§ó¦n, ¨Ã¥B¨Ï±o FreeBSD
+        ¨t²Î³Ì¤Öªº°O¾ÐÅé»Ý¨D´î¤Ö¨ì 5&nbsp;MB¡C
+        ¨ä¥¦ªº§ï¶i¥]¬A§¹¾ãªº NIS cilent and server ¥\¯à¤ä´©¡A
+        ¤ä´© transaction TCP¡BPPP ¼·±µ³s½u¡B¾ã¦Xªº DHCP ¤ä´©¡B
+        SCSI ¤l¨t²Îªº§ï¶i¡BISDN ªº¤ä´©¡AATM¡BFDDI ¥H¤Î¤A¤Óºô¸ô (Ethernet¡B¥]¬A
+        100&nbsp;Mbit ©M Gigabit) ªº¤ä´©¡A´£¤É¤F³Ì·sªº Adaptec 
+	±±¨î¥dÅX°Êµ{¦¡ªº§ïµ½¡A¥H¤Î¼Æ¥H¤d­pªº bug ­×¥¿¡C</para>
+
+      <para>°£¤F³Ì°ò¥»ªº¨t²Î³nÅé¡AFreeBSD ÁÙ´£¨Ñ¤F¼s¨üÅwªïªº®M¥ó³nÅéºÞ²z¾÷¨î¡G Ports Collection¡C
+	¨ì¥»®Ñ¥I¦L®É¡A¤w¦³¶W¹L &os.numports; ­Ó ports¡A¨ä¤¤½dÃ¥¥]¬A±q http(WWW) 
+	¦øªA¾¹¨ì¹CÀ¸¡Bµ{¦¡»y¨¥¡B½s¿è¾¹¥H¤Î±z¯à·Q¨ìªº´X¥G©Ò¦³ªºªF¦è¡C
+	§¹¾ãªº Ports Collection »Ý­n¬ù &ports.size; ªºµwºÐªÅ¶¡¡A°£¤F 
+	port °ò¥»¬[ºcÀÉ®×¥~¡A³£¥uÀx¦s»P¸Ó port ³nÅ骺­ì©l½X¦³¡y¶·­nÅܧó¡zªº³¡¥÷¡C
+	¦p¦¹¤@¨Ó¡A§Ú­Ì¥i¥H§ó®e©ö§ó·s³o¨Ç ports¡A
+	¤]¤j¶qªº´î¤Ö¦pªº 1.0 ª© Ports Collection ¹ï©óµwºÐªÅ¶¡ªº»Ý¨D¡C
+	­n¦w¸Ë¤@­Ó port ªº¸Ü¡A¥u»Ý­n¶i¤J¸Ó port ªº¥Ø¿ý¡A¿é¤J <command>make install</command>
+	¡A³o¼Ë¤l¨t²Î´N·|À°§A¸Ë¦n¤F¡C±z­n½sĶªº¨C­Óµ{¦¡ªº§¹¾ã­ì©lµ{¦¡¡A
+	³£¥i±q FTP ©Î CDROM ¤¤Àò±o¡A©Ò¥H±z¥u»Ý·Ç³Æ¨¬°÷ªºµwºÐªÅ¶¡¨Ó½sĶ§A­nªº port ³nÅé¡C
+	´X¥G¨C¤@­Ó port ³£¦³¤w¨Æ¥ý½sĶ¦nªº <quote>package</quote>¥H¤è«K¦w¸Ë¡A
+	¦pªG¤£·Q±q½sĶ port ªº¤H¡A¥u­n¥Î­Ó²³æ«ü¥O(<command>pkg_add</command>)´N¥i¥H¦w¸Ë¡C
+	¦³Ãö packages ©M ports ªº²Ó¸`¡A¥i¥H°Ñ¾\ <xref linkend="ports">¡C</para>
+
+      <para>FreeBSD ¥D¾÷ªº <filename>/usr/share/doc</filename> ¥Ø¿ý¤U§ä¨ì³\¦h¦³¥Îªº¤å¥ó¡A
+	¨ÓÀ°§U±z¦w¸Ë¡B¨Ï¥Î FreeBSD¡C¤]¥i¥H¨Ï¥Î¤U­±ªººô§}¡A¥HÂsÄý¾¹¨Ó½¾\¥»¾÷¤W¦w¸Ëªº¤â¥U¡J</para>
 
       <variablelist>
         <varlistentry>
-	  <term>The FreeBSD Handbook</term>
+	  <term>FreeBSD ¨Ï¥Î¤â¥U</term>
 
 	  <listitem>
 	    <para><ulink type="html"
 	      url="file://localhost/usr/share/doc/handbook/index.html"><filename>/usr/share/doc/handbook/index.html</filename></ulink></para>
 	  </listitem>
         </varlistentry>
       
         <varlistentry>
-	  <term>The FreeBSD FAQ</term>
+	  <term>FreeBSD ±`¨£°Ýµª¶°</term>
 
 	  <listitem>
 	    <para><ulink type="html"
 	      url="file://localhost/usr/share/doc/faq/index.html"><filename>/usr/share/doc/faq/index.html</filename></ulink></para>
 	  </listitem>
         </varlistentry>
       </variablelist>
     
-      <para>You can also view the master (and most frequently updated)
-        copies at <ulink
-	url="http://www.FreeBSD.org/"></ulink>.</para>
+      <para>¦¹¥~¡A¥i¦b¤U¦Cºô§}§ä¨ì³Ì·sª© (¤]¬O§ó·s³ÌÀWÁcªºª©¥»)¡G<ulink
+	url="http://www.FreeBSD.org/"></ulink>¡C</para>
     </sect2>
   </sect1>
 </chapter>
 
 <!-- 
      Local Variables:
      mode: sgml
      sgml-declaration: "../chapter.decl"
      sgml-indent-data: t
      sgml-omittag: nil
      sgml-always-quote-attributes: t
      sgml-parent-document: ("../book.sgml" "part" "chapter")
      End:
 -->
diff --git a/zh_TW.Big5/books/handbook/linuxemu/chapter.sgml b/zh_TW.Big5/books/handbook/linuxemu/chapter.sgml
index a64a35ff6e..e6ef6c83fd 100644
--- a/zh_TW.Big5/books/handbook/linuxemu/chapter.sgml
+++ b/zh_TW.Big5/books/handbook/linuxemu/chapter.sgml
@@ -1,3348 +1,3358 @@
 <!--
      The FreeBSD Documentation Project
 
      $FreeBSD$
 -->
 
 <chapter id="linuxemu">
   <chapterinfo>
     <authorgroup>
       <author>
 	<firstname>Jim</firstname>
 	<surname>Mock</surname>
 	<contrib>Restructured and parts updated by </contrib>
       </author>
       <!-- 22 Mar 2000 -->
     </authorgroup>
     <authorgroup>
       <author>
 	<firstname>Brian N.</firstname>
 	<surname>Handy</surname>
 	<contrib>Originally contributed by </contrib>
       </author>
       <author>
 	<firstname>Rich</firstname>
 	<surname>Murphey</surname>
       </author>
     </authorgroup>
   </chapterinfo>
 
   <title>Linux Binary Compatibility</title>
 
   <sect1 id="linuxemu-synopsis">
     <title>Synopsis</title>
     <indexterm><primary>Linux binary compatibility</primary></indexterm>
     <indexterm>
       <primary>binary compatibility</primary>
       <secondary>Linux</secondary>
     </indexterm>
 
     <para>FreeBSD provides binary compatibility with several other
       &unix; like operating systems, including Linux.  At this point,
       you may be asking yourself why exactly, does
       FreeBSD need to be able to run Linux binaries?  The answer to that
       question is quite simple.  Many companies and developers develop
       only for Linux, since it is the latest <quote>hot thing</quote> in
       the computing world.  That leaves the rest of us FreeBSD users
       bugging these same companies and developers to put out native
       FreeBSD versions of their applications.  The problem is, that most
       of these companies do not really realize how many people would use
       their product if there were FreeBSD versions too, and most continue
       to only develop for Linux.  So what is a FreeBSD user to do?  This
       is where the Linux binary compatibility of FreeBSD comes into
       play.</para>
 
     <para>In a nutshell, the compatibility allows FreeBSD users to run
       about 90% of all Linux applications without modification.  This
       includes applications such as <application>&staroffice;</application>,
       the Linux version of <application>&netscape;</application>,
       <application>&adobe;&nbsp;&acrobat;</application>,
       <application><trademark class="registered">RealPlayer</trademark></application>,
       <application><trademark>VMware</trademark></application>,
       <application>&oracle;</application>,
       <application><trademark class="registered">WordPerfect</trademark></application>, <application>Doom</application>,
       <application>Quake</application>, and more.  It is also reported
       that in some situations, Linux binaries perform better on FreeBSD
       than they do under Linux.</para>
 
     <para>There are, however, some Linux-specific operating system
       features that are not supported under FreeBSD.  Linux binaries will
       not work on FreeBSD if they overly use &i386; specific
       calls, such as enabling virtual 8086 mode.</para>
 
     <para>After reading this chapter, you will know:</para>
     <itemizedlist>
       <listitem>
 	<para>How to enable Linux binary compatibility on your system.</para>
       </listitem>
 
       <listitem>
 	<para>How to install additional Linux shared
 	  libraries.</para>
 	</listitem>
 
       <listitem>
 	<para>How to install Linux applications on your FreeBSD system.</para>
       </listitem>
 
       <listitem>
 	<para>The implementation details of Linux compatibility in FreeBSD.</para>
       </listitem>
     </itemizedlist>
 
     <para>Before reading this chapter, you should:</para>
 
     <itemizedlist>
       <listitem>
 	<para>Know how to install additional third-party
         software (<xref linkend="ports">).</para>
       </listitem>
     </itemizedlist>
 
   </sect1>
 
   <sect1 id="linuxemu-lbc-install">
     <title>Installation</title>
 
     <indexterm><primary>KLD (kernel loadable object)</primary></indexterm>
 
     <para>Linux binary compatibility is not turned on by default.  The
       easiest way to enable this functionality is to load the
       <literal>linux</literal> KLD object (<quote>Kernel LoaDable
       object</quote>).  You can load this module by typing the
       following as <username>root</username>:</para>
 
     <screen>&prompt.root; <userinput>kldload linux</userinput></screen>
 
     <para>If you would like Linux compatibility to always be enabled,
       then you should add the following line to
       <filename>/etc/rc.conf</filename>:</para>
 
     <programlisting>linux_enable="YES"</programlisting>
 
     <para>The &man.kldstat.8; command can be used to verify that the
       KLD is loaded:</para>
 
     <screen>&prompt.user; <userinput>kldstat</userinput>
 Id Refs Address    Size     Name
  1    2 0xc0100000 16bdb8   kernel
  7    1 0xc24db000 d000     linux.ko</screen>
     <indexterm>
       <primary>kernel options</primary>
       <secondary>LINUX</secondary>
     </indexterm>
 
     <para>If for some reason you do not want to or cannot load the KLD,
       then you may statically link Linux binary compatibility into the kernel
       by adding <literal>options COMPAT_LINUX</literal> to your kernel
       configuration file.  Then install your new kernel as described in
       <xref linkend="kernelconfig">.</para>
 
     <sect2>
       <title>Installing Linux Runtime Libraries</title>
       <indexterm>
 	<primary>Linux</primary>
 	<secondary>installing Linux libraries</secondary>
       </indexterm>
 
       <para>This can be done one of two ways, either by using the
 	<link linkend="linuxemu-libs-port">linux_base</link> port, or
 	by installing them <link
 	linkend="linuxemu-libs-manually">manually</link>.</para>
 
       <sect3 id="linuxemu-libs-port">
 	<title>Installing Using the linux_base Port</title>
 	<indexterm><primary>Ports Collection</primary></indexterm>
 
 	<para>This is by far the easiest method to use when installing the
 	  runtime libraries.  It is just like installing any other port
 	  from the <ulink type="html" url="file://localhost/usr/ports/">Ports Collection</ulink>.
 	  Simply do the following:</para>
 
 	<screen>&prompt.root; <userinput>cd /usr/ports/emulators/linux_base</userinput>
 &prompt.root; <userinput>make install distclean</userinput></screen>
 
 	<para>You should now have working Linux binary compatibility.
 	  Some programs may complain about incorrect minor versions of the
 	  system libraries.  In general, however, this does not seem to be
 	  a problem.</para>
 
 	<note><para>There may be multiple versions of the <filename
 	  role="package">emulators/linux_base</filename> port available,
 	  corresponding to different versions of various Linux distributions.
 	  You should install the port most closely resembling the
 	  requirements of the Linux applications you would like to
 	  install.</para></note>
 
       </sect3>
 
       <sect3 id="linuxemu-libs-manually">
 	<title>Installing Libraries Manually</title>
 
 	<para>If you do not have the <quote>ports</quote> collection
 	  installed, you can install the libraries by hand instead.  You
 	  will need the Linux shared libraries that the program depends on
 	  and the runtime linker.  Also, you will need to create a
 	  <quote>shadow root</quote> directory,
 	  <filename>/compat/linux</filename>, for Linux libraries on your
 	  FreeBSD system.  Any shared libraries opened by Linux programs
 	  run under FreeBSD will look in this tree first.  So, if a Linux
 	  program loads, for example, <filename>/lib/libc.so</filename>,
 	  FreeBSD will first try to open
 	  <filename>/compat/linux/lib/libc.so</filename>, and if that does
 	  not exist, it will then try <filename>/lib/libc.so</filename>.
 	  Shared libraries should be installed in the shadow tree
 	  <filename>/compat/linux/lib</filename> rather than the paths
 	  that the Linux <command>ld.so</command> reports.</para>
 
 	<para>Generally, you will need to look for the shared libraries
 	  that Linux binaries depend on only the first few times that you
 	  install a Linux program on your FreeBSD system.  After a while,
 	  you will have a sufficient set of Linux shared libraries on your
 	  system to be able to run newly imported Linux binaries without
 	  any extra work.</para>
       </sect3>
 
       <sect3>
 	<title>How to Install Additional Shared Libraries</title>
 	<indexterm><primary>shared libraries</primary></indexterm>
 
 	<para>What if you install the <filename>linux_base</filename> port
 	  and your application still complains about missing shared
 	  libraries?  How do you know which shared libraries Linux
 	  binaries need, and where to get them?  Basically, there are 2
 	  possibilities (when following these instructions you will need
 	  to be <username>root</username> on your FreeBSD system).</para>
 
 	<para>If you have access to a Linux system, see what shared
 	  libraries the application needs, and copy them to your FreeBSD
 	  system.  Look at the following example:</para>
 
 	<informalexample>
 	  <para>Let us assume you used FTP to get the Linux binary of
 	    <application>Doom</application>, and put it on a Linux system you have access to.  You
 	    then can check which shared libraries it needs by running
 	    <command>ldd linuxdoom</command>, like so:</para>
 
 	  <screen>&prompt.user; <userinput>ldd linuxdoom</userinput>
 libXt.so.3 (DLL Jump 3.1) =&gt; /usr/X11/lib/libXt.so.3.1.0
 libX11.so.3 (DLL Jump 3.1) =&gt; /usr/X11/lib/libX11.so.3.1.0
 libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
 
 	  <indexterm><primary>symbolic links</primary></indexterm>
 	  <para>You would need to get all the files from the last column,
 	    and put them under <filename>/compat/linux</filename>, with
 	    the names in the first column as symbolic links pointing to
 	    them.  This means you eventually have these files on your
 	    FreeBSD system:</para>
 
 	  <screen>/compat/linux/usr/X11/lib/libXt.so.3.1.0
 /compat/linux/usr/X11/lib/libXt.so.3 -&gt; libXt.so.3.1.0
 /compat/linux/usr/X11/lib/libX11.so.3.1.0
 /compat/linux/usr/X11/lib/libX11.so.3 -&gt; libX11.so.3.1.0
 /compat/linux/lib/libc.so.4.6.29
 /compat/linux/lib/libc.so.4 -&gt; libc.so.4.6.29</screen>
 
 	  <blockquote>
 	    <note>
 	      <para>Note that if you already have a Linux shared library
 		with a matching major revision number to the first column
 		of the <command>ldd</command> output, you will not need to
 		copy the file named in the last column to your system, the
 		one you already have should work.  It is advisable to copy
 		the shared library anyway if it is a newer version,
 		though.  You can remove the old one, as long as you make
 		the symbolic link point to the new one.  So, if you have
 		these libraries on your system:</para>
 
 	      <screen>/compat/linux/lib/libc.so.4.6.27
 /compat/linux/lib/libc.so.4 -&gt; libc.so.4.6.27</screen>
 
 	      <para>and you find a new binary that claims to require a
 		later version according to the output of
 		<command>ldd</command>:</para>
 
 	      <screen>libc.so.4 (DLL Jump 4.5pl26) -&gt; libc.so.4.6.29</screen>
 
 	      <para>If it is only one or two versions out of date in the
 		in the trailing digit then do not worry about copying
 		<filename>/lib/libc.so.4.6.29</filename> too, because the
 		program should work fine with the slightly older version.
 		However, if you like, you can decide to replace the
 		<filename>libc.so</filename> anyway, and that should leave
 		you with:</para>
 
 	      <screen>/compat/linux/lib/libc.so.4.6.29
 /compat/linux/lib/libc.so.4 -&gt; libc.so.4.6.29</screen>
 	    </note>
 	  </blockquote>
 
 	  <blockquote>
 	    <note>
 	      <para>The symbolic link mechanism is
 		<emphasis>only</emphasis> needed for Linux binaries.  The
 		FreeBSD runtime linker takes care of looking for matching
 		major revision numbers itself and you do not need to worry
 		about it.</para>
 	    </note>
 	  </blockquote>
 	</informalexample>
       </sect3>
     </sect2>
 
     <sect2>
       <title>Installing Linux ELF Binaries</title>
       <indexterm>
 	<primary>Linux</primary>
 	<secondary>ELF binaries</secondary>
       </indexterm>
 
       <para>ELF binaries sometimes require an extra step of
 	<quote>branding</quote>.  If you attempt to run an unbranded ELF
 	binary, you will get an error message like the following:</para>
 
       <screen>&prompt.user; <userinput>./my-linux-elf-binary</userinput>
 ELF binary type not known
 Abort</screen>
 
       <para>To help the FreeBSD kernel distinguish between a FreeBSD ELF
 	binary from a Linux binary, use the &man.brandelf.1;
 	utility.</para>
 
       <screen>&prompt.user; <userinput>brandelf -t Linux my-linux-elf-binary</userinput></screen>
 
       <indexterm><primary>GNU toolchain</primary></indexterm>
       <para>The GNU toolchain now places the appropriate branding
 	information into ELF binaries automatically, so this step
 	should become increasingly unnecessary in the future.</para>
     </sect2>
 
     <sect2>
       <title>Configuring the Hostname Resolver</title>
 
       <para>If DNS does not work or you get this message:</para>
 
       <screen>resolv+: "bind" is an invalid keyword resolv+:
 "hosts" is an invalid keyword</screen>
 
       <para>You will need to configure a
 	<filename>/compat/linux/etc/host.conf</filename> file
 	containing:</para>
 
       <programlisting>order hosts, bind
 multi on</programlisting>
 
       <para>The order here specifies that <filename>/etc/hosts</filename>
 	is searched first and DNS is searched second.  When
 	<filename>/compat/linux/etc/host.conf</filename> is not
 	installed, Linux applications find FreeBSD's
 	<filename>/etc/host.conf</filename> and complain about the
 	incompatible FreeBSD syntax.  You should remove
 	<literal>bind</literal> if you have not configured a name server
 	using the <filename>/etc/resolv.conf</filename> file.</para>
     </sect2>
   </sect1>
 
   <sect1 id="linuxemu-mathematica">
     <sect1info>
       <authorgroup>
 	<author>
-	  <firstname>Murray</firstname>
-	  <surname>Stokely</surname>
-	  <contrib>Updated for Mathematica 4.X by </contrib>
-	</author>
-      </authorgroup>
-      <authorgroup>
-	<author>
-	  <firstname>Bojan</firstname>
-	  <surname>Bistrovic</surname>
-	  <contrib>Merged with work by </contrib>
+	  <firstname>Boris</firstname>
+	  <surname>Hollas</surname>
+	  <contrib>Updated for Mathematica 5.X by </contrib>
 	</author>
       </authorgroup>
     </sect1info>
     <title>Installing &mathematica;</title>
 
     <indexterm>
       <primary>applications</primary>
       <secondary><application>Mathematica</application></secondary>
     </indexterm>
 
     <para>This document describes the process of installing the Linux
-      version of <application>&mathematica; 4.X</application> onto
+      version of <application>&mathematica; 5.X</application> onto
       a FreeBSD system.</para>
 
-    <para>The Linux version of <application>&mathematica;</application>
-      runs perfectly under FreeBSD
-      however the binaries shipped by Wolfram need to be branded so that
-      FreeBSD knows to use the Linux ABI to execute them.</para>
-
     <para>The Linux version of <application>&mathematica;</application>
       or <application>&mathematica; for Students</application> can
       be ordered directly from Wolfram at
       <ulink url="http://www.wolfram.com/"></ulink>.</para>
 
     <sect2>
-      <title>Branding the Linux Binaries</title>
-
-      <para>The Linux binaries are located in the <filename>Unix</filename>
-	directory of the <application>&mathematica;</application> CDROM
-	distributed by Wolfram.  You
-	need to copy this directory tree to your local hard drive so that
-	you can brand the Linux binaries with &man.brandelf.1; before
-	running the installer:</para>
+      <title>Running the &mathematica; Installer</title>
 
-      <screen>&prompt.root; <userinput>mount /cdrom</userinput>
-&prompt.root; <userinput>cp -rp /cdrom/Unix/ /localdir/</userinput>
-&prompt.root; <userinput>brandelf -t Linux /localdir/Files/SystemFiles/Kernel/Binaries/Linux/*</userinput>
-&prompt.root; <userinput>brandelf -t Linux /localdir/Files/SystemFiles/FrontEnd/Binaries/Linux/*</userinput>
-&prompt.root; <userinput>brandelf -t Linux /localdir/Files/SystemFiles/Installation/Binaries/Linux/*</userinput>
-&prompt.root; <userinput>brandelf -t Linux /localdir/Files/SystemFiles/Graphics/Binaries/Linux/*</userinput>
-&prompt.root; <userinput>brandelf -t Linux /localdir/Files/SystemFiles/Converters/Binaries/Linux/*</userinput>
-&prompt.root; <userinput>brandelf -t Linux /localdir/Files/SystemFiles/LicenseManager/Binaries/Linux/mathlm</userinput>
-&prompt.root; <userinput>cd /localdir/Installers/Linux/</userinput>
-&prompt.root; <userinput>./MathInstaller</userinput></screen>
-
-      <para>Alternatively, you can simply set the default ELF brand
+      <para>First, you have to tell &os; that
+	<application>&mathematica;</application>'s Linux
+	binaries use the Linux ABI.  The easiest way to do so is to
+	set the default ELF brand
 	to Linux for all unbranded binaries with the command:</para>
+
       <screen>&prompt.root; <userinput>sysctl kern.fallback_elf_brand=3</userinput></screen>
-      <para>This will make FreeBSD assume that unbranded ELF binaries
+
+      <para>This will make &os; assume that unbranded ELF binaries
 	use the Linux ABI and so you should be able to run the
 	installer straight from the CDROM.</para>
+
+      <para>Now, copy the file <filename>MathInstaller</filename> to
+	your hard drive:</para>
+
+      <screen>&prompt.root; <userinput>mount /cdrom</userinput>
+&prompt.root; <userinput>cp /cdrom/Unix/Installers/Linux/MathInstaller /localdir/</userinput></screen>
+
+      <para>and in this file, replace <literal>/bin/sh</literal> in
+	the first line by <literal>/compat/linux/bin/sh</literal>.
+	This makes sure that the installer is executed by the Linux
+	version of &man.sh.1;.  Next, replace all occurrences of
+	<literal>Linux)</literal> by <literal>FreeBSD)</literal> with
+	a text editor or the script below in the next section.  This
+	tells the <application>&mathematica;</application> installer,
+	who calls <command>uname -s</command> to determine the
+	operating system, to treat &os; as a Linux-like operating
+	system.  Invoking <command>MathInstaller</command> will now
+	install <application>&mathematica;</application>.</para>
+    </sect2>
+
+    <sect2>
+      <title>Modifying the &mathematica; Executables</title>
+
+      <para>The shell scripts that
+	<application>&mathematica;</application> created during
+	installation have to be modified before you can use them.  If
+	you chose <filename role="directory">/usr/local/bin</filename>
+	as the directory to place the
+	<application>&mathematica;</application> executables in, you
+	will find symlinks in this directory to files called
+	<filename>math</filename>, <filename>mathematica</filename>,
+	<filename>Mathematica</filename>, and
+	<filename>MathKernel</filename>.  In each of these, replace
+	<literal>Linux)</literal> by <literal>FreeBSD)</literal> with
+	a text editor or the following shell script:</para>
+
+      <programlisting>#!/bin/sh
+cd /usr/local/bin
+for i in math mathematica Mathematica MathKernel
+  do sed 's/Linux)/FreeBSD)/g' $i &gt; $i.tmp
+  sed 's/\/bin\/sh/\/compat\/linux\/bin\/sh/g' $i.tmp &gt; $i
+  rm $i.tmp
+  chmod a+x $i
+done</programlisting>
     </sect2>
 
     <sect2>
       <title>Obtaining Your &mathematica; Password</title>
 
-      <para>Before you can run <application>&mathematica;</application>
-	you will have to obtain a
-	password from Wolfram that corresponds to your <quote>machine
-	ID</quote>.</para>
       <indexterm>
 	<primary>Ethernet</primary>
 	<secondary>MAC address</secondary>
       </indexterm>
 
-      <para>Once you have installed the Linux compatibility runtime
-	libraries and unpacked <application>&mathematica;</application>
-	you can obtain the
-	<quote>machine ID</quote> by running the program
-	<command>mathinfo</command> in the installation directory.  This
-	machine ID is based solely on the MAC address of your first
-	Ethernet card.</para>
-
-      <screen>&prompt.root; <userinput>cd /localdir/Files/SystemFiles/Installation/Binaries/Linux</userinput>
-&prompt.root; <userinput>mathinfo</userinput>
-disco.example.com 7115-70839-20412</screen>
+      <para>When you start <application>&mathematica;</application>
+	for the first time, you will be asked for a password.  If you
+	have not yet obtained a password from Wolfram, run the program
+	<command>mathinfo</command> in the installation directory to
+	obtain your <quote>machine ID</quote>.  This machine ID is
+	based solely on the MAC address of your first Ethernet card,
+	so you cannot run your copy of
+	<application>&mathematica;</application> on different
+	machines.</para>
 
       <para>When you register with Wolfram, either by email, phone or fax,
 	you will give them the <quote>machine ID</quote> and they will
 	respond with a corresponding password consisting of groups of
-	numbers.  You can then enter this information when you attempt to
-	run <application>&mathematica;</application> for the first time
-	exactly as you would for any other
-	<application>&mathematica;</application> platform.</para>
+	numbers.</para>
     </sect2>
 
     <sect2>
       <title>Running the &mathematica; Frontend over a Network</title>
 
       <para><application>&mathematica;</application> uses some special
 	fonts to display characters not
 	present in any of the standard font sets (integrals, sums, Greek
 	letters, etc.).  The X protocol requires these fonts to be install
 	<emphasis>locally</emphasis>.  This means you will have to copy
 	these fonts from the CDROM or from a host with
 	<application>&mathematica;</application>
 	installed to your local machine.  These fonts are normally stored
 	in <filename>/cdrom/Unix/Files/SystemFiles/Fonts</filename> on the
 	CDROM, or
 	<filename>/usr/local/mathematica/SystemFiles/Fonts</filename> on
 	your hard drive.  The actual fonts are in the subdirectories
 	<filename>Type1</filename> and <filename>X</filename>.  There are
 	several ways to use them, as described below.</para>
 
       <para>The first way is to copy them into one of the existing font
 	directories in <filename>/usr/X11R6/lib/X11/fonts</filename>.
 	This will require editing the <filename>fonts.dir</filename> file,
 	adding the font names to it, and changing the number of fonts on
 	the first line.  Alternatively, you should also just be able to
 	run &man.mkfontdir.1; in the directory you have copied
 	them to.</para>
 
       <para>The second way to do this is to copy the directories to
 	<filename>/usr/X11R6/lib/X11/fonts</filename>:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/X11R6/lib/X11/fonts</userinput>
 &prompt.root; <userinput>mkdir X</userinput>
 &prompt.root; <userinput>mkdir MathType1</userinput>
 &prompt.root; <userinput>cd /cdrom/Unix/Files/SystemFiles/Fonts</userinput>
 &prompt.root; <userinput>cp X/* /usr/X11R6/lib/X11/fonts/X</userinput>
 &prompt.root; <userinput>cp Type1/* /usr/X11R6/lib/X11/fonts/MathType1</userinput>
 &prompt.root; <userinput>cd /usr/X11R6/lib/X11/fonts/X</userinput>
 &prompt.root; <userinput>mkfontdir</userinput>
 &prompt.root; <userinput>cd ../MathType1</userinput>
 &prompt.root; <userinput>mkfontdir</userinput></screen>
 
       <para>Now add the new font directories to your font path:</para>
 
       <screen>&prompt.root; <userinput>xset fp+ /usr/X11R6/lib/X11/fonts/X</userinput>
 &prompt.root; <userinput>xset fp+ /usr/X11R6/lib/X11/fonts/MathType1</userinput>
 &prompt.root; <userinput>xset fp rehash</userinput></screen>
 
       <para>If you are using the <application>&xorg;</application> server, you can have these font
 	directories loaded automatically by adding them to your
 	<filename>xorg.conf</filename> file.</para>
 
       <note><para>For <application>&xfree86;</application> servers,
 	the configuration file is <filename>XF86Config</filename>.</para></note>
       <indexterm><primary>fonts</primary></indexterm>
 
       <para>If you <emphasis>do not</emphasis> already have a directory
 	called <filename>/usr/X11R6/lib/X11/fonts/Type1</filename>, you
 	can change the name of the <filename>MathType1</filename>
 	directory in the example above to
 	<filename>Type1</filename>.</para>
     </sect2>
   </sect1>
 
   <sect1 id="linuxemu-maple">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Aaron</firstname>
 	  <surname>Kaplan</surname>
 <!--	  <address><email>aaron@lo-res.org</email></address>-->
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
       <authorgroup>
 	<author>
 	  <firstname>Robert</firstname>
 	  <surname>Getschmann</surname>
 <!--	  <address><email>rob@getschmann.org</email></address>-->
 	  <contrib>Thanks to </contrib>
 	</author>
       </authorgroup>
     </sect1info>
     <title>Installing &maple;</title>
 
     <indexterm>
       <primary>applications</primary>
       <secondary><application>Maple</application></secondary>
     </indexterm>
 
     <para><application>&maple;</application> is a commercial mathematics program similar to
       <application>&mathematica;</application>.  You must purchase this software from <ulink
       url="http://www.maplesoft.com/"></ulink> and then register there
       for a license file.  To install this software on FreeBSD, please
       follow these simple steps.</para>
 
       <procedure>
 	<step><para>Execute the <filename>INSTALL</filename> shell
 	  script from the product distribution.  Choose the
 	  <quote>RedHat</quote> option when prompted by the
 	  installation program.  A typical installation directory
 	  might be <filename
 	  class="directory">/usr/local/maple</filename>.</para></step>
 
         <step><para>If you have not done so, order a license for <application>&maple;</application>
 	  from Maple Waterloo Software (<ulink url="http://register.maplesoft.com/"></ulink>)
 	  and copy it to
 	  <filename>/usr/local/maple/license/license.dat</filename>.</para></step>
 
         <step><para>Install the <application>FLEXlm</application>
 	  license manager by running the
 	  <filename>INSTALL_LIC</filename> install shell script that
 	  comes with <application>&maple;</application>.  Specify the
 	  primary hostname for your machine for the license
 	  server.</para></step>
 
         <step><para>Patch the
           <filename>/usr/local/maple/bin/maple.system.type</filename>
           file with the following:</para>
 <programlisting>   ----- snip ------------------
 *** maple.system.type.orig      Sun Jul  8 16:35:33 2001
 --- maple.system.type   Sun Jul  8 16:35:51 2001
 ***************
 *** 72,77 ****
 --- 72,78 ----
           # the IBM RS/6000 AIX case
           MAPLE_BIN="bin.IBM_RISC_UNIX"
           ;;
 +     "FreeBSD"|\
       "Linux")
           # the Linux/x86 case
         # We have two Linux implementations, one for Red Hat and
    ----- snip end of patch -----</programlisting>
 
 	<para>Please note that after the <literal>"FreeBSD"|\</literal> no other
 	  whitespace should be present.</para>
 
 	<para>This patch instructs <application>&maple;</application> to
 	  recognize <quote>FreeBSD</quote> as a type of Linux system.
 	  The <filename>bin/maple</filename> shell script calls the
 	  <filename>bin/maple.system.type</filename> shell script
 	  which in turn calls <command>uname -a</command> to find out the operating
 	  system name. Depending on the OS name it will find out which
 	  binaries to use.</para></step>
 
       <step><para>Start the license server.</para>
 
 	<para>The following script, installed as
 	  <filename>/usr/local/etc/rc.d/lmgrd.sh</filename> is a
 	  convenient way to start up <command>lmgrd</command>:</para>
 
 	<programlisting>   ----- snip ------------
 
 #! /bin/sh
 PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin
 PATH=${PATH}:/usr/local/maple/bin:/usr/local/maple/FLEXlm/UNIX/LINUX
 export PATH
 
 LICENSE_FILE=/usr/local/maple/license/license.dat
 LOG=/var/log/lmgrd.log
 
 case "$1" in
 start)
-	lmgrd -c ${LICENSE_FILE} 2>> ${LOG} 1>&2
+	lmgrd -c ${LICENSE_FILE} 2&gt;&gt; ${LOG} 1&gt;&2
 	echo -n " lmgrd"
 	;;
 stop)
-	lmgrd -c ${LICENSE_FILE} -x lmdown 2>> ${LOG} 1>&2
+	lmgrd -c ${LICENSE_FILE} -x lmdown 2&gt;&gt; ${LOG} 1&gt;&2
 	;;
 *)
-	echo "Usage: `basename $0` {start|stop}" 1>&2
+	echo "Usage: `basename $0` {start|stop}" 1&gt;&2
 	exit 64
 	;;
 esac
 
 exit 0
    ----- snip ------------</programlisting></step>
 
 
       <step><para>Test-start <application>&maple;</application>:</para>
 	<screen>&prompt.user; <userinput>cd /usr/local/maple/bin</userinput>
 &prompt.user; <userinput>./xmaple</userinput></screen>
 
 	<para>You should be up and running. Make sure to write
 	  Maplesoft to let them know you would like a native FreeBSD
 	  version!</para></step>
     </procedure>
 
     <sect2>
       <title>Common Pitfalls</title>
 
       <itemizedlist>
 	<listitem><para>The <application>FLEXlm</application> license manager can be a difficult
 	  tool to work with.  Additional documentation on the subject
 	  can be found at <ulink
 	  url="http://www.globetrotter.com/"></ulink>.</para></listitem>
 
 	<listitem><para><command>lmgrd</command> is known to be very picky
 	  about the license file and to core dump if there are any
 	  problems.  A correct license file should look like this:</para>
 
 <programlisting># =======================================================
 # License File for UNIX Installations ("Pointer File")
 # =======================================================
 SERVER chillig ANY
 #USE_SERVER
 VENDOR maplelmg
 
 FEATURE Maple maplelmg 2000.0831 permanent 1 XXXXXXXXXXXX \
          PLATFORMS=i86_r ISSUER="Waterloo Maple Inc." \
          ISSUED=11-may-2000 NOTICE=" Technische Universitat Wien" \
          SN=XXXXXXXXX</programlisting>
 
 	  <note><para>Serial number and key 'X''ed out. <hostid>chillig</hostid> is a
 	    hostname.</para></note>
 
   	  <para>Editing the license file works as long as you do not
  	    touch the <quote>FEATURE</quote> line (which is protected by the
  	    license key).</para></listitem>
       </itemizedlist>
     </sect2>
   </sect1>
 
   <sect1 id="linuxemu-matlab">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Dan</firstname>
 	  <surname>Pelleg</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
 	<!-- daniel+handbook@pelleg.org -->
       </authorgroup>
     </sect1info>
     <title>Installing &matlab;</title>
 
     <indexterm>
       <primary>applications</primary>
       <secondary><application>MATLAB</application></secondary>
     </indexterm>
 
     <para>This document describes the process of installing the Linux
       version of <application>&matlab; version 6.5</application> onto
       a &os; system.  It works quite well, with the exception of the
       <application>&java.virtual.machine;</application> (see
       <xref linkend="matlab-jre">).</para>
 
     <para>The Linux version of <application>&matlab;</application> can be
       ordered directly from The MathWorks at <ulink
       url="http://www.mathworks.com"></ulink>.  Make sure you also get
       the license file or instructions how to create it.  While you
       are there, let them know you would like a native &os;
       version of their software.</para>
 
     <sect2>
       <title>Installing &matlab;</title>
 
       <para>To install <application>&matlab;</application>, do the 
 	following:</para>
 
       <procedure>
 	<step>
 	  <para>Insert the installation CD and mount it.
 	    Become <username>root</username>, as recommended by the
 	    installation script.  To start the installation script
 	    type:</para>
 
 	  <screen>&prompt.root; <userinput>/compat/linux/bin/sh /cdrom/install</userinput></screen>
 
 	  <tip>
 	    <para>The installer is graphical.  If you get errors about
 	      not being able to open a display, type
 	      <command>setenv HOME ~<replaceable>USER</replaceable></command>,
 	      where <replaceable>USER</replaceable> is the user you did a
 	      &man.su.1; as.</para>
 	  </tip>
 	</step>
 
 	<step>
 	  <para>
 	    When asked for the <application>&matlab;</application> root
 	    directory, type:
 	    <userinput>/compat/linux/usr/local/matlab</userinput>.</para>
 
 	  <tip>
 	    <para>For easier typing on the rest of the installation
 	      process, type this at your shell prompt:
 	      <command>set MATLAB=/compat/linux/usr/local/matlab</command></para>
 	  </tip>
 	</step>
 
 	<step>
 	  <para>Edit the license file as instructed when
 	    obtaining the <application>&matlab;</application> license.</para>
 
 	  <tip>
 	    <para>You can prepare this file in advance using your
 	      favorite editor, and copy it to
 	      <filename>$MATLAB/license.dat</filename> before the
 	      installer asks you to edit it.</para>
 	  </tip>
 	</step>
 
 	<step>
 	  <para>Complete the installation process.</para>
 	</step>
       </procedure>
 
       <para>At this point your <application>&matlab;</application>
 	installation is complete.  The following steps apply
 	<quote>glue</quote> to connect it to your &os; system.</para>
     </sect2>
 
     <sect2>
       <title>License Manager Startup</title>
       <procedure>
 	<step>
 	  <para>Create symlinks for the license manager scripts:</para>
 
 	  <screen>&prompt.root; <userinput>ln -s $MATLAB/etc/lmboot /usr/local/etc/lmboot_TMW</userinput>
 &prompt.root; <userinput>ln -s $MATLAB/etc/lmdown /usr/local/etc/lmdown_TMW</userinput></screen>
 	</step>
 	
 	<step>
 	  <para>Create a startup file at
 	    <filename>/usr/local/etc/rc.d/flexlm.sh</filename>.  The
 	    example below is a modified version of the distributed
 	    <filename>$MATLAB/etc/rc.lm.glnx86</filename>.  The changes
 	    are file locations, and startup of the license manager
 	    under Linux emulation.</para>
 
 	  <programlisting>#!/bin/sh
 case "$1" in
   start)
         if [ -f /usr/local/etc/lmboot_TMW ]; then
               /compat/linux/bin/sh /usr/local/etc/lmboot_TMW -u <replaceable>username</replaceable> &amp;&amp; echo 'MATLAB_lmgrd'
         fi
         ;;
   stop)
 	if [ -f /usr/local/etc/lmdown_TMW ]; then
             /compat/linux/bin/sh /usr/local/etc/lmdown_TMW  &gt; /dev/null 2&gt;&amp;1
 	fi
         ;;
   *)
 	echo "Usage: $0 {start|stop}"
 	exit 1
 	;;
 esac
 
 exit 0</programlisting>
 
 	  <important>
 	    <para>The file must be made executable:</para>
 
 	    <screen>&prompt.root; <userinput>chmod +x /usr/local/etc/rc.d/flexlm.sh</userinput></screen>
 
 	    <para>You must also replace
 	      <replaceable>username</replaceable> above with the name
 	      of a valid user on your system (and not
 	      <username>root</username>).</para>
 	  </important>
 	</step>
 
 	<step>
 	  <para>Start the license manager with the command:</para>
 
 	  <screen>&prompt.root; <userinput>/usr/local/etc/rc.d/flexlm.sh start</userinput></screen>
 	</step>
       </procedure>
     </sect2>
 
     <sect2 id="matlab-jre">
       <title>Linking the &java; Runtime Environment</title>
 
       <para>Change the <application>&java;</application> Runtime
 	Environment (JRE) link to one working under &os;:</para>
 
       <screen>&prompt.root; <userinput>cd $MATLAB/sys/java/jre/glnx86/</userinput>
 &prompt.root; <userinput>unlink jre; ln -s ./jre1.1.8 ./jre</userinput></screen>
     </sect2>
 
     <sect2>
       <title>Creating a &matlab; Startup Script</title>
 
       <procedure>
 	<step>
 	  <para>Place the following startup script in
 	    <filename>/usr/local/bin/matlab</filename>:
 	  </para>
 
 	  <programlisting>#!/bin/sh
 /compat/linux/bin/sh /compat/linux/usr/local/matlab/bin/matlab "$@"</programlisting>
 	</step>
 
 	<step>
 	  <para>Then type the command
 	    <command>chmod +x /usr/local/bin/matlab</command>.</para>
 	</step>
       </procedure>
 
       <tip>
 	<para>Depending on your version of
 	  <filename role="package">emulators/linux_base</filename>, you
 	  may run into errors when running this script.  To avoid that,
 	  edit the file
 	  <filename>/compat/linux/usr/local/matlab/bin/matlab</filename>,
 	  and change the line that says:</para>
 
 	<programlisting>if [ `expr "$lscmd" : '.*-&gt;.*'` -ne 0 ]; then</programlisting>
 
 	<para>(in version 13.0.1 it is on line 410) to this
 	  line:</para>
 
 	<programlisting>if test -L $newbase; then</programlisting>
       </tip>
     </sect2>
 
     <sect2>
       <title>Creating a &matlab; Shutdown Script</title>
 
       <para>The following is needed to solve a problem with &matlab;
 	not exiting correctly.</para>
 
       <procedure>
 	<step>
 	  <para>Create a file
 	    <filename>$MATLAB/toolbox/local/finish.m</filename>, and
 	    in it put the single line:</para>
 
 	  <programlisting>! $MATLAB/bin/finish.sh</programlisting>
 
 	  <note><para>The <literal>$MATLAB</literal> is
 	    literal.</para></note>
 
 	  <tip>
 	    <para>In the same directory, you will find the files
 	      <filename>finishsav.m</filename> and
 	      <filename>finishdlg.m</filename>, which let you save
 	      your workspace before quitting.  If you use either of
 	      them, insert the line above immediately after the
 	      <literal>save</literal> command.</para></tip>
 	</step>
 
 	<step>
 	  <para>Create a file
 	    <filename>$MATLAB/bin/finish.sh</filename>, which will
 	    contain the following:</para>
 
 	  <programlisting>#!/usr/compat/linux/bin/sh
 (sleep 5; killall -1 matlab_helper) &
 exit 0</programlisting>
 	</step>
 
 	<step>
 	  <para>Make the file executable:</para>
 
 	  <screen>&prompt.root; <userinput>chmod +x $MATLAB/bin/finish.sh</userinput></screen>
 	</step>
       </procedure>
     </sect2>
 
     <sect2 id="matlab-using">
       <title>Using &matlab;</title>
 
       <para>At this point you are ready to type
 	<command>matlab</command> and start using it.</para>
     </sect2>
   </sect1>
 
   <sect1 id="linuxemu-oracle">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Marcel</firstname>
 	  <surname>Moolenaar</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
 	<!-- marcel@cup.hp.com -->
       </authorgroup>
     </sect1info>
     <title>Installing &oracle;</title>
 
     <indexterm>
       <primary>applications</primary>
       <secondary><application>Oracle</application></secondary>
     </indexterm>
 
     <sect2>
       <title>Preface</title>
       <para>This document describes the process of installing <application>&oracle; 8.0.5</application> and
 	<application>&oracle; 8.0.5.1 Enterprise Edition</application> for Linux onto a FreeBSD
 	machine.</para>
     </sect2>
 
     <sect2>
       <title>Installing the Linux Environment</title>
 
       <para>Make sure you have both <filename role='package'>emulators/linux_base</filename> and
 	<filename role='package'>devel/linux_devtools</filename> from the Ports Collection
 	installed.  If you run into difficulties with these ports,
 	you may have to use
 	the packages or older versions available in the Ports Collection.</para>
 
       <para>If you want to run the intelligent agent, you will
 	also need to install the Red Hat Tcl package:
 	<filename>tcl-8.0.3-20.i386.rpm</filename>.  The general command
 	for installing packages with the official <application>RPM</application> port (<filename role='package'>archivers/rpm</filename>) is:</para>
 
       <screen>&prompt.root; <userinput>rpm -i --ignoreos --root /compat/linux --dbpath /var/lib/rpm <replaceable>package</replaceable></userinput></screen>
 
       <para>Installation of the <replaceable>package</replaceable> should not generate any errors.</para>
     </sect2>
 
     <sect2>
       <title>Creating the &oracle; Environment</title>
 
       <para>Before you can install <application>&oracle;</application>, you need to set up a proper
 	environment.  This document only describes what to do
 	<emphasis>specially</emphasis> to run <application>&oracle;</application> for Linux on FreeBSD, not
 	what has been described in the <application>&oracle;</application> installation guide.</para>
 
       <sect3 id="linuxemu-kernel-tuning">
         <title>Kernel Tuning</title>
 	<indexterm><primary>kernel tuning</primary></indexterm>
 
 	<para>As described in the <application>&oracle;</application> installation guide, you need to set
 	  the maximum size of shared memory.  Do not use
 	  <literal>SHMMAX</literal> under FreeBSD. <literal>SHMMAX</literal>
 	  is merely calculated out of <literal>SHMMAXPGS</literal> and
 	  <literal>PGSIZE</literal>.  Therefore define
 	  <literal>SHMMAXPGS</literal>.  All other options can be used as
 	  described in the guide.  For example:</para>
 
 	<programlisting>options SHMMAXPGS=10000
 options SHMMNI=100
 options SHMSEG=10
 options SEMMNS=200
 options SEMMNI=70
 options SEMMSL=61</programlisting>
 
 	<para>Set these options to suit your intended use of <application>&oracle;</application>.</para>
 
 	<para>Also, make sure you have the following options in your kernel
 	  configuration file:</para>
 
 <programlisting>options SYSVSHM #SysV shared memory
 options SYSVSEM #SysV semaphores
 options SYSVMSG #SysV interprocess communication</programlisting>
       </sect3>
 
       <sect3 id="linuxemu-oracle-account">
 
         <title>&oracle; Account</title>
 
 	<para>Create an <username>oracle</username> account just as you would create any other
 	  account. The  <username>oracle</username> account is special only that you need to give
 	  it a Linux shell.  Add <literal>/compat/linux/bin/bash</literal> to
 	  <filename>/etc/shells</filename> and set the shell for the <username>oracle</username>
 	  account to <filename>/compat/linux/bin/bash</filename>.</para>
       </sect3>
 
       <sect3 id="linuxemu-environment">
         <title>Environment</title>
 
 	<para>Besides the normal <application>&oracle;</application> variables, such as
 	  <envar>ORACLE_HOME</envar> and <envar>ORACLE_SID</envar> you must
 	  set the following environment variables:</para>
 
 	<informaltable frame="none" pgwide="1">
 	  <tgroup cols="2">
           <colspec colwidth="1*">
           <colspec colwidth="2*">
 	    <thead>
 	      <row>
 		<entry>Variable</entry>
 
 		<entry>Value</entry>
 	      </row>
 	    </thead>
 	    <tbody>
 	      <row>
 		<entry><envar>LD_LIBRARY_PATH</envar></entry>
 
 		<entry><literal>$ORACLE_HOME/lib</literal></entry>
 	      </row>
 
 	      <row>
 		<entry><envar>CLASSPATH</envar></entry>
 
 		<entry><literal>$ORACLE_HOME/jdbc/lib/classes111.zip</literal></entry>
 	      </row>
 
 	      <row>
 		<entry><envar>PATH</envar></entry>
 
 		<entry><literal>/compat/linux/bin
 /compat/linux/sbin
 /compat/linux/usr/bin
 /compat/linux/usr/sbin
 /bin
 /sbin
 /usr/bin
 /usr/sbin
 /usr/local/bin
 $ORACLE_HOME/bin</literal></entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</informaltable>
 
         <para>It is advised to set all the environment variables in
 	  <filename>.profile</filename>.  A complete example is:</para>
 
 <programlisting>ORACLE_BASE=/oracle; export ORACLE_BASE
 ORACLE_HOME=/oracle; export ORACLE_HOME
 LD_LIBRARY_PATH=$ORACLE_HOME/lib
 export LD_LIBRARY_PATH
 ORACLE_SID=ORCL; export ORACLE_SID
 ORACLE_TERM=386x; export ORACLE_TERM
 CLASSPATH=$ORACLE_HOME/jdbc/lib/classes111.zip
 export CLASSPATH
 PATH=/compat/linux/bin:/compat/linux/sbin:/compat/linux/usr/bin
 PATH=$PATH:/compat/linux/usr/sbin:/bin:/sbin:/usr/bin:/usr/sbin
 PATH=$PATH:/usr/local/bin:$ORACLE_HOME/bin
 export PATH</programlisting>
       </sect3>
     </sect2>
 
     <sect2>
       <title>Installing &oracle;</title>
 
       <para>Due to a slight inconsistency in the Linux emulator, you need to
 	create a directory named <filename>.oracle</filename> in
 	<filename>/var/tmp</filename> before you start the installer.
 	Let it be owned by the <username>oracle</username> user.  You
 	should be able to install <application>&oracle;</application> without any problems.  If you have
 	problems, check your <application>&oracle;</application> distribution and/or configuration first!
 	After you have installed <application>&oracle;</application>, apply the patches described in the
 	next two subsections.</para>
 
       <para>A frequent problem is that the TCP protocol adapter is not
 	installed right. As a consequence, you cannot start any TCP listeners.
 	The following actions help solve this problem:</para>
 
       <screen>&prompt.root; <userinput>cd $ORACLE_HOME/network/lib</userinput>
 &prompt.root; <userinput>make -f ins_network.mk ntcontab.o</userinput>
 &prompt.root; <userinput>cd $ORACLE_HOME/lib</userinput>
 &prompt.root; <userinput>ar r libnetwork.a ntcontab.o</userinput>
 &prompt.root; <userinput>cd $ORACLE_HOME/network/lib</userinput>
 &prompt.root; <userinput>make -f ins_network.mk install</userinput></screen>
 
       <para>Do not forget to run <filename>root.sh</filename> again!</para>
 
     <sect3 id="linuxemu-patch-root">
       <title>Patching root.sh</title>
 
 	<para>When installing <application>&oracle;</application>, some actions, which need to be performed
 	  as <username>root</username>, are recorded in a shell script called
 	  <filename>root.sh</filename>.  This script is
 	  written in the <filename>orainst</filename> directory.  Apply the
 	  following patch to <filename>root.sh</filename>, to have it use to proper location of
 	  <command>chown</command> or alternatively run the script under a
 	  Linux native shell.</para>
 
 	<programlisting>*** orainst/root.sh.orig Tue Oct 6 21:57:33 1998
 --- orainst/root.sh Mon Dec 28 15:58:53 1998
 ***************
 *** 31,37 ****
 # This is the default value for CHOWN
 # It will redefined later in this script for those ports
 # which have it conditionally defined in ss_install.h
 ! CHOWN=/bin/chown
 #
 # Define variables to be used in this script
 --- 31,37 ----
 # This is the default value for CHOWN
 # It will redefined later in this script for those ports
 # which have it conditionally defined in ss_install.h
 ! CHOWN=/usr/sbin/chown
 #
 # Define variables to be used in this script</programlisting>
 
 	<para>When you do not install <application>&oracle;</application> from CD, you can patch the source
 	  for <filename>root.sh</filename>.  It is called
 	  <filename>rthd.sh</filename> and is located in the
 	  <filename>orainst</filename> directory in the source tree.</para>
       </sect3>
 
       <sect3 id="linuxemu-patch-tcl">
 	<title>Patching genclntsh</title>
 
 	<para>The script <command>genclntsh</command> is used to create
 	  a single shared client
 	  library.  It is used when building the demos.  Apply the following
 	  patch to comment out the definition of <envar>PATH</envar>:</para>
 
 	<programlisting>*** bin/genclntsh.orig Wed Sep 30 07:37:19 1998
 --- bin/genclntsh Tue Dec 22 15:36:49 1998
 ***************
 *** 32,38 ****
 #
 # Explicit path to ensure that we're using the correct commands
 #PATH=/usr/bin:/usr/ccs/bin export PATH
 ! PATH=/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin export PATH
 #
 # each product MUST provide a $PRODUCT/admin/shrept.lst
 --- 32,38 ----
 #
 # Explicit path to ensure that we're using the correct commands
 #PATH=/usr/bin:/usr/ccs/bin export PATH
 ! #PATH=/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin export PATH
 #
 # each product MUST provide a $PRODUCT/admin/shrept.lst</programlisting>
       </sect3>
     </sect2>
 
     <sect2>
       <title>Running &oracle;</title>
 
       <para>When you have followed the instructions, you should be able to run
 	<application>&oracle;</application> as if it was run on Linux
 	itself.</para>
     </sect2>
   </sect1>
 
   <sect1 id="sapr3">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Holger</firstname>
 	  <surname>Kipp</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
       <!-- holger.kipp@alogis.com -->
       <authorgroup>
 	<author>
 	  <firstname>Valentino</firstname>
 	  <surname>Vaschetto</surname>
 	  <contrib>Original version converted to SGML by </contrib>
 	</author>
       </authorgroup>
     </sect1info>
 
     <title>Installing &sap.r3;</title>
 
     <indexterm>
       <primary>applications</primary>
       <secondary><application>SAP R/3</application></secondary>
     </indexterm>
 
     <para>Installations of <application>&sap;</application> Systems using FreeBSD will not be
       supported by the &sap; support team &mdash; they only offer support
       for certified platforms.</para>
 
     <sect2 id="preface">
       <title>Preface</title>
 
       <para>This document describes a possible way of installing a
 	<application>&sap.r3; System</application>
 	with <application>&oracle; Database</application>
 	for Linux onto a FreeBSD machine, including the installation
 	of FreeBSD and <application>&oracle;</application>. Two different
 	configurations will be described:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><application>&sap.r3; 4.6B (IDES)</application> with
 	  <application>&oracle; 8.0.5</application> on FreeBSD 4.3-STABLE</para>
 	</listitem>
 
 	<listitem>
 	  <para><application>&sap.r3; 4.6C</application> with
 	  <application>&oracle; 8.1.7</application> on FreeBSD 4.5-STABLE</para>
 	</listitem>
       </itemizedlist>
 
       <para>Even though this document tries to describe all important
         steps in a greater detail, it is not intended as a replacement
         for the <application>&oracle;</application> and
 	<application>&sap.r3;</application> installation guides.</para>
 
       <para>Please see the documentation that comes with the
 	<application>&sap.r3;</application>
 	Linux edition for <application>&sap;</application> and
 	<application>&oracle;</application> specific questions, as well
 	as resources from <application>&oracle;</application> and
 	<application>&sap; OSS</application>.</para>
     </sect2>
 
     <sect2 id="software">
       <title>Software</title>
 
       <para>The following CD-ROMs have been used for <application>&sap;</application> installations:</para>
 
       <sect3 id="software-46b">
 	<title>&sap.r3; 4.6B, &oracle; 8.0.5</title>
 
       <informaltable frame="none" pgwide="1">
 	<tgroup cols=3>
 	  <thead>
 	    <row>
 	      <entry>Name</entry> <entry>Number</entry> <entry>Description</entry>
 	    </row>
 	  </thead>
 	  <tbody>
 	    <row>
 	      <entry>KERNEL</entry> <entry>51009113</entry> <entry>SAP Kernel Oracle /
 		Installation / AIX, Linux, Solaris</entry>
 	    </row>
 
 	    <row>
 	      <entry>RDBMS</entry> <entry>51007558</entry> <entry>Oracle / RDBMS 8.0.5.X /
 		Linux</entry>
 	    </row>
 
 	    <row>
 	      <entry>EXPORT1</entry> <entry>51010208</entry> <entry>IDES / DB-Export /
 		Disc 1 of 6</entry>
 	    </row>
 
 	    <row>
 	      <entry>EXPORT2</entry> <entry>51010209</entry> <entry>IDES / DB-Export /
 		Disc 2 of 6</entry>
 	    </row>
 
 	    <row>
 	      <entry>EXPORT3</entry> <entry>51010210</entry> <entry>IDES / DB-Export /
 		Disc 3 of 6</entry>
 	    </row>
    
 	    <row>
 	      <entry>EXPORT4</entry> <entry>51010211</entry> <entry>IDES / DB-Export /
 		Disc 4 of 6</entry>
 	    </row>
 
 	    <row>
 	      <entry>EXPORT5</entry> <entry>51010212</entry> <entry>IDES / DB-Export /
 		Disc 5 of 6</entry>
 	    </row>
 
 	    <row>
 	      <entry>EXPORT6</entry> <entry>51010213</entry> <entry>IDES / DB-Export /
 		Disc 6 of 6</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
 
       <para>Additionally, we used the <application>&oracle; 8
 	Server</application> (Pre-production version 8.0.5 for Linux,
 	Kernel Version 2.0.33) CD which is not really necessary, and
 	FreeBSD 4.3-STABLE (it was only a few days past 4.3
 	RELEASE).</para>
 
       </sect3>
       <sect3 id="software-46c">
 	<title>&sap.r3; 4.6C SR2, &oracle; 8.1.7</title>
 
 	<informaltable frame="none" pgwide="1">
 	  <tgroup cols=3>
 	    <thead>
 	      <row>
 		<entry>Name</entry> <entry>Number</entry> <entry>Description</entry>
 	      </row>
 	    </thead>
 
 	    <tbody>
 	      <row>
 		<entry>KERNEL</entry> <entry>51014004</entry> <entry>SAP Kernel Oracle /
 		  SAP Kernel Version 4.6D / DEC, Linux</entry>
 	      </row>
 
 	      <row>
 		<entry>RDBMS</entry> <entry>51012930</entry> <entry>Oracle 8.1.7/ RDBMS /
 		  Linux</entry>
 	      </row>
 
 	      <row>
 		<entry>EXPORT1</entry> <entry>51013953</entry> <entry>Release 4.6C SR2 / Export
 		  / Disc 1 of 4</entry>
 	      </row>
 
 	      <row>
 		<entry>EXPORT1</entry> <entry>51013953</entry> <entry>Release 4.6C SR2 / Export
 		  / Disc 2 of 4</entry>
 	      </row>
 
 	      <row>
 		<entry>EXPORT1</entry> <entry>51013953</entry> <entry>Release 4.6C SR2 / Export
 		  / Disc 3 of 4</entry>
 	      </row>
 
 	      <row>
 		<entry>EXPORT1</entry> <entry>51013953</entry> <entry>Release 4.6C SR2 / Export
 		  / Disc 4 of 4</entry>
 	      </row>
 
 	      <row>
 		<entry>LANG1</entry> <entry>51013954</entry> <entry>Release 4.6C SR2 /
 		  Language / DE, EN, FR / Disc 1 of 3</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</informaltable>
 
         <para>Depending on the languages you would like to install, additional
 	  language CDs might be necessary. Here we are just using DE and EN, so
 	  the first language CD is the only one needed. As a little note, the
 	  numbers for all four EXPORT CDs are identical. All three language CDs
 	  also have the same number (this is different from the 4.6B IDES
 	  release CD numbering). At the time of writing this installation is
 	  running on FreeBSD 4.5-STABLE (20.03.2002).</para>
       </sect3>
     </sect2>
 
     <sect2 id="sap-notes">
       <title>&sap; Notes</title>
 
       <para>The following notes should be read before installing
 	<application>&sap.r3;</application> and proved to be useful
 	during installation:</para>
 
       <sect3 id="sap-notes-46b">
 	<title>&sap.r3; 4.6B, &oracle; 8.0.5</title>
 
 	<informaltable frame="none" pgwide="1">
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Number</entry>
 		<entry>Title</entry>
 	      </row>
 	    </thead>
 	    <tbody>
 
 	      <row>
 		<entry>0171356</entry> <entry>SAP Software on Linux: Essential
 		  Comments</entry>
 	      </row>
 
 	      <row>
 		<entry>0201147</entry> <entry>INST: 4.6C R/3 Inst. on UNIX -
 		  Oracle</entry>
 	      </row>
 
 	      <row>
 		<entry>0373203</entry> <entry>Update / Migration Oracle 8.0.5 --&gt;
 		  8.0.6/8.1.6 LINUX</entry>
 	      </row>
 
 	      <row>
 		<entry>0072984</entry> <entry>Release of Digital UNIX 4.0B for
 		  Oracle</entry>
 	      </row>
 
 	      <row>
 		<entry>0130581</entry> <entry>R3SETUP step DIPGNTAB terminates</entry>
 	      </row>
 
 	      <row>
 		<entry>0144978</entry> <entry>Your system has not been installed
 		  correctly</entry>
 	      </row>
 
 	      <row>
 		<entry>0162266</entry> <entry>Questions and tips for R3SETUP on Windows
 		  NT / W2K</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</informaltable>
       </sect3>
 
       <sect3 id="sap-notes-46c">
 	<title>&sap.r3; 4.6C, &oracle; 8.1.7</title>
 
 	<informaltable frame="none" pgwide="1">
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Number</entry>
 		<entry>Title</entry>
 	      </row>
 	    </thead>
 	    <tbody>
 	      <row>
 		<entry>0015023</entry> <entry>Initializing table TCPDB (RSXP0004)
 		  (EBCDIC)</entry>
 	      </row>
 
 	      <row>
 		<entry>0045619</entry> <entry>R/3 with several languages or
 		  typefaces</entry>
 	      </row>
 
 	      <row>
 		<entry>0171356</entry> <entry>SAP Software on Linux: Essential
 		  Comments</entry>
 	      </row>
 
 	      <row>
 		<entry>0195603</entry> <entry>RedHat 6.1 Enterprise version:
 		  Known problems</entry>
 	      </row>
 
 	      <row>
 		<entry>0212876</entry> <entry>The new archiving tool SAPCAR</entry>
 	      </row>
 
 	      <row>
 		<entry>0300900</entry> <entry>Linux: Released DELL Hardware</entry>
 	      </row>
 
 	      <row>
 		<entry>0377187</entry> <entry>RedHat 6.2: important remarks</entry>
 	      </row>
 
 	      <row>
 		<entry>0387074</entry> <entry>INST: R/3 4.6C SR2 Installation on
 		  UNIX</entry>
 	      </row>
 
 	      <row>
 		<entry>0387077</entry> <entry>INST: R/3 4.6C SR2 Inst. on UNIX -
 		  Oracle</entry>
 	      </row>
 
 	      <row>
 		<entry>0387078</entry> <entry>SAP Software on UNIX: OS Dependencies
 		  4.6C SR2</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</informaltable>
       </sect3>
     </sect2>
 
     <sect2 id="hardware-requirements">
       <title>Hardware Requirements</title>
 
       <para>The following equipment is sufficient for the installation
 	of a <application>&sap.r3; System</application>. For production
 	use, a more exact sizing is of course needed:</para>
 
       <informaltable frame="none" pgwide="1">
 	<tgroup cols="3">
 	  <thead>
 	    <row>
 	      <entry>Component</entry>
 	      <entry>4.6B</entry>
 	      <entry>4.6C</entry>
 	    </row>
 	  </thead>
 	  <tbody>
 	    <row>
 	      <entry>Processor</entry>
 	      <entry>2 x 800MHz &pentium; III</entry>
 	      <entry>2 x 800MHz &pentium; III</entry>
 	    </row>
 
 	    <row>
 	      <entry>Memory</entry>
 	      <entry>1GB ECC</entry>
 	      <entry>2GB ECC</entry>
 	    </row>
 
 	    <row>
 	      <entry>Hard Disk Space</entry>
 	      <entry>50-60GB (IDES)</entry>
 	      <entry>50-60GB (IDES)</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
 
       <para>For use in production, &xeon; Processors with large cache,
 	high-speed disk access (SCSI, RAID hardware controller), USV
 	and ECC-RAM is recommended.  The large amount of hard disk
 	space is due to the preconfigured IDES System, which creates
 	27&nbsp;GB of database files during installation. This space is
 	also sufficient for initial production systems and application
 	data.</para>
 
       <sect3 id="hardware-46b">
 	<title>&sap.r3; 4.6B, &oracle; 8.0.5</title>
 
       <para>The following off-the-shelf hardware was used: a dual processor
 	board with 2 800&nbsp;MHz &pentium;&nbsp;III processors, &adaptec; 29160 Ultra160
 	SCSI adapter (for accessing a 40/80&nbsp;GB DLT tape drive and CDROM),
 	&mylex; &acceleraid; (2 channels, firmware 6.00-1-00 with 32&nbsp;MB RAM).
 	To the &mylex; RAID controller are attached two 17&nbsp;GB hard disks
 	(mirrored) and four 36&nbsp;GB hard disks (RAID level 5).</para>
       </sect3>
 
       <sect3 id="hardware-46c">
 	<title>&sap.r3; 4.6C, &oracle; 8.1.7</title>
 
       <para>For this installation a &dell; &poweredge; 2500 was used: a
 	dual processor board with two 1000&nbsp;MHz &pentium;&nbsp;III processors
 	(256&nbsp;kB Cache), 2&nbsp;GB PC133 ECC SDRAM, PERC/3 DC PCI RAID Controller
 	with 128&nbsp;MB, and an EIDE DVD-ROM drive. To the RAID controller are
 	attached two 18&nbsp;GB hard disks (mirrored) and four 36&nbsp;GB hard disks
 	(RAID level 5).</para>
       </sect3>
     </sect2>
 
     <sect2 id="installation">
       <title>Installation of FreeBSD</title>
 
       <para>First you have to install FreeBSD. There are several ways to do
 	this (FreeBSD&nbsp;4.3 was installed via FTP, FreeBSD&nbsp;4.5 directly from
 	the RELEASE CD) for more information read the <xref
 	linkend="install-diff-media">.</para>
 
       <sect3 id="disk-layout">
 	<title>Disk Layout</title>
 
 	<para>To keep it simple, the same disk layout both for the
 	  <application>&sap.r3; 46B</application> and <application>&sap.r3; 46C
 	  SR2</application> installation was used. Only the device names
 	  changed, as the installations were on different hardware (<filename>/dev/da</filename>
 	  and <filename>/dev/amr</filename> respectively, so if using an AMI &megaraid;, one will see
 	  <filename>/dev/amr0s1a</filename> instead of <filename>/dev/da0s1a</filename>):</para>
 
 	<informaltable frame="none" pgwide="1">
 	  <tgroup cols="4">
 	    <thead>
 	      <row>
 		<entry>File system</entry>
 		<entry>Size (1k-blocks)</entry>
 		<entry>Size (GB)</entry>
 		<entry>Mounted on</entry>
 	      </row>
 	    </thead>
 	    <tbody>
 	      <row>
 		<entry><filename>/dev/da0s1a</filename></entry>
 		<entry>1.016.303</entry>
 		<entry>1</entry>
 		<entry><filename>/</filename></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>/dev/da0s1b</filename></entry>
 		<entry> </entry>
 		<entry>6</entry>
 		<entry>swap</entry>
 	      </row>
 
 	      <row>
 		<entry><filename>/dev/da0s1e</filename></entry>
 		<entry>2.032.623</entry>
 		<entry>2</entry>
 		<entry><filename>/var</filename></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>/dev/da0s1f</filename></entry>
 		<entry>8.205.339</entry>
 		<entry>8</entry>
 		<entry><filename>/usr</filename></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>/dev/da1s1e</filename></entry>
 		<entry>45.734.361</entry>
 		<entry>45</entry>
 		<entry><filename>/compat/linux/oracle</filename></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>/dev/da1s1f</filename></entry>
 		<entry>2.032.623</entry>
 		<entry>2</entry>
 		<entry><filename>/compat/linux/sapmnt</filename></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>/dev/da1s1g</filename></entry>
 		<entry>2.032.623</entry>
 		<entry>2</entry>
 		<entry><filename>/compat/linux/usr/sap</filename></entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</informaltable>
 
 	<para>Configure and initialize the two logical drives
 	  with the &mylex; or PERC/3 RAID software beforehand.
 	  The software can be started during the
 	  <acronym>BIOS</acronym> boot phase.</para>
 
 	<para> Please note that this disk layout differs slightly from
 	  the &sap; recommendations, as &sap; suggests mounting the
 	  <application>&oracle;</application> subdirectories (and some others) separately &mdash; we
 	  decided to just create them as real subdirectories for
 	  simplicity.</para>
       </sect3>
 
       <sect3 id="makeworldandnewkernel">
 	<title><command>make world</command> and a New Kernel</title>
 
 	<para>Download the latest -STABLE sources. Rebuild world and your
 	  custom kernel after configuring your kernel configuration file.
 	  Here you should also include the
 	  <link linkend="kerneltuning">kernel parameters</link>
 	  which are required for both <application>&sap.r3;</application>
 	  and <application>&oracle;</application>.</para>
       </sect3>
     </sect2>
 
     <sect2 id="installingthelinuxenviornment">
       <title>Installing the Linux Environment</title>
 
       <sect3 id="installinglinuxbase-system">
 	<title>Installing the Linux Base System</title>
 
 	<para>First the <link linkend="linuxemu-libs-port">linux_base</link>
 	  port needs to be installed (as <username>root</username>):</para>
 
 	<screen>&prompt.root; <userinput>cd /usr/ports/emulators/linux_base</userinput>
 &prompt.root; <userinput>make install distclean</userinput></screen>
 
       </sect3>
 
 
       <sect3 id="installinglinuxdevelopment">
 	<title>Installing Linux Development Environment</title>
 
 	<para>The Linux development environment is needed, if you want to install
 	  <application>&oracle;</application> on FreeBSD according to the
 	  <xref linkend="linuxemu-oracle">:</para>
 
 	<screen>&prompt.root; <userinput>cd /usr/ports/devel/linux_devtools</userinput>
 &prompt.root; <userinput>make install distclean</userinput></screen>
 
 	<para>The Linux development environment has only been installed for the <application>&sap.r3;
 	  46B IDES</application> installation. It is not needed, if
 	  the <application>&oracle; DB</application> is not relinked on the
 	  FreeBSD system. This is the case if you are using the
 	  <application>&oracle;</application> tarball from a Linux system.</para>
 
       </sect3>
 
 
       <sect3 id="installingnecessaryrpms">
 	<title>Installing the Necessary RPMs</title>
 	<indexterm><primary>RPMs</primary></indexterm>
 
 	<para>To start the <command>R3SETUP</command> program, PAM support is needed.
 	  During the first <application>&sap;</application> Installation on FreeBSD 4.3-STABLE we
 	  tried to install PAM with all the required packages and
 	  finally forced the installation of the PAM package, which
 	  worked. For <application>&sap.r3; 4.6C SR2</application> we
 	  directly forced the installation of the PAM RPM, which also
 	  works, so it seems the dependent packages are not needed:</para>
 
 
 <screen>&prompt.root; <userinput>rpm -i --ignoreos --nodeps --root /compat/linux --dbpath /var/lib/rpm \
 pam-0.68-7.i386.rpm</userinput></screen>
 
 	<para>For <application>&oracle; 8.0.5</application> to run the
 	  intelligent agent, we also had to install the RedHat Tcl package
 	  <filename>tcl-8.0.5-30.i386.rpm</filename> (otherwise the
 	  relinking during <application>&oracle;</application> installation
 	  will not work).  There are some other issues regarding
 	  relinking of <application>&oracle;</application>, but that is
 	  a <application>&oracle;</application> Linux issue, not FreeBSD specific.</para>
 
       </sect3>
 
       <sect3 id="linuxprocandfallbackelfbrand">
 	<title>Some Additional Hints</title>
 
 	<para>It might also be a good idea to add <literal>linprocfs</literal>
 	  to <filename>/etc/fstab</filename>, for more information, see the &man.linprocfs.5; manual page.
 	  Another parameter to set is <literal>kern.fallback_elf_brand=3</literal>
 	  which is done in the file <filename>/etc/sysctl.conf</filename>.</para>
       </sect3>
     </sect2>
 
     <sect2 id="creatingsapr3env">
       <title>Creating the &sap.r3; Environment</title>
 
       <sect3 id="filesystemsandmountpoints">
 	<title>Creating the Necessary File Systems and Mountpoints</title>
 
 	<para>For a simple installation, it is sufficient to create the
           following file systems:</para>
 
 	<informaltable frame="none" pgwide="1">
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>mount point</entry>
 		<entry>size in GB</entry>
 	      </row>
 	    </thead>
 	    <tbody>
 	      <row>
 		<entry><filename>/compat/linux/oracle</filename></entry>
 		<entry>45 GB</entry>
 	      </row>
 
 	      <row>
 		<entry><filename>/compat/linux/sapmnt</filename></entry>
 		<entry>2 GB</entry>
 	      </row>
 
 	      <row>
 		<entry><filename>/compat/linux/usr/sap</filename></entry>
 		<entry>2 GB</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</informaltable>
 
 	<para>It is also necessary to created some links. Otherwise
 	  the <application>&sap;</application> Installer will complain, as it is checking the
 	  created links:</para>
 
 	<screen>&prompt.root; <userinput>ln -s /compat/linux/oracle /oracle</userinput>
 &prompt.root; <userinput>ln -s /compat/linux/sapmnt /sapmnt</userinput>
 &prompt.root; <userinput>ln -s /compat/linux/usr/sap /usr/sap</userinput></screen>
 
 	<para>Possible error message during installation (here with
 	  System <emphasis>PRD</emphasis> and the
 	  <application>&sap.r3; 4.6C SR2</application>
 	  installation):</para>
 
 	<screen>INFO 2002-03-19 16:45:36 R3LINKS_IND_IND SyLinkCreate:200
     Checking existence of symbolic link /usr/sap/PRD/SYS/exe/dbg to
     /sapmnt/PRD/exe. Creating if it does not exist...
 
 WARNING 2002-03-19 16:45:36 R3LINKS_IND_IND SyLinkCreate:400
     Link /usr/sap/PRD/SYS/exe/dbg exists but it points to file
     /compat/linux/sapmnt/PRD/exe instead of /sapmnt/PRD/exe. The
     program cannot go on as long as this link exists at this
     location. Move the link to another location.
 
 ERROR 2002-03-19 16:45:36 R3LINKS_IND_IND Ins_SetupLinks:0
     can not setup link '/usr/sap/PRD/SYS/exe/dbg' with content
     '/sapmnt/PRD/exe'</screen>
       </sect3>
 
       <sect3 id="creatingusersanddirectories">
 	<title>Creating Users and Directories</title>
 
 	<para><application>&sap.r3;</application> needs two users and
 	  three groups. The user names depend on the
 	  <application>&sap;</application> system ID (SID) which consists
 	  of three letters. Some of these SIDs are reserved
 	  by <application>&sap;</application> (for example
 	  <literal>SAP</literal> and <literal>NIX</literal>. For a
 	  complete list please see the <application>&sap;</application> documentation).  For the IDES
 	  installation we used <literal>IDS</literal>, for the
 	  4.6C SR2 installation <literal>PRD</literal>, as that system
 	  is intended for production use.  We have
 	  therefore the following groups (group IDs might differ, these
 	  are just the values we used with our installation):</para>
 
         <informaltable frame="none" pgwide="1">
           <tgroup cols="3">
           <thead>
           <row>
             <entry>group ID</entry>
             <entry>group name</entry>
             <entry>description</entry>
           </row>
           </thead>
           <tbody>
           <row>
             <entry>100</entry>
             <entry>dba</entry>
             <entry>Data Base Administrator</entry>
           </row>
           <row>
             <entry>101</entry>
             <entry>sapsys</entry>
             <entry>&sap; System</entry>
           </row>
           <row>
             <entry>102</entry>
             <entry>oper</entry>
             <entry>Data Base Operator</entry>
           </row>
           </tbody>
           </tgroup>
         </informaltable>
 
         <para>For a default <application>&oracle;</application> installation, only group
           <groupname>dba</groupname> is used. As
           <groupname>oper</groupname> group, one also uses group
           <groupname>dba</groupname> (see <application>&oracle;</application> and
           <application>&sap;</application> documentation for further information).</para>
 
         <para>We also need the following users:</para>
 
         <informaltable frame="none" pgwide="1">
           <tgroup cols="6">
           <thead>
           <row>
             <entry>user ID</entry>
             <entry>user name</entry>
             <entry>generic name</entry>
             <entry>group</entry>
             <entry>additional groups</entry>
             <entry>description</entry>
           </row>
           </thead>
           <tbody>
           <row>
             <entry>1000</entry>
             <entry>idsadm/prdadm</entry>
             <entry><replaceable>sid</replaceable>adm</entry>
             <entry>sapsys</entry>
             <entry>oper</entry>
             <entry>&sap; Administrator</entry>
           </row>
           <row>
             <entry>1002</entry>
             <entry>oraids/oraprd</entry>
             <entry>ora<replaceable>sid</replaceable></entry>
             <entry>dba</entry>
             <entry>oper</entry>
             <entry>&oracle; Administrator</entry>
           </row>
           </tbody>
           </tgroup>
         </informaltable>
 
         <para>Adding the users with &man.adduser.8;
           requires the following (please note shell and home
           directory) entries for <quote>&sap; Administrator</quote>:</para>
 
         <programlisting>Name: <replaceable>sid</replaceable>adm
 Password: ******
 Fullname: SAP Administrator <replaceable>SID</replaceable>
 Uid: 1000
 Gid: 101 (sapsys)
 Class:
 Groups: sapsys dba
 HOME: /home/<replaceable>sid</replaceable>adm
 Shell: bash  (/compat/linux/bin/bash)</programlisting>
 
         <para>and for <quote>&oracle; Administrator</quote>:</para>
 
         <programlisting>Name: ora<replaceable>sid</replaceable> 
 Password: ****** 
 Fullname: Oracle Administrator <replaceable>SID</replaceable>
 Uid: 1002 
 Gid: 100 (dba) 
 Class: 
 Groups: dba 
 HOME: /oracle/<replaceable>sid</replaceable> 
 Shell: bash  (/compat/linux/bin/bash)</programlisting>
 
         <para>This should also include group
           <groupname>oper</groupname> in case you are using both
           groups <groupname>dba</groupname> and
           <groupname>oper</groupname>.</para>
 
       </sect3>
 
       <sect3 id="creatingdirectories">
         <title>Creating Directories</title>
 
         <para>These directories are usually created as separate
           file systems.  This depends entirely on your requirements.  We
           choose to create them as simple directories, as they are all
           located on the same RAID 5 anyway:</para>
 
         <para>First we will set owners and rights of some directories (as
           user <username>root</username>):</para>
 
         <screen>&prompt.root; <userinput>chmod 775 /oracle</userinput>
 &prompt.root; <userinput>chmod 777 /sapmnt</userinput>
 &prompt.root; <userinput>chown root:dba /oracle</userinput>
 &prompt.root; <userinput>chown <replaceable>sid</replaceable>adm:sapsys /compat/linux/usr/sap</userinput>
 &prompt.root; <userinput>chmod 775 /compat/linux/usr/sap</userinput></screen>
 
         <para>Second we will create directories as user 
 	  <username>ora<replaceable>sid</replaceable></username>. These
           will all be subdirectories of 
 	  <filename>/oracle/<replaceable>SID</replaceable></filename>:</para>
 
         <screen>&prompt.root; <userinput>su - ora<replaceable>sid</replaceable></userinput>
 &prompt.root; <userinput>cd /oracle/<replaceable>SID</replaceable></userinput>
 &prompt.root; <userinput>mkdir mirrlogA mirrlogB origlogA origlogB</userinput>
 &prompt.root; <userinput>mkdir sapdata1 sapdata2 sapdata3 sapdata4 sapdata5 sapdata6</userinput>
 &prompt.root; <userinput>mkdir saparch sapreorg</userinput>
 &prompt.root; <userinput>exit</userinput></screen>
 
 	<para>For the <application>&oracle; 8.1.7</application> installation
 	  some additional directories are needed:</para>
 
 	<screen>&prompt.root; <userinput>su - ora<replaceable>sid</replaceable></userinput>
 &prompt.root; <userinput>cd /oracle</userinput>
 &prompt.root; <userinput>mkdir 805_32</userinput>
 &prompt.root; <userinput>mkdir client stage</userinput>
 &prompt.root; <userinput>mkdir client/80x_32</userinput>
 &prompt.root; <userinput>mkdir stage/817_32</userinput>
 &prompt.root; <userinput>cd /oracle/<replaceable>SID</replaceable></userinput>
 &prompt.root; <userinput>mkdir 817_32</userinput></screen>
 
 	<note><para>The directory <filename>client/80x_32</filename> is used
 	  with exactly this name. Do not replace the <emphasis>x</emphasis>
 	  with some number or anything.</para></note>
 
         <para>In the third step we create directories as user 
 	  <username><replaceable>sid</replaceable>adm</username>:</para>
 
         <screen>&prompt.root; <userinput>su - <replaceable>sid</replaceable>adm</userinput>
 &prompt.root; <userinput>cd /usr/sap</userinput>
 &prompt.root; <userinput>mkdir <replaceable>SID</replaceable></userinput>
 &prompt.root; <userinput>mkdir trans</userinput>
 &prompt.root; <userinput>exit</userinput></screen>
       </sect3>
 
       <sect3 id="entriesinslashetcslashservices">
         <title>Entries in <filename>/etc/services</filename></title>
 
         <para><application>&sap.r3;</application> requires some entries in file
           <filename>/etc/services</filename>, which will not be set
           correctly during installation under FreeBSD.  Please add the
           following entries (you need at least those entries
           corresponding to the instance number &mdash; in this case,
           <literal>00</literal>.  It will do no harm adding all
           entries from <literal>00</literal> to
           <literal>99</literal> for <literal>dp</literal>,
           <literal>gw</literal>, <literal>sp</literal> and
           <literal>ms</literal>). If you are going to use a <application>SAProuter</application>
 	  or need to access <application>&sap;</application> OSS, you also need <literal>99</literal>,
 	  as port 3299 is usually used for the <application>SAProuter</application> process on the
 	  target system:</para>
 
         <programlisting>
 sapdp00    3200/tcp # SAP Dispatcher.      3200 + Instance-Number
 sapgw00  3300/tcp # SAP Gateway.         3300 + Instance-Number
 sapsp00  3400/tcp #                      3400 + Instance-Number
 sapms00  3500/tcp #                      3500 + Instance-Number
 sapms<replaceable>SID</replaceable> 3600/tcp # SAP Message Server.  3600 + Instance-Number
 sapgw00s   4800/tcp # SAP Secure Gateway   4800 + Instance-Number</programlisting>
       </sect3>
 
       <sect3 id="necessarylocales">
         <title>Necessary Locales</title>
 	<indexterm><primary>locale</primary></indexterm>
 
         <para><application>&sap;</application> requires at least two locales that are not part of
           the default RedHat installation. &sap; offers the required
           RPMs as download from their FTP server (which is only
           accessible if you are a customer with OSS access).  See note
           0171356 for a list of RPMs you need.</para>
 
         <para>It is also possible to just create appropriate links
           (for example from <emphasis>de_DE</emphasis> and
           <emphasis>en_US</emphasis> ), but we would not recommend this
           for a production system (so far it worked with the IDES
           system without any problems, though).  The following locales
           are needed:</para>
 
         <programlisting>de_DE.ISO-8859-1
 en_US.ISO-8859-1</programlisting>
 
 	<para>Create the links like this:</para>
 
 	<screen>&prompt.root; <userinput>cd /compat/linux/usr/share/locale</userinput>
 &prompt.root; <userinput>ln -s de_DE de_DE.ISO-8859-1</userinput>
 &prompt.root; <userinput>ln -s en_US en_US.ISO-8859-1</userinput></screen>
 
         <para>If they are not present, there will be some problems
           during the installation.  If these are then subsequently
           ignored (by setting the <literal>STATUS</literal> of the offending steps to
           <literal>OK</literal> in file <filename>CENTRDB.R3S</filename>), it will be impossible to log onto
           the <application>&sap;</application> system without some additional effort.</para>
       </sect3>
 
       <sect3 id="kerneltuning">
         <title>Kernel Tuning</title>
 	<indexterm><primary>kernel tuning</primary></indexterm>
 
         <para><application>&sap.r3;</application> systems need a lot of resources.  We therefore
         added the following parameters to the kernel configuration file:</para>
 
         <programlisting># Set these for memory pigs (SAP and Oracle):
 options MAXDSIZ="(1024*1024*1024)"
 options DFLDSIZ="(1024*1024*1024)"
 # System V options needed.
 options SYSVSHM #SYSV-style shared memory
 options SHMMAXPGS=262144 #max amount of shared mem. pages
 #options SHMMAXPGS=393216 #use this for the 46C inst.parameters
 options SHMMNI=256 #max number of shared memory ident if.
 options SHMSEG=100 #max shared mem.segs per process
 options SYSVMSG #SYSV-style message queues 
 options MSGSEG=32767 #max num. of mes.segments in system 
 options MSGSSZ=32 #size of msg-seg. MUST be power of 2
 options MSGMNB=65535 #max char. per message queue
 options MSGTQL=2046 #max amount of msgs in system
 options SYSVSEM #SYSV-style semaphores 
 options SEMMNU=256 #number of semaphore UNDO structures
 options SEMMNS=1024 #number of semaphores in system
 options SEMMNI=520 #number of semaphore identifiers
 options SEMUME=100       #number of UNDO keys</programlisting>
 
         <para>The minimum values are specified in the documentation that
           comes from &sap;.  As there is no description for Linux, see the
           HP-UX section (32-bit) for further information. As the system
 	  for the 4.6C SR2 installation has more main memory, the shared
 	  segments can be larger both for <application>&sap;</application>
 	  and <application>&oracle;</application>, therefore choose a larger
 	  number of shared memory pages.</para>
 
 	<note><para>With the default installation of FreeBSD&nbsp;4.5 on &i386;,
 	  leave <literal>MAXDSIZ</literal> and <literal>DFLDSIZ</literal> at 1&nbsp;GB maximum. Otherwise, strange 
 	  errors like <errorname>ORA-27102: out of memory</errorname> and 
           <errorname>Linux Error: 12: Cannot allocate memory</errorname>
           might happen.</para></note>
       </sect3>
     </sect2>
 
     <sect2 id="installingsapr3">
       <title>Installing &sap.r3;</title>
 
       <sect3 id="preparingsapcdroms">
         <title>Preparing &sap; CDROMs</title>
 
         <para>There are many CDROMs to mount and unmount during the
           installation.  Assuming you have enough CDROM drives, you
           can just mount them all.  We decided to copy the CDROMs
           contents to corresponding directories:</para>
 
 	<programlisting>/oracle/<replaceable>SID</replaceable>/sapreorg/<replaceable>cd-name</replaceable></programlisting>
 
         <para>where <replaceable>cd-name</replaceable> was one of <filename>KERNEL</filename>, 
 	  <filename>RDBMS</filename>, <filename>EXPORT1</filename>,
 	  <filename>EXPORT2</filename>, <filename>EXPORT3</filename>,
 	  <filename>EXPORT4</filename>, <filename>EXPORT5</filename> and 
 	  <filename>EXPORT6</filename> for the 4.6B/IDES installation, and
 	  <filename>KERNEL</filename>, <filename>RDBMS</filename>,
 	  <filename>DISK1</filename>, <filename>DISK2</filename>,
 	  <filename>DISK3</filename>, <filename>DISK4</filename> and
 	  <filename>LANG</filename> for the 4.6C SR2 installation. All the
 	  filenames on the mounted CDs should be in capital letters,
 	  otherwise use the <option>-g</option> option for mounting. So use the following
 	  commands:</para>
 
         <screen>&prompt.root; <userinput>mount_cd9660 -g /dev/cd0a /mnt</userinput>
 &prompt.root; <userinput>cp -R /mnt/* /oracle/<replaceable>SID</replaceable>/sapreorg/<replaceable>cd-name</replaceable></userinput>
 &prompt.root; <userinput>umount /mnt</userinput></screen>
       </sect3>
 
       <sect3 id="runningtheinstall-script">
         <title>Running the Installation Script</title>
 
 	<para>First you have to prepare an <filename class="directory">install</filename> directory:</para>
 
 	<screen>&prompt.root; <userinput>cd /oracle/<replaceable>SID</replaceable>/sapreorg</userinput>
 &prompt.root; <userinput>mkdir install</userinput>
 &prompt.root; <userinput>cd install</userinput></screen>
 
         <para>Then the installation script is started, which will copy nearly
           all the relevant files into the <filename class="directory">install</filename> directory:</para>
 
 	<screen>&prompt.root; <userinput>/oracle/<replaceable>SID</replaceable>/sapreorg/KERNEL/UNIX/INSTTOOL.SH</userinput></screen>
 
 	<para>The IDES installation (4.6B) comes with a fully customized
 	  &sap.r3; demonstration system, so there are six instead of just three
           EXPORT CDs.  At this point the installation template
 	  <filename>CENTRDB.R3S</filename> is for installing a standard
 	  central instance (<application>&r3;</application> and database), not the IDES central
 	  instance, so one needs to copy the corresponding <filename>CENTRDB.R3S</filename>
 	  from the <filename class="directory">EXPORT1</filename> directory, otherwise <command>R3SETUP</command> will only ask
 	  for three EXPORT CDs.</para>
 
 	<para>The newer <application>&sap; 4.6C SR2</application> release
 	  comes with four EXPORT CDs. The parameter file that controls
 	  the installation steps is <filename>CENTRAL.R3S</filename>.
 	  Contrary to earlier releases there are no separate installation
 	  templates for a central instance with or without database.
 	  <application>&sap;</application> is using a separate template for database installation. To restart
 	  the installation later it is however sufficient to restart with
 	  the original file.</para>
 
 	<para>During and after installation, <application>&sap;</application> requires
 	  <command>hostname</command> to return the computer name
 	  only, not the fully qualified domain name. So either
 	  set the hostname accordingly, or set an alias with
 	  <command>alias hostname='hostname -s'</command> for
 	  both <username>ora<replaceable>sid</replaceable></username> and 
 	  <username><replaceable>sid</replaceable>adm</username> (and for
 	  <username>root</username> at least during installation
 	  steps performed as <username>root</username>). It is also 
 	  possible to adjust the installed <filename>.profile</filename> and <filename>.login</filename> files of
 	  both users that are installed during 
 	  <application>&sap;</application> installation.</para>
       </sect3>
 
       <sect3 id="startr3setup-46B">
         <title>Start <command>R3SETUP</command> 4.6B</title>
 
         <para>Make sure <envar>LD_LIBRARY_PATH</envar> is set correctly:</para>
 
         <screen>&prompt.root; <userinput>export LD_LIBRARY_PATH=/oracle/IDS/lib:/sapmnt/IDS/exe:/oracle/805_32/lib</userinput></screen>
 
         <para>Start <command>R3SETUP</command> as <username>root</username> from 
 	  installation directory:</para>
 
         <screen>&prompt.root; <userinput>cd /oracle/IDS/sapreorg/install</userinput>
 &prompt.root; <userinput>./R3SETUP -f CENTRDB.R3S</userinput></screen>
 
         <para>The script then asks some questions (defaults in brackets,
         followed by actual input):</para>
 
         <informaltable frame="none" pgwide="1">
           <tgroup cols="3">
           <thead>
           <row>
             <entry>Question</entry>
             <entry>Default</entry>
             <entry>Input</entry>
           </row>
           </thead>
           <tbody>
           <row>
             <entry>Enter SAP System ID</entry>
             <entry>[C11]</entry>
             <entry>IDS<keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Enter SAP Instance Number</entry>
             <entry>[00]</entry>
             <entry><keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Enter SAPMOUNT Directory</entry>
             <entry>[/sapmnt]</entry>
             <entry><keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Enter name of SAP central host</entry>
             <entry>[troubadix.domain.de]</entry>
             <entry><keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Enter name of SAP db host</entry>
             <entry>[troubadix]</entry>
             <entry><keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Select character set</entry>
             <entry>[1] (WE8DEC)</entry>
             <entry><keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Enter Oracle server version (1) Oracle 8.0.5, (2) Oracle 8.0.6, (3) Oracle 8.1.5, (4) Oracle 8.1.6</entry>
             <entry> </entry>
             <entry>1<keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Extract Oracle Client archive</entry>
             <entry>[1] (Yes, extract)</entry>
             <entry><keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Enter path to KERNEL CD</entry>
             <entry>[/sapcd]</entry>
             <entry>/oracle/IDS/sapreorg/KERNEL</entry>
           </row>
           <row>
             <entry>Enter path to RDBMS CD</entry>
             <entry>[/sapcd]</entry>
             <entry>/oracle/IDS/sapreorg/RDBMS</entry>
           </row>
           <row>
             <entry>Enter path to EXPORT1 CD</entry>
             <entry>[/sapcd]</entry>
             <entry>/oracle/IDS/sapreorg/EXPORT1</entry>
           </row>
           <row>
             <entry>Directory to copy EXPORT1 CD</entry>
             <entry>[/oracle/IDS/sapreorg/CD4_DIR]</entry>
             <entry><keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Enter path to EXPORT2 CD</entry>
             <entry>[/sapcd]</entry>
             <entry>/oracle/IDS/sapreorg/EXPORT2</entry>
           </row>
           <row>
             <entry>Directory to copy EXPORT2 CD</entry>
             <entry>[/oracle/IDS/sapreorg/CD5_DIR]</entry>
             <entry><keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Enter path to EXPORT3 CD</entry>
             <entry>[/sapcd]</entry>
             <entry>/oracle/IDS/sapreorg/EXPORT3</entry>
           </row>
           <row>
             <entry>Directory to copy EXPORT3 CD</entry>
             <entry>[/oracle/IDS/sapreorg/CD6_DIR]</entry>
             <entry><keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Enter path to EXPORT4 CD</entry>
             <entry>[/sapcd]</entry>
             <entry>/oracle/IDS/sapreorg/EXPORT4</entry>
           </row>
           <row>
             <entry>Directory to copy EXPORT4 CD</entry>
             <entry>[/oracle/IDS/sapreorg/CD7_DIR]</entry>
             <entry><keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Enter path to EXPORT5 CD</entry>
             <entry>[/sapcd]</entry>
             <entry>/oracle/IDS/sapreorg/EXPORT5</entry>
           </row>
           <row>
             <entry>Directory to copy EXPORT5 CD</entry>
             <entry>[/oracle/IDS/sapreorg/CD8_DIR]</entry>
             <entry><keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Enter path to EXPORT6 CD</entry>
             <entry>[/sapcd]</entry>
             <entry>/oracle/IDS/sapreorg/EXPORT6</entry>
           </row>
           <row>
             <entry>Directory to copy EXPORT6 CD</entry>
             <entry>[/oracle/IDS/sapreorg/CD9_DIR]</entry>
             <entry><keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Enter amount of RAM for SAP + DB</entry>
             <entry> </entry>
             <entry>850<keycap>Enter</keycap> (in Megabytes)</entry>
           </row>
           <row>
             <entry>Service Entry Message Server</entry>
             <entry>[3600]</entry>
             <entry><keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Enter Group-ID of sapsys</entry>
             <entry>[101]</entry>
             <entry><keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Enter Group-ID of oper</entry>
             <entry>[102]</entry>
             <entry><keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Enter Group-ID of dba</entry>
             <entry>[100]</entry>
             <entry><keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Enter User-ID of <replaceable>sid</replaceable>adm</entry>
             <entry>[1000]</entry>
             <entry><keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Enter User-ID of ora<replaceable>sid</replaceable></entry>
             <entry>[1002]</entry>
             <entry><keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Number of parallel procs</entry>
             <entry>[2]</entry>
             <entry><keycap>Enter</keycap></entry>
           </row>
           </tbody>
           </tgroup>
         </informaltable>
       
         <para>If you had not copied the CDs to the different locations,
           then the <application>&sap;</application> installer cannot find the CD needed (identified
           by the <filename>LABEL.ASC</filename> file on the CD) and would
           then ask you to insert and mount the CD and confirm or enter
           the mount path.</para>
    
         <para>The <filename>CENTRDB.R3S</filename> might not be
           error free. In our case, it requested EXPORT4 CD again but
           indicated the correct key (6_LOCATION, then 7_LOCATION
           etc.), so one can just continue with entering the correct
           values.</para>
 
         <para>Apart from some problems mentioned below, everything
           should go straight through up to the point where the &oracle;
           database software needs to be installed.</para>
       </sect3>
 
       <sect3 id="startr3setup-46C">
 	<title>Start <command>R3SETUP</command> 4.6C SR2</title>
 
 	<para>Make sure <envar>LD_LIBRARY_PATH</envar> is set correctly. This is a
 	  different value from the 4.6B installation with
 	  <application>&oracle; 8.0.5</application>:</para>
 
 	<screen>&prompt.root; <userinput>export LD_LIBRARY_PATH=/sapmnt/PRD/exe:/oracle/PRD/817_32/lib</userinput></screen>
 
 	<para>Start <command>R3SETUP</command> as user <username>root</username> from installation directory:</para>
 
 	<screen>&prompt.root; <userinput>cd /oracle/PRD/sapreorg/install</userinput>
 &prompt.root; <userinput>./R3SETUP -f CENTRAL.R3S</userinput></screen>
 
 	<para>The script then asks some questions (defaults in brackets,
 	  followed by actual input):</para>
 
 	<informaltable frame="none" pgwide="1">
 	  <tgroup cols="3">
 	  <thead>
 	  <row>
 	    <entry>Question</entry>
 	    <entry>Default</entry>
 	    <entry>Input</entry>
 	  </row>
 	  </thead>
 	  <tbody>
 	  <row>
 	    <entry>Enter SAP System ID</entry>
 	    <entry>[C11]</entry>
 	    <entry>PRD<keycap>Enter</keycap></entry>
 	  </row>
 	  <row>
 	    <entry>Enter SAP Instance Number</entry>
 	    <entry>[00]</entry>
 	    <entry><keycap>Enter</keycap></entry>
 	  </row>
 	  <row>
 	    <entry>Enter SAPMOUNT Directory</entry>
 	    <entry>[/sapmnt]</entry>
 	    <entry><keycap>Enter</keycap></entry>
 	  </row>
 	  <row>
 	    <entry>Enter name of SAP central host</entry>
 	    <entry>[majestix]</entry>
 	    <entry><keycap>Enter</keycap></entry>
 	  </row>
 	  <row>
 	    <entry>Enter Database System ID</entry>
 	    <entry>[PRD]</entry>
 	    <entry>PRD<keycap>Enter</keycap></entry>
 	  </row>
 	  <row>
 	    <entry>Enter name of SAP db host</entry>
 	    <entry>[majestix]</entry>
 	    <entry><keycap>Enter</keycap></entry>
 	  </row>
 	  <row>
 	    <entry>Select character set</entry>
 	    <entry>[1] (WE8DEC)</entry>
 	    <entry><keycap>Enter</keycap></entry>
 	  </row>
 	  <row>
 	    <entry>Enter Oracle server version (2) Oracle 8.1.7</entry>
 	    <entry> </entry>
 	    <entry>2<keycap>Enter</keycap></entry>
 	  </row>
 	  <row>
 	    <entry>Extract Oracle Client archive</entry>
 	    <entry>[1] (Yes, extract)</entry>
 	    <entry><keycap>Enter</keycap></entry>
 	  </row>
 	  <row>
 	    <entry>Enter path to KERNEL CD</entry>
 	    <entry>[/sapcd]</entry>
 	    <entry>/oracle/PRD/sapreorg/KERNEL</entry>
 	  </row>
 	  <row>
 	    <entry>Enter amount of RAM for SAP + DB</entry>
 	    <entry>2044</entry>
 	    <entry>1800<keycap>Enter</keycap> (in Megabytes)</entry>
 	  </row>
 	  <row>
 	    <entry>Service Entry Message Server</entry>
 	    <entry>[3600]</entry>
 	    <entry><keycap>Enter</keycap></entry>
 	  </row>
 	  <row>
 	    <entry>Enter Group-ID of sapsys</entry>
 	    <entry>[100]</entry>
 	    <entry><keycap>Enter</keycap></entry>
 	  </row>
 	  <row>
             <entry>Enter Group-ID of oper</entry>
             <entry>[101]</entry>
             <entry><keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Enter Group-ID of dba</entry>
             <entry>[102]</entry>
             <entry><keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Enter User-ID of <username>oraprd</username></entry>
             <entry>[1002]</entry>
             <entry><keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Enter User-ID of <username>prdadm</username></entry>
             <entry>[1000]</entry>
             <entry><keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>LDAP support</entry>
             <entry> </entry>
             <entry>3<keycap>Enter</keycap> (no support)</entry>
           </row>
           <row>
             <entry>Installation step completed</entry>
             <entry>[1] (continue)</entry>
             <entry><keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Choose installation service</entry>
             <entry>[1] (DB inst,file)</entry>
             <entry><keycap>Enter</keycap></entry>
           </row>
           </tbody>
           </tgroup>
         </informaltable>
       
         <para>So far, creation of users gives an error during
 	  installation in phases OSUSERDBSID_IND_ORA (for creating
 	  user <username>ora<replaceable>sid</replaceable></username>) and 
 	  OSUSERSIDADM_IND_ORA (creating user 
 	  <username><replaceable>sid</replaceable>adm</username>).</para>
    
         <para>Apart from some problems mentioned below, everything
           should go straight through up to the point where the &oracle;
           database software needs to be installed.</para>
       </sect3>
     </sect2>
 
     <sect2 id="installingoracle805">
       <title>Installing &oracle; 8.0.5</title>
 
       <para>Please see the corresponding &sap; Notes and &oracle; <filename>Readme</filename>s
         regarding Linux and <application>&oracle; DB</application> for possible problems. Most if
         not all problems stem from incompatible libraries.</para>
 
       <para>For more information on installing <application>&oracle;</application>, refer to <link
 	  linkend="linuxemu-oracle">the Installing &oracle;
 	  chapter.</link></para>
 
 
       <sect3 id="installingtheoracle805withorainst">
         <title>Installing the &oracle; 8.0.5 with <command>orainst</command></title>
 
         <para>If <application>&oracle; 8.0.5</application> is to be
           used, some additional libraries are needed for successfully
           relinking, as <application>&oracle; 8.0.5</application> was linked with an old glibc
           (RedHat 6.0), but RedHat 6.1 already uses a new glibc. So
           you have to install the following additional packages to
           ensure that linking will work:</para>
 
         <para><filename>compat-libs-5.2-2.i386.rpm</filename></para>
         <para><filename>compat-glibc-5.2-2.0.7.2.i386.rpm</filename></para>
         <para><filename>compat-egcs-5.2-1.0.3a.1.i386.rpm</filename></para>
         <para><filename>compat-egcs-c++-5.2-1.0.3a.1.i386.rpm</filename></para>
         <para><filename>compat-binutils-5.2-2.9.1.0.23.1.i386.rpm</filename></para>
 
         <para>See the corresponding &sap; Notes or &oracle; <filename>Readme</filename>s for
           further information.  If this is no option (at the time of
           installation we did not have enough time to check this), one
           could use the original binaries, or use the relinked
           binaries from an original RedHat system.</para>
 
         <para>For compiling the intelligent agent, the RedHat Tcl
           package must be installed.  If you cannot get
           <filename>tcl-8.0.3-20.i386.rpm</filename>, a newer one like
           <filename>tcl-8.0.5-30.i386.rpm</filename> for RedHat 6.1
           should also do.</para>
 
         <para>Apart from relinking, the installation is
           straightforward:</para>
 
         <screen>&prompt.root; <userinput>su - oraids</userinput>
 &prompt.root; <userinput>export TERM=xterm</userinput>
 &prompt.root; <userinput>export ORACLE_TERM=xterm</userinput>
 &prompt.root; <userinput>export ORACLE_HOME=/oracle/IDS</userinput>
 &prompt.root; <userinput>cd $ORACLE_HOME/orainst_sap</userinput>
 &prompt.root; <userinput>./orainst</userinput></screen>
 
         <para>Confirm all screens with <keycap>Enter</keycap> until the software is
           installed, except that one has to deselect the
           <emphasis>&oracle; On-Line Text Viewer</emphasis>, as this is
           not currently available for Linux. <application>&oracle;</application> then wants to
           relink with <command>i386-glibc20-linux-gcc</command>
           instead of the available <command>gcc</command>,
           <command>egcs</command> or <command>i386-redhat-linux-gcc
           </command>.</para>
 
         <para>Due to time constrains we decided to use the binaries
           from an <application>&oracle; 8.0.5 PreProduction</application>
 	  release, after the first
           attempt at getting the version from the RDBMS CD working,
           failed, and finding and accessing the correct RPMs was a
           nightmare at that time.</para>
 
       </sect3>
 
       <sect3 id="installingtheoracle805preproduction">
         <title>Installing the &oracle; 8.0.5 Pre-production Release for
           Linux (Kernel 2.0.33)</title>
 
         <para>This installation is quite easy. Mount the CD, start the
           installer.  It will then ask for the location of the &oracle;
           home directory, and copy all binaries there. We did not
           delete the remains of our previous RDBMS installation tries,
           though.</para>
 
         <para>Afterwards, <application>&oracle;</application> Database could be started with no
           problems.</para>
       </sect3>
     </sect2>
 
     <sect2 id="installingoracle817">
       <title>Installing the &oracle; 8.1.7 Linux Tarball</title>
       <para>Take the tarball <filename>oracle81732.tgz</filename> you
 	produced from the installation directory on a Linux system
 	and untar it to <filename>/oracle/<replaceable>SID</replaceable>/817_32/</filename>.</para>
     </sect2>
 
     <sect2 id="continuewithsapr4installation">
       <title>Continue with &sap.r3; Installation</title>
 
       <para>First check the environment settings of users 
 	<username>idsamd</username>
         (<replaceable>sid</replaceable>adm) and 
 	<username>oraids</username> (ora<replaceable>sid</replaceable>). They should now
         both have the files <filename>.profile</filename>,
         <filename>.login</filename> and <filename>.cshrc</filename>
         which are all using <command>hostname</command>. In case the
         system's hostname is the fully qualified name, you need to
         change <command>hostname</command> to <command>hostname
         -s</command> within all three files.</para>
 
       <sect3 id="databaseload">
         <title>Database Load</title>
 
         <para>Afterwards, <command>R3SETUP</command> can either be restarted or continued
           (depending on whether exit was chosen or not). <command>R3SETUP</command> then
 	  creates the tablespaces and loads the data (for 46B IDES, from 
 	  EXPORT1 to EXPORT6, for 46C from DISK1 to DISK4) with <command>R3load</command>
 	  into the database.</para>
 
         <para>When the database load is finished (might take a few
           hours), some passwords are requested. For test
           installations, one can use the well known default passwords
           (use different ones if security is an issue!):</para>
 
         <informaltable frame="none" pgwide="1">
           <tgroup cols="2">
           <thead>
           <row>
             <entry>Question</entry>
             <entry>Input</entry>
           </row>
           </thead>
           <tbody>
           <row>
             <entry>Enter Password for sapr3</entry>
             <entry>sap<keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Confirum Password for sapr3</entry>
             <entry>sap<keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Enter Password for sys</entry>
             <entry>change_on_install<keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Confirm Password for sys</entry>
             <entry>change_on_install<keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Enter Password for system</entry>
             <entry>manager<keycap>Enter</keycap></entry>
           </row>
           <row>
             <entry>Confirm Password for system</entry>
             <entry>manager<keycap>Enter</keycap></entry>
           </row>
           </tbody>
           </tgroup>
         </informaltable>
 
         <para>At this point We had a few problems with 
 	  <command>dipgntab</command> during the 4.6B
 	  installation.</para>
       </sect3>
 
       <sect3 id="listener">
         <title>Listener</title>
 
         <para>Start the <application>&oracle;</application> Listener as user 
 	  <username>ora<replaceable>sid</replaceable></username> as follows:</para>
 
         <screen>&prompt.user; <userinput>umask 0; lsnrctl start</userinput></screen>
 
         <para>Otherwise you might get the error <errorcode>ORA-12546</errorcode> as the sockets will not
         have the correct permissions. See &sap; Note 072984.</para>
       </sect3>
 
       <sect3 id="mnlstables">
 	<title>Updating MNLS Tables</title>
 	<para>If you plan to import non-Latin-1 languages into the <application>&sap;</application> system,
 	  you have to update the Multi National Language Support tables.
 	  This is described in the &sap; OSS Notes 15023 and 45619. Otherwise,
 	  you can skip this question during <application>&sap;</application> installation.</para>
 	<note><para>If you do not need MNLS, it is still necessary to check
 	  the table TCPDB and initializing it if this has not been done. See
 	  &sap; note 0015023 and 0045619 for further information.</para></note>
       </sect3>
     </sect2>
 
     <sect2 id="postinstallationsteps">
       <title>Post-installation Steps</title>
 
       <sect3 id="requestsapr3licensekey">
         <title>Request &sap.r3; License Key</title>
 
         <para>You have to request your <application>&sap.r3;</application> License Key. This is needed,
 	  as the temporary license that was installed during installation
 	  is only valid for four weeks. First get the hardware key.  Log 
 	  on as user <username>idsadm</username> and call 
 	  <command>saplicense</command>:</para>
 
         <screen>&prompt.root; <userinput>/sapmnt/IDS/exe/saplicense -get</userinput></screen>
 
 	<para>Calling <command>saplicense</command> without parameters gives 
 	  a list of options.  Upon receiving the license key, it can be 
 	  installed using:</para>
 
         <screen>&prompt.root; <userinput>/sapmnt/IDS/exe/saplicense -install</userinput></screen>
 
         <para>You are then required to enter the following values:</para>
 
         <programlisting>SAP SYSTEM ID   = <replaceable>SID, 3 chars</replaceable>
 CUSTOMER KEY    = <replaceable>hardware key, 11 chars</replaceable>
 INSTALLATION NO = <replaceable>installation, 10 digits</replaceable>
 EXPIRATION DATE = <replaceable>yyyymmdd, usually "99991231"</replaceable>
 LICENSE KEY     = <replaceable>license key, 24 chars</replaceable></programlisting>
       </sect3>
 
       <sect3 id="creatingusers">
         <title>Creating Users</title>
 
         <para>Create a user within client 000 (for some tasks required
         to be done within client 000, but with a user different from
         users <username>sap*</username> and
         <username>ddic</username>). As a user name, We usually choose
         <username>wartung</username> (or
         <username>service</username> in English).  Profiles
         required are <literal>sap_new</literal> and
         <literal>sap_all</literal>. For additional safety the
         passwords of default users within all clients should be
         changed (this includes users <username>sap*</username> and
         <username>ddic</username>).</para>
       </sect3>
 
       <sect3 id="configtranssysprofileopermodesetc">
         <title>Configure Transport System, Profile, Operation Modes, Etc.</title>
 
         <para>Within client 000, user different from <username>ddic</username>
 	  and <username>sap*</username>, do at least the following:</para>
 
         <informaltable frame="none" pgwide="1">
           <tgroup cols="2">
           <thead>
           <row>
             <entry>Task</entry>
             <entry>Transaction</entry>
           </row>
           </thead>
           <tbody>
           <row>
             <entry>Configure Transport System, e.g. as <emphasis>Stand-Alone
             Transport Domain Entity</emphasis></entry>
 	    <entry>STMS</entry>
           </row>
           <row>
             <entry>Create / Edit Profile for System</entry>
             <entry>RZ10</entry>
           </row>
           <row>
             <entry>Maintain Operation Modes and Instances</entry>
             <entry>RZ04</entry>
           </row>
           </tbody>
           </tgroup>
         </informaltable>
 
         <para>These and all the other post-installation steps are
           thoroughly described in <application>&sap;</application> installation guides.</para>
       </sect3>
 
       <sect3 id="editintsidsap">
         <title>Edit <filename>init<replaceable>sid</replaceable>.sap</filename> (<filename>initIDS.sap</filename>)</title>
 
 	<para>The file <filename>/oracle/IDS/dbs/initIDS.sap</filename>
 	  contains the <application>&sap;</application> backup profile.  Here the size of the tape to 
 	  be used, type of compression and so on need to be defined. To 
           get this running with <command>sapdba</command> /
 	  <command>brbackup</command>, we changed the following values:</para>
 
         <programlisting>compress = hardware
 archive_function = copy_delete_save
 cpio_flags = "-ov --format=newc --block-size=128 --quiet"
 cpio_in_flags = "-iuv --block-size=128 --quiet"
 tape_size = 38000M
 tape_address = /dev/nsa0
 tape_address_rew = /dev/sa0</programlisting>
 
         <para>Explanations:</para>
 
         <para><varname>compress</varname>: The tape we use is a HP DLT1
         which does hardware compression.</para>
 
         <para><varname>archive_function</varname>: This defines the
         default behavior for saving &oracle; archive logs: new logfiles
         are saved to tape, already saved logfiles are saved again and
         are then deleted.  This prevents lots of trouble if you need to
         recover the database, and one of the archive-tapes has gone
         bad.</para>
 
         <para><varname>cpio_flags</varname>: Default is to use <option>-B</option> which
         sets block size to 5120&nbsp;Bytes. For DLT Tapes, HP recommends at
         least 32&nbsp;K block size, so we used <option>--block-size=128</option> for
         64&nbsp;K. <option>--format=newc</option> is needed because we have inode numbers greater than
         65535. The last option <option>--quiet</option> is needed as otherwise 
 	<command>brbackup</command>
         complains as soon as <command>cpio</command> outputs the 
 	numbers of blocks saved.</para>
 
         <para><varname>cpio_in_flags</varname>: Flags needed for
         loading data back from tape. Format is recognized
         automatically.</para>
 
         <para><varname>tape_size</varname>: This usually gives the raw
         storage capability of the tape. For security reason (we use
         hardware compression), the value is slightly lower than the
         actual value.</para>
 
         <para><varname>tape_address</varname>: The non-rewindable
         device to be used with <command>cpio</command>.</para>
 
         <para><varname>tape_address_rew</varname>: The rewindable device to be
         used with <command>cpio</command>.</para>
       </sect3>
 
       <sect3>
 	<title>Configuration Issues after Installation</title>
 
 	<para>The following <application>&sap;</application> parameters should be tuned after
 	  installation (examples for IDES 46B, 1&nbsp;GB memory):</para>
 
 	<informaltable frame="none" pgwide="1">
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Name</entry>
 		<entry>Value</entry>
 	      </row>
 	    </thead>
 	    <tbody>
 	      <row>
 		<entry>ztta/roll_extension</entry>
 		<entry>250000000</entry>
 	      </row>
 	      <row>
 		<entry>abap/heap_area_dia</entry>
                 <entry>300000000</entry>
 	      </row>
 	      <row>
 		<entry>abap/heap_area_nondia</entry>
 		<entry>400000000</entry>
 	      </row>
 	      <row>
 		<entry>em/initial_size_MB</entry>
 		<entry>256</entry>
 	      </row>
 	      <row>
 		<entry>em/blocksize_kB</entry>
 		<entry>1024</entry>
 	      </row>
 	      <row>
 		<entry>ipc/shm_psize_40</entry>
 		<entry>70000000</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</informaltable>
 
 	<para>&sap; Note 0013026:</para>
 
 	<informaltable frame="none" pgwide="1">
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Name</entry>
 		<entry>Value</entry>
 	      </row>
 	    </thead>
 	    <tbody>
 	      <row>
 		<entry>ztta/dynpro_area</entry>
 		<entry>2500000</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</informaltable>
 
 	<para>&sap; Note 0157246:</para>
 
 	<informaltable frame="none" pgwide="1">
 	  <tgroup cols="2">
 	    <thead>
 	      <row>
 		<entry>Name</entry>
 		<entry>Value</entry>
 	      </row>
 	    </thead>
 	    <tbody>
 	      <row>
 		<entry>rdisp/ROLL_MAXFS</entry>
 		<entry>16000</entry>
 	      </row>
 	      <row>
 		<entry>rdisp/PG_MAXFS</entry>
 		<entry>30000</entry>
 	      </row>
 	    </tbody>
 	  </tgroup>
 	</informaltable>
 
 	<note>
 	  <para>With the above parameters, on a system with 1&nbsp;gigabyte
 	    of memory, one may find memory consumption similar to:</para>
 
 	  <programlisting>Mem: 547M Active, 305M Inact, 109M Wired, 40M Cache, 112M Buf, 3492K Free</programlisting>
 	</note>
       </sect3>
     </sect2>
 
     <sect2 id="problemsduringinstallation">
       <title>Problems during Installation</title>
 
       <sect3 id="restartr3setup">
 	<title>Restart <command>R3SETUP</command> after Fixing a Problem</title>
 
 	<para><command>R3SETUP</command> stops if it encounters an error. If you have
 	  looked at the corresponding logfiles and fixed the error,
 	  you have to start <command>R3SETUP</command> again, usually selecting REPEAT
 	  as option for the last step <command>R3SETUP</command> complained about.</para>
 
 	<para>To restart <command>R3SETUP</command>, just start it with the corresponding
 	  <filename>R3S</filename> file:</para>
 
 	  <screen>&prompt.root; <userinput>./R3SETUP -f CENTRDB.R3S</userinput></screen>
 
 	  <para>for 4.6B, or with</para>
 
 	  <screen>&prompt.root; <userinput>./R3SETUP -f CENTRAL.R3S</userinput></screen>
 
 	  <para>for 4.6C, no matter whether the error occurred
 	  with <filename>CENTRAL.R3S</filename> or
 	  <filename>DATABASE.R3S</filename>.</para>
 
 	<note><para>At some stages, <command>R3SETUP</command> assumes that both database
 	    and <application>&sap;</application> processes are up and running (as those were steps it
 	    already completed). Should errors occur and for example the 
 	    database could not be started, you have to start both database 
 	    and <application>&sap;</application> by hand after you fixed the errors and before starting 
 	    <command>R3SETUP</command> again.</para>
 	  <para>Do not forget to also start the <application>&oracle;</application> listener again (as 
 	    <username>ora<replaceable>sid</replaceable></username> with
 	    <command>umask 0; lsnrctl start</command>) if it was also
 	    stopped (for example due to a necessary reboot of the 
 	    system).</para>
 	</note>
       </sect3>
 
       <sect3 id="indoraduringduringr3setup">
         <title>OSUSERSIDADM_IND_ORA during <command>R3SETUP</command></title>
 
         <para>If <command>R3SETUP</command> complains at this stage, edit the
 	  template file <command>R3SETUP</command> used at that time
           (<filename>CENTRDB.R3S</filename> (4.6B) or either
 	  <filename>CENTRAL.R3S</filename> or
 	  <filename>DATABASE.R3S</filename> (4.6C)).
 	  Locate <literal>[OSUSERSIDADM_IND_ORA]</literal> or search for the
 	  only <literal>STATUS=ERROR</literal> entry
 	  and edit the following values:</para>
 
         <programlisting>HOME=/home/<replaceable>sid</replaceable>adm (was empty)
 STATUS=OK (had status ERROR)
         </programlisting>
 
         <para>Then you can restart <command>R3SETUP</command> again.</para>
       </sect3>
 
       <sect3 id="indoraduringr3setup">
         <title>OSUSERDBSID_IND_ORA during <command>R3SETUP</command></title>
 
         <para>Possibly <command>R3SETUP</command> also complains at this stage. The error
 	  here is similar to the one in phase OSUSERSIDADM_IND_ORA. 
 	  Just edit
 	  the template file <command>R3SETUP</command> used at that time
           (<filename>CENTRDB.R3S</filename> (4.6B) or either
 	  <filename>CENTRAL.R3S</filename> or
 	  <filename>DATABASE.R3S</filename> (4.6C)).
 	  Locate <literal>[OSUSERDBSID_IND_ORA]</literal> or search for the
 	  only <literal>STATUS=ERROR</literal> entry
 	  and edit the following value in that section:</para>
 
         <programlisting>STATUS=OK</programlisting>
 
         <para>Then restart <command>R3SETUP</command>.</para>
       </sect3>
 
       <sect3 id="oraviewvrffilenotfound">
         <title><errorname>oraview.vrf FILE NOT FOUND</errorname> during &oracle; Installation</title>
 
         <para>You have not deselected <emphasis>&oracle; On-Line Text Viewer</emphasis>
           before starting the installation. This is marked for installation even
           though this option is currently not available for Linux. Deselect this
           product inside the <application>&oracle;</application> installation menu and restart installation.</para>
       </sect3>
 
       <sect3 id="textenvincalid">
         <title><errorname>TEXTENV_INVALID</errorname> during <command>R3SETUP</command>, RFC or SAPgui Start</title>
 
         <para>If this error is encountered, the correct locale is
 	  missing.  &sap; Note 0171356 lists the necessary RPMs that need
 	  be installed (e.g. <filename>saplocales-1.0-3</filename>,
 	  <filename>saposcheck-1.0-1</filename> for RedHat 6.1). In case
 	  you ignored all the related errors and set the corresponding
 	  <literal>STATUS</literal> from <literal>ERROR</literal> to <literal>OK</literal> (in <filename>CENTRDB.R3S</filename>) every time <command>R3SETUP</command>
 	  complained and just restarted <command>R3SETUP</command>, the <application>&sap;</application> system will not
 	  be properly configured and you will then not be able to
 	  connect to the system with a
 	  <application>SAPgui</application>, even though the system
 	  can be started. Trying to connect with the old Linux
 	  <application>SAPgui</application> gave the following
 	  messages:</para>
 
         <programlisting>Sat May 5 14:23:14 2001
 *** ERROR => no valid userarea given [trgmsgo. 0401]
 Sat May 5 14:23:22 2001
 *** ERROR => ERROR NR 24 occured [trgmsgi. 0410]
 *** ERROR => Error when generating text environment. [trgmsgi. 0435]
 *** ERROR => function failed [trgmsgi. 0447]
 *** ERROR => no socket operation allowed [trxio.c 3363]
 Speicherzugriffsfehler</programlisting>
 
         <para>This behavior is due to <application>&sap.r3;</application> being unable to correctly
 	  assign a locale and also not being properly configured itself
 	  (missing entries in some database tables). To be able to connect
 	  to <application>&sap;</application>, add the following entries to file 
 	  <filename>DEFAULT.PFL</filename> (see Note 0043288):</para>
 
 	<programlisting>abap/set_etct_env_at_new_mode = 0
 install/collate/active = 0
 rscp/TCP0B = TCP0B</programlisting>
 
         <para>Restart the <application>&sap;</application> system. Now you can connect to the
           system, even though country-specific language settings might
           not work as expected.  After correcting country settings
           (and providing the correct locales), these entries can be
           removed from <filename>DEFAULT.PFL</filename> and the <application>&sap;</application>
 	  system can be restarted.</para>
 
       </sect3>
 
       <sect3 id="ora-00001">
 	<title><errorcode>ORA-00001</errorcode></title>
 	<para>This error only happened with 
 	  <application>&oracle; 8.1.7</application> on FreeBSD&nbsp;4.5.
 	  The reason was that the <application>&oracle;</application> database could not initialize itself
 	  properly and crashed, leaving semaphores and shared memory on the
 	  system. The next try to start the database then returned
 	  <errorcode>ORA-00001</errorcode>.</para>
 
 	<para>Find them with <command>ipcs -a</command> and remove them
 	  with <command>ipcrm</command>.</para>
       </sect3>
 
       <sect3 id="ora-00445pmon">
 	<title><errorcode>ORA-00445</errorcode> (Background Process PMON Did Not Start)</title>
 	<para>This error happened with <application>&oracle; 8.1.7</application>.
 	  This error is reported if the database is started with
 	  the usual <command>startsap</command> script (for example
 	  <command>startsap_majestix_00</command>) as user 
 	  <username>prdadm</username>.</para>
 
 	<para>A possible workaround is to start the database as user 
 	  <username>oraprd</username> instead
 	  with <command>svrmgrl</command>:</para>
 
 	<screen>&prompt.user; <userinput>svrmgrl</userinput>
 SVRMGR&gt; <userinput>connect internal;</userinput>
 SVRMGR&gt; <userinput>startup</userinput>;
 SVRMGR&gt; <userinput>exit</userinput></screen>
 
       </sect3>
 
       <sect3 id="ora-12546">
         <title><errorcode>ORA-12546</errorcode> (Start Listener with Correct Permissions)</title>
 
         <para>Start the <application>&oracle;</application> listener as user
           <username>oraids</username> with the following commands:</para>
 
         <screen>&prompt.root; <userinput>umask 0; lsnrctl start</userinput></screen>
 
         <para>Otherwise you might get <errorcode>ORA-12546</errorcode> as the sockets will not
           have the correct permissions. See &sap; Note 0072984.</para>
       </sect3>
 
       <sect3 id="ora-27102">
 	<title><errorcode>ORA-27102</errorcode> (Out of Memory)</title>
 
 	<para>This error happened whilst trying to use values for
 	  <literal>MAXDSIZ</literal> and <literal>DFLDSIZ</literal>
 	  greater than 1&nbsp;GB (1024x1024x1024). Additionally, we got 
 	  <errorname>Linux Error 12: Cannot allocate memory</errorname>.</para>
       </sect3>
 
       <sect3 id="dipgntabindind">
         <title>[DIPGNTAB_IND_IND] during <command>R3SETUP</command></title>
 
         <para>In general, see &sap; Note 0130581 (<command>R3SETUP</command> step 
 	  <literal>DIPGNTAB</literal> terminates).  During the
 	  IDES-specific installation, for some reason the installation
 	  process was not using the proper <application>&sap;</application> system name <quote>IDS</quote>, but
 	  the empty string <literal>""</literal> instead. This leads to some minor problems
 	  with accessing directories, as the paths are generated
 	  dynamically using <replaceable>SID</replaceable> (in this case IDS).  So instead
 	  of accessing:</para>
 
         <programlisting>/usr/sap/IDS/SYS/...
 /usr/sap/IDS/DVMGS00</programlisting>
 
         <para>the following paths were used:</para>
 
         <programlisting>/usr/sap//SYS/...
 /usr/sap/D00</programlisting>
 
         <para>To continue with the installation, we created a link and an
           additional directory:</para>
 
         <screen>&prompt.root; <userinput>pwd</userinput>
 /compat/linux/usr/sap
 &prompt.root; <userinput>ls -l</userinput>
 total 4
 drwxr-xr-x 3  idsadm sapsys 512 May 5 11:20 D00
 drwxr-x--x 5  idsadm sapsys 512 May 5 11:35 IDS
-lrwxr-xr-x 1  root   sapsys 7 May 5 11:35 SYS -> IDS/SYS
+lrwxr-xr-x 1  root   sapsys 7 May 5 11:35 SYS -&gt; IDS/SYS
 drwxrwxr-x 2  idsadm sapsys 512 May 5 13:00 tmp
 drwxrwxr-x 11 idsadm sapsys 512 May 4 14:20 trans</screen>
    
         <para>We also found &sap; Notes (0029227 and 0008401) describing
         this behavior. We did not encounter any of these problems with
 	the <application>&sap; 4.6C</application> installation.</para>
       </sect3>
 
       <sect3 id="rfcrswboiniindind">
         <title>[RFCRSWBOINI_IND_IND] during <command>R3SETUP</command></title>
 
 	<para>During installation of <application>&sap; 4.6C</application>,
           this error was just the result of another error happening
 	  earlier during installation. In this case, you have to look
 	  through the corresponding logfiles and correct the real
 	  problem.</para>
 
         <para>If after looking through the logfiles this error is
 	  indeed the correct one (check the &sap; Notes), you can set 
 	  <literal>STATUS</literal> of the offending step from <literal>ERROR</literal> to <literal>OK</literal> (file
 	  <filename>CENTRDB.R3S</filename>) and restart <command>R3SETUP</command>. After
 	  installation, you have to execute the report
 	  <literal>RSWBOINS</literal> from transaction SE38. See &sap;
 	  Note 0162266 for additional information about phase
 	  <literal>RFCRSWBOINI</literal> and
 	  <literal>RFCRADDBDIF</literal>.</para>
       </sect3>
 
       <sect3 id="rfcraddbdifindind">
         <title>[RFCRADDBDIF_IND_IND] during <command>R3SETUP</command></title>
 	<para>Here the same restrictions apply: make sure by looking
 	  through the logfiles, that this error is not caused by some
 	  previous problems.</para>
 
         <para>If you can confirm that &sap; Note 0162266 applies, just 
 	  set <literal>STATUS</literal> of the offending step from <literal>ERROR</literal> to <literal>OK</literal> (file
 	  <filename>CENTRDB.R3S</filename>) and restart <command>R3SETUP</command>. After
 	  installation, you have to execute the report
 	  <literal>RADDBDIF</literal> from transaction SE38.</para>
       </sect3>
 
       <sect3 id="sigactionsig31">
         <title><errorcode>sigaction sig31: File size limit exceeded</errorcode></title>
 
 	<para>This error occurred during start of <application>&sap;</application> processes
 	  <emphasis>disp+work</emphasis>. If starting <application>&sap;</application> with the
 	  <command>startsap</command> script, subprocesses are then started which
 	  detach and do the dirty work of starting all other <application>&sap;</application>
           processes. As a result, the script itself will not notice
 	  if something goes wrong.</para>
 
 	<para>To check whether the <application>&sap;</application> processes did start properly,
 	  have a look at the process status with 
 	  <command>ps ax | grep <replaceable>SID</replaceable></command>, which will give
 	  you a list of all <application>&oracle;</application> and <application>&sap;</application> processes. If it looks like
 	  some processes are missing or if you cannot connect to the <application>&sap;</application> system,
 	  look at the corresponding logfiles which can be found
 	  at <filename>/usr/sap/<replaceable>SID</replaceable>/DVEBMGS<replaceable>nr</replaceable>/work/</filename>.
 	  The files to look at are <filename>dev_ms</filename> and 
 	  <filename>dev_disp</filename>.</para>
 
 	<para>Signal 31 happens here if the amount of shared memory used by
 	  <application>&oracle;</application> and <application>&sap;</application> exceed the one defined within the kernel configuration
 	  file and could be resolved by using a larger value:</para>
 
         <programlisting># larger value for 46C production systems:
 options SHMMAXPGS=393216
 # smaller value sufficient for 46B:
 #options SHMMAXPGS=262144</programlisting>
 	  
       </sect3>
 
       <sect3 id="saposcolfails">
         <title>Start of <command>saposcol</command> Failed</title>
 	<para>There are some problems with the program <command>saposcol</command> (version 4.6D).
 	  The <application>&sap;</application> system is using <command>saposcol</command> to collect data about the 
 	  system performance. This program is not needed to use the <application>&sap;</application> system,
 	  so this problem can be considered a minor one. The older versions
 	  (4.6B) does work, but does not collect all the data (many calls will
 	  just return 0, for example for CPU usage).</para>
       </sect3>
     </sect2>
   </sect1>
 
   <sect1 id="linuxemu-advanced">
     <title>Advanced Topics</title>
 
     <para>If you are curious as to how the Linux binary compatibility
       works, this is the section you want to read.  Most of what follows
       is based heavily on an email written to &a.chat; by Terry Lambert
       <email>tlambert@primenet.com</email> (Message ID:
       <literal>&lt;199906020108.SAA07001@usr09.primenet.com&gt;</literal>).</para>
 
     <sect2>
       <title>How Does It Work?</title>
       <indexterm><primary>execution class loader</primary></indexterm>
 
       <para>FreeBSD has an abstraction called an <quote>execution class
 	loader</quote>.  This is a wedge into the &man.execve.2; system
 	call.</para>
 
       <para>What happens is that FreeBSD has a list of loaders, instead of
 	a single loader with a fallback to the <literal>#!</literal>
 	loader for running any shell interpreters or shell scripts.</para>
 
       <para>Historically, the only loader on the &unix; platform examined
 	the magic number (generally the first 4 or 8 bytes of the file) to
 	see if it was a binary known to the system, and if so, invoked the
 	binary loader.</para>
 
       <para>If it was not the binary type for the system, the
 	&man.execve.2; call returned a failure, and the shell attempted to
 	start executing it as shell commands.</para>
 
       <para>The assumption was a default of <quote>whatever the current
 	shell is</quote>.</para>
 
       <para>Later, a hack was made for &man.sh.1; to examine the first two
 	characters, and if they were <literal>:\n</literal>, then it
 	invoked the &man.csh.1; shell instead (we believe SCO first made
 	this hack).</para>
 
       <para>What FreeBSD does now is go through a list of loaders, with a
 	generic <literal>#!</literal> loader that knows about interpreters
 	as the characters which follow to the next whitespace next to
 	last, followed by a fallback to
 	<filename>/bin/sh</filename>.</para>
       <indexterm><primary>ELF</primary></indexterm>
 
       <para>For the Linux ABI support, FreeBSD sees the magic number as an
 	ELF binary (it makes no distinction between FreeBSD, &solaris;,
 	Linux, or any other OS which has an ELF image type, at this
 	point).</para>
       <indexterm><primary>Solaris</primary></indexterm>
 
       <para>The ELF loader looks for a specialized
 	<emphasis>brand</emphasis>, which is a comment section in the ELF
 	image, and which is not present on SVR4/&solaris; ELF
 	binaries.</para>
 
       <para>For Linux binaries to function, they must be
 	<emphasis>branded</emphasis> as type <literal>Linux</literal>
 	from &man.brandelf.1;:</para>
 
       <screen>&prompt.root; <userinput>brandelf -t Linux file</userinput></screen>
 
       <para>When this is done, the ELF loader will see the
 	<literal>Linux</literal> brand on the file.</para>
       <indexterm>
         <primary>ELF</primary>
 	<secondary>branding</secondary>
       </indexterm>
 
       <para>When the ELF loader sees the <literal>Linux</literal> brand,
 	the loader replaces a pointer in the <literal>proc</literal>
 	structure.  All system calls are indexed through this pointer (in
 	a traditional &unix; system, this would be the
 	<literal>sysent[]</literal> structure array, containing the system
 	calls).  In addition, the process is flagged for special handling of
 	the trap vector for the signal trampoline code, and several other
 	(minor) fix-ups that are handled by the Linux kernel
 	module.</para>
 
       <para>The Linux system call vector contains, among other things, a
 	list of <literal>sysent[]</literal> entries whose addresses reside
 	in the kernel module.</para>
 
       <para>When a system call is called by the Linux binary, the trap
 	code dereferences the system call function pointer off the
 	<literal>proc</literal> structure, and gets the Linux, not the
 	FreeBSD, system call entry points.</para>
 
       <para>In addition, the Linux mode dynamically
 	<emphasis>reroots</emphasis> lookups; this is, in effect, what the
 	<option>union</option> option to file system mounts
 	(<emphasis>not</emphasis> the <literal>unionfs</literal> file system type!) does.  First, an attempt
 	is made to lookup the file in the
 	<filename>/compat/linux/<replaceable>original-path</replaceable></filename>
 	directory, <emphasis>then</emphasis> only if that fails, the
 	lookup is done in the
 	<filename>/<replaceable>original-path</replaceable></filename>
 	directory.  This makes sure that binaries that require other
 	binaries can run (e.g., the Linux toolchain can all run under
 	Linux ABI support).  It also means that the Linux binaries can
 	load and execute FreeBSD binaries, if there are no corresponding
 	Linux binaries present, and that you could place a &man.uname.1;
 	command in the <filename>/compat/linux</filename> directory tree
 	to ensure that the Linux binaries could not tell they were not
 	running on Linux.</para>
 
       <para>In effect, there is a Linux kernel in the FreeBSD kernel; the
 	various underlying functions that implement all of the services
 	provided by the kernel are identical to both the FreeBSD system
 	call table entries, and the Linux system call table entries: file
 	system operations, virtual memory operations, signal delivery,
 	System V IPC, etc&hellip;  The only difference is that FreeBSD
 	binaries get the FreeBSD <emphasis>glue</emphasis> functions, and
 	Linux binaries get the Linux <emphasis>glue</emphasis> functions
 	(most older OS's only had their own <emphasis>glue</emphasis>
 	functions: addresses of functions in a static global
 	<literal>sysent[]</literal> structure array, instead of addresses
 	of functions dereferenced off a dynamically initialized pointer in
 	the <literal>proc</literal> structure of the process making the
 	call).</para>
 
       <para>Which one is the native FreeBSD ABI?  It does not matter.
 	Basically the only difference is that (currently; this could
 	easily be changed in a future release, and probably will be after
 	this) the FreeBSD <emphasis>glue</emphasis> functions are
 	statically linked into the kernel, and the Linux <emphasis>glue</emphasis> functions
 	can be statically linked, or they can be accessed via a kernel
 	module.</para>
 
       <para>Yeah, but is this really emulation?  No.  It is an ABI
 	implementation, not an emulation.  There is no emulator (or
 	simulator, to cut off the next question) involved.</para>
 
       <para>So why is it sometimes called <quote>Linux emulation</quote>?
 	To make it hard to sell FreeBSD!  Really, it
 	is because the historical implementation was done at a time when
 	there was really no word other than that to describe what was
 	going on; saying that FreeBSD ran Linux binaries was not true, if
 	you did not compile the code in or load a module, and there needed
 	to be a word to describe what was being loaded&mdash;hence
 	<quote>the Linux emulator</quote>.</para>
     </sect2>
   </sect1>
 </chapter>
 
 <!-- 
      Local Variables:
      mode: sgml
      sgml-declaration: "../chapter.decl"
      sgml-indent-data: t
      sgml-omittag: nil
      sgml-always-quote-attributes: t
      sgml-parent-document: ("../book.sgml" "part" "chapter")
      End:
 -->
 
diff --git a/zh_TW.Big5/books/handbook/mirrors/chapter.sgml b/zh_TW.Big5/books/handbook/mirrors/chapter.sgml
index 31726da40b..36094ce40d 100644
--- a/zh_TW.Big5/books/handbook/mirrors/chapter.sgml
+++ b/zh_TW.Big5/books/handbook/mirrors/chapter.sgml
@@ -1,3169 +1,3177 @@
 <!--
      The FreeBSD Documentation Project
 
      $FreeBSD$
 -->
 
 <appendix id="mirrors">
   <title>Obtaining FreeBSD</title>
 
   <sect1 id="mirrors-cdrom">
     <title>CDROM and DVD Publishers</title>
 
     <sect2>
       <title>Retail Boxed Products</title>
 
       <para>FreeBSD is available as a boxed product (FreeBSD CDs,
 	additional software, and printed documentation) from several
 	retailers:</para>
 
       <itemizedlist>
 	<listitem>
 	  <address>
 	    <otheraddr>CompUSA</otheraddr>
 	    WWW: <otheraddr><ulink url="http://www.compusa.com/"></ulink></otheraddr>
 	  </address>
 	</listitem>
 
 	<listitem>
 	  <address>
 	    <otheraddr>Frys Electronics</otheraddr>
 	    WWW: <otheraddr><ulink url="http://www.frys.com/"></ulink></otheraddr>
 	  </address>
 	</listitem>
       </itemizedlist>
     </sect2>
 
     <sect2>
       <title>CD and DVD Sets</title>
 
       <para>FreeBSD CD and DVD sets are available from many online
 	retailers:</para>
 
     <itemizedlist>
       <listitem>
         <address>
 	  <otheraddr>BSD Mall by Daemon News</otheraddr>
 	  <street>PO Box 161</street>
 	  <city>Nauvoo</city>, <state>IL</state> <postcode>62354</postcode>
 	  <country>USA</country>
 	  Phone: <phone>+1 866 273-6255</phone>
 	  Fax: <fax>+1 217 453-9956</fax>
 	  Email: <email>sales@bsdmall.com</email>
 	  WWW: <otheraddr><ulink url="http://www.bsdmall.com/freebsd1.html"></ulink></otheraddr>
         </address>
       </listitem>
 
       <listitem>
         <address>
 	  <otheraddr>BSD-Systems</otheraddr>
 	  Email: <email>info@bsd-systems.co.uk</email>
 	  WWW: <otheraddr><ulink url="http://www.bsd-systems.co.uk"></ulink></otheraddr>
         </address>
       </listitem>
 
       <listitem>
         <address>
 	  <otheraddr>fastdiscs.com</otheraddr>
 	  <street>6 Eltham Close</street>
 	  <city>Leeds</city>, <postcode>LS6 2TY</postcode>
 	  <country>United Kingdom</country>
 	  Phone: <phone>+44 870 1995 171</phone>
 	  Email: <email>sales@fastdiscs.com</email>
 	  WWW: <otheraddr><ulink url="http://fastdiscs.com/freebsd/"></ulink></otheraddr>
         </address>
       </listitem>
 
       <listitem>
         <address>
 	  <otheraddr>FreeBSD Mall, Inc.</otheraddr>
 	  <street>3623 Sanford Street</street>
 	  <city>Concord</city>, <state>CA</state>  <postcode>94520-1405</postcode>
 	  <country>USA</country>
 	  Phone: <phone>+1 925 674-0783</phone>
 	  Fax: <fax>+1 925 674-0821</fax>
 	  Email: <email>info@freebsdmall.com</email>
 	  WWW: <otheraddr><ulink url="http://www.freebsdmall.com/"></ulink></otheraddr>
         </address>
       </listitem>
 
       <listitem>
 	<address>
 	  <otheraddr>Hinner EDV</otheraddr>
 	  <street>St. Augustinus-Str. 10</street>
 	  <postcode>D-81825</postcode> <city>M&uuml;nchen</city>
 	  <country>Germany</country>
 	  Phone: <phone>(089) 428 419</phone>
 	  WWW: <otheraddr><ulink url="http://www.hinner.de/linux/freebsd.html"></ulink></otheraddr>
         </address>
       </listitem>
 
       <listitem>
 	<address>
 	  <otheraddr>Ikarios</otheraddr>
 	  <street>22-24 rue Voltaire</street>
 	  <postcode>92000</postcode> <city>Nanterre</city>
 	  <country>France</country>
 	  WWW: <otheraddr><ulink url="http://ikarios.com/form/#freebsd"></ulink></otheraddr>
         </address>
       </listitem>
 
       <listitem>
 	<address>
 	  <otheraddr>JMC Software</otheraddr>
 	  <country>Ireland</country>
 	  Phone: <phone>353 1 6291282</phone>
 	  WWW: <otheraddr><ulink url="http://www.thelinuxmall.com"></ulink></otheraddr>
 	</address>
       </listitem>
 
       <listitem>
 	<address>
 	  <otheraddr>Linux CD Mall</otheraddr>
 	  <street>Private Bag MBE N348</street>
 	  <city>Auckland 1030</city>
 	  <country>New Zealand</country>
 	  Phone: <phone>+64 21 866529</phone>
 	  WWW: <otheraddr><ulink url="http://www.linuxcdmall.co.nz/"></ulink></otheraddr>
 	</address>
       </listitem>
 
       <listitem>
 	<address>
 	  <otheraddr>The Linux Emporium</otheraddr>
 	  <street>Hilliard House, Lester Way</street>
 	  <city>Wallingford</city>
 	  <postcode>OX10 9TA</postcode>
 	  <country>United Kingdom</country>
 	  Phone: <phone>+44 1491 837010</phone>
 	  Fax: <fax>+44 1491 837016</fax>
 	  WWW: <otheraddr><ulink url="http://www.linuxemporium.co.uk/products/freebsd/"></ulink></otheraddr>
         </address>
       </listitem>
 
       <listitem>
 	<address>
 	  <otheraddr>Linux+ DVD Magazine</otheraddr>
 	  <street>Lewartowskiego 6</street>
 	  <city>Warsaw</city>
 	  <postcode>00-190</postcode>
 	  <country>Poland</country>
 	  Phone: <phone>+48 22 860 18 18</phone>
 	  Email: <email>editors@lpmagazine.org</email>
 	  WWW: <otheraddr><ulink url="http://www.lpmagazine.org/"></ulink></otheraddr>
 	</address>
       </listitem>
 
       <listitem>
 	<address>
 	  <otheraddr>Linux System Labs Australia</otheraddr>
 	  <street>21 Ray Drive</street>
 	  <city>Balwyn North</city>
 	  <postcode>VIC - 3104</postcode>
 	  <country>Australia</country>
 	  Phone: <phone>+61 3 9857 5918</phone>
 	  Fax: <fax>+61 3 9857 8974</fax>
 	  WWW: <otheraddr><ulink url="http://www.lsl.com.au"></ulink></otheraddr>
         </address>
       </listitem>
 
       <listitem>
 	<address>
 	  <otheraddr>LinuxCenter.Ru</otheraddr>
 	  <street>Galernaya Street, 55</street>
 	  <city>Saint-Petersburg</city>
 	  <postcode>190000</postcode>
 	  <country>Russia</country>
 	  Phone: <phone>+7-812-3125208</phone>
 	  Email: <email>info@linuxcenter.ru</email>
 	  WWW: <otheraddr><ulink url="http://linuxcenter.ru/freebsd"></ulink></otheraddr>
 	</address>
       </listitem>
 
     </itemizedlist>
     </sect2>
 
     <sect2>
       <title>Distributors</title>
 
       <para>If you are a reseller and want to carry FreeBSD CDROM products,
 	please contact a distributor:</para>
 
       <itemizedlist>
 	<listitem>
 	  <address>
 	    <otheraddr>Cylogistics</otheraddr>
 	    <street>809B Cuesta Dr., #2149</street>
 	    <city>Mountain View</city>, <state>CA</state> <postcode>94040</postcode>
 	    <country>USA</country>
 	    Phone: <phone>+1 650 694-4949</phone>
 	    Fax: <fax>+1 650 694-4953</fax>
 	    Email: <email>sales@cylogistics.com</email>
 	    WWW: <otheraddr><ulink url="http://www.cylogistics.com/"></ulink></otheraddr>
 	  </address>
 	</listitem>
 
         <listitem>
 	  <address>
 	    <otheraddr>Ingram Micro</otheraddr>
 	    <street>1600 E. St. Andrew Place</street>
 	    <city>Santa Ana</city>, <state>CA</state>  <postcode>92705-4926</postcode>
 	    <country>USA</country>
 	    Phone: <phone>1 (800) 456-8000</phone>
 	    WWW: <otheraddr><ulink url="http://www.ingrammicro.com/"></ulink></otheraddr>
           </address>
         </listitem>
 
 	<listitem>
 	  <address>
 	    <otheraddr>Kudzu, LLC</otheraddr>
 	    <street>7375 Washington Ave. S.</street>
 	    <city>Edina</city>, <state>MN</state> <postcode>55439</postcode>
 	    <country>USA</country>
 	    Phone: <phone>+1 952 947-0822</phone>
 	    Fax: <fax>+1 952 947-0876</fax>
 	    Email: <email>sales@kudzuenterprises.com</email>
 	  </address>
 	</listitem>
 
 	<listitem>
 	  <address>
 	    <otheraddr>LinuxCenter.Ru</otheraddr>
 	    <street>Galernaya Street, 55</street>
 	    <city>Saint-Petersburg</city>
 	    <postcode>190000</postcode>
 	    <country>Russia</country>
 	    Phone: <phone>+7-812-3125208</phone>
 	    Email: <email>info@linuxcenter.ru</email>
 	    WWW: <otheraddr><ulink url="http://linuxcenter.ru/freebsd"></ulink></otheraddr>
 	  </address>
 	</listitem>
 
 	<listitem>
 	  <address>
 	    <otheraddr>Navarre Corp</otheraddr>
 	    <street>7400 49th Ave South</street>
 	    <city>New Hope</city>, <state>MN</state> <postcode>55428</postcode>
 	    <country>USA</country>
 	    Phone: <phone>+1 763 535-8333</phone>
 	    Fax: <fax>+1 763 535-0341</fax>
 	    WWW: <otheraddr><ulink url="http://www.navarre.com/"></ulink></otheraddr>
 	  </address>
 	</listitem>
       </itemizedlist>
     </sect2>
   </sect1>
 
   <sect1 id="mirrors-ftp">
     <title>FTP Sites</title>
 
     <para>The official sources for FreeBSD are available via anonymous FTP
       from a worldwide set of mirror sites.  The site
       <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/"></ulink> is well
       connected and allows a large number of connections to it, but
       you are probably better off finding a <quote>closer</quote>
       mirror site (especially if you decide to set up some sort of
       mirror site).</para>
 
     <para>The <ulink
 	url="http://mirrorlist.FreeBSD.org/">FreeBSD mirror
 	sites database</ulink> is more accurate than the mirror listing in the
       Handbook, as it gets its information from the DNS rather than relying on
       static lists of hosts.</para>
 
     <para>Additionally, FreeBSD is available via anonymous FTP from the
       following mirror sites.  If you choose to obtain FreeBSD via anonymous
       FTP, please try to use a site near you.  The mirror sites listed as
       <quote>Primary Mirror Sites</quote> typically have the entire FreeBSD archive (all
       the currently available versions for each of the architectures) but
       you will probably have faster download times from a site that is
       in your country or region.  The regional sites carry the most recent
       versions for the most popular architecture(s) but might not carry
       the entire FreeBSD archive.  All sites provide access via anonymous
       FTP but some sites also provide access via other methods.  The access
       methods available for each site are provided in parentheses
       after the hostname.</para>
 
     &chap.mirrors.ftp.inc;
   </sect1>
 
     <sect1 id="anoncvs">
       <title>Anonymous CVS</title>
 
       <sect2>
 	<title><anchor id="anoncvs-intro">Introduction</title>
 
 	<indexterm>
 	  <primary>CVS</primary>
 	  <secondary>anonymous</secondary>
 	</indexterm>
 
 	<para>Anonymous CVS (or, as it is otherwise known,
 	  <emphasis>anoncvs</emphasis>) is a feature provided by the CVS
 	  utilities bundled with FreeBSD for synchronizing with a remote
 	  CVS repository.  Among other things, it allows users of FreeBSD
 	  to perform, with no special privileges, read-only CVS operations
 	  against one of the FreeBSD project's official anoncvs servers.
 	  To use it, one simply sets the <envar>CVSROOT</envar>
 	  environment variable to point at the appropriate anoncvs server,
 	  provides the well-known password <quote>anoncvs</quote> with the
 	  <command>cvs login</command> command, and then uses the
 	  &man.cvs.1; command to access it like any local
 	  repository.</para>
 
 	<note>
 	  <para>The <command>cvs login</command> command, stores the passwords
 	    that are used for authenticating to the CVS server in a file
 	    called <filename>.cvspass</filename> in your
 	    <envar>HOME</envar> directory.  If this file does not exist,
 	    you might get an error when trying to use <command>cvs
 	    login</command> for the first time.  Just make an empty
 	    <filename>.cvspass</filename> file, and retry to login.</para>
 	</note>
 
 	<para>While it can also be said that the <link
 	  linkend="cvsup">CVSup</link> and <emphasis>anoncvs</emphasis>
 	  services both perform essentially the same function, there are
 	  various trade-offs which can influence the user's choice of
 	  synchronization methods.  In a nutshell,
 	  <application>CVSup</application> is much more efficient in its
 	  usage of network resources and is by far the most technically
 	  sophisticated of the two, but at a price.  To use
 	  <application>CVSup</application>, a special client must first be
 	  installed and configured before any bits can be grabbed, and
 	  then only in the fairly large chunks which
 	  <application>CVSup</application> calls
 	  <emphasis>collections</emphasis>.</para>
 
 	<para><application>Anoncvs</application>, by contrast, can be used
 	  to examine anything from an individual file to a specific
 	  program (like <command>ls</command> or <command>grep</command>)
 	  by referencing the CVS module name.  Of course,
 	  <application>anoncvs</application> is also only good for
 	  read-only operations on the CVS repository, so if it is your
 	  intention to support local development in one repository shared
 	  with the FreeBSD project bits then
 	  <application>CVSup</application> is really your only
 	  option.</para>
       </sect2>
 
       <sect2>
 	<title><anchor id="anoncvs-usage">Using Anonymous CVS</title>
 
 	<para>Configuring &man.cvs.1; to use an Anonymous CVS repository
 	  is a simple matter of setting the <envar>CVSROOT</envar>
 	  environment variable to point to one of the FreeBSD project's
 	  <emphasis>anoncvs</emphasis> servers.  At the time of this
 	  writing, the following servers are available:</para>
 
 	<itemizedlist>
 	  <listitem>
 	    <para><emphasis>Austria</emphasis>:
 	      :pserver:anoncvs@anoncvs.at.FreeBSD.org:/home/ncvs
 	      (Use <command>cvs login</command> and enter any
 	      password when prompted.)</para>
 	  </listitem>
 	  <listitem>
 	    <para><emphasis>France</emphasis>:
 	      :pserver:anoncvs@anoncvs.fr.FreeBSD.org:/home/ncvs
 	      (pserver (password <quote>anoncvs</quote>), ssh (no password))
 	    </para>
 	  </listitem>
 	  <listitem>
 	    <para><emphasis>Germany</emphasis>:
 	      :pserver:anoncvs@anoncvs.de.FreeBSD.org:/home/ncvs
 	      (Use <command>cvs login</command> and enter the password
 	      <quote>anoncvs</quote> when prompted.)</para>
 	  </listitem>
 	  <listitem>
 	    <para><emphasis>Germany</emphasis>:
 	      :pserver:anoncvs@anoncvs2.de.FreeBSD.org:/home/ncvs
 	      (rsh, pserver, ssh, ssh/2022)
 	      </para>
 	  </listitem>
 	  <listitem>
 	    <para><emphasis>Japan</emphasis>:
 	      :pserver:anoncvs@anoncvs.jp.FreeBSD.org:/home/ncvs
 	      (Use <command>cvs login</command> and enter the password
 	      <quote>anoncvs</quote> when prompted.)</para>
 	  </listitem>
 	  <listitem>
 	    <para><emphasis>Sweden</emphasis>:
 	      freebsdanoncvs@anoncvs.se.FreeBSD.org:/home/ncvs
 	      (ssh only - no password)</para>
 
 	    <programlisting>SSH HostKey: 1024 a7:34:15:ee:0e:c6:65:cf:40:78:2d:f3:cd:87:bd:a6 root@apelsin.fruitsalad.org
 SSH2 HostKey: 1024 21:df:04:03:c7:26:3e:e8:36:1a:50:2d:c7:ae:b8:5f ssh_host_dsa_key.pub</programlisting>
 
 	  </listitem>
 	  <listitem>
 	    <para><emphasis>USA</emphasis>:
 	      freebsdanoncvs@anoncvs.FreeBSD.org:/home/ncvs
 	      (ssh only - no password)</para>
 
 	    <programlisting>SSH HostKey: 1024 a1:e7:46:de:fb:56:ef:05:bc:73:aa:91:09:da:f7:f4 root@sanmateo.ecn.purdue.edu
 SSH2 HostKey: 1024 52:02:38:1a:2f:a8:71:d3:f5:83:93:8d:aa:00:6f:65 ssh_host_dsa_key.pub</programlisting>
 
 	  </listitem>
 	  <listitem>
 	    <para><emphasis>USA</emphasis>:
 	      anoncvs@anoncvs1.FreeBSD.org:/home/ncvs (ssh only - no
 	      password)</para>
 
 	    <programlisting>SSH HostKey: 1024 4b:83:b6:c5:70:75:6c:5b:18:8e:3a:7a:88:a0:43:bb root@ender.liquidneon.com
 SSH2 HostKey: 1024 80:a7:87:fa:61:d9:25:5c:33:d5:48:51:aa:8f:b6:12 ssh_host_dsa_key.pub</programlisting>
 
 	  </listitem>
 	</itemizedlist>
 
 	<para>Since CVS allows one to <quote>check out</quote> virtually
 	  any version of the FreeBSD sources that ever existed (or, in
 	  some cases, will exist), you need to be
 	  familiar with the revision (<option>-r</option>) flag to
 	  &man.cvs.1; and what some of the permissible values for it in
 	  the FreeBSD Project repository are.</para>
 
 	<para>There are two kinds of tags, revision tags and branch tags.
 	  A revision tag refers to a specific revision.  Its meaning stays
 	  the same from day to day.  A branch tag, on the other hand,
 	  refers to the latest revision on a given line of development, at
 	  any given time.  Because a branch tag does not refer to a
 	  specific revision, it may mean something different tomorrow than
 	  it means today.</para>
 
 	<para><xref linkend="cvs-tags"> contains revision tags that users
  	  might be interested
 	  in.  Again, none of these are valid for the Ports Collection
 	  since the Ports Collection does not have multiple
 	  revisions.</para>
 
 	<para>When you specify a branch tag, you normally receive the
 	  latest versions of the files on that line of development.  If
 	  you wish to receive some past version, you can do so by
 	  specifying a date with the <option>-D date</option> flag.
 	  See the &man.cvs.1; manual page for more details.</para>
       </sect2>
 
       <sect2>
 	<title>Examples</title>
 
 	<para>While it really is recommended that you read the manual page
 	  for &man.cvs.1; thoroughly before doing anything, here are some
 	  quick examples which essentially show how to use Anonymous
 	  CVS:</para>
 
 	<example>
 	  <title>Checking Out Something from -CURRENT (&man.ls.1;):</title>
 
 	  <screen>&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.jp.FreeBSD.org:/home/ncvs</userinput>
 &prompt.user; <userinput>cvs login</userinput>
 <emphasis>At the prompt, enter the password</emphasis> <quote>anoncvs</quote>.
 &prompt.user; <userinput>cvs co ls</userinput>
 	  </screen>
 	</example>
 
 	<example>
 	  <title>Using SSH to check out the <filename>src/</filename>
 	    tree:</title>
 	  <screen>&prompt.user; <userinput>cvs -d freebsdanoncvs@anoncvs.FreeBSD.org:/home/ncvs co src</userinput>
 The authenticity of host 'anoncvs.freebsd.org (128.46.156.46)' can't be established.
 DSA key fingerprint is 52:02:38:1a:2f:a8:71:d3:f5:83:93:8d:aa:00:6f:65.
 Are you sure you want to continue connecting (yes/no)? <userinput>yes</userinput>
 Warning: Permanently added 'anoncvs.freebsd.org' (DSA) to the list of known hosts.</screen>
 	</example>
 
 	<example>
 	  <title>Checking Out the Version of &man.ls.1; in the 6-STABLE
 	    Branch:</title>
 
 	  <screen>&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.jp.FreeBSD.org:/home/ncvs</userinput>
 &prompt.user; <userinput>cvs login</userinput>
 <emphasis>At the prompt, enter the password</emphasis> <quote>anoncvs</quote>.
 &prompt.user; <userinput>cvs co -rRELENG_6 ls</userinput>
 	  </screen>
 	</example>
 
 	<example>
 	  <title>Creating a List of Changes (as Unified Diffs) to &man.ls.1;</title>
 
 	  <screen>&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.jp.FreeBSD.org:/home/ncvs</userinput>
 &prompt.user; <userinput>cvs login</userinput>
 <emphasis>At the prompt, enter the password</emphasis> <quote>anoncvs</quote>.
 &prompt.user; <userinput>cvs rdiff -u -rRELENG_5_3_0_RELEASE -rRELENG_5_4_0_RELEASE ls</userinput>
 	  </screen>
 	</example>
 
 	<example>
 	  <title>Finding Out What Other Module Names Can Be Used:</title>
 
 	  <screen>&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.jp.FreeBSD.org:/home/ncvs</userinput>
 &prompt.user; <userinput>cvs login</userinput>
 <emphasis>At the prompt, enter the password</emphasis> <quote>anoncvs</quote>.
 &prompt.user; <userinput>cvs co modules</userinput>
 &prompt.user; <userinput>more modules/modules</userinput>
 	  </screen>
 	</example>
       </sect2>
 
       <sect2>
 	<title>Other Resources</title>
 
 	<para>The following additional resources may be helpful in learning
 	  CVS:</para>
 
 	<itemizedlist>
 	  <listitem>
 	    <para><ulink 
 		url="http://www.csc.calpoly.edu/~dbutler/tutorials/winter96/cvs/">CVS Tutorial</ulink> from Cal Poly.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para><ulink url="http://www.cvshome.org/">CVS Home</ulink>,
 	      the CVS development and support community.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para><ulink
 		url="http://www.FreeBSD.org/cgi/cvsweb.cgi">CVSweb</ulink> is
 	      the FreeBSD Project web interface for CVS.</para>
 	  </listitem>
 	</itemizedlist>
       </sect2>
     </sect1>
     
     
   <sect1 id="ctm">
     <title>Using CTM</title>
 
       <indexterm>
 	<primary>CTM</primary>
       </indexterm>
 
       <para><application>CTM</application> is a method for keeping a
 	remote directory tree in sync with a central one.  It has been
 	developed for usage with FreeBSD's source trees, though other
 	people may find it useful for other purposes as time goes by.
 	Little, if any, documentation currently exists at this time on the
 	process of creating deltas, so contact the &a.ctm-users.name; mailing list for more
 	information and if you wish to use <application>CTM</application>
 	for other things.</para>
 
       <sect2>
 	<title>Why Should I Use <application>CTM</application>?</title>
 
 	<para><application>CTM</application> will give you a local copy of
 	  the FreeBSD source trees.  There are a number of
 	  <quote>flavors</quote> of the tree available.  Whether you wish
 	  to track the entire CVS tree or just one of the branches,
 	  <application>CTM</application> can provide you the information.
 	  If you are an active developer on FreeBSD, but have lousy or
 	  non-existent TCP/IP connectivity, or simply wish to have the
 	  changes automatically sent to you,
 	  <application>CTM</application> was made for you.  You will need
 	  to obtain up to three deltas per day for the most  active
 	  branches.  However, you should consider having them sent by
 	  automatic email.  The sizes of the updates are always kept as
 	  small as possible.  This is typically less than 5K, with an
 	  occasional (one in ten) being 10-50K and every now and then a
 	  large 100K+ or more coming around.</para>
 
 	<para>You will also need to make yourself aware of the various
 	  caveats related to working directly from the development sources
 	  rather than a pre-packaged release.  This is particularly true
 	  if you choose the <quote>current</quote> sources.  It is
 	  recommended that you read <link linkend="current">Staying
 	  current with FreeBSD</link>.</para>
       </sect2>
 
       <sect2>
 	<title>What Do I Need to Use
 	  <application>CTM</application>?</title>
 
 	<para>You will need two things: The <application>CTM</application>
 	  program, and the initial deltas to feed it (to get up to
 	  <quote>current</quote> levels).</para>
 	    
 	<para>The <application>CTM</application> program has been part of
 	  FreeBSD ever since version 2.0 was released, and lives in
 	  <filename>/usr/src/usr.sbin/ctm</filename> if you have a copy
 	  of the source available.</para>
 
 	<para>The <quote>deltas</quote> you feed
 	  <application>CTM</application> can be had two ways, FTP or
 	  email.  If you have general FTP access to the Internet then the
 	  following FTP sites support access to
 	  <application>CTM</application>:</para>
 
 	<para><ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/CTM/"></ulink></para>
 
 	<para>or see section <link
 	  linkend="mirrors-ctm">mirrors</link>.</para>
 
 	<para>FTP the relevant directory and fetch the
 	  <filename>README</filename> file, starting from there.</para>
 
 	<para>If you wish to get your deltas via email:</para>
 
 	<para>Subscribe to one of the
 	  <application>CTM</application> distribution lists.
 	  &a.ctm-cvs-cur.name; supports the entire CVS tree.
 	  &a.ctm-src-cur.name; supports the head of the development
 	  branch.  &a.ctm-src-4.name; supports the 4.X release
 	  branch, etc..  (If you do not know how to subscribe yourself
 	  to a list, click on the list name above or go to
 	  &a.mailman.lists.link; and click on the list that you
 	  wish to subscribe to.  The list page should contain all of
 	  the necessary subscription instructions.)</para>
 
 	<para>When you begin receiving your <application>CTM</application>
 	  updates in the mail, you may use the
 	  <command>ctm_rmail</command> program to unpack and apply them.
 	  You can actually use the <command>ctm_rmail</command> program
 	  directly from a entry in <filename>/etc/aliases</filename> if
 	  you want to have the process run in a fully automated fashion.
 	  Check the <command>ctm_rmail</command> manual page for more
 	  details.</para>
 
 	<note>
 	  <para>No matter what method you use to get the
 	    <application>CTM</application> deltas, you should subscribe to
 	    the &a.ctm-announce.name; mailing list.  In
 	    the future, this will be the only place where announcements
 	    concerning the operations of the
 	    <application>CTM</application> system will be posted.  Click
 	    on the list name above and follow the instructions
 	    to subscribe to the
 	    list.</para>
 	</note>
       </sect2>
 
       <sect2>
 	<title>Using <application>CTM</application> for the First
 	  Time</title>
 
 	<para>Before you can start using <application>CTM</application>
 	  deltas, you will need to get to a starting point for the deltas
 	  produced subsequently to it.</para>
 
 	<para>First you should determine what you already have.  Everyone
 	  can start from an <quote>empty</quote> directory.  You must use
 	  an initial <quote>Empty</quote> delta to start off your
 	  <application>CTM</application> supported tree.  At some point it
 	  is intended that one of these <quote>started</quote> deltas be
 	  distributed on the CD for your convenience, however, this does
 	  not currently happen.</para>
 
 	<para>Since the trees are many tens of megabytes, you should
 	  prefer to start from something already at hand.  If you have a
 	  -RELEASE CD, you can copy or extract an initial source from it.
 	  This will save a significant transfer of data.</para>
 
 	<para>You can recognize these <quote>starter</quote> deltas by the
 	  <literal>X</literal> appended to the number
 	  (<filename>src-cur.3210XEmpty.gz</filename> for instance).  The
 	  designation following the <literal>X</literal> corresponds to
 	  the origin of your initial <quote>seed</quote>.
 	  <filename>Empty</filename> is an empty directory.  As a rule a
 	  base transition from <literal>Empty</literal> is produced
 	  every 100 deltas.  By the way, they are large! 70 to 80
 	  Megabytes of <command>gzip</command>'d data is common for the
 	  <filename>XEmpty</filename> deltas.</para>
 
 	<para>Once you have picked a base delta to start from, you will also
 	  need all deltas with higher numbers following it.</para>
       </sect2>
 
       <sect2>
 	<title>Using <application>CTM</application> in Your Daily
 	  Life</title>
 
 	<para>To apply the deltas, simply say:</para>
 
 	<screen>&prompt.root; <userinput>cd /where/ever/you/want/the/stuff</userinput>
 &prompt.root; <userinput>ctm -v -v /where/you/store/your/deltas/src-xxx.*</userinput></screen>
 
 	<para><application>CTM</application> understands deltas which have
 	  been put through <command>gzip</command>, so you do not need to
 	  <command>gunzip</command> them first, this saves disk space.</para>
 
 	<para>Unless it feels very secure about the entire process,
 	  <application>CTM</application> will not touch your tree.  To
 	  verify a delta you can also use the <option>-c</option> flag and
 	  <application>CTM</application> will not actually touch your
 	  tree; it will merely verify the integrity of the delta and see
 	  if it would apply cleanly to your current tree.</para>
 
 	<para>There are other options to <application>CTM</application>
 	  as well, see the manual pages or look in the sources for more
 	  information.</para>
 
 	<para>That is really all there is to it.  Every time you get a new
 	  delta, just run it through <application>CTM</application> to
 	  keep your sources up to date.</para>
 
 	<para>Do not remove the deltas if they are hard to download again.
 	  You just might want to keep them around in case something bad
 	  happens.  Even if you only have floppy disks, consider using
 	  <command>fdwrite</command> to make a copy.</para>
       </sect2>
 
       <sect2>
 	<title>Keeping Your Local Changes</title>
 
 	<para>As a developer one would like to experiment with and change
 	  files in the source tree.  <application>CTM</application>
 	  supports local modifications in a limited way: before checking
 	  for the presence of a file <filename>foo</filename>, it first
 	  looks for <filename>foo.ctm</filename>.  If this file exists,
 	  <application>CTM</application> will operate on it instead of
 	  <filename>foo</filename>.</para>
 
 	<para>This behavior gives us a simple way to maintain local
 	  changes:  simply copy the files you plan to modify to the
 	  corresponding file names with a <filename>.ctm</filename>
 	  suffix.  Then you can freely hack  the code, while <application>CTM</application> keeps the
 	  <filename>.ctm</filename> file up-to-date.</para>
       </sect2>
 
       <sect2>
 	<title>Other Interesting <application>CTM</application> Options</title>
 
 	<sect3>
 	  <title>Finding Out Exactly What Would Be Touched by an
 	    Update</title>
 
 	  <para>You can determine the list of changes that
 	    <application>CTM</application> will make on your source
 	    repository using the <option>-l</option> option to
 	    <application>CTM</application>.</para>
 
 	  <para>This is useful if you would like to keep logs of the
 	    changes, pre- or post- process the modified files in any
 	    manner, or just are feeling a tad paranoid.</para>
 	</sect3>
 
 	<sect3>
 	  <title>Making Backups Before Updating</title>
 
 	  <para>Sometimes you may want to backup all the files that would
 	    be changed by a <application>CTM</application> update.</para>
 
 	  <para>Specifying the <option>-B backup-file</option> option
 	    causes <application>CTM</application> to backup all files that
 	    would be touched by a given <application>CTM</application>
 	    delta to <filename>backup-file</filename>.</para>
 	</sect3>
 
 	<sect3>
 	  <title>Restricting the Files Touched by an Update</title>
 
 	  <para>Sometimes you would be interested in restricting the scope
 	    of a given <application>CTM</application> update, or may be
 	    interested in extracting just a few files from a sequence of
 	    deltas.</para>
 
 	  <para>You can control the list of files that
 	    <application>CTM</application> would operate on by specifying
 	    filtering regular expressions using the <option>-e</option>
 	    and <option>-x</option> options.</para>
 
 	  <para>For example, to extract an up-to-date copy of
 	    <filename>lib/libc/Makefile</filename> from your collection of
 	    saved <application>CTM</application> deltas, run the commands:</para>
 
 	  <screen>&prompt.root; <userinput>cd /where/ever/you/want/to/extract/it/</userinput>
 &prompt.root; <userinput>ctm -e '^lib/libc/Makefile' ~ctm/src-xxx.*</userinput></screen>
 
 	  <para>For every file specified in a
 	    <application>CTM</application> delta, the <option>-e</option>
 	    and <option>-x</option> options are applied in the order given
 	    on the command line.  The file is processed by
 	    <application>CTM</application> only if it is marked as
 	    eligible after all the <option>-e</option> and
 	    <option>-x</option> options are applied to it.</para>
 	</sect3>
       </sect2>
 
       <sect2>
 	<title>Future Plans for <application>CTM</application></title>
 
 	<para>Tons of them:</para>
 
 	<itemizedlist>
 	  <listitem>
 	    <para>Use some kind of authentication into the <application>CTM</application> system, so
 	      as to allow detection of spoofed <application>CTM</application> updates.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>Clean up the options to <application>CTM</application>,
 	      they became confusing and counter intuitive.</para>
 	  </listitem>
 	</itemizedlist>
       </sect2>
 
       <sect2>
 	<title>Miscellaneous Stuff</title>
 
 	<para>There is a sequence of deltas for the
 	  <literal>ports</literal> collection too, but interest has not
 	  been all that high yet.</para>
       </sect2>
 
     <sect2 id="mirrors-ctm">
       <title>CTM Mirrors</title>
       
     <para><link linkend="ctm">CTM</link>/FreeBSD is available via anonymous
       FTP from the following mirror sites.  If you choose to obtain <application>CTM</application> via
       anonymous FTP, please try to use a site near you.</para>
 
     <para>In case of problems, please contact the &a.ctm-users.name;
       mailing list.</para>
 
     <variablelist>
       <varlistentry>
 	<term>California, Bay Area, official source</term>
 
 	<listitem>
 	  <itemizedlist>
 	    <listitem>
 	      <para><ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CTM/"></ulink></para>
 	    </listitem>
 	  </itemizedlist>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>South Africa, backup server for old deltas</term>
 
 	<listitem>
 	  <itemizedlist>
 	    <listitem>
 	      <para><ulink url="ftp://ftp.za.FreeBSD.org/pub/FreeBSD/CTM/"></ulink></para>
 	    </listitem>
 	  </itemizedlist>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>Taiwan/R.O.C.</term>
 
 	<listitem>
 	  <itemizedlist>
 	    <listitem>
 	      <para><ulink url="ftp://ctm.tw.FreeBSD.org/pub/FreeBSD/development/CTM/"></ulink></para>
 	    </listitem>
 
 	    <listitem>
 	      <para><ulink url="ftp://ctm2.tw.FreeBSD.org/pub/FreeBSD/development/CTM/"></ulink></para>
 	    </listitem>
 
 	    <listitem>
 	      <para><ulink url="ftp://ctm3.tw.FreeBSD.org/pub/FreeBSD/development/CTM/"></ulink></para>
 	    </listitem>
 	  </itemizedlist>
 	</listitem>
       </varlistentry>
     </variablelist>
 
     <para>If you did not find a mirror near to you or the mirror is
       incomplete, try to use a search engine such as
       <ulink url="http://www.alltheweb.com/">alltheweb</ulink>.</para>
   </sect2></sect1>
 
   <sect1 id="cvsup">
     <title>Using CVSup</title>
     
     <sect2 id="cvsup-intro">
       <title>Introduction</title>
       
       <para><application>CVSup</application> is a software package for
 	distributing and updating source trees from a master CVS
 	repository on a remote server host.  The FreeBSD sources are
 	maintained in a CVS repository on a central development machine
 	in California.  With <application>CVSup</application>, FreeBSD
 	users can easily keep their own source trees up to date.</para>
       
       <para><application>CVSup</application> uses the so-called
 	<emphasis>pull</emphasis> model of updating.  Under the pull
 	model, each client asks the server for updates, if and when they
 	are wanted.  The server waits passively for update requests from
 	its clients.  Thus all updates are instigated by the client.
 	The server never sends unsolicited updates.  Users must either
 	run the <application>CVSup</application> client manually to get
 	an update, or they must set up a <command>cron</command> job to
 	run it automatically on a regular basis.</para>
       
       <para>The term <application>CVSup</application>, capitalized just
 	so, refers to the entire software package.  Its main components
 	are the client <command>cvsup</command> which runs on each
 	user's machine, and the server <command>cvsupd</command> which
 	runs at each of the FreeBSD mirror sites.</para>
 
       <para>As you read the FreeBSD documentation and mailing lists, you
 	may see references to <application>sup</application>.
 	<application>Sup</application> was the predecessor of
 	<application>CVSup</application>, and it served a similar
 	purpose.  <application>CVSup</application> is used much in the
 	same way as sup and, in fact, uses configuration files which are
 	backward-compatible with <command>sup</command>'s.
 	<application>Sup</application> is no longer used in the FreeBSD
 	project, because <application>CVSup</application> is both faster
 	and more flexible.</para>
     </sect2>
 
     <sect2 id="cvsup-install">
       <title>Installation</title>
       
       <para>The easiest way to install <application>CVSup</application>
 	is to use the precompiled <filename role="package">net/cvsup</filename> package
 	from the FreeBSD <link linkend="ports">packages collection</link>.
 	If you prefer to build <application>CVSup</application> from
 	source, you can use the <filename role="package">net/cvsup</filename>
 	port instead.  But be forewarned: the
 	<filename role="package">net/cvsup</filename> port depends on the Modula-3
 	system, which takes a substantial amount of time and
 	disk space to download and build.</para>
 
 	<note>
 	  <para>If you are going to be using
 	  <application>CVSup</application> on a machine which will not have
 	  <application>&xfree86;</application> or <application>&xorg;</application> installed, such as a server, be
 	  sure to use the port which does not include the
 	  <application>CVSup</application> <acronym>GUI</acronym>,
 	  <filename role="package">net/cvsup-without-gui</filename>.</para>
 	</note>
     </sect2>
 
     <sect2 id="cvsup-config">
       <title>CVSup Configuration</title>
       
       <para><application>CVSup</application>'s operation is controlled
 	by a configuration file called the <filename>supfile</filename>.
 	There are some sample <filename>supfiles</filename> in the
 	directory <ulink type="html"
 	  url="file://localhost/usr/share/examples/cvsup/"><filename>/usr/share/examples/cvsup/</filename></ulink>.</para>
       
       <para>The information in a <filename>supfile</filename> answers
 	the following questions for <application>CVSup</application>:</para>
       
       <itemizedlist>
 	<listitem>
 	  <para><link linkend="cvsup-config-files">Which files do you
 	      want to receive?</link></para>
 	</listitem>
 	
 	<listitem>
 	  <para><link linkend="cvsup-config-vers">Which versions of them
 	      do you want?</link></para>
 	</listitem>
 	
 	<listitem>
 	  <para><link linkend="cvsup-config-where">Where do you want to
 	      get them from?</link></para>
 	</listitem>
 	
 	<listitem>
 	  <para><link linkend="cvsup-config-dest">Where do you want to
 	      put them on your own machine?</link></para>
 	</listitem>
 	
 	<listitem>
 	  <para><link linkend="cvsup-config-status">Where do you want to
 	      put your status files?</link></para>
 	</listitem>
       </itemizedlist>
 
       <para>In the following sections, we will construct a typical
 	<filename>supfile</filename> by answering each of these
 	questions in turn.  First, we describe the overall structure of
 	a <filename>supfile</filename>.</para>
 
       <para>A <filename>supfile</filename> is a text file.  Comments
 	begin with <literal>#</literal> and extend to the end of the
 	line.  Lines that are blank and lines that contain only
 	comments are ignored.</para>
       
       <para>Each remaining line describes a set of files that the user
 	wishes to receive.  The line begins with the name of a
 	<quote>collection</quote>, a logical grouping of files defined by
 	the server. The name of the collection tells the server which
 	files you want.  After the collection name come zero or more
 	fields, separated by white space.  These fields answer the
 	questions listed above.  There are two types of fields: flag
 	fields and value fields.  A flag field consists of a keyword
 	standing alone, e.g., <literal>delete</literal> or
 	<literal>compress</literal>.  A value field also begins with a
 	keyword, but the keyword is followed without intervening white
 	space by <literal>=</literal> and a second word.  For example,
 	<literal>release=cvs</literal> is a value field.</para>
       
       <para>A <filename>supfile</filename> typically specifies more than
 	one collection to receive.  One way to structure a
 	<filename>supfile</filename> is to specify all of the relevant
 	fields explicitly for each collection.  However, that tends to
 	make the <filename>supfile</filename> lines quite long, and it
 	is inconvenient because most fields are the same for all of the
 	collections in a <filename>supfile</filename>.
 	<application>CVSup</application> provides a defaulting mechanism
 	to avoid these problems.  Lines beginning with the special
 	pseudo-collection name <literal>*default</literal> can be used
 	to set flags and values which will be used as defaults for the
 	subsequent collections in the <filename>supfile</filename>.  A
 	default value can be overridden for an individual collection, by
 	specifying a different value with the collection itself.
 	Defaults can also be changed or augmented in mid-supfile by
 	additional <literal>*default</literal> lines.</para>
 
       <para>With this background, we will now proceed to construct a
 	<filename>supfile</filename> for receiving and updating the main
 	source tree of <link
 	  linkend="current">FreeBSD-CURRENT</link>.</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><anchor id="cvsup-config-files">Which files do you want
 	    to receive?</para>
 	  
 	  <para>The files available via <application>CVSup</application>
 	    are organized into named groups called
 	    <quote>collections</quote>.  The collections that are
 	    available are described in the <link
 	      linkend="cvsup-collec">following section</link>.  In this
 	    example, we
 	    wish to receive the entire main source tree for the FreeBSD
 	    system.  There is a single large collection
 	    <literal>src-all</literal> which will give us all of that.
 	    As a first step toward constructing our
 	    <filename>supfile</filename>, we
 	    simply list the collections, one per line (in this case,
 	    only one line):</para>
 
 	  <programlisting>src-all</programlisting>
 	</listitem>
 
 	<listitem>
 	  <para><anchor id="cvsup-config-vers">Which version(s) of them
 	    do you want?</para>
 
 	  <para>With <application>CVSup</application>, you can receive
 	    virtually any version of the sources that ever existed.
 	    That is possible because the
 	    <application>cvsupd</application> server works directly from
 	    the CVS repository, which contains all of the versions.  You
 	    specify which one of them you want using the
 	    <literal>tag=</literal> and <option>date=</option> value
 	    fields.</para>
 	  
 	  <warning>
 	    <para>Be very careful to specify any <literal>tag=</literal>
 	      fields correctly.  Some tags are valid only for certain
 	      collections of files.  If you specify an incorrect or
 	      misspelled tag, <application>CVSup</application>
 	      will delete files which you probably
 	      do not want deleted.  In particular, use <emphasis>only
 	      </emphasis> <literal>tag=.</literal> for the
 	      <literal>ports-*</literal> collections.</para>
 	  </warning>
 
 	  <para>The <literal>tag=</literal> field names a symbolic tag
 	    in the repository.  There are two kinds of tags, revision
 	    tags and branch tags.  A revision tag refers to a specific
 	    revision.  Its meaning stays the same from day to day.  A
 	    branch tag, on the other hand, refers to the latest revision
 	    on a given line of development, at any given time.  Because
 	    a branch tag does not refer to a specific revision, it may
 	    mean something different tomorrow than it means
 	    today.</para>
 	  
 	  <para><xref linkend="cvs-tags"> contains branch tags that
 	    users might be interested in.  When specifying a tag in
 	    <application>CVSup</application>'s configuration file, it
 	    must be preceded with <literal>tag=</literal>
 	    (<literal>RELENG_4</literal> will become
 	    <literal>tag=RELENG_4</literal>).
 	    Keep in mind that only the <literal>tag=.</literal> is
 	    relevant for the Ports Collection.</para>
 
 	  <warning>
 	    <para>Be very careful to type the tag name exactly as shown.
 	      <application>CVSup</application> cannot distinguish
 	      between valid and invalid tags.  If you misspell the tag,
 	      <application>CVSup</application> will behave as though you
 	      had specified a valid tag which happens to refer to no
 	      files at all.  It will delete your existing sources in
 	      that case.</para>
 	  </warning>
 
 	  <para>When you specify a branch tag, you normally receive the
 	    latest versions of the files on that line of development.
 	    If you wish to receive some past version, you can do so by
 	    specifying a date with the <option>date=</option> value
 	    field. The &man.cvsup.1; manual page explains how to do
 	    that.</para>
 
 	  <para>For our example, we wish to receive FreeBSD-CURRENT.  We
 	    add this line at the beginning of our
 	    <filename>supfile</filename>:</para>
 	  
 	  <programlisting>*default tag=.</programlisting>
 
 	  <para>There is an important special case that comes into play
 	    if you specify neither a <literal>tag=</literal> field nor a
 	    <literal>date=</literal> field.  In that case, you receive
 	    the actual RCS files directly from the server's CVS
 	    repository, rather than receiving a particular version.
 	    Developers generally prefer this mode of operation.  By
 	    maintaining a copy of the repository itself on their
 	    systems, they gain the ability to browse the revision
 	    histories and examine past versions of files.  This gain is
 	    achieved at a large cost in terms of disk space,
 	    however.</para>
 	</listitem>
 
 	<listitem>
 	  <para><anchor id="cvsup-config-where">Where do you want to get
 	    them from?</para>
 	  
 	  <para>We use the <literal>host=</literal> field to tell
 	    <command>cvsup</command> where to obtain its updates.  Any
 	    of the <link linkend="cvsup-mirrors">CVSup mirror
 	      sites</link> will do, though you should try to select one
 	    that is close to you in cyberspace.  In this example we will
 	    use a fictional FreeBSD distribution site,
 	    <hostid role="fqdn">cvsup99.FreeBSD.org</hostid>:</para>
 
 	  <programlisting>*default host=cvsup99.FreeBSD.org</programlisting>
 	  
 	  <para>You will need to change the host to one that actually
 	    exists before running <application>CVSup</application>.
 	    On any particular run of
 	    <command>cvsup</command>, you can override the host  setting
 	    on the command line, with <option>-h
 	      <replaceable>hostname</replaceable></option>.</para>
 	</listitem>
 	
 	<listitem>
 	  <para><anchor id="cvsup-config-dest">Where do you want to put
 	    them on your own machine?</para>
 	  
 	  <para>The <literal>prefix=</literal> field tells
 	    <command>cvsup</command> where to put the files it receives.
 	    In this example, we will put the source files directly into
 	    our main source tree, <filename>/usr/src</filename>.  The
 	    <filename>src</filename> directory is already implicit in
 	    the collections we have chosen to receive, so this is the
 	    correct specification:</para>
 	  
 	  <programlisting>*default prefix=/usr</programlisting>
 	</listitem>
 
 	<listitem>
 	  <para><anchor id="cvsup-config-status">Where should
 	    <command>cvsup</command> maintain its status files?</para>
 
 	  <para>The <application>CVSup</application> client maintains
 	    certain status files in what
 	    is called the <quote>base</quote> directory.  These files
 	    help <application>CVSup</application> to work more
 	    efficiently, by keeping track of which updates you have
 	    already received.  We will use the standard base directory,
 	    <filename>/var/db</filename>:</para>
 
 	  <programlisting>*default base=/var/db</programlisting>
 
 	  <para>If your base directory does not already exist, now would
 	    be a good time to create it.  The <command>cvsup</command>
 	    client will refuse to run if the base directory does not
 	    exist.</para>
 	</listitem>
 
 	<listitem>
 	  <para>Miscellaneous <filename>supfile</filename>
 	    settings:</para>
 	  
 	  <para>There is one more line of boiler plate that normally
 	    needs to be present in the
 	    <filename>supfile</filename>:</para>
 
 	  <programlisting>*default release=cvs delete use-rel-suffix compress</programlisting>
 
 	  <para><literal>release=cvs</literal> indicates that the server
 	    should get its information out of the main FreeBSD CVS
 	    repository.  This is virtually always the case, but there
 	    are other possibilities which are beyond the scope of this
 	    discussion.</para>
 	  
 	  <para><literal>delete</literal> gives
 	    <application>CVSup</application> permission to delete files.
 	    You should always specify this, so that
 	    <application>CVSup</application> can keep your source tree
 	    fully up-to-date.  <application>CVSup</application> is
 	    careful to delete only those files for which it is
 	    responsible.  Any extra files you happen to have will be
 	    left strictly alone.</para>
 	  
 	  <para><literal>use-rel-suffix</literal> is ... arcane.  If you
 	    really want to know about it, see the &man.cvsup.1; manual
 	    page.  Otherwise, just specify it and do not worry about
 	    it.</para>
 
 	  <para><literal>compress</literal> enables the use of
 	    gzip-style compression on the communication channel.  If
 	    your network link is T1 speed or faster, you probably should
 	    not use compression.  Otherwise, it helps
 	    substantially.</para>
 	</listitem>
 
 	<listitem>
 	  <para>Putting it all together:</para>
 
 	  <para>Here is the entire <filename>supfile</filename> for our
 	    example:</para>
 
 	  <programlisting>*default tag=.
 *default host=cvsup99.FreeBSD.org
 *default prefix=/usr
 *default base=/var/db
 *default release=cvs delete use-rel-suffix compress
 
 src-all</programlisting>
 	</listitem>
       </itemizedlist>
       <sect3 id="cvsup-refuse-file">
        <title>The <filename>refuse</filename> File</title>
 
        <para>As mentioned above, <application>CVSup</application> uses
        a <emphasis>pull method</emphasis>. Basically, this means that
        you connect to the <application>CVSup</application> server, and
        it says, <quote>Here is what you can download from
        me...</quote>, and your client responds <quote>OK, I will take
        this, this, this, and this.</quote> In the default
        configuration, the <application>CVSup</application> client will
        take every file associated with the collection and tag you
        chose in the configuration file. However, this is not always
        what you want, especially if you are synching the <filename>doc</filename>, <filename>ports</filename>, or
        <filename>www</filename> trees &mdash; most people cannot read four or five
        languages, and therefore they do not need to download the
        language-specific files. If you are
        <application>CVSup</application>ing the Ports Collection, you
        can get around this by specifying each collection individually
        (e.g., <emphasis>ports-astrology</emphasis>,
        <emphasis>ports-biology</emphasis>, etc instead of simply
        saying <emphasis>ports-all</emphasis>). However, since the <filename>doc</filename>
        and <filename>www</filename> trees do not have language-specific collections, you
        must use one of <application>CVSup</application>'s many nifty
        features: the <filename>refuse</filename> file.</para>
 
        <para>The <filename>refuse</filename> file essentially tells
        <application>CVSup</application> that it should not take every
        single file from a collection; in other words, it tells the
        client to <emphasis>refuse</emphasis> certain files from the
        server. The <filename>refuse</filename> file can be found (or, if you do not yet
        have one, should be placed) in
        <filename><replaceable>base</replaceable>/sup/</filename>.
        <replaceable>base</replaceable> is defined in your <filename>supfile</filename>;
        our defined <replaceable>base</replaceable> is
        <filename>/var/db</filename>, 
        which means that by default the <filename>refuse</filename> file is
        <filename>/var/db/sup/refuse</filename>.</para>
 
        <para>The <filename>refuse</filename> file has a very simple format; it simply
        contains the names of files or directories that you do not wish
        to download.  For example, if you cannot speak any languages other
        than English and some German, and you do not feel the need to read
        the German translation of documentation, you can put the following in your
        <filename>refuse</filename> file:</para>
 
        <screen>doc/bn_*
 doc/da_*
 doc/de_*
 doc/el_*
 doc/es_*
 doc/fr_*
 doc/it_*
 doc/ja_*
 doc/nl_*
 doc/no_*
 doc/pl_*
 doc/pt_*
 doc/ru_*
 doc/sr_*
 doc/tr_*
 doc/zh_*</screen>
 
        <para>and so forth for the other languages (you can find the
        full list by browsing the <ulink
        url="http://www.FreeBSD.org/cgi/cvsweb.cgi/">FreeBSD
        CVS repository</ulink>).</para>
 
        <para>With this very useful feature, those users who are on
        slow links or pay by the minute for their Internet connection
        will be able to save valuable time as they will no longer need
        to download files that they will never use. For more
        information on <filename>refuse</filename> files and other neat
        features of <application>CVSup</application>, please view its
        manual page.</para> 
       </sect3>
     </sect2>
     
     <sect2>
       <title>Running <application>CVSup</application></title>
       
       <para>You are now ready to try an update.  The command line for
 	doing this is quite simple:</para>
 
       <screen>&prompt.root; <userinput>cvsup <replaceable>supfile</replaceable></userinput></screen>
 
       <para>where <filename><replaceable>supfile</replaceable></filename>
 	is of course the name of the <filename>supfile</filename> you have just created. 
 	Assuming you are running under X11, <command>cvsup</command>
 	will display a GUI window with some buttons to do the usual
 	things.  Press the <guibutton>go</guibutton> button, and watch it
 	run.</para>
       
       <para>Since you are updating your actual
 	<filename>/usr/src</filename> tree in this example, you will
 	need to run the program as <username>root</username> so that
 	<command>cvsup</command> has the permissions it needs to update
 	your files.  Having just created your configuration file, and
 	having never used this program before, that might
 	understandably make you nervous. There is an easy way to do a
 	trial run without touching your precious files.  Just create an
 	empty directory somewhere convenient, and name it as an extra
 	argument on the command line:</para>
 
       <screen>&prompt.root; <userinput>mkdir /var/tmp/dest</userinput>
 &prompt.root; <userinput>cvsup supfile /var/tmp/dest</userinput></screen>
       
       <para>The directory you specify will be used as the destination
 	directory for all file updates.
 	<application>CVSup</application> will examine your usual files
 	in <filename>/usr/src</filename>, but it will not modify or
 	delete any of them.  Any file updates will instead land in
 	<filename>/var/tmp/dest/usr/src</filename>.
 	<application>CVSup</application> will also leave its base
 	directory status files untouched when run this way.  The new
 	versions of those files will be written into the specified
 	directory.  As long as you have read access to
 	<filename>/usr/src</filename>, you do not even need to be
 	<username>root</username> to perform this kind of trial run.</para>
       
       <para>If you are not running X11 or if you just do not like GUIs,
 	you should add a couple of options to the command line when you
 	run <command>cvsup</command>:</para>
       
       <screen>&prompt.root; <userinput>cvsup -g -L 2 <replaceable>supfile</replaceable></userinput></screen>
 	    
       <para>The <option>-g</option> tells
 	<application>CVSup</application> not to use its GUI.  This is
 	automatic if you are not running X11, but otherwise you have to
 	specify it.</para>
       
       <para>The <option>-L 2</option> tells 
 	<application>CVSup</application> to print out the
 	details of all the file updates it is doing.  There are three
 	levels of verbosity, from <option>-L 0</option> to
 	<option>-L 2</option>.  The default is 0, which means total
 	silence except for error messages.</para>
       
       <para>There are plenty of other options available.  For a brief
 	list of them, type <command>cvsup -H</command>.  For more
 	detailed descriptions, see the manual page.</para>
 
       <para>Once you are satisfied with the way updates are working, you
 	can arrange for regular runs of <application>CVSup</application>
 	using &man.cron.8;.
 	Obviously, you should not let <application>CVSup</application>
 	use its GUI when running it from &man.cron.8;.</para>
     </sect2>
 
     <sect2 id="cvsup-collec">
       <title><application>CVSup</application> File Collections</title>
 	    
       <para>The file collections available via
 	<application>CVSup</application> are organized hierarchically.
 	There are a few large collections, and they are divided into
 	smaller sub-collections.  Receiving a large collection is
 	equivalent to receiving each of its sub-collections.  The
 	hierarchical relationships among collections are reflected by
 	the use of indentation in the list below.</para>
       
       <para>The most commonly used collections are
 	<literal>src-all</literal>, and
 	<literal>ports-all</literal>.  The other collections are used
 	only by small groups of people for specialized purposes, and
 	some mirror sites may not carry all of them.</para>
       
       <variablelist>
 	<varlistentry>
 	  <term><literal>cvs-all release=cvs</literal></term>
 	  
 	  <listitem>
 	    <para>The main FreeBSD CVS repository, including the
 	      cryptography code.</para>
 	    
 	    <variablelist>
 	      <varlistentry>
 		<term><literal>distrib release=cvs</literal></term>
 		
 		<listitem>
 		  <para>Files related to the distribution and mirroring
 		    of FreeBSD.</para>
 		</listitem>
 	      </varlistentry>
 	      
 	      <varlistentry>
 		<term><literal>doc-all release=cvs</literal></term>
 		<listitem>
 		  <para>Sources for the FreeBSD Handbook and other
 		    documentation.  This does not include files for
 		    the FreeBSD web site.</para>
 		</listitem>
 	      </varlistentry>
 
 	      <varlistentry>
 		<term><literal>ports-all release=cvs</literal></term>
 
 		<listitem>
 		  <para>The FreeBSD Ports Collection.</para>
 
 		  <important id="cvsup-collec-pbase-warn">
 		    <para>If you do not want to update the whole of
 		      <literal>ports-all</literal> (the whole ports tree),
 		      but use one of the subcollections listed below,
 		      make sure that you <emphasis>always</emphasis> update
 		      the <literal>ports-base</literal> subcollection!
 		      Whenever something changes in the ports build
 		      infrastructure represented by
 		      <literal>ports-base</literal>, it is virtually certain
 		      that those changes will be used by <quote>real</quote>
 		      ports real soon.  Thus, if you only update the
 		      <quote>real</quote> ports and they use some of the new
 		      features, there is a very high chance that their build
 		      will fail with some mysterious error message.  The
 		      <emphasis>very first</emphasis> thing to do in this
 		      case is to make sure that your
 		      <literal>ports-base</literal> subcollection is up to
 		      date.</para>
 		  </important>
 
 		  <important id="cvsup-collec-index-warn">
 		    <para>If you are going to be building your own local
 		      copy of <filename>ports/INDEX</filename>, you
 		      <emphasis>must</emphasis> accept 
 		      <literal>ports-all</literal> (the whole ports tree).
 		      Building <filename>ports/INDEX</filename> with
 		      a partial tree is not supported.  See the
 		      <ulink url="&url.books.faq;/applications.html#MAKE-INDEX">
 		      FAQ</ulink>.</para>
 		  </important>
 
 		  <variablelist>
 		    <varlistentry>
 		      <term><literal>ports-accessibility
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Software to help disabled users.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-arabic
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Arabic language support.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-archivers
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Archiving tools.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-astro
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Astronomical ports.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-audio
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Sound support.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-base
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>The Ports Collection build infrastructure -
 			  various files located in the
 			  <filename>Mk/</filename> and
 			  <filename>Tools/</filename> subdirectories of
 			  <filename>/usr/ports</filename>.</para>
 
 			<note>
 			  <para>Please see the <link
 			    linkend="cvsup-collec-pbase-warn">important
 			    warning above</link>: you should
 			    <emphasis>always</emphasis> update this
 			    subcollection, whenever you update any part of
 			    the FreeBSD Ports Collection!</para>
 			</note>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-benchmarks
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Benchmarks.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-biology
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Biology.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-cad
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Computer aided design tools.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-chinese
 			  release=cvs</literal></term>
 			
 		      <listitem>
 			<para>Chinese language support.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-comms
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Communication software.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-converters
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>character code converters.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-databases
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Databases.</para>
 		      </listitem>
 		    </varlistentry>
 		    
 		    <varlistentry>
 		      <term><literal>ports-deskutils
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Things that used to be on the desktop
 			  before computers were invented.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-devel
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Development utilities.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-dns
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>DNS related software.</para>
 		      </listitem>
 		    </varlistentry>
 		    
 		    <varlistentry>
 		      <term><literal>ports-editors
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Editors.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-emulators
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Emulators for other operating
 			  systems.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-finance
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Monetary, financial and related applications.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-ftp
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>FTP client and server utilities.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-games
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Games.</para>
 		      </listitem>
 		    </varlistentry>
 		    
 		    <varlistentry>
 		      <term><literal>ports-german
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>German language support.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-graphics
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Graphics utilities.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-hebrew
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Hebrew language support.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-hungarian
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Hungarian language support.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-irc
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Internet Relay Chat utilities.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-japanese
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Japanese language support.</para>
 		      </listitem>
 		    </varlistentry>
 		    
 		    <varlistentry>
 		      <term><literal>ports-java
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>&java; utilities.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-korean
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Korean language support.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-lang
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Programming languages.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-mail
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Mail software.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-math
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Numerical computation software.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-mbone
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>MBone applications.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-misc
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Miscellaneous utilities.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-multimedia
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Multimedia software.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-net
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Networking software.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-net-im
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Instant messaging software.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-net-mgmt
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Network management software.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-news
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>USENET news software.</para>
 		      </listitem>
 		    </varlistentry>
 		    
 		    <varlistentry>
 		      <term><literal>ports-palm
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Software support for <trademark class="trade">Palm</trademark>
 			  series.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-polish
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Polish language support.</para>
 		      </listitem>
 		    </varlistentry>
 	
 		    <varlistentry>
 		      <term><literal>ports-portuguese
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Portuguese language support.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-print
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Printing software.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-russian
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Russian language support.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-science
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Science.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-security
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Security utilities.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-shells
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Command line shells.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-sysutils
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>System utilities.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-textproc
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>text processing utilities (does not
 			  include desktop publishing).</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-ukrainian
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Ukrainian language support.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-vietnamese
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Vietnamese language support.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-www
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Software related to the World Wide
 			  Web.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-x11
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Ports to support the X window
 			  system.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-x11-clocks
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>X11 clocks.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-x11-fm
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>X11 file managers.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-x11-fonts
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>X11 fonts and font utilities.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-x11-toolkits
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>X11 toolkits.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-x11-servers
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>X11 servers.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-x11-themes
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>X11 themes.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>ports-x11-wm
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>X11 window managers.</para>
 		      </listitem>
 		    </varlistentry>
 		  </variablelist>
 		</listitem>
 	      </varlistentry>
 
 	      <varlistentry>
 		<term><literal>src-all release=cvs</literal></term>
 		
 		<listitem>
 		  <para>The main FreeBSD sources, including the
 		    cryptography code.</para>
 
 		  <variablelist>
 		    <varlistentry>
 		      <term><literal>src-base
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Miscellaneous files at the top of
 			  <filename>/usr/src</filename>.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>src-bin
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>User utilities that may be needed in
 			  single-user mode
 			  (<filename>/usr/src/bin</filename>).</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>src-contrib
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Utilities and libraries from outside the
 			  FreeBSD project, used relatively unmodified
 			  (<filename>/usr/src/contrib</filename>).</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>src-crypto release=cvs</literal></term>
 
 		      <listitem>
 			<para>Cryptography utilities and libraries from
 			  outside the FreeBSD project, used relatively
 			  unmodified
 			  (<filename>/usr/src/crypto</filename>).</para>
 			  </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>src-eBones release=cvs</literal></term>
 		
 		      <listitem>
 			<para>Kerberos and DES
 			  (<filename>/usr/src/eBones</filename>).  Not
 			  used in current releases of FreeBSD.</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>src-etc
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>System configuration files
 			  (<filename>/usr/src/etc</filename>).</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>src-games
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Games
 			  (<filename>/usr/src/games</filename>).</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>src-gnu
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Utilities covered by the GNU Public
 			  License (<filename>/usr/src/gnu</filename>).</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>src-include
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Header files
 			  (<filename>/usr/src/include</filename>).</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>src-kerberos5
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Kerberos5 security package
 			  (<filename>/usr/src/kerberos5</filename>).</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>src-kerberosIV
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>KerberosIV security package
 			  (<filename>/usr/src/kerberosIV</filename>).</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>src-lib
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Libraries
 			  (<filename>/usr/src/lib</filename>).</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>src-libexec
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>System programs normally executed by other
 			  programs
 			  (<filename>/usr/src/libexec</filename>).</para>
 		      </listitem>
 		    </varlistentry>
 		    
 		    <varlistentry>
 		      <term><literal>src-release
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>Files required to produce a FreeBSD
 			  release
 			  (<filename>/usr/src/release</filename>).</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>src-sbin release=cvs</literal></term>
 
 		      <listitem>
 			<para>System utilities for single-user mode
 			  (<filename>/usr/src/sbin</filename>).</para>
 		      </listitem>
 		    </varlistentry>
 		    
 		    <varlistentry>
 		      <term><literal>src-secure
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Cryptographic libraries and commands
 			  (<filename>/usr/src/secure</filename>).</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>src-share
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Files that can be shared across multiple
 			  systems
 			  (<filename>/usr/src/share</filename>).</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>src-sys
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>The kernel
 			  (<filename>/usr/src/sys</filename>).</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>src-sys-crypto
 			release=cvs</literal></term>
 		
 		      <listitem>
 			<para>Kernel cryptography code
 			  (<filename>/usr/src/sys/crypto</filename>).</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>src-tools
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>Various tools for the maintenance of
 			  FreeBSD
 			  (<filename>/usr/src/tools</filename>).</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>src-usrbin
 			  release=cvs</literal></term>
 
 		      <listitem>
 			<para>User utilities
 			  (<filename>/usr/src/usr.bin</filename>).</para>
 		      </listitem>
 		    </varlistentry>
 
 		    <varlistentry>
 		      <term><literal>src-usrsbin
 			  release=cvs</literal></term>
 		      
 		      <listitem>
 			<para>System utilities
 			  (<filename>/usr/src/usr.sbin</filename>).</para>
 		      </listitem>
 		    </varlistentry>
 		  </variablelist>
 		</listitem>
 	      </varlistentry>
 	      
 	      <varlistentry>
 		<term><literal>www release=cvs</literal></term>
 		
 		<listitem>
 		  <para>The sources for the FreeBSD WWW site.</para>
 		</listitem>
 	      </varlistentry>
 	    </variablelist>
 	  </listitem>
 	</varlistentry>
 	
 	<varlistentry>
 	  <term><literal>distrib release=self</literal></term>
 
 	  <listitem>
 	    <para>The <application>CVSup</application> server's own 
 	      configuration files.  Used by <application>CVSup</application>
 	      mirror sites.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><literal>gnats release=current</literal></term>
 
 	  <listitem>
 	    <para>The GNATS bug-tracking database.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><literal>mail-archive release=current</literal></term>
 	  
 	  <listitem>
 	    <para>FreeBSD mailing list archive.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><literal>www release=current</literal></term>
 
 	  <listitem>
 	    <para>The pre-processed FreeBSD WWW site files (not the
 	      source files).  Used by WWW mirror sites.</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
     </sect2>
 
     <sect2>
       <title>For More Information</title>
 
       <para>For the <application>CVSup</application> FAQ and other 
 	information about <application>CVSup</application>, see
 	<ulink url="http://www.polstra.com/projects/freeware/CVSup/">The
 	  CVSup Home Page</ulink>.</para>
 
       <para>Most FreeBSD-related discussion of
 	<application>CVSup</application> takes place on the
 	&a.hackers;.  New versions of the software are announced there,
 	as well as on the &a.announce;.</para>
       
       <para>Questions and bug reports should be addressed to the author
 	of the program at <email>cvsup-bugs@polstra.com</email>.</para>
     </sect2>
 
     <sect2 id="cvsup-mirrors">
     <title>CVSup Sites</title>
 
     <para><link linkend="cvsup">CVSup</link> servers for FreeBSD are running
       at the following sites:</para>
 
     &chap.mirrors.cvsup.inc;
     </sect2>
   </sect1>
   
   <sect1 id="portsnap">
     <title>Using Portsnap</title>
 
     <sect2 id="portsnap-intro">
       <title>Introduction</title>
 
       <para><application>Portsnap</application> is a system for securely
 	distributing the &os; ports tree.  Approximately once an hour,
 	a <quote>snapshot</quote> of the ports tree is generated,
 	repackaged, and cryptographically signed.  The resulting files
 	are then distributed via HTTP.</para>
 
       <para>Like <application>CVSup</application>,
 	<application>Portsnap</application> uses a
 	<emphasis>pull</emphasis> model of updating: The packaged and
 	signed ports trees are placed on a web server which waits
 	passively for clients to request files.  Users must either run
 	&man.portsnap.8; manually to download updates
 	or set up a &man.cron.8; job to download updates
 	automatically on a regular basis.</para>
 
       <para>For technical reasons, <application>Portsnap</application>
 	does not update the <quote>live</quote> ports tree in
 	<filename>/usr/ports/</filename> directly; instead, it works
 	via a compressed copy of the ports tree stored in
 	<filename>/var/db/portsnap/</filename> by default.  This
 	compressed copy is then used to update the live ports tree.</para>
 
       <note>
 	<para>If <application>Portsnap</application> is installed from
 	the &os; Ports Collection, then the default location for its
 	compressed snapshot will be <filename>/usr/local/portsnap/</filename>
 	instead of <filename>/var/db/portsnap/</filename>.</para>
       </note>
     </sect2>
 
     <sect2 id="portsnap-install">
       <title>Installation</title>
 
       <para>On &os; 6.0 and more recent versions,
 	<application>Portsnap</application> is contained in the &os;
 	base system.  On older versions of &os;, it can be installed
 	using the <filename role="package">sysutils/portsnap</filename>
 	port.</para>
     </sect2>
 
     <sect2 id="portsnap-config">
       <title>Portsnap Configuration</title>
 
       <para><application>Portsnap</application>'s operation is controlled
 	by the <filename>/etc/portsnap.conf</filename> configuration
 	file.  For most users, the default configuration file will
 	suffice; for more details, consult the &man.portsnap.conf.5;
 	manual page.</para>
 
       <note>
 	<para>If <application>Portsnap</application> is installed from
 	  the &os; Ports Collection, it will use the configuration file
 	  <filename>/usr/local/etc/portsnap.conf</filename> instead of
 	  <filename>/etc/portsnap.conf</filename>.  This configuration
 	  file is not created when the port is installed, but a sample
 	  configuration file is distributed; to copy it into place, run
 	  the following command:</para>
 
-	<screen>&prompt.root; <userinput>cd /usr/local/etc && cp portsnap.conf.sample portsnap.conf</userinput></screen>
+	<screen>&prompt.root; <userinput>cd /usr/local/etc &amp;&amp; cp portsnap.conf.sample portsnap.conf</userinput></screen>
       </note>
     </sect2>
 
     <sect2>
       <title>Running <application>Portsnap</application> for the First
 	Time</title>
 
       <para>The first time &man.portsnap.8; is run,
 	it will need to download a compressed snapshot of the entire
 	ports tree into <filename>/var/db/portsnap/</filename> (or
 	<filename>/usr/local/portsnap/</filename> if
 	<application>Portsnap</application> was installed from the
-	Ports Collection).  This is approximately a 36&nbsp;MB
+	Ports Collection).  This is approximately a 38&nbsp;MB
 	download.</para>
 
       <screen>&prompt.root; <userinput>portsnap fetch</userinput></screen>
 
       <para>Once the compressed snapshot has been downloaded, a
 	<quote>live</quote> copy of the ports tree can be extracted into
 	<filename>/usr/ports/</filename>.  This is necessary even if a
 	ports tree has already been created in that directory (e.g., by
 	using <application>CVSup</application>), since it establishes a
 	baseline from which <command>portsnap</command> can
 	determine which parts of the ports tree need to be updated
 	later.</para>
 
       <note>
 	<para>In the default installation
 	  <filename role="directory">/usr/ports</filename> is not
 	  created.  It should be created before
 	  <application>portsnap</application> is used.</para>
 
 	<screen>&prompt.root; <userinput>mkdir /usr/ports</userinput></screen>
       </note>
 
       <screen>&prompt.root; <userinput>portsnap extract</userinput></screen>
     </sect2>
 
     <sect2>
       <title>Updating the Ports Tree</title>
 
       <para>After an initial compressed snapshot of the ports tree has
 	been downloaded and extracted into <filename>/usr/ports/</filename>,
 	updating the ports tree consists of two steps:
 	<emphasis>fetch</emphasis>ing updates to the compressed
 	snapshot, and using them to <emphasis>update</emphasis> the
 	live ports tree.  These two steps can be specified to
 	<command>portsnap</command> as a single command:</para>
 
       <screen>&prompt.root; <userinput>portsnap fetch update</userinput></screen>
 
       <note>
 	<para>Some older versions of <command>portsnap</command>
 	  do not support this syntax; if it fails, try instead the
 	  following:</para>
 
         <screen>&prompt.root; <userinput>portsnap fetch</userinput>
 &prompt.root; <userinput>portsnap update</userinput></screen>
       </note>
     </sect2>
 
     <sect2>
       <title>Running Portsnap from cron</title>
 
       <para>In order to avoid problems with <quote>flash crowds</quote>
 	accessing the <application>Portsnap</application> servers,
 	<command>portsnap fetch</command> will not run from
 	a &man.cron.8; job.  Instead, a special
 	<command>portsnap cron</command> command exists, which
 	waits for a random duration up to 3600 seconds before fetching
 	updates.</para>
 
       <para>In addition, it is strongly recommended that
 	<command>portsnap update</command> not be run from a
 	<command>cron</command> job, since it is liable to cause
 	major problems if it happens to run at the same time as a port
 	is being built or installed.  However, it is safe to update
 	the ports INDEX files, and this can be done by passing the
 	<option>-I</option> flag to
 	<command>portsnap</command>.  (Obviously, if
 	<command>portsnap -I update</command> is run from
 	<command>cron</command>, then it will be necessary to run
 	<command>portsnap update</command> without the <option>-I</option>
 	flag at a later time in order to update the rest of the tree.)</para>
 
       <para>Adding the following line to <filename>/etc/crontab</filename>
 	will cause <command>portsnap</command> to update its
 	compressed snapshot and the INDEX files in
 	<filename>/usr/ports/</filename>, and will send an email if any
 	installed ports are out of date:</para>
 
-      <programlisting>0 3 * * * root portsnap -I cron update && pkg_version -vIL=</programlisting>
+      <programlisting>0 3 * * * root portsnap -I cron update &amp;&amp; pkg_version -vIL=</programlisting>
 
       <note>
 	<para>If the system clock is not set to the local time zone,
 	  please replace <literal>3</literal> with a random
 	  value between 0 and 23, in order to spread the load on the
 	  <application>Portsnap</application> servers more evenly.</para>
       </note>
       <note>
 	<para>Some older versions of <command>portsnap</command>
 	  do not support listing multiple commands (e.g., <literal>cron update</literal>)
 	  in the same invocation of <command>portsnap</command>.  If
 	  the line above fails, try replacing
 	  <command>portsnap -I cron update</command> with
-	  <command>portsnap cron && portsnap -I update</command>.</para>
+	  <command>portsnap cron &amp;&amp; portsnap -I update</command>.</para>
       </note>
     </sect2>
   </sect1>
 
   <sect1 id="cvs-tags">
     <title>CVS Tags</title>
 
     <para>When obtaining or updating sources using
       <application>cvs</application> or
       <application>CVSup</application>, a revision tag must be specified.
       A revision tag refers to either a particular line of &os;
       development, or a specific point in time.  The first type are called
       <quote>branch tags</quote>, and the second type are called
       <quote>release tags</quote>.</para>
 
     <sect2>
       <title>Branch Tags</title>
 
       <para>All of these, with the exception of <literal>HEAD</literal> (which
 	is always a valid tag), only apply to the <filename>src/</filename>
 	tree.  The <filename>ports/</filename>, <filename>doc/</filename>, and
 	<filename>www/</filename> trees are not branched.</para>
 
     <variablelist>
       <varlistentry>
 	<term>HEAD</term>
 
 	<listitem>
 	  <para>Symbolic name for the main line, or FreeBSD-CURRENT.
 	    Also the default when no revision is specified.</para>
 
 	  <para>In <application>CVSup</application>, this tag is represented
 	    by a <literal>.</literal> (not punctuation, but a literal
 	    <literal>.</literal> character).</para>
 
 	  <note>
 	    <para>In CVS, this is the default when no revision tag is
 	      specified.  It is usually <emphasis>not</emphasis>
 	      a good idea to checkout or update to CURRENT sources
 	      on a STABLE machine, unless that is your intent.</para>
 	  </note>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_6</term>
 
 	<listitem>
 	  <para>The line of development for FreeBSD-6.X, also known
 	    as FreeBSD 6-STABLE</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_6_0</term>
 
 	<listitem>
 	  <para>The release branch for FreeBSD-6.0, used only for
 	    security advisories and other critical fixes.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_5</term>
 
 	<listitem>
 	  <para>The line of development for FreeBSD-5.X, also known
 	    as FreeBSD 5-STABLE.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_5_4</term>
 
 	<listitem>
 	  <para>The release branch for FreeBSD-5.4, used only 
 	    for security advisories and other critical fixes.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_5_3</term>
 
 	<listitem>
 	  <para>The release branch for FreeBSD-5.3, used only 
 	    for security advisories and other critical fixes.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_5_2</term>
 
 	<listitem>
 	  <para>The release branch for FreeBSD-5.2 and FreeBSD-5.2.1, used only 
 	    for security advisories and other critical fixes.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_5_1</term>
 
 	<listitem>
 	  <para>The release branch for FreeBSD-5.1, used only 
 	    for security advisories and other critical fixes.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_5_0</term>
 
 	<listitem>
 	  <para>The release branch for FreeBSD-5.0, used only 
 	    for security advisories and other critical fixes.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_4</term>
 
 	<listitem>
 	  <para>The line of development for FreeBSD-4.X, also known
 	    as FreeBSD 4-STABLE.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_4_11</term>
 
 	<listitem>
 	  <para>The release branch for FreeBSD-4.11, used only
 	    for security advisories and other critical fixes.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_4_10</term>
 
 	<listitem>
 	  <para>The release branch for FreeBSD-4.10, used only 
 	    for security advisories and other critical fixes.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_4_9</term>
 
 	<listitem>
 	  <para>The release branch for FreeBSD-4.9, used only 
 	    for security advisories and other critical fixes.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_4_8</term>
 
 	<listitem>
 	  <para>The release branch for FreeBSD-4.8, used only 
 	    for security advisories and other critical fixes.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_4_7</term>
 
 	<listitem>
 	  <para>The release branch for FreeBSD-4.7, used only 
 	    for security advisories and other critical fixes.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_4_6</term>
 
 	<listitem>
 	  <para>The release branch for FreeBSD-4.6 and FreeBSD-4.6.2,
             used only for security advisories and other
             critical fixes.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_4_5</term>
 
 	<listitem>
 	  <para>The release branch for FreeBSD-4.5, used only
 	    for security advisories and other critical fixes.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_4_4</term>
 
 	<listitem>
 	  <para>The release branch for FreeBSD-4.4, used only
 	    for security advisories and other critical fixes.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_4_3</term>
 
 	<listitem>
 	  <para>The release branch for FreeBSD-4.3, used only
 	    for security advisories and other critical fixes.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_3</term>
 
 	<listitem>
 	  <para>The line of development for FreeBSD-3.X, also known
 	    as 3.X-STABLE.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_2_2</term>
 
 	<listitem>
 	  <para>The line of development for FreeBSD-2.2.X, also known
 	    as 2.2-STABLE.  This branch is mostly obsolete.</para>
 	</listitem>
       </varlistentry>
     </variablelist>
     </sect2>
 
     <sect2>
       <title>Release Tags</title>
 
       <para>These tags refer to a specific point in time when a particular
 	version	of &os; was released.  The release engineering process is
 	documented in more detail by the
 	<ulink url="&url.base;/releng/">Release Engineering
 	  Information</ulink> and
         <ulink url="&url.articles.releng;/release-proc.html">Release
 	  Process</ulink> documents.
 	The <filename class="directory">src</filename> tree uses tag names that
 	start with <literal>RELENG_</literal> tags.
 	The <filename class="directory">ports</filename> and
 	<filename class="directory">doc</filename> trees use tags whose names
 	begin with <literal>RELEASE</literal> tags.
 	Finally, the <filename class="directory">www</filename> tree is not
 	tagged with any special name for releases.</para>
 
     <variablelist>
+      <varlistentry>
+	<term>RELENG_6_0_0_RELEASE</term>
+
+	<listitem>
+	  <para>FreeBSD 6.0</para>
+	</listitem>
+      </varlistentry>
+
       <varlistentry>
 	<term>RELENG_5_4_0_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD 5.4</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_4_11_0_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD 4.11</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_5_3_0_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD 5.3</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_4_10_0_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD 4.10</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_5_2_1_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD 5.2.1</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_5_2_0_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD 5.2</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_4_9_0_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD 4.9</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_5_1_0_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD 5.1</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_4_8_0_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD 4.8</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_5_0_0_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD 5.0</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_4_7_0_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD 4.7</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_4_6_2_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD 4.6.2</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_4_6_1_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD 4.6.1</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_4_6_0_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD 4.6</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_4_5_0_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD 4.5</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_4_4_0_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD 4.4</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_4_3_0_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD 4.3</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_4_2_0_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD 4.2</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_4_1_1_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD 4.1.1</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_4_1_0_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD 4.1</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_4_0_0_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD 4.0</para>
 	</listitem>
       </varlistentry>
 	  
       <varlistentry>
 	<term>RELENG_3_5_0_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD-3.5</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_3_4_0_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD-3.4</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_3_3_0_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD-3.3</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_3_2_0_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD-3.2</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_3_1_0_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD-3.1</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_3_0_0_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD-3.0</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_2_2_8_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD-2.2.8</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_2_2_7_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD-2.2.7</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_2_2_6_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD-2.2.6</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_2_2_5_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD-2.2.5</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_2_2_2_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD-2.2.2</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_2_2_1_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD-2.2.1</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>RELENG_2_2_0_RELEASE</term>
 
 	<listitem>
 	  <para>FreeBSD-2.2.0</para>
 	</listitem>
       </varlistentry>
     </variablelist>
     </sect2>
   </sect1>
 
   <sect1 id="mirrors-afs">
     <title>AFS Sites</title>
 
     <para>AFS servers for FreeBSD are running at the following sites:</para>
 
     <variablelist>
       <varlistentry>
 	<term>Sweden</term>
 
 	<listitem>
 	  <para>The path to the files are:
   	    <filename>/afs/stacken.kth.se/ftp/pub/FreeBSD/</filename></para>
 
 	  <programlisting>stacken.kth.se         # Stacken Computer Club, KTH, Sweden
 130.237.234.43         #hot.stacken.kth.se
 130.237.237.230        #fishburger.stacken.kth.se
 130.237.234.3          #milko.stacken.kth.se</programlisting>
 
 	  <para>Maintainer <email>ftp@stacken.kth.se</email></para>
 	</listitem>
       </varlistentry>
     </variablelist>
   </sect1>
 
   <sect1 id="mirrors-rsync">
     <title>rsync Sites</title>
 
     <para>The following sites make FreeBSD available through the rsync
       protocol.  The <application>rsync</application> utility works in
       much the same way as the &man.rcp.1; command,
       but has more options and uses the rsync remote-update protocol
       which transfers only the differences between two sets of files,
       thus greatly speeding up the synchronization over the network.  
       This is most useful if you are a mirror site for the
       FreeBSD FTP server, or the CVS repository.  The
       <application>rsync</application> suite is available for many
       operating systems, on FreeBSD, see the
       <filename role="package">net/rsync</filename>
       port or use the package.</para>
 
     <variablelist>
       <varlistentry>
 	<term>Czech Republic</term>
 
 	<listitem>
 	  <para>rsync://ftp.cz.FreeBSD.org/</para>
 
 	  <para>Available collections:</para>
 	  <itemizedlist>
 	    <listitem><para>ftp: A partial mirror of the FreeBSD FTP
 	      server.</para></listitem>
 	    <listitem><para>FreeBSD: A full mirror of the FreeBSD FTP
 	      server.</para></listitem>
 	  </itemizedlist>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>Germany</term>
 
 	<listitem>
 	  <para>rsync://grappa.unix-ag.uni-kl.de/</para>
 
 	  <para>Available collections:</para>
 	  <itemizedlist>
 	    <listitem><para>freebsd-cvs: The full FreeBSD CVS
 	      repository.</para></listitem>
 	  </itemizedlist>
 	  <para>This machine also mirrors the CVS repositories of the
 	    NetBSD and the OpenBSD projects, among others.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>Netherlands</term>
 
 	<listitem>
 	  <para>rsync://ftp.nl.FreeBSD.org/</para>
 
 	  <para>Available collections:</para>
 	  <itemizedlist>
 	    <listitem><para>vol/4/freebsd-core: A full mirror of the
 	      FreeBSD FTP server.</para></listitem>
 	  </itemizedlist>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>United Kingdom</term>
 
 	<listitem>
 	  <para>rsync://rsync.mirror.ac.uk/</para>
 
 	  <para>Available collections:</para>
 	  <itemizedlist>
 	    <listitem><para>ftp.FreeBSD.org: A full mirror of the
 	      FreeBSD FTP server.</para></listitem>
 	  </itemizedlist>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>United States of America</term>
 
 	<listitem>
 	  <para>rsync://ftp-master.FreeBSD.org/</para>
 
 	  <para>This server may only be used by FreeBSD primary mirror
 	    sites.</para>
 	  <para>Available collections:</para>
 	  <itemizedlist>
 	    <listitem><para>FreeBSD: The master archive of the FreeBSD
 	      FTP server.</para></listitem>
 	    <listitem><para>acl: The FreeBSD master ACL
 	      list.</para></listitem>  
 	  </itemizedlist>
 
 	  <para>rsync://ftp13.FreeBSD.org/</para>
 
 	  <para>Available collections:</para>
 	  <itemizedlist>
 	    <listitem><para>FreeBSD: A full mirror of the FreeBSD FTP
 	      server.</para></listitem>
 	  </itemizedlist>
 	</listitem>
       </varlistentry>
     </variablelist>
   </sect1>  
 </appendix>
 
 <!--
      Local Variables:
      mode: sgml
      sgml-declaration: "../appendix.decl"
      sgml-indent-data: t
      sgml-omittag: nil
      sgml-always-quote-attributes: t
      sgml-parent-document: ("../book.sgml" "part" "appendix")
      End:
 -->
 
diff --git a/zh_TW.Big5/books/handbook/multimedia/chapter.sgml b/zh_TW.Big5/books/handbook/multimedia/chapter.sgml
index c7e9e90a67..95977e1b60 100644
--- a/zh_TW.Big5/books/handbook/multimedia/chapter.sgml
+++ b/zh_TW.Big5/books/handbook/multimedia/chapter.sgml
@@ -1,1865 +1,1855 @@
 <!--
      The FreeBSD Documentation Project
 
      $FreeBSD$
 -->
 
 <chapter id="multimedia">
  <chapterinfo>
   <authorgroup>
    <author>
     <firstname>Ross</firstname>
     <surname>Lippert</surname>
     <contrib>Edited by </contrib>
    </author>
   </authorgroup>
  </chapterinfo>
 
- <title>Multimedia</title>
+ <title>¦h´CÅé¼v­µ®T¼Ö(Multimedia)</title>
   <sect1 id="multimedia-synopsis">
-  <title>Synopsis</title>
-
-    <para>FreeBSD supports a wide variety of sound cards, allowing you
-      to enjoy high fidelity output from your computer.  This includes
-      the ability to record and playback audio in the MPEG Audio Layer
-      3 (MP3), WAV, and Ogg Vorbis formats as well as many other
-      formats.  The FreeBSD Ports Collection also contains
-      applications allowing you to edit your recorded audio, add sound
-      effects, and control attached MIDI devices.</para>
-
-    <para>With some willingness to experiment, FreeBSD can support
-      playback of video files and DVD's.  The number of applications
-      to encode, convert, and playback various video media is more
-      limited than the number of sound applications.  For example as
-      of this writing, there is no good re-encoding application in the
-      FreeBSD Ports Collection, which could be use to convert
-      between formats, as there is with <filename
-      role="package">audio/sox</filename>.  However, the software
-      landscape in this area is changing rapidly.</para>
-
-    <para>This chapter will describe the necessary steps to configure
-      your sound card.  The configuration and installation of X11
-      (<xref linkend="x11">) has already taken care of the
-      hardware issues for your video card, though there may be some
-      tweaks to apply for better playback.</para>
-
-    <para>After reading this chapter, you will know:</para>
+  <title>·§­z</title>
+
+    <para>FreeBSD ¼sªx¦a¤ä´©¦UºØ­µ®Ä¥d¡A Åý±z¥i¥H¨É¨ü¨Ó¦Û¹q¸£¤Wªº°ª¶Ç¯u­µ½è(Hi-Fi)¡A
+	¦¹¥~ÁÙ¥]¬A¤F¿ý»s©M¼½©ñ MPEG Audio Layer 3 (MP3)¡B WAV¡B ¥H¤Î Ogg Vorbis 
+	µ¥³\¦hºØ®æ¦¡Án­µªº¯à¤O¡C¦P®É FreeBSD Ports Collection ¤]¥]¬A¤F³\¦hªºÀ³¥Îµ{¦¡¡A
+	Åý±z¥i¥H¿ý­µ¡B½s­×­µ®Ä¥H¤Î±±¨î MIDI °t³Æ¡C</para>
+
+    <para>­n¬O³ßÅw°Ê¤â¹Á¸Õ¤£¦PªºÅéÅç¡A FreeBSD ¤]¯à¼½©ñ¤@¯ëªºµø°TÀÉ©M DVD¡C
+	½s½X¡BÂà´«©M¼½©ñµø°Tªºµ{¦¡¤ñ°_³B²zÁn­µªºµ{¦¡²¤¤Ö¤@¨Ç¡C¨Ò¦p¡A ¦b¼¶¼g³o³¹®É¡A 
+	FreeBSD Ports Collection ¤¤ÁÙ¨S¦³Ãþ¦ü <filename
+      role="package">audio/sox</filename> ¨º¼Ë¦n¥Îªº½s½X¤u¨ã¡A¯à°÷¥Î¨ÓÂà´«¤£¦Pªº®æ¦¡¡C
+	¤£¹L¡A³o­Ó»â°ìªº³nÅé¬ãµo¶i®i¬O¬Û·í¨³³tªº¡C</para>
+
+    <para>¥»³¹±N¤¶²Ð³]©w­µ®Ä¥dªº¥²­n¨BÆJ¡C¥ý«e¤¶²Ð¨ìªº X11
+      (<xref linkend="x11">) ¦w¸Ë©M³]©w¸Ì¡A¤w¸gÁ¿¨ì¤FÅã¥Ü¥dªº³¡¥÷¡A
+	¦ý­n·Q¦³§ó¦nªº¼½©ñ®ÄªG¡A ¤´»Ý­n¤@¨Ç²Ó³¡½Õ¾ã¡C</para>
+
+    <para>Ū§¹³o³¹¡A±z±N¤F¸Ñ¡G</para>
 
     <itemizedlist>
       <listitem>
-        <para>How to configure your system so that your sound card is
-          recognized.</para>
+        <para>¦p¦ó³]©w¨t²Î¡A¥H¥¿½TÃѧO­µ®Ä¥d¡C</para>
       </listitem>
 
       <listitem>
         <para>Methods to test that your card is working using
           sample applications.</para>
       </listitem>
 
       <listitem>
-        <para>How to troubleshoot your sound setup.</para>
+        <para>¦p¦ó¸Ñ¨M­µ®Ä¥dªº³]©w°ÝÃD¡C</para>
       </listitem>
 
       <listitem>
         <para>How to playback and encode MP3s and other audio.</para>
       </listitem>
 
       <listitem>
         <para>How video is supported by the X server.</para>
       </listitem>
 
       <listitem>
         <para>Some video player/encoder ports which give good results.</para>
       </listitem>
 
       <listitem>
-        <para>How to playback DVD's, <filename>.mpg</filename> and
-          <filename>.avi</filename> files.</para>
+        <para>¦p¦ó¼½©ñ DVD ªº <filename>.mpg</filename> ¤Î
+          <filename>.avi</filename> ÀÉ</para>
       </listitem>
 
       <listitem>
-        <para>How to rip CD and DVD information into files.</para>
+        <para>¦p¦ó±q CD ©M DVD ¤¤Â^¨ú(rip)ÀɮסC</para>
       </listitem>
 
       <listitem>
-	<para>How to configure a TV card.</para>
+	<para>¦p¦ó³]©w¹qµø¥d</para>
       </listitem>
 
       <listitem>
-	<para>How to configure an image scanner.</para>
+	<para>¦p¦ó³]©w±½´y¾¹</para>
       </listitem>
     </itemizedlist>
 
-    <para>Before reading this chapter, you should:</para>
+    <para>¦b¾\Ū³o³¹¤§«e¡A±zÀ³·í¤F¸Ñ¡G</para>
 
     <itemizedlist>
-      <listitem><para>Know how to configure and install a new kernel (<xref
-        linkend="kernelconfig">).</para></listitem>
+      <listitem><para>ª¾¹D¦p¦ó³]©w¡B¦w¸Ë·sªº kernel (<xref
+        linkend="kernelconfig">)¡C</para></listitem>
     </itemizedlist>
 
     <warning>
       <para>Trying to mount audio CDs
         with the &man.mount.8; command will
         result in an error, at least, and a <emphasis>kernel
         panic</emphasis>, at worst.  These media have specialized
         encodings which differ from the usual ISO-filesystem.</para>
     </warning>
 
   </sect1>
 
   <sect1 id="sound-setup">
     <sect1info>
       <authorgroup>
         <author>
 	 <firstname>Moses</firstname>
 	 <surname>Moore</surname>
 	 <contrib>Contributed by </contrib>
 	 <!-- 20 November 2000 -->
         </author>
       </authorgroup>
       <authorgroup>
         <author>
 	 <firstname>Marc</firstname>
 	 <surname>Fonvieille</surname>
 	 <contrib>Enhanced for &os;&nbsp;5.X by </contrib>
 	 <!-- 13 September 2004 -->
         </author>
       </authorgroup>
     </sect1info>
 
-    <title>Setting Up the Sound Card</title>
+    <title>³]©w­µ®Ä¥d</title>
     
   <sect2 id="sound-device">
     <title>Configuring the System</title>
 
     <indexterm><primary>PCI</primary></indexterm>
     <indexterm><primary>ISA</primary></indexterm>
     <indexterm><primary>sound cards</primary></indexterm>
     <para>Before you begin, you should know the model of the card you
       have, the chip it uses, and whether it is a PCI or ISA card.
       FreeBSD supports a wide variety of both PCI and ISA cards.
       Check the supported audio devices list of the <ulink
       url="&rel.current.hardware;">Hardware Notes</ulink> to see if
       your card is supported.  This document will also mention which
       driver supports your card.</para>
 
     <indexterm>
       <primary>kernel</primary>
       <secondary>configuration</secondary>
     </indexterm>
 
     <para>To use your sound device, you will need to load the proper
       device driver.  This may be accomplished in one of two ways.
       The easiest way is to simply load a kernel module for your sound
       card with &man.kldload.8; which can either be done from the
       command line:</para>
 
     <screen>&prompt.root; <userinput>kldload snd_emu10k1</userinput></screen>
 
     <para>or by adding the appropriate line to the file
       <filename>/boot/loader.conf</filename> like this:</para>
 
     <programlisting>snd_emu10k1_load="YES"</programlisting>
 
     <para>These examples are for a Creative &soundblaster; Live! sound
       card.  Other available loadable sound modules are listed in
       <filename>/boot/defaults/loader.conf</filename>.
       If you are not sure which driver to use, you may try to load
       the <filename>snd_driver</filename> module:</para>
 
     <screen>&prompt.root; <userinput>kldload snd_driver</userinput></screen>
 
     <para>This is a metadriver loading the most common device drivers
       at once.  This speeds up the search for the correct driver.  It
       is also possible to load all sound drivers via the
       <filename>/boot/loader.conf</filename> facility.</para>
 
     <para>If you wish to find out the driver selected for your
       soundcard after loading the <filename>snd_driver</filename>
       metadriver, you may check the <filename>/dev/sndstat</filename>
       file with the <command>cat /dev/sndstat</command>
       command.</para>
 
     <note>
       <para>Under &os;&nbsp;4.X, to load all sound drivers, you have
 	to load the <filename>snd</filename> module instead of
 	<filename>snd_driver</filename>.</para>
     </note>
 
     <para>A second method is to statically
       compile in support for your sound card in your kernel.  The
       section below provides the information you need to add support
       for your hardware in this manner.  For more information about
       recompiling your kernel, please see <xref
       linkend="kernelconfig">.</para>
 
     <sect3>
       <title>Configuring a Custom Kernel with Sound Support</title>
 
       <para>The first thing to do is adding the generic audio driver
 	&man.sound.4; to the kernel, for that you will need to
 	add the following line to the kernel configuration file:</para>
 
       <programlisting>device sound</programlisting>
 
       <para>Under &os;&nbsp;4.X, you would use the following
 	line:</para>
 
       <programlisting>device pcm</programlisting>
 
       <para>Then we have to add the support for our sound card.
 	Therefore, we need to know which driver supports the card.
 	Check the supported audio devices list of the <ulink
 	url="&rel.current.hardware;">Hardware Notes</ulink>, to
 	determine the correct driver for your sound card.  For
 	example, a Creative &soundblaster; Live! sound card is
 	supported by the &man.snd.emu10k1.4; driver.  To add the support
 	for this card, use the following:</para>
 
       <programlisting>device "snd_emu10k1"</programlisting>
 
       <para>Be sure to read the manual page of the driver for the
 	syntax to use.  Information regarding the syntax of sound
 	drivers in the kernel configuration can also be found in the
 	<filename>/usr/src/sys/conf/NOTES</filename> file
 	(<filename>/usr/src/sys/i386/conf/LINT</filename> for
 	&os;&nbsp;4.X).</para>
 
       <para>Non-PnP ISA cards may require you to provide the kernel
 	with information on the sound card settings (IRQ, I/O port,
 	etc).  This is done via the
 	<filename>/boot/device.hints</filename> file.  At system boot,
 	the &man.loader.8; will read this file and pass the settings
 	to the kernel.  For example, an old
 	Creative &soundblaster; 16 ISA non-PnP card will use the
 	&man.snd.sbc.4; driver in conjunction with snd_sb16(4).  For this card the following lines have to be added to
 	the kernel configuration file:</para>
 
       <programlisting>device snd_sbc
 device snd_sb16</programlisting>
 
       <para>as well as the following in
 	<filename>/boot/device.hints</filename>:</para>
 
       <programlisting>hint.sbc.0.at="isa"
 hint.sbc.0.port="0x220"
 hint.sbc.0.irq="5"
 hint.sbc.0.drq="1"
 hint.sbc.0.flags="0x15"</programlisting>
 
       <para>In this case, the card uses the <literal>0x220</literal>
 	I/O port and the IRQ <literal>5</literal>.</para>
 
       <para>The syntax used in the
 	<filename>/boot/device.hints</filename> file is covered in the
 	sound driver manual page.  On &os;&nbsp;4.X, these settings
 	are directly written in the kernel configuration file.  In the
 	case of our ISA card, we would only use this line:</para>
 
       <programlisting>device sbc0 at isa? port 0x220 irq 5 drq 1 flags 0x15</programlisting>
 
       <para>The settings shown above are the defaults.  In some
 	cases, you may need to change the IRQ or the other settings to
 	match your card.  See the &man.snd.sbc.4; manual page for more
 	information.</para>
 
       <note>
 	<para>Under &os;&nbsp;4.X, some systems with built-in
 	  motherboard sound devices may require the following option in
 	  the kernel configuration:</para>
 
 	<programlisting>options PNPBIOS</programlisting>
       </note>
     </sect3>
   </sect2>
 
   <sect2 id="sound-testing">
     <title>Testing the Sound Card</title>
 
     <para>After rebooting with the modified kernel, or after loading
       the required module, the sound card should appear in your system
       message buffer (&man.dmesg.8;) as something like:</para>
 
     <screen>pcm0: &lt;Intel ICH3 (82801CA)&gt; port 0xdc80-0xdcbf,0xd800-0xd8ff irq 5 at device 31.5 on pci0
 pcm0: [GIANT-LOCKED]
 pcm0: &lt;Cirrus Logic CS4205 AC97 Codec&gt;</screen>
 
     <para>The status of the sound card may be checked via the
       <filename>/dev/sndstat</filename> file:</para>
 
     <screen>&prompt.root; <userinput>cat /dev/sndstat</userinput>
 FreeBSD Audio Driver (newpcm)
 Installed devices:
 pcm0: &lt;Intel ICH3 (82801CA)&gt; at io 0xd800, 0xdc80 irq 5 bufsz 16384
 kld snd_ich (1p/2r/0v channels duplex default)</screen>
 
     <para>The output from your system may vary.  If no
       <devicename>pcm</devicename> devices show up, go back and review
       what was done earlier.  Go through your kernel
       configuration file again and make sure the correct
       device is chosen.  Common problems are listed in <xref
       linkend="troubleshooting">.</para>
 
     <para>If all goes well, you should now have a functioning sound
       card.  If your CD-ROM or DVD-ROM drive is properly coupled to
       your sound card, you can put a CD in the drive and play it
       with &man.cdcontrol.1;:</para>
 
       <screen>&prompt.user; <userinput>cdcontrol -f /dev/acd0 play 1</userinput></screen>
 
     <para>Various applications, such as <filename
       role="package">audio/workman</filename> can provide a friendlier
       interface.  You may want to install an application such as
       <filename role="package">audio/mpg123</filename> to listen to
       MP3 audio files.  A quick way to test the card is sending data
       to the <filename>/dev/dsp</filename>, like this:</para>
 
     <screen>&prompt.user; <userinput>cat <replaceable>filename</replaceable> &gt; /dev/dsp</userinput></screen>
 
     <para>where <replaceable>filename</replaceable> can be any file.
       This command line should produce some noise, confirming the
       sound card is actually working.</para>
 
     <note>
       <para>&os;&nbsp;4.X users need to create the sound card device
 	nodes before being able to use it.  If the card showed up in
 	message buffer as <devicename>pcm0</devicename>, you will have
 	to run the following as <username>root</username>:</para>
 
       <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>sh MAKEDEV snd0</userinput></screen>
 
       <para>If the card detection returned <devicename>pcm1</devicename>,
 	follow the same steps as shown above, replacing
 	<devicename>snd0</devicename> with
 	<devicename>snd1</devicename>.</para>
 
       <para><command>MAKEDEV</command> will create a group of device
 	nodes that will be used by the different sound related
 	applications.</para>
     </note>
 
     <para>Sound card mixer levels can be changed via the &man.mixer.8;
       command.  More details can be found in the &man.mixer.8; manual
       page.</para>
 
     <sect3 id="troubleshooting">
       <title>Common Problems</title>
 
       <indexterm><primary>device nodes</primary></indexterm>
       <indexterm><primary>I/O port</primary></indexterm>
       <indexterm><primary>IRQ</primary></indexterm>
       <indexterm><primary>DSP</primary></indexterm>
 
       <informaltable frame="none" pgwide="1">
          <tgroup cols="2">
   	  <thead>
 	    <row>
 	     <entry>Error</entry>
 	      <entry>Solution</entry>
 	    </row>
           </thead>
 
 	  <tbody>
 	    <row>
 	      <entry><errorname>unsupported subdevice XX</errorname></entry>
 	      <entry><para>One or more of the device nodes was not created
 	        correctly.  Repeat the steps above.</para></entry>
             </row>
 
             <row>
               <entry><errorname>sb_dspwr(XX) timed out</errorname></entry>
               <entry><para>The I/O port is not set correctly.</para></entry>
             </row>
 
             <row>
               <entry><errorname>bad irq XX</errorname></entry>
 	      <entry><para>The IRQ is set incorrectly.  Make sure that
   	        the set IRQ and the sound IRQ are the same.</para></entry>
             </row>
 
             <row>
               <entry><errorname>xxx: gus pcm not attached, out of memory</errorname></entry>
               <entry><para>There is not enough available memory to use
                 the device.</para></entry>
             </row>
 
             <row>
               <entry><errorname>xxx: can't open /dev/dsp!</errorname></entry>
               <entry><para>Check with <command>fstat | grep dsp</command>
                 if another application is holding the device open.
                 Noteworthy troublemakers are <application>esound</application> and <application>KDE</application>'s sound
                 support.</para></entry>
             </row>
           </tbody>
         </tgroup>
       </informaltable>
     </sect3>
   </sect2>
 
   <sect2 id="sound-multiple-sources">
     <sect2info>
      <authorgroup>
       <author>
        <firstname>Munish</firstname>
        <surname>Chopra</surname>
        <contrib>Contributed by </contrib>
       </author>
      </authorgroup>
     </sect2info>
     <title>Utilizing Multiple Sound Sources</title>
 
     <para>It is often desirable to have multiple sources of sound that
       are able to play simultaneously, such as when
       <application>esound</application> or
       <application>artsd</application> do not support sharing of the
       sound device with a certain application.</para>
 
     <para>FreeBSD lets you do this through <emphasis>Virtual Sound
       Channels</emphasis>, which can be set with the &man.sysctl.8;
       facility.  Virtual channels allow you to multiplex your sound
       card's playback channels by mixing sound in the kernel.</para>
 
     <para>To set the number of virtual channels, there are two sysctl
       knobs which, if you are the <username>root</username> user, can
       be set like this:</para>
     <screen>&prompt.root; <userinput>sysctl hw.snd.pcm0.vchans=4</userinput>
 &prompt.root; <userinput>sysctl hw.snd.maxautovchans=4</userinput></screen>
 
     <para>The above example allocates four virtual channels, which is a
       practical number for everyday use.  <varname>hw.snd.pcm0.vchans</varname>
       is the number of virtual channels <devicename>pcm0</devicename> has, and is configurable
       once a device has been attached.
       <literal>hw.snd.maxautovchans</literal> is the number of virtual channels
       a new audio device is given when it is attached using
       &man.kldload.8;.  Since the <devicename>pcm</devicename> module
       can be loaded independently of the hardware drivers,
       <varname>hw.snd.maxautovchans</varname> can store how many
       virtual channels any devices which are attached later will be
       given.</para>
 
     <note>
       <para>You cannot change the number of virtual channels for a
 	device while it is in use.  First close any programs using the
 	device, such as music players or sound daemons.</para>
     </note>
 
     <para>If you are not using &man.devfs.5;, you will have to point
       your applications at
       <filename>/dev/dsp0</filename>.<replaceable>x</replaceable>,
       where <replaceable>x</replaceable> is 0 to 3 if
       <varname>hw.snd.pcm.0.vchans</varname> is set to 4 as in the
       above example.  On a system using &man.devfs.5;, the above will
       automatically be allocated transparently to the user.</para>
    </sect2>
 
   <sect2>
     <sect2info>
       <authorgroup>
 	<author>
 	  <firstname>Josef</firstname>
 	  <surname>El-Rayes</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
     </sect2info>
 
     <title>Setting Default Values for Mixer Channels</title>
 
     <para>The default values for the different mixer channels are
       hardcoded in the sourcecode of the &man.pcm.4; driver.  There are
       a lot of different applications and daemons that allow
       you to set values for the mixer they remember and set
       each time they are started, but this is not a clean
       solution, we want to have default values at the driver
       level.  This is accomplished by defining the appropriate
       values in <filename>/boot/device.hints</filename>. E.g.:</para>
 <programlisting>hint.pcm.0.vol="100"</programlisting>
 
     <para>This will set the volume channel to a default value of
       100, as soon as the &man.pcm.4; module gets loaded.</para>
 
     <note>
       <para>This is only supported in &os; 5.3-RELEASE and later.</para>
     </note>
   </sect2>
 </sect1>
 
   <sect1 id="sound-mp3">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Chern</firstname>
 	  <surname>Lee</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
       <!-- 11 Sept 2001 -->
     </sect1info>
 
-    <title>MP3 Audio</title>
+    <title>MP3 ­µ¼Ö</title>
 
     <para>MP3 (MPEG Layer 3 Audio) accomplishes near CD-quality sound,
       leaving no reason to let your FreeBSD workstation fall short of
       its offerings.</para>
 
     <sect2 id="mp3-players">
       <title>MP3 Players</title>
 
       <para>By far, the most popular X11 MP3 player is
 	<application>XMMS</application> (X Multimedia System).  
 	<application>Winamp</application>
 	skins can be used with <application>XMMS</application> since the
 	GUI is almost identical to that of Nullsoft's 
 	<application>Winamp</application>.
 	<application>XMMS</application> also has native plug-in
 	support.</para>
 
       <para><application>XMMS</application> can be installed from the
 	<filename role="package">multimedia/xmms</filename> port or package.</para>
 
       <para><application>XMMS'</application> interface is intuitive,
 	with a playlist, graphic equalizer, and more.  Those familiar
 	with <application>Winamp</application> will find
 	<application>XMMS</application> simple to use.</para>
 
       <para>The <filename role="package">audio/mpg123</filename> port is an alternative,
 	command-line MP3 player.</para>
 
       <para><application>mpg123</application> can be run by specifying
 	the sound device and the MP3 file on the command line, as
 	shown below:</para>
 
       <screen>&prompt.root; <userinput>mpg123 -a <replaceable>/dev/dsp1.0</replaceable> Foobar-GreatestHits.mp3</userinput>
 High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2 and 3.
 Version 0.59r (1999/Jun/15). Written and copyrights by Michael Hipp.
 Uses code from various people. See 'README' for more!
 THIS SOFTWARE COMES WITH ABSOLUTELY NO WARRANTY! USE AT YOUR OWN RISK!
 
 
 
 
 
 Playing MPEG stream from Foobar-GreatestHits.mp3 ...
 MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo
 </screen>
 
       <para><literal>/dev/dsp1.0</literal> should be replaced with the
 	<devicename>dsp</devicename> device entry on your system.</para>
 
     </sect2>
 
     <sect2 id="rip-cd">
       <title>Ripping CD Audio Tracks</title>
 
       <para>Before encoding a CD or CD track to MP3, the audio data on
 	the CD must be ripped onto the hard drive.  This is done by
 	copying the raw CDDA (CD Digital Audio) data to WAV
 	files.</para>
 
       <para>The <command>cdda2wav</command> tool, which is a part of
 	the <filename role="package">sysutils/cdrtools</filename>
 	suite, is used for ripping audio information from CDs and the
 	information associated with them.</para>
 
       <para>With the audio CD in the drive, the following command can
 	be issued (as <username>root</username>) to rip an entire CD
 	into individual (per track) WAV files:</para>
 
       <screen>&prompt.root; <userinput>cdda2wav -D <replaceable>0,1,0</replaceable> -B</userinput></screen>
 
       <para><application>cdda2wav</application> will support
 	ATAPI (IDE) CDROM drives.  To rip from an IDE drive, specify
 	the device name in place of the SCSI unit numbers.  For
 	example, to rip track 7 from an IDE drive:</para>
 
       <screen>&prompt.root; <userinput>cdda2wav -D <replaceable>/dev/acd0a</replaceable> -t 7</userinput></screen>
 
       <para>The <option>-D <replaceable>0,1,0</replaceable></option>
 	indicates the SCSI device <devicename>0,1,0</devicename>,
 	which corresponds to the output of <command>cdrecord
 	-scanbus</command>.</para>
 
       <para>To rip individual tracks, make use of the
 	<option>-t</option> option as shown:</para>
 
       <screen>&prompt.root; <userinput>cdda2wav -D <replaceable>0,1,0</replaceable> -t 7</userinput></screen>
 
       <para>This example rips track seven of the audio CDROM.  To rip
 	a range of tracks, for example, track one to seven, specify a
 	range:</para>
 
       <screen>&prompt.root; <userinput>cdda2wav -D <replaceable>0,1,0</replaceable> -t 1+7</userinput></screen>
 
       <para>The utility &man.dd.1; can also be used to extract audio tracks
 	on ATAPI drives, read <xref linkend="duplicating-audiocds">
 	for more information on that possibility.</para>
 
     </sect2>
 
     <sect2 id="mp3-encoding">
       <title>Encoding MP3s</title>
 
       <para>Nowadays, the mp3 encoder of choice is
 	<application>lame</application>.
 	<application>Lame</application> can be found at
 	<filename role="package">audio/lame</filename> in the ports tree.</para>
 
       <para>Using the ripped WAV files, the following command will
 	convert <filename>audio01.wav</filename> to
 	<filename>audio01.mp3</filename>:</para>
 
       <screen>&prompt.root; <userinput>lame -h -b <replaceable>128</replaceable> \
 --tt "<replaceable>Foo Song Title</replaceable>" \
 --ta "<replaceable>FooBar Artist</replaceable>" \
 --tl "<replaceable>FooBar Album</replaceable>" \
 --ty "<replaceable>2001</replaceable>" \
 --tc "<replaceable>Ripped and encoded by Foo</replaceable>" \
 --tg "<replaceable>Genre</replaceable>" \
 <replaceable>audio01.wav audio01.mp3</replaceable></userinput></screen>
 
       <para>128&nbsp;kbits seems to be the standard MP3 bitrate in use.
 	Many enjoy the higher quality 160, or 192.  The higher the
 	bitrate, the more disk space the resulting MP3 will
 	consume--but the quality will be higher.  The
 	<option>-h</option> option turns on the <quote>higher quality
 	but a little slower</quote> mode.  The options beginning with
 	<option>--t</option> indicate ID3 tags, which usually contain
 	song information, to be embedded within the MP3 file.
 	Additional encoding options can be found by consulting the
 	lame man page.</para>
     </sect2>
 
     <sect2 id="mp3-decoding">
       <title>Decoding MP3s</title>
 
       <para>In order to burn an audio CD from MP3s, they must be
 	converted to a non-compressed WAV format.  Both
 	<application>XMMS</application> and
 	<application>mpg123</application> support the output of MP3 to
 	an uncompressed file format.</para>
 
       <para>Writing to Disk in <application>XMMS</application>:</para>
 
       <procedure>
 	<step>
 	  <para>Launch <application>XMMS</application>.</para>
 	</step>
 
 	<step>
 	  <para>Right-click on the window to bring up the
 	    <application>XMMS</application> menu.</para>
 	</step>
 
 	<step>
 	  <para>Select <literal>Preference</literal> under
 	    <literal>Options</literal>.</para>
 	</step>
 
 	<step>
 	  <para>Change the Output Plugin to <quote>Disk Writer
 	      Plugin</quote>.</para>
 	</step>
 
 	<step>
 	  <para>Press <literal>Configure</literal>.</para>
 	</step>
 
 	<step>
 	  <para>Enter (or choose browse) a directory to write the
 	    uncompressed files to.</para>
 	</step>
 
 	<step>
 	  <para>Load the MP3 file into <application>XMMS</application>
 	    as usual, with volume at 100% and EQ settings turned
 	    off.</para>
 	</step>
 
 	<step>
 	  <para>Press <literal>Play</literal> &mdash;
 	    <application>XMMS</application> will appear as if it is
 	    playing the MP3, but no music will be heard.  It is
 	    actually playing the MP3 to a file.</para>
 	</step>
 
 	<step>
 	  <para>Be sure to set the default Output Plugin back to what
 	    it was before in order to listen to MP3s again.</para>
 	</step>
       </procedure>
 
       <para>Writing to stdout in <application>mpg123</application>:</para>
 
       <procedure>
 	<step>
 	  <para>Run <command>mpg123 -s <replaceable>audio01.mp3</replaceable>
 	    &gt; audio01.pcm</command></para>
 	</step>
       </procedure>
 
       <para><application>XMMS</application> writes a file in the WAV
 	format, while <application>mpg123</application> converts the
 	MP3 into raw PCM audio data.  Both of these formats can be
 	used with <application>cdrecord</application> to create audio CDs.
 	You have to use raw PCM with &man.burncd.8;.
 	If you use WAV files, you will notice a small tick sound at the
 	beginning of each track, this sound is the header of the WAV
 	file.  You can simply remove the header of a WAV file with the
 	utility <application>SoX</application> (it can be installed from
 	the <filename role="package">audio/sox</filename> port or
 	package):</para>
 
       <screen>&prompt.user; <userinput>sox -t wav -r 44100 -s -w -c 2 <replaceable>track.wav track.raw</replaceable></userinput></screen>
 
       <para>Read <xref linkend="creating-cds"> for more information on using a
 	  CD burner in FreeBSD.</para>
     </sect2>
  </sect1>
 
  <sect1 id="video-playback">
   <sect1info>
     <authorgroup>
       <author>
         <firstname>Ross</firstname>
 	<surname>Lippert</surname>
 	<contrib>Contributed by </contrib>
       </author>
     </authorgroup>
     <!-- 5 June 2002 -->
   </sect1info>
 
-  <title>Video Playback</title>
+  <title>¼½©ñ¼v¤ù</title>
 
     <para>Video playback is a very new and rapidly developing application
       area.  Be patient.  Not everything is going to work as smoothly as
       it did with sound.</para>
 
     <para>Before you begin, you should know the model of the video
       card you have and the chip it uses.  While <application>&xorg;</application> and <application>&xfree86;</application> support a
       wide variety of video cards, fewer give good playback
       performance.  To obtain a list of extensions supported by the
       X server using your card use the command &man.xdpyinfo.1; while
       X11 is running.</para>
 
     <para>It is a good idea to have a short MPEG file which can be
       treated as a test file for evaluating various players and
       options.  Since some DVD players will look for DVD media in
       <filename>/dev/dvd</filename> by default, or have this device
       name hardcoded in them, you might find it useful to make
       symbolic links to the proper devices:</para>
 
       <screen>&prompt.root; <userinput>ln -sf /dev/acd0c /dev/dvd</userinput>
 &prompt.root; <userinput>ln -sf /dev/racd0c /dev/rdvd</userinput></screen>
 
     <para>On FreeBSD&nbsp;5.X, which uses &man.devfs.5; there
         is a slightly different set of recommended links:</para>
 
       <screen>&prompt.root; <userinput>ln -sf /dev/acd0 /dev/dvd</userinput>
 &prompt.root; <userinput>ln -sf /dev/acd0 /dev/rdvd</userinput></screen>
 
     <para>Note that due to the nature of &man.devfs.5;,
       manually created links like these will not persist if you reboot
       your system.  In order to create the symbolic links
       automatically whenever you boot your system, add the following
       lines to <filename>/etc/devfs.conf</filename>:</para>
 
     <programlisting>link acd0 dvd
 link acd0 rdvd</programlisting>
 
     <para>Additionally, DVD decryption, which requires invoking
       special DVD-ROM functions, requires write permission on the DVD
       devices.</para>
 
     <indexterm>
       <primary>kernel options</primary>
       <secondary>CPU_ENABLE_SSE</secondary>
     </indexterm>
     <indexterm>
       <primary>kernel options</primary>
       <secondary>USER_LDT</secondary>
     </indexterm>
 
     <para>Some of the ports discussed rely on the following kernel
       options to build correctly.  Before attempting to build, add
       this option to the kernel configuration file, build a new kernel, and reboot:</para>
 
       <programlisting>options CPU_ENABLE_SSE</programlisting>
 
     <note>
       <para>On &os;&nbsp;4.X <literal>options USER_LDT</literal> should
 	be added to the kernel configuration file.  This option is not
 	available on &os;&nbsp;5.X and later version.</para>
     </note>
 
     <para>To enhance the shared memory X11 interface, it is
       recommended that the values of some &man.sysctl.8; variables
       should be increased:</para>
 
       <programlisting>kern.ipc.shmmax=67108864
 kern.ipc.shmall=32768</programlisting>
 
   <sect2 id="video-interface">
     <title>Determining Video Capabilities</title>
 
     <indexterm><primary>XVideo</primary></indexterm>
     <indexterm><primary>SDL</primary></indexterm>
     <indexterm><primary>DGA</primary></indexterm>
 
     <para>There are several possible ways to display video under X11.
       What will really work is largely hardware dependent.  Each
       method described below will have varying quality across
       different hardware.  Secondly, the rendering of video in X11 is
       a topic receiving a lot of attention lately, and with each
       version of <application>&xorg;</application>, or of <application>&xfree86;</application>, there may be significant improvement.</para>
 
     <para>A list of common video interfaces:</para>
 
     <orderedlist>
     <listitem>
       <para>X11: normal X11 output using shared memory.</para>
     </listitem>
     <listitem>
       <para>XVideo: an extension to the X11
       interface which supports video in any X11 drawable.</para>
     </listitem>
     <listitem>
       <para>SDL: the Simple Directmedia Layer.</para>
     </listitem>
     <listitem>
       <para>DGA: the Direct Graphics Access.</para>
     </listitem>
     <listitem>
       <para>SVGAlib: low level console graphics layer.</para>
     </listitem>
     </orderedlist>
 
     <sect3 id="video-interface-xvideo">
     <title>XVideo</title>
 
       <para><application>&xorg;</application> and <application>&xfree86; 4.X</application> have an extension called
         <emphasis>XVideo</emphasis> (aka Xvideo, aka Xv, aka xv) which
         allows video to be directly displayed in drawable objects
         through a special acceleration.  This extension provides very
         good quality playback even on low-end machines.</para>
 
       <para>To check whether the extension is running,
       use <command>xvinfo</command>:</para>
 
         <screen>&prompt.user; <userinput>xvinfo</userinput></screen>
 
       <para>XVideo is supported for your card if the result looks like:</para>
 <screen>X-Video Extension version 2.2
 screen #0
   Adaptor #0: "Savage Streams Engine"
     number of ports: 1
     port base: 43
     operations supported: PutImage 
     supported visuals:
       depth 16, visualID 0x22
       depth 16, visualID 0x23
     number of attributes: 5
       "XV_COLORKEY" (range 0 to 16777215)
               client settable attribute
               client gettable attribute (current value is 2110)
       "XV_BRIGHTNESS" (range -128 to 127)
               client settable attribute
               client gettable attribute (current value is 0)
       "XV_CONTRAST" (range 0 to 255)
               client settable attribute
               client gettable attribute (current value is 128)
       "XV_SATURATION" (range 0 to 255)
               client settable attribute
               client gettable attribute (current value is 128)
       "XV_HUE" (range -180 to 180)
               client settable attribute
               client gettable attribute (current value is 0)
     maximum XvImage size: 1024 x 1024
     Number of image formats: 7
       id: 0x32595559 (YUY2)
         guid: 59555932-0000-0010-8000-00aa00389b71
         bits per pixel: 16
         number of planes: 1
         type: YUV (packed)
       id: 0x32315659 (YV12)
         guid: 59563132-0000-0010-8000-00aa00389b71
         bits per pixel: 12
         number of planes: 3
         type: YUV (planar)
       id: 0x30323449 (I420)
         guid: 49343230-0000-0010-8000-00aa00389b71
         bits per pixel: 12
         number of planes: 3
         type: YUV (planar)
       id: 0x36315652 (RV16)
         guid: 52563135-0000-0000-0000-000000000000
         bits per pixel: 16
         number of planes: 1
         type: RGB (packed)
         depth: 0
         red, green, blue masks: 0x1f, 0x3e0, 0x7c00
       id: 0x35315652 (RV15)
         guid: 52563136-0000-0000-0000-000000000000
         bits per pixel: 16
         number of planes: 1
         type: RGB (packed)
         depth: 0
         red, green, blue masks: 0x1f, 0x7e0, 0xf800
       id: 0x31313259 (Y211)
         guid: 59323131-0000-0010-8000-00aa00389b71
         bits per pixel: 6
         number of planes: 3
         type: YUV (packed)
       id: 0x0
         guid: 00000000-0000-0000-0000-000000000000
         bits per pixel: 0
         number of planes: 0
         type: RGB (packed)
         depth: 1
         red, green, blue masks: 0x0, 0x0, 0x0</screen>
 
     <para>Also note that the formats listed (YUV2, YUV12, etc) are not
      present with every implementation of XVideo and their absence may
      hinder some players.</para>
 
     <para>If the result looks like:</para>
 <screen>X-Video Extension version 2.2
 screen #0
 no adaptors present</screen>
 
     <para>Then XVideo is probably not supported for your card.</para>
 
     <para>If XVideo is not supported for your card, this only means
       that it will be more difficult for your display to meet the
       computational demands of rendering video.  Depending on your
       video card and processor, though, you might still be able to
       have a satisfying experience.  You should probably read about
       ways of improving performance in the advanced reading <xref
       linkend="video-further-reading">.</para>
 
     </sect3>
 
     <sect3 id="video-interface-SDL">
     <title>Simple Directmedia Layer</title>
 
     <para>The Simple Directmedia Layer, SDL, was intended to be a
       porting layer between &microsoft.windows;, BeOS, and &unix;,
       allowing cross-platform applications to be developed which made
       efficient use of sound and graphics.  The SDL layer provides a
       low-level abstraction to the hardware which can sometimes be
       more efficient than the X11 interface.</para>
 
     <para>The SDL can be found at <filename role="package">devel/sdl12</filename>.</para>
 
     </sect3>
 
     <sect3 id="video-interface-DGA">
     <title>Direct Graphics Access</title>
 
     <para>Direct Graphics Access is an X11 extension which allows
       a program to bypass the X server and directly alter the
       framebuffer.  Because it relies on a low level memory mapping to
       effect this sharing, programs using it must be run as
       <username>root</username>.</para>
 
     <para>The DGA extension can be tested and benchmarked by
       &man.dga.1;.  When <command>dga</command> is running, it
       changes the colors of the display whenever a key is pressed.  To
       quit, use <keycap>q</keycap>.</para>
 
     </sect3>
 
   </sect2>
 
   <sect2 id="video-ports">
     <title>Ports and Packages Dealing with Video</title>
 
     <indexterm><primary>video ports</primary></indexterm>
     <indexterm><primary>video packages</primary></indexterm>
 
     <para>This section discusses the software available from the
       FreeBSD Ports Collection which can be used for video playback.
       Video playback is a very active area of software development,
       and the capabilities of various applications are bound to
       diverge somewhat from the descriptions given here.</para>
 
     <para>Firstly, it is important to know that many of the video
       applications which run on FreeBSD were developed as Linux
       applications.  Many of these applications are still
       beta-quality.  Some of the problems that you may encounter with
       video packages on FreeBSD include:</para>
 
       <orderedlist>
 
       <listitem>
         <para>An application cannot playback a file which another
           application produced.</para>
       </listitem> 
 
       <listitem>
         <para>An application cannot playback a file which the
           application itself produced.</para>
       </listitem>
 
       <listitem>
         <para>The same application on two different machines,
           rebuilt on each machine for that machine, plays back the same
           file differently.</para>
       </listitem>
 
       <listitem>
         <para>A seemingly trivial filter like rescaling of the image
           size results in very bad artifacts from a buggy rescaling
           routine.</para>
       </listitem>
 
       <listitem>
         <para>An application frequently dumps core.</para>
       </listitem>
 
       <listitem>
         <para>Documentation is not installed with the port and can be
           found either on the web or under the port's <filename class='directory'>work</filename>
           directory.</para>
       </listitem>
 
       </orderedlist>
 
     <para>Many of these applications may also exhibit
       <quote>Linux-isms</quote>.  That is, there may be
       issues resulting from the way some standard libraries are
       implemented in the Linux distributions, or some features of the
       Linux kernel which have been assumed by the authors of the
       applications.  These issues are not always noticed and worked around
       by the port maintainers, which can lead to problems like
       these:</para>
        
       <orderedlist>
 
       <listitem>
         <para>The use of <filename>/proc/cpuinfo</filename> to detect
           processor characteristics.</para>
       </listitem>
 
       <listitem>
         <para>A misuse of threads which causes a program to hang upon
           completion instead of truly terminating.</para>
       </listitem>
 
       <listitem>
         <para>Software not yet in the FreeBSD Ports Collection
 	  which is commonly used in conjunction with the application.</para>
       </listitem>
 
       </orderedlist>
 
       <para>So far, these application developers have been cooperative with
         port maintainers to minimize the work-arounds needed for
         port-ing.</para>
 
     <sect3 id="video-mplayer">
       <title>MPlayer</title>
 
       <para><application>MPlayer</application> is a recently developed and rapidly developing
         video player.  The goals of the <application>MPlayer</application> team are speed and
         flexibility on Linux and other Unices.  The project was
         started when the team founder got fed up with bad playback
         performance on then available players.  Some would say that
         the graphical interface has been sacrificed for a streamlined
         design.  However, once
         you get used to the command line options and the key-stroke
         controls, it works very well.</para>
 
       <sect4 id="video-mplayer-building">
         <title>Building MPlayer</title>
         <indexterm><primary>MPlayer</primary>
 	           <secondary>making</secondary></indexterm>
 
 	<para><application>MPlayer</application> resides in <filename
 	  role="package">multimedia/mplayer</filename>.
 	  <application>MPlayer</application> performs a variety of
 	  hardware checks during the build process, resulting in a
 	  binary which will not be portable from one system to
 	  another.  Therefore, it is important to build it from
 	  ports and not to use a binary package.  Additionally, a
 	  number of options can be specified in the <command>make</command>
 	  command line, as described in the <filename>Makefile</filename> and at the start of the build:</para>
 
 	<screen>&prompt.root; <userinput>cd /usr/ports/multimedia/mplayer</userinput>
 &prompt.root; <userinput>make</userinput>
 N - O - T - E
 
 Take a careful look into the Makefile in order
 to learn how to tune mplayer towards you personal preferences!
 For example,
 make WITH_GTK1
 builds MPlayer with GTK1-GUI support.
 If you want to use the GUI, you can either install
 /usr/ports/multimedia/mplayer-skins
 or download official skin collections from
 http://www.mplayerhq.hu/homepage/dload.html
 </screen>
 
 	<para>The default port options should be sufficient for most
 	  users.  However, if you need the XviD codec, you have to
 	  specify the <makevar>WITH_XVID</makevar> option in the
 	  command line.  The default DVD device can also be defined
 	  with the <makevar>WITH_DVD_DEVICE</makevar> option, by
 	  default <filename>/dev/acd0</filename> will be used.</para>
 
         <para>As of this writing, the <application>MPlayer</application> port will build its HTML
           documentation and two executables,
           <command>mplayer</command>, and
           <command>mencoder</command>, which is a tool for
           re-encoding video.</para>
 
         <para>The HTML documentation for <application>MPlayer</application> is very informative.
           If the reader finds the information on video hardware and
           interfaces in this chapter lacking, the <application>MPlayer</application> documentation
           is a very thorough supplement.  You should definitely take
           the time to read the <application>MPlayer</application>
           documentation if you are looking for information about video
           support in &unix;.</para>
 
       </sect4>
 
       <sect4 id="video-mplayer-using">
         <title>Using MPlayer</title>
         <indexterm><primary>MPlayer</primary>
 	           <secondary>use</secondary></indexterm>
 
         <para>Any user of <application>MPlayer</application> must set up a
           <filename>.mplayer</filename> subdirectory of her
           home directory.  To create this necessary subdirectory,
 	  you can type the following:</para>
 
 <screen>&prompt.user; <userinput>cd /usr/ports/multimedia/mplayer</userinput>
 &prompt.user; <userinput>make install-user</userinput></screen>
 
 	<para>The command options for <command>mplayer</command> are
 	  listed in the manual page.  For even more detail there is HTML
 	  documentation.  In this section, we will describe only a few
 	  common uses.</para>
 
 	<para>To play a file, such as
 	  <filename><replaceable>testfile.avi</replaceable></filename>,
 	  through one of the various video interfaces set the
 	  <option>-vo</option> option:</para>
 
 	  <screen>&prompt.user; <userinput>mplayer -vo xv testfile.avi</userinput></screen>
 	  <screen>&prompt.user; <userinput>mplayer -vo sdl testfile.avi</userinput></screen>
 	  <screen>&prompt.user; <userinput>mplayer -vo x11 testfile.avi</userinput></screen>
 	  <screen>&prompt.root; <userinput>mplayer -vo dga testfile.avi</userinput></screen>
 	  <screen>&prompt.root; <userinput>mplayer -vo 'sdl:dga' testfile.avi</userinput></screen>
 
 	<para>It is worth trying all of these options, as their relative
 	  performance depends on many factors and will vary significantly
 	  with hardware.</para>
 
 	<para>To play from a DVD, replace the
 	 <filename>testfile.avi</filename> with <option>dvd://<replaceable>N</replaceable> -dvd-device
 	 <replaceable>DEVICE</replaceable></option> where <replaceable>N</replaceable> is
 	 the title number to play and
 	 <filename><replaceable>DEVICE</replaceable></filename> is the
 	 device node for the DVD-ROM.  For example, to play title 3
 	 from <filename>/dev/dvd</filename>:</para>
 
 	<screen>&prompt.root; <userinput>mplayer -vo xv dvd://3 -dvd-device /dev/dvd</userinput></screen>
 
 	<note>
 	  <para>The default DVD device can be defined during the build
 	    of the <application>MPlayer</application> port via the
 	    <makevar>WITH_DVD_DEVICE</makevar> option.  By default,
 	    this device is <filename>/dev/acd0</filename>.  More
 	    details can be found in the port
 	    <filename>Makefile</filename>.</para>
 	</note>
 
 	<para>To stop, pause, advance and so on, consult the
 	  keybindings, which are output by running <command>mplayer
 	  -h</command> or read the manual page.</para>
 
         <para>Additional important options for playback are:
           <option>-fs -zoom</option> which engages the fullscreen mode
           and <option>-framedrop</option> which helps performance.</para>
 
 	<para>In order for the mplayer command line to not become too
 	  large, the user can create a file
 	  <filename>.mplayer/config</filename> and set default options
 	  there:</para>
 <programlisting>vo=xv
 fs=yes
 zoom=yes</programlisting>
 
 	<para>Finally, <command>mplayer</command> can be used to rip a
 	  DVD title into a <filename>.vob</filename> file.  To dump
 	  out the second title from a DVD, type this:</para>
 
 	  <screen>&prompt.root; <userinput>mplayer -dumpstream -dumpfile out.vob dvd://2 -dvd-device /dev/dvd</userinput></screen>
 
         <para>The output file, <filename>out.vob</filename>, will be
 	  MPEG and can be manipulated by the other packages described
 	  in this section.</para>
 
       </sect4>
       <sect4 id="video-mencoder">
         <title>mencoder</title>
         <indexterm>
 	  <primary>mencoder</primary>
 	</indexterm>
 
 	<para>Before using
          <command>mencoder</command> it is a good idea to
 	 familiarize yourself with the options from the HTML
 	 documentation.  There is a manual page, but it is not very
 	 useful without the HTML documentation.  There are innumerable ways to
 	 improve quality, lower bitrate, and change formats, and some
 	 of these tricks may make the difference between good
 	 or bad performance.  Here are a couple of examples to get
 	 you going.  First a simple copy:</para>
 
 	 <screen>&prompt.user; <userinput>mencoder input.avi -oac copy -ovc copy -o output.avi</userinput></screen>
 
          <para>Improper combinations of command line options can yield
 	 output files that are
 	 unplayable even by <command>mplayer</command>.  Thus, if you
 	 just want to rip to a file, stick to the <option>-dumpfile</option>
 	 in <command>mplayer</command>.</para>
 
 	 <para>To convert <filename>input.avi</filename> to the MPEG4
 	 codec with MPEG3 audio encoding (<filename role="package">audio/lame</filename> is required):</para>
 
 	 <screen>&prompt.user; <userinput>mencoder input.avi -oac mp3lame -lameopts br=192 \
 	 -ovc lavc -lavcopts vcodec=mpeg4:vhq -o output.avi</userinput></screen>
 
 	 <para>This has produced output playable by <command>mplayer</command>
 	 and <command>xine</command>.</para>
 
 	 <para><filename>input.avi</filename> can be replaced with
 	   <option>dvd://1 -dvd-device /dev/dvd</option> and run as
 	   <username>root</username> to re-encode a DVD title
 	   directly.  Since you are likely to be dissatisfied with
 	   your results the first time around, it is recommended you
 	   dump the title to a file and work on the file.</para>
       </sect4>
 
     </sect3>
 
     <sect3 id="video-xine">
     <title>The xine Video Player</title>
 
     <para>The <application>xine</application> video player is a project of wide scope aiming not only at being an
      all in one video solution, but also in producing a reusable base
      library and a modular executable which can be extended with
      plugins.  It comes both as a package and as a port, <filename
      role="package">multimedia/xine</filename>.</para>
 
     <para>The <application>xine</application> player
      is still very rough around the edges, but it is clearly off to a
      good start.  In practice, <application>xine</application> requires either a fast CPU with a
      fast video card, or support for the XVideo extension.  The GUI is
      usable, but a bit clumsy.</para>
 
     <para>As of this writing, there is no input module shipped with
      <application>xine</application> which will play CSS encoded DVD's.  There are third party
      builds which do have modules for this built in them, but none
      of these are in the FreeBSD Ports Collection.</para>
 
     <para>Compared to <application>MPlayer</application>, <application>xine</application> does more for the user, but at the
       same time, takes some of the more fine-grained control away from
       the user.  The <application>xine</application> video player
       performs best on XVideo interfaces.</para>
      
     <para>By default, <application>xine</application> player will
     start up in a graphical user interface.  The menus can then be
     used to open a specific file:</para>
 
       <screen>&prompt.user; <userinput>xine</userinput></screen>
 
     <para>Alternatively, it may be invoked to play a file immediately
       without the GUI with the command:</para>
 
       <screen>&prompt.user; <userinput>xine -g -p mymovie.avi</userinput></screen>
 
     </sect3>
 
     <sect3 id="video-ports-transcode">
     <title>The transcode Utilities</title>
 
     <para>The software <application>transcode</application> is not a player, but a suite of tools for
       re-encoding video and audio files.  With <application>transcode</application>, one has the
       ability to merge video files, repair broken files, using command
       line tools with <filename>stdin/stdout</filename> stream
       interfaces.</para>
 
     <para>A great number of options can be specified during
       the build from the <filename
       role="package">multimedia/transcode</filename> port, we recommend the
       following command line to build
       <application>transcode</application>:</para>
 
     <screen>&prompt.root; <userinput>make WITH_OPTIMIZED_CFLAGS=yes WITH_LIBA52=yes WITH_LAME=yes WITH_OGG=yes \
 WITH_MJPEG=yes -DWITH_XVID=yes</userinput></screen>
 
     <para>The proposed settings should be sufficient for most users.</para>
 
     <para>To illustrate <command>transcode</command> capacities, one
       example to show how to convert a DivX file into a PAL MPEG-1
       file (PAL VCD):</para>
 
       <screen>&prompt.user; <userinput>transcode -i input.avi -V --export_prof vcd-pal -o output_vcd</userinput>
 &prompt.user; <userinput>mplex -f 1 -o output_vcd.mpg output_vcd.m1v output_vcd.mpa</userinput></screen>
 
     <para>The resulting MPEG file,
       <filename>output_vcd.mpg</filename>, is ready to be played with
       <application>MPlayer</application>.  You could even burn the
       file on a CD-R media to create a Video CD, in this case you will
       need to install and use both <filename
       role="package">multimedia/vcdimager</filename> and <filename
       role="package">sysutils/cdrdao</filename> programs.</para>
 
     <para>There is a manual page for <command>transcode</command>, but
       you should also consult the <ulink
       url="http://www.transcoding.org/cgi-bin/transcode">transcode
       wiki</ulink> for further information and examples.</para>
     </sect3>
 
   </sect2>
 
   <sect2 id="video-further-reading">
     <title>Further Reading</title>
 
     <para>The various video software packages for FreeBSD are
       developing rapidly.  It is quite possible that in the near
       future many of the problems discussed here will have been
       resolved.  In the mean time, those who
      want to get the very most out of FreeBSD's A/V capabilities will
      have to cobble together knowledge from several FAQs and tutorials
      and use a few different applications.  This section exists to
       give the reader pointers to such additional information.</para>
 
     <para>The 
       <ulink url="http://www.mplayerhq.hu/DOCS/">MPlayer documentation</ulink>
       is very technically informative.
       These documents should probably be consulted by anyone wishing
       to obtain a high level of expertise with &unix; video.  The
       <application>MPlayer</application> mailing list is hostile to anyone who has not bothered
       to read the documentation, so if you plan on making bug reports
       to them, RTFM.</para>
 
     <para>The
       <ulink url="http://dvd.sourceforge.net/xine-howto/en_GB/html/howto.html">      xine HOWTO</ulink>
       contains a chapter on performance improvement
       which is general to all players.</para>
 
     <para>Finally, there are some other promising applications which
     the reader may try:</para>
 
     <itemizedlist>
 
        <listitem>
          <para><ulink
 	   url="http://avifile.sourceforge.net/">Avifile</ulink> which
 	   is also a port <filename
 	   role='package'>multimedia/avifile</filename>.</para>
        </listitem>
 
        <listitem>
          <para><ulink
 	   url="http://www.dtek.chalmers.se/groups/dvd/">Ogle</ulink>
 	   which is also a port <filename
 	   role='package'>multimedia/ogle</filename>.</para>
        </listitem>
 
        <listitem>
          <para><ulink url="http://xtheater.sourceforge.net/">Xtheater</ulink></para>
        </listitem>
 
 	<listitem>
          <para><filename
            role="package">multimedia/dvdauthor</filename>, an open
            source package for authoring DVD content.</para>
         </listitem>
 
     </itemizedlist>
 
   </sect2>
  </sect1>
 
   <sect1 id="tvcard">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Josef</firstname>
 	  <surname>El-Rayes</surname>
 	  <contrib>Original contribution by </contrib>
 	</author>
       </authorgroup>
       <authorgroup>
 	<author>
 	  <firstname>Marc</firstname>
 	  <surname>Fonvieille</surname>
 	  <contrib>Enhanced and adapted by </contrib>
 	  <!-- 02 January 2004 -->
 	</author>
       </authorgroup>
     </sect1info>
 
-    <title>Setting Up TV Cards</title>
+    <title>³]©w¹qµø¥d(TV Cards)</title>
     <indexterm>
       <primary>TV cards</primary>
     </indexterm>
 
     <sect2>
       <title>Introduction</title>
 
       <para>TV cards allow you to watch broadcast or cable TV on your
 	computer.  Most of them accept composite video via an RCA or
 	S-video input and some of these cards come with a FM
 	radio tuner.</para>
 
       <para>&os; provides support for PCI-based TV cards using a
 	Brooktree Bt848/849/878/879 or a Conexant CN-878/Fusion 878a
 	Video Capture Chip with the &man.bktr.4; driver.  You must
 	also ensure the board comes with a supported tuner, consult
 	the &man.bktr.4; manual page for a list of supported
 	tuners.</para>
     </sect2>
 
     <sect2>
       <title>Adding the Driver</title>
 
       <para>To use your card, you will need to load the &man.bktr.4;
 	driver, this can be done by adding the following line to the
 	<filename>/boot/loader.conf</filename> file like this:</para>
 
       <programlisting>bktr_load="YES"</programlisting>
 
       <para>Alternatively, you may statically compile the support for
 	the TV card in your kernel, in that case add the following
 	lines to your kernel configuration:</para>
 	
       <programlisting>device	 bktr
 device	iicbus
 device	iicbb
 device	smbus</programlisting>
 
       <para>These additional device drivers are necessary because of the
 	card components being interconnected via an I2C bus.  Then build
 	and install a new kernel.</para>
 
       <para>Once the support was added to your system, you have to
 	reboot your machine.  During the boot process, your TV card
 	should show up, like this:</para>
 
       <programlisting>bktr0: &lt;BrookTree 848A&gt; mem 0xd7000000-0xd7000fff irq 10 at device 10.0 on pci0
 iicbb0: &lt;I2C bit-banging driver&gt; on bti2c0
 iicbus0: &lt;Philips I2C bus&gt; on iicbb0 master-only
 iicbus1: &lt;Philips I2C bus&gt; on iicbb0 master-only
 smbus0: &lt;System Management Bus&gt; on bti2c0
 bktr0: Pinnacle/Miro TV, Philips SECAM tuner.</programlisting>
 
       <para>Of course these messages can differ according to your
 	hardware.  However you should check if the tuner is correctly
 	detected; it is still possible to override some of the
 	detected parameters with &man.sysctl.8; MIBs and kernel
 	configuration file options.  For example, if you want to force
 	the tuner to a Philips SECAM tuner, you should add the
 	following line to your kernel configuration file:</para>
 
       <programlisting>options OVERRIDE_TUNER=6</programlisting>
 
       <para>or you can directly use &man.sysctl.8;:</para>
 
       <screen>&prompt.root; <userinput>sysctl hw.bt848.tuner=6</userinput></screen>
 
       <para>See the &man.bktr.4; manual page and the
 	<filename>/usr/src/sys/conf/NOTES</filename> file for more
 	details on the available options. (If you are under
 	&os;&nbsp;4.X, <filename>/usr/src/sys/conf/NOTES</filename> is
 	replaced with
 	<filename>/usr/src/sys/i386/conf/LINT</filename>.)</para>
     </sect2>
 
     <sect2>
       <title>Useful Applications</title>
 
       <para>To use your TV card you need to install one of the
 	following applications:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><filename role="package">multimedia/fxtv</filename>
 	    provides TV-in-a-window and image/audio/video capture
 	    capabilities.</para>
 	</listitem>
 	<listitem>
 	  <para><filename role="package">multimedia/xawtv</filename>
 	    is also a TV application, with the same features as
 	    <application>fxtv</application>.</para>
 	</listitem>
 	<listitem>
 	  <para><filename role="package">misc/alevt</filename> decodes
 	    and displays Videotext/Teletext.</para>
 	</listitem>
 	<listitem>
 	  <para><filename role="package">audio/xmradio</filename>, an
 	    application to use the FM radio tuner coming with some
 	    TV cards.</para>
 	</listitem>
 	<listitem>
 	  <para><filename role="package">audio/wmtune</filename>, a handy
 	    desktop application for radio tuners.</para>
 	</listitem>
       </itemizedlist>
 
       <para>More applications are available in the &os; Ports
 	Collection.</para>
     </sect2>
 
     <sect2>
       <title>Troubleshooting</title>
 
       <para>If you encounter any problem with your TV card, you should
 	check at first if the video capture chip and the tuner are
 	really supported by the &man.bktr.4; driver and if you used the right
 	configuration options.  For more support and various questions
 	about your TV card you may want to contact and use the
 	archives of the &a.multimedia.name; mailing list.</para>
     </sect2>
   </sect1>
 
   <sect1 id="scanners">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Marc</firstname>
 	  <surname>Fonvieille</surname>
 	  <contrib>Written by </contrib>
 	  <!-- 04 August 2004 -->
 	</author>
       </authorgroup>
     </sect1info>
 
-    <title>Image Scanners</title>
+    <title>±½´y¾¹</title>
     <indexterm>
       <primary>image scanners</primary>
     </indexterm>
 
     <sect2>
-      <title>Introduction</title>
+      <title>¤¶²Ð</title>
 
       <para>&os;, like any modern operating system, allows the use of
 	image scanners.  Standardized access to scanners is provided
 	by the <application>SANE</application> (Scanner Access Now
 	Easy) <acronym role="Application Programming
 	Interface">API</acronym> available through the &os; Ports
 	Collection.  <application>SANE</application> will also use
 	some &os; devices drivers to access to the scanner
 	hardware.</para>
 
       <para>&os; supports both SCSI and USB scanners.  Be sure your
 	scanner is supported by <application>SANE</application> prior
 	to performing any configuration.
 	<application>SANE</application> has a <ulink
 	url="http://sane-project.org/sane-supported-devices.html">supported
 	devices</ulink> list that can provide you with information
 	about the support for a scanner and its status.  The
 	&man.uscanner.4; manual page also provides a list of supported
 	USB scanners.</para>
     </sect2>
 
     <sect2>
       <title>Kernel Configuration</title>
 
       <para>As mentioned above both SCSI and USB interfaces are
 	supported.  According to your scanner interface, different
 	device drivers are required.</para>
 
       <sect3 id="scanners-kernel-usb">
 	<title>USB Interface</title>
 
 	<para>The <filename>GENERIC</filename> kernel by default
 	  includes the device drivers needed to support USB scanners.
 	  Should you decide to use a custom kernel, be sure that the
 	  following lines are present in your kernel configuration
 	  file:</para>
 
 	<programlisting>device usb
 device uhci
 device ohci
 device uscanner</programlisting>
 
 	<para>Depending upon the USB chipset on your motherboard, you
 	  will only need either <literal>device uhci</literal> or
 	  <literal>device ohci</literal>, however having both in the
 	  kernel configuration file is harmless.</para>
 
 	<para>If you do not want to rebuild your kernel and your
 	  kernel is not the <filename>GENERIC</filename> one, you can
 	  directly load the &man.uscanner.4; device driver module with
 	  the &man.kldload.8; command:</para>
 
 	<screen>&prompt.root; <userinput>kldload uscanner</userinput></screen>
 
 	<para>To load this module at each system startup, add the
 	  following line to
 	  <filename>/boot/loader.conf</filename>:</para>
 
 	<programlisting>uscanner_load="YES"</programlisting>
 
 	<para>After rebooting with the correct kernel, or after
 	  loading the required module, plug in your USB scanner.  The
 	  scanner should appear in your system message buffer
 	  (&man.dmesg.8;) as something like:</para>
 
 	<screen>uscanner0: EPSON EPSON Scanner, rev 1.10/3.02, addr 2</screen>
 
 	<para>This shows that our scanner is using the
 	  <filename>/dev/uscanner0</filename> device node.</para>
 
 	<note>
 	  <para>On &os;&nbsp;4.X, the USB daemon (&man.usbd.8;) must
 	    be running to be able to see some USB devices.  To enable
 	    this, add <literal>usbd_enable="YES"</literal> to your
 	    <filename>/etc/rc.conf</filename> file and reboot the
 	    machine.</para>
 	  </note>
       </sect3>
 
       <sect3>
 	<title>SCSI Interface</title>
 
 	<para>If your scanner comes with a SCSI interface, it is
 	  important to know which SCSI controller board you will use.
 	  According to the SCSI chipset used, you will have to tune
 	  your kernel configuration file.  The
 	  <filename>GENERIC</filename> kernel supports the most common
 	  SCSI controllers.  Be sure to read the
 	  <filename>NOTES</filename> file (<filename>LINT</filename>
 	  under &os;&nbsp;4.X) and add the correct line to your kernel
 	  configuration file.  In addition to the SCSI adapter driver,
 	  you need to have the following lines in your kernel
 	  configuration file:</para>
 
 	<programlisting>device scbus
 device pass</programlisting>
 
 	<para>Once your kernel has been properly compiled, you should
 	  be able to see the devices in your system message buffer,
 	  when booting:</para>
 
 	<screen>pass2 at aic0 bus 0 target 2 lun 0
 pass2: &lt;AGFA SNAPSCAN 600 1.10&gt; Fixed Scanner SCSI-2 device
 pass2: 3.300MB/s transfers</screen>
 
 	<para>If your scanner was not powered-on at system boot, it is
 	  still possible to manually force the detection by performing
 	  a SCSI bus scan with the &man.camcontrol.8; command:</para>
 
 	<screen>&prompt.root; <userinput>camcontrol rescan all</userinput>
 Re-scan of bus 0 was successful
 Re-scan of bus 1 was successful
 Re-scan of bus 2 was successful
 Re-scan of bus 3 was successful</screen>
 
 	<para>Then the scanner will appear in the SCSI devices
 	  list:</para>
 
 	<screen>&prompt.root; <userinput>camcontrol devlist</userinput>
 &lt;IBM DDRS-34560 S97B&gt;              at scbus0 target 5 lun 0 (pass0,da0)
 &lt;IBM DDRS-34560 S97B&gt;              at scbus0 target 6 lun 0 (pass1,da1)
 &lt;AGFA SNAPSCAN 600 1.10&gt;           at scbus1 target 2 lun 0 (pass3)
 &lt;PHILIPS CDD3610 CD-R/RW 1.00&gt;     at scbus2 target 0 lun 0 (pass2,cd0)</screen>
 
 	<para>More details about SCSI devices, are available in the
 	  &man.scsi.4; and &man.camcontrol.8; manual pages.</para>
       </sect3>
     </sect2>
 
     <sect2>
       <title>SANE Configuration</title>
 
       <para>The <application>SANE</application> system has been
 	splitted in two parts: the backends (<filename
 	role="package">graphics/sane-backends</filename>) and the
 	frontends (<filename
 	role="package">graphics/sane-frontends</filename>).  The
 	backends part provides access to the scanner itself.  The
 	<application>SANE</application>'s <ulink
 	url="http://sane-project.org/sane-supported-devices.html">supported
 	devices</ulink> list specifies which backend will support your
 	image scanner.  It is mandatory to determine the correct
 	backend for your scanner if you want to be able to use your
 	device.  The frontends part provides the graphical scanning
 	interface (<application>xscanimage</application>).</para>
 
       <para>The first thing to do is install the <filename
 	role="package">graphics/sane-backends</filename> port or
 	package.  Then, use the <command>sane-find-scanner</command>
 	command to check the scanner detection by the
 	<application>SANE</application> system:</para>
 
       <screen>&prompt.root; <userinput>sane-find-scanner -q</userinput>
 found SCSI scanner "AGFA SNAPSCAN 600 1.10" at /dev/pass3</screen>
 
       <para>The output will show the interface type of the scanner and
 	the device node used to attach the scanner to the system.  The
 	vendor and the product model may not appear, it is not
 	important.</para>
 
       <note>
 	<para>Some USB scanners require you to load a firmware, this
 	  is explained in the backend manual page.  You should also read
 	  &man.sane-find-scanner.1; and &man.sane.7; manual
 	  pages.</para>
       </note>
 
       <para>Now we have to check if the scanner will be identified by
 	a scanning frontend.  By default, the
 	<application>SANE</application> backends comes with a command
 	line tool called &man.scanimage.1;.  This command allows you
 	to list the devices and to perform an image acquisition from
 	the command line.  The <option>-L</option> option is used to
 	list the scanner device:</para>
 
       <screen>&prompt.root; <userinput>scanimage -L</userinput>
 device `snapscan:/dev/pass3' is a AGFA SNAPSCAN 600 flatbed scanner</screen>
 
       <para>No output or a message saying that no scanners were
 	identified indicates that &man.scanimage.1; is unable to
 	identify the scanner.  If this happens, you will need to edit
 	the backend configuration file and define the scanner device
 	used.  The <filename
 	class="directory">/usr/local/etc/sane.d/</filename> directory
 	contains all backends configuration files.  This
 	identification problem does appear with certain USB
 	scanners.</para>
 
       <para>For example, with the USB scanner used in the <xref
 	linkend="scanners-kernel-usb">,
 	<command>sane-find-scanner</command> gives us the following
 	information:</para>
 
       <screen>&prompt.root; <userinput>sane-find-scanner -q</userinput>
 found USB scanner (UNKNOWN vendor and product) at device /dev/uscanner0</screen>
       <para>The scanner is correctly detected, it uses the USB
 	interface and is attached to the
 	<filename>/dev/uscanner0</filename> device node.  We can now
 	check if the scanner is correctly identified:</para>
 
       <screen>&prompt.root; <userinput>scanimage -L</userinput>
 
 No scanners were identified. If you were expecting something different,
 check that the scanner is plugged in, turned on and detected by the
 sane-find-scanner tool (if appropriate). Please read the documentation
 which came with this software (README, FAQ, manpages).</screen>
 
       <para>Since the scanner is not identified, we will need to edit
 	the <filename>/usr/local/etc/sane.d/epson.conf</filename>
 	file.  The scanner model used was the &epson.perfection; 1650,
 	so we know the scanner will use the <literal>epson</literal>
 	backend.  Be sure to read the help comments in the backends
 	configuration files.  Line changes are quite simple: comment
 	out all lines that have the wrong interface for your scanner
 	(in our case, we will comment out all lines starting with the
 	word <literal>scsi</literal> as our scanner uses the USB
 	interface), then add at the end of the file a line specifying
 	the interface and the device node used.  In this case, we add
 	the following line:</para>
 
       <programlisting>usb /dev/uscanner0</programlisting>
 
       <para>Please be sure to read the comments provided in the
 	backend configuration file as well as the backend manual page
 	for more details and correct syntax to use.  We can now verify
 	if the scanner is identified:</para>
 
       <screen>&prompt.root; <userinput>scanimage -L</userinput>
 device `epson:/dev/uscanner0' is a Epson GT-8200 flatbed scanner</screen>
 
       <para>Our USB scanner has been identified.  It is not important
 	if the brand and the model do not match.  The key item to be
 	concerned with is the
 	<literal>`epson:/dev/uscanner0'</literal> field, which give us
 	the right backend name and the right device node.</para>
 
       <para>Once the <command>scanimage -L</command> command is able
 	to see the scanner, the configuration is complete.  The device
 	is now ready to scan.</para>
 
       <para>While &man.scanimage.1; does allow us to perform an
 	image acquisition from the command line, it is preferable to
 	use a graphical user interface to perform image scanning.
 	<application>SANE</application> offers a simple but efficient
 	graphical interface: <application>xscanimage</application>
 	(<filename
 	role="package">graphics/sane-frontends</filename>).</para>
 
       <para><application>Xsane</application> (<filename
 	role="package">graphics/xsane</filename>) is another popular
 	graphical scanning frontend.  This frontend offers advanced
 	features such as various scanning mode (photocopy, fax, etc.),
 	color correction, batch scans, etc.  Both of these applications
 	are useable as a <application>GIMP</application>
 	plugin.</para>
     </sect2>
 
     <sect2>
       <title>Allowing Scanner Access to Other Users</title>
 
       <para>All previous operations have been done with
 	<username>root</username> privileges.  You may however, need
 	other users to have access
 	to the scanner.  The user will need read and write
 	permissions to the device node used by the scanner.  As an
 	example, our USB scanner uses the device node
 	<filename>/dev/uscanner0</filename> which is owned by the
 	<groupname>operator</groupname> group.  Adding the user
 	<username>joe</username> to the
 	<groupname>operator</groupname> group will allow him to use
 	the scanner:</para>
 
       <screen>&prompt.root; <userinput>pw groupmod operator -m <replaceable>joe</replaceable></userinput></screen>
 
       <para>For more details read the &man.pw.8; manual page.  You
 	also have to set the correct write permissions (0660 or 0664)
 	on the <filename>/dev/uscanner0</filename> device node, by
 	default the <groupname>operator</groupname> group can only
 	read the device node.  This is done by adding the following
 	lines to the <filename>/etc/devfs.rules</filename> file:</para>
 
       <programlisting>[system=5]
 add path uscanner0 mode 660</programlisting>
 
       <para>Then add the following to
 	<filename>/etc/rc.conf</filename> and reboot the
 	machine:</para>
 
       <programlisting>devfs_system_ruleset="system"</programlisting>
 
       <para>More information regarding these lines can be found in the
 	&man.devfs.8; manual page.  Under &os;&nbsp;4.X, the
 	<groupname>operator</groupname> group has, by default, read
 	and write permissions to
 	<filename>/dev/uscanner0</filename>.</para>
 
       <note>
 	<para>Of course, for security reasons, you should think twice
 	  before adding a user to any group, especially the
 	  <groupname>operator</groupname> group.</para>
       </note>
     </sect2>
   </sect1>
 </chapter>
 
 <!--
      Local Variables:
      mode: sgml
      sgml-declaration: "../chapter.decl"
      sgml-indent-data: t
      sgml-omittag: nil
      sgml-always-quote-attributes: t
      sgml-parent-document: ("../book.sgml" "part" "chapter")
      End:
 -->
diff --git a/zh_TW.Big5/books/handbook/ports/chapter.sgml b/zh_TW.Big5/books/handbook/ports/chapter.sgml
index 64393aaf09..5be761ba7f 100644
--- a/zh_TW.Big5/books/handbook/ports/chapter.sgml
+++ b/zh_TW.Big5/books/handbook/ports/chapter.sgml
@@ -1,1405 +1,1366 @@
 <!--
      The FreeBSD Documentation Project
 
      $FreeBSD$
 -->
 
 <chapter id="ports">
-  <title>Installing Applications: Packages and Ports</title>
+  <title>³nÅé®M¥óºÞ²z¨t²Î¡GPackages ¤Î Ports ¾÷¨î</title>
 
   <sect1 id="ports-synopsis">
-    <title>Synopsis</title>
+    <title>·§­z</title>
 
     <indexterm><primary>ports</primary></indexterm>
     <indexterm><primary>packages</primary></indexterm>
-    <para>FreeBSD is bundled with a rich collection of system tools as
-      part of the base system.  However, there is only so much one can
-      do before needing to install an additional third-party
-      application to get real work done.  FreeBSD provides two
-      complementary technologies for installing third party software
-      on your system: the FreeBSD Ports Collection (for installing from
-      source), and packages (for installing from pre-built binaries).
-      Either method may be used to install the
-      newest version of your favorite applications from local media or
-      straight off the network.</para>
-
-    <para>After reading this chapter, you will know:</para>
+    <para>¾¨ºÞ FreeBSD ¦b base system ¤w¥[¤F«Ü¦h¨t²Î¤u¨ã¡C
+	µM¦Ó¡A¦b¹ê°È¹B¥Î¤W¡A±z¥i¯à¤´»Ý­n¦w¸ËÃB¥~ªº³nÅé¡C
+	FreeBSD ´£¨Ñ¤F 2 ºØ¦w¸ËÀ³¥Îµ{¦¡ªº®M¥óºÞ²z¨t²Î¡JPorts Collection(¥H soucre ¨Ó½sĶ¡B¦w¸Ë) ©M 
+	package(¹w¥ý½sĶ¦nªº binary ÀÉ)¡C¤W­zªº¤è¦¡¡AµL½×­n¥Î­þ¤@ºØ¡A³£¥i¥H¥Ñ¹³¬O CDROM 
+	µ¥©Îºô¸ô¤W¨Ó¦w¸Ë·Q¸Ëªº³Ì·sª©³nÅé¡C</para>
+
+    <para>Ū§¹³o³¹¡A±z±N¤F¸Ñ¡G</para>
 
     <itemizedlist>
       <listitem>
-	<para>How to install third-party binary software packages.</para>
+	<para>¦p¦ó¥H packages ¨Ó¦w¸Ë³nÅé¡C</para>
       </listitem>
       <listitem>
-	<para>How to build third-party software from source by using the ports
-	collection.</para>
+	<para>¦p¦ó¥H ports ¨Ó¦w¸Ë³nÅé¡C</para>
       </listitem>
       <listitem>
-	<para>How to remove previously installed packages or ports.</para>
+	<para>¤w¦w¸Ëªº packages ©Î ports ­n¦p¦ó²¾°£¡C</para>
       </listitem>
       <listitem>
-	<para>How to override the default values that the ports
-	  collection uses.</para>
+	<para>¦p¦ó§ó§ï(override) ports collection ©Ò¨Ï¥Îªº¹w³]­È¡C</para>
       </listitem>
       <listitem>
-	<para>How to find the appropriate software package.</para>
+	<para>¦p¦ó¦b®M¥óºÞ²z¨t²Î¤¤¡A§ä¥X·Q¸Ëªº³nÅé¡C</para>
       </listitem>
       <listitem>
-	<para>How to upgrade your applications.</para>
+	<para>¦p¦ó¤É¯Å¤w¦w¸Ëªº³nÅé¡C</para>
       </listitem>
     </itemizedlist>
   </sect1>
 
   <sect1 id="ports-overview">
-    <title>Overview of Software Installation</title>
+    <title>¦w¸Ë³nÅ骺¦UºØ¤è¦¡¤¶²Ð</title>
 
-    <para>If you have used a &unix; system before you will know that
-      the typical procedure for installing third party software goes
-      something like this:</para>
+    <para>³q±`­n¦b &unix; ¨t²Î¤W¦w¸Ë³nÅé®É¡A¦³´X­Ó¨BÆJ­n§@¡G</para>
 
     <procedure>
       <step>
-	<para>Download the software, which might be distributed in
-	  source code format, or as a binary.</para>
+	<para>¥ý¤U¸ü¸Ó³nÅéÀ£ÁYÀÉ(tarball)¡A¦³¥i¯à¬O­ì©l½X©Î¬O binary °õ¦æÀÉ¡C</para>
       </step>
 
       <step>
-	<para>Unpack the software from its distribution format
-	  (typically a tarball compressed with &man.compress.1;,
-	  &man.gzip.1;, or &man.bzip2.1;).</para>
+	<para>¸Ñ¶}¸ÓÀ£ÁYÀÉ¡C(³q±`¬O¥H &man.compress.1; , &man.gzip.1; ©Î &man.bzip2.1; À£ÁYªº)</para>
       </step>
 
       <step>
-	<para>Locate the documentation (perhaps an
-	  <filename>INSTALL</filename> or <filename>README</filename>
-	  file, or some files in a <filename>doc/</filename>
-	  subdirectory) and read up on how to install the
-	  software.</para>
+	<para>¾\Ū¬ÛÃö¤å¥óÀÉ¡A¥H¤F¸Ñ¦p¦ó¦w¸Ë¡C(³q±`ÀɦW¬O <filename>INSTALL</filename> ©Î
+	 <filename>README</filename>¡A ©Î¦b <filename>doc/</filename> ¥Ø¿ý¤Uªº¤@¨Ç¤å¥ó)</para>
       </step>
 
       <step>
-	<para>If the software was distributed in source format,
-	  compile it.  This may involve editing a
-	  <filename>Makefile</filename>, or running a
-	  <command>configure</command> script, and other work.</para>
+	<para>¦pªG©Ò¤U¸üªº¬O­ì©l½X¡A¥i¯à­n¥ý­×§ï <filename>Makefile</filename> ©Î¬O°õ¦æ
+	 <command>./configure</command> ¤§Ãþªº script ¡A±µµÛ¦A½sĶ¸Ó³nÅé¡C</para>
       </step>
 
       <step>
-	<para>Test and install the software.</para>
+	<para>³Ì«á´ú¸Õ¦A´ú¸Õ»P¦w¸Ë¡C</para>
       </step>
     </procedure>
 
-    <para>And that is only if everything goes well.  If you are
-      installing a software package that was not deliberately ported
-      to FreeBSD you may even have to go in and edit the code to make
-      it work properly.</para>
+    <para>¦pªG¤@¤Á¶¶§Qªº¸Ü¡A´N³o»ò²³æ¡C¦pªG¦b¦w¸Ë«D±Mªù³]­p(²¾´Ó)µ¹ FreeBSD ªº³nÅé®É¥X°ÝÃD¡A
+	¨º¥i¯à»Ý­n­×§ï¤@¤U¥¦ªºµ{¦¡½X¡A¤~¯à¥¿±`¨Ï¥Î¡C</para>
 
-    <para>Should you want to, you can continue to install software the
-      <quote>traditional</quote> way with FreeBSD.  However, FreeBSD
-      provides two technologies which can save you a lot of effort:
-      packages and ports.  At the time of writing, over &os.numports;
-      third party applications have been made available in this
-      way.</para>
+    <para>·íµM¡A§Ú­Ì¥i¥H¦b FreeBSD ¤W¨Ï¥Î¤W­zªº¶Ç²Î¤è¦¡¨Ó¦w¸Ë³nÅé¡A¦ý¬O¡A§Ú­ÌÁÙ¦³§ó²³æªº¿ï¾Ü¡C
+	FreeBSD ´£¨Ñ¤F¨âºØ¬Ù¨Æªº³nÅéºÞ²z¾÷¨î¡G packages ©M ports¡C´N¦b¼g³o½g¤å³¹ªº®É­Ô¡A
+	¤w¸g¦³¶W¹L &os.numports; ­Ó port ³nÅé¥i¥H¨Ï¥Î¡C</para>
 
     <para>For any given application, the FreeBSD package for that
       application is a single file which you must download.  The
       package contains pre-compiled copies of all the commands for the
       application, as well as any configuration files or
       documentation.  A downloaded package file can be manipulated
       with FreeBSD package management commands, such as
       &man.pkg.add.1;, &man.pkg.delete.1;, &man.pkg.info.1;, and so
       on.  Installing a new application can be carried out with a
       single command.</para>
 
     <para>A FreeBSD port for an application is a collection of files
       designed to automate the process of compiling an application
       from source code.</para>
 
     <para>Remember that there are a number of steps you would normally
       carry out if you compiled a program yourself (downloading,
       unpacking, patching, compiling, installing).  The files that
       make up a port contain all the necessary information to allow
       the system to do this for you.  You run a handful of simple
       commands and the source code for the application is
       automatically downloaded, extracted, patched, compiled, and
       installed for you.</para>
 
     <para>In fact, the ports system can also be used to generate packages
       which can later be manipulated with <command>pkg_add</command>
       and the other package management commands that will be introduced
       shortly.</para>
 
     <para>Both packages and ports understand
       <emphasis>dependencies</emphasis>.  Suppose you want to install
       an application that depends on a specific library being
       installed.  Both the application and the library have been made
       available as FreeBSD ports and packages.  If you use the
       <command>pkg_add</command> command or the ports system to add
       the application, both will notice that the library has not been
       installed, and automatically install the library first.</para>
 
     <para>Given that the two technologies are quite similar, you might
       be wondering why FreeBSD bothers with both.  Packages and ports
       both have their own strengths, and which one you use will depend
       on your own preference.</para>
 
     <itemizedlist>
-      <title>Package Benefits</title>
+      <title>Package ¦n³B¦b©ó¡G</title>
       
       <listitem>
 	<para>A compressed package tarball is typically smaller than
 	  the compressed tarball containing the source code for the
 	  application.</para>
       </listitem>
 
       <listitem>
 	<para>Packages do not require any additional compilation.  For
 	  large applications, such as
 	  <application>Mozilla</application>,
 	  <application>KDE</application>, or
 	  <application>GNOME</application> this can be important,
 	  particularly if you are on a slow system.</para>
       </listitem>
 
       <listitem>
 	<para>Packages do not require any understanding of the process
 	  involved in compiling software on FreeBSD.</para>
       </listitem>
     </itemizedlist>
 
     <itemizedlist>
-      <title>Ports Benefits</title>
+      <title>Ports ¦n³B¦b©ó¡G</title>
       
       <listitem>
 	<para>Packages are normally compiled with conservative options,
 	  because they have to run on the maximum number of systems.  By
 	  installing from the port, you can tweak the compilation options to
 	  (for example) generate code that is specific to a Pentium
 	  IV or Athlon processor.</para>
       </listitem>
 
       <listitem>
 	<para>Some applications have compile time options relating to
 	  what they can and cannot do.  For example,
 	  <application>Apache</application> can be configured with a
 	  wide variety of different built-in options.  By building
 	  from the port you do not have to accept the default options,
 	  and can set them yourself.</para>
 
 	<para>In some cases, multiple packages will exist for the same
 	  application to specify certain settings.  For example,
 	  <application>Ghostscript</application> is available as a
 	  <filename>ghostscript</filename> package and a
 	  <filename>ghostscript-nox11</filename> package, depending on
 	  whether or not you have installed an X11 server.  This sort
 	  of rough tweaking is possible with packages, but rapidly
 	  becomes impossible if an application has more than one or
 	  two different compile time options.</para>
       </listitem>
 
       <listitem>
 	<para>The licensing conditions of some software distributions forbid
 	  binary distribution.  They must be distributed as source
 	  code.</para>
       </listitem>
 
       <listitem>
 	<para>Some people do not trust binary distributions.  At least
 	  with source code, you can (in theory) read through it and
 	  look for potential problems yourself.</para>
       </listitem>
 
       <listitem>
 	<para>If you have local patches, you will need the source in order to
 	  apply them.</para>
       </listitem>
 
       <listitem>
 	<para>Some people like having code around, so they can read it
 	  if they get bored, hack it, borrow from it (license
 	  permitting, of course), and so on.</para>
       </listitem>
     </itemizedlist>
 
     <para>To keep track of updated ports, subscribe to the
       &a.ports; and the &a.ports-bugs;.</para>
 
     <warning>
       <para>Before installing any application, you should check <ulink
 	url="http://vuxml.freebsd.org/"></ulink> for security issues
 	related to your application.</para>
 
       <para>You can also install <filename
 	role="package">security/portaudit</filename> which will
 	automatically check all installed applications for known
 	vulnerabilities; a check will be also performed before any port
 	build.  Meanwhile, you can use the command <command>portaudit
 	-F -a</command> after you have installed some
 	packages.</para>
     </warning>
 
     <para>The remainder of this chapter will explain how to use
       packages and ports to install and manage third party software on
       FreeBSD.</para>
   </sect1>
 
   <sect1 id="ports-finding-applications">
-    <title>Finding Your Application</title>
+    <title>´M§ä·Q¸Ëªº³nÅé</title>
 
     <para>Before you can install any applications you need to know what you
       want, and what the application is called.</para>
 
     <para>FreeBSD's list of available applications is growing all the
       time.  Fortunately, there are a number of ways to find what you
       want:</para>
 
     <itemizedlist>
       <listitem>
 	<para>The FreeBSD web site maintains an up-to-date searchable
 	  list of all the available applications, at <ulink
 	  url="&url.base;/ports/index.html">http://www.FreeBSD.org/ports/</ulink>.
 	  The ports are divided into categories, and you may either
 	  search for an application by name (if you know it), or see
 	  all the applications available in a category.</para>
       </listitem>
 
       <indexterm><primary>FreshPorts</primary></indexterm>
 
       <listitem>
 	<para>Dan Langille maintains FreshPorts, at <ulink
 	  url="http://www.FreshPorts.org/"></ulink>.  FreshPorts
 	  tracks changes to the applications in the ports tree as they
 	  happen, allows you to <quote>watch</quote> one or more
 	  ports, and can send you email when they are updated.</para>
       </listitem>
 
       <indexterm><primary>FreshMeat</primary></indexterm>
 
       <listitem>
 	<para>If you do not know the name of the application you want,
 	  try using a site like FreshMeat (<ulink
 	  url="http://www.freshmeat.net/"></ulink>) to find an
 	  application, then check back at the FreeBSD site to see if
 	  the application has been ported yet.</para>
       </listitem>
 
       <listitem>
 	<para>If you know the exact name of the port, but just need to
         find out which category it is in, you can use the
         &man.whereis.1; command.
 	Simply type <command>whereis
         <replaceable>file</replaceable></command>, where
         <replaceable>file</replaceable> is the program you want to
         install.  If it is found on your system, you will be told
         where it is, as follows:</para>
 
       <screen>&prompt.root; <userinput>whereis lsof</userinput>
 lsof: /usr/ports/sysutils/lsof</screen>
 
       <para>This tells us that <command>lsof</command> (a system
 	utility) can be found in the
 	<filename>/usr/ports/sysutils/lsof</filename>
 	directory.</para></listitem>
 
       <listitem>
 	<para>Yet another way to find a particular port is by using the
         Ports Collection's built-in search mechanism.  To use the
         search feature, you will need to be in the
         <filename>/usr/ports</filename> directory.  Once in that
         directory, run <command>make search
         name=<replaceable>program-name</replaceable></command> where
         <replaceable>program-name</replaceable> is the name of the
         program you want to find.  For example, if you were looking
         for <command>lsof</command>:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/ports</userinput>
 &prompt.root; <userinput>make search name=lsof</userinput>
 Port:   lsof-4.56.4
 Path:   /usr/ports/sysutils/lsof
 Info:   Lists information about open files (similar to fstat(1))
 Maint:  obrien@FreeBSD.org
 Index:  sysutils
 B-deps: 
 R-deps: </screen>
 
       <para>The part of the output you want to pay particular
         attention to is the <quote>Path:</quote> line, since that
         tells you where to find the port.  The other information
         provided is not needed in order to install the port, so it
         will not be covered here.</para>
 
       <para>For more in-depth searching you can also use <command>make
        search key=<replaceable>string</replaceable></command> where
        <replaceable>string</replaceable> is some text to search for.
        This searches port names, comments, descriptions and
        dependencies and can be used to find ports which relate to a
        particular subject if you do not know the name of the program
        you are looking for.</para>
 
       <para>In both of these cases, the search string is case-insensitive.
        Searching for <quote>LSOF</quote> will yield the same results as 
        searching for <quote>lsof</quote>.</para>
       </listitem>
 
     </itemizedlist>
   </sect1>
 
   <sect1 id="packages-using">
     <sect1info>    
       <authorgroup>
         <author>
           <firstname>Chern</firstname>
 	  <surname>Lee</surname>
 	  <contrib>Contributed by </contrib>
         </author>
       </authorgroup>
     <!-- 30 Mar 2001 -->
     </sect1info>
 
-    <title>Using the Packages System</title>
+    <title>¨Ï¥Î Packages ºÞ²z¾÷¨î</title>
 
     <sect2>
-      <title>Installing a Package</title>
+      <title>Package ªº¦w¸Ë¤è¦¡</title>
       <indexterm>
         <primary>packages</primary>
         <secondary>installing</secondary>
       </indexterm>
     
       <indexterm>
         <primary><command>pkg_add</command></primary>
       </indexterm>
       <para>You can use the &man.pkg.add.1; utility to install a
 	FreeBSD software package from a local file or from a server on
 	the network.</para>
 
       <example>
-        <title>Downloading a Package Manually and Installing It Locally</title>
+        <title>¤â°Ê¤U¸ü¡B¦w¸Ë Package (ĶªÌchinsan: ¦]¤ñ¸û¤£«K¦Ó¤£«Øij³o»ò°µ)</title>
 
         <screen>&prompt.root; <userinput>ftp -a <replaceable>ftp2.FreeBSD.org</replaceable></userinput>
 Connected to ftp2.FreeBSD.org.
 220 ftp2.FreeBSD.org FTP server (Version 6.00LS) ready.
 331 Guest login ok, send your email address as password.
 230-
 230-     This machine is in Vienna, VA, USA, hosted by Verio.
 230-         Questions? E-mail freebsd@vienna.verio.net.
 230-
 230-
 230 Guest login ok, access restrictions apply.
 Remote system type is UNIX.
 Using binary mode to transfer files.
 <prompt>ftp></prompt> <userinput>cd /pub/FreeBSD/ports/packages/sysutils/</userinput>
 250 CWD command successful.
 <prompt>ftp></prompt> <userinput>get lsof-4.56.4.tgz</userinput>
 local: lsof-4.56.4.tgz remote: lsof-4.56.4.tgz
 200 PORT command successful.
 150 Opening BINARY mode data connection for 'lsof-4.56.4.tgz' (92375 bytes).
 100% |**************************************************| 92375       00:00 ETA
 226 Transfer complete.
 92375 bytes received in 5.60 seconds (16.11 KB/s)
 <prompt>ftp></prompt> <userinput>exit</userinput>
 &prompt.root; <userinput>pkg_add <replaceable>lsof-4.56.4.tgz</replaceable></userinput></screen>
       </example>
 
       <para>If you do not have a source of local packages (such as a
         FreeBSD CD-ROM set) then it will probably be easier to use the
         <option>-r</option> option to &man.pkg.add.1;.  This will
         cause the utility to automatically determine the correct
         object format and release and then fetch and install the
         package from an FTP site.
       </para>
 
       <indexterm>
         <primary><command>pkg_add</command></primary></indexterm>
       <screen>&prompt.root; <userinput>pkg_add -r <replaceable>lsof</replaceable></userinput></screen>
 
       <para>The example above would download the correct package and
 	add it without any further user intervention.
 	If you want to specify an alternative &os; Packages Mirror,
 	instead of the main distribution site, you have to set
 	<envar>PACKAGESITE</envar> accordingly, to
 	override the default settings.  &man.pkg.add.1;
 	uses &man.fetch.3; to download the files, which honors various
 	environment variables, including
 	<envar>FTP_PASSIVE_MODE</envar>, <envar>FTP_PROXY</envar>, and
 	<envar>FTP_PASSWORD</envar>.  You may need to set one or more
 	of these if you are behind a firewall, or need to use an
 	FTP/HTTP proxy.  See &man.fetch.3; for the complete list.
 	Note that in the example above
 	<literal>lsof</literal> is used instead of
 	<literal>lsof-4.56.4</literal>.  When the remote fetching
 	feature is used, the version number of the package must be
 	removed.  &man.pkg.add.1; will automatically fetch the latest
 	version of the application.</para>
 
       <note>
 	<para>&man.pkg.add.1; will download the latest version of
 	  your application if you are using &os.current; or
 	  &os.stable;.  If you run a -RELEASE version, it will grab
 	  the version of the package that was built with your
 	  release.  It is possible to change this behavior by
 	  overriding the <envar>PACKAGESITE</envar> environment
 	  variable.  For example, if you run a &os;&nbsp;5.4-RELEASE
 	  system, by default &man.pkg.add.1; will try to fetch
 	  packages from
 	  <literal>ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5.4-release/Latest/</literal>.
 	  If you want to force &man.pkg.add.1; to download
 	  &os;&nbsp;5-STABLE packages, set <envar>PACKAGESITE</envar>
 	  to
 	  <literal>ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5-stable/Latest/</literal>.
 	</para>
       </note>
 
       <para>Package files are distributed in <filename>.tgz</filename>
           and <filename>.tbz</filename> formats.  You can find them at <ulink
           url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/"></ulink>,
           or on the FreeBSD CD-ROM distribution.  Every CD on the
           FreeBSD 4-CD set (and the PowerPak, etc.) contains packages
           in the <filename>/packages</filename> directory.  The layout
           of the packages is similar to that of the
           <filename>/usr/ports</filename> tree.  Each category has its
           own directory, and every package can be found within the
           <filename>All</filename> directory.
       </para>
 
       <para>The directory structure of the package system matches the
         ports layout; they work with each other to form the entire
         package/port system.
       </para>
 
     </sect2>
 
     <sect2>
-      <title>Managing Packages</title>
+      <title>ºÞ²z Packages</title>
 
       <indexterm>
         <primary>packages</primary>
         <secondary>managing</secondary>
       </indexterm>
       <para>&man.pkg.info.1; is a utility that lists and describes 
         the various packages installed.
       </para>
 
       <indexterm>
         <primary><command>pkg_info</command></primary>
       </indexterm>
       <screen>&prompt.root; <userinput>pkg_info</userinput>
 cvsup-16.1          A general network file distribution system optimized for CV
 docbook-1.2         Meta-port for the different versions of the DocBook DTD
 ...</screen>
       <para>&man.pkg.version.1; is a utility that summarizes the
         versions of all installed packages.  It compares the package 
         version to the current version found in the ports tree.
       </para> 
       <indexterm>
         <primary><command>pkg_version</command></primary>
       </indexterm>
         <screen>&prompt.root; <userinput>pkg_version</userinput>
 cvsup                       =
 docbook                     =
 ...</screen>
 
       <para>The symbols in the second column indicate the relative age
         of the installed version and the version available in the
         local ports tree.</para>
 
       <informaltable frame="none" pgwide="1">
         <tgroup cols="2">
 	  <thead>
             <row>
-              <entry>Symbol</entry>
-              <entry>Meaning</entry>
+              <entry>²Å¸¹</entry>
+              <entry>¥Nªí·N¸q</entry>
             </row>
           </thead>
 
  	  <tbody>
   	    <row>
 	    <entry>=</entry> <entry>The version of the
 	    installed package matches the one found in the
 	    local ports tree.</entry>
   	    </row>
  
         <row><entry>&lt;</entry>
 	<entry>The installed version is older than the one available
 	in the ports tree.</entry>
 	</row>
 
         <row><entry>&gt;</entry><entry>The installed version is newer
           than the one found in the local ports tree. (The local ports
           tree is probably out of date.)</entry></row>
 
         <row><entry>?</entry><entry>The installed package cannot be
 	  found in the ports index.  (This can happen, for instance, if an
 	  installed port is removed from the Ports Collection or
 	  renamed.)</entry></row>
 
         <row><entry>*</entry><entry>There are multiple versions of the
         package.</entry></row>
 
 	</tbody>
 	</tgroup>
     </informaltable>
     </sect2>
 
     <sect2>
-      <title>Deleting a Package</title>
+      <title>²¾°£¤w¦w¸Ëªº Package</title>
       <indexterm>
         <primary><command>pkg_delete</command></primary>
       </indexterm>
       <indexterm>
         <primary>packages</primary>
         <secondary>deleting</secondary>
       </indexterm>
       <para>To remove a previously installed software package, use the
 	&man.pkg.delete.1; utility.
       </para>
 
       <screen>&prompt.root; <userinput>pkg_delete <replaceable>xchat-1.7.1</replaceable></userinput></screen>
     </sect2>
 
     <sect2>
-      <title>Miscellaneous</title>
+      <title>¨ä¥L²Ó¸`³¡¥÷</title>
       <para>All package information is stored within the 
         <filename>/var/db/pkg</filename> directory.  The installed
 	file list and descriptions of each package can be found within 
         files in this directory.
       </para>
     </sect2>
   </sect1>
   
   <sect1 id="ports-using">
-    <title>Using the Ports Collection</title>
+    <title>¨Ï¥Î Ports ºÞ²z¾÷¨î</title>
 
     <para>The following sections provide basic instructions on using the
       Ports Collection to install or remove programs from your
       system.  The detailed description of available <command>make</command>
       targets and environment variables is available in &man.ports.7;.</para>
 
     <sect2 id="ports-tree">
-      <title>Obtaining the Ports Collection</title>
+      <title>°O±o¦w¸Ë Ports Collection</title>
 
       <para>Before you can install ports, you must first obtain the
 	Ports Collection&mdash;which is essentially a set of
 	<filename>Makefiles</filename>, patches, and description files
 	placed in <filename>/usr/ports</filename>.
       </para>
 
       <para>When installing your FreeBSD system,
 	<application>sysinstall</application> asked if you would like
 	to install the Ports Collection.  If you chose no, you can
 	follow these instructions to obtain the ports
 	collection:</para>
 
       <procedure>
-	<title>CVSup Method</title>
+	<title>CVSup ¤è¦¡</title>
 
 	<para>This is a quick method for getting and keeping your copy of the
 	  Ports Collection up to date using <application>CVSup</application>.
 	  If you want to learn more about <application>CVSup</application>, see
 	  <link linkend="cvsup">Using CVSup</link>.</para>
 
 	<step>
 	  <para>Install the <filename
 	    role="package">net/cvsup-without-gui</filename> package:</para>
 
 	  <screen>&prompt.root; <userinput>pkg_add -r cvsup-without-gui</userinput></screen>
 
 	  <para>See <link
 	      linkend="cvsup-install">CVSup Installation</link> (<xref
 	      linkend="cvsup-install">) for more details.</para>
 	</step>
 
 	<step>
 	  <para>Run <command>cvsup</command>:</para>
 
 	  <screen>&prompt.root; <userinput>cvsup -L 2 -h <replaceable>cvsup.FreeBSD.org</replaceable> /usr/share/examples/cvsup/ports-supfile</userinput></screen>
 
 	  <para>Change
 	    <replaceable>cvsup.FreeBSD.org</replaceable> to a
 	    <application>CVSup</application> server near you.  See
 	    <link linkend="cvsup-mirrors">CVSup Mirrors</link> (<xref
 	    linkend="cvsup-mirrors">) for a complete listing of mirror
 	    sites.</para>
 
 	  <note>
 	    <para>One may want to use his own
 	      <filename>ports-supfile</filename>, for example to avoid
 	      the need of passing the <application>CVSup</application>
 	      server on the command line.</para>
 
 	    <procedure>
 	      <step>
 		<para>In this case, as <username>root</username>, copy
 		  <filename>/usr/share/examples/cvsup/ports-supfile</filename>
 		  to a new location, such as
 		  <filename>/root</filename> or your home
 		  directory.</para>
 	      </step>
 
 	      <step>
 		<para>Edit <filename>ports-supfile</filename>.</para>
 	      </step>
 
 	      <step>
 		<para>Change
 		  <replaceable>CHANGE_THIS.FreeBSD.org</replaceable>
 		  to a <application>CVSup</application> server near
 		  you.  See <link linkend="cvsup-mirrors">CVSup
 		  Mirrors</link> (<xref linkend="cvsup-mirrors">) for
 		  a complete listing of mirror sites.</para>
 	      </step>
 
 	      <step>
 		<para>And now to run <command>cvsup</command>, use the
 		  following:</para>
 
 		<screen>&prompt.root; <userinput>cvsup -L 2 <replaceable>/root/ports-supfile</replaceable></userinput></screen>
 	      </step>
 	    </procedure>
 	  </note>
 	</step>
 
 	<step>
 	  <para>Running the &man.cvsup.1; command later will download and apply all
 	    the recent changes to your Ports Collection, except
 	    actually rebuilding the ports for your own system.</para>
 	</step>
       </procedure>
 
       <procedure>
-	<title>Portsnap Method</title>
+	<title>Portsnap ¤è¦¡</title>
 
 	<para>&man.portsnap.8; is an alternative system for distributing the
 	  Ports Collection.  It was first included in &os;&nbsp;6.0.  On older
 	  systems, you can install it from <filename
 	  role="package">sysutils/portsnap</filename> port:</para>
 
 	<screen>&prompt.root; <userinput>pkg_add -r portsnap</userinput></screen>
 
 	<para>Please refer to <link linkend="portsnap">Using Portsnap</link>
 	  for a detailed description of all <application>Portsnap</application>
 	  features.</para>
 
 	<step>
 	  <para>Create an empty directory <filename
 	    role="directory">/usr/ports</filename> if it does not exists.</para>
 
 	  <screen>&prompt.root; <userinput>mkdir /usr/ports</userinput></screen>
 	</step>
 
 	<step>
 	  <para>Download a compressed snapshot of the Ports Collection into
 	    <filename role="directory">/var/db/portsnap</filename>.  You can
 	    disconnect from the Internet after this step, if you wish.</para>
 
 	  <screen>&prompt.root; <userinput>portsnap fetch</userinput></screen>
 	</step>
 
 	<step>
 	  <para>If you are running <application>Portsnap</application> for the
 	    first time, extract the snapshot into <filename
 	    role="directory">/usr/ports</filename>:
 	  </para>
 
 	  <screen>&prompt.root; <userinput>portsnap extract</userinput></screen>
 
 	  <para>If you already have a populated <filename
 	    role="directory">/usr/ports</filename> and you are just updating,
 	    run the following command instead:</para>
 
 	  <screen>&prompt.root; <userinput>portsnap update</userinput></screen>
 	</step>
 
       </procedure>
 
       <procedure>
-	<title>Sysinstall Method</title>
+	<title>Sysinstall ¤è¦¡</title>
 
 	<para>This method involves using <application>sysinstall</application>
 	  to install the Ports Collection from the installation media.  Note
 	  that the old copy of Ports Collection from the date of the release
 	  will be installed.  If you have Internet access, you should always
 	  use one of the methods mentioned above.</para>
 
 	<step>
 	  <para>As <username>root</username>, run
 	    <command>sysinstall</command>
 	    (<command>/stand/sysinstall</command> in &os;
 	    versions older than 5.2) as shown below:</para>
 
 	  <screen>&prompt.root; <userinput>sysinstall</userinput></screen>
 	</step>
 
 	<step>
 	  <para>Scroll down and select <guimenuitem>Configure</guimenuitem>,
 	    press <keycap>Enter</keycap>.</para>
 	</step>
 
 	<step>
 	  <para>Scroll down and select
 	    <guimenuitem>Distributions</guimenuitem>, press
 	    <keycap>Enter</keycap>.</para>
 	</step>
 
 	<step>
 	  <para>Scroll down to <guimenuitem>ports</guimenuitem>, press
 	    <keycap>Space</keycap>.</para>
 	</step>
 
 	<step>
 	  <para>Scroll up to <guimenuitem>Exit</guimenuitem>, press
 	    <keycap>Enter</keycap>.</para>
 	</step>
 
 	<step>
 	  <para>Select your desired installation media, such as CDROM,
 	    FTP, and so on.</para>
 	</step>
 
 	<step>
 	  <para>Scroll up to <guimenuitem>Exit</guimenuitem> and press
 	    <keycap>Enter</keycap>.</para>
 	</step>
 
 	<step>
 	  <para>Press <keycap>X</keycap> to exit
 	    <application>sysinstall</application>.</para>
 	</step>
       </procedure>
     </sect2>
 
     <sect2 id="ports-skeleton">
-      <title>Installing Ports</title>
+      <title>Ports ªº¦w¸Ë¤è¦¡</title>
 
       <indexterm>
         <primary>ports</primary>
         <secondary>installing</secondary>
       </indexterm>
       <para>The first thing that should be explained when it comes to
         the Ports Collection is what is actually meant by a
         <quote>skeleton</quote>.  In a nutshell, a port skeleton is a
         minimal set of files that tell your FreeBSD system how to
         cleanly compile and install a program.  Each port skeleton
         includes:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>A <filename>Makefile</filename>.  The
 	    <filename>Makefile</filename> contains various statements
 	    that specify how the application should be compiled and
 	    where it should be installed on your system.</para>
 	</listitem>
 
 	<listitem>
 	  <para>A <filename>distinfo</filename> file.  This file
 	    contains information about the files that must be
 	    downloaded to build the port and their checksums, to
 	    verify that files have not been corrupted during the
 	    download using &man.md5.1;.</para>
 	</listitem>
 	
 	<listitem>
 	  <para>A <filename>files</filename> directory.  This
 	    directory contains patches to make the program compile and
 	    install on your FreeBSD system.  Patches are basically
 	    small files that specify changes to particular files.
 	    They are in plain text format, and basically say
 	    <quote>Remove line 10</quote> or <quote>Change line 26 to
 	    this ...</quote>.  Patches are also known as
 	    <quote>diffs</quote> because they are generated by the
 	    &man.diff.1; program.</para>
 
 	  <para>This directory may also contain other files used to build
 	    the port.</para>
 	</listitem>
 
 	<listitem>
 	  <para>A <filename>pkg-descr</filename> file.  This is a more
 	    detailed, often multiple-line, description of the program.</para>
 	</listitem>
 	
 	<listitem>
 	  <para>A <filename>pkg-plist</filename> file.  This is a list
 	    of all the files that will be installed by the port.  It
 	    also tells the ports system what files to remove upon
 	    deinstallation.</para>
 	</listitem>
       </itemizedlist>
 
       <para>Some ports have other files, such as
         <filename>pkg-message</filename>.  The ports system uses these
         files to handle special situations.  If you want more details
         on these files, and on ports in general, check out the <ulink
         url="&url.books.porters-handbook;/index.html">FreeBSD Porter's
         Handbook</ulink>.</para>
 
       <para>The port includes instructions on how to build source
         code, but does not include the actual source code.  You can
         get the source code from a CD-ROM or from the Internet.
         Source code is distributed in whatever manner the software
         author desires.  Frequently this is a tarred and gzipped file,
         but it might be compressed with some other tool or even
         uncompressed.  The program source code, whatever form it comes
         in, is called a <quote>distfile</quote>.  The two methods for
         installing a &os; port are described below.</para>
 
       <note>
         <para>You must be logged in as <username>root</username> to
           install ports.</para>
       </note>
 
       <warning>
 	<para>Before installing any port, you should be sure to have
 	  an up-to-date Ports Collection and you should check <ulink
 	  url="http://vuxml.freebsd.org/"></ulink> for security issues
 	  related to your port.</para>
 
 	<para>A security vulnerabilities check can be automatically
 	  done by <application>portaudit</application> before any new
 	  application installation.  This tool can be found in the
 	  Ports Collection (<filename
 	  role="package">security/portaudit</filename>).  Consider
 	  running <command>portaudit -F</command> before installing a
 	  new port, to fetch the current vulnerabilities database.  A
 	  security audit and an update of the database will be
 	  performed during the daily security system check.  For more
 	  information read the &man.portaudit.1; and &man.periodic.8;
 	  manual pages.</para>
       </warning>
 
       <para>The Ports Collection makes an assumption that you have a working
 	Internet connection.  If you do not, you will need to put a copy of the
 	distfile into <filename>/usr/ports/distfiles</filename>
 	manually.</para>
 
 	<para>To begin, change to the directory for the port you want to
 	  install:</para>
 
         <screen>&prompt.root; <userinput>cd /usr/ports/sysutils/lsof</userinput></screen>
 
         <para>Once inside the <filename>lsof</filename> directory, you
 	  will see the port skeleton.  The next step is to compile, or
 	  <quote>build</quote>, the port.  This is done by simply
 	  typing <command>make</command> at the prompt.  Once you have
 	  done so, you should see something like this:</para>
 
         <screen>&prompt.root; <userinput>make</userinput>
 &gt;&gt; lsof_4.57D.freebsd.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
 &gt;&gt; Attempting to fetch from ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/.
 ===&gt;  Extracting for lsof-4.57
 ...
 [extraction output snipped]
 ...
 &gt;&gt; Checksum OK for lsof_4.57D.freebsd.tar.gz.
 ===&gt;  Patching for lsof-4.57
 ===&gt;  Applying FreeBSD patches for lsof-4.57
 ===&gt;  Configuring for lsof-4.57
 ...
 [configure output snipped]
 ...
 ===&gt;  Building for lsof-4.57
 ...
 [compilation output snipped]
 ...
 &prompt.root;</screen>
 
         <para>Notice that once the compile is complete you are
 	  returned to your prompt.  The next step is to install the
 	  port.  In order to install it, you simply need to tack one word
 	  onto the <command>make</command> command, and that word is
 	  <command>install</command>:</para>
 
         <screen>&prompt.root; <userinput>make install</userinput>
 ===&gt;  Installing for lsof-4.57
 ...
 [installation output snipped]
 ...
 ===&gt;   Generating temporary packing list
 ===&gt;   Compressing manual pages for lsof-4.57
 ===&gt;   Registering installation for lsof-4.57
 ===&gt;  SECURITY NOTE: 
       This port has installed the following binaries which execute with
       increased privileges.
 &prompt.root;</screen>
 
         <para>Once you are returned to your prompt, you should be able to
           run the application you just installed.  Since 
 	  <command>lsof</command> is a
 	  program that runs with increased privileges, a security
 	  warning is shown.  During the building and installation of
 	  ports, you should take heed of any other warnings that
 	  may appear.</para>
 
 	<para>It is a good idea to delete the working subdirectory,
 	  which contains all the temporary files used during compilation.
 	  Not only it consumes a valuable disk space, it would also cause
 	  problems later when upgrading to the newer version of the port.</para>
 
 	<screen>&prompt.root; <userinput>make clean</userinput>
 ===&gt;  Cleaning for lsof-4.57
 &prompt.root;</screen>
 
         <note>
           <para>You can save an extra step by just running <command>make
 	    install clean</command> instead of <command>make</command>,
 	    <command>make install</command> and <command>make clean</command>
 	    as three separate steps.</para>
 	</note>
 
 	<note>
 	  <para>Some shells keep a cache of the commands that are
 	    available in the directories listed in the
 	    <envar>PATH</envar> environment variable, to speed up
 	    lookup operations for the executable file of these
 	    commands.  If you are using one of these shells, you might
 	    have to use the <command>rehash</command> command after
 	    installing a port, before the newly installed commands can
 	    be used.  This command will work for shells like
 	    <command>tcsh</command>.  Use the <command>hash -r</command>
 	    command for shells like <command>sh</command>.  Look at the
 	    documentation for your shell for more information.</para>
 	</note>
 
 	<para>Some third party DVD-ROM products such as the FreeBSD Toolkit
 	  from the <ulink url="http://www.freebsdmall.com/">FreeBSD
 	  Mall</ulink> contain distfiles.  They can be used with the Ports
 	  Collection.  Mount the DVD-ROM on <filename>/cdrom</filename>.  If
 	  you use a different mount point, set <makevar>CD_MOUNTPTS</makevar>
 	  make variable.  The needed distfiles will be automatically used
 	  if they are present on the disk.</para>
 
 	<note>
 	  <para>Please be aware that the licenses of a few ports do
 	    not allow for inclusion on the CD-ROM.  This could be
 	    because a registration form needs to be filled out before
 	    downloading or redistribution is not allowed, or for
 	    another reason.  If you wish to install a port not
 	    included on the CD-ROM, you will need to be online in
 	    order to do so.</para>
 	</note>
 
 	<para>The ports system uses &man.fetch.1; to download the
 	  files, which honors various environment variables, including
 	  <envar>FTP_PASSIVE_MODE</envar>, <envar>FTP_PROXY</envar>,
 	  and <envar>FTP_PASSWORD</envar>.  You may need to set one or
 	  more of these if you are behind a firewall, or need to use
 	  an FTP/HTTP proxy.  See &man.fetch.3; for the complete
 	  list.</para>
 
 	<para>For users which cannot be connected all the time, the
 	  <command>make <maketarget>fetch</maketarget></command> option is
 	  provided.  Just run this command at the top level directory
 	  (<filename>/usr/ports</filename>) and the required files
 	  will be downloaded for you.  This command will also work in
 	  the lower level categories, for example:
 	  <filename>/usr/ports/net</filename>.
 	  Note that if a port depends on libraries or other ports this will
 	  <emphasis>not</emphasis> fetch the distfiles of those ports too.
 	  Replace <maketarget>fetch</maketarget> with
 	  <maketarget>fetch-recursive</maketarget>
 	  if you want to fetch all the dependencies of a port too.</para>
 
 	<note><para>You can build all the ports in a category or as a
 	  whole by running <command>make</command> in the top level
 	  directory, just like the aforementioned <command>make
 	  <makevar>fetch</makevar></command> method.  This is
 	  dangerous, however, as some ports cannot co-exist.  In other
 	  cases, some ports can install two different files with the
 	  same filename.</para></note>
 
 	<para>In some rare cases, users may need to acquire the
 	  tarballs from a site other than the
 	  <makevar>MASTER_SITES</makevar> (the location where files
 	  are downloaded from).  You can override the
 	  <makevar>MASTER_SITES</makevar> option with the following
 	  command:</para>
 
 	<screen>&prompt.root; <userinput>cd /usr/ports/<replaceable>directory</replaceable></userinput>
 &prompt.root; <userinput>make MASTER_SITE_OVERRIDE= \
 ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
 
 	<para>In this example we change the
 	  <makevar>MASTER_SITES</makevar> option to <hostid
 	  role="fqdn">ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/</hostid>.</para>
 
 	<note><para>Some ports allow (or even require) you to provide
 	  build options which can enable/disable parts of the
 	  application which are unneeded, certain security options,
 	  and other customizations.  A few which come to mind are
 	  <filename role="package">www/mozilla</filename>, <filename
 	  role="package">security/gpgme</filename>, and <filename
 	  role="package">mail/sylpheed-claws</filename>.  A message
 	  will be displayed when options such as these are
 	  available.</para></note>
 
       <sect3>
-        <title>Overriding the Default Ports Directories</title>
+        <title>§ó§ï(Override)¹w³]ªº Ports ¥Ø¿ý</title>
 
 	<para>Sometimes it is useful (or mandatory) to use a different
 	  distfiles and ports directory.  The
 	  <makevar>PORTSDIR</makevar> and <makevar>PREFIX</makevar>
 	  variables can override the default directories.  For
 	  example:</para>
 
 	<screen>&prompt.root; <userinput>make PORTSDIR=/usr/home/example/ports install</userinput></screen>
 
 	<para>will compile the port in
 	    <filename>/usr/home/example/ports</filename> and install
 	    everything under <filename>/usr/local</filename>.</para>
 
 	<screen>&prompt.root; <userinput>make PREFIX=/usr/home/example/local install</userinput></screen>
 
 	<para>will compile it in <filename>/usr/ports</filename> and
 	  install it in
 	  <filename>/usr/home/example/local</filename>.</para>
 
 	<para>And of course,</para>
 
 	<screen>&prompt.root; <userinput>make PORTSDIR=../ports PREFIX=../local install</userinput></screen>
 
 	<para>will combine the two (it is too long to completely write
 	  on this page, but it should give you the general
 	  idea).</para>
 
 	<para>Alternatively, these variables can also be set as part
 	  of your environment.  Read the manual page for your shell
 	  for instructions on doing so.</para>
       </sect3>
 
       <sect3>
 	<title>Dealing with <command>imake</command></title>
 
 	<para>Some ports that use <command>imake</command> (a part of
 	  the X Window System) do not work well with
 	  <makevar>PREFIX</makevar>, and will insist on installing
 	  under <filename>/usr/X11R6</filename>.  Similarly, some Perl
 	  ports ignore <makevar>PREFIX</makevar> and install in the
 	  Perl tree.  Making these ports respect
 	  <makevar>PREFIX</makevar> is a difficult or impossible
 	  job.</para>
 
       </sect3>
     </sect2>
 
     <sect2 id="ports-removing">
-      <title>Removing Installed Ports</title>
+      <title>²¾°£¤w¦w¸Ëªº Ports</title>
 
       <indexterm>
         <primary>ports</primary>
         <secondary>removing</secondary>
       </indexterm>
       <para>Now that you know how to install ports, you are probably
         wondering how to remove them, just in case you install one and
 	later on decide that you installed the wrong port.  
         We will remove our previous example (which was 
 	<command>lsof</command> for
 	those of you not paying attention).  Ports are being removed exactly
 	the same as the packages (discussed in the <link
 	linkend="packages-using">Packages section</link>), using the
 	&man.pkg.delete.1; command:</para>
 
       <screen>&prompt.root; <userinput>pkg_delete lsof-4.57</userinput></screen>
 
     </sect2>
 
     <sect2 id="ports-upgrading">
-      <title>Upgrading Ports</title>
+      <title>¤É¯Å¤w¦w¸Ëªº Ports</title>
 
       <indexterm>
 	<primary>ports</primary>
 	<secondary>upgrading</secondary>
       </indexterm>
       <para>First, list outdated ports that have a newer version available in
 	the Ports Collection with the &man.pkg.version.1; command:</para>
 
       <screen>&prompt.root; <userinput>pkg_version -v</userinput></screen>
 
       <note>
 	<para>Once you updated your Ports Collection, before
 	  attempting a port upgrade, you should check the
 	  <filename>/usr/ports/UPDATING</filename> file.  This file
 	  describes various issues and additional steps users may
 	  encounter and need to perform when updating a port.</para>
       </note>
 
       <sect3 id="portupgrade">
-	<title>Upgrading Ports using Portupgrade</title>
+	<title>¥H Portupgrade ¨Ó¤É¯Å¤w¦w¸Ëªº Ports</title>
 
 	<indexterm>
 	  <primary>portupgrade</primary>
 	</indexterm>
 
       <para>The <application>portupgrade</application> utility is designed
 	to easily upgrade installed ports.  It is available from the <filename
 	role="package">sysutils/portupgrade</filename> port.  Install it like
 	any other port, using the <command>make <makevar>install
 	clean</makevar></command> command:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/ports/sysutils/portupgrade</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
 
       <para>Scan the list of installed ports with the <command>pkgdb
 	-F</command> command and fix all the inconsistencies it reports.  It is
 	a good idea to do this regularly, before every upgrade.</para>
 
       <para>When you run <command>portupgrade -a</command>,
 	<application>portupgrade</application> will begin to upgrade all the
 	outdated ports installed on your system.  Use the <option>-i</option>
 	flag if you want to be asked for confirmation of every individual
 	upgrade.</para>
 
       <screen>&prompt.root; <userinput>portupgrade -ai</userinput></screen>
 
       <para>If you want to upgrade only a
 	certain application, not all available ports, use <command>portupgrade
 	<replaceable>pkgname</replaceable></command>.  Include the
 	<option>-R</option> flag if <application>portupgrade</application>
 	should first upgrade all the ports required by the given
 	application.</para>
 
       <screen>&prompt.root; <userinput>portupgrade -R firefox</userinput></screen>
 
       <para>To use packages instead of ports for installation, provide
 	<option>-P</option> flag.  With this option
 	<application>portupgrade</application> searches
 	the local directories listed in <envar>PKG_PATH</envar>, or
 	fetches packages from remote site if it is not found locally.
 	If packages can not be found locally or fetched remotely,
 	<application>portupgrade</application> will use ports.
 	To avoid using ports, specify <option>-PP</option>.</para>
 
       <screen>&prompt.root; <userinput>portupgrade -PR gnome2</userinput></screen>
 
       <para>To just fetch distfiles (or packages, if
 	<option>-P</option> is specified) without building or
 	installing anything, use <option>-F</option>.
 	For further information see &man.portupgrade.1;.</para>
       </sect3>
 
       <sect3 id="portmanager">
-	<title>Upgrading Ports using Portmanager</title>
+	<title>¥H Portmanager ¨Ó¤É¯Å¤w¦w¸Ëªº Ports</title>
 
 	<indexterm>
 	  <primary>portmanager</primary>
 	</indexterm>
 
 	<para><application>Portmanager</application> is another utility for
 	  easy upgrading of installed ports.  It is available from the
 	  <filename role="package">sysutils/portmanager</filename> port:</para>
 
 	<screen>&prompt.root; <userinput>cd <filename role="directory">/usr/ports/sysutils/portmanager</filename></userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
 
 	<para>All the installed ports can be upgraded using this simple
 	  command:</para>
 
 	<screen>&prompt.root; <userinput>portmanager -u</userinput></screen>
 
 	<para>You can add the <option>-ui</option> flag to get asked for
 	  confirmation of every step <application>Portmanager</application>
 	  will perform.  <application>Portmanager</application> can also be
 	  used to install new ports on the system.  Unlike the usual
 	  <command>make install clean</command> command, it will upgrade all
 	  the dependencies prior to building and installing the
 	  selected port.</para>
 
 	<screen>&prompt.root; <userinput>portmanager <replaceable>x11/gnome2</replaceable></userinput></screen>
 
 	<para>If there are any problems regarding the dependencies for the
 	  selected port, you can use <application>Portmanager</application> to
 	  rebuild all of them in the correct order.  Once finished, the
 	  problematic port will be rebuilt too.</para>
 
 	<screen>&prompt.root; <userinput>portmanager <replaceable>graphics/gimp</replaceable> -f</userinput></screen>
 
 	<para>For more information see
 	  <application>Portmanager</application>'s manual page.</para>
       </sect3>
     </sect2>
 
     <sect2 id="ports-disk-space">
-      <title>Ports and Disk Space</title>
+      <title>Ports »PµwºÐªÅ¶¡</title>
 
       <indexterm>
 	<primary>ports</primary>
 	<secondary>disk-space</secondary>
       </indexterm>
       <para>Using the Ports Collection will use up disk
 	space over time.  After building and installing software from the
 	ports, you should always remember to clean up
 	the temporary <filename class="directory">work</filename> directories using the <command>make
 	<makevar>clean</makevar></command> command.  You can sweep the whole
 	Ports Collection with the following command:</para>
 
       <screen>&prompt.root; <userinput>portsclean -C</userinput></screen>
 
       <para>You will accumulate a lot of old source distribution files in the
 	<filename class="directory">distfiles</filename> directory over time.
 	You can remove them by hand, or you can use the following command to
 	delete all the distfiles that are no longer referenced by any
 	ports:</para>
 
       <screen>&prompt.root; <userinput>portsclean -D</userinput></screen>
 
       <note>
 	<para>The <command>portsclean</command> utility is part of the
 	  <application>portupgrade</application> suite.</para>
       </note>
 
       <para>Do not forget to remove the installed ports once you no longer need
 	them.  A nice tool to help automate this task is available from the
 	<filename role="package">sysutils/pkg_cutleaves</filename> port.</para>
     </sect2>
 
   </sect1>
 
   <sect1 id="ports-nextsteps">
-    <title>Post-installation Activities</title>
+    <title>¦w¸Ë¤§«á¡A¦³¤°»ò«áÄòª`·N¨Æ¶µ¶Ü¡H</title>
 
-    <para>After installing a new application you will normally want to
-      read any documentation it may have included, edit any
-      configuration files that are required, ensure that the
-      application starts at boot time (if it is a daemon), and so
-      on.</para>
+    <para>³q±`¡A¦w¸Ë§¹³nÅé«á¡A§Ú­Ì¥i¥H¾\Ū©Òªþªº¤@¨Ç¤å¥ó¡A©Î»Ý­n½s¿è³]©wÀÉ¡A
+	¨Ó½T«O³o­Ó³nÅé¯à¶¶§Q¹B§@¡A©Î¦b¾÷¾¹¶}¾÷ªº®É­Ô±Ò°Ê(¦pªG¬O daemon ªº¸Ü)µ¥µ¥¡C</para>
 
-    <para>The exact steps you need to take to configure each
-      application will obviously be different.  However, if you have
-      just installed a new application and are wondering <quote>What
-      now?</quote> these tips might help:</para>
+    <para>¤£¦Pªº³nÅé·|¦³¤£¦Pªº³]©w¨BÆJ¡C¤£ºÞ«ç¼Ë¡A¦pªG¸Ë¦n¤F³nÅé¡A
+	¦ý¬O¤£ª¾¹D¤U¤@¨B«ç»ò¿ìªº®É­Ô¡A ¥i¥H¸Õ¸Õ¬Ý³o¨Ç¤p§Þ¥©¡G</para>
 
     <itemizedlist>
       <listitem>
-	<para>Use &man.pkg.info.1; to find out which files were installed,
-	  and where.  For example, if you have just
-	  installed FooPackage version 1.0.0, then this command</para>
+	<para>µ½¥Î &man.pkg.info.1; ¡A³o«ü¥O¥i¥HÅã¥Ü¡G³z¹L®M¥óºÞ²z¨t²Î(Packages/Ports)¸Ë¤F­þ¨Ç³nÅé¡BÀɮ׸˦b­þÃä¡CÁ|¨Ò¨Ó»¡¡A­Y­è¸Ë¤F FooPackage (ª©¥» 1.0.0)¡A¨º»ò¤U­±³o«ü¥O¡G</para>
 
 	<screen>&prompt.root; <userinput>pkg_info -L foopackage-1.0.0 | less</userinput></screen>
 
-	<para>will show all the files installed by the package.  Pay
+	<para>´N·|Åã¥Ü³o³nÅé©Ò¦w¸ËªºÀɮײM³æ¡C Pay
 	  special attention to files in <filename>man/</filename>
 	  directories, which will be manual pages,
 	  <filename>etc/</filename> directories, which will be
 	  configuration files, and <filename>doc/</filename>, which
 	  will be more comprehensive documentation.</para>
 
 	<para>If you are not sure which version of the application was
 	  just installed, a command like this</para>
 
 	<screen>&prompt.root; <userinput>pkg_info | grep -i <replaceable>foopackage</replaceable></userinput></screen>
 
 	<para>will find all the installed packages that have
 	  <replaceable>foopackage</replaceable> in the package name.
 	  Replace <replaceable>foopackage</replaceable> in your
 	  command line as necessary.</para>
       </listitem>
 
       <listitem>
 	<para>Once you have identified where the application's manual
 	  pages have been installed, review them using &man.man.1;.
 	  Similarly, look over the sample configuration files, and any
 	  additional documentation that may have been provided.</para>
       </listitem>
 
       <listitem>
 	<para>If the application has a web site, check it for
 	  additional documentation, frequently asked questions, and so
 	  forth.  If you are not sure of the web site address it may
 	  be listed in the output from</para>
 
 	<screen>&prompt.root; <userinput>pkg_info <replaceable>foopackage-1.0.0</replaceable></userinput></screen>
 	
 	<para>A <literal>WWW:</literal> line, if present, should provide a URL
 	  for the application's web site.</para>
       </listitem>
 
       <listitem>
 	<para>Ports that should start at boot (such as Internet
 	  servers) will usually install a sample script in
 	  <filename>/usr/local/etc/rc.d</filename>.  You should
 	  review this script for correctness and edit or rename it if
 	  needed.  See <link
 	  linkend="configtuning-starting-services">Starting
 	  Services</link> for more information.</para>
       </listitem>
     </itemizedlist>
   </sect1>
 
   <sect1 id="ports-broken">
-    <title>Dealing with Broken Ports</title>
+    <title>¦p¦ó³B²zÄê±¼(Broken)ªº Ports¡H</title>
 
-      <para>If you come across a port that does not work for you,
-        there are a few things you can do, including:</para>
+      <para>¦pªGµo²{¬Y­Ó port µLªk¶¶§Q¦w¸Ë¡B¹B§@¡A ¦³´XºØ¤èªk¥i¥H¸Õ¸Õ¬Ý¡G</para>
 
       <orderedlist>
 	<listitem>
-	  <para>Find out if there is a fix pending for the port in
-	    the <ulink url="&url.base;/support.html#gnats">Problem Report
-	    database</ulink>.  If so, you may be able to use the
-	    proposed fix.</para>
+	  <para>±q <ulink url="&url.base;/support.html#gnats">Problem Report
+	    ¸ê®Æ®w</ulink> ¤¤«õÄ_¬Ý¬Ý¡A»¡¤£©w¤w¸g¦³¤H°e¥i¥Îªº patch ¤W¥hÅo¡A
+	    ¨º»ò©Î³\´N¥i¥H¶¶§Q¸Ñ¨M°ÝÃD­ù¡C</para>
 	</listitem>
 
 	<listitem>
-	  <para>Ask the maintainer of the port for help.  Type
-	    <command>make maintainer</command> or read the
-	    <filename>Makefile</filename> to find the maintainer's
-	    email address.  Remember to include the name and version
-	    of the port (send the <literal>&dollar;FreeBSD:</literal>
-	    line from the <filename>Makefile</filename>) and the
-	    output leading up to the error when you email the
-	    maintainer.</para>
+	  <para>¦V¸Ó port ªº maintainer ´M¨D¨ó§U¡G½Ð¥´
+	    <command>make maintainer</command> ©Î½¾\
+	    <filename>Makefile</filename> ¥H¬d¸ß maintainer ªº
+	    email address¡C°O±o±H«Hµ¹ maintainer ®É¡A­nªþµù¸Ó port ªº¦WºÙ¡Bª©¥»(©Î¬O§â <filename>Makefile</filename> ¤ºªº <literal>&dollar;FreeBSD:</literal> ¨º¤@¾ã¦æªþ¤W) ¥H¤Î¬ÛÃö¿ù»~°T®§¡C</para>
 
 	  <note>
 	    <para>Some ports are not maintained by an individual but
 	      instead by a <ulink
 	      url="&url.articles.mailing-list-faq;/article.html">mailing
 	      list</ulink>.  Many, but not all, of these addresses look like
 	      <email role="nolink">freebsd-listname@FreeBSD.org</email>.  Please
 	      take this into account when phrasing your questions.</para>
 
-	    <para>In particular, ports shown as maintained by
-	      <email role="nolink">freebsd-ports@FreeBSD.org</email> are
-	      actually not maintained by anyone.  Fixes and support, if
-	      any, come from the general community who subscribe to that
-	      mailing list.  More volunteers are always needed!</para>
+	    <para>¤×¨ä·í port ªº maintainer Äæ¦ì¬O
+	      <email role="nolink">freebsd-ports@FreeBSD.org</email> 
+	        ®É¡A¨Æ¹ê¤W¤w¸g¨S¤H·í¸Ó port maintainer ¤F¡C
+	        ¦]¦¹­Y¸Ó port ¤´¦³­×¥¿©Î¨ä¥L§Þ³N¤ä´©ªº¸Ü¡A¬ÛÃö°Q½×³£·|¦b freebsd-ports ¶l»¼½×¾Â¤W¥X²{¡C
+	        ³á¡A¹ï¤F¡A¦pªG¦³¼ô±x¸Ó³nÅéªÌ¡A§ÓÄ@·í¸Ó port maintainer ªº¸Ü¡A§Ú­Ì¤]³£«ÜÅwªï±zªº¥[¤J³á¡C</para>
 	  </note>
 
-	  <para>If you do not get a response,
-	    you can use &man.send-pr.1; to submit a bug
-	    report (see <ulink
+	  <para>­Y port maintainer ¨S¦³¦^Âбzªº«H¥ó¡A «h¥i¥H¥Î &man.send-pr.1; 
+	    ¨Ó´£¥æ°ÝÃD³ø§i PR¡C(½Ð°Ñ¾\ <ulink
 	    url="&url.articles.problem-reports;/article.html">Writing
-	    FreeBSD Problem Reports</ulink>).</para>
+	    FreeBSD Problem Reports</ulink>)¡C</para>
 	</listitem>
 
         <listitem>
-	  <para>Fix it!  The <ulink
+	  <para>¸Õ¸Õ¬Ý­×¥¿¥¦§a!  <ulink
 	    url="&url.books.porters-handbook;/index.html">Porter's
-	    Handbook</ulink> includes detailed information on the
-	    <quote>Ports</quote> infrastructure so that you can fix the occasional
-	    broken port or even submit your own!</para>
+	    Handbook</ulink> ¥]¬A¤F <quote>Ports</quote> 
+	    ¬[ºcªº²Ó¸`³¡¥÷¡A³o¨Ç®Ñ¤¤¤º®e¦³§U±z­×¦n¦³°ÝÃDªº port ¬Æ¦Ü´£¥æ¦Û¤vªº port¡T</para>
 	</listitem>
 
 	<listitem>
-	  <para>Grab the package from an FTP site near you.  The
-	    <quote>master</quote> package collection is on <hostid
-	    role="fqdn">ftp.FreeBSD.org</hostid> in the <ulink
+	  <para>±q¸ûªñªº FTP ¯¸ÂI¤U¸ü½sĶ¦nªº package¡C
+	    package collection ªº³Ì¤W´å¯¸¬O¦b <hostid
+	    role="fqdn">ftp.FreeBSD.org</hostid> ¤Wªº <ulink
 	    url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/">packages
-	    directory</ulink>, but be sure to check your <ulink
+	    ¥Ø¿ý</ulink>¤º¡A¦ý½Ð°O±o¥ýÀˬd¬O§_¤w¦³ <ulink
 	    url="http://mirrorlist.FreeBSD.org/">local mirror</ulink>
-	    <emphasis>first</emphasis>!  These are more likely to work
-	    than trying to compile from source and are a lot faster as
-	    well.  Use the &man.pkg.add.1; program to install the
-	    package on your system.</para>
+	    ¯¸!  ³q±`±¡ªp¤U³o¨Ç package ³£¥i¥Hª½±µ¨Ï¥Î¡A¦Ó¥BÀ³¸Ó¤ñ¦Û¦æ½sĶ§Ö¤@¨Ç¡C
+	    ¥Î &man.pkg.add.1; §Y¥i¶¶§Q¦w¸Ë package ¡C</para>
 	</listitem>
       </orderedlist>
   </sect1>
 
 </chapter>
 
 <!--
      Local Variables:
      mode: sgml
      sgml-declaration: "../chapter.decl"
      sgml-indent-data: t
      sgml-omittag: nil
      sgml-always-quote-attributes: t
      sgml-parent-document: ("../book.sgml" "part" "chapter")
      End:
 -->
diff --git a/zh_TW.Big5/books/handbook/security/chapter.sgml b/zh_TW.Big5/books/handbook/security/chapter.sgml
index 58d2b80de9..0ec3c4b8db 100644
--- a/zh_TW.Big5/books/handbook/security/chapter.sgml
+++ b/zh_TW.Big5/books/handbook/security/chapter.sgml
@@ -1,5123 +1,5087 @@
 <!--
      The FreeBSD Documentation Project
 
      $FreeBSD$
 -->
 
 <chapter id="security">
   <chapterinfo>
     <authorgroup>
       <author>
 	<firstname>Matthew</firstname>
 	<surname>Dillon</surname>
 	<contrib>Much of this chapter has been taken from the
 	security(7) manual page by </contrib>
       </author>
     </authorgroup>
   </chapterinfo>
 
-  <title>Security</title>
+  <title>¨t²Î¦w¥þ</title>
   <indexterm><primary>security</primary></indexterm>
 
   <sect1 id="security-synopsis">
-    <title>Synopsis</title>
+    <title>·§­z</title>
 
-    <para>This chapter will provide a basic introduction to system security
-      concepts, some general good rules of thumb, and some advanced topics
-      under &os;.  A lot of the topics covered here can be applied
-      to system and Internet security in general as well.  The Internet
-      is no longer a <quote>friendly</quote> place in which everyone
-      wants to be your kind neighbor.  Securing your system is imperative
-      to protect your data, intellectual property, time, and much more
-      from the hands of hackers and the like.</para>
+    <para>³o¤@³¹±N¹ï¨t²Î¦w¥þªº°ò¥»·§©À¶i¦æ¤¶²Ð¡A°£¦¹¤§¥~¡AÁÙ±N¤¶²Ð¤@¨Ç¦nªº²ßºD¡A¥H¤Î
+	&os; ¤Uªº¤@¨Ç§ó²`¤Jªº¸ÜÃD¡C³o³¹ªº³\¦h¤º®e¹ï©ó¤@¯ëªº¨t²Î©M Internet 
+	¦w¥þ¤]¾A¥Î¡C¦p¤µ¡AInternet ¤w¸g¤£¦A¹³¥H«e¨º¼Ë¬O­Ó¤H¤H³£Ä@·N»P±z§@¦n¾F©~ªº¡y¤Íµ½³õ©Ò¡z¡C
+	¥²¶·Åý¨t²Î§ó¦w¥þ¡A¤~¯à¥h«OÅ@±zªº¸ê®Æ¡B´¼¼z°]²£¡BÄ_¶Q®É¶¡¥H¤Î¨ä¥L«Ü¦hªF¦è¡A
+	¦Ó¤£¦Ü©ó³Q¤J«IªÌ©Î¤ß¦s´c·Nªº¤H©ÒÅѨú¡C</para>
 
-    <para>&os; provides an array of utilities and mechanisms to ensure
-      the integrity and security of your system and network.</para>
+    <para>&os; ´£¨Ñ¤F¤@¨t¦C¤u¨ã©M¬ÛÃö¾÷¨î¡A¨Ó½T«O¨t²Î©Mºô¸ôªº§¹¾ã¡B¦w¥þ¡C</para>
 
-    <para>After reading this chapter, you will know:</para>
+    <para>Ū§¹³o³¹¡A±z±N¤F¸Ñ¡J</para>
 
     <itemizedlist>
       <listitem>
-	<para>Basic system security concepts, in respect to &os;.</para>
+	<para> &os; ¨t²Îªº°ò¥»¦w¥þ·§©À¡C</para>
       </listitem>
 
       <listitem>
-	<para>About the various crypt mechanisms available in &os;,
-	  such as <acronym>DES</acronym> and <acronym>MD5</acronym>.</para>
+	<para>&os; ¤¤³\¦h¥i¥Îªº¥[±K¾÷¨î¡A¨Ò¦p <acronym>DES</acronym> ¤Î
+	  <acronym>MD5</acronym>¡C</para>
       </listitem>
 
       <listitem>
-	<para>How to set up one-time password authentication.</para>
+	<para>¦p¦ó«Ø¥ß¤@¦¸©Ê(one-time)±K½XÅçÃÒ¾÷¨î¡C</para>
       </listitem>
 
       <listitem>
-	<para>How to configure <acronym>TCP</acronym> Wrappers for use
-	  with <command>inetd</command>.</para>
+	<para>¦p¦ó³]©w <acronym>TCP</acronym> Wrappers 
+	  ¥H«K»P <command>inetd</command> °t¦X¨Ï¥Î¡C</para>
       </listitem>
 
       <listitem>
-	<para>How to set up <application>KerberosIV</application> on &os;
-	  releases prior to 5.0.</para>
+	<para>¦p¦ó¦b &os; 5.0. ¤§«eªºª©¥»¤W³]©w <application>KerberosIV</application>¡C</para>
       </listitem>
 
       <listitem>
-	<para>How to set up <application>Kerberos5</application> on
-	  post &os; 5.0 releases.</para>
+	<para>¦p¦ó¦b &os; 5.0 (§t¤§«áª©¥»)¤W³]©w <application>Kerberos5</application>¡C</para>
       </listitem>
 
       <listitem>
-	<para>How to configure IPsec and create a <acronym>VPN</acronym> between
-	&os;/&windows; machines.</para>
+	<para>¦p¦ó³]©w IPsec ¥H¤Î¦b &os;/&windows; ¤W«Ø¥ß <acronym>VPN</acronym> ºô¸ô¡C</para>
       </listitem>
      
       <listitem>
-	<para>How to configure and use <application>OpenSSH</application>, &os;'s <acronym>SSH</acronym>
-	  implementation.</para>
+	<para>¦p¦ó³]©w¡B¹B¥Î <application>OpenSSH</application>¡A¥H¤Î &os; ªº
+	  <acronym>SSH</acronym> ¹ê§@¤è¦¡(implementation)</para>
       </listitem>
 
       <listitem>
-	<para>What file system <acronym>ACL</acronym>s are and how to use them.</para>
+	<para>¤F¸ÑÀɮרt²Îªº <acronym>ACL</acronym>s ¾÷¨î¬°¦ó¡A¥H¤Î¦p¦ó¹B¥Î¡C</para>
       </listitem>
 
       <listitem>
-	<para>How to use the <application>Portaudit</application>
-	  utility to audit third party software packages installed
-	  from the Ports Collection.</para>
+	<para>¦p¦ó¨Ï¥Î <application>Portaudit</application>
+	  ¤u¨ã¨ÓÀËÅç(audit) ±q Ports Collection ¦w¸Ëªº³nÅé¦w¥þ©Ê¡C</para>
       </listitem>
 
       <listitem>
-	<para>How to utilize the &os; security advisories
-	  publications.</para>
+	<para>¦p¦óµ½¥Î &os; ¦w¥þ¤½§i(Security Advisories)¡A¨Ã±Ä¨ú¬ÛÀ³±¹¬I¡C</para>
       </listitem>
 
       <listitem>
-	<para>Have an idea of what Process Accounting is and how to
-	  enable it on &os;.</para>
+	<para>ÁA¸Ñ Process Accounting ¾÷¨î¤Î¦p¦ó¦b &os; ¤W±Ò°Ê¡C</para>
       </listitem>
     </itemizedlist>
 
-    <para>Before reading this chapter, you should:</para>
+    <para>¦b¶}©l¾\Ū³o³¹¤§«e¡A±z»Ý­n¡J</para>
 
     <itemizedlist>
       <listitem>
-	<para>Understand basic &os; and Internet concepts.</para>
+	<para>ÁA¸Ñ &os; ¤Î Internet ªº°ò¥»·§©À¡C</para>
       </listitem>
     </itemizedlist>
 
-    <para>Additional security topics are covered throughout this book.
-      For example, Mandatory Access Control is discussed in <xref
-      linkend="mac"> and Internet Firewalls are discussed in <xref
-      linkend="firewalls">.</para>
+    <para>¥»®Ñ¤¤¨ä¥L³¹¸`¡A¤]¦³¤¶²Ð¦w¥þ¤è­±ªº¨ä¥L¸ÜÃD¡C¨Ò¦p¡G
+       ¦b <xref linkend="mac"> ¦³½Í¨ì Mandatory Access Control¡A Internet Firewalls «h¦b <xref
+      linkend="firewalls">¡C</para>
   </sect1>
 
   <sect1 id="security-intro">
-    <title>Introduction</title>
-
-    <para>Security is a function that begins and ends with the system
-      administrator.  While all BSD &unix; multi-user systems have some
-      inherent security, the job of building and maintaining additional
-      security mechanisms to keep those users <quote>honest</quote> is
-      probably one of the single largest undertakings of the sysadmin.
-      Machines are only as secure as you make them, and security concerns
-      are ever competing with the human necessity for convenience.  &unix;
-      systems, in general, are capable of running a huge number of
-      simultaneous processes and many of these processes operate as
-      servers &mdash; meaning that external entities can connect and talk
-      to them.  As yesterday's mini-computers and mainframes become
-      today's desktops, and as computers become networked and
-      internetwork, security becomes an even bigger issue.</para>
-
-    <para>Security is best implemented through a layered
-      <quote>onion</quote> approach.  In a nutshell, what you want to do is
-      to create as many layers of security as are convenient and then
-      carefully monitor the system for intrusions.  You do not want to
+    <title>¤¶²Ð</title>
+
+    <para>¦w¥þ¡A¹ï¨t²ÎºÞ²zªÌ¦Ó¨¥¡A¬O¦Ü©l¦Ü²×³Ì°ò¥»ªº­n¨D¡C¥Ñ©ó©Ò¦³ªº BSD &unix; multi-user
+	¨t²Î³£´£¨Ñ¤F»P¥Í­Ñ¨Óªº°ò¥»¦w¥þ¡A©Ò¥H«Ø¥ß¡BºûÅ@ÃB¥~ªº¦w¥þ¾÷¨î¡A¥H½T«O¨Ï¥ÎªÌªº¡y¥i¾a¡z¡A
+	¥i¯à¤]´N¬O¨t²ÎºÞ²z­û³Ì»Ý­n·V«äªºÁ}¥¨¥ô°È¤F¡C¾÷¾¹ªº¦w¥þ©Ê¨ú¨M©ó±z©Ò«Ø¥ßªº¦w¥þ±¹¬I¡A
+	¦Ó³\¦h¦w¥þ¤è­±ªº¦Ò¶q¡A«h·|»P¤H­Ì¨Ï¥Î¹q¸£®Éªº«K§Q¬Û¥Ù¬Þ¡C¤@¯ë¨Ó»¡¡A &unix; 
+	¨t²Î¥i¦P®É°õ¦æ³\¦h¼Æ¥Øªºµ{¦¡ process ¡A¨Ã¥B¨ä¤¤³\¦h process ¤]¦P®É¥H Server ºÝ¨Ó¹B§@¡C
+	 ¢w¢w ³o·N¨ýµÛ¡A¥~³¡¹êÅé¾÷¾¹¯à°÷»P¥¦­Ì¤¬¬Û³s±µ¡A¨Ã²£¥Í¤¬°Ê¡C²{¦bªº¤@¯ë®à¾÷¡A
+	¤w¸g¯à°÷¹F¨ì¥H«e¤p«¬¥D¾÷¬Æ¦Ü¤j«¬¥D¾÷ªº©Ê¯à¡A¦ÓÀHµÛ³o¨Ç¹q¸£ªººô¸ô³s±µ©M¦b§ó¤j½d³ò¤º¤¬¬Û³s±µ
+	¡A¦w¥þ¤]¦¨¬°¤F¤@­Ó¤é¯qÄY®mªº½ÒÃD¡C</para>
+
+    <para>¦w¥þ³Ì¦nªº¤è¦¡¡A¬O¯à°÷³z¹L¹³¡y¬v½µ¡z¨º¼Ëªº¼h¼h¨¾Å@¼Ò¦¡¡C
+	²³æÁ¿¡AÀ³¸Ó¾¨¥i¯àªº«Ø¥ß¦h¼h¦¸¦w¥þ¨¾Å@¡A¨Ã¤p¤ß¦aºÊµø¦UÃþ°w¹ï¨t²Îªº¤J«IºÃÂI¡C
+	You do not want to
       overbuild your security or you will interfere with the detection
       side, and detection is one of the single most important aspects of
       any security mechanism.  For example, it makes little sense to set
       the <literal>schg</literal> flag (see &man.chflags.1;) on every
       system binary because
       while this may temporarily protect the binaries, it prevents an
       attacker who has broken in from making an easily detectable change
       that may result in your security mechanisms not detecting the attacker
       at all.</para>
 
     <para>System security also pertains to dealing with various forms of
       attack, including attacks that attempt to crash, or otherwise make a
       system unusable, but do not attempt to compromise the
       <username>root</username> account (<quote>break root</quote>).
       Security concerns
       can be split up into several categories:</para>
 
     <orderedlist>
       <listitem>
-	<para>Denial of service attacks.</para>
+	<para>ªA°ÈªýÂ_§ðÀ»(DoS)</para>
       </listitem>
 
       <listitem>
-	<para>User account compromises.</para>
+	<para>ÅѨú¨ä¥L¨Ï¥ÎªÌªº±b¸¹¡C</para>
       </listitem>
 
       <listitem>
-	<para>Root compromise through accessible servers.</para>
+	<para>³z¹L¦U¦¡ Server ¤W©Ò´£¨Ñªº Service ¨ÓÅѨú root ±b¸¹¡C</para>
       </listitem>
 
       <listitem>
-	<para>Root compromise via user accounts.</para>
+	<para>³z¹L¨Ï¥ÎªÌ±b¸¹ÅѨú root ±b¸¹¡C</para>
       </listitem>
 
       <listitem>
-	<para>Backdoor creation.</para>
+	<para>¶}«áªù¡C</para>
       </listitem>
     </orderedlist>
 
     <indexterm>
       <primary>DoS attacks</primary>
       <see>Denial of Service (DoS)</see>
     </indexterm>
     <indexterm>
       <primary>security</primary>
       <secondary>DoS attacks</secondary>
       <see>Denial of Service (DoS)</see>
     </indexterm>
     <indexterm><primary>Denial of Service (DoS)</primary></indexterm>
 
     <para>A denial of service attack is an action that deprives the
       machine of needed resources.  Typically, DoS attacks are
       brute-force mechanisms that attempt to crash or otherwise make a
       machine unusable by overwhelming its servers or network stack.  Some
       DoS attacks try to take advantage of bugs in the networking
       stack to crash a machine with a single packet.  The latter can only
       be fixed by applying a bug fix to the kernel.  Attacks on servers
       can often be fixed by properly specifying options to limit the load
       the servers incur on the system under adverse conditions.
       Brute-force network attacks are harder to deal with.  A
       spoofed-packet attack, for example, is nearly impossible to stop,
       short of cutting your system off from the Internet.  It may not be
       able to take your machine down, but it can saturate your
       Internet connection.</para>
 
     <indexterm>
       <primary>security</primary>
       <secondary>account compromises</secondary>
     </indexterm>
 
     <para>A user account compromise is even more common than a DoS
       attack.  Many sysadmins still run standard 
       <application>telnetd</application>, <application>rlogind</application>,
       <application>rshd</application>,
       and <application>ftpd</application> servers on their machines.
       These servers, by default, do
       not operate over encrypted connections.  The result is that if you
       have any moderate-sized user base, one or more of your users logging
       into your system from a remote location (which is the most common
       and convenient way to login to a system) will have his or her
       password sniffed.  The attentive system admin will analyze his
       remote access logs looking for suspicious source addresses even for
       successful logins.</para>
 
     <para>One must always assume that once an attacker has access to a
       user account, the attacker can break <username>root</username>.
       However, the reality is that in a well secured and maintained system,
       access to a user account does not necessarily give the attacker
       access to <username>root</username>.  The distinction is important
       because without access to <username>root</username> the attacker
       cannot generally hide his tracks and may, at best, be able to do
       nothing more than mess with the user's files, or crash the machine.
       User account compromises are very common because users tend not to
       take the precautions that sysadmins take.</para>
 
     <indexterm>
       <primary>security</primary>
       <secondary>backdoors</secondary>
     </indexterm>
 
     <para>System administrators must keep in mind that there are
       potentially many ways to break <username>root</username> on a machine.
       The attacker may know the <username>root</username> password,
       the attacker may find a bug in a root-run server and be able
       to break <username>root</username> over a network
       connection to that server, or the attacker may know of a bug in
       a suid-root program that allows the attacker to break
       <username>root</username> once he has broken into a user's account.
       If an attacker has found a way to break <username>root</username>
       on a machine, the attacker may not have a need
       to install a backdoor.  Many of the <username>root</username> holes
       found and closed to date involve a considerable amount of work
       by the attacker to cleanup after himself, so most attackers install
       backdoors.  A backdoor provides the attacker with a way to easily
       regain <username>root</username> access to the system, but it
       also gives the smart system administrator a convenient way
       to detect the intrusion.
       Making it impossible for an attacker to install a backdoor may
       actually be detrimental to your security, because it will not
       close off the hole the attacker found to break in the first
       place.</para>
 
 
     <para>Security remedies should always be implemented with a
       multi-layered <quote>onion peel</quote> approach and can be
       categorized as follows:</para>
 
     <orderedlist>
       <listitem>
 	<para>Securing <username>root</username> and staff accounts.</para>
       </listitem>
 
       <listitem>
 	<para>Securing <username>root</username>&ndash;run servers
 	  and suid/sgid binaries.</para>
       </listitem>
 
       <listitem>
 	<para>Securing user accounts.</para>
       </listitem>
 
       <listitem>
 	<para>Securing the password file.</para>
       </listitem>
 
       <listitem>
 	<para>Securing the kernel core, raw devices, and
 	  file systems.</para>
       </listitem>
 
       <listitem>
 	<para>Quick detection of inappropriate changes made to the
 	  system.</para>
       </listitem>
 
       <listitem>
 	<para>Paranoia.</para>
       </listitem>
     </orderedlist>
 
     <para>The next section of this chapter will cover the above bullet
       items in greater depth.</para>
   </sect1>
 
   <sect1 id="securing-freebsd">
-    <title>Securing &os;</title>
+    <title>&os; ªº¨t²Î¦w¥þ</title>
     <indexterm>
       <primary>security</primary>
       <secondary>securing &os;</secondary>
     </indexterm>
 
     <note>
       <title>Command vs. Protocol</title>
       <para>Throughout this document, we will use
        <application>bold</application> text to refer to an
        application, and a <command>monospaced</command> font to refer
        to specific commands.  Protocols will use a normal font.  This
        typographical distinction is useful for instances such as ssh,
        since it is
        a protocol as well as command.</para>
     </note>
 
     <para>The sections that follow will cover the methods of securing your
       &os; system that were mentioned in the <link
         linkend="security-intro">last section</link> of this chapter.</para>
 
     <sect2 id="securing-root-and-staff">
       <title>Securing the <username>root</username> Account and
 	Staff Accounts</title>
       <indexterm>
         <primary><command>su</command></primary>
       </indexterm>
 
       <para>First off, do not bother securing staff accounts if you have
 	not secured the <username>root</username> account.
 	Most systems have a password assigned to the <username>root</username>
 	account.  The first thing you do is assume
 	that the password is <emphasis>always</emphasis> compromised.
 	This does not mean that you should remove the password.  The
 	password is almost always necessary for console access to the
 	machine.  What it does mean is that you should not make it
 	possible to use the password outside of the console or possibly
 	even with the &man.su.1; command.  For example, make sure that
 	your ptys are specified as being insecure in the
 	<filename>/etc/ttys</filename> file so that direct
 	<username>root</username> logins
 	via <command>telnet</command> or <command>rlogin</command> are
 	disallowed.  If using other login services such as
         <application>sshd</application>, make sure that direct
 	<username>root</username> logins are disabled there as well.
 	You can do this by editing
         your <filename>/etc/ssh/sshd_config</filename> file, and making
         sure that <literal>PermitRootLogin</literal> is set to
         <literal>NO</literal>.  Consider every access method &mdash;
         services such as FTP often fall through the cracks.
 	Direct <username>root</username> logins should only be allowed
 	via the system console.</para>
       <indexterm>
         <primary><groupname>wheel</groupname></primary>
       </indexterm>
 
       <para>Of course, as a sysadmin you have to be able to get to
 	<username>root</username>, so we open up a few holes.
 	But we make sure these holes require additional password
 	verification to operate.  One way to make <username>root</username>
 	accessible is to add appropriate staff accounts to the
 	<groupname>wheel</groupname> group (in
 	<filename>/etc/group</filename>).  The staff members placed in the
 	<groupname>wheel</groupname> group are allowed to
 	<command>su</command> to <username>root</username>.
 	You should never give staff
 	members native <groupname>wheel</groupname> access by putting them in the
 	<groupname>wheel</groupname> group in their password entry.  Staff
 	accounts should be placed in a <groupname>staff</groupname> group, and
 	then added to the <groupname>wheel</groupname> group via the
 	<filename>/etc/group</filename> file.  Only those staff members
 	who actually need to have <username>root</username> access
 	should be placed in the
 	<groupname>wheel</groupname> group.  It is also possible, when using
 	an authentication method such as Kerberos, to use Kerberos'
 	<filename>.k5login</filename> file in the <username>root</username>
 	account to allow a &man.ksu.1; to <username>root</username>
 	without having to place anyone at all in the
 	<groupname>wheel</groupname> group.  This may be the better solution
 	since the <groupname>wheel</groupname> mechanism still allows an
 	intruder to break <username>root</username> if the intruder
 	has gotten hold of your
 	password file and can break into a staff account.  While having
 	the <groupname>wheel</groupname> mechanism is better than having
 	nothing at all, it is not necessarily the safest option.</para>
 
       <!-- XXX:
 	This will need updating depending on the outcome of PR bin/71147.
 	Personally I know what I'd like to see, which puts this in definite
 	need of a rewrite, but we'll have to wait and see.  ceri@
       -->
 
       <para>An indirect way to secure staff accounts, and ultimately
         <username>root</username> access is to use an alternative
 	login access method and
         do what is known as <quote>starring</quote> out the encrypted
         password for the staff accounts.  Using the &man.vipw.8;
         command, one can replace each instance of an encrypted password
         with a single <quote><literal>*</literal></quote> character.
 	This command will update the <filename>/etc/master.passwd</filename>
 	file and user/password database to disable password-authenticated
         logins.</para>
 
       <para>A staff account entry such as:</para>
 
       <programlisting>foobar:R9DT/Fa1/LV9U:1000:1000::0:0:Foo Bar:/home/foobar:/usr/local/bin/tcsh</programlisting>
 
       <para>Should be changed to this:</para>
 
       <programlisting>foobar:*:1000:1000::0:0:Foo Bar:/home/foobar:/usr/local/bin/tcsh</programlisting>
 
       <para>This change will prevent normal logins from occurring,
         since the encrypted password will never match
         <quote><literal>*</literal></quote>.  With this done,
 	staff members must use
         another mechanism to authenticate themselves such as
         &man.kerberos.1; or &man.ssh.1; using a public/private key
         pair.  When using something like Kerberos, one generally must
         secure the machines which run the Kerberos servers and your
         desktop workstation.  When using a public/private key pair
         with ssh, one must generally secure
         the machine used to login <emphasis>from</emphasis> (typically
         one's workstation).  An additional layer of protection can be
         added to the key pair by password protecting the key pair when
         creating it with &man.ssh-keygen.1;.  Being able to
         <quote>star</quote> out the passwords for staff accounts also
         guarantees that staff members can only login through secure
         access methods that you have set up.  This forces all staff
         members to use secure, encrypted connections for all of their
         sessions, which closes an important hole used by many
         intruders: sniffing the network from an unrelated,
         less secure machine.</para>
 
       <para>The more indirect security mechanisms also assume that you are
 	logging in from a more restrictive server to a less restrictive
 	server.  For example, if your main box is running all sorts of
 	servers, your workstation should not be running any.  In order for
 	your workstation to be reasonably secure you should run as few
 	servers as possible, up to and including no servers at all, and
 	you should run a password-protected screen blanker.  Of course,
 	given physical access to a workstation an attacker can break any
 	sort of security you put on it.  This is definitely a problem that
 	you should consider, but you should also consider the fact that the
 	vast majority of break-ins occur remotely, over a network, from
 	people who do not have physical access to your workstation or
 	servers.</para>
       <indexterm><primary>KerberosIV</primary></indexterm>
 
       <para>Using something like Kerberos also gives you the ability to
 	disable or change the password for a staff account in one place,
 	and have it immediately affect all the machines on which the staff
 	member may have an account.  If a staff member's account gets
 	compromised, the ability to instantly change his password on all
 	machines should not be underrated.  With discrete passwords,
 	changing a password on N machines can be a mess.  You can also
 	impose re-passwording restrictions with Kerberos:  not only can a
 	Kerberos ticket be made to timeout after a while, but the Kerberos
 	system can require that the user choose a new password after a
 	certain period of time (say, once a month).</para>
     </sect2>
 
     <sect2>
       <title>Securing Root-run Servers and SUID/SGID Binaries</title>
 
       <indexterm>
         <primary><command>ntalk</command></primary>
       </indexterm>
       <indexterm>
         <primary><command>comsat</command></primary>
       </indexterm>
       <indexterm>
         <primary><command>finger</command></primary>
       </indexterm>
       <indexterm>
         <primary>sandboxes</primary>
       </indexterm>
       <indexterm>
         <primary><application>sshd</application></primary>
       </indexterm>
       <indexterm>
         <primary><application>telnetd</application></primary>
       </indexterm>
       <indexterm>
         <primary><application>rshd</application></primary>
       </indexterm>
       <indexterm>
         <primary><application>rlogind</application></primary>
       </indexterm>
 
       <para>The prudent sysadmin only runs the servers he needs to, no
 	more, no less.  Be aware that third party servers are often the
 	most bug-prone.  For example, running an old version of
 	<application>imapd</application> or
 	<application>popper</application> is like giving a universal
 	<username>root</username> ticket out to the entire world.
 	Never run a server that you have not checked out carefully.
 	Many servers do not need to be run as <username>root</username>.
 	For example, the <application>ntalk</application>,
 	<application>comsat</application>, and
 	<application>finger</application> daemons can be run in special
 	user <firstterm>sandboxes</firstterm>.  A sandbox is not perfect,
 	unless you go through a large amount of trouble, but the onion
 	approach to security still stands: If someone is able to break
 	in through a server running in a sandbox, they still have to
 	break out of the sandbox.  The more layers the attacker must
 	break through, the lower the likelihood of his success.  Root
 	holes have historically been found in virtually every server
 	ever run as <username>root</username>, including basic system servers.
 	If you are running a machine through which people only login via
 	<application>sshd</application> and never login via
 	<application>telnetd</application> or
 	<application>rshd</application> or
 	<application>rlogind</application>, then turn off those
 	services!</para>
       
       <para>&os; now defaults to running
 	<application>ntalkd</application>,
 	<application>comsat</application>, and
 	<application>finger</application> in a sandbox.  Another program
 	which may be a candidate for running in a sandbox is &man.named.8;.
 	<filename>/etc/defaults/rc.conf</filename> includes the arguments
 	necessary to run <application>named</application> in a sandbox in a
 	commented-out form.  Depending on whether you are installing a new
 	system or upgrading an existing system, the special user accounts
 	used by these sandboxes may not be installed.  The prudent
 	sysadmin would research and implement sandboxes for servers
 	whenever possible.</para>
       <indexterm>
         <primary><application>sendmail</application></primary>
       </indexterm>
 
       <para>There are a number of other servers that typically do not run
 	in sandboxes: <application>sendmail</application>,
 	<application>popper</application>,
 	<application>imapd</application>, <application>ftpd</application>,
 	and others.  There are alternatives to some of these, but
 	installing them may require more work than you are willing to
 	perform (the convenience factor strikes again).  You may have to
 	run these servers as <username>root</username> and rely on other
 	mechanisms to detect break-ins that might occur through them.</para>
 
       <para>The other big potential <username>root</username> holes in a
 	system are the
 	suid-root and sgid binaries installed on the system.  Most of
 	these binaries, such as <application>rlogin</application>, reside
 	in <filename>/bin</filename>, <filename>/sbin</filename>,
 	<filename>/usr/bin</filename>, or <filename>/usr/sbin</filename>.
 	While nothing is 100% safe, the system-default suid and sgid
 	binaries can be considered reasonably safe.  Still,
 	<username>root</username> holes are occasionally found in these
 	binaries.  A <username>root</username> hole was found in
 	<literal>Xlib</literal> in 1998 that made
 	<application>xterm</application> (which is typically suid)
 	vulnerable.  It is better to be safe than sorry and the prudent
 	sysadmin will restrict suid binaries, that only staff should run,
 	to a special group that only staff can access, and get rid of
 	(<command>chmod 000</command>) any suid binaries that nobody uses.
 	A server with no display generally does not need an
 	<application>xterm</application> binary.  Sgid binaries can be
 	almost as dangerous.  If an intruder can break an sgid-kmem binary,
 	the intruder might be able to read <filename>/dev/kmem</filename>
 	and thus read the encrypted password file, potentially compromising
 	any passworded account.  Alternatively an intruder who breaks
 	group <literal>kmem</literal> can monitor keystrokes sent through
 	ptys, including ptys used by users who login through secure
 	methods.  An intruder that breaks the <groupname>tty</groupname>
 	group can write to
 	almost any user's tty.  If a user is running a terminal program or
 	emulator with a keyboard-simulation feature, the intruder can
 	potentially generate a data stream that causes the user's terminal
 	to echo a command, which is then run as that user.</para>
     </sect2>
 
     <sect2 id="secure-users">
       <title>Securing User Accounts</title>
 
       <para>User accounts are usually the most difficult to secure.  While
 	you can impose Draconian access restrictions on your staff and
 	<quote>star</quote> out their passwords, you may not be able to
 	do so with any general user accounts you might have.  If you do
 	have sufficient control, then you may win out and be able to secure
 	the user accounts properly.  If not, you simply have to be more
 	vigilant in your monitoring of those accounts.  Use of
 	ssh and Kerberos for user accounts is
 	more problematic, due to the extra administration and technical
 	support required, but still a very good solution compared to a
 	crypted password file.</para>
     </sect2>
 
     <sect2>
       <title>Securing the Password File</title>
 
       <para>The only sure fire way is to <literal>*</literal> out as many
 	passwords as you can and use ssh or
 	Kerberos for access to those accounts.  Even though the encrypted
 	password file (<filename>/etc/spwd.db</filename>) can only be read
 	by <username>root</username>, it may be possible for an intruder
 	to obtain read access to that file even if the attacker cannot
 	obtain root-write access.</para>
 
       <para>Your security scripts should always check for and report
 	changes to the password file (see the <link
 	  linkend="security-integrity">Checking file integrity</link> section
 	below).</para>
     </sect2>
 
     <sect2>
       <title>Securing the Kernel Core, Raw Devices, and
 	File systems</title>
 
       <para>If an attacker breaks <username>root</username> he can do
         just about anything, but
 	there are certain conveniences.  For example, most modern kernels
 	have a packet sniffing device driver built in.  Under &os; it
 	is called the <devicename>bpf</devicename> device.  An intruder
 	will commonly attempt to run a packet sniffer on a compromised
 	machine.  You do not need to give the intruder the capability and
 	most systems do not have the need for the
 	<devicename>bpf</devicename> device compiled in.</para>
 
       <indexterm>
         <primary><command>sysctl</command></primary>
       </indexterm>
       <para>But even if you turn off the <devicename>bpf</devicename>
 	device, you still have
 	<filename>/dev/mem</filename> and 
 	<filename>/dev/kmem</filename>
 	to worry about.  For that matter, the intruder can still write to
 	raw disk devices.  Also, there is another kernel feature called
 	the module loader, &man.kldload.8;.  An enterprising intruder can
 	use a KLD module to install his own <devicename>bpf</devicename>
 	device, or other sniffing
 	device, on a running kernel.  To avoid these problems you have to
 	run the kernel at a higher secure level, at least securelevel 1.
 	The securelevel can be set with a <command>sysctl</command> on
 	the <varname>kern.securelevel</varname> variable.  Once you have
 	set the securelevel to 1, write access to raw devices will be
 	denied and special <command>chflags</command> flags,
 	such as <literal>schg</literal>,
 	will be enforced.  You must also ensure that the
 	<literal>schg</literal> flag is set on critical startup binaries,
 	directories, and script files &mdash; everything that gets run up
 	to the point where the securelevel is set.  This might be overdoing
 	it, and upgrading the system is much more difficult when you
 	operate at a higher secure level.  You may compromise and run the
 	system at a higher secure level but not set the
 	<literal>schg</literal> flag for every system file and directory
 	under the sun.  Another possibility is to simply mount
 	<filename>/</filename> and <filename>/usr</filename> read-only.
 	It should be noted that being too Draconian in what you attempt to
 	protect may prevent the all-important detection of an
 	intrusion.</para>
     </sect2>
 
     <sect2 id="security-integrity">
       <title>Checking File Integrity: Binaries, Configuration Files,
 	Etc.</title>
 
       <para>When it comes right down to it, you can only protect your core
 	system configuration and control files so much before the
 	convenience factor rears its ugly head.  For example, using
 	<command>chflags</command> to set the <literal>schg</literal> bit
 	on most of the files in <filename>/</filename> and
 	<filename>/usr</filename> is probably counterproductive, because
 	while it may protect the files, it also closes a detection window.
 	The last layer of your security onion is perhaps the most
 	important &mdash; detection.  The rest of your security is pretty
 	much useless (or, worse, presents you with a false sense of
 	safety) if you cannot detect potential incursions.  Half the job
 	of the onion is to slow down the attacker, rather than stop him, in
 	order to give the detection side of the equation a chance to catch
 	him in the act.</para>
 
       <para>The best way to detect an incursion is to look for modified,
 	missing, or unexpected files.  The best way to look for modified
 	files is from another (often centralized) limited-access system.
 	Writing your security scripts on the extra-secure limited-access
 	system makes them mostly invisible to potential attackers, and this
 	is important.  In order to take maximum advantage you generally
 	have to give the limited-access box significant access to the
 	other machines in the business, usually either by doing a
 	read-only NFS export of the other machines to the limited-access
 	box, or by setting up ssh key-pairs to
 	allow the limited-access box to ssh to
 	the other machines.  Except for its network traffic, NFS is the
 	least visible method &mdash; allowing you to monitor the
 	file systems on each client box virtually undetected.  If your
 	limited-access server is connected to the client boxes through a
 	switch, the NFS method is often the better choice.  If your
 	limited-access server is connected to the client boxes through a
 	hub, or through several layers of routing, the NFS method may be
 	too insecure (network-wise) and using
 	ssh may be the better choice even with
 	the audit-trail tracks that ssh
 	lays.</para>
 
       <para>Once you give a limited-access box, at least read access to the
 	client systems it is supposed to monitor, you must write scripts
 	to do the actual monitoring.  Given an NFS mount, you can write
 	scripts out of simple system utilities such as &man.find.1; and
 	&man.md5.1;.  It is best to physically md5 the client-box files
 	at least once a day, and to test control files such as those
 	found in <filename>/etc</filename> and
 	<filename>/usr/local/etc</filename> even more often.  When
 	mismatches are found, relative to the base md5 information the
 	limited-access machine knows is valid, it should scream at a
 	sysadmin to go check it out.  A good security script will also
 	check for inappropriate suid binaries and for new or deleted files
 	on system partitions such as <filename>/</filename> and
 	<filename>/usr</filename>.</para>
 
       <para>When using ssh rather than NFS,
 	writing the security script is much more difficult.   You
 	essentially have to <command>scp</command> the scripts to the client 
 	box in order to
 	run them, making them visible, and for safety you also need to
 	<command>scp</command> the binaries (such as find) that those
 	scripts use.  The <application>ssh</application> client on the
 	client box may already be compromised.  All in all, using
 	ssh may be necessary when running over
 	insecure links, but it is also a lot harder to deal with.</para>
 
       <para>A good security script will also check for changes to user and
 	staff members access configuration files:
 	<filename>.rhosts</filename>, <filename>.shosts</filename>,
 	<filename>.ssh/authorized_keys</filename> and so forth&hellip;
 	files that might fall outside the purview of the
 	<literal>MD5</literal> check.</para>
 
       <para>If you have a huge amount of user disk space, it may take too
 	long to run through every file on those partitions.  In this case,
 	setting mount flags to disallow suid binaries and devices on those
 	partitions is a good idea.  The <literal>nodev</literal> and
 	<literal>nosuid</literal> options (see &man.mount.8;) are what you
 	want to look into.  You should probably scan them anyway, at least
 	once a week, since the object of this layer is to detect a break-in
 	whether or not the break-in is effective.</para>
 
       <para>Process accounting (see &man.accton.8;) is a relatively
 	low-overhead feature of the operating system which might help
 	as a post-break-in evaluation mechanism.  It is especially
 	useful in tracking down how an intruder has actually broken into
 	a system, assuming the file is still intact after the break-in
 	occurs.</para>
 
       <para>Finally, security scripts should process the log files, and the
 	logs themselves should be generated in as secure a manner as
 	possible &mdash; remote syslog can be very useful.  An intruder
 	tries to cover his tracks, and log files are critical to the
 	sysadmin trying to track down the time and method of the initial
 	break-in.  One way to keep a permanent record of the log files is
 	to run the system console to a serial port and collect the
 	information on a continuing basis through a secure machine
 	monitoring the consoles.</para>
     </sect2>
 
     <sect2>
       <title>Paranoia</title>
 
       <para>A little paranoia never hurts.  As a rule, a sysadmin can add
 	any number of security features, as long as they do not affect
 	convenience, and can add security features that
 	<emphasis>do</emphasis> affect convenience with some added thought.
 	Even more importantly, a security administrator should mix it up a
 	bit &mdash; if you use recommendations such as those given by this
 	document verbatim, you give away your methodologies to the
 	prospective attacker who also has access to this document.</para>
     </sect2>
 
     <sect2>
-      <title>Denial of Service Attacks</title>
+      <title>DoS(Denial of Service)ªA°ÈªýÂ_§ðÀ»</title>
       <indexterm><primary>Denial of Service (DoS)</primary></indexterm>
 
-      <para>This section covers Denial of Service attacks.  A DoS attack
-	is typically a packet attack.  While there is not much you can do
-	about modern spoofed packet attacks that saturate your network,
-	you can generally limit the damage by ensuring that the attacks
-	cannot take down your servers.</para>
+      <para>³o¤@¸`±N¤¶²ÐªA°ÈªýÂ_§ðÀ»¡C DoS §ðÀ»³q±`¬O¥H«Ê¥]ªº¤è¦¡¶i¦æ§ðÀ»¡A
+	¾¨ºÞ´X¥G¨S¦³¥ô¦ó¿ìªk¨Óªý¤î¤j¶qªº°°³y«Ê¥]¯ÓºÉºô¸ô¸ê·½¡A
+	¦ý³q±`¥i¥H³z¹L¤@¨Ç¤è¦¡¨Ó­°§C³oÃþ§ðÀ»ªº·l®`¡A¨Ï¥¦­ÌµLªkÀ»«±¦øªA¾¹¡C</para>
 
       <orderedlist>
 	<listitem>
 	  <para>Limiting server forks.</para>
 	</listitem>
 
 	<listitem>
-	  <para>Limiting springboard attacks (ICMP response attacks, ping
-	    broadcast, etc.).</para>
+	  <para>Limiting springboard attacks (ICMP response §ðÀ»¡Aping
+	    broadcastµ¥µ¥)</para>
 	</listitem>
 
 	<listitem>
 	  <para>Kernel Route Cache.</para>
 	</listitem>
       </orderedlist>
 
       <para>A common DoS attack is against a forking server that attempts
 	to cause the server to eat processes, file descriptors, and memory,
 	until the machine dies.  <application>inetd</application>
 	(see &man.inetd.8;) has several
 	options to limit this sort of attack.  It should be noted that
 	while it is possible to prevent a machine from going down, it is
 	not generally possible to prevent a service from being disrupted
 	by the attack.  Read the <application>inetd</application> manual
 	page carefully and pay
 	specific attention to the <option>-c</option>, <option>-C</option>,
 	and <option>-R</option> options.  Note that spoofed-IP attacks
 	will circumvent the <option>-C</option> option to 
 	<application>inetd</application>, so
 	typically a combination of options must be used.  Some standalone
 	servers have self-fork-limitation parameters.</para>
 
       <para><application>Sendmail</application> has its
 	<option>-OMaxDaemonChildren</option> option, which tends to work
 	much better than trying to use sendmail's load limiting options
 	due to the load lag.  You should specify a
 	<literal>MaxDaemonChildren</literal> parameter, when you start
 	<application>sendmail</application>, high enough to handle your
 	expected load, but not so high that the computer cannot handle that
 	number of <application>sendmails</application> without falling on
 	its face.  It is also prudent to run sendmail in queued mode
 	(<option>-ODeliveryMode=queued</option>) and to run the daemon
 	(<command>sendmail -bd</command>) separate from the queue-runs
 	(<command>sendmail -q15m</command>).  If you still want real-time
 	delivery you can run the queue at a much lower interval, such as
 	<option>-q1m</option>, but be sure to specify a reasonable
 	<literal>MaxDaemonChildren</literal> option for
 	<emphasis>that</emphasis> sendmail to prevent cascade failures.</para>
 
       <para><application>Syslogd</application> can be attacked directly
 	and it is strongly recommended that you use the <option>-s</option>
 	option whenever possible, and the <option>-a</option> option
 	otherwise.</para>
 
       <para>You should also be fairly careful with connect-back services
 	such as <application>TCP Wrapper</application>'s reverse-identd,
 	which can be attacked directly.  You generally do not want to use
 	the reverse-ident feature of
 	<application>TCP Wrapper</application> for this reason.</para>
 
       <para>It is a very good idea to protect internal services from
 	external access by firewalling them off at your border routers.
 	The idea here is to prevent saturation attacks from outside your
 	LAN, not so much to protect internal services from network-based
 	<username>root</username> compromise.
 	Always configure an exclusive firewall, i.e.,
 	<quote>firewall everything <emphasis>except</emphasis> ports A, B,
 	C, D, and M-Z</quote>.  This way you can firewall off all of your
 	low ports except for certain specific services such as
 	<application>named</application> (if you are primary for a zone),
 	<application>ntalkd</application>,
 	<application>sendmail</application>, and other Internet-accessible
 	services.  If you try to configure the firewall the other way
 	&mdash; as an inclusive or permissive firewall, there is a good
 	chance that you will forget to <quote>close</quote> a couple of
 	services, or that you will add a new internal service and forget
 	to update the firewall.  You can still open up the high-numbered
 	port range on the firewall, to allow permissive-like operation,
 	without compromising your low ports.  Also take note that &os;
 	allows you to control the range of port numbers used for dynamic
 	binding, via the various <varname>net.inet.ip.portrange</varname>
 	<command>sysctl</command>'s (<command>sysctl -a | fgrep
 	portrange</command>), which can also ease the complexity of your
 	firewall's configuration.  For example, you might use a normal
 	first/last range of 4000 to 5000, and a hiport range of 49152 to
 	65535, then block off everything under 4000 in your firewall
 	(except for certain specific Internet-accessible ports, of
 	course).</para>
 
       <para>Another common DoS attack is called a springboard attack
 	&mdash; to attack a server in a manner that causes the server to
 	generate responses which overloads the server, the local
 	network, or some other machine.  The most common attack of this
 	nature is the <emphasis>ICMP ping broadcast attack</emphasis>.
 	The attacker spoofs ping packets sent to your LAN's broadcast
 	address with the source IP address set to the actual machine they
 	wish to attack.  If your border routers are not configured to
 	stomp on ping's to broadcast addresses, your LAN winds up
 	generating sufficient responses to the spoofed source address to
 	saturate the victim, especially when the attacker uses the same
 	trick on several dozen broadcast addresses over several dozen
 	different networks at once.  Broadcast attacks of over a hundred
 	and twenty megabits have been measured.  A second common
 	springboard attack is against the ICMP error reporting system.
 	By constructing packets that generate ICMP error responses, an
 	attacker can saturate a server's incoming network and cause the
 	server to saturate its outgoing network with ICMP responses.  This
 	type of attack can also crash the server by running it out of
 	mbuf's, especially if the server cannot drain the ICMP responses
 	it generates fast enough.  &os; 4.X kernels have a kernel
 	compile option called <option>ICMP_BANDLIM</option>
 	which limits the effectiveness
 	of these sorts of attacks.
 	Later kernels use the <application>sysctl</application>
 	variable <literal>net.inet.icmp.icmplim</literal>.
 	The last major class of springboard
 	attacks is related to certain internal 
 	<application>inetd</application> services such as the
 	udp echo service.  An attacker simply spoofs a UDP packet with the
 	source address being server A's echo port, and the destination
 	address being server B's echo port, where server A and B are both
 	on your LAN.  The two servers then bounce this one packet back and
 	forth between each other.  The attacker can overload both servers
 	and their LANs simply by injecting a few packets in this manner.
 	Similar problems exist with the internal 
 	<application>chargen</application> port.  A
 	competent sysadmin will turn off all of these inetd-internal test
 	services.</para>
 
       <para>Spoofed packet attacks may also be used to overload the kernel
 	route cache.  Refer to the <varname>net.inet.ip.rtexpire</varname>,
 	<varname>rtminexpire</varname>, and <varname>rtmaxcache</varname>
 	<command>sysctl</command> parameters.  A spoofed packet attack
 	that uses a random source IP will cause the kernel to generate a
 	temporary cached route in the route table, viewable with
 	<command>netstat -rna | fgrep W3</command>.  These routes
 	typically timeout in 1600 seconds or so.  If the kernel detects
 	that the cached route table has gotten too big it will dynamically
 	reduce the <varname>rtexpire</varname> but will never decrease it 
 	to less than <varname>rtminexpire</varname>.  There are two 
 	problems:</para>
 	
       <orderedlist>
 	<listitem>
 	  <para>The kernel does not react quickly enough when a lightly
 	    loaded server is suddenly attacked.</para>
 	</listitem>
 	
 	<listitem>
 	  <para>The <varname>rtminexpire</varname> is not low enough for
 	    the kernel to survive a sustained attack.</para>
 	</listitem>
       </orderedlist>
       
       <para>If your servers are connected to the Internet via a T3 or
         better, it may be prudent to manually override both
 	<varname>rtexpire</varname> and <varname>rtminexpire</varname>
 	via &man.sysctl.8;.  Never set either parameter to zero (unless
 	you want to crash the machine).  Setting both
 	parameters to 2 seconds should be sufficient to protect the route
 	table from attack.</para>
     </sect2>
 
     <sect2>
       <title>Access Issues with Kerberos and SSH</title>
       <indexterm><primary><command>ssh</command></primary></indexterm>
       <indexterm><primary>KerberosIV</primary></indexterm>
 
       <para>There are a few issues with both Kerberos and
 	ssh that need to be addressed if
 	you intend to use them.  Kerberos V is an excellent
 	authentication protocol, but there are bugs in the kerberized
 	<application>telnet</application> and
 	<application>rlogin</application> applications that make them
 	unsuitable for dealing with binary streams.  Also, by default
 	Kerberos does not encrypt a session unless you use the
 	<option>-x</option> option.  <application>ssh</application>
 	encrypts everything by default.</para>
 
       <para>ssh works quite well in every
 	respect except that it forwards encryption keys by default.  What
 	this means is that if you have a secure workstation holding keys
 	that give you access to the rest of the system, and you
 	ssh to an insecure machine, your keys
 	are usable.  The actual keys themselves are not exposed, but
 	ssh installs a forwarding port for the
 	duration of your login, and if an attacker has broken
 	<username>root</username> on the
 	insecure machine he can utilize that port to use your keys to gain
 	access to any other machine that your keys unlock.</para>
 
       <para>We recommend that you use ssh in
 	combination with Kerberos whenever possible for staff logins.
 	<application>ssh</application> can be compiled with Kerberos
 	support.  This reduces your reliance on potentially exposed
 	ssh keys while at the same time
 	protecting passwords via Kerberos.  ssh
 	keys should only be used for automated tasks from secure machines
 	(something that Kerberos is unsuited to do).  We also recommend that
 	you either turn off key-forwarding in the
 	ssh configuration, or that you make use
 	of the <literal>from=IP/DOMAIN</literal> option that
 	ssh allows in its
 	<filename>authorized_keys</filename> file to make the key only
 	usable to entities logging in from specific machines.</para>
     </sect2>
   </sect1>
 
   <sect1 id="crypt">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Bill</firstname>
 	  <surname>Swingle</surname>
 	  <contrib>Parts rewritten and updated by </contrib>
 	</author>
       </authorgroup>
       <!-- 21 Mar 2000 -->
     </sect1info>
 
     <title>DES, MD5, and Crypt</title>
     <indexterm>
       <primary>security</primary>
       <secondary>crypt</secondary>
     </indexterm>
 
     <indexterm><primary>crypt</primary></indexterm>
     <indexterm><primary>DES</primary></indexterm>
     <indexterm><primary>MD5</primary></indexterm>
 
     <para>Every user on a &unix; system has a password associated with
       their account.  It seems obvious that these passwords need to be
       known only to the user and the actual operating system.  In
       order to keep these passwords secret, they are encrypted with
       what is known as a <quote>one-way hash</quote>, that is, they can
       only be easily encrypted but not decrypted.  In other words, what
       we told you a moment ago was obvious is not even true:  the
       operating system itself does not <emphasis>really</emphasis> know
       the password.  It only knows the <emphasis>encrypted</emphasis>
       form of the password.  The only way to get the
       <quote>plain-text</quote> password is by a brute force search of the
       space of possible passwords.</para>
 
     <para>Unfortunately the only secure way to encrypt passwords when
       &unix; came into being was based on DES, the Data Encryption
       Standard.  This was not such a problem for users resident in
       the US, but since the source code for DES could not be exported
       outside the US, &os; had to find a way to both comply with 
       US law and retain compatibility with all the other &unix;
       variants that still used DES.</para>
 
     <para>The solution was to divide up the encryption libraries 
       so that US users could install the DES libraries and use
       DES but international users still had an encryption method
       that could be exported abroad.  This is how &os; came to
       use MD5 as its default encryption method.  MD5 is believed to
       be more secure than DES, so installing DES is offered primarily
       for compatibility reasons.</para>
 
     <sect2>
       <title>Recognizing Your Crypt Mechanism</title>
 
       <para>Before &os;&nbsp;4.4 <filename>libcrypt.a</filename> was a
 	symbolic link pointing to the library which was used for
 	encryption. &os;&nbsp;4.4 changed <filename>libcrypt.a</filename> to
 	provide a configurable password authentication hash library.
 	Currently the library supports DES, MD5 and Blowfish hash
 	functions.  By default &os; uses MD5 to encrypt
 	passwords.</para>
 
       <para>It is pretty easy to identify which encryption method 
 	&os; is set up to use.  Examining the encrypted passwords in
 	the <filename>/etc/master.passwd</filename> file is one way.
 	Passwords encrypted with the MD5 hash are longer than those
 	encrypted with the DES hash and also begin with the characters
 	<literal>&dollar;1&dollar;</literal>.  Passwords starting with
 	<literal>&dollar;2a&dollar;</literal> are encrypted with the
 	Blowfish hash function.  DES password strings do not
 	have any particular identifying characteristics, but they are
 	shorter than MD5 passwords, and are coded in a 64-character
 	alphabet which does not include the <literal>&dollar;</literal>
 	character, so a relatively short string which does not begin with
 	a dollar sign is very likely a DES password.</para>
 
       <para>The password format used for new passwords is controlled
 	by the <literal>passwd_format</literal> login capability in
 	<filename>/etc/login.conf</filename>, which takes values of
 	<literal>des</literal>, <literal>md5</literal> or
 	<literal>blf</literal>.  See the &man.login.conf.5; manual page
 	for more information about login capabilities.</para>
 
     </sect2>
   </sect1>
 
   <sect1 id="one-time-passwords">
     <title>One-time Passwords</title>
     <indexterm><primary>one-time passwords</primary></indexterm>
     <indexterm>
       <primary>security</primary>
       <secondary>one-time passwords</secondary>
     </indexterm>
 
     <para>S/Key is a one-time password scheme based on a one-way hash
       function.  &os; uses the MD4 hash for compatibility but other
       systems have used MD5 and DES-MAC.  S/Key has been part of the
       &os; base system since version 1.1.5 and is also used on a
       growing number of other operating systems.  S/Key is a registered
       trademark of Bell Communications Research, Inc.</para>
 
     <para>From version 5.0 of &os;, S/Key has been replaced with
       the functionally equivalent OPIE (One-time Passwords In
       Everything).  OPIE uses the MD5 hash by default.</para>
 
     <para>There are three different sorts of passwords which we will discuss
       below.  The first is your usual &unix; style or
       Kerberos password; we will call this a <quote>&unix; password</quote>.
       The second sort is the one-time password which is generated by the
       S/Key <command>key</command> program or the OPIE
       &man.opiekey.1; program and accepted by the
       <command>keyinit</command> or &man.opiepasswd.1; programs
       and the login prompt; we will
       call this a <quote>one-time password</quote>.  The final sort of
       password is the secret password which you give to the
       <command>key</command>/<command>opiekey</command> programs (and
       sometimes the
       <command>keyinit</command>/<command>opiepasswd</command> programs)
       which it uses to generate
       one-time passwords; we will call it a <quote>secret password</quote>
       or just unqualified <quote>password</quote>.</para>
 
     <para>The secret password does not have anything to do with your &unix;
       password; they can be the same but this is not recommended.  S/Key
       and OPIE secret passwords are not limited to 8 characters like old
       &unix; passwords<footnote><para>Under &os; the standard login
       password may be up to 128 characters in length.</para></footnote>,
       they can be as long as you like.  Passwords of six or
       seven word long phrases are fairly common.  For the most part, the
       S/Key or OPIE system operates completely independently of the &unix;
       password system.</para>
 
     <para>Besides the password, there are two other pieces of data that
       are important to S/Key and OPIE.  One is what is known as the
       <quote>seed</quote> or <quote>key</quote>, consisting of two letters
       and five digits.  The other is what is called the <quote>iteration
       count</quote>, a number between 1 and 100.  S/Key creates the
       one-time password by concatenating the seed and the secret password,
       then applying the MD4/MD5 hash as many times as specified by the
       iteration count and turning the result into six short English words.
       These six English words are your one-time password.  The
       authentication system (primarily PAM) keeps
       track of the last one-time password used, and the user is
       authenticated if the hash of the user-provided password is equal to
       the previous password.  Because a one-way hash is used it is
       impossible to generate future one-time passwords if a successfully
       used password is captured; the iteration count is decremented after
       each successful login to keep the user and the login program in
       sync.  When the iteration count gets down to 1, S/Key and OPIE must be
       reinitialized.</para>
 
     <para>There are three programs involved in each system
       which we will discuss below.  The <command>key</command> and
       <command>opiekey</command> programs accept an iteration
       count, a seed, and a secret password, and generate a one-time
       password or a consecutive list of one-time passwords.  The
       <command>keyinit</command> and <command>opiepasswd</command>
       programs are used to initialize S/Key and OPIE respectively,
       and to change passwords, iteration counts, or seeds; they
       take either a secret passphrase, or an iteration count,
       seed, and one-time password.  The <command>keyinfo</command>
       and <command>opieinfo</command> programs examine the
       relevant credentials files (<filename>/etc/skeykeys</filename> or
       <filename>/etc/opiekeys</filename>) and print out the invoking user's
       current iteration count and seed.</para>
 
     <para>There are four different sorts of operations we will cover.  The
       first is using <command>keyinit</command> or
       <command>opiepasswd</command> over a secure connection to set up
       one-time-passwords for the first time,  or to change your password
       or seed.  The second operation is using <command>keyinit</command>
       or <command>opiepasswd</command> over an insecure connection, in
       conjunction with <command>key</command> or <command>opiekey</command>
       over a secure connection,  to do the same.  The third is using
       <command>key</command>/<command>opiekey</command> to log in over
       an insecure connection.  The fourth is using <command>key</command>
       or <command>opiekey</command> to generate a number of keys which
       can be written down or printed out to carry with you when going to
       some location without secure connections to anywhere.</para>
 
     <sect2>
       <title>Secure Connection Initialization</title>
 
       <para>To initialize S/Key for the first time, change your password,
 	or change your seed while logged in over a secure connection
 	(e.g. on the console of a machine or via <application>ssh</application>), use the
 	<command>keyinit</command> command without any parameters while
 	logged in as yourself:</para>
 
       <screen>&prompt.user; <userinput>keyinit</userinput>
 Adding unfurl:
 Reminder - Only use this method if you are directly connected.
 If you are using telnet or rlogin exit with no password and use keyinit -s.
 Enter secret password: 
 Again secret password: 
 
 ID unfurl s/key is 99 to17757
 DEFY CLUB PRO NASH LACE SOFT</screen>
 
       <para>For OPIE, <command>opiepasswd</command> is used instead:</para>
 
       <screen>&prompt.user; <userinput>opiepasswd -c</userinput>
 [grimreaper] ~ $ opiepasswd -f -c
 Adding unfurl:
 Only use this method from the console; NEVER from remote. If you are using
 telnet, xterm, or a dial-in, type ^C now or exit with no password.
 Then run opiepasswd without the -c parameter.
 Using MD5 to compute responses.
 Enter new secret pass phrase:
 Again new secret pass phrase:
 ID unfurl OTP key is 499 to4268
 MOS MALL GOAT ARM AVID COED
 </screen>
 
       <para>At the <prompt>Enter new secret pass phrase:</prompt> or
         <prompt>Enter secret password:</prompt> prompts, you
 	should enter a password or phrase.  Remember, this is not the
 	password that you will use to login with, this is used to generate
 	your one-time login keys.  The <quote>ID</quote> line gives the
 	parameters of your particular instance: your login name, the
         iteration count, and seed.  When logging in the system
 	will remember these parameters and present them back to you so you
 	do not have to remember them.  The last line gives the particular
 	one-time password which corresponds to those parameters and your
 	secret password; if you were to re-login immediately, this
 	one-time password is the one you would use.</para>
     </sect2>
 
     <sect2>
       <title>Insecure Connection Initialization</title>
       
       <para>To initialize or change your secret password over an
 	insecure connection, you will need to already have a secure
 	connection to some place where you can run <command>key</command>
         or <command>opiekey</command>; this might be in the form of a
 	desk accessory on a &macintosh;, or a shell prompt on a machine you
 	trust.  You will also need to make up an iteration count (100 is
 	probably a good value), and you may make up your own seed or use a
 	randomly-generated one.  Over on the insecure connection (to the
 	machine you are initializing), use the <command>keyinit
 	-s</command> command:</para>
 
       <screen>&prompt.user; <userinput>keyinit -s</userinput>
 Updating unfurl:
 Old key: to17758
 Reminder you need the 6 English words from the key command.
 Enter sequence count from 1 to 9999: <userinput>100</userinput>
 Enter new key [default to17759]: 
 s/key 100 to 17759
 s/key access password:
 s/key access password:<userinput>CURE MIKE BANE HIM RACY GORE</userinput>
 </screen>
 
       <para>For OPIE, you need to use <command>opiepasswd</command>:</para>
 
       <screen>&prompt.user; <userinput>opiepasswd</userinput>
 
 Updating unfurl:
 You need the response from an OTP generator.
 Old secret pass phrase:
         otp-md5 498 to4268 ext
         Response: GAME GAG WELT OUT DOWN CHAT
 New secret pass phrase:
         otp-md5 499 to4269
         Response: LINE PAP MILK NELL BUOY TROY
 
 ID mark OTP key is 499 gr4269
 LINE PAP MILK NELL BUOY TROY
 </screen>
 
       <para>To accept the default seed (which the
 	<command>keyinit</command> program confusingly calls a
 	<literal>key</literal>), press <keycap>Return</keycap>.
 	Then before entering an
 	access password, move over to your secure connection or S/Key desk
 	accessory, and give it the same parameters:</para>
 
       <screen>&prompt.user; <userinput>key 100 to17759</userinput>
 Reminder - Do not use this program while logged in via telnet or rlogin.
 Enter secret password: <userinput>&lt;secret password&gt;</userinput>
 CURE MIKE BANE HIM RACY GORE</screen>
 
       <para>Or for OPIE:</para>
 
       <screen>&prompt.user; <userinput>opiekey 498 to4268</userinput>
 Using the MD5 algorithm to compute response.
 Reminder: Don't use opiekey from telnet or dial-in sessions.
 Enter secret pass phrase:
 GAME GAG WELT OUT DOWN CHAT
 </screen>
 
       <para>Now switch back over to the insecure connection, and copy the
 	one-time password generated over to the relevant program.</para>
     </sect2>
 
     <sect2>
       <title>Generating a Single One-time Password</title>
 
       <para>Once you have initialized S/Key or OPIE, when you login you will be 
 	presented with a prompt like this:</para>
 
 <screen>&prompt.user; <userinput>telnet example.com</userinput>
 Trying 10.0.0.1...
 Connected to example.com
 Escape character is '^]'.
 
 FreeBSD/i386 (example.com) (ttypa)
 
 login: <userinput>&lt;username&gt;</userinput>
 s/key 97 fw13894
 Password: </screen>
 
       <para>Or for OPIE:</para>
 
 <screen>&prompt.user; <userinput>telnet example.com</userinput>
 Trying 10.0.0.1...
 Connected to example.com
 Escape character is '^]'.
 
 FreeBSD/i386 (example.com) (ttypa)
 
 login: <userinput>&lt;username&gt;</userinput>
 otp-md5 498 gr4269 ext
 Password: </screen>
 
       <para>As a side note, the S/Key and OPIE prompts have a useful feature
 	(not shown here): if you press <keycap>Return</keycap>
 	at the password prompt, the
 	prompter will turn echo on, so you can see what you are
 	typing.  This can be extremely useful if you are attempting to
 	type in a password by hand, such as from a printout.</para>
 
       <indexterm><primary>MS-DOS</primary></indexterm>
       <indexterm><primary>Windows</primary></indexterm>
       <indexterm><primary>MacOS</primary></indexterm>
 
       <para>At this point you need to generate your one-time password to
 	answer this login prompt.  This must be done on a trusted system
 	that you can run <command>key</command> or
         <command>opiekey</command> on.  (There are versions of these for DOS,
 	&windows; and &macos; as well.) They need both the iteration count and
 	the seed as command line options.  You can cut-and-paste these
         right from the login prompt on the machine that you are logging
         in to.</para>
 
       <para>On the trusted system:</para>
 
       <screen>&prompt.user; <userinput>key 97 fw13894</userinput>
 Reminder - Do not use this program while logged in via telnet or rlogin.
 Enter secret password: 
 WELD LIP ACTS ENDS ME HAAG</screen>
 
       <para>For OPIE:</para>
 
       <screen>&prompt.user; <userinput>opiekey 498 to4268</userinput>
 Using the MD5 algorithm to compute response.
 Reminder: Don't use opiekey from telnet or dial-in sessions.
 Enter secret pass phrase:
 GAME GAG WELT OUT DOWN CHAT</screen>
 
       <para>Now that you have your one-time password you can continue
 	logging in:</para>
 
       <screen>login: <userinput>&lt;username&gt;</userinput>
 s/key 97 fw13894
 Password: <userinput>&lt;return to enable echo&gt;</userinput>
 s/key 97 fw13894
 Password [echo on]: WELD LIP ACTS ENDS ME HAAG
 Last login: Tue Mar 21 11:56:41 from 10.0.0.2 ... </screen>
 
     </sect2>
 
     <sect2>
       <title>Generating Multiple One-time Passwords</title>
 
       <para>Sometimes you have to go places where you do not have
 	access to a trusted machine or secure connection.  In this case,
 	it is possible to use the <command>key</command> and
 	<command>opiekey</command> commands to
 	generate a number of one-time passwords beforehand to be printed
 	out and taken with you.  For example:</para>
 
       <screen>&prompt.user; <userinput>key -n 5 30 zz99999</userinput>
 Reminder - Do not use this program while logged in via telnet or rlogin.
 Enter secret password: <userinput>&lt;secret password&gt;</userinput>
 26: SODA RUDE LEA LIND BUDD SILT 
 27: JILT SPY DUTY GLOW COWL ROT  
 28: THEM OW COLA RUNT BONG SCOT  
 29: COT MASH BARR BRIM NAN FLAG  
 30: CAN KNEE CAST NAME FOLK BILK</screen>
 
       <para>Or for OPIE:</para>
 
       <screen>&prompt.user; <userinput>opiekey -n 5 30 zz99999</userinput>
 Using the MD5 algorithm to compute response.
 Reminder: Don't use opiekey from telnet or dial-in sessions.
 Enter secret pass phrase: <userinput>&lt;secret password&gt;</userinput>
 26: JOAN BORE FOSS DES NAY QUIT
 27: LATE BIAS SLAY FOLK MUCH TRIG
 28: SALT TIN ANTI LOON NEAL USE
 29: RIO ODIN GO BYE FURY TIC
 30: GREW JIVE SAN GIRD BOIL PHI</screen>
 
       <para>The <option>-n 5</option> requests five keys in sequence, the
 	<option>30</option> specifies what the last iteration number
 	should be.  Note that these are printed out in
 	<emphasis>reverse</emphasis> order of eventual use.  If you are
 	really paranoid, you might want to write the results down by hand;
 	otherwise you can cut-and-paste into <command>lpr</command>.  Note
 	that each line shows both the iteration count and the one-time
 	password; you may still find it handy to scratch off passwords as
 	you use them.</para>
     </sect2>
 
     <sect2>
       <title>Restricting Use of &unix; Passwords</title>
 
       <para>S/Key can place restrictions on the use of &unix; passwords based
 	on the host name, user name, terminal port, or IP address of a
 	login session.  These restrictions can be found in the
 	configuration file <filename>/etc/skey.access</filename>.  The
 	&man.skey.access.5; manual page has more information on the complete
 	format of the file and also details some security cautions to be
 	aware of before depending on this file for security.</para>
 
       <para>If there is no <filename>/etc/skey.access</filename> file
 	(this is the default on &os;&nbsp;4.X systems), then all users will
 	be allowed to use &unix; passwords.  If the file exists, however,
 	then all users will be required to use S/Key unless explicitly
 	permitted to do otherwise by configuration statements in the
 	<filename>skey.access</filename> file.  In all cases, &unix;
 	passwords are permitted on the console.</para>
 
       <para>Here is a sample <filename>skey.access</filename> configuration
 	file which illustrates the three most common sorts of configuration
 	statements:</para>
 
       <programlisting>permit internet 192.168.0.0 255.255.0.0
 permit user fnord
 permit port ttyd0</programlisting>
 
       <para>The first line (<literal>permit internet</literal>) allows
 	users whose IP source address (which is vulnerable to spoofing)
 	matches the specified value and mask, to use &unix; passwords.  This
 	should not be considered a security mechanism, but rather, a means
 	to remind authorized users that they are using an insecure network
 	and need to use S/Key for authentication.</para>
 
       <para>The second line (<literal>permit user</literal>) allows the
 	specified username, in this case <username>fnord</username>, to use
 	&unix; passwords at any time.  Generally speaking, this should only
 	be used for people who are either unable to use the
 	<command>key</command> program, like those with dumb terminals, or
 	those who are ineducable.</para>
 
       <para>The third line (<literal>permit port</literal>) allows all
 	users logging in on the specified terminal line to use &unix;
 	passwords; this would be used for dial-ups.</para>
 
       <para>OPIE can restrict the use of &unix; passwords based on the IP
 	address of a login session just like S/Key does.  The relevant file
 	is <filename>/etc/opieaccess</filename>, which is present by default
 	on &os;&nbsp;5.0 and newer systems.  Please check &man.opieaccess.5;
 	for more information on this file and which security considerations
 	you should be aware of when using it.</para>
 	
       <para>Here is a sample <filename>opieaccess</filename> file:</para>
 
       <programlisting>permit 192.168.0.0 255.255.0.0</programlisting>
 
       <para>This line allows users whose IP source address (which is
 	vulnerable to spoofing) matches the specified value and mask,
 	to use &unix; passwords at any time.</para>
 	
       <para>If no rules in <filename>opieaccess</filename> are matched,
 	the default is to deny non-OPIE logins.</para>
 
     </sect2>
   </sect1>
 
   <sect1 id="tcpwrappers">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Tom</firstname>
 	  <surname>Rhodes</surname>
 	  <contrib>Written by: </contrib>
 	</author>
       </authorgroup>
     </sect1info>
 
     <indexterm><primary>TCP Wrappers</primary></indexterm>
       
     <title>TCP Wrappers</title>
 
-    <para>Anyone familiar with &man.inetd.8; has probably heard
-      of <acronym>TCP</acronym> Wrappers at some point.  But few
-      individuals seem to fully comprehend its usefulness in a
-      network environment.  It seems that everyone wants to
-      install a firewall to handle network connections.  While a
-      firewall has a wide variety of uses, there are some things
-      that a firewall not handle such as sending text back to the
-      connection originator.  The <acronym>TCP</acronym> software
-      does this and much more.  In the next few sections many of
-      the <acronym>TCP</acronym> Wrappers features will be discussed,
-      and, when applicable, example configuration lines will be
-      provided.</para>
-
-    <para>The <acronym>TCP</acronym> Wrappers software extends the
-      abilities of <command>inetd</command> to provide support for
-      every server daemon under its control.  Using this method it
-      is possible to provide logging support, return messages to
-      connections, permit a daemon to only accept internal connections,
-      etc.  While some of these features can be provided by implementing
-      a firewall, this will add not only an extra layer of protection
-      but go beyond the amount of control a firewall can
-      provide.</para>
-
-    <para>The added functionality of <acronym>TCP</acronym> Wrappers
-      should not be considered a replacement for a good firewall.
-      <acronym>TCP</acronym> Wrappers can be used in conjunction
-      with a firewall or other security enhancements though and
-      it can serve nicely as an extra layer of protection
-      for the system.</para>
-
-    <para>Since this is an extension to the configuration of
-      <command>inetd</command>, the reader is expected have
-      read the <link linkend="network-inetd">inetd configuration</link>
-      section.</para>
+    <para>¨C­Ó¼ô &man.inetd.8; ªº¤H´X¥G³£·|Å¥¹L <acronym>TCP</acronym> 
+	Wrappers ³o­ÓªF¦è¡A¦ý«Ü¤Ö¤H¯à§¹¥þÁA¸Ñ¥¦¦bºô¸ôÀô¹Ò¤Wªº¦n¥Î¦b­þ¡C
+	¤j¦h¼Æªº¤H³£·|¸Ë¨¾¤õÀð¨Ó«OÅ@ºô¸ô¡AÁöµM¡A¨¾¤õÀð¥Î³~«D±`¼sªx¡A¦ý¨Ã«D¸U¯à¡C
+	¨Ò¦p¡G­Y¥´ºâ¦^¶Ç¤@¬q¤å¦rµ¹³s½u¨Ó·½ªÌµ¥¤§Ãþªº¡C¦Ó <acronym>TCP</acronym> 
+	³nÅé«o¥i¥H°µ¨ì³oÂI¡AÁÙ¦³¨ä¥L§ó¦h¨Æ±¡¡C¦b¥H¤U¬q¸¨¤º¡A§Ú­Ì±NÄ~Äò¤¶²Ð
+	<acronym>TCP</acronym> Wrappers ´£¨Ñªº¥\¯à¡A¥H¤Î¤@¨Ç¹ê»Ú¹B¥Îªº¨Ò¤l¡C</para>
+
+    <para><acronym>TCP</acronym> Wrappers ¥i¥HÅý <command>inetd</command> 
+	©ÒºÞ²zªº¨C­Ó server daemon ¡A³£·|¦b <acronym>TCP</acronym> Wrappers 
+	ªº´x´¤¤§¤U¡C³z¹L <acronym>TCP</acronym> Wrappers ³oºØ¤è¦¡¥i¥H¤ä´©³s½u¬ö¿ý(logging)
+	¡B¦^¶Ç¤@¬q¤å¦rµ¹³s½u¨Ó·½ªÌ¡B¥i¥HÅý daemon ¥u±µ¨ü¤º³¡³s½uµ¥µ¥¡C
+	  ÁöµM¨ä¤¤³¡¥÷¥\¯à¥Î¨¾¤õÀð¤]¥i¥H°µ¨ì¡A¦ý <acronym>TCP</acronym> Wrappers 
+	¤£¥u¬O¼W¥[¤F¤@¼h«OÅ@¡AÁÙ´£¨Ñ¤F¨¾¤õÀð©Ò¿ì¤£¨ìªº¨Æ±¡¡C</para>
+
+    <para>µM¦Ó¡A ¥Ñ <acronym>TCP</acronym> Wrappers ©Ò´£¨Ñªº³o¨ÇÃB¥~¦w¥þ¥\¯à¡A
+	¤£À³¸Óµø¬°Àu¨q¨¾¤õÀ𪺴À¥N¤è®×¡CÀ³¸Óµ²¦X <acronym>TCP</acronym> Wrappers
+	¤Î¨¾¤õÀð¡B¨ä¥L¥[±j¦w¥þ±¹¬I¨Ó¤@¨Ö¹B¥Î¤~¹ï¡A³o¼Ë¤~¥i¥H¬°¨t²Î´£¨Ñ¦h¼h¦w¥þ¨¾Å@¡C</para>
+
+    <para>¥Ñ©ó³o¨Ç³]©w¬O¥D­n°w¹ï 
+      <command>inetd</command> ©Ò´£¨Ñªº¡A©Ò¥H§Ú­Ì«Øij±z¥ý°Ñ¾\ <link 
+	linkend="network-inetd">inetd ³]©w</link> ¤@¸`¡C</para>
 
     <note>
-      <para>While programs run by &man.inetd.8; are not exactly
-	<quote>daemons</quote>, they have traditionally been called
-	daemons.  This is the term we will use in this section too.</para>
+      <para>ÁöµM &man.inetd.8; ©Ò±Ò°Êªºµ{¦¡¨Ã«D¥þ³¡³£¬O¯u¥¿ªº
+	¡ydaemons¡z¡A¦ý¤@¯ë¨ÓÁ¿¡A§Ú­Ì³£ÁÙ¬O·|ºÙ©I¬°¡ydaemons¡z¡A
+	¤U­±§Ú­Ì¤´±N¨Ï¥Î³o¦r²´¨Óªí¹F¡C</para>
     </note>
 
     <sect2>
       <title>Initial Configuration</title>
 
-      <para>The only requirement of using <acronym>TCP</acronym>
-	Wrappers in &os; is to ensure the <command>inetd</command>
-	server is started from <filename>rc.conf</filename> with the
-	<option>-Ww</option> option; this is the default setting.  Of
-	course,	proper configuration of
-	<filename>/etc/hosts.allow</filename> is also expected, but
-	&man.syslogd.8; will throw messages in the system logs in
-	these cases.</para>
+      <para>­Y­n¦b &os; ¤¤¨Ï¥Î <acronym>TCP</acronym>
+	Wrappers ªº¸Ü¡A¥u­n½T©w <command>inetd</command>
+	¦b±Ò°Ê®É¡A¦³¦b <filename>/etc/rc.conf</filename> ¥[¤W
+	<option>-Ww</option> ªº°Ñ¼Æ§Y¥i¡A³o­Ó³]©w¦b¨t²Î¹w³]´N¦³¤F¡C
+	·íµMÁٻݭn¾A·í­×§ï <filename>/etc/hosts.allow</filename> ³]©wÀÉ¡A¦ý 
+	&man.syslogd.8; ¤´·|¦b¨t²Î log Àɤº¡A¬ö¿ý¬ÛÃö¸ê®Æ¤U¨Ó¡C</para>
 
       <note>
-	<para>Unlike other implementations of <acronym>TCP</acronym>
-	  Wrappers, the use of <filename>hosts.deny</filename> has
-	  been deprecated.  All configuration options should be placed
-	  in <filename>/etc/hosts.allow</filename>.</para>
+	<para>FreeBSD ªº <acronym>TCP</acronym> Wrappers ¹ê§@¤è¦¡»P¨ä¥L§@·~¨t²Î¤Wªº 
+		<acronym>TCP</acronym> Wrappers ¤£¤Ó¤@¼Ë¡A¥Ø«e FreeBSD ¤w¸g¼o±ó¤£¥Î
+		<filename>/etc/hosts.deny</filename> ¡A¦Ó¤@«ß§ï¥Î 
+		<filename>/etc/hosts.allow</filename>¡C</para>
       </note>
 
-      <para>In the simplest configuration, daemon connection policies
-	are set to either be permitted or blocked depending on the
-	options in <filename>/etc/hosts.allow</filename>.  The default
+      <para>³Ì²³æªº³]©w¤è¦¡¬O¡A¨C­Ó¹ï daemon ªº³s½u³£¥Ñ 
+	<filename>/etc/hosts.allow</filename> ¨Ó¨M©w¬O§_¤¹³\©Î©Úµ´¡C  The default
 	configuration in &os; is to allow a connection to every daemon
 	started with <command>inetd</command>.  Changing this will be
 	discussed only after the basic configuration is covered.</para>
 
       <para>Basic configuration usually takes the form of
 	<literal>daemon : address : action</literal>.  Where
 	<literal>daemon</literal> is the daemon name which
 	<command>inetd</command> started.  The
 	<literal>address</literal> can be a valid hostname, an
 	<acronym>IP</acronym> address or an IPv6 address enclosed in
 	brackets ([&nbsp;]).  The action field can be either allow
 	or deny	to grant or deny access appropriately.  Keep in mind
 	that configuration works off a first rule match semantic,
 	meaning that the configuration file is scanned in ascending
 	order for a matching rule.  When a match is found the rule
 	is applied and the search process will halt.</para>
 
       <para>Several other options exist but they will be explained
 	in a later section.  A simple configuration line may easily be
 	constructed from that information alone.  For example, to
 	allow <acronym>POP</acronym>3 connections via the
 	<filename role="package">mail/qpopper</filename> daemon,
 	the following lines should be appended to
 	<filename>hosts.allow</filename>:</para>
 
       <programlisting># This line is required for POP3 connections:
 qpopper : ALL : allow</programlisting>
 
-      <para>After adding this line, <command>inetd</command> will need
-	restarted.  This can be accomplished by use of the &man.kill.1;
-	command, or with the <parameter>restart</parameter> parameter
-	with <filename>/etc/rc.d/inetd</filename>.</para>
+      <para>¥[¤W¤W­±³o¦æ¤§«á¡A¥²¶·­«·s±Ò°Ê <command>inetd</command>¡C­«·s±Ò°Êªº¤è¦¡¥i¥H¥Î 
+	&man.kill.1; «ü¥O¡A©Î¥´¡y <filename>/etc/rc.d/inetd</filename> <parameter>restart</parameter>
+	¡z ¨Ó§¹¦¨¡C</para>
       </sect2>
 
       <sect2>
         <title>Advanced Configuration</title>
 
       <para><acronym>TCP</acronym> Wrappers has advanced
 	options too; they will allow for more control over the
 	way connections are handled.  In some cases it may be
 	a good idea to return a comment to certain hosts or
 	daemon connections.  In other cases, perhaps a log file
 	should be recorded or an email sent to the administrator.
 	Other situations may require the use of a service for local
 	connections only.  This	is all possible through the use of
 	configuration options known as <literal>wildcards</literal>,
 	expansion characters and external command execution.  The
 	next two sections are written to cover these situations.</para>
 	
       <sect3>
 	<title>External Commands</title>
 
 	<para>Suppose that a situation occurs where a connection
 	  should be denied yet a reason should be sent to the
 	  individual who attempted to establish that connection.  How
 	  could it be done?  That action can be made possible by
 	  using the <option>twist</option> option.  When a connection
 	  attempt is made, <option>twist</option> will be called to
 	  execute a shell command or script.  An example already exists
 	  in the <filename>hosts.allow</filename> file:</para>
 
 	<programlisting># The rest of the daemons are protected.
 ALL : ALL \
         : severity auth.info \
         : twist /bin/echo "You are not welcome to use %d from %h."</programlisting>
 
 	<para>This example shows that the message,
 	  <quote>You are not allowed to use <literal>daemon</literal>
 	  from <literal>hostname</literal>.</quote> will be returned
 	  for any daemon not previously configured in the access file.
 	  This is extremely useful for sending a reply back to the
 	  connection initiator right after the established connection
 	  is dropped.  Note that any message returned
 	  <emphasis>must</emphasis> be wrapped in quote
 	  <literal>"</literal> characters; there are no exceptions to
 	  this rule.</para>
 
 	<warning>
 	  <para>It may be possible to launch a denial of service attack
 	    on the server if an attacker, or group of attackers could
 	    flood these daemons with connection requests.</para>
 	</warning>
 
 	<para>Another possibility is to use the <option>spawn</option>
 	  option in these cases.  Like <option>twist</option>, the
 	  <option>spawn</option> implicitly denies the connection and
 	  may be used to run external shell commands or scripts.
 	  Unlike <option>twist</option>, <option>spawn</option> will
 	  not send a reply back to the individual who established the
 	  connection.  For an example, consider the following
 	  configuration line:</para>
 
 	<programlisting># We do not allow connections from example.com:
 ALL : .example.com \
 	: spawn (/bin/echo %a from %h attempted to access %d &gt;&gt; \
 	  /var/log/connections.log) \
 	: deny</programlisting>
 
 	<para>This will deny all connection attempts from the
 	  <hostid role="fqdn">*.example.com</hostid> domain;
 	  simultaneously logging the hostname, <acronym>IP</acronym>
 	  address and the daemon which they attempted to access in the
 	  <filename>/var/log/connections.log</filename> file.</para>
 
 	<para>Aside from the already explained substitution characters
 	  above, e.g. %a, a few others exist.  See the
 	  &man.hosts.access.5; manual page for the complete list.</para>
       </sect3>
 
       <sect3>
 	<title>Wildcard Options</title>
 
 	<para>Thus far the <literal>ALL</literal> example has been used
 	  continuously throughout the examples.  Other options exist
 	  which could extend the functionality a bit further.  For
 	  instance, <literal>ALL</literal> may be used to match every
 	  instance of either a daemon, domain or an
 	  <acronym>IP</acronym> address. Another wildcard available is
 	  <literal>PARANOID</literal> which may be used to match any
 	  host which provides an <acronym>IP</acronym> address that may
 	  be forged.  In other words, <literal>paranoid</literal> may
 	  be used to define an action to be taken whenever a connection
 	  is made from an <acronym>IP</acronym> address that differs
 	  from its hostname.  The following example may shed some more
 	  light on this discussion:</para>
 
 	<programlisting># Block possibly spoofed requests to sendmail:
 sendmail : PARANOID : deny</programlisting>
 
 	<para>In that example all connection requests to
 	  <command>sendmail</command> which have an
 	  <acronym>IP</acronym> address that varies from its hostname
 	  will be denied.</para>
 
 	<caution>
 	  <para>Using the <literal>PARANOID</literal> may severely
 	    cripple servers if the client or server has a broken
 	    <acronym>DNS</acronym> setup.  Administrator discretion
 	    is advised.</para>
 	</caution>
 
 	<para>To learn more about wildcards and their associated
 	  functionality, see the &man.hosts.access.5; manual
 	  page.</para>
 
 	<para>Before any of the specific configuration lines above will
 	  work, the first configuration line should be commented out
 	  in <filename>hosts.allow</filename>.  This was noted at the
 	  beginning of this section.</para>
       </sect3>
     </sect2>
   </sect1>
 
   <sect1 id="kerberosIV">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Mark</firstname>
 	  <surname>Murray</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
       <authorgroup>
 	<author>
 	  <firstname>Mark</firstname>
 	  <surname>Dapoz</surname>
 	  <contrib>Based on a contribution by </contrib>
 	</author>
       </authorgroup>
     </sect1info>
 
     <title><application>KerberosIV</application></title>
 
     <para>Kerberos is a network add-on system/protocol that allows users to
       authenticate themselves through the services of a secure server.
       Services such as remote login, remote copy, secure inter-system file
       copying and other high-risk tasks are made considerably safer and more
       controllable.</para>
 
     <para>The following instructions can be used as a guide on how to set up
       Kerberos as distributed for &os;. However, you should refer to the
       relevant manual pages for a complete description.</para>
 
     <sect2>
       <title>Installing <application>KerberosIV</application></title>
 
       <indexterm><primary>MIT</primary></indexterm>
       <indexterm>
 	<primary>KerberosIV</primary>
 	<secondary>installing</secondary>
       </indexterm>
       <para>Kerberos is an optional component of &os;.  The easiest
         way to install this software is by selecting the <literal>krb4</literal> or
         <literal>krb5</literal> distribution in <application>sysinstall</application>
         during the initial installation of &os;. This will install
         the <quote>eBones</quote> (KerberosIV) or <quote>Heimdal</quote> (Kerberos5)
         implementation of Kerberos.  These implementations are
         included because they are developed outside the USA/Canada and
         were thus available to system owners outside those countries
         during the era of restrictive export controls on cryptographic
         code from the USA.</para>
 
       <para>Alternatively, the MIT implementation of Kerberos is
         available from the Ports Collection as
         <filename role="package">security/krb5</filename>.</para>
     </sect2>
 
     <sect2>
       <title>Creating the Initial Database</title>
       
       <para>This is done on the Kerberos server only.  First make sure that
 	you do not have any old Kerberos databases around.  You should change
 	to the directory <filename>/etc/kerberosIV</filename> and check that
 	only the following files are present:</para>
 	  
       <screen>&prompt.root; <userinput>cd /etc/kerberosIV</userinput>
 &prompt.root; <userinput>ls</userinput>
 README		krb.conf        krb.realms</screen>
 	  
       <para>If any additional files (such as <filename>principal.*</filename>
 	or <filename>master_key</filename>) exist, then use the
 	<command>kdb_destroy</command> command to destroy the old Kerberos
 	database, or if Kerberos is not running, simply delete the extra
 	files.</para>
 	  
       <para>You should now edit the <filename>krb.conf</filename> and
 	<filename>krb.realms</filename> files to define your Kerberos realm.
 	In this case the realm will be <literal>EXAMPLE.COM</literal> and the
 	server is <hostid role="fqdn">grunt.example.com</hostid>.  We edit
 	or create the <filename>krb.conf</filename> file:</para>
 	  
       <screen>&prompt.root; <userinput>cat krb.conf</userinput>
 EXAMPLE.COM
 EXAMPLE.COM grunt.example.com admin server
 CS.BERKELEY.EDU okeeffe.berkeley.edu
 ATHENA.MIT.EDU kerberos.mit.edu
 ATHENA.MIT.EDU kerberos-1.mit.edu
 ATHENA.MIT.EDU kerberos-2.mit.edu
 ATHENA.MIT.EDU kerberos-3.mit.edu
 LCS.MIT.EDU kerberos.lcs.mit.edu
 TELECOM.MIT.EDU bitsy.mit.edu
 ARC.NASA.GOV trident.arc.nasa.gov</screen>
 	  
       <para>In this case, the other realms do not need to be there.  They are
 	here as an example of how a machine may be made aware of multiple
 	realms.  You may wish to not include them for simplicity.</para>
 	  
       <para>The first line names the realm in which this system works.  The
 	other lines contain realm/host entries.  The first item on a line is a
 	realm, and the second is a host in that realm that is acting as a
 	<quote>key distribution center</quote>.  The words <literal>admin
 	  server</literal> following a host's name means that host also
 	provides an administrative database server.  For further explanation
 	of these terms, please consult the Kerberos manual pages.</para>
 	  
       <para>Now we have to add <hostid role="fqdn">grunt.example.com</hostid>
 	to the <literal>EXAMPLE.COM</literal> realm and also add an entry to
 	put all hosts in the <hostid role="domainname">.example.com</hostid>
 	domain in the <literal>EXAMPLE.COM</literal> realm.  The
 	<filename>krb.realms</filename> file would be updated as
 	follows:</para>
 	  
       <screen>&prompt.root; <userinput>cat krb.realms</userinput>
 grunt.example.com EXAMPLE.COM
 .example.com EXAMPLE.COM
 .berkeley.edu CS.BERKELEY.EDU
 .MIT.EDU ATHENA.MIT.EDU
 .mit.edu ATHENA.MIT.EDU</screen>
 	  
       <para>Again, the other realms do not need to be there.  They are here as
 	an example of how a machine may be made aware of multiple realms.  You
 	may wish to remove them to simplify things.</para>
 	  
       <para>The first line puts the <emphasis>specific</emphasis> system into
 	the named realm.  The rest of the lines show how to default systems of
 	a particular subdomain to a named realm.</para>
 	  
       <para>Now we are ready to create the database.  This only needs to run
 	on the Kerberos server (or Key Distribution Center).  Issue the
 	<command>kdb_init</command> command to do this:</para>
 	  
       <screen>&prompt.root; <userinput>kdb_init</userinput>
 <prompt>Realm name [default  ATHENA.MIT.EDU ]:</prompt> <userinput>EXAMPLE.COM</userinput>
 You will be prompted for the database Master Password.
 It is important that you NOT FORGET this password.
 		
 <prompt>Enter Kerberos master key:</prompt> </screen>
 	  
       <para>Now we have to save the key so that servers on the local machine
 	can pick it up.  Use the <command>kstash</command> command to do
 	this:</para>
 	
       <screen>&prompt.root; <userinput>kstash</userinput>
 	      
 <prompt>Enter Kerberos master key:</prompt>
 
 Current Kerberos master key version is 1.
 
 Master key entered. BEWARE!</screen>
 	
       <para>This saves the encrypted master password in
 	<filename>/etc/kerberosIV/master_key</filename>.</para>
     </sect2>
     
     <sect2>
       <title>Making It All Run</title>
 	
       <indexterm>
 	<primary>KerberosIV</primary>
 	<secondary>initial startup</secondary>
       </indexterm>
 
       <para>Two principals need to be added to the database for
 	<emphasis>each</emphasis> system that will be secured with Kerberos.
 	Their names are <literal>kpasswd</literal> and <literal>rcmd</literal>.
 	These two principals are made for each system, with the instance being
 	the name of the individual system.</para>
 	  
       <para>These daemons, <application>kpasswd</application> and
 	<application>rcmd</application> allow other systems to change Kerberos
 	passwords and run commands like &man.rcp.1;,
 	&man.rlogin.1; and &man.rsh.1;.</para>
 	  
       <para>Now let us add these entries:</para>
 	    
       <screen>&prompt.root; <userinput>kdb_edit</userinput>
 Opening database...
 
 <prompt>Enter Kerberos master key:</prompt>
 
 Current Kerberos master key version is 1.
 
 Master key entered.  BEWARE!
 Previous or default values are in [brackets] ,
 enter return to leave the same, or new value.
 
 <prompt>Principal name:</prompt> <userinput>passwd</userinput>
 <prompt>Instance:</prompt> <userinput>grunt</userinput>
 
 &lt;Not found&gt;, <prompt>Create [y] ?</prompt> <userinput>y</userinput>
 
 Principal: passwd, Instance: grunt, kdc_key_ver: 1
 <prompt>New Password:</prompt>                    &lt;---- enter RANDOM here
 Verifying password
 
 <prompt>New Password:</prompt> &lt;---- enter RANDOM here
 
 <prompt>Random password [y] ?</prompt> <userinput>y</userinput>
 
 Principal's new key version = 1
 <prompt>Expiration date (enter yyyy-mm-dd) [ 2000-01-01 ] ?</prompt>
 <prompt>Max ticket lifetime (*5 minutes) [ 255 ] ?</prompt>
 <prompt>Attributes [ 0 ] ?</prompt>
 Edit O.K.
 <prompt>Principal name:</prompt> <userinput>rcmd</userinput>
 <prompt>Instance:</prompt> <userinput>grunt</userinput>
 
 &lt;Not found&gt;, <prompt>Create [y] ?</prompt>
 
 Principal: rcmd, Instance: grunt, kdc_key_ver: 1
 <prompt>New Password:</prompt>		&lt;---- enter RANDOM here
 Verifying password
 
 <prompt>New Password:</prompt>           &lt;---- enter RANDOM here
 
 <prompt>Random password [y] ?</prompt>
 
 Principal's new key version = 1
 <prompt>Expiration date (enter yyyy-mm-dd) [ 2000-01-01 ] ?</prompt>
 <prompt>Max ticket lifetime (*5 minutes) [ 255 ] ?</prompt>
 <prompt>Attributes [ 0 ] ?</prompt>
 Edit O.K.
 <prompt>Principal name:</prompt>         &lt;---- null entry here will cause an exit</screen>
     </sect2>
 
     <sect2>
       <title>Creating the Server File</title>
       
       <para>We now have to extract all the instances which define the
 	services on each machine.  For this we use the
 	<command>ext_srvtab</command> command.  This will create a file
 	which must be copied or moved <emphasis>by secure
 	  means</emphasis> to each Kerberos client's
 	<filename>/etc/kerberosIV</filename> directory.  This file must
 	be present on each server and client, and is crucial to the
 	operation of Kerberos.</para>
 	  
 	  
       <screen>&prompt.root; <userinput>ext_srvtab grunt</userinput>
 <prompt>Enter Kerberos master key:</prompt>
 		
 Current Kerberos master key version is 1.
 
 Master key entered. BEWARE!
 Generating 'grunt-new-srvtab'....</screen>
 	  
       <para>Now, this command only generates a temporary file which must be
 	renamed to <filename>srvtab</filename> so that all the servers can pick
 	it up.  Use the &man.mv.1; command to move it into place on
 	the original system:</para>
 	  
       <screen>&prompt.root; <userinput>mv grunt-new-srvtab srvtab</userinput></screen>
 	  
       <para>If the file is for a client system, and the network is not deemed
 	safe, then copy the
 	<filename><replaceable>client</replaceable>-new-srvtab</filename> to
 	removable media and transport it by secure physical means.  Be sure to
 	rename it to <filename>srvtab</filename> in the client's
 	<filename>/etc/kerberosIV</filename> directory, and make sure it is
 	mode 600:</para>
 	  
       <screen>&prompt.root; <userinput>mv grumble-new-srvtab srvtab</userinput>
 &prompt.root; <userinput>chmod 600 srvtab</userinput></screen>
     </sect2>
     
     <sect2>
       <title>Populating the Database</title>
       
       <para>We now have to add some user entries into the database.  First
 	let us create an entry for the user <username>jane</username>.  Use the
 	<command>kdb_edit</command> command to do this:</para>
 	  
       <screen>&prompt.root; <userinput>kdb_edit</userinput>
 Opening database...
 
 <prompt>Enter Kerberos master key:</prompt>
 
 Current Kerberos master key version is 1.
 
 Master key entered.  BEWARE!
 Previous or default values are in [brackets] ,
 enter return to leave the same, or new value.
 
 <prompt>Principal name:</prompt> <userinput>jane</userinput>
 <prompt>Instance:</prompt>
 
 &lt;Not found&gt;, <prompt>Create [y] ?</prompt> <userinput>y</userinput>
 
 Principal: jane, Instance: , kdc_key_ver: 1
 <prompt>New Password:</prompt>                &lt;---- enter a secure password here
 Verifying password
 
 <prompt>New Password:</prompt>                &lt;---- re-enter the password here
 Principal's new key version = 1
 <prompt>Expiration date (enter yyyy-mm-dd) [ 2000-01-01 ] ?</prompt>
 <prompt>Max ticket lifetime (*5 minutes) [ 255 ] ?</prompt>
 <prompt>Attributes [ 0 ] ?</prompt>
 Edit O.K.
 <prompt>Principal name:</prompt>		   &lt;---- null entry here will cause an exit</screen>
     </sect2>
 
     <sect2>
       <title>Testing It All Out</title>
       
       <para>First we have to start the Kerberos daemons.  Note that if you
 	have correctly edited your <filename>/etc/rc.conf</filename> then this
 	will happen automatically when you reboot.  This is only necessary on
 	the Kerberos server.  Kerberos clients will automatically get what
 	they need from the <filename>/etc/kerberosIV</filename>
 	directory.</para>
 	  
       <screen>&prompt.root; <userinput>kerberos &amp;</userinput>
 Kerberos server starting
 Sleep forever on error
 Log file is /var/log/kerberos.log
 Current Kerberos master key version is 1.
 
 Master key entered. BEWARE!
 
 Current Kerberos master key version is 1
 Local realm: EXAMPLE.COM
 &prompt.root; <userinput>kadmind -n &amp;</userinput>
 KADM Server KADM0.0A initializing
 Please do not use 'kill -9' to kill this job, use a
 regular kill instead
 
 Current Kerberos master key version is 1.
 
 Master key entered.  BEWARE!</screen>
 	  
       <para>Now we can try using the <command>kinit</command> command to get a
 	ticket for the ID <username>jane</username> that we created
 	above:</para>
 	  
       <screen>&prompt.user; <userinput>kinit jane</userinput>
 MIT Project Athena (grunt.example.com)
 Kerberos Initialization for "jane"
 <prompt>Password:</prompt> </screen>
 	  
       <para>Try listing the tokens using <command>klist</command> to see if we
 	really have them:</para>
 	  
       <screen>&prompt.user; <userinput>klist</userinput>
 Ticket file:    /tmp/tkt245
 Principal:      jane@EXAMPLE.COM
 
   Issued           Expires          Principal
 Apr 30 11:23:22  Apr 30 19:23:22  krbtgt.EXAMPLE.COM@EXAMPLE.COM</screen>
 	  
       <para>Now try changing the password using &man.passwd.1; to
 	check if the <application>kpasswd</application> daemon can get 
 	authorization to the Kerberos database:</para>
 	  
       <screen>&prompt.user; <userinput>passwd</userinput>
 realm EXAMPLE.COM
 <prompt>Old password for jane:</prompt>
 <prompt>New Password for jane:</prompt>
 Verifying password
 <prompt>New Password for jane:</prompt>
 Password changed.</screen>
     </sect2>
 
     <sect2>
       <title>Adding <command>su</command> Privileges</title>
       
       <para>Kerberos allows us to give <emphasis>each</emphasis> user
 	who needs <username>root</username> privileges their own
 	<emphasis>separate</emphasis> &man.su.1; password.
 	We could now add an ID which is authorized to
 	&man.su.1; to <username>root</username>.  This is
 	controlled by having an instance of <username>root</username>
 	associated with a principal.  Using <command>kdb_edit</command>
 	we can create the entry <literal>jane.root</literal> in the
 	Kerberos database:</para>
 	  
       <screen>&prompt.root; <userinput>kdb_edit</userinput>
 Opening database...
 
 <prompt>Enter Kerberos master key:</prompt>
 
 Current Kerberos master key version is 1.
 
 Master key entered.  BEWARE!
 Previous or default values are in [brackets] ,
 enter return to leave the same, or new value.
 
 <prompt>Principal name:</prompt> <userinput>jane</userinput>
 <prompt>Instance:</prompt> <userinput>root</userinput>
 
 &lt;Not found&gt;, Create [y] ? y
 
 Principal: jane, Instance: root, kdc_key_ver: 1
 <prompt>New Password:</prompt>                    &lt;---- enter a SECURE password here
 Verifying password
 
 <prompt>New Password:</prompt>    	 	 &lt;---- re-enter the password here
 
 Principal's new key version = 1
 <prompt>Expiration date (enter yyyy-mm-dd) [ 2000-01-01 ] ?</prompt>
 <prompt>Max ticket lifetime (*5 minutes) [ 255 ] ?</prompt> <userinput>12</userinput> &lt;--- Keep this short!
 <prompt>Attributes [ 0 ] ?</prompt>
 Edit O.K.
 <prompt>Principal name:</prompt>		         &lt;---- null entry here will cause an exit</screen>
 	  
       <para>Now try getting tokens for it to make sure it works:</para>
       
       <screen>&prompt.root; <userinput>kinit jane.root</userinput>
 MIT Project Athena (grunt.example.com)
 Kerberos Initialization for "jane.root"
 <prompt>Password:</prompt></screen>
 	  
       <para>Now we need to add the user to <username>root</username>'s
 	  <filename>.klogin</filename> file:</para>
 	  
       <screen>&prompt.root; <userinput>cat /root/.klogin</userinput>
 jane.root@EXAMPLE.COM</screen>
 	  
       <para>Now try doing the &man.su.1;:</para>
 	  
       <screen>&prompt.user; <userinput>su</userinput>
 <prompt>Password:</prompt></screen>
 	  
       <para>and take a look at what tokens we have:</para>
 	  
       <screen>&prompt.root; <userinput>klist</userinput>
 Ticket file:	/tmp/tkt_root_245
 Principal:      jane.root@EXAMPLE.COM
 
   Issued           Expires          Principal
 May  2 20:43:12  May  3 04:43:12  krbtgt.EXAMPLE.COM@EXAMPLE.COM</screen>
     </sect2>
 
     <sect2>
       <title>Using Other Commands</title>
       
       <para>In an earlier example, we created a principal called
 	<literal>jane</literal> with an instance <literal>root</literal>.
 	This was based on a user with the same name as the principal, and this
 	is a Kerberos default; that a
 	<literal>&lt;principal&gt;.&lt;instance&gt;</literal> of the form
 	<literal>&lt;username&gt;.</literal><username>root</username> will allow
 	that <literal>&lt;username&gt;</literal> to &man.su.1; to
 	<username>root</username> if the necessary entries are in the
 	<filename>.klogin</filename> file in <username>root</username>'s
 	home directory:</para>
 	  
       <screen>&prompt.root; <userinput>cat /root/.klogin</userinput>
 jane.root@EXAMPLE.COM</screen>
       
       <para>Likewise, if a user has in their own home directory lines of the
 	form:</para>
       
       <screen>&prompt.user; <userinput>cat ~/.klogin</userinput>
 jane@EXAMPLE.COM
 jack@EXAMPLE.COM</screen>
 	  
       <para>This allows anyone in the <literal>EXAMPLE.COM</literal> realm
 	who has authenticated themselves as <username>jane</username> or
 	<username>jack</username> (via <command>kinit</command>, see above)
 	to access to <username>jane</username>'s
 	account or files on this system (<hostid>grunt</hostid>) via
 	&man.rlogin.1;, &man.rsh.1; or
 	&man.rcp.1;.</para>
 	  
       <para>For example, <username>jane</username> now logs into another system using
 	Kerberos:</para>
 	  
 	    <screen>&prompt.user; <userinput>kinit</userinput>
 MIT Project Athena (grunt.example.com)
 <prompt>Password:</prompt>
 &prompt.user; <userinput>rlogin grunt</userinput>
 Last login: Mon May  1 21:14:47 from grumble
 Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994
         The Regents of the University of California.   All rights reserved.
 
 FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
 	  
       <para>Or <username>jack</username> logs into <username>jane</username>'s account on the same machine
 	(<username>jane</username> having
 	set up the <filename>.klogin</filename> file as above, and the person
 	in charge of Kerberos having set up principal
 	<emphasis>jack</emphasis> with a null instance):</para>
 	  
       <screen>&prompt.user; <userinput>kinit</userinput>
 &prompt.user; <userinput>rlogin grunt -l jane</userinput>
 MIT Project Athena (grunt.example.com)
 <prompt>Password:</prompt>
 Last login: Mon May  1 21:16:55 from grumble
 Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994
         The Regents of the University of California.   All rights reserved.
 FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
     </sect2>
   </sect1>
 
   <sect1 id="kerberos5">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Tillman</firstname>
 	  <surname>Hodgson</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
       <authorgroup>
 	<author>
 	  <firstname>Mark</firstname>
 	  <surname>Murray</surname>
 	  <contrib>Based on a contribution by </contrib>
 	</author>
       </authorgroup>
     </sect1info>
 
     <title><application>Kerberos5</application></title>
 
     <para>Every &os; release beyond &os;-5.1 includes support
       only for <application>Kerberos5</application>.  Hence
       <application>Kerberos5</application> is the only version
       included, and its configuration is similar in many aspects
       to that of <application>KerberosIV</application>.  The following
       information only applies to
       <application>Kerberos5</application> in post &os;-5.0
       releases.  Users who wish to use the
       <application>KerberosIV</application> package may install the
       <filename role="package">security/krb4</filename> port.</para>
 
     <para><application>Kerberos</application> is a network add-on
       system/protocol that allows users to authenticate themselves
       through the services of a secure server.  Services such as remote
       login, remote copy, secure inter-system file copying and other
       high-risk tasks are made considerably safer and more
       controllable.</para>
 
     <para><application>Kerberos</application> can be described as an
       identity-verifying proxy system.  It can also be described as a
       trusted third-party authentication system.
       <application>Kerberos</application> provides only one
       function &mdash; the secure authentication of users on the network.
       It does not provide authorization functions (what users are
       allowed to do) or auditing functions (what those users did).
       After a client and server have used
       <application>Kerberos</application> to prove their identity, they
       can also encrypt all of their communications to assure privacy
       and data integrity as they go about their business.</para>
 
     <para>Therefore it is highly recommended that
       <application>Kerberos</application> be used with other security
       methods which provide authorization and audit services.</para>
 
     <para>The following instructions can be used as a guide on how to set
       up <application>Kerberos</application> as distributed for &os;.
       However, you should refer to the relevant manual pages for a complete
       description.</para>
 
     <para>For purposes of demonstrating a <application>Kerberos</application>
       installation, the various name spaces will be handled as follows:</para>
 
     <itemizedlist>
       <listitem>
 	<para>The <acronym>DNS</acronym> domain (<quote>zone</quote>)
 	  will be example.org.</para>
       </listitem>
 
       <listitem>
 	<para>The <application>Kerberos</application> realm will be
 	  EXAMPLE.ORG.</para>
       </listitem>
     </itemizedlist>
 
     <note>
       <para>Please use real domain names when setting up
 	<application>Kerberos</application> even if you intend to run
 	it internally.  This avoids <acronym>DNS</acronym> problems
 	and assures inter-operation with other
 	<application>Kerberos</application> realms.</para>
     </note>
 
     <sect2>
       <title>History</title>
       <indexterm>
 	<primary>Kerberos5</primary>
 	<secondary>history</secondary>
       </indexterm>
 
       <para><application>Kerberos</application> was created by
 	<acronym>MIT</acronym> as a solution to network security problems.
 	The <application>Kerberos</application> protocol uses strong
 	cryptography so that a client can prove its identity to a server
 	(and vice versa) across an insecure network connection.</para>
 
       <para><application>Kerberos</application> is both the name of a
 	network authentication protocol and an adjective to describe
 	programs that implement the program
 	(<application>Kerberos</application> telnet, for example).  The
 	current version of the protocol is version 5, described in
 	<acronym>RFC</acronym>&nbsp;1510.</para>
 
       <para>Several free implementations of this protocol are available,
 	covering a wide range of operating systems.  The Massachusetts
 	Institute of Technology (<acronym>MIT</acronym>), where
 	<application>Kerberos</application> was originally developed,
 	continues to develop their <application>Kerberos</application>
 	package.  It is commonly used in the <acronym>US</acronym>
 	as a cryptography product, as such it
 	has historically been affected by <acronym>US</acronym> export
 	regulations.  The <acronym>MIT</acronym>
 	<application>Kerberos</application> is available as a port
 	(<filename role="package">security/krb5</filename>).  Heimdal
 	<application>Kerberos</application> is another version 5
 	implementation, and was explicitly developed outside of the
 	<acronym>US</acronym> to avoid export
 	regulations (and is thus often included in non-commercial &unix;
 	variants).  The Heimdal <application>Kerberos</application>
 	distribution is available as a port
 	(<filename role="package">security/heimdal</filename>), and a
 	minimal installation of it is included in the base &os;
 	install.</para>
 
     <para>In order to reach the widest audience, these instructions assume
 	the use of the Heimdal distribution included in &os;.</para>
 
     </sect2>
 
     <sect2>
       <title>Setting up a Heimdal <acronym>KDC</acronym></title>
       <indexterm>
 	<primary>Kerberos5</primary>
 	<secondary>Key Distribution Center</secondary>
       </indexterm>
 
       <para>The Key Distribution Center (<acronym>KDC</acronym>) is the
 	centralized authentication service that
 	<application>Kerberos</application> provides &mdash; it is the
 	computer that issues <application>Kerberos</application> tickets.
 	The <acronym>KDC</acronym> is considered <quote>trusted</quote> by
 	all other computers in the <application>Kerberos</application>
 	realm, and thus has heightened security concerns.</para>
 
     <para>Note that while running the <application>Kerberos</application>
 	server requires very few computing resources, a dedicated machine
 	acting only as a <acronym>KDC</acronym> is recommended for security
 	reasons.</para>
 
     <para>To begin setting up a <acronym>KDC</acronym>, ensure that your
 	<filename>/etc/rc.conf</filename> file contains the correct
 	settings to act as a <acronym>KDC</acronym> (you may need to adjust
 	paths to reflect your own system):</para>
 
     <programlisting>kerberos5_server_enable="YES"
 kadmind5_server_enable="YES"
 kerberos_stash="YES"</programlisting>
 
       <note>
 	<para>The <option>kerberos_stash</option> is only available in
 	  &os;&nbsp;4.X.</para>
       </note>
 
       <para>Next we will set up your <application>Kerberos</application>
 	config file, <filename>/etc/krb5.conf</filename>:</para>
 
       <programlisting>[libdefaults]
     default_realm = EXAMPLE.ORG
 [realms]
     EXAMPLE.ORG = {
         kdc = kerberos.example.org
         admin_server = kerberos.example.org
     }
 [domain_realm]
     .example.org = EXAMPLE.ORG</programlisting>
 
       <para>Note that this <filename>/etc/krb5.conf</filename> file implies
 	that your <acronym>KDC</acronym> will have the fully-qualified
 	hostname of <hostid role="fqdn">kerberos.example.org</hostid>.
 	You will need to add a CNAME (alias) entry to your zone file to
 	accomplish this if your <acronym>KDC</acronym> has a different
 	hostname.</para>
 
       <note>
 	<para>For large networks with a properly configured
 	  <acronym>BIND</acronym> <acronym>DNS</acronym> server, the
 	  above example could be trimmed to:</para>
 
 	<programlisting>[libdefaults]
       default_realm = EXAMPLE.ORG</programlisting>
 
 	<para>With the following lines being appended to the
 	  <hostid role="fqdn">example.org</hostid> zonefile:</para>
 
 	<programlisting>_kerberos._udp      IN  SRV     01 00 88 kerberos.example.org.
 _kerberos._tcp      IN  SRV     01 00 88 kerberos.example.org.
 _kpasswd._udp       IN  SRV     01 00 464 kerberos.example.org.
 _kerberos-adm._tcp  IN  SRV     01 00 749 kerberos.example.org.
 _kerberos           IN  TXT     EXAMPLE.ORG</programlisting></note>
 
       <note>
         <para>For clients to be able to find the
           <application>Kerberos</application> services, you
           <emphasis>must</emphasis> have either a fully configured
           <filename>/etc/krb5.conf</filename> or a miminally configured
           <filename>/etc/krb5.conf</filename> <emphasis>and</emphasis> a
           properly configured DNS server.</para>
       </note>
 
       <para>Next we will create the <application>Kerberos</application>
 	database.  This database contains the keys of all principals encrypted
 	with a master password.  You are not
 	required to remember this password, it will be stored in a file
 	(<filename>/var/heimdal/m-key</filename>).  To create the master
 	key, run <command>kstash</command> and enter a password.</para>
 
       <para>Once the master key has been created, you can initialize the
 	database using the <command>kadmin</command> program with the
 	<literal>-l</literal> option (standing for <quote>local</quote>).
 	This option instructs <command>kadmin</command> to modify the
 	database files directly rather than going through the
 	<command>kadmind</command> network service.  This handles the
 	chicken-and-egg problem of trying to connect to the database
 	before it is created.  Once you have the <command>kadmin</command>
 	prompt, use the <command>init</command> command to create your
 	realms initial database.</para>
 
       <para>Lastly, while still in <command>kadmin</command>, create your
 	first principal using the <command>add</command> command.  Stick
 	to the defaults options for the principal for now, you can always
 	change them later with the <command>modify</command> command.
 	Note that you can use the <literal>?</literal> command at any
 	prompt to see the available options.</para>
 
       <para>A sample database creation session is shown below:</para>
 
       <screen>&prompt.root; <userinput>kstash</userinput>
 Master key: <userinput>xxxxxxxx</userinput>
 Verifying password - Master key: <userinput>xxxxxxxx</userinput>
 
 &prompt.root; <userinput>kadmin -l</userinput>
 kadmin> <userinput>init EXAMPLE.ORG</userinput>
 Realm max ticket life [unlimited]:
 kadmin> <userinput>add tillman</userinput>
 Max ticket life [unlimited]:
 Max renewable life [unlimited]:
 Attributes []:
 Password: <userinput>xxxxxxxx</userinput>
 Verifying password - Password: <userinput>xxxxxxxx</userinput></screen>
 
       <para>Now it is time to start up the <acronym>KDC</acronym> services.
 	Run <command>/etc/rc.d/kerberos start</command> and
 	<command>/etc/rc.d/kadmind start</command> to bring up the
 	services.  Note that you will not have any kerberized daemons running
 	at this point but you should be able to confirm the that the
 	<acronym>KDC</acronym> is functioning by obtaining and listing a
 	ticket for the principal (user) that you just created from the
 	command-line of the <acronym>KDC</acronym> itself:</para>
 
       <screen>&prompt.user; <userinput>k5init <replaceable>tillman</replaceable></userinput>
 tillman@EXAMPLE.ORG's Password:
 
 &prompt.user; <userinput>k5list</userinput>
 Credentials cache: FILE:<filename>/tmp/krb5cc_500</filename>
 	Principal: tillman@EXAMPLE.ORG
 
   Issued           Expires          Principal
 Aug 27 15:37:58  Aug 28 01:37:58  krbtgt/EXAMPLE.ORG@EXAMPLE.ORG</screen>
 
       </sect2>
 
       <sect2>
 	<title><application>Kerberos</application> enabling a server with
 	  Heimdal services</title>
 
         <indexterm>
 	  <primary>Kerberos5</primary>
 	  <secondary>enabling services</secondary>
         </indexterm>
 
 	<para>First, we need a copy of the <application>Kerberos</application>
 	  configuration file, <filename>/etc/krb5.conf</filename>.  To do
 	  so, simply copy it over to the client computer from the
 	  <acronym>KDC</acronym> in a secure fashion (using network utilities,
 	  such as &man.scp.1;, or physically via a
 	  floppy disk).</para>
 
 	<para>Next you need a <filename>/etc/krb5.keytab</filename> file.
 	  This is the major difference between a server providing
 	  <application>Kerberos</application> enabled daemons and a
 	  workstation &mdash; the server must have a
 	  <filename>keytab</filename> file.  This file
 	  contains the servers host key, which allows it and the
 	  <acronym>KDC</acronym> to verify each others identity.  It
 	  must be transmitted to the server in a secure fashion, as the
 	  security of the server can be broken if the key is made public.
 	  This explicitly means that transferring it via a clear text
 	  channel, such as <acronym>FTP</acronym>, is a very bad idea.</para>
 
 	<para>Typically, you transfer to the <filename>keytab</filename>
 	  to the server using the <command>kadmin</command> program.
 	  This is handy because you also need to create the host principal
 	  (the <acronym>KDC</acronym> end of the
 	  <filename>krb5.keytab</filename>) using
 	  <command>kadmin</command>.</para>
 
 	<para>Note that you must have already obtained a ticket and that this
 	  ticket must be allowed to use the <command>kadmin</command>
 	  interface in the <filename>kadmind.acl</filename>.  See the section
 	  titled <quote>Remote administration</quote> in the Heimdal info
 	  pages (<command>info heimdal</command>) for details on designing
 	  access control lists.  If you do not want to enable remote
 	  <command>kadmin</command> access, you can simply securely connect
 	  to the <acronym>KDC</acronym> (via local console,
 	  &man.ssh.1; or <application>Kerberos</application>
 	  &man.telnet.1;) and perform administration locally
 	  using <command>kadmin -l</command>.</para>
 
 	<para>After installing the <filename>/etc/krb5.conf</filename> file,
 	  you can use <command>kadmin</command> from the
 	  <application>Kerberos</application> server.  The
 	  <command>add --random-key</command> command will let you add the
 	  servers host principal, and the <command>ext</command> command
 	  will allow you to extract the servers host principal to its own
 	  keytab.  For example:</para>
 
 	<screen>&prompt.root; <userinput>kadmin</userinput>
 kadmin><userinput> add --random-key host/myserver.example.org</userinput>
 Max ticket life [unlimited]:
 Max renewable life [unlimited]:
 Attributes []:
 kadmin><userinput> ext host/myserver.example.org</userinput>
 kadmin><userinput> exit</userinput></screen>
 
 	<para>Note that the <command>ext</command> command (short for
 	  <quote>extract</quote>) stores the extracted key in
 	  <filename>/etc/krb5.keytab</filename> by default.</para>
 
 	<para>If you do not have <command>kadmind</command> running on the
 	  <acronym>KDC</acronym> (possibly for security reasons) and thus
 	  do not have access to <command>kadmin</command> remotely, you
 	  can add the host principal
 	  (<username>host/myserver.EXAMPLE.ORG</username>) directly on the
 	  <acronym>KDC</acronym> and then extract it to a temporary file
 	  (to avoid over-writing the <filename>/etc/krb5.keytab</filename>
 	  on the <acronym>KDC</acronym>) using something like this:</para>
 
 	<screen>&prompt.root; <userinput>kadmin</userinput>
 kadmin><userinput> ext --keytab=/tmp/example.keytab host/myserver.example.org</userinput>
 kadmin><userinput> exit</userinput></screen>
 
 	<para>You can then securely copy the keytab to the server
 	  computer (using <command>scp</command> or a floppy, for
 	  example).  Be sure to specify a non-default keytab name
 	  to avoid over-writing the keytab on the
 	  <acronym>KDC</acronym>.</para>
 
 	<para>At this point your server can communicate with the
 	  <acronym>KDC</acronym> (due to its <filename>krb5.conf</filename>
 	  file) and it can prove its own identity (due to the
 	  <filename>krb5.keytab</filename> file).  It is now ready for
 	  you to enable some <application>Kerberos</application> services.
 	  For this example we will enable the <command>telnet</command>
 	  service by putting a line like this into your
 	  <filename>/etc/inetd.conf</filename> and then restarting the
 	  &man.inetd.8; service with
 	  <command>/etc/rc.d/inetd restart</command>:</para>
 
 	<programlisting>telnet    stream  tcp     nowait  root    /usr/libexec/telnetd  telnetd -a user</programlisting>
 
 	<para>The critical bit is that the <command>-a</command>
 	  (for authentication) type is set to user.  Consult the
 	  &man.telnetd.8; manual page for more details.</para>
 
       </sect2>
 
       <sect2>
 	<title><application>Kerberos</application> enabling a client with Heimdal</title>
 
 	<indexterm>
 	  <primary>Kerberos5</primary>
 	  <secondary>configure clients</secondary>
 	</indexterm>
 
 	<para>Setting up a client computer is almost trivially easy.  As
 	  far as <application>Kerberos</application> configuration goes,
 	  you only need the <application>Kerberos</application>
 	  configuration file, located at <filename>/etc/krb5.conf</filename>.
 	  Simply securely copy it over to the client computer from the
 	  <acronym>KDC</acronym>.</para>
 
 	<para>Test your client computer by attempting to use
 	  <command>kinit</command>, <command>klist</command>, and
 	  <command>kdestroy</command> from the client to obtain, show, and
 	  then delete a ticket for the principal you created above.  You
 	  should also be able to use <application>Kerberos</application>
 	  applications to connect to <application>Kerberos</application>
 	  enabled servers, though if that does not work and obtaining a
 	  ticket does the problem is likely with the server and not with
 	  the client or the <acronym>KDC</acronym>.</para>
 
 	<para>When testing an application like <command>telnet</command>,
 	  try using a packet sniffer (such as &man.tcpdump.1;)
 	  to confirm that your password is not sent in the clear.  Try
 	  using <command>telnet</command> with the <literal>-x</literal>
 	  option, which encrypts the entire data stream (similar to
 	  <command>ssh</command>).</para>
 
 	<para>The core <application>Kerberos</application> client applications
 	  (traditionally named <command>kinit</command>,
 	  <command>klist</command>, <command>kdestroy</command>, and
 	  <command>kpasswd</command>) are installed in
 	  the base &os; install. Note that &os; versions prior to 5.0
 	  renamed them to <command>k5init</command>,
 	  <command>k5list</command>, <command>k5destroy</command>,
 	  <command>k5passwd</command>, and <command>k5stash</command>
 	  (though it is typically only used once).</para>
 
 	<para>Various non-core <application>Kerberos</application> client
 	  applications are also installed by default.  This is where the
 	  <quote>minimal</quote> nature of the base Heimdal installation is
 	  felt: <command>telnet</command> is the only
 	  <application>Kerberos</application> enabled service.</para>
 
 	<para>The Heimdal port adds some of the missing client applications:
 	  <application>Kerberos</application> enabled versions of
 	  <command>ftp</command>, <command>rsh</command>,
 	  <command>rcp</command>, <command>rlogin</command>, and a few
 	  other less common programs. The <acronym>MIT</acronym> port also
 	  contains a full suite of <application>Kerberos</application>
 	  client applications.</para>
 
       </sect2>
 
       <sect2>
 	<title>User configuration files: <filename>.k5login</filename> and <filename>.k5users</filename></title>
 
 	<indexterm>
 	  <primary><filename>.k5login</filename></primary>
 	</indexterm>
 
 	<indexterm>
 	  <primary><filename>.k5users</filename></primary>
 	</indexterm>
 
 	<para>Users within a realm typically have their
 	  <application>Kerberos</application> principal (such as
 	  <username>tillman@EXAMPLE.ORG</username>) mapped to a local
 	  user account (such as a local account named
 	  <username>tillman</username>).  Client applications such as
 	  <command>telnet</command> usually do not require a user name
 	  or a principal.</para>
 
 	<para>Occasionally, however, you want to grant access to a local
 	  user account to someone who does not have a matching
 	  <application>Kerberos</application> principal.  For example,
 	  <username>tillman@EXAMPLE.ORG</username> may need access to the
 	  local user account <username>webdevelopers</username>.  Other
 	  principals may also need access to that local account.</para>
 
 	<para>The <filename>.k5login</filename> and
 	  <filename>.k5users</filename> files, placed in a users home
 	  directory, can be used similar to a powerful combination of
 	  <filename>.hosts</filename> and <filename>.rhosts</filename>,
 	  solving this problem. For example, if a
 	  <filename>.k5login</filename> with the following
 	  contents:</para>
 
 	<screen>tillman@example.org
 jdoe@example.org</screen>
 
 	<para>Were to be placed into the home directory of the local user
 	  <username>webdevelopers</username> then both principals listed
 	  would have access to that account without requiring a shared
 	  password.</para>
 
 	<para>Reading the manual pages for these commands is recommended.
 	  Note that the <command>ksu</command> manual page covers
 	  <filename>.k5users</filename>.</para>
 
       </sect2>
 
       <sect2>
 	<title><application>Kerberos</application> Tips, Tricks, and Troubleshooting</title>
 
 	<indexterm>
 	  <primary>Kerberos5</primary>
 	  <secondary>troubleshooting</secondary>
 	</indexterm>
 
 	<itemizedlist>
 	  <listitem>
 	    <para>When using either the Heimdal or <acronym>MIT</acronym>
 	      <application>Kerberos</application> ports ensure that your
 	      <envar>PATH</envar> environment variable lists the
 	      <application>Kerberos</application> versions of the client
 	      applications before the system versions.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>Do all the computers in your realm have synchronized
 	      time settings?  If not, authentication may fail.
 	      <xref linkend="network-ntp"> describes how to synchronize
 	      clocks using <acronym>NTP</acronym>.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para><acronym>MIT</acronym> and Heimdal inter-operate nicely.
 	      Except for <command>kadmin</command>, the protocol for
 	      which is not standardized.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>If you change your hostname, you also need to change your
 	      <username>host/</username> principal and update your keytab.
 	      This also applies to special keytab entries like the
 	      <username>www/</username> principal used for Apache's
 	      <filename role="package">www/mod_auth_kerb</filename>.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>All hosts in your realm must be resolvable (both forwards
 	      and reverse) in <acronym>DNS</acronym> (or
 	      <filename>/etc/hosts</filename> as a minimum).  CNAMEs
 	      will work, but the A and PTR records must be correct and in
 	      place. The error message is not very intuitive:
 	      <errorname>Kerberos5 refuses authentication because Read req
 	      failed: Key table entry not found</errorname>.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>Some operating systems that may being acting as clients
 	      to your <acronym>KDC</acronym> do not set the permissions
 	      for <command>ksu</command> to be setuid
 	      <username>root</username>.  This means that
 	      <command>ksu</command> does not work, which is a good
 	      security idea but annoying. This is not a
 	      <acronym>KDC</acronym> error.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>With <acronym>MIT</acronym>
 	      <application>Kerberos</application>, if you want to allow a
 	      principal to have a ticket life longer than the default ten
 	      hours, you must use <command>modify_principal</command> in
 	      <command>kadmin</command> to change the maxlife of both the
 	      principal in question and the <username>krbtgt</username>
 	      principal.  Then the principal can use the
 	      <literal>-l</literal> option with <command>kinit</command>
 	      to request a ticket with a longer lifetime.</para>
 	  </listitem>
 
 	  <listitem>
 	    <note><para>If you run a packet sniffer on your
 	      <acronym>KDC</acronym> to add in troubleshooting and then
 	      run <command>kinit</command> from a workstation, you will
 	      notice that your <acronym>TGT</acronym> is sent
 	      immediately upon running <command>kinit</command> &mdash;
 	      even before you type your password!  The explanation is
 	      that the <application>Kerberos</application> server freely
 	      transmits a <acronym>TGT</acronym> (Ticket Granting
 	      Ticket) to any unauthorized request;  however, every
 	      <acronym>TGT</acronym> is encrypted in a key derived from
 	      the user's password.  Therefore, when a user types their
 	      password it is not being sent to the <acronym>KDC</acronym>,
 	      it is being used to decrypt the <acronym>TGT</acronym> that
 	      <command>kinit</command> already obtained. If the decryption
 	      process results in a valid ticket with a valid time stamp,
 	      the user has valid <application>Kerberos</application>
 	      credentials.  These credentials include a session key for
 	      establishing secure communications with the
 	      <application>Kerberos</application> server in the future, as
 	      well as the actual ticket-granting ticket, which is actually
 	      encrypted with the <application>Kerberos</application>
 	      server's own key.  This second layer of encryption is
 	      unknown to the user, but it is what allows the
 	      <application>Kerberos</application> server to verify
 	      the authenticity of each <acronym>TGT</acronym>.</para></note>
 	  </listitem>
 
 	  <listitem>
 	    <para>If you want to use long ticket lifetimes (a week, for
 	      example) and you are using <application>OpenSSH</application>
 	      to connect to the machine where your ticket is stored, make
 	      sure that <application>Kerberos</application>
 	      <option>TicketCleanup</option> is set to <literal>no</literal>
 	      in your <filename>sshd_config</filename> or else your tickets
 	      will be deleted when you log out.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>Remember that host principals can have a longer ticket
 	      lifetime as well.  If your user principal has a lifetime of a
 	      week but the host you are connecting to has a lifetime of nine
 	      hours, you will have an expired host principal in your cache
 	      and the ticket cache will not work as expected.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>When setting up a <filename>krb5.dict</filename> file to
 	    prevent specific bad passwords from being used (the manual page
 	    for <command>kadmind</command> covers this briefly), remember
 	    that it only applies to principals that have a password policy
 	    assigned to them.  The <filename>krb5.dict</filename> files
 	    format is simple: one string per line.  Creating a symbolic
 	    link to <filename>/usr/share/dict/words</filename> might be
 	    useful.</para>
 	  </listitem>
         </itemizedlist>
 
       </sect2>
 
       <sect2>
 	<title>Differences with the <acronym>MIT</acronym> port</title>
 
 	<para>The major difference between the <acronym>MIT</acronym>
 	  and Heimdal installs relates to the <command>kadmin</command>
 	  program which has a different (but equivalent) set of commands
 	  and uses a different protocol.  This has a large implications
 	  if your <acronym>KDC</acronym> is <acronym>MIT</acronym> as you
 	  will not be able to use the Heimdal <command>kadmin</command>
 	  program to administer your <acronym>KDC</acronym> remotely
 	  (or vice versa, for that matter).</para>
 
 	<para>The client applications may also take slightly different
 	  command line options to accomplish the same tasks.  Following
 	  the instructions on the <acronym>MIT</acronym>
 	  <application>Kerberos</application> web site
 	  (<ulink url="http://web.mit.edu/Kerberos/www/"></ulink>)
 	  is recommended. Be careful of path issues: the
 	  <acronym>MIT</acronym> port installs into
 	  <filename>/usr/local/</filename> by default, and the
 	  <quote>normal</quote> system applications may be run instead
 	  of <acronym>MIT</acronym> if your <envar>PATH</envar>
 	  environment variable lists the system directories first.</para>
 
 	<note><para>With the <acronym>MIT</acronym>
 	  <filename role="package">security/krb5</filename> port
 	  that is provided by &os;, be sure to read the
 	  <filename>/usr/local/share/doc/krb5/README.FreeBSD</filename>
 	  file installed by the port if you want to understand why logins
 	  via <command>telnetd</command> and <command>klogind</command>
 	  behave somewhat oddly.  Most importantly, correcting the
 	  <quote>incorrect permissions on cache file</quote> behavior
 	  requires that the <command>login.krb5</command> binary be used
 	  for authentication so that it can properly change ownership for
 	  the forwarded credentials.</para></note>
 
       </sect2>
 
       <sect2>
 	<title>Mitigating limitations found in <application>Kerberos</application></title>
 
 	<indexterm>
 	  <primary>Kerberos5</primary>
 	  <secondary>limitations and shortcomings</secondary>
 	</indexterm>
 
 	<sect3>
 	 <title><application>Kerberos</application> is an all-or-nothing approach</title>
 
 	  <para>Every service enabled on the network must be modified to
 	    work with <application>Kerberos</application> (or be otherwise
 	    secured against network attacks) or else the users credentials
 	    could be stolen and re-used.  An example of this would be
 	    <application>Kerberos</application> enabling all remote shells
 	    (via <command>rsh</command> and <command>telnet</command>, for
 	    example) but not converting the <acronym>POP3</acronym> mail
 	    server which sends passwords in plain text.</para>
 
 	</sect3>
 
 	<sect3>
 	  <title><application>Kerberos</application> is intended for single-user workstations</title>
 
 	  <para>In a multi-user environment,
 	    <application>Kerberos</application> is less secure.
 	    This is because it stores the tickets in the
 	    <filename>/tmp</filename> directory, which is readable by all
 	    users.  If a user is sharing a computer with several other
 	    people simultaneously (i.e. multi-user), it is possible that
 	    the user's tickets can be stolen (copied) by another
 	    user.</para>
 
 	  <para>This can be overcome with the <literal>-c</literal>
 	    filename command-line option or (preferably) the
 	    <envar>KRB5CCNAME</envar> environment variable, but this
 	    is rarely done. In principal, storing the ticket in the users
 	    home directory and using simple file permissions can mitigate
 	    this problem.</para>
 
 	</sect3>
 
 	<sect3>
 	  <title>The KDC is a single point of failure</title>
 
 	  <para>By design, the <acronym>KDC</acronym> must be as secure as
 	    the master password database is contained on it.  The
 	    <acronym>KDC</acronym> should have absolutely no other
 	    services running on it and should be physically secured.  The
 	    danger is high because <application>Kerberos</application>
 	    stores all passwords encrypted with the same key (the
 	    <quote>master</quote> key), which in turn is stored as a file
 	    on the <acronym>KDC</acronym>.</para>
 
 	  <para>As a side note, a compromised master key is not quite as
 	    bad as one might normally fear.  The master key is only used
 	    to encrypt the <application>Kerberos</application> database
 	    and as a seed for the random number generator.  As long as
 	    access to your <acronym>KDC</acronym> is secure, an attacker
 	    cannot do much with the master key.</para>
 
 	  <para>Additionally, if the <acronym>KDC</acronym> is unavailable
 	    (perhaps due to a denial of service attack or network problems)
 	    the network services are unusable as authentication can not be
 	    performed, a recipe for a denial-of-service attack.  This can
 	    alleviated with multiple <acronym>KDC</acronym>s (a single
 	    master and one or more slaves) and with careful implementation
 	    of secondary or fall-back authentication
 	    (<acronym>PAM</acronym> is excellent for this).</para>
 
 	</sect3>
 
 	<sect3>
 	  <title><application>Kerberos</application> Shortcomings</title>
 
 	  <para><application>Kerberos</application> allows users, hosts
 	    and services to authenticate between themselves.  It does not
 	    have a mechanism to authenticate the <acronym>KDC</acronym>
 	    to the users, hosts or services.  This means that a trojanned
 	    <command>kinit</command> (for example) could record all user
 	    names and passwords.  Something like
 	    <filename role="package">security/tripwire</filename> or
 	    other file system integrity checking tools can alleviate
 	    this.</para>
 
 	</sect3>
       </sect2>
 
       <sect2>
 	<title>Resources and further information</title>
 
 	<indexterm>
 	  <primary>Kerberos5</primary>
 	  <secondary>external resources</secondary>
 	</indexterm>
 
 	<itemizedlist>
 	  <listitem>
 	  <para><ulink
 	    url="http://www.faqs.org/faqs/Kerberos-faq/general/preamble.html">
 	    The <application>Kerberos</application> FAQ</ulink></para>
 	</listitem>
 
 	<listitem>
 	  <para><ulink url="http://web.mit.edu/Kerberos/www/dialogue.html">Designing
 	    an Authentication System: a Dialog in Four Scenes</ulink></para>
 	</listitem>
 
 	<listitem>
 	  <para><ulink url="http://www.ietf.org/rfc/rfc1510.txt?number=1510">RFC 1510,
 	    The <application>Kerberos</application> Network Authentication Service
 	    (V5)</ulink></para>
 	</listitem>
 
 	<listitem>
 	  <para><ulink url="http://web.mit.edu/Kerberos/www/"><acronym>MIT</acronym>
 	    <application>Kerberos</application> home page</ulink></para>
 	</listitem>
 
 	<listitem>
 	<para><ulink url="http://www.pdc.kth.se/heimdal/">Heimdal
 	  <application>Kerberos</application> home page</ulink></para>
 	</listitem>
 
 	</itemizedlist>
     </sect2>
   </sect1>
 
   <sect1 id="openssl">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Tom</firstname>
 	  <surname>Rhodes</surname>
 	  <contrib>Written by: </contrib>
 	</author>
       </authorgroup>
     </sect1info>
     <title>OpenSSL</title>
     <indexterm>
       <primary>security</primary>
       <secondary>OpenSSL</secondary>
     </indexterm>
 
     <para>One feature that many users overlook is the
       <application>OpenSSL</application> toolkit included
       in &os;.  <application>OpenSSL</application> provides an
       encryption transport layer on top of the normal communications
       layer; thus allowing it to be intertwined with many network
       applications and services.</para>
 
     <para>Some uses of <application>OpenSSL</application> may include
       encrypted authentication of mail clients, web based transactions
       such as credit card payments and more.  Many ports such as
       <filename role="package">www/apache13-ssl</filename>, and
       <filename role="package">mail/sylpheed-claws</filename>
       will offer compilation support for building with
       <application>OpenSSL</application>.</para>
 
     <note>
       <para>In most cases the Ports Collection will attempt to build
 	the <filename role="package">security/openssl</filename> port
 	unless the <makevar>WITH_OPENSSL_BASE</makevar> make variable
 	is explicitly set to <quote>yes</quote>.</para>
     </note>
 
     <para>The version of <application>OpenSSL</application> included
       in &os; supports Secure Sockets Layer v2/v3 (SSLv2/SSLv3),
       Transport Layer Security v1 (TLSv1) network security protocols
       and can be used as a general cryptographic library.</para>
 
     <note>
       <para>While <application>OpenSSL</application> supports the
 	<acronym>IDEA</acronym> algorithm, it is disabled by default
 	due to United States patents.  To use it, the license should
 	be reviewed and, if the restrictions are acceptable, the
 	<makevar>MAKE_IDEA</makevar> variable must be set in
 	<filename>make.conf</filename>.</para>
     </note>
 
     <para>One of the most common uses of
       <application>OpenSSL</application> is to provide certificates for
       use with software applications.  These certificates ensure
       that the credentials of the company or individual are valid
       and not fraudulent.  If the certificate in question has
       not been verified by one of the several <quote>Certificate Authorities</quote>,
       or <acronym>CA</acronym>s, a warning is usually produced.  A
       Certificate Authority is a company, such as <ulink url="http://www.verisign.com">VeriSign</ulink>, which will
       sign certificates in order to validate credentials of individuals
       or companies.  This process has a cost associated with it and
       is definitely not a requirement for using certificates; however,
       it can put some of the more paranoid users at ease.</para>
 
     <sect2>
       <title>Generating Certificates</title>
 
       <indexterm>
 	<primary>OpenSSL</primary>
 	<secondary>certificate generation</secondary>
       </indexterm>
 
       <para>To generate a certificate, the following command is
 	available:</para>
 
       <screen>&prompt.root; <userinput>openssl req -new -nodes -out req.pem -keyout cert.pem</userinput>
 Generating a 1024 bit RSA private key
 ................++++++
 .......................................++++++
 writing new private key to 'cert.pem'
 -----
 You are about to be asked to enter information that will be incorporated
 into your certificate request.
 What you are about to enter is what is called a Distinguished Name or a DN.
 There are quite a few fields but you can leave some blank
 For some fields there will be a default value,
 If you enter '.', the field will be left blank.
 -----
 Country Name (2 letter code) [AU]:<userinput><replaceable>US</replaceable></userinput>
 State or Province Name (full name) [Some-State]:<userinput><replaceable>PA</replaceable></userinput>
 Locality Name (eg, city) []:<userinput><replaceable>Pittsburgh</replaceable></userinput>
 Organization Name (eg, company) [Internet Widgits Pty Ltd]:<userinput><replaceable>My Company</replaceable></userinput>
 Organizational Unit Name (eg, section) []:<userinput><replaceable>Systems Administrator</replaceable></userinput>
 Common Name (eg, YOUR name) []:<userinput><replaceable>localhost.example.org</replaceable></userinput>
 Email Address []:<userinput><replaceable>trhodes@FreeBSD.org</replaceable></userinput>
 
 Please enter the following 'extra' attributes
 to be sent with your certificate request
 A challenge password []:<userinput><replaceable>SOME PASSWORD</replaceable></userinput>
 An optional company name []:<userinput><replaceable>Another Name</replaceable></userinput></screen>
 
       <para>Notice the response directly after the
 	<quote>Common Name</quote> prompt shows a domain name.
 	This prompt requires a server name to be entered for
 	verification purposes; placing anything	but a domain name
 	would yield a useless certificate.  Other options, for
 	instance expire time, alternate encryption algorithms, etc.
 	are available.  A complete list may be obtained by viewing
 	the &man.openssl.1; manual page.</para>
 
       <para>Two files should now exist in
 	the directory in which the aforementioned command was issued.
 	The certificate request, <filename>req.pem</filename>, may be
 	sent to a certificate authority who will validate the credentials
 	that you entered, sign the request and return the certificate to
 	you.  The second file created will be named <filename>cert.pem</filename>
 	and is the private key for the certificate and should be
 	protected at all costs; if this falls in the hands of others it
 	can be used to impersonate you (or your server).</para>
 
       <para>In cases where a signature from a <acronym>CA</acronym> is
 	not required, a self signed certificate can be created.  First,
 	generate the <acronym>RSA</acronym> key:</para>
 
       <screen>&prompt.root; <userinput>openssl dsaparam -rand -genkey -out <filename>myRSA.key</filename> 1024</userinput></screen>
 	
 	<para>Next, generate the <acronym>CA</acronym> key:</para>
 
       <screen>&prompt.root; <userinput>openssl gendsa -des3 -out <filename>myca.key</filename> <filename>myRSA.key</filename></userinput></screen>
 
       <para>Use this key to create the certificate:</para>
 
       <screen>&prompt.root; <userinput>openssl req -new -x509 -days 365 -key <filename>myca.key</filename> -out <filename>new.crt</filename></userinput></screen>
 
       <para>Two new files should appear in the directory: a certificate
 	authority signature file, <filename>myca.key</filename> and the
 	certificate itself, <filename>new.crt</filename>.  These should
 	be placed in a directory, preferably under
 	<filename class="directory">/etc</filename>, which is readable
 	only by <username>root</username>.  Permissions of 0700 should be fine for this and
 	they can be set with the <command>chmod</command>
 	utility.</para>
     </sect2>
 
     <sect2>
       <title>Using Certificates, an Example</title>
 
       <para>So what can these files do?  A good use would be to
 	encrypt connections to the <application>Sendmail</application>
 	<acronym>MTA</acronym>.  This would dissolve the use of clear
 	text authentication for users who send mail via the local
 	<acronym>MTA</acronym>.</para>
 
       <note>
 	<para>This is not the best use in the world as some
 	  <acronym>MUA</acronym>s will present the user with an
 	  error if they have not installed the certificate locally.
 	  Refer to the documentation included with the software for
 	  more information on certificate installation.</para>
       </note>
 
       <para>The following lines should be placed inside the
 	local <filename>.mc</filename> file:</para>
 
       <programlisting>dnl SSL Options
 define(`confCACERT_PATH',`/etc/certs')dnl
 define(`confCACERT',`/etc/certs/new.crt')dnl
 define(`confSERVER_CERT',`/etc/certs/new.crt')dnl
 define(`confSERVER_KEY',`/etc/certs/myca.key')dnl
 define(`confTLS_SRV_OPTIONS', `V')dnl</programlisting>
 
       <para>Where <filename class="directory">/etc/certs/</filename>
 	is the directory to be used for storing the certificate
 	and key files locally.  The last few requirements are a rebuild
 	of the local <filename>.cf</filename> file.  This is easily
 	achieved by typing <command>make</command>
 	<parameter>install</parameter> within the
 	<filename class="directory">/etc/mail</filename>
 	directory.  Follow that up with <command>make</command>
 	<parameter>restart</parameter> which should start the
 	<application>Sendmail</application> daemon.</para>
 
       <para>If all went well there will be no error messages in the
 	<filename>/var/log/maillog</filename> file and
 	<application>Sendmail</application> will show up in the process
 	list.</para>
 
       <para>For a simple test, simply connect to the mail server
 	using the &man.telnet.1; utility:</para>
 
       <screen>&prompt.root; <userinput>telnet <replaceable>example.com</replaceable> 25</userinput>
 Trying 192.0.34.166...
 Connected to <hostid role="fqdn">example.com</hostid>.
 Escape character is '^]'.
 220 <hostid role="fqdn">example.com</hostid> ESMTP Sendmail 8.12.10/8.12.10; Tue, 31 Aug 2004 03:41:22 -0400 (EDT)
 <userinput>ehlo <replaceable>example.com</replaceable></userinput>
 250-example.com Hello example.com [192.0.34.166], pleased to meet you
 250-ENHANCEDSTATUSCODES
 250-PIPELINING
 250-8BITMIME
 250-SIZE
 250-DSN
 250-ETRN
 250-AUTH LOGIN PLAIN
 250-STARTTLS
 250-DELIVERBY
 250 HELP
 <userinput>quit</userinput>
 221 2.0.0 <hostid role="fqdn">example.com</hostid> closing connection
 Connection closed by foreign host.</screen>
 
       <para>If the <quote>STARTTLS</quote> line appears in the output
 	then everything is working correctly.</para>
     </sect2>
   </sect1>
 
   <sect1 id="ipsec">
     <sect1info>
       <authorgroup>
         <author>
   	  <firstname>Nik</firstname>
 	  <surname>Clayton</surname>
 	  <affiliation>
 	    <address><email>nik@FreeBSD.org</email></address>
           </affiliation>
           <contrib>Written by </contrib>
         </author>
       </authorgroup>
     </sect1info>
 
     <indexterm>
       <primary>IPsec</primary>
     </indexterm>
 
     <title>VPN over IPsec</title>
     <para>Creating a VPN between two networks, separated by the
       Internet, using FreeBSD gateways.</para>
  
     <sect2>
       <sect2info>
         <authorgroup>
           <author>
             <firstname>Hiten M.</firstname>
             <surname>Pandya</surname>
 	    <affiliation>
 	      <address><email>hmp@FreeBSD.org</email></address>
 	    </affiliation>
 	    <contrib>Written by </contrib>
 	  </author>
 	</authorgroup>
       </sect2info>
 
       <title>Understanding IPsec</title>
 
       <para>This section will guide you through the process of setting
 	up IPsec, and to use it in an environment which consists of
 	FreeBSD and <application>&microsoft.windows; 2000/XP</application>
 	machines, to make them communicate securely.  In order to set up
 	IPsec, it is necessary that you are familiar with the concepts
 	of building a custom kernel (see
 	<xref linkend="kernelconfig">).</para>
     
       <para><emphasis>IPsec</emphasis> is a protocol which sits on top
 	of the Internet Protocol (IP) layer.  It allows two or more
 	hosts to communicate in a secure manner (hence the name).  The
 	FreeBSD IPsec <quote>network stack</quote> is based on the
 	<ulink url="http://www.kame.net/">KAME</ulink> implementation,
 	which has support for both protocol families, IPv4 and
 	IPv6.</para>
 
       <note>
         <para>FreeBSD 5.X contains a <quote>hardware
         accelerated</quote> IPsec stack, known as <quote>Fast
         IPsec</quote>, that was obtained from OpenBSD.  It employs
         cryptographic hardware (whenever possible) via the
         &man.crypto.4; subsystem to optimize the performance of IPsec.
         This subsystem is new, and does not support all the features
         that are available in the KAME version of IPsec.  However, in
         order to enable hardware-accelerated IPsec, the following
         kernel option has to be added to your kernel configuration
         file:</para>
 
 	<indexterm>
 	  <primary>kernel options</primary>
 	  <secondary>FAST_IPSEC</secondary>
 	</indexterm>
 
         <screen>
 options	  FAST_IPSEC  # new IPsec (cannot define w/ IPSEC)
         </screen>
 
         <para> Note, that it is not currently possible to use the
 	  <quote>Fast IPsec</quote> subsystem in lue with the KAME
 	  implementation of IPsec.  Consult the &man.fast.ipsec.4;
 	  manual page for more information.</para>
 
       </note>
   
       <indexterm>
 	<primary>IPsec</primary>
 	<secondary>ESP</secondary>
       </indexterm>
   
       <indexterm>
 	<primary>IPsec</primary>
 	<secondary>AH</secondary>
       </indexterm>
 
       <para>IPsec consists of two sub-protocols:</para>
 
       <itemizedlist>
         <listitem>
           <para><emphasis>Encapsulated Security Payload
 	      (ESP)</emphasis>, protects the IP packet data from third
 	    party interference, by encrypting the contents using
 	    symmetric cryptography algorithms (like Blowfish,
 	    3DES).</para>
         </listitem>
         <listitem>
           <para><emphasis>Authentication Header (AH)</emphasis>,
 	    protects the IP packet header from third party interference
 	    and spoofing, by computing a cryptographic checksum and
 	    hashing the IP packet header fields with a secure hashing
 	    function.  This is then followed by an additional header
 	    that contains the hash, to allow the information in the
 	    packet to be authenticated.</para>
         </listitem>
       </itemizedlist>
       
       <para><acronym>ESP</acronym> and <acronym>AH</acronym> can
 	either be used together or separately, depending on the
 	environment.</para>
       
       <indexterm>
 	<primary>VPN</primary>
       </indexterm>
 
       <indexterm>
 	<primary>virtual private network</primary>
 	<see>VPN</see>
       </indexterm>
 
       <para>IPsec can either be used to directly encrypt the traffic
 	between two hosts (known as <emphasis>Transport
 	  Mode</emphasis>); or to build <quote>virtual tunnels</quote>
 	between two subnets, which could be used for secure
 	communication between two corporate networks (known as
 	<emphasis>Tunnel Mode</emphasis>).  The latter is more commonly
 	known as a <emphasis>Virtual Private Network (VPN)</emphasis>.
 	The &man.ipsec.4; manual page should be consulted for detailed
 	information on the IPsec subsystem in FreeBSD.</para>
       
       <para>To add IPsec support to your kernel, add the following
 	options to your kernel configuration file:</para>
 
       <indexterm>
 	<primary>kernel options</primary>
 	<secondary>IPSEC</secondary>
       </indexterm>
 
       <indexterm>
 	<primary>kernel options</primary>
 	<secondary>IPSEC_ESP</secondary>
       </indexterm>
 
       <screen>
 options   IPSEC        #IP security
 options   IPSEC_ESP    #IP security (crypto; define w/ IPSEC)
       </screen>
 
       <indexterm>
 	<primary>kernel options</primary>
 	<secondary>IPSEC_DEBUG</secondary>
       </indexterm>
 
       <para>If IPsec debugging support is desired, the following
 	kernel option should also be added:</para>
 
       <screen>
 options   IPSEC_DEBUG  #debug for IP security
       </screen>
     </sect2>
 
     <sect2>
       <title>The Problem</title>
  
       <para>There is no standard for what constitutes a VPN.  VPNs can
 	be implemented using a number of different technologies, each of
 	which have their own strengths and weaknesses.  This section
 	presents a scenario, and the strategies used for implementing a
 	VPN for this scenario.</para>
     </sect2>
     
     <sect2> 
       <title>The Scenario: Two networks, connected to the Internet, to
         behave as one</title>
       
       <indexterm>
 	<primary>VPN</primary>
 	<secondary>creating</secondary>
       </indexterm>
 
       <para>The premise is as follows:</para>
       
       <itemizedlist>
         <listitem>
           <para>You have at least two sites</para>
         </listitem>
         <listitem>
           <para>Both sites are using IP internally</para>
         </listitem>
         <listitem>
           <para>Both sites are connected to the Internet, through a
             gateway that is running FreeBSD.</para>
         </listitem>
         <listitem>
           <para>The gateway on each network has at least one public IP
             address.</para>
         </listitem>
         <listitem>
           <para>The internal addresses of the two networks can be
             public or private IP addresses, it does not matter.  You can
             be running NAT on the gateway machine if necessary.</para>
         </listitem>
         <listitem>
           <para>The internal IP addresses of the two networks
             <emphasis>do not collide</emphasis>.  While I expect it is
             theoretically possible to use a combination of VPN
             technology and NAT to get this to work, I expect it to be a
             configuration nightmare.</para>
         </listitem>
       </itemizedlist>
       
       <para>If you find that you are trying to connect two networks,
         both of which, internally, use the same private IP address range
         (e.g. both of them use <hostid
         role="ipaddr">192.168.1.x</hostid>), then one of the networks will
         have to be renumbered.</para>
  
       <para>The network topology might look something like this:</para>
  
       <mediaobject>
 	<imageobject>
 	  <imagedata fileref="security/ipsec-network" align="center">
 	</imageobject>
 
 	<textobject>
 <literallayout class="monospaced">Network #1            [ Internal Hosts ]    Private Net, 192.168.1.2-254
                       [   Win9x/NT/2K  ]
                       [      UNIX      ]
                                |
                                |
                         .---[fxp1]---.      Private IP, 192.168.1.1
                         |   FreeBSD  |
                         `---[fxp0]---'      Public IP, A.B.C.D
                                |
                                |
                       -=-=- Internet -=-=-
                                |
                                |
                         .---[fxp0]---.      Public IP, W.X.Y.Z
                         |   FreeBSD  |
                         `---[fxp1]---'      Private IP, 192.168.2.1
                                |
                                |
 Network #2            [ Internal Hosts ]
                       [   Win9x/NT/2K  ]    Private Net, 192.168.2.2-254
                       [      UNIX      ]</literallayout>
 	</textobject>
       </mediaobject>
  
       <para>Notice the two public IP addresses.  I will use the letters to
         refer to them in the rest of this article.  Anywhere you see those
         letters in this article, replace them with your own public IP
         addresses.  Note also that internally, the two gateway
         machines have .1 IP addresses, and that the two networks have
         different private IP addresses (<hostid
         role="ipaddr">192.168.1.x</hostid> and <hostid
         role="ipaddr">192.168.2.x</hostid> respectively).  All the
         machines on the private networks have been configured to use the
         <hostid role="ipaddr">.1</hostid> machine as their default
         gateway.</para>
  
       <para>The intention is that, from a network point of view, each
         network should view the machines on the other network as though
         they were directly attached the same router -- albeit a slightly
         slow router with an occasional tendency to drop packets.</para>
  
       <para>This means that (for example), machine <hostid
         role="ipaddr">192.168.1.20</hostid> should be able to run</para>
  
       <programlisting>ping 192.168.2.34</programlisting>
  
       <para>and have it work, transparently.  &windows; machines should
         be able to see the machines on the other network, browse file
         shares, and so on, in exactly the same way that they can browse
         machines on the local network.</para>
  
       <para>And the whole thing has to be secure.  This means that
         traffic between the two networks has to be encrypted.</para>
  
       <para>Creating a VPN between these two networks is a multi-step
         process.  The stages are as follows:</para>
  
       <orderedlist>
         <listitem>
           <para>Create a <quote>virtual</quote> network link between the two
             networks, across the Internet.  Test it, using tools like
             &man.ping.8;, to make sure it works.</para>
         </listitem>
  
         <listitem>
           <para>Apply security policies to ensure that traffic between
             the two networks is transparently encrypted and decrypted as
             necessary.  Test this, using tools like &man.tcpdump.1;, to
             ensure that traffic is encrypted.</para>
         </listitem>
 
         <listitem>
           <para>Configure additional software on the FreeBSD gateways,
             to allow &windows; machines to see one another across the
             VPN.</para>
         </listitem>
       </orderedlist>
 
     <sect3>
       <title>Step 1: Creating and testing a <quote>virtual</quote>
         network link</title>
  
       <para>Suppose that you were logged in to the gateway machine on
         network #1 (with public IP address <hostid
         role="ipaddr">A.B.C.D</hostid>, private IP address <hostid
         role="ipaddr">192.168.1.1</hostid>), and you ran <command>ping
         192.168.2.1</command>, which is the private address of the machine
         with IP address <hostid role="ipaddr">W.X.Y.Z</hostid>.  What
         needs to happen in order for this to work?</para>
 
       <orderedlist>
         <listitem>
           <para>The gateway machine needs to know how to reach <hostid
             role="ipaddr">192.168.2.1</hostid>.  In other words, it needs
             to have a route to <hostid
             role="ipaddr">192.168.2.1</hostid>.</para>
         </listitem>
         <listitem>
           <para>Private IP addresses, such as those in the <hostid
             role="ipaddr">192.168.x</hostid> range are not supposed to
             appear on the Internet at large.  Instead, each packet you
             send to <hostid role="ipaddr">192.168.2.1</hostid> will need
             to be wrapped up inside another packet.  This packet will need
             to appear to be from <hostid role="ipaddr">A.B.C.D</hostid>,
             and it will have to be sent to <hostid
             role="ipaddr">W.X.Y.Z</hostid>.  This process is called
             <firstterm>encapsulation</firstterm>.</para>
         </listitem>
         <listitem>
           <para>Once this packet arrives at <hostid
             role="ipaddr">W.X.Y.Z</hostid> it will need to
             <quote>unencapsulated</quote>, and delivered to <hostid
             role="ipaddr">192.168.2.1</hostid>.</para>
 	</listitem>
       </orderedlist>
  
       <para>You can think of this as requiring a <quote>tunnel</quote>
         between the two networks.  The two <quote>tunnel mouths</quote> are the IP
         addresses <hostid role="ipaddr">A.B.C.D</hostid> and <hostid
         role="ipaddr">W.X.Y.Z</hostid>, and the tunnel must be told the
         addresses of the private IP addresses that will be allowed to pass
         through it.  The tunnel is used to transfer traffic with private
         IP addresses across the public Internet.</para>
  
       <para>This tunnel is created by using the generic interface, or
         <devicename>gif</devicename> devices on FreeBSD.  As you can
         imagine, the <devicename>gif</devicename> interface on each
         gateway host must be configured with four IP addresses; two for
         the public IP addresses, and two for the private IP
         addresses.</para>
  
       <para>Support for the gif device must be compiled in to the
         &os; kernel on both machines.  You can do this by adding the
         line:</para>
  
       <programlisting>device gif</programlisting>
  
       <para>to the kernel configuration files on both machines, and
         then compile, install, and reboot as normal.</para>
  
       <para>Configuring the tunnel is a two step process.  First the
         tunnel must be told what the outside (or public) IP addresses
         are, using &man.gifconfig.8;.  Then the private IP addresses must be
         configured using &man.ifconfig.8;.</para>
 
       <note>
 	<para>In &os;&nbsp;5.X, the functionality provided by the
 	  &man.gifconfig.8; utility has been merged into 
 	  &man.ifconfig.8;.</para></note>
  
       <para>On the gateway machine on network #1 you would run the
         following two commands to configure the tunnel.</para>
  
       <programlisting>gifconfig gif0 A.B.C.D W.X.Y.Z
 ifconfig gif0 inet 192.168.1.1 192.168.2.1 netmask 0xffffffff
       </programlisting>
  
       <para>On the other gateway machine you run the same commands,
         but with the order of the IP addresses reversed.</para>
  
       <programlisting>gifconfig gif0 W.X.Y.Z A.B.C.D
 ifconfig gif0 inet 192.168.2.1 192.168.1.1 netmask 0xffffffff
       </programlisting>
  
       <para>You can then run:</para>
  
       <programlisting>gifconfig gif0</programlisting>
  
       <para>to see the configuration.  For example, on the network #1
         gateway, you would see this:</para>
  
       <screen>&prompt.root; <userinput>gifconfig gif0</userinput>
 gif0: flags=8011&lt;UP,POINTTOPOINT,MULTICAST&gt; mtu 1280
 inet 192.168.1.1 --&gt; 192.168.2.1 netmask 0xffffffff
 physical address inet A.B.C.D --&gt; W.X.Y.Z
       </screen>
  
       <para>As you can see, a tunnel has been created between the
         physical addresses <hostid role="ipaddr">A.B.C.D</hostid> and
         <hostid role="ipaddr">W.X.Y.Z</hostid>, and the traffic allowed
         through the tunnel is that between <hostid
         role="ipaddr">192.168.1.1</hostid> and <hostid
         role="ipaddr">192.168.2.1</hostid>.</para>
  
       <para>This will also have added an entry to the routing table
         on both machines, which you can examine with the command <command>netstat -rn</command>.
         This output is from the gateway host on network #1.</para>
  
       <screen>&prompt.root; <userinput>netstat -rn</userinput>
 Routing tables
  
 Internet:
 Destination      Gateway       Flags    Refs    Use    Netif  Expire
 ...
 192.168.2.1      192.168.1.1   UH        0        0    gif0
 ...
       </screen>
  
       <para>As the <quote>Flags</quote> value indicates, this is a
         host route, which means that each gateway knows how to reach the
         other gateway, but they do not know how to reach the rest of
         their respective networks.  That problem will be fixed
         shortly.</para>
  
       <para>It is likely that you are running a firewall on both
         machines.  This will need to be circumvented for your VPN
         traffic.  You might want to allow all traffic between both
         networks, or you might want to include firewall rules that
         protect both ends of the VPN from one another.</para>
  
       <para>It greatly simplifies testing if you configure the
         firewall to allow all traffic through the VPN.  You can always
         tighten things up later.  If you are using &man.ipfw.8; on the
         gateway machines then a command like</para>
 
       <programlisting>ipfw add 1 allow ip from any to any via gif0</programlisting>
  
       <para>will allow all traffic between the two end points of the
         VPN, without affecting your other firewall rules.  Obviously
         you will need to run this command on both gateway hosts.</para>
  
       <para>This is sufficient to allow each gateway machine to ping
         the other.  On <hostid role="ipaddr">192.168.1.1</hostid>, you
         should be able to run</para>
  
       <programlisting>ping 192.168.2.1</programlisting>
  
       <para>and get a response, and you should be able to do the same
         thing on the other gateway machine.</para>
  
       <para>However, you will not be able to reach internal machines
         on either network yet.  This is because of the routing --
         although the gateway machines know how to reach one another,
         they do not know how to reach the network behind each one.</para>
  
       <para>To solve this problem you must add a static route on each
         gateway machine.  The command to do this on the first gateway
         would be:</para>
  
       <programlisting>route add 192.168.2.0 192.168.2.1 netmask 0xffffff00
       </programlisting>
  
       <para>This says <quote>In order to reach the hosts on the
         network <hostid role="ipaddr">192.168.2.0</hostid>, send the
         packets to the host <hostid
         role="ipaddr">192.168.2.1</hostid></quote>.  You will need to
         run a similar command on the other gateway, but with the
         <hostid role="ipaddr">192.168.1.x</hostid> addresses
         instead.</para>
  
       <para>IP traffic from hosts on one network will now be able to
         reach hosts on the other network.</para>
  
       <para>That has now created two thirds of a VPN between the two
         networks, in as much as it is <quote>virtual</quote> and it is a
         <quote>network</quote>.  It is not private yet.  You can test
         this using &man.ping.8; and &man.tcpdump.1;.  Log in to the
         gateway host and run</para>
  
       <programlisting>tcpdump dst host 192.168.2.1</programlisting>
 
       <para>In another log in session on the same host run</para>
 
       <programlisting>ping 192.168.2.1</programlisting>
  
       <para>You will see output that looks something like this:</para>
  
       <programlisting>
 16:10:24.018080 192.168.1.1 &gt; 192.168.2.1: icmp: echo request
 16:10:24.018109 192.168.1.1 &gt; 192.168.2.1: icmp: echo reply
 16:10:25.018814 192.168.1.1 &gt; 192.168.2.1: icmp: echo request
 16:10:25.018847 192.168.1.1 &gt; 192.168.2.1: icmp: echo reply
 16:10:26.028896 192.168.1.1 &gt; 192.168.2.1: icmp: echo request
 16:10:26.029112 192.168.1.1 &gt; 192.168.2.1: icmp: echo reply
       </programlisting>
  
       <para>As you can see, the ICMP messages are going back and forth
         unencrypted.  If you had used the <option>-s</option> parameter to
         &man.tcpdump.1; to grab more bytes of data from the packets you
         would see more information.</para>
  
       <para>Obviously this is unacceptable.  The next section will
         discuss securing the link between the two networks so that it
         all traffic is automatically encrypted.</para>
  
       <itemizedlist>
         <title>Summary:</title>
         <listitem>
           <para>Configure both kernels with <quote>pseudo-device
           gif</quote>.</para>
         </listitem>
         <listitem>
           <para>Edit <filename>/etc/rc.conf</filename> on gateway host
             #1 and add the following lines (replacing IP addresses as
             necessary).</para>
           <programlisting>gifconfig_gif0="A.B.C.D W.X.Y.Z"
 ifconfig_gif0="inet 192.168.1.1 192.168.2.1 netmask 0xffffffff"
 static_routes="vpn"
 route_vpn="192.168.2.0 192.168.2.1 netmask 0xffffff00"
           </programlisting>
         </listitem>
 
         <listitem>
           <para>Edit your firewall script
           (<filename>/etc/rc.firewall</filename>, or similar) on both
           hosts, and add</para>
 
           <programlisting>ipfw add 1 allow ip from any to any via gif0</programlisting>
         </listitem>
         <listitem>
           <para>Make similar changes to
             <filename>/etc/rc.conf</filename> on gateway host #2,
             reversing the order of IP addresses.</para>
         </listitem>
       </itemizedlist>
     </sect3>
 
     <sect3>
       <title>Step 2: Securing the link</title>
  
       <para>To secure the link we will be using IPsec.  IPsec provides
         a mechanism for two hosts to agree on an encryption key, and to
         then use this key in order to encrypt data between the two
         hosts.</para>
  
       <para>The are two areas of configuration to be considered here.</para>
  
       <orderedlist>
         <listitem>
           <para>There must be a mechanism for two hosts to agree on the
             encryption mechanism to use.  Once two hosts have agreed on
             this mechanism there is said to be a <quote>security association</quote>
             between them.</para>
         </listitem>
         <listitem>
           <para>There must be a mechanism for specifying which traffic
             should be encrypted.  Obviously, you do not want to encrypt
             all your outgoing traffic -- you only want to encrypt the
             traffic that is part of the VPN.  The rules that you put in
             place to determine what traffic will be encrypted are called
             <quote>security policies</quote>.</para>
          </listitem>
        </orderedlist>
  
        <para>Security associations and security policies are both
          maintained by the kernel, and can be modified by userland
          programs.  However, before you can do this you must configure the
          kernel to support IPsec and the Encapsulated Security Payload
          (ESP) protocol.  This is done by configuring a kernel with:</para>
  
        <indexterm>
 	 <primary>kernel options</primary>
 	 <secondary>IPSEC</secondary>
        </indexterm>
 
        <programlisting>options IPSEC
 options IPSEC_ESP
        </programlisting>
  
        <para>and recompiling, reinstalling, and rebooting.  As before
          you will need to do this to the kernels on both of the gateway
          hosts.</para>
  
        <indexterm>
 	 <primary>IKE</primary>
        </indexterm>
 
        <para>You have two choices when it comes to setting up security
          associations.  You can configure them by hand between two hosts,
          which entails choosing the encryption algorithm, encryption keys,
          and so forth, or you can use daemons that implement the Internet
          Key Exchange protocol (IKE) to do this for you.</para>
  
        <para>I recommend the latter.  Apart from anything else, it is
          easier to set up.</para>
  
        <indexterm>
 	 <primary>IPsec</primary>
 	 <secondary>security policies</secondary>
        </indexterm>
 
        <indexterm>
 	 <primary><command>setkey</command></primary>
        </indexterm>
 
        <para>Editing and displaying security policies is carried out
          using &man.setkey.8;.  By analogy, <command>setkey</command> is
          to the kernel's security policy tables as &man.route.8; is to
          the kernel's routing tables.  <command>setkey</command> can
          also display the current security associations, and to continue
          the analogy further, is akin to <command>netstat -r</command>
          in that respect.</para>
  
        <para>There are a number of choices for daemons to manage
          security associations with FreeBSD.  This article will describe
          how to use one of these, racoon&nbsp;&mdash; which is available from
 	 <filename role="package">security/ipsec-tools</filename> in the &os; Ports
 	 collection.</para>
  
        <indexterm>
 	 <primary>racoon</primary>
        </indexterm>
 
        <para>The <application>racoon</application> software must be run on both gateway hosts.  On each host it
          is configured with the IP address of the other end of the VPN,
          and a secret key (which you choose, and must be the same on both
          gateways).</para>
  
        <para>The two daemons then contact one another, confirm that they
          are who they say they are (by using the secret key that you
          configured).  The daemons then generate a new secret key, and use
          this to encrypt the traffic over the VPN.  They periodically
          change this secret, so that even if an attacker were to crack one
          of the keys (which is as theoretically close to unfeasible as it
          gets) it will not do them much good -- by the time they have cracked
          the key the two daemons have chosen another one.</para>
  
        <para>The configuration file for racoon is stored in
          <filename>${PREFIX}/etc/racoon</filename>.  You should find a
          configuration file there, which should not need to be changed
          too much.  The other component of racoon's configuration,
          which you will need to change, is the <quote>pre-shared
          key</quote>.</para>
  
        <para>The default racoon configuration expects to find this in
          the file <filename>${PREFIX}/etc/racoon/psk.txt</filename>.  It is important to note
          that the pre-shared key is <emphasis>not</emphasis> the key that will be used to
          encrypt your traffic across the VPN link, it is simply a token
          that allows the key management daemons to trust one another.</para>
 
        <para><filename>psk.txt</filename> contains a line for each
          remote site you are dealing with.  In this example, where there
          are two sites, each <filename>psk.txt</filename> file will contain one line (because
          each end of the VPN is only dealing with one other end).</para>
  
        <para>On gateway host #1 this line should look like this:</para>
  
        <programlisting>W.X.Y.Z            secret</programlisting>
  
        <para>That is, the <emphasis>public</emphasis> IP address of the remote end,
          whitespace, and a text string that provides the secret.
          Obviously, you should not use <quote>secret</quote> as your key -- the normal
          rules for choosing a password apply.</para>
  
        <para>On gateway host #2 the line would look like this</para>
  
        <programlisting>A.B.C.D            secret</programlisting>
  
        <para>That is, the public IP address of the remote end, and the
          same secret key.  <filename>psk.txt</filename> must be mode
          <literal>0600</literal> (i.e., only read/write to
          <username>root</username>) before racoon will run.</para>
  
        <para>You must run racoon on both gateway machines.  You will
          also need to add some firewall rules to allow the IKE traffic,
          which is carried over UDP to the ISAKMP (Internet Security Association
          Key Management Protocol) port.  Again, this should be fairly early in
          your firewall ruleset.</para>
  
        <programlisting>ipfw add 1 allow udp from A.B.C.D to W.X.Y.Z isakmp
 ipfw add 1 allow udp from W.X.Y.Z to A.B.C.D isakmp
        </programlisting>
  
        <para>Once racoon is running you can try pinging one gateway host
          from the other.  The connection is still not encrypted, but
          racoon will then set up the security associations between the two
          hosts -- this might take a moment, and you may see this as a
          short delay before the ping commands start responding.</para>
  
        <para>Once the security association has been set up you can
          view it using &man.setkey.8;.  Run</para>
  
        <programlisting>setkey -D</programlisting>
  
        <para>on either host to view the security association information.</para>
  
        <para>That's one half of the problem.  They other half is setting
          your security policies.</para>
  
        <para>To create a sensible security policy, let's review what's
          been set up so far.  This discussions hold for both ends of the
          link.</para>
  
        <para>Each IP packet that you send out has a header that contains
          data about the packet.  The header includes the IP addresses of
          both the source and destination.  As we already know, private IP
          addresses, such as the <hostid role="ipaddr">192.168.x.y</hostid>
          range are not supposed to appear on the public Internet.
          Instead, they must first be encapsulated inside another packet.
          This packet must have the public source and destination IP
          addresses substituted for the private addresses.</para>
  
        <para>So if your outgoing packet started looking like this:</para>
  
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="security/ipsec-out-pkt" align="center">
 	  </imageobject>
 
 	  <textobject>
 	    <literallayout class="monospaced">
   .----------------------.
   | Src: 192.168.1.1     |
   | Dst: 192.168.2.1     |
   | &lt;other header info&gt;  |
   +----------------------+
   | &lt;packet data&gt;        |
   `----------------------'</literallayout>
 	  </textobject>
 	</mediaobject>
  
        <para>Then it will be encapsulated inside another packet, looking
          something like this:</para>
  
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="security/ipsec-encap-pkt" align="center">
 	  </imageobject>
 
 	  <textobject>
 	    <literallayout class="monospaced">
   .--------------------------.
   | Src: A.B.C.D             |
   | Dst: W.X.Y.Z             |
   | &lt;other header info&gt;      |
   +--------------------------+
   | .----------------------. |
   | | Src: 192.168.1.1     | |
   | | Dst: 192.168.2.1     | |
   | | &lt;other header info&gt;  | |
   | +----------------------+ |
   | | &lt;packet data&gt;        | |
   | `----------------------' |
   `--------------------------'</literallayout>
 	  </textobject>
 	</mediaobject>
  
        <para>This encapsulation is carried out by the
          <devicename>gif</devicename> device.  As
          you can see, the packet now has real IP addresses on the outside,
          and our original packet has been wrapped up as data inside the
          packet that will be put out on the Internet.</para>
  
        <para>Obviously, we want all traffic between the VPNs to be
          encrypted.  You might try putting this in to words, as:</para>
 
        <para><quote>If a packet leaves from <hostid
          role="ipaddr">A.B.C.D</hostid>, and it is destined for <hostid
          role="ipaddr">W.X.Y.Z</hostid>, then encrypt it, using the
          necessary security associations.</quote></para>
  
        <para><quote>If a packet arrives from <hostid
          role="ipaddr">W.X.Y.Z</hostid>, and it is destined for <hostid
          role="ipaddr">A.B.C.D</hostid>, then decrypt it, using the
          necessary security associations.</quote></para>
  
        <para>That's close, but not quite right.  If you did this, all
          traffic to and from <hostid role="ipaddr">W.X.Y.Z</hostid>, even
          traffic that was not part of the VPN, would be encrypted.  That's
          not quite what you want.  The correct policy is as follows</para>
  
        <para><quote>If a packet leaves from <hostid
          role="ipaddr">A.B.C.D</hostid>, and that packet is encapsulating
          another packet, and it is destined for <hostid
          role="ipaddr">W.X.Y.Z</hostid>, then encrypt it, using the
          necessary security associations.</quote></para>
  
        <para><quote>If a packet arrives from <hostid
          role="ipaddr">W.X.Y.Z</hostid>, and that packet is encapsulating
          another packet, and it is destined for <hostid
          role="ipaddr">A.B.C.D</hostid>, then decrypt it, using the
          necessary security associations.</quote></para>
  
        <para>A subtle change, but a necessary one.</para>
  
        <para>Security policies are also set using &man.setkey.8;.
          &man.setkey.8; features a configuration language for defining the
          policy.  You can either enter configuration instructions via
          stdin, or you can use the <option>-f</option> option to specify a
          filename that contains configuration instructions.</para>
  
        <para>The configuration on gateway host #1 (which has the public
          IP address <hostid role="ipaddr">A.B.C.D</hostid>) to force all
          outbound traffic to <hostid role="ipaddr">W.X.Y.Z</hostid> to be
          encrypted is:</para>
  
        <programlisting>
 spdadd A.B.C.D/32 W.X.Y.Z/32 ipencap -P out ipsec esp/tunnel/A.B.C.D-W.X.Y.Z/require;
        </programlisting>
  
        <para>Put these commands in a file (e.g.
        <filename>/etc/ipsec.conf</filename>) and then run</para>
 
        <screen>&prompt.root; <userinput>setkey -f /etc/ipsec.conf</userinput></screen>
  
        <para><option>spdadd</option> tells &man.setkey.8; that we want
          to add a rule to the secure policy database.  The rest of this
          line specifies which packets will match this policy.  <hostid
          role="ipaddr">A.B.C.D/32</hostid> and <hostid
          role="ipaddr">W.X.Y.Z/32</hostid> are the IP addresses and
          netmasks that identify the network or hosts that this policy will
          apply to.  In this case, we want it to apply to traffic between
          these two hosts.  <option>ipencap</option> tells the kernel that
          this policy should only apply to packets that encapsulate other
          packets.  <option>-P out</option> says that this policy applies
          to outgoing packets, and <option>ipsec</option> says that the
          packet will be secured.</para>
  
        <para>The second line specifies how this packet will be
          encrypted.  <option>esp</option> is the protocol that will be
          used, while <option>tunnel</option> indicates that the packet
          will be further encapsulated in an IPsec packet.  The repeated
          use of <hostid role="ipaddr">A.B.C.D</hostid> and <hostid
          role="ipaddr">W.X.Y.Z</hostid> is used to select the security
          association to use, and the final <option>require</option>
          mandates that packets must be encrypted if they match this
          rule.</para>
  
        <para>This rule only matches outgoing packets.  You will need a
          similar rule to match incoming packets.</para>
  
        <programlisting>spdadd W.X.Y.Z/32 A.B.C.D/32 ipencap -P in ipsec esp/tunnel/W.X.Y.Z-A.B.C.D/require;</programlisting>
  
        <para>Note the <option>in</option> instead of
          <option>out</option> in this case, and the necessary reversal of
          the IP addresses.</para>
  
        <para>The other gateway host (which has the public IP address
          <hostid role="ipaddr">W.X.Y.Z</hostid>) will need similar rules.</para>
  
        <programlisting>spdadd W.X.Y.Z/32 A.B.C.D/32 ipencap -P out ipsec esp/tunnel/W.X.Y.Z-A.B.C.D/require;
 spdadd A.B.C.D/32 W.X.Y.Z/32 ipencap -P in ipsec esp/tunnel/A.B.C.D-W.X.Y.Z/require;</programlisting>
  
        <para>Finally, you need to add firewall rules to allow ESP and
         IPENCAP packets back and forth.  These rules will need to be
         added to both hosts.</para>
  
        <programlisting>ipfw add 1 allow esp from A.B.C.D to W.X.Y.Z
 ipfw add 1 allow esp from W.X.Y.Z to A.B.C.D
 ipfw add 1 allow ipencap from A.B.C.D to W.X.Y.Z
 ipfw add 1 allow ipencap from W.X.Y.Z to A.B.C.D
        </programlisting>
  
        <para>Because the rules are symmetric you can use the same rules
          on each gateway host.</para>
  
        <para>Outgoing packets will now look something like this:</para>
  
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="security/ipsec-crypt-pkt" align="center">
 	  </imageobject>
 
 	  <textobject>
 	    <literallayout class="monospaced">
   .------------------------------.  --------------------------.
   | Src: A.B.C.D                 |                            |
   | Dst: W.X.Y.Z                 |                            |
   | &lt;other header info&gt;          |                            |  Encrypted
   +------------------------------+                            |  packet.
   | .--------------------------. |  -------------.            |  contents
   | | Src: A.B.C.D             | |               |            |  are
   | | Dst: W.X.Y.Z             | |               |            |  completely
   | | &lt;other header info&gt;      | |               |            |- secure
   | +--------------------------+ |               |  Encap'd   |  from third
   | | .----------------------. | |  -.           |  packet    |  party
   | | | Src: 192.168.1.1     | | |   |  Original |- with real |  snooping
   | | | Dst: 192.168.2.1     | | |   |  packet,  |  IP addr   |
   | | | &lt;other header info&gt;  | | |   |- private  |            |
   | | +----------------------+ | |   |  IP addr  |            |
   | | | &lt;packet data&gt;        | | |   |           |            |
   | | `----------------------' | |  -'           |            |
   | `--------------------------' |  -------------'            |
   `------------------------------'  --------------------------'
 	    </literallayout>
 	  </textobject>
 	</mediaobject>
 
        <para>When they are received by the far end of the VPN they will
          first be decrypted (using the security associations that have
          been negotiated by racoon).  Then they will enter the
          <devicename>gif</devicename> interface, which will unwrap
          the second layer, until you are left with the innermost
          packet, which can then travel in to the inner network.</para>
  
        <para>You can check the security using the same &man.ping.8; test from
          earlier.  First, log in to the
          <hostid role="ipaddr">A.B.C.D</hostid> gateway machine, and
          run:</para>
  
        <programlisting>tcpdump dst host 192.168.2.1</programlisting>
  
        <para>In another log in session on the same host run</para>
  
        <programlisting>ping 192.168.2.1</programlisting>
  
        <para>This time you should see output like the following:</para>
  
        <programlisting>XXX tcpdump output</programlisting>
  
        <para>Now, as you can see, &man.tcpdump.1; shows the ESP packets.  If
          you try to examine them with the <option>-s</option> option you will see
          (apparently) gibberish, because of the encryption.</para>
  
       <para>Congratulations.  You have just set up a VPN between two
         remote sites.</para>
  
       <itemizedlist>
         <title>Summary</title>
         <listitem>
           <para>Configure both kernels with:</para>
  
           <programlisting>options IPSEC
 options IPSEC_ESP
           </programlisting>
         </listitem>
         <listitem>
           <para>Install <filename
             role="package">security/ipsec-tools</filename>.  Edit
             <filename>${PREFIX}/etc/racoon/psk.txt</filename> on both
             gateway hosts, adding an entry for the remote host's IP
             address and a secret key that they both know.  Make sure
             this file is mode 0600.</para>
         </listitem>
         <listitem>
           <para>Add the following lines to
             <filename>/etc/rc.conf</filename> on each host:</para>
  
           <programlisting>ipsec_enable="YES"
 ipsec_file="/etc/ipsec.conf"
           </programlisting>
         </listitem>
         <listitem>
           <para>Create an <filename>/etc/ipsec.conf</filename> on each
             host that contains the necessary spdadd lines.  On gateway
             host #1 this would be:</para>
  
           <programlisting>
 spdadd A.B.C.D/32 W.X.Y.Z/32 ipencap -P out ipsec
   esp/tunnel/A.B.C.D-W.X.Y.Z/require;
 spdadd W.X.Y.Z/32 A.B.C.D/32 ipencap -P in ipsec
   esp/tunnel/W.X.Y.Z-A.B.C.D/require;
 </programlisting>
  
           <para>On gateway host #2 this would be:</para>
  
 <programlisting>
 spdadd W.X.Y.Z/32 A.B.C.D/32 ipencap -P out ipsec
   esp/tunnel/W.X.Y.Z-A.B.C.D/require;
 spdadd A.B.C.D/32 W.X.Y.Z/32 ipencap -P in ipsec
   esp/tunnel/A.B.C.D-W.X.Y.Z/require;
 </programlisting>
         </listitem>
         <listitem>
           <para>Add firewall rules to allow IKE, ESP, and IPENCAP
             traffic to both hosts:</para>
  
           <programlisting>
 ipfw add 1 allow udp from A.B.C.D to W.X.Y.Z isakmp
 ipfw add 1 allow udp from W.X.Y.Z to A.B.C.D isakmp
 ipfw add 1 allow esp from A.B.C.D to W.X.Y.Z
 ipfw add 1 allow esp from W.X.Y.Z to A.B.C.D
 ipfw add 1 allow ipencap from A.B.C.D to W.X.Y.Z
 ipfw add 1 allow ipencap from W.X.Y.Z to A.B.C.D
           </programlisting>
         </listitem>
       </itemizedlist>
 
       <para>The previous two steps should suffice to get the VPN up and
         running.  Machines on each network will be able to refer to one
         another using IP addresses, and all traffic across the link will
         be automatically and securely encrypted.</para>
     </sect3> 
     </sect2> 
   </sect1>
 
   <sect1 id="openssh">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Chern</firstname>
 	  <surname>Lee</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
 	<!-- 21 April 2001 -->
       </authorgroup>
     </sect1info>
 
     <title>OpenSSH</title>
     <indexterm><primary>OpenSSH</primary></indexterm>
     <indexterm>
       <primary>security</primary>
       <secondary>OpenSSH</secondary>
     </indexterm>
 
     <para><application>OpenSSH</application> is a set of network connectivity tools used to
       access remote machines securely.  It can be used as a direct
       replacement for <command>rlogin</command>,
       <command>rsh</command>, <command>rcp</command>, and
       <command>telnet</command>.  Additionally, any other TCP/IP
       connections can be tunneled/forwarded securely through SSH.
       <application>OpenSSH</application> encrypts all traffic to effectively eliminate eavesdropping,
       connection hijacking, and other network-level attacks.</para>
 
     <para><application>OpenSSH</application> is maintained by the OpenBSD project, and is based
       upon SSH v1.2.12 with all the recent bug fixes and updates.  It
       is compatible with both SSH protocols 1 and 2.  <application>OpenSSH</application> has been
       in the base system since FreeBSD&nbsp;4.0.</para>
 
     <sect2>
       <title>Advantages of Using OpenSSH</title>
   
       <para>Normally, when using &man.telnet.1; or &man.rlogin.1;,
         data is sent over the network in an clear, un-encrypted form.
         Network sniffers anywhere in between the client and server can
         steal your user/password information or data transferred in
         your session.  <application>OpenSSH</application> offers a variety of authentication and
         encryption methods to prevent this from happening.</para>
     </sect2>
 
     <sect2>
       <title>Enabling sshd</title>
       <indexterm>
         <primary>OpenSSH</primary>
         <secondary>enabling</secondary>
       </indexterm>
 
       <para>The <application>sshd</application> daemon is enabled by
         default on &os;&nbsp;4.X and is enabled or not during the
         installation by the user of &os;&nbsp;5.X.  To see if it is
         enabled, check the <filename>rc.conf</filename> file for:</para>
       <screen>sshd_enable="YES"</screen>
       <para>This will load &man.sshd.8;, the daemon program for <application>OpenSSH</application>,
 	the next time your system initializes.  Alternatively, you can
 	simply run directly the <application>sshd</application> daemon by typing <command>sshd</command> on the command line.</para>
     </sect2>
 
     <sect2>
       <title>SSH Client</title>
       <indexterm>
         <primary>OpenSSH</primary>
         <secondary>client</secondary>
       </indexterm>
 
       <para>The &man.ssh.1; utility works similarly to 
         &man.rlogin.1;.</para>
 
       <screen>&prompt.root; <userinput>ssh <replaceable>user@example.com</replaceable></userinput>
 Host key not found from the list of known hosts.
 Are you sure you want to continue connecting (yes/no)? <userinput>yes</userinput>
 Host 'example.com' added to the list of known hosts.
 user@example.com's password: <userinput>*******</userinput></screen>
 
       <para>The login will continue just as it would have if a session was
         created using <command>rlogin</command> or
         <command>telnet</command>.  SSH utilizes a key fingerprint
         system for verifying the authenticity of the server when the 
         client connects.  The user is prompted to enter
 	<literal>yes</literal> only when
         connecting for the first time.  Future attempts to login are all
         verified against the saved fingerprint key.  The SSH client
         will alert you if the saved fingerprint differs from the
         received fingerprint on future login attempts.  The fingerprints
         are saved in <filename>~/.ssh/known_hosts</filename>, or
 	<filename>~/.ssh/known_hosts2</filename> for SSH v2
 	fingerprints.</para>
 
       <para>By default, recent versions of the
         <application>OpenSSH</application> servers only accept SSH v2
         connections.  The client will use version 2 if possible and
         will fall back to version 1.  The client can also be forced to
         use one or the other by passing it the <option>-1</option> or
         <option>-2</option> for version 1 or version 2, respectively.
         The version 1 compatability is maintained in the client for
         backwards compatability with older versions.</para>
     </sect2>
     
     <sect2>
       <title>Secure Copy</title>
       <indexterm>
         <primary>OpenSSH</primary>
         <secondary>secure copy</secondary>
       </indexterm>
       <indexterm><primary><command>scp</command></primary></indexterm>
 
       <para>The &man.scp.1; command works similarly to
 	&man.rcp.1;; it copies a file to or from a remote machine,
 	except in a secure fashion.</para>
 
       <screen>&prompt.root; <userinput> scp <replaceable>user@example.com:/COPYRIGHT COPYRIGHT</replaceable></userinput>
 user@example.com's password: <userinput>*******</userinput>
 COPYRIGHT            100% |*****************************|  4735       
 00:00    
 &prompt.root;</screen>
       <para>Since the fingerprint was already saved for this host in the
         previous example, it is verified when using &man.scp.1;
         here.</para>
 
       <para>The arguments passed to &man.scp.1; are similar
 	to &man.cp.1;, with the file or files in the first
 	argument, and the destination in the second.  Since the file is
 	fetched over the network, through SSH, one or more of the file
 	arguments takes on the form
 	<option>user@host:&lt;path_to_remote_file&gt;</option>.</para>
 
     </sect2>
 
     <sect2>
       <title>Configuration</title>
       <indexterm>
         <primary>OpenSSH</primary>
         <secondary>configuration</secondary>
       </indexterm>
 
       <para>The system-wide configuration files for both the
         <application>OpenSSH</application> daemon and client reside
         within the <filename>/etc/ssh</filename> directory.</para>
 
       <para><filename>ssh_config</filename> configures the client 
         settings, while <filename>sshd_config</filename> configures the 
         daemon.</para>
 
       <para>Additionally, the <option>sshd_program</option>
 	(<filename>/usr/sbin/sshd</filename> by default), and
 	<option>sshd_flags</option> <filename>rc.conf</filename>
 	options can provide more levels of configuration.</para>
     </sect2>
 
     <sect2 id="security-ssh-keygen">
       <title>ssh-keygen</title>
 
       <para>Instead of using passwords, &man.ssh-keygen.1; can
         be used to generate DSA or RSA keys to authenticate a user:</para>
 
       <screen>&prompt.user; <userinput>ssh-keygen -t <replaceable>dsa</replaceable></userinput>
 Generating public/private dsa key pair.
 Enter file in which to save the key (/home/user/.ssh/id_dsa):
 Created directory '/home/user/.ssh'.
 Enter passphrase (empty for no passphrase):
 Enter same passphrase again:
 Your identification has been saved in /home/user/.ssh/id_dsa.
 Your public key has been saved in /home/user/.ssh/id_dsa.pub.
 The key fingerprint is:
 bb:48:db:f2:93:57:80:b6:aa:bc:f5:d5:ba:8f:79:17 user@host.example.com
 </screen>
 
       <para>&man.ssh-keygen.1; will create a public and private
         key pair for use in authentication.  The private key is stored in
         <filename>~/.ssh/id_dsa</filename> or
         <filename>~/.ssh/id_rsa</filename>, whereas the public key is
         stored in <filename>~/.ssh/id_dsa.pub</filename> or
         <filename>~/.ssh/id_rsa.pub</filename>, respectively for DSA and
         RSA key types.  The public key must be placed in
         <filename>~/.ssh/authorized_keys</filename> of the remote
         machine in order for the setup to work.  Similarly, RSA version
         1 public keys should be placed in
         <filename>~/.ssh/authorized_keys</filename>.</para>
 
       <para>This will allow connection to the remote machine based upon
         SSH keys instead of passwords.</para>
 
       <para>If a passphrase is used in &man.ssh-keygen.1;, the user
         will be prompted for a password each time in order to use the
         private key.  &man.ssh-agent.1; can alleviate the strain of
         repeatedly entering long passphrases, and is explored in the
         <xref linkend="security-ssh-agent"> section below.</para>
 
       <warning><para>The various options and files can be different
         according to the <application>OpenSSH</application> version
         you have on your system; to avoid problems you should consult
         the &man.ssh-keygen.1; manual page.</para></warning>
     </sect2>
 
     <sect2 id="security-ssh-agent">
       <title>ssh-agent and ssh-add</title>
 
       <para>The &man.ssh-agent.1; and &man.ssh-add.1; utilities provide
         methods for <application>SSH</application> keys to be loaded
         into memory for use, without needing to type the passphrase
         each time.</para>
 
       <para>The &man.ssh-agent.1; utility will handle the authentication
         using the private key(s) that are loaded into it.
         &man.ssh-agent.1; should be used to launch another application.
         At the most basic level, it could spawn a shell or at a more
         advanced level, a window manager.<para>
 
       <para>To use &man.ssh-agent.1; in a shell, first it will need to
         be spawned with a shell as an argument.  Secondly, the
         identity needs to be added by running &man.ssh-add.1; and
         providing it the passphrase for the private key.  Once these
         steps have been completed the user will be able to &man.ssh.1;
         to any host that has the corresponding public key installed.
         For example:</para>
 
       <screen>&prompt.user; ssh-agent <replaceable>csh</replaceable>
 &prompt.user; ssh-add
 Enter passphrase for /home/user/.ssh/id_dsa:
 Identity added: /home/user/.ssh/id_dsa (/home/user/.ssh/id_dsa)
 &prompt.user;</screen>
 
       <para>To use &man.ssh-agent.1; in X11, a call to
         &man.ssh-agent.1; will need to be placed in
         <filename>~/.xinitrc</filename>.  This will provide the
         &man.ssh-agent.1; services to all programs launched in X11.
         An example <filename>~/.xinitrc</filename> file might look
         like this:</para>
 
       <programlisting>exec ssh-agent <replaceable>startxfce4</replaceable></programlisting>
 
       <para>This would launch &man.ssh-agent.1;, which would in turn
         launch <application>XFCE</application>, every time X11 starts.
         Then once that is done and X11 has been restarted so that the
         changes can take effect, simply run &man.ssh-add.1; to load
         all of your SSH keys.</para>
     </sect2>
 
     <sect2 id="security-ssh-tunneling">
       <title>SSH Tunneling</title>
       <indexterm>
         <primary>OpenSSH</primary>
         <secondary>tunneling</secondary>
       </indexterm>
 
       <para><application>OpenSSH</application> has the ability to create a tunnel to encapsulate
         another protocol in an encrypted session.</para>
 
       <para>The following command tells &man.ssh.1; to create a tunnel 
          for <application>telnet</application>:</para>
 
        <screen>&prompt.user; <userinput>ssh -2 -N -f -L <replaceable>5023:localhost:23 user@foo.example.com</replaceable></userinput>
 &prompt.user;</screen>
 
       <para>The <command>ssh</command> command is used with the
 	following options:</para>
 
       <variablelist>
 	<varlistentry>
 	  <term><option>-2</option></term>
 	  
 	  <listitem>
 	    <para>Forces <command>ssh</command> to use version 2 of
 	      the protocol. (Do not use if you are working with older
 	      SSH servers)</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><option>-N</option></term>
 
 	  <listitem>
 	    <para>Indicates no command, or tunnel only.  If omitted,
 	      <command>ssh</command> would initiate a normal
 	      session.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><option>-f</option></term>
 
 	  <listitem>
 	    <para>Forces <command>ssh</command> to run in the
 	      background.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><option>-L</option></term>
 
 	  <listitem>
 	    <para>Indicates a local tunnel in
 	      <replaceable>localport:remotehost:remoteport</replaceable>
 	      fashion.</para>
 	  </listitem>
 	  </varlistentry>
 
 	<varlistentry>
 	  <term><option>user@foo.example.com</option></term>
 
 	  <listitem>
 	    <para>The remote SSH server.</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
 
 
       <para>An SSH tunnel works by creating a listen socket on
 	<hostid>localhost</hostid> on the specified port.
 	It then forwards any connection received
 	on the local host/port via the SSH connection to the specified
 	remote host and port.</para>
 
       <para>In the example, port <replaceable>5023</replaceable> on
 	<hostid>localhost</hostid> is being forwarded to port
 	<replaceable>23</replaceable> on <hostid>localhost</hostid>
 	of the remote machine.  Since <replaceable>23</replaceable> is <application>telnet</application>,
 	this would create a secure <application>telnet</application> session through an SSH tunnel.</para>
 
       <para>This can be used to wrap any number of insecure TCP
         protocols such as SMTP, POP3, FTP, etc.</para>
 
       <example>
 	<title>Using SSH to Create a Secure Tunnel for SMTP</title>
 
         <screen>&prompt.user; <userinput>ssh -2 -N -f -L <replaceable>5025:localhost:25 user@mailserver.example.com</replaceable></userinput>
 user@mailserver.example.com's password: <userinput>*****</userinput>
 &prompt.user; <userinput>telnet localhost 5025</userinput>
 Trying 127.0.0.1...
 Connected to localhost.
 Escape character is '^]'.
 220 mailserver.example.com ESMTP</screen>     
 
         <para>This can be used in conjunction with an
           &man.ssh-keygen.1; and additional user accounts to create a
           more seamless/hassle-free SSH tunneling environment.  Keys
           can be used in place of typing a password, and the tunnels
           can be run as a separate user.</para>
       </example>
 
       <sect3>
 	<title>Practical SSH Tunneling Examples</title>
 
 	<sect4>
 	  <title>Secure Access of a POP3 Server</title>
 
 	  <para>At work, there is an SSH server that accepts
 	    connections from the outside.  On the same office network
 	    resides a mail server running a POP3 server.  The network,
 	    or network path between your home and office may or may not
 	    be completely trustable.  Because of this, you need to check
 	    your e-mail in a secure manner.  The solution is to create
 	    an SSH connection to your office's SSH server, and tunnel
 	    through to the mail server.</para>
 
 	  <screen>&prompt.user; <userinput>ssh -2 -N -f -L <replaceable>2110:mail.example.com:110 user@ssh-server.example.com</replaceable></userinput>
 user@ssh-server.example.com's password: <userinput>******</userinput></screen>
 
 	  <para>When the tunnel is up and running, you can point your
 	    mail client to send POP3 requests to <hostid>localhost</hostid>
 	    port 2110.  A connection here will be forwarded securely across
 	    the tunnel to <hostid>mail.example.com</hostid>.</para>
 	</sect4>
 
 	<sect4>
 	  <title>Bypassing a Draconian Firewall</title>
 
 	  <para>Some network administrators impose extremely draconian
 	    firewall rules, filtering not only incoming connections,
 	    but outgoing connections.  You may be only given access
 	    to contact remote machines on ports 22 and 80 for SSH
 	    and web surfing.</para>
 
 	  <para>You may wish to access another (perhaps non-work
 	    related) service, such as an Ogg Vorbis server to stream
 	    music.  If this Ogg Vorbis server is streaming on some other
 	    port than 22 or 80, you will not be able to access it.</para>
 
 	  <para>The solution is to create an SSH connection to a machine
 	    outside of your network's firewall, and use it to tunnel to
 	    the Ogg Vorbis server.</para>
 
 	  <screen>&prompt.user; <userinput>ssh -2 -N -f -L <replaceable>8888:music.example.com:8000 user@unfirewalled-system.example.org</replaceable></userinput>
 user@unfirewalled-system.example.org's password: <userinput>*******</userinput></screen>
 
 	  <para>Your streaming client can now be pointed to
 	    <hostid>localhost</hostid> port 8888, which will be
 	    forwarded over to <hostid>music.example.com</hostid> port
 	    8000, successfully evading the firewall.</para>
         </sect4>
       </sect3>
     </sect2>
 
     <sect2>
       <title>The <varname>AllowUsers</varname> Users Option</title>
 
       <para>It is often a good idea to limit which users can log in and
         from where.  The <literal>AllowUsers</literal> option is a good
         way to accomplish this.  For example, to only allow the
         <username>root</username> user to log in from
         <hostid role="ipaddr">192.168.1.32</hostid>, something like this
         would be appropriate in the
         <filename>/etc/ssh/sshd_config</filename> file:</para>
 
       <programlisting>AllowUsers root@192.168.1.32</programlisting>
 
       <para>To allow the user <username>admin</username> to log in from
         anywhere, just list the username by itself:</para>
 
       <programlisting>AllowUsers admin</programlisting>
 
       <para>Multiple users should be listed on the same line, like so:</para>
 
       <programlisting>AllowUsers root@192.168.1.32 admin</programlisting>
 
       <note>
         <para>It is important that you list each user that needs to
           log in to this machine; otherwise they will be locked out.</para>
       </note>
 
       <para>After making changes to
          <filename>/etc/ssh/sshd_config</filename> you must tell
          &man.sshd.8; to reload its config files, by running:</para>
 
       <screen>&prompt.root; <userinput>/etc/rc.d/sshd reload</userinput></screen>
     </sect2>
 
     <sect2>
       <title>Further Reading</title>
       <para><ulink url="http://www.openssh.com/">OpenSSH</ulink></para>
       <para>&man.ssh.1; &man.scp.1; &man.ssh-keygen.1; 
         &man.ssh-agent.1; &man.ssh-add.1; &man.ssh.config.5;</para>
       <para>&man.sshd.8; &man.sftp-server.8; &man.sshd.config.5;</para>
     </sect2>
   </sect1>
 
   <sect1 id="fs-acl">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Tom</firstname>
 	  <surname>Rhodes</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
     </sect1info>
     <indexterm>
       <primary>ACL</primary>
     </indexterm>
     <title>File System Access Control Lists</title>
 
     <para>In conjunction with file system enhancements like snapshots, FreeBSD 5.0
       and later offers the security of File System Access Control Lists
       (<acronym>ACLs</acronym>).</para>
 
     <para>Access Control Lists extend the standard &unix;
       permission model in a highly compatible (&posix;.1e) way.  This feature
       permits an administrator to make use of and take advantage of a
       more sophisticated security model.</para>
 
     <para>To enable <acronym>ACL</acronym> support for <acronym>UFS</acronym>
       file systems, the following:</para>
 
     <programlisting>options UFS_ACL</programlisting>
 
     <para>must be compiled into the kernel.  If this option has
       not been compiled in, a warning message will be displayed
       when attempting to mount a file system supporting <acronym>ACLs</acronym>.
       This option is included in the <filename>GENERIC</filename> kernel.
       <acronym>ACLs</acronym> rely on extended attributes being enabled on
       the file system.  Extended attributes are natively supported in the next generation
       &unix; file system, <acronym>UFS2</acronym>.</para>
 
     <note><para>A higher level of administrative overhead is required to
       configure extended attributes on <acronym>UFS1</acronym> than on
       <acronym>UFS2</acronym>.  The performance of extended attributes
       on <acronym>UFS2</acronym> is also substantially higher.  As a
       result, <acronym>UFS2</acronym> is generally recommended in preference
       to <acronym>UFS1</acronym> for use with access control lists.</para></note>
 
     <para><acronym>ACLs</acronym> are enabled by the mount-time administrative
       flag, <option>acls</option>, which may be added to <filename>/etc/fstab</filename>.
       The mount-time flag can also be automatically set in a persistent manner using
       &man.tunefs.8; to modify a superblock <acronym>ACLs</acronym> flag in the
       file system header.  In general, it is preferred to use the superblock flag
       for several reasons:</para>
 
     <itemizedlist>
       <listitem>
 	<para>The mount-time <acronym>ACLs</acronym> flag cannot be changed by a
 	remount (&man.mount.8; <option>-u</option>), only by means of a complete
 	&man.umount.8; and fresh &man.mount.8;.  This means that
 	<acronym>ACLs</acronym> cannot be enabled on the root file system after boot.
 	It also means that you cannot change the disposition of a file system once
 	it is in use.</para>
       </listitem>
 
       <listitem>
 	<para>Setting the superblock flag will cause the file system to always be
 	mounted with <acronym>ACLs</acronym> enabled even if there is not an
 	<filename>fstab</filename> entry or if the devices re-order.  This prevents
 	accidental mounting of the file system without <acronym>ACLs</acronym>
 	enabled, which can result in <acronym>ACLs</acronym> being improperly enforced,
 	and hence security problems.</para>
       </listitem>
     </itemizedlist>
 
     <note><para>We may change the <acronym>ACLs</acronym> behavior to allow the flag to
       be enabled without a complete fresh &man.mount.8;, but we consider it desirable to
       discourage accidental mounting without <acronym>ACLs</acronym> enabled, because you
       can shoot your feet quite nastily if you enable <acronym>ACLs</acronym>, then disable
       them, then re-enable them without flushing the extended attributes.  In general, once
       you have enabled <acronym>ACLs</acronym> on a file system, they should not be disabled,
       as the resulting file protections may not be compatible with those intended by the
       users of the system, and re-enabling <acronym>ACLs</acronym> may re-attach the previous
       <acronym>ACLs</acronym> to files that have since had their permissions changed,
       resulting in other unpredictable behavior.</para></note>
       
     <para>File systems with <acronym>ACLs</acronym> enabled will show a <literal>+</literal>
       (plus) sign in their permission settings when viewed.  For example:</para>
 
     <programlisting>drwx------  2 robert  robert  512 Dec 27 11:54 private
 drwxrwx---+ 2 robert  robert  512 Dec 23 10:57 directory1
 drwxrwx---+ 2 robert  robert  512 Dec 22 10:20 directory2
 drwxrwx---+ 2 robert  robert  512 Dec 27 11:57 directory3
 drwxr-xr-x  2 robert  robert  512 Nov 10 11:54 public_html</programlisting>
 
     <para>Here we see that the <filename>directory1</filename>,
       <filename>directory2</filename>, and <filename>directory3</filename>
       directories are all taking advantage of <acronym>ACLs</acronym>.  The
       <filename>public_html</filename> directory is not.</para>
 
     <sect2>
       <title>Making Use of <acronym>ACL</acronym>s</title>
 
       <para>The file system <acronym>ACL</acronym>s can be viewed by the
 	&man.getfacl.1; utility.  For instance, to view the
 	<acronym>ACL</acronym> settings on the <filename>test</filename>
 	file, one would use the command:</para>
 
       <screen>&prompt.user; <userinput>getfacl <filename>test</filename></userinput>
 	#file:test
 	#owner:1001
 	#group:1001
 	user::rw-
 	group::r--
 	other::r--</screen>
 
       <para>To change the <acronym>ACL</acronym> settings on this file,
 	invoke the &man.setfacl.1; utility.  Observe:</para>
 
       <screen>&prompt.user; <userinput>setfacl -k <filename>test</filename></userinput></screen>
 
       <para>The <option>-k</option> flag will remove all of the
 	currently defined <acronym>ACL</acronym>s from a file or file
 	system.  The more preferable method would be to use
 	<option>-b</option> as it leaves the basic fields required for
 	<acronym>ACL</acronym>s to work.</para>
 
       <screen>&prompt.user; <userinput>setfacl -m u:trhodes:rwx,group:web:r--,o::--- <filename>test</filename></userinput></screen>
 
       <para>In the aforementioned command, the <option>-m</option>
 	option was used to modify the default <acronym>ACL</acronym>
 	entries.  Since there were no pre-defined entries, as they were
 	removed by the previous command, this will restore the default
 	options and assign the options listed.  Take care to notice that
 	if you add a user or group which does not exist on the system,
 	an <errorname>Invalid argument</errorname> error will be printed
 	to <devicename>stdout</devicename>.</para>
     </sect2>
   </sect1>
 
   <sect1 id="security-portaudit">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Tom</firstname>
 	  <surname>Rhodes</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
     </sect1info>
 
     <indexterm>
       <primary>Portaudit</primary>
     </indexterm>
     <title>Monitoring Third Party Security Issues</title>
 
     <para>In recent years, the security world has made many improvements
       to how vulnerability assessment is handled.  The threat of system
       intrusion increases as third party utilities are installed and
       configured for virtually any operating system available
       today.</para>
 
     <para>Vulnerability assessment is a key factor in security, and
       while &os; releases advisories for the base system, doing so
       for every third party utility is beyond the &os; Project's
       capability.  There is a way to mitigate third party
       vulnerabilities and warn administrators of known security
       issues.  A &os; add on utility known as
       <application>Portaudit</application> exists solely for this
       purpose.</para>
 
     <para>The <filename role="port">security/portaudit</filename> port
       polls a database, updated and maintained by the &os; Security
       Team and ports developers, for known security issues.</para>
 
     <para>To begin using <application>Portaudit</application>, one
       must install it from the Ports Collection:</para>
 
     <screen>&prompt.root; <userinput>cd /usr/ports/security/portaudit && make install clean</userinput></screen>
 
     <para>During the install process, the configuration files for
       &man.periodic.8; will be updated, permitting
       <application>Portaudit</application> output in the daily security
       runs.  Ensure the daily security run emails, which are sent to
       <username>root</username>'s email account, are being read.  No
       more configuration will be required here.</para>
 
     <para>After installation, an administrator must update the database
       stored locally in
       <filename role="directory">/var/db/portaudit</filename> by
       invoking the following command:</para>
 
     <screen>&prompt.root; <userinput>portaudit -F</userinput></screen>
 
     <note>
       <para>The database will automatically be updated during the
 	&man.periodic.8; run; thus, the previous command is completely
 	optional.  It is only required for the following
 	examples.</para>
     </note>
 
     <para>To audit the third party utilities installed as part of
       the Ports Collection, an administrator need only run the
       following command:</para>
 
     <screen>&prompt.root; <userinput>portaudit -a</userinput></screen>
 
     <para>An example of output is provided:</para>
 
     <programlisting>Affected package: cups-base-1.1.22.0_1
 Type of problem: cups-base -- HPGL buffer overflow vulnerability.
 Reference: &lt;http://www.FreeBSD.org/ports/portaudit/40a3bca2-6809-11d9-a9e7-0001020eed82.html&gt;
 
 1 problem(s) in your installed packages found.
 
 You are advised to update or deinstall the affected package(s) immediately.</programlisting>
 
     <para>By pointing a web browser to the <acronym>URL</acronym> shown,
       an administrator may obtain more information about the
       vulnerability in question.  This will include versions affected,
       by &os; Port version, along with other web sites which may contain
       security advisories.</para>
 
     <para>In short, <application>Portaudit</application> is a powerful
       utility and extremely useful when coupled with the
       <application>Portupgrade</application> port.</para>
   </sect1>
 
   <sect1 id="security-advisories">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Tom</firstname>
 	  <surname>Rhodes</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
     </sect1info>
     <indexterm>
       <primary>FreeBSD Security Advisories</primary>
     </indexterm>
     <title>&os; Security Advisories</title>
 
     <para>Like many production quality operating systems, &os; publishes
       <quote>Security Advisories</quote>.  These advisories are usually
       mailed to the security lists and noted in the Errata only
       after the appropriate releases have been patched.  This section
       will work to explain what an advisory is, how to understand it,
       and what measures to take in order to patch a system.</para>
 
     <sect2>
       <title>What does an advisory look like?</title>
 
       <para>The &os; security advisories look similar to the one below,
 	taken from the &a.security-notifications.name; mailing list.</para>
 
       <programlisting>=============================================================================
 &os;-SA-XX:XX.UTIL                                     Security Advisory
                                                           The &os; Project
 
 Topic:          denial of service due to some problem<co id="co-topic">
 
 Category:       core<co id="co-category">
 Module:         sys<co id="co-module">
 Announced:      2003-09-23<co id="co-announce">
 Credits:        Person@EMAIL-ADDRESS<co id="co-credit">
 Affects:        All releases of &os;<co id="co-affects">
                 &os; 4-STABLE prior to the correction date
 Corrected:      2003-09-23 16:42:59 UTC (RELENG_4, 4.9-PRERELEASE)
                 2003-09-23 20:08:42 UTC (RELENG_5_1, 5.1-RELEASE-p6)
                 2003-09-23 20:07:06 UTC (RELENG_5_0, 5.0-RELEASE-p15)
                 2003-09-23 16:44:58 UTC (RELENG_4_8, 4.8-RELEASE-p8)
                 2003-09-23 16:47:34 UTC (RELENG_4_7, 4.7-RELEASE-p18)
                 2003-09-23 16:49:46 UTC (RELENG_4_6, 4.6-RELEASE-p21)
                 2003-09-23 16:51:24 UTC (RELENG_4_5, 4.5-RELEASE-p33)
                 2003-09-23 16:52:45 UTC (RELENG_4_4, 4.4-RELEASE-p43)
                 2003-09-23 16:54:39 UTC (RELENG_4_3, 4.3-RELEASE-p39)<co id="co-corrected">
 &os; only:   NO<co id="co-only">
 
 For general information regarding FreeBSD Security Advisories,
 including descriptions of the fields above, security branches, and the
 following sections, please visit
 http://www.FreeBSD.org/security/.
 
 I.   Background<co id="co-backround">
 
 
 II.  Problem Description<co id="co-descript">
 
 
 III. Impact<co id="co-impact">
 
 
 IV.  Workaround<co id="co-workaround">
 
 
 V.   Solution<co id="co-solution">
 
 
 VI.  Correction details<co id="co-details">
 
 
 VII. References<co id="co-ref"></programlisting>
 
 
       <calloutlist>
 	<callout arearefs="co-topic">
 	  <para>The <literal>Topic</literal> field indicates exactly what the problem is.
 	    It is basically an introduction to the current security
 	    advisory and notes the utility with the
 	    vulnerability.</para>
 	</callout>
 
 	<callout arearefs="co-category">
 	  <para>The <literal>Category</literal> refers to the affected part of the system
 	    which may be one of <literal>core</literal>, <literal>contrib</literal>, or <literal>ports</literal>.  The <literal>core</literal>
 	    category means that the vulnerability affects a core
 	    component of the &os; operating system.  The <literal>contrib</literal>
 	    category means that the vulnerability affects software
 	    contributed to the &os; Project, such as
 	    <application>sendmail</application>.  Finally the <literal>ports</literal>
 	    category indicates that the vulnerability affects add on
 	    software available as part of the Ports Collection.</para>
 	</callout>
 
 	<callout arearefs="co-module">
 	  <para>The <literal>Module</literal> field refers to the component location, for
 	    instance <literal>sys</literal>.  In this example, we see that the module,
 	    <literal>sys</literal>, is affected; therefore, this vulnerability
 	    affects a component used within the kernel.</para>
 	</callout>
 
 	<callout arearefs="co-announce">
 	  <para>The <literal>Announced</literal> field reflects the date said security
 	    advisory was published, or announced to the world.  This
 	    means that the security team has verified that the problem
 	    does exist and that a patch has been committed to the &os;
 	    source code repository.</para>
 	</callout>
 
 	<callout arearefs="co-credit">
 	  <para>The <literal>Credits</literal> field gives credit to the individual or
 	    organization who noticed the vulnerability and reported
 	    it.</para>
 	</callout>
 
 	<callout arearefs="co-affects">
 	  <para>The <literal>Affects</literal> field explains which releases of &os; are
 	    affected by this vulnerability.  For the kernel, a quick
 	    look over the output from <command>ident</command> on the
 	    affected files will help in determining the revision.
 	    For ports, the version number is listed after the port name
 	    in <filename>/var/db/pkg</filename>.  If the system does not
 	    sync with the &os; <acronym>CVS</acronym> repository and rebuild
 	    daily, chances are that it is affected.</para>
 	</callout>
 
 	<callout arearefs="co-corrected">
 	  <para>The <literal>Corrected</literal> field indicates the date, time, time
 	    offset, and release that was corrected.</para>
 	</callout>
 
 	<callout arearefs="co-only">
 	  <para>The <literal>&os; only</literal> field indicates whether this vulnerability
 	    affects just &os;, or if it affects other operating systems
 	    as well.</para>
 	</callout>
 
 	<callout arearefs="co-backround">
 	  <para>The <literal>Background</literal> field gives information on exactly what
 	    the affected utility is.  Most of the time this is why
 	    the utility exists in &os;, what it is used for, and a bit
 	    of information on how the utility came to be.</para>
 	</callout>
 
 	<callout arearefs="co-descript">
 	  <para>The <literal>Problem Description</literal> field explains the security hole
 	    in depth.  This can include information on flawed code, or
 	    even how the utility could be maliciously used to open
 	    a security hole.</para>
 	</callout>
 
 	<callout arearefs="co-impact">
 	  <para>The <literal>Impact</literal> field describes what type of impact the
 	    problem could have on a system.  For example, this could
 	    be anything from a denial of service attack, to extra
 	    privileges available to users, or even giving the attacker
 	    superuser access.</para>
 	</callout>
 
 	<callout arearefs="co-workaround">
 	  <para>The <literal>Workaround</literal> field offers a feasible workaround to
 	    system administrators who may be incapable of upgrading
 	    the system.  This may be due to time constraints, network
 	    availability, or a slew of other reasons.  Regardless,
 	    security should not be taken lightly, and an affected system
 	    should either be patched or the security hole workaround
 	    should be implemented.</para>
 	</callout>
 
 	<callout arearefs="co-solution">
 	  <para>The <literal>Solution</literal> field offers instructions on patching the
 	    affected system.  This is a step by step tested and verified
 	    method for getting a system patched and working
 	    securely.</para>
 	</callout>
 
 	<callout arearefs="co-details">
 	  <para>The <literal>Correction Details</literal> field displays the
 	    <acronym>CVS</acronym> branch or release name with the
 	    periods changed to underscore characters.  It also shows
 	    the revision number of the affected files within each
 	    branch.</para>
 	</callout>
 
 	<callout arearefs="co-ref">
 	  <para>The <literal>References</literal> field usually offers sources of other
 	    information.  This can included web <acronym>URL</acronym>s,
 	    books, mailing lists, and newsgroups.</para>
 	</callout>
       </calloutlist>
     </sect2>
   </sect1>
 
   <sect1 id="security-accounting">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Tom</firstname>
 	  <surname>Rhodes</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
     </sect1info>
     <indexterm>
       <primary>Process Accounting</primary>
     </indexterm>
     <title>Process Accounting</title>
 
     <para>Process accounting is a security method in which an
       administrator may keep track of system resources used,
       their allocation among users, provide for system monitoring,
       and minimally track a user's commands.</para>
 
     <para>This indeed has its own positive and negative points.  One of
       the positives is that an intrusion may be narrowed down
       to the point of entry.  A negative is the amount of logs
       generated by process accounting, and the disk space they may
       require.  This section will walk an administrator through
       the basics of process accounting.</para>
 
     <sect2>
       <title>Enable and Utilizing Process Accounting</title>
       <para>Before making use of process accounting, it
 	must be enabled.  To do this, execute the following
 	commands:</para>
 
       <screen>&prompt.root; <userinput>touch <filename>/var/account/acct</filename></userinput>
 
 &prompt.root; <userinput>accton <filename>/var/account/acct</filename></userinput>
 
 &prompt.root; <userinput>echo 'accounting_enable="YES"' &gt;&gt; <filename>/etc/rc.conf</filename></userinput></screen>
 
       <para>Once enabled, accounting will begin to track
 	<acronym>CPU</acronym> stats, commands, etc.  All accounting
 	logs are in a non-human readable format and may be viewed
 	using the &man.sa.8; utility.  If issued without any options,
 	<command>sa</command> will print information relating to the
 	number of per user calls, the total elapsed time in minutes,
 	total <acronym>CPU</acronym> and user time in minutes, average
 	number of I/O operations, etc.</para>
 
       <para>To view information about commands being issued, one
 	would use the &man.lastcomm.1; utility.  The
 	<command>lastcomm</command> may be used to print out commands
 	issued by users on specific &man.ttys.5;, for example:</para>
 
       <screen>&prompt.root; <userinput>lastcomm ls
 	<username>trhodes</username> ttyp1</userinput></screen>
 
       <para>Would print out all known usage of the <command>ls</command>
         by <username>trhodes</username> on the ttyp1 terminal.</para>
 
       <para>Many other useful options exist and are explained in the
 	&man.lastcomm.1;, &man.acct.5; and &man.sa.8; manual
 	pages.</para>
     </sect2>
   </sect1>  
 </chapter>
 
 <!--
      Local Variables:
      mode: sgml
      sgml-declaration: "../chapter.decl"
      sgml-indent-data: t
      sgml-omittag: nil
      sgml-always-quote-attributes: t
      sgml-parent-document: ("../book.sgml" "part" "chapter")
      End:
 -->
diff --git a/zh_TW.Big5/books/handbook/users/chapter.sgml b/zh_TW.Big5/books/handbook/users/chapter.sgml
index 68c3ec3df0..3a3ade6f56 100644
--- a/zh_TW.Big5/books/handbook/users/chapter.sgml
+++ b/zh_TW.Big5/books/handbook/users/chapter.sgml
@@ -1,1118 +1,1110 @@
 <!--
      The FreeBSD Documentation Project
 
      $FreeBSD$
 -->
 
 <chapter id="users">
   <chapterinfo>
     <authorgroup>
       <author>
         <firstname>Neil</firstname>
 	<surname>Blakey-Milner</surname>
 	<contrib>Contributed by </contrib>
       </author>
     </authorgroup>
     <!-- Feb 2000 -->
   </chapterinfo>
 
-  <title>Users and Basic Account Management</title>
+  <title>¨Ï¥ÎªÌ»P°ò¥»±b¸¹ºÞ²z</title>
   
   <sect1 id="users-synopsis">
-    <title>Synopsis</title>
+    <title>·§­z</title>
     
-    <para>FreeBSD allows multiple users to use the computer at the same time.
-      Obviously, only one of those users can be sitting in front of the screen and
-      keyboard at any one time
+    <para>FreeBSD ¤¹³\¦h­Ó¨Ï¥ÎªÌ¦P®É¨Ï¥Î¹q¸£¡C·íµM¡A³o¨Ã¤£¬O«Ü¦h¤H¦P®É§¤¦b¦P¤@¥x¹q¸£«e
       <footnote>
-	<para>Well, unless you hook up multiple terminals, but we will
-	save that for <xref linkend="serialcomms">.</para>
-      </footnote>, but any number of users can log in through the
-      network to get their work done.  To use the system every user must have
-      an account.</para>
+	<para>Well..°£«D±z³s±µ multiple terminals¡A³oºØ±¡ªp§Ú­Ì·|¦b <xref
+ 	  linkend="serialcomms"> Á¿¨ì¡C</para>
+      </footnote>¡A¦Ó¬O¨ä¥L¨Ï¥ÎªÌ¥i¥H³z¹Lºô¸ô¨Ó¨Ï¥Î¦P¤@¥x¹q¸£¥H§¹¦¨¥L­Ìªº¤u§@¡C
+	­n¨Ï¥Î¨t²Îªº¸Ü¡A¨º»ò¨C­Ó¤H³£±o¦³¤@­Ó±b¸¹¡C</para>
     
-    <para>After reading this chapter, you will know:</para>
+    <para>Ū§¹³o³¹¡A±z±N¤F¸Ñ¡G</para>
 
     <itemizedlist>
       <listitem>
-	<para>The differences between the various user accounts on a FreeBSD
-	  system.</para>
+	<para>¦b FreeBSD ¨t²Î¤W¤£¦P±b¸¹¤§¶¡ªº°Ï§O¡C</para>
       </listitem>
 
       <listitem>
-	<para>How to add user accounts.</para>
+	<para>¦p¦ó¼W¥[±b¸¹¡C</para>
       </listitem>
 
       <listitem>
-	<para>How to remove user accounts.</para>
+	<para>¦p¦ó§R°£±b¸¹¡C</para>
       </listitem>
 
       <listitem>
-	<para>How to change account details, such as the user's full name, or
-	preferred shell.</para>
+	<para>¦p¦ó§ó§ï±b¸¹ªº°ò¥»¸ê®Æ¡A¹³¬O±b¸¹¥þ¦W¡A©Î¬O¨Ï¥Îªº shell ºØÃþ¡C</para>
       </listitem>
 
       <listitem>
-	<para>How to set limits on a per-account basis, to control the
-	  resources such as memory and CPU time that accounts and groups of
-	  accounts are allowed to access.</para>
+	<para>¦p¦ó°w¹ï±b¸¹¡B¸s²Õ¨Ó³]­­¡A¤ñ¦p¡G¤¹³\¦s¨ú°O¾ÐÅé©Î CPU ¸ê·½¦h¹èµ¥¡C</para>
       </listitem>
 
       <listitem>
-	<para>How to use groups to make account management easier.</para>
+	<para>¦p¦ó¹B¥Î¸s²Õ¡A¨Ó§ó®e©ö¦aºÞ²z±b¸¹¡C</para>
       </listitem>
     </itemizedlist>
 
-    <para>Before reading this chapter, you should:</para>
+    <para>¦b¾\Ū³o³¹¤§«e¡A±zÀ³·í¤F¸Ñ¡G</para>
 
     <itemizedlist>
       <listitem>
-	<para>Understand the basics of &unix; and FreeBSD (<xref
-	    linkend="basics">).</para>
+	<para>ÁA¸Ñ  &unix; ¤Î FreeBSD (<xref
+	    linkend="basics">)ªº°ò¦·§©À¡C</para>
       </listitem>
     </itemizedlist>
   </sect1>
 
   <sect1 id="users-introduction">
-    <title>Introduction</title>
+    <title>¤¶²Ð</title>
 
-    <para>All access to the system is achieved via accounts, and all
-      processes are run by users, so user and account management are
-      of integral importance on FreeBSD systems.</para>
+    <para>¨t²Îªº©Ò¦³¦s¨ú¬O¸g¥Ñ±b¸¹¨Ó¶i¦æ¡A¦Ó©Ò¦³ªºµ{¦¡ process ¬O¥Ñ¨Ï¥ÎªÌ¨Ó¶i¦æ¡A©Ò¥H
+	¨Ï¥ÎªÌ¤Î±b¸¹ºÞ²z¡A¤D¬O FreeBSD ¨t²Î¤W¤£¥i©Î¯Êªº­«ÂI¡C</para>
 
     <para>Every account on a FreeBSD system has certain information associated
       with it to identify the account.</para>
 
     <variablelist>
       <varlistentry>
 	<term>User name</term>
 
 	<listitem>
 	  <para>The user name as it would be typed at the
 	    <prompt>login:</prompt> prompt.  User names must be unique across
 	    the computer; you may not have two users with the same
 	    user name.  There are a number of rules for creating valid user
 	    names, documented in &man.passwd.5;; you would typically use user
 	    names that consist of eight or fewer all lower case
 	    characters.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>Password</term>
 
 	<listitem>
 	  <para>Each account has a password associated with it.  The password
 	    may be blank, in which case no password will be required to access
 	    the system.  This is normally a very bad idea; every account
 	    should have a password.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>User ID (UID)</term>
 
 	<listitem>
 	  <para>The UID is a number, traditionally from 0 to 65535<footnote id="users-largeuidgid">
 	      <para>It is possible to use UID/GIDs as large as
 		4294967295, but such IDs can cause serious problems
 		with software that makes assumptions about the values
 		of IDs.</para>
 	    </footnote>, used to uniquely identify
 	    the user to the system.  Internally, FreeBSD uses the UID to
 	    identify users&mdash;any FreeBSD commands that allow you to
 	    specify a user name will convert it to the UID before working with
 	    it.  This means that you can have several accounts with different
 	    user names but the same UID.  As far as FreeBSD is concerned these
 	    accounts are one user.  It is unlikely you will ever need to do
 	    this.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>Group ID (GID)</term>
 
 	<listitem>
 	  <para>The GID is a number, traditionally from 0 to 65535<footnoteref linkend="users-largeuidgid">, used to uniquely identify
 	    the primary group that the user belongs to.  Groups are a
 	    mechanism for controlling access to resources based on a user's
 	    GID rather than their UID.  This can significantly reduce the size
 	    of some configuration files.  A user may also be in more than one
 	    group.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>Login class</term>
 
 	<listitem>
 	  <para>Login classes are an extension to the group mechanism that
 	    provide additional flexibility when tailoring the system to
 	    different users.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>Password change time</term>
 
 	<listitem>
 	  <para>By default FreeBSD does not force users to change their
 	    passwords periodically.  You can enforce this on a per-user basis,
 	    forcing some or all of your users to change their passwords after
 	    a certain amount of time has elapsed.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>Account expiry time</term>
 
 	<listitem>
 	  <para>By default FreeBSD does not expire accounts.  If you are
 	    creating accounts that you know have a limited lifespan, for
 	    example, in a school where you have accounts for the students,
 	    then you can specify when the account expires.  After the expiry
 	    time has elapsed the account cannot be used to log in to the
 	    system, although the account's directories and files will
 	    remain.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>User's full name</term>
 
 	<listitem>
 	  <para>The user name uniquely identifies the account to FreeBSD, but
 	    does not necessarily reflect the user's real name.  This
 	    information can be associated with the account.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>Home directory</term>
 
 	<listitem>
 	  <para>The home directory is the full path to a directory on the
 	    system in which the user will start when logging on to the
 	    system.  A common convention is to put all user home directories
 	    under
 	    <filename>/home/<replaceable>username</replaceable></filename>
 	    or <filename>/usr/home/<replaceable>username</replaceable></filename>.
 	    The user would store their personal files in their home directory,
 	    and any directories they may create in there.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>User shell</term>
 
 	<listitem>
 	  <para>The shell provides the default environment users use to
 	    interact with the system.  There are many different kinds of
 	    shells, and experienced users will have their own preferences,
 	    which can be reflected in their account settings.</para>
 	</listitem>
       </varlistentry>
     </variablelist>
 
     <para>There are three main types of accounts: the <link
 	linkend="users-superuser">Superuser</link>, <link
 	linkend="users-system">system users</link>, and <link
 	linkend="users-user">user accounts</link>.  The Superuser
       account, usually called <username>root</username>, is used to
       manage the system with no limitations on privileges.  System
       users run services.  Finally, user accounts are used by real
       people, who log on, read mail, and so forth.</para>
   </sect1>
     
   <sect1 id="users-superuser">
     <title>The Superuser Account</title>
     
     <indexterm>
       <primary>accounts</primary>
       <secondary>superuser (root)</secondary>
     </indexterm>
     <para>The superuser account, usually called
       <username>root</username>, comes preconfigured to facilitate
       system administration, and should not be used for day-to-day
       tasks like sending and receiving mail, general exploration of
       the system, or programming.</para>
       
     <para>This is because the superuser, unlike normal user accounts,
       can operate without limits, and misuse of the superuser account
       may result in spectacular disasters.  User accounts are unable
       to destroy the system by mistake, so it is generally best to use
       normal user accounts whenever possible, unless you especially
       need the extra privilege.</para>
 
     <para>You should always double and triple-check commands you issue
       as the superuser, since an extra space or missing character can
       mean irreparable data loss.</para>
 
     <para>So, the first thing you should do after reading this
       chapter is to create an unprivileged user account for yourself
       for general usage if you have not already.  This applies equally
       whether you are running a multi-user or single-user machine.
       Later in this chapter, we discuss how to create additional
       accounts, and how to change between the normal user and
       superuser.</para>
   </sect1>
     
   <sect1 id="users-system">
     <title>System Accounts</title>
 
     <indexterm>
       <primary>accounts</primary>
       <secondary>system</secondary>
     </indexterm>
     <para>System users are those used to run services such as DNS,
       mail, web servers, and so forth.  The reason for this is
       security; if all services ran as the superuser, they could
       act without restriction.</para>
 
     <indexterm>
       <primary>accounts</primary>
       <secondary><username>daemon</username></secondary>
     </indexterm>
     <indexterm>
       <primary>accounts</primary>
       <secondary><username>operator</username></secondary>
     </indexterm>
     <para>Examples of system users are <username>daemon</username>,
       <username>operator</username>, <username>bind</username> (for
       the Domain Name Service), <username>news</username>, and
       <username>www</username>.</para>
 
     <indexterm>
       <primary>accounts</primary>
       <secondary><username>nobody</username></secondary>
     </indexterm>
     <para><username>nobody</username> is the generic unprivileged
       system user.  However, it is important to keep in mind that the
       more services that use <username>nobody</username>, the more
       files and processes that user will become associated with, and
       hence the more privileged that user becomes.</para>
   </sect1>
 
   <sect1 id="users-user">
     <title>User Accounts</title>
 
     <indexterm>
       <primary>accounts</primary>
       <secondary>user</secondary>
     </indexterm>
     <para>User accounts are the primary means of access for real
       people to the system, and these accounts insulate the user and
       the environment, preventing the users from damaging the system
       or other users, and allowing users to customize their
       environment without affecting others.</para>
 
     <para>Every person accessing your system should have a unique user
       account.  This allows you to find out who is doing what, prevent
       people from clobbering each others' settings or reading each
       others' mail, and so forth.</para>
 
     <para>Each user can set up their own environment to accommodate
       their use of the system, by using alternate shells, editors, key
       bindings, and language.</para>
   </sect1>
 
   <sect1 id="users-modifying">
     <title>Modifying Accounts</title>
 
     <indexterm>
       <primary>accounts</primary>
       <secondary>modifying</secondary>
     </indexterm>
 
     <para>There are a variety of different commands available in the
       &unix; environment to manipulate user accounts.  The most common
       commands are summarized below, followed by more detailed
       examples of their usage.</para>
 
     <informaltable frame="none" pgwide="1">
       <tgroup cols="2">
 	<colspec colwidth="1*">
 	<colspec colwidth="2*">
 
 	<thead>
 	  <row>
 	    <entry>Command</entry>
 	    <entry>Summary</entry>
 	  </row>
 	</thead>
 	<tbody>
 	  <row>
 	    <entry>&man.adduser.8;</entry>
 	    <entry>The recommended command-line application for adding
 	    new users.</entry>
 	  </row>
 	  <row>
 	    <entry>&man.rmuser.8;</entry>
 	    <entry>The recommended command-line application for
 	    removing users.</entry>
 	  </row>
 	  <row>
 	    <entry>&man.chpass.1;</entry>
 	    <entry>A flexible tool to change user database information.</entry>
 	  </row>
 	  <row>
 	    <entry>&man.passwd.1;</entry>
 	    <entry>The simple command-line tool to change user
 	    passwords.</entry>
 	  </row>
 	  <row>
 	    <entry>&man.pw.8;</entry>
 	    <entry>A powerful and flexible tool to modify all aspects
 	    of user accounts.</entry>
 	  </row>
 	</tbody>
       </tgroup>
     </informaltable>
 
     <sect2 id="users-adduser">
       <title><command>adduser</command></title>
 
       <indexterm>
         <primary>accounts</primary>
         <secondary>adding</secondary>
       </indexterm>
       <indexterm>
         <primary><command>adduser</command></primary>
       </indexterm>
       <indexterm>
         <primary><filename class="directory">/usr/share/skel</filename></primary>
       </indexterm>
       <indexterm><primary>skeleton directory</primary></indexterm>
       <para>&man.adduser.8; is a simple program for
 	adding new users.  It creates entries in the system
 	<filename>passwd</filename> and <filename>group</filename>
 	files.  It will also create a home directory for the new user,
 	copy in the default configuration files (<quote>dotfiles</quote>) from
 	<filename>/usr/share/skel</filename>, and can optionally mail
 	the new user a welcome message.</para>
 
       <para>In &os;&nbsp;5.0, &man.adduser.8; was rewritten from a
 	Perl script to a shell script that acts as wrapper around
 	&man.pw.8;, so its usage is slightly different on &os;&nbsp;4.X
 	and &os;&nbsp;5.X.</para>
 
       <para>To create the initial configuration file, use
 	<command>adduser -s -config_create</command>.
 	<footnote>
 	  <para>The <option>-s</option> makes &man.adduser.8;
 	    default to
 	    quiet.  We use <option>-v</option> later when we want to
 	    change defaults.</para>
 	</footnote>
 	Next, we configure &man.adduser.8;
 	defaults, and create our first user account, since using
 	<username>root</username> for normal usage is evil and
 	nasty.</para>
 
       <example>
 	<title>Configuring <command>adduser</command> and adding a
 	  user on &os;&nbsp;4.X</title>
 
 	<screen>&prompt.root; <userinput>adduser -v</userinput>
 Use option ``-silent'' if you don't want to see all warnings and questions.
 Check /etc/shells
 Check /etc/master.passwd
 Check /etc/group
 Enter your default shell: csh date no sh tcsh zsh [sh]: <userinput>zsh</userinput>
 Your default shell is: zsh -&gt; /usr/local/bin/zsh
 Enter your default HOME partition: [/home]:
 Copy dotfiles from: /usr/share/skel no [/usr/share/skel]: 
 Send message from file: /etc/adduser.message no 
 [/etc/adduser.message]: <userinput>no</userinput>
 Do not send message
 Use passwords (y/n) [y]: <userinput>y</userinput>
 
 Write your changes to /etc/adduser.conf? (y/n) [n]: <userinput>y</userinput>
 
 Ok, let's go.
 Don't worry about mistakes. I will give you the chance later to correct any input.
 Enter username [a-z0-9_-]: <userinput>jru</userinput>
 Enter full name []: <userinput>J. Random User</userinput>
 Enter shell csh date no sh tcsh zsh [zsh]: 
 Enter home directory (full path) [/home/jru]: 
 Uid [1001]: 
 Enter login class: default []: 
 Login group jru [jru]: 
 Login group is ``jru''. Invite jru into other groups: guest no 
 [no]: <userinput>wheel</userinput>
 Enter password []: 
 Enter password again []: 
 
 Name:	  jru
 Password: ****
 Fullname: J. Random User
 Uid:	  1001
 Gid:	  1001 (jru)
 Class:	  
 Groups:	  jru wheel
 HOME:     /home/jru
 Shell:	  /usr/local/bin/zsh
 OK? (y/n) [y]: <userinput>y</userinput>
 Added user ``jru''
 Copy files from /usr/share/skel to /home/jru
 Add another user? (y/n) [y]: <userinput>n</userinput>
 Goodbye!
 &prompt.root;</screen>
       </example>
 
       <para>In summary, we changed the default shell to
 	<application>zsh</application> (an additional shell found in
 	the Ports Collection), and turned off the sending of a welcome mail to
 	added users.  We then saved the configuration,
 	created an account for <username>jru</username>, and made
 	sure <username>jru</username> is in <username>wheel</username>
 	group (so that she may assume the role of
 	<username>root</username> with the &man.su.1;
 	command.)</para>
 
       <note>
 	<para>The password you type in is not echoed, nor are asterisks
 	  displayed.  Make sure that you do not mistype the password.
 	  </para>
       </note>
 
       <note>
 	<para>Just use &man.adduser.8; without arguments
 	  from now on, and you will not have to go through changing the
 	  defaults.  If the program asks you to change the defaults,
 	  exit the program, and try the <option>-s</option>
 	  option.</para>
       </note>
 
       <example>
 	<title>Adding a user on &os;&nbsp;5.X</title>
 
 	<screen>&prompt.root; <userinput>adduser</userinput>
 Username: <userinput>jru</userinput>
 Full name: <userinput>J. Random User</userinput>
 Uid (Leave empty for default):
 Login group [jru]:
 Login group is jru. Invite jru into other groups? []: <userinput>wheel</userinput>
 Login class [default]:
 Shell (sh csh tcsh zsh nologin) [sh]: <userinput>zsh</userinput>
 Home directory [/home/jru]:
 Use password-based authentication? [yes]:
 Use an empty password? (yes/no) [no]:
 Use a random password? (yes/no) [no]:
 Enter password:
 Enter password again:
 Lock out the account after creation? [no]:
 Username   : jru
 Password   : ****
 Full Name  : J. Random User
 Uid        : 1001
 Class      :
 Groups     : jru wheel
 Home       : /home/jru
 Shell      : /usr/local/bin/zsh
 Locked     : no
 OK? (yes/no): <userinput>yes</userinput>
 adduser: INFO: Successfully added (jru) to the user database.
 Add another user? (yes/no): <userinput>no</userinput>
 Goodbye!
 &prompt.root;</screen>
       </example>
     </sect2>
 
     <sect2 id="users-rmuser">
       <title><command>rmuser</command></title>
 
       <indexterm><primary><command>rmuser</command></primary></indexterm>
       <indexterm>
         <primary>accounts</primary>
         <secondary>removing</secondary>
       </indexterm>
 
       <para>You can use &man.rmuser.8; to
 	completely remove a user from the system.
 	&man.rmuser.8; performs the following
 	steps:</para>
 
       <procedure>
 	<step>
 	  <para>Removes the user's &man.crontab.1; entry (if
 	    any).</para>
 	</step>
 	<step>
 	  <para>Removes any &man.at.1; jobs belonging to the
 	    user.</para>
 	</step>
 	<step>
 	  <para>Kills all processes owned by the user.</para>
 	</step>
 	<step>
 	  <para>Removes the user from the system's local password
 	    file.</para>
 	</step>
 	<step>
 	  <para>Removes the user's home directory (if it is owned by
 	    the user).</para>
 	</step>
 	<step>
 	  <para>Removes the incoming mail files belonging to the user
 	    from <filename>/var/mail</filename>.</para>
 	</step>
 	<step>
 	  <para>Removes all files owned by the user from temporary
 	    file storage areas such as <filename>/tmp</filename>.</para>
 	</step>
 	<step>
 	  <para>Finally, removes the username from all groups to which
 	    it belongs in <filename>/etc/group</filename>.
 	    
 	    <note>
 	      <para>If a group becomes empty and the group name is the
 		same as the username, the group is removed; this
 		complements the per-user unique groups created by
 		&man.adduser.8;.</para>
 	    </note>
 	  </para>
 	</step>
       </procedure>
 
       <para>&man.rmuser.8; cannot be used to remove
 	superuser accounts, since that is almost always an indication
 	of massive destruction.</para>
 
       <para>By default, an interactive mode is used, which attempts to
 	make sure you know what you are doing.</para>
 
       <example>
 	<title><command>rmuser</command> Interactive Account Removal</title>
 
 	<screen>&prompt.root; <userinput>rmuser jru</userinput>
 Matching password entry:
 jru:*:1001:1001::0:0:J. Random User:/home/jru:/usr/local/bin/zsh
 Is this the entry you wish to remove? <userinput>y</userinput>
 Remove user's home directory (/home/jru)? <userinput>y</userinput>
 Updating password file, updating databases, done.
 Updating group file: trusted (removing group jru -- personal group is empty) done.
 Removing user's incoming mail file /var/mail/jru: done.
 Removing files belonging to jru from /tmp: done.
 Removing files belonging to jru from /var/tmp: done.
 Removing files belonging to jru from /var/tmp/vi.recover: done.
 &prompt.root;</screen>
       </example>
     </sect2>
 
     <sect2 id="users-chpass">
       <title><command>chpass</command></title>
 
       <indexterm><primary><command>chpass</command></primary></indexterm>
       <para>&man.chpass.1; changes user database
 	information such as passwords, shells, and personal
 	information.</para>
 
       <para>Only system administrators, as the superuser, may change
 	other users' information and passwords with 
 	&man.chpass.1;.</para>
 
       <para>When passed no options, aside from an optional username,
 	&man.chpass.1; displays an editor
 	containing user information.  When the user exists from the
 	editor, the user database is updated with the new
 	information.</para>
 
       <note>
 	<para>In &os;&nbsp;5.X, you will be asked for your password
 	 after exiting the editor if you are not the superuser.</para>
       </note>
 
       <example>
 	<title>Interactive <command>chpass</command> by Superuser</title>
 
 	<screen>#Changing user database information for jru.
 Login: jru
 Password: *
 Uid [#]: 1001
 Gid [# or name]: 1001
 Change [month day year]:
 Expire [month day year]:
 Class:
 Home directory: /home/jru
 Shell: /usr/local/bin/zsh
 Full Name: J. Random User
 Office Location:
 Office Phone:
 Home Phone:
 Other information:</screen>
       </example>
 
       <para>The normal user can change only a small subset of this
 	information, and only for themselves.</para>
 
       <example>
 	<title>Interactive <command>chpass</command> by Normal User</title>
 
 	<screen>#Changing user database information for jru.
 Shell: /usr/local/bin/zsh
 Full Name: J. Random User
 Office Location:
 Office Phone:
 Home Phone:
 Other information:</screen>
       </example>
 
       <note>
 	<para>&man.chfn.1; and &man.chsh.1; are
 	  just links to &man.chpass.1;, as 
 	  are &man.ypchpass.1;,
 	  &man.ypchfn.1;, and
 	  &man.ypchsh.1;.  NIS support is automatic, so
 	  specifying the <literal>yp</literal> before the command is
 	  not necessary.  If this is confusing to you, do not worry, NIS will
 	  be covered in <xref linkend="network-servers">.</para>
       </note>
     </sect2>
     <sect2 id="users-passwd">
       <title><command>passwd</command></title>
 
       <indexterm><primary><command>passwd</command></primary></indexterm>
       <indexterm>
         <primary>accounts</primary>
         <secondary>changing password</secondary>
       </indexterm>
       <para>&man.passwd.1; is the usual way to
 	change your own password as a user, or another user's password
 	as the superuser.</para>
 
       <note>
 	<para>To prevent accidental or unauthorized changes, the original
 	  password must be entered before a new password can be set.</para>
       </note>
 
       <example>
 	<title>Changing Your Password</title>
 
 	<screen>&prompt.user; <userinput>passwd</userinput>
 Changing local password for jru.
 Old password:
 New password:
 Retype new password:
 passwd: updating the database...
 passwd: done</screen>
       </example>
 
       <example>
 	<title>Changing Another User's Password as the Superuser</title>
 
         <screen>&prompt.root; <userinput>passwd jru</userinput>
 Changing local password for jru.
 New password:
 Retype new password:
 passwd: updating the database...
 passwd: done</screen>
       </example>
 
       <note>
 	<para>As with &man.chpass.1;,
 	  &man.yppasswd.1; is just a link to
 	  &man.passwd.1;, so NIS works with either
 	  command.</para>
       </note>
     </sect2>
 
 
     <sect2 id="users-pw">
       <title><command>pw</command></title>
       <indexterm><primary><command>pw</command></primary></indexterm>
 
       <para>&man.pw.8; is a command line utility to create, remove,
 	modify, and display users and groups.  It functions as a front
 	end to the system user and group files.  &man.pw.8;
 	has a very powerful set of command line options that make it
 	suitable for use in shell scripts, but new users may find it
 	more complicated than the other commands presented
 	here.</para>
     </sect2>
 
 
   </sect1>
 
   <sect1 id="users-limiting">
-    <title>Limiting Users</title>
+    <title>¹ï±b¸¹ªº¸ê·½¹B¥Î§@­­¨î</title>
 
     <indexterm><primary>limiting users</primary></indexterm>
     <indexterm>
       <primary>accounts</primary>
       <secondary>limiting</secondary>
     </indexterm>
     <para>If you have users, the ability to limit their system use may
       have come to mind.  FreeBSD provides
       several ways an administrator can limit the amount of system
       resources an individual may use.  These limits are
       divided into two sections: disk quotas, and other resource
       limits.</para>
 
     <indexterm><primary>quotas</primary></indexterm>
     <indexterm>
       <primary>limiting users</primary>
       <secondary>quotas</secondary>
     </indexterm>
     <indexterm><primary>disk quotas</primary></indexterm>
     <para>Disk quotas limit disk usage to users, and
       they
       provide a way to quickly check that usage without
       calculating it every time.  Quotas are discussed in <xref
       linkend="quotas">.</para>
 
     <para>The other resource limits include ways to limit the amount of
       CPU, memory, and other resources a user may consume.  These are
       defined using login classes and are discussed here.</para>
 
     <indexterm>
       <primary><filename>/etc/login.conf</filename></primary>
     </indexterm>
     <para>Login classes are defined in
       <filename>/etc/login.conf</filename>.  The precise semantics are
       beyond the scope of this section, but are described in detail in the
       &man.login.conf.5; manual page.  It is sufficient to say that each
       user is assigned to a login class (<literal>default</literal> by
       default), and that each login class has a set of login capabilities
       associated with it.  A login capability is a
       <literal><replaceable>name</replaceable>=<replaceable>value</replaceable></literal>
       pair, where <replaceable>name</replaceable> is a well-known
       identifier and <replaceable>value</replaceable> is an arbitrary
       string processed accordingly depending on the name.  Setting up login
       classes and capabilities is rather straight-forward and is also
       described in &man.login.conf.5;.</para>
       
     <note>
       <para>The system does not read the configuration in
 	<filename>/etc/login.conf</filename> directly, but reads the database
 	file <filename>/etc/login.conf.db</filename>.
 	To generate <filename>/etc/login.conf.db</filename> from
 	<filename>/etc/login.conf</filename>, execute the following
 	command:</para>
 
       <screen>&prompt.root; <userinput>cap_mkdb /etc/login.conf</userinput></screen>
     </note>
 
     <para>Resource limits are different from plain vanilla login
       capabilities in two ways.  First, for every limit, there is a soft
       (current) and hard limit.  A soft limit may be adjusted by the user
       or application, but may be no higher than the hard limit.  The latter
       may be lowered by the user, but never raised.  Second, most resource
       limits apply per process to a specific user, not the user as a whole.
       Note, however, that these differences are mandated by the specific
       handling of the limits, not by the implementation of the login
       capability framework (i.e., they are not <emphasis>really</emphasis>
       a special case of login capabilities).</para>
 
     <para>And so, without further ado, below are the most commonly used
       resource limits (the rest, along with all the other login
       capabilities, may be found in &man.login.conf.5;).</para>
 
     <variablelist>
       <varlistentry>
         <term><literal>coredumpsize</literal></term>
 
 	<listitem>
     <indexterm><primary>coredumpsize</primary></indexterm>
     <indexterm>
       <primary>limiting users</primary>
       <secondary>coredumpsize</secondary>
     </indexterm>
 	  <para>The limit on the size of a core file generated by a program
 	  is, for obvious reasons, subordinate to other limits on disk
 	  usage (e.g., <literal>filesize</literal>, or disk quotas).
 	  Nevertheless, it is often used as a less-severe method of
 	  controlling disk space consumption: since users do not generate
 	  core files themselves, and often do not delete them, setting this
 	  may save them from running out of disk space should a large
 	  program (e.g., <application>emacs</application>) crash.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
         <term><literal>cputime</literal></term>
 
 	<listitem>
     <indexterm><primary>cputime</primary></indexterm>
     <indexterm>
       <primary>limiting users</primary>
       <secondary>cputime</secondary>
     </indexterm>
 	  <para>This is the maximum amount of CPU time a user's process may
 	    consume.  Offending processes will be killed by the kernel.
 
 	    <note>
 	      <para>This is a limit on CPU <emphasis>time</emphasis>
 	        consumed, not percentage of the CPU as displayed in some
 	        fields by &man.top.1; and &man.ps.1;.  A limit on the
 	        latter is, at the time of this writing, not possible, and
 	        would be rather useless: a compiler&mdash;probably a
 	        legitimate task&mdash;can easily use almost 100% of a CPU
 	        for some time.</para>
 	    </note>
 	  </para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
         <term><literal>filesize</literal></term>
 
 	<listitem>
     <indexterm><primary>filesize</primary></indexterm>
     <indexterm>
       <primary>limiting users</primary>
       <secondary>filesize</secondary>
     </indexterm>
 	  <para>This is the maximum size of a file the user may possess.
 	    Unlike <link linkend="quotas">disk quotas</link>, this limit is
 	    enforced on individual files, not the set of all files a user
 	    owns.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
         <term><literal>maxproc</literal></term>
 
 	<listitem>
     <indexterm><primary>maxproc</primary></indexterm>
         <indexterm>
       <primary>limiting users</primary>
       <secondary>maxproc</secondary>
     </indexterm>
 	  <para>This is the maximum number of processes a user may be
 	    running.  This includes foreground and background processes
 	    alike.  For obvious reasons, this may not be larger than the
 	    system limit specified by the <varname>kern.maxproc</varname>
 	    &man.sysctl.8;.  Also note that setting this 
 	    too small may hinder a
 	    user's productivity: it is often useful to be logged in
 	    multiple times or execute pipelines.  Some tasks, such as
 	    compiling a large program, also spawn multiple processes (e.g.,
 	    &man.make.1;, &man.cc.1;, and other intermediate
 	    preprocessors).</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
         <term><literal>memorylocked</literal></term>
 
 	<listitem>
     <indexterm><primary>memorylocked</primary></indexterm>
     <indexterm>
       <primary>limiting users</primary>
       <secondary>memorylocked</secondary>
     </indexterm>
 	  <para>This is the maximum amount a memory a process may have
 	    requested to be locked into main memory (e.g., see
 	    &man.mlock.2;).  Some system-critical programs, such as
             &man.amd.8;, lock into main memory such that in the event
 	    of being swapped out, they do not contribute to
 	    a system's trashing in time of trouble.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
         <term><literal>memoryuse</literal></term>
 
 	<listitem>
     <indexterm><primary>memoryuse</primary></indexterm>
     <indexterm>
       <primary>limiting users</primary>
       <secondary>memoryuse</secondary>
     </indexterm>
 	  <para>This is the maximum amount of memory a process may consume
 	    at any given time.  It includes both core memory and swap
 	    usage.  This is not a catch-all limit for restricting memory
 	    consumption, but it is a good start.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
         <term><literal>openfiles</literal></term>
 
 	<listitem>
     <indexterm><primary>openfiles</primary></indexterm>
     <indexterm>
       <primary>limiting users</primary>
       <secondary>openfiles</secondary>
     </indexterm>
 	  <para>This is the maximum amount of files a process may have
 	    open.  In FreeBSD, files are also used to represent sockets and
 	    IPC channels; thus, be careful not to set this too low.  The
 	    system-wide limit for this is defined by the
 	    <varname>kern.maxfiles</varname> &man.sysctl.8;.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
         <term><literal>sbsize</literal></term>
 
 	<listitem>
     <indexterm><primary>sbsize</primary></indexterm>
     <indexterm>
       <primary>limiting users</primary>
       <secondary>sbsize</secondary>
     </indexterm>
 	  <para>This is the limit on the amount of network memory, and thus
 	    mbufs, a user may consume.  This originated as a response to an
 	    old DoS attack by creating a lot of sockets, but can be
 	    generally used to limit network communications.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
         <term><literal>stacksize</literal></term>
 
 	<listitem>
     <indexterm><primary>stacksize</primary></indexterm>
     <indexterm>
       <primary>limiting users</primary>
       <secondary>stacksize</secondary>
     </indexterm>
 	  <para>This is the maximum size a process' stack may grow to.
 	    This alone is not sufficient to limit the amount of memory a
 	    program may use; consequently, it should be used in conjunction
 	    with other limits.</para>
 	</listitem>
       </varlistentry>
     </variablelist>
 
     <para>There are a few other things to remember when setting resource
       limits.  Following are some general tips, suggestions, and
       miscellaneous comments.</para>
 
     <itemizedlist>
       <listitem>
         <para>Processes started at system startup by
           <filename>/etc/rc</filename> are assigned to the
           <literal>daemon</literal> login class.</para>
       </listitem>
 
       <listitem>
         <para>Although the <filename>/etc/login.conf</filename> that comes
           with the system is a good source of reasonable values for most
           limits, only you, the administrator, can know what is appropriate
           for your system.  Setting a limit too high may open your system
           up to abuse, while setting it too low may put a strain on
           productivity.</para>
       </listitem>
 
       <listitem>
         <para>Users of the X Window System (X11) should probably be granted
 	  more resources than other users.  X11 by itself takes a lot of
 	  resources, but it also encourages users to run more programs
 	  simultaneously.</para>
       </listitem>
 
       <listitem>
         <para>Remember that many limits apply to individual processes, not
           the user as a whole.  For example, setting 
 	  <varname>openfiles</varname> to 50 means
           that each process the user runs may open up to 50 files.  Thus,
           the gross amount of files a user may open is the value of
           <literal>openfiles</literal> multiplied by the value of
           <literal>maxproc</literal>.  This also applies to memory
           consumption.</para>
       </listitem>
     </itemizedlist>
 
     <para>For further information on resource limits and login classes and
       capabilities in general, please consult the relevant manual pages:
       &man.cap.mkdb.1;, &man.getrlimit.2;, &man.login.conf.5;.</para>
   </sect1>
 
   <sect1 id="users-groups">
     <title>Groups</title>
 
     <indexterm><primary>groups</primary></indexterm>
     <indexterm>
       <primary><filename>/etc/groups</filename></primary>
     </indexterm>
     <indexterm>
       <primary>accounts</primary>
       <secondary>groups</secondary>
     </indexterm>
     <para>A group is simply a list of users.  Groups are identified by
       their group name and GID (Group ID).  In FreeBSD (and most other &unix; like
       systems), the two factors the kernel uses to decide whether a process
       is allowed to do something is its user ID and list of groups it
       belongs to.  Unlike a user ID, a process has a list of groups
       associated with it.  You may hear some things refer to the <quote>group ID</quote>
       of a user or process; most of the time, this just means the first
       group in the list.</para>
 
     <para>The group name to group ID map is in
       <filename>/etc/group</filename>.  This is a plain text file with four
       colon-delimited fields.  The first field is the group name, the
       second is the encrypted password, the third the group ID, and the
       fourth the comma-delimited list of members.  It can safely be edited
       by hand (assuming, of course, that you do not make any syntax
       errors!).  For a more complete description of the syntax, see the
       &man.group.5; manual page.</para>
 
     <para>If you do not want to edit <filename>/etc/group</filename>
       manually, you can use the &man.pw.8; command to add and edit groups.
       For example, to add a group called <groupname>teamtwo</groupname> and
       then confirm that it exists you can use:</para>
 
     <example>
       <title>Adding a Group Using &man.pw.8;</title>
 
       <screen>&prompt.root; <userinput>pw groupadd teamtwo</userinput>
 &prompt.root; <userinput>pw groupshow teamtwo</userinput>
 teamtwo:*:1100:</screen>
     </example>
 
     <para>The number <literal>1100</literal> above is the group ID of the
       group <groupname>teamtwo</groupname>.  Right now,
       <groupname>teamtwo</groupname> has no members, and is thus rather
       useless.  Let's change that by inviting <username>jru</username> to
       the <groupname>teamtwo</groupname> group.</para>
 
     <example>
       <title>Adding Somebody to a Group Using &man.pw.8;</title>
 
       <screen>&prompt.root; <userinput>pw groupmod teamtwo -M jru</userinput>
 &prompt.root; <userinput>pw groupshow teamtwo</userinput>
 teamtwo:*:1100:jru</screen>
     </example>
 
     <para>The argument to the <option>-M</option> option is a
       comma-delimited list of users who are members of the group.  From the
       preceding sections, we know that the password file also contains a
       group for each user.  The latter (the user) is automatically added to
       the group list by the system; the user will not show up as a member
       when using the <option>groupshow</option> command to &man.pw.8;,
       but will show up when the information is queried via &man.id.1; or
       similar tool.  In other words, &man.pw.8; only manipulates the
       <filename>/etc/group</filename> file; it will never attempt to read
       additionally data from <filename>/etc/passwd</filename>.</para>
 
     <example>
       <title>Using &man.id.1; to Determine Group Membership</title>
 
       <screen>&prompt.user; <userinput>id jru</userinput>
 uid=1001(jru) gid=1001(jru) groups=1001(jru), 1100(teamtwo)</screen>
     </example>
 
     <para>As you can see, <username>jru</username> is a member of the
       groups <groupname>jru</groupname> and
       <groupname>teamtwo</groupname>.</para>
 
     <para>For more information about &man.pw.8;, see its manual page, and
       for more information on the format of
       <filename>/etc/group</filename>, consult the &man.group.5; manual
       page.</para>
   </sect1>
 </chapter>
 
 <!-- 
      Local Variables:
      mode: sgml
      sgml-declaration: "../chapter.decl"
      sgml-indent-data: t
      sgml-omittag: nil
      sgml-always-quote-attributes: t
      sgml-parent-document: ("../book.sgml" "part" "chapter")
      End:
 -->
diff --git a/zh_TW.Big5/books/handbook/x11/chapter.sgml b/zh_TW.Big5/books/handbook/x11/chapter.sgml
index c21eda03d2..532dd51106 100644
--- a/zh_TW.Big5/books/handbook/x11/chapter.sgml
+++ b/zh_TW.Big5/books/handbook/x11/chapter.sgml
@@ -1,1822 +1,1822 @@
 <!--
      The FreeBSD Documentation Project
 
      $FreeBSD$
 -->
 
 <chapter id="x11">
   <chapterinfo>
     <authorgroup>
       <author>
 	<firstname>Ken</firstname>
 	<surname>Tom</surname>
 	<contrib>Updated for X.Org's X11 server by </contrib>
       </author>
       <author>
 	<firstname>Marc</firstname>
 	<surname>Fonvieille</surname>
       </author>
     </authorgroup>
   </chapterinfo>
 
-  <title>The X Window System</title>
+  <title>X Window µøµ¡¨t²Î</title>
 
   <sect1 id="x11-synopsis">
-    <title>Synopsis</title>
+    <title>·§­z</title>
 
     <para>FreeBSD uses X11 to provide users with
       a powerful graphical user interface.  X11
       is an open-source implementation of the X Window System that
       includes both <application>&xorg;</application> and
       <application>&xfree86;</application>.  &os; versions up to and
       including &os;&nbsp;4.11-RELEASE and &os;&nbsp;5.2.1-RELEASE
       will find the default installation to be
       <application>&xfree86;</application>, the X11 server released by
       The &xfree86; Project, Inc.  As of &os;&nbsp;5.3-RELEASE, the
       default and official flavor of X11 was changed to
       <application>&xorg;</application>, the X11 server developed by
       the X.Org Foundation.</para>
 
     <para>This chapter will cover the installation and configuration
       of X11 with emphasis on
       <application>&xorg;</application>.</para>
 
     <para>For more information on the video hardware that X11
       supports, check either the <ulink
       url="http://www.x.org/">&xorg;</ulink> or <ulink
       url="http://www.XFree86.org/">&xfree86;</ulink> web
       sites.</para>
 
-    <para>After reading this chapter, you will know:</para>
+    <para>Ū§¹³o³¹¡A±z±N¤F¸Ñ¡G</para>
 
     <itemizedlist>
       <listitem>
         <para>The various components of the X Window System, and how they
           interoperate.</para>
       </listitem>
 
       <listitem>
 	<para>How to install and configure X11.</para>
       </listitem>
 
       <listitem>
         <para>How to install and use different window managers.</para>
       </listitem>
 
       <listitem>
 	<para>How to use &truetype; fonts in X11.</para>
       </listitem>
 
       <listitem>
         <para>How to set up your system for graphical logins
           (<application>XDM</application>).</para>
       </listitem>
     </itemizedlist>
 
-    <para>Before reading this chapter, you should:</para>
+    <para>¦b¶}©l¾\Ū³o³¹¤§«e¡A±z»Ý­n¡J</para>
 
     <itemizedlist>
       <listitem><para>Know how to install additional third-party
         software (<xref linkend="ports">).</para></listitem>
     </itemizedlist>
 
     <note>
       <para>This chapter covers the installation and the configuration
 	of both <application>&xorg;</application> and
 	<application>&xfree86;</application> X11 servers.  For the most
 	part, configuration files, commands and syntaxes are identical.
 	In the case where there are differences, both
 	<application>&xorg;</application> and
 	<application>&xfree86;</application> syntaxes will be
 	shown.</para>
     </note>
   </sect1>
 
   <sect1 id="x-understanding">
     <title>Understanding X</title>
 
     <para>Using X for the first time can be somewhat of a shock to someone
       familiar with other graphical environments, such as &microsoft.windows; or
       &macos;.</para>
 
     <para>While it is not necessary to understand all of the details of various
       X components and how they interact, some basic knowledge makes
       it possible to take advantage of X's strengths.</para>
 
     <sect2>
       <title>Why X?</title>
 
       <para>X is not the first window system written for &unix;, but it is the
         most popular of them.  X's original development team had worked on another
         window system prior to writing X.  That system's name was
         <quote>W</quote> (for <quote>Window</quote>).  X was just the next
         letter in the Roman alphabet.</para>
 
       <para>X can be called <quote>X</quote>, <quote>X Window System</quote>,
 	<quote>X11</quote>, and a number of other terms.  You may find
 	that using the term <quote>X Windows</quote> to describe X11
 	can be offensive to some people; for a bit more insight on
 	this, see &man.X.7;.</para>
     </sect2>
 
     <sect2>
       <title>The X Client/Server Model</title>
 
       <para>X was designed from the beginning to be network-centric, and
         adopts a <quote>client-server</quote> model.</para>
 
       <para>In the X model, the
         <quote>X server</quote> runs on the computer that has the keyboard,
         monitor, and mouse attached.  The server's responsibility includes tasks such as managing
         the display, handling input from the keyboard and mouse, and so on.
         Each X application (such as <application>XTerm</application>, or
         <application>&netscape;</application>) is a <quote>client</quote>.  A
         client sends messages to the server such as <quote>Please draw a
           window at these coordinates</quote>, and the server sends back
           messages such as <quote>The user just clicked on the OK
           button</quote>.</para>
 
       <para>In a home or small
         office environment, the X server and the X clients commonly run on
         the same computer.  However, it is perfectly possible to run the X
         server on a less powerful desktop computer, and run X applications
         (the clients) on, say, the powerful and expensive machine that serves
         the office.  In this scenario the communication between the X client
         and server takes place over the network.</para>
 
       <para>This confuses some people, because the X terminology is
         exactly backward to what they expect.  They expect the <quote>X
           server</quote> to be the big powerful machine down the hall, and
         the <quote>X client</quote> to be the machine on their desk.</para>
 
       <para>It is important to remember that the X server is the machine with the monitor and
         keyboard, and the X clients are the programs that display the
         windows.</para>
 
       <para>There is nothing in the protocol that forces the client and
         server machines to be running the same operating system, or even to
         be running on the same type of computer.  It is certainly possible to
         run an X server on &microsoft.windows; or Apple's &macos;, and there are
         various free and commercial applications available that do exactly
         that.</para>
 
       <para>Starting with &os;&nbsp;5.3-RELEASE, the X server that
 	installs with &os; is <application>&xorg;</application>,
         and is available for free, under a
         license very similar to the FreeBSD license.  Commercial X servers for
         FreeBSD are also available.</para>
     </sect2>
 
     <sect2>
       <title>The Window Manager</title>
 
       <para>The X design philosophy is much like the &unix; design philosophy,
         <quote>tools, not policy</quote>.  This means that X does not try to
         dictate how a task is to be accomplished.  Instead, tools are provided
         to the user, and it is the user's responsibility to decide how to use
         those tools.</para>
 
       <para>This philosophy extends to X not dictating what windows should
         look like on screen, how to move them around with the mouse, what
         keystrokes should be used to move between windows (i.e.,
         <keycombo action="simul">
           <keycap>Alt</keycap>
           <keycap>Tab</keycap>
         </keycombo>, in the case of &microsoft.windows;), what the title bars
         on each window should look like, whether or not they have close
         buttons on them, and so on.</para>
 
       <para>Instead, X delegates this responsibility to an application called
         a <quote>Window Manager</quote>.  There are dozens of window
         managers available for X: <application>AfterStep</application>,
         <application>Blackbox</application>, <application>ctwm</application>,
         <application>Enlightenment</application>,
         <application>fvwm</application>, <application>Sawfish</application>,
         <application>twm</application>,
         <application>Window Maker</application>, and more.  Each of these
         window managers provides a different look and feel; some of them
         support <quote>virtual desktops</quote>; some of them allow customized
         keystrokes to manage the desktop; some have a <quote>Start</quote>
         button or similar device; some are <quote>themeable</quote>, allowing
         a complete change of look-and-feel by applying a new theme.  These
         window managers, and many more, are available in the
         <filename>x11-wm</filename> category of the Ports Collection.</para>
 
       <para>In addition, the <application>KDE</application> and
 	<application>GNOME</application> desktop environments both have their
 	own window managers which integrate with the desktop.</para>
 
       <para>Each window manager also has a different configuration mechanism;
         some expect configuration file written by hand, others feature
         GUI tools for most of the configuration tasks; at least one
         (<application>Sawfish</application>) has a configuration file written
         in a dialect of the Lisp language.</para>
 
       <note>
         <title>Focus Policy</title>
 
         <para>Another feature the window manager is responsible for is the
           mouse <quote>focus policy</quote>.  Every windowing system
           needs some means of choosing a window to be actively receiving
           keystrokes, and should visibly indicate which window is active as
           well.</para>
 
         <para>A familiar focus policy is called <quote>click-to-focus</quote>.
           This is the model utilized by &microsoft.windows;, in which a window
           becomes active upon receiving a mouse click.</para>
 
         <para>X does not support any particular focus policy.  Instead, the
           window manager controls which window has the focus at any one time.
           Different window managers will support different focus methods.  All
           of them support click to focus, and the majority of them support
           several others.</para>
 
         <para>The most popular focus policies are:</para>
 
         <variablelist>
           <varlistentry>
             <term>focus-follows-mouse</term>
 
             <listitem>
               <para>The window that is under the mouse pointer is the
                 window that has the focus.  This may not necessarily be
                 the window that is on top of all the other windows.
                 The focus is changed by pointing at another window, there
                 is no need to click in it as well.</para>
             </listitem>
           </varlistentry>
 
           <varlistentry>
             <term>sloppy-focus</term>
 
             <listitem>
               <para>This policy is a small extension to focus-follows-mouse.
                 With focus-follows-mouse, if the mouse is moved over the
                 root window (or background) then no window has the focus,
                 and keystrokes are simply lost.  With sloppy-focus, focus is
                 only changed when the cursor enters a new window, and not
                 when exiting the current window.</para>
             </listitem>
           </varlistentry>
 
           <varlistentry>
             <term>click-to-focus</term>
 
             <listitem>
               <para>The active window is selected by mouse click.  The
                 window may then be <quote>raised</quote>, and appear in
                 front of all other windows.  All keystrokes will now be
                 directed to this window, even if the cursor is moved to
                 another window.</para>
             </listitem>
           </varlistentry>
         </variablelist>
 
         <para>Many window managers support other policies, as well as
           variations on these.  Be sure to consult the documentation for
           the window manager itself.</para>
       </note>
     </sect2>
 
     <sect2>
       <title>Widgets</title>
 
       <para>The X approach of providing tools and not policy extends to the
         widgets seen on screen in each application.</para>
 
       <para><quote>Widget</quote> is a term for all the items in the user
         interface that can be clicked or manipulated in some way; buttons,
         check boxes, radio buttons, icons, lists, and so on.  &microsoft.windows;
         calls these <quote>controls</quote>.</para>
 
       <para>&microsoft.windows; and Apple's &macos; both have a very rigid widget
         policy.  Application developers are supposed to ensure that their
         applications share a common look and feel.  With X, it was not
         considered sensible to mandate a particular graphical style, or set
         of widgets to adhere to.</para>
 
       <para>As a result, do not expect X applications to have a common
         look and feel.  There are several popular widget sets and
         variations, including the original Athena widget set from MIT,
         <application>&motif;</application> (on which the widget set in
         &microsoft.windows; was modeled, all bevelled edges and three shades of
         grey), <application>OpenLook</application>, and others.</para>
 
       <para>Most newer X applications today will use a modern-looking widget
         set, either Qt, used by <application>KDE</application>, or
         GTK+, used by the
         <application>GNOME</application>
         project.  In this respect, there is some convergence in
         look-and-feel of the &unix; desktop, which certainly makes things
         easier for the novice user.</para>
     </sect2>
   </sect1>
 
   <sect1 id="x-install">
-    <title>Installing X11</title>
+    <title>¦w¸Ë X11</title>
 
     <para><application>&xorg;</application> or
       <application>&xfree86;</application> may be installed on &os;.
       Beginning with &os;&nbsp;5.3-RELEASE,
       <application>&xorg;</application> is the default X11
       implementation for &os;.  <application>&xorg;</application> is
       the X server of the open source X Window System implementation released by the X.Org
       Foundation.  <application>&xorg;</application> is based on the code of
       <application>&xfree86&nbsp;4.4RC2</application> and X11R6.6.
       The X.Org Foundation released X11R6.7 in April 2004 and
       X11R6.8.2 in February 2005, this latter is the version
       currently available in the &os; Ports Collection.</para>
 
     <para>To build and install <application>&xorg;</application> from the
       Ports Collection:</para>
 
     <screen>&prompt.root; <userinput>cd /usr/ports/x11/xorg</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
 
     <note>
       <para>To build <application>&xorg;</application> in its
 	entirety, be sure to have at least 4&nbsp;GB of free space
 	available.</para>
     </note>
 
     <para>To build and install <application>&xfree86;</application>
       from the Ports Collection:</para>
 
     <screen>&prompt.root; <userinput>cd /usr/ports/x11/XFree86-4</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
 
     <para>Alternatively, X11
       can be installed directly from packages.
       Binary packages to use with &man.pkg.add.1; tool are also available for
       X11.  When the remote fetching
       feature of &man.pkg.add.1; is used, the version number of the
       package must be removed.  &man.pkg.add.1; will automatically fetch
       the latest version of the application.</para>
 
     <para>So to fetch and install the package of
       <application>&xorg;</application>, simply type:</para>
 
     <screen>&prompt.root; <userinput>pkg_add -r xorg</userinput></screen>
 
     <para>The <application>&xfree86;&nbsp;4.X</application> package can be
       installed by typing:</para>
 
     <screen>&prompt.root; <userinput>pkg_add -r XFree86</userinput></screen>
 
     <note><para>The examples above will install the complete
       X11 distribution including the
       servers, clients, fonts etc.  Separate packages and ports of X11
       are also
       available.</para></note>
 
     <para>The rest of this chapter will explain how to configure
       X11, and how to set up a productive desktop
       environment.</para>
 
     <sect2 id="x-to-xorg">
       <title>Moving from <application>&xfree86;</application> to
 	<application>&xorg;</application></title>
 
       <para>As with any port, you should check the
 	<filename>/usr/ports/UPDATING</filename> file for changes.
 	Included in this file are instructions for converting your
 	system from <application>&xfree86;</application> to
 	<application>&xorg;</application>.</para>
 
       <para>Use <application>CVSup</application> to update your ports
 	tree prior to attempting any conversion.  You will also need
 	to install <filename
 	role="package">sysutils/portupgrade</filename> prior to
 	converting your X11 installation.</para>
 
       <para>In your <filename>/etc/make.conf</filename> you will need
 	to add the variable <literal>X_WINDOW_SYSTEM=xorg</literal>.
 	This ensures that your system knows which X11 is being used.
 	The older <literal>XFREE86_VERSION</literal> variable has been
 	deprecated and has been replaced with the
 	<literal>X_WINDOW_SYSTEM</literal> variable.</para>
 
       <para>Then, use the following commands:</para>
 
       <screen>&prompt.root; <userinput>pkg_delete -f /var/db/pkg/imake-4* /var/db/pkg/XFree86-*</userinput>
 &prompt.root; <userinput>cd /usr/ports/x11/xorg</userinput>
 &prompt.root; <userinput>make install clean</userinput>
 &prompt.root; <userinput>pkgdb -F</userinput></screen>
 
       <para>The &man.pkgdb.1; command is part of the
 	<application>portupgrade</application> software and will
 	update various package dependencies.</para>
 
       <note>
 	<para>To build <application>&xorg;</application> in its
 	  entirety, be sure to have at least 4&nbsp;GB of free space
 	  available.</para>
       </note>
     </sect2>
   </sect1>
 
   <sect1 id="x-config">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Christopher</firstname>
           <surname>Shumway</surname>
           <contrib>Contributed by </contrib>
           <!-- July 2001 -->
         </author>
       </authorgroup>
     </sect1info>
-    <title>X11 Configuration</title>
+    <title>³]©w X11</title>
 
 
     <indexterm><primary>&xfree86;&nbsp;4.X</primary></indexterm>
     <indexterm><primary>&xfree86;</primary></indexterm>
     <indexterm><primary>&xorg;</primary></indexterm>
     <indexterm><primary>X11</primary></indexterm>
 
     <sect2>
       <title>Before Starting</title>
 
       <para>Before configuration of X11
         the following information about the target system is needed:</para>
 
       <itemizedlist>
         <listitem><para>Monitor specifications</para></listitem>
         <listitem><para>Video Adapter chipset</para></listitem>
         <listitem><para>Video Adapter memory</para></listitem>
       </itemizedlist>
 
       <indexterm><primary>horizontal scan rate</primary></indexterm>
       <indexterm><primary>vertical scan rate</primary></indexterm>
 
       <para>The specifications for the monitor are used by
         X11 to determine the resolution and
         refresh rate to run at.  These specifications can usually be
         obtained from the documentation that came with the monitor or from
         the manufacturer's website.  There are two ranges of numbers that
         are needed, the horizontal scan rate and the vertical synchronization
         rate.</para>
 
       <para>The video adapter's chipset defines what driver module
         X11 uses to talk to the graphics
         hardware.  With most chipsets, this can be automatically
         determined, but it is still useful to know in case the automatic
         detection does not work correctly.</para>
 
       <para>Video memory on the graphic adapter determines the
         resolution and color depth which the system can run at.  This is
         important to know so the user knows the limitations of the
         system.</para>
 
     </sect2>
 
     <sect2>
       <title>Configuring X11</title>
 
       <para>Configuration of X11 is
         a multi-step process.  The first step is to build an initial
         configuration file.
         As the super user, simply
         run:</para>
 
       <screen>&prompt.root; <userinput>Xorg -configure</userinput></screen>
 
       <para>In the case of <application>&xfree86;</application>
 	type:</para>
 
       <screen>&prompt.root; <userinput>XFree86 -configure</userinput></screen>
 
       <para>This will generate an
         X11 configuration skeleton file in the
         <filename>/root</filename> directory called
 	<filename>xorg.conf.new</filename> (whether you &man.su.1; or
 	do a direct login affects the inherited supervisor
 	<envar>$HOME</envar> directory variable).
 	For <application>&xfree86;</application>, this configuration
 	file is called  <filename>XF86Config.new</filename>.  The
         X11 program will attempt to probe
         the graphics hardware on the system and write a
         configuration file to load the proper drivers for the detected
         hardware on the target system.</para>
 
       <para>The next step is to test the existing
         configuration to verify that <application>&xorg;</application>
         can work with the graphics
         hardware on the target system.  To perform this task,
         type:</para>
 
       <screen>&prompt.root; <userinput>Xorg -config xorg.conf.new</userinput></screen>
 
       <para><application>&xfree86;</application> users will type:</para>
 
       <screen>&prompt.root; <userinput>XFree86 -xf86config XF86Config.new</userinput></screen>
 
       <para>If a black and grey grid and an X mouse cursor appear,
         the configuration was successful.  To exit the test, just press
         <keycombo action="simul">
           <keycap>Ctrl</keycap>
           <keycap>Alt</keycap>
           <keycap>Backspace</keycap>
         </keycombo> simultaneously.</para>
 
 	<note><para>If the mouse does not work, you will need to first
 	  configure it before proceeding.  See <xref linkend="mouse">
 	  in the &os; install chapter.</para></note>
 
       <indexterm><primary>X11 tuning</primary></indexterm>
 
       <para>Next, tune the <filename>xorg.conf.new</filename> (or <filename>XF86Config.new</filename> if you are running <application>&xfree86;</application>)
         configuration file to taste.  Open the file in a text editor such
         as &man.emacs.1; or &man.ee.1;.  First, add the
         frequencies for the target system's monitor.  These are usually
         expressed as a horizontal and vertical synchronization rate.  These
         values are added to the <filename>xorg.conf.new</filename> file
         under the <literal>"Monitor"</literal> section:</para>
 
       <programlisting>Section "Monitor"
         Identifier   "Monitor0"
         VendorName   "Monitor Vendor"
         ModelName    "Monitor Model"
         HorizSync    30-107
         VertRefresh  48-120
 EndSection</programlisting>
 
       <para>The <literal>HorizSync</literal> and
         <literal>VertRefresh</literal> keywords may be missing in the
         configuration file.  If they are, they need to be added, with
         the correct horizontal synchronization rate placed after the
         <literal>HorizSync</literal> keyword and the vertical
         synchronization rate after the <literal>VertRefresh</literal>
         keyword.  In the example above the target monitor's rates were
         entered.</para>
 
       <para>X allows DPMS (Energy Star) features to be used with capable
         monitors. The &man.xset.1; program controls the time-outs and can force
         standby, suspend, or off modes.  If you wish to enable DPMS features
         for your monitor, you must add the following line to the monitor
         section:</para>
 
       <programlisting>
         Option       "DPMS"</programlisting>
 
       <indexterm>
         <primary><filename>xorg.conf</filename></primary>
       </indexterm>
       <indexterm>
         <primary><filename>XF86Config</filename></primary>
       </indexterm>
 
       <para>While the <filename>xorg.conf.new</filename> (or <filename>XF86Config.new</filename>)
         configuration file is still open in an editor, select
         the default resolution and color depth desired.  This is
         defined in the <literal>"Screen"</literal> section:</para>
 
       <programlisting>Section "Screen"
         Identifier "Screen0"
         Device     "Card0"
         Monitor    "Monitor0"
         DefaultDepth 24
         SubSection "Display"
                 Viewport  0 0
                 Depth     24
                 Modes     "1024x768"
         EndSubSection
 EndSection</programlisting>
 
       <para>The <literal>DefaultDepth</literal> keyword describes
         the color depth to run at by default.  This can be overridden
         with the <option>-depth</option> command line switch to
         &man.Xorg.1; (or &man.XFree86.1;).
         The <literal>Modes</literal> keyword
         describes the resolution to run at for the given color depth.
         Note that only VESA standard modes are supported as defined by
         the target system's graphics hardware.
         In the example above, the default color depth is twenty-four
         bits per pixel.  At this color depth, the accepted resolution is
         1024 by 768
         pixels.</para>
 
       <para>Finally, write the configuration file and test it using
         the test mode given above.</para>
 
       <note>
 	<para>One of the tools available to assist you during
 	  troubleshooting process are the X11 log files, which contain
 	  information on each device that the X11 server attaches to.
 	  <application>&xorg;</application> log file names are in the format
 	  of <filename>/var/log/Xorg.0.log</filename>
 	  (<application>&xfree86;</application> log file names follow the
 	  format of <filename>XFree86.0.log</filename>).  The exact name
 	  of the log can vary from <filename>Xorg.0.log</filename> to
 	  <filename>Xorg.8.log</filename> and so forth.</para>
       </note>
 
       <para>If all is well, the configuration
         file needs to be installed in a common location where
         &man.Xorg.1; (or &man.XFree86.1;)
         can find it.
 	This is typically <filename>/etc/X11/xorg.conf</filename> or
 	<filename>/usr/X11R6/etc/X11/xorg.conf</filename> (for
 	<application>&xfree86;</application> it is called
         <filename>/etc/X11/XF86Config</filename> or
         <filename>/usr/X11R6/etc/X11/XF86Config</filename>).</para>
 
       <screen>&prompt.root; <userinput>cp xorg.conf.new /etc/X11/xorg.conf</userinput></screen>
 
       <para>For <application>&xfree86;</application>:</para>
 
       <screen>&prompt.root; <userinput>cp XF86Config.new /etc/X11/XF86Config</userinput></screen>
 
       <para>The X11 configuration process is now
         complete.  In order to start
         <application>&xfree86;&nbsp;4.X</application> with &man.startx.1;,
         install the <filename role="package">x11/wrapper</filename> port.
 	<application>&xorg;</application> already includes the wrapper
 	code and does not require the installation of the wrapper port.
 	The X11 server may also be started with the use of
         &man.xdm.1;.</para>
 
       <note><para>There is also a graphical configuration tool,
 	&man.xorgcfg.1; (&man.xf86cfg.1; for <application>&xfree86;</application>), that comes with the
 	X11 distribution.  It
 	allows you to interactively define your configuration by choosing
 	the appropriate drivers and settings.  This program can be invoked from the console, by typing the command <command>xorgcfg -textmode</command>.  For more details,
 	refer to the &man.xorgcfg.1; and &man.xf86cfg.1; manual pages.</para>
 
       <para>Alternatively, there is also a tool called &man.xorgconfig.1;
 	(&man.xf86config.1; for <application>&xfree86;</application>),
 	this program is a console utility that is less user friendly,
 	but it may work in situations where the other tools do
 	not.</para></note>
 
     </sect2>
 
     <sect2>
       <title>Advanced Configuration Topics</title>
 
       <sect3>
         <title>Configuration with &intel; i810 Graphics Chipsets</title>
 
         <indexterm><primary>Intel i810 graphic chipset</primary></indexterm>
 
         <para>Configuration with &intel; i810 integrated chipsets
           requires the <devicename>agpgart</devicename>
           AGP programming interface for X11
           to drive the card.  The &man.agp.4; driver is in the
 	  <filename>GENERIC</filename> kernel since releases
 	  4.8-RELEASE and 5.0-RELEASE.  On prior releases, you will
 	  have to add the following line:</para>
 
 	<programlisting>device agp</programlisting>
 
 	<para>in your kernel configuration file and rebuild a new
 	  kernel.  Instead, you may want to load
 	  the <filename>agp.ko</filename> kernel module
           automatically with the &man.loader.8; at boot time.
           For that, simply add this line to
           <filename>/boot/loader.conf</filename>:</para>
 
         <programlisting>agp_load="YES"</programlisting>
 
         <para>Next, if you are running FreeBSD&nbsp;4.X or earlier, a
           device node needs to be created for the
           programming interface.  To create the AGP device node, run
           &man.MAKEDEV.8; in the <filename>/dev</filename>
           directory:</para>
 
         <screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>sh MAKEDEV agpgart</userinput></screen>
 
 	<note>
 	  <para>FreeBSD&nbsp;5.X or later will use &man.devfs.5; to allocate
 	    device nodes transparently, therefore the
 	    &man.MAKEDEV.8; step is not required.</para>
 	</note>
 
         <para>This will allow configuration of the hardware as any other
           graphics board.  Note on systems without the &man.agp.4;
 	  driver compiled in the kernel, trying to load the module
 	  with &man.kldload.8; will not work.  This driver has to be
 	  in the kernel at boot time through being compiled in or
 	  using <filename>/boot/loader.conf</filename>.</para>
 
 	<para>If you are using <application>&xfree86;&nbsp;4.1.0</application> (or
 	  later) and messages about unresolved symbols like
           <literal>fbPictureInit</literal> appear, try adding the
           following line after <literal>Driver "i810"</literal> in the
           X11 configuration file:</para>
         <programlisting>Option "NoDDC"</programlisting>
       </sect3>
     </sect2>
   </sect1>
 
   <sect1 id="x-fonts">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Murray</firstname>
           <surname>Stokely</surname>
           <contrib>Contributed by </contrib>
         </author>
       </authorgroup>
     </sect1info>
-    <title>Using Fonts in X11</title>
+    <title>¦b X11 ¤¤¨Ï¥Î¦r«¬</title>
 
     <sect2 id="type1">
-    <title>Type1 Fonts</title>
+    <title>Type1 ³W®æªº¦r«¬</title>
     <para>The default fonts that ship with
       X11 are less than ideal for typical
     desktop publishing applications.  Large presentation fonts show up
     jagged and unprofessional looking, and small fonts in
     <application>&netscape;</application> are almost completely unintelligible.
     However, there are several free, high quality Type1 (&postscript;) fonts
     available which can be readily used
     with X11.  For instance, the URW font collection
     (<filename role="package">x11-fonts/urwfonts</filename>) includes
     high quality versions of standard type1 fonts (<trademark class="registered">Times Roman</trademark>,
     <trademark class="registered">Helvetica</trademark>, <trademark class="registered">Palatino</trademark> and others).  The Freefonts collection
     (<filename role="package">x11-fonts/freefonts</filename>) includes
     many more fonts, but most of them are intended for use in
     graphics software such as the <application>Gimp</application>, and are not
     complete enough to serve as screen fonts.  In addition,
     X11 can be configured to use
     &truetype; fonts with a minimum of effort.  For more details on
     this, see the &man.X.7; manual page or the
     <link linkend="truetype">section on &truetype; fonts</link>.</para>
 
     <para>To install the above Type1 font collections from the ports
         collection, run the following commands:</para>
 
     <screen>&prompt.root; <userinput>cd /usr/ports/x11-fonts/urwfonts</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
 
     <para>And likewise with the freefont or other collections.  To have the X
       server detect these fonts, add an appropriate line to the
       X server configuration file in <filename>/etc/X11/</filename>
       (<filename>xorg.conf</filename> for
       <application>&xorg;</application> and
       <filename>XF86Config</filename> for
       <application>&xfree86;</application>), which reads:</para>
 
       <programlisting>FontPath "/usr/X11R6/lib/X11/fonts/URW/"</programlisting>
 
       <para>Alternatively, at the command line in the X session
         run:</para>
 
       <screen>&prompt.user; <userinput>xset fp+ /usr/X11R6/lib/X11/fonts/URW</userinput>
 &prompt.user; <userinput>xset fp rehash</userinput></screen>
 
       <para>This will work but will be lost when the X session is closed,
     unless it is added to the startup file (<filename>~/.xinitrc</filename>
     for a normal <command>startx</command> session,
     or <filename>~/.xsession</filename> when logging in through a
     graphical login manager like <application>XDM</application>).
     A third way is to use the new
     <filename>/usr/X11R6/etc/fonts/local.conf</filename> file: see the
     section on <link linkend="antialias">anti-aliasing</link>.
     </para>
     </sect2>
 
     <sect2 id="truetype">
-    <title>&truetype; Fonts</title>
+    <title>&truetype; ³W®æªº¦r«¬</title>
 
     <indexterm><primary>TrueType Fonts</primary></indexterm>
     <indexterm><primary>fonts</primary>
       <secondary>TrueType</secondary>
     </indexterm>
 
     <para>Both <application>&xfree86;&nbsp;4.X</application> and <application>&xorg;</application> have built in support
     for rendering &truetype; fonts.  There are two different modules
     that can enable this functionality.  The freetype module is used
     in this example because it is more consistent with the other font
     rendering back-ends.  To enable the freetype module just add the
     following line to the <literal>"Module"</literal> section of the
     <filename>/etc/X11/xorg.conf</filename> or
     <filename>/etc/X11/XF86Config</filename> file.</para>
 
     <programlisting>Load  "freetype"</programlisting>
 
     <para>For <application>&xfree86;&nbsp;3.3.X</application>, a separate
       &truetype; font server is needed.
       <application>Xfstt</application> is commonly used for
       this purpose.  To install <application>Xfstt</application>,
       simply install the port
       <filename role="package">x11-servers/Xfstt</filename>.</para>
 
     <para>Now make a directory for the &truetype; fonts (for example,
       <filename>/usr/X11R6/lib/X11/fonts/TrueType</filename>)
       and copy all of the &truetype; fonts into this directory.  Keep in
       mind that &truetype; fonts cannot be directly taken from a
       &macintosh;; they must be in &unix;/&ms-dos;/&windows; format for use by
       X11.  Once the files have been
       copied into this directory, use
       <application>ttmkfdir</application> to create a
       <filename>fonts.dir</filename> file, so that the X font renderer
       knows that these new files have been installed.
       <command>ttmkfdir</command> is available from the FreeBSD
       Ports Collection as
       <filename role="package">x11-fonts/ttmkfdir</filename>.</para>
 
     <screen>&prompt.root; <userinput>cd /usr/X11R6/lib/X11/fonts/TrueType</userinput>
 &prompt.root; <userinput>ttmkfdir &gt; fonts.dir</userinput></screen>
 
     <para>Now add the &truetype; directory to the font
       path.  This is just the same as described above for <link
       linkend="type1">Type1</link> fonts, that is, use</para>
 
     <screen>&prompt.user; <userinput>xset fp+ /usr/X11R6/lib/X11/fonts/TrueType</userinput>
 &prompt.user; <userinput>xset fp rehash</userinput></screen>
 
     <para>or add a <literal>FontPath</literal> line to the
        <filename>xorg.conf</filename> (or <filename>XF86Config</filename>) file.</para>
 
       <para>That's it.  Now <application>&netscape;</application>,
         <application>Gimp</application>,
         <application>&staroffice;</application>, and all of the other X
         applications should now recognize the installed &truetype;
         fonts.  Extremely small fonts (as with text in a high resolution
         display on a web page) and extremely large fonts (within
         <application>&staroffice;</application>) will look much better
         now.</para>
     </sect2>
 
     <sect2 id="antialias">
     <sect2info>
       <authorgroup>
         <author>
           <firstname>Joe Marcus</firstname>
           <surname>Clarke</surname>
           <contrib>Updated by </contrib>
           <!-- May 2003 -->
         </author>
       </authorgroup>
     </sect2info>
-    <title>Anti-Aliased Fonts</title>
+    <title>Anti-Aliased ³W®æªº¦r«¬</title>
 
     <indexterm><primary>anti-aliased fonts</primary></indexterm>
     <indexterm><primary>fonts</primary>
       <secondary>anti-aliased</secondary></indexterm>
 
     <para>Anti-aliasing has been available in X11 since
       <application>&xfree86;</application> 4.0.2.  However, font
       configuration was cumbersome before the introduction of
       <application>&xfree86;</application> 4.3.0.
       Beginning with
       <application>&xfree86;</application> 4.3.0, all fonts in X11
       that are found
       in <filename>/usr/X11R6/lib/X11/fonts/</filename> and
       <filename>~/.fonts/</filename> are automatically 
       made available for anti-aliasing to Xft-aware applications.  Not
       all applications are Xft-aware, but many have received Xft support.
       Examples of Xft-aware applications include Qt 2.3 and higher (the 
       toolkit for the <application>KDE</application> desktop), 
       GTK+ 2.0 and higher (the toolkit for the 
       <application>GNOME</application> desktop), and 
       <application>Mozilla</application> 1.2 and higher.
     </para>
 
     <para>In order to control which fonts are anti-aliased, or to
       configure anti-aliasing properties, create (or edit, if it
       already exists) the file
       <filename>/usr/X11R6/etc/fonts/local.conf</filename>.  Several
       advanced features of the Xft font system can be tuned using
       this file; this section describes only some simple
       possibilities.  For more details, please see
       &man.fonts-conf.5;.</para>
 
     <indexterm><primary>XML</primary></indexterm>
 
     <para>This file must be in XML format.  Pay careful attention to
       case, and make sure all tags are properly closed.  The file
       begins with the usual XML header followed by a DOCTYPE
       definition, and then the <literal>&lt;fontconfig&gt;</literal> tag:</para>
 
     <programlisting>
       &lt;?xml version="1.0"?&gt;
       &lt;!DOCTYPE fontconfig SYSTEM "fonts.dtd"&gt;
       &lt;fontconfig&gt;
     </programlisting>
 
     <para>As previously stated, all fonts in
       <filename>/usr/X11R6/lib/X11/fonts/</filename> as well as
       <filename>~/.fonts/</filename> are already made available to
       Xft-aware applications.  If you wish to add another directory
       outside of these two directory trees, add a line similar to the
       following to
       <filename>/usr/X11R6/etc/fonts/local.conf</filename>:</para>
 
     <programlisting>&lt;dir&gt;/path/to/my/fonts&lt;/dir&gt;</programlisting>
 
     <para>After adding new fonts, and especially new font directories,
       you should run the following command to rebuild the font
       caches:</para>
 
     <screen>&prompt.root; <userinput>fc-cache -f</userinput></screen>
 
     <para>Anti-aliasing makes borders slightly fuzzy, which makes very
       small text more readable and removes <quote>staircases</quote> from
       large text, but can cause eyestrain if applied to normal text.  To
       exclude font sizes smaller than 14 point from anti-aliasing, include
       these lines:</para>
 
       <programlisting>        &lt;match target="font"&gt;
             &lt;test name="size" compare="less"&gt;
                 &lt;double&gt;14&lt;/double&gt;
             &lt;/test&gt;
             &lt;edit name="antialias" mode="assign"&gt;
                 &lt;bool&gt;false&lt;/bool&gt;
             &lt;/edit&gt;
         &lt;/match&gt;
         &lt;match target="font"&gt;
             &lt;test name="pixelsize" compare="less" qual="any"&gt;
                 &lt;double&gt;14&lt;/double&gt;
             &lt;/test&gt;
             &lt;edit mode="assign" name="antialias"&gt;
                 &lt;bool&gt;false&lt;/bool&gt;
             &lt;/edit&gt;
         &lt;/match&gt;</programlisting>
 
     <indexterm><primary>fonts</primary>
       <secondary>spacing</secondary></indexterm>
 
     <para>Spacing for some monospaced fonts may also be inappropriate
       with anti-aliasing.  This seems to be an issue with
       <application>KDE</application>, in particular.  One possible fix for
       this is to force the spacing for such fonts to be 100.  Add the
       following lines:</para>
 
      <programlisting>       &lt;match target="pattern" name="family"&gt;
            &lt;test qual="any" name="family"&gt;
                &lt;string&gt;fixed&lt;/string&gt;
            &lt;/test&gt;
            &lt;edit name="family" mode="assign"&gt;
                &lt;string&gt;mono&lt;/string&gt;
            &lt;/edit&gt;
         &lt;/match&gt;
         &lt;match target="pattern" name="family"&gt;
             &lt;test qual="any" name="family"&gt;
                 &lt;string&gt;console&lt;/string&gt;
             &lt;/test&gt;
             &lt;edit name="family" mode="assign"&gt;
                 &lt;string&gt;mono&lt;/string&gt;
             &lt;/edit&gt;
         &lt;/match&gt;</programlisting>
 
       <para>(this aliases the other common names for fixed fonts as
         <literal>"mono"</literal>), and then add:</para>
 
       <programlisting>         &lt;match target="pattern" name="family"&gt;
              &lt;test qual="any" name="family"&gt;
                  &lt;string&gt;mono&lt;/string&gt;
              &lt;/test&gt;
              &lt;edit name="spacing" mode="assign"&gt;
                  &lt;int&gt;100&lt;/int&gt;
              &lt;/edit&gt;
          &lt;/match&gt;      </programlisting>
 
       <para>Certain fonts, such as Helvetica, may have a problem when
 	anti-aliased.  Usually this manifests itself as a font that
 	seems cut in half vertically.  At worst, it may cause
 	applications such as <application>Mozilla</application> to
 	crash.  To avoid this, consider adding the following to
 	<filename>local.conf</filename>:</para>
 
       <programlisting>         &lt;match target="pattern" name="family"&gt;
              &lt;test qual="any" name="family"&gt;
                  &lt;string&gt;Helvetica&lt;/string&gt;
              &lt;/test&gt;
              &lt;edit name="family" mode="assign"&gt;
                  &lt;string&gt;sans-serif&lt;/string&gt;
              &lt;/edit&gt;
          &lt;/match&gt;        </programlisting>
 
       <para>Once you have finished editing
         <filename>local.conf</filename> make sure you end the file
         with the <literal>&lt;/fontconfig&gt;</literal> tag.  Not doing this will cause
         your changes to be ignored.</para>
 
        <para>The default font set that comes with 
 	 X11 is not very
          desirable when it comes to anti-aliasing.  A much better
 	 set of default fonts can be found in the 
 	 <filename role="package">x11-fonts/bitstream-vera</filename>
 	 port.  This port will install a
 	 <filename>/usr/X11R6/etc/fonts/local.conf</filename> file
 	 if one does not exist already.  If the file does exist,
 	 the port will create a <filename>/usr/X11R6/etc/fonts/local.conf-vera
 	 </filename> file.  Merge the contents of this file into
 	 <filename>/usr/X11R6/etc/fonts/local.conf</filename>, and the 
 	 Bitstream fonts will automatically replace the default 
 	 X11 Serif, Sans Serif, and Monospaced
 	 fonts.</para>
 
        <para>Finally, users can add their own settings via their personal 
         <filename>.fonts.conf</filename> files.  To do this, each user should 
 	simply create a <filename>~/.fonts.conf</filename>.  This file must 
 	also be in XML format.</para>
 
        <indexterm><primary>LCD screen</primary></indexterm>
        <indexterm><primary>Fonts</primary>
          <secondary>LCD screen</secondary></indexterm>
 
        <para>One last point: with an LCD screen, sub-pixel sampling may be
         desired.  This basically treats the (horizontally separated)
         red, green and blue components separately to improve the horizontal
         resolution; the results can be dramatic.  To enable this, add the
         line somewhere in the <filename>local.conf</filename> file:</para>
 
        <programlisting>
          &lt;match target="font"&gt;
              &lt;test qual="all" name="rgba"&gt;
                  &lt;const&gt;unknown&lt;/const&gt;
              &lt;/test&gt;
              &lt;edit name="rgba" mode="assign"&gt;
                  &lt;const&gt;rgb&lt;/const&gt;
              &lt;/edit&gt;
          &lt;/match&gt;
        </programlisting>
 
        <note><para>Depending on the sort of display,
 	 <literal>rgb</literal> may need to be changed to <literal>bgr</literal>,
 	 <literal>vrgb</literal> or <literal>vbgr</literal>: experiment and
 	 see which works best.</para></note>
 
        <indexterm>
 	 <primary>Mozilla</primary>
          <secondary>disabling anti-aliased fonts</secondary>
        </indexterm>
 
        <para>Anti-aliasing should be enabled the next time the X
          server is started.  However, programs must know how to take
          advantage of it.  At present, the Qt toolkit does,
          so the entire <application>KDE</application> environment can
          use anti-aliased fonts (see <xref
          linkend="x11-wm-kde-antialias"> on
          <application>KDE</application> for details).  GTK+ and 
          <application>GNOME</application> can also be made to use 
          anti-aliasing via the <quote>Font</quote> capplet (see <xref
          linkend="x11-wm-gnome-antialias"> for details).  By default,
          <application>Mozilla</application> 1.2 and greater will 
          automatically use anti-aliasing. To disable this, rebuild 
          <application>Mozilla</application> with the
          <makevar>-DWITHOUT_XFT</makevar> flag.</para>
     </sect2>
   </sect1>
 
   <sect1 id="x-xdm">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Seth</firstname>
           <surname>Kingsley</surname>
           <contrib>Contributed by </contrib>
         </author>
       </authorgroup>
     </sect1info>
     <title>The X Display Manager</title>
     <sect2>
       <title>Overview</title>
 
       <indexterm><primary>X Display Manager</primary></indexterm>
       <para>The X Display Manager (<application>XDM</application>) is
         an optional part of the X Window System that is used for login
         session management.  This is useful for several types of
         situations, including minimal <quote>X Terminals</quote>,
         desktops, and large network display
         servers.  Since the X Window System is network and protocol
         independent, there are a wide variety of possible configurations
         for running X clients and servers on different machines
         connected by a network.  <application>XDM</application> provides
         a graphical interface for choosing which display server to
         connect to, and entering authorization information such as a
         login and password combination.</para>
 
       <para>Think of <application>XDM</application> as
         providing the same functionality to the user as the
         &man.getty.8; utility (see <xref linkend="term-config"> for
           details).  That is, it performs system logins to the display
           being connected to and then runs a session manager on behalf of
           the user (usually an X window
           manager).  <application>XDM</application> then waits for this
           program to exit, signaling that the user is done and should be
           logged out of the display.  At this point,
           <application>XDM</application> can display the login and display
           chooser screens for the next user to login.</para>
     </sect2>
 
     <sect2>
       <title>Using XDM</title>
 
       <para>The <application>XDM</application> daemon program is
         located in <filename>/usr/X11R6/bin/xdm</filename>.  This program
         can be run at any time as <username>root</username> and it will
         start managing the X display on the local machine.  If
         <application>XDM</application> is to be run every
         time the machine boots up, a convenient way to do this is by
         adding an entry to <filename>/etc/ttys</filename>.  For more
         information about the format and usage of this file, see <xref
         linkend="term-etcttys">.  There is a line in the default
         <filename>/etc/ttys</filename> file for running the
         <application>XDM</application> daemon on a virtual terminal:</para>
 
       <screen>ttyv8   "/usr/X11R6/bin/xdm -nodaemon"  xterm   off secure</screen>
 
       <para>By default this entry is disabled; in order to enable it
         change field 5 from <literal>off</literal> to
         <literal>on</literal> and restart &man.init.8; using the
         directions in <xref linkend="term-hup">.  The first field, the
         name of the terminal this program will manage, is
         <literal>ttyv8</literal>.  This means that
         <application>XDM</application> will start running on the 9th
         virtual terminal.</para>
     </sect2>
 
     <sect2>
       <title>Configuring XDM</title>
 
       <para>The <application>XDM</application> configuration directory
         is located in <filename>/usr/X11R6/lib/X11/xdm</filename>.  In
         this directory there are several files used to change the
         behavior and appearance of
         <application>XDM</application>.  Typically these files will
         be found:</para>
 
         <informaltable frame="none" pgwide="1">
           <tgroup cols="2">
             <thead>
               <row>
                 <entry>File</entry>
                 <entry>Description</entry>
               </row>
             </thead>
 
             <tbody>
               <row>
                 <entry><filename>Xaccess</filename></entry>
                 <entry>Client authorization ruleset.</entry>
               </row>
 
               <row>
                 <entry><filename>Xresources</filename></entry>
                 <entry>Default X resource values.</entry>
               </row>
 
               <row>
                 <entry><filename>Xservers</filename></entry>
                 <entry>List of remote and local displays to manage.</entry>
               </row>
 
               <row>
                 <entry><filename>Xsession</filename></entry>
                 <entry>Default session script for logins.</entry>
               </row>
 
               <row>
                 <entry><filename>Xsetup_</filename>*</entry>
                 <entry>Script to launch applications before the login
                   interface.</entry>
               </row>
 
               <row>
                 <entry><filename>xdm-config</filename></entry>
                 <entry>Global configuration for all displays running on
                   this machine.</entry>
               </row>
 
               <row>
                 <entry><filename>xdm-errors</filename></entry>
                 <entry>Errors generated by the server program.</entry>
               </row>
 
               <row>
                 <entry><filename>xdm-pid</filename></entry>
                 <entry>The process ID of the currently running XDM.</entry>
               </row>
             </tbody>
           </tgroup>
         </informaltable>
 
       <para>Also in this directory are a few scripts and programs used
         to set up the desktop when <application>XDM</application> is
         running.  The purpose of each of these files will be briefly
         described.  The exact syntax and usage of all of these files is
         described in &man.xdm.1;.</para>
 
       <para>The default configuration is a simple rectangular login
         window with the hostname of the machine displayed at the top in
         a large font and <quote>Login:</quote> and
         <quote>Password:</quote> prompts below.  This is a good starting
         point for changing the look and feel of
         <application>XDM</application> screens.</para>
 
       <sect3>
         <title>Xaccess</title>
 
         <para>The protocol for connecting to
           <application>XDM</application> controlled displays is called
           the X Display Manager Connection Protocol (XDMCP).  This file
           is a ruleset for controlling XDMCP connections from remote
 	  machines.  It's ignored unless the <filename>xdm-config</filename>
 	  is changed to listen for remote connections.  By default, it does
 	  not allow any clients to connect.</para>
       </sect3>
 
       <sect3>
         <title>Xresources</title>
         <para>This is an application-defaults file for the display
           chooser and the login screens.  This is where the appearance
           of the login program can be modified.  The format is identical
           to the app-defaults file described in the
 	  X11 documentation.</para>
       </sect3>
 
       <sect3>
         <title>Xservers</title>
         <para>This is a list of the remote displays the chooser should
           provide as choices.</para>
       </sect3>
 
       <sect3>
         <title>Xsession</title>
         <para>This is the default session script for
           <application>XDM</application> to run after a user has logged
           in.  Normally each user will have a customized session script
           in <filename>~/.xsession</filename> that overrides this
           script.</para>
       </sect3>
 
       <sect3>
         <title>Xsetup_*</title>
         <para>These will be run automatically before displaying the
           chooser or login interfaces.  There is a script for each
           display being used, named <filename>Xsetup_</filename> followed
           by the local display number (for instance
           <filename>Xsetup_0</filename>).  Typically these scripts will
           run one or two programs in the background such as
           <command>xconsole</command>.</para>
       </sect3>
 
       <sect3>
         <title>xdm-config</title>
         <para>This contains settings in the form of app-defaults
           that are applicable to every display that this installation
           manages.</para>
       </sect3>
 
       <sect3>
         <title>xdm-errors</title>
         <para>This contains the output of the X servers that
           <application>XDM</application> is trying to run.  If a display
           that <application>XDM</application> is trying to start hangs
           for some reason, this is a good place to look for error
           messages.  These messages are also written to the user's
           <filename>~/.xsession-errors</filename> file on a per-session
           basis.</para>
       </sect3>
     </sect2>
 
     <sect2>
       <title>Running a Network Display Server</title>
 
       <para>In order for other clients to connect to the display
         server, edit the access control rules, and enable the connection
         listener.  By default these are set to conservative values.
         To make <application>XDM</application> listen for connections,
         first comment out a line in the <filename>xdm-config</filename>
         file:</para>
 
       <screen>! SECURITY: do not listen for XDMCP or Chooser requests
 ! Comment out this line if you want to manage X terminals with xdm
 DisplayManager.requestPort:     0</screen>
 
       <para>and then restart <application>XDM</application>.  Remember that
         comments in app-defaults files begin with a <quote>!</quote>
         character, not the usual <quote>#</quote>.  More strict
         access controls may be desired.  Look at the example
         entries in <filename>Xaccess</filename>, and refer to the
         &man.xdm.1; manual page.</para>
     </sect2>
 
      <sect2>
         <title>Replacements for XDM</title>
 
         <para>Several replacements for the default
           <application>XDM</application> program exist.  One of them,
           <application>kdm</application> (bundled with
           <application>KDE</application>) is described later in this
           chapter.  The <application>kdm</application> display manager offers many visual
           improvements and cosmetic frills, as well as the
           functionality to allow users to choose their window manager
           of choice at login time.</para>
      </sect2>
   </sect1>
 
   <sect1 id="x11-wm">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Valentino</firstname>
           <surname>Vaschetto</surname>
           <contrib>Contributed by </contrib>
         </author>
         <!-- June 2001 -->
       </authorgroup>
     </sect1info>
 
     <title>Desktop Environments</title>
 
     <para>This section describes the different desktop environments
       available for X on FreeBSD.  A <quote>desktop environment</quote>
       can mean anything ranging from a simple window manager to a
       complete suite of desktop applications, such as
       <application>KDE</application> or <application>GNOME</application>.
     </para>
 
     <sect2 id="x11-wm-gnome">
       <title>GNOME</title>
 
       <sect3 id="x11-wm-gnome-about">
         <title>About GNOME</title>
 
         <indexterm><primary>GNOME</primary></indexterm>
         <para><application>GNOME</application> is a user-friendly
           desktop environment that enables users to easily use and
           configure their computers.  <application>GNOME</application>
           includes a panel (for starting applications and displaying
           status), a desktop (where data and applications can be
           placed), a set of standard desktop tools and applications, and
           a set of conventions that make it easy for applications to
           cooperate and be consistent with each other.  Users of other
           operating systems or environments should feel right at home
           using the powerful graphics-driven environment that
           <application>GNOME</application> provides.  More
 	  information regarding <application>GNOME</application> on
 	  FreeBSD can be found on the <ulink
 	  url="http://www.FreeBSD.org/gnome">FreeBSD GNOME
 	  Project</ulink>'s web site.  The web site also contains fairly
 	  comprehensive FAQs about installing, configuring, and managing
 	  <application>GNOME</application>.</para>
       </sect3>
 
       <sect3 id="x11-wm-gnome-install">
         <title>Installing GNOME</title>
 
         <para>The easiest way to install
           <application>GNOME</application> is through the
           <quote>Desktop Configuration</quote> menu during the FreeBSD
 	  installation process as described in <xref
 	  linkend="default-desktop"> of Chapter&nbsp;2.  It can also
           be easily installed from a package or the ports
           collection:</para>
 
         <para>To install the <application>GNOME</application> package
           from the network, simply type:</para>
 
         <screen>&prompt.root; <userinput>pkg_add -r gnome2</userinput></screen>
 
         <para>To build <application>GNOME</application> from source, use
           the ports tree:</para>
 
         <screen>&prompt.root; <userinput>cd /usr/ports/x11/gnome2</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
 
         <para>Once <application>GNOME</application> is installed,
           the X server must be told to start
           <application>GNOME</application> instead of a default window
           manager.</para>
 
         <para>The easiest way to start
           <application>GNOME</application> is with
           <application>GDM</application>, the GNOME Display Manager.
           <application>GDM</application>, which is installed as a part
           of the <application>GNOME</application> desktop (but is
           disabled by default), can be enabled by adding
           <literal>gdm_enable="YES"</literal> to
           <filename>/etc/rc.conf</filename>.  Once you have rebooted,
           <application>GNOME</application> will start automatically
           once you log in &mdash; no further configuration is
           necessary.</para>
 
         <para><application>GNOME</application> may also be started
 	  from the command-line by properly configuring a file named
 	  <filename>.xinitrc</filename>.
           If a custom <filename>.xinitrc</filename> is already in
           place, simply replace the line that starts the current window
           manager with one that starts
           <application>/usr/X11R6/bin/gnome-session</application> instead.
           If nothing special has been done to the configuration file,
           then it is enough simply to type:</para>
 
         <screen>&prompt.user; <userinput>echo "/usr/X11R6/bin/gnome-session" &gt; ~/.xinitrc</userinput></screen>
 
         <para>Next, type <command>startx</command>, and the
           <application>GNOME</application> desktop environment will be
           started.</para>
 
         <note><para>If an older display manager, like
           <application>XDM</application>, is being used, this will not work.
           Instead, create an executable <filename>.xsession</filename>
           file with the same command in it.  To do this, edit the file
           and replace the existing window manager command with
           <application>/usr/X11R6/bin/gnome-session</application>:
           </para></note>
 
         <screen>&prompt.user; <userinput>echo "#!/bin/sh" > ~/.xsession</userinput>
 &prompt.user; <userinput>echo "/usr/X11R6/bin/gnome-session" >> ~/.xsession</userinput>
 &prompt.user; <userinput>chmod +x ~/.xsession</userinput></screen>
 
         <para>Yet another option is to configure the display manager to
           allow choosing the window manager at login time; the section on
           <link linkend="x11-wm-kde-details">KDE details</link>
           explains how to do this for <application>kdm</application>, the
           display manager of <application>KDE</application>.</para>
       </sect3>
 
       <sect3 id="x11-wm-gnome-antialias">
         <title>Anti-aliased Fonts with GNOME</title>
 
         <indexterm><primary>GNOME</primary>
           <secondary>anti-aliased fonts</secondary></indexterm>
 	<para>X11
 	  supports anti-aliasing via its <quote>RENDER</quote> extension.
 	  GTK+ 2.0 and greater (the toolkit used by
 	  <application>GNOME</application>) can make use of this
 	  functionality.  Configuring anti-aliasing is described in
 	  <xref linkend="antialias">.  So, with up-to-date software,
 	  anti-aliasing is possible within the
 	  <application>GNOME</application> desktop.  Just go to
 	  <menuchoice>
 	    <guimenu>Applications</guimenu>
 	    <guisubmenu>Desktop Preferences</guisubmenu>
 	    <guimenuitem>Font</guimenuitem></menuchoice>, and select either
 	  <guibutton>Best shapes</guibutton>, 
 	  <guibutton>Best contrast</guibutton>, or
 	  <guibutton>Subpixel smoothing (LCDs)</guibutton>.  For a
 	  GTK+ application that is not part of the 
 	  <application>GNOME</application> desktop, set the
 	  environment variable <varname>GDK_USE_XFT</varname> to
 	  <literal>1</literal> before launching the program.</para>
       </sect3>
     </sect2>
 
     <sect2 id="x11-wm-kde">
       <title>KDE</title>
 
       <indexterm><primary>KDE</primary></indexterm>
       <sect3 id="x11-wm-kde-about">
         <title>About KDE</title>
 
         <para><application>KDE</application> is an easy to use
           contemporary desktop environment.  Some of the things that
           <application>KDE</application> brings to the user are:</para>
 
         <itemizedlist>
           <listitem>
 	    <para>A beautiful contemporary desktop</para>
 	  </listitem>
 
           <listitem>
 	    <para>A desktop exhibiting complete network transparency</para>
 	  </listitem>
 
           <listitem>
 	    <para>An integrated help system allowing for convenient,
 	      consistent access to help on the use of the
 	      <application>KDE</application> desktop and its
 	      applications</para>
 	  </listitem>
 
           <listitem>
 	    <para>Consistent look and feel of all
               <application>KDE</application> applications</para>
 	  </listitem>
 
           <listitem>
 	    <para>Standardized menu and toolbars, keybindings, color-schemes,
 	      etc.</para>
 	  </listitem>
 
           <listitem>
 	    <para>Internationalization: <application>KDE</application>
               is available in more than 40 languages</para>
 	  </listitem>
 
           <listitem>
 	    <para>Centralized consisted dialog driven desktop
 	      configuration</para>
 	  </listitem>
 
           <listitem>
 	    <para>A great number of useful
               <application>KDE</application> applications</para>
 	  </listitem>
         </itemizedlist>
 
         <para><application>KDE</application> has an office application
           suite based on <application>KDE</application>'s
           <quote>KParts</quote> technology consisting
           of a spread-sheet, a presentation application, an organizer, a
           news client and more.  <application>KDE</application> also
           comes with a web browser called
           <application>Konqueror</application>, which represents
           a solid competitor to other existing web browsers on &unix;
           systems.  More information on <application>KDE</application>
           can be found on the <ulink url="http://www.kde.org/">KDE
           website</ulink>.  For FreeBSD specific information and
 	  resources on <application>KDE</application>, consult
 	  the <ulink url="http://freebsd.kde.org/">FreeBSD-KDE
 	  team</ulink>'s website.</para>
       </sect3>
 
       <sect3 id="x11-wm-kde-install">
         <title>Installing KDE</title>
 
         <para>Just as with <application>GNOME</application> or any
           other desktop environment, the easiest way to install
           <application>KDE</application> is through the <quote>Desktop
           Configuration</quote> menu during the FreeBSD installation
 	  process as described in <xref linkend="default-desktop"> of Chapter
 	  2.  Once again, the software can be easily installed from a package
 	  or from the Ports Collection:</para>
 
         <para>To install the <application>KDE</application> package
           from the network, simply type:</para>
 
         <screen>&prompt.root; <userinput>pkg_add -r kde</userinput></screen>
 
 	<para>&man.pkg.add.1; will automatically fetch the latest version
 	  of the application.</para>
 
         <para>To build <application>KDE</application> from source,
           use the ports tree:</para>
 
         <screen>&prompt.root; <userinput>cd /usr/ports/x11/kde3</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
 
         <para>After <application>KDE</application> has been installed,
           the X server must be told to launch this application
           instead of the default window manager.  This is accomplished
           by editing the <filename>.xinitrc</filename> file:</para>
 
         <screen>&prompt.user; <userinput>echo "exec startkde" &gt; ~/.xinitrc</userinput></screen>
 
 	<para>Now, whenever the X Window System is invoked with
 	  <command>startx</command>,
           <application>KDE</application> will be the desktop.</para>
 
         <para>If a display manager such as
           <application>XDM</application> is being used, the
           configuration is slightly different.  Edit the
           <filename>.xsession</filename> file instead.  Instructions
           for <application>kdm</application> are described later in
           this chapter.</para>
       </sect3>
     </sect2>
 
     <sect2 id="x11-wm-kde-details">
         <title>More Details on KDE</title>
 
         <para>Now that <application>KDE</application> is installed on
           the system, most things can be discovered through the
           help pages, or just by pointing and clicking at various menus.
           &windows; or &mac; users will feel quite at home.</para>
 
         <para>The best reference for <application>KDE</application> is
           the on-line documentation.  <application>KDE</application>
           comes with its own web browser,
           <application>Konqueror</application>, dozens of useful
           applications, and extensive documentation.  The remainder of
           this section discusses the technical items that are
           difficult to learn by random exploration.</para>
 
       <sect3 id="x11-wm-kde-kdm">
         <title>The KDE Display Manager</title>
 
         <indexterm><primary>KDE</primary>
           <secondary>display manager</secondary></indexterm>
         <para>An administrator of a multi-user system may wish to have
           a graphical login screen to welcome users.
           <link linkend="x-xdm">XDM</link> can be
           used, as described earlier.  However,
           <application>KDE</application> includes an
           alternative, <application>kdm</application>, which is designed
           to look more attractive and include more login-time options.
           In particular, users can easily choose (via a menu) which
           desktop environment (<application>KDE</application>,
           <application>GNOME</application>, or something else) to run
           after logging on.</para>
 
         <para>To begin with, run the <application>KDE</application>
           control panel, <command>kcontrol</command>, as
           <username>root</username>.  It is generally considered
           unsafe to run the entire X environment as
           <username>root</username>.  Instead, run the window manager
           as a normal user, open a terminal window (such as
           <filename>xterm</filename> or <application>KDE</application>'s
           <filename>konsole</filename>), become <username>root</username>
           with <userinput>su</userinput> (the user must be in the
           <groupname>wheel</groupname>
           group in <filename>/etc/group</filename> for this), and then
           type <userinput>kcontrol</userinput>.</para>
 
 	<para>Click on the icon on the left marked
 	  <guibutton>System</guibutton>, then on <guibutton>Login
 	  manager</guibutton>.  On the right there are
           various configurable options, which the
           <application>KDE</application> manual will explain in greater
           detail.  Click on <guibutton>sessions</guibutton> on the right.
           Click <guibutton>New type</guibutton> to add various window
           managers and desktop environments.  These are just labels,
           so they can say <application>KDE</application> and
           <application>GNOME</application> rather than
           <application>startkde</application> or
           <application>gnome-session</application>.
           Include a label <literal>failsafe</literal>.</para>
 
         <para>Play with the other menus as well, they are mainly
           cosmetic and self-explanatory.  When you are done, click on
           <guibutton>Apply</guibutton> at the bottom, and quit the
           control center.</para>
 
         <para>To make sure <application>kdm</application> understands
           what the labels (<application>KDE</application>,
           <application>GNOME</application> etc) mean, edit the files used
           by <link linkend="x-xdm">XDM</link>.
           <note><para>In <application>KDE 2.2</application> this has
             changed: <application>kdm</application> now uses its own
             configuration files.  Please see the <application>KDE
             2.2</application> documentation for details.</para>
           </note>
           In a terminal window, as <username>root</username>,
           edit the file
           <filename>/usr/X11R6/lib/X11/xdm/Xsession</filename>.  There is
           a section in the middle like this:</para>
 
 	<screen>case $# in
 1)
         case $1 in
         failsafe)
                 exec xterm -geometry 80x24-0-0
                 ;;
         esac
 esac</screen>
 
         <para>A few lines need to be added to this section.
           Assuming the labels from used were <quote>KDE</quote> and
           <quote>GNOME</quote>,
           use the following:</para>
 
 	<screen>case $# in
 1)
         case $1 in
         kde)
                 exec /usr/local/bin/startkde
                 ;;
         GNOME)
                 exec /usr/X11R6/bin/gnome-session
                 ;;
         failsafe)
                 exec xterm -geometry 80x24-0-0
                 ;;
         esac
 esac</screen>
 
         <para>For the <application>KDE</application>
           login-time desktop background to be honored,
           the following line needs to be added to
           <filename>/usr/X11R6/lib/X11/xdm/Xsetup_0</filename>:</para>
 
         <screen>/usr/local/bin/krootimage</screen>
 
         <para>Now, make sure <application>kdm</application> is listed in
           <filename>/etc/ttys</filename> to be started at the next bootup.
           To do this, simply follow the instructions from the previous
           section on <link linkend="x-xdm">XDM</link> and replace
           references to the <command>/usr/X11R6/bin/xdm</command>
           program with <command>/usr/local/bin/kdm</command>.</para>
       </sect3>
 
       <sect3 id="x11-wm-kde-antialias">
         <title>Anti-aliased Fonts</title>
 
         <indexterm><primary>KDE</primary>
           <secondary>anti-aliased fonts</secondary></indexterm>
         <para>X11
 	  supports anti-aliasing via
 	  its <quote>RENDER</quote> extension, and starting with version 2.3,
 	  Qt (the toolkit used by <application>KDE</application>) supports
 	  this extension.  Configuring this is described in <xref
           linkend="antialias"> on antialiasing X11 fonts.  So, with
           up-to-date software, anti-aliasing is possible on a
           <application>KDE</application> desktop.  Just go to the KDE
 	  menu, go to
 	  <menuchoice>
 	    <guimenu>Preferences</guimenu>
 	    <guisubmenu>Look and Feel</guisubmenu>
 	    <guimenuitem>Fonts</guimenuitem></menuchoice>, and click on the check box
           <guibutton>Use Anti-Aliasing for Fonts and Icons</guibutton>.
           For a Qt application which is not part of
 	  <application>KDE</application>, the environment variable
 	  <varname>QT_XFT</varname> needs to be set to <literal>true</literal>
 	  before starting the program.</para>
 
        </sect3>
      </sect2>
 
      <sect2 id="x11-wm-xfce">
          <title>XFce</title>
        <sect3 id="x11-wm-xfce-about">
          <title>About XFce</title>
 
         <para><application>XFce</application> is a desktop environment
           based on the GTK+
           toolkit used by <application>GNOME</application>, but is much
           more lightweight and meant for those who want a simple,
           efficient desktop which is nevertheless easy to use and
           configure.  Visually, it looks very much like
           <application>CDE</application>, found on commercial &unix;
           systems.  Some of <application>XFce</application>'s features
           are:</para>
 
          <itemizedlist>
            <listitem>
 	     <para>A simple, easy-to-handle desktop</para>
            </listitem>
 
            <listitem>
 	     <para>Fully configurable via mouse, with drag and
                drop, etc </para>
            </listitem>
 
            <listitem>
 	     <para>Main panel similar to <application>CDE</application>, with
 	       menus, applets and applications launchers</para>
            </listitem>
 
            <listitem>
 	     <para>Integrated window manager, file manager, sound manager,
 	       <application>GNOME</application> compliance module, and other
 	       things</para>
            </listitem>
 
            <listitem>
 	     <para>Themeable (since it uses GTK+)</para>
            </listitem>
 
            <listitem>
 	     <para>Fast, light and efficient: ideal for older/slower machines
 	       or machines with memory limitations</para>
            </listitem>
          </itemizedlist>
 
          <para>More information on <application>XFce</application>
           can be found on the <ulink url="http://www.xfce.org/">XFce
             website</ulink>.</para>
        </sect3>
 
        <sect3 id="x11-wm-xfce-install">
          <title>Installing XFce</title>
 
         <para>A binary package for <application>XFce</application>
           exists (at the time of writing).  To install, simply type:</para>
 
         <screen>&prompt.root; <userinput>pkg_add -r xfce4</userinput></screen>
 
         <para>Alternatively, to build from source, use the ports
           collection:</para>
 
         <screen>&prompt.root; <userinput>cd /usr/ports/x11-wm/xfce4</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
 
         <para>Now, tell the X server to launch
          <application>XFce</application> the next time X is started.
          Simply type this:</para>
 
         <screen>&prompt.user; <userinput>echo "/usr/X11R6/bin/startxfce4" &gt; ~/.xinitrc</userinput></screen>
 
         <para>The next time X is started,
           <application>XFce</application> will be the desktop.
           As before, if a display manager like
           <application>XDM</application> is being used, create an
           <filename>.xsession</filename>, as described in the
           section on <link linkend="x11-wm-gnome">GNOME</link>, but
           with the <filename>/usr/X11R6/bin/startxfce4</filename>
           command; or, configure the display manager to allow
           choosing a desktop at login time, as explained in
           the section on <link linkend="x11-wm-kde-kdm">kdm</link>.</para>
       </sect3>
     </sect2>
   </sect1>
 
 </chapter>
 
 <!--
      Local Variables:
      mode: sgml
      sgml-declaration: "../chapter.decl"
      sgml-indent-data: t
      sgml-omittag: nil
      sgml-always-quote-attributes: t
      sgml-parent-document: ("../book.sgml" "part" "chapter")
      End:
 -->
diff --git a/zh_TW.Big5/books/porters-handbook/book.sgml b/zh_TW.Big5/books/porters-handbook/book.sgml
index b9a77a6283..f160957394 100644
--- a/zh_TW.Big5/books/porters-handbook/book.sgml
+++ b/zh_TW.Big5/books/porters-handbook/book.sgml
@@ -1,9888 +1,9957 @@
 <!--
      The FreeBSD Documentation Project
 
      Original Revision: 1.645
      $FreeBSD$
 -->
 
 <!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
 <!ENTITY % books.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Books Entity Set//EN">
 %books.ent;
 ]>
 
 <book>
   <bookinfo>
     <title>FreeBSD Porter's Handbook</title>
 
     <authorgroup>
       <corpauthor>FreeBSD ¤å¥ó­p¹º</corpauthor>
     </authorgroup>
 
     <pubdate>April 2000</pubdate>
 
     <copyright>
       <year>2000</year>
       <year>2001</year>
       <year>2002</year>
       <year>2003</year>
       <year>2004</year>
       <year>2005</year>
+      <year>2006</year>
       <holder role="mailto:doc@FreeBSD.org">FreeBSD ¤å¥ó­p¹º</holder>
     </copyright>
 
     &bookinfo.trademarks;
 
     &bookinfo.legalnotice;
   </bookinfo>
 
     <chapter id="why-port">
       <title>·¤¤l</title>
 
       <para>´X¥G¨C­Ó FreeBSD ·R¥ÎªÌ³£¬O³z¹L FreeBSD Ports Collection
 	¨Ó¸Ë¦U¦¡À³¥Îµ{¦¡("ports")¡C¦p¦P FreeBSD ªº¨ä¥L³¡¤À¤@¼Ë¡A
 	³o¨Ç ports ³£¥D­n¨Ó¦Û³\¦h§Ó¤uªº§V¤O¦¨ªG¡A©Ò¥H¦b¾\Ū³o¥÷¤å¥ó®É¡A
 	½Ð°È¥²·P®¦¦b¤ß¡C</para>
 
       <para>¦b FreeBSD ¤W­±¡A¨C­Ó¤H³£¥i¥H´£¥æ·sªº port¡A
 	©Î°²¦p¸Ó port ¨Ã¨S¦³¤HºûÅ@ªº¸Ü¡A¥i¥H¦ÛÄ@ºûÅ@ &mdash; 
 	³oÂI¨Ã¤£»Ý­n¥ô¦ó commit ªºÅv­­¡A´N¥i¥H¨Ó°µ³o¥ó¨Æ±¡¡C</para>
 
     </chapter>
 
     <chapter id="own-port">
-      <title>¦Û¦æ»s§@ port</title>
+      <title>¦Û¦æ¥´³y port</title>
 
       <para>¨º»ò¡A¶}©l¹ï¦Û¦æ»s§@ port ©Î§ó·s²{¦³ port
 	¦³¤@¨Ç¿³½ì¤F¶Ü¡H¤Ó¦nÅo¡I</para>
 
       <para>¤U­±±N¤¶²Ð¤@¨Ç«Ø¥ß port ®É¸Óª`·Nªº¨Æ¶µ¡C¦pªG¬O·Q¤É¯Å²{¦³ªº port
 	¡A¨º»ò¤]½Ð°Ñ¾\ <xref linkend="port-upgrading"> »¡©ú¡C</para>
 
       <para>¦]¬°³o¥÷¤å¥ó¥i¯àÁ¿±o¤£¬O¤Q¤À¸Ô²Ó¡A¥i¯à»Ý­n°Ñ¦Ò 
 	<filename>/usr/ports/Mk/bsd.port.mk</filename>
 	³oÀɬO©Ò¦³ port ªº Makefile Àɳ£·|¥Î¨ìªº¡C´Nºâ§A¤£¬O¨C¤Ñ¤£Â_ hacking Makefiles
 	¡A¤]³£¥i¥HÂǥѥ¦¨Ó¹ï¾ã­Ó port ¾÷¨î¡BMakefile §óÁA¸Ñ¡A¸Ì­±ªºµùÄÀ¬Û·í¸Ô²Ó¡C
 	¦¹¥~¡A­Y¦³¨ä¥L¯S©w port ªº°ÝÃD¡A¤]¥i¥H¨ì &a.ports; ¨ÓÀò±oµª®×¡C</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>
     </chapter>
 
     <chapter id="quick-porting">
       <title>¥´³y Port §Ö³t¤W¤â½g</title>
 
       <para>¥»¸`¥D­n¤¶²Ð¦p¦ó¨Ó§Ö³t¥´³y port¡AµM¦Ó¡A«Ü¦h®É­Ô³o¨Ç¤º®e¨Ã¤£¬O«Ü°÷¥Î¡A
 	«Øij¾\Ū¥»¤å¥ó¤¤§ó²`¶øªº¦a¤è¡C</para>
 
       <para>­º¥ý¨ú±o¸ÓÀ³¥Îµ{¦¡ªº­ì©lµ{¦¡½XÀ£ÁYÀÉ(tarball)¡A¨Ã§â¥¦©ñ¨ì
 	<makevar>DISTDIR</makevar>¡A¹w³]¸ô®|À³¸Ó¬O
 	<filename>/usr/ports/distfiles</filename>¡C</para>
 
       <note>
 	<para>¤U­±ªº¨Ò¤l¡A¬O°²³]¨Ã¤£»Ý­n¦A­×§ï¸ÓÀ³¥Îµ{¦¡ªº­ì©l½X¡A´N¥i¥H¦b
 	  FreeBSD ¤W½sĶ¦¨¥\ªº¡F°²¦pÁٻݭn¥t¥~­×§ï¤~¯à¦¨¥\½sĶªº¸Ü¡A¨º»ò½Ð°Ñ¦Ò¤U¤@³¹ªº»¡©ú¡C
 	  </para>
       </note>
 
       <sect1 id="porting-makefile">
 	<title>½s¼g <filename>Makefile</filename></title>
 
 	<para>³Ì²³æªº <filename>Makefile</filename> ¤j·§¬O¹³³o¼Ë¡G</para>
 
 	<programlisting># New ports collection makefile for:   oneko
 # Date created:        5 December 1994
 # Whom:                asami
 #
 # &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=       A cat chasing a mouse all over the screen
 
 MAN1=          oneko.1
 MANCOMPRESSED= yes
 USE_IMAKE=     yes
 
 .include &lt;bsd.port.mk&gt;</programlisting>
 
 	<para>¶â¡A¤j­P´N¬O³o¼Ë¡A¬Ý¬Ý§A¤w¸g»â²¤¦h¤Ö¤F©O¡H¬Ý¨ì <literal>&dollar;FreeBSD&dollar;</literal>
 	  ³o¤@¦æªº¸Ü¡A§O·Q¤Ó¦h¡A¥¦¬O CVS ID tag ¥Î³~¡A·í¸Ó port ¥¿¦¡¶i¤J port tree ®É¡A´N·|¦Û°ÊÂà´«¬°¬ÛÃö¦r¦êÅo¡C
 	  ¦³Ãö³oÂIªº²Ó¸`³¡¥÷¡A¥i¥H°Ñ¾\ <link linkend="porting-samplem">sample Makefile</link> ³¹¸`¡C</para>
       </sect1>
 
       <sect1 id="porting-desc">
 	<title>¼¶¼g¸Ó³nÅ骺»¡©úÀÉ</title>
 
-	<para>µL½×¬O§_¥´ºâ¦A¥[¤u°µ¦¨ package¡A¦³ 2 ­Ó»¡©úÀɬO¥ô¦ó¹êÅé port (Slave port«h¤£¤@©w)³£¥²¶·­n¨ã³Æªº¡C
+	<para>µL½×¬O§_¥´ºâ¦A¥[¤u°µ¦¨ package¡A¦³ 2 ­ÓÀɮ׬O¥ô¦ó¹êÅé port (Slave port«h¤£¤@©w)³£¥²¶·­n¨ã³Æªº¡C
 	  ³o 2 ­ÓÀɤÀ§O¬O <filename>pkg-descr</filename> ÀɤÎ
 	  <filename>pkg-plist</filename> ÀÉ¡C³o¨â­ÓÀÉ®×ÀɦW«e­±³£¦³ <filename>pkg-</filename>
 	  ¥H¸ò¨ä¥LÀÉ®×°µ°Ï§O¡C</para>
 
 	<sect2>
 	  <title><filename>pkg-descr</filename></title>
 
 	  <para>³o¬O¦¹ port ªº¸Ô²Ó»¡©úÀÉ¡A½Ð¥Î¤@¬q©Î´X¬q¤å¦r¨Ó»¡©ú¸Ó port ªº§@¥Î¡A¨Ãªþ¤W WWW 
 	  ºô§}(­Y¦³ªº¸Ü)</para>
 
 	  <note><para>½Ðª`·N¡A³oÀɵ´«D¡u¸Ó³nÅ骺»¡©ú¤â¥U¡v©Î¬O¡u¦p¦ó½sĶ¡B¨Ï¥Î¸Ó port ªº»¡©ú¡v¡C
 	      ­Y¬O±q¸Ó³nÅ骺 <filename>README</filename> ©Î manpage ª½±µ½Æ»s¹L¨Óªº¸Ü¡A
 	      ½Ðª`·N¡A¦]¬°¥¦­Ì³q±`³£¼g±o¤Ó¸Ô²Ó¡B®æ¦¡¸û¯S§O(¤ñ¦p manpage ·|¦Û°Ê½Õ¾ãªÅ¥Õ)¡A
 	      ½Ð¾¨¶qÁקK³o¨Ç¤¾ªøÂصü©Î±Ä¥Î¯S®í®æ¦¡¡C­Y¸Ó³nÅ馳©x¤èª©­º­¶ªº¸Ü¡A½Ð¦b¦¹¦C¥X¨Ó¡C
 	      ¨C­Óºô§}½Ð¥Î <literal>WWW:</literal> §@¬°¶}ÀY¡A³o¼Ë¤l¬ÛÃö¤u¨ãµ{¦¡´N·|¦Û°Ê³B²z§¹²¦¡C<para>
 	  </note>
 
-	  <para>¸Ó port
-	    ªº <filename>pkg-descr</filename> ¤º®e¡A¤j­P¦p¤U­±¨Ò¤l:</para>
+	  <para>¸Ó port ªº <filename>pkg-descr</filename> ¤º®e¡A¤j­P¦p¤U­±¨Ò¤l¡G</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> or
-	    <filename>/usr/X11R6</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>³o¬O¸Ó port ©Ò·|¸Ëªº©Ò¦³ÀɮײM³æ¡A¥t¥~¦]¬° package ·|¥Ñ³o²M³æ©Ò²£¥Í¡A¦]¦¹¤]³QºÙ¬°¡ypacking list
+		(¥´¥]²M³æ)¡z¡C ¥H <literal>${PREFIX}</literal> ¬°°ò·ÇÂI¡A¦Ó¥Î¬Û¹ï¸ô®|ªí¥Ü¡C
+		(<literal>${PREFIX}</literal> ³q±`¬O <filename>/usr/local</filename> ©Î
+	    	<filename>/usr/X11R6</filename>)   ¦ý¬O¦pªG¸Óµ{¦¡¦³¦w¸Ë man page ªº¸Ü¡A«h­n¥HÃþ¦ü 
+		<makevar>MAN<replaceable>n</replaceable>=</makevar> ªº¤è¦¡¼g¦b
+		<filename>Makefile</filename> ¤º¡A¤£¯à¦C¦b <filename>pkg-plist</filename> ®@¡C
+		 °£¤F¦C¥XÀÉ®×¥H¥~¡A¤]­n§â¸Ó port ©Ò·|«Ø¥ßªº¥Ø¿ý¤]¦C¶i¥h¡A¤è¦¡¦³¨âºØ¡G¤@ºØ¬O¼g¦b 
+		<filename>pkg-plist</filename> ¤ºªº¤è¦¡¡A¤ñ¦p¡G
+	    	<literal>@dirrm</literal> ¡C¦Ü©ó¥t¥~¤@ºØ¤è¦¡¡A«h¬O¼g¦b <filename>Makefile</filename> ¤º¡A¤ñ¦p
+		¡G<literal>PLIST_FILES=</literal> ¤§Ãþªº¤è¦¡¡C</para>
 
-	  <para>Here is a small example:</para>
+	  <para>¸Ó port ªº <filename>pkg-plist</filename> ¤º®e¡A¤j­P¦p¤U­±¨Ò¤l:</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>
+	  <para>Ãö©ó packing list ¤è­±¡A¥i¥H°Ñ¾\ &man.pkg.create.1; ·|¦³¸Ô¸Ñ¡C</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>
+	    <para>«Øij²M³æ¤ºªºÀɦW¡A¨Ì·Ó¦r¥À¶¶§Ç§@±Æ§Ç¡A¨º»ò¤U¦¸­n¤É¯Å®É¡A·|¤ñ¸û²M·¡¡B¤è«K¨Ó§ó·s³o¥÷²M³æ¡C </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>
+	    <para>¤â°Ê¥Í³o¥÷²M³æ¹ê¦b¤Ó­W¤F¡C¤×¨ä­Y¸Ó port ·|¸Ë¤@¤j°ïÀɮתº¸Ü¡A½Ð¦hµ½¥Î <link
+		linkend="plist-autoplist">¦Û°Ê²£¥Í packing list</link> ·|¤ñ¸û¬Ù®É¬Ù¤O­ò¡C</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
+	  <para>¥u¦³¦b¤@ ºØ±¡ªp¤U¥i¥H¬Ù²¤¤£¥Î¥Í <filename>pkg-plist</filename> ÀÉ¡C  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 fulfil
 	    <link linkend="plist">more sophisticated
 	    tasks</link>.</para>
 	</sect2>
       </sect1>
 
       <sect1 id="porting-checksum">
-	<title>Creating the checksum file</title>
+	<title>²£¥Í checksum ¥Î³~ªº distinfo ÀÉ</title>
 
-	<para>Just type <command>make makesum</command>. The ports make rules
-	  will automatically generate the file
-	  <filename>distinfo</filename>.</para>
+	<para>¥u­n¥´¡y<command>make makesum</command>¡z´N¦n¤F¡A±µ¤U¨Ó´N·|¦Û°Ê²£¥Í¬Û¹ïÀ³ªº 
+	  <filename>distinfo</filename> ÀÉ­ù¡C</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>
+	<title>ÀËÅç port ¬O§_§¹¾ã¡B¥i¦æ</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>
+	  <title>«Øij±Ä¦æªº´ú¸Õ¶¶§Ç¡G</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>
 	</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>
       </sect1>
 
       <sect1 id="porting-portlint">
-	<title>Checking your port with <command>portlint</command></title>
+	<title>¥H <command>portlint</command> ¨Ó§@ÀËÅç</title>
 
 	<para>Please use <command>portlint</command> to see if your port
 	  conforms to our guidelines.  The <filename role="package">
 	  devel/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 port</title>
+	<title>´£¥æ(Submit) port</title>
 
 	<para>First, 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 FreeBSD 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, simply include the output of <command>shar `find
 	    port_dir`</command> 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 and
 	  the shar 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 and
 	    <quote>Update port: &lt;category&gt;/&lt;portname&gt;
 	    &lt;short description of the update&gt;</quote> for port updates.
 	    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>.</para>
 
 	<para>After you have submitted your port, please be patient.
 	  Sometimes it can take a few months before a port is included
 	  in FreeBSD, 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
 	  waiting to be committed to FreeBSD</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 appear in the list of
 	  <ulink url="&url.articles.contributors;/contrib-additional.html">Additional FreeBSD Contributors</ulink>
 	  and other files. Isn't that great?!? <!-- smiley
 	  -->:-)</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>:-&gt;</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 gzip'd
 	      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!</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.Z</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 FreeBSD.  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 FreeBSD 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 recursive &man.diff.1;
 	  for later feeding to &man.patch.1;.  Each set of patches you
 	  wish to apply should be collected into a file named
 	  <filename>patch-<replaceable>*</replaceable></filename> where
 	  <replaceable>*</replaceable> indicates
 	  the pathnames of the files that are patched,
 	  such as <filename>patch-Imakefile</filename> or
 	  <filename>patch-src-config.h</filename>.  These files should
 	  be stored in <makevar>PATCHDIR</makevar>, 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>).</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 path and file name
 	  in patch names.</para>
 
 	<para>Do not put RCS strings in patches.  CVS 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_AUTOCONF_VER=213</literal> and take the
+	  lines!); define <literal>USE_AUTOTOOLS=autoconf:253</literal> and take the
 	  diffs of <filename>configure.in</filename>.</para>
 
 	<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 those files from CR/LF to just LF, you can do
 	  something like this:</para>
 
 	<programlisting>USE_REINPLACE=	yes
 
 post-extract:
 	@${FIND} -E ${WRKDIR} -type f -iregex ".*\.(c|cpp|h|txt)" -print0 | \
 		${XARGS} -0 ${REINPLACE_CMD} -e 's/[[:cntrl:]]*$$//'</programlisting>
 
 	<para>Of course, if you need to process each and every file,
 	  <option>-iregex</option> above can be omitted.  Be aware that this
 	  piece of code will strip all trailing control characters from each
 	  line of processed file (except <literal>\n</literal>).</para>
 
 	<para>Also, 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.  Once you are happy with the resulting diff, please split
 	  it up into one source file per patch file.</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
 	  gzip'd 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.  (The most common case is
 	  <literal>EXTRACT_SUFX=.tar.Z</literal>, when the tarball is
 	  condensed by regular <command>compress</command>, not
 	  <command>gzip</command>.)</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>
 
 	  <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 pre-empt
 	    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 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 <filename>name</filename> part
 	    should be lowercase.  (The rest of the name can 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>.  If the software in question
 	    has numbers, hyphens, or underscores in its name, you may include
 	    them as well (like <literal>kinput2</literal>).</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
 	    papersize 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><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.</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>XFree86-3.3.6</entry>
 	      <entry>(empty)</entry>
 	      <entry>XFree86</entry>
 	      <entry>(empty)</entry>
 	      <entry>3.3.6</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>Papersize 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><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>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>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>graphics</filename></entry>
 		<entry>Graphics utilities.</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 language.</entry>
 		<entry>The <filename>java</filename> category shall 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">K Desktop Environment (KDE)</ulink>
 		  Project.</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>news</filename></entry>
 		<entry>USENET news software.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>offix*</filename></entry>
 		<entry>Ports from the <ulink url="http://leb.net/offix/">OffiX</ulink> suite.</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>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>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>sysutils</filename></entry>
 		<entry>System utilities.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>tcl80*</filename></entry>
 		<entry>Ports that use Tcl version 8.0 to run.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>tcl81*</filename></entry>
 		<entry>Ports that use Tcl version 8.1 to run.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>tcl82*</filename></entry>
 		<entry>Ports that use Tcl version 8.2 to run.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>tcl83*</filename></entry>
 		<entry>Ports that use Tcl version 8.3 to run.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>tcl84*</filename></entry>
 		<entry>Ports that use Tcl version 8.4 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>tk80*</filename></entry>
 		<entry>Ports that use Tk version 8.0 to run.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>tk82*</filename></entry>
 		<entry>Ports that use Tk version 8.2 to run.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>tk83*</filename></entry>
 		<entry>Ports that use Tk version 8.3 to run.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>tk84*</filename></entry>
 		<entry>Ports that use Tk version 8.4 to run.</entry>
 		<entry></entry>
 	      </row>
 
 	      <row>
 		<entry><filename>tkstep80*</filename></entry>
 		<entry>Ports that use TkSTEP version 8.0 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).
 		  If your port <emphasis>is</emphasis> an X
 		  application, define <makevar>USE_XLIB</makevar> (implied by
 		  <makevar>USE_IMAKE</makevar>) and put it in the appropriate
 		  category.</entry>
 	      </row>
 
 	      <row>
 		<entry><filename>x11-clocks</filename></entry>
 		<entry>X11 clocks.</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 relating 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>mbone</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><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;/#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>s 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="1">
 	  <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 X-contrib, 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_XCONTRIB</makevar> and
 	  <makevar>MASTER_SITE_PERL_GNU</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_XCONTRIB}
 MASTER_SITE_SUBDIR=   applications</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>The user can also set the <makevar>MASTER_SITE_*</makevar>
 	  variables in <filename>/etc/make.conf</filename> to override our
 	  choices, and use their favorite mirrors of these popular archives
 	  instead.</para>
       </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> and <makevar>USE_ZIP</makevar>
 	  variables automatically set <makevar>EXTRACT_SUFX</makevar> to
 	  <literal>.tar.bz2</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 gzip'd 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 gzip'd or compress'd 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>
 	  hereon.</para>
 
 	<para>A little background first.  OpenBSD has a neat feature
 	  inside both <makevar>DISTFILES</makevar> and
 	  <makevar>PATCHFILES</makevar> variables, both files and
 	  patches can be postfixed with <literal>:n</literal>
 	  identifiers where <literal>n</literal> both can be
 	  <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
 	  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 1 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 1 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
 
 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
 
 MASTER_SITES=   alpha:DEFAULT alpha:SOME_SITE
 
 MASTER_SITES=   alpha:SOME_SITE,DEFAULT
 
 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> -> old:n</para>
+			  <literal>DEFAULT</literal> -&gt; old:n</para>
 		      </listitem>
 
 		      <listitem>
 			<para>Directories within group
-			  <literal>NEW</literal> -> new</para>
+			  <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>
     </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>For a detailed description of the responsibilities of maintainers,
 	  refer to the <ulink url="&url.books.developers-handbook;/policies.html#POLICIES-MAINTAINER">MAINTAINER on
 	    Makefiles</ulink> section.</para>
 
 	<para>If the maintainer of a port does not respond to an update
 	  request from a user 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>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.
 	  <emphasis>Please</emphasis> do not include the package name (or
 	  version number of the software) in the comment.  The comment
 	  should begin with a capital and end without a period.  Here
 	  is an example:</para>
 
 	<programlisting>COMMENT=       A 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>
 
 	<para>Please try to keep the COMMENT line less than 70
 	  characters, as it is displayed to users as a one-line
 	  summary of the port.</para>
       </sect1>
 
       <sect1 id="makefile-depend">
 	<title>Dependencies</title>
 
 	<para>Many ports depend on other ports.  There are seven variables that
 	  you can use 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,
 	    <programlisting>LIB_DEPENDS=   jpeg.9:${PORTSDIR}/graphics/jpeg:install</programlisting>
 	    will check for a shared jpeg library with major version 9, 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.[5-7]</literal> and <literal>intl</literal> are
 	      allowed.  The first pattern,
 	      <literal>intl.[5-7]</literal>, will match any of:
 	      <literal>intl.5</literal>, <literal>intl.6</literal> or
 	      <literal>intl.7</literal>.  The second pattern,
 	      <literal>intl</literal>, will match any version of the
 	      <literal>intl</literal> library.</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}/etc/innd:${PORTSDIR}/news/inn \
 	       wish8.0:${PORTSDIR}/x11-toolkits/tk80</programlisting>
 
 	  <para>will check if the file or directory
 	    <filename>/usr/local/etc/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>wish8.0</command> is in the search
 	    path, and descend into the <filename>x11-toolkits/tk80</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:/usr/X11R6/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>
 	</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, <programlisting> BUILD_DEPENDS=
 	      unzip:${PORTSDIR}/archivers/unzip</programlisting> 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, <programlisting> FETCH_DEPENDS=
 	      ncftp2:${PORTSDIR}/net/ncftp2</programlisting> 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, <programlisting>EXTRACT_DEPENDS=
 	      unzip:${PORTSDIR}/archivers/unzip</programlisting> 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, <programlisting> PATCH_DEPENDS=
 	      ${NONEXISTENT}:${PORTSDIR}/java/jfc:extract
 		</programlisting>will descend into the
 	    <filename>java/jfc</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>patch</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>DEPENDS</makevar></title>
 
 	  <para>If there is a dependency that does not fall into either of the
 	    above categories, or your port requires having the source of
 	    the other port extracted in addition to having it installed,
 	    then use this variable.  This is a list of
 	    <replaceable>dir</replaceable><optional><replaceable>:target</replaceable></optional>,
 	    as there is nothing to check, unlike the previous four.  The
 	    <replaceable>target</replaceable> part can be omitted if it is the
 	    same as <makevar>DEPENDS_TARGET</makevar>.</para>
 	</sect2>
 
 	<sect2 id="use-vars">
 	<title><makevar>USE_<replaceable>*</replaceable></makevar></title>
 
 	<para>A number of variables exist in order to encapsulate common
 	  dependencies that many ports have.  Although their use is
 	  optional, they can help to reduce the verbosity of the port
 	  <filename>Makefile</filename>s.  Each of them is styled
 	  as <makevar>USE_<replaceable>*</replaceable></makevar>.  The
 	  usage of these variables is restricted to the port
 	  <filename>Makefile</filename>s and
 	  <filename>ports/Mk/bsd.*.mk</filename> and is not designed
 	  to encapsulate user-settable options &mdash; use
 	  <makevar>WITH_<replaceable>*</replaceable></makevar> and
 	  <makevar>WITHOUT_<replaceable>*</replaceable></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 <programlisting>USE_GCC=3.2</programlisting>
 	    would adds a dependency on gcc32 for every port,
 	    including gcc32 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_BISON</makevar></entry>
 
 		<entry>The port uses <command>bison</command> for
 		  building.</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.2</literal>.
 		  The minimal required version can be specified as
 		  <literal>3.2+</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.
 		  <makevar>USE_GCC</makevar> can't be used together with
-		  <makevar>USE_LIBTOOL_VER</makevar>.</entry>
+		  <makevar>USE_AUTOTOOLS=libtool:<replaceable>XX</replaceable></makevar>.</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">.
 	    Finally, <xref linkend="using-sdl"> provides variables used for
 	    <application>SDL</application> applications.</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
 
 	    <programlisting>BUILD_DEPENDS=   ${NONEXISTENT}:${PORTSDIR}/graphics/jpeg:extract</programlisting>
 
 	    will always descend to the <literal>jpeg</literal> port and extract it.</para>
 
 	  <para>Do not use <makevar>DEPENDS</makevar> unless there is no other
 	    way the behavior you want can be accomplished.  It will cause the
 	    other port to always be built (and installed, by default), and the
 	    dependency will go into the packages as well.  If this is really
 	    what you need, you should probably write it as
 	    <literal>BUILD_DEPENDS</literal> and
 	    <literal>RUN_DEPENDS</literal> instead&mdash;at least the
 	    intention will be clear.</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>
 
       </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 && ${RESOLUTION} != 240 && \
        ${RESOLUTION} != 300 && ${RESOLUTION} != 400
        @${ECHO} "Error: invalid value for RESOLUTION: \"${RESOLUTION}\""
        @${ECHO} "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>Manpages</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>NOMANCOMPRESS</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>NOMANCOMPRESS</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>${PREFIX}/man/man1/foo.1.gz
 ${PREFIX}/man/ja/man1/foo.1.gz
 ${PREFIX}/share/foobar/man/man3/bar.3.gz
 ${PREFIX}/share/foobar/man/ja/man3/bar.3.gz
 ${PREFIX}/man/man4/baz.4.gz
 ${PREFIX}/man/ja/man4/baz.4.gz</programlisting>
 
       <para>Additionally <filename>${PREFIX}/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>
 
     </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>), and 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>Some large applications can be built in a number of
 	configurations, adding functionality if one of a number of
 	libraries or applications is available.  Examples include
 	choice of natural (human) language, GUI versus command-line,
 	or type of database to support.  Since not all users
 	want those libraries or applications, the ports system
 	provides hooks that the port author can use to control which
 	configuration should be built. Supporting these properly will
 	make users happy, and effectively provide 2 or more ports for the
 	price of one.</para>
 
       <sect2>
           <title><makevar>KNOBS</makevar></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
 	    <filename>ports/Mk/bsd.*.mk</filename>; others are not,
 	    which can be confusing.  If you need to add such a
 	    configuration variable, please consider using one of the
 	    ones from the following list.</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
 	      some kind of variable such as <literal>YES</literal> or
 	      <literal>NO</literal>.</para>
 	  </note>
 
 	  <table frame="none">
 	    <title>The <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>
 		  <entry><makevar>WITH_APACHE2</makevar></entry>
 
 		  <entry>If set, use
 		    <filename role="package">www/apache2</filename>
 		    instead of the default of
 		    <filename role="package">www/apache</filename>.</entry>
 	        </row>
 
 	        <row>
 		  <entry><makevar>WITH_BERKELEY_DB</makevar></entry>
 
 		  <entry>Define this variable to specify the ability to
 		    use a variant of the Berkeley database package such as
 		    <filename role="package">databases/db41</filename>.
 		    An associated variable,
 		    <makevar>WITH_BDB_VER</makevar>, may be
 		    set to values such as 2, 3, 4, 41 or 42.</entry>
 	        </row>
 
 	        <row>
 		  <entry><makevar>WITH_MYSQL</makevar></entry>
 
 		  <entry>Define this variable to specify the ability to
 		    use a variant of the MySQL database package such as
 		    <filename role="package">databases/mysql40-server</filename>.
 		    An associated variable,
 		    <makevar>WANT_MYSQL_VER</makevar>, may be
 		    set to values such as 323, 40, 41, or 50.</entry>
 	        </row>
 
 	        <row>
 		  <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>Use the version of OpenSSL from
 		    <filename role="package">security/openssh</filename>,
 		    overwriting the version that was originally installed
 		    in the base system.</entry>
 	        </row>
 
 	        <row>
 		  <entry><makevar>WITH_POSTGRESQL</makevar></entry>
 
 		  <entry>Define this variable to specify the ability to
 		    use a variant of the PostGreSQL database package such as
 		    <filename role="package">databases/postgresql72</filename>.
 		    </entry>
 	        </row>
 
 	        <row>
 		  <entry><makevar>WITHOUT_X11</makevar></entry>
 
 		  <entry>If the port can be built both with and without
 		    X support, then it should normally be built with
 		    X support. If this variable is defined, then
 		    the version that does not have X support should
 		    be built instead.</entry>
 	        </row>
 	      </tbody>
 	    </tgroup>
 	  </table>
 
 	</sect3>
 
 	<sect3>
 	  <title>Knob naming</title>
 	    <para>It is recommended that porters use like-named knobs, 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://www.freebsd.org/cgi/cvsweb.cgi/ports/KNOBS?rev=HEAD&amp;content-type=text/x-cvsweb-markup">KNOBS</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> variable gives the user who
 	      installs the port a dialog with the available options and saves
 	      them to <filename>/var/db/ports/<replaceable>portname</replaceable>/options</filename>.
 	      Next time when the port has to be rebuild, the options are reused.
 	      Never again you will have to remember all the twenty
 	      <makevar>WITH_<replaceable>*</replaceable></makevar> and
 	      <makevar>WITHOUT_<replaceable>*</replaceable></makevar> options you
 	      used to build this port!</para>
 
 	    <para>When the user runs <command>make config</command> (or runs
 	      <command>make build</command> for the first time), the framework will
 	      check for
 	      <filename>/var/db/ports/<replaceable>portname</replaceable>/options</filename>.
 	      If that file does not exist, it will use the values of
 	      <makevar>OPTIONS</makevar> to create a dialogbox where the options
 	      can be enabled or disabled.  Then the
 	      <filename>options</filename> file is saved and the selected
 	      variables will be used when building the port.</para>
 
 	    <para>Use <command>make showconfig</command> to see the saved
 	      configuration.  Use <command>make rmconfig</command> to remove the
 	      saved configuration.</para>
 	</sect3>
 
 	<sect3>
 	  <title>Syntax</title>
 	    <para>The syntax for the <makevar>OPTIONS</makevar> variable is:
 
 <programlisting>OPTIONS=	OPTION	"descriptive text" default ...
 </programlisting>
 
 	      The value for default is either <literal>ON</literal> or
 	      <literal>OFF</literal>.  Multiple repetitions of these three fields
 	      are allowed.</para>
 
 	    <para><makevar>OPTIONS</makevar> definition must appear before
 	      the inclusion of <filename>bsd.port.pre.mk</filename>.
 	      The <makevar>WITH_*</makevar> and <makevar>WITHOUT_*</makevar>
 	      variables can only be tested after the inclusion of
 	      <filename>bsd.port.pre.mk</filename>.  Due to a deficiency
 	      in the infrastructure, you can only test
 	      <makevar>WITH_*</makevar> variables for options, which are
 	      <literal>OFF</literal> by default, and
 	      <makevar>WITHOUT_*</makevar> variables for options, which
 	      defaults to <literal>ON</literal>.</para>
 
 	<sect3>
 	  <title>Example</title>
 	  <example id="ports-options-simple-use">
 	    <title>Simple use of <makevar>OPTIONS</makevar></title>
 	    <para><programlisting>OPTIONS=      FOO "Enable option foo" On \
               BAR "Support feature bar" Off
 
 .include &lt;bsd.port.pre.mk&gt;
 
 .if defined(WITHOUT_FOO)
 CONFIGURE_ARGS+=	--without-foo
 .else
 CONFIGURE_ARGS+=	--with-foo
 .endif
 
 .if defined(WITH_BAR)
 RUN_DEPENDS+=	bar:${PORTSDIR}/bar/bar
 .endif
 
 .include &lt;bsd.port.post.mk&gt;</programlisting></para>
 	  </example>
 
       </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><makevar>CONFLICTS</makevar></title>
 
 	<para>If your package cannot coexist with other packages
 	  (because of file conflicts, runtime incompatibility, etc.),
 	  list the other package names 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</makevar> does not match this port's
 	  package itself, or else forcing its installation with
 	  <makevar>FORCE_PKG_REGISTER</makevar> will no longer work.
        </para>
 
       <note>
 	<para><makevar>CONFLICTS</makevar> automatically sets
 	  <makevar>IGNORE</makevar>, which is more fully documented
 	  in <xref linkend="dads-noinstall">.</para>
       </note>
     </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>INSTALLS_SHLIB</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>
 
 	<para>If you need, you can override the default location where the new
 	  library is installed by defining the <makevar>LDCONFIG_DIRS</makevar>
 	  make variable, which should contain 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>INSTALLS_SHLIB= yes
 LDCONFIG_DIRS=  %%PREFIX%%/lib/foo %%PREFIX%%/lib/bar</programlisting>
 
 	<para>Remember that non-standard directories will not be passed to
 	  &man.ldconfig.8; on (re-)boot!  If any port really
 	  needs this to work, install a startup-script as
 	  <filename role="package">x11/kdelibs3</filename> does.  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/mozilla</filename> does.</para>
 
 	<para>Note that content of <makevar>LDCONFIG_DIRS</makevar> is passed
 	  through &man.sed.1; just like the rest of <filename>pkg-plist</filename>,
 	  so <makevar>PLIST_SUB</makevar> substitutions also apply here.  It is
 	  recommended that you use <literal>%%PREFIX%%</literal> for
 	  <makevar>PREFIX</makevar>, <literal>%%LOCALBASE%%</literal> for
 	  <makevar>LOCALBASE</makevar> and <literal>%%X11BASE%%</literal> for
 	  <makevar>X11BASE</makevar>.</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>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>
     </sect1>
 
     <sect1 id="building">
       <title>Building mechanisms</title>
 
       <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 gmake</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}
 	  &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>
 
 	<para>If your package uses GNU <command>configure</command>, and
 	  the resulting executable file has a <quote>strange</quote> name
 	  like
 	  <filename>i386-portbld-freebsd4.7-</filename><replaceable>appname</replaceable>,
 	  you will need to additionally override the
 	  <makevar>CONFIGURE_TARGET</makevar> variable to specify the
 	  target in the way required by scripts generated by recent
 	  versions of <command>autoconf</command>.  Add the following line
 	  immediately after the <literal>GNU_CONFIGURE=yes</literal> line
 	  in your <filename>Makefile</filename>:</para>
 
 	<para>
 	  <literal>CONFIGURE_TARGET=--build=${MACHINE_ARCH}-portbld-freebsd${OSREL}</literal>
 	  </para>
 
 	  <table frame="none">
 	    <title>Variables for ports that use configure</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>
     </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>Before proceeding any further, it cannot be stressed highly
 	    enough that the constructs discussed here are for use ONLY in
 	    building other ports.  For cross-development work, the
 	    <literal>devel/gnu-{automake,autoconf,libtool}</literal> ports
 	    should be used, such as within an IDE.  <filename
 	    role="package">devel/anjuta</filename> and <filename
 	    role="package">devel/kdevelop</filename> (GNOME and KDE
 	    respectively) are good examples of how to achieve this.</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 Ports Collection provides a
 	    number of versions of <command>libtool</command> modified for use by
 	    &os;.</para>
 
 	  <programlisting>USE_AUTOTOOLS= libtool:<replaceable>version</replaceable>[:inc|:env]</programlisting>
 
 	  <para>With no additional operations,
 	    <literal>libtool:<replaceable>version</replaceable></literal> tells
 	    the building framework that the port uses
 	    <command>libtool</command>, implying
 	    <makevar>GNU_CONFIGURE</makevar>.  The configure script will be
 	    patched with the system-installed copy of
 	    <command>libtool</command>.  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>:inc</literal> operation, the environment
 	    will be set up, and a slightly different set of patching will be
 	    performed.</para>
 
 	  <para>With the <literal>:env</literal> operation, only the
 	    environment will be set up.</para>
 
 	  <informaltable frame="none">
 	    <tgroup cols="2">
 	      <thead>
 		<row>
 		  <entry>Previously</entry>
 
 		  <entry><makevar>USE_AUTOTOOLS</makevar> construct</entry>
 		</row>
 	      </thead>
 
 	      <tbody>
 		<row>
 		  <entry><literal>USE_LIBTOOL_VER=13</literal></entry>
 
 		  <entry><literal>libtool:13</literal></entry>
 		</row>
 
 		<row>
 		  <entry><literal>USE_INC_LIBTOOL_VER=15</literal></entry>
 
 		  <entry><literal>libtool:15:inc</literal></entry>
 		</row>
 
 		<row>
 		  <entry><literal>WANT_LIBTOOL_VER=15</literal></entry>
 
 		  <entry><literal>libtool:15:env</literal></entry>
 		</row>
 
 	      </tbody>
 	    </tgroup>
 	  </informaltable>
 
 	  <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>
 
 	  <informaltable frame="none">
 	    <tgroup cols="2">
 	      <thead>
 		<row>
 		  <entry>Previously</entry>
 
 		  <entry><makevar>USE_AUTOTOOLS</makevar> construct</entry>
 		</row>
 	      </thead>
 
 	      <tbody>
 		<row>
 		  <entry><literal>USE_LIBLTDL=YES</literal></entry>
 
 		  <entry><literal>libltdl:15</literal></entry>
 		</row>
 
 	      </tbody>
 	    </tgroup>
 	  </informaltable>
 
 	</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>
 
 	  <informaltable frame="none">
 	    <tgroup cols="2">
 	      <thead>
 		<row>
 		  <entry>Previously</entry>
 
 		  <entry><makevar>USE_AUTOTOOLS</makevar> construct</entry>
 		</row>
 	      </thead>
 
 	      <tbody>
 		<row>
 		  <entry><literal>USE_AUTOCONF_VER=213</literal></entry>
 
 		  <entry><literal>autoconf:213</literal></entry>
 		</row>
 
 		<row>
 		  <entry><literal>WANT_AUTOCONF_VER=259</literal></entry>
 
 		  <entry><literal>autoconf:259:env</literal></entry>
 		</row>
 
 		<row>
 		  <entry><literal>USE_AUTOHEADER_VER=253</literal></entry>
 
 		  <entry><literal>autoheader:253</literal> (implies
 		    <literal>autoconf:253</literal>)</entry>
 		</row>
 
 	      </tbody>
 	    </tgroup>
 	  </informaltable>
 
 	  <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>
 
 	  <informaltable frame="none">
 	    <tgroup cols="2">
 	      <thead>
 		<row>
 		  <entry>Previously</entry>
 
 		  <entry><makevar>USE_AUTOTOOLS</makevar> construct</entry>
 		</row>
 	      </thead>
 
 	      <tbody>
 		<row>
 		  <entry><literal>USE_AUTOMAKE_VER=14</literal></entry>
 
 		  <entry><literal>automake:14</literal></entry>
 		</row>
 
 		<row>
 		  <entry><literal>WANT_AUTOMAKE_VER=15</literal></entry>
 
 		  <entry><literal>automake:15:env</literal></entry>
 		</row>
 
 		<row>
 		  <entry><literal>USE_ACLOCAL_VER=19</literal></entry>
 
 		  <entry><literal>aclocal:19</literal> (implies
 		    <literal>automake:19</literal>)</entry>
 		</row>
 
 	      </tbody>
 	    </tgroup>
 	  </informaltable>
 
 	  <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
 	    overriden by the port <filename>Makefile</filename> if
 	    required.</para>
 
 	</sect2>
     </sect1>
 
     <sect1 id="using-perl">
       <title>Using <literal>perl</literal></title>
 
       <table frame="none">
 	<title>Variables for ports that use <literal>perl</literal></title>
 
 	<tgroup cols="2">
 	  <thead>
 	    <row>
 	      <entry>Variable</entry>
 
 	      <entry>Means</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry><makevar>USE_PERL5</makevar></entry>
 
 	      <entry>Says that the port uses <literal>perl 5</literal> to build and run.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_PERL5_BUILD</makevar></entry>
 
 	      <entry>Says that the port uses <literal>perl 5</literal> to build.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_PERL5_RUN</makevar></entry>
 
 	      <entry>Says that the port uses <literal>perl 5</literal> to run.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>PERL</makevar></entry>
 
 	      <entry>The full path of <literal>perl 5</literal>, 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>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry><makevar>PERL_VERSION</makevar></entry>
 
 	      <entry>The full version of <literal>perl</literal> installed (e.g.,
 		<literal>5.00503</literal>).</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>PERL_VER</makevar></entry>
 
 	      <entry>The short version of <literal>perl</literal> installed (e.g.,
 		<literal>5.005</literal>).</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>PERL_LEVEL</makevar></entry>
 
 	      <entry>The installed <literal>perl</literal> version as an integer of the form <literal>MNNNPP</literal>
 		(e.g., <literal>500503</literal>).</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>PERL_ARCH</makevar></entry>
 
 	      <entry>Where <literal>perl</literal> stores architecture dependent libraries.
 		Defaults to <literal>${ARCH}-freebsd</literal>.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>PERL_PORT</makevar></entry>
 
 	      <entry>Name of the <literal>perl</literal> port that is
 		installed (e.g., <literal>perl5</literal>).</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>SITE_PERL</makevar></entry>
 
 	      <entry>Directory name where site specific
 		<literal>perl</literal> packages go.
 		This value is added to PLIST_SUB.</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </table>
 
       <note>
 	<para>Ports of Perl modules, which do not have an official website,
 	  should link <hostid>cpan.org</hostid> in the WWW line of a
 	  <filename>pkg-descr</filename> file.  The suggested URL scheme is
 	  <literal>http://search.cpan.org/dist/Module-Name</literal>.</para>
       </note>
 
     </sect1>
 
     <sect1 id="using-x11">
       <title>Using X11</title>
 
       <sect2 id="x11-variables">
 	<title>Variable definitions</title>
 
       <table frame="none">
 	<title>Variables for ports that use X</title>
 
 	<tgroup cols="2">
 	  <tbody>
 	    <row>
 	      <entry><makevar>USE_X_PREFIX</makevar></entry>
 
 	      <entry>The port installs in <makevar>X11BASE</makevar>, not
 		<makevar>PREFIX</makevar>.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_XLIB</makevar></entry>
 
 	      <entry>The port uses the X libraries.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_MOTIF</makevar></entry>
 
 	      <entry>The port uses the Motif toolkit.  Implies
 		<makevar>USE_XPM</makevar>.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_IMAKE</makevar></entry>
 
 	      <entry>The port uses <command>imake</command>.  Implies
 		<makevar>USE_X_PREFIX</makevar>.</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 in port</title>
 	<programlisting># Use X11 libraries and depend on
 # font server as well as cyrillic fonts.
 RUN_DEPENDS=   ${X11BASE}/bin/xfs:${X_FONTSERVER_PORT} \
                ${X11BASE}/lib/X11/fonts/cyrillic/crox1c.pcf.gz:${X_FONTS_CYRILLIC_PORT}
 
 USE_XLIB=      yes</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/X11R6/lib -lXm</literal> or
 	  <literal>/usr/X11R6/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>X11BASE</makevar>/lib/X11/fonts/local</filename>.<para>
 
       </sect2>
 
+      <sect2>
+	<title>Getting fake <envar>DISPLAY</envar> using Xvfb</title>
+
+	<para>Some applications require a working X11 display for compilation to
+	  succeed.  This pose a problem for the FreeBSD package building
+	  cluster, which operates headless.  When the following canonical hack
+	  is used, the package cluster will start the virtual framebuffer
+	  X server.  The working <envar>DISPLAY</envar> is then passed
+	  to the build.</para>
+
+	<programlisting>.if defined(PACKAGE_BUILDING)
+BUILD_DEPENDS+= Xvfb:${X_VFBSERVER_PORT} \
+                ${X11BASE}/lib/X11/fonts/misc/8x13O.pcf.gz:${X_FONTS_MISC_PORT}
+.endif</programlisting>
+
+      </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>
 
       <note>
 	<para>Your port does not need to depend on GNOME if it merely installs
 	  <application>pkg-config</application> metadata files to
 	  <filename><makevar>PREFIX</makevar>/libdata/pkgconfig</filename>.
 	  As usual, your port should be prepared to clean up after itself
 	  and remove that directory if it becomes empty.
 	  Assuming that your port installs a file named
 	  <filename>gtkmumble.pc</filename> to the said location, just add
 	  the following lines to <filename>pkg-plist</filename>:</para>
 
 	<programlisting>libdata/pkgconfig/gtkmumble.pc
 @unexec rmdir %B 2>/dev/null || true</programlisting>
 
 	<para>The latter line must appear immediately after the former one
 	  so that <literal>%B</literal> expands correctly.  Please refer
 	  to &man.pkg.create.1; for a detailed description of the syntax
 	  used in <filename>pkg-plist</filename>.</para>
       </note>
 
     </sect1>
 
     <sect1 id="using-kde">
       <title>Using KDE</title>
 
       <table frame="none">
 	<title>Variables for ports that use KDE</title>
 
 	<tgroup cols="2">
 	  <tbody>
 	    <row>
 	      <entry><makevar>USE_QT_VER</makevar></entry>
 
 	      <entry>The port uses the Qt toolkit.  Possible values are
 		<literal>1</literal> and
 		<literal>3</literal>;  each specify the major version
 		of Qt to use.  Sets both <makevar>MOC</makevar> and
 		<makevar>QTCPPFLAGS</makevar>to default appropriate
 		values.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_KDELIBS_VER</makevar></entry>
 
 	      <entry>The port uses KDE libraries.  Possible values are
 		<literal>3</literal>;  each specify the major version
 		of KDE to use.  Implies <makevar>USE_QT_VER</makevar>
 		of the appropriate version.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>USE_KDEBASE_VER</makevar></entry>
 
 	      <entry>The port uses KDE base.  Possible values are
 		<literal>3</literal>;  each specify the major version
 		of KDE to use.  Implies <makevar>USE_KDELIBS_VER</makevar>
 		of the appropriate version.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>MOC</makevar></entry>
 
 	      <entry>Set to the path of <command>moc</command>.
 		Default set according to <makevar>USE_QT_VER</makevar>
 		value.</entry>
 	    </row>
 
 	    <row>
 	      <entry><makevar>QTCPPFLAGS</makevar></entry>
 
 	      <entry>Set the <makevar>CPPFLAGS</makevar> to use when
 		processing Qt code.  Default set according to
 		<makevar>USE_QT_VER</makevar> value.</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </table>
 
     </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) 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/jdk14</filename>.</para>
 
       <table frame="none">
 	<title>Variables that 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.1[+] 1.2[+] 1.3[+] 1.4[+]</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 ibm
 		blackdown</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>
 	    <row>
 	      <entry><makevar>USE_JIKES</makevar></entry>
 	      <entry>Whether the port should or should not use the
 		<command>jikes</command> bytecode compiler to build. When
 		no value is set for this variable, the port will use
 		<command>jikes</command> to build if available. You may
 		also explicitly forbid or enforce the use of
 		<command>jikes</command> (by setting <literal>'no'</literal>
 		or <literal>'yes'</literal>). In the later case, <filename
 		role="package">devel/jikes</filename> will be added to build
 		dependencies of the port. In any case that <command>jikes</command>
 		is actually used in place of <command>javac</command>, then the
 		<makevar>HAVE_JIKES</makevar> variable is defined by
 		<filename>bsd.java.mk</filename>.</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/jdk14'</literal>).</entry>
 	    </row>
 	    <row>
 	      <entry><makevar>JAVA_PORT_VERSION</makevar></entry>
 	      <entry>The full version of the JDK port (e.g.
 		<literal>'1.4.2'</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>'linux'</literal>).</entry>
 	    </row>
 	    <row>
 	      <entry><makevar>JAVA_PORT_VENDOR</makevar></entry>
 	      <entry>The vendor of the JDK port (e.g.
 		<literal>'sun'</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>'Linux'</literal>).</entry>
 	    </row>
 	    <row>
 	      <entry><makevar>JAVA_PORT_VENDOR_DESCRIPTION</makevar></entry>
 	      <entry>Description of the vendor of the JDK port (e.g.
 		<literal>'FreeBSD Foundation'</literal>).</entry>
 	    </row>
 	    <row>
 	      <entry><makevar>JAVA_HOME</makevar></entry>
 	      <entry>Path to the installation directory of the JDK (e.g.
 		<filename>'/usr/local/jdk1.3.1'</filename>).</entry>
 	    </row>
 	    <row>
 	      <entry><makevar>JAVAC</makevar></entry>
 	      <entry>Path to the Java compiler to use (e.g.
 		<filename>'/usr/local/jdk1.1.8/bin/javac'</filename> or
 		<filename>'/usr/local/bin/jikes'</filename>).</entry>
 	    </row>
 	    <row>
 	      <entry><makevar>JAR</makevar></entry>
 	      <entry>Path to the <command>jar</command> tool to use (e.g.
 		<filename>'/usr/local/jdk1.2.2/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/linux-jdk1.2.2/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/jdk1.3.1/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.
 		This variable is available only if the JDK is Java 1.2 or
 		higher.</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.
 		This variable is available only if the JDK is Java 1.2 or
 		higher.</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>.
 		This variable is only available if the JDK is Java 1.2
 		or higher.</entry>
 	    </row>
 	    <row>
 	      <entry><makevar>JAVA_CLASSES</makevar></entry>
 	      <entry>Path to the archive that contains the JDK class
 		files. On JDK 1.2 or later, this is
 		<filename>${JAVA_HOME}/jre/lib/rt.jar</filename>.  Earlier
 		JDKs used
 		<filename>${JAVA_HOME}/lib/classes.zip</filename>.</entry>
 	    </row>
 	    <row>
 	      <entry><makevar>HAVE_JIKES</makevar></entry>
 	      <entry>Defined whenever <command>jikes</command> is used by
 	        the port (see <makevar>USE_JIKES</makevar> above).</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_TARGETS</makevar>.
 	  This is similar to the <makevar>USE_GMAKE</makevar> mechanism,
 	  which is documented in <xref linkend="building">.</para>
 
 	<para>If <command>jikes</command> is used in place of
 	  <command>javac</command> (see <makevar>USE_JIKES</makevar> in
 	  <xref linkend="java-variables">), then Ant will automatically
 	  use it to build the port.</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="dads-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://www.freebsd.org/cgi/cvsweb.cgi/ports/Mk/bsd.java.mk">
 	  bsd.java.mk CVS 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>Using 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>USE_APACHE</entry>
 
 		<entry>The port requires Apache.</entry>
 	      </row>
 
 	      <row>
 		<entry>WITH_APACHE2</entry>
 
 		<entry>The port requires Apache 2.0.  Without this variable,
 		  the port will depend on Apache 1.3.</entry>
 	      </row>
 
 	      <row>
 		<entry>APXS</entry>
 
 		<entry>Full path to the <command>apxs</command> binary
 		  (read-only variable).</entry>
 	      </row>
 
 	    </tbody>
 	  </tgroup>
 	</table>
 
       </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>4</literal>. Possible values: <literal>4</literal>,
 		  <literal>5</literal></entry>
 	      </row>
 
 	      <row>
 		<entry><makevar>BROKEN_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>
 
 	      <row>
 		<entry><makevar>WANT_PHP_PEAR</makevar></entry>
 
 		<entry>Want the PEAR framework.</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-PEAR/Makefile.common</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-PEAR/Makefile.common"
 .include &lt;bsd.port.post.mk&gt;</programlisting>
 
 	</example>
 
       </sect2>
 
     </sect1>
 
     <sect1 id="using-python">
       <title>Using Python</title>
 
       <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.3+</literal>.
 		Version ranges can also be specified, by separating two version
 		numbers with a dash, e.g.: <literal>2.1-2.3</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>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.3.  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-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_SITEARCHILIBDIR</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="rc-scripts">
       <title>Starting and stopping services (rc scripts)</title>
 
-      <para>Startup scripts are used to start services on system
-	startup, and to give administrator a standard way of stopping,
-	starting and restarting the service.  Ports integrates into
+      <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 usage
 	can be found in
-	<ulink url="&url.books.handbook;/configtuning-rcng.html">the Handbook
-	chapter</ulink>.  Detailed explanation of available commands is in
-	&man.rc.subr.8;.</para>
+	<ulink url="&url.books.handbook;/configtuning-rcd.html">the rc.d Handbook
+	chapter</ulink>.  Detailed explanation of available commands are in
+	&man.rc.8; and .&man.rc.subr.8;.</para>
 
       <para>One or more rc scripts can be installed:</para>
 
       <programlisting>USE_RC_SUBR=	doorman.sh</programlisting>
 
       <para>Scripts must be placed in the <filename>files</filename>
 	subdirectory and a <literal>.in</literal> suffix must be added to their
-	filename.  The only difference from a base system rc script is that the
-	<literal>.&nbsp;/etc/rc.subr</literal> line must be replaced with
+	filename.  The only difference from a base system <filename>rc.d</filename> script is that the
+	<literal>.&nbsp;/etc/rc.subr</literal> line must be replaced with the
 	<literal>.&nbsp;%%RC_SUBR%%</literal>, because older versions of &os;
 	do not have an <filename>/etc/rc.subr</filename> file.  Standard
-	<makevar>SUB_LIST</makevar> expansions are used too. Especially using
-	<literal>%%PREFIX%%</literal> is advised.  More on
+	<makevar>SUB_LIST</makevar> expansions are used too.
+	Use of the <literal>%%PREFIX%%</literal>,
+	<literal>%%LOCALBASE%%</literal>, and
+	<literal>%%X11BASE%%</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>Integration with &man.rcorder.8; is available by using
+      <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 deprecated.</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 rc script:</para>
+      <para>Example simple <filename>rc.d</filename> script:</para>
 
       <programlisting>#!/bin/sh
 
 # PROVIDE: doorman
 # REQUIRE: LOGIN
-# KEYWORD: FreeBSD
 
 #
-# Add the following lines to /etc/rc.conf to enable doorman:
+# Add the following lines to /etc/rc.conf.local or /etc/rc.conf to enable doorman:
 # doorman_enable (bool):      Set to "NO" by default.
 #                             Set it to "YES" to enable doorman
 # doorman_config (path):      Set to "%%PREFIX%%/etc/doormand/doormand.cf" by default.
 #
 
 . %%RC_SUBR%%
 
 name="doorman"
 rcvar=`set_rcvar`
 
 load_rc_config $name
 
 : ${doorman_enable="NO"}
 : ${doorman_config="%%PREFIX%%/etc/doormand/doormand.cf"}
 
 command=%%PREFIX%%/sbin/doormand
 pidfile=/var/run/doormand.pid
 command_args="-p $pidfile -f $doorman_config"
 
 run_rc_command "$1"</programlisting>
 
+      <para>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
+	<programlisting>doorman_flags=""</programlisting> in their
+	<filename>rc.conf.local</filename> file, and a variable
+	substitution using &quot;:=&quot; would inappropriately
+	override the user's intention.</para>
+
     </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> is
 	  the full version number of <command>perl</command> (e.g.,
 	  <literal>5.00502</literal>) and <literal>%%PERL_VER%%</literal>
 	  is the <command>perl</command> version number minus
 	  the patchlevel (e.g., <literal>5.005</literal>).  Several other
 	  <literal>%%<replaceable>VARS</replaceable>%%</literal> related to
 	  port's documentation files are described in <link
 	  linkend="dads-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>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 call <command>rmdir</command> from <literal>@unexec</literal> to
 	  remove only empty directories without warning.</para>
 
 	<programlisting>@unexec rmdir %D/share/doc/gimp 2>/dev/null || true</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 requires some configuration files in
 	  <filename><makevar>PREFIX</makevar>/etc</filename>, do
 	  <emphasis>not</emphasis> just install them and list them in
 	  <filename>pkg-plist</filename>.  That will cause
 	  &man.pkg.delete.1; to delete files carefully edited by
 	  the user and a new installation to wipe them out.</para>
 
 	<para>Instead, install sample files with a suffix
 	  (<filename><replaceable>filename</replaceable>.sample</filename>
 	  will work well).  Copy the sample file as the real configuration
 	  file, if it does not exist.  On deinstall, delete the configuration
 	  file, but only if it was not modified by the user.  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>Example of the <filename>pkg-plist</filename> part:</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>Alternatively, print out a <link
 	    linkend="porting-message">message</link> pointing out that the
 	  user has to copy and edit the file before the software can be made
 	  to work.</para>
       </sect1>
 
       <sect1 id="plist-dynamic">
 	<title>Dynamic vs. 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>
+      <title>¦Û°Ê²£¥Í package list</title>
 
-      <para>First, make sure your port is almost complete, with only
-	<filename>pkg-plist</filename> missing.</para>
+      <para>­º¥ý¡A¥ý½T»{±zªº port °£¤F <filename>pkg-plist</filename> ©|¥¼·d©w¤§¥~¡A¨ä¥L³£§¹¦¨¤F¡C</para>
 
-      <para>Next, create a temporary directory tree into which your port can be
+      <para>±µµÛ¡A create a temporary directory tree into which your port can be
 	installed, and install any dependencies.
 	<replaceable>port-type</replaceable> should be <literal>local</literal>
 	for non-X ports and <literal>x11-4</literal> or <literal>x11</literal>
 	for ports which install into the directory hierarchy of XFree86 4
 	or an earlier XFree86 release, respectively.</para>
 
       <screen>&prompt.root; <userinput>mkdir /var/tmp/<replaceable>port-name</replaceable></userinput>
 &prompt.root; <userinput>mtree -U -f /etc/mtree/BSD.<replaceable>port-type</replaceable>.dist -d -e -p /var/tmp/<replaceable>port-name</replaceable></userinput>
 &prompt.root; <userinput>make depends PREFIX=/var/tmp/<replaceable>port-name</replaceable></userinput></screen>
 
       <para>Store the directory structure in a new file.</para>
 
       <screen>&prompt.root; <userinput>(cd /var/tmp/<replaceable>port-name</replaceable> && find -d * -type d) | sort &gt; OLD-DIRS</userinput></screen>
 
       <para>Create an empty <filename>pkg-plist</filename> file:</para>
 
       <screen>&prompt.root; <userinput>touch 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/<replaceable>port-name</replaceable></userinput>
 &prompt.root; <userinput>(cd /var/tmp/<replaceable>port-name</replaceable> && 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/<replaceable>port-name</replaceable> && 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 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/<replaceable>port-name</replaceable></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 /etc/mtree/BSD.<replaceable>port-type</replaceable>.dist /var/tmp/<replaceable>port-name</replaceable> &gt; pkg-plist</userinput></screen>
 
       <para>The packing list still has to be tidied up by hand as
 	stated above.</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>
 
 	<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="1">
 	  <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> and
-	  <makevar>USE_RCORDER</makevar> are automatically added to
+	  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-reg</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>X11BASE</makevar>,
 	  <makevar>DATADIR</makevar>, <makevar>DOCSDIR</makevar>,
 	  <makevar>EXAMPLESDIR</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's 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="porting-prefix">
 	<title><makevar>PREFIX</makevar></title>
 
 	<para>Do try to make your port install relative to
 	  <makevar>PREFIX</makevar>.  The value of this variable will be set
 	  to <makevar>LOCALBASE</makevar> (default
 	  <filename>/usr/local</filename>).  If
 	  <makevar>USE_X_PREFIX</makevar> or <makevar>USE_IMAKE</makevar> is
 	  set, <makevar>PREFIX</makevar> will be <makevar>X11BASE</makevar> (default
 	  <filename>/usr/X11R6</filename>).  If
 	  <makevar>USE_LINUX_PREFIX</makevar> is set, <makevar>PREFIX</makevar>
 	  will be <makevar>LINUXBASE</makevar> (default
 	  <filename>/compat/linux</filename>).</para>
 
 	<para>Avoiding the hard-coding of <filename>/usr/local</filename> or
 	  <filename>/usr/X11R6</filename> anywhere in the source will make the
 	  port much more flexible and able to cater to the needs of other
 	  sites.  For X ports that use <command>imake</command>, this is
 	  automatic; otherwise, this can often be done by simply replacing the
 	  occurrences of <filename>/usr/local</filename> (or
 	  <filename>/usr/X11R6</filename> for X ports that do not use imake)
 	  in the various <filename>scripts/Makefile</filename>s in the port to read
 	  <makevar>${PREFIX}</makevar>, as 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 this is to do this is:</para>
 
 	<screen>&prompt.root; <userinput>make clean; make package PREFIX=/var/tmp/<replaceable>port-name</replaceable></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>
 
 	<!-- XXX This paragraph is confusing and poorly indented. -->
 	<para>This does not test for the existence of internal references,
 	or correct use of <makevar>LOCALBASE</makevar> for references to
 	files from other ports.  Testing the installation in
 	<filename>/var/tmp/<replaceable>port-name</replaceable></filename>
 	to do that while you have it installed would do that.</para>
 
 	<para>Do not set <makevar>USE_X_PREFIX</makevar> unless your port
 	  truly requires it (i.e., it links against X libs or it needs to
 	  reference files in <makevar>X11BASE</makevar>).</para>
 
 	<para>The variable <makevar>PREFIX</makevar> can be reassigned in your
 	  <filename>Makefile</filename> or in the user's environment.
 	  However, it is strongly discouraged for individual ports to set this
 	  variable explicitly in the <filename>Makefile</filename>s.</para>
 
 	<para>Also, refer to programs/files from other ports with the
 	  variables mentioned above, not explicit pathnames.  For instance, if
 	  your port requires a macro <literal>PAGER</literal> to be the full
 	  pathname of <command>less</command>, use the compiler flag:
 
 	  <programlisting>-DPAGER=\"&dollar;{LOCALBASE}/bin/less\"</programlisting>
 
 	  instead of
 	  <literal>-DPAGER=\"/usr/local/bin/less\"</literal>. This way it will
 	  have a better chance of working if the system administrator has
 	  moved the whole <filename>/usr/local</filename> tree somewhere else.</para>
       </sect1>
   </chapter>
 
     <chapter id="port-upgrading">
       <title>Upgrading</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>CVSup</application> to keep your whole ports collection
 	up-to-date, as described in the
 	<ulink url="&url.books.handbook;/synching.html#CVSUP-CONFIG">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 make the changes and save
 	the result of the
 	recursive <command>diff</command> 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.  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 2000 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
 	<ulink url="&url.books.developers-handbook;/policies.html#POLICIES-MAINTAINER">
 	MAINTAINER on Makefiles</ulink> section.)</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 volunteering to maintain 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.cvs.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!</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>
 
     </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 as
 	    a security vulnerability is discovered 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
 	    just 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 by the time 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
 	    are monitoring 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, or whatever, 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>All right, you elected the hard way.  As it may be obvious
 	    from its title, the VuXML database is essentially 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 as a template.</para>
 	</sect2>
 
 	<sect2 id="security-notify-vuxml-intro">
 	  <title>A short introduction to VuXML</title>
 
 	  <para>The full-blown XML 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.  Sounds
 	    very similar to HTML, doesn't it?  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 let's 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;/entry&gt; <co id="co-vx-mod">
   &lt;/dates&gt;
 &lt;/vuln&gt;</programlisting>
 
 	  <para>The tag names are supposed to be self-descriptive,
 	    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; in
 		FreeBSD 5.x, or you may install the port <filename
 		role="package">devel/p5-Data-UUID</filename> and issue
 		the following command:</para>
 
 	      <programlisting>perl -MData::UUID -le 'print lc new Data::UUID-&gt;create_str'</programlisting>
 	    </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 obviously 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 install fresh versions of the
 	    ports <filename role="package">security/portaudit</filename> and
 	    <filename role="package">security/portaudit-db</filename>.</para>
 
 	  <para>First, check whether there already is an entry for this
 	    vulnerability.  If there were such 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>
 
 	  <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>
 	  </note>
 
 	  <para>If there is none found, you get the green light to add
 	    a new entry for this vulnerability.  Now you can generate
 	    a brand-new UUID (assume it's
 	    <literal>74a9541d-5d6c-11d8-80e3-0020ed76ef5a</literal>) and
 	    add your new entry to the VuXML database.  Please verify
 	    its syntax after that as follows:</para>
 
 	  <screen>&prompt.user; <userinput>cd ${PORTSDIR}/security/vuxml && 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 74a9541d-5d6c-11d8-80e3-0020ed76ef5a</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>Obviously, 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>
 
 	<sect2 id="security-notify-noxml">
 	  <title>If VuXML still scares you...</title>
 
 	  <para>As an easy alternative to writing VuXML, you may opt to add
 	    a single line to a different file with much simpler syntax,
 	    <filename><envar>PORTSDIR</envar>/security/portaudit-db/database/portaudit.txt</filename>,
 	    which resides within the port <filename
 	    role="package">security/portaudit-db</filename>, and
 	    send a request for review to the Security Officer Team
 	    as described on the <ulink
 	    url="http://www.freebsd.org/security/#how">FreeBSD
 	    Security Information</ulink> page.</para>
 
 	  <para>A line in that file consists of four fields
 	    separated by <literal>|</literal>, a pipe character.
 	    The first field is a &man.pkg.version.1; pattern
 	    expression matching the vulnerable packages.  The second
 	    field contains URLs to relevant information, separated
 	    by space characters.  The third field is a one-line
 	    description of the issue.  The fourth and last field
 	    is the entry's UUID.</para>
 
 	  <para>You may want take a closer look at existing entries in
 	    <filename>portaudit.txt</filename> before adding your
 	    first line to that file.</para>
 	</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="dads-strip">
 	<title>Stripping Binaries</title>
 
 	<para>Do not strip binaries manually unless you have to.  All binaries
 	  should be stripped, but the <maketarget>INSTALL_PROGRAM</maketarget>
 	  macro will install and strip a binary at the same time (see the next
 	  section).</para>
 
 	<para>If you need to strip a file, but do not wish to use the
 	  <makevar>INSTALL_PROGRAM</makevar> macro,
 	  <makevar>${STRIP_CMD}</makevar> will strip your program.  This is
 	  typically done within the <literal>post-install</literal>
 	  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>
       </sect1>
 
       <sect1 id="dads-install">
 	<title>INSTALL_* 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_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.  See below for an example on how to use
 	  them.</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://cvsweb.freebsd.org/src/sys/sys/param.h">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 vs.
 	  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> vs
 	      <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>__FreeBSD_version values</title>
+	<title>FreeBSD ª©¥»³t¬dªí(__FreeBSD_version)</title>
 
-	  <para>Here is a convenient list of
-	    <literal>__FreeBSD_version</literal> values as defined in
-	    <ulink url="http://cvsweb.freebsd.org/src/sys/sys/param.h">sys/param.h</ulink>:</para>
+	  <para>¥H¤U¬O <ulink url="http://cvsweb.freebsd.org/src/sys/sys/param.h">sys/param.h</ulink> ¤ºªº <literal>__FreeBSD_version</literal> ª©¥»³t¬dªí¡G</para>
 
 		<table frame="none">
 		  <title>__FreeBSD_version values</title>
 		<tgroup cols="2">
 		<thead>
 		  <row>
 		    <entry>Release</entry>
 		    <entry><literal>__FreeBSD_version</literal></entry>
 		  </row>
 		</thead>
 
 		<tbody>
 		  <row>
 		    <entry>2.0-RELEASE</entry>
 		    <entry>119411</entry>
 		  </row>
 
 		  <row>
 		    <entry>2.1-CURRENT</entry>
 		    <entry>199501, 199503</entry>
 		  </row>
 
 		  <row>
 		    <entry>2.0.5-RELEASE</entry>
 		    <entry>199504</entry>
 		  </row>
 
 		  <row>
 		    <entry>2.2-CURRENT before 2.1</entry>
 		    <entry>199508</entry>
 		  </row>
 
 		  <row>
 		    <entry>2.1.0-RELEASE</entry>
 		    <entry>199511</entry>
 		  </row>
 
 		  <row>
 		    <entry>2.2-CURRENT before 2.1.5</entry>
 		    <entry>199512</entry>
 		  </row>
 
 		  <row>
 		    <entry>2.1.5-RELEASE</entry>
 		    <entry>199607</entry>
 		  </row>
 
 		  <row>
 		    <entry>2.2-CURRENT before 2.1.6</entry>
 		    <entry>199608</entry>
 		  </row>
 
 		  <row>
 		    <entry>2.1.6-RELEASE</entry>
 		    <entry>199612</entry>
 		  </row>
 
 		  <row>
 		    <entry>2.1.7-RELEASE</entry>
 		    <entry>199612</entry>
 		  </row>
 
 		  <row>
 		    <entry>2.2-RELEASE</entry>
 		    <entry>220000</entry>
 		  </row>
 
 		  <row>
 		    <entry>2.2.1-RELEASE</entry>
 		    <entry>220000 (no change)</entry>
 		  </row>
 
 		  <row>
 		    <entry>2.2-STABLE after 2.2.1-RELEASE</entry>
 		    <entry>220000 (no change)</entry>
 		  </row>
 
 		  <row>
 		    <entry>2.2-STABLE after texinfo-3.9</entry>
 		    <entry>221001</entry>
 		  </row>
 
 		  <row>
 		    <entry>2.2-STABLE after top</entry>
 		    <entry>221002</entry>
 		  </row>
 
 		  <row>
 		    <entry>2.2.2-RELEASE</entry>
 		    <entry>222000</entry>
 		  </row>
 
 		  <row>
 		    <entry>2.2-STABLE after 2.2.2-RELEASE</entry>
 		    <entry>222001</entry>
 		  </row>
 
 		  <row>
 		    <entry>2.2.5-RELEASE</entry>
 		    <entry>225000</entry>
 		  </row>
 
 		  <row>
 		    <entry>2.2-STABLE after 2.2.5-RELEASE</entry>
 		    <entry>225001</entry>
 		  </row>
 
 		  <row>
 		    <entry>2.2-STABLE after ldconfig -R merge</entry>
 		    <entry>225002</entry>
 		  </row>
 
 		  <row>
 		    <entry>2.2.6-RELEASE</entry>
 		    <entry>226000</entry>
 		  </row>
 
 		  <row>
 		    <entry>2.2.7-RELEASE</entry>
 		    <entry>227000</entry>
 		  </row>
 
 		  <row>
 		    <entry>2.2-STABLE after 2.2.7-RELEASE</entry>
 		    <entry>227001</entry>
 		  </row>
 
 		  <row>
 		    <entry>2.2-STABLE after &man.semctl.2; change</entry>
 		    <entry>227002</entry>
 		  </row>
 
 		  <row>
 		    <entry>2.2.8-RELEASE</entry>
 		    <entry>228000</entry>
 		  </row>
 
 		  <row>
 		    <entry>2.2-STABLE after 2.2.8-RELEASE</entry>
 		    <entry>228001</entry>
 		  </row>
 
 		  <row>
 		    <entry>3.0-CURRENT before &man.mount.2; change</entry>
 		    <entry>300000</entry>
 		  </row>
 
 		  <row>
 		    <entry>3.0-CURRENT after &man.mount.2; change</entry>
 		    <entry>300001</entry>
 		  </row>
 
 		  <row>
 		    <entry>3.0-CURRENT after &man.semctl.2; change</entry>
 		    <entry>300002</entry>
 		  </row>
 
 		  <row>
 		    <entry>3.0-CURRENT after ioctl arg changes</entry>
 		    <entry>300003</entry>
 		  </row>
 
 		  <row>
 		    <entry>3.0-CURRENT after ELF conversion</entry>
 		    <entry>300004</entry>
 		  </row>
 
 		  <row>
 		    <entry>3.0-RELEASE</entry>
 		    <entry>300005</entry>
 		  </row>
 
 		  <row>
 		    <entry>3.0-CURRENT after 3.0-RELEASE</entry>
 		    <entry>300006</entry>
 		  </row>
 
 		  <row>
 		    <entry>3.0-STABLE after 3/4 branch</entry>
 		    <entry>300007</entry>
 		  </row>
 
 		  <row>
 		    <entry>3.1-RELEASE</entry>
 		    <entry>310000</entry>
 		  </row>
 
 		  <row>
 		    <entry>3.1-STABLE after 3.1-RELEASE</entry>
 		    <entry>310001</entry>
 		  </row>
 
 		  <row>
 		    <entry>3.1-STABLE after C++ constructor/destructor order
 		      change</entry>
 		    <entry>310002</entry>
 		  </row>
 
 		  <row>
 		    <entry>3.2-RELEASE</entry>
 		    <entry>320000</entry>
 		  </row>
 
 		  <row>
 		    <entry>3.2-STABLE</entry>
 		    <entry>320001</entry>
 		  </row>
 
 		  <row>
 		    <entry>3.2-STABLE after binary-incompatible IPFW and
 		      socket changes</entry>
 		    <entry>320002</entry>
 		  </row>
 
 		  <row>
 		    <entry>3.3-RELEASE</entry>
 		    <entry>330000</entry>
 		  </row>
 
 		  <row>
 		    <entry>3.3-STABLE</entry>
 		    <entry>330001</entry>
 		  </row>
 
 		  <row>
 		    <entry>3.3-STABLE after adding &man.mkstemp.3;
 		      to libc</entry>
 		    <entry>330002</entry>
 		  </row>
 
 		  <row>
 		    <entry>3.4-RELEASE</entry>
 		    <entry>340000</entry>
 		  </row>
 
 		  <row>
 		    <entry>3.4-STABLE</entry>
 		    <entry>340001</entry>
 		  </row>
 
 		  <row>
 		    <entry>3.5-RELEASE</entry>
 		    <entry>350000</entry>
 		  </row>
 
 		  <row>
 		    <entry>3.5-STABLE</entry>
 		    <entry>350001</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.0-CURRENT after 3.4 branch</entry>
 		    <entry>400000</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.0-CURRENT after change in dynamic linker
 		      handling</entry>
 		    <entry>400001</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.0-CURRENT after C++ constructor/destructor
 		      order change</entry>
 		    <entry>400002</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.0-CURRENT after functioning &man.dladdr.3;</entry>
 		    <entry>400003</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.0-CURRENT after __deregister_frame_info dynamic
 		      linker bug fix (also 4.0-CURRENT after EGCS 1.1.2
 		      integration)
 		    </entry>
 		    <entry>400004</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.0-CURRENT after &man.suser.9; API change
 		      (also 4.0-CURRENT after newbus)</entry>
 		    <entry>400005</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.0-CURRENT after cdevsw registration change</entry>
 		    <entry>400006</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.0-CURRENT after the addition of so_cred for
 		      socket level credentials</entry>
 		    <entry>400007</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.0-CURRENT after the addition of a poll syscall
 		      wrapper to libc_r</entry>
 		    <entry>400008</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.0-CURRENT after the change of the kernel's
 		      <literal>dev_t</literal> type to <literal>struct
 		      specinfo</literal> pointer</entry>
 		    <entry>400009</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.0-CURRENT after fixing a hole
 		      in &man.jail.2;</entry>
 		    <entry>400010</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.0-CURRENT after the <literal>sigset_t</literal>
 		      datatype change</entry>
 		    <entry>400011</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.0-CURRENT after the cutover to the GCC 2.95.2
 		      compiler</entry>
 		    <entry>400012</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.0-CURRENT after adding pluggable linux-mode
 		      ioctl handlers</entry>
 		    <entry>400013</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.0-CURRENT after importing OpenSSL</entry>
 		    <entry>400014</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.0-CURRENT after the C++ ABI change in GCC 2.95.2
 		      from -fvtable-thunks to -fno-vtable-thunks by
 		      default</entry>
 		    <entry>400015</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.0-CURRENT after importing OpenSSH</entry>
 		    <entry>400016</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.0-RELEASE</entry>
 		    <entry>400017</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.0-STABLE after 4.0-RELEASE</entry>
 		    <entry>400018</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.0-STABLE after the introduction of delayed
 		      checksums.</entry>
 		    <entry>400019</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.0-STABLE after merging libxpg4 code into
 		      libc.</entry>
 		    <entry>400020</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.0-STABLE after upgrading Binutils to 2.10.0, ELF
 		      branding changes, and tcsh in the base system.</entry>
 		    <entry>400021</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.1-RELEASE</entry>
 		    <entry>410000</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.1-STABLE after 4.1-RELEASE</entry>
 		    <entry>410001</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.1-STABLE after &man.setproctitle.3; moved from
 		      libutil to libc.</entry>
 		    <entry>410002</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.1.1-RELEASE</entry>
 		    <entry>411000</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.1.1-STABLE after 4.1.1-RELEASE</entry>
 		    <entry>411001</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.2-RELEASE</entry>
 		    <entry>420000</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.2-STABLE after combining libgcc.a and
 		      libgcc_r.a, and associated GCC linkage changes.</entry>
 		    <entry>420001</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.3-RELEASE</entry>
 		    <entry>430000</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.3-STABLE after wint_t introduction.</entry>
 		    <entry>430001</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.3-STABLE after PCI powerstate API merge.</entry>
 		    <entry>430002</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.4-RELEASE</entry>
 		    <entry>440000</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.4-STABLE after d_thread_t introduction.</entry>
 		    <entry>440001</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.4-STABLE after mount structure changes (affects
 		      filesystem klds).</entry>
 		    <entry>440002</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.4-STABLE after the userland components of smbfs
 		      were imported.</entry>
 		    <entry>440003</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.5-RELEASE</entry>
 		    <entry>450000</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.5-STABLE after the usb structure element rename.</entry>
 		    <entry>450001</entry>
 		  </row>
 
 		  <row>
 		    <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>
 		    <entry>450004</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.5-STABLE after moving to XFree86 4 by default
 		      for package builds.</entry>
 		    <entry>450005</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.5-STABLE after accept filtering was fixed so
 		      that is no longer susceptible to an easy DoS.</entry>
 		    <entry>450006</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.6-RELEASE</entry>
 		    <entry>460000</entry>
 		  </row>
 
 		  <row>
 		    <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>
 		    <entry>460001</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.6.2-RELEASE</entry>
 		    <entry>460002</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.6-STABLE</entry>
 		    <entry>460100</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.6-STABLE after MFC of `sed -i'.</entry>
 		    <entry>460101</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.6-STABLE after MFC of many new pkg_install
 		      features from the HEAD.</entry>
 		    <entry>460102</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.7-RELEASE</entry>
 		    <entry>470000</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.7-STABLE</entry>
 		    <entry>470100</entry>
 		  </row>
 
 		  <row>
 		    <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>
 		    <entry>470101</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.7-STABLE after MFC of mbuf changes to replace
 		       m_aux mbufs by m_tag's</entry>
 		    <entry>470102</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.7-STABLE gets OpenSSL 0.9.7</entry>
 		    <entry>470103</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.8-RELEASE</entry>
 		    <entry>480000</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.8-STABLE</entry>
 		    <entry>480100</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.8-STABLE after &man.realpath.3; has been made
 		      thread-safe</entry>
 		    <entry>480101</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.8-STABLE 3ware API changes to twe.</entry>
 		    <entry>480102</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.9-RELEASE</entry>
 		    <entry>490000</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.9-STABLE</entry>
 		    <entry>490100</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.9-STABLE after e_sid was added to struct
 		      kinfo_eproc.</entry>
 		    <entry>490101</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.9-STABLE after MFC of libmap functionality
 		      for rtld.</entry>
 		    <entry>490102</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.10-RELEASE</entry>
 		    <entry>491000</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.10-STABLE</entry>
 		    <entry>491100</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.10-STABLE after MFC of revision 20040629 of
 		      the package tools</entry>
 		    <entry>491101</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.10-STABLE after VM fix dealing with unwiring
 		      of fictitious pages</entry>
 		    <entry>491102</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.11-RELEASE</entry>
 		    <entry>492000</entry>
 		  </row>
 
 		  <row>
 		    <entry>4.11-STABLE</entry>
 		    <entry>492100</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT</entry>
 		    <entry>500000</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after adding addition ELF header fields,
 		      and changing our ELF binary branding method.</entry>
 		    <entry>500001</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after kld metadata changes.</entry>
 		    <entry>500002</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after buf/bio changes.</entry>
 		    <entry>500003</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after binutils upgrade.</entry>
 		    <entry>500004</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after merging libxpg4 code into
 		      libc and after TASKQ interface introduction.</entry>
 		    <entry>500005</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after the addition of AGP
 		      interfaces.</entry>
 		    <entry>500006</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after Perl upgrade to 5.6.0</entry>
 		    <entry>500007</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after the update of KAME code to
 		      2000/07 sources.</entry>
 		    <entry>500008</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after ether_ifattach() and
 		      ether_ifdetach() changes.</entry>
 		    <entry>500009</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after changing mtree defaults
 		      back to original variant, adding -L to follow
 		      symlinks.</entry>
 		    <entry>500010</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after kqueue API changed.</entry>
 		    <entry>500011</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after &man.setproctitle.3; moved from
 		      libutil to libc.</entry>
 		    <entry>500012</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after the first SMPng commit.</entry>
 		    <entry>500013</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after &lt;sys/select.h&gt; moved to
 		      &lt;sys/selinfo.h&gt;.</entry>
 		    <entry>500014</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after combining libgcc.a and
 		      libgcc_r.a, and associated GCC linkage changes.</entry>
 		    <entry>500015</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after change allowing libc and libc_r
 		      to be linked together, deprecating -pthread
 		      option.</entry>
 		    <entry>500016</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after switch from struct ucred to
 		      struct xucred to stabilize kernel-exported API for
 		      mountd et al.</entry>
 		    <entry>500017</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after addition of CPUTYPE make variable
 		      for controlling CPU-specific optimizations.</entry>
 		    <entry>500018</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after moving machine/ioctl_fd.h to
 		      sys/fdcio.h</entry>
 		    <entry>500019</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after locale names renaming.</entry>
 		    <entry>500020</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after Bzip2 import.
 		    Also signifies removal of S/Key.</entry>
 		    <entry>500021</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after SSE support.</entry>
 		    <entry>500022</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after KSE Milestone 2.</entry>
 		    <entry>500023</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after d_thread_t,
 		      and moving UUCP to ports.</entry>
 		    <entry>500024</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after ABI change for descriptor
 		      and creds passing on 64 bit platforms.</entry>
 		    <entry>500025</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after moving to XFree86 4 by default for
 		      package builds, and after the new libc strnstr() function
 		      was added.</entry>
 		    <entry>500026</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after the new libc strcasestr() function
 		      was added.</entry>
 		    <entry>500027</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after the userland components of smbfs
 		      were imported.</entry>
 		    <entry>500028</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after the new C99 specific-width
 		      integer types were added.</entry>
 		    <entry>(Not incremented.)</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after a change was made in the return
 		      value of &man.sendfile.2;.</entry>
 		    <entry>500029</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after the introduction of the
 		      type <literal>fflags_t</literal>, which is the
 		      appropriate size for file flags.</entry>
 		    <entry>500030</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after the usb structure element rename.</entry>
 		    <entry>500031</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after the introduction of
 		      Perl 5.6.1.</entry>
 		    <entry>500032</entry>
 		  </row>
 
 		  <row>
 		    <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>
 		    <entry>500033</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after mtx_init() grew a third argument.</entry>
 		    <entry>500034</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT with Gcc 3.1.</entry>
 		    <entry>500035</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT without Perl in /usr/src</entry>
 		    <entry>500036</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after the addition of &man.dlfunc.3;</entry>
 		    <entry>500037</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after the types of some struct
 		      sockbuf members were changed and the structure was
 		      reordered.</entry>
 		    <entry>500038</entry>
 		  </row>
 
 		  <row>
 		    <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>
 		    <entry>500039</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after various changes to disk functions
 		      were made in the name of removing dependency on disklabel
 		      structure internals.</entry>
 		    <entry>500040</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after the addition of &man.getopt.long.3;
 		      to libc.</entry>
 		    <entry>500041</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after Binutils 2.13 upgrade, which
 		      included new FreeBSD emulation, vec, and output format.
 		      </entry>
 		    <entry>500042</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after adding weak pthread_XXX stubs
 		      to libc, obsoleting libXThrStub.so.  5.0-RELEASE.</entry>
 		    <entry>500043</entry>
 		  </row>
 
 		  <row>
 		    <entry>5.0-CURRENT after branching for RELENG_5_0</entry>
 		    <entry>500100</entry>
 		  </row>
 		  <row>
 		    <entry>&lt;sys/dkstat.h&gt; is empty and should
 		    not be included.</entry>
 		    <entry>500101</entry>
 		  </row>
 		  <row>
 		    <entry>5.0-CURRENT after the d_mmap_t interface
 		      change.</entry>
 		    <entry>500102</entry>
 		  </row>
 		  <row>
 		    <entry>5.0-CURRENT after taskqueue_swi changed to run
 		      without Giant, and taskqueue_swi_giant added to run
 		      with Giant.</entry>
 		    <entry>500103</entry>
 		  </row>
 		  <row>
 		    <entry>cdevsw_add() and cdevsw_remove() no
 		      longer exists.
 		      Appearance of MAJOR_AUTO allocation facility.</entry>
 		    <entry>500104</entry>
 		  </row>
 		  <row>
 		    <entry>5.0-CURRENT after new cdevsw initialization method.</entry>
 		    <entry>500105</entry>
 		  </row>
 		  <row>
 		    <entry>devstat_add_entry() has been replaced by
 		      devstat_new_entry()</entry>
 		    <entry>500106</entry>
 		  </row>
 		  <row>
 		    <entry>Devstat interface change; see sys/sys/param.h 1.149</entry>
 		    <entry>500107</entry>
 		  </row>
 		  <row>
 		    <entry>Token-Ring interface changes.</entry>
 		    <entry>500108</entry>
 		  </row>
 		  <row>
 		    <entry>Addition of vm_paddr_t.</entry>
 		    <entry>500109</entry>
 		  </row>
 		  <row>
 		    <entry>5.0-CURRENT after &man.realpath.3; has been made
 		      thread-safe</entry>
 		    <entry>500110</entry>
 		  </row>
 		  <row>
 		    <entry>5.0-CURRENT after &man.usbhid.3; has been synced with
 		      NetBSD</entry>
 		    <entry>500111</entry>
 		  </row>
 		  <row>
 		    <entry>5.0-CURRENT after new NSS implementation
 		      and addition of POSIX.1 getpw*_r, getgr*_r
 		      functions</entry>
 		    <entry>500112</entry>
 		  </row>
 		  <row>
 		    <entry>5.0-CURRENT after removal of the old rc system.</entry>
 		    <entry>500113</entry>
 		  </row>
 		  <row>
 		    <entry>5.1-RELEASE.</entry>
 		    <entry>501000</entry>
 		  </row>
 		  <row>
 		    <entry>5.1-CURRENT after branching for RELENG_5_1.</entry>
 		    <entry>501100</entry>
 		  </row>
 		  <row>
 		    <entry>5.1-CURRENT after correcting the semantics of
 		      sigtimedwait(2) and sigwaitinfo(2).</entry>
 		    <entry>501101</entry>
 		  </row>
 		  <row>
 		    <entry>5.1-CURRENT after adding the lockfunc and lockfuncarg
 		      fields to &man.bus.dma.tag.create.9;.</entry>
 		    <entry>501102</entry>
 		  </row>
 		  <row>
 		    <entry>5.1-CURRENT after GCC 3.3.1-pre 20030711 snapshot
 		      integration.</entry>
 		    <entry>501103</entry>
 		  </row>
 		  <row>
 		    <entry>5.1-CURRENT 3ware API changes to twe.</entry>
 		    <entry>501104</entry>
 		  </row>
 		  <row>
 		    <entry>5.1-CURRENT dynamically-linked /bin and /sbin
 		      support and movement of libraries to /lib.</entry>
 		    <entry>501105</entry>
 		  </row>
 		  <row>
 		    <entry>5.1-CURRENT after adding kernel support for
 		      Coda 6.x.</entry>
 		    <entry>501106</entry>
 		  </row>
 		  <row>
 		    <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>
 		    <entry>501107</entry>
 		  </row>
 		  <row>
 		    <entry>5.1-CURRENT after PFIL_HOOKS API update</entry>
 		    <entry>501108</entry>
 		  </row>
 		  <row>
 		    <entry>5.1-CURRENT after adding kiconv(3)</entry>
 		    <entry>501109</entry>
 		  </row>
 		  <row>
 		    <entry>5.1-CURRENT after changing default operations
 			for open and close in cdevsw</entry>
 		    <entry>501110</entry>
 		  </row>
 		  <row>
 		    <entry>5.1-CURRENT after changed layout of cdevsw</entry>
 		    <entry>501111</entry>
 		  </row>
 		  <row>
 		    <entry> 5.1-CURRENT after adding kobj multiple inheritance
 		    </entry>
 		    <entry>501112</entry>
 		  </row>
 		  <row>
 		    <entry> 5.1-CURRENT after the if_xname change in
 			struct ifnet</entry>
 		    <entry>501113</entry>
 		  </row>
 		  <row>
 		    <entry> 5.1-CURRENT after changing /bin and /sbin to
 			be dynamically linked</entry>
 		    <entry>501114</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-RELEASE</entry>
 		    <entry>502000</entry>
 		  </row>
 		  <row>
 		    <entry>5.2.1-RELEASE</entry>
 		    <entry>502010</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-CURRENT after branching for RELENG_5_2</entry>
 		    <entry>502100</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-CURRENT after __cxa_atexit/__cxa_finalize
 			functions were added to libc.</entry>
 		    <entry>502101</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-CURRENT after change of default thread library
 			from libc_r to libpthread.</entry>
 		    <entry>502102</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-CURRENT after device driver API megapatch.
 		    </entry>
 		    <entry>502103</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-CURRENT after getopt_long_only() addition.
 		    </entry>
 		    <entry>502104</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-CURRENT after NULL is made into ((void *)0)
 			for C, creating more warnings.
 		    </entry>
 		    <entry>502105</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-CURRENT after pf is linked to the build and
 			install.
 		    </entry>
 		    <entry>502106</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-CURRENT after time_t is changed to a
 			64-bit value on sparc64.
 		    </entry>
 		    <entry>502107</entry>
 		  </row>
 		  <row>
 		    <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>
 		    <entry>502108</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-CURRENT after the introduction of the
 		      bus_alloc_resource_any API
 		    </entry>
 		    <entry>502109</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-CURRENT after the addition of UTF-8 locales
 		    </entry>
 		    <entry>502110</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-CURRENT after the removal of the getvfsent(3)
 		      API
 		    </entry>
 		    <entry>502111</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-CURRENT after the addition of the .warning
 		      directive for make.</entry>
 		    <entry>502112</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-CURRENT after ttyioctl() was made mandatory
 		      for serial drivers.</entry>
 		    <entry>502113</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-CURRENT after import of the ALTQ framework.
 		    </entry>
 		    <entry>502114</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-CURRENT after changing sema_timedwait(9) to
 		      return 0 on success and a non-zero error code on
 		      failure.
 		    </entry>
 		    <entry>502115</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-CURRENT after changing kernel dev_t to
 		      be pointer to struct cdev *.
 		    </entry>
 		    <entry>502116</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-CURRENT after changing kernel udev_t to dev_t.
 		    </entry>
 		    <entry>502117</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-CURRENT after adding support for CLOCK_VIRTUAL
 		      and CLOCK_PROF to clock_gettime(2) and clock_getres(2).
 		    </entry>
 		    <entry>502118</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-CURRENT after changing network interface
 		      cloning overhaul.
 		    </entry>
 		    <entry>502119</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-CURRENT after the update of the package tools
 		      to revision 20040629.
 		    </entry>
 		    <entry>502120</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-CURRENT after marking Bluetooth code as
 		      non-i386 specific.
 		    </entry>
 		    <entry>502121</entry>
 		  </row>
 		  <row>
 		    <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>
 		    <entry>502122</entry>
 		  </row>
 		  <row>
 		    <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>
 		    <entry>502123</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-CURRENT after the change to separate the way
 		      ports rc.d and legacy scripts are started.
 		    </entry>
 		    <entry>502124</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-CURRENT after the backout of the
 		      previous change.
 		    </entry>
 		    <entry>502125</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-CURRENT after the removal of
 		      kmem_alloc_pageable() and the import of gcc 3.4.2.
 		    </entry>
 		    <entry>502126</entry>
 		  </row>
 		  <row>
 		    <entry>5.2-CURRENT after changing the UMA kernel
 		      API to allow ctors/inits to fail.
 		    </entry>
 		    <entry>502127</entry>
 		  </row>
 		  <row>
 		    <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>
 		    <entry>502128</entry>
 		  </row>
 		  <row>
 		    <entry>5.3-BETA/RC before the pfil API change</entry>
 		    <entry>503000</entry>
 		  </row>
 		  <row>
 		    <entry>5.3-RELEASE</entry>
 		    <entry>503001</entry>
 		  </row>
 		  <row>
 		    <entry>5.3-STABLE after branching for RELENG_5_3</entry>
 		    <entry>503100</entry>
 		  </row>
 		  <row>
 		    <entry>5.3-STABLE after addition of glibc style
 		      &man.strftime.3; padding options.</entry>
 		    <entry>503101</entry>
 		  </row>
 		  <row>
 		    <entry>5.3-STABLE after OpenBSD's nc(1) import MFC.</entry>
 		    <entry>503102</entry>
 		  </row>
 		  <row>
 		    <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>
 		    <entry>503103</entry>
  		  </row>
 		  <row>
 		    <entry>5.4-PRERELEASE after the MFC of the change of
 		       ifi_epoch from wall clock time to uptime.</entry>
 		    <entry>503104</entry>
  		  </row>
 		  <row>
 		    <entry>5.4-PRERELEASE after the MFC of the fix of EOVERFLOW check in vswprintf(3).</entry>
 		    <entry>503105</entry>
 		  </row>
 		  <row>
 		    <entry>5.4-RELEASE.</entry>
 		    <entry>504000</entry>
 		  </row>
 		  <row>
 		    <entry>5.4-STABLE after branching for RELENG_5_4</entry>
 		    <entry>504100</entry>
 		  </row>
 		  <row>
 		    <entry>5.4-STABLE after increasing the default
 		      thread stacksizes</entry>
 		    <entry>504101</entry>
 		  </row>
 		  <row>
 		    <entry>5.4-STABLE after the addition of sha256</entry>
 		    <entry>504102</entry>
 		  </row>
 		  <row>
 		    <entry>5.4-STABLE after the MFC of if_bridge</entry>
 		    <entry>504103</entry>
 		  </row>
 		  <row>
 		    <entry>5.4-STABLE after the MFC of bsdiff and portsnap</entry>
 		    <entry>504104</entry>
 		  </row>
+		  <row>
+		    <entry>5.4-STABLE after MFC of ldconfig_local_dirs
+		      change.</entry>
+		    <entry>504105</entry>
+		  </row>
 		  <row>
 		    <entry>6.0-CURRENT</entry>
 		    <entry>600000</entry>
 		  </row>
 		  <row>
 		    <entry>6.0-CURRENT after permanently enabling PFIL_HOOKS
 		      in the kernel.
 		    </entry>
 		    <entry>600001</entry>
 		  </row>
 		  <row>
 		    <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>
 		    <entry>600002</entry>
 		  </row>
 		  <row>
 		    <entry>6.0-CURRENT after the re-addition of the
 		      ifi_epoch member of struct if_data.
 		    </entry>
 		    <entry>600003</entry>
 		  </row>
 		  <row>
 		    <entry>6.0-CURRENT after addition of the struct inpcb
 		      argument to the pfil API.
 		    </entry>
 		    <entry>600004</entry>
 		  </row>
 		  <row>
 		    <entry>6.0-CURRENT after addition of the "-d
 		      DESTDIR" argument to newsyslog.
 		    </entry>
 		    <entry>600005</entry>
 		  </row>
 		  <row>
 		    <entry>6.0-CURRENT after addition of glibc style
 		      &man.strftime.3; padding options.
 		    </entry>
 		    <entry>600006</entry>
 		  </row>
 		  <row>
 		    <entry>6.0-CURRENT after addition of 802.11 framework
 		      updates.
 		    </entry>
 		    <entry>600007</entry>
 		  </row>
 		  <row>
 		    <entry>6.0-CURRENT after changes to VOP_*VOBJECT() functions
 		      and introduction of MNTK_MPSAFE flag for Giantfree filesystems.
 		    </entry>
 		    <entry>600008</entry>
 		  </row>
 		  <row>
 		    <entry>6.0-CURRENT after addition of the cpufreq framework
 		      and drivers.
 		    </entry>
 		    <entry>600009</entry>
 		  </row>
 		  <row>
 		    <entry>6.0-CURRENT after importing OpenBSD's nc(1).</entry>
 		    <entry>600010</entry>
 		  </row>
 		  <row>
 		    <entry>6.0-CURRENT after removing semblance of SVID2
 			<literal>matherr()</literal> support.</entry>
 		    <entry>600011</entry>
 		  </row>
 		  <row>
 		    <entry>6.0-CURRENT after increase of default thread stacks'
 			size.</entry>
 		    <entry>600012</entry>
 		  </row>
 		  <row>
 		    <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>
 		    <entry>600013</entry>
 		  </row>
 		  <row>
 		    <entry>6.0-CURRENT after EOVERFLOW checks in vswprintf(3) fixed.</entry>
 		    <entry>600014</entry>
 		  </row>
 		  <row>
 		    <entry>6.0-CURRENT after changing the struct if_data
 		       member, ifi_epoch, from wall clock time to uptime.</entry>
 		    <entry>600015</entry>
 		  </row>
 		  <row>
 		    <entry>6.0-CURRENT after LC_CTYPE disk format changed.</entry>
 		    <entry>600016</entry>
 		  </row>
 		  <row>
 		    <entry>6.0-CURRENT after NLS catalogs disk format changed.</entry>
 		    <entry>600017</entry>
 		  </row>
 		  <row>
 		    <entry>6.0-CURRENT after LC_COLLATE disk format changed.</entry>
 		    <entry>600018</entry>
 		  </row>
 		  <row>
 		    <entry>Installation of acpica includes into /usr/include.</entry>
 		    <entry>600019</entry>
 		  </row>
 		  <row>
 		    <entry>Addition of MSG_NOSIGNAL flag to send(2) API.</entry>
 		    <entry>600020</entry>
 		  </row>
 		  <row>
 		    <entry>Addition of fields to cdevsw</entry>
 		    <entry>600021</entry>
 		  </row>
 		  <row>
 		    <entry>Removed gtar from base system.</entry>
 		    <entry>600022</entry>
 		  </row>
 		  <row>
 		    <entry>LOCAL_CREDS, LOCAL_CONNWAIT socket options added to unix(4).</entry>
 		    <entry>600023</entry>
 		  </row>
 		  <row>
 		    <entry>&man.hwpmc.4; and related tools added to 6.0-CURRENT.</entry>
 		    <entry>600024</entry>
 		  </row>
 		  <row>
 		    <entry>struct icmphdr added to 6.0-CURRENT.</entry>
 		    <entry>600025</entry>
 		  </row>
 		  <row>
 		    <entry>pf updated to 3.7.</entry>
 		    <entry>600026</entry>
 		  </row>
 		  <row>
 		    <entry>Kernel libalias and ng_nat introduced.</entry>
 		    <entry>600027</entry>
 		  </row>
 		  <row>
 		    <entry>POSIX ttyname_r(3) made available through unistd.h and libc.</entry>
 		    <entry>600028</entry>
 		  </row>
 		  <row>
 		    <entry>6.0-CURRENT after libpcap updated to v0.9.1 alpha 096.</entry>
 		    <entry>600029</entry>
 		  </row>
 		  <row>
 		    <entry>6.0-CURRENT after importing NetBSD's if_bridge(4).</entry>
 		    <entry>600030</entry>
 		  </row>
 		  <row>
 		    <entry>6.0-CURRENT after struct ifnet was broken out
 		      of the driver softcs.</entry>
 		    <entry>600031</entry>
 		  </row>
 		  <row>
 		    <entry>6.0-CURRENT after the import of libpcap v0.9.1.</entry>
 		    <entry>600032</entry>
 		  </row>
 		  <row>
 		    <entry>6.0-STABLE after bump of all shared library
 		      versions that had not been changed since
 		      RELENG_5.</entry>
 		    <entry>600033</entry>
 		  </row>
 		  <row>
 		    <entry>6.0-STABLE after credential argument is added to
 		      dev_clone vent handler.  6.0-RELEASE.</entry>
 		    <entry>600034</entry>
 		  </row>
 		  <row>
 		    <entry>6.0-STABLE after 6.0-RELEASE</entry>
 		    <entry>600100</entry>
 		  </row>
 		  <row>
 		    <entry>6.0-STABLE after incorporating scripts from the
-		      local_startup directories into the base rcorder.</entry>
+		      local_startup directories into the base &man.rcorder.8;.</entry>
 		    <entry>600101</entry>
 		  </row>
+		  <row>
+		    <entry>6.0-STABLE after updating the ELF types and
+		      constants.</entry>
+		    <entry>600102</entry>
+		  </row>
+		  <row>
+		    <entry>6.0-STABLE after MFC of pidfile(3) API.</entry>
+		    <entry>600103</entry>
+		  </row>
+		  <row>
+		    <entry>6.0-STABLE after MFC of ldconfig_local_dirs
+		      change.</entry>
+		    <entry>600104</entry>
+		  </row>
 		  <row>
 		    <entry>7.0-CURRENT.</entry>
 		    <entry>700000</entry>
 		  </row>
 		  <row>
 		    <entry>7.0-CURRENT after bump of all shared library
 		      versions that had not been changed since
 		      RELENG_5.</entry>
 		    <entry>700001</entry>
 		  </row>
 		  <row>
 		    <entry>7.0-CURRENT after credential argument is added to
 		      dev_clone vent handler.</entry>
 		    <entry>700002</entry>
 		  </row>
 		  <row>
 		    <entry>7.0-CURRENT after memmem(3) is added to libc.</entry>
 		    <entry>700003</entry>
 		  </row>
 		  <row>
 		    <entry>7.0-CURRENT after solisten(9) kernel arguments
 		      are modified to accept a backlog paramater.</entry>
 		    <entry>700004</entry>
 		  </row>
 		  <row>
 		    <entry>7.0-CURRENT after IFP2ENADDR() was changed to return
 		      a pointer to IF_LLADDR().</entry>
 		    <entry>700005</entry>
 		  </row>
 		  <row>
 		    <entry>7.0-CURRENT after addition of <literal>if_addr</literal>
 		      member to <literal>struct ifnet</literal> and IFP2ENADDR()
 		      removal.</entry>
 		    <entry>700006</entry>
 		  </row>
 		  <row>
 		    <entry>7.0-CURRENT after incorporating scripts from the
-		      local_startup directories into the base rcorder.</entry>
+		      local_startup directories into the base &man.rcorder.8;.</entry>
 		    <entry>700007</entry>
 		  </row>
 		  <row>
 		    <entry>7.0-CURRENT after removal of MNT_NODEV mount
 		      option.</entry>
 		    <entry>700008</entry>
 		  </row>
 		  <row>
 		    <entry>7.0-CURRENT after ELF-64 type changes and symbol
 		      versioning.</entry>
 		    <entry>700009</entry>
 		  </row>
 		  <row>
 		    <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>
 		    <entry>700010</entry>
 		  </row>
+		  <row>
+		    <entry>7-0.CURRENT after tv_sec was made time_t on
+		      all platforms but Alpha.</entry>
+		    <entry>700011</entry>
+		  </row>
+		  <row>
+		    <entry>7-0.CURRENT after ldconfig_local_dirs change.</entry>
+		    <entry>700012</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>You need to 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="1">
 	  <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>PORTOBJFORMAT</makevar></entry>
 		<entry>The object format of the system
 		  (<literal>elf</literal> or <literal>aout</literal>;
 		  note that for <quote>modern</quote> versions of FreeBSD,
 		  <literal>aout</literal> is deprecated.)</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>X11BASE</makevar></entry>
 		<entry>The base of the <quote>X11</quote> tree (e.g.,
 		  <literal>/usr/X11R6</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>, <makevar>USE_X_PREFIX</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} > 300003
+.if ${OSVERSION} &gt; 300003
 BROKEN= perl is in system
 .endif
 
 # only one shlib version number for ELF
 .if ${PORTOBJFORMAT} == "elf"
 TCL_LIB_FILE=  ${TCL_LIB}.${SHLIB_MAJOR}
 .else
 TCL_LIB_FILE=  ${TCL_LIB}.${SHLIB_MAJOR}.${SHLIB_MINOR}
 .endif
 
 # software already makes link for ELF, but not for a.out
 post-install:
 .if ${PORTOBJFORMAT} == "aout"
        ${LN} -sf liblinpack.so.1.0 ${PREFIX}/lib/liblinpack.so
 .endif</programlisting>
 
 	<para>You did remember to use tab instead of spaces after
 	  <literal>BROKEN=</literal> and
 	  <literal>TCL_LIB_FILE=</literal>, did you not?
 	  <!-- smiley -->:-).</para>
       </sect1>
 
       <sect1 id="dads-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
 	  <makevar>NOPORTDOCS</makevar> so that users can disable it in
 	  <filename>/etc/make.conf</filename>, like this:</para>
 
 	<programlisting>post-install:
 .if !defined(NOPORTDOCS)
 	${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>DOCSDIR</makevar> gets expanded to
 	      <filename><makevar>PREFIX</makevar>/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>
 	</itemizedlist>
 
 	<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 documentation files and directories installed 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 <makevar>NOPORTDOCS</makevar>
 	  is defined then files and directories listed in 
 	  <makevar>PORTDOCS</makevar> would not be installed and neither
 	  would be 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>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>
       </sect1>
 
       <sect1 id="dads-subdirs">
 	<title>Subdirectories</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 the 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>
       </sect1>
 
       <sect1 id="dads-uid-and-gids">
 	<title>UIDs and GIDs</title>
 
 	<para>If your port requires a certain user to be on the installed
 	  system, let the <filename>pkg-install</filename> script call
 	  <command>pw</command> to create it automatically.  Look at
 	  <filename role="package">net/cvsup-mirror</filename> for an example.</para>
 
 	<para>If your port must use the same user/group ID number when it is
 	  installed as a binary package as when it was compiled, then you must
 	  choose a free UID from 50 to 999 and register it below.  Look at
 	  <filename role="package">japanese/Wnn6</filename> for an example.</para>
 
 	<para>Make sure you do not use a UID already used by the system or
 	  other ports.</para>
 
 	<para>This is the current list of UIDs between 50 and 999.</para>
 
 	<!-- Please keep this list sorted by uid -->
 	<programlisting>bind:*:53:53:Bind Sandbox:/:/sbin/nologin
 majordom:*:54:54:Majordomo Pseudo User:/usr/local/majordomo:/nonexistent
 rdfdb:*:55:55:rdfDB Daemon:/var/db/rdfdb:/bin/sh
 spamd:*:58:58:SpamAssassin user:/var/spool/spamd:/sbin/nologin
 cyrus:*:60:60:the cyrus mail server:/nonexistent:/nonexistent
 gnats:*:61:1:GNATS database owner:/usr/local/share/gnats/gnats-db:/bin/sh
 proxy:*:62:62:Packet Filter pseudo-user:/nonexistent:/nonexistent
 uucp:*:66:66:UUCP pseudo-user:/var/spool/uucppublic:/usr/libexec/uucp/uucico
 xten:*:67:67:X-10 daemon:/usr/local/xten:/nonexistent
 pop:*:68:6:Post Office Owner (popper):/nonexistent:/sbin/nologin
 wnn:*:69:7:Wnn:/nonexistent:/nonexistent
 pgsql:*:70:70:PostgreSQL pseudo-user:/usr/local/pgsql:/bin/sh
 oracle:*:71:71::0:0:Oracle:/usr/local/oracle7:/sbin/nologin
 ircd:*:72:72:IRC daemon:/nonexistent:/nonexistent
 ircservices:*:73:73:IRC services:/nonexistent:/nonexistent
 simscan:*:74:74:Simscan User:/nonexistent:/sbin/nologin
 ifmail:*:75:66:Ifmail user:/nonexistent:/nonexistent
 www:*:80:80:World Wide Web Owner:/nonexistent:/sbin/nologin
 alias:*:81:81:QMail user:/var/qmail/alias:/nonexistent
 qmaild:*:82:81:QMail user:/var/qmail:/nonexistent
 qmaill:*:83:81:QMail user:/var/qmail:/nonexistent
 qmailp:*:84:81:QMail user:/var/qmail:/nonexistent
 qmailq:*:85:82:QMail user:/var/qmail:/nonexistent
 qmailr:*:86:82:QMail user:/var/qmail:/nonexistent
 qmails:*:87:82:QMail user:/var/qmail:/nonexistent
 mysql:*:88:88:MySQL Daemon:/var/db/mysql:/sbin/nologin
 vpopmail:*:89:89:VPop Mail User:/usr/local/vpopmail:/nonexistent
 firebird:*:90:90:Firebird Database Administrator:/usr/local/firebird:/bin/sh
 mailman:*:91:91:Mailman User:/usr/local/mailman:/sbin/nologin
 gdm:*:92:92:GDM Sandbox:/:/sbin/nologin
 jabber:*:93:93:Jabber Daemon:/nonexistent:/nonexistent
 p4admin:*:94:94:Perforce admin:/usr/local/perforce:/sbin/nologin
 interch:*:95:95:Interchange user:/usr/local/interchange:/sbin/nologin
 squeuer:*:96:96:SQueuer Owner:/nonexistent:/bin/sh
 mud:*:97:97:MUD Owner:/nonexistent:/bin/sh
 msql:*:98:98:mSQL-2 pseudo-user:/var/db/msqldb:/bin/sh
 rscsi:*:99:99:Remote SCSI:/usr/local/rscsi:/usr/local/sbin/rscsi
 squid:*:100:100:squid caching-proxy pseudo user:/usr/local/squid:/sbin/nologin
 quagga:*:101:101:Quagga route daemon pseudo user:/usr/local/etc/quagga:/sbin/nologin
 ganglia:*:102:102:Ganglia User:/nonexistent:/sbin/nologin
 sgeadmin:*:103:103:Sun Grid Engine Admin:/nonexistent:/sbin/nologin
 slimserv:*:104:104:Slim Devices SlimServer pseudo-user:/nonexistent:/sbin/nologin
 dnetc:*:105:105:distributed.net client and proxy pseudo-user:/nonexistent:/sbin/nologin
 clamav:*:106:106:Clamav Antivirus:/nonexistent:/sbin/nologin
 cacti:*:107:107:Cacti Sandbox:/nonexistent:/sbin/nologin
 webkit:*:108:108:WebKit Default User:/usr/local/www/webkit:/bin/sh
 quickml:*:109:109:quickml Server:/nonexistent:/sbin/nologin
 vscan:*:110:110:Scanning Virus Account:/var/amavis:/bin/sh
 fido:*:111:111:Fido System:/usr/local/fido:/bin/sh
 dcc:*:112:112:Distributed Checksum Clearinghouse:/nonexistent:/sbin/nologin
 amavis:*:113:113:Amavis-stats Account:/nonexistent:/sbin/nologin
 dhis:*:114:114:DHIS Daemon:/nonexistent:/sbin/nologin
 _symon:*:115:115:Symon Account:/var/empty:/sbin/nologin
 postfix:*:125:125:Postfix Mail System:/var/spool/postfix:/sbin/nologin
 rbldns:*:153:153:rbldnsd pseudo-user:/nonexistent:/sbin/nologin
 sfs:*:171:171:Self-Certifying File System:/nonexistent:/sbin/nologin
 agk:*:172:172:AquaGateKeeper:/nonexistent:/nonexistent
 polipo:*:173:173:polipo web cache:/nonexistent:/sbin/nologin
 bogomilter:*:174:174:milter-bogom:/nonexistent:/sbin/nologin
 moinmoin:*:192:192:MoinMoin User:/nonexistent:/sbin/nologin
 sympa:*:200:200:Sympa Owner:/nonexistent:/sbin/nologin
 privoxy:*:201:201:Privoxy proxy user:/nonexistent:/sbin/nologin
 dspam:*:202:202:Dspam:/nonexistent:/sbin/nologin
 shoutcast:*:210:210:Shoutcast sandbox:/nonexistent:/bin/sh
 _tor:*:256:256:Tor anonymising router:/var/db/tor:/bin/sh
 smxs:*:260:260:Sendmail X SMTPS:/nonexistent:/sbin/nologin
 smxq:*:261:261:Sendmail X QMGR:/nonexistent:/sbin/nologin
 smxc:*:262:262:Sendmail X SMTPC:/nonexistent:/sbin/nologin
 smxm:*:263:263:Sendmail X misc:/nonexistent:/sbin/nologin
 smx:*:264:264:Sendmail X other:/nonexistent:/sbin/nologin
 ldap:*:389:389:OpenLDAP Server:/nonexistent:/sbin/nologin
 drweb:*:426:426:Dr.Web Mail Scanner:/nonexistent:/sbin/nologin
 courier:*:465:465:Courier Mail Server:/nonexistent:/sbin/nologin
 _bbstored:*:505:505::0:0:BoxBackup Store Daemon:/nonexistent:/bin/sh
 qtss:*:554:554:Darwin Streaming Server:/nonexistent:/sbin/nologin
 ircdru:*:555:555:Russian hybrid IRC server:/nonexistent:/bin/sh
 messagebus:*:556:556:D-BUS Daemon User:/nonexistent:/sbin/nologin
 avahi:*:558:558:Avahi Daemon User:/nonexistent:/sbin/nologin
 bnetd:*:700:700:Bnetd user:/nonexistent:/sbin/nologin
 bopm:*:717:717:Blitzed Open Proxy Monitor:/nonexistent:/bin/sh
 bacula:*:910:910:Bacula Daemon:/var/db/bacula:/sbin/nologin</programlisting>
 
 	<para>This is the current list of reserved GIDs.</para>
 
 	<!-- Please keep this list sorted by gid -->
 	<!-- XXX incomplete! -->
 	<programlisting>bind:*:53:
 rdfdb:*:55:
 spamd:*:58:
 cyrus:*:60:
 proxy:*:62:
 authpf:*:63:
 uucp:*:66:
 xten:*:67:
 dialer:*:68:
 network:*:69:
 pgsql:*:70:
 simscan:*:74:
 www:*:80:
 qnofiles:*:81:
 qmail:*:82:
 mysql:*:88:
 vpopmail:*:89:
 firebird:*:90:
 mailman:*:91:
 gdm:*:92:
 jabber:*:93:
 p4admin:*:94:
 interch:*:95:
 squeuer:*:96:
 mud:*:97:
 msql:*:98:
 rscsi:*:99:
 squid:*:100:
 quagga:*:101:
 ganglia:*:102:
 sgeadmin:*:103:
 slimserv:*:104:
 dnetc:*:105:
 clamav:*:106:
 cacti:*:107:
 webkit:*:108:
 quickml:*:109:
 vscan:*:110:
 fido:*:111:
 dcc:*:112:
 amavis:*:113:
 dhis:*:114:
 _symon:*:115:
 postfix:*:125:
 maildrop:*:126:
 rbldns:*:153:
 sfs:*:171:
 agk:*:172:
 polipo:*:173:
 moinmoin:*:192:
 sympa:*:200:
 dspam:*:202:
 _tor:*:256:
 smxs:*:260:
 smxq:*:261:
 smxc:*:262:
 smxm:*:263:
 smx:*:264:
 ldap:*:389:
 drweb:*:426:
 courier:*:465:
 _bbstored:*:505:
 qtss:*:554:
 ircdru:*:555:
 messagebus:*:556:
 realtime:*:557:
 avahi:*:558:
 bnetd:*:700:
 bopm:*:717:
 bacula:*:910:</programlisting>
 
 	<para>Please include a notice when you submit a port (or an upgrade)
 	  that reserves a new UID or GID in this range.  This allows us to
 	  keep the list of reserved IDs up to date.</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 should respect both <makevar>CC</makevar>
 	  and <makevar>CXX</makevar> variables.  What we mean by this
 	  is that the port should not set the values of these variables
 	  absolutely, overriding existing values; instead, it should 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 should respect the <makevar>CFLAGS</makevar> variable.
 	  What we mean by this is that the port should not set the value of
 	  this variable absolutely, overriding the existing value; instead,
 	  it should 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 linker flag <literal>-pthread</literal> on
+	  &os;.  If a port insists on linking
+	  <literal>-lpthread</literal> or <literal>-lc_r</literal>
+	  directly, patch it to use <makevar>PTHREAD_LIBS</makevar>
+	  variable provided by the ports framework.  This variable
+	  usually has the value of <literal>-pthread</literal>, but
+	  on certain architectures and &os; versions it can have
+	  different values, so do not just hardcode
+	  <literal>-pthread</literal> into patches and always use
+	  <makevar>PTHREAD_LIBS</makevar>.</para>
+      </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 cvs collection but is generated using the
 	  <command>make readme</command> command.
 	</para>
       </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 the problem is
 	      believed to be temporary.
 	      The build cluster will still attempt to try to build
 	      them to see if the underlying problem has been
 	      resolved.  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> and
 		  <filename>${X11BASE}</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
 	      do contain a security vulnerability or induce grave
 	      concern regarding the security of a FreeBSD system with
 	      a given port installed (ex: 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 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/apache21</filename> but
 		  <filename role="package">www/apache13</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 perfoms 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 sould 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= alpha ia64 sparc64</programlisting>
 	  </listitem>
 
 	</itemizedlist>
 
 	</sect2>
 	<sect2 id="dads-noinstall-notes">
 	  <title>Implementation Notes</title>
 
 	  <para>Due to vagaries in the usage of <makevar>IGNORECMD</makevar>
 	    in <filename>bsd.port.mk</filename> among other places,
 	    the value of <makevar>BROKEN</makevar> should be enclosed
 	    in quotes, and the value of <makevar>IGNORE</makevar> should
 	    not be enclosed in quotes.</para>
 
 	  <para>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>===>  foobar-0.1 is marked as broken: this port is unsupported on FreeBSD 5.x.</programlisting>
+	  <programlisting>===&gt;  foobar-0.1 is marked as broken: this port is unsupported on FreeBSD 5.x.</programlisting>
 
-	  <programlisting>===>  foobar-0.1 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 nonblank 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 occurence 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 -V 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
 	    <programlisting>USE_POINTYHAT=yes</programlisting>
 	    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-workarounds">
 	<title>Necessary workarounds</title>
 
 	<para>Sometimes it is necessary to work around bugs in
 	  software included with older versions of &os;.</para>
 
 	<itemizedlist>
 	  <listitem>
 	    <para>Some versions of &man.make.1; were broken
 	      on at least 4.8 and 5.0 with respect to handling
 	      comparisons based on <makevar>OSVERSION</makevar>.
 	      This would often lead to failures during
 	      <command>make describe</command> (and thus, the overall
 	      ports <command>make index</command>).  The workaround is
 	      to enclose the conditional comparison in spaces, e.g.:
-	      <programlisting>if ( ${OSVERSION} > 500023 )</programlisting>
+	      <programlisting>if ( ${OSVERSION} &gt; 500023 )</programlisting>
 	      Be aware that test-installing a port on 4.9 or 5.2
 	      will <emphasis>not</emphasis> detect this problem.</para>
 	  </listitem>
 
 	</itemizedlist>
 
       </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.]
 # New ports collection makefile for:   xdvi
 [the "version required" line is only needed when the PORTVERSION
  variable is not specific enough to describe the port.]
 # Date created:                26 May 1995
 [this is the person who did the original port to FreeBSD, in particular, the
 person who wrote the first version of this Makefile.  Remember, this should
 not be changed when upgrading the port later.]
 # Whom:                        Satoshi Asami &lt;asami@FreeBSD.org&gt;
 #
 # &dollar;FreeBSD&dollar;
 [ ^^^^^^^^^ This will be automatically replaced with RCS ID string by CVS
 when it is committed to our repository.  If upgrading a port, do not alter
 this line back to "&dollar;FreeBSD&dollar;".  CVS 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.5:${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="cvsweb">
 	<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://cvsweb.FreeBSD.org/ports/CHANGES">
 	  CHANGES</ulink> file.  Changes that affect individual ports
 	  are now documented in the
 	  <ulink url="http://cvsweb.FreeBSD.org/ports/UPDATING">
 	  UPDATING</ulink> file.  However, the definitive answer to any
 	  question is undoubtedly to read the source code of <ulink
 	  url="http://cvsweb.FreeBSD.org/ports/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>
 
       </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>The &os; Port Distfile Survey</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.  The <ulink
 	    url="http://people.FreeBSD.org/~fenner/portsurvey/">FreeBSD
 	    Ports distfiles survey</ulink> attempts to query every
 	    download site for every port to find out if each distfile
 	    is still currently available.  Maintainers are asked to
 	    check this report periodically, not only to speed up the
 	    building process for users, but to help avoid wasting
 	    bandwidth of the sites that volunteer to host all these
 	    distfiles.</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 its 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>
 </book>
 
 <!--
      Local Variables:
      mode: sgml
      sgml-indent-data: t
      sgml-omittag: nil
      sgml-always-quote-attributes: t
      End:
 -->
diff --git a/zh_TW.Big5/share/sgml/glossary/freebsd-glossary.sgml b/zh_TW.Big5/share/sgml/glossary/freebsd-glossary.sgml
index 95c9da32dc..785bb437c8 100644
--- a/zh_TW.Big5/share/sgml/glossary/freebsd-glossary.sgml
+++ b/zh_TW.Big5/share/sgml/glossary/freebsd-glossary.sgml
@@ -1,1926 +1,1920 @@
 <!--
     $FreeBSD$
 
     FreeBSD Glossary Terms
 	Please keep this file sorted alphabetically/ASCIIly by glossterm.
 
 	glossterms that are acronyms should have two entries - one for
 	the expanded acronym and another for the acronym itself.  The
 	second of these should reference the entry for the expanded acronym
 	via a glosssee element.  For example:
 
 	<glossentry>
 	  <glossterm>FUBAR</glossterm>
 	  <glosssee otherterm="fubar-glossary">
 	</glossentry>
 
 	<glossentry id="fubar-glossary">
 	  <glossterm>Fuc... Up Beyond All Recognition</glossterm>
 	  <acronym>FUBAR</acronym>
 	  <glossdef>
 	    <para>Broken.</para>
 	  </glossdef>
 	</glossentry>
 
 	Note that in this instance, the expanded acronym sorts below the
 	unexpanded acronym.  That's OK.
 
 	Finally, id attribute values should end in the string
 	"-glossary" to avoid conflicting with id attribute values in
 	the main text.
 
 -->
 
 <glossary status="draft" id="freebsd-glossary">
   <title>&os; Glossary</title>
   <para>This glossary contains terms and acronyms used within the &os;
     community and documentation.</para>
 
   <glossdiv>
     <title>A</title>
 
     <glossentry>
       <glossterm>ACL</glossterm>
       <glosssee otherterm="acl-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>ACPI</glossterm>
       <glosssee otherterm="acpi-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>AMD</glossterm>
       <glosssee otherterm="amd-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>AML</glossterm>
       <glosssee otherterm="aml-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>API</glossterm>
       <glosssee otherterm="api-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>APIC</glossterm>
       <glosssee otherterm="apic-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>APM</glossterm>
       <glosssee otherterm="apm-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>APOP</glossterm>
       <glosssee otherterm="apop-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>ASL</glossterm>
       <glosssee otherterm="asl-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>ATA</glossterm>
       <glosssee otherterm="ata-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>ATM</glossterm>
       <glosssee otherterm="atm-glossary">
     </glossentry>
 
     <glossentry id="aml-glossary">
       <glossterm><acronym>ACPI</acronym> Machine Language</glossterm>
       <acronym>AML</acronym>
       <glossdef>
         <para>Pseudocode, interpreted by a virtual machine within an
 	  <acronym>ACPI</acronym>-compliant operating system, providing a
 	  layer between the underlying hardware and the documented
 	  interface presented to the <acronym>OS</acronym>.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="asl-glossary">
       <glossterm><acronym>ACPI</acronym> Source Language</glossterm>
       <acronym>ASL</acronym>
       <glossdef>
         <para>The programming language <acronym>AML</acronym> is written in.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="acl-glossary">
       <glossterm>Access Control List</glossterm>
       <acronym>ACL</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="acpi-glossary">
       <glossterm>Advanced Configuration and Power Interface</glossterm>
       <acronym>ACPI</acronym>
       <glossdef>
         <para>A specification which provides an abstraction of the
 	  interface the hardware presents to the operating system, so
 	  that the operating system should need to know nothing about
 	  the underlying hardware to make the most of it.  <acronym>ACPI</acronym>
 	  evolves and supercedes the functionality provided previously by
 	  <acronym>APM</acronym>, <acronym>PNPBIOS</acronym> and other technologies, and
 	  provides facilities for controlling power consumption, machine
 	  suspension, device enabling and disabling, etc.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="api-glossary">
       <glossterm>Application Programming Interface</glossterm>
       <acronym>API</acronym>
       <glossdef>
         <para>A set of procedures, protocols and tools that specify the
 	  canonical interaction of one or more program parts; how, when
 	  and why they do work together, and what data they share or
 	  operate on.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="apm-glossary">
       <glossterm>Advanced Power Management</glossterm>
       <acronym>APM</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="apic-glossary">
       <glossterm>Advanced Programmable Interrupt Controller</glossterm>
       <acronym>APIC</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="ata-glossary">
       <glossterm>Advanced Technology Attachment</glossterm>
       <acronym>ATA</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="atm-glossary">
       <glossterm>Asynchronous Transfer Mode</glossterm>
       <acronym>ATM</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="apop-glossary">
       <glossterm>Authenticated Post Office Protocol</glossterm>
       <acronym>APOP</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="amd-glossary">
       <glossterm>Automatic Mount Daemon</glossterm>
       <acronym>AMD</acronym>
       <glossdef>
         <para>A daemon that automatically mounts a filesystem when a file
           or directory within that filesystem is accessed.</para>
       </glossdef>
     </glossentry>
   </glossdiv>
 
   <glossdiv>
     <title>B</title>
 
     <glossentry>
       <glossterm>BIND</glossterm>
       <glosssee otherterm="bind-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>BIOS</glossterm>
       <glosssee otherterm="bios-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>BSD</glossterm>
       <glosssee otherterm="bsd-glossary">
     </glossentry>
 
     <glossentry id="bios-glossary">
       <glossterm>Basic Input/Output System</glossterm>
       <acronym>BIOS</acronym>
       <glossdef>
         <para>The definition of <acronym>BIOS</acronym> depends a bit on
 	  the context. Some people refer to it as the <acronym>ROM</acronym>
 	  chip with a basic set of routines to provide an interface between
 	  software and hardware.  Others refer to it as the set of routines
 	  contained in the chip that help in bootstrapping the system.  Some
 	  might also refer to it as the screen used to configure the
 	  boostrapping process. The <acronym>BIOS</acronym> is PC-specific
 	  but other systems have something similar.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="bind-glossary">
       <glossterm>Berkeley Internet Name Domain</glossterm>
       <acronym>BIND</acronym>
       <glossdef>
 	<para>An implementation of the <acronym>DNS</acronym> protocols.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="bsd-glossary">
       <glossterm>Berkeley Software Distribution</glossterm>
       <acronym>BSD</acronym>
       <glossdef>
-	<para>This is the name that the Computer Systems Research Group
-	  (CSRG) at <ulink url="http://www.berkeley.edu">The University
-	  of California at Berkeley</ulink>
-	  gave to their improvements and modifications to
-	  AT&amp;T's 32V &unix;.
-	  &os; is a descendant of the CSRG work.</para>
+	<para>³o¬O¥Ñ <ulink url="http://www.berkeley.edu">U.C. Berkeley</ulink> ªº
+	  Computer Systems Research Group(CSRG) ¿ï¨Ó·í§@¥L­Ì©Ò§ï¨}¡B­×§ï¹Lªº 
+	  AT&amp;T's 32V &unix; ¦WºÙ¡C&os; «h¬O¥Ñ CSRG ªº³o­Ó¤ß¦å­l¥Í¥X¨Ó¡C<para>
       </glossdef>
     </glossentry>
 
     <glossentry id="bikeshed-glossary">
       <glossterm>Bikeshed Building</glossterm>
       <glossdef subject="FreeBSD">
 	<para>A phenomenon whereby many people will give an opinion on
 	  an uncomplicated topic, whilst a complex topic receives little
 	  or no discussion.  See the
 	  <ulink url="&url.books.faq;/misc.html#BIKESHED-PAINTING">FAQ</ulink> for
 	  the origin of the term.</para>
       </glossdef>
     </glossentry>
   </glossdiv>
 
   <glossdiv>
     <title>C</title>
 
     <glossentry>
       <glossterm>CD</glossterm>
       <glosssee otherterm="cd-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>CHAP</glossterm>
       <glosssee otherterm="chap-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>CLIP</glossterm>
       <glosssee otherterm="clip-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>COFF</glossterm>
       <glosssee otherterm="coff-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>CPU</glossterm>
       <glosssee otherterm="cpu-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>CTS</glossterm>
       <glosssee otherterm="cts-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>CVS</glossterm>
       <glosssee otherterm="cvs-glossary">
     </glossentry>
 
     <glossentry id="cd-glossary">
       <glossterm>Carrier Detect</glossterm>
       <acronym>CD</acronym>
       <glossdef>
         <para>An RS232C signal indicating that a carrier has been
           detected.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="cpu-glossary">
       <glossterm>Central Processing Unit</glossterm>
       <acronym>CPU</acronym>
       <glossdef>
         <para>Also known as the processor.  This is the brain of the
 	  computer where all calculations take place.  There are a number of
 	  different architectures with different instruction sets.  Among
 	  the more well-known are the Intel-x86 and derivatives, Sun SPARC,
 	  PowerPC, and Alpha.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="chap-glossary">
       <glossterm>Challenge Handshake Authentication Protocol</glossterm>
       <acronym>CHAP</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="clip-glossary">
       <glossterm>Classical <acronym>IP</acronym> over <acronym>ATM</acronym></glossterm>
       <acronym>CLIP</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="cts-glossary">
       <glossterm>Clear To Send</glossterm>
       <acronym>CTS</acronym>
       <glossdef>
         <para>An RS232C signal giving the remote system
           permission to send data.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="coff-glossary">
       <glossterm>Common Object File Format</glossterm>
       <acronym>COFF</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="cvs-glossary">
       <glossterm>Concurrent Versions System</glossterm>
       <acronym>CVS</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
   </glossdiv>
 
   <glossdiv>
     <title>D</title>
 
     <glossentry>
       <glossterm>DAC</glossterm>
       <glosssee otherterm="dac-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>DDB</glossterm>
       <glosssee otherterm="ddb-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>DES</glossterm>
       <glosssee otherterm="des-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>DHCP</glossterm>
       <glosssee otherterm="dhcp-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>DNS</glossterm>
       <glosssee otherterm="dns-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>DSDT</glossterm>
       <glosssee otherterm="dsdt-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>DSR</glossterm>
       <glosssee otherterm="dsr-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>DTR</glossterm>
       <glosssee otherterm="dtr-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>DVMRP</glossterm>
       <glosssee otherterm="dvmrp-glossary">
     </glossentry>
 
     <glossentry id="dac-glossary">
       <glossterm>Discretionary Access Control</glossterm>
       <acronym>DAC</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="des-glossary">
       <glossterm>Data Encryption Standard</glossterm>
       <acronym>DES</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="dsr-glossary">
       <glossterm>Data Set Ready</glossterm>
       <acronym>DSR</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="dtr-glossary">
       <glossterm>Data Terminal Ready</glossterm>
       <acronym>DTR</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="ddb-glossary">
       <glossterm>Debugger</glossterm>
       <acronym>DDB</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="dsdt-glossary">
       <glossterm>Differentiated System Description Table</glossterm>
       <acronym>DSDT</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="dvmrp-glossary">
       <glossterm>Distance-Vector Multicast Routing Protocol</glossterm>
       <acronym>DVMRP</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="dns-glossary">
       <glossterm>Domain Name System</glossterm>
       <acronym>DNS</acronym>
       <glossdef>
 	<para>The system that converts humanly readable hostnames (i.e.,
 	  mail.example.net) to Internet addresses and vice versa.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="dhcp-glossary">
       <glossterm>Dynamic Host Configuration Protocol</glossterm>
       <acronym>DHCP</acronym>
       <glossdef>
 	<para>A protocol that dynamically assigns IP addresses to a computer
 	  (host) when it requests one from the server.  The address assignment
 	  is called a <quote>lease</quote>.<para>
       </glossdef>
     </glossentry>
   </glossdiv>
 
   <glossdiv>
     <title>E</title>
 
     <glossentry>
       <glossterm>ECOFF</glossterm>
       <glosssee otherterm="ecoff-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>ELF</glossterm>
       <glosssee otherterm="elf-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>ESP</glossterm>
       <glosssee otherterm="esp-glossary">
     </glossentry>
 
     <glossentry id="esp-glossary">
       <glossterm>Encapsulated Security Payload</glossterm>
       <acronym>ESP</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="elf-glossary">
       <glossterm>Executable and Linking Format</glossterm>
       <acronym>ELF</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="ecoff-glossary">
       <glossterm>Extended <acronym>COFF</acronym></glossterm>
       <acronym>ECOFF</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
   </glossdiv>
 
   <glossdiv>
     <title>F</title>
 
     <glossentry>
       <glossterm>FADT</glossterm>
       <glosssee otherterm="fadt-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>FAT</glossterm>
       <glosssee otherterm="fat-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>FAT16</glossterm>
       <glosssee otherterm="fat16-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>FTP</glossterm>
       <glosssee otherterm="ftp-glossary">
     </glossentry>
 
     <glossentry id="fat-glossary">
       <glossterm>File Allocation Table</glossterm>
       <acronym>FAT</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="fat16-glossary">
       <glossterm>File Allocation Table (16-bit)</glossterm>
       <acronym>FAT16</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="ftp-glossary">
       <glossterm>File Transfer Protocol</glossterm>
       <acronym>FTP</acronym>
       <glossdef>
 	<para>A member of the family of high-level protocols implemented
 	  on top of <acronym>TCP</acronym> which can be used to transfer
 	  files over a <acronym>TCP/IP</acronym> network.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="fadt-glossary">
       <glossterm>Fixed <acronym>ACPI</acronym> Description Table</glossterm>
       <acronym>FADT</acronym>
       <glossdef>
         <para></para>
       </glossdef>
   </glossdiv>
 
   <glossdiv>
     <title>G</title>
 
     <glossentry>
       <glossterm>GUI</glossterm>
       <glosssee otherterm="gui-glossary">
     </glossentry>
 
     <glossentry id="giant-glossary">
       <glossterm>Giant</glossterm>
       <glossdef subject="FreeBSD">
 	<para>The name of a mutual exclusion mechanism
 	  (a <literal>sleep mutex</literal>) that protects a large
 	  set of kernel resources.  Although a simple locking mechanism
 	  was adequate in the days where a machine might have only
 	  a few dozen processes, one networking card, and certainly
 	  only one processor, in current times it is an unacceptable
 	  performance bottleneck.  &os; developers are actively working
 	  to replace it with locks that protect individual resources,
 	  which will allow a much greater degree of parallelism for
 	  both single-processor and multi-processor machines.</para>
       </glossdef>
     </glossentry>
     
     <glossentry id="gui-glossary">
       <glossterm>Graphical User Interface</glossterm>
       <acronym>GUI</acronym>
       <glossdef>
         <para>A system where the user and computer interact with
           graphics.</para>
       </glossdef>
     </glossentry>
   </glossdiv>
 
   <glossdiv>
     <title>H</title>
 
     <glossentry>
       <glossterm>HTML</glossterm>
       <glosssee otherterm="html-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>HUP</glossterm>
       <glosssee otherterm="hup-glossary">
     </glossentry>
 
     <glossentry id="hup-glossary">
       <glossterm>HangUp</glossterm>
       <acronym>HUP</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="html-glossary">
       <glossterm>HyperText Markup Language</glossterm>
       <acronym>HTML</acronym>
       <glossdef>
         <para>The markup language used to create web pages.</para>
       </glossdef>
     </glossentry>
   </glossdiv>
 
   <glossdiv>
     <title>I</title>
 
     <glossentry>
       <glossterm>I/O</glossterm>
       <glosssee otherterm="io-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>IASL</glossterm>
       <glosssee otherterm="iasl-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>IMAP</glossterm>
       <glosssee otherterm="imap-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>IP</glossterm>
       <glosssee otherterm="ip-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>IPFW</glossterm>
       <glosssee otherterm="ipfw-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>IPP</glossterm>
       <glosssee otherterm="ipp-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>IPv4</glossterm>
       <glosssee otherterm="ipv4-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>IPv6</glossterm>
       <glosssee otherterm="ipv6-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>ISP</glossterm>
       <glosssee otherterm="isp-glossary">
     </glossentry>
 
     <glossentry id="ipfw-glossary">
       <glossterm><acronym>IP</acronym> Firewall</glossterm>
       <acronym>IPFW</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="ipv4-glossary">
       <glossterm><acronym>IP</acronym> Version 4</glossterm>
       <acronym>IPv4</acronym>
       <glossdef>
 	<para>The <acronym>IP</acronym> protocol version 4, which uses 32 bits
 	  for addressing.  This version is still the most widely used, but it
 	  is slowly being replaced with <acronym>IPv6</acronym>.</para>
 	<glossseealso otherterm="ipv6-glossary">
       </glossdef>
     </glossentry>
 
     <glossentry id="ipv6-glossary">
       <glossterm><acronym>IP</acronym> Version 6</glossterm>
       <acronym>IPv6</acronym>
       <glossdef>
 	<para>The new <acronym>IP</acronym> protocol. Invented because the
 	  address space in <acronym>IPv4</acronym> is running out.  Uses 128
 	  bits for addressing.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="io-glossary">
       <glossterm>Input/Output</glossterm>
       <acronym>I/O</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="iasl-glossary">
       <glossterm>Intel&rsquo;s <acronym>ASL</acronym> compiler</glossterm>
       <acronym>IASL</acronym>
       <glossdef>
         <para>Intel&rsquo;s compiler for converting <acronym>ASL</acronym> into
 	  <acronym>AML</acronym>.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="imap-glossary">
       <glossterm>Internet Message Access Protocol</glossterm>
       <acronym>IMAP</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="ipp-glossary">
       <glossterm>Internet Printing Protocol</glossterm>
       <acronym>IPP</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="ip-glossary">
       <glossterm>Internet Protocol</glossterm>
       <acronym>IP</acronym>
       <glossdef>
 	<para>The packet transmitting protocol that is the basic protocol on
 	  the Internet.  Originally developed at the U.S. Department of
 	  Defense and an extremly important part of the <acronym>TCP/IP
 	  </acronym> stack.  Without the Internet Protocol, the Internet
 	  would not have become what it is today.  For more information, see
 	  <ulink url="ftp://ftp.rfc-editor.org/in-notes/rfc791.txt">
 	  RFC 791</ulink>.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="isp-glossary">
       <glossterm>Internet Service Provider</glossterm>
       <acronym>ISP</acronym>
       <glossdef>
 	<para>A company that provides access to the Internet.</para>
       </glossdef>
   </glossdiv>
 
   <glossdiv>
     <title>K</title>
 
     <glossentry id="kame-glossary">
       <glossterm>KAME</glossterm>
       <glossdef>
         <para>Japanese for <quote>turtle</quote>, the term KAME is used
 	  in computing circles to refer to the <ulink
 	  url="http://www.kame.net/">KAME Project</ulink>, who work on
 	  an implementation of <acronym>IPv6</acronym>.</para>
       </glossdef>
     </glossentry>
 
     <glossentry>
       <glossterm>KDC</glossterm>
       <glosssee otherterm="kdc-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>KLD</glossterm>
       <glosssee otherterm="kld-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>KSE</glossterm>
       <glosssee otherterm="kse-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>KVA</glossterm>
       <glosssee otherterm="kva-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>Kbps</glossterm>
       <glosssee otherterm="kbps-glossary">
     </glossentry>
 
     <glossentry id="kld-glossary">
       <glossterm>Kernel &man.ld.1;</glossterm>
       <acronym>KLD</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="kse-glossary">
       <glossterm>Kernel Scheduler Entities</glossterm>
       <acronym>KSE</acronym>
       <glossdef>
 	<para>A kernel-supported threading system.  See the <ulink
 	  url="http://www.FreeBSD.org/kse">project home page</ulink>
 	  for further details.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="kva-glossary">
       <glossterm>Kernel Virtual Address</glossterm>
       <acronym>KVA</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="kdc-glossary">
       <glossterm>Key Distribution Center</glossterm>
       <acronym>KDC</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="kbps-glossary">
       <glossterm>Kilo Bits Per Second</glossterm>
       <acronym>Kbps</acronym>
       <glossdef>
 	<para>Used to measure bandwith (how much data can pass a given
 	  point at a specified amount of time).  Alternates to the Kilo
 	  prefix include Mega, Giga, Tera, and so forth.</para>
       </glossdef>
     </glossentry>
   </glossdiv>
 
   <glossdiv>
     <title>L</title>
 
     <glossentry>
       <glossterm>LAN</glossterm>
       <glosssee otherterm="lan-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>LOR</glossterm>
       <glosssee otherterm="lor-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>LPD</glossterm>
       <glosssee otherterm="lpd-glossary">
     </glossentry>
 
     <glossentry id="lpd-glossary">
       <glossterm>Line Printer Daemon</glossterm>
       <acronym>LPD</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="lan-glossary">
       <glossterm>Local Area Network</glossterm>
       <acronym>LAN</acronym>
       <glossdef>
 	<para>A network used on a local area, e.g. office, home, or so forth.
 	  </para>
       </glossdef>
     </glossentry>
 
     <glossentry id="lor-glossary">
       <glossterm>Lock Order Reversal</glossterm>
       <acronym>LOR</acronym>
       <glossdef>
 	<para>The &os; kernel uses a number of resource locks to
 	  arbitrate contention for those resources.  A run-time
 	  lock diagnostic system found in &os.current; kernels
 	  (but removed for releases), called &man.witness.4;,
 	  detects the potential for deadlocks due to locking errors.
 	  (&man.witness.4; is actually slightly conservative, so
 	  it is possible to get false positives.)  A true positive
 	  report indicates that <quote>if you were unlucky, a deadlock would
 	  have happened here</quote>.</para>
 
 	<para>True positive LORs tend to get fixed quickly, so
 	  check &a.current.url; and the
 	  <ulink url="http://sources.zabbadoz.net/freebsd/lor.html">
 	  LORs Seen</ulink> page before posting to the mailing lists.</para>
       </glossdef>
     </glossentry>
   </glossdiv>
 
   <glossdiv>
     <title>M</title>
 
     <glossentry>
       <glossterm>MAC</glossterm>
       <glosssee otherterm="mac-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>MADT</glossterm>
       <glosssee otherterm="madt-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>MFC</glossterm>
       <glosssee otherterm="mfc-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>MFP4</glossterm>
       <glosssee otherterm="mfp4-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>MFS</glossterm>
       <glosssee otherterm="mfs-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>MIT</glossterm>
       <glosssee otherterm="mit-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>MLS</glossterm>
       <glosssee otherterm="mls-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>MOTD</glossterm>
       <glosssee otherterm="motd-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>MTA</glossterm>
       <glosssee otherterm="mta-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>MUA</glossterm>
       <glosssee otherterm="mua-glossary">
     </glossentry>
 
     <glossentry id="mta-glossary">
       <glossterm>Mail Transfer Agent</glossterm>
       <acronym>MTA</acronym>
       <glossdef>
 	<para>An application used to transfer email.  An
 	  <acronym>MTA</acronym> has traditionally been part of the BSD
 	  base system.  Today Sendmail is included in the base system, but
 	  there are many other <acronym>MTAs</acronym>, such as postfix,
 	  qmail and Exim.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="mua-glossary">
       <glossterm>Mail User Agent</glossterm>
       <acronym>MUA</acronym>
       <glossdef>
 	<para>An application used by users to display and write email.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="mac-glossary">
       <glossterm>Mandatory Access Control</glossterm>
       <acronym>MAC</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="mit-glossary">
       <glossterm>Massachusetts Institute of Technology</glossterm>
       <acronym>MIT</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="mfc-glossary">
       <glossterm>Merge From Current</glossterm>
       <acronym>MFC</acronym>
       <glossdef subject="FreeBSD">
-	<para>To merge functionality or a patch from the -CURRENT
-	  branch to another, most often -STABLE.</para>
+	<para>MFC ¬O¤@­ÓÁY¼g¡A¥¦¥Nªí¤F <quote>Merged From -CURRENT</quote>
+	 ¡A³o¦r²´·|¦b CVS logs ¤¤±`¨£¡A
+	  ¥Hªí¥Ü³o¬O±q -CURRENT ¤¤¾ã¦X¶i¨ä¥L¤À¤ä(³q±`¬O -STABLE)ªº patch ©Î¥\¯à¡C</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="mfp4-glossary">
       <glossterm>Merge From Perforce</glossterm>
       <acronym>MFP4</acronym>
       <glossdef subject="FreeBSD">
 	<para>To merge functionality or a patch from the Perforce
 	  repository to the -CURRENT branch.</para>
 	<glossseealso otherterm="perforce-glossary">
       </glossdef>
     </glossentry>
 
     <glossentry id="mfs-glossary">
       <glossterm>Merge From Stable</glossterm>
       <acronym>MFS</acronym>
       <glossdef subject="FreeBSD">
 	<para>In the normal course of FreeBSD development, a change will
 	  be committed to the -CURRENT branch for testing before being
 	  merged to -STABLE.  On rare occasions, a change will go into
 	  -STABLE first and then be merged to -CURRENT.</para>
 
 	<para>This term is also used when a patch is merged from -STABLE
 	  to a security branch.</para>
 	<glossseealso otherterm="mfc-glossary">
       </glossdef>
     </glossentry>
 
     <glossentry id="motd-glossary">
       <glossterm>Message Of The Day</glossterm>
       <acronym>MOTD</acronym>
       <glossdef>
         <para>A message, usually shown on login, often used to
 	  distribute information to users of the system.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="mls-glossary">
       <glossterm>Multi-Level Security</glossterm>
       <acronym>MLS</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="madt-glossary">
       <glossterm>Multiple <acronym>APIC</acronym> Description Table</glossterm>
       <acronym>MADT</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
   </glossdiv>
 
   <glossdiv>
     <title>N</title>
 
     <glossentry>
       <glossterm>NAT</glossterm>
       <glosssee otherterm="nat-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>NDISulator</glossterm>
       <glosssee otherterm="projectevil-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>NFS</glossterm>
       <glosssee otherterm="nfs-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>NTFS</glossterm>
       <glosssee otherterm="ntfs-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>NTP</glossterm>
       <glosssee otherterm="ntp-glossary">
     </glossentry>
 
     <glossentry id="nat-glossary">
       <glossterm>Network Address Translation</glossterm>
       <acronym>NAT</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="nfs-glossary">
       <glossterm>Network File System</glossterm>
       <acronym>NFS</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="ntfs-glossary">
       <glossterm>New Technology File System</glossterm>
       <acronym>NTFS</acronym>
       <glossdef>
         <para>A filesystem developed by Microsoft and available in its
 	  <quote>New Technology</quote> operating systems, such as
 	  &windows2k;, &windowsnt; and &windowsxp;.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="ntp-glossary">
       <glossterm>Network Time Protocol</glossterm>
       <acronym>NTP</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
   </glossdiv>
 
   <glossdiv>
     <title>O</title>
 
     <glossentry>
       <glossterm>OBE</glossterm>
       <glosssee otherterm="obe-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>ODMR</glossterm>
       <glosssee otherterm="odmr-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>OS</glossterm>
       <glosssee otherterm="os-glossary">
     </glossentry>
 
     <glossentry id="odmr-glossary">
       <glossterm>On-Demand Mail Relay</glossterm>
       <acronym>ODMR</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="os-glossary">
       <glossterm>Operating System</glossterm>
       <acronym>OS</acronym>
       <glossdef>
 	<para>A set of programs, libraries and tools that provide access to
 	  the hardware resources of a computer.  Operating systems range
 	  today from simplistic designs that support only one program
 	  running at a time, accessing only one device to fully
 	  multi-user, multi-tasking and multi-process systems that can
 	  serve thousands of users simultaneously, each of them running
 	  dozens of different applications.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="obe-glossary">
       <glossterm>Overtaken By Events</glossterm>
       <acronym>OBE</acronym>
       <glossdef>
 	<para>Indicates a suggested change (such as a Problem Report
 	  or a feature request) which is no longer relevant or
 	  applicable due to such things as later changes to &os;,
 	  changes in networking standards, the affected hardware
 	  having since become obsolete, and so forth.</para>
       </glossdef>
     </glossentry>
   </glossdiv>
 
   <glossdiv>
     <title>P</title>
 
     <glossentry>
       <glossterm>p4</glossterm>
       <glosssee otherterm="perforce-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>PAE</glossterm>
       <glosssee otherterm="pae-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>PAM</glossterm>
       <glosssee otherterm="pam-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>PAP</glossterm>
       <glosssee otherterm="pap-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>PC</glossterm>
       <glosssee otherterm="pc-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>PCNSFD</glossterm>
       <glosssee otherterm="pcnfsd-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>PDF</glossterm>
       <glosssee otherterm="pdf-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>PID</glossterm>
       <glosssee otherterm="pid-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>POLA</glossterm>
       <glosssee otherterm="pola-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>POP</glossterm>
       <glosssee otherterm="pop-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>POP3</glossterm>
       <glosssee otherterm="pop3-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>PPD</glossterm>
       <glosssee otherterm="ppd-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>PPP</glossterm>
       <glosssee otherterm="ppp-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>PPPoA</glossterm>
       <glosssee otherterm="pppoa-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>PPPoE</glossterm>
       <glosssee otherterm="pppoe-glossary">
     </glossentry>
 
     <glossentry id="pppoa-glossary">
       <glossterm><acronym>PPP</acronym> over <acronym>ATM</acronym></glossterm>
       <acronym>PPPoA</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="pppoe-glossary">
       <glossterm><acronym>PPP</acronym> over <acronym>Ethernet</acronym></glossterm>
       <acronym>PPPoE</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry>
       <glossterm>PR</glossterm>
       <glosssee otherterm="pr-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>PXE</glossterm>
       <glosssee otherterm="pxe-glossary">
     </glossentry>
 
     <glossentry id="pap-glossary">
       <glossterm>Password Authentication Protocol</glossterm>
       <acronym>PAP</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="perforce-glossary">
       <glossterm>Perforce</glossterm>
       <glossdef>
 	<para>A source code control product made by
 	  <ulink url="http://www.perforce.com/">Perforce Software</ulink>
 	  which is more advanced than CVS.  Although not open source, it use
 	  is free of charge to open-source projects such as &os;.</para>
 
 	<para>Some &os; developers use a Perforce repository as a staging
 	  area for code that is considered too experimental for the
 	  -CURRENT branch.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="pc-glossary">
       <glossterm>Personal Computer</glossterm>
       <acronym>PC</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="pcnfsd-glossary">
       <glossterm>Personal Computer Network File System Daemon</glossterm>
       <acronym>PCNFSD</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="pae-glossary">
       <glossterm>Physical Address Extensions</glossterm>
       <acronym>PAE</acronym>
       <glossdef>
         <para>A method of enabling access to up to 64 GB of <acronym>RAM</acronym> on
 	  systems which only physically have a 32-bit wide address space
 	  (and would therefore be limited to 4 GB without PAE).</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="pam-glossary">
       <glossterm>Pluggable Authentication Modules</glossterm>
       <acronym>PAM</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="ppp-glossary">
       <glossterm>Point-to-Point Protocol</glossterm>
       <acronym>PPP</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="pointyhat">
       <glossterm>Pointy Hat</glossterm>
       <glossdef subject="FreeBSD">
 	<para>A mythical piece of headgear, much like a
 	  <literal>dunce cap</literal>, awarded to any &os;
 	  committer who breaks the build, makes revision numbers
 	  go backwards, or creates any other kind of havoc in
 	  the source base.  Any committer worth his or her salt
 	  will soon accumulate a large collection.  The usage is
 	  (almost always?) humorous.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="pdf-glossary">
       <glossterm>Portable Document Format</glossterm>
       <acronym>PDF</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="pop-glossary">
       <glossterm>Post Office Protocol</glossterm>
       <acronym>POP</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="pop3-glossary">
       <glossterm>Post Office Protocol Version 3</glossterm>
       <acronym>POP3</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="ppd-glossary">
       <glossterm>PostScript Printer Description</glossterm>
       <acronym>PPD</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="pxe-glossary">
       <glossterm>Preboot eXecution Environment</glossterm>
       <acronym>PXE</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="pola-glossary">
       <glossterm>Principle Of Least Astonishment</glossterm>
       <acronym>POLA</acronym>
       <glossdef>
-	<para>As &os; evolves, changes visible to the user should be
-	  kept as unsurprising as possible.  For example, arbitrarily
-	  rearranging system startup variables in
-	  <filename>/etc/defaults/rc.conf</filename> violates
-	  <acronym>POLA</acronym>.  Developers consider
-	  <acronym>POLA</acronym> when contemplating user-visible
-	  system changes.</para>
+	<para>¦b &os; ªºµo®i¹Lµ{¤¤¡A¥ô¦óªº§ïÅÜ´T«×¡A³£¤£¸ÓÅý¨Ï¥ÎªÌ²ßºD·P¨ì¤£¾A¡C
+	  Á|¨Ò¨Ó»¡¡G­Y¥ô·N½Õ°Ê <filename>/etc/defaults/rc.conf</filename> ¤¤ªº¨t²Î±Ò°Ê¶¶§Ç¡A
+	  ´N¬O¹H­I <acronym>POLA</acronym> ­ì«hªººë¯«¡C¥ô¦ó¶}µo¤H­û¡A³£¸Ó¦b°µ¥X­«¤j§ïÅÜ«e¡A
+	  ¥ý¤T«ä¬O§_·|»P <acronym>POLA</acronym> ­ì«h¦³©Ò¹H­I¡C</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="pr-glossary">
       <glossterm>Problem Report</glossterm>
       <acronym>PR</acronym>
       <glossdef>
         <para>A description of some kind of problem that has been
 	  found in either the &os; source or documentation.  See
 	  <ulink url="&url.articles.problem-reports;/index.html">
 	  Writing &os; Problem Reports</ulink>.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="pid-glossary">
       <glossterm>Process ID</glossterm>
       <acronym>PID</acronym>
       <glossdef>
         <para>A number, unique to a particular process on a system,
 	  which identifies it and allows actions to be taken against it.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="projectevil-glossary">
       <glossterm>Project Evil</glossterm>
       <glossdef subject="FreeBSD">
 	<para>The working title for the <acronym>NDISulator</acronym>,
 	  written by Bill Paul, who named it referring to how awful
 	  it is (from a philosophical standpoint) to need to have
 	  something like this in the first place.  The
 	  <acronym>NDISulator</acronym> is a special compatibility
 	  module to allow Microsoft Windows&trade; NDIS miniport
 	  network drivers to be used with &os;/i386.  This is usually
 	  the only way to use cards where the driver is closed-source.
 	  See <filename>src/sys/compat/ndis/subr_ndis.c</filename>.</para>
       </glossdef>
     </glossentry>
   </glossdiv>
 
   <glossdiv>
     <title>R</title>
 
     <glossentry>
       <glossterm>RA</glossterm>
       <glosssee otherterm="ra-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>RAID</glossterm>
       <glosssee otherterm="raid-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>RAM</glossterm>
       <glosssee otherterm="ram-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>RD</glossterm>
       <glosssee otherterm="rd-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>RFC</glossterm>
       <glosssee otherterm="rfc-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>RISC</glossterm>
       <glosssee otherterm="risc-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>RPC</glossterm>
       <glosssee otherterm="rpc-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>RS232C</glossterm>
       <glosssee otherterm="rs232c-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>RTS</glossterm>
       <glosssee otherterm="rts-glossary">
     </glossentry>
 
     <glossentry id="ram-glossary">
       <glossterm>Random Access Memory</glossterm>
       <acronym>RAM</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="rd-glossary">
       <glossterm>Received Data</glossterm>
       <acronym>RD</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="rs232c-glossary">
       <glossterm>Recommended Standard 232C</glossterm>
       <acronym>RS232C</acronym>
       <glossdef>
         <para>A standard for communications between serial devices.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="risc-glossary">
       <glossterm>Reduced Instruction Set Computer</glossterm>
       <acronym>RISC</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="raid-glossary">
       <glossterm>Redundant Array of Inexpensive Disks</glossterm>
       <acronym>RAID</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="rpc-glossary">
       <glossterm>Remote Procedure Call</glossterm>
       <acronym>RPC</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
     
     <glossentry>
       <glossterm>repocopy</glossterm>
       <glosssee otherterm="repocopy-glossary">
     </glossentry>
 
     <glossentry id="repocopy-glossary">
       <glossterm>Repository Copy</glossterm>
       <glossdef>
-	<para>A direct copying of files within the CVS repository.</para>
-
-	<para>Without a repocopy, if a file needed to be copied or
-	  moved to another place in the repository, the committer would
-	  run <command>cvs add</command> to put the file in its new
-	  location, and then <command>cvs rm</command> on the old file
-	  if the old copy was being removed.</para>
-
-	<para>The disadvantage of this method is that the history
-	  (i.e. the entries in the CVS logs) of the file would not be
-	  copied to the new location. As the &os; Project considers
-	  this history very useful, a repository copy is often used
-	  instead. This is a process where one of the repository meisters
-	  will copy the files directly within the repository, rather than
-	  using the &man.cvs.1; program.</para>
+	<para>repocopy(<quote>repository copy</quote> ªºÁY¼g)
+	  ´N¬Oª½±µ±q CVS repository ¤¤½Æ»sÀɮסC</para>
+
+	<para>­Y¤£¥Î repocopy ªº¤è¦¡¡A¨º»ò­Y­n¦b repository ¤º½Æ»s¡B²¾°ÊÀɮתº¸Ü¡A
+	  committer ´N¥²¶·°õ¦æ <command>cvs add</command> ¨Ó§âÀɮשñ¨ì·s¦ì¸m¡A
+	  ¨Ã¥BÁÙ­n°õ¦æ <command>cvs rm</command> ¨Ó§R°£ÂÂÀÉ¡C</para>
+
+	<para>­è­èÁ¿ªº³oºØ¤è¦¡ªº¯ÊÂI¦b©ó¡A¸ÓÀɪº¤§«e¬ÛÃö¬ö¿ý
+	  (¤ñ¦p¦b CVS logs ¤¤ªº¬ÛÃö¶µ¥Ø)¨Ã¤£·|ÀH¤§¦Ó½Æ»s¨ì·s¦a¤è¥h¡C
+	  ¦Ó &os; ­p¹º¤¤»{¬°³o¨Ç¾ú¥v°O¿ý³£¬O¬Û·í¦³¥Îªº¡A
+	  ©Ò¥H·|¸g±`±Ä¥Î repository copy ªº¤è¦¡¡C
+	  ³o¤]´N¬O¬°¦ó repository ºÞ²z­û·|ª½±µ¦b repository ¤º½Æ»sÀɮתº¤è¦¡¡A
+	  ¦Ó«D±Ä¨ú &man.cvs.1; µ{¦¡¨Ó¶i¦æ <command>cvs add</command>¡B
+	  <command>cvs rm</command>¤§Ãþªº°Ê§@¡C</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="rfc-glossary">
       <glossterm>Request For Comments</glossterm>
       <acronym>RFC</acronym>
       <glossdef>
 	<para>A set of documents defining Internet standards, protocols, and
 	  so forth.  See
 	  <ulink url="http://www.rfc-editor.org/">www.rfc-editor.org</ulink>.
 	  <para>
 	  
 	<para>Also used as a general term when someone has a suggested change
 	  and wants feedback.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="rts-glossary">
       <glossterm>Request To Send</glossterm>
       <acronym>RTS</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="ra-glossary">
       <glossterm>Router Advertisement</glossterm>
       <acronym>RA</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
   </glossdiv>
 
   <glossdiv>
     <title>S</title>
 
     <glossentry>
       <glossterm>SCI</glossterm>
       <glosssee otherterm="sci-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>SCSI</glossterm>
       <glosssee otherterm="scsi-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>SG</glossterm>
       <glosssee otherterm="sg-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>SMB</glossterm>
       <glosssee otherterm="smb-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>SMP</glossterm>
       <glosssee otherterm="smp-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>SMTP</glossterm>
       <glosssee otherterm="smtp-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>SMTP AUTH</glossterm>
       <glosssee otherterm="smtpauth-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>SSH</glossterm>
       <glosssee otherterm="ssh-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>STR</glossterm>
       <glosssee otherterm="str-glossary">
     </glossentry>
 
     <glossentry id="smtpauth-glossary">
       <glossterm><acronym>SMTP</acronym> Authentication</glossterm>
       <acronym>SMTP AUTH</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="smb-glossary">
       <glossterm>Server Message Block</glossterm>
       <acronym>SMB</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="sg-glossary">
       <glossterm>Signal Ground</glossterm>
       <acronym>SG</acronym>
       <glossdef>
         <para>An RS232 pin or wire that is the ground reference
           for the signal.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="smtp-glossary">
       <glossterm>Simple Mail Transfer Protocol</glossterm>
       <acronym>SMTP</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="ssh-glossary">
       <glossterm>Secure Shell</glossterm>
       <acronym>SSH</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="scsi-glossary">
       <glossterm>Small Computer System Interface</glossterm>
       <acronym>SCSI</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="str-glossary">
       <glossterm>Suspend To <acronym>RAM</acronym></glossterm>
       <acronym>STR</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="smp-glossary">
       <glossterm>Symmetric MultiProcessor</glossterm>
       <acronym>SMP</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="sci-glossary">
       <glossterm>System Control Interrupt</glossterm>
       <acronym>SCI</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
   </glossdiv>
 
   <glossdiv>
     <title>T</title>
 
     <glossentry>
       <glossterm>TCP</glossterm>
       <glosssee otherterm="tcp-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>TCP/IP</glossterm>
       <glosssee otherterm="tcpip-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>TD</glossterm>
       <glosssee otherterm="td-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>TFTP</glossterm>
       <glosssee otherterm="tftp-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>TGT</glossterm>
       <glosssee otherterm="tgt-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>TSC</glossterm>
       <glosssee otherterm="tsc-glossary">
     </glossentry>
 
     <glossentry id="tgt-glossary">
       <glossterm>Ticket-Granting Ticket</glossterm>
       <acronym>TGT</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="tsc-glossary">
       <glossterm>Time Stamp Counter</glossterm>
       <acronym>TSC</acronym>
       <!-- From dg@, 20040814125503.GF40460@nexus.dglawrence.com -->
       <glossdef>
 	<para>A profiling counter internal to modern &pentium; processors
 	  that counts core frequency clock ticks.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="tcp-glossary">
       <glossterm>Transmission Control Protocol</glossterm>
       <acronym>TCP</acronym>
       <glossdef>
         <para>A protocol that sits on top of (e.g.) the <acronym>IP</acronym>
 	  protocol and guarantees that packets are delivered in a reliable,
 	  ordered, fashion.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="tcpip-glossary">
       <glossterm>Transmission Control Protocol/Internet Protocol</glossterm>
       <acronym>TCP/IP</acronym>
       <glossdef>
         <para>The term for the combination of the <acronym>TCP</acronym>
 	  protocol running over the <acronym>IP</acronym> protocol.  Much of
 	  the Internet runs over <acronym>TCP/IP</acronym>.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="td-glossary">
       <glossterm>Transmitted Data</glossterm>
       <acronym>TD</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="tftp-glossary">
       <glossterm>Trivial <acronym>FTP</acronym></glossterm>
       <acronym>TFTP</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
   </glossdiv>
 
   <glossdiv>
     <title>U</title>
 
     <glossentry>
       <glossterm>UDP</glossterm>
       <glosssee otherterm="udp-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>UFS1</glossterm>
       <glosssee otherterm="ufs1-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>UFS2</glossterm>
       <glosssee otherterm="ufs2-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>UID</glossterm>
       <glosssee otherterm="uid-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>URL</glossterm>
       <glosssee otherterm="url-glossary">
     </glossentry>
 
     <glossentry>
       <glossterm>USB</glossterm>
       <glosssee otherterm="usb-glossary">
     </glossentry>
 
     <glossentry id="url-glossary">
       <glossterm>Uniform Resource Locator</glossterm>
       <acronym>URL</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="ufs1-glossary">
       <glossterm>Unix File System Version 1</glossterm>
       <acronym>UFS1</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="ufs2-glossary">
       <glossterm>Unix File System Version 2</glossterm>
       <acronym>UFS2</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="usb-glossary">
       <glossterm>Universal Serial Bus</glossterm>
       <acronym>USB</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
 
     <glossentry id="uid-glossary">
       <glossterm>User ID</glossterm>
       <acronym>UID</acronym>
       <glossdef>
         <para>A unique number assigned to each user of a computer,
 	  by which the resources and permissions assigned to that
 	  user can be identified.</para>
       </glossdef>
     </glossentry>
 
     <glossentry id="udp-glossary">
       <glossterm>User Datagram Protocol</glossterm>
       <acronym>UDP</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
   </glossdiv>
 
   <glossdiv>
     <title>V</title>
 
     <glossentry>
       <glossterm>VPN</glossterm>
       <glosssee otherterm="vpn-glossary">
     </glossentry>
 
     <glossentry id="vpn-glossary">
       <glossterm>Virtual Private Network</glossterm>
       <acronym>VPN</acronym>
       <glossdef>
         <para></para>
       </glossdef>
     </glossentry>
   </glossdiv>
 </glossary>