path: root/el_GR.ISO8859-7/books/faq/book.sgml

<!--

  Óõ÷íÝò ÅñùôÞóåéò ãéá ôï FreeBSD

  The FreeBSD Greek Documentation Project

  %SOURCE%      en_US.ISO8859-1/books/faq/book.sgml
  %SRCID%       1.807

-->

<!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
<!ENTITY % books.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Books Entity Set//EL">
%books.ent;
<!ENTITY bibliography SYSTEM "../../../share/sgml/bibliography.sgml">
]>

<book>
  <bookinfo>
    <title>Óõ÷íÝò ÅñùôÞóåéò ãéá ôï &os; 5.X êáé 6.X</title>

    <corpauthor>Ç ÏìÜäá Ôåêìçñßùóçò ôïõ &os;</corpauthor>

    <pubdate>$FreeBSD$</pubdate>

    <copyright>
      <year>1995</year>
      <year>1996</year>
      <year>1997</year>
      <year>1998</year>
      <year>1999</year>
      <year>2000</year>
      <year>2001</year>
      <year>2002</year>
      <year>2003</year>
      <year>2004</year>
      <year>2005</year>
      <year>2006</year>
      <year>2007</year>
      <holder>Ç ÏìÜäá Ôåêìçñßùóçò ôïõ &os;</holder>
    </copyright>

    &bookinfo.legalnotice;

    <legalnotice id="trademarks" role="trademarks">
      &tm-attrib.freebsd;
      &tm-attrib.3com;
      &tm-attrib.adobe;
      &tm-attrib.creative;
      &tm-attrib.cvsup;
      &tm-attrib.ibm;
      &tm-attrib.ieee;
      &tm-attrib.intel;
      &tm-attrib.iomega;
      &tm-attrib.linux;
      &tm-attrib.microsoft;
      &tm-attrib.mips;
      &tm-attrib.netscape;
      &tm-attrib.opengroup;
      &tm-attrib.oracle;
      &tm-attrib.sgi;
      &tm-attrib.sparc;
      &tm-attrib.sun;
      &tm-attrib.usrobotics;
      &tm-attrib.xfree86;
      &tm-attrib.general;
    </legalnotice>

    <abstract>
      <para>Ôï êåßìåíï áõôü áðïôåëåß ôéò Óõ÷íÝò ÅñùôÞóåéò (FAQ) ãéá ôéò
        åêäüóåéò 5.× êáé 6.× ôïõ &os;. ¼ëåò ïé êáôá÷ùñÞóåéò èåùñåßôáé üôé
        ó÷åôßæïíôáé ìå ôçí Ýêäïóç &os; 5.X êáé ìåôáãåíÝóôåñåò, åêôüò
        áí áíáöÝñåôáé äéáöïñåôéêÜ. Áí åíäéáöÝñåóôå íá ìáò âïçèÞóåôå óå áõôü
        ôï Ýñãï, óôåßëôå Ýíá email óôçí &a.doc;. Ç ôåëåõôáßá Ýêäïóç áõôïý
        ôïõ êåéìÝíïõ åßíáé ðÜíôïôå äéáèÝóéìç óôçí
        <ulink
        url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/index.html">äéêôõáêÞ ôïðïèåóßá ôïõ &os;</ulink>. Ìðïñåßôå åðßóçò íá ôçí êáôåâÜóåôå ùò
        Ýíá ìåãÜëï <ulink url="book.html">HTML</ulink> áñ÷åßï ìÝóù HTTP Þ
        áêüìá êáé ùò áðëü êåßìåíï, &postscript;, PDF, êëð. áðü ôïí <ulink
        url="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">åîõðçñåôçôÞ FTP ôïõ
        &os;</ulink>. Ìðïñåßôå áêüìá íá <ulink
        url="&url.base;/search/index.html">øÜîåôå óôéò Óõ÷íÝò ÅñùôÞóåéò
        </ulink>.</para>
    </abstract>
  </bookinfo>

  <chapter id="introduction">
    <title>ÅéóáãùãÞ</title>

    <para>Êáëþò Þëèáôå óôéò Óõ÷íÝò ÅñùôÞóåéò (FAQ) ôïõ &os; 5.X-6.X!</para>

    <para>¼ðùò óõíçèßæåôáé óôá FAQs ôïõ Usenet, ôï êåßìåíï áõôü Ý÷åé óêïðü
      íá êáëýøåé ôéò ðéï óõíçèéóìÝíåò åñùôÞóåéò ðïõ áöïñïýí ôï ëåéôïõñãéêü
      óýóôçìá &os; (êáé öõóéêÜ íá ôéò áðáíôÞóåé!). Áí êáé ï áñ÷éêüò óêïðüò
      ôùí FAQs Þôáí ç åîïéêïíüìçóç åýñïõò æþíçò ôïõ äéáäéêôýïõ áðü ôçí
      åðáíáëáìâáíüìåíç áðÜíôçóç ôùí ßäéùí åñùôÞóåùí, ôá FAQs áíáãíùñßóôçêáí
      ôåëéêÜ ùò ðïëýôéìåò ðçãÝò ðëçñïöïñéþí.</para>

    <para>¸÷åé êáôáâëçèåß êÜèå ðñïóðÜèåéá þóôå áõôü ôï FAQ íá ãßíåé üóï ðéï
      ðëçñïöïñéáêü ãßíåôáé. Áí èÝëåôå íá êÜíåôå êÜðïéåò õðïäåßîåéò ó÷åôéêÜ
      ìå ôñüðïõò âåëôßùóçò ôïõ, óáò ðáñáêáëïýìå óôåßëôå ìáò Ýíá email óôç
      &a.doc;.</para>

    <qandaset>
      <qandaentry>
        <question id="what-is-FreeBSD">
          <para>Ôé åßíáé ôï &os;;</para>
        </question>

        <answer>
         <para>Åí óõíôïìßá, ôï &os; åßíáé Ýíá ëåéôïõñãéêü óýóôçìá ôýðïõ
           &unix;&nbsp;ãéá ôéò áñ÷éôåêôïíéêÝò Alpha/AXP, AMD64 êáé &intel;
           EM64T, &i386; IA-64, PC-98, êáé &ultrasparc; êáé âáóßæåôáé óôçí
           Ýêäïóç <quote>4.4BSD-Lite</quote> ôïõ Ðáíåðéóôçìßïõ ôïõ Berkeley,
           ìå êÜðïéåò âåëôéþóåéò áðü ôï <quote>4.4BSD-Lite2</quote>. Âáóßæåôáé
           åðßóçò Ýììåóá óôçí åñãáóßá ìåôáöïñÜò (port) ôïõ
           <quote>Net/2</quote> (åðßóçò áðü ôï Berkeley) ðïõ Ýãéíå áðü ôïí
           William Jolitz, áí êáé äåí Ý÷åé ìåßíåé ó÷åäüí ôßðïôá áðü ôïí áñ÷éêü
           êþäéêá ôïõ 386BSD. ÐëçñÝóôåñç ðåñéãñáöÞ ãéá ôï ôé åßíáé ôï &os; êáé
           ðùò ìðïñåß íá ëåéôïõñãÞóåé ãéá åóÜò, ìðïñåßôå íá âñåßôå óôçí
           <ulink url="&url.base;/index.html">äéêôõáêÞ ôïðïèåóßá ôïõ &os;
           </ulink>.</para>

         <para>Ôï &os; ÷ñçóéìïðïéåßôáé áðü åôáéñßåò, ðáñï÷åßò õðçñåóéþí
           Internet (ISPs), öïéôçôÝò êáé ïéêéáêïýò ÷ñÞóôåò, åñåõíçôÝò,
           êáé åðáããåëìáôßåò ôùí õðïëïãéóôþí óå üëï ôïí êüóìï, óôç äïõëåéÜ
           ôïõò, óôçí åêðáßäåõóç êáé ãéá áíáøõ÷Þ.</para>

         <para>Ãéá ðåñéóóüôåñåò ëåðôïìÝñåéåò ó÷åôéêÜ ìå ôï &os;, ðáñáêáëïýìå
           äéáâÜóôå ôï
           <ulink url="&url.books.handbook;/index.html">Åã÷åéñßäéï ôïõ &os;
           </ulink>.</para>
       </answer>
      </qandaentry>

      <qandaentry>
        <question id="FreeBSD-goals">
          <para>Ðïéïò åßíáé ï óêïðüò ôïõ &os; Project;</para>
        </question>

        <answer>
          <para>Ï óêïðüò ôïõ &os; Project åßíáé íá ðáñÝ÷åé ëïãéóìéêü ôï ïðïßï
            íá ìðïñåß íá ÷ñçóéìïðïéçèåß ãéá ïðïéïõóäÞðïôå óêïðïýò êáé ÷ùñßò
            ðåñéïñéóìïýò. Ðïëëïß áðü åìÜò Ý÷ïõìå åðåíäýóåé óçìáíôéêÜ óôïí
            êþäéêá (êáé óôï ßäéï ôï Ýñãï) êáé óßãïõñá äåí èá ìáò ðåßñáæå
            êáé êÜðïéá ÷ñçìáôéêÞ áðïæçìßùóç ðïõ êáé ðïõ, áëëÜ óßãïõñá äåí
            åðéìÝíïõìå óå áõôü. Ðéóôåýïõìå üôé ç ðñþôç êáé âáóéêüôåñç
            <quote>áðïóôïëÞ</quote> ìáò åßíáé íá ðáñÝ÷ïõìå êþäéêá óå üëïõò,
            ãéá ïðïéïäÞðïôå ðéèáíü óêïðü, Ýôóé þóôå ï êþäéêáò ìáò íá Ý÷åé
            ôçí åõñýôåñç äõíáôÞ ÷ñÞóç êáé åðéôõã÷Üíåé ôï ìåãáëýôåñï äõíáôü
            üöåëïò. Ðéóôåýïõìå üôé áõôüò åßíáé Ýíáò áðü ôïõò óçìáíôéêüôåñïõò
            óêïðïýò ôïõ Åëåýèåñïõ Ëïãéóìéêïý êáé ôïí õðïóôçñßæïõìå èåñìÜ.
          </para>

          <para>Ï êþäéêáò, óôï äÝíôñï ôïõ ðçãáßïõ ìáò êþäéêá, ï ïðïßïò
            åìðßðôåé óôç Üäåéá ÷ñÞóçò
            <ulink url="http://www.FreeBSD.org/copyright/COPYING">GNU
            General Public License (GPL)</ulink> Þ <ulink
            url="http://www.FreeBSD.org/copyright/COPYING.LIB">GNU
            Library General Public License (LGPL)</ulink> Ý÷åé ðåñéóóüôåñïõò
            ðåñéïñéóìïýò, áëëÜ ôïõëÜ÷éóôïí üóï áöïñÜ ôçí õðï÷ñÝùóç
            åëåýèåñçò ðñüóâáóçò áíôß ãéá ôï áíôßèåôï ðïõ åßíáé êáé ôï ðëÝïí
            óõíçèéóìÝíï. Ëüãù ôçò áõîçìÝíçò ðïëõðëïêüôçôáò ðïõ ìðïñåß íá
            ðñïêýøåé áðü ôçí åìðïñéêÞ ÷ñÞóç ëïãéóìéêïý GPL, ðñïóðáèïýìå ãåíéêÜ
            íá áíôéêáôáóôÞóïõìå áõôü ôï ëïãéóìéêü ìå áíôßóôïé÷ï õðü ôçí
            ðéï ÷áëáñÞ <ulink
            url="http://www.FreeBSD.org/copyright/freebsd-license.html">
            Üäåéá &os;</ulink>, üðïõ áõôü åßíáé äõíáôü.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="bsd-license-restrictions">
          <para>ÕðÜñ÷ïõí êÜðïéïé ðåñéïñéóìïß óôçí Üäåéá ôïõ &os;;</para>
        </question>

        <answer>
          <para>Íáé. Ïé ðåñéïñéóìïß áõôïß äåí åëÝã÷ïõí ðùò ÷ñçóéìïðïéåßôå ôïí
            êþäéêá, áëëÜ ìüíï ðùò ìåôá÷åéñßæåóôå ôï ßäéï ôï &os; Project. Áí
            óáò åíäéáöÝñåé óïâáñÜ ç Üäåéá, äéáâÜóôå ôçí
            <ulink
            url="http://www.FreeBSD.org/copyright/freebsd-license.html">
            åäþ</ulink>.  Ãéá ôïõò áðëþò ðåñßåñãïõò, ç Üäåéá ðåñéëçðôéêÜ
            ãñÜöåé:</para>

          <itemizedlist>
            <listitem>
              <para>Ìçí éó÷õñéóèåßôå üôé ãñÜøáôå áõôü ôï ëïãéóìéêü.</para>
            </listitem>

            <listitem>
              <para>Ìç ìáò ìçíýóåôå áí ÷áëÜóåé.</para>
            </listitem>
          </itemizedlist>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="replace-current-OS">
          <para>Ìðïñåß ôï &os; íá áíôéêáôáóôÞóåé ôï ôñÝ÷ïí ëåéôïõñãéêü
            ìïõ óýóôçìá;</para>
        </question>

        <answer>
          <para>Ãéá ôïõò ðåñéóóüôåñïõò áíèñþðïõò, íáé. ÁëëÜ áõôÞ ç áðÜíôçóç
            äåí ìðïñåß íá äïèåß ôüóï îåñÜ.</para>

          <para>Ïé ðåñéóóüôåñïé Üíèñùðïé äåí ÷ñçóéìïðïéïýí óôçí ðñáãìáôéêüôçôá
            êÜðïéï ëåéôïõñãéêü. ×ñçóéìïðïéïýí åöáñìïãÝò. Ôï &os; åßíáé
            ó÷åäéáóìÝíï íá ðáñÝ÷åé Ýíá óôéâáñü êáé ðëÞñùí äõíáôïôÞôùí
            ðåñéâÜëëïí ãéá åöáñìïãÝò. Õðïóôçñßæåé ìåãÜëç ðïéêéëßá áðü
            öõëëïìåôñçôÝò, óïõßôåò ãñáöåßïõ, ðñïãñÜììáôá çëåêôñïíéêïý
            ôá÷õäñïìåßïõ, ðñïãñÜììáôá ãñáöéêþí, ãëþóóåò ðñïãñáììáôéóìïý,
            åîõðçñåôçôÝò äéêôýïõ, êáé ïõóéáóôéêÜ ïôéäÞðïôå Üëëï ìðïñåß íá
            èåëÞóåôå. Ìðïñåßôå íá äéá÷åéñéóôåßôå ôéò ðåñéóóüôåñåò áðü áõôÝò
            ôéò åöáñìïãÝò ìÝóù ôçò
            <ulink url="http://www.FreeBSD.org/ports/">ÓõëëïãÞò ôùí Ports
            </ulink>.</para>

          <para>Áí ÷ñåéÜæåôáé íá ÷ñçóéìïðïéÞóåôå ìéá åöáñìïãÞ ðïõ åßíáé
            äéáèÝóéìç óå Ýíá ìüíï ëåéôïõñãéêü óýóôçìá, ôüôå áðëÜ äåí ìðïñåßôå
            íá áíôéêáôáóôÞóåôå ôï óýóôçìá áõôü. ÕðÜñ÷ïõí ùóôüóï êáëÝò
            ðéèáíüôçôåò íá âñåßôå ìéá áíôßóôïé÷ç åöáñìïãÞ óôï &os;. Áí
            èÝëåôå Ýíá åîõðçñåôçôÞ ãéá ôï ãñáöåßï óáò Þ ãéá ôï Internet,
            Ýíá áîéüðéóôï óôáèìü åñãáóßáò, Þ áðëþò ôçí éêáíüôçôá íá êÜíåôå
            ôçí åñãáóßáò óáò ÷ùñßò äéáêïðÝò, ôï &os; åßíáé ó÷åäüí óßãïõñï üôé
            èá êÜíåé üôé ÷ñåéÜæåóôå. Ðïëëïß ÷ñÞóôåò õðïëïãéóôþí óå üëï ôïí
            êüóìï, ðåñéëáìâáíïìÝíùí ôüóï áñ÷Üñéùí üóï êáé ðñï÷ùñçìÝíùí
            äéá÷åéñéóôþí óõóôçìÜôùí &unix;, ÷ñçóéìïðïéïýí ôï &os; ùò ôï
            ìïíáäéêü ôïõò desktop óýóôçìá.</para>

          <para>Áí Ýñ÷åóôå óôï &os; áðü êÜðïéï Üëëï &unix; ðåñéâÜëëïí, îÝñåôå
            Þäç ôá ðåñéóóüôåñá áðü áõôÜ ðïõ ÷ñåéÜæåóôå. Áí ùóôüóï ç åìðåéñßá
            óáò ðñïÝñ÷åôáé áðü ëåéôïõñãéêÜ óõóôÞìáôá ìå ãñáöéêü ðåñéâÜëëïí,
            üðùò ôá &windows; êáé ïé ðáëéüôåñåò åêäüóåéò ôïõ &macos;,
            èá ðñÝðåé íá åðåíäýóåôå, üðùò åßíáé áíáìåíüìåíï, åðéðëÝïí ÷ñüíï
            ãéá íá åîïéêåéùèåßôå ìå ôïí &unix; ôñüðï åêôÝëåóçò ôùí åñãáóéþí.
            Áõôü ôï FAQ, êáèþò êáé ôï
            <ulink
            url="&url.books.handbook;/index.html">Åã÷åéñßäéï ôïõ &os;</ulink>
            áðïôåëïýí åîáéñåôéêÜ áíáãíþóìáôá ãéá íá îåêéíÞóåôå.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="why-called-FreeBSD">
          <para>Ãéáôß ïíïìÜæåôáé &os;;</para>
        </question>

        <answer>
          <itemizedlist>
            <listitem>
              <para>Ìðïñåß íá ÷ñçóéìïðïéçèåß ÷ùñßò ÷ñÝùóç, áêüìá êáé ãéá
                åìðïñéêïýò óêïðïýò.</para>
            </listitem>

            <listitem>
              <para>Äéáôßèåôáé ï ðëÞñçò ðçãáßïò êþäéêáò ãéá ôï ëåéôïõñãéêü
                óýóôçìá, êáé ìå ôïõò åëÜ÷éóôïõò äõíáôïýò ðåñéïñéóìïýò ó÷åôéêÜ
                ìå ôç ÷ñÞóç ôïõ, ôç äéáíïìÞ ôïõ êáé ôçí åíóùìÜôùóç ôïõ óå Üëëá
                Ýñãá (åìðïñéêÜ Þ ìç).</para>
            </listitem>

            <listitem>
              <para>ÏðïéïóäÞðïôå Ý÷åé íá ðñïôåßíåé ìéá âåëôßùóç Þ äéüñèùóç,
                åßíáé åëåýèåñïò íá õðïâÜëëåé ôïí êþäéêá ôïõ, ï ïðïßïò êáé
                èá ðñïóôåèåß óôï äÝíôñï ðçãáßïõ êþäéêá (õðü ìéá-äõï âáóéêÝò
                ðñïöáíåßò ðñïûðïèÝóåéò).</para>
            </listitem>
          </itemizedlist>

          <para>Áîßæåé íá áíáöÝñïõìå üôé ç ëÝîç <quote>åëåýèåñï</quote>
            ÷ñçóéìïðïéåßôáé åäþ ìå äýï ôñüðïõò, ï Ýíáò óçìáßíåé
            <quote>äùñåÜí</quote>, êáé ï Üëëïò óçìáßíåé
            <quote>ìðïñåßôå íá ôï êÜíåôå üôé èÝëåôå</quote>. Åêôüò áðü
            Ýíá-äýï ðñÜãìáôá ðïõ <emphasis>äåí</emphasis> ìðïñåßôå íá êÜíåôå
            ìå ôïí êþäéêá ôïõ &os;, ãéá ðáñÜäåéãìá íá éó÷õñéóèåßôå üôé ôïí
            ãñÜøáôå, ìðïñåßôå óôá áëÞèåéá íá ôïí êÜíåôå üôé èÝëåôå.</para>
        </answer>
      </qandaentry>

      <qandaentry>
	<question id="differences-to-other-bsds">
	  <para>Ðïéåò åßíáé ïé äéáöïñÝò ìåôáîý ôïõ &os; êáé ôïõ NetBSD,
            OpenBSD êáé ôùí Üëëùí BSD óõóôçìÜôùí áíïéêôïý êþäéêá;</para>
	</question>

	<answer>
	  <para>Ï James Howard Ý÷åé ãñÜøåé ìéá êáëÞ åîÞãçóç ôçò éóôïñßáò
            êáé ôùí äéáöïñþí ìåôáîý ôùí äéÜöïñùí Ýñãùí ãéá ôï
	    <ulink url="http://www.daemonnews.org/">DaemonNews</ulink>,
	    óôï Üñèñï ðïõ ïíïìÜæåôáé  <ulink
	    url="http://ezine.daemonnews.org/200104/bsd_family.html">Ç
	    ÏéêïãÝíåéá Ëåéôïõñãéêþí BSD</ulink> êáé ôï ïðïßï åìâáèýíåé
            éäéáßôåñá óå áõôÞ ôçí åñþôçóç.</para>
	</answer>
      </qandaentry>

      <qandaentry>
        <question id="latest-version">
          <para>Ðïéá åßíáé ç ôåëåõôáßá Ýêäïóç ôïõ &os;;</para>
        </question>

<!--
   Ç åñþôçóç áõôÞ Ý÷åé ìðåé ãéá íá áðïóáöçíßæåôáé ôï ãåãïíüò üôé õðÜñ÷ïõí
   ðëÝïí ðïëëáðëÝò íÝåò åêäüóåéò ôïõ FreeBSD
-->

        <answer>
	  <para>ÁõôÞ ôç óôéãìÞ óôçí áíÜðôõîç ôïõ &os;, õðÜñ÷ïõí äýï ðáñÜëëçëïé
            êëÜäïé. Êáé áðü ôïõò äýï áõôïýò êëÜäïõò, ðñïêýðôïõí íÝåò åêäüóåéò.
            Ç óåéñÜ ôùí åêäüóåùí 5.× äçìéïõñãåßôáé áðü ôïí êëÜäï
	    <emphasis>5-STABLE</emphasis> åíþ ç óåéñÜ ôùí åêäüóåùí 6.×
	    áðü ôïí <emphasis>6-STABLE</emphasis>.

	  <para>ÌÝ÷ñé êáé ôçí Ýêäïóç ôçò 5.3, ç óåéñÜ 4.× Þôáí ãíùóôÞ ùò
	    <emphasis>-STABLE</emphasis>. Ùóôüóï áðü ôçí 5.3 êáé ìåôÜ, ç
            óåéñÜ 4.× èåùñåßôáé üôé åéóÝñ÷åôáé óôç öÜóç ôçò
	    <quote>åêôåôáìÝíçò õðïóôÞñéîçò</quote> êáé èá ëáìâÜíåé ìüíï
            äéïñèþóåéò ãéá óïâáñÜ ðñïâëÞìáôá, üðùò ð.÷. áõôÜ ðïõ áíáöÝñïíôáé
            óå êåíÜ áóöáëåßáò. Èá õðÜñîïõí ðåñéóóüôåñåò åêäüóåéò áðü ôçí
            óåéñÜ <emphasis>5-STABLE</emphasis>, áëëÜ êáé áõôÞ èåùñåßôáé
	    <quote>ðáñù÷çìÝíç</quote> êáé ç ðåñéóóüôåñç ôñÝ÷ïõóá åñãáóßá èá
            áðïôåëåß ôìÞìá ìüíï ôçò óåéñÜò <emphasis>6-STABLE</emphasis>.

          <para>Ç Ýêäïóç <ulink
            url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/">&rel.current;</ulink>
            åßíáé ç ðëÝïí ôåëåõôáßá ôçò óåéñÜò
            <emphasis>6-STABLE</emphasis> êáé Ýãéíå óôéò
            &rel.current.date;.  Ç Ýêäïóç <ulink
            url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel2.current;-RELEASE/">&rel2.current;</ulink>
            åßíáé ç ðëÝïí ôåëåõôáßá ôçò óåéñÜò
            <emphasis>5-STABLE</emphasis> êáé Ýãéíå óôéò
            &rel2.current.date;.</para>

          <para>Åí óõíôïìßá, ç óåéñÜ  <emphasis>-STABLE</emphasis> ðñïïñßæåôáé
            ãéá ôïõò ISPs, ôïõò åôáéñéêïýò ÷ñÞóôåò êáèþò êáé ïðïéïäÞðïôå
            ÷ñÞóôç èÝëåé óôáèåñüôçôá êáé ìßíéìïõì áñéèìü áëëáãþí óå ó÷Ýóç ìå
            ôá íÝá (êáé ðéèáíüí áóôáèÞ) ÷áñáêôçñéóôéêÜ ðïõ åìöáíßæïíôáé óôç
            óåéñÜ <emphasis>-CURRENT</emphasis>. Åêäüóåéò ìðïñåß íá ãßíïíôáé
            áðü ïðïéïäÞðïôå êëÜäï, áëëÜ ç Ýêäïóç <emphasis>-CURRENT</emphasis>
            èá ðñÝðåé íá ÷ñçóéìïðïéåßôáé ìüíï áí åßóôå ðñïåôïéìáóìÝíïé íá
            ÷åéñéóôåßôå ôá åíäå÷ïìÝíùò ðéï áóôáèÞ ÷áñáêôçñéóôéêÜ ôçò (óå ó÷Ýóç
            ðÜíôá ìå ôçí áíôßóôïé÷ç <emphasis>-STABLE</emphasis>).</para>

          <para>ÍÝåò åêäüóåéò åìöáíßæïíôáé <link linkend="release-freq">êÜèå
            ìåñéêïýò ìÞíåò</link>. Áí êáé ðïëëïß åðéëÝãïõí íá äéáôçñïýíôáé
            åíçìåñùìÝíïé êáé ðéï óõ÷íÜ ìÝóù ôïõ ðçãáßïõ êþäéêá ôïõ &os;
            (äåßôå ôéò åñùôÞóåéò óôï
            <link linkend="current">&os.current;</link> êáé <link
            linkend="stable">&os.stable;</link>), ïé åêäüóåéò åßíáé êÜôé
            ðáñáðÜíù áðü õðï÷ñÝùóç, êáèþò ï ðçãáßïò êþäéêáò åßíáé ðåñéóóüôåñï
            Ýíáò êéíïýìåíïò óôü÷ïò.</para>

	  <para>Ðåñéóóüôåñåò ðëçñïöïñßåò ãéá ôéò åêäüóåéò ôïõ &os; ìðïñåßôå
            íá âñåßôå óôçí
	    <ulink
	    url="http://www.FreeBSD.org/releng/index.html">Óåëßäá
            Ðñïåôïéìáóßáò Åêäüóåùí</ulink> óôçí äéêôõáêÞ ôïðïèåóßá ôïõ &os;.
          </para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="current">
          <para>Ôé åßíáé ôï &os;-CURRENT;</para>
        </question>

        <answer>
          <para>Ôï <ulink
            url="&url.books.handbook;/cutting-edge.html#CURRENT">&os.current;</ulink>
            åßíáé ç õðü åîÝëéîç Ýêäïóç ôïõ ëåéôïõñãéêïý óõóôÞìáôïò, ôï ïðïßï
            ìå ôïí êáéñü èá åîåëé÷èåß óôï íÝï êëÜäï &os.stable;. Ãéá ôï ëüãï
            áõôü, ðáñïõóéÜæåé óõíÞèùò åíäéáöÝñïí ìüíï óå üóïõò áó÷ïëïýíôáé ìå
            ôçí áíÜðôõîç êþäéêá ôïõ óõóôÞìáôïò êáé óå óêëçñïðõñçíéêïýò
            ÷ïìðßóôåò. Äåßôå ôï
            <ulink
            url="&url.books.handbook;/cutting-edge.html#CURRENT">ó÷åôéêü
            ôìÞìá</ulink> óôï  <ulink
            url="&url.books.handbook;/index.html">åã÷åéñßäéï</ulink> ãéá
            ëåðôïìÝñåéåò ó÷åôéêÜ ìå ôï -CURRENT.</para>

          <para>Áí äåí åßóôå åîïéêåéùìÝíïò ìå ôï ëåéôïõñãéêü óýóôçìá, Þ äåí
            åßóôå éêáíüò íá áíáãíùñßóåôå ôç äéáöïñÜ ìåôáîý åíüò ðñáãìáôéêïý
            êáé åíüò ðñïóùñéíïý ðñïâëÞìáôïò, ìÜëëïí äåí èá ðñÝðåé íá
            ÷ñçóéìïðïéÞóåôå ôï &os.current;. Ï êëÜäïò áõôüò ïñéóìÝíåò öïñÝò
            åîåëßóóåôáé ðïëý ãñÞãïñá, êáé ìðïñåß áêüìá êáé ç ìåôáãëþôôéóç ôïõ
            íá ìçí åßíáé äõíáôÞ ãéá ïëüêëçñåò ìÝñåò êÜèå öïñÜ. ¼óïé
            ÷ñçóéìïðïéïýí ôï &os.current; áíáìÝíåôáé íá åßíáé éêáíïß íá
            áíáëýïõí ôá üðïéá ðñïâëÞìáôá êáé íá ôá áíáöÝñïõí, ìüíï áí èåùñïýí
            üôé ðñüêåéôáé ãéá ëÜèç êáé ü÷é ãéá
            <quote>ìéêñïðñïâëÞìáôá</quote>. ÅñùôÞóåéò ôïõ ôýðïõ
            <quote>ôï make world ðáñÜãåé êÜðïéá óöÜëìáôá ó÷åôéêÜ ìå ôá
            groups</quote> óôç ëßóôá ôá÷õäñïìåßïõ -CURRENT, ìðïñåß íá
            áíôéìåôùðéóôïýí ðåñéöñïíçôéêÜ.</para>

          <para>ÊÜèå ìÝñá, ðáñÜãïíôáé  <ulink
	    url="&url.base;/snapshots/">óôéãìéüôõðá
            </ulink> åêäüóåùí ðïõ âáóßæïíôáé óôçí ôñÝ÷ïõóá êáôÜóôáóç ôùí
            êëÜäùí -CURRENT êáé -STABLE. Ãßíïíôáé êáôÜ êáéñïýò äéáèÝóéìåò
            ïé åêäüóåéò êÜðïéùí óôéãìéüôõðùí. Ïé óôü÷ïé ðßóù áðü êÜèå Ýêäïóç
            óôéãìéüôõðïõ åßíáé:</para>

          <itemizedlist>
            <listitem>
              <para>Ï Ýëåã÷ïò ôçò ôåëåõôáßáò Ýêäïóçò ôïõ ëïãéóìéêïý
                åãêáôÜóôáóçò.</para>
            </listitem>

            <listitem>
              <para>Íá äþóåé ôç äõíáôüôçôá åýêïëçò åãêáôÜóôáóçò óå üóïõò
                åðéèõìïýí íá åêôåëïýí ôï -CURRENT Þ ôï -STABLE áëëÜ äåí Ý÷ïõí
                ôï ÷ñüíï Þ ôï åýñïò æþíçò íá ôï ðáñáêïëïõèïýí ìÝñá ìå ôç ìÝñá.
              </para>
            </listitem>

            <listitem>
              <para>Ç äéáôÞñçóç åíüò óôáèåñïý óçìåßïõ áíáöïñÜò ó÷åôéêÜ ìå ôïí
                ðçãáßï êþäéêá, óå ðåñßðôùóç ðïõ ÷áëÜóïõìå êÜôé ðïëý Üó÷çìá
                áñãüôåñá. (Áí êáé ëüãù ôçò ÷ñÞóçò ôïõ CVS åßíáé äýóêïëï íá
                óõìâåß êÜôé ðñáãìáôéêÜ ôüóï öñéêôü :)</para>
            </listitem>

            <listitem>
              <para>Íá åîáóöáëéóôåß üôé êÜèå íÝï ÷áñáêôçñéóôéêü êáé äéüñèùóç
                ðïõ ÷ñåéÜæåôáé Ýëåã÷ï, èá Ý÷åé ôï ìåãáëýôåñï äõíáôü êïéíü
                ðéèáíþí äïêéìáóôþí.</para>
            </listitem>
          </itemizedlist>

          <para>Äåí õðÜñ÷åé ðïôÝ ï éó÷õñéóìüò üôé êÜðïéï óôéãìéüôõðï -CURRENT
            ìðïñåß íá èåùñçèåß <quote>ôåëéêÞò ðïéüôçôáò</quote> ãéá
            ïðïéïäÞðïôå óêïðü. Áí èÝëåôå íá åêôåëåßôå Ýíá ðëÞñùò óôáèåñü êáé
            äïêéìáóìÝíï óýóôçìá, èá ðñÝðåé íá ìåßíåôå óôéò ðëÞñåéò åêäüóåéò Þ
            íá ÷ñçóéìïðïéåßôå ôá óôéãìéüôõðá -STABLE.</para>

	  <para>Åêäüóåéò óôéãìéïôýðùí åßíáé Üìåóá äéáèÝóéìåò áðü <ulink
	    url="&url.base;/snapshots/">åäþ</ulink>.</para>

          <para>ÊáôÜ ìÝóï üñï, ãéá êÜèå êëÜäï ðïõ âñßóêåôáé óå åíåñãÞ
            áíÜðôõîç, ðáñÜãåôáé óôéãìéüôõðï êáèçìåñéíÜ.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="stable">
          <para>Ðïéá åßíáé ç Ýííïéá ôïõ &os;-STABLE;</para>
        </question>

        <answer>
          <para>¼ôáí êõêëïöüñçóå ôï &os; 2.0.5, ç áíÜðôõîç ôïõ &os; ÷ùñßóôçêå
            óå äýï êëÜäïõò. ¼ Ýíáò êëÜäïò ïíïìÜóôçêå
            <ulink url="&url.books.handbook;/current-stable.html#STABLE">
           -STABLE</ulink>, êáé ï Üëëïò <ulink
            url="&url.books.handbook;/current-stable.html#CURRENT">-CURRENT</ulink>.
            Ôï &os;-STABLE ðñïïñßæåôáé ãéá Ðáñï÷åßò Õðçñåóéþí Internet (ISPs)
            êáé ãåíéêÜ åìðïñéêÝò ÷ñÞóåéò, üðïõ ïé áðüôïìåò áëëáãÝò êáé ôá
            ôõ÷üí ðåéñáìáôéêÜ ÷áñáêôçñéóôéêÜ åßíáé ãåíéêÜ áíåðéèýìçôá. Óôïí
            êëÜäï áõôü åíóùìáôþíïíôáé ìüíï êáëÜ äïêéìáóìÝíåò äéïñèþóåéò êáé
            Üëëåò ìéêñÝò ðñüóèåôåò áëëáãÝò. Áðü ôçí Üëëç ìåñéÜ, ôï
            &os;-CURRENT âñßóêåôáé óå ìéá ìïíáäéêÞ áäéÜêïðç ãñáììÞ áíÜðôõîçò
            áðü ôçí åðï÷Þ ôçò êõêëïöïñßáò ôçò Ýêäïóçò 2.0, ïäçãþíôáò ðñïò
            ôçí Ýêäïóç 6.2-RELEASE áëëÜ êáé ìåôÜ áðü áõôÞ. Ëßãï ðñéí ôç
            êõêëïöïñßá ôçò Ýêäïóçò 6.0-RELEASE, äçìéïõñãÞèçêå ï êëÜäïò
            6-STABLE êáé ôï &os.current; Ýãéíå 7-CURRENT. Ãéá ðåñéóóüôåñåò
            ðëçñïöïñßåò äåßôå
            <quote><ulink url="&url.articles.releng;/release-proc.html#REL-BRANCH">
		Ðñïåôïéìáóßá Åêäüóåùí ôïõ &os;:
		Äçìéïõñãßá ôïõ ÊëÜäïõ ¸êäïóçò</ulink></quote>.</para>

          <para>Ï êëÜäïò 2.2-STABLE åãêáôáëåßöèçêå ìå ôçí êõêëïöïñßá ôçò
            Ýêäïóçò 2.2.8. Ï êëÜäïò 3-STABLE ôåëåßùóå ìå ôçí êõêëïöïñßá ôçò
            Ýêäïóçò 3.5.1, ðïõ Þôáí êáé ç ôåëåõôáßá ôçò óåéñÜò åêäüóåùí 3.X.
            Ï êëÜäïò 4-STABLE ôåëåßùóå ìå ôçí êõêëïöïñßá ôçò Ýêäïóçò 4.11, ôçò
            ôåëåõôáßáò ôçò óåéñÜò 4.X. Ïé ìüíåò áëëáãÝò ðïõ ãßíïíôáé êáôÜ
            âÜóç óå êÜèå Ýíá áðü áõôïýò ôïõò êëÜäïõò, Ý÷ïõí ó÷Ýóç ìå
            äéïñèþóåéò óå êåíÜ áóöáëåßáò. Ç õðïóôÞñéîç ôùí êëÜäùí 5-STABLE èá
            óõíå÷éóôåß ãéá êÜðïéï äéÜóôçìá, ùóôüóï èá åðéêåíôñùèåß
            ðåñéóóüôåñï óå äéïñèþóåéò êåíþí áóöáëåßáò êáé Üëëùí óïâáñþí
            ðñïâëçìÜôùí.</para>

          <para>Ôï &rel.current;-STABLE åßíáé ï êëÜäïò ðïõ âñßóêåôáé õðü
            åíåñãÞ áíÜðôõîç. Ç ôåëåõôáßá êõêëïöïñßá ðïõ âáóßæåôáé óôïí êëÜäï
            &rel.current;-STABLE åßíáé ç &rel.current;-RELEASE, êáé Ýãéíå
            óôéò &rel.current.date;.</para>

          <para>Ï êëÜäïò 7-CURRENT åßíáé ï êëÜäïò -CURRENT ðïõ áíáðôýóóåôáé
            áõôÞ ôç óôéãìÞ åíåñãÜ þóôå íá äçìéïõñãçèåß ç íÝá ãåíéÜ ôïõ &os;.
	    Äåßôå  <link linkend="current">Ôé åßíáé ôï &os;-CURRENT;</link>
            ãéá ðåñéóóüôåñåò ðëçñïöïñßåò ó÷åôéêÜ ìå áõôü ôïí êëÜäï.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="release-freq">
          <para>ÊÜèå ðüôå ãßíïíôáé åðßóçìåò êõêëïöïñßåò ôïõ &os;;</para>
        </question>

        <answer>
	  <para>H &a.re; äßíåé óôçí êõêëïöïñßá ìéá êáéíïýñéá Ýêäïóç ôïõ &os;
            êÜèå ðåñßðïõ ôÝóóåñéò ìÞíåò, êáôÜ ìÝóï üñï. Ïé çìåñïìçíßåò
            êõêëïöïñßáò áíáêïéíþíïíôáé áñêåôü êáéñü ðñéí, þóôå üóïé äïõëåýïõí
            ðÜíù óôï óýóôçìá íá îÝñïõí ðüôå ïé åñãáóßåò ôïõò ðñÝðåé íá Ý÷ïõí
            ïëïêëçñùèåß êáé äïêéìáóôåß. Ðñéí áðü êÜèå êõêëïöïñßá, ðñïçãåßôáé
            ìéá ðåñßïäïò äïêéìþí, þóôå íá åîáóöáëéóôåß üôé ç ðñïóèÞêç íÝùí
            ÷áñáêôçñéóôéêþí äåí Ý÷åé áñíçôéêÝò åðéðôþóåéò óôç óôáèåñüôçôá
            ôçò Ýêäïóçò. Ðïëëïß ÷ñÞóôåò èåùñïýí áõôü ôï åßäïò ôçò ðñïóï÷Þò
            Ýíá áðü ôá êáëýôåñá ðñÜãìáôá ó÷åôéêÜ ìå ôï &os;, áí êáé ç áíáìïíÞ
            ùò üôïõ öôÜóïõí üëá ôá ùñáßá íÝá ÷áñáêôçñéóôéêÜ ôï -STABLE ìðïñåß
            íá ãßíåé ëßãï åêíåõñéóôéêÞ.</para>

	  <para>Ðåñéóóüôåñåò ðëçñïöïñßåò ó÷åôéêÜ ìå ôç äéáäéêáóßá êõêëïöïñßáò
            (ðåñéëáìâáíïìÝíïõ êáé åíüò ÷ñïíïäéáãñÜììáôïò åðéêåßìåíùí
            êõêëïöïñéþí) ìðïñïýí íá âñåèïýí óôéò óåëßäåò
	    <ulink
	    url="http://www.FreeBSD.org/releng/index.html">ðñïåôïéìáóßáò
	    åêäüóåùí</ulink> óôç äéêôõáêÞ ôïðïèåóßá ôïõ &os;.</para>

          <para>Ãéá ôïõò ðéï åíèïõóéþäåéò, õðÜñ÷ïõí êáèçìåñéíÜ óôéãìéüôõðá
            (binary snapshots) üðùò áíáöÝñèçêå ðéï ðÜíù.</para>
         </answer>
      </qandaentry>

      <qandaentry>
        <question id="responsible">
          <para>Ðïéïò åßíáé õðåýèõíïò ãéá ôï &os;</para>
        </question>

        <answer>
          <para>Ïé âáóéêÝò áðïöÜóåéò ðïõ áöïñïýí ôï &os; Project, üðùò ç
            óõíïëéêÞ êáôåýèõíóç ôïõ Ýñãïõ êáé ðïéïò åðéôñÝðåôáé íá ðñïóèÝóåé
            ðçãáßï êþäéêá óôï äÝíôñï, ðáßñíïíôáé áðü ôçí
            <ulink
            url="&url.base;/administration.html#t-core">âáóéêÞ ïìÜäá
            (core team)</ulink> ðïõ áðïôåëåßôáé áðü 9 Üôïìá. ÕðÜñ÷åé ìéá
            áêüìá ìåãáëýôåñç ïìÜäá ìå ðåñéóóüôåñá áðü 350 Üôïìá ðïõ
            ïíïìÜæïíôáé
            <ulink
            url="&url.articles.contributors;/article.html#STAFF-COMMITTERS">
            äéáðñÜêôåò (committers)</ulink>
            êáé ïé ïðïßïé Ý÷ïõí ôçí Ýãêñéóç íá êÜíïõí áðåõèåßáò áëëáãÝò óôï
            äÝíôñï ðçãáßïõ êþäéêá ôïõ &os;.</para>

          <para>Ùóôüóï ïé ðåñéóóüôåñåò óçìáíôéêÝò áëëáãÝò óõæçôïýíôáé áðü
            ðñéí óôéò <link linkend="mailing">ëßóôåò çëåêôñïíéêïý
            ôá÷õäñïìåßïõ</link>, êáé äåí õðÜñ÷ïõí ðåñéïñéóìïß ó÷åôéêÜ ìå ôï
            ðïéïé ëáìâÜíïõí ìÝñïò óå áõôÝò ôéò óõæçôÞóåéò.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="where-get">
          <para>Ðïõ ìðïñþ íá ðñïìçèåõôþ ôï &os;;</para>
        </question>

        <answer>
          <para>ÊÜèå óçìáíôéêÞ Ýêäïóç ôïõ &os; åßíáé äéáèÝóéìç ìÝóù áíþíõìïõ
            FTP áðü ôïí <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/">
            äéáêïìéóôÞ FTP ôïõ &os;</ulink>:</para>

          <itemizedlist>
            <listitem>
              <para>Ç ôåëåõôáßá êõêëïöïñßá ðïõ âáóßæåôáé óôï 6-STABLE,
                &rel.current;-RELEASE ìðïñåß íá âñåèåß óôïí êáôÜëïãï
                <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/">&rel.current;-RELEASE</ulink>.</para>
            </listitem>

            <listitem>
              <para>Åêäüóåéò ðïõ âáóßæïíôáé óå<ulink
		url="&url.base;/snapshots/">
                Óôéãìéüôõðá</ulink> ãßíïíôáé êáèçìåñéíÜ áðü ôïõò êëÜäïõò
		<link linkend="current">-CURRENT</link> êáé
                <link linkend="stable">-STABLE</link>, êáé åîõðçñåôïýí êáôÜ
                âÜóç üóïõò áó÷ïëïýíôáé ìå ôçí áíÜðôõîç êáé ôïí Ýëåã÷ï ôùí
                ôåëåõôáßáò ãåíéÜò ðñïãñáììÜôùí.</para>
            </listitem>

            <listitem>
              <para>Ç ôåëåõôáßá êõêëïöïñßá ðïõ âáóßæåôáé óôïí êëÜäï  5-STABLE
                ,ç  &rel2.current;-RELEASE, ìðïñåß íá âñåèåß óôïí êáôÜëïãï
                <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel2.current;-RELEASE/">&rel2.current;-RELEASE</ulink>.</para>
            </listitem>
          </itemizedlist>

	  <para>Ðëçñïöïñßåò ó÷åôéêÜ ìå ôç äéÜèåóç ôïõ &os; óå CD, DVD êáé Üëëá
            ìÝóá ìðïñïýí íá âñåèïýí
	    <ulink url="&url.books.handbook;/mirrors.html">óôï Åã÷åéñßäéï
	    </ulink>.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="access-pr">
          <para>Ðùò ìðïñþ íá Ý÷ù ðñüóâáóç óôç ÂÜóç ÄåäïìÝíùí ìå ôéò
            ÁíáöïñÝò ÐñïâëçìÜôùí;</para>
        </question>

        <answer>
          <para>Ìðïñåßôå íá êÜíåôå áíáæçôÞóåéò óôç âÜóç äåäïìÝíùí ìå ôéò
            áíáöïñÝò ðñïâëçìÜôùí ìÝóù ôçò
            <ulink
            url="http://www.FreeBSD.org/cgi/query-pr-summary.cgi?query">
            äéåðáöÞò áíáæçôÞóåùí óôï Web</ulink>.</para>

	  <para>Ç åíôïëÞ &man.send-pr.1; ìðïñåß íá ÷ñçóéìïðïéçèåß ãéá ôçí
            õðïâïëÞ áíáöïñþí ðñïâëçìÜôùí, êáèþò êáé áéôÞóåùí ãéá áëëáãÝò,
            ìÝóù çëåêôñïíéêïý ôá÷õäñïìåßïõ. ÅíáëëáêôéêÜ, ìðïñåßôå íá
            ÷ñçóéìïðïéÞóåôå ôçí áíôßóôïé÷ç äõíáôüôçôá
	      <ulink url="http://www.freebsd.org/send-pr.html">õðïâïëÞò
            áíáöïñþí ðñïâëçìÜôùí ìÝóù ôçò äéåðáöÞò web</ulink> ìå ôç âïÞèåéá
            åíüò ðñïãñÜììáôïò öõëëïìåôñçôÞ.</para>

          <para>Ðñéí õðïâÜëåôå ìéá áíáöïñÜ ðñïâëÞìáôïò, ðáñáêáëïýìå äéáâÜóôå
            ôï
            <ulink url="&url.articles.problem-reports;/article.html">ÃñÜöïíôáò
            ÁíáöïñÝò ÐñïâëçìÜôùí ãéá ôï &os;</ulink>, Ýíá Üñèñï ãéá ôï ðùò
            íá ãñÜöåôå êáëÝò áíáöïñÝò ðñïâëçìÜôùí.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="other-info-sources">
          <para>Ôé Üëëåò ðçãÝò ðëçñïöïñéþí õðÜñ÷ïõí;</para>
        </question>

        <answer>
          <para>Ðáñáêáëïýìå åëÝãîôå ôç ëßóôá ôçò <ulink
            url="http://www.FreeBSD.org/docs.html">Ôåêìçñßùóçò</ulink>
            óôçí êýñéá äéêôõáêÞ ôïðïèåóßá ôïõ <ulink
            url="http://www.FreeBSD.org">&os;</ulink>.</para>
        </answer>
      </qandaentry>
    </qandaset>
  </chapter>

  <chapter id="support">
    <title>Ôåêìçñßùóç êáé ÕðïóôÞñéîç</title>
    
    <qandaset>
      <qandaentry>
	<question id="books">
	  <para>Ðïéá êáëÜ âéâëßá õðÜñ÷ïõí ó÷åôéêÜ ìå ôï &os;;</para>
	</question>
	
	<answer>
	  <para>Ôï Project ðáñÜãåé ìéá ìåãÜëç ãêÜìá ôåêìçñßùóçò ðïõ äéáôßèåôáé
            online áðü ôïí ðáñáêÜôù óýíäåóìï:
            <ulink url="http://www.FreeBSD.org/docs.html"></ulink>. Ôá ßäéá
            áõôÜ Ýããñáöá åßíáé äéáèÝóéìá êáé ùò ðáêÝôá ôá ïðïßá ìðïñåßôå íá
            åãêáôáóôÞóåôå åýêïëá óôï &os; óýóôçìá óáò. Ðåñéóóüôåñåò
            ëåðôïìÝñåéåò ó÷åôéêÜ ìå ôá ðáêÝôá ôåêìçñßùóçò, èá âñåßôå óôéò
            áêüëïõèåò ðáñáãñÜöïõò.</para>
	    
	    <para>Åðéðñüóèåôá, èá âñåßôå êáé Üëëá óõíéóôþìåíá âéâëßá óôçí
              Âéâëéïãñáößá óôï ôÝëïò áõôïý ôïõ FAQ, êáé ôïõ Åã÷åéñéäßïõ.
	    </para>
	</answer>
      </qandaentry>
      
      <qandaentry>
        <question id="doc-formats">
          <para>Åßíáé äéáèÝóéìç ç ôåêìçñßùóç êáé óå Üëëåò ìïñöÝò, üðùò áðëü
            êåßìåíï (ASCII) Þ &postscript;;</para>
        </question>

        <answer>
          <para>Íáé. Ç ôåêìçñßùóç åßíáé äéáèÝóéìç óå ðëÞèïò äéáöïñåôéêþí
            ìïñöþí êáé ôñüðùí óõìðßåóåçò, óôï äéáêïìéóôÞ FTP ôïõ &os;, óôïí
            êáôÜëïãï <ulink
            url="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">/pub/FreeBSD/doc/</ulink>.</para>

          <para>Ç ôåêìçñßùóç åßíáé êáôçãïñéïðïéçìÝíç ìå äéÜöïñïõò ôñüðïõò.
            Áõôïß ðåñéëáìâÜíïõí:</para>

          <itemizedlist>
            <listitem>
              <para>Ôï üíïìá ôïõ åããñÜöïõ, üðùò ð.÷. <literal>faq</literal>, Þ
                <literal>handbook</literal>.</para>
            </listitem>

            <listitem>
              <para>H ãëþóóá êáé ç êùäéêïðïßçóç ôïõ êåéìÝíïõ. ÁõôÜ âáóßæïíôáé
                óôá ïíüìáôá ðïõ Ý÷ïõí äïèåß óôéò ôïðéêÝò ñõèìßóåéò êáé ðïõ
                ìðïñåßôå íá âñåßôå óôïí êáôÜëïãï
                <filename>/usr/share/locale</filename> óôï &os; óýóôçìá óáò. 
                Ïé ôñÝ÷ïõóåò ãëþóóåéò êáé êùäéêïðïéÞóåéò ðïõ Ý÷ïõìå äéáèÝóéìåò
                áõôÞ ôç óôéãìÞ óôçí ôåêìçñßùóç åßíáé ïé ðáñáêÜôù:</para>

              <informaltable frame="none" pgwide="1">
                <tgroup cols="2">
                  <thead>
                    <row>
                      <entry>¼íïìá</entry>

                      <entry>Åñìçíåßá</entry>
                    </row>
                  </thead>

                  <tbody>
                    <row>
                      <entry><literal>en_US.ISO8859-1</literal></entry>

                      <entry>ÁããëéêÜ ÇÐÁ</entry>
                    </row>

                    <row>
                      <entry><literal>bn_BD.ISO10646-1</literal></entry>

                      <entry>Bengali (Þ Bangla)</entry>
                    </row>

                    <row>
                      <entry><literal>da_DK.ISO8859-1</literal></entry>

                      <entry>ÄáíÝæéêá</entry>
                    </row>

                    <row>
                      <entry><literal>de_DE.ISO8859-1</literal></entry>

                      <entry>ÃåñìáíéêÜ</entry>
                    </row>

                    <row>
                      <entry><literal>es_ES.ISO8859-1</literal></entry>

                      <entry>ÉóðáíéêÜ</entry>
                    </row>

                    <row>
                      <entry><literal>fr_FR.ISO8859-1</literal></entry>

                      <entry>ÃáëëéêÜ</entry>
                    </row>

                    <row>
                      <entry><literal>hu_HU.ISO8859-2</literal></entry>

                      <entry>ÏõããáñÝæéêá</entry>
                    </row>

		    <row>
		      <entry><literal>it_IT.ISO8859-15</literal></entry>

		      <entry>ÉôáëéêÜ</entry>
		    </row>

                    <row>
                      <entry><literal>ja_JP.eucJP</literal></entry>

                      <entry>ÃéáðùíÝæéêá (êùäéêïðïßçóç EUC)</entry>
                    </row>

                    <row>
                      <entry><literal>mn_MN.UTF-8</literal></entry>

                      <entry>ÌïããïëéêÜ (êùäéêïðïßçóç UTF-8)</entry>
                    </row>

                    <row>
                      <entry><literal>nl_NL.ISO8859-1</literal></entry>

                      <entry>ÏëëáíäéêÜ</entry>
                    </row>

                    <row>
                      <entry><literal>pl_PL.ISO8859-2</literal></entry>

                      <entry>ÐïëùíéêÜ</entry>
                    </row>

                    <row>
                      <entry><literal>pt_BR.ISO8859-1</literal></entry>

                      <entry>ÐïñôïãáëëéêÜ (Âñáæéëßá)</entry>
                    </row>

                    <row>
                      <entry><literal>ru_RU.KOI8-R</literal></entry>

                      <entry>Ñþóóéêá (êùäéêïðïßçóç KOI8-R)</entry>
                    </row>

                    <row>
                      <entry><literal>sr_YU.ISO8859-2</literal></entry>

                      <entry>ÓÝñâéêá</entry>
                    </row>

                    <row>
                      <entry><literal>tr_TR.ISO8859-9</literal></entry>

                      <entry>Ôïýñêéêá</entry>
                    </row>

                    <row>
                      <entry><literal>zh_CN.GB2312</literal></entry>

                      <entry>ÁðëïðïéçìÝíá ÊéíÝæéêá (êùäéêïðïßçóç GB2312)
                        </entry>
                    </row>

                    <row>
                      <entry><literal>zh_TW.Big5</literal></entry>

                      <entry>ÐáñáäïóéáêÜ ÊéíÝæéêá (êùäéêïðïßçóç Big5)</entry>
                    </row>
                  </tbody>
                </tgroup>
              </informaltable>

              <note>
                <para>ÊÜðïéá Ýããñáöá ìðïñåß íá ìçí åßíáé äéáèÝóéìá óå üëåò
                  ôéò ãëþóóåò.</para>
              </note>
            </listitem>

            <listitem>
              <para>Ôç ìïñöÞ ôïõ åããñÜöïõ. ÐáñÜãïõìå ôåêìçñßùóç óå ðëÞèïò
                äéáöïñåôéêþí ìïñöþí åîüäïõ. ÊÜèå ìïñöÞ Ý÷åé ôá äéêÜ ôçò
                ðëåïíåêôÞìáôá êáé ìåéïíåêôÞìáôá. ÊÜðïéåò ìïñöÝò åßíáé
                ðåñéóóüôåñï êáôÜëëçëåò ãéá äéÜâáóìá online, åíþ Üëëåò
                äßíïõí ðéï êáëáßóèçôï áðïôÝëåóìá üôáí åêôõðùèïýí. Ç äéÜèåóç
                ôçò ôåêìçñßùóçò óå üëåò áõôÝò ôéò ìïñöÝò åîáóöáëßæåé üôé ïé
                áíáãíþóôåò ìáò èá ìðïñïýí íá äéáâÜóïõí ôá ôìÞìáôá ðïõ ôïõò
                åíäéáöÝñïõí, åßôå óôçí ïèüíç ôïõò, åßôå áöïý ôá åêôõðþóïõí.
                Ïé äéáèÝóéìåò áõôÞ ôç óôéãìÞ ìïñöÝò åßíáé:</para>

              <informaltable frame="none" pgwide="1">
                <tgroup cols="2">
                  <thead>
                    <row>
                      <entry>ÌïñöÞ</entry>

                      <entry>Åñìçíåßá</entry>
                    </row>
                  </thead>

                  <tbody>
                    <row>
                      <entry><literal>html-split</literal></entry>

                      <entry>ÓõëëïãÞ ìéêñþí, óõíäåìÝíùí ìåôáîý ôïõò, áñ÷åßùí
                        HTML.</entry>
                    </row>

                    <row>
                      <entry><literal>html</literal></entry>

                      <entry>¸íá ìåãÜëï HTML áñ÷åßï ðïõ ðåñéÝ÷åé ïëüêëçñï ôï
                        Ýããñáöï.</entry>
                    </row>

                    <row>
                      <entry><literal>pdb</literal></entry>

                      <entry>ÌïñöÞ âÜóçò äåäïìÝíùí ãéá ôï Palm Pilot, ãéá
                        ÷ñÞóç ìå ôï ðñüãñáììá áíÜãíùóçò
                        <ulink url="http://www.iSilo.com/">iSilo</ulink>.
                      </entry>
                    </row>

                    <row>
                      <entry><literal>pdf</literal></entry>

                      <entry>ÌïñöÞ êåéìÝíïõ PDF ôçò Adobe.</entry>
                    </row>

                    <row>
                      <entry><literal>ps</literal></entry>

                      <entry>&postscript;</entry>
                    </row>

                    <row>
                      <entry><literal>rtf</literal></entry>

                      <entry>ÌïñöÞ ÅìðëïõôéóìÝíïõ ÊåéìÝíïõ ôçò Microsoft
                          <footnote><para>Ïé áñéèìïß óåëßäùí äåí áíáíåþíïíôáé
                          áõôüìáôá üôáí öïñôþíåôáé áõôÞ ôç ìïñöÞ åããñÜöïõ óôï
                          Word. ÐéÝóôå
                          <keycombo
                          action="simul"><keycap>CTRL</keycap><keycap>A</keycap></keycombo>,
                          <keycombo
                          action="simul"><keycap>CTRL</keycap><keycap>END</keycap></keycombo>,
                          <keycap>F9</keycap> ìåôÜ ôç öüñôùóç ôïõ êåéìÝíïõ ãéá
                          ôçí áíáíÝùóç ôùí áñéèìþí óåëßäùí.</para>
                        </footnote>
                      </entry>
                    </row>

                    <row>
                      <entry><literal>txt</literal></entry>

                      <entry>Áðëü êåßìåíï</entry>
                    </row>
                  </tbody>
                </tgroup>
              </informaltable>
            </listitem>

            <listitem>
              <para>Ï ôñüðïò óõìðßåóçò êáé ðáêåôáñßóìáôïò. ÕðÜñ÷ïõí ôñåéò
                ôñüðïé ðïõ ÷ñçóéìïðïéïýíôáé áõôÞ ôç óôéãìÞ.</para>

              <orderedlist>
                <listitem>
                  <para>¼ôáí ç ìïñöÞ åßíáé
                    <literal>html-split</literal>, ôá áñ÷åßá óõìðéÝæïíôáé
                    ìå ÷ñÞóç ôçò &man.tar.1;.  Ôï áñ÷åßï
                    <filename>.tar</filename> ðïõ ðñïêýðôåé, óõìðéÝæåôáé
                    Ýðåéôá ìå ôïõò ôñüðïõò óõìðßåóçò ðïõ ðåñéãñÜöïíôáé
                    ðáñáêÜôù.</para>
                </listitem>

                <listitem>
                  <para>¼ëåò ïé Üëëåò ìïñöÝò äçìéïõñãïýí Ýíá áñ÷åßï ðïõ
                    ïíïìÜæåôáé
                    <filename>book.<replaceable>ìïñöÞ</replaceable></filename>
                    (ð.÷., <filename>book.pdb</filename>,
                    <filename>book.html</filename>, ê.ï.ê.).</para>

                  <para>Ôá áñ÷åßá áõôÜ óõìðéÝæïíôáé êáôüðéí ìå äýï ôñüðïõò
                    óõìðßåóçò.</para>

                  <informaltable frame="none" pgwide="1">
                    <tgroup cols="2">
                      <thead>
                        <row>
                          <entry>Ôñüðïò</entry>

                          <entry>ÐåñéãñáöÞ</entry>
                        </row>
                      </thead>

                      <tbody>
                        <row>
                          <entry><literal>zip</literal></entry>

                          <entry>ÌïñöÞ óõìðßåóçò Zip. Áí èÝëåôå íá
                            ôï áðïóõìðéÝóåôå óôï &os; èá ðñÝðåé íá
                            åãêáôáóôÞóåôå ðñþôá ôï port
                            <filename
                            role="package">archivers/unzip</filename>.
                          </entry>
                        </row>

                        <row>
                          <entry><literal>bz2</literal></entry>

                          <entry>Ç ìïñöÞ BZip2. Åßíáé ëéãüôåñï äéáäåäïìÝíç 
                            áðü ôï Zip, áëëÜ ãåíéêÜ äçìéïõñãåß ìéêñüôåñá
                            áñ÷åßá.  ÅãêáôáóôÞóôå ôï port <filename
                            role="package">archivers/bzip2</filename>
                            ãéá íá áðïóõìðéÝóåôå áñ÷åßá áõôïý ôïõ ôýðïõ.
                          </entry>
                        </row>
                      </tbody>
                    </tgroup>
                  </informaltable>

                  <para>Ìå ôïí ôñüðï áõôü, ç  &postscript; ôïõ Åã÷åéñéäßïõ,
                    óõìðéåóìÝíç ìå ÷ñÞóç ôïõ BZip2 èá áðïèçêåõôåß óå Ýíá
                    áñ÷åßï ìå üíïìá <filename>book.ps.bz2</filename> óôïí
                    êáôÜëïãï <filename>handbook/</filename>.</para>
                </listitem>
              </orderedlist>
            </listitem>
          </itemizedlist>

          <para>Áöïý åðéëÝîåôå ôç ìïñöÞ êáé ôï ìç÷áíéóìü óõìðßåóç ðïõ
            åðéèõìåßôå íá êáôåâÜóåôå, èá ðñÝðåé Ýðåéôá íá áðïöáóßóåôå áí
            èÝëåôå Þ ü÷é  íá êáôåâÜóåôå ôï Ýããñáöï ìå ôç ìïñöÞ
            <emphasis>ðáêÝôïõ</emphasis> ôïõ &os;.</para>

          <para>Ôï ðëåïíÝêôçìá óôï íá êáôåâÜóåôå êáé íá åãêáôáóôÞóåôå ôï
            ðáêÝôï åßíáé üôé Ýðåéôá ìðïñåßôå íá äéá÷åéñéóôåßôå ôçí
            ôåêìçñßùóç ÷ñçóéìïðïéþíôáò ôá óõíçèéóìÝíá åñãáëåßá äéá÷åßñéóçò
            ðáêÝôùí ôïõ &os; üðùò ôçí &man.pkg.add.1; êáé ôçí
            &man.pkg.delete.1;.</para>

          <para>Áí áðïöáóßóåôå íá êáôåâÜóåôå êáé íá åãêáôáóôÞóåôå ôçí
            ôåêìçñßùóç ùò ðáêÝôï, èá ðñÝðåé íá îÝñåôå ôï áêñéâÝò üíïìá áñ÷åßïõ
            ðïõ èá êáôåâÜóåôå. Ôá áñ÷åßá ôåêìçñßùóçò-ùò-ðáêÝôï áðïèçêåýïíôáé
            óå Ýíá êáôÜëïãï ìå ôï üíïìá <filename>packages</filename>. ÊÜèå
            ðáêÝôï ìïéÜæåé ìå
            <filename><replaceable>üíïìá-êåéìÝíïõ</replaceable>.<replaceable>ãëþóóá</replaceable>.<replaceable>êùäéêïðïßçóç</replaceable>.<replaceable>ìïñöÞ</replaceable>.tgz</filename>.</para>

          <para>Ãéá ðáñÜäåéãìá, ôï FAQ, óôá ÁããëéêÜ, óå ìïñöÞ PDF, åßíáé óôï
            ðáêÝôï ìå üíïìá
            <filename>faq.en_US.ISO8859-1.pdf.tgz</filename>.</para>

          <para>Áí ôï îÝñåôå áõôü ìðïñåßôå íá ÷ñçóéìïðïéÞóåôå ôçí áêüëïõèç
            åíôïëÞ ãéá íá åãêáôáóôÞóåôå ôï ðáêÝôï ôïõ Áããëéêïý PDF FAQ:</para>

          <screen>&prompt.root; <userinput>pkg_add ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/packages/faq.en_US.ISO8859-1.pdf.tgz</userinput></screen>

          <para>Áöïý ôï êÜíåôå áõôü, ìðïñåßôå íá ÷ñçóéìïðïéÞóåôå ôçí åíôïëÞ
            &man.pkg.info.1; ãéá íá âñåßôå ðïõ Ý÷åé åãêáôáóôáèåß ôï áñ÷åßï.
          </para>

          <screen>&prompt.root; <userinput>pkg_info -f faq.en_US.ISO8859-1.pdf</userinput>
Information for faq.en_US.ISO8859-1.pdf:

Packing list:
        Package name: faq.en_US.ISO8859-1.pdf
        CWD to /usr/share/doc/en_US.ISO8859-1/books/faq
File: book.pdf
        CWD to .
File: +COMMENT (ignored)
File: +DESC (ignored)</screen>

          <para>¼ðùò ìðïñåßôå íá äåßôå, ôï <filename>book.pdf</filename> èá
            Ý÷åé åãêáôáóôáèåß óôïí êáôÜëïãï
            <filename>/usr/share/doc/en_US.ISO8859-1/books/faq</filename>.
          </para>

          <para>Áí äåí èÝëåôå íá ÷ñçóéìïðïéÞóåôå ôá ðáêÝôá, èá ðñÝðåé íá
            êáôåâÜóåôå ìüíïé óáò ôá óõìðéåóìÝíá áñ÷åßá, íá ôá áðïóõìðéÝóåôå
            êáé Ýðåéôá íá áíôéãñÜøåôå ôá áíôßóôïé÷á Ýããñáöá óôç èÝóç ôïõò.
          </para>

          <para>Ãéá ðáñÜäåéãìá, ç Ýêäïóç  HTML óå óõíäåìÝíá áñ÷åßá ôïõ FAQ,
            óõìðéåóìÝíç ìå ÷ñÞóç ôïõ &man.bzip2.1;, ìðïñåß íá âñåèåß óôï 
            áñ÷åßï
            <filename>doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2
            </filename>. Ãéá íá êáôåâÜóåôå êáé íá áðïóõìðéÝóåôå áõôü ôï áñ÷åßï
            èá ðñÝðåé íá êÜíåôå ôï ðáñáêÜôù:</para>

          <screen>&prompt.root; <userinput>fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2</userinput>
&prompt.root; <userinput>bzip2 -d book.html-split.tar.bz2</userinput>
&prompt.root; <userinput>tar xvf book.html-split.tar</userinput></screen>

          <para>Èá êáôáëÞîåôå ìå ìéá óõëëïãÞ áðü áñ÷åßá
            <filename>.html</filename>. Ôï âáóéêü ïíïìÜæåôá
            <filename>index.html</filename>, êáé èá ðåñéÝ÷åé ôïí ðßíáêá
            ðåñéå÷ïìÝíùí, åéóáãùãéêü õëéêü, êáé äåóìïýò ðñïò ôá Üëëá ôìÞìáôá
            ôïõ åããñÜöïõ. Ìðïñåßôå Ýðåéôá íá áíôéãñÜøåôå Þ íá ìåôáêéíÞóåôå
            ôá áñ÷åßá áõôÜ óôéò ôåëéêÝò ôïõò èÝóåéò, üðùò áðáéôåßôáé.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="mailing">
          <para>Ðïõ ìðïñþ íá âñù ðëçñïöïñßåò ãéá ëßóôåò çëåêôñïíéêïý
            ôá÷õäñïìåßïõ ôïõ &os;;</para>
        </question>

        <answer>
          <para>Ìðïñåßôå íá âñåßôå ðëÞñåéò ðëçñïöïñßåò óôçí áíôßóôïé÷ç <ulink
            url="&url.books.handbook;/eresources.html#ERESOURCES-MAIL">
            êáôá÷þñçóç ôïõ Åã÷åéñéäßïõ ãéá ôéò ëßóôåò çëåêôñïíéêïý
            ôá÷õäñïìåßïõ.</ulink>.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="newsgroups">
          <para>Ôé ïìÜäåò óõæÞôçóçò åßíáé äéáèÝóéìåò ãéá ôï &os;;</para>
        </question>

        <answer>
          <para>Ìðïñåßôå íá âñåßôå ðëÞñåéò ðëçñïöïñßåò óôçí <ulink
            url="&url.books.handbook;/eresources-news.html">êáôá÷þñçóç ôïõ
            Åã÷åéñéäßïõ ãéá ôéò ïìÜäåò óõæçôÞóåùí.</ulink>.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="irc">
          <para>ÕðÜñ÷ïõí êáíÜëéá óôï IRC (Internet Relay Chat) ãéá ôï &os;;
            </para>
        </question>

        <answer>
          <para>Íáé, ôá ðåñéóóüôåñá IRC äßêôõá äéáèÝôïõí êáíÜëé óõæÞôçóçò ãéá
            ôï &os;:</para>

          <itemizedlist>
            <listitem>
              <para>Ôï êáíÜëé <literal>#FreeBSD</literal> óôï
                <ulink url="http://www.efnet.org/index.php">EFNet</ulink>
                áó÷ïëåßôáé ìå ôï &os;, áëëÜ ìçí ðÜôå åêåß ãéá ôå÷íéêÞ
                õðïóôÞñéîç Þ ãéá íá ðñïóðáèÞóåôå íá ðåßóåôå ôïõò èáìþíåò íá
                óáò âïçèÞóïõí ãéá íá áðáëëáãåßôå áðü ôïí êüðï íá äéáâÜóåôå ôéò
                óåëßäåò âïÞèåéáò Þ íá åñåõíÞóåôå ìüíïò óáò. Åßíáé áðëþò Ýíá
                êáíÜëé óõæÞôçóçò, ðñþôá áðü üëá, êáé ôá èÝìáôá åêåß ìðïñåß
                íá êõìáßíïíôáé áíÜìåóá óôï óåî, ôïí áèëçôéóìü, ôá ðõñçíéêÜ
                üðëá ùò êáé ôï &os;. Óáò Ý÷ïõìå ðñïåéäïðïéÞóåé! Åßíáé
                äéáèÝóéìï óôïí åîõðçñåôçôÞ <hostid>irc.chat.org</hostid>.
              </para>
            </listitem>

            <listitem>
              <para>Ôï êáíÜëé <literal>#FreeBSDhelp</literal> óôï
                <ulink url="http://www.efnet.org/index.php">EFNet</ulink>
                åßíáé áöéåñùìÝíï óôç âïÞèåéá ôùí ÷ñçóôþí ôïõ &os;. ¸÷åôå
                ðïëý ìåãáëýôåñç ðéèáíüôçôá íá âñåßôå áðáíôÞóåéò óôéò åñùôÞóåéò
                óáò óå áõôü, ðáñÜ óôï <literal>#FreeBSD</literal>.</para>
            </listitem>

	    <listitem>
              <para>Ôï êáíÜëé <literal>##FreeBSD</literal> óôï
                <ulink url="http://freenode.net/">Freenode</ulink>
                åßíáé Ýíá ãåíéêü êáíÜëé âïÞèåéáò ìå ðåñßðïõ 300 ÷ñÞóôåò êÜèå
                öïñÜ. Ïé óõæçôÞóåéò ìåñéêÝò öïñÝò îåöåýãïõí áðü ôï èÝìá,
                áëëÜ äßíåôáé ðñïôåñáéüôçôá óôïõò ÷ñÞóôåò ìå åñùôÞóåéò ãéá ôï
                &os;. Åßìáóôå êáëïß óôï íá óáò âïçèÞóïõìå íá êáôáëÜâåôå ôá
                âáóéêÜ, íá óáò äåßîïõìå ðïõ íá áíáôñÝîåôå óôï Åã÷åéñßäéï üðïôå
                ÷ñåéÜæåôáé, êáé íá óáò êáôåõèýíïõìå åêåß üðïõ ìðïñåßôå íá
                ìÜèåôå ðåñéóóüôåñá ãéá èÝìá ðïõ óáò áðáó÷ïëåß. Åßìáóôå êáôÜ
                âÜóç Áããëüöùíï êáíÜëé, áí êáé Ý÷ïõìå ÷ñÞóôåò áðü üëï ôïí
                êüóìï. Áí èÝëåôå íá ñùôÞóåôå óôç ìçôñéêÞ óáò ãëþóóá,
                ðñïóðáèÞóôå íá êÜíåôå ôçí åñþôçóç óôá ÁããëéêÜ êáé Ýðåéôá
                ìåôáêéíçèåßôå óå êÜðïéï Üëëï êáíÜëé
		##freebsd-<replaceable>lang</replaceable> áí ÷ñåéÜæåôáé. 
	      </para>
	    </listitem>

            <listitem>
              <para>Ôï êáíÜëé <literal>#FreeBSD</literal> óôï
                <ulink url="http://www.dal.net/">DALNET</ulink>
                åßíáé äéáèÝóéìï óôï <hostid>irc.dal.net</hostid> óôéò ÇÐÁ
                êáé óôï  <hostid>irc.eu.dal.net</hostid> óôçí Åõñþðç.</para>
            </listitem>

            <listitem>
              <para>Ôï êáíÜëé <literal>#FreeBSDHelp</literal> óôï
                <ulink url="http://www.dal.net/">DALNET</ulink>
                åßíáé äéáèÝóéìï óôï <hostid>irc.dal.net</hostid> óôéò ÇÐÁ
                êáé óôï <hostid>irc.eu.dal.net</hostid> óôçí Åõñþðç.</para>
            </listitem>

            <listitem>
              <para>Ôï êáíÜëé  <literal>#FreeBSD</literal> óôï
                <ulink url="http://www.undernet.org/">UNDERNET</ulink>
                åßíáé äéáèÝóéìï óôï <hostid>us.undernet.org</hostid>
                óôéò ÇÐÁ êáé óôï  <hostid>eu.undernet.org</hostid> óôçí
                Åõñþðç. Êáèþò åßíáé êáíÜëé âïÞèåéáò, èá ðñÝðåé íá åßóôå
                ðñïåôïéìáóìÝíïé íá äéáâÜóåôå ôá Ýããñáöá óôá ïðïßá èá óáò
                ðáñáðÝìøïõí.</para>
            </listitem>

	    <listitem>
	      <para>Ôï êáíÜëé <literal>#FreeBSD</literal> óôï
		<ulink url="http://www.rusnet.org.ru/">RUSNET</ulink>
                åßíáé ðñïóáíáôïëéóìÝíï óôç âïÞèåéá ÷ñçóôþí ôïõ &os; ðïõ
                ìéëïýí ôç ÑùóóóéêÞ ãëþóóá. Åßíáé åðßóçò Ýíá êáëü ìÝñïò ãéá
                ìç-ôå÷íéêÝò óõæçôÞóåéò.</para>
	    </listitem>

	    <listitem>
	      <para>Ôï êáíÜëé <literal>#BSDChat</literal> óôï
		<ulink url="http://www.ircnet.net/">IRCNET</ulink>
                åßíáé Ýíá êáíÜëé óå ðáñáäïóéáêÞ ÊéíåæéêÞ ãëþóóá, áöéåñùìÝíï
                óôç âïÞèåéá ÷ñçóôþí ôïõ &os;. Åßíáé åðßóçò Ýíá êáëü ìÝñïò ãéá
                ìç-ôå÷íéêÝò óõæçôÞóåéò.</para>
	    </listitem>
          </itemizedlist>

          <para>ÊÜèå Ýíá áðü áõôÜ ôá êáíÜëéá, åßíáé ÷ùñéóôü, êáé äåí
            äéáóõíäÝåôáé ìå ôá õðüëïéðá. Ôá óôõë ôçò óõæÞôçóçò äéáöÝñïõí,
            êáé ßóùò èá èÝëåôå íá äïêéìÜóåôå êáèÝíá ãéá íá âñåßôå êÜðïéï
            ðïõ íá ôáéñéÜæåé óôï äéêü óáò. ¼ðùò ìå <emphasis>êÜèå</emphasis>
            ôýðï óõæÞôçóçò óôï IRC, áí åßóôå áðü áõôïýò ðïõ ðñïóâÜëëïíôáé
            åýêïëá, Þ äåí ìðïñåßôå íá áíôéìåôùðßóåôå ðïëëïýò íÝïõò áíèñþðïõò
            (êáé áñêåôïýò ðéï ìåãÜëïõò) íá åðéäßäïíôáé óôï ëåêôéêü áíôßóôïé÷ï
            ôçò ðõãìá÷ßáò, ìçí áó÷ïëçèåßôå êáèüëïõ.</para>
        </answer>
      </qandaentry>

      <qandaentry>
	<question id="training">
	  <para>Ðïõ ìðïñþ íá âñù åðß ðëçñùìÞ õðïóôÞñéîç êáé åêðÜéäåõóç ãéá
            ôï &os;;</para>
	</question>

	<answer>
	  <para>Ôï DaemonNews ðáñÝ÷åé åðß ðëçñùìÞ åêðáßäåõóç êáé õðïóôÞñéîç
            ãéá ôï &os;. Ðåñéóóüôåñåò ðëçñïöïñßåò ìðïñåßôå íá âñåßôå óôçí
            äéêôõáêÞ ôïõò ôïðïèåóßá
	    <ulink url="http://www.bsdmall.com/">BSD Mall</ulink>.</para>

          <para>Ôï &os; Mall ðáñÝ÷åé åðßóçò åðß ðëçñùìÞ õðïóôÞñéîç ãéá ôï
            &os;. Ìðïñåßôå íá âñåßôå ðåñéóóüôåñåò ðëçñïöïñßåò óôçí
            <ulink url="http://www.freebsdmall.com/">äéêôõáêÞ ôïõò
            ôïðïèåóßá</ulink>.</para>

	  <para>ÏðïéïóäÞðïôå Üëëïò ïñãáíéóìüò ðáñÝ÷åé åêðáßäåõóç êáé
            õðïóôÞñéîç, èá ðñÝðåé íá åðéêïéíùíÞóåé ìå ôï Project ãéá íá
            êáôá÷ùñçèåß óôç ëßóôá áõôÞ.</para>
	</answer>
      </qandaentry>
    </qandaset>
  </chapter>

  <chapter
    id="install">
    <chapterinfo>
      <author>
	<firstname>Nik</firstname>
	<surname>Clayton</surname>
	<affiliation>
	  <address><email>nik@FreeBSD.org</email></address>
	</affiliation>
      </author>
    </chapterinfo>
    
    <title>ÅãêáôÜóôáóç</title>

    <qandaset>
      <qandaentry>
        <question id="floppy-download">
          <para>Which file do I download to get FreeBSD?</para>
        </question>

        <answer>
          <para>You need three floppy images:
	    <filename>floppies/boot.flp</filename>,
	    <filename>floppies/kern1.flp</filename>, and
            <filename>floppies/kern2.flp</filename>. These images need to
            be copied onto floppies by tools like
	    <command>fdimage</command> or &man.dd.1;.</para>

          <para>If you need to download the distributions yourself (for a
            DOS filesystem install, for instance), below are some
            recommendations for distributions to grab:</para>


          <itemizedlist>
            <listitem>
              <para>base/</para>
            </listitem>

            <listitem>
              <para>manpages/</para>
            </listitem>

            <listitem>
              <para>compat*/</para>
            </listitem>

            <listitem>
              <para>doc/</para>
            </listitem>

            <listitem>
              <para>src/ssys.*</para>
            </listitem>
          </itemizedlist>


          <para>Full instructions on this procedure and a little bit more
            about installation issues in general can be found in the
            <ulink url="&url.books.handbook;/install.html">Handbook entry on
            installing FreeBSD</ulink>.</para>

        </answer>
      </qandaentry>

      <qandaentry>
        <question id="floppy-image-too-large">
          <para>What do I do if the floppy images does not fit on a single
            floppy?</para>
        </question>

        <answer>
          <para>A 3.5 inch (1.44MB) floppy can accommodate 1474560 bytes
            of data. The boot image is exactly 1474560 bytes in size.</para>

          <para>Common mistakes when preparing the boot floppy are:</para>

          <itemizedlist>
            <listitem>
              <para>Not downloading the floppy image in
                <emphasis>binary</emphasis> mode when using
                <acronym>FTP</acronym>.</para>


              <para>Some FTP clients default their transfer mode to
                <emphasis>ascii</emphasis> and attempt to change any
                end-of-line characters received to match the conventions
                used by the client's system. This will almost invariably
                corrupt the boot image. Check the size of the downloaded
                boot image: if it is not <emphasis>exactly</emphasis> that
                on the server, then the download process is suspect.</para>

              <para>To workaround: type <emphasis>binary</emphasis> at the
                FTP command prompt after getting connected to the server
                and before starting the download of the image.</para>
            </listitem>

            <listitem>
              <para>Using the DOS <command>copy</command> command (or
                equivalent GUI tool) to transfer the boot image to
                floppy.</para>

              <para>Programs like <command>copy</command> will not work as
                the boot image has been created to be booted into directly.
                The image has the complete content of the floppy, track for
                track, and is not meant to be placed on the floppy as a
                regular file. You have to transfer it to the floppy
                <quote>raw</quote>, using the low-level tools (e.g.
                <command>fdimage</command> or <command>rawrite</command>)
                described in the <ulink
                url="&url.books.handbook;/install.html">installation guide to
                FreeBSD</ulink>.</para>
            </listitem>
          </itemizedlist>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="install-instructions-location">
          <para>Where are the instructions for installing FreeBSD?</para>
        </question>

        <answer>
          <para>Installation instructions can be found in the
            <ulink url="&url.books.handbook;/install.html">Handbook entry on installing FreeBSD</ulink>.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="need-to-run">
          <para>What do I need in order to run FreeBSD?</para>
        </question>

        <answer>
	  <para>For &os; 5.X and later you will need a 486 or better
            PC, with 24 MB or more of RAM and at least 150 MB of hard disk
            space.</para>

	  <para>All versions of &os; can run with a low
            end MDA graphics card but to run &xorg;, a VGA or better video
            card is needed.</para>

          <para>See also <xref linkend="hardware">.</para>

        </answer>
      </qandaentry>

      <qandaentry>
        <question id="custom-boot-floppy">
          <para>How can I make my own custom install floppy?</para>
        </question>

        <answer>
          <para>Currently there is no way to <emphasis>just</emphasis>
            make a custom install floppy. You have to cut a whole new
            release, which will include your install floppy.</para>

          <para>To make a custom release, follow the instructions in the
            <ulink url="&url.articles.releng;/article.html">Release
            Engineering</ulink> article.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="multiboot">
          <para>Can I have more than one operating system on my PC?</para>
        </question>

        <answer>
          <para>Have a look at
            <ulink url="&url.articles.multi-os;/index.html">
            the multi-OS page</ulink>.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="windows-coexist">
          <para>Can &windows; co-exist with FreeBSD?</para>
        </question>

        <answer>
          <para>Install &windows; first, then FreeBSD.
            FreeBSD's boot manager will then manage to boot &windows; and
            FreeBSD. If you install &windows; second, it will boorishly
            overwrite your boot manager without even asking. If that
            happens, see the next section.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="win95-damaged-boot-manager">
          <para>&windows; killed my boot manager!
            How do I get it back?</para>
        </question>

        <answer>
          <para>You can reinstall the boot manager FreeBSD comes with in
            one of three ways:</para>

          <itemizedlist>
            <listitem>
              <para>Running DOS, go into the tools/ directory of your
                FreeBSD distribution and look for
                <filename>bootinst.exe</filename>.  You run it like
                so:</para>

              <screen><prompt>...\TOOLS&gt;</prompt> <userinput>bootinst.exe boot.bin</userinput></screen>

              <para>and the boot manager will be reinstalled.</para>
            </listitem>

            <listitem>
              <para>Boot the FreeBSD boot floppy again and go to the
                Custom installation menu item. Choose Partition. Select the
                 drive which used to contain your boot manager (likely the
                 first one) and when you come to the partition editor for
                 it, as the very first thing (e.g. do not make any changes)
                 select (W)rite. This will ask for confirmation, say yes,
                 and when you get the Boot Manager selection prompt, be
                 sure to select <quote>Boot Manager</quote>. This will
                 re-write the boot manager to disk. Now quit out of the
                 installation menu and reboot off the hard disk as
                 normal.</para>
            </listitem>

            <listitem>
              <para>Boot the FreeBSD boot floppy (or CDROM) and choose the
                <quote>Fixit</quote> menu item. Select either the Fixit
                floppy or CDROM #2 (the <quote>live</quote> filesystem
                option) as appropriate and enter the fixit shell. Then
                execute the following command:</para>

              <screen><prompt>Fixit#</prompt> <userinput>fdisk -B -b /boot/boot0 <replaceable>bootdevice</replaceable></userinput></screen>

              <para>substituting <replaceable>bootdevice</replaceable> for
                your real
                boot device such as <devicename>ad0</devicename> (first IDE
                disk), <devicename>ad4</devicename> (first IDE disk on
                auxiliary controller), <devicename>da0</devicename> (first
                SCSI disk), etc.</para>
            </listitem>
          </itemizedlist>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="boot-on-thinkpad">
          <para>My A, T, or X series IBM Thinkpad locks up when I first
            booted up my FreeBSD installation.  How can I solve this?</para>
        </question>

        <answer>
          <para>A bug in early revisions of IBM's BIOS on these machines
            mistakenly identifies the FreeBSD partition as a potential FAT
            suspend-to-disk partition.  When the BIOS tries to parse the
            FreeBSD partition it hangs.</para>

          <para>According to IBM<footnote><para>In an e-mail from Keith
                Frechette
                <email>kfrechet@us.ibm.com</email>.</para></footnote>, the
            following model/BIOS release numbers incorporate the fix.</para>

          <informaltable frame="none" pgwide="1">
            <tgroup cols="2">
              <thead>
                <row>
                  <entry>Model</entry>
                  <entry>BIOS revision</entry>
                </row>
              </thead>

              <tbody>
                <row>
                  <entry>T20</entry>
                  <entry>IYET49WW or later</entry>
                </row>

                <row>
                  <entry>T21</entry>
                  <entry>KZET22WW or later</entry>
                </row>

                <row>
                  <entry>A20p</entry>
                  <entry>IVET62WW or later</entry>
                </row>

                <row>
                  <entry>A20m</entry>
                  <entry>IWET54WW or later</entry>
                </row>

                <row>
                  <entry>A21p</entry>
                  <entry>KYET27WW or later</entry>
                </row>

                <row>
                  <entry>A21m</entry>
                  <entry>KXET24WW or later</entry>
                </row>

                <row>
                  <entry>A21e</entry>
                  <entry>KUET30WW</entry>
                </row>
              </tbody>
            </tgroup>
          </informaltable>

	  <para>It has been reported that later IBM BIOS revisions may
	    have reintroduced the bug.  <ulink
	    url="http://docs.FreeBSD.org/cgi/mid.cgi?20010427133759.A71732">This
	    message</ulink> from Jacques Vidrine to the &a.mobile;
	    describes a procedure which may work if your newer IBM
	    laptop does not boot FreeBSD properly, and you can upgrade
	    or downgrade the BIOS.</para>
	
          <para>If you have an earlier BIOS, and upgrading is not an option, a
            workaround is to install FreeBSD, change the partition ID FreeBSD
            uses, and install new boot blocks that can handle the different
            partition ID.</para>

          <para>First, you will need to restore the machine to a state where
            it can get through its self-test screen.  Doing this requires
            powering up the machine without letting it find a FreeBSD
            partition on its primary disk.  One way is to remove the hard disk
            and temporarily move it to an older ThinkPad (such as a ThinkPad
            600) or a desktop PC with an appropriate conversion cable.  Once
            it is there, you can delete the FreeBSD partition and move the hard
            disk back.  The ThinkPad should now be in a bootable state
            again.</para>

          <para>With the machine functional again, you can use the workaround
            procedure described here to get a working FreeBSD
            installation.</para>

          <procedure>
            <step>
              <para>Download <filename>boot1</filename> and
                <filename>boot2</filename> from <ulink
                  url="http://people.FreeBSD.org/~bmah/ThinkPad/"></ulink>.
                Put these files somewhere you will be able to retrieve them
                later.</para>
            </step>

            <step>
              <para>Install FreeBSD as normal on to the ThinkPad.
                <emphasis>Do not</emphasis> use <literal>Dangerously
                  Dedicated</literal> mode.  <emphasis>Do not</emphasis>
                reboot when the install has finished.</para>
            </step>

            <step>
              <para>Either switch to the <quote>Emergency Holographic
                  Shell</quote> (<keycombo action="simul"><keycap>ALT</keycap>
                  <keycap>F4</keycap></keycombo>) or start a
                <quote>fixit</quote> shell.</para>
            </step>

            <step>
              <para>Use &man.fdisk.8; to change the FreeBSD partition ID from
                <literal>165</literal> to <literal>166</literal> (this is the
                  type used by OpenBSD).</para>
            </step>

            <step>
              <para>Bring the <filename>boot1</filename> and
                <filename>boot2</filename> files to the local
                filesystem.</para>
            </step>

            <step>
              <para>Use &man.disklabel.8; to write <filename>boot1</filename>
                and <filename>boot2</filename> to your FreeBSD slice.</para>

              <screen>&prompt.root; <userinput>disklabel -B -b boot1 -s boot2 ad0s<replaceable>n</replaceable></userinput></screen>

              <para><replaceable>n</replaceable> is the number of the slice
                where you installed FreeBSD.</para>
            </step>

            <step>
              <para>Reboot.  At the boot prompt you will be given the option
                of booting <literal>OpenBSD</literal>.  This will actually
                boot FreeBSD.</para>
            </step>
          </procedure>

          <para>Getting this to work in the case where you want to dual boot
          OpenBSD and FreeBSD on the same laptop is left as an exercise for
          the reader.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="install-bad-blocks">
          <para>Can I install on a disk with bad blocks?</para>
        </question>

        <answer>
          <para>You can, but it is a bad idea.</para>

	  <para>If you are seeing bad block errors with a modern IDE
            drive, chances are the drive is going to die very soon (the
            drive's internal remapping functions are no longer sufficient
            to fix the bad blocks, which means the disk is heavily
            corrupted); we suggest you buy a new hard drive.</para>

          <para>If you have a SCSI drive with bad blocks, see
            <link linkend="awre">this answer</link>.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="boot-floppy-strangeness">
          <para>Strange things happen when I boot the install floppy!
            What is happening?</para>
        </question>

        <answer>
          <para>If you are seeing things like the machine grinding to a halt
            or spontaneously rebooting when you try to boot the install
            floppy, here are three questions to ask yourself:-</para>

          <orderedlist>
            <listitem>
              <para>Did you use a new, freshly-formatted, error-free floppy
                (preferably a brand-new one straight out of the box, as
                opposed to the magazine cover disk that has been lying under
                the bed for the last three years)?</para>
            </listitem>

            <listitem>
              <para>Did you download the floppy image in binary (or image)
                mode? (do not be embarrassed, even the best of us have
                accidentally downloaded a binary file in ASCII mode at
                least once!)</para>
            </listitem>

            <listitem>
              <para>If you are using &windows; 95 or 98 did you run
                <command>fdimage</command> or
                <command>rawrite</command> in pure DOS mode? These
                operating systems can interfere with programs that
                write directly to hardware, which the disk creation
                program does; even running it inside a DOS shell in
                the GUI can cause this problem.</para>
            </listitem>
          </orderedlist>

          <para>There have also been reports of &netscape; causing problems
            when downloading the boot floppy, so it is probably best to use
            a different FTP client if you can.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="no-install-cdrom">
          <para>I booted from my ATAPI CDROM, but the install program
            says no CDROM is found.  Where did it go?</para>
        </question>

        <answer>
          <para>The usual cause of this problem is a mis-configured CDROM
            drive.  Many PCs now ship with the CDROM as the slave device on
            the secondary IDE controller, with no master device on that
            controller.  This is illegal according to the ATAPI specification,
            but &windows; plays fast and loose with the specification, and the
            BIOS ignores it when booting.  This is why the BIOS was able to
            see the  CDROM to boot from it, but why FreeBSD cannot see it to
            complete  the install.</para>

          <para>Reconfigure your system so that the CDROM is either the
            master device on the IDE controller it is attached to, or make
            sure that it is the slave on an IDE controller that also has a
            master device.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="install-PLIP">
          <para>Can I install on my laptop over PLIP (Parallel Line
            IP)?</para>
        </question>

        <answer>
          <para>Yes. Use a standard Laplink cable. If necessary, you
            can check out the <ulink url="&url.books.handbook;/network-plip.html">PLIP
            section of the Handbook</ulink> for details on parallel
            port networking.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="geometry">
          <para>Which geometry should I use for a disk drive?</para>
        </question>

        <answer>
            <note>
              <para>By the <quote>geometry</quote> of a disk, we mean
              the number of cylinders, heads and sectors/track on a
              disk.  We will refer to this as C/H/S for
              convenience. This is how the PC's BIOS works out which
              area on a disk to read/write from.</para>
            </note>

          <para>This causes a lot of confusion among new system
            administrators.  First of all, the
            <emphasis>physical</emphasis> geometry of a SCSI drive is
            totally irrelevant, as FreeBSD works in term of disk
            blocks. In fact, there is no such thing as
            <quote>the</quote> physical geometry, as the sector
            density varies across the disk.  What manufacturers claim
            is the <quote>physical geometry</quote> is usually the
            geometry that they have determined wastes the least
            space. For IDE disks, FreeBSD does work in terms of C/H/S,
            but all modern drives internally convert this into block
            references.</para>

          <para>All that matters is the <emphasis>logical</emphasis>
            geometry.  This is the answer that the BIOS gets when it
            asks the drive <quote>what is your geometry?</quote> It
            then uses this geometry to access the disk. As FreeBSD
            uses the BIOS when booting, it is very important to get
            this right. In particular, if you have more than one
            operating system on a disk, they must all agree on the
            geometry.  Otherwise you will have serious problems
            booting!</para>

          <para>For SCSI disks, the geometry to use depends on whether
           extended translation support is turned on in your
           controller (this is often referred to as <quote>support for
           DOS disks &gt;1GB</quote> or something similar). If it is
           turned off, then use <replaceable>N</replaceable>
           cylinders, 64 heads and 32 sectors/track, where
           <replaceable>N</replaceable> is the capacity of the disk in
           MB. For example, a 2GB disk should pretend to have 2048
           cylinders, 64 heads and 32 sectors/track.</para>

          <para>If it <emphasis>is</emphasis> turned on (it is often
            supplied this way to get around certain limitations in
            &ms-dos;) and the disk capacity is more than 1GB, use M
            cylinders, 63 sectors per track (<emphasis>not</emphasis>
            64), and 255 heads, where <literal>M</literal> is the disk capacity in MB
            divided by 7.844238 (!). So our example 2GB drive would
            have 261 cylinders, 63 sectors per track and 255
            heads.</para>

          <para>If you are not sure about this, or FreeBSD fails to
            detect the geometry correctly during installation, the
            simplest way around this is usually to create a small DOS
            partition on the disk. The BIOS should then detect the
            correct geometry, and you can always remove the DOS
            partition in the partition editor if you do not want to
            keep it.  You might want to leave it around for
            programming network cards and the like, however.</para>

          <para>Alternatively, there is a freely available utility
            distributed with FreeBSD called
            <filename>pfdisk.exe</filename>.  You can find it in the
            <filename>tools</filename> subdirectory on the FreeBSD
            CDROM or on the various FreeBSD FTP sites.  This program
            can be used to work out what geometry the other operating
            systems on the disk are using. You can then enter this
            geometry in the partition editor.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="disk-divide-restrictions">
          <para>Are there any restrictions on how I divide the disk up?</para>
        </question>

        <answer>
          <para>Yes. You must make sure that your root partition is below 1024
            cylinders so the BIOS can boot the kernel from it.  (Note that
            this is a limitation in the PC's BIOS, not FreeBSD).</para>

          <para>For a SCSI drive, this will normally imply that the root
            partition will be in the first 1024MB (or in the first 4096MB
            if extended translation is turned on - see previous question).
            For IDE, the corresponding figure is 504MB.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="disk-manager">
          <para>Is FreeBSD compatible with any disk managers?</para>
        </question>

        <answer>
          <para>FreeBSD recognizes the Ontrack Disk Manager and makes
            allowances for it. Other disk managers are not supported.</para>

          <para>If you just want to use the disk with FreeBSD you do not
            need a disk manager. Just configure the disk for as much space
            as the BIOS can deal with (usually 504 megabytes), and FreeBSD
            should figure out how much space you really have. If you are
            using an old disk with an MFM controller, you may need to
            explicitly tell FreeBSD how many cylinders to use.</para>

          <para>If you want to use the disk with FreeBSD and another
            operating system, you may be able to do without a disk manager:
            just make sure the FreeBSD boot partition and the slice for
            the other operating system are in the first 1024 cylinders. If
            you are reasonably careful, a 20 megabyte boot partition should
            be plenty.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="missing-os">
          <para>When I boot FreeBSD for the first time after install I get <errorname>Missing Operating
            System</errorname>.  What is happening?</para>
        </question>

        <answer>
          <para>This is classically a case of FreeBSD and DOS or some other
            OS conflicting over their ideas of disk <link
            linkend="geometry">geometry</link>. You will have to reinstall
            FreeBSD, but obeying the instructions given above will almost
            always get you going.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="stop-at-boot-manager">
          <para>Why can I not get past the boot manager's <prompt>F?</prompt>
            prompt?</para>
        </question>

        <answer>
          <para>This is another symptom of the problem described in the
            preceding question. Your BIOS geometry and FreeBSD geometry
            settings do not agree! If your controller or BIOS supports
            cylinder translation (often marked as <quote>&gt;1GB drive
            support</quote>), try toggling its setting and reinstalling
            FreeBSD.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="need-complete-sources">
          <para>Do I need to install the complete sources?</para>
        </question>

        <answer>
          <para>In general, no.  However, we would strongly recommend that
            you install, at a minimum, the <literal>base</literal> source
            kit, which includes several of the files mentioned here, and
            the <literal>sys</literal> (kernel) source kit, which includes
            sources for the kernel. There is nothing in the system which
            requires the presence of the sources to operate, however,
            except for the kernel-configuration program &man.config.8;.
            With the exception of the kernel sources, our build structure
            is set up so that you can read-only mount the sources from
            elsewhere via NFS and still be able to make new binaries
            (due to the kernel-source restriction, we recommend that
            you not mount this on <filename>/usr/src</filename> directly,
            but rather in some other location with appropriate symbolic
            links to duplicate the top-level structure of the source
            tree).</para>

          <para>Having the sources on-line and knowing how to build a
            system with them will make it much easier for you to upgrade
            to future releases of FreeBSD.</para>

          <para>To actually select a subset of the sources, use the Custom
            menu item when you are in the Distributions menu of the
            system installation tool.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="need-kernel">
          <para>Do I need to build a kernel?</para>
        </question>

        <answer>
          <para>Building a new kernel was originally pretty much a required
            step in a FreeBSD installation, but more recent releases have
            benefited from the introduction of much friendlier kernel
	    configuration methods.  In &os; 5.X and later, it is very easily
	    to configure the kernel's configuration by much more flexible 
	    "hints" which can be set from the loader prompt.</para>

          <para>It may still be worthwhile building a new
            kernel containing just the drivers that you need, just to save a
            bit of RAM, but it is no longer necessary for most
            systems.</para>

        </answer>
      </qandaentry>

      <qandaentry>
        <question id="password-encryption">
          <para>Should I use DES, Blowfish, or MD5 passwords and how
            do I specify which form my users receive?</para>
        </question>

        <answer>
          <para>The default password format on FreeBSD is to use
            <emphasis>MD5</emphasis>-based passwords. These are
            believed to be more secure than the traditional &unix;
            password format, which used a scheme based on the
            <emphasis>DES</emphasis> algorithm.  DES passwords are
            still available if you need to share your password file
            with legacy operating systems which still use the less
            secure password format (they are available if you choose
            to install the <quote>crypto</quote> distribution in
            sysinstall, or by installing the crypto sources if
            building from source). Installing the crypto libraries
            will also allow you to use the Blowfish password format,
            which is more secure.  Which password format to use for
            new passwords is controlled by the
            <quote>passwd_format</quote> login capability in
            <filename>/etc/login.conf</filename>, which takes values
            of <quote>des</quote>, <quote>blf</quote> (if these are
            available) or <quote>md5</quote>.  See the
            &man.login.conf.5; manual page for more information about
            login capabilities.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="boot-floppy-hangs">
          <para>Why does the boot floppy start, but hang at the
            <literal>Probing Devices...</literal> screen?</para>
        </question>

        <answer>

          <para>If you have a IDE &iomegazip; or &jaz; drive installed, remove it
            and try again. The boot floppy can get confused by the drives.
            After the system is installed you can reconnect the drive.
            Hopefully this will be fixed in a later release.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="panic-on-install-reboot">
          <para>Why do I get a <errorname>panic: can't mount root</errorname>
            error when rebooting the system after installation?</para>
        </question>

        <answer>
          <para>This error comes from confusion between the boot
            block's and the kernel's understanding of the disk
            devices. The error usually manifests on two-disk IDE
            systems, with the hard disks arranged as the master or
            single device on separate IDE controllers, with FreeBSD
            installed on the secondary IDE controller. The boot blocks
            think the system is installed on ad0 (the second BIOS
            disk) while the kernel assigns the first disk on the
            secondary controller device, ad2. After the device
            probing, the kernel tries to mount what the boot blocks
            think is the boot disk, ad0, while it is really ad2, and
            fails.</para>

          <para>To fix the problem, do one of the following:</para>

            <orderedlist>
              <listitem>
                <para>Reboot the system and hit <keycap>Enter</keycap>
                  at the <literal>Booting kernel in 10 seconds; hit
                  [Enter] to interrupt</literal> prompt.  This will
                  drop you into the boot loader.</para>

                <para>Then type
                  <literal>
                  set
                  root_disk_unit="<replaceable>disk_number</replaceable>"
                  </literal>. <replaceable>disk_number</replaceable>
                  will be <literal>0</literal> if FreeBSD is installed
                  on the master drive on the first IDE controller,
                  <literal>1</literal> if it is installed on the slave
                  on the first IDE controller, <literal>2</literal> if
                  it is installed on the master of the second IDE
                  controller, and <literal>3</literal> if it is
                  installed on the slave of the second IDE
                  controller.</para>

                <para>Then type <literal>boot</literal>, and your
                  system should boot correctly.</para>

                <para>To make this change permanent (i.e, so you do not
                  have to do this every time you reboot or turn on
                  your FreeBSD machine), put the line <literal>
                  root_disk_unit="<replaceable>disk_number</replaceable>"</literal>
                  in <filename>/boot/loader.conf.local
                  </filename>.</para>
              </listitem>

              <listitem>
                <para>Move the FreeBSD disk onto the primary IDE
                  controller, so the hard disks are
                  consecutive.</para>
              </listitem>
            </orderedlist>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="memory-limits">
          <para>What are the limits for memory?</para>
        </question>

        <answer>
          <para>The limit is 4 gigabytes on a standard &i386; install.
            Beginning with &os; versions 4.9 and 5.1, more memory can be
            supported through &man.pae.4;.  This does require a kernel
            recompile, with an extra option to enable PAE:</para>

            <programlisting>options       PAE</programlisting>

          <para>&os;/pc98 has a limit of 4 GB memory, and PAE can not
            be used with it.  On &os;/alpha, the limit on memory depends
            on the type of hardware in use - consult the Alpha Hardware
            Release Notes for details.  Other architectures
            supported by &os; have much higher theoretical limits on
            maximum memory (many terabytes).</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="ffs-limits">
          <para>What are the limits for ffs filesystems?</para>
        </question>

        <answer>
          <para>For ffs filesystems, the maximum theoretical limit is 8
            terabytes (2G blocks), or 16TB for the default block size of
            8K. In practice, there is a soft limit of 1 terabyte, but with
            modifications filesystems with 4 terabytes are possible (and
            exist).</para>

          <para>The maximum size of a single ffs file is approximately 1G
            blocks, or 4TB with a block size of 4K.</para>

          <table>
            <title>Maximum file sizes</title>

            <tgroup cols="3">
              <thead>
                <row>
                  <entry>fs block size</entry>

                  <entry>works</entry>

                  <entry>should work</entry>
                </row>
              </thead>

              <tbody>
                <row>
                  <entry>4K</entry>

                  <entry>4T-1</entry>

                  <entry>&gt;4T</entry>
                </row>

                <row>
                  <entry>8K</entry>

                  <entry>&gt;32G</entry>

                  <entry>32T-1</entry>
                </row>

                <row>
                  <entry>16K</entry>

                  <entry>&gt;128G</entry>

                  <entry>32T-1</entry>
                </row>

                <row>
                  <entry>32K</entry>

                  <entry>&gt;512G</entry>

                  <entry>64T-1</entry>
                </row>

                <row>
                  <entry>64K</entry>

                  <entry>&gt;2048G</entry>

                  <entry>128T-1</entry>
                </row>
              </tbody>
            </tgroup>
          </table>

          <para>When the fs block size is 4K, triple indirect blocks work
            and everything should be limited by the maximum fs block number
            that can be represented using triple indirect blocks (approx.
            1K^3 + 1K^2 + 1K), but everything is limited by a (wrong) limit
            of 1G-1 on fs block numbers. The limit on fs block numbers
            should be 2G-1. There are some bugs for fs block numbers near
            2G-1, but such block numbers are unreachable when the fs block
            size is 4K.</para>

          <para>For block sizes of 8K and larger, everything should be
            limited by the 2G-1 limit on fs block numbers, but is
            actually limited by the 1G-1 limit on fs block numbers.
            Using the correct limit of 2G-1 blocks does cause
            problems.</para>

        </answer>
      </qandaentry>

      <qandaentry>
        <question id="archsw-readin-failed-error">
          <para>Why do I get an error message,
            <errorname>archsw.readin.failed</errorname> after compiling
            and booting a new kernel?</para>
        </question>

        <answer>
          <para>Because your world and kernel are out of sync.  This
            is not supported.  Be sure you use <command>make
            buildworld</command> and <command>make
            buildkernel</command> to update your kernel.</para>

	  <para>You can boot by specifying the kernel directly at the
            second stage, pressing any key when the | shows up before
            loader is started.</para>
        </answer>
      </qandaentry>

      <qandaentry>
	<question id="boot-acpi">
	  <para>Installation crashes while booting, what can I do?</para>
	</question>

	<answer>
	  <para>Try disabling ACPI support.  When the bootloader loads, press
	    the space key.  The system displays <screen>OK</screen>.  Type
	    <screen><userinput>unset acpi_load</userinput></screen> and then
	    <screen><userinput>boot</userinput></screen>.</para>
	</answer>
      </qandaentry>

    </qandaset>
  </chapter>

  <chapter
    id="hardware">
    <title>Óõìâáôüôçôá Õëéêïý</title>

      <sect1 id="compatibility-general">
	<title>ÃåíéêÜ</title>

    <qandaset>
      <qandaentry>
        <question id="which-hardware-to-get">
          <para>I want to get a piece of hardware for my FreeBSD
            system.  Which model/brand/type is best?</para>
        </question>

        <answer>
          <para>This is discussed continually on the FreeBSD mailing
            lists.  Since hardware changes so quickly, however, we
            expect this.  We <emphasis>still</emphasis> strongly
            recommend that you read through the Hardware notes for &os;
	    <ulink url="&rel.current.hardware;">&rel.current;</ulink>
	    or
	    <ulink url="&rel2.current.hardware;">&rel2.current;</ulink>
	    and search the mailing list
            <ulink url="http://www.FreeBSD.org/search/#mailinglists">
            archives</ulink> before asking about the latest and
            greatest hardware.  Chances are a discussion about the
            type of hardware you are looking for took place just last
            week.</para>

          <para>If you are looking for a laptop, check the
            FreeBSD-mobile mailing list archives.  Otherwise, you
            probably want the archives for FreeBSD-questions, or
            possibly a specific mailing list for a particular hardware
            type.</para>
        </answer>
      </qandaentry>

    </qandaset>
      </sect1>

      <sect1 id="compatibility-processors">
	<title>Áñ÷éôåêôïíéêÝò êáé ÅðåîåñãáóôÝò</title>

    <qandaset>
      <qandaentry>
        <question id="architectures">
          <para>Does FreeBSD support architectures other than the x86?</para>
        </question>

        <answer>

          <para>Yes.  FreeBSD currently runs on the Intel x86 and DEC
            (now Compaq) Alpha architectures.  As of FreeBSD 5.0, the
            AMD64 and Intel EM64T, IA-64, and &sparc64; architectures
            are also supported.  Upcoming platforms are &mips; and
            &powerpc;, join the &a.ppc; or the &a.mips; respectively
            for more information about ongoing work on these
            platforms.  For general discussion on new architectures,
            join the &a.platforms;.</para>

          <para>If your machine has a different architecture and you
            need something right now, we suggest you look at <ulink
            url="http://www.netbsd.org/">NetBSD</ulink> or <ulink
            url="http://www.openbsd.org/">OpenBSD</ulink>.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="smp-support">
          <para>Does FreeBSD support Symmetric Multiprocessing
            (SMP)?</para>
        </question>

        <answer>
          <para>Yes.  SMP was enabled by default in the
            <emphasis>GENERIC</emphasis> kernel as of &os; 5.2.</para>

          <para>The intention was also to enable it by default for
	    the &os; 5.3 release, but problems running the SMP kernel
	    on certain UP machines led to the decision to disable it
	    until those problems can be addressed.  This is a priority
	    for &os; 5.4.</para>
        </answer>
      </qandaentry>
        </qandaset>
      </sect1>

      <sect1 id="compatibility-drives">
	<title>Óêëçñïß äßóêïé, ìïíÜäåò ôáéíßáò, ïäçãïß CD êáé DVD</title>

	<qandaset>

      <qandaentry>
        <question id="supported-hard-drives">
          <para>What kind of hard drives does FreeBSD support?</para>
        </question>

        <answer>
	  <para>FreeBSD supports EIDE, SATA, SCSI, and SAS drives (with a 
	    compatible controller; see the next section), and all drives using
	    the original <quote>Western Digital</quote> interface (MFM, RLL,
            ESDI, and of course IDE). A few ESDI controllers that use
            proprietary interfaces may not work: stick to WD1002/3/6/7
            interfaces and clones.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="supported-scsi-controllers">
          <para>Which SCSI or SAS controllers are supported?</para>
        </question>

        <answer>
          <para>See the complete list in the Hardware Notes for &os;
	    <ulink url="&rel.current.hardware;">&rel.current;</ulink> or
	    <ulink url="&rel2.current.hardware;">&rel2.current;</ulink>.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="tape-support">
          <para>What types of tape drives are supported?</para>
        </question>

        <answer>

          <para>FreeBSD supports SCSI and QIC-36 (with a QIC-02 interface).
            This includes 8-mm (aka Exabyte) and DAT drives.</para>

          <para>Some of the early 8-mm drives are not quite compatible
          with SCSI-2, and may not work well with FreeBSD.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="tape-changer-support">
          <para>Does FreeBSD support tape changers?</para>
        </question>

        <answer>
          <para>FreeBSD supports SCSI changers using the &man.ch.4;
            device and the &man.chio.1; command. The details of how you
            actually control the changer can be found in the &man.chio.1;
            manual page.</para>

          <para>If you are not using <application>AMANDA</application>
            or some other product that already understands changers,
            remember that they only know how to move a tape from one
            point to another, so you need to keep track of which slot a
            tape is in, and which slot the tape currently in the drive
            needs to go back to.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="supported-cdrom-drives">
          <para>Which CDROM drives are supported by FreeBSD?</para>
        </question>

        <answer>
          <para>Any SCSI drive connected to a supported controller is
            supported.</para>

          <para>The following proprietary CDROM interfaces are also
            supported:</para>

            <itemizedlist>
              <listitem>
                <para>Mitsumi LU002 (8bit), LU005 (16bit) and FX001D
                  (16bit 2x Speed).</para>
              </listitem>

              <listitem>
                <para>Sony CDU 31/33A</para>
              </listitem>

              <listitem>
                <para>Sound Blaster Non-SCSI CDROM</para>
              </listitem>

              <listitem>
                <para>Matsushita/Panasonic CDROM</para>
              </listitem>

              <listitem>
                <para>ATAPI compatible IDE CDROMs</para>
              </listitem>
            </itemizedlist>

          <para>All non-SCSI cards are known to be extremely slow compared
            to SCSI drives, and some ATAPI CDROMs may not work.</para>

          <para>The official FreeBSD CDROM ISO, and CDROMs from Daemon
            News and FreeBSD Mall, support booting directly from the
            CD.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="supported-cdrw-drives">
          <para>Which CD-RW drives are supported by FreeBSD?</para>
        </question>

	<answer>
	  <para>FreeBSD supports any ATAPI-compatible IDE CD-R or CD-RW
	    drive.  See &man.burncd.8; for details.</para>

	  <para>FreeBSD also supports any SCSI CD-R or CD-RW drives.
	    Install and use the <command>cdrecord</command> command from the
	    ports or packages system, and make sure that you have the
	    <devicename>pass</devicename> device compiled in your
	    kernel.</para>
	</answer>
      </qandaentry>

      <qandaentry>
        <question id="zip-support">
          <para>Does FreeBSD support &iomegazip; drives?</para>
        </question>

        <answer>
          <para>FreeBSD supports SCSI and ATAPI (IDE) &iomegazip; drives out
            of the box. SCSI ZIP drives can only be set to
            run at SCSI target IDs 5 or 6, but if your SCSI host
            adapter's BIOS supports it you can even boot from it.  It
            is not clear which host adapters support booting from
            targets other than 0 or 1, so you will have to consult
            your adapter's documentation if you would like to use this
            feature.</para>

          <para>FreeBSD also supports Parallel Port Zip Drives.  Check
            that your kernel contains the
            <devicename>scbus0</devicename>,
            <devicename>da0</devicename>,
            <devicename>ppbus0</devicename>, and
            <devicename>vp0</devicename> drivers (the GENERIC kernel
            contains everything except
            <devicename>vp0</devicename>). With all these drivers
            present, the Parallel Port drive should be available as
            <devicename>/dev/da0s4</devicename>. Disks can be mounted
            using <command>mount /dev/da0s4 /mnt</command> OR (for dos
            disks) <command>mount_msdos /dev/da0s4 /mnt</command> as
            appropriate.</para>

          <para>Also check out <link linkend="media-change">the FAQ on
            removable drives</link> later in this chapter, and <link
            linkend="removable-drives">the note on
            <quote>formatting</quote></link>in the Administration
            chapter.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="jaz-zip-removable-support">
          <para>Does FreeBSD support &jaz;, EZ and other removable
            drives?</para>
        </question>

        <answer>
          <para>They work.  Most of these are SCSI devices, so they
            look like SCSI disks to FreeBSD.  The IDE EZ looks like an
            IDE drive.</para>

	  <para>Make sure that any external units are powered on when
            booting the system.</para>

          <para><anchor id="media-change">To change the media while
            running, check out &man.mount.8;, &man.umount.8;, and
            &man.camcontrol.8; (for SCSI devices) or
            &man.atacontrol.8; (for IDE devices), plus the <link
            linkend="removable-drives">discussion on using removable
            drives</link> later in the FAQ.</para>
        </answer>
      </qandaentry>

	</qandaset>

      </sect1>

      <sect1 id="compatibility-kbd-mice">
	<title>Ðëçêôñïëüãéá êáé ðïíôßêéá</title>

	<qandaset>

      <qandaentry>
        <question id="usbkbd">
          <para>Does FreeBSD support my USB keyboard?</para>
        </question>

        <answer>
          <para>FreeBSD supports USB keyboards
            out-of-the-box.  Enable USB support in
            <filename>/etc/rc.conf</filename>.</para>

          <para>Once you have USB keyboard support enabled on your
            system, the AT keyboard becomes
            <devicename>/dev/kbd0</devicename> and the USB keyboard
            becomes <devicename>/dev/kbd1</devicename>, if both are
            connected to the system.  If there is the USB keyboard
            only, it will be
            <devicename>/dev/ukbd0</devicename>.</para>

          <para>If you want to use the USB keyboard in the console,
            you have to explicitly tell the console driver to use the
            existing USB keyboard. This can be done by running the
            following command as a part of system
            initialization.</para>

          <screen>&prompt.root; <userinput>kbdcontrol -k /dev/kbd1 &lt; /dev/ttyv0 &gt; /dev/null</userinput></screen>

          <para>Note that if the USB keyboard is the only keyboard, it
            is accessed as <devicename>/dev/ukbd0</devicename>, thus,
            the command should look like:</para>

          <screen>&prompt.root; <userinput>kbdcontrol -k /dev/ukbd0 &lt; /dev/ttyv0 &gt; /dev/null</userinput></screen>

          <para><filename>/etc/rc.i386</filename> is a good place to
            add the above command.</para>

          <para>Once this is done, the USB keyboard should work in the
            X environment as well without any special settings.</para>

          <para>Hot-plugging and unplugging of the USB keyboard may
            not work quite right yet. We recommend connecting the
            keyboard before starting the system and leaving it
            connected until the system is shutdown to avoid
            troubles.</para>

          <para>See the &man.ukbd.4; manual page for more information.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="busmouse">
          <para>I have an unusual bus mouse. How do I set it
            up?</para>
        </question>

        <answer>
          <para>FreeBSD supports the bus mouse and the InPort bus
            mouse from such manufacturers as Microsoft, Logitech and
            ATI. The GENERIC kernel does not include the device
            driver.  To build a custom kernel with the bus mouse
            driver, add the following line to the kernel config
            file:</para>

          <programlisting>device mse0 at isa? port 0x23c irq5</programlisting>

          <para>Bus mice usually come with dedicated interface cards.
            These cards may allow you to set the port address and the
            IRQ number other than shown above. Refer to the manual of
            your mouse and the &man.mse.4; manual page for more
            information.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="ps2mouse">
          <para>How do I use my PS/2 (<quote>mouse port</quote> or
            <quote>keyboard</quote>) mouse?</para>
        </question>

        <answer>
          <para>The PS/2 mouse is supported out-of-the-box.  The
             necessary device driver, <devicename>psm</devicename>, is
             included in the kernel.</para>

          <para>If your custom kernel does not have this, add the
            following line to your kernel configuration and compile a
            new kernel.</para>

          <programlisting>device psm0 at atkbdc? irq 12</programlisting>

          <para>Once the kernel detects <devicename>psm0</devicename>
            correctly at boot time, make sure that an entry for
            <devicename>psm0</devicename> exists in
            <filename>/dev</filename>.  You can create this entry by
            typing:</para>

          <screen>&prompt.root; <userinput>cd /dev; sh MAKEDEV psm0</userinput></screen>

          <para>when logged in as <username>root</username>.</para>

          <note>
	    <para>You can omit this step if you are running FreeBSD
	      5.0-RELEASE or newer with &man.devfs.5; enabled,
	      since the proper device nodes will be created automatically
	      under <filename>/dev</filename>.</para>
	  </note>
	</answer>
      </qandaentry>

      <qandaentry>
        <question id="moused">
          <para>Is it possible to use a mouse in any way outside the X
            Window system?</para>
        </question>

        <answer>
          <para>If you are using the default console driver,
            &man.syscons.4;, you can use a mouse pointer in text
            consoles to cut &amp; paste text. Run the mouse daemon,
            &man.moused.8;, and turn on the mouse pointer in the
            virtual console:</para>

          <screen>&prompt.root; <userinput>moused -p /dev/<replaceable>xxxx</replaceable> -t <replaceable>yyyy</replaceable></userinput>
&prompt.root; <userinput>vidcontrol -m on</userinput></screen>

          <para>Where <replaceable>xxxx</replaceable> is the mouse
            device name and <replaceable>yyyy</replaceable> is a
            protocol type for the mouse.  The mouse daemon can
            automatically determine the protocol type of most
            mice, except old serial mice. Specify the
            <literal>auto</literal> protocol to invoke automatic
            detection.  If automatic detection does not work, see the
            &man.moused.8; manual page for a list of supported
            protocol types.</para>

          <para>If you have a PS/2 mouse, just add
            <literal>moused_enable="YES"</literal> to
            <filename>/etc/rc.conf</filename> to start the mouse
            daemon at boot-time.  Additionally, if you would like to
            use the mouse daemon on all virtual terminals instead of
            just the console, add <literal>allscreens_flags="-m
            on"</literal> to <filename>/etc/rc.conf</filename>.</para>

          <para>When the mouse daemon is running, access to the mouse
            must be coordinated between the mouse daemon and other
            programs such as X Windows. Refer to the FAQ <link
            linkend="x-and-moused">Why does my mouse not work with
            X?</link> for more details on this issue.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="text-mode-cut-paste">
          <para>How do I cut and paste text with a mouse in the text
            console?</para>
        </question>

        <answer>
          <para>Once you get the mouse daemon running (see the <link
            linkend="moused">previous section</link>), hold down the
            button 1 (left button) and move the mouse to select a
            region of text. Then, press the button 2 (middle button)
            to paste it at the text cursor.  Pressing button 3 (right
            button) will <quote>extend</quote> the selected region of
            text.</para>

	  <para>If your mouse does not have a middle button, you may
            wish to emulate one or remap buttons using mouse daemon
            options. See the &man.moused.8; manual page for
            details.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="mouse-wheel-buttons">
          <para>My mouse has a fancy wheel and buttons.  Can I use them in
            FreeBSD?</para>
        </question>

        <answer>
          <para>The answer is, unfortunately, <quote>It depends</quote>.
            These mice with additional features require specialized driver
            in most cases. Unless the mouse device driver or the user
            program has specific support for the mouse, it will act just
            like a standard two, or three button mouse.</para>

          <para>For the possible usage of wheels in the X Window
            environment, refer to <link linkend="x-and-wheel">that
            section</link>.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="laptop-mouse-trackball">
          <para>How do I use the mouse/trackball/touchpad on my laptop?</para>
        </question>

        <answer>
          <para>Please refer to <link linkend="ps2mouse">the answer to
            the previous question</link>.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="keyboard-delete-key">
          <para>How do I use my delete key in <command>sh</command> and
            <command>csh</command>?</para>
        </question>

        <answer>
	  <para>For the <application>Bourne Shell</application>, add the
	    following lines to your <filename>.shrc</filename>.  See &man.sh.1;
	    and &man.editrc.5;.</para>

	  <programlisting>bind ^? ed-delete-next-char # for console
bind ^[[3~ ed-delete-next-char # for xterm</programlisting>

	  <para>For the <application>C Shell</application>, add the following
	    lines to your <filename>.cshrc</filename>.  See &man.csh.1;.</para>

	  <programlisting>bindkey ^? delete-char # for console
bindkey ^[[3~ delete-char # for xterm</programlisting>

	  <para>For more information, see <ulink
	      url="http://www.ibb.net/~anne/keyboard.html">this page</ulink>.
          </para>
        </answer>
      </qandaentry>

	</qandaset>

      </sect1>

      <sect1 id="compatibility-networking">
	<title>ÓõóêåõÝò óåéñéáêÞò åðéêïéíùíßáò êáé Äéêôýùóçò</title>

	<qandaset>

      <qandaentry>
        <question id="network-cards">
          <para>Which network cards does FreeBSD support?</para>
        </question>

        <answer>
          <para>See the Hardware Notes supplied with each release of
            FreeBSD for a more
            complete list.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="support-winmodem">
          <para>Does FreeBSD support software modems, such as Winmodems?</para>
        </question>

        <answer>
          <para>FreeBSD supports many software modems via add-on
            software.  The <filename role="package">comms/ltmdm</filename> port adds
            support for modems based on the very popular Lucent LT
            chipset.  The <filename role="package">comms/mwavem</filename> port
            supports the modem in IBM Thinkpad 600 and 700
            laptops.</para>

          <para>You cannot install FreeBSD via a software modem; this
            software must be installed after the OS is
            installed.</para>
        </answer>
      </qandaentry>

      <qandaentry>
	<question id="support-broadcom">
	  <para>Is there a native driver for the Broadcom 43xx cards?</para>
	</question>

	<answer>
	  <para>No, and there is not likely to be.</para>

	  <para>Broadcom refuses to publically release programming
	    information for their wireless chipsets, most likely because
	    they use software controlled radios.  In order to get FCC type
	    acceptance for their parts, they have to ensure that users
	    cannot arbitrarily set things like operating frequencies,
	    modulation parameters and power output.  But without knowing
	    how to program the chipsets, it is nearly impossible to write
	    a driver.</para>
	</answer>
      </qandaentry>

      <qandaentry>
        <question id="multiport-serial-support">
          <para>Which multi-port serial cards are supported by
            FreeBSD?</para>
        </question>

        <answer>
          <para>There is a list of these in the <ulink
            url="&url.books.handbook;/install.html#INSTALL-MISC">Miscellaneous
            devices</ulink> section of the handbook.</para>

          <para>Some unnamed clone cards have also been known to work,
            especially those that claim to be AST compatible.</para>

          <para>Check the &man.sio.4; manual page to get more
            information on configuring such cards.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="serial-console-prompt">
          <para>How do I get the boot: prompt to show on the serial
            console?</para>
        </question>

        <answer>
            <orderedlist>
              <listitem>
                <para>Build a kernel with
                  <literal>options COMCONSOLE</literal>.</para>
              </listitem>

              <listitem>
                <para>Create /boot.config and place <option>-P</option>
                  as the only text in the file.</para>
              </listitem>

              <listitem>
                <para>Unplug the keyboard from the system.</para>
              </listitem>
            </orderedlist>

          <para>See
            <filename>/usr/src/sys/i386/boot/biosboot/README.serial</filename>
            for information.</para>
        </answer>
      </qandaentry>

	</qandaset>

      </sect1>

      <sect1 id="compatibility-sound">
	<title>ÓõóêåõÝò Þ÷ïõ</title>

	<qandaset>

      <qandaentry>
        <question id="sound-card-support">
          <para>Which sound cards are supported by FreeBSD?</para>
        </question>

        <answer>
          <para>&os; supports various sound cards including the &soundblaster;,
	    &soundblaster; Pro, &soundblaster; 16, Pro Audio Spectrum 16,
            AdLib, and Gravis UltraSound sound cards (for more details,
            see <ulink url="&url.base;/releases/">&os; Release Information</ulink>
            and the &man.snd.4; manual page).
            There is also limited support for
            MPU-401 and compatible MIDI cards. Cards conforming to the
            &microsoft; Sound System specification are also supported.</para>

            <note>
              <para>This is only for sound!  This driver does not support
                CDROMs, SCSI or joysticks on these cards, except for the
                &soundblaster;. The &soundblaster; SCSI interface and some
                non-SCSI CDROMs are supported, but you cannot boot off this
                device.</para>
             </note>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="es1370-silent-pcm">
          <para>Workarounds for no sound from my &man.pcm.4; sound
            card?</para>
        </question>

        <answer>
          <para>Some sound cards, such as the es1370, set their output
            volume to 0 at every boot.  Run the following command
            every time the machine boots:</para>

          <screen>&prompt.root; <userinput>mixer pcm 100 vol 100 cd 100</userinput></screen>
        </answer>
      </qandaentry>

	</qandaset>

      </sect1>

      <sect1 id="compatibility-other">
	<title>¶ëëï õëéêü</title>

	<qandaset>

      <qandaentry>
        <question id="other-device-support">
          <para>What other devices does FreeBSD support?</para>
        </question>

        <answer>
          <para>See the <ulink
            url="&url.books.handbook;/install.html#INSTALL-MISC">Handbook</ulink>
            for the list of other devices supported.</para>

        </answer>
      </qandaentry>

      <qandaentry>
        <question id="power-management-support">
          <para>Does FreeBSD support power management on my
            laptop?</para>
        </question>

        <answer>
          <para>FreeBSD 4.X and later support <acronym>APM</acronym>
            on certain machines.  Further information can be found in
            &man.apm.4;.</para>

	  <para>FreeBSD 5.X and later support the
	    <acronym>ACPI</acronym> features found in most modern
	    hardware.  Further information can be found in
	    &man.acpi.4;.  If a system supports both
	    <acronym>APM</acronym> and <acronym>ACPI</acronym>, either
	    can be used.  We suggest you try both and choose the one
	    that best fits your needs.</para>

        </answer>
      </qandaentry>

      <qandaentry>
	<question id="disable-acpi">
	  <para>How do I disable ACPI?</para>
	</question>

	<answer>
	  <para>Add following line <screen>hint.acpi.0.disabled="1"</screen>
	    into your <filename>/boot/device.hints</filename> file.</para>
	</answer>
      </qandaentry>

      <qandaentry>
        <question id="micron-hang-boot">
          <para>Why does my Micron system hang at boot time?</para>
        </question>

        <answer>
          <para>Certain Micron motherboards have a non-conforming PCI BIOS
            implementation that causes grief when FreeBSD boots because PCI
            devices do not get configured at their reported addresses.</para>

          <para>Disable the <quote>Plug and Play Operating System</quote>
            flag in the BIOS to work around this problem.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="asusk7v-boot-failure">
          <para>The boot floppy hangs on a system with an ASUS K7V
            motherboard.  How do I fix this?</para>
        </question>

        <answer>
          <para>Go into the BIOS setup and disable the <quote>boot virus
            protection</quote>.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="micron-3comnic-failure">
          <para>Why does my &tm.3com; PCI network card not work with my Micron
            computer?</para>
        </question>

        <answer>
          <para>Certain Micron motherboards have a non-conforming PCI BIOS
            implementation that does not configure PCI devices at the
            addresses reported. This causes grief when FreeBSD
            boots.</para>

          <para>To work around this problem, disable the
            <quote>Plug and Play Operating System</quote> flag in the
            BIOS.</para>
        </answer>
      </qandaentry>

      <qandaentry>
	<question id="newcard-does-not-work">
	  <para>My PCMCIA card does not work. I have a message:
	    <quote>cbb0: unsupported card type detected.</quote>
	    What can I do?</para>
	</question>

	<answer>
	  <para>You can try to use the original OLDCARD implementation.  Edit
	    your kernel configuration file and remove the following lines:
	    <programlisting>device cbb
device pccard
device cardbus</programlisting>
	    Then add:
	    <programlisting>device pcic
device card 1</programlisting>
	    Rebuild and install the new kernel as described in
	    <ulink url="&url.books.handbook;/kernelconfig.html">Configuring
	    the FreeBSD Kernel</ulink>.</para>
	</answer>
      </qandaentry>
    </qandaset>

      </sect1>

  </chapter>

  <chapter id="troubleshoot">
    <title>Áíôéìåôþðéóç ÐñïâëçìÜôùí</title>

    <qandaset>
      <qandaentry>
        <question id="pae">
          <para>Why is &os; finding the wrong amount of memory?</para>
        </question>

        <answer>
	  <para>The reason is the difference between physical memory addresses
	    and virtual addresses.</para>

	  <para>The convention for most PC hardware is to use the memory area
	    between 3.5G and 4G for a special purpose (usually for PCI).  This
	    address space is used to access PCI hardware.  As a result real,
	    physical memory can not appear in that address space.</para>

	  <para>What happens to the memory that should appear in that location
	    is dependent on your hardware.  Unfortunately, some hardware does
	    nothing and the ability to use that last 500M of RAM is entirely
	    lost.</para>

	  <para>Luckily, most hardware remaps the memory to a higher location
	    so that it can still be used.  However, this can cause some
	    confusion if you watch the boot messages.</para>

	  <para>On a 32 bit version of &os;, the memory appears lost, since it
	    will be remapped above 4G, which a 32 bit kernel is unable to
	    access.  In this case, the solution is to build a PAE enabled
	    kernel.  See <link linkend="memory-limits">this FAQ entry</link>
	    for more information.</para>

	  <para>On a 64 bit version of &os;, or when running a PAE-enabled
	    kernel, &os; will correctly detect and remap the memory so it is
	    usable.  During boot, however, it may seem as if &os; is detecting
	    more memory than the system really has.  This is normal and the
	    available memory will be corrected as the boot process
	    completes.<para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="awre">
          <para>What do I do when I have bad blocks on my hard drive?</para>
        </question>

        <answer>
          <para>With SCSI drives, the drive should be capable of re-mapping
            these automatically.  However, many drives ship with
            this feature disabled.</para>

          <para>To enable bad block remapping edit the first device page
            mode, which can be done by giving the command
            (as <username>root</username>)</para>

          <screen>&prompt.root; <userinput>camcontrol modepage sd0 -m 1 -e -P 3</userinput></screen>

          <para>and changing the values of AWRE and ARRE from 0 to 1:-</para>

          <programlisting>AWRE (Auto Write Reallocation Enbld):  1
ARRE (Auto Read Reallocation Enbld):  1</programlisting>

	  <para>Modern IDE drives also have bad block remapping
	    features in the controller, and they ship with this
	    feature turned on.</para>

	  <para>If you see warnings about bad blocks (on either type
	    of drive), it is time to consider replacing the drive.
	    You might be able to use the drive manufacturer's
	    diagnostic program to lock out those bad blocks, but at
	    best this will buy you some time.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="hpnetserver-scsi-failure">
          <para>Why does FreeBSD not detect my HP Netserver's SCSI
            controller?</para>
        </question>

        <answer>
          <para>This is basically a known problem.  The EISA on-board SCSI
            controller in the HP Netserver machines occupies EISA slot
            number 11, so all the <quote>true</quote> EISA slots are in
            front of it. Alas, the address space for EISA slots &gt;= 10
            collides with the address space assigned to PCI, and FreeBSD's
            auto-configuration currently cannot handle this situation very
            well.</para>

          <para>So now, the best you can do is to pretend there is no
            address range clash :), by bumping the kernel option
            <literal>EISA_SLOTS</literal> to a value of 12. Configure and
            compile a kernel, as described in the <ulink
            url="&url.books.handbook;/kernelconfig.html">Handbook entry on
            configuring the kernel</ulink>.</para>

          <para>Of course, this does present you with a chicken-and-egg
            problem when installing on such a machine. In order to work
            around this problem, a special hack is available inside
            <emphasis>UserConfig</emphasis>. Do not use the
            <quote>visual</quote> interface, but the plain command-line
            interface there. Simply type</para>

          <programlisting>eisa 12
quit</programlisting>

          <para>at the prompt, and install your system as usual.  While
            it is recommended you compile and install a custom kernel
            anyway.</para>

          <para>Hopefully, future versions will have a proper fix for
            this problem.</para>

            <note>
              <para>You cannot use a
                <literal>dangerously dedicated</literal> disk
                with an HP Netserver. See <link linkend="dedicate">this
                note</link> for more info.</para>
            </note>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="ed1-timeout">
          <para>I keep seeing messages like
            <errorname>ed1: timeout</errorname>.  What do these messages
            mean?</para>
        </question>

        <answer>
          <para>This is usually caused by an interrupt conflict (e.g.,
            two boards using the same IRQ).  Boot with the
            -c option and change the ed0/de0/... entry to match your
            board.</para>

          <para>If you are using the BNC connector on your network card,
            you may also see device timeouts because of bad termination. To
            check this, attach a terminator directly to the NIC (with no
            cable) and see if the error messages go away.</para>

          <para>Some NE2000 compatible cards will give this error if there
            is no link on the UTP port or if the cable is disconnected.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="bad-3c509">
          <para>Why did my &tm.3com; 3C509 card stop working for no
            apparent reason?</para>
        </question>

        <answer>
          <para>This card has a bad habit of losing its configuration
            information.  Refresh your card's settings with the DOS
            utility <command>3c5x9.exe</command>.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="printer-slow">
          <para>My parallel printer is ridiculously slow. What can I do?</para>
        </question>

        <answer>
          <para>If the only problem is that the printer is terribly
            slow, try changing your <ulink
            url="&url.books.handbook;/printing-intro-setup.html#PRINTING-PARALLEL-PORT-MODE">printer
            port mode</ulink> as discussed in the <ulink
            url="&url.books.handbook;/printing-intro-setup.html">Printer
            Setup</ulink> section of the Handbook.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="signal11">
          <para>Why do my programs occasionally die with
            <errorname>Signal 11</errorname> errors?</para>
        </question>

        <answer>
          <para>Signal 11 errors are caused when your process has attempted
            to access memory which the operating system has not granted it
            access to. If something like this is happening at seemingly
            random intervals then you need to start investigating things
            very carefully.</para>

          <para>These problems can usually be attributed to either:</para>

          <orderedlist>
            <listitem>
              <para>If the problem is occurring only in a specific
                application that you are developing yourself it is probably
                a bug in your code.</para>
            </listitem>

            <listitem>
              <para>If it is a problem with part of the base FreeBSD system,
                it may also be buggy code, but more often than not these
                problems are found and fixed long before us general FAQ
                readers get to use these bits of code (that is what -current
                is for).</para>
            </listitem>
          </orderedlist>

          <para>In particular, a dead giveaway that this is
            <emphasis>not</emphasis> a FreeBSD bug is if you see the
            problem when you are compiling a program, but the activity
            that the compiler is carrying out changes each
            time.</para>

          <para>For example, suppose you are running <quote>make
            buildworld</quote>, and the compile fails while trying to
            compile <filename>ls.c</filename> into
            <filename>ls.o</filename>. If you then run <quote>make
            buildworld</quote> again, and the compile fails in the same
            place then this is a broken build -- try updating your sources
            and try again. If the compile fails elsewhere then this is
            almost certainly hardware.</para>

          <para>What you should do:</para>

          <para>In the first case you can use a debugger e.g. gdb to find
            the point in the program which is attempting to access a bogus
            address and then fix it.</para>

          <para>In the second case you need to verify that it is not your
            hardware at fault.</para>

          <para>Common causes of this include:</para>

          <orderedlist>
            <listitem>
              <para>Your hard disks might be overheating: Check the fans in
                your case are still working, as your disk (and perhaps
                other hardware might be overheating).</para>
            </listitem>

            <listitem>
              <para>The processor running is overheating: This might be
                because the processor has been overclocked, or the fan on
                the processor might have died. In either case you need to
                ensure that you have hardware running at what it is
                specified to run at, at least while trying to solve this
                problem. i.e. Clock it back to the default settings.</para>

              <para>If you are overclocking then note that it is far cheaper
                to have a slow system than a fried system that needs
                replacing! Also the wider community is not often
                sympathetic to problems on overclocked systems, whether you
                believe it is safe or not.</para>
            </listitem>

            <listitem>
              <para>Dodgy memory: If you have multiple memory SIMMS/DIMMS
                installed then pull them all out and try running the
                machine with each SIMM or DIMM individually and narrow the
                problem down to either the problematic DIMM/SIMM or perhaps
                even a combination.</para>
            </listitem>

            <listitem>
              <para>Over-optimistic Motherboard settings: In your BIOS
                settings, and some motherboard jumpers you have options to
                set various timings, mostly the defaults will be
                sufficient, but sometimes, setting the wait states on RAM
                too low, or setting the <quote>RAM Speed: Turbo</quote> option, or
                similar in the BIOS will cause strange behavior. A
                possible idea is to set to BIOS defaults, but it might be
                worth noting down your settings first!</para>
            </listitem>

            <listitem>
              <para>Unclean or insufficient power to the motherboard. If you
                have any unused I/O boards, hard disks, or CDROMs in your
                system, try temporarily removing them or disconnecting the
                power cable from them, to see if your power supply can
                manage a smaller load. Or try another power supply,
                preferably one with a little more power (for instance, if
                your current power supply is rated at 250 Watts try one
                rated at 300 Watts).</para>
            </listitem>

          </orderedlist>

          <para>You should also read the SIG11 FAQ (listed below) which has
            excellent explanations of all these problems, albeit from a
            &linux; viewpoint. It also discusses how memory testing software
            or hardware can still pass faulty memory.</para>

          <para>Finally, if none of this has helped it is possible that
            you have just found a bug in FreeBSD, and you should follow the
            instructions to send a problem report.</para>

          <para>There is an extensive FAQ on this at <ulink
            url="http://www.bitwizard.nl/sig11/">
            the SIG11 problem FAQ</ulink></para>
          </answer>
        </qandaentry>

        <qandaentry>
          <question id="trap-12-panic">
            <para>My system crashes with either <errorname>Fatal
              trap 12: page fault in kernel mode</errorname>, or
              <errorname>panic:</errorname>, and spits out a
              bunch of information.  What should I do?</para>
          </question>

          <answer>
            <para>The FreeBSD developers are very interested in these
              errors, but need some more information than just the
              error you see.  Copy your full crash message.  Then
              consult the FAQ section on <link linkend=
              "KERNEL-PANIC-TROUBLESHOOTING">kernel panics</link>,
              build a debugging kernel, and get a backtrace.  This
              might sound difficult, but you do not need any
              programming skills; you just have to follow the
              instructions.</para>
          </answer>
        </qandaentry>

        <qandaentry>
          <question id="screen-loses-sync">
            <para>Why does the screen go black and lose sync when I
              boot?</para>
          </question>

          <answer>
            <para>This is a known problem with the ATI Mach 64 video card.
              The problem is that this card uses address
              <literal>2e8</literal>, and the fourth serial port does too.
              Due to a bug (feature?) in the &man.sio.4;
              driver it will touch this port even if you do not have the
              fourth serial port, and <emphasis>even</emphasis> if
              you disable sio3 (the fourth port) which normally uses this
              address.</para>

            <para>Until the bug has been fixed, you can use this
              workaround:</para>

              <orderedlist>
                <listitem>
                  <para>Enter <option>-c</option> at the boot prompt.
                    (This will put the kernel into configuration mode).</para>
                </listitem>

                <listitem>
                  <para>Disable <devicename>sio0</devicename>,
                    <devicename>sio1</devicename>,
                    <devicename>sio2</devicename> and
                    <devicename>sio3</devicename> (all of them).  This way
                    the sio driver does not get activated -&gt; no
                    problems.</para>
                </listitem>

                <listitem>
                  <para>Type exit to continue booting.</para>
                </listitem>
              </orderedlist>

          <para>If you want to be able to use your serial ports, you will
            have to build a new kernel with the following modification: in
            <filename>/usr/src/sys/i386/isa/sio.c</filename> find the one
            occurrence of the string <literal>0x2e8</literal> and remove
            that string and the preceding comma (keep the trailing comma).
            Now follow the normal procedure of building a new
            kernel.</para>

          <para>Even after applying these workarounds, you may still find
            that the X Window System does not work properly. If this is the
            case, make sure that the &xfree86; version you are using is at
            least &xfree86; 3.3.3 or higher. This version and upwards has
            built-in support for the Mach64 cards and even a dedicated X
            server for those cards.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="reallybigram">
          <para>Why does FreeBSD only use 64 MB of RAM when my system has
            128 MB of RAM installed?</para>
        </question>

        <answer>
          <para>Due to the manner in which FreeBSD gets the memory size
            from the BIOS, it can only detect 16 bits worth of Kbytes in
            size (65535 Kbytes = 64MB) (or less... some BIOSes peg the
            memory size to 16M). If you have more than 64MB, FreeBSD will
            attempt to detect it; however, the attempt may fail.</para>

          <para>To work around this problem, you need to use the kernel
            option specified below. There is a way to get complete memory
            information from the BIOS, but we do not have room in the
            bootblocks to do it. Someday when lack of room in the
            bootblocks is fixed, we will use the extended BIOS functions to
            get the full memory information...but for now we are stuck with
            the kernel option.</para>

          <para><literal>options "MAXMEM=<replaceable>n</replaceable>"</literal></para>

          <para>Where <replaceable>n</replaceable> is your memory in
            Kilobytes. For a 128 MB machine, you would want to use
            <literal>131072</literal>.</para>
        </answer>
      </qandaentry>

      <qandaentry>
	<question id="kmem-map-too-small">
	  <para>My system has more than 1 GB of RAM, and I'm getting panics
	    with <quote>kmem_map too small</quote> messages. What is wrong?
	    </para>
	</question>

	<answer>
	  <para>Normally, FreeBSD determines a number of kernel parameters,
	    such as as the maximum number of files that can be open
	    concurrently, from the  amount of memory installed in the
	    system.  On systems with one gigabyte of RAM or more, this
	    <quote>auto sizing</quote> mechanism may choose values that are
	    too high: while starting up, the kernel allocates various tables
	    and other structures that fill up most of the available kernel
	    memory. Later on, while the system is running, the kernel has no
	    more space left for dynamic memory allocations, and
	    panics.</para>

	  <para>Compile your own kernel, and add the
	    <option>VM_KMEM_SIZE_MAX</option> to your kernel configuration
	    file, increasing the maximum size to 400&nbsp;MB
	    (<option>options VM_KMEM_SIZE_MAX=419430400</option>).
	    400&nbsp;MB appears to be sufficient for machines with up to
	    6&nbsp;GB of memory.</para>
	</answer>
      </qandaentry>
      
      <qandaentry>
	<question id="panic-kmemmap-too-small">
	  <para>My system does not have 1 GB of RAM, and FreeBSD still
	    panics with <errorname>kmem_map too small!</errorname>
	    </para>
	</question>

        <answer>
          <para>The panic indicates that the system ran out of virtual
            memory for network buffers (specifically, mbuf clusters). You
            can increase the amount of VM available for mbuf clusters by
            following the instructions in the <ulink
            url="&url.books.handbook;/configtuning-kernel-limits.html#NMBCLUSTERS">Network
            Limits</ulink> section of the Handbook.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="proc-table-full">
          <para>Why do I get the error <errorname>/kernel: proc: table
            is full</errorname>?</para>
        </question>

        <answer>
          <para>The FreeBSD kernel will only allow a certain number of
            processes to exist at one time.  The number is based on
            the <literal>MAXUSERS</literal> option in the kernel
            configuration.  <literal>MAXUSERS</literal> also affects
            various other in-kernel limits, such as network buffers
            (see <link linkend="panic-kmemmap-too-small">this</link>
            earlier question).  If your machine is heavily loaded, you
            probably want to increase <literal>MAXUSERS</literal>.
            This will increase these other system limits in addition
            to the maximum number of processes.</para>

	  <para>To adjust your <literal>MAXUSERS</literal> value, see
	    the <ulink
	    url="&url.books.handbook;/configtuning-kernel-limits.html#KERN-MAXFILES">File/Process
	    Limits</ulink> section of the Handbook.  (While that
	    section refers to open files, the same limits apply to
	    processes.)</para>

          <para>If your machine is lightly loaded, and you are simply
            running a very large number of processes, you can adjust
            this with the <varname>kern.maxproc</varname> tunable.  If
            this tunable needs adjustion it needs to be defined in
            in <filename>/boot/loader.conf</filename>.  The tunable
            will not get adjusted until the system is rebooted.  For
            more information about tuning tunables, you should see the
            &man.loader.conf.5; and &man.sysctl.conf.5; manual pages.
            If these processes are being run by a single user, you will
            also need to adjust <varname>kern.maxprocperuid</varname>
            to be one less than your new
            <varname>kern.maxproc</varname> value.  (It must be at
            least one less because one system program, &man.init.8;,
            must always be running.)</para>

	  <para>To make a sysctl change permanent place the proper value
	    in <filename>/etc/sysctl.conf</filename>.  More information
	    about system tuning with &man.sysctl.8; can be found at
	    the <ulink
	      url="&url.books.handbook;/configtuning-sysctl.html">Tuning
	      with sysctl</ulink> section of the Handbook.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="cmap-busy-panic">
          <para>Why do I get an error reading <errorname>CMAP
              busy</errorname> when rebooting with a new
            kernel?</para>
        </question>

        <answer>
          <para>The logic that attempts to detect an out of date
            <filename>/var/db/kvm_*.db</filename> files sometimes fails
            and using a mismatched file can sometimes lead to panics.</para>

          <para>If this happens, reboot single-user and do:</para>

          <screen>&prompt.root; <userinput>rm /var/db/kvm_*.db</userinput></screen>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="brkadrint-illegal-host-access">
          <para>What does the message <errorname>ahc0: brkadrint,
              Illegal Host Access at seqaddr 0x0</errorname>
            mean?</para>
        </question>

        <answer>
          <para>This is a conflict with an Ultrastor SCSI Host Adapter.</para>

          <para>During the boot process enter the kernel configuration
            menu and disable
            <devicename>uha0</devicename>,
            which is causing the problem.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="aci0-illegal-cable">
          <para>When I boot my system, I get the error
            <errorname>ahc0: illegal cable configuration</errorname>.
            My cabling is correct.  What is going on?</para>
        </question>

        <answer>
           <para>Your motherboard lacks the external logic to support
             automatic termination.  Switch your SCSI BIOS to specify
             the correct termination for your configuration rather
             than automatic termination.  The AIC7XXX driver cannot
             determine if the external logic for cable detection (and
             thus auto-termination) is available.  The driver simply
             assumes that this support must exist if the configuration
             contained in the serial EEPROM is set to "automatic
             termination".  Without the external cable detection logic
             the driver will often configure termination incorrectly,
             which can compromise the reliability of the SCSI
             bus.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="mail-loopback">
          <para>Why does Sendmail give me an error reading
            <quote><errorname>mail loops back to
              myself</errorname></quote>?</para>
        </question>

        <answer>
          <para>This is answered in the sendmail FAQ as follows:-</para>

<literallayout>        * I'm getting "Local configuration error" messages, such as:

        553 relay.domain.net config error: mail loops back to myself
        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 record, but the relay machine does not recognize
        itself as domain.net.  Add domain.net to /etc/mail/local-host-names
        (if you are using FEATURE(use_cw_file)) or add "Cw domain.net"
        to /etc/mail/sendmail.cf.
            </literallayout>

          <para>The current version of the <ulink
            url="ftp://rtfm.mit.edu/pub/usenet/news.answers/mail/sendmail-faq">sendmail
            FAQ</ulink> is no longer maintained with the sendmail release.
            It is however regularly posted to <ulink
            url="news:comp.mail.sendmail">comp.mail.sendmail</ulink>,
            <ulink url="news:comp.mail.misc">comp.mail.misc</ulink>, <ulink
            url="news:comp.mail.smail">comp.mail.smail</ulink>, <ulink
            url="news:comp.answers">comp.answers</ulink>, and <ulink
            url="news:news.answers">news.answers</ulink>. You can also
            receive a copy via email by sending a message to
            <email>mail-server@rtfm.mit.edu</email> with the command
            <literal>send usenet/news.answers/mail/sendmail-faq</literal>
            as the body of the message.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="remote-fullscreen">
          <para>Why do full screen applications on remote machines
            misbehave?</para>
        </question>

        <answer>
          <para>The remote machine may be setting your terminal type
            to something other than the <literal>cons25</literal> terminal
            type required by the FreeBSD console.</para>

          <para>There are a number of possible work-arounds for this
            problem:</para>
            <itemizedlist>
              <listitem>
                <para>After logging on to the remote machine, set your
                  TERM shell variable to <literal>ansi</literal> or
                  <literal>sco</literal> if the remote machine knows
                  about these terminal types.</para>
              </listitem>

              <listitem>
                <para>Use a VT100 emulator like
                  <application>screen</application> at the FreeBSD console.
                  <application>screen</application> offers you the ability
                  to run multiple concurrent sessions from one terminal,
                  and is a neat program in its own right. Each
                  <application>screen</application> window behaves like a
                  VT100 terminal, so the TERM variable at the remote end
                  should be set to <literal>vt100</literal>.</para>
              </listitem>

              <listitem>
                <para>Install the <literal>cons25</literal> terminal
                  database entry on the remote machine. The way to do this
                  depends on the operating system on the remote machine.
                  The system administration manuals for the remote system
                  should be able to help you here.</para>
              </listitem>

              <listitem>
                <para>Fire up an X server at the FreeBSD end and login to
                  the remote machine using an X based terminal emulator
                  such as <command>xterm</command> or
                  <command>rxvt</command>. The TERM variable at the remote
                  host should be set to <literal>xterm</literal> or
                  <literal>vt100</literal>.</para>
              </listitem>
            </itemizedlist>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="calcru-negative">
          <para>Why does my machine print
            <errorname>calcru: negative time...</errorname>?</para>
        </question>

        <answer>
          <para>This can be caused by various hardware or software
            ailments relating to interrupts. It may be due to bugs but can
            also happen by nature of certain devices. Running TCP/IP over
            the parallel port using a large MTU is one good way to provoke
            this problem. Graphics accelerators can also get you here, in
            which case you should check the interrupt setting of the card
            first.</para>

          <para>A side effect of this problem are dying processes with the
            message <quote>SIGXCPU exceeded cpu time limit</quote>.</para>

          <para>If the problem cannot be fixed otherwise the solution
            is to set this sysctl variable:</para>

          <screen>&prompt.root; <userinput>sysctl -w kern.timecounter.method=1</userinput></screen>

	  <note>
	    <para>The <option>-w</option> option of &man.sysctl.8; is
	      deprecated and silently ignored in &os; 4.4-RELEASE and all
	      newer versions.  You can safely ommit it when setting options
	      with <command>sysctl</command> as shown above.</para>
	  </note>

          <para>This means a performance impact, but considering the cause
            of this problem, you probably will not notice. If the problem
            persists, keep the sysctl set to one and set the
            <literal>NTIMECOUNTER</literal> option in your kernel to
            increasingly large values. If by the time you have reached
            <literal>NTIMECOUNTER=20</literal> the problem is not solved,
            interrupts are too hosed on your machine for reliable
            time keeping.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="pnp-not-found">
          <para>Why is my PnP card no longer found (or found as
            <literal>unknown</literal>) since upgrading to FreeBSD 4.X?</para>
        </question>

        <answer>
          <para>FreeBSD 4.X is now much more <emphasis>PnP-centric</emphasis>
            and this has had the side effect of some PnP devices (e.g. sound
            cards and internal modems) not working even though they worked
            under FreeBSD 3.X.</para>

          <para>The reasons for this behavior are explained by the following
            e-mail, posted to the freebsd-questions mailing list by Peter
            Wemm, in answer to a question about an internal modem that was
            no longer found after an upgrade to FreeBSD 4.X (the comments
            in <literal>[]</literal> have been added to clarify the
            context.</para>

          <note>
            <para>The contents of this quotation has been updated from
             its original text.</para>
          </note>

          <blockquote>
            <para>The PNP bios preconfigured it [the modem] and left it
              laying around in port space, so [in 3.X] the old-style ISA
              probes <quote>found</quote> it there.</para>

            <para>Under 4.0, the ISA code is much more PnP-centric. It was
              possible [in 3.X] for an ISA probe to find a
              <quote>stray</quote> device and then for the PNP device id to
              match and then fail due to resource conflicts. So, it
              disables the programmable cards first so this double probing
              cannot happen. It also means that it needs to know the PnP
              ids for supported PnP hardware. Making this more user
              tweakable is on the TODO list.</para>
          </blockquote>

          <para>To get the device working again requires finding its PnP id
            and adding it to the list that the ISA probes use to identify
            PnP devices. This is obtained using &man.pnpinfo.8; to probe the
            device, for example this is the output from &man.pnpinfo.8; for
            an internal modem:</para>

          <screen>&prompt.root; <userinput>pnpinfo</userinput>
Checking for Plug-n-Play devices...

Card assigned CSN #1
Vendor ID PMC2430 (0x3024a341), Serial Number 0xffffffff
PnP Version 1.0, Vendor Version 0
Device Description: Pace 56 Voice Internal Plug & Play Modem

Logical Device ID: PMC2430 0x3024a341 #0
        Device supports I/O Range Check
TAG Start DF
    I/O Range 0x3f8 .. 0x3f8, alignment 0x8, len 0x8
        [16-bit addr]
    IRQ: 4  - only one type (true/edge)</screen>

          <para>[more TAG lines elided]</para>

          <screen>TAG End DF
End Tag

Successfully got 31 resources, 1 logical fdevs
-- card select # 0x0001

CSN PMC2430 (0x3024a341), Serial Number 0xffffffff

Logical device #0
IO:  0x03e8 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8
IRQ 5 0
DMA 4 0
IO range check 0x00 activate 0x01</screen>

          <para>The information you require is in the
            <quote>Vendor ID</quote> line at the start of the output. The
            hexadecimal number in parentheses (0x3024a341 in this example)
            is the PnP id and the string immediately before this (PMC2430)
            is a unique ASCII id.</para>

          <para>Alternatively, if &man.pnpinfo.8; does not list the card in
            question, &man.pciconf.8; can be used instead.  This is part of
            the output from <command>pciconf -vl</command> for an onboard
            sound chip:</para>

          <screen>&prompt.root; <userinput>pciconf -vl</userinput>
chip1@pci0:31:5:        class=0x040100 card=0x00931028 chip=0x24158086 rev=0x02 hdr=0x00
    vendor   = 'Intel Corporation'
    device   = '82801AA 8xx Chipset AC'97 Audio Controller'
    class    = multimedia
    subclass = audio</screen>

          <para>Here, you would use the <varname>chip</varname> value,
            <quote>0x24158086</quote>.</para>

          <para>This information (Vendor ID or chip value) needs adding 
            to the file
            <filename>/usr/src/sys/isa/sio.c</filename>.</para>

          <para>You should first make a backup of <filename>sio.c</filename>
            just in case things go wrong. You will also need it to make the
            patch to submit with your PR (you are going to submit a PR,
            are you not?) then edit <filename>sio.c</filename> and search
            for the line</para>

          <programlisting>static struct isa_pnp_id sio_ids[] = {</programlisting>

          <para>then scroll down to find the correct place to add the entry
            for your device. The entries look like this, and are sorted on
            the ASCII Vendor ID string which should be included in the
            comment to the right of the line of code along with all (if it
            will fit) or part of the <emphasis>Device Description</emphasis>
            from the output of &man.pnpinfo.8;:</para>

          <programlisting>{0x0f804f3f, NULL},     /* OZO800f - Zoom 2812 (56k Modem) */
{0x39804f3f, NULL},     /* OZO8039 - Zoom 56k flex */
{0x3024a341, NULL},     /* PMC2430 - Pace 56 Voice Internal Modem */
{0x1000eb49, NULL},     /* ROK0010 - Rockwell ? */
{0x5002734a, NULL},     /* RSS0250 - 5614Jx3(G) Internal Modem */</programlisting>

          <para>Add the hexadecimal Vendor ID for your device in the
            correct place, save the file, rebuild your kernel, and reboot.
            Your device should now be found as an <literal>sio</literal>
            device as it was under FreeBSD 3.X</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="nlist-failed">
          <para>Why do I get the error <errorname>nlist failed</errorname> when
            running, for example, <command>top</command> or
            <command>systat</command>?</para>
        </question>

        <answer>
          <para>The problem is that the application you are trying to run is
            looking for a specific kernel symbol, but, for whatever reason,
            cannot find it; this error stems from one of two problems:</para>

          <itemizedlist>
            <listitem>
              <para>Your kernel and userland are not synchronized (i.e., you
                built a new kernel but did not do an
                <maketarget>installworld</maketarget>, or vice versa), and
                thus the symbol table is different from what the user
                application thinks it is.  If this is the case, simply
                complete the upgrade process (see
                <filename>/usr/src/UPDATING</filename> for the correct
                sequence).</para>
            </listitem>

            <listitem>
              <para>You are not using <command>/boot/loader</command> to load
                your kernel, but doing it directly from boot2 (see
                &man.boot.8;).  While there is nothing wrong with bypassing
                <command>/boot/loader</command>, it generally does a better
                job of making the kernel symbols available to user
                applications.</para>
            </listitem>
          </itemizedlist>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="connection-delay">
          <para>Why does it take so long to connect to my computer via
            <command>ssh</command> or <command>telnet</command>?</para>
        </question>

        <answer>
          <para>The symptom: there is a long delay between the time the TCP
            connection is established and the time when the client software
            asks for a password (or, in &man.telnet.1;'s case, when a login
            prompt appears).</para>

          <para>The problem: more likely than not, the delay is caused by
            the server software trying to resolve the client's IP address
            into a hostname.  Many servers, including the Telnet and SSH
            servers that come with FreeBSD, do this in order to, among
            other things, store the hostname in a log file for future
            reference by the administrator.</para>

          <para>The remedy: if the problem occurs whenever you connect from
            your computer (the client) to any server, the problem is with
            the client; likewise, if the problem only occurs when someone
            connects to your computer (the server) the problem is with the
            server.</para>

          <para>If the problem is with the client, the only remedy is to
            fix the DNS so the server can resolve it.  If this is on a
            local network, consider it a server problem and keep reading;
            conversely, if this is on the global Internet, you will most
            likely need to contact your ISP and ask them to fix it for
            you.</para>

          <para>If the problem is with the server, and this is on a local
            network, you need to configure the server to be able to resolve
            address-to-hostname queries for your local address range.  See
            the &man.hosts.5; and &man.named.8; manual pages for more
            information.  If this is on the global Internet, the problem
            may be that your server's resolver is not functioning
            correctly.  To check, try to look up another host--say,
            <hostid>www.yahoo.com</hostid>.  If it does not work, that is
            your problem.</para>

	  <para>Following a fresh install of &os;, it is also possible
	    that domain and nameserver information is missing from
	    <filename>/etc/resolv.conf</filename>.  This will often cause
	    a delay in <application>SSH</application>, as the option
	    <quote>UseDNS</quote> is set to <quote>yes</quote> by default
	    in the <filename>sshd_config</filename> file in
	    <filename>/etc/ssh</filename>.  If this is causing the
	    problem, you will either need to fill in the missing information
	    in <filename>/etc/resolv.conf</filename> or set <quote>UseDNS</quote>
	    to <quote>no</quote> in <filename>sshd_config</filename>
	    as a temporary workaround.</para>
	</answer>
      </qandaentry>

      <qandaentry>
        <question id="stray-irq">
          <para>What does <errorname>stray IRQ</errorname> mean?</para>
        </question>
	<answer>
	  <para>Stray IRQs are indications of hardware IRQ glitches,
            mostly from hardware that removes its interrupt request in
            the middle of the interrupt request acknowledge
            cycle.</para>
	  <para>One has three options for dealing with this:</para>
	  <itemizedlist>
	    <listitem>
	      <para>Live with the warnings.  All except the first 5
                per irq are suppressed anyway.</para>
	    </listitem>
	    <listitem>
	      <para>Break the warnings by changing 5 to 0 in
	        <function>isa_strayintr()</function> so that all the
	        warnings are suppressed.</para>
	    </listitem>
	    <listitem>
	      <para>Break the warnings by installing parallel port
              hardware that uses irq 7 and the PPP driver for it (this
              happens on most systems), and install an ide drive or
              other hardware that uses irq 15 and a suitable driver
              for it.</para>
	    </listitem>
	  </itemizedlist>
	</answer>
      </qandaentry>

      <qandaentry>
        <question id="file-table-full">
          <para>Why does <errorname>file: table is full</errorname> show up
            repeatedly in dmesg?</para>
        </question>
        <answer>
          <para>
            This error message indicates you have exhausted the number
            of available file descriptors on your system.  Please see
            the <ulink
            url="&url.books.handbook;/configtuning-kernel-limits.html#KERN-MAXFILES">kern.maxfiles
            </ulink>section of the <ulink
            url="&url.books.handbook;/configtuning-kernel-limits.html">Tuning
            Kernel Limits</ulink> section of the Handbook for a
            discussion and solution.</para>
        </answer>
      </qandaentry>

      <qandaentry>
	<question id="laptop-clock-skew">
	  <para>Why does the clock on my laptop keep incorrect time?</para>
	</question>

	<answer>
	  <para>Your laptop has two or more clocks, and FreeBSD has chosen to
	    use the wrong one.</para>

	  <para>Run &man.dmesg.8;, and check for lines that contain
	    <literal>Timecounter</literal>.  The last line printed is the one
	    that FreeBSD chose, and will almost certainly be
	    <literal>TSC</literal>.</para>

	  <screen>&prompt.root; <userinput>dmesg | grep Timecounter</userinput>
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 595573479 Hz</screen>

	  <para>You can confirm this by checking the
	    <varname>kern.timecounter.hardware</varname>
	      &man.sysctl.3;.</para>

	  <screen>&prompt.root; <userinput>sysctl kern.timecounter.hardware</userinput>
kern.timecounter.hardware: TSC</screen>
	
	  <para>The BIOS may modify the TSC clock&mdash;perhaps to change the
	    speed of the processor when running from batteries, or going into
	    a power saving mode, but FreeBSD is unaware of these adjustments,
	    and appears to gain or lose time.</para>

	  <para>In this example, the <literal>i8254</literal> clock is also
	    available, and can be selected by writing its name to the
	    <varname>kern.timecounter.hardware</varname>
	      &man.sysctl.3;.</para>

	  <screen>&prompt.root; <userinput>sysctl -w kern.timecounter.hardware=i8254</userinput>
kern.timecounter.hardware: TSC -&gt; i8254</screen>

	  <para>Your laptop should now start keeping more accurate
	    time.</para>

	  <para>To have this change automatically run at boot time, add the
	    following line to <filename>/etc/sysctl.conf</filename>.</para>

	  <programlisting>kern.timecounter.hardware=i8254</programlisting>
	</answer>
      </qandaentry>

      <qandaentry>
	<question id="null-null">
	  <para>Why did my laptop fail to correctly probe PC cards?</para>
	</question>

	<answer>
	  <para>This problem is common on laptops that boot more than
	    one operating system.  Some non-BSD operating systems
	    leave PC card hardware in an inconsistent state.
	    <command>pccardd</command> will detect the card as
	    <errorname>"(null)""(null)"</errorname> instead of its
	    actual model.</para>

	  <para>You must remove all power from the PC card slot to
	    fully reset the hardware.  Completely power off the
	    laptop.  (Do not suspend it, do not let it go into standby;
	    the power needs to be completely off.)  Wait a few
	    moments, and reboot.  Your PC card should work now.</para>

	  <para>Some laptop hardware lies when it claims to be off.
	    If the above does not work shut down, remove the battery,
	    wait a moment, replace the battery, and reboot.</para>
	</answer>
      </qandaentry>

      <qandaentry>
        <question id="boot-read-error">
          <para>Why does FreeBSD's boot loader display
            <errorname>Read error</errorname> and stop after the BIOS
            screen?</para>
        </question>

        <answer>
          <para>FreeBSD's boot loader is incorrectly recognizing the hard 
            drive's geometry. This must be manually set within fdisk when 
            creating or modifying FreeBSD's slice.
          </para>

          <para>The correct drive geometry values can be found within the
            machine's BIOS. Look for the number of cylinders, heads and
            sectors for the particular drive.
          </para>

          <para>Within &man.sysinstall.8;'s fdisk, hit
            <keycap>G</keycap> to set the drive geometry.</para>

          <para>A dialog will pop up requesting the number of
            cylinders, heads and sectors.  Type the numbers found from
            the BIOS separated by forward slashes.  For example, values
            of 5000 cylinders, 250 heads, and 60 sectors would be entered as
            <userinput>5000/250/60</userinput>.
          </para>

          <para>Press enter to set the values, and hit
            <keycap>W</keycap> to write the new partition table to the
            drive.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="bootmanager-restore">
          <para>Another operating system destroyed my Boot Manager.  How do I 
            get it back?</para>
        </question>

        <answer>
          <para>Enter &man.sysinstall.8; and choose Configure,
            then Fdisk.  Select the disk the Boot Manager resided on
            with the <keycap>space</keycap> key.  Press 
            <keycap>W</keycap> to write changes to the drive.  A prompt
            will appear asking which boot loader to install.  Select this,
            and it will be restored.
          </para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="indefinite-wait-buffer">
          <para>What does the error <errorname>swap_pager: indefinite
            wait buffer:</errorname> mean?</para>
        </question>

        <answer>
          <para>This means that a process is trying to page memory to
            disk, and the page attempt has hung trying to access the
            disk for more than 20 seconds.  It might be caused by bad
            blocks on the disk drive, disk wiring, cables, or any
            other disk I/O-related hardware.  If the drive itself is
            actually bad, you will also see disk errors in
            <filename>/var/log/messages</filename> and in the output
            of <command>dmesg</command>.  Otherwise, check your cables
            and connections.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="udma-icrc">
          <para>What are <quote>UDMA ICRC</quote> errors, and how do I
            fix them?</para>
        </question>

        <answer>
          <para>The &man.ata.4; driver reports <quote>UDMA ICRC</quote>
            errors when a DMA transfer to or from a drive is corrupted.
            The driver will retry the operation a few times.  Should
            the retries fail, it will switch from DMA to the slower PIO
            mode of communication with the device.</para>

          <para>The problem can be caused by many factors, although
            perhaps the most common cause is faulty or incorrect
            cabling.  Check that the ATA cables are undamaged and rated
            for the Ultra DMA mode in use.  If you are using removable
            drive trays, they must also be compatible.  Be sure that
            all connections are making good contact.  Problems have
            also been noticed when an old drive is installed on the
            same ATA channel as an Ultra DMA 66 (or faster) drive.
            Lastly, these errors can indicate that the drive is
            failing.  Most drive vendors provide testing software for
            their drives, so test your drive, and, if necessary, back
            up your data and replace it.</para>

          <para>The &man.atacontrol.8; utility can be used to show and
            select the DMA or PIO modes used for each ATA device.  In
            particular, <command>atacontrol mode
            <replaceable>channel</replaceable></command> will show the
            modes in use on a particular ATA channel, where the primary
            channel is numbered 0, and so on.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="lock-order-reversal">
          <para>What is a <errorname>lock order reversal</errorname>?</para>
        </question>

        <answer>
          <para>&a.rwatson; answered this question very succinctly on
            the freebsd-current list in a thread entitled <quote><ulink
            url="http://docs.freebsd.org/cgi/getmsg.cgi?fetch=65165+0+/usr/local/www/db/text/2003/freebsd-current/20031221.freebsd-current">lock
            order reversals - what do they mean?</ulink></quote></para>

          <blockquote>
            <attribution>&a.rwatson; on freebsd-current, December 14,
              2003</attribution>

            <para>These warnings are generated by Witness, a run-time lock
              diagnostic system found in FreeBSD -CURRENT kernels (but
              removed in releases).  You can read more about Witness in the
              &man.witness.4; man page, which talks about its capabilities.  Among
              other things, Witness performs run-time lock order verification
              using a combination of hard coded lock orders, and run-time
              detected lock orders, and generates console warnings when lock
              orders are violated.  The intent of this is to detect the
              potential for deadlocks due to lock order violations; it is worth
              observing that Witness is actually slightly conservative, and so
              it is possible to get false positives.  In the event that Witness
              is accurately reporting a lock order problem, it is basically
              saying "If you were unlucky, a deadlock would have happened
              here".  There are a couple of "well known" false positives,
              which we need to do a better job of documenting to prevent
              spurious reports.  The non-well-known ones typically correspond
              to bugs in newly added locking, as lock order reversals usually
              get fixed pretty quickly because Witness is busy generating
              warnings :-).</para>
          </blockquote>

          <note>
	    <para>A so-called "false positive" is actually Witness tripping
                over a much more serious bug.  Such bugs are typically a page
                fault or memory corruption experienced inside of the kernel, or
                a name clash with mutexes.</para>
	  </note>
          <note>
            <para>See <ulink
              url="http://sources.zabbadoz.net/freebsd/lor.html">Bjoern
              Zeeb's lock order reversal page</ulink> for the status of
              known lock order reversals.</para>
          </note>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="called-with-non-sleepable-locks-held">
          <para>What does <errorname>Called ... with the following
            non-sleepable locks held</errorname> mean?</para>
        </question>

        <answer>
          <para>This means that a function that may sleep was called while
              a mutex (or other unsleepable) lock was held.</para>

          <para>The reason this is an error is because mutexes are not
              intended to be held for long periods of time; they are
              supposed to only be held to maintain short periods of
              synchronization.  This programming contract allows device
              drivers to use mutexes to synchronize with the rest of the kernel
              during interrupts.  Interrupts (under FreeBSD) may not sleep.
              Hence it is imperative that no subsystem in the kernel
              block for an extended period while holding a mutex.</para>

          <para>To catch such errors, assertions may be added to the kernel
              that interact with the witness subsystem to emit a warning
              or fatal error (depending on the system configuration) when
              a potentially blocking call is made while holding a mutex.</para>

          <para>In summary, such warnings are non-fatal, however with
              unfortunate timing they could cause undesirable effects
              ranging from a minor blip in the system's responsiveness
              to a complete system lockup.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="touch-not-found">
	  <para>Why does buildworld/installworld die with the message
	    <errorname>touch: not found</errorname>?</para>
        </question>

	<answer>
	  <para>This error does not mean that the &man.touch.1; utility is
	      missing. The error is instead probably due to the dates of the
	      files being set sometime in the future. If your CMOS-clock is
	      set to local time you need to run the command
	      <command>adjkerntz&nbsp;-i</command> to adjust the kernel clock
	      when booting into single user mode.</para>
	</answer>
      </qandaentry>
    </qandaset>
  </chapter>

  <chapter id="commercial">
    <title>ÅìðïñéêÝò ÅöáñìïãÝò</title>

      <note>
        <para>This section is still very sparse, though we are hoping, of
          course, that companies will add to it! :) The FreeBSD group has
          no financial interest in any of the companies listed here but
          simply lists them as a public service (and feels that commercial
          interest in FreeBSD can have very positive effects on FreeBSD's
          long-term viability). We encourage commercial software vendors to
          send their entries here for inclusion. See <ulink
          url="&url.base;/commercial/index.html">the
          Vendors page</ulink> for a longer list.</para>
      </note>

    <qandaset>
      <qandaentry>
        <question id="officesuite">
          <para>Where can I get an Office Suite for FreeBSD?</para>
        </question>

        <answer>
	  <para>The open-source <ulink
	    url="http://www.openoffice.org">OpenOffice.org</ulink> office
	    suite works natively on FreeBSD.  The &linux; version of
	    <ulink
	    url="http://www.sun.com/staroffice/">StarOffice</ulink>,
	    the value-added closed-source version of OpenOffice.org, also
	    works on FreeBSD.</para>

	  <para>FreeBSD also includes a variety of text editors,
	    spreadsheets, and drawing programs in the Ports
	    Collection.</para>
        </answer>
      </qandaentry>
      <qandaentry>
        <question id="motif">
          <para>Where can I get &motif; for FreeBSD?</para>
        </question>

        <answer>
	  <para>The Open Group has released the source code to &motif; 2.2.2.
	    You can install the <literal>open-motif</literal> package, or
	    compile it from ports.  Refer to
	    <ulink url="&url.books.handbook;/ports.html">the ports section of the
	      Handbook</ulink> for more information on how to do this.

	    <note>
	      <para>The Open &motif; distribution only allows redistribution
		if it is running on an <ulink url="http://www.opensource.org/">
		  open source</ulink> operating system.</para>
	    </note>
	  </para>

          <para>In addition, there are commercial distributions of the &motif;
            software available.  These, however, are not for free, but their
            license allows them to be used in closed-source software.
	    Contact <link linkend="apps2go">Apps2go</link> for the
            least expensive ELF &motif; 2.1.20 distribution for FreeBSD
            (either &i386; or Alpha).<anchor id="apps2go"></para>

          <para>There are two distributions, the <quote>development
            edition</quote> and the <quote>runtime edition</quote> (for
            much less).  These distributions includes:</para>

            <itemizedlist>
              <listitem>
                <para>OSF/&motif; manager, xmbind, panner, wsm.</para>
              </listitem>

              <listitem>
                <para>Development kit with uil, mrm, xm, xmcxx, include
                  and Imake files.</para>
              </listitem>

              <listitem>
                <para>Static and dynamic ELF libraries.</para>
              </listitem>

              <listitem>
                <para>Demonstration applets.</para>
              </listitem>
            </itemizedlist>

          <para>Be sure to specify that you want the FreeBSD version of
            &motif; when ordering (do not forget to mention the architecture
            you want too)! Versions for NetBSD and OpenBSD are also sold by
            <emphasis>Apps2go</emphasis>. This is currently a FTP only
            download.</para>

            <variablelist>
              <varlistentry>
                <term>More info</term>
                <listitem>
                  <para><ulink url="http://www.apps2go.com/">
                    Apps2go WWW page</ulink></para>
                </listitem>
              </varlistentry>

              <varlistentry>
                <term>or</term>
                  <listitem>
                    <para>
                      <email>sales@apps2go.com</email> or
                      <email>support@apps2go.com</email>
                      </para>
                  </listitem>
                </varlistentry>

                <varlistentry>
                  <term>or</term>
                  <listitem>
                    <para>phone (817) 431 8775  or +1 817 431-8775</para>
                  </listitem>
                </varlistentry>
              </variablelist>

          <para>Contact <link linkend="xig">Xi Graphics</link> for an
            a.out &motif; 2.0 distribution for FreeBSD.</para>

          <para>This distribution includes:</para>
            <itemizedlist>
              <listitem>
                <para>OSF/&motif; manager, xmbind, panner, wsm.</para>
              </listitem>

              <listitem>
                <para>Development kit with uil, mrm, xm, xmcxx, include
                  and Imake files.</para>
              </listitem>

              <listitem>
                <para>Static and dynamic libraries (for use with FreeBSD
                  2.2.8 and earlier).</para>
              </listitem>

              <listitem>
                <para>Demonstration applets.</para>
              </listitem>

              <listitem>
                <para>Preformatted manual pages.</para>
              </listitem>
            </itemizedlist>

          <para>Be sure to specify that you want the FreeBSD version
            of &motif; when ordering! Versions for BSDI and &linux; are also
            sold by <emphasis>Xi Graphics</emphasis>. This is currently a 4
            diskette set... in the future this will change to a unified CD
            distribution like their CDE.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="cde">
          <para>Where can I get CDE for FreeBSD?</para>
        </question>

        <answer>
          <para><link linkend="xig">Xi Graphics</link> used to sell CDE
            for FreeBSD, but no longer do.</para>

          <para><ulink url="http://www.kde.org/">KDE</ulink> is an open
            source X11 desktop which is similar to CDE in many respects.
            You might also like the look and feel of <ulink
            url="http://www.xfce.org/">xfce</ulink>. KDE and xfce are both
            in the <ulink url="&url.base;/ports/index.html">ports
            system</ulink>.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="commercial-xserver">
          <para>Are there any commercial high-performance X servers?</para>
        </question>

        <answer>
          <para>Yes, <ulink url="http://www.xig.com/">Xi Graphics</ulink>
            sells Accelerated-X products for FreeBSD and other Intel based
            systems.</para>

          <para>The Xi Graphics offering is a high performance X Server
            that offers easy configuration, support for multiple concurrent
            video boards and is distributed in binary form only, in a
            unified diskette distribution for FreeBSD and &linux;. Xi
            Graphics also offers a high performance X Server tailored for
            laptop support.<anchor id="xig"></para>

          <para>There is a free <quote>compatibility demo</quote> of
            version 5.0 available.</para>

          <para>Xi Graphics also sells &motif; and CDE for FreeBSD (see
            above).</para>

            <variablelist>
              <varlistentry>
                <term>More info</term>
                <listitem>
                  <para><ulink url="http://www.xig.com/">
                    Xi Graphics WWW page</ulink></para>
                </listitem>
              </varlistentry>

              <varlistentry>
                <term>or</term>
                  <listitem>
                    <para><email>sales@xig.com</email>
                      or <email>support@xig.com</email>
                      </para>
                  </listitem>
                </varlistentry>

                <varlistentry>
                  <term>or</term>
                  <listitem>
                    <para>phone (800) 946 7433  or +1 303 298-7478.</para>
                  </listitem>
                </varlistentry>
              </variablelist>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="database-systems">
          <para>Are there any Database systems for FreeBSD?</para>
        </question>

        <answer>
          <para>Yes! See the <ulink
            url="&url.base;/commercial/software_bycat.html#CATEGORY_DATABASE">
            Commercial Vendors</ulink> section of FreeBSD's Web site.</para>

          <para>Also see the <ulink
            url="&url.base;/ports/databases.html">
            Databases</ulink> section of the Ports collection.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="oracle-support">
          <para>Can I run &oracle; on FreeBSD?</para>
        </question>

        <answer>
          <para>Yes. The following pages tell you exactly how to set up
            &linux;-&oracle; on FreeBSD:</para>

            <itemizedlist>
              <listitem>
                <para><ulink
		  url="http://www.unixcities.com/oracle/index.html">
		  http://www.unixcities.com/oracle/index.html</ulink></para>
              </listitem>

              <listitem>
                <para><ulink
		  url="http://www.shadowcom.net/freebsd-oracle9i/">
		  http://www.shadowcom.net/freebsd-oracle9i/</ulink></para>

              </listitem>
            </itemizedlist>
        </answer>
      </qandaentry>
    </qandaset>
  </chapter>

  <chapter id="applications">
    <title>ÅöáñìïãÝò Ôåëéêïý ×ñÞóôç</title>

    <qandaset>
      <qandaentry>
        <question id="user-apps">
          <para>So, where are all the user applications?</para>
        </question>

        <answer>
          <para>Please take a look at <ulink
            url="&url.base;/ports/index.html">the ports page</ulink>
            for info on software packages ported to FreeBSD.  The list
            currently tops &os.numports; and is growing daily, so come
            back to check often or subscribe to the
            <literal>freebsd-announce</literal> <link
            linkend="mailing">mailing list</link> for periodic updates
            on new entries.</para>

          <para>Most ports should work on the 4.X, 5.X, and 6.X branches.
            Each time a FreeBSD release is made, a snapshot of the
            ports tree at the time of release in also included in the
            <filename>ports/</filename> directory.</para>

          <para>We also support the concept of a
            <quote>package</quote>, essentially no more than a compressed
            binary distribution with a little extra intelligence
            embedded in it for doing whatever custom installation work
            is required. A package can be installed and uninstalled
            again easily without having to know the gory details of
            which files it includes.</para>

          <para>Use the package installation menu in
            <filename>/stand/sysinstall</filename> (under the
            post-configuration menu item) or invoke the
            &man.pkg.add.1; command on the specific package files you
            are interested in installing. Package files can usually be
            identified by their <filename>.tgz</filename> or <filename>.tbz</filename> suffix and
            CDROM distribution people will have a
            <filename>packages/All</filename> directory on their CD
            which contains such files. They can also be downloaded
            over the net for various versions of FreeBSD at the
            following locations:</para>

            <variablelist>
              <varlistentry>
                <term>for 4.X-RELEASE/4-STABLE</term>
                <listitem>
                  <para><ulink
                    url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-stable/">
                    ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-stable/</ulink></para>

                </listitem>
              </varlistentry>

              <varlistentry>
                <term>for 5.X-RELEASE/5-STABLE</term>
                <listitem>
                  <para><ulink
                    url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-5-stable/">
                    ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-5-stable</ulink></para>
                </listitem>
              </varlistentry>

              <varlistentry>
		<term>for 6.X-RELEASE/6-STABLE</term>
                <listitem>
                  <para><ulink
                    url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-6-stable/">
                    ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-6-stable</ulink></para>
                </listitem>
              </varlistentry>

              <varlistentry>
                <term>for 7-CURRENT</term>
                <listitem>
                  <para><ulink
                    url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-7-current/">
                    ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-7-current</ulink></para>
                </listitem>
              </varlistentry>
            </variablelist>

          <para>or your nearest local mirror site.</para>

          <para>Note that all ports may not be available as packages since
            new ones are constantly being added. It is always a good idea
            to check back periodically to see which packages are available
            at the <ulink
            url="ftp://ftp.FreeBSD.org/pub/FreeBSD/">ftp.FreeBSD.org</ulink>
            master site.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="configure-inn">
          <para>How do I configure INN (Internet News) for my machine?</para>
        </question>

        <answer>
          <para>After installing the <filename
            role="package">news/inn</filename> package or port, an
            excellent place to start is <ulink
            url="http://www.visi.com/~barr/INN.html">Dave
            Barr's INN Page</ulink> where you will find the INN
            FAQ.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="java">
          <para>Does FreeBSD support &java;?</para>
        </question>

        <answer>
          <para>Yes. Please see <ulink
            url="&url.base;/java/index.html">
            http://www.FreeBSD.org/java/</ulink>.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="ports-4x">
          <para>Why can I not build this port on my 4.X-STABLE machine?</para>
        </question>

        <answer>
          <para>If you are running a FreeBSD version that lags
            significantly behind -CURRENT or -STABLE, you may need to
            update your ports collection; see the <ulink
	    url="&url.books.porters-handbook;/keeping-up.html">
	    Keeping Up</ulink> section of the Porter's Handbook for further
	    information on how to do this.
            If you are up to date,
            then someone might have committed a change to the port which
            works for -CURRENT but which broke the port for -STABLE. Please
            submit a bug report on this with the
            &man.send-pr.1; command, since the ports
            collection is supposed to work for both the -CURRENT and
            -STABLE branches.</para>
        </answer>
      </qandaentry>

      <qandaentry>
	<question id="make-index">
	  <para>I just tried to build <filename>INDEX</filename>
	    using <command>make index</command>, and it failed.
	    Why?</para>
	</question>

	<answer>
	  <para>First, always make sure that you have a completely
	    up-to-date Ports Collection.  Errors that affect building
	    <filename>INDEX</filename> from an up-to-date copy of the
	    Ports Collection are high-visibility and are thus almost
	    always fixed immediately.</para>

	  <para>However, if you are up-to-date, perhaps you are seeing
	    another problem.  <command>make index</command> has a
	    known bug in dealing with incomplete copies of the Ports
	    Collection.  It assumes that you have a local copy of every
	    single port that every other port that you have a local copy
	    of depends on.  To explain, if you have a copy of
	    <filename>foo/bar</filename> on your disk, and
	    <filename>foo/bar</filename> depends on
	    <filename>baz/quux</filename>, then you must also have
	    a copy of <filename>baz/quux</filename> on your disk, and
	    the ports <filename>baz/quux</filename> depends on, and
	    so on.  Otherwise, <command>make index</command> has
	    insufficient information to create its dependency tree.</para>

	  <para>This is particularly a problem for &os; users who
	    utilize &man.cvsup.1; to track the Ports Collection but
	    choose not to install certain categories by specifying
	    them in <filename>refuse</filename>.  In theory, one
	    should be able to refuse categories, but in practice
	    there are too many ports that depend on ports in other
	    categories.  Until someone comes up with a solution for
	    this problem, the general rule is is that if you want to
	    build <filename>INDEX</filename>, you must have a complete
	    copy of the Ports Collection.</para>

	  <para>There are rare cases where <filename>INDEX</filename>
	    will not build due to odd cases involving
	    <makevar>WITH_<replaceable>*</replaceable></makevar> or
	    <makevar>WITHOUT_<replaceable>*</replaceable></makevar>
	    variables being set in <filename>make.conf</filename>.  If
	    you suspect that this is the case, please try to make
	    <filename>INDEX</filename> with those Makevars turned off
	    before reporting it to &a.ports;.</para>
	</answer>
      </qandaentry>

      <qandaentry>
        <question id="cvsup-in-base">
	  <para>Why is CVSup not integrated in the main FreeBSD tree?
	  </para>
	</question>

	<answer>
	  <para>The FreeBSD base system is designed as self-hosting - it
	    should be possible to build the whole operating system starting
	    with a very limited set of tools.  Thus, the actual build tools
	    needed to compile the FreeBSD sources are bundled with the
	    sources themselves.  This includes a C compiler (&man.gcc.1;),
	    &man.make.1;, &man.awk.1;, and similar tools.</para>

	  <para>Since CVSup is written in Modula-3, adding it to the FreeBSD
	    base system would also require adding and maintaining a Modula-3
	    compiler.  This would lead to both an increase in the disk space
	    consumed by the FreeBSD sources and additional maintenance work.
	    Thus, it is much easier for both the developers and users to
	    keep CVSup as a separate port, which can be easily installed as
	    a package bundled on the FreeBSD installation CDs.</para>
	</answer>
      </qandaentry>

      <qandaentry>
        <question id="ports-update">
           <para>I updated the sources, now how do I update my installed
             ports?</para>
        </question>

        <answer>
          <para>FreeBSD does not include a port upgrading tool, but it
            does have some tools to make the upgrade process somewhat
            easier.  You can also install additional tools to simplify
            port handling.</para>

          <para>The &man.pkg.version.1; command can generate a script
            that will update installed ports to the latest version in
            the ports tree.</para>

          <screen>&prompt.root; <userinput>pkg_version -c &gt; <replaceable>/tmp/myscript</replaceable></userinput></screen>

          <para>The output script <emphasis>must</emphasis> be edited by
            hand before you use it. Recent versions of
            &man.pkg.version.1; force this by inserting an
            &man.exit.1; at the beginning of the script.</para>

          <para>You should save the output of the script, as it will note
            packages that depend on the one that has been updated. These
            may or may not need to be updated as well. The usual case where
            they need to be updated is that a shared library has changed
            version numbers, so the ports that used that library need to be
            rebuilt to use the new version.</para>

	  <note>
	    <para>Beginning with FreeBSD 5.0 (and higher revisions),
	      &man.pkg.version.1; no longer supports the
	      <option>-c</option> option.</para>
	  </note>

          <para>If you have the disk space, you can use the
            <command>portupgrade</command> tool to automate all of
            this.  <command>portupgrade</command> includes various
            tools to simplify package handling.  It is available under
            <filename role="package">ports-mgmt/portupgrade</filename>.
            Since it is written in Ruby,
            <command>portupgrade</command> is an unlikely candidate for
            integration with the main FreeBSD tree.  That should not
            stop anyone from using it, however.</para>

          <para>If your system is up full time, the &man.periodic.8; system
            can be used to generate a weekly list of ports that might need
            updating by setting
            <literal>weekly_status_pkg_enable="YES"</literal> in
            <filename>/etc/periodic.conf</filename>.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="minimal-sh">
          <para>Why is <command>/bin/sh</command> so minimal?  Why does
            FreeBSD not use <command>bash</command> or another shell?</para>
        </question>

        <answer>
          <para>Because &posix; says that there shall be such a shell.</para>

          <para>The more complicated answer: many people need to write shell
            scripts which will be portable across many systems. That is why
            &posix; specifies the shell and utility commands in great detail.
            Most scripts are written in Bourne shell, and because several
            important programming interfaces (&man.make.1;, &man.system.3;,
            &man.popen.3;, and analogues in higher-level scripting
            languages like Perl and Tcl) are specified to use the Bourne
            shell to interpret commands. Because the Bourne shell is so
            often and widely used, it is important for it to be quick to
            start, be deterministic in its behavior, and have a small
            memory footprint.</para>

          <para>The existing implementation is our best effort at meeting as
            many of these requirements simultaneously as we can. In order to
            keep <command>/bin/sh</command> small, we have not provided many
            of the convenience features that other shells have. That is why the
            Ports Collection includes more featureful shells like bash, scsh,
            tcsh, and zsh.  (You can compare for yourself the memory
            utilization of all these shells by looking at the
            <quote>VSZ</quote> and <quote>RSS</quote> columns in a <command>ps
              -u</command> listing.)</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="netscape-slow-startup">
          <para>Why do &netscape; and Opera take so long to
            start?</para>
        </question>

        <answer>
          <para>The usual answer is that DNS on your system is
            misconfigured.  Both &netscape; and Opera perform DNS checks
            when starting up.  The browser will not appear on your
            desktop until the program either gets a response or
            determines that the system has no network
            connection.</para>
        </answer>
      </qandaentry>

      <qandaentry>
	<question id="ports-base-update">
	  <para>I updated parts of the Ports Collection using CVSup, and
	    now many ports fail to build with mysterious error messages!
	    What happened?  Is the Ports Collection broken in some major
	    way?</para>
	</question>

	<answer>
	  <para>If you only update parts of the Ports Collection, using
	    one of its CVSup subcollections and not the
	    <literal>ports-all</literal> CVSup collection, you should
	    <emphasis>always</emphasis> update the
	    <literal>ports-base</literal> subcollection too!  The reasons
	    are described <ulink
	    url="&url.books.handbook;/cvsup.html#CVSUP-COLLEC-PBASE-WARN">in the
	    Handbook</ulink>.</para>
	</answer>
      </qandaentry>

      <qandaentry>
	<question id="midi-sound-files">
	  <para>How do I create audio CDs from my MIDI files?</para>
	</question>

	<answer><para>To create audio CDs from MIDI files, first
          install <filename role="package">audio/timidity++</filename>
          from ports then install manually the GUS patches set by Eric
          A. Welsh, available at <ulink
          url="http://www.stardate.bc.ca/eawpatches/html/default.htm"></ulink>.
          After timidity++ has been installed properly, midi files may
          be converted to wav files with the following command
          line:</para>

        <screen>&prompt.user; <userinput>timidity -Ow -s 44100 -o /tmp/juke/01.wav 01.mid</userinput></screen>

          <para>The wav files can then be converted to other formats
            or burned onto audio CDs, as described in the FreeBSD
            Handbook.</para>
        </answer>
      </qandaentry>
    </qandaset>
  </chapter>

  <chapter id="kernelconfig">
    <title>Ñýèìéóç ÐõñÞíá</title>

    <qandaset>
      <qandaentry>
        <question id="make-kernel">
          <para>I would like to customize my kernel. Is it difficult?</para>
        </question>

        <answer>
          <para>Not at all! Check out the <ulink
            url="&url.books.handbook;/kernelconfig.html">
            kernel config section of the Handbook</ulink>.</para>

            <note>
	      <para>We recommend that you make a dated snapshot of
	        your new <filename>/kernel</filename> called
	        <filename>/kernel.YYMMDD</filename> after you get it
	        working properly.  Also back up your new
	        <filename>/modules</filename> directory to
	        <filename>/modules.YYMMDD</filename>.  That way, if
	        you make a mistake the next time you play with your
	        configuration you can boot the backup kernel instead
	        of having to fall back to
	        <filename>kernel.GENERIC</filename>. This is
	        particularly important if you are now booting from a
	        controller that GENERIC does not support.</para>
            </note>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="missing-hw-float">
          <para>My kernel compiles fail because
            <literal>_hw_float</literal> is missing.  How do I solve
            this problem?</para>
        </question>

        <answer>
          <para>You probably removed <devicename>npx0</devicename>
            (see &man.npx.4;) from your kernel configuration file
            because you do not have a math co-processor.  The
            <devicename>npx0</devicename> device is
            <emphasis>MANDATORY</emphasis>.  Somewhere inside your
            hardware lies a device that provides hardware
            floating-point support, even if it is no longer a separate
            device as used in the good old 386 days.  You
            <emphasis>must</emphasis> include the
            <devicename>npx0</devicename> device.  Even if you manage
            to build a kernel without <devicename>npx0</devicename>
            support, it will not boot anyway. </para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="why-kernel-big">
          <para>Why is my kernel so big (over 10MB)?</para>
        </question>

        <answer>
          <para>Chances are, you compiled your kernel in
            <emphasis>debug mode</emphasis>.  Kernels built in debug
            mode contain many symbols that are used for debugging,
            thus greatly increasing the size of the kernel.  Note that
            there will be little or no performance decrease from
            running a debug kernel, and it is useful to keep one
            around in case of a system panic.</para>

          <para>However, if you are running low on disk space, or
            you simply do not want to run a debug kernel, make sure
            that both of the following are true:</para>

          <itemizedlist>
            <listitem>
              <para>You do not have a line in your kernel
                configuration file that reads:</para>

              <programlisting>makeoptions DEBUG=-g</programlisting>
            </listitem>

            <listitem>
              <para>You are not running &man.config.8; with
                the <option>-g</option> option.</para>
            </listitem>
          </itemizedlist>

          <para>Either of the above settings will cause your kernel to
            be built in debug mode.  As long as you make sure you
            follow the steps above, you can build your kernel
            normally, and you should notice a fairly large size
            decrease; most kernels tend to be around 1.5MB to
            2MB.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="multiport-serial-interrupts">
          <para>Why do I get interrupt conflicts with multi-port serial
            code?</para>
        </question>

        <answer>
          <para>When I compile a kernel
            with multi-port serial code, it tells me that only the first
            port is probed and the rest skipped due to interrupt conflicts.
            How do I fix this?</para>

          <para>The problem here is that
            FreeBSD has code built-in to keep the kernel from getting
            trashed due to hardware or software conflicts. The way to fix
            this is to leave out the IRQ settings on all but one port. Here
            is an example:</para>

          <programlisting>#
# Multiport high-speed serial line - 16550 UARTS
#
device sio2 at isa? port 0x2a0 tty irq 5 flags 0x501 vector siointr
device sio3 at isa? port 0x2a8 tty flags 0x501 vector siointr
device sio4 at isa? port 0x2b0 tty flags 0x501 vector siointr
device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="generic-kernel-build-failure">
          <para>Why does every kernel I try to build fail to compile, even
            GENERIC?</para>
        </question>

        <answer>
          <para>There are a number of possible causes for this problem.
            They are, in no particular order:</para>

          <itemizedlist>
            <listitem>
              <para>You are not using the new <command>make
                buildkernel</command> and <command>make
                installkernel</command> targets, and your source tree is
                different from the one used to build the currently running
                system (e.g., you are compiling 4.3-RELEASE on a 4.0-RELEASE
                system).  If you are attempting an upgrade, please read the
                <filename>/usr/src/UPDATING</filename> file, paying
                particular attention to the <quote>COMMON ITEMS</quote>
                section at the end.</para>
            </listitem>

            <listitem>
              <para>You are using the new <command>make
                buildkernel</command> and <command>make
                installkernel</command> targets, but you failed to assert
                the completion of the <command>make buildworld</command>
                target.  The <command>make buildkernel</command> target
                relies on files generated by the <command>make
                buildworld</command> target to complete its job
                correctly.</para>
            </listitem>

            <listitem>
              <para>Even if you are trying to build <link
                linkend="stable">FreeBSD-STABLE</link>, it is possible that
                you fetched the source tree at a time when it was either
                being modified, or broken for other reasons; only releases
                are absolutely guaranteed to be buildable, although <link
                linkend="stable">FreeBSD-STABLE</link> builds fine the
                majority of the time.  If you have not already done so, try
                re-fetching the source tree and see if the problem goes
                away.  Try using a different server in case the one you are
                using is having problems.</para>
            </listitem>
          </itemizedlist>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="scheduler-in-use">
          <para>How can I verify which scheduler is in use on a
            running system?</para>
        </question>

        <answer>
	  <para>If you are running &os; version 5.2.1 or earlier, check for
	    the existence of the <literal>kern.quantum</literal> sysctl.
	    If you have it, you should see something like this:</para>

	  <screen>&prompt.user; sysctl <replaceable>kern.quantum</replaceable>
kern.sched.quantum: 99960</screen>

	  <para>If the <literal>kern.quantum</literal> sysctl exists, you are
	    using the 4BSD scheduler.  If not, you will get an error printed
	    by &man.sysctl.8; (which you can safely ignore):</para>

	    <screen>&prompt.user; sysctl <replaceable>kern.sched.quantum</replaceable>
sysctl: unknown oid 'kern.sched.quantum'</screen>

	  <para>In &os; version 5.3-RELEASE and later, the name of the
	    scheduler currently being used is directly available as the value
	    of the <literal>kern.sched.name</literal> sysctl:</para>

	  <screen>&prompt.user; sysctl <replaceable>kern.sched.name</replaceable>
kern.sched.name: 4BSD</screen>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="scheduler-kern-quantum">
          <para>What is <literal>kern.quantum</literal>?</para>
        </question>

        <answer>
          <para><literal>kern.quantum</literal> is the maximum number of
            ticks a process can run without being preempted.  It is
            specific to the 4BSD scheduler, so you can use its
            presence or absence to determine which scheduler is in
            use.  In &os; 5.X or later <literal>kern.quantum</literal> has
	    been renamed to <literal>kern.sched.quantum</literal>.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="scheduler-kern-sched-quantum">
	  <para>What is <literal>kern.sched.quantum</literal>?</para>
	</question>

	<answer>
	  <para>See <xref linkend="scheduler-kern-quantum"></para>
	</answer>
      </qandaentry>
    </qandaset>
  </chapter>

  <chapter id="disks">
    <title>Äßóêïé, ÓõóôÞìáôá Áñ÷åßùí êáé ÖïñôùôÝò Åêêßíçóçò</title>

    <qandaset>
      <qandaentry>
        <question id="adding-disks">
          <para>How can I add my new hard disk to my FreeBSD system?</para>
        </question>

        <answer>
          <para>See the Disk Formatting Tutorial at <ulink
            url="&url.articles.formatting-media;/index.html">
            www.FreeBSD.org</ulink>.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="new-huge-disk">
          <para>How do I move my system over to my huge new disk?</para>
        </question>

        <answer>
          <para>The best way is to reinstall the OS on the new
            disk, then move the user data over.  This is highly
            recommended if you have been tracking -STABLE for more
            than one release, or have updated a release instead of
            installing a new one.  You can install booteasy on both
            disks with &man.boot0cfg.8;, and dual boot them until
            you are happy with the new configuration.  Skip the
            next paragraph to find out how to move the data after
            doing this.</para>

          <para>Should you decide not to do a fresh install, you
            need to partition and label the new disk with either
            <filename>/stand/sysinstall</filename>, or &man.fdisk.8;
            and &man.disklabel.8;.  You should also install booteasy
            on both disks with &man.boot0cfg.8;, so that you can
            dual boot to the old or new system after the copying
            is done.  See the <ulink
            url="&url.articles.formatting-media;/index.html">
            formatting-media article</ulink> for details on this
            process.</para>

          <para>Now you have the new disk set up, and are ready
            to move the data.  Unfortunately, you cannot just blindly
            copy the data.  Things like device files (in
	    <filename>/dev</filename>), flags, and links tend to
            screw that up.  You need to use tools that understand
            these things, which means &man.dump.8;.
            Although it is suggested that you move the data in single user
            mode, it is not required.</para>

          <para>You should never use anything but &man.dump.8; and
            &man.restore.8; to move the root filesystem.  The
            &man.tar.1; command may work - then again, it may not.
            You should also use &man.dump.8; and &man.restore.8;
            if you are moving a single partition to another empty
            partition.  The sequence of steps to use dump to move
            a partitions data to a new partition is:</para>

          <procedure>
            <step>
              <para>newfs the new partition.</para>
            </step>

            <step>
              <para>mount it on a temporary mount point.</para>
            </step>

            <step>
              <para>cd to that directory.</para>
            </step>

            <step>
              <para>dump the old partition, piping output to the
                new one.</para>
            </step>
          </procedure>

          <para>For example, if you are going to move root to
            <devicename>/dev/ad1s1a</devicename>, with
            <filename>/mnt</filename> as the temporary mount point,
            it is:</para>

          <screen>&prompt.root; <userinput>newfs /dev/ad1s1a</userinput>
&prompt.root; <userinput>mount /dev/ad1s1a /mnt</userinput>
&prompt.root; <userinput>cd /mnt</userinput>
&prompt.root; <userinput>dump 0af - / | restore xf -</userinput></screen>

          <para>Rearranging your partitions with dump takes a bit more
            work. To merge a partition like <filename>/var</filename>
            into its parent, create the new partition large enough
            for both, move the parent partition as described above,
            then move the child partition into the empty directory
            that the first move created:</para>
	  
          <screen>&prompt.root; <userinput>newfs /dev/ad1s1a</userinput>
&prompt.root; <userinput>mount /dev/ad1s1a /mnt</userinput>
&prompt.root; <userinput>cd /mnt</userinput>
&prompt.root; <userinput>dump 0af - / | restore xf -</userinput>
&prompt.root; <userinput>cd var</userinput>
&prompt.root; <userinput>dump 0af - /var | restore xf -</userinput></screen>

	  <para>To split a directory from its parent, say putting
	    <filename>/var</filename> on its own partition when it was not
	    before, create both partitions, then mount the child partition
	    on the appropriate directory in the temporary mount point, then
	    move the old single partition:</para>

          <screen>&prompt.root; <userinput>newfs /dev/ad1s1a</userinput>
&prompt.root; <userinput>newfs /dev/ad1s1d</userinput>
&prompt.root; <userinput>mount /dev/ad1s1a /mnt</userinput>
&prompt.root; <userinput>mkdir /mnt/var</userinput>
&prompt.root; <userinput>mount /dev/ad1s1d /mnt/var</userinput>
&prompt.root; <userinput>cd /mnt</userinput>
&prompt.root; <userinput>dump 0af - / | restore xf -</userinput></screen>

          <para>You might prefer &man.cpio.1;, &man.pax.1;,
            &man.tar.1; to &man.dump.8; for user data. At the time of
            this writing, these are known to lose file flag information,
            so use them with caution.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="dangerously-dedicated">
          <para>Will a <quote>dangerously dedicated</quote> disk endanger
            my health?</para>
        </question>

        <answer>

          <para><anchor id="dedicate">The installation procedure allows
            you to chose two different methods in partitioning your
            hard disk(s). The default way makes it compatible with other
            operating systems on the same machine, by using fdisk table
            entries (called <quote>slices</quote> in FreeBSD), with a
            FreeBSD slice that employs partitions of its own. Optionally,
            one can chose to install a boot-selector to switch between the
            possible operating systems on the disk(s). The alternative uses
            the entire disk for FreeBSD, and makes no attempt to be
            compatible with other operating systems.</para>

          <para>So why it is called <quote>dangerous</quote>?  A disk
            in this mode does not contain what normal PC utilities
            would consider a valid fdisk table. Depending on how well
            they have been designed, they might complain at you once
            they are getting in contact with such a disk, or even
            worse, they might damage the BSD bootstrap without even
            asking or notifying you. In addition, the
            <quote>dangerously dedicated</quote> disk's layout is
            known to confuse many BIOSes, including those from AWARD
            (e.g. as found in HP Netserver and Micronics systems as
            well as many others) and Symbios/NCR (for the popular
            53C8xx range of SCSI controllers). This is not a complete
            list, there are more. Symptoms of this confusion include
            the <errorname>read error</errorname> message printed by
            the FreeBSD bootstrap when it cannot find itself, as well
            as system lockups when booting.</para>

          <para>Why have this mode at all then?  It only saves a few kbytes
            of disk space, and it can cause real problems for a new
            installation. <quote>Dangerously dedicated</quote> mode's
            origins lie in a desire to avoid one of the most common
            problems plaguing new FreeBSD installers - matching the BIOS
            <quote>geometry</quote> numbers for a disk to the disk
            itself.</para>

          <para><quote>Geometry</quote> is an outdated concept, but one
            still at the heart of the PC's BIOS and its interaction with
            disks. When the FreeBSD installer creates slices, it has to
            record the location of these slices on the disk in a fashion
            that corresponds with the way the BIOS expects to find them. If
            it gets it wrong, you will not be able to boot.</para>

          <para><quote>Dangerously dedicated</quote> mode tries to work
            around this by making the problem simpler. In some cases, it
            gets it right. But it is meant to be used as a last-ditch
            alternative - there are better ways to solve the problem 99
            times out of 100.</para>

          <para>So, how do you avoid the need for <quote>DD</quote> mode
            when you are installing? Start by making a note of the geometry
            that your BIOS claims to be using for your disks. You can
            arrange to have the kernel print this as it boots by specifying
            <option>-v</option> at the <literal>boot:</literal> prompt, or
            using <command>boot -v</command> in the loader. Just before the
            installer starts, the kernel will print a list of BIOS
            geometries. Do not panic - wait for the installer to start and
            then use scrollback to read the numbers. Typically the BIOS
            disk units will be in the same order that FreeBSD lists your
            disks, first IDE, then SCSI.</para>

          <para>When you are slicing up your disk, check that the disk
            geometry displayed in the FDISK screen is correct (ie. it
            matches the BIOS numbers); if it is wrong, use the
            <keycap>g</keycap> key to fix it. You may have to do this if
            there is absolutely nothing on the disk, or if the disk has been
            moved from another system. Note that this is only an issue with
            the disk that you are going to boot from; FreeBSD will sort
            itself out just fine with any other disks you may have.</para>

          <para>Once you have got the BIOS and FreeBSD agreeing about the
            geometry of the disk, your problems are almost guaranteed to be
            over, and with no need for <quote>DD</quote> mode at all. If,
            however, you are still greeted with the dreaded <errorname>read
            error</errorname> message when you try to boot, it is time to cross
            your fingers and go for it - there is nothing left to
            lose.</para>

          <para>To return a <quote>dangerously dedicated</quote> disk
            for normal PC use, there are basically two options. The first
            is, you write enough NULL bytes over the MBR to make any
            subsequent installation believe this to be a blank disk. You
            can do this for example with</para>

          <screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/rda0 count=15</userinput></screen>

          <para>Alternatively, the undocumented DOS
            <quote>feature</quote></para>

          <screen><prompt>C:\&gt;</prompt> <userinput>fdisk /mbr</userinput></screen>

          <para>will to install a new master boot record as well, thus
            clobbering the BSD bootstrap.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="safe-softupdates">
          <para>Which partitions can safely use Soft Updates?  I have
            heard that Soft Updates on <filename>/</filename> can cause
            problems.</para>
        </question>

        <answer>
          <para>Short answer: you can usually use Soft Updates safely
            on all partitions.</para>

          <para>Long answer: There used to be some concern over using
            Soft Updates on the root partition.  Soft Updates has two
            characteristics that caused this.  First, a Soft Updates
            partition has a small chance of losing data during a
            system crash.  (The partition will not be corrupted; the
            data will simply be lost.)  Also, Soft Updates can cause
            temporary space shortages.</para>

          <para>When using Soft Updates, the kernel can take up to
            thirty seconds to actually write changes to the physical
            disk.  If you delete a large file, the file still resides
            on disk until the kernel actually performs the deletion.
            This can cause a very simple race condition.  Suppose you
            delete one large file and immediately create another large
            file.  The first large file is not yet actually removed
            from the physical disk, so the disk might not have enough
            room for the second large file.  You get an error that the
            partition does not have enough space, although you know
            perfectly well that you just released a large chunk of
            space!  When you try again mere seconds later, the file
            creation works as you expect.  This has left more than one
            user scratching his head and doubting his sanity, the
            FreeBSD filesystem, or both.</para>

          <para>If a system should crash after the kernel accepts a
            chunk of data for writing to disk, but before that data is
            actually written out, data could be lost or corrupted.
            This risk is extremely small, but generally manageable.
            Use of IDE write caching greatly increases this risk; it
            is strongly recommended that you disable IDE write caching
            when using Soft Updates.</para>

          <para>These issues affect all partitions using Soft Updates.
            So, what does this mean for the root partition?</para>

          <para>Vital information on the root partition changes very
            rarely.  Files such as <filename>/kernel</filename> and
            the contents of <filename>/etc</filename> only change
            during system maintenance, or when users change their
            passwords.  If the system crashed during the
            thirty-second window after such a change is made, it is
            possible that data could be lost.  This risk is negligible
            for most applications, but you should be aware that it
            exists.  If your system cannot tolerate this much risk,
            do not use Soft Updates on the root filesystem!</para>

          <para><filename>/</filename> is traditionally one of the
            smallest partitions.  By default, FreeBSD puts the
            <filename>/tmp</filename> directory on
            <filename>/</filename>.  If you have a busy
            <filename>/tmp</filename>, you might see intermittent
            space problems.  Symlinking <filename>/tmp</filename> to
            <filename>/var/tmp</filename> will solve this
            problem.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="inappropriate-ccd">
          <para>What is inappropriate about my ccd?</para>
        </question>

        <answer>
          <para>The symptom of this is:</para>

          <screen>&prompt.root; <userinput>ccdconfig -C</userinput>
ccdconfig: ioctl (CCDIOCSET): /dev/ccd0c: Inappropriate file type or format</screen>

          <para>This usually happens when you are trying to concatenate
            the <literal>c</literal> partitions, which default to type
            <literal>unused</literal>. The ccd driver requires the
            underlying partition type to be FS_BSDFFS. Edit the disklabel
            of the disks you are trying to concatenate and change the types
            of partitions to <literal>4.2BSD</literal>.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="ccd-disklabel">
          <para>Why can I not edit the disklabel on my ccd?</para>
        </question>

        <answer>
          <para>The symptom of this is:</para>

          <screen>&prompt.root; <userinput>disklabel ccd0</userinput>
(it prints something sensible here, so let us try to edit it)
&prompt.root; <userinput>disklabel -e ccd0</userinput>
(edit, save, quit)
disklabel: ioctl DIOCWDINFO: No disk label on disk;
use "disklabel -r" to install initial label</screen>

          <para>This is because the disklabel returned by ccd is actually
            a <quote>fake</quote> one that is not really on the disk.
            You can solve this problem by writing it back explicitly,
            as in:</para>

          <screen>&prompt.root; <userinput>disklabel ccd0 &gt; /tmp/disklabel.tmp</userinput>
&prompt.root; <userinput>disklabel -Rr ccd0 /tmp/disklabel.tmp</userinput>
&prompt.root; <userinput>disklabel -e ccd0</userinput>
(this will work now)</screen>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="mount-foreign-fs">
          <para>Can I mount other foreign filesystems under FreeBSD?</para>
        </question>

        <answer>
	  <para>FreeBSD supports a variety of other
	    filesystems.</para>

          <variablelist>
            <varlistentry>
              <term>Digital UNIX</term>

              <listitem>
                <para>UFS CDROMs can be mounted directly on FreeBSD.
                  Mounting disk partitions from Digital UNIX and other
                  systems that support UFS may be more complex, depending
                  on the details of the disk partitioning for the operating
                  system in question.</para>
              </listitem>
            </varlistentry>

            <varlistentry>
              <term>&linux;</term>

              <listitem>
                <para>FreeBSD supports <literal>ext2fs</literal>
                  partitions.  See &man.mount.ext2fs.8; for more
                  information.</para>
              </listitem>
            </varlistentry>

            <varlistentry>
              <term>&windowsnt;</term>

              <listitem>
                <para>FreeBSD includes a read-only NTFS driver.  For
		  more information, see &man.mount.ntfs.8;.
                </para>
              </listitem>
            </varlistentry>

	    <varlistentry>
	      <term>FAT</term>

	      <listitem>
		<para>FreeBSD includes a read-write FAT driver.  For
                  more information, see &man.mount.msdosfs.8;.</para>
  	      </listitem>
  	    </varlistentry>

	    <varlistentry>
	      <term>ReiserFS</term>

	      <listitem>
		<para>FreeBSD includes a read-only ReiserFS driver.  For
		  more information, see &man.mount.reiserfs.8;.</para>
	      </listitem>
	    </varlistentry>
          </variablelist>

          <para>FreeBSD also supports network filesystems such as NFS
            (see &man.mount.nfs.8;), NetWare (see &man.mount.nwfs.8;),
            and Microsoft-style SMB filesystems (see
            &man.mount.smbfs.8;).
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="mount-dos">
          <para>How do I mount a secondary DOS partition?</para>
        </question>

        <answer>

        <para>The secondary DOS partitions are found after ALL the
          primary partitions. For example, if you have an
          <quote>E</quote> partition as the second DOS partition on
          the second SCSI drive, you need to create the special files
          for <quote>slice 5</quote> in <filename>/dev</filename>,
          then mount <devicename>/dev/da1s5</devicename>:</para>

        <screen>&prompt.root; <userinput>cd /dev</userinput>
&prompt.root; <userinput>sh MAKEDEV da1s5</userinput>
&prompt.root; <userinput>mount -t msdos /dev/da1s5 /dos/e</userinput></screen>

        <note>
	  <para>You can omit this step if you are running FreeBSD
	    5.0-RELEASE or newer with &man.devfs.5;
	    enabled.</para>
	</note>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="crypto-filesystem">
          <para>Is there a cryptographic filesystem for &os;?</para>
        </question>

        <answer>

          <para>Yes.  FreeBSD 5.0 includes &man.gbde.8;, and FreeBSD 6.0
            added &man.geli.8;.  For earlier releases, see the <filename
            role="package">security/cfs</filename> port.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="nt-bootloader">
          <para>How can I use the &windowsnt; loader to boot FreeBSD?</para>
        </question>

        <answer>
          <para>The general idea is that you copy the first sector of your
            native root FreeBSD partition into a file in the DOS/&windowsnt;
            partition. Assuming you name that file something like
            <filename>c:\bootsect.bsd</filename> (inspired by
            <filename>c:\bootsect.dos</filename>), you can then edit the
            <filename>c:\boot.ini</filename> file to come up with something
            like this:</para>

          <programlisting>[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows NT"
C:\BOOTSECT.BSD="FreeBSD"
C:\="DOS"</programlisting>

          <para>If FreeBSD is installed on the same disk as the &windowsnt; boot
            partition simply copy <filename>/boot/boot1</filename> to
            <filename>C:\BOOTSECT.BSD</filename>. However, if FreeBSD is
            installed on a different disk <filename>/boot/boot1</filename>
            will not work, <filename>/boot/boot0</filename> is needed.</para>

          <para><filename>/boot/boot0</filename> needs to be installed
            using sysinstall by selecting the FreeBSD boot manager on
            the screen which asks if you wish to use a boot
            manager. This is because <filename>/boot/boot0</filename>
            has the partition table area filled with NULL characters
            but sysinstall copies the partition table before copying
            <filename>/boot/boot0</filename> to the MBR.</para>

            <warning>
              <para><emphasis>Do not simply copy <filename>/boot/boot0</filename>
                instead of <filename>/boot/boot1</filename>; you will
                overwrite your partition table and render your computer
                un-bootable!</emphasis></para>
            </warning>

          <para>When the FreeBSD boot manager runs it records the last
            OS booted by setting the active flag on the partition table
            entry for that OS and then writes the whole 512-bytes of itself
            back to the MBR so if you just copy
            <filename>/boot/boot0</filename> to
            <filename>C:\BOOTSECT.BSD</filename> then it writes an empty
            partition table, with the active flag set on one entry, to the
            MBR.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="lilo-bootloader">
          <para>How do I boot FreeBSD and &linux; from LILO?</para>
        </question>

        <answer>
          <para>If you have FreeBSD and &linux; on the same disk, just follow
            LILO's installation instructions for booting a non-&linux;
            operating system.  Very briefly, these are:</para>

          <para>Boot &linux;, and add the following lines to
            <filename>/etc/lilo.conf</filename>:</para>

            <programlisting>other=/dev/hda2
        table=/dev/hda
        label=FreeBSD</programlisting>

          <para>(the above assumes that your FreeBSD slice is known to
            &linux; as <devicename>/dev/hda2</devicename>; tailor to
            suit your setup).  Then, run <command>lilo</command> as
            <username>root</username> and you should be done.</para>

          <para>If FreeBSD resides on another disk, you need to add
            <literal>loader=/boot/chain.b</literal> to the LILO entry.
            For example:</para>

          <programlisting>other=/dev/dab4
        table=/dev/dab
        loader=/boot/chain.b
        label=FreeBSD</programlisting>

          <para>In some cases you may need to specify the BIOS drive number
            to the FreeBSD boot loader to successfully boot off the second
            disk.  For example, if your FreeBSD SCSI disk is probed by BIOS
            as BIOS disk 1, at the FreeBSD boot loader prompt you need to
            specify:</para>

          <screen>Boot: <userinput>1:da(0,a)/kernel</userinput></screen>

          <para>You can configure
            &man.boot.8;
            to automatically do this for you at boot time.</para>

          <para>The <ulink
            url="http://sunsite.unc.edu/LDP/HOWTO/mini/Linux+FreeBSD.html">
            &linux;+FreeBSD mini-HOWTO</ulink> is a good reference for
	    FreeBSD and &linux; interoperability issues.</para>
        </answer>
      </qandaentry>

      <qandaentry>
	<question id="grub-loader">
	  <para>How do I boot &os; and &linux; using GRUB</para>
        </question>

	<answer>
	  <para>Booting &os; using GRUB is very simple.  Just
	    add the following to your configuration file
	    <filename>/boot/grub/grub.conf</filename>.</para>
	  
	  <programlisting>title FreeBSD 6.1
	root (hd0,a)
	kernel /boot/loader
	  </programlisting>

	  <para>Where <literal>hd0,a</literal> points to your root partition
	    on the first disk.  If you need to specify which slice number
	    should be used, use something like this <literal>(hd0,2,a)</literal>.
	    By default, if the slice number is omitted, GRUB searches the
	    first slice which has <literal>'a'</literal> partition.</para>
	</answer>
      </qandaentry>

      <qandaentry>
        <question id="booteasy-loader">
          <para>How do I boot FreeBSD and &linux; using BootEasy?</para>
        </question>

        <answer>
          <para>Install LILO at the start of your &linux; boot partition
            instead of in the Master Boot Record.   You can then boot LILO
            from BootEasy.</para>

          <para>If you are running &windows; 95 and &linux; this is recommended
            anyway, to make it simpler to get &linux; booting again if you
            should need to reinstall &windows; 95 (which is a Jealous
            Operating System, and will bear no other Operating Systems in
            the Master Boot Record).</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="changing-bootprompt">
          <para>How do I change the boot prompt from <literal>???</literal> to
            something more meaningful?</para>
        </question>

        <answer>
          <para>You can not do that with the standard boot manager without
            rewriting it. There are a number of other boot managers
            in the <filename>sysutils</filename> ports category that
            provide this functionality.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="removable-drives">
          <para>I have a new removable drive, how do I use it?</para>
        </question>

        <answer>

          <para>Whether it is a removable drive like a &iomegazip; or an EZ drive
            (or even a floppy, if you want to use it that way), or a new
            hard disk, once it is installed and recognized by the system,
            and you have your cartridge/floppy/whatever slotted in, things
            are pretty much the same for all devices.</para>

          <para>(this section is based on <ulink
            url="http://www.vmunix.com/mark/FreeBSD/ZIP-FAQ.html">
            Mark Mayo's ZIP FAQ</ulink>)</para>

          <para>If it is a ZIP drive or a floppy, you have already got a DOS
            filesystem on it, you can use a command like this:</para>

          <screen>&prompt.root; <userinput>mount -t msdos /dev/fd0c /floppy</userinput></screen>

          <para>if it is a floppy, or this:</para>

          <screen>&prompt.root; <userinput>mount -t msdos /dev/da2s4 /zip</userinput></screen>

          <para>for a ZIP disk with the factory configuration.</para>

          <para>For other disks, see how they are laid out using
            &man.fdisk.8; or
            &man.sysinstall.8;.</para>

          <para>The rest of the examples will be for a ZIP drive on da2,
            the third SCSI disk.</para>

          <para>Unless it is a floppy, or a removable you plan on sharing
            with other people, it is probably a better idea to stick a BSD
            filesystem on it. You will get long filename support, at least a
            2X improvement in performance, and a lot more stability. First,
            you need to redo the DOS-level partitions/filesystems. You can
            either use &man.fdisk.8; or
            <filename>/stand/sysinstall</filename>, or for a small drive
            that you do not want to bother with multiple operating system
            support on, just blow away the whole FAT partition table
            (slices) and just use the BSD partitioning:</para>

          <screen>&prompt.root; <userinput>dd if=/dev/zero of=/dev/rda2 count=2</userinput>
&prompt.root; <userinput>disklabel -Brw da2 auto</userinput></screen>

          <para>You can use disklabel or
            <filename>/stand/sysinstall</filename> to create multiple BSD
            partitions. You will certainly want to do this if you are adding
            swap space on a fixed disk, but it is probably irrelevant on a
            removable drive like a ZIP.</para>

          <para>Finally, create a new filesystem, this one is on our ZIP
            drive using the whole disk:</para>

          <screen>&prompt.root; <userinput>newfs /dev/rda2c</userinput></screen>

          <para>and mount it:</para>

          <screen>&prompt.root; <userinput>mount /dev/da2c /zip</userinput></screen>

          <para>and it is probably a good idea to add a line like this
            to <filename>/etc/fstab</filename> (see &man.fstab.5;) so
            you can just type <command>mount /zip</command> in the
            future:</para>

          <programlisting>/dev/da2c /zip ffs rw,noauto 0 0</programlisting>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="mount-cd-superblock">
          <para>Why do I get <errorname>Incorrect super block</errorname> when
            mounting a CDROM?</para>
        </question>

        <answer>
          <para>You have to tell &man.mount.8; the type of the device
            that you want to mount.  This is described in the <ulink
            url="&url.books.handbook;/creating-cds.html"> Handbook section on
            optical media</ulink>, specifically the section <ulink
            url="&url.books.handbook;/creating-cds.html#MOUNTING-CD">Using Data
            CDs</ulink>.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="cdrom-not-configured">
          <para>Why do I get <errorname>Device not
            configured</errorname> when mounting a CDROM?</para>
        </question>

        <answer>
          <para>This generally means that there is no CDROM in the
            CDROM drive, or the drive is not visible on the
            bus. Please see the <ulink
            url="&url.books.handbook;/creating-cds.html#MOUNTING-CD">Using Data
            CDs</ulink> section of the Handbook for a detailed
            discussion of this issue.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="cdrom-unicode-filenames">
          <para>Why do all non-English characters in filenames show up as
            <quote>?</quote> on my CDs when mounted in FreeBSD?</para>
        </question>

        <answer>
          <para>Your CDROM probably uses the <quote>Joliet</quote>
            extension for storing information about files and
            directories.  This is discussed in the Handbook chapter on
            <ulink url="&url.books.handbook;/creating-cds.html">creating and
            using CDROMs</ulink>, specifically the section on <ulink
            url="&url.books.handbook;/creating-cds.html#MOUNTING-CD">Using Data
            CDROMs</ulink>.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="burncd-isofs">
          <para>I burned a CD under FreeBSD and now I can not read it
            under any other operating system. Why?</para>
        </question>
  
        <answer>
          <para>You most likely burned a raw file to your CD, rather
            than creating an ISO 9660 filesystem.  Take a look at the
            <ulink url="&url.books.handbook;/creating-cds.html">Handbook
            chapter on creating CDROMs</ulink>, particularly the
            section on <ulink
            url="&url.books.handbook;/creating-cds.html#RAWDATA-CD">burning raw
            data CDs</ulink>.</para>
	</answer>
      </qandaentry>

      <qandaentry>
        <question id="copy-cd">
          <para>How can I create an image of a data CD?</para>
        </question>

        <answer>
          <para>This is discussed in the Handbook section on <ulink
            url="&url.books.handbook;/creating-cds.html#IMAGING-CD">duplicating
            data CDs</ulink>. For more on working with CDROMs, see the
            <ulink url="&url.books.handbook;/creating-cds.html">Creating CDs
            Section</ulink> in the Storage chapter in the
            Handbook.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="mount-audio-CD">
          <para>Why can I not <command>mount</command> an audio
          CD?</para>
         </question>

        <answer>
          <para>If you try to mount an audio CD, you will get an error
            like <errorname>cd9660: /dev/acd0c: Invalid
            argument</errorname>.  This is because
            <command>mount</command> only works on filesystems.  Audio
            CDs do not have filesystems; they just have data.  You
            need a program that reads audio CDs, such as the
            <filename role="package">audio/xmcd</filename> port.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="multi-session-CD">
          <para>How do I <command>mount</command> a multi-session CD?</para>
        </question>

        <answer>
          <para>By default, &man.mount.8; will attempt to mount the
            last data track (session) of a CD.  If you would like to
            load an earlier session, you must use the
            <option>-s</option> command line argument.  Please see
            &man.mount.cd9660.8; for specific examples.</para>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="user-floppymount">
          <para>How do I let ordinary users mount floppies, CDROMs and
            other removable media?</para>
        </question>

        <answer>
          <para>Ordinary users can be permitted to mount devices. Here is
            how:</para>

          <procedure>
            <step>
              <para>As <username>root</username> set the sysctl variable
                <varname>vfs.usermount</varname> to
                <literal>1</literal>.</para>

              <screen>&prompt.root; <userinput>sysctl -w vfs.usermount=1</userinput></screen>
            </step>

            <step>
              <para>As <username>root</username> assign the appropriate
                permissions to the block device associated with the
                removable media.</para>

              <para>For example, to allow users to mount the first floppy
                drive, use:</para>

              <screen>&prompt.root; <userinput>chmod 666 /dev/fd0</userinput></screen>

              <para>To allow users in the group
                <groupname>operator</groupname> to mount the CDROM drive,
                use:</para>

              <screen>&prompt.root; <userinput>chgrp operator /dev/acd0c</userinput>
&prompt.root; <userinput>chmod 640 /dev/acd0c</userinput></screen>
            </step>

	    <step>
	      <para>If you are running &os; 5.X or later, you will need to alter 
		<filename>/etc/devfs.conf</filename> to make these changes
		permanent across reboots.</para>

	      <para>As <username>root</username>, add the necessary lines to
		<filename>/etc/devfs.conf</filename>.  For example, to allow
		  users to mount the first floppy drive add:</para>

	      <programlisting># Allow all users to mount the floppy disk.
own       /dev/fd0	  root:operator
perm	  /dev/fd0	  0666</programlisting>

	      <para>To allow users in the group <groupname>operator</groupname>
		to mount the CD-ROM drive add:</para>

	      <programlisting># Allow members of the group operator to mount CD-ROMs.
own       /dev/acd0	  root:operator
perm	  /dev/acd0	  0660</programlisting>
	    </step>

            <step>
              <para>Finally, add the line
                <literal><varname>vfs.usermount</varname>=1</literal>
                to the file <filename>/etc/sysctl.conf</filename> so
                that it is reset at system boot time.</para>
            </step>
          </procedure>

          <para>All users can now mount the floppy
            <devicename>/dev/fd0</devicename> onto a directory that they
            own:</para>

          <screen>&prompt.user; <userinput>mkdir ~/my-mount-point</userinput>
&prompt.user; <userinput>mount -t msdos /dev/fd0 ~/my-mount-point</userinput></screen>

          <para>Users in group <groupname>operator</groupname> can now
            mount the CDROM <devicename>/dev/acd0c</devicename> onto a
            directory that they own:</para>

          <screen>&prompt.user; <userinput>mkdir ~/my-mount-point</userinput>
&prompt.user; <userinput>mount -t cd9660 /dev/acd0c ~/my-mount-point</userinput></screen>

          <para>Unmounting the device is simple:</para>

          <screen>&prompt.user; <userinput>umount ~/my-mount-point</userinput></screen>

          <para>Enabling <varname>vfs.usermount</varname>, however,
            has negative security implications.  A better way to
            access &ms-dos; formatted media is to use the
            <filename role="package">emulators/mtools</filename>
            package in the ports collection.</para>

	  <note>
	    <para>The device name used in the previous examples must be
	      changed according to your configuration.</para>
	  </note>
        </answer>
      </qandaentry>

      <qandaentry>
        <question id="du-vs-df">
          <para>The <command>du</command> and <command>df</command>
            commands show different amounts of disk space available.
            What is going on?</para>
        </question>

        <answer>
          <para>You need to understand what <command>du</command> and
            <command>df</command> really do.  <command>du</command>
            goes through the directory tree, measures how large each
            file is, and presents the totals.  <command>df</command>
            just asks the filesystem how much space it has left.  They
            seem to be the same thing, but a file without a directory
            entry will affect <command>df</command> but not
            <command>du</command>.</para>

          <para>When a program is using a file, and you delete the
            file, the file is not really removed from the filesystem
            until the program stops using it.  The file is immediately
            deleted from the directory listing, however.  You can see
            this easily enough with a program such as
            <command>more</command>.  Assume you have a file large
            enough that its presence affects the output of
            <command>du</command> and <command>df</command>.  (Since
            disks can be so large today, this might be a
            <emphasis>very</emphasis> large file!)  If you delete this
            file while using <command>more</command> on it,
            <command>more</command> does not immediately choke and
            complain that it cannot view the file.  The entry is
            simply removed from the directory so no other program or
            user can access it.  <command>du</command> shows that it
            is gone &mdash; it has walked the directory tree and the file
            is not listed.  <command>df</command> shows that it is
            still there, as the filesystem knows that