diff --git a/mn_MN.UTF-8/books/handbook/cutting-edge/chapter.xml b/mn_MN.UTF-8/books/handbook/cutting-edge/chapter.xml
index 61446d6846..4b9b537a3e 100644
--- a/mn_MN.UTF-8/books/handbook/cutting-edge/chapter.xml
+++ b/mn_MN.UTF-8/books/handbook/cutting-edge/chapter.xml
@@ -1,3027 +1,2970 @@
 <?xml version="1.0" encoding="utf-8"?>
 <!--
      The FreeBSD Mongolian Documentation Project
 
      Original revision 40608
 
      $FreeBSD$
 -->
 
 <chapter id="updating-upgrading">
   <chapterinfo>
     <authorgroup>
       <author>
 	<firstname>Жим</firstname>
 	<surname>Мок</surname>
 	<contrib>Бүтцийг дахин өөрчлөн зохион байгуулж зарим хэсгүүдийг шинэчилсэн </contrib>
       </author>
       <!-- Mar 2000 -->
     </authorgroup>
     <authorgroup>
       <author>
 	<firstname>Жордан</firstname>
 	<surname>Хаббард</surname>
 	<contrib>Анхлан эхийг бичсэн </contrib>
       </author>
       <author>
 	<firstname>Поул-Хэннинг</firstname>
 	<surname>Камп</surname>
       </author>
       <author>
 	<firstname>Жон</firstname>
 	<surname>Полстра</surname>
       </author>
       <author>
 	<firstname>Ник</firstname>
 	<surname>Клэйтон</surname>
       </author>
     </authorgroup>
     <!-- with feedback from various others -->
     <authorgroup>
       <author>
 	<firstname>Цагаанхүүгийн</firstname>
 	<surname>Ганболд</surname>
 	<contrib>Орчуулсан  </contrib>
  	<!-- Nov 2006 -->
       </author>
     </authorgroup>
   </chapterinfo>
 
   <title>&os;-г шинэчилж сайжруулах нь</title>
 
   <sect1 id="updating-upgrading-synopsis">
     <title>Ерөнхий агуулга</title>
 
     <para>&os; нь өөрийн хувилбаруудын хооронд байнгын хөгжүүлэлтийн доор оршин тогтнож
       байдаг. Зарим хүмүүс албан ёсоор гаргасан хувилбаруудыг ашиглах хүсэлтэй
       байдаг бол зарим хүмүүс хамгийн сүүлийн үеийн хөгжүүлэлтийг дагах сонирхолтой
       байдаг. Гэхдээ албан ёсны хувилбарууд хүртэл аюулгүй байдлын болоод бусад
       чухал засваруудаар шинэчлэгдэж байдаг. Ямар хувилбар ашиглаж байгаагаас үл
       хамаараад &os; нь таны системийг шинэ байлгахад шаардлагатай бүх л хэрэгслүүд
       болон хувилбар хооронд хялбараар шинэчлэх боломжоор хангадаг.
       Энэхүү бүлэг нь хөгжүүлэлтийн системийг дагахыг хүсэх эсвэл гаргасан
       хувилбартай үлдэх эсэхийг шийдэхэд танд туслах болно. Таны системийг шинэчлэхэд
       зориулсан үндсэн хэрэгслүүдийг бас харуулах болно.</para>
 
     <para>Энэ бүлгийг уншсаны дараа, та дараах зүйлсийг мэдэх болно:</para>
 
     <itemizedlist>
       <listitem><para>Систем болон портын цуглуулгыг ямар хэрэгслүүд
 	  ашиглан шинэчилж болох талаар.</para>
       </listitem>
       <listitem><para>
 	  <application>freebsd-update</application>,
 	  <application>Subversion</application>,
 	  <application>CVSup</application>,
 	  <application>CVS</application>, эсвэл
 	  <application>CTM</application> програмуудын тусламжтай өөрийн системийг
 		хэрхэн хамгийн сүүлийн хэлбэрт авчрах талаар.</para>
       </listitem>
 
       <listitem>
 	<para>Суулгагдсан системийн төлвийг мэдэгдэж байгаа сайн хуулбартай
 	  хэрхэн харьцуулах талаар.</para>
       </listitem>
 
       <listitem>
         <para><application>Subversion</application> эсвэл баримтжуулах порт ашиглан өөрийн баримтуудыг
 	  хэрхэн сүүлийн хувилбарт байлгаж байх талаар<!-- and
           <application>Docsnap</application>-->.</para>
       </listitem>
 
       <listitem>
 	<para>&os.stable; болон &os.current; хөгжүүлэлтийн
 	  салбаруудын ялгаа.</para>
       </listitem>
 
       <listitem><para>Бүх үндсэн системийг <command>make buildworld</command>
 	(гэх мэт) ашиглан хэрхэн дахин бүтээж суулгах талаар.</para>
       </listitem>
 
     </itemizedlist>
 
     <para>Энэ бүлгийг уншихаасаа өмнө, та дараах зүйлсийг мэдэх шаардлагатай:</para>
 
     <itemizedlist>
       <listitem><para>Өөрийн сүлжээний холболтыг зөв тохируулах (<xref
       linkend="advanced-networking"/>).</para>
       </listitem>
       <listitem><para>Нэмэлт гуравдагч програм хангамжуудыг
 	хэрхэн суулгахыг мэдэх (<xref linkend="ports"/>).</para></listitem>
     </itemizedlist>
 
     <note>
       <para>Энэ бүлэгт &os;-ийн эхийг авч шинэчлэхийн тулд
 	<command>svn</command> тушаалыг ашиглагдсан. Үүнийг хэрэглэхийн
 	тулд <filename role="package">devel/subversion</filename>
 	гэсэн порт буюу багцыг та суулгах хэрэгтэй.</para>
     </note>
   </sect1>
 
   <sect1 id="updating-upgrading-freebsdupdate">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Том</firstname>
 	  <surname>Рөүдс</surname>
 	  <contrib>Бичсэн </contrib>
 	</author>
       </authorgroup>
       <authorgroup>
 	<author>
 	  <firstname>Колин</firstname>
 	  <surname>Персивал</surname>
 	  <contrib>Тэмдэглэгээ бичсэн </contrib>
 	</author>
       </authorgroup>
     </sect1info>
 
     <title>FreeBSD-ийн шинэчлэлт</title>
 
     <indexterm><primary>Updating and Upgrading</primary></indexterm>
     <indexterm>
       <primary>freebsd-update</primary>
       <see>updating-upgrading</see>
     </indexterm>
 
     <para>Аюулгүй байдлын засваруудыг хийнэ гэдэг компьютерийн програм
       хангамж ялангуяа үйлдлийн системийг арчлалтын чухал хэсгийн нэг юм.
       Удаан хугацааны туршид &os; дээр энэ процесс хялбар биш байлаа.
       Засваруудыг эх код руу хийж кодыг хоёртын хэлбэр рүү дахин бүтээж
       дараа нь хоёртын файлуудыг дахин суулгах шаардлагатай байлаа.</para>
 
     <para>Энэ нь одоо тийм биш болсон бөгөөд &os; нь
       <command>freebsd-update</command> гэгддэг хэрэгслийг агуулдаг.
       Энэ хэрэгсэл нь хоёр тусдаа функцээр хангадаг. Нэгдүгээрт энэ нь
       бүтээлт болон суулгах шаардлагагүйгээр хоёртын аюулгүй байдал болон
       алдааны шинэчлэлтүүдийг &os;-ийн үндсэн системд оруулах боломжийг
       олгодог. Хоёрдугаарт уг хэрэгсэл бага болон том хувилбарын шинэчлэлтүүдийг
       дэмждэг.</para>
 
     <note>
       <para>Аюулгүй байдлын багаар дэмжигдсэн бүх архитектур болон
 	хувилбаруудын хувьд хоёртын шинэчлэлтүүд байдаг. Шинэ хувилбар
 	руу шинэчлэхээс өмнө хүссэн хувилбарт чинь хамаатай чухал мэдээлэл байж
 	болох учир одоогийн хувилбарын зарлалуудыг дахин үзэх хэрэгтэй. Тэдгээр
 	зарлалуудыг дараах холбоосоос үзэж болно:
 	<ulink url="http://www.FreeBSD.org/releases/"></ulink>.</para>
     </note>
 
     <para>Хэрэв <command>crontab</command> нь <command>freebsd-update</command>-ийн
       боломжуудыг хэрэглэж байвал дараах үйлдлийг эхлэхээс өмнө түүнийг болиулах
       хэрэгтэй.</para>
 
     <sect2 id="freebsdupdate-config-file">
       <title>Тохиргооны файл</title>
 
       <para>Процессийг илүү хянах боломжтой болгож зарим хэрэглэгчид
 	<filename>/etc/freebsd-update.conf</filename> анхны тохиргооны
 	файлыг өөрчлөхийг хүсэж болох юм. Тохиргоонууд нь
 	маш сайн баримтжуулагдсан байдаг боловч дараах хэдэн зүйлийг
 	арай илүү тайлбарлах шаардлагатай байж болох юм:</para>
 
       <programlisting># Components of the base system which should be kept updated.
 Components src world kernel</programlisting>
 
       <para>Энэ өгөгдөл нь &os;-ийн аль хэсгийг шинэчлэхийг хянадаг.
 	Анхдагчаар эх код, үндсэн систем бүтнээрээ ба цөмийг шинэчлэх
 	байдаг. Бүрэлдэхүүн хэсгүүд нь суулгах явцад байдагтай адил
 	байдаг бөгөөд жишээ нь <literal>world/games</literal> гэдгийг энд нэмэхэд
 	тоглоомын засваруудыг хийх боломжийг олгоно. <literal>src/bin</literal> гэдгийг
 	ашиглах нь <filename class="directory">src/bin</filename>
 	дахь эх кодыг шинэчлэх боломжийг олгодог.</para>
 
       <para>Хамгийн сайн тохиргоо бол үүнийг анхдагчаар нь үлдээх бөгөөд
 	тусгай зүйлс оруулж үүнийг өөрчилснөөр хэрэглэгчид өөрсдийн шинэчлэхийг
 	хүссэн зүйл болгоноо жагсааж оруулах шаардлагатай болно. Ингэснээр
 	эх код болон хоёртын файлуудын хоорондох уялдаа алдагдаж гамшигт
 	үр дагаварт хүргэж болно.</para>
 
       <programlisting># Paths which start with anything matching an entry in an IgnorePaths
 # statement will be ignored.
 IgnorePaths</programlisting>
 
       <para><filename class="directory">/bin</filename> эсвэл
 	<filename class="directory">/sbin</filename> зэрэг замуудыг
 	нэмж эдгээр тусгай сангуудыг шинэчлэх процессийн явцад
 	оролдохгүй орхиж болно. Энэ тохиргоо нь
 	<command>freebsd-update</command> локал өөрчлөлтүүдийг
 	дарж бичихээс хамгаалахад хэрэглэж болно.</para>
 
       <programlisting># Paths which start with anything matching an entry in an UpdateIfUnmodified
 # statement will only be updated if the contents of the file have not been
 # modified by the user (unless changes are merged; see below).
 UpdateIfUnmodified /etc/ /var/ /root/ /.cshrc /.profile</programlisting>
 
       <para>Заагдсан сангууд дахь тохиргооны файлууд өөрчлөгдөөгүй
 	тохиолдолд шинэчилнэ. Хэрэглэгчийн хийсэн өөрчлөлтүүд эдгээр
 	файлуудын автомат шинэчлэлтийг хүчингүй болгоно.
 	<command>freebsd-update</command>-г нийлүүлэх явцад
 	өөрчлөлтүүдийг хадгалахыг тушаах <literal>KeepModifiedMetadata</literal>
 	гэсэн өөр нэг тохиргоо байдаг.</para>
 
       <programlisting># When upgrading to a new &os; release, files which match MergeChanges
 # will have any local changes merged into the version from the new release.
 MergeChanges /etc/ /var/named/etc/</programlisting>
 
       <para><command>freebsd-update</command>-ийн нийлүүлэхийг оролдох
 	тохиргооны файлуудтай сангуудын жагсаалт. Файл нийлүүлэх процесс нь
 	цөөн тохиргоотой &man.mergemaster.8;-тай төстэй &man.diff.1; засварууд
 	бөгөөд нийлүүлэлтийг эсвэл хүлээн авах юм уу эсвэл засварлагч нээж эсвэл
 	<command>freebsd-update</command> ажиллагаагаа зогсоох болно. Эргэлзэж
 	байвал <filename class="directory">/etc</filename> санг нөөцөлж аваад
 	нийлүүлэлтүүдийг хүлээн авах хэрэгтэй. <command>mergemaster</command> тушаалын
 	талаар дэлгэрэнгүй мэдээллийг <xref linkend="mergemaster"/>-с үзнэ үү.</para>
 
       <programlisting># Directory in which to store downloaded updates and temporary
 # files used by &os; Update.
 # WorkDir /var/db/freebsd-update</programlisting>
 
       <para>Энэ сан нь бүх засварууд болон түр зуурын файлууд байх сан
 	юм. Хэрэглэгч хувилбар шинэчлэлт хийж байвал энэ байрлал нь хамгийн
 	багаар бодоход гигабайт дискийн зайтай байх шаардлагатай.</para>
 
       <programlisting># When upgrading between releases, should the list of Components be
 # read strictly (StrictComponents yes) or merely as a list of components
 # which *might* be installed of which &os; Update should figure out
 # which actually are installed and upgrade those (StrictComponents no)?
 # StrictComponents no</programlisting>
 
       <para><literal>yes</literal> гэж тохируулсан үед
 	<command>freebsd-update</command> нь <literal>Components</literal> буюу
 	бүрэлдэхүүн хэсгүүдийн жагсаалт бүрэн гэж тооцох бөгөөд жагсаалтаас гадна өөрчлөлт
 	хийхийг оролдохгүй. <command>freebsd-update</command> нь
 	<literal>Components</literal>-ийн жагсаалтад хамаарах файл
 	бүрийг шинэчлэхийг оролдох болно.</para>
     </sect2>
 
     <sect2 id="freebsdupdate-security-patches">
       <title>Аюулгүй байдлын засварууд</title>
 
       <para>Аюулгүй байдлын засварууд нь алсын машин дээр хадгалагддаг
 	бөгөөд дараах тушаал ашиглан татан авч суулгаж болно:</para>
 
       <screen>&prompt.root; <userinput>freebsd-update fetch</userinput>
 &prompt.root; <userinput>freebsd-update install</userinput></screen>
 
       <para>Хэрэв цөмийн ямар нэг засвар хийгдсэн бол системийг дахин
 	ачаалах хэрэгтэй. Хэрэв бүгд зөв явагдсан бол систем нь засвар хийгдсэн
 	байх ёстой бөгөөд <command>freebsd-update</command>-ийг
 	&man.cron.8; ажлаас шөнө бүр ажиллуулж болно. Энэ ажлыг хийхэд
 	дараах мөрийг <filename>/etc/crontab</filename>-д хийхэд
 	хангалттай байх болно:</para>
 
       <programlisting>@daily                                  root    freebsd-update cron</programlisting>
 
       <para>Энэ мөр нь өдөр бүр <command>freebsd-update</command> хэрэгслийг
 	ажиллуулахыг зааж байна. Ийм аргаар <option>cron</option>-ий нэмэлт
 	өгөгдлийг ашиглан <command>freebsd-update</command> нь зөвхөн
 	шинэчлэлт байгаа эсэхийг шалгах болно. Хэрэв засварууд байвал тэдгээрийг
 	автоматаар диск рүү татаж авах бөгөөд гэхдээ засваруудыг хийхгүй.
 	<username>root</username> хэрэглэгч рүү захиа илгээгдэх бөгөөд
 	дараа нь тэд гараар суулгаж болох юм.</para>
 
       <para>Хэрэв ямар нэг зүйл буруу болбол <command>freebsd-update</command> нь
 	дараах тушаалаар сүүлийн өөрчлөлтүүдийг буцаах чадвартай байдаг:</para>
 
       <screen>&prompt.root; <userinput>freebsd-update rollback</userinput></screen>
 
       <para>Дууссаны дараа цөм эсвэл цөмийн модулиуд өөрчлөгдсөн бол
 	системийг дахин эхлүүлэх хэрэгтэй. Энэ нь шинэ хоёртын файлуудыг санах
 	ой руу дуудах боломжийг &os;-д олгоно.</para>
 
       <para><command>freebsd-update</command> хэрэгсэл нь автоматаар
 	зөвхөн <filename>GENERIC</filename> цөмийг шинэчилж чаддаг.
 	Хэрэв өөрчлөн тохируулсан цөм ашиглагдаж байвал <command>freebsd-update</command> нь
 	шинэчлэлтийг хийж дууссаны дараа цөмийг дахин бүтээж суулгах шаардлагатай.
 	Гэхдээ <command>freebsd-update</command> нь <filename
 	  class="directory">/boot/GENERIC</filename> (хэрэв байгаа бол)
 	дахь <filename>GENERIC</filename> цөмийг системийн тухайн үеийн (ажиллаж байгаа)
 	цөм биш байсан ч гэсэн олж шинэчилдэг.</para>
 
       <note>
 	<para><filename
 	  class="directory">/boot/GENERIC</filename> дахь
 	  <filename>GENERIC</filename> цөмийн хуулбарыг үргэлж хадгалах нь ер нь зүйтэй
 	  байдаг. Энэ нь төрөл бүрийн асуудлуудыг шинжлэх болон
 	  <xref linkend="freebsdupdate-upgrade"/>-т тайлбарласны дагуу
 	  <command>freebsd-update</command>-г ашиглан
 	  хувилбар шинэчлэлтийг хийхэд ач тустай байх болно.</para>
       </note>
 
       <para><filename>/etc/freebsd-update.conf</filename> дахь анхдагч тохиргоо
 	өөрчлөгдөөгүй л бол <command>freebsd-update</command> шинэчлэгдсэн
 	цөмийн эхийг бусад шинэчлэлттэй цуг суулгах болно. Дараа нь өөрийн өөрчлөн
 	тохируулсан цөмийг дахин бүтээж суулгахдаа энгийн сурсан аргаараа хийж
 	болно.</para>
 
       <note>
 	<para><command>freebsd-update</command>-аар түгээгдсэн шинэчлэлтүүд нь
 	  цөмтэй үргэлж холбоотой байдаггүй. <command>freebsd-update install</command>
 	  тушаалаар цөмийн эх өөрчлөгдөөгүй бол өөрийн өөрчлөн тохируулсан цөмийг дахин
 	  бүтээх шаардлагагүй юм. Гэхдээ <command>freebsd-update</command>
 	  тушаал <filename>/usr/src/sys/conf/newvers.sh</filename> файлыг
 	  үргэлж шинэчлэх болно. Тухайн үеийн нөхөөсийн түвшинг (<command>uname -r</command>
 	  тушаалаас гарсан <literal>-p</literal> дугаараар заагдсан) энэ файлаас
 	  авдаг. Өөр бусад юмс өөрчлөгдөөгүй байсан ч гэсэн өөрийн өөрчлөн тохируулсан
 	  цөмийг дахин бүтээх нь системийн тухайн үеийн нөхөөсийн түвшинг зөв гаргах
 	  боломжийг &man.uname.1;-д олгоно. Энэ нь олон системийг арчилж байгаа үед
 	  ялангуяа ач тустай байдаг бөгөөд ингэснээр тэр системүүд дээр суулгагдсан
 	  шинэчлэлтүүдэд түргэн шуурхай үнэлгээ өгөх боломжийг олгодог.</para>
       </note>
     </sect2>
 
     <sect2 id="freebsdupdate-upgrade">
       <title>Major ба Minor буюу Том ба Бага шинэчлэлтүүд</title>
 
       <para>Энэ процесс нь ихэнх гуравдагч талын прорамуудыг эвдэх
 	хуучин обьект файлууд болон сангуудыг устгах болно.
 	Бүх суулгагдсан портуудыг устгаж дахин суулгах эсвэл
 	<filename role="package">ports-mgmt/portupgrade</filename>
 	хэрэгсэл ашиглан сүүлд нь шинэчлэхийг зөвлөдөг. Дараах тушаалыг
 	ашиглан ихэнх хэрэглэгчид тест бүтээлтийг ажиллуулахыг хүснэ:</para>
 
       <screen>&prompt.root; <userinput>portupgrade -af</userinput></screen>
 
       <para>Энэ нь бүгдийг зөв дахин суулгах баталгаа болох юм.
 	<makevar>BATCH</makevar> орчны хувьсагчийг <literal>yes</literal>
 	гэж тохируулснаар энэ процессийн явцад гарч ирэх хүлээх мөрөнд
 	<literal>yes</literal> гэж хариулан бүтээх процессийн
 	үед оролцох шаардлагыг үгүй болгоно.</para>
 
       <para>Хэрэв өөрчлөн тохируулсан цөм ашиглагдаж байгаа бол шинэчлэх
 	процесс арай илүү ажиллагаатай. <filename>GENERIC</filename> цөмийн
 	хуулбар шаардлагатай бөгөөд <filename
 	  class="directory">/boot/GENERIC</filename>-д байрлуулах
 	шаардлагатай. Хэрэв <filename>GENERIC</filename> цөм системд байхгүй
 	бол үүнийг доор дурдсан аргуудын аль нэгийг ашиглан олж авч болно:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>Хэрэв өөрчлөн тохируулсан цөм зөвхөн нэг удаа бүтээгдсэн бол
 	    <filename class="directory">/boot/kernel.old</filename> дахь
 	    цөм нь <filename>GENERIC</filename> цөм юм. Энэ санг
 	    <filename class="directory">/boot/GENERIC</filename> гэж
 	    өөрчлөхөд л болно.</para>
 	</listitem>
 
 	<listitem>
 	  <para>Машинд физикээр хандах боломжтой гэж тооцвол
 	    <filename>GENERIC</filename> цөмийн хуулбарыг CD-ROM зөөвөрлөгчөөс
 	    суулгаж болно. Өөрийн суулгац дискийг хийж дараах тушаалуудыг
 	    ашиглана:</para>
 
 	  <screen>&prompt.root; <userinput>mount /cdrom</userinput>
 &prompt.root; <userinput>cd /cdrom/<replaceable>X.Y-RELEASE</replaceable>/kernels</userinput>
 &prompt.root; <userinput>./install.sh GENERIC</userinput></screen>
 
 	  <para><filename
 	      class="directory"><replaceable>X.Y-RELEASE</replaceable></filename>-г
 	    өөрийн ашиглаж байгаа хувилбараар солих хэрэгтэй. <filename>GENERIC</filename>
 	    цөм анхдагчаар <filename
 	      class="directory">/boot/GENERIC</filename>-д суулгагдах болно.</para>
 	</listitem>
 
 	<listitem>
 	  <para>Дээр дурдсан бүгдийг хийх боломжгүй бол <filename>GENERIC</filename>
 	    цөмийг эхээс нь дахин бүтээж суулгаж болох юм:</para>
 
 	  <screen>&prompt.root; <userinput>cd /usr/src</userinput>
 &prompt.root; <userinput>env DESTDIR=/boot/GENERIC make kernel</userinput>
 &prompt.root; <userinput>mv /boot/GENERIC/boot/kernel/* /boot/GENERIC</userinput>
 &prompt.root; <userinput>rm -rf /boot/GENERIC/boot</userinput></screen>
 
 	  <para>Энэ цөмийг <command>freebsd-update</command> хэрэгсэлд
 	    <filename>GENERIC</filename> гэж харуулахын тулд <filename>GENERIC</filename>
 	    тохиргооны файлыг ямар ч тохиолдолд өөрчилсөн байх ёсгүй. Бас ямар нэг
 	    тусгай сонголтуудгүйгээр (аль болох хоосон <filename>/etc/make.conf</filename>
 	    файлтайгаар) бүтээгдсэн байх ёстойг зөвлөдөг.</para>
 	</listitem>
       </itemizedlist>
 
       <para>Энэ үед <filename>GENERIC</filename> цөм рүү дахин ачаалах
 	шаардлагагүй юм.</para>
 
       <para>Том ба бага хувилбарын шинэчлэлтүүдийг
 	<command>freebsd-update</command> тушаалд хувилбарын дугаарыг өгч
 	гүйцэтгэж болно, жишээ нь дараах тушаал &os;&nbsp;8.1 руу
 	шинэчилнэ:</para>
 
       <screen>&prompt.root; <userinput>freebsd-update -r 8.1-RELEASE upgrade</userinput></screen>
 
       <para>Тушаал хүлээн авсны дараа <command>freebsd-update</command>
 	системийг шинэчлэхэд шаардлагатай мэдээллийг цуглуулахын тулд
 	тохиргооны файл болон одоогийн системийг шалгана. Ямар бүрэлдэхүүн
 	хэсгүүд илрүүлэгдсэн болон ямар бүрэлдэхүүн хэсгүүд илрүүлэгдээгүй
 	гэдгийг дэлгэц дээр үзүүлнэ. Жишээ нь:</para>
 
       <screen>Looking up update.FreeBSD.org mirrors... 1 mirrors found.
 Fetching metadata signature for 8.1-RELEASE from update1.FreeBSD.org... done.
 Fetching metadata index... done.
 Inspecting system... done.
 
 The following components of FreeBSD seem to be installed:
 kernel/smp src/base src/bin src/contrib src/crypto src/etc src/games
 src/gnu src/include src/krb5 src/lib src/libexec src/release src/rescue
 src/sbin src/secure src/share src/sys src/tools src/ubin src/usbin
 world/base world/info world/lib32 world/manpages
 
 The following components of FreeBSD do not seem to be installed:
 kernel/generic world/catpages world/dict world/doc world/games
 world/proflibs
 
 Does this look reasonable (y/n)? y</screen>
 
       <para>Энд хүрэхэд <command>freebsd-update</command> шинэчлэлтэд
 	шаардлагатай бүх файлуудыг татан авахаар оролдох болно. Зарим
 	тохиолдолд хэрэглэгчээс юу суулгах эсвэл хэрхэн цааш үргэлжлүүлэх
 	талаар асуултууд асууж болох юм.</para>
 
       <para>Өөрчлөн тохируулсан цөмийг ашиглаж байх үед дээрх алхам
 	дараахтай төстэй анхааруулгыг харуулах болно:</para>
 
       <screen>WARNING: This system is running a "<replaceable>MYKERNEL</replaceable>" kernel, which is not a
 kernel configuration distributed as part of FreeBSD 8.0-RELEASE.
 This kernel will not be updated: you MUST update the kernel manually
 before running "/usr/sbin/freebsd-update install"</screen>
 
       <para>Энэ анхааруулгыг энэ үед орхигдуулахад аюулгүй байдаг. Шинэчлэгдсэн
 	<filename>GENERIC</filename> цөм шинэчлэлтийн явцад завсрын алхам
 	болон ашиглагдах болно.</para>
 
       <para>Бүх засварууд локал систем рүү татагдсаны дараа тэдгээрийг
 	хийж өгөх болно. Машины хурд болон ачааллаас хамаарч энэ процесс нь
 	хугацаа шаардаж болох юм. Тохиргооны файлуудыг нийлүүлэх болно.
 	Файл нийлүүлэгдэх юм уу эсвэл гараар нийлүүлэхэд зориулж засварлагч
 	дэлгэц дээр гарч ирч болох учир процессийн энэ хэсэг хэрэглэгчийн
 	оролцоо шаардана. Амжилттай нийлүүлэлт болгоны үр дүн хэрэглэгчид
 	харуулагдаж процесс үргэлжлэх болно. Амжилтгүй болсон эсвэл орхигдсон
 	нийлүүлэлт нь процессийг зогсоох болно. Хэрэглэгчид нь
 	<filename class="directory">/etc</filename> сангийн нөөцийг
 	хийж  <filename>master.passwd</filename> эсвэл
 	<filename>group</filename> зэрэг чухал файлуудыг гараар сүүлд нь
 	нийлүүлэхийг хүсэж болох юм.</para>
 
       <note>
 	<para>Систем нь өөрчлөгдөөгүй байгаа бөгөөд бүх засвар оруулалт
 	  болон нийлүүлэлт өөр сан дотор болж байгаа болно. Бүх засварууд
 	  амжилттай хийгдэж бүх тохиргооны файлууд нийлүүлэгдэж процесс
 	  тэгш явагдаж байгаа мэт санагдвал хэрэглэгч өөрчлөлтүүдийг хийх
 	  хэрэгтэй.</para>
       </note>
 
       <para>Энэ процесс дууссаны дараа шинэчлэлтийг дараах тушаалыг ашиглан
 	диск рүү хийж болно.</para>
 
       <screen>&prompt.root; <userinput>freebsd-update install</userinput></screen>
 
       <para>Цөм болон цөмийн модулиудад эхлээд засвар хийнэ. Энэ үед
 	машиныг дахих ачаалах ёстой. Хэрэв систем өөрчлөн тохируулсан цөмөөр
 	ажиллаж байгаа бол цөмийг <filename
 	  class="directory">/boot/GENERIC</filename> (шинэчлэгдсэн)
 	цөмөөр дараа нь ачаалахаар болгохын тулд &man.nextboot.8;-ийг
 	ашиглана:</para>
 
       <screen>&prompt.root; <userinput>nextboot -k GENERIC</userinput></screen>
 
       <warning>
 	<para><filename>GENERIC</filename> цөмөөр ачаалахаас өмнө (хэрэв шинэчлэгдэж
 	  байгаа машинд алсаас хандаж байгаа бол сүлжээнд холбогдон) таны систем зөв ачаалахын
 	  тулд шаардлагатай бүх драйверуудыг агуулсан эсэхийг шалгах хэрэгтэй. Ялангуяа
 	  хэрэв өмнө нь ажиллаж байсан өөрчлөн тохируулсан цөм ерөнхийдөө цөмийн модулиудаар
 	  хангагдаж байдаг ажиллагааг өөртөө агуулсан бол <filename>/boot/loader.conf</filename>
 	  боломжийг ашиглан эдгээр модулиудыг <filename>GENERIC</filename> цөмд түр зуур
 	  ачаалахаа мартуузай. Шинэчлэх процесс бүрэн дуустал шаардлагагүй үйлчилгээнүүд, диск
 	  болон сүлжээний холболтууд гэх мэтийг та бас хааж өгч болох юм.</para>
       </warning>
 
       <para>Одоо машин шинэчлэгдсэн цөмөөр ачаалагдах ёстой:</para>
 
       <screen>&prompt.root; <userinput>shutdown -r now</userinput></screen>
 
       <para>Систем буцаж ассаны дараа <command>freebsd-update</command>-г
 	дахин эхлүүлэх хэрэгтэй. Процессийн төлөв хадгалагдсан болохоор
 	<command>freebsd-update</command> эхнээсээ эхлэхгүй бөгөөд бүх
 	хуучин хуваалцсан сангууд болон обьект файлуудыг устгах болно.
 	Энэ шатыг үргэлжлүүлэхийн тулд дараах тушаалыг ажиллуулна:</para>
 
       <screen>&prompt.root; <userinput>freebsd-update install</userinput></screen>
 
       <note>
 	<para>Сангуудын хувилбарын тоо дээшилсэн эсэхээс хамаарч
 	  суулгах гурван шатны оронд хоёр шат байж болох юм.</para>
       </note>
 
       <para>Бүх гуравдагч талын програм хангамжийг дахин бүтээж дахин суулгах
 	хэрэгтэй. Суулгагдсан програм хангамж нь шинэчлэлтийн процессийн явцад
 	устгагдсан сангуудаас хамаарч болох учраас энэ нь шаардлагатай юм.
 	<filename role="package">ports-mgmt/portupgrade</filename> тушаалыг
 	үүнийг автоматжуулахад ашиглаж болох юм. Энэ процессийг эхлүүлэхийн
 	тулд дараах тушаалыг хэрэглэж болно:</para>
 
       <screen>&prompt.root; <userinput>portupgrade -f ruby</userinput>
 &prompt.root; <userinput>rm /var/db/pkg/pkgdb.db</userinput>
 &prompt.root; <userinput>portupgrade -f ruby18-bdb</userinput>
 &prompt.root; <userinput>rm /var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db</userinput>
 &prompt.root; <userinput>portupgrade -af</userinput></screen>
 
       <para>Үүнийг дууссаны дараа шинэчлэлтийн процессийг
 	<command>freebsd-update</command>-ийг сүүлийн удаа дуудаж
 	төгсгөнө. Шинэчлэлтийн процессийн сул байгаа бүх зүйлсийг гүйцээхийн
 	тулд дараах тушаалыг ажиллуулна:</para>
 
       <screen>&prompt.root; <userinput>freebsd-update install</userinput></screen>
 
       <para>Хэрэв <filename>GENERIC</filename> цөм түр зуур ашиглагдаж байсан
 	бол өөрчлөн тохируулсан шинэ цөмийг ердийн хэвшсэн аргаар одоо бүтээж суулгах цаг
 	болжээ.</para>
 
       <para>Машинаа &os;-ийн шинэ хувилбар руу дахин ачаалах хэрэгтэй.
 	Процесс дууслаа.</para>
     </sect2>
 
     <sect2 id="freebsdupdate-system-comparison">
       <title>Системийн төлвийн харьцуулалт</title>
 
       <para><command>freebsd-update</command> хэрэгслийг
 	&os;-ийн суулгагдсан хувилбарын төлвийг байгаа зөв хуулбарын
 	эсрэг тест хийхэд хэрэглэж болно. Энэ сонголт нь системийн хэрэгслүүд
 	сангууд болон тохиргооны файлуудын одоогийн хувилбаруудыг шалгадаг.
 	Харьцуулалтыг эхлүүлэхийн тулд дараах тушаалыг ажиллуулна:</para>
 
       <screen>&prompt.root; <userinput>freebsd-update IDS &gt;&gt; outfile.ids</userinput></screen>
 
       <warning>
 	<para>Тушаалын нэр <acronym>IDS</acronym> боловч энэ нь
 	  ямар ч тохиолдолд <filename role="package">security/snort</filename> зэрэг
 	  халдлага илрүүлэгч системийг солих зориулалттай биш юм.
 	  <command>freebsd-update</command> нь өгөгдлийг диск дээр
 	  хадгалдаг бөгөөд түүнийг өөрчлөх боломж тодорхой юм.
 	  <varname>kern.securelevel</varname> тохиргоог ашиглах болон
 	  <command>freebsd-update</command>-ийн өгөгдлийг зөвхөн уншигдах файлын
 	  систем дээр ашиглагдаагүй тохиолдолд хадгалах нь энэ боломжийг
 	  багасгах боловч илүү сайн шийдэл нь системийг <acronym>DVD</acronym> эсвэл
 	  нууцлаг хадгалсан гадаад <acronym>USB</acronym> дискийн төхөөрөмж зэрэг
 	  нууцлаг дисктэй харьцуулах явдал юм.</para>
       </warning>
 
       <para>Систем нь одоо шалгагдах бөгөөд файлууд нь өөрсдийн
 	&man.sha256.1; утгуудын хамт, хувилбар дахь мэдэгдэж байгаа сайн утгууд болон
 	одоо суугдсан байгаа утгуудын хамт хэвлэгдэн харуулагдана.
 	Энэ нь яагаад гаралт <filename>outfile.ids</filename> файл руу
 	илгээгдсэн шалтгаан юм. Үүнийг нүдээр шалгахад хэтэрхий хурдан дээш
 	гүйж удалгүй консолын буфферийг дүүргэх болно.</para>
 
       <para>Эдгээр мөрүүд нь бас хэтэрхий урт боловч гаралтын хэлбэрийг
 	хялбараар задлан ялгаж болно. Жишээ нь хувилбарт байгаагаас ондоо
 	бүх файлуудын жагсаалтыг авахын тулд дараах тушаалыг ажиллуулна:</para>
 
 	  <screen>&prompt.root; <userinput>cat outfile.ids | awk '{ print $1 }' | more</userinput>
 /etc/master.passwd
 /etc/motd
 /etc/passwd
 /etc/pf.conf</screen>
 
       <para>Энэ гаралт нь тайрагдсан бөгөөд олон файл байгаа болно.
 	Эдгээр файлуудын зарим нь төрөлхийн өөрчлөлтүүдтэй байна, жишээ нь
 	<filename>/etc/passwd</filename> нь хэрэглэгч системд нэмэгдсэн
 	болохоор өөрчлөгдсөн байна. Зарим тохиолдолд
 	<command>freebsd-update</command> нь шинэчилсэн байж болзошгүй учир
 	цөмийн модулиуд зэрэг бусад файлууд өөр байж болох юм.
 	Тусгай файлууд болон сангуудыг хасахын тулд тэдгээрийг
 	<filename>/etc/freebsd-update.conf</filename> файлын
 	<literal>IDSIgnorePaths</literal> тохиргоонд нэмж өгнө.</para>
 
       <para>Өмнө хэлэлцсэн хувилбараас гадна нарийн нягт шинэчлэлтийн аргын
 	хэсэг болгон энэ системийг ашиглаж болно.</para>
     </sect2>
   </sect1>
 
   <sect1 id="updating-upgrading-portsnap">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Том</firstname>
 	  <surname>Рөүдс</surname>
 	  <contrib>Бичсэн </contrib>
 	</author>
       </authorgroup>
       <authorgroup>
 	<author>
 	  <firstname>Колин</firstname>
 	  <surname>Персивал</surname>
 	  <contrib>Тэмдэглэгээ бичсэн </contrib>
 	</author>
       </authorgroup>
     </sect1info>
     <title>Portsnap: Портын цуглуулгыг шинэчлэх хэрэгсэл</title>
 
     <indexterm><primary>Updating and Upgrading</primary></indexterm>
     <indexterm>
       <primary>Portsnap</primary>
       <see>updating-upgrading</see>
     </indexterm>
 
     <para>&os;-ийн үндсэн систем портын цуглуулгыг бас шинэчилдэг
       &man.portsnap.8; хэрэгслийг агуулдаг. Ажиллуулсны дараа энэ нь
       алсын сайт руу холбогдож нууц түлхүүрийг шалгаж портын цуглуулгын шинэ
       хуулбарыг татан авдаг. Түлхүүр нь бүх татаж авсан файлууд татагдаж байхдаа
       өөрчлөгдөөгүй эсэхийг хянан бүрэн бүтэн байдлыг шалгахад ашиглагддаг.
       Хамгийн сүүлийн үеийн портын цуглуулгыг татаж авахын тулд дараах
       тушаалыг ажиллуулна:</para>
 
     <screen>&prompt.root; <userinput>portsnap fetch</userinput>
 Looking up portsnap.FreeBSD.org mirrors... 9 mirrors found.
 Fetching snapshot tag from geodns-1.portsnap.FreeBSD.org... done.
 Fetching snapshot metadata... done.
 Updating from Tue May 22 02:12:15 CEST 2012 to Wed May 23 16:28:31 CEST 2012.
 Fetching 3 metadata patches.. done.
 Applying metadata patches... done.
 Fetching 3 metadata files... done.
 Fetching 90 patches.....10....20....30....40....50....60....70....80....90. done.
 Applying patches... done.
 Fetching 133 new ports or files... done.</screen>
 
     <para>Энэ жишээ нь юу үзүүлж байна вэ гэхээр &man.portsnap.8;
       одоо байгаа портын өгөгдөлд хэд хэдэн засварууд байгааг олж шалгаж байна.
       Энэ нь бас уг хэрэгсэл өмнө нь ажилласныг харуулж байгаа бөгөөд
       хэрэв эхний удаа ажилласан бол цуглуулга татагдан авагдах байсан
       юм.</para>
 
     <para>&man.portsnap.8; нь <command>fetch</command> үйлдлийг хийж
       дууссаны дараа локал систем дээр байгаа портын цуглуулга болон дараа дараагийн
       засваруудыг шалгалтад дамжуулна. <command>portsnap</command>-ийг эхний удаа ажиллуулахдаа
       <literal>extract</literal>-г ашиглан татан авсан файлуудыг суулгаж болно:</para>
 
     <screen>&prompt.root; <userinput>portsnap extract</userinput>
 /usr/ports/.cvsignore
 /usr/ports/CHANGES
 /usr/ports/COPYRIGHT
 /usr/ports/GIDs
 /usr/ports/KNOBS
 /usr/ports/LEGAL
 /usr/ports/MOVED
 /usr/ports/Makefile
 /usr/ports/Mk/bsd.apache.mk
 /usr/ports/Mk/bsd.autotools.mk
 /usr/ports/Mk/bsd.cmake.mk
 <replaceable>...</replaceable></screen>
 
     <para>Аль хэдийн суулгасан портын цуглуулгыг шинэчлэхдээ
       <command>portsnap update</command> тушаалыг ашиглах ёстой:</para>
 
     <screen>&prompt.root; <userinput>portsnap update</userinput></screen>
 
     <para>Процесс одоо дууссан бөгөөд портын цуглуулыг ашиглан
       програмуудыг суулгаж эсвэл шинэчилж болно.</para>
 
     <para><literal>fetch</literal> болон <literal>extract</literal> эсвэл
       <literal>update</literal> үйлдлүүдийг доор харуулсан шиг дараалуулан
       ажиллуулж болно:</para>
 
     <screen>&prompt.root; <userinput>portsnap fetch update</userinput></screen>
 
     <para>Энэ тушаал нь портын цуглуулгын сүүлийн хувилбарыг
       татан авч таны машин дээр байгаа локал хувилбарыг
       <filename class="directory">/usr/ports</filename> санд
       шинэчилдэг.</para>
   </sect1>
 
   <sect1 id="updating-upgrading-documentation">
     <title>Баримтын цуглуулгыг шинэчлэх нь</title>
 
     <indexterm><primary>Updating and Upgrading</primary></indexterm>
 
     <indexterm>
       <primary>Documentation</primary>
       <see>Updating and Upgrading</see>
     </indexterm>
 
     <para>Үндсэн систем болон портын цуглуулгаас гадна
       баримтууд нь &os; үйлдлийн системийн салшгүй хэсэг юм. Хэдийгээр
       &os;-ийн хамгийн сүүлийн үеийн баримтын цуглуулга <ulink
 	url="http://www.freebsd.org/doc/">&os; вэб сайт</ulink> дээр
       үргэлж байдаг боловч зарим хэрэглэгчид удаан сүлжээний холболттой эсвэл
       бүр тогтмол сүлжээний холболтгүй байж болох юм. Азаар &os;-ийн хамгийн
       сүүлийн үеийн баримтын цуглуулгын локал хуулбарыг арчлан хувилбар бүртэй цуг
       ирдэг баримтыг шинэчлэх хэд хэдэн арга байдаг.</para>
 
     <sect2 id="dsvn-doc">
       <title>Баримтыг шинэчлэхийн тулд <application>Subversion</application>-г ашиглах нь</title>
 
       <para>&os;-ийн 
 	баримтуудын эхийг <application>Subversion</application> 
 	ашиглан авч болно. Энэ хэсэг дараах зүйлсийг 
 	  тайлбарладаг:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>&os;-ийн баримтуудыг эхээс нь бүтээхэд шаардлагатай
 	    хэрэгслүүд, баримтын хэрэгслүүдийг хэрхэн суулгах
 	    талаар.</para>
 	</listitem>
 
 	<listitem>
 	  <para><application>Subversion</application> ашиглан 
 	    <filename class="directory">/usr/doc</filename> дахь 
 	    баримтын эхийн хуулбарыг хэрхэн татаж авах талаар.</para>
 	</listitem>
 
 	<listitem>
 	  <para>&os;-ийн баримтыг эхээс нь хэрхэн бүтээж
 	    <filename class="directory">/usr/share/doc</filename> дотор
 	    суулгах талаар.</para>
 	</listitem>
 
 	<listitem>
 	  <para>Баримтыг бүтээх системийн дэмждэг бүтээлтийн
 	    зарим тохируулгууд, өөрөөр хэлбэл баримтын зарим нэг
 	    хэл дээрх орчуулгыг зөвхөн бүтээдэг тохируулгууд эсвэл
 	    тусгай гаралтын хэлбэржүүлэлтийг сонгодог тохируулгууд.</para>
 	</listitem>
       </itemizedlist>
     </sect2>
 
     <sect2 id="installing-documentation-toolchain">
       <title><application>Subversion</application> болон баримтын хэрэгслүүдийг суулгах нь</title>
 
       <para>&os;-ийн баримтыг эхээс нь бүтээхэд нэлээн олон
 	тооны хэрэгслүүдийг шаарддаг. Эдгээр хэрэгслүүд нь
 	&os;-ийн үндсэн системийн хэсэг биш байдаг. Учир нь эдгээр нь
 	ихээхэн хэмжээний дискийн зай шаарддаг бөгөөд &os;-ийн бүх
 	хэрэглэгчдэд хэрэгтэй байдаггүй. Тэдгээр нь &os;-д зориулж
 	шинэ баримтууд идэвхтэй бичдэг эсвэл өөрсдийн баримтыг
 	эхээс нь байнга шинэчилдэг хэрэглэгчдэд зөвхөн хэрэгтэй
 	байдаг.</para>
 
       <para>Бүх шаардлагатай хэрэгслүүд портын цуглуулгад байдаг.
 	Эдгээр хэрэгслүүдийн эхний суулгалт болон хожмын шинэчлэлтүүдийг
 	хялбаршуулах <filename
 	  role="package">textproc/docproj</filename> порт нь &os;-ийг
 	баримтжуулах төслөөс хөгжүүлсэн мастер порт юм.</para>
 
       <note>
 	<para>&postscript; эсвэл PDF баримт шаардлагагүй үед харин
 	  <filename
 	    role="package">textproc/docproj-nojadetex</filename> портыг
 	  суулгаж болох юм. Баримтын хэрэгслийн энэ хувилбар нь
 	  <application>teTeX</application> тайпсет хөдөлгүүрээс бусад
 	  бүгдийг багтаасан байдаг. <application>teTeX</application> нь
 	  маш олон хэрэгслүүдийн цуглуулга учир PDF гаралт үнэхээр
 	  шаардлагагүй тохиолдолд суулгахгүй байх нь зохимжтой
 	  байдаг.</para>
       </note>
 
       <para><application>Subversion</application> нь 
 	<filename role="package">textproc/docproj</filename> порттой цуг суудаг.</para>
     </sect2>
 
     <sect2 id="updating-documentation-sources">
       <title>Баримтын эхийг шинэчлэх нь</title>
 
       <para><application>Subversion</application> нь 
 	баримтын эхийн цэвэр хуулбарыг татан 
 	авч чаддаг.</para>
 
 	<screen>&prompt.root; <userinput>svn checkout <literal>svn://svn.FreeBSD.org/doc/head</literal> <filename class="directory">/usr/doc</filename></userinput></screen>
 
       <para>Баримтын эхийн эхний таталт хугацаа шаардаж болох юм. Дуустал нь
 	хүлээх хэрэгтэй.</para>
 
       <para>Баримтын эхийн дараа дараагийн шинэчлэлтүүдийг доорх тушаалыг 
 	ашиглан татан авч болно.</para>
 
       <screen>&prompt.root; <userinput>svn update <filename class="directory">/usr/doc</filename></userinput></screen>
 
       <para>Эхийг татан авсныхаа дараа баримтыг шинэчлэх өөр нэг арга нь 
 	<filename
 	  class="directory">/usr/doc</filename> сангийн 
 	<filename>Makefile</filename>-аар дэмжигдсэн байдаг бөгөөд 
 	дараахийг ажиллуулна:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/doc</userinput>
 &prompt.root; <userinput>make update</userinput></screen>
     </sect2>
 
     <sect2 id="updating-documentation-options">
       <title>Баримтын эхийн тааруулж болох тохируулгууд</title>
 
       <para>&os;-ийн баримтжуулалтыг бүтээж шинэчлэх систем нь баримтын
 	зөвхөн тодорхой хэсгийг шинэчлэх эсвэл тусгай орчуулгыг бүтээх
 	процессийг амарчлах хэдэн тохируулгыг дэмждэг. Эдгээр тохируулгуудыг
 	<filename>/etc/make.conf</filename> файлд бүхэл системийн
 	хувьд зааж өгөх юм уу эсвэл &man.make.1; хэрэгсэлд тушаалын
 	мөрийн тохиргоо маягаар зааж өгч болно.</para>
 
       <para>Дараах тохируулгууд нь эдгээрийн зарим нь юм:</para>
 
       <variablelist>
 	<varlistentry>
 	  <term><makevar>DOC_LANG</makevar></term>
 
 	  <listitem>
 	    <para>Бүтээж суулгах хэл ба кодчилолын жагсаалт, жишээ нь
 	      Англи баримтад зөвхөн зориулсан <literal>en_US.ISO8859-1</literal>
 	      байна.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><makevar>FORMATS</makevar></term>
 
 	  <listitem>
 	    <para>Бүтээх ганц хэлбэржүүлэлт эсвэл гаралтын хэлбэржүүлэлтийн
 	      жагсаалт. Одоогоор <literal>html</literal>,
 	      <literal>html-split</literal>, <literal>txt</literal>,
 	      <literal>ps</literal>, <literal>pdf</literal>,
 	      болон <literal>rtf</literal> дэмжигдсэн байгаа.</para>
 	  </listitem>
 	</varlistentry>
 
         <varlistentry>
           <term><makevar>DOCDIR</makevar></term>
 
           <listitem>
             <para>Баримтыг суулгах газар.  Анхдагчаар
               <filename
                 class="directory">/usr/share/doc</filename> байдаг.</para>
           </listitem>
         </varlistentry>
       </variablelist>
 
       <para>&os; дээрх системийн тохируулга болон дэмжигдсэн бүтээлтийн
 	хувьсагчуудын талаар дэлгэрэнгүйг &man.make.conf.5;-с үзнэ үү.</para>
 
       <para>&os;-ийн баримтжуулалт бүтээх системийн дэмждэг бүтээлтийн
 	хувьсагчуудын талаар дэлгэрэнгүйг
 	<ulink url="&url.doc.langbase;/books/fdp-primer">Шинэ хувь нэмэр оруулагчдад
 	  зориулсан &os; баримтжуулах төслийн гарын авлагаас</ulink> үзнэ үү.</para>
     </sect2>
 
     <sect2 id="updating-installed-documentation">
       <title>&os;-ийн баримтуудыг эхээс суулгах нь</title>
 
       <para>Баримтын эхийн хамгийн сүүлийн хормын хувилбарыг
 	<filename class="directory">/usr/doc</filename> санд татаж авснаар
 	суулгагдсан баримтын шинэчлэлтийг хийхэд бүх юм бэлэн болно.</para>
 
       <para><makevar>DOC_LANG</makevar> makefile-ийн тохиргоонд заагдсан
 	бүх хэлний бүрэн шинэчлэлтийг дараахийг бичин хийж болно:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/doc</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
 
       <para>Хэрэв зөвхөн тусгай хэлний шинэчлэлт хэрэгтэй бол
 	<filename class="directory">/usr/doc</filename>-ийн тухайн хэлний
 	тусгай дэд санд &man.make.1;-ийг ажиллуулж болно, жишээ нь:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/doc/en_US.ISO8859-1</userinput>
 &prompt.root; <userinput>make update install clean</userinput></screen>
 
       <para>Суулгах гаралтын хэлбэржүүлэлтийг <makevar>FORMATS</makevar>
 	бүтээлтийн хувьсагчийг зааж өгөн хийж өгч болно,
 	жишээ нь:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/doc</userinput>
 &prompt.root; <userinput>make FORMATS='html html-split' install clean</userinput></screen>
     </sect2>
 
     <sect2 id="doc-ports">
       <sect2info>
 	<authorgroup>
 	  <author>
 	    <firstname>Марк</firstname>
 	    <surname>Фонвил</surname>
 	    <contrib>Хувь нэмэр болгосон </contrib>
 	  </author>
 	</authorgroup>
       </sect2info>
 
       <title>Баримтжуулах портуудыг ашиглах нь</title>
 
       <indexterm><primary>Updating and Upgrading</primary></indexterm>
 
       <indexterm>
 	<primary>documentation package</primary>
 	<see>Updating and Upgrading</see>
       </indexterm>
 
       <para>Өмнөх хэсэгт &os;-ийн баримтжуулалтыг эхээс нь
 	шинэчлэх аргыг бид танилцуулсан. &os;-ийн бүх системүүдийн
 	хувьд эх дээр тулгуурласан шинэчлэлтүүд нь боломжтой эсвэл
 	практикийн биш байж болох юм. Баримтжуулалтын эхүүдийг
 	бүтээх нь нэлээн их хэмжээний хэрэгслийн цуглуулга буюу
 	<emphasis>баримтжуулалт бүтээх хэрэгслийн олонлог</emphasis>,
 	<application>Subversion</application>-ийг тодорхой хэмжээгээр мэдэх, 
 	репозиториос эхийг татаж авах болон татаж авсан эхээ 
 	бүтээх хэд хэдэн шат дарааллуудыг шаарддаг. Энэ хэсэгт 
 	бид &os;-ийн баримтжуулалтын суулгагдсан хуулбаруудыг 
 	шинэчлэх өөр аргыг тайлбарлах болно. Энэ нь портын
 	цуглуулгыг ашиглах бөгөөд дараах боломжийг бүрдүүлнэ:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>Бүгдийг бүтээлгүйгээр баримтжуулалтын урьдчилан
 	    бүтээсэн хормын хувилбарыг татан авч суулгах
 	    (ингэснээр баримтжуулалт бүтээх хэрэгслийн олонлогийг
 	    бүхэлд нь суулгах шаардлагагүй болно).</para>
 	</listitem>
 
 	<listitem>
 	  <para>Баримтжуулалтын эхийг татаж аван портын тогтолцоог
 	    ашиглан бүтээх (татаж аван бүтээх алхмуудыг арай хялбар
 	    болгодог).</para>
 	</listitem>
       </itemizedlist>
 
       <para>&os;-ийн баримтжуулалтыг шинэчлэх эдгээр хоёр арга нь
 	&a.doceng;-ийн сар бүр шинэчилдэг <emphasis>баримтжуулалтын
 	портуудын</emphasis> цуглуулгаар дэмжигддэг. Эдгээр нь
 	&os;-ийн портын цуглуулгад <ulink
 	  url="http://www.freshports.org/docs/">docs</ulink>
 	виртуал төрөлд байдаг.</para>
 
       <sect3 id="doc-ports-install-make">
 	<title>Баримтжуулалтын портуудыг бүтээж суулгах нь</title>
 
 	<para>Баримтжуулалтын портууд нь баримтжуулалтын бүтээлтийг
 	  хялбар болгохын тулд порт бүтээх тогтолцоог хэрэглэдэг.
 	  &man.make.1;-ийг тохирох орчны тохиргоонууд болон тушаалын
 	  мөрийн тохиргоонуудын хамтаар ажиллуулж баримтжуулалтын
 	  эхийг татаж авах процессыг тэд автоматжуулдаг бөгөөд
 	  баримтжуулалтын суулгалт болон устгалтыг &os;-ийн
 	  бусад порт эсвэл багцын суулгалтын нэгэн адил хялбар
 	  болгодог.</para>
 
 	<note>
 	  <para>Мөн баримтжуулалтын портуудыг бүтээсний дараа тэд
 	    хамааралтай <emphasis>баримтжуулалтыг бүтээх хэрэгслийн олонлогийн</emphasis>
 	    портуудыг бүртгэдэг бөгөөд тэдгээрийг автоматаар бас
 	    суулгадаг.</para>
 	</note>
 
 	<para>Баримтжуулалтын портуудын зохион байгуулалт нь
 	  дараах хэлбэрийн байна:</para>
 
 	<itemizedlist>
 	  <listitem>
 	    <para>Баримтжуулалтын портын файлууд байдаг
 	      <filename
 		role="package">misc/freebsd-doc-en</filename>
 	      <quote>мастер порт</quote> байдаг. Энэ нь бүх
 	      баримтжуулалтын портуудын үндэс болдог. Анхдагчаар
 	      энэ нь Англи баримтжуулалтыг зөвхөн бүтээдэг.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para><quote>Нэг портод бүгд багтсан</quote> <filename
 		role="package">misc/freebsd-doc-all</filename> байдаг
 	      бөгөөд энэ нь байгаа бүх хэл дээр бүх баримтжуулалтыг
 	      бүтээж суулгадаг.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>Эцэст нь орчуулга бүрийн хувьд <quote>зарц порт</quote>
 	      байдаг, жишээ нь Унгар хэл дээрх баримтуудад зориулсан
 	      <filename
 		role="package">misc/freebsd-doc-hu</filename>-г дурдаж
 	      болно. Эдгээр нь бүгд мастер портоос хамаарах бөгөөд
 	      тухайн хэлний орчуулсан баримтжуулалтыг суулгадаг.</para>
 	  </listitem>
 	</itemizedlist>
 
 	<para>Баримтжуулалтын портыг эхээс суулгахын тулд дараах
 	  тушаалуудыг ажиллуулна (<username>root</username> эрхээр):</para>
 
 	<screen>&prompt.root; <userinput>cd /usr/ports/misc/freebsd-doc-en</userinput>
 &prompt.root; <userinput>make install clean</userinput></screen>
 
 	<para>Энэ нь Англи баримтжуулалтыг хуваагдсан <acronym>HTML</acronym>
 	  хэлбэрээр (<ulink
 	    url="http://www.FreeBSD.org"></ulink> дээр ашигладагийн адилаар)
 	  бүтээж <filename
 	    class="directory">/usr/local/share/doc/freebsd</filename> санд
 	  суулгадаг.</para>
 
 	<sect4 id="doc-ports-options">
 	  <title>Нийтлэг Knob болон тохируулгууд</title>
 
 	  <para>Баримтжуулалтын портуудын анхдагч байдлыг өөрчлөх
 	    олон тохиргоо байдаг. Доор цөөхөн хэдэн жагсаалтыг
 	    дурдав:</para>
 
 	  <variablelist>
 	    <varlistentry>
 	      <term><makevar>WITH_HTML</makevar></term>
 
 	      <listitem>
 		<para>HTML хэлбэрээр бүтээхийг зөвшөөрдөг: баримт
 		  бүрийн хувьд нэг HTML файл. Хэлбэршүүлсэн
 		  баримтжуулалт нь тохирох <filename>article.html</filename> юм уу
 		  эсвэл <filename>book.html</filename> гэсэн файлуудад зургийн
 		  хамтаар хадгалагддаг.</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term><makevar>WITH_PDF</makevar></term>
 
 	      <listitem>
 		<para>&adobe; &acrobat.reader;,
 		  <application>Ghostscript</application> эсвэл бусад PDF уншигчдыг
 		  ашиглах &adobe;-ийн хөрвөх баримтын хэлбэрээр бүтээхийг
 		  зөвшөөрдөг. Хэлбэршүүлсэн
 		  баримтжуулалт нь тохирох <filename>article.pdf</filename> юм уу
 		  эсвэл <filename>book.pdf</filename> гэсэн файлуудад
 		  хадгалагддаг.</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term><makevar>DOCBASE</makevar></term>
 
 	      <listitem>
 		<para>Баримтжуулалтын суулгах байрлал. Энэ нь
 		  анхдагчаар <filename
 		    class="directory">/usr/local/share/doc/freebsd</filename>
 		  байдаг.</para>
 
 		<note>
 		  <para>Анхдагч суулгах сан нь <application>Subversion</application> 
 		    аргын ашигладаг сангаас ялгаатайг санаарай. 
 		    Энэ нь яагаад гэвэл бид порт суулгаж байгаа 
 		    бөгөөд портууд нь ихэвчлэн <filename
 		      class="directory">/usr/local</filename> санд
 		    суудаг. Үүнийг <makevar>PREFIX</makevar> хувьсагчийг
 		    нэмэн өөрчилж болдог.</para>
 		</note>
 	      </listitem>
 	    </varlistentry>
 	  </variablelist>
 
 	  <para>Энд Унгар баримтжуулалтыг Хөрвөх Баримтын Хэлбэрээр (PDF)
 	    суулгахын тулд дээр дурдсан хувьсагчуудыг хэрхэн
 	    ашиглахыг харуулсан жишээг үзүүлэв:</para>
 
 	  <screen>&prompt.root; cd /usr/ports/misc/freebsd-doc-hu
 &prompt.root; make -DWITH_PDF DOCBASE=share/doc/freebsd/hu install clean</screen>
 	</sect4>
       </sect3>
 
       <sect3 id="doc-ports-install-package">
 	<title>Баримтжуулалтын багцуудыг ашиглах нь</title>
 
 	<para>Өмнөх хэсэгт тайлбарласнаар баримтжуулалтын портуудыг
 	  эхээс бүтээх нь баримтжуулалтыг бүтээх хэрэгслийн
 	  олонлогийг суулгах болон  портуудыг бүтээхэд тодорхой
 	  хэмжээний дискийн зай шаарддаг. Баримтжуулалтын
 	  хэрэгслүүдийг суулгахад эх үүсвэр хүрэлцэхгүй үед эсвэл
 	  эхээс бүтээх нь ихээхэн хэмжээний дискийн зай эзлэх
 	  бол баримтжуулалтын портуудын урьдчилан бүтээсэн
 	  хормын хувилбаруудыг суулгах боломж бас байдаг.</para>
 
 	<para>&a.doceng; нь &os;-ийн баримтжуулалтын багцуудын
 	  сар бүрийн хормын хувилбаруудыг бэлддэг. Эдгээр
 	  хоёртын багцуудыг &man.pkg.add.1;,
 	  &man.pkg.delete.1; гэх зэрэг багцын хэрэгслүүдийн
 	  хамтаар ашиглаж болдог.</para>
 
 	<note>
 	  <para>Хоёртын багцуудыг ашиглаж байгаа үед &os;-ийн
 	    баримтжуулалт нь тухайн хэлний хувьд байгаа
 	    <emphasis>бүх</emphasis> хэлбэрээр суудаг.</para>
 	</note>
 
 	<para>Жишээ нь дараах тушаал Унгар баримтжуулалтын
 	  хамгийн сүүлийн урьдчилан бүтээсэн багцыг суулгах
 	  болно:</para>
 
 	<screen>&prompt.root; <userinput>pkg_add -r hu-freebsd-doc</userinput></screen>
 
 	<note>
 	  <para>Багцууд нь харгалзах портын нэрнээсээ ялгаатай дараах
 	    нэрийн хэлбэртэй байдаг:
 	    <literal><replaceable>lang</replaceable>-freebsd-doc</literal>.
 	    Энд <replaceable>lang</replaceable> нь хэлний кодын богино
 	    хэлбэр юм, жишээ нь <literal>hu</literal> нь Унгар, эсвэл
 	    <literal>zh_cn</literal> нь хялбаршуулсан Хятад хэл юм.</para>
 	</note>
       </sect3>
 
       <sect3 id="doc-ports-update">
 	<title>Баримтжуулалтын портуудыг шинэчлэх нь</title>
 
 	<para>Өмнө нь суулгасан баримтжуулалтын портыг шинэчлэхийн
 	  тулд портууд шинэчлэх аль ч хэрэгсэл байхад хангалттай.
 	  Жишээ нь дараах тушаал суулгасан Унгар баримтжуулалтыг
 	  <filename
 	    role="package">ports-mgmt/portupgrade</filename> хэрэгслийн
 	  тусламжтайгаар зөвхөн багцуудыг ашиглан шинэчилнэ:</para>
 
 	<screen>&prompt.root; <userinput>portupgrade -PP hu-freebsd-doc</userinput></screen>
       </sect3>
     </sect2>
   </sect1>
 
   <sect1 id="current-stable">
     <title>Хөгжүүлэлтийн салбарыг дагах нь</title>
     <indexterm><primary>-CURRENT</primary></indexterm>
     <indexterm><primary>-STABLE</primary></indexterm>
 
     <para>FreeBSD-ийн хоёр хөгжүүлэлтийн салбар байдаг: &os.current; болон
       &os.stable;. Энэ хэсэгт эдгээр тус бүрийг тайлбарлаж өөрийн системийг тус
 	тусын модны хувьд хамгийн шинэ хэлбэрт байнга байлгах талаар тайлбарлах болно.
 	&os.current; эхлээд хэлэлцэгдэх бөгөөд дараа нь &os.stable;-ийн тухай
 	яригдах болно.</para>
 
     <sect2 id="current">
       <title>&os;-ийн одоо үеийн хэлбэрт байх нь</title>
 
       <para>Та үүнийг уншихдаа &os.current; нь &os;-ийн хөгжүүлэлтийн
 	<quote>bleeding edge салбар буюу амжилт ололтын хамгийн тэргүүний
 	салбар</quote> гэдгийг санаарай. &os.current; хэрэглэгчдийг техникийн өндөр
 	чадавхитай бөгөөд системийн хүнд хэцүү асуудлуудыг өөрсдөө шийдвэрлэх
 	чадвартай байна гэж тооцдог. Хэрэв та &os;-д анхлан суралцагч бол
 	үүнийг суулгахаасаа өмнө дахин сайн бодоорой.</para>
 
       <sect3>
 	<title>&os.current; гэж юу вэ?</title>
 	<indexterm><primary>хормын агшны хувилбар</primary></indexterm>
 
 	<para>&os.current; нь &os;-ийн хамгийн сүүлийн үеийн ажлын эх юм.
 	     Энэ нь хийгдэж байгаа ажлууд, туршилтын өөрчлөлтүүд болон програм хангамжийн
 	     дараагийн албан ёсны хувилбарт байхгүй ч байж болох эсвэл байж ч болох
 	     шилжилтийн аргуудыг багтаадаг. &os;-ийн олон хөгжүүлэгчид &os.current;-ийн
 	     эх кодыг өдөр болгон эмхэтгэн хөрвүүлж байдаг боловч эхийг бүтээх боломжгүй үе бас
 	     байдаг. Эдгээр асуудлууд нь боломжийн хэрээр хурдан шийдэгддэг боловч
 	  &os.current; нь сүйрэл авчрах эсвэл тун их хүссэн ажиллагааг авчрах эсэх нь
 	     та яг ямар агшинд эх кодыг татаж авснаас хамаарах юм!</para>
       </sect3>
 
       <sect3>
 	<title>&os.current; хэнд хэрэгтэй вэ?</title>
 
 	<para>&os.current; нь үндсэн 3 сонирхлын бүлэгт зориулагдан
 		хийгдсэн:</para>
 
 	<orderedlist>
 	  <listitem>
 	    <para>Эх модны зарим хэсэг дээр идэвхтэйгээр ажиллаж байгаа &os;-ийн хүрээний
 		гишүүд болон <quote>current буюу одоо үеийн хэлбэрт</quote> байлгах нь
 		туйлын шаардлага болсон хүмүүст.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>&os.current;-г аль болох ухаалаг байлгахыг хичээж асуудлуудыг шийдвэрлэхэд
 		цагаа зарах хүсэлтэй байдаг идэвхтэй тест хийгч &os;-ийн хүрээний гишүүд.
 		Эдгээр хүмүүс нь өөрчлөлтүүд болон  &os;-ийн ерөнхий чиглэлд цаг үеийн
 		саналуудыг тусгахыг хүсэж тэдгээрийг шийдэх засваруудыг илгээдэг бас хүмүүс
 		юм..</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>Юу болж байгааг зөвхөн харж мэдэж байхыг хүссэн эсвэл одоо үеийн эхийг
 		лавлагааны зорилгоор ашиглахыг зөвхөн хүссэн хүмүүс (өөрөөр хэлбэл
 		ажиллуулах биш <emphasis>унших</emphasis> зорилгоор).
 		Эдгээр хүмүүс нь хааяа бас санал гаргаж кодонд хувь нэмэр оруулдаг.</para>
 	  </listitem>
 	</orderedlist>
       </sect3>
 
       <sect3>
 	<title>&os.current; нь юу <emphasis>Биш</emphasis> вэ?</title>
 
 	<orderedlist>
 	  <listitem>
 	    <para>Та зарим нэг дажгүй шинэ боломж байгааг сонссон учраас бусдаас
 		түрүүлж урьдчилсан хувилбарын тэдгээр битүүдийг авах таны нэн тэргүүний
 		арга зам. Шинэ боломжийг авч эхэнд байна гэдэг нь та шинэ алдаанууд,
 		хорхойнуудыг бас авч эхэнд байна гэсэн үг юм.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>Алдааны засваруудыг хурдан авах арга зам. &os.current;-ийн
 		өгөгдсөн дурын хувилбар нь илэрсэн алдаануудыг засахын хажуугаар бас
 		магадгүй шинэ алдаанууд бас гаргаж байдаг.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>Аль ч үед <quote>албан ёсоор дэмжигдсэн</quote>. Бид өөрсдийн
 		чадлын хирээр <quote>хууль ёсны</quote> 3 &os.current; бүлгийн
 		аль нэгэнд хүмүүст бодитоор туслахыг хичээдэг, гэхдээ бидэнд ердөө л
 		техникийн дэмжлэг үзүүлэх <emphasis>цаг байдаггүй</emphasis>.
 		Энэ нь бид хүмүүст туслах дургүй өөдгүй муухай хүмүүс учраас гэсэн үг
 		биш юм (хэрэв бид байгаагүй бол бид &os;-г хийж байхгүй байх байсан).
 		Бид ердөө л өдрийн хэдэн зуун захидлуудад хариулахын
 		<emphasis>хажуугаар</emphasis> FreeBSD дээр ажиллаж чаддаггүй!
 		&os;-г сайжруулах болон туршилтын кодон дээр тавигдсан маш олон
 		асуултуудад хариулах хоёр сонголтын эхнийхийг хөгжүүлэгчид сонгосон
 		юм.</para>
 	  </listitem>
 	</orderedlist>
       </sect3>
 
       <sect3>
 	<title>&os.current; ашиглах нь</title>
 
 	<orderedlist>
 	  <listitem>
-	    <indexterm>
-	      <primary>-CURRENT</primary>
-	      <secondary>ашиглах нь</secondary>
-	    </indexterm>
-
-	    <para>&a.current.name; болон &a.svn-src-head.name; жагсаалтуудад элсэн орно уу.
+	    <para>&a.current.name;<indexterm><primary>-CURRENT</primary><secondary>ашиглах нь</secondary></indexterm> болон &a.svn-src-head.name; жагсаалтуудад элсэн орно уу.
 		Энэ нь зөвхөн сайн санаанаас гадна бас <emphasis>чухал</emphasis>
 		юм. Хэрэв та <emphasis>&a.current.name;</emphasis> жагсаалтад
 		ороогүй бол системийн одоогийн төлвийн талаар хүмүүсийн  өгч байгаа санал
 		хүсэлтүүдийг харахгүй учраас бусдын аль хэдийн олоод шийдсэн маш их асуудлууд
 		дээр магадгүй та бүдрэн төөрөлдөж дуусах биз ээ. Бүр илүү чухал зүйл нь юу вэ гэвэл
 		таны системийн эрүүл мэндэд эгзэгтэй байж болох чухал мэдээнүүдээс та хоцрох
 		болно.</para>
 
 	    <para>&a.svn-src-head.name; жагсаалт нь кодонд оруулсан өөрчлөлт бүрийн
 		бүртгэл оруулгыг болзошгүй сөрөг нөлөөнүүдийн талаар тохирсон мэдээллийн
 		хамтаар танд харах боломжийг олгодог.</para>
 
 	    <para>Эдгээр жагсаалтууд эсвэл байгаа бусдын аль нэгэнд элсэхийн тулд
 		&a.mailman.lists.link; хаяг уруу орж элсэхийг хүссэн жагсаалтаа
 		сонгоорой. Дарааллын үлдсэн зааврууд тэнд байгаа болно. Хэрэв та
 	        бүх л эх модон дахь өөрчлөлтийг дагах сонирхолтой байгаа бол
 	        &a.svn-src-all.name; жагсаалтад бүртгүүлэхийг бид зөвлөж байна.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>&os;-ийн <link linkend="mirrors">толин тусгал</link>аас
 		эхийг авна. Та үүнийг гурван аргаар хийж болно:</para>
 
 	    <orderedlist>
-                <indexterm>
-                  <primary><command>svn</command></primary>
-                </indexterm>
-		<indexterm>
-		  <primary><command>cvsup</command></primary>
-		</indexterm>
-		<indexterm>
-		  <primary><command>cron</command></primary>
-		</indexterm>
-		<indexterm>
-		  <primary>-CURRENT</primary>
-		  <secondary><application>CVSup</application> ашиглан сүүлийн хэлбэрт аваачих</secondary>
-		</indexterm>
-
                 <listitem>
                   <para>Хүссэн хөгжүүлэлт эсвэл салбар хувилбарыг 
-		    татаж авахдаа <link linkend="svn">svn</link> програмыг 
+		    татаж авахдаа <link linkend="svn">svn</link><indexterm><primary><command>svn</command></primary></indexterm> програмыг 
 		    ашиглах хэрэгтэй. Энэ аргыг &os;-н хөгжүүлэлтэд хандахад
 		    зөвлөдөг. -CURRENT суурь системийн 
-		    <application>Subversion</application> татаж авах үндсэн 
+		    <application>Subversion</application><indexterm><primary>-CURRENT</primary><secondary><application>SVN</application> ашиглан сүүлийн хэлбэрт аваачих</secondary></indexterm> татаж авах үндсэн 
 		    URL нь <literal>http://svn.freebsd.org/base/head/</literal> бөгөөд 
 		    репозиторын хэмжээ их тул зөвхөн хүссэн дэд модоо 
 		    татаж авахыг зөвлөдөг.
                   </para>
                 </listitem>
 
                 <listitem>
 		  <para><filename>/usr/share/examples/cvsup</filename> санд байх
 			<filename>standard-supfile</filename> гэж нэрлэгдсэн
 			<filename>supfile</filename>-тай цуг
 			<link linkend="cvsup">cvsup</link> програм ашигла.
 			Та дээр дурдсан жишээ <filename>supfile</filename>-г
 			өөрчлөн <link linkend="cvsup">cvsup</link>-г өөрийн орчны хувьд
 			тохируулах хэрэгтэй.</para>
 
                   <warning>
                    <para><command>cvsup</command>-г ашиглах нь хуучирсан 
 		    бөгөөд төсөл ашиглахыг зөвлөдөггүй.</para>
                   </warning>
 
 		  <note>
 		    <para>Жишээ <filename>standard-supfile</filename> нь
 		      &os.current;-ийн биш &os;-ийн аюулгүй байдлын тусгай
 		      салбарыг дагахад хэрэглэгдэнэ. Танд энэ файлыг засварлаж дараах
 		      мөрийг өөрчлөх хэрэгтэй болно:</para>
 
 		    <programlisting>*default release=cvs tag=RELENG_<replaceable>X</replaceable>_<replaceable>Y</replaceable></programlisting>
 
 		    <para>Дээрх мөрийг дараах мөрөөр сольно:</para>
 
 		    <programlisting>*default release=cvs tag=.</programlisting>
 
 		    <para>Хэрэгцээтэй хаяг/шошгонуудын дэлгэрэнгүй тайлбарыг
 		      гарын авлагын <link
 		      linkend="cvs-tags">CVS хаяг/шошгонууд</link> хэсгээс үзнэ үү.</para>
 		  </note>
 	      </listitem>
 
 	      <listitem>
-		<indexterm>
-		  <primary>-CURRENT</primary>
-		  <secondary>CTM ашиглан сүүлийн хэлбэрт аваачих</secondary>
-		</indexterm>
-
 		<para><application><link
-		  linkend="ctm">CTM</link></application> хэрэгслийг ашигла.
+		  linkend="ctm">CTM</link></application><indexterm><primary>-CURRENT</primary><secondary>CTM ашиглан сүүлийн хэлбэрт аваачих</secondary></indexterm> хэрэгслийг ашигла.
 			Хэрэв та маш муу холболттой (өндөр үнэтэй холболтууд эсвэл
 			зөвхөн цахим захидлын хандалт) бол <application>CTM</application>
 			нь сонголт болох юм. Гэхдээ энэ нь бөөн зовлон бөгөөд та эвдэрсэн
 			файлуудтай үлдэж болох юм. Энэ нь үүнийг ховор ашиглахад хүргэдэг бөгөөд
 			ингэснээр ажиллахгүй байх боломжийг нэлээн удаан хугацаагаар ихэсгэдэг.
 			Бид Интернэт холболттой хүмүүст
 			<application><link linkend="svn">Subversion</link></application>-г
 			ашиглахыг зөвлөдөг.
 		</para>
 	      </listitem>
 	    </orderedlist>
 	  </listitem>
 
 	  <listitem>
 	    <para>Хэрэв та эхийг зөвхөн харахаар биш ажиллуулахаар татаж авч байгаа бол
 		зөвхөн сонгосон хэсгүүдийг биш &os.current;-ийн <emphasis>бүх</emphasis>
 		эхийг татаж аваарай. Үүний шалтгаан нь эхийн төрөл бүрийн хэсгүүд нь бусад хаа нэгтээ байгаа
 		шинэчлэлтүүдээс хамаардаг бөгөөд зөвхөн хэсэг бүлэг эхийг хөрвүүлэхийг оролдох нь
 		таныг бараг л баталгаатайгаар асуудалтай учруулах болно.</para>
 
-	  <indexterm>
-	    <primary>-CURRENT</primary>
-	    <secondary>хөрвүүлэх</secondary>
-	  </indexterm>
-	    <para>&os.current;-ийг хөрвүүлэхээсээ өмнө <filename>/usr/src</filename>
+	    <para>&os.current;-ийг<indexterm><primary>-CURRENT</primary><secondary>хөрвүүлэх</secondary></indexterm> хөрвүүлэхээсээ өмнө <filename>/usr/src</filename>
 		дахь <filename>Makefile</filename>-г анхааралтай уншина уу.
 		Эхний удаа та хамгийн багаар бодоход шинэчлэлтийн процессийн хэсэг болох <link
 	      linkend="makeworld">шинэ цөмийг суулгаж ертенцийг дахин бүтээх</link> хэсгээр
 		дамжих хэрэгтэй. &a.current; болон <filename>/usr/src/UPDATING</filename>
 		файлыг унших нь биднийг дараагийн хувилбар уруу шилжихэд заримдаа шаардлагатай
 		болдог бусад эхлүүлэх процедуруудын хувьд хамгийн сүүлийн мэдээлэлтэй  байлгах
 		боломжийг бидэнд олгодог.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>Идэвхтэй бай! Хэрэв та &os.current; ажиллуулж байгаа бол
 		түүний талаар таныг юу хэлэхийг ялангуяа хэрэв танд өргөжүүлэлт эсвэл
 		алдааны засваруудын талаар санал хүсэлт байвал түүнийг бид мэдэхийг
 		хүсдэг юм. Хавсаргасан кодтой санал хүсэлтүүдийг хамгийн их урам зоригтойгоор
 		хүлээн авдаг билээ!</para>
 	  </listitem>
 	</orderedlist>
       </sect3>
     </sect2>
 
     <sect2 id="stable">
       <title>&os;-ийн тогтвортой хэлбэрт байх нь</title>
 
       <sect3>
 	<title>&os.stable; гэж юу вэ?</title>
 	<indexterm><primary>-STABLE</primary></indexterm>
 
 	<para>&os.stable; нь үндсэн хувилбарууд гардаг бидний хөгжүүлэлтийн салбар юм.
 		Өөрчлөлтүүд нь эхлээд тест хийгдэх зорилгоор &os.current; уруу ордог гэсэн
 		ерөнхий төсөөлөл/таамаглалтайгаар янз бүрийн зөвшөөрлөөр энэ салбар уруу
 		ордог. Энэ нь <emphasis>одоо болтол</emphasis> хөгжүүлэлтийн салбар
 		бөгөөд гэхдээ энэ нь ямар ч үед &os.stable;-д зориулагдсан эх нь ямар ч зорилгод
 		тохирч эсвэл тохирохгүй байж болно гэсэн үг юм. Энэ нь эцсийн хэрэглэгчид
 		зориулагдсан эх үүсвэр бус ердөө л өөр нэг инженерчлэлийн хөгжүүлэлтийн арга зам
 		юм.</para>
       </sect3>
 
       <sect3>
 	<title>&os.stable; хэнд хэрэгтэй вэ?</title>
 
 	<para>Хэрэв та FreeBSD-ийн хөгжүүлэлтийн процессод хувь нэмэр оруулах сонирхолтой,
 		энэ нь ялангуяа FreeBSD-ийн дараагийн <quote>гарах</quote> хувилбартай холбоотой байдаг,
 		эсвэл юу болж байгааг мэдэж байх сонирхолтой байгаа бол та дараах
 		&os.stable;-г бодолцох хэрэгтэй.</para>
 
 	<para>Аюулгүй байдлын засварууд бас &os.stable; салбар уруу орж байдаг нь
 		үнэн боловч та үүнийг хийхийн тулд &os.stable;-г заавал дагах
 		<emphasis>хэрэггүй</emphasis>. FreeBSD-ийн аюулгүй байдлын
 		зөвлөмжүүд нь тухайн хувилбарт хамааралтай асуудлыг хэрхэн засах тухай
 		тайлбарладаг
 	  <footnote><para>Энэ нь бүр яг үнэн биш юм. Бид FreeBSD-ийн хуучин хувилбаруудыг
 		үргэлж дэмжиж чадахгүй, гэхдээ бид тэдгээрийг олон жилийн турш дэмжсээр
 		ирсэн. FreeBSD-ийн хуучин хувилбаруудын одоогийн аюулгүй байдлын бодлогын
 		бүрэн тайлбарыг <ulink
   	    url="&url.base;/security/">http://www.FreeBSD.org/security/</ulink>-с
 		үзнэ үү.</para>
 	  </footnote>
 		бөгөөд зөвхөн аюулгүй байдлын үүднээс бүхэл бүтэн хөгжүүлэлтийн салбарыг
 		дагаж байна гэдэг бас зөндөө олон хүсээгүй өөрчлөлтүүдийг авчрах
 		магадлалтай юм.</para>
 
 	<para>Бид &os.stable; салбар үргэлж хөрвүүлэгдэн эмхэтгэгдэж дандаа ажилладаг байлгахаар
 		чармайж байдаг боловч энэ нь баталгаатай биш юм. Нэмж хэлэхэд код нь &os.stable;-д
 		орохоосоо өмнө &os.current;-д хөгжүүлэгдэж байдаг боловч &os.current;-г
 		ашиглан ажиллуулдгаас илүү &os.stable;-г хүмүүс ажиллуулдаг болохоор
 		&os.current;-ийн хувьд илэрхий биш байсан алдаанууд болон булангийн тохиолдлууд
 		&os.stable;-д  илрэх нь заримдаа зайлшгүй юм.</para>
 
 	<para>Эдгээр шалтгаануудаас болоод бид &os.stable;-г сохроор дагахыг танд
 		<emphasis>зөвлөдөггүй</emphasis> бөгөөд энэ нь
 		өөрийн хөгжүүлэлтийн орчиндоо кодыг эхлээд сайтар тест хийлгүйгээр
 		үйлдвэрлэлд (production) ашиглаж байгаа серверүүдээ  &os.stable;
 		уруу шинэчлэхгүй байхад танд ялангуяа чухал ач холбогдолтой юм.</para>
 
 	<para>Хэрэв танд үүнийг хийх эх үүсвэрүүд байхгүй бол бид FreeBSD-ийн хамгийн сүүлийн үеийн
 		хувилбарыг ажиллуулж хоёртын шинэчлэлт хийх аргыг хувилбараас хувилбар уруу шилжихдээ
 		ашиглахыг танд зөвлөж байна.</para>
       </sect3>
 
       <sect3>
 	<title>&os.stable; ашиглах нь</title>
 
 	<orderedlist>
 	  <listitem>
-	    <indexterm>
-	      <primary>-STABLE</primary>
-	      <secondary>ашиглах нь</secondary>
-	    </indexterm>
-
-	    <para>&a.stable.name; жагсаалтад элсэн орно уу. Энэ нь
+	    <para>&a.stable.name;<indexterm><primary>-STABLE</primary><secondary>ашиглах нь</secondary></indexterm> жагсаалтад элсэн орно уу. Энэ нь
 		&os.stable;-д илэрч болох бүтээлтийн хамаарлууд эсвэл
 		тусгайлсан анхаарал шаардлагатай өөр бусад асуудлуудын талаар
 		танд мэдээлж байх болно. Хөгжүүлэгчид нь зарим нэг маргаантай засвар
 		эсвэл шинэчлэлийн талаар бодож байгаа талаараа бас энэ захидлын жагсаалтад
 		мэдээлдэг бөгөөд ийнхүү санал болгож байгаа өөрчлөлтийн талаар хэрэглэгчдэд
 		ямар нэг асуудал байвал тэдэнд эргээд хариу өгөх боломж олгодог юм.</para>
 
 	    <para>Өөрийн дагаж байгаа салбарын тохирох <application>SVN</application>
 	      жагсаалтад элсэн орох хэрэгтэй. Жишээ нь хэрэв та 9-STABLE салбарыг дагаж
 	      байгаа бол &a.svn-src-stable-9.name; жагсаалтад элсэн ороорой.
 	      Энэ нь кодонд оруулсан өөрчлөлт бүрийн
 	      бүртгэл оруулгыг болзошгүй сөрөг нөлөөнүүдийн талаар тохирсон мэдээллийн
 	      хамтаар танд харах боломжийг олгодог.</para>
 
 	    <para>Эдгээр жагсаалтууд эсвэл байгаа бусдын аль нэгэнд элсэхийн тулд
 		&a.mailman.lists.link; хаяг уруу орж элсэхийг хүссэн жагсаалтаа
 		сонгоорой. Дарааллын үлдсэн зааврууд тэнд байгаа болно. Хэрэв та
 	        бүх л эх модон дахь өөрчлөлтийг дагах сонирхолтой байгаа бол
 	        &a.svn-src-all.name; жагсаалтад бүртгүүлэхийг бид зөвлөж байна.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>Хэрэв та шинэ систем суулгаж &os.stable;-ээс бүтээсэн сар бүрийн хормын
 		агшны хувилбарыг түүн дээр ажиллуулахыг хүсэж байгаа бол дэлгэрэнгүй
 		мэдээллийн талаар <ulink url="&url.base;/snapshots/">
 		Хормын агшны хувилбарууд</ulink> вэб хуудаснаас шалгана уу.
 		Үүнээс гадна хамгийн сүүлийн үеийн &os.stable; хувилбарыг
 		<link linkend="mirrors">толин тусгалын хаягууд</link>аас
 		татан авч суулгах боломжтой бөгөөд доор дурдсан заавруудыг дагаж
 		өөрийн системийг хамгийн сүүлийн үеийн &os.stable; эх код уруу
 		шинэчилж болох юм.</para>
 
 	    <para>Хэрэв та &os;-ийн урдны хувилбар аль хэдийн ажиллуулж байгаа бөгөөд
 		эхээс шинэчлэхийг хүсэж байгаа бол &os;-ийн
 		<link linkend="mirrors">толин тусгал хуудас</link>аас хялбараар
 		хийж болно. Үүнийг гурван аргаар хийж болно:</para>
 
 	    <orderedlist>
-		<indexterm>
-		  <primary><command>svn</command></primary>
-		</indexterm>
-		<indexterm>
-		  <primary><command>cvsup</command></primary>
-		</indexterm>
-		<indexterm>
-		  <primary><command>cron</command></primary>
-		</indexterm>
-		<indexterm>
-		  <primary>-STABLE</primary>
-		  <secondary><application>Subversion</application>  ашиглан сүүлийн хэлбэрт аваачих</secondary>
-		</indexterm>
-
               <listitem>
                 <para>Хүссэн хөгжүүлэлт эсвэл салбар хувилбарыг 
-		   татахдаа <link linkend="svn">svn</link> програмыг ашиглах хэрэгтэй.
+		   татахдаа <link linkend="svn">svn</link><indexterm><primary><command>svn</command></primary></indexterm> програмыг ашиглах хэрэгтэй.
 		   Энэ аргыг &os;-н хөгжүүлэлтэд хандахад
 		   зөвлөдөг. Салбарын нэрсэд одоогийн хөгжүүлэлтийн 
 		   толгой хувилбарын хувьд <literal>head</literal>, 
 		   болон <literal>stable/9</literal> эсвэл 
                    <literal>releng/9.0</literal> гэх зэрэг <ulink
                    url="&url.base;/releng/">хувилбар инженерчлэлийн хуудас</ulink> 
 		   дахь салбарууд ордог. Суурь системийн 
 		   <application>Subversion</application> татаж авах үндсэн 
-		   URL нь <literal>http://svn.freebsd.org/base/</literal> бөгөөд 
+		   URL нь <literal>http://svn.freebsd.org/base/</literal><indexterm><primary>-STABLE</primary><secondary><application>Subversion</application>  ашиглан сүүлийн хэлбэрт аваачих</secondary></indexterm> бөгөөд 
 		   репозиторын хэмжээ их тул зөвхөн хүссэн дэд модоо 
 		   татаж авахыг зөвлөдөг.
                </para>
               </listitem>
 
               <listitem>
 		<para><filename>/usr/share/examples/cvsup</filename> санд байх
 			<filename>standard-supfile</filename> гэж нэрлэгдсэн
 			<filename>supfile</filename>-тай цуг
 			<link linkend="cvsup">cvsup</link> програм ашигла.
 			Та дээр дурдсан жишээ <filename>supfile</filename>-г
 			өөрчлөн <link linkend="cvsup">cvsup</link>-г өөрийн орчны хувьд
 			тохируулах хэрэгтэй.</para>
 
                 <warning>
                   <para><command>cvsup</command> нь хуучирсан бөгөөд 
 		    төсөл ашиглахыг зөвлөдөггүй.</para>
                 </warning>	      
 	      </listitem>
 
 	      <listitem>
-		<indexterm>
-		  <primary>-STABLE</primary>
-		  <secondary>CTM ашиглан сүүлийн хэлбэрт аваачих</secondary>
-		</indexterm>
-
 		<para><application><link
-		  linkend="ctm">CTM</link></application> хэрэгслийг ашигла.
+		  linkend="ctm">CTM</link></application><indexterm><primary>-STABLE</primary><secondary>CTM ашиглан сүүлийн хэлбэрт аваачих</secondary></indexterm> хэрэгслийг ашигла.
 			Хэрэв танд Интернэт уруу холбогдсон хурдан хямд холболт байхгүй бол
 			энэ аргыг та ашиглах хэрэгтэй.
 		  </para>
 	      </listitem>
 	   </orderedlist>
 	 </listitem>
 
 	  <listitem>
 	    <para>Гол нь хэрэв та эхэд хурдан, шаардлагын улмаас хандах хэрэгтэй болоод
 		холболтуудын зурвасын өргөн ач холбогдолгүй бол <command>cvsup</command> эсвэл
 		<command>ftp</command> ашиглаарай. Бусад тохиолдолд
 		<application>CTM</application>-г ашигла.</para>
 	  </listitem>
 
 	  <listitem>
-	    <indexterm>
-	      <primary>-STABLE</primary>
-	      <secondary>хөрвүүлэх нь</secondary>
-	    </indexterm>
-
-	    <para>&os.current;-ийг хөрвүүлэхээсээ өмнө <filename>/usr/src</filename>
+	    <para>&os.current;-ийг<indexterm><primary>-STABLE</primary><secondary>хөрвүүлэх нь</secondary></indexterm> хөрвүүлэхээсээ өмнө <filename>/usr/src</filename>
 		дахь <filename>Makefile</filename>-г анхааралтай уншина уу.
 		Эхний удаа та хамгийн багаар бодоход шинэчлэлтийн процессийн хэсэг болох <link
 	      linkend="makeworld">шинэ цөмийг суулгаж ертенцийг дахин бүтээх</link> хэсгээр
 		дамжих хэрэгтэй. &a.current; болон <filename>/usr/src/UPDATING</filename>
 		файлыг унших нь биднийг дараагийн хувилбар уруу шилжихэд заримдаа шаардлагатай
 		болдог бусад эхлүүлэх процедуруудын хувьд хамгийн сүүлийн мэдээлэлтэй  байлгах
 		боломжийг бидэнд олгодог.</para>
 	  </listitem>
 	</orderedlist>
       </sect3>
     </sect2>
   </sect1>
 
   <sect1 id="synching">
     <title>Өөрийн эхийг хамгийн сүүлийн хэлбэрт аваачих нь</title>
 
     <para>Интернетийн (эсвэл цахим захидал) холболт ашиглан &os; төслийн эхүүдийн аль ч
 	хэсгийн хувьд эсвэл таны юу сонирхож байгаагаас хамааран бүх хэсгүүдийг
 	хамгийн шинэ байлгаж байх төрөл бүрийн аргууд байдаг. Бидний санал болгодог үндсэн
 	үйлчилгээнүүд бол <link linkend="svn">Subversion</link>, <link linkend="anoncvs">Anonymous буюу нэргүй
       CVS</link>, <link linkend="cvsup">CVSup</link> болон <link
       linkend="ctm">CTM</link> юм.</para>
 
     <warning>
       <para>Өөрийн эх модны зөвхөн зарим хэсгийг шинэчлэх боломжтой боловч
 	цорын ганц шинэчлэх арга бол модыг бүтнээр нь шинэчилж хэрэглэгчийн талбар
 	(өөрөөр хэлбэл <filename>/bin</filename> болон
         <filename>/sbin</filename> гэх мэт дэх хэрэглэгчийн талбарт ажилладаг
 	бүх програмууд) болон цөмийн эхүүдийг дахин эмхэтгэх явдал юм. Өөрийн эх модны
 	зөвхөн нэг хэсэг зөвхөн цөм эсвэл зөвхөн хэрэглэгчийн талбарыг шинэчлэх нь
 	асуудлууд гарахад ихэвчлэн хүргэдэг. Эдгээр асуудлууд нь эмхэтгэлтийн үеийн
 	алдаануудаас авахуулаад цөмийн сүйрлүүд эсвэл өгөгдлийн эвдрэлийг хүртэл
 	хамардаг.</para>
     </warning>
 
     <indexterm>
       <primary>CVS</primary>
       <secondary>anonymous буюу нэргүй</secondary>
     </indexterm>
 
     <para><application>Subversion</application>, <application>Нэргүй CVS</application> болон
       <application>CVSup</application> нь эхийг шинэчлэхдээ
 	<emphasis>татах</emphasis> загварыг хэрэглэдэг.
 	<application>Subversion</application>-ийн хувьд хэрэглэгч (эсвэл
 	<command>cron</command> скрипт) <command>svn</command>
 	програмыг эхлүүлэн файлуудыг хамгийн шинэ хэлбэрт авчирдаг.
 	Локал эх модыг шинэчлэхэд зөвлөдөг арга бол <application>Subversion</application>
 	юм. <command>cvsup</command> ба <command>cvs</command> нь ижил 
 	зарчмаар ажиллах боловч хуучирсан бөгөөд Subversion-ийг ашиглахыг зөвлөдөг.
 	Таны хүлээн авах шинэчлэлтүүд нь хамгийн сүүлийн минут хүртэлх үеийнх
 	байх бөгөөд та тэдгээрийг зөвхөн өөрийн хүссэн тэр үедээ авдаг. Та өөрийн
 	шинэчлэлтүүдийг таны сонирхож байгаа тусгайлсан файлууд эсвэл сангуудаар
 	хялбараар хязгаарлаж болно. Шинэчлэлтүүд нь таны юуг авахыг хүссэн болон танд
 	юу байгаагаас хамааран серверээр тухайн үед үүсгэгддэг.
 	Үнэхээр шаардлагагүй л бол хуучирч ирээдүйд үргэлжүүлэн ашиглахаа болих 
 	бусад синхрон хийх аргуудаас илүүтэй <application>Subversion</application>-г 
 	ашиглах ёстой юм.</para>
 
     <indexterm>
       <primary><application>CTM</application></primary>
     </indexterm>
     <para>Нөгөө талаас <application>CTM</application> нь танд байгаа эхийг
 	мастер архив дахь эхтэй лавлаж асуух зарчмаар харьцуулдаггүй бөгөөд өөрөөр хэлбэл
 	тэдгээрийг татаж авдаггүй. Ингэхийн оронд харин өмнө нь ажиллуулснаас хойшх
 	файл дахь өөрчлөлтүүдийг таньдаг скрипт өдөрт хэд хэдэн удаа мастер CTM машин
 	дээр ажиллаж илэрсэн өөрчлөлтүүдийг шахаж дарааллын-дугаар тавин цахим
 	захидлаар дамжуулахад зориулан кодчилдог (зөвхөн хэвлэгдэх боломжтой ASCII
 	хэлбэрээр). Эдгээр <quote>CTM дельтануудыг</quote> авсаны дараа
 	тэдгээрийг автоматаар декод хийж шалган хэрэгчид байгаа эхийн хуулбарт
 	өөрчлөлтүүдийг хийх &man.ctm.rmail.1; хэрэгсэл уруу өгдөг. Энэ процесс
 	нь <application>CVSup</application>-с хамаагүй илүү үр дүнтэй
 	бөгөөд энэ нь <emphasis>татах</emphasis> биш харин
 	<emphasis>түлхэх</emphasis> загвар учраас бидний серверийн эх үүсвэрт
 	бага ачаалал учруулдаг юм.</para>
 
     <para>Мэдээж үүнээс гадна харилцан сул болон давуу талуудтай асуудлууд байдаг.
 	Хэрэв та санамсаргүйгээр өөрийн архивын хэсгийг устгачих юм бол
 	<application>CVSup</application> үүнийг илрүүлж эвдэрсэн хэсгүүдийг
 	дахин бүтээж өгдөг. <application>CTM</application> ингэж
 	хийдэггүй бөгөөд хэрэв та өөрийн эх модны зарим хэсгийг устгасан
 	(бас нөөцлөн аваагүй) бол та дахин шинээр эхнээс нь (хамгийн сүүлийн үеийн
 	CVS <quote>суурь дельтагаас</quote>) эхэлж
 	<application>CTM</application>-ийн тусламжтайгаар бүгдийг дахин бүтээх
 	буюу эсвэл <application>Нэргүй CVS</application>-ийн тусламжтайгаар
 	муу битүүдийг ердөө л устгаж дахин сүүлийн хэлбэрт аваачих хэрэгтэй болно.</para>
   </sect1>
 
   <sect1 id="makeworld">
     <title><quote>Ертөнц</quote>ийг дахин бүтээх нь</title>
 
     <indexterm>
       <primary><quote>Ертөнц</quote>ийг дахин бүтээх нь</primary>
     </indexterm>
     <para>Та өөрийн локал эх модоо &os;-ийн тухайн хувилбарын (&os.stable;,
 	&os.current;, гэх зэрэг) хамгийн сүүлийн үеийн хэлбэрт аваачсаныхаа
 	дараа та эх модоо ашиглан системийг дахин бүтээж болно.</para>
 
     <warning>
       <title>Нөөц хий</title>
 
       <para>Та дээрхийг хийхээсээ <emphasis>өмнө</emphasis> өөрийн системийг
 	нөөцлөн авах нь ямар чухал болохыг энэ нь хангалттай хэлж өгч чаддаггүй.
 	Ертөнцийг дахин бүтээх нь (хэрэв та эдгээр заавруудыг дагасан тохиолдолд)
 	хялбар боловч таныг алдаа гаргахад эсвэл бусдын эх модонд хийсэн алдаанууд
 	нь таны системийг ачаалагдахгүй болгох нөхцөлд зайлшгүй хүргэдэг.</para>
 
       <para>Нөөц хийж авсан эсэхээ шалгаарай. Засварлах уян диск эсвэл ачаалагдах
 	CD-г гарын дор байлгаарай. Магадгүй та үүнийг хэзээ ч хэрэглэхгүй байж болох
 	юм, гэхдээ харамсахаасаа өмнө аюулгүй байж байх нь илүү дээр юм!</para>
     </warning>
 
     <warning>
       <title>Тохирох захидлын жагсаалтад бүртгүүл</title>
 
       <indexterm><primary>захидлын жагсаалт</primary></indexterm>
       <para>&os.stable; болон &os.current; салбарууд нь угаасаа
 	<emphasis>хөгжүүлэлтэд байдаг</emphasis>. &os;-д хувь нэмэр
 	оруулж байгаа хүмүүс нь хүн л учраас алдаанууд заримдаа гардаг.</para>
 
       <para>Заримдаа эдгээр алдаанууд нь нэг их хор хөнөөлгүй бөгөөд ердөө л таны
 	системийг шинэ оношлогооны анхааруулга хэвлэхэд хүргэдэг. Эсвэл
 	өөрчлөлт нь сүйрлийн байж болзошгүй байдаг бөгөөд таны системийг ачаалагдахгүй
 	болгож эсвэл файлын системүүдийг чинь устгаж (эсвэл бүр муу юм болж) болох юм.</para>
 
       <para>Эдгээртэй адил асуудлууд гарвал асуудлын учир шалтгаан болон аль систем дээр
 	энэ асуудал хамааралтайг тайлбарласан <quote>heads up буюу бүхний сонорт</quote>
 	хандсан зарлал тохирох захидлын жагсаалтад  илгээгддэг. Тэгээд
 	<quote>all clear буюу бүгд цэвэр</quote> зарлал асуудал шийдэгдсэний дараа
 	тавигддаг.</para>
 
       <para>Хэрэв та &os.stable; эсвэл &os.current;-ийг дагахыг оролдож &a.stable;
 	эсвэл &a.current;-г харгалзуулан уншихгүй байгаа бол энэ нь та өөртөө гай төвөг асууж
 	байна л гэсэн үг юм.</para>
     </warning>
 
     <warning>
       <title><command>make world</command> тушаалыг бүү ашигла</title>
 
       <para>Ихэнх хуучин баримтууд үүнд зориулан <command>make world</command>
 	тушаалыг ашиглахыг зөвлөдөг. Энэ тушаалыг ажиллуулснаар зарим нэг чухал алхмуудыг
 	алгасах бөгөөд та юу хийж байгаагаа  мэдэж байгаа тохиолдолд үүнийг зөвхөн ашиглах
 	хэрэгтэй. Бараг ихэнх тохиолдолд <command>make world</command> хийх нь
 	буруу зүйл бөгөөд энд тайлбарласан процедурыг түүний оронд ашиглах ёстой юм.</para>
     </warning>
 
     <sect2 id="canonical-build">
       <title>Шалгагдсан аргаар өөрийн системийг шинэчлэх нь</title>
 
       <para>Өөрийн системийг шинэчлэхийн тулд өөрт чинь байгаа эхийн хувилбарт шаардлагатай байгаа
 	бүтээхээс урьдах алхмууд та <filename>/usr/src/UPDATING</filename>
 	файлд байгаа эсэхийг шалгах хэрэгтэй бөгөөд үүний дараа энд дурдсан процедурыг
 	ашиглана.</para>
 
       <para>Эдгээр шинэчлэлтийн алхмууд нь таныг хуучин хөрвүүлэгч, хуучин цөм, хуучин
 	ертөнц болон хуучин тохиргооны файлууд бүхий &os;-ийн хуучин хувилбар ашиглаж
 	байгаа гэж тооцдог. <quote>Ертөнц</quote> гэдгийг бид энд системийн гол хоёртын
 	файлууд, сангууд болон програмын файлууд гэж ойлгоно. Хөрвүүлэгч нь
 	<quote>ертөнц</quote>ийн хэсэг бөгөөд цөөн асуудлуудтай байдаг.</para>
 
       <para>Таныг шинэ системийн эхийг аль хэдийн авсан байгаа гэж бид бас
 	энд тооцдог. Тухайн систем дээр байгаа эхүүд бас хуучин байвал шинэ хувилбар
 	руу шилжүүлэх талаар бичсэн <xref linkend="synching"/>-с дэлгэрэнгүйг
 	үзнэ үү.</para>
 
       <para>Системийг эхээс шинэчлэх нь эхлээд санагдсанаасаа илүү нарийн байдаг
 	бөгөөд тойрон гарах боломжгүй, хамаарлууд бүхий шинэ асуудлууд гардгаас болоод
 	&os;-ийн хөгжүүлэгчид зөвлөдөг чиг хандлагаа жил ирэх тутам нэлээнээр
 	өөрчлөх шаардлагатай болсон. Энэ хэсгийн үлдсэн хэсэг нь одоогоор зөвлөж
 	байгаа шинэчлэх дарааллын талаар тайлбарлах болно.</para>
 
       <para>Амжилттай болох шинэчлэх дараалал бүр дараах асуудлуудыг
 	шийдэх ёстой:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>Хуучин хөрвүүлэгч шинэ цөмийг бүтээж чадахгүй байж болох
 	    юм. (Хуучин хөрвүүлэгчид заримдаа алдаатай байдаг.) Тиймээс шинэ
 	    цөмийг шинэ хөрвүүлэгчээр бүтээх ёстой. Ялангуяа шинэ цөм бүтээхээсээ
 	    өмнө шинэ хөрвүүлэгчийг бүтээх хэрэгтэй. Энэ нь шинэ хөрвүүлэгчийг
 	    заавал шинэ цөмөөс өмнө <emphasis>суулгасан</emphasis> байх ёстой
 	    гэсэн үг биш юм.</para>
 	</listitem>
 
 	<listitem>
 	  <para>Шинэ ертөнц шинэ цөмийн боломжууд дээр тулгуурлаж байж
 	    болох юм. Тиймээс шинэ цөмийг шинэ ертөнцийг суулгахаасаа өмнө
 	    суулгасан байх шаардлагатай.</para>
 	</listitem>
       </itemizedlist>
 
       <para>Эдгээр хоёр асуудал нь бидний дараагийн хэсгүүдэд тайлбарлах
 	гол <maketarget>buildworld</maketarget>,
 	<maketarget>buildkernel</maketarget>,
 	<maketarget>installkernel</maketarget>,
 	<maketarget>installworld</maketarget> дарааллын үндэс болдог.
 	Энэ нь одоогоор зөвлөдөг шинэчлэлтийн просессийг та яагаад заавал
 	сонгох ёстойг харуулсан бүх шалтгаануудын бүрэн дүүрэн жагсаалт
 	биш юм. Зарим нэг тийм ч мэдээжийн биш зүйлсийг доор жагсаав:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>Хуучин ертөнц шинэ цөм дээр зөв ажиллахгүй байж болох учир
 	    та шинэ цөм суулгасныхаа дараа шинэ ертөнцийг даруйхан суулгах
 	    ёстой.</para>
 	</listitem>
 
 	<listitem>
 	  <para>Шинэ ертөнц суулгахаасаа өмнө зарим нэг тохиргооны өөрчлөлтүүдийг
 	    хийх ёстой боловч зарим нь хуучин ертөнцийг эвдэж магадгүй юм. Тийм
 	    болохоор хоёр өөр тохиргооны шинэчлэлтийн алхам ерөнхийдөө шаардлагатай
 	    байдаг.</para>
 	</listitem>
 
 	<listitem>
 	  <para>Ихэнх хэсгийн хувьд шинэчлэх процесс нь зөвхөн файлуудыг солих юм уу
 	    эсвэл нэмдэг бөгөөд байгаа хуучин файлуудыг устгадаггүй. Цөөн тохиолдолд
 	    энэ нь асуудал үүсгэж болох юм. Үүний дүнд шинэчлэх арга зам нь зарим нэг
 	    алхам дээр гараар устгах тодорхой файлуудыг заримдаа зааж өгдөг. Үүнийг
 	    ирээдүйд автоматчилах юм уу эсвэл үгүй ч байж болох юм.</para>
 	</listitem>
       </itemizedlist>
 
       <para>Эдгээр зүйлс нь дараах зөвлөсөн дараалалд хүргэдэг. Тухайн шинэчлэлтүүдэд
 	зориулсан дэлгэрэнгүй дараалал нь нэмэлт алхмуудыг шаардаж болохыг санаарай.
 	Гэхдээ эдгээр гол процессууд тодорхой хугацаагаар өөрчлөгдөхгүй байх
 	ёстой юм:</para>
 
       <orderedlist>
 	<listitem>
 	  <para><command>make <maketarget>buildworld</maketarget></command></para>
 
 	  <para>Энэ нь эхлээд шинэ хөрвүүлэгч болон хамааралтай цөөн хэрэгслүүдийг
 	    бүтээж дараа нь шинэ ертөнцийн бусдыг хөрвүүлэхийн тулд шинэ хөрвүүлэгчийг
 	    ашигладаг. Үр дүн нь <filename class="directory">/usr/obj</filename>-д
 	    хадгалагддаг.</para>
 	</listitem>
 
 	<listitem>
 	  <para><command>make <maketarget>buildkernel</maketarget></command></para>
 
 	  <para>&man.config.8; болон &man.make.1;-ийг ашигладаг хуучин аргаасаа
 	    ялгаатай нь энэ тушаал <filename class="directory">/usr/obj</filename>
 	    санд байрлаж байгаа <emphasis>шинэ</emphasis> хөрвүүлэгчийг ашигладаг.
 	    Энэ нь хөрвүүлэгч болон цөмийн хооронд тохиромжгүй байдал үүсэхээс таныг
 	    хамгаалдаг.</para>
 	</listitem>
 
 	<listitem>
 	  <para><command>make <maketarget>installkernel</maketarget></command></para>
 
 	  <para>Шинэ цөм болон цөмийн модулиудыг дискэд байрлуулж шинээр шинэчилсэн
 	    цөмөөр ачаалах боломжийг бүрдүүлдэг.</para>
 	</listitem>
 
 	<listitem>
 	  <para>Ганц хэрэглэгчийн горим руу ачаалан орно.</para>
 
 	  <para>Ганц хэрэглэгчийн горим нь ажиллаж байгаа програм хангамжуудыг
 	    шинэчлэхэд гарах асуудлуудыг багасгадаг. Энэ нь бас шинэ цөм дээр
 	    хуучин ертөнцийг ажиллуулахад гарах асуудлыг багасгадаг.</para>
 	</listitem>
 
 	<listitem>
 	  <para><command>mergemaster <option>-p</option></command></para>
 
 	  <para>Энэ нь шинэ ертөнцөд зориулж зарим нэг тохиргооны файлуудын эхний
 	    шинэчлэлтүүдийг хийдэг. Жишээ нь энэ нь шинэ хэрэглэгчийн бүлгийг
 	    системд нэмэх, эсвэл шинэ хэрэглэгчийн нэрсийг нууц үгийн мэдээллийн санд
 	    нэмж болох юм. Сүүлийн шинэчлэлтээс хойш шинэ бүлгүүд эсвэл системийн
 	    тусгай хэрэглэгчийн бүртгэлүүдийг нэмэх үед энэ нь ихэвчлэн шаардлагатай
 	    байдаг. Ингэснээр <maketarget>installworld</maketarget> алхам нь
 	    шинээр суулгагдсан системийн хэрэглэгч эсвэл системийн бүлгийн нэрсийг
 	    ямар ч асуудалгүйгээр ашиглах боломжтой болох юм.</para>
 	</listitem>
 
 	<listitem>
 	  <para><command>make <maketarget>installworld</maketarget></command></para>
 
 	  <para><filename class="directory">/usr/obj</filename> сангаас
 	    ертөнцийг хуулдаг. Та одоо диск дээрээ шинэ цөм болон шинэ ертөнцтэй
 	    боллоо.</para>
 	</listitem>
 
 	<listitem>
 	  <para><command>mergemaster</command></para>
 
 	  <para>Нэгэнт диск дээрээ шинэ ертөнцтэй болсон болохоор та одоо
 	    үлдсэн тохиргооны файлуудаа шинэчилж болно.</para>
 	</listitem>
 
 	<listitem>
 	  <para>Дахин ачаална.</para>
 
 	  <para>Шинэ цөм болон шинэ ертөнцийг шинэ тохиргооны файлуудтай
 	    дуудахын тулд машиныг бүрэн дахин ачаалах хэрэгтэй.</para>
 	</listitem>
       </orderedlist>
 
       <para>Хэрэв та &os;-ийн нэг салбар дотор нэг хувилбараас илүү сүүлийн
 	хувилбар руу шинэчилж байгаа бол, өөрөөр хэлбэл 7.0-с 7.1 рүү шинэчилж
 	байгаа бол хөрвүүлэгч, цөм, хэрэглэгчийн талбар болон тохиргооны файлуудын
 	хооронд айхтар таарамжгүй байдлууд тантай бараг л тохиолдохгүй учир энэ
 	арга нь заавал шаардлагатай биш байж болох юм. Хуучин арга болох
 	<command>make <maketarget>world</maketarget></command> болон шинэ
 	цөмийг бүтээж суулгах нь жижиг шинэчлэлтийн хувьд хангалттай сайн
 	ажиллаж болох юм.</para>
 
       <para>Гэхдээ гол хувилбаруудын хооронд шинэчлэлт хийж байх үед энэ арга
 	замыг дагахгүй байгаа хүмүүст зарим асуудлууд учирч болох юм.</para>
 
       <para>Олон шинэчлэлтүүд (өөрөөр хэлбэл 4.<replaceable>X</replaceable>-с
 	5.0 руу) тусгайлсан нэмэлт алхмуудыг (жишээ нь installworld хийхээс өмнө
 	тусгай файлуудын нэрийг өөрчлөх эсвэл устгах гэх мэт) шаардаж болохыг энд
 	тэмдэглэх нь зүйтэй юм. <filename>/usr/src/UPDATING</filename> файлыг
 	анхааралтай уншина уу, ялангуяа одоогоор зөвлөсөн байгаа шинэчлэх дарааллыг
 	тусгайлан тайлбарласан төгсгөл хэсгийг уншаарай.</para>
 
       <para>Зарим нэг тохиромжгүй байдалтай холбоотой асуудлуудаас бүрэн
 	гүйцэд хамгаалах боломжгүйг хөгжүүлэгчид мэдсэнээр энэ арга нь цаг хугацааны
 	туршид сайжруулагдсаар ирсэн юм. Одоогийн арга замууд нь удаан хугацааны
 	туршид тогвортой байна гэдэгт найдаж байна.</para>
 
       <para>Дүгнэхэд &os;-г эхээс шинэчлэхэд одоогоор зөвлөдөг арга
 	бол:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/src</userinput>
 &prompt.root; <userinput>make buildworld</userinput>
 &prompt.root; <userinput>make buildkernel</userinput>
 &prompt.root; <userinput>make installkernel</userinput>
 &prompt.root; <userinput>shutdown -r now</userinput></screen>
 
       <note>
 	<para><maketarget>buildworld</maketarget> алхмаас өмнө
 	  <command>mergemaster -p</command> тушаалыг нэмж ажиллуулах
 	    цөөн ховор тохиолдлууд байдаг. Эдгээрийн талаар <filename>UPDATING</filename>
 	    файлд тайлбарласан байдаг. Хэрэв та &os;-ийн нэг буюу олон голлох
 	    хувилбаруудын дагуу шинэчлэл хийхгүй байгаа бол ерөнхийдөө энэ алхмыг
 	    эмээлгүйгээр орхиж болох юм.</para>
       </note>
 
       <para><maketarget>installkernel</maketarget> амжилттай дууссаны
 	дараа та ганц хэрэглэгчийн горим уруу ачаалах хэрэгтэй (өөрөөр хэлбэл&nbsp;
 	<command>boot -s</command> тушаалыг дуудагч мөрөөс ашиглана).
 	Дараа нь доор дурдсан тушаалуудыг ажиллуулна:</para>
 
       <screen>&prompt.root; <userinput>mount -u /</userinput>
 &prompt.root; <userinput>mount -a -t ufs</userinput>
 &prompt.root; <userinput>adjkerntz -i</userinput>
 &prompt.root; <userinput>mergemaster -p</userinput>
 &prompt.root; <userinput>cd /usr/src</userinput>
 &prompt.root; <userinput>make installworld</userinput>
 &prompt.root; <userinput>mergemaster</userinput>
 &prompt.root; <userinput>reboot</userinput></screen>
 
       <warning>
 	<title>Тайлбаруудыг цааш уншина уу</title>
 
 	<para>Дээр тайлбарласан дараалал нь зөвхөн таныг эхлэхэд туслах богино
 	     сэргээлт болох юм. Гэхдээ хэрэв та ялангуяа өөрчлөн тохируулсан
 	     цөмийн тохиргоо ашиглахыг хүсэж байгаа бол дараах хэсгүүдийг уншиж
 	     алхам бүрийг сайтар ойлгох хэрэгтэй.</para>
       </warning>
     </sect2>
 
     <sect2 id="src-updating">
       <title><filename>/usr/src/UPDATING</filename> файлыг унш</title>
 
       <para>Өөр юм хийж эхлэхээсээ өмнө та <filename>/usr/src/UPDATING</filename>-г
 	(эсвэл эх кодын хуулбар хаана байгаа тэндээс үүнтэй төстэй файлыг ) уншаарай.
 	Энэ файл нь танд учирч болзошгүй асуудлуудын талаар  чухал мэдээлэл агуулдаг бөгөөд
 	эсвэл таны ажиллуулах зарим нэг тушаалуудын дарааллын талаар заасан байдаг.
 	Хэрэв <filename>UPDATING</filename> файл таны энд уншсантай зөрчилдөж
 	байвал <filename>UPDATING</filename> файлд заасныг дагах хэрэгтэй.</para>
 
       <important>
 	<para><filename>UPDATING</filename> файлыг унших нь өмнө нь тайлбарласнаар
 	     зөв захидлын жагсаалтад бүртгүүлэхтэй харьцуулах юм бол хүлээн зөвшөөрч болохуйц
 	     орлогч байж чадахгүй юм. Энэ хоёр шаардлага нь нэмэлт бөгөөд заавал шаардлагатай
 	     биш юм.</para>
       </important>
     </sect2>
 
     <sect2 id="make-conf">
       <title><filename>/etc/make.conf</filename> файлыг шалга</title>
       <indexterm>
         <primary><filename>make.conf</filename></primary>
       </indexterm>
 
       <para><filename>/usr/share/examples/etc/make.conf</filename>
 	болон <filename>/etc/make.conf</filename> файлыг шалгаарай.
 	Эхнийх нь зарим нэг анхдагч тодорхойлолтуудыг агуулдаг &ndash; тэдгээрийн
 	ихэнх нь тайлбар болон хаагдсан байдаг. Та системээ эхээс нь дахин бүтээх үедээ
 	тэдгээрийг ашиглахын тулд <filename>/etc/make.conf</filename>
 	файлд нэмэх хэрэгтэй. <filename>/etc/make.conf</filename> файлд
 	нэмсэн болгон <command>make</command> тушаалыг ажиллуулах бүрд
 	бас ашиглагддаг учир өөрийн системдээ зориулан тэдгээрийг боломжийн утгаар
 	тохируулж өгөх нь зүйтэй юм.</para>
 
       <para>Ердийн хэрэглэгч <filename>/usr/share/examples/etc/make.conf</filename>
 	файлд байдаг <makevar>NO_PROFILE</makevar> мөрийг
 	<filename>/etc/make.conf</filename> уруу хуулж
 	тайлбар болгосныг болиулж нээхийг магадгүй хүсэж
 	болох юм.</para>
 
       <para><makevar>NOPORTDOCS</makevar> гэх зэрэг бусад 
         тодорхойлолтуудыг шалгаж танд хамаатай
 	эсэхээс хамаарч оруулах эсэхээ шийдээрэй.</para>
     </sect2>
 
     <sect2 id="updating-etc">
       <title><filename>/etc</filename> дэх файлуудыг шинэчил</title>
 
       <para><filename>/etc</filename> сан нь таны системийн тохиргооны мэдээллийн
 	ихэнх хэсгийг агуулдгаас гадна системийг эхлүүлэхэд ажилладаг скриптүүд энд байдаг.
 	Эдгээр скриптүүдийн зарим нь FreeBSD-ийн хувилбараас хувилбарт өөрчлөгддөг.</para>
 
       <para>Тохиргооны файлуудын зарим нь бас системийг ажиллуулахад өдөр тутам хэрэглэгддэг.
 	Ялангуяа <filename>/etc/group</filename>-г дурдаж болно.</para>
 
       <para><command>make installworld</command> тушаалын суулгалт хийх хэсэг нь
 	зарим нэг хэрэглэгчийн нэр эсвэл бүлгүүд байж байна гэж тооцдог тохиолдлууд байдаг.
 	Шинэчлэл хийж байх үед эдгээр хэрэглэгчид эсвэл бүлгүүд ихэнхдээ байхгүй байдаг.
 	Энэ нь шинэчлэл хийхэд асуудал учруулдаг. Зарим тохиолдолд <command>make buildworld</command>
 	нь эдгээр хэрэглэгчид эсвэл бүлгүүд байгаа эсэхийг шалгана.</para>
 
       <para>Үүний нэг жишээ нь <username>smmsp</username> хэрэглэгч нэмэгдсэн
 	тохиолдол юм. &man.mtree.8; нь <filename>/var/spool/clientmqueue</filename>-г
 	үүсгэхийг оролдох үед хэрэглэгчийн суулгалтын процесс энэ асуудлаас болж амжилтгүй
 	болж байсан.</para>
 
       <para>Үүний шийдэл нь &man.mergemaster.8;-г ертөнцийг бүтээхээс урд <option>-p</option>
 	тохируулгатай ажиллуулах явдал юм. Энэ нь <maketarget>buildworld</maketarget>
 	эсвэл <maketarget>installworld</maketarget> тушаалыг амжилттай болгоход
 	зөвхөн шаардлагатай файлуудыг харьцуулдаг.</para>
 
       <tip>
 	<para>Хэрэв та ялангуяа хэтэрхий санаа зовж байгаа бол тухайн бүлэгт харьяалагдаж байгаа
 	нэрийг нь өөрчилж байгаа эсвэл устгаж байгаа ямар файлууд байгааг өөрийн системээс
 	шалгаарай:</para>
 
 	<screen>&prompt.root; <userinput>find / -group <replaceable>GID</replaceable> -print</userinput></screen>
 
 	<para>дээрх нь <replaceable>GID</replaceable> (энэ бүлгийн нэр байж болно эсвэл
 	бүлгийн тоон ID байж болно) бүлгийн эзэмшдэг файлуудыг харуулна.</para>
       </tip>
     </sect2>
 
     <sect2 id="makeworld-singleuser">
       <title>Ганц хэрэглэгчийн горимд шилж</title>
       <indexterm><primary>ганц хэрэглэгчийн горим</primary></indexterm>
 
       <para>Та системийг ганц хэрэглэгчийн горимд эмхэтгэхийг хүсэж болох юм.
 	Энэ нь шинэчлэлтийг арай илүү хурдасгах илэрхий ашиг тустайгаас гадна
 	системийг дахин суулгах нь системийн стандарт хоёртын файлууд,
 	libraries буюу туслах сангууд, оруулгын файлууд гэх зэрэг системийн
 	маш олон чухал файлуудыг хөнддөг. Ажиллаж байгаа систем дээр эдгээрийг
 	өөрчлөх нь (ялангуяа хэрэв тухайн үед таны систем дээр идэвхтэй хэрэглэгчид
 	байвал) гай төвгийг өөрөө эрж байна гэсэн үг юм.</para>
 
       <indexterm><primary>олон хэрэглэгчийн горим</primary></indexterm>
       <para>Өөр нэг арга бол системийг олон хэрэглэгчийн горимд эмхэтгэж дараа нь
 	суулгахдаа ганц хэрэглэгчийн горимд шилжин хийх явдал юм. Хэрэв та энэ замаар
 	хийхийг хүсэж байвал бүтээлт дуустал дараах алхмууд дээр хүлээж байгаарай.
 	Та <maketarget>installkernel</maketarget> эсвэл
 	<maketarget>installworld</maketarget> хийх хүртлээ ганц хэрэглэгчийн горимд
 	оролгүйгээр хүлээж байж болно.</para>
 
       <para>Супер хэрэглэгч болоод та доор дурдсаныг:</para>
 
       <screen>&prompt.root; <userinput>shutdown now</userinput></screen>
 
       <para>ажиллаж байгаа системээс ганц хэрэглэгчийн горим уруу оруулахдаа
 	ажиллуулж болно.</para>
 
       <para>Өөр нэг арга нь системийг дахин ачаалаад ачаалалтын тушаал хүлээх мөрөн дээр
 	<quote>single user буюу ганц хэрэглэгч</quote> тохируулгыг сонгоорой.
 	Ингэхэд систем ганц хэрэглэгчийг ачаална. Бүрхүүлийн тушаал хүлээх мөрөнд та
 	доор дурдсан тушаалуудыг ажиллуулах шаардлагатай:</para>
 
       <screen>&prompt.root; <userinput>fsck -p</userinput>
 &prompt.root; <userinput>mount -u /</userinput>
 &prompt.root; <userinput>mount -a -t ufs</userinput>
 &prompt.root; <userinput>swapon -a</userinput></screen>
 
       <para>Энэ нь файлын системүүдийг шалгаж <filename>/</filename>-г
 	дахин унших/бичихээр дахин холбож бусад бүх UFS файлын системүүдийг
 	<filename>/etc/fstab</filename>-д заасны дагуу холбон дараа нь
 	swap-ийг идэмвхжүүлэх болно.</para>
 
 
         <note>
           <para>Хэрэв таны CMOS цаг нь GMT биш локал хугацаагаар тохируулагдсан бол
 		(хэрэв &man.date.1; тушаалын гаралт зөв цаг болон бүсийг харуулахгүй
 		бол энэ нь үнэн) та дараах тушаалыг бас ажиллуулах хэрэгтэй болж
 		болох юм:</para>
 <screen>&prompt.root; <userinput>adjkerntz -i</userinput></screen>
 
           <para>Энэ нь таны локал цагийн бүсийн тохируулгуудыг зөвөөр тохируулж өгдөг &mdash;
 		үүнийг хийхгүй бол та дараа нь зарим асуудлуудтай тулгарч магадгүй.
           </para>
         </note>
 
     </sect2>
 
     <sect2 id="cleaning-usr-obj">
       <title><filename>/usr/obj</filename>-г устга</title>
 
       <para>Системийн хэсгүүд дахин бүтээгдсэнийхээ дараа (анхдагчаар)
 	<filename>/usr/obj</filename> дахь сангуудад байршдаг. Эдгээр сангууд нь
 	<filename>/usr/src</filename> дотор байгааг халхалдаг.</para>
 
       <para>Та <command>make buildworld</command> процессийг хурдасгаж болох бөгөөд
 	энэ санг бас устгаснаар хамаарлын зовлонгуудаас өөрийгөө магадгүй аврах болно.</para>
 
       <para><filename>/usr/obj</filename> доторх зарим файлуудад immutable
 	буюу хувиршгүй туг тавигдсан (дэлгэрэнгүй мэдээллийг &man.chflags.1;-с үзнэ үү )
 	байж болох бөгөөд түүнийг эхлээд арилгах хэрэгтэй.</para>
 
       <screen>&prompt.root; <userinput>cd /usr/obj</userinput>
 &prompt.root; <userinput>chflags -R noschg *</userinput>
 &prompt.root; <userinput>rm -rf *</userinput></screen>
     </sect2>
 
     <sect2 id="updating-upgrading-compilebase">
       <title>Үндсэн системийг дахин эмхэтгэ</title>
 
       <sect3>
 	<title>Гаралтыг хадгалах нь</title>
 
 	<para>&man.make.1;-г ажиллуулахдаа гарах үр дүнг өөр файл уруу хадгалах нь
 	зүйтэй юм. Хэрэв ямар нэг юм болохоо боливол та алдааны мэдэгдлийн хуулбартай
 	байх болно. Энэ нь танд юу буруутсаныг шинжлэхэд чинь тус болохгүй байж болох боловч
 	та өөрийн энэ асуудлаа &os;-ийн аль нэг захидлын жагсаалт уруу илгээсэн тохиолдолд
 	бусдад тус болж болох юм.</para>
 
 	<para>Үүнийг хамгийн амраар хийхийн тулд &man.script.1; тушаалыг бүх гаралтыг хадгалах
 	файлын нэрийг заасан параметрийн хамтаар ашиглана. Та үүнийг ертөнцийг дахин бүтээхээс
 	өмнөхөн нэн даруй хийж дараа нь процесс дууссаны дараа <userinput>exit</userinput>
 	гэж бичиж гарна.</para>
 
 	<screen>&prompt.root; <userinput>script /var/tmp/mw.out</userinput>
 Script started, output file is /var/tmp/mw.out
 &prompt.root; <userinput>make TARGET</userinput>
 <emphasis>&hellip; compile, compile, compile &hellip;</emphasis>
 &prompt.root; <userinput>exit</userinput>
 Script done, &hellip;</screen>
 
 	<para>Хэрэв та үүнийг хийх бол гаралтыг <filename>/tmp</filename> дотор
 	<emphasis>битгий </emphasis> хадгалаарай. Энэ сан нь таныг дахин ачаалсны
 	дараа цэвэрлэгдэж болох юм. Энэ файлыг хадгалах арай илүү боломжийн газар нь
 	<filename>/var/tmp</filename> (өмнөх жишээн дээрх шиг) эсвэл
 	<username>root</username> хэрэглэгчийн гэр сан байж болох юм.</para>
       </sect3>
 
       <sect3 id="make-buildworld">
 	<title>Үндсэн системийг эмхэтгэ</title>
 
 	<para>Та <filename>/usr/src</filename> сан дотор байх
 	шаардлагатай:</para>
 
 	<screen>&prompt.root; <userinput>cd /usr/src</userinput></screen>
 
 	<para>(гэхдээ мэдээж таны код өөр газар байгаа тохиолдолд тэр сан уруугаа орох
 	     хэрэгтэй).</para>
 	<indexterm><primary><command>make</command></primary></indexterm>
 
 	<para>Ертөнцийг дахин бүтээхдээ та &man.make.1; тушаалыг ашиглана. Энэ
 	тушаал нь &os;-ийн агуулсан програмууд ямар дарааллаар дахин хэрхэн бүтээгдэх зэргийг
 	тайлбарласан <filename>Makefile</filename> файлаас заавруудыг уншдаг.</para>
 
 	<para>Таны бичих тушаалын мөрийн ерөнхий хэлбэр нь дараах байдлаар байна:</para>
 
 	<screen>&prompt.root; <userinput>make -<replaceable>x</replaceable> -D<replaceable>VARIABLE</replaceable> <replaceable>target</replaceable></userinput></screen>
 
 	<para>Энэ жишээн дээр <option>-<replaceable>x</replaceable></option> нь
 	&man.make.1; уруу таны дамжуулах тохируулга юм. &man.make.1;-н гарын авлагын хуудаснаас
 	та дамжуулж болох тохируулгуудын жишээг үзнэ үү.</para>
 
 	<para><option>-D<replaceable>VARIABLE</replaceable></option>
 	  тохируулга нь <filename>Makefile</filename> уруу хувьсагч дамжуулж байна.
 	<filename>Makefile</filename>-ийн ажиллагаа эдгээр хувьсагчуудаар
 	хянагдана. Эдгээр нь <filename>/etc/make.conf</filename> дотор
 	зааж өгсөн хувьсагчуудтай адил бөгөөд энэ нь тэдгээрийг тохируулах бас нэг өөр
 	арга юм.</para>
 
 	<screen>&prompt.root; <userinput>make -DNO_PROFILE <replaceable>target</replaceable></userinput></screen>
 
 	<para>тушаал нь профиль хийгдсэн сангууд бүтээгдэх ёсгүйг заах өөр нэг арга бөгөөд
 	энэ нь <filename>/etc/make.conf</filename> дахь дараах</para>
 
 	<programlisting>NO_PROFILE=    true 	#    Avoid compiling profiled libraries</programlisting>
 
 	<para>мөрд харгалзах юм.</para>
 
 	<para><replaceable>target</replaceable> нь &man.make.1;-д
 	таны юу хийхийг хэлж өгдөг. <filename>Makefile</filename> болгон
 	өөр өөр <quote>targets буюу даалгаврын төрлүүдийг</quote> тодорхойлдог
 	бөгөөд таны сонгосон төрөл юу болохыг тодорхойлдог.</para>
 
 	<para>Зарим төрлүүд <filename>Makefile</filename>-д жагсаагдсан байх
 	бөгөөд гэхдээ эдгээр нь таныг ажиллуулахад зориулагдаагүй. Харин тэдгээр нь
 	системийг дахин бүтээхэд шаардлагатай алхмуудыг хэд хэдэн дэд алхмуудад хуваахын
 	тулд бүтээх процессод хэрэглэгддэг.</para>
 
 	<para>Ихэнх тохиолдолд та &man.make.1; уруу ямар ч параметр дамжуулах
 	хэрэггүй бөгөөд тэгэхээр таны тушаал дараахтай ижил байж болно:</para>
 
 	<screen>&prompt.root; <userinput>make <replaceable>target</replaceable></userinput></screen>
 
 	<para>дээрх <replaceable>target</replaceable> нь олон бүтээх тохируулгуудын
 	нэг болно. Эхний төрөл нь үргэлж <makevar>buildworld</makevar>
 	байх ёстой.</para>
 
 	<para>Нэртэйгээ адилаар <maketarget>buildworld</maketarget> нь
 	<filename>/usr/obj</filename> дотор бүрэн гүйцэд шинэ модыг бүтээх бөгөөд
 	өөр нэг төрөл болох <maketarget>installworld</maketarget> нь
 	энэ модыг тухайн машин дээр суулгадаг.</para>
 
 	<para>Тусдаа тохируулгуудтай байх нь хоёр шалтгаанаар маш ач холбогдолтой юм.
 	Нэгдүгээрт энэ нь бүтээлтийг таны ажиллаж байгаа системийн ямар ч хэсэгт нөлөөлөхгүйгээр
 	аюулгүйгээр хийхийг танд зөвшөөрдөг. Бүтээлт нь <quote>өөр дээрээ хийгдэнэ (self hosted)</quote>.
 	Ийм болохоор та <maketarget>buildworld</maketarget> тушаалыг олон
 	хэрэглэгчийн горимд ажиллаж байгаа машин дээр буруу нөлөөллөөс айлгүйгээр аюулгүйгээр
 	хийж болно. Гэхдээ <maketarget>installworld</maketarget> хэсгийн хувьд ганц
 	хэрэглэгчийн горимд хийхийг танд зөвлөдөг.</para>
 
 	<para>Хоёрдугаарт энэ нь сүлжээн дэх олон машинуудыг шинэчлэхэд
 	NFS холболтуудыг ашиглахыг танд зөвшөөрдөг. Хэрэв танд гурван машин байгаа бөгөөд
 	<hostid>A</hostid>, <hostid>B</hostid> болон <hostid>C</hostid>
 	машинуудыг шинэчлэхийг хүсвэл <command>make
 	  buildworld</command> болон <command>make installworld</command>
 	тушаалыг <hostid>A</hostid> дээр ажиллуулна.  Дараа нь <hostid>B</hostid> болон <hostid>C</hostid>
 	 машинууд <hostid>A</hostid> дээрх <filename>/usr/src</filename>
 	  болон <filename>/usr/obj</filename> сангуудыг NFS холболт хийн
 	<command>make installworld</command>-г ажиллуулж
 	бүтээлтийн үр дүнг <hostid>B</hostid> болон <hostid>C</hostid> дээр
 	суулгаж болох юм.</para>
 
 	<para><maketarget>world</maketarget> төрөл байсаар байгаа хэдий ч
 	танд түүнийг ашиглахгүй байхыг зөвлөж байна.</para>
 
 	<para>Дараах тушаалыг ажиллуул</para>
 
 	<screen>&prompt.root; <userinput>make buildworld</userinput></screen>
 
         <para>Хэд хэдэн зэрэгцээ процессуудыг үүсгэх <option>-j</option> тохируулгыг
 	<command>make</command> тушаалд зааж өгөх боломжтой. Энэ нь олон CPU-тэй
 	машинууд дээр хамгийн их ашигтай. Гэхдээ эмхэтгэх процессийн ихэнх нь CPU дээр биш
 	IO дээр ажилладаг болохоор энэ нь бас нэг CPU-тэй машинууд дээр ашигтай юм.</para>
 
 	<para>Ердийн нэг CPU-тэй  машин дээр та доор дурдсаныг ажиллуулж болох юм:</para>
 
 	  <screen>&prompt.root; <userinput>make -j4 buildworld</userinput></screen>
 
 	<para>&man.make.1; нь 4 хүртэлх процессийг нэгэн зэрэг ажиллуулах юм. Захидлын
 	жагсаалтуудад илгээгдсэн туршлагаас харахад энэ нь ерөнхийдөө ажиллагааг хамгийн сайн
 	хангаж хурдасгадаг байна.</para>
 
 	<para>Хэрэв та олон CPU машинтай бөгөөд SMP тохируулагдсан цөм ашиглаж байвал
 	утгыг 6-аас 10 хүртэл болгож хэр хурдсаж байгааг хараарай.</para>
       </sect3>
 
       <sect3>
 	<title>Хугацаа</title>
 	<indexterm>
 	  <primary><quote>ертөнцийг</quote> дахин бүтээх нь</primary>
 	  <secondary>хугацаа</secondary>
 	</indexterm>
 
         <para>Бүтээхэд шаардагдах хугацаанд олон хүчин зүйлс нөлөөлдөг, гэхдээ
 	нэлээн сүүлийн үеийн машинуудын хувьд &os.stable; модыг процессийн явцад ямар нэгэн
 	заль мэх эсвэл дөт зам ашиглалгүйгээр бүтээхэд зөвхөн нэг юм уу эсвэл хоёр цаг л
 	шаардагдах болох юм.  &os.current; модны хувьд арай удах болов уу.</para>
       </sect3>
     </sect2>
 
     <sect2 id="new-kernel">
       <title>Шинэ цөмийг эмхэтгэж суулга</title>
       <indexterm>
         <primary>цөм</primary>
 	<secondary>суулгах нь</secondary>
       </indexterm>
 
       <para>Та өөрийн шинэ системийн давуу талыг бүгдийг нь авахын тулд цөмөө дахин эмхэтгэх
 	хэрэгтэй. Зарим нэг санах ойн бүтцүүд өөрчлөгдсөн байх талтай бөгөөд
 	&man.ps.1; болон &man.top.1; зэрэг програмууд нь цөм болон эх кодын хувилбарууд
 	адил болтол ажилладаггүй болохоор эмхэтгэх нь үнэндээ чухал хэрэгцээтэй юм.</para>
 
       <para>Үүнийг хамгийн хялбараар аюулгүйгээр хийхийн тулд <filename>GENERIC</filename>
 	дээр тулгуурласан цөмийг бүтээж суулгах явдал юм. <filename>GENERIC</filename> нь
 	таны системийн хувьд хэрэгцээтэй төхөөрөмжүүдийг агуулаагүй байж болох боловч
 	таны системийг ядаж ганц хэрэглэгчийн горимд ачаалахад шаардлагатай бүгдийг агуулсан
 	байх ёстой. Шинэ систем зөв ажиллуулахад энэ сайн тест болж өгдөг.
 	<filename>GENERIC</filename>-с ачаалж таны систем ажиллаж байгааг шалгасны
 	дараа та өөрийн ердийн цөмийн тохиргооны файл дээр тулгуурлан шинэ цөмөө бүтээж
 	болох юм.</para>
 
       <para>&os; дээр шинэ цөм бүтээхээсээ өмнө <link
         linkend="make-buildworld">ертөнцийг бүтээх</link> нь чухал юм.</para>
 
       <note><para>Хэрэв та өөрчлөн тохируулсан цөмийг бүтээхийг хүсэж тохиргооны файлаа аль
 	хэдийн үүсгэсэн бол доор дурдсантай адилаар
 	<literal>KERNCONF=<replaceable>MYKERNEL</replaceable></literal>
 	гэж ашиглаарай:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/src</userinput>
 &prompt.root; <userinput>make buildkernel KERNCONF=<replaceable>MYKERNEL</replaceable></userinput>
 &prompt.root; <userinput>make installkernel KERNCONF=<replaceable>MYKERNEL</replaceable></userinput></screen>
       </note>
 
       <para>Хэрэв та <literal>kern.securelevel</literal> хувьсагчийг
 	1-ээс дээш болгон ихэсгэсэн <emphasis>бөгөөд</emphasis>
 	<literal>noschg</literal> эсвэл түүнтэй адил тугуудыг өөрийн цөмийн хоёртын
 	файлд тавьсан бол <maketarget>installkernel</maketarget> хийхийн тулд
 	та ганц хэрэглэгчийн горимд шилжин орох шаардлагатай байж болох юм. Үгүй бол
 	та энэ хоёр тушаалыг олон хэрэглэгчийн горимоос ямар ч асуудалгүйгээр
 	ажиллуулах ёстой. <literal>kern.securelevel</literal>-ийн талаар
 	дэлгэрэнгүйг &man.init.8; болон төрөл бүрийн файлын тугуудын талаар дэлгэрэнгүйг
 	&man.chflags.1; гарын авлагын хуудаснуудаас үзнэ үү.</para>
     </sect2>
 
     <sect2 id="new-kernel-singleuser">
       <title>Ганц хэрэглэгчийн горим уруу дахин ачаалан ор</title>
       <indexterm><primary>ганц хэрэглэгчийн горим</primary></indexterm>
 
       <para>Та шинэ цөмийн ажиллагааг шалгахын тулд ганц хэрэглэгчийн горимд дахин
 	ачаалан орох хэрэгтэй. Үүнийг <xref linkend="makeworld-singleuser"/>
 	дахь заавруудын дагуу хийнэ.</para>
     </sect2>
 
     <sect2 id="make-installworld">
       <title>Шинэ системийн хоёртын файлуудыг суулга</title>
 
       <para>Та шинэ системийн хоёртын
 	файлуудыг суулгахын тулд <maketarget>installworld</maketarget>
 	тушаалыг ашиглах шаардлагатай.</para>
 
       <para>Доор дурдсаныг ажиллуулна</para>
 
       <screen>&prompt.root; <userinput>cd /usr/src</userinput>
 &prompt.root; <userinput>make installworld</userinput></screen>
 
       <note>
 	<para>Хэрэв та <command>make buildworld</command> тушаалын мөрөнд
 	хувьсагчуудыг зааж өгсөн бол тэдгээр хувьсагчуудыг
 	<command>make installworld</command> тушаалын мөрөнд бас адилаар
 	зааж өгөх хэрэгтэй. Энэ бусад тохируулгуудын хувьд заавал шаардлагатай биш
 	байж болох юм; жишээ нь <option>-j</option> тохируулга
 	<maketarget>installworld</maketarget>-той цуг хэзээ ч хэрэглэгдэх
 	ёсгүй.</para>
 
 	<para>Жишээ нь хэрэв та доор дурдсаныг ажиллуулсан бол:</para>
 
 	<screen>&prompt.root; <userinput>make -DNO_PROFILE buildworld</userinput></screen>
 
 	<para>хоёртын файлуудыг дараах тушаалаар суулгана:</para>
 
 	<screen>&prompt.root; <userinput>make -DNO_PROFILE installworld</userinput></screen>
 
 	<para>ингэхгүй бол <command>make buildworld</command> тушаалын ажиллах
 	явцад бүтээгдээгүй профиль хийгдсэн сангуудыг (libraries) суулгахыг оролдох болно.</para>
       </note>
     </sect2>
 
     <sect2 id="post-installworld-updates">
       <title><command>make installworld</command> тушаалаар шинэчлэгдээгүй файлуудыг шинэчил</title>
 
       <para>Ертөнцийг дахин бүтээх нь зарим нэг сангуудыг (ялангуяа <filename>/etc</filename>,
 	<filename>/var</filename> болон <filename>/usr</filename>) шинэ болон
 	өөрчлөгдсөн тохиргооны файлуудаар шинэчилдэггүй.</para>
 
       <para>Эдгээр файлуудыг хамгийн амархнаар шинэчлэх арга нь &man.mergemaster.8;-г
 	ашиглах явдал юм, гэхдээ та хэрэв хүсвэл үүнийг гараар ажиллуулах боломжтой юм.
 	Аль ч аргыг сонголоо гэсэн  ямар нэгэн зүйл буруутсан тохиолдолд сэргээх боломжтойгоор
 	<filename>/etc</filename>-г нөөцөлж авах нь зүйтэй юм.</para>
 
     <sect3 id="mergemaster">
       <sect3info>
 	<authorgroup>
 	  <author>
 	    <firstname>Том</firstname>
 	    <surname>Рөүдс</surname>
 	    <contrib>Хувь нэмэр болгон оруулсан </contrib>
 	  </author>
 	</authorgroup>
       </sect3info>
       <title><command>mergemaster</command></title>
         <indexterm><primary><command>mergemaster</command></primary></indexterm>
 
       <para>&man.mergemaster.8; хэрэгсэл нь <filename>/etc</filename> дэх
 	таны тохиргооны файлууд  болон <filename>/usr/src/etc</filename> эх модон дахь
 	тохиргооны файлуудын ялгааг тодорхойлоход танд тусалдаг Bourne скрипт юм.
 	Энэ нь системийн тохиргооны файлуудыг эх модон дахь тохиргооны файлуудаар шинэчлэх
 	зориулалттай бидний зөвлөдөг шийдэл юм.</para>
 
       <para>Эхлэхийн тулд өөрийн тушаал оруулах мөрөнд ердөө л <command>mergemaster</command>-г
 	бичиж түүний эхлэхийг нь хараарай. <command>mergemaster</command> нь түр зуурын
 	root орчныг <filename>/</filename>-с доошлуулан бүтээж төрөл бүрийн системийн тохиргооны
 	файлуудаар дамждаг. Тэдгээр файлууд нь таны системд суулгагдсан файлуудтай харьцуулагддаг.
 	Энэ үед хоорондоо ялгаатай файлууд &man.diff.1; хэлбэрээр үзүүлэгддэг бөгөөд
 	<option>+</option> тэмдэгтээр нэмэгдсэн эсвэл өөрчлөгдсөн мөрүүдийг
 	<option>-</option> тэмдэгтээр устгагдсан эсвэл шинэ мөрөөр солигдсон мөрүүдийг
 	харуулдаг. &man.diff.1;-н синтакс болон файлын өөрчлөлтүүдийг хэрхэн үзүүлдэг талаар
 	дэлгэрэнгүй мэдээллийг &man.diff.1; гарын авлагын хуудаснаас үзнэ үү.</para>
 
       <para>&man.mergemaster.8; нь зөрчилдөөнүүдийг үзүүлсэн файл болгоныг харуулдаг бөгөөд
 	энэ үед танд шинэ файлыг устгах (түр зуурын файл гэгддэг), түр зуурын файлыг өөрчлөлгүйгээр
 	суулгах, суусан байгаа файлтай түр зуурын файлыг нийлүүлэх эсвэл &man.diff.1;-н
 	гаралтыг дахин харах сонголтыг үзүүлэх болно.</para>
 
       <para>Түр зуурын файлыг устгахыг сонгосноор бид одоо байгаа файлаа хэвээр өөрчлөлгүй үлдээж
 	шинэ хувилбарыг устгахыг хүсэж байгаагаа &man.mergemaster.8;-д хэлж байна гэсэн үг юм.
 	Хэрэв та одоо байгаа файлаа өөрчлөх шалтгааныг олж харахгүй байгаагаас бусад тохиолдолд
 	энэ сонголтыг хийхийг зөвлөдөггүй. Та ямар ч үед &man.mergemaster.8; тушаал хүлээх
 	мөрөн дээр <keycap>?</keycap> гэж бичин тусламж авч болох юм. Хэрэв хэрэглэгч
 	файлыг орхихоор сонгосон бол энэ нь бусад бүх файлуудтай ажилсны дараа дахин үзүүлэгдэн
 	хэрэглэгчээс тушаал хүлээх болно.</para>
 
       <para>Өөрчлөгдөөгүй түр зуурын файлыг суулгахыг сонгосноор одоо байгаа файлыг шинээр
 	сольдог. Ихэнх өөрчлөгдөөгүй файлуудын хувьд энэ нь хамгийн шилдэг сонголт юм.</para>
 
       <para>Файлыг нийлүүлэхийг сонгосноор текст засварлагч болон хоёр файлын агуулгыг танд
 	харуулах болно. Та дэлгэцийн хоёр талд байрласан тэдгээр хоёр файлыг хоёуланг нь
 	шалган аль аль талаас нь хэрэгтэй хэсгүүдийг сонгон эцсийн бүтээгдэхүүн гаргаж аван
 	нийлүүлж болно. Файлууд нь дэлгэцийн хоёр талд байрлан харьцуулагдах явцад
 	<keycap>l</keycap> түлхүүр таны зүүн талын агуулгыг сонгодог бол
 	<keycap>r</keycap> түлхүүр нь таны баруун тал дахь агуулгыг сонгох юм.
 	Гарах эцсийн үр дүн нь хоёр файлын хоёулангийн хэсгүүдийг агуулсан файл болох бөгөөд
 	түүнийг дараа нь суулгах боломжтой болох юм. Энэ сонголтыг хэрэглэгчийн тохиргоонуудад
 	хийгдсэн өөрчлөлтүүдтэй файлуудын хувьд хэрэглэх нь зуршил болжээ.</para>
 
       <para>&man.diff.1;-ээс гарах үр дүнг дахин харахыг сонгосноор өмнө нь
 	&man.mergemaster.8; файлын өөрчлөлтүүдийг харуулан таны сонголтыг хүлээсний
 	нэгэн адилыг дахин харуулдаг.</para>
 
       <para>&man.mergemaster.8; системийн файлуудтай ажиллаж дууссаны дараа
 	танаас бусад сонголтуудыг хийхийг хүлээдэг. &man.mergemaster.8; тушаал
 	нууц үгийн файлыг дахин бүтээхийг хүсэж байгаа эсэхийг танаас асууж үлдсэн
 	түр зуурын файлуудыг устгах сонголтыг үзүүлэн дуусдаг.</para>
       </sect3>
 
       <sect3>
 	<title>Гараар шинэчлэх</title>
 
       <para>Хэрэв та гараар шинэчлэхийг хүсвэл гэхдээ та <filename>/usr/src/etc</filename>
 	сангаас <filename>/etc</filename> сан уруу файлуудыг зүгээр л дарж хуулж ажиллуулж
 	чадахгүй. Зарим файлуудыг эхлээд <quote>суулгах</quote> хэрэгтэй. Учир нь
 	<filename>/usr/src/etc</filename> сан таны <filename>/etc</filename>
 	сангийн хуулбар шиг байхаар <emphasis>харагддагүй</emphasis>. Мөн
 	<filename>/usr/src/etc</filename> санд байдаггүй хэрнээ
 	<filename>/etc</filename> сан дотор байх шаардлагатай зарим файлууд
 	байдаг.</para>
 
       <para>Хэрэв та &man.mergemaster.8; (зөвлөсний дагуу) ашиглаж байвал та
 	<link linkend="updating-upgrading-rebooting">дагаагийн хэсэг</link> уруу
 	орж болно.</para>
 
       <para>Үүнийг гараар хамгийн хялбар аргаар хийхийн тулд файлуудыг шинэ сан уруу
 	суулгаж нэг бүрчлэн өөрчлөлтүүдийг хайн ажиллах хэрэгтэй.</para>
 
       <warning>
 	<title>Өөрт байгаа <filename>/etc</filename>-г нөөцөл</title>
 
 	<para>Онолоор бол автоматаар энэ санд юу ч хүрдэггүй ч үүнд үргэлж итгэлтэй
 	байх хэрэгтэй. Тэгэхээр өөрийн байгаа <filename>/etc</filename> санг
 	хаа нэг аюулгүй газар хуулах хэрэгтэй. Доорхтой адилаар:</para>
 
 	<screen>&prompt.root; <userinput>cp -Rp /etc /etc.old</userinput></screen>
 
 	<para><option>-R</option> нь рекурсив хуулбар хийх бөгөөд
 	<option>-p</option> нь файлуудын хугацаа, эзэмшигч гэх мэтийг
 	хадгалдаг.</para>
       </warning>
 
       <para>Та шинэ <filename>/etc</filename> болон бусад файлуудыг суулгахын тулд
 	хоосон сангууд бүтээх хэрэгтэй. <filename>/var/tmp/root</filename> нь
 	боломжийн сонголт болох бөгөөд энэ сангийн доор хэд хэдэн дэд сангууд бас
 	шаардлагатай болно.</para>
 
       <screen>&prompt.root; <userinput>mkdir /var/tmp/root</userinput>
 &prompt.root; <userinput>cd /usr/src/etc</userinput>
 &prompt.root; <userinput>make DESTDIR=/var/tmp/root distrib-dirs distribution</userinput></screen>
 
       <para>Энэ нь шаардлагатай сангийн бүтцийг бүтээж файлуудыг суулгадаг.
 	<filename>/var/tmp/root</filename> дотор үүсгэгдсэн олон дэд сангууд
 	хоосон бөгөөд тэдгээрийг устгах шаардлагатай байдаг. Үүнийг хамгийн хялбараар
 	хийхийн тулд:</para>
 
       <screen>&prompt.root; <userinput>cd /var/tmp/root</userinput>
 &prompt.root; <userinput>find -d . -type d | xargs rmdir 2&gt;/dev/null</userinput></screen>
 
       <para>Энэ нь бүх хоосон сангуудыг устгана. (Хоосон биш сангуудын тухай анхааруулгуудыг
 	гаргахгүйн тулд стандарт алдаа нь <filename>/dev/null</filename>
 	уруу илгээгддэг.)</para>
 
       <para>Одоо <filename>/var/tmp/root</filename> нь <filename>/</filename>-с
 	доор байрлах тохирох байрлалуудад байршуулах ёстой бүх файлуудыг агуулсан байх болно.
 	Та одоо эдгээр файл бүрийг шалгаж танд байгаа файлуудаас хэрхэн ялгаатай болохыг
 	тогтоох хэрэгтэй.</para>
 
       <para><filename>/var/tmp/root</filename> дотор суулгагдсан зарим файлуудын нэр
 	урдаа <quote>.</quote> тэмдэгттэй байдгийг анхаарна уу. Энэ баримтыг бичиж байх үед
 	ийм файлуудтай адил файлууд <filename>/var/tmp/root/</filename> болон
 	<filename>/var/tmp/root/root/</filename> сан дахь бүрхүүлийн эхлүүлэх файлууд
 	байсан, гэхдээ (таны хэзээ үүнийг уншиж байгаагаас хамаарч) өөр бусад файлууд байхыг
 	үгүйсгэхгүй. Тэдгээрийг олж харахын тулд <command>ls -a</command> тушаалыг
 	заавал ашиглаарай.</para>
 
       <para>Үүнийг хамгийн хялбар аргаар хийж хоёр файлыг харьцуулахын тулд &man.diff.1;
 	тушаалыг ашиглах явдал юм:</para>
 
       <screen>&prompt.root; <userinput>diff /etc/shells /var/tmp/root/etc/shells</userinput></screen>
 
       <para>Энэ нь таны <filename>/etc/shells</filename> файл болон
 	шинэ <filename>/var/tmp/root/etc/shells</filename> файлын хоорондын
 	ялгааг харуулна. Эдгээрийг ашиглаж өөрийн хийсэн өөрчлөлтүүдийг нийлүүлэх эсвэл
 	өөрийн хуучин файл дээрээс хуулах эсэхээ шийдээрэй.</para>
 
       <tip>
 	<title>Хувилбаруудын Хоорондох Ялгаануудыг Хялбараар Харьцуулахын Тулд Та
 	Шинэ Root Сангаа Тухайн Үеийн Хугацаагаар Нэрлээрэй</title>
 
 	<para>Ертөнцийг байнга дахин бүтээнэ гэдэг нь <filename>/etc</filename>-г
 	та бас байнга шинэчилнэ гэсэн үг бөгөөд энэ нь ердөө л жижиг хэвшмэл ажил юм.</para>
 
 	<para>Та энэ процессийг <filename>/etc</filename> уруу нийлүүлсэн
 	өөрийн хамгийн сүүлийн өөрчлөгдсөн файлуудыг хадгалснаар хурдасгаж болох юм.
 	Дараах процедур үүнийг хэрхэн хийж болох нэг санааг өгч байна.</para>
 
 	<procedure>
 	  <step>
 	    <para>Ертөнцийг жирийнээр бүтээ. <filename>/etc</filename> болон
 		бусад сангуудыг шинэчлэхийг хүсэхдээ тухайн цаг дээр тулгуурласан нэр бүхий
 		санг өг. Хэрэв та үүнийг 1998 оны 2 сарын 14-нд хийж байгаа бол дараах
 		байдлаар хийнэ:</para>
 
 	    <screen>&prompt.root; <userinput>mkdir /var/tmp/root-19980214</userinput>
 &prompt.root; <userinput>cd /usr/src/etc</userinput>
 &prompt.root; <userinput>make DESTDIR=/var/tmp/root-19980214 \
     distrib-dirs distribution</userinput></screen>
 	  </step>
 
 	  <step>
 	    <para>Энэ сангийн өөрчлөлтүүдийг дээр дурдсаны дагуу нийлүүл.</para>
 
 	    <para>Та дууссаныхаа дараа <filename>/var/tmp/root-19980214</filename>
 		санг <emphasis>битгий</emphasis> устгаарай.</para>
 	  </step>
 
 	  <step>
 	    <para>Та эхийн хамгийн сүүлийн хувилбарыг татан авч дахин бүтээхдээ 1-р алхмыг дага.
 		Энэ нь танд шинэ сан өгөх бөгөөд <filename>/var/tmp/root-19980221</filename>
 		гэж нэрлэгдсэн байж болох юм (хэрэв та шинэчлэлтүүдийг хийхдээ долоо хоног
 		хүлээсэн бол).</para>
 	  </step>
 
 	  <step>
 	    <para>Та одоо &man.diff.1; ашиглан хоёр сангийн хооронд рекурсив diff үүсгэж
 		долоо хоногийн хооронд хийгдсэн өөрчлөлтүүдийг харж болно:</para>
 
 	    <screen>&prompt.root; <userinput>cd /var/tmp</userinput>
 &prompt.root; <userinput>diff -r root-19980214 root-19980221</userinput></screen>
 
 	    <para>Ихэнхдээ энэ нь <filename>/var/tmp/root-19980221/etc</filename> болон
 		<filename>/etc</filename> хоёрын хоорондох өөрчлөлтүүдийг бодох юм бол
 		харьцангуй бага өөрчлөлтүүд байдаг. Өөрчлөлтүүд нь арай бага болохоор тэдгээр
 		өөрчлөлтүүдийг өөрийн <filename>/etc</filename> сан уруу шилжүүлэх нь
 		илүү хялбар байдаг.</para>
 	  </step>
 
 	  <step>
 	    <para>Та одоо хоёр <filename>/var/tmp/root-*</filename> сангуудын аль хуучныг
 		устгаж болно:</para>
 
 	    <screen>&prompt.root; <userinput>rm -rf /var/tmp/root-19980214</userinput></screen>
 	  </step>
 
 	  <step>
 	    <para><filename>/etc</filename> уруу өөрчлөлтүүдийг
 		нийлүүлэх болгондоо энэ процессийг давтах хэрэгтэй.</para>
 	  </step>
 	</procedure>
 
 	<para>Та &man.date.1;-г ашиглан сангийн нэрсийг автоматаар үүсгэж
 		болно:</para>
 
 	<screen>&prompt.root; <userinput>mkdir /var/tmp/root-`date "+%Y%m%d"`</userinput></screen>
       </tip>
       </sect3>
     </sect2>
 
     <sect2 id="updating-upgrading-rebooting">
       <title>Дахин ачаалах нь</title>
 
       <para>Та ерөнхийдөө ингээд хийгээд дуусч байна. Та бүх зүйл байх ёстой байрандаа байгаа эсэхийг шалгасныхаа
 	дараа системийг дахин ачаалж болно. Энгийн &man.shutdown.8; үүнийг
 	хийх болно:</para>
 
       <screen>&prompt.root; <userinput>shutdown -r now</userinput></screen>
     </sect2>
 
     <sect2>
       <title>Дууслаа</title>
 
       <para>Одоо та өөрийн &os; системийг амжилттайгаар шинэчлээд дууссан байх
 		ёстой. Баяр хүргэе.</para>
 
       <para>Хэрэв юмс шал буруугаар эргэвэл системийн тухайн хэсгийг дахин бүтээхэд амархан
 	байдаг. Жишээ нь хэрэв та шинэчлэлтийн явцад эсвэл <filename>/etc</filename>-г
 	нийлүүлэх явцад санамсаргүйгээр <filename>/etc/magic</filename> файлыг
 	устгасан бол &man.file.1; тушаал ажиллахаа больно. Ийм тохиолдолд дараах
 	засварыг ажиллуулж болох юм:</para>
 
 	<screen>&prompt.root; <userinput>cd /usr/src/usr.bin/file</userinput>
 &prompt.root; <userinput>make all install</userinput></screen>
     </sect2>
 
     <sect2 id="updating-questions">
       <title>Асуултууд</title>
 
       <qandaset>
 	<qandaentry>
 	  <question>
 	    <para>Өөрчлөлт бүрт зориулан ертөнцийг дахин бүтээх хэрэгтэй юу?</para>
 	  </question>
 
 	  <answer>
             <para>Үүнд хялбар хариулт байхгүй, учир нь өөрчлөлтийн цаад утга чанараас
 		хамаарна. Жишээ нь хэрэв та <application>CVSup</application>-г
 		дөнгөж ажиллуулахад дараах файлууд шинэчлэгдэж байгааг үзүүлж байгаа бол:</para>
 
 	    <screen><filename>src/games/cribbage/instr.c</filename>
 <filename>src/games/sail/pl_main.c</filename>
 <filename>src/release/sysinstall/config.c</filename>
 <filename>src/release/sysinstall/media.c</filename>
 <filename>src/share/mk/bsd.port.mk</filename></screen>
 
 	    <para>магадгүй бүхэл ертөнцийг дахин бүтээх хэрэггүй байж болох юм.
 		Та тохирох дэд сангууд уруу орж <command>make all install</command>
 		гэж тушаалыг өгөөд л болох юм. Хэрэв зарим нэг гол чухал зүйл жишээ нь
 		<filename>src/lib/libc/stdlib</filename> өөрчлөгдсөн бол
 		та ертөнцийг эсвэл хамгийн багаар бодоход статикаар холбогдсон (statically linked)
 		түүний тэдгээр хэсгүүдийг дахин бүтээх шаардлагатай болно.</para>
 
 	    <para>Эцсийн эцэст энэ нь танаас л хамаарна. Та жишээ нь хоёр долоо хоног тутам
 		ертөнцийг дахин бүтээж тэр хоёр долоо хоногийн хугацаанд өөрчлөлтүүдийг
 		хуримтлуулж байгаадаа сэтгэл хангалуун байж болно. Эсвэл та зөвхөн өөрчлөгдсөн
 		зүйлсүүдийг дахин бүтээхийг хүсэж магадгүй бөгөөд бүх хамаарлуудыг шийднэ
 		гэдэгтээ итгэлтэй байх хэрэгтэй.</para>
 
 	    <para>Тэгээд мэдээж энэ бүхэн таны ямар давтамжтайгаар шинэчлэхийг хүсдэг болон
 		&os.stable; эсвэл &os.current;-ийн алийг дагаж байгаагаас хамаарах
 		болно.</para>
 	  </answer>
 	</qandaentry>
 
 	<qandaentry>
 	  <question>
 	    <para>Миний эмхэтгэл маш олон дохио 11<indexterm>
 		<primary>дохио 11</primary></indexterm> (эсвэл бусад дохионы дугаар)
 		алдаагаар амжилтгүй болсон. Юу болсон юм бол?</para>
 	  </question>
 
 	  <answer>
 
 	    <para>Энэ нь ихэвчлэн тоног төхөөрөмжийн асуудлыг илэрхийлдэг.
 		Ертөнцийг (дахин) бүтээх нь өөрийн тоног төхөөрөмжийг ачаалах тест
 		хийх үр дүнтэй арга бөгөөд удаа дараа санах ойн асуудлууд байвал
 		тэдгээрийг илрүүлдэг. Эмхэтгэгч нь сонин/хачин дохионуудыг хүлээн авч
 		ид шидийн байдлаар амжилтгүй болсноор тэдгээр асуудлууд нь өөрсдийгөө
 		зарлан тунхагладаг.</para>
 
 	    <para>Хэрэв та бүтээлтийг дахин эхлүүлээд тэр нь процессийн өөр өөр хэсэгт
 		амжилтгүй болж байвал энэ нь үүнийг тодоор зааж байна
 		гэсэн үг юм.</para>
 
 	    <para>Энэ тохиолдолд та өөрийн машин дахь бүрэлдэхүүн хэсгүүдээ өөрчлөн
 		нэгээс нөгөөд сольж тавин аль нь ажиллахгүй байгааг олохоос өөр зүйл
 		хийж чадахгүй л болов уу.</para>
 	  </answer>
 	</qandaentry>
 
 	<qandaentry>
 	  <question>
 	    <para>Би дууссаныхаа дараа <filename>/usr/obj</filename>-г устгаж болох уу?</para>
 	  </question>
 
 	  <answer>
 	    <para>Товчхондоо бол болно.</para>
 
 	    <para><filename>/usr/obj</filename> нь эмхэтгэх үед бүтээгдсэн бүх
 		обьект файлуудыг агуулдаг. Жирийн үед <command>make buildworld</command>
 		процессийн эхний алхмуудын нэг нь энэ санг устгаад цоо шинээр эхлэх явдал
 		юм. Энэ тохиолдолд <filename>/usr/obj</filename>-г дууссаныхаа
 		дараа байлгаад байх нь ухаалаг биш бөгөөд үүнийг устгаснаар ихээхэн хэмжээний дискний зайг
 		суллах болно (одоогоор 2&nbsp;GB орчим).</para>
 
 	    <para>Гэхдээ хэрэв та юу хийж байгаагаа мэдэж байгаа бол <command>make buildworld</command>
 		хийхдээ энэ алхмыг алгасаж болно. Энэ нь дараа дараагийн бүтээлтийг илүү хурдасгадаг
 		бөгөөд учир нь ихэнх эхүүд дахин эмхэтгэх шаардлагагүй байдаг. Үүний сул тал нь
 		баригдашгүй хамаарлын асуудлууд илэрч таны бүтээлтийг хачин байдлаар амжилтгүй
 		болгодог. Хэн нэгэн илүү дөтлөх гэснээсээ болоод амжилтгүй болсныг мэдэлгүй өөрийн
 		бүтээлтийг амжилтгүй болсныг гомдоллосноор &os;-ийн захидлын жагсаалтуудад
 		хий дэмий шуугианыг удаа дараа  үүсгэдэг билээ.</para>
 	  </answer>
 	</qandaentry>
 
 	<qandaentry>
 	  <question>
 	    <para>Тасалдсан бүтээлтүүдийг үргэлжлүүлж болох уу?</para>
 	  </question>
 
 	  <answer>
 	    <para>Энэ нь асуудлыг олох хүртлээ та хэр хол явснаас хамаарна.</para>
 	    <para><emphasis>Ерөнхийдөө</emphasis> (энэ нь хэцүү бас хурдан дүрэм биш)
 		<command>make buildworld</command> процесс нь үндсэн
 		багажуудын (&man.gcc.1;, болон &man.make.1; зэрэг) болон системийн
 		сангуудын шинэ хуулбаруудыг бүтээдэг. Тэдгээр багажууд болон сангууд нь
 		дараа нь суулгагддаг. Шинэ багажууд болон сангууд дараа нь
 		өөрсдийгөө дахин бүтээхэд ашиглагддаг бөгөөд дахин суулгагддаг. Бүхэл бүтэн
 		систем (одоо &man.ls.1; эсвэл &man.grep.1; зэрэг ердийн хэрэглэгчийн програмууд)
 		дараа нь шинэ системийн файлуудтайгаар дахин бүтээгддэг.</para>
 
 	    <para>Хэрэв та сүүлийн шатанд байгаа бөгөөд та үүнийг мэдэж байгаа бол (та
 		хадгалж байгаа гаралтаас харсан болохоор) та дараах тушаалыг ажиллуулж
 		(бараг л аюулгүйгээр) болно:</para>
 
 	    <screen><emphasis>&hellip; fix the problem &hellip;</emphasis>
 &prompt.root; <userinput>cd /usr/src</userinput>
 &prompt.root; <userinput>make -DNO_CLEAN all</userinput></screen>
 
 	    <para>Энэ нь өмнөх <command>make buildworld</command> тушаалын
 		хийснийг буцаахгүй.</para>
 
 	    <para>Хэрэв та доорх мэдэгдлийг :</para>
 
 	      <screen>--------------------------------------------------------------
 Building everything..
 --------------------------------------------------------------</screen>
 
 	    <para><command>make buildworld</command> тушаалын гаралт дээр харсан
 		бол магадгүй тэгж хийх нь аюулгүй байж болох юм.</para>
 
 	    <para>Хэрэв та тийм мэдэгдэл харахгүй байгаа бол эсвэл та итгэлтэй биш байгаа бол
 		харамсахаасаа өмнө аюулгүй байдлыг бодож бүтээлтийг бүр эхнээс нь дахин эхлүүлсэн нь
 		дээр юм.</para>
 	  </answer>
 	</qandaentry>
 
 	<qandaentry>
 	  <question>
 	    <para>Би ертөнцийг бүтээхийг хэрхэн хурдасгах вэ?</para>
           </question>
 
           <answer>
 	    <itemizedlist>
 	      <listitem>
 		<para>Ганц хэрэглэгчийн горимд ажиллуул.</para>
 	      </listitem>
 
 	      <listitem>
 		<para><filename>/usr/src</filename> болон
 		  <filename>/usr/obj</filename> сангуудыг тус тусдаа байх дискнүүд
 		дээр тус тусдаа байх файлын системүүд дээр байрлуул. Хэрэв боломжтой бол
 		эдгээр дискнүүдийг тус тусад нь дискний хянагчууд дээр байрлуул.</para>
 	      </listitem>
 
 	      <listitem>
 		<para>&man.ccd.4; (нийлүүлсэн дискний драйвер) төхөөрөмж ашиглан
 		эдгээр файлын системүүдийг олон дискнүүдийн дагуу байрлуулах нь бас
 		арай илүү хурдасгах юм.</para>
 	      </listitem>
 
 	      <listitem>
 		<para>Профиль хийгдэхийг (<filename>/etc/make.conf</filename> файлд
 		<quote>NO_PROFILE=true</quote> гэж зааж өг) болиул. Танд энэ бараг
 		гарцаагүй хэрэггүй.</para>
 	      </listitem>
 
 	      <listitem>
 		<para><option>-j<replaceable>n</replaceable></option> тохируулгыг
 		&man.make.1;-д дамжуулж олон процессийг зэрэгцээгээр ажиллуул. Энэ нь
 		танд ганц эсвэл олон процессортой машин аль нь ч байсан ялгаагүйгээр ихэвчлэн тусалдаг.</para>
 	      </listitem>
 
 	      <listitem><para><filename>/usr/src</filename>-г агуулж байгаа файлын
 		систем <option>noatime</option> тохируулгаар холболт хийгдэж (эсвэл салгагдаж)
 		болно. Энэ нь файлын систем файл уруу хандах хандалтын хугацааг бүртгэхийг
 		болиулдаг. Танд магадгүй энэ мэдээлэл бараг л хэрэггүй биз ээ.</para>
 
 		  <screen>&prompt.root; <userinput>mount -u -o noatime /usr/src</userinput></screen>
 
 		  <warning>
 		    <para>Энэ жишээ <filename>/usr/src</filename> нь өөрийн файлын
 			систем дээр байгаа гэж тооцож байгаа болно. Хэрэв энэ нь тийм биш бол
 			(хэрэв энэ сан жишээ нь <filename>/usr</filename>-ийн хэсэг маягаар
 			байгаа бол) та <filename>/usr/src</filename>-г биш харин тэр
 			файлын системээ холболтын цэг болгон ашиглах хэрэгтэй.</para>
 		  </warning>
 	      </listitem>
 
 	      <listitem>
 		<para><filename>/usr/obj</filename>-г агуулж байгаа файлын систем
 		<option>async</option> тохируулгатай холболт хийгдэж (эсвэл салгагдаж)
 		болно. Энэ нь диск уруу хийх бичилтийг асинхроноор буюу зэрэг биш хийлгэдэг.
 		Өөрөөр хэлбэл бичилт нэн даруй хийгдээд өгөгдөл диск уруу цөөн секундын дараа
 		бичигддэг. Энэ нь бичилтүүдийг бүлэглэхийг зөвшөөрч маш их үр дүнтэйгээр
 		ажиллагааг хурдасгаж болох юм.</para>
 
 		<warning>
 		  <para>Энэ тохируулга нь таны файлын системийг илүү
 			эмзэг болгохыг санаарай. Тэжээл тасалдаж машин дахин ачаалах үед
 			файлын систем сэргээж болшгүй төлөвт орох магадлал энэ тохируулгатай
 			байхад илүү байдаг.</para>
 
 		  <para>Хэрэв <filename>/usr/obj</filename> нь энэ файлын систем
 			дээрх цорын ганц зүйл бол энэ асуудал биш юм. Хэрэв танд уг файлын
 			систем дээр өөр, үнэтэй өгөгдөл байгаа бол энэ тохируулгыг
 			идэвхжүүлэхээсээ өмнө өөрийн нөөц чинь шинэ эсэхийг шалгаарай.</para>
 		</warning>
 
 		<screen>&prompt.root; <userinput>mount -u -o async /usr/obj</userinput></screen>
 
 		<warning>
 		  <para>Дээр дурдсан шиг хэрэв <filename>/usr/obj</filename> нь
 			өөрийн файлын систем дээр биш байх юм бол жишээн дээрхийг
 			тохирох холболт хийх цэгийн нэрээр солиорой.</para>
 		</warning>
 	      </listitem>
 	    </itemizedlist>
 	  </answer>
 	</qandaentry>
 
         <qandaentry>
           <question>
             <para>Хэрэв ямар нэг юм буруутвал би юу хийх вэ?</para>
           </question>
 
           <answer>
             <para>Таны орчинд өмнөх бүтээлтүүдийн үеийн илүү үлдэгдлүүд
 		байхгүйд үнэхээр итгэлтэй байх хэрэгтэй. Энэ нь их амархан
 		юм.</para>
 
             <screen>&prompt.root; <userinput>chflags -R noschg /usr/obj/usr</userinput>
 &prompt.root; <userinput>rm -rf /usr/obj/usr</userinput>
 &prompt.root; <userinput>cd /usr/src</userinput>
 &prompt.root; <userinput>make cleandir</userinput>
 &prompt.root; <userinput>make cleandir</userinput></screen>
 
             <para>Тиймээ, <command>make cleandir</command> тушаалыг үнэндээ
 		хоёр удаа ажиллуулах шаардлагатай.</para>
 
             <para>Тэгээд <command>make buildworld</command>
 		тушаалыг эхлүүлж бүх процессийг дахин эхлүүл.</para>
 
             <para>Хэрэв та асуудалтай хэвээр байгаа бол алдаа болон
 		<command>uname -a</command> тушаалын дүнг &a.questions;
 		уруу явуулаарай. Өөрийн тохиргооныхоо талаар бусад асуултанд
 		хариулахад бэлэн байгаарай!</para>
           </answer>
         </qandaentry>
       </qandaset>
     </sect2>
   </sect1>
 
   <sect1 id="make-delete-old">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Антон</firstname>
 	  <surname>Штеренлихт</surname>
 	  <contrib>Тэмдэглэгээ хийсэн </contrib>
 	</author>
       </authorgroup>
     </sect1info>
     <title>Хуучин файлууд, хавтаснууд болон сангуудыг устгах</title>
     <indexterm>
       <primary>Хуучин файлууд, хавтаснууд болон сангуудыг устгах</primary>
     </indexterm>
 
     <para>&os; хөгжүүлэлтийн явцад файлууд болон тэдгээрийн агуулга
       үе үе хуучирдаг.Тэдгээрийн үүрэг болон боломжууд өөр хаа нэгтээ
       хийгдсэн юм уу эсвэл сангийн хувилбарын дугаар өөрчлөгдсөн юм уу эсвэл
       системээс бүрмөсөн хасагдсанаас болоод тийм
       байж болох юм. Эдгээрт хуучин файлууд, сангууд болон хавтаснууд
       ордог бөгөөд эдгээрийг системийг шинэчлэхдээ устгах ёстой. Энэ нь
       хэрэглэгчийн хувьд хадгалах (болон нөөц) төхөөрөмж дээр хэрэгцээгүй
       зай эзлээд байгаа хуучин файлуудаар систем дүүрэхгүй байх ашигтай  юм.
       Үүнээс гадна хуучин сан аюулгүй байдлын болон найдвартай ажиллагааны
       хувьд асуудалтай байсан бол та өөрийн системийг аюулгүй болгож хуучин
       сангаас болоод ажиллахаа болиод байсан асуудлаас сэргийлэхийн тулд
       шинэ сан руу шинэчлэх хэрэгтэй.
       Хуучин гэгдсэн файлууд, хавтаснууд, сангуудын жагсаалт
       <filename>/usr/src/ObsoleteFiles.inc</filename> файлд байдаг.
       Дараах заавар нь системийг шинэчлэх явцад хуучин файлуудыг устгахад
       туслах болно.</para>
 
     <para>Таныг  <xref
       linkend="canonical-build"/>-д заасны дагуу явж байгаа гэж энд үзнэ.
 	<command>make
       <maketarget>installworld</maketarget></command> болон дараагийн
 	<command>mergemaster</command> тушаал амжилттай хэрэгжсэний
 	дараа дараах маягаар та хуучин файлууд болон сангуудыг шалгах
 	ёстой:</para>
 
     <screen>&prompt.root; <userinput>cd /usr/src</userinput>
 &prompt.root; <userinput>make check-old</userinput></screen>
 
     <para>Хэрэв ямар нэг хуучин файл олдвол дараах тушаал
       ашиглан тэдгээрийг устгаж болно:</para>
 
     <screen>&prompt.root; <userinput>make delete-old</userinput></screen>
 
     <tip>
       <para>Түлхүүр үгсийн талаар дэлгэрэнгүйг сонирхож байгаа бол <filename>/usr/src/Makefile</filename>
         файлыг үзнэ үү.</para>
     </tip>
 
     <para>Хуучин файл бүрийг устгахын өмнө асууж хариулах дэлгэц гарна.
       Та энэ дэлгэцийг өнгөрөөж систем эдгээр файлуудыг автоматаар устгахаар
       тохируулахын тулд <makevar>BATCH_DELETE_OLD_FILES</makevar> хувьсагчийг
       дараах байдлаар ашиглана:</para>
 
       <screen>&prompt.root; <userinput>make -DBATCH_DELETE_OLD_FILES delete-old</userinput></screen>
 
       <para>Мөн энэ зорилгод хүрэхийн тулд
       доорхитой адилаар эдгээр тушаалд <command>yes</command> өгч хүрч болно:</para>
 
     <screen>&prompt.root; <userinput>yes|make delete-old</userinput></screen>
 
     <warning>
       <title>Анхааруулга</title>
         <para>Хуучин файлуудыг устгах нь тэдгээр хуучин файлуудаас
 	  хамааралтай програмуудыг ажиллахгүй болгоно.
 	  Энэ нь ялангуяа хуучин сангуудын хувьд үнэн байдаг.
 	  Ихэнх тохиолдолд та <command>make
        <maketarget>delete-old-libs</maketarget></command> тушаалыг биелүүлэхээсээ
 	  өмнө хуучин сан ашиглаж байсан програмууд, портууд эсвэл сангуудыг
 	  дахин бүтээх хэрэгтэй.</para>
     </warning>
 
     <para>Хуваалцсан сангуудаас хамааралтай эсэхийг шалгадаг хэрэгслүүд
       <filename role="package">sysutils/libchk</filename> эсвэл
       <filename role="package">sysutils/bsdadminscripts</filename> зэрэг портын
       цуглуулгад байдаг.</para>
 
     <para>Хуучин хуваалцсан сангууд нь шинэ сангуудтай зөрчилдөж болох
       бөгөөд доорх шиг алдаа өгч болно:</para>
 
     <screen>/usr/bin/ld: warning: libz.so.4, needed by /usr/local/lib/libtiff.so, may conflict with libz.so.5
 /usr/bin/ld: warning: librpcsvc.so.4, needed by /usr/local/lib/libXext.so, may conflict with librpcsvc.so.5</screen>
 
     <para>Эдгээр асуудлуудыг шийдэхийн тулд уг санг аль порт суулгасныг
       олно:</para>
 
     <screen>&prompt.root; <userinput>pkg_info -W  /usr/local/lib/libtiff.so</userinput>
 /usr/local/lib/libtiff.so was installed by package tiff-3.9.4
 &prompt.root; <userinput>pkg_info -W /usr/local/lib/libXext.so</userinput>
 /usr/local/lib/libXext.so was installed by package libXext-1.1.1,1</screen>
 
     <para>Дараа нь уг портыг deinstall хийгээд дахин бүтээж суулгах
       хэрэгтэй. Энэ явцыг автоматжуулахын тулд <filename
       role="package">ports-mgmt/portmaster</filename> болон <filename
       role="package">ports-mgmt/portupgrade</filename>
       хэрэгслийг ашиглаж болно. Бүх портуудыг дахин бүтээсэн гэдэгтээ
       итгэлтэй болсны дараа хуучин сангуудыг ашиглах хэрэггүй бөгөөд тэдгээрийг
       дараах тушаал ашиглан устгаж болно:</para>
 
     <screen>&prompt.root; <userinput>make delete-old-libs</userinput></screen>
   </sect1>
 
   <sect1 id="small-lan">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Майк</firstname>
 	  <surname>Мэйэр</surname>
 	  <contrib>Хувь нэмэр болгон оруулсан </contrib>
 	</author>
       </authorgroup>
     </sect1info>
     <title>Олон машины хувьд дагах нь</title>
     <indexterm>
       <primary>NFS</primary>
       <secondary>олон машин суулгах нь</secondary>
     </indexterm>
 
     <para>Хэрэв та олон машинуудын хувьд ижил эх модыг дагахыг хүсэж бүгдийн хувьд
 	эхийг татан авахуулж бүгдийг дахин бүтээхийг хүсэж байгаа бол энэ нь дискний зай,
 	сүлжээний зурвасын өргөн болон
 	CPU циклүүд зэрэг эх үүсвэрүүдийг үр ашиггүйгээр ашиглахад хүргэхээр санагдаж
 	болох юм. Тиймээ, үүний шийдэл нь нэг машинаар ихэнх ажлыг хийлгэж
 	бусад машинууд нь тэр ажлыг NFS-ээр дамжуулан холбох явдал юм. Энэ хэсэгт
 	ингэж хийх аргыг тайлбарсан.</para>
 
     <sect2 id="small-lan-preliminaries">
       <title>Бэлтгэл ажлууд</title>
 
       <para>Эхлээд хоёртын адил файлуудыг ажиллуулах <emphasis>build set буюу
 	бүтээх олонлог</emphasis> гэж бидний нэрлэх машинуудыг олох хэрэгтэй.
 	Машин бүр өөрчлөн тохируулсан цөмтэй байж болох бөгөөд гэхдээ тэд ижил хэрэглэгчийн
 	талбарын хоёртын файлуудыг ажиллуулж байх ёстой. Тэр олонлогоос
 	<emphasis>бүтээх машин</emphasis>ыг сонгох хэрэгтэй. Энэ нь
 	ертөнц болон цөм бүтээгдэх машин байх юм. Туйлын хүслээр бол энэ
 	нь <command>make buildworld</command> болон
 	<command>make buildkernel</command> тушаалуудыг ажиллуулахад
 	хангалттай нөөц CPU бүхий хурдан машин байх хэрэгтэй. Та мөн
 	үйлдвэрлэлд ашиглахаас өмнө програм хангамжуудыг тест хийдэг
 	<emphasis>тест машин</emphasis> сонгохыг бас хүсэж болох юм.
 	Энэ нь удаан хугацаагаар унтраастай эсвэл зогссон байж болох машин <emphasis>байх
 	ёстой</emphasis>. Энэ нь бүтээх машин байж болох юм, гэхдээ заавал
 	биш юм.</para>
 
       <para>Энэ бүтээх олонлог дахь бүх машинууд нь өөр өөрийн машин дээрээсээ ижил цэг дээр
 	<filename>/usr/obj</filename> болон <filename>/usr/src</filename>-г
 	холболт хийх хэрэгтэй. Туйлын хүслээр бол энэ нь бүтээх машин дээрх хоёр өөр дискнүүд
 	байж болох бөгөөд гэхдээ эдгээр нь уг машин дээр  NFS холболт бас хийгдэж болохоор
 	байж болох юм. Хэрэв танд олон бүтээх олонлогууд байгаа бол
 	<filename>/usr/src</filename> сан нь нэг бүтээх машин дээр байрлаж
 	бусад дээр нь NFS холболт хийгдсэн байх юм.</para>
 
       <para>Төгсгөлд нь бүтээх олонлогийн бүх машинууд дээрх <filename>/etc/make.conf</filename>
 	болон <filename>/etc/src.conf</filename> файлууд бүтээх машиныхтай тохирч байгаа эсэхийг шалгаарай. Энэ нь бүтээх олонлогийн
 	машин бүрийн суулгах үндсэн системийн бүх хэсгүүдийг бүтээх машин хийх ёстой гэсэн
 	үг юм. Мөн бүтээх машин бүр өөрийн цөмийн нэрийг <filename>/etc/make.conf</filename>
 	файлд <makevar>KERNCONF</makevar> хувьсагчид заан өгөх ёстой бөгөөд бүтээх
 	машин бүр <makevar>KERNCONF</makevar> хувьсагчдаа өөрийн цөмийг эхэнд
 	оруулан дараа нь тэдгээрийг жагсаах ёстой байдаг. Бүтээх машин нь машин бүрийн
 	цөмийг бүтээхээр болох юм бол тэдгээрийн тохиргооны файлыг
 	<filename>/usr/src/sys/<replaceable>arch</replaceable>/conf</filename>
 	санд агуулсан байх шаардлагатай.</para>
     </sect2>
 
     <sect2 id="small-lan-base-system">
       <title>Үндсэн систем</title>
 
       <para>Одоо бүх юм ингэж хийгдсэний дараа та бүгдийг бүтээхэд бэлэн боллоо.
 	Бүтээх машин дээр <xref linkend="make-buildworld"/>-д тайлбарласны
 	дагуу цөм болон ертөнцийг бүтээ, гэхдээ юуг ч битгий суулгаарай. Бүтээлт
 	дууссаны дараа тест машин дээр дөнгөж саяхан бүтээсэн цөмөө суулга.
 	Хэрэв энэ машин нь <filename>/usr/src</filename>
 	болон <filename>/usr/obj</filename> сангуудыг NFS-ээр холболт хийх
 	гэж байгаа бол та ганц хэрэглэгчийн горимд дахин ачаалахдаа сүлжээг нээж
 	тэдгээрийг холбож өгөх хэрэгтэй. Үүнийг хамгийн хялбараар хийхийн тулд
 	олон хэрэглэгчийн горимд ачаалан <command>shutdown now</command>
 	тушаалыг ажиллуулж ганц хэрэглэгчийн горимд орох явдал юм. Тэгэж орсныхоо
 	дараа та шинэ цөм болон ертөнцийг суулгаж жирийн үедээ хийдэг
 	<command>mergemaster</command> тушаалыг ажиллуулж болно.
 	Ингэж дууссаныхаа дараа энэ машины хувьд ердийн олон хэрэглэгчийн
 	үйлдлүүдэд дахин ачаалж орно.</para>
 
       <para>Тест машин дээрх бүх зүйлс зөв ажиллаж байгааг мэдсэнийхээ дараа та
 	бүтээх олонлогийн бусад машин бүр дээр шинэ програм хангамж суулгахдаа
 	ижил процедурыг ашиглаарай.</para>
     </sect2>
 
     <sect2 id="small-lan-ports">
       <title>Портууд</title>
 
       <para>Үүнтэй адил санааг бас портуудын модонд ашиглаж болно. Эхний чухал
 	алхам бол нөгөө машин дээрх <filename>/usr/ports</filename> санг
 	бүтээх олонлогийн бусад машинууд дээр холбож өгөх явдал юм. Дараа нь та
 	<filename>/etc/make.conf</filename> файлыг distfiles
 	буюу түгээлтийн файлуудыг хуваалцахаар зөв тохируулж өгч болно.
 	Та <makevar>DISTDIR</makevar> хувьсагчийг таны NFS холболтуудад заагдсан
 	аль ч <username>root</username> хэрэглэгчийн хувьд бичигдэх боломжтой байх
 	нийтлэг хуваалцсан сангаар тохируулах шаардлагатай.
 	Машин бүр <makevar>WRKDIRPREFIX</makevar> хувьсагчийг локал
 	бүтээх сангаар зааж өгөх хэрэгтэй. Эцэст нь хэрэв та багцуудыг бүтээж түгээх
 	гэж байгаа бол <makevar>PACKAGES</makevar> хувьсагчийг
 	<makevar>DISTDIR</makevar> хувьсагчийн нэгэн адил сангаар зааж өгөх
 	хэрэгтэй.</para>
     </sect2>
   </sect1>
 </chapter>
diff --git a/zh_CN.GB2312/articles/contributing/article.xml b/zh_CN.GB2312/articles/contributing/article.xml
index 4309e0c9bc..ba80c2c4cd 100644
--- a/zh_CN.GB2312/articles/contributing/article.xml
+++ b/zh_CN.GB2312/articles/contributing/article.xml
@@ -1,510 +1,505 @@
 <?xml version="1.0" encoding="gb2312"?>
 <!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.5-Based Extension//EN"
 	"../../../share/xml/freebsd45.dtd">
 
 <!--
      The FreeBSD Documentation Project
      The FreeBSD Chinese (Simplified) Documentation Project
 
      Original Revision: 1.511
 -->
 
 <article lang='zh_cn'>
   <articleinfo>
     <title>Ϊ FreeBSD �ṩ����</title>
 
     <abstract>
       <para>��������Ϊ���˻�����֯�����������ϣ��ΪFreeBSD��Ŀ�ṩ������
         �������ڱ������ҵ����ʵķ�����</para>
     </abstract>
 
     <authorgroup>
       <author>
 	<firstname>Jordan</firstname>
 	<surname>Hubbard</surname>
 	<contrib>ԭ��</contrib>
       </author>
     </authorgroup>
 
     <legalnotice id="trademarks" role="trademarks">
       &tm-attrib.freebsd;
       &tm-attrib.ieee;
       &tm-attrib.general;
     </legalnotice>
 
     <pubdate>$FreeBSD$</pubdate>
 
     <releaseinfo>$FreeBSD$</releaseinfo>
 
   </articleinfo>
 
    <indexterm><primary>���� </primary></indexterm>
 
   <para>��ϣ���� FreeBSD ��Ŀ����ʲô�� ̫���ˣ� ���ǻ�ӭ���� FreeBSD ����
     <emphasis>����</emphasis> ����û��Ĺ��ײŵ��Է�չ׳��ġ�
     ���Dz����dz���л�������Ĺ��ף����ң���Щ�������� FreeBSD �ij�����չҲ������Ҫ��</para>
 
   <para>Ҳ����������IJ�ͬ�� ���Ȳ�����һ����ɫ�ij���Ա�� Ҳ�����
     FreeBSD �����Ŷӳ�Ա�кܺõ�˽���� ���ǻ�һ��ͬ�ʵĶԴ����Ĺ�����
     FreeBSD �Ŀ�����Ա�鲼ȫ�� ��Ҽ���ר�����죬 ����ֲ�Ҳ�dz��㷺��
     ÿ�죬 ���Ƕ�����Գ��������Ĺ���������û���㹻�����֣�
     ���������ʱ��ӭ���İ�����</para>
 
   <para>FreeBSD ��Ŀ��������һ�������IJ���ϵͳ������
     ����ֻ��һ���ں˻���һЩ��ɢ�Ĺ��߰��� ��ˣ� ���ǵ�
     <filename>TODO</filename> �����б���������ָ����Ĺ�����
     ���ĵ����û����ԡ���ʾ�� ��ϵͳ��װ����͸߶�רҵ���ں˿�����
     ����������ļ���ˮƽ��Σ� ���º������� �����԰��������Ŀ��</para>
 
   <para>���ǹ������º� FreeBSD ��ع�������ҵ��������ϵ��
     ����ҪһЩ�������չ��ʹ���IJ�Ʒ��ת����ô��
     ���ᷢ�����Ǻ������Ӧ�������� �������ر�ϡ��Źֵġ�
     ���Ƿ���������ص���ֵҵ�� ���������������ɣ�
     ����Ҳ�����������е�ijЩ�����໥Э����
     ����������������Ŭ�����ƾ��еĹ������������� ���ۺ�ά���Ŀ��
     ����ϣ�������������ܸ���һ�λ��ᡣ</para>
 
   <sect1 id="contrib-what">
     <title>���ǵ�����</title>
 
     <para>�����г���һЩ��Ҫ��ɵ����������Ŀ��
       ���ǻ����Ͽ��Ա���ͬ�� <filename>TODO</filename>(�����б�)
       �б��� �Լ��û���Ҫ��</para>
 
     <sect2 id="non-programmer-tasks">
       <title>���ڽ����еķǿ�������</title>
 
       <para>�ܶ�μ�FreeBSD��Ŀ���˲��dz���Ա��
 	�����Ŀ�����ĵ�׫д�ߡ� ��ҳ���ʦ�� �Լ�����֧����Ա��
 	������Щ־Ը����˵�� ����ֻ��Ҫ����һЩʱ�䣬
 	���Ҿ���ѧϰ����Ը��</para>
 
       <orderedlist>
 	<listitem>
 	  <para>�����Ծ���ͨ��FAQ���ֲᣬ ����������˷����Ľ��ͣ�
 	    �����ǹ�ʱ��֪ʶ�� ������ȫ����ȷ�ĵط��� ����������ǡ�
 	    �������˳�ְ����ǸĹ����Ǿ͸�����
 	    (SGML��ʵ������ѧ�� ������Ҳ��������ֱ���ύ
 	    ASCII �İ汾)��</para>
 	</listitem>
 
 	<listitem>
 	  <para>�������ǰ� FreeBSD �ĵ����������ĸ�
 	    �������ĸ��汾�Ѿ������ˣ�
 	    ��Ҳ���Է���һЩ�������ĵ����߼����Щ���е��ĵ��Ƿ������¸��¹��ġ�
 	    �������ȼ򵥿��� FreeBSD �ĵ��ƻ����й� <ulink
 	    url="&url.books.fdp-primer;/translations.html">����ij�������</ulink>��
 	    �μӷ��빤��������˵��Ҫ�¾���ս�������е� FreeBSD �ĵ���
 	    ��Ϊһ��־Ը�ߣ� �����ٹ�����ȫȡ����������Ը�� һ��ij���˿�ʼ�����ˣ�
 	    �����˼���һ������뵽��Щ����������
 	    �����ֻ�����޵�ʱ����߾���ȥ���벿���ĵ���
 	    ����������ȥ���밲װָ�ϡ�</para>
 	</listitem>
 
 	<listitem>
 	  <para>�Ķ� &a.questions; ��ż����һ�� &ng.misc;
 	    (�����й��ɵ�������)�� ����˷�������רҵ֪ʶ��
 	    ���������ǽ��������һ���������õ����飻
 	    ��Щʱ�����������������������ѧ��һЩ�¶�����
 	    ��Щ��̳��ʱҲ��Ϊ���ṩһЩ�м�ֵ�����⡣</para>
 	</listitem>
       </orderedlist>
     </sect2>
 
     <sect2 id="ongoing-programmer-tasks">
       <title>���ڽ��еĿ�������</title>
         <para>��������Ĵ󲿷�������Ҫ��Ͷ��ɹ۵�ʱ�䣬
         ������Ҫ���� FreeBSD �ں˷����зḻ��֪ʶ�� �������߶�Ҫ��
         ��Ȼ����Ҳ�кܶ���Ҫ������Ҳ����һ��
         <quote>��ĩ������Ա</quote> �Ϳ��Ը��ꡣ</para>
 
       <orderedlist>
 	<listitem>
 	  <para>������������� FreeBSD-CURRENT �汾������һ�����ٵ�
 	    Internet������·�� �����Է��� <hostid
 	    role="fqdn">current.FreeBSD.org</hostid>��
 	    ����ÿ�����һ���°汾 &mdash; ������пգ�
 	    �����Ը������������һ�ݲ��Ұ�װ����
 	    ����������ʲô���⣬��������ǡ�</para>
 	</listitem>
 
 	<listitem>
 	  <para>�Ķ� &a.bugs;�� �����ܻ�Ϊ��Щ�����ṩ���н�������������ۣ�
 	    ���߰�æ����һЩ������ ���⣬
 	    ���������Գ����������е�һЩ���⡣</para>
 	</listitem>
 
 	<listitem>
 	  <para>�����֪����һЩ�����Ѿ��� -CURRENT �ϳɹ��ؽ��У�
 	    ���ھ���һ��ʱ��֮����Ȼû�кϲ��� -STABLE
 	    (ͨ���� 2������)�� ����ص� committer ��һ����ò����ʾ�š�</para>
 	</listitem>
 
 	<listitem>
 	  <para>���������������뵽Դ�����е�
 	    <filename class="directory">src/contrib</filename> Ŀ¼��</para>
 	</listitem>
 
 	<listitem>
 	  <para>ȷ�� <filename class="directory">src/contrib</filename>
 	    �еĴ��������µ�</para>
 	</listitem>
 
 	<listitem>
 	  <para>�Ը��ߵľ��漶�𹹽�Դ���� (��һ����Դ����)
 	    ��������Щ���档</para>
 	</listitem>
 
 	<listitem>
 	  <para>������Щ�� ports ��ʹ�ù�ʱ�Ķ�����
 	    ���� <function>gets()</function> �����
 	    <filename>malloc.h</filename> �������ľ��档</para>
 	</listitem>
 
 	<listitem>
 	  <para>����������� ports�� ��������һЩ���
 	    &os; �ĸĶ��� �����IJ������ظ�ԭ����
 	    (�����´�����ʱ���Ĺ�����������һЩ)��</para>
 	</listitem>
 
 	<listitem>
 	  <para>��ȡһ����ʽ�ı�׼�� �� &posix; �ĸ�����
 	    �������� <ulink
 	    url="&url.base;/projects/c99/index.html">FreeBSD
 	    C99 &amp; POSIX ��׼˳Ӧ��Ŀ</ulink> ��վ�ϵõ���ص����ӡ�
 	    �� FreeBSD ����Ϊͬ��׼���бȽϡ� ������׼��ͬ��
 	    �ر�����Щϸ�ڵط���΢С���죬 �뷢��һ���������� PR (���ⱨ��)��
 	    ������ܣ� ��ָ������������� ���� PR �ύ������
 	    �������Ϊ��׼�����⣬
 	    �����׼������Ҫ�����������µĿ��ǡ�</para>
 	</listitem>
 
 	<listitem>
 	  <para>Ϊ����б������������ݣ�</para>
 	</listitem>
       </orderedlist>
     </sect2>
 
     <sect2>
       <title>�鿴���� PR ���ݿ�</title>
 
       <indexterm><primary>���ⱨ�����ݿ�</primary></indexterm>
 
       <para><ulink
 	url="http://www.FreeBSD.org/cgi/query-pr-summary.cgi">FreeBSD
 	PR �б�</ulink> չʾ�����е�ǰ���ڻ�Ծ״̬�����ⱨ�棬 �Լ���
 	FreeBSD �û��ύ�ĸĽ����顣 PR
 	���ݿ�ͬʱ�����˿�����Ա�ͷǿ�����Ա������
 	�鿴��Щ��δ����� PR�� �������Ƿ���������Ȥ������
 	�����п�����һЩ�Ƿdz��򵥵����⣬
 	ֻ��Ҫ��һ����ȷ�� PR ����ȷ�ġ� ����һЩ���ܻ�dz����ӣ�
 	������ȫû�а����κ�������</para>
 
       <para>���ȿ�һ����Щ��û���˽��ֵ� PR��
 	��� PR �Ѿ�������������ˣ� �������������ܹ������ģ�
 	�����Ը��Ǹ��˷��ţ� ��ѯ�����Ƿ�����ṩ���� &mdash;
 	���ǿ����Ѿ����˿ɹ����ԵIJ����� ����һЩ�ɹ����۵������</para>
     </sect2>
 
     <sect2>
       <title>�� <quote>����</quote> ��ҳ��������Ŀ</title>
 
       <para><ulink url="&url.base;/projects/ideas/">&os;
 	־Ը����Ŀ�͵����嵥</ulink> Ҳ���ṩ��Ը��Ϊ
 	&os; ��Ŀ�������׵����ǵġ�
 	�����嵥һֱ�ڱ����ڸ����ţ�
 	�����˶Գ���Ա�ͷdz���Ա���õ�ÿ����Ŀ����Ϣ��</para>
     </sect2>
   </sect1>
 
   <sect1 id="contrib-how">
     <title>����ṩ����</title>
 
     <para>�����Ľ�ϵͳ�����Ͽ��Է�Ϊ 5 �ࣺ</para>
 
     <sect2 id="contrib-general">
       <title>���󱨸��һ���ע��</title>
 
       <para>ͨ���� <emphasis>һ�������ϵ�</emphasis>
 	�����뷨�ͽ���Ӧ�÷��� &a.hackers;��
 	ͬ���أ� ������Щ��������Ȥ���� (��Ȼ��
 	����ͬʱ��Ҫ�ܹ����� <emphasis>������</emphasis> �ʼ���)
 	���Կ��Ƕ��� &a.hackers;��
 	�μ� <ulink
 	url="&url.books.handbook;/eresources.html#ERESOURCES-MAIL">FreeBSD
 	ʹ���ֲ�</ulink> ���˽��������ʼ��б���
 	�Լ������ʼ��б�����ϸ�����</para>
 
       <para>����������� bug ������Ҫ�ύijЩ�޸ģ�
 	��ͨ�� &man.send-pr.1; �����ʹ��
 	<ulink url="&url.base;/send-pr.html">���� WEB
 	���ύҳ��</ulink> ���ύ�� ��������д bug �����ÿһ�
 	һ����˵�� ���ǽ����� bug ������ֱ�Ӹ��ϲ����� ������������ 65KB��
 	�����������ֱ��Ӧ�õ�Դ�����ϣ� �������ڱ����
 	synopsis һ��д�� <literal>[PATCH]</literal>��
 	�ڸ�������ʱ�� �� <emphasis>��Ҫ</emphasis>
 	ͨ�����ƺ�ճ�������У� ��Ϊ��������� tab ��ɿո�
 	��������ܿ��ܾͲ������ˡ� ����������� 20KB �ܶ࣬
 	Ӧ���ǽ���ѹ�� (����ʹ�� &man.gzip.1; �� &man.bzip2.1;)
 	֮���� &man.uuencode.1; ���б���֮���ٷŽ��������ⱨ���С�</para>
 
       <para>һ�����汻�浵�� �����յ�һ��ȷ���ʼ��Լ�һ���¼�׷�ٱ�š�
 	�뱣�������ţ� ��Ϊ��������֮��ʹ�������ţ�
 	���ʼ��� &a.bugfollowup;
 	���ṩ���ڸ��¼��Ľ�һ����Ϣ�� ����Ҫ�����ǽ���ŷŵ��ʼ��ı����У�
 	����  <literal>"Re:
 	kern/3377"</literal>��
 	����ͬһ�������һ�������Ӧ��ͨ�����ַ�ʽ���ύ��</para>
 
       <para>�������һ��ʱ��֮����Ȼû���յ�ȷ���� (���� 3
 	������ 1 �ܣ� ��ȡ���������ʼ�����)
 	��������ij��ԭ���޷�ʹ�� &man.send-pr.1; ���
 	����Է��Ÿ� &a.bugs; Ҫ����˴�����������</para>
 
       <para>��μ� <ulink
   	url="&url.articles.problem-reports;/article.html">��ƪ����</ulink>
   	�˽����׫д�õ����ⱨ�档</para>
     </sect2>
 
     <sect2>
       <title>�����ĵ����޶�</title>
 
       <indexterm><primary>�ύ�ĵ�</primary></indexterm>
 
       <para>�����ĵ����޸��� &a.doc; ����顣
 	��μ� <ulink
 	url="&url.books.fdp-primer;/index.html">FreeBSD
 	�ĵ��ƻ���������</ulink> �����������ָ����
 	�밴�� <xref
 	linkend="contrib-general"/> �н��ܵķ���ʹ�� &man.send-pr.1;
 	�������µ��ĵ����߶��������ĵ������� (�����Ǻ�С�ĸĽ�Ҳ�ǻ�ӭ�ģ�)��</para>
     </sect2>
 
     <sect2>
       <title>��������Դ������޸�</title>
 
       <indexterm><primary>FreeBSD-CURRENT</primary></indexterm>
 
       <para>�����д����Ͻ����޸Ļ����ӹ�����ij�̶ֳ�������Ҫ���༼�ɵ����飬
 	���һ���������Ŀǰ FreeBSD �Ŀ�����״���˽��йء�
 	�ж��ַ�ʽ���Եõ������� <quote>FreeBSD-CURRENT</quote>
 	�� FreeBSD �����汾�� ������ͨ�������˽�����Ŀ��������
 	��μ� <ulink url="
 	&url.books.handbook;/current-stable.html">FreeBSD
 	ʹ���ֲ�</ulink> ���˽�ʹ�� FreeBSD-CURRENT �Ľ�һ�����顣</para>
 
       <para>�ھɵĴ����Ͻ����޸ģ� ��ͨ���������ڴ����Ѿ���ʱ��
 	�����µĿ����汾����̫����޷������¼��ɵ� FreeBSD �С�
 	����������� &a.announce; �Լ� &a.current; �ʼ��б���
 	�����ͨ�������������˽�Ŀǰ�Ŀ���״̬��</para>
 
       <para>����˵���ܹ����ھ������µĴ�������������޸ģ�
 	����һ��Ҫ����������������������е��޸ĵIJ����ļ���
 	���������� FreeBSD ��ά����Ա�� ���������ͨ�� &man.diff.1;
 	��������ɡ�</para>
 
       <para>�ύ����ʱ�Ƽ��� &man.diff.1; ��ʽ��һ�²��� (unified diff)��
         ������ͨ�� <command>diff
         -u</command> �����ɡ� ������ ������޸��˴����Ĵ��룬
         ��ʹ�� <command>diff -c</command> �����ɵ������ĸ�ʽ (context diff)
         �IJ�����ܸ������Ķ��� ����Ƽ�ʹ�á�</para>
 
       <indexterm>
         <primary><command>diff</command></primary>
       </indexterm>
 
       <para>���磺</para>
 
       <screen>&prompt.user; <userinput>diff -c oldfile newfile</userinput></screen>
 
       <para>����</para>
 
       <screen>&prompt.user; <userinput>diff -c -r olddir newdir</userinput></screen>
 
       <para>���ֱ����ɸ����ļ���Ŀ¼�ṹ�� context diff��</para>
 
       <para>���Ƶأ�</para>
 
       <screen>&prompt.user; <userinput>diff -u oldfile newfile</userinput></screen>
 
       <para>��</para>
 
       <screen>&prompt.user; <userinput>diff -u -r olddir newdir</userinput></screen>
 
       <para>��������ǰ������ƣ� �����õĸ�ʽ�� unified diff��</para>
 
       <para>��μ� &man.diff.1; �����ֲ��˽����ϸ�ڡ�</para>
 
       <para>һ����ʹ�� &man.diff.1; �����˲��켯 (����ʹ��
 	&man.patch.1; ����������һ��)�� �Ϳ����ύ���ǣ�
 	�Ա㱻 FreeBSD ��¼�� ͨ��ʹ�� <xref linkend="contrib-general"/>
 	�������ܵ� &man.send-pr.1; ����Ϳ�������������
 	<emphasis>��Ҫ</emphasis> ֻ�ǰѲ��켯���� &a.hackers;��
 	�������ǿ��ܻᱻ������ ���ǻ�dz��м����ύ���޸�
 	(����һ��־Ը����Ŀ��)�� ��Ϊ���Ƕ���æ��
 	�����ʱ��һ���ܹ������������⣬ �� PR
 	���ݿ⽫һֱ��������Щ��¼��
 	���ֻҪ��������ʱ�����Ǿ��ܱ������ˡ�
 	����������ⱨ���а��������� һ����Ҫ�����ڱ�������
 	<literal>[PATCH]</literal> ��ǿ��һ�¡�</para>
 
       <indexterm>
         <primary><command>uuencode</command></primary>
       </indexterm>
 
       <para>�������Ϊ���� (���������ӡ� ɾ�������������ļ�)��
 	�����Կ���ʹ��
 	<command>tar</command> �����ļ������ Ȼ���� &man.uuencode.1;
 	�����롣 ����Ҳ��ӭ�� &man.shar.1; �����İ���</para>
 
       <para>��������޸Ŀ��ܴ���DZ�ڵ����飬 ���磬
 	����ȷ����֮��صİ�Ȩ���⣬ ���߸о���Ҫ�������ϸ�ĸ���ſ��Է������ǣ�
 	��Ӧֱ�ӷ��� &a.core;�� ������ͨ�� &man.send-pr.1; �����͡�
 	&a.core; ��һ��С�飬 ���Ա����Ĵ��� FreeBSD ���ճ�������
 	��Ҫע����ǣ� ���С��Ҳ��� <emphasis>��æ</emphasis>��
 	���ֻ���ڷdz���Ҫ��ʱ���Ӧ������д�š�</para>
 
       <para>��ο� &man.intro.9; �� &man.style.9; ���˽���ڱ���ϰ�ߺ�Լ�������顣
 	������˽���ЩԼ���� ���������˵���Ǽ���İ�����</para>
     </sect2>
 
     <sect2>
       <title>�´������Ҫ����ֵ������</title>
 
       <para>����������ṩ��ģ�ϴ�Ĵ��룬 ����Ϊ FreeBSD ������Ҫ���¹��ܣ�
 	����ܱ��뽫����ͨ�� uuencode ���б��룬 �򴫵�ij�� Web ��
 	FTP վ�㣬 �Ա��������ܹ��õ����� �����û�������ķ�������
 	�뵽��ص� FreeBSD �ʼ��б������ �����Ƿ�����Ը������������ǡ�</para>
 
       <para>���ڴ����Ĵ�����ԣ� ���ڰ�Ȩ������϶��ᱻ�����
 	FreeBSD ����ϵͳ���ܹ�ʹ�õİ�Ȩ����������</para>
 
       <orderedlist>
-  <indexterm><primary>BSD ��Ȩ����</primary></indexterm>
 	<listitem>
-	  <para>BSD ��Ȩ�� ����������ʹ��������Ȩ�Ĵ��룬
+	  <para>BSD<indexterm><primary>BSD ��Ȩ����</primary></indexterm> ��Ȩ�� ����������ʹ��������Ȩ�Ĵ��룬
 	    ��Ϊ�� <quote>�����Ӷ��������</quote>�� ������ܹ�������ҵ��ҵʹ�á�
 	    FreeBSD ����������ҵ��˾ʹ�����Ĵ��룬 �෴��
 	    ���ǻ����ع�����ҵ��˾ʹ�����ǵĴ��룬
 	    ��Ȼ�� ����������հ�һ���ִ������¾����� FreeBSD
 	    �͸����ˡ�</para>
 	</listitem>
 
 	<listitem>
-	  <indexterm><primary>GPL</primary><see>GNU General Public License</see></indexterm>
-
-	  <indexterm><primary>GNU General Public License</primary></indexterm>
-
-	  <para>GNU General Public License�� ���� <quote>GPL</quote>��
+	  <para>GNU General Public License��<indexterm><primary>GPL</primary><see>GNU General Public License</see></indexterm><indexterm><primary>GNU General Public License</primary></indexterm> ���� <quote>GPL</quote>��
 	    ���Dz����ܻ�ӭʹ��������Ȩ�Ĵ��룬
 	    ��Ϊ��ҵ��˾ʹ������Ҫ������Ĺ����� ������ ���ںܶ�ʹ��
 	    GPL ��Ȩ�Ĵ���Ŀǰ���޷������ (�������� �������
 	    �ı��Ű����ȵ�)�� �ܾ�ʹ�����в���������Ȩ�������Ǻܲ����ǵġ�
 	    ���� GPL ��Ȩ�Ĵ���ᱻ�ŵ�Դ�����һЩר�ŵ�λ�ã� ����
 	    <filename class="directory">/sys/gnu</filename> ��
 	    <filename class="directory">/usr/src/gnu</filename>��
 	    �Է�����Щʹ�� GPL ������ܻ�����Ǵ����������ʶ��</para>
 	</listitem>
       </orderedlist>
 
       <para>ʹ��������Ȩ�Ĵ����ڽ��� FreeBSD ֮ǰ���뾭�����صĸ���Ϳ��ǡ�
 	���ð����������Ƶ���ҵ��Ȩ�Ĵ��룬 һ����˵�ᱻ�ܾ���
 	�����ǹ�����Щ���������ͨ���Լ����������������ǡ�</para>
 
       <para>Ҫ�����ijɹ��ϼ��� <quote>BSDʽ</quote> �İ�Ȩ��
 	��������ı��ŵ�ÿһ��Դ�ļ����ʼ���֣�
 	�����ʵ��������滻 <literal>%%</literal> ֮������֡�</para>
 
       <programlisting>Copyright (c) %%proper_years_here%%
         %%your_name_here%%, %%your_state%%  %%your_zip%%.
 	All rights reserved.
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions
 are met:
 1. Redistributions of source code 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 binary form 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 SOFTWARE IS PROVIDED BY %%your_name_here%% ``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 %%your_name_here%% 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 SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
         &#36;Id&#36;</programlisting>
 
       <para>Ϊ�˷�������ʹ�ã� ��
 	<filename>/usr/share/examples/etc/bsd-style-copyright</filename>
 	Ҳ�����ҵ�����Ȩ�ĸ�����</para>
     </sect2>
 
     <sect2>
       <title>�ʽ� Ӳ���� Internet ����</title>
 
       <para>���Ƿdz�Ը����ܸ�����ʽ�ľ����� �Խ�һ����չ FreeBSD
 	Project ����ҵ�� ��Ϊ������֧�֣�
 	������������־Ը��Ŭ�����ܹ��и���ijɾͣ�
 	����Ӳ��Ҳ�dz���Ҫ�� ��Ϊ�����ܹ������������ӿ���֧�ֵ�Ӳ�����࣬
 	�������еĺܶ��˲�û���㹻���ʽ���������ЩӲ����</para>
 
       <sect3>
 	<title><anchor id="donations"/>���</title>
 
 	<para>FreeBSD �������һ����Ӫ���ġ� �п�˰����Ȩ�Ļ���ᣬ
 	  �������������Ŀ����Ϊ���� FreeBSD Project �ܹ���ɸ��ӳ�Զ��Ŀ�ꡣ
 	  ��Ϊ 501(c)3 ʵ�壬 һ����Ի������������Ͻ�������������˰��
 	  �Լ���������������˰�� ͨ�����ڿ�˰�����ʵ����о�����
 	  �����۵�����������Ӧ��˰���ֵĽ�</para>
 
 	<para>�����԰�֧Ʊ������
 	  <address>
 	    The FreeBSD Foundation
 	    <street>7321 Brockway Dr.</street>
 	    <city>Boulder</city>, <state>CO</state> <postcode>80303</postcode>
 	    <country>USA</country>
 	  </address>
 	</para>
 
 	<para>FreeBSD ��������ڿ���ͨ�� PayPal �����Ͻ��ܾ�
 	  �������������� ��������� <ulink
 	  url="http://www.freebsdfoundation.org">web
 	  վ��</ulink>��</para>
 
 	<para>���� FreeBSD �����ĸ������飬 ������ <ulink
 	  url="http://people.FreeBSD.org/~jdp/foundation/announcement.html">FreeBSD
 	  ����� -- ����</ulink> �ҵ��� Ҫ�������ᣬ
 	  �뷢�͵����ʼ���
 	  <email>bod@FreeBSDFoundation.org</email>��</para>
       </sect3>
 
       <sect3>
 	<title>����Ӳ��</title>
   <indexterm><primary>����</primary></indexterm>
 
 	<para>FreeBSD �ƻ���ӭ�κ��˾�������ʹ�õ�Ӳ����
 	  ���������Ȥ����Ӳ���� ����ϵ <ulink
 	  url="&url.base;/donations/">���������˰칫��</ulink>��</para>
       </sect3>
 
       <sect3>
 	<title>���� Internet ����</title>
 
 	<para>���ǻ�ӭ�µ� FTP�� WWW ��
 	  <command>cvsup</command> ���� �����ϣ����Ϊ�����ľ���
 	  ��μ� <ulink
 	  url="&url.articles.hubs;/index.html">���� FreeBSD ����</ulink>
 	  һ�ģ� ���˽��һ���������</para>
       </sect3>
     </sect2>
   </sect1>
 
 </article>
diff --git a/zh_CN.GB2312/books/handbook/boot/chapter.xml b/zh_CN.GB2312/books/handbook/boot/chapter.xml
index 67e51f1240..72edb0e0df 100644
--- a/zh_CN.GB2312/books/handbook/boot/chapter.xml
+++ b/zh_CN.GB2312/books/handbook/boot/chapter.xml
@@ -1,868 +1,864 @@
 <?xml version="1.0" encoding="gb2312"?>
 <!--
      The FreeBSD Documentation Project
      The FreeBSD Chinese (Simplified) Project
 
      Original Revision: r36653
      $FreeBSD$
 -->
 
 <chapter id="boot"> <title>FreeBSD ��������</title>
 
   <sect1 id="boot-synopsis"> <title>����</title>
   <indexterm><primary>����</primary></indexterm>
 
     <para>���������Լ����ز���ϵͳ�Ĺ��̱���Ϊ<quote>��������</quote>��
       ���߼��Ϊ<quote>����</quote>��
       FreeBSD ���������̸��û��Զ��������ṩ�˺ܴ�������ԣ�
       ������ѡ��������ͬ�IJ���ϵͳ��������ͬһϵͳ�IJ�ͬ�汾���ںˡ�</para>
     <para>���½���ϸ���������� FreeBSD �������������õ�����ѡ�
       ������������ںˡ�̽���豸������ &man.init.8; �ȵ�֮ǰ���������������顣
       ��Щ����һ�㷢�����ı��ɰױ��ʱ��</para>
 
     <para>��������������֪����</para>
 
     <itemizedlist>
       <listitem>
 	<para>FreeBSD ����ϵͳ��ĸ��������
 	  �Լ�����֮��Ľ�����ʽ.</para>
       </listitem>
 
       <listitem>
 	<para>�� FreeBSD ����ʱ�����������ѡ���Կ����������̡�</para>
       </listitem>
 
       <listitem>
 	<para> &man.device.hints.5;�Ļ���֪ʶ��</para>
       </listitem>
     </itemizedlist>
 
     <note>
       <title>ֻ������x86 </title>
 
       <para>����ֻ������������ Intel x86 ��ϵ֮�ϵ� FreeBSD ���������̡�</para>
     </note>
   </sect1>
 
   <sect1 id="boot-introduction">
     <title>��������</title>
 
     <para>�������Լ���������������ϵͳ������һ����Ȥ�����Ѿ��ء�
       ���ն����ڲ���ϵͳ������֮ǰ��������޷�����κ�����ģ��������д����ϵij���
       ����������û�в���ϵͳ������²������������ڴ����ϵij��������ϵͳ���Ƿ��ڴ����ϵģ�
       �Dz���ϵͳ������������أ�</para>
 
     <para>�� <citetitle>Munchausen�о����ռ� (The Adventures of
       Baron Munchausen)</citetitle> �Ȿ������һ��������������ƵĹ��£�
       һ���˵�������ˮ�ܵ�� Ȼ�������Լ���ѥ�� (bootstrap)
       �˷������������˳����� �����������У� ��������
       <firstterm>bootstrap</firstterm> ��ָ������ϵͳ�ļ��ػ��ƣ�
       ������𽥱���дΪ <quote>booting</quote>��</para>
 
     <indexterm><primary>BIOS</primary></indexterm>
 
     <indexterm><primary>��������/���ϵͳ</primary><see>BIOS</see></indexterm>
 
     <para>�� x86 Ӳ����ϵ�У���������/���ϵͳ (BIOS) ������ز���ϵͳ��
       Ϊ��������һ�㣬BIOS �ڴ�����Ѱ����������¼ (MBR)���� MBR
       �����ڷ��õĴ��̵��ض�λ�á�BIOS ���㹻����������������� MBR��
       �Ҽ�ʹ����Ϊ MBR ����ɼ��ز���ϵͳ��ʣ������
       MBR������ҪBIOS�İ�����</para>
 
     <indexterm><primary>Master Boot Record (MBR)</primary></indexterm>
 
     <indexterm><primary>Boot Manager</primary></indexterm>
 
     <indexterm><primary>Boot Loader</primary></indexterm>
 
     <para>��MBR�еĴ���ͨ������Ϊ<emphasis>����������</emphasis>��
       ���������û����������ࡣ��һ��������ͨ���и������λ�ڴ��̵�һ
       <emphasis>���</emphasis>���ڲ���ϵͳ���ļ�ϵͳ�С�
       (������������ʱҲ����Ϊ<emphasis>boot loader</emphasis>��
       ����FreeBSD�Ժ���������׶β�ʹ��������)
       �����������������<application>boot0</application>(���<application>Boot
       Easy</application>����׼�� &os; ����������)��
       <application>Grub</application>��<application>GAG</application>���Լ�
       <application>LILO</application>��
       (ֻ��<application>boot0</application>��װ�ý�MBR��)</para>
 
     <para>�����ֻ��װ��һ������ϵͳ����ôһ����׼�� MBR ���㹻�ˡ�
       ��� MBR ���ڴ�����������������(��ơ���ġ�)������
       Ȼ�����з����ϵĴ����Լ��ز���ϵͳ���������֡�
       MBR��&man.fdisk.8;��װ����һ��ȱʡ��MBR������ļ�Ϊ
       <filename>/boot/mbr</filename>��</para>
 
     <para>������ڴ����ϰ�װ�˶������ϵͳ��ô�����԰�װһ����ͬ��
       ������������������ʾһ�Ų���ϵͳ���б������ܴ���ѡ�������ĸ���
       ����������������������һС�������ۡ�</para>
 
     <para>����ϵͳ��ʣ�ಿ�ֱ���Ϊ�����׶Ρ���һ�׶���
       MBR ִ��,��ֻ��ʹ����������ض���״̬Ȼ��ִ�еڶ��׶Ρ�
       �ڶ��׶���΢�ɵö�һЩ�������׶���ɼ��ز���ϵͳ������
       ��������Ϊ�����׶�����Ϊ PC ��׼�Ե�һ�ڶ��׶�ִ�еij���Ĵ�С�������ơ�
       ����Щ��������һ��ʹ�� FreeBSD �����ṩ���������Եļ����� (loader)��</para>
 
     <indexterm><primary>�ں�</primary></indexterm>
     <indexterm><primary><command>init</command></primary></indexterm>
 
     <para>Ȼ���ں�����������ʼ̽���豸����ʼ�����ǡ�
       һ���ں�����������������ں˽�����Ȩ�����û����� &man.init.8;��
       ��ȷ�ϴ����Ƿ��ڿ���״̬��&man.init.8; Ȼ��ʼ�û�����Դ���ã�
       �����ļ�ϵͳ���������������Ե��������� FreeBSD
       ϵͳ����ʱ�������еĽ��̡�</para>
   </sect1>
 
   <sect1 id="boot-blocks">
     <title>�����������͸������׶�</title>
 
     <indexterm><primary>Boot Manager</primary></indexterm>
 
     <sect2 id="boot-boot0">
       <title>The Boot Manager</title>
       <indexterm><primary>��������¼ (MBR)</primary></indexterm>
 
       <para>��MBR�������������еĴ�����ʱ����Ϊ�������̵�
         <emphasis>�׶�0</emphasis>����һС�ڱ���ǰ���ᵽ�������е����֣�
         <application>boot0</application>��<application>LILO</application>��</para>
 
       <formalpara><title><application>boot0</application>������������</title>
          <para>�� FreeBSD �İ�װ�����Լ� boot0cfg(8) ����װ�� MBR��
           Ĭ�ϻ��� <filename>/boot/boot0</filename>��
           (����<application>boot0</application>�dz��򵥣�
           ������<abbrev>MBR</abbrev>�еij���ֻ����446�ֽڳ���
           ��������MBRĩ�˵�<literal>0x55AA</literal>��ʶҲҪ��ռһЩ�ռ䡣)
           ������Ѿ���װ<application>boot0</application>
           �����ж������ϵͳ�����Ӳ���ϣ�
           ��ô���������װ�� FreeBSD MBR ���Ұ�װ�˶������ϵͳ��
           �����ϵͳ����ʱ���������������ʾ��</para></formalpara>
 
       <example id="boot-boot0-example">
 	<title><filename>boot0</filename> ����</title>
 
 	<screen>F1 DOS
 F2 FreeBSD
 F3 Linux
 F4 ??
 F5 Drive 1
 
 Default: F2</screen>
       </example>
 
       <para>Ŀǰ�Ѿ�֪��һЩ��������ϵͳ���ر��� &windows;&nbsp;�� �����Լ���
 	MBR �������� MBR�� ����������������飬 ����������
 	FreeBSD �� MBR �������е� MBR��������ʹ�����µ����</para>
 
       <screen>&prompt.root; <userinput>fdisk -B -b /boot/boot0 <replaceable>device</replaceable></userinput></screen>
 
       <para><replaceable>device</replaceable> ��Ҫд�� MBR
 	���豸�������� <devicename>ad0</devicename>
 	������һ�� IDE ���̣�<devicename>ad2</devicename>
 	�����ڶ��� IDE �������ϵĵ�һ�� IDE ���̣�
 	<devicename>da0</devicename> ������һ�� SCSI ���̣��ȵȡ�
 	�ֻ��������Ҫһ���������õ�MBR����ʹ��&man.boot0cfg.8;��</para>
 
       <formalpara><title>The LILO Boot Manager:</title>
 
       <para>Ҫ�밲װ���������������Ҳ��������FreeBSD��
 	��������Linux����������ѡ����뵽���е������ļ�
 	<filename>/etc/lilo.conf</filename>��</para></formalpara>
 
       <programlisting>other=/dev/hdXY
 table=/dev/hdX
 loader=/boot/chain.b
 label=FreeBSD</programlisting>
 
       <para>������������ʹ��Linux�ı�ʾ��ָ����FreeBSD������������������
 	��<replaceable>X</replaceable>�滻ΪLinux��������ĸ��
 	��<replaceable>Y</replaceable>�滻ΪLinux�������š�
 	�����ʹ�õ��� <acronym>SCSI</acronym> ������������Ҫ��
 	<replaceable>/dev/hd</replaceable> �ij� <replaceable>/dev/sd</replaceable>��
 	�����ٴ�ʹ���� <replaceable>XY</replaceable> ���﷨��
 	�������װ������ϵͳ��ͬһ�������ϣ�<option>loader=/boot/chain.b</option>
 	ѡ�����ȥ��������������ִ�� <command>/sbin/lilo&nbsp;-v</command>
 	ʹ�޸���Ч��Ӧ�����Ļ�ϵ���Ϣȷ���޸ġ�</para>
     </sect2>
 
     <sect2 id="boot-boot1">
       <title>��һ�׶Σ�<filename>/boot/boot1</filename>���͵ڶ��׶Σ�
 	<filename>/boot/boot2</filename></title>
 
       <para>�����ϣ���һ���ڶ��׶�ͬ����һ�����򣬴��ڴ��̵���ͬ���򡣵����ڿռ����ƣ�
 	���DZ���Ϊ�����֡����������ǻ�һ��װ���ǡ������ɰ�װ����
 	<application>bsdlabel</application>(������)�����Ա���϶��ɵ�
 	<filename>/boot/boot</filename>��</para>
 
       <para>����λ���ļ�ϵͳ�⣬���������ĵ�һ������ӵ�һ������ʼ��������<link
 	linkend="boot-boot0">boot0</link>�����������������������
 	�����ҵ�һ���������У������������̡�
 	��ʹ�õ�����������<filename>/boot/boot</filename>�Ĵ�Сȷ����</para>
 
       <para><filename>boot1</filename> �dz��򵥣���Ϊ���ٶ�Ҳֻ���� 512 �ֽڣ�
 	ֻ��ʶ�𴢴��ŷ�����Ϣ�� <firstterm>bsdlabel</firstterm>��
 	��Ѱ��ִ�� <filename>boot2</filename>��</para>
 
       <para><filename>boot2</filename> ��΢�е��ǿ���ܹ����� FreeBSD
 	���ļ�ϵͳ�Ա���Ѱ��������ļ���
 	���ṩѡ���ں˺ͼ������ļ򵥽��档</para>
 
       <para>��Ϊ <link linkend="boot-loader">loader</link> ���Ÿ�ǿ�Ĺ��ܣ�
 	�ṩ��һ������ʹ�õ��������ã�<filename>boot2</filename> һ�㶼ִ�� loader��
 	����ǰ����������ֱ�������ںˡ�</para>
 
       <example id="boot-boot2-example">
 	<title><filename>boot2</filename> ����Ļ���</title>
 
 	<screen>&gt;&gt; FreeBSD/i386 BOOT
 Default: 0:ad(0,a)/boot/loader
 boot:</screen>
       </example>
 
       <para>�����Ҫ�����Ѱ�װ�� <filename>boot1</filename> ��
 	<filename>boot2</filename>����ʹ������
 	&man.bsdlabel.8;��</para>
 
       <screen>&prompt.root; <userinput>bsdlabel -B <replaceable>diskslice</replaceable></userinput></screen>
 
       <para><replaceable>diskslice</replaceable> �����������Ĵ��̺ͷ�����
 	���� <devicename>ad0s1</devicename>
 	������һ�� IDE �����ϵĵ�һ��������</para>
 
       <warning>
 	<title>dangerously dedicated</title>
 
 	<para>������� &man.bsdlabel.8; ������ֻʹ���˴�����������
 	  <devicename>ad0</devicename>���ͻ��ƻ������ϵ����з�����
 	  �⵱Ȼ��������ϣ���ģ������ڰ��� <keycap>�س�</keycap> ֮ǰ
 	  һ��Ҫ��������ж��ȷ�ϡ�</para>
       </warning>
     </sect2>
 
   <sect2 id="boot-loader">
     <title>�����׶Σ�<filename>/boot/loader</filename></title>
 
     <indexterm><primary>boot-loader</primary></indexterm>
     <para>������ (loader) �������׶��е����׶Σ�
       ���Ƿ������ļ�ϵͳ֮�еģ�һ�����ļ�
       <filename>/boot/loader</filename>��</para>
 
     <para>loader ����Ϊһ���Ѻõ����÷�ʽ��ʹ����һ���ڽ������õ������
       ��Щ������һ��ǿ��Ķ�Ľ�����֧�ֹ������䱾�����и��ӵö�������</para>
 
     <sect3 id="boot-loader-flow">
       <title>Loader ��������</title>
 
       <para>��ʼʱ��loader ��̽�����̨�ʹ��̣�ʶ���Ǵ��Ŀ��������ġ�
 	���������Щ��Ϣ���ñ�����
 	�����������Խ���ͨ���ű��򽻻���ʽ�������û����</para>
       <indexterm><primary>loader</primary></indexterm>
       <indexterm><primary>loader ����</primary></indexterm>
 
       <para>loader Ȼ����ȡ������ <filename>/boot/loader.rc</filename>��
 	Ĭ�ϵض�ȡ <filename>/boot/defaults/loader.conf</filename>
 	�����ÿɿ���Ĭ�ϱ�������ȡ <filename>/boot/loader.conf</filename>
 	����Щ�����������޸ġ�<filename>loader.rc</filename>
 	������Щ�������ж����������κα�ѡ���ģ����ںˡ�</para>
 
       <para>���Ĭ�ϵأ�loader ��ͣ�� 10 ��ȴ�������
 	��û�з����жϣ��Ϳ�ʼ�����ںˡ�������жϣ��û���õ�һ����������ʾ����
 	�������û��ø��ı�����ж������ģ�顢����ģ�顢�������
 	������������</para>
 
     </sect3>
 
     <sect3 id="boot-loader-commands">
       <title>Loader �ڽ�������</title>
 
       <para>��Щ����õ� loader ����.�����п�������Ľ�����μ�
 	&man.loader.8;��</para>
 
       <variablelist>
 	<varlistentry>
 	  <term>autoboot<replaceable>seconds</replaceable></term>
 
 	  <listitem>
 	    <para>�ڸ�����ʱ�������û���жϷ����������ںˡ�����ʾһ��������ʱ��
 	      Ĭ�ϵ�ʱ�䷶Χ�� 10 �롣</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>boot
 	    <optional><replaceable>-options</replaceable></optional>
 	    <optional><replaceable>kernelname</replaceable></optional></term>
 
 	  <listitem>
 	    <para>������ָ����ѡ������ָ�����ֵ��ں� (�����ָ���Ļ�)��
 	      ֻ������ִ�й� <emphasis>unload</emphasis>
 	      ����֮��ָ�����ں����ֲŻ���Ч��
 	      ���� �����Ľ�����ǰ�Ѿ����ص��ںˡ�</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>boot-conf</term>
 
 	  <listitem>
 	    <para>���ڱ����Ը���ģ������Զ����� (�������ں�ʱ������һ��)��
 	      ��ֻ���סҪ��ʹ�� <command>unload</command> ���
 	      Ȼ���޸�һЩ���������� <envar>kernel</envar>��</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>help
 	    <optional><replaceable>topic</replaceable></optional></term>
 
 	  <listitem>
 	    <para>��ʾ���ļ� <filename>/boot/loader.help</filename>
 	      ��ȡ�İ�����Ϣ����������������� <literal>index</literal>��
 	      ��ô�г����������п��õ����⡣</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>include <replaceable>filename</replaceable>
 	    &hellip;</term>
 
 	  <listitem>
 	    <para>ͨ���������ļ��������ļ����ļ������룬Ȼ��һ��һ�еؽ��͡�
 	      �κδ��󶼻�������ֹ include ���</para>
 	  </listitem>
 	</varlistentry>
 	<varlistentry>
 	  <term>load <optional><option>-t</option>
 	    <replaceable>type</replaceable></optional>
 	    <replaceable>filename</replaceable></term>
 
 	  <listitem>
 	    <para>�����ںˡ��ں�ģ�飬�����Ǹ������͵��ļ� (ͨ���������ļ���)��
 	      �κ����ļ�������IJ������ᱻ�����ļ���</para>
 	  </listitem>
 	</varlistentry>
 	<varlistentry>
 	  <term>ls <optional><option>-l</option></optional>
 	    <optional><replaceable>path</replaceable></optional></term>
 
 	  <listitem>
 	    <para>��ʾ����·�������Ǹ�Ŀ¼ (���·��û��ָ��) ������ļ��б���
 	      ���ָ���� <option>-l</option> ѡ��ļ���СҲ����ʾ��</para>
 	  </listitem>
 	</varlistentry>
 	<varlistentry>
 	  <term>lsdev <optional><option>-v</option></optional></term>
 
 	  <listitem>
 	    <para>�г����п��Լ���ģ����豸��
 	      ���ָ����<option>-v</option> ѡ�����ʾ�������ϸ�ڡ�</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>lsmod <optional><option>-v</option></optional></term>
 
 	  <listitem>
 	    <para>��ʾ�ѱ����ص�ģ�顣���ָ���� <option>-v</option> ѡ�
 	      ����ʾ�����ϸ�ڡ�</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>more <replaceable>filename</replaceable></term>
 
 	  <listitem>
 	    <para>��ʾָ�����ļ���ÿ�� <varname>LINES</varname> ͣ��һ�Ρ�</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>reboot</term>
 
 	  <listitem>
 	    <para>��������ϵͳ��</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>set <replaceable>variable</replaceable></term>
 	  <term>set
 	    <replaceable>variable</replaceable>=<replaceable>value</replaceable></term>
 
 	  <listitem>
 	    <para>���� loader �Ļ���������</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>unload</term>
 
 	  <listitem>
 	    <para>�Ƴ������ѱ����ص�ģ�顣</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
     </sect3>
 
     <sect3 id="boot-loader-examples">
       <title>Loader ʾ��</title>
 
       <para>������һЩʵ���� loader �÷���ʾ��</para>
 
       <itemizedlist>
-	<indexterm><primary>single-user mode</primary></indexterm>
 	<listitem>
-	  <para>ֻ�Ǽ򵥵�����Ĭ���ںˣ���ͬ���ǽ��뵥�û�ģʽ��</para>
+	  <para>ֻ�Ǽ򵥵�����Ĭ���ںˣ���ͬ���ǽ��뵥�û�ģʽ��<indexterm><primary>single-user mode</primary></indexterm></para>
 
 	  <screen><userinput>boot -s</userinput></screen>
 	</listitem>
 
 	<listitem>
 	  <para>ж��Ĭ���ں˺�ģ�飬Ȼ����ؾɵ� (��������) ���ںˣ�</para>
-    <indexterm>
-      <primary><filename>kernel.old</filename></primary>
-    </indexterm>
 
 	  <screen><userinput>unload</userinput>
 <userinput>load <replaceable>kernel.old</replaceable></userinput></screen>
 
 	  <para>������ʹ�ñ���Ϊͨ���ں˵� <filename>kernel.GENERIC</filename>��
-	    ��������ǰ��װ���ں� <filename>kernel.old</filename>
+	    ��������ǰ��װ���ں� <filename>kernel.old</filename><indexterm><primary><filename>kernel.old</filename></primary></indexterm>
 	    (�������������������Լ����ں˵�ʱ��)��</para>
 
 	  <note>
 	    <para>ʹ������������س��õ�ģ�����һ���ںˣ�</para>
 
 	    <screen><userinput>unload</userinput>
 <userinput>set kernel="<replaceable>kernel.old</replaceable>"</userinput>
 <userinput>boot-conf</userinput></screen></note>
 	</listitem>
 
 	<listitem>
 	  <para>�����ں����ýű���</para>
 
 	  <screen><userinput>load -t userconfig_script <replaceable>/boot/kernel.conf</replaceable></userinput></screen>
 	</listitem>
       </itemizedlist>
   </sect3>
 
       <sect3 id="boot-splash">
 	<sect3info>
 	  <authorgroup>
 	    <author>
 	      <firstname>Joseph J.</firstname>
 	      <surname>Barbish</surname>
 	      <contrib>Contributed by </contrib>
 	    </author>
 	  </authorgroup>
 	</sect3info>
 
         <title>����ʱ�� Splash ͼ��</title>
 
         <para>������ʱ���ֵ� splash ͼ�����ԭ����������Ϣ���ӿ��ӻ���
           ���ͼ�񽫱�ʼ����ʾ����Ļ��ֱ�����ֿ���̨�ĵ�¼��ʾ����
           X ��ʾ�������ṩ�˵�¼���档</para>
 
         <para>�� &os; ϵͳ�������������Ļ�����
           ��һ����Ĭ�ϴ�ͳ�Ŀ���̨�����л����� ��ϵͳ����֮��
           ���ڿ���̨�ϳ���һ����¼��ʾ�� �ڶ��������� X11
           ����ͼ�λ����� �ڰ�װ�� <link linkend="x-install">X11</link>
           ��һ��ͼ�� <link linkend="x11-wm">���滷��</link>��
           ���� <application>GNOME</application>��
 	  <application>KDE</application>�� ����
 	  <application>XFce</application>��
           X11 ��������� <command>startx</command> ��������</para>
 
         <para>����ͳ�����ַ��ĵ�¼��ʾ����Щ�û����ܸ�ϲ�� X11
           ͼ�λ��ĵ�¼���档 ͼ�λ��ĵ�¼��������
           &xorg; �� <application>XDM</application>��
           <application>GNOME</application> �� <application>gdm</application>��
           <application>KDE</application> �� <application>kdm</application>
           (�������� Port Collection �е�)
           �����϶��ṩ��һ��ͼ�λ��ĵ�¼����������̨�ϵĵ�¼��ʾ����
           �ڳɹ���¼֮�� ����չ�ָ��û�һ��ͼ�λ������档</para>
 
         <para>����������� splash
           ͼ������ʾ��¼��ʾ��֮ǰ������������ʱ�ļ����������������Ϣ��
           �� X11 ������ �û�������һ���Ӿ��ϸ�����ˬ�������飬
           ������ijЩ�� (&microsoft; &windows; ���߷� &unix; ���͵�ϵͳ)
           �û���ϣ�����鵽�ġ�</para>
 
 	<sect4 id="boot-splash-function">
 	  <title>Splash ͼ����</title>
 
           <para>Ŀǰ�� splash ͼ��Ĺ��ܽ�����֧�� 256 ɫ��λͼ
             (<filename>.bmp</filename>) ���� ZSoft
             <acronym>PCX</acronym> (<filename>.pcx</filename>) �ļ���
             ���⣬ splash ͼ���ļ��ķֱ��ʱ����� 320x200 ���ػ��߸��٣�
             �Ź����ڱ�׼ VGA ��������ʹ�á�</para>
 
           <para>Ҫʹ�óߴ�����ͼ�� �ﵽ���ֱ��� 1024x768 ���أ�
             ���迪�� &os; �� <acronym>VESA</acronym> ֧�֡�
             �����ͨ����ϵͳ����ʱ���� <acronym>VESA</acronym> ģ����ɣ�
             �������ں������ļ��м��� <literal>VESA</literal> ѡ�����
             (���� <xref linkend="kernelconfig"/>)�� <acronym>VESA</acronym>
             ֧�ָ������û���ʾ����������ʾ������������������</para>
 
           <para>��������ʱ�� splash ͼ��ͻᱻ��ʾ����Ļ�ϣ�
             ���������κ�ʱ�򶼰�������رա�</para>
 
           <para>Splash ͼ��ͬ��Ҳ���� X11 ֮��Ĭ�ϵ���Ļ������
             ��һ��ʱ������ú���Ļ���תΪ�����Եı任��ʾ splash ͼ��
             �������������� �ܶ���ʼ�� Ĭ�ϵ� splash ͼ�� (��Ļ����)
             ���� <filename>/etc/rc.conf</filename> �е�
             <literal>saver=</literal> ѡ����ơ�
             <literal>saver=</literal> ѡ����һЩ���õ���Ļ�����ɹ�ѡ��
             �������б������� &man.splash.4; �ֲ�ҳ���ҵ���
             Ĭ�ϵ���Ļ��������Ϊ <quote>warp</quote>��
             ��ע���� <filename>/etc/rc.conf</filename> ����ָ��
             <literal>saver=</literal> ѡ�����Ӧ�����������̨��
             ���� X11 ͼ�λ��ĵ�¼��������Ч��</para>
 
           <para>һЩ�й���������������Ϣ��
             ��������ѡ��˵���һ����ʱ������ʾ������������ʱ��ʾ��
             ���ǿ����� splash ͼ���ܡ�</para>
 
 	  <para>splash ͼ���ļ��������Դ� <ulink
 	      url="http://artwork.freebsdgr.org/node/3/">http://artwork.freebsdgr.org</ulink> ���ء�
 	    ��װ�� <filename
 	      role="package">sysutils/bsd-splash-changer</filename>
 	    port ֮�� ÿ��������ʱ����ܴӼ��������ѡ��
 	    splash ͼ��</para>
 	</sect4>
 
 	<sect4 id="boot-splash-enable">
           <title>���� Splash ͼ����</title>
 
           <para>Splash ͼ�� (<filename>.bmp</filename>) ����
             (<filename>.pcx</filename>) �ļ���������� root �����ϣ�
             ���� <filename class="directory">/boot</filename> Ŀ¼��</para>
 
           <para>����Ĭ�ϵ���ʾ�ֱ��� (256 ɫ��320x200 ���ػ����)
             �༭ <filename>/boot/lodaer.conf</filename>��
             �������µ����ã�</para>
 
 	  <programlisting>splash_bmp_load="YES"
 bitmap_load="YES"
 bitmap_name="<replaceable>/boot/splash.bmp</replaceable>"</programlisting>
 
           <para>���ڸ��ߵķֱ��ʣ������ 1024x768 ���أ�
             �༭ <filename>/boot/lodaer.conf</filename>��
             �������µ����ã�</para>
 
 	  <programlisting>vesa_load="YES"
 splash_bmp_load="YES"
 bitmap_load="YES"
 bitmap_name="<replaceable>/boot/splash.bmp</replaceable>"</programlisting>
 
           <para>������Щ���ü���
             <filename><replaceable>/boot/splash.bmp</replaceable></filename>
             Ϊ��Ҫ��ʹ�õ� splash ͼ�� ����Ҫʹ�� <acronym>PCX</acronym>
             �ļ���ʱ�� �������������ã� ���ݷֱ��ʵĸߵ�����
             <literal>vesa_load="YES"</literal>��</para>
 	  <programlisting>splash_pcx_load="YES"
 bitmap_load="YES"
 bitmap_name="<replaceable>/boot/splash.pcx</replaceable>"</programlisting>
 
           <para>�ļ��������������������е� <quote>splash</quote>��
             ���������κ����ƣ�ֻҪ�� <acronym>BMP</acronym> ����
             <acronym>PCX</acronym> ���͵��ļ��� ����
 	    <filename><replaceable>splash_640x400</replaceable>.bmp</filename>
             ����
 	    <filename><replaceable>blue_wave</replaceable>.pcx</filename>.</para>
 
           <para>һЩ��Ȥ�� <filename>loader.conf</filename> ѡ�</para>
 
 	  <variablelist>
 	    <varlistentry>
 	      <term><literal>beastie_disable="YES"</literal></term>
 
 	      <listitem>
                 <para>�⽫�ر���ʾ����ѡ��˵���
                   ���ǵ�����ʱ��Ȼ����֡� �����������˵�ѡ����õ�ʱ��
                   �ڵ�����ʱ�μ�����Ӧ������ѡ����Ȼ��Ч��</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term><literal>loader_logo="beastie"</literal></term>
 
 	      <listitem>
                 <para>�⽫�滻����ѡ��˵��Ҳ�Ĭ����ʾ��
                   <quote>&os;</quote> Ϊ��ɫ��Сħ����־��
                   ���������ķ��а�������</para>
 	      </listitem>
 	    </varlistentry>
 	  </variablelist>
 
           <para>����� &man.splash.4;�� &man.loader.conf.5; ��
             &man.vga.4; �ֲ�ҳ��ȡ������ϸ��Ϣ��</para>
 	</sect4>
       </sect3>
     </sect2>
   </sect1>
 
   <sect1 id="boot-kernel">
     <title>�ں�������ʱ�Ľ���</title>
     <indexterm>
       <primary>�ں�</primary>
       <secondary>��������</secondary>
     </indexterm>
 
     <para>һ���ں˱� <link
       linkend="boot-loader">loader</link> (һ�������) ���� <link
       linkend="boot-boot1">boot2</link> (Խ�� loader) ���أ�
       �������������־������еĻ����ͻ���б�Ҫ�Ķ���������</para>
 
     <sect2 id="boot-kernel-bootflags">
       <title>�ں�������־</title>
 
       <indexterm>
         <primary>�ں�</primary>
         <secondary>������־</secondary>
       </indexterm>
 
       <para>������һЩ���õ�������־��</para>
 
       <variablelist id="boot-kernel-bootflags-list">
 	<varlistentry>
 	  <term><option>-a</option></term>
 
 	  <listitem>
 	    <para>���ں˳�ʼ��ʱ��ѯ����Ϊ�����ص��豸��</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><option>-C</option></term>
 
 	  <listitem>
 	    <para>�� CDROM ������</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><option>-c</option></term>
 
 	  <listitem>
 	    <para>���� UserConfig (����ʱ���ں�������)</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><option>-s</option></term>
 
 	  <listitem>
 	    <para>�������뵥�û�ģʽ</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><option>-v</option></term>
 
 	  <listitem>
 	    <para>���ں�������������ʾ���е���Ϣ</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
 
       <note>
 	<para>���и����������־���Ķ� &man.boot.8;
 	  �Ի�ȡ�й����ǵ���Ϣ��</para></note>
     </sect2>
 
 <!--    <sect2 id="boot-kernel-userconfig">
       <title>UserConfig: ����ʱ���ں�������</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>
 
     <title>Device Hints</title>
 
     <indexterm>
       <primary>device.hints</primary>
     </indexterm>
 
     <para>�ڳ�ʼ��ϵͳ����ʱ��&man.loader.8; ���ȡ
       &man.device.hints.5; �ļ�������ļ��Ա�������ʽ�������ں�������Ϣ��
       ��ʱ����Ϊ <quote>device hints</quote>��
       �豸����������<quote>device hints</quote>
       ���豸�������á�</para>
 
     <para>Device hints Ҳ������ <link linkend="boot-loader">
       �����׶ε�boot loader</link> ����������ʾ����ָ��������������
       <command>set</command> �������ӣ�<command>unset</command> ����ɾ����
       <command>show</command> ����鿴�����ļ� <filename>/boot/device.hints</filename>
       ���õı�������������ﱻ���ǡ����� boot loader
       �еı������������Եģ����´�����ʱ�ͻᱻ���ǡ�</para>
 
     <para>һ��ϵͳ�����ɹ���&man.kenv.1; �����������������еı�����</para>
 
     <para>�ļ� <filename>/boot/device.hints</filename> ���﷨��һ��һ��������
       ʹ��<quote>#</quote>��Ϊע�ͱ�ǡ�
       ÿ���ǰ������·�ʽ��֯�ģ�</para>
 
     <screen><userinput>hint.driver.unit.keyword="<replaceable>value</replaceable>"</userinput></screen>
 
     <para>�����׶� boot loader ���﷨�ǣ�</para>
     <screen><userinput>set hint.driver.unit.keyword=<replaceable>value</replaceable></userinput></screen>
 
     <para><literal>driver</literal> ���豸������������<literal>unit</literal>
       ���豸��������λ����<literal>keyword</literal> �� hint �ؼ��֡�
       �ؼ��ֿ���������ѡ����ɣ�</para>
 
     <itemizedlist>
       <listitem>
 	<para><literal>at</literal>��ָ���豸���󶨵�����</para>
       </listitem>
 
       <listitem>
 	<para><literal>port</literal>��ָ����ʹ�� <acronym>I/O</acronym>
 	  ����ʼ��ַ��</para>
       </listitem>
 
       <listitem>
 	<para><literal>irq</literal>��ָ����ʹ�õ��ж�����š�</para>
       </listitem>
 
       <listitem>
 	<para><literal>drq</literal>��ָ�� DMA channel �š�</para>
       </listitem>
 
       <listitem>
 	<para><literal>maddr</literal>��ָ���豸ռ�õ������ڴ��ַ��</para>
       </listitem>
 
       <listitem>
 	<para><literal>flags</literal>�����豸���ø��ֱ�־λ��</para>
       </listitem>
 
       <listitem>
 	<para><literal>disabled</literal>�������� <literal>1</literal>��
 	  �豸�����á�</para>
       </listitem>
     </itemizedlist>
 
     <para>�豸���������ܹ����ܸ���� hints���Ƽ����ο����ǵ������ֲᡣ�ο�
       &man.device.hints.5;��&man.kenv.1;��&man.loader.conf.5; ��
       &man.loader.8; �����ֲ��Ի�ȡ�������Ϣ��</para>
   </sect1>
 
   <sect1 id="boot-init">
     <title>Init�����̿��Ƽ���ʼ��</title>
 
     <indexterm>
       <primary><command>init</command></primary>
     </indexterm>
 
     <para>һ���ں�������������Ͱѿ���Ȩ�������û�����
       &man.init.8;���������� <filename>/sbin/init</filename>��
       ���� <envar>init_path</envar> ����ָ���ij���·���С�
       ����������� <command>loader</command> �������õġ�</para>
 
     <sect2 id="boot-autoreboot">
       <title>�Զ���������</title>
 
       <para>�Զ��������̻�ȷ��ϵͳ�п��õ��ļ�ϵͳ���ڽ�����״̬��
 	������ǣ� ����ʹ�� &man.fsck.8; Ҳ�޷��޸���Щ���⣬
 	&man.init.8; ����� <link linkend="boot-singleuser">���û�ģʽ</link>
 	�Ա�ϵͳ����Աֱ��������Щ���⡣</para>
     </sect2>
 
     <sect2 id="boot-singleuser">
       <title>���û�ģʽ</title>
       <indexterm><primary>���û�ģʽ</primary></indexterm>
       <indexterm><primary>����̨</primary></indexterm>
 
       <para>��ģʽ����ͨ��
 	<link linkend="boot-autoreboot">�Զ���������</link> ����ͨ������
 	<option>-s</option> ѡ����û�������ͨ���� <command>loader</command>
 	������ <envar>boot_single</envar> �����ȶ��ַ�ʽ���ﵽ��</para>
 
       <para>Ҳ�����ڶ��û�ģʽ�µ��������� (<option>-r</option>) ѡ���ͣ��
 	(<option>-h</option>) ѡ��� &man.shutdown.8;
 	���������뵥�û�ģʽ��</para>
 
       <para>���ϵͳ <literal>����̨</literal> ���ļ�
 	<filename>/etc/ttys</filename> �б�����Ϊ
 	<literal>����ȫ(insecure)</literal>��
 	�ڳ�ʼ�����û�ģʽǰ�����Ҫ������ <username>root</username>
 	�������������ʾ����</para>
 
       <example id="boot-insecure-console">
 	<title>�� <filename>/etc/ttys</filename> �ļ��еIJ���ȫ����̨</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>�ѿ���̨���ó� <literal>����ȫ (insecure)</literal>
 	  ʹֻ֪�� <username>root</username> ������˲��ܽ��뵥�û�ģʽ��
 	  ��Ϊ����Ϊ����̨���������Dz���ȫ�ġ������������ǵ���ȫ�ԣ�
 	  ��ѡ�� <literal>����ȫ (insecure)</literal>������
 	  <literal>��ȫ (secure)</literal>��</para>
       </note>
     </sect2>
 
     <sect2 id="boot-multiuser">
       <title>���û�ģʽ</title>
       <indexterm><primary>���û�ģʽ</primary></indexterm>
 
       <para>��� &man.init.8; ���������ļ�ϵͳһ���������ֻ����û���<link
 	linkend="boot-singleuser">���û�ģʽ</link>����˹�����
 	ϵͳ�ͻ������û�ģʽ����ʼϵͳ����Դ���á�</para>
 
       <sect3 id="boot-rc">
 	<title>��Դ���� (rc)</title>
 
       <indexterm><primary>rc �ļ�</primary></indexterm>
 
 	<para>��Դ���÷ֱ���ļ� <filename>/etc/defaults/rc.conf</filename>��
 	  <filename>/etc/rc.conf</filename> �ж�ȡĬ�����ú�ϸ�����ã�
 	  Ȼ��������ļ� <filename>/etc/fstab</filename> ���ἰ���ļ�ϵͳ��
 	  �������������������ϵͳ�ػ����̣�����������ذ�װ���������ű���</para>
 
 	<para>&man.rc.8; �����ֲ��ǹ�����Դ���õĺܺõIJο���</para>
       </sect3>
     </sect2>
   </sect1>
 
   <sect1 id="boot-shutdown">
     <title>�ػ� (shutdown) ����</title>
     <indexterm>
       <primary><command>shutdown</command></primary>
     </indexterm>
 
     <para>������ &man.shutdown.8; �ķ���Ĺػ������У�
       &man.init.8; ���������� <filename>/etc/rc.shutdown</filename> �ű���
       �����н��̷��� <literal>TERM</literal> �źţ� ��������ʱֹͣ�Ľ��̷���
       <literal>KILL</literal> �źš�</para>
 
     <para>��֧�ֵ�Դ������ƽ̨�Ϲر� FreeBSD ϵͳ�ĵ�Դ�� ֻҪ�򵥵�ʹ������
       <command>shutdown -p now</command> ���ɡ� ���⣬ ����������
       <command>shutdown -r now</command> ������ FreeBSD�� Ҫִ�� &man.shutdown.8;
       �������� <username>root</username> �û��� <groupname>operator</groupname> ��ij�Ա��
       Ҳ����ʹ�� &man.halt.8; �� &man.reboot.8; �������ر�ϵͳ��
       ��ο����ǵ������ֲ��Ի�ø������Ϣ��</para>
 
     <note>
       <para>��Դ������Ҫ֧�֣� ��Ҫ���ں�֧��
 	&man.acpi.4; ����ģ����ʽ��������</para>
     </note>
 
   </sect1>
 </chapter>
diff --git a/zh_CN.GB2312/books/handbook/l10n/chapter.xml b/zh_CN.GB2312/books/handbook/l10n/chapter.xml
index 2975100ce9..63be4917f6 100644
--- a/zh_CN.GB2312/books/handbook/l10n/chapter.xml
+++ b/zh_CN.GB2312/books/handbook/l10n/chapter.xml
@@ -1,846 +1,843 @@
 <?xml version="1.0" encoding="gb2312"?>
 <!--
      The FreeBSD Documentation Project
      The FreeBSD Chinese Documentation Project
 
      Original Revision: 1.134
      $FreeBSD$
 -->
 
 <chapter id="l10n">
   <chapterinfo>
     <authorgroup>
       <author>
 	<firstname>Andrey</firstname>
 	<surname>Chernov</surname>
 	<contrib>Contributed by </contrib>
       </author>
     </authorgroup>
     <authorgroup>
       <author>
 	<firstname>Michael C.</firstname>
 	<surname>Wu</surname>
 	<contrib>Rewritten by </contrib>
       </author>
       <!-- 30 Nv 2000 -->
     </authorgroup>
   </chapterinfo>
 
   <title>���ػ���I18N/L10Nʹ�ú�����</title>
 
   <sect1 id="l10n-synopsis">
     <title>����</title>
 
     <para>FreeBSD��һ���ɷֲ���ȫ������û��͹�����֧�ֵ���Ŀ��
     ���½�����FreeBSD�Ĺ��ʻ��ͱ��ػ�������,������Ӣ���û�Ҳ��ʹ��FreeBSD�ܺõع�����
     ��ϵͳ��Ӧ��ˮƽ�ϣ���Ҫ��ͨ��ִ��i18N��׼��ʵ�ֵģ������������ǽ�Ϊ�����ṩ��ϸ�Ľ��ܡ�</para>
 
     <para>������һ�£������˽⣺</para>
     <itemizedlist>
       <listitem><para>��ͬ�����Ժ͵�����������ִ�����ϵͳ�Ͻ��б���ġ�
       </para></listitem>
       <listitem><para>���Ϊ���ĵ���shell���ñ��ػ���</para></listitem>
       <listitem><para>����������Ŀ���̨Ϊ��Ӣ�����ԡ�
       languages.</para></listitem>
       <listitem><para>���ʹ�ò�ͬ����������Ч��ʹ��X Windows��</para></listitem>
       <listitem><para>����������ҵ������йؿ�������i18N��׼��Ӧ�ó������Ϣ��</para></listitem>
    </itemizedlist>
 
     <para>�Ķ�����֮ǰ����Ӧ���˽⣺</para>
 
     <itemizedlist>
       <listitem><para>������װ����ĵ���������<xref linkend="ports"/>����</para></listitem>
     </itemizedlist>
   </sect1>
 
   <sect1 id="l10n-basics">
     <title>����֪ʶ</title>
 
     <sect2>
       <title>I18N/L10N ��ʲô��</title>
     <indexterm>
       <primary>���ʻ�</primary>
       <see>���ػ�</see>
     </indexterm>
     <indexterm><primary>���ػ�</primary></indexterm>
 
       <para>������Ա��internationalization��д��I18N,�м��������ǰ��������ĸ�����ĸ������
       L10N����<quote>localization</quote> ʹ��ͬ������������
       I18N/L10N������Э���Ӧ�ý����һ�������û�ʹ�������Լ���ѡ������ԡ�</para>
 
       <para>I18NӦ�ó���ʹ��I18N��������̡�������������Աдһ���򵥵��ļ���
       �Ϳ��Խ���ʾ�IJ˵����ı�����ɱ������ԡ����Ƿdz���������Ա��ѭ���ֹ���</para>
     </sect2>
 
     <sect2>
       <title>ΪʲôҪʹ��I18N/L10N?</title>
 
       <para>I18N/L10N��׼�ܹ��ܺõ�֧�����鿴�����������Ӣ�����ԡ�</para>
     </sect2>
 
     <sect2>
       <title>I18N֧����Щ���ԣ�</title>
 
       <para>I18N��L10N����FreeBSD���еġ���ǰ������֧�������Ͼ��󲿷��������ԣ�
       �����������ڣ����ģ����ģ����ģ������ģ����ģ����ģ�Խ���ĵȵȡ�</para>
     </sect2>
   </sect1>
 
   <sect1 id="using-localization">
     <title>ʹ�ñ��ػ�����</title>
 
     <para>I18N����FreeBSD���еģ�����һ���������ǹ���������FreeBSD������һ����</para>
     <indexterm><primary>locale</primary></indexterm>
 
     <para>���ػ�������Ҫ�߱��������������Դ��� (Language Code)�� ���Ҵ���
       (Country Code) �ͱ���(Encoding)�� �������ֿ�����������Щ���������죺</para>
 
     <programlisting><replaceable>���Դ���</replaceable>_<replaceable>���Ҵ���</replaceable>.<replaceable>����</replaceable></programlisting>
 
     <sect2>
       <title>���Ժ͹��Ҵ���</title>
       <indexterm><primary>���Դ���</primary></indexterm>
       <indexterm><primary>���Ҵ���</primary></indexterm>
 
       <para>Ϊ�����������������FreeBSDϵͳ���б��ػ�����������&unix;ϵͳ����
       �û�����Ҫ֪����Ӧ�Ĺ��Һ����Դ��루���Ҵ������Ӧ�ó���ʹ����һ�����Թ淶����
       ���⣬WEB�������SMTP/POP��������web�������ȶ��������Ϊ�����ġ��������һ�����Һ����Դ��������:
       </para>
 
       <informaltable frame="none" pgwide="1">
 	<tgroup cols="2">
 	  <thead>
 	    <row>
 	      <entry>����/���Ҵ���</entry>
 	      <entry>����</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry>en_US</entry>
 	      <entry>����Ӣ��</entry>
 	    </row>
 
 	    <row>
 	      <entry>ru_RU</entry>
 	      <entry>����</entry>
 	    </row>
 
 	    <row>
 	      <entry>zh_CN</entry>
 	      <entry>��������</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
 
     </sect2>
 
     <sect2>
       <title>����</title>
       <indexterm><primary>����</primary></indexterm>
       <indexterm><primary>ASCII</primary></indexterm>
 
       <para>һЩ���Բ�ʹ�� ASCII ���룬����ʹ��8-λ�� ������ֽڵ��ַ���
 	�������Ϣ��ο� &man.multibyte.3;��
 	�Ƚ��ϵ�Ӧ�ó�����ܻ��޷�ʶ�����ǣ� ������Ϊ�ǿ����ַ���
 	�Ƚ��µ�Ӧ�ó���ͨ�����ϳ� 8-λ�ַ��� ��ʵ�ֵIJ�ͬ��
 	�û����ܲ��ò���������ֽ��ַ�֧�ֱ���Ӧ�ó��� �����һЩ��������ã�
 	���ܹ�����ʹ�����ǡ� Ҫ����ʹ���������ֽ��ַ��� <ulink
 	url="&url.base;/ports/index.html">FreeBSD Ports Collection</ulink>
 	�Ѿ�Ϊÿ�������ṩ�˲�ͬ�ij��� ��ο����� FreeBSD Port �е� I18N
 	�ĵ���</para>
 
       <para>�ر���Ҫָ�����ǣ� �û�������Ҫ�鿴Ӧ�ó�����ĵ���
 	��ȷ�������ȷ���������� ����ҪΪ configure/Makefile/������
 	ָ��ʲô���IJ�����</para>
 
       <para>��ס������Щ:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>�ض����Եļ�C�ַ��� (�μ� &man.multibyte.3;)������
 	    ISO8859-1, ISO8859-15, KOI8-R, CP437��</para>
 	</listitem>
 
 	<listitem>
 	  <para>���ֽڻ���ֽڱ��룬��EUC, Big5��</para>
 	</listitem>
       </itemizedlist>
 
       <para>��������<ulink
 	url="http://www.iana.org/assignments/character-sets">IANA Registry</ulink>���һ�����е��ַ����б���</para>
 
       <note>
       <para>��˲�ͬ���ǣ� &os; ʹ���� X11-���ݵı��ر���ģʽ��</para>
       </note>
 
     </sect2>
 
     <sect2>
       <title>I18NӦ�ó���</title>
 
       <para>��FreeBSD Ports��Packageϵͳ���棬I18NӦ�ó����Ѿ�ʹ��<literal>I18N</literal>
       ��������Ȼ�����Dz�����֧����Ҫ�����ԡ�</para>
     </sect2>
 
     <sect2 id="setting-locale">
       <title>���ػ�����</title>
 
       <para>ͨ��ֻҪ�ڵ���shell��������<envar>LANG</envar>Ϊ���ػ���
       һ��ͨ�������û��� <filename>~/.login_conf</filename>
 	���û�shell�������ļ���<filename>~/.profile</filename>��<filename>~/.bashrc</filename>,
 	<filename>~/.cshrc</filename>����û�б�Ҫ����
 	<envar>LC_CTYPE</envar>��<envar>LC_CTIME</envar>��
 	�������Ϣ��ο��ض����Ե�FreeBSD�ĵ���</para>
 
       <para>��Ӧ�������������ļ���������������������</para>
 
       <itemizedlist>
-        <indexterm><primary>POSIX</primary></indexterm>
         <listitem>
-	  <para><envar>LANG</envar> Ϊ&posix;���ñ��ػ����Թ��ܡ�</para>
+	  <para><envar>LANG</envar> Ϊ&posix;���ñ��ػ����Թ��ܡ�<indexterm><primary>POSIX</primary></indexterm></para>
 	</listitem>
 
 	<listitem>
-	  <indexterm><primary>MIME</primary></indexterm>
-
-	  <para><envar>MM_CHARSET</envar>Ӧ�ó����MIME�ַ�����</para>
+	  <para><envar>MM_CHARSET</envar>Ӧ�ó����MIME�ַ�����<indexterm><primary>MIME</primary></indexterm></para>
 	</listitem>
       </itemizedlist>
 
       <para>������û���shell���ã��ض���Ӧ�����ú�X11���á�</para>
 
       <sect3>
 	<title>���ñ��ػ��ķ���</title>
         <indexterm><primary>���ػ�</primary></indexterm>
         <indexterm><primary>�������</primary></indexterm>
 
 	<para>�����ַ��������ñ��ػ�������������������
 	��һ�� (�Ƽ�) ������ <link linkend="login-class">�������</link>����ָ������������
 	�ڶ��ַ����ǰѻ��������ӵ�shell��<link linkend="startup-file">�����ļ�</link>���档
 	</para>
 
 	<sect4 id="login-class">
 	  <title>������෽��</title>
 
 	  <para>���ַ��������ѱ��ػ����ƺ�MIME�ַ����Ļ��������������ܵ�shell��
 	   �����Ǽӵ�ÿ���ض�shell�������ļ����档
 	   <link linkend="usr-setup">�û�������
 	    Level Setup</link> ������ͨ�û��Լ����������ã���<link
 	    linkend="adm-setup">����Ա������</link>��Ҫ�����û�Ȩ�ޡ�</para>
 
 	  <sect5 id="usr-setup">
 	    <title>�û�������</title>
 
 	    <para>����һ�������û���Ŀ¼�ļ�<filename>.login_conf</filename>��С���ӣ�
 	    ��Ϊ������������������Latin-1���롣</para>
 
 	    <programlisting>me:\
 	:charset=ISO-8859-1:\
 	:lang=de_DE.ISO8859-1:</programlisting>
 
 	    <indexterm><primary>��������</primary><secondary>BIG-5����</secondary></indexterm>
 	    <para>����һ��Ϊ<filename>.login_conf</filename>���÷������ĵ�BIG-5��������ӡ�Ӧ����������Ĵ󲿷ֱ�����
 	    ��Ϊ�ܶ�������û��Ϊ���ģ����ĺͺ���������ȷ�ı��ػ�������</para>
 
 	    <programlisting>#Users who do not wish to use monetary units or time formats
 #of Taiwan can manually change each variable
 me:\
 	:lang=zh_TW.Big5:\
 	:setenv=LC_ALL=zh_TW.Big5:\
 	:setenv=LC_COLLATE=zh_TW.Big5:\
 	:setenv=LC_CTYPE=zh_TW.Big5:\
 	:setenv=LC_MESSAGES=zh_TW.Big5:\
 	:setenv=LC_MONETARY=zh_TW.Big5:\
 	:setenv=LC_NUMERIC=zh_TW.Big5:\
 	:setenv=LC_TIME=zh_TW.Big5:\
 	:charset=big5:\
 	:xmodifiers="@im=gcin": #Set gcin as the XIM Input Server</programlisting>
 
 	    <para>�������Ϣ�ο�<link linkend="adm-setup">����Ա������</link>��&man.login.conf.5;</para>
 	  </sect5>
 
 	  <sect5 id="adm-setup">
 	    <title>����Ա������</title>
 
 	    <para>����û��ĵ��������
 	      <filename>/etc/login.conf</filename>�����Ƿ���������ȷ�����ԡ���Ҫȷ������ļ������ã�</para>
 
 	    <programlisting><replaceable>language_name</replaceable>|<replaceable>Account Type Description</replaceable>:\
 	:charset=<replaceable>MIME_charset</replaceable>:\
 	:lang=<replaceable>locale_name</replaceable>:\
 	:tc=default:</programlisting>
 
 	    <para>�ٴ�ʹ��ǰ���Latin-1��������ӣ�</para>
 
 	    <programlisting>german|German Users Accounts:\
 	:charset=ISO-8859-1:\
 	:lang=de_DE.ISO8859-1:\
 	:tc=default:</programlisting>
 
 	    <para>���޸��û��ĵ�������֮ǰ�� Ӧ����ִ����������</para>
 
 	    <screen>&prompt.root; <userinput>cap_mkdb /etc/login.conf</userinput></screen>
 
 	    <para>�Ա�ʹ��
 	      <filename>/etc/login.conf</filename> ����������������</para>
 
 	    <bridgehead renderas="sect4">ʹ�� &man.vipw.8; �ı�������͡�</bridgehead>
 
 	    <indexterm>
         <primary><command>vipw</command></primary>
       </indexterm>
 	    <para>ʹ��<command>vipw</command>�������û���������������������
 	    </para>
 
 	    <programlisting>user:password:1111:11:<replaceable>language</replaceable>:0:0:User Name:/home/user:/bin/sh</programlisting>
 
 	    <bridgehead renderas="sect4">��&man.adduser.8;�ı�������͡�</bridgehead>
 
 	    <indexterm>
         <primary><command>adduser</command></primary>
       </indexterm>
 	    <indexterm><primary>�������</primary></indexterm>
 	    <para>��<command>adduser</command>�������û�������������������</para>
 
 	    <itemizedlist>
 	      <listitem>
 		<para>��<filename>/etc/adduser.conf</filename>��������<literal>defaultclass =
 		  <replaceable>����</replaceable></literal>��Ӧ�ü�ס��������Ϊʹ���������Ե������û�����
 		  <literal>ȱʡ</literal>���
 		  </para>
 	      </listitem>
 
 	      <listitem>
 		<para>ÿһ��ʹ��&man.adduser.8;��ʱ��һ���ض����ԵĿ�ѡ���Իش������������������
                 <screen><prompt>Enter login class: default []: </prompt></screen>
                 </para>
 	      </listitem>
 
 	      <listitem>
 		<para>����������ÿһ���û�ʹ������һ�����ԣ���Ӧ��������
 		</para>
 
 		<screen>&prompt.root; <userinput>adduser -class <replaceable>language</replaceable></userinput></screen>
 	      </listitem>
 	    </itemizedlist>
 
 	    <bridgehead renderas="sect4">ʹ��&man.pw.8;�ı�������͡�</bridgehead>
 	    <indexterm>
         <primary><command>pw</command></primary>
       </indexterm>
 	    <para>�����ʹ��&man.pw.8;���������û���Ӧ������ʹ�ã�</para>
 
 	    <screen>&prompt.root; <userinput>pw useradd <replaceable>user_name</replaceable> -L <replaceable>language</replaceable></userinput></screen>
 	  </sect5>
 	</sect4>
 
 	<sect4 id="startup-file">
 	  <title>Shell�����ļ�����</title>
 
 	  <note>
 	    <para>���Ƽ�ʹ�����ַ�������Ϊ����Ҫ��ÿһ�����ܵ�shell����һ����ͬ�������ļ���
 	    Ӧ����<link linkend="login-class">������෽��</link>���������ַ�����
 	    </para>
 	  </note>
 
 	  <indexterm><primary>MIME</primary></indexterm>
 	  <indexterm><primary>locale</primary></indexterm>
 	  <para>Ϊ�����ñ��ػ����ƺ�MIME�ַ�����ֻҪ��<filename>/etc/profile</filename>��
 	    <filename>/etc/csh.login</filename>�����ļ�����������������������������ʹ�õ��������ӣ�
 	    </para>
 
 	  <para>��<filename>/etc/profile</filename>���棺</para>
 
 	  <programlisting><envar>LANG=de_DE.ISO8859-1; export LANG</envar>
 <envar>MM_CHARSET=ISO-8859-1; export MM_CHARSET</envar></programlisting>
 
 	  <para>����<filename>/etc/csh.login</filename>���棺</para>
 
 	  <programlisting><envar>setenv LANG de_DE.ISO8859-1</envar>
 <envar>setenv MM_CHARSET ISO-8859-1</envar></programlisting>
 
 	  <para>���⣬�����԰�������������ӵ�<filename>/usr/share/skel/dot.profile</filename>
 	  ����ǰ���<filename>/etc/profile</filename>һ����������<filename>/usr/share/skel/dot.login</filename>
 	  ����ǰ���<filename>/etc/csh.login</filename>һ������</para>
 
 	  <para>����X11��</para>
 
 	  <para>��<filename>$HOME/.xinitrc</filename>���棺</para>
 
 	  <programlisting><envar>LANG=de_DE.ISO8859-1; export LANG</envar></programlisting>
 
 	  <para>���ߣ�</para>
 
 	  <programlisting><envar>setenv LANG de_DE.ISO8859-1</envar></programlisting>
 
 	  <para>��������shell(�����棩��</para>
 
 	</sect4>
       </sect3>
     </sect2>
 
     <sect2 id="setting-console">
       <title>����̨����</title>
 
       <para>�������еļ�C�ַ�������<filename>/etc/rc.conf</filename>�����������۵�����������ȷ�Ŀ���̨�ַ���
       </para>
 
       <programlisting>font8x16=<replaceable>font_name</replaceable>
 font8x14=<replaceable>font_name</replaceable>
 font8x8=<replaceable>font_name</replaceable></programlisting>
 
       <para>�����<replaceable>font_name</replaceable>������<filename>/usr/share/syscons/fonts</filename>Ŀ¼��
       ����<filename>.fnt</filename>��׺��</para>
 
       <indexterm>
         <primary><application>sysinstall</application></primary>
       </indexterm>
       <indexterm><primary>keymap</primary></indexterm>
       <indexterm><primary>screenmap</primary></indexterm>
       <para>�����Ҫ�Ļ��� ��Ӧͨ��
 	<command>sysinstall</command> �������뵥�ֽ� C
 	�ַ�����Ӧ�� keymap �� screenmap��
 	�� <application>sysinstall</application> ��
 	ѡ�� <guimenuitem>Configure</guimenuitem> ֮��ѡ��
 	<guimenuitem>Console</guimenuitem> ���ɽ������á�
 	����֮�⣬ ��Ҳ������ <filename>/etc/rc.conf</filename> �м���������������ã�</para>
 
       <programlisting>scrnmap=<replaceable>screenmap_name</replaceable>
 keymap=<replaceable>keymap_name</replaceable>
 keychange="<replaceable>fkey_number sequence</replaceable>"</programlisting>
 
       <para>�����<replaceable>screenmap_name</replaceable>������<filename>/usr/share/syscons/scrnmaps</filename>Ŀ¼��
       ����<filename>.scm</filename>��׺�� һ����Ӱ���������Ļ����ͨ������Ϊһ����������
       ������VGA�����������������չ8λ��9λ�� �����Ļ������ʹ��һ��8λ�����У�Ҫ�ƶ���Щ��ĸ�뿪��Щ����</para>
 
       <para>
 	�������<filename>/etc/rc.conf</filename>����������<application>moused</application> daemon��</para>
 
 <programlisting>moused_enable="YES"</programlisting>
 
       <para>��ô��Ҫ����һ�μ�����ָ����Ϣ��</para>
 
       <indexterm>
         <primary><application>moused</application></primary>
       </indexterm>
       <para>Ĭ������£� &man.syscons.4;������������ָ�����ַ�����ռ��0xd0-0xd3�ķ�Χ��
 	�����������ʹ�������Χ���������ָ�뷶Χ�Ƴ������Χ��
 	Ҫ�ƹ�������⣬ ��Ҫ��
 	<filename>/etc/rc.conf</filename> �м��룺</para>
 
       <programlisting>mousechar_start=3</programlisting>
 
       <para>��� <replaceable>keymap_name</replaceable>
         ������ <filename>/usr/share/syscons/keymaps</filename> Ŀ¼��
 	��ȥ���� <filename>.kbd</filename> ��׺��
 	�����ȷ��Ӧ��ʹ����һ�����̲��֣� �����ʹ�� &man.kbdmap.1;
 	�����ԣ� �����跴��������</para>
 
       <para>ͨ���� <literal>keychange</literal> ���趨���ܼ�ʱ��
         ƥ��ѡ�����ն�������˵�DZ���ģ� ��Ϊ���ܼ������޷��ڼ��̲����ж��塣</para>
 
       <para>��������Ӧ�ü�鲢ȷ����
         <filename>/etc/ttys</filename> ���Ѿ�Ϊ���е� <literal>ttyv*</literal>
 	����������ȷ���ն����͡� Ŀǰ�� ��ص�Ĭ�϶����ǣ�</para>
 
       <informaltable frame="none" pgwide="1">
 	<tgroup cols="2">
 	  <thead>
 	    <row>
 	      <entry>�ַ�������</entry>
 	      <entry>�ն�����</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry>ISO8859-1 or ISO8859-15</entry>
 	      <entry><literal>cons25l1</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry>ISO8859-2</entry>
 	      <entry><literal>cons25l2</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry>ISO8859-7</entry>
 	      <entry><literal>cons25l7</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry>KOI8-R</entry>
 	      <entry><literal>cons25r</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry>KOI8-U</entry>
 	      <entry><literal>cons25u</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry>CP437 (VGA default)</entry>
 	      <entry><literal>cons25</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry>US-ASCII</entry>
 	      <entry><literal>cons25w</literal></entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
 
       <para>���ڶ��ֽ��ַ����ԣ�����������
 	<filename>/usr/ports/<replaceable>language</replaceable></filename>
 	Ŀ¼��ʹ����ȷ��FreeBSD port��һЩport�Կ���̨���֣�
 	��ϵͳ������Ϊ����vtty�նˣ���ˣ� ����Ϊ X11
 	��α���п���̨׼���㹻��vtty�նˡ�
 	�������ڿ���̨��ʹ���������Ե�Ӧ�ó���IJ����б���</para>
 
       <informaltable frame="none" pgwide="1">
 	<tgroup cols="2">
 	  <thead>
 	    <row>
 	      <entry>����</entry>
 	      <entry>�ض�����</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry>Traditional Chinese (BIG-5)</entry>
 	      <entry><filename role="package">chinese/big5con</filename></entry>
 	    </row>
 
 	    <row>
 	      <entry>Japanese</entry>
 	      <entry><filename role="package">japanese/kon2-16dot</filename> or
 	        <filename role="package">japanese/mule-freewnn</filename></entry>
 	    </row>
 
 	    <row>
 	      <entry>Korean</entry>
 	      <entry><filename role="package">korean/han</filename></entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
     </sect2>
 
     <sect2>
       <title>X11����</title>
 
       <para>��ȻX11����FreeBSD�ƻ���һ���֣�
 	�������Ѿ�ΪFreeBSD�û�������һЩ��Ϣ��
 	����ϸ�ڿ��Բο�<ulink
 	url="http://www.x.org/">&xorg;
 	Web վ��</ulink>
 	������ʹ�õ� X11 Server ����վ��</para>
 
       <para>��<filename>~/.Xresources</filename>���棬�������ʵ������ض�Ӧ�ó����I18N���ã������壬�˵��ȣ���</para>
 
       <sect3>
 	<title>��ʾ����</title>
 	<indexterm><primary>X11 True Type ���������</primary></indexterm>
 	<para>��װ <application>&xorg;</application> ������
 	  (<filename role="package">x11-servers/xorg-server</filename>)��
 	  Ȼ��װ��Ӧ���Ե� &truetype; ���塣 ��������ȷ�ĵ�����Ϣ��
 	  �⽫�����ܹ��ڲ˵��������ط�������ѡ������ԡ�</para>
       </sect3>
 
       <sect3>
 	<title>�����Ӣ���ַ�</title>
 	<indexterm><primary>X11���뷽��(XIM)</primary></indexterm>
 	<para>
 	X11���뷽����XIM��Э��������X11�ͻ��˵�һ���±�׼��
 	���н���ΪXIM�ͻ�����д��X11Ӧ�ó����XIM������������롣
 	��ͬ�������м���XIM���������á�
 	</para>
       </sect3>
     </sect2>
 
     <sect2>
       <title>��ӡ������</title>
 
        <para>һЩ�򵥵�C�ַ���ͨ������Ӳ�������������ӡ���ġ��������λ���ַ�����Ҫ�ض������ã�
 	�����Ƽ�ʹ��<application>apsfilter</application>����Ҳ����ʹ���ض�����ת�������ĵ�ת��Ϊ
 	&postscript;��PDF��ʽ��
         </para>
     </sect2>
 
     <sect2>
       <title>�ں˺��ļ�ϵͳ</title>
 
       <para>FreeBSD �Ŀ����ļ�ϵͳ (FFS) ����ȫ֧�� 8-λ �ַ��ģ�
 	��������Ա������κμ򵥵� C �ַ��� (�μ� &man.multibyte.3;)��
 	�����ļ�ϵͳ�в��ᱣ���ַ��������֣�
 	Ҳ����˵�� �������޸ĵر��� 8-λ��Ϣ�� ������֪����α��롣
 	��ʽ˵���� FFS Ŀǰ����֧���κ���ʽ�Ŀ�����ֽ��ַ�����
 	������ ijЩ������ַ����ṩ�˶��������
 	FFS �IJ������������ù������ǵ�֧�֡� Ŀǰ��ЩҪô���޷���ֲ�ģ�
 	Ҫô���ڴֲڣ� ������Dz���������Ǽ��뵽Դ�����С�
 	��ο�������Ե� Web վ�㣬 ���˽������Щ�����Ľ�һ�������</para>
 
       <indexterm><primary>DOS</primary></indexterm>
       <indexterm><primary>Unicode</primary></indexterm>
       <para>FreeBSD &ms-dos;�Ѿ��ܹ����ó�����&ms-dos;�ϣ�Unicode�ַ����Ϳ�ѡ��FreeBSD�ļ�ϵͳ�ַ����ĸ�����Ϣ��
       ��ο� &man.mount.msdosfs.8; �����ֲᡣ</para>
     </sect2>
   </sect1>
 
   <sect1 id="l10n-compiling">
     <title>����I18N����</title>
 
     <para>����FreeBSD Ports�Ѿ�֧��I18N�ˡ������е�һЩ����-I18N����ǡ�
     ��Щ�������ܶ�����Ѿ��ڽ�I18N��֧�֣�����Ҫ���������������ˡ�
     </para>
 
     <indexterm>
       <primary><application>MySQL</application></primary>
     </indexterm>
     <para>Ȼ��һЩ��<application>MySQL</application>������Ӧ�ó�����Ҫ���������ַ���������
       <filename>Makefile</filename>�������ã�����ֱ�ӰѲ������ݸ�<application>configure</application>��
       </para>
   </sect1>
 
   <sect1 id="lang-setup">
     <title>���ػ�FreeBSD</title>
 
     <sect2 id="ru-localize">
       <sect2info>
 	<authorgroup>
 	  <author>
 	    <firstname>Andrey</firstname>
 	    <surname>Chernov</surname>
 	    <contrib>Originally contributed by </contrib>
 	  </author>
 	</authorgroup>
       </sect2info>
       <title>���KOI8-R���룩</title>
       <indexterm>
 	<primary>���ػ�</primary>
 	<secondary>����</secondary>
       </indexterm>
 
       <para>����KOI8-R����ĸ�����Ϣ�����<ulink
 	url="http://koi8.pp.ru/">KOI8-R���Russian Net Character Set��</ulink>��
 	</para>
 
       <sect3>
 	<title>��������</title>
 
 	<para>��������м��뵽����<filename>~/.login_conf</filename>�ļ���</para>
 
 	<programlisting>me:My Account:\
 	:charset=KOI8-R:\
 	:lang=ru_RU.KOI8-R:</programlisting>
 
 	<para>�ο�ǰ�������<link linkend="setting-locale">���ػ�</link>�����ӡ�</para>
       </sect3>
 
       <sect3>
 	<title>����̨����</title>
 
 	<itemizedlist>
 	  <listitem>
 	    <para>������һ�мӵ�
 	      <filename>/etc/rc.conf</filename>��</para>
 
 	    <programlisting>mousechar_start=3</programlisting>
 	  </listitem>
 
 	  <listitem>
 	    <para>���� <filename>/etc/rc.conf</filename> ���������������ã�</para>
 
 	    <programlisting>keymap="ru.koi8-r"
 scrnmap="koi8-r2cp866"
 font8x16="cp866b-8x16"
 font8x14="cp866-8x14"
 font8x8="cp866-8x8"</programlisting>
 
 	  </listitem>
 
 	  <listitem>
 	    <para>����<filename>/etc/ttys</filename>�����<literal>ttyv*</literal>��¼��Ҫʹ��
 	      <literal>cons25r</literal>��Ϊ�ն����͡�</para>
 	  </listitem>
 	</itemizedlist>
 
 	<para>�ο�ǰ�������<link linkend="setting-console">����̨</link>�����ӡ�</para>
       </sect3>
 
        <sect3>
 	<title>��ӡ������</title>
 	<indexterm><primary>��ӡ��</primary></indexterm>
 	<para>��Ȼ��������������ַ��Ĵ�ӡ����ѭCP866�ı�׼��
 	��ô��Ҫһ�����KOI8-R��CP866ת�����ض������������������һ��������Ĭ�ϵİ�װ��
 	<filename>/usr/libexec/lpr/ru/koi2alt</filename>��
 	  һ��֧�ֶ���Ĵ�ӡ����<filename>/etc/printcap</filename>��¼�������������ģ�
 	  </para>
 
 	<programlisting>lp|Russian local line printer:\
 	:sh:of=/usr/libexec/lpr/ru/koi2alt:\
 	:lp=/dev/lpt0:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs:</programlisting>
 
 	<para>������Ϣ�ο�&man.printcap.5;�ֲ�ҳ��</para>
       </sect3>
 
       <sect3>
 	<title>&ms-dos;�ļ�ϵͳ�Ͷ����ļ���</title>
 
 	<para>������������ڹ���&ms-dos; �ļ�ϵͳ�����öԶ����ļ���֧�ֵ�&man.fstab.5;��¼��
 	</para>
 
 	<programlisting>/dev/ad0s2      /dos/c  msdos   rw,-Wkoi2dos,-Lru_RU.KOI8-R 0 0</programlisting>
 
 	<para>ѡ�� <option>-L</option> ����ѡ��������ƣ�
 	  �� <option>-W</option> �����������ַ�ת������
 	  Ҫʹ�� <option>-W</option> ѡ�
 	  ��һ��Ҫ���ȹҽ� <filename>/usr</filename>��
 	  Ȼ���ٹҽ� &ms-dos; ������ ��Ϊת�����Ƿ���
 	  <filename>/usr/libdata/msdosfs</filename> �ġ�
 	  Ҫ�˽��һ����ϸ�ڣ� ��ο� &man.mount.msdosfs.8; �����ֲᡣ</para>
       </sect3>
 
       <sect3>
 	<title>X11����</title>
 
 	<orderedlist>
 	  <listitem>
 	    <para>���������ǰ����ܵ� <link linkend="setting-locale">��-X
 	      �ı��ػ�����</link>��</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>�������ʹ�� <application>&xorg;</application>�� �밲װ
 	    <filename role="package">x11-fonts/xorg-fonts-cyrillic</filename>
 	    package��</para>
 
 	    <para>����� <filename>/etc/X11/xorg.conf</filename> �ļ��е�
 	      <literal>"Files"</literal> С�ڡ� ������У� Ӧ�ӵ��κ�����
 	      <literal>FontPath</literal> ��֮ǰ��</para>
 
 	    <programlisting>FontPath   "/usr/local/lib/X11/fonts/cyrillic"</programlisting>
 
 	    <note>
 	      <para>��鿴 ports �е�������������塣</para></note>
 	  </listitem>
 
 	  <listitem>
 	    <para>Ҫ���������̣� ��Ҫ��
 	      <filename>xorg.conf</filename> �ļ���
 	      <literal>"Keyboard"</literal> С���м����������ݣ�</para>
 
 	    <programlisting>Option "XkbLayout"   "us,ru"
 Option "XkbOptions"  "grp:toggle"</programlisting>
 
 	    <para>Ҫȷ��<literal>XkbDisable</literal> �Ѿ��ر� (ע�͵�) �ˡ�</para>
 
 	    <para>RUS/LAT���л���<keycap>CapsLock</keycap>���ϵ�<keycap>CapsLock</keycap>���ܿ���ͨ��
 	    <keycombo action="simul"><keycap>Shift</keycap><keycap>CapsLock</keycap></keycombo>
 	    ��ģ�⣨ֻ����LATģʽ��ʱ�򣩡�</para>
 
 	    <para>ʹ�� <literal>grp:toggle</literal>
 	    ʱ�� RUS/LAT �л������� <keycap>�� Alt</keycap>��
 	      ��ʹ�� <literal>grp:ctrl_shift_toggle</literal> ���ʾ�л�����
 	      <keycombo action="simul"><keycap>Ctrl</keycap><keycap>Shift</keycap></keycombo>��
 	      ʹ�� <literal>grp:caps_toggle</literal>
 	    ʱ�� RUS/LAT �л������� <keycap>CapsLock</keycap>��
 	    �ɵ� <keycap>CapsLock</keycap> �����Կ�ͨ�� <keycombo action="simul"><keycap>Shift</keycap><keycap>CapsLock</keycap></keycombo> (ֻ�� LAT
 	      ģʽ��Ч)�� ���ڲ���ԭ��
 	    <literal>grp:caps_toggle</literal> ��
 	    <application>&xorg;</application> ���޷�ʹ�á�</para>
 
 	    <para>������ļ������� <quote>&windows;</quote> ����
 	      ������ RUS ģʽ�£� ijЩ����ĸ��ӳ�䲻������ ��Ӧ������
 	      <filename>xorg.conf</filename> �ļ��м����������У�</para>
 
 	<programlisting>Option "XkbVariant" ",winkeys"</programlisting>
 
 	    <note>
 	      <para>����� XKB ���̿��ܲ���ΪijЩ���߱����ػ����ܵ�Ӧ�ó�����֧�֡�</para>
 	    </note>
 	  </listitem>
 	</orderedlist>
 	<note>
 	  <para>���ػ���������޶�Ӧ�ڳ�������ʱ���� <function>XtSetLanguageProc (NULL, NULL,
 	    NULL);</function> ������</para>
 	  <para>�μ� <ulink
 	    url="http://koi8.pp.ru/xwin.html">
 	    KOI8-R for X Window</ulink> �Ի�ù��ڶ� X11 Ӧ�ý��б��ػ���ָ����</para>
 	</note>
       </sect3>
     </sect2>
 
     <sect2>
       <title>���÷�������</title>
       <indexterm>
 	<primary>���ػ�</primary>
 	<secondary>��������</secondary>
       </indexterm>
       <para>FreeBSD-Taiwan�ƻ���һ��ʹ�úܶ�����ports�����Ļ�ָ����
       <ulink url="http://netlab.cse.yzu.edu.tw/~statue/freebsd/zh-tut/"></ulink>��
 	Ŀǰ�� <literal>FreeBSD ���Ļ�ָ��</literal> ��ά����Ա��
         ���� <email>statue@freebsd.sinica.edu.tw</email>��
       </para>
 
       <para>���� <email>statue@freebsd.sinica.edu.tw</email>
 	���� FreeBSD-Taiwan �� <literal>zh-L10N-tut</literal>������
 	<ulink url="http://netlab.cse.yzu.edu.tw/~statue/cfc/">
 	Chinese FreeBSD Collection (CFC)</ulink>�� ��ص� packages �ͽű��ȿ�����
 	<ulink url="ftp://freebsd.csie.nctu.edu.tw/pub/taiwan/CFC/"></ulink> �ҵ���</para>
     </sect2>
 
     <sect2>
       <title>���ﱾ�ػ����ʺ����е�ISO 8859-1���ԣ�</title>
       <indexterm>
 	<primary>���ػ�</primary>
 	<secondary>����</secondary>
       </indexterm>
 
       <para>Slaven Rezic <email>eserte@cs.tu-berlin.de</email>
 	д��һ���� FreeBSD ���������ʹ���ն������Եĵ���ָ�ϡ� ��ݵ���̳̿�����
 	<ulink url="http://user.cs.tu-berlin.de/~eserte/FreeBSD/doc/umlaute/umlaute.html"></ulink> �ҵ���</para>
     </sect2>
 
     <sect2>
       <title>ϣ���ﱾ�ػ�</title>
 
       <indexterm>
 	<primary>localization (���ػ�)</primary>
 	<secondary>Greek (ϣ����)</secondary>
       </indexterm>
       <para>Nikos Kokkalis <email>nickkokkalis@gmail.com</email>
 	׫д�˹����� &os; ��֧��ϣ������������£� �� <ulink
 	  url="&url.doc.base;/el_GR.ISO8859-7/articles/greek-language-support/index.html">http://www.freebsd.org/doc/el_GR.ISO8859-7/articles/greek-language-support/index.html</ulink>��
 	��ע����ƪ���� <emphasis>ֻ��</emphasis> ϣ����İ汾��</para>
     </sect2>
 
     <sect2>
       <title>����ͺ��ﱾ�ػ�</title>
       <indexterm>
 	<primary>���ػ�</primary>
 	<secondary>����</secondary>
       </indexterm>
       <indexterm>
 	<primary>���ػ�</primary>
 	<secondary>����</secondary>
       </indexterm>
       <para>���ﱾ�ػ���ο�<ulink url="http://www.jp.FreeBSD.org/"></ulink>������ο�
 	<ulink url="http://www.kr.FreeBSD.org/"></ulink>��</para>
     </sect2>
 
     <sect2>
       <title>��Ӣ���FreeBSD�ĵ�</title>
 
       <para>һЩ FreeBSD �Ĺ������Ѿ������� FreeBSD �ĵ���������������ԡ�
 	������ <ulink
 	url="&url.base;/index.html">��վ</ulink> �Լ�
 	<filename>/usr/share/doc</filename> �ҵ���</para>
     </sect2>
   </sect1>
 </chapter>
diff --git a/zh_CN.GB2312/books/handbook/network-servers/chapter.xml b/zh_CN.GB2312/books/handbook/network-servers/chapter.xml
index ab71f2b27e..18435169f1 100644
--- a/zh_CN.GB2312/books/handbook/network-servers/chapter.xml
+++ b/zh_CN.GB2312/books/handbook/network-servers/chapter.xml
@@ -1,4843 +1,4829 @@
 <?xml version="1.0" encoding="gb2312"?>
 <!--
      The FreeBSD Documentation Project
      The FreeBSD Simplified Chinese Project
 
      Original Revision: 1.127
      $FreeBSD$
 -->
 
 <chapter id="network-servers">
   <chapterinfo>
     <authorgroup>
       <author>
         <firstname>Murray</firstname>
 	<surname>Stokely</surname>
 	<contrib>Reorganized by </contrib>
       </author>
     </authorgroup>
     <!-- 23 July 2004 -->
   </chapterinfo>
 
   <title>���������</title>
 
   <sect1 id="network-servers-synopsis">
     <title>��Ҫ</title>
 
     <para>���½�����ijЩ�� &unix; ϵͳ�ϳ��õ�������񡣻��⽫���漰
       ��ΰ�װ�����á����Ժ�ά�����ֲ�ͬ���͵�������񡣱��½��н���
       �����������ļ��������������ܹ������������档</para>
 
     <para>�ڶ��걾��֮��������֪����</para>
 
     <itemizedlist>
 
       <listitem>
 	<para>���� <application>inetd</application>��</para>
       </listitem>
 
       <listitem>
 	<para>�����������һ�������ļ�ϵͳ��</para>
       </listitem>
 
       <listitem>
 	<para>�������һ��������Ϣ�������Թ����û��ʺš�</para>
       </listitem>
 
       <listitem>
 	<para>���ͨ��DHCP�Զ��������硣</para>
       </listitem>
 
       <listitem>
 	<para>�������һ��������������</para>
       </listitem>
 
       <listitem>
 	<para>�������<application>Apache</application> HTTP ��������</para>
       </listitem>
 
       <listitem>
 	<para>��������ļ����䣨FTP����������</para>
       </listitem>
 
       <listitem>
 	<para>���ʹ��<application>Samba</application>Ϊ &windows;
 		�ͻ��������ļ��ʹ�ӡ����</para>
       </listitem>
 
       <listitem>
 	<para>���ͬ��ʱ������ڣ��Լ��������ʹ��NTPЭ���ʱ���������</para>
       </listitem>
 
       <listitem>
         <para>������ñ�׼����־�ػ����̣�
           <command>syslogd</command>�� ����Զ����������־��</para>
       </listitem>
 
     </itemizedlist>
 
     <para>���Ķ����½�֮ǰ����Ӧ����</para>
 
     <itemizedlist>
       <listitem>
 	<para>�����й�<filename>/etc/rc</filename>�нű��Ļ���֪ʶ��</para>
       </listitem>
 
       <listitem>
 	<para>��Ϥ�����������</para>
       </listitem>
 
       <listitem>
       <para>������ΰ�װ����ĵ�����������<xref linkend="ports"/>����</para>
       </listitem>
 
     </itemizedlist>
   </sect1>
 
   <sect1 id="network-inetd">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Chern</firstname>
           <surname>Lee</surname>
           <contrib>Contributed by </contrib>
         </author>
       </authorgroup>
       <authorgroup>
 	<author>
 	  <contrib>���� </contrib>
 	  <othername>The &os; Documentation Project</othername>
 	</author>
       </authorgroup>
     </sect1info>
 
     <title> <application>inetd</application> <quote>����������</quote></title>
 
     <sect2 id="network-inetd-overview">
       <title>����</title>
 
       <para>&man.inetd.8; ��ʱҲ������ <quote>Internet
 	����������</quote>�� ��Ϊ������Ϊ���ַ���������ӡ�
 	�� <application>inetd</application> �յ�����ʱ��
 	���ܹ�ȷ����������ij��� ������Ӧ�Ľ��̣�
 	���� socket ������ (���� socket ����Ϊ����ı�׼���롢
 	����ʹ������������)�� ʹ��
 	<application>inetd</application> ��������Щ���ز��صķ��������ڽ���ϵͳ���أ�
 	��Ϊ������ҪΪÿ���������������ķ������</para>
 
       <para>һ��˵���� <application>inetd</application> ��Ҫ�������������������
 	����Ҳ������ֱ�Ӵ���ijЩ�򵥵ķ���
 	���� <application>chargen</application>��
 	<application>auth</application>�� �Լ�
 	<application>daytime</application>��</para>
 
       <para>��һ�ڽ����ܹ������ͨ��������ѡ� �Լ������ļ�
 	<filename>/etc/inetd.conf</filename> ����
 	<application>inetd</application> �������õ�һЩ����֪ʶ��</para>
     </sect2>
 
     <sect2 id="network-inetd-settings">
       <title>����</title>
 
       <para><application>inetd</application> ��ͨ�� &man.rc.8; ϵͳ�����ġ�
 	<literal>inetd_enable</literal> ѡ��Ĭ����Ϊ
 	<literal>NO</literal>�� �������ڰ�װϵͳʱ��
 	���û�������Ҫͨ�� <application>sysinstall</application> ���򿪡�
 	����</para>
 
       <programlisting>inetd_enable="YES"</programlisting>
 
       <para>��</para>
 
       <programlisting>inetd_enable="NO"</programlisting>
 
       <para>�
 	<filename>/etc/rc.conf</filename> �������û����ϵͳ����ʱ
 	<application>inetd</application> ���Զ������� ���</para>
 
       <screen>&prompt.root; <userinput>/etc/rc.d/inetd rcvar</userinput></screen>
       <para>������ʾĿǰ�����á�</para>
 
       <para>���⣬ ��������ͨ��
 	<literal>inetd_flags</literal> �������� <application>inetd</application>
 	���ݶ��������������</para>
     </sect2>
 
     <sect2 id="network-inetd-cmdline">
       <title>������ѡ��</title>
 
       <para>���������������ƣ� <application>inetd</application>
 	Ҳ�ṩ��Ϊ���ڶ�����Կ�������Ϊ�IJ����� �����IJ����б����£�</para>
 
       <para><command>inetd</command> <option>[-d] [-l] [-w] [-W] [-c maximum] [-C rate] [-a address | hostname]
            [-p filename] [-R rate] [-s maximum] [configuration file]</option></para>
 
       <para>��Щ����������ͨ��
 	<filename>/etc/rc.conf</filename> ��
 	<literal>inetd_flags</literal> ѡ�������� <application>inetd</application>��
 	Ĭ������£�
 	<literal>inetd_flags</literal> ��Ϊ
 	<literal>-wW -C 60</literal>�� �߱�ʾϣ��Ϊ
 	<application>inetd</application> �ķ������� TCP wrapping��
 	����ֹ����ͬһ IP ÿ���ӳ��� 60 �ε�����</para>
 
       <para>��Ȼ���ǻ���������ܹ�����������Ƶ�ʵ�ѡ�
 	����ѧ���û����ܻ�ܸ��˵ط�����Щ����ͨ��������Ҫ�����޸ġ�
 	���յ�����������������ʱ�� ��Щѡ�����п��ܻᷢ�����á�
 	�����IJ����б��� ������ &man.inetd.8; �����ֲ����ҵ���</para>
 
       <variablelist>
 	<varlistentry>
 	  <term>-c maximum</term>
 
 	  <listitem>
 	    <para>ָ�������������󲢷�����������Ĭ��Ϊ���ޡ�
 	      Ҳ�����ڴ˷���ľ�����������ͨ��<option>max-child</option>�ĵ���</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>-C rate</term>
 
 	  <listitem>
 	    <para>ָ����������һ�������ܱ�����IP��ַ���õ���������
 	      Ĭ�ϲ��ޡ�Ҳ�����ڴ˷���ľ�����������ͨ��<option>max-connections-per-ip-per-minute</option>
 	      �ĵ���</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>-R rate</term>
 
 	  <listitem>
 	    <para>ָ����������һ�������ܱ����õ���������Ĭ��Ϊ256��
 	      ��Ϊ0 ���������޴������á�</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>-s maximum</term>
 
 	  <listitem>
 	    <para>ָ��ͬһ IP ͬʱ����ͬһ����ʱ���������ֵ�� Ĭ��ֵΪ�����ơ�
 	      ������ͨ�� <option>max-child-per-ip</option>
 	      �������Է���Ϊ��λ�������ơ�</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
     </sect2>
 
     <sect2 id="network-inetd-conf">
       <!-- XXX This section isn't very clear, and could do with some lovin' -->
       <title><filename>inetd.conf</filename></title>
 
       <para>���� <application>inetd</application> �����ã�
 	��ͨ�� <filename>/etc/inetd.conf</filename> �ļ�����ɵġ�</para>
 
       <para>���޸���
 	<filename>/etc/inetd.conf</filename> ֮�� ����ʹ�������������ǿ��
 	<application>inetd</application> ���¶�ȡ�����ļ���</para>
 
       <example id="network-inetd-reread">
 	<title>���¼��� <application>inetd</application>
 	  �����ļ�</title>
 
 	<screen>&prompt.root; <userinput>/etc/rc.d/inetd reload</userinput></screen>
       </example>
 
       <para>�����ļ��е�ÿһ�ж���һ�������ķ������ ������ļ��У� ǰ����
 	<quote>#</quote> �����ݱ���Ϊ��ע�͡�
 	<filename>/etc/inetd.conf</filename> �ļ��ĸ�ʽ���£�</para>
 
       <programlisting>service-name
 socket-type
 protocol
 {wait|nowait}[/max-child[/max-connections-per-ip-per-minute[/max-child-per-ip]]]
 user[:group][/login-class]
 server-program
 server-program-arguments</programlisting>
 
       <para>��������� IPv4 �� &man.ftpd.8; ��������ӣ�</para>
 
       <programlisting>ftp     stream  tcp     nowait  root    /usr/libexec/ftpd       ftpd -l</programlisting>
 
       <variablelist>
 	<varlistentry>
 	  <term>service-name</term>
 
 	  <listitem>
 	    <para>ָ����������ķ��������������������<filename>/etc/services</filename>���г���һ�¡�
 	      �⽫����<application>inetd</application>������ĸ�port��
 	      һ�����µķ�����Ҫ���ӣ���������<filename>/etc/services</filename>�������ӡ�</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>socket-type</term>
 
 	  <listitem>
 	    <para>������<literal>stream</literal>��<literal>dgram</literal>��<literal>raw</literal>����
 	      <literal>seqpacket</literal>�� <literal>stream</literal>
 	      ���ڻ������ӵ� TCP ���񣻶� <literal>dgram</literal> ������ʹ�� <acronym>UDP</acronym> Э��ķ���</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>protocol</term>
 
 	  <listitem>
 	    <para>����֮һ��</para>
 
 	    <informaltable frame="none" pgwide="1">
 	      <tgroup cols="2">
 		<thead>
 		  <row>
 		    <entry>��</entry>
 		    <entry>˵��</entry>
 		  </row>
 		</thead>
 		<tbody>
 		  <row>
 		    <entry>tcp�� tcp4</entry>
 		    <entry>TCP IPv4</entry>
 		  </row>
 		  <row>
 		    <entry>udp�� udp4</entry>
 		    <entry>UDP IPv4</entry>
 		  </row>
 		  <row>
 		    <entry>tcp6</entry>
 		    <entry>TCP IPv6</entry>
 		  </row>
 		  <row>
 		    <entry>udp6</entry>
 		    <entry>UDP IPv6</entry>
 		  </row>
 		  <row>
 		    <entry>tcp46</entry>
 		    <entry>Both TCP IPv4 and v6</entry>
 		  </row>
 		  <row>
 		    <entry>udp46</entry>
 		    <entry>Both UDP IPv4 and v6</entry>
 		  </row>
 		</tbody>
 	      </tgroup>
 	    </informaltable>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>{wait|nowait}[/max-child[/max-connections-per-ip-per-minute[/max-child-per-ip]]]</term>
 
 	  <listitem>
 	    <para><option>wait|nowait</option> ָ����<application>inetd</application>
 	    	��ͷ���õķ����Ƿ�����Լ�����socket.
 	      <option>dgram</option>socket���ͱ���ʹ��<option>wait</option>��
 	      ��stream socket daemons�� ����ͨ��ʹ�ö��̷߳�ʽ��Ӧ��ʹ��
 	      <option>nowait</option>.  <option>wait</option> ͨ���Ѷ��
 	      socket ��������������̣� �� <option>nowait</option> ��
 	      ��Ϊÿ���µ� socket ����һ���ӽ��̡�</para>
 
 	    <para><option>max-child</option> ѡ���ܹ�����
 	      <application>inetd</application> ��Ϊ������������������ӽ���������
 	      ���ij�ض�������Ҫ�޶����10��ʵ���� ��<literal>/10</literal>
 	      �ŵ�<option>nowait</option>��ͷ�Ϳ����ˡ� ָ�� <literal>/0</literal>
 	      ��ʾ�������ӽ��̵�������</para>
 
 	    <para>���� <option>max-child</option> ֮�⣬
 	      ��������ѡ�������������ͬһλ�õ��ض�����������������
 	      <option>max-connections-per-ip-per-minute</option> ���������ض� IP
 	      ��ַÿ���ӵ����������� ���磬 �����κ�
 	      IP ��ַÿ�����������ʮ�Ρ� <option>max-child-per-ip</option>
 	      ���������Ϊijһ IP ��ַ���κ�ʱ�����������ӽ���������
 	      ��Щѡ����ڷ�ֹ��Է�����������������Դ�Ľߺ;ܾ����� (DoS)
 	      ����ʮ�����á�</para>
 
 	    <para>����ֶ��У� ����ָ�� <option>wait</option> ��
 	      <option>nowait</option> ����֮һ�� ��
 	      <option>max-child</option>��
 	      <option>max-connections-per-ip-per-minute</option> ��
 	      <option>max-child-per-ip</option> ���ǿ�ѡ�</para>
 
 	    <para>��ʽ���̷߳��� ���Ҳ������κ�
 	      <option>max-child</option>��
 	      <option>max-connections-per-ip-per-minute</option> ��
 	      <option>max-child-per-ip</option> ����ʱ��
 	      �������� <literal>nowait</literal>��</para>
 
 	    <para>ͬһ������ ��ϣ����������������������Ϊʮ��ʱ��
 	      ���ǣ� <literal>nowait/10</literal>��</para>
 
 	    <para>ͬ�����ã� ����ÿ�� IP ��ַÿ����������Ӷ�ʮ�Σ�
 	      ��ͬʱ�������ӽ������ʮ���� Ӧд����
 	      <literal>nowait/10/20</literal>��</para>
 
 	    <para>������ &man.fingerd.8; �����Ĭ�����ã�</para>
 
 	    <programlisting>finger stream  tcp     nowait/3/10 nobody /usr/libexec/fingerd fingerd -s</programlisting>
 
 	    <para>�����������У� ���ӽ���������Ϊ
 	      100 ���� ������ IP ���ͬʱ���� 5 �����ӣ�
 	      <literal>nowait/100/0/5</literal>��</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>user</term>
 
 	  <listitem>
 	    <para>�ÿ���ָ��������ʲô�û��������С�һ����ԣ���������������
 	      <username>root</username>�����ڰ�ȫĿ�ģ����Կ�����Щ������
 	      <username>daemon</username>���ݣ���������С��Ȩ��
 	      <username>nobody</username>��������</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>server-program</term>
 
 	  <listitem>
 	    <para>�����ӵ���ʱ��ִ�з�������ȫ·���������������
 	    <application>inetd</application>�����ṩ�ģ���<option>internal</option>���档</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>server-program-arguments</term>
 
 	  <listitem>
 	    <para>��<option>server-program</option>���õ�ʱ���ÿ���
 	    ��ֵͨ��<literal>argv[0]</literal>ͨ�����ݸ������������
 	    �����������<command>mydaemon -d</command>����
 	      <literal>mydaemon -d</literal>Ϊ<option>server-program-arguments</option>
 	      ���ص�ֵ��ͬ���ģ������������<application>inetd</application>
 	      �����ṩ�ģ����ﻹ��
 	      <option>internal</option>��</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
     </sect2>
 
     <sect2 id="network-inetd-security">
       <title>Security</title>
 
       <para>�氲װʱ��ѡ��ģʽ��ͬ��
 	���� <application>inetd</application> �ķ�������Ѿ�Ĭ�����á�
 	���ȷʵ����Ҫij���ض��ķ��� ��Ӧ���ǽ�������
 	�� <filename>/etc/inetd.conf</filename> ��
 	����Ӧ���������ǰ����� <quote>#</quote>��
 	Ȼ�� <link linkend="network-inetd-reread">���¼���
 	inetd ����</link> �Ϳ����ˡ� ijЩ���� ����
 	<application>fingerd</application>�� ��������ȫ����Ҫ�ģ�
 	��Ϊ�����ṩ����Ϣ���ܶԹ��������á�</para>
 
       <para>ijЩ���������ʱ��ȱ�ٰ�ȫ��ʶ�ģ� �����й�����ѹ��û����������ij�ʱ���ơ�
 	��ʹ�ù������ܹ�ͨ�������ض���Щ���������ӣ� ���ľ����õ���Դ��
 	������������� ���� <option>max-connections-per-ip-per-minute</option>��
 	<option>max-child</option> �� <option>max-child-per-ip</option> ���ƣ�
 	����Լ�������Ϊ�Ǹ��ð취��</para>
 
       <para>Ĭ������£�TCP wrapping �Ǵ򿪵ġ��ο�
 	&man.hosts.access.5; �ֲᣬ�Ի�ø�������ڸ��� <application>inetd</application>
 	���õķ���������TCP���Ƶ���Ϣ��</para>
     </sect2>
 
     <sect2 id="network-inetd-misc">
       <title>����</title>
 
       <para><application>daytime</application>��
 	<application>time</application>��
 	<application>echo</application>��
 	<application>discard</application>��
 	<application>chargen</application>�� �Լ�
 	<application>auth</application> ������ <application>inetd</application>
 	�ṩ���ڽ�����</para>
 
       <para><application>auth</application> �����ṩ���������ݷ���
 	����������Ϊ�ṩ��ͬ����ķ��� ������������ͨ��ֻ�ܼ򵥵Ĵ򿪻�رա�</para>
 
       <para>�ο� &man.inetd.8; �ֲ��ø�����Ϣ��</para>
     </sect2>
   </sect1>
 
   <sect1 id="network-nfs">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Tom</firstname>
           <surname>Rhodes</surname>
           <contrib>Reorganized and enhanced by </contrib>
         </author>
       </authorgroup>
       <authorgroup>
         <author>
           <firstname>Bill</firstname>
       	  <surname>Swingle</surname>
 	  <contrib>Written by </contrib>
         </author>
       </authorgroup>
     </sect1info>
     <title>�����ļ�ϵͳ��NFS��</title>
 
     <indexterm><primary>NFS</primary></indexterm>
     <para>�����ļ�ϵͳ��FreeBSD֧�ֵ��ļ�ϵͳ�е�һ�֣�
       Ҳ����Ϊ <acronym role="Network
       File System">NFS</acronym>�� <acronym role="Network File
       System">NFS</acronym>����һ��ϵͳ�������������˹���Ŀ¼���ļ���ͨ��ʹ��<acronym
       role="Network File System">NFS</acronym>���û��ͳ����������ʱ����ļ�
       һ������Զ��ϵͳ�ϵ��ļ���</para>
 
     <para>������<acronym>NFS</acronym>���Զ��׼��ĺô���</para>
 
     <itemizedlist>
       <listitem>
 	<para>���ع���վʹ�ø��ٵĴ��̿ռ䣬��Ϊͨ�������ݿ��Դ����һ
 	̨�����϶��ҿ���ͨ��������ʵ���</para>
       </listitem>
 
       <listitem>
 	<para>�û�������ÿ�������ϻ�����ͷ����һ��homeĿ¼��HomeĿ¼
 	  ���Ա�����<acronym>NFS</acronym>�������ϲ����������ϴ������á�
 	  </para>
       </listitem>
 
       <listitem>
 	<para>����������CDROM���� &iomegazip; ֮��Ĵ洢�豸�������������汻��Ļ���ʹ�á�
 	  ����Լ������������ϵĿ��ƶ������豸��������</para>
       </listitem>
     </itemizedlist>
 
     <sect2>
       <title><acronym>NFS</acronym>��������</title>
 
       <para><acronym>NFS</acronym> ���ٰ���������Ҫ�IJ��֣� һ̨��������
         �Լ�����һ̨�ͻ����� �ͻ���Զ�̵ط��ʱ����ڷ������ϵ����ݡ�
         Ҫ����һ����ת������ ��Ҫ���ò����м�������</para>
 
       <para>�����������������·���</para>
       <indexterm>
         <primary>NFS</primary>
         <secondary>server (����)</secondary>
       </indexterm>
       <indexterm>
         <primary>�ļ�������</primary>
         <secondary>UNIX �ͻ���</secondary>
       </indexterm>
 
       <indexterm>
 	<primary><application>rpcbind</application></primary>
       </indexterm>
       <indexterm>
         <primary><application>mountd</application></primary>
       </indexterm>
       <indexterm>
         <primary><application>nfsd</application></primary>
       </indexterm>
 
       <informaltable frame="none" pgwide="1">
 	<tgroup cols="2">
 	  <colspec colwidth="1*"/>
 	  <colspec colwidth="3*"/>
 
 	  <thead>
 	    <row>
 	      <entry>����</entry>
 	      <entry>����</entry>
 	    </row>
 	  </thead>
 	  <tbody>
 	    <row>
 	      <entry><application>nfsd</application></entry>
 	      <entry><acronym>NFS</acronym>��Ϊ����<acronym>NFS</acronym>�ͻ��˵�
 	      �������</entry>
 	    </row>
 	    <row>
 	      <entry><application>mountd</application></entry>
 	      <entry><acronym>NFS</acronym>���ط��񣬴���&man.nfsd.8;�ݽ�����������</entry>
 	    </row>
 	    <row>
 	      <entry><application>rpcbind</application></entry>
 	      <entry> �˷�������
 	      <acronym>NFS</acronym> �ͻ������ѯ���ڱ� <acronym>NFS</acronym> ����ʹ�õĶ˿ڡ�</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
 
       <para>�ͻ���ͬ������һЩ���̣�����
         <application>nfsiod</application>��
         <application>nfsiod</application>��������<acronym>NFS</acronym>������
         ���ǿ�ѡ�ģ����ҿ���������ܣ�������ͨ����ȷ�IJ�����˵�����DZ���ġ�
         �ο�&man.nfsiod.8;�ֲ��ø�����Ϣ��
       </para>
     </sect2>
 
     <sect2 id="network-configuring-nfs">
       <title>����<acronym>NFS</acronym></title>
       <indexterm>
         <primary>NFS</primary>
         <secondary>configuration</secondary>
       </indexterm>
 
       <para><acronym>NFS</acronym>�����ù�����Լ򵥡��������ֻ��Ҫ
       ��<filename>/etc/rc.conf</filename>�ļ���һЩ���޸ġ�</para>
 
       <para>��<acronym>NFS</acronym>��������ˣ�ȷ��<filename>/etc/rc.conf</filename>
       �ļ���ͷ���¿��ض�������:</para>
 
       <programlisting>rpcbind_enable="YES"
 nfs_server_enable="YES"
 mountd_flags="-r"</programlisting>
 
       <para>ֻҪ<acronym>NFS</acronym>������Ϊenable��<application>mountd</application>
       �����Զ����С�</para>
 
       <para>�ڿͻ���һ�࣬ȷ������������س�����
         <filename>/etc/rc.conf</filename>��ͷ:</para>
 
       <programlisting>nfs_client_enable="YES"</programlisting>
 
       <para><filename>/etc/exports</filename>�ļ�ָ�����ĸ��ļ�ϵͳ
       <acronym>NFS</acronym>Ӧ���������ʱ����Ϊ<quote>����</quote>����
       <filename>/etc/exports</filename>����ÿ��ָ��һ��������ļ�ϵͳ��
       ��Щ�������Է��ʸ��ļ�ϵͳ����ָ����������Ȩ�޵�ͬʱ������ѡ��
       ����Ҳ���Ա�ָ�����кܶ࿪�ؿ��Ա���������ļ���ͷ��������������
       ����ϸ̸��������ͨ���Ķ�&man.exports.5; �ֲ���������Щ���ء�</para>
 
       <para>������һЩ<filename>/etc/exports</filename>�����ӣ�</para>
 
       <indexterm>
         <primary>NFS</primary>
         <secondary>export examples</secondary>
       </indexterm>
 
       <para>������һ������ļ�ϵͳ�����ӣ� �������������������������绷����������������ء�
       ���磬 ���Ҫ�� <filename>/cdrom</filename> ������������������ͬ����̨�����
       (���������ֻ�л������� ��û�и�����Щ�����������)�� ����
       <filename>/etc/hosts</filename> �ļ��н������������á� <option>-ro</option>
       ��־��ʾ��������ļ�ϵͳ��Ϊֻ���� ����ʹ���������־��
       Զ��ϵͳ��������ļ�ϵͳ�ϾͲ���д���κα䶯�ˡ�</para>
 
       <programlisting>/cdrom -ro host1 host2 host3</programlisting>
 
       <para>��������ӿ������<filename>/home</filename>��������IP��ַ��ʽ��ʾ��������
 	������û������<acronym>DNS</acronym>��������˽��������ͷ��������á�
 	���⣬ <filename>/etc/hosts</filename> �ļ�Ҳ���������������������ο� &man.hosts.5; ��
 	<option>-alldirs</option> ���������Ŀ¼����Ϊ���ص㡣
 	Ҳ����˵���ͻ��˿��Ը�����Ҫ������Ҫ��Ŀ¼�� </para>
 
       <programlisting>/home  -alldirs  10.0.0.2 10.0.0.3 10.0.0.4</programlisting>
 
       <para>���漸����� <filename>/a</filename> ���Ա��������Բ�ͬ��Ŀͻ��˿��Է����ļ�ϵͳ��
 	<option>-maproot=root</option> �����ȨԶ��ϵͳ�ϵ�
 	<username>root</username> �û��ڱ�������ļ�ϵͳ����<username>root</username>���ݽ��ж�д��
 	���û���ر�ָ�� <literal>-maproot=root</literal> ��ǣ�
 	��ʹ�û���Զ��ϵͳ���� <username>root</username> ���ݣ�
 	Ҳ�����޸ı�����ļ�ϵͳ�ϵ��ļ��� </para>
 
       <programlisting>/a  -maproot=root  host.example.com box.example.org</programlisting>
 
       <para> Ϊ���ܹ����ʵ���������ļ�ϵͳ���ͻ��˱��뱻��Ȩ��
       ��ȷ�Ͽͻ��������� <filename>/etc/exports</filename> ���г��� </para>
 
       <para>�� <filename>/etc/exports</filename> ��ͷ��ÿһ�����棬�����Ϣ���ļ�ϵͳһһ��Ӧ��
 	һ��Զ������ÿ��ֻ�ܶ�Ӧһ���ļ�ϵͳ������ֻ����һ��Ĭ����ڡ����磬����
 	<filename>/usr</filename> �Ƕ������ļ�ϵͳ����� <filename>/etc/exports</filename> ������Ч�ģ�</para>
 
       <programlisting># Invalid when /usr is one file system
 /usr/src   client
 /usr/ports client</programlisting>
 
       <para>һ���ļ�ϵͳ��<filename>/usr</filename>�� ������ָ�������ͬһ������
 	<hostid>client</hostid>.
 	�����һ�������ȷ�ĸ�ʽ�ǣ�</para>
 
       <programlisting>/usr/src /usr/ports  client</programlisting>
 
       <para>��ͬһ�ļ�ϵͳ�У� �����ָ���ͻ���������Ŀ¼�� ������д��ͬһ���ϡ�
 	û��ָ���ͻ������лᱻ��Ϊ�ǵ�һ������ �����������������������ļ�ϵͳ��
 	���Ծ����������˵�ⲻ�����⡣</para>
 
       <para>������һ����Ч����б������ӣ�
 	<filename>/usr</filename> �� <filename>/exports</filename>
 	�DZ����ļ�ϵͳ��</para>
 
       <programlisting># Export src and ports to client01 and client02, but only
 # client01 has root privileges on it
 /usr/src /usr/ports -maproot=root    client01
 /usr/src /usr/ports               client02
 # The client machines have root and can mount anywhere
 # on /exports. Anyone in the world can mount /exports/obj read-only
 /exports -alldirs -maproot=root      client01 client02
 /exports/obj -ro</programlisting>
 
       <para>���޸��� <filename>/etc/exports</filename> �ļ�֮��
 	�ͱ����� <application>mountd</application> �������¼������
 	�Ա�ʹ�޸���Ч�� һ�ַ�����ͨ�����������еķ�������� HUP
 	�ź�����ɣ�</para>
 
       <screen>&prompt.root; <userinput>kill -HUP `cat /var/run/mountd.pid`</userinput></screen>
 
       <para>��ָ���ʵ��IJ��������� <command>mountd</command> &man.rc.8; �ű���</para>
 
       <screen>&prompt.root; <userinput>/etc/rc.d/mountd onereload</userinput></screen>
 
       <para>����ʹ�� rc �ű���ϸ�ڣ� ��μ� <xref linkend="configtuning-rcd"/>��</para>
 
       <para>���⣬ ϵͳ������������ FreeBSD ��һ�ж�Ū�á� ������ˣ�
         �������DZ���ġ� �� <username>root</username> ����ִ�������������Ը㶨һ�С�</para>
 
       <para>�� <acronym>NFS</acronym> �������ˣ�</para>
 
       <screen>&prompt.root; <userinput>rpcbind</userinput>
 &prompt.root; <userinput>nfsd -u -t -n 4</userinput>
 &prompt.root; <userinput>mountd -r</userinput></screen>
 
       <para>�� <acronym>NFS</acronym> �ͻ��ˣ�</para>
 
       <screen>&prompt.root; <userinput>nfsiod -n 4</userinput></screen>
 
       <para>����ÿ�����鶼Ӧ�þ������Ա�����һ��Զ���ļ�ϵͳ�� ����Щ������ͷ��
       ���������ֽ��ǣ�<hostid>server</hostid> �����ͻ��˵����ֽ��ǣ� <hostid>client</hostid>��
       �����ֻ������ʱ����һ��Զ���ļ�ϵͳ����ֻ�Ǵ���������������ȷ���
       ֻҪ�ڿͻ����� <username>root</username> ����ִ����������</para>
       <indexterm>
         <primary>NFS</primary>
         <secondary>mounting</secondary>
       </indexterm>
       <screen>&prompt.root; <userinput>mount server:/home /mnt</userinput></screen>
 
       <para>���������ѷ���˵� <filename>/home</filename> Ŀ¼���ص��ͻ��˵� <filename>/mnt</filename> �ϡ�
       ���������ȷ����Ӧ�ÿ��Խ���ͻ��˵� <filename>/mnt</filename> Ŀ¼���ҿ������з���˵��ļ��� </para>
 
       <para>�����������ϵͳÿ������������ʱ���Զ�����Զ�˵��ļ�ϵͳ�����Ǹ��ļ�ϵͳ�ӵ�
 	<filename>/etc/fstab</filename> �ļ���ͷȥ�����������ӣ�</para>
 
       <programlisting>server:/home	/mnt	nfs	rw	0	0</programlisting>
 
       <para> &man.fstab.5; �ֲ��������п��õĿ��ء�</para>
     </sect2>
 
     <sect2>
       <title>��</title>
 
       <para>ijЩӦ�ó��� (���� <application>mutt</application>)
 	��Ҫ�ļ�����֧�ֲ����������С� ��ʹ��
 	<acronym>NFS</acronym> ʱ�� ������ <application>rpc.lockd</application>
 	��֧���ļ��������ܡ� Ҫ��������
 	��Ҫ�ڷ������Ϳͻ����� <filename>/etc/rc.conf</filename> �м���
 	(�ٶ����˾�������� <acronym>NFS</acronym>)��</para>
 
       <programlisting>rpc_lockd_enable="YES"
 rpc_statd_enable="YES"</programlisting>
 
       <para>Ȼ��ʹ���������������ó���</para>
 
       <screen>&prompt.root; <userinput>/etc/rc.d/lockd start</userinput>
 &prompt.root; <userinput>/etc/rc.d/statd start</userinput></screen>
 
       <para>���������Ҫ����� <acronym>NFS</acronym> �ͻ�����
 	<acronym>NFS</acronym> ��������ȷ�����������壬
 	������ <acronym>NFS</acronym> �ͻ����ڱ���������
 	������ʹ�� &man.mount.nfs.8; ʱָ�� <option>-L</option> ������
 	��μ� &man.mount.nfs.8; �����ֲ����˽����ϸ�ڡ�
       </para>
     </sect2>
 
     <sect2>
       <title>ʵ��Ӧ��</title>
 
       <para><acronym>NFS</acronym> �кܶ�ʵ��Ӧ�á������DZȽϳ�����һЩ��</para>
 
       <indexterm>
         <primary>NFS</primary>
         <secondary>uses</secondary>
       </indexterm>
       <itemizedlist>
         <listitem>
 	  <para>�����������һ̨CDROM���������豸��������ڶ�̨�����а�װ������˵���ӱ��˸����㡣
 	   </para>
 	</listitem>
 
 	<listitem>
 	  <para>�ڴ��������У�����һ̨���� <acronym>NFS</acronym> �������������������û���homeĿ¼���ܻ����������
 	    ��ЩĿ¼�ܱ�����������Ա��û���������̨����վ�ϵ�¼�����ܵõ���ͬ��homeĿ¼��
 	    </para>
 	</listitem>
 
 	<listitem>
 	  <para>��̨����������ͨ�õ�<filename>/usr/ports/distfiles</filename> Ŀ¼��
           �����Ļ���������Ҫ�ڼ�̨�����ϰ�װportʱ��������������ÿ̨�豸�����ض����ٷ���Դ�롣
            </para>
 	</listitem>
       </itemizedlist>
     </sect2>
 
     <sect2 id="network-amd">
       <sect2info>
 	<authorgroup>
 	  <author>
 	    <firstname>Wylie</firstname>
 	    <surname>Stilwell</surname>
 	    <contrib>Contributed by </contrib>
 	  </author>
 	</authorgroup>
 	<authorgroup>
 	  <author>
 	    <firstname>Chern</firstname>
 	    <surname>Lee</surname>
 	    <contrib>Rewritten by </contrib>
 	  </author>
 	</authorgroup>
       </sect2info>
       <title>ͨ�� <application>amd</application> �Զ��عҽ�</title>
 
       <indexterm><primary>amd</primary></indexterm>
       <indexterm><primary>�Զ��ҽӷ���</primary></indexterm>
 
       <para>&man.amd.8; (�Զ��ҽӷ���) �ܹ��Զ����ڷ���ʱ�ҽ�Զ�̵��ļ�ϵͳ��
 	����ļ�ϵͳ��һ��ʱ��֮��û�л�� ��ᱻ
 	<application>amd</application> �Զ�ж�¡� ͨ��ʹ��
 	<application>amd</application>�� �ܹ��ṩһ���־ùҽ������ѡ��
 	������������Ҫ����
         <filename>/etc/fstab</filename>��</para>
 
       <para><application>amd</application> ͨ�����Լ��� NFS ����������ʽ��
 	���ӵ� <filename>/host</filename> ��
 	<filename>/net</filename> Ŀ¼����������
 	��������ЩĿ¼�е��ļ�ʱ�� <application>amd</application>
 	��������Ӧ��Զ�̹ҽӵ㣬 ���Զ��عҽӡ�
 	<filename>/net</filename> ���ڹҽ�Զ�� IP ��ַ�ϵ������ļ�ϵͳ��
 	�� <filename>/host</filename> �����ڹҽ�Զ���������ϵ��ļ�ϵͳ��</para>
 
       <para>����
 	<filename>/host/foobar/usr</filename> �е��ļ��� �൱�ڸ���
 	<application>amd</application> ���Թҽ�������
 	<hostid>foobar</hostid> �ϵ�����
 	<filename>/usr</filename>��</para>
 
       <example>
 	<title>ͨ�� <application>amd</application> ���ҽӵ������ļ�ϵͳ</title>
 
 	<para>������ͨ��ʹ�� <command>showmount</command>
 	  �������鿴Զ�������ϵ������ļ�ϵͳ�� ���磬
 	  Ҫ�鿴 <hostid>foobar</hostid> �ϵ������ļ�ϵͳ�� �����ã�</para>
 
 	<screen>&prompt.user; <userinput>showmount -e foobar</userinput>
 Exports list on foobar:
 /usr                               10.10.10.0
 /a                                 10.10.10.0
 &prompt.user; <userinput>cd /host/foobar/usr</userinput></screen>
       </example>
 
       <para>��ͬ��ǰ���������������ģ� <command>showmount</command> ��ʾ�˵�����
 	<filename>/usr</filename>�� ������
 	<filename>/host/foobar/usr</filename> ���Ŀ¼ʱ�� <application>amd</application>
 	�����Խ��������� <hostid>foobar</hostid>
 	���Զ��عҽ���Ҫ���ļ�ϵͳ������</para>
 
       <para><application>amd</application> ����ͨ�������ű��������� ��������
 	<filename>/etc/rc.conf</filename> �м��룺</para>
 
       <programlisting>amd_enable="YES"</programlisting>
 
       <para>����֮�⣬ �����Ը�
       <application>amd</application> ͨ��
       <varname>amd_flags</varname> ѡ�������ݶ���IJ����� Ĭ������£�
       <varname>amd_flags</varname> ��</para>
 
       <programlisting>amd_flags="-a /.amd_mnt -l syslog /host /etc/amd.map /net /etc/amd.map"</programlisting>
 
       <para><filename>/etc/amd.map</filename>
 	�ļ������˹ҽӵ����ļ�ϵͳʱ��ʹ�õ�Ĭ��ѡ�
 	<filename>/etc/amd.conf</filename> �ļ��� �����˸������
 	<application>amd</application> �ĸ߼�����ѡ�</para>
 
       <para>��ο� &man.amd.8; �� &man.amd.conf.5; �����ֲᣬ
 	���˽��һ���������</para>
     </sect2>
 
     <sect2 id="network-nfs-integration">
       <sect2info>
         <authorgroup>
           <author>
             <firstname>John</firstname>
             <surname>Lind</surname>
             <contrib>Contributed by </contrib>
           </author>
         </authorgroup>
       </sect2info>
       <title>������ϵͳ����ʱ�ij�������</title>
 
       <para>ijЩ�ض��� ISA PC ϵͳ�ϵ���̫������������һЩ���ƣ�
 	��Щ���ƿ��ܻᵼ�����ص��������⣬ �ر����� NFS ���ʹ��ʱ��
 	��Щ���Ⲣ�� FreeBSD �����еģ� �� FreeBSD ϵͳ���ܵ���Щ�����Ӱ�졣</para>
 
       <para>���������⣬ ���������ڵ� (FreeBSD) PC ϵͳ������ܵĹ���վ��
 	���� Silicon Graphics, Inc., �� Sun Microsystems, Inc. �Ĺ���վ����ʱ������
 	NFS �ҽ��ܹ����������� ����һЩ����Ҳ���ܳɹ���
 	����������ܿ��öԿͻ�����̫���ᣬ
 	��Ȼ�������ͻ�����������Ȼ�ܹ�����������
 	�������ͨ�������ڿͻ��ˣ� ��������һ�� FreeBSD ϵͳ�����նˡ�
 	������ϵͳ�ϣ� һ�����������������⣬ ͨ��û�취�����عرտͻ�����
 	Ψһ�İ취ͨ�������ն˸�λ�� ��Ϊ��һ NFS ״��û�а취�������</para>
 
       <para>���� <quote>��ȷ��</quote> ����취�� ��Ϊ
 	FreeBSD ϵͳ�䱸һ������ܵġ� ���õ���̫����������
 	Ȼ��Ҳ�а취�ƹ����Ⲣ�õ��������Ľ����
 	��� FreeBSD ϵͳ��
 	<emphasis>������</emphasis>�� ���ڿͻ����ҽ�ʱ�� Ӧ��ָ��
 	<option>-w=1024</option>�� ���
 	FreeBSD ϵͳ�� <emphasis>�ͻ���</emphasis>��
 	��Ӧ���� <option>-r=1024</option> ������ ��Щѡ�����ͨ���ڶ�Ӧ��
 	<filename>fstab</filename> �ĵ��ĸ��ֶμ��룬
 	�Ա��ÿͻ����ܹ��Զ��عҽӣ� ����ͨ�� &man.mount.8; ��
 	<option>-o</option> �������ֹ��ҽ�ʱָ����</para>
 
       <para>����Ҫע�������һ�����⣬ ��ʱ�ᱻ����Ϊ�Ǻ�����һ�������⡣
 	����������� NFS �������Ϳͻ����ڲ�ͬ��������ʱ�� �������������� һ��Ҫ
 	<emphasis>ȷ��</emphasis> ����·����ȷʵ�ѱ���� <acronym>UDP</acronym>
 	��Ϣ·�ɵ���Ŀ�ĵأ� ��������ʲôҲ�����ˡ�</para>
 
       <para>����������� <hostid>fastws</hostid> ������
 	(�ӿ�) �����֣� ����һ̨�����ܵ��նˣ� ��
 	<hostid>freebox</hostid> ����һ̨���� (�ӿ�) �����֣�
 	����һ��ʹ�ýϵ����ܵ���̫���������� FreeBSD ϵͳ�� ͬʱ��
 	<filename>/sharedfs</filename> ����������Ϊ NFS
 	�ļ�ϵͳ (�μ� &man.exports.5;)�� ��
 	<filename>/project</filename>
 	���ǿͻ����Ϲҽ���һ�����ļ�ϵͳ�Ĺҽӵ㡣 ���е�Ӧ�ó����У�
 	��ע�⸽��ѡ� ���� <option>hard</option> ��
 	<option>soft</option> �Լ� <option>bg</option> ����������Ӧ������Ҫ�ġ�</para>
 
       <para>���� FreeBSD ϵͳ (<hostid>freebox</hostid>)
 	��Ϊ�ͻ�����ʾ�� <filename>/etc/fstab</filename> �ļ��� ����
 	<hostid>freebox</hostid> ֮�ϣ�</para>
 
       <programlisting>fastws:/sharedfs /project nfs rw,-r=1024 0 0</programlisting>
 
       <para>�� <hostid>freebox</hostid> ���ֹ��ҽӣ�</para>
 
       <screen>&prompt.root; <userinput>mount -t nfs -o -r=1024 fastws:/sharedfs /project</userinput></screen>
 
       <para>�� FreeBSD ϵͳ��Ϊ�����������ӣ� �� <hostid>fastws</hostid> �ϵ�
 	<filename>/etc/fstab</filename>��</para>
 
       <programlisting>freebox:/sharedfs /project nfs rw,-w=1024 0 0</programlisting>
 
       <para>�� <hostid>fastws</hostid> ���ֹ��ҽӵ������ǣ�</para>
 
       <screen>&prompt.root; <userinput>mount -t nfs -o -w=1024 freebox:/sharedfs /project</userinput></screen>
 
       <para>�������е� 16-λ ��̫����������
 	���ܹ���û��������д�ߴ����Ƶ����������������</para>
 
       <para>������Щ���ĵ�����ʲô������ˣ� ������ʧ����η����Ľ��ͣ�
 	ͬʱ��Ҳ˵����Ϊʲô����һ���޷��ָ������⡣ ��������£�
 	NFS ��ʹ��һ�� <quote>��</quote> Ϊ��λ���в����� ��ߴ���
 	8&nbsp;K (��Ȼ�����ܻὫ�����ֳɸ�С�ߴ�ķ�Ƭ)��
 	����������̫�����ߴ��Լ�� 1500&nbsp;�ֽڣ�
 	��� NFS <quote>��</quote> ��ֳɶ����̫������
 	��Ȼ�ڸ��߲�Ĵ��뿴������Ȼ��һ�������ĵ�Ԫ��
 	���ڽ��շ�������װ�� ��Ϊһ��������
 	<emphasis>ȷ��</emphasis>�� �����ܵĹ���վ��
 	���Խ����� NFS ��Ԫ�İ�Ѹ�ٷ����� ������쵽��׼����������޶ȡ�
 	��������С�Ŀ��ϣ� �����İ�����ͬһ��Ԫ�ڵĽ���İ���
 	���������Ԫ�޷����ؽ���ȷ�ϡ� �����ǣ�
 	����վ����ʱ�����ԣ� ����Ȼ�������� 8&nbsp;K ��Ԫ��
 	��һ���̽�����ֹ���ظ���ȥ��</para>
 
       <para>�������Ԫ�ߴ���������̫�����ߴ�֮�£�
 	���Ǿ��ܹ�ȷ��ÿһ����̫�������ܹ��������ؽ��պ�ȷ�ϣ�
 	�Ӷ�������������������Ρ�</para>
 
       <para>����ڸ����ܹ���վ�����ݿ�Ͷ�� PC ϵͳʱ�Իᷢ����
 	���ڸ��õ������ϣ� �ܹ���֤�������������ÿһ�� NFS
 	<quote>��Ԫ</quote> �϶������� ���������ʱ��
 	��Ӱ��ĵ�Ԫ���ش��� �����ʱ�кܴ�Ļ�����������ȷ���ա�
 	���飬 ��ȷ�ϡ�</para>
     </sect2>
   </sect1>
 
   <sect1 id="network-nis">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Bill</firstname>
       	  <surname>Swingle</surname>
 	  <contrib>Written by </contrib>
          </author>
       </authorgroup>
       <authorgroup>
 	<author>
 	  <firstname>Eric</firstname>
 	  <surname>Ogren</surname>
 	  <contrib>Enhanced by </contrib>
 	</author>
 	<author>
 	  <firstname>Udo</firstname>
 	  <surname>Erdelhoff</surname>
 	</author>
       </authorgroup>
     </sect1info>
     <title>������Ϣ���� (NIS/YP)</title>
 
     <sect2>
       <title>����ʲô��</title>
       <indexterm><primary>NIS</primary></indexterm>
       <indexterm><primary>Solaris</primary></indexterm>
       <indexterm><primary>HP-UX</primary></indexterm>
       <indexterm><primary>AIX</primary></indexterm>
       <indexterm><primary>Linux</primary></indexterm>
       <indexterm><primary>NetBSD</primary></indexterm>
       <indexterm><primary>OpenBSD</primary></indexterm>
 
       <para><acronym role="Network Information System">NIS</acronym>��
         ��ʾ������Ϣ���� (Network Information Services)��
         ����� Sun Microsystems ������ ���� &unix;
         (����� &sunos;) ϵͳ�ļ��й����� Ŀǰ��
         ���������Ѿ���Ϊ��ҵ���׼�� ������������ &unix; ϵͳ
         (&solaris;, HP-UX, &aix;, Linux, NetBSD, OpenBSD, FreeBSD,
         �ȵ�) ��֧�� <acronym role="Network Information
         System">NIS</acronym>��</para>
 
       <indexterm><primary>��ҳ (yellow pages)</primary><see>NIS</see></indexterm>
 
       <para><acronym role="Network Information System">NIS</acronym>
 	Ҳ������������֪�Ļ�ҳ(Yellow Pages)�� �������̱�����⣬
 	Sun �������Ϊ���ڵ����֡� �ɵ����� (�Լ� yp)��
 	��Ȼ�������Կ����� �����㷺ʹ�á�</para>
 
       <indexterm>
         <primary>NIS</primary>
         <secondary>��</secondary>
       </indexterm>
 
       <para>����һ������ RPC �Ŀͻ���/������ϵͳ��
 	��������һ�� NIS ���е�һ���������һϵ�������ļ���
 	������ ϵͳ����Ա�Ϳ�������ֻ����������������ݵ� NIS �ͻ���ϵͳ��
 	���ڵ��������ӡ� ɾ�����޸��������ݡ�</para>
 
       <indexterm><primary>Windows NT</primary></indexterm>
 
       <para>����ʵ�ֵ��ڲ�ϸ�ڽ�Ȼ��ͬ�� ��� &windowsnt; ��ϵͳ�dz����ƣ�
         �����ڿ��Խ����ߵĻ��������໥��ȡ�</para>
     </sect2>
 
     <sect2>
       <title>��Ӧ��֪��������ͽ���</title>
 
       <para>��һϵ���������Ҫ���û����̽������� FreeBSD
         ��ʵ�� NIS ʱ�õ��� �������ڴ���
         NIS �������� ����Ϊ NIS �ͻ�����</para>
 
       <indexterm>
 	<primary><application>rpcbind</application></primary>
       </indexterm>
       <indexterm>
 	<primary><application>portmap</application></primary>
       </indexterm>
 
       <informaltable frame="none" pgwide="1">
 	<tgroup cols="2">
 	<colspec colwidth="1*"/>
 	<colspec colwidth="3*"/>
 
 	  <thead>
 	    <row>
 	      <entry>����</entry>
 	      <entry>˵��</entry>
 	    </row>
 	  </thead>
 	  <tbody>
 	    <row>
 	      <entry>NIS ����</entry>
 
 	      <entry>NIS ����������������ͻ���
 		(�����ӷ�����) ��ʹ��ͬһ NIS ������
 		�� &windowsnt; �������ƣ� NIS ������
 		<acronym>DNS</acronym> �޹ء�</entry>
 	    </row>
 	    <row>
 	      <entry><application>rpcbind</application></entry>
 
 	      <entry>��������������� ���ܹ�����
 		<acronym>RPC</acronym> (Զ�̹��̵��ã� NIS
 		�õ���һ������Э��)�� ���û������
 		<application>rpcbind</application>��
 		��û�а취���� NIS ��������
 		����Ϊ NIS �ͻ�����</entry>
 	    </row>
 	    <row>
 	      <entry><application>ypbind</application></entry>
 
 	      <entry><quote>��(bind)</quote> NIS �ͻ��������� NIS
 		�������ϡ� ������ ������ϵͳ�л�ȡ NIS ������
 		��ʹ�� <acronym>RPC</acronym> ���ӵ��������ϡ�
 		<application>ypbind</application> �� NIS ������
 		�ͻ���-������ͨѶ�ĺ��ģ� ����ͻ����ϵ�
 		<application>ypbind</application> �����Ļ��� �����޷�����
 		NIS ��������</entry>
 	    </row>
 	    <row>
 	      <entry><application>ypserv</application></entry>
 	      <entry>ֻӦ�� NIS ���������������� ���� NIS �ķ��������̡�
 		��� &man.ypserv.8; �����Ļ���
 		������������پ�����Ӧ NIS ��������� (��ʱ��
 		����дӷ������Ļ��� ���ӹܲ���)�� ��һЩ NIS
 		��ʵ�� (������ FreeBSD �����) �Ŀͻ����ϣ�
 		���֮ǰ�ù�һ���������� ����̨�����������Ļ���
 		���������������ӵ���һ���������� ͨ����
 		�����������ʱ�� Ψһ�İ취����������������������
 		(���ߣ� ������������������) ��ͻ����ϵ�
 		<application>ypbind</application> ���̡�
 	      </entry>
 	    </row>
 	    <row>
 	      <entry><application>rpc.yppasswdd</application></entry>
 	      <entry>��һ��ֻӦ��
 		NIS �������������еĽ��̣� ����һ���������
 		������������ NIS �ͻ����ı����ǵ� NIS ���
 		���û������������� �û��������¼�� NIS
 		���������ϣ� ���������޸Ŀ��</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
       <!-- XXX Missing: rpc.ypxfrd (not important, though) May only run
       on the master -->
 
     </sect2>
 
     <sect2>
       <title>������ι����ģ�</title>
 
       <para>�� NIS �����У� ���������͵�������
 	���������� �ӷ������� �Լ��ͻ�����
 	�������������dz䵱����������Ϣ���������ݿ⡣
 	���������ϱ�������Щ��Ϣ��Ȩ��������
 	���ӷ��������DZ�����Щ��Ϣ�����ั����
 	�ͻ��������ڷ������������ṩ��Щ��Ϣ��</para>
 
       <para>�����ļ�����Ϣ����ͨ�����ַ�ʽ��������
 	ͨ������£� <filename>master.passwd</filename>��
 	<filename>group</filename>�� �Լ� <filename>hosts</filename>
 	��ͨ�� NIS �ַ��ġ� ����ʲôʱ��
 	����ͻ����ϵ�ij������������Щ��Ӧ�ڱ��ص��ļ��е����ϵ�ʱ��
 	�����������󶨵� NIS �������������� ����ʹ�ñ��صİ汾��</para>
 
       <sect3>
         <title>��������</title>
 
         <itemizedlist>
-	  <indexterm>
-	    <primary>NIS</primary>
-	    <secondary>��������</secondary>
-	  </indexterm>
           <listitem>
-            <para>һ̨ <emphasis>NIS ��������</emphasis>��
+            <para>һ̨ <emphasis>NIS ��������</emphasis>��<indexterm><primary>NIS</primary><secondary>��������</secondary></indexterm>
               ��̨�������� �� &windowsnt; ����������ƣ�
               ��ά������ NIS �ͻ�����ʹ�õ��ļ��� <filename>passwd</filename>��
               <filename>group</filename>�� �Լ��������� NIS
               �ͻ�����ʹ�õ��ļ��� ������ŵ����������ϡ�</para>
 
             <note><para>���Խ�һ̨ NIS �����������ڶ�� NIS ���С�
               Ȼ���� ���鲻������������ý��н��ܣ�
               ��Ϊ�������ã� ͨ��ֻ������С��ģ�� NIS �����С�</para></note>
           </listitem>
 
           <listitem>
-	    <indexterm>
-	      <primary>NIS</primary>
-	      <secondary>�ӷ�����</secondary>
-	    </indexterm>
-
-            <para><emphasis>NIS �ӷ�����</emphasis>�� ��һ���
+            <para><emphasis>NIS �ӷ�����</emphasis><indexterm><primary>NIS</primary><secondary>�ӷ�����</secondary></indexterm>�� ��һ���
               �� &windowsnt; �ı�������������ơ� NIS �ӷ�������
               ����ά�� NIS ���������������ļ�������
               NIS �ӷ������ṩ��һ�����࣬
               ����������Ҫ�Ļ������DZ���ġ� ���⣬
               ��Ҳ�������������������ĸ��ɣ� NIS
               �ͻ������ǹҽӵ�������Ӧ���ǵ� NIS �������ϣ�
               ����Ҳ�������Դӷ���������Ӧ��</para>
           </listitem>
 
           <listitem>
-	    <indexterm>
-	      <primary>NIS</primary>
-	      <secondary>�ͻ���</secondary>
-	    </indexterm>
-
-            <para><emphasis>NIS �ͻ���</emphasis>�� NIS �ͻ�����
+            <para><emphasis>NIS �ͻ���</emphasis>��<indexterm><primary>NIS</primary><secondary>�ͻ���</secondary></indexterm> NIS �ͻ�����
               �Ͷ��� &windowsnt; ����վ���ƣ� ͨ��
               NIS ������ (����� &windowsnt; ����վ�� ����
               &windowsnt; �������) ����ɵ�¼ʱ��������֤���̡�</para>
           </listitem>
         </itemizedlist>
       </sect3>
     </sect2>
 
     <sect2>
       <title>ʹ�� NIS/YP</title>
 
       <para>��һ�ڽ�ͨ��ʵ������������� NIS ������</para>
 
       <sect3>
         <title>�滮</title>
 
         <para>�ٶ������ڹ�����ѧ�е�һ��С��ʵ���ҡ� �����ʵ�����У�
           �� 15 ̨ FreeBSD ������ Ŀǰ��û�м��еĹ����㣻
           ÿһ̨���������Լ���
           <filename>/etc/passwd</filename> ��
           <filename>/etc/master.passwd</filename>��
           ��Щ�ļ�ͨ���˹���Ԥ�ķ��������������������ϰ汾��ͬ����
           Ŀǰ�� �������ʵ����������һ���û��� �����ò������� 15
           ̨�������ֹ�ִ�� <command>adduser</command> ���
           ��ӹ���ɣ� ��һ��״����ı䣬
           ���������������ʵ����תΪʹ�� NIS��
           ��ʹ����̨������Ϊ��������</para>
 
         <para>��ˣ� ʵ���ҵ�����Ӧ���������ģ�</para>
 
         <informaltable frame="none" pgwide="1">
           <tgroup cols="3">
             <thead>
               <row>
                 <entry>������</entry>
                 <entry>IP ��ַ</entry>
                 <entry>�����Ľ�ɫ</entry>
               </row>
             </thead>
             <tbody>
               <row>
                 <entry><hostid>ellington</hostid></entry>
                 <entry><hostid role="ipaddr">10.0.0.2</hostid></entry>
                 <entry>NIS ��������</entry>
               </row>
               <row>
                 <entry><hostid>coltrane</hostid></entry>
                 <entry><hostid role="ipaddr">10.0.0.3</hostid></entry>
                 <entry>NIS �ӷ�����</entry>
               </row>
               <row>
                 <entry><hostid>basie</hostid></entry>
                 <entry><hostid role="ipaddr">10.0.0.4</hostid></entry>
                 <entry>��Ա����վ</entry>
               </row>
               <row>
                 <entry><hostid>bird</hostid></entry>
                 <entry><hostid role="ipaddr">10.0.0.5</hostid></entry>
                 <entry>�ͻ���</entry>
               </row>
               <row>
                 <entry><hostid>cli[1-11]</hostid></entry>
                 <entry><hostid role="ipaddr">10.0.0.[6-17]</hostid></entry>
                 <entry>�����ͻ���</entry>
               </row>
             </tbody>
           </tgroup>
         </informaltable>
 
         <para>��������״����� NIS�� ��ϸ˼����ν��й滮��ʮ����Ҫ��
 	  ������������Ĵ�С��Σ� ��������м������ߡ�</para>
 
         <sect4>
           <title>ѡ�� NIS ����</title>
 
 	  <indexterm>
 	    <primary>NIS</primary>
 	    <secondary>����</secondary>
 	  </indexterm>
           <para>����ܲ�������ȥʹ�õ� <quote>����(domainname)</quote>��
 	    ���Ĺ淶�Ľз��� Ӧ����
 	    <quote>NIS ����</quote>�� ���ͻ����㲥�Դ���Ϣ������ʱ��
 	    ���Ὣ NIS ���������Ϊ�����һ���ַ����� ������
 	    ͳһ�����ϵĶ���������� ���ܹ�֪��˭Ӧ�û�Ӧ����
 	    �����԰� NIS �����������ij�ַ�ʽ��ص�һ�����������֡�</para>
 
 	  <para>һЩ������ѡ��ʹ�����ǵ� Internet
 	    ��������Ϊ NIS ������ �����Ƽ��������� ��Ϊ�ڵ�����������ʱ��
 	    ����ܻᵼ�²���Ҫ�����š� NIS ����Ӧ��������������Ψһ�ģ�
 	    �����������˽����������ĵ�������һ������� ������� Acme
 	    ��˾���������ţ� ���Կ���ʹ��
 	    <quote>acme-art</quote> ������ NIS ������
 	    ����������У� ��ʹ�õ�������
 	    <literal>test-domain</literal>��</para>
 
 	  <indexterm><primary>SunOS</primary></indexterm>
           <para>Ȼ���� ijЩ����ϵͳ (���������� &sunos;)
           ��ʹ���� NIS ������Ϊ Internet ������
           ������������ϴ��ڰ����������ƵĻ����� ��
           <emphasis>����</emphasis> ʹ�� Internet ��������Ϊ���� NIS ������</para>
         </sect4>
 
         <sect4>
           <title>������������Ҫ��</title>
 
 	  <para>ѡ�� NIS ������ʱ�� ��Ҫʱ���μ�һЩ������
 	    NIS ��һ����̫�õ����Ծ�����ͻ������ڷ������������̶ȡ�
 	    ����ͻ����޷����� NIS ��ķ�������ϵ��
 	    ����̨����ͨ�������ڲ����õ�״̬�� ȱ���û�������Ϣ��
 	    ��ʹ�������ϵͳ������ݵĶ���״̬�� ���������Ŀ��ǣ�
 	    ����Ҫѡ��һ̨���������������� �����ڿ����Ļ������е������Ρ�
 	    ����������粻̫æ�� Ҳ����ʹ����������������Ļ��������� NIS
 	    ���� ֻ����Ҫע�⣬ һ�� NIS �����������ã� ��
 	    <emphasis>����</emphasis> �� NIS �ͻ��������ܵ�Ӱ�졣</para>
         </sect4>
       </sect3>
 
       <sect3>
         <title>NIS ������</title>
 
 	<para>���е� NIS ��Ϣ������汾��
 	  ����������һ̨�����ij��� NIS ���������Ļ����ϡ�
 	  ���ڱ�����Щ��Ϣ�����ݿ⣬ ��Ϊ NIS ӳ��(map)��
 	  �� FreeBSD �У� ��Щӳ�䱻������
 	  <filename>/var/yp/[domainname]</filename> � ����
 	  <filename>[domainname]</filename> ���ṩ����� NIS
 	  ������֡� һ̨ NIS �������� ����ͬʱ֧�ֶ����
 	  ��˿��Խ����ܶ�������Ŀ¼�� ��֧��һ�����Ӧһ����
 	  ÿһ���򶼻���һ�������ӳ�䡣</para>
 
 	<para>NIS ���ʹӷ������� ͨ�� <command>ypserv</command>
 	  ����������������е� NIS ����
 	  <command>ypserv</command> �����ν������� NIS �ͻ���������
 	  ����������� ��������ӳ��Ϊ��ص����ݿ��ļ���·����
 	  Ȼ���������ݿ�����ݴ��ؿͻ�����</para>
 
         <sect4>
 	  <title>���� NIS ��������</title>
 	  <indexterm>
 	    <primary>NIS</primary>
 	    <secondary>����������</secondary>
 	  </indexterm>
 	  <para>������ NIS ��������Զ���ʮ�ֵļ򵥣�
 	    ������岽����ȡ����������Ҫ�� FreeBSD
 	    �ṩ��һ����λ�� NIS ֧�֡� ����Ҫ����ȫ�����飬 ֻ����
 	    <filename>/etc/rc.conf</filename> �м���һЩ���ã�
 	    ������������ FreeBSD ��ɡ�</para>
 
           <procedure>
             <step>
               <para><programlisting>nisdomainname="test-domain"</programlisting>
                 ��һ�н����������� (������������) ʱ�� �� NIS ��������Ϊ
                 <literal>test-domain</literal>��</para>
             </step>
             <step>
               <para><programlisting>nis_server_enable="YES"</programlisting>
                 �⽫Ҫ�� FreeBSD ��������ϵͳ����֮����������
                 NIS ������̡�</para>
             </step>
             <step>
               <para><programlisting>nis_yppasswdd_enable="YES"</programlisting>
                 �⽫���� <command>rpc.yppasswdd</command>
                 ������� ��ǰ���ᵽ�ģ�
                 �������û��ڿͻ������޸��Լ��� NIS ���</para>
             </step>
           </procedure>
 
           <note>
             <para>�� NIS ���õIJ�ͬ�� ���ܻ���Ҫ��������һЩ��Ŀ�� ��μ� <link
               linkend="network-nis-server-is-client">���� NIS ������ͬʱ�䵱 NIS
               �ͻ���</link> ��һ�ڣ� ���˽��һ���������</para>
           </note>
 
           <para>���ú�ǰ����Щ����֮�� ��Ҫ�Գ����û���������
             <command>/etc/netstart</command> ��� �������
             <filename>/etc/rc.conf</filename> ������������ϵͳ�е��������֡�
             ��� �ڳ�ʼ�� NIS ӳ��֮ǰ�� ����Ҫ�ֹ�����
 	    <application>ypserv</application> �������</para>
 
 	  <screen>&prompt.root; <userinput>/etc/rc.d/ypserv start</userinput></screen>
         </sect4>
 
         <sect4>
           <title>��ʼ�� NIS ӳ��</title>
           <indexterm>
             <primary>NIS</primary>
             <secondary>ӳ��</secondary>
           </indexterm>
           <para><emphasis>NIS ӳ��</emphasis> ��һЩ���ݿ��ļ���
             ����λ�� <filename>/var/yp</filename> Ŀ¼�С�
             ��Щ�ļ������϶��Ǹ��� NIS ���������� <filename>/etc</filename>
             Ŀ¼�Զ����ɵģ� Ψһ�������ǣ�
             <filename>/etc/master.passwd</filename> �ļ��� һ����˵��
             �����зdz���ֵ����ɲ��� <username>root</username>
             �Լ����������ʺŵĿ�������� NIS ���ϵķ������ϡ�
             ��ˣ� �ڿ�ʼ��ʼ�� NIS ӳ��֮ǰ�� ����Ӧ�ã�</para>
 
           <screen>&prompt.root; <userinput>cp /etc/master.passwd /var/yp/master.passwd</userinput>
 &prompt.root; <userinput>cd /var/yp</userinput>
 &prompt.root; <userinput>vi master.passwd</userinput></screen>
 
           <para>��� ɾ������ϵͳ�йص��ʺŶ�Ӧ���� (<username>bin</username>��
             <username>tty</username>�� <username>kmem</username>��
             <username>games</username>�� �ȵ�)��
             �Լ�������ϣ������ɢ�� NIS �ͻ������ʺ�
             (���� <username>root</username> ������� UID 0
             (�����û�) ���ʺ�)��</para>
 
           <note><para>ȷ��
             <filename>/var/yp/master.passwd</filename> ����ļ���ͬ���û���
             �Լ������û����ɶ��� (ģʽ 600)�� �����Ҫ�Ļ��� ��
             <command>chmod</command> ������������</para></note>
 
 	  <indexterm><primary>Tru64 UNIX</primary></indexterm>
 
           <para>�����Щ����֮�� �Ϳ��Գ�ʼ��
             NIS ӳ���ˣ� FreeBSD �ṩ��һ����Ϊ
             <command>ypinit</command> �Ľű����������������� (��ϸ��Ϣ��
             ����������ֲ�)�� ��ע�⣬ ����ű��ھ������ &unix;
             ����ϵͳ�϶������ҵ��� �����������в���ϵͳ�Ķ��ṩ��
             �� Digital UNIX/Compaq Tru64 UNIX ������������
             <command>ypsetup</command>�� ���������������ɵ��� NIS
             ����������ӳ�䣬 ���Ӧ��ʹ��  <command>ypinit</command> ��
             <option>-m</option> ������ ����Ѿ�������������裬
             Ҫ���� NIS ӳ�䣬 ֻ��ִ�У�</para>
 
           <screen>ellington&prompt.root; <userinput>ypinit -m test-domain</userinput>
 Server Type: MASTER Domain: test-domain
 Creating an YP server will require that you answer a few questions.
 Questions will all be asked at the beginning of the procedure.
 Do you want this procedure to quit on non-fatal errors? [y/n: n] <userinput>n</userinput>
 Ok, please remember to go back and redo manually whatever fails.
 If you don't, something might not work.
 At this point, we have to construct a list of this domains YP servers.
 rod.darktech.org is already known as master server.
 Please continue to add any slave servers, one per line. When you are
 done with the list, type a &lt;control D&gt;.
 master server   :  ellington
 next host to add:  <userinput>coltrane</userinput>
 next host to add:  <userinput>^D</userinput>
 The current list of NIS servers looks like this:
 ellington
 coltrane
 Is this correct?  [y/n: y] <userinput>y</userinput>
 
 [..output from map generation..]
 
 NIS Map update completed.
 ellington has been setup as an YP master server without any errors.</screen>
 
           <para><command>ypinit</command> Ӧ�û����
             <filename>/var/yp/Makefile.dist</filename> ������
             <filename>/var/yp/Makefile</filename> �ļ���
             ������֮�� ����ļ���ٶ������ڲ���ֻ�� FreeBSD
             �����ĵ������� NIS ������ ���� <literal>test-domain</literal>
             ����һ���ӷ������� ������༭
             <filename>/var/yp/Makefile</filename>��</para>
 
           <screen>ellington&prompt.root; <userinput>vi /var/yp/Makefile</userinput></screen>
 
 	  <para>Ӧ���ܹ���������һ�У� ��������</para>
 
 	  <programlisting>NOPUSH = "True"</programlisting>
 
 	  <para>(�����û��ע�͵��Ļ�)��</para>
         </sect4>
 
         <sect4>
 	  <title>���� NIS �ӷ�����</title>
 	  <indexterm>
 	    <primary>NIS</primary>
 	    <secondary>�ӷ�����</secondary>
 	  </indexterm>
 	  <para>���� NIS �ӷ������� ��������������������Ҫ�򵥡�
 	    ��¼���ӷ������ϣ� ������ǰ��ķ�����
             �༭ <filename>/etc/rc.conf</filename> �ļ��� Ψһ�������ǣ�
             ������ <command>ypinit</command> ʱ��Ҫʹ��
             <option>-s</option> ������
             ����� <option>-s</option> ѡ� ͬʱҪ���ṩ NIS
             �������������֣� ������ǵ�������Ӧ���ǣ�</para>
 
   <screen>coltrane&prompt.root; <userinput>ypinit -s ellington test-domain</userinput>
 
 Server Type: SLAVE Domain: test-domain Master: ellington
 
 Creating an YP server will require that you answer a few questions.
 Questions will all be asked at the beginning of the procedure.
 
 Do you want this procedure to quit on non-fatal errors? [y/n: n]  <userinput>n</userinput>
 
 Ok, please remember to go back and redo manually whatever fails.
 If you don't, something might not work.
 There will be no further questions. The remainder of the procedure
 should take a few minutes, to copy the databases from ellington.
 Transferring netgroup...
 ypxfr: Exiting: Map successfully transferred
 Transferring netgroup.byuser...
 ypxfr: Exiting: Map successfully transferred
 Transferring netgroup.byhost...
 ypxfr: Exiting: Map successfully transferred
 Transferring master.passwd.byuid...
 ypxfr: Exiting: Map successfully transferred
 Transferring passwd.byuid...
 ypxfr: Exiting: Map successfully transferred
 Transferring passwd.byname...
 ypxfr: Exiting: Map successfully transferred
 Transferring group.bygid...
 ypxfr: Exiting: Map successfully transferred
 Transferring group.byname...
 ypxfr: Exiting: Map successfully transferred
 Transferring services.byname...
 ypxfr: Exiting: Map successfully transferred
 Transferring rpc.bynumber...
 ypxfr: Exiting: Map successfully transferred
 Transferring rpc.byname...
 ypxfr: Exiting: Map successfully transferred
 Transferring protocols.byname...
 ypxfr: Exiting: Map successfully transferred
 Transferring master.passwd.byname...
 ypxfr: Exiting: Map successfully transferred
 Transferring networks.byname...
 ypxfr: Exiting: Map successfully transferred
 Transferring networks.byaddr...
 ypxfr: Exiting: Map successfully transferred
 Transferring netid.byname...
 ypxfr: Exiting: Map successfully transferred
 Transferring hosts.byaddr...
 ypxfr: Exiting: Map successfully transferred
 Transferring protocols.bynumber...
 ypxfr: Exiting: Map successfully transferred
 Transferring ypservers...
 ypxfr: Exiting: Map successfully transferred
 Transferring hosts.byname...
 ypxfr: Exiting: Map successfully transferred
 
 coltrane has been setup as an YP slave server without any errors.
 Don't forget to update map ypservers on ellington.</screen>
 
 	  <para>����Ӧ�û���һ������
 	    <filename>/var/yp/test-domain</filename> ��Ŀ¼��
 	    �����Ŀ¼�У� Ӧ�ñ��� NIS ���������ϵ�ӳ��ĸ�����
 	    ��������Ҫȷ����Щ�ļ�����ʱ��ͬ�������ˡ� �ڴӷ������ϣ� �����
 	    <filename>/etc/crontab</filename> �������ȷ����һ�㣺</para>
 
 	  <programlisting>20      *       *       *       *       root   /usr/libexec/ypxfr passwd.byname
 21      *       *       *       *       root   /usr/libexec/ypxfr passwd.byuid</programlisting>
 
 	  <para>�����н�ǿ�ƴӷ�������ӳ������������ͬ����
 	    �������������᳢��ȷ�������� NIS ӳ��ı䶯��֪��ӷ�������
 	    �����Щ����Ǿ��Ա���ġ� ������
 	    ���ڱ��������ͻ��˵Ŀ�����Ϣ��ȷ��ʮ����Ҫ�� �����������ڴӷ�������
 	    ǿ���Ƽ���ȷָ����ϵͳʱ��ǿ�Ƹ��¿���ӳ�䡣 ���ڷ�æ��������ԣ�
 	    ��һ��������Ҫ�� ��Ϊ��ʱ���ܳ���ӳ����²���ȫ�������</para>
 
           <para>���ڣ� �ڴӷ�������ִ�� <command>/etc/netstart</command>��
             �Ϳ������� NIS �����ˡ�</para>
 	</sect4>
       </sect3>
 
       <sect3>
         <title>NIS �ͻ���</title>
 
 	<para>NIS �ͻ�����ͨ��
 	  <command>ypbind</command> ������������ض��� NIS
 	  ����������һ�ֳ����󶨵���ϵ��
 	  <command>ypbind</command> ����ϵͳ��Ĭ����
 	  (����ͨ�� <command>domainname</command> ���������õ�)��
 	  ����ʼ�ڱ��������Ϲ㲥 RPC ���� ��Щ�����ָ��
 	  <command>ypbind</command> ���԰󶨵�������
 	  ����Ѿ������˷������� ������Щ�������ӵ��˹㲥�� ������Ӧ
 	  <command>ypbind</command>�� �������¼�������ĵ�ַ��
 	  ����ж�����õķ����� (����һ������������ ���϶���ӷ�����)��
 	  <command>ypbind</command> ��ʹ�õ�һ����Ӧ�ĵ�ַ��
 	  ����һʱ�̿�ʼ�� �ͻ���������е� NIS ����ֱ�ӷ����Ǹ���������
 	  <command>ypbind</command> ż���� <quote>ping</quote>
 	  ��������ȷ������Ȼ���������С� ����ں�����ʱ����û�еõ���Ӧ�� ��
 	  <command>ypbind</command> �������Ϊδ�󶨣� ���ٴη���㲥��
 	  �����ҵ���һ̨��������</para>
 
 	<sect4>
 	  <title>���� NIS �ͻ���</title>
 	  <indexterm>
 	    <primary>NIS</primary>
 	    <secondary>�ͻ�������</secondary>
 	  </indexterm>
 	  <para>����һ̨ FreeBSD ������Ϊ NIS �ͻ����Ƿdz��򵥵ġ�</para>
 
 	  <procedure>
 	    <step>
 	      <para>�༭ <filename>/etc/rc.conf</filename> �ļ���
                 �������м������漸�У� ������ NIS ������
                 ������������ʱ���� <command>ypbind</command>��</para>
 
 	      <programlisting>nisdomainname="test-domain"
 nis_client_enable="YES"</programlisting>
 	    </step>
 
 	    <step>
 	      <para>Ҫ�� NIS �������������еĿ����
 		��Ҫ������
 		<filename>/etc/master.passwd</filename> �ļ���ɾ�������û���
 		��ʹ��
 		<command>vipw</command> ������ļ������һ�м��룺</para>
 
 	      <programlisting>+:::::::::</programlisting>
 
 	      <note>
 		<para>��һ�н��� NFS �������Ŀ���ӳ���е��ʺ��ܹ���¼��
 		  Ҳ�кܶ��޸���һ�������� NIS �ͻ����İ취��
 		  ��μ��Ժ�� <link linkend="network-netgroups">netgroups
 		  С��</link> ���˽��һ���������
                   Ҫ�˽������Ϣ�� ���Բ��� O'Reilly ��
 		  <literal>Managing NFS and NIS</literal> �Ȿ�顣</para>
 	      </note>
 
               <note>
                 <para>��Ҫ���ٱ���һ�������ʺ� (Ҳ���Dz�ͨ�� NIS ����) ������
                   <filename>/etc/master.passwd</filename> �ļ��У�
                   ������ʺ�Ӧ����
                   <groupname>wheel</groupname> ��ij�Ա�� ��� NIS �������⣬
                   ����ʺſ�������Զ�̵�¼��
                   ��Ϊ <username>root</username>�� ���������⡣</para>
               </note>
             </step>
 
 	    <step>
 	      <para>Ҫ�� NIS �������ϵ�������Ϣ�� ��Ҫ��
 		<filename>/etc/group</filename> �ļ�ĩβ���룺</para>
 
 	      <programlisting>+:*::</programlisting>
 	    </step>
 	  </procedure>
 
 	  <para>��Ҫ�������� NIS �ͻ��ˣ� ��Ҫ�Գ����û���������ִ���������</para>
 
 	  <screen>&prompt.root; <userinput>/etc/netstart</userinput>
 &prompt.root; <userinput>/etc/rc.d/ypbind start</userinput></screen>
 
 	  <para>�����Щ����֮�� ��Ӧ�ÿ���ͨ������
 	    <command>ypcat passwd</command> ������ NIS �������Ŀ���ӳ���ˡ�</para>
 	</sect4>
       </sect3>
     </sect2>
 
     <sect2>
       <title>NIS �İ�ȫ��</title>
 
       <para>�����ϣ� �κ�Զ���û������Է���һ�� RPC ��
 	&man.ypserv.8; ��������� NIS ӳ������ݣ�
 	���Զ���û��˽����������Ļ���
 	Ҫ��������δ����Ȩ�ķ��ʣ� &man.ypserv.8;
 	֧��һ����Ϊ <quote>securenets</quote> �����ԣ�
 	���Խ�����������һ���ض��Ļ����ϡ� �����������У�
 	&man.ypserv.8; �᳢�Դ�
 	<filename>/var/yp/securenets</filename>
 	�м��� securenet ��Ϣ��</para>
 
       <note>
 	<para>���·����
 	  <option>-p</option> �����ı䡣 ����ļ�������һЩ�
 	  ÿһ���а�����һ�������ʶ���������룬 �м��ÿո�ֿ���
 	  �� <quote>#</quote> ��ͷ���лᱻ��Ϊ��ע�͡�
 	  ʾ���� securenets �ļ�������ʾ��</para>
       </note>
 
       <programlisting># allow connections from local host -- mandatory
 127.0.0.1     255.255.255.255
 # allow connections from any host
 # on the 192.168.128.0 network
 192.168.128.0 255.255.255.0
 # allow connections from any host
 # between 10.0.0.0 to 10.0.15.255
 # this includes the machines in the testlab
 10.0.0.0      255.255.240.0</programlisting>
 
       <para>��� &man.ypserv.8; �ӵ�������ƥ��������һ����ĵ�ַ������
 	������������������ ��֮�� �����󽫱����ԣ� ����¼һ��������Ϣ�� ���
 	<filename>/var/yp/securenets</filename> �ļ������ڣ� ��
 	<command>ypserv</command> ������������������������</para>
 
       <para><command>ypserv</command> ����Ҳ֧��
 	Wietse Venema �� <application>TCP Wrapper</application> ��������
 	������ ����Ա���ܹ�ʹ��
 	<application>TCP Wrapper</application> �������ļ�������
 	<filename>/var/yp/securenets</filename> ��ɷ��ʿ��ơ�</para>
 
       <note>
         <para>���������ַ��ʿ��ƻ��ƶ��ܹ��ṩij�̶ֳȵİ�ȫ��
           ���ǣ� ����Ȩ�˿ڼ��һ����
           �����޷����� <quote>IP α��</quote> ������ ���ķ���ǽӦ����ֹ������
           NIS �йصķ��ʡ�</para>
 
         <para>ʹ�� <filename>/var/yp/securenets</filename> �ķ�������
           ���ܻ��޷�ΪijЩʹ�ó¾ɵ� TCP/IP ʵ�ֵ� NIS �ͻ�������
           ��Щʵ�ֿ��ܻ��ڹ㲥ʱ�� ������λ������Ϊ 0��
           ���ڼ���㲥��ַʱ�����������롣
           ������Щ�������ͨ���޸Ŀͻ����������������
           ����һЩ����Ҳ���ܵ��²��ò���̭��Щ�ͻ���ϵͳ��
           ���߲�ʹ�� <filename>/var/yp/securenets</filename>��</para>
 
         <para>��ʹ�ó¾ɵ� TCP/IP ʵ�ֵ�ϵͳ�ϣ�
 	  ʹ�� <filename>/var/yp/securenets</filename> ��һ���dz�����������
 	  ��Ϊ�⽫�������������ϵ� NIS ɥʧ�󲿷ֹ��ܡ�</para>
 
 	<indexterm><primary>TCP Wrappers</primary></indexterm>
         <para>ʹ�� <application>TCP Wrapper</application>
           �������� �ᵼ������ NIS ����������Ӧ�ӳ����ӡ�
           �����ӵ��ӳ٣� ����ܻᵼ�¿ͻ��˳���ʱ��
           �ر����ڷ�æ��������ߺ�����
           NIS �������ϡ� �������ij���ͻ�����˶�����һЩ�쳣��
           ��Ӧ����Щ�ͻ�����Ϊ NIS �ӷ�������
           ��ǿ������Լ���</para>
       </note>
     </sect2>
 
     <sect2>
       <title>������ijЩ�û���¼</title>
 
       <para>�����ǵ�ʵ�����У� <hostid>basie</hostid> ��̨������
         ��һ̨��Աר�õĹ���վ�� ���Dz�ϣ������̨�����ó� NIS ��
         ���� NIS �������ϵ� <filename>passwd</filename> �ļ���
         ��ͬʱ�����˽�Ա��ѧ�����ʺš� ��ʱӦ����ô����</para>
 
       <para>��һ�ְ취����ֹ�ض����û���¼������ ��ʹ�������� NIS ���ݿ�֮�С�
         Ҫ�����һ������ ֻ��Ҫ�ڿͻ����� <filename>/etc/master.passwd</filename>
         �ļ��м���һЩ
         <literal>-<replaceable>username</replaceable></literal> �������
         ���У� <replaceable>username</replaceable> ��ϣ����ֹ��¼���û�����
         һ���Ƽ�ʹ�� <command>vipw</command> ��������������
         ��Ϊ <command>vipw</command> ������� <filename>/etc/master.passwd</filename>
         �ļ����������޸Ľ��кϷ��Լ�飬
         ���ڱ༭����ʱ���¹����������ݿ⡣ ���磬 ���ϣ����ֹ�û�
         <username>bill</username> ��¼
         <hostid>basie</hostid>�� ����Ӧ�ã�</para>
 
         <screen>basie&prompt.root; <userinput>vipw</userinput>
 <userinput>[��ĩβ���� -bill�� ���˳�]</userinput>
 vipw: rebuilding the database...
 vipw: done
 
 basie&prompt.root; <userinput>cat /etc/master.passwd</userinput>
 
 root:[password]:0:0::0:0:The super-user:/root:/bin/csh
 toor:[password]:0:0::0:0:The other super-user:/root:/bin/sh
 daemon:*:1:1::0:0:Owner of many system processes:/root:/sbin/nologin
 operator:*:2:5::0:0:System &amp;:/:/sbin/nologin
 bin:*:3:7::0:0:Binaries Commands and Source,,,:/:/sbin/nologin
 tty:*:4:65533::0:0:Tty Sandbox:/:/sbin/nologin
 kmem:*:5:65533::0:0:KMem Sandbox:/:/sbin/nologin
 games:*:7:13::0:0:Games pseudo-user:/usr/games:/sbin/nologin
 news:*:8:8::0:0:News Subsystem:/:/sbin/nologin
 man:*:9:9::0:0:Mister Man Pages:/usr/share/man:/sbin/nologin
 bind:*:53:53::0:0:Bind Sandbox:/:/sbin/nologin
 uucp:*:66:66::0:0:UUCP pseudo-user:/var/spool/uucppublic:/usr/libexec/uucp/uucico
 xten:*:67:67::0:0:X-10 daemon:/usr/local/xten:/sbin/nologin
 pop:*:68:6::0:0:Post Office Owner:/nonexistent:/sbin/nologin
 nobody:*:65534:65534::0:0:Unprivileged user:/nonexistent:/sbin/nologin
 +:::::::::
 -bill
 
 basie&prompt.root;</screen>
     </sect2>
 
     <sect2 id="network-netgroups">
       <sect2info>
         <authorgroup>
           <author>
             <firstname>Udo</firstname>
             <surname>Erdelhoff</surname>
             <contrib>Contributed by </contrib>
           </author>
         </authorgroup>
       </sect2info>
 
       <title>ʹ�� Netgroups</title>
       <indexterm><primary>netgroups</primary></indexterm>
 
       <para>ǰһ�ڽ��ܵķ�����
         ������ҪΪ�dz��ٵ��û���/�������������Ĺ�������ʱ����պϡ�
         �ڸ���������ϣ� ��
         <emphasis>һ����</emphasis> ���ǽ�ֹijЩ�û���¼�����еĻ����ϣ�
         ���ߣ� �������뵥�����޸�ÿһ̨���������ã� ��������� NIS ����Ҫ����Խ�ԣ�
         <emphasis>����ʽ</emphasis> ������</para>
 
       <para>NIS ������ԱΪ��������ṩ�Ľ�������� ������
         <emphasis>netgroups</emphasis>�� ���ǵ����ú����壬
         �����Ͽ��Ե�ͬ�� &unix; �ļ�ϵͳ��ʹ�õ��顣
         ��Ҫ������������û�����ֻ��� ID�� �Լ������� netgroup
         ��ͬʱ�����û������� netgroup��</para>
 
       <para>Netgroups ���������������ġ� ���ӵİ��������û��ͻ��������硣
         һ���棬 �������ò�������������ʱ�� ����һ�������õĶ�����
         ����һ���棬 ���ĸ�������ʹ��ͨ���dz��򵥵����Ӻ��ѽ��� netgroup
         ������ʲô�� ��һ�ڵ����ಿ�ֵ����ӽ�չʾ������⡣</para>
 
       <para>��������ʵ�����гɹ��ز��� NIS ��������˾����Ȥ��
         ���������������ǽ� NIS ����չ�� �Ը���У԰�е�һЩ�����Ļ�����
         �������������а��������û����»����� �����Ҫ˵����</para>
 
       <informaltable frame="none" pgwide="1">
         <tgroup cols="2">
           <thead>
             <row>
               <entry>�û���</entry>
               <entry>˵��</entry>
             </row>
           </thead>
 
           <tbody>
             <row>
               <entry><username>alpha</username>, <username>beta</username></entry>
               <entry>IT ���ŵ���ͨ��Ա</entry>
             </row>
 
             <row>
               <entry><username>charlie</username>, <username>delta</username></entry>
               <entry>IT ���ŵ�ѧͽ</entry>
             </row>
 
             <row>
               <entry><username>echo</username>, <username>foxtrott</username>, <username>golf</username>, ...</entry>
               <entry>��ͨ��Ա</entry>
             </row>
 
             <row>
               <entry><username>able</username>, <username>baker</username>, ...</entry>
               <entry>Ŀǰ��ʵϰ��</entry>
             </row>
           </tbody>
         </tgroup>
       </informaltable>
 
       <informaltable frame="none" pgwide="1">
         <tgroup cols="2">
           <thead>
             <row>
               <entry>������</entry>
               <entry>˵��</entry>
             </row>
           </thead>
 
           <tbody>
             <row>
               <!--  Names taken from "Good Omens" by Neil Gaiman and Terry
                     Pratchett.  Many thanks for a brilliant book.  -->
 
               <entry><hostid>war</hostid>, <hostid>death</hostid>,
               <hostid>famine</hostid>,
               <hostid>pollution</hostid></entry>
               <entry>����Ҫ�ķ������� ֻ�� IT
                 ���ŵĹ�Ա��������¼��Щ������</entry>
             </row>
             <row>
               <!-- gluttony was omitted because it was too fat -->
 
               <entry><hostid>pride</hostid>, <hostid>greed</hostid>,
               <hostid>envy</hostid>, <hostid>wrath</hostid>,
               <hostid>lust</hostid>, <hostid>sloth</hostid></entry>
               <entry>��̫��Ҫ�ķ������� ���� IT ���ŵij�Ա��
               �����Ե�¼��Щ������</entry>
             </row>
 
             <row>
               <entry><hostid>one</hostid>, <hostid>two</hostid>,
                 <hostid>three</hostid>, <hostid>four</hostid>,
                 ...</entry>
 
               <entry>��ͨ����վ�� ֻ��
                 <emphasis>������</emphasis> ��Ա��������¼��Щ������</entry>
             </row>
 
             <row>
               <entry><hostid>trashcan</hostid></entry>
               <entry>һ̨�������ؼ����ݵľɻ�����
                 ��ʹ��ʵϰ���� Ҳ������¼����</entry>
             </row>
           </tbody>
         </tgroup>
       </informaltable>
 
       <para>���������ͨ��һ��һ������ֹ�û���ʵ����Щ���ƣ�
         ����Ҫ��ÿһ��ϵͳ�� <filename>passwd</filename> �ļ��У�
         Ϊÿһ����������¼��ϵͳ���û����Ӷ�Ӧ��
         <literal>-<replaceable>user</replaceable></literal> �С�
         ����������κ�һ���� �Ϳ��ܻ�������⡣ �ڽ��г�ʼ����ʱ��
         ��ȷ������Ҳ������ʲô���⣬ �������ո�һ�յ��������û���
         <emphasis>����һ��</emphasis> ��������Ϊ���û�����ij���С�
         �Ͼ��� Murphy ��һ���ֹ۵��ˡ�</para>
 
       <para>ʹ�� netgroups ��������һ״�����Դ�������ô���
         ����Ҫ�����ش���ÿһ���û��� �����Ը����û�һ������ netgroups
         ���ݣ� ���������ֹijһ�� netgroup �����г�Ա��¼��
         ����������µĻ����� ֻ��Ҫ���� netgroup �ĵ�¼���ơ�
         ������������û��� Ҳֻ��Ҫ���û�����һ������ netgroup��
         ��Щ�仯���໥�����ģ� ������Ҫ <quote>��ÿһ���û��ͻ���ִ��
         ����</quote>�� ������� NIS ���þ����˽����Ĺ滮��
         ��ֻ��Ҫ�޸�һ������������ļ��� ���ܹ��������ֹ����ij̨������Ȩ���ˡ�</para>
 
       <para>��һ���dz�ʼ�� NIS ӳ��
         netgroup�� FreeBSD �� &man.ypinit.8; Ĭ������²����������ӳ�䣬
         ������ NIS ʵ���ܹ��ڴ������ӳ��֮�����������ṩ֧�֡�
         Ҫ������ӳ�䣬 �򵥵�����</para>
 
       <screen>ellington&prompt.root; <userinput>vi /var/yp/netgroup</userinput></screen>
 
       <para>����ʼ�������ݡ� �����ǵ������У� ������Ҫ�ĸ� nergruop��
          IT ��Ա�� IT ѧͽ�� ��ͨ��Ա��ʵϰ����</para>
 
       <programlisting>IT_EMP  (,alpha,test-domain)    (,beta,test-domain)
 IT_APP  (,charlie,test-domain)  (,delta,test-domain)
 USERS   (,echo,test-domain)     (,foxtrott,test-domain) \
         (,golf,test-domain)
 INTERNS (,able,test-domain)     (,baker,test-domain)</programlisting>
 
       <para><literal>IT_EMP</literal>, <literal>IT_APP</literal> �ȵȣ�
         �� netgroup �����֡� ÿһ�������е����У�
         ����һЩ�û��ʺš� ���е������ֶ��ǣ�</para>
 
       <orderedlist>
         <listitem>
           <para>����Щ�������ܹ�ʹ����Щ� �����ָ����������
             ���������л����϶���Ч�� ���ָ����������
             ���������ɻ�����</para>
         </listitem>
 
         <listitem>
           <para>������� netgroup ���ʺš�</para>
         </listitem>
 
         <listitem>
           <para>�ʺŵ� NIS �� �����Դ����� NIS
             ���а��ʺŵ��뵽���� netgroup �У�
             ������������ NIS ��Ļ���</para>
         </listitem>
       </orderedlist>
 
       <para>ÿһ���ֶζ����԰���ͨ����� �μ�
         &man.netgroup.5; �˽����ϸ�ڡ�</para>
 
       <note>
         <indexterm><primary>netgroups</primary></indexterm>
         <para>Netgroup ������һ����˵��Ӧ���� 8 ���ַ���
           �ر��ǵ����� NIS �����л�������������������ϵͳ��ʱ��
           ���������ִ�Сд�ģ� ʹ�ô�д��ĸ��Ϊ netgroup �����֣�
           �ܹ����������׵������û��� ������ netgroup �����֡�</para>
 
         <para>ijЩ NIS �ͻ����� (FreeBSD �������Щ) �����޷��������д������
           netgroup�� ���磬 ijЩ���ڰ汾�� &sunos; ���� netgroup
           �а������� 15 �� <emphasis>��</emphasis> ʱ�������⡣
           Ҫ�ƹ�������⣬ ���Դ������ ��netgroup��ÿһ���а������� 15 ���û���
           �Լ�һ���������� ��netgroup �������� netgroup��</para>
 
         <programlisting>BIGGRP1  (,joe1,domain)  (,joe2,domain)  (,joe3,domain) [...]
 BIGGRP2  (,joe16,domain)  (,joe17,domain) [...]
 BIGGRP3  (,joe31,domain)  (,joe32,domain)
 BIGGROUP  BIGGRP1 BIGGRP2 BIGGRP3</programlisting>
 
         <para>�����Ҫ���� 225 ���û��� ���Լ����ظ�����Ĺ��̡�</para>
       </note>
 
       <para>����ַ��µ� NIS ӳ��dz��򵥣�</para>
 
       <screen>ellington&prompt.root; <userinput>cd /var/yp</userinput>
 ellington&prompt.root; <userinput>make</userinput></screen>
 
       <para>����������������� NIS ӳ�䣬 ��
         <filename>netgroup</filename>��
         <filename>netgroup.byhost</filename> ��
         <filename>netgroup.byuser</filename>�� �� &man.ypcat.1;
         ���Լ����Щ NIS ӳ���Ƿ�����ˣ�</para>
 
       <screen>ellington&prompt.user; <userinput>ypcat -k netgroup</userinput>
 ellington&prompt.user; <userinput>ypcat -k netgroup.byhost</userinput>
 ellington&prompt.user; <userinput>ypcat -k netgroup.byuser</userinput></screen>
 
       <para>��һ������������
         Ӧ���� <filename>/var/yp/netgroup</filename> �����������
         �ڶ������ ���û��ָ������ר�е� netgroup��
         ��Ӧ��û������� ���������
         ��������ʾij���û���Ӧ�� netgroup �б���</para>
 
       <para>�ͻ���������Ҳ�ܼ򵥡� Ҫ���÷�����
         <hostid>war</hostid>�� ֻ�����
         &man.vipw.8; ����</para>
 
       <programlisting>+:::::::::</programlisting>
 
       <para>��Ϊ</para>
 
       <programlisting>+@IT_EMP:::::::::</programlisting>
 
       <para>���ڣ� ֻ�� netgroup
         <literal>IT_EMP</literal> �ж�����û��ᱻ���뵽
         <hostid>war</hostid> �Ŀ������ݿ��У�
         ���ֻ����Щ�û��ܹ���¼��</para>
 
       <para>������ �������Ҳ�������� shell ��
 	<literal>~</literal>�� �Լ��������û����������û� ID
 	֮��ʵʩת���ĺ����Ĺ��ܡ� ����֮�� <command>cd
 	~<replaceable>user</replaceable></command> ���������������� ��
 	<command>ls -l</command> Ҳ����ʾ���ֵ� ID �������û�����
 	���� <command>find . -user joe -print</command>
 	��ʧ�ܣ� ������ <errorname>No such user</errorname> �Ĵ�����Ϣ��
 	Ҫ����������⣬ ����Ҫ�������е��û�� ��
 	<emphasis>���������ǵ�¼������</emphasis>��</para>
 
       <para>�����ͨ����
         <filename>/etc/master.passwd</filename> ������һ������ɡ�
         ���е������ǣ�</para>
 
       <para><literal>+:::::::::/sbin/nologin</literal>�� ��˼��
         <quote>�������е�� ��������� shell ���滻Ϊ
         <filename>/sbin/nologin</filename></quote>��
         ͨ���� <filename>/etc/master.passwd</filename>
         ������Ĭ��ֵ�� �����滻��
         <literal>passwd</literal> �е������ֶΡ�</para>
 
       <!-- Been there, done that, got the scars to prove it - ue -->
       <warning>
         <para>���ȷ��
         <literal>+:::::::::/sbin/nologin</literal> ��һ�г�����
         <literal>+@IT_EMP:::::::::</literal> ֮��
         ���� ���д� NIS ������û��ʺŽ��� <filename>/sbin/nologin</filename>
         ��Ϊ��¼ shell��</para>
       </warning>
 
       <para>���������޸�֮�� �� IT ����������Ա��ʱ��
         ֻ���޸�һ�� NIS ӳ����㹻�ˡ� ��Ҳ���������Ƶķ�����
         �ڲ�̫��Ҫ�ķ������ϣ� ����ǰ���ذ汾�� <filename>/etc/master.passwd</filename>
         �е� <literal>+:::::::::</literal> ��Ϊ��</para>
 
       <programlisting>+@IT_EMP:::::::::
 +@IT_APP:::::::::
 +:::::::::/sbin/nologin</programlisting>
 
       <para>��ص�������ͨ����վ��������Ӧ�ǣ�</para>
 
       <programlisting>+@IT_EMP:::::::::
 +@USERS:::::::::
 +:::::::::/sbin/nologin</programlisting>
 
       <para>һ��ƽ�����£� ֱ�����ܺ� ��һ����Է����˱仯��
         IT ����Ҳ��ʼ����ʵϰ���ˡ� IT ʵϰ������ʹ����ͨ���նˣ�
         �Լ���̫��Ҫ�ķ������� �� IT ѧͽ�� ����Ե�¼����������
         ���������µ� netgroup <literal>IT_INTERN</literal>�� �Լ��µ� IT
         ʵϰ������� netgroup ����ʼ�޸�ÿһ̨�����ϵ����á���
         �ϻ�˵�úã�<quote>ǣһ���� ��ȫ��</quote>��</para>
 
       <para>NIS ͨ�� netgroup ������ netgroup ��������
         �����Ա������������Ρ� һ�ֿ��ܵķ����ǽ������ڽ�ɫ�� netgroup��
         ���磬 �����Դ�����Ϊ
         <literal>BIGSRV</literal> �� netgroup�� ���ڶ�������Ҫ�ķ������ϵĵ�¼���ƣ�
         �Լ���һ����Ϊ <literal>SMALLSRV</literal> �� netgroup��
         ���Զ������Ҫ�ķ������� �Լ��������� ������ͨ����վ�� netgroup
         <literal>USERBOX</literal>�� ������ netgroup �е�ÿһ����
         ��������������¼����Щ�����ϵ����� netgroup��
         ���� NIS ӳ���е�����������ʾ��</para>
 
       <programlisting>BIGSRV    IT_EMP  IT_APP
 SMALLSRV  IT_EMP  IT_APP  ITINTERN
 USERBOX   IT_EMP  ITINTERN USERS</programlisting>
 
       <para>���ֶ����¼���Ƶķ�����
         �����ܹ����������鲢�������Ƶ�ʱ����Թ������൱�á�
         ���ҵ��ǣ� ���������⣬ ���dz�������� ����ʱ��
         ��Ҫ������ȥ�����¼���ơ�</para>
 
       <para>�������ص� netgroup ���壬 �Ǵ����������ԸĶ�����һ�ֿ��ܵķ�����
         ��ʱ�� ÿ̨������ <filename>/etc/master.passwd</filename> �У�
         ���������� <quote>+</quote> ��ͷ���С� ��һ����������������¼�� netgroup
         �ʺţ� ���ڶ������������������ʺţ� ���� shell
         ����Ϊ <filename>/sbin/nologin</filename>�� ʹ�� <quote>ȫ��д</quote>
         �Ļ�������Ϊ netgroup ���Ǹ������⡣ ����֮�� ��Щ��Ӧ�������ڣ�</para>
 
       <programlisting>+@<replaceable>BOXNAME</replaceable>:::::::::
 +:::::::::/sbin/nologin</programlisting>
 
       <para>һ�������л����϶�������������޸ģ� ����Ҳ����Ҫ�޸ı��ص�
         <filename>/etc/master.passwd</filename> �ˡ�
         ����δ�����޸Ķ������� NIS ӳ���н��С� ������һ�����ӣ�
         ����չʾ������һӦ���龰������Ҫ�� netgroup ӳ�䣬
         �Լ�����һЩ���õļ��ɣ�</para>
 
       <programlisting># Define groups of users first
 IT_EMP    (,alpha,test-domain)    (,beta,test-domain)
 IT_APP    (,charlie,test-domain)  (,delta,test-domain)
 DEPT1     (,echo,test-domain)     (,foxtrott,test-domain)
 DEPT2     (,golf,test-domain)     (,hotel,test-domain)
 DEPT3     (,india,test-domain)    (,juliet,test-domain)
 ITINTERN  (,kilo,test-domain)     (,lima,test-domain)
 D_INTERNS (,able,test-domain)     (,baker,test-domain)
 #
 # Now, define some groups based on roles
 USERS     DEPT1   DEPT2     DEPT3
 BIGSRV    IT_EMP  IT_APP
 SMALLSRV  IT_EMP  IT_APP    ITINTERN
 USERBOX   IT_EMP  ITINTERN  USERS
 #
 # And a groups for a special tasks
 # Allow echo and golf to access our anti-virus-machine
 SECURITY  IT_EMP  (,echo,test-domain)  (,golf,test-domain)
 #
 # machine-based netgroups
 # Our main servers
 WAR       BIGSRV
 FAMINE    BIGSRV
 # User india needs access to this server
 POLLUTION  BIGSRV  (,india,test-domain)
 #
 # This one is really important and needs more access restrictions
 DEATH     IT_EMP
 #
 # The anti-virus-machine mentioned above
 ONE       SECURITY
 #
 # Restrict a machine to a single user
 TWO       (,hotel,test-domain)
 # [...more groups to follow]</programlisting>
 
       <para>�������ʹ��ij�����ݿ��������ʺţ�
         Ӧ�ÿ���ʹ���������ݿ�ı��湤��������ӳ��ĵ�һ���֡�
         ������ ���û����Զ��ؿ��Է�����Щ�����ˡ�</para>
 
       <para>�������ѣ� ʹ�û��ڻ����� netgroup �����������õġ�
         �������Ϊѧ��ʵ���Ҳ�����ʮ̨�����ϰ�̨ͬ���Ļ�����
         ��Ӧ��ʹ�û��ڽ�ɫ�� netgroup�� �����ǻ��ڻ����� netgroup��
         �Ա�� NIS ӳ��ijߴ籣����һ�������ķ�Χ�ڡ�</para>
     </sect2>
 
     <sect2>
       <title>��Ҫ�μǵ�����</title>
 
       <para>������һЩ������ʹ�� NIS ����ʱ��Ҫע��ĵط���</para>
 
       <itemizedlist>
         <listitem>
           <para>ÿ����Ҫ��ʵ�������������û�ʱ��
             ���� <emphasis>ֻ</emphasis> �� NIS �������ϼ����û���
             ���� <emphasis>һ��Ҫ�ǵ��ؽ� NIS ӳ��</emphasis>��
             ������������������� ���û����޷���¼�� NIS
             ��������֮����κ����������� ���磬 ���Ҫ��ʵ�����������û�
             <username>jsmith</username>�� ������Ҫ��</para>
 
           <screen>&prompt.root; <userinput>pw useradd jsmith</userinput>
 &prompt.root; <userinput>cd /var/yp</userinput>
 &prompt.root; <userinput>make test-domain</userinput></screen>
 
           <para>Ҳ�������� <command>adduser jsmith</command> ������
             <command>pw useradd jsmith</command>.</para>
         </listitem>
         <listitem>
           <para><emphasis>�������õ��ʺ��ų���
             NIS ӳ��֮��</emphasis>�� һ����˵��
             ����ϣ����Щ�����ʺźͿ����ɢ����Щ������Ӧʹ�����ǵ��û��Ļ����ϡ�</para>
         </listitem>
         <listitem>
           <para><emphasis>ȷ�� NIS ���ʹӷ������İ�ȫ��
             �������ܼ�����ͣ��ʱ��</emphasis>��
             ������˹����򵥵عر���Щ������
             ������ʵ���ҵ���Ҳ���޷���¼�ˡ�</para>
 
           <para>���Ǽ���ʽ����ϵͳ������Ļ��ڡ�
             ���û�б����� NIS �������� �����д�����ŭ���û���Ҫ�Ը��ˣ�</para>
         </listitem>
       </itemizedlist>
     </sect2>
 
     <sect2>
       <title>NIS v1 ������</title>
 
       <para>FreeBSD �� <application>ypserv</application> �ṩ��ijЩΪ NIS v1
 	�ͻ��ṩ�����֧�������� FreeBSD �� NIS ʵ�֣�
 	ֻʹ�� NIS v2 Э�飬 ������ʵ�ֿ��ܻ���� v1 Э�飬
 	���ṩ�Ծ�ϵͳ�����¼��������� ����Щϵͳ�ṩ��
 	<application>ypbind</application> �������ȳ��԰� NIS v1
 	�������� ��ʹ���Dz��������Ҫ�� (��Щ�������ܻ�һֱ�㲥��������
 	��ʹ�Ѿ���ij̨ v2 �������õ��˻�ӦҲ�����)��
 	ע�⣬ ����֧��һ��Ŀͻ������ã� ����汾��
 	<application>ypserv</application> �����ܴ��� v1 ��ӳ�䴫������
 	����� ���Ͳ���������֧�� v1 Э��� NIS ���������ʹ�ã�
 	��������Ϊ�����������Ǵӷ������� ���˵��ǣ�
 	�ֽ�Ӧ���Ѿ�û����Ȼ���õ������ķ������ˡ�</para>
     </sect2>
 
     <sect2 id="network-nis-server-is-client">
       <title>ͬʱ��Ϊ NIS �ͻ����� NIS ������</title>
 
       <para>�ڶ��������Ļ����У� ���������ͬʱ��Ϊ NIS �ͻ��� ������
 	<application>ypserv</application> ʱҪ�ر�С�ġ�
 	һ����˵�� ǿ�Ʒ��������Լ�Ҫ���������ǹ㲥������Ҫ�ã�
 	��Ϊ������������ǿ��ܻ��໥�󶨡� ijЩ����Ĺ��ϣ�
 	�ܿ���������ijһ̨������ͣ���� ����������������������������µġ�
 	���գ� ���еĿͻ������ᳬʱ���󶨵�������������
 	������ӳٿ��ܻ��൱�ɹۣ�
 	���һָ�֮����Ȼ�����ٴη������������������</para>
 
       <para>������ǿ��һ̨�����󶨵��ض��ķ������� ����ͨ��
 	<command>ypbind</command> �� <option>-S</option>
 	��������ɵġ� �����ϣ��ÿ������ NIS ������ʱ���ֹ�����������
 	������ <filename>/etc/rc.conf</filename> �м��룺</para>
 
       <programlisting>nis_client_enable="YES"	# run client stuff as well
 nis_client_flags="-S <replaceable>NIS domain</replaceable>,<replaceable>server</replaceable>"</programlisting>
 
       <para>�μ� &man.ypbind.8; ���˽���������</para>
     </sect2>
 
     <sect2>
       <title>�����ʽ</title>
       <indexterm>
         <primary>NIS</primary>
 	<secondary>�����ʽ</secondary>
       </indexterm>
       <para>��ʵ�� NIS ʱ�� �����ʽ�ļ�����������һ����Ϊ���������⡣
 	�������� NIS ������ʹ�� DES ���ܿ�� ����ֻ��֧��ʹ�� DES
 	�Ŀͻ����� ���磬 ���������������
 	&solaris; NIS �ͻ����� �򼸺��϶���Ҫʹ�� DES ���ܿ��</para>
 
       <para>Ҫ������ķ������Ϳͻ���ʹ�õĿ����ʽ��
 	��Ҫ�鿴 <filename>/etc/login.conf</filename>��
 	�������������Ϊʹ�� DES ���ܵĿ�� ��
 	<literal>default</literal> class �����������������</para>
 
       <programlisting>default:\
 	:passwd_format=des:\
 	:copyright=/etc/COPYRIGHT:\
 	[Further entries elided]</programlisting>
 
       <para>����һЩ���ܵ� <literal>passwd_format</literal>
 	���� <literal>blf</literal> �� <literal>md5</literal>
 	(�ֱ��Ӧ�� Blowfish �� MD5 ���ܿ���)��</para>
 
       <para>����޸���
 	<filename>/etc/login.conf</filename>�� �ͱ����ؽ���¼�������ݿ⣬
 	����ͨ����
 	<username>root</username> ������������ij�������ɵģ�</para>
 
       <screen>&prompt.root; <userinput>cap_mkdb /etc/login.conf</userinput></screen>
 
       <note><para>�Ѿ���
 	<filename>/etc/master.passwd</filename> �еĿ���ĸ�ʽ���ᱻ���£�
 	ֱ���û��ڵ�¼�������ݿ��ؽ�
 	<emphasis>֮��</emphasis> �״��޸Ŀ���Ϊֹ��</para></note>
 
       <para>�������� Ϊ��ȷ�����еĿ��������ѡ��ĸ�ʽ�����ˣ�
 	����Ҫ��� <filename>/etc/auth.conf</filename>
 	�� <literal>crypt_default</literal> ����������ѡ��Ŀ����ʽ��
 	Ҫ��ɴ˹����� ����ѡ��ĸ�ʽ�ŵ��б��ĵ�һ� ���磬
 	��ʹ�� DES ���ܵĿ���ʱ�� ��Ӧ��ӦΪ��</para>
 
       <programlisting>crypt_default	=	des blf md5</programlisting>
 
       <para>��ÿһ̨���� &os; �� NIS �������Ϳͻ����������������֮��
 	�Ϳ��Կ϶��������������Ƕ���ʹ��ͬ���Ŀ����ʽ�ˡ� ����� NIS
 	�ͻ�������������֤ʱ�������⣬ ��Ҳ�ǵ�һ�����ܳ�������ĵط���
 	ע�⣺ �����ϣ���ڻ�ϵ������ϲ��� NIS ��������
 	���ܾ���Ҫ������ϵͳ�϶�ʹ�� DES��
 	��Ϊ��������ϵͳ���ܹ�֧�ֵ�����޶ȵĹ�����׼��</para>
     </sect2>
   </sect1>
 
   <sect1 id="network-dhcp">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Greg</firstname>
       	  <surname>Sutter</surname>
 	  <contrib>Written by </contrib>
         </author>
       </authorgroup>
     </sect1info>
     <title>�����Զ����� (DHCP)</title>
 
     <sect2>
       <title>ʲô�� DHCP��</title>
       <indexterm>
         <primary>��̬��������Э��</primary>
         <see>DHCP</see>
       </indexterm>
       <indexterm>
         <primary>Internet Systems Consortium (ISC)</primary>
       </indexterm>
 
       <para>DHCP�� ��̬��������Э�飬 ��һ����ϵͳ�������ӵ������ϣ�
         ����ȡ����Ҫ�����ò����ֶΡ� FreeBSD ʹ������ OpenBSD&nbsp;3.7
 	�� OpenBSD <command>dhclient</command>��
 	�����ṩ�����й��� <command>dhclient</command> ����Ϣ��
 	������ ISC �� OpenBSD DHCP �ͻ��˳���Ϊ׼�ġ� DHCP
 	�������� ISC ��������һ���֡�</para>
     </sect2>
 
     <sect2>
       <title>��һ�ڶ�������Щ����</title>
 
       <para>��һ�������� ISC �� DHCP ϵͳ�еĿͻ��ˣ�
 	�Լ��� ISC DHCP ϵͳ�еķ������˵������
 	�ͻ��˳��� <command>dhclient</command>��
 	���� FreeBSD ��Ϊ����һ�����ṩ�ģ� �����������֣�
 	�����ͨ�� <filename
 	role="package">net/isc-dhcp31-server</filename> port �õ���
 	&man.dhclient.8;�� &man.dhcp-options.5;�� �Լ�
 	&man.dhclient.conf.5; �����ֲᣬ �������������ܵIJο����ף�
 	���Ƿdz����õ���Դ��</para>
     </sect2>
 
     <sect2>
       <title>������</title>
       <indexterm><primary>UDP</primary></indexterm>
       <para>�� DHCP �ͻ����� <command>dhclient</command>
 	�ڿͻ���������ʱ�� ���Ὺʼ�㲥����������Ϣ����Ϣ�� Ĭ������£�
 	��Щ�������� UDP �˿� 68 �ϡ� ������ͨ�� UDP 67
 	������Ӧ�� ��ͻ����ṩһ�� IP ��ַ�� �Լ������йص����ò�����
 	�����������롢 ·������ �Լ� DNS ��������
 	������Щ��Ϣ������ DHCP
 	<quote>lease</quote> ����ʽ������ ����ֻ��һ���ض���ʱ������Ч
 	(������ DHCP ��������ά�������õ�)�� ������
 	��Щ�Ѿ��Ͽ�����Ŀͻ���ʹ�õij¾ɵ� IP ��ַ���ܱ��Զ��ػ����ˡ�</para>
 
       <para>DHCP �ͻ�������Դӷ������˻�ȡ��������Ϣ��
         �����ܻ�õ���Ϣ����ϸ�б��� ��ο�
         &man.dhcp-options.5;��</para>
     </sect2>
 
     <sect2>
       <title>FreeBSD ����</title>
 
       <para>&os; ��ȫ�ؼ����� OpenBSD �� DHCP �ͻ��ˣ�
         <command>dhclient</command>��
         DHCP �ͻ���֧���ڰ�װ����ͻ���ϵͳ�о����ṩ��
         ��ʹ����������Ҫȥ�˽���Щ�Ѿ������� DHCP ������������ľ������ò�����</para>
         <indexterm>
           <primary><application>sysinstall</application></primary>
         </indexterm>
 
         <para><application>sysinstall</application> �ܹ�֧�� DHCP�� ��
           <application>sysinstall</application> ����������ӿ�ʱ��
           ��ѯ�ʵĵڶ���������ǣ� <quote>Do you want to try DHCP configuration of
           the interface? (���Ƿ�ϣ���ڴ˽ӿ��ϳ��� DHCP ����?)</quote>��
           ������϶��Ļش� ������ <command>dhclient</command>��
           һ���ɹ��� ���Զ�����д����������Ϣ��</para>
 
         <para>Ҫ��ϵͳ����ʱʹ�� DHCP�� �������������£�</para>
         <indexterm>
           <primary>DHCP</primary>
           <secondary>����</secondary>
         </indexterm>
 	<itemizedlist>
 	  <listitem>
             <para>�����ں��У� ������� <devicename>bpf</devicename>
 	      �豸�� �����Ҫ�������� ��Ҫ��
 	      <literal>device bpf</literal> ���ӵ��ں˵ı��������ļ��У� �����±����ںˡ�
 	      Ҫ�˽���ڱ����ں˵Ľ�һ����Ϣ�� ��μ� <xref
 	      linkend="kernelconfig"/>��</para> <para><devicename>bpf</devicename>
 	      �豸�Ѿ��� FreeBSD ���а���Ĭ�ϵ� <filename>GENERIC</filename>
 	      �ں˵�һ�����ˣ� ��������û�ж��ں˽��ж��ƣ�
 	      ���ô���һ���µ��ں������ļ��� DHCP ���ܹ����ˡ�</para>
 	    <note>
 	      <para>������Щ��ȫ��ʶ��ǿ������˵��
 	        ��Ӧ��֪�� <devicename>bpf</devicename>
 	        Ҳ�ǰ����������ܹ���ȷ����������֮һ (��Ȼ��
 	        ���ǻ���Ҫ��
 		<username>root</username> ���������)�� <devicename>bpf</devicename>
 		<emphasis>��</emphasis> ʹ�� DHCP ������ģ�
 		��������԰�ȫ�dz����У�
 		��ܿ��ܻ������ɲ��� <devicename>bpf</devicename>
 		���뵽�����ں������У� ֱ���������Ҫʹ�� DHCP
 		Ϊֹ��</para>
 	    </note>
 	  </listitem>
           <listitem>
             <para>�༭���� <filename>/etc/rc.conf</filename> ��������������ã�</para>
 
             <programlisting>ifconfig_fxp0="DHCP"</programlisting>
 
             <note>
               <para>��ؽ� <literal>fxp0</literal>
                 �滻Ϊ��ϣ���Զ����õ�����ӿڵ����֣� ��������
 		 <xref linkend="config-network-setup"/> �ҵ�����һ���Ľ��ܡ�</para>
             </note>
 
             <para>�����ϣ��ʹ����һλ�õ�
               <command>dhclient</command>��
               ������Ҫ�� <command>dhclient</command> ��������������
               ������������������� (������Ҫ�����޸�)��</para>
 
             <programlisting>dhclient_program="/sbin/dhclient"
 dhclient_flags=""</programlisting>
           </listitem>
         </itemizedlist>
 
         <indexterm>
           <primary>DHCP</primary>
           <secondary>������</secondary>
         </indexterm>
         <para>DHCP �������� <application>dhcpd</application>��
           ����Ϊ <filename
           role="package">net/isc-dhcp31-server</filename> port ��һ�����ṩ�ġ�
           ��� port ������ ISC DHCP �����������ĵ���</para>
     </sect2>
 
     <sect2>
       <title>�ļ�</title>
       <indexterm>
         <primary>DHCP</primary>
         <secondary>�����ļ�</secondary>
       </indexterm>
       <itemizedlist>
         <listitem><para><filename>/etc/dhclient.conf</filename></para>
           <para><command>dhclient</command> ��Ҫһ�������ļ���
             <filename>/etc/dhclient.conf</filename>�� һ��˵����
             ����ļ���ֻ����ע�ͣ� ��Ĭ��ֵ�����϶��Ǻ����ġ�
             ��������ļ��� &man.dhclient.conf.5; �����ֲ��н����˽�һ���IJ�����</para>
         </listitem>
 
         <listitem><para><filename>/sbin/dhclient</filename></para>
           <para><command>dhclient</command> ��һ����̬����ģ�
             ������װ�� <filename>/sbin</filename> �С� &man.dhclient.8;
             �����ֲ�����˹���
             <command>dhclient</command> �Ľ�һ��ϸ�ڡ�</para>
         </listitem>
 
         <listitem><para><filename>/sbin/dhclient-script</filename></para>
           <para><command>dhclient-script</command> ��һ�� FreeBSD ר�õ�
             DHCP �ͻ������ýű��� ��
             &man.dhclient-script.8; ���������������
             ��һ����˵�� �û�����Ҫ��������κ��޸ģ�
             ���ܹ���һ��������ת�ˡ�</para>
         </listitem>
 
         <listitem><para><filename>/var/db/dhclient.leases</filename></para>
           <para>DHCP �ͻ������ά��һ�����ݿ���������Ч�� lease��
             ���DZ�����־����ʽ���浽����ļ��С� &man.dhclient.leases.5;
             �����˸�Ϊϸ�µĽ��ܡ�</para>
         </listitem>
       </itemizedlist>
     </sect2>
 
     <sect2>
       <title>���׶���</title>
 
       <para>DHCP �������������
         <ulink url="http://www.freesoft.org/CIE/RFC/2131/">RFC 2131</ulink>��
         ��������������Ϣ��Դ��վ��
         <ulink url="http://www.dhcp.org/"></ulink>
         Ҳ�ṩ���꾡�����ϡ�</para>
     </sect2>
 
     <sect2 id="network-dhcp-server">
 	<title>��װ������ DHCP ������</title>
 
 	<sect3>
 	  <title>��һ�°�����Щ����</title>
 
 	  <para>��һ���ṩ�˹�������� FreeBSD ϵͳ��ʹ�� ISC
 	    (Internet ϵͳЭ��) �� DHCP ʵ���׼������� DHCP ����������Ϣ��</para>
 
 	  <para>DHCP �׼��еķ��������ֲ�û����Ϊ FreeBSD ��һ�������ṩ��
 	    �������Ҫ��װ
 	    <filename role="package">net/isc-dhcp31-server</filename>
 	    port �����ṩ������� ��μ� <xref linkend="ports"/>
 	    ���˽�������ʹ�� Ports Collection �Ľ�һ�����顣</para>
 	</sect3>
 
 	<sect3>
 	  <title>��װ DHCP ������</title>
 	  <indexterm>
 	    <primary>DHCP</primary>
 	    <secondary>��װ</secondary>
 	  </indexterm>
 	  <para>Ϊ�������� FreeBSD ϵͳ�Ͻ��������Ա���Ϊ DHCP ��������ʹ�ã�
 	    ��Ҫ�� &man.bpf.4; �豸������ںˡ� Ҫ���������� ��Ҫ��
 	    <literal>device bpf</literal> ���뵽�����ں������ļ��У�
 	    �����������ںˡ� Ҫ�õ�������������ں˵Ľ�һ����Ϣ�� ��μ�
 	    <xref linkend="kernelconfig"/>��</para>
 
 	  <para><devicename>bpf</devicename> �豸�� FreeBSD ��������
 	    <filename>GENERIC</filename> �ں����Ѿ�����������
 	    �����������ҪΪ���� DHCP �����������ر�ض����ںˡ�</para>
 
 	    <note>
 	      <para>������н�ǿ�İ�ȫ��ʶ�� Ӧ��ע��
 	        <devicename>bpf</devicename> ͬʱҲ�������������ܹ���ȷ�������豸
 		(�������������Ȼ��Ҫ����Ȩ�û���������)��
 		<devicename>bpf</devicename>
 		<emphasis>��</emphasis> ʹ�� DHCP ������ģ�
 		��������԰�ȫ�dz����У� �����ܻ᲻ϣ����
 		<devicename>bpf</devicename> �Ž��ںˣ�
 		ֱ���������Ϊ DHCP �DZ����Ϊֹ��</para>
 	    </note>
 
 	  <para>������Ҫ�����DZ༭ʾ����
 	    <filename>dhcpd.conf</filename>�� ����
 	    <filename role="package">net/isc-dhcp31-server</filename> port
 	    ��װ�� Ĭ������£� ��������Ӧ����
 	    <filename>/usr/local/etc/dhcpd.conf.sample</filename>��
 	    �ڿ�ʼ�޸�֮ǰ�� ����Ҫ��������Ϊ
 	    <filename>/usr/local/etc/dhcpd.conf</filename>��</para>
 	</sect3>
 
 	<sect3>
 	  <title>���� DHCP ������</title>
 	  <indexterm>
 	    <primary>DHCP</primary>
 	    <secondary>dhcpd.conf</secondary>
 	  </indexterm>
 	  <para><filename>dhcpd.conf</filename> ������һϵ�й��������������Ķ��壬
 	    ��������ӿ��԰�������������</para>
 
 	  <programlisting>option domain-name "example.com";<co id="domain-name"/>
 option domain-name-servers 192.168.4.100;<co id="domain-name-servers"/>
 option subnet-mask 255.255.255.0;<co id="subnet-mask"/>
 
 default-lease-time 3600;<co id="default-lease-time"/>
 max-lease-time 86400;<co id="max-lease-time"/>
 ddns-update-style none;<co id="ddns-update-style"/>
 
 subnet 192.168.4.0 netmask 255.255.255.0 {
   range 192.168.4.129 192.168.4.254;<co id="range"/>
   option routers 192.168.4.1;<co id="routers"/>
 }
 
 host mailhost {
   hardware ethernet 02:03:04:05:06:07;<co id="hardware"/>
   fixed-address mailhost.example.com;<co id="fixed-address"/>
 }</programlisting>
 
 	  <calloutlist>
 	    <callout arearefs="domain-name">
 	      <para>���ѡ��ָ�����ṩ���ͻ�����ΪĬ��������������� ��ο�
 		&man.resolv.conf.5; ���˽������һ��������顣</para>
 	    </callout>
 
 	    <callout arearefs="domain-name-servers">
 	      <para>���ѡ������ָ��һ��ͻ���ʹ�õ� DNS ��������
 		����֮���Զ��ŷָ���</para>
 	    </callout>
 
 	    <callout arearefs="subnet-mask">
 	      <para>�ṩ���ͻ������������롣</para>
 	    </callout>
 
 	    <callout arearefs="default-lease-time">
 	      <para>�ͻ�������������Լ����Ч�ڣ� �����û�У�
 		���������ָ��һ����Լ��Ч�ڣ� Ҳ�������ֵ (��λ����)��</para>
 	    </callout>
 
 	    <callout arearefs="max-lease-time">
 	      <para>���Ƿ��������������ַ�����ʱ����
 		����ͻ��������˸��������ڣ� �������õ�һ����ַ��
 		�������ڽ����� <literal>max-lease-time</literal> �롣</para>
 	    </callout>
 
 	    <callout arearefs="ddns-update-style">
 	      <para>���ѡ������ָ�� DHCP ��������һ����ַ�����ܻ��ͷ�ʱ�Ƿ�Ӧ��Ӧ���Ը���
 		DNS�� �� ISC ʵ���У� ��һѡ���� <emphasis>����ָ����</emphasis>��</para>
 	    </callout>
 
 	    <callout arearefs="range">
 	      <para>ָ����ַ���п�������������ͻ����� IP ��ַ��Χ��
 		�������Χ֮�䣬 �Լ���߽�� IP ��ַ��������ͻ�����</para>
 	    </callout>
 
 	    <callout arearefs="routers">
 	      <para>����ͻ�����Ĭ�����ء�</para>
 	    </callout>
 
 	    <callout arearefs="hardware">
 	      <para>������Ӳ�� MAC ��ַ (���� DHCP
 		���������ܹ��ڽӵ�����ʱ֪���������������)��</para>
 	    </callout>
 
 	    <callout arearefs="fixed-address">
 	      <para>ָ�����ǵõ�ͬһ IP ��ַ��������
 		��ע���ڴ˴�ʹ���������ǶԵģ� ��Ϊ DHCP
 		���������ڷ�������ַ��Ϣ֮ǰ���н�����������</para>
 	    </callout>
 	  </calloutlist>
 
 	  <para>�����ƺ�
 	    <filename>dhcpd.conf</filename> ֮�� Ӧ��
 	    <filename>/etc/rc.conf</filename> ������ DHCP ��������
 	    Ҳ�������ӣ�</para>
 
 	  <programlisting>dhcpd_enable="YES"
 dhcpd_ifaces="dc0"</programlisting>
 
 	  <para>�˴��� <literal>dc0</literal> �ӿ���Ӧ��Ϊ DHCP
 	    ��������Ҫ���� DHCP �ͻ�������Ľӿ� (����ж���� ���ÿո�ֿ�)��</para>
 
 	  <para>�������� �������������������������</para>
 
 	  <screen>&prompt.root; <userinput>/usr/local/etc/rc.d/isc-dhcpd start</userinput></screen>
 
 	  <para>���δ������Ҫ�޸ķ����������ã� ������μǷ���
 	    <literal>SIGHUP</literal> �źŸ�
 	    <application>dhcpd</application> �� <emphasis>����</emphasis>
 	    ���������ļ������¼��أ� ����������������������DZȽ��ձ��Լ����
 	    ����Ҫ���� <literal>SIGTERM</literal> �ź���ֹͣ���̣�
 	    Ȼ��ʹ�������������������������</para>
 	</sect3>
 
 	<sect3>
 	  <title>�ļ�</title>
 	  <indexterm>
 	    <primary>DHCP</primary>
 	    <secondary>�����ļ�</secondary>
 	  </indexterm>
 	  <itemizedlist>
 	    <listitem><para><filename>/usr/local/sbin/dhcpd</filename></para>
 	      <para><application>dhcpd</application> �Ǿ�̬���ӵģ� ����װ��
 		<filename>/usr/local/sbin</filename> �С� �� port ��װ��
 		&man.dhcpd.8; �����ֲ��ṩ�˹���
 		<application>dhcpd</application> ��Ϊ�꾡����Ϣ��</para>
 	    </listitem>
 
 	    <listitem><para><filename>/usr/local/etc/dhcpd.conf</filename></para>
 	      <para><application>dhcpd</application> ��Ҫ�����ļ���
 		�� <filename>/usr/local/etc/dhcpd.conf</filename>
 		���ܹ���ͻ����ṩ���� ����ļ���Ҫ����Ӧ�ṩ���ͻ�����������Ϣ��
 		�Լ����ڷ��������е�������Ϣ�� �������ļ�����ϸ������������ port
 		��װ�� &man.dhcpd.conf.5; �����ֲ����ҵ���</para>
 	    </listitem>
 
 	    <listitem><para><filename>/var/db/dhcpd.leases</filename></para>
 	      <para>DHCP ��������ά��һ����ǩ�������õ�ַ���ݿ⣬
 		������������ļ��У� ����ļ�������־����ʽ����ġ�
 		�� port ��װ��
 		&man.dhcpd.leases.5; �����ֲ��ṩ�˸���ϸ��������</para>
 	    </listitem>
 
 	    <listitem><para><filename>/usr/local/sbin/dhcrelay</filename></para>
 	      <para><application>dhcrelay</application> �ڸ�Ϊ���ӵĻ����У�
 		��������֧��ʹ�� DHCP ������ת���������һ�����������ϵ�
 		DHCP �������� �������Ҫ������ܣ� ��Ҫ��װ <filename
 		role="package">net/isc-dhcp31-relay</filename> port��
 		&man.dhcrelay.8; �����ֲ��ṩ�˸�Ϊ�꾡�Ľ��ܡ�</para>
 	    </listitem>
 	  </itemizedlist>
 	</sect3>
 
       </sect2>
 
   </sect1>
 
   <sect1 id="network-dns">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Chern</firstname>
           <surname>Lee</surname>
           <contrib>Contributed by </contrib>
         </author>
 
 	<author>
 	  <firstname>Tom</firstname>
 	  <surname>Rhodes</surname>
 	</author>
 
 	<author>
 	  <firstname>Daniel</firstname>
 	  <surname>Gerzo</surname>
 	</author>
       </authorgroup>
     </sect1info>
     <title>����ϵͳ (<acronym>DNS</acronym>)</title>
 
     <sect2>
       <title>����</title>
       <indexterm><primary>BIND</primary></indexterm>
 
       <para>&os; ��Ĭ�������ʹ��һ���汾�� BIND (Berkeley
         Internet Name Domain)�� ����Ŀǰ��Ϊ���е� <acronym>DNS</acronym> Э��ʵ�֡�
         <acronym>DNS</acronym> ��һ��Э�飬 ����ͨ����������ͬ <acronym>IP</acronym>  ��ַ�໥��Ӧ��
         ���磬 ��ѯ <hostid role="fqdn">www.FreeBSD.org</hostid>
         ���õ� &os; Project �� web �������� <acronym>IP</acronym>  ��ַ�� ����ѯ <hostid
         role="fqdn">ftp.FreeBSD.org</hostid> �򽫵õ���Ӧ�� <acronym>FTP</acronym>  ������
         <acronym>IP</acronym>  ��ַ�� ���Ƶأ� Ҳ�������෴�����顣 ��ѯ <acronym>IP</acronym>
         ��ַ���Եõ����������� ��Ȼ�� ��� <acronym>DNS</acronym>
         ��ѯ������Ҫ��ϵͳ������������������</para>
 
       <para>Ŀǰ�� Ĭ�������&os; ʹ�õ��� <acronym>BIND</acronym>9
 	<acronym>DNS</acronym> ���������� �����ڽ���ϵͳ�еİ汾�ṩ����ǿ�İ�ȫ���ԡ�
 	�µ��ļ�Ŀ¼�ṹ�� �Լ��Զ��� &man.chroot.8; ���á�</para>
 
       <indexterm><primary>DNS</primary></indexterm>
       <para>�� Internet �ϵ� <acronym>DNS</acronym> ��ͨ��һ�׽�Ϊ���ӵ�Ȩ��������ϵͳ��
 	�������� (<acronym>TLD</acronym>)�� �Լ�һϵ��С��ģ�ģ�
 	�ṩ���������������񲢶�������Ϣ���л����������������ɵġ�</para>
 
       <para>Ŀǰ�� BIND ��
 	Internet Systems Consortium
         <ulink url="https://www.isc.org/"></ulink>
         ����</para>
     </sect2>
 
     <sect2>
       <title>����</title>
 
       <para>Ҫ��������ĵ��� ��Ҫ�����˽�һЩ��ص�
 	 <acronym>DNS</acronym> ���</para>
 
       <indexterm><primary>resolver (������)</primary></indexterm>
       <indexterm><primary>reverse DNS (���� DNS)</primary></indexterm>
       <indexterm><primary>root zone (����)</primary></indexterm>
 
       <informaltable frame="none" pgwide="1">
 	<tgroup cols="2">
 	  <colspec colwidth="1*"/>
 	  <colspec colwidth="3*"/>
 
 	  <thead>
 	    <row>
 	      <entry>����</entry>
 	      <entry>����</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry>���� <acronym>DNS</acronym></entry>
 	      <entry>������ӳ�䵽 IP ��ַ</entry>
 	    </row>
 
 	    <row>
 	      <entry>ԭ�� (Origin)</entry>
 	      <entry>��ʾ�ض����ļ����ڵ���</entry>
 	    </row>
 
 	    <row>
 	      <entry><application>named</application>, BIND</entry>
 	      <entry>�� &os; �� BIND �����������������ij������</entry>
 	    </row>
 
 	    <row>
 	      <entry>������ (Resolver)</entry>
 	      <entry>�����������������������ѯ������Ϣ��һ��ϵͳ����</entry>
 	    </row>
 
 	    <row>
 	      <entry>���� <acronym>DNS</acronym></entry>
 	      <entry>�� <acronym>IP</acronym> ��ַӳ��Ϊ������</entry>
 	    </row>
 
 	    <row>
 	      <entry>����</entry>
 
 	      <entry>Internet ���ε���㡣 ���е����ڸ���֮�£�
 		�����ļ�ϵͳ�У� �ļ����ڸ�Ŀ¼֮��������</entry>
 	    </row>
 
 	    <row>
 	      <entry>�� (Zone)</entry>
 	      <entry>�������� ���� ������ͬһ���������� <acronym>DNS</acronym> ��һ���֡�</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
 
       <indexterm>
 	<primary>��</primary>
 	<secondary>����</secondary>
       </indexterm>
 
       <para>������ӣ�</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><hostid>.</hostid> �ڱ��ĵ���ͨ��ָ������</para>
 	</listitem>
 
 	<listitem>
 	  <para><hostid>org.</hostid> �Ǹ���֮�µ�һ����������
 	    (<acronym>TLD</acronym>)��</para>
 	</listitem>
 
 	<listitem>
 	  <para><hostid role="domainname">example.org.</hostid> ����
 	    <hostid>org.</hostid>
 	    <acronym>TLD</acronym> ֮�µ�һ����</para>
 	</listitem>
 
 	<listitem>
 	  <para><hostid>1.168.192.in-addr.arpa</hostid> ��һ����ʾ����
 	    <hostid role="ipaddr">192.168.1.*</hostid>
 	    <acronym>IP</acronym> ��ַ�ռ��� <acronym>IP</acronym>
 	    ��ַ����</para>
 	</listitem>
       </itemizedlist>
 
       <para>���������� ������Խϸ�ڵIJ��ֻ�Խ������֡� ���磬 <hostid
 	role="domainname">example.org.</hostid> �ͱ�
 	<hostid>org.</hostid> ��Χ��С�� ���Ƶ� <hostid>org.</hostid> �ֱȸ����С��
 	�����������ֵĸ�����ļ�ϵͳʮ�����ƣ�
 	<filename class="directory">/dev</filename> Ŀ¼�ڸ�Ŀ¼֮�£� �ȵȡ�</para>
     </sect2>
 
     <sect2>
       <title>��������������������</title>
 
       <para>����������ͨ������������ʽ�� Ȩ��������������
 	�Լ�����������������</para>
 
       <para>���������Ҫ��Ȩ��������������</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>��Ҫ��ȫ�����ṩ <acronym>DNS</acronym> ��Ϣ��
 	    �����������Ȩ��Ӧ��</para>
 	</listitem>
 
 	<listitem>
 	  <para>ע�������� <hostid role="domainname">example.org</hostid>
 	    ���� ����Ҫ�� <acronym>IP</acronym> ָ�������µ��������ϡ�</para>
 	</listitem>
 
 	<listitem>
 	  <para>ij�� <acronym>IP</acronym> ��ַ����Ҫ����
 	    <acronym>DNS</acronym> �� (<acronym>IP</acronym> ��������)��</para>
 	</listitem>
 
 	<listitem>
 	  <para>���ݷ������� ��˵�Ĵ� (slave) ��������
 	    ����������������������޷�����ʱ��Ӧ���ѯ����</para>
 	</listitem>
       </itemizedlist>
 
       <para>���������Ҫ�л���������������</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>���ص� <acronym>DNS</acronym> �������ܹ����棬
 	    ����ֱ�������������������������صõ�Ӧ��</para>
 	</listitem>
       </itemizedlist>
 
       <para>�����˲�ѯ <hostid
 	role="fqdn">www.FreeBSD.org</hostid> ʱ��������ͨ�������ϼ�
 	<acronym>ISP</acronym> �������������������� ����û�Ӧ�� ����б��صĻ���
 	<acronym>DNS</acronym> �������� ��ѯֻ���ڵ�һ�α����� <acronym>DNS</acronym>
 	�����������ⲿ���硣 �����IJ�ѯ���ᷢ��������⣬
 	��Ϊ�����Ѿ����ڱ��صĻ����ˡ�</para>
     </sect2>
 
     <sect2>
       <title>DNS �������</title>
       <para>�� &os; �У� BIND ������򱻳�Ϊ
 	<application>named</application>��</para>
 
       <informaltable frame="none" pgwide="1">
 	<tgroup cols="2">
 	  <thead>
 	    <row>
 	      <entry>�ļ�</entry>
 	      <entry>����</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry>&man.named.8;</entry>
 	      <entry>BIND �������</entry>
 	    </row>
 
 	    <row>
 	      <entry>&man.rndc.8;</entry>
 	      <entry>����������Ƴ���</entry>
 	    </row>
 
 	    <row>
 	      <entry><filename class="directory">/etc/namedb</filename></entry>
 	      <entry>BIND ���������Ϣ��λ�á�</entry>
 	    </row>
 
 	    <row>
 	      <entry><filename>/etc/namedb/named.conf</filename></entry>
 	      <entry>�������������ļ�</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
 
       <para>���ڷ����������õ�������ʲ�ͬ��
 	��Ķ����ļ�һ����ŵ�
 	<filename class="directory">/etc/namedb</filename> Ŀ¼�е� <filename
 	class="directory">master</filename>�� <filename
 	class="directory">slave</filename>�� �� <filename
 	class="directory">dynamic</filename> ��Ŀ¼�С�
 	��Щ�ļ����ṩ����������������Ӧ��ѯʱ����Ҫ�� <acronym>DNS</acronym> ��Ϣ��</para>
     </sect2>
 
     <sect2>
       <title>���� BIND</title>
 
       <indexterm>
         <primary>BIND</primary>
 	<secondary>starting (����)</secondary>
       </indexterm>
 
       <para>���� BIND ��Ĭ�ϰ�װ�ģ� �����������Զ��Ժܼ򵥡�</para>
 
       <para>Ĭ�ϵ� <application>named</application> ���ã� ����
 	&man.chroot.8; �������ṩ������������������
 	����ֻ���ڼ������� IPv4 �ػ���ַ (127.0.0.1)��
 	���ϣ��������һ���ã� ����ʹ����������</para>
 
       <screen>&prompt.root; <userinput>/etc/rc.d/named onestart</userinput></screen>
 
       <para>���ϣ�� <application>named</application>
          ������ÿ��������ʱ���ܹ������� ��Ҫ��
          <filename>/etc/rc.conf</filename> �м��룺</para>
 
       <programlisting>named_enable="YES"</programlisting>
 
       <para>��Ȼ�� ��������ĵ������ܵ�����ѡ��֮�⣬ ��
 	<filename>/etc/namedb/named.conf</filename> �л��кܶ�������ѡ�
 	������ �������Ҫ�˽� &os; ���������� <application>named</application>
 	����Щѡ��Ļ��� ����Բ鿴
 	<filename>/etc/defaults/rc.conf</filename> �е�
 	<literal>named_<replaceable>*</replaceable></literal> ������ ���ο�
 	&man.rc.conf.5; �����ֲᡣ ����֮�⣬
 	<xref linkend="configtuning-rcd"/> Ҳ��һ����������㡣</para>
     </sect2>
 
     <sect2>
       <title>�����ļ�</title>
 
       <indexterm>
 	<primary>BIND</primary>
 	<secondary>configuration files (�����ļ�)</secondary>
       </indexterm>
 
       <para>Ŀǰ�� <application>named</application> �������ļ������
 	<filename class="directory">/etc/namedb</filename> Ŀ¼��
 	��ʹ��ǰӦ������Ҫ�����޸ģ�
 	������ֻ����������ɼ򵥵�������������
 	���Ŀ¼ͬʱҲ�������о���������õĵط���</para>
 
       <sect3>
 	<title><filename>/etc/namedb/named.conf</filename></title>
 
 	<programlisting>// &dollar;FreeBSD&dollar;
 //
 // Refer to the named.conf(5) and named(8) man pages, and the documentation
 // in /usr/share/doc/bind9 for more details.
 //
 // If you are going to set up an authoritative server, make sure you
 // understand the hairy details of how DNS works.  Even with
 // simple mistakes, you can break connectivity for affected parties,
 // or cause huge amounts of useless Internet traffic.
 
 options {
 	// Relative to the chroot directory, if any
 	directory	"/etc/namedb";
 	pid-file	"/var/run/named/pid";
 	dump-file	"/var/dump/named_dump.db";
 	statistics-file	"/var/stats/named.stats";
 
 // If named is being used only as a local resolver, this is a safe default.
 // For named to be accessible to the network, comment this option, specify
 // the proper IP address, or delete this option.
 	listen-on	{ 127.0.0.1; };
 
 // If you have IPv6 enabled on this system, uncomment this option for
 // use as a local resolver.  To give access to the network, specify
 // an IPv6 address, or the keyword "any".
 //	listen-on-v6	{ ::1; };
 
 // These zones are already covered by the empty zones listed below.
 // If you remove the related empty zones below, comment these lines out.
 	disable-empty-zone "255.255.255.255.IN-ADDR.ARPA";
 	disable-empty-zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA";
 	disable-empty-zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA";
 
 // If you've got a DNS server around at your upstream provider, enter
 // its IP address here, and enable the line below.  This will make you
 // benefit from its cache, thus reduce overall DNS traffic in the Internet.
 /*
 	forwarders {
 		127.0.0.1;
 	};
 */
 
 // If the 'forwarders' clause is not empty the default is to 'forward first'
 // which will fall back to sending a query from your local server if the name
 // servers in 'forwarders' do not have the answer.  Alternatively you can
 // force your name server to never initiate queries of its own by enabling the
 // following line:
 //	forward only;
 
 // If you wish to have forwarding configured automatically based on
 // the entries in /etc/resolv.conf, uncomment the following line and
 // set named_auto_forward=yes in /etc/rc.conf.  You can also enable
 // named_auto_forward_only (the effect of which is described above).
 //	include "/etc/namedb/auto_forward.conf";</programlisting>
 
 	<para>����ע�����ԣ� ���ϣ�����ϼ����������棬
 	  �����ڴ˴����� <literal>forwarders</literal>��
 	  ��������£� �������������𼶵ز�ѯ
 	  Internet ���ҵ��ض��������������� ֱ���õ���Ϊֹ��
           ���ѡ��������Ȳ�ѯ�ϼ����������� (�������ṩ������������)��
           �Ӷ������ǵĻ����еõ������ ����ϼ�������������һ����æ�ĸ���������������
           ���������������ڸ��Ʒ���Ʒ�ʡ�</para>
 
 	<warning><para><hostid role="ipaddr">127.0.0.1</hostid>
             <emphasis>����</emphasis> ����������
             һ��Ҫ�ѵ�ַ��Ϊ���ϼ��������� <acronym>IP</acronym> ��ַ��</para>
         </warning>
 
 	<programlisting>	/*
 	   Modern versions of BIND use a random UDP port for each outgoing
 	   query by default in order to dramatically reduce the possibility
 	   of cache poisoning.  All users are strongly encouraged to utilize
 	   this feature, and to configure their firewalls to accommodate it.
 
 	   AS A LAST RESORT in order to get around a restrictive firewall
 	   policy you can try enabling the option below.  Use of this option
 	   will significantly reduce your ability to withstand cache poisoning
 	   attacks, and should be avoided if at all possible.
 
 	   Replace NNNNN in the example with a number between 49160 and 65530.
 	*/
 	// query-source address * port NNNNN;
 };
 
 // If you enable a local name server, don't forget to enter 127.0.0.1
 // first in your /etc/resolv.conf so this server will be queried.
 // Also, make sure to enable it in /etc/rc.conf.
 
 // The traditional root hints mechanism. Use this, OR the slave zones below.
 zone "." { type hint; file "named.root"; };
 
 /*	Slaving the following zones from the root name servers has some
 	significant advantages:
 	1. Faster local resolution for your users
 	2. No spurious traffic will be sent from your network to the roots
 	3. Greater resilience to any potential root server failure/DDoS
 
 	On the other hand, this method requires more monitoring than the
 	hints file to be sure that an unexpected failure mode has not
 	incapacitated your server.  Name servers that are serving a lot
 	of clients will benefit more from this approach than individual
 	hosts.  Use with caution.
 
 	To use this mechanism, uncomment the entries below, and comment
 	the hint zone above.
 */
 /*
 zone "." {
 	type slave;
 	file "slave/root.slave";
 	masters {
 		192.5.5.241;	// F.ROOT-SERVERS.NET.
 	};
 	notify no;
 };
 zone "arpa" {
 	type slave;
 	file "slave/arpa.slave";
 	masters {
 		192.5.5.241;	// F.ROOT-SERVERS.NET.
 	};
 	notify no;
 };
 zone "in-addr.arpa" {
 	type slave;
 	file "slave/in-addr.arpa.slave";
 	masters {
 		192.5.5.241;	// F.ROOT-SERVERS.NET.
 	};
 	notify no;
 };
 */
 
 /*	Serving the following zones locally will prevent any queries
 	for these zones leaving your network and going to the root
 	name servers.  This has two significant advantages:
 	1. Faster local resolution for your users
 	2. No spurious traffic will be sent from your network to the roots
 */
 // RFC 1912
 zone "localhost"	{ type master; file "master/localhost-forward.db"; };
 zone "127.in-addr.arpa" { type master; file "master/localhost-reverse.db"; };
 zone "255.in-addr.arpa"	{ type master; file "master/empty.db"; };
 
 // RFC 1912-style zone for IPv6 localhost address
 zone "0.ip6.arpa"	{ type master; file "master/localhost-reverse.db"; };
 
 // "This" Network (RFCs 1912 and 3330)
 zone "0.in-addr.arpa"		{ type master; file "master/empty.db"; };
 
 // Private Use Networks (RFC 1918)
 zone "10.in-addr.arpa"		{ type master; file "master/empty.db"; };
 zone "16.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
 zone "17.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
 zone "18.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
 zone "19.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
 zone "20.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
 zone "21.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
 zone "22.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
 zone "23.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
 zone "24.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
 zone "25.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
 zone "26.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
 zone "27.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
 zone "28.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
 zone "29.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
 zone "30.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
 zone "31.172.in-addr.arpa"	{ type master; file "master/empty.db"; };
 zone "168.192.in-addr.arpa"	{ type master; file "master/empty.db"; };
 
 // Link-local/APIPA (RFCs 3330 and 3927)
 zone "254.169.in-addr.arpa"	{ type master; file "master/empty.db"; };
 
 // TEST-NET for Documentation (RFC 3330)
 zone "2.0.192.in-addr.arpa"	{ type master; file "master/empty.db"; };
 
 // Router Benchmark Testing (RFC 3330)
 zone "18.198.in-addr.arpa"	{ type master; file "master/empty.db"; };
 zone "19.198.in-addr.arpa"	{ type master; file "master/empty.db"; };
 
 // IANA Reserved - Old Class E Space
 zone "240.in-addr.arpa"		{ type master; file "master/empty.db"; };
 zone "241.in-addr.arpa"		{ type master; file "master/empty.db"; };
 zone "242.in-addr.arpa"		{ type master; file "master/empty.db"; };
 zone "243.in-addr.arpa"		{ type master; file "master/empty.db"; };
 zone "244.in-addr.arpa"		{ type master; file "master/empty.db"; };
 zone "245.in-addr.arpa"		{ type master; file "master/empty.db"; };
 zone "246.in-addr.arpa"		{ type master; file "master/empty.db"; };
 zone "247.in-addr.arpa"		{ type master; file "master/empty.db"; };
 zone "248.in-addr.arpa"		{ type master; file "master/empty.db"; };
 zone "249.in-addr.arpa"		{ type master; file "master/empty.db"; };
 zone "250.in-addr.arpa"		{ type master; file "master/empty.db"; };
 zone "251.in-addr.arpa"		{ type master; file "master/empty.db"; };
 zone "252.in-addr.arpa"		{ type master; file "master/empty.db"; };
 zone "253.in-addr.arpa"		{ type master; file "master/empty.db"; };
 zone "254.in-addr.arpa"		{ type master; file "master/empty.db"; };
 
 // IPv6 Unassigned Addresses (RFC 4291)
 zone "1.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "3.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "4.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "5.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "6.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "7.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "8.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "9.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "a.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "b.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "c.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "d.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "e.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "0.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "1.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "2.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "3.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "4.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "5.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "6.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "7.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "8.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "9.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "a.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "b.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "0.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "1.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "2.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "3.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "4.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "5.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "6.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "7.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 
 // IPv6 ULA (RFC 4193)
 zone "c.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "d.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 
 // IPv6 Link Local (RFC 4291)
 zone "8.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "9.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "a.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "b.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 
 // IPv6 Deprecated Site-Local Addresses (RFC 3879)
 zone "c.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "d.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "e.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 zone "f.e.f.ip6.arpa"		{ type master; file "master/empty.db"; };
 
 // IP6.INT is Deprecated (RFC 4159)
 zone "ip6.int"			{ type master; file "master/empty.db"; };
 
 // NB: Do not use the IP addresses below, they are faked, and only
 // serve demonstration/documentation purposes!
 //
 // Example slave zone config entries.  It can be convenient to become
 // a slave at least for the zone your own domain is in.  Ask
 // your network administrator for the IP address of the responsible
 // master name server.
 //
 // Do not forget to include the reverse lookup zone!
 // This is named after the first bytes of the IP address, in reverse
 // order, with ".IN-ADDR.ARPA" appended, or ".IP6.ARPA" for IPv6.
 //
 // Before starting to set up a master zone, make sure you fully
 // understand how DNS and BIND work.  There are sometimes
 // non-obvious pitfalls.  Setting up a slave zone is usually simpler.
 //
 // NB: Don't blindly enable the examples below. :-)  Use actual names
 // and addresses instead.
 
 /* An example dynamic zone
 key "exampleorgkey" {
 	algorithm hmac-md5;
 	secret "sf87HJqjkqh8ac87a02lla==";
 };
 zone "example.org" {
 	type master;
 	allow-update {
 		key "exampleorgkey";
 	};
 	file "dynamic/example.org";
 };
 */
 
 /* Example of a slave reverse zone
 zone "1.168.192.in-addr.arpa" {
 	type slave;
 	file "slave/1.168.192.in-addr.arpa";
 	masters {
 		192.168.1.1;
 	};
 };
 */</programlisting>
 
 	<para>�� <filename>named.conf</filename> ��
 	  �������˴���ת����ͷ�����������ӡ�</para>
 
 	<para>����������� �ͱ����� <filename>named.conf</filename> �м����Ӧ����Ŀ��</para>
 
 	<para>���磬 ����
 	  <hostid role="domainname">example.org</hostid> �����ļ���������������������</para>
 
 	<programlisting>zone "example.org" {
 	type master;
 	file "master/example.org";
 };</programlisting>
 
 	<para>�� <option>type</option> �������ʾ��������
 	  ����һ������ ����Ϣ������
 	  <filename>/etc/namedb/master/example.org</filename>
 	  �У� �� <option>file</option> �����ʾ��</para>
 
 	<programlisting>zone "example.org" {
 	type slave;
 	file "slave/example.org";
 };</programlisting>
 
 	<para>�ڴ���������У� ��ָ���������Ϣ������������������ݹ�����
 	  �����浽��Ӧ���ļ��С� �������������������򲻿ɴ�ʱ��
 	  ����������������һ�ݿ��õ�������Ϣ�� �Ӷ��ܹ������ṩ����</para>
       </sect3>
 
       <sect3>
 	<title>���ļ�</title>
 	<indexterm>
 	  <primary>BIND</primary>
 	  <secondary>zone files (���ļ�)</secondary>
 	</indexterm>
 
 	<para>���������չʾ������ <hostid
 	  role="domainname">example.org</hostid> �������ļ� (�����
 	  <filename>/etc/namedb/master/example.org</filename>)��</para>
 
 	<programlisting>&dollar;TTL 3600        ; 1 hour default TTL
 example.org.    IN      SOA      ns1.example.org. admin.example.org. (
                                 2006051501      ; Serial
                                 10800           ; Refresh
                                 3600            ; Retry
                                 604800          ; Expire
                                 300             ; Negative Reponse TTL
                         )
 
 ; DNS Servers
                 IN      NS      ns1.example.org.
                 IN      NS      ns2.example.org.
 
 ; MX Records
                 IN      MX 10   mx.example.org.
                 IN      MX 20   mail.example.org.
 
                 IN      A       192.168.1.1
 
 ; Machine Names
 localhost       IN      A       127.0.0.1
 ns1             IN      A       192.168.1.2
 ns2             IN      A       192.168.1.3
 mx              IN      A       192.168.1.4
 mail            IN      A       192.168.1.5
 
 ; Aliases
 www             IN      CNAME   example.org.</programlisting>
 
         <para>��ע���� <quote>.</quote> ��β����������ȫ���������� ����βû��
           <quote>.</quote> �����������ԭ����������� ���磬
           <literal>ns1</literal> ����ת��Ϊ
           <literal>ns1.<replaceable>example.org.</replaceable></literal></para>
 
         <para>����Ϣ�ļ��ĸ�ʽ���£�</para>
 
         <programlisting>��¼��          IN ��¼����     ֵ</programlisting>
 
 	<indexterm>
 	  <primary>DNS</primary>
 	  <secondary>��¼</secondary>
 	</indexterm>
 
         <para>��õ� DNS ��¼��</para>
 
 	<variablelist>
 	  <varlistentry>
 	    <term>SOA</term>
 
 	    <listitem><para>��Ȩ����ʼ</para></listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term>NS</term>
 
 	    <listitem><para>Ȩ������������</para></listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term>A</term>
 
 	    <listitem><para>������ַ</para></listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term>CNAME</term>
 
 	    <listitem><para>������Ӧ����������</para></listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term>MX</term>
 
 	    <listitem><para>�ʼ����ݷ�����</para></listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term>PTR</term>
 
 	    <listitem><para>����ָ�� (���ڷ��� DNS)
 	      </para></listitem>
 	  </varlistentry>
 	</variablelist>
 
         <programlisting>example.org. IN SOA ns1.example.org. admin.example.org. (
                         2006051501      ; Serial
                         10800           ; Refresh after 3 hours
                         3600            ; Retry after 1 hour
                         604800          ; Expire after 1 week
                         300 )           ; Negative Reponse TTL</programlisting>
 
 	<variablelist>
 	  <varlistentry>
 	    <term><hostid role="domainname">example.org.</hostid></term>
 
 	    <listitem>
 	      <para>������ ͬʱҲ���������Ϣ�ļ���ԭ�㡣</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term><hostid role="fqdn">ns1.example.org.</hostid></term>
 
 	    <listitem>
 	      <para>�������/Ȩ��������������</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term><literal>admin.example.org.</literal></term>
 
 	    <listitem>
 	      <para>����ĸ����˵ĵ����ʼ���ַ��
 		���� <quote>@</quote>
 		��Ҫ���� (<email>admin@example.org</email> ��Ӧ
 		<literal>admin.example.org</literal>)</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term><literal>2006051501</literal></term>
 
 	    <listitem>
 	      <para>�ļ�����š� ÿ���޸����ļ�ʱ����������������֡�
 		�ֽ� �������Ա�ῼ��ʹ��
 		<literal>yyyymmddrr</literal> �����ĸ�ʽ����ʾ��š�
 		<literal>2006051501</literal> ͨ����ʾ�ϴ��޸���
 		05/15/2006�� �������
 		<literal>01</literal> ���ʾ������ĵ�һ���޸ġ�
 		��ŷdz���Ҫ�� ������֪ͨ����������������ݡ�</para>
 	    </listitem>
 	  </varlistentry>
 	</variablelist>
 
         <programlisting>       IN NS           ns1.example.org.</programlisting>
 
         <para>����һ�� NS � ÿ��׼���ṩȨ��Ӧ��ķ�������������һ����Ӧ�</para>
 
         <programlisting>localhost       IN      A       127.0.0.1
 ns1             IN      A       192.168.1.2
 ns2             IN      A       192.168.1.3
 mx              IN      A       192.168.1.4
 mail            IN      A       192.168.1.5</programlisting>
 
         <para>A ��¼ָ���˻������� ������ǰ���������ģ�
           <hostid role="fqdn">ns1.example.org</hostid> ������Ϊ
           <hostid role="ipaddr">192.168.1.2</hostid>��</para>
 
         <programlisting>                IN      A       192.168.1.1</programlisting>
 
 	<para>��һ�аѵ�ǰԭ�� <hostid role="domainname">example.org</hostid>
 	  ָ��Ϊʹ�� IP ��ַ
 	  <hostid role="ipaddr">192.168.1.1</hostid>��</para>
 
         <programlisting>www             IN CNAME        @</programlisting>
 
         <para>������ (CNAME) ��¼ͨ������Ϊij̨����ָ��������
           ����������� �� <hostid>www</hostid>
           ָ������ <quote>��</quote> ������һ��������
           ���ߵ�����������
 	  <hostid role="domainname">example.org</hostid>
           (<hostid role="ipaddr">192.168.1.1</hostid>) ��ͬ��
           CNAME ����ͬ��֮����ͬ���ֵ��κ�������¼���档</para>
 
 	<indexterm>
 	  <primary>MX ��¼</primary>
 	</indexterm>
 
         <programlisting>               IN MX   10      mail.example.org.</programlisting>
 
         <para>MX ��¼��ʾ�ĸ��ʼ�������������շ����������ʼ���
           <hostid role="fqdn">mail.example.org</hostid> ���ʼ�����������������
           �� 10 �����������ȼ���</para>
 
         <para>�����ж�̨�ʼ��������� �����ȼ��ֱ��� 10��
           20 �ȵȡ� ������ <hostid
 	    role="domainname">example.org</hostid> Ͷ���ʼ��ķ�������
           �����ȳ������ȼ���ߵ� MX (���ȼ���ֵ��С�ļ�¼)��
 	  ���ų��Դθߵģ� ���ظ���һ����ֱ���ʼ��ݴ�Ϊֹ��</para>
 
         <para>in-addr.arpa ������Ϣ�ļ� (���� DNS)�� ���õĸ�ʽ��ͬ���ģ�
           ֻ�� PTR ������� A �� CNAME ��λ�á�</para>
 
         <programlisting>$TTL 3600
 
 1.168.192.in-addr.arpa. IN SOA ns1.example.org. admin.example.org. (
                         2006051501      ; Serial
                         10800           ; Refresh
                         3600            ; Retry
                         604800          ; Expire
                         300 )           ; Negative Reponse TTL
 
         IN      NS      ns1.example.org.
         IN      NS      ns2.example.org.
 
 1       IN      PTR     example.org.
 2       IN      PTR     ns1.example.org.
 3       IN      PTR     ns2.example.org.
 4       IN      PTR     mx.example.org.
 5       IN      PTR     mail.example.org.</programlisting>
 
         <para>����ļ������������������� IP ��ַ��������ӳ���ϵ��</para>
 
 	<para>��Ҫ˵�����ǣ� �� PTR ��¼�Ҳ�����ֱ�����ȫ������
 	  (Ҳ���DZ����� <quote>.</quote> ����)��</para>
       </sect3>
     </sect2>
 
     <sect2>
       <title>��������������</title>
       <indexterm>
         <primary>BIND</primary>
         <secondary>��������������</secondary>
       </indexterm>
 
       <para>����������������һ����Ҫ�е������ݹ��ѯ��ɫ��������������
 	���򵥵����н��в�ѯ�� ������ѯ�����ס�Ա�����ʹ�á�</para>
     </sect2>
 
     <sect2>
       <title>��ȫ</title>
 
       <para>���� BIND ����Ϊ���õ� DNS ʵ�֣� ����������һЩ��ȫ���⡣
         ʱ�������˷���һЩ���ܵ������������õİ�ȫ©����
       </para>
 
       <para>���� &os; ���Զ���
 	<application>named</application> �ŵ� &man.chroot.8;
 	���������У� ������һЩ�������õİ�ȫ���������������DZ�ڵ����
 	<acronym>DNS</acronym> ���������</para>
 
       <para>�Ķ� <ulink
 	url="http://www.cert.org/">CERT</ulink> �İ�ȫ���棬
 	������ the &a.security-notifications; ��һ�������ڰ������˽�����
 	Internet �� &os; ��ȫ����ĺ�ϰ�ߡ�</para>
 
       <tip>
 	<para>������������⣬ ȷ��Դ���������µģ�
 	  ����������һ�� <application>named</application> �п��ܻ�����������</para>
       </tip>
     </sect2>
 
     <sect2>
       <title>��һ���Ķ�</title>
 
       <para>BIND/<application>named</application> �����ֲ᣺
       &man.rndc.8; &man.named.8; &man.named.conf.5;</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><ulink
 	      url="https://www.isc.org/software/bind">�ٷ��� ISC BIND
 	      ҳ��</ulink></para>
 	</listitem>
 
 	<listitem>
 	  <para><ulink
 	      url="https://www.isc.org/software/guild">Official ISC BIND
 	      Forum</ulink></para>
 	</listitem>
 
 	<listitem>
 	  <para><ulink url="http://www.oreilly.com/catalog/dns5/">O'Reilly
 	      DNS �� BIND �� 5 ��</ulink></para>
 	</listitem>
 
 	<listitem>
 	  <para><ulink
 	      url="http://www.rfc-editor.org/rfc/rfc1034.txt">RFC1034
 	      - ���� - ����͹���</ulink></para>
 	</listitem>
 
 	<listitem>
 	  <para><ulink
 	      url="http://www.rfc-editor.org/rfc/rfc1035.txt">RFC1035
 	      - ���� - ʵ�ּ����׼</ulink></para>
 	</listitem>
       </itemizedlist>
     </sect2>
   </sect1>
 
   <sect1 id="network-apache">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Murray</firstname>
 	  <surname>Stokely</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
     </sect1info>
     <title>Apache HTTP ������</title>
 
     <indexterm><primary>web ������</primary>
       <secondary>����</secondary></indexterm>
     <indexterm><primary>Apache</primary></indexterm>
 
     <sect2>
       <title>����</title>
 
       <para>&os; ��������������ȫ����Ϊ��æ�� web վ�㡣
         ����� Internet �ϵ� web ��������
         ��ʹ�� <application>Apache HTTP ������</application>��
         <application>Apache</application> ���������������� FreeBSD
         ��װ�����ҵ��� ���û�����״ΰ�װʱ������װ
         <application>Apache</application>�� �����ͨ�� <filename
         role="package">www/apache13</filename> �� <filename
         role="package">www/apache22</filename> port ����װ��</para>
 
       <para>һ���ɹ��ذ�װ�� <application>Apache</application>��
         �ͱ������������á�</para>
 
       <note><para>��һ�ڽ����� 1.3.X �汾��
         <application>Apache HTTP ������</application> �����ã�
         ��Ϊ������ &os; һͬʹ�õ����İ汾��
         <application>Apache</application>&nbsp;2.X �����˺ܶ��¼�����
         ���ڴ˲������ۡ� Ҫ�˽���� <application>Apache</application>&nbsp;2.X
         �ĸ������ϣ� ��μ� <ulink
         url="http://httpd.apache.org/"></ulink>��</para></note>
 
     </sect2>
 
     <sect2>
       <title>����</title>
 
       <indexterm><primary>Apache</primary>
 	<secondary>�����ļ�</secondary></indexterm>
 
       <para>��Ҫ�� <application>Apache HTTP Server</application> �����ļ���
 	�� &os; �ϻᰲװΪ
 	<filename>/usr/local/etc/apache/httpd.conf</filename>��
 	����һ�����͵� &unix; �ı������ļ��� ��ʹ�� <literal>#</literal>
 	��Ϊע�ͷ��� ����ȫ������ѡ����꾡���ܳ����˱���ķ�Χ��
 	���ｫֻ��������޸ĵ���Щ��</para>
 
       <variablelist>
 	<varlistentry>
 	  <term><literal>ServerRoot "/usr/local"</literal></term>
 
 	  <listitem>
 	    <para>��ָ���� <application>Apache</application>
 	    ��װ�Ķ���Ŀ¼�� ִ���ļ����ŵ���������Ŀ¼ (server root) ��
 	    <filename class="directory">bin</filename> ��
 	    <filename class="directory">sbin</filename> ��Ŀ¼�У�
 	    �������ļ���λ��
 	    <filename class="directory">etc/apache</filename>��</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><literal>ServerAdmin you@your.address</literal></term>
 
 	  <listitem>
 	    <para>�����ַ���ڷ�������������ʱӦ���͵����ʼ��ĵ�ַ��
 	      ��������ڷ��������ɵ�ҳ���ϣ� �������ҳ�档</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><literal>ServerName www.example.com</literal></term>
 
 	  <listitem>
 	    <para><literal>ServerName</literal> ���������÷��ͻؿͻ��˵���������
 	      ������ķ��������û��Ա�����ַ��� (���磬 ʹ�� <hostid>www</hostid>
 	      ������������������ʵ����)��</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><literal>DocumentRoot "/usr/local/www/data"</literal></term>
 
 	  <listitem>
 	    <para><literal>DocumentRoot</literal>�� ���Ŀ¼�������ĵ����ڵ�Ŀ¼��
 	      Ĭ������£� ���е����󶼻�����λ��ȥ��ȡ��
 	      ��Ҳ����ͨ���������Ӻͱ���ָ��������λ�á�</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
 
       <para>���޸�����֮ǰ����
 	<application>Apache</application> �������ļ���Զ��һ����ϰ�ߡ�
 	һ���Գ�ʼ���������ˣ� �Ϳ��Կ�ʼ���� <application>Apache</application> �ˡ�</para>
 
 <!-- sect3 for performance tuning directives?  maxservers minservers -->
 <!-- etc..?? -->
 
 <!-- Advanced configuration section.
 
 Performance tuning directives.
 
 Log file format -->
 
     </sect2>
 
     <sect2>
       <title>���� <application>Apache</application></title>
 
       <indexterm><primary>Apache</primary>
 	<secondary>������ֹͣ</secondary></indexterm>
 
       <para>�����������������ͬ�� <application>Apache</application> ��������
         <application>inetd</application> ����������������
         һ������»��������Ϊһ�������ķ������� �����ڿͻ��� web
         ��������� HTTP ����ʱ�� �ܹ���ø��õ����ܡ� ���ṩ��һ�� shell
         �ű���ʹ������ ֹͣ������������������þ����ܵؼ򵥡�
         �״����� <application>Apache</application>��
         ֻ��ִ�У�</para>
 
       <screen>&prompt.root; <userinput>/usr/local/sbin/apachectl start</userinput></screen>
 
       <para>�������κ�ʱ��ʹ�������������ֹͣ����</para>
 
       <screen>&prompt.root; <userinput>/usr/local/sbin/apachectl stop</userinput></screen>
 
       <para>������ij��ԭ���޸��������ļ�֮�� ��Ҫ������������</para>
 
       <screen>&prompt.root; <userinput>/usr/local/sbin/apachectl restart</userinput></screen>
 
       <para>Ҫ������ <application>Apache</application> ������ʱ���жϵ�ǰ�����ӣ�
 	��Ӧ���У�</para>
 
       <screen>&prompt.root; <userinput>/usr/local/sbin/apachectl graceful</userinput></screen>
 
       <para>�������Ϣ�� ������
 	&man.apachectl.8; �����ֲ����ҵ���</para>
 
       <para>Ҫ��ϵͳ����ʱ���� <application>Apache</application>�� ��Ӧ��
         <filename>/etc/rc.conf</filename> �м��룺</para>
 
       <programlisting>apache_enable="YES"</programlisting>
 
       <para>���߶���<application>Apache</application> 2.2��</para>
 
       <programlisting>apache22_enable="YES"</programlisting>
 
       <para>�����ϣ����ϵͳ����ʱ���� <application>Apache</application>
 	<command>httpd</command> ����ָ������һЩѡ�
 	����԰�������мӵ�
 	<filename>rc.conf</filename>��</para>
 
       <programlisting>apache_flags=""</programlisting>
 
       <para>���� web �������Ϳ�ʼ�����ˣ� ������ʹ�� web �������
         <literal>http://localhost/</literal>�� Ĭ����ʾ�� web ҳ����
         <filename>/usr/local/www/data/index.html</filename>��</para>
 
     </sect2>
 
     <sect2>
       <title>��������</title>
 
       <para><application>Apache</application> ֧�����ֲ�ͬ���͵�����������
 	��һ�ַ����ǻ������ֵ����������� �������ֵ���������ʹ�ÿͻ���������
 	HTTP/1.1 ͷ������������� ��ʹ�ò�ͬ������Թ���ͬһ�� IP ��ַ��</para>
 
       <para>Ҫ���� <application>Apache</application> ��ʹ�û������ֵ�����������
         ��Ҫ�������������ӵ����� <filename>httpd.conf</filename> �У�</para>
 
       <programlisting>NameVirtualHost *</programlisting>
 
       <para>������� web �������������� <hostid role="fqdn">www.domain.tld</hostid>��
         ����ϣ������һ��
         <hostid role="fqdn">www.someotherdomain.tld</hostid> ��������
         ��Ӧ��
         <filename>httpd.conf</filename> �м��룺</para>
 
       <screen>&lt;VirtualHost *&gt;
 ServerName www.domain.tld
 DocumentRoot /www/domain.tld
 &lt;/VirtualHost&gt;
 
 &lt;VirtualHost *&gt;
 ServerName www.someotherdomain.tld
 DocumentRoot /www/someotherdomain.tld
 &lt;/VirtualHost&gt;</screen>
 
       <para>����Ҫ������ĵ�ַ���ĵ�·����Ϊ��ʹ�õ���Щ��</para>
 
       <para>Ҫ�˽�������������ĸ�����Ϣ��
         ��ο��ٷ��� <application>Apache</application> �ĵ��� ��Щ�ĵ������� <ulink
         url="http://httpd.apache.org/docs/vhosts/"></ulink> �ҵ���</para>
 
     </sect2>
 
     <sect2>
       <title>Apache ģ��</title>
 
       <indexterm><primary>Apache</primary>
 	<secondary>ģ��</secondary></indexterm>
 
       <para>�����಻ͬ�� <application>Apache</application> ģ�飬
         ���ǿ����ڻ����ķ������������ṩ���฽�ӵĹ��ܡ� FreeBSD ��
         Ports Collection Ϊ��װ
         <application>Apache</application>
         �ͳ��õĸ���ģ���ṩ�˷dz�����ķ�����</para>
 
       <sect3>
         <title>mod_ssl</title>
 
 	<indexterm><primary>web ������</primary>
           <secondary>��ȫ</secondary></indexterm>
 	<indexterm><primary>SSL</primary></indexterm>
 	<indexterm><primary>����ѧ</primary></indexterm>
 
         <para><application>mod_ssl</application> ���ģ��ʹ�� OpenSSL �⣬
           ���ṩͨ�� ��ȫ�׽��ֲ� (SSL v2/v3) �� ����㰲ȫ (TLS v1)
           Э���ǿ����������
           ���ģ���ṩ�˴�ijһ���ŵ�֤��ǩ���������ǩ��֤����������й��ߣ�
           �����Խ���� &os; �����а�ȫ�� web ��������</para>
 
 	<para>�����δ����װ
 	  <application>Apache</application>�� Ҳ����ֱ�Ӱ�װһ�ݰ�����
 	  <application>mod_ssl</application> �İ汾��
 	  <application>Apache</application>
 	  1.3.X�� �䷽����ͨ�� <filename
 	  role="package">www/apache13-modssl</filename> port ������ SSL
 	  ֧���Ѿ���Ϊ <application>Apache</application>&nbsp;2.X ��һ�����ṩ��
 	  ������ͨ��
 	  <filename role="package">www/apache22</filename> port ����װ���ߡ�</para>
 
 <!-- XXX add more information about configuring mod_ssl here. -->
 <!-- Generating keys, getting the key signed, setting up your secure -->
 <!-- web server! -->
       </sect3>
 
       <sect3>
 	<title>���԰�</title>
 
 	<para>Apache����һЩ��Ҫ�Ľű����Զ�����Ӧ��ģ�顣
 	  ��Щģ��ʹ����ȫʹ��ij�ֽű�������д
 	  <application>Apache</application> ģ���Ϊ���ܡ�
 	  ����ͨ��Ҳ��Ƕ�뵽��������Ϊһ����פ�ڴ�Ľ�������
 	  �Ա�������һ���ⲿ������������һ�ڽ������Ķ�̬��վ����ʱ�����Դ�ϵĿ�����
 	</para>
       </sect3>
     </sect2>
 
     <sect2>
       <title>��̬��վ</title>
 
       <indexterm><primary>web servers</primary>
         <secondary>dynamic</secondary></indexterm>
 
       <para>�ڹ�ȥ��ʮ���Խ��Խ�����ҵΪ����������ͱ����ʶ�ת���˻�������
 	��Ҳͬʱ�����˶��ڻ�����ҳ���ݵ�������Щ��˾������ &microsoft;
 	�Ƴ��˻�������ר�в�Ʒ�Ľ����������Դ����Ҳ�����˻����Ļ�Ӧ��
 	�Ƚ�ʱ�е�ѡ����� Django��Ruby on Rails��
         <application>mod_perl</application>, and
         <application>mod_php</application>.</para>
 
       <sect3>
         <title>Django</title>
 
 	<indexterm><primary>Python</primary></indexterm>
 	<indexterm><primary>Django</primary></indexterm>
 
 	<para>Django ��һ���� BSD ����֤������ framework��
 	  ���ÿ����߿���д�������ܸ�Ʒ�ʵ� web Ӧ�ó���
 	  ���ṩ��һ�������ϵӳ��������������Ϳ��Ա��� Python
 	  �еĶ��󣬺�һ��ḻ�Ķ�̬���ݿ���� API��
 	  ʹ�����߱�����д SQL ��䡣��ͬʱ���ṩ�˿���չ��ģ��ϵͳ��
 	  ��Ӧ�ó�����߼������� HTML �ı��ֲ���롣</para>
 
 	<para>Django ������ <application>mod_python</application>��
 	  <application>Apache</application>, ��һ����ѡ�� SQL
 	  ���ݿ����档 ��������һЩǡ���ı�־��FreeBSD �� Port
 	  ϵͳ��������㰲װ��Щ����������⡣</para>
 
 	<example id="network-www-django-install">
 	  <title>��װ Django��Apache2�� mod_python3���� PostgreSQL</title>
 
 	  <screen>&prompt.root; <userinput>cd /usr/ports/www/py-django; make all install clean -DWITH_MOD_PYTHON3 -DWITH_POSTGRESQL</userinput></screen>
         </example>
 
 	<para>�ڰ�װ�� Django ����Щ����������֮��
 	  ����Ҫ����һ�� Django ��Ŀ��Ŀ¼��Ȼ������
 	  Apache�����ж�������վ��Ӧ�ó����ijЩָ���� URL
 	  ʱ������Ƕ�� Python ��������</para>
 
 	<example id="network-www-django-apache-config">
 	  <title>Django/mod_python �й� Apache ���ֵ�����</title>
 
 	  <para>����Ҫ�� Apache �������ļ�
 	    <filename>httpd.conf</filename> ���������⼸�У�
 	    �Ѷ�ijЩ URL �����󴫸���� web Ӧ�ó���</para>
 
       <screen>&lt;Location "/"&gt;
     SetHandler python-program
     PythonPath "['/dir/to/your/django/packages/'] + sys.path"
     PythonHandler django.core.handlers.modpython
     SetEnv DJANGO_SETTINGS_MODULE mysite.settings
     PythonAutoReload On
     PythonDebug On
 &lt;/Location&gt;</screen>
 	</example>
       </sect3>
 
       <sect3>
         <title>Ruby on Rails</title>
 
 	<indexterm><primary>Ruby on Rails</primary></indexterm>
 
 	<para>Ruby on Rails ������һ����Դ�� web framework��
 	  �ṩ��һ��ȫ��Ŀ�����ܣ��ܰ��� web
 	  �����߹������г�Ч�Ϳ���д��ǿ���Ӧ�á�
 	  ���ܷdz����׵Ĵ� posts ϵͳ��װ��</para>
 
 	  <screen>&prompt.root; <userinput>cd /usr/ports/www/rubygem-rails; make all install clean</userinput></screen>
       </sect3>
 
       <sect3>
         <title>mod_perl</title>
 
 	<indexterm>
           <primary>mod_perl</primary>
           <secondary>Perl</secondary>
         </indexterm>
 
         <para><application>Apache</application>/Perl ���ɼƻ��� �� Perl
 	  ����������Ե�ǿ���ܣ� �� <application>Apache
 	  HTTP ������</application> ���ܵؽ�ϵ���һ��
 	  ͨ�� <application>mod_perl</application> ģ�飬
 	  ������ȫʹ�� Perl ��׫д <application>Apache</application> ģ�顣
 	  ���⣬ ��������Ƕ��ij־��Խ������� ���������������ⲿ�Ľ�����Ϊ Perl
 	  �ű�����������ɵ�������ʧ��</para>
 
           <para><application>mod_perl</application> ͨ�����ַ�ʽ�ṩ��
             Ҫʹ�� <application>mod_perl</application>��
             Ӧ��ע�� <application>mod_perl</application> 1.0
             ֻ����� <application>Apache</application> 1.3 ��
             <application>mod_perl</application> 2.0 ֻ�����
             <application>Apache</application> 2.X ʹ�á�
             <application>mod_perl</application> 1.0 ����ͨ��
             <filename role="package">www/mod_perl</filename> ��װ��
             ���Ծ�̬��ʽ����İ汾�� �����ͨ��
             <filename role="package">www/apache13-modperl</filename>
             ����װ��
             <application>mod_perl</application> 2.0 �����ͨ��
             <filename role="package">www/mod_perl2</filename> ��װ��</para>
         </sect3>
 
         <sect3>
           <sect3info>
 	  <authorgroup>
 	    <author>
 	      <firstname>Tom</firstname>
 	      <surname>Rhodes</surname>
 	      <contrib>Written by </contrib>
 	    </author>
 	  </authorgroup>
         </sect3info>
         <title>mod_php</title>
 
 	<indexterm>
           <primary>mod_php</primary>
           <secondary>PHP</secondary>
         </indexterm>
 
 	<para><acronym>PHP</acronym>�� Ҳ��Ϊ <quote>PHP:
           Hypertext Preprocessor</quote>��
           ��һ���ر��ʺ��� Web ������ͨ�ýű����ԡ�
 	  ���ܹ������׵�Ƕ�뵽 <acronym>HTML</acronym> ֮�У�
 	  ���﷨�ӽ���  C�� &java;�� �Լ� Perl�� ������ web
 	  ������Ա��һѸ��׫д��̬���ɵ�ҳ�档</para>
 
 	<para>Ҫ�������
 	  <application>Apache</application> web ��������
 	  <acronym>PHP</acronym>5 ֧�֣� ���ԴӰ�װ
 	  <filename role="package">lang/php5</filename>
 	  port ��ʼ��</para>
 
 	<para>���״ΰ�װ <filename role="package">lang/php5</filename> port
 	  ��ʱ�� ϵͳ���Զ���ʾ���õ�һϵ��
 	  <literal>OPTIONS</literal> (����ѡ��)�� �����û�п����˵���
 	  �������ڹ�ȥ������װ�� <filename
 	  role="package">lang/php5</filename> port �ȵȣ�
 	  ����������������ٴ���ʾ���ò˵��� �� port ��Ŀ¼��ִ�У�</para>
 
 	<screen>&prompt.root; <userinput>make config</userinput></screen>
 
 	<para>������ѡ��Ի����У� ѡ��
 	  <literal>APACHE</literal> ��һ� �Ϳ��������������
 	  <application>Apache</application> web ���������ʹ�õĿɶ�̬���ص�
 	  <application>mod_php5</application> ģ���ˡ�</para>
 
 	<note>
 	  <para>���ڸ�ʽ������ԭ�� (���磬 �����Ѿ������ web Ӧ�õļ����Կ���)��
 	    ������վ����ʹ�� <acronym>PHP</acronym>4�� �������Ҫ
 	    <application>mod_php4</application> ������
 	    <application>mod_php5</application>�� ��ʹ��
 	    <filename role="package">lang/php4</filename> port��
 	    <filename role="package">lang/php4</filename> port Ҳ֧������
 	    <filename role="package">lang/php5</filename> port �ṩ�����úͱ���ʱѡ�</para>
 	</note>
 
 	<para>ǰ�������Ѿ��ɹ��ذ�װ������������֧�ֶ�̬ <acronym>PHP</acronym> Ӧ�������ģ�顣
           ���鲢ȷ�����ѽ��������ü��뵽��
 	  <filename>/usr/local/etc/apache/httpd.conf</filename> �У�</para>
 
 	<programlisting>LoadModule php5_module        libexec/apache/libphp5.so</programlisting>
 
         <programlisting>AddModule mod_php5.c
     &lt;IfModule mod_php5.c&gt;
         DirectoryIndex index.php index.html
     &lt;/IfModule&gt;
     &lt;IfModule mod_php5.c&gt;
         AddType application/x-httpd-php .php
         AddType application/x-httpd-php-source .phps
     &lt;/IfModule&gt;</programlisting>
 
           <para>��Щ�������֮�� ����Ҫʹ��
             <command>apachectl</command> ���������һ�� graceful
             restart �Ա���� <acronym>PHP</acronym> ģ�飺</para>
 
 	<screen>&prompt.root; <userinput>apachectl graceful</userinput></screen>
 
 	<para>��δ�������� <acronym>PHP</acronym> ʱ��
 	  <command>make config</command> �ⲽ�����Ͳ����DZ�����ˣ�
 	  ����ѡ��� <literal>OPTIONS</literal> ���� &os;
 	  �� Ports ����Զ����档</para>
 
           <para>�� &os; �е� <acronym>PHP</acronym> ֧���Ǹ߶�ģ�黯�ģ�
             ��˻�����װ�Ĺ���ʮ�����ޡ� �����������ܵ�֧�ַdz��򵥣� ֻ��ͨ��
             <filename role="package">lang/php5-extensions</filename> port
             ������ɡ� ��� port �ṩ��һ���˵������Ľ������������
             <acronym>PHP</acronym> ��չ�İ�װ�� ���⣬ Ҳ����ͨ����Ӧ�� port
             ��������װ��չ��</para>
 
 	<para>���磬 Ҫ������
 	  <application>MySQL</application> ���ݿ��������֧�ּ���
 	  <acronym>PHP</acronym>5�� ֻ��򵥵ذ�װ
           <filename>databases/php5-mysql</filename>��</para>
 <!-- deactivate the filename link as there is no pkg-descr file for this port -->
 <!--
           <filename role="package">databases/php5-mysql</filename>
 	  port��</para>
 -->
           <para>��װ����չ֮�� ������������
             <application>Apache</application> ��������
               ��������Ӧ�µ����ñ����</para>
 
 	<screen>&prompt.root; <userinput>apachectl graceful</userinput></screen>
       </sect3>
     </sect2>
   </sect1>
 
   <sect1 id="network-ftp">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Murray</firstname>
 	  <surname>Stokely</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
     </sect1info>
     <title>�ļ�����Э�� (FTP)</title>
 
     <indexterm><primary>FTP ������</primary></indexterm>
 
     <sect2>
       <title>����</title>
 
       <para>�ļ�����Э�� (FTP) Ϊ�û��ṩ��һ���򵥵ģ� �� <acronym
 	role="File Transfer Protocol">FTP</acronym> �����������ļ��ķ����� &os;
 	ϵͳ�а����� <acronym role="File Transfer Protocol">FTP</acronym>
 	���������� <application>ftpd</application>�� ��ʹ���� &os;
 	�Ͻ����͹��� <acronym
 	role="File Transfer Protocol">FTP</acronym> ��������÷dz��򵥡�</para>
     </sect2>
 
     <sect2>
       <title>����</title>
 
       <para>����Ҫ�����ò����Ǿ���������Щ�ʺŷ��� FTP ��������
 	һ��� &os; ϵͳ������һϵ��ϵͳ�ʺŷֱ�����ִ�в�ͬ�ķ������
 	��δ֪���û���Ӧ��������¼��ʹ����Щ�ʺš�
 	<filename>/etc/ftpusers</filename> �ļ��У� �г��˲�����ͨ��
 	FTP ���ʵ��û��� Ĭ������£� �������ǰ����ϵͳ�ʺţ�
 	��Ҳ�������������������Ӧͨ�� FTP ���ʵ��û���</para>
 
       <para>�����ܻ�ϣ������ͨ�� FTP ��¼��ijЩ�û���
 	��������ȫ��ֹ����ʹ�� FTP�� �����ͨ�� <filename>/etc/ftpchroot</filename>
 	�ļ�����ɡ� ��һ�ļ��г���ϣ���� FTP ���ʽ������Ƶ��û�����ı���
 	���� &man.ftpchroot.5; �����ֲ��У� �Ѿ��Դ˽������꾡�Ľ��ܣ�
 	�ʶ�����׸����</para>
 
       <indexterm>
 	<primary>FTP</primary>
 	<secondary>����</secondary>
       </indexterm>
 
       <para>�������Ҫ�ڷ����������������� FTP ���ʣ� ����뽨��һ����Ϊ
 	<username>ftp</username> �� &os; �û��� ������ �û��Ϳ���ʹ��
 	<username>ftp</username> �� <username>anonymous</username>
 	������Ŀ��� (ϰ���ϣ� Ӧ�������Ǹ��û����ʼ���ַ��Ϊ����)
 	����¼�ͷ������� FTP �������� FTP ���������������û���¼ʱ����
 	&man.chroot.2;�� �Ա㽫�����������
 	<username>ftp</username> �û�����Ŀ¼�С�</para>
 
       <para>�������ı��ļ���������ָ����ʾ�� FTP �ͻ������еĻ�ӭ���֡�
 	<filename>/etc/ftpwelcome</filename> �ļ��е����ݽ����û�������֮��
 	�ڵ�¼��ʾ֮ǰ��ʾ�� �ڳɹ��ĵ�¼֮�� ����ʾ
 	<filename>/etc/ftpmotd</filename> �ļ��е����ݡ�
 	��ע�����������ڵ�¼�����ģ� ��˶��������û����ԣ�
 	����ʾ <filename>~ftp/etc/ftpmotd</filename>��</para>
 
       <para>һ����ȷ�������� FTP ��������
         �ͱ����� <filename>/etc/inetd.conf</filename> ����������
         ������Ҫ����ȫ���������ǽ�ע�ͷ�
         <quote>#</quote> �����е�
         <application>ftpd</application> ��֮ǰȥ����</para>
 
       <programlisting>ftp	stream	tcp	nowait	root	/usr/libexec/ftpd	ftpd -l</programlisting>
 
       <para>�� <xref linkend="network-inetd-reread"/> �����ܵ�������
         �޸�����ļ�֮�� ������ <application>inetd</application> ���¼�������
         ����ʹ�µ�������Ч������� <xref linkend="network-inetd-settings"/>
         �Ի�ȡ�����й��������ϵͳ������ <application>inetd</application>
         ����ϸ��Ϣ��</para>
 
       <para><application>ftpd</application> Ҳ������Ϊһ�������ķ���������
         �����Ļ�����Ҫ�� <filename>/etc/rc.conf</filename>
         ���������µı�����</para>
 
       <programlisting>ftpd_enable="YES"</programlisting>
 
       <para>����������������֮�󣬶����ķ������´�ϵͳ������ʱ��������
         ����ͨ���� <username>root</username> �����ֶ�ִ�����µ�����������</para>
 
       <screen>&prompt.root; <userinput>/etc/rc.d/ftpd start</userinput></screen>
 
       <para>���ڿ���ͨ�������������������¼���� FTP �������ˣ�</para>
 
       <screen>&prompt.user; <userinput>ftp localhost</userinput></screen>
 
     </sect2>
 
     <sect2>
       <title>��</title>
 
       <indexterm><primary>syslog</primary></indexterm>
       <indexterm><primary>��־�ļ�</primary>
 	<secondary>FTP</secondary></indexterm>
 
       <para><application>ftpd</application> �������ʹ��
         &man.syslog.3; ����¼��Ϣ�� Ĭ������£�
         ϵͳ��־���Ѻ� FTP ��ص���Ϣ��¼��
         <filename>/var/log/xferlog</filename> �ļ��С� FTP ��־��λ�ã�
         ����ͨ���޸�
         <filename>/etc/syslog.conf</filename> ��������ʾ�������޸ģ�</para>
 
       <programlisting>ftp.info      /var/log/xferlog</programlisting>
 
       <indexterm>
 	<primary>FTP</primary>
 	<secondary>����</secondary>
       </indexterm>
 
       <para>һ��ҪС�ĶԴ������� FTP �������п���������DZ�����⡣
         һ����ԣ� ���������û��ϴ��ļ�Ӧ��˼�� �����ܷ����Լ��� FTP
         վ���Ϊ�˽���δ����Ȩ����ҵ��������̳�� ���������������
         �������Ҫ������ FTP �ϴ��� �������ļ�������Ȩ�ޣ�
         ʹ�����ܹ������������û��ܹ�������Щ�ļ�֮ǰ�������ǡ�</para>
 
     </sect2>
   </sect1>
 
   <sect1 id="network-samba">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Murray</firstname>
 	  <surname>Stokely</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
     </sect1info>
     <title>Ϊ &microsoft.windows; �ͻ����ṩ�ļ��ʹ�ӡ���� (Samba)</title>
 
     <indexterm><primary>Samba ������</primary></indexterm>
     <indexterm><primary>Microsoft Windows</primary></indexterm>
     <indexterm>
       <primary>�ļ�������</primary>
       <secondary>Windows �ͻ���</secondary>
     </indexterm>
     <indexterm>
       <primary>��ӡ������</primary>
       <secondary>Windows �ͻ���</secondary>
     </indexterm>
 
     <sect2>
       <title>����</title>
 
       <para><application>Samba</application> ��һ�����еĿ�Դ��������
         ���ṩ����� &microsoft.windows; �ͻ������ļ��ʹ�ӡ����
         ����ͻ����������Ӳ�ʹ�� FreeBSD ϵͳ�ϵ��ļ��ռ䣬
         ����ͬʹ�ñ��صĴ���һ���� ������ʹ�ñ��ش�ӡ��һ��ʹ��
         FreeBSD �ϵĴ�ӡ����</para>
 
       <para><application>Samba</application> ���������������� FreeBSD
         ��װ�����ҵ��� �����û���ڳ��ΰ�װ FreeBSD
         ʱ��װ <application>Samba</application>�� �����ͨ�� <filename
         role="package">net/samba34</filename> port �� package ����װ��</para>
 
 <!-- mention LDAP, Active Directory, WinBIND, ACL, Quotas, PAM, .. -->
 
     </sect2>
 
     <sect2>
       <title>����</title>
 
       <para>Ĭ�ϵ� <application>Samba</application> �����ļ�����
         <filename>/usr/local/share/examples/samba34/smb.conf.default</filename>
 	�����ְ�װ������ļ����븴��Ϊ
         <filename>/usr/local/etc/smb.conf</filename> �����ж��ƣ�
         ���ܿ�ʼʹ�� <application>Samba</application>��</para>
 
       <para><filename>smb.conf</filename> �ļ��а�����
         <application>Samba</application> ������ʱ������Ϣ��
         ������ڴ�ӡ���Ķ��壬 �Լ�ϣ�������� &windows;
         �ͻ����� <quote>�����ļ�ϵͳ</quote>��
         <application>Samba</application> ������������һ����Ϊ
         <application>swat</application> �� web �������ߣ�
         �����ṩ������ <filename>smb.conf</filename> �ļ��ļ򵥷�����</para>
 
       <sect3>
 	<title>ʹ�� Samba Web �������� (SWAT)</title>
 
 	<para>Samba Web �������� (SWAT) ��һ��ͨ��
 	  <application>inetd</application> ���еķ������ ��ˣ�
 	  ��Ҫ�� <filename>/etc/inetd.conf</filename> �����漸�е�ע��ȥ����
 	  ���ܹ�ʹ�� <application>swat</application>
 	  ������ <application>Samba</application>��</para>
 
 	<programlisting>swat   stream  tcp     nowait/400      root    /usr/local/sbin/swat    swat</programlisting>
         <para>�� <xref linkend="network-inetd-reread"/> �������ܵ�������
           ���޸�����������ļ�֮�� ������ <application>inetd</application>
           ���¼������ã� ����ʹ����Ч��</para>
 
 	<para>һ���� <filename>inetd.conf</filename> ��������
 	  <application>swat</application>�� �Ϳ��������������
 	  connect to <ulink url="http://localhost:901"></ulink> �ˡ�
 	  ��������ʹ��ϵͳ�� <username>root</username>
 	  �ʺŵ�¼��</para>
 
 <!-- XXX screenshots go here, loader is creating them -->
 
 	<para>ֻҪ�ɹ��ص�¼����
 	  <application>Samba</application> ����ҳ�棬
 	  �Ϳ������ϵͳ���ĵ��� ���
 	  <guimenu>Globals</guimenu>(ȫ��) ѡ���ʼ�����ˡ�
 	  <guimenu>Globals</guimenu> С�ڶ�Ӧ�� <literal>[global]</literal>
 	  С���еı����� ǰ��λ��
 	  <filename>/usr/local/etc/smb.conf</filename> �С�</para>
       </sect3>
 
       <sect3>
 	<title>ȫ������</title>
 
 	<para>������ʹ�� <application>swat</application>��
 	  ����ֱ�ӱ༭ <filename>/usr/local/etc/smb.conf</filename>��
 	  ͨ������Ҫ���õ� <application>Samba</application>
 	  ѡ��ǣ�</para>
 
         <variablelist>
 	  <varlistentry>
 	    <term><literal>workgroup</literal></term>
 
 	    <listitem>
 	      <para>NT ��������������
 	        �����������ͨ����Щ�������ҵ���������</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term><literal>netbios name</literal></term>
 
 	    <listitem>
 	      <indexterm><primary>NetBIOS</primary></indexterm>
 
 	      <para>���ѡ���������� <application>Samba</application> ��������
 		NetBIOS ���֡� Ĭ������£� �������������� DNS ���ֵĵ�һ���֡�</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term><literal>server string</literal></term>
 
 	    <listitem>
 	      <para>���ѡ����������ͨ�� <command>net view</command>
 		��� �Լ�ijЩ�������繤�߿��Բ鿴���Ĺ��ڷ�������˵�������֡�</para>
 	    </listitem>
 	  </varlistentry>
         </variablelist>
       </sect3>
 
       <sect3>
 	<title>��ȫ����</title>
 
 	<para>��
 	  <filename>/usr/local/etc/smb.conf</filename> �е���������Ҫ�����ã�
 	  ��ѡ���İ�ȫģ�ͣ� �Լ��ͻ������û��Ŀ����ź�ˡ�
 	  �������������Щѡ�</para>
 
         <variablelist>
 	  <varlistentry>
 	    <term><literal>security</literal></term>
 
 	    <listitem>
 	      <para>�����ѡ����ʽ��
 	        <literal>security = share</literal> �� <literal>security
 	        = user</literal>�� ������Ŀͻ���ʹ���û�����
 	        ������Щ�û��������� &os; ����һ�£�
 	        һ��Ӧѡ���û��� (user) ��ȫ�� ����Ĭ�ϵİ�ȫ���ԣ�
 	        ��Ҫ��ͻ������ȵ�¼�� Ȼ����ܷ��ʹ�������Դ��</para>
 
 	      <para>������ù����� (share) ��ȫ��
 	        ��ͻ�������Ҫ����Ч���û����Ϳ����¼��������
 	        ���ܹ����ӹ�������Դ�� ���ǽ���汾��
 	        <application>Samba</application> �е�Ĭ��ֵ��</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term><literal>passdb backend</literal></term>
 
 	    <listitem>
 	      <indexterm><primary>NIS+</primary></indexterm>
 	      <indexterm><primary>LDAP</primary></indexterm>
 	      <indexterm><primary>SQL ���ݿ�</primary></indexterm>
 
 	      <para><application>Samba</application> �ṩ�������ֲ�ͬ����֤���ģ�͡�
 	        ������ͨ�� LDAP�� NIS+�� SQL ���ݿ⣬ �򾭹��޸ĵĿ����ļ���
 	        ����ɿͻ��˵�������֤�� Ĭ�ϵ���֤ģʽ��
 	        <literal>smbpasswd</literal>�� ��Ҳ�DZ��½����ܵ�ȫ�����ݡ�</para>
 	    </listitem>
 	  </varlistentry>
 	</variablelist>
 
 	<para>������ʹ�õ���Ĭ�ϵ� <literal>smbpasswd</literal>
 	  ��ˣ� ��������ȴ���һ��
 	  <filename>/usr/local/etc/samba/smbpasswd</filename> �ļ���
 	  ������ <application>Samba</application> �Կͻ�����������֤��
 	  ����������� &unix; �û��ʺ��ܹ��� &windows;
 	  �ͻ����ϵ�¼�� ����ʹ����������</para>
 
 	<screen>&prompt.root; <userinput>smbpasswd -a username</userinput></screen>
 	<note>
 	  <para>Ŀǰ�Ƽ�ʹ�õĺ���� <literal>tdbsam</literal>��
 	    ��Ӧʹ������������������û��ʺţ�</para>
 
 	  <screen>&prompt.root; <userinput><command>pdbedit <option>-a</option> <option>-u</option> <replaceable>username</replaceable></command></userinput></screen>
 	</note>
 
 	<para>��ο�
 	  <ulink
 	  url="http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/">�ٷ��� Samba HOWTO</ulink>
 	  ���˽��������ѡ��Ľ�һ����Ϣ�� ����ǰ������Ļ���������
 	  ��Ӧ���Ѿ���������
 	  <application>Samba</application> �ˡ�</para>
       </sect3>
 
     </sect2>
     <sect2>
       <title>���� <application>Samba</application></title>
 
       <para><filename role="package">net/samba34</filename> port
 	������һ���µ����ڿ���
 	<application>Samba</application> �������ű��� Ҫ��������ű���
 	�Ա���������������� ֹͣ������
 	<application>Samba</application> ������ ��Ҫ��
 	<filename>/etc/rc.conf</filename> �ļ��м��룺</para>
 
       <programlisting>samba_enable="YES"</programlisting>
 
       <para>���⣬ Ҳ���Խ��и�ϸ���ȵĿ��ƣ�</para>
 
       <programlisting>nmbd_enable="YES"</programlisting>
       <programlisting>smbd_enable="YES"</programlisting>
 
       <note>
 	<para>��Ҳͬʱ��������ϵͳ����ʱ���� <application>Samba</application>��</para>
       </note>
 
       <para>���ú�֮�� �Ϳ������κ�ʱ��ͨ�����������������
 	<application>Samba</application> �ˣ�</para>
 
       <screen>&prompt.root; <userinput>/usr/local/etc/rc.d/samba start</userinput>
 Starting SAMBA: removing stale tdbs :
 Starting nmbd.
 Starting smbd.</screen>
 
       <para>��μ� <xref linkend="configtuning-rcd"/> ���˽����ʹ�� rc �ű��Ľ�һ����Ϣ��</para>
 
       <para><application>Samba</application> ��ʵ�ϰ����������໥�����ķ������
         ��Ӧ���ܹ�����
         <application>nmbd</application> �� <application>smbd</application>
         �������������ͨ�� <filename>samba</filename> �ű������ġ� �����
         <filename>smb.conf</filename> �������� winbind ���ֽ�������
         ��Ӧ�ÿ��Կ��� <application>winbindd</application>
         ��������������</para>
 
       <para>�������κ�ʱ��ͨ�������������ֹͣ����
         <application>Samba</application>��</para>
 
       <screen>&prompt.root; <userinput>/usr/local/etc/rc.d/samba stop</userinput></screen>
 
       <para><application>Samba</application> ��һ�����ӵ���������
         ���ṩ�������� &microsoft.windows; ������м��ɵĸ�ʽ�����Ĺ��ܡ�
         Ҫ�˽�������������ܵĻ�����װ������������ܣ�
         ����� <ulink url="http://www.samba.org"></ulink>��</para>
     </sect2>
 
   </sect1>
 
   <sect1 id="network-ntp">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Tom</firstname>
 	  <surname>Hukins</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
     </sect1info>
     <title>ͨ�� NTP ����ʱ��ͬ��</title>
 
     <indexterm><primary>NTP</primary></indexterm>
 
     <sect2>
       <title>����</title>
 
       <para>����ʱ������ƣ� �������ʱ�ӻ�������Ư�ơ�
 	����ʱ��Э�� (NTP) ��һ��ȷ������ʱ�ӱ���׼ȷ�ķ�����</para>
 
       <para>���� Internet ���������� �򼫴�������ڱ��ؼ����ʱ�ӵ�׼ȷ�ԡ�
 	���磬 web ���������ܻ���յ�һ������
 	Ҫ������ļ���ijһʱ��֮���޸Ĺ��ŷ�������
 	�ھ����������У� �����ļ��ļ����֮���ʱ���Ƿ�ͬ��������Ҫ��
 	��Ϊ��������ʹʱ�������һ�¡� ���� &man.cron.8;
 	�����ij��� Ҳ��������ȷ��ϵͳʱ�ӣ� ���ܹ�׼ȷ��ִ�в�����</para>
 
       <indexterm>
 	<primary>NTP</primary>
 	<secondary>ntpd</secondary>
       </indexterm>
       <para>FreeBSD ������ &man.ntpd.8; <acronym role="Network
 	Time Protocol">NTP</acronym> ��������
 	���������ڲ�ѯ������ <acronym role="Network Time Protocol">NTP</acronym>
 	�������� �����ñ��ؼ������ʱ�ӣ� ����Ϊ���������ṩ����</para>
     </sect2>
 
     <sect2>
       <title>ѡ����ʵ� NTP ������</title>
 
       <indexterm>
 	<primary>NTP</primary>
 	<secondary>ѡ�������</secondary>
       </indexterm>
 
       <para>Ϊ��ͬ������ϵͳʱ�ӣ�
 	��Ҫ�����ҵ�����һ�� <acronym role="Network Time
 	Protocol">NTP</acronym> �������Թ�ʹ�á� �������Ա��
 	�� ISP �����ܻ��ṩ��������Ŀ�ĵ� NTP
 	������&mdash;��鿴���ǵ��ĵ����˽��Ƿ���������
 	���⣬ Ҳ��һ�����ߵ� <ulink
 	url="http://ntp.isc.org/bin/view/Servers/WebHome">������
 	NTP �������б�</ulink>�� �����Դ���ѡһ���Ͻ��� NTP ��������
 	��ȷ����ѡ��ķ������ķ��ʲ��ԣ� �����Ҫ�Ļ���
 	����һ����������ɡ�</para>
 
       <para>ѡ�����໥�����ӵ� NTP ��������һ�������⣬
 	������ij�����������ɴ ����ʱ�Ӳ��ɿ�ʱ�Ϳ����б��ѡ��
 	�������� &man.ntpd.8;
 	�����ܵ�ѡ�����յ�����Ӧ&mdash;�����������ʹ�ÿɿ��ķ�������</para>
     </sect2>
 
     <sect2>
       <title>�������Ļ���</title>
 
       <indexterm>
 	<primary>NTP</primary>
 	<secondary>����</secondary>
       </indexterm>
 
       <sect3>
 	<title>��������</title>
 	<indexterm><primary>ntpdate</primary></indexterm>
 
 	<para>���ֻ����ϵͳ����ʱͬ��ʱ�ӣ�
 	  �����ʹ�� &man.ntpdate.8;�� ���ھ�������������
 	  ���Ҳ���Ҫ����ͬ��������ϵͳ��˵��Ƚ��ʺϣ�
 	  ���������������Ӧ������ &man.ntpd.8;��</para>
 
 	<para>������ʱʹ�� &man.ntpdate.8; ��������� &man.ntpd.8;
 	  Ҳ��һ�������⡣ &man.ntpd.8; ����������ʱ�ӣ�
 	  �� &man.ntpdate.8; ��ֱ������ʱ�ӣ�
 	  ���ۻ����ĵ�ǰʱ�����ȷʱ���ж���ƫ�</para>
 
 	<para>Ҫ��������ʱ�� &man.ntpdate.8;�� ��Ҫ��
 	  <literal>ntpdate_enable="YES"</literal> �ӵ�
 	  <filename>/etc/rc.conf</filename> �С� ���⣬
 	  ����Ҫͨ�� <varname>ntpdate_flags</varname>
 	  ������ͬ���ķ�������ѡ�
 	  ���ǽ����ݸ� &man.ntpdate.8;��</para>
       </sect3>
 
       <sect3>
 	<title>һ������</title>
 
 	<indexterm>
 	  <primary>NTP</primary>
 	  <secondary>ntp.conf</secondary>
 	</indexterm>
 
 	<para>NTP ��ͨ��
 	  <filename>/etc/ntp.conf</filename> �ļ����������õģ�
 	  ���ʽ�� &man.ntp.conf.5; �н�����������
 	  ������һ�����ӣ�</para>
 
 	<programlisting>server ntplocal.example.com prefer
 server timeserver.example.org
 server ntp2a.example.net
 
 driftfile /var/db/ntp.drift</programlisting>
 
 	<para>��� <literal>server</literal> ѡ��ָ����ʹ����һ����������
 	  ÿһ��������������һ�С� ���ijһ̨��������ָ���� <literal>prefer</literal>
 	  (ƫ��) ������ ������� <hostid
 	  role="fqdn">ntplocal.example.com</hostid>��
 	  �������ѡ�������������
 	  ���ƫ�õķ���������������������Ӧ���������IJ��
 	  ����������Ӧ�� ����ʹ������������Ӧ��
 	  �������������������� һ����˵��
 	  <literal>prefer</literal> ����Ӧ�ñ�ע�ڷdz���ȷ�� NTP
 	  ʱԴ�� ������Щ���������ʱ����Ӳ���ķ������ϡ�</para>
 
 	<para>�� <literal>driftfile</literal> ѡ�
 	  ��ָ������������ϵͳʱ��Ƶ��ƫ����ļ���
 	  &man.ntpd.8; ����ʹ�������Զ��ز���ʱ�ӵ���ȻƯ�ƣ�
 	  �Ӷ�ʹʱ�Ӽ�ʹ���ж�������ʱԴ������£�
 	  ���ܱ����൱��׼ȷ�ȡ�</para>
 
 	<para>���⣬ <literal>driftfile</literal>
 	  ѡ��Ҳ������һ����Ӧ��ʹ�õ� NTP ����������Ϣ��
 	  ����ļ������� NTP ���ڲ���Ϣ�� ����Ӧ���κ����������޸ġ�</para>
       </sect3>
 
       <sect3>
 	<title>�������ķ������ķ���</title>
 
 	<para>Ĭ������£� NTP ���������Ա����� Internet �ϵ��������ʡ�
 	  ����� <filename>/etc/ntp.conf</filename> ��ָ�� <literal>restrict</literal>
 	  ������ ����Կ���������Щ�����������ķ�������</para>
 
 	<para>���ϣ���ܾ����еĻ����������� NTP
 	  �������� ֻ����
 	  <filename>/etc/ntp.conf</filename> �м��룺</para>
 
         <programlisting>restrict default ignore</programlisting>
 
 	<note>
 	  <para>���������ֹ���ķ����������ڱ����������г��ķ�������
 	    �������Ҫ�� NTP ������������ NTP
 	    ������ͬ��ʱ�䣬 ��Ӧ����ָ���������� ��μ������ֲ�
 	    &man.ntp.conf.5; ���˽��һ����ϸ�ڡ�</para>
 	</note>
 
         <para>���ֻϣ�������ڵĻ���ͨ�����ķ�����ͬ��ʱ�ӣ�
 	  ����������������Ϊ�������� ����Ϊͬ��ʱ�ӵĽڵ���ʱ�ã�
 	  �����</para>
 
         <programlisting>restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap</programlisting>
 
 	<para>��� ��Ҫ�� <hostid role="ipaddr">192.168.1.0</hostid> ��Ϊ�������ϵ�
 	  IP ��ַ�� ���� <hostid
 	  role="netmask">255.255.255.0</hostid> ��Ϊ�����������롣</para>
 
 	<para><filename>/etc/ntp.conf</filename> ���ܰ������
 	  <literal>restrict</literal> ѡ� Ҫ�˽��һ����ϸ�ڣ�
 	  ��μ� &man.ntp.conf.5; ��
 	  <literal>Access Control Support</literal>(���ʿ���֧��)
 	  С�ڡ�</para>
       </sect3>
     </sect2>
 
     <sect2>
       <title>���� NTP ������</title>
 
       <para>Ҫ�� NTP ��������ϵͳ����ʱ��֮������
 	��Ҫ�� <literal>ntpd_enable="YES"</literal> ���뵽
 	<filename>/etc/rc.conf</filename> �С�
 	���ϣ���� &man.ntpd.8; ���ݸ�������� ��Ҫ�༭
 	<filename>/etc/rc.conf</filename> �е�
 	<varname>ntpd_flags</varname>��</para>
 
       <para>Ҫ�ڲ���������������ǰ���������������� ��Ҫ�ֹ�����
 	<command>ntpd</command>�� ������
 	<filename>/etc/rc.conf</filename>
 	�е� <varname>ntpd_flags</varname> ��ָ���IJ�����
 	���磺</para>
 
       <screen>&prompt.root; <userinput>ntpd -p /var/run/ntpd.pid</userinput></screen>
     </sect2>
 
     <sect2>
       <title>����ʱ�Ե� Internet ������ʹ�� ntpd</title>
 
       <para>&man.ntpd.8; �������������������Ҫ�����Ե� Internet ���ӡ�
 	Ȼ���� ���������ʱ������������Ϊ���貦�ŵģ�
 	��ô��ֹ NTP ͨѶƵ���������ţ� �򱣳����Ӿ��б�Ҫ�ˡ�
 	�����ʹ���û��� PPP�� ����ʹ�� <literal>filter</literal>
 	��䣬 �� <filename>/etc/ppp/ppp.conf</filename> �н��б�Ҫ�����á�
 	���磺</para>
 
       <programlisting> set filter dial 0 deny udp src eq 123
  # Prevent NTP traffic from initiating dial out
  set filter dial 1 permit 0 0
  set filter alive 0 deny udp src eq 123
  # Prevent incoming NTP traffic from keeping the connection open
  set filter alive 1 deny udp dst eq 123
  # Prevent outgoing NTP traffic from keeping the connection open
  set filter alive 2 permit 0/0 0/0</programlisting>
 
       <para>Ҫ�˽��һ������Ϣ�� ��ο� &man.ppp.8; �� <literal>PACKET
 	FILTERING</literal>(������) С�ڣ� �Լ�
 	<filename>/usr/share/examples/ppp/</filename> �е����ӡ�</para>
 
       <note>
 	<para>ijЩ Internet �����ṩ�̻���ֹ�ͱ�ŵĶ˿ڣ�
 	  ��ᵼ�� NTP �޷����������� ��Ϊ��Ӧ�޷��������Ļ�����</para>
       </note>
     </sect2>
 
     <sect2>
       <title>��һ������Ϣ</title>
 
       <para>���� NTP ���������ĵ��� ������
 	<filename>/usr/share/doc/ntp/</filename> �ҵ� HTML
 	��ʽ�İ汾��</para>
     </sect2>
   </sect1>
 
   <sect1 id="network-syslogd">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Tom</firstname>
           <surname>Rhodes</surname>
           <contrib>Contributed by </contrib>
         </author>
       </authorgroup>
     </sect1info>
 
     <title>ʹ�� <command>syslogd</command> ��¼Զ����������־</title>
 
     <para>����ϵͳ��־����ϵͳ��ȫ�͹�����һ����Ҫ���档
       ���ж�̨�ֲ������ͻ��������Ļ������ٻ����Ǵ��ڸ��ֲ�ͬ���͵������У�
       ���������������־�ļ����Ե÷dz����Բ����� ����������£�
       ����Զ����־��¼��ʹ�����������̱�ø������ɡ�</para>
 
     <para>���м�¼��־��һָ̨���Ļ����ܹ�����һЩ��־�ļ������ĸ�����
       ��־�ļ����ռ��� �ϲ���ѭ��������һ�����ã�
       ʹ�� &os; ԭ���Ĺ��ߣ� ���� &man.syslogd.8; �� &man.newsyslog.8;��
       �����µ�����ʾ���У� ���� <hostid>A</hostid>�� ����Ϊ
       <hostid role="fqdn">logserv.example.com</hostid>��
       �������ռ������������־��Ϣ�� ���� <hostid>B</hostid>��
       ����Ϊ <hostid role="fqdn">logclient.example.com</hostid>
       ������־��Ϣ���͸��������� ����ʵ�У�
       ��������������Ҫ������ȷ������ͷ���� <acronym>DNS</acronym>
       ������ <filename>/etc/hosts</filename> �м�¼��
       ���� ���ݽ������������ա�</para>
 
     <sect2>
       <title>��־������������</title>
 
       <para>��־�����������ó���������Զ��������־��Ϣ�Ļ�����
         �ڴ���������������Ϊ�˷������ã� ������Ϊ�˸��õĹ�����
         �����Ǻ�ԭ�� �ڼ�������֮ǰ��Ҫ��һЩ����������</para>
 
       <para>һ����ȷ���õ���־����������������¼����������������</para>
 
       <itemizedlist>
 	<listitem>
           <para>�������Ϳͻ��˵ķ���ǽ�������� 514 �˿��ϵ�
             <acronym>UDP</acronym> ����ͨ����</para>
 	</listitem>
 
 	<listitem>
           <para>syslogd �����óɽ��ܴ�Զ�̿ͻ���������Ϣ��</para>
 	</listitem>
 
 	<listitem>
           <para>syslogd �����������еĿͻ��˶�������������ȷ������ͷ���
             <acronym>DNS</acronym>�� ������
             <filename>/etc/hosts</filename> ������Ӧ���á�</para>
 	</listitem>
       </itemizedlist>
 
       <para>������־�������� �ͻ��˱�����
         <filename>/etc/syslog.conf</filename> ���г�,
         ��ָ����־�� facility��</para>
 
       <programlisting>+logclient.example.com
 *.*     /var/log/logclient.log</programlisting>
 
       <note>
         <para>������ڸ��ֱ�֧�ֲ����õ� <emphasis>facility</emphasis>
           ���� &man.syslog.conf.5; �ֲ�ҳ���ҵ���</para>
       </note>
 
       <para>һ�������Ժ� ���д��� <literal>facility</literal>
         ��Ϣ���ᱻ��¼����ǰָ�����ļ�
 	<filename>/var/log/logclient.log</filename>��</para>
 
       <para>�ṩ����Ļ�������Ҫ����
 	<filename>/etc/rc.conf</filename> �����ã�</para>
 
       <programlisting>syslogd_enable="YES"
 syslogd_flags="-a logclient.example.com -v -v"</programlisting>
 
       <para>��һ��ѡ���ʾ��ϵͳ����ʱ���� <command>syslogd</command>
 	���� �ڶ���ѡ���ʾ������������������ָ����־Դ�ͻ��˵����ݡ�
 	�ڶ������������IJ��֣� ʹ�� <option>-v -v</option>��
 	��ʾ������־��Ϣ����ϸ�̶ȡ� �ڵ��� facility ���õ�ʱ��
 	������÷dz����ã� ��Ϊ����Ա�ܹ�������Щ��Ϣ����Ϊ�ĸ�
 	facility ����������¼��</para>
 
       <para>����ͬʱָ����� <option>-a</option> ѡ������������ͻ�����
 	���⣬ ������ָ�� <acronym>IP</acronym>
 	��ַ�����Σ� �����
 	&man.syslog.3; �����ֲ����˽�������õ������б���</para>
 
       <para>��� ��־�ļ�Ӧ�ñ������� �������ú��ַ���������
         ���� &man.touch.1; �ܺܺõ���ɴ�������</para>
 
       <screen>&prompt.root; <userinput>touch <filename>/var/log/logclient.log</filename></userinput></screen>
 
       <para>��ʱ�� Ӧ��������ȷ��һ�� <command>syslogd</command>
         �ػ����̣�</para>
 
       <screen>&prompt.root; <userinput>/etc/rc.d/syslogd restart</userinput>
 &prompt.root; <userinput>pgrep syslog</userinput></screen>
 
       <para>���������һ�� <acronym>PIC</acronym> �Ļ���
         �����Ӧ�ñ��ɹ�������,  ��������ʼ���ÿͻ��ˡ�
         ��������û�������Ļ��� ����
         <filename>/var/log/messages</filename>
         ��־�в�����������</para>
     </sect2>
 
     <sect2>
       <title>��־�ͻ�������</title>
 
       <para>��־�ͻ�����һ̨������־��Ϣ����־�������Ļ�����
         ���ڱ��ر��濽����</para>
 
       <para>����־���������ƣ� �ͻ���Ҳ��Ҫ����һЩ�������������</para>
 
       <itemizedlist>
 	<listitem>
           <para>&man.syslogd.8;
             ���뱻���óɷ���ָ�����͵���Ϣ���ܽ������ǵ���־��������</para>
 	</listitem>
 
 	<listitem>
           <para>����ǽ�������� 514 �˿��ϵ� <acronym>UDP</acronym> ��ͨ����</para>
 	</listitem>
 
 	<listitem>
           <para>�������������뷴�� <acronym>DNS</acronym>��
             ������ <filename>/etc/hosts</filename> ������ȷ�ļ�¼��</para>
 	</listitem>
       </itemizedlist>
 
       <para>��ȷ�������˵���ÿͻ��˸�����һЩ��
         �ͻ��˵Ļ����� <filename>/etc/rc.conf</filename>
         �������µ����ã�</para>
 
       <programlisting>syslogd_enable="YES"
 syslogd_flags="-s -v -v"</programlisting>
 
       <para>��ǰ�����ƣ� ��Щѡ�����ϵͳ��������������
 	<command>syslogd</command> ���� ��������־��Ϣ����ϸ�̶ȡ�
 	�� <option>-s</option>
 	ѡ�����ʾ��ֹ�����������������������־��</para>
 
       <para>Facility ������ij����Ϣ��ϵͳ���IJ������ɵġ� ������˵��
         <acronym>ftp</acronym> �� <acronym>ipfw</acronym> ���� facility��
         �����������������־��Ϣʱ�� ����ͨ������־��Ϣ�а����������ֹ��ߡ�
         Facility ͨ������һ�����ȼ���ȼ���
         �����������һ����־��Ϣ����Ҫ�̶ȡ� ����ͨ��Ϊ
         <literal>warning</literal> �� <literal>info</literal>��
         ����� &man.syslog.3; �ֲ�ҳ�Ի��һ���������õ�
         facility �����ȼ��б���</para>
 
       <para>��־�����������ڿͻ��˵� <filename>/etc/syslog.conf</filename>
         ��ָ���� �ڴ����У� <literal>@</literal>
         ���ű�������ʾ������־���ݵ�Զ�̵ķ�������
         ����ȥ�������������</para>
 
       <programlisting>*.*		@logserv.example.com</programlisting>
 
       <para>���Ӻ� �������� <command>syslogd</command>
         ʹ�������޸���Ч��</para>
 
       <screen>&prompt.root; <userinput>/etc/rc.d/syslogd restart</userinput></screen>
 
       <para>������־��Ϣ�Ƿ���ͨ�����緢�ͣ�
 	��׼��������Ϣ�Ŀͻ������� &man.logger.1; ����
 	<command>syslogd</command> ������Ϣ��</para>
 
       <screen>&prompt.root; <userinput>logger "<replaceable>Test message from logclient</replaceable>"</userinput></screen>
 
       <para>�����Ϣ����Ӧ��ͬʱ�����ڿͻ�����
 	<filename>/var/log/messages</filename> �Լ���־��������
 	<filename>/var/log/logclient.log</filename> �С�</para>
     </sect2>
 
     <sect2>
       <title>������־������</title>
 
       <para>��ijЩ����£� �����־������û���յ���Ϣ�Ļ�����Ҫ����һ���ˡ�
         �м������ܵ�ԭ�� ������������������ӵ������
         <acronym>DNS</acronym> �����⡣ Ϊ�˲�����Щ���⣬
         ��ȷ�����ߵĻ�������ʹ�� <filename>/etc/rc.conf</filename>
         �����趨�����������ʵ��Է��� �����������������Ļ���
         ��ô����Ҫ�� <filename>/etc/rc.conf</filename>
         �е� <literal>syslogd_flags</literal> ѡ����Щ�޸��ˡ�</para>
 
       <para>�����µ�ʾ���У�
         <filename>/var/log/logclient.log</filename> �ǿյģ�
         <filename>/var/log/message</filename> ��Ҳû�б����κ�ʧ�ܵ�ԭ��
         Ϊ�����ӵ��Ե������ �޸� <literal>ayalogd_flags</literal>
         ѡ�������������µ�ʾ���� ����������</para>
 
       <programlisting>syslogd_flags="-d -a logclien.example.com -v -v"</programlisting>
 
       <screen>&prompt.root; <userinput>/etc/rc.d/syslogd restart</userinput></screen>
 
       <para>����������֮�� ��Ļ�Ͻ������������������ĵ������ݣ�</para>
 
       <screen>logmsg: pri 56, flags 4, from logserv.example.com, msg syslogd: restart
 syslogd: restarted
 logmsg: pri 6, flags 4, from logserv.example.com, msg syslogd: kernel boot file is /boot/kernel/kernel
 Logging to FILE /var/log/messages
 syslogd: kernel boot file is /boot/kernel/kernel
 cvthname(192.168.1.10)
 validate: dgram from IP 192.168.1.10, port 514, name logclient.example.com;
 rejected in rule 0 due to name mismatch.</screen>
 
       <para>�����ԣ���Ϣ��������������ƥ��������յġ�
         ��һ��һ��ļ���������ļ�֮�� ������
         <filename>/etc/rc.conf</filename> �������������������</para>
 
       <programlisting>syslogd_flags="-d -a logclien.example.com -v -v"</programlisting>
 
       <para>����Ӧ�ð����� <literal>logclient</literal>�� ������
         <literal>logclien</literal>��
         ��������ȷ���޸IJ�����֮����ܼ���Ԥ�ڵ�Ч���ˣ�</para>
 
       <screen>&prompt.root; <userinput>/etc/rc.d/syslogd restart</userinput>
 logmsg: pri 56, flags 4, from logserv.example.com, msg syslogd: restart
 syslogd: restarted
 logmsg: pri 6, flags 4, from logserv.example.com, msg syslogd: kernel boot file is /boot/kernel/kernel
 syslogd: kernel boot file is /boot/kernel/kernel
 logmsg: pri 166, flags 17, from logserv.example.com,
 msg Dec 10 20:55:02 &lt;syslog.err&gt; logserv.example.com syslogd: exiting on signal 2
 cvthname(192.168.1.10)
 validate: dgram from IP 192.168.1.10, port 514, name logclient.example.com;
 accepted in rule 0.
 logmsg: pri 15, flags 0, from logclient.example.com, msg Dec 11 02:01:28 trhodes: Test message 2
 Logging to FILE /var/log/logclient.log
 Logging to FILE /var/log/messages</screen>
 
       <para>�˿̣� ��Ϣ�ܹ�����ȷ���ղ��������ļ��ˡ�</para>
     </sect2>
 
     <sect2>
       <title>��ȫ�Է����˼��</title>
 
       <para>�����������������һ���� ��ʵ������֮ǰ��Ҫ���ǰ�ȫ�ԡ�
         ��ʱ��־�ļ�Ҳ������������Ϣ�� ���籾�������������õķ���
         �û��ʺź��������ݡ� �ӿͻ��˷��������ݾ������絽���������
         ���ڼ��û�м���Ҳû�����뱣���� ����м�����Ҫ�Ļ���
         ����ʹ�� <filename role="package">security/stunnel</filename>��
         ������һ�����ܵ������д������ݡ�</para>
 
       <para>���ذ�ȫҲͬ���Ǹ����⡣ ��־�ļ���ʹ���л�ѭ��ת��û�б����ܡ�
         �����û����ܶ�ȡ��Щ�ļ��Ի�ö�ϵͳ��������˽⡣
         ������������� ����Щ�ļ�������ȷ��Ȩ���Ƿdz��б�Ҫ�ġ�
         &man.newsyslog.8; ����֧�ָ��´�����ѭ������־����Ȩ�ޡ�
         ����־�ļ���Ȩ������Ϊ <literal>600</literal>
         ����ֹ�����û�����Ҫ�Ŀ�̽��</para>
     </sect2>
   </sect1>
 </chapter>
diff --git a/zh_CN.GB2312/books/handbook/ppp-and-slip/chapter.xml b/zh_CN.GB2312/books/handbook/ppp-and-slip/chapter.xml
index 55bf7c23b6..2d14e538cd 100644
--- a/zh_CN.GB2312/books/handbook/ppp-and-slip/chapter.xml
+++ b/zh_CN.GB2312/books/handbook/ppp-and-slip/chapter.xml
@@ -1,2883 +1,2837 @@
 <?xml version="1.0" encoding="gb2312"?>
 <!--
      The FreeBSD Documentation Project
      The FreeBSD Simplified Chinese Project
 
      Original Revision: 1.196
      $FreeBSD$
 -->
 
 <chapter id="ppp-and-slip">
   <chapterinfo>
     <authorgroup>
       <author>
 	<firstname>Jim</firstname>
 	<surname>Mock</surname>
 	<contrib>Restructured, reorganized, and updated by </contrib>
 	<!-- 1 Mar 2000 -->
       </author>
     </authorgroup>
   </chapterinfo>
 
   <title>PPP �� SLIP</title>
 
   <sect1 id="ppp-and-slip-synopsis">
     <title>����</title>
-    <indexterm id="ppp-ppp">
-      <primary>PPP</primary>
-    </indexterm>
-    <indexterm id="ppp-slip">
-      <primary>SLIP</primary>
-    </indexterm>
 
     <para>FreeBSD �кܶ෽�����Խ����������������������
       ͨ��ʹ�ò��� modem ����������� Internet ���ӣ�
       ������������ͨ�����Ļ������������磬
-      ��Щ��Ҫ��ʹ�� PPP �� SLIP��
+      ��Щ��Ҫ��ʹ�� PPP<indexterm id="ppp-ppp"><primary>PPP</primary></indexterm> �� SLIP��<indexterm id="ppp-slip"><primary>SLIP</primary></indexterm>
       ���½���ϸ����������Щ���� modem ��ͨ�ŷ���ķ�����</para>
 
     <para>������һ�£� �����˽⣺</para>
 
     <itemizedlist>
       <listitem>
 	<para>��������û��� PPP��</para>
       </listitem>
       <listitem>
 	<para>��������ں˼� PPP�� (���� &os; 7.X)��</para>
       </listitem>
       <listitem>
 	<para>������� <acronym>PPPoE</acronym> (PPP over
 	  Ethernet)��</para>
       </listitem>
       <listitem>
 	<para>������� <acronym>PPPoA</acronym> (PPP over
 	  ATM)��</para>
 	</listitem>
       <listitem>
 	<para>������úͰ�װ SLIP �ͻ��˺ͷ������� (���� &os; 7.X)��</para>
       </listitem>
     </itemizedlist>
 
     <indexterm id="ppp-ppp-user">
       <primary>PPP</primary>
       <secondary>�û��� PPP</secondary>
     </indexterm>
     <indexterm id="ppp-ppp-kernel">
       <primary>PPP</primary>
       <secondary>�ں˼� PPP</secondary>
     </indexterm>
     <indexterm id="ppp-ppp-ethernet">
       <primary>PPP</primary>
       <secondary>PPPoE</secondary>
     </indexterm>
 
     <para>���Ķ�����֮ǰ�� ��Ӧ��</para>
 
     <itemizedlist>
       <listitem>
 	<para>��Ϥ�������������</para>
       </listitem>
       <listitem>
 	<para>���Ⲧ�����Ӻ� PPP�� SLIP �Ļ���֪ʶ��</para>
       </listitem>
     </itemizedlist>
 
     <para>��������֪���û��� PPP ���ں˼� PPP ֮��IJ�֮ͬ���� �ش�ܼ򵥣�
       �û��� PPP �����û����������������ݣ� �������ں˼���
       ���ں����û���֮�临�����ݵĻ���Ҫ��һЩ��
       �������ṩ���и������Ե�PPPʵ�֡�
       �û���PPPʹ�� <devicename>tun</devicename>
       �豸�����ͨ�Ŷ��ں˼� PPP ʹ��
       <devicename>ppp</devicename> �豸��</para>
 
     <note>
       <para>�������У� ���û������˵����
 	�� <application>ppp</application> ָ�����û�̬ PPP��
 	������Ҫ������ PPP ������ ����
 	<application>pppd</application> (���� &os;&nbsp;7.X) �������֡�
 	���⣬ ��û�ж����ע���� ���������ܵ����������Ҫ��
 	<username>root</username> ����������Ȩ�ޡ�</para>
     </note>
   </sect1>
 
   <sect1 id="userppp">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Tom</firstname>
           <surname>Rhodes</surname>
           <contrib>Updated and enhanced by </contrib>
         </author>
       </authorgroup>
       <authorgroup>
         <author>
           <firstname>Brian</firstname>
           <surname>Somers</surname>
 	  <contrib>Originally contributed by </contrib>
         </author>
       </authorgroup>
       <authorgroup>
 	<author>
 	  <firstname>Nik</firstname>
 	  <surname>Clayton</surname>
 	  <contrib>With input from </contrib>
         </author>
         <author>
 	  <firstname>Dirk</firstname>
           <surname>Fr&ouml;mberg</surname>
         </author>
         <author>
           <firstname>Peter</firstname>
           <surname>Childs</surname>
         </author>
       </authorgroup>
     </sect1info>
 
     <title>ʹ���û��� PPP</title>
 
     <warning>
       <para>�� &os; 8.0 ��ʼ�� &man.uart.4; ����ȡ����
 	&man.sio.4; ������ ���Ա�ʾ���ڵ��豸�ڵ��ɷֱ�
 	<filename>/dev/cuad<replaceable>N</replaceable></filename> ����
 	<filename>/dev/cuau<replaceable>N</replaceable></filename>��
 	����
 	<filename>/dev/ttyd<replaceable>N</replaceable></filename> ����
 	<filename>/dev/ttyu<replaceable>N</replaceable></filename>��
 	&os;&nbsp;7.X �û�������ʱ��Ҫ��Ӧ֮�������ļ����б�Ҫ�ĸ��ġ�</para>
     </warning>
 
     <sect2>
       <title>�û��� PPP</title>
 
       <sect3>
 	<title>ǰ������</title>
 
 	<para>���¼ٶ����߱�����������</para>
 
 	<itemizedlist>
-	  <indexterm id="ppp-isp">
-	    <primary>ISP</primary>
-	  </indexterm>
-	  <indexterm id="ppp-ppp2">
-	    <primary>PPP</primary>
-	  </indexterm>
 	  <listitem>
-	    <para>����һ�� ISP �ṩ����������ʹ�� PPP ���ʺš�</para>
+	    <para>����һ�� ISP<indexterm id="ppp-isp"><primary>ISP</primary></indexterm> �ṩ����������ʹ�� PPP<indexterm id="ppp-ppp2"><primary>PPP</primary></indexterm> ���ʺš�</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>����Ҫ��������ϵͳ�ϣ� ��������ȷ���õ� modem��
 	      �������ܹ������� ISP ���豸��</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>ISP �IJ��ź��롣</para>
 	  </listitem>
 
 	  <listitem>
-	  <indexterm id="ppp-pap">
-	    <primary>PAP</primary>
-	  </indexterm>
-	  <indexterm id="ppp-chap">
-	    <primary>CHAP</primary>
-	  </indexterm>
-	  <indexterm id="ppp-unix">
-	    <primary>UNIX</primary>
-	  </indexterm>
-	  <indexterm id="ppp-login">
-	    <primary>login name</primary>
-	  </indexterm>
-	  <indexterm id="ppp-password">
-	    <primary>password</primary>
-	  </indexterm>
-	    <para>���ĵ�¼���ƺ����� (������һ��� UNIX ���ĵ�¼��������ԣ�
-	    Ҳ������ PAP �� CHAP ��¼���������)��</para>
+	    <para>���ĵ�¼���ƺ����� (������һ��� UNIX<indexterm id="ppp-unix"><primary>UNIX</primary></indexterm> ���ĵ�¼��������ԣ�<indexterm id="ppp-login"><primary>login name</primary></indexterm><indexterm id="ppp-password"><primary>password</primary></indexterm>
+	    Ҳ������ PAP<indexterm id="ppp-pap"><primary>PAP</primary></indexterm> �� CHAP<indexterm id="ppp-chap"><primary>CHAP</primary></indexterm> ��¼���������)��</para>
 	  </listitem>
 
 	  <listitem>
-	    <indexterm id="ppp-nameserver">
-	      <primary>nameserver</primary>
-	    </indexterm>
-
 	    <para>һ���������������� IP ��ַ��
 	     ͨ���� �����ISP���õ�����������IP��ַ��
 	     ��������ٵõ���һ���� �Ϳ������ļ�
 	     <filename>ppp.conf</filename> ��� <command>enable dns</command>
 	     ����ʹ <application>ppp</application> ������������
-	     �������ȡ���� ISP ��֧�� DNS Э�̵ľ���ʵ�֡�</para>
+	     �������ȡ���� ISP ��֧�� DNS Э�̵ľ���ʵ�֡�<indexterm id="ppp-nameserver"><primary>nameserver</primary></indexterm></para>
 	  </listitem>
 	</itemizedlist>
 
 	<para>�������Ϣ������ ISP �ṩ�� �����DZ���ģ�</para>
 
 	<itemizedlist>
 	  <listitem>
 	    <para>ISP������IP��ַ�� ��������׼�����ӣ� ����Ϊ
 	     <emphasis>Ĭ��·��</emphasis> ��������
 	     �����û�������Ϣ�� �������鹹һ����
 	     ������ʱ ISP �� PPP ���������Զ���������ȷ��ֵ��</para>
 
 	    <para>����鹹�� IP ��ַ�� <application>ppp</application> �м���
 	      <literal>HISADDR</literal>��</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>׼��ʹ�õ��������롣 ���ISPû���ṩ�� һ��ʹ��
 	    <hostid role="netmask">255.255.255.255</hostid> ��û������ġ�</para>
 	  </listitem>
 
 	  <listitem>
-	    <indexterm id="ppp-static-ip">
-	      <primary>static IP address (��̬ IP ��ַ)</primary>
-	    </indexterm>
-
 	    <para>��� ISP �ṩ�˾�̬��IP��ַ���������� �����������ǡ�
-	    ��֮�� ��Ӧ�öԷ�����ָ������Ϊ���ʵ� IP ��ַ��</para>
+	    ��֮�� ��Ӧ�öԷ�����ָ������Ϊ���ʵ� IP ��ַ��<indexterm id="ppp-static-ip"><primary>static IP address (��̬ IP ��ַ)</primary></indexterm></para>
 	  </listitem>
 	</itemizedlist>
 
 	<para>�������֪����Щ��Ϣ�� �������� ISP ��ϵ��</para>
 
 	<note><para>������У� ������Ϊ����չʾ�������ļ��ж����кš�
 	    ��Щ�к�ֻ��Ϊ��ʹ���ͺ����۱�÷��㣬 ����ʵ���ļ��в������ڡ�
 	    ���⣬ �ڱ�ҪʱӦʹ�� Tab �Ϳո�������������</para>
 	</note>
 
       </sect3>
 
       <sect3>
         <title><application>PPP</application>�Զ�������</title>
 
 	<indexterm>
 	  <primary>PPP</primary>
 	  <secondary>configuration (����)</secondary>
 	</indexterm>
 
 	<para> <command>ppp</command>��<command>pppd</command>(PPP���ں˼�ʵ�֣� ���� &os;&nbsp;7.X)
 	  ��ʹ�� <filename class="directory">/etc/ppp</filename> Ŀ¼�е������ļ��� �û��� PPP
 	  �����ӿ�����
 	  <filename class="directory">/usr/share/examples/ppp/</filename> ���ҵ���</para>
 
 	<para>����<command>ppp</command>Ҫ�����������Ҫ�༭�����ļ���
 	  �༭�ļ����ļ�ȡ��������
 	  IP �Ǿ�̬���� (ÿ�ζ�ʹ��ͬһ����ַ)
 	  ���Ƕ�̬����� (ÿ�����ӵ� ISP �����ò�ͬ�� IP ��ַ)��</para>
 
 	<sect4 id="userppp-staticIP">
 	  <title>PPP�;�̬IP��ַ</title>
 
 	  <indexterm>
             <primary>PPP</primary>
             <secondary>with static IP addresses</secondary>
           </indexterm>
 
 	  <para>����Ҫ�༭�����ļ�<filename>/etc/ppp/ppp.conf</filename>�� ������ʾ��</para>
 
 	  <note>
 	    <para>��ð��<literal>:</literal>��β���дӵ�һ�� (����)��ʼ��
 	      �������е��ж�Ҫʹ�ÿո���Ʊ��� (Tab) ��������</para>
 	  </note>
 
 	  <programlisting>1     default:
 2       set log Phase Chat LCP IPCP CCP tun command
 3       ident user-ppp VERSION (built COMPILATIONDATE)
 4       set device /dev/cuau0
 5       set speed 115200
 6       set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \
 7                 \"\" AT OK-AT-OK ATE1Q0 OK \\dATDT\\T TIMEOUT 40 CONNECT"
 8       set timeout 180
 9       enable dns
 10
 11    provider:
 12      set phone "(123) 456 7890"
 13      set authname foo
 14      set authkey bar
 15      set login "TIMEOUT 10 \"\" \"\" gin:--gin: \\U word: \\P col: ppp"
 16      set timeout 300
 17      set ifaddr <replaceable>x.x.x.x</replaceable> <replaceable>y.y.y.y</replaceable> 255.255.255.255 0.0.0.0
 18      add default HISADDR</programlisting>
 
 	  <variablelist>
 	    <varlistentry>
 	      <term>��1��</term>
 
 	      <listitem>
 		<para>ָ��Ĭ�ϵ�� ��PPP����ʱ������е�����Զ�ִ�С�</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>��2��</term>
 
 	      <listitem>
 		<para>���õ�¼������ ���������� Ϊ��������������־�ļ��� ����Ӧ�ü�Ϊ��</para>
 
 	        <programlisting>set log phase tun</programlisting>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>�� 3��</term>
 
 	      <listitem>
 		<para>���� PPP ������Է���ʶ�Լ���
                   ����ڽ�����ʹ������ʱ�����κ��鷳�� PPP�ͻ���Է��������ұ�ʶ��
                   �Է���������Ա�ڴ����������ʱ�� ��Щ��Ϣ�����á�</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>�� 4��</term>
 
 	      <listitem>
 		<para>����modemҪ���ӵĶ˿ںš�
                   <devicename>COM1</devicename> ��Ӧ���豸��
 		  <filename class="devicefile">/dev/cuau0</filename>
                   �� <devicename>COM2</devicename>
 		  ��Ӧ������
 		  <filename class="devicefile">/dev/cuau1</filename>��</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>�� 5��</term>
 
 	      <listitem>
 		<para>�������ӵ��ٶȡ� ��� 115200
 		  �����⣬ ���� 38400��</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>�� 6 &amp; 7��</term>
 
 	      <listitem>
-		<indexterm>
-		  <primary>PPP</primary>
-		  <secondary>user PPP</secondary>
-		</indexterm>
-
-		<para>�����ַ����� �û��� PPP ʹ��һ���� &man.chat.8;�������Ƶ��﷨��
+		<para>�����ַ����� �û��� PPP<indexterm><primary>PPP</primary><secondary>user PPP</secondary></indexterm> ʹ��һ���� &man.chat.8;�������Ƶ��﷨��
 		   ��ο������ֲ��˽��������Ե������Ϣ��</para>
 
 		<para>ע�⣬ Ϊ�˱����Ķ�����������˻��С� �κ�
 		  <filename>ppp.conf</filename> ������������������
 		  ǰ�����е����һ���ַ������� <literal>\</literal>��</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>�� 8��</term>
 
 	      <listitem>
 		<para>�������ӵ�ʱ������ Ĭ���� 180 �룬 ������һ���Ƕ���ġ�</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>�� 9��</term>
 
 	      <listitem>
 		<para>����PPP��Է�����ȷ�ϱ��������������á�
 		  ����������˱��ص������������� Ҫע�ͻ�ɾ������һ�С�</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>�� 10��</term>
 
 	      <listitem>
 		<para>Ϊ�˿ɶ��Ե���Ҫ����һ�����С� ���лᱻPPP���ԡ�</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>�� 11��</term>
 
 	      <listitem>
 		<para>Ϊ <quote>provider</quote>ָ��һ��� ���Ըij�
 		 <acronym>ISP</acronym>�����֣� �������Ժ�Ϳ���ʹ��
 		 <option>load <replaceable>ISP</replaceable></option> ���������ӡ�</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>�� 12��</term>
 
 	      <listitem>
 		<para>�����ṩ�̵ĵ绰���롣 ����绰�������ʹ��ð�� (<literal>:</literal>)
 		  ��ܵ����� (<literal>|</literal>) ������
 		  �������ַ���������&man.ppp.8;�������ֲ����н��ܡ�
 		  �ܵ������� �����Ҫѭ��ʹ����Щ���룬 ����ʹ��ð�š�
 		  �������ʹ�õ�һ�����룬 ����һ������ʧ�������õڶ������룬
 		  ��ʹ�ùܵ����š� ����ʾ�������� Ҫ�������绰�����������(")��</para>
 
 	      <para> ����绰�������пո� ����������(<literal>"</literal>)������������
 		     �������ɼ�ȴ���Բ���Ĵ���</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>�� 13 &amp; 14��</term>
 
 	      <listitem>
 		<para>ָ���û��������롣 ��ʹ�� &unix; ����������ʾ����¼ʱ��
 		  ��Щֵ�����ô��� \U \P ������ <command>set login</command>
 		  ��������޸ġ� ��ʹ��PAP��CHAP��������ʱ�� ��Щֵ����֤ʹ�á�</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>�� 15��</term>
 
 	      <listitem>
-		<indexterm><primary>PAP</primary></indexterm>
-		<indexterm><primary>CHAP</primary></indexterm>
 		<para>�����ʹ�õ���PAP����CHAP�� ������Ͳ����е�¼��
 		  Ҫע�ͻ�ɾ������һ�С�
-		  ��ο� <link linkend="userppp-PAPnCHAP">PAP �� CHAP��֤</link>
+		  ��ο� <link linkend="userppp-PAPnCHAP">PAP<indexterm><primary>PAP</primary></indexterm> �� CHAP��֤<indexterm><primary>CHAP</primary></indexterm></link>
 		  ���˽����ϸ�ڡ�</para>
 
                 <para>��¼�����ǵ��﷨��chat���͵ġ� ������������������ģ�</para>
 
 		<screen>J. Random Provider
 login: <replaceable>foo</replaceable>
 password: <replaceable>bar</replaceable>
 protocol: ppp</screen>
 
 		<para>����Ҫ�ı�����ű����ʺ����Լ�����Ҫ��
 		  ������һ��д����ű�ʱ�� Ӧ��ȷ���Ѿ�����
 		  <quote>chat</quote> �����ڵ�¼״̬��
 		  ����������ȷ��ͨ���Ƿ����ڰ��ƻ����С�</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>��16��</term>
 
 	      <listitem>
-		<indexterm><primary>timeout</primary></indexterm>
-
 		<para>����Ĭ�ϵij�ʱʱ�䡣 ��� �������� 300
 		  ��������Ӧ�����Ͽ���������������óɳ�ʱ��
-		  �����ֵ���ó�0�� ����������ʹ�� <option>-ddial</option> ѡ�</para>
+		  �����ֵ���ó�0�� ����������ʹ�� <option>-ddial</option> ѡ�<indexterm><primary>timeout</primary></indexterm></para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>�� 17��</term>
 	      <listitem>
-		<indexterm><primary>ISP</primary></indexterm>
-
-		<para>���ýӿڵ�ַ�� ����Ҫ�� ISP �ṩ������ IP ��ַ�滻�ַ���
+		<para>���ýӿڵ�ַ�� ����Ҫ�� ISP<indexterm><primary>ISP</primary></indexterm> �ṩ������ IP ��ַ�滻�ַ���
 		  <replaceable>x.x.x.x</replaceable>�� �� ISP ������ IP
 		  ��ַ (����Ҫ���ӵ�����) �滻�ַ���
 		  <replaceable>y.y.y.y</replaceable>��
 		  ���ISPû�и����ṩ���ص�ַ�� ����ʹ��
 		  <hostid role="netmask">10.0.0.2/0</hostid>��
 		  �������Ҫʹ��һ�� <quote>�µ�</quote>�ĵ�ַ��
 		  ��ȷ���� <filename>/etc/ppp/ppp.linkup</filename>
 		  ��Ϊÿ�� <link linkend="userppp-dynamicIP">PPP�Ͷ�̬IP��ַ</link>
 		  ָ�������һ� ���û����һ�У� <command>ppp</command>
 		  ���޷��� <option>-auto</option> ģʽ���С�</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>��18��</term>
 
 	      <listitem>
 		<para>����һ����ISP���ص�Ĭ��·�ɡ�
 		  <literal>HISADDR</literal>����ؼ��ֻᱻ��17����ָ�������ص�ַ�滻��
 		  ���б�������ڵ�17��֮�������� <literal>HISADDR</literal>
 		  ��ʼ��֮ǰʹ������ֵ��</para>
 
 		<para>���������ʹ�� <option>-auto</option> �� PPP��������ӦŲ��
                   <filename>ppp.linkup</filename> �ļ��С�</para>
 	      </listitem>
 	    </varlistentry>
 	  </variablelist>
 
 	  <para>������һ����̬IP��ַ�� ��ʹ��<option>-auto</option>
 	    ģʽ����ppp(��Ϊ������֮ǰ�Ѿ���ȷ������·�ɱ���)�� �ǾͲ���Ҫ����<filename>ppp.linkup</filename>
            ����� ������ϣ���������Ժ󴴽�һ���������ó��� �����Ժ��sendmail�������л���͡�</para>
 
 	  <para>ʾ�������ļ�������Ŀ¼
 	    <filename class="directory">/usr/share/examples/ppp/</filename> ���ҵ���</para>
 	</sect4>
 
 	<sect4 id="userppp-dynamicIP">
 	  <title>PPP�Ͷ�̬IP��ַ</title>
 
 	  <indexterm>
             <primary>PPP</primary>
             <secondary>with dynamic IP addresses</secondary>
           </indexterm>
 
 	  <indexterm>
             <primary>IPCP</primary>
           </indexterm>
 
 	  <para>���ISPû����ָ����̬��IP��ַ�� <command>ppp</command>Ҫ�����ó��ܹ���Է�Э��ȷ�����غ�Զ�̵�ַ��
 	    Ҫ���������� ��Ҫ<quote>��</quote>һ��IP��ַ�� Ȼ������
 	    <command>ppp</command>�����Ӻ�ʹ��IP����Э��(IPCP)������ȷ���á�
 	    <filename>ppp.conf</filename>����������
 	    <link linkend="userppp-staticIP">PPP�;�̬IP��ַ</link>һ���ģ� �������µĸı䣺</para>
 
 	  <programlisting>17      set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 0.0.0.0</programlisting>
 
 	  <para>�ٴ�ǿ���� ��Ҫ�����кţ� ��ֻ��һ�����ñ�ǡ� ����һ���ո��DZ���ġ�</para>
 
 	  <variablelist>
 	    <varlistentry>
 	      <term>��17��</term>
 
 	      <listitem>
 		<para><literal>/</literal> �ַ������� PPP ��Ҫ��ĵ�ַ���롣
 		�����Ը�����Ҫʹ�ò�ͬ IP ��ַ�� �����ϵ�������Զ�ǿ��еġ�</para>
 
 		<para>���IJ���(<literal>0.0.0.0</literal>)����
 		  PPP��<hostid
 		    role="ipaddr">0.0.0.0</hostid> ������ <hostid
 		    role="ipaddr">10.0.0.1</hostid> ��ʼЭ�̵�ַ�� ������ЩISP��
 		  ���DZ���ġ� ��Ҫ�� <literal>0.0.0.0</literal>
 		  ��Ϊ <command>set ifaddr</command> �ĵ�һ��������
 		  ��Ϊ��ʹ�� PPP �� <option>-auto</option> ģʽʱ�������ó�ʼ·�ɡ�</para>
 	      </listitem>
 	    </varlistentry>
 	  </variablelist>
 
 	  <para>�����������<option>-auto</option>ģʽ��
 	  ����Ҫ��<filename>/etc/ppp/ppp.linkup</filename>�д���һ���
 	   ���ӽ���֮�� <filename>ppp.linkup</filename>�����á� ��ʱ��
 	   <command>ppp</command>��ָ�ɽӿڵ�ַ�� ����������·�ɱ��</para>
 	 <programlisting>1     provider:
 2        add default HISADDR</programlisting>
 
 	  <variablelist>
 	    <varlistentry>
 	      <term>�� 1��</term>
 
 	      <listitem>
 		<para>Ϊ�˽������ӣ�
 		  <command>ppp</command> �ᰴ�����¹�����
 		  <filename>ppp.linkup</filename>Ѱ����:���ȣ� ��ͼѰ����ͬ�ı�ǩ
 		  (��ͬ��<filename>ppp.conf</filename>һ������ ���ʧ���ˣ�
 		  Ѱ����Ϊ���� IP ��ַ��� �������ĸ���λ�ֽڵķ��
 		  �������û���ҵ��� ��Ѱ�� <literal>MYADDR</literal> ��</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>�� 2��</term>
 
 	      <listitem>
 		<para>���и��� <command>ppp</command>����ָ��
 		  <literal>HISADDR</literal>��Ĭ��·�ɡ�
 		  <literal>HISADDR</literal>��ͨ��IPCPЭ�̵õ���IP���滻��</para>
 	      </listitem>
 	    </varlistentry>
 	  </variablelist>
 
 	  <para>�ο�<filename>/usr/share/examples/ppp/ppp.conf.sample</filename>
 	    ��<filename>/usr/share/examples/ppp/ppp.linkup.sample</filename>
 	    �е�<literal>pmdemand</literal>���Ի�ȡϸ�ڻ������ӡ�</para>
 	</sect4>
 
 	<sect4>
 	  <title>���ղ���</title>
 
 	  <indexterm>
             <primary>PPP</primary>
             <secondary>receiving incoming calls</secondary>
           </indexterm>
 
 	  <para>��Ҫ���� <application>ppp</application>��������LAN�ϵ�
 	    ����ʱ�� ����Ҫ�����Ƿ񽫰�ת��LAN�� ����ǵĻ��� ���ͱ���� LAN
 	    �����и��Է�����һ��IP�� ��Ҫ���ļ� <filename>/etc/ppp/ppp.conf</filename>
 	    ��ʹ������ <command>enable proxy</command>�� ����Ӧ��ȷ���ļ�
 	    <filename>/etc/rc.conf</filename> �а����������ݣ�</para>
 
 	  <programlisting>gateway_enable="YES"</programlisting>
 	</sect4>
 
 	  <sect4>
 	    <title>ʹ���ĸ�getty��</title>
 
 	    <para><link linkend="dialup">���� FreeBSD �IJ��ŷ���</link>
 	     ����������� &man.getty.8; ���������ŷ���</para>
 
 	    <para>���� <command>getty</command> ֮�⻹�� <ulink
 		url="http://mgetty.greenie.net/">mgetty</ulink> (��ͨ��
 	      <filename role="package">comms/mgetty+sendfax</filename> port
 	      ����װ)��
 	      ���� <command>getty</command> �����ܰ汾�� �ǰ��ղ����ߵ�˼����Ƶġ�</para>
 
 	    <para>ʹ�� <command>mgetty</command> �ĺô������ܻ������� modem ����
 	      <emphasis>�Ự</emphasis>��
 	      �����ζ�������<filename>/etc/ttys</filename>�еĶ˿ڱ��رգ�
 	      ����moderm�Ͳ����Ӧ���롣</para>
 
 	    <para>���°汾�� <command>mgetty</command> (��
 	      0.99beta ��) Ҳ֧���Զ���� PPP ��������
 	      ��������ͻ��˲�ʹ�ýű�Ҳ�ܷ��ʷ������ˡ�</para>
 
 	    <para>�ο�<link linkend="userppp-mgetty">Mgetty ��
 	      AutoPPP</link>�������ֲ��˽������Ϣ��</para>
 	  </sect4>
 
 	  <sect4>
 	    <title><application>PPP</application> Ȩ��</title>
 
 	    <para><command>ppp</command> ����ͨ�������� <username>root</username>
 	      �û����������С� ���ϣ������ͨ�û����������� <command>ppp</command>
 	      ���� (������������������)�� �ͱ���Ѵ��û�����
 	      <groupname>network</groupname> �飬 ʹ�������� <command>ppp</command>
 	      ��Ȩ�ޡ�</para>
 
 	    <para>������Ҫʹ��<command>allow</command>����ʹ�û��ܷ���������
 	    ����һ���������֣�</para>
 	    <programlisting>allow users fred mary</programlisting>
 
 	    <para>������������� <literal>default</literal>
 	      �����У� ��������ָ�����û������κζ�����</para>
 	  </sect4>
 
 	  <sect4>
 	    <title>��̬IP�û���PPP Shell</title>
 
 	    <indexterm>
               <primary>PPP shells</primary>
             </indexterm>
 
 	    <para>����һ����Ϊ<filename>/etc/ppp/ppp-shell</filename>�ļ��� �����������ݣ�</para>
 	    <programlisting>#!/bin/sh
 IDENT=`echo $0 | sed -e 's/^.*-\(.*\)$/\1/'`
 CALLEDAS="$IDENT"
 TTY=`tty`
 
 if [ x$IDENT = xdialup ]; then
         IDENT=`basename $TTY`
 fi
 
 echo "PPP for $CALLEDAS on $TTY"
 echo "Starting PPP for $IDENT"
 
 exec /usr/sbin/ppp -direct $IDENT</programlisting>
 
 	    <para>����ű�Ҫ�п�ִ�����ԡ� Ȼ��ͨ�����������һ��ָ��˽ű�����Ϊ
 	       <filename>ppp-dialup</filename>�ķ������ӣ�</para>
 
 	    <screen>&prompt.root; <userinput>ln -s ppp-shell /etc/ppp/ppp-dialup</userinput></screen>
 
 	    <para>��Ӧ�ý�����ű���Ϊ���в����û���
 	      <emphasis>shell</emphasis>��
 	      ���������ļ� <filename>/etc/passwd</filename>
 	      �й��� PPP �û�
 	      <username>pchilds</username> ������ (�мǣ�
 	      ��Ҫֱ���޸���������ļ��� �� &man.vipw.8; ���޸���)��</para>
 
 	    <programlisting>pchilds:*:1011:300:Peter Childs PPP:/home/ppp:/etc/ppp/ppp-dialup</programlisting>
 
 	    <para>����һ����Ϊ <filename class="directory">/home/ppp</filename>
 	      ��Ŀ¼��Ϊ�����û�����Ŀ¼�� ���а���������Щ���ļ���</para>
 
 	    <screen>-r--r--r--   1 root     wheel           0 May 27 02:23 .hushlogin
 -r--r--r--   1 root     wheel           0 May 27 02:22 .rhosts</screen>
 
 	    <para>�����Ϳ��Է�ֹ<filename>/etc/motd</filename>����ʾ������</para>
 	  </sect4>
 
 	  <sect4>
 	    <title>��̬IP�û���Shell </title>
 
 	    <indexterm>
               <primary>PPP shells</primary>
             </indexterm>
 
 	    <para>��������������<filename>ppp-shell</filename>�ļ���
 	      Ϊÿ����̬����IP�û�����һ���� <filename>ppp-shell</filename>��
 	      �������ӡ�</para>
 
 	    <para>���磬 �����ϣ��Ϊ���������û���
 	      <username>fred</username>�� <username>sam</username>�� ��
 	      <username>mary</username> ·�� /24 CIDR �����磬 ����Ҫ�����������ݣ�</para>
 
 	    <screen>&prompt.root; <userinput>ln -s /etc/ppp/ppp-shell /etc/ppp/ppp-fred</userinput>
 &prompt.root; <userinput>ln -s /etc/ppp/ppp-shell /etc/ppp/ppp-sam</userinput>
 &prompt.root; <userinput>ln -s /etc/ppp/ppp-shell /etc/ppp/ppp-mary</userinput></screen>
 
 	    <para>ÿ���û���Shell���뱻���һ����������(�����û�
 	      <username>mary</username>��ShellӦ����<filename>/etc/ppp/ppp-mary</filename>)��</para>
 	  </sect4>
 
 	  <sect4>
 	    <title>Ϊ��̬IP�û�����<filename>ppp.conf</filename> </title>
 
 	    <para> <filename>/etc/ppp/ppp.conf</filename>�ļ�Ӧ�ð�������
 	    ����</para>
 
 	    <programlisting>default:
   set debug phase lcp chat
   set timeout 0
 
 ttyu0:
   set ifaddr 203.14.100.1 203.14.100.20 255.255.255.255
   enable proxy
 
 ttyu1:
   set ifaddr 203.14.100.1 203.14.100.21 255.255.255.255
   enable proxy</programlisting>
 
 	    <note>
 	      <para>�����ñ���ġ�</para>
 	    </note>
 
 	    <para> <literal>default:</literal>����ÿ�λỰʱ������ء� ÿ����
 	      <filename>/etc/ttys</filename> �����õ��ж�����Ϊ�䴴��һ��������
 	      <literal>ttyu0:</literal> ��� ÿһ��Ӧ�ôӶ�̬ IP
 	      ��ַ����ȡ��Ψһ��IP��ַ��</para>
 	  </sect4>
 
 	  <sect4>
 	    <title>Ϊ��̬ IP �û����� <filename>ppp.conf</filename></title>
 
 	    <para>�������� <filename>/usr/share/examples/ppp/ppp.conf</filename> �ļ������ݣ�
 	    ������Ϊÿ����̬�����û�����һ��� ���Ǽ�����
 	    <username>fred</username>�� <username>sam</username>
 	    �Լ� <username>mary</username>Ϊ����</para>
 
 	    <programlisting>fred:
   set ifaddr 203.14.100.1 203.14.101.1 255.255.255.255
 
 sam:
   set ifaddr 203.14.100.1 203.14.102.1 255.255.255.255
 
 mary:
   set ifaddr 203.14.100.1 203.14.103.1 255.255.255.255</programlisting>
 
 	    <para> �����Ҫ�� <filename>/etc/ppp/ppp.linkup</filename>
 	      ҲӦ�ð���ÿ����̬IP�û��ĵ�·����Ϣ��
 	      ������һ��Ϊ�ͻ����������˵�
 	       <hostid role="ipaddr">203.14.101.0/24</hostid> �����·�ɡ�</para>
 
 	    <programlisting>fred:
   add 203.14.101.0 netmask 255.255.255.0 HISADDR
 
 sam:
   add 203.14.102.0 netmask 255.255.255.0 HISADDR
 
 mary:
   add 203.14.103.0 netmask 255.255.255.0 HISADDR</programlisting>
 	</sect4>
 
 	  <sect4 id="userppp-mgetty">
 	    <title><command>mgetty</command>��AutoPPP</title>
 
 	    <indexterm>
 	      <primary><command>mgetty</command></primary>
 	    </indexterm>
 
 	    <indexterm>
 	      <primary>AutoPPP</primary>
 	    </indexterm>
 
 	    <indexterm>
 	      <primary>LCP</primary>
 	    </indexterm>
 
 	    <para>Ĭ������£� <filename
 	      role="package">comms/mgetty+sendfax</filename> port
 	      �ڱ���ʱ������ <literal>AUTO_PPP</literal> ѡ�
 	      ��ʹ <command>mgetty</command> �ܹ���� PPP ���ӵ� LCP ״̬��
 	      ���Զ����� PPP shell�� ������ ������Ĭ�������е�
 	      login/password ���в������֣� ��ˣ�
 	      �ͱ���ʹ�� PAP �� CHAP �������û����ݡ�</para>
 
 	    <para>��ڼٶ��û��Ѿ���ϵͳ�гɹ��ر��벢��װ�� <filename
 	      role="package">comms/mgetty+sendfax</filename>��</para>
 
 	    <para>ȷ������
 	      <filename>/usr/local/etc/mgetty+sendfax/login.config</filename>
 	      �ļ��а����������ݣ�</para>
 
 	    <programlisting>/AutoPPP/ -     -		      /etc/ppp/ppp-pap-dialup</programlisting>
 
 	    <para>�����<command>mgetty</command>����
 	      <filename>ppp-pap-dialup</filename>�ű�������PPP���ӡ�</para>
 
 	    <para>����<filename>/etc/ppp/ppp-pap-dialup</filename>�ļ�д���������� (���ļ�Ӧ���ǿ�ִ�е�)��</para>
 
 	    <programlisting>#!/bin/sh
 exec /usr/sbin/ppp -direct pap$IDENT</programlisting>
 
 	    <para>��Ӧ��ÿ����<filename>/etc/ttys</filename>�������У� ��Ҫ��<filename>/etc/ppp/ppp.conf</filename>
 	    �д�����Ӧ��� �������Ķ�������ͬ�ġ�</para>
 
 	    <programlisting>pap:
   enable pap
   set ifaddr 203.14.100.1 203.14.100.20-203.14.100.40
   enable proxy</programlisting>
 
 	    <para>ÿ�������ַ�ʽ��¼���û��� ��������
 	      <filename>/etc/ppp/ppp.secret</filename> �ļ��и����û���/���
 	      ����ʹ������ѡ� ��ͨ�� PAP ��ʽ�� <filename>/etc/passwd</filename>
 	      �ļ��ṩ����Ϣ�����������֤��</para>
 
 	    <programlisting>enable passwdauth</programlisting>
 
 	    <para>�������ΪijЩ�û����侲̬IP��
 	      ������ <filename>/etc/ppp/ppp.secret</filename>
 	      �н�IP����Ϊ����������ָ���� ��μ�
 	      <filename>/usr/share/examples/ppp/ppp.secret.sample</filename>
 	      �е����ӡ�</para>
 	  </sect4>
 
 	  <sect4>
 	    <title>MS Extensions</title>
 
 	    <indexterm>
               <primary>DNS</primary>
             </indexterm>
 
 	    <indexterm>
               <primary>NetBIOS</primary>
             </indexterm>
 
 	    <indexterm>
               <primary>PPP</primary><secondary>Microsoft extensions</secondary>
             </indexterm>
 
 	    <para>��������PPP���ṩDNS��NetBIOS������������ַ��</para>
 
 	    <para>Ҫ�� PPP 1.x �汾��������Щ��չ�� ��Ҫ��
 	      <filename>/etc/ppp/ppp.conf</filename> �Ķ�Ӧ���м����������ã�</para>
 
 	    <programlisting>enable msext
 set ns 203.14.100.1 203.14.100.2
 set nbns 203.14.100.5</programlisting>
 
 	    <para>PPP�汾2�����ϣ�</para>
 
 	    <programlisting>accept dns
 set dns 203.14.100.1 203.14.100.2
 set nbns 203.14.100.5</programlisting>
 
 	    <para>�⽫���߿ͻ�����ѡ�����������ͱ���������������</para>
 
 	    <para>�ڰ汾2�����ϰ汾�У� ���ʡ����
 	      <literal>set dns</literal>�� PPP��ʹ��
 	      <filename>/etc/resolv.conf</filename>�е�ֵ��</para>
 	</sect4>
 
         <sect4 id="userppp-PAPnCHAP">
 	  <title>PAP �� CHAP ��֤</title>
 	  <indexterm><primary>PAP</primary></indexterm>
 	  <indexterm><primary>CHAP</primary></indexterm>
 	  <para>һЩ ISP ��ϵͳ����Ϊʹ�� PAP �� CHAP ���������������֤��
 	    ���������������� ��������ʱ ISP �Ͳ��ῴ��
 	    <prompt>login:</prompt> ��ʾ���� ����������ʼ PPP �Ի���</para>
 
 	  <para>PAP ��ȫ��Ҫ�� CHAP ��һЩ�� �������ﰲȫ�Բ��������⣬
 	    ��Ϊ���� (��ʹ�����Ĵ���) ֻ��ͨ�������ߴ��ͣ�
 	    �����߲�û��̫�����ȥ <quote>����</quote> ����</para>
 
 	  <para>�ο� <link linkend="userppp-staticIP">PPP
 	    �뾲̬ IP ��ַ</link> �� <link
 	    linkend="userppp-dynamicIP">PPP �붯̬ IP ��ַ</link>
 	    С�ڣ� ��������иĶ���</para>
 
 	  <programlisting>13      set authname <replaceable>MyUserName</replaceable>
 14      set authkey <replaceable>MyPassword</replaceable>
 15      set login</programlisting>
 
 	  <variablelist>
 	    <varlistentry>
 	      <term>�� 13 ��</term>
 
 	      <listitem>
 		<para>��һ��ָ������PAP/CHAP�û�����
 		  ����ҪΪ<replaceable>MyUserName</replaceable>������ȷ��ֵ��</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>�� 14 ��</term>
 	      <listitem>
 		<indexterm><primary>password</primary></indexterm>
 
 		<para>��һ��ָ������ PAP/CHAP password���롣
 		  ����ҪΪ <replaceable>MyPassword</replaceable> ������ȷ��ֵ��
 		  ���⣬������ϣ������һЩ�����ѡ����磺</para>
 
 		<programlisting>16      accept PAP</programlisting>
 
 		<para>��</para>
 
 		<programlisting>16      accept CHAP</programlisting>
 
 		<para>����ȷ������ͼ�� ������ Ĭ������� PAP �� CHAP ���ᱻ���ܡ�</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>�� 15��</term>
 
 	      <listitem>
 		<para>�����ʹ�õ��� PAP �� CHAP�� һ����˵ ISP
 		  �Ͳ���Ҫ������¼�������ˡ� ��ʱ��
 		  �ͱ������ <quote>set login</quote>
 		  ���á�</para>
 	      </listitem>
 	    </varlistentry>
 	  </variablelist>
 	</sect4>
 
 	<sect4>
 	  <title>��ʱ�ı�����<command>ppp</command> ����</title>
 
 	  <para>���̨���е�<command>ppp</command>������жԻ��ǿ��ܵģ�
 	ǰ����������һ�����ʵ���϶˿ڡ� ������һ�㣬 ��Ҫ��������м��뵽���������У�</para>
 
 	  <programlisting>set server /var/run/ppp-tun<replaceable>%d</replaceable> DiagnosticPassword 0177</programlisting>
 
 	  <para>���и��� PPP��ָ����&unix;��socket�������� ���û�����ʱ��Ҫ����ָ�������롣
 	    <literal>%d</literal>��<devicename>tun</devicename>�豸���滻��</para>
 
 	  <para>һ��������socket�� �Ϳ����ڽű��е��ó���&man.pppctl.8;�������������е�
 	       ��PPP��</para>
 	</sect4>
       </sect3>
 
       <sect3 id="userppp-nat">
        <title>ʹ��PPP�����ַ����</title>
 
        <indexterm>
          <primary>PPP</primary>
          <secondary>NAT</secondary>
        </indexterm>
 
        <para>PPP ����ʹ���ڽ��� NAT�� �������ں�֧�֡�
 	 �������� <filename>/etc/ppp/ppp.conf</filename> ���������������������</para>
 
 	<programlisting>nat enable yes</programlisting>
 
        <para> PPP NATҲ����ʹ��������ѡ��
 	 <literal>-nat</literal>������ ��
          <filename>/etc/rc.conf</filename> �ļ���Ҳ��
          <literal>ppp_nat</literal> � ��Ĭ�����á�</para>
 
        <para>�����ʹ����������ԣ� �����ᷢ����
          <filename>/etc/ppp/ppp.conf</filename>������
          ѡ���������incoming connections forwarding�����õģ�</para>
 
 	<programlisting>nat port tcp 10.0.0.2:ftp ftp
 nat port tcp 10.0.0.2:http http</programlisting>
 
        <para>������ȫ����������������</para>
 
 	<programlisting>nat deny_incoming yes</programlisting>
       </sect3>
 
       <sect3 id="userppp-final">
 	<title>����ϵͳ����</title>
 
 	<indexterm>
           <primary>PPP</primary><secondary>configuration</secondary>
         </indexterm>
 
 	<para>��������������<command>ppp</command>�� ������������֮ǰ����һЩ����Ҫ����
 	  ���޸� <filename>/etc/rc.conf</filename>��</para>
 
 	<para>�����������¿��� ȷ���Ѿ���ȷ��������
 	  <literal>hostname=</literal>�� ���磺</para>
 
 	<programlisting>hostname="foo.example.com"</programlisting>
 
 	<para>�������ISP�ṩ����һ����̬��IP�����֣� �����������Ϊhostname������ʵġ�</para>
 
 	<para>Ѱ�� <literal>network_interfaces</literal> ������
 	  ���Ҫ����ϵͳͨ����������ISP��
 	  һ��Ҫ��<devicename>tun0</devicename>�豸��������б��� �����ɾ������</para>
 
 	<programlisting>network_interfaces="lo0 tun0"
 ifconfig_tun0=</programlisting>
 
 	<note>
 	  <para> <literal>ifconfig_tun0</literal>����Ӧ���ǿյģ� ��Ҫ����һ����Ϊ
 	    <filename>/etc/start_if.tun0</filename>���ļ���
 	  ����ļ�Ӧ�ð�����һ�У�</para>
 
 	  <programlisting>ppp -auto mysystem</programlisting>
 
 	  <para>�˽ű�����������ʱ��ִ�У� ����PPP�ػ����̽����Զ�ģʽ��
 	    �����̨���ӳ䵱һ��LAN�����أ� ������ϣ��ʹ��
 	    <option>-alias</option>�� �ο���������ֲ��˽����ϸ�ڡ�</para>
 	</note>
 
 	<para>�����
 	  <filename>/etc/rc.conf</filename> �У�
           ��·�ɳ�������Ϊ <literal>NO</literal>��</para>
 
 	<programlisting>router_enable="NO"</programlisting>
 
 	<indexterm>
           <primary><application>routed</application></primary>
         </indexterm>
 
 	<para>������ <command>routed</command> �������dz���Ҫ�� ��Ϊ
 	  <command>routed</command> �ܻ�ɾ���� <command>ppp</command>
 	  ��������Ĭ��·�ɡ�</para>
 
 	<para>���⣬ ���ǽ�����ȷ��һ��
 	  <literal>sendmail_flags</literal> ��һ����û��ָ��
 	  <option>-q</option> ������ ����
 	  <command>sendmail</command> ���᲻�ϵس��Բ������磬
 	  �����������ᵼ�»������ϵؽ��в��š� ���Կ��ǣ�</para>
 
 	<programlisting>sendmail_flags="-bd"</programlisting>
 
 	<indexterm>
     <primary><application>sendmail</application></primary>
   </indexterm>
 	<para>����������ǵ�ÿ�� PPP ���ӽ���ʱ������ͨ��������������ǿ��
 	  <command>sendmail</command> ���¼���ʼ����У�</para>
 
 	<screen>&prompt.root; <userinput>/usr/sbin/sendmail -q</userinput></screen>
 
 	<para>��Ҳ������<filename>ppp.linkup</filename>ʹ��<command>!bg</command>�����Զ������Щ������</para>
 
 	<programlisting>1     provider:
 2       delete ALL
 3       add 0 0 HISADDR
 4       !bg sendmail -bd -q30m</programlisting>
 
         <indexterm>
           <primary>SMTP</primary>
         </indexterm>
 
 	<para>�������ϲ���������� ��������һ��
 	  <quote>dfilter</quote> ����ֹ SMTP ���䡣
 	  �ο�����ļ��˽����ϸ�ڡ�</para>
 
 	<para>������ΨһҪ�����������������������
 	  ����֮�󣬿������룺</para>
 
 	<screen>&prompt.root; <userinput>ppp</userinput></screen>
 
 	<para>Ȼ����<command>dial provider</command>�Կ��� PPP�Ự��
 	   �������������<command>ppp</command>�Զ������Ự��
 	   ��Ϊ����һ������������ (��û�д��� <filename>start_if.tun0</filename>
 	   �ű�)�� ���룺</para>
 
 	<screen>&prompt.root; <userinput>ppp -auto provider</userinput></screen>
       </sect3>
 
       <sect3>
 	<title>�ܽ�</title>
 
 	<para>����һ������PPPʱ�� ���漸���DZ���ģ�</para>
 
 	<para>�ͻ��ˣ�</para>
 
 	<procedure>
 	  <step>
 	    <para>ȷ�� <devicename>tun</devicename>������˽��ˡ�</para>
 	  </step>
 
 	  <step>
 	    <para>ȷ�� <filename class="directory">/dev</filename>
 	      Ŀ¼����Ϊ
 	      <filename class="devicefile">tun<replaceable>N</replaceable></filename>
 	      ���豸�ļ��ǿ��õġ�</para>
 	  </step>
 
 	  <step>
 	    <para>��
 	      <filename>/etc/ppp/ppp.conf</filename>�д���һ���
 	      <filename>pmdemand</filename>ʾ��Ӧ���ʺ��ھ������ISP��</para>
 	  </step>
 
 	  <step>
 	    <para>�����ʹ�ö�̬IP��ַ�� ��<filename>/etc/ppp/ppp.linkup</filename>����һ���</para>
 	  </step>
 
 	  <step>
 	    <para>����<filename>/etc/rc.conf</filename>
 	      �ļ���</para>
 	  </step>
 
 	  <step>
 	    <para>�����Ҫ���貦�ţ� ����һ��<filename>start_if.tun0</filename>�ű���</para>
 	  </step>
 	</procedure>
 
 	<para>�������ˣ�</para>
 
 	<procedure>
 	  <step>
 	    <para>ȷ��<devicename>tun</devicename>�豸�ѱ������ںˡ�</para>
 	  </step>
 
 	  <step>
 	    <para>ȷ�� <filename class="directory">/dev</filename>
 	      Ŀ¼����Ϊ
 	      <filename class="devicefile">tun<replaceable>N</replaceable></filename>
 	      ���豸�ļ��ǿ��õġ�</para>
 	  </step>
 
 	  <step>
 	    <para>��<filename>/etc/passwd</filename>�д���һ����
 	      (ʹ��&man.vipw.8;����)��</para>
 	  </step>
 
 	  <step>
 	    <para>���û���homeĿ¼����һ������
 	      <command>ppp -direct direct-server</command>�����������profile��</para>
 	  </step>
 
 	  <step>
 	    <para>��<filename>/etc/ppp/ppp.conf</filename>�д���һ���
 	      <filename>direct-server</filename>ʾ��Ӧ��������Ҫ��</para>
 	  </step>
 
 	  <step>
 	    <para>��
 	      <filename>/etc/ppp/ppp.linkup</filename>�д���һ���</para>
 	  </step>
 
 	  <step>
 	    <para>���� <filename>/etc/rc.conf</filename>
 	     �ļ���</para>
 	  </step>
 	</procedure>
       </sect3>
     </sect2>
   </sect1>
 
   <sect1 id="ppp">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Gennady B.</firstname>
           <surname>Sorokopud</surname>
           <contrib>Parts originally contributed by </contrib>
         </author>
         <author>
           <firstname>Robert</firstname>
           <surname>Huff</surname>
         </author>
       </authorgroup>
     </sect1info>
 
     <title>ʹ���ں˼�PPP</title>
 
     <warning>
       <para>�������ֻ��
 	&os;&nbsp;7.X �Ͽ��á�</para>
     </warning>
 
     <sect2>
       <title>�����ں˼�PPP</title>
 
       <indexterm>
         <primary>PPP</primary>
         <secondary>kernel PPP</secondary>
       </indexterm>
 
       <para>�ڿ�ʼ���� PPP ֮ǰ��
 	��ȷ�� <command>pppd</command> �Ѿ������
 	<filename class="directory">/usr/sbin</filename> �� ����
 	<filename class="directory">/etc/ppp</filename> Ŀ¼�Ǵ��ڵġ�</para>
 
       <para><command>pppd</command>��������ģʽ�¹�����</para>
 
       <orderedlist>
 	<listitem>
 	  <para>��Ϊһ�� <quote>�ͻ�</quote> &mdash;
 	    ��Ҫͨ��PPP�����߻�modem�߰����Ļ������ӵ��������ϡ�</para>
 	</listitem>
 
 	<listitem>
 	  <indexterm>
 	    <primary>PPP</primary>
 	    <secondary>server</secondary>
 	  </indexterm>
 
 	  <para>��Ϊ<quote>������</quote> &mdash;������Ѿ�λ�������ϣ� �ұ�����ͨ��PPP��������������ӡ�</para>
 	</listitem>
       </orderedlist>
 
       <para>�������������Ҫ����һ��ѡ���ļ���
         (<filename>/etc/ppp/options</filename> ������
 	<filename>~/.ppprc</filename> ������ļ�����ж���û�ʹ��PPP)��</para>
 
       <para>������ҪһЩmodem/serial����(<filename role="package">comms/kermit</filename>�ͺ��ʺ�)��
       ʹ���ܹ����Ų���Զ�������������ӡ�</para>
     </sect2>
 
     <sect2>
       <sect2info>
 	<authorgroup>
 	  <author>
 	    <firstname>Trev</firstname>
 	    <surname>Roydhouse</surname>
 	    <contrib>Based on information provided by </contrib>
 	    <!-- Trev.Roydhouse@f401.n711.z3.fidonet.org -->
 	  </author>
 	</authorgroup>
       </sect2info>
 
       <title>ʹ��<command>pppd</command>��Ϊ�ͻ���</title>
 
       <indexterm>
         <primary>PPP</primary>
         <secondary>client</secondary>
       </indexterm>
 
       <indexterm>
         <primary>Cisco</primary>
       </indexterm>
 
       <para>������� <filename>/etc/ppp/options</filename>ѡ���ļ��ܹ���������CISCO�ն˷�������
       PPP�����ӡ�</para>
 
       <programlisting>crtscts         # enable hardware flow control
 modem           # modem control line
 noipdefault     # remote PPP server must supply your IP address
                 # if the remote host does not send your IP during IPCP
                 # negotiation, remove this option
 passive         # wait for LCP packets
 domain ppp.foo.com      # put your domain name here
 
 :<replaceable>remote_ip</replaceable>    # put the IP of remote PPP host here
                 # it will be used to route packets via PPP link
                 # if you didn't specified the noipdefault option
                 # change this line to <replaceable>local_ip</replaceable>:<replaceable>remote_ip</replaceable>
 
 defaultroute    # put this if you want that PPP server will be your
                 # default router</programlisting>
 
       <para>���ӣ�</para>
 
       <indexterm><primary>Kermit</primary></indexterm>
       <indexterm><primary>modem</primary></indexterm>
       <procedure>
 	<step>
 	  <para>ʹ�� <application>Kermit</application> (������ modem
 	    ����������)�� Ȼ�����������û����Ϳ���
 	    (����Զ������������ PPP �����������Ϣ)��</para>
 	</step>
 
 	<step>
 	  <para>�˳� <application>Kermit</application> (�����Ҷ�����)��</para>
 	</step>
 
 	<step>
 	  <para>������������</para>
 
 	  <screen>&prompt.root; <userinput>/usr/sbin/pppd <replaceable>/dev/tty01</replaceable> <replaceable>19200</replaceable></userinput></screen>
 
 	  <para>һ��Ҫʹ����ȷ���ٶȺ��豸����</para>
 	</step>
       </procedure>
 
       <para>�������ļ�����Ѿ���PPP���ӡ� �������ʧ�ܣ�
 	�������ļ� <filename>/etc/ppp/options</filename> ������
 	<option>debug</option> ѡ� ���鿴����̨��Ϣ�Ը������⡣</para>
 
       <para>�������<filename>/etc/ppp/pppup</filename>�ű����Զ�������������裺</para>
 
       <programlisting>#!/bin/sh
 pgrep -l pppd
 pid=`pgrep pppd`
 if [ "X${pid}" != "X" ] ; then
         echo 'killing pppd, PID=' ${pid}
         kill ${pid}
 fi
 pgrep -l kermit
 pid=`pgrep kermit`
 if [ "X${pid}" != "X" ] ; then
         echo 'killing kermit, PID=' ${pid}
         kill -9 ${pid}
 fi
 
 ifconfig ppp0 down
 ifconfig ppp0 delete
 
 kermit -y /etc/ppp/kermit.dial
 pppd /dev/tty01 19200</programlisting>
 
       <indexterm>
         <primary>Kermit</primary>
       </indexterm>
 
       <para><filename>/etc/ppp/kermit.dial</filename> ��һ�� <application>Kermit</application>
       �ű��� ������ɲ��ţ� ����Զ�����������������Ҫ��������֤����
       (����ĵ��������һ���ű�ʵ��)��</para>
 
       <para>ʹ����������ű�<filename>/etc/ppp/pppdown</filename>�Ͽ�PPP���ߣ�</para>
 
       <programlisting>#!/bin/sh
 pid=`pgrep pppd`
 if [ X${pid} != "X" ] ; then
         echo 'killing pppd, PID=' ${pid}
         kill -TERM ${pid}
 fi
 
 pgrep -l kermit
 pid=`pgrep kermit`
 if [ "X${pid}" != "X" ] ; then
         echo 'killing kermit, PID=' ${pid}
         kill -9 ${pid}
 fi
 
 /sbin/ifconfig ppp0 down
 /sbin/ifconfig ppp0 delete
 kermit -y /etc/ppp/kermit.hup
 /etc/ppp/ppptest</programlisting>
 
       <para>ͨ��ִ��<filename>/usr/etc/ppp/ppptest</filename>��
         ����<command>pppd</command> �Ƿ��������У�</para>
 
       <programlisting>#!/bin/sh
 pid=`pgrep pppd`
 if [ X${pid} != "X" ] ; then
         echo 'pppd running: PID=' ${pid-NONE}
 else
         echo 'No pppd running.'
 fi
 set -x
 netstat -n -I ppp0
 ifconfig ppp0</programlisting>
 
       <para>ִ�нű�
 	<filename>/etc/ppp/kermit.hup</filename>�Թ���moderm�� ����ļ�������</para>
 
       <programlisting>set line /dev/tty01	; put your modem device here
 set speed 19200
 set file type binary
 set file names literal
 set win 8
 set rec pack 1024
 set send pack 1024
 set block 3
 set term bytesize 8
 set command bytesize 8
 set flow none
 
 pau 1
 out +++
 inp 5 OK
 out ATH0\13
 echo \13
 exit</programlisting>
 
       <para>Ҳ������<command>chat</command>
 	����<command>kermit</command>��</para>
 
       <para>���������ļ����Խ���<command>pppd</command>���ӡ�</para>
 
       <para><filename>/etc/ppp/options</filename>��</para>
 
       <programlisting>/dev/cuad1 115200
 
 crtscts		# enable hardware flow control
 modem		# modem control line
 connect "/usr/bin/chat -f /etc/ppp/login.chat.script"
 noipdefault	# remote PPP serve must supply your IP address
 	        # if the remote host doesn't send your IP during
                 # IPCP negotiation, remove this option
 passive         # wait for LCP packets
 domain <replaceable>your.domain</replaceable>	# put your domain name here
 
 :		# put the IP of remote PPP host here
 	        # it will be used to route packets via PPP link
                 # if you didn't specified the noipdefault option
                 # change this line to <replaceable>local_ip</replaceable>:<replaceable>remote_ip</replaceable>
 
 defaultroute	# put this if you want that PPP server will be
 	        # your default router</programlisting>
 
       <para><filename>/etc/ppp/login.chat.script</filename>��</para>
 
       <note>
 	<para>���µ�����Ӧ�÷���һ���ڡ�</para>
       </note>
 
       <programlisting>ABORT BUSY ABORT 'NO CARRIER' "" AT OK ATDT<replaceable>phone.number</replaceable>
   CONNECT "" TIMEOUT 10 ogin:-\\r-ogin: <replaceable>login-id</replaceable>
   TIMEOUT 5 sword: <replaceable>password</replaceable></programlisting>
 
       <para>һ����Щ����װ���޸���ȷ�� ����Ҫ���ľ�������<command>pppd</command>�� ����������</para>
 
       <screen>&prompt.root; <userinput>pppd</userinput></screen>
     </sect2>
 
     <sect2>
       <title>ʹ��<command>pppd</command>��Ϊ������</title>
 
       <para><filename>/etc/ppp/options</filename>Ҫ����������Щ���ݣ�</para>
 
       <programlisting>crtscts                         # Hardware flow control
 netmask 255.255.255.0           # netmask (not required)
 192.114.208.20:192.114.208.165  # IP's of local and remote hosts
                                 # local ip must be different from one
                                 # you assigned to the Ethernet (or other)
                                 # interface on your machine.
                                 # remote IP is IP address that will be
                                 # assigned to the remote machine
 domain ppp.foo.com              # your domain
 passive                         # wait for LCP
 modem                           # modem line</programlisting>
 
       <para>��������ű�<filename>/etc/ppp/pppserv</filename>
      ʹ<application>pppd</application>�Է�������ʽ������</para>
 
       <programlisting>#!/bin/sh
 pgrep -l pppd
 pid=`pgrep pppd`
 if [ "X${pid}" != "X" ] ; then
         echo 'killing pppd, PID=' ${pid}
         kill ${pid}
 fi
 pgrep -l kermit
 pid=`pgrep kermit`
 if [ "X${pid}" != "X" ] ; then
         echo 'killing kermit, PID=' ${pid}
         kill -9 ${pid}
 fi
 
 # reset ppp interface
 ifconfig ppp0 down
 ifconfig ppp0 delete
 
 # enable autoanswer mode
 kermit -y /etc/ppp/kermit.ans
 
 # run ppp
 pppd /dev/tty01 19200</programlisting>
 
       <para>ʹ�ýű�<filename>/etc/ppp/pppservdown</filename>ֹͣ��������</para>
 
       <programlisting>#!/bin/sh
 pgrep -l pppd
 pid=`pgrep pppd`
 if [ "X${pid}" != "X" ] ; then
         echo 'killing pppd, PID=' ${pid}
         kill ${pid}
 fi
 pgrep -l kermit
 pid=`pgrep kermit`
 if [ "X${pid}" != "X" ] ; then
         echo 'killing kermit, PID=' ${pid}
         kill -9 ${pid}
 fi
 ifconfig ppp0 down
 ifconfig ppp0 delete
 
 kermit -y /etc/ppp/kermit.noans</programlisting>
 
       <para>����� <application>Kermit</application> �ű�
 	(<filename>/etc/ppp/kermit.ans</filename>) �ܹ�����/������ modem
 	���Զ�Ӧ��ģʽ�� ��������������������</para>
 
       <programlisting>set line /dev/tty01
 set speed 19200
 set file type binary
 set file names literal
 set win 8
 set rec pack 1024
 set send pack 1024
 set block 3
 set term bytesize 8
 set command bytesize 8
 set flow none
 
 pau 1
 out +++
 inp 5 OK
 out ATH0\13
 inp 5 OK
 echo \13
 out ATS0=1\13   ; change this to out ATS0=0\13 if you want to disable
                 ; autoanswer mode
 inp 5 OK
 echo \13
 exit</programlisting>
 
       <para>һ����Ϊ<filename>/etc/ppp/kermit.dial</filename>�Ľű�������Զ������
       ���в��ź���֤�� ��Ҫ������Ҫ�������� Ҫ�������ĵ�Ѱ�������룬
       ����Ҫ���� modem ��Զ�������ķ�Ӧ�޸�������䡣</para>
 
       <programlisting>;
 ; put the com line attached to the modem here:
 ;
 set line /dev/tty01
 ;
 ; put the modem speed here:
 ;
 set speed 19200
 set file type binary            ; full 8 bit file xfer
 set file names literal
 set win 8
 set rec pack 1024
 set send pack 1024
 set block 3
 set term bytesize 8
 set command bytesize 8
 set flow none
 set modem hayes
 set dial hangup off
 set carrier auto                ; Then SET CARRIER if necessary,
 set dial display on             ; Then SET DIAL if necessary,
 set input echo on
 set input timeout proceed
 set input case ignore
 def \%x 0                       ; login prompt counter
 goto slhup
 
 :slcmd                          ; put the modem in command mode
 echo Put the modem in command mode.
 clear                           ; Clear unread characters from input buffer
 pause 1
 output +++                      ; hayes escape sequence
 input 1 OK\13\10                ; wait for OK
 if success goto slhup
 output \13
 pause 1
 output at\13
 input 1 OK\13\10
 if fail goto slcmd              ; if modem doesn't answer OK, try again
 
 :slhup                          ; hang up the phone
 clear                           ; Clear unread characters from input buffer
 pause 1
 echo Hanging up the phone.
 output ath0\13                  ; hayes command for on hook
 input 2 OK\13\10
 if fail goto slcmd              ; if no OK answer, put modem in command mode
 
 :sldial                         ; dial the number
 pause 1
 echo Dialing.
 output atdt9,550311\13\10               ; put phone number here
 assign \%x 0                    ; zero the time counter
 
 :look
 clear                           ; Clear unread characters from input buffer
 increment \%x                   ; Count the seconds
 input 1 {CONNECT }
 if success goto sllogin
 reinput 1 {NO CARRIER\13\10}
 if success goto sldial
 reinput 1 {NO DIALTONE\13\10}
 if success goto slnodial
 reinput 1 {\255}
 if success goto slhup
 reinput 1 {\127}
 if success goto slhup
 if &lt; \%x 60 goto look
 else goto slhup
 
 :sllogin                        ; login
 assign \%x 0                    ; zero the time counter
 pause 1
 echo Looking for login prompt.
 
 :slloop
 increment \%x                   ; Count the seconds
 clear                           ; Clear unread characters from input buffer
 output \13
 ;
 ; put your expected login prompt here:
 ;
 input 1 {Username: }
 if success goto sluid
 reinput 1 {\255}
 if success goto slhup
 reinput 1 {\127}
 if success goto slhup
 if &lt; \%x 10 goto slloop         ; try 10 times to get a login prompt
 else goto slhup                 ; hang up and start again if 10 failures
 
 :sluid
 ;
 ; put your userid here:
 ;
 output ppp-login\13
 input 1 {Password: }
 ;
 ; put your password here:
 ;
 output ppp-password\13
 input 1 {Entering SLIP mode.}
 echo
 quit
 
 :slnodial
 echo \7No dialtone.  Check the telephone line!\7
 exit 1
 
 ; local variables:
 ; mode: csh
 ; comment-start: "; "
 ; comment-start-skip: "; "
 ; end:</programlisting>
     </sect2>
   </sect1>
 
   <sect1 id="ppp-troubleshoot">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Tom</firstname>
 	  <surname>Rhodes</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
       <!-- 13 June 2003 -->
     </sect1info>
     <title><acronym>PPP</acronym> ���ӹ����ų�</title>
 
     <indexterm>
       <primary>PPP</primary>
       <secondary>troubleshooting</secondary>
     </indexterm>
 
     <warning>
       <para>�� &os; 8.0 ��ʼ�� &man.uart.4; ����ȡ����
 	&man.sio.4; ������ ���Ա�ʾ���ڵ��豸�ڵ��ɷֱ�
 	<filename>/dev/cuad<replaceable>N</replaceable></filename> ����
 	<filename>/dev/cuau<replaceable>N</replaceable></filename>��
 	����
 	<filename>/dev/ttyd<replaceable>N</replaceable></filename> ����
 	<filename>/dev/ttyu<replaceable>N</replaceable></filename>��
 	&os;&nbsp;7.X �û�������ʱ��Ҫ��Ӧ֮�������ļ����б�Ҫ�ĸ��ġ�</para>
     </warning>
 
       <para>���ڽ�����ͨ��modem����ʹ��PPPʱ���ܳ��ֵ����⡣
 	���磬 ��������Ҫȷ�е�֪���������ϵͳ�����һ����������������ʾ����
 	��Щ <acronym>ISP</acronym> ���ṩ <literal>ssword</literal>��ʾ����
 	�������Ŀ��ܻ���� <literal>password</literal>��
 	���û�и�������IJ�ͬ��Ӧ�ر�д <command>ppp</command>
 	�ű��� ��¼�ͻ�ʧ�ܡ� ��� <command>ppp</command>
 	��õķ������ֶ��������ӡ� ���µ���Ϣ��һ��һ���ش�������ֶ����ӡ�</para>
 
     <sect2>
       <title>����豸�ڵ�</title>
 
 	<para>���ʹ�õ��Ƕ����ںˣ� ȷ��������������а����������ã�</para>
 
 	<programlisting>device   uart</programlisting>
 
 	<para>Ĭ�ϵ� <literal>GENERIC</literal> �ں��а�����
 	  <devicename>uart</devicename> �豸�� ��������ʹ�õ������Ļ���
 	  �Ͳ���Ҫ�����ˡ� ֻҪ�鿴 <command>dmesg</command> ������Ƿ��� modem
 	  �豸��</para>
 
 	<screen>&prompt.root; <userinput>dmesg | grep uart</userinput></screen>
 
 	<para>��Ӧ���ҵ��� <devicename>uart</devicename> �豸�йص������
 	  ��Щ����������Ҫ�� COM �˿ڡ� ������� modem ���ձ�׼���ж˿ڹ�����
 	  ���ͻ��� <devicename>uart1</devicename> �� <devicename>COM2</devicename>
 	  ���ҵ����� ��� modem �豸������ <devicename>uart1</devicename>
 	  �ӿ� (�� DOS �г�Ϊ<devicename>COM2</devicename>)��
 	  ���� modem ������ <filename class="devicefile">/dev/cuau1</filename>��</para>
     </sect2>
 
     <sect2>
       <title>�ֶ�����</title>
 
       <para>ͨ���ֶ�����<command>ppp</command>������Internet
       ��������Ӽ���֪<acronym>ISP</acronym>����<application>PPP</application>�ͻ��˷�ʽ��һ�����٣� �򵥵ķ�����
 	�����Ǵ�<application>PPP</application> �����п�ʼ�� �����е�����������ʹ��
 	<emphasis>example</emphasis> ��ʾ���� <application>PPP</application>
 	������������� ����<command>ppp</command>
 	����� <command>ppp</command>��</para>
 
       <screen>&prompt.root; <userinput>ppp</userinput></screen>
 
       <para>���������Ѿ�����<command>ppp</command>��</para>
 
       <screen>ppp ON example&gt; <userinput>set device <filename class="devicefile">/dev/cuau1</filename></userinput></screen>
 
       <para>����modem�豸�� �ڱ���������
 	<devicename>cuau1</devicename>��</para>
 
       <screen>ppp ON example&gt; <userinput>set speed 115200</userinput></screen>
 
       <para>���������ٶȣ� �ڱ���������ʹ��15,200 <acronym>kbps</acronym>��</para>
 
       <screen>ppp ON example&gt; <userinput>enable dns</userinput></screen>
 
       <para>ʹ<command>ppp</command>������������
 	���ļ�<filename>/etc/resolv.conf</filename>�����������������С�
 	��� <command>ppp</command>����ȷ�����ǵ��������� �������Ժ����á�</para>
 
       <screen>ppp ON example&gt; <userinput>term</userinput></screen>
 
       <para>�л��� <quote>�ն�</quote>�����Ǿ����ֶ��ؿ�����̨ modem ��ģʽ��</para>
 
       <programlisting>deflink: Entering terminal mode on <filename class="devicefile">/dev/cuau1</filename>
 type '~h' for help</programlisting>
 
       <screen><userinput>at</userinput>
 OK
 <userinput>atdt<replaceable>123456789</replaceable></userinput></screen>
 
       <para>ʹ������<command>at</command>��ʼ��modem��
 	Ȼ��ʹ��<command>atdt</command>��<acronym>ISP</acronym>�����ĺ�����в��š�</para>
 
       <screen>CONNECT</screen>
 
       <para>�������ã� ���������������Ӳ���޹ص��������⣬ ���������ﳢ�Խ����</para>
 
       <screen>ISP Login:<userinput>myusername</userinput></screen>
 
       <para>������ʾ�������û����� ����<acronym>ISP</acronym>�ṩ���û���Ȼ�󰴻س���</para>
 
       <screen>ISP Pass:<userinput>mypassword</userinput></screen>
 
       <para>��ʱ��ʾ�����������룬 ����
 	<acronym>ISP</acronym>�ṩ�����롣
 	��ͬ��¼��&os;�� ���벻����ʾ��</para>
 
       <screen>Shell or PPP:<userinput>ppp</userinput></screen>
 
       <para>����<acronym>ISP</acronym>�IJ�ͬ�� �����ʾ�����ܲ�����֡�
 	����������Ҫ���ǣ� ��ʹ���������ṩ�̶˵� Shell��
 	�������� <command>ppp</command>�� �Ȿ���У�
 	����ѡ��ʹ�� <command>ppp</command>�� ��Ϊ����ϣ���õ� Internet ���ӡ�</para>
 
       <screen>Ppp ON example&gt;</screen>
 
       <para>ע������������У� ��һ�� <option>p</option>�Ѿ���д��
 	���ʾ�����Ѿ��ɹ����������� <acronym>ISP</acronym>��</para>
 
       <screen>PPp ON example&gt;</screen>
 
       <para>�����Ѿ��ɹ�ͨ����
 	<acronym>ISP</acronym>����֤�� ���ڵȴ�����<acronym>IP</acronym>��ַ��</para>
 
       <screen>PPP ON example&gt;</screen>
 
       <para>���ǵõ���һ�� <acronym>IP</acronym>
 	��ַ�� �ɹ�����������ӡ�</para>
 
       <screen>PPP ON example&gt;<userinput>add default HISADDR</userinput></screen>
 
       <para>���������������Ĭ��·����������á� ���������ͨ��������ġ�
 	��Ϊ֮ǰ����ֻ����������˽��������ӡ� ��������Ѵ��ڵ�·�ɶ����²���ʧ�ܣ�
 	�������� <option>add</option> ǰ�� <literal>!</literal>�š�
 	����֮�⣬ ��Ҳ��������������֮ǰ������Щ (ָ add default HISADDR)��
 	ppp ����������趨Э��ȡ���µ�·�ɡ�</para>
 
       <para>���һ��˳���� ��������Ӧ���ܵõ�һ����� Internet ���ӣ�
 	����ʹ�� <keycombo
 	action="simul"><keycap>CTRL</keycap>
 	<keycap>z</keycap></keycombo> ʹ��ת���̨�� ���������
 	<command>PPP</command>���±�Ϊ <command>ppp</command>��
 	���ʾ���ӱ��Ͽ��� ��д�� P ���������˵� <acronym>ISP</acronym> �����ӣ�
 	��Сд�� p ���ʾ��������ij��ԭ�򱻶Ͽ��� �������ڰ��������˽����ӵ�״̬��
 	<command>ppp</command> ֻ��������״̬��</para>
 
       <sect3>
 	<title>����Ŵ�</title>
 
 	<para>�������һ��ֱ�������ƺ����ܽ������ӣ� Ҫʹ��<option>set
 	  ctsrts off</option>�Թر��ֽ�����<acronym>CTS/RTS</acronym>��
 	  �������һ�㷢�������Ӽ��� <application>PPP</application> ���ն˷�����ʱ��
 	  ������ͨ������д������ʱ�� <application>PPP</application>�ͻ����
 	  һֱ�ȴ�һ��<acronym>CTS</acronym>��
 	  ����һ�������ܳ��ֵ� Clear to Send �źš� ���ʹ�������ѡ� ����Ӧʹ��
 	  <option>set accmap</option>ѡ�
 	  ijЩ����ȱ�ݵ�Ӳ������ɶ˶Զ˷����ض��ַ��� �ر���
 	  XON/XOFF ʱ���ܻ��������ѡ� ��μ� &man.ppp.8;
 	  �����ֲ����˽���ڿ���ѡ��ĸ���ϸ�ڣ� �Լ����ʹ�����ǡ�</para>
 
 	<para>������� modem �ȽϾɣ� ����Ҫʹ��
 	  <option>set parity even</option> �ˡ� ��żУ���Ĭ�������� none��
 	  ���ھ�ʽ�� (��������������ʱ) ���ƽ������ijЩ
 	  <acronym>ISP</acronym> ������������ ����Ҫʹ�����ѡ�����ʹ��
 	  Compuserve <acronym>ISP</acronym>��</para>
 
 	<para><application>PPP</application> ���ܲ�����������ģʽ��
 	  ��ͨ���� <acronym>ISP</acronym> �ȴ�����һ�˷���Э��ʱ�����˴���
 	  ��ʱ�� ʹ�� <command>~p</command> ���ǿ�� ppp ��ʼ����������Ϣ��</para>
 
 	<para>�����û�п�����¼��ʾ�� ��ܿ�����Ҫʹ��
 	  <acronym>PAP</acronym> ��
 	  <acronym>CHAP</acronym> ��֤������ǰ�������е�
 	  &unix; �����֤�� Ҫʹ��
 	  <acronym>PAP</acronym> �� <acronym>CHAP</acronym>
 	  ֻ���ڽ����ն�ģʽ֮ǰ�������ѡ�����
 	  <application>PPP</application>��</para>
 
 	<screen>ppp ON example&gt; <userinput>set authname <replaceable>myusername</replaceable></userinput></screen>
 
 	<para>�˴� <replaceable>myusername</replaceable> Ӧ��Ϊ����
 	  <acronym>ISP</acronym> ����������û�����</para>
 
 	<screen>ppp ON example&gt; <userinput>set authkey <replaceable>mypassword</replaceable></userinput></screen>
 
 	<para>�˴� <replaceable>mypassword</replaceable> Ӧ��Ϊ����
 	  <acronym>ISP</acronym> ��������Ŀ��</para>
 
 	<para>������������� ���޷����������� �볢��
 	  &man.ping.8; ij�� <acronym>IP</acronym>
 	  ��ַ�������Ƿ񷵻�����Ϣ�� ��������ְٷ�֮�� (100%) ������
 	  ��ô���ܿ���û�з���Ĭ��·�ɡ� ����ϸ���ѡ��
 	  <option>add default HISADDR</option>
 	  �Ƿ�������ʱ�������ˡ� ����������ӵ�Զ�̵�
 	  <acronym>IP</acronym> ��ַ���п������������������ĵ�ַû�б����뵽
 	  <filename>/etc/resolv.conf</filename>�� ����ļ�Ӧ������������ӣ�</para>
 
 	<programlisting>domain <replaceable>example.com</replaceable>
 nameserver <replaceable>x.x.x.x</replaceable>
 nameserver <replaceable>y.y.y.y</replaceable></programlisting>
 
 	<para>�˴� <replaceable>x.x.x.x</replaceable> ��
 	  <replaceable>y.y.y.y</replaceable> Ӧ�ø�Ϊ����
 	  <acronym>ISP</acronym> �� DNS ��������
 	  <acronym>IP</acronym> ��ַ��
 	  ��һ��Ϣ����ע��ʱ���ܻ��ṩ������
 	  ����ͨ��ֻ��� <acronym>ISP</acronym> ����绰����֪���ˡ�</para>
 
 	<para>���������� &man.syslog.3; ���� <application>PPP</application>
 	  �����ṩ��־�� ֻ�����ӣ�</para>
 
 	<programlisting>!ppp
 *.*     /var/log/ppp.log</programlisting>
 
 	<para>�� <filename>/etc/syslog.conf</filename> �С� �����������£�
 	  �������Ĭ���Ѿ����ˡ�</para>
 
       </sect3>
     </sect2>
   </sect1>
 
 
 
 
   <sect1 id="pppoe">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Jim</firstname>
           <surname>Mock</surname>
           <contrib>Contributed (from http://node.to/freebsd/how-tos/how-to-freebsd-pppoe.html) by </contrib>
 	</author>
       </authorgroup>
       <!-- 10 Jan 2000 -->
     </sect1info>
 
     <title>ʹ�û�����̫����PPP(PPPoE)</title>
 
     <indexterm>
       <primary>PPP</primary>
       <secondary>over Ethernet</secondary>
     </indexterm>
 
     <indexterm>
       <primary>PPPoE</primary>
       <see>PPP, over Ethernet (��̫���ϵ� PPP)</see>
     </indexterm>
 
     <para>���ڽ�������ν���������̫����PPP
       (<acronym>PPPoE</acronym>)��</para>
 
     <sect2>
       <title>�����ں�</title>
 
       <para>����PPPOE�� ��û�б�����ں����á� �������� netgraph
 	֧��û�б������ںˣ� �������� <application>ppp</application> ��̬���ء�</para>
     </sect2>
 
     <sect2>
       <title>����<filename>ppp.conf</filename></title>
 
       <para>������һ��<filename>ppp.conf</filename>�����ӣ�</para>
 
       <programlisting>default:
   set log Phase tun command # you can add more detailed logging if you wish
   set ifaddr 10.0.0.1/0 10.0.0.2/0
 
 name_of_service_provider:
   set device PPPoE:<replaceable>xl1</replaceable> # replace xl1 with your Ethernet device
   set authname YOURLOGINNAME
   set authkey YOURPASSWORD
   set dial
   set login
   add default HISADDR</programlisting>
 
     </sect2>
 
     <sect2>
       <title>����<application>ppp</application></title>
 
       <para>�� <username>root</username> ����ִ�У�</para>
 
       <screen>&prompt.root; <userinput>ppp -ddial name_of_service_provider</userinput></screen>
 
     </sect2>
 
     <sect2>
       <title>����ʱ����<application>ppp</application></title>
 
       <para>�� <filename>/etc/rc.conf</filename> �м����������ݣ�</para>
 
       <programlisting>ppp_enable="YES"
 ppp_mode="ddial"
 ppp_nat="YES"	# if you want to enable nat for your local network, otherwise NO
 ppp_profile="name_of_service_provider"</programlisting>
     </sect2>
 
     <sect2>
       <title>ʹ�� PPPoE �����ǩ</title>
 
       <para>��ijЩʱ�� �б�Ҫʹ��һ�������ǩ�������������ӡ�
 	�����ǩ��������ͬһ�����еIJ�ͬ��������</para>
 
       <para>��������ISP�ṩ���ĵ����ҵ���Ҫ�ķ����ǩ��Ϣ��
 	�������ҵ��� ��Ӧ������ ISP Ѱ����֧�֡�</para>
 
       <para>��Ϊ���ķ����� ����������
 	<ulink url="http://www.roaringpenguin.com/pppoe/">Roaring Penguin
 	PPPoE</ulink>�� �������� <link
 	linkend="ports">Ports Collection</link> ���ҵ���
 	Ȼ����Ҫע����ǣ� �����ܻ���� modem �Ĺ̼��� ��ʹ���޷�����������
 	���һ��Ҫ��ϸ����֮��������������� �򵥵ذ�װ�ɷ����ṩ���� modem
 	�ṩ�ij��� ��� ѡ��
 	<guimenu>System</guimenu> �˵��� ���������ļ�Ӧ�û��������г���
 	һ����˵��������Ӧ����
 	<emphasis>ISP</emphasis>��</para>
 
       <para>�����ļ��� (service tag�� �����ǩ) �������� PPPoE
 	�� <filename>ppp.conf</filename> �е������
 	��Ϊ������ <command>set device</command> �����һ���� (�μ� &man.ppp.8;
 	�����ֲ����˽����ϸ��)�� ��Ӧ��������������ӣ�</para>
 
       <programlisting>set device PPPoE:<replaceable>xl1</replaceable>:<replaceable>ISP</replaceable></programlisting>
 
       <para>��ס��<replaceable>xl1</replaceable>����ʵ�ʵ���̫���豸��</para>
       <para>��ס�� <replaceable>ISP</replaceable>
 	�������ո��ҵ���profile����</para>
 
       <para>��ø������Ϣ�� ��ο���</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><ulink
 	    url="http://renaud.waldura.com/doc/freebsd/pppoe/">Cheaper
 	    Broadband with FreeBSD on DSL</ulink> by Renaud
 	    Waldura.</para>
 	</listitem>
 
 	<listitem>
 	  <para><ulink
 	      url="http://www.ruhr.de/home/nathan/FreeBSD/tdsl-freebsd.html">
 	      Nutzung von T-DSL und T-Online mit FreeBSD</ulink>
 	    by Udo Erdelhoff (in German).</para>
 	</listitem>
       </itemizedlist>
     </sect2>
 
     <sect2 id="ppp-3com">
 
       <title>����һ��&tm.3com;
         <trademark class="registered">HomeConnect</trademark>
         ADSL Modem��PPPOE˫������</title>
 
       <para>��� modem ����ѭ <ulink
   	  url="http://www.faqs.org/rfcs/rfc2516.html">RFC 2516</ulink>
 	(<emphasis>A Method for transmitting PPP over Ethernet
 	(PPPoE)</emphasis>�� ������Ϊ L. Mamakos�� K. Lidl�� J. Evarts��
 	D. Carrel�� D. Simone �Լ� R. Wheeler)��
 	����ʹ�ò�ͬ�����ݰ���ʽ��Ϊ��̫���Ŀ�ܡ� ����
 	<ulink url="http://www.3com.com/">3Com</ulink> ��Թ��
 	�������Ϊ��Ӧ������ PPPoE �Ĺ淶��</para>
 
       <para>Ϊ����FreeBSD�ܹ�������豸ͨ�ţ� ��������sysctl��
 	ͨ������<filename>/etc/sysctl.conf</filename>��
 	��һ������������ʱ�Զ���ɣ�</para>
 
 	<programlisting>net.graph.nonstandard_pppoe=1</programlisting>
 
       <para>���ߣ� Ҳ����ֱ��ִ����������</para>
 
       <screen>&prompt.root; <userinput>sysctl net.graph.nonstandard_pppoe=1</userinput></screen>
 
       <para>�ܲ��ң���������ϵͳȫ�����ã� �޷�ͬʱ��������PPP�ͻ���(�������)
       ��&tm.3com;<trademark class="registered">HomeConnect</trademark>
       ADSL Modemͨ�š�</para>
 
     </sect2>
   </sect1>
 
   <sect1 id="pppoa">
     <title>ʹ�� ATM �ϵ� <application>PPP</application> (PPPoA)</title>
 
     <indexterm>
       <primary>PPP</primary>
       <secondary>over ATM</secondary>
     </indexterm>
 
     <indexterm>
       <primary>PPPoA</primary>
       <see>����ATM��PPP</see>
     </indexterm>
 
     <para>���½�����������û���ATM��PPP(PPPoA)��
       PPPoA��ŷ��DSL�ṩ�̵��ձ�ѡ��</para>
 
     <sect2>
       <title>ʹ�� Alcatel &speedtouch;USB �� PPPoA</title>
 
       <para>�����һ�豸�� PPPoA ֧�֣� ��
 	FreeBSD ������Ϊ port �ṩ�ģ� ��Ϊ��̼�ʹ���� <ulink
 	url="http://www.speedtouchdsl.com/disclaimer_lx.htm">��������������</ulink>��
 	��������� FreeBSD �Ļ���ϵͳһ����ѵ��ٷ�����</para>
 
       <para>ʹ�� <link
 	  linkend="ports">Ports �׼�</link> ���Էdz�����ذ�װ
 	<filename role="package">net/pppoa</filename> port��
 	֮�������ṩ��ָʾ�����Ϳ����ˡ�</para>
 
       <para>������ USB �豸���ƣ� �������ص� &speedtouch; USB
         ��Ҫ�����������ع̼����ܹ����������� �� &os; �������Խ��˲����Զ�����
         �����豸�嵽ij�� USB �ڵ�ʱ���Զ����ع̼��� ������
         <filename>/etc/usbd.conf</filename>
         �ļ��м����������Ϣ�������Զ���ɹ̼��Ĵ��͡� ע�⣬ ������
         <username>root</username> �û������ݱ༭����</para>
 
       <programlisting>device "Alcatel SpeedTouch USB"
     devname "ugen[0-9]+"
     vendor 0x06b9
     product 0x4061
     attach "/usr/local/sbin/modem_run -f /usr/local/libdata/mgmt.o"</programlisting>
 
      <para>Ҫ����USB�ػ�����<application>usbd</application>��
        ��<filename>/etc/rc.conf</filename>����������</para>
 
      <programlisting>usbd_enable="YES"</programlisting>
 
      <para>Ҳ���Խ�<application>ppp</application>���ó�����ʱ���š� ��
        <filename>/etc/rc.conf</filename>���������⼸�С�
        ͬ��������Ҫ��<username>root</username>�û���¼��</para>
 
      <programlisting>ppp_enable="YES"
 ppp_mode="ddial"
 ppp_profile="adsl"</programlisting>
 
      <para>Ϊ��ʹ������������ ����Ҫʹ��<filename role="package">net/pppoa</filename>
      port�ṩ��<filename>ppp.conf</filename>������</para>
 
     </sect2>
 
     <sect2>
       <title>ʹ��mpd</title>
 
       <para>����ʹ�� <application>mpd</application> �����Ӷ������͵ķ���
         �ر��� PPTP ���� �������� Ports Collection ���ҵ�
         <application>mpd</application>�� �������
         <filename role="package">net/mpd</filename>�� ���� ADSL modem
         ��Ҫ�� modem �ͼ����֮�佨��һ�� PPTP ������
         ���������� &speedtouch; Home �������е�һ�֡�</para>
 
       <para>������Ҫ�� port ��ɰ�װ��
         Ȼ��������� <application>mpd</application> ������������Ҫ��
         ����ɷ����̵����á� port ���һϵ�а�������ϸע��������ļ�ʵ���ŵ�
         <filename class="directory"><replaceable>PREFIX</replaceable>/etc/mpd/</filename>��
         ע�⣬ ����� <replaceable>PREFIX</replaceable> ��ʾ ports
         ��װ��Ŀ¼�� Ĭ������£� Ӧ����
         <filename class="directory">/usr/local/</filename>��
         �������� <application>mpd</application> ������˵���� ����
         HTML ��ʽ�� port һ��װ�� ��Щ�ļ�������
         <filename class="directory"><replaceable>PREFIX</replaceable>/share/doc/mpd/</filename>��
         ������ͨ�� <application>mpd</application> ���� ADSL
         �����һ�������ӡ� ���ñ��ֱ�ŵ��������ļ��У� ��һ����
         <filename>mpd.conf</filename>��</para>
 
       <programlisting>default:
     load adsl
 
 adsl:
     new -i ng0 adsl adsl
     set bundle authname <replaceable>username</replaceable> <co
     id="co-mpd-ex-user"/>
     set bundle password <replaceable>password</replaceable> <co
     id="co-mpd-ex-pass"/>
     set bundle disable multilink
 
     set link no pap acfcomp protocomp
     set link disable chap
     set link accept chap
     set link keep-alive 30 10
 
     set ipcp no vjcomp
     set ipcp ranges 0.0.0.0/0 0.0.0.0/0
 
     set iface route default
     set iface disable on-demand
     set iface enable proxy-arp
     set iface idle 0
 
     open</programlisting>
 
     <calloutlist>
       <callout arearefs="co-mpd-ex-user">
         <para>username����������ISP������֤��</para>
       </callout>
       <callout arearefs="co-mpd-ex-pass">
         <para> password����������ISP������֤��</para>
       </callout>
     </calloutlist>
 
     <para><filename>mpd.links</filename>�������ӵ���Ϣ��</para>
 
     <programlisting>adsl:
     set link type pptp
     set pptp mode active
     set pptp enable originate outcall
     set pptp self <replaceable>10.0.0.1</replaceable> <co
     id="co-mpd-ex-self"/>
     set pptp peer <replaceable>10.0.0.138</replaceable> <co
     id="co-mpd-ex-peer"/></programlisting>
 
     <calloutlist>
       <callout arearefs="co-mpd-ex-self">
 	<para>����<application>mpd</application>��������IP��ַ��</para>
       </callout>
       <callout arearefs="co-mpd-ex-peer">
 	<para>ADSL modem��IP��ַ�� Alcatel
 	  &speedtouch; Home Ĭ�ϵ��� <hostid
 	  role="ipaddr">10.0.0.138</hostid>��</para>
       </callout>
     </calloutlist>
 
     <para>��ʼ�����ӣ�</para>
 
     <screen>&prompt.root; <userinput>mpd -b <replaceable>adsl</replaceable></userinput></screen>
 
     <para>������ͨ����������鿴����״̬��</para>
 
     <screen>&prompt.user; <userinput>ifconfig <replaceable>ng0</replaceable></userinput>
 ng0: flags=88d1&lt;UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST&gt; mtu 1500
      inet 216.136.204.117 --> 204.152.186.171 netmask 0xffffffff</screen>
 
     <para>ʹ��<application>mpd</application>����ADSL�������Ƽ��ķ�ʽ��</para>
 
     </sect2>
 
     <sect2>
       <title>ʹ��pptpclient</title>
 
       <para>Ҳ����ʹ��<filename role="package">net/pptpclient</filename>����������
       PPPoA��</para>
 
       <para>Ҫʹ�� <filename role="package">net/pptpclient</filename> ����
 	 DSL ���� ��Ҫ��װ port �� package ���༭
 	 <filename>/etc/ppp/ppp.conf</filename>�� ����Ҫ��
 	 <username>root</username> Ȩ�޲�����������������
 	 ������ <filename>ppp.conf</filename> �е�һ��ʾ���
 	 �ο� <application>ppp</application> �������ֲ� &man.ppp.8;��
 	 ���˽�����й� <filename>ppp.conf</filename> ѡ�����Ϣ��</para>
 
       <programlisting>adsl:
  set log phase chat lcp ipcp ccp tun command
  set timeout 0
  enable dns
  set authname <replaceable>username</replaceable> <co id="co-pptp-ex-user"/>
  set authkey <replaceable>password</replaceable> <co id="co-pptp-ex-pass"/>
  set ifaddr 0 0
  add default HISADDR</programlisting>
 
    <calloutlist>
      <callout arearefs="co-pptp-ex-user">
 	   <para>���� DSL �����ṩ��������û���</para>
 	 </callout>
 	 <callout arearefs="co-pptp-ex-pass">
 	   <para>���ʻ��Ŀ��</para>
 	 </callout>
    </calloutlist>
 
    <warning>
      <para>���������뽫�ʺ����������ĵķ�ʽ����<filename>ppp.conf</filename>
 	 ��Ӧ��ȷ��û���κ����ܿ������ļ������ݡ� ����һϵ�������ȷ�����ļ�ֻ��
 	 <username>root</username>�û��ɶ���
 	 ��μ� &man.chmod.1; �� &man.chown.8; �������ֲ����˽��й���β����Ľ�һ����Ϣ��</para>
 	 <screen>&prompt.root; <userinput>chown root:wheel /etc/ppp/ppp.conf</userinput>
 &prompt.root; <userinput>chmod 600 /etc/ppp/ppp.conf</userinput></screen>
    </warning>
 
       <para>���½�Ϊ�� DSL ·�����ĻỰ��һ�� tunnel��
 	��̫��DSL modem��һ�����õľ�����IP��ַ�� �� Alcatel &speedtouch; Home
 	Ϊ���� �����ַ�� <hostid role="ipaddr">10.0.0.138</hostid>��
 	·�������ĵ�Ӧ�û��������ʹ�õĵ�ַ��
 	ִ�����������Դ� tunnel ����ʼ�Ự��</para>
 
       <screen>&prompt.root; <userinput>pptp <replaceable>address</replaceable> <replaceable>adsl</replaceable></userinput></screen>
 
       <tip>
 	<para>��Ӧ���������������(<quote>&amp;</quote>)�ţ� ���� <application>pptp</application>
 	�޷����ص���������ʾ����</para>
       </tip>
 
       <para>Ҫ����һ�� <devicename>tun</devicename>�����豸���ڽ���<application>pptp</application>
 	��<application>ppp</application> ֮��Ľ����� һ�����ص��������У�
 	���� <application>pptp</application>
 	����ȷ����һ�����ӣ� �������������tunnel�豸��</para>
 
       <screen>&prompt.user; <userinput>ifconfig <replaceable>tun0</replaceable></userinput>
 tun0: flags=8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1500
         inet 216.136.204.21 --> 204.152.186.171 netmask 0xffffff00
         Opened by PID 918</screen>
 
       <para>������޷����ӣ� һ�����ͨ��<application>telnet</application>����web��������·����(modem)�����á�
       ��������޷����ӣ� ��Ӧ�ü��<command>pptp</command>�������<application>ppp</application>����־�ļ�
 	<filename>/var/log/ppp.log</filename> �Ի��������</para>
     </sect2>
   </sect1>
 
   <sect1 id="slip">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Satoshi</firstname>
 	  <surname>Asami</surname>
 	  <contrib>Originally contributed by </contrib>
 	</author>
       </authorgroup>
       <authorgroup>
 	<author>
 	  <firstname>Guy</firstname>
 	  <surname>Helmer</surname>
 	  <contrib>With input from </contrib>
 	</author>
 	<author>
 	  <firstname>Piero</firstname>
           <surname>Serini</surname>
 	</author>
       </authorgroup>
     </sect1info>
 
     <title>ʹ��SLIP</title>
     <indexterm><primary>SLIP</primary></indexterm>
 
     <warning>
       <para>�������ֻ��
 	&os;&nbsp;7.X �Ͽ��á�</para>
     </warning>
 
     <sect2 id="slipc">
       <title>���� SLIP �ͻ���</title>
 
       <indexterm>
 	<primary>SLIP</primary>
 	<secondary>client (�ͻ���)</secondary>
       </indexterm>
 
       <para>�������ھ�̬�������������� FreeBSD ����ʹ�� SLIP �ķ�����
 	���ڶ�̬���������� (���ĵ�ַ����ÿ�β��Ŷ���ͬ)��
 	��������Ҫ�Ը���һЩ�����á�</para>
 
       <para>���ȣ� ����Ҫȷ�ϵ��ƽ���������ӵĴ��ڡ�
 	�����˻�����һ���������ӣ� ����
 	<filename class="devicefile">/dev/modem</filename>�� ����ָ��ʵ�ʵ��豸���� ��
 	<filename class="devicefile">/dev/cuad<replaceable>N</replaceable></filename>��
 	�������Ϳ��Զ�ʵ�ʵ��豸�����г���
 	�Ա����ƽ����������������ʱ�������֮�á� ��Ȼ�� �޸�
 	<filename class="directory">/etc</filename> �ͱ鲼��ϵͳ�е� <filename>.kermrc</filename>
 	�ļ�����һ�����鷳�����飡</para>
 
       <note>
 	<para><filename class="devicefile">/dev/cuad0</filename> ��Ӧ
 	  <devicename>COM1</devicename>�� �� <filename class="devicefile">/dev/cuad1</filename>
 	  ���Ӧ
 	  <devicename>COM2</devicename>�� �ȵȡ�</para>
       </note>
 
       <para>ȷ�������ں��ļ������������ݣ�</para>
 
       <programlisting>device   sl</programlisting>
 
       <para>�������<filename>GENERIC</filename>�ںˣ� ������Ӧ�ò����Ǹ����⣬ ������
         �Ѿ�ɾ��������</para>
 
       <sect3>
 	<title>ֻ����һ�ε�����</title>
 
 	<procedure>
 	  <step>
 	    <para>�������������ϵĻ����� �����Լ�������������
 	      �����뵽 <filename>/etc/hosts</filename> �ļ��С�
 	      ���ǵ�������������ӣ�</para>
 
 	    <programlisting>127.0.0.1               localhost loghost
 136.152.64.181          water.CS.Example.EDU water.CS water
 136.152.64.1            inr-3.CS.Example.EDU inr-3 slip-gateway
 128.32.136.9            ns1.Example.EDU ns1
 128.32.136.12           ns2.Example.EDU ns2</programlisting>
 	  </step>
 
 	  <step>
 	    <para>��ȷ�������� <filename>/etc/nsswitch.conf</filename>
 	      �е� <literal>hosts:</literal> С�����棬 <literal>files</literal> ����
 	      <literal>dns</literal> ���֡� ������������Ļ���
 	      ���ܻ����һЩ��ϣ��������</para>
 	  </step>
 
 	  <step>
 	    <para>�༭<filename>/etc/rc.conf</filename>��</para>
 
 	    <orderedlist>
 	      <listitem>
 		<para>�༭������������������(hostname)��</para>
 
 		<programlisting>hostname="myname.my.domain"</programlisting>
 
 		<para>Ӧ������������Internetȫ�����档</para>
 	      </listitem>
 
 	      <listitem>
 		<indexterm><primary>default route</primary></indexterm>
 
 		<para>�ı���һ����ָ��Ĭ�ϵ�·�ɣ�</para>
 
 		<programlisting>defaultrouter="NO"</programlisting>
 
 		<para>����</para>
 
 		<programlisting>defaultrouter="slip-gateway"</programlisting>
 	      </listitem>
 	    </orderedlist>
 	  </step>
 
 	  <step>
 	    <para>�����ļ�<filename>/etc/resolv.conf</filename>�� д���������ݣ�</para>
 
 	    <programlisting>domain CS.Example.EDU
 nameserver 128.32.136.9
 nameserver 128.32.136.12</programlisting>
 
 	    <indexterm><primary>nameserver</primary></indexterm>
 	    <indexterm><primary>domain name</primary></indexterm>
 	    <para>�����������ģ� ��Щ�������������������� ��Ȼ��
 	      ʵ�ʵ�������IP��ַȡ�������Ļ�����</para>
 	  </step>
 
 	  <step>
 	    <para>����<username>root</username>��
 	      <username>toor</username>������(�����κ�û��������ʺ�)��</para>
 	  </step>
 
 	  <step>
 	    <para>����������� Ȼ��ȷ��ʹ������ȷ����������</para>
 	  </step>
 	</procedure>
       </sect3>
 
       <sect3>
 	<title>����һ��SLIP����</title>
 
 	<indexterm>
           <primary>SLIP</primary>
           <secondary>connecting with</secondary>
         </indexterm>
 
 	<procedure>
 	  <step>
 	    <para>��������ʾ��֮������ <command>slip</command> ���в��ţ�
 	      �������Ļ������Ϳ�� ������Ҫ����ʲô��
 	      �����Ļ���������ء� ���ʹ��
 	      <application>Kermit</application>��
 	      �����ʹ����������Ľű���</para>
 
 	    <programlisting># kermit setup
 set modem hayes
 set line /dev/modem
 set speed 115200
 set parity none
 set flow rts/cts
 set terminal bytesize 8
 set file type binary
 # The next macro will dial up and login
 define slip dial 643-9600, input 10 =&gt;, if failure stop, -
 output slip\x0d, input 10 Username:, if failure stop, -
 output silvia\x0d, input 10 Password:, if failure stop, -
 output ***\x0d, echo \x0aCONNECTED\x0a</programlisting>
 
 	    <para>��Ȼ�� ������Ҫ�޸��û����Ϳ���������ʵ����Ҫ��
 	      �����Щ����֮�� ֻ���� <application>Kermit</application>
               ��ʾ��֮������ <command>slip</command> �Ϳ��������ˡ�</para>
 
 	    <note>
 	      <para>�������Դ��ı�����ʽ������ļ�ϵͳ������ζ��Ǹ� <emphasis>��</emphasis> ���⡣
 		�뿼���������ķ��ա�</para>
 	    </note>
 	  </step>
 
 	  <step>
 	    <para>�������˳� <application>Kermit</application> (Ҳ������
 	      <keycombo>
 		<keycap>Ctrl</keycap>
 		<keycap>z</keycap>
 	      </keycombo> �������)�� �� <username>root</username> �û����룺</para>
 
 	    <screen>&prompt.root; <userinput>slattach -h -c -s 115200 /dev/modem</userinput></screen>
 
 	    <para>�������<command>ping</command>ͨ·������һ�˵������� �������Ӻ���! ������У�
 	    ������ʹ��<option>-a</option>ѡ�����
 <option>-c</option>��Ϊ<command>slattach</command>�IJ�����</para>
 	  </step>
 	</procedure>
       </sect3>
 
       <sect3>
 	<title>�ر�����</title>
 
 	<para>������IJ�������</para>
 
 	<screen>&prompt.root; <userinput>kill -INT `cat /var/run/slattach.modem.pid`</userinput></screen>
 
 	<para>��ɱ�� <command>slattach</command>�� �м���������ֻ����
 	  <username>root</username> ���ݲ�����ɡ� �������ص�
 	  <command>kermit</command> (���֮ǰ�ǽ��������ˣ�
 	  ��ʹ�� <command>fg</command>) ���˳� (<keycap>q</keycap>)��</para>
 
 	<para>�� &man.slattach.8; �����ֲ����ᵽ��
 	  ����ʹ�� <command>ifconfig sl0 down</command>
           ���ܽ��ӿڱ��Ϊ�رգ� �����������ƺ�û��ʲô����
 	  (<command>ifconfig sl0</command> ��Ȼ����ͬ���Ķ�����)</para>
 
 	<para>��ʱ�� ���� modem ���ܻ�ܾ��Ҷϡ�
 	  ��������£� ֻ���������� <command>kermit</command>
 	  ���ٴ��˳����Ϳ����ˡ� һ����˵�Զ��ξͿ����ˡ�</para>
       </sect3>
 
       <sect3>
 	<title>������</title>
 
 	<para>��������У� ���ܷ��ʼ��� &a.net.name; �ʼ��б������ʡ�
 	  ���������������</para>
 
 	<itemizedlist>
 	  <listitem>
 	    <para>ִ�� <command>slattach</command> ʱ��ʹ��
 	      <option>-c</option>��<option>-a</option>ѡ��
 	      (��Ӧ�ò��ǹؼ��ģ� ����Щ�û��������������������)��</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>ʹ��<option>s10</option>�滻
 	      <option>sl0</option> (��һЩ�����º��ѿ�����ͬ)��</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>����<command>ifconfig sl0</command>���鿴���Ľӿ�״̬��
 	      ���磬 ��������������</para>
 
 	    <screen>&prompt.root; <userinput>ifconfig sl0</userinput>
 sl0: flags=10&lt;POINTOPOINT&gt;
         inet 136.152.64.181 --&gt; 136.152.64.1 netmask ffffff00</screen>
 	  </listitem>
 
 	  <listitem>
 	    <para>�����ʹ�� &man.ping.8; ʱ�õ���
             <errorname>no route to host</errorname> ��������ʾ��
             ��˵������·�ɱ����������⡣ ������ <command>netstat -r</command>
             ��������ʾ��ǰ��·�ɣ�</para>
 
 	    <screen>&prompt.root; <userinput>netstat -r</userinput>
 Routing tables
 Destination      Gateway            Flags     Refs     Use  IfaceMTU    Rtt    Netmasks:
 
 (root node)
 (root node)
 
 Route Tree for Protocol Family inet:
 (root node) =&gt;
 default          inr-3.Example.EDU  UG          8   224515  sl0 -      -
 localhost.Exampl localhost.Example. UH          5    42127  lo0 -       0.438
 inr-3.Example.ED water.CS.Example.E UH          1        0  sl0 -      -
 water.CS.Example localhost.Example. UGH        34 47641234  lo0 -       0.438
 (root node)</screen>
 
 	    <para>ǰ��������������һ���dz���æ��ϵͳ��
               ��ϵͳ�ϵ���Щ���ֻ��������IJ�ͬ���ı䡣</para>
 
 	  </listitem>
 	</itemizedlist>
       </sect3>
     </sect2>
 
     <sect2 id="slips">
       <title>����SLIP������</title>
 
       <indexterm>
         <primary>SLIP</primary>
         <secondary>server</secondary>
       </indexterm>
 
       <para>�����ṩ���� FreeBSD ������ SLIP ����
 	Ҳ���������������ϵͳ�� ʹ������Զ�� SLIP
 	�ͻ��˵�¼ʱ�Զ��ؿ������ӵĽ��顣</para>
 
       <!-- Disclaimer is not necessarily relevant
       <para> The author has written this document based
 	on his experience; however, as your system and needs may be
 	different, this document may not answer all of your questions, and
 	the author cannot be responsible if you damage your system or lose
 	data due to attempting to follow the suggestions here.</para>
       -->
 
       <sect3 id="slips-prereqs">
 	<title>ǰ������</title>
 	<indexterm><primary>TCP/IP networking</primary></indexterm>
 	<para>��һ�ڼ����Ժ�ǿ�� ����Ҫ������һ���ı���֪ʶ��
 	  ���ڼٶ�����Ϥ TCP/IP ����Э�飬 �ر�������ͽڵ�Ѱַ��
 	  �������롢 �������֡� ·�ɡ� ·��Э�� (��RIP) ��֪ʶ��
 	  �ڲ��ŷ����������� SLIP ��Ҫ��Щ�����Ե�֪ʶ��
 	  ���������Ϥ���ǣ� �����Ķ� Craig Hunt �� <emphasis>TCP/IP �������</emphasis>
 	  ��O'Reilly &amp; Associates, Inc. ���� (ISBN 0-937175-82-X)��
 	  �� Douglas Comer �й� TCP/IP Э����鼮��</para>
 
 	<indexterm><primary>modem</primary></indexterm>
 	<para>���⻹�ٶ����Ѿ����ú������ĵ��ƽ�����Լ���Ӧ��ϵͳ�ļ���
 	  ������ͨ�����ƽ�������е�¼�� �������û��Ϊ�����ú�ϵͳ��
 	  ��μ� <xref
 	  linkend="dialup"/> ���˽������ν��в��ŷ�������á�
 	  ������Ҳ���뿴һ�� &man.sio.4; �������ֲᣬ
 	  ���˽���ڴ����豸�����Ľ�һ����Ϣ�� �Լ� &man.ttys.5;��
 	  &man.gettytab.5;�� &man.getty.8; &amp; &man.init.8;
 	  �Ϲ�����������ϵͳ���������Ե��ƽ�����ĵ�¼����ľ��������
 	  ���� &man.stty.1; ���˽�������ô��ڲ���
 	  (���� <literal>clocal</literal> ��ʾ����ֱ��) �ȡ�</para>
       </sect3>
 
       <sect3>
 	<title>�������</title>
 
 	<para>ʹ��FreeBSD��ΪSLIP�������� �ڵ�������ʱ�� �������������ģ�
 	  һ��SLIP�ͻ����Ų���ר�õ�login ID��¼��FreeBSD SLIP������ϵͳ��
 	  ����û�ʹ�� <filename>/usr/sbin/sliplogin</filename>
 	  ��Ϊ shell�� <command>sliplogin</command> ��������ļ�
 	  <filename>/etc/sliphome/slip.hosts</filename> �в�������û����
 	  ����ҵ���ƥ��� �ͽ����������ӵ�һ�����õ� SLIP �ӿڣ�
 	  Ȼ������ shell �ű� <filename>/etc/sliphome/slip.login</filename>
 	  ������ SLIP �ӿڡ�</para>
 
         <sect4>
 	  <title>һ��SLIP��������¼������</title>
 
 	  <para>���磬 ���һ��SLIP�û���ID��<username>Shelmerg</username>��
          ��<filename>/etc/master.passwd</filename>��<username>Shelmerg</username>�������µ���ʾ��</para>
 
 	  <programlisting>Shelmerg:password:1964:89::0:0:Guy Helmer - SLIP:/usr/users/Shelmerg:/usr/sbin/sliplogin</programlisting>
 
 	  <para><username>Shelmerg</username>��¼ʱ��
 	    <command>sliplogin</command>���ļ�
 	    <filename>/etc/sliphome/slip.hosts</filename>���������û�IDƥ�����;������ʾ��</para>
 
 	  <programlisting>Shelmerg        dc-slip sl-helmer       0xfffffc00		  autocomp</programlisting>
 
 	  <para><command>sliplogin</command>�ҵ����������У�
 	   ��������������һ�����õ�SLIP�ӿ���������
 	   Ȼ��ִ��<filename>/etc/sliphome/slip.login</filename>�ű���</para>
 
 	  <programlisting>/etc/sliphome/slip.login 0 19200 Shelmerg dc-slip sl-helmer 0xfffffc00 autocomp</programlisting>
 
 	  <para>���һ��˳��
 	    <filename>/etc/sliphome/slip.login</filename> ����
             <command>sliplogin</command> �󶨵� SLIP �ӿ��Ϸ���
 	    <command>ifconfig</command> (ǰ������������ SLIP �ӿ�
 	    0�� ���� <filename>slip.login</filename> �ĵ�һ������)��
 	    �����ñ��� IP ��ַ (<hostid>dc-slip</hostid>)�� Զ�� IP ��ַ
 	    (<hostid>sl-helmer</hostid>)�� ��һ SLIP
 	    �ӿڵ��������� (<hostid role="netmask">0xfffffc00</hostid>)��
 	    �Լ��κ�������־ (<literal>autocomp</literal>)��
 	    ����������� <command>sliplogin</command> ͨ����ͨ��
 	    <application>syslogd</application> �� daemon facility
 	    �������õ���Ϣ�� ǰ�߻����Щ��Ϣ���浽
             <filename>/var/log/messages</filename>
 	    (�μ� &man.syslogd.8; �� &man.syslog.conf.5; �Լ�
 	    <filename>/etc/syslog.conf</filename> �������ֲᣬ ���˽�
 	    <application>syslogd</application> �ڼ�¼ʲô��
 	    �Լ���Щ���ݽ�����������)��</para>
 	</sect4>
       </sect3>
 
       <sect3>
 	<title>�ں�����</title>
 
 	<indexterm>
           <primary>kernel</primary>
           <secondary>configuration</secondary>
         </indexterm>
 
 	<indexterm>
           <primary>SLIP</primary>
         </indexterm>
 
 	<para>&os; ��Ĭ���ں� (<filename>GENERIC</filename>)
 	  �ṩ�� SLIP (&man.sl.4;) ֧�֣� ʹ�ö��Ƶ��ں�ʱ��
 	  ���������������ü��뵽�����ļ���</para>
 
 	<programlisting>device   sl</programlisting>
 
 	<para>Ĭ������£� ���� &os; ���������ת������
 	  �����ϣ���� FreeBSD SLIP ��������Ϊ·����ʹ�ã�
 	  ����Ҫ�޸� <filename>/etc/rc.conf</filename> �ļ���
 	  �� <literal>gateway_enable</literal> ������Ϊ
 	  <option>YES</option>�� �����´�ϵͳ����ʱ���ܹ�������һ�����ˡ�</para>
 
 	<para>Ҫ����Ӧ����Щ���ã� ���� <username>root</username>
 	  ����������</para>
 
 	<screen>&prompt.root; /etc/rc.d/routing start</screen>
 
 	<para>����� <xref linkend="kernelconfig"/> ���˽�������� FreeBSD
 	  �ںˣ� ����������������ں˷����ָ����</para>
       </sect3>
 
       <sect3>
 	<title>Sliplogin����</title>
 
 	<para>������ǰ���ᵽ�ģ�
 	  <filename class="directory">/etc/sliphome</filename> Ŀ¼���������ļ���
 	  ���ǹ�ͬ���� <filename>/usr/sbin/sliplogin</filename> ������ (�ο�
 	  <command>sliplogin</command> �������ֲ� &man.sliplogin.8;)��
 	  ���ڶ��� SLIP �û�����ص� IP
 	  ��ַ�� <filename>slip.hosts</filename>��
 	  ͨ������������ SLIP �ӿڵ� <filename>slip.login</filename>�� �Լ� (��ѡ��)
 	  <filename>slip.logout</filename>�� ���Գ�����
 	  <filename>slip.login</filename> ��ִ�еĶ�����</para>
 
         <sect4>
 	  <title>���� <filename>slip.hosts</filename></title>
 
 	  <para><filename>/etc/sliphome/slip.hosts</filename>���ÿ�а��������ĸ�Ԫ�أ� Ԫ��֮���ɿո������</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>SLIP�û��ĵ�¼ID</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>SLIP���ӵı��ص�ַ(ָSLIP������)</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>SLIP���ӵ�Զ�̵�ַ</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>��������</para>
 	    </listitem>
 	  </itemizedlist>
 
 	  <para>���غ�Զ�̵�ַ������������
 	    (ͨ���ļ�<filename>/etc/hosts</filename>���������������ΪIP��ַ��
 	    ��ȡ�����ļ�<filename>/etc/nsswitch.conf</filename>
 	    �е�����)�� ��������������һ��
 	    ��ͨ���ļ�<filename>/etc/networks</filename>���������֡�
 	    ��һ������ϵͳ�У�
 	    <filename>/etc/sliphome/slip.hosts</filename>�������ģ�</para>
 
 	  <programlisting>#
 # login local-addr      remote-addr     mask            opt1    opt2
 #                                               (normal,compress,noicmp)
 #
 Shelmerg  dc-slip       sl-helmerg      0xfffffc00      autocomp</programlisting>
 
 	  <para>������ĩβ��һ����ѡ�</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para><option>normal</option> &mdash;��ѹ����ͷ
 		</para>
 	    </listitem>
 
 	    <listitem>
 	      <para><option>compress</option> &mdash; ѹ����ͷ</para>
 	    </listitem>
 
 	    <listitem>
 	      <para><option>autocomp</option> &mdash;���Զ�̶������� ѹ����ͷ</para>
 	    </listitem>
 
 	    <listitem>
 	      <para><option>noicmp</option> &mdash;����ICMP���ݰ�
 		(�����ͻᶪ�����е�<quote>ping</quote>���ݰ��� ��ռ�����Ĵ���)</para>
 	    </listitem>
 	  </itemizedlist>
 
   	  <indexterm><primary>SLIP</primary></indexterm>
   	  <indexterm><primary>TCP/IP networking</primary></indexterm>
 	  <para>��SLIP���ӵı��ؼ�Զ�̵�ַ��ѡ��ȡ��������׼����SLIP��������ʹ�� TCP/IP
 	    ��������ʹ��<quote>ARP����</quote> (��������<quote>������</quote>ARP������ ���������ڱ������ڽ��ܵ�����)��
 	    ���������ȷ��ѡ����ַ�ʽ������η����ַ�� ��ο�"ǰ������"(<xref linkend="slips-prereqs"/>)���г���TCP/IP�鼮
 	    ����������IP�������Ա��̡�</para>
 
 	  <para>�������Ϊ���� SLIP �ͻ�ʹ��һ��������������
 	    ����Ҫ�ȴӷ���õ����������ȡ��һ�������ţ�
 	    Ȼ����������������ÿ�� SLIP �ͻ����� IP ��ַ��
 	    �������� ������Ҫͨ�� SLIP ������������� IP
 	    ·����������һ��ָ�� SLIP �����ľ�̬·�ɡ�</para>
 
   	  <indexterm><primary>Ethernet</primary></indexterm>
 	  <para>���Ҫʹ�� <quote>���� ARP</quote>
 	    �ķ�ʽ�� ������Ҫ�� SLIP ����������̫������Ϊÿ�� SLIP �ͻ�����IP��ַ��
 	    �������޸�<filename>/etc/sliphome/slip.login</filename> ��
 	    <filename>/etc/sliphome/slip.logout</filename>�ű���ʹ��
 	    &man.arp.8;�������� SLIP
 	    ������ ARP ���е� <quote>���� ARP</quote> �</para>
 	</sect4>
 
 	<sect4>
 	  <title><filename>slip.login</filename> Configuration</title>
 
 	  <para>���͵�<filename>/etc/sliphome/slip.login</filename>
 	   ������ʾ��</para>
 
 	  <programlisting>#!/bin/sh -
 #
 #       @(#)slip.login  5.1 (Berkeley) 7/1/90
 
 #
 # generic login file for a slip line.  sliplogin invokes this with
 # the parameters:
 #      1        2         3        4          5         6     7-n
 #   slipunit ttyspeed loginname local-addr remote-addr mask opt-args
 #
 /sbin/ifconfig sl$1 inet $4 $5 netmask $6</programlisting>
 
 	  <para>���<filename>slip.login</filename>�ű�����Ϊ������Ӧ���ؼ�Զ�̵�ַ�������SLIP�ӿ�ִ��
 	    <command>ifconfig</command>��</para>
 
 	  <para>���������ʹ��<quote>ARP����</quote>
 	    ��ʽ(����Ϊ����SLIP�ͻ�ʹ�ö���������)�� ����<filename>/etc/sliphome/slip.login</filename>
 	   Ӧ����������</para>
 
 	  <programlisting>#!/bin/sh -
 #
 #       @(#)slip.login  5.1 (Berkeley) 7/1/90
 
 #
 # generic login file for a slip line.  sliplogin invokes this with
 # the parameters:
 #      1        2         3        4          5         6     7-n
 #   slipunit ttyspeed loginname local-addr remote-addr mask opt-args
 #
 /sbin/ifconfig sl$1 inet $4 $5 netmask $6
 # Answer ARP requests for the SLIP client with our Ethernet addr
 /usr/sbin/arp -s $5 00:11:22:33:44:55 pub</programlisting>
 
 	  <para><filename>slip.login</filename>�¼ӵ���<command>arp -s
 	    &#36;5 00:11:22:33:44:55 pub</command> �� SLIP �������� ARP
 	   ���м�����һ����� ���ARP��ʹ��ÿ�������̫���ϵ�����
 	   IP �ڵ�� SLIP �ͻ��� IP ��ַ���� ARP ����ʱ��
 	   SLIP �������������ѵ���̫��MAC��ַ��Ϊ��Ӧ��</para>
 
   	  <indexterm>
             <primary>Ethernet (��̫��)</primary>
             <secondary>MAC address (MAC ��ַ)</secondary>
           </indexterm>
 
 	  <para>��ʹ�����ϵ�����ʱ�� һ��Ҫ��
 	  ��̫��MAC��ַ ��<hostid role="mac">00:11:22:33:44:55</hostid>��
             �滻����ϵͳ������MAC��ַ�� ����<quote>ARP����</quote>
             ����ȫ�޷������� �����Բ鿴 <command>netstat -i</command>
             ��������ȡ����̫�� MAC ��ַ; ����ĵڶ���Ӧ����������</para>
 
 	  <screen>ed0   1500  &lt;Link&gt;0.2.c1.28.5f.4a         191923	0   129457     0   116</screen>
 
 	  <para>���б������ϵͳ����̫��MAC��ַ��<hostid role="mac">00:02:c1:28:5f:4a</hostid>
 	    &mdash;<command>netstat -i</command>�������̫��MAC��ַ����ij���ð�Ÿ����� ����Ҫ����ʮ������ǰ���ϡ�
 	     ����&man.arp.8;Ҫ��ĸ�ʽ; �ο�&man.arp.8; �������ֲ��Ի�ȡ������ʹ�÷�����</para>
 
 	  <note>
 	    <para>�ڱ�д
 	      <filename>/etc/sliphome/slip.login</filename> ��
 	      <filename>/etc/sliphome/slip.logout</filename> ʱ�� һ��Ҫ����
 	      <quote>��ִ��</quote> (execute) λ (����֮�� <command>chmod 755
 	      /etc/sliphome/slip.login /etc/sliphome/slip.logout</command>)��
 	      ���� <command>sliplogin</command>���޷�ִ������</para>
 	  </note>
 	</sect4>
 
 	<sect4>
 	  <title><filename>slip.logout</filename>����</title>
 
 	  <para><filename>/etc/sliphome/slip.logout</filename>�����DZ����
 	  (������ʹ����<quote>ARP����</quote>)�� �����׼���������� ������һ��������
 	  <filename>slip.logout</filename> �ű������ӣ�</para>
 
 	  <programlisting>#!/bin/sh -
 #
 #       slip.logout
 
 #
 # logout file for a slip line.  sliplogin invokes this with
 # the parameters:
 #      1        2         3        4          5         6     7-n
 #   slipunit ttyspeed loginname local-addr remote-addr mask opt-args
 #
 /sbin/ifconfig sl$1 down</programlisting>
 
 	  <para>���ʹ���� <quote>���� ARP</quote>��
 	    �����ϣ�� <filename>/etc/sliphome/slip.logout</filename>
 	    ���û�ע��ʱ�Զ�Ϊ SLIP �ͻ���ɾ��
 	    ARP �</para>
 
 	  <programlisting>#!/bin/sh -
 #
 #       @(#)slip.logout
 
 #
 # logout file for a slip line.  sliplogin invokes this with
 # the parameters:
 #      1        2         3        4          5         6     7-n
 #   slipunit ttyspeed loginname local-addr remote-addr mask opt-args
 #
 /sbin/ifconfig sl$1 down
 # Quit answering ARP requests for the SLIP client
 /usr/sbin/arp -d $5</programlisting>
 
 	  <para><command>arp -d &#36;5</command> ��ɾ���� <quote>���� ARP</quote>
 	    <filename>slip.login</filename> �� SLIP �ͻ������¼ʱ�����ɵ�
 	    ARP �</para>
 
 	  <para>�ٴ�ǿ���� ����
 	    <filename>/etc/sliphome/slip.logout</filename> ֮��
 	    һ��Ҫ���ÿ�ִ��λ (Ҳ����˵�� <command>chmod 755
 	    /etc/sliphome/slip.logout</command>)��</para>
 	</sect4>
       </sect3>
 
       <sect3>
 	<title>·�ɿ���</title>
 	<indexterm>
     <primary>SLIP</primary>
     <secondary>routing</secondary>
   </indexterm>
 	<para>���û��ʹ�� <quote>���� ARP</quote> �ķ�����������
 	  SLIP �ͻ�������������ಿ�� (Ҳ������ Internet)
 	  ֮��·�����ݰ��� ��������Ҫ�������������Ĭ��·�����ľ�̬·�ɣ�
 	  �Ա�ͨ�� SLIP ���������� SLIP �ͻ��������Ͻ���·�ɡ�</para>
 
 	<sect4>
 	  <title>��̬·��</title>
 	  <indexterm><primary>static routes</primary></indexterm>
 
 	  <para>���������Ĭ��·������һ����̬·�ɿ���˵�Ǻ��鷳
 	    (����˵�Dz����ܣ� �����û��Ȩ����ô��)�� �����������֯��ʹ�ö�·�������磬
 	    ��Щ·���� (���� Cisco �� Proteon ������) ����Ҫ����ָ�� SLIP
 	    ������·�ɣ� ���һ���Ҫ���ý���Щ��̬·�ɴ���������·������
 	    ����һЩר����������������ʹ���ھ�̬·�ɱ���·�������������б�Ҫ��</para>
 	</sect4>
       </sect3>
     </sect2>
   </sect1>
 </chapter>
diff --git a/zh_TW.Big5/articles/contributing/article.xml b/zh_TW.Big5/articles/contributing/article.xml
index d372acf288..f888dfdf8b 100644
--- a/zh_TW.Big5/articles/contributing/article.xml
+++ b/zh_TW.Big5/articles/contributing/article.xml
@@ -1,488 +1,483 @@
 <?xml version="1.0" encoding="big5"?>
 <!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.5-Based Extension//EN"
 	"../../../share/xml/freebsd45.dtd">
 
 <!--
      The FreeBSD Documentation Project
      The FreeBSD Chinese (Traditional) Documentation Project
 
      Original Revision: 1.506
      Chased Revision: 1.508
 -->
 
 <article lang='zh_tw'>
   <articleinfo>
     <title>���U FreeBSD</title>
 
     <abstract>
       <para>�L�׬O�ӤH�άO�U�ز�´�A�p�G�Ʊ欰 FreeBSD �������U�A���i�H�b���夤���X�A����k�C</para>
     </abstract>
 
     <authorgroup>
       <author>
 	<firstname>Jordan</firstname>
 	<surname>Hubbard</surname>
 	<contrib>��ۡG </contrib>
       </author>
     </authorgroup>
 
     <legalnotice id="trademarks" role="trademarks">
       &tm-attrib.freebsd;
       &tm-attrib.ieee;
       &tm-attrib.general;
     </legalnotice>
 
     <pubdate>$FreeBSD$</pubdate>
 
     <releaseinfo>$FreeBSD$</releaseinfo>
 
   </articleinfo>
 
    <indexterm><primary>�^�m</primary></indexterm>
 
   <para>�A�Ʊ�� FreeBSD ���I����ܡH�Ӧn�F�A�ڭ��w��A�CFreeBSD
     ���O�����s�j�ϥΪ̪��^�m�~�o�H�o�i���j���C�ڭ̤��ȫD�`�P�±z�Ұ����^�m�A�ӥB�A�o�Ǥu�@��� FreeBSD ������o�i�]�������n�C</para>
 
 
   <para>�]�\�P�z�Q�������P�A�z�J�����o�O�@�W�X�⪺ Programmer�A�]�L���M
     FreeBSD core team �������ܦn���p��A�ڭ̷|�@���P������ݱz���u�@�C
     FreeBSD ���}�o�H���M�����y�A�j�a�޳N�M���U���A�~�֤����]�D�`�s�x�C
     �M�ӡA�C�ѧڭ̳��b�������W�[���u�@�A�ӭW��S���������H��A�]���ڭ��H���w��z�����U�C</para>
 
   <para>FreeBSD �p���ҳB�z���O�@�ӧ��㪺�@�~�t�����ҡA�Ӥ��u�O�@�� kernel �άO�@�ǹs�����u��]�C
 	�]���A�ڭ̪� <filename>TODO</filename> �ݿ���ȦC���̥]�t�U���U�˪��u�@�G
     �q���B�ϥΪ̴��աBdemo�A��t�Φw�˵{���M��M�~�� kernel �}�o�C
     �]���L�ױz���޳N���Ǧp��A�q�Ʀ�ػ��A���i�H���U�o�ӭp���C</para>
 
   <para>�ڭ̹��y�q�ƩM FreeBSD �����u�@�����~�M�ڭ��pô�C
     �z�ݭn�@�ǯS�����X�i�Өϱz�����~�B��_�ӶܡH
     �z�|�o�{�ڭַ̫ܼN�����z���ШD�A���D�O�S�O�}�_�j�Ǫ��C
     �z�O�_���q�Ƭ������W�ȷ~�ȡH ���ڭ̨����U�z�a�A
     �ڭ̤]�\�i�H�b�Y�Ǥ譱�ۤ��X�@�C
     �ۥѳn��ɥ��b�V�O���}�¦����خ�(���O����n��}�o�B�P��M���@)�A
     �ڭ̧Ʊ����бz�ܤ֯൹���@�����|�C</para>
 
   <sect1 id="contrib-what">
     <title>�ڭ̪��ݨD</title>
 
     <para>�U���C�X�F�@�ǻݭn���������ȩM�l�p���A
       ���̥N�� <filename>TODO</filename>(�ݿ���ȦC��)
       �C�����N��A�H�ΨϥΪ̪��n�D�C</para>
 
     <sect2 id="non-programmer-tasks">
       <title>���b�i�椤������(�D�{���}�o�H��)</title>
 
       <para>�ܦh�ѥ[ FreeBSD �p�����H���O Programmer�C
 	�o�ӭp���̦���󼶼g�̡B�����]�p�v�B�H�Χ޳N�䴩�H���C
 	���o�Ǹq�u�ӻ��A�L�̥u�ݭn�^�m�@�Ǯɶ��A�åB�㦳�Dzߪ��N�@�C</para>
 
       <orderedlist>
 	<listitem>
 	  <para>�z�i�H�ɱ`½�\ FAQ �M��U(Handbook)
 	    �A�p�G�o�{���������M�����a��A�άO���X�ɩy�����A�Ʀܧ��������T���a��A
 	    ���Чi�D�ڭ̡C���M�A�Y�බ���L�̭ץ��A�ç�ɻ~�H���ڭ̡A���N��n�F�C:)
 	    (SGML ���ä����ǡA���ڭ̤]���Ϲ�z��������@�� ASCII ���¤�r����)�C</para>
 	</listitem>
 
 	<listitem>
 	  <para>���U�ڭ̧� FreeBSD ���½Ķ���A�����y�C
 	    �p�G�A�����y�����w�g�s�b�F�A
 	    �]�i�H½Ķ�@���B�~�����A�Ϊ��ˬd���Ǥw�������O�_���̷s���C
 	    �z�i�H��²��ݬ� FreeBSD ���p�������� <ulink
 	    url="&url.books.fdp-primer;/translations.html">½Ķ�ɪ��`�����D</ulink>�C
 	    �ѥ[½Ķ�u�@�A�ä��O���z�n�t�x�ľ�½Ķ�Ҧ� FreeBSD ���C
 	    �����q�u�A�n���h�֤u�@�������M��z���N�@�C�@���Y�ӤH�}�l½Ķ�F�A
 	    ����X�G�@�w�|����L�H�ѻP��o�Ǥu�@���ӡC
 	    �p�G�ɶ������A�Ϊ̺�O�����h½Ķ������A���i�H�����h½Ķ�w�˫��n�C</para>
 	</listitem>
 
 	<listitem>
 	  <para>�\Ū &a.questions; �ð���½�\(�Ʀܦ��W�ߦa�o�˰�) &ng.misc;
 	    �C�P�O�H���ɱz���M�~���ѡA
 	    �����U�L�̸ѨM���D�A�O��O�H�r�����Ʊ��F
 	    ���ɭԡA�z�Ʀܥi�H�b�o�ӹL�{���Ǩ�@�Ƿs�F��I
 	    �o�ǽ׾¦��ɤ]�|���z�E�o�X�@�Ǥ������Q�k�C</para>
 	</listitem>
       </orderedlist>
     </sect2>
 
     <sect2 id="ongoing-programmer-tasks">
       <title>���b�i�椤������(�{���}�o�H��)</title>
         <para>�C�b�o�̪��j�������ȳ��ݭn�z��J�i�[���ɶ��A�Ϊ̻ݭn�z�b FreeBSD kernel
 	�譱���״I�����ѡA�Ϊ̨�̳��n�C���M�o�̤]���ܦh���n�����ȡA�A�X���O
 	<quote>weekend hackers</quote> �o���u�ζg���N�i�H�d�w�� Hacker�C</para>
 
       <orderedlist>
 	<listitem>
 	  <para>�p�G�z���b�]���O FreeBSD -CURRENT �����A�åB�����t���٤����A
 	    ����i�H�� <hostid
 	    role="fqdn">current.FreeBSD.org</hostid>�A
 	    �o�x�C�ѷ|���@�ӷs���� &mdash; �p�G�z���šA
 	    �z�i�H�T�����ɤU���æw�ˡA
 	    �䶡�p�G�X�F������D�A�Чi�D�ڭ̡C</para>
 	</listitem>
 
 	<listitem>
 	  <para>�\Ū &a.bugs;�C�o�ǰ��D�A�γ\�z�ണ�Ѧ��س]�ʷN�q���N���A
 	    �Ϊ��������դ@�� patch �C���~�A�Ʀܥi�H���խץ��䤤���@�ǰ��D�C</para>
 	</listitem>
 
 	<listitem>
 	  <para>�p�G�z���D���@�ǭץ��w�g�b -CURRENT �W���\�a�ϥΡA
 	    ���b�g�L�@�q�ɶ�(�q�`�O 2 �g���k)����A�����X�֨� -STABLE
 	    (�o�B�J�N�O MFC -- Merged From Current)�A����i�H�������� committer �H���o��§���������H�C</para>
 	</listitem>
 
 	<listitem>
 	  <para>�N�ĤT��(3rd party)�n��[�J���l�X����
 	    <filename>src/contrib</filename> �ؿ��C</para>
 	</listitem>
 
 	<listitem>
 	  <para>�T�O <filename>src/contrib</filename> ������l�X�O�̷s���C</para>
 	</listitem>
 
 	<listitem>
 	  <para>�sĶ��l�X(�άO������l�X)�ɡA�Ч�Χ󰪪�ĵ�i����(warning level)
 	     �H�K����(debug)�ΡA�æb�������աB�T�{���`��������A�M���o�ǽsĶ��ĵ�i���šC</para>
 	</listitem>
 
 	<listitem>
 	  <para>��s���Ǧb ports ���ϥιL�ɪ��F��A
 	    �Ҧp <function>gets()</function> �Υ]�t
 	    <filename>malloc.h</filename> �Ҳ��ͪ�ĵ�i�C</para>
 	</listitem>
 
 	<listitem>
 	  <para>�p�G���� ports �@�F����ץ��A
 	    �аO�o�N�z�� patch �o����@�� (�o�ˤU���ɯŮɡA�z���u�@�|�ܱo���P�@��)�C</para>
 	</listitem>
 
 	<listitem>
 	  <para>�����o�������зǡA�p &posix; ���ƥ��C
 	    �b <ulink
 	    url="&url.base;/projects/c99/index.html">FreeBSD
 	    C99 &amp; POSIX �зǬۮe�p��</ulink> �����W�A�i�H�o������챵�C
 	    �бN FreeBSD ���欰�P�W�z���зǶi�����A�Y�ұo���G�P C99 &amp; POSIX �зǤ��P���ܡA
 	    �S�O�O���DzӸ`�a�誺�L�p�t���A�еo�@�����󥦪� PR (���D���i)�C
 	    �p�G�i��A�Ы��X�p��ץ����A���H PR ���� patch �C
 	    �p�G�z�{���зǦ����D�A�ЦV�o�dzW��зǪ���������A�ШD���i�歫�s���Ҽ{�C</para>
 	</listitem>
 
 	<listitem>
 	  <para>���o���C�����ѧ�h��ij�I</para>
 	</listitem>
       </orderedlist>
     </sect2>
 
     <sect2>
       <title>�d�\��� PR ��Ʈw</title>
 
       <indexterm><primary>���D���i��Ʈw</primary></indexterm>
 
       <para><ulink
 	url="http://www.FreeBSD.org/cgi/query-pr-summary.cgi">FreeBSD
 	PR �C��</ulink> �o�̷|��ܥثe�Ҧ� PR �����D���A�A�H�Υ�
 	FreeBSD �ϥΪ̴��檺��i��ij�C
 	PR ��Ʈw�P�ɥ]�A�F�}�o�H���M�D�}�o�H�������ȡC
 	�d�ݨ��ǩ|���ѨM�� PR�A�ìݬݬO�_���z�P���쪺���ȡC
 	�o�䤤�i�঳�@�ǬO�D�`²�檺���D�A�u�ݭn�ݤ@�ݨýT�{ PR �O���T���C
 	�t�~�@�ǥi��|�D�`�����A�Ϊ̧�����������ץ��C</para>
 
       <para>�����ݤ@�ݨ����٨S���H���⪺ PR�C
 	�p�G PR �w�g���t���F�䥦�H�A���ݰ_�ӬO�z����B�z���A
 	�z�i�H�H�H�����ӤH�A�ø߰ݱz�O�_�i�H�������U &mdash;
 	�L�̥i��w�g���i�Ѵ��ժ� patch �A�Φ��@�ǥi�ѰQ�ת��N���C</para>
     </sect2>
 
     <sect2>
       <title>�� <quote>Ideas</quote> ����@��</title>
 
       <para><ulink url="&url.base;/projects/ideas/">&os; list of
 	projects and ideas for volunteers</ulink> �P�˦a�}�񵹦��N�@�ѻP
 	&os; �p�����H�C
 	�o���M��N����a��s�A�P�ɴ��ѦU�Ӷ��ت���T���Ҧ��H
 	�]���׬O�_���{���]�p�H���^�C</para>
     </sect2>
   </sect1>
 
   <sect1 id="contrib-how">
     <title>�p�󴣨����U</title>
 
     <para>�򥻤W�i�H�����H�U 5 �ؤ覡�G</para>
 
     <sect2 id="contrib-general">
       <title>���~���i�M�N���o��</title>
 
       <para>�q�`�A<emphasis>�@��</emphasis>
 	���޳N�Q�k�M��ij���ӵo�� &a.hackers;�C
 	�P�˦a�A���o�ǪF�観���쪺�H (���M�A
 	�L�̦P���٭n����e�� <emphasis>�j�q��</emphasis> �l��I)
 	�i�H�Ҽ{�q�\ &a.hackers;�C
 	�аѾ\ <ulink
 	url="&url.books.handbook;/eresources.html#ERESOURCES-MAIL">FreeBSD
 	�ϥΤ�U</ulink> �H�F������o�Ӷl���׾¡A
 	�H�Ψ䥦�l���׾ª��Բӱ��p�C</para>
 
       <para>�p�G�z�o�{�F bug �Ϊ̷Q�n����Y�ǭק�A
 	�гz�L &man.send-pr.1; �{���Ψϥ�
 	<ulink url="&url.base;/send-pr.html">��������
 	���^��</ulink> �Ӵ���C�иյ۶�g PR ���C�Ӷ��ءC
 	�@��ӻ��A���D patch �ɶW�L 65 KB�A�ڭ̫�ij�b PR ���������W patch �N�i�H�F�C
 	�Y�i�����M��  patch ���l�X���ܡA�����ij�b PR ��
 	Synopsis ������ <literal>[PATCH]</literal>�C
 	��F�A�b���W patch �ɡA�� <emphasis>���n</emphasis>
 	�z�L�ƹ����y�ƻs�B�K�W�z�Ӷi��A�]���o�˰��|�� Tab �ܦ��Ů�A
 	�|�ɭP patch �N����ΤF�C�p�G patch �W�L 20KB�A
 	�ЦҼ{���Y���èϥ� &man.uuencode.1; �Ӷi��s�X�C</para>
 
       <para>�b�g�� PR ����A�z�|����@�ʽT�{�l��H�Ψƥ�l�ܽs���C
 	�ЫO�d�o�ӽs���A�]���ƫ�i�H�γo�s���o�H�� &a.bugfollowup;
 	�Ӧ^�СB��������Өƥ󪺫����ơC�z�ݭn�����O�N�s�����l�󪺼��D���A
 	�Ҧp  <literal>"Re:
 	kern/3377"</literal>�C
 	�Y�O�P�@���D���^�Ф譱�A���ӳz�L�o�ؤ覡�Ӷi��C</para>
 
       <para>�p�G�z�b�@�q�ɶ� (�W�L 3 �ѬƦ� 1 �g�A�o���M��z���l��A��)���ᤴ�M�S������T�{�H
 	�Ϊ̥ѩ�@�ǭ�]�L�k�ϥ� &man.send-pr.1; �{���A
 	�h�i�H�o�H�� &a.bugs; �ӽЧO�H���A�N�H�C</para>
 
       <para>�аѾ\ <ulink
   	url="&url.articles.problem-reports;/article.html">�o�g�峹</ulink>
   	�F�Ѧp�󼶼g�n�����D���i�C</para>
     </sect2>
 
     <sect2>
       <title>����󪺭׭q</title>
 
       <indexterm><primary>������</primary></indexterm>
 
       <para>��󪺭ק�譱�A�O�� &a.doc; �Ӽf�d�C
 	�аѾ\ <ulink
 	url="&url.books.fdp-primer;/index.html">FreeBSD Documentation Project Primer</ulink>
 	����o���㪺�оDzӸ`�C
 	���� <xref
 	linkend="contrib-general"/> �����Ъ���k�ϥ� &man.send-pr.1;
 	�Ӵ���s�����A�Ϊ̧ﵽ�{������� (���ȬO�ܤp����i�]�O�w�諸�I)�C</para>
     </sect2>
 
     <sect2>
       <title>���{����l�X���ק�</title>
 
       <indexterm><primary>FreeBSD-CURRENT</primary></indexterm>
 
       <para>�b�{����l�X�W�i��ק�μW�[�\��A�b�Y�ص{�פW�O�ݭn��h�ޥ����ơA
 	�åB�ٸ�z���ثe FreeBSD ���}�o�{���F�ѵ{�צ����C
 	���h�ؤ覡�i�H�o��Q�٧@ <quote>FreeBSD-CURRENT</quote>
 	�� FreeBSD �}�o�����C
 	�аѾ\ FreeBSD �ϥΤ�U�� <ulink url="
 	&url.books.handbook;/current-stable.html">��������</ulink> �A�ӤF�Ѩϥ� FreeBSD-CURRENT ���Ա��C</para>
 
       <para>�b�ª���l�X�W�i��ק�A�h�q�`�i���l�X�w�L�ɡA
 	�λP�s�������t���Ӥj�ӵL�k�Q���s��X�� FreeBSD ���C
 	�p�G�z���q &a.announce; �H�� &a.current; ���ܡA
 	�h�i�H�z�L���̨Ӥj�P�F�ѥثe���}�o���A�C</para>
 
       <para>�Y�z������q�H�̷s����l�X�Ӷi��z���ק�A
 	�h�U�@�B�n�����Ʊ��N�O���ͱz�ҭק諸 diff �ɡA
 	�ñN���o�� FreeBSD �����@�H���C�o���u�@�i�H�z�L &man.diff.1;
 	�R�O�ӧ����C</para>
 
       <para>���� patch �ɡA��ij &man.diff.1; �榡�ĥ� unified diff (�i�H�� <command>diff
         -u</command> �Ӳ���)�C���L�A�p�G�z�ק�F�j�q����l�X�A
         �h�ϥ� <command>diff -c</command> �ӥͦ��� context diff
         �� diff �i���e���\Ū�A�]�ӱ��˨ϥΡC�@��Ө��A�j���O�ĥ� <command>diff -ruN</command> �Y�i�C</para>
 
       <indexterm>
         <primary><command>diff</command></primary>
       </indexterm>
 
       <para>�Ҧp�G</para>
 
       <para>
 	<screen>&prompt.user; <userinput>diff -c oldfile newfile</userinput></screen>
 
 	��
 
 	<screen>&prompt.user; <userinput>diff -c -r olddir newdir</userinput></screen>
 
 	�N�|��S�w�ؿ��A���� context �� diff �ɡC</para>
 
       <para>�Ϊ̹��O...
         <screen>&prompt.user; <userinput>diff -u oldfile newfile</userinput></screen>
         ��
         <screen>&prompt.user; <userinput>diff -u -r olddir newdir</userinput></screen>
 
         �N���ͤ@�˪� diff �A���O�榡�� unified �C</para>
 
       <para>��h���Ӹ`�����A�аѾ\ &man.diff.1;�C</para>
 
       <para>�@���z�ϥ� &man.diff.1; �Ӳ��� diff �� (�i�H�ϥ�
 	&man.patch.1; �R�O�Ӵ��դ@�U)�A�N�i�H���楦�̡A�H�K�Q FreeBSD �����C
         �z�L�ϥ� <xref linkend="contrib-general"/>
 	���Ҥ��Ъ� &man.send-pr.1; �{���N�i�H�����o���u�@�C
 	�Ъ`�N�G���n�u�� diff �ɵo�� &a.hackers;�A
 	�_�h���̥i��|�Q��ѡI �ڭ̷|�D�`�P�E�z���檺�ק�
 	(�o�O�@�Ӹq�u�p���I)�F �]���ڭ̳��ܦ��A
 	�]�����ɤ��@�w����ߧY�ץ����D�A�� PR ��Ʈw�N�@���O���۳o�ǰO���A
 	�]���u�n���H���F�ɶ����̴N��Q�勵�F�C
 	�p�G�z�����D���i���]�A patch �A���n�ѤF�b���D�[�W
 	<literal>[PATCH]</literal> �ӱj�դ@�U�C</para>
 
       <indexterm>
         <primary><command>uuencode</command></primary>
       </indexterm>
 
       <para>�p�G�z�{���X�A (�Ҧp�W�B�R�ɮשΧ���ɦW)�A
 	�٥i�H�Ҽ{�ϥ�
 	<command>tar</command> �ӱN�ɮץ��]�A�M��� &man.uuencode.1;
 	�ӽs�X�C���~�A�]�i�H�� &man.shar.1; ���ͪ��覡�C</para>
 
       <para>�p�G�z���ק�i��s�b��b����ij�A�Ҧp�A
 	�z���T�w���������v���D�A�Ϊ̷Pı�ݭn�g�L���Y�檺�_�f�~�i�H�o�G���̡A
 	�h�������o�� &a.core;�A�Ӥ��O�z�L &man.send-pr.1; �ӵo�e�C
 	&a.core; �o�p�զ����j�h�q�� FreeBSD ����`�u�@�C
 	�ݭn�`�N���O�A�o�Ӥp�դ]�]���Q�����L�A
 	�]���u���b�D�`���n���ɭԡA�~���g�H���L�̡C</para>
 
       <para>�аѦ� &man.intro.9; �M &man.style.9; �H�F�����󼶼g�{���X�����氾�n�C
 	�Y��b�e�X�����{���X���e�A���F�ѳo�ǡA����j�a�ӻ��N�O���j�����U�C</para>
     </sect2>
 
     <sect2>
       <title>�s��l�X�έ��n���[�ȳn��]</title>
 
       <para>�p�G�z���ⴣ�ѳW�Ҹ��j����l�X�A�Ϊ̬� FreeBSD �W�[���n���s�\��A
 	�h�i�ॲ���N���̳z�L uuencode �i��s�X�A�ζǨ�Y�� Web ��
 	FTP ���I�A�H�K��h���H����o�쥦�C�p�G�z�S���o�˪��D���A
 	�Ш������ FreeBSD �l���׾´��X�A�ݬݬO�_���H�@�N���z��m���̡C</para>
 
       <para>���j�q����l�X�Ө��A�����v�����D�֩w�|�Q���X�C
 	FreeBSD �򥻨t�Τ�����ϥΪ����v�n���]�A�G</para>
 
       <orderedlist>
-  <indexterm><primary>BSD ���v�n��</primary></indexterm>
 	<listitem>
-	  <para>BSD ���v�C�ڭ̶ɦV��ϥγo�����v����l�X�A
+	  <para>BSD<indexterm><primary>BSD ���v�n��</primary></indexterm> ���v�C�ڭ̶ɦV��ϥγo�����v����l�X�A
 	    �]�����y�����[�h�l������z�A�]�ӧ����l�ްӷ~���~�ϥΡC
 	    FreeBSD �ä��Ϲ�ӷ~���q�ϥΥ�����l�X�A�ۤϡA
 	    �ڭ̿n���a���y�ӷ~���q�ϥΧڭ̪���l�X�A
 	    ���M�A�p�G���̭Y�̲ׯ�ⳡ����l�X�A���s���ص� FreeBSD �N��n�F�C</para>
 	</listitem>
 
 	<listitem>
-	  <indexterm><primary>GPL</primary><see>GNU General Public License</see></indexterm>
-
-	  <indexterm><primary>GNU General Public License</primary></indexterm>
-
-	  <para>GNU General Public License�A��²�� <quote>GPL</quote>�C
+	  <para>GNU General Public License�A��²�� <quote>GPL</quote>�C<indexterm><primary>GPL</primary><see>GNU General Public License</see></indexterm><indexterm><primary>GNU General Public License</primary></indexterm>
 	    �ڭ̨ä����w��ϥγo�˱��v����l�X�A
 	    �]���ӷ~���q�ϥΥ��ݭn����h���u�@�C���L�A�ѩ�ܦh�ϥ�
 	    GPL ���v����l�X�ثe�O�L�k�קK�� (compiler, assembler, text formatter����)
 	    �A�ڵ��ϥΩҦ��ĥγo�˱��v���n��O�ܤ��������C
 	    �ĥ� GPL ���v����l�X�|�Q����l�X���@�ǯS�w����m�A�Ҧp
 	    <filename>/sys/gnu</filename> ��
 	    <filename>/usr/src/gnu</filename>�A�H�K���ǻ{�� GPL
 	    �i��|�y���·Ъ��H����@�X�A�����P�_�C</para>
 	</listitem>
       </orderedlist>
 
       <para>�ϥΨ䥦���v����l�X�b�i�J FreeBSD ���e�����g�L�V�����_�f�M�Ҽ{�C
 	�ĥΥ]�t�Y�F����ӷ~���v����l�X�A�@��ӻ��|�Q�ڵ��A
 	���ڭ̹��y�o�ǭ�l�X���@�̡A�z�L�ۤv���޹D�ӵo�����̡C</para>
 
       <para>�Y�n�b�z�����G�W�[�J <quote>BSD-based</quote> ���v���ܡA
 	�Ч�U�C��r���C����l�X���̶}�l�����A
 	�åξA������r���� <literal>%%</literal> ��������r�C</para>
 
       <programlisting>Copyright (c) %%proper_years_here%%
         %%your_name_here%%, %%your_state%%  %%your_zip%%.
 	All rights reserved.
 
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions
 are met:
 1. Redistributions of source code 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 binary form 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 SOFTWARE IS PROVIDED BY %%your_name_here%% ``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 %%your_name_here%% 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 SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
         &#36;Id&#36;</programlisting>
 
       <para>���F��K�z���ϥΡA�b
 	<filename>/usr/share/examples/etc/bsd-style-copyright</filename>
 	�]�i�H��즹���v���ƥ��C</para>
     </sect2>
 
     <sect2>
       <title>�٧U����B�w��� Internet mirror</title>
 
       <para>�ڭ̫D�`�@�N�����U�اΦ������ءA�H�i�@�B�ݮi FreeBSD �p��
 	�A�]�����z������A���ڭ̳o�˪��q�u�V�O�~�������j�����N�I
 	���صw��]�D�`���n�A�]���o�˯�����U�ڭ̼W�[�i�䴩���w������A
 	�ӧڭ̤����ܦh�H�èS��������������ʸm�o�ǵw��C</para>
 
       <sect3>
 	<title><anchor id="donations"/>����</title>
 
 	<para>FreeBSD ����|�O�@�ӫD��Q���B���ҵ|�ŧK�v������|�A
 	  ���ҥH�|�إ߳o�Ӱ���|�A�O���F�� FreeBSD �p������i���i�[�C
 	  �]���Ӱ���|�� 501(c)3 ����A�@��Ө����ڵ�����|���ܡA�i�H�Kú�����p�����J�|�A
 	  �H�ά�ù�Ԧh�{���J�|�C�q�`��󦳽ҵ|�ŧK�v������i�殽�ت��ܡA
 	  �i�H����p�����J�����ҵ|���������B�C</para>
 
 	<para>�z�i�H��䲼�H���G
 	  <address>
 	    The FreeBSD Foundation
 	    <street>7321 Brockway Dr.</street>
 	    <city>Boulder</city>, <state>CO</state> <postcode>80303</postcode>
 	    <country>USA</country>
 	  </address>
 	</para>
 
 	<para>FreeBSD ����|�{�b�i�H�z�L PayPal �q���W�������ڡC
 	  �p�G�z�Q�V����|���ڡA�аѾ\ <ulink
 	  url="http://www.freebsdfoundation.org">FreeBSD ����|</ulink> �����C</para>
 
 	<para>���� FreeBSD ����|����h�Ա��A�i�H�b <ulink
 	  url="http://people.FreeBSD.org/~jdp/foundation/announcement.html">FreeBSD
 	  ����| -- ����</ulink> ���C�n�p������|�A
 	  �еo�e�q�l�l���
 	  <email>bod@FreeBSDFoundation.org</email>�C</para>
       </sect3>
 
       <sect3>
 	<title>���صw��</title>
   <indexterm><primary>����</primary></indexterm>
 
 	<para>FreeBSD �p���w�����H���إi�H�ϥΪ��w��C
 	  �p�G�z�����쮽�صw��A���pô <ulink
 	  url="&url.base;/donations/">�����p���H�줽��</ulink>�C</para>
       </sect3>
 
       <sect3>
 	<title>���� FreeBSD mirror ������</title>
 
 	<para>�ڭ��w��s�� FTP�BWWW ��
 	  <command>cvsup</command> mirror ���C�p�G�z�Ʊ榨���o�˪� mirror ���A
 	  �аѾ\ <ulink
 	  url="&url.articles.hubs;/index.html">�p��[�] FreeBSD mirror</ulink>
 	  �@��A�H�F�Ѷi�@�B�����p�C</para>
       </sect3>
     </sect2>
   </sect1>
 
 </article>
diff --git a/zh_TW.Big5/books/handbook/boot/chapter.xml b/zh_TW.Big5/books/handbook/boot/chapter.xml
index 5400fc8b2c..55e11f129a 100644
--- a/zh_TW.Big5/books/handbook/boot/chapter.xml
+++ b/zh_TW.Big5/books/handbook/boot/chapter.xml
@@ -1,816 +1,812 @@
 <?xml version="1.0" encoding="big5"?>
 <!--
      The FreeBSD Documentation Project
 
      $FreeBSD$
      Original revision: 1.62
 -->
 
 <chapter id="boot">
   <title>FreeBSD �}���y�{�g</title>
 
   <sect1 id="boot-synopsis">
     <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>Ū���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>&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>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>
+	    mode:<indexterm><primary>single-user mode</primary></indexterm></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
+	    disk, or <filename>kernel.old</filename><indexterm><primary><filename>kernel.old</filename></primary></indexterm> 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">
       <title>Kernel Boot Flags</title>
 
       <indexterm>
         <primary>kernel</primary>
         <secondary>bootflags</secondary>
       </indexterm>
 
       <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>
 
     <title>Device Hints</title>
 
     <indexterm>
       <primary>device.hints</primary>
     </indexterm>
 
     <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">
     <title>Init: Process Control Initialization</title>
 
     <indexterm>
       <primary><command>init</command></primary>
     </indexterm>
 
     <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">
 	<title>Resource Configuration (rc)</title>
 
 	<indexterm><primary>rc files</primary></indexterm>
 
 	<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>
diff --git a/zh_TW.Big5/books/handbook/cutting-edge/chapter.xml b/zh_TW.Big5/books/handbook/cutting-edge/chapter.xml
index d595f24567..08ea2f4dd1 100644
--- a/zh_TW.Big5/books/handbook/cutting-edge/chapter.xml
+++ b/zh_TW.Big5/books/handbook/cutting-edge/chapter.xml
@@ -1,1619 +1,1570 @@
 <?xml version="1.0" encoding="big5"?>
 <!--
      The FreeBSD Documentation Project
 
      $FreeBSD$
      Original revision: 1.225
 -->
 
 <chapter id="cutting-edge">
   <chapterinfo>
     <authorgroup>
       <author>
 	<firstname>Jim</firstname>
 	<surname>Mock</surname>
 	<contrib>Restructured, reorganized, and parts updated by </contrib>
       </author>
       <!-- Mar 2000 -->
     </authorgroup>
     <authorgroup>
       <author>
 	<firstname>Jordan</firstname>
 	<surname>Hubbard</surname>
 	<contrib>Original work by </contrib>
       </author>
       <author>
 	<firstname>Poul-Henning</firstname>
 	<surname>Kamp</surname>
       </author>
       <author>
 	<firstname>John</firstname>
 	<surname>Polstra</surname>
       </author>
       <author>
 	<firstname>Nik</firstname>
 	<surname>Clayton</surname>
       </author>
     </authorgroup>
     <!-- with feedback from various others -->
   </chapterinfo>
 
   <title>��s�B�ɯ� FreeBSD</title>
 
   <sect1 id="cutting-edge-synopsis">
     <title>���z</title>
 
     <para>&os; �O�ӫ���o�i���@�~�t�ΡC�����w�l�D�s�A�B��E���ϥΪ̦Ө��A
       ���ܦh��k�i�H�ϱz���t�λ��P��s���̷s���C
       �`�N�G�ëD�C�ӤH���A�X�o�򰵡I�@�����D�n�O��U�z�M�w�쩳�n��}�o�����A
       �άO�n�ϥθ�í�w�����X���C
       </para>
 
     <para>Ū���o���A�z�N�F�ѡJ</para>
 
     <itemizedlist>
       <listitem><para>&os.stable; �P &os.current;�@�o����䪺���P���B�F</para>
       </listitem>
       <listitem><para>�p��H
 	  <application>CSup</application>,
 	  <application>CVSup</application>,
 	  <application>CVS</application> ��
 	  <application>CTM</application> �ӧ�s�A���t��</para>
       </listitem>
       <listitem><para>�p��H <command>make buildworld</command>
       �����O�ӭ��s�sĶ�B�w�˾�� base system�C</para>
       </listitem>
 
     </itemizedlist>
 
     <para>�b�}�l�\Ū�o�����e�A�z�ݭn�J</para>
 
     <itemizedlist>
       <listitem><para>���]�n�A������(<xref linkend="advanced-networking"/>)�C
 	</para>
       </listitem>
       <listitem><para>���D�p��z�L port/package �w�˳n��(<xref
 	linkend="ports"/>)�C</para></listitem>
     </itemizedlist>
   </sect1>
 
   <sect1 id="current-stable">
     <title>&os.current; vs. &os.stable;</title>
     <indexterm><primary>-CURRENT</primary></indexterm>
     <indexterm><primary>-STABLE</primary></indexterm>
 
     <para>FreeBSD ����ӵo�i����G&os.current; ��
       &os.stable;�C���`�N�|���򤶲СA�ä��Х��̤��O�S�O�p���s�C
       �����A������ &os.current;�A���ۦA���� &os.stable;�C</para>
 
     <sect2 id="current">
       <title>�ϥγ̷s�� &os; CURRENT</title>
 
       <para>�o�̦A���j�աA&os.current; �O &os; �}�o�� <quote>�̫e�u</quote>�C
 	&os.current; �ϥΪ̶������j���޳N��O�A
 	�ӥB���ӭn����O�ۤv�ѨM�x�����t�ΰ��D�C  �Y�z�O &os; �s��A
 	����Цb�w�˫e�̦n���T��C</para>
 
       <sect3>
 	<title>����O &os.current;�H</title>
 	<indexterm><primary>snapshot</primary></indexterm>
 
 	<para>&os.current; �O &os; ���̷s���C���]�t�G
 	  ���b��o���q�B����ʽ誺�ק�B�L��ɴ�������A
 	  �o�ǪF��b�U�@������ relase �������i��|���A�]�i�ण�|�����C
 	  ���ަ��\�h &os; �}�o�̨C�ѳ��|�sĶ &os.current; source code�A
 	  �����ɳo�ǭ�l�X�O�L�k�sĶ���\�C  ���M�A�o�ǰ��D�q�`�|���ָѨM�A
 	  �� &os.current; �쩳�O�a�ӯE�T�άO�h�F�Q�n�Ϊ��s�\��B�ﵽ�A
 	  �o�I�D�n���M��z��s��l�X���ɾ�����өw�I</para>
       </sect3>
 
       <sect3>
 	<title>�ֻݭn &os.current;�H</title>
 
 	<para>&os.current; �A�X�U�C�o�T���H�G</para>
 
 	<orderedlist>
 	  <listitem>
 	    <para>&os; ���s�����G�n���M�`�� source tree ���Y�@�����A
 	      �H�λ{���O���� <quote>current(�̷s���A)</quote>
 	      ������ݨD���H�C</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>&os; ���s�����G���F�T�O &os.current;
 	      ������i��a�����b��í�w�����A�A
 	      �ӥD�ʪ�ɶ��ѨM���D�����ժ̡C  ���~�A�٦��� &os;
 	      �ണ�X�����ij�H�Χﵽ��V�A�ô��X patch �ץ��ɪ��H�C</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>�u�O���ߩΪ̷Q�Ѧ�(��p�A�u�O<emphasis>�\Ū</emphasis>�A
 	      �ӫD����)���H�C
 	      �o�ǤH���ɤ]�|���ǵ��ѡA�ΰ^�m��l�X�C</para>
 	  </listitem>
 	</orderedlist>
       </sect3>
 
       <sect3>
 	<title>&os.current; <emphasis>��O</emphasis> ����H</title>
 
 	<orderedlist>
 	  <listitem>
 	    <para>�l�D�̷s�\��C  ť���̭����ǫܻŪ��s�\��A
 	      �çƱ榨���z�P�򪺤H���Ĥ@�ӹ��ժ��H�A
 	      �]���N &os.current; �������o�m�A�������|�C
 	      ���ޡA�z����]�������A�Ѩ�̷s���\��A
 	      ���o�]�N���ۭY�X�{�s�� bug �ɡA�z�]�O������ġC</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>�״_ bug ���t���k�C  �]�� &os.current;
 	      �����󪩥��b�״_�w�� bug ���P�ɡA�S�i��|���ͷs�� bug�C
 	      </para>
 	  </listitem>
 
 	  <listitem>
 	    <para>�L�Ҥ��b�� <quote>officially supported</quote>�C
 	      �ڭ̷|�ɤO��U�W�z &os.current; �����T�����O��
 	      <quote>legitimate</quote> �ϥΪ̡A
 	      ���ڭ�<emphasis>�S�ɶ�</emphasis>���L�̴��ѧ޳N�䴩�C
 	      �o���N���ڭ̫ܴc�H�A�άO���Q���U�H(�Y�O���ܡA
 	      �ڭ̤]���|�� &os; �V�O�F)
 	      �A��b�O�]���ڭ̤����F�N�A�L�k�C�Ѧ^���ƦʭӰ��D�A
 	      <emphasis>�ӦP��</emphasis>�~��}�o &os;�C
 	      �i�H�T�w���@�I�N�O�A
 	      �b�ﵽ &os; �άO�^���j�q��������X�����D�����A
 	      �Y�n���ӿ�ܪ��ܡA�}�o�̷|��ܫe�̡C</para>
 	  </listitem>
 	</orderedlist>
       </sect3>
 
       <sect3>
 	<title>�ϥ� &os.current;</title>
 
-	<indexterm>
-	  <primary>-CURRENT</primary>
-	  <secondary>using</secondary>
-	</indexterm>
 	<orderedlist>
 	  <listitem>
-	    <para>�[�J &a.current.name; �� &a.cvsall.name; �׾¡C
+	    <para>�[�J &a.current.name;<indexterm><primary>-CURRENT</primary><secondary>using</secondary></indexterm> �� &a.cvsall.name; �׾¡C
 	      �o����u�O�ӫ�ij�A�]�O <emphasis>����</emphasis> �@���C
 	      �Y�z�S�q�\ <emphasis>&a.current.name;</emphasis>
 	      �A����N�|���L�O�H��ثe�t�Ϊ��A�������A�Ӭ\�Ӧb�O�H�w�Ѫ����D�C
 	      �󭫭n���O�A�i��|�����@�ǹ�v���Һިt�Φw�M�۷����n�����i�C
 	      </para>
 
 	    <para>�b &a.cvsall.name; �W�h�i�H�ݨ�C�� commit �����A
 	      �]���o�ǰO���|�s�a�v�T��L������T�C</para>
 
 	    <para>�n�q�\�o�ǽ׾©Ψ�L�׾¡A�аѦ� &a.mailman.lists.link;
 	      ���I��Q�q�\�������Y�i�C  �ܩ��L����B�J�p��i��A
 	      �b���̷|�������C</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>�q &os; <link linkend="mirrors">mirror ��</link>
 	      ���o��l�X�C  ����ؤ覡�i�H�F���G</para>
 
 	    <orderedlist>
-              <indexterm>
-                <primary><command>cvsup</command></primary>
-              </indexterm>
-              <indexterm>
-                <primary><command>cron</command></primary>
-              </indexterm>
-              <indexterm>
-	        <primary>-CURRENT</primary>
-		<secondary>Syncing with <application>CVSup</application></secondary>
-	      </indexterm>
-
 	      <listitem>
-		<para>�H <link linkend="cvsup">csup</link> ��
+		<para>�H <link linkend="cvsup">csup</link><indexterm><primary><command>cvsup</command></primary></indexterm> ��
 		  <link linkend="cvsup">cvsup</link> �{���f�t���
 		  <filename>/usr/share/examples/cvsup</filename> �ɦW��
 		  <filename>standard-supfile</filename> ��
 		  <filename>supfile</filename>�C
 		  �o�O�j�a�̱`���˪��覡�A�]�����i�H���z���� tree ����^�ӡA
 		  ����N�u������s�������Y�i�C
 		  ���~�A�\�h�H�|�� <command>csup</command> ��
 		  <command>cvsup</command> ���
-		  <command>cron</command> �H�w���۰ʧ�s�C
+		  <command>cron</command><indexterm><primary><command>cron</command></primary></indexterm> �H�w���۰ʧ�s�C
  		  �z���n�ۭq�e�z�� <filename>supfile</filename> �d���ɡA
 		  �ðw��ۨ��������ҥH�վ� <link linkend="cvsup">csup</link>
-		  �� <link linkend="cvsup">cvsup</link> �����]�w�C</para>
+		  �� <link linkend="cvsup">cvsup</link><indexterm><primary>-CURRENT</primary><secondary>Syncing with <application>CVSup</application></secondary></indexterm> �����]�w�C</para>
 	      </listitem>
 
 	      <listitem>
-		<indexterm>
-		  <primary>-CURRENT</primary>
-		  <secondary>Syncing with CTM</secondary>
-		</indexterm>
-
 		<para>�ϥ� <application><link
-		  linkend="ctm">CTM</link></application> �u��C  �Y�������Ҥ���
+		  linkend="ctm">CTM</link></application><indexterm><primary>-CURRENT</primary><secondary>Syncing with CTM</secondary></indexterm> �u��C  �Y�������Ҥ���
 		  (�W���O�ζQ�A�Υu��� email �Ӥw)
 		  <application>CTM</application> �|����A�X�z���ݨD�C
 		  �M�ӡA�o�]���@�Ǫ�ij�åB�`���@�Ǧ����D���ɮסC  �]���A
 		  �ܤ֤H�|�Υ��C  �o�]���w�F��������̿�o�ӧ�s�覡�C
 		  �Y�O�ϥ� 9600&nbsp;bps modem ���W�e��j���W���̡A��ij�ϥ�
 		  <application><link linkend="cvsup">CVSup</link></application>
 		  �C</para>
 	      </listitem>
 	    </orderedlist>
 	  </listitem>
 
 	  <listitem>
 	    <para>�Y�� source code �O�n�ΨӶ]���A�Ӥ��ȥu�O�ݬݦӤw�A
 	      ����N�� <emphasis>���</emphasis> &os.current;�A�Ӥ��n�u�쳡���C
 	      �]���j������ source code ���|�̨ۨ��L source code ���`�����A
 	      �Y�O�z�u�sĶ�䤤�@�����A�O�ҷ|�ܳ·СC</para>
 
-	  <indexterm>
-	    <primary>-CURRENT</primary>
-	    <secondary>compiling</secondary>
-	  </indexterm>
-	    <para>�b�sĶ &os.current; ���e�A�ХJ�Ӿ\Ū
+	    <para>�b�sĶ &os.current;<indexterm><primary>-CURRENT</primary><secondary>compiling</secondary></indexterm> ���e�A�ХJ�Ӿ\Ū
 	      <filename>/usr/src</filename> ���� <filename>Makefile</filename>�C
 	      ���ޥu�O�ɯų����F��Ӥw�A�z�ܤ֤]�n�� <link linkend="makeworld">
 	      �˷s�� kernel �H�έ��s�sĶ world</link>�C  ���~�A�h�h�\Ū
 	      &a.current; �H�� <filename>/usr/src/UPDATING</filename>
 	      �]�O�������A
 	      �~�ા�D�ثe�i�׬O��˥H�ΤU�@���|������s�F��C</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>����I�Y�z���b�] &os.current;�A
 	      �ڭ̫ܷQ���D�z��󥦪��Q�k�O����A�ר�O�[�j���ǥ\��A
 	      �θӭץ����ǿ��~����ij�C  �p�G�z�b��ij�ɯ���W�����{���X���ܡA
 	      ���u�O�ӴΤF�I</para>
 	  </listitem>
 	</orderedlist>
       </sect3>
     </sect2>
 
     <sect2 id="stable">
       <title>�ϥγ̷s�� &os; STABLE</title>
 
       <sect3>
 	<title>����O &os.stable;�H</title>
 	<indexterm><primary>-STABLE</primary></indexterm>
 
 	<para>&os.stable; �O�ڭ̪��}�o����A�D�n���o�檩�N�Ѧ��ӨӡC
 	  �o�Ӥ���|�H���P�t�ק@�ק��ܤơA�åB���]�o�ǬO�Ĥ@���i�J &os.current;
 	  �i����աC  �M�ӡA�o <emphasis>���M</emphasis> �ݩ�}�o��������A
 	  �]�N�O���b�Y�ǮɭԡA&os.stable; �i��|�B�]�i�ण�|�ŦX�@�ǯS���ݨD�C
 	  ���u���L�O�t�@�Ӷ}�o����Ӥw�A�i�ण�ӾA�X�@��ϥΪ̡C</para>
       </sect3>
 
       <sect3>
 	<title>�ֻݭn &os.stable;�H</title>
 
 	<para>�Y�z������h�l�ܡB�^�m FreeBSD �}�o�L�{�Χ@�ǰ^�m�A
 	  �ר�O�|�� FreeBSD ���U�Ӫ� <quote>�����</quote> �o�榳���A
 	  ���ӦҼ{�ĥ� &os.stable;�C</para>
 
 	<para>���M�w���|�}���׸ɤ]�|�i�J &os.stable; ����A
 	  �������ȶȦ]���� <emphasis>�ݭn</emphasis> �h�� &os.stable;�C
 	  FreeBSD �C�� security advisory(�w�����i)
 	  ���|�ѻ��p��h�״_������v�T������
 	  <footnote><para>�M�ӡA�o�]���@�w�O���T�A�ڭ̤��i��û��䴩 FreeBSD
 	    ���骺�U�صo�檩���A���ިC�ӵo�檩�o�G����A�����|����䴩�Ʀ~���[�C
 	    �Y���A�� FreeBSD �ثe����ª����䴩�F���Ӹ`�A�аѾ\ <ulink
   	    url="&url.base;/security/">http://www.FreeBSD.org/security/</ulink>
 	    �C</para>
 	  </footnote>
 	  �A�Y�Ȧ]���w���]���ӥh�ĥζ}�o����A���M�|�ѨM�{���w�����D�A
 	  ���]�i��a�Ӥ@�Ǽ��ê����D�C</para>
 
 	<para>���ާڭ̺ɤO�T�O &os.stable; ����b����ɭԧ��ॿ�T�sĶ�B�B�@�A
 	  ���S�H�����O���H�ɳ��i�H�ŦX�W�z�ت��C  ���~�A���M��l�X�b�i�J
 	  &os.stable; ���e�A���|���b &os.current; �}�o�����A���ϥ� &os.current;
 	  ���H�������� &os.stable; �ϥΪ̨Ӫ��֡A�ҥH�q�`���ǰ��D�A�i��b
 	  &os.current; ����S�H�`�N��A�H�� &os.stable;
 	  �ϥΪ̪��s�x�ϥΤ~�|�B�{�C</para>
 
 	<para>�ѩ�W�z�o�Dzz�ѡA�ڭ�<emphasis>�ä�����</emphasis> ���ذl�H
 	  &os.stable;�A�ӥB�󭫭n���O�A�O�b��l�X�|���g������դ��e�A
 	  �N�İʧ� production server �ಾ�� &os.stable; ���ҡC</para>
 
 	<para>�Y�z�S���o�Ǧh���ɶ��B�믫���ܡA�����˱z�ϥγ̷s�� FreeBSD
 	  �o�檩�Y�i�A�ñĥΨ�Ҵ��Ѫ� binary ��s����ӧ����ɯ��ಾ�C</para>
       </sect3>
 
       <sect3>
 	<title>�ϥ� &os.stable;</title>
 
 	<orderedlist>
-	  <indexterm>
-	    <primary>-STABLE</primary>
-	    <secondary>using</secondary>
-	  </indexterm>
-
 	  <listitem>
-	    <para>�q�\ &a.stable.name; list�C  �i�H���z�H���A�� &os.stable;
+	    <para>�q�\ &a.stable.name;<indexterm><primary>-STABLE</primary><secondary>using</secondary></indexterm> list�C  �i�H���z�H���A�� &os.stable;
 	      ���n��sĶ�ɪ��ۨ����Y�A�H�Ψ�L�ݯS�O�`�N�����D�C
 	      �}�o�̦b�Ҽ{�@�Ǧ���ij���ץ��Χ�s�ɡA�N�|���b�o�̵o�H�����A
 	      ���ϥΪ̦����|�i�H�����A
 	      �ݥL�̹�Ҵ������O�_�������ij�ΰ��D�C</para>
 
 	    <para>�� &a.cvsall.name; list �o��i�H�ݨ�C�� commit log�A
 	      �䤤�]�A�F�\�h���֪���T�A�Ҧp�@�ǥi��o�ͪ���ڮ��������C</para>
 
 	    <para>�Q�n�[�J�o�dzq�H�׾ª��ܡA�u�n�� &a.mailman.lists.link;
 	      �I�U�Q�q�\�� list �Y�i�C  ��l���B�J�b�����W�|�������C</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>�Y����n�w�ˤ@�ӥ��s���t�ΡA�åB�Ʊ��  &os.stable;
 	      �C��w���� snapshot�A����аѾ\ <ulink
 	      url="&url.base;/snapshots/">Snapshots</ulink> �����H�A�Ѭ����Ӹ`�C
 	      ���~�A�]�i�q <link linkend="mirrors">mirror ��</link>
 	      �Ӧw�˳̷s�� &os.stable; �o�檩�A�óz�L�U�C���������ӧ�s��̷s��
 	      &os.stable; ��l�X�C</para>
 
 	    <para>�Y�w�˪��O &os; �H�e�������A�ӷQ�z�L��l�X�覡�ӤɯšA
 	      ����]�O�i�H�Q�� &os; <link linkend="mirrors">mirror ��</link>
 	      �ӧ����C  �H�U���Ш�ؤ覡�G</para>
 
 	    <orderedlist>
-	      <indexterm>
-		<primary><command>cvsup</command></primary>
-	      </indexterm>
-	      <indexterm>
-		<primary><command>cron</command></primary>
-	      </indexterm>
-	      <indexterm>
-	        <primary>-STABLE</primary>
-		<secondary>syncing with <application>CVSup</application></secondary>
-	      </indexterm>
 	      <listitem>
-		<para>�H <link linkend="cvsup">csup</link> ��
+		<para>�H <link linkend="cvsup">csup</link><indexterm><primary><command>cvsup</command></primary></indexterm> ��
 		  <link linkend="cvsup">cvsup</link> �{���f�t���
 		  <filename>/usr/share/examples/cvsup</filename> �ɦW��
 		  <filename>stable-supfile</filename> ��
 		  <filename>supfile</filename>�C  �o�O�j�a�̱`���˪��覡�A
 		  �]�����i�H���A���� tree ����^�ӡA
 		  ����N�u������s�������Y�i�C
 		  ���~�A�\�h�H�|�� <command>csup</command> ��
-		  <command>cvsup</command> ��� <command>cron</command>
+		  <command>cvsup</command> ��� <command>cron</command><indexterm><primary><command>cron</command></primary></indexterm>
 		  �H�w���۰ʧ�s�C  �z���n�ۭq�e�z��
 		  <filename>supfile</filename> �d���ɡA�ðw��ۨ��������ҥH�վ�
 		  <link linkend="cvsup">csup</link> ��
-		  <link linkend="cvsup">cvsup</link> �����]�w�C</para>
+		  <link linkend="cvsup">cvsup</link><indexterm><primary>-STABLE</primary><secondary>syncing with <application>CVSup</application></secondary></indexterm> �����]�w�C</para>
 	      </listitem>
 
 	      <listitem>
-		<indexterm>
-		  <primary>-STABLE</primary>
-		  <secondary>syncing with CTM</secondary>
-		</indexterm>
-
 		<para>�ϥ� <application><link
-		  linkend="ctm">CTM</link></application> ��s�u��C
+		  linkend="ctm">CTM</link></application><indexterm><primary>-STABLE</primary><secondary>syncing with CTM</secondary></indexterm> ��s�u��C
 		  �Y�������֩κ����O�ζQ�A����i�H�Ҽ{�ĥΡC</para>
 	      </listitem>
 	   </orderedlist>
 	 </listitem>
 
 	  <listitem>
 	    <para>�@��Ө��A�Y�`�ݦs���̷s��l�X�A�Ӥ��p�������W�e���ܡA
 	      �i�H�ϥ� <command>csup</command> �� <command>cvsup</command>
 	      �� <command>ftp</command>�C  �_�h�A�N�Ҽ{
 	      <application>CTM</application>�C</para>
 	  </listitem>
 
 	  <listitem>
-	    <indexterm>
-	      <primary>-STABLE</primary>
-	      <secondary>compiling</secondary>
-	    </indexterm>
-
-	    <para>�b�sĶ &os.stable; ���e�A�Х��J�Ӿ\Ū
+	    <para>�b�sĶ &os.stable;<indexterm><primary>-STABLE</primary><secondary>compiling</secondary></indexterm> ���e�A�Х��J�Ӿ\Ū
 	      <filename>/usr/src</filename> ���� <filename>Makefile</filename>
 	      �ɡC  ���ޥu�O�ɯų����F��Ӥw�A�z�ܤ֤]�n�� <link
 	      linkend="makeworld">�˷s�� kernel �H�έ��s�sĶ world</link>�C
 	      ���~�A�h�h�\Ū &a.stable; �H��
 	      <filename>/usr/src/UPDATING</filename> �]�O���ƪ��A
 	      �o�ˤ~�ા�D�ثe�i�׬O��ˡA�H�ΤU�@���|�����Ƿs�F��C</para>
 	  </listitem>
 	</orderedlist>
       </sect3>
     </sect2>
   </sect1>
 
   <sect1 id="synching">
     <title>��s�A�� Source</title>
 
     <para>&os; �p����l�X���\�h�z�L����(�� email)���覡�ӧ�s�A
       �L�׬O��s���@�����A�o�ǥ��ѱz�ۦ�M�w�C  �ڭ̥D�n���Ѫ��O <link
       linkend="anoncvs">Anonymous CVS</link>�B<link linkend="cvsup">CVSup</link>
       �B<link linkend="ctm">CTM</link>�C</para>
 
     <warning>
       <para>���M�i�H�u��s������l�X�A���ߤ@�䴩����s�y�{�O��s��� tree�A
 	�åB���s userland(��p�G�ѨϥΪ̥h���檺�Ҧ��{���A���O
 	<filename>/bin</filename>�B<filename>/sbin</filename> �����{��)�H��
 	kernel ��l�X�C
         �Y�u��s������ source tree�B�Υu�� kernel �����B�Υu�� userland
 	�����A�q�`�|�y���@�ǿ��~�A���O�G�sĶ���~�Bkernel panic�B��Ʒ��l��
 	�C</para>
     </warning>
 
     <indexterm>
       <primary>CVS</primary>
       <secondary>anonymous</secondary>
     </indexterm>
 
     <para><application>Anonymous CVS</application> ��
       <application>CVSup</application> ���O�� <emphasis>pull</emphasis>
       �Ҧ��ӧ�s��l�X�C  �H <application>CVSup</application> ���ҡA
       �ϥΪ�(�� <command>cron</command> script)�|���� <command>cvsup</command>
       �{���A��̷|�P�Y�@�x <command>cvsupd</command> ���A���@�Ǥ��ʡA
       �H��s������l�X�ɮסC  �z�Ҧ����s�|�O���ɳ̷s���A
       �ӥB�u�|����ݧ�s�������C  ���~�A�]�i�H�ܻ��P�h�]�w�n��s���d��C
       ��s�|�Ѧ��A���򥻾���蠟��A��X���ɱz�һݭn����s�ɮ׵��A�C
       <application>Anonymous CVS</application> �������۹��
       <application>CVSup</application> �ӱo��²��ǡA�]�����u�O
       <application>CVS</application> �������Ӥw�A�@�����A�i�q���ݪ�
       CVS repository ���X�̷s��l�X�C  �M�� <application>CVSup</application>
       �b�o�譱�|�󦳮IJv�A���L <application>Anonymous CVS</application>
       ��s��Ө��A�O�ΰ_�Ӥ��²��C</para>
 
     <indexterm>
       <primary><application>CTM</application></primary>
     </indexterm>
     <para>�t�@�ؤ覡�h�O <application>CTM</application>�C
       ���ä��O�H��ͦ������Ӥ��z�Ҿ֦��� sources �M���A���W�� sources
       �άO�z���o����s�����C  �ۤϪ��A�|���@�� script
       �ɱM���Ψӿ����ܧ�L���ɮסA�o�ӵ{���O�� CTM ���A���Ӱ���A
       �C�ѷ|���Ʀ��A�ç�⦸����������ܧ�L���ɮץ[�H���Y�A
       �õ����̤@�ӧǸ��A�M��N�[�H�s�X(�u�� printable ASCII �r��)�A
       �åH email ���覡�H�X�C  ���z���쥦���ɭԡA�o�� <quote>CTM deltas</quote>
       �N�i�H�� &man.ctm.rmail.1; �{���ӳB�z�A�ӵ{���|�۰ʸѽX�B�T�{�B
       �M�γo���ܧ�C �o�{�Ǥ� <application>CVSup</application> �ӻ��O�ֱo�h�F�A
       �ӥB�A�o�ӼҦ���ڭ̪����A���ӻ��O������P���A�]���o�O�@��
       <emphasis>push</emphasis> ���Ҧ��A�ӫD <emphasis>pull</emphasis>
       ���Ҧ��C</para>
 
     <para>���M�A�o�˰��]�|�a�Ӥ@�Ǥ��K�C  �Y���p�ߧ�z�������{���M�����F�A
       <application>CVSup</application> �|�����X�ӡA�æ۰ʬ��z�⤣���������ɻ��C
       <application>CTM</application> �ä��|���z���o�ǰʧ@�C
       �Y�M���F�z������ source (�ӥB�S�ƥ�)�A�z�i�H�q�Y�}�l(�q�̷s�� CVS
       <quote>base delta</quote>)�å� <application>CTM</application> �ӭ��إ���
       �A�άO�� <application>Anonymous CVS</application> �ӧ����A
       �u�n�⤣���T���a��屼�A�A���s���P�B���ʧ@�Y�i�C</para>
   </sect1>
 
   <sect1 id="makeworld">
     <title>���s�sĶ <quote>world</quote></title>
 
     <indexterm>
       <primary>Rebuilding <quote>world</quote></primary>
     </indexterm>
     <para>�b��s &os; �� source tree ��̷s����(�L�׬O &os.stable;�B
       &os.current; ����)�A���U�ӴN�i�H�γo�� source tree �ӭ��s�sĶ�t��
       �C</para>
 
     <warning>
       <title>���n�ƥ�</title>
 
       <para>�b�@����j�ʧ@ <emphasis>���e</emphasis>
 	�n�O�o����t�Χ@�ƥ������n�ʵL���j�աC ���ޭ��s�sĶ world �O
 	(�u�n���Ӥ����ܥh�@����)�@���²�檺�Ʊ��A���X���]�O�b�����K���C
 	�t�~�A�O�H�b source tree ���V�d�V�����~�A�]�i��|�y���t�εL�k�}��
 	�C</para>
 
       <para>�нT�{�ۤv�w�@�������ƥ��A�åB���䦳 fixit �Ϥ��ζ}�����СC
 	�z�i��û��]�Τ���o�ǪF��A
 	���w���Ĥ@�`��ƫỡ��p�ӱo�n�a�I</para>
     </warning>
 
     <warning>
       <title>�q�\������ Mailing List</title>
 
       <indexterm><primary>mailing list</primary></indexterm>
       <para>&os.stable; �H�� &os.current; ����A����W�N�O�ݩ� <emphasis>
 	�}�o���q</emphasis>�C  �� &os; �@�^�m���]���O�H�A�����]�|�ǿ��~�C</para>
 
       <para>���ɭԳo�ǿ��~�õL�jê�A�u�O�|���t�β��ͷs�����~ĵ�i�Ӥw�C
 	���ɫh�O�a���A�i��|�ɭP����}�����ɮרt�Ϊ����l(�Χ��V)�C</para>
 
       <para>�Y�J���������D�A�K�ʼ��D�� <quote>heads up(�`�N)</quote>
 	�}�Y���H������� mailing list�A�����M�����D�I�H�η|�v�T���Ǩt�ΡC
 	�b���D��ѨM��A�A�K���D�� <quote>all clear(�w�ѨM)</quote>
 	�}�Y���n���H�C</para>
 
       <para>�Y�Ϊ��O &os.stable; �� &os.current;�A�o�S���\Ū &a.stable; ��
 	&a.current; ���Q�סA����|�O�ۧ�·ЦӤw�C</para>
     </warning>
 
     <warning>
       <title>���n�� <command>make world</command></title>
 
       <para>�@�玲�����¤�󳣷|��ij���ϥ� <command>make world</command>�C
 	�o�˰��|���L�@�ǭ��n�B�J�A��ij�u���b�A���D�ۤv�b�@����A�A�o�򰵡C
 	�b���j�h�ƪ����p�U�A�Ф��n�å� <command>make world</command>�A
 	�Ӹӧ�ΤU�����Ъ��覡�C</para>
     </warning>
 
     <sect2>
       <title>��s�t�Ϊ��зǤ覡</title>
 
       <para>�n�ɯŨt�Ϋe�A�@�w�n���d�\ <filename>/usr/src/UPDATING</filename>
 	���A�H�A�� buildworld ���e�ݭn�@���ǨƱ��Ϊ`�N�ƶ��A
 	�M��~�ΤU�C�B�J�G</para>
 
       <screen>&prompt.root; <userinput>make buildworld</userinput>
 &prompt.root; <userinput>make buildkernel</userinput>
 &prompt.root; <userinput>make installkernel</userinput>
 &prompt.root; <userinput>reboot</userinput></screen>
 
       <note>
 	<para>�b�ּƪ��p�A�i��ݭn���b <maketarget>buildworld</maketarget>
 	  �B�J���e���@ <command>mergemaster -p</command> �~�৹���C
 	  �ܩ��ɻݭn�Τ��ݭn�A�аѾ\ <filename>UPDATING</filename> ���������C
 	  �@��ӻ��A�u�n���O�i��󪩸�(major)�� &os; �����ɯšA
 	  �N�i���L�o�B�J�C</para>
       </note>
 
       <para>���� <maketarget>installkernel</maketarget> ����A�ݭn���}���ä���
 	single user �Ҧ�(�|�ҡG�]�i�H�b loader ���ܲŸ��᭱�[�W
 	<command>boot -s</command>)�C  ���U�Ӱ���G</para>
 
       <screen>&prompt.root; <userinput>mergemaster -p</userinput>
 &prompt.root; <userinput>make installworld</userinput>
 &prompt.root; <userinput>mergemaster</userinput>
 &prompt.root; <userinput>reboot</userinput></screen>
 
       <warning>
 	<title>Read Further Explanations</title>
 
 	<para>�W�z�B�J�u�O��U�z�ɯŪ�²�满���Ӥw�A�Y�n�M���A�ѨC�@�B�J�A
 	  �ר�O�Y���ۦ楴�y kernel �]�w�A�N��Ӿ\Ū�U�������e�C</para>
       </warning>
     </sect2>
 
     <sect2>
       <title>�\Ū <filename>/usr/src/UPDATING</filename></title>
 
       <para>�b�@����Ʊ����e�A�аȥ����\Ū
 	<filename>/usr/src/UPDATING</filename> (�Φb source code �����������)
 	�C  �o�����|�g��i��D�J�����D�A�Ϋ��w���Ƿ|���檺���O���Ǭ���C
 	�p�G�A�����{�b�� <filename>UPDATING</filename>
 	���P�o�䪺�y�z���Ĭ�B�٬ޤ��B�A����ХH�����W��
 	<filename>UPDATING</filename> ���ǡC</para>
 
       <important>
 	<para>�M�ӡA�p�P���e�ҭz�A���u�a�\Ū <filename>UPDATING</filename>
 	  �ä��৹�����N mailing list�C  �o��̳��O���ɪ��A�Ӥ��۱ƥ��C</para>
       </important>
     </sect2>
 
     <sect2>
       <title>�ˬd <filename>/etc/make.conf</filename></title>
       <indexterm>
         <primary><filename>make.conf</filename></primary>
       </indexterm>
 
       <para>�ˬd
 	<filename>/usr/share/examples/etc/make.conf</filename>
 	�H��
 	<filename>/etc/make.conf</filename>�C  �Ĥ@�����D�O�@�Ǩt�ιw�]��
 	&ndash; ���L�A�j�������Q���Ѱ_�ӡC  ���F�b���s�sĶ�ɯ���ϥγo�ǡA
 	�Ч�o�dz]�w�[�� <filename>/etc/make.conf</filename>�C  �Ъ`�N�b
 	<filename>/etc/make.conf</filename> ������]�w�]�|�v�T��C���ϥ�
 	<command>make</command> �����G�A
 	�]���]�w�@�ǾA�X�ۤv�t�Ϊ��ﶵ�|�O�������@�k�C</para>
 
       <para>�@��ϥΪ̳q�`�|�q
 	<filename>/usr/share/examples/etc/make.conf</filename> �ƻs
 	<makevar>CFLAGS</makevar> �H�� <makevar>NO_PROFILE</makevar>
 	�������]�w�� <filename>/etc/make.conf</filename>�A�øѰ��������ѦL�O
 	�C</para>
 
       <para>���~�A�]�i�H�ոլݨ�L�]�w (<makevar>COPTFLAGS</makevar>�B
 	<makevar>NOPORTDOCS</makevar> ����)�A�O�_�ŦX�ۤv�һݡC</para>
     </sect2>
 
     <sect2>
       <title>��s <filename>/etc</filename> �����]�w��</title>
 
       <para>�b <filename>/etc</filename> �ؿ��|���t�Ϊ������]�w�ɡA
 	�H�ζ}���ɪ��U���A�ȱҰ� script�C  ���� script �H FreeBSD
 	���������P�Ӧ��Ǯt���C</para>
 
       <para>�䤤���dz]�w�ɷ|�b�C��B�@���t�θ̤]�|�Ψ�C  �ר�O
 	<filename>/etc/group</filename>�C</para>
 
       <para>���ɭԦb <command>make installworld</command> �w�˹L�{���A
 	�|�ݭn���إ߬Y�ǯS�w�b���θs�աC  �b�i��ɯŤ��e�A���̥i��ä��s�b�A
 	�]���ɯŮɴN�|�y�����D�C  ���ɭ� <command>make buildworld</command>
 	�|���ˬd�o�ǩһݪ��b���θs�լO�_�w���s�b�C</para>
 
       <para>�|�ӳo�˪��Ҥl�A���O�Y���ɯŤ��ᥲ���s�W <username>smmsp</username>
 	�b���C  �Y�ϥΪ̩|���s�W�ӱb���N�n�����ɯžާ@���ܡA
 	�|�b &man.mtree.8; ���իإ� <filename>/var/spool/clientmqueue</filename>
 	�ɵo�ͥ��ѡC</para>
 
       <para>�Ѫk�O�b buildworld ���q���e�A������ &man.mergemaster.8; �÷f�t
 	<option>-p</option> �ﶵ�C  ���|��墨�ǰ���
 	<maketarget>buildworld</maketarget> ��
 	<maketarget>installworld</maketarget> �һݤ�����]�w�ɡC
 	�Y�A�ҥΪ��O���������䴩 <option>-p</option> ��
 	<command>mergemaster</command> �����A���򪽱��ϥ� source tree
 	�����s���Y�i�G</para>
 
       <screen>&prompt.root; <userinput>cd /usr/src/usr.sbin/mergemaster</userinput>
 &prompt.root; <userinput>./mergemaster.sh -p</userinput></screen>
 
       <tip>
 	<para>�Y�z�O�����g(paranoid)�A
 	  �i�H���U���o�˥h�յ��ˬd�t�ΤW�������ɮ��ݩ�w��W�γQ�R�����s��
 	  �G</para>
 
 	<screen>&prompt.root; <userinput>find / -group <replaceable>GID</replaceable> -print</userinput></screen>
 
 	<para>�o�|��ܩҦ��ŦX�n�䪺 <replaceable>GID</replaceable> �s��
 	  (�i�H�O�s�զW�١A�Ϊ̬O�s�ժ��Ʀr�N��)���Ҧ��ɮסC</para>
       </tip>
     </sect2>
 
     <sect2 id="makeworld-singleuser">
       <title>������ Single User �Ҧ�</title>
       <indexterm><primary>single-user mode</primary></indexterm>
 
       <para>�z�i��|�Q�b single user �Ҧ��U�sĶ�t�ΡC
 	���F�i�H�����֧������~�A�w�˹L�{���N�|�o�A�\�h���n���t���ɮסA
 	�]�A�Ҧ��t�� binaries�Blibraries�Binclude �ɮ׵��C
 	�Y�b�B�@�����t��(�ר䦳�\�h�ϥΪ̦b�Ϊ��ɭ�)�����o���ɮסA
 	��²���O�ۧ�·Ъ��@�k�C</para>
 
       <indexterm><primary>multi-user mode</primary></indexterm>
       <para>�t�@�ؼҦ��O���b multi-user �Ҧ��U�sĶ�n�t�ΡA�M��A���� single user
 	�Ҧ��h�w�ˡC  �Y�z������w�o�ؤ覡�A�u�ݦb build(�sĶ�L�{) ��������A
 	�A�h����U�����B�J�Y�i�C  �@����i���� single user �Ҧ��ɡA�A�h����
 	<maketarget>installkernel</maketarget> ��
 	<maketarget>installworld</maketarget> �Y�i�C</para>
 
       <para>������ root �������G</para>
 
       <screen>&prompt.root; <userinput>shutdown now</userinput></screen>
 
       <para>�o�˴N�|�q�쥻�� multi-user �Ҧ������� single user �Ҧ��C</para>
 
       <para>�������~�]�i�H���}���A���ۦb�}�����B���
 	<quote>single user</quote> �ﶵ�C  �p���@�ӴN�|�i�J single user �Ҧ��A
 	�M��b shell ���ܲŸ��B��J�G</para>
 
       <screen>&prompt.root; <userinput>fsck -p</userinput>
 &prompt.root; <userinput>mount -u /</userinput>
 &prompt.root; <userinput>mount -a -t ufs</userinput>
 &prompt.root; <userinput>swapon -a</userinput></screen>
 
       <para>�o�˷|���ˬd�ɮרt�ΡA�í��s�N <filename>/</filename>
 	��H�iŪ�g���Ҧ������A�H�� <filename>/etc/fstab</filename>
 	���ҳ]�w����L UFS �ɮרt�ΡA�̫�ҥ� swap �ϰϡC</para>
 
 
         <note>
           <para>�Y CMOS �����O�]�����a�ɶ��A�ӫD GMT �ɰ�(�Y &man.date.1;
 	    ���O�S��ܥ��T���ɶ��B�ɰ�)�A���i��ݭn�A��J�U�C���O�G</para>
 <screen>&prompt.root; <userinput>adjkerntz -i</userinput></screen>
 
           <para>�o�B�J�i�H�T�{�z�����a�ɰϳ]�w�O�_���T &mdash;
 	    �_�h���|�y���@�ǰ��D�C</para>
         </note>
 
     </sect2>
 
     <sect2>
       <title>���� <filename>/usr/obj</filename></title>
 
       <para>�b���s�sĶ�t�Ϊ��L�{���A�sĶ���G�|���(�w�]���p)
 	<filename>/usr/obj</filename> ���C  �o�̭����ؿ��|������
 	<filename>/usr/src</filename> ���ؿ����c�C</para>
 
       <para>�屼�o�ؿ��A�i�H���H�᪺ <command>make buildworld</command>
 	�L�{��֤@�ǡA�ӥB�i�קK�H�e�sĶ���F���{�b���V�c�b�@�_���ۨ̿���
 	�C</para>
 
       <para>�Ӧ��� <filename>/usr/obj</filename> �����ɮץi��|�]�w���i��ʪ�
 	flag(�Ӹ`�аѾ\ &man.chflags.1;)�A�ӥ����������o�� flag �]�w�~��
 	�C</para>
 
       <screen>&prompt.root; <userinput>cd /usr/obj</userinput>
 &prompt.root; <userinput>chflags -R noschg *</userinput>
 &prompt.root; <userinput>rm -rf *</userinput></screen>
     </sect2>
 
     <sect2 id="cutting-edge-compilebase">
       <title>���s�sĶ Base System</title>
 
       <sect3>
 	<title>�O�d�sĶ������</title>
 
 	<para>��ij�i���n�ߺD�A����� &man.make.1; �ɲ��ͪ������s�_�ӡC
 	  �o�˭Y������X���A�N�|�����~�T���������C  ���M���o�ˡA
 	  �A�i�ण���D�p����R�O����X�F�áA���Y��A���D�O���K�� &os; ������
 	  mailing list �N�i�H���H�i�H�����ݬO���@�^�Ʊ��C</para>
 
 	<para>��²�檺��O�N�O�� &man.script.1; ���O�A�å[�W�Ѽ�
 	  (�A�Q�s��O�����ɮצ�m�B�ɦW)�Y�i�C
 	  �o�B�J���Ӧb���s�sĶ�t�ήɴN�n�@�A�M��b�����sĶ���J
 	  <userinput>exit</userinput> �Y�i���}�C</para>
 
 	<screen>&prompt.root; <userinput>script /var/tmp/mw.out</userinput>
 Script started, output file is /var/tmp/mw.out
 &prompt.root; <userinput>make TARGET</userinput>
 <emphasis>&hellip; compile, compile, compile &hellip;</emphasis>
 &prompt.root; <userinput>exit</userinput>
 Script done, &hellip;</screen>
 
 	<para>��F�A�٦��@�I���q<emphasis>�O��</emphasis>�ɮצs��
 	  <filename>/tmp</filename> �ؿ����C  �]�����}������A
 	  �o�ؿ������F�賣�|�Q�M�šC  ����������a��O
 	  <filename>/var/tmp</filename> (�p�W�ҩҥ�) �Ϊ̬O
 	  <username>root</username> ���a�ؿ��C</para>
       </sect3>
 
       <sect3 id="make-buildworld">
 	<title>�sĶ Base System</title>
 
 	<para>�����Х������� <filename>/usr/src</filename> �ؿ��G</para>
 
 	<screen>&prompt.root; <userinput>cd /usr/src</userinput></screen>
 
 	<para>(���M�A���D�A�� source code ����L�a��A�Y�u�O�o�ˡA
 	  �N�����쨺�ӥؿ��Y�i)�C</para>
 	<indexterm><primary><command>make</command></primary></indexterm>
 
 	<para>�ϥ� &man.make.1; ���O�ӭ��s�sĶ world�C
 	  �o���O�|�q <filename>Makefile</filename> ��(�o�ɷ|�g &os;
 	  ���{���Ӧp�󭫷s�sĶ�B�H���Ƕ��ǨӽsĶ����)�hŪ���������O�C</para>
 
 	<para>�@��U���O���榡�p�U�G</para>
 
 	<screen>&prompt.root; <userinput>make -<replaceable>x</replaceable> -D<replaceable>VARIABLE</replaceable> <replaceable>target</replaceable></userinput></screen>
 
 	<para>�b�o�ӨҤl�A<option>-<replaceable>x</replaceable></option>
 	  �O�A�Q�ǵ� &man.make.1; ���ﶵ�A�Ӹ`�����аѾ\ &man.make.1; �����A
 	  �̭��������d�һ����C</para>
 
 	<para><option>-D<replaceable>VARIABLE</replaceable></option>
 	  �h�O���ܼƳ]�w�ǵ� <filename>Makefile</filename>�C  �o���ܼƷ|����
 	  <filename>Makefile</filename> ���欰�C  �o�dz]�w�P
 	  <filename>/etc/make.conf</filename> ���ܼƳ]�w�O�@�ˡA
 	  �u�O�t�@�س]�w�覡�Ӥw�C</para>
 
 	<screen>&prompt.root; <userinput>make -DNO_PROFILE <replaceable>target</replaceable></userinput></screen>
 
 	<para>�W�����Ҥl�h�O�t�@�س]�w�覡�A�]�N�O���Ǥ��n�C
 	  �o�ӨҤl�����N��O���h�sĶ profiled libraries�A�ĪG�N�p�P�]�w�b
 	  <filename>/etc/make.conf</filename> ��</para>
 
 	<programlisting>NO_PROFILE=    true 	#    Avoid compiling profiled libraries</programlisting>
 
 	<para><replaceable>target</replaceable> �h�O�i�D &man.make.1;
 	  �ӥh�����ǡC  �C�� <filename>Makefile</filename> ���|�w�q���P��
 	  <quote>targets</quote>�A�M��̱z�ҵ��� target �N�|�M�w�|�����ǰʧ@
 	  �C</para>
 
 	<para>Some targets are listed in the
 	  <filename>Makefile</filename>, but are not meant for you to run.
 	  Instead, they are used by the build process to break out the
 	  steps necessary to rebuild the system into a number of
 	  sub-steps.</para>
 
 	<para>Most of the time you will not need to pass any parameters to
 	    &man.make.1;, and so your command like will look like
 	    this:</para>
 
 	<screen>&prompt.root; <userinput>make <replaceable>target</replaceable></userinput></screen>
 
 	<para>Where <replaceable>target</replaceable> will be one of
 	  many build options.  The first target should always be
 	  <makevar>buildworld</makevar>.</para>
 
 	<para>As the names imply, <maketarget>buildworld</maketarget>
 	  builds a complete new tree under <filename>/usr/obj</filename>,
 	  and <maketarget>installworld</maketarget>, another target, installs this tree on
 	  the current machine.</para>
 
 	<para>Having separate options is very useful for two reasons.  First, it allows you
 	  to do the build safe in the knowledge that no components of
 	  your running system will be affected.  The build is
 	  <quote>self hosted</quote>.  Because of this, you can safely
 	  run <maketarget>buildworld</maketarget> on a machine running
 	  in multi-user mode with no fear of ill-effects.  It is still
 	  recommended that you run the
 	  <maketarget>installworld</maketarget> part in single user
 	  mode, though.</para>
 
 	<para>Secondly, it allows you to use NFS mounts to upgrade
 	  multiple machines on your network.  If you have three machines,
 	  <hostid>A</hostid>, <hostid>B</hostid> and <hostid>C</hostid> that you want to upgrade, run <command>make
 	  buildworld</command> and <command>make installworld</command> on
 	  <hostid>A</hostid>.  <hostid>B</hostid> and <hostid>C</hostid> should then NFS mount <filename>/usr/src</filename>
 	  and <filename>/usr/obj</filename> from <hostid>A</hostid>, and you can then run
 	  <command>make installworld</command> to install the results of
 	  the build on <hostid>B</hostid> and <hostid>C</hostid>.</para>
 
 	<para>Although the <maketarget>world</maketarget> target still exists,
 	  you are strongly encouraged not to use it.</para>
 
 	<para>Run</para>
 
 	<screen>&prompt.root; <userinput>make buildworld</userinput></screen>
 
         <para>It is possible to specify a <option>-j</option> option to
           <command>make</command> which will cause it to spawn several
           simultaneous processes.  This is most useful on multi-CPU machines.
           However, since much of the compiling process is IO bound rather
           than CPU bound it is also useful on single CPU machines.</para>
 
 	<para>On a typical single-CPU machine you would run:</para>
 
 	  <screen>&prompt.root; <userinput>make -j4 buildworld</userinput></screen>
 
 	<para>&man.make.1; will then have up to 4 processes running at any one
 	  time.  Empirical evidence posted to the mailing lists shows this
 	  generally gives the best performance benefit.</para>
 
 	<para>If you have a multi-CPU machine and you are using an SMP
 	  configured kernel try values between 6 and 10 and see how they speed
 	  things up.</para>
       </sect3>
 
       <sect3>
 	<title>Timings</title>
 	<indexterm>
 	  <primary>rebuilding <quote>world</quote></primary>
 	  <secondary>timings</secondary>
 	</indexterm>
 
         <para>Many factors influence the build time, but fairly recent
           machines may only take a one or two hours to build
           the &os.stable; tree, with no tricks or shortcuts used during the
           process.  A &os.current; tree will take somewhat longer.</para>
       </sect3>
     </sect2>
 
     <sect2>
       <title>Compile and Install a New Kernel</title>
       <indexterm>
         <primary>kernel</primary>
 	<secondary>compiling</secondary>
       </indexterm>
 
       <para>To take full advantage of your new system you should recompile the
 	kernel.  This is practically a necessity, as certain memory structures
 	may have changed, and programs like &man.ps.1; and &man.top.1; will
 	fail to work until the kernel and source code versions are the
 	same.</para>
 
       <para>The simplest, safest way to do this is to build and install a
 	kernel based on <filename>GENERIC</filename>.  While
 	<filename>GENERIC</filename> may not have all the necessary devices
 	for your system, it should contain everything necessary to boot your
 	system back to single user mode.  This is a good test that the new
 	system works properly.  After booting from
 	<filename>GENERIC</filename> and verifying that your system works you
 	can then build a new kernel based on your normal kernel	configuration
 	file.</para>
 
       <para>On &os; it is important to <link
         linkend="make-buildworld">build world</link> before building a
         new kernel.</para>
 
       <note><para>If you want to build a custom kernel, and already have a configuration
 	file, just use <literal>KERNCONF=<replaceable>MYKERNEL</replaceable></literal>
 	like this:</para>
 
       <screen>&prompt.root; <userinput>cd /usr/src</userinput>
 &prompt.root; <userinput>make buildkernel KERNCONF=<replaceable>MYKERNEL</replaceable></userinput>
 &prompt.root; <userinput>make installkernel KERNCONF=<replaceable>MYKERNEL</replaceable></userinput></screen>
       </note>
 
       <para>Note that if you have raised <literal>kern.securelevel</literal>
 	above 1 <emphasis>and</emphasis> you have set either the
 	<literal>noschg</literal> or similar flags to your kernel binary, you
 	might find it necessary to drop into single user mode to use
 	<maketarget>installkernel</maketarget>.  Otherwise you should be able
 	to run both these commands from multi user mode without
 	problems.  See &man.init.8; for details about
 	<literal>kern.securelevel</literal> and &man.chflags.1; for details
 	about the various file flags.</para>
     </sect2>
 
     <sect2>
       <title>Reboot into Single User Mode</title>
       <indexterm><primary>single-user mode</primary></indexterm>
 
       <para>You should reboot into single user mode to test the new kernel
 	works.  Do this by following the instructions in
 	<xref linkend="makeworld-singleuser"/>.</para>
     </sect2>
 
     <sect2 id="make-installworld">
       <title>Install the New System Binaries</title>
 
       <para>If you were building a version of &os; recent enough to have
 	used <command>make buildworld</command> then you should now use
 	<maketarget>installworld</maketarget> to install the new system
 	binaries.</para>
 
       <para>Run</para>
 
       <screen>&prompt.root; <userinput>cd /usr/src</userinput>
 &prompt.root; <userinput>make installworld</userinput></screen>
 
       <note>
 	<para>If you specified variables on the <command>make
 	    buildworld</command> command line, you must specify the same
 	  variables in the <command>make installworld</command> command
 	  line.  This does not necessarily hold true for other options;
 	  for example, <option>-j</option> must never be used with
 	  <maketarget>installworld</maketarget>.</para>
 
 	<para>For example, if you ran:</para>
 
 	<screen>&prompt.root; <userinput>make -DNO_PROFILE buildworld</userinput></screen>
 
 	<para>you must install the results with:</para>
 
 	<screen>&prompt.root; <userinput>make -DNO_PROFILE installworld</userinput></screen>
 
 	<para>otherwise it would try to install profiled libraries that
 	  had not been built during the <command>make buildworld</command>
 	  phase.</para>
       </note>
     </sect2>
 
     <sect2>
       <title>Update Files Not Updated by <command>make installworld</command></title>
 
       <para>Remaking the world will not update certain directories (in
 	particular, <filename>/etc</filename>, <filename>/var</filename> and
 	<filename>/usr</filename>) with new or changed configuration files.</para>
 
       <para>The simplest way to update these files is to use
         &man.mergemaster.8;, though it is possible to do it manually
         if you would prefer to do that.  Regardless of which way you
 	choose, be sure to make a backup of <filename>/etc</filename> in
 	case anything goes wrong.</para>
 
     <sect3 id="mergemaster">
       <sect3info>
 	<authorgroup>
 	  <author>
 	    <firstname>Tom</firstname>
 	    <surname>Rhodes</surname>
 	    <contrib>Contributed by </contrib>
 	  </author>
 	</authorgroup>
       </sect3info>
       <title><command>mergemaster</command></title>
         <indexterm><primary><command>mergemaster</command></primary></indexterm>
 
       <para>The &man.mergemaster.8; utility is a Bourne script that will
         aid you in determining the differences between your configuration files
         in <filename>/etc</filename>, and the configuration files in
         the source tree <filename>/usr/src/etc</filename>. This is
         the recommended solution for keeping the system configuration files up to date
         with those located in the source tree.</para>
 
       <para>To begin simply type <command>mergemaster</command> at your prompt, and
         watch it start going.  <command>mergemaster</command> will then build a
         temporary root environment, from <filename>/</filename> down, and populate
         it with various system configuration files.  Those files are then compared
         to the ones currently installed in your system.  At this point, files that
         differ will be shown in &man.diff.1; format, with the <option>+</option> sign
         representing added or modified lines, and <option>-</option> representing
         lines that will be either removed completely, or replaced with a new line.
         See the &man.diff.1; manual page for more information about the &man.diff.1;
         syntax and how file differences are shown.</para>
 
       <para>&man.mergemaster.8; will then show you each file that displays variances,
         and at this point you will have the option of either deleting the new file (referred
         to as the temporary file), installing the temporary file in its unmodified state,
         merging the temporary file with the currently installed file, or viewing the
         &man.diff.1; results again.</para>
 
       <para>Choosing to delete the temporary file will tell &man.mergemaster.8; that we
         wish to keep our current file unchanged, and to delete the new version.
         This option is not recommended, unless you see no
         reason to change the current file.  You can get help at any time by
         typing <keycap>?</keycap> at the &man.mergemaster.8; prompt.  If the user
         chooses to skip a file, it will be presented again after all other files
         have been dealt with.</para>
 
       <para>Choosing to install the unmodified temporary file will replace the
         current file with the new one.  For most unmodified files, this is the best
         option.</para>
 
       <para>Choosing to merge the file will present you with a text editor,
         and the contents of both files.  You can now merge them by
         reviewing both files side by side on the screen, and choosing parts from
         both to create a finished product.  When the files are compared side by side,
         the <keycap>l</keycap> key will select the left contents and the
         <keycap>r</keycap> key will select contents from your right.
         The final output will be a file consisting of both parts, which can then be
         installed.  This option is customarily used for files where settings have been
         modified by the user.</para>
 
       <para>Choosing to view the &man.diff.1; results again will show you the file differences
         just like &man.mergemaster.8; did before prompting you for an option.</para>
 
       <para>After &man.mergemaster.8; is done with the system files you will be
         prompted for other options.  &man.mergemaster.8; may ask if you want to rebuild
         the password file and will finish up with an option to
         remove left-over temporary files.</para>
       </sect3>
 
       <sect3>
 	<title>Manual Update</title>
 
       <para>If you wish to do the update manually, however,
         you cannot just copy over the files from
 	<filename>/usr/src/etc</filename> to <filename>/etc</filename> and
 	have it work.  Some of these files must be <quote>installed</quote>
 	first.  This is because the <filename>/usr/src/etc</filename>
 	directory <emphasis>is not</emphasis> a copy of what your
 	<filename>/etc</filename> directory should look like.  In addition,
 	there are files that should be in <filename>/etc</filename> that are
 	not in <filename>/usr/src/etc</filename>.</para>
 
       <para>If you are using &man.mergemaster.8; (as recommended),
         you can skip forward to the <link linkend="cutting-edge-rebooting">next
 	section</link>.</para>
 
       <para>The simplest way to do this by hand is to install the
 	files into a new directory, and then work through them looking
 	for differences.</para>
 
       <warning>
 	<title>Backup Your Existing <filename>/etc</filename></title>
 
 	<para>Although, in theory, nothing is going to touch this directory
 	  automatically, it is always better to be sure.  So copy your
 	  existing <filename>/etc</filename> directory somewhere safe.
 	  Something like:</para>
 
 	<screen>&prompt.root; <userinput>cp -Rp /etc /etc.old</userinput></screen>
 
 	<para><option>-R</option> does a recursive copy, <option>-p</option>
 	  preserves times, ownerships on files and suchlike.</para>
       </warning>
 
       <para>You need to build a dummy set of directories to install the new
 	<filename>/etc</filename> and other files into.
 	<filename>/var/tmp/root</filename> is a reasonable choice, and
 	there are a number of subdirectories required under this as
 	well.</para>
 
       <screen>&prompt.root; <userinput>mkdir /var/tmp/root</userinput>
 &prompt.root; <userinput>cd /usr/src/etc</userinput>
 &prompt.root; <userinput>make DESTDIR=/var/tmp/root distrib-dirs distribution</userinput></screen>
 
       <para>This will build the necessary directory structure and install the
 	files.  A lot of the subdirectories that have been created under
 	<filename>/var/tmp/root</filename> are empty and should be deleted.
 	The simplest way to do this is to:</para>
 
       <screen>&prompt.root; <userinput>cd /var/tmp/root</userinput>
 &prompt.root; <userinput>find -d . -type d | xargs rmdir 2&gt;/dev/null</userinput></screen>
 
       <para>This will remove all empty directories.  (Standard error is
         redirected to <filename>/dev/null</filename> to prevent the warnings
         about the directories that are not empty.)</para>
 
       <para><filename>/var/tmp/root</filename> now contains all the files that
 	should be placed in appropriate locations below
 	<filename>/</filename>.  You now have to go through each of these
 	files, determining how they differ with your existing files.</para>
 
       <para>Note that some of the files that will have been installed in
 	<filename>/var/tmp/root</filename> have a leading <quote>.</quote>.  At the
 	time of writing the only files like this are shell startup files in
 	<filename>/var/tmp/root/</filename> and
 	<filename>/var/tmp/root/root/</filename>, although there may be others
 	(depending on when you are reading this).  Make sure you use
 	<command>ls -a</command> to catch them.</para>
 
       <para>The simplest way to do this is to use &man.diff.1; to compare the
 	two files:</para>
 
       <screen>&prompt.root; <userinput>diff /etc/shells /var/tmp/root/etc/shells</userinput></screen>
 
       <para>This will show you the differences between your
 	<filename>/etc/shells</filename> file and the new
 	<filename>/var/tmp/root/etc/shells</filename> file.  Use these to decide whether to
 	merge in changes that you have made or whether to copy over your old
 	file.</para>
 
       <tip>
 	<title>Name the New Root Directory
 	  (<filename>/var/tmp/root</filename>) with a Time Stamp, so You Can
 	  Easily Compare Differences Between Versions</title>
 
 	<para>Frequently rebuilding the world means that you have to update
 	<filename>/etc</filename> frequently as well, which can be a bit of
 	  a chore.</para>
 
 	<para>You can speed this process up by keeping a copy of the last set
 	  of changed files that you merged into <filename>/etc</filename>.
 	  The following procedure gives one idea of how to do this.</para>
 
 	<procedure>
 	  <step>
 	    <para>Make the world as normal.  When you want to update
 	      <filename>/etc</filename> and the other directories, give the
 	      target directory a name based on the current date.  If you were
 	      doing this on the 14th of February 1998 you could do the
 	      following:</para>
 
 	    <screen>&prompt.root; <userinput>mkdir /var/tmp/root-19980214</userinput>
 &prompt.root; <userinput>cd /usr/src/etc</userinput>
 &prompt.root; <userinput>make DESTDIR=/var/tmp/root-19980214 \
     distrib-dirs distribution</userinput></screen>
 	  </step>
 
 	  <step>
 	    <para>Merge in the changes from this directory as outlined
 	      above.</para>
 
 	    <para><emphasis>Do not</emphasis> remove the
 	      <filename>/var/tmp/root-19980214</filename> directory when you
 	      have finished.</para>
 	  </step>
 
 	  <step>
 	    <para>When you have downloaded the latest version of the source
 	      and remade it, follow step 1.  This will give you a new
 	      directory, which might be called
 	      <filename>/var/tmp/root-19980221</filename> (if you wait a week
 	      between doing updates).</para>
 	  </step>
 
 	  <step>
 	    <para>You can now see the differences that have been made in the
 	      intervening week using &man.diff.1; to create a recursive diff
 	      between the two directories:</para>
 
 	    <screen>&prompt.root; <userinput>cd /var/tmp</userinput>
 &prompt.root; <userinput>diff -r root-19980214 root-19980221</userinput></screen>
 
 	    <para>Typically, this will be a much smaller set of differences
 	      than those between
 	      <filename>/var/tmp/root-19980221/etc</filename> and
 	      <filename>/etc</filename>.  Because the set of differences is
 	      smaller, it is easier to migrate those changes across into your
 	      <filename>/etc</filename> directory.</para>
 	  </step>
 
 	  <step>
 	    <para>You can now remove the older of the two
 	      <filename>/var/tmp/root-*</filename> directories:</para>
 
 	    <screen>&prompt.root; <userinput>rm -rf /var/tmp/root-19980214</userinput></screen>
 	  </step>
 
 	  <step>
 	    <para>Repeat this process every time you need to merge in changes
 	      to <filename>/etc</filename>.</para>
 	  </step>
 	</procedure>
 
 	<para>You can use &man.date.1; to automate the generation of the
 	  directory names:</para>
 
 	<screen>&prompt.root; <userinput>mkdir /var/tmp/root-`date "+%Y%m%d"`</userinput></screen>
       </tip>
       </sect3>
     </sect2>
 
     <sect2 id="cutting-edge-rebooting">
       <title>Rebooting</title>
 
       <para>You are now done.  After you have verified that everything appears
 	to be in the right place you can reboot the system.  A simple
 	&man.shutdown.8; should do it:</para>
 
       <screen>&prompt.root; <userinput>shutdown -r now</userinput></screen>
     </sect2>
 
     <sect2>
       <title>Finished</title>
 
       <para>You should now have successfully upgraded your &os; system.
 	Congratulations.</para>
 
       <para>If things went slightly wrong, it is easy to rebuild a particular
         piece of the system.  For example, if you accidentally deleted
         <filename>/etc/magic</filename> as part of the upgrade or merge of
         <filename>/etc</filename>, the &man.file.1; command will stop working.
         In this case, the fix would be to run:</para>
 
 	<screen>&prompt.root; <userinput>cd /usr/src/usr.bin/file</userinput>
 &prompt.root; <userinput>make all install</userinput></screen>
     </sect2>
 
     <sect2>
       <title>Questions</title>
 
       <qandaset>
 	<qandaentry>
 	  <question>
 	    <para>Do I need to re-make the world for every change?</para>
 	  </question>
 
 	  <answer>
             <para>There is no easy answer to this one, as it depends on the
 	      nature of the change.  For example, if you just ran <application>CVSup</application>, and
 	      it has shown the following files as being updated:</para>
 
 	    <screen><filename>src/games/cribbage/instr.c</filename>
 <filename>src/games/sail/pl_main.c</filename>
 <filename>src/release/sysinstall/config.c</filename>
 <filename>src/release/sysinstall/media.c</filename>
 <filename>src/share/mk/bsd.port.mk</filename></screen>
 
 	    <para>it probably is not worth rebuilding the entire world.
 	      You could just go to the appropriate sub-directories and
 	      <command>make all install</command>, and that's about it.  But
 	      if something major changed, for example
 	      <filename>src/lib/libc/stdlib</filename> then you should either
 	      re-make the world, or at least those parts of it that are
 	      statically linked (as well as anything else you might have added
 	      that is statically linked).</para>
 
 	    <para>At the end of the day, it is your call.  You might be happy
 	      re-making the world every fortnight say, and let changes
 	      accumulate over that fortnight.  Or you might want to re-make
 	      just those things that have changed, and be confident you can
 	      spot all the dependencies.</para>
 
 	    <para>And, of course, this all depends on how often you want to
 	      upgrade, and whether you are tracking &os.stable; or
 	      &os.current;.</para>
 	  </answer>
 	</qandaentry>
 
 	<qandaentry>
 	  <question>
 	    <para>My compile failed with lots of signal 11<indexterm>
 	      <primary>signal 11</primary></indexterm> (or other signal
 	      number) errors.  What has happened?</para>
 	  </question>
 
 	  <answer>
 	    <para>This is normally indicative of hardware problems.
 	      (Re)making the world is an effective way to stress test your
 	      hardware, and will frequently throw up memory problems.  These
 	      normally manifest themselves as the compiler mysteriously dying
 	      on receipt of strange signals.</para>
 
 	    <para>A sure indicator of this is if you can restart the make and
 	      it dies at a different point in the process.</para>
 
 	    <para>In this instance there is little you can do except start
 	      swapping around the components in your machine to determine
 	      which one is failing.</para>
 	  </answer>
 	</qandaentry>
 
 	<qandaentry>
 	  <question>
 	    <para>Can I remove <filename>/usr/obj</filename> when I have
 	      finished?</para>
 	  </question>
 
 	  <answer>
 	    <para>The short answer is yes.</para>
 
 	    <para><filename>/usr/obj</filename> contains all the object files
 	      that were produced during the compilation phase.  Normally, one
 	      of the first steps in the <command>make buildworld</command> process is to
 	      remove this directory and start afresh.  In this case, keeping
 	      <filename>/usr/obj</filename> around after you have finished
 	      makes little sense, and will free up a large chunk of disk space
 	      (currently about 340&nbsp;MB).</para>
 
 	    <para>However, if you know what you are doing you can have
 	      <command>make buildworld</command> skip this step.  This will make subsequent
 	      builds run much faster, since most of sources will not need to
 	      be recompiled.  The flip side of this is that subtle dependency
 	      problems can creep in, causing your build to fail in odd ways.
 	      This frequently generates noise on the &os; mailing lists,
 	      when one person complains that their build has failed, not
 	      realizing that it is because they have tried to cut
 	      corners.</para>
 	  </answer>
 	</qandaentry>
 
 	<qandaentry>
 	  <question>
 	    <para>Can interrupted builds be resumed?</para>
 	  </question>
 
 	  <answer>
 	    <para>This depends on how far through the process you got before
 	      you found a problem.</para>
 
 	    <para><emphasis>In general</emphasis> (and this is not a hard and
 	      fast rule) the <command>make buildworld</command> process builds new
 	      copies of essential tools (such as &man.gcc.1;, and
 	      &man.make.1;) and the system libraries.  These tools and
 	      libraries are then installed.  The new tools and libraries are
 	      then used to rebuild themselves, and are installed again. The
 	      entire system (now including regular user programs, such as
 		&man.ls.1; or &man.grep.1;) is then rebuilt with the new
 	      system files.</para>
 
 	    <para>If you are at the last stage, and you know it (because you
 	      have looked through the output that you were storing) then you
 	      can (fairly safely) do:</para>
 
 	    <screen><emphasis>&hellip; fix the problem &hellip;</emphasis>
 &prompt.root; <userinput>cd /usr/src</userinput>
 &prompt.root; <userinput>make -DNO_CLEAN all</userinput></screen>
 
 	    <para>This will not undo the work of the previous
 	      <command>make buildworld</command>.</para>
 
 	    <para>If you see the message:</para>
 
 	      <screen>--------------------------------------------------------------
 Building everything..
 --------------------------------------------------------------</screen>
 
 	    <para>in the <command>make buildworld</command> output then it is
 	      probably fairly safe to do so.</para>
 
 	    <para>If you do not see that message, or you are not sure, then it
 	      is always better to be safe than sorry, and restart the build
 	      from scratch.</para>
 	  </answer>
 	</qandaentry>
 
 	<qandaentry>
 	  <question>
 	    <para>How can I speed up making the world?</para>
           </question>
 
           <answer>
 	    <itemizedlist>
 	      <listitem>
 		<para>Run in single user mode.</para>
 	      </listitem>
 
 	      <listitem>
 		<para>Put the <filename>/usr/src</filename> and
 		  <filename>/usr/obj</filename> directories on separate
 		  file systems held on separate disks.  If possible, put these
 		  disks on separate disk controllers.</para>
 	      </listitem>
 
 	      <listitem>
 		<para>Better still, put these file systems across multiple
 		  disks using the &man.ccd.4; (concatenated disk
 		  driver) device.</para>
 	      </listitem>
 
 	      <listitem>
 		<para>Turn off profiling (set <quote>NO_PROFILE=true</quote> in
 		  <filename>/etc/make.conf</filename>).  You almost certainly
 		  do not need it.</para>
 	      </listitem>
 
 	      <listitem>
 		<para>Also in <filename>/etc/make.conf</filename>, set
 		  <makevar>CFLAGS</makevar> to something like <option>-O
 		  -pipe</option>.  The optimization <option>-O2</option> is much
 		  slower, and the optimization difference between
 		  <option>-O</option> and <option>-O2</option> is normally
 		  negligible.  <option>-pipe</option> lets the compiler use
 		  pipes rather than temporary files for communication, which
 		  saves disk access (at the expense of memory).</para>
 	      </listitem>
 
 	      <listitem>
 		<para>Pass the <option>-j<replaceable>n</replaceable></option> option to &man.make.1; to
 		  run multiple processes in parallel.  This usually helps
 		  regardless of whether you have a single or a multi processor
 		  machine.</para>
 	      </listitem>
 
 	      <listitem><para>The file system holding
 		  <filename>/usr/src</filename> can be mounted (or remounted)
 		  with the <option>noatime</option> option.  This prevents the
 		  file system from recording the file access time.  You probably
 		  do not need this information anyway.</para>
 
 		  <screen>&prompt.root; <userinput>mount -u -o noatime /usr/src</userinput></screen>
 
 		  <warning>
 		    <para>The example assumes <filename>/usr/src</filename> is
 		      on its own file system.  If it is not (if it is a part of
 		      <filename>/usr</filename> for example) then you will
 		      need to use that file system mount point, and not
 		      <filename>/usr/src</filename>.</para>
 		  </warning>
 	      </listitem>
 
 	      <listitem>
 		<para>The file system holding <filename>/usr/obj</filename> can
 		  be mounted (or remounted) with the <option>async</option>
 		  option.  This causes disk writes to happen asynchronously.
 		  In other words, the write completes immediately, and the
 		  data is written to the disk a few seconds later.  This
 		  allows writes to be clustered together, and can be a
 		  dramatic performance boost.</para>
 
 		<warning>
 		  <para>Keep in mind that this option makes your file system
 		    more fragile.  With this option there is an increased
 		    chance that, should power fail, the file system will be in
 		    an unrecoverable state when the machine restarts.</para>
 
 		  <para>If <filename>/usr/obj</filename> is the only thing on
 		    this file system then it is not a problem.  If you have
 		    other, valuable data on the same file system then ensure
 		    your backups are fresh before you enable this
 		    option.</para>
 		</warning>
 
 		<screen>&prompt.root; <userinput>mount -u -o async /usr/obj</userinput></screen>
 
 		<warning>
 		  <para>As above, if <filename>/usr/obj</filename> is not on
 		    its own file system, replace it in the example with the
 		    name of the appropriate mount point.</para>
 		</warning>
 	      </listitem>
 	    </itemizedlist>
 	  </answer>
 	</qandaentry>
 
         <qandaentry>
           <question>
             <para>What do I do if something goes wrong?</para>
           </question>
 
           <answer>
             <para>Make absolutely sure your environment has no
               extraneous cruft from earlier builds.  This is simple
               enough.</para>
 
             <screen>&prompt.root; <userinput>chflags -R noschg /usr/obj/usr</userinput>
 &prompt.root; <userinput>rm -rf /usr/obj/usr</userinput>
 &prompt.root; <userinput>cd /usr/src</userinput>
 &prompt.root; <userinput>make cleandir</userinput>
 &prompt.root; <userinput>make cleandir</userinput></screen>
 
             <para>Yes, <command>make cleandir</command> really should
               be run twice.</para>
 
             <para>Then restart the whole process, starting
               with <command>make buildworld</command>.</para>
 
             <para>If you still have problems, send the error and the
               output of <command>uname -a</command> to &a.questions;.
               Be prepared to answer other questions about your
               setup!</para>
           </answer>
         </qandaentry>
       </qandaset>
     </sect2>
   </sect1>
 
   <sect1 id="small-lan">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Mike</firstname>
 	  <surname>Meyer</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
     </sect1info>
     <title>Tracking for Multiple Machines</title>
     <indexterm>
       <primary>NFS</primary>
       <secondary>installing multiple machines</secondary>
     </indexterm>
 
     <para>If you have multiple machines that you want to track the
       same source tree, then having all of them download sources and
       rebuild everything seems like a waste of resources: disk space,
       network bandwidth, and CPU cycles.  It is, and the solution is
       to have one machine do most of the work, while the rest of the
       machines mount that work via NFS.  This section outlines a
       method of doing so.</para>
 
     <sect2 id="small-lan-preliminaries">
       <title>Preliminaries</title>
 
       <para>First, identify a set of machines that is going to run
 	the same set of binaries, which we will call a
 	<emphasis>build set</emphasis>.  Each machine can have a
 	custom kernel, but they will be running the same userland
 	binaries.  From that set, choose a machine to be the
 	<emphasis>build machine</emphasis>.  It is going to be the
 	machine that the world and kernel are built on. Ideally, it
 	should be a fast machine that has sufficient spare CPU to
 	run <command>make buildworld</command> and
 	<command>make buildkernel</command>.  You will also want to
 	choose a machine to be the <emphasis>test
 	machine</emphasis>, which will test software updates before they
 	are put into production.  This <emphasis>must</emphasis> be a
 	machine that you can afford to have down for an extended
 	period of time.  It can be the build machine, but need not be.</para>
 
       <para>All the machines in this build set need to mount
 	<filename>/usr/obj</filename> and
 	<filename>/usr/src</filename> from the same machine, and at
 	the same point.  Ideally, those are on two different drives
 	on the build machine, but they can be NFS mounted on that machine
 	as well.  If you have multiple build sets,
 	<filename>/usr/src</filename> should be on one build machine, and
 	NFS mounted on the rest.</para>
 
       <para>Finally make sure that
 	<filename>/etc/make.conf</filename> on all the machines in
 	the build set agrees with the build machine.  That means that
 	the build machine must build all the parts of the base
 	system that any machine in the build set is going to
 	install.  Also, each build machine should have its kernel
 	name set with <makevar>KERNCONF</makevar> in
 	<filename>/etc/make.conf</filename>, and the build machine
 	should list them all in <makevar>KERNCONF</makevar>, listing
 	its own kernel first.  The build machine must have the kernel
 	configuration files for each machine in
 	<filename>/usr/src/sys/<replaceable>arch</replaceable>/conf</filename>
 	if it is going to build their kernels.</para>
     </sect2>
 
     <sect2>
       <title>The Base System</title>
 
       <para>Now that all that is done, you are ready to build
 	everything.  Build the kernel and world as described in <xref
 	linkend="make-buildworld"/> on the build machine,
 	but do not install anything.  After the build has finished, go
 	to the test machine, and install the kernel you just
 	built.  If this machine mounts <filename>/usr/src</filename>
 	and <filename>/usr/obj</filename> via NFS, when you reboot
 	to single user you will need to enable the network and mount
 	them.  The easiest way to do this is to boot to multi-user,
 	then run <command>shutdown now</command> to go to single user
 	mode.  Once there, you can install the new kernel and world and run
 	<command>mergemaster</command> just as you normally would.  When
 	done, reboot to return to normal multi-user operations for this
 	machine.</para>
 
       <para>After you are certain that everything on the test
 	machine is working properly, use the same procedure to
 	install the new software on each of the other machines in
 	the build set.</para>
     </sect2>
 
     <sect2>
       <title>Ports</title>
 
       <para>The same ideas can be used for the ports tree.  The first
 	critical step is mounting <filename>/usr/ports</filename> from
 	the same machine to all the machines in the build set.  You can
 	then set up <filename>/etc/make.conf</filename> properly to share
 	distfiles.  You should set <makevar>DISTDIR</makevar> to a
 	common shared directory that is writable by whichever user
 	<username>root</username> is mapped to by your NFS mounts.  Each
 	machine should set <makevar>WRKDIRPREFIX</makevar> to a
 	local build directory.  Finally, if you are going to be
 	building and distributing packages, you should set
 	<makevar>PACKAGES</makevar> to a directory similar to
 	<makevar>DISTDIR</makevar>.</para>
     </sect2>
   </sect1>
 </chapter>
diff --git a/zh_TW.Big5/books/handbook/l10n/chapter.xml b/zh_TW.Big5/books/handbook/l10n/chapter.xml
index 4029f6e690..ec34ee2791 100644
--- a/zh_TW.Big5/books/handbook/l10n/chapter.xml
+++ b/zh_TW.Big5/books/handbook/l10n/chapter.xml
@@ -1,908 +1,905 @@
 <?xml version="1.0" encoding="big5"?>
 <!--
      The FreeBSD Documentation Project
 
      $FreeBSD$
      Original revision: 1.119
 -->
 
 <chapter id="l10n">
   <chapterinfo>
     <authorgroup>
       <author>
 	<firstname>Andrey</firstname>
 	<surname>Chernov</surname>
 	<contrib>Contributed by </contrib>
       </author>
     </authorgroup>
     <authorgroup>
       <author>
 	<firstname>Michael C.</firstname>
 	<surname>Wu</surname>
 	<contrib>Rewritten by </contrib>
       </author>
       <!-- 30 Nv 2000 -->
     </authorgroup>
   </chapterinfo>
 
   <title>�y�t�]�w - I18N/L10N �Ϊk�P�]�w</title>
 
   <sect1 id="l10n-synopsis">
     <title>���z</title>
 
     <para>�ѩ� FreeBSD �O���G���@�ɪ��ϥΪ̤ΧӤu�Ҥ�����p�e�A�����D�n���Q���O
       FreeBSD ����ڤơB���g��ij�D�A�H�K�����y���O�^�y�t���H�]�බ�Q�����U���u�@�C
       �b�@�~�t�ΡB���ε{����ؼh���A�D�n���O�z�L i18n �зǨӹ�@���A�ҥH�A
       �o�̧ڭ̱N�|���Фj�P�B�@�覡�C</para>
 
     <para>Ū���o���A�z�N�F�ѡJ</para>
     <itemizedlist>
       <listitem><para>�U�ؤ��P���y���P�a�ϳ]�w�p��b�@�~�t�ΤW�i��s�X�C</para></listitem>
       <listitem><para>�p��]�w�n�J�Ϊ� shell �y�t���ҡC</para></listitem>
       <listitem><para>�p��N�A�� console �]���^�y�H�~���y�t�]�w�C</para></listitem>
       <listitem><para>�p��ϥΤ��P�y�t���]�w�A���� X Window �B�@��ˤ��C</para></listitem>
       <listitem><para>����i�H����h�P i18n �W��ۮe�����ε{���W���ơC</para></listitem>
    </itemizedlist>
 
     <para>�b�}�l�\Ū�o�����e�A�z�ݭn�J</para>
 
     <itemizedlist>
       <listitem><para>���D�p��H ports/packages �Ӧw�����ε{��(<xref linkend="ports"/>)�C</para></listitem>
     </itemizedlist>
   </sect1>
 
   <sect1 id="l10n-basics">
     <title>L10N ��¦����</title>
 
     <sect2>
       <title>����O I18N/L10N?</title>
     <indexterm>
       <primary>internationalization</primary>
       <see>localization</see>
     </indexterm>
     <indexterm><primary>localization</primary></indexterm>
 
       <para>�{���}�o�H���ߺD�� internationalization �Y�g�� I18N�A�������Ʀr 18 �D�O�̫e�P�̫᭱�r���������r���Ӽ��`�M�A
         �� L10N �]�O�H�@�˪��覡�A�O <quote>localization</quote> ���Y�g�C
         �u�n���ŦX I18N/L10N �W��B��w�����ε{���A�N�i�H���ϥΪ̨̦U�ۻy�t�ӧ@�]�w�C</para>
 
       <para>I18N ���ε{���O�H I18N �}�o�u��Ӷi��}�o���A
         ���i�H���{���}�o�H���z�L�g²�檺��r�ɡA�N�i�H�����e���W�����B�T��½Ķ���U�y�t�������C
         �ڭ̱j�P��ij�{���}�o�H�����`�o�ӹC���W�h�C</para>
     </sect2>
 
     <sect2>
       <title>����Өϥ� I18N/L10N�H</title>
 
       <para>�u�n���ŦX I18N/L10N �зǡA�N�i�H���P�a�ݡB��J�B�B�z�D�^�媺��ơC</para>
     </sect2>
 
     <sect2>
       <title>I18N �䴩���ǻy�t�H</title>
 
       <para>I18N �M L10N �ëD FreeBSD �үS�����A�ثe�o�@�ɤW���X�G���@�D�n�y�t�����䴩�A
 	���O�G����B�w��B���B����B�k��B�X��B�V�n�嵥���C</para>
     </sect2>
   </sect1>
 
   <sect1 id="using-localization">
     <title>�ϥλy�t�]�w(Localization)</title>
 
     <para>I18N �M L10N �ëD FreeBSD �үS�����A�ӬO�@�q���C���W�h�C
       �ڭ̹��y�A�b FreeBSD �@�ɤ��P�˿��u�o���C���W�h�C</para>
     <indexterm><primary>locale</primary></indexterm>
 
     <para>Locale �]�w�ѤT�ӳ����Ҳզ��G�y���N�X(Language Code)�B��X(Country Code)�B�s�X(Encoding)�C
       �ҥH�ALocale ���]�w�W�ٴN�O�ѳo�T�Ӥ@�_�զ��G</para>
 
     <programlisting><replaceable>�y���N�X</replaceable>_<replaceable>��X</replaceable>.<replaceable>�s�X</replaceable></programlisting>
 
     <sect2>
       <title>�y���B��X</title>
       <indexterm><primary>language codes</primary></indexterm>
       <indexterm><primary>country codes</primary></indexterm>
 
       <para>�ϥΪ̥����n�����D�o�ǯS�w����X�B�y���N�X(��X�|�i�D���ε{���Өϥέ��@�ػy��)�A
         �~���� FreeBSD �Ψ�L�䴩 I18N �� &unix; ���t�Χ@ locale �����]�w�C
         ���~�A�����s����(borwser)�BSMTP/POP �D���BWeb �D�����]���H�o�[�c���D�C
         �U���O�p��ϥΡy�y���N�X�B��X�z���Ҥl�G</para>
 
       <informaltable frame="none" pgwide="1">
 	<tgroup cols="2">
 	  <thead>
 	    <row>
 	      <entry>�y���N�X/��X</entry>
 	      <entry>²��</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry>en_US</entry>
 	      <entry>�^��(����)</entry>
 	    </row>
 
 	    <row>
 	      <entry>ru_RU</entry>
 	      <entry>�X��(�X��)</entry>
 	    </row>
 
 	    <row>
 	      <entry>zh_TW</entry>
 	      <entry>���餤��(�x�W)</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
 
     </sect2>
 
     <sect2>
       <title>�s�X</title>
       <indexterm><primary>encodings</primary></indexterm>
       <indexterm><primary>ASCII</primary></indexterm>
 
       <para>���ǻy���ëD�ĥ� ASCII �s�X�A�i��O�G 8-bit�Bwide
 	�� multibyte �r���A�Ա��аѾ\ &man.multibyte.3;�C
 	���j�����{���i��L�k���T�P�O�B�λ~�P���S������r���C�Ӹ��s���{�����i�H��{
 	8-bit �r���C  �ѩ�U�{�����@�k���@�A�ϥΪ̥i��ݭn�b�sĶ�{���ɡA�[�W
 	wide �� multibyte �r�����䴩�]�w�A�άO���T�վ�~��C
 	�n��J�B�B�z wide �� multibyte �r�����ܡA�i�h�h�Q�� <ulink
 	url="&url.base;/ports/index.html">FreeBSD Ports Collection</ulink> �����U��y���������{���C
 	�Ա��аѾ\ FreeBSD �U port ���� I18N �������C</para>
 
       <para>Specifically, the user needs to look at the application
 	documentation to decide on how to configure it correctly or to
 	pass correct values into the configure/Makefile/compiler.</para>
 
       <para>Some things to keep in mind are:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>Language specific single C chars character sets
 	  (see &man.multibyte.3;), e.g.
 	    ISO8859-1, ISO8859-15, KOI8-R, CP437.</para>
 	</listitem>
 
 	<listitem>
 	  <para>Wide or multibyte encodings, e.g. EUC, Big5.</para>
 	</listitem>
       </itemizedlist>
 
       <para>You can check the active list of character sets at the
 	<ulink
 	url="http://www.iana.org/assignments/character-sets">IANA Registry</ulink>.</para>
 
       <note>
       <para>&os; use X11-compatible locale encodings instead.</para>
       </note>
 
     </sect2>
 
     <sect2>
       <title>I18N Applications</title>
 
       <para>In the FreeBSD Ports and Package system, I18N applications
 	have been named with <literal>I18N</literal> in their names for
 	easy identification.  However, they do not always support the
 	language needed.</para>
     </sect2>
 
     <sect2 id="setting-locale">
       <title>Setting Locale</title>
 
       <para>Usually it is sufficient to export the value of the locale name
         as <envar>LANG</envar> in the login shell.  This could be done in
 	the user's <filename>~/.login_conf</filename> file or in the
 	startup file of the user's shell (<filename>~/.profile</filename>,
 	<filename>~/.bashrc</filename>, <filename>~/.cshrc</filename>).
 	There is no need to set the locale subsets such as
 	<envar>LC_CTYPE</envar>, <envar>LC_CTIME</envar>.  Please
 	refer to language-specific FreeBSD documentation for more
 	information.</para>
 
       <para>You should set the following two environment variables in your configuration
 	files:</para>
 
       <itemizedlist>
-        <indexterm><primary>POSIX</primary></indexterm>
         <listitem>
-	  <para><envar>LANG</envar> for &posix; &man.setlocale.3; family
+	  <para><envar>LANG</envar> for &posix;<indexterm><primary>POSIX</primary></indexterm> &man.setlocale.3; family
 	    functions</para>
 	</listitem>
 
 	<listitem>
-	  <indexterm><primary>MIME</primary></indexterm>
-
-	  <para><envar>MM_CHARSET</envar> for applications' MIME character
+	  <para><envar>MM_CHARSET</envar> for applications' MIME<indexterm><primary>MIME</primary></indexterm> character
 	    set</para>
 	</listitem>
       </itemizedlist>
 
       <para>This includes the user shell configuration, the specific application
         configuration, and the X11 configuration.</para>
 
       <sect3>
 	<title>Setting Locale Methods</title>
         <indexterm><primary>locale</primary></indexterm>
         <indexterm><primary>login class</primary></indexterm>
 
 	<para>There are two methods for setting locale, and both are
 	  described below.  The first (recommended one) is by assigning
 	  the environment variables in <link linkend="login-class">login
 	  class</link>, and the second is by adding the environment
 	  variable assignments to the system's shell <link
 	  linkend="startup-file">startup file</link>.</para>
 
 	<sect4 id="login-class">
 	  <title>Login Classes Method</title>
 
 	  <para>This method allows environment variables needed for locale
 	    name and MIME character sets to be assigned once for every
 	    possible shell instead of adding specific shell assignments to
 	    each shell's startup file.  <link linkend="usr-setup">User
 	    Level Setup</link> can be done by an user himself and <link
 	    linkend="adm-setup">Administrator Level Setup</link> require
 	    superuser privileges.</para>
 
 	  <sect5 id="usr-setup">
 	    <title>User Level Setup</title>
 
 	    <para>Here is a minimal example of a
 	      <filename>.login_conf</filename> file in user's home
 	      directory which has both variables set for Latin-1
 	      encoding:</para>
 
 	    <programlisting>me:\
 	:charset=ISO-8859-1:\
 	:lang=de_DE.ISO8859-1:</programlisting>
 
 	    <indexterm><primary>Traditional Chinese</primary><secondary>BIG-5 encoding</secondary></indexterm>
 	    <para>Here is an example of a
 	       <filename>.login_conf</filename> that sets the variables
 	       for Traditional Chinese in BIG-5 encoding.  Notice the many
 	       more variables set because some software does not respect
 	       locale variables correctly for Chinese, Japanese, and Korean.</para>
 
 	    <programlisting>#Users who do not wish to use monetary units or time formats
 #of Taiwan can manually change each variable
 me:\
 	:lang=zh_TW.Big5:\
 	:lc_all=zh_TW.Big:\
 	:lc_collate=zh_TW.Big5:\
 	:lc_ctype=zh_TW.Big5:\
 	:lc_messages=zh_TW.Big5:\
 	:lc_monetary=zh_TW.Big5:\
 	:lc_numeric=zh_TW.Big5:\
 	:lc_time=zh_TW.Big5:\
 	:charset=big5:\
 	:xmodifiers="@im=xcin": #Setting the XIM Input Server</programlisting>
 
 	    <para>See <link linkend="adm-setup">Administrator Level
 	      Setup</link> and &man.login.conf.5; for more details.</para>
 	  </sect5>
 
 	  <sect5 id="adm-setup">
 	    <title>Administrator Level Setup</title>
 
 	    <para>Verify that the user's login class in
 	      <filename>/etc/login.conf</filename> sets the correct
 	      language.  Make sure these settings
 	      appear in <filename>/etc/login.conf</filename>:</para>
 
 	    <programlisting><replaceable>language_name</replaceable>:<replaceable>accounts_title</replaceable>:\
 	:charset=<replaceable>MIME_charset</replaceable>:\
 	:lang=<replaceable>locale_name</replaceable>:\
 	:tc=default:</programlisting>
 
 	    <para>So sticking with our previous example using Latin-1, it
 	      would look like this:</para>
 
 	    <programlisting>german:German Users Accounts:\
 	:charset=ISO-8859-1:\
 	:lang=de_DE.ISO8859-1:\
 	:tc=default:</programlisting>
 
 	    <para>Before changing users Login Classes execute
 	      the following command</para>
 
 	    <screen>&prompt.root; <userinput>cap_mkdb /etc/login.conf</userinput></screen>
 
 	    <para>to make new configuration in
 	      <filename>/etc/login.conf</filename> visible to the system.</para>
 
 	    <bridgehead renderas="sect4">Changing Login Classes with &man.vipw.8;</bridgehead>
 
 	    <indexterm>
         <primary><command>vipw</command></primary>
       </indexterm>
 	    <para>Use <command>vipw</command> to add new users, and make
 	      the entry look like this:</para>
 
 	    <programlisting>user:password:1111:11:<replaceable>language</replaceable>:0:0:User Name:/home/user:/bin/sh</programlisting>
 
 	    <bridgehead renderas="sect4">Changing Login Classes with &man.adduser.8;</bridgehead>
 
 	    <indexterm>
         <primary><command>adduser</command></primary>
       </indexterm>
 	    <indexterm><primary>login class</primary></indexterm>
 	    <para>Use <command>adduser</command> to add new users, and do
 	      the following:</para>
 
 	    <itemizedlist>
 	      <listitem>
 		<para>Set <literal>defaultclass =
 		  <replaceable>language</replaceable></literal> in
 		  <filename>/etc/adduser.conf</filename>.  Keep in mind
 		  you must enter a <literal>default</literal> class for
 		  all users of other languages in this case.</para>
 	      </listitem>
 
 	      <listitem>
 		<para>An alternative variant is answering the specified
 		  language each time that
 <screen><prompt>Enter login class: default []: </prompt></screen>
 		  appears from &man.adduser.8;.</para>
 	      </listitem>
 
 	      <listitem>
 		<para>Another alternative is to use the following for each
 		  user of a different language that you wish to
 		  add:</para>
 
 		<screen>&prompt.root; <userinput>adduser -class <replaceable>language</replaceable></userinput></screen>
 	      </listitem>
 	    </itemizedlist>
 
 	    <bridgehead renderas="sect4">Changing Login Classes with &man.pw.8;</bridgehead>
 	    <indexterm>
         <primary><command>pw</command></primary>
       </indexterm>
 	    <para>If you use &man.pw.8; for adding new users, call it in
 	      this form:</para>
 
 	    <screen>&prompt.root; <userinput>pw useradd <replaceable>user_name</replaceable> -L <replaceable>language</replaceable></userinput></screen>
 	  </sect5>
 	</sect4>
 
 	<sect4 id="startup-file">
 	  <title>Shell Startup File Method</title>
 
 	  <note>
 	    <para>This method is not recommended because it requires a
 	      different setup for each possible shell program chosen.  Use
 	      the <link linkend="login-class">Login Class Method</link>
 	      instead.</para>
 	  </note>
 
 	  <indexterm><primary>MIME</primary></indexterm>
 	  <indexterm><primary>locale</primary></indexterm>
 	  <para>To add the locale name and MIME character set, just set
 	    the two environment variables shown below in the
 	    <filename>/etc/profile</filename> and/or
 	    <filename>/etc/csh.login</filename> shell startup files.  We
 	    will use the German language as an example below:</para>
 
 	  <para>In <filename>/etc/profile</filename>:</para>
 
 	  <programlisting><envar>LANG=de_DE.ISO8859-1; export LANG</envar>
 <envar>MM_CHARSET=ISO-8859-1; export MM_CHARSET</envar></programlisting>
 
 	  <para>Or in <filename>/etc/csh.login</filename>:</para>
 
 	  <programlisting><envar>setenv LANG de_DE.ISO8859-1</envar>
 <envar>setenv MM_CHARSET ISO-8859-1</envar></programlisting>
 
 	  <para>Alternatively, you can add the above instructions to
 	    <filename>/usr/share/skel/dot.profile</filename> (similar to
 	    what was used in <filename>/etc/profile</filename> above), or
 	    <filename>/usr/share/skel/dot.login</filename> (similar to
 	    what was used in <filename>/etc/csh.login</filename>
 	    above).</para>
 
 	  <para>For X11:</para>
 
 	  <para>In <filename>$HOME/.xinitrc</filename>:</para>
 
 	  <programlisting><envar>LANG=de_DE.ISO8859-1; export LANG</envar></programlisting>
 
 	  <para>Or:</para>
 
 	  <programlisting><envar>setenv LANG de_DE.ISO8859-1</envar></programlisting>
 
 	  <para>Depending on your shell (see above).</para>
 
 	</sect4>
       </sect3>
     </sect2>
 
     <sect2 id="setting-console">
       <title>Console Setup</title>
 
       <para>For all single C chars character sets, set the correct
 	console fonts in <filename>/etc/rc.conf</filename> for the
 	language in question with:</para>
 
       <programlisting>font8x16=<replaceable>font_name</replaceable>
 font8x14=<replaceable>font_name</replaceable>
 font8x8=<replaceable>font_name</replaceable></programlisting>
 
       <para>The <replaceable>font_name</replaceable> here is taken from
         the <filename>/usr/share/syscons/fonts</filename> directory,
 	without the <filename>.fnt</filename> suffix.</para>
 
       <indexterm>
         <primary><application>sysinstall</application></primary>
       </indexterm>
       <indexterm><primary>keymap</primary></indexterm>
       <indexterm><primary>screenmap</primary></indexterm>
       <para>Also be sure to set the correct keymap and screenmap for your
 	single C chars character set through
 	<command>sysinstall</command> (<command>/stand/sysinstall</command>
 	in &os; versions older than 5.2).
 	Once inside <application>sysinstall</application>, choose <guimenuitem>Configure</guimenuitem>, then
 	<guimenuitem>Console</guimenuitem>.  Alternatively, you can add the
 	following to <filename>/etc/rc.conf</filename>:</para>
 
       <programlisting>scrnmap=<replaceable>screenmap_name</replaceable>
 keymap=<replaceable>keymap_name</replaceable>
 keychange="<replaceable>fkey_number sequence</replaceable>"</programlisting>
 
       <para>The <replaceable>screenmap_name</replaceable> here is taken
         from the <filename>/usr/share/syscons/scrnmaps</filename>
 	directory, without the <filename>.scm</filename> suffix.  A
 	screenmap with a corresponding mapped font is usually needed as a
 	workaround for expanding bit 8 to bit 9 on a VGA adapter's font
 	character matrix in pseudographics area, i.e., to move letters out
 	of that area if screen font uses a bit 8 column.</para>
 
       <para>If you have the <application>moused</application> daemon
 	enabled by setting the following
 	in your <filename>/etc/rc.conf</filename>:</para>
 
 <programlisting>moused_enable="YES"</programlisting>
 
       <para>then examine the mouse cursor information in the next
 	paragraph.</para>
 
       <indexterm>
         <primary><application>moused</application></primary>
       </indexterm>
       <para>By default the mouse cursor of the &man.syscons.4; driver occupies the
 	0xd0-0xd3 range in the character set.  If your language uses this
 	range, you need to move the cursor's range outside of it.  To enable
 	the workaround for &os;, add the following line to
 	<filename>/etc/rc.conf</filename>:</para>
 
       <programlisting>mousechar_start=3</programlisting>
 
       <para>The <replaceable>keymap_name</replaceable> here is taken from
         the <filename>/usr/share/syscons/keymaps</filename> directory,
 	without the <filename>.kbd</filename> suffix.  If you are
 	uncertain which keymap to use, you use can &man.kbdmap.1; to test
 	keymaps without rebooting.</para>
 
       <para>The <literal>keychange</literal> is usually needed to program
         function keys to match the selected terminal type because
 	function key sequences cannot be defined in the key map.</para>
 
       <para>Also be sure to set the correct console terminal type in
         <filename>/etc/ttys</filename> for all <literal>ttyv*</literal>
 	entries.  Current pre-defined correspondences are:</para>
 
       <informaltable frame="none" pgwide="1">
 	<tgroup cols="2">
 	  <thead>
 	    <row>
 	      <entry>Character Set</entry>
 	      <entry>Terminal Type</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry>ISO8859-1 or ISO8859-15</entry>
 	      <entry><literal>cons25l1</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry>ISO8859-2</entry>
 	      <entry><literal>cons25l2</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry>ISO8859-7</entry>
 	      <entry><literal>cons25l7</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry>KOI8-R</entry>
 	      <entry><literal>cons25r</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry>KOI8-U</entry>
 	      <entry><literal>cons25u</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry>CP437 (VGA default)</entry>
 	      <entry><literal>cons25</literal></entry>
 	    </row>
 
 	    <row>
 	      <entry>US-ASCII</entry>
 	      <entry><literal>cons25w</literal></entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
 
       <para>For wide or multibyte characters languages, use the correct
 	FreeBSD port in your
 	<filename>/usr/ports/<replaceable>language</replaceable></filename>
 	directory.  Some ports appear as console while the system sees it
 	as serial vtty's, hence you must reserve enough vtty's for both
 	X11 and the pseudo-serial console.  Here is a partial list of
 	applications for using other languages in console:</para>
 
       <informaltable frame="none" pgwide="1">
 	<tgroup cols="2">
 	  <thead>
 	    <row>
 	      <entry>Language</entry>
 	      <entry>Location</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry>Traditional Chinese (BIG-5)</entry>
 	      <entry><filename role="package">chinese/big5con</filename></entry>
 	    </row>
 
 	    <row>
 	      <entry>Japanese</entry>
 	      <entry><filename role="package">japanese/kon2-16dot</filename> or
 	        <filename role="package">japanese/mule-freewnn</filename></entry>
 	    </row>
 
 	    <row>
 	      <entry>Korean</entry>
 	      <entry><filename role="package">korean/han</filename></entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
     </sect2>
 
     <sect2>
       <title>X11 Setup</title>
 
       <para>Although X11 is not part of the FreeBSD Project, we have
 	included some information here for FreeBSD users.  For more
 	details, refer to the <ulink
 	url="http://www.x.org/">&xorg;
 	web site</ulink> or whichever X11 Server you use.</para>
 
       <para>In <filename>~/.Xresources</filename>, you can additionally
 	tune application specific I18N settings (e.g., fonts, menus,
 	etc.).</para>
 
       <sect3>
 	<title>Displaying Fonts</title>
 	<indexterm><primary>X11 True Type font server</primary></indexterm>
 	<para>Install <application>&xorg;</application> server
 	  (<filename role="package">x11-servers/xorg-server</filename>)
 	  or <application>&xfree86;</application> server
 	  (<filename role="package">x11-servers/XFree86-4-Server</filename>),
 	  then install the language &truetype; fonts.  Setting the correct
 	  locale should allow you to view your selected language in menus
 	  and such.</para>
       </sect3>
 
       <sect3>
 	<title>Inputting Non-English Characters</title>
 	<indexterm><primary>X11 Input Method (XIM)</primary></indexterm>
 	<para>The X11 Input Method (XIM) Protocol is a new standard for
 	  all X11 clients.  All X11 applications should be written as XIM
 	  clients that take input from XIM Input servers.  There are
 	  several XIM servers available for different languages.</para>
       </sect3>
     </sect2>
 
     <sect2>
       <title>Printer Setup</title>
 
       <para>Some single C chars character sets are usually hardware
 	coded into printers. Wide or multibyte
 	character sets require special setup and we recommend using
 	<application>apsfilter</application>.  You may also convert the
 	document to &postscript; or PDF formats using language specific
 	converters.</para>
     </sect2>
 
     <sect2>
       <title>Kernel and File Systems</title>
 
       <para>The FreeBSD fast filesystem (FFS) is 8-bit clean, so it can be used
 	with any single C chars character set (see &man.multibyte.3;),
 	but there is no character set
 	name stored in the filesystem; i.e., it is raw 8-bit and does not
 	know anything about encoding order.  Officially, FFS does not
 	support any form of wide or multibyte character sets yet.  However, some
 	wide or multibyte character sets have independent patches for FFS
 	enabling such support.  They are only temporary unportable
 	solutions or hacks and we have decided to not include them in the
 	source tree.  Refer to respective languages' web sites for more
 	information and the patch files.</para>
 
       <indexterm><primary>DOS</primary></indexterm>
       <indexterm><primary>Unicode</primary></indexterm>
       <para>The FreeBSD &ms-dos; filesystem has the configurable ability to
 	convert between &ms-dos;, Unicode character sets and chosen
 	FreeBSD filesystem character sets.  See &man.mount.msdos.8; for
 	details.</para>
     </sect2>
   </sect1>
 
   <sect1 id="l10n-compiling">
     <title>Compiling I18N Programs</title>
 
     <para>Many FreeBSD Ports have been ported with I18N support.  Some
       of them are marked with -I18N in the port name.  These and many
       other programs have built in support for I18N and need no special
       consideration.</para>
 
     <indexterm>
       <primary><application>MySQL</application></primary>
     </indexterm>
     <para>However, some applications such as
       <application>MySQL</application> need to be have the
       <filename>Makefile</filename> configured with the specific
       charset.  This is usually done in the
       <filename>Makefile</filename> or done by passing a value to
       <application>configure</application> in the source.</para>
   </sect1>
 
   <sect1 id="lang-setup">
     <title>Localizing FreeBSD to Specific Languages</title>
 
     <sect2 id="ru-localize">
       <sect2info>
 	<authorgroup>
 	  <author>
 	    <firstname>Andrey</firstname>
 	    <surname>Chernov</surname>
 	    <contrib>Originally contributed by </contrib>
 	  </author>
 	</authorgroup>
       </sect2info>
       <title>Russian Language (KOI8-R Encoding)</title>
       <indexterm>
 	<primary>localization</primary>
 	<secondary>Russian</secondary>
       </indexterm>
 
       <para>For more information about KOI8-R encoding, see the <ulink
 	url="http://koi8.pp.ru/">KOI8-R References
 	(Russian Net Character Set)</ulink>.</para>
 
       <sect3>
 	<title>Locale Setup</title>
 
 	<para>Put the following lines into your
 	  <filename>~/.login_conf</filename> file:</para>
 
 	<programlisting>me:My Account:\
 	:charset=KOI8-R:\
 	:lang=ru_RU.KOI8-R:</programlisting>
 
 	<para>See earlier in this chapter for examples of setting up the
 	  <link linkend="setting-locale">locale</link>.</para>
       </sect3>
 
       <sect3>
 	<title>Console Setup</title>
 
 	<itemizedlist>
 	  <listitem>
 	    <para>Add the following line
 	      to your <filename>/etc/rc.conf</filename> file:</para>
 
 	    <programlisting>mousechar_start=3</programlisting>
 	  </listitem>
 
 	  <listitem>
 	    <para>Also, use following settings in
 	      <filename>/etc/rc.conf</filename>:</para>
 
 	    <programlisting>keymap="ru.koi8-r"
 scrnmap="koi8-r2cp866"
 font8x16="cp866b-8x16"
 font8x14="cp866-8x14"
 font8x8="cp866-8x8"</programlisting>
 
 	  </listitem>
 
 	  <listitem>
 	    <para>For each <literal>ttyv*</literal> entry in
 	      <filename>/etc/ttys</filename>, use
 	      <literal>cons25r</literal> as the terminal type.</para>
 	  </listitem>
 	</itemizedlist>
 
 	<para>See earlier in this chapter for examples of setting up the
 	  <link linkend="setting-console">console</link>.</para>
       </sect3>
 
       <sect3>
 	<title>Printer Setup</title>
 	<indexterm><primary>printers</primary></indexterm>
 	<para>Since most printers with Russian characters come with
 	  hardware code page CP866, a special output filter is needed
 	  to convert from KOI8-R to CP866.  Such a filter is installed by
 	  default as <filename>/usr/libexec/lpr/ru/koi2alt</filename>.
 	  A Russian printer <filename>/etc/printcap</filename> entry
 	  should look like:</para>
 
 	<programlisting>lp|Russian local line printer:\
 	:sh:of=/usr/libexec/lpr/ru/koi2alt:\
 	:lp=/dev/lpt0:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs:</programlisting>
 
 	<para>See &man.printcap.5; for a detailed description.</para>
       </sect3>
 
       <sect3>
 	<title>&ms-dos; FS and Russian Filenames</title>
 
 	<para>The following example &man.fstab.5; entry enables support
 	  for Russian filenames in mounted &ms-dos; filesystems:</para>
 
 	<programlisting>/dev/ad0s2      /dos/c  msdos   rw,-Wkoi2dos,-Lru_RU.KOI8-R 0 0</programlisting>
 
 	<para>The option <option>-L</option> selects the locale name
 	  used, and <option>-W</option> sets the character conversion
 	  table.  To use the <option>-W</option> option, be sure to
 	  mount <filename>/usr</filename> before the &ms-dos; partition
 	  because the conversion tables are located in
 	  <filename>/usr/libdata/msdosfs</filename>.  For more
 	  information, see the &man.mount.msdos.8; manual
 	  page.</para>
       </sect3>
 
       <sect3>
 	<title>X11 Setup</title>
 
 	<orderedlist>
 	  <listitem>
 	    <para>Do <link linkend="setting-locale">non-X locale
 	      setup</link> first as described.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>If you use <application>&xorg;</application>,
 	    install
 	    <filename role="package">x11-fonts/xorg-fonts-cyrillic</filename>
 	    package.</para>
 
 	    <para>Check the <literal>"Files"</literal> section
 	      in your <filename>/etc/X11/xorg.conf</filename> file.
 	      The following
 	      lines must be added <emphasis>before</emphasis> any other
 	      <literal>FontPath</literal> entries:</para>
 
 	    <programlisting>FontPath   "/usr/X11R6/lib/X11/fonts/cyrillic/misc"
 FontPath   "/usr/X11R6/lib/X11/fonts/cyrillic/75dpi"
 FontPath   "/usr/X11R6/lib/X11/fonts/cyrillic/100dpi"</programlisting>
 
 	    <para>If you use a high resolution video mode, swap the 75 dpi
 	      and 100 dpi lines.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>To activate a Russian keyboard, add the following to the
 	      <literal>"Keyboard"</literal> section of your
 	      <filename>xorg.conf</filename> file.</para>
 
 	    <programlisting>Option "XkbLayout"   "us,ru"
 Option "XkbOptions"  "grp:toggle"</programlisting>
 
 	    <para>Also make sure that <literal>XkbDisable</literal> is
 	      turned off (commented out) there.</para>
 
 	    <para>For <literal>grp:caps_toggle</literal>
 	    the RUS/LAT switch will be <keycap>CapsLock</keycap>.
 	    The old <keycap>CapsLock</keycap> function is still
 	    available via <keycombo action="simul"><keycap>Shift</keycap><keycap>CapsLock</keycap></keycombo> (in LAT mode
 	      only). For <literal>grp:toggle</literal>
 	    the RUS/LAT switch will be <keycap>Right Alt</keycap>.
 	    <literal>grp:caps_toggle</literal> does not work in
 	    <application>&xorg;</application> for unknown reason.</para>
 
 	    <para>If you have <quote>&windows;</quote> keys on your keyboard,
 	      and notice that some non-alphabetical keys are mapped
 	      incorrectly in RUS mode, add the following line in your
 	      <filename>xorg.conf</filename> file.</para>
 
 	<programlisting>Option "XkbVariant" ",winkeys"</programlisting>
 
 	    <note>
 	      <para>The Russian XKB keyboard may not work with non-localized
 		applications.</para>
 	    </note>
 	  </listitem>
 	</orderedlist>
 	<note>
 	  <para>Minimally localized applications
 	    should call a <function>XtSetLanguageProc (NULL, NULL,
 	    NULL);</function> function early in the program.</para>
 	  <para>See <ulink
 	    url="http://koi8.pp.ru/xwin.html">
 	    KOI8-R for X Window</ulink> for more instructions on
 	    localizing X11 applications.</para>
 	</note>
       </sect3>
     </sect2>
 
     <sect2>
       <title>Traditional Chinese Localization for Taiwan</title>
       <indexterm>
 	<primary>localization</primary>
 	<secondary>Traditional Chinese</secondary>
       </indexterm>
       <para>The FreeBSD-Taiwan Project has an Chinese HOWTO for
 	FreeBSD at <ulink url="http://netlab.cse.yzu.edu.tw/~statue/freebsd/zh-tut/"></ulink>
 	using many Chinese ports.
 	Current editor for the <literal>FreeBSD Chinese HOWTO</literal> is
         Shen Chuan-Hsing <email>statue@freebsd.sinica.edu.tw</email>.
       </para>
 
       <para>Chuan-Hsing Shen <email>statue@freebsd.sinica.edu.tw</email> has
 	created the <ulink url="http://netlab.cse.yzu.edu.tw/~statue/cfc/">
 	Chinese FreeBSD Collection (CFC)</ulink> using FreeBSD-Taiwan's
 	<literal>zh-L10N-tut</literal>.  The packages and the script files
 	are available at <ulink url="ftp://freebsd.csie.nctu.edu.tw/pub/taiwan/CFC/"></ulink>.</para>
     </sect2>
 
     <sect2>
       <title>German Language Localization (for All ISO 8859-1
 	Languages)</title>
       <indexterm>
 	<primary>localization</primary>
 	<secondary>German</secondary>
       </indexterm>
 
       <para>Slaven Rezic <email>eserte@cs.tu-berlin.de</email> wrote a
 	tutorial how to use umlauts on a FreeBSD machine.  The tutorial
 	is written in German and available at
 	<ulink url="http://www.de.FreeBSD.org/de/umlaute/"></ulink>.</para>
     </sect2>
 
     <sect2>
       <title>Japanese and Korean Language Localization</title>
       <indexterm>
 	<primary>localization</primary>
 	<secondary>Japanese</secondary>
       </indexterm>
       <indexterm>
 	<primary>localization</primary>
 	<secondary>Korean</secondary>
       </indexterm>
       <para>For Japanese, refer to
         <ulink url="http://www.jp.FreeBSD.org/"></ulink>,
 	and for Korean, refer to
 	<ulink url="http://www.kr.FreeBSD.org/"></ulink>.</para>
     </sect2>
 
     <sect2>
       <title>Non-English FreeBSD Documentation</title>
 
       <para>Some FreeBSD contributors have translated parts of FreeBSD to
 	other languages.  They are available through links on the <ulink
 	url="&url.base;/index.html">main site</ulink> or in
 	<filename>/usr/share/doc</filename>.</para>
     </sect2>
   </sect1>
 </chapter>
diff --git a/zh_TW.Big5/books/handbook/mail/chapter.xml b/zh_TW.Big5/books/handbook/mail/chapter.xml
index 5d93615541..37966654b2 100644
--- a/zh_TW.Big5/books/handbook/mail/chapter.xml
+++ b/zh_TW.Big5/books/handbook/mail/chapter.xml
@@ -1,2300 +1,2299 @@
 <?xml version="1.0" encoding="big5"?>
 <!--
      The FreeBSD Documentation Project
 
      $FreeBSD$
      Original revision: 1.136
 -->
 
 <chapter id="mail">
   <chapterinfo>
     <authorgroup>
       <author>
 	<firstname>Bill</firstname>
 	<surname>Lloyd</surname>
 	<contrib>Original work by </contrib>
       </author>
     </authorgroup>
     <authorgroup>
       <author>
 	<firstname>Jim</firstname>
 	<surname>Mock</surname>
 	<contrib>Rewritten by </contrib>
 	<!-- 2 Dec 1999 -->
       </author>
     </authorgroup>
   </chapterinfo>
 
   <title>�q�l�l��</title>
 
   <sect1 id="mail-synopsis">
     <title>���z</title>
     <indexterm><primary>email</primary></indexterm>
 
     <para><quote>�q�l�l��</quote>�Ϊ̫U�٪� email�A
       �D�O�{���ϥγ̼s�x�����q�覡���@�C  �����D�n���Цp��b &os; �W�w�ˡB
       �]�w email �A�ȡA�H�Φp��b &os; ���o�H��F  �M�ӳo�ä��O���㪺�ѦҤ�U�A
       ��ڤW�\�h�ݦҶq�����n�ƶ��å����ΡA�Y���A�ѲӸ`�аѾ\ <xref
       linkend="bibliography"/> �����ѦҮ��y�C</para>
 
     <para>Ū���o���A�z�N�F�ѡJ</para>
 
     <itemizedlist>
       <listitem>
 	<para>���dzn�餸��P���o�q�l�l�����C</para>
       </listitem>
 
       <listitem>
 	<para>FreeBSD ���� <application>sendmail</application>
 	  �򥻳]�w�ɦb���C</para>
       </listitem>
 
       <listitem>
         <para>���ݫH�c�P�����H�c���ϧO�C</para>
       </listitem>
 
       <listitem>
 	<para>�p����� spammer(�U���l��s�y��)�D�k�B�αz���l����A���@��
 	  relay(��o���~�I)�C</para>
       </listitem>
 
       <listitem>
 	<para>�p��w�ˡB�]�w��L Mail Transfer Agent(MTA) �Ө��N
 	  <application>sendmail</application>�C</para>
       </listitem>
 
       <listitem>
 	<para>�p��B�z�`�����l����A�����D�C</para>
       </listitem>
 
       <listitem>
 	<para>�p��ϥ� UUCP �Ӷi�� SMTP�C</para>
       </listitem>
 
       <listitem>
 	<para>�p��]�w�t�ΡA�Ϩ�u��o�e�l��C</para>
       </listitem>
 
       <listitem>
 	<para>�p��b�����W�����Ҥ��A���o�l��C</para>
       </listitem>
 
       <listitem>
         <para>�p��]�w SMTP ���ҡA�H�[�j�w���ʡC</para>
       </listitem>
 
       <listitem>
         <para>�p��w�ˡB�ϥ� Mail User Agent(MUA) �{���A��p
 	  <application>mutt</application> �Ӧ��o�l��C</para>
       </listitem>
 
       <listitem>
 
         <para>�p��q���� <acronym>POP</acronym> �� <acronym>IMAP</acronym>
 	  �D���h�U���l��C</para>
       </listitem>
 
       <listitem>
         <para>�p��b���H�譱�A�۰ʮM�ζl��L�o�C</para>
       </listitem>
     </itemizedlist>
 
     <para>�b�}�l�\Ū�o�����e�A�z�ݭn�J</para>
 
     <itemizedlist>
       <listitem>
 	<para>���]�n�A������
 	  (<xref linkend="advanced-networking"/>)�C</para>
       </listitem>
 
       <listitem>
 	<para>�ॿ�T���l����A���]�w DNS
 	  (<xref linkend="network-servers"/>)�C</para>
       </listitem>
 
       <listitem>
 	<para>���D�p��z�L port/package �w�˳n��
 	  (<xref linkend="ports"/>)�C</para></listitem>
     </itemizedlist>
   </sect1>
 
   <sect1 id="mail-using">
     <title>�ϥιq�l�l��</title>
     <indexterm><primary>POP</primary></indexterm>
     <indexterm><primary>IMAP</primary></indexterm>
     <indexterm><primary>DNS</primary></indexterm>
 
     <para>�b email �洫���L�{���� 5 �ӥD�n�����A���O�O�G<link
       linkend="mail-mua">MUA</link>�B<link linkend="mail-mta">MTA</link>�B
       <link linkend="mail-dns">DNS</link>�B<link linkend="mail-receive">
       ���ݩΥ������H�c</link>�A���M�٦� <link linkend="mail-host">�l��D������
       </link>�C</para>
 
     <sect2 id="mail-mua">
       <title>MUA �{��</title>
 
       <para>�]�A�@�Ǥ�r�������{���A���O
 	<application>mutt</application>�B
 	<application>pine</application>�B<application>elm</application>�B
 	and <command>mail</command>�A�H�� <acronym>GUI</acronym> �������{���A
 	���O <application>balsa</application>�B
 	<application>xfmail</application> �����C  ���~�A�٦���
 	<quote>������</quote> ���O WWW �s�����C
 	�o�ǵ{���|�l��B�z�浹 <link
 	linkend="mail-host"><quote>�l��D��</quote></link>�A�Ϊ̳z�L�I�s
 	<link linkend="mail-mta">MTA</link>(�Y������)�Ϊ̬O�z�L
 	<acronym>TCP</acronym> �Ӷǻ��l��C</para>
     </sect2>
 
     <sect2 id="mail-mta">
       <title>Mailhost Server Daemon</title>
       <indexterm>
         <primary>mail server daemons</primary>
         <secondary><application>sendmail</application></secondary>
       </indexterm>
       <indexterm>
         <primary>mail server daemons</primary>
         <secondary><application>postfix</application></secondary>
       </indexterm>
       <indexterm>
         <primary>mail server daemons</primary>
         <secondary><application>qmail</application></secondary>
       </indexterm>
       <indexterm>
         <primary>mail server daemons</primary>
         <secondary><application>exim</application></secondary>
       </indexterm>
 
       <para>&os; ships with <application>sendmail</application> by
 	default, but also support numerous other mail server daemons,
 	just some of which include:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><application>exim</application>;</para>
 	</listitem>
 
 	<listitem>
 	  <para><application>postfix</application>;</para>
 	</listitem>
 
 	<listitem>
 	  <para><application>qmail</application>.</para>
 	</listitem>
       </itemizedlist>
 
       <para>The server daemon usually has two functions&mdash;it is responsible
 	for receiving incoming mail as well as delivering outgoing mail.  It is
 	<emphasis>not</emphasis> responsible for the collection of mail using protocols
 	such as <acronym>POP</acronym> or <acronym>IMAP</acronym> to
 	read your email, nor does it allow connecting to local
 	<filename>mbox</filename> or Maildir mailboxes.  You may require
 	an additional <link linkend="mail-receive">daemon</link> for
 	that.</para>
 
       <warning>
 	<para>Older versions of <application>sendmail</application>
 	  have some serious security issues which may result in an
 	  attacker gaining local and/or remote access to your machine.
 	  Make sure that you are running a current version to avoid
 	  these problems.  Optionally, install an alternative
 	  <acronym>MTA</acronym> from the <link linkend="ports">&os;
 	  Ports Collection</link>.</para>
       </warning>
     </sect2>
 
     <sect2 id="mail-dns">
       <title>Email and DNS</title>
 
       <para>The Domain Name System (DNS) and its daemon
         <command>named</command> play a large role in the delivery of
 	email.  In order to deliver mail from your site to another, the
 	server daemon will look up the remote site in the DNS to determine the
 	host that will receive mail for the destination.  This process
 	also occurs when mail is sent from a remote host to your mail
 	server.</para>
 
       <indexterm>
 	<primary>MX record</primary>
       </indexterm>
 
       <para><acronym>DNS</acronym> is responsible for mapping
 	hostnames to IP addresses, as well as for storing information
 	specific to mail delivery, known as MX records.  The MX (Mail
 	eXchanger) record specifies which host, or hosts, will receive
 	mail for a particular domain.  If you do not have an MX record
 	for your hostname or domain, the mail will be delivered
 	directly to your host provided you have an A record pointing
 	your hostname to your IP address.</para>
 
       <para>You may view the MX records for any domain by using the
 	&man.host.1; command, as seen in the example below:</para>
 
       <screen>&prompt.user; <userinput>host -t mx FreeBSD.org</userinput>
 FreeBSD.org mail is handled (pri=10) by mx1.FreeBSD.org</screen>
     </sect2>
 
     <sect2 id="mail-receive">
       <title>Receiving Mail</title>
       <indexterm>
         <primary>email</primary>
         <secondary>receiving</secondary>
       </indexterm>
 
       <para>Receiving mail for your domain is done by the mail host.  It
 	will collect all mail sent to your domain and store it
 	either in <filename>mbox</filename> (the default method for storing mail) or Maildir format, depending
 	on your configuration.
 	Once mail has been stored, it may either be read locally using
 	applications such as &man.mail.1; or
 	<application>mutt</application>, or remotely accessed and
 	collected using protocols such as
 	<acronym>POP</acronym> or <acronym>IMAP</acronym>.
 	This means that should you only
 	wish to read mail locally, you are not required to install a
 	<acronym>POP</acronym> or <acronym>IMAP</acronym> server.</para>
 
       <sect3 id="pop-and-imap">
         <title>Accessing remote mailboxes using <acronym>POP</acronym> and <acronym>IMAP</acronym></title>
 
         <indexterm><primary>POP</primary></indexterm>
         <indexterm><primary>IMAP</primary></indexterm>
 	<para>In order to access mailboxes remotely, you are required to
 	  have access to a <acronym>POP</acronym> or <acronym>IMAP</acronym>
 	  server.  These protocols allow users to connect to their mailboxes from
 	  remote locations with ease.  Though both
 	  <acronym>POP</acronym> and <acronym>IMAP</acronym> allow users
 	  to remotely access mailboxes, <acronym>IMAP</acronym> offers
 	  many advantages, some of which are:</para>
 
         <itemizedlist>
           <listitem>
 	    <para><acronym>IMAP</acronym> can store messages on a remote
 	      server as well as fetch them.</para>
           </listitem>
 
           <listitem>
 	    <para><acronym>IMAP</acronym> supports concurrent updates.</para>
           </listitem>
 
           <listitem>
 	    <para><acronym>IMAP</acronym> can be extremely useful over
 	      low-speed links as it allows users to fetch the structure
 	      of messages without downloading them; it can also
 	      perform tasks such as searching on the server in
 	      order to minimize data transfer between clients and
 	      servers.</para>
           </listitem>
 
         </itemizedlist>
 
         <para>In order to install a <acronym>POP</acronym> or
 	  <acronym>IMAP</acronym> server, the following steps should be
 	  performed:</para>
 
         <procedure>
 	  <step>
 	    <para>Choose an <acronym>IMAP</acronym> or
 	      <acronym>POP</acronym> server that best suits your needs.
 	      The following <acronym>POP</acronym> and
 	      <acronym>IMAP</acronym> servers are well known and serve
 	      as some good examples:</para>
 
 	      <itemizedlist>
 	        <listitem>
 		  <para><application>qpopper</application>;</para>
 	        </listitem>
 
 	        <listitem>
 		  <para><application>teapop</application>;</para>
 	        </listitem>
 
 	        <listitem>
 		  <para><application>imap-uw</application>;</para>
 	        </listitem>
 
 	        <listitem>
 		  <para><application>courier-imap</application>;</para>
 	        </listitem>
 	      </itemizedlist>
 
 	  </step>
 
           <step>
 	    <para>Install the <acronym>POP</acronym> or
 	      <acronym>IMAP</acronym> daemon of your choosing from the
 	      ports
 	      collection.</para>
 	  </step>
 
 	  <step>
 	    <para>Where required, modify <filename>/etc/inetd.conf</filename>
 	      to load the <acronym>POP</acronym> or
 	      <acronym>IMAP</acronym> server.</para>
 	  </step>
         </procedure>
 
 	<warning>
 	  <para>It should be noted that both <acronym>POP</acronym> and
 	    <acronym>IMAP</acronym> transmit information, including
 	    username and password credentials in clear-text.  This means
 	    that if you wish to secure the transmission of information
 	    across these protocols, you should consider tunneling
 	    sessions over &man.ssh.1;.  Tunneling sessions is
 	    described in <xref linkend="security-ssh-tunneling"/>.</para>
         </warning>
       </sect3>
 
       <sect3 id="local">
         <title>Accessing local mailboxes</title>
 
 	<para>Mailboxes may be accessed locally by directly utilizing
 	  <acronym>MUA</acronym>s on the server on which the mailbox
 	  resides.  This can be done using applications such as
 	  <application>mutt</application> or &man.mail.1;.
 	</para>
       </sect3>
     </sect2>
 
     <sect2 id="mail-host">
       <title>The Mail Host</title>
       <indexterm><primary>mail host</primary></indexterm>
 
       <para>The mail host is the name given to a server that is
         responsible for delivering and receiving mail for your host, and
 	possibly your network.</para>
     </sect2>
   </sect1>
 
   <sect1 id="sendmail">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Christopher</firstname>
           <surname>Shumway</surname>
           <contrib>Contributed by </contrib>
         </author>
       </authorgroup>
     </sect1info>
     <title><application>sendmail</application> Configuration</title>
 
     <indexterm>
       <primary><application>sendmail</application></primary>
     </indexterm>
 
     <para>&man.sendmail.8; is the default Mail Transfer Agent (MTA) in
       FreeBSD.  <application>sendmail</application>'s job is to accept
       mail from Mail User Agents (<acronym>MUA</acronym>) and deliver it
       to the appropriate mailer as defined by its configuration file.
       <application>sendmail</application> can also accept network
       connections and deliver mail to local mailboxes or deliver it to
       another program.</para>
 
     <para><application>sendmail</application> uses the following
       configuration files:</para>
 
     <indexterm>
       <primary><filename>/etc/mail/access</filename></primary>
     </indexterm>
     <indexterm>
       <primary><filename>/etc/mail/aliases</filename></primary>
     </indexterm>
     <indexterm>
       <primary><filename>/etc/mail/local-host-names</filename></primary>
     </indexterm>
     <indexterm>
       <primary><filename>/etc/mail/mailer.conf</filename></primary>
     </indexterm>
     <indexterm>
       <primary><filename>/etc/mail/mailertable</filename></primary>
     </indexterm>
     <indexterm>
       <primary><filename>/etc/mail/sendmail.cf</filename></primary>
     </indexterm>
     <indexterm>
       <primary><filename>/etc/mail/virtusertable</filename></primary>
     </indexterm>
     <informaltable frame="none" pgwide="1">
       <tgroup cols="2">
 	<thead>
 	  <row>
 	    <entry>Filename</entry>
 	    <entry>Function</entry>
 	  </row>
 	</thead>
 	<tbody>
 	  <row>
 	    <entry>
 	      <filename>/etc/mail/access</filename>
 	    </entry>
 	    <entry><application>sendmail</application> access database
  	      file</entry>
 	  </row>
 	  <row>
 	    <entry>
 	      <filename>/etc/mail/aliases</filename>
 	    </entry>
 	    <entry>Mailbox aliases</entry>
 	  </row>
 	  <row>
 	    <entry>
 	      <filename>/etc/mail/local-host-names</filename>
 	    </entry>
 	    <entry>Lists of hosts <application>sendmail</application>
 	    accepts mail for</entry>
     </row>
 	  <row>
 	    <entry>
 	      <filename>/etc/mail/mailer.conf</filename>
 	    </entry>
 	    <entry>Mailer program configuration</entry>
 	  </row>
 	  <row>
 	    <entry>
 	      <filename>/etc/mail/mailertable</filename>
 	    </entry>
 	    <entry>Mailer delivery table</entry>
 	  </row>
 	  <row>
 	    <entry>
 	      <filename>/etc/mail/sendmail.cf</filename>
 	    </entry>
 	    <entry><application>sendmail</application> master
 	    configuration file</entry>
 	  </row>
 	  <row>
 	    <entry>
 	      <filename>/etc/mail/virtusertable</filename>
 	    </entry>
 	    <entry>Virtual users and domain tables</entry>
 	  </row>
 	</tbody>
       </tgroup>
     </informaltable>
 
   <sect2>
     <title><filename>/etc/mail/access</filename></title>
 
     <para>The access database defines what host(s) or IP addresses
       have access to the local mail server and what kind of access
       they have.  Hosts can be listed as <option>OK</option>,
       <option>REJECT</option>, <option>RELAY</option> or simply passed
       to <application>sendmail</application>'s error handling routine with a given mailer error.
       Hosts that are listed as <option>OK</option>, which is the
       default, are allowed to send mail to this host as long as the
       mail's final destination is the local machine.  Hosts that are
       listed as <option>REJECT</option> are rejected for all mail
       connections.  Hosts that have the <option>RELAY</option> option
       for their hostname are allowed to send mail for any destination
       through this mail server.</para>
 
       <example>
 	<title>Configuring the <application>sendmail</application>
   	  Access Database</title>
 
     <programlisting>cyberspammer.com                550 We do not accept mail from spammers
 FREE.STEALTH.MAILER@            550 We do not accept mail from spammers
 another.source.of.spam          REJECT
 okay.cyberspammer.com           OK
 128.32                          RELAY</programlisting>
       </example>
 
    <para>In this example we have five entries.  Mail senders that
      match the left hand side of the table are affected by the action
      on the right side of the table.  The first two examples give an
      error code to <application>sendmail</application>'s error
      handling routine.  The message is printed to the remote host when
      a mail matches the left hand side of the table.  The next entry
      rejects mail from a specific host on the Internet,
      <hostid>another.source.of.spam</hostid>.  The next entry accepts
      mail connections from a host
      <hostid role="fqdn">okay.cyberspammer.com</hostid>, which is more exact than
      the <hostid role="domainname">cyberspammer.com</hostid> line above.  More specific
      matches override less exact matches.  The last entry allows
      relaying of electronic mail from hosts with an IP address that
      begins with <hostid>128.32</hostid>.  These hosts would be able
      to send mail through this mail server that are destined for other
      mail servers.</para>
 
    <para>When this file is updated, you need to run
      <command>make</command> in <filename>/etc/mail/</filename> to
      update the database.</para>
 
    </sect2>
    <sect2>
     <title><filename>/etc/mail/aliases</filename></title>
 
     <para>The aliases database contains a list of virtual mailboxes
       that are expanded to other user(s), files, programs or other
       aliases.  Here are a few examples that can be used in
       <filename>/etc/mail/aliases</filename>:</para>
 
       <example>
 	<title>Mail Aliases</title>
     <programlisting>root: localuser
 ftp-bugs: joe,eric,paul
 bit.bucket:  /dev/null
 procmail: "|/usr/local/bin/procmail"</programlisting>
       </example>
 
       <para>The file format is simple; the mailbox name on the left
 	side of	the colon is expanded to the target(s) on the right.
 	The
 	first example simply expands the mailbox <username>root</username>
 	to the mailbox <username>localuser</username>, which is then
 	looked up again in the aliases database.  If no match is found,
 	then the message is delivered to the local user
 	<username>localuser</username>.  The next example shows a mail
 	list.  Mail to the mailbox <username>ftp-bugs</username> is
 	expanded to the three local mailboxes <username>joe</username>,
 	<username>eric</username>, and <username>paul</username>.  Note
 	that a remote mailbox could be specified as <email>user@example.com</email>.  The
 	next example shows writing mail to a file, in this case
 	<filename>/dev/null</filename>.  The last example shows sending
 	mail to a program, in this case the mail message is written to the
 	standard input of <filename>/usr/local/bin/procmail</filename>
 	through a &unix; pipe.</para>
 
    <para>When this file is updated, you need to run
    <command>make</command> in <filename>/etc/mail/</filename> to
    update the database.</para>
   </sect2>
   <sect2>
     <title><filename>/etc/mail/local-host-names</filename></title>
 
     <para>This is a list of hostnames &man.sendmail.8; is to accept as
       the local host name.  Place any domains or hosts that
       <application>sendmail</application> is to be receiving mail for.
       For example, if this mail server was to accept mail for the
       domain <hostid role="domainname">example.com</hostid> and the host
       <hostid role="fqdn">mail.example.com</hostid>, its
       <filename>local-host-names</filename> might look something like
       this:</para>
 
     <programlisting>example.com
 mail.example.com</programlisting>
 
     <para>When this file is updated, &man.sendmail.8; needs to be
     restarted to read the changes.</para>
 
   </sect2>
 
   <sect2>
     <title><filename>/etc/mail/sendmail.cf</filename></title>
 
     <para><application>sendmail</application>'s master configuration
       file, <filename>sendmail.cf</filename> controls the overall
       behavior of <application>sendmail</application>, including everything
       from rewriting e-mail addresses to printing rejection messages to
       remote mail servers.  Naturally, with such a diverse role, this
       configuration file is quite complex and its details are a bit
       out of the scope of this section.  Fortunately, this file rarely
       needs to be changed for standard mail servers.</para>
 
     <para>The master <application>sendmail</application> configuration
       file can be built from &man.m4.1; macros that define the features
       and behavior of <application>sendmail</application>.  Please see
       <filename>/usr/src/contrib/sendmail/cf/README</filename> for
       some of the details.</para>
 
     <para>When changes to this file are made,
       <application>sendmail</application> needs to be restarted for
       the changes to take effect.</para>
 
   </sect2>
   <sect2>
     <title><filename>/etc/mail/virtusertable</filename></title>
 
     <para>The <filename>virtusertable</filename> maps mail addresses for
       virtual domains and
       mailboxes to real mailboxes.  These mailboxes can be local,
       remote, aliases defined in
       <filename>/etc/mail/aliases</filename> or files.</para>
 
     <example>
 	<title>Example Virtual Domain Mail Map</title>
 
     <programlisting>root@example.com                root
 postmaster@example.com          postmaster@noc.example.net
 @example.com                    joe</programlisting>
       </example>
 
     <para>In the above example, we have a mapping for a domain
       <hostid role="domainname">example.com</hostid>.  This file is processed in a
       first match order down the file.  The first item maps
       <email>root@example.com</email> to the local mailbox <username>root</username>.  The next entry maps
       <email>postmaster@example.com</email> to the mailbox <username>postmaster</username> on the host
       <hostid role="fqdn">noc.example.net</hostid>.  Finally, if nothing from <hostid role="domainname">example.com</hostid> has
       matched so far, it will match the last mapping, which matches
       every other mail message addressed to someone at
       <hostid role="domainname">example.com</hostid>.
       This will be mapped to the local mailbox <username>joe</username>.</para>
 
   </sect2>
   </sect1>
 
   <sect1 id="mail-changingmta">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Andrew</firstname>
           <surname>Boothman</surname>
           <contrib>Written by </contrib>
         </author>
       </authorgroup>
       <authorgroup>
         <author>
           <firstname>Gregory</firstname>
           <surname>Neil Shapiro</surname>
           <contrib>Information taken from e-mails written by </contrib>
         </author>
       </authorgroup>
     </sect1info>
     <title>Changing Your Mail Transfer Agent</title>
     <indexterm>
       <primary>email</primary>
       <secondary>change mta</secondary>
     </indexterm>
 
     <para>As already mentioned, FreeBSD comes with
       <application>sendmail</application> already installed as your
       MTA (Mail Transfer Agent).  Therefore by default it is
       in charge of your outgoing and incoming mail.</para>
 
     <para>However, for a variety of reasons, some system
       administrators want to change their system's MTA.  These
       reasons range from simply wanting to try out another MTA to
       needing a specific feature or package which relies on another
       mailer.  Fortunately, whatever the reason, FreeBSD makes it
       easy to make the change.</para>
 
     <sect2>
       <title>Install a New MTA</title>
 
       <para>You have a wide choice of MTAs available.  A good
 	starting point is the
 	<link linkend="ports">FreeBSD Ports Collection</link> where
 	you will be able to find many.  Of course you are free to use
 	any MTA you want from any location, as long as you can make
 	it run under FreeBSD.</para>
 
       <para>Start by installing your new MTA.  Once it is installed
 	it gives you a chance to decide if it really fulfills your
 	needs, and also gives you the opportunity to configure your
 	new software before getting it to take over from
 	<application>sendmail</application>.  When doing this, you
 	should be sure that installing the new software will not attempt
 	to overwrite system binaries such as
 	<filename>/usr/bin/sendmail</filename>.  Otherwise, your new
 	mail software has essentially been put into service before
 	you have configured it.</para>
 
       <para>Please refer to your chosen MTA's documentation for
 	information on how to configure the software you have
 	chosen.</para>
     </sect2>
 
     <sect2 id="mail-disable-sendmail">
       <title>Disable <application>sendmail</application></title>
 
       <para>The procedure used to start
 	<application>sendmail</application> changed significantly
 	between 4.5-RELEASE, 4.6-RELEASE, and later releases.
 	Therefore, the procedure used to disable it is subtly
 	different.</para>
 
 	<warning>
 	  <para>If you disable <application>sendmail</application>'s
 	    outgoing mail service, it is important that you replace it
 	    with an alternative mail delivery system.  If
 	    you choose not to, system functions such as &man.periodic.8;
 	    will be unable to deliver their results by e-mail as they
 	    would normally expect to.  Many parts of your system may
 	    expect to have a functional
 	    <application>sendmail</application>-compatible system.  If
 	    applications continue to use
 	    <application>sendmail</application>'s binaries to try to send
 	    e-mail after you have disabled them, mail could go into an
 	    inactive <application>sendmail</application> queue, and
 	    never be delivered.</para>
 	</warning>
 
       <sect3>
 	<title>FreeBSD 4.5-STABLE before 2002/4/4 and Earlier
 	  (Including 4.5-RELEASE and Earlier)</title>
 
 	<para>Enter:</para>
 
 	  <programlisting>sendmail_enable="NO"</programlisting>
 
 	  <para>into <filename>/etc/rc.conf</filename>.  This will disable
 	  <application>sendmail</application>'s incoming mail service,
 	  but if <filename>/etc/mail/mailer.conf</filename> (see below)
 	  is not changed, <application>sendmail</application> will
 	  still be used to send e-mail.</para>
       </sect3>
 
       <sect3>
 	<title>FreeBSD 4.5-STABLE after 2002/4/4
 	  (Including 4.6-RELEASE and Later)</title>
 
 	<para>In order to completely disable
 	  <application>sendmail</application>, including the outgoing
 	  mail service, you must use</para>
 
 	  <programlisting>sendmail_enable="NONE"</programlisting>
 
 	  <para>in <filename>/etc/rc.conf.</filename></para>
 
 	<para>If you only want to disable
 	  <application>sendmail</application>'s incoming mail service,
 	  you should set</para>
 
 	  <programlisting>sendmail_enable="NO"</programlisting>
 
 	<para>in <filename>/etc/rc.conf</filename>.  However, if
 	  incoming mail is disabled, local delivery will still
 	  function.  More information on
 	  <application>sendmail</application>'s startup options is
 	  available from the &man.rc.sendmail.8; manual page.</para>
       </sect3>
 
       <sect3>
 	<title>FreeBSD 5.0-STABLE and Later</title>
 
 	<para>In order to completely disable
 	  <application>sendmail</application>, including the outgoing
 	  mail service, you must use</para>
 
 	  <programlisting>sendmail_enable="NO"
 sendmail_submit_enable="NO"
 sendmail_outbound_enable="NO"
 sendmail_msp_queue_enable="NO"</programlisting>
 
 	  <para>in <filename>/etc/rc.conf.</filename></para>
 
 	<para>If you only want to disable
 	  <application>sendmail</application>'s incoming mail service,
 	  you should set</para>
 
 	  <programlisting>sendmail_enable="NO"</programlisting>
 
 	<para>in <filename>/etc/rc.conf</filename>.  More information on
 	  <application>sendmail</application>'s startup options is
 	  available from the &man.rc.sendmail.8; manual page.</para>
       </sect3>
     </sect2>
 
     <sect2>
       <title>Running Your New MTA on Boot</title>
 
       <para>You may have a choice of two methods for running your
 	new MTA on boot, again depending on what version of FreeBSD
 	you are running.</para>
 
       <sect3>
 	<title>FreeBSD 4.5-STABLE before 2002/4/11
 	  (Including 4.5-RELEASE and Earlier)</title>
 
 	<para>Add a script to
 	  <filename>/usr/local/etc/rc.d/</filename> that
 	  ends in <filename>.sh</filename> and is executable by
 	  <username>root</username>.  The script should accept <literal>start</literal> and
 	  <literal>stop</literal> parameters.  At startup time the
 	  system scripts will execute the command</para>
 
 	<programlisting>/usr/local/etc/rc.d/supermailer.sh start</programlisting>
 
 	<para>which you can also use to manually start the server.  At
 	  shutdown time, the system scripts will use the
 	  <literal>stop</literal> option, running the command</para>
 
 	<programlisting>/usr/local/etc/rc.d/supermailer.sh stop</programlisting>
 
 	<para>which you can also use to manually stop the server
 	  while the system is running.</para>
 
       </sect3>
 
       <sect3>
 	<title>FreeBSD 4.5-STABLE after 2002/4/11
 	  (Including 4.6-RELEASE and Later)</title>
 
 	<para>With later versions of FreeBSD, you can use the
 	  above method or you can set</para>
 
 	<programlisting>mta_start_script="filename"</programlisting>
 
 	<para>in <filename>/etc/rc.conf</filename>, where
 	  <replaceable>filename</replaceable> is the name of some
 	  script that you want executed at boot to start your
 	  MTA.</para>
       </sect3>
 
     </sect2>
 
     <sect2>
       <title>Replacing <application>sendmail</application> as
        the System's Default Mailer</title>
 
       <para>The program <application>sendmail</application> is so ubiquitous
 	as standard software on &unix; systems that some software
 	just assumes it is already installed and configured.
 	For this reason, many alternative MTA's provide their own compatible
 	implementations of the <application>sendmail</application>
 	command-line interface; this facilitates using them as
 	<quote>drop-in</quote> replacements for <application>sendmail</application>.</para>
 
       <para>Therefore, if you are using an alternative mailer,
 	you will need to make sure that software trying to execute
 	standard <application>sendmail</application> binaries such as
 	<filename>/usr/bin/sendmail</filename> actually executes
 	your chosen mailer instead.  Fortunately, FreeBSD provides
 	a system called &man.mailwrapper.8; that does this job for
 	you.</para>
 
       <para>When <application>sendmail</application> is operating as installed, you will
 	find something like the following
 	in <filename>/etc/mail/mailer.conf</filename>:</para>
 
 <programlisting>sendmail	 /usr/libexec/sendmail/sendmail
 send-mail	/usr/libexec/sendmail/sendmail
 mailq		/usr/libexec/sendmail/sendmail
 newaliases	/usr/libexec/sendmail/sendmail
 hoststat	/usr/libexec/sendmail/sendmail
 purgestat	/usr/libexec/sendmail/sendmail</programlisting>
 
       <para>This means that when any of these common commands
 	(such as <filename>sendmail</filename> itself) are run,
 	the system actually invokes a copy of mailwrapper named <filename>sendmail</filename>, which
 	checks <filename>mailer.conf</filename> and
 	executes <filename>/usr/libexec/sendmail/sendmail</filename>
 	instead.  This system makes it easy to change what binaries
 	are actually executed when these default <filename>sendmail</filename> functions
 	are invoked.</para>
 
       <para>Therefore if you wanted
 	<filename>/usr/local/supermailer/bin/sendmail-compat</filename>
 	to be run instead of <application>sendmail</application>, you could change
 	<filename>/etc/mail/mailer.conf</filename> to read:</para>
 
 <programlisting>sendmail	 /usr/local/supermailer/bin/sendmail-compat
 send-mail	/usr/local/supermailer/bin/sendmail-compat
 mailq		/usr/local/supermailer/bin/mailq-compat
 newaliases	/usr/local/supermailer/bin/newaliases-compat
 hoststat	/usr/local/supermailer/bin/hoststat-compat
 purgestat	/usr/local/supermailer/bin/purgestat-compat</programlisting>
 
 	</sect2>
 
 	<sect2>
 	  <title>Finishing</title>
 
 	<para>Once you have everything configured the way you want it, you should
 	  either kill the <application>sendmail</application> processes that
 	  you no longer need and start the processes belonging to your new
 	  software, or simply reboot.  Rebooting will also
 	  give you the opportunity to ensure that you have correctly
 	  configured your system to start your new MTA automatically on boot.</para>
 
       </sect2>
     </sect1>
 
   <sect1 id="mail-trouble">
     <title>Troubleshooting</title>
     <indexterm>
       <primary>email</primary>
       <secondary>troubleshooting</secondary>
     </indexterm>
 
     <qandaset>
       <qandaentry>
         <question>
 	<para>Why do I have to use the FQDN for hosts on my site?</para>
 	</question>
 
 	<answer>
 	<para>You will probably find that the host is actually in a
 	  different domain; for example, if you are in
 	  <hostid role="fqdn">foo.bar.edu</hostid> and you wish to reach
 	  a host called <hostid>mumble</hostid> in the <hostid
 	  role="domainname">bar.edu</hostid> domain, you will have to
 	  refer to it by the fully-qualified domain name, <hostid
 	  role="fqdn">mumble.bar.edu</hostid>, instead of just
 	  <hostid>mumble</hostid>.</para>
 
 	<para>Traditionally, this was allowed by BSD BIND<indexterm>
 	  <primary>BIND</primary></indexterm> resolvers.
 	  However the current version of <application>BIND</application>
 	  that ships with FreeBSD no longer provides default abbreviations
 	  for non-fully qualified domain names other than the domain you
 	  are in. So an unqualified host <hostid>mumble</hostid> must
 	  either be found as <hostid
 	  role="fqdn">mumble.foo.bar.edu</hostid>, or it will be searched
 	  for in the root domain.</para>
 
         <para>This is different from the previous behavior, where the
 	  search continued across <hostid
 	  role="domainname">mumble.bar.edu</hostid>, and <hostid
 	  role="domainname">mumble.edu</hostid>. Have a look at RFC 1535
 	  for why this was considered bad practice, or even a security
 	  hole.</para>
 
         <para>As a good workaround, you can place the line:
 
           <programlisting>search foo.bar.edu bar.edu</programlisting>
 
           instead of the previous:
 
           <programlisting>domain foo.bar.edu</programlisting>
 
           into your <filename>/etc/resolv.conf</filename>.  However, make
 	  sure that the search order does not go beyond the
 	  <quote>boundary between local and public administration</quote>,
 	  as RFC 1535 calls it.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
 	<question>
 
 	<para><application>sendmail</application> says <errorname>mail
 	  loops back to myself</errorname></para>
 	</question>
 
 	<answer>
 	<para>This is answered in the
 	<application>sendmail</application> FAQ as follows:</para>
 
         <programlisting>I'm getting these error messages:
 
 553 MX list for domain.net points back to relay.domain.net
 554 &lt;user@domain.net&gt;... Local configuration error
 
 How can I solve this problem?
 
 You have asked mail to the domain (e.g., domain.net) to be
 forwarded to a specific host (in this case, relay.domain.net)
 by using an MX<indexterm><primary>MX record</primary></indexterm>
 record, but the relay machine does not recognize
 itself as domain.net. Add domain.net to /etc/mail/local-host-names
 [known as /etc/sendmail.cw prior to version 8.10]
 (if you are using FEATURE(use_cw_file)) or add <quote>Cw domain.net</quote>
 to /etc/mail/sendmail.cf.</programlisting>
 
         <para>The <application>sendmail</application> FAQ can be found at
 	  <ulink url="http://www.sendmail.org/faq/"></ulink> and is
 	  recommended reading if you want to do any
 	  <quote>tweaking</quote> of your mail setup.</para>
 	</answer>
       </qandaentry>
 
       <qandaentry>
         <question>
 	<para>How can I run a mail server on a dial-up PPP<indexterm>
 	  <primary>PPP</primary></indexterm> host?</para>
 	</question>
 
 	<answer>
 	<para>You want to connect a FreeBSD box on a LAN to the
 	  Internet.  The FreeBSD box will be a mail gateway for the LAN.
 	  The PPP connection is non-dedicated.</para>
 
 	<para>There are at least two ways to do this.  One way is to use
 	  UUCP<indexterm><primary>UUCP</primary></indexterm>.</para>
 
 	<para>Another way is to get a full-time Internet server to provide secondary
 	  MX<indexterm><primary>MX record</primary></indexterm>
 	  services for your domain.  For example, if your company's domain is
 	  <hostid role="domainname">example.com</hostid> and your Internet service provider has
 	  set <hostid role="domainname">example.net</hostid> up to provide secondary MX services
 	  to your domain:</para>
 
 	<programlisting>example.com.          MX        10      example.com.
                       MX        20      example.net.</programlisting>
 
 	<para>Only one host should be specified as the final recipient
 	  (add <literal>Cw example.com</literal> in
 	  <filename>/etc/mail/sendmail.cf</filename> on <hostid role="domainname">example.com</hostid>).</para>
 
 	<para>When the sending <command>sendmail</command> is trying to
 	  deliver the mail it will try to connect to you (<hostid role="domainname">example.com</hostid>) over the modem
 	  link.  It will most likely time out because you are not online.
 	  The program <application>sendmail</application> will automatically deliver it to the
 	  secondary MX site, i.e. your Internet provider (<hostid role="domainname">example.net</hostid>).  The secondary MX
 	  site will then periodically try to connect to
 	  your host and deliver the mail to the primary MX host (<hostid role="domainname">example.com</hostid>).</para>
 
 	<para>You might want to use something like this as a login
 	  script:</para>
 
 	<programlisting>#!/bin/sh
 # Put me in /usr/local/bin/pppmyisp
 ( sleep 60 ; /usr/sbin/sendmail -q ) &amp;
 /usr/sbin/ppp -direct pppmyisp</programlisting>
 
 	<para>If you are going to create a separate login script for a
 	  user you could use <command>sendmail -qRexample.com</command>
 	  instead in the script above. This will force all mail in your
 	  queue for <hostid role="domainname">example.com</hostid> to be processed immediately.</para>
 
 	<para>A further refinement of the situation is as follows:</para>
 
 	<para>Message stolen from the &a.isp;.</para>
 
 	<programlisting>&gt; we provide the secondary MX for a customer. The customer connects to
 &gt; our services several times a day automatically to get the mails to
 &gt; his primary MX (We do not call his site when a mail for his domains
 &gt; arrived). Our sendmail sends the mailqueue every 30 minutes. At the
 &gt; moment he has to stay 30 minutes online to be sure that all mail is
 &gt; gone to the primary MX.
 &gt;
 &gt; Is there a command that would initiate sendmail to send all the mails
 &gt; now? The user has not root-privileges on our machine of course.
 
 In the <quote>privacy flags</quote> section of sendmail.cf, there is a
 definition Opgoaway,restrictqrun
 
 Remove restrictqrun to allow non-root users to start the queue processing.
 You might also like to rearrange the MXs. We are the 1st MX for our
 customers like this, and we have defined:
 
 # If we are the best MX for a host, try directly instead of generating
 # local config error.
 OwTrue
 
 That way a remote site will deliver straight to you, without trying
 the customer connection.  You then send to your customer.  Only works for
 <quote>hosts</quote>, so you need to get your customer to name their mail
 machine <quote>customer.com</quote> as well as
 <quote>hostname.customer.com</quote> in the DNS.  Just put an A record in
 the DNS for <quote>customer.com</quote>.</programlisting>
         </answer>
       </qandaentry>
 
       <qandaentry>
         <question>
 	  <para>Why do I keep getting <errorname>Relaying
 	    Denied</errorname> errors when sending mail from other
 	    hosts?</para>
 	</question>
 
 	<answer>
 	  <para>In default FreeBSD installations,
  	    <application>sendmail</application> is configured to only
  	    send mail from the host it is running on.  For example, if
 	    a <acronym>POP</acronym> server is available, then users
 	    will be able to check mail from school, work, or other
 	    remote locations but they still will not be able to send
 	    outgoing emails from outside locations.  Typically, a few
 	    moments after the attempt, an email will be sent from
 	    <application>MAILER-DAEMON</application> with a
 	    <errorname>5.7 Relaying Denied</errorname> error
 	    message.</para>
 
 	  <para>There are several ways to get around this.  The most
  	    straightforward solution is to put your ISP's address in
  	    a relay-domains file at
  	    <filename>/etc/mail/relay-domains</filename>.  A quick way
  	    to do this would be:</para>
 
 	  <screen>&prompt.root; <userinput>echo "your.isp.example.com" &gt; /etc/mail/relay-domains</userinput></screen>
 
 	  <para>After creating or editing this file you must restart
   	    <application>sendmail</application>.  This works great if
   	    you are a server administrator and do not wish to send mail
   	    locally, or would like to use a point and click
   	    client/system on another machine or even another ISP.  It
   	    is also very useful if you only have one or two email
   	    accounts set up.  If there is a large number of addresses
   	    to add, you can simply open this file in your favorite
   	    text editor and then add the domains, one per line:</para>
 
 	  <programlisting>your.isp.example.com
 other.isp.example.net
 users-isp.example.org
 www.example.org</programlisting>
 
 	  <para>Now any mail sent through your system, by any host in
 	    this list (provided the user has an account on your
 	    system), will succeed.  This is a very nice way to allow
 	    users to send mail from your system remotely without
 	    allowing people to send SPAM through your system.</para>
 
 	</answer>
       </qandaentry>
     </qandaset>
   </sect1>
 
   <sect1 id="mail-advanced">
     <title>Advanced Topics</title>
 
     <para>The following section covers more involved topics such as mail
       configuration and setting up mail for your entire domain.</para>
 
     <sect2 id="mail-config">
       <title>Basic Configuration</title>
       <indexterm>
         <primary>email</primary>
         <secondary>configuration</secondary>
       </indexterm>
 
       <para>Out of the box, you should be able to send email to external
         hosts as long as you have set up
 	<filename>/etc/resolv.conf</filename> or are running your own
 	name server.  If you would like to have mail for your host
 	delivered to the MTA (e.g., <application>sendmail</application>) on your own FreeBSD host, there are two methods:</para>
 
       <itemizedlist>
         <listitem>
           <para>Run your own name server and have your own domain.  For
 	    example, <hostid
 	    role="domainname">FreeBSD.org</hostid></para>
         </listitem>
 
         <listitem>
           <para>Get mail delivered directly to your host.  This is done by
 	    delivering mail directly to the current DNS name for your
 	    machine.  For example, <hostid
 	    role="fqdn">example.FreeBSD.org</hostid>.</para>
         </listitem>
       </itemizedlist>
 
       <indexterm><primary>SMTP</primary></indexterm>
       <para>Regardless of which of the above you choose, in order to have
         mail delivered directly to your host, it must have a permanent
         static IP address (not a dynamic address, as with most PPP dial-up configurations).  If you are behind a
         firewall, it must pass SMTP traffic on to you.  If you want to
         receive mail directly at your host, you need to be sure of either of two
         things:</para>
 
       <itemizedlist>
-        <indexterm><primary>MX record</primary></indexterm>
         <listitem>
-          <para>Make sure that the (lowest-numbered) MX record in your DNS points to your
+          <para>Make sure that the (lowest-numbered) MX record<indexterm><primary>MX record</primary></indexterm> in your DNS points to your
 	    host's IP address.</para>
         </listitem>
 
         <listitem>
           <para>Make sure there is no MX entry in your DNS for your
 	    host.</para>
         </listitem>
       </itemizedlist>
 
       <para>Either of the above will allow you to receive mail directly at
         your host.</para>
 
       <para>Try this:</para>
 
       <screen>&prompt.root; <userinput>hostname</userinput>
 example.FreeBSD.org
 &prompt.root; <userinput>host example.FreeBSD.org</userinput>
 example.FreeBSD.org has address 204.216.27.XX</screen>
 
       <para>If that is what you see, mail directly to
         <email role="nolink">yourlogin@example.FreeBSD.org</email> should work without
         problems (assuming <application>sendmail</application> is
         running correctly on <hostid role="fqdn">example.FreeBSD.org</hostid>).</para>
 
       <para>If instead you see something like this:</para>
 
       <screen>&prompt.root; <userinput>host example.FreeBSD.org</userinput>
 example.FreeBSD.org has address 204.216.27.XX
 example.FreeBSD.org mail is handled (pri=10) by hub.FreeBSD.org</screen>
 
       <para>All mail sent to your host (<hostid
         role="fqdn">example.FreeBSD.org</hostid>) will end up being
 	collected on <hostid>hub</hostid> under the same username instead
 	of being sent directly to your host.</para>
 
       <para>The above information is handled by your DNS server.  The DNS
         record that carries mail routing information is the
         <emphasis>M</emphasis>ail e<emphasis>X</emphasis>change entry.  If
         no MX record exists, mail will be delivered directly to the host by
         way of its IP address.</para>
 
       <para>The MX entry for <hostid
         role="fqdn">freefall.FreeBSD.org</hostid> at one time looked like
         this:</para>
 
       <programlisting>freefall		MX	30	mail.crl.net
 freefall		MX	40	agora.rdrop.com
 freefall		MX	10	freefall.FreeBSD.org
 freefall		MX	20	who.cdrom.com</programlisting>
 
       <para>As you can see, <hostid>freefall</hostid> had many MX entries.
         The lowest MX number is the host that receives mail directly if
         available; if it is not accessible for some reason, the others
         (sometimes called <quote>backup MXes</quote>) accept messages
         temporarily, and pass it along when a lower-numbered host becomes
         available, eventually to the lowest-numbered host.</para>
 
       <para>Alternate MX sites should have separate Internet connections
         from your own in order to be most useful.  Your ISP or another
         friendly site should have no problem providing this service for
         you.</para>
     </sect2>
 
     <sect2 id="mail-domain">
       <title>Mail for Your Domain</title>
 
       <para>In order to set up a <quote>mailhost</quote> (a.k.a. mail
         server) you need to have any mail sent to various workstations
 	directed to it.  Basically, you want to <quote>claim</quote> any
 	mail for any hostname in your domain (in this case <hostid
 	role="fqdn">*.FreeBSD.org</hostid>) and divert it to your mail
 	server so your users can receive their mail on
 	the master mail server.</para>
 
       <indexterm><primary>DNS</primary></indexterm>
       <para>To make life easiest, a user account with the same
         <emphasis>username</emphasis> should exist on both machines.  Use
 	&man.adduser.8; to do this.</para>
 
       <para>The mailhost you will be using must be the designated mail
         exchanger for each workstation on the network.  This is done in
 	your DNS configuration like so:</para>
 
       <programlisting>example.FreeBSD.org	A	204.216.27.XX		; Workstation
 			MX	10 hub.FreeBSD.org	; Mailhost</programlisting>
 
       <para>This will redirect mail for the workstation to the mailhost no
         matter where the A record points.  The mail is sent to the MX
 	host.</para>
 
       <para>You cannot do this yourself unless you are running a DNS
         server.  If you are not, or cannot run your own DNS server, talk
 	to your ISP or whoever provides your DNS.</para>
 
       <para>If you are doing virtual email hosting, the following
         information will come in handy.  For this example, we
 	will assume you have a customer with his own domain, in this
 	case <hostid role="domainname">customer1.org</hostid>, and you want
 	all the mail for <hostid role="domainname">customer1.org</hostid>
 	sent to your mailhost, <hostid
 	role="fqdn">mail.myhost.com</hostid>.  The entry in your DNS
 	should look like this:</para>
 
       <programlisting>customer1.org		MX	10	mail.myhost.com</programlisting>
 
       <para>You do <emphasis>not</emphasis> need an A record for <hostid role="domainname">customer1.org</hostid> if you only
         want to handle email for that domain.</para>
 
       <note>
 	<para>Be aware that pinging <hostid
 	  role="domainname">customer1.org</hostid> will not work unless
 	  an A record exists for it.</para>
       </note>
 
       <para>The last thing that you must do is tell
         <application>sendmail</application> on your mailhost what domains
 	and/or hostnames it should be accepting mail for.  There are a few
 	different ways this can be done.  Either of the following will
 	work:</para>
 
       <itemizedlist>
         <listitem>
 	  <para>Add the hosts to your
 	  <filename>/etc/mail/local-host-names</filename> file if you are using the
 	  <literal>FEATURE(use_cw_file)</literal>.  If you are using
 	  a version of <application>sendmail</application> earlier than 8.10, the file is
 	  <filename>/etc/sendmail.cw</filename>.</para>
 	</listitem>
 
 	<listitem>
 	  <para>Add a <literal>Cwyour.host.com</literal> line to your
 	    <filename>/etc/sendmail.cf</filename> or
 	    <filename>/etc/mail/sendmail.cf</filename> if you are using
 	    <application>sendmail</application> 8.10 or higher.</para>
 	</listitem>
       </itemizedlist>
     </sect2>
   </sect1>
 
   <sect1 id="SMTP-UUCP">
   <title>SMTP with UUCP</title>
 
     <para>The <application>sendmail</application> configuration that ships with FreeBSD is
       designed for sites that connect directly to the Internet.  Sites
       that wish to exchange their mail via UUCP must install another
       <application>sendmail</application> configuration file.</para>
 
     <para>Tweaking <filename>/etc/mail/sendmail.cf</filename> manually
       is an advanced topic. <application>sendmail</application> version 8 generates config files
       via &man.m4.1; preprocessing, where the actual configuration
       occurs on a higher abstraction level. The &man.m4.1;
       configuration files can be found under
       <filename>/usr/share/sendmail/cf</filename>.  The file
       <filename>README</filename> in the <filename>cf</filename>
       directory can serve as a basic introduction to &man.m4.1;
       configuration.</para>
 
     <para>The best way to support UUCP delivery is to use the
       <literal>mailertable</literal> feature.  This creates a database
       that <application>sendmail</application> can use to make routing decisions.</para>
 
     <para>First, you have to create your <filename>.mc</filename>
       file.  The directory
       <filename>/usr/share/sendmail/cf/cf</filename> contains a
       few examples.  Assuming you have named your file
       <filename>foo.mc</filename>, all you need to do in order to
       convert it into a valid <filename>sendmail.cf</filename>
       is:</para>
 
     <screen>&prompt.root; <userinput>cd /etc/mail</userinput>
 &prompt.root; <userinput>make foo.cf</userinput>
 &prompt.root; <userinput>cp foo.cf /etc/mail/sendmail.cf</userinput></screen>
 
     <para>A typical <filename>.mc</filename> file might look
         like:</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>The lines containing
       <literal>accept_unresolvable_domains</literal>,
       <literal>nocanonify</literal>, and
       <literal>confDONT_PROBE_INTERFACES</literal> features will
       prevent any usage of the DNS during mail delivery.  The
       <literal>UUCP_RELAY</literal> clause is needed to support UUCP
       delivery.  Simply put an Internet hostname there that is able to
       handle .UUCP pseudo-domain addresses; most likely, you will
       enter the mail relay of your ISP there.</para>
 
     <para>Once you have this, you need an
       <filename>/etc/mail/mailertable</filename> file.  If you have
       only one link to the outside that is used for all your mails,
       the following file will suffice:</para>
 
     <programlisting>#
 # makemap hash /etc/mail/mailertable.db &lt; /etc/mail/mailertable
 .                             uucp-dom:<replaceable>your.uucp.relay</replaceable></programlisting>
 
     <para>A more complex example might look like this:</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>The first three lines handle special cases where
       domain-addressed mail should not be sent out to the default
       route, but instead to some UUCP neighbor in order to
       <quote>shortcut</quote> the delivery path. The next line handles
       mail to the local Ethernet domain that can be delivered using
       SMTP. Finally, the UUCP neighbors are mentioned in the .UUCP
       pseudo-domain notation, to allow for a
       <literal><replaceable>uucp-neighbor
       </replaceable>!<replaceable>recipient</replaceable></literal>
       override of the default rules. The last line is always a single
       dot, matching everything else, with UUCP delivery to a UUCP
       neighbor that serves as your universal mail gateway to the
       world. All of the node names behind the
       <literal>uucp-dom:</literal> keyword must be valid UUCP
       neighbors, as you can verify using the command
       <literal>uuname</literal>.</para>
 
     <para>As a reminder that this file needs to be converted into a
       DBM database file before use.  The command line to accomplish
       this is best placed as a comment at the top of the <filename>mailertable</filename> file.
       You always have to execute this command each time you change
       your <filename>mailertable</filename> file.</para>
 
     <para>Final hint: if you are uncertain whether some particular
       mail routing would work, remember the <option>-bt</option>
       option to <application>sendmail</application>. It starts <application>sendmail</application> in <emphasis>address test
       mode</emphasis>; simply enter <literal>3,0</literal>, followed
       by the address you wish to test for the mail routing.  The last
       line tells you the used internal mail agent, the destination
       host this agent will be called with, and the (possibly
       translated) address. Leave this mode by typing <keycombo
       action="simul"><keycap>Ctrl</keycap><keycap>D</keycap></keycombo>.</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>
   </sect1>
 
   <sect1 id="outgoing-only">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Bill</firstname>
           <surname>Moran</surname>
           <contrib>Contributed by </contrib>
         </author>
       </authorgroup>
     </sect1info>
 
     <title>Setting Up to Send Only</title>
 
     <para>There are many instances where you may only want to send
       mail through a relay.  Some examples are:</para>
 
     <itemizedlist>
       <listitem>
 	<para>Your computer is a desktop machine, but you want
 	  to use programs such as &man.send-pr.1;.  To do so, you should use
 	  your ISP's mail relay.</para>
       </listitem>
 
       <listitem>
 	<para>The computer is a server that does not handle mail
 	  locally, but needs to pass off all mail to a relay for
 	  processing.</para>
       </listitem>
     </itemizedlist>
 
     <para>Just about any <acronym>MTA</acronym> is capable of filling
       this particular niche.  Unfortunately, it can be very difficult
       to properly configure a full-featured <acronym>MTA</acronym>
       just to handle offloading mail.  Programs such as
       <application>sendmail</application> and
       <application>postfix</application> are largely overkill for
       this use.</para>
 
     <para>Additionally, if you are using a typical Internet access
       service, your agreement may forbid you from running a
       <quote>mail server</quote>.</para>
 
     <para>The easiest way to fulfill those needs is to install the
       <filename role="package">mail/ssmtp</filename> port.  Execute
       the following commands as <username>root</username>:</para>
 
     <screen>&prompt.root; <userinput>cd /usr/ports/mail/ssmtp</userinput>
 &prompt.root; <userinput>make install replace clean</userinput></screen>
 
     <para>Once installed,
       <filename role="package">mail/ssmtp</filename> can be configured
       with a four-line file located at
       <filename>/usr/local/etc/ssmtp/ssmtp.conf</filename>:</para>
 
     <programlisting>root=yourrealemail@example.com
 mailhub=mail.example.com
 rewriteDomain=example.com
 hostname=_HOSTNAME_</programlisting>
 
     <para>Make sure you use your real email address for
       <username>root</username>.  Enter your ISP's outgoing mail relay
       in place of <hostid role="fqdn">mail.example.com</hostid> (some ISPs call
       this the <quote>outgoing mail server</quote> or
       <quote>SMTP server</quote>).</para>
 
     <para>Make sure you disable <application>sendmail</application>,
       including the outgoing mail service. See
       <xref linkend="mail-disable-sendmail"/> for details.</para>
 
     <para><filename role="package">mail/ssmtp</filename> has some
       other options available.  See the example configuration file in
       <filename>/usr/local/etc/ssmtp</filename> or the manual page of
       <application>ssmtp</application> for some examples and more
       information.</para>
 
     <para>Setting up <application>ssmtp</application> in this manner
       will allow any software on your computer that needs to send
       mail to function properly, while not violating your ISP's usage
       policy or allowing your computer to be hijacked for spamming.</para>
   </sect1>
 
   <sect1 id="SMTP-dialup">
     <title>Using Mail with a Dialup Connection</title>
 
     <para>If you have a static IP address, you should not need to
       adjust anything from the defaults.  Set your host name to your
       assigned Internet name and <application>sendmail</application> will do the rest.</para>
 
     <para>If you have a dynamically assigned IP number and use a
       dialup PPP connection to the Internet, you will probably have a
       mailbox on your ISPs mail server. Let's assume your ISP's domain
       is <hostid role="domainname">example.net</hostid>, and that your
       user name is <username>user</username>, you have called your
       machine <hostid role="fqdn">bsd.home</hostid>, and your ISP has
       told you that you may use <hostid
       role="fqdn">relay.example.net</hostid> as a mail relay.</para>
 
     <para>In order to retrieve mail from your mailbox, you must
       install a retrieval agent.  The
       <application>fetchmail</application> utility is a good choice as
       it supports many different protocols.  This program is available
       as a package or from the Ports Collection (<filename
       role="package">mail/fetchmail</filename>).  Usually, your <acronym>ISP</acronym> will
       provide <acronym>POP</acronym>. If you are using user <acronym>PPP</acronym>, you can
       automatically fetch your mail when an Internet connection is
       established with the following entry in
       <filename>/etc/ppp/ppp.linkup</filename>:</para>
 
     <programlisting>MYADDR:
 !bg su user -c fetchmail</programlisting>
 
     <para>If you are using <application>sendmail</application> (as
       shown below) to deliver mail to non-local accounts, you probably
       want to have <application>sendmail</application> process your
       mailqueue as soon as your Internet connection is established.
       To do this, put this command after the
       <command>fetchmail</command> command in
       <filename>/etc/ppp/ppp.linkup</filename>:</para>
 
     <programlisting>  !bg su user -c "sendmail -q"</programlisting>
 
     <para>Assume that you have an account for
       <username>user</username> on <hostid
       role="fqdn">bsd.home</hostid>. In the home directory of
       <username>user</username> on <hostid
       role="fqdn">bsd.home</hostid>, create a
       <filename>.fetchmailrc</filename> file:</para>
 
     <programlisting>poll example.net protocol pop3 fetchall pass MySecret</programlisting>
 
     <para>This file should not be readable by anyone except
       <username>user</username> as it contains the password
       <literal>MySecret</literal>.</para>
 
     <para>In order to send mail with the correct
       <literal>from:</literal> header, you must tell
       <application>sendmail</application> to use
       <email>user@example.net</email> rather than
       <email role="nolink">user@bsd.home</email>. You may also wish to tell
       <application>sendmail</application> to send all mail via <hostid
       role="fqdn">relay.example.net</hostid>, allowing quicker mail
       transmission.</para>
 
     <para>The following <filename>.mc</filename> file should
       suffice:</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>Refer to the previous section for details of how to turn
       this <filename>.mc</filename> file into a
       <filename>sendmail.cf</filename> file.  Also, do not forget to
       restart <application>sendmail</application> after updating
       <filename>sendmail.cf</filename>.</para>
   </sect1>
 
   <sect1 id="SMTP-Auth">
     <sect1info>
     <authorgroup>
       <author>
         <firstname>James</firstname>
         <surname>Gorham</surname>
         <contrib>Written by </contrib>
       </author>
     </authorgroup>
     </sect1info>
 
     <title>SMTP Authentication</title>
 
     <para>Having <acronym>SMTP</acronym> Authentication in place on
       your mail server has a number of benefits.
       <acronym>SMTP</acronym> Authentication can add another layer
       of security to <application>sendmail</application>, and has the benefit of giving mobile
       users who switch hosts the ability to use the same mail server
       without the need to reconfigure their mail client settings
       each time.</para>
 
     <procedure>
       <step>
 	<para>Install <filename role="package">security/cyrus-sasl2</filename>
 	  from the ports. You can find this port in
 	  <filename role="package">security/cyrus-sasl2</filename>.  The
 	  <filename role="package">security/cyrus-sasl2</filename> port
 	  supports a number of compile-time options.  For the SMTP
 	  Authentication method we will be using here, make sure that
 	  the <option>LOGIN</option> option is not disabled.</para>
       </step>
 
 
       <step>
 	<para>After installing <filename role="package">security/cyrus-sasl2</filename>,
 	  edit <filename>/usr/local/lib/sasl2/Sendmail.conf</filename>
 	  (or create it if it does not exist) and add the following
 	  line:</para>
 
 	<programlisting>pwcheck_method: saslauthd</programlisting>
       </step>
 
       <step>
 	<para>Next, install <filename role="package">security/cyrus-sasl2-saslauthd</filename>,
 	  edit <filename>/etc/rc.conf</filename> to add the following
 	  line:</para>
 
 	<programlisting>saslauthd_enable="YES"</programlisting>
 
 	<para>and finally start the saslauthd daemon:</para>
 
 	<screen>&prompt.root; <userinput>/usr/local/etc/rc.d/saslauthd start</userinput></screen>
 
 	<para>This daemon serves as a broker for <application>sendmail</application> to
 	  authenticate against your FreeBSD <filename>passwd</filename>
 	  database.  This saves the trouble of creating a new set of usernames
 	  and passwords for each user that needs to use
 	  <acronym>SMTP</acronym> authentication, and keeps the login
 	  and mail password the same.</para>
       </step>
 
       <step>
 	<para>Now edit <filename>/etc/make.conf</filename> and add the
 	  following lines:</para>
 
 	<programlisting>SENDMAIL_CFLAGS=-I/usr/local/include/sasl -DSASL
 SENDMAIL_LDFLAGS=-L/usr/local/lib
 SENDMAIL_LDADD=-lsasl2</programlisting>
 
 	<para>These lines will give <application>sendmail</application>
 	the proper configuration options for linking
 	to <filename role="package">cyrus-sasl2</filename> at compile time.
 	Make sure that <filename role="package">cyrus-sasl2</filename>
 	has been installed before recompiling
 	<application>sendmail</application>.</para>
       </step>
 
       <step>
 	<para>Recompile <application>sendmail</application> by executing the following commands:</para>
 
 	<screen>&prompt.root; <userinput>cd /usr/src/lib/libsmutil</userinput>
 &prompt.root; <userinput>make cleandir &amp;&amp; make obj &amp;&amp; make</userinput>
 &prompt.root; <userinput>cd /usr/src/lib/libsm</userinput>
 &prompt.root; <userinput>make cleandir &amp;&amp; make obj &amp;&amp; make</userinput>
 &prompt.root; <userinput>cd /usr/src/usr.sbin/sendmail</userinput>
 &prompt.root; <userinput>make cleandir &amp;&amp; make obj &amp;&amp; make &amp;&amp; make install</userinput></screen>
 
 	<para>The compile of <application>sendmail</application> should not have any problems
 	  if <filename>/usr/src</filename> has not been changed extensively
 	  and the shared libraries it needs are available.</para>
       </step>
 
       <step>
 	<para>After <application>sendmail</application> has been compiled
 	  and reinstalled, edit your <filename>/etc/mail/freebsd.mc</filename>
 	  file (or whichever file you use as your <filename>.mc</filename> file. Many administrators
 	  choose to use the output from &man.hostname.1; as the <filename>.mc</filename> file for
 	  uniqueness).  Add these lines to it:</para>
 
 	<programlisting>dnl set SASL options
 TRUST_AUTH_MECH(`GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN')dnl
 define(`confAUTH_MECHANISMS', `GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN')dnl</programlisting>
 
 	<para>These options configure the different methods available to
 	<application>sendmail</application> for authenticating users.
 	If you would like to use a method other than
 	<application>pwcheck</application>, please see the
 	included documentation.</para>
       </step>
 
       <step>
 	<para>Finally, run &man.make.1; while in <filename>/etc/mail</filename>.
 	  That will run your new <filename>.mc</filename> file and create a <filename>.cf</filename> file named
 	  <filename>freebsd.cf</filename> (or whatever name you have used
 	  for your <filename>.mc</filename> file).  Then use the
 	  command <command>make install restart</command>, which will
 	  copy the file to <filename>sendmail.cf</filename>, and will
 	  properly restart <application>sendmail</application>.
 	  For more information about this process, you should refer
 	  to <filename>/etc/mail/Makefile</filename>.</para>
       </step>
     </procedure>
 
     <para>If all has gone correctly, you should be able to enter your login
       information into the mail client and send a test message.
       For further investigation, set the <option>LogLevel</option> of
       <application>sendmail</application> to 13 and watch
       <filename>/var/log/maillog</filename> for any errors.</para>
 
     <para>For more information, please see the <application>sendmail</application>
       page regarding
       <ulink url="http://www.sendmail.org/~ca/email/auth.html">
       <acronym>SMTP</acronym> authentication</ulink>.</para>
 
   </sect1>
 
   <sect1 id="mail-agents">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Marc</firstname>
 	  <surname>Silver</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
     </sect1info>
     <title>Mail User Agents</title>
 
     <indexterm>
       <primary>Mail User Agents</primary>
     </indexterm>
 
     <para>A Mail User Agent (<acronym>MUA</acronym>) is an application
       that is used to send and receive email.  Furthermore, as email
       <quote>evolves</quote> and becomes more complex,
       <acronym>MUA</acronym>'s are becoming increasingly powerful in the
       way they interact with email; this gives users increased
       functionality and flexibility.  &os; contains support for
       numerous mail user agents, all of which can be easily installed
       using the <link linkend="ports">FreeBSD Ports Collection</link>.
       Users may choose between graphical email clients such as
       <application>evolution</application> or
       <application>balsa</application>, console based clients such as
       <application>mutt</application>, <application>pine</application>
       or <command>mail</command>, or the web interfaces used by some
       large organizations.</para>
 
     <sect2 id="mail-command">
       <title>mail</title>
 
       <para>&man.mail.1; is the default Mail User Agent
 	(<acronym>MUA</acronym>) in &os;.  It is a
 	console based <acronym>MUA</acronym> that offers all the basic
 	functionality required to send and receive text-based email,
 	though it is limited in interaction abilities with attachments
 	and can only support local mailboxes.</para>
 
       <para>Although <command>mail</command> does not natively support
 	interaction with <acronym>POP</acronym> or
 	<acronym>IMAP</acronym> servers, these mailboxes may be
 	downloaded to a local <filename>mbox</filename> file using an
 	application such as <application>fetchmail</application>, which
 	will be discussed later in this chapter (<xref
 	linkend="mail-fetchmail"/>).</para>
 
       <para>In order to send and receive email, simply invoke the
 	<command>mail</command> command as per the following
 	example:</para>
 
       <screen>&prompt.user; <userinput>mail</userinput></screen>
 
       <para>The contents of the user mailbox in
 	<filename class="directory">/var/mail</filename> are
 	automatically read by the <command>mail</command> utility.
 	Should the mailbox be empty, the utility exits with a
 	message indicating that no mails could be found.  Once the
 	mailbox has been read, the application interface is started, and
 	a list of messages will be displayed.  Messages are automatically
 	numbered, as can be seen in the following example:</para>
 
       <screen>Mail version 8.1 6/6/93.  Type ? for help.
 "/var/mail/marcs": 3 messages 3 new
 >N  1 root@localhost        Mon Mar  8 14:05  14/510   "test"
  N  2 root@localhost        Mon Mar  8 14:05  14/509   "user account"
  N  3 root@localhost        Mon Mar  8 14:05  14/509   "sample"</screen>
 
       <para>Messages can now be read by using the <keycap>t</keycap>
 	<command>mail</command> command, suffixed by the message number
 	that should be displayed.  In this example, we will read the
 	first email:</para>
 
       <screen>&amp; <userinput>t 1</userinput>
 Message 1:
 From root@localhost  Mon Mar  8 14:05:52 2004
 X-Original-To: marcs@localhost
 Delivered-To: marcs@localhost
 To: marcs@localhost
 Subject: test
 Date: Mon,  8 Mar 2004 14:05:52 +0200 (SAST)
 From: root@localhost (Charlie Root)
 
 This is a test message, please reply if you receive it.</screen>
 
       <para>As can be seen in the example above, the <keycap>t</keycap>
 	key will cause the message to be displayed with full headers.
 	To display the list of messages again, the <keycap>h</keycap>
 	key should be used.</para>
 
       <para>If the email requires a response, you may use
 	<command>mail</command> to reply, by using either the
 	<keycap>R</keycap> or <keycap>r</keycap> <command>mail</command>
 	keys.  The <keycap>R</keycap> key instructs
 	<command>mail</command> to reply only to the sender of the
 	email, while <keycap>r</keycap> replies not only to the sender,
 	but also to other recipients of the message.  You may also
 	suffix these commands with the mail number which you would like
 	make a reply to.  Once this has been done, the response should
 	be entered, and the end of the message should be marked by a
 	single <keycap>.</keycap> on a new line.  An example can be seen
 	below:</para>
 
       <screen>&amp; <userinput>R 1</userinput>
 To: root@localhost
 Subject: Re: test
 
 <userinput>Thank you, I did get your email.
 .</userinput>
 EOT</screen>
 
       <para>In order to send new email, the <keycap>m</keycap>
 	key should be used, followed by the
 	recipient email address.  Multiple recipients may also be
 	specified by separating each address with the <keycap>,</keycap>
 	delimiter.  The subject of the message may then be entered,
 	followed by the message contents.  The end of the message should
 	be specified by putting a single <keycap>.</keycap> on a new
 	line.</para>
 
       <screen>&amp; <userinput>mail root@localhost</userinput>
 Subject: <userinput>I mastered mail
 
 Now I can send and receive email using mail ... :)
 .</userinput>
 EOT</screen>
 
       <para>While inside the <command>mail</command> utility, the
 	<keycap>?</keycap> command may be used to display help at any
 	time, the &man.mail.1; manual page should also be consulted for
 	more help with <command>mail</command>.</para>
 
       <note>
         <para>As previously mentioned, the &man.mail.1; command was not
 	  originally designed to handle attachments, and thus deals with
 	  them very poorly.  Newer <acronym>MUA</acronym>s such as
 	  <application>mutt</application> handle attachments in a much
 	  more intelligent way.  But should you still wish to use the
 	  <command>mail</command> command, the <filename
 	  role="package">converters/mpack</filename> port may be of
 	  considerable use.</para>
       </note>
     </sect2>
 
     <sect2 id="mutt-command">
       <title>mutt</title>
 
       <para><application>mutt</application> is a small yet very
 	 powerful Mail User Agent, with excellent features,
 	 just some of which include:</para>
 
       <itemizedlist>
         <listitem>
 	  <para>The ability to thread messages;</para>
         </listitem>
 
         <listitem>
 	  <para>PGP support for digital signing and encryption of
 	    email;</para>
         </listitem>
 
         <listitem>
 	  <para>MIME Support;</para>
         </listitem>
 
         <listitem>
 	  <para>Maildir Support;</para>
         </listitem>
 
         <listitem>
 	  <para>Highly customizable.</para>
         </listitem>
       </itemizedlist>
 
       <para>All of these features help to make
 	<application>mutt</application> one of the most advanced mail
 	user agents available.  See <ulink
 	url="http://www.mutt.org"></ulink> for more
 	information on <application>mutt</application>.</para>
 
       <para>The stable version of <application>mutt</application> may be
 	installed using the <filename
 	role="package">mail/mutt</filename> port, while the current
 	development version may be installed via the <filename
 	role="package">mail/mutt-devel</filename> port.  After the port
 	has been installed, <application>mutt</application> can be
 	started by issuing the following command:</para>
 
       <screen>&prompt.user; <userinput>mutt</userinput></screen>
 
       <para><application>mutt</application> will automatically read the
 	contents of the user mailbox in <filename
 	class="directory">/var/mail</filename> and display the contents
 	if applicable.  If no mails are found in the user mailbox, then
 	<application>mutt</application> will wait for commands from the
 	user.  The example below shows <application>mutt</application>
 	displaying a list of messages:</para>
 
       <mediaobject>
 	<imageobject>
 	  <imagedata fileref="mail/mutt1"/>
 	</imageobject>
       </mediaobject>
 
       <para>In order to read an email, simply select it using the cursor
 	keys, and press the <keycap>Enter</keycap> key.  An example of
 	<application>mutt</application> displaying email can be seen
 	below:</para>
 
       <mediaobject>
 	<imageobject>
 	  <imagedata fileref="mail/mutt2"/>
 	</imageobject>
       </mediaobject>
 
       <para>As with the &man.mail.1; command,
 	<application>mutt</application> allows users to reply only to
 	the sender of the message as well as to all recipients.  To
 	reply only to the sender of the email, use the
 	<keycap>r</keycap> keyboard shortcut.  To send a group reply,
 	which will be sent to the original sender as well as all the
 	message recipients, use the <keycap>g</keycap> shortcut.</para>
 
       <note>
 	<para><application>mutt</application> makes use of the
 	  &man.vi.1; command as an editor for creating and replying to
 	  emails.  This may be customized by the user by creating or
 	  editing their own <filename>.muttrc</filename> file in their home directory and setting the
 	  <literal>editor</literal> variable or by setting the
 	  <envar>EDITOR</envar> environment variable.  See
 	  <ulink url="http://www.mutt.org/"></ulink> for more
 	  information about configuring
 	  <application>mutt</application>.</para>
       </note>
 
       <para>In order to compose a new mail message, press
 	<keycap>m</keycap>.  After a valid subject has been given,
 	<application>mutt</application> will start &man.vi.1; and the
 	mail can be written.  Once the contents of the mail are
 	complete, save and quit from <command>vi</command> and
 	<application>mutt</application> will resume, displaying a
 	summary screen of the mail that is to be delivered.  In order to
 	send the mail, press <keycap>y</keycap>.  An example of the
 	summary screen can be seen below:</para>
 
       <mediaobject>
 	<imageobject>
 	  <imagedata fileref="mail/mutt3"/>
 	</imageobject>
       </mediaobject>
 
       <para><application>mutt</application> also contains extensive
 	help, which can be accessed from most of the menus by pressing
 	the <keycap>?</keycap> key.  The top line also displays the
 	keyboard shortcuts where appropriate.</para>
 
     </sect2>
 
     <sect2 id="pine-command">
       <title>pine</title>
 
       <para><application>pine</application> is aimed at a beginner
 	user, but also includes some advanced features.</para>
 
       <warning>
 	<para>The <application>pine</application> software has had several remote vulnerabilities
 	  discovered in the past, which allowed remote attackers to
 	  execute arbitrary code as users on the local system, by the
 	  action of sending a specially-prepared email. All such
 	  <emphasis>known</emphasis> problems have been fixed, but the
 	  <application>pine</application> code is written in a very insecure style and the &os;
 	  Security Officer believes there are likely to be other
 	  undiscovered vulnerabilities. You install
 	  <application>pine</application> at your own risk.</para>
       </warning>
 
       <para>The current version of <application>pine</application> may
 	be installed using the <filename
 	role="package">mail/pine4</filename> port.  Once the port has
 	installed, <application>pine</application> can be started by
 	issuing the following command:</para>
 
       <screen>&prompt.user; <userinput>pine</userinput></screen>
 
       <para>The first time that <application>pine</application> is run
 	it displays a greeting page with a brief introduction, as well
 	as a request from the <application>pine</application>
 	development team to send an anonymous email message allowing
 	them to judge how many users are using their client.  To send
 	this anonymous message, press <keycap>Enter</keycap>, or
 	alternatively press <keycap>E</keycap> to exit the greeting
 	without sending an anonymous message.  An example of the
 	greeting page can be seen below:</para>
 
       <mediaobject>
 	<imageobject>
 	  <imagedata fileref="mail/pine1"/>
 	</imageobject>
       </mediaobject>
 
       <para>Users are then presented with the main menu, which can be
 	easily navigated using the cursor keys.  This main menu provides
 	shortcuts for the composing new mails, browsing of mail directories,
 	and even the administration of address book entries.  Below the
 	main menu, relevant keyboard shortcuts to perform functions
 	specific to the task at hand are shown.</para>
 
       <para>The default directory opened by <application>pine</application>
 	is the <filename class="directory">inbox</filename>.  To view the message index, press
 	<keycap>I</keycap>, or select the <guimenuitem>MESSAGE INDEX</guimenuitem>
 	option as seen below:</para>
 
       <mediaobject>
 	<imageobject>
 	  <imagedata fileref="mail/pine2"/>
 	</imageobject>
       </mediaobject>
 
       <para>The message index shows messages in the current directory,
 	and can be navigated by using the cursor keys.  Highlighted
 	messages can be read by pressing the
 	<keycap>Enter</keycap> key.</para>
 
       <mediaobject>
 	<imageobject>
 	  <imagedata fileref="mail/pine3"/>
 	</imageobject>
       </mediaobject>
 
       <para>In the screenshot below, a sample message is displayed by
 	<application>pine</application>.  Keyboard shortcuts are
 	displayed as a reference at the bottom of the screen.  An
 	example of one of these shortcuts is the <keycap>r</keycap> key,
 	which tells the <acronym>MUA</acronym> to reply to the current
 	message being displayed.</para>
 
       <mediaobject>
 	<imageobject>
 	  <imagedata fileref="mail/pine4"/>
 	</imageobject>
       </mediaobject>
 
       <para>Replying to an email in <application>pine</application> is
 	done using the <application>pico</application> editor, which is
 	installed by default with <application>pine</application>.
 	The <application>pico</application> utility makes it easy to
 	navigate around the message and is slightly more forgiving on
 	novice users than &man.vi.1; or &man.mail.1;.  Once the reply
 	is complete, the message can be sent by pressing
 	<keycombo action="simul"><keycap>Ctrl</keycap><keycap>X</keycap>
 	</keycombo>. The <application>pine</application> application
 	will ask for confirmation.</para>
 
       <mediaobject>
 	<imageobject>
 	  <imagedata fileref="mail/pine5"/>
 	</imageobject>
       </mediaobject>
 
       <para>The <application>pine</application> application can be
 	customized using the <guimenuitem>SETUP</guimenuitem> option from the main
 	menu.  Consult <ulink url="http://www.washington.edu/pine/"></ulink>
 	for more information.</para>
 
     </sect2>
   </sect1>
 
   <sect1 id="mail-fetchmail">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Marc</firstname>
 	  <surname>Silver</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
     </sect1info>
     <title>Using fetchmail</title>
 
     <indexterm>
       <primary>fetchmail</primary>
     </indexterm>
 
     <para><application>fetchmail</application> is a full-featured
       <acronym>IMAP</acronym> and <acronym>POP</acronym> client which
       allows users to automatically download mail from remote
       <acronym>IMAP</acronym> and <acronym>POP</acronym> servers and
       save it into local mailboxes; there it can be accessed more easily.
       <application>fetchmail</application> can be installed using the
       <filename role="package">mail/fetchmail</filename> port, and
       offers various features, some of which include:</para>
 
     <itemizedlist>
       <listitem>
 	<para>Support of <acronym>POP3</acronym>,
 	  <acronym>APOP</acronym>, <acronym>KPOP</acronym>,
 	  <acronym>IMAP</acronym>, <acronym>ETRN</acronym> and
 	  <acronym>ODMR</acronym> protocols.</para>
       </listitem>
 
       <listitem>
 	<para>Ability to forward mail using <acronym>SMTP</acronym>, which
 	  allows filtering, forwarding, and aliasing to function
 	  normally.</para>
       </listitem>
 
       <listitem>
 	<para>May be run in daemon mode to check periodically for new
 	  messages.</para>
       </listitem>
 
       <listitem>
 	<para>Can retrieve multiple mailboxes and forward them based
 	  on configuration, to different local users.</para>
       </listitem>
     </itemizedlist>
 
     <para>While it is outside the scope of this document to explain
       all of <application>fetchmail</application>'s features, some
       basic features will be explained.  The
       <application>fetchmail</application> utility requires a
       configuration file known as <filename>.fetchmailrc</filename>,
       in order to run correctly.  This file includes server information
       as well as login credentials.  Due to the sensitive nature of the
       contents of this file, it is advisable to make it readable only by the owner,
       with the following command:</para>
 
     <screen>&prompt.user; <userinput>chmod 600 .fetchmailrc</userinput></screen>
 
     <para>The following <filename>.fetchmailrc</filename> serves as an
       example for downloading a single user mailbox using
       <acronym>POP</acronym>.  It tells
       <application>fetchmail</application> to connect to <hostid
       role="fqdn">example.com</hostid> using a username of
       <username>joesoap</username> and a password of
       <literal>XXX</literal>.  This example assumes that the user
       <username>joesoap</username> is also a user on the local
       system.</para>
 
     <programlisting>poll example.com protocol pop3 username "joesoap" password "XXX"</programlisting>
 
     <para>The next example connects to multiple <acronym>POP</acronym>
       and <acronym>IMAP</acronym> servers and redirects to different
       local usernames where applicable:</para>
 
     <programlisting>poll example.com proto pop3:
 user "joesoap", with password "XXX", is "jsoap" here;
 user "andrea", with password "XXXX";
 poll example2.net proto imap:
 user "john", with password "XXXXX", is "myth" here;</programlisting>
 
     <para>The <application>fetchmail</application> utility can be run in daemon
       mode by running it with the <option>-d</option> flag, followed
       by the interval (in seconds) that
       <application>fetchmail</application> should poll servers listed
       in the <filename>.fetchmailrc</filename> file.  The following
       example would cause <application>fetchmail</application> to poll
       every 600 seconds:</para>
 
     <screen>&prompt.user; <userinput>fetchmail -d 600</userinput></screen>
 
     <para>More information on <application>fetchmail</application> can
       be found at <ulink
       url="http://fetchmail.berlios.de/"></ulink>.</para>
   </sect1>
 
   <sect1 id="mail-procmail">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Marc</firstname>
 	  <surname>Silver</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
     </sect1info>
     <title>Using procmail</title>
 
     <indexterm>
       <primary>procmail</primary>
     </indexterm>
 
     <para>The <application>procmail</application> utility is an
       incredibly powerful application used to filter incoming mail.
       It allows users to define <quote>rules</quote> which can be
       matched to incoming mails to perform specific functions or to
       reroute mail to alternative mailboxes and/or email addresses.
       <application>procmail</application> can be installed using the
       <filename role="package">mail/procmail</filename> port.  Once
       installed, it can be directly integrated into most
       <acronym>MTA</acronym>s; consult your <acronym>MTA</acronym>
       documentation for more information.  Alternatively,
       <application>procmail</application> can be integrated by adding
       the following line to a <filename>.forward</filename> in the home
       directory of the user utilizing
       <application>procmail</application> features:</para>
 
     <programlisting>"|exec /usr/local/bin/procmail || exit 75"</programlisting>
 
     <para>The following section will display some basic
       <application>procmail</application> rules, as well as brief
       descriptions on what they do.  These rules, and others must be
       inserted into a <filename>.procmailrc</filename> file, which
       must reside in the user's home directory.</para>
 
     <para>The majority of these rules can also be found in the
       &man.procmailex.5; manual page.</para>
 
     <para>Forward all mail from <email>user@example.com</email> to an
       external address of <email role="nolink">goodmail@example2.com</email>:</para>
 
     <programlisting>:0
 * ^From.*user@example.com
 ! goodmail@example2.com</programlisting>
 
     <para>Forward all mails shorter than 1000 bytes to an external
       address of <email role="nolink">goodmail@example2.com</email>:</para>
 
     <programlisting>:0
 * &lt; 1000
 ! goodmail@example2.com</programlisting>
 
     <para>Send all mail sent to <email>alternate@example.com</email>
       into a mailbox called <filename>alternate</filename>:</para>
 
     <programlisting>:0
 * ^TOalternate@example.com
 alternate</programlisting>
 
     <para>Send all mail with a subject of <quote>Spam</quote> to
       <filename>/dev/null</filename>:</para>
 
     <programlisting>:0
 ^Subject:.*Spam
 /dev/null</programlisting>
 
     <para>A useful recipe that parses incoming <hostid role="domainname">&os;.org</hostid> mailing lists
       and places each list in its own mailbox:</para>
 
     <programlisting>:0
 * ^Sender:.owner-freebsd-\/[^@]+@FreeBSD.ORG
 {
 	LISTNAME=${MATCH}
 	:0
 	* LISTNAME??^\/[^@]+
 	FreeBSD-${MATCH}
 }</programlisting>
   </sect1>
 </chapter>
diff --git a/zh_TW.Big5/books/handbook/network-servers/chapter.xml b/zh_TW.Big5/books/handbook/network-servers/chapter.xml
index 92a98f24de..5588e07fc1 100644
--- a/zh_TW.Big5/books/handbook/network-servers/chapter.xml
+++ b/zh_TW.Big5/books/handbook/network-servers/chapter.xml
@@ -1,5202 +1,5185 @@
 <?xml version="1.0" encoding="big5"?>
 <!--
      The FreeBSD Documentation Project
 
      $FreeBSD$
      Original revision: 1.75
 -->
 
 <chapter id="network-servers">
   <chapterinfo>
     <authorgroup>
       <author>
         <firstname>Murray</firstname>
 	<surname>Stokely</surname>
 	<contrib>Reorganized by </contrib>
       </author>
     </authorgroup>
     <!-- 23 July 2004 -->
   </chapterinfo>
 
   <title>Network Servers</title>
 
   <sect1 id="network-servers-synopsis">
     <title>���z</title>
 
     <para>This chapter will cover some of the more frequently used
       network services on &unix; systems.  We will cover how to
       install, configure, test, and maintain many different types of
       network services.  Example configuration files are included
       throughout this chapter for you to benefit from.</para>
 
     <para>After reading this chapter, you will know:</para>
 
     <itemizedlist>
 
       <listitem>
 	<para>How to manage the <application>inetd</application>
 	  daemon.</para>
       </listitem>
 
       <listitem>
 	<para>How to set up a network file system.</para>
       </listitem>
 
       <listitem>
 	<para>How to set up a network information server for sharing
 	  user accounts.</para>
       </listitem>
 
       <listitem>
 	<para>How to set up automatic network settings using DHCP.</para>
       </listitem>
 
       <listitem>
 	<para>How to set up a domain name server.</para>
       </listitem>
 
       <listitem>
 	<para>How to set up the <application>Apache</application> HTTP Server.</para>
       </listitem>
 
       <listitem>
 	<para>How to set up a File Transfer Protocol (FTP) Server.</para>
       </listitem>
 
       <listitem>
 	<para>How to set up a file and print server for &windows;
 	  clients using <application>Samba</application>.</para>
       </listitem>
 
       <listitem>
 	<para>How to synchronize the time and date, and set up a
 	  time server, with the NTP protocol.</para>
       </listitem>
 
     </itemizedlist>
 
     <para>Before reading this chapter, you should:</para>
 
     <itemizedlist>
       <listitem>
 	<para>Understand the basics of the
 	  <filename>/etc/rc</filename> scripts.</para>
       </listitem>
 
       <listitem>
 	<para>Be familiar with basic network terminology.</para>
       </listitem>
 
       <listitem>
       <para>Know how to install additional third-party
         software (<xref linkend="ports"/>).</para>
       </listitem>
 
     </itemizedlist>
   </sect1>
 
   <sect1 id="network-inetd">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Chern</firstname>
           <surname>Lee</surname>
           <contrib>Contributed by </contrib>
         </author>
       </authorgroup>
     </sect1info>
 
     <title>The <application>inetd</application> <quote>Super-Server</quote></title>
 
     <sect2 id="network-inetd-overview">
       <title>Overview</title>
 
       <para>&man.inetd.8; is referred to as the <quote>Internet
 	Super-Server</quote> because it manages connections for
 	several services.  When a
 	connection is received by <application>inetd</application>, it
 	determines which program the connection is destined for, spawns
 	the particular process and delegates the socket to it (the program
 	is invoked with the service socket as its standard input, output
 	and error descriptors).  Running
 	one instance of <application>inetd</application> reduces the
 	overall system load as compared to running each daemon
 	individually in stand-alone mode.</para>
 
       <para>Primarily, <application>inetd</application> is used to
 	spawn other daemons, but several trivial protocols are handled
 	directly, such as <application>chargen</application>,
 	<application>auth</application>, and
 	<application>daytime</application>.</para>
 
       <para>This section will cover the basics in configuring
 	<application>inetd</application> through its command-line
 	options and its configuration file,
 	<filename>/etc/inetd.conf</filename>.</para>
     </sect2>
 
     <sect2 id="network-inetd-settings">
       <title>Settings</title>
 
       <para><application>inetd</application> is initialized through
 	the <filename>/etc/rc.conf</filename> system.  The
 	<literal>inetd_enable</literal> option is set to
 	<literal>NO</literal> by default, but is often times turned on
 	by <application>sysinstall</application> with the medium
 	security profile.  Placing:
 	<programlisting>inetd_enable="YES"</programlisting> or
 	<programlisting>inetd_enable="NO"</programlisting> into
 	<filename>/etc/rc.conf</filename> can enable or disable
 	<application>inetd</application> starting at boot time.</para>
 
       <para>Additionally, different command-line options can be passed
 	to <application>inetd</application> via the
 	<literal>inetd_flags</literal> option.</para>
     </sect2>
 
     <sect2 id="network-inetd-cmdline">
       <title>Command-Line Options</title>
 
       <para><application>inetd</application> synopsis:</para>
 
       <para><option>     inetd [-d] [-l] [-w] [-W] [-c maximum] [-C rate] [-a address | hostname]
            [-p filename] [-R rate] [configuration file]</option></para>
 
       <variablelist>
 	<varlistentry>
 	  <term>-d</term>
 
 	  <listitem>
 	    <para>Turn on debugging.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>-l</term>
 
 	  <listitem>
 	    <para>Turn on logging of successful connections.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>-w</term>
 
 	  <listitem>
 	    <para>Turn on TCP Wrapping for external services (on by
 	      default).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>-W</term>
 
 	  <listitem>
 	    <para>Turn on TCP Wrapping for internal services which are
 	      built into <application>inetd</application> (on by
 	      default).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>-c maximum</term>
 
 	  <listitem>
 	    <para>Specify the default maximum number of simultaneous
 	      invocations of each service; the default is unlimited.
 	      May be overridden on a per-service basis with the
 	      <option>max-child</option> parameter.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>-C rate</term>
 
 	  <listitem>
 	    <para>Specify the default maximum number of times a
 	      service can be invoked from a single IP address in one
 	      minute; the default is unlimited.  May be overridden on a
 	      per-service basis with the
 	      <option>max-connections-per-ip-per-minute</option>
 	      parameter.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>-R rate</term>
 
 	  <listitem>
 	    <para>Specify the maximum number of times a service can be
 	      invoked in one minute; the default is 256.  A rate of 0
 	      allows an unlimited number of invocations.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>-a</term>
 
 	  <listitem>
 	    <para>Specify one specific IP address to bind to.
 	      Alternatively, a hostname can be specified, in which case
 	      the IPv4 or IPv6 address which corresponds to that
 	      hostname is used.  Usually a hostname is specified when
 	      <application>inetd</application> is run inside a
 	      &man.jail.8;, in which case the hostname corresponds to
 	      the &man.jail.8; environment.</para>
 
 	    <para>When hostname specification is used and both IPv4
 	      and IPv6 bindings are desired, one entry with the
 	      appropriate protocol type for each binding is required
 	      for each service in
 	      <filename>/etc/inetd.conf</filename>.  For example, a
 	      TCP-based service would need two entries, one using
 	      <literal>tcp4</literal> for the protocol and the other
 	      using <literal>tcp6</literal>.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>-p</term>
 
 	  <listitem>
 	    <para>Specify an alternate file in which to store the
 	      process ID.</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
 
       <para>These options can be passed to
 	<application>inetd</application> using the
 	<literal>inetd_flags</literal> option in
 	<filename>/etc/rc.conf</filename>.  By default,
 	<literal>inetd_flags</literal> is set to
 	<literal>-wW</literal>, which turns on TCP wrapping for
 	<application>inetd</application>'s internal and external
 	services.  For novice users, these parameters usually do not
 	need to be modified or even entered in
 	<filename>/etc/rc.conf</filename>.</para>
 
       <note>
 	<para>An external service is a daemon outside of
 	  <application>inetd</application>, which is invoked when a
 	  connection is received for it.  On the other hand, an
 	  internal service is one that
 	  <application>inetd</application> has the facility of
 	  offering within itself.</para>
       </note>
 
     </sect2>
 
     <sect2 id="network-inetd-conf">
       <title><filename>inetd.conf</filename></title>
 
       <para>Configuration of <application>inetd</application> is
 	controlled through the <filename>/etc/inetd.conf</filename>
 	file.</para>
 
       <para>When a modification is made to
 	<filename>/etc/inetd.conf</filename>,
 	<application>inetd</application> can be forced to re-read its
 	configuration file by sending a HangUP signal to the
 	<application>inetd</application> process as shown:</para>
 
       <example id="network-inetd-hangup">
 	<title>Sending <application>inetd</application> a HangUP Signal</title>
 
 	<screen>&prompt.root; <userinput>kill -HUP `cat /var/run/inetd.pid`</userinput></screen>
       </example>
 
       <para>Each line of the configuration file specifies an
 	individual daemon.  Comments in the file are preceded by a
 	<quote>#</quote>.  The format of
 	<filename>/etc/inetd.conf</filename> is as follows:</para>
 
       <programlisting>service-name
 socket-type
 protocol
 {wait|nowait}[/max-child[/max-connections-per-ip-per-minute]]
 user[:group][/login-class]
 server-program
 server-program-arguments</programlisting>
 
       <para>An example entry for the <application>ftpd</application> daemon
 	using IPv4:</para>
 
       <programlisting>ftp     stream  tcp     nowait  root    /usr/libexec/ftpd       ftpd -l</programlisting>
 
       <variablelist>
 	<varlistentry>
 	  <term>service-name</term>
 
 	  <listitem>
 	    <para>This is the service name of the particular daemon.
 	      It must correspond to a service listed in
 	      <filename>/etc/services</filename>.  This determines
 	      which port <application>inetd</application> must listen
 	      to.  If a new service is being created, it must be
 	      placed in <filename>/etc/services</filename>
 	      first.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>socket-type</term>
 
 	  <listitem>
 	    <para>Either <literal>stream</literal>,
 	      <literal>dgram</literal>, <literal>raw</literal>, or
 	      <literal>seqpacket</literal>.  <literal>stream</literal>
 	      must be used for connection-based, TCP daemons, while
 	      <literal>dgram</literal> is used for daemons utilizing
 	      the <acronym>UDP</acronym> transport protocol.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>protocol</term>
 
 	  <listitem>
 	    <para>One of the following:</para>
 
 	    <informaltable frame="none" pgwide="1">
 	      <tgroup cols="2">
 		<thead>
 		  <row>
 		    <entry>Protocol</entry>
 		    <entry>Explanation</entry>
 		  </row>
 		</thead>
 		<tbody>
 		  <row>
 		    <entry>tcp, tcp4</entry>
 		    <entry>TCP IPv4</entry>
 		  </row>
 		  <row>
 		    <entry>udp, udp4</entry>
 		    <entry>UDP IPv4</entry>
 		  </row>
 		  <row>
 		    <entry>tcp6</entry>
 		    <entry>TCP IPv6</entry>
 		  </row>
 		  <row>
 		    <entry>udp6</entry>
 		    <entry>UDP IPv6</entry>
 		  </row>
 		  <row>
 		    <entry>tcp46</entry>
 		    <entry>Both TCP IPv4 and v6</entry>
 		  </row>
 		  <row>
 		    <entry>udp46</entry>
 		    <entry>Both UDP IPv4 and v6</entry>
 		  </row>
 		</tbody>
 	      </tgroup>
 	    </informaltable>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>{wait|nowait}[/max-child[/max-connections-per-ip-per-minute]]</term>
 
 	  <listitem>
 	    <para><option>wait|nowait</option> indicates whether the
 	      daemon invoked from <application>inetd</application> is
 	      able to handle its own socket or not.
 	      <option>dgram</option> socket types must use the
 	      <option>wait</option> option, while stream socket
 	      daemons, which are usually multi-threaded, should use
 	      <option>nowait</option>.  <option>wait</option> usually
 	      hands off multiple sockets to a single daemon, while
 	      <option>nowait</option> spawns a child daemon for each
 	      new socket.</para>
 
 	    <para>The maximum number of child daemons
 	      <application>inetd</application> may spawn can be set
 	      using the <option>max-child</option> option.  If a limit
 	      of ten instances of a particular daemon is needed, a
 	      <literal>/10</literal> would be placed after
 	      <option>nowait</option>.</para>
 
 	    <para>In addition to <option>max-child</option>, another
 	      option limiting the maximum connections from a single
 	      place to a particular daemon can be enabled.
 	      <option>max-connections-per-ip-per-minute</option> does
 	      just this.  A value of ten here would limit any particular
 	      IP address connecting to a particular service to ten
 	      attempts per minute.  This is useful to prevent
 	      intentional or unintentional resource consumption and
 	      Denial of Service (DoS) attacks to a machine.</para>
 
 	    <para>In this field, <option>wait</option> or
 	      <option>nowait</option> is mandatory.
 	      <option>max-child</option> and
 	      <option>max-connections-per-ip-per-minute</option> are
 	      optional.</para>
 
 	    <para>A stream-type multi-threaded daemon without any
 	      <option>max-child</option> or
 	      <option>max-connections-per-ip-per-minute</option> limits
 	      would simply be: <literal>nowait</literal>.</para>
 
 	    <para>The same daemon with a maximum limit of ten daemons
 	      would read: <literal>nowait/10</literal>.</para>
 
 	    <para>Additionally, the same setup with a limit of twenty
 	      connections per IP address per minute and a maximum
 	      total limit of ten child daemons would read:
 	      <literal>nowait/10/20</literal>.</para>
 
 	    <para>These options are all utilized by the default
 	      settings of the <application>fingerd</application> daemon,
 	      as seen here:</para>
 
 	    <programlisting>finger stream  tcp     nowait/3/10 nobody /usr/libexec/fingerd fingerd -s</programlisting>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>user</term>
 
 	  <listitem>
 	    <para>This is the username that the particular daemon
 	      should run as.  Most commonly, daemons run as the
 	      <username>root</username> user.  For security purposes, it is
 	      common to find some servers running as the
 	      <username>daemon</username> user, or the least privileged
 	      <username>nobody</username> user.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>server-program</term>
 
 	  <listitem>
 	    <para>The full path of the daemon to be executed when a
 	      connection is received.  If the daemon is a service
 	      provided by <application>inetd</application> internally,
 	      then <option>internal</option> should be
 	      used.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>server-program-arguments</term>
 
 	  <listitem>
 	    <para>This works in conjunction with
 	      <option>server-program</option> by specifying the
 	      arguments, starting with <literal>argv[0]</literal>,
 	      passed to the daemon on invocation.  If
 	      <command>mydaemon -d</command> is the command line,
 	      <literal>mydaemon -d</literal> would be the value of
 	      <option>server-program-arguments</option>.  Again, if
 	      the daemon is an internal service, use
 	      <option>internal</option> here.</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
     </sect2>
 
     <sect2 id="network-inetd-security">
       <title>Security</title>
 
       <para>Depending on the security profile chosen at install, many
 	of <application>inetd</application>'s daemons may be enabled
 	by default.  If there is no apparent need for a particular
 	daemon, disable it!  Place a <quote>#</quote> in front of the
 	daemon in question in <filename>/etc/inetd.conf</filename>,
 	and then send a <link linkend="network-inetd-hangup">hangup
 	signal to inetd</link>.  Some daemons, such as
 	<application>fingerd</application>, may not be desired at all
 	because they provide an attacker with too much
 	information.</para>
 
       <para>Some daemons are not security-conscious and have long, or
 	non-existent timeouts for connection attempts.  This allows an
 	attacker to slowly send connections to a particular daemon,
 	thus saturating available resources.  It may be a good idea to
 	place <option>max-connections-per-ip-per-minute</option> and
 	<option>max-child</option> limitations on certain
 	daemons.</para>
 
       <para>By default, TCP wrapping is turned on.  Consult the
 	&man.hosts.access.5; manual page for more information on placing
 	TCP restrictions on various <application>inetd</application>
 	invoked daemons.</para>
     </sect2>
 
     <sect2 id="network-inetd-misc">
       <title>Miscellaneous</title>
 
       <para><application>daytime</application>,
 	<application>time</application>,
 	<application>echo</application>,
 	<application>discard</application>,
 	<application>chargen</application>, and
 	<application>auth</application> are all internally provided
 	services of <application>inetd</application>.</para>
 
       <para>The <application>auth</application> service provides
 	identity (<application>ident</application>,
 	<application>identd</application>) network services, and is
 	configurable to a certain degree.</para>
 
       <para>Consult the &man.inetd.8; manual page for more in-depth
 	information.</para>
     </sect2>
   </sect1>
 
   <sect1 id="network-nfs">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Tom</firstname>
           <surname>Rhodes</surname>
           <contrib>Reorganized and enhanced by </contrib>
         </author>
       </authorgroup>
       <authorgroup>
         <author>
           <firstname>Bill</firstname>
       	  <surname>Swingle</surname>
 	  <contrib>Written by </contrib>
         </author>
       </authorgroup>
     </sect1info>
     <title>Network File System (NFS)</title>
 
     <indexterm><primary>NFS</primary></indexterm>
     <para>Among the many different file systems that FreeBSD supports
       is the Network File System, also known as <acronym role="Network
       File System">NFS</acronym>.  <acronym role="Network File
       System">NFS</acronym> allows a system to share directories and
       files with others over a network.  By using <acronym
       role="Network File System">NFS</acronym>, users and programs can
       access files on remote systems almost as if they were local
       files.</para>
 
     <para>Some of the most notable benefits that
       <acronym>NFS</acronym> can provide are:</para>
 
     <itemizedlist>
       <listitem>
 	<para>Local workstations use less disk space because commonly
 	  used data can be stored on a single machine and still remain
 	  accessible to others over the network.</para>
       </listitem>
 
       <listitem>
 	<para>There is no need for users to have separate home
 	  directories on every network machine.  Home directories
 	  could be set up on the <acronym>NFS</acronym> server and
 	  made available throughout the network.</para>
       </listitem>
 
       <listitem>
 	<para>Storage devices such as floppy disks, CDROM drives, and
 	  &iomegazip; drives can be used by other machines on the network.
 	  This may reduce the number of removable media drives
 	  throughout the network.</para>
       </listitem>
     </itemizedlist>
 
     <sect2>
       <title>How <acronym>NFS</acronym> Works</title>
 
       <para><acronym>NFS</acronym> consists of at least two main
         parts: a server and one or more clients.  The client remotely
         accesses the data that is stored on the server machine.  In
         order for this to function properly a few processes have to be
         configured and running.</para>
 
       <note><para>Under &os;&nbsp;4.X, the <application>portmap</application>
 	utility is used in place of the
 	<application>rpcbind</application> utility.  Thus, in &os;&nbsp;4.X
 	the user is required to replace every instance of
 	<application>rpcbind</application> with
 	<application>portmap</application> in the forthcoming
 	examples.</para></note>
 
       <para>The server has to be running the following daemons:</para>
       <indexterm>
         <primary>NFS</primary>
         <secondary>server</secondary>
       </indexterm>
       <indexterm>
         <primary>file server</primary>
         <secondary>UNIX clients</secondary>
       </indexterm>
 
       <indexterm>
 	<primary><application>rpcbind</application></primary>
       </indexterm>
       <indexterm>
         <primary><application>portmap</application></primary>
       </indexterm>
       <indexterm>
         <primary><application>mountd</application></primary>
       </indexterm>
       <indexterm>
         <primary><application>nfsd</application></primary>
       </indexterm>
 
       <informaltable frame="none" pgwide="1">
 	<tgroup cols="2">
 	  <colspec colwidth="1*"/>
 	  <colspec colwidth="3*"/>
 
 	  <thead>
 	    <row>
 	      <entry>Daemon</entry>
 	      <entry>Description</entry>
 	    </row>
 	  </thead>
 	  <tbody>
 	    <row>
 	      <entry><application>nfsd</application></entry>
 	      <entry>The <acronym>NFS</acronym> daemon which services
 	      requests from the <acronym>NFS</acronym>
 	      clients.</entry>
 	    </row>
 	    <row>
 	      <entry><application>mountd</application></entry>
 	      <entry>The <acronym>NFS</acronym> mount daemon which carries out
 		the requests that &man.nfsd.8; passes on to it.</entry>
 	    </row>
 	    <row>
 	      <entry><application>rpcbind</application></entry>
 	      <entry> This daemon allows
 	      <acronym>NFS</acronym> clients to discover which port
 	      the <acronym>NFS</acronym> server is using.</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
 
       <para>The client can also run a daemon, known as
         <application>nfsiod</application>.  The
         <application>nfsiod</application> daemon services the requests
         from the <acronym>NFS</acronym> server.  This is optional, and
         improves performance, but is not required for normal and
         correct operation.  See the &man.nfsiod.8; manual page for
         more information.
       </para>
     </sect2>
 
     <sect2 id="network-configuring-nfs">
       <title>Configuring <acronym>NFS</acronym></title>
       <indexterm>
         <primary>NFS</primary>
         <secondary>configuration</secondary>
       </indexterm>
 
       <para><acronym>NFS</acronym> configuration is a relatively
         straightforward process.  The processes that need to be
         running can all start at boot time with a few modifications to
         your <filename>/etc/rc.conf</filename> file.</para>
 
       <para>On the <acronym>NFS</acronym> server, make sure that the
         following options are configured in the
         <filename>/etc/rc.conf</filename> file:</para>
 
       <programlisting>rpcbind_enable="YES"
 nfs_server_enable="YES"
 mountd_flags="-r"</programlisting>
 
       <para><application>mountd</application> runs automatically
         whenever the <acronym>NFS</acronym> server is enabled.</para>
 
       <para>On the client, make sure this option is present in
         <filename>/etc/rc.conf</filename>:</para>
 
       <programlisting>nfs_client_enable="YES"</programlisting>
 
       <para>The <filename>/etc/exports</filename> file specifies which
         file systems <acronym>NFS</acronym> should export (sometimes
         referred to as <quote>share</quote>).  Each line in
         <filename>/etc/exports</filename> specifies a file system to be
         exported and which machines have access to that file system.
         Along with what machines have access to that file system,
         access options may also be specified.  There are many such
         options that can be used in this file but only a few will be
         mentioned here.  You can easily discover other options by
         reading over the &man.exports.5; manual page.</para>
 
       <para>Here are a few example <filename>/etc/exports</filename>
 	entries:</para>
 
       <indexterm>
         <primary>NFS</primary>
         <secondary>export examples</secondary>
       </indexterm>
 
       <para>The following examples give an idea of how to export
         file systems, although the settings may be different depending
         on your environment and network configuration.  For instance,
         to export the <filename>/cdrom</filename> directory to three
         example machines that have the same domain name as the server
         (hence the lack of a domain name for each) or have entries in
         your <filename>/etc/hosts</filename> file.  The
         <option>-ro</option> flag makes the exported file system
         read-only.  With this flag, the remote system will not be able
         to write any changes to the exported file system.</para>
 
       <programlisting>/cdrom -ro host1 host2 host3</programlisting>
 
       <para>The following line exports <filename>/home</filename> to
 	three hosts by IP address.  This is a useful setup if you have
 	a private network without a <acronym>DNS</acronym> server
 	configured.  Optionally the <filename>/etc/hosts</filename>
 	file could be configured for internal hostnames; please review
 	&man.hosts.5; for more information.  The
 	<option>-alldirs</option> flag allows the subdirectories to be
 	mount points.  In other words, it will not mount the
 	subdirectories but permit the client to mount only the
 	directories that are required or needed.</para>
 
       <programlisting>/home  -alldirs  10.0.0.2 10.0.0.3 10.0.0.4</programlisting>
 
       <para>The following line exports <filename>/a</filename> so that
 	two clients from different domains may access the file system.
 	The <option>-maproot=root</option> flag allows the
 	<username>root</username> user on the remote system to write
 	data on the exported file system as <username>root</username>.
 	If the <literal>-maproot=root</literal> flag is not specified,
 	then even if a user has <username>root</username> access on
 	the remote system, he will not be able to modify files on
 	the exported file system.</para>
 
       <programlisting>/a  -maproot=root  host.example.com box.example.org</programlisting>
 
       <para>In order for a client to access an exported file system,
 	the client must have permission to do so.  Make sure the
 	client is listed in your <filename>/etc/exports</filename>
 	file.</para>
 
       <para>In <filename>/etc/exports</filename>, each line represents
 	the export information for one file system to one host.  A
 	remote host can only be specified once per file system, and may
 	only have one default entry.  For example, assume that
 	<filename>/usr</filename> is a single file system.  The
 	following <filename>/etc/exports</filename> would be
 	invalid:</para>
 
       <programlisting># Invalid when /usr is one file system
 /usr/src   client
 /usr/ports client</programlisting>
 
       <para>One file system, <filename>/usr</filename>, has two lines
 	specifying exports to the same host, <hostid>client</hostid>.
         The correct format for this situation is:</para>
 
       <programlisting>/usr/src /usr/ports  client</programlisting>
 
       <para>The properties of one file system exported to a given host
 	must all occur on one line.  Lines without a client specified
 	are treated as a single host.  This limits how you can export
 	file systems, but for most people this is not an issue.</para>
 
       <para>The following is an example of a valid export list, where
 	<filename>/usr</filename> and <filename>/exports</filename>
 	are local file systems:</para>
 
       <programlisting># Export src and ports to client01 and client02, but only
 # client01 has root privileges on it
 /usr/src /usr/ports -maproot=root    client01
 /usr/src /usr/ports               client02
 # The client machines have root and can mount anywhere
 # on /exports. Anyone in the world can mount /exports/obj read-only
 /exports -alldirs -maproot=root      client01 client02
 /exports/obj -ro</programlisting>
 
       <para>You must restart
         <application>mountd</application> whenever you modify
         <filename>/etc/exports</filename> so the changes can take effect.
         This can be accomplished by sending the HUP signal
         to the <command>mountd</command> process:</para>
 
       <screen>&prompt.root; <userinput>kill -HUP `cat /var/run/mountd.pid`</userinput></screen>
 
       <para>Alternatively, a reboot will make FreeBSD set everything
         up properly.  A reboot is not necessary though.
         Executing the following commands as <username>root</username>
         should start everything up.</para>
 
       <para>On the <acronym>NFS</acronym> server:</para>
 
       <screen>&prompt.root; <userinput>rpcbind</userinput>
 &prompt.root; <userinput>nfsd -u -t -n 4</userinput>
 &prompt.root; <userinput>mountd -r</userinput></screen>
 
       <para>On the <acronym>NFS</acronym> client:</para>
 
       <screen>&prompt.root; <userinput>nfsiod -n 4</userinput></screen>
 
       <para>Now everything should be ready to actually mount a remote file
 	system.  In these examples the
 	server's name will be <hostid>server</hostid> and the client's
 	name will be <hostid>client</hostid>.  If you only want to
 	temporarily mount a remote file system or would rather test the
 	configuration, just execute a command like this as <username>root</username> on the
         client:</para>
       <indexterm>
         <primary>NFS</primary>
         <secondary>mounting</secondary>
       </indexterm>
       <screen>&prompt.root; <userinput>mount server:/home /mnt</userinput></screen>
 
       <para>This will mount the <filename>/home</filename> directory
 	on the server at <filename>/mnt</filename> on the client.  If
 	everything is set up correctly you should be able to enter
 	<filename>/mnt</filename> on the client and see all the files
         that are on the server.</para>
 
       <para>If you want to automatically mount a remote file system
 	each time the computer boots, add the file system to the
 	<filename>/etc/fstab</filename> file.  Here is an example:</para>
 
       <programlisting>server:/home	/mnt	nfs	rw	0	0</programlisting>
 
       <para>The &man.fstab.5; manual page lists all the available
         options.</para>
     </sect2>
 
     <sect2>
       <title>Practical Uses</title>
 
       <para><acronym>NFS</acronym> has many practical uses.  Some of
         the more common ones are listed below:</para>
 
       <indexterm>
         <primary>NFS</primary>
         <secondary>uses</secondary>
       </indexterm>
       <itemizedlist>
         <listitem>
 	  <para>Set several machines to share a CDROM or other media
 	    among them.  This is cheaper and often a more convenient
 	    method to install software on multiple machines.</para>
 	</listitem>
 
 	<listitem>
 	  <para>On large networks, it might be more convenient to
 	    configure a central <acronym>NFS</acronym> server in which
 	    to store all the user home directories.  These home
 	    directories can then be exported to the network so that
 	    users would always have the same home directory,
 	    regardless of which workstation they log in to.</para>
 	</listitem>
 
 	<listitem>
 	  <para>Several machines could have a common
             <filename>/usr/ports/distfiles</filename> directory.  That
             way, when you need to install a port on several machines,
             you can quickly access the source without downloading it
             on each machine.</para>
 	</listitem>
       </itemizedlist>
     </sect2>
 
     <sect2 id="network-amd">
       <sect2info>
 	<authorgroup>
 	  <author>
 	    <firstname>Wylie</firstname>
 	    <surname>Stilwell</surname>
 	    <contrib>Contributed by </contrib>
 	  </author>
 	</authorgroup>
 	<authorgroup>
 	  <author>
 	    <firstname>Chern</firstname>
 	    <surname>Lee</surname>
 	    <contrib>Rewritten by </contrib>
 	  </author>
 	</authorgroup>
       </sect2info>
       <title>Automatic Mounts with <application>amd</application></title>
 
       <indexterm><primary>amd</primary></indexterm>
       <indexterm><primary>automatic mounter daemon</primary></indexterm>
 
       <para>&man.amd.8; (the automatic mounter daemon)
 	automatically mounts a
 	remote file system whenever a file or directory within that
 	file system is accessed.  Filesystems that are inactive for a
 	period of time will also be automatically unmounted by
 	<application>amd</application>.  Using
 	<application>amd</application> provides a simple alternative
 	to permanent mounts, as permanent mounts are usually listed in
         <filename>/etc/fstab</filename>.</para>
 
       <para><application>amd</application> operates by attaching
 	itself as an NFS server to the <filename>/host</filename> and
 	<filename>/net</filename> directories.  When a file is accessed
 	within one of these directories, <application>amd</application>
 	looks up the corresponding remote mount and automatically mounts
 	it.  <filename>/net</filename> is used to mount an exported
 	file system from an IP address, while <filename>/host</filename>
 	is used to mount an export from a remote hostname.</para>
 
       <para>An access to a file within
 	<filename>/host/foobar/usr</filename> would tell
 	<application>amd</application> to attempt to mount the
 	<filename>/usr</filename> export on the host
 	<hostid>foobar</hostid>.</para>
 
       <example>
 	<title>Mounting an Export with <application>amd</application></title>
 
 	<para>You can view the available mounts of a remote host with
 	  the <command>showmount</command> command.  For example, to
 	  view the mounts of a host named <hostid>foobar</hostid>, you
 	  can use:</para>
 
 	<screen>&prompt.user; <userinput>showmount -e foobar</userinput>
 Exports list on foobar:
 /usr                               10.10.10.0
 /a                                 10.10.10.0
 &prompt.user; <userinput>cd /host/foobar/usr</userinput></screen>
       </example>
 
       <para>As seen in the example, the <command>showmount</command> shows
 	<filename>/usr</filename> as an export.  When changing directories to
 	<filename>/host/foobar/usr</filename>, <application>amd</application>
 	attempts to resolve the hostname <hostid>foobar</hostid> and
 	automatically mount the desired export.</para>
 
       <para><application>amd</application> can be started by the
 	startup scripts by placing the following lines in
 	<filename>/etc/rc.conf</filename>:</para>
 
       <programlisting>amd_enable="YES"</programlisting>
 
       <para>Additionally, custom flags can be passed to
       <application>amd</application> from the
       <varname>amd_flags</varname> option.  By default,
       <varname>amd_flags</varname> is set to:</para>
 
       <programlisting>amd_flags="-a /.amd_mnt -l syslog /host /etc/amd.map /net /etc/amd.map"</programlisting>
 
       <para>The <filename>/etc/amd.map</filename> file defines the
 	default options that exports are mounted with.  The
 	<filename>/etc/amd.conf</filename> file defines some of the more
 	advanced features of <application>amd</application>.</para>
 
       <para>Consult the &man.amd.8; and &man.amd.conf.5; manual pages for more
 	information.</para>
     </sect2>
 
     <sect2 id="network-nfs-integration">
       <sect2info>
         <authorgroup>
           <author>
             <firstname>John</firstname>
             <surname>Lind</surname>
             <contrib>Contributed by </contrib>
           </author>
         </authorgroup>
       </sect2info>
       <title>Problems Integrating with Other Systems</title>
 
       <para>Certain Ethernet adapters for ISA PC systems have limitations
 	which can lead to serious network problems, particularly with NFS.
 	This difficulty is not specific to FreeBSD, but FreeBSD systems
 	are affected by it.</para>
 
       <para>The problem nearly always occurs when (FreeBSD) PC systems are
 	networked with high-performance workstations, such as those made
 	by Silicon Graphics, Inc., and Sun Microsystems, Inc.  The NFS
 	mount will work fine, and some operations may succeed, but
 	suddenly the server will seem to become unresponsive to the
 	client, even though requests to and from other systems continue to
 	be processed.  This happens to the client system, whether the
 	client is the FreeBSD system or the workstation.  On many systems,
 	there is no way to shut down the client gracefully once this
 	problem has manifested itself.  The only solution is often to
 	reset the client, because the NFS situation cannot be
 	resolved.</para>
 
       <para>Though the <quote>correct</quote> solution is to get a
 	higher performance and capacity Ethernet adapter for the
 	FreeBSD system, there is a simple workaround that will allow
 	satisfactory operation.  If the FreeBSD system is the
 	<emphasis>server</emphasis>, include the option
 	<option>-w=1024</option> on the mount from the client.  If the
 	FreeBSD system is the <emphasis>client</emphasis>, then mount
 	the NFS file system with the option <option>-r=1024</option>.
 	These options may be specified using the fourth field of the
 	<filename>fstab</filename> entry on the client for automatic
 	mounts, or by using the <option>-o</option> parameter of the
 	&man.mount.8; command for manual mounts.</para>
 
       <para>It should be noted that there is a different problem,
 	sometimes mistaken for this one, when the NFS servers and
 	clients are on different networks.  If that is the case, make
 	<emphasis>certain</emphasis> that your routers are routing the
 	necessary <acronym>UDP</acronym> information, or you will not get anywhere, no
 	matter what else you are doing.</para>
 
       <para>In the following examples, <hostid>fastws</hostid> is the host
 	(interface) name of a high-performance workstation, and
 	<hostid>freebox</hostid> is the host (interface) name of a FreeBSD
 	system with a lower-performance Ethernet adapter.  Also,
 	<filename>/sharedfs</filename> will be the exported NFS
 	file system (see &man.exports.5;), and
 	<filename>/project</filename> will be the mount point on the
 	client for the exported file system.  In all cases, note that
 	additional options, such as <option>hard</option> or
 	<option>soft</option> and <option>bg</option> may be desirable in
 	your application.</para>
 
       <para>Examples for the FreeBSD system (<hostid>freebox</hostid>)
 	as the client in <filename>/etc/fstab</filename> on
 	<hostid>freebox</hostid>:</para>
 
       <programlisting>fastws:/sharedfs /project nfs rw,-r=1024 0 0</programlisting>
 
       <para>As a manual mount command on <hostid>freebox</hostid>:</para>
 
       <screen>&prompt.root; <userinput>mount -t nfs -o -r=1024 fastws:/sharedfs /project</userinput></screen>
 
       <para>Examples for the FreeBSD system as the server in
 	<filename>/etc/fstab</filename> on
 	<hostid>fastws</hostid>:</para>
 
       <programlisting>freebox:/sharedfs /project nfs rw,-w=1024 0 0</programlisting>
 
       <para>As a manual mount command on <hostid>fastws</hostid>:</para>
 
       <screen>&prompt.root; <userinput>mount -t nfs -o -w=1024 freebox:/sharedfs /project</userinput></screen>
 
       <para>Nearly any 16-bit Ethernet adapter will allow operation
 	without the above restrictions on the read or write size.</para>
 
       <para>For anyone who cares, here is what happens when the
 	failure occurs, which also explains why it is unrecoverable.
 	NFS typically works with a <quote>block</quote> size of
 	8&nbsp;K (though it may do fragments of smaller sizes).  Since
 	the maximum Ethernet packet is around 1500&nbsp;bytes, the NFS
 	<quote>block</quote> gets split into multiple Ethernet
 	packets, even though it is still a single unit to the
 	upper-level code, and must be received, assembled, and
 	<emphasis>acknowledged</emphasis> as a unit.  The
 	high-performance workstations can pump out the packets which
 	comprise the NFS unit one right after the other, just as close
 	together as the standard allows.  On the smaller, lower
 	capacity cards, the later packets overrun the earlier packets
 	of the same unit before they can be transferred to the host
 	and the unit as a whole cannot be reconstructed or
 	acknowledged.  As a result, the workstation will time out and
 	try again, but it will try again with the entire 8&nbsp;K
 	unit, and the process will be repeated, ad infinitum.</para>
 
       <para>By keeping the unit size below the Ethernet packet size
 	limitation, we ensure that any complete Ethernet packet
 	received can be acknowledged individually, avoiding the
 	deadlock situation.</para>
 
       <para>Overruns may still occur when a high-performance
 	workstations is slamming data out to a PC system, but with the
 	better cards, such overruns are not guaranteed on NFS
 	<quote>units</quote>.  When an overrun occurs, the units
 	affected will be retransmitted, and there will be a fair
 	chance that they will be received, assembled, and
 	acknowledged.</para>
     </sect2>
   </sect1>
 
   <sect1 id="network-nis">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Bill</firstname>
       	  <surname>Swingle</surname>
 	  <contrib>Written by </contrib>
          </author>
       </authorgroup>
       <authorgroup>
 	<author>
 	  <firstname>Eric</firstname>
 	  <surname>Ogren</surname>
 	  <contrib>Enhanced by </contrib>
 	</author>
 	<author>
 	  <firstname>Udo</firstname>
 	  <surname>Erdelhoff</surname>
 	</author>
       </authorgroup>
     </sect1info>
     <title>Network Information System (NIS/YP)</title>
 
     <sect2>
       <title>What Is It?</title>
       <indexterm><primary>NIS</primary></indexterm>
       <indexterm><primary>Solaris</primary></indexterm>
       <indexterm><primary>HP-UX</primary></indexterm>
       <indexterm><primary>AIX</primary></indexterm>
       <indexterm><primary>Linux</primary></indexterm>
       <indexterm><primary>NetBSD</primary></indexterm>
       <indexterm><primary>OpenBSD</primary></indexterm>
 
       <para><acronym role="Network Information System">NIS</acronym>,
         which stands for Network Information Services, was developed
         by Sun Microsystems to centralize administration of &unix;
         (originally &sunos;) systems.  It has now essentially become
         an industry standard; all major &unix; like systems
         (&solaris;, HP-UX, &aix;, Linux, NetBSD, OpenBSD, FreeBSD,
         etc) support <acronym role="Network Information
         System">NIS</acronym>.</para>
 
       <indexterm><primary>yellow pages</primary><see>NIS</see></indexterm>
 
       <para><acronym role="Network Information System">NIS</acronym>
 	was formerly known as Yellow Pages, but because of trademark
 	issues, Sun changed the name.  The old term (and yp) is still
 	often seen and used.</para>
 
       <indexterm>
         <primary>NIS</primary>
         <secondary>domains</secondary>
       </indexterm>
 
       <para>It is a RPC-based client/server system that allows a group
 	of machines within an NIS domain to share a common set of
 	configuration files.  This permits a system administrator to
 	set up NIS client systems with only minimal configuration data
 	and add, remove or modify configuration data from a single
 	location.</para>
 
       <indexterm><primary>Windows NT</primary></indexterm>
 
       <para>It is similar to the &windowsnt; domain system; although
         the internal implementation of the two are not at all similar,
         the basic functionality can be compared.</para>
     </sect2>
 
     <sect2>
       <title>Terms/Processes You Should Know</title>
 
       <para>There are several terms and several important user
         processes that you will come across when attempting to
         implement NIS on FreeBSD, whether you are trying to create an
         NIS server or act as an NIS client:</para>
 
       <indexterm>
 	<primary><application>rpcbind</application></primary>
       </indexterm>
       <indexterm>
 	<primary><application>portmap</application></primary>
       </indexterm>
 
       <informaltable frame="none" pgwide="1">
 	<tgroup cols="2">
 	<colspec colwidth="1*"/>
 	<colspec colwidth="3*"/>
 
 	  <thead>
 	    <row>
 	      <entry>Term</entry>
 	      <entry>Description</entry>
 	    </row>
 	  </thead>
 	  <tbody>
 	    <row>
 	      <entry>NIS domainname</entry>
 
 	      <entry>An NIS master server and all of its clients
 		(including its slave servers) have a NIS domainname.
 		Similar to an &windowsnt; domain name, the NIS
 		domainname does not have anything to do with
 		<acronym>DNS</acronym>.</entry>
 	    </row>
 	    <row>
 	      <entry><application>rpcbind</application></entry>
 
 	      <entry>Must be running in order to enable
 		<acronym>RPC</acronym> (Remote Procedure Call, a
 		network protocol used by NIS).  If
 		<application>rpcbind</application> is not running, it
 		will be impossible to run an NIS server, or to act as
 		an NIS client (Under &os;&nbsp;4.X
 		<application>portmap</application> is used in place of
 		<application>rpcbind</application>).</entry>
 	    </row>
 	    <row>
 	      <entry><application>ypbind</application></entry>
 
 	      <entry><quote>Binds</quote> an NIS client to its NIS
 		server.  It will take the NIS domainname from the
 		system, and using <acronym>RPC</acronym>, connect to
 		the server.  <application>ypbind</application> is the
 		core of client-server communication in an NIS
 		environment; if <application>ypbind</application> dies
 		on a client machine, it will not be able to access the
 		NIS server.</entry>
 	    </row>
 	    <row>
 	      <entry><application>ypserv</application></entry>
 	      <entry>Should only be running on NIS servers; this is
 		the NIS server process itself.  If &man.ypserv.8;
 		dies, then the server will no longer be able to
 		respond to NIS requests (hopefully, there is a slave
 		server to take over for it).  There are some
 		implementations of NIS (but not the FreeBSD one), that
 		do not try to reconnect to another server if the
 		server it used before dies.  Often, the only thing
 		that helps in this case is to restart the server
 		process (or even the whole server) or the
 		<application>ypbind</application> process on the
 		client.
 	      </entry>
 	    </row>
 	    <row>
 	      <entry><application>rpc.yppasswdd</application></entry>
 	      <entry>Another process that should only be running on
 		NIS master servers; this is a daemon that will allow NIS
 		clients to change their NIS passwords.  If this daemon
 		is not running, users will have to login to the NIS
 		master server and change their passwords there.</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
       <!-- XXX Missing: rpc.ypxfrd (not important, though) May only run
       on the master -->
 
     </sect2>
 
     <sect2>
       <title>How Does It Work?</title>
 
       <para>There are three types of hosts in an NIS environment:
 	master servers, slave servers, and clients.  Servers act as a
 	central repository for host configuration information.  Master
 	servers hold the authoritative copy of this information, while
 	slave servers mirror this information for redundancy.  Clients
 	rely on the servers to provide this information to
 	them.</para>
 
       <para>Information in many files can be shared in this manner.
 	The <filename>master.passwd</filename>,
 	<filename>group</filename>, and <filename>hosts</filename>
 	files are commonly shared via NIS.  Whenever a process on a
 	client needs information that would normally be found in these
 	files locally, it makes a query to the NIS server that it is
 	bound to instead.</para>
 
       <sect3>
         <title>Machine Types</title>
 
         <itemizedlist>
-	  <indexterm>
-	    <primary>NIS</primary>
-	    <secondary>master server</secondary>
-	  </indexterm>
           <listitem>
-            <para>A <emphasis>NIS master server</emphasis>.  This
+            <para>A <emphasis>NIS master server</emphasis><indexterm><primary>NIS</primary><secondary>master server</secondary></indexterm>.  This
               server, analogous to a &windowsnt; primary domain
               controller, maintains the files used by all of the NIS
               clients.  The <filename>passwd</filename>,
               <filename>group</filename>, and other various files used
               by the NIS clients live on the master server.</para>
 
             <note><para>It is possible for one machine to be an NIS
               master server for more than one NIS domain.  However,
               this will not be covered in this introduction, which
               assumes a relatively small-scale NIS
               environment.</para></note>
           </listitem>
 
           <listitem>
-	    <indexterm>
-	      <primary>NIS</primary>
-	      <secondary>slave server</secondary>
-	    </indexterm>
-
-            <para><emphasis>NIS slave servers</emphasis>.  Similar to
+            <para><emphasis>NIS slave servers</emphasis><indexterm><primary>NIS</primary><secondary>slave server</secondary></indexterm>.  Similar to
               the &windowsnt; backup domain controllers, NIS slave
               servers maintain copies of the NIS master's data files.
               NIS slave servers provide the redundancy, which is
               needed in important environments.  They also help to
               balance the load of the master server: NIS Clients
               always attach to the NIS server whose response they get
               first, and this includes slave-server-replies.</para>
           </listitem>
 
           <listitem>
-	    <indexterm>
-	      <primary>NIS</primary>
-	      <secondary>client</secondary>
-	    </indexterm>
-
-            <para><emphasis>NIS clients</emphasis>.  NIS clients, like
+            <para><emphasis>NIS clients</emphasis><indexterm><primary>NIS</primary><secondary>client</secondary></indexterm>.  NIS clients, like
               most &windowsnt; workstations, authenticate against the
               NIS server (or the &windowsnt; domain controller in the
               &windowsnt; workstations case) to log on.</para>
           </listitem>
         </itemizedlist>
       </sect3>
     </sect2>
 
     <sect2>
       <title>Using NIS/YP</title>
 
       <para>This section will deal with setting up a sample NIS
         environment.</para>
 
       <note><para>This section assumes that you are running
         FreeBSD&nbsp;3.3 or later.  The instructions given here will
         <emphasis>probably</emphasis> work for any version of FreeBSD
         greater than 3.0, but there are no guarantees that this is
         true.</para></note>
 
 
       <sect3>
         <title>Planning</title>
 
         <para>Let us assume that you are the administrator of a small
           university lab.  This lab, which consists of 15 FreeBSD
           machines, currently has no centralized point of
           administration; each machine has its own
           <filename>/etc/passwd</filename> and
           <filename>/etc/master.passwd</filename>.  These files are
           kept in sync with each other only through manual
           intervention; currently, when you add a user to the lab, you
           must run <command>adduser</command> on all 15 machines.
           Clearly, this has to change, so you have decided to convert
           the lab to use NIS, using two of the machines as
           servers.</para>
 
         <para>Therefore, the configuration of the lab now looks something
           like:</para>
 
         <informaltable frame="none" pgwide="1">
           <tgroup cols="3">
             <thead>
               <row>
                 <entry>Machine name</entry>
                 <entry>IP address</entry>
                 <entry>Machine role</entry>
               </row>
             </thead>
             <tbody>
               <row>
                 <entry><hostid>ellington</hostid></entry>
                 <entry><hostid role="ipaddr">10.0.0.2</hostid></entry>
                 <entry>NIS master</entry>
               </row>
               <row>
                 <entry><hostid>coltrane</hostid></entry>
                 <entry><hostid role="ipaddr">10.0.0.3</hostid></entry>
                 <entry>NIS slave</entry>
               </row>
               <row>
                 <entry><hostid>basie</hostid></entry>
                 <entry><hostid role="ipaddr">10.0.0.4</hostid></entry>
                 <entry>Faculty workstation</entry>
               </row>
               <row>
                 <entry><hostid>bird</hostid></entry>
                 <entry><hostid role="ipaddr">10.0.0.5</hostid></entry>
                 <entry>Client machine</entry>
               </row>
               <row>
                 <entry><hostid>cli[1-11]</hostid></entry>
                 <entry><hostid role="ipaddr">10.0.0.[6-17]</hostid></entry>
                 <entry>Other client machines</entry>
               </row>
             </tbody>
           </tgroup>
         </informaltable>
 
         <para>If you are setting up a NIS scheme for the first time, it
 	  is a good idea to think through how you want to go about it.  No
 	  matter what the size of your network, there are a few decisions
 	  that need to be made.</para>
 
         <sect4>
           <title>Choosing a NIS Domain Name</title>
 
 	  <indexterm>
 	    <primary>NIS</primary>
 	    <secondary>domainname</secondary>
 	  </indexterm>
           <para>This might not be the <quote>domainname</quote> that
 	    you are used to.  It is more accurately called the
 	    <quote>NIS domainname</quote>.  When a client broadcasts
 	    its requests for info, it includes the name of the NIS
 	    domain that it is part of.  This is how multiple servers
 	    on one network can tell which server should answer which
 	    request.  Think of the NIS domainname as the name for a
 	    group of hosts that are related in some way.</para>
 
 	  <para>Some organizations choose to use their Internet
 	    domainname for their NIS domainname.  This is not
 	    recommended as it can cause confusion when trying to debug
 	    network problems.  The NIS domainname should be unique
 	    within your network and it is helpful if it describes the
 	    group of machines it represents.  For example, the Art
 	    department at Acme Inc. might be in the
 	    <quote>acme-art</quote> NIS domain.  For this example,
 	    assume you have chosen the name
 	    <literal>test-domain</literal>.</para>
 
 	  <indexterm><primary>SunOS</primary></indexterm>
           <para>However, some operating systems (notably &sunos;) use
           their NIS domain name as their Internet domain name.  If one
           or more machines on your network have this restriction, you
           <emphasis>must</emphasis> use the Internet domain name as
           your NIS domain name.</para>
         </sect4>
 
         <sect4>
           <title>Physical Server Requirements</title>
 
 	  <para>There are several things to keep in mind when choosing
 	    a machine to use as a NIS server.  One of the unfortunate
 	    things about NIS is the level of dependency the clients
 	    have on the server.  If a client cannot contact the server
 	    for its NIS domain, very often the machine becomes
 	    unusable.  The lack of user and group information causes
 	    most systems to temporarily freeze up.  With this in mind
 	    you should make sure to choose a machine that will not be
 	    prone to being rebooted regularly, or one that might be
 	    used for development.  The NIS server should ideally be a
 	    stand alone machine whose sole purpose in life is to be an
 	    NIS server.  If you have a network that is not very
 	    heavily used, it is acceptable to put the NIS server on a
 	    machine running other services, just keep in mind that if
 	    the NIS server becomes unavailable, it will affect
 	    <emphasis>all</emphasis> of your NIS clients
 	    adversely.</para>
         </sect4>
       </sect3>
 
       <sect3>
         <title>NIS Servers</title>
 
 	<para> The canonical copies of all NIS information are stored
 	  on a single machine called the NIS master server.  The
 	  databases used to store the information are called NIS maps.
 	  In FreeBSD, these maps are stored in
 	  <filename>/var/yp/[domainname]</filename> where
 	  <filename>[domainname]</filename> is the name of the NIS
 	  domain being served.  A single NIS server can support
 	  several domains at once, therefore it is possible to have
 	  several such directories, one for each supported domain.
 	  Each domain will have its own independent set of
 	  maps.</para>
 
 	<para>NIS master and slave servers handle all NIS requests
 	  with the <command>ypserv</command> daemon.
 	  <command>ypserv</command> is responsible for receiving
 	  incoming requests from NIS clients, translating the
 	  requested domain and map name to a path to the corresponding
 	  database file and transmitting data from the database back
 	  to the client.</para>
 
         <sect4>
 	  <title>Setting Up a NIS Master Server</title>
 	  <indexterm>
 	    <primary>NIS</primary>
 	    <secondary>server configuration</secondary>
 	  </indexterm>
 	  <para>Setting up a master NIS server can be relatively
 	    straight forward, depending on your needs.  FreeBSD comes
 	    with support for NIS out-of-the-box.  All you need is to
 	    add the following lines to
 	    <filename>/etc/rc.conf</filename>, and FreeBSD will do the
 	    rest for you.</para>
 
           <procedure>
             <step>
               <para><programlisting>nisdomainname="test-domain"</programlisting>
                 This line will set the NIS domainname to
                 <literal>test-domain</literal>
                 upon network setup (e.g. after reboot).</para>
             </step>
             <step>
               <para><programlisting>nis_server_enable="YES"</programlisting>
                 This will tell FreeBSD to start up the NIS server processes
                 when the networking is next brought up.</para>
             </step>
             <step>
               <para><programlisting>nis_yppasswdd_enable="YES"</programlisting>
                 This will enable the <command>rpc.yppasswdd</command>
                 daemon which, as mentioned above, will allow users to
                 change their NIS password from a client machine.</para>
             </step>
           </procedure>
 
           <note>
             <para>Depending on your NIS setup, you may need to add
               further entries.  See the <link
               linkend="network-nis-server-is-client">section about NIS
               servers that are also NIS clients</link>, below, for
               details.</para>
           </note>
 
           <para>Now, all you have to do is to run the command
             <command>/etc/netstart</command> as superuser.  It will
             set up everything for you, using the values you defined in
             <filename>/etc/rc.conf</filename>.</para>
         </sect4>
 
         <sect4>
           <title>Initializing the NIS Maps</title>
           <indexterm>
             <primary>NIS</primary>
             <secondary>maps</secondary>
           </indexterm>
           <para>The <emphasis>NIS maps</emphasis> are database files,
             that are kept in the <filename>/var/yp</filename>
             directory.  They are generated from configuration files in
             the <filename>/etc</filename> directory of the NIS master,
             with one exception: the
             <filename>/etc/master.passwd</filename> file.  This is for
             a good reason, you do not want to propagate passwords to
             your <username>root</username> and other administrative
             accounts to all the servers in the NIS domain.  Therefore,
             before we initialize the NIS maps, you should:</para>
 
           <screen>&prompt.root; <userinput>cp /etc/master.passwd /var/yp/master.passwd</userinput>
 &prompt.root; <userinput>cd /var/yp</userinput>
 &prompt.root; <userinput>vi master.passwd</userinput></screen>
 
           <para>You should remove all entries regarding system
             accounts (<username>bin</username>,
             <username>tty</username>, <username>kmem</username>,
             <username>games</username>, etc), as well as any accounts
             that you do not want to be propagated to the NIS clients
             (for example <username>root</username> and any other UID 0
             (superuser) accounts).</para>
 
           <note><para>Make sure the
             <filename>/var/yp/master.passwd</filename> is neither group
             nor world readable (mode 600)!  Use the
             <command>chmod</command> command, if appropriate.</para></note>
 
 	  <indexterm><primary>Tru64 UNIX</primary></indexterm>
 
           <para>When you have finished, it is time to initialize the
             NIS maps!  FreeBSD includes a script named
             <command>ypinit</command> to do this for you (see its
             manual page for more information).  Note that this script
             is available on most &unix; Operating Systems, but not on
             all.  On Digital UNIX/Compaq Tru64 UNIX it is called
             <command>ypsetup</command>.  Because we are generating
             maps for an NIS master, we are going to pass the
             <option>-m</option> option to <command>ypinit</command>.
             To generate the NIS maps, assuming you already performed
             the steps above, run:</para>
 
           <screen>ellington&prompt.root; <userinput>ypinit -m test-domain</userinput>
 Server Type: MASTER Domain: test-domain
 Creating an YP server will require that you answer a few questions.
 Questions will all be asked at the beginning of the procedure.
 Do you want this procedure to quit on non-fatal errors? [y/n: n] <userinput>n</userinput>
 Ok, please remember to go back and redo manually whatever fails.
 If you don't, something might not work.
 At this point, we have to construct a list of this domains YP servers.
 rod.darktech.org is already known as master server.
 Please continue to add any slave servers, one per line. When you are
 done with the list, type a &lt;control D&gt;.
 master server   :  ellington
 next host to add:  <userinput>coltrane</userinput>
 next host to add:  <userinput>^D</userinput>
 The current list of NIS servers looks like this:
 ellington
 coltrane
 Is this correct?  [y/n: y] <userinput>y</userinput>
 
 [..output from map generation..]
 
 NIS Map update completed.
 ellington has been setup as an YP master server without any errors.</screen>
 
           <para><command>ypinit</command> should have created
             <filename>/var/yp/Makefile</filename> from
             <filename>/var/yp/Makefile.dist</filename>.
             When created, this file assumes that you are operating
             in a single server NIS environment with only FreeBSD
             machines.  Since <literal>test-domain</literal> has
             a slave server as well, you must edit
             <filename>/var/yp/Makefile</filename>:</para>
 
           <screen>ellington&prompt.root; <userinput>vi /var/yp/Makefile</userinput></screen>
 
 	  <para>You should comment out the line that says</para>
 
 	  <programlisting>NOPUSH = "True"</programlisting>
 
 	  <para>(if it is not commented out already).</para>
         </sect4>
 
         <sect4>
 	  <title>Setting up a NIS Slave Server</title>
 	  <indexterm>
 	    <primary>NIS</primary>
 	    <secondary>slave server</secondary>
 	  </indexterm>
 	  <para>Setting up an NIS slave server is even more simple than
 	    setting up the master.  Log on to the slave server and edit the
             file <filename>/etc/rc.conf</filename> as you did before.
             The only difference is that we now must use the
             <option>-s</option> option when running <command>ypinit</command>.
             The <option>-s</option> option requires the name of the NIS
             master be passed to it as well, so our command line looks
             like:</para>
 
   <screen>coltrane&prompt.root; <userinput>ypinit -s ellington test-domain</userinput>
 
 Server Type: SLAVE Domain: test-domain Master: ellington
 
 Creating an YP server will require that you answer a few questions.
 Questions will all be asked at the beginning of the procedure.
 
 Do you want this procedure to quit on non-fatal errors? [y/n: n]  <userinput>n</userinput>
 
 Ok, please remember to go back and redo manually whatever fails.
 If you don't, something might not work.
 There will be no further questions. The remainder of the procedure
 should take a few minutes, to copy the databases from ellington.
 Transferring netgroup...
 ypxfr: Exiting: Map successfully transferred
 Transferring netgroup.byuser...
 ypxfr: Exiting: Map successfully transferred
 Transferring netgroup.byhost...
 ypxfr: Exiting: Map successfully transferred
 Transferring master.passwd.byuid...
 ypxfr: Exiting: Map successfully transferred
 Transferring passwd.byuid...
 ypxfr: Exiting: Map successfully transferred
 Transferring passwd.byname...
 ypxfr: Exiting: Map successfully transferred
 Transferring group.bygid...
 ypxfr: Exiting: Map successfully transferred
 Transferring group.byname...
 ypxfr: Exiting: Map successfully transferred
 Transferring services.byname...
 ypxfr: Exiting: Map successfully transferred
 Transferring rpc.bynumber...
 ypxfr: Exiting: Map successfully transferred
 Transferring rpc.byname...
 ypxfr: Exiting: Map successfully transferred
 Transferring protocols.byname...
 ypxfr: Exiting: Map successfully transferred
 Transferring master.passwd.byname...
 ypxfr: Exiting: Map successfully transferred
 Transferring networks.byname...
 ypxfr: Exiting: Map successfully transferred
 Transferring networks.byaddr...
 ypxfr: Exiting: Map successfully transferred
 Transferring netid.byname...
 ypxfr: Exiting: Map successfully transferred
 Transferring hosts.byaddr...
 ypxfr: Exiting: Map successfully transferred
 Transferring protocols.bynumber...
 ypxfr: Exiting: Map successfully transferred
 Transferring ypservers...
 ypxfr: Exiting: Map successfully transferred
 Transferring hosts.byname...
 ypxfr: Exiting: Map successfully transferred
 
 coltrane has been setup as an YP slave server without any errors.
 Don't forget to update map ypservers on ellington.</screen>
 
 	  <para>You should now have a directory called
 	    <filename>/var/yp/test-domain</filename>.  Copies of the NIS
 	    master server's maps should be in this directory.  You will
 	    need to make sure that these stay updated.  The following
 	    <filename>/etc/crontab</filename> entries on your slave
 	    servers should do the job:</para>
 
 	  <programlisting>20      *       *       *       *       root   /usr/libexec/ypxfr passwd.byname
 21      *       *       *       *       root   /usr/libexec/ypxfr passwd.byuid</programlisting>
 
 	  <para>These two lines force the slave to sync its maps with
 	    the maps on the master server.  Although these entries are
 	    not mandatory, since the master server attempts to ensure
 	    any changes to its NIS maps are communicated to its slaves
 	    and because password information is vital to systems
 	    depending on the server, it is a good idea to force the
 	    updates.  This is more important on busy networks where map
 	    updates might not always complete.</para>
 
           <para>Now, run the command <command>/etc/netstart</command> on the
             slave server as well, which again starts the NIS server.</para>
 	</sect4>
       </sect3>
 
       <sect3>
         <title>NIS Clients</title>
 
 	<para> An NIS client establishes what is called a binding to a
 	  particular NIS server using the
 	  <command>ypbind</command> daemon.
 	  <command>ypbind</command> checks the system's default
 	  domain (as set by the <command>domainname</command> command),
 	  and begins broadcasting RPC requests on the local network.
 	  These requests specify the name of the domain for which
 	  <command>ypbind</command> is attempting to establish a binding.
 	  If a server that has been configured to serve the requested
 	  domain receives one of the broadcasts, it will respond to
 	  <command>ypbind</command>,  which will record the server's
 	  address.  If there are several servers available (a master and
 	  several slaves, for example), <command>ypbind</command> will
 	  use the address of the first one to respond.  From that point
 	  on, the client system will direct all of its NIS requests to
 	  that server.  <command>ypbind</command> will
 	  occasionally <quote>ping</quote> the server to make sure it is
 	  still up and running.  If it fails to receive a reply to one of
 	  its pings within a reasonable amount of time,
 	  <command>ypbind</command> will mark the domain as unbound and
 	  begin broadcasting again in the hopes of locating another
 	  server.</para>
 
 	<sect4>
 	  <title>Setting Up a NIS Client</title>
 	  <indexterm>
 	    <primary>NIS</primary>
 	    <secondary>client configuration</secondary>
 	  </indexterm>
 	  <para>Setting up a FreeBSD machine to be a NIS client is fairly
 	    straightforward.</para>
 
 	  <procedure>
 	    <step>
 	      <para>Edit the file <filename>/etc/rc.conf</filename> and
                 add the following lines in order to set the NIS domainname
                 and start <command>ypbind</command> upon network
                 startup:</para>
 
 	      <programlisting>nisdomainname="test-domain"
 nis_client_enable="YES"</programlisting>
 	    </step>
 
 	    <step>
 	      <para>To import all possible password entries from the NIS
 		server, remove all user accounts from your
 		<filename>/etc/master.passwd</filename> file and use
 		<command>vipw</command> to add the following line to
                 the end of the file:</para>
 
 	      <programlisting>+:::::::::</programlisting>
 
 	      <note>
 		<para>This line will afford anyone with a valid account in
 		  the NIS server's password maps an account.  There are
 		  many ways to configure your NIS client by changing this
 		  line.  See the <link linkend="network-netgroups">netgroups
 		  section</link> below for more information.
                   For more detailed reading see O'Reilly's book on
 		  <literal>Managing NFS and NIS</literal>.</para>
 	      </note>
 
               <note>
                 <para>You should keep at least one local account (i.e.
                   not imported via NIS) in your
                   <filename>/etc/master.passwd</filename> and this
                   account should also be a member of the group
                   <groupname>wheel</groupname>.  If there is something
                   wrong with NIS, this account can be used to log in
                   remotely, become <username>root</username>, and fix things.</para>
               </note>
             </step>
 
 	    <step>
 	      <para>To import all possible group entries from the NIS
 		server, add this line to your
 		<filename>/etc/group</filename> file:</para>
 
 	      <programlisting>+:*::</programlisting>
 	    </step>
 	  </procedure>
 
 	  <para>After completing these steps, you should be able to run
 	    <command>ypcat passwd</command> and see the NIS server's
 	    passwd map.</para>
 	</sect4>
       </sect3>
     </sect2>
 
     <sect2>
       <title>NIS Security</title>
 
       <para>In general, any remote user can issue an RPC to
 	&man.ypserv.8; and retrieve the contents of your NIS maps,
 	provided the remote user knows your domainname.  To prevent
 	such unauthorized transactions, &man.ypserv.8; supports a
 	feature called <quote>securenets</quote> which can be used to
 	restrict access to a given set of hosts.  At startup,
 	&man.ypserv.8; will attempt to load the securenets information
 	from a file called
 	<filename>/var/yp/securenets</filename>.</para>
 
       <note>
 	<para>This path varies depending on the path specified with the
 	  <option>-p</option> option.  This file contains entries that
 	  consist of a network specification and a network mask separated
 	  by white space.  Lines starting with <quote>#</quote> are
 	  considered to be comments.  A sample securenets file might look
 	  like this:</para>
       </note>
 
       <programlisting># allow connections from local host -- mandatory
 127.0.0.1     255.255.255.255
 # allow connections from any host
 # on the 192.168.128.0 network
 192.168.128.0 255.255.255.0
 # allow connections from any host
 # between 10.0.0.0 to 10.0.15.255
 # this includes the machines in the testlab
 10.0.0.0      255.255.240.0</programlisting>
 
       <para>If &man.ypserv.8; receives a request from an address that
 	matches one of these rules, it will process the request
 	normally.  If the address fails to match a rule, the request
 	will be ignored and a warning message will be logged.  If the
 	<filename>/var/yp/securenets</filename> file does not exist,
 	<command>ypserv</command> will allow connections from any
 	host.</para>
 
       <para>The <command>ypserv</command> program also has support for
 	Wietse Venema's <application>TCP Wrapper</application> package.
 	This allows the administrator to use the
 	<application>TCP Wrapper</application> configuration files for
 	access control instead of
 	<filename>/var/yp/securenets</filename>.</para>
 
       <note>
         <para>While both of these access control mechanisms provide some
           security, they, like the privileged port test, are
           vulnerable to <quote>IP spoofing</quote> attacks.  All
           NIS-related traffic should be blocked at your firewall.</para>
 
         <para>Servers using <filename>/var/yp/securenets</filename>
           may fail to serve legitimate NIS clients with archaic TCP/IP
           implementations.  Some of these implementations set all
           host bits to zero when doing broadcasts and/or fail to
           observe the subnet mask when calculating the broadcast
           address.  While some of these problems can be fixed by
           changing the client configuration, other problems may force
           the retirement of the client systems in question or the
           abandonment of <filename>/var/yp/securenets</filename>.</para>
 
         <para>Using <filename>/var/yp/securenets</filename> on a
           server with such an archaic implementation of TCP/IP is a
           really bad idea and will lead to loss of NIS functionality
           for large parts of your network.</para>
 
 	<indexterm><primary>TCP Wrappers</primary></indexterm>
         <para>The use of the <application>TCP Wrapper</application>
           package increases the latency of your NIS server.  The
           additional delay may be long enough to cause timeouts in
           client programs, especially in busy networks or with slow
           NIS servers.  If one or more of your client systems
           suffers from these symptoms, you should convert the client
           systems in question into NIS slave servers and force them
           to bind to themselves.</para>
       </note>
     </sect2>
 
     <sect2>
       <title>Barring Some Users from Logging On</title>
 
       <para>In our lab, there is a machine <hostid>basie</hostid> that
         is supposed to be a faculty only workstation.  We do not want
         to take this machine out of the NIS domain, yet the
         <filename>passwd</filename> file on the master NIS server
         contains accounts for both faculty and students.  What can we
         do?</para>
 
       <para>There is a way to bar specific users from logging on to a
         machine, even if they are present in the NIS database.  To do
         this, all you must do is add
         <literal>-<replaceable>username</replaceable></literal> to the
         end of the <filename>/etc/master.passwd</filename> file on the
         client machine, where <replaceable>username</replaceable> is
         the username of the user you wish to bar from logging in.
         This should preferably be done using <command>vipw</command>,
         since <command>vipw</command> will sanity check your changes
         to <filename>/etc/master.passwd</filename>, as well as
         automatically rebuild the password database when you finish
         editing.  For example, if we wanted to bar user
         <username>bill</username> from logging on to
         <hostid>basie</hostid> we would:</para>
 
         <screen>basie&prompt.root; <userinput>vipw</userinput>
 <userinput>[add -bill to the end, exit]</userinput>
 vipw: rebuilding the database...
 vipw: done
 
 basie&prompt.root; <userinput>cat /etc/master.passwd</userinput>
 
 root:[password]:0:0::0:0:The super-user:/root:/bin/csh
 toor:[password]:0:0::0:0:The other super-user:/root:/bin/sh
 daemon:*:1:1::0:0:Owner of many system processes:/root:/sbin/nologin
 operator:*:2:5::0:0:System &amp;:/:/sbin/nologin
 bin:*:3:7::0:0:Binaries Commands and Source,,,:/:/sbin/nologin
 tty:*:4:65533::0:0:Tty Sandbox:/:/sbin/nologin
 kmem:*:5:65533::0:0:KMem Sandbox:/:/sbin/nologin
 games:*:7:13::0:0:Games pseudo-user:/usr/games:/sbin/nologin
 news:*:8:8::0:0:News Subsystem:/:/sbin/nologin
 man:*:9:9::0:0:Mister Man Pages:/usr/share/man:/sbin/nologin
 bind:*:53:53::0:0:Bind Sandbox:/:/sbin/nologin
 uucp:*:66:66::0:0:UUCP pseudo-user:/var/spool/uucppublic:/usr/libexec/uucp/uucico
 xten:*:67:67::0:0:X-10 daemon:/usr/local/xten:/sbin/nologin
 pop:*:68:6::0:0:Post Office Owner:/nonexistent:/sbin/nologin
 nobody:*:65534:65534::0:0:Unprivileged user:/nonexistent:/sbin/nologin
 +:::::::::
 -bill
 
 basie&prompt.root;</screen>
     </sect2>
 
     <sect2 id="network-netgroups">
       <sect2info>
         <authorgroup>
           <author>
             <firstname>Udo</firstname>
             <surname>Erdelhoff</surname>
             <contrib>Contributed by </contrib>
           </author>
         </authorgroup>
       </sect2info>
 
       <title>Using Netgroups</title>
       <indexterm><primary>netgroups</primary></indexterm>
 
       <para>The method shown in the previous section works reasonably
         well if you need special rules for a very small number of
         users and/or machines.  On larger networks, you
         <emphasis>will</emphasis> forget to bar some users from logging
         onto sensitive machines, or you may even have to modify each
         machine separately, thus losing the main benefit of NIS:
         <emphasis>centralized</emphasis> administration.</para>
 
       <para>The NIS developers' solution for this problem is called
         <emphasis>netgroups</emphasis>.  Their purpose and semantics
         can be compared to the normal groups used by &unix; file
         systems.  The main differences are the lack of a numeric ID
         and the ability to define a netgroup by including both user
         accounts and other netgroups.</para>
 
       <para>Netgroups were developed to handle large, complex networks
         with hundreds of users and machines.  On one hand, this is
         a Good Thing if you are forced to deal with such a situation.
         On the other hand, this complexity makes it almost impossible to
         explain netgroups with really simple examples.  The example
         used in the remainder of this section demonstrates this
         problem.</para>
 
       <para>Let us assume that your successful introduction of NIS in
         your laboratory caught your superiors' interest.  Your next
         job is to extend your NIS domain to cover some of the other
         machines on campus.  The two tables contain the names of the
         new users and new machines as well as brief descriptions of
         them.</para>
 
       <informaltable frame="none" pgwide="1">
         <tgroup cols="2">
           <thead>
             <row>
               <entry>User Name(s)</entry>
               <entry>Description</entry>
             </row>
           </thead>
 
           <tbody>
             <row>
               <entry><username>alpha</username>, <username>beta</username></entry>
               <entry>Normal employees of the IT department</entry>
             </row>
 
             <row>
               <entry><username>charlie</username>, <username>delta</username></entry>
               <entry>The new apprentices of the IT department</entry>
             </row>
 
             <row>
               <entry><username>echo</username>, <username>foxtrott</username>, <username>golf</username>, ...</entry>
               <entry>Ordinary employees</entry>
             </row>
 
             <row>
               <entry><username>able</username>, <username>baker</username>, ...</entry>
               <entry>The current interns</entry>
             </row>
           </tbody>
         </tgroup>
       </informaltable>
 
       <informaltable frame="none" pgwide="1">
         <tgroup cols="2">
           <thead>
             <row>
               <entry>Machine Name(s)</entry>
               <entry>Description</entry>
             </row>
           </thead>
 
           <tbody>
             <row>
               <!--  Names taken from "Good Omens" by Neil Gaiman and Terry
                     Pratchett.  Many thanks for a brilliant book.  -->
 
               <entry><hostid>war</hostid>, <hostid>death</hostid>,
               <hostid>famine</hostid>,
               <hostid>pollution</hostid></entry>
               <entry>Your most important servers.  Only the IT
                 employees are allowed to log onto these
                 machines.</entry>
             </row>
             <row>
               <!-- gluttony was omitted because it was too fat -->
 
               <entry><hostid>pride</hostid>, <hostid>greed</hostid>,
               <hostid>envy</hostid>, <hostid>wrath</hostid>,
               <hostid>lust</hostid>, <hostid>sloth</hostid></entry>
               <entry>Less important servers.  All members of the IT
               department are allowed to login onto these
               machines.</entry>
             </row>
 
             <row>
               <entry><hostid>one</hostid>, <hostid>two</hostid>,
                 <hostid>three</hostid>, <hostid>four</hostid>,
                 ...</entry>
 
               <entry>Ordinary workstations.  Only the
                 <emphasis>real</emphasis> employees are allowed to use
                 these machines.</entry>
             </row>
 
             <row>
               <entry><hostid>trashcan</hostid></entry>
               <entry>A very old machine without any critical data.
                 Even the intern is allowed to use this box.</entry>
             </row>
           </tbody>
         </tgroup>
       </informaltable>
 
       <para>If you tried to implement these restrictions by separately
         blocking each user, you would have to add one
         <literal>-<replaceable>user</replaceable></literal> line to
         each system's <filename>passwd</filename> for each user who is
         not allowed to login onto that system.  If you forget just one
         entry, you could be in trouble.  It may be feasible to do this
         correctly during the initial setup, however you
         <emphasis>will</emphasis> eventually forget to add the lines
         for new users during day-to-day operations.  After all, Murphy
         was an optimist.</para>
 
       <para>Handling this situation with netgroups offers several
         advantages.  Each user need not be handled separately; you
         assign a user to one or more netgroups and allow or forbid
         logins for all members of the netgroup.  If you add a new
         machine, you will only have to define login restrictions for
         netgroups.  If a new user is added, you will only have to add
         the user to one or more netgroups.  Those changes are
         independent of each other: no more <quote>for each combination
         of user and machine do...</quote> If your NIS setup is planned
         carefully, you will only have to modify exactly one central
         configuration file to grant or deny access to machines.</para>
 
       <para>The first step is the initialization of the NIS map
         netgroup.  FreeBSD's &man.ypinit.8; does not create this map by
         default, but its NIS implementation will support it once it has
         been created.  To create an empty map, simply type</para>
 
       <screen>ellington&prompt.root; <userinput>vi /var/yp/netgroup</userinput></screen>
 
       <para>and start adding content.  For our example, we need at
          least four netgroups: IT employees, IT apprentices, normal
          employees and interns.</para>
 
       <programlisting>IT_EMP  (,alpha,test-domain)    (,beta,test-domain)
 IT_APP  (,charlie,test-domain)  (,delta,test-domain)
 USERS   (,echo,test-domain)     (,foxtrott,test-domain) \
         (,golf,test-domain)
 INTERNS (,able,test-domain)     (,baker,test-domain)</programlisting>
 
       <para><literal>IT_EMP</literal>, <literal>IT_APP</literal> etc.
         are the names of the netgroups.  Each bracketed group adds
         one or more user accounts to it.  The three fields inside a
         group are:</para>
 
       <orderedlist>
         <listitem>
           <para>The name of the host(s) where the following items are
             valid.  If you do not specify a hostname, the entry is
             valid on all hosts.  If you do specify a hostname, you
             will enter a realm of darkness, horror and utter confusion.</para>
         </listitem>
 
         <listitem>
           <para>The name of the account that belongs to this
             netgroup.</para>
         </listitem>
 
         <listitem>
           <para>The NIS domain for the account.  You can import
             accounts from other NIS domains into your netgroup if you
             are one of the unlucky fellows with more than one NIS
             domain.</para>
         </listitem>
       </orderedlist>
 
       <para>Each of these fields can contain wildcards.  See
         &man.netgroup.5; for details.</para>
 
       <note>
         <indexterm><primary>netgroups</primary></indexterm>
         <para>Netgroup names longer than 8 characters should not be
           used, especially if you have machines running other
           operating systems within your NIS domain.  The names are
           case sensitive; using capital letters for your netgroup
           names is an easy way to distinguish between user, machine
           and netgroup names.</para>
 
         <para>Some NIS clients (other than FreeBSD) cannot handle
           netgroups with a large number of entries.  For example, some
           older versions of &sunos; start to cause trouble if a netgroup
           contains more than 15 <emphasis>entries</emphasis>.  You can
           circumvent this limit by creating several sub-netgroups with
           15 users or less and a real netgroup that consists of the
           sub-netgroups:</para>
 
         <programlisting>BIGGRP1  (,joe1,domain)  (,joe2,domain)  (,joe3,domain) [...]
 BIGGRP2  (,joe16,domain)  (,joe17,domain) [...]
 BIGGRP3  (,joe31,domain)  (,joe32,domain)
 BIGGROUP  BIGGRP1 BIGGRP2 BIGGRP3</programlisting>
 
         <para>You can repeat this process if you need more than 225
           users within a single netgroup.</para>
       </note>
 
       <para>Activating and distributing your new NIS map is
         easy:</para>
 
       <screen>ellington&prompt.root; <userinput>cd /var/yp</userinput>
 ellington&prompt.root; <userinput>make</userinput></screen>
 
       <para>This will generate the three NIS maps
         <filename>netgroup</filename>,
         <filename>netgroup.byhost</filename> and
         <filename>netgroup.byuser</filename>.  Use &man.ypcat.1; to
         check if your new NIS maps are available:</para>
 
       <screen>ellington&prompt.user; <userinput>ypcat -k netgroup</userinput>
 ellington&prompt.user; <userinput>ypcat -k netgroup.byhost</userinput>
 ellington&prompt.user; <userinput>ypcat -k netgroup.byuser</userinput></screen>
 
       <para>The output of the first command should resemble the
         contents of <filename>/var/yp/netgroup</filename>.  The second
         command will not produce output if you have not specified
         host-specific netgroups.  The third command can be used to
         get the list of netgroups for a user.</para>
 
       <para>The client setup is quite simple.  To configure the server
         <hostid>war</hostid>, you only have to start
         &man.vipw.8; and replace the line</para>
 
       <programlisting>+:::::::::</programlisting>
 
       <para>with</para>
 
       <programlisting>+@IT_EMP:::::::::</programlisting>
 
       <para>Now, only the data for the users defined in the netgroup
         <literal>IT_EMP</literal> is imported into
         <hostid>war</hostid>'s password database and only
         these users are allowed to login.</para>
 
       <para>Unfortunately, this limitation also applies to the
 	<literal>~</literal> function of the shell and all routines
 	converting between user names and numerical user IDs.  In
 	other words, <command>cd
 	~<replaceable>user</replaceable></command> will not work,
 	<command>ls -l</command> will show the numerical ID instead of
 	the username and <command>find . -user joe -print</command>
 	will fail with <errorname>No such user</errorname>.  To fix
 	this, you will have to import all user entries
 	<emphasis>without allowing them to login onto your
 	servers</emphasis>.</para>
 
       <para>This can be achieved by adding another line to
         <filename>/etc/master.passwd</filename>.  This line should
         contain:</para>
 
       <para><literal>+:::::::::/sbin/nologin</literal>, meaning
         <quote>Import all entries but replace the shell with
         <filename>/sbin/nologin</filename> in the imported
         entries</quote>.  You can replace any field in the
         <literal>passwd</literal> entry by placing a default value in
         your <filename>/etc/master.passwd</filename>.</para>
 
       <!-- Been there, done that, got the scars to prove it - ue -->
       <warning>
         <para>Make sure that the line
         <literal>+:::::::::/sbin/nologin</literal> is placed after
         <literal>+@IT_EMP:::::::::</literal>.  Otherwise, all user
         accounts imported from NIS will have <filename>/sbin/nologin</filename> as their
         login shell.</para>
       </warning>
 
       <para>After this change, you will only have to change one NIS
         map if a new employee joins the IT department.  You could use
         a similar approach for the less important servers by replacing
         the old <literal>+:::::::::</literal> in their local version
         of <filename>/etc/master.passwd</filename> with something like
         this:</para>
 
       <programlisting>+@IT_EMP:::::::::
 +@IT_APP:::::::::
 +:::::::::/sbin/nologin</programlisting>
 
       <para>The corresponding lines for the normal workstations
         could be:</para>
 
       <programlisting>+@IT_EMP:::::::::
 +@USERS:::::::::
 +:::::::::/sbin/nologin</programlisting>
 
       <para>And everything would be fine until there is a policy
         change a few weeks later: The IT department starts hiring
         interns.  The IT interns are allowed to use the normal
         workstations and the less important servers; and the IT
         apprentices are allowed to login onto the main servers.  You
         add a new netgroup <literal>IT_INTERN</literal>, add the new
         IT interns to this netgroup and start to change the
         configuration on each and every machine...  As the old saying
         goes: <quote>Errors in centralized planning lead to global
         mess</quote>.</para>
 
       <para>NIS' ability to create netgroups from other netgroups can
         be used to prevent situations like these.  One possibility
         is the creation of role-based netgroups.  For example, you
         could create a netgroup called
         <literal>BIGSRV</literal> to define the login
         restrictions for the important servers, another netgroup
         called <literal>SMALLSRV</literal> for the less
         important servers and a third netgroup called
         <literal>USERBOX</literal> for the normal
         workstations.  Each of these netgroups contains the netgroups
         that are allowed to login onto these machines.  The new
         entries for your NIS map netgroup should look like this:</para>
 
       <programlisting>BIGSRV    IT_EMP  IT_APP
 SMALLSRV  IT_EMP  IT_APP  ITINTERN
 USERBOX   IT_EMP  ITINTERN USERS</programlisting>
 
       <para>This method of defining login restrictions works
         reasonably well if you can define groups of machines with
         identical restrictions.  Unfortunately, this is the exception
         and not the rule.  Most of the time, you will need the ability
         to define login restrictions on a per-machine basis.</para>
 
       <para>Machine-specific netgroup definitions are the other
         possibility to deal with the policy change outlined above.  In
         this scenario, the <filename>/etc/master.passwd</filename> of
         each box contains two lines starting with <quote>+</quote>.
         The first of them adds a netgroup with the accounts allowed to
         login onto this machine, the second one adds all other
         accounts with <filename>/sbin/nologin</filename> as shell.  It
         is a good idea to use the <quote>ALL-CAPS</quote> version of
         the machine name as the name of the netgroup.  In other words,
         the lines should look like this:</para>
 
       <programlisting>+@<replaceable>BOXNAME</replaceable>:::::::::
 +:::::::::/sbin/nologin</programlisting>
 
       <para>Once you have completed this task for all your machines,
         you will not have to modify the local versions of
         <filename>/etc/master.passwd</filename> ever again.  All
         further changes can be handled by modifying the NIS map.  Here
         is an example of a possible netgroup map for this
         scenario with some additional goodies:</para>
 
       <programlisting># Define groups of users first
 IT_EMP    (,alpha,test-domain)    (,beta,test-domain)
 IT_APP    (,charlie,test-domain)  (,delta,test-domain)
 DEPT1     (,echo,test-domain)     (,foxtrott,test-domain)
 DEPT2     (,golf,test-domain)     (,hotel,test-domain)
 DEPT3     (,india,test-domain)    (,juliet,test-domain)
 ITINTERN  (,kilo,test-domain)     (,lima,test-domain)
 D_INTERNS (,able,test-domain)     (,baker,test-domain)
 #
 # Now, define some groups based on roles
 USERS     DEPT1   DEPT2     DEPT3
 BIGSRV    IT_EMP  IT_APP
 SMALLSRV  IT_EMP  IT_APP    ITINTERN
 USERBOX   IT_EMP  ITINTERN  USERS
 #
 # And a groups for a special tasks
 # Allow echo and golf to access our anti-virus-machine
 SECURITY  IT_EMP  (,echo,test-domain)  (,golf,test-domain)
 #
 # machine-based netgroups
 # Our main servers
 WAR       BIGSRV
 FAMINE    BIGSRV
 # User india needs access to this server
 POLLUTION  BIGSRV  (,india,test-domain)
 #
 # This one is really important and needs more access restrictions
 DEATH     IT_EMP
 #
 # The anti-virus-machine mentioned above
 ONE       SECURITY
 #
 # Restrict a machine to a single user
 TWO       (,hotel,test-domain)
 # [...more groups to follow]</programlisting>
 
       <para>If you are using some kind of database to manage your user
         accounts, you should be able to create the first part of the
         map with your database's report tools.  This way, new users
         will automatically have access to the boxes.</para>
 
       <para>One last word of caution: It may not always be advisable
         to use machine-based netgroups.  If you are deploying a couple of
         dozen or even hundreds of identical machines for student labs,
         you should use role-based netgroups instead of machine-based
         netgroups to keep the size of the NIS map within reasonable
         limits.</para>
     </sect2>
 
     <sect2>
       <title>Important Things to Remember</title>
 
       <para>There are still a couple of things that you will need to do
         differently now that you are in an NIS environment.</para>
 
       <itemizedlist>
         <listitem>
           <para>Every time you wish to add a user to the lab, you
             must add it to the master NIS server <emphasis>only</emphasis>,
             and <emphasis>you must remember to rebuild the NIS
             maps</emphasis>.  If you forget to do this, the new user will
             not be able to login anywhere except on the NIS master.
             For example, if we needed to add a new user
             <username>jsmith</username> to the lab, we would:</para>
 
           <screen>&prompt.root; <userinput>pw useradd jsmith</userinput>
 &prompt.root; <userinput>cd /var/yp</userinput>
 &prompt.root; <userinput>make test-domain</userinput></screen>
 
           <para>You could also run <command>adduser jsmith</command> instead
             of <command>pw useradd jsmith</command>.</para>
         </listitem>
         <listitem>
           <para><emphasis>Keep the administration accounts out of the
             NIS maps</emphasis>.  You do not want to be propagating
             administrative accounts and passwords to machines that
             will have users that should not have access to those
             accounts.</para>
         </listitem>
         <listitem>
           <para><emphasis>Keep the NIS master and slave secure, and
             minimize their downtime</emphasis>.  If somebody either
             hacks or simply turns off these machines, they have
             effectively rendered many people without the ability to
             login to the lab.</para>
 
           <para>This is the chief weakness of any centralized administration
             system.  If you do
             not protect your NIS servers, you will have a lot of angry
             users!</para>
         </listitem>
       </itemizedlist>
     </sect2>
 
     <sect2>
       <title>NIS v1 Compatibility</title>
 
       <para> FreeBSD's <application>ypserv</application> has some
 	support for serving NIS v1 clients.  FreeBSD's NIS
 	implementation only uses the NIS v2 protocol, however other
 	implementations include support for the v1 protocol for
 	backwards compatibility with older systems.  The
 	<application>ypbind</application> daemons supplied with these
 	systems will try to establish a binding to an NIS v1 server
 	even though they may never actually need it (and they may
 	persist in broadcasting in search of one even after they
 	receive a response from a v2 server).  Note that while support
 	for normal client calls is provided, this version of
 	<application>ypserv</application> does not handle v1 map
 	transfer requests; consequently, it cannot be used as a master
 	or slave in conjunction with older NIS servers that only
 	support the v1 protocol.  Fortunately, there probably are not
 	any such servers still in use today.</para>
     </sect2>
 
     <sect2 id="network-nis-server-is-client">
       <title>NIS Servers That Are Also NIS Clients</title>
 
       <para> Care must be taken when running
 	<application>ypserv</application> in a multi-server domain
 	where the server machines are also NIS clients.  It is
 	generally a good idea to force the servers to bind to
 	themselves rather than allowing them to broadcast bind
 	requests and possibly become bound to each other.  Strange
 	failure modes can result if one server goes down and others
 	are dependent upon it.  Eventually all the clients will time
 	out and attempt to bind to other servers, but the delay
 	involved can be considerable and the failure mode is still
 	present since the servers might bind to each other all over
 	again.</para>
 
       <para>You can force a host to bind to a particular server by running
 	<command>ypbind</command> with the <option>-S</option>
 	flag.  If you do not want to do this manually each time you
         reboot your NIS server, you can add the following lines to
         your <filename>/etc/rc.conf</filename>:</para>
 
       <programlisting>nis_client_enable="YES"	# run client stuff as well
 nis_client_flags="-S <replaceable>NIS domain</replaceable>,<replaceable>server</replaceable>"</programlisting>
 
       <para>See &man.ypbind.8; for further information.</para>
     </sect2>
 
     <sect2>
       <title>Password Formats</title>
       <indexterm>
         <primary>NIS</primary>
 	<secondary>password formats</secondary>
       </indexterm>
       <para>One of the most common issues that people run into when trying
 	to implement NIS is password format compatibility.  If your NIS
 	server is using DES encrypted passwords, it will only support
 	clients that are also using DES.  For example, if you have
 	&solaris; NIS clients in your network, then you will almost certainly
 	need to use DES encrypted passwords.</para>
 
       <para>To check which format your servers
 	and clients are using, look at <filename>/etc/login.conf</filename>.
 	If the host is configured to use DES encrypted passwords, then the
 	<literal>default</literal> class will contain an entry like this:</para>
 
       <programlisting>default:\
 	:passwd_format=des:\
 	:copyright=/etc/COPYRIGHT:\
 	[Further entries elided]</programlisting>
 
       <para>Other possible values for the <literal>passwd_format</literal>
 	capability include <literal>blf</literal> and <literal>md5</literal>
 	(for Blowfish and MD5 encrypted passwords, respectively).</para>
 
       <para>If you have made changes to
 	<filename>/etc/login.conf</filename>, you will also need to
 	rebuild the login capability database, which is achieved by
 	running the following command as
 	<username>root</username>:</para>
 
       <screen>&prompt.root; <userinput>cap_mkdb /etc/login.conf</userinput></screen>
 
       <note><para>The format of passwords already in
 	<filename>/etc/master.passwd</filename> will not be updated
 	until a user changes his password for the first time
 	<emphasis>after</emphasis> the login capability database is
 	rebuilt.</para></note>
 
       <para>Next, in order to ensure that passwords are encrypted with
 	the format that you have chosen, you should also check that
 	the <literal>crypt_default</literal> in
 	<filename>/etc/auth.conf</filename> gives precedence to your
 	chosen password format.  To do this, place the format that you
 	have chosen first in the list.  For example, when using DES
 	encrypted passwords, the entry would be:</para>
 
       <programlisting>crypt_default	=	des blf md5</programlisting>
 
       <para>Having followed the above steps on each of the &os; based
 	NIS servers and clients, you can be sure that they all agree
 	on which password format is used within your network.  If you
 	have trouble authenticating on an NIS client, this is a pretty
 	good place to start looking for possible problems.  Remember:
 	if you want to deploy an NIS server for a heterogenous
 	network, you will probably have to use DES on all systems
 	because it is the lowest common standard.</para>
     </sect2>
   </sect1>
 
   <sect1 id="network-dhcp">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Greg</firstname>
       	  <surname>Sutter</surname>
 	  <contrib>Written by </contrib>
         </author>
       </authorgroup>
     </sect1info>
     <title>Automatic Network Configuration (DHCP)</title>
 
     <sect2>
       <title>What Is DHCP?</title>
       <indexterm>
         <primary>Dynamic Host Configuration Protocol</primary>
         <see>DHCP</see>
       </indexterm>
       <indexterm>
         <primary>Internet Software Consortium (ISC)</primary>
       </indexterm>
 
       <para>DHCP, the Dynamic Host Configuration Protocol, describes
         the means by which a system can connect to a network and obtain the
         necessary information for communication upon that network.  FreeBSD
 	versions prior to 6.0 use the ISC (Internet Software
 	Consortium) DHCP client (&man.dhclient.8;) implementation.
 	Later versions use the OpenBSD <command>dhclient</command>
 	taken from OpenBSD&nbsp;3.7.  All
 	information here regarding <command>dhclient</command> is for
 	use with either of the ISC or OpenBSD DHCP clients. The DHCP
 	server is the one included in the ISC distribution.</para>
     </sect2>
 
     <sect2>
       <title>What This Section Covers</title>
 
       <para>This section describes both the client-side components of the ISC and OpenBSD DHCP client and
         server-side components of the ISC DHCP system.  The
         client-side program, <command>dhclient</command>, comes
         integrated within FreeBSD, and the server-side portion is
         available from the <filename
         role="package">net/isc-dhcp3-server</filename> port.  The
         &man.dhclient.8;, &man.dhcp-options.5;, and
         &man.dhclient.conf.5; manual pages, in addition to the
         references below, are useful resources.</para>
     </sect2>
 
     <sect2>
       <title>How It Works</title>
       <indexterm><primary>UDP</primary></indexterm>
       <para>When <command>dhclient</command>, the DHCP client, is
 	executed on the client machine, it begins broadcasting
 	requests for configuration information.  By default, these
 	requests are on UDP port 68.  The server replies on UDP 67,
 	giving the client an IP address and other relevant network
 	information such as netmask, router, and DNS servers.  All of
 	this information comes in the form of a DHCP
 	<quote>lease</quote> and is only valid for a certain time
 	(configured by the DHCP server maintainer).  In this manner,
 	stale IP addresses for clients no longer connected to the
 	network can be automatically reclaimed.</para>
 
       <para>DHCP clients can obtain a great deal of information from
         the server.  An exhaustive list may be found in
         &man.dhcp-options.5;.</para>
     </sect2>
 
     <sect2>
       <title>FreeBSD Integration</title>
 
       <para>&os; fully integrates the ISC or OpenBSD DHCP client,
         <command>dhclient</command> (according to the &os; version you run).  DHCP client support is provided
         within both the installer and the base system, obviating the need
         for detailed knowledge of network configurations on any network
         that runs a DHCP server.  <command>dhclient</command> has been
         included in all FreeBSD distributions since 3.2.</para>
         <indexterm>
           <primary><application>sysinstall</application></primary>
         </indexterm>
 
         <para>DHCP is supported by
           <application>sysinstall</application>.  When configuring a
           network interface within
           <application>sysinstall</application>, the second question
           asked is: <quote>Do you want to try DHCP configuration of
           the interface?</quote>. Answering affirmatively will
           execute <command>dhclient</command>, and if successful, will
           fill in the network configuration information
           automatically.</para>
 
         <para>There are two things you must do to have your system use
 	  DHCP upon startup:</para>
         <indexterm>
           <primary>DHCP</primary>
           <secondary>requirements</secondary>
         </indexterm>
 	<itemizedlist>
 	  <listitem>
             <para>Make sure that the <devicename>bpf</devicename>
 	      device is compiled into your kernel.  To do this, add
 	      <literal>device bpf</literal> (<literal>pseudo-device
 	      bpf</literal> under &os;&nbsp;4.X) to your kernel
 	      configuration file, and rebuild the kernel.  For more
 	      information about building kernels, see <xref
 	      linkend="kernelconfig"/>.</para> <para>The
 	      <devicename>bpf</devicename> device is already part of
 	      the <filename>GENERIC</filename> kernel that is supplied
 	      with FreeBSD, so if you do not have a custom kernel, you
 	      should not need to create one in order to get DHCP
 	      working.</para>
 	    <note>
 	      <para>For those who are particularly security conscious,
 	        you should be warned that <devicename>bpf</devicename>
 		is also the device that allows packet sniffers to work
 		correctly (although they still have to be run as
 		<username>root</username>).  <devicename>bpf</devicename>
 		<emphasis>is</emphasis> required to use DHCP, but if
 		you are very sensitive about security, you probably
 		should not add <devicename>bpf</devicename> to your
 		kernel in the expectation that at some point in the
 		future you will be using DHCP.</para>
 	    </note>
 	  </listitem>
           <listitem>
             <para>Edit your <filename>/etc/rc.conf</filename> to
 	      include the following:</para>
 
             <programlisting>ifconfig_fxp0="DHCP"</programlisting>
 
             <note>
               <para>Be sure to replace <literal>fxp0</literal> with the
                 designation for the interface that you wish to dynamically
                  configure, as described in
 		 <xref linkend="config-network-setup"/>.</para>
             </note>
 
             <para>If you are using a different location for
               <command>dhclient</command>, or if you wish to pass additional
               flags to <command>dhclient</command>, also include the
               following (editing as necessary):</para>
 
             <programlisting>dhcp_program="/sbin/dhclient"
 dhcp_flags=""</programlisting>
           </listitem>
         </itemizedlist>
 
         <indexterm>
           <primary>DHCP</primary>
           <secondary>server</secondary>
         </indexterm>
         <para>The DHCP server, <application>dhcpd</application>, is included
           as part of the <filename
           role="package">net/isc-dhcp3-server</filename> port in the ports
           collection.  This port contains the ISC DHCP server and
           documentation.</para>
     </sect2>
 
     <sect2>
       <title>Files</title>
       <indexterm>
         <primary>DHCP</primary>
         <secondary>configuration files</secondary>
       </indexterm>
       <itemizedlist>
         <listitem><para><filename>/etc/dhclient.conf</filename></para>
           <para><command>dhclient</command> requires a configuration file,
             <filename>/etc/dhclient.conf</filename>.  Typically the file
             contains only comments, the defaults being reasonably sane.  This
             configuration file is described by the &man.dhclient.conf.5;
             manual page.</para>
         </listitem>
 
         <listitem><para><filename>/sbin/dhclient</filename></para>
           <para><command>dhclient</command> is statically linked and
             resides in <filename>/sbin</filename>.  The &man.dhclient.8;
             manual page gives more information about
             <command>dhclient</command>.</para>
         </listitem>
 
         <listitem><para><filename>/sbin/dhclient-script</filename></para>
           <para><command>dhclient-script</command> is the FreeBSD-specific
             DHCP client configuration script.  It is described in
             &man.dhclient-script.8;, but should not need any user
             modification to function properly.</para>
         </listitem>
 
         <listitem><para><filename>/var/db/dhclient.leases</filename></para>
           <para>The DHCP client keeps a database of valid leases in this
             file, which is written as a log.  &man.dhclient.leases.5;
             gives a slightly longer description.</para>
         </listitem>
       </itemizedlist>
     </sect2>
 
     <sect2>
       <title>Further Reading</title>
 
       <para>The DHCP protocol is fully described in
         <ulink url="http://www.freesoft.org/CIE/RFC/2131/">RFC 2131</ulink>.
         An informational resource has also been set up at
         <ulink url="http://www.dhcp.org/"></ulink>.</para>
     </sect2>
 
     <sect2 id="network-dhcp-server">
 	<title>Installing and Configuring a DHCP Server</title>
 
 	<sect3>
 	  <title>What This Section Covers</title>
 
 	  <para>This section provides information on how to configure
 	    a FreeBSD system to act as a DHCP server using the ISC
 	    (Internet Software Consortium) implementation of the DHCP
 	    suite.</para>
 
 	  <para>The server portion of the suite is not provided as part of
 	    FreeBSD, and so you will need to install the
 	    <filename role="package">net/isc-dhcp3-server</filename>
 	    port to provide this service.  See <xref linkend="ports"/> for
 	    more information on using the Ports Collection.</para>
 	</sect3>
 
 	<sect3>
 	  <title>DHCP Server Installation</title>
 	  <indexterm>
 	    <primary>DHCP</primary>
 	    <secondary>installation</secondary>
 	  </indexterm>
 	  <para>In order to configure your FreeBSD system as a DHCP
 	    server, you will need to ensure that the &man.bpf.4;
 	    device is compiled into your kernel.  To do this, add
 	    <literal>device bpf</literal> (<literal>pseudo-device
 	    bpf</literal> under &os;&nbsp;4.X) to your kernel
 	    configuration file, and rebuild the kernel.  For more
 	    information about building kernels, see <xref
 	    linkend="kernelconfig"/>.</para>
 
 	  <para>The <devicename>bpf</devicename> device is already
 	    part of the <filename>GENERIC</filename> kernel that is
 	    supplied with FreeBSD, so you do not need to create a custom
 	    kernel in order to get DHCP working.</para>
 
 	    <note>
 	      <para>Those who are particularly security conscious
 	        should note that <devicename>bpf</devicename>
 		is also the device that allows packet sniffers to work
 		correctly (although such programs still need privileged
 		access).  <devicename>bpf</devicename>
 		<emphasis>is</emphasis> required to use DHCP, but if
 		you are very sensitive about security, you probably
 		should not include <devicename>bpf</devicename> in your
 		kernel purely because you expect to use DHCP at some
 		point in the future.</para>
 	    </note>
 
 	  <para>The next thing that you will need to do is edit the sample
 	    <filename>dhcpd.conf</filename> which was installed by the
 	    <filename role="package">net/isc-dhcp3-server</filename> port.
 	    By default, this will be
 	    <filename>/usr/local/etc/dhcpd.conf.sample</filename>, and you
 	    should copy this to
 	    <filename>/usr/local/etc/dhcpd.conf</filename> before proceeding
 	    to make changes.</para>
 	</sect3>
 
 	<sect3>
 	  <title>Configuring the DHCP Server</title>
 	  <indexterm>
 	    <primary>DHCP</primary>
 	    <secondary>dhcpd.conf</secondary>
 	  </indexterm>
 	  <para><filename>dhcpd.conf</filename> is
 	    comprised of declarations regarding subnets and hosts, and is
 	    perhaps most easily explained using an example :</para>
 
 	  <programlisting>option domain-name "example.com";<co id="domain-name"/>
 option domain-name-servers 192.168.4.100;<co id="domain-name-servers"/>
 option subnet-mask 255.255.255.0;<co id="subnet-mask"/>
 
 default-lease-time 3600;<co id="default-lease-time"/>
 max-lease-time 86400;<co id="max-lease-time"/>
 ddns-update-style none;<co id="ddns-update-style"/>
 
 subnet 192.168.4.0 netmask 255.255.255.0 {
   range 192.168.4.129 192.168.4.254;<co id="range"/>
   option routers 192.168.4.1;<co id="routers"/>
 }
 
 host mailhost {
   hardware ethernet 02:03:04:05:06:07;<co id="hardware"/>
   fixed-address mailhost.example.com;<co id="fixed-address"/>
 }</programlisting>
 
 	  <calloutlist>
 	    <callout arearefs="domain-name">
 	      <para>This option specifies the domain that will be provided
 		to clients as the default search domain.  See
 		&man.resolv.conf.5; for more information on what this
 		means.</para>
 	    </callout>
 
 	    <callout arearefs="domain-name-servers">
 	      <para>This option specifies a comma separated list of DNS
 		servers that the client should use.</para>
 	    </callout>
 
 	    <callout arearefs="subnet-mask">
 	      <para>The netmask that will be provided to clients.</para>
 	    </callout>
 
 	    <callout arearefs="default-lease-time">
 	      <para>A client may request a specific length of time that a
 		lease will be valid.  Otherwise the server will assign
 		a lease with this expiry value (in seconds).</para>
 	    </callout>
 
 	    <callout arearefs="max-lease-time">
 	      <para>This is the maximum length of time that the server will
 		lease for.  Should a client request a longer lease, a lease
 		will be issued, although it will only be valid for
 		<literal>max-lease-time</literal> seconds.</para>
 	    </callout>
 
 	    <callout arearefs="ddns-update-style">
 	      <para>This option specifies whether the DHCP server should
 		attempt to update DNS when a lease is accepted or released.
 		In the ISC implementation, this option is
 		<emphasis>required</emphasis>.</para>
 	    </callout>
 
 	    <callout arearefs="range">
 	      <para>This denotes which IP addresses should be used in
 		the pool reserved for allocating to clients.  IP
 		addresses between, and including, the ones stated are
 		handed out to clients.</para>
 	    </callout>
 
 	    <callout arearefs="routers">
 	      <para>Declares the default gateway that will be provided to
 		clients.</para>
 	    </callout>
 
 	    <callout arearefs="hardware">
 	      <para>The hardware MAC address of a host (so that the DHCP server
 		can recognize a host when it makes a request).</para>
 	    </callout>
 
 	    <callout arearefs="fixed-address">
 	      <para>Specifies that the host should always be given the
 		same IP address.  Note that using a hostname is
 		correct here, since the DHCP server will resolve the
 		hostname itself before returning the lease
 		information.</para>
 	    </callout>
 	  </calloutlist>
 
 	  <para>Once you have finished writing your
 	    <filename>dhcpd.conf</filename>, you can proceed to start the
 	    server by issuing the following command:</para>
 
 	  <screen>&prompt.root; <userinput>/usr/local/etc/rc.d/isc-dhcpd.sh start</userinput></screen>
 
 	  <para>Should you need to make changes to the configuration of your
 	    server in the future, it is important to note that sending a
 	    <literal>SIGHUP</literal> signal to
 	    <application>dhcpd</application> does <emphasis>not</emphasis>
 	    result in the configuration being reloaded, as it does with most
 	    daemons.  You will need to send a <literal>SIGTERM</literal>
 	    signal to stop the process, and then restart it using the command
 	    above.</para>
 	</sect3>
 
 	<sect3>
 	  <title>Files</title>
 	  <indexterm>
 	    <primary>DHCP</primary>
 	    <secondary>configuration files</secondary>
 	  </indexterm>
 	  <itemizedlist>
 	    <listitem><para><filename>/usr/local/sbin/dhcpd</filename></para>
 	      <para><application>dhcpd</application> is statically linked and
 		resides in <filename>/usr/local/sbin</filename>.  The
 		&man.dhcpd.8; manual page installed with the
 		port gives more information about
 		<application>dhcpd</application>.</para>
 	    </listitem>
 
 	    <listitem><para><filename>/usr/local/etc/dhcpd.conf</filename></para>
 	      <para><application>dhcpd</application> requires a configuration
 		file, <filename>/usr/local/etc/dhcpd.conf</filename> before it
 		will start providing service to clients.  This file needs to
 		contain all the information that should be provided to clients
 		that are being serviced, along with information regarding the
 		operation of the server.  This configuration file is described
 		by the &man.dhcpd.conf.5; manual page installed
 		by the port.</para>
 	    </listitem>
 
 	    <listitem><para><filename>/var/db/dhcpd.leases</filename></para>
 	      <para>The DHCP server keeps a database of leases it has issued
 		in this file, which is written as a log.  The manual page
 		&man.dhcpd.leases.5;, installed by the port
 		gives a slightly longer description.</para>
 	    </listitem>
 
 	    <listitem><para><filename>/usr/local/sbin/dhcrelay</filename></para>
 	      <para><application>dhcrelay</application> is used in advanced
 		environments where one DHCP server forwards a request from a
 		client to another DHCP server on a separate network.  If you
 		require this functionality, then install the <filename
 		role="package">net/isc-dhcp3-relay</filename> port.  The
 		&man.dhcrelay.8; manual page provided with the
 		port contains more detail.</para>
 	    </listitem>
 	  </itemizedlist>
 	</sect3>
 
       </sect2>
 
   </sect1>
 
   <sect1 id="network-dns">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Chern</firstname>
           <surname>Lee</surname>
           <contrib>Contributed by </contrib>
         </author>
       </authorgroup>
     </sect1info>
     <title>Domain Name System (DNS)</title>
 
     <sect2>
       <title>Overview</title>
       <indexterm><primary>BIND</primary></indexterm>
 
       <para>FreeBSD utilizes, by default, a version of BIND (Berkeley
         Internet Name Domain), which is the most common implementation
         of the DNS protocol.  DNS is the protocol through which names
         are mapped to IP addresses, and vice versa.  For example, a
         query for <hostid role="fqdn">www.FreeBSD.org</hostid> will
         receive a reply with the IP address of The FreeBSD Project's
         web server, whereas, a query for <hostid
         role="fqdn">ftp.FreeBSD.org</hostid> will return the IP
         address of the corresponding FTP machine.  Likewise, the
         opposite can happen.  A query for an IP address can resolve
         its hostname.  It is not necessary to run a name server to
         perform DNS lookups on a system.
       </para>
 
       <indexterm><primary>DNS</primary></indexterm>
       <para>DNS is coordinated across the Internet through a somewhat
         complex system of authoritative root name servers, and other
         smaller-scale name servers who host and cache individual domain
         information.
       </para>
 
       <para>
         This document refers to BIND 8.x, as it is the stable version
 	used in &os;.  Versions of &os;&nbsp;5.3 and beyond include
 	<acronym>BIND</acronym>9 and the configuration instructions
 	may be found later in this chapter.  Users of &os;&nbsp;5.2
 	and other previous versions may install <acronym>BIND</acronym>9
 	from the <filename role="package">net/bind9</filename> port.</para>
 
       <para>
         RFC1034 and RFC1035 dictate the DNS protocol.
       </para>
 
       <para>
         Currently, BIND is maintained by the
         Internet Software Consortium <ulink url="http://www.isc.org/"></ulink>.
       </para>
     </sect2>
 
     <sect2>
       <title>Terminology</title>
 
       <para>To understand this document, some terms related to DNS must be
 	understood.</para>
 
       <indexterm><primary>resolver</primary></indexterm>
       <indexterm><primary>reverse DNS</primary></indexterm>
       <indexterm><primary>root zone</primary></indexterm>
       <informaltable frame="none" pgwide="1">
 	<tgroup cols="2">
 	  <colspec colwidth="1*"/>
 	  <colspec colwidth="3*"/>
 
 	  <thead>
 	    <row>
 	      <entry>Term</entry>
 	      <entry>Definition</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry>Forward DNS</entry>
 	      <entry>Mapping of hostnames to IP addresses</entry>
 	    </row>
 
 	    <row>
 	      <entry>Origin</entry>
 	      <entry>Refers to the domain covered in a particular zone
 		file</entry>
 	    </row>
 
 	    <row>
 	      <entry><application>named</application>, BIND, name server</entry>
 	      <entry>Common names for the BIND name server package within
 		FreeBSD</entry>
 	    </row>
 
 	    <row>
 	      <entry>Resolver</entry>
 	      <entry>A system process through which a
 		machine queries a name server for zone information</entry>
 	    </row>
 
 	    <row>
 	      <entry>Reverse DNS</entry>
 	      <entry>The opposite of forward DNS; mapping of IP addresses to
 		hostnames</entry>
 	    </row>
 
 	    <row>
 	      <entry>Root zone</entry>
 
 	      <entry>The beginning of the Internet zone hierarchy.
 		All zones fall under the root zone, similar to how
 		all files in a file system fall under the root directory.</entry>
 	    </row>
 
 	    <row>
 	      <entry>Zone</entry>
 	      <entry>An individual domain, subdomain, or portion of the DNS administered by
 		the same authority</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
 
       <indexterm>
 	<primary>zones</primary>
 	<secondary>examples</secondary>
       </indexterm>
 
       <para>Examples of zones:
       </para>
       <itemizedlist>
         <listitem>
           <para><hostid>.</hostid> is the root zone</para>
         </listitem>
         <listitem>
           <para><hostid>org.</hostid> is a zone under the root zone</para>
         </listitem>
         <listitem>
           <para><hostid role="domainname">example.org.</hostid> is a
           zone under the <hostid>org.</hostid> zone</para>
         </listitem>
         <listitem>
           <para><hostid role="domainname">foo.example.org.</hostid> is
             a subdomain, a zone under the <hostid
             role="domainname">example.org.</hostid> zone</para>
         </listitem>
         <listitem>
           <para>
             <hostid>1.2.3.in-addr.arpa</hostid> is a zone referencing
 	    all IP addresses which fall under the <hostid
 	    role="ipaddr">3.2.1.*</hostid> IP space.
           </para>
         </listitem>
       </itemizedlist>
 
       <para>As one can see, the more specific part of a hostname
         appears to its left.  For example, <hostid
         role="domainname">example.org.</hostid> is more specific than
         <hostid>org.</hostid>, as <hostid>org.</hostid> is more
         specific than the root zone.  The layout of each part of a
         hostname is much like a file system: the
         <filename>/dev</filename> directory falls within the root, and
         so on.</para>
 
 
     </sect2>
 
     <sect2>
       <title>Reasons to Run a Name Server</title>
 
       <para>Name servers usually come in two forms: an authoritative
 	name server, and a caching name server.</para>
 
       <para>An authoritative name server is needed when:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>one wants to serve DNS information to the
 	    world, replying authoritatively to queries.</para>
 	</listitem>
 	<listitem>
 	  <para>a domain, such as <hostid role="domainname">example.org</hostid>, is
 	    registered and IP addresses need to be assigned to hostnames
 	    under it.</para>
 	</listitem>
 	<listitem>
 	  <para>an IP address block requires reverse DNS entries (IP to
 	    hostname).</para>
 	</listitem>
 	<listitem>
 	  <para>a backup name server, called a slave, must reply to queries
 	    when the primary is down or inaccessible.</para>
 	  </listitem>
       </itemizedlist>
 
       <para>A caching name server is needed when:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>a local DNS server may cache and respond more quickly
 	    than querying an outside name server.</para>
 	</listitem>
 	<listitem>
 	  <para>a reduction in overall network traffic is desired (DNS
 	    traffic has been measured to account for 5% or more of total
 	    Internet traffic).</para>
 	</listitem>
       </itemizedlist>
 
       <para>When one queries for <hostid
 	role="fqdn">www.FreeBSD.org</hostid>, the resolver usually
 	queries the uplink ISP's name server, and retrieves the reply.
 	With a local, caching DNS server, the query only has to be
 	made once to the outside world by the caching DNS server.
 	Every additional query will not have to look to the outside of
 	the local network, since the information is cached
 	locally.</para>
 
     </sect2>
 
     <sect2>
       <title>How It Works</title>
       <para>In FreeBSD, the BIND daemon is called
 	<application>named</application> for obvious reasons.</para>
 
       <informaltable frame="none" pgwide="1">
 	<tgroup cols="2">
 	  <thead>
 	    <row>
 	      <entry>File</entry>
 	      <entry>Description</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry><application>named</application></entry>
 	      <entry>the BIND daemon</entry>
 	    </row>
 
 	    <row>
 	      <entry><command>ndc</command></entry>
 	      <entry>name daemon control program</entry>
 	    </row>
 
 	    <row>
 	      <entry><filename>/etc/namedb</filename></entry>
 	      <entry>directory where BIND zone information resides</entry>
 	    </row>
 
 	    <row>
 	      <entry><filename>/etc/namedb/named.conf</filename></entry>
 	      <entry>daemon configuration file</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
 
       <para>
         Zone files are usually contained within the
         <filename>/etc/namedb</filename>
         directory, and contain the DNS zone information
 	served by the name server.
       </para>
     </sect2>
 
     <sect2>
       <title>Starting BIND</title>
       <indexterm>
         <primary>BIND</primary>
 	<secondary>starting</secondary>
       </indexterm>
       <para>
         Since BIND is installed by default, configuring it all is
         relatively simple.
       </para>
       <para>
         To ensure the <application>named</application> daemon is
          started at boot, put the following line in
          <filename>/etc/rc.conf</filename>:
       </para>
       <programlisting>named_enable="YES"</programlisting>
       <para>To start the daemon manually (after configuring it):</para>
       <screen>&prompt.root; <userinput>ndc start</userinput></screen>
     </sect2>
 
     <sect2>
       <title>Configuration Files</title>
       <indexterm>
         <primary>BIND</primary>
 	<secondary>configuration files</secondary>
       </indexterm>
       <sect3>
         <title>Using <command>make-localhost</command></title>
         <para>Be sure to:
         </para>
         <screen>&prompt.root; <userinput>cd /etc/namedb</userinput>
 &prompt.root; <userinput>sh make-localhost</userinput></screen>
         <para>to properly create the local reverse DNS zone file in
           <filename>/etc/namedb/master/localhost.rev</filename>.
         </para>
       </sect3>
 
       <sect3>
         <title><filename>/etc/namedb/named.conf</filename></title>
 
         <programlisting>// &dollar;FreeBSD$
 //
 // Refer to the named(8) manual page for details.  If you are ever going
 // to setup a primary server, make sure you've understood the hairy
 // details of how DNS is working.  Even with simple mistakes, you can
 // break connectivity for affected parties, or cause huge amount of
 // useless Internet traffic.
 
 options {
         directory "/etc/namedb";
 
 // In addition to the "forwarders" clause, you can force your name
 // server to never initiate queries of its own, but always ask its
 // forwarders only, by enabling the following line:
 //
 //      forward only;
 
 // If you've got a DNS server around at your upstream provider, enter
 // its IP address here, and enable the line below.  This will make you
 // benefit from its cache, thus reduce overall DNS traffic in the
 Internet.
 /*
         forwarders {
                 127.0.0.1;
         };
 */</programlisting>
 
         <para>
 	  Just as the comment says, to benefit from an uplink's cache,
           <literal>forwarders</literal> can be enabled here.  Under normal
           circumstances, a name server will recursively query the Internet
           looking at certain name servers until it finds the answer it is
           looking for.  Having this enabled will have it query the uplink's
           name server (or name server provided) first, taking advantage of
           its cache.  If the uplink name server in question is a heavily
           trafficked, fast name server, enabling this may be worthwhile.
         </para>
 
 	<warning><para><hostid role="ipaddr">127.0.0.1</hostid>
             will <emphasis>not</emphasis> work here.
             Change this IP address to a name server at your uplink.</para>
         </warning>
 
         <programlisting>        /*
          * If there is a firewall between you and name servers you want
          * to talk to, you might need to uncomment the query-source
          * directive below.  Previous versions of BIND always asked
          * questions using port 53, but BIND 8.1 uses an unprivileged
          * port by default.
          */
         // query-source address * port 53;
 
         /*
          * If running in a sandbox, you may have to specify a different
          * location for the dumpfile.
          */
         // dump-file "s/named_dump.db";
 };
 
 // Note: the following will be supported in a future release.
 /*
 host { any; } {
         topology {
                 127.0.0.0/8;
         };
 };
 */
 
 // Setting up secondaries is way easier and the rough picture for this
 // is explained below.
 //
 // If you enable a local name server, don't forget to enter 127.0.0.1
 // into your /etc/resolv.conf so this server will be queried first.
 // Also, make sure to enable it in /etc/rc.conf.
 
 zone "." {
         type hint;
         file "named.root";
 };
 
 zone "0.0.127.IN-ADDR.ARPA" {
         type master;
         file "localhost.rev";
 };
 
 // NB: Do not use the IP addresses below, they are faked, and only
 // serve demonstration/documentation purposes!
 //
 // Example secondary config entries.  It can be convenient to become
 // a secondary at least for the zone where your own domain is in.  Ask
 // your network administrator for the IP address of the responsible
 // primary.
 //
 // Never forget to include the reverse lookup (IN-ADDR.ARPA) zone!
 // (This is the first bytes of the respective IP address, in reverse
 // order, with ".IN-ADDR.ARPA" appended.)
 //
 // Before starting to setup a primary zone, better make sure you fully
 // understand how DNS and BIND works, however.  There are sometimes
 // unobvious pitfalls.  Setting up a secondary is comparably simpler.
 //
 // NB: Don't blindly enable the examples below. :-)  Use actual names
 // and addresses instead.
 //
 // NOTE!!! FreeBSD runs BIND in a sandbox (see named_flags in rc.conf).
 // The directory containing the secondary zones must be write accessible
 // to BIND.  The following sequence is suggested:
 //
 //      mkdir /etc/namedb/s
 //      chown bind:bind /etc/namedb/s
 //      chmod 750 /etc/namedb/s</programlisting>
 
 	<para>For more information on running BIND in a sandbox, see
 	  <link linkend="network-named-sandbox">Running named in a sandbox</link>.
 	</para>
 
 	<programlisting>/*
 zone "example.com" {
         type slave;
         file "s/example.com.bak";
         masters {
                 192.168.1.1;
         };
 };
 
 zone "0.168.192.in-addr.arpa" {
         type slave;
         file "s/0.168.192.in-addr.arpa.bak";
         masters {
                 192.168.1.1;
         };
 };
 */</programlisting>
         <para>In <filename>named.conf</filename>, these are examples of slave
 	  entries for a forward and reverse zone.</para>
 
         <para>For each new zone served, a new zone entry must be added to
 	  <filename>named.conf</filename>.</para>
 
         <para>For example, the simplest zone entry for
 	  <hostid role="domainname">example.org</hostid> can look like:</para>
 
         <programlisting>zone "example.org" {
 	type master;
 	file "example.org";
 };</programlisting>
 
 	<para>The zone is a master, as indicated by the <option>type</option>
 	  statement, holding its zone information in
 	  <filename>/etc/namedb/example.org</filename> indicated by
 	  the <option>file</option> statement.</para>
 
         <programlisting>zone "example.org" {
 	type slave;
 	file "example.org";
 };</programlisting>
 
         <para>In the slave case, the zone information is transferred from
 	  the master name server for the particular zone, and saved in the
 	  file specified.  If and when the master server dies or is
 	  unreachable, the slave name server will have the transferred
 	  zone information and will be able to serve it.</para>
       </sect3>
 
       <sect3>
         <title>Zone Files</title>
         <para>
           An example master zone file for <hostid
 	  role="domainname">example.org</hostid> (existing within
 	  <filename>/etc/namedb/example.org</filename>) is as follows:
         </para>
 
         <programlisting>$TTL 3600
 
 example.org. IN SOA ns1.example.org. admin.example.org. (
                         5               ; Serial
                         10800           ; Refresh
                         3600            ; Retry
                         604800          ; Expire
                         86400 )         ; Minimum TTL
 
 ; DNS Servers
 @       IN NS           ns1.example.org.
 @       IN NS           ns2.example.org.
 
 ; Machine Names
 localhost       IN A    127.0.0.1
 ns1             IN A    3.2.1.2
 ns2             IN A    3.2.1.3
 mail            IN A    3.2.1.10
 @               IN A    3.2.1.30
 
 ; Aliases
 www             IN CNAME        @
 
 ; MX Record
 @               IN MX   10      mail.example.org.</programlisting>
 
         <para>
           Note that every hostname ending in a <quote>.</quote> is an
           exact hostname, whereas everything without a trailing
           <quote>.</quote> is referenced to the origin.  For example,
           <literal>www</literal> is translated into
           <literal>www.<replaceable>origin</replaceable></literal>.
           In our fictitious zone file, our origin is
           <hostid>example.org.</hostid>, so <literal>www</literal>
           would translate to <hostid>www.example.org.</hostid>
         </para>
 
         <para>
           The format of a zone file follows:
         </para>
         <programlisting>recordname      IN recordtype   value</programlisting>
 
 	<indexterm>
 	  <primary>DNS</primary>
 	  <secondary>records</secondary>
 	</indexterm>
         <para>
           The most commonly used DNS records:
         </para>
 
 	<variablelist>
 	  <varlistentry>
 	    <term>SOA</term>
 
 	    <listitem><para>start of zone authority</para></listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term>NS</term>
 
 	    <listitem><para>an authoritative name server</para></listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term>A</term>
 
 	    <listitem><para>a host address</para></listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term>CNAME</term>
 
 	    <listitem><para>the canonical name for an alias</para></listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term>MX</term>
 
 	    <listitem><para>mail exchanger</para></listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term>PTR</term>
 
 	    <listitem><para>a domain name pointer (used in reverse DNS)
 	      </para></listitem>
 	  </varlistentry>
 	</variablelist>
 
         <programlisting>
 example.org. IN SOA ns1.example.org. admin.example.org. (
                         5               ; Serial
                         10800           ; Refresh after 3 hours
                         3600            ; Retry after 1 hour
                         604800          ; Expire after 1 week
                         86400 )         ; Minimum TTL of 1 day</programlisting>
 
 
 
 	<variablelist>
 	  <varlistentry>
 	    <term><hostid role="domainname">example.org.</hostid></term>
 
 	    <listitem><para>the domain name, also the origin for this
 		zone file.</para></listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term><hostid role="fqdn">ns1.example.org.</hostid></term>
 
 	    <listitem><para>the primary/authoritative name server for this
 		zone.</para></listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term><literal>admin.example.org.</literal></term>
 
 	    <listitem><para>the responsible person for this zone,
 		email address with <quote>@</quote>
           replaced.  (<email>admin@example.org</email> becomes
 		<literal>admin.example.org</literal>)</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term><literal>5</literal></term>
 
 	      <listitem><para>the serial number of the file.  This
 		  must be incremented each time the zone file is
 		  modified.  Nowadays, many admins prefer a
 		  <literal>yyyymmddrr</literal> format for the serial
 		  number.  <literal>2001041002</literal> would mean
 		  last modified 04/10/2001, the latter
 		  <literal>02</literal> being the second time the zone
 		  file has been modified this day.  The serial number
 		  is important as it alerts slave name servers for a
 		  zone when it is updated.</para>
 	      </listitem>
 	  </varlistentry>
 	</variablelist>
 
         <programlisting>
 @       IN NS           ns1.example.org.</programlisting>
 
         <para>
           This is an NS entry.  Every name server that is going to reply
           authoritatively for the zone must have one of these entries.
 	  The <literal>@</literal> as seen here could have been
 	  <hostid role="domainname">example.org.</hostid>
 	  The <literal>@</literal> translates to the origin.
         </para>
 
         <programlisting>
 localhost       IN A    127.0.0.1
 ns1             IN A    3.2.1.2
 ns2             IN A    3.2.1.3
 mail            IN A    3.2.1.10
 @               IN A    3.2.1.30</programlisting>
 
         <para>
           The A record indicates machine names.  As seen above,
           <hostid role="fqdn">ns1.example.org</hostid> would resolve
           to <hostid role="ipaddr">3.2.1.2</hostid>.  Again, the
           origin symbol, <literal>@</literal>, is used here, thus
           meaning <hostid role="domainname">example.org</hostid> would
           resolve to <hostid role="ipaddr">3.2.1.30</hostid>.
         </para>
 
         <programlisting>
 www             IN CNAME        @</programlisting>
 
         <para>
           The canonical name record is usually used for giving aliases
           to a machine.  In the example, <hostid>www</hostid> is
           aliased to the machine addressed to the origin, or
           <hostid role="domainname">example.org</hostid>
           (<hostid role="ipaddr">3.2.1.30</hostid>).
           CNAMEs can be used to provide alias
           hostnames, or round robin one hostname among multiple
           machines.
         </para>
 
 	<indexterm>
 	  <primary>MX record</primary>
 	</indexterm>
 
         <programlisting>
 @               IN MX   10      mail.example.org.</programlisting>
 
         <para>
           The MX record indicates which mail
           servers are responsible for handling incoming mail for the
           zone.  <hostid role="fqdn">mail.example.org</hostid> is the
           hostname of the mail server, and 10 being the priority of
           that mail server.
         </para>
 
         <para>
           One can have several mail servers, with priorities of 3, 2,
           1.  A mail server attempting to deliver to <hostid
           role="domainname">example.org</hostid> would first try the
           highest priority MX, then the second highest, etc, until the
           mail can be properly delivered.
         </para>
 
         <para>
           For in-addr.arpa zone files (reverse DNS), the same format is
           used, except with PTR entries instead of
 	  A or CNAME.
         </para>
 
         <programlisting>$TTL 3600
 
 1.2.3.in-addr.arpa. IN SOA ns1.example.org. admin.example.org. (
                         5               ; Serial
                         10800           ; Refresh
                         3600            ; Retry
                         604800          ; Expire
                         3600 )          ; Minimum
 
 @       IN NS   ns1.example.org.
 @       IN NS   ns2.example.org.
 
 2       IN PTR  ns1.example.org.
 3       IN PTR  ns2.example.org.
 10      IN PTR  mail.example.org.
 30      IN PTR  example.org.</programlisting>
 
         <para>This file gives the proper IP address to hostname
           mappings of our above fictitious domain.</para>
       </sect3>
     </sect2>
 
     <sect2>
       <title>Caching Name Server</title>
       <indexterm>
         <primary>BIND</primary>
         <secondary>caching name server</secondary>
       </indexterm>
 
       <para>A caching name server is a name server that is not
         authoritative for any zones.  It simply asks queries of its
         own, and remembers them for later use.  To set one up, just
         configure the name server as usual, omitting any inclusions of
         zones.</para>
     </sect2>
 
     <sect2 id="network-named-sandbox">
       <title>Running <application>named</application> in a Sandbox</title>
       <indexterm>
         <primary>BIND</primary>
         <secondary>running in a sandbox</secondary>
       </indexterm>
 
       <indexterm>
         <primary><command>chroot</command></primary>
       </indexterm>
       <para>For added security you may want to run &man.named.8; as an
 	unprivileged user, and configure it to &man.chroot.8; into a
 	sandbox directory.  This makes everything outside of the
 	sandbox inaccessible to the <application>named</application>
 	daemon.  Should <application>named</application> be
 	compromised, this will help to reduce the damage that can be
 	caused.  By default, FreeBSD has a user and a group called
 	<groupname>bind</groupname>, intended for this use.</para>
 
       <note><para>Various people would recommend that instead of configuring
 	<application>named</application> to <command>chroot</command>, you
 	should run <application>named</application> inside a &man.jail.8;.
 	This section does not attempt to cover this situation.</para>
       </note>
 
       <para>Since <application>named</application> will not be able to
 	access anything outside of the sandbox (such as shared
 	libraries, log sockets, and so on), there are a number of steps
 	that need to be followed in order to allow
 	<application>named</application> to function correctly.  In the
 	following checklist, it is assumed that the path to the sandbox
 	is <filename>/etc/namedb</filename> and that you have made no
 	prior modifications to the contents of this directory.  Perform
 	the following steps as <username>root</username>:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>Create all directories that <application>named</application>
 	    expects to see:</para>
 
 	  <screen>&prompt.root; <userinput>cd /etc/namedb</userinput>
 &prompt.root; <userinput>mkdir -p bin dev etc var/tmp var/run master slave</userinput>
 &prompt.root; <userinput>chown bind:bind slave var/*</userinput><co id="chown-slave"/></screen>
 
 
 
 	  <calloutlist>
 	    <callout arearefs="chown-slave">
 	      <para><application>named</application> only needs write access to
 		these directories, so that is all we give it.</para>
 	    </callout>
 	  </calloutlist>
 	</listitem>
 
 	<listitem>
 	  <para>Rearrange and create basic zone and configuration files:</para>
 	  <screen>&prompt.root; <userinput>cp /etc/localtime etc</userinput><co id="localtime"/>
 &prompt.root; <userinput>mv named.conf etc &amp;&amp; ln -sf etc/named.conf</userinput>
 &prompt.root; <userinput>mv named.root master</userinput>
 <!-- I don't like this next bit -->
 &prompt.root; <userinput>sh make-localhost</userinput>
 &prompt.root; <userinput>cat &gt; master/named.localhost
 $ORIGIN localhost.
 $TTL 6h
 @	IN	SOA	localhost. postmaster.localhost. (
 			1	; serial
 			3600	; refresh
 			1800	; retry
 			604800	; expiration
 			3600 )	; minimum
 	IN	NS	localhost.
 	IN	A		127.0.0.1
 ^D</userinput></screen>
 
 	  <calloutlist>
 	    <callout arearefs="localtime">
 	      <para>This allows <application>named</application> to log the
 		correct time to &man.syslogd.8;.</para>
 	    </callout>
 	  </calloutlist>
 	</listitem>
 
 	<listitem>
 
         <indexterm><primary>syslog</primary></indexterm>
         <indexterm><primary>log files</primary>
 	  <secondary>named</secondary></indexterm>
 
 	  <para>If you are running a version of &os; prior to 4.9-RELEASE, build a statically linked copy of
 	    <application>named-xfer</application>, and copy it into the sandbox:</para>
 
 	      <screen>&prompt.root; <userinput>cd /usr/src/lib/libisc</userinput>
 &prompt.root; <userinput>make cleandir &amp;&amp; make cleandir &amp;&amp; make depend &amp;&amp; make all</userinput>
 &prompt.root; <userinput>cd /usr/src/lib/libbind</userinput>
 &prompt.root; <userinput>make cleandir &amp;&amp; make cleandir &amp;&amp; make depend &amp;&amp; make all</userinput>
 &prompt.root; <userinput>cd /usr/src/libexec/named-xfer</userinput>
 &prompt.root; <userinput>make cleandir &amp;&amp; make cleandir &amp;&amp; make depend &amp;&amp; make NOSHARED=yes all</userinput>
 &prompt.root; <userinput>cp named-xfer /etc/namedb/bin &amp;&amp; chmod 555 /etc/namedb/bin/named-xfer</userinput><co id="clean-cruft"/></screen>
 
 	  <para>After your statically linked
 	    <command>named-xfer</command> is installed some cleaning up
 	    is required, to avoid leaving stale copies of libraries or
 	    programs in your source tree:</para>
 
 	  <screen>&prompt.root; <userinput>cd /usr/src/lib/libisc</userinput>
 &prompt.root; <userinput>make cleandir</userinput>
 &prompt.root; <userinput>cd /usr/src/lib/libbind</userinput>
 &prompt.root; <userinput>make cleandir</userinput>
 &prompt.root; <userinput>cd /usr/src/libexec/named-xfer</userinput>
 &prompt.root; <userinput>make cleandir</userinput></screen>
 
 	  <calloutlist>
 	    <callout arearefs="clean-cruft">
 	      <para>This step has been reported to fail occasionally.  If this
 		happens to you, then issue the command:</para>
 
 	      <screen>&prompt.root; <userinput>cd /usr/src &amp;&amp; make cleandir &amp;&amp; make cleandir</userinput></screen>
 
 	      <para>and delete your <filename>/usr/obj</filename> tree:</para>
 
 	      <screen>&prompt.root; <userinput>rm -fr /usr/obj &amp;&amp; mkdir /usr/obj</userinput></screen>
 
 		<para>This will clean out any <quote>cruft</quote> from your
 		  source tree, and retrying the steps above should then work.</para>
 	    </callout>
 	  </calloutlist>
 
 	  <para>If you are running &os; version 4.9-RELEASE or later,
 	    then the copy of <command>named-xfer</command> in
 	    <filename>/usr/libexec</filename> is statically linked by
 	    default, and you can simply use &man.cp.1; to copy it into
 	    your sandbox.</para>
 	</listitem>
 
 	<listitem>
 	  <para>Make a <filename>dev/null</filename> that
 	    <application>named</application> can see and write to:</para>
 
 	  <screen>&prompt.root; <userinput>cd /etc/namedb/dev &amp;&amp; mknod null c 2 2</userinput>
 &prompt.root; <userinput>chmod 666 null</userinput></screen>
 	</listitem>
 
 	<listitem>
 	  <para>Symlink <filename> /var/run/ndc</filename> to
 	    <filename>/etc/namedb/var/run/ndc</filename>:</para>
 
 	  <screen>&prompt.root; <userinput>ln -sf /etc/namedb/var/run/ndc /var/run/ndc</userinput></screen>
 
 	  <note>
 	    <para>This simply avoids having to specify the
 	      <option>-c</option> option to &man.ndc.8; every time you
 	      run it.  Since the contents of
 	      <filename>/var/run</filename> are deleted on boot, it may
 	      be useful to add this command to
 	      <username>root</username>'s &man.crontab.5;, using the
 	      <option>@reboot</option> option.</para>
 	  </note>
 
 	</listitem>
 
 	<listitem>
 
         <indexterm><primary>syslog</primary></indexterm>
         <indexterm><primary>log files</primary>
 	  <secondary>named</secondary></indexterm>
 
 	  <para>Configure &man.syslogd.8; to create an extra
 	    <devicename>log</devicename> socket that
 	    <application>named</application> can write to.  To do this,
 	    add <literal>-l /etc/namedb/dev/log</literal> to the
 	    <varname>syslogd_flags</varname> variable in
 	    <filename>/etc/rc.conf</filename>.</para>
 	</listitem>
 
 	<listitem>
 
           <indexterm><primary><command>chroot</command></primary></indexterm>
 
 	  <para>Arrange to have <application>named</application> start
 	    and <command>chroot</command> itself to the sandbox by
 	    adding the following to
 	    <filename>/etc/rc.conf</filename>:</para>
 
 	  <programlisting>named_enable="YES"
 named_flags="-u bind -g bind -t /etc/namedb /etc/named.conf"</programlisting>
 
 	  <note>
 	    <para>Note that the configuration file
 	    <replaceable>/etc/named.conf</replaceable> is denoted by a full
 	    pathname <emphasis>relative to the sandbox</emphasis>, i.e. in
 	    the line above, the file referred to is actually
 	    <filename>/etc/namedb/etc/named.conf</filename>.</para>
 	  </note>
 	</listitem>
       </itemizedlist>
 
       <para>The next step is to edit
 	<filename>/etc/namedb/etc/named.conf</filename> so that
 	<application>named</application> knows which zones to load and
 	where to find them on the disk.  There follows a commented
 	example (anything not specifically commented here is no
 	different from the setup for a DNS server not running in a
 	sandbox):</para>
 
 	<programlisting>options {
         directory "/";<co id="directory"/>
         named-xfer "/bin/named-xfer";<co id="named-xfer"/>
         version "";		// Don't reveal BIND version
         query-source address * port 53;
 };
 // ndc control socket
 controls {
         unix "/var/run/ndc" perm 0600 owner 0 group 0;
 };
 // Zones follow:
 zone "localhost" IN {
         type master;
         file "master/named.localhost";<co id="master"/>
         allow-transfer { localhost; };
         notify no;
 };
 zone "0.0.127.in-addr.arpa" IN {
         type master;
         file "master/localhost.rev";
         allow-transfer { localhost; };
         notify no;
 };
 zone "." IN {
         type hint;
         file "master/named.root";
 };
 zone "private.example.net" in {
         type master;
         file "master/private.example.net.db";
 	allow-transfer { 192.168.10.0/24; };
 };
 zone "10.168.192.in-addr.arpa" in {
         type slave;
         masters { 192.168.10.2; };
         file "slave/192.168.10.db";<co id="slave"/>
 };</programlisting>
 
       <calloutlist>
 	<callout arearefs="directory">
 	  <para>The
 	    <literal>directory</literal> statement is specified as
 	    <filename>/</filename>, since all files that
 	    <application>named</application> needs are within this
 	    directory (recall that this is equivalent to a
 	    <quote>normal</quote> user's
 	    <filename>/etc/namedb</filename>).</para>
 	</callout>
 
 	<callout arearefs="named-xfer">
 	  <para>Specifies the full path
 	    to the <command>named-xfer</command> binary (from
 	    <application>named</application>'s frame of reference).  This
 	    is necessary since <application>named</application> is
 	    compiled to look for <command>named-xfer</command> in
 	    <filename>/usr/libexec</filename> by default.</para>
 	</callout>
 	<callout arearefs="master"><para>Specifies the filename (relative
 	  to the <literal>directory</literal> statement above) where
 	  <application>named</application> can find the zone file for this
 	  zone.</para>
 	</callout>
 	<callout arearefs="slave"><para>Specifies the filename
 	    (relative to the <literal>directory</literal> statement above)
 	    where <application>named</application> should write a copy of
 	    the zone file for this zone after successfully transferring it
 	    from the master server.  This is why we needed to change the
 	    ownership of the directory <filename>slave</filename> to
 	    <groupname>bind</groupname> in the setup stages above.</para>
 	</callout>
       </calloutlist>
 
       <para>After completing the steps above, either reboot your
 	server or restart &man.syslogd.8; and start &man.named.8;, making
 	sure to use the new options specified in
 	<varname>syslogd_flags</varname> and
 	<varname>named_flags</varname>.  You should now be running a
 	sandboxed copy of <application>named</application>!</para>
 
     </sect2>
 
     <sect2>
       <title>Security</title>
 
       <para>Although BIND is the most common implementation of DNS,
         there is always the issue of security.  Possible and
         exploitable security holes are sometimes found.
       </para>
 
       <para>
         It is a good idea to read <ulink
         url="http://www.cert.org/">CERT</ulink>'s security advisories and
 	to subscribe to the &a.security-notifications;
         to stay up to date with the current Internet and FreeBSD security
         issues.
       </para>
 
       <tip><para>If a problem arises, keeping sources up to date and
         having a fresh build of <application>named</application> would
         not hurt.</para></tip>
     </sect2>
 
     <sect2>
       <title>Further Reading</title>
 
       <para>BIND/<application>named</application> manual pages:
       &man.ndc.8; &man.named.8; &man.named.conf.5;</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><ulink
 	      url="http://www.isc.org/products/BIND/">Official ISC BIND
 	      Page</ulink></para>
 	</listitem>
 
 	<listitem>
 	  <para><ulink
 	  url="http://www.nominum.com/getOpenSourceResource.php?id=6">
 	  BIND FAQ</ulink></para>
 	</listitem>
 
 	<listitem>
 	  <para><ulink url="http://www.oreilly.com/catalog/dns4/">O'Reilly
          DNS and BIND 4th Edition</ulink></para>
 	</listitem>
 
 	<listitem>
 	  <para><ulink
 	      url="ftp://ftp.isi.edu/in-notes/rfc1034.txt">RFC1034
 	      - Domain Names - Concepts and Facilities</ulink></para>
 	</listitem>
 
 	<listitem>
 	  <para><ulink
 	      url="ftp://ftp.isi.edu/in-notes/rfc1035.txt">RFC1035
 	      - Domain Names - Implementation and Specification</ulink></para>
 	</listitem>
       </itemizedlist>
     </sect2>
   </sect1>
 
   <sect1 id="network-bind9">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Tom</firstname>
 	  <surname>Rhodes</surname>
 	  <contrib>Written by </contrib>
 	</author>
       </authorgroup>
     </sect1info>
     <title><acronym>BIND</acronym>9 and &os;</title>
 
 <!-- This section is here to get users up with BIND9 configurations!  It
   does not cover the terminology, theoretical discussion (why run a name
   server) or the further reading which is still in the previous section.
   I did things this way to avoid repetition of content and obviously we
   cannot just remove the previous section since other supported releases
   use it.  When the previous section is removed then those comments
   should be moved here.  // Tom Rhodes -->
 
     <indexterm><primary>bind9</primary>
       <secondary>setting up</secondary></indexterm>
 
     <para>The release of &os;&nbsp;5.3 brought the
       <acronym>BIND</acronym>9 <acronym>DNS</acronym> server software
       into the distribution.  New security features, a new file system
       layout and automated &man.chroot.8; configuration came with the
       import.  This section has been written in two parts, the first
       will discuss new features and their configuration; the latter
       will cover upgrades to aid in move to &os;&nbsp;5.3.  From this
       moment on, the server will be referred to simply as
       &man.named.8; in place of <acronym>BIND</acronym>.  This section
       skips over the terminology described in the previous section as
       well as some of the theoretical discussions; thus, it is
       recommended that the previous section be consulted before reading
       any further here.</para>
 
     <para>Configuration files for <application>named</application> currently
       reside in
       <filename class="directory">/var/named/etc/namedb/</filename> and
       will need modification before use.  This is where most of the
       configuration will be performed.</para>
 
     <sect2>
       <title>Configuration of a Master Zone</title>
 
       <para>To configure a master zone visit
 	<filename class="directory">/var/named/etc/namedb/</filename>
 	and run the following command:</para>
 
       <screen>&prompt.root; <userinput>sh make-localhost</userinput></screen>
 
       <para>If all went well a new file should exist in the
 	<filename class="directory">master</filename> directory.  The
 	filenames should be <filename>localhost.rev</filename> for
 	the local domain name and <filename>localhost-v6.rev</filename>
 	for <acronym>IPv6</acronym> configurations.  As the default
 	configuration file, configuration for its use will already
 	be present in the <filename>named.conf</filename> file.</para>
     </sect2>
 
     <sect2>
       <title>Configuration of a Slave Zone</title>
 
       <para>Configuration for extra domains or sub domains may be
 	done properly by setting them as a slave zone.  In most cases,
 	the <filename>master/localhost.rev</filename> file could just be
 	copied over into the <filename class="directory">slave</filename>
 	directory and modified.  Once completed, the files need
 	to be properly added in <filename>named.conf</filename> such
 	as in the following configuration for
 	<hostid role="domainname">example.com</hostid>:</para>
 
       <programlisting>zone "example.com" {
         type slave;
         file "slave/example.com";
         masters {
                 10.0.0.1;
         };
 };
 
 zone "0.168.192.in-addr.arpa" {
         type slave;
         file "slave/0.168.192.in-addr.arpa";
         masters {
                 10.0.0.1;
         };
 };</programlisting>
 
       <para>Note well that in this example, the master
 	<acronym>IP</acronym> address is the primary domain server
 	from which the zones are transferred; it does not necessary serve
 	as <acronym>DNS</acronym> server itself.</para>
     </sect2>
 
     <sect2>
       <title>System Initialization Configuration</title>
 
       <para>In order for the <application>named</application> daemon to start
 	when the system is booted, the following option must be present
 	in the <filename>rc.conf</filename> file:</para>
 
       <programlisting>named_enable="YES"</programlisting>
 
       <para>While other options exist, this is the bare minimal
 	requirement.  Consult the &man.rc.conf.5; manual page for
 	a list of the other options.  If nothing is entered in the
 	<filename>rc.conf</filename> file then <application>named</application>
 	may be started on the command line by invoking:</para>
 
       <screen>&prompt.root; <userinput>/etc/rc.d/named start</userinput></screen>
     </sect2>
 
     <sect2>
       <title><acronym>BIND</acronym>9 Security</title>
 
       <para>While &os; automatically drops <application>named</application>
 	into a &man.chroot.8; environment; there are several other
 	security mechanisms in place which could help to lure off
 	possible <acronym>DNS</acronym> service attacks.</para>
 
       <sect3>
 	<title>Query Access Control Lists</title>
 
 	<para>A query access control list can be used to restrict
 	  queries against the zones.  The configuration works by
 	  defining the network inside of the <literal>acl</literal>
 	  token and then listing <acronym>IP</acronym> addresses in
 	  the zone configuration.  To permit domains to query the
 	  example host, just define it like this:</para>
 
 	<programlisting>acl "example.com" {
         192.168.0.0/24;
 };
 
 zone "example.com" {
         type slave;
         file "slave/example.com";
         masters {
                 10.0.0.1;
         };
 	allow-query { example.com; };
 };
 
 zone "0.168.192.in-addr.arpa" {
         type slave;
         file "slave/0.168.192.in-addr.arpa";
         masters {
                 10.0.0.1;
         };
 	allow-query { example.com; };
 };</programlisting>
       </sect3>
 
       <sect3>
 	<title>Restrict Version</title>
 
 	<para>Permitting version lookups on the <acronym>DNS</acronym>
 	  server could be opening the doors for an attacker.  A
 	  malicious user may use this information to hunt up known
 	  exploits or bugs to utilize against the host.</para>
 
 	<warning>
 	  <para>Setting a false version will not protect the server
 	    from exploits.  Only upgrading to a version that is not
 	    vulnerable will protect your server.</para>
 	</warning>
 
 	<para>A false version string can be placed the
 	  <literal>options</literal> section of
 	  <filename>named.conf</filename>:</para>
 
 	<programlisting>options {
         directory       "/etc/namedb";
         pid-file        "/var/run/named/pid";
         dump-file       "/var/dump/named_dump.db";
         statistics-file "/var/stats/named.stats";
         version		"None of your business";
 };</programlisting>
       </sect3>
 
 <!-- Here is where I stopped for now
       <sect3>
         <title>Authentication</title>
 
 	<para> ... </para>
 
 -->
     </sect2>
   </sect1>
 
 
   <sect1 id="network-apache">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Murray</firstname>
 	  <surname>Stokely</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
     </sect1info>
     <title>Apache HTTP Server</title>
 
     <indexterm><primary>web servers</primary>
       <secondary>setting up</secondary></indexterm>
     <indexterm><primary>Apache</primary></indexterm>
 
     <sect2>
       <title>Overview</title>
 
       <para>&os; is used to run some of the busiest web sites in the
         world.  The majority of web servers on the Internet are using
         the <application>Apache HTTP Server</application>.
         <application>Apache</application> software packages should be
         included on your FreeBSD installation media.  If you did not
         install <application>Apache</application> when you first
         installed FreeBSD, then you can install it from the <filename
         role="package">www/apache13</filename> or <filename
         role="package">www/apache20</filename> port.</para>
 
       <para>Once <application>Apache</application> has been installed
         successfully, it must be configured.</para>
 
       <note><para>This section covers version 1.3.X of the
         <application>Apache HTTP Server</application> as that is the
         most widely used version for &os;.  <application>Apache</application>&nbsp;2.X introduces many
         new technologies but they are not discussed here.  For more
         information about <application>Apache</application>&nbsp;2.X, please see <ulink
         url="http://httpd.apache.org/"></ulink>.</para></note>
 
     </sect2>
 
     <sect2>
       <title>Configuration</title>
 
       <indexterm><primary>Apache</primary>
 	<secondary>configuration file</secondary></indexterm>
 
       <para>The main <application>Apache HTTP Server</application> configuration file is
 	installed as
 	<filename>/usr/local/etc/apache/httpd.conf</filename> on &os;.
 	This file is a typical &unix; text configuration file with
 	comment lines beginning with the <literal>#</literal>
 	character.  A comprehensive description of all possible
 	configuration options is outside the scope of this book, so
 	only the most frequently modified directives will be described
 	here.</para>
 
       <variablelist>
 	<varlistentry>
 	  <term><literal>ServerRoot "/usr/local"</literal></term>
 
 	  <listitem>
 	    <para>This specifies the default directory hierarchy for
 	    the <application>Apache</application> installation.  Binaries are stored in the
 	    <filename class="directory">bin</filename> and
 	    <filename class="directory">sbin</filename> subdirectories
 	    of the server root, and configuration files are stored in
 	    <filename class="directory">etc/apache</filename>.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><literal>ServerAdmin you@your.address</literal></term>
 
 	  <listitem>
 	    <para>The address to which problems with the server should
 	      be emailed.  This address appears on some
 	      server-generated pages, such as error documents.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><literal>ServerName www.example.com</literal></term>
 
 	  <listitem>
 	    <para><literal>ServerName</literal> allows you to set a host name which is
 	      sent back to clients for your server if it is different
 	      to the one that the host is configured with (i.e., use <hostid>www</hostid>
 	      instead of the host's real name).</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><literal>DocumentRoot "/usr/local/www/data"</literal></term>
 
 	  <listitem>
 	    <para><literal>DocumentRoot</literal>: The directory out of which you will
 	      serve your documents. By default, all requests are taken
 	      from this directory, but symbolic links and aliases may
 	      be used to point to other locations.</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
 
       <para>It is always a good idea to make backup copies of your
 	<application>Apache</application> configuration file before making changes.  Once you are
 	satisfied with your initial configuration you are ready to
 	start running <application>Apache</application>.</para>
 
 <!-- sect3 for performance tuning directives?  maxservers minservers -->
 <!-- etc..?? -->
 
 <!-- Advanced configuration section.
 
 Performance tuning directives.
 
 Log file format -->
 
     </sect2>
 
     <sect2>
       <title>Running <application>Apache</application></title>
 
       <indexterm><primary>Apache</primary>
 	<secondary>starting or stopping</secondary></indexterm>
 
       <para><application>Apache</application> does not run from the
         <application>inetd</application> super server as many other
         network servers do.  It is configured to run standalone for
         better performance for incoming HTTP requests from client web
         browsers.  A shell script wrapper is included to make
         starting, stopping, and restarting the server as simple as
         possible.  To start up <application>Apache</application> for
         the first time, just run:</para>
 
       <screen>&prompt.root; <userinput>/usr/local/sbin/apachectl start</userinput></screen>
 
       <para>You can stop the server at any time by typing:</para>
 
       <screen>&prompt.root; <userinput>/usr/local/sbin/apachectl stop</userinput></screen>
 
       <para>After making changes to the configuration file for any
       reason, you will need to restart the server:</para>
 
       <screen>&prompt.root; <userinput>/usr/local/sbin/apachectl restart</userinput></screen>
 
       <para>To restart <application>Apache</application> without
 	aborting current connections, run:</para>
 
       <screen>&prompt.root; <userinput>/usr/local/sbin/apachectl graceful</userinput></screen>
 
       <para>Additional information available at
 	&man.apachectl.8; manual page.</para>
 
       <para>To launch <application>Apache</application> at system
         startup, add the following line to
         <filename>/etc/rc.conf</filename>:</para>
 
       <programlisting>apache_enable="YES"</programlisting>
 
       <para>If you would like to supply additional command line
 	options for the <application>Apache</application>
 	<command>httpd</command> program started at system boot, you
 	may specify them with an additional line in
 	<filename>rc.conf</filename>:</para>
 
       <programlisting>apache_flags=""</programlisting>
 
       <para>Now that the web server is running, you can view your web
         site by pointing a web browser to
         <literal>http://localhost/</literal>.  The default web page
         that is displayed is
         <filename>/usr/local/www/data/index.html</filename>.</para>
 
     </sect2>
 
     <sect2>
       <title>Virtual Hosting</title>
 
       <para><application>Apache</application> supports two different
 	types of Virtual Hosting. The first method is Name-based
 	Virtual Hosting. Name-based virtual hosting uses the clients
 	HTTP/1.1 headers to figure out the hostname. This allows many
 	different domains to share the same IP address.</para>
 
       <para>To setup <application>Apache</application> to use
         Name-based Virtual Hosting add an entry like the following to
         your <filename>httpd.conf</filename>:</para>
 
       <programlisting>NameVirtualHost *</programlisting>
 
       <para>If your webserver was named <hostid role="fqdn">www.domain.tld</hostid> and
         you wanted to setup a virtual domain for
         <hostid role="fqdn">www.someotherdomain.tld</hostid> then you would add
         the following entries to
         <filename>httpd.conf</filename>:</para>
 
       <screen>&lt;VirtualHost *&gt;
 ServerName www.domain.tld
 DocumentRoot /www/domain.tld
 &lt;/VirtualHost&gt;
 
 &lt;VirtualHost *&gt;
 ServerName www.someotherdomain.tld
 DocumentRoot /www/someotherdomain.tld
 &lt;/VirtualHost&gt;</screen>
 
       <para>Replace the addresses with the addresses you want to use
         and the path to the documents with what you are using.</para>
 
       <para>For more information about setting up virtual hosts,
         please consult the official <application>Apache</application>
         documentation at: <ulink
         url="http://httpd.apache.org/docs/vhosts/"></ulink>.</para>
 
     </sect2>
 
     <sect2>
       <title>Apache Modules</title>
 
       <indexterm><primary>Apache</primary>
 	<secondary>modules</secondary></indexterm>
 
       <para>There are many different <application>Apache</application> modules available to add
         functionality to the basic server.  The FreeBSD Ports
         Collection provides an easy way to install
         <application>Apache</application> together with some of the
         more popular add-on modules.</para>
 
       <sect3>
         <title>mod_ssl</title>
 
 	<indexterm><primary>web servers</primary>
           <secondary>secure</secondary></indexterm>
 	<indexterm><primary>SSL</primary></indexterm>
 	<indexterm><primary>cryptography</primary></indexterm>
 
         <para>The <application>mod_ssl</application> module uses the OpenSSL library to provide
           strong cryptography via the Secure Sockets Layer (SSL v2/v3)
           and Transport Layer Security (TLS v1) protocols.  This
           module provides everything necessary to request a signed
           certificate from a trusted certificate signing authority so
           that you can run a secure web server on &os;.</para>
 
 	<para>If you have not yet installed
 	  <application>Apache</application>, then a version of <application>Apache</application>
 	  1.3.X that includes <application>mod_ssl</application> may be installed with the <filename
 	  role="package">www/apache13-modssl</filename> port.  SSL
 	  support is also available for <application>Apache</application>&nbsp;2.X in the
 	  <filename role="package">www/apache20</filename> port,
 	  where it is enabled by default.</para>
 
 <!-- XXX add more information about configuring mod_ssl here. -->
 <!-- Generating keys, getting the key signed, setting up your secure -->
 <!-- web server! -->
       </sect3>
 
       <sect3>
         <title>Dynamic Websites with Perl &amp; PHP</title>
         <para>In the past few years, more businesses have turned to the
           Internet in order to enhance their revenue and increase
           exposure.  This has also increased the need for interactive
           web content.  While some companies, such as &microsoft;, have
           introduced solutions into their proprietary products, the
           open source community answered the call.  Two options for
           dynamic web content include mod_perl &amp; mod_php.</para>
 
         <sect4>
         <title>mod_perl</title>
 
 	<indexterm>
           <primary>mod_perl</primary>
           <secondary>Perl</secondary>
         </indexterm>
 
         <para>The <application>Apache</application>/Perl integration project brings together the
 	  full power of the Perl programming language and the <application>Apache
 	  HTTP Server</application>.  With the <application>mod_perl</application> module it is possible to
 	  write <application>Apache</application> modules entirely in Perl.  In addition, the
 	  persistent interpreter embedded in the server avoids the
 	  overhead of starting an external interpreter and the penalty
 	  of Perl start-up time.</para>
 
           <para><application>mod_perl</application> is available a few
             different ways.  To use <application>mod_perl</application>
             remember that <application>mod_perl</application> 1.0 only
             works with <application>Apache</application> 1.3 and
             <application>mod_perl</application> 2.0 only works with
             <application>Apache</application> 2.
             <application>mod_perl</application> 1.0 is available in
             <filename role="package">www/mod_perl</filename> and a
             statically compiled version is available in
             <filename role="package">www/apache13-modperl</filename>.
             <application>mod_perl</application> 2.0 is avaliable in
             <filename role="package">www/mod_perl2</filename>.</para>
         </sect4>
 
         <sect4>
           <sect4info>
 	  <authorgroup>
 	    <author>
 	      <firstname>Tom</firstname>
 	      <surname>Rhodes</surname>
 	      <contrib>Written by </contrib>
 	    </author>
 	  </authorgroup>
         </sect4info>
         <title>mod_php</title>
 
 	<indexterm>
           <primary>mod_php</primary>
           <secondary>PHP</secondary>
         </indexterm>
 
 	<para><acronym>PHP</acronym>, also known as <quote>PHP:
           Hypertext Preprocessor</quote> is a general-purpose scripting
           language that is especially suited for Web development.
           Capable of being embedded into <acronym>HTML</acronym> its
           syntax draws upon C, &java;, and Perl with the intention of
           allowing web developers to write dynamically generated
           webpages quickly.</para>
 
 	<para>To gain support for <acronym>PHP</acronym>5 for the
 	  <application>Apache</application> web server, begin by
 	  installing the
 	  <filename role="package">www/mod_php5</filename>
 	  port.</para>
 
 	<para>This will install and configure the modules required
           to support dynamic <acronym>PHP</acronym> applications.  Check
           to ensure the following lines have been added to
 	  <filename>/usr/local/etc/apache/httpd.conf</filename>:</para>
 
 	<programlisting>LoadModule php5_module        libexec/apache/libphp5.so
 AddModule mod_php5.c
     &lt;IfModule mod_php5.c&gt;
         DirectoryIndex index.php index.html
     &lt;/IfModule&gt;
 
     &lt;IfModule mod_php5.c&gt;
         AddType application/x-httpd-php .php
         AddType application/x-httpd-php-source .phps
     &lt;/IfModule&gt;</programlisting>
 
           <para>Once completed, a simple call to the
             <command>apachectl</command> command for a graceful
             restart is needed to load the <acronym>PHP</acronym>
             module:</para>
 
 	<screen>&prompt.root; <userinput>apachectl graceful</userinput></screen>
 
           <para>The <acronym>PHP</acronym> support in &os; is extremely
             modular so the base install is very limited.  It is very easy
             to add support using the
             <filename role="package">lang/php5-extensions</filename> port.
             This port provides a menu driven interface to
             <acronym>PHP</acronym> extension installation.
             Alternatively, individual extensions can be installed using
             the appropriate port.</para>
 
 	<para>For instance, to add support for the
 	  <application>MySQL</application> database server to
 	  <acronym>PHP</acronym>5, simply install the
 	  <filename role="package">databases/php5-mysql</filename>
 	  port.</para>
 
           <para>After installing an extension, the
             <application>Apache</application> server must be reloaded to
               pick up the new configuration changes.</para>
 
 	<screen>&prompt.root; <userinput>apachectl graceful</userinput></screen>
         </sect4>
       </sect3>
     </sect2>
   </sect1>
 
   <sect1 id="network-ftp">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Murray</firstname>
 	  <surname>Stokely</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
     </sect1info>
     <title>File Transfer Protocol (FTP)</title>
 
     <indexterm><primary>FTP servers</primary></indexterm>
 
     <sect2>
       <title>Overview</title>
 
       <para>The File Transfer Protocol (FTP) provides users with a
 	simple way to transfer files to and from an <acronym
 	role="File Transfer Protocol">FTP</acronym> server.  &os;
 	includes <acronym role="File Transfer Protocol">FTP</acronym>
 	server software, <application>ftpd</application>, in the base
 	system.  This makes setting up and administering an <acronym
 	role="File Transfer Protocol">FTP</acronym> server on FreeBSD
 	very straightforward.</para>
     </sect2>
 
     <sect2>
       <title>Configuration</title>
 
       <para>The most important configuration step is deciding which
 	accounts will be allowed access to the FTP server.  A normal
 	FreeBSD system has a number of system accounts used for
 	various daemons, but unknown users should not be allowed to
 	log in with these accounts.  The
 	<filename>/etc/ftpusers</filename> file is a list of users
 	disallowed any FTP access.  By default, it includes the
 	aforementioned system accounts, but it is possible to add
 	specific users here that should not be allowed access to
 	FTP.</para>
 
       <para>You may want to restrict the access of some users without
 	preventing them completely from using FTP.  This can be
 	accomplished with the <filename>/etc/ftpchroot</filename>
 	file.  This file lists users and groups subject to FTP access
 	restrictions.  The &man.ftpchroot.5; manual page has all of
 	the details so it will not be described in detail here.</para>
 
       <indexterm>
 	<primary>FTP</primary>
 	<secondary>anonymous</secondary>
       </indexterm>
 
       <para>If you would like to enable anonymous FTP access to your
 	server, then you must create a user named
 	<username>ftp</username> on your &os; system.  Users will then
 	be able to log on to your FTP server with a username of
 	<username>ftp</username> or <username>anonymous</username> and
 	with any password (by convention an email address for the user
 	should be used as the password).  The FTP server will call
 	&man.chroot.2; when an anonymous user logs in, to restrict
 	access to only the home directory of the
 	<username>ftp</username> user.</para>
 
       <para>There are two text files that specify welcome messages to
 	be displayed to FTP clients.  The contents of the file
 	<filename>/etc/ftpwelcome</filename> will be displayed to
 	users before they reach the login prompt.  After a successful
 	login, the contents of the file
 	<filename>/etc/ftpmotd</filename> will be displayed.  Note
 	that the path to this file is relative to the login environment, so the
 	file <filename>~ftp/etc/ftpmotd</filename> would be displayed
 	for anonymous users.</para>
 
       <para>Once the FTP server has been configured properly, it must
         be enabled in <filename>/etc/inetd.conf</filename>.  All that
         is required here is to remove the comment symbol
         <quote>#</quote> from in front of the existing
         <application>ftpd</application> line :</para>
 
       <programlisting>ftp	stream	tcp	nowait	root	/usr/libexec/ftpd	ftpd -l</programlisting>
 
       <para>As explained in <xref linkend="network-inetd-hangup"/>, a
         HangUP Signal must be sent to <application>inetd</application>
         after this configuration file is changed.</para>
 
       <para>You can now log on to your FTP server by typing:</para>
 
       <screen>&prompt.user; <userinput>ftp localhost</userinput></screen>
 
     </sect2>
 
     <sect2>
       <title>Maintaining</title>
 
       <indexterm><primary>syslog</primary></indexterm>
       <indexterm><primary>log files</primary>
 	<secondary>FTP</secondary></indexterm>
 
       <para>The <application>ftpd</application> daemon uses
         &man.syslog.3; to log messages.  By default, the system log
         daemon will put messages related to FTP in the
         <filename>/var/log/xferlog</filename> file.  The location of
         the FTP log can be modified by changing the following line in
         <filename>/etc/syslog.conf</filename>:</para>
 
       <programlisting>ftp.info      /var/log/xferlog</programlisting>
 
       <indexterm>
 	<primary>FTP</primary>
 	<secondary>anonymous</secondary>
       </indexterm>
 
       <para>Be aware of the potential problems involved with running
         an anonymous FTP server.  In particular, you should think
         twice about allowing anonymous users to upload files.  You may
         find that your FTP site becomes a forum for the trade of
         unlicensed commercial software or worse.  If you do need to
         allow anonymous FTP uploads, then you should set up the
         permissions so that these files can not be read by other
         anonymous users until they have been reviewed.</para>
 
     </sect2>
   </sect1>
 
   <sect1 id="network-samba">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Murray</firstname>
 	  <surname>Stokely</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
     </sect1info>
     <title>File and Print Services for &microsoft.windows; clients (Samba)</title>
 
     <indexterm><primary>Samba server</primary></indexterm>
     <indexterm><primary>Microsoft Windows</primary></indexterm>
     <indexterm>
       <primary>file server</primary>
       <secondary>Windows clients</secondary>
     </indexterm>
     <indexterm>
       <primary>print server</primary>
       <secondary>Windows clients</secondary>
     </indexterm>
 
     <sect2>
       <title>Overview</title>
 
       <para><application>Samba</application> is a popular open source
         software package that provides file and print services for
         &microsoft.windows; clients.  Such clients can connect to and
         use FreeBSD filespace as if it was a local disk drive, or
         FreeBSD printers as if they were local printers.</para>
 
       <para><application>Samba</application> software packages should
         be included on your FreeBSD installation media.  If you did
         not install <application>Samba</application> when you first
         installed FreeBSD, then you can install it from the <filename
         role="package">net/samba3</filename> port or package.</para>
 
 <!-- mention LDAP, Active Directory, WinBIND, ACL, Quotas, PAM, .. -->
 
     </sect2>
 
     <sect2>
       <title>Configuration</title>
 
       <para>A default <application>Samba</application> configuration
         file is installed as
         <filename>/usr/local/etc/smb.conf.default</filename>.  This
         file must be copied to
         <filename>/usr/local/etc/smb.conf</filename> and customized
         before <application>Samba</application> can be used.</para>
 
       <para>The <filename>smb.conf</filename> file contains runtime
         configuration information for
         <application>Samba</application>, such as definitions of the
         printers and <quote>file system shares</quote> that you would
         like to share with &windows; clients.  The
         <application>Samba</application> package includes a web based
         tool called <application>swat</application> which provides a
         simple way of configuring the <filename>smb.conf</filename>
         file.</para>
 
       <sect3>
 	<title>Using the Samba Web Administration Tool (SWAT)</title>
 
 	<para>The Samba Web Administration Tool (SWAT) runs as a
 	  daemon from <application>inetd</application>.  Therefore, the
 	  following line in <filename>/etc/inetd.conf</filename>
 	  should be uncommented before <application>swat</application> can be
 	  used to configure <application>Samba</application>:</para>
 
 	<programlisting>swat   stream  tcp     nowait/400      root    /usr/local/sbin/swat</programlisting>
         <para>As explained in <xref linkend="network-inetd-hangup"/>, a
           HangUP Signal must be sent to
           <application>inetd</application> after this configuration
           file is changed.</para>
 
 	<para>Once <application>swat</application> has been enabled in
 	  <filename>inetd.conf</filename>, you can use a browser to
 	  connect to <ulink url="http://localhost:901"></ulink>.  You will
 	  first have to log on with the system <username>root</username> account.</para>
 
 <!-- XXX screenshots go here, loader is creating them -->
 
 	<para>Once you have successfully logged on to the main
 	  <application>Samba</application> configuration page, you can
 	  browse the system documentation, or begin by clicking on the
 	  <guimenu>Globals</guimenu> tab.  The <guimenu>Globals</guimenu> section corresponds to the
 	  variables that are set in the <literal>[global]</literal>
 	  section of
 	  <filename>/usr/local/etc/smb.conf</filename>.</para>
       </sect3>
 
       <sect3>
 	<title>Global Settings</title>
 
 	<para>Whether you are using <application>swat</application> or
 	  editing <filename>/usr/local/etc/smb.conf</filename>
 	  directly, the first directives you are likely to encounter
 	  when configuring <application>Samba</application>
 	  are:</para>
 
         <variablelist>
 	  <varlistentry>
 	    <term><literal>workgroup</literal></term>
 
 	    <listitem>
 	      <para>NT Domain-Name or Workgroup-Name for the computers
 	        that will be accessing this server.</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term><literal>netbios name</literal></term>
 
 	    <listitem>
 	      <indexterm><primary>NetBIOS</primary></indexterm>
 
 	      <para>This sets the NetBIOS name by which a <application>Samba</application> server
 		is known. By default it is the same as the first
 		component of the host's DNS name.</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term><literal>server string</literal></term>
 
 	    <listitem>
 	      <para>This sets the string that will be displayed with
 		the <command>net view</command> command and some other
 		networking tools that seek to display descriptive text
 		about the server.</para>
 	    </listitem>
 	  </varlistentry>
         </variablelist>
       </sect3>
 
       <sect3>
 	<title>Security Settings</title>
 
 	<para>Two of the most important settings in
 	  <filename>/usr/local/etc/smb.conf</filename> are the
 	  security model chosen, and the backend password format for
 	  client users.  The following directives control these
 	  options:</para>
 
         <variablelist>
 	  <varlistentry>
 	    <term><literal>security</literal></term>
 
 	    <listitem>
 	      <para>The two most common options here are
 	        <literal>security = share</literal> and <literal>security
 	        = user</literal>.  If your clients use usernames that
 	        are the same as their usernames on your &os; machine
 	        then you will want to use user level security.  This
 	        is the default security policy and it requires clients
 	        to first log on before they can access shared
 	        resources.</para>
 
 	      <para>In share level security, client do not need to log
 	        onto the server with a valid username and password
 	        before attempting to connect to a shared resource.
 	        This was the default security model for older versions
 	        of <application>Samba</application>.</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term><literal>passdb backend</literal></term>
 
 	    <listitem>
-	      <indexterm><primary>NIS+</primary></indexterm>
-	      <indexterm><primary>LDAP</primary></indexterm>
-	      <indexterm><primary>SQL database</primary></indexterm>
-
 	      <para><application>Samba</application> has several
 	        different backend authentication models.  You can
-	        authenticate clients with LDAP, NIS+, a SQL database,
+	        authenticate clients with LDAP<indexterm><primary>LDAP</primary></indexterm>,
+		NIS+<indexterm><primary>NIS+</primary></indexterm>, a SQL database<indexterm><primary>SQL database</primary></indexterm>,
 	        or a modified password file.  The default
 	        authentication method is <literal>smbpasswd</literal>,
 	        and that is all that will be covered here.</para>
 	    </listitem>
 	  </varlistentry>
 	</variablelist>
 
 	<para>Assuming that the default <literal>smbpasswd</literal>
 	  backend is used, the
 	  <filename>/usr/local/private/smbpasswd</filename> file must
 	  be created to allow <application>Samba</application> to
 	  authenticate clients.  If you would like to give all of
 	  your &unix; user accounts access from &windows; clients, use the
 	  following command:</para>
 
 	<screen>&prompt.root; <userinput>grep -v "^#" /etc/passwd | make_smbpasswd &gt; /usr/local/private/smbpasswd</userinput>
 &prompt.root; <userinput>chmod 600 /usr/local/private/smbpasswd</userinput></screen>
 
 	<para>Please see the <application>Samba</application>
 	  documentation for additional information about configuration
 	  options.  With the basics outlined here, you should have
 	  everything you need to start running
 	  <application>Samba</application>.</para>
       </sect3>
 
     </sect2>
     <sect2>
       <title>Starting <application>Samba</application></title>
 
       <para>To enable <application>Samba</application> when your
         system boots, add the following line to
         <filename>/etc/rc.conf</filename>:</para>
 
       <programlisting>samba_enable="YES"</programlisting>
 
       <para>You can then start <application>Samba</application> at any
         time by typing:</para>
 
       <screen>&prompt.root; <userinput>/usr/local/etc/rc.d/samba.sh start</userinput>
 Starting SAMBA: removing stale tdbs :
 Starting nmbd.
 Starting smbd.</screen>
 
       <para><application>Samba</application> actually consists of
         three separate daemons.  You should see that both the
         <application>nmbd</application> and <application>smbd</application> daemons
         are started by the <filename>samba.sh</filename> script.  If
         you enabled winbind name resolution services in
         <filename>smb.conf</filename>, then you will also see that
         the <application>winbindd</application> daemon is started.</para>
 
       <para>You can stop <application>Samba</application> at any time
         by typing :</para>
 
       <screen>&prompt.root; <userinput>/usr/local/etc/rc.d/samba.sh stop</userinput></screen>
 
       <para><application>Samba</application> is a complex software
         suite with functionality that allows broad integration with
         &microsoft.windows; networks.  For more information about
         functionality beyond the basic installation described here,
         please see <ulink url="http://www.samba.org"></ulink>.</para>
     </sect2>
 
   </sect1>
 
   <sect1 id="network-ntp">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Tom</firstname>
 	  <surname>Hukins</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
     </sect1info>
     <title>Clock Synchronization with NTP</title>
 
     <indexterm><primary>NTP</primary></indexterm>
 
     <sect2>
       <title>Overview</title>
 
       <para>Over time, a computer's clock is prone to drift.  The
 	Network Time Protocol (NTP) is one way to ensure your clock stays
 	accurate.</para>
 
       <para>Many Internet services rely on, or greatly benefit from,
 	computers' clocks being accurate.  For example, a web server
 	may receive requests to send a file if it has been modified since a
 	certain time.  In a local area network environment, it is
 	essential that computers sharing files from the same file
 	server have synchronized clocks so that file timestamps stay
 	consistent.  Services such as &man.cron.8; also rely on
 	an accurate system clock to run commands at the specified
 	times.</para>
 
       <indexterm>
 	<primary>NTP</primary>
 	<secondary>ntpd</secondary>
       </indexterm>
       <para>FreeBSD ships with the &man.ntpd.8; <acronym role="Network
 	Time Protocol">NTP</acronym> server which can be used to query
 	other <acronym role="Network Time Protocol">NTP</acronym>
 	servers to set the clock on your machine or provide time
 	services to others.</para>
     </sect2>
 
     <sect2>
       <title>Choosing Appropriate NTP Servers</title>
 
       <indexterm>
 	<primary>NTP</primary>
 	<secondary>choosing servers</secondary>
       </indexterm>
 
       <para>In order to synchronize your clock, you will need to find
 	one or more <acronym role="Network Time
 	Protocol">NTP</acronym> servers to use.  Your network
 	administrator or ISP may have set up an NTP server for this
 	purpose&mdash;check their documentation to see if this is the
 	case.  There is an <ulink
 	url="http://ntp.isc.org/bin/view/Servers/WebHome">online
 	list of publicly accessible NTP servers</ulink> which you can
 	use to find an NTP server near to you.  Make sure you are
 	aware of the policy for any servers you choose, and ask for
 	permission if required.</para>
 
       <para>Choosing several unconnected NTP servers is a good idea in
 	case one of the servers you are using becomes unreachable or
 	its clock is unreliable.  &man.ntpd.8; uses the responses it
 	receives from other servers intelligently&mdash;it will favor
 	unreliable servers less than reliable ones.</para>
     </sect2>
 
     <sect2>
       <title>Configuring Your Machine</title>
 
       <indexterm>
 	<primary>NTP</primary>
 	<secondary>configuration</secondary>
       </indexterm>
 
       <sect3>
 	<title>Basic Configuration</title>
 	<indexterm><primary>ntpdate</primary></indexterm>
 
 	<para>If you only wish to synchronize your clock when the
 	  machine boots up, you can use &man.ntpdate.8;.  This may be
 	  appropriate for some desktop machines which are frequently
 	  rebooted and only require infrequent synchronization, but
 	  most machines should run &man.ntpd.8;.</para>
 
 	<para>Using &man.ntpdate.8; at boot time is also a good idea
 	  for machines that run &man.ntpd.8;.  The &man.ntpd.8;
 	  program changes the clock gradually, whereas &man.ntpdate.8;
 	  sets the clock, no matter how great the difference between a
 	  machine's current clock setting and the correct time.</para>
 
 	<para>To enable &man.ntpdate.8; at boot time, add
 	  <literal>ntpdate_enable="YES"</literal> to
 	  <filename>/etc/rc.conf</filename>.  You will also need to
 	  specify all servers you wish to synchronize with and any
 	  flags to be passed to &man.ntpdate.8; in
 	  <varname>ntpdate_flags</varname>.</para>
       </sect3>
 
       <sect3>
 	<title>General Configuration</title>
 
 	<indexterm>
 	  <primary>NTP</primary>
 	  <secondary>ntp.conf</secondary>
 	</indexterm>
 
 	<para>NTP is configured by the
 	  <filename>/etc/ntp.conf</filename> file in the format
 	  described in &man.ntp.conf.5;.  Here is a simple
 	  example:</para>
 
 	<programlisting>server ntplocal.example.com prefer
 server timeserver.example.org
 server ntp2a.example.net
 
 driftfile /var/db/ntp.drift</programlisting>
 
 	<para>The <literal>server</literal> option specifies which
 	  servers are to be used, with one server listed on each line.
 	  If a server is specified with the <literal>prefer</literal>
 	  argument, as with <hostid
 	  role="fqdn">ntplocal.example.com</hostid>, that server is
 	  preferred over other servers.  A response from a preferred
 	  server will be discarded if it differs significantly from
 	  other servers' responses, otherwise it will be used without
 	  any consideration to other responses.  The
 	  <literal>prefer</literal> argument is normally used for NTP
 	  servers that are known to be highly accurate, such as those
 	  with special time monitoring hardware.</para>
 
 	<para>The <literal>driftfile</literal> option specifies which
 	  file is used to store the system clock's frequency offset.
 	  The &man.ntpd.8; program uses this to automatically
 	  compensate for the clock's natural drift, allowing it to
 	  maintain a reasonably correct setting even if it is cut off
 	  from all external time sources for a period of time.</para>
 
 	<para>The <literal>driftfile</literal> option specifies which
 	  file is used to store information about previous responses
 	  from the NTP servers you are using.  This file contains
 	  internal information for NTP.  It should not be modified by
 	  any other process.</para>
       </sect3>
 
       <sect3>
 	<title>Controlling Access to Your Server</title>
 
 	<para>By default, your NTP server will be accessible to all
 	  hosts on the Internet.  The <literal>restrict</literal>
 	  option in <filename>/etc/ntp.conf</filename> allows you to
 	  control which machines can access your server.</para>
 
 	<para>If you want to deny all machines from accessing your NTP
 	  server, add the following line to
 	  <filename>/etc/ntp.conf</filename>:</para>
 
         <programlisting>restrict default ignore</programlisting>
 
         <para>If you only want to allow machines within your own
 	  network to synchronize their clocks with your server, but
 	  ensure they are not allowed to configure the server or used
 	  as peers to synchronize against, add</para>
 
         <programlisting>restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap</programlisting>
 
 	<para>instead, where <hostid role="ipaddr">192.168.1.0</hostid> is
 	  an IP address on your network and <hostid
 	  role="netmask">255.255.255.0</hostid> is your network's
 	  netmask.</para>
 
 	<para><filename>/etc/ntp.conf</filename> can contain multiple
 	  <literal>restrict</literal> options.  For more details, see
 	  the <literal>Access Control Support</literal> subsection of
 	  &man.ntp.conf.5;.</para>
       </sect3>
     </sect2>
 
     <sect2>
       <title>Running the NTP Server</title>
 
       <para>To ensure the NTP server is started at boot time, add the
 	line <literal>ntpd_enable="YES"</literal> to
 	<filename>/etc/rc.conf</filename>.  If you wish to pass
 	additional flags to &man.ntpd.8;, edit the
 	<varname>ntpd_flags</varname> parameter in
 	<filename>/etc/rc.conf</filename>.</para>
 
       <para>To start the server without rebooting your machine, run
 	<command>ntpd</command> being sure to specify any additional
 	parameters from <varname>ntpd_flags</varname> in
 	<filename>/etc/rc.conf</filename>.  For example:</para>
 
       <screen>&prompt.root; <userinput>ntpd -p /var/run/ntpd.pid</userinput></screen>
 
       <note>
 	<para>Under &os;&nbsp;4.X,
 	  you have to replace every instance of <literal>ntpd</literal>
 	  with <literal>xntpd</literal> in the options above.</para></note>
     </sect2>
 
     <sect2>
       <title>Using ntpd with a Temporary Internet
 	Connection</title>
 
       <para>The &man.ntpd.8; program does not need a permanent
 	connection to the Internet to function properly.  However, if
 	you have a temporary connection that is configured to dial out
 	on demand, it is a good idea to prevent NTP traffic from
 	triggering a dial out or keeping the connection alive.  If you
 	are using user PPP, you can use <literal>filter</literal>
 	directives in <filename>/etc/ppp/ppp.conf</filename>.  For
 	example:</para>
 
       <programlisting> set filter dial 0 deny udp src eq 123
  # Prevent NTP traffic from initiating dial out
  set filter dial 1 permit 0 0
  set filter alive 0 deny udp src eq 123
  # Prevent incoming NTP traffic from keeping the connection open
  set filter alive 1 deny udp dst eq 123
  # Prevent outgoing NTP traffic from keeping the connection open
  set filter alive 2 permit 0/0 0/0</programlisting>
 
       <para>For more details see the <literal>PACKET
 	FILTERING</literal> section in &man.ppp.8; and the examples in
 	<filename>/usr/share/examples/ppp/</filename>.</para>
 
       <note>
 	<para>Some Internet access providers block low-numbered ports,
 	  preventing NTP from functioning since replies never
 	  reach your machine.</para>
       </note>
     </sect2>
 
     <sect2>
       <title>Further Information</title>
 
       <para>Documentation for the NTP server can be found in
 	<filename>/usr/share/doc/ntp/</filename> in HTML
 	format.</para>
     </sect2>
   </sect1>
 
 </chapter>
diff --git a/zh_TW.Big5/books/handbook/ppp-and-slip/chapter.xml b/zh_TW.Big5/books/handbook/ppp-and-slip/chapter.xml
index 234cd31fd2..d7d20829a5 100644
--- a/zh_TW.Big5/books/handbook/ppp-and-slip/chapter.xml
+++ b/zh_TW.Big5/books/handbook/ppp-and-slip/chapter.xml
@@ -1,3233 +1,3193 @@
 <?xml version="1.0" encoding="big5"?>
 <!--
      The FreeBSD Documentation Project
 
      $FreeBSD$
      Original revision: 1.170
 -->
 
 <chapter id="ppp-and-slip">
   <chapterinfo>
     <authorgroup>
       <author>
 	<firstname>Jim</firstname>
 	<surname>Mock</surname>
 	<contrib>Restructured, reorganized, and updated by </contrib>
 	<!-- 1 Mar 2000 -->
       </author>
     </authorgroup>
   </chapterinfo>
 
   <title>PPP and SLIP</title>
 
   <sect1 id="ppp-and-slip-synopsis">
     <title>Synopsis</title>
     <indexterm id="ppp-ppp">
       <primary>PPP</primary>
     </indexterm>
     <indexterm id="ppp-slip">
       <primary>SLIP</primary>
     </indexterm>
 
     <para>FreeBSD has a number of ways to link one computer to
       another.  To establish a network or Internet connection through a
       dial-up modem, or to allow others to do so through you, requires
       the use of PPP or SLIP.  This chapter describes setting up
       these modem-based communication services in detail.</para>
 
     <para>After reading this chapter, you will know:</para>
 
     <itemizedlist>
       <listitem>
 	<para>How to set up user PPP.</para>
       </listitem>
       <listitem>
 	<para>How to set up kernel PPP.</para>
       </listitem>
       <listitem>
 	<para>How to set up <acronym>PPPoE</acronym> (PPP over
 	  Ethernet).</para>
       </listitem>
       <listitem>
 	<para>How to set up <acronym>PPPoA</acronym> (PPP over
 	  ATM).</para>
 	</listitem>
       <listitem>
 	<para>How to configure and set up a SLIP client and
 	  server.</para>
       </listitem>
     </itemizedlist>
 
     <indexterm id="ppp-ppp-user">
       <primary>PPP</primary>
       <secondary>user PPP</secondary>
     </indexterm>
     <indexterm id="ppp-ppp-kernel">
       <primary>PPP</primary>
       <secondary>kernel PPP</secondary>
     </indexterm>
     <indexterm id="ppp-ppp-ethernet">
       <primary>PPP</primary>
       <secondary>over Ethernet</secondary>
     </indexterm>
 
     <para>Before reading this chapter, you should:</para>
 
     <itemizedlist>
       <listitem>
 	<para>Be familiar with basic network terminology.</para>
       </listitem>
       <listitem>
 	<para>Understand the basics and purpose of a dialup connection
 	  and PPP and/or SLIP.</para>
       </listitem>
     </itemizedlist>
 
     <para>You may be wondering what the main difference is between user
       PPP and kernel PPP.  The answer is simple: user PPP processes the
       inbound and outbound data in userland rather than in the kernel.
       This is expensive in terms of copying the data between the kernel
       and userland, but allows a far more feature-rich PPP implementation.
       User PPP uses the <devicename>tun</devicename> device to communicate
       with the outside world whereas kernel PPP uses the
       <devicename>ppp</devicename> device.</para>
 
     <note>
       <para>Throughout in this chapter, user PPP will simply be
 	referred to as <application>ppp</application> unless a distinction needs to be made between it
 	and any other PPP software such as <application>pppd</application>.
 	Unless otherwise stated, all of the commands explained in this
 	chapter should be executed as <username>root</username>.</para>
     </note>
   </sect1>
 
   <sect1 id="userppp">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Tom</firstname>
           <surname>Rhodes</surname>
           <contrib>Updated and enhanced by </contrib>
         </author>
       </authorgroup>
       <authorgroup>
         <author>
           <firstname>Brian</firstname>
           <surname>Somers</surname>
 	  <contrib>Originally contributed by </contrib>
         </author>
       </authorgroup>
       <authorgroup>
 	<author>
 	  <firstname>Nik</firstname>
 	  <surname>Clayton</surname>
 	  <contrib>With input from </contrib>
         </author>
         <author>
 	  <firstname>Dirk</firstname>
           <surname>Fr&ouml;mberg</surname>
         </author>
         <author>
           <firstname>Peter</firstname>
           <surname>Childs</surname>
         </author>
       </authorgroup>
     </sect1info>
 
     <title>Using User PPP</title>
 
     <sect2>
       <title>User PPP</title>
 
       <sect3>
 	<title>Assumptions</title>
 
 	<para>This document assumes you have the following:</para>
 
 	<itemizedlist>
-	  <indexterm id="ppp-isp">
-	    <primary>ISP</primary>
-	  </indexterm>
-	  <indexterm id="ppp-ppp2">
-	    <primary>PPP</primary>
-	  </indexterm>
 	  <listitem>
-	    <para>An account with an Internet Service Provider (ISP) which
-	      you connect to using PPP.</para>
+	    <para>An account with an Internet Service Provider (ISP)<indexterm id="ppp-isp"><primary>ISP</primary></indexterm> which
+	      you connect to using PPP<indexterm id="ppp-ppp2"><primary>PPP</primary></indexterm>.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>You have a modem or
 	      other device connected to your system and configured
 	      correctly which allows you to connect to your ISP.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>The dial-up number(s) of your ISP.</para>
 	  </listitem>
 
 	  <listitem>
-	  <indexterm id="ppp-pap">
-	    <primary>PAP</primary>
-	  </indexterm>
-	  <indexterm id="ppp-chap">
-	    <primary>CHAP</primary>
-	  </indexterm>
-	  <indexterm id="ppp-unix">
-	    <primary>UNIX</primary>
-	  </indexterm>
-	  <indexterm id="ppp-login">
-	    <primary>login name</primary>
-	  </indexterm>
-	  <indexterm id="ppp-password">
-	    <primary>password</primary>
-	  </indexterm>
-	    <para>Your login name and password. (Either a
-	      regular &unix; style login and password pair, or a PAP or CHAP
+	    <para>Your login name<indexterm id="ppp-login"><primary>login name</primary></indexterm> and password<indexterm id="ppp-password"><primary>password</primary></indexterm>. (Either a
+	      regular &unix;<indexterm id="ppp-unix"><primary>UNIX</primary></indexterm> style login and password pair, or a
+	      PAP<indexterm id="ppp-pap"><primary>PAP</primary></indexterm> or CHAP<indexterm id="ppp-chap"><primary>CHAP</primary></indexterm>
 	      login and password pair.)</para>
 	  </listitem>
 
 	  <listitem>
-	    <indexterm id="ppp-nameserver">
-	      <primary>nameserver</primary>
-	    </indexterm>
-
-	    <para>The IP address of one or more name servers.
+	    <para>The IP address of one or more name servers<indexterm id="ppp-nameserver"><primary>nameserver</primary></indexterm>.
 	      Normally, you will be given two IP addresses by your ISP to
 	      use for this.  If they have not given you at least one, then
 	      you can use the <command>enable dns</command> command in
 	      <filename>ppp.conf</filename> and
 	      <application>ppp</application> will set the name servers for
 	      you.  This feature depends on your ISPs PPP implementation
               supporting DNS negotiation.</para>
 	  </listitem>
 	</itemizedlist>
 
 	<para>The following information may be supplied by your ISP, but
 	  is not completely necessary:</para>
 
 	<itemizedlist>
 	  <listitem>
 	    <para>The IP address of your ISP's gateway.  The gateway is
 	      the machine to which you will connect and will be set up as
 	      your <emphasis>default route</emphasis>.  If you do not have
 	      this information, we can make one up and your ISP's PPP
 	      server will tell us the correct value when we connect.</para>
 
 	    <para>This IP number is referred to as
 	      <literal>HISADDR</literal> by
 	      <application>ppp</application>.</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>The netmask you should use.  If your ISP has not
 	      provided you with one, you can safely use <hostid
 	      role="netmask">255.255.255.255</hostid>.</para>
 	  </listitem>
 
 	  <listitem>
-	    <indexterm id="ppp-static-ip">
-	      <primary>static IP address</primary>
-	    </indexterm>
-
-	    <para>If your ISP provides you with a static IP address and
+	    <para>If your ISP provides you with a static IP address<indexterm id="ppp-static-ip"><primary>static IP address</primary></indexterm> and
 	      hostname, you can enter it.  Otherwise, we simply let the
 	      peer assign whatever IP address it sees fit.</para>
 	  </listitem>
 	</itemizedlist>
 
 	<para>If you do not have any of the required information, contact
 	  your ISP.</para>
 
 	<note>
 	  <para>Throughout this section, many of the examples showing
 	    the contents of configuration files are numbered by line.
 	    These numbers serve to aid in the presentation and
 	    discussion only and are not meant to be placed in the actual
 	    file.  Proper indentation with tab and space characters is
 	    also important.</para>
 	</note>
 
       </sect3>
 
       <sect3>
 	<title>Creating PPP Device Nodes</title>
 	<indexterm><primary>PPP</primary><secondary>creating device nodes</secondary></indexterm>
 
 	<para>Under normal circumstances, most users will only need
 	  one <devicename>tun</devicename> device
 	  (<filename>/dev/tun0</filename>).  References to
 	  <devicename>tun0</devicename> below may be changed to
 	  <devicename>tun<replaceable>N</replaceable></devicename>
 	  where <replaceable>N</replaceable> is any unit number
 	  corresponding to your system.</para>
 
         <para>For FreeBSD installations that do not have &man.devfs.5; enabled
 	  (FreeBSD&nbsp;4.X and earlier), the existence of the
 	  <devicename>tun0</devicename> device should  be verified (this is not
 	  necessary if &man.devfs.5; is enabled as device nodes will be created
 	  on demand).</para>
 
 	<para>The easiest way to make sure that the
 	  <devicename>tun0</devicename> device is configured correctly
 	  is to remake the device.  To remake the device, do the
           following:</para>
 
 	<screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>sh MAKEDEV tun0</userinput></screen>
 
 	<para>If you need 16 tunnel devices in your kernel, you will need
 	  to create them.  This can be done by executing the following
 	  commands:</para>
 
 	<screen>&prompt.root; <userinput>cd /dev</userinput>
 &prompt.root; <userinput>sh MAKEDEV tun15</userinput></screen>
       </sect3>
 
       <sect3>
         <title>Automatic <application>PPP</application> Configuration</title>
 
 	<indexterm><primary>PPP</primary><secondary>configuration</secondary></indexterm>
 	<para>Both <command>ppp</command> and <command>pppd</command>
 	  (the kernel level implementation of PPP) use the configuration
 	  files located in the <filename>/etc/ppp</filename> directory.
           Examples for user ppp can be found in
           <filename>/usr/share/examples/ppp/</filename>.</para>
 
 	<para>Configuring <command>ppp</command> requires that you edit a
 	  number of files, depending on your requirements.  What you put
 	  in them depends to some extent on whether your ISP allocates IP
 	  addresses statically (i.e., you get given one IP address, and
 	  always use that one) or dynamically (i.e., your IP address
 	  changes each time you connect to your ISP).</para>
 
 	<sect4 id="userppp-staticIP">
 	  <title>PPP and Static IP Addresses</title>
 
 	  <indexterm><primary>PPP</primary><secondary>with static IP addresses</secondary></indexterm>
 	  <para>You will need to edit the
 	    <filename>/etc/ppp/ppp.conf</filename> configuration file.  It
             should look similar to the example below.</para>
 
 	  <note>
 	    <para>Lines that end in a <literal>:</literal> start in
 	      the first column (beginning of the line)&mdash; all other
 	      lines should be indented as shown using spaces or
 	      tabs.</para>
 	  </note>
 
 	  <programlisting>1     default:
 2       set log Phase Chat LCP IPCP CCP tun command
 3       ident user-ppp VERSION (built COMPILATIONDATE)
 4       set device /dev/cuaa0
 5       set speed 115200
 6       set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \
 7                 \"\" AT OK-AT-OK ATE1Q0 OK \\dATDT\\T TIMEOUT 40 CONNECT"
 8       set timeout 180
 9       enable dns
 10
 11    provider:
 12      set phone "(123) 456 7890"
 13      set authname foo
 14      set authkey bar
 15      set login "TIMEOUT 10 \"\" \"\" gin:--gin: \\U word: \\P col: ppp"
 16      set timeout 300
 17      set ifaddr <replaceable>x.x.x.x</replaceable> <replaceable>y.y.y.y</replaceable> 255.255.255.255 0.0.0.0
 18      add default HISADDR</programlisting>
 
 	  <variablelist>
 	    <varlistentry>
 	      <term>Line 1:</term>
 
 	      <listitem>
 		<para>Identifies the default entry.  Commands in this
 		  entry are executed automatically when ppp is run.</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>Line 2:</term>
 
 	      <listitem>
 		<para>Enables logging parameters.  When the configuration
 		  is working satisfactorily, this line should be reduced
                   to saying
 
 	          <programlisting>set log phase tun</programlisting>
 
                   in order to avoid excessive log file sizes.</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>Line 3:</term>
 
 	      <listitem>
 		<para>Tells PPP how to identify itself to the peer.
                   PPP identifies itself to the peer if it has any trouble
                   negotiating and setting up the link, providing information
                   that the peers administrator may find useful when
                   investigating such problems.</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>Line 4:</term>
 
 	      <listitem>
 		<para>Identifies the device to which the modem is
 		  connected.  <devicename>COM1</devicename> is
 		  <filename>/dev/cuaa0</filename> and
 		  <devicename>COM2</devicename> is
 		  <filename>/dev/cuaa1</filename>.</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>Line 5:</term>
 
 	      <listitem>
 		<para>Sets the speed you want to connect at.  If 115200
 		  does not work (it should with any reasonably new modem),
 		  try 38400 instead.</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>Line 6 &amp; 7:</term>
 
 	      <listitem>
-		<indexterm><primary>PPP</primary><secondary>user PPP</secondary></indexterm>
-
-		<para>The dial string.  User PPP uses an expect-send
+		<para>The dial string.  User PPP<indexterm><primary>PPP</primary><secondary>user PPP</secondary></indexterm> uses an expect-send
 		  syntax similar to the &man.chat.8; program.  Refer to
 		  the manual page for information on the features of this
 		  language.</para>
 
 		<para>Note that this command continues onto the next line
                    for readability.  Any command in
                    <filename>ppp.conf</filename> may do this if the last
                    character on the line is a ``\'' character.</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>Line 8:</term>
 
 	      <listitem>
 		<para>Sets the idle timeout for the link.  180 seconds
 		  is the default, so this line is purely cosmetic.</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>Line 9:</term>
 
 	      <listitem>
 		<para>Tells PPP to ask the peer to confirm the local
 		  resolver settings.  If you run a local name server, this
                   line should be commented out or removed.</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>Line 10:</term>
 
 	      <listitem>
 		<para>A blank line for readability.  Blank lines are ignored
 		by PPP.</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>Line 11:</term>
 
 	      <listitem>
 		<para>Identifies an entry for a provider called
 		  <quote>provider</quote>.  This could be changed
                     to the name of your <acronym>ISP</acronym> so
                     that later you can use the <option>load ISP</option>
                     to start the connection.</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>Line 12:</term>
 
 	      <listitem>
 		<para>Sets the phone number for this provider.  Multiple
 		  phone numbers may be specified using the colon
 		  (<literal>:</literal>) or pipe character
 		  (<literal>|</literal>)as a separator.  The difference
 		  between the two separators is described in &man.ppp.8;.
 		  To summarize, if you want to rotate through the numbers,
 		  use a colon.  If you want to always attempt to dial the
 		  first number first and only use the other numbers if the
 		  first number fails, use the pipe character.  Always
 		  quote the entire set of phone numbers as shown.</para>
 
 	      <para>You must enclose the phone number in quotation marks
 		(<literal>"</literal>) if there is any intention on using
 		spaces in the phone number.  This can cause a simple, yet
 		subtle error.</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>Line 13 &amp; 14:</term>
 
 	      <listitem>
 		<para>Identifies the user name and password.  When
                   connecting using a &unix; style login prompt, these
                   values are referred to by the <command>set
                   login</command> command using the \U and \P
                   variables.  When connecting using PAP or CHAP, these
                   values are used at authentication time.</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>Line 15:</term>
 
 	      <listitem>
-		<indexterm><primary>PAP</primary></indexterm>
-		<indexterm><primary>CHAP</primary></indexterm>
 		<para>If you are using PAP or CHAP, there will be no login
 		  at this point, and this line should be commented out or
-		  removed.  See <link linkend="userppp-PAPnCHAP">PAP and CHAP
+		  removed.  See <link linkend="userppp-PAPnCHAP">PAP<indexterm><primary>PAP</primary></indexterm> and CHAP<indexterm><primary>CHAP</primary></indexterm>
 		  authentication</link> for further details.</para>
 
                 <para>The login string is of the same chat-like syntax as
 		  the dial string.  In this example, the string works for
 		  a service whose login session looks like this:</para>
 
 		<screen>J. Random Provider
 login: <replaceable>foo</replaceable>
 password: <replaceable>bar</replaceable>
 protocol: ppp</screen>
 
 		<para>You will need to alter this script to suit your
 		  own needs.  When you write this script for the first
 		  time, you should ensure that you have enabled
 		  <quote>chat</quote> logging so you can determine if
 		  the conversation is going as expected.</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>Line 16:</term>
 
 	      <listitem>
-		<indexterm><primary>timeout</primary></indexterm>
-
-		<para>Sets the default idle timeout (in seconds) for the
+		<para>Sets the default idle timeout<indexterm><primary>timeout</primary></indexterm> (in seconds) for the
 		  connection.  Here, the connection will be closed
 		  automatically after 300 seconds of inactivity.  If you
 		  never want to timeout, set this value to zero or use
                   the <option>-ddial</option> command line switch.</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>Line 17:</term>
 	      <listitem>
-		<indexterm><primary>ISP</primary></indexterm>
-
 		<para>Sets the interface addresses.  The string
 		  <replaceable>x.x.x.x</replaceable> should be
 		  replaced by the IP address that your provider has
 		  allocated to you.  The string
 		  <replaceable>y.y.y.y</replaceable> should be
 		  replaced by the IP address that your ISP indicated
 		  for their gateway (the machine to which you
-		  connect).  If your ISP has not given you a gateway
+		  connect).  If your ISP<indexterm><primary>ISP</primary></indexterm> has not given you a gateway
 		  address, use <hostid
 		  role="netmask">10.0.0.2/0</hostid>.  If you need to
 		  use a <quote>guessed</quote> address, make sure that
 		  you create an entry in
 		  <filename>/etc/ppp/ppp.linkup</filename> as per the
 		  instructions for <link
 		  linkend="userppp-dynamicIP">PPP and Dynamic IP
 		  addresses</link>.  If this line is omitted,
 		  <command>ppp</command> cannot run in
 		  <option>-auto</option> mode.</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>Line 18:</term>
 
 	      <listitem>
 		<para>Adds a default route to your ISP's gateway.  The
 		  special word <literal>HISADDR</literal> is replaced with
 		  the gateway address specified on line 17.  It is
 		  important that this line appears after line 17,
 		  otherwise <literal>HISADDR</literal> will not yet be
 		  initialized.</para>
 
 		<para>If you do not wish to run ppp in <option>-auto</option>,
 		  this line should be moved to the
                   <filename>ppp.linkup</filename> file.</para>
 	      </listitem>
 	    </varlistentry>
 	  </variablelist>
 
 	  <para>It is not necessary to add an entry to
 	    <filename>ppp.linkup</filename> when you have a static IP
 	    address and are running ppp in <option>-auto</option> mode as your
             routing table entries are already correct before you connect.
             You may however wish to create an entry to invoke programs after
             connection.  This is explained later with the sendmail
             example.</para>
 
 	  <para>Example configuration files can be found in the
 	    <filename>/usr/share/examples/ppp/</filename> directory.</para>
 	</sect4>
 
 	<sect4 id="userppp-dynamicIP">
 	  <title>PPP and Dynamic IP Addresses</title>
 	  <indexterm><primary>PPP</primary><secondary>with dynamic IP addresses</secondary></indexterm>
 	  <indexterm><primary>IPCP</primary></indexterm>
 	  <para>If your service provider does not assign static IP
 	    addresses, <command>ppp</command> can be configured to
 	    negotiate the local and remote addresses.  This is done by
 	    <quote>guessing</quote> an IP address and allowing
 	    <command>ppp</command> to set it up correctly using the IP
 	    Configuration Protocol (IPCP) after connecting.  The
 	    <filename>ppp.conf</filename> configuration is the same as
 	    <link linkend="userppp-staticIP">PPP and Static IP
 	    Addresses</link>, with the following change:</para>
 
 	  <programlisting>17      set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255</programlisting>
 
 	  <para>Again, do not include the line number, it is just for
 	    reference.  Indentation of at least one space is
 	    required.</para>
 
 	  <variablelist>
 	    <varlistentry>
 	      <term>Line 17:</term>
 
 	      <listitem>
 		<para>The number after the <literal>/</literal> character
 		  is the number of bits of the address that ppp will
 		  insist on.  You may wish to use IP numbers more
 		  appropriate to your circumstances, but the above example
 		  will always work.</para>
 
 		<para>The last argument (<literal>0.0.0.0</literal>) tells
 		  PPP to start negotiations using address <hostid
 		  role="ipaddr">0.0.0.0</hostid> rather than <hostid
 		  role="ipaddr">10.0.0.1</hostid> and is necessary for some
                   ISPs.  Do not use <literal>0.0.0.0</literal> as the first
                   argument to <command>set ifaddr</command> as it prevents
                   PPP from setting up an initial route in
                   <option>-auto</option> mode.</para>
 	      </listitem>
 	    </varlistentry>
 	  </variablelist>
 
 	  <para>If you are not running in <option>-auto</option> mode, you
 	    will need to create an entry in
             <filename>/etc/ppp/ppp.linkup</filename>.
 	    <filename>ppp.linkup</filename> is used after a connection has
 	    been established.  At this point, <command>ppp</command> will
 	    have assigned the interface addresses and it will now be
 	    possible to add the routing table entries:</para>
 
 	  <programlisting>1     provider:
 2      add default HISADDR</programlisting>
 
 	  <variablelist>
 	    <varlistentry>
 	      <term>Line 1:</term>
 
 	      <listitem>
 		<para>On establishing a connection,
 		  <command>ppp</command> will look for an entry in
 		  <filename>ppp.linkup</filename> according to the
 		  following rules: First, try to match the same label
 		  as we used in <filename>ppp.conf</filename>.  If
 		  that fails, look for an entry for the IP address of
 		  our gateway.  This entry is a four-octet IP style
 		  label.  If we still have not found an entry, look
 		  for the <literal>MYADDR</literal> entry.</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>Line 2:</term>
 
 	      <listitem>
 		<para>This line tells <command>ppp</command> to add a
 		  default route that points to
 		  <literal>HISADDR</literal>.
 		  <literal>HISADDR</literal> will be replaced with the
 		  IP number of the gateway as negotiated by the
 		  IPCP.</para>
 	      </listitem>
 	    </varlistentry>
 	  </variablelist>
 
 	  <para>See the <literal>pmdemand</literal> entry in the files
 	    <filename>/usr/share/examples/ppp/ppp.conf.sample</filename>
 	    and
 	    <filename>/usr/share/examples/ppp/ppp.linkup.sample</filename>
 	    for a detailed example.</para>
 	</sect4>
 
 	<sect4>
 	  <title>Receiving Incoming Calls</title>
 	  <indexterm><primary>PPP</primary><secondary>receiving
 	  incoming calls</secondary></indexterm>
 	  <para>When you configure <application>ppp</application> to
 	    receive incoming calls on a machine connected to a LAN, you
 	    must decide if you wish to forward packets to the LAN.  If you
 	    do, you should allocate the peer an IP number from your LAN's
 	    subnet, and use the command <command>enable proxy</command> in
 	    your <filename>/etc/ppp/ppp.conf</filename> file.  You should
 	    also confirm that the <filename>/etc/rc.conf</filename> file
 	    contains the following:</para>
 
 	  <programlisting>gateway_enable="YES"</programlisting>
 	</sect4>
 
 	  <sect4>
 	    <title>Which getty?</title>
 
 	    <para><link linkend="dialup">Configuring FreeBSD for Dial-up
 	      Services</link> provides a good description on enabling
 	      dial-up services using &man.getty.8;.</para>
 
 	    <para>An alternative to <command>getty</command> is <ulink
 	      url="http://www.leo.org/~doering/mgetty/index.html">mgetty</ulink>,
 	      a smarter version of <command>getty</command> designed
 	      with dial-up lines in mind.</para>
 
 	    <para>The advantages of using <command>mgetty</command> is
 	      that it actively <emphasis>talks</emphasis> to modems,
 	      meaning if port is turned off in
 	      <filename>/etc/ttys</filename> then your modem will not answer
 	      the phone.</para>
 
 	    <para>Later versions of <command>mgetty</command> (from
 	      0.99beta onwards) also support the automatic detection of
 	      PPP streams, allowing your clients script-less access to
 	      your server.</para>
 
 	    <para>Refer to <link linkend="userppp-mgetty">Mgetty and
 	      AutoPPP</link> for more information on
 	      <command>mgetty</command>.</para>
 	  </sect4>
 
 	  <sect4>
 	    <title><application>PPP</application> Permissions</title>
 
 	    <para>The <command>ppp</command> command must normally be
 	      run as the <username>root</username> user.  If however,
 	      you wish to allow <command>ppp</command> to run in
 	      server mode as a normal user by executing
 	      <command>ppp</command> as described below, that user
 	      must be given permission to run <command>ppp</command>
 	      by adding them to the <username>network</username> group
 	      in <filename>/etc/group</filename>.</para>
 
 	    <para>You will also need to give them access to one or more
 	      sections of the configuration file using the
 	      <command>allow</command> command:</para>
 
 	    <programlisting>allow users fred mary</programlisting>
 
 	    <para>If this command is used in the <literal>default</literal>
 	      section, it gives the specified users access to
 	      everything.</para>
 	  </sect4>
 
 	  <sect4>
 	    <title>PPP Shells for Dynamic-IP Users</title>
 	    <indexterm><primary>PPP shells</primary></indexterm>
 
 	    <para>Create a file called
 	      <filename>/etc/ppp/ppp-shell</filename> containing the
 	      following:</para>
 
 	    <programlisting>#!/bin/sh
 IDENT=`echo $0 | sed -e 's/^.*-\(.*\)$/\1/'`
 CALLEDAS="$IDENT"
 TTY=`tty`
 
 if [ x$IDENT = xdialup ]; then
         IDENT=`basename $TTY`
 fi
 
 echo "PPP for $CALLEDAS on $TTY"
 echo "Starting PPP for $IDENT"
 
 exec /usr/sbin/ppp -direct $IDENT</programlisting>
 
 	    <para>This script should be executable.  Now make a symbolic
 	      link called <filename>ppp-dialup</filename> to this script
 	      using the following commands:</para>
 
 	    <screen>&prompt.root; <userinput>ln -s ppp-shell /etc/ppp/ppp-dialup</userinput></screen>
 
 	    <para>You should use this script as the
 	      <emphasis>shell</emphasis> for all of your dialup users.
 	      This is an example from <filename>/etc/passwd</filename>
 	      for a dialup PPP user with username
 	      <username>pchilds</username> (remember do not directly edit
 	      the password file, use &man.vipw.8;).</para>
 
 	    <programlisting>pchilds:*:1011:300:Peter Childs PPP:/home/ppp:/etc/ppp/ppp-dialup</programlisting>
 
 	    <para>Create a <filename>/home/ppp</filename> directory that
 	      is world readable containing the following 0 byte
 	      files:</para>
 
 	    <screen>-r--r--r--   1 root     wheel           0 May 27 02:23 .hushlogin
 -r--r--r--   1 root     wheel           0 May 27 02:22 .rhosts</screen>
 
 	    <para>which prevents <filename>/etc/motd</filename> from being
 	      displayed.</para>
 	  </sect4>
 
 	  <sect4>
 	    <title>PPP Shells for Static-IP Users</title>
 	    <indexterm><primary>PPP shells</primary></indexterm>
 
 	    <para>Create the <filename>ppp-shell</filename> file as above,
 	      and for each account with statically assigned IPs create a
 	      symbolic link to <filename>ppp-shell</filename>.</para>
 
 	    <para>For example, if you have three dialup customers,
 	      <username>fred</username>, <username>sam</username>, and
 	      <username>mary</username>, that you route class C networks
 	      for, you would type the following:</para>
 
 	    <screen>&prompt.root; <userinput>ln -s /etc/ppp/ppp-shell /etc/ppp/ppp-fred</userinput>
 &prompt.root; <userinput>ln -s /etc/ppp/ppp-shell /etc/ppp/ppp-sam</userinput>
 &prompt.root; <userinput>ln -s /etc/ppp/ppp-shell /etc/ppp/ppp-mary</userinput></screen>
 
 	    <para>Each of these users dialup accounts should have their
 	      shell set to the symbolic link created above (for example,
 	      <username>mary</username>'s shell should be
 	      <filename>/etc/ppp/ppp-mary</filename>).</para>
 	  </sect4>
 
 	  <sect4>
 	    <title>Setting Up <filename>ppp.conf</filename> for Dynamic-IP Users</title>
 
 	    <para>The <filename>/etc/ppp/ppp.conf</filename> file should
 	      contain something along the lines of:</para>
 
 	    <programlisting>default:
   set debug phase lcp chat
   set timeout 0
 
 ttyd0:
   set ifaddr 203.14.100.1 203.14.100.20 255.255.255.255
   enable proxy
 
 ttyd1:
   set ifaddr 203.14.100.1 203.14.100.21 255.255.255.255
   enable proxy</programlisting>
 
 	    <note>
 	      <para>The indenting is important.</para>
 	    </note>
 
 	    <para>The <literal>default:</literal> section is loaded for
 	      each session.  For each dialup line enabled in
 	      <filename>/etc/ttys</filename> create an entry similar to
 	      the one for <literal>ttyd0:</literal> above.  Each line
 	      should get a unique IP address from your pool of IP
 	      addresses for dynamic users.</para>
 	  </sect4>
 
 	  <sect4>
 	    <title>Setting Up <filename>ppp.conf</filename> for Static-IP
 	      Users</title>
 
 	    <para>Along with the contents of the sample
 	      <filename>/usr/share/examples/ppp/ppp.conf</filename>
 	      above you should add a section for each of the
 	      statically assigned dialup users.  We will continue with
 	      our <username>fred</username>, <username>sam</username>,
 	      and <username>mary</username> example.</para>
 
 	    <programlisting>fred:
   set ifaddr 203.14.100.1 203.14.101.1 255.255.255.255
 
 sam:
   set ifaddr 203.14.100.1 203.14.102.1 255.255.255.255
 
 mary:
   set ifaddr 203.14.100.1 203.14.103.1 255.255.255.255</programlisting>
 
 	    <para>The file <filename>/etc/ppp/ppp.linkup</filename>
 	      should also contain routing information for each static
 	      IP user if required.  The line below would add a route
 	      for the <hostid role="ipaddr">203.14.101.0</hostid>
 	      class C via the client's ppp link.</para>
 
 	    <programlisting>fred:
   add 203.14.101.0 netmask 255.255.255.0 HISADDR
 
 sam:
   add 203.14.102.0 netmask 255.255.255.0 HISADDR
 
 mary:
   add 203.14.103.0 netmask 255.255.255.0 HISADDR</programlisting>
 	</sect4>
 
 	  <sect4 id="userppp-mgetty">
 	    <title><command>mgetty</command> and AutoPPP</title>
 	    <indexterm>
         <primary><command>mgetty</command></primary>
       </indexterm>
 	    <indexterm><primary>AutoPPP</primary></indexterm>
 	    <indexterm><primary>LCP</primary></indexterm>
 
 	    <para>Configuring and compiling <command>mgetty</command>
 	      with the <literal>AUTO_PPP</literal> option enabled
 	      allows <command>mgetty</command> to detect the LCP phase
 	      of PPP connections and automatically spawn off a ppp
 	      shell.  However, since the default login/password
 	      sequence does not occur it is necessary to authenticate
 	      users using either PAP or CHAP.</para>
 
 	    <para>This section assumes the user has successfully
 	      configured, compiled, and installed a version of
 	      <command>mgetty</command> with the
 	      <literal>AUTO_PPP</literal> option (v0.99beta or
 	      later).</para>
 
 	    <para>Make sure your
 	      <filename>/usr/local/etc/mgetty+sendfax/login.config</filename>
 	      file has the following in it:</para>
 
 	    <programlisting>/AutoPPP/ -     -		      /etc/ppp/ppp-pap-dialup</programlisting>
 
 	    <para>This will tell <command>mgetty</command> to run the
 	      <filename>ppp-pap-dialup</filename> script for detected
 	      PPP connections.</para>
 
 	    <para>Create a file called
 	      <filename>/etc/ppp/ppp-pap-dialup</filename> containing the
 	      following (the file should be executable):</para>
 
 	    <programlisting>#!/bin/sh
 exec /usr/sbin/ppp -direct pap$IDENT</programlisting>
 
 	    <para>For each dialup line enabled in
 	      <filename>/etc/ttys</filename>, create a corresponding entry
 	      in <filename>/etc/ppp/ppp.conf</filename>.  This will
 	      happily co-exist with the definitions we created
 	      above.</para>
 
 	    <programlisting>pap:
   enable pap
   set ifaddr 203.14.100.1 203.14.100.20-203.14.100.40
   enable proxy</programlisting>
 
 	    <para>Each user logging in with this method will need to have
 	      a username/password in
 	      <filename>/etc/ppp/ppp.secret</filename> file, or
 	      alternatively add the following option to authenticate users
 	      via PAP from the <filename>/etc/passwd</filename> file.</para>
 
 	    <programlisting>enable passwdauth</programlisting>
 
 	    <para>If you wish to assign some users a static IP number,
 	      you can specify the number as the third argument in
 	      <filename>/etc/ppp/ppp.secret</filename>.  See
 	      <filename>/usr/share/examples/ppp/ppp.secret.sample</filename>
 	      for examples.</para>
 	  </sect4>
 
 	  <sect4>
 	    <title>MS Extensions</title>
 	    <indexterm><primary>DNS</primary></indexterm>
 	    <indexterm><primary>NetBIOS</primary></indexterm>
 	    <indexterm><primary>PPP</primary><secondary>Microsoft extensions</secondary></indexterm>
 	    <para>It is possible to configure PPP to supply DNS and
 	      NetBIOS nameserver addresses on demand.</para>
 
 	    <para>To enable these extensions with PPP version 1.x, the
 	      following lines might be added to the relevant section of
 	      <filename>/etc/ppp/ppp.conf</filename>.</para>
 
 	    <programlisting>enable msext
 set ns 203.14.100.1 203.14.100.2
 set nbns 203.14.100.5</programlisting>
 
 	    <para>And for PPP version 2 and above:</para>
 
 	    <programlisting>accept dns
 set dns 203.14.100.1 203.14.100.2
 set nbns 203.14.100.5</programlisting>
 
 	    <para>This will tell the clients the primary and secondary
 	      name server addresses, and a NetBIOS nameserver host.</para>
 
 	    <para>In version 2 and above, if the
 	      <literal>set dns</literal> line is omitted, PPP will use the
 	      values found in <filename>/etc/resolv.conf</filename>.</para>
 	</sect4>
 
         <sect4 id="userppp-PAPnCHAP">
 	  <title>PAP and CHAP Authentication</title>
 	  <indexterm><primary>PAP</primary></indexterm>
 	  <indexterm><primary>CHAP</primary></indexterm>
 	  <para>Some ISPs set their system up so that the authentication
 	    part of your connection is done using either of the PAP or
 	    CHAP authentication mechanisms.  If this is the case, your ISP
 	    will not give a <prompt>login:</prompt> prompt when you
 	    connect, but will start talking PPP immediately.</para>
 
 	  <para>PAP is less secure than CHAP, but security is not normally
 	    an issue here as passwords, although being sent as plain text
 	    with PAP, are being transmitted down a serial line only.
 	    There is not much room for crackers to
 	    <quote>eavesdrop</quote>.</para>
 
 	  <para>Referring back to the <link linkend="userppp-staticIP">PPP
 	    and Static IP addresses</link> or <link
 	    linkend="userppp-dynamicIP">PPP and Dynamic IP addresses</link>
 	    sections, the following alterations must be made:</para>
 
 	  <programlisting>13      set authname <replaceable>MyUserName</replaceable>
 14      set authkey <replaceable>MyPassword</replaceable>
 15      set login</programlisting>
 
 	  <variablelist>
 	    <varlistentry>
 	      <term>Line 13:</term>
 
 	      <listitem>
 		<para>This line specifies your PAP/CHAP user name.  You
 		  will need to insert the correct value for
 		  <replaceable>MyUserName</replaceable>.</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>Line 14:</term>
 	      <listitem>
-		<indexterm><primary>password</primary></indexterm>
-
-		<para>This line specifies your PAP/CHAP password.  You
+		<para>This line specifies your PAP/CHAP password<indexterm><primary>password</primary></indexterm>.  You
 		  will need to insert the correct value for
 		  <replaceable>MyPassword</replaceable>.  You may want to
 		  add an additional line, such as:</para>
 
 		<programlisting>16      accept PAP</programlisting>
 
 		<para>or</para>
 
 		<programlisting>16      accept CHAP</programlisting>
 
 		<para>to make it obvious that this is the intention, but
 		  PAP and CHAP are both accepted by default.</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term>Line 15:</term>
 
 	      <listitem>
 		<para>Your ISP will not normally require that you log into
 		  the server if you are using PAP or CHAP.  You must
 		  therefore disable your <quote>set login</quote>
 		  string.</para>
 	      </listitem>
 	    </varlistentry>
 	  </variablelist>
 	</sect4>
 
 	<sect4>
 	  <title>Changing Your <command>ppp</command> Configuration on the
 	    Fly</title>
 
 	  <para>It is possible to talk to the <command>ppp</command>
 	    program while it is running in the background, but only if a
 	    suitable diagnostic port has been set up.  To do this, add the
 	    following line to your configuration:</para>
 
 	  <programlisting>set server /var/run/ppp-tun<replaceable>%d</replaceable> DiagnosticPassword 0177</programlisting>
 
 	  <para>This will tell PPP to listen to the specified
 	    &unix; domain socket, asking clients for the specified
 	    password before allowing access.  The
 	    <literal>%d</literal> in the name is replaced with the
 	    <devicename>tun</devicename> device number that is in
 	    use.</para>
 
 	  <para>Once a socket has been set up, the &man.pppctl.8;
 	    program may be used in scripts that wish to manipulate the
 	    running program.</para>
 	</sect4>
       </sect3>
 
       <sect3 id="userppp-nat">
        <title>Using PPP Network Address Translation Capability</title>
        <indexterm><primary>PPP</primary><secondary>NAT</secondary></indexterm>
 
        <para>PPP has ability to use internal NAT without kernel diverting
          capabilities. This functionality may be enabled by the following
          line in <filename>/etc/ppp/ppp.conf</filename>:</para>
 
        <programlisting>nat enable yes</programlisting>
 
        <para>Alternatively, PPP NAT may be enabled by command-line
          option <literal>-nat</literal>. There is also
          <filename>/etc/rc.conf</filename> knob named
          <literal>ppp_nat</literal>, which is enabled by default.</para>
 
        <para>If you use this feature, you may also find useful
          the following <filename>/etc/ppp/ppp.conf</filename> options
          to enable incoming connections forwarding:</para>
 
        <programlisting>nat port tcp 10.0.0.2:ftp ftp
 nat port tcp 10.0.0.2:http http</programlisting>
 
        <para>or do not trust the outside at all</para>
 
        <programlisting>nat deny_incoming yes</programlisting>
       </sect3>
 
       <sect3 id="userppp-final">
 	<title>Final System Configuration</title>
 	<indexterm><primary>PPP</primary><secondary>configuration</secondary></indexterm>
 
 	<para>You now have <command>ppp</command> configured, but there
 	  are a few more things to do before it is ready to work.  They
 	  all involve editing the <filename>/etc/rc.conf</filename>
 	  file.</para>
 
 	<para>Working from the top down in this file, make sure the
 	  <literal>hostname=</literal> line is set, e.g.:</para>
 
 	<programlisting>hostname="foo.example.com"</programlisting>
 
 	<para>If your ISP has supplied you with a static IP address and
 	  name, it is probably best that you use this name as your host
 	  name.</para>
 
 	<para>Look for the <literal>network_interfaces</literal> variable.
 	  If you want to configure your system to dial your ISP on demand,
 	  make sure the <devicename>tun0</devicename> device is added to
 	  the list, otherwise remove it.</para>
 
 	<programlisting>network_interfaces="lo0 tun0"
 ifconfig_tun0=</programlisting>
 
 	<note>
 	  <para>The <literal>ifconfig_tun0</literal> variable should be
 	    empty, and a file called
 	    <filename>/etc/start_if.tun0</filename> should be created.
 	    This file should contain the line:</para>
 
 	  <programlisting>ppp -auto mysystem</programlisting>
 
 	  <para>This script is executed at network configuration time,
 	    starting your ppp daemon in automatic mode.  If you have a LAN
 	    for which this machine is a gateway, you may also wish to use
 	    the <option>-alias</option> switch.  Refer to the manual page
 	    for further details.</para>
 	</note>
 
 	<para>Make sure that the router program is set to <literal>NO</literal> with
 	  the following line in your
 	  <filename>/etc/rc.conf</filename>:</para>
 
 	<programlisting>router_enable="NO"</programlisting>
 
 	<indexterm>
     <primary><application>routed</application></primary>
   </indexterm>
 	<para>It is important that the <command>routed</command> daemon is
 	  not started, as
 	  <command>routed</command> tends to delete the default routing
 	  table entries created by <command>ppp</command>.</para>
 
 	<para>It is probably worth your while ensuring that the
 	  <literal>sendmail_flags</literal> line does not include the
 	  <option>-q</option> option, otherwise
 	  <command>sendmail</command> will attempt to do a network lookup
 	  every now and then, possibly causing your machine to dial out.
 	  You may try:</para>
 
 	<programlisting>sendmail_flags="-bd"</programlisting>
 
 	<indexterm>
     <primary><application>sendmail</application></primary>
   </indexterm>
 	<para>The downside of this is that you must force
 	  <command>sendmail</command> to re-examine the mail queue
 	  whenever the ppp link is up by typing:</para>
 
 	<screen>&prompt.root; <userinput>/usr/sbin/sendmail -q</userinput></screen>
 
 	<para>You may wish to use the <command>!bg</command> command in
 	  <filename>ppp.linkup</filename> to do this automatically:</para>
 
 	<programlisting>1     provider:
 2       delete ALL
 3       add 0 0 HISADDR
 4       !bg sendmail -bd -q30m</programlisting>
 
         <indexterm><primary>SMTP</primary></indexterm>
 	<para>If you do not like this, it is possible to set up a
 	  <quote>dfilter</quote> to block SMTP traffic.  Refer to the
 	  sample files for further details.</para>
 
 	<para>All that is left is to reboot the machine.  After rebooting,
 	  you can now either type:</para>
 
 	<screen>&prompt.root; <userinput>ppp</userinput></screen>
 
 	<para>and then <command>dial provider</command> to start the PPP
 	  session, or, if you want <command>ppp</command> to establish
 	  sessions automatically when there is outbound traffic (and
 	  you have not created the <filename>start_if.tun0</filename>
 	  script), type:</para>
 
 	<screen>&prompt.root; <userinput>ppp -auto provider</userinput></screen>
       </sect3>
 
       <sect3>
 	<title>Summary</title>
 
 	<para>To recap, the following steps are necessary when setting up
 	  ppp for the first time:</para>
 
 	<para>Client side:</para>
 
 	<procedure>
 	  <step>
 	    <para>Ensure that the <devicename>tun</devicename> device is
 	      built into your kernel.</para>
 	  </step>
 
 	  <step>
 	    <para>Ensure that the
 	      <filename>tun<replaceable>N</replaceable></filename> device
 	      file is available in the <filename>/dev</filename>
 	      directory.</para>
 	  </step>
 
 	  <step>
 	    <para>Create an entry in
 	      <filename>/etc/ppp/ppp.conf</filename>.  The
 	      <filename>pmdemand</filename> example should suffice for
 	      most ISPs.</para>
 	  </step>
 
 	  <step>
 	    <para>If you have a dynamic IP address, create an entry in
 	      <filename>/etc/ppp/ppp.linkup</filename>.</para>
 	  </step>
 
 	  <step>
 	    <para>Update your <filename>/etc/rc.conf</filename>
 	      file.</para>
 	  </step>
 
 	  <step>
 	    <para>Create a <filename>start_if.tun0</filename> script if
 	      you require demand dialing.</para>
 	  </step>
 	</procedure>
 
 	<para>Server side:</para>
 
 	<procedure>
 	  <step>
 	    <para>Ensure that the <devicename>tun</devicename> device is
 	      built into your kernel.</para>
 	  </step>
 
 	  <step>
 	    <para>Ensure that the
 	      <filename>tun<replaceable>N</replaceable></filename> device
 	      file is available in the <filename>/dev</filename>
 	      directory.</para>
 	  </step>
 
 	  <step>
 	    <para>Create an entry in <filename>/etc/passwd</filename>
 	      (using the &man.vipw.8; program).</para>
 	  </step>
 
 	  <step>
 	    <para>Create a profile in this users home directory that runs
 	      <command>ppp -direct direct-server</command> or
 	      similar.</para>
 	  </step>
 
 	  <step>
 	    <para>Create an entry in
 	      <filename>/etc/ppp/ppp.conf</filename>.  The
 	      <filename>direct-server</filename> example should
 	      suffice.</para>
 	  </step>
 
 	  <step>
 	    <para>Create an entry in
 	      <filename>/etc/ppp/ppp.linkup</filename>.</para>
 	  </step>
 
 	  <step>
 	    <para>Update your <filename>/etc/rc.conf</filename>
 	      file.</para>
 	  </step>
 	</procedure>
       </sect3>
     </sect2>
   </sect1>
 
   <sect1 id="ppp">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Gennady B.</firstname>
           <surname>Sorokopud</surname>
           <contrib>Parts originally contributed by </contrib>
         </author>
         <author>
           <firstname>Robert</firstname>
           <surname>Huff</surname>
         </author>
       </authorgroup>
     </sect1info>
 
     <title>Using Kernel PPP</title>
 
     <sect2>
       <title>Setting Up Kernel PPP</title>
       <indexterm><primary>PPP</primary><secondary>kernel PPP</secondary></indexterm>
 
       <para>Before you start setting up PPP on your machine, make sure
 	that <command>pppd</command> is located in
 	<filename>/usr/sbin</filename> and the directory
 	<filename>/etc/ppp</filename> exists.</para>
 
       <para><command>pppd</command> can work in two modes:</para>
 
       <orderedlist>
 	<listitem>
 	  <para>As a <quote>client</quote> &mdash; you want to connect your
 	    machine to the outside world via a PPP serial connection or
 	    modem line.</para>
 	</listitem>
 
 	<listitem>
-	  <indexterm><primary>PPP</primary><secondary>server</secondary></indexterm>
-
-	  <para>As a <quote>server</quote> &mdash; your machine is located on
+	  <para>As a <quote>server</quote><indexterm><primary>PPP</primary><secondary>server</secondary></indexterm> &mdash; your machine is located on
 	    the network, and is used to connect other computers using
 	    PPP.</para>
 	</listitem>
       </orderedlist>
 
       <para>In both cases you will need to set up an options file
         (<filename>/etc/ppp/options</filename> or
 	<filename>~/.ppprc</filename> if you have more than one user on
 	your machine that uses PPP).</para>
 
       <para>You will also need some modem/serial software (preferably
 	<filename role="package">comms/kermit</filename>), so you can dial and
 	establish a connection with the remote host.</para>
     </sect2>
 
     <sect2>
       <sect2info>
 	<authorgroup>
 	  <author>
 	    <firstname>Trev</firstname>
 	    <surname>Roydhouse</surname>
 	    <contrib>Based on information provided by </contrib>
 	    <!-- Trev.Roydhouse@f401.n711.z3.fidonet.org -->
 	  </author>
 	</authorgroup>
       </sect2info>
 
       <title>Using <command>pppd</command> as a Client</title>
       <indexterm><primary>PPP</primary><secondary>client</secondary></indexterm>
       <indexterm><primary>Cisco</primary></indexterm>
       <para>The following <filename>/etc/ppp/options</filename> might be
         used to connect to a Cisco terminal server PPP line.</para>
 
       <programlisting>crtscts         # enable hardware flow control
 modem           # modem control line
 noipdefault     # remote PPP server must supply your IP address
                 # if the remote host does not send your IP during IPCP
                 # negotiation, remove this option
 passive         # wait for LCP packets
 domain ppp.foo.com      # put your domain name here
 
 :&lt;remote_ip&gt;    # put the IP of remote PPP host here
                 # it will be used to route packets via PPP link
                 # if you didn't specified the noipdefault option
                 # change this line to &lt;local_ip&gt;:&lt;remote_ip&gt;
 
 defaultroute    # put this if you want that PPP server will be your
                 # default router</programlisting>
 
       <para>To connect:</para>
 
       <indexterm><primary>Kermit</primary></indexterm>
       <indexterm><primary>modem</primary></indexterm>
       <procedure>
 	<step>
 	  <para>Dial to the remote host using <application>Kermit</application> (or some other modem
 	    program), and enter your user name and password (or whatever
 	    is needed to enable PPP on the remote host).</para>
 	</step>
 
 	<step>
 	  <para>Exit <application>Kermit</application> (without
 	  hanging up the line).</para>
 	</step>
 
 	<step>
 	  <para>Enter the following:</para>
 
 	  <screen>&prompt.root; <userinput>/usr/src/usr.sbin/pppd.new/pppd <replaceable>/dev/tty01</replaceable> <replaceable>19200</replaceable></userinput></screen>
 
 	  <para>Be sure to use the appropriate speed and device name.</para>
 	</step>
       </procedure>
 
       <para>Now your computer is connected with PPP.  If the connection
 	fails, you can add the <option>debug</option> option to the
 	<filename>/etc/ppp/options</filename> file, and check console messages
 	to track the problem.</para>
 
       <para>Following <filename>/etc/ppp/pppup</filename> script will make
 	all 3 stages automatic:</para>
 
       <programlisting>#!/bin/sh
 ps ax |grep pppd |grep -v grep
 pid=`ps ax |grep pppd |grep -v grep|awk '{print $1;}'`
 if [ "X${pid}" != "X" ] ; then
         echo 'killing pppd, PID=' ${pid}
         kill ${pid}
 fi
 ps ax |grep kermit |grep -v grep
 pid=`ps ax |grep kermit |grep -v grep|awk '{print $1;}'`
 if [ "X${pid}" != "X" ] ; then
         echo 'killing kermit, PID=' ${pid}
         kill -9 ${pid}
 fi
 
 ifconfig ppp0 down
 ifconfig ppp0 delete
 
 kermit -y /etc/ppp/kermit.dial
 pppd /dev/tty01 19200</programlisting>
 
       <indexterm><primary>Kermit</primary></indexterm>
       <para><filename>/etc/ppp/kermit.dial</filename> is a <application>Kermit</application>
       script that dials and makes all necessary authorization on the
       remote host (an example of such a script is attached to the end
       of this document).</para>
 
       <para>Use the following <filename>/etc/ppp/pppdown</filename> script
         to disconnect the PPP line:</para>
 
       <programlisting>#!/bin/sh
 pid=`ps ax |grep pppd |grep -v grep|awk '{print $1;}'`
 if [ X${pid} != "X" ] ; then
         echo 'killing pppd, PID=' ${pid}
         kill -TERM ${pid}
 fi
 
 ps ax |grep kermit |grep -v grep
 pid=`ps ax |grep kermit |grep -v grep|awk '{print $1;}'`
 if [ "X${pid}" != "X" ] ; then
         echo 'killing kermit, PID=' ${pid}
         kill -9 ${pid}
 fi
 
 /sbin/ifconfig ppp0 down
 /sbin/ifconfig ppp0 delete
 kermit -y /etc/ppp/kermit.hup
 /etc/ppp/ppptest</programlisting>
 
       <para>Check to see if <command>pppd</command> is still running by executing
 	<filename>/usr/etc/ppp/ppptest</filename>, which should look like
 	this:</para>
 
       <programlisting>#!/bin/sh
 pid=`ps ax| grep pppd |grep -v grep|awk '{print $1;}'`
 if [ X${pid} != "X" ] ; then
         echo 'pppd running: PID=' ${pid-NONE}
 else
         echo 'No pppd running.'
 fi
 set -x
 netstat -n -I ppp0
 ifconfig ppp0</programlisting>
 
       <para>To hang up the modem, execute
 	<filename>/etc/ppp/kermit.hup</filename>, which should
 	contain:</para>
 
       <programlisting>set line /dev/tty01	; put your modem device here
 set speed 19200
 set file type binary
 set file names literal
 set win 8
 set rec pack 1024
 set send pack 1024
 set block 3
 set term bytesize 8
 set command bytesize 8
 set flow none
 
 pau 1
 out +++
 inp 5 OK
 out ATH0\13
 echo \13
 exit</programlisting>
 
       <para>Here is an alternate method using <command>chat</command>
 	instead of <command>kermit</command>:</para>
 
       <para>The following two files are sufficient to accomplish a
 	<command>pppd</command>	connection.</para>
 
       <para><filename>/etc/ppp/options</filename>:</para>
 
       <programlisting>/dev/cuaa1 115200
 
 crtscts		# enable hardware flow control
 modem		# modem control line
 connect "/usr/bin/chat -f /etc/ppp/login.chat.script"
 noipdefault	# remote PPP serve must supply your IP address
 	        # if the remote host doesn't send your IP during
                 # IPCP negotiation, remove this option
 passive         # wait for LCP packets
 domain &lt;your.domain&gt;	# put your domain name here
 
 :		# put the IP of remote PPP host here
 	        # it will be used to route packets via PPP link
                 # if you didn't specified the noipdefault option
                 # change this line to &lt;local_ip&gt;:&lt;remote_ip&gt;
 
 defaultroute	# put this if you want that PPP server will be
 	        # your default router</programlisting>
 
       <para><filename>/etc/ppp/login.chat.script</filename>:</para>
 
       <note>
 	<para>The following should go on a single line.</para>
       </note>
 
       <programlisting>ABORT BUSY ABORT 'NO CARRIER' "" AT OK ATDT&lt;phone.number&gt;
   CONNECT "" TIMEOUT 10 ogin:-\\r-ogin: &lt;login-id&gt;
   TIMEOUT 5 sword: &lt;password&gt;</programlisting>
 
       <para>Once these are installed and modified correctly, all you need
 	to do is run <command>pppd</command>, like so:</para>
 
       <screen>&prompt.root; <userinput>pppd</userinput></screen>
     </sect2>
 
     <sect2>
       <title>Using <command>pppd</command> as a Server</title>
 
       <para><filename>/etc/ppp/options</filename> should contain something
 	similar to the following:</para>
 
       <programlisting>crtscts                         # Hardware flow control
 netmask 255.255.255.0           # netmask (not required)
 192.114.208.20:192.114.208.165  # IP's of local and remote hosts
                                 # local ip must be different from one
                                 # you assigned to the Ethernet (or other)
                                 # interface on your machine.
                                 # remote IP is IP address that will be
                                 # assigned to the remote machine
 domain ppp.foo.com              # your domain
 passive                         # wait for LCP
 modem                           # modem line</programlisting>
 
       <para>The following <filename>/etc/ppp/pppserv</filename> script
 	will tell <application>pppd</application> to behave as a
 	server:</para>
 
       <programlisting>#!/bin/sh
 ps ax |grep pppd |grep -v grep
 pid=`ps ax |grep pppd |grep -v grep|awk '{print $1;}'`
 if [ "X${pid}" != "X" ] ; then
         echo 'killing pppd, PID=' ${pid}
         kill ${pid}
 fi
 ps ax |grep kermit |grep -v grep
 pid=`ps ax |grep kermit |grep -v grep|awk '{print $1;}'`
 if [ "X${pid}" != "X" ] ; then
         echo 'killing kermit, PID=' ${pid}
         kill -9 ${pid}
 fi
 
 # reset ppp interface
 ifconfig ppp0 down
 ifconfig ppp0 delete
 
 # enable autoanswer mode
 kermit -y /etc/ppp/kermit.ans
 
 # run ppp
 pppd /dev/tty01 19200</programlisting>
 
       <para>Use this <filename>/etc/ppp/pppservdown</filename> script to
 	stop the server:</para>
 
       <programlisting>#!/bin/sh
 ps ax |grep pppd |grep -v grep
 pid=`ps ax |grep pppd |grep -v grep|awk '{print $1;}'`
 if [ "X${pid}" != "X" ] ; then
         echo 'killing pppd, PID=' ${pid}
         kill ${pid}
 fi
 ps ax |grep kermit |grep -v grep
 pid=`ps ax |grep kermit |grep -v grep|awk '{print $1;}'`
 if [ "X${pid}" != "X" ] ; then
         echo 'killing kermit, PID=' ${pid}
         kill -9 ${pid}
 fi
 ifconfig ppp0 down
 ifconfig ppp0 delete
 
 kermit -y /etc/ppp/kermit.noans</programlisting>
 
       <para>The following <application>Kermit</application> script
 	(<filename>/etc/ppp/kermit.ans</filename>) will enable/disable
 	autoanswer mode on your modem.  It should look like this:</para>
 
       <programlisting>set line /dev/tty01
 set speed 19200
 set file type binary
 set file names literal
 set win 8
 set rec pack 1024
 set send pack 1024
 set block 3
 set term bytesize 8
 set command bytesize 8
 set flow none
 
 pau 1
 out +++
 inp 5 OK
 out ATH0\13
 inp 5 OK
 echo \13
 out ATS0=1\13   ; change this to out ATS0=0\13 if you want to disable
                 ; autoanswer mode
 inp 5 OK
 echo \13
 exit</programlisting>
 
       <para>A script named <filename>/etc/ppp/kermit.dial</filename> is
 	used for dialing and authenticating on the remote host.  You will
 	need to customize it for your needs.  Put your login and password
 	in this script; you will also need to change the input statement
 	depending on responses from your modem and remote host.</para>
 
       <programlisting>;
 ; put the com line attached to the modem here:
 ;
 set line /dev/tty01
 ;
 ; put the modem speed here:
 ;
 set speed 19200
 set file type binary            ; full 8 bit file xfer
 set file names literal
 set win 8
 set rec pack 1024
 set send pack 1024
 set block 3
 set term bytesize 8
 set command bytesize 8
 set flow none
 set modem hayes
 set dial hangup off
 set carrier auto                ; Then SET CARRIER if necessary,
 set dial display on             ; Then SET DIAL if necessary,
 set input echo on
 set input timeout proceed
 set input case ignore
 def \%x 0                       ; login prompt counter
 goto slhup
 
 :slcmd                          ; put the modem in command mode
 echo Put the modem in command mode.
 clear                           ; Clear unread characters from input buffer
 pause 1
 output +++                      ; hayes escape sequence
 input 1 OK\13\10                ; wait for OK
 if success goto slhup
 output \13
 pause 1
 output at\13
 input 1 OK\13\10
 if fail goto slcmd              ; if modem doesn't answer OK, try again
 
 :slhup                          ; hang up the phone
 clear                           ; Clear unread characters from input buffer
 pause 1
 echo Hanging up the phone.
 output ath0\13                  ; hayes command for on hook
 input 2 OK\13\10
 if fail goto slcmd              ; if no OK answer, put modem in command mode
 
 :sldial                         ; dial the number
 pause 1
 echo Dialing.
 output atdt9,550311\13\10               ; put phone number here
 assign \%x 0                    ; zero the time counter
 
 :look
 clear                           ; Clear unread characters from input buffer
 increment \%x                   ; Count the seconds
 input 1 {CONNECT }
 if success goto sllogin
 reinput 1 {NO CARRIER\13\10}
 if success goto sldial
 reinput 1 {NO DIALTONE\13\10}
 if success goto slnodial
 reinput 1 {\255}
 if success goto slhup
 reinput 1 {\127}
 if success goto slhup
 if &lt; \%x 60 goto look
 else goto slhup
 
 :sllogin                        ; login
 assign \%x 0                    ; zero the time counter
 pause 1
 echo Looking for login prompt.
 
 :slloop
 increment \%x                   ; Count the seconds
 clear                           ; Clear unread characters from input buffer
 output \13
 ;
 ; put your expected login prompt here:
 ;
 input 1 {Username: }
 if success goto sluid
 reinput 1 {\255}
 if success goto slhup
 reinput 1 {\127}
 if success goto slhup
 if &lt; \%x 10 goto slloop         ; try 10 times to get a login prompt
 else goto slhup                 ; hang up and start again if 10 failures
 
 :sluid
 ;
 ; put your userid here:
 ;
 output ppp-login\13
 input 1 {Password: }
 ;
 ; put your password here:
 ;
 output ppp-password\13
 input 1 {Entering SLIP mode.}
 echo
 quit
 
 :slnodial
 echo \7No dialtone.  Check the telephone line!\7
 exit 1
 
 ; local variables:
 ; mode: csh
 ; comment-start: "; "
 ; comment-start-skip: "; "
 ; end:</programlisting>
     </sect2>
   </sect1>
 
   <sect1 id="ppp-troubleshoot">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Tom</firstname>
 	  <surname>Rhodes</surname>
 	  <contrib>Contributed by </contrib>
 	</author>
       </authorgroup>
       <!-- 13 June 2003 -->
     </sect1info>
     <title>Troubleshooting <acronym>PPP</acronym> Connections</title>
 
     <indexterm><primary>PPP</primary><secondary>troubleshooting</secondary></indexterm>
 
       <para>This section covers a few issues which may arise when
 	using PPP over a modem connection.  For instance, perhaps you
 	need to know exactly what prompts the system you are dialing
 	into will present.  Some <acronym>ISP</acronym>s present the
 	<literal>ssword</literal> prompt, and others will present
 	<literal>password</literal>; if the <command>ppp</command>
 	script is not written accordingly, the login attempt will
 	fail.  The most common way to debug <command>ppp</command>
 	connections is by connecting manually.  The following
 	information will walk you through a manual connection step by
 	step.</para>
 
     <sect2>
       <title>Check the Device Nodes</title>
 
 	<para>If you reconfigured your kernel then you recall the
 	  <devicename>sio</devicename> device.  If you did not
 	  configure your kernel, there is no reason to worry.  Just
 	  check the <command>dmesg</command> output for the modem
 	  device with:</para>
 
 	<screen>&prompt.root; <userinput>dmesg | grep sio</userinput></screen>
 
 	<para>You should get some pertinent output about the
 	  <devicename>sio</devicename> devices.  These are the COM
 	  ports we need.  If your modem acts like a standard serial
 	  port then you should see it listed on
 	  <devicename>sio1</devicename>, or <devicename>COM2</devicename>.  If so, you are not
 	  required to rebuild the kernel, you just need to make the
 	  serial device.  You can do this by changing your directory
 	  to <filename>/dev</filename> and running the
 	  <filename>MAKEDEV</filename> script like above.  Now make
 	  the serial devices with:</para>
 
 	<screen>&prompt.root; <userinput>sh MAKEDEV cuaa0 cuaa1 cuaa2 cuaa3</userinput></screen>
 
 	<para>which will create the serial devices for your system.
 	  When matching up sio modem is on <devicename>sio1</devicename> or
           <devicename>COM2</devicename> if you are in DOS, then your
 	  modem device would be <filename>/dev/cuaa1</filename>.</para>
     </sect2>
 
     <sect2>
       <title>Connecting Manually</title>
 
       <para>Connecting to the Internet by manually controlling
 	<command>ppp</command> is quick, easy, and a great way to
 	debug a connection or just get information on how your
 	<acronym>ISP</acronym> treats <command>ppp</command> client
 	connections.  Lets start <application>PPP</application> from
 	the command line.  Note that in all of our examples we will
 	use <emphasis>example</emphasis> as the hostname of the
 	machine running <application>PPP</application>.  You start
 	<command>ppp</command> by just typing
 	<command>ppp</command>:</para>
 
       <screen>&prompt.root; <userinput>ppp</userinput></screen>
 
       <para>We have now started <command>ppp</command>.</para>
 
       <screen>ppp ON example&gt; <userinput>set device <filename>/dev/cuaa1</filename></userinput></screen>
 
       <para>We set our modem device, in this case it is
 	<devicename>cuaa1</devicename>.</para>
 
       <screen>ppp ON example&gt; <userinput>set speed 115200</userinput></screen>
 
       <para>Set the connection speed, in this case we
 	are using 115,200 <acronym>kbps</acronym>.</para>
 
       <screen>ppp ON example&gt; <userinput>enable dns</userinput></screen>
 
       <para>Tell <command>ppp</command> to configure our
 	resolver and add the nameserver lines to
 	<filename>/etc/resolv.conf</filename>.  If <command>ppp</command>
 	cannot determine our hostname, we can set one manually later.</para>
 
       <screen>ppp ON example&gt; <userinput>term</userinput></screen>
 
       <para>Switch to <quote>terminal</quote> mode so that we can manually
 	control the modem.</para>
 
       <programlisting>deflink: Entering terminal mode on <filename>/dev/cuaa1</filename>
 type '~h' for help</programlisting>
 
       <screen><userinput>at</userinput>
 OK
 <userinput>atdt<replaceable>123456789</replaceable></userinput></screen>
 
       <para>Use <command>at</command> to initialize the modem,
 	then use <command>atdt</command> and the number for your
 	<acronym>ISP</acronym> to begin the dial in process.</para>
 
       <screen>CONNECT</screen>
 
       <para>Confirmation of the connection, if we are going to have
 	any connection problems, unrelated to hardware, here is where
 	we will attempt to resolve them.</para>
 
       <screen>ISP Login:<userinput>myusername</userinput></screen>
 
       <para>Here you are prompted for a username, return the
 	prompt with the username that was provided by the
 	<acronym>ISP</acronym>.</para>
 
       <screen>ISP Pass:<userinput>mypassword</userinput></screen>
 
       <para>This time we are prompted for a password, just
 	reply with the password that was provided by the
 	<acronym>ISP</acronym>.  Just like logging into
 	&os;, the password will not echo.</para>
 
       <screen>Shell or PPP:<userinput>ppp</userinput></screen>
 
       <para>Depending on your <acronym>ISP</acronym> this prompt
 	may never appear.  Here we are being asked if we wish to
 	use a shell on the provider, or to start
 	<command>ppp</command>.  In this example, we have chosen
 	to use <command>ppp</command> as we want an Internet
 	connection.</para>
 
       <screen>Ppp ON example&gt;</screen>
 
       <para>Notice that in this example the first <option>p</option>
 	has been capitalized.  This shows that we have successfully
 	connected to the <acronym>ISP</acronym>.</para>
 
       <screen>PPp ON example&gt;</screen>
 
       <para>We have successfully authenticated with our
 	<acronym>ISP</acronym> and are waiting for the
 	assigned <acronym>IP</acronym> address.</para>
 
       <screen>PPP ON example&gt;</screen>
 
       <para>We have made an agreement on an <acronym>IP</acronym>
 	address and successfully completed our connection.</para>
 
       <screen>PPP ON example&gt;<userinput>add default HISADDR</userinput></screen>
 
       <para>Here we add our default route, we need to do this before
 	we can talk to the outside world as currently the only
 	established connection is with the peer.  If this fails due to
 	existing routes you can put a bang character
 	<literal>!</literal> in front of the <option>add</option>.
 	Alternatively, you can set this before making the actual
 	connection and it will negotiate a new route
 	accordingly.</para>
 
       <para>If everything went good we should now have an active
 	connection to the Internet, which could be thrown into the
 	background using <keycombo
 	action="simul"><keycap>CTRL</keycap>
 	<keycap>z</keycap></keycombo> If you notice the
 	<command>PPP</command> return to <command>ppp</command> then
 	we have lost our connection.  This is good to know because it
 	shows our connection status.  Capital P's show that we have a
 	connection to the <acronym>ISP</acronym> and lowercase p's
 	show that the connection has been lost for whatever reason.
 	<command>ppp</command> only has these 2 states.</para>
 
       <sect3>
 	<title>Debugging</title>
 
 	<para>If you have a direct line and cannot seem to make a
 	  connection, then turn hardware flow
 	  <acronym>CTS/RTS</acronym> to off with the <option>set
 	  ctsrts off</option>.  This is mainly the case if you are
 	  connected to some <application>PPP</application> capable
 	  terminal servers, where <application>PPP</application> hangs
 	  when it tries to write data to your communication link, so
 	  it would be waiting for a <acronym>CTS</acronym>, or Clear
 	  To Send signal which may never come.  If you use this option
 	  however, you should also use the <option>set accmap</option>
 	  option, which may be required to defeat hardware dependent
 	  on passing certain characters from end to end, most of the
 	  time XON/XOFF.  See the &man.ppp.8; manual page for more
 	  information on this option, and how it is used.</para>
 
 	<para>If you have an older modem, you may need to use the
 	  <option>set parity even</option>.  Parity is set at none
 	  be default, but is used for error checking (with a large
 	  increase in traffic) on older modems and some
 	  <acronym>ISP</acronym>s.  You may need this option for
 	  the Compuserve <acronym>ISP</acronym>.</para>
 
 	<para><application>PPP</application> may not return to the
 	  command mode, which is usually a negotiation error where
 	  the <acronym>ISP</acronym> is waiting for your side to start
 	  negotiating.  At this point, using the <command>~p</command>
 	  command will force ppp to start sending the configuration
 	  information.</para>
 
 	<para>If you never obtain a login prompt, then most likely you
 	  need to use <acronym>PAP</acronym> or
 	  <acronym>CHAP</acronym> authentication instead of the
 	  &unix; style in the example above.  To use
 	  <acronym>PAP</acronym> or <acronym>CHAP</acronym> just add
 	  the following options to <application>PPP</application>
 	  before going into terminal mode:</para>
 
 	<screen>ppp ON example&gt; <userinput>set authname <replaceable>myusername</replaceable></userinput></screen>
 
 	<para>Where <replaceable>myusername</replaceable> should be
 	  replaced with the username that was assigned by the
 	  <acronym>ISP</acronym>.</para>
 
 	<screen>ppp ON example&gt; <userinput>set authkey <replaceable>mypassword</replaceable></userinput></screen>
 
 	<para>Where <replaceable>mypassword</replaceable> should be
 	  replaced with the password that was assigned by the
 	  <acronym>ISP</acronym>.</para>
 
 	<para>If you connect fine, but cannot seem to find any domain
 	  name, try to use &man.ping.8; with an <acronym>IP</acronym>
 	  address and see if you can get any return information.  If
 	  you experience 100 percent (100%) packet loss, then it is most
 	  likely that you were not assigned a default route.  Double
 	  check that the option <option>add default HISADDR</option>
 	  was set during the connection.  If you can connect to a
 	  remote <acronym>IP</acronym> address then it is possible
 	  that a resolver address has not been added to the
 	  <filename>/etc/resolv.conf</filename>.  This file should
 	  look like:</para>
 
 	<programlisting>domain <replaceable>example.com</replaceable>
 nameserver <replaceable>x.x.x.x</replaceable>
 nameserver <replaceable>y.y.y.y</replaceable></programlisting>
 
 	<para>Where <replaceable>x.x.x.x</replaceable> and
 	  <replaceable>y.y.y.y</replaceable> should be replaced with
 	  the <acronym>IP</acronym> address of your
 	  <acronym>ISP</acronym>'s DNS servers.  This information may
 	  or may not have been provided when you signed up, but a
 	  quick call to your <acronym>ISP</acronym> should remedy
 	  that.</para>
 
 	<para>You could also have &man.syslog.3; provide a logging
 	  function for your <application>PPP</application> connection.
 	  Just add:</para>
 
 	<programlisting>!ppp
 *.*     /var/log/ppp.log</programlisting>
 
 	<para>to <filename>/etc/syslog.conf</filename>.  In most cases, this
 	  functionality already exists.</para>
 
       </sect3>
     </sect2>
   </sect1>
 
 
 
 
   <sect1 id="pppoe">
     <sect1info>
       <authorgroup>
         <author>
           <firstname>Jim</firstname>
           <surname>Mock</surname>
           <contrib>Contributed (from http://node.to/freebsd/how-tos/how-to-freebsd-pppoe.html) by </contrib>
 	</author>
       </authorgroup>
       <!-- 10 Jan 2000 -->
     </sect1info>
 
     <title>Using PPP over Ethernet (PPPoE)</title>
     <indexterm><primary>PPP</primary><secondary>over Ethernet</secondary></indexterm>
     <indexterm>
       <primary>PPPoE</primary>
       <see>PPP, over Ethernet</see>
     </indexterm>
 
     <para>This section describes how to set up PPP over Ethernet
       (<acronym>PPPoE</acronym>).</para>
 
     <sect2>
       <title>Configuring the Kernel</title>
 
       <para>No kernel configuration is necessary for PPPoE any longer.  If
 	the necessary netgraph support is not built into the kernel, it will
         be dynamically loaded by <application>ppp</application>.</para>
     </sect2>
 
     <sect2>
       <title>Setting Up <filename>ppp.conf</filename></title>
 
       <para>Here is an example of a working
         <filename>ppp.conf</filename>:</para>
 
       <programlisting>default:
   set log Phase tun command # you can add more detailed logging if you wish
   set ifaddr 10.0.0.1/0 10.0.0.2/0
 
 name_of_service_provider:
   set device PPPoE:<replaceable>xl1</replaceable> # replace xl1 with your Ethernet device
   set authname YOURLOGINNAME
   set authkey YOURPASSWORD
   set dial
   set login
   add default HISADDR</programlisting>
 
     </sect2>
 
     <sect2>
       <title>Running <application>ppp</application></title>
 
       <para>As <username>root</username>, you can run:</para>
 
       <screen>&prompt.root; <userinput>ppp -ddial name_of_service_provider</userinput></screen>
 
     </sect2>
 
     <sect2>
       <title>Starting <application>ppp</application> at Boot</title>
 
       <para>Add the following to your <filename>/etc/rc.conf</filename>
         file:</para>
 
       <programlisting>ppp_enable="YES"
 ppp_mode="ddial"
 ppp_nat="YES"	# if you want to enable nat for your local network, otherwise NO
 ppp_profile="name_of_service_provider"</programlisting>
     </sect2>
 
     <sect2>
       <title>Using a PPPoE Service Tag</title>
 
       <para>Sometimes it will be necessary to use a service tag to establish
 	your connection.  Service tags are used to distinguish between
 	different PPPoE servers attached to a given network.</para>
 
       <para>You should have been given any required service tag information
 	in the documentation provided by your ISP.  If you cannot locate
 	it there, ask your ISP's tech support personnel.</para>
 
       <para>As a last resort, you could try the method suggested by the
 	<ulink url="http://www.roaringpenguin.com/pppoe/">Roaring Penguin
 	PPPoE</ulink> program which can be found in the <link
 	linkend="ports">Ports Collection</link>.  Bear in mind however,
 	this may de-program your modem and render it useless, so
 	think twice before doing it.  Simply install the program shipped
 	with the modem by your provider.  Then, access the
 	<guimenu>System</guimenu> menu from the program.  The name of your
 	profile should be listed there.  It is usually
 	<emphasis>ISP</emphasis>.</para>
 
       <para>The profile name (service tag) will be used in the PPPoE
 	configuration entry in <filename>ppp.conf</filename> as the provider
 	part of the <command>set device</command> command (see the &man.ppp.8;
 	manual page for full details).  It should look like this:</para>
 
       <programlisting>set device PPPoE:<replaceable>xl1</replaceable>:<replaceable>ISP</replaceable></programlisting>
 
       <para>Do not forget to change <replaceable>xl1</replaceable>
 	to the proper device for your Ethernet card.</para>
       <para>Do not forget to change <replaceable>ISP</replaceable>
 	to the profile you have just found above.</para>
 
       <para>For additional information, see:</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><ulink
 	    url="http://renaud.waldura.com/doc/freebsd/pppoe/">Cheaper
 	    Broadband with FreeBSD on DSL</ulink> by Renaud
 	    Waldura.</para>
 	</listitem>
 
 	<listitem>
 	  <para><ulink
 	      url="http://www.ruhr.de/home/nathan/FreeBSD/tdsl-freebsd.html">
 	      Nutzung von T-DSL und T-Online mit FreeBSD</ulink>
 	    by Udo Erdelhoff (in German).</para>
 	</listitem>
       </itemizedlist>
     </sect2>
 
     <sect2 id="ppp-3com">
 
       <title>PPPoE with a &tm.3com; <trademark class="registered">HomeConnect</trademark> ADSL Modem Dual Link</title>
 
       <para>This modem does not follow <ulink
 	url="http://www.faqs.org/rfcs/rfc2516.html">RFC 2516</ulink>
 	(<emphasis>A Method for transmitting PPP over Ethernet
 	(PPPoE)</emphasis>, written by L. Mamakos, K. Lidl, J. Evarts,
 	D. Carrel, D. Simone, and R. Wheeler).  Instead, different packet
 	type codes have been used for the Ethernet frames.  Please complain
 	to <ulink url="http://www.3com.com/">3Com</ulink> if you think it
 	should comply with the PPPoE specification.</para>
 
       <para>In order to make FreeBSD capable of communicating with this
 	device, a sysctl must be set.  This can be done automatically at
 	boot time by updating <filename>/etc/sysctl.conf</filename>:</para>
 
 	<programlisting>net.graph.nonstandard_pppoe=1</programlisting>
 
       <para>or can be done immediately with the command:</para>
 
       <screen>&prompt.root; <userinput>sysctl net.graph.nonstandard_pppoe=1</userinput></screen>
 
       <para>Unfortunately, because this is a system-wide setting, it is
 	not possible to talk to a normal PPPoE client or server and a
 	&tm.3com; <trademark class="registered">HomeConnect</trademark> ADSL Modem at the same time.</para>
 
     </sect2>
   </sect1>
 
   <sect1 id="pppoa">
     <title>Using <application>PPP</application> over ATM (PPPoA)</title>
     <indexterm><primary>PPP</primary><secondary>over ATM</secondary></indexterm>
     <indexterm>
       <primary>PPPoA</primary>
       <see>PPP, over ATM</see>
     </indexterm>
 
     <para>The following describes how to set up PPP over ATM (PPPoA).
       PPPoA is a popular choice among European DSL providers.</para>
 
     <sect2>
       <title>Using PPPoA with the Alcatel &speedtouch; USB</title>
 
       <para>PPPoA support for this device is supplied as a port in
 	FreeBSD because the firmware is distributed under <ulink
 	url="http://www.speedtouchdsl.com/disclaimer_lx.htm">Alcatel's
 	license agreement</ulink> and can not be redistributed freely
 	with the base system of FreeBSD.</para>
 
       <para>To install the software, simply use the <link
 	  linkend="ports">Ports Collection</link>. Install the
 	<filename role="package">net/pppoa</filename> port and follow the
 	instructions provided with it.</para>
 
       <para>Like many USB devices, the Alcatel &speedtouch; USB needs to
         download firmware from the host computer to operate properly.
         It is possible to automate this process in &os; so that this
         transfer takes place whenever the device is plugged into a USB
         port.  The following information can be added to the
         <filename>/etc/usbd.conf</filename> file to enable this
         automatic firmware transfer.  This file must be edited as the
         <username>root</username> user.</para>
 
       <programlisting>device "Alcatel SpeedTouch USB"
     devname "ugen[0-9]+"
     vendor 0x06b9
     product 0x4061
     attach "/usr/local/sbin/modem_run -f /usr/local/libdata/mgmt.o"</programlisting>
 
      <para>To enable the USB daemon, <application>usbd</application>,
        put the following the line into
        <filename>/etc/rc.conf</filename>:</para>
 
      <programlisting>usbd_enable="YES"</programlisting>
 
      <para>It is also possible to set up
        <application>ppp</application> to dial up at startup.  To do
        this add the following lines to
        <filename>/etc/rc.conf</filename>.  Again, for this procedure
        you will need to be logged in as the <username>root</username>
        user.</para>
 
      <programlisting>ppp_enable="YES"
 ppp_mode="ddial"
 ppp_profile="adsl"</programlisting>
 
      <para>For this to work correctly you will need to have used the
        sample <filename>ppp.conf</filename> which is supplied with the
        <filename role="package">net/pppoa</filename> port.</para>
 
     </sect2>
 
     <sect2>
       <title>Using mpd</title>
 
       <para>You can use <application>mpd</application> to connect to a
         variety of services, in particular PPTP services. You can find
         <application>mpd</application> in the Ports Collection,
         <filename role="package">net/mpd</filename>.  Many ADSL modems
         require that a PPTP tunnel is created between the modem and
         computer, one such modem is the Alcatel &speedtouch;
         Home.</para>
 
       <para>First you must install the port, and then you can
         configure <application>mpd</application> to suit your
         requirements and provider settings. The port places a set of
         sample configuration files which are well documented in
         <filename><replaceable>PREFIX</replaceable>/etc/mpd/</filename>.
         Note here that <replaceable>PREFIX</replaceable> means the directory
         into which your ports are installed, this defaults to
         <filename>/usr/local/</filename>. A complete guide to
         configure <application>mpd</application> is available in
         HTML format once the port has been installed. It is placed in
         <filename><replaceable>PREFIX</replaceable>/share/doc/mpd/</filename>.
         Here is a sample configuration for connecting to an ADSL
         service with <application>mpd</application>. The configuration
         is spread over two files, first the
         <filename>mpd.conf</filename>:</para>
 
       <programlisting>default:
     load adsl
 
 adsl:
     new -i ng0 adsl adsl
     set bundle authname <replaceable>username</replaceable> <co
     id="co-mpd-ex-user"/>
     set bundle password <replaceable>password</replaceable> <co
     id="co-mpd-ex-pass"/>
     set bundle disable multilink
 
     set link no pap acfcomp protocomp
     set link disable chap
     set link accept chap
     set link keep-alive 30 10
 
     set ipcp no vjcomp
     set ipcp ranges 0.0.0.0/0 0.0.0.0/0
 
     set iface route default
     set iface disable on-demand
     set iface enable proxy-arp
     set iface idle 0
 
     open</programlisting>
 
     <calloutlist>
       <callout arearefs="co-mpd-ex-user">
         <para>The username used to authenticate with your ISP.</para>
       </callout>
       <callout arearefs="co-mpd-ex-pass">
         <para>The password used to authenticate with your ISP.</para>
       </callout>
     </calloutlist>
 
     <para>The <filename>mpd.links</filename> file contains information about
       the link, or links, you wish to establish. An example
       <filename>mpd.links</filename> to accompany the above example is given
       beneath:</para>
 
     <programlisting>adsl:
     set link type pptp
     set pptp mode active
     set pptp enable originate outcall
     set pptp self <replaceable>10.0.0.1</replaceable> <co
     id="co-mpd-ex-self"/>
     set pptp peer <replaceable>10.0.0.138</replaceable> <co
     id="co-mpd-ex-peer"/></programlisting>
 
     <calloutlist>
       <callout arearefs="co-mpd-ex-self">
 	<para>The IP address of your &os; computer which you will be
 	  using <application>mpd</application> from.</para>
       </callout>
       <callout arearefs="co-mpd-ex-peer">
 	<para>The IP address of your ADSL modem.  For the Alcatel
 	  &speedtouch; Home this address defaults to <hostid
 	  role="ipaddr">10.0.0.138</hostid>.</para>
       </callout>
     </calloutlist>
 
     <para>It is possible to initialize the connection easily by issuing the
       following command as <username>root</username>:</para>
 
     <screen>&prompt.root; <userinput>mpd -b <replaceable>adsl</replaceable></userinput></screen>
 
     <para>You can see the status of the connection with the following
       command:</para>
 
     <screen>&prompt.user; <userinput>ifconfig <replaceable>ng0</replaceable></userinput>
 ng0: flags=88d1&lt;UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST&gt; mtu 1500
      inet 216.136.204.117 --> 204.152.186.171 netmask 0xffffffff</screen>
 
     <para>Using <application>mpd</application> is the recommended way to
       connect to an ADSL service with &os;.</para>
 
     </sect2>
 
     <sect2>
       <title>Using pptpclient</title>
 
       <para>It is also possible to use FreeBSD to connect to other PPPoA
 	services using
 	<filename role="package">net/pptpclient</filename>.</para>
 
       <para>To use <filename role="package">net/pptpclient</filename> to
 	connect to a DSL service, install the port or package and edit your
 	<filename>/etc/ppp/ppp.conf</filename>. You will need to be
 	<username>root</username> to perform both of these operations. An
 	example section of <filename>ppp.conf</filename> is given
 	below. For further information on <filename>ppp.conf</filename>
 	options consult the <application>ppp</application> manual page,
 	&man.ppp.8;.</para>
 
       <programlisting>adsl:
  set log phase chat lcp ipcp ccp tun command
  set timeout 0
  enable dns
  set authname <replaceable>username</replaceable> <co id="co-pptp-ex-user"/>
  set authkey <replaceable>password</replaceable> <co id="co-pptp-ex-pass"/>
  set ifaddr 0 0
  add default HISADDR</programlisting>
 
    <calloutlist>
      <callout arearefs="co-pptp-ex-user">
 	   <para>The username of your account with the DSL provider.</para>
 	 </callout>
 	 <callout arearefs="co-pptp-ex-pass">
 	   <para>The password for your account.</para>
 	 </callout>
    </calloutlist>
 
    <warning>
      <para>Because you must put your account's password in the
 	 <filename>ppp.conf</filename> file in plain text form you should
 	 make sure than nobody can read the contents of this file. The
 	 following series of commands will make sure the file is only
 	 readable by the <username>root</username> account. Refer to the
 	 manual pages for &man.chmod.1; and &man.chown.8; for further
 	 information.</para>
 	 <screen>&prompt.root; <userinput>chown root:wheel /etc/ppp/ppp.conf</userinput>
 &prompt.root; <userinput>chmod 600 /etc/ppp/ppp.conf</userinput></screen>
    </warning>
 
       <para>This will open a tunnel for a PPP session to your DSL router.
 	Ethernet DSL modems have a preconfigured LAN IP address which you
 	connect to. In the case of the Alcatel &speedtouch; Home this address is
 	<hostid role="ipaddr">10.0.0.138</hostid>. Your router documentation
 	should tell you which address your device uses. To open the tunnel and
 	start a PPP session execute the following
 	command:</para>
 
       <screen>&prompt.root; <userinput>pptp <replaceable>address</replaceable> <replaceable>adsl</replaceable></userinput></screen>
 
       <tip>
 	<para>You may wish to add an ampersand (<quote>&amp;</quote>) to the
 	  end of the previous command because <application>pptp</application>
 	  will not return your prompt to you otherwise.</para>
       </tip>
 
       <para>A <devicename>tun</devicename> virtual tunnel device will be
 	created for interaction between the <application>pptp</application>
 	and <application>ppp</application> processes. Once you have been
 	returned to your prompt, or the <application>pptp</application>
 	process has confirmed a connection you can examine the tunnel like
 	so:</para>
 
       <screen>&prompt.user; <userinput>ifconfig <replaceable>tun0</replaceable></userinput>
 tun0: flags=8051&lt;UP,POINTOPOINT,RUNNING,MULTICAST&gt; mtu 1500
         inet 216.136.204.21 --> 204.152.186.171 netmask 0xffffff00
         Opened by PID 918</screen>
 
       <para>If you are unable to connect, check the configuration of
 	your router, which is usually accessible via
 	<application>telnet</application> or with a web browser. If you still
 	cannot connect you should examine the output of the
 	<command>pptp</command> command and the contents of the
 	<application>ppp</application> log file,
 	<filename>/var/log/ppp.log</filename> for clues.</para>
     </sect2>
   </sect1>
 
   <sect1 id="slip">
     <sect1info>
       <authorgroup>
 	<author>
 	  <firstname>Satoshi</firstname>
 	  <surname>Asami</surname>
 	  <contrib>Originally contributed by </contrib>
 	</author>
       </authorgroup>
       <authorgroup>
 	<author>
 	  <firstname>Guy</firstname>
 	  <surname>Helmer</surname>
 	  <contrib>With input from </contrib>
 	</author>
 	<author>
 	  <firstname>Piero</firstname>
           <surname>Serini</surname>
 	</author>
       </authorgroup>
     </sect1info>
 
     <title>Using SLIP</title>
     <indexterm><primary>SLIP</primary></indexterm>
 
     <sect2 id="slipc">
       <title>Setting Up a SLIP Client</title>
       <indexterm><primary>SLIP</primary><secondary>client</secondary></indexterm>
       <para>The following is one way to set up a FreeBSD machine for SLIP
 	on a static host network.  For dynamic hostname assignments (your
 	address changes each time you dial up), you probably need to
 	have a more complex setup.</para>
 
       <para>First, determine which serial port your modem is connected to.
 	Many people set up a symbolic link, such as
 	<filename>/dev/modem</filename>, to point to the real device name,
 	<filename>/dev/cuaaN</filename> (or <filename>/dev/cuadN</filename> under &os;&nbsp;6.X).  This allows you to
 	abstract the actual device name should you ever need to move
 	the modem to a different port.  It can become quite cumbersome when you
 	need to fix a bunch of files in <filename>/etc</filename> and
 	<filename>.kermrc</filename> files all over the system!</para>
 
       <note>
 	<para><filename>/dev/cuaa0</filename> (or <filename>/dev/cuad0</filename> under &os;&nbsp;6.X) is
 	  <devicename>COM1</devicename>, <filename>cuaa1</filename> (or <filename>/dev/cuad1</filename>) is
 	  <devicename>COM2</devicename>, etc.</para>
       </note>
 
       <para>Make sure you have the following in your kernel configuration
 	file:</para>
 
       <programlisting>device   sl</programlisting>
 
       <para>Under &os;&nbsp;4.X, use instead the following
 	line:</para>
 
       <programlisting>pseudo-device   sl      1</programlisting>
 
       <para>It is included in the <filename>GENERIC</filename> kernel, so
 	this should not be a problem unless you have deleted it.</para>
 
       <sect3>
 	<title>Things You Have to Do Only Once</title>
 
 	<procedure>
 	  <step>
 	    <para>Add your home machine, the gateway and nameservers to
 	      your <filename>/etc/hosts</filename> file.  Ours looks like
 	      this:</para>
 
 	    <programlisting>127.0.0.1               localhost loghost
 136.152.64.181          water.CS.Example.EDU water.CS water
 136.152.64.1            inr-3.CS.Example.EDU inr-3 slip-gateway
 128.32.136.9            ns1.Example.EDU ns1
 128.32.136.12           ns2.Example.EDU ns2</programlisting>
 	  </step>
 
 	  <step>
 	    <para>Make sure you have <literal>hosts</literal> before
 	      <literal>bind</literal> in your
 	      <filename>/etc/host.conf</filename> on FreeBSD versions
 	      prior to 5.0.  Since FreeBSD&nbsp;5.0, the system uses
 	      the file <filename>/etc/nsswitch.conf</filename> instead,
 	      make sure you have <literal>files</literal> before
 	      <literal>dns</literal> in the <option>hosts</option> line
 	      of this file.  Without these parameters funny
 	      things may happen.</para>
 	  </step>
 
 	  <step>
 	    <para>Edit the <filename>/etc/rc.conf</filename> file.</para>
 
 	    <orderedlist>
 	      <listitem>
 		<para>Set your hostname by editing the line that
 		  says:</para>
 
 		<programlisting>hostname="myname.my.domain"</programlisting>
 
 		<para>Your machine's full Internet hostname should be
 		  placed here.</para>
 	      </listitem>
 
 	      <listitem>
 		<indexterm><primary>default route</primary></indexterm>
 
-		<para>Designate the default router by changing the
+		<para>Designate the default router<indexterm><primary>default route</primary></indexterm> by changing the
 		  line:</para>
 
 		<programlisting>defaultrouter="NO"</programlisting>
 
 		<para>to:</para>
 
 		<programlisting>defaultrouter="slip-gateway"</programlisting>
 	      </listitem>
 	    </orderedlist>
 	  </step>
 
 	  <step>
 	    <para>Make a file <filename>/etc/resolv.conf</filename> which
 	      contains:</para>
 
 	    <programlisting>domain CS.Example.EDU
 nameserver 128.32.136.9
 nameserver 128.32.136.12</programlisting>
 
 	    <indexterm><primary>nameserver</primary></indexterm>
 	    <indexterm><primary>domain name</primary></indexterm>
 	    <para>As you can see, these set up the nameserver hosts.  Of
 	      course, the actual domain names and addresses depend on your
 	      environment.</para>
 	  </step>
 
 	  <step>
 	    <para>Set the password for <username>root</username> and
 	      <username>toor</username> (and any other
 	      accounts that do not have a password).</para>
 	  </step>
 
 	  <step>
 	    <para>Reboot your machine and make sure it comes up with the
 	      correct hostname.</para>
 	  </step>
 	</procedure>
       </sect3>
 
       <sect3>
 	<title>Making a SLIP Connection</title>
 	<indexterm><primary>SLIP</primary><secondary>connecting with</secondary></indexterm>
 	<procedure>
 	  <step>
 	    <para>Dial up, type <command>slip</command> at the prompt,
 	      enter your machine name and password.  What is required to
 	      be entered depends on your environment.  If you use
 	      <application>Kermit</application>, you can try a script like this:</para>
 
 	    <programlisting># kermit setup
 set modem hayes
 set line /dev/modem
 set speed 115200
 set parity none
 set flow rts/cts
 set terminal bytesize 8
 set file type binary
 # The next macro will dial up and login
 define slip dial 643-9600, input 10 =&gt;, if failure stop, -
 output slip\x0d, input 10 Username:, if failure stop, -
 output silvia\x0d, input 10 Password:, if failure stop, -
 output ***\x0d, echo \x0aCONNECTED\x0a</programlisting>
 
 	    <para>Of course, you have to change the username and password
 	      to fit yours.  After doing so, you can just type
 	      <command>slip</command> from the <application>Kermit</application> prompt to
 	      connect.</para>
 
 	    <note>
 	      <para>Leaving your password in plain text anywhere in the
 	        filesystem is generally a <emphasis>bad</emphasis> idea.
 		Do it at your own risk.</para>
 	    </note>
 	  </step>
 
 	  <step>
 	    <para>Leave the <application>Kermit</application> there (you can suspend it by
 	      <keycombo>
 		<keycap>Ctrl</keycap>
 		<keycap>z</keycap>
 	      </keycombo>) and as <username>root</username>, type:</para>
 
 	    <screen>&prompt.root; <userinput>slattach -h -c -s 115200 /dev/modem</userinput></screen>
 
 	    <para>If you are able to <command>ping</command> hosts on the
 	      other side of the router, you are connected!  If it does not
 	      work, you might want to try <option>-a</option> instead of
 	      <option>-c</option> as an argument to
               <command>slattach</command>.</para>
 	  </step>
 	</procedure>
       </sect3>
 
       <sect3>
 	<title>How to Shutdown the Connection</title>
 
 	<para>Do the following:</para>
 
 	<screen>&prompt.root; <userinput>kill -INT `cat /var/run/slattach.modem.pid`</userinput></screen>
 
 	<para>to kill <command>slattach</command>.  Keep in mind you must be
 	  <username>root</username> to do the above.  Then go back to
 	  <command>kermit</command> (by running <command>fg</command> if you suspended it) and
 	  exit from
 	  it (<keycap>q</keycap>).</para>
 
 	<para>The &man.slattach.8; manual page says you have
 	  to use <command>ifconfig sl0 down</command>
           to mark the interface down, but this does not
 	  seem to make any difference.
 	  (<command>ifconfig sl0</command> reports the same thing.)</para>
 
 	<para>Some times, your modem might refuse to drop the carrier.
 	  In that case, simply start <command>kermit</command> and quit
 	  it again. It usually goes out on the second try.</para>
       </sect3>
 
       <sect3>
 	<title>Troubleshooting</title>
 
 	<para>If it does not work, feel free to ask on &a.net.name; mailing list.  The things that
 	  people tripped over so far:</para>
 
 	<itemizedlist>
 	  <listitem>
 	    <para>Not using <option>-c</option> or <option>-a</option> in
 	      <command>slattach</command> (This should not be fatal,
 	      but some users have reported that this solves their
 	      problems.)</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>Using <option>s10</option> instead of
 	      <option>sl0</option> (might be hard to see the difference on
 	      some fonts).</para>
 	  </listitem>
 
 	  <listitem>
 	    <para>Try <command>ifconfig sl0</command> to see your
 	      interface status.  For example, you might get:</para>
 
 	    <screen>&prompt.root; <userinput>ifconfig sl0</userinput>
 sl0: flags=10&lt;POINTOPOINT&gt;
         inet 136.152.64.181 --&gt; 136.152.64.1 netmask ffffff00</screen>
 	  </listitem>
 
 	  <listitem>
 	    <para>If you get <errorname>no route to host</errorname>
             messages from &man.ping.8;, there may be a problem with your
             routing table.  You can use the <command>netstat -r</command>
             command to display the current routes :</para>
 
 	    <screen>&prompt.root; <userinput>netstat -r</userinput>
 Routing tables
 Destination      Gateway            Flags     Refs     Use  IfaceMTU    Rtt    Netmasks:
 
 (root node)
 (root node)
 
 Route Tree for Protocol Family inet:
 (root node) =&gt;
 default          inr-3.Example.EDU  UG          8   224515  sl0 -      -
 localhost.Exampl localhost.Example. UH          5    42127  lo0 -       0.438
 inr-3.Example.ED water.CS.Example.E UH          1        0  sl0 -      -
 water.CS.Example localhost.Example. UGH        34 47641234  lo0 -       0.438
 (root node)</screen>
 
 	    <para>The preceding examples are from a relatively busy system.
               The numbers on your system will vary depending on
               network activity.</para>
 
 	  </listitem>
 	</itemizedlist>
       </sect3>
     </sect2>
 
     <sect2 id="slips">
       <title>Setting Up a SLIP Server</title>
       <indexterm><primary>SLIP</primary><secondary>server</secondary></indexterm>
 
       <para>This document provides suggestions for setting up SLIP Server
 	services on a FreeBSD system, which typically means configuring
 	your system to automatically startup connections upon login for
 	remote SLIP clients.</para>
 
       <!-- Disclaimer is not necessarily relevant
       <para> The author has written this document based
 	on his experience; however, as your system and needs may be
 	different, this document may not answer all of your questions, and
 	the author cannot be responsible if you damage your system or lose
 	data due to attempting to follow the suggestions here.</para>
       -->
 
       <sect3 id="slips-prereqs">
 	<title>Prerequisites</title>
 	<indexterm><primary>TCP/IP networking</primary></indexterm>
 	<para>This section is very technical in nature, so background
 	  knowledge is required.  It is assumed that you are familiar with
 	  the TCP/IP network protocol, and in particular, network and node
 	  addressing, network address masks, subnetting, routing, and
 	  routing protocols, such as RIP.  Configuring SLIP services on a
 	  dial-up server requires a knowledge of these concepts, and if
 	  you are not familiar with them, please read a copy of either
 	  Craig Hunt's <emphasis>TCP/IP Network Administration</emphasis>
 	  published by O'Reilly &amp; Associates, Inc. (ISBN Number
 	  0-937175-82-X), or Douglas Comer's books on the TCP/IP
 	  protocol.</para>
 
 	<indexterm><primary>modem</primary></indexterm>
 	<para>It is further assumed that you have already set up your
 	  modem(s) and configured the appropriate system files to allow
 	  logins through your modems.  If you have not prepared your
 	  system for this yet, please see <xref
 	  linkend="dialup"/> for details on dialup services
 	  configuration.
 	  You may also want to check the manual pages for &man.sio.4; for
 	  information on the serial port device driver and &man.ttys.5;,
 	  &man.gettytab.5;, &man.getty.8;, &amp; &man.init.8; for
 	  information relevant to configuring the system to accept logins
 	  on modems, and perhaps &man.stty.1; for information on setting
 	  serial port parameters (such as <literal>clocal</literal> for
 	  directly-connected serial interfaces).</para>
       </sect3>
 
       <sect3>
 	<title>Quick Overview</title>
 
 	<para>In its typical configuration, using FreeBSD as a SLIP server
 	  works as follows:  a SLIP user dials up your FreeBSD SLIP Server
 	  system and logs in with a special SLIP login ID that uses
 	  <filename>/usr/sbin/sliplogin</filename> as the special user's
 	  shell.  The <command>sliplogin</command> program browses the
 	  file <filename>/etc/sliphome/slip.hosts</filename> to find a
 	  matching line for the special user, and if it finds a match,
 	  connects the serial line to an available SLIP interface and then
 	  runs the shell script
 	  <filename>/etc/sliphome/slip.login</filename> to configure the
 	  SLIP interface.</para>
 
         <sect4>
 	  <title>An Example of a SLIP Server Login</title>
 
 	  <para>For example, if a SLIP user ID were
 	    <username>Shelmerg</username>, <username>Shelmerg</username>'s
 	    entry in <filename>/etc/master.passwd</filename> would look
 	    something like this:</para>
 
 	  <programlisting>Shelmerg:password:1964:89::0:0:Guy Helmer - SLIP:/usr/users/Shelmerg:/usr/sbin/sliplogin</programlisting>
 
 	  <para>When <username>Shelmerg</username> logs in,
 	    <command>sliplogin</command> will search
 	    <filename>/etc/sliphome/slip.hosts</filename> for a line that
 	    had a matching user ID; for example, there may be a line in
 	    <filename>/etc/sliphome/slip.hosts</filename> that
 	    reads:</para>
 
 	  <programlisting>Shelmerg        dc-slip sl-helmer       0xfffffc00		  autocomp</programlisting>
 
 	  <para><command>sliplogin</command> will find that matching line,
 	    hook the serial line into the next available SLIP interface,
 	    and then execute <filename>/etc/sliphome/slip.login</filename>
 	    like this:</para>
 
 	  <programlisting>/etc/sliphome/slip.login 0 19200 Shelmerg dc-slip sl-helmer 0xfffffc00 autocomp</programlisting>
 
 	  <para>If all goes well,
 	    <filename>/etc/sliphome/slip.login</filename> will issue an
 	    <command>ifconfig</command> for the SLIP interface to which
 	    <command>sliplogin</command> attached itself (SLIP interface
 	    0, in the above example, which was the first parameter in the
 	    list given to <filename>slip.login</filename>) to set the
 	    local IP address (<hostid>dc-slip</hostid>), remote IP address
 	    (<hostid>sl-helmer</hostid>), network mask for the SLIP
 	    interface (<hostid role="netmask">0xfffffc00</hostid>), and
 	    any additional flags (<literal>autocomp</literal>).  If
 	    something goes wrong, <command>sliplogin</command> usually
 	    logs good informational messages via the
 	    <application>syslogd</application> daemon facility, which usually logs
 	    to <filename>/var/log/messages</filename> (see the manual
 	    pages for &man.syslogd.8; and &man.syslog.conf.5; and perhaps
 	    check <filename>/etc/syslog.conf</filename> to see to what
 	    <application>syslogd</application> is logging and where it is
 	    logging to).</para>
 	</sect4>
       </sect3>
 
       <sect3>
 	<title>Kernel Configuration</title>
 	<indexterm><primary>kernel</primary><secondary>configuration</secondary></indexterm>
 	<indexterm><primary>SLIP</primary></indexterm>
 
 	<para>&os;'s default kernel (<filename>GENERIC</filename>)
 	  comes with SLIP (&man.sl.4;) support; in case of a custom
 	  kernel, you have to add the following line to your kernel
 	  configuration file:</para>
 
 	<programlisting>device   sl</programlisting>
 
 	<para>Under &os;&nbsp;4.X, use instead the following
 	  line:</para>
 
 	<programlisting>pseudo-device   sl      2</programlisting>
 
 	<note>
 	  <para>The number at the end of the line is the maximum
 	    number of SLIP connections that may be operating
 	    simultaneously.  Since &os;&nbsp;5.0, the &man.sl.4;
 	    driver is <quote>auto-cloning</quote>.</para>
 	</note>
 
 	<para>By default, your &os; machine will not forward packets.
 	  If you want your FreeBSD SLIP Server to act as a router, you
 	  will have to edit the <filename>/etc/rc.conf</filename> file and
 	  change the setting of the <literal>gateway_enable</literal> variable to
 	  <option>YES</option>.</para>
 
 	<para>You will then need to reboot for the new settings to take
 	  effect.</para>
 
 	<para>Please refer to <xref linkend="kernelconfig"/> on
 	  Configuring the FreeBSD Kernel for help in
 	  reconfiguring your kernel.</para>
       </sect3>
 
       <sect3>
 	<title>Sliplogin Configuration</title>
 
 	<para>As mentioned earlier, there are three files in the
 	  <filename>/etc/sliphome</filename> directory that are part of
 	  the configuration for <filename>/usr/sbin/sliplogin</filename>
 	  (see &man.sliplogin.8; for the actual manual page for
 	  <command>sliplogin</command>): <filename>slip.hosts</filename>,
 	  which defines the SLIP users and their associated IP
 	  addresses; <filename>slip.login</filename>, which usually just
 	  configures the SLIP interface; and (optionally)
 	  <filename>slip.logout</filename>, which undoes
 	  <filename>slip.login</filename>'s effects when the serial
 	  connection is terminated.</para>
 
         <sect4>
 	  <title><filename>slip.hosts</filename> Configuration</title>
 
 	  <para><filename>/etc/sliphome/slip.hosts</filename> contains
 	    lines which have at least four items separated by
 	    whitespace:</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>SLIP user's login ID</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Local address (local to the SLIP server) of the SLIP
 		link</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Remote address of the SLIP link</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Network mask</para>
 	    </listitem>
 	  </itemizedlist>
 
 	  <para>The local and remote addresses may be host names
 	    (resolved to IP addresses by
 	    <filename>/etc/hosts</filename> or by the domain name
 	    service, depending on your specifications in the file
 	    <filename>/etc/nsswitch.conf</filename>,
 	    or in <filename>/etc/host.conf</filename>
 	    if you use FreeBSD&nbsp;4.X), and the network mask may be
 	    a name that can be resolved by a lookup into
 	    <filename>/etc/networks</filename>.  On a sample system,
 	    <filename>/etc/sliphome/slip.hosts</filename> looks like
 	    this:</para>
 
 	  <programlisting>#
 # login local-addr      remote-addr     mask            opt1    opt2
 #                                               (normal,compress,noicmp)
 #
 Shelmerg  dc-slip       sl-helmerg      0xfffffc00      autocomp</programlisting>
 
 	  <para>At the end of the line is one or more of the
 	    options:</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para><option>normal</option> &mdash; no header
 		compression</para>
 	    </listitem>
 
 	    <listitem>
 	      <para><option>compress</option> &mdash; compress
 		headers</para>
 	    </listitem>
 
 	    <listitem>
 	      <para><option>autocomp</option> &mdash; compress headers if
 		the remote end allows it</para>
 	    </listitem>
 
 	    <listitem>
 	      <para><option>noicmp</option> &mdash; disable ICMP packets
 		(so any <quote>ping</quote> packets will be dropped instead
 		of using up your bandwidth)</para>
 	    </listitem>
 	  </itemizedlist>
 
   	  <indexterm><primary>SLIP</primary></indexterm>
   	  <indexterm><primary>TCP/IP networking</primary></indexterm>
 	  <para>Your choice of local and remote addresses for your SLIP
 	    links depends on whether you are going to dedicate a TCP/IP
 	    subnet or if you are going to use <quote>proxy ARP</quote> on
 	    your SLIP server (it is not <quote>true</quote> proxy ARP, but
 	    that is the terminology used in this section to describe it).
 	    If you are not sure which method to select or how to assign IP
 	    addresses, please refer to the TCP/IP books referenced in
 	    the SLIP Prerequisites (<xref linkend="slips-prereqs"/>)
 	    and/or consult your IP network manager.</para>
 
 	  <para>If you are going to use a separate subnet for your SLIP
 	    clients, you will need to allocate the subnet number out of
 	    your assigned IP network number and assign each of your SLIP
 	    client's IP numbers out of that subnet.  Then, you will
 	    probably need to configure a static route to the SLIP
 	    subnet via your SLIP server on your nearest IP router.</para>
 
   	  <indexterm><primary>Ethernet</primary></indexterm>
 	  <para>Otherwise, if you will use the <quote>proxy ARP</quote>
 	    method, you will need to assign your SLIP client's IP
 	    addresses out of your SLIP server's Ethernet subnet, and you
 	    will also need to adjust your
 	    <filename>/etc/sliphome/slip.login</filename> and
 	    <filename>/etc/sliphome/slip.logout</filename> scripts to use
 	    &man.arp.8; to manage the proxy-ARP entries in the SLIP
 	    server's ARP table.</para>
 	</sect4>
 
 	<sect4>
 	  <title><filename>slip.login</filename> Configuration</title>
 
 	  <para>The typical <filename>/etc/sliphome/slip.login</filename>
 	    file looks like this:</para>
 
 	  <programlisting>#!/bin/sh -
 #
 #       @(#)slip.login  5.1 (Berkeley) 7/1/90
 
 #
 # generic login file for a slip line.  sliplogin invokes this with
 # the parameters:
 #      1        2         3        4          5         6     7-n
 #   slipunit ttyspeed loginname local-addr remote-addr mask opt-args
 #
 /sbin/ifconfig sl$1 inet $4 $5 netmask $6</programlisting>
 
 	  <para>This <filename>slip.login</filename> file merely runs
 	    <command>ifconfig</command> for the appropriate SLIP interface
 	    with the local and remote addresses and network mask of the
 	    SLIP interface.</para>
 
 	  <para>If you have decided to use the <quote>proxy ARP</quote>
 	    method (instead of using a separate subnet for your SLIP
 	    clients), your <filename>/etc/sliphome/slip.login</filename>
 	    file will need to look something like this:</para>
 
 	  <programlisting>#!/bin/sh -
 #
 #       @(#)slip.login  5.1 (Berkeley) 7/1/90
 
 #
 # generic login file for a slip line.  sliplogin invokes this with
 # the parameters:
 #      1        2         3        4          5         6     7-n
 #   slipunit ttyspeed loginname local-addr remote-addr mask opt-args
 #
 /sbin/ifconfig sl$1 inet $4 $5 netmask $6
 # Answer ARP requests for the SLIP client with our Ethernet addr
 /usr/sbin/arp -s $5 00:11:22:33:44:55 pub</programlisting>
 
 	  <para>The additional line in this
 	    <filename>slip.login</filename>, <command>arp -s
 	    &#36;5 00:11:22:33:44:55 pub</command>, creates an ARP entry
 	    in the SLIP server's ARP table.  This ARP entry causes the
 	    SLIP server to respond with the SLIP server's Ethernet MAC
 	    address whenever another IP node on the Ethernet asks to
 	    speak to the SLIP client's IP address.</para>
 
   	  <indexterm><primary>Ethernet</primary><secondary>MAC address</secondary></indexterm>
 	  <para>When using the example above, be sure to replace the
 	    Ethernet MAC address (<hostid
 	    role="mac">00:11:22:33:44:55</hostid>) with the MAC address of
 	    your system's Ethernet card, or your <quote>proxy ARP</quote>
 	    will definitely not work!  You can discover your SLIP server's
 	    Ethernet MAC address by looking at the results of running
 	    <command>netstat -i</command>; the second line of the output
 	    should look something like:</para>
 
 	  <screen>ed0   1500  &lt;Link&gt;0.2.c1.28.5f.4a         191923	0   129457     0   116</screen>
 
 	  <para>This indicates that this particular system's Ethernet MAC
 	    address is <hostid role="mac">00:02:c1:28:5f:4a</hostid>
 	    &mdash; the periods in the Ethernet MAC address given by
 	    <command>netstat -i</command> must be changed to colons and
 	    leading zeros should be added to each single-digit hexadecimal
 	    number to convert the address into the form that &man.arp.8;
 	    desires; see the manual page on &man.arp.8; for complete
 	    information on usage.</para>
 
 	  <note>
 	    <para>When you create
 	      <filename>/etc/sliphome/slip.login</filename> and
 	      <filename>/etc/sliphome/slip.logout</filename>, the
 	      <quote>execute</quote> bit (i.e., <command>chmod 755
 	      /etc/sliphome/slip.login /etc/sliphome/slip.logout</command>)
 	      must be set, or <command>sliplogin</command> will be unable
 	      to execute it.</para>
 	  </note>
 	</sect4>
 
 	<sect4>
 	  <title><filename>slip.logout</filename> Configuration</title>
 
 	  <para><filename>/etc/sliphome/slip.logout</filename> is not
 	    strictly needed (unless you are implementing <quote>proxy
 	    ARP</quote>), but if you decide to create it, this is an
 	    example of a basic
 	    <filename>slip.logout</filename> script:</para>
 
 	  <programlisting>#!/bin/sh -
 #
 #       slip.logout
 
 #
 # logout file for a slip line.  sliplogin invokes this with
 # the parameters:
 #      1        2         3        4          5         6     7-n
 #   slipunit ttyspeed loginname local-addr remote-addr mask opt-args
 #
 /sbin/ifconfig sl$1 down</programlisting>
 
 	  <para>If you are using <quote>proxy ARP</quote>, you will want to
 	    have <filename>/etc/sliphome/slip.logout</filename> remove the
 	    ARP entry for the SLIP client:</para>
 
 	  <programlisting>#!/bin/sh -
 #
 #       @(#)slip.logout
 
 #
 # logout file for a slip line.  sliplogin invokes this with
 # the parameters:
 #      1        2         3        4          5         6     7-n
 #   slipunit ttyspeed loginname local-addr remote-addr mask opt-args
 #
 /sbin/ifconfig sl$1 down
 # Quit answering ARP requests for the SLIP client
 /usr/sbin/arp -d $5</programlisting>
 
 	  <para>The <command>arp -d &#36;5</command> removes the ARP entry
 	    that the <quote>proxy ARP</quote>
 	    <filename>slip.login</filename> added when the SLIP client
 	    logged in.</para>
 
 	  <para>It bears repeating: make sure
 	    <filename>/etc/sliphome/slip.logout</filename> has the execute
 	    bit set after you create it (i.e., <command>chmod 755
 	    /etc/sliphome/slip.logout</command>).</para>
 	</sect4>
       </sect3>
 
       <sect3>
 	<title>Routing Considerations</title>
 	<indexterm>
     <primary>SLIP</primary>
     <secondary>routing</secondary>
   </indexterm>
 	<para>If you are not using the <quote>proxy ARP</quote> method for
 	  routing packets between your SLIP clients and the rest of your
 	  network (and perhaps the Internet), you will probably
 	  have to add static routes to your closest default router(s) to
 	  route your SLIP clients subnet via your SLIP server.</para>
 
 	<sect4>
 	  <title>Static Routes</title>
 	  <indexterm><primary>static routes</primary></indexterm>
 
 	  <para>Adding static routes to your nearest default routers
 	    can be troublesome (or impossible if you do not have
 	    authority to do so...).  If you have a multiple-router
 	    network in your organization, some routers, such as those
 	    made by Cisco and Proteon, may not only need to be
 	    configured with the static route to the SLIP subnet, but
 	    also need to be told which static routes to tell other
 	    routers about, so some expertise and
 	    troubleshooting/tweaking may be necessary to get
 	    static-route-based routing to work.</para>
 	</sect4>
 
 	<sect4>
 	  <title>Running <application>&gated;</application></title>
 	  <indexterm>
       <primary><application>&gated;</application></primary>
     </indexterm>
 
 	<note>
 	  <para><application>&gated;</application> is proprietary software now and
 	    will not be available as source code to the public anymore
 	    (more info on the <ulink
 	    url="http://www.gated.org/">&gated;</ulink> website). This
 	    section only exists to ensure backwards compatibility for
 	    those that are still using an older version.</para>
 	</note>
 
 	  <para>An alternative to the headaches of static routes is to
 	    install <application>&gated;</application> on your FreeBSD SLIP server
 	    and configure it to use the appropriate routing protocols
 	    (RIP/OSPF/BGP/EGP) to tell other routers about your SLIP
 	    subnet.
 	    You will need to write a <filename>/etc/gated.conf</filename>
 	    file to configure your <application>&gated;</application>; here is a sample, similar to
 	    what the author used on a FreeBSD SLIP server:</para>
 
 	  <programlisting>#
 # gated configuration file for dc.dsu.edu; for gated version 3.5alpha5
 # Only broadcast RIP information for xxx.xxx.yy out the ed Ethernet interface
 #
 #
 # tracing options
 #
 traceoptions "/var/tmp/gated.output" replace size 100k files 2 general ;
 
 rip yes {
   interface sl noripout noripin ;
   interface ed ripin ripout version 1 ;
   traceoptions route ;
 } ;
 
 #
 # Turn on a bunch of tracing info for the interface to the kernel:
 kernel {
   traceoptions remnants request routes info interface ;
 } ;
 
 #
 # Propagate the route to xxx.xxx.yy out the Ethernet interface via RIP
 #
 
 export proto rip interface ed {
   proto direct {
       <replaceable>xxx.xxx.yy</replaceable> mask 255.255.252.0 metric 1; # SLIP connections
   } ;
 } ;
 
 #
 # Accept routes from RIP via ed Ethernet interfaces
 
 import proto rip interface ed {
   all ;
 } ;</programlisting>
 
           <indexterm><primary>RIP</primary></indexterm>
 	  <para>The above sample <filename>gated.conf</filename> file
 	    broadcasts routing information regarding the SLIP subnet
 	    <replaceable>xxx.xxx.yy</replaceable> via RIP onto the
 	    Ethernet; if you are using a different Ethernet driver than
 	    the <devicename>ed</devicename> driver, you will need to
 	    change the references to the <devicename>ed</devicename>
 	    interface appropriately.  This sample file also sets up
 	    tracing to <filename>/var/tmp/gated.output</filename> for
 	    debugging <application>&gated;</application>'s activity; you can
 	    certainly turn off the tracing options if
 	    <application>&gated;</application> works correctly for you.  You will need to
 	    change the <replaceable>xxx.xxx.yy</replaceable>'s into the
 	    network address of your own SLIP subnet (be sure to change the
 	    net mask in the <literal>proto direct</literal> clause as
 	    well).</para>
 
 	  <para>Once you have installed and configured
 	    <application>&gated;</application> on your system, you will need to
 	    tell the FreeBSD startup scripts to run
 	    <application>&gated;</application> in place of
 	    <application>routed</application>.  The easiest way to accomplish
 	    this is to set the <varname>router</varname> and
 	    <varname>router_flags</varname> variables in
 	    <filename>/etc/rc.conf</filename>.  Please see the manual
 	    page for <application>&gated;</application> for information on
 	    command-line parameters.</para>
         </sect4>
       </sect3>
     </sect2>
   </sect1>
 </chapter>
diff --git a/zh_TW.Big5/books/handbook/printing/chapter.xml b/zh_TW.Big5/books/handbook/printing/chapter.xml
index acec03c739..4e07ddb9f0 100644
--- a/zh_TW.Big5/books/handbook/printing/chapter.xml
+++ b/zh_TW.Big5/books/handbook/printing/chapter.xml
@@ -1,4834 +1,4803 @@
 <?xml version="1.0" encoding="big5"?>
 <!--
      The FreeBSD Traditional Chinese Documentation Project
 
      $FreeBSD$
      Original revision: 1.96
 -->
 
 <chapter id="printing">
   <chapterinfo>
     <authorgroup>
       <author>
 	<firstname>Sean</firstname>
 	<surname>Kelly</surname>
 	<contrib>Contributed by </contrib>
       </author>
       <!-- 30 Sept 1995 -->
     </authorgroup>
     <authorgroup>
       <author>
 	<firstname>Jim</firstname>
 	<surname>Mock</surname>
 	<contrib>Restructured and updated by </contrib>
 	<!-- Mar 2000 -->
       </author>
     </authorgroup>
   </chapterinfo>
 
   <title>�C�L</title>
 
   <sect1 id="printing-synopsis">
     <title>���z</title>
     <indexterm><primary>LPD spooling system</primary></indexterm>
     <indexterm><primary>LPD �w�Ĩt��</primary></indexterm>
     <indexterm><primary>printing</primary></indexterm>
     <indexterm><primary>�C�L</primary></indexterm>
 
     <para>FreeBSD �i�H�M�U���U�˪��L�����f�t�C�L�A
       �q�̦Ѫ����w���L������̷s���p�g�L�������S���D�A
       ���z�����ε{���i�H���ͥX���~�誺���C�L��X�C</para>
 
     <para>�]�i�H�� FreeBSD �]�w���@�x�����C�L���A���F�o�ɭԪ� FreeBSD
       �౵����L�q���e�Ӫ��C�L�u�@�A�]�A��L FreeBSD ���q���B&windows;
       ���q���H�� &macos; ���q���C  FreeBSD
       �|�T�O�P�ɥu���@���󥿦b�C�L�A�ӥB�i�H�έp���ӨϥΪ̤ξ����L�o�̦h�A
       �٦��N�O�L�X���U�ӬO�֪����o����<quote>���D</quote>�����C</para>
 
     <para>Ū���o���A�z�N�F�ѡG</para>
 
     <itemizedlist>
       <listitem>
 	<para>�p��]�w FreeBSD ���C�L�h�u�w�ijB�z���C</para>
       </listitem>
 
       <listitem>
 	<para>�p��w�˦C�L�L�o���H���O�B�z�S�����C�L�u�@�A
 	  �]�A�⦬�쪺����ഫ���z���L�����ݱo�����C�L�榡���C</para>
       </listitem>
 
       <listitem>
 	<para>�F�Ѧp��b�z�C�L�ɶ��K�L�X�����μ��D�C</para>
       </listitem>
 
       <listitem>
 	<para>�p��Q�ΧO�x�q���W���L�����C�L�C</para>
       </listitem>
 
       <listitem>
 	<para>�p��Q�������b�����W���L�����C�L�C</para>
       </listitem>
 
       <listitem>
 	<para>�p�󱱨�L�������v���A�]�A����C�L�u�@���ɮפj�p�A
 	  �H�Τ����\�S�w�ϥΪ̦C�L���C</para>
       </listitem>
 
       <listitem>
 	<para>�p��O�U�L�������έp��ơA�H�ΦU�b�����L�����ϥζq�C</para>
       </listitem>
 
       <listitem>
 	<para>�p��ѨM�C�L�ɹJ�쪺���D�C</para>
       </listitem>
     </itemizedlist>
 
     <para>�b�}�l�\Ū�o�����e�A�z�ݭn�J</para>
 
     <itemizedlist>
       <listitem>
 	<para>�n���]�w�B�sĶ kernel ����¦����
 	  (<xref linkend="kernelconfig"/>)�C</para>
       </listitem>
     </itemizedlist>
   </sect1>
 
   <sect1 id="printing-intro-spooler">
     <title>����</title>
 
     <para>�n�b FreeBSD �W�ϥΦL�����A�z�ݭn�]�w�n Berkeley
       ��C���L�����C�L�w�Ĩt�ΡA�S�٬� <application>LPD</application>
       �C�L�w�Ĩt�ΡA�Ϊ̴N�s�L <application>LPD</application> �a�C
       �o�O FreeBSD �зǪ��L��������t�ΡA�����|���Шñбz�p��]�w
       <application>LPD</application>�C</para>
 
     <para>�p�G�z�w�g�� <application>LPD</application>
       �άO��L�C�L�w�Ĩt�Ϋܼ��x�F�A
       �z�i�H��������<link linkend="printing-intro-setup">�򥻳]�w</link>�C
       </para>
 
     <para><application>LPD</application> ����ۥD���W�L�������@���C
       ���t�d�o�Ǥu�@�G</para>
 
     <itemizedlist>
       <listitem>
 	<para>������κ����L�������ϥΡC</para>
       </listitem>
 
       <listitem>
-	<indexterm><primary>print jobs</primary></indexterm>
-
-	<para>���ϥΪ̥i�H�C�L���A�e�X�����٬�<emphasis>�u�@</emphasis>�C
+	<para>���ϥΪ̥i�H�C�L���A�e�X�����٬�<emphasis>�u�@</emphasis>�C<indexterm><primary>print jobs</primary></indexterm>
 	  </para>
       </listitem>
 
       <listitem>
 	<para>���C�x�L�����dzƤ@��<emphasis>��C</emphasis>�A
 	  �קK�h�ӨϥΪ̦P�ɨϥΦP�@�x�L�����C</para>
       </listitem>
 
       <listitem>
 	<para>�C�L <emphasis>header pages</emphasis> (�S�٬�
 	  <emphasis>banner</emphasis> or <emphasis>burst</emphasis>
 	  pages)�A��K�ϥΪ̦b�X�ȹh�����ۤw�C�L�����C</para>
       </listitem>
 
       <listitem>
 	<para>�Ⱶ�b��C��W���L�������q�T�ѼƳ]�w�n�C</para>
       </listitem>
 
       <listitem>
 	<para>�Q�κ����ǰe�C�L�u�@���O�x�D���W��
 	  <application>LPD</application>�C</para>
       </listitem>
 
       <listitem>
 	<para>����S�O���L�o�{���N�C�L�u�@�榡�ƥH�t�X���P���C�L�y���ΦL�����C
 	  </para>
       </listitem>
 
       <listitem>
 	<para>�έp�L�������ϥα��p�C</para>
       </listitem>
     </itemizedlist>
 
     <para>�ǥѳ]�w�� (<filename>/etc/printcap</filename>) �H�ιL�o�{�������U�A
       �z�i�H���j�h�ƪ��L�����t�X <application>LPD</application>
       �F���W�z����������\��C</para>
 
     <sect2 id="printing-intro-why">
       <title>������ݭn�ϥΦh�u�w�ijB�z��</title>
 
       <para>�p�G�z���t�άO�ӤH�ϥΡA
 	���ݭn����s���v���B�C�L���D���Ϊ̲έp�ϥα��p���\��ɡA
 	�z�i��|ı�o�ܩ_�Ǭ������ٻݭn�h�޳o�Ӧh�u�w�ijB�z���C
 	���M�n��������L�����i�檺�A
 	���L�L�צp��z�٬O�ݭn�h�u�w�ijB�z���A�]���G</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><application>LPD</application> �i�H�b�I�� (background)
 	    �C�L�A�z���ݭn�b���䵥���e��L�����C</para>
 	</listitem>
 
 	<listitem>
-	  <indexterm><primary>&tex;</primary></indexterm>
-
 	  <para><application>LPD</application> �i�H�ܻ��P�a�ιL�o���W�[��� /
-	    �ɶ��󭶭��άO��S�O���ɮ׮榡 (���O &tex; DVI ��)
+	    �ɶ��󭶭��άO��S�O���ɮ׮榡 (���O &tex;<indexterm><primary>&tex;</primary></indexterm> DVI ��)
 	    �ഫ���L�����ݱo�������榡�A�z���ݭn��ʥh���o�ǨB�J�C</para>
 	</listitem>
 
 	<listitem>
 	  <para>�\�h�K�O�ΰӷ~�n�鴣�Ѫ��C�L�\��q�`���O�M�h�u�w�ijB�z�����q�C
 	    �z�L�]�w�w�Ĩt�ΡA�䴩�z�{���άO�Y�N�n�w�˪���L�n��N�ܱo��e���C
 	    </para>
 	</listitem>
       </itemizedlist>
     </sect2>
   </sect1>
 
   <sect1 id="printing-intro-setup">
     <title>��¦�]�w</title>
 
     <para>�n�ΦL�����f�t <application>LPD</application>
       �h�u�w�Ĩt�ΡA�z�ݭn���L�����o�ӵw��H��
       <application>LPD</application> �o�M�n��C
       ����U���ѤF�ⶥ�q���]�w�����G</para>
 
     <itemizedlist>
       <listitem>
 	<para>�\Ū <link linkend="printing-simple">²���L�����]�w</link>
 	  �ӾDzߦp��s���L�����B���L�����M <application>LPD</application>
 	  ���q�H�ΦC�L�¤�r���C</para>
       </listitem>
 
       <listitem>
 	<para>�\Ū <link linkend="printing-advanced">�i���L�����]�w</link>
 	  �ӾDzߦp��C�L�U�دS���榡���B�C�L�����B�����C�L�B
 	  ����L�����v���H�βέp�ϥΪ��p���C</para>
       </listitem>
     </itemizedlist>
 
     <sect2 id="printing-simple">
       <title>²���L�����]�w</title>
 
       <para>�����`�|�i�D�z�p��]�w�L�����]�ƩM
 	<application>LPD</application> �n��H�ϥΦL�����A
 	  �򥻱оǤ��e�G</para>
 
       <itemizedlist>
 	<listitem>
 	  <para><link linkend="printing-hardware">�w��]�w</link>
 	    �|���ܦp��N�L�������W�q�����s����C</para>
 	</listitem>
 
 	<listitem>
 	  <para><link linkend="printing-software">�n��]�w</link>
 	    �|�ܽd�p��g <application>LPD</application> �w�ľ��]�w��
 	    (<filename>/etc/printcap</filename>)�C</para>
 	</listitem>
       </itemizedlist>
 
       <para>�p�G�z�n��L�����]�w���������C�L��ƦӤ��O�����ݪ��ܡA�аѦ�
 	<link linkend="printing-advanced-network-net-if">
 	�L�����κ�����ƶǿ餶��</link>�C</para>
 
       <para>�o�ӳ��`���M�s��<quote>²���L�����]�w</quote>�A
         ��ڤW�٬O���I�������C �̧x���������O���A���L�����M�q���W��
 	<application>LPD</application> �w�ľ�������`�B�@�C
 	  �@���L�����i�H���`�u�@����A
 	  ���O�L�����άO���C�L�έp�o�Ƕi�����\��N��������F�C
 	  </para>
 
       <sect3 id="printing-hardware">
 	<title>�w��]�w</title>
 
 	<para>�����`�Q�צU�سs���L������ PC ���覡�C
 	  �o�̷|���줣�P�������s����M�s���u�A
 	  �H�ά��F�� FreeBSD ��M�L�������q�z�i��|�ݭn�}�Ҫ��֤߰ѼƵ��C
 	  </para>
 
 	<para>�p�G�z�w�g��L�������W�q���A
 	  �ӥB�b��L�@�~�t�ΤW�����\�C�L�L���ܡA�i�H��������
 	  <link linkend="printing-software">�n��]�w</link>�C</para>
 
 	<sect4 id="printing-ports">
 	  <title>�s����M�ƽu</title>
 
 	  <para>����ӤH�q���L�����@��ӻ����X�o�T�جɭ��G</para>
 
 	  <itemizedlist>
-	    <indexterm>
-        <primary>printers</primary>
-        <secondary>serial</secondary>
-      </indexterm>
 	    <listitem>
-	      <para><emphasis>�ǦC (Serial)</emphasis>
+	      <para><emphasis>�ǦC (Serial)</emphasis><indexterm><primary>printers</primary><secondary>serial</secondary></indexterm>
 		�ɭ��A�S�٬� RS-232 �� COM ��A
 		�αz�q���W���ǦC��ǰe��ƨ�L�����C
 		�ǦC�ɭ��s�x�����q���~�ɩұĥΡA
 		�ҥH�ƽu�e�����o�A�n�]�w�s�u�ä��x���C
 		�M�ӧǦC�������ɭԷ|�ݭn�ϥθ��S�O���ƽu�A
 		�o�ɭԴN���i��ݭn�]�w�@�Ǹ����������q�T�ѼƤF�C
 		�j���� PC �ǦC�𪺶ǿ�t�׳̰��u�� 115200&nbsp;bps�A
 		�]���Q�n�ΧǦC��ӦC�L�j�ϬO������ڪ��C</para>
 	    </listitem>
 
 	    <listitem>
-	      <indexterm>
-		<primary>printers</primary>
-		<secondary>parallel</secondary>
-	       </indexterm>
-
-	      <para><emphasis>�æC (Parallel)</emphasis>
+	      <para><emphasis>�æC (Parallel)</emphasis><indexterm><primary>printers</primary><secondary>parallel</secondary></indexterm>
 		�ɭ��Q�ιq�����æC��N��ưe��L�����C
 		�æC��� RS-232 �ǦC���٧֡A�]�O�@�عq���~�ɱ`�Ϊ��ɭ��C
 		�o�جɭ����ƽu�D�`�e�����o�A���O�����Τ�u���y�C
 		�q�`�ӻ��æC�ɭ��èS������q�T�Ѽƻݭn���w�A
 		�ҥH�]�w�_�ӶW�Ůe���C</para>
 
-	      <indexterm>
-	        <primary>centronics</primary>
-		<see>parallel printers</see>
-	      </indexterm>
-	      <para>�æC��ɭ����ɭԤ]�|�Q�٬� <quote>Centronics</quote>
+	      <para>�æC��ɭ����ɭԤ]�|�Q�٬� <quote>Centronics</quote><indexterm><primary>centronics</primary><see>parallel printers</see></indexterm>
 		�ɭ��A�o�O�L���������Y���W�١C</para>
 	    </listitem>
 
 	    <listitem>
-	      <indexterm>
-		<primary>printers</primary>
-		<secondary>USB</secondary>
-	      </indexterm>
-
-	      <para>USB �ɭ��A�]�N�O�q�ΧǦC�׬y�ơA�ǿ�t�v��æC�ɭ��άO
+	      <para>USB<indexterm><primary>printers</primary><secondary>USB</secondary></indexterm> �ɭ��A�]�N�O�q�ΧǦC�׬y�ơA�ǿ�t�v��æC�ɭ��άO
 		RS-232 �ǦC�ɭ����ӱo�֡A�ӥB USB �ƽu��¤S�K�y�C
 		��C�L�u�@�Ө��AUSB �� RS-232
 		�ǦC��άO�æC�𳣨ӱo�n�A���O�b
 		&unix; �t�ΤW���䴩�׸��t�C �ʶR�P�ɨ㦳 USB
 		�ΨæC���جɭ����L�����i�H�קK���o�ذ��D�C</para>
 	    </listitem>
 	  </itemizedlist>
 
 	  <para>�@��Ө��A�æC�ɭ��u�ണ�ѳ�V�ǿ�
 	    (�q���ܦL����)�A�ӭn�� USB �~�ണ�����V�C �M�Ӧb FreeBSD
 	    �U�A�ϥθ��s���æC�� (EPP �M ECP) �H�ΦL�����A�A�t�X�ϥ�
 	    IEEE-1284 �ۮe�ƽu�]�i�H�������V���q�C</para>
 
 	  <indexterm><primary>PostScript</primary></indexterm>
 
 	  <para>�q���M�L���������ǥѨæC���i���V���q���覡����ءC
 	    �Ĥ@�جO�ϥίS�s���B��M�S�w�L�������q�� FreeBSD �L�����X�ʵ{���C
 	    �o�ؤ覡�b�Q���L�����W�ܱ`���A�ΨӦ^�������s�q�H�Ψ�L���A��T���C
 	    �ĤG�ؤ�k�O�� &postscript;�A�p�G�L�������䴩���ܡC</para>
 
 	  <para>&postscript; jobs are
 	    actually programs sent to the printer; they need not produce
 	    paper at all and may return results directly to the computer.
 	    &postscript; also uses two-way communication to tell the
 	    computer about problems, such as errors in the &postscript;
 	    program or paper jams.  Your users may be appreciative of such
 	    information.  Furthermore, the best way to do effective
 	    accounting with a &postscript; printer requires two-way
 	    communication: you ask the printer for its page count (how
 	    many pages it has printed in its lifetime), then send the
 	    user's job, then ask again for its page count.  Subtract the
 	    two values and you know how much paper to charge to the
 	    user.</para>
 	</sect4>
 
 	<sect4 id="printing-parallel">
 	  <title>Parallel Ports</title>
 
 	  <para>To hook up a printer using a parallel interface, connect
 	    the Centronics cable between the printer and the computer.
 	    The instructions that came with the printer, the computer, or
 	    both should give you complete guidance.</para>
 
 	  <para>Remember which parallel port you used on the computer.
 	    The first parallel port is <filename>ppc0</filename> to
 	    FreeBSD; the second is <filename>ppc1</filename>, and so
 	    on.  The printer device name uses the same scheme:
 	    <filename>/dev/lpt0</filename> for the printer on the first
 	    parallel ports etc.</para>
 	</sect4>
 
 	<sect4 id="printing-serial">
 	  <title>Serial Ports</title>
 
 	  <para>To hook up a printer using a serial interface, connect the
 	    proper serial cable between the printer and the computer.  The
 	    instructions that came with the printer, the computer, or both
 	    should give you complete guidance.</para>
 
 	  <para>If you are unsure what the <quote>proper serial
 	    cable</quote> is, you may wish to try one of the following
 	    alternatives:</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>A <emphasis>modem</emphasis> cable connects each pin
 		of the connector on one end of the cable straight through
 		to its corresponding pin of the connector on the other
 		end.  This type of cable is also known as a
 		<quote>DTE-to-DCE</quote> cable.</para>
 	    </listitem>
 
 	    <listitem>
-	      <indexterm><primary>null-modem cable</primary></indexterm>
-
-	      <para>A <emphasis>null-modem</emphasis> cable connects some
+	      <para>A <emphasis>null-modem</emphasis><indexterm><primary>null-modem cable</primary></indexterm> cable connects some
 		pins straight through, swaps others (send data to receive
 		data, for example), and shorts some internally in each
 		connector hood.  This type of cable is also known as a
 		<quote>DTE-to-DTE</quote> cable.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>A <emphasis>serial printer</emphasis> cable, required
 		for some unusual printers, is like the null-modem cable,
 		but sends some signals to their counterparts instead of
 		being internally shorted.</para>
 	    </listitem>
 	  </itemizedlist>
 
 	  <indexterm><primary>baud rate</primary></indexterm>
 	  <indexterm><primary>parity</primary></indexterm>
 	  <indexterm><primary>flow control protocol</primary></indexterm>
 	  <para>You should also set up the communications parameters for
 	    the printer, usually through front-panel controls or DIP
 	    switches on the printer.  Choose the highest
 	    <literal>bps</literal> (bits per second, sometimes
 	    <emphasis>baud rate</emphasis>) that both your computer
 	    and the printer can support.  Choose 7 or 8 data bits; none,
 	    even, or odd parity; and 1 or 2 stop bits.  Also choose a flow
 	    control protocol:  either none, or XON/XOFF (also known as
 	    <quote>in-band</quote> or <quote>software</quote>) flow control.
 	    Remember these settings for the software configuration that
 	    follows.</para>
 	</sect4>
       </sect3>
 
       <sect3 id="printing-software">
 	<title>Software Setup</title>
 
 	<para>This section describes the software setup necessary to print
 	  with the <application>LPD</application> spooling system in FreeBSD.
 	</para>
 
 	<para>Here is an outline of the steps involved:</para>
 
 	<procedure>
 	  <step>
 	    <para>Configure your kernel, if necessary, for the port you
 	      are using for the printer; section <link
 	      linkend="printing-kernel">Kernel Configuration</link> tells
 	      you what you need to do.</para>
 	  </step>
 
 	  <step>
 	    <para>Set the communications mode for the parallel port, if
 	      you are using a parallel port; section <link
 	      linkend="printing-parallel-port-mode">Setting the
 	      Communication Mode for the Parallel Port</link> gives
 	      details.</para>
 	  </step>
 
 	  <step>
 	    <para>Test if the operating system can send data to the printer.
 	      Section <link linkend="printing-testing">Checking Printer
 	      Communications</link> gives some suggestions on how to do
 	      this.</para>
 	  </step>
 
 	  <step>
 	    <para>Set up <application>LPD</application> for the printer by
 	      modifying the file
 	      <filename>/etc/printcap</filename>.  You will find out how
 	      to do this later in this chapter.</para>
 	  </step>
 	</procedure>
 
 	<sect4 id="printing-kernel">
 	  <title>Kernel Configuration</title>
 
 	  <para>The operating system kernel is compiled to work with a
 	    specific set of devices.  The serial or parallel interface for
 	    your printer is a part of that set.  Therefore, it might be
 	    necessary to add support for an additional serial or parallel
 	    port if your kernel is not already configured for one.</para>
 
 	  <para>To find out if the kernel you are currently using supports
 	    a serial interface, type:</para>
 
 	  <screen>&prompt.root; <userinput>grep sio<replaceable>N</replaceable> /var/run/dmesg.boot</userinput></screen>
 
 	  <para>Where <replaceable>N</replaceable> is the number of the
 	    serial port, starting from zero.  If you see output similar to
 	    the following:</para>
 
 	  <screen>sio2 at port 0x3e8-0x3ef irq 5 on isa
 sio2: type 16550A</screen>
 
 	  <para>then the kernel supports the port.</para>
 
 	  <para>To find out if the kernel supports a parallel interface,
 	    type:</para>
 
 	  <screen>&prompt.root; <userinput>grep ppc<replaceable>N</replaceable> /var/run/dmesg.boot</userinput></screen>
 
 	  <para>Where <replaceable>N</replaceable> is the number of the
 	    parallel port, starting from zero.  If you see output similar
 	    to the following:</para>
 
 	    <screen>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/8 bytes threshold</screen>
 
 	    <para>then the kernel supports the port.</para>
 
 	  <para>You might have to reconfigure your kernel in order for the
 	    operating system to recognize and use the parallel or serial
 	    port you are using for the printer.</para>
 
 	  <para>To add support for a serial port, see the section on
 	    kernel configuration.  To add support for a parallel port, see
 	    that section <emphasis>and</emphasis> the section that
 	    follows.</para>
 	</sect4>
       </sect3>
 	<sect3 id="printing-parallel-port-mode">
 	  <title>Setting the Communication Mode for the Parallel
 	    Port</title>
 
 	  <para>When you are using the parallel interface, you can choose
 	    whether FreeBSD should use interrupt-driven or polled
 	    communication with the printer.  The generic printer
 	    device driver (&man.lpt.4;) on FreeBSD
 	    uses the &man.ppbus.4; system, which controls the port
 	    chipset with the &man.ppc.4; driver.</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>The <emphasis>interrupt-driven</emphasis> method is
 		the default with the GENERIC kernel.  With this method,
 		the operating system uses an IRQ line to determine when
 		the printer is ready for data.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>The <emphasis>polled</emphasis> method directs the
 		operating system to repeatedly ask the printer if it is
 		ready for more data.  When it responds ready, the kernel
 		sends more data.</para>
 	    </listitem>
 	  </itemizedlist>
 
 	  <para>The interrupt-driven method is usually somewhat faster
 	    but uses up a precious IRQ line.  Some newer HP printers
 	    are claimed not to work correctly in interrupt mode,
 	    apparently due to some (not yet exactly understood) timing
 	    problem.  These printers need polled mode.  You should use
 	    whichever one works.  Some printers will work in both
 	    modes, but are painfully slow in interrupt mode.</para>
 
 	  <para>You can set the communications mode in two ways: by
 	    configuring the kernel or by using the &man.lptcontrol.8;
 	    program.</para>
 
 	  <para><emphasis>To set the communications mode by configuring
 	    the kernel:</emphasis></para>
 
 	  <procedure>
 	    <step>
 	      <para>Edit your kernel configuration file.  Look for
 		an <literal>ppc0</literal> entry.  If you are setting up
 		the second parallel port, use <literal>ppc1</literal>
 		instead.  Use <literal>ppc2</literal> for the third port,
 		and so on.</para>
 
 	      <itemizedlist>
 		<listitem>
 		  <para>If you want interrupt-driven mode, edit the following line:</para>
 
 		  <programlisting>hint.ppc.0.irq="<replaceable>N</replaceable>"</programlisting>
 
 		  <para>in the <filename>/boot/device.hints</filename> file
 		    and replace <replaceable>N</replaceable> with the right
 		    IRQ number.  The kernel configuration file must
 		    also contain the &man.ppc.4; driver:</para>
 
 		  <screen>device ppc</screen>
 
 		</listitem>
 
 		<listitem>
 		  <para>If you want polled mode, remove in your
 		    <filename>/boot/device.hints</filename> file, the
 		    following line:</para>
 
 		  <programlisting>hint.ppc.0.irq="<replaceable>N</replaceable>"</programlisting>
 
 		  <para>In some cases, this is not enough to put the
 		    port in polled mode under FreeBSD.  Most of
 		    time it comes from &man.acpi.4; driver, this latter
 		    is able to probe and attach devices, and therefore,
 		    control the access mode to the printer port.  You
 		    should check your &man.acpi.4; configuration to
 		    correct this problem.</para>
 		</listitem>
 	      </itemizedlist>
 	    </step>
 
 	    <step>
 	      <para>Save the file.  Then configure, build, and install the
 		kernel, then reboot.  See <link
 		linkend="kernelconfig">kernel configuration</link> for
 		more details.</para>
 	    </step>
 	  </procedure>
 
 	  <para><emphasis>To set the communications mode with</emphasis>
 	    &man.lptcontrol.8;:</para>
 
 	  <procedure>
 	    <step>
 	      <para>Type:</para>
 
 	      <screen>&prompt.root; <userinput>lptcontrol -i -d /dev/lpt<replaceable>N</replaceable></userinput></screen>
 
 	      <para>to set interrupt-driven mode for
 		<literal>lpt<replaceable>N</replaceable></literal>.</para>
 	    </step>
 
 	    <step>
 	      <para>Type:</para>
 
 	      <screen>&prompt.root; <userinput>lptcontrol -p -d /dev/lpt<replaceable>N</replaceable></userinput></screen>
 
 	      <para>to set polled-mode for
 		<literal>lpt<replaceable>N</replaceable></literal>.</para>
 	    </step>
 	  </procedure>
 
 	  <para>You could put these commands in your
 	    <filename>/etc/rc.local</filename> file to set the mode each
 	    time your system boots.  See &man.lptcontrol.8; for more
 	    information.</para>
 	</sect3>
 
 	<sect3 id="printing-testing">
 	  <title>Checking Printer Communications</title>
 
 	  <para>Before proceeding to configure the spooling system, you
 	    should make sure the operating system can successfully send
 	    data to your printer.  It is a lot easier to debug printer
 	    communication and the spooling system separately.</para>
 
 	  <para>To test the printer, we will send some text to it.  For
 	    printers that can immediately print characters sent to them,
 	    the program  &man.lptest.1; is perfect: it generates all 96
 	    printable ASCII characters in 96 lines.</para>
 
 	  <indexterm><primary>PostScript</primary></indexterm>
 	  <para>For a &postscript; (or other language-based) printer, we
 	    will need a more sophisticated test.  A small &postscript;
 	    program, such as the following, will suffice:</para>
 
 	  <programlisting>%!PS
 100 100 moveto 300 300 lineto stroke
 310 310 moveto /Helvetica findfont 12 scalefont setfont
 (Is this thing working?) show
 showpage</programlisting>
 
 	  <para>The above &postscript; code can be placed into a file and
 	    used as shown in the examples appearing in the following
 	    sections.</para>
 
 	  <indexterm><primary>PCL</primary></indexterm>
 	  <note>
 	    <para>When this document refers to a printer language, it is
 	      assuming a language like &postscript;, and not Hewlett
 	      Packard's PCL.  Although PCL has great functionality, you
 	      can intermingle plain text with its escape sequences.
 	      &postscript; cannot directly print plain text, and that is the
 	      kind of printer language for which we must make special
 	      accommodations.</para>
 	  </note>
 
 	  <sect4 id="printing-checking-parallel">
 	    <title>Checking a Parallel Printer</title>
 
 	    <indexterm>
         <primary>printers</primary>
         <secondary>parallel</secondary>
       </indexterm>
 	    <para>This section tells you how to check if FreeBSD can
 	      communicate with a printer connected to a parallel
 	      port.</para>
 
 	    <para><emphasis>To test a printer on a parallel
 	      port:</emphasis></para>
 
 	    <procedure>
 	      <step>
 		<para>Become <username>root</username> with  &man.su.1;.</para>
 	      </step>
 
 	      <step>
 		<para>Send data to the printer.</para>
 
 		<itemizedlist>
 		  <listitem>
 		    <para>If the printer can print plain text, then use
 		      &man.lptest.1;.  Type:</para>
 
 		    <screen>&prompt.root; <userinput>lptest &gt; /dev/lpt<replaceable>N</replaceable></userinput></screen>
 
 		    <para>Where <replaceable>N</replaceable> is the number
 		      of the parallel port, starting from zero.</para>
 		  </listitem>
 
 		  <listitem>
 		    <para>If the printer understands &postscript; or other
 		      printer language, then send a small program to the
 		      printer.  Type:</para>
 
 		    <screen>&prompt.root; <userinput>cat &gt; /dev/lpt<replaceable>N</replaceable></userinput></screen>
 
 		    <para>Then, line by line, type the program
 		      <emphasis>carefully</emphasis> as you cannot edit a
 		      line once you have pressed <literal>RETURN</literal>
 		      or <literal>ENTER</literal>.  When you have finished
 		      entering the program, press
 		      <literal>CONTROL+D</literal>, or whatever your end
 		      of file key is.</para>
 
 		    <para>Alternatively, you can put the program in a file
 		      and type:</para>
 
 		    <screen>&prompt.root; <userinput>cat <replaceable>file</replaceable> &gt; /dev/lpt<replaceable>N</replaceable></userinput></screen>
 
 		    <para>Where <replaceable>file</replaceable> is the
 		      name of the file containing the program you want to
 		      send to the printer.</para>
 		  </listitem>
 		</itemizedlist>
 	      </step>
 	    </procedure>
 
 	    <para>You should see something print.  Do not worry if the
 	      text does not look right; we will fix such things
 	      later.</para>
 	  </sect4>
 
 	  <sect4 id="printing-checking-serial">
 	    <title>Checking a Serial Printer</title>
 
 	    <indexterm>
         <primary>printers</primary>
         <secondary>serial</secondary>
       </indexterm>
 	    <para>This section tells you how to check if FreeBSD can
 	      communicate with a printer on a serial port.</para>
 
 	    <para><emphasis>To test a printer on a serial
 	      port:</emphasis></para>
 
 	    <procedure>
 	      <step>
 		<para>Become <username>root</username> with &man.su.1;.</para>
 	      </step>
 
 	      <step>
 		<para>Edit the file <filename>/etc/remote</filename>.  Add
 		  the following entry:</para>
 
 		<programlisting>printer:dv=/dev/<replaceable>port</replaceable>:br#<replaceable>bps-rate</replaceable>:pa=<replaceable>parity</replaceable></programlisting>
 
 		<indexterm><primary>bits-per-second</primary></indexterm>
 		<indexterm><primary>serial port</primary></indexterm>
 		<indexterm><primary>parity</primary></indexterm>
 		<para>Where <replaceable>port</replaceable> is the device
 		  entry for the serial port (<literal>ttyd0</literal>,
 		  <literal>ttyd1</literal>, etc.),
 		  <replaceable>bps-rate</replaceable> is the
 		  bits-per-second rate at which the printer communicates,
 		  and <replaceable>parity</replaceable> is the parity
 		  required by the printer (either <literal>even</literal>,
 		  <literal>odd</literal>, <literal>none</literal>, or
 		  <literal>zero</literal>).</para>
 
 		<para>Here is a sample entry for a printer connected via
 		  a serial line to the third serial port at 19200&nbsp;bps with
 		  no parity:</para>
 
 		<programlisting>printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
 	      </step>
 
 	      <step>
 		<para>Connect to the printer with &man.tip.1;.
 		  Type:</para>
 
 		<screen>&prompt.root; <userinput>tip printer</userinput></screen>
 
 		<para>If this step does not work, edit the file
 		  <filename>/etc/remote</filename> again and try using
 		  <filename>/dev/cuaa<replaceable>N</replaceable></filename>
 		  instead of
 		  <filename>/dev/ttyd<replaceable>N</replaceable></filename>.</para>
 	      </step>
 
 	      <step>
 		<para>Send data to the printer.</para>
 
 		<itemizedlist>
 		  <listitem>
 		    <para>If the printer can print plain text, then use
 		      &man.lptest.1;.  Type:</para>
 
 		    <screen>&prompt.user; <userinput>$lptest</userinput></screen>
 		  </listitem>
 
 		  <listitem>
 		    <para>If the printer understands &postscript; or other
 		      printer language, then send a small program to the
 		      printer.  Type the program, line by line,
 		      <emphasis>very carefully</emphasis> as backspacing
 		      or other editing keys may be significant to the
 		      printer.  You may also need to type a special
 		      end-of-file key for the printer so it knows it
 		      received the whole program.  For &postscript;
 		      printers, press <literal>CONTROL+D</literal>.</para>
 
 		    <para>Alternatively, you can put the program in a file
 		      and type:</para>
 
 		    <screen>&prompt.user; <userinput>&gt;<replaceable>file</replaceable></userinput></screen>
 
 		    <para>Where <replaceable>file</replaceable> is the
 		      name of the file containing the program.  After
 		      &man.tip.1; sends the file, press any required
 		      end-of-file key.</para>
 		  </listitem>
 		</itemizedlist>
 	      </step>
 	    </procedure>
 
 	    <para>You should see something print.  Do not worry if the
 	      text does not look right; we will fix that later.</para>
 	  </sect4>
 	</sect3>
 
       <sect3 id="printing-printcap">
 	<title>Enabling the Spooler: the <filename>/etc/printcap</filename>
 	  File</title>
 
 	<para>At this point, your printer should be hooked up, your kernel
 	  configured to communicate with it (if necessary), and you have
 	  been able to send some simple data to the printer.  Now, we are
 	  ready to configure <application>LPD</application> to control access
 	  to your printer.</para>
 
 	<para>You configure <application>LPD</application> by editing the file
 	  <filename>/etc/printcap</filename>.  The
 	  <application>LPD</application> spooling system
 	  reads this file each time the spooler is used, so updates to the
 	  file take immediate effect.</para>
 
 	<indexterm>
     <primary>printers</primary>
     <secondary>capabilities</secondary>
   </indexterm>
 	<para>The format of the &man.printcap.5; file is straightforward.
 	  Use your favorite text editor to make changes to
 	  <filename>/etc/printcap</filename>.  The format is identical to
 	  other capability files like
 	  <filename>/usr/share/misc/termcap</filename> and
 	  <filename>/etc/remote</filename>.  For complete information
 	  about the format, see the &man.cgetent.3;.</para>
 
 	<para>The simple spooler configuration consists of the following
 	  steps:</para>
 
 	<procedure>
 	  <step>
 	    <para>Pick a name (and a few convenient aliases) for the
 	      printer, and put them in the
 	      <filename>/etc/printcap</filename> file; see the
 	      <link linkend="printing-naming">Naming the Printer</link>
 	      section for more information on naming.</para>
 	  </step>
 
 	  <step>
-	    <indexterm><primary>header pages</primary></indexterm>
-
-	    <para>Turn off header pages (which are on by default) by
+	    <para>Turn off header pages<indexterm><primary>header pages</primary></indexterm> (which are on by default) by
 	      inserting the <literal>sh</literal> capability; see the
 	      <link linkend="printing-no-header-pages">Suppressing Header
 	      Pages</link> section for more information.</para>
 	  </step>
 
 	  <step>
 	    <para>Make a spooling directory, and specify its location with
 	      the <literal>sd</literal> capability; see the <link
 	      linkend="printing-spooldir">Making the Spooling
 	      Directory</link> section for more information.</para>
 	  </step>
 
 	  <step>
 	    <para>Set the <filename>/dev</filename> entry to use for the
 	      printer, and note it in <filename>/etc/printcap</filename>
 	      with the <literal>lp</literal> capability; see the <link
 	      linkend="printing-device">Identifying the Printer
 	      Device</link> for more information.  Also, if the printer is
 	      on a serial port, set up the communication parameters with
 	      the <literal>ms#</literal> capability which is discussed in the <link
 	      linkend="printing-commparam">Configuring Spooler
 	      Communications Parameters</link> section.</para>
 	  </step>
 
 	  <step>
 	    <para>Install a plain text input filter; see the <link
 	    linkend="printing-textfilter">Installing the Text
 	    Filter</link> section for details.</para>
 	  </step>
 
 	  <step>
 	    <para>Test the setup by printing something with the
 	      &man.lpr.1; command.  More details are available in the
 	      <link linkend="printing-trying">Trying It Out</link> and
 	      <link
 	      linkend="printing-troubleshooting">Troubleshooting</link>
 	      sections.</para>
 	  </step>
 	</procedure>
 
 	<note>
 	  <para>Language-based printers, such as &postscript; printers,
 	    cannot directly print plain text.  The simple setup outlined
 	    above and described in the following sections assumes that if
 	    you are installing such a printer you will print only files
 	    that the printer can understand.</para>
 	</note>
 
 	<para>Users often expect that they can print plain text to any of
 	  the printers installed on your system.  Programs that interface
 	  to <application>LPD</application> to do their printing usually
 	  make the same assumption.
 	  If you are installing such a printer and want to be able to
 	  print jobs in the printer language <emphasis>and</emphasis>
 	  print plain text jobs, you are strongly urged to add an
 	  additional step to the simple setup outlined above: install an
 	  automatic plain-text-to-&postscript; (or other printer language)
 	  conversion program.  The section entitled <link
 	  linkend="printing-advanced-if-conversion">Accommodating Plain
 	  Text Jobs on &postscript; Printers</link> tells how to do
 	  this.</para>
 
 	<sect4 id="printing-naming">
 	  <title>Naming the Printer</title>
 
 	  <para>The first (easy) step is to pick a name for your printer.
 	    It really does not matter whether you choose functional or
 	    whimsical names since you can also provide a number of aliases
 	    for the printer.</para>
 
 	  <para>At least one of the printers specified in the
 	    <filename>/etc/printcap</filename> should have the alias
 	    <literal>lp</literal>.  This is the default printer's name.
 	    If users do not have the <envar>PRINTER</envar> environment
 	    variable nor specify a printer name on the command line of any
 	    of the <application>LPD</application> commands,
 	    then <literal>lp</literal> will be the
 	    default printer they get to use.</para>
 
 	  <para>Also, it is common practice to make the last alias for a
 	    printer be a full description of the printer, including make
 	    and model.</para>
 
 	  <para>Once you have picked a name and some common aliases, put
 	    them in the <filename>/etc/printcap</filename> file.  The name
 	    of the printer should start in the leftmost column.  Separate
 	    each alias with a vertical bar and put a colon after the last
 	    alias.</para>
 
 	  <para>In the following example, we start with a skeletal
 	    <filename>/etc/printcap</filename> that defines two printers
 	    (a Diablo 630 line printer and a Panasonic KX-P4455 &postscript;
 	    laser printer):</para>
 
 	  <programlisting>#
 #  /etc/printcap for host rose
 #
 rattan|line|diablo|lp|Diablo 630 Line Printer:
 
 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:</programlisting>
 
 	  <para>In this example, the first printer is named
 	    <literal>rattan</literal> and has as aliases
 	    <literal>line</literal>, <literal>diablo</literal>,
 	    <literal>lp</literal>, and <literal>Diablo 630 Line
 	    Printer</literal>.  Since it has the alias
 	    <literal>lp</literal>, it is also the default printer.  The
 	    second is named <literal>bamboo</literal>, and has as aliases
 	    <literal>ps</literal>, <literal>PS</literal>,
 	    <literal>S</literal>, <literal>panasonic</literal>, and
 	    <literal>Panasonic KX-P4455 PostScript v51.4</literal>.</para>
 	</sect4>
 
 	<sect4 id="printing-no-header-pages">
 	  <title>Suppressing Header Pages</title>
 	  <indexterm>
       <primary>printing</primary>
       <secondary>header pages</secondary>
     </indexterm>
 
 	  <para>The <application>LPD</application> spooling system will
 	    by default print a
 	    <emphasis>header page</emphasis> for each job.  The header
 	    page contains the user name who requested the job, the host
 	    from which the job came, and the name of the job, in nice
 	    large letters.  Unfortunately, all this extra text gets in the
 	    way of debugging the simple printer setup, so we will suppress
 	    header pages.</para>
 
 	  <para>To suppress header pages, add the <literal>sh</literal>
 	    capability to the entry for the printer in
 	    <filename>/etc/printcap</filename>.  Here is an example
 	    <filename>/etc/printcap</filename> with <literal>sh</literal>
 	    added:</para>
 
 	  <programlisting>#
 #  /etc/printcap for host rose - no header pages anywhere
 #
 rattan|line|diablo|lp|Diablo 630 Line Printer:\
         :sh:
 
 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
         :sh:</programlisting>
 
 	  <para>Note how we used the correct format: the first line starts
 	    in the leftmost column, and subsequent lines are indented.
 	    Every line in an entry except the last ends in
 	    a backslash character.</para>
 	</sect4>
 
 	<sect4 id="printing-spooldir">
 	  <title>Making the Spooling Directory</title>
 	  <indexterm><primary>printer spool</primary></indexterm>
 	  <indexterm><primary>print jobs</primary></indexterm>
 
 	  <para>The next step in the simple spooler setup is to make a
 	    <emphasis>spooling directory</emphasis>, a directory where
 	    print jobs reside until they are printed, and where a number
 	    of other spooler support files live.</para>
 
 	  <para>Because of the variable nature of spooling directories, it
 	    is customary to put these directories under
 	    <filename>/var/spool</filename>.  It is not necessary to
 	    backup the contents of spooling directories, either.
 	    Recreating them is as simple as running &man.mkdir.1;.</para>
 
 	  <para>It is also customary to make the directory with a name
 	    that is identical to the name of the printer, as shown
 	    below:</para>
 
 	  <screen>&prompt.root; <userinput>mkdir /var/spool/<replaceable>printer-name</replaceable></userinput></screen>
 
 	  <para>However, if you have a lot of printers on your network,
 	    you might want to put the spooling directories under a single
 	    directory that you reserve just for printing with
 	    <application>LPD</application>.  We
 	    will do this for our two example printers
 	    <literal>rattan</literal> and
 	    <literal>bamboo</literal>:</para>
 
 	  <screen>&prompt.root; <userinput>mkdir /var/spool/lpd</userinput>
 &prompt.root; <userinput>mkdir /var/spool/lpd/rattan</userinput>
 &prompt.root; <userinput>mkdir /var/spool/lpd/bamboo</userinput></screen>
 
 	  <note>
 	    <para>If you are concerned about the privacy of jobs that
 	      users print, you might want to protect the spooling
 	      directory so it is not publicly accessible.  Spooling
 	      directories should be owned and be readable, writable, and
 	      searchable by user daemon and group daemon, and no one else.
 	      We will do this for our example printers:</para>
 
 	    <screen>&prompt.root; <userinput>chown daemon:daemon /var/spool/lpd/rattan</userinput>
 &prompt.root; <userinput>chown daemon:daemon /var/spool/lpd/bamboo</userinput>
 &prompt.root; <userinput>chmod 770 /var/spool/lpd/rattan</userinput>
 &prompt.root; <userinput>chmod 770 /var/spool/lpd/bamboo</userinput></screen>
 	  </note>
 
 	  <para>Finally, you need to tell <application>LPD</application>
 	    about these directories
 	    using the <filename>/etc/printcap</filename> file.  You
 	    specify the pathname of the spooling directory with the
 	    <literal>sd</literal> capability:</para>
 
 	  <programlisting>#
 #  /etc/printcap for host rose - added spooling directories
 #
 rattan|line|diablo|lp|Diablo 630 Line Printer:\
         :sh:sd=/var/spool/lpd/rattan:
 
 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
         :sh:sd=/var/spool/lpd/bamboo:</programlisting>
 
 	  <para>Note that the name of the printer starts in the first
 	    column but all other entries describing the printer should be
 	    indented and each line end escaped with a
 	    backslash.</para>
 
 	  <para>If you do not specify a spooling directory with
 	    <literal>sd</literal>, the spooling system will use
 	    <filename>/var/spool/lpd</filename> as a default.</para>
 	</sect4>
 
 	<sect4 id="printing-device">
 	  <title>Identifying the Printer Device</title>
 
 	  <para>In the
 	     Entries for the Ports
 	    section, we identified which entry in the
 	    <filename>/dev</filename> directory FreeBSD will use to
 	    communicate with the printer.  Now, we tell
 	    <application>LPD</application> that
 	    information.  When the spooling system has a job to print, it
 	    will open the specified device on behalf of the filter program
 	    (which is responsible for passing data to the printer).</para>
 
 	  <para>List the <filename>/dev</filename> entry pathname in the
 	    <filename>/etc/printcap</filename> file using the
 	    <literal>lp</literal> capability.</para>
 
 	  <para>In our running example, let us assume that
 	    <literal>rattan</literal> is on the first parallel port, and
 	    <literal>bamboo</literal> is on a sixth serial port; here are
 	    the additions to <filename>/etc/printcap</filename>:</para>
 
 	  <programlisting>#
 #  /etc/printcap for host rose - identified what devices to use
 #
 rattan|line|diablo|lp|Diablo 630 Line Printer:\
         :sh:sd=/var/spool/lpd/rattan:\
         :lp=/dev/lpt0:
 
 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
         :sh:sd=/var/spool/lpd/bamboo:\
         :lp=/dev/ttyd5:</programlisting>
 
 	  <para>If you do not specify the <literal>lp</literal> capability
 	    for a printer in your <filename>/etc/printcap</filename> file,
 	    <application>LPD</application> uses <filename>/dev/lp</filename>
 	    as a default.
 	    <filename>/dev/lp</filename> currently does not exist in
 	    FreeBSD.</para>
 
 	  <para>If the printer you are installing is connected to a
 	    parallel port, skip to the section entitled, <link
 	    linkend="printing-textfilter">Installing the Text
 	    Filter</link>.  Otherwise, be sure to follow the instructions
 	    in the next section.</para>
 	</sect4>
 
 	<sect4 id="printing-commparam">
 	  <title>Configuring Spooler Communication Parameters</title>
 	  <indexterm>
       <primary>printers</primary>
       <secondary>serial</secondary>
     </indexterm>
 
 	  <para>For printers on serial ports, <application>LPD</application>
 	    can set up the bps rate,
 	    parity, and other serial communication parameters on behalf of
 	    the filter program that sends data to the printer.  This is
 	    advantageous since:</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>It lets you try different communication parameters by
 		simply editing the <filename>/etc/printcap</filename>
 		file; you do not have to recompile the filter
 		program.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>It enables the spooling system to use the same filter
 		program for multiple printers which may have different
 		serial communication settings.</para>
 	    </listitem>
 	  </itemizedlist>
 
 	  <para>The following <filename>/etc/printcap</filename>
 	    capabilities control serial communication parameters of the
 	    device listed in the <literal>lp</literal> capability:</para>
 
 	  <variablelist>
 	    <varlistentry>
 	      <term><literal>br#<replaceable>bps-rate</replaceable></literal></term>
 
 	      <listitem>
 		<para>Sets the communications speed of the device to
 		  <replaceable>bps-rate</replaceable>, where
 		  <replaceable>bps-rate</replaceable> can be 50, 75, 110,
 		  134, 150, 200, 300, 600, 1200, 1800, 2400, 4800, 9600,
 		  19200, 38400, 57600, or 115200 bits-per-second.</para>
 	      </listitem>
 	    </varlistentry>
 
 	    <varlistentry>
 	      <term><literal>ms#<replaceable>stty-mode</replaceable></literal></term>
 
 	      <listitem>
 		<para>Sets the options for the terminal device after
 		  opening the device.  &man.stty.1; explains the
 		  available options.</para>
 	      </listitem>
 	    </varlistentry>
 	  </variablelist>
 
 	  <para>When <application>LPD</application> opens the device
 	    specified by the <literal>lp</literal> capability, it sets
 	    the characteristics of the device to those specified with
 	    the <literal>ms#</literal> capability.  Of particular
 	    interest will be the <literal>parenb</literal>,
 	    <literal>parodd</literal>, <literal>cs5</literal>,
 	    <literal>cs6</literal>, <literal>cs7</literal>,
 	    <literal>cs8</literal>, <literal>cstopb</literal>,
 	    <literal>crtscts</literal>, and <literal>ixon</literal>
 	    modes, which are explained in the &man.stty.1;
 	    manual page.</para>
 
 	  <para>Let us add to our example printer on the sixth serial
 	    port.  We will set the bps rate to 38400.  For the mode,
 	    we will set no parity with <literal>-parenb</literal>,
 	    8-bit characters with <literal>cs8</literal>,
 	    no modem control with <literal>clocal</literal> and
 	    hardware flow control with <literal>crtscts</literal>:</para>
 
 	  <programlisting>bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
         :sh:sd=/var/spool/lpd/bamboo:\
         :lp=/dev/ttyd5:ms#-parenb cs8 clocal crtscts:</programlisting>
 	</sect4>
 
 	<sect4 id="printing-textfilter">
 	  <title>Installing the Text Filter</title>
 	  <indexterm>
 	    <primary>printing</primary>
 	    <secondary>filters</secondary>
 	  </indexterm>
 
 	  <para>We are now ready to tell <application>LPD</application>
 	    what text filter to use to
 	    send jobs to the printer.  A <emphasis>text filter</emphasis>,
 	    also known as an <emphasis>input filter</emphasis>, is a
 	    program that <application>LPD</application> runs when it
 	    has a job to print.  When <application>LPD</application>
 	    runs the text filter for a printer, it sets the filter's
 	    standard input to the job to print, and its standard output to
 	    the printer device specified with the <literal>lp</literal>
 	    capability.  The filter is expected to read the job from
 	    standard input, perform any necessary translation for the
 	    printer, and write the results to standard output, which will
 	    get printed.  For more information on the text filter, see
 	    the <link linkend="printing-advanced-filters">Filters</link>
 	    section.</para>
 
 	  <para>For our simple printer setup, the text filter can be a
 	    small shell script that just executes
 	    <command>/bin/cat</command> to send the job to the printer.
 	    FreeBSD comes with another filter called
 	    <filename>lpf</filename> that handles backspacing and
 	    underlining for printers that might not deal with such
 	    character streams well.  And, of course, you can use any other
 	    filter program you want.  The filter <command>lpf</command> is
 	    described in detail in section entitled <link
 	    linkend="printing-advanced-lpf">lpf: a Text
 	    Filter</link>.</para>
 
 	  <para>First, let us make the shell script
 	    <filename>/usr/local/libexec/if-simple</filename> be a simple
 	    text filter.  Put the following text into that file with your
 	    favorite text editor:</para>
 
 	  <programlisting>#!/bin/sh
 #
 # if-simple - Simple text input filter for lpd
 # Installed in /usr/local/libexec/if-simple
 #
 # Simply copies stdin to stdout.  Ignores all filter arguments.
 
 /bin/cat &amp;&amp; exit 0
 exit 2</programlisting>
 
 	  <para>Make the file executable:</para>
 
 	  <screen>&prompt.root; <userinput>chmod 555 /usr/local/libexec/if-simple</userinput></screen>
 
 	  <para>And then tell LPD to use it by specifying it with the
 	    <literal>if</literal> capability in
 	    <filename>/etc/printcap</filename>.  We will add it to the two
 	    printers we have so far in the example
 	    <filename>/etc/printcap</filename>:</para>
 
 	  <programlisting>#
 #  /etc/printcap for host rose - added text filter
 #
 rattan|line|diablo|lp|Diablo 630 Line Printer:\
         :sh:sd=/var/spool/lpd/rattan:\ :lp=/dev/lpt0:\
         :if=/usr/local/libexec/if-simple:
 
 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
         :sh:sd=/var/spool/lpd/bamboo:\
         :lp=/dev/ttyd5:ms#-parenb cs8 clocal crtscts:\
         :if=/usr/local/libexec/if-simple:</programlisting>
 
 	  <note>
 	    <para>A copy of the <filename>if-simple</filename> script
 	      can be found in the <filename
 	      class="directory">/usr/share/examples/printing</filename>
 	      directory.</para>
 	  </note>
 	</sect4>
 
 	<sect4>
 	  <title>Turn on <application>LPD</application></title>
 
 	  <para>&man.lpd.8; is run from <filename>/etc/rc</filename>,
 	    controlled by the <literal>lpd_enable</literal> variable.  This
 	    variable defaults to <literal>NO</literal>.  If you have not done
 	    so already, add the line:</para>
 
 	  <programlisting>lpd_enable="YES"</programlisting>
 
 	  <para>to <filename>/etc/rc.conf</filename>, and then either restart
 	    your machine, or just run &man.lpd.8;.</para>
 
 	  <screen>&prompt.root; <userinput>lpd</userinput></screen>
 	</sect4>
 
 	<sect4 id="printing-trying">
 	  <title>Trying It Out</title>
 
 	  <para>You have reached the end of the simple
 	    <application>LPD</application> setup.
 	    Unfortunately, congratulations are not quite yet in order,
 	    since we still have to test the setup and correct any
 	    problems.  To test the setup, try printing something.  To
 	    print with the <application>LPD</application> system, you
 	    use the command &man.lpr.1;,
 	    which submits a job for printing.</para>
 
 	  <para>You can combine &man.lpr.1; with the &man.lptest.1;
 	    program, introduced in section <link
 	    linkend="printing-testing">Checking Printer
 	    Communications</link> to generate some test text.</para>
 
 	  <para><emphasis>To test the simple <application>LPD</application>
 	      setup:</emphasis></para>
 
 	  <para>Type:</para>
 
 	  <screen>&prompt.root; <userinput>lptest 20 5 | lpr -P<replaceable>printer-name</replaceable></userinput></screen>
 
 	  <para>Where <replaceable>printer-name</replaceable> is a the
 	    name of a printer (or an alias) specified in
 	    <filename>/etc/printcap</filename>.  To test the default
 	    printer, type &man.lpr.1; without any <option>-P</option>
 	    argument.  Again, if you are testing a printer that expects
 	    &postscript;, send a &postscript; program in that language instead
 	    of using &man.lptest.1;.  You can do so by putting the program
 	    in a file and typing <command>lpr
 	    <replaceable>file</replaceable></command>.</para>
 
 	  <para>For a &postscript; printer, you should get the results of
 	    the program.  If you are using &man.lptest.1;, then your
 	    results should look like the following:</para>
 
 	  <programlisting>!"#$%&amp;'()*+,-./01234
 "#$%&amp;'()*+,-./012345
 #$%&amp;'()*+,-./0123456
 $%&amp;'()*+,-./01234567
 %&amp;'()*+,-./012345678</programlisting>
 
 	  <para>To further test the printer, try downloading larger
 	    programs (for language-based printers) or running
 	    &man.lptest.1; with different arguments.  For example,
 	    <command>lptest 80 60</command> will produce 60 lines of 80
 	    characters each.</para>
 
 	  <para>If the printer did not work, see the <link
 	    linkend="printing-troubleshooting">Troubleshooting</link>
 	    section.</para>
 	</sect4>
       </sect3>
     </sect2>
   </sect1>
 
   <sect1 id="printing-advanced">
     <title>Advanced Printer Setup</title>
 
     <para>This section describes filters for printing specially formatted
       files, header pages, printing across networks, and restricting and
       accounting for printer usage.</para>
 
     <sect2 id="printing-advanced-filter-intro">
       <title>Filters</title>
       <indexterm>
 	<primary>printing</primary>
 	<secondary>filters</secondary>
       </indexterm>
 
       <para>Although <application>LPD</application> handles network protocols,
 	queuing, access control,
         and other aspects of printing, most of the <emphasis>real</emphasis>
         work happens in the <emphasis>filters</emphasis>.  Filters are
         programs that communicate with the printer and handle its device
         dependencies and special requirements.  In the simple printer setup,
         we installed a plain text filter&mdash;an extremely simple one that
         should work with most printers (section <link
           linkend="printing-textfilter">Installing the Text
           Filter</link>).</para>
 
       <para>However, in order to take advantage of format conversion, printer
         accounting, specific printer quirks, and so on, you should understand
         how filters work.  It will ultimately be the filter's responsibility
         to handle these aspects.  And the bad news is that most of the time
         <emphasis>you</emphasis> have to provide filters yourself.  The good
         news is that many are generally available; when they are not, they are
         usually easy to write.</para>
 
       <para>Also, FreeBSD comes with one,
         <filename>/usr/libexec/lpr/lpf</filename>, that works with many
         printers that can print plain text.  (It handles backspacing and tabs
         in the file, and does accounting, but that is about all it does.)
         There are also several filters and filter components in the FreeBSD
         Ports Collection.</para>
 
       <para>Here is what you will find in this section:</para>
 
       <itemizedlist>
         <listitem>
           <para>Section <link linkend="printing-advanced-filters">How Filters
               Work</link>, tries to give an overview of a filter's role in the
             printing process.  You should read this section to get an
             understanding of what is happening <quote>under the hood</quote>
             when <application>LPD</application> uses filters.  This knowledge
 	    could help you anticipate
             and debug problems you might encounter as you install more and
             more filters on each of your printers.</para>
         </listitem>
 
         <listitem>
           <para><application>LPD</application> expects every printer to be
 	    able to print plain text by
             default.  This presents a problem for &postscript; (or other
             language-based printers) which cannot directly print plain text.
             Section <link
               linkend="printing-advanced-if-conversion">Accommodating
               Plain Text Jobs on &postscript; Printers</link> tells you what you
             should do to overcome this problem.  You should read this
             section if you have a &postscript; printer.</para>
         </listitem>
 
         <listitem>
           <para>&postscript; is a popular output format for many programs.
             Some people even write &postscript; code directly.  Unfortunately,
             &postscript; printers are expensive.  Section <link
               linkend="printing-advanced-ps">Simulating &postscript; on
               Non &postscript; Printers</link> tells how you can further modify
             a printer's text filter to accept and print &postscript; data on a
             <emphasis>non &postscript;</emphasis> printer.  You should read
             this section if you do not have a &postscript; printer.</para>
         </listitem>
 
         <listitem>
           <para>Section <link
               linkend="printing-advanced-convfilters">Conversion
               Filters</link> tells about a way you can automate the conversion
             of specific file formats, such as graphic or typesetting data,
             into formats your printer can understand.  After reading this
             section, you should be able to set up your printers such that
             users can type <command>lpr -t</command> to print troff data, or
             <command>lpr -d</command> to print &tex; DVI data, or <command>lpr
               -v</command> to print raster image data, and so forth.  I
             recommend reading this section.</para>
         </listitem>
 
         <listitem>
           <para>Section <link linkend="printing-advanced-of">Output
               Filters</link> tells all about a not often used feature of
 	    <application>LPD</application>:
             output filters.  Unless you are printing header pages (see <link
               linkend="printing-advanced-header-pages">Header Pages</link>),
             you can probably skip that section altogether.</para>
         </listitem>
 
         <listitem>
           <para>Section <link linkend="printing-advanced-lpf">lpf: a Text
               Filter</link> describes <command>lpf</command>, a fairly
             complete if simple text filter for line printers (and laser
             printers that act like line printers) that comes with FreeBSD.  If
             you need a quick way to get printer accounting working for plain
             text, or if you have a printer which emits smoke when it sees
             backspace characters, you should definitely consider
             <command>lpf</command>.</para>
         </listitem>
       </itemizedlist>
 
       <note>
 	<para>A copy of the various scripts described below can be
 	  found in the <filename
 	  class="directory">/usr/share/examples/printing</filename>
 	  directory.</para>
       </note>
 
       <sect3 id="printing-advanced-filters">
         <title>How Filters Work</title>
 
         <para>As mentioned before, a filter is an executable program started
           by <application>LPD</application> to handle the device-dependent part of
 	  communicating with the printer.</para>
 
         <para>When <application>LPD</application> wants to print a file in a
 	  job, it starts a filter
           program.  It sets the filter's standard input to the file to print,
           its standard output to the printer, and its standard error to the
           error logging file (specified in the <literal>lf</literal>
           capability in <filename>/etc/printcap</filename>, or
           <filename>/dev/console</filename> by default).</para>
 
         <indexterm>
           <primary><command>troff</command></primary>
         </indexterm>
         <para>Which filter <application>LPD</application> starts and the
 	  filter's arguments depend on
           what is listed in the <filename>/etc/printcap</filename> file and
           what arguments the user specified for the job on the
             &man.lpr.1; command line.  For example, if the user typed
           <command>lpr -t</command>, <application>LPD</application> would
 	  start the troff filter, listed
           in the <literal>tf</literal> capability for the destination printer.
           If the user wanted to print plain text, it would start the
           <literal>if</literal> filter (this is mostly true: see <link
             linkend="printing-advanced-of">Output Filters</link> for
           details).</para>
 
         <para>There are three kinds of filters you can specify in
           <filename>/etc/printcap</filename>:</para>
 
         <itemizedlist>
           <listitem>
             <para>The <emphasis>text filter</emphasis>, confusingly called the
               <emphasis>input filter</emphasis> in
 	      <application>LPD</application> documentation, handles
               regular text printing.  Think of it as the default filter.
 	      <application>LPD</application>
               expects every printer to be able to print plain text by default,
               and it is the text filter's job to make sure backspaces, tabs,
               or other special characters do not confuse the printer.  If you
               are in an environment where you have to account for printer
               usage, the text filter must also account for pages printed,
               usually by counting the number of lines printed and comparing
               that to the number of lines per page the printer supports.  The
               text filter is started with the following argument list:
 
               <cmdsynopsis>
                 <command>filter-name</command>
                 <arg>-c</arg>
                 <arg choice="plain">-w<replaceable>width</replaceable></arg>
                 <arg choice="plain">-l<replaceable>length</replaceable></arg>
                 <arg choice="plain">-i<replaceable>indent</replaceable></arg>
                 <arg choice="plain">-n <replaceable>login</replaceable></arg>
                 <arg choice="plain">-h <replaceable>host</replaceable></arg>
                 <arg choice="plain"><replaceable>acct-file</replaceable></arg>
               </cmdsynopsis>
 
               where
 
               <variablelist>
                 <varlistentry>
                   <term><option>-c</option></term>
 
                   <listitem>
                     <para>appears if the job is submitted with <command>lpr
                         -l</command></para>
                   </listitem>
                 </varlistentry>
 
                 <varlistentry>
                   <term><replaceable>width</replaceable></term>
 
                   <listitem>
                     <para>is the value from the <literal>pw</literal> (page
                       width) capability specified in
                       <filename>/etc/printcap</filename>, default 132</para>
                   </listitem>
                 </varlistentry>
 
                 <varlistentry>
                   <term><replaceable>length</replaceable></term>
 
                   <listitem>
                     <para>is the value from the <literal>pl</literal> (page
                       length) capability, default 66</para>
                   </listitem>
                 </varlistentry>
 
                 <varlistentry>
                   <term><replaceable>indent</replaceable></term>
 
                   <listitem>
                     <para>is the amount of the indentation from <command>lpr
                         -i</command>, default 0</para>
                   </listitem>
                 </varlistentry>
 
                 <varlistentry>
                   <term><replaceable>login</replaceable></term>
 
                   <listitem>
                     <para>is the account name of the user printing the
                       file</para>
                   </listitem>
                 </varlistentry>
 
                 <varlistentry>
                   <term><replaceable>host</replaceable></term>
 
                   <listitem>
                     <para>is the host name from which the job was
                       submitted</para>
                   </listitem>
                 </varlistentry>
 
                 <varlistentry>
                   <term><replaceable>acct-file</replaceable></term>
 
                   <listitem>
                     <para>is the name of the accounting file from the
                       <literal>af</literal> capability.</para>
                   </listitem>
                 </varlistentry>
               </variablelist>
             </para>
           </listitem>
 
           <listitem>
-	    <indexterm>
-	      <primary>printing</primary>
-	      <secondary>filters</secondary>
-	    </indexterm>
-
-            <para>A <emphasis>conversion filter</emphasis> converts a specific
+            <para>A <emphasis>conversion filter</emphasis><indexterm><primary>printing</primary><secondary>filters</secondary></indexterm> converts a specific
               file format into one the printer can render onto paper.  For
               example, ditroff typesetting data cannot be directly printed,
               but you can install a conversion filter for ditroff files to
               convert the ditroff data into a form the printer can digest and
               print.  Section <link
                 linkend="printing-advanced-convfilters">Conversion
                 Filters</link> tells all about them. Conversion filters also
               need to do accounting, if you need printer accounting.
               Conversion filters are started with the following arguments:
 
               <cmdsynopsis>
                 <command>filter-name</command>
                 <arg
                   choice="plain">-x<replaceable>pixel-width</replaceable></arg>
                 <arg choice="plain">-y<replaceable>pixel-height</replaceable></arg>
                 <arg choice="plain">-n <replaceable>login</replaceable></arg>
                 <arg choice="plain">-h <replaceable>host</replaceable></arg>
                 <arg choice="plain"><replaceable>acct-file</replaceable></arg>
               </cmdsynopsis>
 
               where <replaceable>pixel-width</replaceable> is the value
               from the <literal>px</literal> capability (default 0) and
               <replaceable>pixel-height</replaceable> is the value from the
               <literal>py</literal> capability (default 0).</para>
           </listitem>
 
           <listitem>
             <para>The <emphasis>output filter</emphasis> is used only if there
               is no text filter, or if header pages are enabled. In my
               experience, output filters are rarely used.  Section <link
                 linkend="printing-advanced-of">Output Filters</link> describe
               them.  There are only two arguments to an output filter:
 
               <cmdsynopsis>
                 <command>filter-name</command>
                 <arg choice="plain">-w<replaceable>width</replaceable></arg>
                 <arg choice="plain">-l<replaceable>length</replaceable></arg>
               </cmdsynopsis>
 
               which are identical to the text filters <option>-w</option> and
               <option>-l</option> arguments.</para>
           </listitem>
         </itemizedlist>
 
         <para>Filters should also <emphasis>exit</emphasis> with the
           following exit status:</para>
 
         <variablelist>
           <varlistentry>
             <term>exit 0</term>
 
             <listitem>
               <para>If the filter printed the file successfully.</para>
             </listitem>
           </varlistentry>
 
           <varlistentry>
             <term>exit 1</term>
 
             <listitem>
               <para>If the filter failed to print the file but wants
 		<application>LPD</application> to
                 try to print the file again.  <application>LPD</application>
 		will restart a filter if it exits with this status.</para>
             </listitem>
           </varlistentry>
 
           <varlistentry>
             <term>exit 2</term>
 
             <listitem>
               <para>If the filter failed to print the file and does not want
                 <application>LPD</application> to try again.
 		<application>LPD</application> will throw out the file.</para>
             </listitem>
           </varlistentry>
         </variablelist>
 
         <para>The text filter that comes with the FreeBSD release,
           <filename>/usr/libexec/lpr/lpf</filename>, takes advantage of the
           page width and length arguments to determine when to send a form
           feed and how to account for printer usage.  It uses the login, host,
           and accounting file arguments to make the accounting entries.</para>
 
         <para>If you are shopping for filters, see if they are LPD-compatible.
           If they are, they must support the argument lists described above.
           If you plan on writing filters for general use, then have them
           support the same argument lists and exit codes.</para>
       </sect3>
 
       <sect3 id="printing-advanced-if-conversion">
         <title>Accommodating Plain Text Jobs on &postscript; Printers</title>
         <indexterm><primary>print jobs</primary></indexterm>
 
         <para>If you are the only user of your computer and &postscript; (or
           other language-based) printer, and you promise to never send plain
           text to your printer and to never use features of various programs
           that will want to send plain text to your printer, then you do not
           need to worry about this section at all.</para>
 
         <para>But, if you would like to send both &postscript; and plain text
           jobs to the printer, then you are urged to augment your printer
           setup.  To do so, we have the text filter detect if the arriving job
           is plain text or &postscript;.  All &postscript; jobs must start with
           <literal>%!</literal> (for other printer languages, see your printer
           documentation).  If those are the first two characters in the job,
           we have &postscript;, and can pass the rest of the job directly.  If
           those are not the first two characters in the file, then the filter
           will convert the text into &postscript; and print the result.</para>
 
         <para>How do we do this?</para>
 
         <indexterm>
           <primary>printers</primary>
           <secondary>serial</secondary>
         </indexterm>
         <para>If you have got a serial printer, a great way to do it is to
           install <command>lprps</command>.  <command>lprps</command> is a
           &postscript; printer filter which performs two-way communication with
           the printer.  It updates the printer's status file with verbose
           information from the printer, so users and administrators can see
           exactly what the state of the printer is (such as <errorname>toner
             low</errorname> or <errorname>paper jam</errorname>).  But more
           importantly, it includes a program called <command>psif</command>
           which detects whether the incoming job is plain text and calls
           <command>textps</command> (another program that comes with
           <command>lprps</command>) to convert it to &postscript;.  It then uses
           <command>lprps</command> to send the job to the printer.</para>
 
         <para><command>lprps</command> is part of the FreeBSD Ports Collection
           (see <link linkend="ports">The Ports Collection</link>).  You can
           fetch, build and install it yourself, of course.  After installing
           <command>lprps</command>, just specify the pathname to the
           <command>psif</command> program that is part of
           <command>lprps</command>.  If you installed <command>lprps</command>
           from the Ports Collection, use the following in the serial
           &postscript; printer's entry in
           <filename>/etc/printcap</filename>:</para>
 
         <programlisting>:if=/usr/local/libexec/psif:</programlisting>
 
         <para>You should also specify the <literal>rw</literal> capability;
           that tells <application>LPD</application> to open the printer in
 	  read-write mode.</para>
 
         <para>If you have a parallel &postscript; printer (and therefore cannot
           use two-way communication with the printer, which
           <command>lprps</command> needs), you can use the following shell
           script as the text filter:</para>
 
         <programlisting>#!/bin/sh
 #
 #  psif - Print PostScript or plain text on a PostScript printer
 #  Script version; NOT the version that comes with lprps
 #  Installed in /usr/local/libexec/psif
 #
 
 IFS="" read -r first_line
 first_two_chars=`expr "$first_line" : '\(..\)'`
 
 if [ "$first_two_chars" = "%!" ]; then
     #
     #  PostScript job, print it.
     #
     echo "$first_line" &amp;&amp; cat &amp;&amp; printf "\004" &amp;&amp; exit 0
     exit 2
 else
     #
     #  Plain text, convert it, then print it.
     #
     ( echo "$first_line"; cat ) | /usr/local/bin/textps &amp;&amp; printf "\004" &amp;&amp; exit 0
     exit 2
 fi</programlisting>
 
         <para>In the above script, <command>textps</command> is a program we
           installed separately to convert plain text to &postscript;.  You can
           use any text-to-&postscript; program you wish.  The FreeBSD Ports
           Collection (see <link linkend="ports">The Ports Collection</link>)
           includes a full featured text-to-&postscript; program called
           <literal>a2ps</literal> that you might want to investigate.</para>
       </sect3>
 
       <sect3 id="printing-advanced-ps">
         <title>Simulating &postscript; on Non &postscript; Printers</title>
         <indexterm>
           <primary>PostScript</primary>
           <secondary>emulating</secondary>
         </indexterm>
         <indexterm>
           <primary>Ghostscript</primary></indexterm>
         <para>&postscript; is the <emphasis>de facto</emphasis> standard for
           high quality typesetting and printing.  &postscript; is, however, an
           <emphasis>expensive</emphasis> standard. Thankfully, Aladdin
           Enterprises has a free &postscript; work-alike called
           <application>Ghostscript</application> that runs with FreeBSD.
           Ghostscript can read most &postscript; files and can render their
           pages onto a variety of devices, including many brands of
           non-PostScript printers.  By installing Ghostscript and using a
           special text filter for your printer, you can make your
           non &postscript; printer act like a real &postscript; printer.</para>
 
         <para>Ghostscript is in the FreeBSD Ports Collection, if you
           would like to install it from there.  You can fetch, build, and
           install it quite easily yourself, as well.</para>
 
         <para>To simulate &postscript;, we have the text filter detect if it is
           printing a &postscript; file.  If it is not, then the filter will pass
           the file directly to the printer; otherwise, it will use Ghostscript
           to first convert the file into a format the printer will
           understand.</para>
 
         <para>Here is an example: the following script is a text filter
           for Hewlett Packard DeskJet 500 printers.  For other printers,
           substitute the <option>-sDEVICE</option> argument to the
           <command>gs</command> (Ghostscript) command.  (Type <command>gs
             -h</command> to get a list of devices the current installation of
           Ghostscript supports.)</para>
 
         <programlisting>#!/bin/sh
 #
 #  ifhp - Print Ghostscript-simulated PostScript on a DeskJet 500
 #  Installed in /usr/local/libexec/ifhp
 
 #
 #  Treat LF as CR+LF (to avoid the "staircase effect" on HP/PCL
 #  printers):
 #
 printf "\033&amp;k2G" || exit 2
 
 #
 #  Read first two characters of the file
 #
 IFS="" read -r first_line
 first_two_chars=`expr "$first_line" : '\(..\)'`
 
 if [ "$first_two_chars" = "%!" ]; then
     #
     #  It is PostScript; use Ghostscript to scan-convert and print it.
     #
     /usr/local/bin/gs -dSAFER -dNOPAUSE -q -sDEVICE=djet500 \
       -sOutputFile=- - &amp;&amp; exit 0
 else
     #
     #  Plain text or HP/PCL, so just print it directly; print a form feed
     #  at the end to eject the last page.
     #
     echo "$first_line" &amp;&amp; cat &amp;&amp; printf "\033&amp;l0H" &amp;&amp;
 exit 0
 fi
 
 exit 2</programlisting>
 
         <para>Finally, you need to notify <application>LPD</application> of
 	  the filter via the <literal>if</literal> capability:</para>
 
         <programlisting>:if=/usr/local/libexec/ifhp:</programlisting>
 
         <para>That is it.  You can type <command>lpr plain.text</command> and
           <filename>lpr whatever.ps</filename> and both should print
           successfully.</para>
       </sect3>
 
       <sect3 id="printing-advanced-convfilters">
         <title>Conversion Filters</title>
 
         <para>After completing the simple setup described in <link
             linkend="printing-simple">Simple Printer Setup</link>, the first
           thing you will probably want to do is install conversion filters for
           your favorite file formats (besides plain ASCII text).</para>
 
         <sect4>
           <title>Why Install Conversion Filters?</title>
           <indexterm>
             <primary>&tex;</primary>
             <secondary>printing DVI files</secondary>
           </indexterm>
 
           <para>Conversion filters make printing various kinds of files easy.
             As an example, suppose we do a lot of work with the &tex;
             typesetting system, and we have a &postscript; printer.  Every time
             we generate a DVI file from &tex;, we cannot print it directly until
             we convert the DVI file into &postscript;.  The command sequence
             goes like this:</para>
 
           <screen>&prompt.user; <userinput>dvips seaweed-analysis.dvi</userinput>
 &prompt.user; <userinput>lpr seaweed-analysis.ps</userinput></screen>
 
           <para>By installing a conversion filter for DVI files, we can skip
             the hand conversion step each time by having
 	    <application>LPD</application> do it for us.
             Now, each time we get a DVI file, we are just one step away from
             printing it:</para>
 
           <screen>&prompt.user; <userinput>lpr -d seaweed-analysis.dvi</userinput></screen>
 
           <para>We got <application>LPD</application> to do the DVI file
 	    conversion for us by specifying
             the <option>-d</option> option.  Section <link
               linkend="printing-lpr-options-format">Formatting and Conversion
               Options</link> lists the conversion options.</para>
 
           <para>For each of the conversion options you want a printer to
             support, install a <emphasis>conversion filter</emphasis> and
             specify its pathname in <filename>/etc/printcap</filename>.  A
             conversion filter is like the text filter for the simple printer
             setup (see section <link linkend="printing-textfilter">Installing
               the Text Filter</link>) except that instead of printing plain
             text, the filter converts the file into a format the printer can
             understand.</para>
         </sect4>
 
         <sect4>
           <title>Which Conversion Filters Should I Install?</title>
 
           <para>You should install the conversion filters you expect to use.
             If you print a lot of DVI data, then a DVI conversion filter is in
             order.  If you have got plenty of troff to print out, then you
             probably want a troff filter.</para>
 
           <para>The following table summarizes the filters that
 	    <application>LPD</application> works
             with, their capability entries for the
             <filename>/etc/printcap</filename> file, and how to invoke them
             with the <command>lpr</command> command:</para>
 
           <informaltable frame="none" pgwide="1">
             <tgroup cols="3">
               <thead>
                 <row>
                   <entry>File type</entry>
                   <entry><filename>/etc/printcap</filename> capability</entry>
                   <entry><command>lpr</command> option</entry>
                 </row>
               </thead>
 
               <tbody>
                 <row>
                   <entry>cifplot</entry>
                   <entry><literal>cf</literal></entry>
                   <entry><option>-c</option></entry>
                 </row>
 
                 <row>
                   <entry>DVI</entry>
                   <entry><literal>df</literal></entry>
                   <entry><option>-d</option></entry>
                 </row>
 
                 <row>
                   <entry>plot</entry>
                   <entry><literal>gf</literal></entry>
                   <entry><option>-g</option></entry>
                 </row>
 
                 <row>
                   <entry>ditroff</entry>
                   <entry><literal>nf</literal></entry>
                   <entry><option>-n</option></entry>
                 </row>
 
                 <row>
                   <entry>FORTRAN text</entry>
                   <entry><literal>rf</literal></entry>
                   <entry><option>-f</option></entry>
                 </row>
 
                 <row>
                   <entry>troff</entry>
                   <entry><literal>tf</literal></entry>
                   <entry><option>-f</option></entry>
                 </row>
 
                 <row>
                   <entry>raster</entry>
                   <entry><literal>vf</literal></entry>
                   <entry><option>-v</option></entry>
                 </row>
 
                 <row>
                   <entry>plain text</entry>
                   <entry><literal>if</literal></entry>
                   <entry>none, <option>-p</option>, or
                     <option>-l</option></entry>
                 </row>
               </tbody>
             </tgroup>
           </informaltable>
 
           <para>In our example, using <command>lpr -d</command> means the
             printer needs a <literal>df</literal> capability in its entry in
             <filename>/etc/printcap</filename>.</para>
 
           <indexterm><primary>FORTRAN</primary></indexterm>
           <para>Despite what others might contend, formats like FORTRAN text
             and plot are probably obsolete.  At your site, you can give new
             meanings to these or any of the formatting options just by
             installing custom filters.  For example, suppose you would like to
             directly print Printerleaf files (files from the Interleaf desktop
             publishing program), but will never print plot files.  You could
             install a Printerleaf conversion filter under the
             <literal>gf</literal> capability and then educate your users that
             <command>lpr -g</command> mean <quote>print Printerleaf
             files.</quote></para>
         </sect4>
 
         <sect4>
           <title>Installing Conversion Filters</title>
 
           <para>Since conversion filters are programs you install outside of
             the base FreeBSD installation, they should probably go under
             <filename>/usr/local</filename>.  The directory
             <filename>/usr/local/libexec</filename> is a popular location,
             since they are specialized programs that only
 	    <application>LPD</application> will run;
             regular users should not ever need to run them.</para>
 
           <para>To enable a conversion filter, specify its pathname under the
             appropriate capability for the destination printer in
             <filename>/etc/printcap</filename>.</para>
 
           <para>In our example, we will add the DVI conversion filter to the
             entry for the printer named <literal>bamboo</literal>.  Here is
             the example <filename>/etc/printcap</filename> file again, with
             the new <literal>df</literal> capability for the printer
             <literal>bamboo</literal>.</para>
 
           <programlisting>#
 #  /etc/printcap for host rose - added df filter for bamboo
 #
 rattan|line|diablo|lp|Diablo 630 Line Printer:\
         :sh:sd=/var/spool/lpd/rattan:\
         :lp=/dev/lpt0:\
         :if=/usr/local/libexec/if-simple:
 
 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
         :sh:sd=/var/spool/lpd/bamboo:\
         :lp=/dev/ttyd5:ms#-parenb cs8 clocal crtscts:rw:\
         :if=/usr/local/libexec/psif:\
         :df=/usr/local/libexec/psdf:</programlisting>
 
           <para>The DVI filter is a shell script named
             <filename>/usr/local/libexec/psdf</filename>.  Here is that
             script:</para>
 
           <programlisting>#!/bin/sh
 #
 #  psdf - DVI to PostScript printer filter
 #  Installed in /usr/local/libexec/psdf
 #
 # Invoked by lpd when user runs lpr -d
 #
 exec /usr/local/bin/dvips -f | /usr/local/libexec/lprps "$@"</programlisting>
 
           <para>This script runs <command>dvips</command> in filter mode (the
             <option>-f</option> argument) on standard input, which is the job
             to print.  It then starts the &postscript; printer filter
             <command>lprps</command> (see section <link
               linkend="printing-advanced-if-conversion">Accommodating Plain
               Text Jobs on &postscript; Printers</link>) with the arguments
 	    <application>LPD</application>
             passed to this script. <command>lprps</command> will use those
             arguments to account for the pages printed.</para>
         </sect4>
 
         <sect4>
           <title>More Conversion Filter Examples</title>
 
           <para>Since there is no fixed set of steps to install conversion
             filters, let me instead provide more examples.  Use these as
             guidance to making your own filters.  Use them directly, if
             appropriate.</para>
 
           <para>This example script is a raster (well, GIF file, actually)
             conversion filter for a Hewlett Packard LaserJet III-Si
             printer:</para>
 
           <programlisting>#!/bin/sh
 #
 #  hpvf - Convert GIF files into HP/PCL, then print
 #  Installed in /usr/local/libexec/hpvf
 
 PATH=/usr/X11R6/bin:$PATH; export PATH
 giftopnm | ppmtopgm | pgmtopbm | pbmtolj -resolution 300 \
     &amp;&amp; exit 0 \
     || exit 2</programlisting>
 
           <para>It works by converting the GIF file into a portable anymap,
             converting that into a portable graymap, converting that into a
             portable bitmap, and converting that into LaserJet/PCL-compatible
             data.</para>
 
           <para>Here is the <filename>/etc/printcap</filename> file with an
             entry for a printer using the above filter:</para>
 
           <programlisting>#
 #  /etc/printcap for host orchid
 #
 teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\
         :lp=/dev/lpt0:sh:sd=/var/spool/lpd/teak:mx#0:\
         :if=/usr/local/libexec/hpif:\
         :vf=/usr/local/libexec/hpvf:</programlisting>
 
           <para>The following script is a conversion filter for troff data
             from the groff typesetting system for the &postscript; printer named
             <literal>bamboo</literal>:</para>
 
           <programlisting>#!/bin/sh
 #
 #  pstf - Convert groff's troff data into PS, then print.
 #  Installed in /usr/local/libexec/pstf
 #
 exec grops | /usr/local/libexec/lprps "$@"</programlisting>
 
           <para>The above script makes use of <command>lprps</command> again
             to handle the communication with the printer.  If the printer were
             on a parallel port, we would use this script instead:</para>
 
           <programlisting>#!/bin/sh
 #
 #  pstf - Convert groff's troff data into PS, then print.
 #  Installed in /usr/local/libexec/pstf
 #
 exec grops</programlisting>
 
           <para>That is it.  Here is the entry we need to add to
             <filename>/etc/printcap</filename> to enable the filter:</para>
 
           <programlisting>:tf=/usr/local/libexec/pstf:</programlisting>
 
           <para>Here is an example that might make old hands at FORTRAN blush.
             It is a FORTRAN-text filter for any printer that can directly
             print plain text.  We will install it for the printer
             <literal>teak</literal>:</para>
 
           <programlisting>#!/bin/sh
 #
 # hprf - FORTRAN text filter for LaserJet 3si:
 # Installed in /usr/local/libexec/hprf
 #
 
 printf "\033&amp;k2G" &amp;&amp; fpr &amp;&amp; printf "\033&amp;l0H" &amp;&amp;
  exit 0
 exit 2</programlisting>
 
           <para>And we will add this line to the
             <filename>/etc/printcap</filename> for the printer
             <literal>teak</literal> to enable this filter:</para>
 
           <programlisting>:rf=/usr/local/libexec/hprf:</programlisting>
 
           <para>Here is one final, somewhat complex example.  We will add a
             DVI filter to the LaserJet printer <literal>teak</literal>
             introduced earlier.  First, the easy part: updating
             <filename>/etc/printcap</filename> with the location of the DVI
             filter:</para>
 
           <programlisting>:df=/usr/local/libexec/hpdf:</programlisting>
 
           <para>Now, for the hard part: making the filter.  For that, we need
             a DVI-to-LaserJet/PCL conversion program.  The FreeBSD Ports
             Collection (see <link linkend="ports">The Ports Collection</link>)
             has one: <command>dvi2xx</command> is the name of the package.
             Installing this package gives us the program we need,
             <command>dvilj2p</command>, which converts DVI into LaserJet IIp,
             LaserJet III, and LaserJet 2000 compatible codes.</para>
 
           <para><command>dvilj2p</command> makes the filter
             <command>hpdf</command> quite complex since
             <command>dvilj2p</command> cannot read from standard input.  It
             wants to work with a filename. What is worse, the filename has to
             end in <filename>.dvi</filename> so using
             <filename>/dev/fd/0</filename> for standard input is problematic.
             We can get around that problem by linking (symbolically) a
             temporary file name (one that ends in <filename>.dvi</filename>)
             to <filename>/dev/fd/0</filename>, thereby forcing
             <command>dvilj2p</command> to read from standard input.</para>
 
           <para>The only other fly in the ointment is the fact that we cannot
             use <filename>/tmp</filename> for the temporary link. Symbolic
             links are owned by user and group <username>bin</username>.  The
             filter runs as user <username>daemon</username>.  And the
             <filename>/tmp</filename> directory has the sticky bit set. The
             filter can create the link, but it will not be able clean up when
             done and remove it since the link will belong to a different
             user.</para>
 
           <para>Instead, the filter will make the symbolic link in the current
             working directory, which is the spooling directory (specified by
             the <literal>sd</literal> capability in
             <filename>/etc/printcap</filename>).  This is a perfect place for
             filters to do their work, especially since there is (sometimes)
             more free disk space in the spooling directory than under
             <filename>/tmp</filename>.</para>
 
           <para>Here, finally, is the filter:</para>
 
           <programlisting>#!/bin/sh
 #
 #  hpdf - Print DVI data on HP/PCL printer
 #  Installed in /usr/local/libexec/hpdf
 
 PATH=/usr/local/bin:$PATH; export PATH
 
 #
 #  Define a function to clean up our temporary files.  These exist
 #  in the current directory, which will be the spooling directory
 #  for the printer.
 #
 cleanup() {
    rm -f hpdf$$.dvi
 }
 
 #
 #  Define a function to handle fatal errors: print the given message
 #  and exit 2.  Exiting with 2 tells LPD to do not try to reprint the
 #  job.
 #
 fatal() {
     echo "$@" 1&gt;&amp;2
     cleanup
     exit 2
 }
 
 #
 #  If user removes the job, LPD will send SIGINT, so trap SIGINT
 #  (and a few other signals) to clean up after ourselves.
 #
 trap cleanup 1 2 15
 
 #
 #  Make sure we are not colliding with any existing files.
 #
 cleanup
 
 #
 #  Link the DVI input file to standard input (the file to print).
 #
 ln -s /dev/fd/0 hpdf$$.dvi || fatal "Cannot symlink /dev/fd/0"
 
 #
 #  Make LF = CR+LF
 #
 printf "\033&amp;k2G" || fatal "Cannot initialize printer"
 
 #
 #  Convert and print.  Return value from dvilj2p does not seem to be
 #  reliable, so we ignore it.
 #
 dvilj2p -M1 -q -e- dfhp$$.dvi
 
 #
 #  Clean up and exit
 #
 cleanup
 exit 0</programlisting>
         </sect4>
 
         <sect4 id="printing-advanced-autoconv">
           <title>Automated Conversion: an Alternative to Conversion
             Filters</title>
 
           <para>All these conversion filters accomplish a lot for your
             printing environment, but at the cost forcing the user to specify
             (on the &man.lpr.1; command line) which one to use.
             If your users are not particularly computer literate, having to
             specify a filter option will become annoying.  What is worse,
             though, is that an incorrectly specified filter option may run a
             filter on the wrong type of file and cause your printer to spew
             out hundreds of sheets of paper.</para>
 
           <para>Rather than install conversion filters at all, you might want
             to try having the text filter (since it is the default filter)
             detect the type of file it has been asked to print and then
             automatically run the right conversion filter.  Tools such as
             <command>file</command> can be of help here.  Of course, it will
             be hard to determine the differences between
             <emphasis>some</emphasis> file types&mdash;and, of course, you can
             still provide conversion filters just for them.</para>
 
           <indexterm><primary>apsfilter</primary></indexterm>
           <indexterm>
             <primary>printing</primary>
             <secondary>filters</secondary>
             <tertiary>apsfilter</tertiary>
           </indexterm>
           <para>The FreeBSD Ports Collection has a text filter that performs
             automatic conversion called <command>apsfilter</command>.  It can
             detect plain text, &postscript;, and DVI files, run the proper
             conversions, and print.</para>
         </sect4>
       </sect3>
 
       <sect3 id="printing-advanced-of">
         <title>Output Filters</title>
 
         <para>The <application>LPD</application> spooling system supports one
 	  other type of filter that
           we have not yet explored: an output filter.  An output filter is
           intended for printing plain text only, like the text filter, but
           with many simplifications.  If you are using an output filter but no
           text filter, then:</para>
 
         <itemizedlist>
           <listitem>
             <para><application>LPD</application> starts an output filter once
 	      for the entire job instead
               of once for each file in the job.</para>
           </listitem>
 
           <listitem>
             <para><application>LPD</application> does not make any provision
 	      to identify the start or the
               end of files within the job for the output filter.</para>
           </listitem>
 
           <listitem>
             <para><application>LPD</application> does not pass the user's
 	      login or host to the filter, so
               it is not intended to do accounting.  In fact, it gets only two
               arguments:</para>
 
             <cmdsynopsis>
               <command>filter-name</command>
               <arg choice="plain">-w<replaceable>width</replaceable></arg>
               <arg choice="plain">-l<replaceable>length</replaceable></arg>
             </cmdsynopsis>
 
             <para>Where <replaceable>width</replaceable> is from the
               <literal>pw</literal> capability and
               <replaceable>length</replaceable> is from the
               <literal>pl</literal> capability for the printer in
               question.</para>
           </listitem>
         </itemizedlist>
 
         <para>Do not be seduced by an output filter's simplicity.  If you
           would like each file in a job to start on a different page an output
           filter <emphasis>will not work</emphasis>.  Use a text filter (also
           known as an input filter); see section <link
             linkend="printing-textfilter">Installing the Text Filter</link>.
           Furthermore, an output filter is actually <emphasis>more
             complex</emphasis> in that it has to examine the byte stream being
           sent to it for special flag characters and must send signals to
           itself on behalf of <application>LPD</application>.</para>
 
         <para>However, an output filter is <emphasis>necessary</emphasis> if
           you want header pages and need to send escape sequences or other
           initialization strings to be able to print the header page.  (But it
           is also <emphasis>futile</emphasis> if you want to charge header
           pages to the requesting user's account, since
 	  <application>LPD</application> does not give any
           user or host information to the output filter.)</para>
 
         <para>On a single printer, <application>LPD</application>
 	  allows both an output filter and text or other filters.  In
 	  such cases, <application>LPD</application> will start the
 	  output filter
           to print the header page (see section <link
             linkend="printing-advanced-header-pages">Header Pages</link>)
           only.  <application>LPD</application> then expects the
 	  output filter to <emphasis>stop
             itself</emphasis> by sending two bytes to the filter: ASCII 031
           followed by ASCII 001.  When an output filter sees these two bytes
           (031, 001), it should stop by sending <literal>SIGSTOP</literal>
 	  to itself.  When
 	  <application>LPD</application>'s
           done running other filters, it will restart the output filter by
           sending <literal>SIGCONT</literal> to it.</para>
 
         <para>If there is an output filter but <emphasis>no</emphasis> text
           filter and <application>LPD</application> is working on a plain
 	  text job, <application>LPD</application> uses the output
           filter to do the job.  As stated before, the output filter will
           print each file of the job in sequence with no intervening form
           feeds or other paper advancement, and this is probably
           <emphasis>not</emphasis> what you want.  In almost all cases, you
           need a text filter.</para>
 
         <para>The program <command>lpf</command>, which we introduced earlier
           as a text filter, can also run as an output filter.  If you need a
           quick-and-dirty output filter but do not want to write the byte
           detection and signal sending code, try <command>lpf</command>.  You
           can also wrap <command>lpf</command> in a shell script to handle any
           initialization codes the printer might require.</para>
       </sect3>
 
       <sect3 id="printing-advanced-lpf">
         <title><command>lpf</command>: a Text Filter</title>
 
         <para>The program <filename>/usr/libexec/lpr/lpf</filename> that comes
           with FreeBSD binary distribution is a text filter (input filter)
           that can indent output (job submitted with <command>lpr
             -i</command>), allow literal characters to pass (job submitted
           with <command>lpr -l</command>), adjust the printing position for
           backspaces and tabs in the job, and account for pages printed.  It
           can also act like an output filter.</para>
 
         <para><command>lpf</command> is suitable for many printing
           environments.  And although it has no capability to send
           initialization sequences to a printer, it is easy to write a shell
           script to do the needed initialization and then execute
           <command>lpf</command>.</para>
 
         <indexterm><primary>page accounting</primary></indexterm>
         <indexterm>
           <primary>accounting</primary>
           <secondary>printer</secondary>
         </indexterm>
         <para>In order for <command>lpf</command> to do page accounting
           correctly, it needs correct values filled in for the
           <literal>pw</literal> and <literal>pl</literal> capabilities in the
           <filename>/etc/printcap</filename> file.  It uses these values to
           determine how much text can fit on a page and how many pages were in
           a user's job.  For more information on printer accounting, see <link
             linkend="printing-advanced-acct">Accounting for Printer
             Usage</link>.</para>
       </sect3>
     </sect2>
 
     <sect2 id="printing-advanced-header-pages">
       <title>Header Pages</title>
 
       <para>If you have <emphasis>lots</emphasis> of users, all of them using
         various printers, then you probably want to consider <emphasis>header
           pages</emphasis> as a necessary evil.</para>
 
       <indexterm>
         <primary>banner pages</primary>
 	<see>header pages</see>
       </indexterm>
       <indexterm><primary>header pages</primary></indexterm>
       <para>Header pages, also known as <emphasis>banner</emphasis> or
         <emphasis>burst pages</emphasis> identify to whom jobs belong after
         they are printed.  They are usually printed in large, bold letters,
         perhaps with decorative borders, so that in a stack of printouts they
         stand out from the real documents that comprise users' jobs.  They
         enable users to locate their jobs quickly.  The obvious drawback to a
         header page is that it is yet one more sheet that has to be printed
         for every job, their ephemeral usefulness lasting not more than a few
         minutes, ultimately finding themselves in a recycling bin or rubbish
         heap.  (Note that header pages go with each job, not each file in a
         job, so the paper waste might not be that bad.)</para>
 
       <para>The <application>LPD</application> system can provide header
 	pages automatically for your
         printouts <emphasis>if</emphasis> your printer can directly print
        plain text.  If you have a &postscript; printer, you will need an
         external program to generate the header page; see <link
           linkend="printing-advanced-header-pages-ps">Header Pages on
           &postscript; Printers</link>.</para>
 
           <sect3 id="printing-advanced-header-pages-enabling">
         <title>Enabling Header Pages</title>
 
         <para>In the <link linkend="printing-simple">Simple Printer
             Setup</link> section, we turned off header pages by specifying
           <literal>sh</literal> (meaning <quote>suppress header</quote>) in the
           <filename>/etc/printcap</filename> file.  To enable header pages for
           a printer, just remove the <literal>sh</literal> capability.</para>
 
         <para>Sounds too easy, right?</para>
 
         <para>You are right.  You <emphasis>might</emphasis> have to provide
           an output filter to send initialization strings to the printer.
           Here is an example output filter for Hewlett Packard PCL-compatible
           printers:</para>
 
         <programlisting>#!/bin/sh
 #
 #  hpof - Output filter for Hewlett Packard PCL-compatible printers
 #  Installed in /usr/local/libexec/hpof
 
 printf "\033&amp;k2G" || exit 2
 exec /usr/libexec/lpr/lpf</programlisting>
 
         <para>Specify the path to the output filter in the
           <literal>of</literal> capability.  See the <link
             linkend="printing-advanced-of">Output Filters</link> section for more
           information.</para>
 
         <para>Here is an example <filename>/etc/printcap</filename> file for
           the printer <literal>teak</literal> that we introduced earlier; we
           enabled header pages and added the above output filter:</para>
 
         <programlisting>#
 #  /etc/printcap for host orchid
 #
 teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\
         :lp=/dev/lpt0:sd=/var/spool/lpd/teak:mx#0:\
         :if=/usr/local/libexec/hpif:\
         :vf=/usr/local/libexec/hpvf:\
         :of=/usr/local/libexec/hpof:</programlisting>
 
         <para>Now, when users print jobs to <literal>teak</literal>, they get
           a header page with each job.  If users want to spend time searching
           for their printouts, they can suppress header pages by submitting
           the job with <command>lpr -h</command>; see the <link
             linkend="printing-lpr-options-misc">Header Page Options</link> section for
           more &man.lpr.1; options.</para>
 
         <note>
           <para><application>LPD</application> prints a form feed character
 	    after the header page. If
             your printer uses a different character or sequence of characters
             to eject a page, specify them with the <literal>ff</literal>
             capability in <filename>/etc/printcap</filename>.</para>
         </note>
       </sect3>
 
       <sect3 id="printing-advanced-header-pages-controlling">
         <title>Controlling Header Pages</title>
 
         <para>By enabling header pages, <application>LPD</application> will
 	  produce a <emphasis>long
             header</emphasis>, a full page of large letters identifying the
           user, host, and job.  Here is an example (kelly printed the job
           named outline from host <hostid>rose</hostid>):</para>
 
         <programlisting>      k                   ll       ll
       k                    l        l
       k                    l        l
       k   k     eeee       l        l     y    y
       k  k     e    e      l        l     y    y
       k k      eeeeee      l        l     y    y
       kk k     e           l        l     y    y
       k   k    e    e      l        l     y   yy
       k    k    eeee      lll      lll     yyy y
                                                y
                                           y    y
                                            yyyy
 
 
                                    ll
                           t         l        i
                           t         l
        oooo    u    u   ttttt       l       ii     n nnn     eeee
       o    o   u    u     t         l        i     nn   n   e    e
       o    o   u    u     t         l        i     n    n   eeeeee
       o    o   u    u     t         l        i     n    n   e
       o    o   u   uu     t  t      l        i     n    n   e    e
        oooo     uuu u      tt      lll      iii    n    n    eeee
 
 
 
 
 
 
 
 
 
       r rrr     oooo     ssss     eeee
       rr   r   o    o   s    s   e    e
       r        o    o    ss      eeeeee
       r        o    o      ss    e
       r        o    o   s    s   e    e
       r         oooo     ssss     eeee
 
 
 
 
 
 
 
                                               Job:  outline
                                               Date: Sun Sep 17 11:04:58 1995</programlisting>
 
         <para><application>LPD</application> appends a form feed after this
 	  text so the job starts on a
           new page (unless you have <literal>sf</literal> (suppress form
           feeds) in the destination printer's entry in
           <filename>/etc/printcap</filename>).</para>
 
         <para>If you prefer, <application>LPD</application> can make a
 	  <emphasis>short header</emphasis>;
           specify <literal>sb</literal> (short banner) in the
           <filename>/etc/printcap</filename> file. The header page will look
           like this:</para>
 
         <programlisting>rose:kelly  Job: outline  Date: Sun Sep 17 11:07:51 1995</programlisting>
 
         <para>Also by default, <application>LPD</application> prints the
 	  header page first, then the job.
           To reverse that, specify <literal>hl</literal> (header last) in
           <filename>/etc/printcap</filename>.</para>
       </sect3>
 
       <sect3 id="printing-advanced-header-pages-accounting">
         <title>Accounting for Header Pages</title>
 
         <para>Using <application>LPD</application>'s built-in header pages
 	  enforces a particular paradigm
           when it comes to printer accounting: header pages must be
           <emphasis>free of charge</emphasis>.</para>
 
         <para>Why?</para>
 
         <para>Because the output filter is the only external program that will
           have control when the header page is printed that could do
           accounting, and it is not provided with any <emphasis>user or
             host</emphasis> information or an accounting file, so it has no
           idea whom to charge for printer use.  It is also not enough to just
           <quote>add one page</quote> to the text filter or any of the
           conversion filters (which do have user and host information) since
           users can suppress header pages with <command>lpr -h</command>.
           They could still be charged for header pages they did not print.
           Basically, <command>lpr -h</command> will be the preferred option of
           environmentally-minded users, but you cannot offer any incentive to
           use it.</para>
 
         <para>It is <emphasis>still not enough</emphasis> to have each of the
           filters generate their own header pages (thereby being able to
           charge for them).  If users wanted the option of suppressing the
           header pages with <command>lpr -h</command>, they will still get
           them and be charged for them since <application>LPD</application>
 	  does not pass any knowledge
           of the <option>-h</option> option to any of the filters.</para>
 
         <para>So, what are your options?</para>
 
         <para>You can:</para>
 
         <itemizedlist>
           <listitem>
             <para>Accept <application>LPD</application>'s paradigm and make
 	      header pages free.</para>
           </listitem>
 
           <listitem>
             <para>Install an alternative to <application>LPD</application>,
 	      such as
 		<application>LPRng</application>. Section
               <link linkend="printing-lpd-alternatives">Alternatives to the
                 Standard Spooler</link> tells more about other spooling
               software you can substitute for <application>LPD</application>.
 	    </para>
           </listitem>
 
           <listitem>
             <para>Write a <emphasis>smart</emphasis> output filter. Normally,
               an output filter is not meant to do anything more than
               initialize a printer or do some simple character conversion.  It
               is suited for header pages and plain text jobs (when there is no
               text (input) filter).  But, if there is a text filter for the
               plain text jobs, then <application>LPD</application> will start
 	      the output filter only for
               the header pages.  And the output filter can parse the header
               page text that <application>LPD</application> generates to
 	      determine what user and host to
               charge for the header page.  The only other problem with this
               method is that the output filter still does not know what
               accounting file to use (it is not passed the name of the file
               from the <literal>af</literal> capability), but if you have a
               well-known accounting file, you can hard-code that into the
               output filter.  To facilitate the parsing step, use the
               <literal>sh</literal> (short header) capability in
               <filename>/etc/printcap</filename>.  Then again, all that might
               be too much trouble, and users will certainly appreciate the
               more generous system administrator who makes header pages
               free.</para>
           </listitem>
         </itemizedlist>
       </sect3>
 
       <sect3 id="printing-advanced-header-pages-ps">
         <title>Header Pages on &postscript; Printers</title>
 
         <para>As described above, <application>LPD</application> can generate
 	  a plain text header page
           suitable for many printers.  Of course, &postscript; cannot directly
           print plain text, so the header page feature of
 	  <application>LPD</application> is
           useless&mdash;or mostly so.</para>
 
         <para>One obvious way to get header pages is to have every conversion
           filter and the text filter generate the header page. The filters
           should use the user and host arguments to generate a suitable
           header page.  The drawback of this method is that users will always
           get a header page, even if they submit jobs with <command>lpr
             -h</command>.</para>
 
         <para>Let us explore this method.  The following script takes three
           arguments (user login name, host name, and job name) and makes a
           simple &postscript; header page:</para>
 
         <programlisting>#!/bin/sh
 #
 #  make-ps-header - make a PostScript header page on stdout
 #  Installed in /usr/local/libexec/make-ps-header
 #
 
 #
 #  These are PostScript units (72 to the inch).  Modify for A4 or
 #  whatever size paper you are using:
 #
 page_width=612
 page_height=792
 border=72
 
 #
 #  Check arguments
 #
 if [ $# -ne 3 ]; then
     echo "Usage: `basename $0` &lt;user&gt; &lt;host&gt; &lt;job&gt;" 1&gt;&amp;2
     exit 1
 fi
 
 #
 #  Save these, mostly for readability in the PostScript, below.
 #
 user=$1
 host=$2
 job=$3
 date=`date`
 
 #
 #  Send the PostScript code to stdout.
 #
 exec cat &lt;&lt;EOF
 %!PS
 
 %
 %  Make sure we do not interfere with user's job that will follow
 %
 save
 
 %
 %  Make a thick, unpleasant border around the edge of the paper.
 %
 $border $border moveto
 $page_width $border 2 mul sub 0 rlineto
 0 $page_height $border 2 mul sub rlineto
 currentscreen 3 -1 roll pop 100 3 1 roll setscreen
 $border 2 mul $page_width sub 0 rlineto closepath
 0.8 setgray 10 setlinewidth stroke 0 setgray
 
 %
 %  Display user's login name, nice and large and prominent
 %
 /Helvetica-Bold findfont 64 scalefont setfont
 $page_width ($user) stringwidth pop sub 2 div $page_height 200 sub moveto
 ($user) show
 
 %
 %  Now show the boring particulars
 %
 /Helvetica findfont 14 scalefont setfont
 /y 200 def
 [ (Job:) (Host:) (Date:) ] {
 200 y moveto show /y y 18 sub def }
 forall
 
 /Helvetica-Bold findfont 14 scalefont setfont
 /y 200 def
 [ ($job) ($host) ($date) ] {
         270 y moveto show /y y 18 sub def
 } forall
 
 %
 % That is it
 %
 restore
 showpage
 EOF</programlisting>
 
         <para>Now, each of the conversion filters and the text filter can call
           this script to first generate the header page, and then print the
           user's job.  Here is the DVI conversion filter from earlier in this
           document, modified to make a header page:</para>
 
         <programlisting>#!/bin/sh
 #
 #  psdf - DVI to PostScript printer filter
 #  Installed in /usr/local/libexec/psdf
 #
 #  Invoked by lpd when user runs lpr -d
 #
 
 orig_args="$@"
 
 fail() {
     echo "$@" 1&gt;&amp;2
     exit 2
 }
 
 while getopts "x:y:n:h:" option; do
     case $option in
         x|y)  ;; # Ignore
         n)    login=$OPTARG ;;
         h)    host=$OPTARG ;;
         *)    echo "LPD started `basename $0` wrong." 1&gt;&amp;2
               exit 2
               ;;
     esac
 done
 
 [ "$login" ] || fail "No login name"
 [ "$host" ] || fail "No host name"
 
 ( /usr/local/libexec/make-ps-header $login $host "DVI File"
   /usr/local/bin/dvips -f ) | eval /usr/local/libexec/lprps $orig_args</programlisting>
 
         <para>Notice how the filter has to parse the argument list in order to
           determine the user and host name.  The parsing for the other
           conversion filters is identical.  The text filter takes a slightly
           different set of arguments, though (see section <link
             linkend="printing-advanced-filters">How      Filters
             Work</link>).</para>
 
         <para>As we have mentioned before, the above scheme, though fairly
           simple, disables the <quote>suppress header page</quote> option (the
           <option>-h</option> option) to <command>lpr</command>.  If users
           wanted to save a tree (or a few pennies, if you charge for header
           pages), they would not be able to do so, since every filter's going
           to print a header page with every job.</para>
 
         <para>To allow users to shut off header pages on a per-job basis, you
           will need to use the trick introduced in section <link
             linkend="printing-advanced-header-pages-accounting">Accounting for
             Header Pages</link>: write an output filter that parses the
           LPD-generated header page and produces a &postscript; version.  If the
           user submits the job with <command>lpr -h</command>, then
 	  <application>LPD</application> will
           not generate a header page, and neither will your output filter.
           Otherwise, your output filter will read the text from
 	  <application>LPD</application> and send
           the appropriate header page &postscript; code to the printer.</para>
 
         <para>If you have a &postscript; printer on a serial line, you can make
           use of <command>lprps</command>, which comes with an output filter,
           <command>psof</command>, which does the above.  Note that
           <command>psof</command> does not charge for header pages.</para>
       </sect3>
     </sect2>
 
     <sect2 id="printing-advanced-network-printers">
       <title>Networked Printing</title>
 
       <indexterm>
         <primary>printers</primary>
         <secondary>network</secondary>
       </indexterm>
       <indexterm><primary>network printing</primary></indexterm>
       <para>FreeBSD supports networked printing: sending jobs to remote
         printers.  Networked printing generally refers to two different
         things:</para>
 
       <itemizedlist>
         <listitem>
           <para>Accessing a printer attached to a remote host.  You install a
             printer that has a conventional serial or parallel interface on
             one host.  Then, you set up <application>LPD</application> to
 	    enable access to the printer
             from other hosts on the network. Section <link
               linkend="printing-advanced-network-rm">Printers Installed on
               Remote Hosts</link> tells how to do this.</para>
         </listitem>
 
         <listitem>
           <para>Accessing a printer attached directly to a network.  The
             printer has a network interface in addition (or in place of) a
             more conventional serial or parallel interface.  Such a printer
             might work as follows:</para>
 
           <itemizedlist>
             <listitem>
               <para>It might understand the <application>LPD</application>
 		protocol and can even queue
                 jobs from remote hosts.  In this case, it acts just like a
                 regular host running <application>LPD</application>.  Follow
 		the same procedure in
                 section <link linkend="printing-advanced-network-rm">Printers
                   Installed on Remote Hosts</link> to set up such a
                 printer.</para>
             </listitem>
 
             <listitem>
               <para>It might support a data stream network connection. In this
                 case, you <quote>attach</quote> the printer to one host on the
                 network by making that host responsible for spooling jobs and
                 sending them to the printer. Section <link
                   linkend="printing-advanced-network-net-if">Printers with
                   Networked Data Stream Interfaces</link> gives some
                 suggestions on installing such printers.</para>
             </listitem>
           </itemizedlist>
         </listitem>
       </itemizedlist>
 
       <sect3 id="printing-advanced-network-rm">
         <title>Printers Installed on Remote Hosts</title>
 
         <para>The <application>LPD</application> spooling system has built-in
 	  support for sending jobs to
           other hosts also running <application>LPD</application> (or are
 	  compatible with <application>LPD</application>).  This
           feature enables you to install a printer on one host and make it
           accessible from other hosts.  It also works with printers that have
           network interfaces that understand the
 	  <application>LPD</application> protocol.</para>
 
         <para>To enable this kind of remote printing, first install a printer
           on one host, the <emphasis>printer host</emphasis>, using the simple
           printer setup described in the <link linkend="printing-simple">Simple
             Printer Setup</link> section.  Do any advanced setup in <link
             linkend="printing-advanced">Advanced Printer Setup</link> that you
           need.  Make sure to test the printer and see if it works with the
           features of <application>LPD</application> you have enabled.
 	  Also ensure that the
           <emphasis>local host</emphasis> has authorization to use the
 	  <application>LPD</application>
           service in the <emphasis>remote host</emphasis> (see <link
             linkend="printing-advanced-restricting-remote">Restricting Jobs
             from Remote Printers</link>).</para>
 
         <indexterm>
           <primary>printers</primary>
           <secondary>network</secondary>
         </indexterm>
         <indexterm><primary>network printing</primary></indexterm>
         <para>If you are using a printer with a network interface that is
           compatible with <application>LPD</application>, then the
 	  <emphasis>printer host</emphasis> in
           the discussion below is the printer itself, and the
           <emphasis>printer name</emphasis> is the name you configured for the
           printer.  See the documentation that accompanied your printer and/or
           printer-network interface.</para>
 
         <tip>
           <para>If you are using a Hewlett Packard Laserjet then the printer
             name <literal>text</literal> will automatically perform the LF to
             CRLF conversion for you, so you will not require the
             <filename>hpif</filename> script.</para>
         </tip>
 
         <para>Then, on the other hosts you want to have access to the printer,
           make an entry in their <filename>/etc/printcap</filename> files with
           the following:</para>
 
         <orderedlist>
           <listitem>
             <para>Name the entry anything you want.  For simplicity, though,
               you probably want to use the same name and aliases as on the
               printer host.</para>
           </listitem>
 
           <listitem>
             <para>Leave the <literal>lp</literal> capability blank, explicitly
               (<literal>:lp=:</literal>).</para>
           </listitem>
 
           <listitem>
             <para>Make a spooling directory and specify its location in the
               <literal>sd</literal> capability.  <application>LPD</application>
 	      will store jobs here
               before they get sent to the printer host.</para>
           </listitem>
 
           <listitem>
             <para>Place the name of the printer host in the
               <literal>rm</literal> capability.</para>
           </listitem>
 
           <listitem>
             <para>Place the printer name on the <emphasis>printer
                 host</emphasis> in the <literal>rp</literal>
               capability.</para>
           </listitem>
         </orderedlist>
 
         <para>That is it.  You do not need to list conversion filters, page
           dimensions, or anything else in the
           <filename>/etc/printcap</filename> file.</para>
 
         <para>Here is an example.  The host <hostid>rose</hostid> has two
           printers, <literal>bamboo</literal> and <literal>rattan</literal>.
           We will enable users on the host <hostid>orchid</hostid> to print
           to those printers.
           Here is the <filename>/etc/printcap</filename> file for
           <hostid>orchid</hostid> (back from section <link
             linkend="printing-advanced-header-pages-enabling">Enabling Header
             Pages</link>).  It already had the entry for the printer
           <literal>teak</literal>; we have added entries for the two printers
           on the host <hostid>rose</hostid>:</para>
 
         <programlisting>#
 #  /etc/printcap for host orchid - added (remote) printers on rose
 #
 
 #
 #  teak is local; it is connected directly to orchid:
 #
 teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\
         :lp=/dev/lpt0:sd=/var/spool/lpd/teak:mx#0:\
         :if=/usr/local/libexec/ifhp:\
         :vf=/usr/local/libexec/vfhp:\
         :of=/usr/local/libexec/ofhp:
 
 #
 #  rattan is connected to rose; send jobs for rattan to rose:
 #
 rattan|line|diablo|lp|Diablo 630 Line Printer:\
         :lp=:rm=rose:rp=rattan:sd=/var/spool/lpd/rattan:
 
 #
 #  bamboo is connected to rose as well:
 #
 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
         :lp=:rm=rose:rp=bamboo:sd=/var/spool/lpd/bamboo:</programlisting>
 
         <para>Then, we just need to make spooling directories on
           <hostid>orchid</hostid>:</para>
 
         <screen>&prompt.root; <userinput>mkdir -p /var/spool/lpd/rattan /var/spool/lpd/bamboo</userinput>
 &prompt.root; <userinput>chmod 770 /var/spool/lpd/rattan /var/spool/lpd/bamboo</userinput>
 &prompt.root; <userinput>chown daemon:daemon /var/spool/lpd/rattan /var/spool/lpd/bamboo</userinput></screen>
 
         <para>Now, users on <hostid>orchid</hostid> can print to
           <literal>rattan</literal> and <literal>bamboo</literal>.  If, for
           example, a user on <hostid>orchid</hostid> typed
 
           <screen>&prompt.user; <userinput>lpr -P bamboo -d sushi-review.dvi</userinput></screen>
 
           the <application>LPD</application> system on <hostid>orchid</hostid>
 	  would copy the job to the spooling
           directory <filename>/var/spool/lpd/bamboo</filename> and note that it was a
           DVI job.  As soon as the host <hostid>rose</hostid> has room in its
           <literal>bamboo</literal> spooling directory, the two
 	  <application>LPDs</application> would transfer the
           file to <hostid>rose</hostid>.  The file would wait in <hostid>rose</hostid>'s
           queue until it was finally printed.  It would be converted from DVI to
           &postscript; (since <literal>bamboo</literal> is a &postscript; printer) on
           <hostid>rose</hostid>.</para>
       </sect3>
 
       <sect3 id="printing-advanced-network-net-if">
         <title>Printers with Networked Data Stream Interfaces</title>
 
         <para>Often, when you buy a network interface card for a printer, you
           can get two versions: one which emulates a spooler (the more
           expensive version), or one which just lets you send data to it as if
           you were using a serial or parallel port (the cheaper version).
           This section tells how to use the cheaper version. For the more
           expensive one, see the previous section <link
             linkend="printing-advanced-network-rm">Printers Installed on
             Remote Hosts</link>.</para>
 
         <para>The format of the <filename>/etc/printcap</filename> file lets
           you specify what serial or parallel interface to use, and (if you
           are using a serial interface), what baud rate, whether to use flow
           control, delays for tabs, conversion of newlines, and more.  But
           there is no way to specify a connection to a printer that is
           listening on a TCP/IP or other network port.</para>
 
         <para>To send data to a networked printer, you need to develop a
           communications program that can be called by the text and conversion
           filters.  Here is one such example: the script
           <command>netprint</command> takes all data on standard input and
           sends it to a network-attached printer.  We specify the hostname of
           the printer as the first argument and the port number to which to
           connect as the second argument to <command>netprint</command>.  Note
           that this supports one-way communication only (FreeBSD to printer);
           many network printers support two-way communication, and you might
           want to take advantage of that (to get printer status, perform
           accounting, etc.).</para>
 
         <programlisting>#!/usr/bin/perl
 #
 #  netprint - Text filter for printer attached to network
 #  Installed in /usr/local/libexec/netprint
 #
 $#ARGV eq 1 || die "Usage: $0 &lt;printer-hostname&gt; &lt;port-number&gt;";
 
 $printer_host = $ARGV[0];
 $printer_port = $ARGV[1];
 
 require 'sys/socket.ph';
 
 ($ignore, $ignore, $protocol) = getprotobyname('tcp');
 ($ignore, $ignore, $ignore, $ignore, $address)
     = gethostbyname($printer_host);
 
 $sockaddr = pack('S n a4 x8', &amp;AF_INET, $printer_port, $address);
 
 socket(PRINTER, &amp;PF_INET, &amp;SOCK_STREAM, $protocol)
     || die "Can't create TCP/IP stream socket: $!";
 connect(PRINTER, $sockaddr) || die "Can't contact $printer_host: $!";
 while (&lt;STDIN&gt;) { print PRINTER; }
 exit 0;</programlisting>
 
         <para>We can then use this script in various filters.  Suppose we had
           a Diablo 750-N line printer connected to the network.  The printer
           accepts data to print on port number 5100.  The host name of the
           printer is scrivener.  Here is the text filter for the
           printer:</para>
 
         <programlisting>#!/bin/sh
 #
 #  diablo-if-net - Text filter for Diablo printer `scrivener' listening
 #  on port 5100.   Installed in /usr/local/libexec/diablo-if-net
 #
 exec /usr/libexec/lpr/lpf "$@" | /usr/local/libexec/netprint scrivener 5100</programlisting>
       </sect3>
     </sect2>
 
     <sect2 id="printing-advanced-restricting">
       <title>Restricting Printer Usage</title>
 
       <indexterm>
         <primary>printers</primary>
         <secondary>restricting access to</secondary>
       </indexterm>
       <para>This section gives information on restricting printer usage. The
         <application>LPD</application> system lets you control who can access
 	a printer, both locally or
         remotely, whether they can print multiple copies, how large their jobs
         can be, and how large the printer queues can get.</para>
 
       <sect3 id="printing-advanced-restricting-copies">
         <title>Restricting Multiple Copies</title>
 
         <para>The <application>LPD</application> system makes it easy for
 	  users to print multiple copies
           of a file.  Users can print jobs with <command>lpr -#5</command>
           (for example) and get five copies of each file in the job.  Whether
           this is a good thing is up to you.</para>
 
         <para>If you feel multiple copies cause unnecessary wear and tear on
           your printers, you can disable the <option>-#</option> option to
             &man.lpr.1; by adding the <literal>sc</literal> capability to the
           <filename>/etc/printcap</filename> file.  When users submit jobs
           with the <option>-#</option> option, they will see:</para>
 
         <screen>lpr: multiple copies are not allowed</screen>
 
 
         <para>Note that if you have set up access to a printer remotely (see
           section <link linkend="printing-advanced-network-rm">Printers
             Installed on Remote Hosts</link>), you need the
           <literal>sc</literal> capability on the remote
           <filename>/etc/printcap</filename> files as well, or else users will
           still be able to submit multiple-copy jobs by using another
           host.</para>
 
         <para>Here is an example.  This is the
           <filename>/etc/printcap</filename> file for the host
           <hostid>rose</hostid>.  The printer <literal>rattan</literal> is
           quite hearty, so we will allow multiple copies, but the laser
           printer <literal>bamboo</literal> is a bit more delicate, so we will
           disable multiple copies by adding the <literal>sc</literal>
           capability:</para>
 
         <programlisting>#
 #  /etc/printcap for host rose - restrict multiple copies on bamboo
 #
 rattan|line|diablo|lp|Diablo 630 Line Printer:\
         :sh:sd=/var/spool/lpd/rattan:\
         :lp=/dev/lpt0:\
         :if=/usr/local/libexec/if-simple:
 
 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
         :sh:sd=/var/spool/lpd/bamboo:sc:\
         :lp=/dev/ttyd5:ms#-parenb cs8 clocal crtscts:rw:\
         :if=/usr/local/libexec/psif:\
         :df=/usr/local/libexec/psdf:</programlisting>
 
         <para>Now, we also need to add the <literal>sc</literal> capability on
           the host <hostid>orchid</hostid>'s
           <filename>/etc/printcap</filename> (and while we are at it, let us
           disable multiple copies for the printer
           <literal>teak</literal>):</para>
 
         <programlisting>#
 #  /etc/printcap for host orchid - no multiple copies for local
 #  printer teak or remote printer bamboo
 teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\
         :lp=/dev/lpt0:sd=/var/spool/lpd/teak:mx#0:sc:\
         :if=/usr/local/libexec/ifhp:\
         :vf=/usr/local/libexec/vfhp:\
         :of=/usr/local/libexec/ofhp:
 
 rattan|line|diablo|lp|Diablo 630 Line Printer:\
         :lp=:rm=rose:rp=rattan:sd=/var/spool/lpd/rattan:
 
 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
         :lp=:rm=rose:rp=bamboo:sd=/var/spool/lpd/bamboo:sc:</programlisting>
 
         <para>By using the <literal>sc</literal> capability, we prevent the
           use of <command>lpr -#</command>, but that still does not prevent
           users from running &man.lpr.1;
           multiple times, or from submitting the same file multiple times in
           one job like this:</para>
 
         <screen>&prompt.user; <userinput>lpr forsale.sign forsale.sign forsale.sign forsale.sign forsale.sign</userinput></screen>
 
         <para>There are many ways to prevent this abuse (including ignoring
           it) which you are free to explore.</para>
       </sect3>
 
       <sect3 id="printing-advanced-restricting-access">
         <title>Restricting Access to Printers</title>
 
         <para>You can control who can print to what printers by using the &unix;
           group mechanism and the <literal>rg</literal> capability in
           <filename>/etc/printcap</filename>.  Just place the users you want
           to have access to a printer in a certain group, and then name that
           group in the <literal>rg</literal> capability.</para>
 
         <para>Users outside the group (including <username>root</username>)
 	  will be greeted with
 
           <errorname>lpr: Not a member of the restricted group</errorname>
 
           if they try to print to the controlled printer.</para>
 
         <para>As with the <literal>sc</literal> (suppress multiple copies)
           capability, you need to specify <literal>rg</literal> on remote
           hosts that also have access to your printers, if you feel it is
           appropriate (see section <link
             linkend="printing-advanced-network-rm">Printers Installed on
             Remote Hosts</link>).</para>
 
         <para>For example, we will let anyone access the printer
           <literal>rattan</literal>, but only those in group
           <literal>artists</literal> can use <literal>bamboo</literal>.  Here
           is the familiar <filename>/etc/printcap</filename> for host
           <hostid>rose</hostid>:</para>
 
         <programlisting>#
 #  /etc/printcap for host rose - restricted group for bamboo
 #
 rattan|line|diablo|lp|Diablo 630 Line Printer:\
         :sh:sd=/var/spool/lpd/rattan:\
         :lp=/dev/lpt0:\
         :if=/usr/local/libexec/if-simple:
 
 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
         :sh:sd=/var/spool/lpd/bamboo:sc:rg=artists:\
         :lp=/dev/ttyd5:ms#-parenb cs8 clocal crtscts:rw:\
         :if=/usr/local/libexec/psif:\
         :df=/usr/local/libexec/psdf:</programlisting>
 
         <para>Let us leave the other example
           <filename>/etc/printcap</filename> file (for the host
           <hostid>orchid</hostid>) alone.  Of course, anyone on
           <hostid>orchid</hostid> can print to <literal>bamboo</literal>.  It
           might be the case that we only allow certain logins on
           <hostid>orchid</hostid> anyway, and want them to have access to the
           printer.  Or not.</para>
 
         <note>
           <para>There can be only one restricted group per printer.</para>
         </note>
       </sect3>
 
       <sect3 id="printing-advanced-restricting-sizes">
         <title>Controlling Sizes of Jobs Submitted</title>
 
         <indexterm><primary>print jobs</primary></indexterm>
         <para>If you have many users accessing the printers, you probably need
           to put an upper limit on the sizes of the files users can submit to
           print.  After all, there is only so much free space on the
           filesystem that houses the spooling directories, and you also need
           to make sure there is room for the jobs of other users.</para>
 
         <indexterm>
           <primary>print jobs</primary>
           <secondary>controlling</secondary>
         </indexterm>
         <para><application>LPD</application> enables you to limit the maximum
 	  byte size a file in a job
           can be with the <literal>mx</literal> capability. The units are in
           <literal>BUFSIZ</literal> blocks, which are 1024 bytes.  If you put
 	  a zero for this
           capability, there will be no limit on file size; however, if no
           <literal>mx</literal> capability is specified, then a default limit
           of 1000 blocks will be used.</para>
 
         <note>
           <para>The limit applies to <emphasis>files</emphasis> in a job, and
             <emphasis>not</emphasis> the total job size.</para>
         </note>
 
         <para><application>LPD</application> will not refuse a file that is
 	  larger than the limit you
           place on a printer.  Instead, it will queue as much of the file up
           to the limit, which will then get printed.  The rest will be
           discarded.  Whether this is correct behavior is up for
           debate.</para>
 
         <para>Let us add limits to our example printers
           <literal>rattan</literal> and <literal>bamboo</literal>.  Since
           those artists' &postscript; files tend to be large, we will limit them
           to five megabytes. We will put no limit on the plain text line
           printer:</para>
 
         <programlisting>#
 #  /etc/printcap for host rose
 #
 
 #
 #  No limit on job size:
 #
 rattan|line|diablo|lp|Diablo 630 Line Printer:\
         :sh:mx#0:sd=/var/spool/lpd/rattan:\
         :lp=/dev/lpt0:\
         :if=/usr/local/libexec/if-simple:
 
 #
 #  Limit of five megabytes:
 #
 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
         :sh:sd=/var/spool/lpd/bamboo:sc:rg=artists:mx#5000:\
         :lp=/dev/ttyd5:ms#-parenb cs8 clocal crtscts:rw:\
         :if=/usr/local/libexec/psif:\
         :df=/usr/local/libexec/psdf:</programlisting>
 
         <para>Again, the limits apply to the local users only.  If you have
           set up access to your printers remotely, remote users will not get
           those limits.  You will need to specify the <literal>mx</literal>
           capability in the remote <filename>/etc/printcap</filename> files as
           well.  See section <link
             linkend="printing-advanced-network-rm">Printers Installed      on
             Remote Hosts</link> for more information on remote
           printing.</para>
 
         <para>There is another specialized way to limit job sizes from remote
           printers; see section <link
             linkend="printing-advanced-restricting-remote">Restricting Jobs
             from Remote Printers</link>.</para>
       </sect3>
 
       <sect3 id="printing-advanced-restricting-remote">
         <title>Restricting Jobs from Remote Printers</title>
 
         <para>The <application>LPD</application> spooling system provides
 	  several ways to restrict print
           jobs submitted from remote hosts:</para>
 
         <variablelist>
           <varlistentry>
             <term>Host restrictions</term>
 
             <listitem>
               <para>You can control from which remote hosts a local
 		<application>LPD</application> accepts requests with the files
                 <filename>/etc/hosts.equiv</filename> and
                 <filename>/etc/hosts.lpd</filename>.
 		<application>LPD</application> checks to see if an
                 incoming request is from a host listed in either one of these
                 files.  If not, <application>LPD</application> refuses the
 		request.</para>
 
               <para>The format of these files is simple: one host name per
                 line.  Note that the file
                 <filename>/etc/hosts.equiv</filename> is also used by the
                   &man.ruserok.3; protocol, and affects programs like
                   &man.rsh.1; and &man.rcp.1;, so be careful.</para>
 
               <para>For example, here is the
                 <filename>/etc/hosts.lpd</filename> file on the host
                 <hostid>rose</hostid>:</para>
 
               <programlisting>orchid
 violet
 madrigal.fishbaum.de</programlisting>
 
               <para>This means <hostid>rose</hostid> will accept requests from
                 the hosts <hostid>orchid</hostid>, <hostid>violet</hostid>,
                 and <hostid role="fqdn">madrigal.fishbaum.de</hostid>. If any
                 other host tries to access <hostid>rose</hostid>'s
                 <application>LPD</application>, the job will be refused.</para>
             </listitem>
           </varlistentry>
 
           <varlistentry>
             <term>Size restrictions</term>
 
             <listitem>
               <para>You can control how much free space there needs to remain
                 on the filesystem where a spooling directory resides.  Make a
                 file called <filename>minfree</filename> in the spooling
                 directory for the local printer.  Insert in that file a number
                 representing how many disk blocks (512 bytes) of free space
                 there has to be for a remote job to be accepted.</para>
 
               <para>This lets you insure that remote users will not fill your
                 filesystem.  You can also use it to give a certain priority to
                 local users: they will be able to queue jobs long after the
                 free disk space has fallen below the amount specified in the
                 <filename>minfree</filename> file.</para>
 
               <para>For example, let us add a <filename>minfree</filename>
                 file for the printer <literal>bamboo</literal>.  We examine
                 <filename>/etc/printcap</filename> to find the spooling
                 directory for this printer; here is <literal>bamboo</literal>'s
                 entry:</para>
 
               <programlisting>bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
         :sh:sd=/var/spool/lpd/bamboo:sc:rg=artists:mx#5000:\
         :lp=/dev/ttyd5:ms#-parenb cs8 clocal crtscts:rw:mx#5000:\
         :if=/usr/local/libexec/psif:\
         :df=/usr/local/libexec/psdf:</programlisting>
 
               <para>The spooling directory is given in the <literal>sd</literal>
                 capability.  We will make three megabytes (which is 6144 disk blocks)
                 the amount of free disk space that must exist on the filesystem for
                 <application>LPD</application> to accept remote jobs:</para>
 
               <screen>&prompt.root; <userinput>echo 6144 &gt; /var/spool/lpd/bamboo/minfree
               </userinput></screen>
             </listitem>
           </varlistentry>
 
           <varlistentry>
             <term>User restrictions</term>
 
             <listitem>
               <para>You can control which remote users can print to local
                 printers by specifying the <literal>rs</literal> capability in
                 <filename>/etc/printcap</filename>.  When
                 <literal>rs</literal> appears in the entry for a
                 locally-attached printer, <application>LPD</application> will
 		accept jobs from remote
                 hosts <emphasis>if</emphasis> the user submitting the job also
                 has an account of the same login name on the local host.
                 Otherwise, <application>LPD</application> refuses the job.</para>
 
               <para>This capability is particularly useful in an environment
                 where there are (for example) different departments sharing a
                 network, and some users transcend departmental boundaries.  By
                 giving them accounts on your systems, they can use your
                 printers from their own departmental systems.  If you would
                 rather allow them to use <emphasis>only</emphasis> your
                 printers and not your computer resources, you can give them
                 <quote>token</quote> accounts, with no home directory and a
                 useless shell like <filename>/usr/bin/false</filename>.</para>
             </listitem>
           </varlistentry>
         </variablelist>
       </sect3>
     </sect2>
 
     <sect2 id="printing-advanced-acct">
       <title>Accounting for Printer Usage</title>
 
       <indexterm>
         <primary>accounting</primary>
         <secondary>printer</secondary>
       </indexterm>
       <para>So, you need to charge for printouts.  And why not? Paper and ink
         cost money.  And then there are maintenance costs&mdash;printers are
         loaded with moving parts and tend to break down.  You have examined
         your printers, usage patterns, and maintenance fees and have come up
         with a per-page (or per-foot, per-meter, or per-whatever) cost.  Now,
         how do you actually start accounting for printouts?</para>
 
       <para>Well, the bad news is the <application>LPD</application> spooling
 	system does not provide
         much help in this department.  Accounting is highly dependent on the
         kind of printer in use, the formats being printed, and
         <emphasis>your</emphasis> requirements in charging for printer
         usage.</para>
 
       <para>To implement accounting, you have to modify a printer's text
         filter (to charge for plain text jobs) and the conversion filters (to
         charge for other file formats), to count pages or query the printer
         for pages printed.  You cannot get away with using the simple output
         filter, since it cannot do accounting.  See section <link
           linkend="printing-advanced-filter-intro">Filters</link>.</para>
 
       <para>Generally, there are two ways to do accounting:</para>
 
       <itemizedlist>
         <listitem>
           <para><emphasis>Periodic accounting</emphasis> is the more common
             way, possibly because it is easier.  Whenever someone prints a
             job, the filter logs the user, host, and number of pages to an
             accounting file.  Every month, semester, year, or whatever time
             period you prefer, you collect the accounting files for the
             various printers, tally up the pages printed by users, and charge
             for usage.  Then you truncate all the logging files, starting with
             a clean slate for the next period.</para>
         </listitem>
 
         <listitem>
           <para><emphasis>Timely accounting</emphasis> is less common,
             probably because it is more difficult.  This method has the
             filters charge users for printouts as soon as they use the
             printers.  Like disk quotas, the accounting is immediate. You can
             prevent users from printing when their account goes in the red,
             and might provide a way for users to check and adjust their
             <quote>print quotas.</quote> But this method requires some database
             code to track users and their quotas.</para>
         </listitem>
       </itemizedlist>
 
       <para>The <application>LPD</application> spooling system supports both
 	methods easily: since you
         have to provide the filters (well, most of the time), you also have to
         provide the accounting code.  But there is a bright side: you have
         enormous flexibility in your accounting methods.  For example, you
         choose whether to use periodic or timely accounting. You choose what
         information to log: user names, host names, job types, pages printed,
         square footage of paper used, how long the job took to print, and so
         forth.  And you do so by modifying the filters to save this
         information.</para>
 
       <sect3>
         <title>Quick and Dirty Printer Accounting</title>
 
         <para>FreeBSD comes with two programs that can get you set up with
           simple periodic accounting right away.  They are the text filter
           <command>lpf</command>, described in section <link
             linkend="printing-advanced-lpf">lpf: a Text Filter</link>, and
             &man.pac.8;, a program to gather and total
           entries from printer accounting files.</para>
 
         <para>As mentioned in the section on filters (<link
             linkend="printing-advanced-filters">Filters</link>),
 	  <application>LPD</application> starts
           the text and the conversion filters with the name of the accounting
           file to use on the filter command line.  The filters can use this
           argument to know where to write an accounting file entry.  The name
           of this file comes from the <literal>af</literal> capability in
           <filename>/etc/printcap</filename>, and if not specified as an
           absolute path, is relative to the spooling directory.</para>
 
         <para><application>LPD</application> starts <command>lpf</command>
 	  with page width and length
           arguments (from the <literal>pw</literal> and <literal>pl</literal>
           capabilities).  <command>lpf</command> uses these arguments to
           determine how much paper will be used.  After sending the file to
           the printer, it then writes an accounting entry in the accounting
           file.  The entries look like this:</para>
 
         <programlisting>2.00 rose:andy
 3.00 rose:kelly
 3.00 orchid:mary
 5.00 orchid:mary
 2.00 orchid:zhang</programlisting>
 
         <para>You should use a separate accounting file for each printer, as
           <command>lpf</command> has no file locking logic built into it, and
           two <command>lpf</command>s might corrupt each other's entries if
           they were to write to the same file at the same time.  An easy way
           to insure a separate accounting file for each printer is to use
           <literal>af=acct</literal> in <filename>/etc/printcap</filename>.
           Then, each accounting file will be in the spooling directory for a
           printer, in a file named <filename>acct</filename>.</para>
 
         <para>When you are ready to charge users for printouts, run the
             &man.pac.8; program.  Just change to the spooling directory for
           the printer you want to collect on and type <literal>pac</literal>.
           You will get a dollar-centric summary like the following:</para>
 
         <screen>  Login               pages/feet   runs    price
 orchid:kelly                5.00    1   $  0.10
 orchid:mary                31.00    3   $  0.62
 orchid:zhang                9.00    1   $  0.18
 rose:andy                   2.00    1   $  0.04
 rose:kelly                177.00  104   $  3.54
 rose:mary                  87.00   32   $  1.74
 rose:root                  26.00   12   $  0.52
 
 total                     337.00  154   $  6.74</screen>
 
         <para>These are the arguments &man.pac.8; expects:</para>
 
         <variablelist>
           <varlistentry>
             <term><option>-P<replaceable>printer</replaceable></option></term>
 
             <listitem>
               <para>Which <replaceable>printer</replaceable> to summarize.
                 This option works only if there is an absolute path in the
                 <literal>af</literal> capability in
                 <filename>/etc/printcap</filename>.</para>
             </listitem>
           </varlistentry>
 
           <varlistentry>
             <term><option>-c</option></term>
 
             <listitem>
               <para>Sort the output by cost instead of alphabetically by user
                 name.</para>
             </listitem>
           </varlistentry>
 
           <varlistentry>
             <term><option>-m</option></term>
 
             <listitem>
               <para>Ignore host name in the accounting files.  With this
                 option, user <username>smith</username> on host
                 <hostid>alpha</hostid> is the same user
                 <username>smith</username> on host <hostid>gamma</hostid>.
                 Without, they are different users.</para>
             </listitem>
           </varlistentry>
 
           <varlistentry>
             <term><option>-p<replaceable>price</replaceable></option></term>
 
             <listitem>
               <para>Compute charges with <replaceable>price</replaceable>
                 dollars per page or per foot instead of the price from the
                 <literal>pc</literal> capability in
                 <filename>/etc/printcap</filename>, or two cents (the
                 default).  You can specify <replaceable>price</replaceable> as
                 a floating point number.</para>
             </listitem>
           </varlistentry>
 
           <varlistentry>
             <term><option>-r</option></term>
 
             <listitem>
               <para>Reverse the sort order.</para>
             </listitem>
           </varlistentry>
 
           <varlistentry>
             <term><option>-s</option></term>
 
             <listitem>
               <para>Make an accounting summary file and truncate the
                 accounting file.</para>
             </listitem>
           </varlistentry>
 
           <varlistentry>
             <term><replaceable>name</replaceable>
               <replaceable>&hellip;</replaceable></term>
 
             <listitem>
               <para>Print accounting information for the given user
                 <replaceable>names</replaceable> only.</para>
             </listitem>
           </varlistentry>
         </variablelist>
 
         <para>In the default summary that &man.pac.8; produces, you see the
           number of pages printed by each user from various hosts.  If, at
           your site, host does not matter (because users can use any host),
           run <command>pac -m</command>, to produce the following
           summary:</para>
 
         <screen>  Login               pages/feet   runs    price
 andy                        2.00    1   $  0.04
 kelly                     182.00  105   $  3.64
 mary                      118.00   35   $  2.36
 root                       26.00   12   $  0.52
 zhang                       9.00    1   $  0.18
 
 total                     337.00  154   $  6.74</screen>
 
 
         <para>To compute the dollar amount due,
             &man.pac.8; uses the <literal>pc</literal> capability in the
           <filename>/etc/printcap</filename> file (default of 200, or 2 cents
           per page).  Specify, in hundredths of cents, the price per page or
           per foot you want to charge for printouts in this capability.  You
           can override this value when you run &man.pac.8; with the
           <option>-p</option> option.  The units for the <option>-p</option>
           option are in dollars, though, not hundredths of cents.  For
           example,
 
           <screen>&prompt.root; <userinput>pac -p1.50</userinput></screen>
 
           makes each page cost one dollar and fifty cents.  You can really
           rake in the profits by using this option.</para>
 
         <para>Finally, running <command>pac -s</command> will save the summary
           information in a summary accounting file, which is named the same as
           the printer's accounting file, but with <literal>_sum</literal>
           appended to the name.  It then truncates the accounting file.  When
           you run &man.pac.8; again, it rereads the
           summary file to get starting totals, then adds information from the
           regular accounting file.</para>
       </sect3>
 
       <sect3>
         <title>How Can You Count Pages Printed?</title>
 
         <para>In order to perform even remotely accurate accounting, you need
           to be able to determine how much paper a job uses.  This is the
           essential problem of printer accounting.</para>
 
         <para>For plain text jobs, the problem is not that hard to solve: you
           count how many lines are in a job and compare it to how many lines
           per page your printer supports.  Do not forget to take into account
           backspaces in the file which overprint lines, or long logical lines
           that wrap onto one or more additional physical lines.</para>
 
         <para>The text filter <command>lpf</command> (introduced in <link
             linkend="printing-advanced-lpf">lpf: a Text Filter</link>) takes
           into account these things when it does accounting.  If you are
           writing a text filter which needs to do accounting, you might want
           to examine <command>lpf</command>'s source code.</para>
 
         <para>How do you handle other file formats, though?</para>
 
         <para>Well, for DVI-to-LaserJet or DVI-to-&postscript; conversion, you
           can have your filter parse the diagnostic output of
           <command>dvilj</command> or <command>dvips</command> and look to see
           how many pages were converted.  You might be able to do similar
           things with other file formats and conversion programs.</para>
 
         <para>But these methods suffer from the fact that the printer may not
           actually print all those pages.  For example, it could jam, run out
           of toner, or explode&mdash;and the user would still get
           charged.</para>
 
         <para>So, what can you do?</para>
 
         <para>There is only one <emphasis>sure</emphasis> way to do
           <emphasis>accurate</emphasis> accounting.  Get a printer that can
           tell you how much paper it uses, and attach it via a serial line or
           a network connection.  Nearly all &postscript; printers support this
           notion.  Other makes and models do as well (networked Imagen laser
           printers, for example).  Modify the filters for these printers to
           get the page usage after they print each job and have them log
           accounting information based on that value
           <emphasis>only</emphasis>.  There is no line counting nor
           error-prone file examination required.</para>
 
         <para>Of course, you can always be generous and make all printouts
           free.</para>
       </sect3>
     </sect2>
   </sect1>
 
   <sect1 id="printing-using">
     <title>Using Printers</title>
 
     <indexterm>
       <primary>printers</primary>
       <secondary>usage</secondary>
    </indexterm>
     <para>This section tells you how to use printers you have set up with
       FreeBSD.  Here is an overview of the user-level commands:</para>
 
     <variablelist>
       <varlistentry>
 	<term>&man.lpr.1;</term>
 
 	<listitem>
 	  <para>Print jobs</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>&man.lpq.1;</term>
 
 	<listitem>
 	  <para>Check printer queues</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>&man.lprm.1;</term>
 
 	<listitem>
 	  <para>Remove jobs from a printer's queue</para>
 	</listitem>
       </varlistentry>
     </variablelist>
 
     <para>There is also an administrative command, &man.lpc.8;,
       described in the section <link
 	linkend="printing-lpc">Administering Printers</link>, used to
       control printers and their queues.</para>
 
     <para>All three of the commands &man.lpr.1;, &man.lprm.1;, and &man.lpq.1;
       accept an option <option>-P
 	<replaceable>printer-name</replaceable></option> to specify on which
       printer/queue to operate, as listed in the
       <filename>/etc/printcap</filename> file.  This enables you to submit,
       remove, and check on jobs for various printers.  If you do not use the
       <option>-P</option> option, then these commands use the printer
       specified in the <envar>PRINTER</envar> environment variable.  Finally,
       if you do not have a <envar>PRINTER</envar> environment variable, these
       commands default to the printer named <literal>lp</literal>.</para>
 
     <para>Hereafter, the terminology <emphasis>default printer</emphasis>
       means the printer named in the <envar>PRINTER</envar> environment
       variable, or the printer named <literal>lp</literal> when there is no
       <envar>PRINTER</envar> environment variable.</para>
 
     <sect2 id="printing-lpr">
       <title>Printing Jobs</title>
 
       <para>To print files, type:</para>
 
       <screen>&prompt.user; <userinput>lpr <replaceable>filename</replaceable> <replaceable>...</replaceable></userinput></screen>
 
       <indexterm><primary>printing</primary></indexterm>
       <para>This prints each of the listed files to the default printer.  If
 	you list no files, &man.lpr.1; reads data to
 	print from standard input.  For example, this command prints some
 	important system files:</para>
 
       <screen>&prompt.user; <userinput>lpr /etc/host.conf /etc/hosts.equiv</userinput></screen>
 
       <para>To select a specific printer, type:</para>
 
       <screen>&prompt.user; <userinput>lpr -P <replaceable>printer-name</replaceable> <replaceable>filename</replaceable> <replaceable>...</replaceable></userinput></screen>
 
       <para>This example prints a long listing of the current directory to the
 	printer named <literal>rattan</literal>:</para>
 
       <screen>&prompt.user; <userinput>ls -l | lpr -P rattan</userinput></screen>
 
       <para>Because no files were listed for the
 	  &man.lpr.1; command, <command>lpr</command> read the data to print
 	from standard input, which was the output of the <command>ls
 	  -l</command> command.</para>
 
       <para>The &man.lpr.1; command can also accept a wide variety of options
 	to control formatting, apply file conversions, generate multiple
 	copies, and so forth. For more information, see the section <link
 	  linkend="printing-lpr-options">Printing Options</link>.</para>
     </sect2>
 
     <sect2 id="printing-lpq">
       <title>Checking Jobs</title>
 
       <indexterm><primary>print jobs</primary></indexterm>
       <para>When you print with &man.lpr.1;, the data you wish to print is put
 	together in a package called a <quote>print job</quote>, which is sent
 	to the <application>LPD</application> spooling system.  Each printer
 	has a queue of jobs, and
 	your job waits in that queue along with other jobs from yourself and
 	from other users.  The printer prints those jobs in a first-come,
 	first-served order.</para>
 
       <para>To display the queue for the default printer, type &man.lpq.1;.
 	For a specific printer, use the <option>-P</option> option.  For
 	example, the command
 
 	<screen>&prompt.user; <userinput>lpq -P bamboo</userinput></screen>
 
 	shows the queue for the printer named <literal>bamboo</literal>.  Here
 	is an example of the output of the <command>lpq</command>
 	command:</para>
 
       <screen>bamboo is ready and printing
 Rank   Owner    Job  Files                              Total Size
 active kelly    9    /etc/host.conf, /etc/hosts.equiv   88 bytes
 2nd    kelly    10   (standard input)                   1635 bytes
 3rd    mary     11   ...                                78519 bytes</screen>
 
       <para>This shows three jobs in the queue for <literal>bamboo</literal>.
 	The first job, submitted by user kelly, got assigned <quote>job
 	number</quote> 9.  Every job for a printer gets a unique job number.
 	Most of the time you can ignore the job number, but you will need it
 	if you want to cancel the job; see section <link
 	  linkend="printing-lprm">Removing Jobs</link> for details.</para>
 
       <para>Job number nine consists of two files; multiple files given on the
 	  &man.lpr.1; command line are treated as part of a single job.  It
 	is the currently active job (note the word <literal>active</literal>
 	under the <quote>Rank</quote> column), which means the printer should
 	be currently printing that job.  The second job consists of data
 	passed as the standard input to the &man.lpr.1; command.  The third
 	  job came from user <username>mary</username>; it is a much larger
 	  job. The pathname of the file she is trying to print is too long to
 	  fit, so the &man.lpq.1; command just shows three dots.</para>
 
       <para>The very first line of the output from &man.lpq.1; is also useful:
 	it tells what the printer is currently doing (or at least what
 	<application>LPD</application> thinks the printer is doing).</para>
 
       <para>The &man.lpq.1; command also support a <option>-l</option> option
 	to generate a detailed long listing.  Here is an example of
 	<command>lpq -l</command>:</para>
 
       <screen>waiting for bamboo to become ready (offline ?)
 kelly: 1st				 [job 009rose]
        /etc/host.conf                    73 bytes
        /etc/hosts.equiv                  15 bytes
 
 kelly: 2nd				 [job 010rose]
        (standard input)                  1635 bytes
 
 mary: 3rd                                [job 011rose]
       /home/orchid/mary/research/venus/alpha-regio/mapping 78519 bytes</screen>
     </sect2>
 
     <sect2 id="printing-lprm">
       <title>Removing Jobs</title>
 
       <para>If you change your mind about printing a job, you can remove the
 	job from the queue with the &man.lprm.1; command.  Often, you can
 	even use &man.lprm.1; to remove an active job, but some or all of the
 	job might still get printed.</para>
 
       <para>To remove a job from the default printer, first use
 	  &man.lpq.1; to find the job number.  Then type:</para>
 
       <screen>&prompt.user; <userinput>lprm <replaceable>job-number</replaceable></userinput></screen>
 
       <para>To remove the job from a specific printer, add the
 	<option>-P</option> option.  The following command removes job number
 	10 from the queue for the printer <literal>bamboo</literal>:</para>
 
       <screen>&prompt.user; <userinput>lprm -P bamboo 10</userinput></screen>
 
       <para>The &man.lprm.1; command has a few shortcuts:</para>
 
       <variablelist>
 	<varlistentry>
 	  <term>lprm -</term>
 
 	  <listitem>
 	    <para>Removes all jobs (for the default printer) belonging to
 	      you.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>lprm <replaceable>user</replaceable></term>
 
 	  <listitem>
 	    <para>Removes all jobs (for the default printer) belonging to
 	      <replaceable>user</replaceable>.  The superuser can remove other
 	      users' jobs; you can remove only your own jobs.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term>lprm</term>
 
 	  <listitem>
 	    <para>With no job number, user name, or <option>-</option>
 	      appearing on the command line,
 		    &man.lprm.1; removes the currently active job on the
 	      default printer, if it belongs to you.  The superuser can remove
 	      any active job.</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
 
       <para>Just use the <option>-P</option> option with the above shortcuts
 	to operate on a specific printer instead of the default. For example,
 	the following command removes all jobs for the current user in the
 	queue for the printer named <literal>rattan</literal>:</para>
 
       <screen>&prompt.user; <userinput>lprm -P rattan -</userinput></screen>
 
       <note>
 	<para>If you are working in a networked environment, &man.lprm.1; will
 	  let you remove jobs only from the
 	  host from which the jobs were submitted, even if the same printer is
 	  available from other hosts. The following command sequence
 	  demonstrates this:</para>
 
 	<screen>&prompt.user; <userinput>lpr -P rattan myfile</userinput>
 &prompt.user; <userinput>rlogin orchid</userinput>
 &prompt.user; <userinput>lpq -P rattan</userinput>
 Rank   Owner	  Job  Files                          Total Size
 active seeyan	  12	...                           49123 bytes
 2nd    kelly      13   myfile                         12 bytes
 &prompt.user; <userinput>lprm -P rattan 13</userinput>
 rose: Permission denied
 &prompt.user; <userinput>logout</userinput>
 &prompt.user; <userinput>lprm -P rattan 13</userinput>
 dfA013rose dequeued
 cfA013rose dequeued
 	</screen>
       </note>
     </sect2>
 
     <sect2 id="printing-lpr-options">
       <title>Beyond Plain Text: Printing Options</title>
 
       <para>The &man.lpr.1; command supports a number of options that control
 	formatting text, converting graphic and other file formats, producing
 	multiple copies, handling of the job, and more.  This section
 	describes the options.</para>
 
       <sect3 id="printing-lpr-options-format">
 	<title>Formatting and Conversion Options</title>
 
 	<para>The following &man.lpr.1; options control formatting of the
 	  files in the job.  Use these options if the job does not contain
 	  plain text or if you want plain text formatted through the
 	    &man.pr.1; utility.</para>
 
         <indexterm><primary>&tex;</primary></indexterm>
 	<para>For example, the following command prints a DVI file (from the
 	  &tex; typesetting system) named <filename>fish-report.dvi</filename>
 	  to the printer named <literal>bamboo</literal>:</para>
 
 	<screen>&prompt.user; <userinput>lpr -P bamboo -d fish-report.dvi</userinput></screen>
 
 	<para>These options apply to every file in the job, so you cannot mix
 	  (say) DVI and ditroff files together in a job. Instead, submit the
 	  files as separate jobs, using a different conversion option for each
 	  job.</para>
 
 	<note>
 	  <para>All of these options except <option>-p</option> and
 	    <option>-T</option> require conversion filters installed for the
 	    destination printer.  For example, the <option>-d</option> option
 	    requires the DVI conversion filter.  Section <link
 	      linkend="printing-advanced-convfilters">Conversion
 	      Filters</link> gives details.</para>
 	</note>
 
 	<variablelist>
 	  <varlistentry>
 	    <term><option>-c</option></term>
 
 	    <listitem>
 	      <para>Print cifplot files.</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term><option>-d</option></term>
 
 	    <listitem>
 	      <para>Print DVI files.</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term><option>-f</option></term>
 
 	    <listitem>
 	      <para>Print FORTRAN text files.</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term><option>-g</option></term>
 
 	    <listitem>
 	      <para>Print plot data.</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term><option>-i <replaceable>number</replaceable></option></term>
 
 	    <listitem>
 	      <para>Indent the output by <replaceable>number</replaceable>
 		columns; if you omit <replaceable>number</replaceable>, indent
 		by 8 columns.  This option works only with certain conversion
 		filters.</para>
 
 	      <note>
 		<para>Do not put any space between the <option>-i</option> and
 		  the number.</para>
 	      </note>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term><option>-l</option></term>
 
 	    <listitem>
 	      <para>Print literal text data, including control
 		characters.</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term><option>-n</option></term>
 
 	    <listitem>
 	      <para>Print ditroff (device independent troff) data.</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term>-p</term>
 
 	    <listitem>
 	      <para>Format plain text with &man.pr.1; before printing.  See
 		  &man.pr.1; for more information.</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term><option>-T <replaceable>title</replaceable></option></term>
 
 	    <listitem>
 	      <para>Use <replaceable>title</replaceable> on the
 		  &man.pr.1; header instead of the file name.  This option has
 		effect only when used with the <option>-p</option>
 		option.</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term><option>-t</option></term>
 
 	    <listitem>
 	      <para>Print troff data.</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term><option>-v</option></term>
 
 	    <listitem>
 	      <para>Print raster data.</para>
 	    </listitem>
 	  </varlistentry>
 	</variablelist>
 
 	<para>Here is an example: this command prints a nicely formatted
 	  version of the &man.ls.1; manual page on the default printer:</para>
 
 	<screen>&prompt.user; <userinput>zcat /usr/share/man/man1/ls.1.gz | troff -t -man | lpr -t</userinput></screen>
 
 	<para>The &man.zcat.1; command uncompresses the source of the
 	  &man.ls.1; manual page and passes it to the &man.troff.1;
 	  command, which formats that source and makes GNU troff
 	  output and passes it to &man.lpr.1;, which submits the job
 	  to the <application>LPD</application> spooler.  Because we
 	  used the <option>-t</option>
 	  option to &man.lpr.1;, the spooler will convert the GNU
 	  troff output into a format the default printer can
 	  understand when it prints the job.</para>
       </sect3>
 
       <sect3 id="printing-lpr-options-job-handling">
 	<title>Job Handling Options</title>
 
 	<para>The following options to &man.lpr.1; tell
 	  <application>LPD</application> to handle the job
 	  specially:</para>
 
 	<variablelist>
 	  <varlistentry>
 	    <term>-# <replaceable>copies</replaceable></term>
 
 	    <listitem>
 	      <para>Produce a number of <replaceable>copies</replaceable> of
 		each file in the job instead of just one copy.  An
 		administrator may disable this option to reduce printer
 		wear-and-tear and encourage photocopier usage.  See section
 		<link
 		  linkend="printing-advanced-restricting-copies">Restricting
 		  Multiple Copies</link>.</para>
 
 	      <para>This example prints three copies of
 		<filename>parser.c</filename> followed by three copies of
 		<filename>parser.h</filename> to the default printer:</para>
 
 	      <screen>&prompt.user; <userinput>lpr -#3 parser.c parser.h</userinput></screen>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term>-m</term>
 
 	    <listitem>
 	      <para>Send mail after completing the print job.  With this
 		option, the <application>LPD</application> system will send
 		mail to your account when it
 		finishes handling your job.  In its message, it will tell you
 		if the job completed successfully or if there was an error,
 		and (often) what the error was.</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term>-s</term>
 
 	    <listitem>
 	      <para>Do not copy the files to the spooling directory, but make
 		symbolic links to them instead.</para>
 
 	      <para>If you are printing a large job, you probably want to use
 		this option.  It saves space in the spooling directory (your
 		job might overflow the free space on the filesystem where the
 		spooling directory resides).  It saves time as well since
 		<application>LPD</application>
 		will not have to copy each and every byte of your job to the
 		spooling directory.</para>
 
 	      <para>There is a drawback, though: since
 		<application>LPD</application> will refer to the
 		original files directly, you cannot modify or remove them
 		until they have been printed.</para>
 
 	      <note>
 		<para>If you are printing to a remote printer,
 		  <application>LPD</application> will
 		  eventually have to copy files from the local host to the
 		  remote host, so the <option>-s</option> option will save
 		  space only on the local spooling directory, not the remote.
 		  It is still useful, though.</para>
 	      </note>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term>-r</term>
 
 	    <listitem>
 	      <para>Remove the files in the job after copying them to the
 		spooling directory, or after printing them with the
 		<option>-s</option> option.  Be careful with this
 		option!</para>
 	    </listitem>
 	  </varlistentry>
 	</variablelist>
       </sect3>
 
       <sect3 id="printing-lpr-options-misc">
 	<title>Header Page Options</title>
 
 	<para>These options to &man.lpr.1; adjust the text that normally
 	  appears on a job's header page. If header pages are suppressed for
 	  the destination printer, these options have no effect.  See section
 	  <link linkend="printing-advanced-header-pages">Header Pages</link>
 	  for information about setting up header pages.</para>
 
 	<variablelist>
 	  <varlistentry>
 	    <term>-C <replaceable>text</replaceable></term>
 
 	    <listitem>
 	      <para>Replace the hostname on the header page with
 		<replaceable>text</replaceable>.  The hostname is normally the
 		name of the host from which the job was submitted.</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term>-J <replaceable>text</replaceable></term>
 
 	    <listitem>
 	      <para>Replace the job name on the header page with
 		<replaceable>text</replaceable>.  The job name is normally the
 		name of the first file of the job, or
 		<filename>stdin</filename> if you are printing standard
 		input.</para>
 	    </listitem>
 	  </varlistentry>
 
 	  <varlistentry>
 	    <term>-h</term>
 
 	    <listitem>
 	      <para>Do not print any header page.</para>
 
 	      <note>
 		<para>At some sites, this option may have no effect due to the
 		  way header pages are generated.  See <link
 		    linkend="printing-advanced-header-pages">Header
 		    Pages</link> for details.</para>
 	      </note>
 	    </listitem>
 	  </varlistentry>
 	</variablelist>
       </sect3>
     </sect2>
 
     <sect2 id="printing-lpc">
       <title>Administering Printers</title>
 
       <para>As an administrator for your printers, you have had to install,
 	set up, and test them.  Using the &man.lpc.8; command, you
 	can interact with your printers in yet more ways. With &man.lpc.8;,
 	you can</para>
 
       <itemizedlist>
 	<listitem>
 	  <para>Start and stop the printers</para>
 	</listitem>
 
 	<listitem>
 	  <para>Enable and disable their queues</para>
 	</listitem>
 
 	<listitem>
 	  <para>Rearrange the order of the jobs in each queue.</para>
 	</listitem>
       </itemizedlist>
 
       <para>First, a note about terminology: if a printer is
 	<emphasis>stopped</emphasis>, it will not print anything in its queue.
 	Users can still submit jobs, which will wait in the queue until the
 	printer is <emphasis>started</emphasis> or the queue is
 	cleared.</para>
 
       <para>If a queue is <emphasis>disabled</emphasis>, no user (except
 	<username>root</username>) can submit jobs for the printer.  An
 	<emphasis>enabled</emphasis> queue allows jobs to be submitted.  A
 	printer can be <emphasis>started</emphasis> for a disabled queue, in
 	which case it will continue to print jobs in the queue until the queue
 	is empty.</para>
 
       <para>In general, you have to have <username>root</username> privileges
 	to use the &man.lpc.8; command.  Ordinary users can use the &man.lpc.8;
 	command to get printer status and to restart a hung printer only.</para>
 
       <para>Here is a summary of the &man.lpc.8; commands.  Most of the
 	commands take a <replaceable>printer-name</replaceable> argument to
 	tell on which printer to operate.  You can use <literal>all</literal>
 	for the <replaceable>printer-name</replaceable> to mean all printers
 	listed in <filename>/etc/printcap</filename>.</para>
 
       <variablelist>
 	<varlistentry>
 	  <term><command>abort
 	      <replaceable>printer-name</replaceable></command></term>
 
 	  <listitem>
 	    <para>Cancel the current job and stop the printer.  Users can
 	      still submit jobs if the queue is enabled.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><command>clean
 	      <replaceable>printer-name</replaceable></command></term>
 
 	  <listitem>
 	    <para>Remove old files from the printer's spooling directory.
 	      Occasionally, the files that make up a job are not properly
 	      removed by <application>LPD</application>, particularly if
 	      there have been errors during
 	      printing or a lot of administrative activity.  This command
 	      finds files that do not belong in the spooling directory and
 	      removes them.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><command>disable
 	      <replaceable>printer-name</replaceable></command></term>
 
 	  <listitem>
 	    <para>Disable queuing of new jobs.  If the printer is running, it
 	      will continue to print any jobs remaining in the queue.  The
 	      superuser (<username>root</username>) can always submit jobs,
 	      even to a disabled queue.</para>
 
 	    <para>This command is useful while you are testing a new printer
 	      or filter installation: disable the queue and submit jobs as
 	      <username>root</username>.  Other users will not be able to submit
 	      jobs until you complete your testing and re-enable the queue with
 	      the <command>enable</command> command.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><command>down <replaceable>printer-name</replaceable>
 	      <replaceable>message</replaceable></command></term>
 
 	  <listitem>
 	    <para>Take a printer down.  Equivalent to
 	      <command>disable</command> followed by <command>stop</command>.
 	      The <replaceable>message</replaceable> appears as the printer's
 	      status whenever a user checks the printer's queue with
 		    &man.lpq.1; or status with <command>lpc
 		status</command>.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><command>enable
 	      <replaceable>printer-name</replaceable></command></term>
 
 	  <listitem>
 	    <para>Enable the queue for a printer.  Users can submit jobs but
 	      the printer will not print anything until it is started.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><command>help
 	      <replaceable>command-name</replaceable></command></term>
 
 	  <listitem>
 	    <para>Print help on the command
 	      <replaceable>command-name</replaceable>.  With no
 	      <replaceable>command-name</replaceable>, print a summary of the
 	      commands available.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><command>restart
 	      <replaceable>printer-name</replaceable></command></term>
 
 	  <listitem>
 	    <para>Start the printer.  Ordinary users can use this command if
 	      some extraordinary circumstance hangs
 	      <application>LPD</application>, but they cannot start
 	      a printer stopped with either the <command>stop</command> or
 	      <command>down</command> commands.  The
 	      <command>restart</command> command is equivalent to
 	      <command>abort</command> followed by
 	      <command>start</command>.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><command>start
 	      <replaceable>printer-name</replaceable></command></term>
 
 	  <listitem>
 	    <para>Start the printer.  The printer will print jobs in its
 	      queue.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><command>stop
 	      <replaceable>printer-name</replaceable></command></term>
 
 	  <listitem>
 	    <para>Stop the printer.  The printer will finish the current job
 	      and will not print anything else in its queue.  Even though the
 	      printer is stopped, users can still submit jobs to an enabled
 	      queue.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><command>topq <replaceable>printer-name</replaceable>
 	      <replaceable>job-or-username</replaceable></command></term>
 
 	  <listitem>
 	    <para>Rearrange the queue for
 	      <replaceable>printer-name</replaceable> by placing the jobs with
 	      the listed <replaceable>job</replaceable> numbers or the jobs
 	      belonging to <replaceable>username</replaceable> at the top of
 	      the queue. For this command, you cannot use
 	      <literal>all</literal> as the
 	      <replaceable>printer-name</replaceable>.</para>
 	  </listitem>
 	</varlistentry>
 
 	<varlistentry>
 	  <term><command>up
 	      <replaceable>printer-name</replaceable></command></term>
 
 	  <listitem>
 	    <para>Bring a printer up; the opposite of the
 	      <command>down</command> command.  Equivalent to
 	      <command>start</command> followed by
 	      <command>enable</command>.</para>
 	  </listitem>
 	</varlistentry>
       </variablelist>
 
       <para>&man.lpc.8; accepts the above commands on the command line.  If
 	you do not enter any commands, &man.lpc.8; enters an interactive mode,
 	where you can enter commands until you type <command>exit</command>,
 	<command>quit</command>, or end-of-file.</para>
     </sect2>
   </sect1>
 
   <sect1 id="printing-lpd-alternatives">
     <title>Alternatives to the Standard Spooler</title>
 
     <para>If you have been reading straight through this manual, by now you
       have learned just about everything there is to know about the
       <application>LPD</application>
       spooling system that comes with FreeBSD.  You can probably appreciate
       many of its shortcomings, which naturally leads to the question:
       <quote>What other spooling systems are out there (and work with
       FreeBSD)?</quote></para>
 
     <variablelist>
       <varlistentry>
 	<term>LPRng</term>
 
 	<listitem>
 	  <indexterm><primary>LPRng</primary></indexterm>
 
 	  <para><application>LPRng</application>, which purportedly means
 	    <quote>LPR: the Next
 	    Generation</quote> is a complete rewrite of PLP.  Patrick Powell
 	    and Justin Mason (the principal maintainer of PLP) collaborated to
 	    make <application>LPRng</application>.  The main site for
 	    <application>LPRng</application> is <ulink
 	      url="http://www.lprng.org/"></ulink>.</para>
 	</listitem>
       </varlistentry>
       <varlistentry>
 	<term>CUPS</term>
 
 	<listitem>
 	  <indexterm><primary>CUPS</primary></indexterm>
 
 	  <para><application>CUPS</application>, the Common UNIX Printing
 	    System, provides a portable printing layer for &unix;-based
 	    operating systems.  It has been developed by Easy Software
 	    Products to promote a standard printing solution for all &unix;
 	    vendors and users.</para>
 
 	  <para><application>CUPS</application> uses the Internet Printing
 	    Protocol (<acronym>IPP</acronym>) as the basis for managing
 	    print jobs and queues.  The Line Printer Daemon
 	    (<acronym>LPD</acronym>), Server Message Block
 	    (<acronym>SMB</acronym>), and AppSocket (a.k.a. JetDirect)
 	    protocols are also supported with reduced functionality.  CUPS
 	    adds network printer browsing and PostScript Printer Description
 	    (<acronym>PPD</acronym>) based printing options to support
 	    real-world printing under &unix;.</para>
 
 	  <para>The main site for <application>CUPS</application> is <ulink
 	    url="http://www.cups.org/"></ulink>.</para>
 	</listitem>
       </varlistentry>
     </variablelist>
   </sect1>
 
   <sect1 id="printing-troubleshooting">
     <title>Troubleshooting</title>
 
     <para>After performing the simple test with &man.lptest.1;, you might
       have gotten one of the following results instead of the correct
       printout:</para>
 
     <variablelist>
       <varlistentry>
 	<term>It worked, after awhile; or, it did not eject a full
 	  sheet.</term>
 
 	<listitem>
 	  <para>The printer printed the above, but it sat for awhile and
 	    did nothing.  In fact, you might have needed to press a
 	    PRINT REMAINING or FORM FEED button on the printer to get any
 	    results to appear.</para>
 
 	  <para>If this is the case, the printer was probably waiting to
 	    see if there was any more data for your job before it printed
 	    anything.  To fix this problem, you can have the text filter
 	    send a FORM FEED character (or whatever is necessary) to the
 	    printer.  This is usually sufficient to have the printer
 	    immediately print any text remaining in its internal buffer.
 	    It is also useful to make sure each print job ends on a full
 	    sheet, so the next job does not start somewhere on the middle
 	    of the last page of the previous job.</para>
 
 	  <para>The following replacement for the shell script
 	    <filename>/usr/local/libexec/if-simple</filename> prints a
 	    form feed after it sends the job to the printer:</para>
 
 	  <programlisting>#!/bin/sh
 #
 # if-simple - Simple text input filter for lpd
 # Installed in /usr/local/libexec/if-simple
 #
 # Simply copies stdin to stdout.  Ignores all filter arguments.
 # Writes a form feed character (\f) after printing job.
 
 /bin/cat &amp;&amp; printf "\f" &amp;&amp; exit 0
 exit 2</programlisting>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>It produced the <quote>staircase effect.</quote></term>
 
 	<listitem>
 	  <para>You got the following on paper:</para>
 
 	  <programlisting>!"#$%&amp;'()*+,-./01234
                 "#$%&amp;'()*+,-./012345
                                  #$%&amp;'()*+,-./0123456</programlisting>
 
 	  <indexterm><primary>MS-DOS</primary></indexterm>
  	  <indexterm><primary>OS/2</primary></indexterm>
  	  <indexterm><primary>ASCII</primary></indexterm>
 	  <para>You have become another victim of the <emphasis>staircase
 	    effect</emphasis>, caused by conflicting interpretations of
 	    what characters should indicate a new line.  &unix; style
 	    operating systems use a single character:  ASCII code 10, the
 	    line feed (LF). &ms-dos;, &os2;, and others uses a pair of
 	    characters, ASCII code 10 <emphasis>and</emphasis> ASCII code
 	    13 (the carriage return or CR).  Many printers use the &ms-dos;
 	    convention for representing new-lines.</para>
 
 	  <para>When you print with FreeBSD, your text used just the line
 	    feed character.  The printer, upon seeing a line feed
 	    character, advanced the paper one line, but maintained the
 	    same horizontal position on the page for the next character
 	    to print.  That is what the carriage return is for:  to move
 	    the location of the next character to print to the left edge
 	    of the paper.</para>
 
 	  <para>Here is what FreeBSD wants your printer to do:</para>
 
 	  <informaltable frame="none" pgwide="1">
 	    <tgroup cols="2">
 	      <tbody>
 		<row>
 		  <entry>Printer received CR</entry>
 		  <entry>Printer prints CR</entry>
 		</row>
 
 		<row>
 		  <entry>Printer received LF</entry>
 		  <entry>Printer prints CR + LF</entry>
 		</row>
 	      </tbody>
 	    </tgroup>
 	  </informaltable>
 
 	  <para>Here are some ways to achieve this:</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>Use the printer's configuration switches or control
 		panel to alter its interpretation of these characters.
 		Check your printer's manual to find out how to do
 		this.</para>
 
 	      <note>
 	        <para>If you boot your system into other operating systems
 		  besides FreeBSD, you may have to
 		  <emphasis>reconfigure</emphasis> the printer to use a an
 		  interpretation for CR and LF characters that those other
 		  operating systems use.  You might prefer one of the other
 		  solutions, below.</para>
 	      </note>
 	    </listitem>
 
 	    <listitem>
 	      <para>Have FreeBSD's serial line driver automatically
 		convert LF to CR+LF.  Of course, this works with printers
 		on serial ports <emphasis>only</emphasis>.  To enable this
 		feature, use the <literal>ms#</literal> capability and
 		set the <literal>onlcr</literal> mode
 		in the <filename>/etc/printcap</filename> file
 		for the printer.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>Send an <emphasis>escape code</emphasis> to the
 	        printer to have it temporarily treat LF characters
 		differently.  Consult your printer's manual for escape
 		codes that your printer might support.  When you find the
 		proper escape code, modify the text filter to send the
 		code first, then send the print job.</para>
 
 	      <indexterm><primary>PCL</primary></indexterm>
 	      <para>Here is an example text filter for printers that
 		understand the Hewlett-Packard PCL escape codes.  This
 		filter makes the printer treat LF characters as a LF and
 		CR; then it sends the job; then it sends a form feed to
 		eject the last page of the job.  It should work with
 		nearly all Hewlett Packard printers.</para>
 
 	      <programlisting>#!/bin/sh
 #
 # hpif - Simple text input filter for lpd for HP-PCL based printers
 # Installed in /usr/local/libexec/hpif
 #
 # Simply copies stdin to stdout.  Ignores all filter arguments.
 # Tells printer to treat LF as CR+LF.  Ejects the page when done.
 
 printf "\033&amp;k2G" &amp;&amp; cat &amp;&amp; printf "\033&amp;l0H" &amp;&amp; exit 0
 exit 2</programlisting>
 
 	      <para>Here is an example <filename>/etc/printcap</filename>
 		from a host called <hostid>orchid</hostid>.  It has a single printer
 		attached to its first parallel port, a Hewlett Packard
 		LaserJet 3Si named <literal>teak</literal>.  It is using the
 		above script as its text filter:</para>
 
 	      <programlisting>#
 #  /etc/printcap for host orchid
 #
 teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\
         :lp=/dev/lpt0:sh:sd=/var/spool/lpd/teak:mx#0:\
         :if=/usr/local/libexec/hpif:</programlisting>
 	    </listitem>
           </itemizedlist>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>It overprinted each line.</term>
 
 	<listitem>
 	  <para>The printer never advanced a line.  All of the lines of
 	    text were printed on top of each other on one line.</para>
 
 	  <para>This problem is the <quote>opposite</quote> of the
 	    staircase effect, described above, and is much rarer.
 	    Somewhere, the LF characters that FreeBSD uses to end a line
 	    are being treated as CR characters to return the print
 	    location to the left edge of the paper, but not also down a
 	    line.</para>
 
 	  <para>Use the printer's configuration switches or control panel
 	    to enforce the following interpretation of LF and CR
 	    characters:</para>
 
 	  <informaltable frame="none" pgwide="1">
 	    <tgroup cols="2">
 	      <thead>
 		<row>
 		  <entry>Printer receives</entry>
 		  <entry>Printer prints</entry>
 		</row>
 	      </thead>
 
 	      <tbody>
 		<row>
 		  <entry>CR</entry>
 		  <entry>CR</entry>
 		</row>
 
 		<row>
 		  <entry>LF</entry>
 		  <entry>CR + LF</entry>
 		</row>
 	      </tbody>
 	    </tgroup>
 	  </informaltable>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>The printer lost characters.</term>
 
 	<listitem>
 	  <para>While printing, the printer did not print a few characters
 	    in each line.  The problem might have gotten worse as the
 	    printer ran, losing more and more characters.</para>
 
 	  <para>The problem is that the printer cannot keep up with the
 	    speed at which the computer sends data over a serial line
 	    (this problem should not occur with printers on parallel
 	    ports).  There are two ways to overcome the problem:</para>
 
 	  <itemizedlist>
 	    <listitem>
 	      <para>If the printer supports XON/XOFF flow control, have
 		FreeBSD use it by specifying the <literal>ixon</literal> mode
 		in the <literal>ms#</literal> capability.</para>
 	    </listitem>
 
 	    <listitem>
 	      <para>If the printer supports carrier flow control, specify
 		the <literal>crtscts</literal> mode in the
 		<literal>ms#</literal> capability.
 		Make sure the cable connecting the printer to the computer
 		is correctly wired for carrier flow control.</para>
 	    </listitem>
 	  </itemizedlist>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>It printed garbage.</term>
 
 	<listitem>
 	  <para>The printer printed what appeared to be random garbage,
 	    but not the desired text.</para>
 
 	  <para>This is usually another symptom of incorrect
 	    communications parameters with a serial printer.  Double-check
 	    the bps rate in the <literal>br</literal> capability, and the
 	    parity setting in the
 	    <literal>ms#</literal> capability; make sure the printer is
 	    using the same settings as specified in the
 	    <filename>/etc/printcap</filename> file.</para>
 	</listitem>
       </varlistentry>
 
       <varlistentry>
 	<term>Nothing happened.</term>
 
 	<listitem>
 	  <para>If nothing happened, the problem is probably within
 	    FreeBSD and not the hardware.  Add the log file
 	    (<literal>lf</literal>) capability to the entry for the
 	    printer you are debugging in the
 	    <filename>/etc/printcap</filename> file.  For example, here is
 	    the entry for <literal>rattan</literal>, with the
 	    <literal>lf</literal> capability:</para>
 
 	  <programlisting>rattan|line|diablo|lp|Diablo 630 Line Printer:\
         :sh:sd=/var/spool/lpd/rattan:\
         :lp=/dev/lpt0:\
         :if=/usr/local/libexec/if-simple:\
         :lf=/var/log/rattan.log</programlisting>
 
 	  <para>Then, try printing again.  Check the log file (in our
 	    example, <filename>/var/log/rattan.log</filename>) to see any
 	    error messages that might appear.  Based on the messages you
 	    see, try to correct the problem.</para>
 
 	  <para>If you do not specify a <literal>lf</literal> capability,
 	    <application>LPD</application> uses
 	    <filename>/dev/console</filename> as a default.</para>
 	</listitem>
       </varlistentry>
     </variablelist>
   </sect1>
 </chapter>