FreeBSD Bugzilla – Attachment 59440 Details for
Bug 89456
[UPDATE] zh_TW.Big5: update FAQ(Chapter 1 - Chapter 4)
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Help
|
New Account
|
Log In
Remember
[x]
|
Forgot Password
Login:
[x]
[patch]
zh_TW4.diff
zh_TW4.diff (text/plain), 201.89 KB, created by
chinsan
on 2005-11-23 12:00:37 UTC
(
hide
)
Description:
zh_TW4.diff
Filename:
MIME Type:
Creator:
chinsan
Created:
2005-11-23 12:00:37 UTC
Size:
201.89 KB
patch
obsolete
>diff -ruN zh_TW.Big5.orig/books/faq/book.sgml zh_TW.Big5/books/faq/book.sgml >--- zh_TW.Big5.orig/books/faq/book.sgml Tue Nov 22 09:25:02 2005 >+++ zh_TW.Big5/books/faq/book.sgml Wed Nov 23 19:50:48 2005 >@@ -14,12 +14,15 @@ > <!ENTITY % mailing-lists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN"> > %mailing-lists; > >+<!ENTITY % books.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Books Entity Set//EN"> >+%books.ent; >+ > <!ENTITY bibliography SYSTEM "../../../share/sgml/bibliography.sgml"> > ]> > > <book> > <bookinfo> >- <title>FreeBSD 2.X¡A3.X ¤Î 4.X ±`¨£°Ýµª¶°</title> >+ <title>FreeBSD 4.X¡A5.X ¤Î 6.X ±`¨£°Ýµª¶°</title> > > <corpauthor>FreeBSD ¤å¥ópµe</corpauthor> > >@@ -34,23 +37,50 @@ > <year>2000</year> > <year>2001</year> > <year>2002</year> >+ <year>2003</year> >+ <year>2004</year> >+ <year>2005</year> > <holder>FreeBSD ¤å¥ópµe</holder> > </copyright> > > &bookinfo.legalnotice; > >+ <legalnotice id="trademarks" role="trademarks"> >+ &tm-attrib.freebsd; >+ &tm-attrib.3com; >+ &tm-attrib.adobe; >+ &tm-attrib.creative; >+ &tm-attrib.cvsup; >+ &tm-attrib.ibm; >+ &tm-attrib.ieee; >+ &tm-attrib.intel; >+ &tm-attrib.iomega; >+ &tm-attrib.linux; >+ &tm-attrib.microsoft; >+ &tm-attrib.mips; >+ &tm-attrib.netscape; >+ &tm-attrib.opengroup; >+ &tm-attrib.oracle; >+ &tm-attrib.sgi; >+ &tm-attrib.sparc; >+ &tm-attrib.sun; >+ &tm-attrib.usrobotics; >+ &tm-attrib.xfree86; >+ &tm-attrib.general; >+ </legalnotice> >+ > <abstract> >- <para>³o¥÷¤å¥ó¬O FreeBSD 2.X¡A3.X ¤Î 4.X ªº±`¨£°Ýµª¶°¡C >- °£«D¦³¯S§O¥[µù¡A§_«h³o¨Ç¶µ¥Ø¥Ø³£¾A¥Î©ó FreeBSD 2.0.5 ¤Î¥H«áªºª©¥»¡C >- ¦pªG±ø¥Ø¤º®e¤¤¦³ <XXX> «h¬O©|¥¼§¹¦¨ªº³¡¥÷¡C ¦pªG±z¹ï¨ó§U¥»pµe >+ <para>³o¥÷¤å¥ó¬O FreeBSD 4.X¡A5.X ¤Î 6.X ªº±`¨£°Ýµª¶°¡C >+ °£«D¦³¯S§O¥[µù¡A§_«h³o¨Ç¶µ¥Ø¥Ø³£¾A¥Î©ó FreeBSD 4.0 ¤Î¥H«áªºª©¥»¡C >+ (¦pªG±ø¥Ø¤º®e¤¤¦³ <XXX> «h¬O©|¥¼§¹¦¨¤¤Ä¶ªº³¡¥÷¡C) ¦pªG±z¹ï¨ó§U¥»pµe > ªº¶i¦æ¦³¿³½ìªº¸Ü¡A½Ð±H¤@«Ê¹q¤l¶l¥ó¨ìFreeBSD ¤å¥ópµeªº mailing list >- &a.doc;¡C±z¥i¥H±q <ulink URL="../../../../index.html"> >+ &a.doc;¡C±z¥i¥H±q <ulink URL="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/index.html"> > FreeBSD World Wide Web</ulink> ®³¨ì³o¥÷¤å¥óªº³Ì·sª©¥»¡C >- ±z¤]¥i¥H§Q¥Î HTTP ¨Ó¤U¸ü¤@¥÷Ãe¤jªº <ulink URL="book.html">HTML</ulink> >+ ¤]¥i¥H§Q¥Î HTTP ¨Ó¤U¸ü¤@¥÷Ãe¤jªº <ulink URL="book.html">HTML</ulink> > ¤å¥ó¡A©Î¬O¸g¥Ñ <ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/"> > FreeBSD FTP ¯¸</ulink> ¤U¸ü¯Â¤å¦r¡Apostscript¡A©Î PDF ª©¥»ªºÀɮסC > ±z¤]¥i¥H¦b³o¸Ì¨Ï¥Î >- <ulink URL="http://www.FreeBSD.org/search/search.html">·j´M¸ê®Æ</ulink> >+ <ulink URL="&url.base;/search/search.html">·j´M¸ê®Æ</ulink> > ªº¥\¯à¡C</para> > </abstract> > </bookinfo> >@@ -68,7 +98,7 @@ > > <title>«e¨¥</title> > >- <para>Åwªï¨Ó¨ì FreeBSD 2.X-4.X FAQ!</para> >+ <para>Åwªï¨Ï¥Î FreeBSD 4.X-6.X FAQ!</para> > > <para>¸ò¨ä¥L Usenet ¤Wªº FAQ ¤@¼Ë¡A³o¥÷¤å¥ó²[»\¤F¦³Ãö FreeBSD ³o®M§@·~ > ¨t²Î³Ì±`³Q°Ý¨ìªº°ÝÃD (·íµM¥]¬A¤F¦^µª¡I)¡CÁöµM»¡§ÚÌ¥»¨Óªº¥Øªº¬O¬°¤F >@@ -76,7 +106,7 @@ > ¬°¬O¤@ºØÈ±o¾\Ūªº¤å¥ó¸ê·½¡C</para> > > <para>§Ṳ́w¸g¾¨¥i¯à¦a¨Ï³o¥÷ FAQ §óÂ×´I¤F¡C¦pªG±z¹ï¦p¦ó¨Ï¨ä§ó¶i¨B¦³¥ô >- ¦ó«ØÄ³¡A½ÐÀH®É±H¹q¤l¶l¥óµ¹ &a.faq;¡C</para> >+ ¦ó«ØÄ³¡A½ÐÀH®É±H¹q¤l¶l¥óµ¹ &a.doc;¡C</para> > > <qandaset> > <qandaentry> >@@ -85,24 +115,22 @@ > </question> > > <answer> >- <para>²³æ¦a¨Ó»¡¡AFreeBSD ¬O¤@®M¥i¥H¦b i386 ©M Alpha/AXP ¤W°õ¦æªº >+ <para>²³æ¦a¨Ó»¡¡AFreeBSD ¬O¤@®M¥i¥H¦b Alpha/AXP, AMD64 ¤Î >+ &intel; EM64T, &i386; IA-64, PC-98, &ultrasparc; ¤W°õ¦æªº > UN*X-like §@·~¨t²Î¡A¥¦¬O®Ú¾Ú U.C. Berkeley ©Ò¶}µo¥X¨Óªº > <quote>4.4BSD-Lite</quote>¡A¨Ã¥[¤W¤F³\¦h <quote>4.4BSD-Lite2</quote> > ªº¼W±j¥\¯à¡C¥¦¦P®É¤]¶¡±µ¨Ï¥Î¤F U.C. Berkeley ©Ò¶}µo¥X¨Ó¨Ã¥Ñ > William Jolitz ²¾´Ó¨ì i386 ªº <quote>Net/2</quote>¡A¤]´N¬O > <quote>386BSD</quote>¡A¤£¹L²{¦b 386BSD ªºµ{¦¡½X¥u³Ñ¤U·¥¤Ö¼ÆÁÙ¯d > ¦s¦b FreeBSD ¤¤¡C±z¥i¥H¦b >- <ulink URL="../../../../index.html">FreeBSD º¶</ulink>§ä¨ì¦³Ãö >+ <ulink URL="&url.base;/index.html">FreeBSD º¶</ulink>§ä¨ì¦³Ãö > ¤°»ò¬O FreeBSD ¥H¤Î¥¦¥i¥HÀ°±z°µ¨Ç¤°»òªº¬ÛÃö¸ê°T¡C</para> > > <para>FreeBSD ¤w³Q¼sªx¦a³Q¥@¬É¦U¦aªº¤½¥q¦æ¸¹¡AISP¡A¬ã¨s¤Hû¡A¹q¸£ >- ±M®a¡A¾Ç¥Í¡A¥H¤Î®a®x¥Î¤á©Ò¨Ï¥Î¡A¥Î¦b¤u§@¡A±Ð¨|¡A¥H¤Î®T¼Ö¤W¡C±z¥i >- ¥H¦b >- <ulink URL="../../../../gallery/index.html">FreeBSD Gallery</ulink> >- ¬Ý¨ì¤@¨Ç¦³Ãö¥L̪º¸ê®Æ¡C</para> >+ ±M®a¡A¾Ç¥Í¡A¥H¤Î®a®x¥Î¤á©Ò¨Ï¥Î¡A¥Î¦b¤u§@¡A±Ð¨|¡A¥H¤Î®T¼Ö¤W¡C</para> > > <para>¦pªG·Q¬ÝÃö©ó FreeBSD §ó²`¤Jªº¸ê®Æ¡A½Ð¬Ý >- <ulink URL="../handbook/index.html">FreeBSD ¨Ï¥Î¤â¥U</ulink>¡C</para> >+ <ulink URL="&url.books.handbook;/index.html">FreeBSD ¨Ï¥Î¤â¥U</ulink>¡C</para> > </answer> > </qandaentry> > >@@ -175,15 +203,14 @@ > ªº¸Ü¡A§A´N¤£¯à»´©ö¦a§â¥¦´«±¼¡A©ÎªÌ«ü±æ¦b FreeBSD ¤W¦³«Ü¬Û¦üªºÀ³¥Î > µ{¦¡¤~¦³¾÷·|¡C¦pªG§A·Qnªº¬O¤@Ó±j°·ªº¿ì¤½«Ç©Î¬Oºô¸ô¦øªA¾¹¡A©Î¬O > ¤@³¡Ã©wªº¤u§@¯¸¡A©Î¬O·Q¦b¤£³Q¤¤Â_ªºÀô¹Ò¤U¤u§@ªº¸Ü¡AFreeBSD µLºÃ >- ¬O±zªº³Ì¨Î¿ï¾Ü¡C¥@¬É¦U¦a¦³«Ü¦h¨Ï¥ÎªÌ¡A¥]¬Aªì¾Ç©Î¸ê²`ªº UNIX ºÞ²z >+ ¬O±zªº³Ì¨Î¿ï¾Ü¡C¥@¬É¦U¦a¦³«Ü¦h¨Ï¥ÎªÌ¡A¥]¬Aªì¾Ç©Î¸ê²`ªº &unix; ºÞ²z > ¤Hû³£¿ï¥Î FreeBSD ·í¥L̰ߤ@ªº®à¤W§@·~¨t²Î¡C</para> > >- <para>¦pªG§A¬O±q¨ä¥Lªº UNIX Àô¹ÒÂà´«¨ì FreeBSD ªº¸Ü¡A°ò¥»¤W¬O¤j¦P¤p >- ²§ªº¡C¦ý¬O¦pªG§A¤§«e¥Îªº¬O¹Ï§Î¬É±ªº§@·~¨t²Î¨Ò¦p»¡¬O Windows ©Î¬O >- ¤ñ¸û¥j¦Ñªº Mac OS ªº¸Ü¡A¥i¯à´Nn¦hªá¤@ÂI®É¶¡¨Ó¾Ç²ß«ç»ò¥Î UNIX ªº >+ <para>¦pªG§A¬O±q¨ä¥Lªº &unix; Àô¹ÒÂà´«¨ì FreeBSD ªº¸Ü¡A°ò¥»¤W¬O¤j¦P¤p >+ ²§ªº¡C¦ý¬O¦pªG§A¤§«e¥Îªº¬O¹Ï§Î¬É±ªº§@·~¨t²Î¡A¨Ò¦p»¡¬O &windows; ©Î¬O >+ ¤ñ¸û¥j¦Ñªº &macos; ªº¸Ü¡A¥i¯à´Nn¦hªá¤@ÂI®É¶¡¨Ó¾Ç²ß«ç»ò¥Î &unix; ªº > ¤èªk¨Ó°µ¨Æ¡C§A¥i¥H±q³o¥÷ FAQ ©M <ulink >- url="../handbook/index.html">FreeBSD ¨Ï¥Î¤â¥U</ulink> ¨Ó¤J >- ªù¡C</para> >+ url="&url.books.handbook;/index.html">FreeBSD ¨Ï¥Î¤â¥U</ulink> ¨Ó¤Jªù¡C</para> > </answer> > </qandaentry> > >@@ -218,16 +245,49 @@ > </qandaentry> > > <qandaentry> >+ <question id="differences-to-other-bsds"> >+ <para>FreeBSD ¤Î NetBSD, OpenBSD ¥H¤Î¨ä¥L >+ open source BSD §@·~¨t²Î¤§¶¡¦³¦ó¤£¦P¤§³B©O¡H</para> >+ </question> >+ >+ <answer> >+ <para>James Howard ¦b <ulink url="http://www.daemonnews.org/">DaemonNews</ulink> >+ ¤W¼g¤F <ulink url="http://ezine.daemonnews.org/200104/bsd_family.html"> >+ The BSD Family Tree</ulink> ªº¤å¥ó¡A¸Ì±»¡©ú¤F³o¨Ç¾ú¥v²W·½¤Î³o¨Ç *BSD >+ ®a±Úpµe¤§¶¡ªº®t²§¡C</para> >+ </answer> >+ </qandaentry> >+ >+ <qandaentry> > <question id="latest-version"> > <para>³Ì·sª©ªº FreeBSD ¬O¨º¤@ª©¡H</para> > </question> > >- <answer> >- <para><ulink >- URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE">&rel.current;</ulink> >- ¬O¥Ø«e³Ì·sªº <emphasis>RELEASE</emphasis> ª©¡F¥¦©ó >- &rel.current.date; µo¦æ¡C¥¦¦P®É¤]¬O¥Ø«e³Ì·sªº >- <emphasis>STABLE</emphasis> ª©¡C</para> >+<!-- >+ This answer is a hack to deal with the fact that for now there are >+ multiple "latest" versions of FreeBSD. >+ ³oÓ¦³ÂIÃø¥H¦^µª¡A¨Æ¹ê¤W FreeBSD ¦³³\¦hºØÃþªº¡y³Ì·sª©¡z¡C >+--> >+ >+ <answer> >+ <para>´N FreeBSD ¥Ø«eªºµo®i¦Ó¨¥¡A¦³¥|Ó¥Dnµo®i¤À¤ä(¨ä¤¤¤TÓ¤w¦³ RELEASE)¡G >+ ¥Ñ <emphasis>4-STABLE</emphasis> ©Òµo¦æ(release)ªº 4.X ¨t¦C¡B >+ ¥Ñ <emphasis>5-STABLE</emphasis> ©Òµo¦æ(release)ªº 5.X ¨t¦C¡B >+ ¥Ñ <emphasis>6-STABLE</emphasis> ©Òµo¦æ(release)ªº 6.X ¨t¦C¡A >+ ¥H¤Î <emphasis>7-CURRENT</emphasis> ¤À¤ä¡C</para> >+ >+ <para>¦b 5.3 release ¤§«e¡A4.X ¨t¦C¤´³Qµø¬°¬O <emphasis>-STABLE</emphasis> ¤§¤@¡C >+ ¦Û±q 5.3 ¶}©l¡A5.X ¶}©l³W¹º·sªº <emphasis>-STABLE</emphasis> µo®i«ÂI¡A >+ ¦Ó 4.X ±N¥uµÛ«¦b«¤j°ÝÃD¤W(¤ñ¦p¡Gº|¬}׸ɡB¦w¥þºûÅ@)¥H¤Î "extended support" >+ ¡A¤£¦A·|¦³·sªº¬ð¯}©Êµo®i¡C</para> >+ >+<!-- note: the entity definitions are out of date --> >+ <para>©ó &rel.current.date; ©Òµo¦æªº<ulink >+ url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE">&rel.current;</ulink> >+ ª©¬O¥Ø«e³Ì·sªº <emphasis>6-STABLE</emphasis> ª©¡F >+ ¦Ó©ó &rel2.current.date; ©Òµo¦æªº<ulink >+ url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel2.current;-RELEASE/">&rel2.current;</ulink> >+ ª©«h¬O¥Ø«e³Ì·sªº <emphasis> &rel.current.date;</emphasis> ª©¡C</para> > > <para>²³æªº»¡¡A<emphasis>-STABLE</emphasis> ªº¥Dn¶D¨D¹ï¶H¬O¹ï©ó > éw©Ê¤Î§CÅܲ§©Êªº»Ý¨D»·³Ó¹L¹ï³Ì·s <emphasis>-CURRENT</emphasis> >@@ -237,11 +297,14 @@ > ®e©ö§ó°Ê³o¤@ÂI¡A¤~À³¸Ó¥Î <emphasis>-CURRENT</emphasis>¡C</para> > > <para>Release ª©<link linkend="release-freq">¨C´XÓ¤ë</link>¤~·|µo >- ¦æ¤@¦¸¡CÁöµM¦p¦¹¡A¦³«Ü¦h¤H©M FreeBSD ìµ{½X¦P¨B§ó·s¡]¸Ô¨£ >+ ¦æ¤@¦¸¡CÁöµM¦p¦¹¡A¦³«Ü¦h¤H©M FreeBSD ì©l½X¦P¨B§ó·s¡]¸Ô¨£ > <link linkend="current">FreeBSD-CURRENT</link> ©M <link > linkend="stable">FreeBSD-STABLE</link> ªº¬ÛÃö°ÝÃD)¡A¦ý¦]¬°ì©l½X > ¬O¤@ª½¤£Â_¦a¦bÅܰʪº¡A©Ò¥H¦pªGn³o»ò°µªº¸Ü±onªá¤W§ó¦hªººë > ¤O¡C</para> >+ >+ <para>¨ä¥L§ó¦h¬ÛÃö FreeBSD µo¦æ±¡³ø¡A¥i¥Ñ FreeBSD ºô¯¸¤Wªº <ulink >+ url="http://www.FreeBSD.org/releng/index.html"> Release Engineering</ulink> ±oª¾</para> > </answer> > </qandaentry> > >@@ -252,12 +315,12 @@ > > <answer> > <para><ulink >- URL="../handbook/cutting-edge.html#CURRENT">FreeBSD-CURRENT</ulink> >+ url="&url.books.handbook;/cutting-edge.html#CURRENT">FreeBSD-CURRENT</ulink> > «üªº¬O¥¿¦bµo®i¤¤ªº§@·~¨t²Îª©¥»¡A¥¦²×±N¦b¾A·íªº®É¾÷¦¨¬° >- 5.0-RELEASE¡C¥¦¹ê¦b¬O¥u¾A¦Xµ¹¨t²Îµo®iªÌ¥H¤Î¦³¼Ý¤Oªº·~¾l·R¦nªÌ¨Ï¥Î >+ &os.stable; ¤À¤ä¡C¥¦¹ê¦b¬O¥u¾A¦Xµ¹¨t²Îµo®iªÌ¥H¤Î¦³¼Ý¤Oªº·~¾l·R¦nªÌ¨Ï¥Î > ¡C¦pªG·Qn±o¨ì¦³Ãö¦p¦ó¨Ï¥Î -CURRENT ªº²`¤J¸ê°T¡A½Ð°Ñ¦Ò <ulink >- URL="../handbook/index.html">¨Ï¥Î¤â¥U</ulink> ªº <ulink >- URL="../handbook/cutting-edge.html#CURRENT">¬ÛÃö³¡¥÷</ulink>¡C >+ url="&url.books.handbook;/index.html">¨Ï¥Î¤â¥U</ulink> ªº <ulink >+ url="&url.books.handbook;/cutting-edge.html#CURRENT">¬ÛÃö³¡¥÷</ulink>¡C > </para> > > <para>¦pªG±z¹ï§@·~¨t²Î¥»¨¨Ã¤£¬O«Ü¼ô±x¡A©Î¬O±z¨S¿ìªk¤À¿ë±z¹J¨ìªº°Ý >@@ -270,7 +333,7 @@ > »~</quote>¤§Ãþªº°ÝÃDªº¸Ü¡A¤]³\·|³Q¨ä¥L¤H»´µø¡C</para> > > <para>§Ų́C¤Ñ³£·|®Ú¾Ú¥Ø«e -CURRENT ©M -STABLE ªºª¬ªp¹ï³o¨âÓ¤À¤ä¦U >- µo¦æ¤@Ó<ulink URL="../../../../releases/snapshots.html">snapshot >+ µo¦æ¤@Ó<ulink URL="&url.base;/releases/snapshots.html">snapshot > </ulink> ª©¡C¦³ªº®ÉԬƦÜÁÙ·|µo¦æ¥i¨Ñ¨ú±oªºª©¥»¡Cµoªí³o¨Ç snapshot > ªº¥Øªº¦b©ó¡G</para> > >@@ -295,17 +358,14 @@ > </listitem> > </itemizedlist> > >- <para>§Ṳ́£¹ï -CURRENT snapshot °µ¥ô¦X§Î¦¡ªº<quote>«~½è«O >+ <para>§Ṳ́£¹ï -CURRENT snapshot °µ¥ô¦ó§Î¦¡ªº<quote>«~½è«O > ÃÒ</quote>¡C¦pªG§A·Qnªº¬O¤@Óéw¥B¸g¹L¥R¤À´ú¸Õ¹Lªº¨t²Îªº¸Ü¡A > ³Ì¦n¿ï¾Ü¨Ï¥Î§¹¾ã release ªºª©¥»¡A©Î¬O¨Ï¥Î -STABLE snapshots¡C</para> > > <para>±z¥i¥Hª½±µ±q <ulink >- URL="ftp://current.FreeBSD.org/pub/FreeBSD/"> >- ftp://current.FreeBSD.org/pub/FreeBSD/</ulink> ¨ú±o 5.0-CURRENT ªº >- snapshot release¡A¦Ó±q <ulink >- URL="ftp://releng4.FreeBSD.org/pub/FreeBSD">releng4.FreeBSD.org >- </ulink> ¨ú±o 4-STABLE ªº snapshots¡C¦b¥»¤å¼g§@ªº®ÉÔ >- (2000 ¦~ 5 ¤ë) ´N¤w¸g¤£¦A´£¨Ñ 3-STABLE ªº snapshots ¤F¡C</para> >+ URL="ftp://current.FreeBSD.org/pub/FreeBSD/snapshots/"> >+ ftp://current.FreeBSD.org/pub/FreeBSD/snapshots/</ulink> ¨ú±o -CURRENT ªº >+ snapshot release</para> > > <para>¹ï¨CÓ¦³¦b¬¡°Êªº¤À¤ä¦Ó¨¥¡A¥§¡¨C¤Ñ³£·|²£¥Í¤@¦¸ snapshots¡C > </para> >@@ -319,12 +379,17 @@ > > <answer> > <para>¦^·¹¨ì FreeBSD 2.0.5 èµoªíªº®ÉÔ¡A§Ų́M©w§â FreeBSD ªºµo®i >- ¤À¦¨¨â¤ä¡C¤@¤ä¥s°µ <ulink URL="../handbook/stable.html">-STABLE >- </ulink>¡A§ÚÌ¥u¹ï¥¦°µ¿ù»~×¥¿¤Î¤p´T«×ªº×§ï (³o¬Oµ¹ ISP ©M°Ó·~ >- ¤½¥qµ¥¹ï¹êÅ礤¥\¯à¤£·P¿³½ìªº³æ¦ì©Ò¨Ï¥Îªº)¡C¥t¥~¤@¤ä¥s°µ <ulink >- URL="../handbook/cutting-edge.html#CURRENT">-CURRENT</ulink>¡A±q >- 2.0 ª©µo¦æ¥H«á´N¤£¶¡Â_¦a´ÂµÛ 5.0-RELEASE (¥H¤Î¥H«áªºª©¥») «e¶i >- µÛ¡C¤U±´N¬Oª©¥»ºt¶iªº¥Ü·N¹Ï¡G</para> >+ ¤À¦¨¨â¤ä¡C¤@¤ä¥s°µ <ulink url="&url.books.handbook;/current-stable.html#STABLE">-STABLE</ulink> >+ ¡A§ÚÌ¥u¹ï¥¦°µ¿ù»~×¥¿¤Î¤p´T«×ªº×§ï (³o¬Oµ¹ ISP ©M°Ó·~¤½¥qµ¥¡A¹ï¹êÅ礤¥\¯à¤£·P¿³½ìªº³æ¦ì©Ò¨Ï¥Îªº)¡C >+ ¥t¥~¤@¤ä¥s°µ <ulink url="&url.books.handbook;/current-stable.html#CURRENT">-CURRENT</ulink>¡A±q >+ 2.0 ª©µo¦æ¥H«á¡A´N¤£Â_¦a´ÂµÛ 6.0-RELEASE (§t«áÄòªºª©¥»)«e¶iµÛ¡C</para> >+ >+ <para>6-STABLE ¤À¤ä¬O±q 6.0-RELEASE ¶}©l(5-STABLE ¤À¤äºâ¬O 5.3-RELEASE ¤§«á¤~¶}©lªº)¡A >+ µM«á쥻ªº &os.current; ´N·|¦¨¬° 7-CURRENT¡C >+ </para> >+ >+ >+ <para>¤U±´N¬Oª©¥»ºt¶iªº¥Ü·N¹Ï¡G</para> > > <programlisting> 2.0 > | >@@ -349,43 +414,56 @@ > | (May 1999) (Sep 1999) (Dec 1999) (June 2000) (July 2000) > | > | [4.0-STABLE] >- *BRANCH* 4.0 (Mar 2000) -> 4.1 -> 4.1.1 -> 4.2 -> 4.3 -> 4.4 -> ... future 4.x releases ... >+ *BRANCH* 4.0 (Mar 2000) -> 4.1 -> 4.1.1 -> 4.2 -> 4.3 -> 4.4 -> ... -> 4.11 >+ | >+ | (July 2000) (Sep 2000) (Nov 2000) (Jan 2005) >+ | >+ | [5.0-STABLE] >+ *BRANCH* 5.0 (2001) -> 5.1 -> 5.2 -> 5.3 -> 5.4 -> ... future 5.x releases... >+ | >+ | ( 2001) (Nov 2004) (May 2005) >+ | >+ | [6.0-STABLE] >+ *BRANCH* 6.0 (Nov 2005) ... future 6.x releases... > | >- | (July 2000) (Sep 2000) (Nov 2000) > \|/ > + >- [5.0-CURRENT continues]</programlisting> >+ [7.0-CURRENT continues]</programlisting> > > <para>2.2-STABLE ³oÓ¤À¤äÀHµÛ 2.2.8 ªºµoªí¦Ó¥\¦¨¨°h¡C3-STABLE ³oÓ > ¤À¤ä«h¬Oµ²§ô¦b 3.5.1 µoªí¤§«á¡A¥¦¤]¬O 3.X ªº³Ì«á¤@¦¸µoªí¡C¤§«á°£¤F >- ¦w¥þ¬ÛÃöªº×¥¿¤§¥~¡A³o¨âÓ¤À¤ä´N´X¥G¨S¦³¦A§ó°Ê¹L¡C</para> >+ ¦w¥þ¬ÛÃöªº×¥¿¤§¥~¡A³o¨âÓ¤À¤ä´N´X¥G¨S¦³¦A§ó°Ê¹L¡C4-STABLE ¤À¤äªº¤ä´© >+ ·|«ùÄò¨ì 2007/01/31¡A¦ý¥DnµJÂI¦b©ó¦w¥þ¤è±ªºº|¬}¡B¯äÂΤΨä¥LÄY«°ÝÃDªº×¸É¡C</para> > >- <para>4-STABLE ¬O¥Ø«e¥¿¦bµo®i¤¤ªº -STABLE ¤À¤ä¡C4-STABLE ªº³Ì·sªº¤@ >- ¦¸µoªí¬O &rel.current.date; µo¦æªº &rel.current;-RELEASE¡C</para> >+ <para>5-STABLE ¬O¥Ø«e¥¿¦bµo®i¤¤ªº -STABLE ¤À¤ä¡C5-STABLE ªº³Ì·sªº¤@ >+ ¦¸µoªí¬O¦b &rel2.current.date; µo¦æªº &rel2.current;-RELEASE¡C</para> > >- <para>5-CURRENT ªº³oÓ¤À¤ä¥Ø«e¥¿¥H½wºCªº³t«× 5.0-RELEASE ¥H¤Î¤§«áªº >- ª©¥»ÁÚ¶i¤¤¡C¦pªG·Qnª¾¹D§ó¦hÃö©ó³oÓ¤À¤äªº¸ê°Tªº¸Ü¡A½Ð°Ñ¦Ò <link >- linkend="current">¤°»ò¬O FreeBSD-CURRENT¡H</link>¡C</para> >+ <para>6-STABLE ¬O¥Ø«e¥¿¦bµo®i¤¤ªº -STABLE ¤À¤ä¡C6-STABLE ªº³Ì·sªº¤@ >+ ¦¸µoªí¬O¦b &rel.current.date; µo¦æªº &rel.current;-RELEASE¡C</para> >+ >+ <para>7-CURRENT ³oÓ¤À¤ä¬O &os; ªº -CURRENT ¤À¤ä¡A¤´µM¤£Â_¦a¦bµo®i·í¤¤¡C >+ ¦pªG·Qnª¾¹D§ó¦hÃö©ó³oÓ¤À¤äªº¸ê°Tªº¸Ü¡A½Ð°Ñ¦Ò <link >+ linkend="current">¤°»ò¬O &os;-CURRENT¡H</link>¡C</para> > </answer> > </qandaentry> > > <qandaentry> > <question id="release-freq"> >- <para>·sªº FreeBSD ±N©ó¤°»ò®ÉÔ±À¥X¡H</para> >+ <para>¨C¦¸·sªº FreeBSD ±N©ó¤°»ò®ÉÔ±À¥X¡H</para> > </question> > > <answer> >- <para>¤@¯ë¦Ó¨¥¡A·í FreeBSD core team »{¬°¤w¸g²Ö¿n¤F¨¬°÷¦hªº·s¥\¯à >- ©M¿ù»~×¥¿¡A¦Ó¥B³o¨Ç§ó°Ê³£¤w¸g§¹¾ã¦a´ú¸Õ¹L¥B¤£·|¼vÅT¨t²Îéw«×ªº >- ®ÉÔ¡A¥L̤~·|±À¥X·sª©ªº FreeBSD¡C·sª©¥»ªºµoªí®Éµ{³£·|¨Æ¥ý¤½§i¡A >- ¬ÛÃöªº¶}µo¤Hû´Nª¾¹D¤°»ò®ÉÔ¸Ó§â¤âÃ䪺p¹º§¹¦¨¨Ã¥B´ú¸Õ¹L¡CÁöµMµ¥ >- ³o¨Ç¦nªF¦è¶i¤J -STABLE ªº®É¶¡¥O¤H¦³ÂIªq³à¡A¦ý¬O¤j¦h¼Æªº¨Ï¥ÎªÌ³£ >- »{¬°³oºØÂÔ·VªººA«×¬O FreeBSD ³Ì¦nªºÀuÂI¤§¤@¡C</para> >+ <para>¤@¯ë¦Ó¨¥¡A&a.re; ¥§¡¨C¥|Ó¤ëµo¦æ¤@¦¸ release¡A¨C¦¸·sª©¥»ªºµoªí®Éµ{³£·|¨Æ¥ý¤½§i¡A >+ ¬ÛÃöªº¶}µo¤Hû´N·|ª¾¹D¡A¤°»ò®ÉÔ¸Ó¥ý§â¤âÃ䪺p¹º§¹¦¨¨Ã¥B´ú¸Õ¹L¡A >+ ¦¹¥~¡A³o¨Ç§ó°Ê³£¤w¸g§¹¾ã¦a´ú¸Õ¹L¡A¥B¤£·|¼vÅT¨t²Îéw«×¡C >+ ÁöµM¡Aµ¥³o¨Ç¦nªF¦è¶i¤J -STABLE ªº®É¶¡¥O¤Hµ¥±o¦³¨Ç¤£@·Ð¡A >+ ¦ý¬O¤j¦h¼Æªº¨Ï¥ÎªÌ³£»{¬°³oºØÂÔ·VªººA«×¬O FreeBSD ³Ì¦nªºÀuÂI¤§¤@¡C</para> > >- <para>¥§¡¦Ó¨¥¡A§Ų́C¥|Ó¤ëµo¦æ¤@¦¸ release¡C</para> >+ <para>¦³Ãöµo¦æ±¡³øªº§ó¦h²Ó¸`³¡¤À(¥]¬A release ªº¦æµ{ªí¡B¶i«×)¡A³£¥i¦b FreeBSD ºô¯¸¤Wªº >+ <ulink url="http://www.FreeBSD.org/releng/index.html">µo¦æ±¡³ø</ulink> ¤W±Àò±o¡C</para> > >- <para>¬°¤Fº¡¨¬¨º¨Ç»Ýn (©Î·Qn) ¨ë¿Eªº¨Ï¥ÎªÌ¡A¤W±¤w¸g»¡¹L§Ų́C¤Ñ >- ³£·|µo¦æ snapshots ª©¥i¨Ñ¨Ï¥Î¡C</para> >+ <para>¬°¤Fº¡¨¬¨º¨Ç»Ýn (©Î·Qn) ·sÂA¨ë¿E·Pªº¨Ï¥ÎªÌ¡A >+ ¤W±(-CURRENTªº³¡¤À)¤w¸g´£¨ì§Ų́C¤Ñ³£·|µo¦æ snapshots ª©¥i¨Ñ¨Ï¥Î¡C</para> > </answer> > </qandaentry> > >@@ -397,15 +475,15 @@ > <answer> > <para>¦pªG¬O¤@¨Ç¦³Ãö FreeBSD pµeªºÃöÁä©Ê¨M©w¡A¹³¬O¾ãÓpµeªº¨«¦V > ©Î¬O¨M©w½Ö¥i¥H§ï source tree ¸Ìªºµ{¦¡½X³oÃþªº¨Æ¡A¬O¥Ñ¤@ 9 Ó >- ¤H©Ò²Õ¦¨ªº <ulink >- URL="../../articles/contributors/article.html#STAFF-CORE">core >- team</ulink> ¨Ó¨M©w¡C¦Ó¦³¥t¤@¸s¶W¹L 200 Ó¤Hªº <ulink >- URL="../../articles/contributors/article.html#STAFF-COMMITTERS"> >+ ¤H©Ò²Õ¦¨ªº <ulink >+ url="&url.articles.contributors;/article.html#STAFF-CORE">core >+ team</ulink> ¨Ó¨M©w¡C¦Ó¦³¥t¤@¸s¶W¹L 300 Ó¤Hªº <ulink >+ url="&url.articles.contributors;/article.html#STAFF-COMMITTERS"> > commiters</ulink> ¦³Åv§Q¥i¥Hª½±µ×§ï FreeBSD ªº source tree¡C > </para> > > <para>µL½×¦p¦ó¡A¤j¦h¼Æªº§ïÅܳ£·|¨Æ«e¦b <link linkend="mailing"> >- mailing lists</link> ¥ý°Q½×¹L¡A¦Ó¥B¨CÓ¤H³£¥i¥H°Ñ»P°Q½×¡C</para> >+ mailing lists</link> ¥ý°Q½×¹L¡A¦Ó¥B¤£¤À¨¤¦â¡A¨CÓ¤H³£¥i¥H°Ñ»P°Q½×¡C</para> > </answer> > </qandaentry> > >@@ -416,74 +494,86 @@ > > <answer> > <para>¨CÓ FreeBSD ªº«nª©¥»³£¥i¥H¸g¥Ñ°Î¦W ftp ±q <ulink >- URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/">FreeBSD FTP site</ulink> >- ¨ú±o¡G</para> >+ url="ftp://ftp.FreeBSD.org/pub/FreeBSD/">FreeBSD FTP ¯¸</ulink>¨ú±o¡G</para> > >- <itemizedlist> >- <listitem> >- <para>¦pªGnªº¬O 3.X-STABLE ªº³Ì·sª©¡A¤]´N¬O 3.5.1-RELEASE¡A½Ð¨ì >- <ulink >- URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/3.5.1-RELEASE/">3.5.1-RELEASE</ulink> ³oӥؿý¡C</para> >- </listitem> >+ <itemizedlist> >+ <listitem> >+ <para>¦pªG»Ýn 6-STABLE ªº³Ì·sª©¡A¤]´N¬O &rel.current;-RELEASE¡A½Ð¨ì <ulink >+ url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/">&rel.current;-RELEASE </ulink>³oӥؿý</para> >+ </listitem> > >- <listitem> >- <para>¦pªGnªº¬O 4-STABLE ªº³Ì·sª©¡A¤]´N¬O &rel.current;-RELEASE >- ¡A½Ð¨ì <ulink >- URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/">&rel.current;-RELEASE </ulink>³oӥؿý</para> >- </listitem> >+ <listitem> >+ <para><ulink url="ftp://current.FreeBSD.org/pub/FreeBSD/">7-CURRENT Snapshot</ulink> >+ ³q±`¤]¬O¨C¤Ñ³£·|°µ¤@¥÷¡A³o¬O±q <link linkend="current">-CURRENT</link> ¤À¤ä°µ¥X¨Óªº¡A >+ ¥Dn¬O¬°¤F´£¨Ñµ¹¨º¨Ç¼ö¤ßªº´ú¸ÕªÌ©M¶}µo¤Hû¡C</para> >+ </listitem> > >- <listitem> >- <para><ulink >- URL="ftp://releng4.FreeBSD.org/pub/FreeBSD/">4.X >- snapshots</ulink> ³q±`¨C¤Ñ³£·|°µ¤@¥÷¡C</para> >- </listitem> >+ <listitem> >+ <para>¦pªG»Ýn 5-STABLE ªº³Ì·sª©¡A¤]´N¬O &rel2.current;-RELEASE¡A½Ð¨ì <ulink >+ url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel2.current;-RELEASE/">&rel2.current;-RELEASE </ulink>³oӥؿý</para> >+ </listitem> > >- <listitem> >- <para><ulink >- URL="ftp://current.FreeBSD.org/pub/FreeBSD/"> >- 5.0 Snapshot</ulink> ³q±`¤]¬O¨C¤Ñ³£·|°µ¤@¥÷¡A³o¬O±q <link >- linkend="current">-CURRENT</link> ¤À¤ä°µ¥X¨Óªº¡A¥Dn¬O¬°¤FªA >- °È¨º¨Ç¼ö¤ßªº´ú¸ÕªÌ©M¶}µo¤Hû©Ò´£¨Ñªº¡C</para> >- </listitem> >+ <listitem> >+ <para>¦pªG»Ýn 4-STABLE ªº³Ì·sª©¡A¤]´N¬O 4.11-RELEASE¡A½Ð¨ì <ulink >+ url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/4.11-RELEASE/">4.11-RELEASE </ulink>³oӥؿý</para> >+ </listitem> >+ >+ <listitem> >+ <para><ulink >+ url="ftp://current.FreeBSD.org/pub/FreeBSD/snapshots/">4.X¡B5.X¡B6X snapshots</ulink> >+ ³q±`¨C¤Ñ³£·|°µ¤@¥÷¡C</para> >+ </listitem> > </itemizedlist> > >- <para>FreeBSD ªº CD¡ADVD¡AÁÙ¦³¤@¨Ç¨ä¥LªºªF¦èªº¨ú±oªk¥i¥H¦b <ulink url="../handbook/mirrors.html">¨Ï¥Î¤â¥U</ulink>¤¤§ä¨ì¸Ñµª¡C</para> >+ <para>FreeBSD ªº CD¡BDVD¡AÁÙ¦³¨ä¥L¨ú±o¤è¦¡¥i¥H¦b <ulink url="&url.books.handbook;/mirrors.html">¨Ï¥Î¤â¥U</ulink> ¤¤§ä¨ì¸Ñµª¡C</para> > </answer> > </qandaentry> > > <qandaentry> >+ <question id="howto-mirror"> >+ <para>«ç»ò«Ø¥ß FreeBSD ªº¬M®g(mirror)¯¸¥x¡H</para> >+ </question> >+ >+ <answer> >+ <para>¦³Ãö¦p¦ó«Ø¥ß FreeBSD ¬M®g¯¸(mirror)ªº¸ê®Æ¡A¥i¥H°Ñ¦Ò <ulink >+ url="&url.articles.hubs;/">Mirroring FreeBSD</ulink> ¤å³¹</para> >+ </answer> >+ </qandaentry> >+ >+ <qandaentry> > <question id="access-pr"> >- <para>§Ún¦p¦ó¥h¦s¨ú¿ù»~¦^³ø¸ê®Æ®w©O¡H</para> >+ <para>§Ún¦p¦ó¥h¬d¸ß¡B´£¥æ°ÝÃD¦^³ø(Problem Report)¸ê®Æ®w©O¡H</para> > </question> > > <answer> >- <para>©Ò¦³¨Ï¥ÎªÌªºÅܧón¨D³£¥i¥H¸g¥Ñ§Ú̺ô¶¤¶±ªº PR <ulink >- URL="http://www.FreeBSD.org/send-pr.html">submission</ulink> ¤Î >+ <para>©Ò¦³¨Ï¥ÎªÌªºÅܧón¨D³£¥i¥H¸g¥Ñºô¶¤¶±ªº PR > <ulink URL="http://www.FreeBSD.org/cgi/query-pr-summary.cgi?query"> >- query</ulink> ¨Ó¬d¸ß (©Î¬O¦^³ø) §Ú̪º¿ù»~¦^³ø¸ê®Æ®w¡C¤]¥i¥H§Q¥Î >- &man.send-pr.1; ³oÓ«ü¥O³z¹L¹q¤l¶l¥ó¨Ó¦^³ø¿ù»~©Î¬On¨DÅܧó¡C</para> >+ ¬d¸ß¤¶±</ulink> ¨Ó¹î¬Ý (©Î¬O¦^³ø) §Ú̪º¿ù»~¦^³ø¸ê®Æ®w¡C</para> >+ >+ <para>¤]¥i¥H¨Ï¥Î &man.send-pr.1; ³oÓ«ü¥O³z¹L¹q¤l¶l¥ó¨Ó¦^³ø°ÝÃD¡Bn¨DÅܧó¡C >+ ©ÎªÌ¬O¸g¥Ñ <ulink url="http://www.FreeBSD.org/send-pr.html">ºô¶¤¶±ªº PR</ulink> ¨Ó°e¥X°ÝÃD¦^³ø¡C</para> > >- <para>¦b¦^³ø¿ù»~¤§«e¡A½Ð¥ýŪ¹L <ulink >- URL="../../articles/problem-reports/article.html">¦p¦ó¼¶¼g >- FreeBSD ªº¿ù»~¦^³ø³æ</ulink>¡A³o¬O¤@½g§i¶D§A«ç¼Ë¤~¯à¼g¥X¤@½g¦³¥Îªº >- ¿ù»~¦^³ø³æ¡C</para> >+ <para>µM¦Ó¡A¦b±z¦^³ø°ÝÃD¤§«e¡A½Ð¥ý¾\Ū <ulink >+ URL="&url.articles.problem-reports;/article.html">¦p¦ó¼¶¼g >+ FreeBSD ªº°ÝÃD¦^³ø³æ</ulink>¡A³o¬O¤@½g§i¶D§A«ç¼Ë¤~¯à¼g¥X¤@½g¯u¥¿¦³¥Îªº >+ °ÝÃD¦^³ø³æ¡C</para> > </answer> > </qandaentry> > > <qandaentry> > <question id="become-web-mirror"> >- <para>n«ç¼Ë¤~¯à¦¨¬° FreeBSD ªººô¶¬M®g¯¸¥x¡H</para> >+ <para>n«ç¼Ë¤~¯à¦¨¬° FreeBSD ªººô¶¬M®g(mirror)¯¸¥x¡H</para> > </question> > > <answer> >- <para>¦³«Ü¦h¤èªk¥i¥H¬M®g§Ú̪ººô¶¡C</para> >+ <para>¦³«Ü¦h¤èªk¥i¥H¬M®g(mirror)§Ú̪ººô¶¡C</para> > > <itemizedlist> > <listitem> > <para>±z¥i¥H§Q¥Î <filename role="package">net/cvsup</filename> > ±q cvsup.FreeBSD.org ¨ú±o®æ¦¡¤Æ¹LªºÀɮסC >- <filename>/usr/share/examples/cvsup/www-supfile</filename>´N >- ¬O¤@ӱЧA«ç¼Ë°µºô¶¬M®gªº CVSup ³]©w½d¨Ò¡C >+ <filename>/usr/share/examples/cvsup/www-supfile</filename> >+ ³oÀÉ´N¬O¤@ӱЧA«ç¼Ë°µºô¶¬M®gªº CVSup ³]©w½d¨Ò¡C > </para> > </listitem> > >@@ -491,7 +581,7 @@ > <para>±z¥i¥H§Q¥Î±z³ßÅwªº ftp mirror ¤u¨ã±q FreeBSD ªº FTP ¯¸»O > ¤¤¨ú±oºô¶ªºì©l½X¡C¦ý¬Onª`·Nªº¬O¦b§A¥´ºâ´£¨Ñ¤½¶}ªA°È¤§«e¡A > °O±on¥ý§Q¥Î³o¨Çì©l½X§âºô¶««Ø°_¨Ó¡C½Ð±q <ulink >- URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/www">ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/www</ulink> ¶}©l§ì¨ú¡C</para> >+ url="ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/www"></ulink> ¶}©l§ì¨ú¡C</para> > </listitem> > </itemizedlist> > </answer> >@@ -512,60 +602,66 @@ > </chapter> > > <chapter id="support"> >- <title>Documentation and Support</title> >+ <chapterinfo> >+ <author> >+ <firstname>Chin-San</firstname> >+ <surname>Huang</surname> >+ <affiliation> >+ <address><email>chinsan.tw@gmail.com</email></address> >+ </affiliation> >+ </author> >+ </chapterinfo> >+ >+ <title>¤å¥ó»P¤ä´©</title> > > <qandaset> > <qandaentry> > <question id="books"> >- <para>What good books are there about FreeBSD?</para> >+ <para>Ãö©ó FreeBSD ¦³þ¨Ç¦n®Ñ¥i¥H±ÀÂ˾\Ūªº¶Ü¡H</para> > </question> > > <answer> >- <para>The project produces a wide range of documentation, available >- from this link: >- <ulink url="http://www.freebsd.org/docs.html">http://www.FreeBSD.org/docs.html</ulink>. >+ <para>FreeBSD ¤å¥ópµe¤w³°Äòµoªí¤F¬Û·í¼sªx½d³òªº¤å¥ó¡A¥i¦b <ulink >+ url="http://www.FreeBSD.org/docs.html"></ulink> ¨ú±o¡C¥t¥~¡A >+ FreeBSD ¥»¨ªº manual(¤@¯ë³qºÙªºman)¡Bdoc¤]¦p¦P®M¥ó³nÅé¤@¼Ë¡A¥i¥H»´ÃP¦a¸Ë¦b±z¨t²Î¤W¡C >+ </para> > >- In addition, the Bibliography at the end of this FAQ, and the >- one in the Handbook reference other recommended books.</para> >+ <para>¦¹¥~¡A¤]«ØÄ³°Ñ¾\¥»¥÷ FAQ ³Ì«á©Ò¦Cªº°Ñ¦Ò®Ñ¥Øªí(Bibliography)»P¡m FreeBSD ¨Ï¥Î¤â¥U¡n¡C >+ </para> > </answer> > </qandaentry> > > <qandaentry> > <question id="doc-formats"> >- <para>Is the documentation available in other formats, such as plain >- text (ASCII), or Postscript?</para> >+ <para>³o¨Ç¤å¥ó¦³¨ä¥L®æ¦¡ªº¶Ü¡H¹³¬O¡G¯Â¤å¦r(ASCII)©Î &postscript; ¤§Ãþªº®æ¦¡¡H</para> > </question> > > <answer> >- <para>Yes. The documentation is available in a number of >- different formats and compression schemes on the FreeBSD >- FTP site, in the <ulink >- URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">/pub/FreeBSD/doc/</ulink> >- directory.</para> >+ <para>¦³ªº¡C³o¨Ç¤å¥ó³£¤À§O¥H¤£¦P®æ¦¡Àx¦s¥H¤ÎÀ£ÁY³B²z¡A©ñ¦b >+ FTP ¤W±¡A¥i¥H±q¦U FreeBSD FTP ¯¸ªº <ulink >+ url="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">/pub/FreeBSD/doc/</ulink> >+ ¥Ø¿ý¤º§ä¨ì§Anªº¡C</para> > >- <para>The documentation is categorized in a number of different >- ways. These include:</para> >+ <para>¤å¥óªº¤ÀÃþ¤è±¥Dn¬O¤@¨Ç¤£¦P©Ê½è©Ò²Õ¦¨¡G</para> > > <itemizedlist> > <listitem> >- <para>The document's name, such as <literal>faq</literal>, or >- <literal>handbook</literal>.</para> >+ <para>¤å¥ó¦WºÙ¡A¤ñ¦p¡G<literal>faq(±`¨£°Ýµª¶°)</literal>©Î¬O >+ <literal>handbook(FreeBSD ¨Ï¥Î¤â¥U)</literal>µ¥µ¥¡C</para> > </listitem> > > <listitem> >- <para>The document's language and encoding. These are based on >- the locale names you will find under >- <filename>/usr/share/locale</filename> on your FreeBSD >- system. The current languages and encodings that we have for >- documentation are as follows:</para> >+ <para>¦U°ê½Ķªºªº¤å¥ó¡G³o¥Dn¬O¥Ñ locale ¦WºÙ¨Ó¨M©wªº >+ (¤£²M·¡ªº¸Ü¡A¥i°Ñ¦Ò±zªº FreeBSD §@·~¨t²Î¤Wªº <filename>/usr/share/locale</filename>) >+ ¥Ø«e¤å¥óÁ`¦@¦³¤U¦C´XºØ»y¨¥(¤Î½s½X)¦³Â½Ä¶¡G</para> > >- <informaltable frame="none"> >+ <informaltable frame="none" pgwide="1"> > <tgroup cols="2"> > <thead> > <row> >- <entry>Name</entry> >+ <entry>Locale ¦WºÙ</entry> > >- <entry>Meaning</entry> >+ <entry>»¡©ú(©Ò¥Nªíªº»y¨t¡B½s½X)</entry> > </row> > </thead> > >@@ -573,72 +669,72 @@ > <row> > <entry><literal>en_US.ISO8859-1</literal></entry> > >- <entry>US English</entry> >+ <entry>¬ü¦¡^¤å(US English)</entry> > </row> > > <row> > <entry><literal>de_DE.ISO8859-1</literal></entry> > >- <entry>German</entry> >+ <entry>¼w¤å(German)</entry> > </row> > > <row> > <entry><literal>es_ES.ISO8859-1</literal></entry> > >- <entry>Spanish</entry> >+ <entry>¦è¯Z¤ú¤å(Spanish)</entry> > </row> > > <row> > <entry><literal>fr_FR.ISO8859-1</literal></entry> > >- <entry>French</entry> >+ <entry>ªk¤å(French)</entry> > </row> > >+ <row> >+ <entry><literal>it_IT.ISO8859-15</literal></entry> >+ >+ <entry>¸q¤j§Q¤å(Italian)</entry> >+ </row> >+ > <row> > <entry><literal>ja_JP.eucJP</literal></entry> > >- <entry>Japanese (EUC encoding)</entry> >+ <entry>¤é¤å(Japanese¡A½s½X¤è¦¡¡GEUC)</entry> > </row> > > <row> > <entry><literal>ru_RU.KOI8-R</literal></entry> > >- <entry>Russian (KOI8-R encoding)</entry> >+ <entry>«X¤å(Russian¡A½s½X¤è¦¡¡GKOI8-R)</entry> > </row> > > <row> > <entry><literal>zh_TW.Big5</literal></entry> > >- <entry>Chinese (Big5 encoding)</entry> >+ <entry>¥¿Å餤¤å(Chinese¡A½s½X¤è¦¡¡GBig5)</entry> > </row> > </tbody> > </tgroup> > </informaltable> > > <note> >- <para>Some documents may not be available in all >- languages.</para> >+ <para>¤W¦Cªº¦U°ê½Ķ»y¨t¤å¥ó¤¤¡A¨Ã«D©Ò¦³¤å¥ó³£¦³Â½Ä¶¡C</para> > </note> > </listitem> > > <listitem> >- <para>The document's format. We produce the documentation in a >- number of different output formats. Each format has its own >- advantages and disadvantages. Some formats are better suited >- for online reading, while others are meant to be aesthetically >- pleasing when printed on paper. Having the documentation >- available in any of these formats ensures that our readers >- will be able to read the parts they are interested in, either >- on their monitor, or on paper after printing the documents. >- The currently available formats are:</para> >+ <para>¤å¥óªº®æ¦¡¡G¨C¥÷¤å¥ó³£¥H¦UºØ¤£¦P®æ¦¡Àx¦s¡A¨CºØ®æ¦¡³£¦U¦³¦nÃa¡A >+ ¦³¨Ç®æ¦¡¾A¦X½u¤W¾\Ū¡A¦Ó¦³¨Ç«h¾A¦X¦C¦L¥X¬üÆ[ªº¤å¥ó¡C >+ §Ú̳£´£¨Ñ³o¨Ç¤£¦P®æ¦¡ªº¤å¥ó¡A¨Ó½T«OµL½×¬O¿Ã¹õ¤W¡B¦C¦L¯È¥»¡A¨CÓ¤H³£¥i¥H¥¿±`¦a¾\Ū¤º®e¡A >+ ¥Ø«e¥i¨Ñ¨Ï¥Îªº®æ¦¡¦p¤U:</para> > >- <informaltable frame="none"> >+ <informaltable frame="none" pgwide="1"> > <tgroup cols="2"> > <thead> > <row> >- <entry>Format</entry> >+ <entry>®æ¦¡</entry> > >- <entry>Meaning</entry> >+ <entry>»¡©ú</entry> > </row> > </thead> > >@@ -646,47 +742,45 @@ > <row> > <entry><literal>html-split</literal></entry> > >- <entry>A collection of small, linked, HTML >- files.</entry> >+ <entry>³¹¸`¼Ò¦¡</entry> > </row> > > <row> > <entry><literal>html</literal></entry> > >- <entry>One large HTML file containing the entire >- document</entry> >+ <entry>§¹¾ã¼Ò¦¡</entry> > </row> > > <row> > <entry><literal>pdb</literal></entry> > >- <entry>Palm Pilot database format, for use with the >- <ulink URL="http://www.iSilo.com/">iSilo</ulink> >- reader.</entry> >+ <entry>Palm Pilot ¸ê®Æ®æ¦¡¡A¨Ï¥Î >+ <ulink url="http://www.iSilo.com/">iSilo</ulink> >+ µ{¦¡¨Ó¾\Ū</entry> > </row> > > <row> > <entry><literal>pdf</literal></entry> > >- <entry>Adobe's Portable Document Format</entry> >+ <entry>Adobe's PDF ®æ¦¡</entry> > </row> > > <row> > <entry><literal>ps</literal></entry> > >- <entry>Postscript</entry> >+ <entry>&postscript; ®æ¦¡</entry> > </row> > > <row> > <entry><literal>rtf</literal></entry> > >- <entry>Microsoft's Rich Text Format<footnote> >- <para>Page numbers are not automatically updated >- when loading this format in to Word. Press >- <keycombo action="simul"><keycap>CTRL</keycap><keycap>A</keycap></keycombo>, >- <keycombo action="simul"><keycap>CTRL</keycap><keycap>END</keycap></keycombo>, >- <keycap>F9</keycap> after loading the document, to >- update the page numbers.</para> >+ <entry>Microsoft's RTF®æ¦¡<footnote> >+ <para>·í¨Ï¥Î MS Word ¨Ó¶}±Ò RTF ®æ¦¡ªº¸Ü¡A¶¼ÆÅã¥Ü¨Ã¤£·|¦Û°Ê§ó·s¡C >+ (¦b¶}±Ò¤å¥ó«á¡An«ö <keycombo >+ action="simul"><keycap>CTRL</keycap><keycap>A</keycap></keycombo>, >+ <keycombo >+ action="simul"><keycap>CTRL</keycap><keycap>END</keycap></keycombo>, >+ <keycap>F9</keycap>¡A³o¼Ë¤l¤~·|§ó·s¶¼ÆªºÅã¥Ü¡C)</para> > </footnote> > </entry> > </row> >@@ -694,7 +788,7 @@ > <row> > <entry><literal>txt</literal></entry> > >- <entry>Plain text</entry> >+ <entry>¯Â¤å¦r(ASCII)</entry> > </row> > </tbody> > </tgroup> >@@ -702,33 +796,31 @@ > </listitem> > > <listitem> >- <para>The compression and packaging scheme. There are three of >- these currently in use.</para> >+ <para>¤å¥óªºÀ£ÁY¡B¥´¥]¤è¦¡¡G¥Ø«e¦³¤TºØ¤è¦¡¡G</para> > > <orderedlist> > <listitem> >- <para>Where the format is <literal>html-split</literal>, the >- files are bundled up using &man.tar.1;. The resulting >- <filename>.tar</filename> file is then compressed using >- the compression schemes detailed in the next point.</para> >+ <para>·í±Ä¥Î >+ <literal>³¹¸`¼Ò¦¡(html-split)</literal>¡A³¹¸`¼Ò¦¡©Ò²£¥Íªº¦UÀÉ®×·|¥ý¨Ï¥Î >+ &man.tar.1; ¨ÓÀ£ÁY¡CÀɦWµ²§À¦³ <filename>.tar</filename> ªºÀÉ®×´N¬O tar ®æ¦¡¡C >+ ±µµÛ¡A·|¦A¥H¤U¦C¤è¦¡¦AÀ£ÁY¡C >+ </para> > </listitem> > > <listitem> >- <para>All the other formats generate one file, called >- <filename>book.<replaceable>format</replaceable></filename> >- (i.e., <filename>book.pdb</filename>, >- <filename>book.html</filename>, and so on).</para> >- >- <para>These files are then compressed using three >- compression schemes.</para> >+ <para>¨ä¥L®æ¦¡ªºÀɮ׳£·|¬O³æ¤@ÀɮסAÀɦW³q±`·|¬O¡G >+ <filename>book.<replaceable>®æ¦¡</replaceable></filename> >+ (Á|¨Ò¡G <filename>book.pdb</filename>¡A >+ <filename>book.html</filename> µ¥µ¥..«á±³q±`¥[¤W¡y.®æ¦¡¡z).</para> >+ <para>¦Ó³o¨ÇÀÉ®×·|¤À§O¥H¨âºØÀ£ÁY«¬ºA¶i¦æÀ£ÁY¡A¦Ó¦s¦¨¨âºØÀ£ÁY«¬ºA¡C</para> > >- <informaltable frame="none"> >+ <informaltable frame="none" pgwide="1"> > <tgroup cols="2"> > <thead> > <row> >- <entry>Scheme</entry> >+ <entry>®æ¦¡</entry> > >- <entry>Description</entry> >+ <entry>»¡©ú</entry> > </row> > </thead> > >@@ -736,166 +828,137 @@ > <row> > <entry><literal>zip</literal></entry> > >- <entry>The Zip format. If you want to uncompress >- this on FreeBSD you will need to install the >- <filename role="package">archivers/unzip</filename> port >- first.</entry> >- </row> >- >- <row> >- <entry><literal>gz</literal></entry> >- >- <entry>The GNU Zip format. Use &man.gunzip.1; to >- uncompress these files, which is part of >- FreeBSD.</entry> >+ <entry>Zip ®æ¦¡¡AYn¦b FreeBSD ¤W¸ÑÀ£ zip ÀÉ¡A«h¥²¶·¥ý¦w¸Ë >+ <filename role="package">chinese/unzip</filename> ©Î >+ <filename role="package">archivers/unzip</filename>¡C >+ </entry> > </row> > > <row> > <entry><literal>bz2</literal></entry> > >- <entry>The BZip2 format. Less widespread than the >- others, but generally gives smaller files. >- Install the <filename role="package">archivers/bzip2</filename> >- port to uncompress these files.</entry> >+ <entry>BZip2 ®æ¦¡¡AÁöµM¤£¦p zip ®æ¦¡ªº¼sªx¨Ï¥Î¡A¦ý¬O¦n³B¦b©ó¥iÀ£ÁY¦¨§ó¤pªºÀɮסC >+ n¸ÑÀ£ bz2 ®æ¦¡ªº¸Ü¡A»Ý¥ý¦w¸Ë <filename role="package">archivers/bzip2 >+ </filename>¡C</entry> > </row> > </tbody> > </tgroup> > </informaltable> > >- <para>So the Postscript version of the Handbook, compressed >- using BZip2 will be stored in a file called >- <filename>book.ps.bz2</filename> in the >- <filename>handbook/</filename> directory.</para> >- </listitem> >- >- <listitem> >- <para>The formatted documentation is also available as a >- FreeBSD package, of which more later.</para> >+ <para>©Ò¥H¹³¬O Handbook ªº &postscript; ª©®æ¦¡¡A·|¥H BZip2 ®æ¦¡À£ÁY¡A >+ ¦s©ñ¦b <filename>handbook/</filename> ¥Ø¿ý¤º¡A >+ ÀɦW´N¬O<filename>book.ps.bz2</filename>¡C</para> > </listitem> > </orderedlist> > </listitem> > </itemizedlist> > >- <para>After choosing the format and compression mechanism that you >- want to download, you must then decide whether or not you want to >- download the document as a FreeBSD >- <emphasis>package</emphasis>.</para> >- >- <para>The advantage of downloading and installing the package is >- that the documentation can then be managed using the normal >- FreeBSD package management comments, such as &man.pkg.add.1; and >- &man.pkg.delete.1;.</para> >- >- <para>If you decide to download and install the package then you >- must know the filename to download. The documentation-as-packages >- files are stored in a directory called >- <filename>packages</filename>. Each package file looks like >- <filename><replaceable>document-name</replaceable>.<replaceable>lang</replaceable>.<replaceable>encoding</replaceable>.<replaceable>format</replaceable>.tgz</filename>.</para> >- >- <para>For example, the FAQ, in English, formatted as PDF, is in the >- package called >- <filename>faq.en_US.ISO8859-1.pdf.tgz</filename>.</para> >- >- <para>Knowing this, you can use the following command to install the >- English PDF FAQ package.</para> >+ <para>¿ï¾Ü·Qn¤U¸üªº¤å¥ó®æ¦¡»PÀ£ÁY«¬ºA¤§«á¡A«hn¨M©w¬O§_¥H FreeBSD <emphasis>®M¥ó(package)</emphasis> >+ «¬ºA¨Ó¤U¸ü¡C</para> >+ >+ <para>¤U¸ü¡B¦w¸Ë¡ypackage¡zªº¦n³B¦b©ó¡G¥i¥H³z¹L¤@¯ë FreeBSD >+ ®M¥óºÞ²z¤è¦¡¨Ó¶i¦æºÞ²z¡A¤ñ¦p &man.pkg.add.1; ¤Î >+ &man.pkg.delete.1;¡C</para> > >- <screen>&prompt.root; <userinput>pkg_add ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/packages/faq.en_US.ISO8859-1.pdf.tgz</userinput></screen> > >- <para>Having done that, you can use &man.pkg.info.1; to determine >- where the file has been installed.</para> >+ <para>Y¨M©w¦nn¤U¸ü¡B¦w¸Ë¡ypackage¡zªº¸Ü¡A¥²¶·n½T»{©Òn¤U¸üªºÀɦW¡C >+ ¤å¥ópµeªº®M¥ó(package)³q±`¬O©ñ¦b¬O <filename>packages</filename> ªº¥Ø¿ý¤º¡A >+ ¨CÓ¤å¥ópµeªº®M¥óÀɦW³q±`¬O¡G >+ <filename><replaceable>¤å¥ó¦WºÙ</replaceable>.<replaceable>»y¨t</replaceable>.<replaceable>½s½X</replaceable>.<replaceable>®æ¦¡</replaceable>.tgz</filename> >+ ¡C</para> > >- <screen>&prompt.root; <userinput>pkg_info -f faq.en_US.ISO8859-1.pdf</userinput> >-Information for faq.en_US.ISO8859-1.pdf: >+ <para>Á|Ó¨Ò¤l¡A^¤åª©ªº FAQ (®æ¦¡¿ï¾Ü PDF)¦b package ´N¥s°µ >+ <filename>faq.en_US.ISO8859-1.pdf.tgz</filename>¡C</para> >+ >+ <para>¦AÁ|Ó¨Ò¤l¡A¤¤¤åª©ªº FAQ (®æ¦¡¿ï¾Ü PDF)¦b package ´N¥s°µ >+ <filename>faq.zh_TW.Big5.pdf.tgz</filename>¡C</para> >+ >+ <para>ª¾¹D³oÂI¤§«á¡A´N¥i¥H¥Î¤U±«ü¥O¨Ó¦w¸Ë¤¤¤åª© FAQ ®M¥ó¡G</para> >+ >+ <screen>&prompt.root; <userinput>pkg_add ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/packages/faq.zh_TW.Big5.pdf.tgz</userinput></screen> >+ >+ <para>§¹¦¨¤§«á¡A¥i¥H¥Î &man.pkg.info.1; ¨Ó§ä¥XÀɮ׸˦bþÃä¡G</para> >+ >+ <screen>&prompt.root; <userinput>pkg_info -f faq.zh_TW.Big5.pdf</userinput> >+Information for faq.zh_TW.Big5.pdf: > > Packing list: >- Package name: faq.en_US.ISO8859-1.pdf >- CWD to /usr/share/doc/en_US.ISO8859-1/books/faq >+ Package name: faq.zh_TW.Big5.pdf >+ CWD to /usr/share/doc/zh_TW.Big5/books/faq > File: book.pdf > CWD to . > File: +COMMENT (ignored) > File: +DESC (ignored)</screen> > >- <para>As you can see, <filename>book.pdf</filename> will have been >- installed in to >- <filename>/usr/share/doc/en_US.ISO8859-1/books/faq</filename>. >- </para> >+ <para>¦p¦P±z©Ò¬Ý¨ìªº <filename>book.pdf</filename> ·|³Q¦w¸Ë¨ì >+ <filename>/usr/share/doc/zh_TW.Big5/books/faq</filename> ¤º¡C</para> > >- <para>If you do not want to use the packages then you will have to >- download the compressed files yourself, uncompress them, and then >- copy the appropriate documents in to place.</para> >- >- <para>For example, the split HTML version of the FAQ, compressed >- using &man.gzip.1;, can be found in the >- <filename>doc/en_US.ISO8859-1/books/faq/book.html-split.tar.gz</filename> >- file. To download and uncompress that file you would have to do >- this.</para> >+ <para>Y¤£·Q¥Î package ¤è¦¡¦w¸Ë¡A¨º»ò´N»Ý¤â°Ê¤U¸ü¡B¸ÑÀ£ÁY¡B½Æ»s¨ì§A·QnÂ\©ñªº¦ì¸m¥h¡C</para> > >- <screen>&prompt.root; <userinput>fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/faq/book.html-split.tar.gz</userinput> >-&prompt.root; <userinput>gzip -d book.html-split.tar.gz</userinput> >+ <para>Á|¨Ò¡A³¹¸`¼Ò¦¡(split HTML)ª©ªº^¤å FAQ (À£ÁY¬° &man.bzip2.1;)·|©ñ¦b >+ <filename>doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2</filename> >+ n¤U¸ü¡B¸ÑÀ£ªº¸Ü¡A«hn¥´¡G</para> >+ >+ <screen>&prompt.root; <userinput>fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2</userinput> >+&prompt.root; <userinput>bzip2 -d book.html-split.tar.bz2</userinput> > &prompt.root; <userinput>tar xvf book.html-split.tar</userinput></screen> > >- <para>You will be left with a collection of >- <filename>.html</filename> files. The main one is called >- <filename>index.html</filename>, which will contain the table of >- contents, introductory material, and links to the other parts of >- the document. You can then copy or move these to their final >- location as necessary.</para> >+ <para>³o®É§A·|¬Ý¨ì¤@°ï <filename>.html</filename> ªºÀɮסA >+ ¥Dnªº¥Ø¿ýÀɬ° <filename>index.html</filename> >+ ¤º§t¥D¥Ø¿ý¤Î³sµ²¨ì¨ä¥L¤å¥ó¡C(Y¦³»Ýnªº¸Ü¡A¤]¥i¥H½Æ»s©Î·h²¾³o¨ÇÀɮרì¦P¤@¥Ø¿ý¤U)</para> > </answer> > </qandaentry> > > <qandaentry> > <question id="mailing"> >- <para>Where do I find info on the FreeBSD mailing lists?</para> >+ <para>þ¸Ì¦³Ãö©ó FreeBSD ªº¶l»¼½×¾Â(mailing lists)©O¡H</para> > </question> > > <answer> >- <para>You can find full information in the <ulink >- URL="../handbook/eresources.html#ERESOURCES-MAIL">Handbook >- entry on mailing-lists</ulink>.</para> >+ <para>³oÓ°ÝÃD¡A¥i¥H±q¡m FreeBSD ¨Ï¥Î¤â¥U¡n¤W±ªº <ulink >+ url="&url.books.handbook;/eresources.html#ERESOURCES-MAIL">¶l»¼½×¾Â(mailing-lists)</ulink> >+ ³¡¤ÀÀò±oµª®×¡C</para> > </answer> > </qandaentry> > > <qandaentry> > <question id="y2k"> >- <para>Where do I find the FreeBSD Y2K info?</para> >+ <para>§Ú¸Ó±qþÃä±o¨ì¦³Ãö FreeBSD ¦b¤dÁHÂÎ(Y2K)¤è±ªº¸ê®Æ©O?</para> > </question> > > <answer> >- <para>You can find full information in the <ulink >- URL="../../../../y2kbug.html">FreeBSD Y2K >- page</ulink>.</para> >+ <para>³oµª®×¥i¥H¦b <ulink >+ url="&url.base;/y2kbug.html">FreeBSD ¤dÁHÂÎ(Y2K)</ulink>¤W±Àò±o</para> > </answer> > </qandaentry> > > <qandaentry> > <question id="newsgroups"> >- <para>What FreeBSD news groups are available?</para> >+ <para>¦³þ¨Ç¥i¥H¨Ï¥Îªº FreeBSD ·s»D¸s²Õ(news groups)©O?</para> > </question> > > <answer> >- <para>You can find full information in the <ulink >- URL="../handbook/eresources-news.html">Handbook entry on >- newsgroups</ulink>.</para> >+ <para>³oµª®×¥i¥H±q¡m FreeBSD ¨Ï¥Î¤â¥U¡n¤W±ªº <ulink >+ url="&url.books.handbook;/eresources-news.html">·s»D¸s²Õ(newsgroups)</ulink> >+ ³¡¤ÀÀò±oµª®×¡C</para> > </answer> > </qandaentry> > > <qandaentry> > <question id="irc"> >- <para>Are there FreeBSD IRC (Internet Relay Chat) >- channels?</para> >+ <para>¦³þ¨Ç FreeBSD IRC (Internet Relay Chat)ÀW¹D©O¡H</para> > </question> > > <answer> >- <para>Yes, most major IRC networks host a FreeBSD chat >- channel:</para> >+ <para>¦³ªº¡A¤j³¡¤Àªº IRC ¥D¾÷³£¦³ FreeBSD ²á¤ÑÀW¹D¡G</para> > > <itemizedlist> > <listitem> > <para>Channel <literal>#FreeBSD</literal> on >- <ulink URL="http://www.efnet.org/index.php">EFNet</ulink> >+ <ulink url="http://www.efnet.org/index.php">EFNet</ulink> > is a FreeBSD forum, but do not go there for tech > support or try to get folks there to help you avoid >- the pain of reading man pages or doing your own research. >+ the pain of reading manual pages or doing your own research. > It is a chat channel, first and foremost, and topics there > are just as likely to involve sex, sports or nuclear > weapons as they are FreeBSD. You Have Been Warned! >@@ -904,35 +967,37 @@ > > <listitem> > <para>Channel <literal>#FreeBSDhelp</literal> on >- <ulink URL="http://www.efnet.org/index.php">EFNet</ulink> >+ <ulink url="http://www.efnet.org/index.php">EFNet</ulink> > is a channel dedicated to helping FreeBSD users. They >- are much more sympathetic to questions then >+ are much more sympathetic to questions than > <literal>#FreeBSD</literal> is.</para> > </listitem> > > <listitem> > <para>Channel <literal>#FreeBSD</literal> on >- <ulink URL="http://www.dal.net/">DALNET</ulink> >+ <ulink url="http://www.dal.net/">DALNET</ulink> > is available at <hostid>irc.dal.net</hostid> in the > US and <hostid>irc.eu.dal.net</hostid> in Europe.</para> > </listitem> > > <listitem> >+ <para>Channel <literal>#FreeBSDHelp</literal> on >+ <ulink url="http://www.dal.net/">DALNET</ulink> >+ is available at <hostid>irc.dal.net</hostid> in the >+ US and <hostid>irc.eu.dal.net</hostid> in Europe. >+ The channel owners also have a web page with useful >+ information about the channel and &os;, available at >+ <ulink url="http://www.freebsdhelp.net/"></ulink>.</para> >+ </listitem> >+ >+ <listitem> > <para>Channel <literal>#FreeBSD</literal> on >- <ulink URL="http://www.undernet.org/">UNDERNET</ulink> >+ <ulink url="http://www.undernet.org/">UNDERNET</ulink> > is available at <hostid>us.undernet.org</hostid> > in the US and <hostid>eu.undernet.org</hostid> in Europe. > Since it is a help channel, be prepared to read the > documents you are referred to.</para> > </listitem> >- >- <listitem> >- <para>Channel <literal>#FreeBSD</literal> on <ulink >- url="http://www.hybnet.net/">HybNet</ulink>. This channel >- <emphasis>is</emphasis> a help channel. A list of servers >- can be found on the <ulink >- url="http://www.hybnet.net/">HybNet web site</ulink>.</para> >- </listitem> > </itemizedlist> > > <para>Each of these channels are distinct and are not >@@ -948,26 +1013,21 @@ > > <qandaentry> > <question id="training"> >- <para>Where can I get commercial FreeBSD training and support?</para> >+ <para>¥i¥H±qþÃäÀò±o FreeBSD ªº°Ó·~½Òµ{°V½m¤Î§Þ³N¤ä´©©O¡H</para> > </question> > > <answer> >- <para>DaemonNews provides commercial training and support for >- FreeBSD. More information can be found at their >- <ulink url="http://www.bsdmall.com/">BSD Mall</ulink> >- site.</para> >- >- <para>FreeBSD Services Ltd provide commercial support for FreeBSD >- in the UK (as well as selling FreeBSD on DVD). See their >- <ulink url="http://www.freebsd-services.com">web site</ulink> >- for more information.</para> >- >- <para>The FreeBSD Mall provides commercial FreeBSD support. >- You can get more information at their <ulink >- url="http://www.freebsdmall.com/">web site</ulink>.</para> >+ <para>DaemonNews ¦³±Mªù´£¨Ñ FreeBSD ªº°Ó·~½Òµ{°V½m¤Î§Þ³N¤ä´©¡C >+ ¸Ô±¡½Ð¨ì <ulink url="http://www.bsdmall.com/">BSD Mall</ulink> >+ ¹î¬Ý¡AÁÂÁ¡C</para> >+ >+ <para>FreeBSD Mall ¦³´£¨Ñ°Ó·~¤Æªº BSD §Þ³N¤ä´©¡A >+ ¸Ô±¡½Ð¨ì <ulink >+ url="http://www.freebsdmall.com/">FreeBSD Mall</ulink> ¹î¬Ý¡AÁÂÁ¡C</para> >+ > >- <para>Any other organizations providing training and support should >- contact the project in order to be listed here.</para> >+ <para>¨ä¥L¥ô¦ó¦³´£¨Ñ½Òµ{°V½m¤Î§Þ³N¤ä´©ªº²Õ´¡B³æ¦ì¡AY¤]·Q¦Cªí©ó¦¹ªº¸Ü¡A >+ ½Ð»P &a.doc; Ápµ¸¡AÁÂÁ¡C</para> > </answer> > </qandaentry> > </qandaset> >@@ -985,33 +1045,30 @@ > </author> > </chapterinfo> > >- <title>Installation</title> >+ <title>¦w¸Ë</title> > > <qandaset> > <qandaentry> > <question id="floppy-download"> >- <para>Which file do I download to get FreeBSD?</para> >+ <para>Yn¥Î³nºÐ¤ù¶}¾÷¨Ó¦w¸Ë FreeBSD ªº¸Ü¡An¤U¸üþ¨ÇÀɮשO¡H</para> > </question> > > <answer> >- <para>Prior to release 3.1, you only needed one floppy image to >- install FreeBSD, namely <filename>floppies/boot.flp</filename>. >- However, since release 3.1 the Project has added out-of-the-box >- support for a wide variety of hardware, which takes up more >- space. For 3.x and later you need two floppy images: >- <filename>floppies/kernel.flp</filename> and >- <filename>floppies/mfsroot.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> >+ <para>&os; 4.X ªº¸Ü¡A»Ýn¨âÓ image ÀÉ¡G >+ <filename>floppies/kernel.flp</filename> ¤Î >+ <filename>floppies/mfsroot.flp</filename>¡Cimage ÀÉ¥²¶·¥Î¤u¨ã¹³¬O >+ <command>fdimage</command> ©Î &man.dd.1; ¨Ó¶Ç°e¨ìºÏ¤ù¤W¡C >+ Y¬O¦b &os; 5.3 (¤Î¤§«áª©¥»)¦³«·s³W¹º¶}¾÷¤ù¬[ºc¡A©Ò¥Hn§ìªº¬O >+ <filename>floppies/boot.flp</filename> ¥H¤Î <filename>floppies/kern<replaceable>X</replaceable></filename> >+ ÀÉ®×(¥Ø«e X ¬° 1 ¸ò 2 ¨âÓ¡A¥[¤W<filename>floppies/boot.flp</filename>¡AÁ`¦@¬O 3 ÓÀÉ®×)¡C</para> >+ >+ <para>Y·Q¦Û¤v¤U¸ü distributions ªº¸Ü(¤ñ¦p¥H &ms-dos; Àɮרt²Î®æ¦¡¦w¸Ë)¡A >+ ¥H¤U¬O«ØÄ³n§ìªº distributions ¡G</para> > > > <itemizedlist> > <listitem> >- <para>bin/</para> >+ <para>base/ (bin/ in 4.X)</para> > </listitem> > > <listitem> >@@ -1032,61 +1089,50 @@ > </itemizedlist> > > >- <para>Full instructions on this procedure and a little bit more >- about installation issues in general can be found in the >- <ulink URL="../handbook/install.html">Handbook entry on >- installing FreeBSD</ulink>.</para> >+ <para>§¹¾ã¦w¸Ë¨BÆJ¥H¤Î¤j³¡¤Àªº¦w¸Ë°ÝÃD¡A½Ð°Ñ¾\¡m FreeBSD ¨Ï¥Î¤â¥U¡nªº >+ <ulink url="&url.books.handbook;/install.html">¦w¸Ë 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> >+ <para>YºÏ¤ù¸Ë¤£¤U image Àɪº¸Ü¡A¸Ó«ç»ò¿ì©O¡H</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>¤@±i 3.5 ^¦T(1.44MB) ªººÏºÐ¤ù¬O¥i¥H¸Ë¤W 1474560 bytes ªº¸ê®Æ >+ ¡A¦Ó¶}¾÷¤ùªº image Àɮפj¤p¹ê»Ú¤W¤]¬O 1474560 bytes¡C</para> > >- <para>Common mistakes when preparing the boot floppy are:</para> >+ <para>¦b»s§@¶}¾÷¤ù®É¡A±`¨£¿ù»~¦³¡G</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> >+ <para>¨Ï¥Î <acronym>FTP</acronym> ¨Ó¤U¸üÀɮ׮ɡA >+ ¥¼¿ï¾Ü <emphasis>binary</emphasis> ¶Ç¿é¼Ò¦¡¨Ó¤U¸ü¡C</para> >+ >+ >+ <para>¦³¨Ç FTP clientºÝµ{¦¡¡A¬O¹w³]±N¶Ç¿é¼Ò¦¡³]©w¬° >+ <emphasis>ascii</emphasis> ¼Ò¦¡¡A¦Ó¥B·|×§ï±µ¦¬¨ìªºÀɮצæ§À¦r¦ê¬° client ºÝªº§@·~¨t²Î¤è¦¡ >+ ¡A¤ñ¦p newline(&unix;®æ¦¡) ¨ì¤F§@·~¨t²Î¬° &windows; ªº client ºÝ·|³Q§ï¬° CR-LF(&ms-dos;®æ¦¡)¡A >+ ³o·|¨Ï±o image ÀÉ¥»¨¾D¨ì×§ï¦ÓµLªk¥¿±`¨Ï¥Î¡C¦]¦¹¡A¦pªG¤U¸üªº image >+ Àɮפj¤pY»P FTP ¥D¾÷¤W±ªºÀÉ®× <emphasis>¤£¤@P</emphasis> >+ ªº¸Ü¡A½Ð«·s¨Ï¥Î binary ¶Ç¿é¼Ò¦¡¤U¸ü§Y¥i¡C</para> >+ >+ <para>FTP «ü¥O: ¶i¤J FTP ¤§«á¡A¥´ <emphasis>binary</emphasis> >+ «ü¥O¡A§Y¥i¤Á´«¨ì binary ¶Ç¿é¼Ò¦¡¡AµM«á¦A¤U¸ü¬ÛÃö image ÀɮסC</para> > </listitem> > > <listitem> >- <para>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="../handbook/install.html">installation guide to >- FreeBSD</ulink>.</para> >+ <para>ª½±µ¥Î &ms-dos; ªº <command>copy</command> «ü¥O(©ÎÃþ¦ü >+ ªº GUI µ{¦¡¡B©Î¬Oµøµ¡¤Wª½±µ½Æ»s)¨Ó½Æ»s¶}¾÷¥Îªº image ÀɨìºÏ¤ù¤W¡C >+ </para> >+ >+ <para>¤£¥i¥H¥Î¹³¬O <command>copy</command> ³oÃþµ{¦¡ª½±µ±N image >+ Àɽƻs¨ìºÏ¤ù¤W¡A¦]¬° image ÀÉ¥»¨¥]§t¤F§¹¾ãªººÏy¸ê®Æ¡A©Ò¥H¤£¯à³æ¯Â¥Î½Æ»s¤è¦¡¡A >+ ¦Ó¥²¶·¨Ï¥Î§C¶¥¤u¨ãµ{¦¡(¹³¬O <command>fdimage</command> ©Î <command>rawrite</command>)¡A >+ ¥H <quote>raw</quote> ¤è¦¡¶Ç°e¨ìºÏ¤ù¤W¡C(³o³¡¤À¥i°Ñ¾\¡m FreeBSD ¨Ï¥Î¤â¥U¡n¤Wªº <ulink >+ url="&url.books.handbook;/install.html">¦w¸Ë FreeBSD</ulink>)</para> > </listitem> > </itemizedlist> > </answer> >@@ -1094,162 +1140,139 @@ > > <qandaentry> > <question id="install-instructions-location"> >- <para>Where are the instructions for installing FreeBSD?</para> >+ <para>¥i¥H¦bþÃä§ä¨ì¦w¸Ë FreeBSD ªº¸Ñ»¡¨BÆJ©O¡H</para> > </question> > > <answer> >- <para>Installation instructions can be found in the >- <ulink URL="../handbook/install.html">Handbook entry on installing FreeBSD</ulink>.</para> >+ <para>¦w¸Ë¨BÆJªº¸Ñ»¡¡A½Ð°Ñ¾\¡m FreeBSD ¨Ï¥Î¤â¥U¡n¤Wªº >+ <ulink url="&url.books.handbook;/install.html">¦w¸Ë FreeBSD</ulink> ³¹¸`³¡¤À¡C</para> > </answer> > </qandaentry> > > <qandaentry> > <question id="need-to-run"> >- <para>What do I need in order to run FreeBSD?</para> >+ <para>n¶] FreeBSD »Ýn¤°»òªº°t³Æ©O¡H</para> > </question> > > <answer> >- <para>You will need a 386 or better PC, with 5 MB or more of RAM >- and at least 60 MB of hard disk space. It can run with a low >- end MDA graphics card but to run X11R6, a VGA or better video >- card is needed.</para> >+ <para>&os; 5.X ¤§«eªºª©¥»¡AµwÅé»Ý¨D¬° 386 ©Î§ó°ª¯Åªº PC >+ ¡A°O¾ÐÅé(RAM)¦Ü¤Ön 5 MB ©Î§ó¦h¡AµwºÐªÅ¶¡¦Ü¤Ön 60 MB ©Î§ó¦h¡C >+ ¤£¹L¡A&os; ¡y¨t²Î¦w¸Ëµ{¦¡¡zªº°O¾ÐÅé(RAM)»Ý¨D¬°¦Ü¤Ö 16 MB¡C</para> >+ >+ <para>±q &os; 5.X °_¡AµwÅé»Ý¨D¬° 486 ©Î§ó°ª¯Åªº PC >+ ¡A°O¾ÐÅé(RAM)¦Ü¤Ön 24 MB ©Î§ó¦h¡AµwºÐªÅ¶¡¦Ü¤Ön 150 MB ©Î§ó¦h¡C >+ </para> > >- <para>See also >- <xref linkend="hardware"></para> >+ <para>&os; ªº©Ò¦³ª©¥»³£¥i¥H¥u¥Î§C¶¥ªº MDA ³W®æÅã¥Ü¥d¡A¤£¹L¡Kn¶] X11R6 µøµ¡ªº¸Ü¡A >+ ÁÙ¬O¦Ü¤Ö¥Î VGA ©Î§ó¦n³W®æªºÅã¥Ü¥d¨Ó¥Î§a¡C</para> >+ >+ <para>³o³¡¤À¤]¥i°Ñ¾\ <xref linkend="hardware">¡C</para> > > </answer> > </qandaentry> > > <qandaentry> > <question id="four-meg-ram-install"> >- <para>I have only 4 MB of RAM. Can I install FreeBSD?</para> >+ <para>§Ú¹q¸£ RAM ¥u¦³ 4MB ¦Ó¤w¡A¥i¥H¸Ë FreeBSD ¶Ü¡H</para> > </question> > > <answer> >- <para>FreeBSD 2.1.7 was the last version of FreeBSD that >- could be installed on a 4MB system. FreeBSD 2.2 and later >- needs at least 5MB to install on a new system.</para> >- >- <para>All versions of FreeBSD will <emphasis>run</emphasis> >- in 4MB of RAM, they just cannot run the installation >- program in 4MB. You can add extra memory for the install >- process, if you like, and then after the system is up and >- running, go back to 4MB. Or you could swap your disk into >- a system which has >4MB, install onto the disk and then >- swap it back.</para> >- >- <para>FreeBSD 2.1.7 will not install with 640 kB base + 3 MB >- extended memory. If your motherboard can remap some of the >- <quote>lost</quote> memory out of the 640kB to 1MB region, >- then you may still be able to get FreeBSD 2.1.7 up. Try >- to go into your BIOS setup and look for a >- <quote>remap</quote> option. Enable it. You may also >- have to disable ROM shadowing. It may be easier to get 4 >- more MB just for the install. Build a custom kernel with >- only the options you need and then remove the 4MB out. >- You can also install 2.0.5 and then upgrade your system to >- 2.1.7 with the <quote>upgrade</quote> option of the 2.1.7 >- installation program.</para> >- >- <para>After the installation, if you build a custom kernel, >- it will run in 4 MB. Someone has even successfully booted >- with 2 MB, although the system was almost unusable.</para> >+ <para>¦w¸Ë &os; 4.X ªº°O¾ÐÅé»Ý¨D¬°¦Ü¤Ö 5 MB ¡A¦Ó >+ ¦w¸Ë &os; 5.X (§t¤§«áª©¥») «h¬O¦Ü¤Ön 8 MB ¡C</para> >+ >+ <para>¦b 5.X ¤§«eªº©Ò¦³ &os; ª©¥»¡A³£¥i¥H¥u¥Î 4 MB ªº°O¾ÐÅé¨Ó >+ <emphasis>¡y¹B§@¡z</emphasis>¡A¤£¹L¡A«e±¨º¸`§ÚÌ»¡¹L¤F¡y¨t²Î¦w¸Ëµ{¦¡¡zªº¸Ü¡A >+ «hµLªk¥u¥Î 4 MB ªº°O¾ÐÅé¨Ó°õ¦æ¡C¦]¦¹¡A§A¥i¥H¥ý¦b¡y¨t²Î¦w¸Ëµ{¦¡¡z³o¨BÆJ¤§«e¡A >+ ¥ý±N°O¾ÐÅé¥[¨ì 16 MB ¥H¤W¡A¦w¸Ë§¹ FreeBSD ¤§«á¡A´N¥i¥H§â¦h¾lªº°O¾ÐÅ鮳¤U¨Ó¡C >+ ©ÎªÌ¬O¡A¥ý§ân¦w¸ËªºµwºÐ®³¨ì¦³¨¬°÷°O¾ÐÅ骺¾÷¾¹¤W¥ý¸Ë¦n¡A >+ µM«á¦A§âµwºÐ©ñ¦^ì¾÷¾¹¡C</para> >+ >+ <para>¦¹¥~¡A¥u¥Î 4 MB ªº°O¾ÐÅé¨Ó¹B§@ªº¸Ü¡A¥²¶·n¦Û»s kernel(®³±¼¤£¥²nªº¥H¤ÎÄ묹¤@¨ÇªF¦è)¡C >+ ¤]¦³¤Hªº &os ¦¨¥\¥u¥Î 2 MB ªº°O¾ÐÅé¨Ó¶}¾÷(ÁöµM³o¼Ëªº¨t²Î´X¥Gµ¥©ó¼o¤F..)</para> > </answer> > </qandaentry> > > <qandaentry> > <question id="custom-boot-floppy"> >- <para>How can I make my own custom install floppy?</para> >+ <para>n«ç¼Ë¤~¯à¦Û¦æ¥´³y±M¥Îªº¶}¾÷¡B¦w¸ËºÏ¤ù©O¡H</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>¥Ø«e¡AÁÙ¨S¦³¿ìªk<emphasis>¡y¥u¡z</emphasis>¦Û»s±M¥Îªº¶}¾÷¡B¦w¸ËºÏ¤ù¡C >+ ¥²¶·³z¹L¦Û¦æ¥´³y§¹¾ã§@·~¨t²Îªº release(µo¦æ)¡A³o¼Ë¸Ì±¤~·|¥]¬A¦Û¤vªº¶}¾÷¡B¦w¸ËºÏ¤ù¡C</para> > >- <para>To make a custom release, follow the instructions in the >- <ulink url="../../articles/releng/article.html">Release >- Engineering</ulink> article.</para> >+ <para>Y·Q¦Û¦æ¥´³y¡Bµo¦æ(release)¤@Ó§¹¾ãªº§@·~¨t²Î¡A½Ð°Ñ¾\³o½g >+ <ulink url="&url.articles.releng;/article.html">Release Engineering</ulink> ¤å³¹¡C</para> > </answer> > </qandaentry> > > <qandaentry> > <question id="multiboot"> >- <para>Can I have more than one operating system on my PC?</para> >+ <para>§Ú¹q¸£¤W¥i¥H¦³¦h«§@·~¨t²Î¶Ü¡H</para> > </question> > > <answer> >- <para>Have a look at >- <ulink URL="../../articles/multi-os/index.html"> >- the multi-OS page</ulink>.</para> >+ <para>¥i¥H§r¡A½Ð°Ñ¾\ >+ <ulink url="&url.articles.multi-os;/index.html"> >+ ¦h«§@·~¨t²Î</ulink> ³o½g¤å³¹¡C</para> > </answer> > </qandaentry> > > <qandaentry> > <question id="windows-coexist"> >- <para>Can Windows 95/98 co-exist with FreeBSD?</para> >+ <para>&windows; ¥i¥H»P FreeBSD ¦@¦s©ó¹q¸£¤W¶Ü¡H</para> > </question> > > <answer> >- <para>Install Windows 95/98 first, after that FreeBSD. >- FreeBSD's boot manager will then manage to boot Win95/98 and >- FreeBSD. If you install Windows 95/98 second, it will boorishly >- overwrite your boot manager without even asking. If that >- happens, see the next section.</para> >+ <para>¥ý¸Ë &windows; ¦A¸Ë FreeBSD¡C >+ ¨º»ò FreeBSD ¶}¾÷ºÞ²zû(boot manager)´N·|¥X²{¿ï³æÅý§A¿ï¾Ün¥H &windows; ©Î >+ FreeBSD ¨Ó¶}¾÷¡C¤£¹L¡AY§A¬O¥ý¸Ë FreeBSD ¦A¸Ë &windows; ªº¸Ü¡A >+ ¨º»ò &windows; ±N·|¤£°Ý¥ý®_¡A§â FreeBSD ªº¶}¾÷ºÞ²zû(boot manager)»\±¼¡A >+ ·í§A¹J¤W³oºØ±¡ªp®É¡A½Ð°Ñ¦Ò¤U¤@¸`»¡©ú¡C</para> > </answer> > </qandaentry> > > <qandaentry> > <question id="win95-damaged-boot-manager"> >- <para>Windows 95/98 killed my boot manager! >- How do I get it back?</para> >+ <para>¶ã¡ã&windows; §â§Úªº¶}¾÷ºÞ²zû(boot manager)®³±¼¤F¡I§Ún«ç»ò±Ï¦^¨Ó©O¡H</para> > </question> > > <answer> >- <para>You can reinstall the boot manager FreeBSD comes with in >- one of three ways:</para> >+ <para>¥i¥H¥Î¥H¤U¤TºØ¤è¦¡¤§¤@¡A¨Ó±Ï¦^§Aªº FreeBSD ¶}¾÷ºÞ²zû(boot manager)¡G</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> >+ <para>¥i¥H±q¦U FreeBSD FTP ¯¸ªº <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">/pub/FreeBSD/tools/</ulink> >+ §ä¨ì <filename>bootinst.exe</filename> ¤Î <filename>boot.bin</filename> ³o¨âÓÀÉ¡A >+ ¥H binary ¶Ç¿é¼Ò¦¡¤U¸ü«á¡A½Æ»s¨ìºÏ¤ù¤W¡A¦A¥Î DOS ¶}¾÷¤ù¶}¾÷¡A >+ ±µµÛ¥´Ãþ¦ü¤U±ªº«ü¥O¡G</para> > >- <screen><prompt>...\TOOLS></prompt> <userinput>bootinst.exe boot.bin</userinput></screen> >+ <screen><prompt>></prompt> <userinput>bootinst.exe boot.bin</userinput></screen> > >- <para>and the boot manager will be reinstalled.</para> >+ <para>³o¼Ë¶}¾÷ºÞ²zû(boot manager)´N·|«¸Ë§¹²¦¤F¡C</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> >+ <para>¥Î FreeBSD ¶}¾÷¤ù¶}¾÷¡AµM«á¿ï³æ¨ºÃä¿ï Custom installation(¦Ûq¦w¸Ë)¡A >+ ¦A¿ï Partition¡A±µµÛ¿ï¾Ü§An¸Ë¶}¾÷ºÞ²zû(boot manager)ªºµwºÐ(³q±`¬O²Ä¤@Áû)¡A >+ µM«á·|¥X²{ partition editor ªºµe±¡A³o®É½Ð¤£n°µ¥ô¦ó×§ï¡Aª½±µ«ö W Àx¦s¡A >+ ³o®Éµ{¦¡´N·|°Ý¬O§_n½T©w Write ¡A³Ì«á¥X²{ Boot Manager ¿ï¾Üµe±¡A >+ °O±on¿ï <quote>Boot Manager</quote> ¡A³o¼Ë´N·|«·s±N¶}¾÷ºÞ²zû(boot manager) >+ ¦w¸Ë¨ìµwºÐ¤W¡C²{¦b¡A´N¤j¥\§i¦¨¥i¥HÂ÷¶}¦w¸Ë¿ï³æ¨Ã«¶}¾÷¤F¡C</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> file system >- option) as appropriate and enter the fixit shell. Then >- execute the following command:</para> >+ <para>¥Î FreeBSD ¶}¾÷¤ù©Î¬O¶}¾÷¥úºÐ¶}¾÷¡AµM«á¿ï³æ¨ºÃä¿ï <quote>Fixit</quote> >+ ¡A©Î¬O¥H Fixit ¶}¾÷¤ù©Î¬O¥úºÐ¦w¸Ëªº²Ä¤G¤ù(¿ï¾Ü <quote>live</quote> filesystem >+ ¿ï¶µ)µM«á´N·|¶i¤J fixit shell ¤F¡A±µµÛ¥´¤U¦C«ü¥O¡G</para> > > <screen><prompt>Fixit#</prompt> <userinput>fdisk -B -b /boot/boot0 <replaceable>bootdevice</replaceable></userinput></screen> > >- <para>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> >+ <para>½Ð±N¤W±ªº <replaceable>bootdevice</replaceable> קאּ±z¹ê»Úªº¶}¾÷µwºÐ¥N¸¹ >+ ¤ñ¦p <devicename>ad0</devicename> (²Ä¤@Áû IDE µwºÐ) >+ ¡A©Î¬O<devicename>ad4</devicename> (first IDE disk on >+ auxiliary controller), <devicename>da0</devicename> (²Ä¤@Áû >+ SCSI µwºÐ)µ¥µ¥¡K¡C</para> > </listitem> > </itemizedlist> > </answer> >@@ -1257,59 +1280,55 @@ > > <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> >+ <para>·í¸Ë§¹ FreeBSD ¤§«á«¶}¾÷¡A§Úªº IBM Thinkpad A¨t¦C¡BT¨t¦C©Î X¨t¦Cªºµ§°O«¬¹q¸£´Nw¤F¡A¸Ó«ç»ò¿ì©O¡H</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>³o¨Ç IBM ¾÷¾¹¤Wªº BIOS ¦´Áª©¥»¦³Ó¯äÂÎ(bug)·|§â FreeBSD ¤À³Î°Ï»~»{¬° >+ FAT ®æ¦¡¤À³Î°Ï¡AµM«á·í BIOS ¸ÕµÛ°»´ú FreeBSD ¤À³Î°Ï®É¡A´N·|w¤F¡C</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> >+ <para>®Ú¾Ú IBM ¤è±ªº»¡ªk<footnote><para>¤@«Ê¨Ó¦Û Keith >+ Frechette ªº e-mail <email>kfrechet@us.ibm.com</email>¡C</para></footnote> >+ ¡A¥H¤U«¬¸¹/BIOSª©¥»ªº¾÷ºØ¡A¤w¸g³£¦³×¥¿¡G</para> > >- <informaltable frame="none"> >+ <informaltable frame="none" pgwide="1"> > <tgroup cols="2"> > <thead> > <row> >- <entry>Model</entry> >- <entry>BIOS revision</entry> >+ <entry>«¬¸¹</entry> >+ <entry>BIOS ª©¥»</entry> > </row> > </thead> > > <tbody> > <row> > <entry>T20</entry> >- <entry>IYET49WW or later</entry> >+ <entry>IYET49WW(§t¤§«á)</entry> > </row> > > <row> > <entry>T21</entry> >- <entry>KZET22WW or later</entry> >+ <entry>KZET22WW(§t¤§«á)</entry> > </row> > > <row> > <entry>A20p</entry> >- <entry>IVET62WW or later</entry> >+ <entry>IVET62WW(§t¤§«á)</entry> > </row> > > <row> > <entry>A20m</entry> >- <entry>IWET54WW or later</entry> >+ <entry>IWET54WW(§t¤§«á)</entry> > </row> > > <row> > <entry>A21p</entry> >- <entry>KYET27WW or later</entry> >+ <entry>KYET27WW(§t¤§«á)</entry> > </row> > > <row> > <entry>A21m</entry> >- <entry>KXET24WW or later</entry> >+ <entry>KXET24WW(§t¤§«á)</entry> > </row> > > <row> >@@ -1320,14 +1339,15 @@ > </tgroup> > </informaltable> > >- <para>It has been reported that later IBM BIOS revisions may have >- reintroduced the bug. <ulink >- url="http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=200565+208320+/usr/local/www/db/text/2001/freebsd-mobile/20010429.freebsd-mobile">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>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 >+ <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> >@@ -1350,7 +1370,7 @@ > <step> > <para>Download <filename>boot1</filename> and > <filename>boot2</filename> from <ulink >- url="http://people.FreeBSD.org/~bmah/ThinkPad/">http://people.FreeBSD.org/~bmah/ThinkPad/</ulink>. >+ url="http://people.FreeBSD.org/~bmah/ThinkPad/"></ulink>. > Put these files somewhere you will be able to retrieve them > later.</para> > </step> >@@ -1406,176 +1426,86 @@ > > <qandaentry> > <question id="install-bad-blocks"> >- <para>Can I install on a disk with bad blocks?</para> >- </question> >- >- <answer> >- <para>Prior to 3.0, FreeBSD included a utility known as >- <command>bad144</command>, which automatically remapped bad >- blocks. Because modern IDE drives perform this function >- themselves, <command>bad144</command> has been removed from the >- FreeBSD source tree. If you wish to install FreeBSD 3.0 or >- later, we strongly suggest you purchase a newer disk drive. If >- you do not wish to do this, you must run FreeBSD 2.x.</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="bad144-3x-4x"> >- <para>I have just upgraded from 3.X to 4.X, and my first boot >- failed with <errorname>bad sector table not >- supported</errorname></para> >- </question> >- >- <answer> >- <para>FreeBSD 3.X and earlier supported >- <command>bad144</command>, which automatically remapped >- bad blocks. FreeBSD 4.X and later do not support this, as >- modern IDE drives include this functionality. See <link >- linkend="install-bad-blocks">this question</link> for >- more information.</para> >- >- <para>To fix this after an upgrade, you need to physically >- place the drive in a working system and use >- &man.disklabel.8; as discussed in the following >- questions.</para> >- </answer> >- </qandaentry> >- >- <qandaentry> >- <question id="find-bad144"> >- <para>How do I tell if a drive has <command>bad144</command> >- information on it before I try to upgrade to FreeBSD 4.0 >- and it fails?</para> >+ <para>¦³ÃayªºµwºÐ¥i¥H®³¨Ó¸Ë FreeBSD ¹À¡H</para> > </question> > > <answer> >- <para>Use &man.disklabel.8; for this. <command>disklabel -r >- <replaceable>drive device</replaceable></command> will >- give you the contents of your disk label. Look for a >- <literal>flags</literal> field. If you see >- <literal>flags: badsect</literal>, this drive is using >- bad144. For example, the following drive has >- <command>bad144</command> enabled.:</para> >- >- <screen>&prompt.root; disklabel -r wd0 >-# /dev/rwd0c: >-type: ESDI >-disk: wd0s1 >-label: >-flags: badsect >-bytes/sector: 512 >-sectors/track: 63</screen> >- </answer> >- </qandaentry> >- >- <qandaentry> >- <question id="disable-bad144"> >- <para>How do I remove <command>bad144</command> from my >- pre-4.X system so I can upgrade safely?</para> >- </question> >+ <para>(¦pªG«Ü°í«ùªº¸Ü)¤]¬O¥i¥H¡A¤£¹L³o·QªkÅãµM¤£¤Ó¦n¡C:(</para> > >- <answer> >- <para>Use <command>disklabel -e -rwd0 </command> to edit the >- disklabel in place. Just remove the word >- <literal>badsect</literal> from the flags field, save, and >- exit. The bad144 file will still take up some space on >- your drive, but the disk itself will be usable.</para> >+ <para>¦pªG¦b¤@¯ë¸û·sªº IDE µwºÐ¤W¬Ý¨ì¦³Ãay¡A«Ü¦³¥i¯à¥Nªí¡G³oÁûµwºÐ§Y±N±¾ÂI¤F¡C >+ (¦]¬°¥Ø«e©Ò¦³¸û·sªº IDE µwºÐ¡A¤º³¡³£¦³¦Û°Ê remapping Ãayªº¯à¤O¡C >+ ¦pªG¬Ý¨ì¦³Ãay¡A«hªí¥Ü¥¦¤º³¡¦Û°Ê remapping ¥\¯à¥¢®Ä¡AµLªk³B²zÃay¡A >+ ¤]´N¬O»¡³oÁûµwºÐ¤w¸g¬OÄY«·lÃaµ{«×¤F¡C)§ÚÌ«ØÄ³¶RÁû·sµwºÐ¤ñ¸û°®¯Ü¨Çò¡C</para> > >- <para>We still recommend you purchase a new disk if you have >- a large number of bad blocks.</para> >+ <para>¦pªG¬O SCSI µwºÐ¦³Ãayªº¸Ü¡A½Ð¸ÕµÛ°Ñ¦Ò³oÓ >+ <link linkend="awre">¸Ñªk</link>¡C</para> > </answer> > </qandaentry> > > <qandaentry> > <question id="boot-floppy-strangeness"> >- <para>Strange things happen when I boot the install floppy! >- What is happening?</para> >+ <para>¥Î¦w¸ËºÏ¤ù¶}¾÷®É¡A«o¦³¨Ç©Ç²{¶Hµo¥Í¡I³o¬O¤°»ò±¡ªp©O¡H</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> >+ <para>Y¬Ý¨ì¤@¨Ç©Ç²§²{¶H¡A¹³¬O¶}¾÷¤ù¶}¾÷¶}¨ì¤@¥b´N·í¤F¡AºÏºÐ¾÷§¹¥þ¨S¥ô¦ó°Ê§@¡B >+ ©Î¬O¤£Â_¤ÏÂЫ¶}¾÷¡A½Ð¥ýÀˬd¥H¤U´XÓ½u¯Á¡G</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> >+ <para>½Ð½T©w¬O§_¬°¥þ·s¡B¨S¦³ºÏy¿ù»~ªººÏ¤ù¡H >+ (³Ì¦n¨Ï¥Î·s¶Rªº¡A¦Ó«DÂø»x¡B®Ñ¥»ªþÃØªº¡A¬Æ¦ÜÁÙÂæb§É©³¤U¤T¦~¤F...)</para> > </listitem> > > <listitem> >- <para>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> >+ <para>½Ð½T©w¬O§_¦³¥Î binary(©Îimage)¶Ç¿é¼Ò¦¡¨Ó¤U¸ü image ÀÉ¡H >+ (¤£¥Îı±o¤£¦n·N«ä¡A§Y¨Ï¬O§Ṳ́]´¿·N¥~¥H ASCII ¶Ç¿é¼Ò¦¡¨Ó¤U¸ü binary ÀɮסI)</para> > </listitem> > > <listitem> >- <para>If you are using Windows95 or Win98 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> >+ <para>Y§A¬O &windows; 95/98/ME/NT/2000/XP/2003 ¨Ó¤U¸ü¡B»s§@¶}¾÷ºÏ¤ùªº¸Ü¡A >+ ½Ð½T©w¬O§_¦³¦b DOS ¼Ò¦¡¨Ï¥Î <command>fdimage</command> ©Î >+ <command>rawrite</command> ³o¨âÓ¤u¨ãµ{¦¡¡HèÁ¿ªº³o¨Ç§@·~¨t²Î¡A >+ ³£·|¼vÅTµ{¦¡¥hª½±µ¼g¤JµwÅé¡A¹³¬O»s§@¶}¾÷¤ù¤§Ãþªº°Ê§@¡C >+ ¦³®ÉÔ¡A¦b GUI ¤¶±¤Wªº DOS shell ¤]¥i¯à·|µo¥Í³o¼Ëªº°ÝÃD¡C >+ </para> > </listitem> > </orderedlist> > >- <para>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> >+ <para>¦¹¥~¡Aª½±µ³z¹L &netscape; ÂsÄý¾¹¤U¸ü image Àɪº¸Ü¡A¤]¦³Ãþ¦ü²{¶H¡C >+ ©Ò¥H¡A¦pªG¥i¥Hªº¸Ü¡A½Ð§ï¥Î¨ä¥L¥i¥H½Õ¾ã³]©wªº FTP clientºÝµ{¦¡¨Ó¶i¦æ¤U¸ü¡C >+ (·íµM¡An°O±o½Õ binary ¶Ç¿é¼Ò¦¡)</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> >+ <para>¥Î¥úºÐ¶}¾÷¤ù¨Ó¦w¸Ë¡A¦ý¥úºÐ¶}¾÷«á¡A¦w¸Ëµ{¦¡»¡§ä¤£¨ì¥úºÐ...³o¬O«ç»ò¤F¡H</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> >+ <para>³q±`°ÝÃD¦b©ó¥úºÐ¾÷³]©w¿ù»~¡C¥Ø«e«Ü¦h¹q¸£ªº¥X¼t¼Ð·Ç°t³Æ³£¦³¥úºÐ¾÷¡A¨Ã¥B >+ ·|¹w¥ý³]©w¬° IDE ³q¹D¤W± Secondary ªº Slave ³]³Æ¡A¦Ó Secondary ¤W±ªº >+ «o¨S¦³ Master ³]³Æ¡C¥H ATAPI ªº³W®æ¦Ó¨¥¡A³o¬O¿ù»~ªº³]©w¡AµM¦Ó &windows; ªº§@ªk >+ ¬O¤£²z·|³o¨Ç³W®æ¤Wªº³]©w°ÝÃD¡A¦Ó¥B¶}¾÷®É BIOS °»´ú¤]·|²¤¹L³oÂI¡C >+ ³o¤]´N¬O¬°¤°»ò BIOS ¥i¥H¬Ý¨ì¥úºÐ¡A¨Ã¥B¥i¥Î¥úºÐ¶}¾÷¡A¦ý FreeBSD >+ µLªk¥¿±`§ì¨ì¥úºÐ¥H¶¶§Q¶i¦æ¦w¸Ë¡C</para> >+ >+ <para>¸Ñªk¡G«·s³]©w¨t²Î¡AÅý¥úºÐ¦¨¬°¥¦©Ò³s±µ¨º±ø IDE ³q¹Dªº Master¡A >+ ©ÎªÌ¥u¦³¤@±ø IDE ³q¹Dªº¸Ü¡A¨º´NÅý¥úºÐ¾÷¦¨¬° Slave >+ ¡A·íµM¸Ó IDE ³q¹D¤W¦Ü¤Ön¦³ Master ³]³Æ¡C</para> > </answer> > </qandaentry> > > <qandaentry> > <question id="install-PLIP"> >- <para>Can I install on my laptop over PLIP (Parallel Line >- IP)?</para> >+ <para>§Ú¥i¥H¥Î PLIP(Parallel Line IP)¤è¦¡¨Ó¦w¸Ë FreeBSD ¨ìµ§°O«¬¹q¸£¤W¶Ü¡H</para> > </question> > > <answer> >- <para>Yes. Use a standard Laplink cable. If necessary, you >- can check out the <ulink url="../handbook/plip.html">PLIP >- section of the Handbook</ulink> for details on parallel >- port networking.</para> >- >- <para>If you are running FreeBSD 3.X or earlier, also look at >- the <ulink >- url="http://www.FreeBSD.org/docs.html#PAO">Mobile >- Computing page</ulink>.</para> >+ <para>¥i¥H¡A¥Î¤@±ø´¶³qªº Laplink ½u´N¥i¥HÅo¡CY¦³³o¤è±»Ý¨Dªº¸Ü¡A½Ð°Ñ¾\¡m FreeBSD ¨Ï¥Î¤â¥U¡n¤¤ªº >+ <ulink url="&url.books.handbook;/network-plip.html">PLIP >+ ³¹¸`</ulink> ªº²Ó³¡³]©w</para> > </answer> > </qandaentry> > >@@ -1604,8 +1534,7 @@ > 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> >+ references.</para> > > <para>All that matters is the <emphasis>logical</emphasis> > geometry. This is the answer that the BIOS gets when it >@@ -1629,9 +1558,9 @@ > > <para>If it <emphasis>is</emphasis> turned on (it is often > supplied this way to get around certain limitations in >- MSDOS) and the disk capacity is more than 1GB, use M >+ &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 'M' is the disk capacity in MB >+ 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> >@@ -1662,8 +1591,7 @@ > </question> > > <answer> >- <para>Yes. You must make sure that your root partition is below >- 1024 >+ <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> > >@@ -1701,7 +1629,7 @@ > > <qandaentry> > <question id="missing-os"> >- <para>When I boot FreeBSD I get <errorname>Missing Operating >+ <para>When I boot FreeBSD for the first time after install I get <errorname>Missing Operating > System</errorname>. What is happening?</para> > </question> > >@@ -1745,12 +1673,12 @@ > 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. >- (Because of the kernel-source restriction, we recommend that >+ 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> >+ 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 >@@ -1770,15 +1698,17 @@ > <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 a much friendlier kernel >- configuration tool. When at the FreeBSD boot prompt (boot:), >+ benefited from the introduction of much friendlier kernel >+ configuration methods. In 4.X and earlier, when at the FreeBSD boot prompt (boot:), > use the <option>-c</option> flag and you will be dropped into a > visual configuration screen which allows you to configure the >- kernel's settings for most common ISA cards.</para> >+ kernel's settings for most common ISA cards. In &os; 5.X and later >+ this has been replaced by much more flexible "hints" which >+ can be set from the loader prompt.</para> > >- <para>It is still recommended that you eventually build a new >+ <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 a strict requirement for most >+ bit of RAM, but it is no longer necessary for most > systems.</para> > > </answer> >@@ -1786,28 +1716,31 @@ > > <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> >+ <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 >+ <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> >+ 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> > >@@ -1819,7 +1752,7 @@ > > <answer> > >- <para>If you have a IDE Zip or Jaz drive installed, remove it >+ <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> >@@ -1833,79 +1766,57 @@ > </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 >- wd1 (the second BIOS disk) while the kernel assigns the first >- disk on the secondary controller device wd2. After the device >- probing, the kernel tries to mount what the boot blocks think >- is the boot disk, wd1, while it is really wd2, and >+ <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>For FreeBSD 3.3 and later, reboot the system and hit >- <literal>Enter</literal> at the <literal>Booting kernel >- in 10 seconds; hit [Enter] to interrupt</literal> prompt. >- This will drop you into the boot loader.</para> >+ <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>" >+ 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 (ie 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 >+ 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 (ie 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>If using FreeBSD 3.2 or earlier, at the Boot: prompt, >- enter <literal>1:wd(2,a)kernel</literal> and press Enter. >- If the system starts, then run the command >- <command>echo "1:wd(2,a)kernel" > /boot.config</command> >- to make it the default boot string.</para> >- </listitem> >- >- <listitem> >- <para>Move the FreeBSD disk onto the primary IDE controller, >- so the hard disks are consecutive.</para> >- </listitem> >- >- <listitem> >- <para><ulink URL="../handbook/kernelconfig.html">Rebuild >- your kernel,</ulink> modify the wd configuration lines to >- read:</para> >- >- <programlisting>controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr >-disk wd0 at wdc0 drive 0 >-# disk wd1 at wdc0 drive 1 # comment out this line >- >-controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr >-disk wd1 at wdc1 drive 0 # change from wd2 to wd1 >-disk wd2 at wdc1 drive 1 # change from wd3 to wd2</programlisting> >- >- <para>Install the new kernel. If you moved your disks and >- wish to restore the previous configuration, replace the >- disks in the desired configuration and reboot. Your >- system should boot successfully.</para> >+ <para>Move the FreeBSD disk onto the primary IDE >+ controller, so the hard disks are >+ consecutive.</para> > </listitem> > </orderedlist> > </answer> >@@ -1917,14 +1828,19 @@ > </question> > > <answer> >- <para>For memory, the limit is 4 gigabytes. This configuration >- has been tested, see <ulink >- URL="ftp://ftp.cdrom.com/archive-info/configuration">wcarchive's >- configuration</ulink> for more details. If you plan to install >- this much memory into a machine, you need to be careful. You will >- probably want to use ECC memory and to reduce capacitive >- loading use 9 chip memory modules versus 18 chip memory >- modules.</para> >+ <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> > >@@ -1941,20 +1857,16 @@ > exist).</para> > > <para>The maximum size of a single ffs file is approximately 1G >- blocks (4TB) if the block size is 4K.</para> >+ blocks, or 4TB with a block size of 4K.</para> > > <table> > <title>Maximum file sizes</title> > >- <tgroup cols="5"> >+ <tgroup cols="3"> > <thead> > <row> > <entry>fs block size</entry> > >- <entry>2.2.7-stable</entry> >- >- <entry>3.0-current</entry> >- > <entry>works</entry> > > <entry>should work</entry> >@@ -1967,10 +1879,6 @@ > > <entry>4T-1</entry> > >- <entry>4T-1</entry> >- >- <entry>4T-1</entry> >- > <entry>>4T</entry> > </row> > >@@ -1979,10 +1887,6 @@ > > <entry>>32G</entry> > >- <entry>8T-1</entry> >- >- <entry>>32G</entry> >- > <entry>32T-1</entry> > </row> > >@@ -1991,10 +1895,6 @@ > > <entry>>128G</entry> > >- <entry>16T-1</entry> >- >- <entry>>128G</entry> >- > <entry>32T-1</entry> > </row> > >@@ -2003,10 +1903,6 @@ > > <entry>>512G</entry> > >- <entry>32T-1</entry> >- >- <entry>>512G</entry> >- > <entry>64T-1</entry> > </row> > >@@ -2015,10 +1911,6 @@ > > <entry>>2048G</entry> > >- <entry>64T-1</entry> >- >- <entry>>2048G</entry> >- > <entry>128T-1</entry> > </row> > </tbody> >@@ -2035,14 +1927,10 @@ > 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, except under >- -STABLE triple indirect blocks are unreachable, so the limit is >- the maximum fs block number that can be represented using >- double indirect blocks (approx. (blocksize/4)^2 + >- (blocksize/4)), and under -CURRENT exceeding this limit may >- cause problems. Using the correct limit of 2G-1 blocks does >- cause problems.</para> >+ 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> >@@ -2055,44 +1943,14 @@ > </question> > > <answer> >- <para>You can boot by specifying the kernel directly at the second >- stage, pressing any key when the | shows up before loader is >- started. More specifically, you have upgraded the source for >- your kernel, and installed a new kernel builtin from them >- <emphasis>without making world</emphasis>. This is not >- supported. Make world.</para> >- </answer> >- </qandaentry> >- >- <qandaentry> >- <question id="upgrade-3x-4x"> >- <para>How do I upgrade from 3.X -> 4.X?</para> >- </question> >- >- <answer> >- <para>We <emphasis>strongly</emphasis> recommend that you use >- binary snapshots to do this. 4-STABLE snapshots are available at >- <ulink >- URL="ftp://releng4.FreeBSD.org/">ftp://releng4.FreeBSD.org/</ulink>.</para> >- >- <para>Because of the many changes between 3.X and 4-STABLE, >- a direct upgrade from source will probably fail. A source >- upgrade can be done, but only in stages. First, upgrade >- to the latest 3-STABLE (<literal>RELENG_3</literal>). >- Then upgrade to 4.1.1-RELEASE >- (<literal>RELENG_4_1_1_RELEASE</literal>). Finally, >- upgrade to 4-STABLE (<literal>RELENG_4</literal>).</para> >- >- <para>If you wish to upgrade using source, please see the <ulink >- URL="../handbook/cutting-edge.html">FreeBSD >- Handbook</ulink> for more information.</para> >- >- <caution> >- <para>Upgrading via source is never recommended for new >- users, and upgrading from 3.X to 4.X is even less so; make sure >- you have read the instructions carefully before attempting to >- upgrade via source.</para> >- </caution> >+ <para>Because your world and kernel are out of synch. 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> > >@@ -2106,9 +1964,9 @@ > options that attempts to achieve the desired ratio of security > to convenience by enabling and disabling certain programs and > other settings. For full details, see the <ulink >- url="../handbook/install-post.html#SECURITYPROFILE">Security >+ url="&url.books.handbook;/install-post.html#SECURITYPROFILE">Security > Profile</ulink> section of the Handbook's <ulink >- url="../handbook/install-post.html">post-install >+ url="&url.books.handbook;/install-post.html">post-install > chapter</ulink>.</para> > </answer> > </qandaentry> >@@ -2119,31 +1977,10 @@ > id="hardware"> > <title>Hardware compatibility</title> > >- <qandaset> >- <qandaentry> >- <question id="architectures"> >- <para>Does FreeBSD support architectures other than the >- x86?</para> >- </question> >- >- <answer> >- >- <para>Yes. FreeBSD currently runs on both Intel x86 and >- DEC (now Compaq) Alpha architectures. Interest has also >- been expressed in a port of FreeBSD to the SPARC architecture, >- join the &a.sparc; if you are interested in joining that project. >- Most recent additions to the list of upcoming platforms are >- IA-64 and PowerPC, join the &a.ia64; and/or the &a.ppc; for more >- information. 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> >+ <sect1 id="compatibility-general"> >+ <title>General</title> > >+ <qandaset> > <qandaentry> > <question id="which-hardware-to-get"> > <para>I want to get a piece of hardware for my FreeBSD >@@ -2154,10 +1991,12 @@ > <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 >- <ulink URL="&rel.current.hardware;">Hardware Notes</ulink> >+ 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"> >+ <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 >@@ -2171,6 +2010,66 @@ > </answer> > </qandaentry> > >+ </qandaset> >+ </sect1> >+ >+ <sect1 id="compatibility-processors"> >+ <title>Architectures and processors</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> >+ >+ <para>In &os; 4.X, SMP is not enabled in the default kernel, >+ so you must recompile your kernel to enable SMP. Take a >+ look at <filename>/sys/i386/conf/LINT</filename> to learn >+ which options to put in your kernel config file.</para> >+ </answer> >+ </qandaentry> >+ </qandaset> >+ </sect1> >+ >+ <sect1 id="compatibility-drives"> >+ <title>Hard drives, tape drives, and CD and DVD drives</title> >+ >+ <qandaset> >+ > <qandaentry> > <question id="supported-hard-drives"> > <para>What kind of hard drives does FreeBSD support?</para> >@@ -2192,8 +2091,44 @@ > </question> > > <answer> >- <para>See the complete list in the current <ulink >- URL="&rel.current.hardware;">Hardware Notes</ulink>.</para> >+ <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> > >@@ -2235,8 +2170,9 @@ > <para>All non-SCSI cards are known to be extremely slow compared > to SCSI drives, and some ATAPI CDROMs may not work.</para> > >- <para>As of 2.2 the FreeBSD CDROM from the FreeBSD Mall supports >- booting directly from the CD.</para> >+ <para>The official FreeBSD CDROM ISO, and CDROMs from Daemon >+ News and FreeBSD Mall, support booting directly from the >+ CD.</para> > </answer> > </qandaentry> > >@@ -2247,9 +2183,7 @@ > > <answer> > <para>FreeBSD supports any ATAPI-compatible IDE CD-R or CD-RW >- drive. For FreeBSD versions 4.0 and later, see the man page for >- &man.burncd.8;. For earlier FreeBSD versions, see the examples >- in <filename>/usr/share/examples/atapi</filename>.</para> >+ 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 >@@ -2261,80 +2195,72 @@ > > <qandaentry> > <question id="zip-support"> >- <para>Does FreeBSD support ZIP drives?</para> >+ <para>Does FreeBSD support &iomegazip; drives?</para> > </question> > > <answer> >- <para>FreeBSD supports the SCSI ZIP drive out of the box, of >- course. The ZIP drive 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>ATAPI (IDE) Zip drives are supported in FreeBSD 2.2.6 and >- later releases.</para> >- >- <para>FreeBSD has contained support for Parallel Port Zip Drives >- since version 3.0. If you are using a sufficiently up to date >- version, then you should check that your kernel contains the >- <devicename>scbus0</devicename>, <devicename>da0</devicename>, >+ <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 >+ 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="jaz">the FAQ on removable >- drives</link> later in this chapter, and <link linkend="disklabel">the note on >- <quote>formatting</quote></link>in the Administration chapter.</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 >+ <para>Does FreeBSD support &jaz;, EZ and other removable > drives?</para> > </question> > > <answer> >- <para>Apart from the IDE version of the EZ drive, these are all >- SCSI devices, so they should all look like SCSI disks to >- FreeBSD, and the IDE EZ should look like an IDE drive.</para> >- >- <para><anchor id="jaz">I am not sure how well FreeBSD supports >- changing the media out while running. You will of course need >- to dismount the drive before swapping media, and make sure that >- any external units are powered on when you boot the system so >- FreeBSD can see them.</para> >+ <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>See <link linkend="disklabel">this note on >- <quote>formatting</quote></link>.</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> > >- <qandaentry> >- <question id="multiport-serial-support"> >- <para>Which multi-port serial cards are supported by >- FreeBSD?</para> >- </question> >+ </qandaset> > >- <answer> >- <para>There is a list of these in the <ulink >- URL="../handbook/install.html#INSTALL-MISC">Miscellaneous >- devices</ulink> section of the handbook.</para> >+ </sect1> > >- <para>Some unnamed clone cards have also been known to work, >- especially those that claim to be AST compatible.</para> >+ <sect1 id="compatibility-kbd-mice"> >+ <title>Keyboards and mice</title> > >- <para>Check the &man.sio.4; >- man page to get more information on configuring such cards.</para> >- </answer> >- </qandaentry> >+ <qandaset> > > <qandaentry> > <question id="usbkbd"> >@@ -2342,119 +2268,69 @@ > </question> > > <answer> >- <para>USB device support was added to FreeBSD 3.1. However, it >- is still in preliminary state and may not always work as of >- version 3.2. If you want to experiment with the USB keyboard >- support, follow the procedure described below.</para> >+ <para>FreeBSD supports USB keyboards >+ out-of-the-box. Enable USB support in >+ <filename>/etc/rc.conf</filename>.</para> > >- <procedure> >- <step> >- <para>Use FreeBSD 3.2 or later.</para> >- </step> >+ <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> > >- <step> >- <para>Add the following lines to your kernel configuration >- file, and rebuild the kernel.</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> > >- <programlisting>device uhci >-device ohci >-device usb >-device ukbd >-options KBD_INSTALL_CDEV</programlisting> >- >- <para>In versions of FreeBSD before 4.0, use this >- instead:</para> >- >- <programlisting>controller uhci0 >-controller ohci0 >-controller usb0 >-controller ukbd0 >-options KBD_INSTALL_CDEV</programlisting> >- </step> >+ <screen>&prompt.root; <userinput>kbdcontrol -k /dev/kbd1 < /dev/ttyv0 > /dev/null</userinput></screen> > >- <step> >- <para>Go to the <filename>/dev</filename> directory and create >- device nodes as follows:</para> >+ <para>Note that if the USB keyboard is the only keyboard, it >+ is accessed as <devicename>/dev/kbd0</devicename>, thus, >+ the command should look like:</para> > >- <screen>&prompt.root; <userinput>cd /dev</userinput> >-&prompt.root; <userinput>./MAKEDEV kbd0 kbd1</userinput></screen> >+ <screen>&prompt.root; <userinput>kbdcontrol -k /dev/kbd0 < /dev/ttyv0 > /dev/null</userinput></screen> > >- </step> >- >- <step> >- <para>Edit <filename>/etc/rc.conf</filename> and add the >- following lines:</para> >- >- <programlisting>usbd_enable="YES" >-usbd_flags=""</programlisting> >- >- </step> >- </procedure> >+ <para><filename>/etc/rc.i386</filename> is a good place to >+ add the above command.</para> > >- <para>After the system is rebooted, 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>Once this is done, the USB keyboard should work in the >+ X environment as well without any special settings.</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 < /dev/ttyv0 > /dev/null</userinput></screen> >+ <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>Note that if the USB keyboard is the only keyboard, it is >- accessed as <devicename>/dev/kbd0</devicename>, thus, the command >- should look like:</para> >- >- <screen>&prompt.root; <userinput>kbdcontrol -k /dev/kbd0 < /dev/ttyv0 > /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. It is a good idea to connect the keyboard >- before you start the system and leave it connected until the >- system is shutdown to avoid troubles.</para> >- >- <para>See the &man.ukbd.4; man page for more information.</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> >+ <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 manufactures as Microsoft, Logitech and ATI. The bus >- device driver is compiled in the GENERIC kernel by default in >- FreeBSD versions 2.X, but not included in version 3.0 or later. >- If you are building a custom kernel with the bus mouse driver, >- make sure to add the following line to the kernel config >- file</para> >- >- <para>In FreeBSD 3.0 or before, add:</para> >- >- <programlisting>device mse0 at isa? port 0x23c tty irq5 vector mseintr</programlisting> >- >- <para>In FreeBSD 3.X, the line should be:</para> >- >- <programlisting>device mse0 at isa? port 0x23c tty irq5</programlisting> >- >- <para>And in FreeBSD 4.X and later, the line should read:</para> >+ <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 comes 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; man page for more information.</para> >+ <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> > >@@ -2465,218 +2341,96 @@ > </question> > > <answer> >- >- <para>If you are running a post-2.2.5 version of FreeBSD, the >- necessary driver, <devicename>psm</devicename>, is included and >- enabled in the kernel. The kernel should detect your PS/2 mouse >- at boot time.</para> >- >- <para>If you are running a previous but relatively recent version >- of FreeBSD (2.1.x or better) then you can simply enable it in >- the kernel configuration menu at installation time, otherwise >- later with <option>-c</option> at the <command>boot:</command> >- prompt. It is disabled by default, so you will need to enable >- it explicitly.</para> >- >- <para>If you are running an older version of FreeBSD then you will >- have to add the following lines to your kernel configuration >- file and compile a new kernel.</para> >- >- <para>In FreeBSD 3.0 or earlier, the line should be:</para> >- >- <programlisting>device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr</programlisting> >- >- <para>In FreeBSD 3.1 or later, the line should be:</para> >- >- <programlisting>device psm0 at isa? tty irq 12</programlisting> >- >- <para>In FreeBSD 4.0 or later, the line should be:</para> >+ <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>See the <ulink >- URL="../handbook/kernelconfig.html">Handbook entry on >- configuring the kernel</ulink> if you have no experience with >- building kernels.</para> >- >- <para>Once you have a kernel detecting >- <devicename>psm0</devicename> correctly at boot time, make sure >- that an entry for <devicename>psm0</devicename> exists in >- <filename>/dev</filename>. You can do this by typing:</para> >+ <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> >- </answer> >+ >+ <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 make use of a mouse in any way outside >- the X Window system?</para> >+ <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, syscons, you >- can use a mouse pointer in text consoles to cut & paste >- text. Run the mouse daemon, moused, and turn on the mouse >- pointer in the virtual console:</para> >+ <para>If you are using the default console driver, >+ &man.syscons.4;, you can use a mouse pointer in text >+ consoles to cut & 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. See the &man.moused.8; man page for supported >+ <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>You may wish to run the mouse daemon automatically when the >- system starts. In version 2.2.1, set the following variables in >- <filename>/etc/sysconfig</filename>.</para> >- >- <programlisting>mousedtype="yyyy" >-mousedport="xxxx" >-mousedflags=""</programlisting> >- >- <para>In versions 2.2.2 to 3.0, set the following variables in >- <filename>/etc/rc.conf</filename>.</para> >- >- <programlisting>moused_type="yyyy" >-moused_port="xxxx" >-moused_flags=""</programlisting> >- >- <para>In 3.1 and later, assuming you have a PS/2 mouse, all you >- need to is add <literal>moused_enable="YES"</literal> to >- <filename>/etc/rc.conf</filename>.</para> >- >- <para>In addition, if you would like to be able to use the mouse >- daemon on all virtual terminals instead of just console at >- boot-time, add the following to >- <filename>/etc/rc.conf</filename>.</para> >- >- <programlisting>allscreens_flags="-m on"</programlisting> >- >- <para>Staring from FreeBSD 2.2.6, the mouse daemon is capable of >- determining the correct protocol type automatically unless the >- mouse is a relatively old serial mouse model. Specify >- <literal>auto</literal> the protocol to invoke automatic >- detection.</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 >- needs to be coordinated between the mouse daemon and other >- programs such as the X Window. Refer to <link >- linkend="x-and-moused">another section</link> on this >- issue.</para> >+ 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 mouse in the text >+ <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 >- <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) or the button 3 >- (right button) to paste it at the text cursor.</para> >- >- <para>In versions 2.2.6 and later, pressing the button 2 will >- paste the text. Pressing the button 3 will >- <quote>extend</quote> the selected region of text. If your >- mouse does not have the middle button, you may wish to emulate >- it or remap buttons using moused options. See the >- &man.moused.8; man page for details.</para> >- </answer> >- </qandaentry> >- >- <qandaentry> >- <question id="usbmouse"> >- <para>Does FreeBSD support any USB mice?</para> >- </question> >- >- <answer> >- >- <para>Preliminary USB device support was added to FreeBSD >- 3.1. It did not always work through early versions of >- 3.X. As of FreeBSD 4.0, USB devices should work out of >- the box. If you want to experiment with the USB mouse >- support under FreeBSD 3.X, follow the procedure described >- below.</para> >- >- <procedure> >- <step> >- <para>Use FreeBSD 3.2 or later.</para> >- </step> >- >- <step> >- <para>Add the following lines to your kernel configuration >- file, and rebuild the kernel.</para> >- >- <programlisting>device uhci >-device ohci >-device usb >-device ums</programlisting> >- >- <para>In versions of FreeBSD before 4.0, use this >- instead:</para> >- >- <programlisting>controller uhci0 >-controller ohci0 >-controller usb0 >-device ums0</programlisting> >- </step> >- >- <step> >- <para>Go to the <filename>/dev</filename> directory and >- create a device node as follows:</para> >- >- <screen>&prompt.root; <userinput>cd /dev</userinput> >-&prompt.root; <userinput>./MAKEDEV ums0</userinput></screen> >- </step> >- >- <step> >- <para>Edit <filename>/etc/rc.conf</filename> and add the >- following lines:</para> >- >- <programlisting>moused_enable="YES" >-moused_type="auto" >-moused_port="/dev/ums0" >-moused_flags="" >-usbd_enable="YES" >-usbd_flags=""</programlisting> >- >- <para>See the <link linkend="moused">previous section</link> >- for more detailed discussion on moused.</para> >- </step> >- >- <step> >- <para>In order to use the USB mouse in the X session, edit >- <filename>XF86Config</filename>. If you are using XFree86 >- 3.3.2 or later, be sure to have the following lines in the >- <emphasis>Pointer</emphasis> section:</para> >- >- <programlisting>Device "/dev/sysmouse" >-Protocol "Auto"</programlisting> >- >- <para>If you are using earlier versions of XFree86, be sure to >- have the following lines in the <emphasis>Pointer</emphasis> >- section:</para> >- >- <programlisting>Device "/dev/sysmouse" >-Protocol "SysMouse"</programlisting> >- </step> >- </procedure> >- >- <para>Refer to <link linkend="x-and-moused">another section</link> >- on the mouse support in the X environment.</para> >- >- <para>Hot-plugging and unplugging of the USB mouse may not work >- quite right yet. It is a good idea connect the mouse before you >- start the system and leave it connected until the system is >- shutdown to avoid trouble.</para> >+ <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> > >@@ -2700,149 +2454,24 @@ > </qandaentry> > > <qandaentry> >- <question id="psmerr"> >- <para>Why does my wheel-equipped PS/2 mouse cause my mouse cursor >- to jump around the screen?</para> >- </question> >- >- <answer> >- <para>The PS/2 mouse driver psm in FreeBSD versions 3.2 or >- earlier has difficulty with some wheel mice, including Logitech >- model M-S48 and its OEM siblings. Apply the following patch to >- <filename>/sys/i386/isa/psm.c</filename> and rebuild the >- kernel.</para> >- >- <programlisting>Index: psm.c >-=================================================================== >-RCS file: /src/CVS/src/sys/i386/isa/Attic/psm.c,v >-retrieving revision 1.60.2.1 >-retrieving revision 1.60.2.2 >-diff -u -r1.60.2.1 -r1.60.2.2 >---- psm.c 1999/06/03 12:41:13 1.60.2.1 >-+++ psm.c 1999/07/12 13:40:52 1.60.2.2 >-@@ -959,14 +959,28 @@ >- sc->mode.packetsize = vendortype[i].packetsize; >- >- /* set mouse parameters */ >-+#if 0 >-+ /* >-+ * A version of Logitech FirstMouse+ won't report wheel movement, >-+ * if SET_DEFAULTS is sent... Don't use this command. >-+ * This fix was found by Takashi Nishida. >-+ */ >- i = send_aux_command(sc->kbdc, PSMC_SET_DEFAULTS); >- if (verbose >= 2) >- printf("psm%d: SET_DEFAULTS return code:%04x\n", unit, i); >-+#endif >- if (sc->config & PSM_CONFIG_RESOLUTION) { >- sc->mode.resolution >- = set_mouse_resolution(sc->kbdc, >-- (sc->config & PSM_CONFIG_RESOLUTION) - 1); >-+ (sc->config & PSM_CONFIG_RESOLUTION) - 1); >-+ } else if (sc->mode.resolution >= 0) { >-+ sc->mode.resolution >-+ = set_mouse_resolution(sc->kbdc, sc->dflt_mode.resolution); >-+ } >-+ if (sc->mode.rate > 0) { >-+ sc->mode.rate = set_mouse_sampling_rate(sc->kbdc, sc->dflt_mode.rate); >- } >-+ set_mouse_scaling(sc->kbdc, 1); >- >- /* request a data packet and extract sync. bits */ >- if (get_mouse_status(sc->kbdc, stat, 1, 3) < 3) {</programlisting> >- >- <para>Versions later than 3.2 should be all right.</para> >- </answer> >- </qandaentry> >- >- <qandaentry> > <question id="laptop-mouse-trackball"> >- <para>How do I use the mouse/trackball/touchpad on my >- laptop?</para> >+ <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>. Also check out the <ulink >- url="http://www.FreeBSD.org/docs.html#PAO">Mobile >- Computing page</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 2.2 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; >- man 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> >+ the previous question</link>.</para> > </answer> > </qandaentry> > >- <qandaentry> >- <question id="sound-card-support"> >- <para>Which sound cards are supported by FreeBSD?</para> >- </question> >- >- <answer> >- <para>FreeBSD supports the SoundBlaster, SoundBlaster Pro, >- SoundBlaster 16, Pro Audio Spectrum 16, AdLib and Gravis >- UltraSound sound cards. There is also limited support for >- MPU-401 and compatible MIDI cards. Cards conforming to the >- Microsoft Sound System specification are also supported through >- the pcm driver.</para> >+ </qandaset> > >- <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 es1370 with pcm driver?</para> >- </question> >+ </sect1> > >- <answer> >- <para>You can run the following command every time the machine >- booted up:</para> >+ <sect1 id="compatibility-networking"> >+ <title>Networking and serial devices</title> > >- <screen>&prompt.root; <userinput>mixer pcm 100 vol 100 cd 100</userinput></screen> >- </answer> >- </qandaentry> >+ <qandaset> > > <qandaentry> > <question id="network-cards"> >@@ -2850,106 +2479,13 @@ > </question> > > <answer> >- <para>See the <ulink >- URL="../handbook/install.html#INSTALL-NICS"> >- Ethernet cards</ulink> section of the handbook for a more >+ <para>See the Hardware Notes supplied with each release of >+ FreeBSD for a more > complete list.</para> > </answer> > </qandaentry> > > <qandaentry> >- <question id="no-math-coprocessor"> >- <para>I do not have a math co-processor - is that bad?</para> >- </question> >- >- <answer> >- <note> >- <para>This will only affect 386/486SX/486SLC owners - other >- machines will have one built into the CPU.</para> >- </note> >- >- <para>In general this will not cause any problems, but there are >- circumstances where you will take a hit, either in performance >- or accuracy of the math emulation code (see the section <link >- linkend="emul">on FP emulation</link>). In particular, drawing >- arcs in X will be VERY slow. It is highly recommended that you >- buy a math co-processor; it is well worth it.</para> >- >- <note> >- <para>Some math co-processors are better than others. It >- pains us to say it, but nobody ever got fired for buying >- Intel. Unless you are sure it works with FreeBSD, beware of >- clones.</para> >- </note> >- </answer> >- </qandaentry> >- >- <qandaentry> >- <question id="other-device-support"> >- <para>What other devices does FreeBSD support?</para> >- </question> >- >- <answer> >- <para>See the <ulink >- URL="../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 supports <acronym>APM</acronym> on certain machines. Please look in >- the <filename>LINT</filename> kernel config file, searching for >- the >- <acronym>APM</acronym> >- keyword. Further information can be found in &man.apm.4;.</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. More information >- can be found at <ulink >- URL="http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html#micron"> >- http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html#micron</ulink></para> >- </answer> >- </qandaentry> >- >- <qandaentry> >- <question id="newer-adaptec-support"> >- <para>Why does FreeBSD not recognize my Adaptec SCSI >- controller card?</para> >- </question> >- >- <answer> >- <para>The newer AIC789x series Adaptec chips are supported under >- the CAM SCSI framework which made its debut in 3.0. Patches >- against 2.2-STABLE are in <ulink >- URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/development/cam/"> >- ftp://ftp.FreeBSD.org/pub/FreeBSD/development/cam/</ulink>. >- A CAM-enhanced boot floppy is available at <ulink >- URL="http://people.FreeBSD.org/~abial/cam-boot/"> >- http://people.FreeBSD.org/~abial/cam-boot/</ulink>. >- In both cases read the README before beginning.</para> >- </answer> >- </qandaentry> >- >- <qandaentry> > <question id="internal-plugnplay-modem"> > <para>Why is FreeBSD not finding my internal Plug & Play > modem?</para> >@@ -2980,8 +2516,7 @@ > > <qandaentry> > <question id="support-winmodem"> >- <para>Does FreeBSD support software modems, such as >- Winmodems?</para> >+ <para>Does FreeBSD support software modems, such as Winmodems?</para> > </question> > > <answer> >@@ -2999,6 +2534,44 @@ > </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> >@@ -3027,38 +2600,111 @@ > </answer> > </qandaentry> > >+ </qandaset> >+ >+ </sect1> >+ >+ <sect1 id="compatibility-sound"> >+ <title>Sound devices</title> >+ >+ <qandaset> >+ > <qandaentry> >- <question id="micron-3comnic-failure"> >- <para>Why does my 3Com PCI network card not work with my Micron >- computer?</para> >+ <question id="sound-card-support"> >+ <para>Which sound cards are supported by FreeBSD?</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>&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 >+ µsoft; Sound System specification are also supported.</para> > >- <para>To work around this problem, disable the >- <quote>Plug and Play Operating System</quote> flag in the >- BIOS.</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> > >- <para>More information on this problem is available at URL: >- <ulink URL="http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html#micron">http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html#micron</ulink></para> >+ <answer> >+ <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>Other hardware</title> >+ >+ <qandaset> >+ > <qandaentry> >- <question id="smp-support"> >- <para>Does FreeBSD support Symmetric Multiprocessing (SMP)?</para> >+ <question id="other-device-support"> >+ <para>What other devices does FreeBSD support?</para> > </question> > > <answer> >- <para>SMP is supported in 3.0-STABLE and later releases only. >- SMP is not enabled in the <emphasis>GENERIC</emphasis> kernel, >- so you will have to recompile your kernel to enable SMP. Take a >- look at <filename>/sys/i386/conf/LINT</filename> to figure out >- what options to put in your kernel config file.</para> >+ <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="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> > >@@ -3069,11 +2715,32 @@ > </question> > > <answer> >- <para>Go in to the BIOS setup and disable the <quote>boot virus >+ <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> > </qandaset> >+ >+ </sect1> >+ > </chapter> > > <chapter id="troubleshoot"> >@@ -5771,7 +5438,7 @@ > > <para>Unmounting the device is simple:</para> > >- <screen>&prompt.user; <userinput>umount<filename>~/my-mount-point</filename></userinput></screen> >+ <screen>&prompt.user; <userinput>umount <filename>~/my-mount-point</filename></userinput></screen> > > <para>Enabling <varname>vfs.usermount</varname>, however, has > negative security implications. A better way to access MSDOS >diff -ruN zh_TW.Big5.orig/share/sgml/bookinfo.ent zh_TW.Big5/share/sgml/bookinfo.ent >--- zh_TW.Big5.orig/share/sgml/bookinfo.ent Tue Nov 22 09:25:03 2005 >+++ zh_TW.Big5/share/sgml/bookinfo.ent Tue Nov 22 09:25:48 2005 >@@ -10,3 +10,7 @@ > --> > > <!ENTITY bookinfo.legalnotice SYSTEM "legalnotice.sgml"> >+ >+<!ENTITY bookinfo.trademarks SYSTEM "trademarks.sgml"> >+ >+<!ENTITY bookinfo.freebsd-glossary SYSTEM "glossary/freebsd-glossary.sgml"> >diff -ruN zh_TW.Big5.orig/share/sgml/glossary/freebsd-glossary.sgml zh_TW.Big5/share/sgml/glossary/freebsd-glossary.sgml >--- zh_TW.Big5.orig/share/sgml/glossary/freebsd-glossary.sgml Thu Jan 1 08:00:00 1970 >+++ zh_TW.Big5/share/sgml/glossary/freebsd-glossary.sgml Tue Nov 22 09:26:51 2005 >@@ -0,0 +1,1784 @@ >+<!-- >+ $FreeBSD$ >+ >+ FreeBSD Glossary Terms >+ Please keep this file sorted alphabetically/ASCIIly by glossterm. >+ >+ glossterms that are acronyms should have two entries - one for >+ the expanded acronym and another for the acronym itself. The >+ second of these should reference the entry for the expanded acronym >+ via a glosssee element. For example: >+ >+ <glossentry> >+ <glossterm>FUBAR</glossterm> >+ <glosssee otherterm="fubar-glossary"> >+ </glossentry> >+ >+ <glossentry id="fubar-glossary"> >+ <glossterm>Fuc... Up Beyond All Recognition</glossterm> >+ <acronym>FUBAR</acronym> >+ <glossdef> >+ <para>Broken.</para> >+ </glossdef> >+ </glossentry> >+ >+ Note that in this instance, the expanded acronym sorts below the >+ unexpanded acronym. That's OK. >+ >+ Finally, id attribute values should end in the string >+ "-glossary" to avoid conflicting with id attribute values in >+ the main text. >+ >+--> >+ >+<glossary status="draft" id="freebsd-glossary"> >+ <title>&os; Glossary</title> >+ <para>This glossary contains terms and acronyms used within the &os; >+ community and documentation.</para> >+ >+ <glossdiv> >+ <title>A</title> >+ >+ <glossentry> >+ <glossterm>ACL</glossterm> >+ <glosssee otherterm="acl-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>ACPI</glossterm> >+ <glosssee otherterm="acpi-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>AMD</glossterm> >+ <glosssee otherterm="amd-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>AML</glossterm> >+ <glosssee otherterm="aml-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>APIC</glossterm> >+ <glosssee otherterm="apic-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>APM</glossterm> >+ <glosssee otherterm="apm-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>APOP</glossterm> >+ <glosssee otherterm="apop-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>ASL</glossterm> >+ <glosssee otherterm="asl-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>ATA</glossterm> >+ <glosssee otherterm="ata-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>ATM</glossterm> >+ <glosssee otherterm="atm-glossary"> >+ </glossentry> >+ >+ <glossentry id="aml-glossary"> >+ <glossterm><acronym>ACPI</acronym> Machine Language</glossterm> >+ <acronym>AML</acronym> >+ <glossdef> >+ <para>Pseudocode, interpreted by a virtual machine within an >+ <acronym>ACPI</acronym>-compliant operating system, providing a >+ layer between the underlying hardware and the documented >+ interface presented to the <acronym>OS</acronym>.</para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="asl-glossary"> >+ <glossterm><acronym>ACPI</acronym> Source Language</glossterm> >+ <acronym>ASL</acronym> >+ <glossdef> >+ <para>The programming language <acronym>AML</acronym> is written in.</para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="acl-glossary"> >+ <glossterm>Access Control List</glossterm> >+ <acronym>ACL</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="acpi-glossary"> >+ <glossterm>Advanced Configuration and Power Interface</glossterm> >+ <acronym>ACPI</acronym> >+ <glossdef> >+ <para>A specification which provides an abstraction of the >+ interface the hardware presents to the operating system, so >+ that the operating system should need to know nothing about >+ the underlying hardware to make the most of it. <acronym>ACPI</acronym> >+ evolves and supercedes the functionality provided previously by >+ <acronym>APM</acronym>, <acronym>PNPBIOS</acronym> and other technologies, and >+ provides facilities for controlling power consumption, machine >+ suspension, device enabling and disabling, etc.</para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="apm-glossary"> >+ <glossterm>Advanced Power Management</glossterm> >+ <acronym>APM</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="apic-glossary"> >+ <glossterm>Advanced Programmable Interrupt Controller</glossterm> >+ <acronym>APIC</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="ata-glossary"> >+ <glossterm>Advanced Technology Attachment</glossterm> >+ <acronym>ATA</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="atm-glossary"> >+ <glossterm>Asynchronous Transfer Mode</glossterm> >+ <acronym>ATM</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="apop-glossary"> >+ <glossterm>Authenticated Post Office Protocol</glossterm> >+ <acronym>APOP</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="amd-glossary"> >+ <glossterm>Automatic Mount Daemon</glossterm> >+ <acronym>AMD</acronym> >+ <glossdef> >+ <para>A daemon that automatically mounts a filesystem when a file >+ or directory within that filesystem is accessed.</para> >+ </glossdef> >+ </glossentry> >+ </glossdiv> >+ >+ <glossdiv> >+ <title>B</title> >+ >+ <glossentry> >+ <glossterm>BIND</glossterm> >+ <glosssee otherterm="bind-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>BIOS</glossterm> >+ <glosssee otherterm="bios-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>BSD</glossterm> >+ <glosssee otherterm="bsd-glossary"> >+ </glossentry> >+ >+ <glossentry id="bios-glossary"> >+ <glossterm>Basic Input/Output System</glossterm> >+ <acronym>BIOS</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="bind-glossary"> >+ <glossterm>Berkeley Internet Name Domain</glossterm> >+ <acronym>BIND</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="bsd-glossary"> >+ <glossterm>Berkeley Software Distribution</glossterm> >+ <acronym>BSD</acronym> >+ <glossdef> >+ <para>This is the name that the Computer Systems Research Group >+ (CSRG) at <ulink url="http://www.berkeley.edu">The University >+ of California at Berkeley</ulink> >+ gave to their improvements and modifications to >+ AT&T's 32V &unix;. >+ &os; is a descendant of the CSRG work.</para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="bikeshed-glossary"> >+ <glossterm>Bikeshed Building</glossterm> >+ <glossdef subject="FreeBSD"> >+ <para>A phenomenon whereby many people will give an opinion on >+ an uncomplicated topic, whilst a complex topic receives little >+ or no discussion. See the >+ <ulink url="&url.books.faq;/misc.html#BIKESHED-PAINTING">FAQ</ulink> for >+ the origin of the term.</para> >+ </glossdef> >+ </glossentry> >+ </glossdiv> >+ >+ <glossdiv> >+ <title>C</title> >+ >+ <glossentry> >+ <glossterm>CD</glossterm> >+ <glosssee otherterm="cd-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>CHAP</glossterm> >+ <glosssee otherterm="chap-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>CLIP</glossterm> >+ <glosssee otherterm="clip-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>COFF</glossterm> >+ <glosssee otherterm="coff-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>CPU</glossterm> >+ <glosssee otherterm="cpu-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>CTS</glossterm> >+ <glosssee otherterm="cts-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>CVS</glossterm> >+ <glosssee otherterm="cvs-glossary"> >+ </glossentry> >+ >+ <glossentry id="cd-glossary"> >+ <glossterm>Carrier Detect</glossterm> >+ <acronym>CD</acronym> >+ <glossdef> >+ <para>An RS232C signal indicating that a carrier has been >+ detected.</para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="cpu-glossary"> >+ <glossterm>Central Processing Unit</glossterm> >+ <acronym>CPU</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="chap-glossary"> >+ <glossterm>Challenge Handshake Authentication Protocol</glossterm> >+ <acronym>CHAP</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="clip-glossary"> >+ <glossterm>Classical <acronym>IP</acronym> over <acronym>ATM</acronym></glossterm> >+ <acronym>CLIP</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="cts-glossary"> >+ <glossterm>Clear To Send</glossterm> >+ <acronym>CTS</acronym> >+ <glossdef> >+ <para>An RS232C signal giving the remote system >+ permission to send data.</para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="coff-glossary"> >+ <glossterm>Common Object File Format</glossterm> >+ <acronym>COFF</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="cvs-glossary"> >+ <glossterm>Concurrent Versions System</glossterm> >+ <acronym>CVS</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ </glossdiv> >+ >+ <glossdiv> >+ <title>D</title> >+ >+ <glossentry> >+ <glossterm>DAC</glossterm> >+ <glosssee otherterm="dac-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>DDB</glossterm> >+ <glosssee otherterm="ddb-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>DES</glossterm> >+ <glosssee otherterm="des-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>DHCP</glossterm> >+ <glosssee otherterm="dhcp-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>DNS</glossterm> >+ <glosssee otherterm="dns-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>DSDT</glossterm> >+ <glosssee otherterm="dsdt-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>DSR</glossterm> >+ <glosssee otherterm="dsr-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>DTR</glossterm> >+ <glosssee otherterm="dtr-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>DVMRP</glossterm> >+ <glosssee otherterm="dvmrp-glossary"> >+ </glossentry> >+ >+ <glossentry id="dac-glossary"> >+ <glossterm>Discretionary Access Control</glossterm> >+ <acronym>DAC</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="des-glossary"> >+ <glossterm>Data Encryption Standard</glossterm> >+ <acronym>DES</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="dsr-glossary"> >+ <glossterm>Data Set Ready</glossterm> >+ <acronym>DSR</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="dtr-glossary"> >+ <glossterm>Data Terminal Ready</glossterm> >+ <acronym>DTR</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="ddb-glossary"> >+ <glossterm>Debugger</glossterm> >+ <acronym>DDB</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="dsdt-glossary"> >+ <glossterm>Differentiated System Description Table</glossterm> >+ <acronym>DSDT</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="dvmrp-glossary"> >+ <glossterm>Distance-Vector Multicast Routing Protocol</glossterm> >+ <acronym>DVMRP</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="dns-glossary"> >+ <glossterm>Domain Name System</glossterm> >+ <acronym>DNS</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="dhcp-glossary"> >+ <glossterm>Dynamic Host Configuration Protocol</glossterm> >+ <acronym>DHCP</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ </glossdiv> >+ >+ <glossdiv> >+ <title>E</title> >+ >+ <glossentry> >+ <glossterm>ECOFF</glossterm> >+ <glosssee otherterm="ecoff-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>ELF</glossterm> >+ <glosssee otherterm="elf-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>ESP</glossterm> >+ <glosssee otherterm="esp-glossary"> >+ </glossentry> >+ >+ <glossentry id="esp-glossary"> >+ <glossterm>Encapsulated Security Payload</glossterm> >+ <acronym>ESP</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="elf-glossary"> >+ <glossterm>Executable and Linking Format</glossterm> >+ <acronym>ELF</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="ecoff-glossary"> >+ <glossterm>Extended <acronym>COFF</acronym></glossterm> >+ <acronym>ECOFF</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ </glossdiv> >+ >+ <glossdiv> >+ <title>F</title> >+ >+ <glossentry> >+ <glossterm>FADT</glossterm> >+ <glosssee otherterm="fadt-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>FAT</glossterm> >+ <glosssee otherterm="fat-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>FAT16</glossterm> >+ <glosssee otherterm="fat16-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>FTP</glossterm> >+ <glosssee otherterm="ftp-glossary"> >+ </glossentry> >+ >+ <glossentry id="fat-glossary"> >+ <glossterm>File Allocation Table</glossterm> >+ <acronym>FAT</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="fat16-glossary"> >+ <glossterm>File Allocation Table (16-bit)</glossterm> >+ <acronym>FAT16</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="ftp-glossary"> >+ <glossterm>File Transfer Protocol</glossterm> >+ <acronym>FTP</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="fadt-glossary"> >+ <glossterm>Fixed <acronym>ACPI</acronym> Description Table</glossterm> >+ <acronym>FADT</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossdiv> >+ >+ <glossdiv> >+ <title>G</title> >+ >+ <glossentry> >+ <glossterm>GUI</glossterm> >+ <glosssee otherterm="gui-glossary"> >+ </glossentry> >+ >+ <glossentry id="giant-glossary"> >+ <glossterm>Giant</glossterm> >+ <glossdef subject="FreeBSD"> >+ <para>The name of a mutual exclusion mechanism >+ (a <literal>sleep mutex</literal>) that protects a large >+ set of kernel resources. Although a simple locking mechanism >+ was adequate in the days where a machine might have only >+ a few dozen processes, one networking card, and certainly >+ only one processor, in current times it is an unacceptable >+ performance bottleneck. &os; developers are actively working >+ to replace it with locks that protect individual resources, >+ which will allow a much greater degree of parallelism for >+ both single-processor and multi-processor machines.</para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="gui-glossary"> >+ <glossterm>Graphical User Interface</glossterm> >+ <acronym>GUI</acronym> >+ <glossdef> >+ <para>A system where the user and computer interact with >+ graphics.</para> >+ </glossdef> >+ </glossentry> >+ </glossdiv> >+ >+ <glossdiv> >+ <title>H</title> >+ >+ <glossentry> >+ <glossterm>HTML</glossterm> >+ <glosssee otherterm="html-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>HUP</glossterm> >+ <glosssee otherterm="hup-glossary"> >+ </glossentry> >+ >+ <glossentry id="hup-glossary"> >+ <glossterm>HangUp</glossterm> >+ <acronym>HUP</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="html-glossary"> >+ <glossterm>HyperText Markup Language</glossterm> >+ <acronym>HTML</acronym> >+ <glossdef> >+ <para>The markup language used to create web pages.</para> >+ </glossdef> >+ </glossentry> >+ </glossdiv> >+ >+ <glossdiv> >+ <title>I</title> >+ >+ <glossentry> >+ <glossterm>I/O</glossterm> >+ <glosssee otherterm="io-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>IASL</glossterm> >+ <glosssee otherterm="iasl-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>IMAP</glossterm> >+ <glosssee otherterm="imap-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>IP</glossterm> >+ <glosssee otherterm="ip-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>IPFW</glossterm> >+ <glosssee otherterm="ipfw-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>IPP</glossterm> >+ <glosssee otherterm="ipp-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>IPv4</glossterm> >+ <glosssee otherterm="ipv4-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>IPv6</glossterm> >+ <glosssee otherterm="ipv6-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>ISP</glossterm> >+ <glosssee otherterm="isp-glossary"> >+ </glossentry> >+ >+ <glossentry id="ipfw-glossary"> >+ <glossterm><acronym>IP</acronym> Firewall</glossterm> >+ <acronym>IPFW</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="ipv4-glossary"> >+ <glossterm><acronym>IP</acronym> Version 4</glossterm> >+ <acronym>IPv4</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="ipv6-glossary"> >+ <glossterm><acronym>IP</acronym> Version 6</glossterm> >+ <acronym>IPv6</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="io-glossary"> >+ <glossterm>Input/Output</glossterm> >+ <acronym>I/O</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="iasl-glossary"> >+ <glossterm>Intel’s <acronym>ASL</acronym> compiler</glossterm> >+ <acronym>IASL</acronym> >+ <glossdef> >+ <para>Intel’s compiler for converting <acronym>ASL</acronym> into >+ <acronym>AML</acronym>.</para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="imap-glossary"> >+ <glossterm>Internet Message Access Protocol</glossterm> >+ <acronym>IMAP</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="ipp-glossary"> >+ <glossterm>Internet Printing Protocol</glossterm> >+ <acronym>IPP</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="ip-glossary"> >+ <glossterm>Internet Protocol</glossterm> >+ <acronym>IP</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="isp-glossary"> >+ <glossterm>Internet Service Provider</glossterm> >+ <acronym>ISP</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossdiv> >+ >+ <glossdiv> >+ <title>K</title> >+ >+ <glossentry id="kame-glossary"> >+ <glossterm>KAME</glossterm> >+ <glossdef> >+ <para>Japanese for <quote>turtle</quote>, the term KAME is used >+ in computing circles to refer to the <ulink >+ url="http://www.kame.net/">KAME Project</ulink>, who work on >+ an implementation of <acronym>IPv6</acronym>.</para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>KDC</glossterm> >+ <glosssee otherterm="kdc-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>KLD</glossterm> >+ <glosssee otherterm="kld-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>KSE</glossterm> >+ <glosssee otherterm="kse-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>KVA</glossterm> >+ <glosssee otherterm="kva-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>Kbps</glossterm> >+ <glosssee otherterm="kbps-glossary"> >+ </glossentry> >+ >+ <glossentry id="kld-glossary"> >+ <glossterm>Kernel &man.ld.1;</glossterm> >+ <acronym>KLD</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="kse-glossary"> >+ <glossterm>Kernel Scheduler Entities</glossterm> >+ <acronym>KSE</acronym> >+ <glossdef> >+ <para>A kernel-supported threading system. See the <ulink >+ url="http://www.FreeBSD.org/kse">project home page</ulink> >+ for further details.</para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="kva-glossary"> >+ <glossterm>Kernel Virtual Address</glossterm> >+ <acronym>KVA</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="kdc-glossary"> >+ <glossterm>Key Distribution Center</glossterm> >+ <acronym>KDC</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="kbps-glossary"> >+ <glossterm>Kilo Bits Per Second</glossterm> >+ <acronym>Kbps</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ </glossdiv> >+ >+ <glossdiv> >+ <title>L</title> >+ >+ <glossentry> >+ <glossterm>LAN</glossterm> >+ <glosssee otherterm="lan-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>LOR</glossterm> >+ <glosssee otherterm="lor-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>LPD</glossterm> >+ <glosssee otherterm="lpd-glossary"> >+ </glossentry> >+ >+ <glossentry id="lpd-glossary"> >+ <glossterm>Line Printer Daemon</glossterm> >+ <acronym>LPD</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="lan-glossary"> >+ <glossterm>Local Area Network</glossterm> >+ <acronym>LAN</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="lor-glossary"> >+ <glossterm>Lock Order Reversal</glossterm> >+ <acronym>LOR</acronym> >+ <glossdef> >+ <para>The &os; kernel uses a number of resource locks to >+ arbitrate contention for those resources. A run-time >+ lock diagnostic system found in &os.current; kernels >+ (but removed for releases), called &man.witness.4;, >+ detects the potential for deadlocks due to locking errors. >+ (&man.witness.4; is actually slightly conservative, so >+ it is possible to get false positives.) A true positive >+ report indicates that <quote>if you were unlucky, a deadlock would >+ have happened here</quote>.</para> >+ >+ <para>True positive LORs tend to get fixed quickly, so >+ check &a.current.url; and the >+ <ulink url="http://sources.zabbadoz.net/freebsd/lor.html"> >+ LORs Seen</ulink> page before posting to the mailing lists.</para> >+ </glossdef> >+ </glossentry> >+ </glossdiv> >+ >+ <glossdiv> >+ <title>M</title> >+ >+ <glossentry> >+ <glossterm>MAC</glossterm> >+ <glosssee otherterm="mac-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>MADT</glossterm> >+ <glosssee otherterm="madt-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>MFC</glossterm> >+ <glosssee otherterm="mfc-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>MFS</glossterm> >+ <glosssee otherterm="mfs-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>MIT</glossterm> >+ <glosssee otherterm="mit-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>MLS</glossterm> >+ <glosssee otherterm="mls-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>MOTD</glossterm> >+ <glosssee otherterm="motd-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>MTA</glossterm> >+ <glosssee otherterm="mta-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>MUA</glossterm> >+ <glosssee otherterm="mua-glossary"> >+ </glossentry> >+ >+ <glossentry id="mta-glossary"> >+ <glossterm>Mail Transfer Agent</glossterm> >+ <acronym>MTA</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="mua-glossary"> >+ <glossterm>Mail User Agent</glossterm> >+ <acronym>MUA</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="mac-glossary"> >+ <glossterm>Mandatory Access Control</glossterm> >+ <acronym>MAC</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="mit-glossary"> >+ <glossterm>Massachusetts Institute of Technology</glossterm> >+ <acronym>MIT</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="mfc-glossary"> >+ <glossterm>Merge From Current</glossterm> >+ <acronym>MFC</acronym> >+ <glossdef subject="FreeBSD"> >+ <para>To merge functionality or a patch from the -CURRENT >+ branch to another, most often -STABLE.</para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="mfs-glossary"> >+ <glossterm>Merge From Stable</glossterm> >+ <acronym>MFS</acronym> >+ <glossdef subject="FreeBSD"> >+ <para>In the normal course of FreeBSD development, a change will >+ be committed to the -CURRENT branch for testing before being >+ merged to -STABLE. On rare occasions, a change will go into >+ -STABLE first and then be merged to -CURRENT.</para> >+ >+ <para>This term is also used when a patch is merged from -STABLE >+ to a security branch.</para> >+ <glossseealso otherterm="mfc-glossary"> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="motd-glossary"> >+ <glossterm>Message Of The Day</glossterm> >+ <acronym>MOTD</acronym> >+ <glossdef> >+ <para>A message, usually shown on login, often used to >+ distribute information to users of the system.</para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="mls-glossary"> >+ <glossterm>Multi-Level Security</glossterm> >+ <acronym>MLS</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="madt-glossary"> >+ <glossterm>Multiple <acronym>APIC</acronym> Description Table</glossterm> >+ <acronym>MADT</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ </glossdiv> >+ >+ <glossdiv> >+ <title>N</title> >+ >+ <glossentry> >+ <glossterm>NAT</glossterm> >+ <glosssee otherterm="nat-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>NDISulator</glossterm> >+ <glosssee otherterm="projectevil-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>NFS</glossterm> >+ <glosssee otherterm="nfs-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>NTFS</glossterm> >+ <glosssee otherterm="ntfs-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>NTP</glossterm> >+ <glosssee otherterm="ntp-glossary"> >+ </glossentry> >+ >+ <glossentry id="nat-glossary"> >+ <glossterm>Network Address Translation</glossterm> >+ <acronym>NAT</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="nfs-glossary"> >+ <glossterm>Network File System</glossterm> >+ <acronym>NFS</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="ntfs-glossary"> >+ <glossterm>New Technology File System</glossterm> >+ <acronym>NTFS</acronym> >+ <glossdef> >+ <para>A filesystem developed by Microsoft and available in its >+ <quote>New Technology</quote> operating systems, such as >+ &windows2k;, &windowsnt; and &windowsxp;.</para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="ntp-glossary"> >+ <glossterm>Network Time Protocol</glossterm> >+ <acronym>NTP</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ </glossdiv> >+ >+ <glossdiv> >+ <title>O</title> >+ >+ <glossentry> >+ <glossterm>OBE</glossterm> >+ <glosssee otherterm="obe-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>ODMR</glossterm> >+ <glosssee otherterm="odmr-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>OS</glossterm> >+ <glosssee otherterm="os-glossary"> >+ </glossentry> >+ >+ <glossentry id="odmr-glossary"> >+ <glossterm>On-Demand Mail Relay</glossterm> >+ <acronym>ODMR</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="os-glossary"> >+ <glossterm>Operating System</glossterm> >+ <acronym>OS</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="obe-glossary"> >+ <glossterm>Overtaken By Events</glossterm> >+ <acronym>OBE</acronym> >+ <glossdef> >+ <para>Indicates a suggested change (such as a Problem Report >+ or a feature request) which is no longer relevant or >+ applicable due to such things as later changes to &os;, >+ changes in networking standards, the affected hardware >+ having since become obsolete, and so forth.</para> >+ </glossdef> >+ </glossentry> >+ </glossdiv> >+ >+ <glossdiv> >+ <title>P</title> >+ >+ <glossentry> >+ <glossterm>PAE</glossterm> >+ <glosssee otherterm="pae-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>PAM</glossterm> >+ <glosssee otherterm="pam-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>PAP</glossterm> >+ <glosssee otherterm="pap-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>PC</glossterm> >+ <glosssee otherterm="pc-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>PCNSFD</glossterm> >+ <glosssee otherterm="pcnfsd-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>PDF</glossterm> >+ <glosssee otherterm="pdf-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>PID</glossterm> >+ <glosssee otherterm="pid-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>POLA</glossterm> >+ <glosssee otherterm="pola-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>POP</glossterm> >+ <glosssee otherterm="pop-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>POP3</glossterm> >+ <glosssee otherterm="pop3-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>PPD</glossterm> >+ <glosssee otherterm="ppd-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>PPP</glossterm> >+ <glosssee otherterm="ppp-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>PPPoA</glossterm> >+ <glosssee otherterm="pppoa-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>PPPoE</glossterm> >+ <glosssee otherterm="pppoe-glossary"> >+ </glossentry> >+ >+ <glossentry id="pppoa-glossary"> >+ <glossterm><acronym>PPP</acronym> over <acronym>ATM</acronym></glossterm> >+ <acronym>PPPoA</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="pppoe-glossary"> >+ <glossterm><acronym>PPP</acronym> over <acronym>Ethernet</acronym></glossterm> >+ <acronym>PPPoE</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>PR</glossterm> >+ <glosssee otherterm="pr-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>PXE</glossterm> >+ <glosssee otherterm="pxe-glossary"> >+ </glossentry> >+ >+ <glossentry id="pap-glossary"> >+ <glossterm>Password Authentication Protocol</glossterm> >+ <acronym>PAP</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="pc-glossary"> >+ <glossterm>Personal Computer</glossterm> >+ <acronym>PC</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="pcnfsd-glossary"> >+ <glossterm>Personal Computer Network File System Daemon</glossterm> >+ <acronym>PCNFSD</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="pae-glossary"> >+ <glossterm>Physical Address Extensions</glossterm> >+ <acronym>PAE</acronym> >+ <glossdef> >+ <para>A method of enabling access to up to 64 GB of <acronym>RAM</acronym> on >+ systems which only physically have a 32-bit wide address space >+ (and would therefore be limited to 4 GB without PAE).</para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="pam-glossary"> >+ <glossterm>Pluggable Authentication Modules</glossterm> >+ <acronym>PAM</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="ppp-glossary"> >+ <glossterm>Point-to-Point Protocol</glossterm> >+ <acronym>PPP</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="pointyhat"> >+ <glossterm>Pointy Hat</glossterm> >+ <glossdef subject="FreeBSD"> >+ <para>A mythical piece of headgear, much like a >+ <literal>dunce cap</literal>, awarded to any &os; >+ committer who breaks the build, makes revision numbers >+ go backwards, or creates any other kind of havoc in >+ the source base. Any committer worth his or her salt >+ will soon accumulate a large collection. The usage is >+ (almost always?) humorous.</para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="pdf-glossary"> >+ <glossterm>Portable Document Format</glossterm> >+ <acronym>PDF</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="pop-glossary"> >+ <glossterm>Post Office Protocol</glossterm> >+ <acronym>POP</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="pop3-glossary"> >+ <glossterm>Post Office Protocol Version 3</glossterm> >+ <acronym>POP3</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="ppd-glossary"> >+ <glossterm>PostScript Printer Description</glossterm> >+ <acronym>PPD</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="pxe-glossary"> >+ <glossterm>Preboot eXecution Environment</glossterm> >+ <acronym>PXE</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="pola-glossary"> >+ <glossterm>Principle Of Least Astonishment</glossterm> >+ <acronym>POLA</acronym> >+ <glossdef> >+ <para>As &os; evolves, changes visible to the user should be >+ kept as unsurprising as possible. For example, arbitrarily >+ rearranging system startup variables in >+ <filename>/etc/defaults/rc.conf</filename> violates >+ <acronym>POLA</acronym>. Developers consider >+ <acronym>POLA</acronym> when contemplating user-visible >+ system changes.</para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="pr-glossary"> >+ <glossterm>Problem Report</glossterm> >+ <acronym>PR</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="pid-glossary"> >+ <glossterm>Process ID</glossterm> >+ <acronym>PID</acronym> >+ <glossdef> >+ <para>A number, unique to a particular process on a system, >+ which identifies it and allows actions to be taken against it.</para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="projectevil-glossary"> >+ <glossterm>Project Evil</glossterm> >+ <glossdef subject="FreeBSD"> >+ <para>The working title for the <acronym>NDISulator</acronym>, >+ written by Bill Paul, who named it referring to how awful >+ it is (from a philosophical standpoint) to need to have >+ something like this in the first place. The >+ <acronym>NDISulator</acronym> is a special compatibility >+ module to allow Microsoft Windows™ NDIS miniport >+ network drivers to be used with &os;/i386. This is usually >+ the only way to use cards where the driver is closed-source. >+ See <filename>src/sys/compat/ndis/subr_ndis.c</filename>.</para> >+ </glossdef> >+ </glossentry> >+ </glossdiv> >+ >+ <glossdiv> >+ <title>R</title> >+ >+ <glossentry> >+ <glossterm>RA</glossterm> >+ <glosssee otherterm="ra-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>RAID</glossterm> >+ <glosssee otherterm="raid-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>RAM</glossterm> >+ <glosssee otherterm="ram-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>RD</glossterm> >+ <glosssee otherterm="rd-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>RFC</glossterm> >+ <glosssee otherterm="rfc-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>RISC</glossterm> >+ <glosssee otherterm="risc-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>RPC</glossterm> >+ <glosssee otherterm="rpc-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>RS232C</glossterm> >+ <glosssee otherterm="rs232c-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>RTS</glossterm> >+ <glosssee otherterm="rts-glossary"> >+ </glossentry> >+ >+ <glossentry id="ram-glossary"> >+ <glossterm>Random Access Memory</glossterm> >+ <acronym>RAM</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="rd-glossary"> >+ <glossterm>Received Data</glossterm> >+ <acronym>RD</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="rs232c-glossary"> >+ <glossterm>Recommended Standard 232C</glossterm> >+ <acronym>RS232C</acronym> >+ <glossdef> >+ <para>A standard for communications between serial devices.</para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="risc-glossary"> >+ <glossterm>Reduced Instruction Set Computer</glossterm> >+ <acronym>RISC</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="raid-glossary"> >+ <glossterm>Redundant Array of Inexpensive Disks</glossterm> >+ <acronym>RAID</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="rpc-glossary"> >+ <glossterm>Remote Procedure Call</glossterm> >+ <acronym>RPC</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="rfc-glossary"> >+ <glossterm>Request For Comments</glossterm> >+ <acronym>RFC</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="rts-glossary"> >+ <glossterm>Request To Send</glossterm> >+ <acronym>RTS</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="ra-glossary"> >+ <glossterm>Router Advertisement</glossterm> >+ <acronym>RA</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ </glossdiv> >+ >+ <glossdiv> >+ <title>S</title> >+ >+ <glossentry> >+ <glossterm>SCI</glossterm> >+ <glosssee otherterm="sci-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>SCSI</glossterm> >+ <glosssee otherterm="scsi-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>SG</glossterm> >+ <glosssee otherterm="sg-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>SMB</glossterm> >+ <glosssee otherterm="smb-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>SMP</glossterm> >+ <glosssee otherterm="smp-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>SMTP</glossterm> >+ <glosssee otherterm="smtp-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>SMTP AUTH</glossterm> >+ <glosssee otherterm="smtpauth-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>SSH</glossterm> >+ <glosssee otherterm="ssh-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>STR</glossterm> >+ <glosssee otherterm="str-glossary"> >+ </glossentry> >+ >+ <glossentry id="smtpauth-glossary"> >+ <glossterm><acronym>SMTP</acronym> Authentication</glossterm> >+ <acronym>SMTP AUTH</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="smb-glossary"> >+ <glossterm>Server Message Block</glossterm> >+ <acronym>SMB</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="sg-glossary"> >+ <glossterm>Signal Ground</glossterm> >+ <acronym>SG</acronym> >+ <glossdef> >+ <para>An RS232 pin or wire that is the ground reference >+ for the signal.</para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="smtp-glossary"> >+ <glossterm>Simple Mail Transfer Protocol</glossterm> >+ <acronym>SMTP</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="ssh-glossary"> >+ <glossterm>Secure Shell</glossterm> >+ <acronym>SSH</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="scsi-glossary"> >+ <glossterm>Small Computer System Interface</glossterm> >+ <acronym>SCSI</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="str-glossary"> >+ <glossterm>Suspend To <acronym>RAM</acronym></glossterm> >+ <acronym>STR</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="smp-glossary"> >+ <glossterm>Symmetric MultiProcessor</glossterm> >+ <acronym>SMP</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="sci-glossary"> >+ <glossterm>System Control Interrupt</glossterm> >+ <acronym>SCI</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ </glossdiv> >+ >+ <glossdiv> >+ <title>T</title> >+ >+ <glossentry> >+ <glossterm>TCP</glossterm> >+ <glosssee otherterm="tcp-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>TD</glossterm> >+ <glosssee otherterm="td-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>TFTP</glossterm> >+ <glosssee otherterm="tftp-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>TGT</glossterm> >+ <glosssee otherterm="tgt-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>TSC</glossterm> >+ <glosssee otherterm="tsc-glossary"> >+ </glossentry> >+ >+ <glossentry id="tgt-glossary"> >+ <glossterm>Ticket-Granting Ticket</glossterm> >+ <acronym>TGT</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="tsc-glossary"> >+ <glossterm>Time Stamp Counter</glossterm> >+ <acronym>TSC</acronym> >+ <!-- From dg@, 20040814125503.GF40460@nexus.dglawrence.com --> >+ <glossdef> >+ <para>A profiling counter internal to modern &pentium; processors >+ that counts core frequency clock ticks.</para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="tcp-glossary"> >+ <glossterm>Transmission Control Protocol</glossterm> >+ <acronym>TCP</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="td-glossary"> >+ <glossterm>Transmitted Data</glossterm> >+ <acronym>TD</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="tftp-glossary"> >+ <glossterm>Trivial <acronym>FTP</acronym></glossterm> >+ <acronym>TFTP</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ </glossdiv> >+ >+ <glossdiv> >+ <title>U</title> >+ >+ <glossentry> >+ <glossterm>UDP</glossterm> >+ <glosssee otherterm="udp-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>UFS1</glossterm> >+ <glosssee otherterm="ufs1-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>UFS2</glossterm> >+ <glosssee otherterm="ufs2-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>UID</glossterm> >+ <glosssee otherterm="uid-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>URL</glossterm> >+ <glosssee otherterm="url-glossary"> >+ </glossentry> >+ >+ <glossentry> >+ <glossterm>USB</glossterm> >+ <glosssee otherterm="usb-glossary"> >+ </glossentry> >+ >+ <glossentry id="url-glossary"> >+ <glossterm>Uniform Resource Locator</glossterm> >+ <acronym>URL</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="ufs1-glossary"> >+ <glossterm>Unix File System Version 1</glossterm> >+ <acronym>UFS1</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="ufs2-glossary"> >+ <glossterm>Unix File System Version 2</glossterm> >+ <acronym>UFS2</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="usb-glossary"> >+ <glossterm>Universal Serial Bus</glossterm> >+ <acronym>USB</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="uid-glossary"> >+ <glossterm>User ID</glossterm> >+ <acronym>UID</acronym> >+ <glossdef> >+ <para>A unique number assigned to each user of a computer, >+ by which the resources and permissions assigned to that >+ user can be identified.</para> >+ </glossdef> >+ </glossentry> >+ >+ <glossentry id="udp-glossary"> >+ <glossterm>User Datagram Protocol</glossterm> >+ <acronym>UDP</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ </glossdiv> >+ >+ <glossdiv> >+ <title>V</title> >+ >+ <glossentry> >+ <glossterm>VPN</glossterm> >+ <glosssee otherterm="vpn-glossary"> >+ </glossentry> >+ >+ <glossentry id="vpn-glossary"> >+ <glossterm>Virtual Private Network</glossterm> >+ <acronym>VPN</acronym> >+ <glossdef> >+ <para></para> >+ </glossdef> >+ </glossentry> >+ </glossdiv> >+</glossary>
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 89456
: 59440