diff --git a/zh_TW.Big5/books/faq/book.sgml b/zh_TW.Big5/books/faq/book.sgml
index 9a8ea43075..336cfb965c 100644
--- a/zh_TW.Big5/books/faq/book.sgml
+++ b/zh_TW.Big5/books/faq/book.sgml
@@ -1,11667 +1,11334 @@
%man;
%freebsd;
%authors;
%teams;
%bookinfo;
%mailing-lists;
+
+%books.ent;
+
]>
- FreeBSD 2.X¡A3.X ¤Î 4.X ±`¨£°Ýµª¶°
+ FreeBSD 4.X¡A5.X ¤Î 6.X ±`¨£°Ýµª¶°
FreeBSD ¤å¥ópµe
$FreeBSD$
1995
1996
1997
1998
1999
2000
2001
2002
+ 2003
+ 2004
+ 2005
FreeBSD ¤å¥ópµe
&bookinfo.legalnotice;
+
+ &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;
+
+
- ³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
+ ³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
+ &a.doc;¡C±z¥i¥H±q
FreeBSD World Wide Web ®³¨ì³o¥÷¤å¥óªº³Ì·sª©¥»¡C
- ±z¤]¥i¥H§Q¥Î HTTP ¨Ó¤U¸ü¤@¥÷Ãe¤jªº HTML
+ ¤]¥i¥H§Q¥Î HTTP ¨Ó¤U¸ü¤@¥÷Ãe¤jªº HTML
¤å¥ó¡A©Î¬O¸g¥Ñ
FreeBSD FTP ¯¸ ¤U¸ü¯Â¤å¦r¡Apostscript¡A©Î PDF ª©¥»ªºÀɮסC
±z¤]¥i¥H¦b³o¸Ì¨Ï¥Î
- ·j´M¸ê®Æ
+ ·j´M¸ê®Æ
ªº¥\¯à¡C
Ying-Chieh
Liao
ijliao@FreeBSD.org
«e¨¥
- Åwªï¨Ó¨ì FreeBSD 2.X-4.X FAQ!
+ Åwªï¨Ï¥Î FreeBSD 4.X-6.X FAQ!
¸ò¨ä¥L Usenet ¤Wªº FAQ ¤@¼Ë¡A³o¥÷¤å¥ó²[»\¤F¦³Ãö FreeBSD ³o®M§@·~
¨t²Î³Ì±`³Q°Ý¨ìªº°ÝÃD (·íµM¥]¬A¤F¦^µª¡I)¡CÁöµM»¡§ÚÌ¥»¨Óªº¥Øªº¬O¬°¤F
´î¤Öºô¸ôÀW¼eªº®ö¶O¥H¤ÎÁקK¦P¼Ëªº°ÝÃD¤@¦A¥X²{¡A¦ý¨Æ¹ê¤W FAQ ¤w¸g³Qµø
¬°¬O¤@ºØȱo¾\Ūªº¤å¥ó¸ê·½¡C
§Ṳ́w¸g¾¨¥i¯à¦a¨Ï³o¥÷ FAQ §óÂ×´I¤F¡C¦pªG±z¹ï¦p¦ó¨Ï¨ä§ó¶i¨B¦³¥ô
- ¦ó«Øij¡A½ÐÀH®É±H¹q¤l¶l¥óµ¹ &a.faq;¡C
+ ¦ó«Øij¡A½ÐÀH®É±H¹q¤l¶l¥óµ¹ &a.doc;¡C
¤°»ò¬O FreeBSD¡H
- ²³æ¦a¨Ó»¡¡AFreeBSD ¬O¤@®M¥i¥H¦b i386 ©M Alpha/AXP ¤W°õ¦æªº
+ ²³æ¦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¨Óªº
4.4BSD-Lite
¡A¨Ã¥[¤W¤F³\¦h 4.4BSD-Lite2
ªº¼W±j¥\¯à¡C¥¦¦P®É¤]¶¡±µ¨Ï¥Î¤F U.C. Berkeley ©Ò¶}µo¥X¨Ó¨Ã¥Ñ
William Jolitz ²¾´Ó¨ì i386 ªº Net/2
¡A¤]´N¬O
386BSD
¡A¤£¹L²{¦b 386BSD ªºµ{¦¡½X¥u³Ñ¤U·¥¤Ö¼ÆÁÙ¯d
¦s¦b FreeBSD ¤¤¡C±z¥i¥H¦b
- FreeBSD º¶ §ä¨ì¦³Ãö
+ FreeBSD º¶ §ä¨ì¦³Ãö
¤°»ò¬O FreeBSD ¥H¤Î¥¦¥i¥HÀ°±z°µ¨Ç¤°»òªº¬ÛÃö¸ê°T¡C
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
- FreeBSD Gallery
- ¬Ý¨ì¤@¨Ç¦³Ãö¥L̪º¸ê®Æ¡C
+ ±M®a¡A¾Ç¥Í¡A¥H¤Î®a®x¥Î¤á©Ò¨Ï¥Î¡A¥Î¦b¤u§@¡A±Ð¨|¡A¥H¤Î®T¼Ö¤W¡C
¦pªG·Q¬ÝÃö©ó FreeBSD §ó²`¤Jªº¸ê®Æ¡A½Ð¬Ý
- FreeBSD ¨Ï¥Î¤â¥U ¡C
+ FreeBSD ¨Ï¥Î¤â¥U ¡C
µo®i FreeBSD ªº¥Øªº¬O¤°»ò¡H
FreeBSD pµeªº¥Øªº¬O´£¨Ñ¥i¥H¥ô·N¨Ï¥Î¥B¨S¦³¨îªº³nÅé¡C§Ú̦b
µ{¦¡½X (¥H¤Îp±Þ¥»¨) ¤W¥I¥X¤F¤j¶q¤ß¦å¡A·íµM¤£·|¤¶·N¨ÓÂIª÷¿ú¤Wªº
¦^õX¡A¤£¹L§Ú̵´¹ï¤£·|¦p¦¹°í«ù¡C§Ú̬۫H§Ú̺nªº
¥ô°È
´N¬O´£¨Ñµ{¦¡½Xµ¹¨C¤@ӨϥΪ̡A¤£ºÞ¥LÌ¥´ºâ¥Î
¨Ó·F¹À¡F³o»ò¤@¨Ó¡A³o¨Çµ{¦¡½X¤~¯à³Q¥Î¦b³Ì¦h¦a¤è¡A¤]¤~¯àµo´§¥¦Ì³Ì
¤jªº§Q¯q¡C§Ú̬۫H³o´N¬O¦Û¥Ñ³nÅé³Ì°ò¥»ªº¥Ø¼Ð¤§¤@¡A¦Ó¥B§ÚÌ·|ºÉ¥þ
¤O¥h¤ä«ù¥¦¡C
¦b§ÚÌ source tree ¤¤¦³³¡¥÷ªºµ{¦¡½X¬O±Ä¥Î©Ò¿×ªºGPL ©Î¬O
LGPL
ª©Åv«Å§i¡AÁöµM³o¨Çª©Åv«Å§i¬O¥Î¨Ó«O»Ù¦Ó«D¨î¨Ï¥ÎªÌªºÅv
§Q¡A²¦³º¬O¤£¨º»ò¦Û¥Ñ¤F¨Ç¡C¥Ñ©ó³o¨Ç GPL ªº³nÅé¦b°Ó·~¨Ï¥Î¤W·|¤Þ°_
«D±`½ÆÂøªºª©Åv°ÝÃD¡A¦]¦¹¥un¦³¾÷·|¡A§ÚÌ·|ºÉ¶q¥H±Ä¥Î¤ñ¸ûÃPªº
FreeBSD ª©Åv ªº³nÅé¨Ó¨ú¥N³o¨Ç GPL ª©Åv«Å§iªº³nÅé¡C
FreeBSD ª©Åv¦³¥ô¦ó¨î¶Ü¡H
¦³ªº¡C¦ý¬O³o¨Ã¤£¬O¨î§A«ç»ò¥h¨Ï¥Î³o¨Çµ{¦¡½X¡A¦Ó¬O§A«ç»ò¬Ý«Ý
FreeBSD ³oÓpµe¡C¦pªG§A¦³ª©ÅvµJ¼{¯gªº¸Ü¡A½Ð¾\Ū
ª©Åv¥»¤å ¡C²³æ¦a¨Ó»¡¡A³o¥÷ª©Åvªº«ÂI¥i¥H±ø¦C¦p¤U¡C
½Ð¤Å«ÅºÙ¬O±z¼g¤F³oÓµ{¦¡¡C
¦pªG¥¦¥X°ÝÃD¤F¡A¤£n±±§i§ÚÌ¡C
FreeBSD ¥i¥H¨ú¥N§Ú²{¦b¦b¥Îªº§@·~¨t²Î¶Ü¡H
¹ï¤j³¡¥÷ªº¤H¨Ó»¡¬O³o¼Ë¨S¿ù¡A¦ý¨Æ¹ê¤W³o°ÝÃD¨Ã¨S¦³³o»ò¦n¦^
榭C
¤j³¡¥÷ªº¤H¨Ã¤£¬O¯u¥¿¦b¨Ï¥Î¤@Ó§@·~¨t²Î¡C¥L̨ϥΪº¬OÀ³¥Îµ{¦¡
¡F¦Ó¨º¨ÇÀ³¥Îµ{¦¡¤~¬O¯u¥¿¥Î¨ì§@·~¨t²ÎªºªF¦è¡CFreeBSD ¬O³]p¥Î¨Ó´£
¨Ñ¤@Ó±j¶´¥B¥\¯à§¹¾ãªº§@·~Àô¹Òµ¹À³¥Îµ{¦¡¨Ó°õ¦æ¡C¥¦¤ä´©¤F¦hºØÂsÄý
¾¹¡A¿ì¤½«Ç®M¥ó³nÅé¡A¹q¤l¶l¥ó¾\Ū³nÅé¡Aø¹Ïµ{¦¡¡Aµ{¦¡³]pÀô¹Ò¡Aºô
¸ô¦øªA¾¹³nÅé¡A¥H¤Î´X¥G©Ò¦³§A·QnªºªF¦è¡C¤j³¡¥÷ªºµ{¦¡³£¥i¥H¾aPorts Collection ¨ÓºÞ
²z¡C
¦ý¬O¦pªG§A·Qn¨Ï¥ÎªºÀ³¥Îµ{¦¡¥u¯à¦b¬YÓ¯S©wªº§@·~¨t²Î¤W±°õ¦æ
ªº¸Ü¡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
- ¦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 ªº
+ ¦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 FreeBSD ¨Ï¥Î¤â¥U ¨Ó¤J
- ªù¡C
+ url="&url.books.handbook;/index.html">FreeBSD ¨Ï¥Î¤â¥U ¨Ó¤Jªù¡C
¬°¤°»òn¥s°µ FreeBSD¡H
±z¥i¥H§K¶O¨Ï¥Î¥¦¡A§Y¨Ï¬O¥Î©ó°Ó·~¥Î³~¡C
¾ãÓ FreeBSD §@·~¨t²Î§¹¾ãªºì©lµ{¦¡³£¥i¥H§K¶O¨ú±o¡A¦Ó¥B¤£
ºÞ¬O¦b¨Ï¥Î¡A´²§G©Î¬O¾ã¦X¶i¨ä¥Lµ{¦¡µ¥¦U¤è±¤]¥u¨ü¨ì³Ì¤pªº
¨î (¤£½×¬O§_¥Î©ó°Ó·~¥Î³~)¡C
¥ô¦ó¤H³£¥i¥H¦Û¥Ñ¦a§â¥L¹ï¨t²Îªº§ï¨}©Î¿ù»~×¥¿ªºµ{¦¡½X¥[¤J
source tree ¤§¤¤ (·íµMn²Å¦X´XÓ¥ý¨M±ø¥ó)¡C
¯S§Oȱoª`·Nªº¬O³o¸Ìªº free
¥X²{¤F¨â¦¸¡A¦Ó¥B¥¦Ì
ªº·N«ä¬O¤£¤@¼Ëªº¡G¤@ºØ¥Nªí §K¶O
¡A¥t¤@ºØ¥Nªí
¦Û¥Ñ
¡C±z¥i¥H®³ FreeBSD ¥h°µ¥ô¦ó±z·Qn°µªº¨Æ¡A°£¤F¤@¨Ç
¨Ò¥~ ¡A¨Ò¦p±z«ÅºÙ FreeBSD ¬O±z¼gªº¡C
+
+
+ FreeBSD ¤Î NetBSD, OpenBSD ¥H¤Î¨ä¥L
+ open source BSD §@·~¨t²Î¤§¶¡¦³¦ó¤£¦P¤§³B©O¡H
+
+
+
+ James Howard ¦b DaemonNews
+ ¤W¼g¤F
+ The BSD Family Tree ªº¤å¥ó¡A¸Ì±»¡©ú¤F³o¨Ç¾ú¥v²W·½¤Î³o¨Ç *BSD
+ ®a±Úpµe¤§¶¡ªº®t²§¡C
+
+
+
³Ì·sª©ªº FreeBSD ¬O¨º¤@ª©¡H
-
- &rel.current;
- ¬O¥Ø«e³Ì·sªº RELEASE ª©¡F¥¦©ó
- &rel.current.date; µo¦æ¡C¥¦¦P®É¤]¬O¥Ø«e³Ì·sªº
- STABLE ª©¡C
+
+
+
+ ´N FreeBSD ¥Ø«eªºµo®i¦Ó¨¥¡A¦³¥|Ó¥Dnµo®i¤À¤ä(¨ä¤¤¤TÓ¤w¦³ RELEASE)¡G
+ ¥Ñ 4-STABLE ©Òµo¦æ(release)ªº 4.X ¨t¦C¡B
+ ¥Ñ 5-STABLE ©Òµo¦æ(release)ªº 5.X ¨t¦C¡B
+ ¥Ñ 6-STABLE ©Òµo¦æ(release)ªº 6.X ¨t¦C¡A
+ ¥H¤Î 7-CURRENT ¤À¤ä¡C
+
+ ¦b 5.3 release ¤§«e¡A4.X ¨t¦C¤´³Qµø¬°¬O -STABLE ¤§¤@¡C
+ ¦Û±q 5.3 ¶}©l¡A5.X ¶}©l³W¹º·sªº -STABLE µ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
+
+
+ ©ó &rel.current.date; ©Òµo¦æªº&rel.current;
+ ª©¬O¥Ø«e³Ì·sªº 6-STABLE ª©¡F
+ ¦Ó©ó &rel2.current.date; ©Òµo¦æªº&rel2.current;
+ ª©«h¬O¥Ø«e³Ì·sªº &rel.current.date; ª©¡C
²³æªº»¡¡A-STABLE ªº¥Dn¶D¨D¹ï¶H¬O¹ï©ó
éw©Ê¤Î§CÅܲ§©Êªº»Ý¨D»·³Ó¹L¹ï³Ì·s -CURRENT
snapshot ¤¤¯S§O·s¥\¯àªº»Ý¨D¡A¨Ò¦p ISP ©Î¤½¥q¦æ¸¹ªº¨Ï¥ÎªÌ¡C³o¨âÓ
branch ³£¦³¥i¯à·|²£¥Í release ª©¡A¦ý¥u¦³·í§A¯à±µ¨ü
-CURRENT »·¤ñ -STABLE
®e©ö§ó°Ê³o¤@ÂI¡A¤~À³¸Ó¥Î -CURRENT ¡C
Release ª© ¨C´XÓ¤ë¤~·|µ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¡]¸Ô¨£
FreeBSD-CURRENT ©M FreeBSD-STABLE ªº¬ÛÃö°ÝÃD)¡A¦ý¦]¬°ì©l½X
¬O¤@ª½¤£Â_¦a¦bÅܰʪº¡A©Ò¥H¦pªGn³o»ò°µªº¸Ü±onªá¤W§ó¦hªººë
¤O¡C
+
+ ¨ä¥L§ó¦h¬ÛÃö FreeBSD µo¦æ±¡³ø¡A¥i¥Ñ FreeBSD ºô¯¸¤Wªº Release Engineering ±oª¾
¤°»ò¬O FreeBSD-CURRENT¡H
FreeBSD-CURRENT
+ url="&url.books.handbook;/cutting-edge.html#CURRENT">FreeBSD-CURRENT
«üªº¬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½Ð°Ñ¦Ò ¨Ï¥Î¤â¥U ªº ¬ÛÃö³¡¥÷ ¡C
+ url="&url.books.handbook;/index.html">¨Ï¥Î¤â¥U ªº ¬ÛÃö³¡¥÷ ¡C
¦pªG±z¹ï§@·~¨t²Î¥»¨¨Ã¤£¬O«Ü¼ô±x¡A©Î¬O±z¨S¿ìªk¤À¿ë±z¹J¨ìªº°Ý
ÃD¬O¯uªºµo¥Í¤F°ÝÃD¥ç©Î¬O¼È®É©Êªº¤pª¬ªp¡A¨º»ò±z´N¤£À³¸Ó¨Ï¥Î
FreeBSD-CURRENT¡C³oÓ¤À¤äªºµ{¦¡½X¦³®ÉÔÅܰʱo«Ü§Ö¡A¦Ó¥B¥i¯à·|¦]¦¹
¦Ó¨Ï±z¦³¦n´X¤Ñªº®É¶¡µLªk§ó·s±zªº¨t²Î¡C§ÚÌ°²³]¨Ï¥Î
FreeBSD-CURRENT ªº¨Ï¥ÎªÌ³£¦³¯à¤O¥h¤ÀªR¥LÌ©Ò¹J¨ìªº°ÝÃD¨Ã¥B¥u¦^³ø
¯u¥¿ªº°ÝÃD¦Ó«D¤pª¬ªp
¡C¦pªG±z¦b -CURRENT mailing
list ¤¤´£¨ìÃþ¦ümake world ³y¦¨¤@¨Ç¦³Ãö groups ªº¿ù
»~
¤§Ãþªº°ÝÃDªº¸Ü¡A¤]³\·|³Q¨ä¥L¤H»´µø¡C
§Ų́C¤Ñ³£·|®Ú¾Ú¥Ø«e -CURRENT ©M -STABLE ªºª¬ªp¹ï³o¨âÓ¤À¤ä¦U
- µo¦æ¤@Ósnapshot
+ µo¦æ¤@Ósnapshot
ª©¡C¦³ªº®ÉԬƦÜÁÙ·|µo¦æ¥i¨Ñ¨ú±oªºª©¥»¡Cµoªí³o¨Ç snapshot
ªº¥Øªº¦b©ó¡G
´ú¸Õ³Ì·sª©ªº¦w¸Ëµ{¦¡¡C
´£¨Ñ¤@Ó²³æªº¤èªkµ¹¨º¨Ç³ßÅw¨Ï¥Î -CURRENT ©Î¬O -STABLE ¦ý
¬O¨S¦³®É¶¡©MÀW¼e¥h¨C¤Ñª@¯Åªº¨Ï¥ÎªÌ¡C
¬°¤F´À§Ú̵o®i¤¤ªºµ{¦¡«O¯d¤@Ó©T©wªº°Ñ¦ÒÂI¡A¥H¨¾¤î§ÚÌ¥¼
¨Ó³y¦¨¤£©¯¡C(ÁöµM¤@¯ë¦Ó¨¥ CVS ¥i¥H¨¾¤îÃþ¦ü³oºØªº¥i©È¨Æ¥ó :)
¬°¤F½T«O©Ò¦³»Ýn´ú¸Õªº·s¥\¯à³£¥i¥H±o¨ì³Ì¦hªº´ú¸Õ¡C
- §Ṳ́£¹ï -CURRENT snapshot °µ¥ô¦X§Î¦¡ªº«~½è«O
+ §Ṳ́£¹ï -CURRENT snapshot °µ¥ô¦ó§Î¦¡ªº«~½è«O
ÃÒ
¡C¦pªG§A·Qnªº¬O¤@Óéw¥B¸g¹L¥R¤À´ú¸Õ¹Lªº¨t²Îªº¸Ü¡A
³Ì¦n¿ï¾Ü¨Ï¥Î§¹¾ã release ªºª©¥»¡A©Î¬O¨Ï¥Î -STABLE snapshots¡C
±z¥i¥Hª½±µ±q
- ftp://current.FreeBSD.org/pub/FreeBSD/ ¨ú±o 5.0-CURRENT ªº
- snapshot release¡A¦Ó±q releng4.FreeBSD.org
- ¨ú±o 4-STABLE ªº snapshots¡C¦b¥»¤å¼g§@ªº®ÉÔ
- (2000 ¦~ 5 ¤ë) ´N¤w¸g¤£¦A´£¨Ñ 3-STABLE ªº snapshots ¤F¡C
+ URL="ftp://current.FreeBSD.org/pub/FreeBSD/snapshots/">
+ ftp://current.FreeBSD.org/pub/FreeBSD/snapshots/ ¨ú±o -CURRENT ªº
+ snapshot release
¹ï¨CÓ¦³¦b¬¡°Êªº¤À¤ä¦Ó¨¥¡A¥§¡¨C¤Ñ³£·|²£¥Í¤@¦¸ snapshots¡C
¤°»ò¬O FreeBSD-STABLE¡H
¦^·¹¨ì FreeBSD 2.0.5 èµoªíªº®ÉÔ¡A§Ų́M©w§â FreeBSD ªºµo®i
- ¤À¦¨¨â¤ä¡C¤@¤ä¥s°µ -STABLE
- ¡A§ÚÌ¥u¹ï¥¦°µ¿ù»~×¥¿¤Î¤p´T«×ªº×§ï (³o¬Oµ¹ ISP ©M°Ó·~
- ¤½¥qµ¥¹ï¹êÅ礤¥\¯à¤£·P¿³½ìªº³æ¦ì©Ò¨Ï¥Îªº)¡C¥t¥~¤@¤ä¥s°µ -CURRENT ¡A±q
- 2.0 ª©µo¦æ¥H«á´N¤£¶¡Â_¦a´ÂµÛ 5.0-RELEASE (¥H¤Î¥H«áªºª©¥») «e¶i
- µÛ¡C¤U±´N¬Oª©¥»ºt¶iªº¥Ü·N¹Ï¡G
+ ¤À¦¨¨â¤ä¡C¤@¤ä¥s°µ -STABLE
+ ¡A§ÚÌ¥u¹ï¥¦°µ¿ù»~×¥¿¤Î¤p´T«×ªº×§ï (³o¬Oµ¹ ISP ©M°Ó·~¤½¥qµ¥¡A¹ï¹êÅ礤¥\¯à¤£·P¿³½ìªº³æ¦ì©Ò¨Ï¥Îªº)¡C
+ ¥t¥~¤@¤ä¥s°µ -CURRENT ¡A±q
+ 2.0 ª©µo¦æ¥H«á¡A´N¤£Â_¦a´ÂµÛ 6.0-RELEASE (§t«áÄòªºª©¥»)«e¶iµÛ¡C
+
+ 6-STABLE ¤À¤ä¬O±q 6.0-RELEASE ¶}©l(5-STABLE ¤À¤äºâ¬O 5.3-RELEASE ¤§«á¤~¶}©lªº)¡A
+ µM«á쥻ªº &os.current; ´N·|¦¨¬° 7-CURRENT¡C
+
+
+
+ ¤U±´N¬Oª©¥»ºt¶iªº¥Ü·N¹Ï¡G
2.0
|
|
| [2.1-STABLE]
*BRANCH* 2.0.5 -> 2.1 -> 2.1.5 -> 2.1.6 -> 2.1.7.1 [2.1-STABLE ends]
| (Mar 1997)
|
|
| [2.2-STABLE]
*BRANCH* 2.2.1 -> 2.2.2-RELEASE -> 2.2.5 -> 2.2.6 -> 2.2.7 -> 2.2.8 [end]
| (Mar 1997) (Oct 97) (Apr 98) (Jul 98) (Dec 98)
|
|
3.0-SNAPs (started Q1 1997)
|
|
3.0-RELEASE (Oct 1998)
|
| [3.0-STABLE]
*BRANCH* 3.1-RELEASE (Feb 1999) -> 3.2 -> 3.3 -> 3.4 -> 3.5 -> 3.5.1
| (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]
+ [7.0-CURRENT continues]
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
+ ¦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
- 4-STABLE ¬O¥Ø«e¥¿¦bµo®i¤¤ªº -STABLE ¤À¤ä¡C4-STABLE ªº³Ì·sªº¤@
- ¦¸µoªí¬O &rel.current.date; µo¦æªº &rel.current;-RELEASE¡C
+ 5-STABLE ¬O¥Ø«e¥¿¦bµo®i¤¤ªº -STABLE ¤À¤ä¡C5-STABLE ªº³Ì·sªº¤@
+ ¦¸µoªí¬O¦b &rel2.current.date; µo¦æªº &rel2.current;-RELEASE¡C
- 5-CURRENT ªº³oÓ¤À¤ä¥Ø«e¥¿¥H½wºCªº³t«× 5.0-RELEASE ¥H¤Î¤§«áªº
- ª©¥»ÁÚ¶i¤¤¡C¦pªG·Qnª¾¹D§ó¦hÃö©ó³oÓ¤À¤äªº¸ê°Tªº¸Ü¡A½Ð°Ñ¦Ò ¤°»ò¬O FreeBSD-CURRENT¡H¡C
+ 6-STABLE ¬O¥Ø«e¥¿¦bµo®i¤¤ªº -STABLE ¤À¤ä¡C6-STABLE ªº³Ì·sªº¤@
+ ¦¸µoªí¬O¦b &rel.current.date; µo¦æªº &rel.current;-RELEASE¡C
+
+ 7-CURRENT ³oÓ¤À¤ä¬O &os; ªº -CURRENT ¤À¤ä¡A¤´µM¤£Â_¦a¦bµo®i·í¤¤¡C
+ ¦pªG·Qnª¾¹D§ó¦hÃö©ó³oÓ¤À¤äªº¸ê°Tªº¸Ü¡A½Ð°Ñ¦Ò ¤°»ò¬O &os;-CURRENT¡H¡C
- ·sªº FreeBSD ±N©ó¤°»ò®ÉÔ±À¥X¡H
+ ¨C¦¸·sªº FreeBSD ±N©ó¤°»ò®ÉÔ±À¥X¡H
- ¤@¯ë¦Ó¨¥¡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
+ ¤@¯ë¦Ó¨¥¡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
- ¥§¡¦Ó¨¥¡A§Ų́C¥|Ó¤ëµo¦æ¤@¦¸ release¡C
+ ¦³Ãöµo¦æ±¡³øªº§ó¦h²Ó¸`³¡¤À(¥]¬A release ªº¦æµ{ªí¡B¶i«×)¡A³£¥i¦b FreeBSD ºô¯¸¤Wªº
+ µo¦æ±¡³ø ¤W±Àò±o¡C
- ¬°¤Fº¡¨¬¨º¨Ç»Ýn (©Î·Qn) ¨ë¿Eªº¨Ï¥ÎªÌ¡A¤W±¤w¸g»¡¹L§Ų́C¤Ñ
- ³£·|µo¦æ snapshots ª©¥i¨Ñ¨Ï¥Î¡C
+ ¬°¤Fº¡¨¬¨º¨Ç»Ýn (©Î·Qn) ·sÂA¨ë¿E·Pªº¨Ï¥ÎªÌ¡A
+ ¤W±(-CURRENTªº³¡¤À)¤w¸g´£¨ì§Ų́C¤Ñ³£·|µo¦æ snapshots ª©¥i¨Ñ¨Ï¥Î¡C
½Öt³d FreeBSD ªºµo®i¡H
¦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©Ò²Õ¦¨ªº core
- team ¨Ó¨M©w¡C¦Ó¦³¥t¤@¸s¶W¹L 200 Ó¤Hªº
+ ¤H©Ò²Õ¦¨ªº core
+ team ¨Ó¨M©w¡C¦Ó¦³¥t¤@¸s¶W¹L 300 Ó¤Hªº
commiters ¦³Åv§Q¥i¥Hª½±µ×§ï FreeBSD ªº source tree¡C
µL½×¦p¦ó¡A¤j¦h¼Æªº§ïÅܳ£·|¨Æ«e¦b
- mailing lists ¥ý°Q½×¹L¡A¦Ó¥B¨CÓ¤H³£¥i¥H°Ñ»P°Q½×¡C
+ mailing lists ¥ý°Q½×¹L¡A¦Ó¥B¤£¤À¨¤¦â¡A¨CÓ¤H³£¥i¥H°Ñ»P°Q½×¡C
§Ún¦p¦ó¨ú±o FreeBSD¡H
¨CÓ FreeBSD ªº«nª©¥»³£¥i¥H¸g¥Ñ°Î¦W ftp ±q FreeBSD FTP site
- ¨ú±o¡G
+ url="ftp://ftp.FreeBSD.org/pub/FreeBSD/">FreeBSD FTP ¯¸¨ú±o¡G
-
-
- ¦pªGnªº¬O 3.X-STABLE ªº³Ì·sª©¡A¤]´N¬O 3.5.1-RELEASE¡A½Ð¨ì
- 3.5.1-RELEASE ³oӥؿý¡C
-
+
+
+ ¦pªG»Ýn 6-STABLE ªº³Ì·sª©¡A¤]´N¬O &rel.current;-RELEASE¡A½Ð¨ì &rel.current;-RELEASE ³oӥؿý
+
-
- ¦pªGnªº¬O 4-STABLE ªº³Ì·sª©¡A¤]´N¬O &rel.current;-RELEASE
- ¡A½Ð¨ì &rel.current;-RELEASE ³oӥؿý
-
+
+ 7-CURRENT Snapshot
+ ³q±`¤]¬O¨C¤Ñ³£·|°µ¤@¥÷¡A³o¬O±q -CURRENT ¤À¤ä°µ¥X¨Óªº¡A
+ ¥Dn¬O¬°¤F´£¨Ñµ¹¨º¨Ç¼ö¤ßªº´ú¸ÕªÌ©M¶}µo¤Hû¡C
+
-
- 4.X
- snapshots ³q±`¨C¤Ñ³£·|°µ¤@¥÷¡C
-
+
+ ¦pªG»Ýn 5-STABLE ªº³Ì·sª©¡A¤]´N¬O &rel2.current;-RELEASE¡A½Ð¨ì &rel2.current;-RELEASE ³oӥؿý
+
-
-
- 5.0 Snapshot ³q±`¤]¬O¨C¤Ñ³£·|°µ¤@¥÷¡A³o¬O±q -CURRENT ¤À¤ä°µ¥X¨Óªº¡A¥Dn¬O¬°¤FªA
- °È¨º¨Ç¼ö¤ßªº´ú¸ÕªÌ©M¶}µo¤Hû©Ò´£¨Ñªº¡C
-
+
+ ¦pªG»Ýn 4-STABLE ªº³Ì·sª©¡A¤]´N¬O 4.11-RELEASE¡A½Ð¨ì 4.11-RELEASE ³oӥؿý
+
+
+
+ 4.X¡B5.X¡B6X snapshots
+ ³q±`¨C¤Ñ³£·|°µ¤@¥÷¡C
+
- FreeBSD ªº CD¡ADVD¡AÁÙ¦³¤@¨Ç¨ä¥LªºªF¦èªº¨ú±oªk¥i¥H¦b ¨Ï¥Î¤â¥U ¤¤§ä¨ì¸Ñµª¡C
+ FreeBSD ªº CD¡BDVD¡AÁÙ¦³¨ä¥L¨ú±o¤è¦¡¥i¥H¦b ¨Ï¥Î¤â¥U ¤¤§ä¨ì¸Ñµª¡C
+
+
+ «ç»ò«Ø¥ß FreeBSD ªº¬M®g(mirror)¯¸¥x¡H
+
+
+
+ ¦³Ãö¦p¦ó«Ø¥ß FreeBSD ¬M®g¯¸(mirror)ªº¸ê®Æ¡A¥i¥H°Ñ¦Ò Mirroring FreeBSD ¤å³¹
+
+
+
- §Ún¦p¦ó¥h¦s¨ú¿ù»~¦^³ø¸ê®Æ®w©O¡H
+ §Ún¦p¦ó¥h¬d¸ß¡B´£¥æ°ÝÃD¦^³ø(Problem Report)¸ê®Æ®w©O¡H
- ©Ò¦³¨Ï¥ÎªÌªºÅܧón¨D³£¥i¥H¸g¥Ñ§Ú̺ô¶¤¶±ªº PR submission ¤Î
+ ©Ò¦³¨Ï¥ÎªÌªºÅܧón¨D³£¥i¥H¸g¥Ñºô¶¤¶±ªº PR
- query ¨Ó¬d¸ß (©Î¬O¦^³ø) §Ú̪º¿ù»~¦^³ø¸ê®Æ®w¡C¤]¥i¥H§Q¥Î
- &man.send-pr.1; ³oÓ«ü¥O³z¹L¹q¤l¶l¥ó¨Ó¦^³ø¿ù»~©Î¬On¨DÅܧó¡C
+ ¬d¸ß¤¶± ¨Ó¹î¬Ý (©Î¬O¦^³ø) §Ú̪º¿ù»~¦^³ø¸ê®Æ®w¡C
+
+ ¤]¥i¥H¨Ï¥Î &man.send-pr.1; ³oÓ«ü¥O³z¹L¹q¤l¶l¥ó¨Ó¦^³ø°ÝÃD¡Bn¨DÅܧó¡C
+ ©ÎªÌ¬O¸g¥Ñ ºô¶¤¶±ªº PR ¨Ó°e¥X°ÝÃD¦^³ø¡C
- ¦b¦^³ø¿ù»~¤§«e¡A½Ð¥ýŪ¹L ¦p¦ó¼¶¼g
- FreeBSD ªº¿ù»~¦^³ø³æ ¡A³o¬O¤@½g§i¶D§A«ç¼Ë¤~¯à¼g¥X¤@½g¦³¥Îªº
- ¿ù»~¦^³ø³æ¡C
+ µM¦Ó¡A¦b±z¦^³ø°ÝÃD¤§«e¡A½Ð¥ý¾\Ū ¦p¦ó¼¶¼g
+ FreeBSD ªº°ÝÃD¦^³ø³æ ¡A³o¬O¤@½g§i¶D§A«ç¼Ë¤~¯à¼g¥X¤@½g¯u¥¿¦³¥Îªº
+ °ÝÃD¦^³ø³æ¡C
- n«ç¼Ë¤~¯à¦¨¬° FreeBSD ªººô¶¬M®g¯¸¥x¡H
+ n«ç¼Ë¤~¯à¦¨¬° FreeBSD ªººô¶¬M®g(mirror)¯¸¥x¡H
- ¦³«Ü¦h¤èªk¥i¥H¬M®g§Ú̪ººô¶¡C
+ ¦³«Ü¦h¤èªk¥i¥H¬M®g(mirror)§Ú̪ººô¶¡C
±z¥i¥H§Q¥Î net/cvsup
±q cvsup.FreeBSD.org ¨ú±o®æ¦¡¤Æ¹LªºÀɮסC
- /usr/share/examples/cvsup/www-supfile ´N
- ¬O¤@ӱЧA«ç¼Ë°µºô¶¬M®gªº CVSup ³]©w½d¨Ò¡C
+ /usr/share/examples/cvsup/www-supfile
+ ³oÀÉ´N¬O¤@ӱЧA«ç¼Ë°µºô¶¬M®gªº CVSup ³]©w½d¨Ò¡C
±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 ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/www ¶}©l§ì¨ú¡C
+ url="ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/www"> ¶}©l§ì¨ú¡C
¦³¨ä¥Lªº¸ê°T¨Ó·½¶Ü¡H
¸Ô¨£ FreeBSD ºô¯¸¤Wªº ¤å¥ó ¦Cªí¡C
- Documentation and Support
+
+
+ Chin-San
+ Huang
+
+ chinsan.tw@gmail.com
+
+
+
+
+ ¤å¥ó»P¤ä´©
- What good books are there about FreeBSD?
+ Ãö©ó FreeBSD ¦³þ¨Ç¦n®Ñ¥i¥H±ÀÂ˾\Ūªº¶Ü¡H
- The project produces a wide range of documentation, available
- from this link:
- http://www.FreeBSD.org/docs.html .
+ FreeBSD ¤å¥ópµe¤w³°Äòµoªí¤F¬Û·í¼sªx½d³òªº¤å¥ó¡A¥i¦b ¨ú±o¡C¥t¥~¡A
+ FreeBSD ¥»¨ªº manual(¤@¯ë³qºÙªºman)¡Bdoc¤]¦p¦P®M¥ó³nÅé¤@¼Ë¡A¥i¥H»´ÃP¦a¸Ë¦b±z¨t²Î¤W¡C
+
- In addition, the Bibliography at the end of this FAQ, and the
- one in the Handbook reference other recommended books.
+ ¦¹¥~¡A¤]«Øij°Ñ¾\¥»¥÷ FAQ ³Ì«á©Ò¦Cªº°Ñ¦Ò®Ñ¥Øªí(Bibliography)»P? FreeBSD ¨Ï¥Î¤â¥U?¡C
+
- Is the documentation available in other formats, such as plain
- text (ASCII), or Postscript?
+ ³o¨Ç¤å¥ó¦³¨ä¥L®æ¦¡ªº¶Ü¡H¹³¬O¡G¯Â¤å¦r(ASCII)©Î &postscript; ¤§Ãþªº®æ¦¡¡H
- Yes. The documentation is available in a number of
- different formats and compression schemes on the FreeBSD
- FTP site, in the /pub/FreeBSD/doc/
- directory.
+ ¦³ªº¡C³o¨Ç¤å¥ó³£¤À§O¥H¤£¦P®æ¦¡Àx¦s¥H¤ÎÀ£ÁY³B²z¡A©ñ¦b
+ FTP ¤W±¡A¥i¥H±q¦U FreeBSD FTP ¯¸ªº /pub/FreeBSD/doc/
+ ¥Ø¿ý¤º§ä¨ì§Anªº¡C
- The documentation is categorized in a number of different
- ways. These include:
+ ¤å¥óªº¤ÀÃþ¤è±¥Dn¬O¤@¨Ç¤£¦P©Ê½è©Ò²Õ¦¨¡G
- The document's name, such as faq , or
- handbook .
+ ¤å¥ó¦WºÙ¡A¤ñ¦p¡Gfaq(±`¨£°Ýµª¶°) ©Î¬O
+ handbook(FreeBSD ¨Ï¥Î¤â¥U) µ¥µ¥¡C
- The document's language and encoding. These are based on
- the locale names you will find under
- /usr/share/locale on your FreeBSD
- system. The current languages and encodings that we have for
- documentation are as follows:
+ ¦U°ê½Ķªºªº¤å¥ó¡G³o¥Dn¬O¥Ñ locale ¦WºÙ¨Ó¨M©wªº
+ (¤£²M·¡ªº¸Ü¡A¥i°Ñ¦Ò±zªº FreeBSD §@·~¨t²Î¤Wªº /usr/share/locale )
+ ¥Ø«e¤å¥óÁ`¦@¦³¤U¦C´XºØ»y¨¥(¤Î½s½X)¦³Â½Ä¶¡G
-
+
- Name
+ Locale ¦WºÙ
- Meaning
+ »¡©ú(©Ò¥Nªíªº»y¨t¡B½s½X)
en_US.ISO8859-1
- US English
+ ¬ü¦¡^¤å(US English)
de_DE.ISO8859-1
- German
+ ¼w¤å(German)
es_ES.ISO8859-1
- Spanish
+ ¦è¯Z¤ú¤å(Spanish)
fr_FR.ISO8859-1
- French
+ ªk¤å(French)
+
+ it_IT.ISO8859-15
+
+ ¸q¤j§Q¤å(Italian)
+
+
ja_JP.eucJP
- Japanese (EUC encoding)
+ ¤é¤å(Japanese¡A½s½X¤è¦¡¡GEUC)
ru_RU.KOI8-R
- Russian (KOI8-R encoding)
+ «X¤å(Russian¡A½s½X¤è¦¡¡GKOI8-R)
zh_TW.Big5
- Chinese (Big5 encoding)
+ ¥¿Å餤¤å(Chinese¡A½s½X¤è¦¡¡GBig5)
- Some documents may not be available in all
- languages.
+ ¤W¦Cªº¦U°ê½Ķ»y¨t¤å¥ó¤¤¡A¨Ã«D©Ò¦³¤å¥ó³£¦³Â½Ä¶¡C
- 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:
-
-
+ ¤å¥óªº®æ¦¡¡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:
+
+
- Format
+ ®æ¦¡
- Meaning
+ »¡©ú
html-split
- A collection of small, linked, HTML
- files.
+ ³¹¸`¼Ò¦¡
html
- One large HTML file containing the entire
- document
+ §¹¾ã¼Ò¦¡
pdb
- Palm Pilot database format, for use with the
- iSilo
- reader.
+ Palm Pilot ¸ê®Æ®æ¦¡¡A¨Ï¥Î
+ iSilo
+ µ{¦¡¨Ó¾\Ū
pdf
- Adobe's Portable Document Format
+ Adobe's PDF ®æ¦¡
ps
- Postscript
+ &postscript; ®æ¦¡
rtf
- Microsoft's Rich Text Format
- Page numbers are not automatically updated
- when loading this format in to Word. Press
- CTRL A ,
- CTRL END ,
- F9 after loading the document, to
- update the page numbers.
+ Microsoft's RTF®æ¦¡
+ ·í¨Ï¥Î MS Word ¨Ó¶}±Ò RTF ®æ¦¡ªº¸Ü¡A¶¼ÆÅã¥Ü¨Ã¤£·|¦Û°Ê§ó·s¡C
+ (¦b¶}±Ò¤å¥ó«á¡An«ö CTRL A ,
+ CTRL END ,
+ F9 ¡A³o¼Ë¤l¤~·|§ó·s¶¼ÆªºÅã¥Ü¡C)
txt
- Plain text
+ ¯Â¤å¦r(ASCII)
- The compression and packaging scheme. There are three of
- these currently in use.
+ ¤å¥óªºÀ£ÁY¡B¥´¥]¤è¦¡¡G¥Ø«e¦³¤TºØ¤è¦¡¡G
- Where the format is html-split , the
- files are bundled up using &man.tar.1;. The resulting
- .tar file is then compressed using
- the compression schemes detailed in the next point.
+ ·í±Ä¥Î
+ ³¹¸`¼Ò¦¡(html-split) ¡A³¹¸`¼Ò¦¡©Ò²£¥Íªº¦UÀÉ®×·|¥ý¨Ï¥Î
+ &man.tar.1; ¨ÓÀ£ÁY¡CÀɦWµ²§À¦³ .tar ªºÀÉ®×´N¬O tar ®æ¦¡¡C
+ ±µµÛ¡A·|¦A¥H¤U¦C¤è¦¡¦AÀ£ÁY¡C
+
- All the other formats generate one file, called
- book.format
- (i.e., book.pdb ,
- book.html , and so on).
+ ¨ä¥L®æ¦¡ªºÀɮ׳£·|¬O³æ¤@ÀɮסAÀɦW³q±`·|¬O¡G
+ book.®æ¦¡
+ (Á|¨Ò¡G book.pdb ¡A
+ book.html µ¥µ¥..«á±³q±`¥[¤W¡y.®æ¦¡¡z).
+ ¦Ó³o¨ÇÀÉ®×·|¤À§O¥H¨âºØÀ£ÁY«¬ºA¶i¦æÀ£ÁY¡A¦Ó¦s¦¨¨âºØÀ£ÁY«¬ºA¡C
- These files are then compressed using three
- compression schemes.
-
-
+
- Scheme
+ ®æ¦¡
- Description
+ »¡©ú
zip
- The Zip format. If you want to uncompress
- this on FreeBSD you will need to install the
- archivers/unzip port
- first.
-
-
-
- gz
-
- The GNU Zip format. Use &man.gunzip.1; to
- uncompress these files, which is part of
- FreeBSD.
+ Zip ®æ¦¡¡AYn¦b FreeBSD ¤W¸ÑÀ£ zip ÀÉ¡A«h¥²¶·¥ý¦w¸Ë
+ chinese/unzip ©Î
+ archivers/unzip ¡C
+
bz2
- The BZip2 format. Less widespread than the
- others, but generally gives smaller files.
- Install the archivers/bzip2
- port to uncompress these files.
+ BZip2 ®æ¦¡¡AÁöµM¤£¦p zip ®æ¦¡ªº¼sªx¨Ï¥Î¡A¦ý¬O¦n³B¦b©ó¥iÀ£ÁY¦¨§ó¤pªºÀɮסC
+ n¸ÑÀ£ bz2 ®æ¦¡ªº¸Ü¡A»Ý¥ý¦w¸Ë archivers/bzip2
+ ¡C
- So the Postscript version of the Handbook, compressed
- using BZip2 will be stored in a file called
- book.ps.bz2 in the
- handbook/ directory.
-
-
-
- The formatted documentation is also available as a
- FreeBSD package, of which more later.
+ ©Ò¥H¹³¬O Handbook ªº &postscript; ª©®æ¦¡¡A·|¥H BZip2 ®æ¦¡À£ÁY¡A
+ ¦s©ñ¦b handbook/ ¥Ø¿ý¤º¡A
+ ÀɦW´N¬Obook.ps.bz2 ¡C
- 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
- package .
+ ¿ï¾Ü·Qn¤U¸üªº¤å¥ó®æ¦¡»PÀ£ÁY«¬ºA¤§«á¡A«hn¨M©w¬O§_¥H FreeBSD ®M¥ó(package)
+ «¬ºA¨Ó¤U¸ü¡C
- 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;.
+ ¤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
- 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
- packages . Each package file looks like
- document-name .lang .encoding .format .tgz .
- For example, the FAQ, in English, formatted as PDF, is in the
- package called
- faq.en_US.ISO8859-1.pdf.tgz .
+ Y¨M©w¦nn¤U¸ü¡B¦w¸Ë¡ypackage¡zªº¸Ü¡A¥²¶·n½T»{©Òn¤U¸üªºÀɦW¡C
+ ¤å¥ópµeªº®M¥ó(package)³q±`¬O©ñ¦b¬O packages ªº¥Ø¿ý¤º¡A
+ ¨CÓ¤å¥ópµeªº®M¥óÀɦW³q±`¬O¡G
+ ¤å¥ó¦WºÙ .»y¨t .½s½X .®æ¦¡ .tgz
+ ¡C
+
+ Á|Ó¨Ò¤l¡A^¤åª©ªº FAQ (®æ¦¡¿ï¾Ü PDF)¦b package ´N¥s°µ
+ faq.en_US.ISO8859-1.pdf.tgz ¡C
- Knowing this, you can use the following command to install the
- English PDF FAQ package.
+ ¦AÁ|Ó¨Ò¤l¡A¤¤¤åª©ªº FAQ (®æ¦¡¿ï¾Ü PDF)¦b package ´N¥s°µ
+ faq.zh_TW.Big5.pdf.tgz ¡C
- &prompt.root; pkg_add ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/packages/faq.en_US.ISO8859-1.pdf.tgz
+ ª¾¹D³oÂI¤§«á¡A´N¥i¥H¥Î¤U±«ü¥O¨Ó¦w¸Ë¤¤¤åª© FAQ ®M¥ó¡G
- Having done that, you can use &man.pkg.info.1; to determine
- where the file has been installed.
+ &prompt.root; pkg_add ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/packages/faq.zh_TW.Big5.pdf.tgz
- &prompt.root; pkg_info -f faq.en_US.ISO8859-1.pdf
-Information for faq.en_US.ISO8859-1.pdf:
+ §¹¦¨¤§«á¡A¥i¥H¥Î &man.pkg.info.1; ¨Ó§ä¥XÀɮ׸˦bþÃä¡G
+
+ &prompt.root; pkg_info -f faq.zh_TW.Big5.pdf
+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)
- As you can see, book.pdf will have been
- installed in to
- /usr/share/doc/en_US.ISO8859-1/books/faq .
-
+ ¦p¦P±z©Ò¬Ý¨ìªº book.pdf ·|³Q¦w¸Ë¨ì
+ /usr/share/doc/zh_TW.Big5/books/faq ¤º¡C
- 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.
+ Y¤£·Q¥Î package ¤è¦¡¦w¸Ë¡A¨º»ò´N»Ý¤â°Ê¤U¸ü¡B¸ÑÀ£ÁY¡B½Æ»s¨ì§A·QnÂ\©ñªº¦ì¸m¥h¡C
- For example, the split HTML version of the FAQ, compressed
- using &man.gzip.1;, can be found in the
- doc/en_US.ISO8859-1/books/faq/book.html-split.tar.gz
- file. To download and uncompress that file you would have to do
- this.
+ Á|¨Ò¡A³¹¸`¼Ò¦¡(split HTML)ª©ªº^¤å FAQ (À£ÁY¬° &man.bzip2.1;)·|©ñ¦b
+ doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2
+ n¤U¸ü¡B¸ÑÀ£ªº¸Ü¡A«hn¥´¡G
- &prompt.root; fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/faq/book.html-split.tar.gz
-&prompt.root; gzip -d book.html-split.tar.gz
+ &prompt.root; fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2
+&prompt.root; bzip2 -d book.html-split.tar.bz2
&prompt.root; tar xvf book.html-split.tar
- You will be left with a collection of
- .html files. The main one is called
- index.html , 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.
+ ³o®É§A·|¬Ý¨ì¤@°ï .html ªºÀɮסA
+ ¥Dnªº¥Ø¿ýÀɬ° index.html
+ ¤º§t¥D¥Ø¿ý¤Î³sµ²¨ì¨ä¥L¤å¥ó¡C(Y¦³»Ýnªº¸Ü¡A¤]¥i¥H½Æ»s©Î·h²¾³o¨ÇÀɮרì¦P¤@¥Ø¿ý¤U)
- Where do I find info on the FreeBSD mailing lists?
+ þ¸Ì¦³Ãö©ó FreeBSD ªº¶l»¼½×¾Â(mailing lists)©O¡H
- You can find full information in the Handbook
- entry on mailing-lists .
+ ³oÓ°ÝÃD¡A¥i¥H±q? FreeBSD ¨Ï¥Î¤â¥U?¤W±ªº ¶l»¼½×¾Â(mailing-lists)
+ ³¡¤ÀÀò±oµª®×¡C
- Where do I find the FreeBSD Y2K info?
+ §Ú¸Ó±qþÃä±o¨ì¦³Ãö FreeBSD ¦b¤dÁHÂÎ(Y2K)¤è±ªº¸ê®Æ©O?
- You can find full information in the FreeBSD Y2K
- page .
+ ³oµª®×¥i¥H¦b FreeBSD ¤dÁHÂÎ(Y2K) ¤W±Àò±o
- What FreeBSD news groups are available?
+ ¦³þ¨Ç¥i¥H¨Ï¥Îªº FreeBSD ·s»D¸s²Õ(news groups)©O?
- You can find full information in the Handbook entry on
- newsgroups .
+ ³oµª®×¥i¥H±q? FreeBSD ¨Ï¥Î¤â¥U?¤W±ªº ·s»D¸s²Õ(newsgroups)
+ ³¡¤ÀÀò±oµª®×¡C
- Are there FreeBSD IRC (Internet Relay Chat)
- channels?
+ ¦³þ¨Ç FreeBSD IRC (Internet Relay Chat)ÀW¹D©O¡H
- Yes, most major IRC networks host a FreeBSD chat
- channel:
+ ¦³ªº¡A¤j³¡¤Àªº IRC ¥D¾÷³£¦³ FreeBSD ²á¤ÑÀW¹D¡G
Channel #FreeBSD on
- EFNet
+ EFNet
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!
Available at server irc.chat.org .
Channel #FreeBSDhelp on
- EFNet
+ EFNet
is a channel dedicated to helping FreeBSD users. They
- are much more sympathetic to questions then
+ are much more sympathetic to questions than
#FreeBSD is.
Channel #FreeBSD on
- DALNET
+ DALNET
is available at irc.dal.net in the
US and irc.eu.dal.net in Europe.
+
+ Channel #FreeBSDHelp on
+ DALNET
+ is available at irc.dal.net in the
+ US and irc.eu.dal.net in Europe.
+ The channel owners also have a web page with useful
+ information about the channel and &os;, available at
+ .
+
+
Channel #FreeBSD on
- UNDERNET
+ UNDERNET
is available at us.undernet.org
in the US and eu.undernet.org in Europe.
Since it is a help channel, be prepared to read the
documents you are referred to.
-
-
- Channel #FreeBSD on HybNet . This channel
- is a help channel. A list of servers
- can be found on the HybNet web site .
-
Each of these channels are distinct and are not
connected to each other. Their chat styles also differ,
so you may need to try each to find one suited to your
chat style. As with all types of IRC
traffic, if you are easily offended or cannot deal with
lots of young people (and more than a few older ones)
doing the verbal equivalent of jello wrestling, do not
even bother with it.
- Where can I get commercial FreeBSD training and support?
+ ¥i¥H±qþÃäÀò±o FreeBSD ªº°Ó·~½Òµ{°V½m¤Î§Þ³N¤ä´©©O¡H
- DaemonNews provides commercial training and support for
- FreeBSD. More information can be found at their
- BSD Mall
- site.
-
- FreeBSD Services Ltd provide commercial support for FreeBSD
- in the UK (as well as selling FreeBSD on DVD). See their
- web site
- for more information.
-
- The FreeBSD Mall provides commercial FreeBSD support.
- You can get more information at their web site .
-
- Any other organizations providing training and support should
- contact the project in order to be listed here.
+ DaemonNews ¦³±Mªù´£¨Ñ FreeBSD ªº°Ó·~½Òµ{°V½m¤Î§Þ³N¤ä´©¡C
+ ¸Ô±¡½Ð¨ì BSD Mall
+ ¹î¬Ý¡AÁÂÁ¡C
+
+ FreeBSD Mall ¦³´£¨Ñ°Ó·~¤Æªº BSD §Þ³N¤ä´©¡A
+ ¸Ô±¡½Ð¨ì FreeBSD Mall ¹î¬Ý¡AÁÂÁ¡C
+
+
+ ¨ä¥L¥ô¦ó¦³´£¨Ñ½Òµ{°V½m¤Î§Þ³N¤ä´©ªº²Õ´¡B³æ¦ì¡AY¤]·Q¦Cªí©ó¦¹ªº¸Ü¡A
+ ½Ð»P &a.doc; Ápµ¸¡AÁÂÁ¡C
Nik
Clayton
nik@FreeBSD.org
- Installation
+ ¦w¸Ë
- Which file do I download to get FreeBSD?
+ Yn¥Î³nºÐ¤ù¶}¾÷¨Ó¦w¸Ë FreeBSD ªº¸Ü¡An¤U¸üþ¨ÇÀɮשO¡H
- Prior to release 3.1, you only needed one floppy image to
- install FreeBSD, namely floppies/boot.flp .
- 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:
- floppies/kernel.flp and
- floppies/mfsroot.flp . These images need to
- be copied onto floppies by tools like
- fdimage or &man.dd.1;.
+ &os; 4.X ªº¸Ü¡A»Ýn¨âÓ image ÀÉ¡G
+ floppies/kernel.flp ¤Î
+ floppies/mfsroot.flp ¡Cimage ÀÉ¥²¶·¥Î¤u¨ã¹³¬O
+ fdimage ©Î &man.dd.1; ¨Ó¶Ç°e¨ìºÏ¤ù¤W¡C
+ Y¬O¦b &os; 5.3 (¤Î¤§«áª©¥»)¦³«·s³W¹º¶}¾÷¤ù¬[ºc¡A©Ò¥Hn§ìªº¬O
+ floppies/boot.flp ¥H¤Î floppies/kernX
+ ÀÉ®×(¥Ø«e X ¬° 1 ¸ò 2 ¨âÓ¡A¥[¤Wfloppies/boot.flp ¡AÁ`¦@¬O 3 ÓÀÉ®×)¡C
- If you need to download the distributions yourself (for a
- DOS filesystem install, for instance), below are some
- recommendations for distributions to grab:
+ Y·Q¦Û¤v¤U¸ü distributions ªº¸Ü(¤ñ¦p¥H &ms-dos; Àɮרt²Î®æ¦¡¦w¸Ë)¡A
+ ¥H¤U¬O«Øijn§ìªº distributions ¡G
- bin/
+ base/ (bin/ in 4.X)
manpages/
compat*/
doc/
src/ssys.*
- Full instructions on this procedure and a little bit more
- about installation issues in general can be found in the
- Handbook entry on
- installing FreeBSD .
+ §¹¾ã¦w¸Ë¨BÆJ¥H¤Î¤j³¡¤Àªº¦w¸Ë°ÝÃD¡A½Ð°Ñ¾\? FreeBSD ¨Ï¥Î¤â¥U?ªº
+ ¦w¸Ë FreeBSD ³¹¸`
- What do I do if the floppy images does not fit on a single
- floppy?
+ YºÏ¤ù¸Ë¤£¤U image Àɪº¸Ü¡A¸Ó«ç»ò¿ì©O¡H
- A 3.5 inch (1.44MB) floppy can accommodate 1474560 bytes
- of data. The boot image is exactly 1474560 bytes in size.
+ ¤@±i 3.5 ^¦T(1.44MB) ªººÏºÐ¤ù¬O¥i¥H¸Ë¤W 1474560 bytes ªº¸ê®Æ
+ ¡A¦Ó¶}¾÷¤ùªº image Àɮפj¤p¹ê»Ú¤W¤]¬O 1474560 bytes¡C
- Common mistakes when preparing the boot floppy are:
+ ¦b»s§@¶}¾÷¤ù®É¡A±`¨£¿ù»~¦³¡G
- Not downloading the floppy image in
- binary mode when using
- FTP .
-
-
- Some FTP clients default their transfer mode to
- ascii 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 exactly that
- on the server, then the download process is suspect.
-
- To workaround: type binary at the
- FTP command prompt after getting connected to the server
- and before starting the download of the image.
+ ¨Ï¥Î FTP ¨Ó¤U¸üÀɮ׮ɡA
+ ¥¼¿ï¾Ü binary ¶Ç¿é¼Ò¦¡¨Ó¤U¸ü¡C
+
+
+ ¦³¨Ç FTP clientºÝµ{¦¡¡A¬O¹w³]±N¶Ç¿é¼Ò¦¡³]©w¬°
+ ascii ¼Ò¦¡¡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±ªºÀÉ®× ¤£¤@P
+ ªº¸Ü¡A½Ð«·s¨Ï¥Î binary ¶Ç¿é¼Ò¦¡¤U¸ü§Y¥i¡C
+
+ FTP «ü¥O: ¶i¤J FTP ¤§«á¡A¥´ binary
+ «ü¥O¡A§Y¥i¤Á´«¨ì binary ¶Ç¿é¼Ò¦¡¡AµM«á¦A¤U¸ü¬ÛÃö image ÀɮסC
- Using the DOS copy command (or
- equivalent GUI tool) to transfer the boot image to
- floppy.
-
- Programs like copy 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
- raw
, using the low-level tools (e.g.
- fdimage or rawrite )
- described in the installation guide to
- FreeBSD .
+ ª½±µ¥Î &ms-dos; ªº copy «ü¥O(©ÎÃþ¦ü
+ ªº GUI µ{¦¡¡B©Î¬Oµøµ¡¤Wª½±µ½Æ»s)¨Ó½Æ»s¶}¾÷¥Îªº image ÀɨìºÏ¤ù¤W¡C
+
+
+ ¤£¥i¥H¥Î¹³¬O copy ³oÃþµ{¦¡ª½±µ±N image
+ Àɽƻs¨ìºÏ¤ù¤W¡A¦]¬° image ÀÉ¥»¨¥]§t¤F§¹¾ãªººÏy¸ê®Æ¡A©Ò¥H¤£¯à³æ¯Â¥Î½Æ»s¤è¦¡¡A
+ ¦Ó¥²¶·¨Ï¥Î§C¶¥¤u¨ãµ{¦¡(¹³¬O fdimage ©Î rawrite )¡A
+ ¥H raw
¤è¦¡¶Ç°e¨ìºÏ¤ù¤W¡C(³o³¡¤À¥i°Ñ¾\? FreeBSD ¨Ï¥Î¤â¥U?¤Wªº ¦w¸Ë FreeBSD )
- Where are the instructions for installing FreeBSD?
+ ¥i¥H¦bþÃä§ä¨ì¦w¸Ë FreeBSD ªº¸Ñ»¡¨BÆJ©O¡H
- Installation instructions can be found in the
- Handbook entry on installing FreeBSD .
+ ¦w¸Ë¨BÆJªº¸Ñ»¡¡A½Ð°Ñ¾\? FreeBSD ¨Ï¥Î¤â¥U?¤Wªº
+ ¦w¸Ë FreeBSD ³¹¸`³¡¤À¡C
- What do I need in order to run FreeBSD?
+ n¶] FreeBSD »Ýn¤°»òªº°t³Æ©O¡H
- 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.
+ &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
+
+ ±q &os; 5.X °_¡AµwÅé»Ý¨D¬° 486 ©Î§ó°ª¯Åªº PC
+ ¡A°O¾ÐÅé(RAM)¦Ü¤Ön 24 MB ©Î§ó¦h¡AµwºÐªÅ¶¡¦Ü¤Ön 150 MB ©Î§ó¦h¡C
+
+
+ &os; ªº©Ò¦³ª©¥»³£¥i¥H¥u¥Î§C¶¥ªº MDA ³W®æÅã¥Ü¥d¡A¤£¹L?n¶] X11R6 µøµ¡ªº¸Ü¡A
+ ÁÙ¬O¦Ü¤Ö¥Î VGA ©Î§ó¦n³W®æªºÅã¥Ü¥d¨Ó¥Î§a¡C
- See also
-
+ ³o³¡¤À¤]¥i°Ñ¾\ ¡C
- I have only 4 MB of RAM. Can I install FreeBSD?
+ §Ú¹q¸£ RAM ¥u¦³ 4MB ¦Ó¤w¡A¥i¥H¸Ë FreeBSD ¶Ü¡H
- 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.
+ ¦w¸Ë &os; 4.X ªº°O¾ÐÅé»Ý¨D¬°¦Ü¤Ö 5 MB ¡A¦Ó
+ ¦w¸Ë &os; 5.X (§t¤§«áª©¥») «h¬O¦Ü¤Ön 8 MB ¡C
- All versions of FreeBSD will run
- 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.
+ ¦b 5.X ¤§«eªº©Ò¦³ &os; ª©¥»¡A³£¥i¥H¥u¥Î 4 MB ªº°O¾ÐÅé¨Ó
+ ¡y¹B§@¡z ¡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
- FreeBSD 2.1.7 will not install with 640 kB base + 3 MB
- extended memory. If your motherboard can remap some of the
- lost
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
- remap
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 upgrade
option of the 2.1.7
- installation program.
-
- 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.
+ ¦¹¥~¡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..)
- How can I make my own custom install floppy?
+ n«ç¼Ë¤~¯à¦Û¦æ¥´³y±M¥Îªº¶}¾÷¡B¦w¸ËºÏ¤ù©O¡H
- Currently there is no way to just
- make a custom install floppy. You have to cut a whole new
- release, which will include your install floppy.
+ ¥Ø«e¡AÁÙ¨S¦³¿ìªk¡y¥u¡z ¦Û»s±M¥Îªº¶}¾÷¡B¦w¸ËºÏ¤ù¡C
+ ¥²¶·³z¹L¦Û¦æ¥´³y§¹¾ã§@·~¨t²Îªº release(µo¦æ)¡A³o¼Ë¸Ì±¤~·|¥]¬A¦Û¤vªº¶}¾÷¡B¦w¸ËºÏ¤ù¡C
- To make a custom release, follow the instructions in the
- Release
- Engineering article.
+ Y·Q¦Û¦æ¥´³y¡Bµo¦æ(release)¤@Ó§¹¾ãªº§@·~¨t²Î¡A½Ð°Ñ¾\³o½g
+ Release Engineering ¤å³¹¡C
- Can I have more than one operating system on my PC?
+ §Ú¹q¸£¤W¥i¥H¦³¦h«§@·~¨t²Î¶Ü¡H
- Have a look at
-
- the multi-OS page .
+ ¥i¥H§r¡A½Ð°Ñ¾\
+
+ ¦h«§@·~¨t²Î ³o½g¤å³¹¡C
- Can Windows 95/98 co-exist with FreeBSD?
+ &windows; ¥i¥H»P FreeBSD ¦@¦s©ó¹q¸£¤W¶Ü¡H
- 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.
+ ¥ý¸Ë &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
- Windows 95/98 killed my boot manager!
- How do I get it back?
+ ¶ã??&windows; §â§Úªº¶}¾÷ºÞ²zû(boot manager)®³±¼¤F¡I§Ún«ç»ò±Ï¦^¨Ó©O¡H
- You can reinstall the boot manager FreeBSD comes with in
- one of three ways:
+ ¥i¥H¥Î¥H¤U¤TºØ¤è¦¡¤§¤@¡A¨Ó±Ï¦^§Aªº FreeBSD ¶}¾÷ºÞ²zû(boot manager)¡G
- Running DOS, go into the tools/ directory of your
- FreeBSD distribution and look for
- bootinst.exe . You run it like
- so:
+ ¥i¥H±q¦U FreeBSD FTP ¯¸ªº /pub/FreeBSD/tools/
+ §ä¨ì bootinst.exe ¤Î boot.bin ³o¨âÓÀÉ¡A
+ ¥H binary ¶Ç¿é¼Ò¦¡¤U¸ü«á¡A½Æ»s¨ìºÏ¤ù¤W¡A¦A¥Î DOS ¶}¾÷¤ù¶}¾÷¡A
+ ±µµÛ¥´Ãþ¦ü¤U±ªº«ü¥O¡G
- ...\TOOLS> bootinst.exe boot.bin
+ > bootinst.exe boot.bin
- and the boot manager will be reinstalled.
+ ³o¼Ë¶}¾÷ºÞ²zû(boot manager)´N·|«¸Ë§¹²¦¤F¡C
- 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 Boot Manager
. This will
- re-write the boot manager to disk. Now quit out of the
- installation menu and reboot off the hard disk as
- normal.
+ ¥Î 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¿ï Boot Manager
¡A³o¼Ë´N·|«·s±N¶}¾÷ºÞ²zû(boot manager)
+ ¦w¸Ë¨ìµwºÐ¤W¡C²{¦b¡A´N¤j¥\§i¦¨¥i¥HÂ÷¶}¦w¸Ë¿ï³æ¨Ã«¶}¾÷¤F¡C
- Boot the FreeBSD boot floppy (or CDROM) and choose the
- Fixit
menu item. Select either the Fixit
- floppy or CDROM #2 (the live
file system
- option) as appropriate and enter the fixit shell. Then
- execute the following command:
+ ¥Î FreeBSD ¶}¾÷¤ù©Î¬O¶}¾÷¥úºÐ¶}¾÷¡AµM«á¿ï³æ¨ºÃä¿ï Fixit
+ ¡A©Î¬O¥H Fixit ¶}¾÷¤ù©Î¬O¥úºÐ¦w¸Ëªº²Ä¤G¤ù(¿ï¾Ü live
filesystem
+ ¿ï¶µ)µM«á´N·|¶i¤J fixit shell ¤F¡A±µµÛ¥´¤U¦C«ü¥O¡G
Fixit# fdisk -B -b /boot/boot0 bootdevice
- substituting bootdevice for
- your real
- boot device such as ad0 (first IDE
- disk), ad4 (first IDE disk on
- auxiliary controller), da0 (first
- SCSI disk), etc.
+ ½Ð±N¤W±ªº bootdevice קאּ±z¹ê»Úªº¶}¾÷µwºÐ¥N¸¹
+ ¤ñ¦p ad0 (²Ä¤@Áû IDE µwºÐ)
+ ¡A©Î¬Oad4 (first IDE disk on
+ auxiliary controller), da0 (²Ä¤@Áû
+ SCSI µwºÐ)µ¥µ¥?¡C
- My A, T, or X series IBM Thinkpad locks up when I first
- booted up my FreeBSD installation. How can I solve this?
+ ·í¸Ë§¹ FreeBSD ¤§«á«¶}¾÷¡A§Úªº IBM Thinkpad A¨t¦C¡BT¨t¦C©Î X¨t¦Cªºµ§°O«¬¹q¸£´Nw¤F¡A¸Ó«ç»ò¿ì©O¡H
- 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.
+ ³o¨Ç IBM ¾÷¾¹¤Wªº BIOS ¦´Áª©¥»¦³Ó¯äÂÎ(bug)·|§â FreeBSD ¤À³Î°Ï»~»{¬°
+ FAT ®æ¦¡¤À³Î°Ï¡AµM«á·í BIOS ¸ÕµÛ°»´ú FreeBSD ¤À³Î°Ï®É¡A´N·|w¤F¡C
- According to IBMIn an e-mail from Keith
- Frechette
- kfrechet@us.ibm.com . , the
- following model/BIOS release numbers incorporate the fix.
+ ®Ú¾Ú IBM ¤è±ªº»¡ªk¤@«Ê¨Ó¦Û Keith
+ Frechette ªº e-mail kfrechet@us.ibm.com ¡C
+ ¡A¥H¤U«¬¸¹/BIOSª©¥»ªº¾÷ºØ¡A¤w¸g³£¦³×¥¿¡G
-
+
- Model
- BIOS revision
+ «¬¸¹
+ BIOS ª©¥»
T20
- IYET49WW or later
+ IYET49WW(§t¤§«á)
T21
- KZET22WW or later
+ KZET22WW(§t¤§«á)
A20p
- IVET62WW or later
+ IVET62WW(§t¤§«á)
A20m
- IWET54WW or later
+ IWET54WW(§t¤§«á)
A21p
- KYET27WW or later
+ KYET27WW(§t¤§«á)
A21m
- KXET24WW or later
+ KXET24WW(§t¤§«á)
A21e
KUET30WW
- It has been reported that later IBM BIOS revisions may have
- reintroduced the bug. This message
- 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..
+ It has been reported that later IBM BIOS revisions may
+ have reintroduced the bug. This
+ message 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.
- If you have an earlier BIOS, and upgrading is not an option a
+ 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.
First, you will need to restore the machine to a state where
it can get through its self-test screen. Doing this requires
powering up the machine without letting it find a FreeBSD
partition on its primary disk. One way is to remove the hard disk
and temporarily move it to an older ThinkPad (such as a ThinkPad
600) or a desktop PC with an appropriate conversion cable. Once
it is there, you can delete the FreeBSD partition and move the hard
disk back. The ThinkPad should now be in a bootable state
again.
With the machine functional again, you can use the workaround
procedure described here to get a working FreeBSD
installation.
Download boot1 and
boot2 from http://people.FreeBSD.org/~bmah/ThinkPad/ .
+ url="http://people.FreeBSD.org/~bmah/ThinkPad/">.
Put these files somewhere you will be able to retrieve them
later.
Install FreeBSD as normal on to the ThinkPad.
Do not use Dangerously
Dedicated mode. Do not
reboot when the install has finished.
Either switch to the Emergency Holographic
Shell
(ALT
F4 ) or start a
fixit
shell.
Use &man.fdisk.8; to change the FreeBSD partition ID from
165 to 166 (this is the
type used by OpenBSD).
Bring the boot1 and
boot2 files to the local
filesystem.
Use &man.disklabel.8; to write boot1
and boot2 to your FreeBSD slice.
&prompt.root; disklabel -B -b boot1 -s boot2 ad0sn
n is the number of the slice
where you installed FreeBSD.
Reboot. At the boot prompt you will be given the option
of booting OpenBSD . This will actually
boot FreeBSD.
Getting this to work in the case where you want to dual boot
OpenBSD and FreeBSD on the same laptop is left as an exercise for
the reader.
- Can I install on a disk with bad blocks?
-
-
-
- Prior to 3.0, FreeBSD included a utility known as
- bad144 , which automatically remapped bad
- blocks. Because modern IDE drives perform this function
- themselves, bad144 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.
- 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.
-
- If you have a SCSI drive with bad blocks, see
- this answer.
-
-
-
-
-
- I have just upgraded from 3.X to 4.X, and my first boot
- failed with bad sector table not
- supported
-
-
-
- FreeBSD 3.X and earlier supported
- bad144 , which automatically remapped
- bad blocks. FreeBSD 4.X and later do not support this, as
- modern IDE drives include this functionality. See this question for
- more information.
-
- 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.
-
-
-
-
-
- How do I tell if a drive has bad144
- information on it before I try to upgrade to FreeBSD 4.0
- and it fails?
+ ¦³ÃayªºµwºÐ¥i¥H®³¨Ó¸Ë FreeBSD ¹À¡H
- Use &man.disklabel.8; for this. disklabel -r
- drive device will
- give you the contents of your disk label. Look for a
- flags field. If you see
- flags: badsect , this drive is using
- bad144. For example, the following drive has
- bad144 enabled.:
-
- &prompt.root; disklabel -r wd0
-# /dev/rwd0c:
-type: ESDI
-disk: wd0s1
-label:
-flags: badsect
-bytes/sector: 512
-sectors/track: 63
-
-
+ (¦pªG«Ü°í«ùªº¸Ü)¤]¬O¥i¥H¡A¤£¹L³o·QªkÅãµM¤£¤Ó¦n¡C:(
-
-
- How do I remove bad144 from my
- pre-4.X system so I can upgrade safely?
-
-
-
- Use disklabel -e -rwd0 to edit the
- disklabel in place. Just remove the word
- badsect 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.
+ ¦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)§ÚÌ«Øij¶RÁû·sµwºÐ¤ñ¸û°®¯Ü¨Çò¡C
- We still recommend you purchase a new disk if you have
- a large number of bad blocks.
+ ¦pªG¬O SCSI µwºÐ¦³Ãayªº¸Ü¡A½Ð¸ÕµÛ°Ñ¦Ò³oÓ
+ ¸Ñªk¡C
- Strange things happen when I boot the install floppy!
- What is happening?
+ ¥Î¦w¸ËºÏ¤ù¶}¾÷®É¡A«o¦³¨Ç©Ç²{¶Hµo¥Í¡I³o¬O¤°»ò±¡ªp©O¡H
- 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:-
+ Y¬Ý¨ì¤@¨Ç©Ç²§²{¶H¡A¹³¬O¶}¾÷¤ù¶}¾÷¶}¨ì¤@¥b´N·í¤F¡AºÏºÐ¾÷§¹¥þ¨S¥ô¦ó°Ê§@¡B
+ ©Î¬O¤£Â_¤ÏÂЫ¶}¾÷¡A½Ð¥ýÀˬd¥H¤U´XÓ½u¯Á¡G
- 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)?
+ ½Ð½T©w¬O§_¬°¥þ·s¡B¨S¦³ºÏy¿ù»~ªººÏ¤ù¡H
+ (³Ì¦n¨Ï¥Î·s¶Rªº¡A¦Ó«DÂø»x¡B®Ñ¥»ªþÃتº¡A¬Æ¦ÜÁÙÂæb§É©³¤U¤T¦~¤F...)
- 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!)
+ ½Ð½T©w¬O§_¦³¥Î binary(©Îimage)¶Ç¿é¼Ò¦¡¨Ó¤U¸ü image ÀÉ¡H
+ (¤£¥Îı±o¤£¦n·N«ä¡A§Y¨Ï¬O§Ṳ́]´¿·N¥~¥H ASCII ¶Ç¿é¼Ò¦¡¨Ó¤U¸ü binary ÀɮסI)
- If you are using Windows95 or Win98 did you run
- fdimage or rawrite 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.
+ Y§A¬O &windows; 95/98/ME/NT/2000/XP/2003 ¨Ó¤U¸ü¡B»s§@¶}¾÷ºÏ¤ùªº¸Ü¡A
+ ½Ð½T©w¬O§_¦³¦b DOS ¼Ò¦¡¨Ï¥Î fdimage ©Î
+ rawrite ³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
+
- 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.
+ ¦¹¥~¡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 ¶Ç¿é¼Ò¦¡)
- I booted from my ATAPI CDROM, but the install program says no
- CDROM is found. Where did it go?
+ ¥Î¥úºÐ¶}¾÷¤ù¨Ó¦w¸Ë¡A¦ý¥úºÐ¶}¾÷«á¡A¦w¸Ëµ{¦¡»¡§ä¤£¨ì¥úºÐ...³o¬O«ç»ò¤F¡H
- 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.
+ ³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
- 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.
+ ¸Ñª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
- Can I install on my laptop over PLIP (Parallel Line
- IP)?
+ §Ú¥i¥H¥Î PLIP(Parallel Line IP)¤è¦¡¨Ó¦w¸Ë FreeBSD ¨ìµ§°O«¬¹q¸£¤W¶Ü¡H
- Yes. Use a standard Laplink cable. If necessary, you
- can check out the PLIP
- section of the Handbook for details on parallel
- port networking.
-
- If you are running FreeBSD 3.X or earlier, also look at
- the Mobile
- Computing page .
+ ¥i¥H¡A¥Î¤@±ø´¶³qªº Laplink ½u´N¥i¥HÅo¡CY¦³³o¤è±»Ý¨Dªº¸Ü¡A½Ð°Ñ¾\? FreeBSD ¨Ï¥Î¤â¥U?¤¤ªº
+ PLIP
+ ³¹¸` ªº²Ó³¡³]©w
Which geometry should I use for a disk drive?
By the geometry
of a disk, we mean
the number of cylinders, heads and sectors/track on a
disk. We will refer to this as C/H/S for
convenience. This is how the PC's BIOS works out which
area on a disk to read/write from.
This causes a lot of confusion among new system
administrators. First of all, the
physical geometry of a SCSI drive is
totally irrelevant, as FreeBSD works in term of disk
blocks. In fact, there is no such thing as
the
physical geometry, as the sector
density varies across the disk. What manufacturers claim
is the physical geometry
is usually the
geometry that they have determined wastes the least
space. For IDE disks, FreeBSD does work in terms of C/H/S,
but all modern drives internally convert this into block
- references.
-
+ references.
All that matters is the logical
geometry. This is the answer that the BIOS gets when it
asks the drive what is your geometry?
It
then uses this geometry to access the disk. As FreeBSD
uses the BIOS when booting, it is very important to get
this right. In particular, if you have more than one
operating system on a disk, they must all agree on the
geometry. Otherwise you will have serious problems
booting!
For SCSI disks, the geometry to use depends on whether
extended translation support is turned on in your
controller (this is often referred to as support for
DOS disks >1GB
or something similar). If it is
turned off, then use N
cylinders, 64 heads and 32 sectors/track, where
N is the capacity of the disk in
MB. For example, a 2GB disk should pretend to have 2048
cylinders, 64 heads and 32 sectors/track.
If it is 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 (not
- 64), and 255 heads, where 'M' is the disk capacity in MB
+ 64), and 255 heads, where M 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.
If you are not sure about this, or FreeBSD fails to
detect the geometry correctly during installation, the
simplest way around this is usually to create a small DOS
partition on the disk. The BIOS should then detect the
correct geometry, and you can always remove the DOS
partition in the partition editor if you do not want to
keep it. You might want to leave it around for
programming network cards and the like, however.
Alternatively, there is a freely available utility
distributed with FreeBSD called
pfdisk.exe . You can find it in the
tools subdirectory on the FreeBSD
CDROM or on the various FreeBSD FTP sites. This program
can be used to work out what geometry the other operating
systems on the disk are using. You can then enter this
geometry in the partition editor.
Are there any restrictions on how I divide the disk up?
- Yes. You must make sure that your root partition is below
- 1024
+ 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).
For a SCSI drive, this will normally imply that the root
partition will be in the first 1024MB (or in the first 4096MB
if extended translation is turned on - see previous question).
For IDE, the corresponding figure is 504MB.
Is FreeBSD compatible with any disk managers?
FreeBSD recognizes the Ontrack Disk Manager and makes
allowances for it. Other disk managers are not supported.
If you just want to use the disk with FreeBSD you do not
need a disk manager. Just configure the disk for as much space
as the BIOS can deal with (usually 504 megabytes), and FreeBSD
should figure out how much space you really have. If you are
using an old disk with an MFM controller, you may need to
explicitly tell FreeBSD how many cylinders to use.
If you want to use the disk with FreeBSD and another
operating system, you may be able to do without a disk manager:
just make sure the FreeBSD boot partition and the slice for
the other operating system are in the first 1024 cylinders. If
you are reasonably careful, a 20 megabyte boot partition should
be plenty.
- When I boot FreeBSD I get Missing Operating
+ When I boot FreeBSD for the first time after install I get Missing Operating
System . What is happening?
This is classically a case of FreeBSD and DOS or some other
OS conflicting over their ideas of disk geometry. You will have to reinstall
FreeBSD, but obeying the instructions given above will almost
always get you going.
Why can I not get past the boot manager's F?
prompt?
This is another symptom of the problem described in the
preceding question. Your BIOS geometry and FreeBSD geometry
settings do not agree! If your controller or BIOS supports
cylinder translation (often marked as >1GB drive
support
), try toggling its setting and reinstalling
FreeBSD.
Do I need to install the complete sources?
In general, no. However, we would strongly recommend that
you install, at a minimum, the base source
kit, which includes several of the files mentioned here, and
the sys (kernel) source kit, which includes
sources for the kernel. There is nothing in the system which
requires the presence of the sources to operate, however,
except for the kernel-configuration program &man.config.8;.
With the exception of the kernel sources, our build structure
is set up so that you can read-only mount the sources from
- elsewhere via NFS and still be able to make new binaries.
- (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 /usr/src directly,
but rather in some other location with appropriate symbolic
links to duplicate the top-level structure of the source
- tree.)
+ tree).
Having the sources on-line and knowing how to build a
system with them will make it much easier for you to upgrade
to future releases of FreeBSD.
To actually select a subset of the sources, use the Custom
menu item when you are in the Distributions menu of the
system installation tool.
Do I need to build a kernel?
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 -c 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.
+ 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.
- It is still recommended that you eventually build a new
+ 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.
- Should I use DES, Blowfish, or MD5 passwords and how do I specify
- which form my users receive?
+ Should I use DES, Blowfish, or MD5 passwords and how
+ do I specify which form my users receive?
The default password format on FreeBSD is to use
- MD5 -based passwords. These are believed to
- be more secure than the traditional Unix password format, which
- used a scheme based on the DES 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
+ MD5 -based passwords. These are
+ believed to be more secure than the traditional &unix;
+ password format, which used a scheme based on the
+ DES 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 crypto
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 passwd_format
login capability
- in /etc/login.conf , which takes values of
- des
, blf
(if these are available) or md5
.
- See the &man.login.conf.5; manual page for more information about login
- capabilities.
+ 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
+ passwd_format
login capability in
+ /etc/login.conf , which takes values
+ of des
, blf
(if these are
+ available) or md5
. See the
+ &man.login.conf.5; manual page for more information about
+ login capabilities.
Why does the boot floppy start, but hang at the
Probing Devices... screen?
- If you have a IDE Zip or Jaz drive installed, remove it
+ 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.
Why do I get a panic: can't mount root
error when rebooting the system after installation?
- 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
+ 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.
To fix the problem, do one of the following:
- For FreeBSD 3.3 and later, reboot the system and hit
- Enter at the Booting kernel
- in 10 seconds; hit [Enter] to interrupt prompt.
- This will drop you into the boot loader.
+ Reboot the system and hit Enter
+ at the Booting kernel in 10 seconds; hit
+ [Enter] to interrupt prompt. This will
+ drop you into the boot loader.
Then type
- set root_disk_unit="disk_number "
+ set
+ root_disk_unit="disk_number "
. disk_number
- will be 0 if FreeBSD is installed on
- the master drive on the first IDE controller,
- 1 if it is installed on the slave on
- the first IDE controller, 2 if it is
- installed on the master of the second IDE controller, and
- 3 if it is installed on the slave of
- the second IDE controller.
-
- Then type boot , and your system
- should boot correctly.
-
- 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
- root_disk_unit="disk_number " in /boot/loader.conf.local
+ will be 0 if FreeBSD is installed
+ on the master drive on the first IDE controller,
+ 1 if it is installed on the slave
+ on the first IDE controller, 2 if
+ it is installed on the master of the second IDE
+ controller, and 3 if it is
+ installed on the slave of the second IDE
+ controller.
+
+ Then type boot , and your
+ system should boot correctly.
+
+ 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
+ root_disk_unit="disk_number "
+ in /boot/loader.conf.local
.
- If using FreeBSD 3.2 or earlier, at the Boot: prompt,
- enter 1:wd(2,a)kernel and press Enter.
- If the system starts, then run the command
- echo "1:wd(2,a)kernel" > /boot.config
- to make it the default boot string.
-
-
-
- Move the FreeBSD disk onto the primary IDE controller,
- so the hard disks are consecutive.
-
-
-
- Rebuild
- your kernel, modify the wd configuration lines to
- read:
-
- 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
-
- 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.
+ Move the FreeBSD disk onto the primary IDE
+ controller, so the hard disks are
+ consecutive.
What are the limits for memory?
- For memory, the limit is 4 gigabytes. This configuration
- has been tested, see wcarchive's
- configuration 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.
+ 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:
+
+ options PAE
+
+ &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).
What are the limits for ffs filesystems?
For ffs filesystems, the maximum theoretical limit is 8
terabytes (2G blocks), or 16TB for the default block size of
8K. In practice, there is a soft limit of 1 terabyte, but with
modifications filesystems with 4 terabytes are possible (and
exist).
The maximum size of a single ffs file is approximately 1G
- blocks (4TB) if the block size is 4K.
+ blocks, or 4TB with a block size of 4K.
Maximum file sizes
-
+
fs block size
- 2.2.7-stable
-
- 3.0-current
-
works
should work
4K
4T-1
- 4T-1
-
- 4T-1
-
>4T
8K
>32G
- 8T-1
-
- >32G
-
32T-1
16K
>128G
- 16T-1
-
- >128G
-
32T-1
32K
>512G
- 32T-1
-
- >512G
-
64T-1
64K
>2048G
- 64T-1
-
- >2048G
-
128T-1
When the fs block size is 4K, triple indirect blocks work
and everything should be limited by the maximum fs block number
that can be represented using triple indirect blocks (approx.
1K^3 + 1K^2 + 1K), but everything is limited by a (wrong) limit
of 1G-1 on fs block numbers. The limit on fs block numbers
should be 2G-1. There are some bugs for fs block numbers near
2G-1, but such block numbers are unreachable when the fs block
size is 4K.
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.
+ 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.
Why do I get an error message,
archsw.readin.failed after compiling
and booting a new kernel?
- 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
- without making world . This is not
- supported. Make world.
-
-
-
-
-
- How do I upgrade from 3.X -> 4.X?
-
-
-
- We strongly recommend that you use
- binary snapshots to do this. 4-STABLE snapshots are available at
- ftp://releng4.FreeBSD.org/ .
-
- 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 (RELENG_3 ).
- Then upgrade to 4.1.1-RELEASE
- (RELENG_4_1_1_RELEASE ). Finally,
- upgrade to 4-STABLE (RELENG_4 ).
+ Because your world and kernel are out of synch. This
+ is not supported. Be sure you use make
+ buildworld and make
+ buildkernel to update your kernel.
- If you wish to upgrade using source, please see the FreeBSD
- Handbook for more information.
-
-
- 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.
-
+ You can boot by specifying the kernel directly at the
+ second stage, pressing any key when the | shows up before
+ loader is started.
What are these security profiles
?
A security profile
is a set of configuration
options that attempts to achieve the desired ratio of security
to convenience by enabling and disabling certain programs and
other settings. For full details, see the Security
+ url="&url.books.handbook;/install-post.html#SECURITYPROFILE">Security
Profile section of the Handbook's post-install
+ url="&url.books.handbook;/install-post.html">post-install
chapter .
Hardware compatibility
-
-
-
- Does FreeBSD support architectures other than the
- x86?
-
-
-
-
- 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;.
-
- If your machine has a different architecture and you need
- something right now, we suggest you look at NetBSD or OpenBSD .
-
-
+
+ General
+
I want to get a piece of hardware for my FreeBSD
system. Which model/brand/type is best?
This is discussed continually on the FreeBSD mailing
lists. Since hardware changes so quickly, however, we
expect this. We still strongly
- recommend that you read through the
- Hardware Notes
+ recommend that you read through the Hardware notes for &os;
+ &rel.current;
+ or
+ &rel2.current;
and search the mailing list
-
+
archives before asking about the latest and
greatest hardware. Chances are a discussion about the
type of hardware you are looking for took place just last
week.
If you are looking for a laptop, check the
FreeBSD-mobile mailing list archives. Otherwise, you
probably want the archives for FreeBSD-questions, or
possibly a specific mailing list for a particular hardware
type.
+
+
+
+
+ Architectures and processors
+
+
+
+
+ Does FreeBSD support architectures other than the x86?
+
+
+
+
+ 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;.
+
+ If your machine has a different architecture and you
+ need something right now, we suggest you look at NetBSD or OpenBSD .
+
+
+
+
+
+ Does FreeBSD support Symmetric Multiprocessing
+ (SMP)?
+
+
+
+ Yes. SMP was enabled by default in the
+ GENERIC kernel as of &os; 5.2.
+
+ 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.
+
+ 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 /sys/i386/conf/LINT to learn
+ which options to put in your kernel config file.
+
+
+
+
+
+
+ Hard drives, tape drives, and CD and DVD drives
+
+
+
What kind of hard drives does FreeBSD support?
FreeBSD supports EIDE and SCSI drives (with a compatible
controller; see the next section), and all drives using the
original Western Digital
interface (MFM, RLL,
ESDI, and of course IDE). A few ESDI controllers that use
proprietary interfaces may not work: stick to WD1002/3/6/7
interfaces and clones.
Which SCSI controllers are supported?
- See the complete list in the current Hardware Notes .
+ See the complete list in the Hardware Notes for &os;
+ &rel.current; or
+ &rel2.current; .
+
+
+
+
+
+ What types of tape drives are supported?
+
+
+
+
+ FreeBSD supports SCSI and QIC-36 (with a QIC-02 interface).
+ This includes 8-mm (aka Exabyte) and DAT drives.
+
+ Some of the early 8-mm drives are not quite compatible
+ with SCSI-2, and may not work well with FreeBSD.
+
+
+
+
+
+ Does FreeBSD support tape changers?
+
+
+
+ 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.
+
+ If you are not using AMANDA
+ 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.
Which CDROM drives are supported by FreeBSD?
Any SCSI drive connected to a supported controller is
supported.
The following proprietary CDROM interfaces are also
supported:
Mitsumi LU002 (8bit), LU005 (16bit) and FX001D
(16bit 2x Speed).
Sony CDU 31/33A
Sound Blaster Non-SCSI CDROM
Matsushita/Panasonic CDROM
ATAPI compatible IDE CDROMs
All non-SCSI cards are known to be extremely slow compared
to SCSI drives, and some ATAPI CDROMs may not work.
- As of 2.2 the FreeBSD CDROM from the FreeBSD Mall supports
- booting directly from the CD.
+ The official FreeBSD CDROM ISO, and CDROMs from Daemon
+ News and FreeBSD Mall, support booting directly from the
+ CD.
Which CD-RW drives are supported by FreeBSD?
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 /usr/share/examples/atapi .
+ drive. See &man.burncd.8; for details.
FreeBSD also supports any SCSI CD-R or CD-RW drives.
Install and use the cdrecord command from the
ports or packages system, and make sure that you have the
pass device compiled in your
kernel.
- Does FreeBSD support ZIP drives?
+ Does FreeBSD support &iomegazip; drives?
- 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.
-
- ATAPI (IDE) Zip drives are supported in FreeBSD 2.2.6 and
- later releases.
+ 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.
- 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
- scbus0 , da0 ,
+ FreeBSD also supports Parallel Port Zip Drives. Check
+ that your kernel contains the
+ scbus0 ,
+ da0 ,
ppbus0 , and
vp0 drivers (the GENERIC kernel
- contains everything except vp0 ). With
- all these drivers present, the Parallel Port drive should be
- available as /dev/da0s4 . Disks can be
- mounted using mount /dev/da0s4 /mnt OR (for
- dos disks) mount_msdos /dev/da0s4 /mnt as
+ contains everything except
+ vp0 ). With all these drivers
+ present, the Parallel Port drive should be available as
+ /dev/da0s4 . Disks can be mounted
+ using mount /dev/da0s4 /mnt OR (for dos
+ disks) mount_msdos /dev/da0s4 /mnt as
appropriate.
- Also check out the FAQ on removable
- drives later in this chapter, and the note on
- formatting
in the Administration chapter.
+ Also check out the FAQ on
+ removable drives later in this chapter, and the note on
+ formatting
in the Administration
+ chapter.
- Does FreeBSD support JAZ, EZ and other removable
+ Does FreeBSD support &jaz;, EZ and other removable
drives?
- 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.
+ They work. Most of these are SCSI devices, so they
+ look like SCSI disks to FreeBSD. The IDE EZ looks like an
+ IDE drive.
- 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.
+ Make sure that any external units are powered on when
+ booting the system.
- See this note on
- formatting
.
+ 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 discussion on using removable
+ drives later in the FAQ.
-
-
- Which multi-port serial cards are supported by
- FreeBSD?
-
+
-
- There is a list of these in the Miscellaneous
- devices section of the handbook.
+
- Some unnamed clone cards have also been known to work,
- especially those that claim to be AST compatible.
+
+ Keyboards and mice
- Check the &man.sio.4;
- man page to get more information on configuring such cards.
-
-
+
Does FreeBSD support my USB keyboard?
- 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.
+ FreeBSD supports USB keyboards
+ out-of-the-box. Enable USB support in
+ /etc/rc.conf .
-
-
- Use FreeBSD 3.2 or later.
-
+ Once you have USB keyboard support enabled on your
+ system, the AT keyboard becomes
+ /dev/kbd0 and the USB keyboard
+ becomes /dev/kbd1 , if both are
+ connected to the system. If there is the USB keyboard
+ only, it will be
+ /dev/ukbd0 .
-
- Add the following lines to your kernel configuration
- file, and rebuild the kernel.
-
- device uhci
-device ohci
-device usb
-device ukbd
-options KBD_INSTALL_CDEV
-
- In versions of FreeBSD before 4.0, use this
- instead:
-
- controller uhci0
-controller ohci0
-controller usb0
-controller ukbd0
-options KBD_INSTALL_CDEV
-
+ 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.
-
- Go to the /dev directory and create
- device nodes as follows:
+ &prompt.root; kbdcontrol -k /dev/kbd1 < /dev/ttyv0 > /dev/null
- &prompt.root; cd /dev
-&prompt.root; ./MAKEDEV kbd0 kbd1
+ Note that if the USB keyboard is the only keyboard, it
+ is accessed as /dev/kbd0 , thus,
+ the command should look like:
-
+ &prompt.root; kbdcontrol -k /dev/kbd0 < /dev/ttyv0 > /dev/null
-
- Edit /etc/rc.conf and add the
- following lines:
+ /etc/rc.i386 is a good place to
+ add the above command.
- usbd_enable="YES"
-usbd_flags=""
+ Once this is done, the USB keyboard should work in the
+ X environment as well without any special settings.
-
-
+ 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.
- After the system is rebooted, the AT keyboard becomes
- /dev/kbd0 and the USB keyboard becomes
- /dev/kbd1 , if both are connected to the
- system. If there is the USB keyboard only, it will be
- /dev/ukbd0 .
-
- 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.
-
- &prompt.root; kbdcontrol -k /dev/kbd1 < /dev/ttyv0 > /dev/null
-
- Note that if the USB keyboard is the only keyboard, it is
- accessed as /dev/kbd0 , thus, the command
- should look like:
-
- &prompt.root; kbdcontrol -k /dev/kbd0 < /dev/ttyv0 > /dev/null
-
- /etc/rc.i386 is a good place to add the
- above command.
-
- Once this is done, the USB keyboard should work in the X
- environment as well without any special settings.
-
- 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.
-
- See the &man.ukbd.4; man page for more information.
+ See the &man.ukbd.4; manual page for more information.
- I have an unusual bus mouse. How do I set it up?
+ I have an unusual bus mouse. How do I set it
+ up?
- 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
-
- In FreeBSD 3.0 or before, add:
-
- device mse0 at isa? port 0x23c tty irq5 vector mseintr
-
- In FreeBSD 3.X, the line should be:
-
- device mse0 at isa? port 0x23c tty irq5
-
- And in FreeBSD 4.X and later, the line should read:
+ 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:
device mse0 at isa? port 0x23c irq5
- 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.
+ 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.
How do I use my PS/2 (mouse port
or
keyboard
) mouse?
+ The PS/2 mouse is supported out-of-the-box. The
+ necessary device driver, psm , is
+ included in the kernel.
- If you are running a post-2.2.5 version of FreeBSD, the
- necessary driver, psm , is included and
- enabled in the kernel. The kernel should detect your PS/2 mouse
- at boot time.
-
- 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 -c at the boot:
- prompt. It is disabled by default, so you will need to enable
- it explicitly.
-
- 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.
-
- In FreeBSD 3.0 or earlier, the line should be:
-
- device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr
-
- In FreeBSD 3.1 or later, the line should be:
-
- device psm0 at isa? tty irq 12
-
- In FreeBSD 4.0 or later, the line should be:
+ If your custom kernel does not have this, add the
+ following line to your kernel configuration and compile a
+ new kernel.
device psm0 at atkbdc? irq 12
- See the Handbook entry on
- configuring the kernel if you have no experience with
- building kernels.
-
- Once you have a kernel detecting
- psm0 correctly at boot time, make sure
- that an entry for psm0 exists in
- /dev . You can do this by typing:
+ Once the kernel detects psm0
+ correctly at boot time, make sure that an entry for
+ psm0 exists in
+ /dev . You can create this entry by
+ typing:
&prompt.root; cd /dev; sh MAKEDEV psm0
when logged in as root .
-
+
+
+ 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 /dev .
+
+
- Is it possible to make use of a mouse in any way outside
- the X Window system?
+ Is it possible to use a mouse in any way outside the X
+ Window system?
- 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:
+ 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:
&prompt.root; moused -p /dev/xxxx -t yyyy
&prompt.root; vidcontrol -m on
- Where xxxx is the mouse device
- name and yyyy is a protocol type for
- the mouse. See the &man.moused.8; man page for supported
+ Where xxxx is the mouse
+ device name and yyyy 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
+ auto 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.
- You may wish to run the mouse daemon automatically when the
- system starts. In version 2.2.1, set the following variables in
- /etc/sysconfig .
-
- mousedtype="yyyy"
-mousedport="xxxx"
-mousedflags=""
-
- In versions 2.2.2 to 3.0, set the following variables in
- /etc/rc.conf .
-
- moused_type="yyyy"
-moused_port="xxxx"
-moused_flags=""
-
- In 3.1 and later, assuming you have a PS/2 mouse, all you
- need to is add moused_enable="YES" to
- /etc/rc.conf .
-
- 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
- /etc/rc.conf .
-
- allscreens_flags="-m on"
-
- 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
- auto the protocol to invoke automatic
- detection.
+ If you have a PS/2 mouse, just add
+ moused_enable="YES" to
+ /etc/rc.conf 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 allscreens_flags="-m
+ on" to /etc/rc.conf .
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 another section on this
- issue.
+ must be coordinated between the mouse daemon and other
+ programs such as X Windows. Refer to the FAQ Why does my mouse not work with
+ X? for more details on this issue.
- How do I cut and paste text with mouse in the text
+ How do I cut and paste text with a mouse in the text
console?
- Once you get the mouse daemon running (see
- previous section), 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.
-
- In versions 2.2.6 and later, pressing the button 2 will
- paste the text. Pressing the button 3 will
- extend
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.
-
-
-
-
-
- Does FreeBSD support any USB mice?
-
-
-
-
- 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.
-
-
-
- Use FreeBSD 3.2 or later.
-
-
-
- Add the following lines to your kernel configuration
- file, and rebuild the kernel.
-
- device uhci
-device ohci
-device usb
-device ums
-
- In versions of FreeBSD before 4.0, use this
- instead:
-
- controller uhci0
-controller ohci0
-controller usb0
-device ums0
-
-
-
- Go to the /dev directory and
- create a device node as follows:
-
- &prompt.root; cd /dev
-&prompt.root; ./MAKEDEV ums0
-
-
-
- Edit /etc/rc.conf and add the
- following lines:
-
- moused_enable="YES"
-moused_type="auto"
-moused_port="/dev/ums0"
-moused_flags=""
-usbd_enable="YES"
-usbd_flags=""
-
- See the previous section
- for more detailed discussion on moused.
-
-
-
- In order to use the USB mouse in the X session, edit
- XF86Config . If you are using XFree86
- 3.3.2 or later, be sure to have the following lines in the
- Pointer section:
+ Once you get the mouse daemon running (see the previous section), 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 extend
the selected region of
+ text.
- Device "/dev/sysmouse"
-Protocol "Auto"
-
- If you are using earlier versions of XFree86, be sure to
- have the following lines in the Pointer
- section:
-
- Device "/dev/sysmouse"
-Protocol "SysMouse"
-
-
-
- Refer to another section
- on the mouse support in the X environment.
-
- 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.
+ 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.
My mouse has a fancy wheel and buttons. Can I use them in
FreeBSD?
The answer is, unfortunately, It depends
.
These mice with additional features require specialized driver
in most cases. Unless the mouse device driver or the user
program has specific support for the mouse, it will act just
like a standard two, or three button mouse.
For the possible usage of wheels in the X Window
environment, refer to that
section.
-
-
- Why does my wheel-equipped PS/2 mouse cause my mouse cursor
- to jump around the screen?
-
-
-
- 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
- /sys/i386/isa/psm.c and rebuild the
- kernel.
-
- 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) {
-
- Versions later than 3.2 should be all right.
-
-
-
- How do I use the mouse/trackball/touchpad on my
- laptop?
+ How do I use the mouse/trackball/touchpad on my laptop?
Please refer to the answer to
- the previous question. Also check out the Mobile
- Computing page .
-
-
-
-
-
- What types of tape drives are supported?
-
-
-
-
- FreeBSD supports SCSI and QIC-36 (with a QIC-02 interface).
- This includes 8-mm (aka Exabyte) and DAT drives.
-
- Some of the early 8-mm drives are not quite compatible
- with SCSI-2, and may not work well with FreeBSD.
-
-
-
-
-
- Does FreeBSD support tape changers?
-
-
-
- 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.
-
- If you are not using AMANDA
- 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.
+ the previous question.
-
-
- Which sound cards are supported by FreeBSD?
-
-
-
- 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.
+
-
- 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.
-
-
-
-
-
-
- Workarounds for no sound from es1370 with pcm driver?
-
+
-
- You can run the following command every time the machine
- booted up:
+
+ Networking and serial devices
- &prompt.root; mixer pcm 100 vol 100 cd 100
-
-
+
Which network cards does FreeBSD support?
- See the
- Ethernet cards section of the handbook for a more
+ See the Hardware Notes supplied with each release of
+ FreeBSD for a more
complete list.
-
-
- I do not have a math co-processor - is that bad?
-
-
-
-
- This will only affect 386/486SX/486SLC owners - other
- machines will have one built into the CPU.
-
-
- 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 on FP emulation). 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.
-
-
- 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.
-
-
-
-
-
-
- What other devices does FreeBSD support?
-
-
-
- See the Handbook
- for the list of other devices supported.
-
-
-
-
-
-
- Does FreeBSD support power management on my laptop?
-
-
-
- FreeBSD supports APM on certain machines. Please look in
- the LINT kernel config file, searching for
- the
- APM
- keyword. Further information can be found in &man.apm.4;.
-
-
-
-
-
-
- Why does my Micron system hang at boot time?
-
-
-
- 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.
-
- Disable the Plug and Play Operating System
- flag in the BIOS to work around this problem. More information
- can be found at
- http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html#micron
-
-
-
-
-
- Why does FreeBSD not recognize my Adaptec SCSI
- controller card?
-
-
-
- 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
- ftp://ftp.FreeBSD.org/pub/FreeBSD/development/cam/ .
- A CAM-enhanced boot floppy is available at
- http://people.FreeBSD.org/~abial/cam-boot/ .
- In both cases read the README before beginning.
-
-
-
Why is FreeBSD not finding my internal Plug & Play
modem?
You will need to add the modem's PnP ID to the PnP ID
list in the serial driver. To enable Plug & Play support,
compile a new kernel with controller pnp0 in
the configuration file, then reboot the system. The kernel will
print the PnP IDs of all the devices it finds. Copy the PnP ID
from the modem to the table in
/sys/i386/isa/sio.c , at about line 2777.
Look for the string SUP1310 in the structure
siopnp_ids[] to find the table. Build the
kernel again, install, reboot, and your modem should be
found.
You may have to manually configure the PnP devices using
the pnp command in the boot-time
configuration with a command like
pnp 1 0 enable os irq0 3 drq0 0 port0 0x2f8
to make the modem show.
- Does FreeBSD support software modems, such as
- Winmodems?
+ Does FreeBSD support software modems, such as Winmodems?
FreeBSD supports many software modems via add-on
software. The comms/ltmdm port adds
support for modems based on the very popular Lucent LT
chipset. The comms/mwavem port
supports the modem in IBM Thinkpad 600 and 700
laptops.
You cannot install FreeBSD via a software modem; this
software must be installed after the OS is
installed.
+
+
+ Is there a native driver for the Broadcom 43xx cards?
+
+
+
+ No, and there is not likely to be.
+
+ 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.
+
+
+
+
+
+ Which multi-port serial cards are supported by
+ FreeBSD?
+
+
+
+ There is a list of these in the Miscellaneous
+ devices section of the handbook.
+
+ Some unnamed clone cards have also been known to work,
+ especially those that claim to be AST compatible.
+
+ Check the &man.sio.4; manual page to get more
+ information on configuring such cards.
+
+
+
How do I get the boot: prompt to show on the serial
console?
Build a kernel with
options COMCONSOLE .
Create /boot.config and place -P
as the only text in the file.
Unplug the keyboard from the system.
See
/usr/src/sys/i386/boot/biosboot/README.serial
for information.
+
+
+
+
+
+ Sound devices
+
+
+
-
- Why does my 3Com PCI network card not work with my Micron
- computer?
+
+ Which sound cards are supported by FreeBSD?
- 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.
+ &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 &os; Release Information
+ 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.
- To work around this problem, disable the
- Plug and Play Operating System
flag in the
- BIOS.
+
+ 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.
+
+
+
+
+
+
+ Workarounds for no sound from my &man.pcm.4; sound
+ card?
+
- More information on this problem is available at URL:
- http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html#micron
+
+ 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:
+
+ &prompt.root; mixer pcm 100 vol 100 cd 100
+
+
+
+
+
+ Other hardware
+
+
+
-
- Does FreeBSD support Symmetric Multiprocessing (SMP)?
+
+ What other devices does FreeBSD support?
+
+
+
+ See the Handbook
+ for the list of other devices supported.
+
+
+
+
+
+
+ Does FreeBSD support power management on my
+ laptop?
- SMP is supported in 3.0-STABLE and later releases only.
- SMP is not enabled in the GENERIC kernel,
- so you will have to recompile your kernel to enable SMP. Take a
- look at /sys/i386/conf/LINT to figure out
- what options to put in your kernel config file.
+ FreeBSD 4.X and later support APM
+ on certain machines. Further information can be found in
+ &man.apm.4;.
+
+ FreeBSD 5.X and later support the
+ ACPI features found in most modern
+ hardware. Further information can be found in
+ &man.acpi.4;. If a system supports both
+ APM and ACPI , either
+ can be used. We suggest you try both and choose the one
+ that best fits your needs.
+
+
+
+
+
+
+ Why does my Micron system hang at boot time?
+
+
+
+ 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.
+
+ Disable the Plug and Play Operating System
+ flag in the BIOS to work around this problem.
The boot floppy hangs on a system with an ASUS K7V
motherboard. How do I fix this?
- Go in to the BIOS setup and disable the boot virus
+ Go into the BIOS setup and disable the boot virus
protection
.
+
+
+
+ Why does my &tm.3com; PCI network card not work with my Micron
+ computer?
+
+
+
+ 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.
+
+ To work around this problem, disable the
+ Plug and Play Operating System
flag in the
+ BIOS.
+
+
+
+
+
William
Liao
chliao@tpts4.seed.net.tw
±`¨£°ÝÃD¸Ñ¨M
§ÚªºµwºÐ¦³Ãay®É¸Ó«ç»ò¿ì?
Y¬O SCSI µwºÐªº¸Ü¡A¨º»òºÏºÐ¾÷À³¸Ó¦³¯à¤O¦Û°Ê§@ re-mapping
ªº°Ê§@¡CµM¦Ó¡A¦]¬°¤@¨Ç¥¼ª¾ªº¦]¯À¡A¦b¥X¼t®É¡A«Ü¦hµwºÐªº³o¶µ
¥\¯à¬OÃö³¬ªº...
n±N¨ä«·s¶}±Ò¡A±z»Ýn½s¿è¸Ë¸mªº²Ä¤@Ó page ¼Ò¦¡
¡]first device page mode¡^¡A¦b FreeBSD ¤W¥i¥H¥Î¤U±ªº«ü¥O¿ì¨ì
¡]¥H root ¨¤À°õ¦æ¡^
&prompt.root; scsi -f /dev/rsd0c -m 1 -e -P 3
µM«á±N AWRE ©M ARRE ªº¼Æȱq 0 Åܦ¨ 1:-
AWRE¡]Auto Write Reallocation Enbld¡^¡G 1
ARRE¡]Auto Read Reallocation Enbld¡^¡G 1
¥H¤U³o¬q¬O¥Ñ Ted Mittelstaedt
tedm@toybox.placo.com ©Ò´£¨Ñ¡G
Y¬° IDE µwºÐ¡A¥ô¦óªºÃay³q±`³£¬O³Â·Ðªº¹w¥ü¡C¥Ø«e©Ò¦³¸û·sªº
IDE µwºÐ¡A¤º³¡³£¦³¦Û°Ê remapping Ãayªº¯à¤O¡C¥Ø«e©Ò¦³ IDE µwºÐ
»s³y°Ó¡A³£´£¨Ñ¤F§ó¤[ªº«OÃÒ¡A¦Ó¥B·|À°±z§ó´«¥X²{ÃayªºµwºÐ¡C
¦pªG±z¤´·Qn×´_²£¥ÍÃayªº IDE µwºÐ¡A±z¤´¥i¥H¸ÕµÛ¥h¤U¸ü IDE
µwºÐ»s³y°Ó©Ò´£¨ÑªºÀË´úµ{¦¡¡A¨Ã¥Î¥¦¨ÓÀˬd±zªºµwºÐ¡C¦³®É³o¨Ç³nÅé¥i
¥H±j¢«·sÀˬdµwºÐªºÃay¡A¨Ã±N¥¦Ì¼Ð¥Ü¥X¨Ó¡C
¹ï ESDI¡ARLL ¤Î MFM ªºµwºÐ¨Ó»¡¡A³q±`Ãay¬O¥¿±`²{¶H¡A¤]¤£¬O¤°
»ò³Â·Ðªº«e¥ü¡C¦b PC ¤W¡AºÏºÐ±±¨î¥d©M BIOS t³d¼Ð¥ÜÃayªº¥ô°È¡C³o
¹ï¤@¨Ç¨Ï¥Î BIOS¨Ó¦s¨úºÏºÐªº§@·~Àô¹Ò¡]¦p DOS¡^¬O¨S¦³°ÝÃDªº¡CµM¦Ó¡A
FreeBSD ªººÏºÐÅX°Êµ{¦¡¨Ã¤£¸g¹L BIOS ¨Ó¦s¨úºÏºÐ¡A©Ò¥H¡A¦³Ó bad144
ªº¾÷¨î¥Î¨Ó¨ú¥N³o¶µ¥\¯à¡Cbad144 ¥u¯à¥Î¦b wd ³oӺϺÐÅX°Êµ{¦¡¤W¡]³o
Ó¥Nªí¤F FreeBSD 4.0 ¨Ã¤£¤ä´©¥¦¡^¡A¥¦¤]µLªk¥Î¦b SCSI µwºÐ¤W¡C
bad144ªº¤u§@¤èªk¬O±N©Ò¦³§ä¨ìªºÃay¸ê®Æ¦s¨ì¤@Ó¯S§OªºÀÉ®×ùØ¡C
¨Ï¥Î bad144 ªºÄµ§i - ¦sµÛÃay¸ê®Æªº¯S§OÀɮ׬O©ñ¦bµwºÐªº³Ì«á
¤@y¤W¡C¦]¬°³oÓÀÉ®×Àx¦sªºÃay¸ê®Æ¤¤¡A¦³¥i¯à¦³¨Ç¸ê®Æ¬O«ü¦VµwºÐ³Ì
«eºÝ©Òµo¥ÍªºÃay±¡§Î¡A´N¬O¥i¯àÀx¦s /kernel ³oÓÀɪº¦a¤è¡A©Ò¥H¥¦
¤@©wn¯à³Q¶}¾÷µ{¦¡©ÒŪ¨ú¡A¦Ó¶}¾÷µ{¦¡¬O³z¹L BIOS ¨ÓŪ¨ú kernel
ÀÉ¡C³oªí¥Ü¤F¨Ï¥Î bad144 ªºµwºÐµ´¤£¯à¾Ö¦³¶W¹L 1024 Ó cylinder¡A
16 Ó head ¤Î 63 Ó sector¡C¦Ó³o¨Ï±o±ý¨Ï¥Î bad144 ªºµwºÐªº¤j¤p¤£
¯à¤j©ó 500 MB¡C
n¨Ï¥Î bad144 «Ü²³æ¡A¥un¦b¶}©l¦w¸Ë®É¡A¦b FreeBSD fdisk µe±
§âBad Block
±½ºË³]¬° ON §Y¥i¡C¦b FreeBSD 2.2.7 ¥H
«á³£¥i¥H¨Ï¥Î¦¹¤èªk¡C¦ý³oÓµwºÐªº cylinder ¤@©wn¦b 1024 ¥H¤U¡C¨Ï
¥Î«e¡A§ÚÌ«Øij³oÓµwºÐn¦Ü¤Ö¥ý¨Ï¥Î¥|Ó¤p®É¡A¥H«K¼ö¿±µÈ»PºÏy°¾²¾
¹F¤@¯ëª¬ºA¡C
¦pªG³oÓµwºÐ¾Ö¦³¶W¹L 1024 Ó cylinder¡]¹³¤j®e¶qªº ESDI µwºÐ¡^
¡AESDI ±±¨î¥d§Q¥Î¤@Ó¯S§OªºÂà´«¼Ò¦¡¨Ï¥¦¯à¦b DOS ¤U¤u§@¡C¦Ó¦pªG±z
¦b fdisk ùتº set geometry
¤¤¿é¤J
Âà´«¹L
ªº geometry¡Awd ³oÓÅX°Êµ{¦¡¯à¤F¸Ñ³o¨ÇÂà´«
¼Ò¦¡¡C±z¤]µ´¹ï¤£¯à¨Ï¥Î dangerously dedicated ¼Ò¦¡¨Ó«Ø¥ß FreeBSD
ªº¤À³Î°Ï¡A¦]¬°¥¦·|©¿²¤ geometry ³oӰѼơC¦¹¥~¡A´Nºâ fdisk ¨Ï¥Î
±z©Ò¿é¤Jªº geometry °Ñ¼Æ¡A¥¦¨ÌµM·|¥hŪ¨ú³oµwºÐªº¯u¥¿¸ê®Æ¡A¦Ó·|¹Á
¸Õ¥h«Ø¥ß¤@Ó¹L¤jªº FreeBSD ¤À³Î°Ï¡C¦pªGºÏºÐªº geometry ¤w¸g³Q
Âà´«
¹L¤F¡A¨º»ò ³oÓ¤À³Î°Ï ¥²¶·
¥H¤â°Ê¿é¤J block ¼Æ¥Øªº¤èªk¨Ó«Ø¥ß¡C
¤@Ó§Ö³tªº¤p§Þ¥©¬O§Q¥Î ESDI ±±¨î¥d¨Ó³]©w¤j®e¶qªº ESDI µwºÐ¡A
¥Î DOS ¶}¾÷¤ù¶}¾÷¡A¦A±N¥¦ format ¬° DOS ªº¤À³Î°Ï¡CµM«á«¶}¾÷¶i¤J
FreeBSD ¦w¸Ëµ{§Ç¡A¦b fdisk µe±¡A§âDOS ¤À³Î°Ïªº blocksize ©M
block number §Û¤U¨Ó¡CµM«á«·s³]©w geometry ¨Ï¨ä¸ò DOS ¨Ï¥Îªº¤@¼Ë¡C
§R°£ DOS ¤À³Î°Ï¡AµM«á¨Ï¥Î±zèè§Û¤Uªº blocksize ¨Ó«Ø¥ß¤@Ó
cooperative
FreeBSD ¤À³Î°Ï¡CµM«á³]©w³oÓ¤À³Î°Ï¬°¥i
¶}¾÷¡A¦A¥´¶}Ãay±½ºË¡C¦b¯u¥¿ªº¦w¸Ë¹Lµ{¤¤¡Abad144 ·|¦b¥ô¦óÀɮרt²Î
³Q«Ø¥ß«e¥ý³Q°õ¦æ¡C¡]±z¥i¥H«ö Alt-F2 ¨ÓºÊ¬Ý³o¤@¤Á¡^¦pªG¦b«Ø¥ßÃay¸ê
®ÆÀɮɵo¥Í¤F°ÝÃD¡A±z·|»Ýn³]©w¤@Ó¸û¤jªººÏºÐ geometry - ³oªí¥Ü±z
»Ýn«¶}¾÷¡AµM«á¥þ³¡¦A«·s¶}©l¡]¥]¬A«·s¤À³Î¥H¤Î¦b DOS ¤U«·s
format¡^¡C
¦pªG remapping ªº¥\¯à¤w¸g±Ò°Ê¤F¡A¦Ó±z¨ÌµM¤@ª½¬Ý¨ìÃay²£¥Í¡A
¨º»ò¦Ò¼{´«¤@¥xµwºÐ§a¡CÃayªº±¡§Î¥u·|ÀH®É¶¡¼W¥[¦Ó§ó¬°ÄY«¡C
¬°¤°»ò FreeBSD §ì¤£¨ì§Úªº Bustek 742a EISA SCSI ¥d¡H
¤U±ªº¸ê°T¬Oµ¹ 742a ³o±i¥d¥Îªº¡A¦ý¬O¨ä¥L Buslogic ªº¥d©Î³\¤]
¥i¥H¾A¥Î¡C¡]Bustek ´N¬O Buslogic¡^
742a ³o±i¥d¦³¨âÓ¥Dnªºª©¥»
¡C¤@Ó¬Oª©¥» A-G¡A
¥t¤@Ó¬Oª©¥» H ¤Î¨ä¥H«á¡Cª©¥»¸ê°T¥i¥H±q¤¶±¥dÃä½tªº¬y¤ô¸¹³Ì«á±
±oª¾¡C742a ³o±i¥d¦³¨âÓ°ßŪ´¹¤ù¦b¥¦¤W±¡A¤@Ó¬O BIOS ´¹¤ù¡A¦Ó¥t
¤@Ó¬O¶´Åé´¹¤ù¡C FreeBSD ¨Ã¤£¦b¥G±z¥d¤Wªº BIOS ª©¥»¡A¦ý¬O¶´Å骺
ª©¥»´N«Ü«n¤F¡C¦pªG§A¥´¹q¸Üµ¹¥Ļ޳N¤ä´©±M½uªº¸Ü¡A¥LÌ·|±Hµ¹
±z³Ì·sªºª©¥»¨Ñ±z¤É¯Å¡C BIOS ©M¶´Åé´¹¤ù¬O¤@°_°e¨Óªº¡C ±z»Ýn±N¥d
¤W BIOS ©M¶´Å骩¥»¡A¨Ì±z¥dª©¥»ªº¤£¦P¡A¤É¯Å¨ì³Ì·sªº¤@ª©¡C
ª©¥» A-G ªº¥d³Ì°ª¥u¯à±N BIOS/¶´Åé ¤É¯Å¨ì 2.41/2.21 ª©¡A¦Ó H
¤Î¨ä¤§«áªºª©¥»¡A¥Ø«e BIOS/¶´Å骺³Ì·sª©¥»¬O 4.70/3.37¡C³o¨âÓ¶´Åé
ª©¥»¶¡ªº®t²§¦b©ó¡A3.37 ³oª©¤ä´© round robin
Buslogic ªº¥d¤W±¤]³£¦³§Ç¸¹¡C¦pªG±z¥dªºª©¥»¸û¡A±z¥i¥H¸ÕµÛ¥´
¹q¸Üµ¹ Buslogic ªºRMA ³¡ªù¡AµM«áµ¹¥Ḻzªº§Ç¸¹¡A¬Ý¯à¤£¯à¸ò¥LÌ¥æ
´«¤@±i¸û·sª©¥»ªº¥d¡C¦pªG¨º±i¥d°÷ªº¸Ü¡A¥LÌ·|´«µ¹§A¡C
FreeBSD 2.1 ¥u¤ä´©¶´Åé 2.21 ª©¥H«áªºª©¥»¡C¦pªG±z¶´Å骩¥»¤ñ³o
ÓÁÙªº¸Ü¡A¨º»ò±zªº¥d´N¤£¯à³Q¿ëÃÑ¥X¬O Buslogic ªº¥d¡C¥¦¦³¥i¯à·|
³Q¿ëÃѦ¨ Adaptec 1540¡C¸û¦ªº Buslogic ¥d¤Wªº¶´Å馳¤@Ó AHA1540
¼ÒÀÀ
¼Ò¦¡¡A³o¹ï¤@±i EISA ¥d¨Ó»¡¨Ã¤£¬O¥ó¦n¨Æ¡C
¦pªG±z¦³¤@±i¸ûª©¥»ªº¥d¡A¦Ó±z¨ú±o 2.21 ª©¶´Å骺¸Ü¡A±z»ÝnÀË
¬d¤@¤U jumper W1 ªº¦ì¸m¡A±N¥¦½Õ¦Ü B-C¡Aì©l³]©w¬O A-B¡C
¬°¤°»ò FreeBSD §ì¤£¨ì§Úªº HP Netserver ªº SCSI ±±¨î¥d¡H
°ò¥»¤W³oÓ¬O¤@Ó¤wª¾ªº°ÝÃD¡C¦b HP Netserver ¾÷¾¹¤Wªº on-board
EISA ¤¶± SCSI ±±¨î¥d¥e¾Ú¤F©w§}¬°²Ä 11 ªº EISA ¼Ñ¡A¦]¦¹©Ò¦³ªº
¯u¹ê
EISA ¼Ñ³£¦b¥¦¤§«e¡C¥i¬O¡A¦b EISA ©w§}ªÅ¶¡
>= 10 ®É¡A·|»P«ü©wµ¹ PCI ¥Îªº©w§}ªÅ¶¡¬Û½Ä¬ð¡A¥B FreeBSD ªº
auto-configuration µLªk¥¿½Tªº³B²z³oÓ±¡§Î¡C
¦]¦¹¡A²{¦b§A¯à°µªº³Ì¦n¨Æ±¡´N¬O¦b kernel ùس]©w
EISA_SLOTS ³oӿﶵ¬° 12 ¡AµM«á·í§@¨S¦³³oÓ
°ÝÃD :)¡C½Ð¨Ì·Ó
Handbook ¤¤¦³Ãö kernel ªº³]©w ùØ©Ò»¡ªº¤èªk¨Ó³]©w»P½sĶ
±zªº kernel¡C
·íµM¡A¦b¦w¸Ë FreeBSD ¨ì³oºØ¾÷¾¹¤W®É¡A³o¬O¤@ÓÂû¥Í³J³J¥ÍÂûªº
°ÝÃD¡C¬°¤F¸Ñ¨M³oÓ°ÝÃD¡A¦b UserConfig ¤¤¦³
¤@Ó¯S§Oªº¤èªk¡A¦w¸Ë®É¤£n¶i¤J visual
¤¶±¡A¬Û¤Ï
ªº¡A¦b©R¥O¦C¼Ò¦¡¤¤¡AÁä¤J
eisa 12
quit
µM«á´N¦p¥H©¹¤@¼Ë¦w¸Ë±zªº¨t²Î¡C¤£¹L§ÚÌ«Øij±z½sĶ»P¦w¸Ë¤@Ó
ÄÝ©ó¦Û¤vªº kernel¡A¦ý
§Æ±æ¦b¥¼¨Óªºª©¥»¤¤¯à¹ï³oÓ°ÝÃD¦³¤@Ó¦nªº¸Ñ¨M¤èªk¡C
±zµLªk¦b HP Netserver ¤W¨Ï¥Î
dangerously dedicated ºÏºÐ¼Ò¦¡¡C±z¥i¥H°Ñ¦Ò
³o¥÷µù¸Ñ ¥HÀò±o§ó¦h¸ê°T¡C
CMD640 IDE ±±¨î´¹¤ù¥X¤F¤°»ò°ÝÃD¡H
¥¦ªº°ÝÃD¦b©óµLªk¦P®É³B²z¨âÓ channel ªº«ü¥O¡C
²{¦b¤w¸g¦³Ó¸Ñ¨M¤èªk¤F¡A¦Ó¥B¦b±zªº¨t²Î¤¤¦³³o¶ô´¹¤ù®É·|¦Û°Ê
±Ò°Ê¡C¦pªG»Ýn§ó¸ÔºÉªº¸ê°T¡A½Ð¬d¾\¦³ÃöºÏºÐÅX°Êµ{¦¡ªº»¡©ú
¡]man 4 wd¡^¡C
¦pªG±z¥Ø«e¬O¨Ï¥Î CMD640 IDE ±±¨î´¹¤ù¡A¥[¤W FreeBSD 2.2.1 ©Î
2.2.2¡A¦Ó¥B±z¤S·Qn¨Ï¥Î¨ì²Ä¤GÓ channel ®É¡A½Ð¦b±zªº kernel ³]
©w¤¤¥[¤J options "CMD640" µM«á«·s½sĶ¤@Ó·s
ªº kernel¡C³oÓ option ¦b 2.2.5 ª©¥H«á¬O¤º©w±Ò°Êªº¡C
§Ú¤@ª½¬Ý¨ìÃþ¦ü
ed1: timeout ªº°T®§¡C¥¦Ì¬O¤°»ò·N«ä©O¡H
³oÓ³q±`¬O¥Ñ©ó¤¤Â_½Ä¬ð¡]interrupt conflict¡^©Ò³y¦¨ªº¡]¨Ò¦p¡A
¨â¶ô¥d¨Ï¥Î¨ì¤F¬Û¦Pªº IRQ¡^¡C FreeBSD ¦b 2.0.5 ª©¥H«e³£®e³\³oÓ
±¡§Î¡A´Nºâ¦³ IRQ ½Ä¬ð±¡§Î¡Aºô¸ô¥d¤]À³¸Ó¤´¥i¥¿±`¹B§@¡CµM¦Ó¡A¦b
2.0.5 ª©¤Î¨ä¥H«á¡A¤w¤£¦A®e³\¦³ IRQ ½Ä¬ðªº±¡§Î¤F¡C½Ð©ó¶}¾÷®É¨Ï
¥Î -c ³oӿﶵ¡AµM«á§ó§ï ed0/de0/..¡Cµ¥ªº³]©w¡A¨Ï¨ä©M±zºô¸ô¥d
¥»¨ªº³]©w¤@P¡C
¦pªG±z¬O¨Ï¥Î±zºô¸ô¥d¤Wªº BNC ±µÀY¡A±z©Î³\¤]·|¦]¤£¨}ªº²×ºÝ¹q
ªý³]©w¡A¦Óµo¥Í¸Ë¸m (device) timeout ªº±¡§Î¡CnÀˬd¬O§_¦³³oºØ±¡
§Î¡A±z¥i¥H¦bºô¸ô¥d¤Wª½±µ±µ¤W²×ºÝ¹qªý¡]¤£n±µºô¸ô½u¡^¡AµM«á¬Ý¬Ý³o
Ó¿ù»~°T®§¬O¤£¬O´N®ø¥¢¤F¡C
¦³¨Ç NE2000 ªº¬Û®e¥d¡A¦pªG¥¦ªº UTP °ð¨S¦³±µºô¸ô½u¡A©Î¬O¸Óºô
¸ô½u¨Ã¨S³Q¨Ï¥Îªº¸Ü¡A¤]·|¥X²{³oÓ¿ù»~°T®§¡C
¬°¤°»ò§Úªº 3COM 3C509 ³o¶ôºô¸ô¥d¦b¨S¦³¥ô¦ó©úÅãì¦]¤U°±¤î¤u§@
¤F©O¡H
³o¶ô¥d¦³Ó¤£¦nªº¦a¤è¦b©ó¥¦±`±`·|¿ò¥¢¥»¨ªº³]©w¸ê®Æ¡C½Ð¨Ï¥Î¸Ó
¥dªº DOS ¤u¨ã 3c5x9.exe ¨Ó§ó·s¥d¤W³]©w¡C
§Úªº¥¦æ°ð¦Lªí³t«×¯}¤Ñ¯îªººC¡C§Ú¸Ó«ç»ò°µ¡H
¦pªG°ß¤@ªº°ÝÃD´N¬O³t«×«ÜºCªº¸Ü¡A¸ÕµÛ§ïÅܱzªº
¦Lªí¾÷³s±µ°ð³]©w ³oÓ¦b¤â¥U¤¤ªº
¦Lªí¾÷³]©w
³oÓ³¹¸`¦³¥[¥H°Q½×¡C
§Úªºµ{¦¡¦³®É·|¦]
Signal 11 ³oÓ¿ù»~¦Ó°±¤î¡H
Signal 11 ³oÓ¿ù»~¬O¦]¬°§Aªº process ¹Á¸Õn¦s¨ú¤@¶ô°O¾ÐÅé¡A
¦Ó§Aªº§@·~¨t²Î¨Ã¤£¤¹³\¥¦°µ³oӰʧ@¦Óµo¥Íªº¡C¦pªG³oºØ±¡§Î±`±`¤£
©w®Éµo¥Í¡A¨º»ò§AÀ³¸Ón¶}©l¬Ý¬Ý¬O¤£¬Oþ¸Ì¥X°ÝÃD¤F¡C
³o¨Ç°ÝÃD¥i¯à¬O»P¤U¦C±¡§Î¦³Ãö¡G
¦pªG³oÓ°ÝÃD¥u¦b¬Y¤@Ó±z¦Û¤v¼gªº¬YÓ¯S©wµ{¦¡µo¥Í¡A¨º
»ò«Ü¦³¥i¯à¬O±zªºµ{¦¡½X¦³°ÝÃD¡C
¦pªG³oÓ°ÝÃD¬O¦b FreeBSD ªº¬Y¨Ç¨t²ÎÀÉ®×µo¥Í¡A¦³¥i¯à¬O
¦]¬°µ{¦¡¦³°ÝÃD¡A¦ý³q±`¦b§Ú̳o¸sŪ FAQ ªº¨Ï¥ÎªÌ¥h¶]³o¨Ç¦³
°ÝÃDªºµ{¦¡½X«e¡A¥¦Ì¦´N´N¤w¸g³Q¸Ñ¨M¤F¡]³o¬O -current ¦b°µ
ªº¨Æ¡^¡C
¤×¨ä¦pªG§A¦b½sĶ¤@Óµ{¦¡¡A¦ý¬O¨C¦¸½sĶ¾¹¶]¥X¨Óªºµ²ªG³£¤£¤@¼Ë
ªº¸Ü¡A³o¬O¤@ÓµL¸Ñªº°ÝÃD¡A¦Ó¤£¬O
FreeBSD ¯äÂΡC
Á|¨Ò¨Ó»¡¡A°²³]±z¥¿¦b¶] make buildworld
¡A
¦Ó compiler ¦b±N ls.c ½sĶ¦¨
ls.o ®Éµo¥Í¿ù»~¡A³o®É½Ð¦A¶]¤@¦¸
make buildworld
¡A¦pªG compiler ¨ÌµM¦b¦P¼Ëªº¦a¤èµo
¥Í°ÝÃD¡A¨º»ò´N¬Oµ{¦¡½X¦³°ÝÃD¡Ð¡Ð½Ð§ó·sì©l½XµM«á¦A¸Õ¸Õ¬Ý¡C¦Ó¦pªG
compiler ¬O¦b¨ä¥Lªº¦a¤èµo¥Í¿ù»~¡A¨º»ò´X¥G¥i¥H½T©w¬OµwÅ骺°ÝÃD¤F¡C
±z³o®ÉÀ³¸Ó°µ¤°»ò¡G
¦pªG¬O²Ä¤@ºØ±¡§Î¡A¥i¥H¨Ï¥Î¤@¨Ç debugger¡A¦p¡Ggdb¡A¨Ó§ä¥Xµ{¦¡
¬O¦b¨º¨à·|¥h¹Á¸Õ¦s¨ú¿ù»~ªº°O¾ÐÅé¦ì§}¡AµM«á¦A×¥¿¥¦¡C
¦pªG¬O²Ä¤GºØ±¡§Î¡A´N»ÝnÀˬd¬Ý¬Ý¬O¤£¬OµwÅ骺°ÝÃD¤F¡C
¤@¨Ç³y¦¨µwÅ餣êºì¦]¥]¬A¡G
¥i¯à¬OµwºÐ¹L¼ö¡G½ÐÀˬd¾÷´ß¤ºªº·®°¬O§_¹B§@¥¿±`¡A¦]¬°±z
ªºµwºÐ¡]©ÎªÌÁÙ¦³¨ä¥LªºµwÅé¸Ë¸m¡^¹L¼ö¤F¡C
³B²z¾¹¹L¼ö¡G³oÓ¦³¥i¯à¬O¦]¬°¶WÀW¡A©ÎªÌ¬O³B²z¾¹ªº·®°±¾¤F¡C
¤£½×¬OþºØì¦]¡A±z³£»Ýn±N©Ò¦³ªº¤¸¥ó¦^´_¨ì¥¦Ìì¥ý³]©wªº¤u§@ª¬
ºA¡A³o¼Ë¤~¯à¸Ñ¨M³oÓ°ÝÃD¡CÁ|Ó¨Ò¤l¨Ó»¡¡G±N³B²z¾¹½Õ¦^ì¥ýªº¤u§@
ÀW²v¡C
¦pªG±zÁÙ¬O°í«ùn¶WÀWªº¸Ü¡A½ÐÂÔ°O¡A»P¨ä¿NÃa¦Ó»Ýn´«·sªº¤@¥x
¥D¾÷¡A¤£¦p±N³t«×½ÕºC¤@ÂI¡I°£¦¹¤§¥~¡A¤£ºÞ§Aı±o¥¦¦w¤£¦w¥þ¡A¤@¯ë
¤H¹ï©ó±z¦]¬°¶WÀW¦Óµo¥Íªº°ÝÃD¡A¬O¤£·|¦³¤°»ò¦P±¡¤ßªº¡C
¤£Ã©wªº°O¾ÐÅé¡G¦pªG¥D¾÷¤W¦³¦w¸Ë¼Æ®Ú SIMM/DIMM °O¾ÐÅé¡A
¸ÕµÛ§â¥¦Ì¥þ©î¤U¨Ó¡AµM«á¤@®Ú¤@®Ú´¡¤W¥h°µ´ú¸Õ¡AÂǦ¹ÁY¤p½d³ò¡A
¥H«K§ä¥X¦³°ÝÃDªº¬Y®Ú°O¾ÐÅé©Î¬O¬YºØ°O¾ÐÅé²Õ¦X¡C
³Ì¨Î¤Æ¹LÀYªº¥D¾÷ªO³]©w¡G¦b BIOS ùةάO¦³¨Ç¥D¾÷ªOªº jumper
¤W¡A¦³®É¥i¥H§ó§ï¤@¨Ç timing¡A¦ý¦b¤j¦h¼Æªº±¡§ÎùØ¡A¨Ï¥Î¹w³]È´N
¤w¸g¨¬°÷¤F¡Cªp¥B¦³®ÉÔ§â RAM ªº wait states ³]¤Ó¤p¡A©Î¬O¦b
BIOS ùØ¡A§â RAM Speed: Turbo
³oөάO¨ä¥LÃþ¦ü
ªº¿ï¶µ¥´¶}³£¦³¥i¯à·|³y¦¨¤@¨Ç¤£¥¿±`ªº²{¶H¡C¤@ӸѨMªº¤èªk¬O§â
BIOS ³]¦^¹w³]È¡A¤£¹L¦b³o¤§«e°O±o¥ý°O¤U¥Ø«eªº³]©w¡I
¨Ñµ¹¥D¾÷ªOªº¹q¤O¤£°®²b©Î¬O¤£¨¬¡C¸ÕµÛ§â¨t²Î¤º¨S¦³¥Î¨ìªº
I/O ¥d¡DµwºÐ©Î¬O CDROM ¼È®É©î±¼©Î¬O©Þ±¼¹q·½½u¡A¬Ý¬Ý§Aªº¹q·½
¨ÑÀ³¾¹¬O¤£¬O¯à°÷¦b¤p¤@ÂIªºt²ü¤U¥¿±`¤u§@¡C¤£µM´N¬O´«¤W¥t¤@
Ó·sªº¹q·½¨ÑÀ³¾¹¡A³Ì¦n¬O¥Ë¼Æ°ª¤@ÂIªº¡]¥´Ó¤ñ¤è¨Ó»¡¡A¦pªGì
¥ýªº¹q·½¨ÑÀ³¾¹¬O 250 ¥Ëªº¡A¨º»ò´N´«¤W 300 ¥Ëªº¸Õ¸Õ¡^¡C
½Ð¶¶«K°Ñ¾\ SIG11 FAQ¡]³sµ²¦b¤U±¡^¡AÁöµM¥¦¬O¯¸¦b Linux ªº¨¤
«×¼gªº¡A¥i¬O¸Ì±¹ï³o¨Ç°ÝÃD¦³³\¦h«Ü´Îªº¸Ñ»¡¡C¥¦¸Ì±¤]¦³°Q½×¬°¤°»ò
¦³°ÝÃDªº°O¾ÐÅé¯à³q¹L³nÅé©ÎµwÅ骺´ú¸Õªºì¦]¡C
³Ì«á¡A¦pªG¤W±³o¨Çì¦]³£±Æ°£¤F¡A¨º»ò¦³¥i¯à¬O¹J¨ì¤F FreeBSD
ùتº¤@°¦¯äÂΡA½Ð°Ñ¾\«ü¥Ü°µ¤@Ó°ÝÃD¦^³ø¡C
³o¨à¦³¤@Ó§ó¸Ô²Óªº FAQ ¡Ð
the SIG11 problem FAQ
§Úªº¨t²Î·í¾÷®É¥X²{¡GFatal
trap 12: page fault in kernel mode ¡A©Î¬O
panic: ¡A¦A¥[¤W¤@°ï¿ù»~°T®§¡A
§Ú¸Ó«ç»ò¿ì¡H
FreeBSD ªº¶}µoªÌ¹ï©ó³o¨Ç¿ù»~°T®§¬Û·íªº¦³¿³½ì¡A¦ý¬O¥LÌ»Ýn
§ó¸Ô²Óªº¤@¨Ç²Ó¸`¡C½Ð§â±zªº·í¾÷ªº°T®§¥þ³¡½Æ»s¤U¨Ó¡A±µµÛ¬d¾\ FAQ
ùØ kernel
panics ³o¸`¡A¨Ì»¡©ú½sĶ¤@Ó§t°£¿ù½Xªº kernel¡A¥H¨ú±o¨ç¦¡
©I¥s¶¶§Ç¡]backtrace¡^¡C³oÓÅ¥°_¨Ó«ÜÃø¡A¦ý¹ê»Ú¤W¨Ã¤£»Ýn¥ô¦óµ{¦¡
³]pªº¯à¤O¡A±z¥u»Ýn¨Ì·Ó«ü¥Ü°µ§Y¥i¡C
¬°¤°»ò·í§Ú¶}¾÷®É¡A¿Ã¹õÅܶ¡A¥B¤£°±°{°Ê¡H
³oÓ°ÝÃD¡A¤wª¾¬O¥Ñ ATI Mach 64 Åã¥Ü¥d©Ò¤Þ°_ªº¡C¦]¬°³o¶ô¥d
¨Ï¥Î¨ì 2e8 ³oÓ¦ì§}¡A¦Ó³o»P²Ä¥|ӧǦC°ð
¡]serial port¡^©Ò¨Ï¥Îªº¦ì§}¬Û¦P¡C¦Ó¦b &man.sio.4; ³oÓÅX°Ê
µ{¦¡ùØ¡A¤£ª¾¹D¬O bug ©Î¬O¥\¯à¡]feature¡^¡A´Nºâ±z¨S¦³²Ä¥|Ó§Ç
¦C°ð¡A©Î¬O¤w¸g±N sio3¡]²Ä¥|ӧǦC°ð¡^¨ú®ø¤F¡A¥¦
¨ÌµM ·|¥h¹Á¸ÕÅX°Ê¥¦¡C
ª½¨ì³oÓ°ÝÃD³Q¸Ñ¨M¥H«e¡A±z¥i¥H¨Ï¥Î³oÓ¤èªk¡G
¦b¬Ý¨ì¶}¾÷´£¥Ü®É¿é¤J -c
¡]³o·|Åý kernel ¶i¤J³]©w¼Ò¦¡¡^¡C
¨ú®ø sio0 ¡A
sio1 ¡A
sio2 ©M
sio3 ¡]¥þ³¡¡^¡C
³o¥i¥HÅý sio ÅX°Êµ{¦¡¤£°Ê§@ -> ©ó¬O°ÝÃD¸Ñ¨M¡C
¿é¤J exit ¥HÄ~Äò±Ò°Êµ{§Ç¡C
¦pªG±z·Qn¨Ï¥Î±zªº§Ç¦C°ð¡A±z»Ýnקï
/usr/src/sys/i386/isa/sio.c ¡A¦b¸ÓÀɤ¤§ä¥X
0x2e8 ³oÓ¦r¦ê¡A²¾°£³oÓ¦r¦ê¤Î¥¦«e±ªº³r¸¹
¡]«O¯d«á±ªº¡^¡AµM«á«·s½sĶ¤@Ó·sªº kernel¡C
´Nºâ¨Ï¥Î¤F¤W±³o¨Ç¤èªk¡AX Window ¤´µM¦³¥i¯àµLªk¶¶§Q°õ¦æ¡C
¦pªGµo¥Í¤F³oºØ±¡§Î¡A½Ð½T©w§A¥Îªº XFree86 ªºª©¥»¬O³Ì·sªº XFree86
3.3.3 ©Î¬O¨ä«áªºª©¥»¡C¥¦Ì¦³¤º«Ø¤ä´© Mach 64 ³o±i¥d¡A¬Æ¦Ü¬°¤F³o
¨Ç¥dÁÙªþ¦³¤@Ó¯S§Oªº X Server
¬°¤°»ò§Úªº¨t²Î¸Ë¦³ 128 MB ªº RAM¡A¦Ó FreeBSD ¥u¥Î¤F¨ä¤¤ªº
64MB¡H
¦]¬° FreeBSD ¬O¨Ï¥Î©I¥s BIOS ¨Ó¨ú±o°O¾ÐÅé¤j¤pªº¤èªk¡A¦]¦¹¥¦
¥u¯à°»´ú¨ì 16 bits ¦ì¤¸ªø«×ªº KByte ¤j¤p¡]65535 KBytes = 64MB¡^
¡]©ÎªÌ§ó¤Ö..¡C¦³¨Ç BIOS ±N³Ì°ª°O¾ÐÅé¤j¤p¬°¥u¦³ 16MB¡^
¦pªG±z¾Ö¦³ 64MB ¥H¤Wªº RAM¡AFreeBSD ·|¹Á¸Õ¥h°»´ú¥X¥¦¡A¦ý¬O¦³¥i¯à
·|¥¢±Ñ¡C
n¸Ñ¨M³oÓ°ÝÃD¡A±z»Ýn¨Ï¥Î¤U±©Ò´£ªº kernel ³]©w¿ï¶µ¡CÁöµM¦³
¤èªk¥i¥H±q BIOS ¤¤¨ú±o°O¾ÐÅ骺§¹¾ã¸ê°T¡A¦ý¬O¥Ø«e§Ú̦b¶}¾÷°Ï¤¤¨Ã
¨S¦³¦h¾lªºªÅ¶¡¨Ó°µ³o¥ó¨Æ¡C·í¬Y¤Ñ¶}¾÷°ÏªÅ¶¡¤£¨¬ªº±¡§ÎÀò±o¸Ñ¨M®É¡A
§Ú̱N·|¨Ï¥Î BIOS ªº©µ¦ù¥\¯à¨Ó¨ú±o°O¾ÐÅ骺§¹¾ã¸ê°T...¦ý²{¦b§ÚÌ
±N¥¦©ñ¦b kernel ³]©w¿ï¶µ¤¤¡C
options "MAXMEM=n "
n ¬O«ü±zªº°O¾ÐÅé¤j¤p¡A¥H KB
¬°³æ¦ì¡C¥H¤@¥x¦³ 128MB RAM ªº¾÷¾¹¨Ó»¡¡A±z¥i¨Ï¥Î
131072 ³oӼƦr¡C
¬°¤°»ò FreeBSD 2.0 ¦]¬°
kmem_map too small! ³oÓì¦]¦Óµo¥Í
panic ¡H
³oÓ°T®§¤]¦³¥i¯à¬O
mb_map too small!
³oÓ panic ªºì¦]¬Oªí¥Ü¨t²Î¥Î¥ú¤Fµ¹ºô¸ô½w½Ä°Ïªº©Ò¦³ªºµê
ÀÀ°O¾ÐÅé¡]¯S§O¬O mbuf clusters¡^¡C±z¥i¥H¼W¥[µ¹ mbuf clusters
ªº VM ªº¼Æ¶q¡A¥un¥[¤J:
options "NMBCLUSTERS=n "
¦b±zªº kernel ³]©wÀɤ¤¡An
¬O¤@Ó¦b 512-4096 ¶¡ªº¼Æ¦r¡A¨Ì±z·Q´£¨Ñ¦h¤Ö¦P®Éªº TCP ³s±µ¼Æ¥Ø
¦h¹è¦Ó©w¡C§Ú·|«Øij¸Õ¸Õ 2048 - ³o¼Æ¦rÀ³¸Ó¥i¥H§¹¥þÁקK³oÓ panic
¤F¡C±z¥i¥H°õ¦æ: netstat -m
¡]see &man.netstat.1;¡^¨ÓºÊ¬Ý¦³¦h¤Ö mbuf clusters ¦b¨t²Î¤W¥¿³Q
°t¸m/¨Ï¥Î¡CNMBCLUSTERS ªº¼ÆȤº©w¬° 512 + MAXUSERS * 16
¡C
¬°¤°»ò§Ú¤@ª½¬Ý¨ì /kernel: proc: table
is full ³oÓ¿ù»~°T®§¡H
FreeBSD ªº kernel ¥u·|¤¹³\¤@©w¼Æ¶qªº process ¦b¦P¤@®É¶¡¸Ì¦P
®É¹B§@¡C¦Ó³oӼƥجO®Ú¾Ú kernel ³]©wÀɸ̱ªº
MAXUSERS ȨӨM©wªº¡CMAXUSERS
³oÓȤ]·|¼vÅT¨ä¥Lªº kernel ¤º©wÈ¡A¤ñ¦p»¡ºô¸ô½w½Ä°Ï
¡]½Ð°Ñ¾\ ³oÓ¤§«e°Q
½×¹Lªº°ÝÃD¡^¡C¦pªG¾÷¾¹t²ü¡]load¡^«Ü«¡A±z¥i¯à»Ýn¼W¥[
MAXUSERS ³oÓÈ¡C³o»ò§@·|¤@¨Ö´£°ª¨t²Îªº¨ä¥L¤º
©wÈ¡A¥]¬A³Ì¤j¥i¾Ö¦³ªº process ¼Æµ¥¡C
¦b FreeBSD 4.4 ¤§«á¡AMAXUSERS ¤w¸gÅܦ¨¥i
¥H¾aµÛ§ó§ï /boot/loader.conf ùتº
kern.maxusers ³oÓȦӽվ㪺ÅܼƤF¡C¦Ó¦b¤§«e
ªº FreeBSD ª©¥»¤¤¡A³oÓÈ¥u¯à¦b kernel ³]©wÀÉùؽվã¡C
¦pªG¾÷¾¹t²ü¨Ã¤£«¡A¦Ó±z¥u¬O»Ýn¦P®É¶]«Ü¦h«Ü¦h process¡A
¨º»ò¤]¥i¥Hª½±µ¥Î sysctl ½Õ¾ã kern.maxproc
³oÓÈ¡C°²¦p³o¨Ç process ³£¬OÄÝ©ó¬YӨϥΪ̪º¡A¨º»ò±zÁÙ»Ýn¥t
¥~½Õ¾ã kern.maxprocperuid ³oÓÈ¡A¨Ï¥¦¤ñ·s
ªº kern.maxproc ³oÓȤ֤@¡]¤@©wn¤Ö¤@¡A
¦]¬° &man.init.8; ³oÓ¨t²Îµ{¦¡µ´¹ïn«O«ù¦b¹B§@ª¬ºA¡^¡C
¦pªG·Q¦b¨C¦¸¶}¾÷³£n§ó§ï sysctl ªºÈ¡A¦Ó¥B±zªº FreeBSD ¬O
³Ìªñªºª©¥»ªº¸Ü¡A½Ð¦b /etc/sysctl.conf ³o
ÓÀɤ¤³]©w¡A¦Ó¦pªG¬Oªºª©¥»¡A¥i¥H¦b
/etc/rc.local ¤¤§@³]©w¡C
¬°¤°»ò¥Î·s kernel ¶}¾÷®É¡A¥X²{ CMAP
busy ³oÓ¿ù»~°T®§¡H
¥Î¨Ó°»´ú¹L®É
/var/db/kvm_*.db Àɮתº¾÷¨î°¸º¸·|
µo¥Í°ÝÃD¡A¦Ó¨Ï¥Î¨ì¤F¤@Ó¤£¨ó½Õ¡]mismatch¡^ªºÀɮצ³®É´N·|¾ÉP
panic¡C
¦pªGµo¥Í¤F³oÓ°ÝÃD¡A½Ð«·s¶}¾÷¡A¶i¤J³æ¨Ï¥ÎªÌ¼Ò¦¡¡AµM«á°õ
¦æ¡G
&prompt.root; rm /var/db/kvm_*.db
½Ð°Ý³oÓ°T®§¡Gahc0: brkadrint,
Illegal Host Access at seqaddr 0x0
¬O¤°»ò·N«ä¡H
³o¬O¤@Ó©M Ultrastor SCSI ±±¨î¥d¦³Ãöªº½Ä¬ð¡]conflict¡^¡C
¦b¶}¾÷®É¡A¶i¤J kernel ³]©w¿ï³æ¨ú®ø
uha0 ¡A¥¦¬O³y¦¨³oÓ°ÝÃDªºì¦]¡C
¦b¶}¾÷®É¡A§Ú¬Ý¨ì³oÓ¿ù»~°T®§
ahc0: illegal cable configuration ¡C
§Úªº±Æ½u½T©w¦³±µ¹ï¡C ¬O¥X¤F¤°»ò°ÝÃD©O¡H
±zªº¥D¾÷ªO¥i¯à¤£¤ä´©¦Û°Ê²×ºÝ¹qªý³]©w¡C½Ð¶i¨ì SCSI ªº BIOS
¸Ì±¤â°Ê«ü©w¥¿½Tªº²×ºÝ¹qªý¶¶§Ç¡A¦Ó¤£n¨Ï¥Î¦Û°Ê³]©w¡CAIC7XXX ªº
ÅX°Êµ{¦¡¨ÃµLªkª¾¹D¦³¨S¦³³o¨Ç±Æ½u°»´ú¡]¥H¤Î¦Û°Ê²×ºÝ¹qªý³]©w¡^ªº
¹q¸ô¡]external logic¡^¦s¦b¡C¦pªG EEPROM ¸Ì±ªº³]©w¬O
"automatic termination" ®É¡A¥¦¥u·|³æ¯Â°²©w³o¨Ç¹q¸ô·íµM¬O¦s¦bªº¡C
Y¯Ê¤Ö¤F³oÓ¹q¸ô¡AÅX°Êµ{¦¡¦b³]©w²×ºÝ¹qªý®É´N±`±`¥X°ÝÃD¡C
¦Ó³oºØ°ÝÃD±N¾ÉP SCSI ¶×¬y±Æªº¥i¾a©Ê°§C¡C
¬°¤°»ò Sendmail ¤@ª½¥X²{
mail loops back to myself
³oÓ¿ù»~°T®§¡H
³oÓ°ÝÃD¦b sendmail ªº FAQ ¤¤¬O³o¼Ë¦^µªªº:-
* §Ú¤@ª½¦¬¨ì¦³Ãö "Local configuration error" ªº«H¥ó¡A¨Ò¦p¡G
553 relay.domain.net config error: mail loops back to myself
554 <user@domain.net>... Local configuration error
§Ún¦p¦ó¸Ñ¨M³oÓ°ÝÃD¡H
±z§Q¥Î MX ³]©w¡AÅýn±H¨ì¬Y domain¡]¦p: domain.net¡^ªº«H¥ó¡A
±H¨ì±z©Ò«ü©wªº¾÷¾¹¡]¦b³oÓ¨Ò¤l¤¤¬° relay.domain.net¡^¡A¦ý¬O³o
³¡¾÷¾¹¨Ã¥¼³Q³]©w±µ¨ü domain.net ªº«H¥ó¡C½Ð§â domain.net ¥[¨ì
/etc/sendmail.cw ¤¤¡]¦pªG±z¦³¨Ï¥Î FEATURE(use_cw_file)) ©Î¬O
¦b sendmail.cf ¤¤¥[¤J "Cw domain.net"
³Ì·sª©¥»ªº sendmail
FAQ ²{¦b¤w¤£¦AÀHµÛ sendmail ¥X³f
¡C
¥¦¥Ø«e¬O³Q©w´Áªºµoªí¦b comp.mail.sendmail ¡A
comp.mail.misc ¡Acomp.mail.smail ¡Acomp.answers ¡A©M news.answers . ±z¤]¥i¥H±H¤@«Ê
Email ¨ì mail-server@rtfm.mit.edu ¡AµM«á¦b«H¥ó¤º¤å
¤¤¼g¤W
send usenet/news.answers/mail/sendmail-faq
¥H¨ú±o³o¥÷ FAQ ¤å¥ó¡C
¬°¤°»ò°õ¦æ»·ºÝ¾÷¾¹¡]remote machine¡^ªº¥þ¿Ã¹õªº³nÅé®É¡A
¦³¤£¥¿±`ªº±¡§Î¡H
©Î³\»·ºÝ¾÷¾¹¨Ã«D±N±zªº²×ºÝ¾÷¼Ò¦¡³]¬° FreeBSD console ©Ò¥Îªº
cons25 ¡A¦Ó¬O³]¬°¨ä¥¦¼Ò¦¡¡C
³o¨à¦³´XӸѨM³oÓ°ÝÃDªº¤èªk¡G
¦b logging ¶i»·ºÝ¾÷¾¹«á¡A§ó§ï±zªº shell ÅÜ¼Æ TERM ¬°
ansi ©Î¬O sco
¡}¦pªG»·ºÝ¾÷¾¹¤ä´©³o¨Ç¼Ò¦¡ªº¸Ü¡^¡C
¨Ï¥Î¤ä´© VT100 ªº¼ÒÀÀ³nÅé¡A¦p FreeBSD console ¤Uªº
screen ³nÅé¡C
screen ´£¨Ñ±z¦b¤@Ó terminal
ùئP®É¶]¦n´XÓ session ªº¯à¤O¡A¦Ó¥B¥¦¥»¨¤]¬O¤@Ó¬Û·í¦n
ªº³nÅé¡C¨CÓ screen ³£¹³¬O¤@Ó
VT100 ªº²×ºÝ¾÷¡A©Ò¥H»·ºÝ¾÷¾¹ªº TERM ÅܼÆÀ³¸Ó³]¬°
vt100 ¡C
¦b»·ºÝ¾÷¾¹ªº²×ºÝ¾÷¸ê®Æ®w¡]terminal database¡^¤¤¥[¤J
cons25 ªº¸ê®Æ¡C¥[¤Jªº¤èªkµø»·ºÝ¾÷¾¹ªº
§@·~¨t²Î¤£¦P¦Ó¦³©Ò®t²§¡C½Ð°Ñ¾\»·ºÝ¾÷¾¹µ¹¨t²ÎºÞ²zûªº»¡©ú
®Ñ¡AÀ³¸Ó·|¦³©ÒÀ°§U¡C
±Ò°Ê FreeBSD ªº X ¦øªA¾¹¡AµM«á¨Ï¥Î¤@¨Ç X Window ¤Uªº
²×ºÝ¾÷¼ÒÀÀ¾¹¨Óµn¤J»·ºÝ¾÷¾¹¡A¨Ò¦p xterm
©Î rxvt ¡C¦Ó»·ºÝ¾÷¾¹ªº TERM ÅܼÆÀ³¸Ón
³]¬° xterm ©Î vt100 ¡C
¬°¤°»ò§Úªº¾÷¾¹¤@ª½Åã¥Ü
calcru: negative time... ¡H
¸ò¤¤Â_¡]interrupt¡^¦³Ãöªº¤£¦PµwÅé »P/©Î ³nÅ骺·f°t³£¦³¥i¯à³y¦¨
³oÓ°ÝÃD¡C³o¦³¥i¯à¬O bug ©Î¬O¬YӸ˸m¥»¨ªº°ÝÃD¡C¦b¥¦æ°ð¤W¨Ï¥Î
¤jªº MTU ¨Ó§@ TCP/IP ¶Ç¿é¥i¥H«²{³oÓ°ÝÃD¡CY¬O¹Ï§Î¥[³t¥d³y¦¨³oÓ
°ÝÃDªº¸Ü¡A±zÀ³¸Ó¥ýÀˬd¥dªº¤¤Â_³]©w¡C
³oÓ°ÝÃDªºÃä»Ú®ÄÀ³¬O·|³y¦¨¦³¨Ç process ¥X²{
SIGXCPU exceeded cpu time limit
ªº°T®§¡A¦Ó¤£¥¿±`
°±¤î¡C
Y¬O FreeBSD 3.0 ©Î¬O 1998 ¦~ 11 ¤ë 29 ¤é¥H«á¨ä¥Lª©¥»¡A¸U¤@
³oÓ°ÝÃD¤@ª½µLªk¥H¨ä¥L¤èªk¸Ñ¨M¡A´N¥u¯à³]©w sysctl ÅܼơG
&prompt.root; sysctl -w kern.timecounter.method=1
³o¼Ë·|¹ï®Ä¯à¦³¨Ç¼vÅT¡A¦ý¬OY¦Ò¼{¨ì³oÓ°ÝÃD±a¨Óªº«áªG¡A³o¼Ë°µ
¬Oȱoªº¡C¦pªG³oÓ°ÝÃDÁÙ¬O¦s¦bªº¸Ü¡AÅý sysctl ¨ºÓȨ̵M³]¬° 1¡A
µM«á¼W¥[ kernel ³]©wÀɤ¤ NTIMECOUNTER ³oÓ¿ï
¶µªº¼ÆÈ¡C¦pªG±z±N NTIMECOUNTER ¼W¥[¨ì 20 ¨Ì
µMµLªk¸Ñ¨M³oÓ°ÝÃD¡A¨º»ò±z¾÷¾¹¤Wªº¤¤Â_¤w¸g¦h¨ìµLªkÅýp¼Æ¾¹ºû«ù¦b
¥i¾aªºª¬ºA¤F¡C
¥X²{ pcm0 not found ³oÓ°T®§¡A©ÎªÌ¬O
§Úªºµ®Ä¥dÅܦ¨¤F pcm1 ¡A¦ý¦b kernel ³]©w
ÀÉùاڬO³] device pcm0 °Ú¡C³o¬O«ç»ò¦^¨Æ©O¡H
¦pªG±z¦b FreeBSD 3.x ¤W¨Ï¥Î PCI µ®Ä¥d´N·|µo¥Í³oºØ°ÝÃD¡C
¦]¬°pcm0 ³oÓ device ¬O¤º©w«O¯dµ¹ ISA
ªºµ®Ä¥dªº¡A©Ò¥H¦pªG±z¦³¤@±i PCI ªºµ®Ä¥d¡A±z´N·|¹J¨ì³oÓ°ÝÃD¡A
¦Ó±zªº¥d·|Åܦ¨ pcm1 ¡C
¦pªG±z¥u§â kernel ³]©wÀɤ¤ªº³]©w§ï¦¨
device pcm1 ¬OµLªk°£¥h³oÓĵ§i°T®§ªº¡A
³o¼Ë·|³y¦¨ pcm1 ³Q«O¯dµ¹ ISA µ®Ä¥d¡A
¦Ó PCI µ®Ä¥d«h·|Åܦ¨ pcm2
¡]¥~¥[ pcm1 not found ªºÄµ§i°T®§¡^¡C
¦pªG±z¦³¤@±i PCI ªºµ®Ä¥d¡A±z»Ýn make
snd1 ³oÓ device¡A¦Ó¤£¬O
snd0 ¡G
&prompt.root; cd /dev
&prompt.root; ./MAKEDEV snd1
³oÓ°ÝÃD¦b FreeBSD 4.x ¤W¨Ã¤£·|µo¥Í¡A¦]¬°«Ü¦h¤H§ë¤U¤F³\¦h¤ß
¤OÅý¥¦§óPnP ¾É¦V ¡A¦Ó¥B
pcm0 ³oÓ device ¤]¤£¦A¬O¥u«O¯dµ¹ ISA
ªºµ®Ä¥d¤F¡C
¬°¤°»ò¦b§ó·s¨ì FreeBSD 4.X «á·|§ì¤£¨ì§Úªº PnP ¥d
¡]©ÎªÌ¬O§ì¦¨ unknown ¡^¡H
FreeBSD 4.X ²{¦b¤w¸g§ó PnP ¾É¦V ¤F¡A
¦ÓÃä»Ú®ÄÀ³´N¬O·|µo¥Í¦³¨Ç¦b FreeBSD 3.X ¥i¥H¥Îªº PnP ¸Ë¸m
¡]¦pµ®Ä¥d©Î¬O¤º´¡¦¡¼Æ¾Ú¾÷¡^Åܦ¨µLªk¨Ï¥Î¡C
³oÓì¦]¥i¥H¥Î¤@«Ê¥Ñ Peter Wemm µo¨ì freebsd-questions
³oÓ mailing list ¤Wªº«H¨Ó¸ÑÄÀ¡A¥¦ì¥»¬O¸ÑÄÀ¬°¤°»ò¦³¤@Ó¤º
´¡¦¡¼Æ¾Ú¾÷¡A¦b¨t²Î¤É¯Å¨ì FreeBSD 4.x «á¡A´N¨Sªk³Q§ì¨ì¤F
¡]¦b [] ùتº¬O¥t¥~¥[ªºµù¸Ñ¡AÅý¤º®e§ó©öÀ´¡^¡C
The PNP bios preconfigured it [the modem] and left it
laying around in port space¡Aso [in 3.x] the old-style ISA
probes found
it there.
Under 4.0¡Athe ISA code is much more PnP-centric. It was
possible [in 3.x] for an ISA probe to find a
stray
device and then for the PNP device id to
match and then fail due to resource conflicts. So¡Ait
disables the programmable cards first so this double probing
cannot happen. It also means that it needs to know the PnP
id's for supported PnP hardware. Making this more user
tweakable is on the TODO list.
¦pªGnÅý¸Ë¸m¯à¦A«×¹B§@¡A§ÚÌ»Ýn§ä¥X¥¦ªº PnP id¡AµM«á¦A±N¥¦
¥[¤J¤@¥÷¦b°»´ú ISA ¸Ë¸m®É·|¨Ï¥Îªºªí¤¤¡C¥i¥H°õ¦æ &man.pnpinfo.8;
¨Ó°»´ú³oӸ˸m¡AÁ|¨Ò¨Ó»¡¡A¤U±¬O &man.pnpinfo.8; §ì¨ìªº¤@Ó¤º´¡
¦¡¼Æ¾Ú¾÷ªº¸ê®Æ¡G
&prompt.root; pnpinfo
Checking for Plug-n-Play devices...
Card assigned CSN #1
Vendor ID PMC2430 (0x3024a341)¡ASerial Number 0xffffffff
PnP Version 1.0¡AVendor Version 0
Device Description: Pace 56 Voice Internal Plug & Play Modem
Logical Device ID: PMC2430 0x3024a341 #0
Device supports I/O Range Check
TAG Start DF
I/O Range 0x3f8 .. 0x3f8¡Aalignment 0x8¡Alen 0x8
[16-bit addr]
IRQ: 4 - only one type (true/edge)
[more TAG lines elided]
TAG End DF
End Tag
Successfully got 31 resources¡A1 logical fdevs
-- card select # 0x0001
CSN PMC2430 (0x3024a341)¡ASerial Number 0xffffffff
Logical device #0
IO: 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8
IRQ 5 0
DMA 4 0
IO range check 0x00 activate 0x01
±z©Ò»Ýnªº¸ê°T¬O¤@¶}©l¬Ý¨ìªº Vendor ID
³o¤@¦æ¡C¬A¸¹¤¤ªº¤Q¤»¦ì¤¸½X¡]³oÓ¨Ò¤l¤¤¬O 0x3024a341¡^´N¬O
PnP id¡A¦Ó¦b³o¤§«eªº¦r¦ê¡]PMC2430¡^«h¬O¤@Ó¿W¤@µL¤Gªº ASCII id¡C
¦Ó³o¨Ç¸ê®Æ»Ýn³Q¥[¨ì /usr/src/sys/isa/sio.c
³oÓÀÉ®×ùØ¡C
¬°¤F¨¾¤î¥ô¦óªF¦è¥X¿ù¡A±zÀ³¸Ón¥ý³Æ¥÷¥Ø«eªº
sio.c ¡C¦Ó¥B±zn submit PR ®É¤]»Ýn³oÓ
ì©lÀɮרӰµ¥X patch¡]±zÀ³¸Ó·|±N¥¦ submit PR §a..¡G¡^..¡^¡C
±µµÛ´N½s¿è sio.c §ä´M¤U±³o¦æ
static struct isa_pnp_id sio_ids[] = {
±µµÛ©¹¤U±²°Ê¡A§äÓ¥¿½Tªº¦ì¸m¨Ó´¡¤J±zªº¸Ë¸m¸ê°T¡C±z¬Ý¨ìªº´N
¤U±³oӼˤl¡A¥¦Ì¬O·Ó¥kÃäµù¸Ñ¸Ì±ªº ASCII ³oÓ Vender ID °µ±Æ
§Çªº¡A©Î¬O &man.pnpinfo.8; ©Ò§ä¨ìªº¤@³¡¤À
¸Ë¸m´yz ¡G
{0x0f804f3f¡ANULL}¡A /* OZO800f - Zoom 2812 (56k Modem) */
{0x39804f3f¡ANULL}¡A /* OZO8039 - Zoom 56k flex */
{0x3024a341¡ANULL}¡A /* PMC2430 - Pace 56 Voice Internal Modem */
{0x1000eb49¡ANULL}¡A /* ROK0010 - Rockwell ? */
{0x5002734a¡ANULL}¡A /* RSS0250 - 5614Jx3(G) Internal Modem */
§â±z³oӸ˸mªº¤Q¤»¶i¦ìªº Vender ID ¥[¨ì¥¿½Tªº¦a¤è¡A¦sÀÉ¡A
µM«á«·s½s¤@Ó kernel¡A¦A«¶}¾÷¡C¤§«á³oӸ˸mÀ³¸Ó´N·|¹³¦b
FreeBSD 3.X ¤U¡A³Q°»´ú¬° sio ¸Ë¸m¤F¡C
¬°¤°»ò§Ú±`±`¦b¶]¤@¨Çµ{¦¡¡]¨Ò¦p top ©Î
systat ¡^ªº®ÉÔ¥X²{
nlist failed ³oÓ¿ù»~°T®§¡H
³oÓ°ÝÃD¬O¦]¬°±z¶]ªºµ{¦¡»Ýn¤@Ó¯S§Oªº kernel symbol¡A¥i¬O
¤£ª¾¹D¤°»òì¦]¦Ó§ä¤£¨ì¡Q¦Ó·|µo¥Í³oÓ°ÝÃD¥i¯à¬O¦]¬°¤U±¨âÓì¦]¡G
±zªº kernel ©M userland ªºÀɮת©¥»¨Ã¤£¤@P¡]¨Ò¦p»¡¡A±z
½s¤F¤@Ó·sªº kernel¡A¦ý¬O¨Ã¨S¦³°õ¦æ¹ïÀ³ªº
installworld ¡A©Î¬O¨ä¥LÃþ¦ü±¡§Î¡^¡A
¦]¦¹ symbol table ªº¤º®e´N©MÀ³¥Îµ{¦¡½sĶ®Éªº¤£¤Ó¤@¼Ë¤F¡C¦p
ªG¬O³oºØ±¡§Î¡A½Ð°õ¦æ§¹¾ãªº¤É¯Å¨BÆJ¡]½Ð°Ñ¾\
/usr/src/UPDATING ¥H±oª¾¥¿½Tªº¬y
µ{¡^¡C
±z¨S¦³¥Î /boot/loader ¨Ó¸ü¤J±zªº
kernel¡A¦Ó¬Oª½±µ¥Ñ boot2 ¶}¾÷¡]½Ð°Ñ¾\ &man.boot.8;¡^¡C
ÁöµM»¡¸õ¹L /boot/loader ¨Ã¨S¦³¤°»ò¿ù¡A
¦ý¬O¥¦¦b kernel symbols ¸òÀ³¥Îµ{¦¡ªº·¾³q¤è±¦û¤F«Ü«ªº¥÷¶q¡C
¬°¤°»ò§Ú¥Î ssh ©Î telnet
³s¨ì§Úªº¹q¸£®É¡A·|µ¥«Ý«Üªøªº¤@¬q®É¶¡¤~¯à³s¤W¡H
¯gª¬¡GTCP ³s½u«Ø¥ß¤§«á©M¸ß°Ý±K½X¤§«e¡]¦pªG¬O¦b»¡ &man.telnet.1;
ªº¸Ü¡A«h¬O login ´£¥Ü²Å¸¹¸õ¥X¨Ó¤§«e¡^¡Anµ¥«Ý«Üªøªº¤@¬q®É
¶¡¡C
°ÝÃD©Ò¦b¡G³oºØ©µ¿ð±¡§Î±`±`¬O¦]¬°¦øªA³nÅé¡]server software¡^
¹Á¸Õn±N«È¤áºÝ¡]client¡^ªº IP ¦ì§}Âà´«¦¨¥D¾÷¦WºÙ¡C¦]¬°«Ü¦h¦øªA
³nÅé¡A¥]¬A FreeBSD ¤º«Øªº Telnet ©M SSH¡A¬°¤F±N¥D¾÷¦WºÙ¼g¤J¬ö
¿ýÀɤ¤¥H¨ÑºÞ²zªÌ§@°Ñ¦Ò¡A¦Ó·|°µ³o¶µ°Ê§@¡C
¸Ñ¨M¤èªk¡G¦pªG³oÓ°ÝÃD¦b±z³s±µ¤£¦Pªº¦øªA¾¹®É³£·|µo¥Í¡A¨º»ò
°ÝÃD¬O¦b±z«È¤áºÝ³o¤@¤è¡Q¦P¼Ëªº¡A¦pªG§O¤H¥u¦³¦b³s¨ì±zªº¦øªA¾¹¤W
¤~·|µo¥Í³oÓ±¡§Î¡A¨º»ò°ÝÃD´N¬O¦b¦øªA¾¹³oÃä¤F¡C
¦pªG¬O«È¤áºÝ³o¤è¦³°ÝÃD¡A°ß¤@ªº¤èªk´N¬O±N DNS ¦øªA¾¹×¦n¡A
³o¼Ë¹ï¤è¦øªA¾¹¤~¯à¥¿½TªºÂà´«¦WºÙ¡C¦pªG°ÝÃD¬O¦b¤º³¡°Ï°ìºô¸ôµo
¥Íªº¡A³oÀ³¸Ó¬O¦øªA¾¹¦³°ÝÃD¡A½Ð¸Ô²ÓÀˬd¤@¤U¡Q¬Û¤Ïªº¡A¦pªG¬O±z
¦b¤W Internet ®Éµo¥Íªº¡A¨º»ò±z»Ýn¸ò±zªº ISP Ápµ¸¡A½Ð¥L̸ѨM
³oÓ°ÝÃD¡C
¦pªG¬O¦øªA¾¹³oÃ䪺°ÝÃD¡A¦Ó¥B¬Oµo¥Í¦b¤º³¡°Ï°ìºô¸ô¡A¨º»ò±z»Ý
n³]©w³oÓ¦øªA¾¹¡A¨Ï¥¦¯à¥¿½T±N¤º³¡ºô¸ôªº IP ¦ì§}Âà´«¬°¥D¾÷¦WºÙ¡C
½Ð°Ñ¾\ &man.hosts.5; ©M &man.named.8; ªº»¡©ú¥HÀò±o§ó¦h¸ê°T¡C¦p
ªG¬O¦b Internet ¤Wªº¦øªA¾¹µo¥Í³oÓ°ÝÃD¡A¨º»ò¦³¥i¯à¬O±z¦øªA¾¹ªº
Âà´«¥\¯à¥X°ÝÃD¡C±z¥i¥H¸Õ¸Õ¬d¸ß¥t¤@Ó¥D¾÷¦WºÙ¡A¤ñ¦p¡G
www.yahoo.com ¡C¦pªG¬d¤£¨ì¡A¨º»ò¥i¥H½T©w¬O±z³o
Ãä¥X°ÝÃD¤F¡C
stray IRQ ³oÓ¿ù»~°T®§¬O¤°»ò·N«ä¡H
Stray IRQs ¬OµwÅé IRQ ¦³ÂI¤p°ÝÃDªº²{¶H¡A¤j¦h¬O¦]¬°µwÅ饻¨
¦bµo¥X¤¤Â_»Ý¨D«á¡A¤S¨ú®ø¤F¥¦¦Û¤vªº¤¤Â_n¨D¡C
¦³¤TÓ¤èªk¥i¥HÀ³¥I³oÓ°ÝÃD¡G
¤£²z·|³oÓĵ§i¡C¤Ï¥¿¤@Ó irq ¥X²{¤¦¸Äµ§i«á¨t²Î´N¤£·|
¦AÅã¥Ü¤F¡C
§â isa_strayintr() ùتºÈ¡A¥Ñ 5
§ï¦¨ 0¡A³o¼Ë©Ò¦³ªºÄµ§i°T®§³£¤£·|¥X²{¡C
¦w¸Ë¨Ï¥Î irq 7 ªº¥¦æ°ðµwÅé³]³Æ¡A¥H¤Î¥¦ªº PPP ÅX°Êµ{¦¡
¡]³oÓ¤j³¡¤À¨t²Î³£¦³°µ¡^¡A±µµÛ¦w¸Ë ide µwºÐ©Î¬O¨ä¥L·|¨Ï¥Î
irq 15 ªºµwÅé³]³Æ¥H¤Î¥¦ªºÅX°Êµ{¦¡¡C
¬°¤°»ò file: table is full ³oÓ°T®§
¤@ª½¦b dmesg ùØ«½Æ¥X²{¡H
³oÓ¿ù»~°T®§¥Nªí¤F±z¨t²Îªº file descriptors ¤w¸g¨Ï¥Î¥ú¤F¡C
½Ð°Ñ¾\¤â¥U¤º
Tuning Kernel Limits ¸Ì±ªº
kern.maxfiles ³oÓ³¹¸`¡A¸Ì±¦³¤@¨Ç°Q½×¤Î¸Ñ¨M¤èªk¡C
¬°¤°»ò§Úµ§°O«¬¹q¸£¤Wªº®ÉÄÁ¤@ª½Åã¥Ü¿ù»~ªº®É¶¡¡H
±zªºµ§°O«¬¹q¸£¸Ì¦³¨âÓ¥H¤Wªº®ÉÄÁ¡A¦Ó FreeBSD ¿ï¨ì¤F¿ùªº
¨ºÓ¡C
°õ¦æ &man.dmesg.8;¡AÀˬd¤@¤U¦³ Timecounter
¦r¦êªº¨º´X¦æ¡C³Ì«á¤@¦æ¬O FreeBSD ¿ï¥Îªº¡A³q±`¬O
TSC ¡C
&prompt.root; dmesg | grep Timecounter
Timecounter "i8254" frequency 1193182 Hz
Timecounter "TSC" frequency 595573479 Hz
±z¥i¥H°õ¦æ &man.sysctl.3; ¬Ý¤@¤U
kern.timecounter.hardware ³oÓÈ°µ½T»{¡C
&prompt.root; sysctl kern.timecounter.hardware
kern.timecounter.hardware: TSC
BIOS ¥i¯à¦b¤@¨Ç±¡§Î¤U·|§ó§ï TSC ªº®É¯ß—¦³®ÉÔ¬O¦]¬°
¦b¨Ï¥Î¹q¦À¤u§@®É·|§ó§ï³B²z¾¹ªº³t«×¡A¥t¥~¤]¦³¥i¯à¬O¶i¤J¤F¬Ù¹q¼Ò
¦¡¡A¥i¬O FreeBSD ¨Ã¤£·|¹îı¨ì³o¨Ç½Õ¾ã¡A¦Ó·|µo¥Í®É¶¡¼W¥[©Î¬O´î
¤Öªº±¡§Î¡C
¦b¤W±ªº¨Ò¤l·í¤¤¡A§Ú̬ݨìÁÙ¦³ i8254
³oÓ®ÉÄÁ¥i¥H¿ï¾Ü¡A°õ¦æ &man.sysctl.3; ¥Î¤â°Êªº¤è¦¡±N³oÓȼg¤J
kern.timecounter.hardware ¤¤¡C
&prompt.root; sysctl -w kern.timecounter.hardware=i8254
kern.timecounter.hardware: TSC -> i8254
³o¼Ë±zªºµ§°O«¬¹q¸£À³¸Ó´N¥i¥H«O«ù¥¿½Tªº®É¶¡¤F¡C
¦pªGnÅý³oÓ§ó§ïªº°Ê§@¦A¨C¦¸¶}¾÷®É¦Û°Ê°õ¦æ¡A¦b
/etc/sysctl.conf ùØ¥[¤J¤U±³o¦æ¡C
kern.timecounter.hardware=i8254
¬°¤°»ò§Úªºµ§°O«¬¹q¸£µLªk¥¿½Tªº°»´ú¨ì PC card ¡H
³oÓ°ÝÃD±`±`µo¥Í¦bÄé¤F¦hÓ§@·~¨t²Îªºµ§°O«¬¹q¸£¤W¡C¦³¨Ç«D
BSD ªº§@·~¨t²Î·|Åý PC card ªºµwÅé¸Ë¸m³B¦b¤@Ó¤£¤@Pªºª¬ºA¤U
¡]inconsistent state¡^¡C¨Ï±o pccardd ¦b°»
´ú³o¤ù¥d®É¡AµLªk§ì¨ì¥¿½Tªº«¬¸¹¡A¦Ó¬O
"(null)""(null)" ¡C
±z»Ýn²¾°£ PC card ´¡¼Ñªº¹q·½¥H«¸m³oÓµwÅé¸Ë¸m¡C¤@Ó¤èªk¬O
±N±zªºµ§°O«¬¹q¸£Ãö¾÷¡]¤£¬O¥ð¯v¼Ò¦¡¡A¤]¤£¬O«Ý©R¼Ò¦¡¡Qn§¹¥þªºÃö
¾÷¡^¡Cµ¥Ó´X¬íÄÁ¦A«¶}¾÷¡C³o¼Ë±zªº PC card À³¸Ó´N¥¿±`¤F¡C
¦³®É¦³¨Çµ§°O«¬¹q¸£ÁöµM¬Ý°_¨Ó¤w¸gÃö¾÷¤F¡A¦ý¹ê»Ú¤W¨Ã¨S¦³¡C
¦pªG±zµo²{¤W±¨ºÓ¤èªk¨S¦³¥Î¡A½ÐÃö¾÷¡A²¾°£¹q¦À¡Aµ¥Ó´X¬íÄÁ¡A
§â¹q¦À¸Ë¤W¥hµM«á«¶}¾÷¡C
¬°¤°»ò¦b BIOS µe±¤§«á¡AFreeBSD ªº boot loader Åã¥Ü
Read error µM«á´N°±¤î¤£°Ê¤F¡H
³o¬O¦]¬°FreeBSD ªº boot loader µLªk¥¿½Tªº§ä¥XµwºÐªº
geometry¡C³o¼Ëªº¸Ü¡A´N»Ýn¦b¥Î fdisk ¤À³Î©Î¬Oקï FreeBSD
ªº slice ®É¡A¤â°Ê±N¥¿½TªºÈ¿é¤J¶i¥h¤F¡C
¥¿½TªºµwºÐ geometry Ȧb BIOS ¸Ì±¥i¥H¬dªº¨ì¡Cª`·N¸ÓµwºÐªº
cylinders¡Aheads ¥H¤Î sectors ³o¨Ç¼ÆÈ¡C
¦b°õ¦æ &man.sysinstall.8;ªº fdisk ®É¡A«ö¤U G
¥H«K¤â°Ê³]©wµwºÐªº geometry¡C
³o®É·|¦³¤@Ó¹ï¸Ü®Ø¸õ¥X¨Ó¡A¸ß°Ý±z¦³Ãö cylinders¡Aheads ¥H¤Î
sectors ³o¨ÇªF¦èªºÈ¡C½Ð±Nèè¦b BIOS ¬d¨ìªº¼Æ¦r¡A¥H / §@¤À¹j¿é
¤J¶i¥h¡C
Á|¨Ò¨Ó»¡¡A¦pªG¬O 5000 cylinders¡A250 sectors ©M 60 sectors
´N¿é¤J 5000/250/60
¿é¤J§¹«á½Ð«ö enter Áä½T»{¡A³Ì«á«ö¤U W Áä§â
·sªº¤À³Î°Ïªí¼g¤JµwºÐ·í¤¤¡C
¥t¤@Ó§@·~¨t²ÎºR·´¤F§Úªº Boot Manager¡C§Ún«ç»ò¼Ë¤~¯à§â¥¦ÁÙ
ì¦^¨Ó¡H
°õ¦æ &man.sysinstall.8; ±µµÛ¿ï Configure¡AµM«á¿ï Fdisk¡C
¦A¨Ó¥ÎªÅ¥Õ Áä¿ï¾Üì¥ý Boot Manager ©Ò¦bªºµwºÐ¡C
«ö¤U W Áä¨Ó§@¼g¤Jªº°Ê§@¡C³o®É·|¸õ¥X¤@Ó´£¥Ü
°T®§¡A¸ß°Ý±zn¦w¸Ëþ¤@Ó boot loader¡C½Ð¿ï¾Ü Boot Manager¡A
³o¼Ë´N¥i¥H±N¥¦ÁÙì¤F¡C
³oÓ¿ù»~°T®§¡Gswap_pager: indefinite
wait buffer: ¬O¤°»ò·N«ä©O¡H
³oÓ°T®§¬O»¡¦³¤@Ó°õ¦æµ{§Ç¥¿¦b¹Á¸Õ±N¤À¶°O¾ÐÅé¡]page memory¡^
¼g¤JµwºÐ¤¤¡A¦Ó³oӰʧ@¹Á¸Õ¤F 20 ¬íÄÁ¤´µMµLªk¦¨¥\¡C³oÓ¦³¥i¯à¬O¦]¬°
µwºÐ¦³Ãay¡B¹q¸ô©Î±Æ½u¦³°ÝÃD¡B¥H¤Î¨ä¥L¸òµwºÐŪ¥X¼g¤J¦³ÃöªºµwÅé³]³Æ¡C
¦pªG¯uªº¬OµwºÐÃayªº°ÝÃD¡A±zÀ³¸Ó·|¦b
/var/log/messages ³oÓÀɮפ¤¡A©Î¬O¦b°õ¦æ
dmesg ³oÓ«ü¥O«á¡A¬Ý¨ì¦³ÃöºÏºÐ¿ù»~ªº°T®§¡C
¦pªG¨S¦³¡A¨º»ò½ÐÀˬd±zªº±Æ½uÁÙ¦³±µÀY³s±µ¬O§_¨}¦n¡C
Vanilla
Shu
vanilla@FreeBSD.org
°Ó·~³nÅé
³o¤@¸`ªº¤º®eÁÙ¬O¬Û·í¤Ö¡A¤£¹L§ÚÌ·íµM§Æ±æ¦UÓ¤½¥q¯à¬°¥¦¥[
ÂI¤º®e :) FreeBSD ²Õ´©M¦C¦b³o¸Ìªº¥ô¦ó¤@®a¤½¥q³£¨S¦³ª÷¿ú¤Wªº§Q®`
Ãö«Y¡A¦C¥X¨Ó¥u¬O¹ï¤j²³ªº¤½¶}ªA°È¡]¦P®É¤]»{¬°¦b FreeBSD ¤Wªº°Ó·~¿³
½ì¡A·|¹ï FreeBSD ªø¤[¥Í¾÷¦³·¥¥¿±ªº®Ä¯q¡^¡C§Ú̹ªÀy°Ó·~³nÅ骺¼t°Ó
§â¥L̪º²£«~¥]¬A¦b¤U±ªº¦W³æ¤¤¡A¦b
Vendors page
¥i¥H¬Ý¨ì¸ûªø¦Cªí¡C
¦bþÃä§ä¨ìµ¹ FreeBSD ¥Îªº Office ®M¥ó©O¡H
FreeBSD Mall
´£¨Ñ¤F VistaSource
ªº ApplixWare 5 ªº FreeBSD ª©¥»¡C
ApplixWare ¬O¤@®M°Ó·~ª©¥»ªº Office ®M¥ó¡A¥L´£¨Ñ¤F
¤å¥ó³B²z¡B¸Õºâªí¡B¦V¶qø¹Ïµ¥¬ÛÃöµ{¦¡¡C
ApplixWare ¦P®É¤]¬O FreeBSD Mall's BSD Desktop Edition
ªº¤@³¡¥÷¡C
Linux ª©¥»ªº StarOffice
¥i¥H«Ü¥¿±`ªº¦b FreeBSD ¤U°õ¦æ¡A¥i¥H³z¹L FreeBSD Ports collection
¨Ó¦w¸Ë Linux ª©¥»ªº StarOffice¡C¦Ó open-source OpenOffice «Ü§Ö±o
¤]¥i¥H¦b FreeBSD ¤W¥¿±`ªº°õ¦æ¡C
¦bþÃä§ä¨ìµ¹ FreeBSD ¥Îªº Motif¡H
Open Group ÄÀ¥X¤F Motif 2.1.30 ªºì©l½X¡A¥i¥H³z¹L
open-motif package ¦w¸Ë¡A©Î¬O¥Ñ ports ¦Û¦æ
½sĶ¡C¬ÛÃöªº¸ê°T¡A½Ð°Ñ¦Ò handbook ¤¤ªº ports ³¹¸`¡C
Open Motif ¥u¯à¦b¦P¼Ë¤]¬O open source
ªº§@·~¨t²Î©Îp¹º¤¤¨Ï¥Î¡C
¥t¥~¡A¤]¬O¦³°Ó·~ª©¥»ªº Motif ¦s¦b¡C¤]³\³oºØª©¥»ªº Motif
¤£¬O§K¶Oªº¡A¦ý¬Oµ´¹ï¤¹³\¥Î¦b closed-source ªºÀô¹Ò¤U¡C
Apps2go ´£¨Ñ¤F³Ì«K©yªº FreeBSD
(¥]¬A i386 ¸ò alpha)ª©¥»ªº ELF Motif 2.1.20 ®M¥ó¡C
¥Ø«e´£¨Ñ¨âºØ¤£¦PÀô¹Òªºª©¥»¡A µo®i¥Îª©¥»
¤Î
runtime ª©¥»
¡C³o¨âºØ®M¥ó³£¥]¬A¡G
OSF/Motif manager, xmbind, panner, wsm.
Development kit with uil, mrm, xm, xmcxx, include
and Imake files.
Static and dynamic ELF libraries (for use with
FreeBSD 3.0 and above).
Demonstration applets.
¦]¬° Apps2go ¤]¦³´£¨Ñ NetBSD ©M OpenBSD
ªºª©¥»¡A©Ò¥H¦bqÁʮɽЯS§O«ü©w¬On FreeBSD ª©¥»ªº Motif¡I
¥L̥ثe¥u´£¨Ñ¥H FTP ªº¤è¦¡¨ú±o³o¥÷®M¥ó¡C
§ó¦h¸ê°T
Apps2go WWW page
©Î
sales@apps2go.com ©Î
support@apps2go.com
©Î
phone (817) 431 8775 or +1 817 431-8775
¤]¥i¥HÁpµ¸ Metro Link
¨ú±oµ¹ FreeBSD ELF©Î a.out ª©¥»ªº Motif 2.1 ®M¥ó¡C
³o¥÷®M¥ó¥]¬A¡G
OSF/Motif manager, xmbind, panner, wsm.
Development kit with uil, mrm, xm, xmcxx, include
and Imake files.
Static and dynamic libraries (specify ELF for use
with FreeBSD 3.0 and later; or a.out for use with FreeBSD
2.2.8 and earlier).
Demonstration applets.
Preformatted man pages.
¥Ñ©ó Metro Link ¤]¦³´£¨Ñ Linux ªºª©¥»¡A
©Ò¥HqÁÊ®Én¯S§O«ü©ú¬O FreeBSD ª©¥»ªº Motif¡I ¥i¥H¥Ñ¥úºÐ©Î±q FTP
¨Ó¨ú±o³oÓ®M¥ó¡C
Ápµ¸ Xi Graphics ¡A¥LÌ´£¨Ñ¤F¤@Ó
FreeBSD a.out ®æ¦¡ªº Motif 2.0 ®M¥ó¡C
¦b³o®M¥ó¤¤¥]¬A¤F¡G
OSF/Motif manager, xmbind, panner, wsm.
Development kit with uil, mrm, xm, xmcxx, include
and Imake files.
Static and dynamic libraries (for use with FreeBSD
2.2.8 and earlier).
Demonstration applets.
Preformatted man pages.
¦b§A¸ò¥LÌqÁÊ Motif ®É¡A½Ð¤@©wµù©ú§Anªº¬O FreeBSD ªºª©¥»¡I
¦]¬° Xi Graphics ¤]¦P®É´£¨Ñ¤F BSDI ¸ò Linux
ª©¥»ªº Motif¡C¥Ø«eµo¦æªºª©¥»¬O©ñ¦b¥|¶ôºÏ¤ù¤¤¡A±N¨Ó¥LÌ·|±N©Ò¦³ªº
ªF¦è³£©ñ¨ì¥úºÐ¸Ì¡A´N¹³¥LÌ©Òµo¦æªº CDE ¤@¼Ë¡C
¦bþÃä§ä¨ìµ¹ FreeBSD ¥Îªº CDE¡H
Xi Graphics ¥H«e¦³½æ FreeBSD ¥Îªº
CDE¡A¤£¹L²{¦b¤w¸g°±¤îµo°â¤F¡C
KDE is an open
source X11 desktop which is similar to CDE in many respects.
You might also like the look and feel of xfce . KDE and xfce are both
in the ports
system .
¦³¨S¦³n¿ú¡A¦ý¬O°ª®Ä²vªº X servers¡H
¦³¡A Xi Graphics
©M Metro Link
³£¦³´£¨Ñµ¹ FreeBSD¡]©Î¨ä¥L Intel ¥¥x¤W¡^¥Îªº X µøµ¡¥[³t²£«~¡C
Metro Link °ª®Ä¯à X Server ¨Ï¥Î¤F FreeBSD ¤º«Øªº package
¥]¸Ë¤è¦¡, ¦]¦¹³]©w¤Q¤À®e©ö¡A¤ä´©¥Ø«e¥«±¤W¦U¤j¼tµPªºÅã¥Ü¥d¡C
¥Ø«e¥u´£¨Ñ binary ®æ¦¡ÀɮסA¥i¥H±q FTP ¯¸¬Û·í¤è«K¦aª½±µ¤U¸ü¡A
¨Ã¥B Metro Link ³o®M²£«~ªº»ù®æ¬O«D±`¦X²zªº $39¡C
Metro Link ¦P®É´£¨Ñ FreeBSD ¤Wªº ELF ©M a.out ®æ¦¡ªº Motif
¡]©¹¤W±¬Ý¬Ý¡^¡C
§ó¦hªº¸ê°T
Metro Link WWW page
©Î
sales@metrolink.com
©Î tech@metrolink.com
©Î
phone (954) 938-0283 or +1 954 938-0283
Xi Graphics ©Ò´£¨Ñªº°ª®Ä¯à X Server ¦³«D±`²³æªº³]©w¤è¦¡¡A
¨Ã¥B¤ä´©¤F¥Ø«e¥«±¤W·í¬õªº¦U¤j¼tµPªºÅã¥Ü¥d¡C¥¦¥uµ¹§A Binary ÀɮסA
¬O¥ÎºÏ¤ùªº¤è¦¡µo¦æ¡AFreeBSD ¸ò Linux ª©¥»³£¬Û¦P¡CXi Graphics ¦P®É
¤]´£¨Ñ¤F±Mªùµ¹ laptop ¥Îªº°ª®Ä¯à X Server¡C
5.0 ª©¦³´£¨Ñ§K¶Oªº compatibility demo
ª©¥»
Xi Graphics ¤]¦³¦b½æ FreeBSD ¥Îªº Motif ¸ò CDE¡]©¹¤W±¬Ý¬Ý¡^¡C
§ó¦hªº¸ê°T
Xi Graphics WWW page
©Î
sales@xig.com
©Î support@xig.com
©Î
phone (800) 946 7433 or +1 303 298-7478.
¦b FreeBSD ¤W¦³¥ô¦óªº¸ê®Æ®w¶Ü¡H
¦³! ½Ð¬Ý FreeBSD ºô¯¸¤W
°Ó·~³nÅ餽¥q ³o¤@³¡¥÷¡C
ÁÙ¦³½Ð°Ñ¦Ò ports ¤¤
Databases ¬ÛÃöªº¦¬¶°¡C
¥i¥H¦b FreeBSD ¤W°õ¦æ Oracle ¶Ü¡H
¥i¥H¡A¤U±³oÓºô¶·|»¡©ú¦p¦ó¦b FreeBSD ¤W°õ¦æ Linux
ª©ªº Oracle¡G
http://www.scc.nl/~marcel/howto-oracle.html
http://www.lf.net/lf/pi/oracle/install-linux-oracle-on-freebsd
Kang-min
Liu
gugod@gugod.org
¤@¯ëÀ³¥Îµ{¦¡
¶â..§Ún¦bþ§ä¨ì§Únªºµ{¦¡©O?
½Ð¬Ý¬Ý ports
¥Ø¿ý §a¡C³oÃ䦳¥÷¤w¸g port ¨ì FreeBSD ªº³nÅé¦Cªí¡C
¥Ø«e¦³¶W¹L &os.numports; Ó³nÅé¤w¸g³Qport ¨ì FreeBSD ¤W¡A¨Ã¥B¨C¤Ñ
³£¦b¼W¥[¤¤¡C©Ò¥H¦³ªÅ´N¦h¬Ý¬Ý³o¥÷¦Cªí¡A¤£µM§A¤]¥i¥Hq¾\
freebsd-announce
³o¥÷ mailing list¡A·|¦³¤H±N¨CÓ¬P´Á³Ì·sªº³nÅé¦Cªí¶K¦b
¤W±¡C
¤j³¡¥÷ªº ports À³¸Ó³£¥i¥H¦b 2.2¡A3.0 ¸ò 4.0 ªº¨t²Î¤W¨Ï
¥Î¡A¨Ã¥BÁÙ¦³³¡¥÷ªº ports ¥i¥H¦b 2.1.x ªº¨t²Î¤W¹B§@¡C¨C¦¸
·í FreeBSD release ®É¡A³£·|¦³¤@¥÷ ports tree ³Q©ñ¦b³o¤@Ó
release cd ¸Ì±ªº ports/ ¥Ø¿ý¸Ì¡C
§Ṳ́]¤ä´©¤@ºØ¥s package
ªº·§©À¡A°ò¥»¤W
´N¬O gzip À£ÁY¡B¥i¥Î¨Óµo¦æªº binary ÀɮסA¦ý¬O¸Ì±ÂäF¤@
¨Ç¬Û·í¦³¥Îªº¸ê°T¡A¥i¥Hµ¹¦UºØ¦Ûq¦w¸Ë¨Ó¨Ï¥Î¡C¨Ï¥ÎªÌ¤£¥²ª¾
¹D¬YÓ package ¸Ì¨s³º¦³¥]¬Aþ¨ÇÀɮסA´N¥i`¥H«Ü¤è«K¦a«½Æ±N
¥¦¦w¸Ë/¤Ï¦w¸Ë¡C
§A¥i¥H°õ¦æ /stand/sysinstall «á¡A
¦b post-configuration ¿ï³æ¤U¿ï¾Ü package ³oÓ¦w¸Ë¿ï¶µ¡F©Î
¬O¹ï¬YÓ¦³¿³½ìªº package ÀÉ®×°õ¦æ &man.pkg.add.1;
§â¥¦¸Ë°_¨Ó¡CPackage Àɮ׳q±`¥H .tgz
§@¬°©µ¦ùÀɦW¡A¤â¤W¦³ FreeBSD CDROM ªº¤H¥i¥H¦b
packages/All ³oӥؿý¤U§ä¨ì³oÃþÀɮסC
¹ï¤£¦Pªº FreeBSD ª©¥»¡A¤]¥i¥H±q¤U¦C¦ì§}¥Ñºô¸ô¤W¨ú±o¡G
µ¹ 2.2.8-release/2.2.8-stable ¥Îªº
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-2.2.8/
µ¹ 3.2-release/3.2-stable ¥Îªº
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-3-stable/
µ¹ 4.X-RELEASE/4-STABLE ¥Îªº
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-current/
µ¹ 5.X-CURRENT ¥Îªº
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-5-current
©Î¬OÂ÷§A³Ìªñªº mirror ¯¸¡C
nª`·Nªº¬O¡A¦]¬°·sªº port ¤@ª½¦b¼W¥[¤¤¡A©Ò¥H¨Ã¤£¬O©Ò¦³ port
³£¦³¬Û¹ïÀ³ªº package¡C³Ì¦n©w®ÉÀˬdftp.FreeBSD.org
¡A¬Ý¬Ý¦³þ¨Ç package ¥i¥H¥Î¡C
§Ú¥i¥H¦bþÃä§ä¨ì libc.so.3.0?
§A¥i¯à¦b¤@¥x 2.1.x ªº¾÷¾¹¤W¡A¶]µÛµ¹ 2.2/3.x/4.0 ªº³nÅé¡C
½Ð¦A©¹¤W±¤@Ó³¹¸`¬Ý¡A¥¿½Tªº¨ú±oµ¹§A¾÷¾¹¥Îªº port/package¡C
¬°¦ó§Ú±o¨ì¤F³oÓ°T®§ ?Error: can't find
libc.so.4.0 ?
§A¤£¤p¤ß§ì¤Fµ¹ 4.X ¤Î 5.X ¨t²Î¥Îªº package¡A¨Ã¥B¹Á¸ÕµÛ
¥h¸Ë¦b§Aªº 2.X ©Î 3.X ªº¨t²Î¤W±¡C½Ð¤U¸ü¥¿½Tª©¥»ªº package¡C
ghostscript ¦b§Úªº 386/486SX ¤W¦³ÂI°ÝÃD©O¡I
§A¨S¦³¯BÂI¹Bºâ¾¹¡A¹ï§a¡H§A¥²¶·¦b§Aªº kernel ¤¤¥[¤J¼Æ¾Ç
¹Bºâ¼ÒÀÀ¾¹¡A§A¥i¥H¸òµÛ¤U±ªº¨BÆJ°µ¡A¨Ã¦b§ó§ï¹L§Aªº kernel ³]©w
ÀÉ«á¡A«·s½sĶ¹L¤@¦¸¡C
options GPL_MATH_EMULATE
·í§A¥[¤J¤W¤@¦æªº¦P®É¡A§A¥²¶·±N
MATH_EMULATE ²¾°£±¼¡C
¬°¤°»ò·í§Ú°õ¦æ SCO/iBCS2 ªºµ{¦¡®É¡A¥¦¦b
socksys ³oÓ¦a¤è¥X¤F°ÝÃD¡H
(FreeBSD 3.0 ¥H¤Î§ó¦ªºª©¥»¤~¦³¦¹°ÝÃD¡C)
§A¥²¶·¥ýקï /etc/sysconfig (©Î¬O
/etc/rc.conf , ½ÐŪ &man.rc.conf.5;)
³oÀɮ׳̫á¤@Ó³¹¸`¡A±N¤U±©ÒÁ¿¨ìªºÅܼƳ]¦¨
YES ¡G
# Set to YES if you want ibcs2 (SCO) emulation
loaded at startup ibcs2=NO
³o·|¦b¶}¾÷®É±N ibcs2 ³o¤@Ó kernel ¼Ò²Õ¸ü¤J¡C
§AÁÙn±N§Aªº /compat/ibcs2/dev §ï¦¨¤U±³o¼Ë¡G
lrwxr-xr-x 1 root wheel 9 Oct 15 22:20 X0R@ -> /dev/null
lrwxr-xr-x 1 root wheel 7 Oct 15 22:20 nfsd@ -> socksys
-rw-rw-r-- 1 root wheel 0 Oct 28 12:02 null
lrwxr-xr-x 1 root wheel 9 Oct 15 22:20 socksys@ -> /dev/null
crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx
§A¥u»Ýn±N socksys Âà¦V¨ì /dev/null
(½ÐŪ &man.null.4;) ¥hÄF¹L open & close ªº°Ê§@¡C¦b -current
¸Ì±ªº ibcs2 ¬ÛÃöµ{¦¡½X±N·|³B²z¨ä¾lªº³¡¥÷¡A³oºØ§@ªk¤ñ¥H«eªº¤è¦¡
°®²b¤Ó¦h¤F¡C°²¦p§A·Qn¨Ï¥Î spx ¤è±ªº
µ{¦¡¡A¦b§Aªº®Ö¤ß³]©wÀɸ̱ ¥[¤WSPX_HACK ¡C
§Ún¦p¦ó¦b§Úªº¾÷¾¹¤W³]©w INN (Internet News)¡H
¦b§A¨Ï¥Î package ©ÎªÌ¬O port ¦w¸Ë§¹ inn ¤§«á¡ADave Barr's
INN Page ¬OÓ«D±`¦nªº¶}©l¡A§A¥i¥H¦b¨ºÃä§ä¨ìINN ªº FAQ¡C
§Ú¸Ó¨Ï¥Î¨ºÓª©¥»ªº Microsoft FrontPage¡H
Use the Port, Luke¡I¦b ports tree ¤¤¤w¸g¦³¤@Ó¥]§t FrontPage
ªº Apache ª©¥»¤F¡C
FreeBSD ¤ä´© Java ¶Ü¡H
¦³¡A½Ð¬Ý
http://www.FreeBSD.org/java .
¬°¤°»ò§ÚµLªk¦b 3.X-STABLE ¾÷¾¹¤W¶¶§Q½s¦n³oÓ port?
¦pªG§Aªº FreeBSD ª©¥»¬Û¸û -CURRENT ©Î -STABLE ¤§¤U¬O«Ü¥j
¦ªº¸Ü¡A©Î³\§A·|»Ýn¤@ӤɯŠports ªº¤u¨ã¡A¦b
http://www.FreeBSD.org/ports/ ¡C¦pªG§A¥H±N¨ä§ó·s«o¤´µL¥Î¡A
¨º»ò¤@©w¬O¬Y¤H§ó°Ê¤§«á³y¦¨ -CURRENT ¤~¯à¥Î¡A-STABLE µLªk¥Îªº±¡ªp¡C
¥Ñ©ó ports ¤º©Ò¦¬¶°ªº³nÅé¦b -CURRENT ©Î¬O -STABLE ¤W³£n¯à¥Î¡A
©Ò¥H½Ð¾¨³t°e¥XÃö©ó¦¹°ÝÃDªºÂγø§i¡F½Ð¨Ï¥Î &man.send-pr.1; ³oÓ«ü
¥O¨Ó°eÂγø§i¡C
¨º¸Ì¥i¥H§ä±o¨ì ld.so¡H
¦³¨Ç a.out ®æ¦¡ªºÀ³¥Îµ{¦¡·|»Ýn a.out ®æ¦¡ªº¨ç¦¡®w¡A
Netscape Navigator ´N¬O¤@Ó¨Ò¤l¡C¤£¹L¥Î ELF ¨ç¦¡®w½s°_¨Ó
ªº FreeBSD ¹w³]¨Ã¤£·|¦w¸Ëªº a.out ¨ç¦¡®w¡A©Ò¥H±z¥i¯à·|±o
¨ìÃþ¦ü§ä¤£¨ì /usr/libexec/ld.so ªº©ê«è°T
®§¡C¦pªG»¡±zªº¨t²Î¦³³o¦w¸Ë a.out ¨ç¦¡®wªº¥²n¡A³o¨Ç¨ç¦¡®w
(compat22) ¤]¯à°÷§Q¥Î &man.sysinstall.8; ¨Ó¦w¸Ë¡C©ÎªÌ§Q¥Î
FreeBSD ì©l½X¨Ó¦w¸Ë¡G
&prompt.root; cd /usr/src/lib/compat/compat22 &prompt.root; make install clean
¦pªG§A§Æ±æ¨C¦¸ make world ®É·|¦Û°Ê§ó·s
compat22 ¨ç¦¡®w¡A¨º»òקï /etc/make.conf ¡A
¥[¤J COMPAT22=YES ¡C³o¨Ç¬Û®e©ó¥j¦Ñª©¥»ªº¨ç¦¡®w
¤w¸g¨S¤°»ò¦b§ó·s¤F¡A©Ò¥H¤@¯ë»¡¨Ó¬O¤£»Ýn³o¼Ëªº¡C
¦P®É¤]½Ð±z¬Ý¤@¤U 3.1-RELEASE ©M 3.2-RELEASE ªº°É»~ªí(ERRATA)¡C
§Ú§ó·s¤F¨t²Îì©l½X¡A²{¦b§Ún«ç¼Ë¤É¯Å¬YÓ¤w¸g¦w¸Ë¤W
ªº ports ?
FreeBSD ¥»¨¨Ã¨S¦³¦Û°Ê¤É¯Å ports ªº¤u¨ã¡A¦ý¦³¤@¨Ç¥i¥HÅý¤É¯Å
²¤Æ¤@¨Çªº¤pµ{¦¡¡C§A¤]¥i¥H¦Û¤v¸Ë¤WÃB¥~ªº¤u¨ã¨Ó³B²z¡C
&man.pkg.version.1; «ü¥O¥i¥H¦Û°Ê²£¥Í¥Î¨Ó¹F¨ì¦Û°Ê¤É¯Å¨ì
ports tree ³Ì·sª©¥»ªº script¡C
&prompt.root; pkg_version -c > /tmp/myscript
¤@©wn ¦b¤â°Êקï¤@¤U²£¥Í¥X¨Óªº script¡C
¥Ø«eªº &man.pkg.version.1; ¦b script ³Ì«e±¥[¤J &man.exit.1; ±j
¢§A¥hק復¡C
§AÀ³±N°õ¦æ script ©Ò²£¥Íªº¿é¥X°O¿ý¤U¨Ó¡A¦]¬°¸Ì±·|¦³°O¸ü¬Y¨Ç
©|¥¼¤É¯Å¦ý¤w¸g§ó·sªº ports¡C¤£¹L§A¤£¤@©wn¥h¤É¯Å¥¦Ì¡C³q±`¬O¦]¬°
¦³¬YÓ¦@¥Îªº¨ç¦¡®w¤w¸g§ïÅܪ©¥»¸¹¤F¡A¤~n¥h«½s¤@¦¸¨º¨Ç¨Ï¥Î¨ì¸Ó¨ç
¦¡®wªº ports¡C
¦pªG§AªºµwºÐªÅ¶¡«Ü°÷¡A¨º»ò¥i¥H¥Î portupgrade
³oÓ¤u¨ã¨Ó°µ¥þ¦Û°Ê³B¸Ì¡Cportupgrade ¸Ì±¤]¦³
¤@¨Ç¤pµ{¦¡¨Ó²¤Æ package ¤É¯Å¡A¥¦¦b
sysutils/portupgrade ¡C
³oÓ¤u¨ã¬O¥Î Ruby ³oÓ»y¨¥¼gªº¡A©Ò¥H¨Ã¤£¾A¦X¥[¤J¨ì FreeBSD ªºì
©l½X¤¤¡A¤£¹L¨Ã¤£·|¦]¦¹Åý¬Y¨Ç¤H¤£¥Î¥¦¡C
¦pªG§Aªº¨t²Î¤@ª½³£³B©ó¶}¾÷ª¬ºA¡A¥i§Q¥Î &man.periodic.8; ¨t²Î¡A
¨CÓ¬P´Á²£¥Í¤@±i»Ýn¤É¯Åªº²M³æ¡C¥un¦b
/etc/periodic.conf ¥[¤J
weekly_status_pkg_enable="YES" ´N¥i¥H¤F¡C
¬°¤°»ò /bin/sh ³o»òªº¤p¡H¬°¤°»ò FreeBSD
¤£§ï¥Î bash ©ÎªÌ¬O¨ä¥L¤ñ¸û±j®«ªº shell¡H
¦]¬° POSIX »¡¡A¸Ón¦³³o»ò¼Ëªº¤@Ó shell ¦b¤~¦æ¡C
¤ñ¸ûÁcº¾ªºµª®×¡G³\¦h¤H»Ýn¼g¥i¥H¸ó«Ü¦h¥¥xªº shell script ¡C
³o¤]¬O¬°¦ó POSIX ±N shell ¥H¤Î¤u¨ã©RºÙ³£©w¸qªº«D±`¸Ô²Óªº½t¬G¡C
¤j³¡¥÷ªº script ³£¾A¥Î©ó Bourne shell¡A¤S¦]¬°¦³´XÓ«nªº
¼gµ{¦¡©Ò¥Î¨ìªºµ{¦¡©ÎªÌ¨ç¦¡ (&man.make.1; , &man.system.3;,
&man.popen.3;, ÁÙ¦³¦b Perl ©ÎªÌ Tcl ¸Ì±©I¥s¨t²Îµ{¦¡ªº¦a¤è)
³£«ü©w¥Î Bourne shell ¡C¨º»ò¦]¬° Bourne Shell ¦p¦¹ªº¼sªx±`¥Î¡A
¨º»ò¥¦ªº°õ¦æ®Ä²v«K«Ü«n¡A§Ö³t¬O¥¦¨M©w©ÊªºnÂI¤§¤@¡AÁÙn¤£¦û¤Ó¦h
°O¾ÐÅé¡C
¥Ø«eªº /bin/sh ¤w¬O§Ú̹äßÃw¦å¤§§@¡A¥¦¤w
¸gºÉ¶q¦a²Å¦X¼Ð·Ç³W©w¡C¬°¤FÅý¥¦«D±`¤p¡A§ÚÌ®³±¼¤F¤@¨Ç¨ä¥L shell
¦³ªº¤è«K¥\¯à¡C³o¤]¬O¬°¤°»ò ports ¸Ì±ÁÙ¦³«Ü¦h±j®«ªº shell ¡A¹³¬O
bash, scsh, tcsh ¥H¤Î zsh ¡C (§A¥i¥H¦Û¤v¤ñ¸û¤@¤U³o¨Ç shell °õ¦æ
®É©Ò¦ûªº°O¾ÐÅé¤j¤p¡A¥h¬Ý¬Ý ps -u ¦C¥X¨Óªº
VSZ
©M RSS
³o¨âÓÄæ¦ì´Nª¾¹D¤F¡C)
¬°¤°»ò Netscape ©M Opera nªá¦n¤[ªº®É¶¡¤~¯à±Ò°Ê¡H
³q±`¬O¦]¬°§Aªº DNS ¨S¦³³]©w¦n¡C Netscape ¸ò Opera ¦b±Ò°Êªº®ÉÔ
³£·|¥hÀˬd¤@¤U DNS¡Cª½¨ì DNS ¦³¦^À³¡A©ÎªÌ¬OÂ_©wºô¸ô¥Ø«e¬OÂ_½u¤§«á¡A
¥¦Ì¤~·|Åã¥Üµe±¥X¨Ó¡C
Kang-min
Liu
gugod@gugod.org
®Ö¤ß³]©w
§Ú·Q¦Ûq®Ö¤ßµ{¦¡¡A³o·|«Ü§xÃø¶Ü¡H
¤£·|¡I½Ð¬d¾\
¨Ï¥Î¤â¥U¤¤ªº®Ö¤ß³]©w¤@¸` ¡C
§Ú·|«Øij§A¦b§AÅý®Ö¤ß¯à¥¿±`¤u§@«á¡A°µ¤@Ó
kernel.YYMMDD ¤é´Á§Î¦¡ªº³Æ¥÷¡A¦P®É¤]³Æ¥÷
/module ³oӥؿý¦Ü
/modules.YYMMDD ¡C³o¼Ë¤U¦¸¦pªG§A«Ü¤£©¯ªºª±
Ãa¤F³]©w¡A¦Ü¤Ö¥i¥H¤£»Ýn¨Ï¥Î³Ìì©lªº
kernel.GENERIC ¡C¦p§A¥¿±q¤@Ó GENERIC
kernel ¸Ì±¤£¤ä´©ªº±±¨î¾¹¸Ì±Ò°Ê®É¡A³o´NÅã±o¯S§O«n¡C
§Úªº®Ö¤ß¦]¬° _hw_float ¿ò¥¢¦Ó½sĶ¥¢±Ñ¡C
¸Ó«ç»ò×¥¿©O¡H
Åý§Ú²q¬Ý¬Ý¡A§A§â npx0
(¸Ô¨£ &man.npx.4;) ±q§Aªº®Ö¤ß³]©wÀɲ¾°£¤F¡A¦]¬°§A¨S¦³¼Æ¾Ç¹Bºâ¾¹¡A
¹ï¶Ü¡H¿ù¤F¡I:-) ³oÓ npx0 ¬O
¥²¶·n¦³ªº ¡C´Nºâ§A¨S¦³¼Æ¾Ç¹Bºâ¾¹¡A§AÁÙ¬O
¥²¶· ¤Þ¤J npx0 ¸Ë¸m¡C
¬°¤°»ò³y¥X¨Óªº kernel ³o»ò¤j (10MB ¥H¤W) ¡H
³o«Ü¦³¥i¯à¬O¦]¬°¡A§A§â kernel ½s¦¨ °»¿ù¼Ò¦¡
¤F¡C°»¿ù¼Ò¦¡¤§¤Uªº kernel ¸Ì±·|¦sµÛ°»¿ù¥Îªº³\¦h²Å¸¹¡A¦]¦¹·|¤j´T
¼W¥[ kernel ªº¤j¤p¡C¦pªG»¡§Aªº FreeBSD ¬O 3.0 ¥H«áªºª©¥»¡A³o¹ï©ó
®Ä¯à¨Ó»¡¼vÅT¨Ã¤£¤j¡A´X¥G¬O¨S¦³¡C¦Ó¦b¨t²Î·|¦]¬Y¨Çì¦] panic ®É¡A
¦³Ó°»¿ù¼Ò¦¡ªº kernel ¦b¤]®¼¦³¥Îªº¡C
¤£¹L©O¡A¦pªG§AªººÏºÐªÅ¶¡«Ü¤p¡A©ÎªÌ§A´N¬O¤£·Q¥Î°»¿ù¼Ò¦¡ªº
kernel ªº¸Ü¡A½Ð½T»{¥H¤U¨Æ±¡¡G
kernel ³]©wÀɸ̱¨S¦³³o¤@¦æ¡G
makeoptions DEBUGS=-g
°õ¦æ &man.config.8; ®É¨S¦³¥[¤W -g
³oӿﶵ¡C
¥H¤W¨â¥ó¨Æ±¡³£·|Åý§A½s¥X¤@Ó°»¿ù¼Ò¦¡ªº kernel¡C¦ý¥unÁקK¤§¡A
´N¥i¥H½s¥X¤@Ó¥¿±`ªº kernel¡A¦Ó§A¤]·|ª`·N¨ì¡Akernel ©úÅ㪺Åܤp¤F¡F
¤j³¡¥÷ªº kernel ³£®t¤£¦h¦b 1.5MB ¨ì 2MB ¤§¶¡¡C
¬°¦ó¥X²{¤F multi-port serial code ªº¤¤Â_½Ä¬ð¡H
·í§Ú½sĶ¤@Ó multi-port serial code ªº®Ö¤ß®É¡A¥¦§i¶D§Ú¥u¦³
²Ä¤@Ó³Q°»´ú¨ì¡A¨ä¥Lªº«h¦]¤¤Â_½Ä¬ð¦Ó¸õ¹L¤F¡A§Ú¸Ó«ç»ò×¥¿¥¦¡H
³oÓ°ÝÃD¬O¦]¬° FreeBSD ¨Ï¥Î¤º«Øµ{¦¡½XÁקK¦]¬°µwÅé©Î³nÅé½Ä¬ð
¾ÉP®Ö¤ßµ{¦¡¹L©óªÎ¤j©ÎµL¥Î¡Cn×¥¿³oºØ±¡§Îªº¤èªk¬O°£¤F¤@Ó port
¥~§â¨ä¥L©Ò¦³ªº IRQ ³]©w³£°µ«O¯d¡C³o¸Ì¦³¤@Ó½d¨Ò¡G
#
# Multiport high-speed serial line - 16550 UARTS
#
device sio2 at isa? port 0x2a0 tty irq 5 flags 0x501 vector siointr
device sio3 at isa? port 0x2a8 tty flags 0x501 vector siointr
device sio4 at isa? port 0x2b0 tty flags 0x501 vector siointr
device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr
¬°¤°»ò§Ú¤@Ó kernel ³£½s¤£°_¨Ó¡H¬Æ¦Ü GENERIC ¤]¤£¦æ¡H
³o¦³«Ü¦hºØ¥i¯àªºì¦]¡G
§A¨S¦³¥Î·sªº make buildkernel »P
make installkernel ³o¨âÓ¤èªk¨Ó½s¡A¦Ó¥¿¦n
§Aªº¨t²Îì©l½Xªºª©¥»©M¥¿¦b°õ¦æªº¨t²Î®Ö¤ßª©¥»¤£¤@¼Ë (¹³¬O¡A
¦b¶] 4.0-RELEASE ªº¨t²Î¤W¹Á¸ÕµÛ½s 4.3-RELEASE)¡C¦pªG»¡§An¤É
¯Å¨t²Îªº¸Ü¡A½Ð°È¥²¥h¬Ý¬Ý /usr/src/UPDATING
³oÓÀɮסA¯S§Oª`·N³Ì«á±ªº COMMON ITEMS
³oÓ¤p¸`¡C
§A¤w¸g¥Î¤W make buildkernel ¥H¤Î
make installkernel ¤F¡A¦ý¬O¦b
make buildworld ®É¥¢±Ñ¤F¡C¥i±¤ªº¬O¡A
make buildkernel n¦¨¥\¡A»Ýn¨Ì¿à
make buildworld «á³y¥X¨Óªº¤@¨ÇÀɮסC
´Nºâ¬O§A¦b½s FreeBSD-STABLE¡A
ÁÙ¬O¦³¥i¯à§A§ì¨ì¤F¥¿¦bק襤¡A©ÎµÛ¦]¬°¬Y¨Ç½t¬G¦Ó®Ú¥»ÁÙ¨S§ï¦n
ªºì©l½X¡FÁöµM»¡ FreeBSD-STABLE
¤j³¡¥÷ªº®ÉÔ³£¬O¥i¥H½sªº¡A¦ý¥u¦³ RELEASE ¤~¬O«OÃÒ¥i¥H½sªº¡C¸I
¨ì³oÓ°ÝÃD®É¡A¦A¦¸§ó·sì©l½X¨Ã¥B¦A¸Õ¸Õ¬Ý¡C¤]¦³¥i¯à¬O©ñì©l½Xªº
¦øªA¾¹¥X²{¬Y¨Ç°ÝÃD¡A©Ò¥H§ó·sì©l½X®É¤]¸Õ¸Õ±q¤£¦P¦øªA¾¹¨Ó§ó·s¬Ý
¬Ý¡C
Disks, Filesystems, and Boot Loaders
How can I add my new hard disk to my FreeBSD system?
See the Disk Formatting Tutorial at
www.FreeBSD.org .
How do I move my system over to my huge new disk?
The best way is to reinstall the OS on the new
disk, then move the user data over. This is highly
recommended if you have been tracking -stable for more
than one release, or have updated a release instead of
installing a new one. You can install booteasy on both
disks with &man.boot0cfg.8;, and dual boot them until
you are happy with the new configuration. Skip the
next paragraph to find out how to move the data after
doing this.
Should you decide not to do a fresh install, you
need to partition and label the new disk with either
/stand/sysinstall , or &man.fdisk.8;
and &man.disklabel.8;. You should also install booteasy
on both disks with &man.boot0cfg.8;, so that you can
dual boot to the old or new system after the copying
is done. See the
formatting-media article for details on this
process.
Now you have the new disk set up, and are ready
to move the data. Unfortunately, you cannot just blindly
copy the data. Things like device files (in
/dev ), flags, and links tend to
screw that up. You need to use tools that understand
these things, which means &man.dump.8;.
Although it is suggested that you move the data in single user
mode, it is not required.
You should never use anything but &man.dump.8; and
&man.restore.8; to move the root file system. The
&man.tar.1; command may work - then again, it may not.
You should also use &man.dump.8; and &man.restore.8;
if you are moving a single partition to another empty
partition. The sequence of steps to use dump to move
a partitions data to a new partition is:
newfs the new partition.
mount it on a temporary mount point.
cd to that directory.
dump the old partition, piping output to the
new one.
For example, if you are going to move root to
/dev/ad1s1a , with
/mnt as the temporary mount point,
it is:
&prompt.root; newfs /dev/ad1s1a
&prompt.root; mount /dev/ad1s1a /mnt
&prompt.root; cd /mnt
&prompt.root; dump 0af - / | restore xf -
Rearranging your partitions with dump takes a bit more
work. To merge a partition like /var
into its parent, create the new partition large enough
for both, move the parent partition as described above,
then move the child partition into the empty directory
that the first move created:
&prompt.root; newfs /dev/ad1s1a
&prompt.root; mount /dev/ad1s1a /mnt
&prompt.root; cd /mnt
&prompt.root; dump 0af - / | restore xf -
&prompt.root; cd var
&prompt.root; dump 0af - /var | restore xf -
To split a directory from its parent, say putting
/var on its own partition when it was not
before, create both partitions, then mount the child partition
on the appropriate directory in the temporary mount point, then
move the old single partition:
&prompt.root; newfs /dev/ad1s1a
&prompt.root; newfs /dev/ad1s1d
&prompt.root; mount /dev/ad1s1a /mnt
&prompt.root; mkdir /mnt/var
&prompt.root; mount /dev/ad1s1d /mnt/var
&prompt.root; cd /mnt
&prompt.root; dump 0af - / | restore xf -
You might prefer &man.cpio.1;, &man.pax.1;,
&man.tar.1; to &man.dump.8; for user data. At the time of
this writing, these are known to lose file flag information,
so use them with caution.
Will a dangerously dedicated
disk endanger
my health?
The installation procedure allows
you to chose two different methods in partitioning your
hard disk(s). The default way makes it compatible with other
operating systems on the same machine, by using fdisk table
entries (called slices
in FreeBSD), with a
FreeBSD slice that employs partitions of its own. Optionally,
one can chose to install a boot-selector to switch between the
possible operating systems on the disk(s). The alternative uses
the entire disk for FreeBSD, and makes no attempt to be
compatible with other operating systems.
So why it is called dangerous
? A disk in
this mode does not contain what normal PC utilities would
consider a valid fdisk table. Depending on how well they have
been designed, they might complain at you once they are getting
in contact with such a disk, or even worse, they might damage
the BSD bootstrap without even asking or notifying you. In
addition, the dangerously dedicated
disk's
layout is known to confuse many BIOSes, including those from
AWARD (e.g. as found in HP Netserver and Micronics systems as
well as many others) and Symbios/NCR (for the popular 53C8xx
range of SCSI controllers). This is not a complete list, there
are more. Symptoms of this confusion include the read
error message printed by the FreeBSD bootstrap when it
cannot find itself, as well as system lockups when
booting.
Why have this mode at all then? It only saves a few kbytes
of disk space, and it can cause real problems for a new
installation. Dangerously dedicated
mode's
origins lie in a desire to avoid one of the most common
problems plaguing new FreeBSD installers - matching the BIOS
geometry
numbers for a disk to the disk
itself.
Geometry
is an outdated concept, but one
still at the heart of the PC's BIOS and its interaction with
disks. When the FreeBSD installer creates slices, it has to
record the location of these slices on the disk in a fashion
that corresponds with the way the BIOS expects to find them. If
it gets it wrong, you will not be able to boot.
Dangerously dedicated
mode tries to work
around this by making the problem simpler. In some cases, it
gets it right. But it is meant to be used as a last-ditch
alternative - there are better ways to solve the problem 99
times out of 100.
So, how do you avoid the need for DD
mode
when you are installing? Start by making a note of the geometry
that your BIOS claims to be using for your disks. You can
arrange to have the kernel print this as it boots by specifying
-v at the boot: prompt, or
using boot -v in the loader. Just before the
installer starts, the kernel will print a list of BIOS
geometries. Do not panic - wait for the installer to start and
then use scrollback to read the numbers. Typically the BIOS
disk units will be in the same order that FreeBSD lists your
disks, first IDE, then SCSI.
When you are slicing up your disk, check that the disk
geometry displayed in the FDISK screen is correct (ie. it
matches the BIOS numbers); if it is wrong, use the
g key to fix it. You may have to do this if
there is absolutely nothing on the disk, or if the disk has been
moved from another system. Note that this is only an issue with
the disk that you are going to boot from; FreeBSD will sort
itself out just fine with any other disks you may have.
Once you have got the BIOS and FreeBSD agreeing about the
geometry of the disk, your problems are almost guaranteed to be
over, and with no need for DD
mode at all. If,
however, you are still greeted with the dreaded read
error message when you try to boot, it is time to cross
your fingers and go for it - there is nothing left to
lose.
To return a dangerously dedicated
disk
for normal PC use, there are basically two options. The first
is, you write enough NULL bytes over the MBR to make any
subsequent installation believe this to be a blank disk. You
can do this for example with
&prompt.root; dd if=/dev/zero of=/dev/rda0 count=15
Alternatively, the undocumented DOS
feature
C:\> fdisk /mbr
will to install a new master boot record as well, thus
clobbering the BSD bootstrap.
Which partitions can safely use softupdates? I have
heard that softupdates on / can cause
problems.
Short answer: you can usually use softupdates safely
on all partitions.
Long answer: There used to be some concern over using
softupdates on the root partition. Softupdates has two
characteristics that caused this. First, a softupdates
partition has a small chance of losing data during a
system crash. (The partition will not be corrupted; the
data will simply be lost.) Also, softupdates can cause
temporary space shortages.
When using softupdates, the kernel can take up to
thirty seconds to actually write changes to the physical
disk. If you delete a large file, the file still resides
on disk until the kernel actually performs the deletion.
This can cause a very simple race condition. Suppose you
delete one large file and immediately create another large
file. The first large file is not yet actually removed
from the physical disk, so the disk might not have enough
room for the second large file. You get an error that the
partition does not have enough space, although you know
perfectly well that you just released a large chunk of
space! When you try again mere seconds later, the file
creation works as you expect. This has left more than one
user scratching his head and doubting his sanity, the
FreeBSD filesystem, or both.
If a system should crash after the kernel accepts a
chunk of data for writing to disk, but before that data is
actually written out, data could be lost or corrupted.
This risk is extremely small, but generally manageable.
Use of IDE write caching greatly increases this risk; it
is strongly recommended that you disable IDE write caching
when using softupdates.
These issues affect all partitions using softupdates.
So, what does this mean for the root partition?
Vital information on the root partition changes very
rarely. Files such as /kernel and
the contents of /etc only change
during system maintenance, or when users change their
passwords. If the system crashed during the
thirty-second window after such a change is made, it is
possible that data could be lost. This risk is negligible
for most applications, but you should be aware that it
exists. If your system cannot tolerate this much risk,
do not use softupdates on the root filesystem!
/ is traditionally one of the
smallest partitions. By default, FreeBSD puts the
/tmp directory on
/ . If you have a busy
/tmp , you might see intermittent
space problems. Symlinking /tmp to
/var/tmp will solve this
problem.
What is inappropriate about my ccd?
The symptom of this is:
&prompt.root; ccdconfig -C
ccdconfig: ioctl (CCDIOCSET): /dev/ccd0c: Inappropriate file type or format
This usually happens when you are trying to concatenate
the c partitions, which default to type
unused . The ccd driver requires the
underlying partition type to be FS_BSDFFS. Edit the disklabel
of the disks you are trying to concatenate and change the types
of partitions to 4.2BSD .
Why can I not edit the disklabel on my ccd?
The symptom of this is:
&prompt.root; disklabel ccd0
(it prints something sensible here, so let us try to edit it)
&prompt.root; disklabel -e ccd0
(edit, save, quit)
disklabel: ioctl DIOCWDINFO: No disk label on disk;
use "disklabel -r" to install initial label
This is because the disklabel returned by ccd is actually
a fake
one that is not really on the disk.
You can solve this problem by writing it back explicitly,
as in:
&prompt.root; disklabel ccd0 > /tmp/disklabel.tmp
&prompt.root; disklabel -Rr ccd0 /tmp/disklabel.tmp
&prompt.root; disklabel -e ccd0
(this will work now)
Can I mount other foreign filesystems under FreeBSD?
Digital UNIX
UFS CDROMs can be mounted directly on FreeBSD.
Mounting disk partitions from Digital UNIX and other
systems that support UFS may be more complex, depending
on the details of the disk partitioning for the operating
system in question.
Linux
As of 2.2, FreeBSD supports ext2fs
partitions. See &man.mount.ext2fs.8; for more
information.
NT
A read-only NTFS driver exists for FreeBSD. For more
information, see this tutorial by Mark Ovens at
http://ukug.uk.FreeBSD.org/~mark/ntfs_install.html .
Any other information on this subject would be
appreciated.
How do I mount a secondary DOS partition?
The secondary DOS partitions are found after ALL the primary
partitions. For example, if you have an E
partition as the second DOS partition on the second SCSI drive,
you need to create the special files for slice 5
in /dev, then mount /dev/da1s5:
&prompt.root; cd /dev
&prompt.root; sh MAKEDEV da1s5
&prompt.root; mount -t msdos /dev/da1s5 /dos/e
Is there a cryptographic filesystem for &os;?
Yes; see the security/cfs port.
How can I use the NT loader to boot FreeBSD?
This procedure is slightly different for 2.2.x and 3.x
(with the 3-stage boot) systems.
The general idea is that you copy the first sector of your
native root FreeBSD partition into a file in the DOS/NT
partition. Assuming you name that file something like
c:\bootsect.bsd (inspired by
c:\bootsect.dos ), you can then edit the
c:\boot.ini file to come up with something
like this:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows NT"
C:\BOOTSECT.BSD="FreeBSD"
C:\="DOS"
For 2.2.x systems this procedure assumes that DOS, NT,
FreeBSD, or whatever have been installed into their respective
fdisk partitions on the same
disk. This example was tested on a system where DOS & NT
were on the first fdisk partition, and FreeBSD on the second.
FreeBSD was also set up to boot from its native partition, not
the disk's MBR.
Mount a DOS-formatted floppy (if you have converted to NTFS)
or the FAT partition, under, say,
/mnt .
&prompt.root; dd if=/dev/rda0a of=/mnt/bootsect.bsd bs=512 count=1
Reboot into DOS or NT. NTFS users copy the
bootsect.bsd and/or the
bootsect.lnx file from the floppy to
C:\ . Modify the attributes (permissions)
on boot.ini with:
C:\> attrib -s -r c:\boot.ini
Edit to add the appropriate entries from the example
boot.ini above, and restore the
attributes:
C:\> attrib +s +r c:\boot.ini
If FreeBSD is booting from the MBR, restore it with the DOS
fdisk command after you reconfigure them to
boot from their native partitions.
For FreeBSD 3.x systems the procedure is somewhat
simpler.
If FreeBSD is installed on the same disk as the NT boot
partition simply copy /boot/boot1 to
C:\BOOTSECT.BSD However, if FreeBSD is
installed on a different disk /boot/boot1
will not work, /boot/boot0 is needed.
DO NOT SIMPLY COPY /boot/boot0
INSTEAD OF /boot/boot1 , YOU WILL
OVERWRITE YOUR PARTITION TABLE AND RENDER YOUR COMPUTER
UN-BOOTABLE!
/boot/boot0 needs to be installed using
sysinstall by selecting the FreeBSD boot manager on the
screen which asks if you wish to use a boot manager. This is
because /boot/boot0 has the partition
table area filled with NULL characters but sysinstall copies
the partition table before copying
/boot/boot0 to the MBR.
When the FreeBSD boot manager runs it records the last
OS booted by setting the active flag on the partition table
entry for that OS and then writes the whole 512-bytes of itself
back to the MBR so if you just copy
/boot/boot0 to
C:\BOOTSECT.BSD then it writes an empty
partition table, with the active flag set on one entry, to the
MBR.
How do I boot FreeBSD and Linux from LILO?
If you have FreeBSD and Linux on the same disk, just follow
LILO's installation instructions for booting a non-Linux
operating system. Very briefly, these are:
Boot Linux, and add the following lines to
/etc/lilo.conf :
other=/dev/hda2
table=/dev/hda
label=FreeBSD
(the above assumes that your FreeBSD slice is known to Linux
as /dev/hda2 ; tailor to suit your setup).
Then, run lilo as root and you should be
done.
If FreeBSD resides on another disk, you need to add
loader=/boot/chain.b to the LILO entry.
For example:
other=/dev/dab4
table=/dev/dab
loader=/boot/chain.b
label=FreeBSD
In some cases you may need to specify the BIOS drive number
to the FreeBSD boot loader to successfully boot off the second
disk. For example, if your FreeBSD SCSI disk is probed by BIOS
as BIOS disk 1, at the FreeBSD boot loader prompt you need to
specify:
Boot: 1:da(0,a)/kernel
On FreeBSD 2.2.5 and later, you can configure
&man.boot.8;
to automatically do this for you at boot time.
The
Linux+FreeBSD mini-HOWTO is a good reference for
FreeBSD and Linux interoperability issues.
How do I boot FreeBSD and Linux using BootEasy?
Install LILO at the start of your Linux boot partition
instead of in the Master Boot Record. You can then boot LILO
from BootEasy.
If you are running Windows-95 and Linux this is recommended
anyway, to make it simpler to get Linux booting again if you
should need to reinstall Windows95 (which is a Jealous
Operating System, and will bear no other Operating Systems in
the Master Boot Record).
How do I change the boot prompt from ??? to
something more meaningful?
You can not do that with the standard boot manager without
rewriting it. There are a number of other boot managers
in the sysutils ports category that
provide this functionality.
I have a new removable drive, how do I use it?
Whether it is a removable drive like a ZIP or an EZ drive
(or even a floppy, if you want to use it that way), or a new
hard disk, once it is installed and recognized by the system,
and you have your cartridge/floppy/whatever slotted in, things
are pretty much the same for all devices.
(this section is based on
Mark Mayo's ZIP FAQ )
If it is a ZIP drive or a floppy, you have already got a DOS
filesystem on it, you can use a command like this:
&prompt.root; mount -t msdos /dev/fd0c /floppy
if it is a floppy, or this:
&prompt.root; mount -t msdos /dev/da2s4 /zip
for a ZIP disk with the factory configuration.
For other disks, see how they are laid out using
&man.fdisk.8; or
&man.sysinstall.8;.
The rest of the examples will be for a ZIP drive on da2,
the third SCSI disk.
Unless it is a floppy, or a removable you plan on sharing
with other people, it is probably a better idea to stick a BSD
file system on it. You will get long filename support, at least a
2X improvement in performance, and a lot more stability. First,
you need to redo the DOS-level partitions/filesystems. You can
either use &man.fdisk.8; or
/stand/sysinstall , or for a small drive
that you do not want to bother with multiple operating system
support on, just blow away the whole FAT partition table
(slices) and just use the BSD partitioning:
&prompt.root; dd if=/dev/zero of=/dev/rda2 count=2
&prompt.root; disklabel -Brw da2 auto
You can use disklabel or
/stand/sysinstall to create multiple BSD
partitions. You will certainly want to do this if you are adding
swap space on a fixed disk, but it is probably irrelevant on a
removable drive like a ZIP.
Finally, create a new file system, this one is on our ZIP
drive using the whole disk:
&prompt.root; newfs /dev/rda2c
and mount it:
&prompt.root; mount /dev/da2c /zip
and it is probably a good idea to add a line like this to
/etc/fstab (see &man.fstab.5;) so you can just type
mount /zip in the future:
/dev/da2c /zip ffs rw,noauto 0 0
Why do I get Incorrect super block when
mounting a CDROM?
You have to tell &man.mount.8; the type of the device
that you want to mount. This is described in the Handbook section on
optical media , specifically the section Using Data
CDs .
Why do I get Device not configured when
mounting a CDROM?
This generally means that there is no CDROM in the
CDROM drive, or the drive is not visible on the
bus. Please see the Using Data
CDs section of the Handbook for a detailed
discussion of this issue.
Why do all non-English characters in filenames show up as
?
on my CDs when mounted in FreeBSD?
Your CDROM probably uses the Joliet
extension for storing information about files and
directories. This is discussed in the Handbook chapter on
creating and
using CDROMs , specifically the section on Using Data
CDROMs .
I burned a CD under FreeBSD and now I can not read it
under any other operating system. Why?
You most likely burned a raw file to your CD, rather
than creating an ISO 9660 filesystem. Take a look at the
Handbook
chapter on creating CDROMs , particularly the
section on burning raw
data CDs .
How can I create an image of a data CD?
This is discussed in the Handbook section on duplicating
data CDs . For more on working with CDROMs, see the
Creating CDs
Section in the Storage chapter in the
Handbook.
Why can I not mount an audio
CD?
If you try to mount an audio CD, you will get an error
like cd9660: /dev/acd0c: Invalid
argument . This is because
mount only works on filesystems. Audio
CDs do not have filesystems; they just have data. You
need a program that reads audio CDs, such as the
audio/xmcd port.
How do I mount a multi-session CD?
By default, &man.mount.8; will attempt to mount the
last data track (session) of a CD. If you would like to
load an earlier session, you must use the
-s command line argument. Please see
&man.mount.cd9660.8; for specific examples.
How do I let ordinary users mount floppies, CDROMs and
other removable media?
Ordinary users can be permitted to mount devices. Here is
how:
As root set the sysctl variable
vfs.usermount to
1 .
&prompt.root; sysctl -w vfs.usermount=1
As root assign the appropriate
permissions to the block device associated with the
removable media.
For example, to allow users to mount the first floppy
drive, use:
&prompt.root; chmod 666 /dev/fd0
To allow users in the group
operator to mount the CDROM drive,
use:
&prompt.root; chgrp operator /dev/cd0c
&prompt.root; chmod 640 /dev/cd0c
Finally, add the line
vfs.usermount =1 to the file
/etc/sysctl.conf so that it is reset
at system boot time.
All users can now mount the floppy
/dev/fd0 onto a directory that they
own:
&prompt.user; mkdir ~/my-mount-point
&prompt.user; mount -t msdos /dev/fd0 ~/my-mount-point
Users in group operator can now
mount the CDROM /dev/cd0c onto a
directory that they own:
&prompt.user; mkdir ~/my-mount-point
&prompt.user; mount -t msdos /dev/cd0c ~/my-mount-point
Unmounting the device is simple:
- &prompt.user; umount~/my-mount-point
+ &prompt.user; umount ~/my-mount-point
Enabling vfs.usermount , however, has
negative security implications. A better way to access MSDOS
formatted media is to use the mtools package in the ports collection.
The du and df
commands show different amounts of disk space available.
What is going on?
You need to understand what du and
df really do. du
goes through the directory tree, measures how large each
file is, and presents the totals. df
just asks the filesystem how much space it has left. They
seem to be the same thing, but a file without a directory
entry will affect df but not
du .
When a program is using a file, and you delete the
file, the file is not really removed from the filesystem
until the program stops using it. The file is immediately
deleted from the directory listing, however. You can see
this easily enough with a program such as
more . Assume you have a file large
enough that its presence affects the output of
du and df . (Since
disks can be so large today, this might be a
very large file!) If you delete this
file while using more on it,
more does not immediately choke and
complain that it cannot view the file. The entry is
simply removed from the directory so no other program or
user can access it. du shows that it
is gone — it has walked the directory tree and the file
is not listed. df shows that it is
still there, as the filesystem knows that
more is still using that space. Once
you end the more session,
du and df will
agree.
Note that softupdates can delay the freeing of disk
space; you might need to wait up to 30 seconds for the
change to be visible!
This situation is common on web servers. Many people
set up a FreeBSD web server and forget to rotate the log
files. The access log fills up /var .
The new administrator deletes the file, but the system
still complains that the partition is full. Stopping and
restarting the web server program would free the file,
allowing the system to release the disk space. To prevent
this from happening, set up &man.newsyslog.8;.
How can I add more swap space?
In the Configuration and
Tuning section of the Handbook, you will find a
section
describing how to do this.
Wei-Hon
Chen
plasmaball@pchome.com.tw
¨t²ÎºÞ²z
¨t²Î°_©l³]©wÀɦbþ¡H
±q 2.0.5R ¨ì 2.2.1R¡A¥Dnªº³]©wÀɬO
/etc/sysconfig ¡C©Ò¦³ªº¿ï¶µ³£³Q«ü©w¦b³oÓÀÉ¡A
¦Ó¨ä¥L¹³ /etc/rc (°Ñ¨£ &man.rc.8;)
©M /etc/netstart ¥u¬O¤Þ¥Î¥¦¡C
Æ[¹î /etc/sysconfig ³oÓÀɨÃ×¥¿¨äÈ¥H
¾A¦X§Aªº¨t²Î¡C³oÓÀɥεù¸Ñ¶ñº¡¥Hªí¥Ü¦ó³B¸Ó©ñ¸m¤°»ò³]©w¡C
¦b post-2.2.1 ¥H«á¤Î 3.0¡A/etc/sysconfig
¥ç§ó¦W¬°¤@Ó§ó®e©ö´yzªºÀɦW¥s &man.rc.conf.5; ¡A¨Ã¥B»yªk²¤Æ¤F¨Ç¡C
/etc/netstart ¥ç§ó¦W¬°
/etc/rc.network ¦]¦¹©Ò¦³ªºÀɮ׳£¥i¥H¥Î
cp /usr/src/etc/rc* /etc ¨Ó«þ¨©¡C
¦b 3.1 ¥H¤Î¡A/etc/rc.conf ³Q²¾¨ì
/etc/defaults/rc.conf ¡C
¤d¸U¤£n½s¿è³oÓÀÉ¡I ¦pªG
/etc/defaults/rc.conf ¤º¦³·Qn§ó°Êªº¶µ¥Ø¡A
§AÀ³¸Ó±N¨º¤@¦æªº¤º®e«þ¨©¨ì /etc/rc.conf ¡A
µM«á¦Aק復¡C
¨Ò¦p FreeBSD 3.1 ¤Î¥H«áªºª©¥»¤º¡A¦³¤@Ó DNS ¦øªA¾¹ named¡A
¦Ó§A·Qn±Ò°Ê¥¦¡C§A©Ò»Ýn§@ªº¨Æ´N¬O¡G
&prompt.root; echo named_enable="YES" >> /etc/rc.conf
·Qn¦b FreeBSD 3.1 ¤Î¥H«áªºª©¥»¤¤¡A±Ò°Ê¥»¦aºÝªA°Èªº¸Ü¡A±N
shell script ¸m©ó /usr/local/etc/rc.d ¥Ø¿ý
¤U¡C³o¨Ç shell script À³¸Ó³]©w¦¨¥i°õ¦æ¡A¨Ã¥BÀɦW¥H .sh µ²§ô¡C
¦b FreeBSD 3.0 ¤Î§ó¦ªºª©¥»¤¤¡A§AÀ³¸Óª½±µ½s¿è
/etc/rc.local ÀÉ¡C
/etc/rc.serial ¥Î¨Óªì©l¤Æ§Ç¦C°ð
¡]¹³¬OÂê©w°ðªº¯S©Êµ¥¡^¡C
/etc/rc.i386 ¬O Intel ±M¥Î³]©w¡A
¹³¬O iBCS2 ¼ÒÀÀ©Î¬O PC ¨t²Î¥D±±¥x³]©w¡C
§Ú¸Ó¦p¦ó²³æ¦a¥[¤J¨Ï¥ÎªÌ¡H
¨Ï¥Î &man.adduser.8; «ü¥O¡C¦pªG»Ýn§ó½ÆÂøªº¨Ï¥Î¤è¦¡¡A
½Ð¥Î &man.pw.8; ³oÓ«ü¥O¡C
n¦A¦¸²¾°£¨Ï¥ÎªÌ¡A¨Ï¥Î &man.rmuser.8; «ü¥O¡CÁÙ¦³¡A
&man.pw.8; ¤]¥i¥H¨Ï¥Î¡C
¦b§Ú½s¿è crontab Àɮפ§«á¡A¬°¤°»ò§Ú¦Ñ¬O¦¬¨ì³o¼Ëªº°T®§¡G
root: not found ¡H
³q±`³£¬O¦]¬°½s¿è¤F¨t²Îªº crontab
(/etc/crontab ) µM«á´N¥Î &man.crontab.1;
¥h¦w¸Ë¥¦¡G
&prompt.root; crontab /etc/crontab
³o¼Ë§@¬O¤£¹ïªº¡C¨t²Îªº crontab ©M &man.crontab.1;
©Ò§ó·sªº¨Ï¥ÎªÌªº crontab ®æ¦¡¨Ã¤£¤@¼Ë (&man.crontab.5;
»¡©ú¤å¥ó°w¹ï®t²§³B¦³¸Ô²Óªº»¡©ú)¡C
¦pªG§A¤w¸g¥Î³oºØ¤èªk¡AÃB¥~¦h¥Xªº crontab ¥u´N¬O
/etc/crontab ªº«þ¨©¡A¥u¬O®æ¦¡¬O¿ù»~ªº¡C
¥i¥Î¥H¤Uªº©R¥O§R°£¡G
&prompt.root; crontab -r
¤U¦¸§A½s¿è /etc/crontab Àɮתº®ÉÔ¡A
§A¤£¥Î§@¥ô¦ó°Ê§@¥h³qª¾ &man.cron.8; ¡A¥¦¦Û°Ê·|¥h°»´ú¬O§_¦³§ó°Ê¡C
¦pªG§A·Qn¨C¤Ñ¡B¨C¶g¡B©Î¬O¨C¤ë©T©w°õ¦æ¬Y¨Ç°Ê§@¤@¦¸¡A¤]³\¥[Ó
shell script ¦b /usr/local/etc/periodic
¥Ø¿ý¤U·|§ó¦n¡A¨t²Îªº cron ·|©T©w°õ¦æ &man.periodic.8; ©R¥O¡A
¥¦¥i±N§Aªºµ{¦¡©M¨ä¥¦ªº¨t²Î¶g´Á©Ê¤u§@¤@°_°õ¦æ¡C
³oÓ¿ù»~ªº¯u¥¿ì¦]¡A¬O¦]¬°¨t²Îªº crontab ¦³¤@ÓÃB¥~ªºÄæ¦ì¡A
»¡©ú¸Ó©R¥On¥H¤°»ò¨Ï¥ÎªÌ¨¥÷°õ¦æ¡C¦b FreeBSD ªº¹w³]¨t²Î crontab
¤¤¡A©Ò¦³ªº¶µ¥Ø³£¬O root ¡C ·í³oÓ crontab
³Q·í§@¬O root ªº¨Ï¥ÎªÌ crontab (¥¦©M¨t²Îªº
crontab ¬O ¤£ ¤@¼Ëªº)¡A&man.cron.8; ·|¥H¬°
root ¦r¦ê¬O±ý°õ¦æªº©R¥Oªº²Ä¤@Ó¦r¡A¦ý¬O¹ê»Ú¤W
¨Ã¨S¦³³o¼Ëªº©R¥O¦s¦b¡C
¬°¤°»ò§Ú·Qn¥Î su ¦¨¬° root ®É¡A·|±o¨ì
you are not in the correct group to su root
ªº¿ù»~°T®§¡H
³o¬O¤@Ó¦w¥þ¯S©Ê¡C·Qn§Q¥Î su ¦¨¬° root
(©Î¨ä¥¦¦³ superuser Åvªº±b¸¹)¡A§A¤@©wn¦b
wheel ¸s²Õ¤º¡C¦pªG¨S¦³³oÓ¯S©Êªº¸Ü¡A
¥ô¦ó¤H¥un¦b¨t²Î¸Ì¦³±b¸¹¡A¨Ã¥B«ê¥©ª¾¹D root
ªº±K½X¡A´N¥i¥H¨ú±o superuser µ¥¯ÅªºÅv¥H¦s¨ú¨t²Î¡C¦³¤F³oÓ¯S©Ê¡A
³o¼Ëªº±¡ªp´N¤£·|µo¥Í¡F¦pªG¨Ï¥ÎªÌ¤£¦b wheel
¸s²Õ¤ºªº¸Ü¡A&man.su.1; ·|Åý¥L̳s¸ÕµÛÁä¤J±K½Xªº¾÷·|³£¨S¦³¡C
nÅý¬Y¤H¥i¥H§Q¥Î su ¦¨¬° root ªº¸Ü¡A
¥un§â¥LÌ©ñ¤J wheel ¸s²Õ¤º§Y¥i¡C
§Ú¦b rc.conf ÁÙ¬O¬YÓ°_°ÊÀɮ׸̥ǤF¿ù»~¡A
¦]¬°Àɮרt²ÎÅܦ¨°ßŪªº¡A§ÚµLªk¥h½s¿è¥¦¡C§Ú¸Ó«ç»ò¿ì¡H
·í¹q¸£°Ý§A shell §¹¾ã¸ô®|¦W®É¡A¥un«ö ENTER
¡AµM«á°õ¦æ mount / ¥HŪ¼g¼Ò¦¡
«·s±¾¸ü®ÚÀɮרt²Î¡C§A¤]³\»Ýn°õ¦æ mount -a -t ufs
¡A±N§AºD¥Îªº¤å¦r½s¿è¾¹©Ò¦bªºÀɮרt²Î±¾¸ü¤W¨Ó¡C¦pªG
§AºD¥Îªº¤å¦r½s¿è¾¹¦bºô¸ôÀɮרt²Î¤Wªº¸Ü¡A§A¥²¶·¥ý¤â°Ê±Nºô¸ô³]©w
°_¨Ó¡A¥H«K±Nºô¸ôÀɮרt²Î±¾¸ü¤W¨Ó¡A©Î¬O¨Ï¥Î¥»¦aºÝÀɮרt²Î¤Wªº
½s¿è¾¹¡A¨Ò¦p &man.ed.1;¡C
¦pªG§A·Qn¨Ï¥Î¹³ &man.vi.1; ©Î¬O &man.emacs.1; µ¥ªº¥þ¿Ã¹õ
¤å¦r½s¿è¾¹ªº¸Ü¡A§A¤]»Ýn°õ¦æ
export TERM=cons25 ¡A¥H«KÅý³o¨Ç½s¿è¾¹¯à°÷±q
&man.termcap.5; ¸ê®Æ®w¸ÌŪ¨ú¥¿½Tªº¸ê®Æ¡C
·í§A¤w¸g§¹¦¨¤F³o¨Ç¨BÆJ«á¡A§A¥i¥H·Ó§A¥±`קï¤åªk¿ù»~ªº¤è¦¡
¥h½s¿è /etc/rc.conf ÀɮסC¦b®Ö¤ß (kernel)
±Ò°Ê®É©ÒÅã¥Üªº¿ù»~°T®§¡A¯à°÷§i¶D§AÀɮפ¤þ¤@¦æ¦³¿ù»~¡C
¬°¤°»ò§Ú¨S¿ìªk³]©w§Úªº¦Lªí¾÷¡H
½Ð°Ñ¦Ò¤@¤U Handbook ¤¤¡A¦³Ãö¦C¦Lªº³¡¥÷¡C¥¦À³¸Ó¯à°÷¸Ñ¨M
§A¤j³¡¥÷ªº°ÝÃD¡C½Ð°Ñ¦Ò
Handbook ¤¤ªº¦C¦L³¡¥÷ ¡C
¦³¨Ç¦Lªí¾÷»Ýn¥D¾÷¤ä´©ªºÅX°Êµ{¦¡ (host-based driver) ¤~¯à
°õ¦æ¥ô¦ó¦C¦L¥\¯à¡CFreeBSD ¥»¨¨Ã¤£¤ä´©³o¨Ç©Ò¿×ªº
WinPrinters
¡C ¦pªG§Aªº¦Lªí¾÷µLªk¦b DOS ©Î
Windows NT 4.0 ¤U°õ¦æ¡A¨º¥¦¤j·§´N¬O¤@¥x WinPrinter¡C§A°ß¤@¯à¨Ï¥Î
³o¼Ëªº¦Lªí¾÷ªº§Æ±æ¡A´N¬O¸Õ¸Õ
print/pnm2ppa ¤ä¤£¤ä´©¥¦¤F¡C
§Ún«ç»ò¼Ë×¥¿§Úªº¨t²Î©Ò¨Ï¥ÎªºÁä½L¹ï¬M (keyboard mapping)¡H
½Ð°Ñ¦Ò Handbook ¤¤ªº using localization
³¹¸`¡A¤×¨ä¬O console
setup ³¹¸`¡C
¬°¤°»ò§Ú¦b¨t²Î±Ò°Ê®É¡A±o¨ì unknown: <PNP0303>
can't assign resources ªº°T®§¡H
¥H¤U¬O±q freebsd-current ³q«H½×¾Âªº¤@½g¤å³¹¤¤¸`¿ý¥X¨Óªº¡C
&a.wollman;, 2001 ¦~¥|¤ë 24 ¤é
µLªk«ü¬£¸ê·½ (can't assign resources)
°T®§ªí¥Ü
¨º¨Ç¸Ë¸m¬O¶Ç²Îªº ISA ¸Ë¸m¡A¦Ó®Ö¤ß¤¤¤w¸g½s¤J¤£»{±o PNP ªºÅX°Êµ{
¦¡¡C³o¨Ç¸Ë¸m¥]¬AÁä½L±±¨î¾¹¡A¥iµ{¦¡¤Æ§ÃÂ_±±¨î´¹¤ù¡AÁÙ¦³´XӼзÇ
³]³Æ¡C¸ê·½µLªk«ü¬£µ¹³o¨Ç¸Ë¸m¡A¬O¦]¬°¦¤w¦³ÅX°Êµ{¦¡¨Ï¥Î¨º¨Ç¦ì§}
¤F¡C
¬°¤°»ò§ÚµLªkÅý user quotas ¥¿±`¤u§@¡H
¤£n¦b / ¥´¶} quotas¡A
§â quotas ÀÉ©ñ¦b¥¦¥²¶·±j¢¸m¤JªºÀɮרt²Î¤º¡AÁ|¨Ò¡G
Àɮרt²Î
Quota ÀÉ
/usr
/usr/admin/quotas
/home
/home/admin/quotas
…
…
FreeBSD ¤ä´© System V IPC ®æ¦¡«ü¥O¶°¡H
¬Oªº¡AFreeBSD ¤ä´© System V-style IPC¡C³o¥]¬A¦@¨É°O¾ÐÅé¡A
°T®§¸ò«H¸¹¡C§A»Ýn¦b§Aªº®Ö¤ß³]©wÀɤº¥[¤J¤U¦C´X¦æ¥H±Ò°Ê¥¦Ì¡C
options SYSVSHM # enable shared memory
options SYSVSEM # enable for semaphores
options SYSVMSG # enable for messaging
¦b FreeBSD 3.2 ¥H¤Î¤§«áªºª©¥»¡A³o¨Ç¿ï¶µ¤w¸g¬O
GENERIC ®Ö¤ßªº¤@³¡¥÷¡A¤]´N¬O»¡¥¦Ì¤w
¸g½s¶i¤F§Aªº¨t²Î¤¤¡C
«·s½sĶ¨Ã¦w¸Ë¡C
§Ú¸Ó¦p¦óÅý sendmail ³z¹L UUCP ¨Ó»¼°e¶l¥ó¡H
¸òÀH FreeBSD ®M¸Ë¦Ó¨Óªº sendmail ³]©w¬O¾A¦X¨º¨Çª½±µ³s¤Wºô»Úºô¸ô
ªº¯¸¥x¡C·Q³z¹L UUCP ¥æ´«¶l¥óªº¯¸¥x¥²¶·¥t¥~¦w¸Ë sendmail ªº³]©wÀɮסC
¤â°Êקï /etc/sendmail.cf ¬Oµ´¹ï¥²nªº¡C
²Ä 8 ª©ªº sendmail ´£¨Ñ¤@Ó¥þ·sªº¤J¤f¥H³z¹L¤@¨Ç¹³ &man.m4.1;
ªº³B²z´N¯à²£¥Í³]©wÀÉ¡A³o¨Æ¹ê¤W¬O¤@Ó°ª¼h·§©Àµ¥¯Åªº§Þ¥©©Ê³]©w¡C
§AÀ³¸Ó¥i¥H¦b /usr/src/usr.sbin/sendmail/cf
¥H¤U¸Ì¨Ï¥Î¥¦¡G
°²¦p§A¤£¬O¥Î full sources ¤è¦¡¦w¸Ë¨t²Î¡A¨º»ò sendmail
³]©w¶µ¥Ø¥i¯à¤w¸g¤À´²¦¨¦n´XÓ¨Ó·½¤À¥¬Àɦbµ¥µÛ§A¡A°²³]§A¤w¸g
mount ¥úºÐ¾÷¡A°µ¥H¤U°Ê§@¡G
&prompt.root; cd /cdrom/src
&prompt.root; cat scontrib.?? | tar xzf - -C /usr/src contrib/sendmail
§OÅå·W¡A³o¥u¦³¼Æ¤Q¸UӦ줸²Õªº¤j¤p¡C¦b cf
¥Ø¿ý¸Ìªº README ¥i¥H´£¨Ñ¤@Ó m4 ³]©wªkªº°ò
¥»¤¶²Ð¡C
¥H UUCP »¼°e¨Ó»¡¡A«Øij§A³Ì¦n¨Ï¥Î mailertable
¯SÂI¡C«Øºc¤@Ó¸ê®Æ®wÅý sendmail ¥i¥H¨Ï¥Î¥¦¦Û¤vªº¸ô®|¨Mµ¦¡C
º¥ý¡A§A¥²¶·«Ø¥ß¦Û¤vªº .mc ÀÉ¡C
/usr/src/usr.sbin/sendmail/cf/cf ¥Ø¿ý¬O³o¨Ç
Àɮתº®a¡C¬d¬Ý¤@¤U¡A¤w¸g¦³¦n´XÓ½d¨ÒÀÉ¡A°²³]§A¤w¸g©R¦W¦Û¤vªºÀÉ¥s
foo.mc ¡A§An°µªº¥u¬O§â¥¦Âà´«¦¨¤@Ó¦³®Äªº
sendmail.cf ¡G
&prompt.root; cd /usr/src/usr.sbin/sendmail/cf/cf
&prompt.root; make foo.cf
&prompt.root; cp foo.cf /etc/mail/sendmail.cf
¤@Ө嫬ªº .mc Àɬݰ_¨Ó¥i¯à¹³³o¼Ë¡G
VERSIONID(`Your version number ')
OSTYPE(bsd4.4)
FEATURE(accept_unresolvable_domains)
FEATURE(nocanonify)
FEATURE(mailertable, `hash -o /etc/mail/mailertable')
define(`UUCP_RELAY', your.uucp.relay )
define(`UUCP_MAX_SIZE', 200000)
define(`confDONT_PROBE_INTERFACES')
MAILER(local)
MAILER(smtp)
MAILER(uucp)
Cw your.alias.host.name
Cw youruucpnodename.UUCP
accept_unresolvable_domains ¡A
nocanonify ¡A ©M
confDONT_PROBE_INTERFACES ¯S©Ê±NÁקK¥ô¦ó¦b
»¼°e¶l¥ó®É·|¥Î¨ì DNS ªº¾÷·|¡CUUCP_RELAY
¶µ¥Øªº¥X²{²z¥Ñ«Ü©_©Ç¡A´N¤£n°Ý¬°¦ó¤F¡C²³æªº©ñ¤J¤@Óºô»Úºô¸ô
¤W¥i¥H³B²z .UUCP µêÀÀºô°ì¦ì§}ªº¥D¾÷¦WºÙ¡F³q±`¡A§A¥u»Ýn¦b³o
¸Ì¶ñ¤J§A ISP ªº«H¥ó¦^ÂгB (mail replay)¡C
§A¤w¸g°µ¨ì³o¸Ì¤F¡A§AÁÙ»Ýn³oÓ¥s
/etc/mail/mailertable ¡C¦pªG§A¥u¦³¤@Ó¥Î
¨Ó¶Ç»¼©Ò¦³¶l¥óªº¹ï¥~³q¹Dªº¸Ü¡A¥H¤UªºÀÉ®×´N¨¬°÷¤F¡G
#
# makemap hash /etc/mail/mailertable.db < /etc/mail/mailertable
uucp-dom:your.uucp.relay
¥t¤@Ó§ó½ÆÂøªº¨Ò¤l¬Ý°_¨Ó¹³³o¼Ë¡G
#
# makemap hash /etc/mail/mailertable.db < /etc/mail/mailertable
#
horus.interface-business.de uucp-dom:horus
interface-business.de uucp-dom:if-bus
interface-business.de uucp-dom:if-bus
heep.sax.de smtp8:%1
horus.UUCP uucp-dom:horus
if-bus.UUCP uucp-dom:if-bus
uucp-dom:
¦p§A©Ò¨£¡A³o¬O¬YÓ¯u¹êÀɮ׸̪º¤@³¡¥÷¡Cº¤T¦æ³B²zºô°ì©w§}«H¥ó
¤£À³¸Ó³Q°e¥X¨ì¤º©w¸ô®|¡A¦Ó¥Ñ¬Y¨Ç UUCP ¾F©~(UUCP neighbor)¨ú¥N
ªº¯S®í±¡§Î¡A³o¬O¬°¤F ÁYµu
»¼°eªº¸ô®|¡C¤U¤@¦æ³B²z¨ì
¥»¦a¤A¤Óºô¸ôºô°ìªº«H¥óÅý¥¦¥i¥H¨Ï¥Î SMTP ¨Ó»¼°e¡C³Ì«á¡AUUCP ¾F©~´£¨ì
.UUCP µêÀÀºô°ìªº°O¸ü¡A¤¹³\¤@Ó uucp-neighbor
!recipient ±À½
¤º©w³W«h¡C³Ì«á¤@¦æ«h¥H¤@Ó³æ¿Wªº¥yÂI°µµ²§ô¡A¥H UUCP »¼°e¨ì´£¨Ñ·í
§A¥þ¥@¬É©Ê¶l¥ó¹hªùªºUUCP ¾F©~¡C©Ò¦³¦b uucp-dom:
ÃöÁä¦r¸Ìªº¸`ÂI¦WºÙ¥²¶·³£¬O¦³®Äªº UUCP ¾F©~¡A§A¥i¥H¥Î
uuname ©R¥O¥h½T»{¡C
´£¿ô§A³oÓÀɮצb¨Ï¥Î«e¥²¶·³QÂà´«¦¨ DBM ¸ê®Æ®wÀɮסA³Ì¦n¦b
mailertable ³Ì¤W±¥Îµù¸Ñ¼g¥X©R¥O¦C¨Ó§¹¦¨³oÓ¤u§@¡C·í§A¨C¦¸§ó´«§A
ªº mailertable «á§AÁ`¬O»Ýn°õ¦æ³oÓ©R¥O¡C
³Ì«á´£¥Ü¡G¦pªG§A¤£½T©w¬Y¨Ç¯S©wªº«H¥ó¸ô®|¥i¥Î¡A°O±o§â
-bt ¿ï¶µ¥[¨ì sendmail¡C³o·|±N sendmail ±Ò°Ê¦b
address test mode ¡F¥un«ö¤U
0 ¡A±µµÛ¿é¤J§A§Æ±æ´ú¸Õªº«H¥ó¸ô®|¦ì§}¡C
³Ì«á¤@¦æ§i¶D§A¨Ï¥Î¤º³¡ªº«H¥ó¥N²zµ{¦¡¡A¥N²zµ{¦¡ªº·|³qª¾¥Øªº¥D¾÷¡A
¥H¤Î(¥i¯àÂà´«ªº)¦ì§}¡CnÂ÷¶}¦¹¼Ò¦¡½Ð«ö Control-D¡C
&prompt.user; sendmail -bt
ADDRESS TEST MODE (ruleset 3 NOT automatically invoked)
Enter <ruleset> <address>
> 3,0 foo@example.com
canonify input: foo @ example . com
..
parse returns: $# uucp-dom $@ your.uucp.relay $: foo < @ example . com . >
> ^D
·í§Ú¥Î¼·±µ³s¤Wºô¸ô®É¸Ó«ç»ò³]©w«H¥ó»¼°e¡H
¦pªG§A¤w¸g¦³¤@Ó©T©wªº IP ¼Æ¦r¡A§A¤£»Ýn½Õ¾ã¥ô¦ó¤º©wÈ¡C³]¦n
§An«ü©wªººô¸ô¦WºÙ¡A¨ä¥Lªº sendmail ³£·|À°§A°µ§¹¡C
¦pªG§A®³¨ìªº¬O°ÊºA°t¸mªº IP ¼Æ¦r¦Ó¨Ï¥Î¼·±µ ppp ³s±µ¨ìºô»Úºô
¸ô¡A§A¥i¯à¤w¸g¦b§Aªº ISP «H¥ó¥D¾÷¤W¦³¤@Ó«H½c¡C°²³]§Aªº ISP ºô°ì
¬O example.net ¡A§Aªº¨Ï¥ÎªÌ¦W
ºÙ¬O user ¡C¥ç°²³]§AºÙ¦Û¤vªº¥D¾÷¦WºÙ¬O
bsd.home ¦Ó§Aªº ISP §i¶D§A¥i¥H¨Ï¥Î
relay.example.net ·í§@«H¥ó¦^ÂгB¡C
¬°¤F±q§Aªº«H½c±µ¦¬«H¥ó¡A§A±N»Ýn¦w¸Ë¨ú«Hµ{¦¡¥H«K±q«H½c¨ú¦^«H¥ó¡C
Fetchmail ¬O¤@Ó¤£¿ùªº¿ï¾Ü¡A¦]¬°¥¦¤ä
´©³\¦h¤£¦Pªº³q°T¨ó©w¡A³q±`§Aªº ISP ·|´£¨Ñ POP3¡C¦pªG§A¿ï¾Ü¨Ï¥Î
user-ppp¡A§A¥i¥H¦b³s½u¨ìºô¸ô¦¨¥\«á¦Û°Ê§ì¨ú§Aªº«H¥ó¡A¥un¦b
/etc/ppp/ppp.linkup ¸Ì±³]©w¥H¤U³o¶µ¡G
MYADDR:
!bg su user -c fetchmail
°²¨Ï§A¥¿¨Ï¥Î sendmail (¦p¤U©Ò¥Ü)
¶Ç°e«H¥ó¨ì«D¥»¦a±b¸¹¡A¸m¤J¥H¤U©R¥O¡G
!bg su user -c "sendmail -q"
¦b¤W±¨º¶µ©R¥O¤§«á¡C³o·|±j¢ sendmail
¦b³s±µ¤Wºô¸ô«á°¨¤W¶}©l³B²z mailqueue¡C
§Ú°²³]§A¦b bsd.home ¾÷¾¹¤W¦³¤@Ó
user ªº±b¸¹¡C¦b bsd.home ¾÷¾¹¤W user
ªº®a¥Ø¿ý¸Ì«Ø¥ß¤@Ó .fetchmailrc ªºÀɮסG
poll example.net protocol pop3 fetchall pass MySecret
µL¶·Âب¥¡A³oÓÀÉ°£¤F user ¥~¤£À³¸Ó³Q¥ô
¦ó¤HŪ¨ú¡A¦]¬°¥¦¥]§t MySecret ³oÓ±K½X¡C
¬°¤F¦b±H«H®É¦³¥¿½Tªº©ïÀY from: ¡A§A¥²¶·§i¶D
sendmail ¨Ï¥Î
user@example.net ¦Ó«D
user@bsd.home ¡C§A¥i¯à·|§Æ±æ§i¶D
sendmail ±q
relay.example.net °e¥X©Ò¦³«H¥ó¡A
¥[§Ö«H¥ó¶Ç°e¡C
¥H¤Uªº .mc ÀÉÀ³¯àº¡¨¬§Aªºn¨D¡G
VERSIONID(`bsd.home.mc version 1.0')
OSTYPE(bsd4.4)dnl
FEATURE(nouucp)dnl
MAILER(local)dnl
MAILER(smtp)dnl
Cwlocalhost
Cwbsd.home
MASQUERADE_AS(`example.net')dnl
FEATURE(allmasquerade)dnl
FEATURE(masquerade_envelope)dnl
FEATURE(nocanonify)dnl
FEATURE(nodns)dnl
define(`SMART_HOST', `relay.example.net')
Dmbsd.home
define(`confDOMAIN_NAME',`bsd.home')dnl
define(`confDELIVERY_MODE',`deferred')dnl
¦p¦óÂà´«³oÓ .mc Àɮרì
sendmail.cf Àɪº¸Ô²Ó²Ó¸`¡A½Ð°Ñ¦Ò¤W¤@¸`¡C
¥t¥~¡A¦b§ó·s sendmail.cf ¥H«á¤£n§Ñ°O«·s±Ò°Ê
sendmail ¡C
°£¤F Sendmail ¥~¡AÁÙ¦³þ¨Ç¶l¥ó¦øªA¾¹¥i¥H¨Ï¥Î©O¡H
Sendmail
¬O FreeBSD ¹w³]¨Ï¥Îªº¶l¥ó¦øªA¾¹¡A¦ý¬O§AÁÙ¬O¥i¥H«Ü®e©ö¦a¥H¨ä¥¦
¶l¥ó¦øªA¾¹ (¨Ò¦p¡A±q port ¦w¸Ëªº¶l¥ó¦øªA¾¹) ¨ú¥N¤§¡C
port ¸Ì¦³«Ü¦h¥i¨Ñ¿ï¾Üªº¶l¥ó¦øªA¾¹¡A¹³
mail/exim ¡B
mail/postfix ¡B
mail/qmail ¡B
mail/zmailer 杭A
´N¬O´XӫܨüÅwªïªº¿ï¾Ü¡C
¦h¼Ë¿ï¾Ü¬O¦n¨Æ¡A¦Ó¥B¤j®a¦³³\¦h¶l¥ó¦øªA¾¹¥i¥H¨Ï¥Î¤]³Q»{¬°¬O
¦n¨Æ¡F©Ò¥H½ÐÁקK¦b³q«H½×¾Â¸Ì°Ý¹³ Sendmail ¦³¤ñ Qmail
¦n¶Ü¡H
³o¼Ëªº°ÝÃD¡C¦pªG§A¯uªº«Ü·Q°Ýªº¸Ü¡A½Ð¥ý¨ì³q«H½×¾Â
archive ¸Ì§ä¤@¤U¡C¨C¤@Ó¶l¥ó¦øªA¾¹ªºÀuÂI»P¯ÊÂI¡A¥H«e¤j·§´N¤w¸g
°Q½×¦n´X¦¸¤F¡C
§Ú§Ñ¤F root ±K½X¤F¡I«ç»ò¿ì¡H
¤£nÅå·W¡I¥un«·s±Ò°Ê¨t²Î¡A¦b¬Ý¨ì Boot: ®É¿é¤J
boot -s §Y¥i¶i¤J³æ¨Ï¥ÎªÌ¼Ò¦¡
(¦b 3.2-RELEASE ¤§«eªºª©¥»½Ð§ï¥Î -s )¡C
¦b°Ýn¨Ï¥ÎþÓ shell ®É¡A«ö¤U ENTER¡C§A·|¬Ý¨ì¤@Ó &prompt.root;
ªº´£¥Ü¸¹¡A¿é¤J mount -u / ¥H«·s±¾¤W(mount)
§Aªº®ÚÀɮרt²Î¥i¨ÑŪ/¼g¡C°õ¦æ passwd root
¥H§ó´« root ±K½X¡AµM«á°õ¦æ &man.exit.1;
Ä~Äò±Ò°Êµ{§Ç¡C
§Ú¸Ó«ç»òÅý Control-Alt-Delete ¤£·|«·s±Ò°Ê¨t²Î¡H
¦pªG§A¬O¨Ï¥Î FreeBSD 2.2.7-RELEASE ©Î¤§«áª©¥»ªº
syscons(¨t²Î¤º©wªº¥D±±¥xÅX°Êµ{¦¡)¡A§â¤U¦C³o¦æ©ñ¨ì®Ö¤ß³]©wÀɤº¡A
µM«á«°µ¤@Ó·sªº®Ö¤ß¡G
options SC_DISABLE_REBOOT
Y¬O¨Ï¥Î FreeBSD 2.2.5-RELEASE ©Î¤§«áª©¥»ªº PCVT ¥D±±¥xÅX°Ê
µ{¦¡¡A«h¥H¤U¦C¿ï¶µ¥N´À¡G
options PCVT_CTRL_ALT_DEL
¨ä¥L§ó¦´Áªº FreeBSD ª©¥»¡A½Ðקï§A¥¿¦b¨Ï¥Îªº¥D±±¥xÁä½L¹ïÀ³¡A
¨Ã±N©Ò¦³ boot ÃöÁä¦r¥H nop
¨ú¥N¡C¤º©wªºÁä½L¹ïÀ³¬O¦b
/usr/share/syscons/keymaps/us.iso.kbd ¡C
§A¥i¯à»Ýn©ú¥Õªº§h©J /etc/rc.conf ¥hŪ¨ú
³oÓÁä½L¹ïÀ³¥H½T«O§ó°Ê¥Í®Ä¡C·íµM¦pªG§A¥¿¦b¥Î¾A¦X§A°êÄyªºÁä½L¹ïÀ³¡A
§AÀ³¸Ó½s¿è¨º¤@Ó¡C
§Ú¸Ó«ç»ò§â DOS ¤å¦rÀɮ׫·s®æ¦¡¤Æ¦¨ UNIX ªº¡H
¥un¨Ï¥Î³oÓ perl ©R¥O¡G
&prompt.user; perl -i.bak -npe 's/\r\n/\n/g' file ...
file ´N¬On³B²zªºÀɮסC³oÓקï¬O¦b¤º³¡§¹¦¨¡Aì©lªºÀÉ®×·|Àx¦s¦¨
°ÆÀɦW¬° .bak ªºÀɮסC
©ÎªÌ§A¥i¥H¨Ï¥Î &man.tr.1; ³oÓ©R¥O¡G
&prompt.user; tr -d '\r' < dos-text-file > unix-file
dos-text-file ¬O¥]§t DOS ¤å¦rªº
ÀɮסA¦Ó unix-text-file «h¬O¥]§tÂà´«
ªº¿é¥Xµ²ªG¡C³o¤ñ¨Ï¥Î perl ÁÙn§Ö¤W¤@ÂIÂI¡C
§Ú¸Ó«ç»ò¥Î¦WºÙ¬å±¼ process¡H
¨Ï¥Î &man.killall.1; ¡C
¬°¦ó¦b su ¤@ª½»¡§Ú¤£¦b root ªº ACL ¸Ì¡H
³oÓ¿ù»~¬O¦]¬° Kerberos ¤À´²»{ÃÒ¨t²Î¡C³oÓ°ÝÃD¨Ã¤£¬O«ÜÄY«
¦ý¬O¥O¤H¹½·Ð¡C§A¥i¥H¥Î -K ¿ï¶µ¥h°õ¦æ su¡A©Î¬O¹³¤UÓ°ÝÃD©Ò´yzªº
²¾°£ Kerberos¡C
§Ú¸Ó«ç»ò²¾°£ Kerberos¡H
n±q¨t²Î¸Ì²¾°£ Kerberos¡A«¸Ë§A¥¿¦b°õ¦æªº release ª©¥»ªº
bin distribution¡C¦pªG§A¦³ CDROM¡A§A¥i¥H mount cd(°²³]¦b /cdrom)
¨Ã°õ¦æ¡G
&prompt.root; cd /cdrom/bin
&prompt.root; ./install.sh
©ÎªÌ§A¤]¥i¥H±N /etc/make.conf ¸Ìªº
"MAKE_KERBEROS" ¿ï¶µ¥þ³£®³±¼¡AµM«á¦A build world.
§Ú¸Ó«ç»ò¼W¥[¨t²ÎªºµêÀÀ²×ºÝ¾÷¡H
¦pªG§A¦³³\¦h telnet¡Assh¡AX ©Î¬O screen ¨Ï¥ÎªÌ¡A§A©Î³\·|¥Î§¹
µêÀÀ²×ºÝ¾÷¡A³o¯à±Ð§A«ç»ò¥[§ó¦h¡G
«Ø¥ß¨Ã¦w¸Ë¤@Ó·sªº®Ö¤ßµ{¦¡¨Ã¥B§â³o¤@¦æ
pseudo-device pty 256
¥[¤J¨ì³]©wÀɸ̡C
°õ¦æ³oÓ©R¥O¡G
&prompt.root; cd /dev
&prompt.root; sh MAKEDEV pty{1,2,3,4,5,6,7}
·|³y¥X 256 ÓµêÀÀ²×ºÝ¾÷ªº¸Ë¸m¸`ÂI¡C
½s¿è /etc/ttys ¨Ã¥[¤J²Å¦X 256
Ӳ׺ݾ÷ªº¦æ¼Æ¡C¥¦ÌÀ³¸Ó²Å¦X¤w¸g¦s¦b³æ¶µªº®æ¦¡¡AÁ|¨Ò¨Ó»¡¡A
¥¦Ì¬Ý°_¨Ó¹³¡G
ttyqc none network
¦r¥À³]pªº¶¶§Ç¬O
tty[pqrsPQRS][0-9a-v] ¡A¨Ï¥Î¥¿³Wªí¥Ü¦¡¡C
¥Î·sªº®Ö¤ßµ{¦¡«·s±Ò°Ê¹q¸£´N¥i¥H¤F¡C
/dev/snd0 ³oӸ˸m°µ¤£¥X¨Ó¡I
¨Ã¨S snd ³oӸ˸mªº¦s¦b¡C³oÓ¦W¦r
¬O¥Î¨Ó·í§@¦UÓ²Õ¦¨ FreeBSD ÁnµÅX°Êµ{¦¡²Õ¡A½Ñ¦p
mixer ¡A
sequencer ¡A¥H¤Î
dsp ªºÂ²ºÙ¡C
¥i¥H¥Î¥H¤Uªº©R¥O§@¥X³o¨Ç¸Ë¸m¡G
&prompt.root; cd /dev
&prompt.root; sh MAKEDEV snd0
¥i¥H¤£¥Î¶}¾÷¡A«·sŪ¨ú /etc/rc.conf ¡B
¦A¦¸±Ò°Ê /etc/rc ¶Ü?
¥ý¶i¤J³æ¤H¨Ï¥ÎªÌ¼Ò¦¡¡AµM«á¦A¦^¨ì¦h¨Ï¥ÎªÌ¼Ò¦¡¡C
¦b¥D±±¥x°õ¦æ¡G
&prompt.root; shutdown now
(Note: without -r or -h)
&prompt.root; return
&prompt.root; exit
¤°»ò¬O sandbox¡H
Sandbox
¬O¨t²Î¦w¥þ¥Îªº³N»y¡A¦³¨âÓ·N¸q¡G
©ñ¦b¬Y¨ÇµêÀÀ¨¾Å@Àð¸Ìªº°õ¦æµ{§Ç¡A³o¨Ç¨¾Å@Àð¬O¥Î¨Óªý¤î
¬Y¨Ç¤H«I¤J³o¹Dµ{§Ç¡A¶i¦Ó¥X¤J©ó§ó¤jªº¨t²Î¤¤¡C
³o¹Dµ{§Ç¥i¥H§¹¥þ¦b¨¾Å@Àð¸Ì °Ê§@
¡C¤]´N
¬O»¡¡A¥¦©Ò°õ¦æªº¥ô¦óµ{¦¡¤£¥i¯à·|º¯³z¨ìÀ𪺥~±¡C©Ò¥H¦pªG
±z¹ï¥¦¦³¦w¥þ¤WªºÅU¼{¡A¨Ã¤£»Ýn¯S§O¥hºÊÅ¥¥¦ªº¤@Á|¤@°Ê¡A¤Ï
¥¿¥¦¥u¯à¦bÀ𤺬¡°Ê¡C
Á|¨Ò¨Ó»¡¡A¥i¥H¥Î userid ¨Ó°µ³o¹D¨¾Å@Àð¡A³o¥¿¬O security
©M named »¡©ú¤å¥ó¤¤ªº©w¸q¡C
²{¦b´N¥Î ntalk ³oÓªA°È§@»¡©ú¡]¨£
/etc/inetd.conf¡^¡C³oÓªA°È¥H«eªº userid ¬O
root ¡A²{¦b°õ¦æ®É«h¬O¥Î
tty ¡Ctty
³oӨϥΪ̴N¬O¤@Ó sandbox¡A¦pªG¦³¤H¯à°÷¶¶§Q¥Î ntalk
«I¤J¨t²Î¡A²{¦b¥L´Nºâ¶i±o¨Ó¤]¥u¯à¥Î³oÓ userid¡C
©ñ¦b¬YÓ¼ÒÀÀ¾÷¾¹¸Ìªºµ{¦¡¡A³o¤ñ¤Wz¨Ó±o§óÄY±K¡C°ò¥»¤W
³oªí¥Ü¯à«I¤J¸Óµ{¦¡ªº¤H¬Û«H¥L¯à¦A¶i¤J©ÒÄݪº¾÷¾¹¡A¦ý¨Æ¹ê¤W
¥u·|¶i¤J¼ÒÀÀ¥X¨Óªº¾÷¾¹¡AµLªk¶i¤@¨Bקï¥ô¦ó¯u¹êªº¸ê®Æ¡C
¹F¨ì³oӥتº³Ì±`¥Îªº¤èªk¡A´N¬O¦b¬YÓ¤l¥Ø¿ý¤U°µ¥X¼ÒÀÀªº
Àô¹Ò¡AµM«á¥Î chroot °õ¦æ¸Óµ{¦¡¡A³o¼Ë¸Óµ{¦¡ªº®Ú¥Ø¿ý«K¬O³oÓ
¤l¥Ø¿ý¡A¦Ó«D¨t²Î¯u¥¿ªº®Ú¥Ø¿ý¡C
¥t¤@Ó±`¨£§@ªk¬O±N¬YÓÀɮרt²Î mount ¦¨°ßŪ¡A¦ý¦b¥¦
¤W±¥t¥~»s³y¥Xµ{¦¡¥H¬°¥i¥H¼g¤JªºÀɮרt²Î¡C³oÓµ{¦¡·|¬Û«H
¥¦¥i¥H¹ï¨ä¥LÀÉ®×Ū¼g¡A¦ý¥u¦³¥¦¬Ý¤£¨ì³oÓ°ßŪ®ÄÀ³ - ¨t²Î
°õ¦æªº¤@¯ëµ{¦¡³£¬Ý±o¨ì¡C
§Ú̸չϱN³oÃþ sandbox ºÉ¶q³z©ú¤Æ¡AÅý¨Ï¥ÎªÌ©Î«I¤JªÌ
µLªk¬Ý¨ì¥L¬O§_¦b¬YÓ sandbox ¸Ì±¡C
UNIX ¹ê§@¨âºØ sandbox¡A¤@Ó¦bµ{¦¡¼h±¡A¥t¤@Ó«h¬O¥Ñ userid
¨Ó¹F¦¨¡C
¨CÓ UNIX °õ¦æµ{§Ç·|¥Î¨¾¤õÀð±N¥¦©M©Ò¦³¨ä¥Lµ{§Ç¹j¶}¡A¬YÓµ{§Ç
¤£¥i¥HÀH·Nקï¨ä¥Lµ{§Ç¦ì§}ªº¸ê®Æ¡C³o©M Windows ¤¤¡Aµ{¦¡¥i¥H»´©ö
קï¨ä¥L¦ì§}¸ê®Æ¡Aµ²ªG¾ÉP·í¾÷ªº±¡§Î¤j¤£¬Û¦P¡C
¨CÓ UNIX µ{§Ç³£ÄÝ©ó¬YÓ¯S©wªº userid¡C¦pªG¸Ó userid ¤£¬O
root ¡A´N·|±N¥¦©M¨ä¥L¨Ï¥ÎªÌªºµ{§Ç¹j¶}¡C
Userid ¦P®É¤]¥Î©óµwºÐ¸ê®Æªº¦s¨úÅv¤W¡C
¤°»ò¬O securelevel?
securelevel ¬O®Ö¤ß¤¤©Ò¹ê§@ªº¤@Ó¦w¥þ¾÷¨î¡C°ò¥»¤W·í
securelevel ¬O¥¿È®É¡A®Ö¤ß·|¨î¬Y¨Ç¤u§@¡F§Y¨Ï¬O superuser
(¤]´N¬O root ) ¤]µLªk§¹¦¨¨º¨Ç¤u§@¡C¦b¼¶¼g
¥»¤å®É¡Asecurelevel ¾÷¨î¦b¤@¯ëªº¨î¥~¡AÁÙ¯à°÷¨î¥H¤Uªº¥\¯à¡G
²M°£¬Y¨Ç¯S©wªºÀɮ׺X¼Ð¡A¨Ò¦p schg
(¨t²Î°ßŪ¼ÐºX, the system immutable flag)
¸g¥Ñ /dev/mem »P
/dev/kmem ¡A ±N¸ê®Æ¼g¤J¦Ü®Ö¤ß°O¾ÐÅ餤
¸ü¤J®Ö¤ß¼Ò²Õ
§ó°Ê &man.ipfirewall.4; ³W«h¡C
·QnÀˬd¦b¬YÓ¹B§@¤¤ªº¨t²Îªº securelevel ª¬ºA¡A¥un°õ¦æ¥H¤U
©R¥O§Y¥i¡G
&prompt.root; sysctl kern.securelevel
¿é¥Xªºµ²ªG·|¥]§t¤@Ó &man.sysctl.8; ÅܼƦWºÙ (¦b³oÓ¨Ò¤l¤¤¡A
¥¦¬O kern.securelevel ) ¥H¤Î¤@ӼƦr¡C«áªÌ§Y¬O
¥Ø«eªº securelevel È¡C¦pªG¥¦¬O¤@Ó¥¿È (¤]´N¬O¤j©ó 0)¡Aªí¥Ü¦Ü¤Ö
¦³¤@¨Ç securelevel ªº«OÅ@¾÷¨î¤w¸g¶}±Ò¤F¡C
§A¨S¦³¿ìªk°§C¤@Ó¹B§@¤¤ªº¨t²Îªº securelevel¡F¦pªG¥i¥Hªº¸Ü¡A
´N¥¢¥h¤F³oÓ¾÷¨îªº·N¸q¤F¡C¦pªG§An§@¤@¨Ç»Ýn securelevel ¬°
«D¥¿È¤~¥i¥Hªº°Ê§@ªº¸Ü (¨Ò¦p installworld
©Î§ó°Ê¤é´Á)¡A§A»Ýnקï /etc/rc.conf ¤ºªº
securelevel ³]©w (§ä§ä kern_securelevel ©M
kern_securelevel_enable ÅܼÆ)¡AµM«á«·s¶}¾÷¡C
·Qnª¾¹D§ó¦h¦³Ãö©ó securelevel »P¦UÓ¤£¦Pµ¥¯Å¼vÅTªº²Ó¸`¡A
½Ð°Ñ¦Ò &man.init.8; »¡©ú¤å¥ó¡C
securelevel ¥i¤£¬O¸UÆF¤¦¡F¥¦¦³³\¦h¤wª¾ªº¯Ê³´¡A©¹©¹³y¦¨
¤@ºØ¦w¥þªº°²¶H¡C
¥¦¤@ӳ̤jªº°ÝÃD¡A´N¬OnÅý³oÓ¥\¯à§¹¥þ¦³®Äªº¸Ü¡A¦b
securelevel µo´§§@¥Î«eªº±Ò°Ê¹Lµ{¤¤¡A©Ò¦³¨Ï¥Î¨ìªºÀɮ׳£
¥²¶·³Q«OÅ@°_¨Ó¡C¦pªG¤@Ó§ðÀ»ªÌ¦b securelevel ¦³®Ä«e (¥Ñ©ó
¦³¨Ç¨t²Î¦b±Ò°Ê¤¤©Ò§@ªº¨Æ±¡¡AµLªk¦b¸û°ªªº securelevel ¤¤
¥¿±`¹B§@¡A©Ò¥H³o·|¦b±Ò°Ê¹Lµ{¤¤«á´Á¤~·|¹B§@)¡A¯àÅý¥L̪ºµ{¦¡
³Q°õ¦æªº¸Ü¡Asecurelevel ªº«OÅ@´N§¹¥þµL®Ä¤F¡C«OÅ@±Ò°Êµ{§Ç
¤¤©Ò¦³ªºÀɮצb§Þ³N¤W¬O¥i¦æªº¡A¦ý¬O¦pªG¯uªº³o¼Ë§@ªº¸Ü¡A¨t²Î
ºûÅ@±N·|Åܦ¨¤@³õ¹ÚÆL¡C§Y¨Ï¥u¬Oקï¤@Ó³]©wÀÉ¡A¤]¥²¶·±N¾ãÓ
¨t²ÎÃö³¬¡A¦Ü¤Ö¤]±o¨ì³æ¤H¼Ò¦¡¡C
°£¤F³oÂI¡AÁÙ¦³³\¦h¨ä¥¦ªºªF¦è³£¦b³q«H½×¾Â¤W°Q½×¡A¤×¨ä¬O
freebsd-security¡C½Ð¨ì ³o¸Ì ·j´M¥H«eªº
°Q½×¡C¦³¨Ç¤H§Æ±æ securelevel ¯à°÷¾¨§Ö®ø¥¢¡A¥Ñ¥t¤@Ó§óÀu¨qªº
¾÷¨î¨ú¥N¡A¤£¹L¾÷·|¦³ÂI´ù¯í¡C
·ÀI¦Û¦æ©Ó¾á¡C
§Ú·Qn§â§Úªº¨t²Îª@¯Å¨ì³Ì·sªº -STABLE¡A¦ý¬O±o¨ìªº¬O -RC ©Î
-PRERELEASE¡I«ç»ò¤F¡H
²³æ¦a»¡¡G¨º¥u¬O¦W¦r¦Ó¤w¡CRC ªº·N«ä¬O Release Candiate¡A
µo¦æԿ睊¥»
¡A¥¦ªí¥Ü·sª©¥»§Önµo¦æ¤F¡C¦b FreeBSD ¤¤¡A
-PRERELEASE ³q±`¬Oµo¦æ«eªºµ{¦¡½Xáµ²ªº¥N¦Wµü¡C(¦³¨Çµo¦æª©¥»¤¤¡A
-BETA ¼ÐÅÒ¸ò -PRERELEASE ¬O¬Û¦P·N«äªº¡C)
¸Ô²Ó¦a»¡¡GFreeBSD ±q¨âÓ¦a¤è¤À¤ä¥X¥¦ªºµo¦æª©¥»¡C¥Dª©¸¹¡B
ÂI¹s¡Brelease (¨Ò¦p 3.0-RELEASE ¤Î 4.0-RELEASE) ªº¡A¬O±qµo®i¹Lµ{
¶}©l®É¤À¤ä¥X¨Óªº¡A³q±`ºÙ¬° -CURRENT
¡C¦³°Æª©¸¹ªºª©¥» (¨Ò¦p 3.1-RELEASE ©Î 4.2-RELEASE)¡A¬O
¬¡ÅDªº -STABLE ¤À¤ä¤¤ªºµo¦æª©¥»
§Ö·Ó¡C±q 4.3-RELEASE ¶}©l¡A¨C¤@Óµo¦æª©¥»¦³¥¦¦Û¤vªº¤À¤ä¡A¥i¬°
°¾¦n·¥«×«O¦uªºµo®i³t«× (³q±`¥u·|§@¦w¥þ¤è±ªº§ó·s) ªº¤H©Ò¥Î¡C
·Ç³Æn»s§@µo¦æª©¥»®É¡A¨ä©Ò¦bªº¤À¤ä·|¸g¹L¤@©wªºµ{§Ç¡C¦³¤@Ó¬O
µ{¦¡½Xáµ²¡C·íµ{¦¡½Xáµ²¶}©l®É¡A¤À¤ä¦WºÙ·|§ó¦W¡A¥H¤Ï¬M¥¦§Ön¦¨¬°
¤@Óµo¦æª©¥»¤F¡CÁ|Ó¨Ò¤l¡A¦pªGì¨Óªº¤À¤ä¥s 4.5-STABLE¡A¥¦ªº¦W¦r
·|Åܦ¨ 4.6-PRERELEASE ¥Hªí¥Üµ{¦¡½X¤wáµ²¡A¨Ã¥BÃB¥~ªºµo¦æ«e´ú¸Õ
±Nn¶}©l¤F¡C¯äÂΧ󥿤´¥i¦^³ø¡A¥H¦¨¬°µo¦æª©¥»ªº¤@³¡¥÷¡C·íµ{¦¡½X
¦³¤F¥i¦¨¬°µo¦æª©¥»ªºÂú§Î®É¡A¥¦ªº¦W¦r´N·|Åܦ¨ 4.6-RC¡A¥Hªí¥Üµo¦æ
ª©¥»§Ö¦n¤F¡C¶i¤J RC ¶¥¬q«á¡A¥u¦³§ä¨ìªº³Ì¦³¼vÅTªº¯äÂΤ~·|³Q×¥¿¡C
·íµo¦æª©¥» (¥»¨Ò¤¤¬° 4.6-RELEASE) ²£¥Í«á¡Aµo¦æª©¥»·|¦³¦Û¤vªº¤À¤ä¡A
ì¤À¤ä·|³Q§ó¦W¬° 4.6-STABLE¡C
·Qn±oª¾§ó¦h¦³Ãöª©¥»¸¹½X»P¦U CVS ¤À¤äªº¸ê°T¡A½Ð°Ñ¦Ò
Release
Engineering ¤@¤å¡C
§Ú¸ÕµÛn¦w¸Ë¤@Ó·sªº®Ö¤ß¡A¦ý¬OµLªk chflags¡C§Ú¸Ó«ç»ò¸Ñ¨M¡H
²³æ¦a»¡¡G§Aªº securelevel ¥i¯à¤j©ó¹s¡Cª½±µ«·s¶}¾÷¨ì
³æ¤H¼Ò¦¡¡A¦A¦w¸Ë®Ö¤ß¡C
¸Ô²Ó¦a»¡¡GFreeBSD ¦b securelevel ¤j©ó¹s±¡ªp¤U¡A¤£¤¹³\
Åܧó¨t²ÎºX¼Ð (system flags)¡C§A¥i¥H¥Î³oÓ«ü¥OÀˬd§Aªº
securelevel¡G
&prompt.root; sysctl kern.securelevel
§A¨S¦³¿ìªk°§C securelevel¡F§A¥²¶·±Ò°Ê¨t²Î¨ì³æ¤H¼Ò¦¡¥H
¦w¸Ë®Ö¤ß¡A©Î¬Oקï /etc/rc.conf ¤ºªº
securelevel ¦A«·s¶}¾÷¡C½Ð°Ñ¦Ò &man.init.8; »¡©ú¤å¥ó¡A¥H¨ú±o
§ó¦h¦³Ãö securelevel ªº¸ê°T¡AÁÙ¦³ /etc/defaults/rc.conf
©M &man.rc.conf.5; »¡©ú¤å¥ó¡A¥H¨ú±o§ó¦h¦³Ãö rc.conf
ªº¸ê°T¡C
¦b§Úªº¨t²Î¤W¡A§ÚµLªkÅܧó®É¶¡¶W¹L¤@¬í¥H¤Wªº½d³ò¡I
§Ú¸Ó«ç»ò¿ì¡H
²³æ¦aÁ¿¡G§A¨t²Îªº securelevel ¤]³\¤j©ó 1¡Cª½±µ«·s¶}¾÷¦Ü
³æ¤H¼Ò¦¡¡AµM«á¦Aקï®É¶¡¡C
¸Ô²Ó¦a»¡¡G¦b securelevel ¤j©ó 1 ªº±¡ªp¤U¡AFreeBSD ¤£¤¹³\®É¶¡
Åܰʤj©ó¤@¬í¡C§A¥i¥H¥Î¥H¤Uªº©R¥O¨ÓÀˬd¥Ø«eªº securelevel¡G
&prompt.root; sysctl kern.securelevel
§AµLªk°§C securelevel¡F§A¥²¶·±Ò°Ê¹q¸£¦Ü³æ¤H¼Ò¦¡¤U¥Hקï®É¶¡¡A
©Î¬Oקï /etc/rc.conf ¦A«·s¶}¾÷¡C½Ð°Ñ¦Ò
&man.init.8; »¡©ú¤å¥ó¡A¥H¨ú±o§ó¦h¦³Ãö securelevel ªº¸ê°T¡AÁÙ¦³
/etc/defaults/rc.conf ©M &man.rc.conf.5;
»¡©ú¤å¥ó¡A¥H¨ú±o§ó¦h¦³Ãö rc.conf ªº¸ê°T¡C
¬°¤°»ò rpc.statd ¥Î¤F 256 megabytes
ªº°O¾ÐÅé¡H
¤£¡A¨º¤£¬O memory leak¡A¦Ó¥B¥¦¤]¤£¬O¯uªº¥Î¤F 256 Mbyte
ªº°O¾ÐÅé¡C¥¦¥u¬O³ßÅw (·N«ä´N¬OÁ`·|³o¼Ë§@) ±N¤@ª¯²¼ªº°O¾ÐÅé
¬MÁ¨쥦¦Û¤vªº¦ì§}ªÅ¶¡¡A¥H¤è«K§@¨Æ¡C´N§Þ³N¦Ó¨¥¡A³o¼Ë¨Ã¨S¦³
¤°»ò¤£¹ï¡F³o¼Ë¥u¬O·|Åý &man.top.1; ©M &man.ps.1; À~¤@¤j¸õ¦Ó¤w¡C
&man.rpc.statd.8; ·|±N¥¦ªºª¬ºAÀÉ®× (¦ì©ó /var
) ¬M®g¦Ü¥¦ªº¦ì§}ªÅ¶¡¸Ì¡F¬°¤F¨¾¤î»Ýnªº®ÉÔ¦A¼W¤j©Ò
¾ÉPªº«·s¬M®g¡A¥¦¤@¦¸·|¨Ï¥Î¬Û·í¤jªº¤j¤p¡C±qµ{¦¡½X¨Ó¬Ýªº¸Ü´N
§ó©úÅã¤F¡A¥i¥H¬Ý¨ì &man.mmap.2; ªºªø«×°Ñ¼Æ¬° 0x10000000
¡A¥¦¬O IA32 ¬[ºc¤Wªº¤Q¤»¤À¤§¤@ªº©w§}ªÅ¶¡¡A¤]´N¬O
256MB¡C
¬°¤°»ò§Ú¨S¿ìªk¨ú®ø schg Àɮ׺X¼Ð¡H
§A¥¿¦b¤@Ó´£°ª¤F securelevel (¤]´N¬O¤j©ó 0) ªº¨t²Î¹B§@¡C
°§C securelevel ¦A¸Õ¸Õ¬Ý¡C½Ð°Ñ¦Ò
FAQ ¤¤¹ï securelevel ªº»¡©ú ©M &man.init.8; »¡©ú¤å¥ó¡C
¬°¤°»òªñ¨Óªº·sª© FreeBSD ¹w³]µLªk§Q¥Î .shosts
§¹¦¨ SSH »{ÃÒ¡H
¬°¤°»òªñ¨Ó·sª© FreeBSD .shosts »{ÃÒ¹w³]
¬°¨ú®øªºì¦]¡A¬O¦]¬° &man.ssh.1; ¹w³]¤£¦w¸Ë¬° suid ¦¨
root ¡Cn ×¥¿
³oÂI¡A§A¥i¥H§@¤U¦Cªº
¥ô¦ó¤@¥ó¨Æ¡G
n¤@³Ò¥Ã¶h¸Ñ¨M¡A½Ð±N /etc/make.conf
¸Ìªº ENABLE_SUID_SSH ³]¦¨ true
¡AµM«á¦A«·s build ssh (©Î¬O°õ¦æ make
world )¡C
¥u§@¤@®Éªº×¥¿ªº¸Ü¡A¥i¥H root ¨¥÷
°õ¦æ chmod 4755 /usr/bin/ssh ±N
/usr/bin/ssh ³]¦¨ 4555
¡CµM«á±N ENABLE_SUID_SSH= true
¥[¤J /etc/make.conf ¸Ì¡A³o¼Ë¤U¦¸
make world °õ¦æ´N·|¥Í®Ä¤F¡C
¤°»ò¬O vnlru ?
·í¨t²Î¹F¨ì¤W kern.maxvnodes ®É¡A
vnlru ·|²M°£¨ÃÄÀ©ñ vnode¡C³oÓ®Ö¤ß
°õ¦æºü¤j³¡¥÷ªº®É¶¡³£¨S¨Æ§@¡A¥u¦³·í§A¦³«Ü¤jªº°O¾ÐÅé¡A¦Ó¥B
¥¿¦b¦s¨ú¤W¸UÓ¤pÀɮ׮ɡA¤~·|³Q±Ò°Ê¡C
Wei-Hon
Chen
plasmaball@pchome.com.tw
X Window System ¤Î Virtual Consoles
§Ú·Qn°õ¦æ X ¡A§Ú¸Ó«ç»ò°µ¡H
³Ì²³æªº¤èªk´N¬O¦b¦w¸Ë¨t²Îªº®ÉÔ¤@¨Ö¦w¸Ë¡C
µM«á¬Ý¬Ý xf86config ªº¤å¥ó¡A³oÓµ{¦¡¥i¥H
À°±z³]©w XFree86(tm) ¨Ï¥¦¯à°÷¨Ï¥Î±zªºÅã¥Ü¥d/·Æ¹«µ¥¶gÃä¡C
±z©Î³\¤]·Q¸Õ¸Õ¬Ý Xaccel server¡C¸Ô±¡½Ð¬Ý
Xi Graphics ©Î¬O Metro Link
³o¤@¬q¡C
§Ú ¸ÕµÛ n°õ¦æ X, ¦ý¬O·í§ÚÁä¤J
startx ®É¡A±o¨ì
KDENABIO failed (Operation not permitted)
¿ù»~¡C§Ú¸Ó«ç»ò¿ì¡H
§Aªº¨t²Î¤@©w´£°ª¤F securelevel¡A¹ï¤£¹ï¡H¦b¤@Ó´£°ª¤F
securelevel ªº¨t²Î¤W¡A¬Oµ´¹ïµLªk°_°Ê X ªº¡C·Qª¾¹D¬°¤°»ò¡A
½Ð°Ñ¦Ò &man.init.8; »¡©ú¤å¥ó¡C
©Ò¥H³oÓ°ÝÃDÅܦ¨¡G§AÁÙ¯à«ç»ò¿ì¡C°ò¥»¤W§A¦³¨âºØ¿ï¾Ü¡G
±N§Aªº securelevel ³]¦^¹s (³q±`¦b /etc/rc.conf
¸Ì±³]©w)¡A©Î¬O¦b±Ò°Ê®É°õ¦æ &man.xdm.1; (¦b
securelevel ³Qª@°ª«e)¡C
½Ð°Ñ¦Ò ¥H¨ú±o§ó¦h¦³Ãö±Ò°Ê®É
°õ¦æ &man.xdm.1; ªº¸ê°T¡C
¬°¤°»ò§Ú¤£¯à¦b X ¸Ì¨Ï¥Î·Æ¹«¡H
¦pªG±z¥Îªº¬O syscons (¤º©wªº console ÅX°Êµ{¦¡) ªº¸Ü¡A±z¥i¥H
¸g¥Ñ³]©w FreeBSD ¨ÓÅý¥¦¤ä´©¦b¨CÓ virtual console ¨Ï¥Î·Æ¹«¡C¬°¤F
ÁקK©M X ²£¥Í½Ä¬ð¡Asyscons ¨Ï¥Î¤F¤@Ó¥s°µ
/dev/sysmouse ªºµêÀÀ¸Ë¸m¡C©Ò¦³·Æ¹«²£¥Íªº
event ³£·|§Q¥Î moused ¨Ó¼g¨ì sysmouse ³oӸ˸m¡C¦pªG±z§Æ±æ¦b¤@Ó
©Î¥H¤Wªº virtual console ¤W¨Ï¥Î·Æ¹«¡A¨Ã¥B
¯à°÷¨Ï¥Î X ªº¸Ü¡A½Ð°Ñ¦Ò
¨Ã¥B³]©w¦n
moused¡C
µM«á½s¿è /etc/XF86Config ³oÓÀɮסA
¨Ã¥B½T»{§A¦³¥H¤U³o´X¦æªº³]©w¡C
Section Pointer
Protocol "SysMouse"
Device "/dev/sysmouse"
....
¥H¤Wªº¨Ò¤l¡A¾A¥Î©ó XFree86 3.3.2 ¤Î¨ä«áªºª©¥»¡C¥Î©ó§ó¦ªº
ª©¥»ªº¡A¨ä Protocol À³¬°
MouseSystems ¡C
¦³¨Ç¤H¤ñ¸û³ßÅw¦b³]©w X ªº®ÉÔ¥Î
/dev/mouse ³oӸ˸m¡C¦pªG±znÅý¥¦¯à°÷
¥¿±`¤u§@ªº¸Ü¡A±z´N¥²¶·§â /dev/mouse
³sµ²¨ì /dev/sysmouse (½Ð°Ñ¦Ò
&man.sysmouse.4;):
&prompt.root; cd /dev
&prompt.root; rm -f mouse
&prompt.root; ln -s sysmouse mouse
§Úªº·Æ¹«¦³Ó«Ü¬¯ªººu½ü¡C§Ú¯à¦b X ¸Ì±¨Ï¥Î¶Ü¡H
¥i¥H¡C¤£¹L§A»Ýn³]©w X ¥Î¤áºÝµ{¦¡¡C ½Ð°Ñ¦Ò
Colas Nahaboo ªººô¶
(http://www.inria.fr/koala/colas/mouse-wheel-scroll/)
.
¦pªG§An¨Ï¥Î imwheel µ{¦¡¡A
¥un¸òµÛ¤U¦C¨BÆJ§@§Y¥i¡C
Âà´«ºu½ü event
Translate the Wheel Events
imwheel µ{¦¡ªº¹B§@ì²z¡A
¬O±N·Æ¹«ªº²Ä¥|Áä»P²Ä¤ÁäÂà´«¦¨«öÁä event¡C¦]¬°¦p¦¹¡A©Ò¥H
§A¥²¶·Åý·Æ¹«ÅX°Êµ{¦¡±N·Æ½ü¨Æ¥óÂà´«¦¨²Ä¥|Áä»P²Ä¤Áä event¡C
¦³¨âºØ¤èªk¥i¥H¹F¨ì¥Øªº¡A¤@¬OÅý &man.moused.8; §@Âà´«¡A¤G¬O
Åý X ¥»¨¥h§@ event Âà´«¡C
¨Ï¥Î &man.moused.8; ¨ÓÂà´«ºu½ü Event
nÅý &man.moused.8; ¨Ó§@ event Âà´«¡A¥un¦b
°õ¦æ &man.moused.8; ªº©R¥O¦C¤¤¥[¤W -z 4
§Y¥i¡CÁ|Ó¨Ò¤l¡A¦pªG§A¤@¯ë³£¬O¥H
moused -p /dev/psm0 ¨Ó°_°Ê
&man.moused.8; ªº¸Ü¡A¥un§ï¦¨ moused -p
/dev/psm0 -z 4 §Y¥i¡C¦pªG§A¬O¦b¶}¾÷¹Lµ{¤¤§Q¥Î
/etc/rc.conf ¨Ó°_°Ê &man.moused.8;¡A
§A¥i¥H¦b /etc/rc.conf ¤¤±N
moused_flags ¤W¥[ -z 4
§Y¥i¡C
§A²{¦b»ÝnÅý X ª¾¹D§Aªº·Æ¹«¦³¤Ó«öÁä¡A¥un¦b
/etc/XF86Config ¤¤ªº
Pointer
°Ï¶ô¤¤¥[¤W
Buttons 5 ³o¤@¦æ§Y¥i¡C¨Ò¦p¡A
§A¥i¯à¦b /etc/XF86Config ¤¤¦³
¥H¤Uªº Pointer
°Ï¶ô¡G
¦b XFree86 3.3.x ¨t¦Cªº XF86Config ³]©wÀɪº
Pointer
°Ï¶ô¤¤¡A¥H moused §@Âà´«
ªººu½ü¹«ªº³]©w½d¨Ò
Section "Pointer"
Protocol "SysMouse"
Device "/dev/sysmouse"
Buttons 5
EndSection
¦b XFree86 4.x ¨t¦Cªº XF86Config ³]©wÀɪº
InputDevice
°Ï¶ô¤¤¡A¥H X Server §@Âà´«
ªººu½ü¹«ªº³]©w½d¨Ò
Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/sysmouse"
Option "Buttons" "5"
EndSection
¦b .emacs
¤¤¡A³]©wºu½ü¹«ªºì¥Í
¶±ºu°Ê¤ä´©½d¨Ò
;; wheel mouse
(global-set-key [mouse-4] 'scroll-down)
(global-set-key [mouse-5] 'scroll-up)
§Q¥Î§Aªº X Server ¨Ó§@ºu½ü Event Âà´«
¦pªG§A¨S¦³°õ¦æ &man.moused.8;¡A©Î¬O§A¤£·Q§Q¥Î
&man.moused.8; ¥h§@ºu½ü event Âà´«¡A§A¥i¥H§ï¥Î
X server ¨Ó§@³o¼Ëªº event Âà´«¡C§A±o¦b
/etc/XF86Config Àɮפ¤§@´XÓ§ó°Ê¡C²Ä¤@¡A
§An¬°§Aªº·Æ¹«¿ï¾Ü¾A·íªº³q°T¨ó©w¡C¤j¦h¼Æªººu½ü¹«³£
¨Ï¥Î IntelliMouse
¨ó©w¡A¤£¹L XFree86
¤]¤ä´©¨ä¥¦ªº³q°T¨ó©w¡A¨Ò¦pù§Þªº MouseMan+ ·Æ¹«©Ò¥Îªº
MouseManPlusPS/2
¡C·í§A¿ï¦n¤§«á¡A¥un
¥[¶i¤@¦æ Pointer
°Ï¶ôªº
Protocol ÅܼƧY¥i¡C
²Ä¤G¡A§An§i¶D X server ±N±²°Ê¨Æ¥ó«·s¹ï¬M¦Ü·Æ¹«ªº
²Ä¥|©M²Ä¤Áä¡C³o¥i¥H§Q¥Î ZAxisMapping
¿ï¶µ¿ì¨ì¡C
Á|Ó¨Ò¤l¡A¦pªG§A¨S¦³¨Ï¥Î &man.moused.8;¡A¦Ó§A¦³¤@Ó
IntelliMouse ¦w¸Ë¦b PS/2 ·Æ¹«°ðªº¸Ü¡A§A¥i¥H¦b
/etc/XF86Config ¸Ì¨Ï¥Î¥H¤Uªº³]©w¡C
¦b XF86Config ³]©wÀɪº Pointer
°Ï¶ô¤¤¡A¥H X Server §@Âà´«ªººu½ü¹«ªº³]©w½d¨Ò
Section "Pointer"
Protocol "IntelliMouse"
Device "/dev/psm0"
ZAxisMapping 4 5
EndSection
¦b XFree86 4.x ¨t¦Cªº XF86Config ³]©wÀɪº
InputDevice
°Ï¶ô¤¤¡A¥H X Server §@Âà´«
ªººu½ü¹«ªº³]©w½d¨Ò
Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psm0"
Option "ZAxisMapping" "4 5"
EndSection
¦b .emacs
¤¤¡A³]©wºu½ü¹«ªºì¥Í
¶±ºu°Ê¤ä´©½d¨Ò
;; wheel mouse
(global-set-key [mouse-4] 'scroll-down)
(global-set-key [mouse-5] 'scroll-up)
¦w¸Ë imwheel
±µ¤U¨Ó¡A±q Ports ¸Ì¦w¸Ë imwheel
¡C¦b x11 Ãþ§O¸Ì¥i¥H§ä¨ì¥¦¡A¥¦¥i¥H±N
ºu½ü event ¹ï¬M¨ìÁä½L event¡CÁ|Ó¨Ò¤l¡A¥¦¥i¥H¦b§A
±Nºu½ü©¹«e±À®É¡A°e¥X¤@Ó Page Up
¨ì§AªºÀ³¥Îµ{¦¡¥h¡CImwheel
§Q¥Î¤@Ó³]©wÀÉ¡A¥H«K¹ïÀ³ºu½ü event ¦ÜÁä½L event¡A³o¼Ë
¥¦´N¥i¥H¦b¤£¦PªºÀ³¥Îµ{¦¡¤¤¡A°e¥X¤£¦PªºÁä½L«öÁä¡C¹w³]ªº
imwheel ³]©wÀɬO¦b
/usr/X11R6/etc/imwheelrc ¡A¦pªG§A·Q
½s¿è¦Ûqªº³]©wÀɪº¸Ü¡A¥i¥H±N¥¦½Æ»s¨ì
~/.imwheelrc ¡AµM«á¨Ì§Aªº»Ýnק復¡C
³]©wÀɪº®æ¦¡¦b &man.imwheel.1; ¸Ì±¦³¸Ô²Óªº»¡©ú¡C
³]©w Emacs »P
Imwheel ¨ó¦P¤u§@
(¿ï¾Ü©Ê )
¦pªG§A¨Ï¥Î emacs ©Î¬O
Xemacs ªº¸Ü¡A¨º§A»Ýn¦b§Aªº
~/.emacs Àɮ׸̥[¤W¤@¤p¬q³]©w¡C
emacs ½Ð¥[¤W³o¤@¬q¡G
Imwheel ªº
Emacs ³]©w
;;; For imwheel
(setq imwheel-scroll-interval 3)
(defun imwheel-scroll-down-some-lines ()
(interactive)
(scroll-down imwheel-scroll-interval))
(defun imwheel-scroll-up-some-lines ()
(interactive)
(scroll-up imwheel-scroll-interval))
(global-set-key [?\M-\C-\)] 'imwheel-scroll-up-some-lines)
(global-set-key [?\M-\C-\(] 'imwheel-scroll-down-some-lines)
;;; end imwheel section
Xemacs «h¦b
~/.emacs Àɸ̥[¤W³o¤@¬q¡G
Imwheel ªº
Xemacs ³]©w
;;; For imwheel
(setq imwheel-scroll-interval 3)
(defun imwheel-scroll-down-some-lines ()
(interactive)
(scroll-down imwheel-scroll-interval))
(defun imwheel-scroll-up-some-lines ()
(interactive)
(scroll-up imwheel-scroll-interval))
(define-key global-map [(control meta \))] 'imwheel-scroll-up-some-lines)
(define-key global-map [(control meta \()] 'imwheel-scroll-down-some-lines)
;;; end imwheel section
°õ¦æ Imwheel
¦w¸Ë¤§«á¡A§A¥i¥Hª½±µ¦b xterm ¸ÌÁä¤J imwheel
©R¥O¥H°_°Ê¥¦¡C¥¦·|¥HI´º°õ¦æ¡A¨Ã¥B°¨¤Wµo´§®Ä¥Î¡C
¦pªG§A½T©wnª½±µ¨Ï¥Î imwheel ¡A
¥un§â¥¦¥[¶i§A¦Û¤vªº .xinitrc ©Î
.xsession ¤ºÀɮקY¥i¡C§A¥i¥H¤£ºÞ
imwheel ©Ò°e¥X¨Ó¦³Ãö PID ÀÉ®×
ĵ§i¡C¨º¨Çĵ§i¥u¹ï Linux ª©ªº imwheel
¦³®Ä¦Ó¤w¡C
§â Num Lock Ãö±¼¸Õ¸Õ¡C
¦pªG±zªº Num Lock ¦b¶}¾÷®Éªº¹w³]ȬO¶}µÛªº¸Ü¡A±z¥²¶·§â¤U¦C
³o¦æ©ñ¨ì XF86Config ³]©wÀɤ¤ªº
Keyboard ³¡¥÷¡C
# Let the server do the NumLock processing. This should only be
# required when using pre-R6 clients
ServerNumLock
¤°»ò¬O virtual console¡H§Ún«ç»ò°µ¤~¯à¥Î¦h¤@ÂI¡H
²³æ¨Ó»¡¡Avirtual console ´N¬O¥i¥HÅý±z¤£¥²°µ¤Ó¦h½ÆÂøªº³]©w
¦p¨Ï¥Îºô¸ô©Î°õ¦æ X ¡A¦Ó¦b¦P¤@»O¾÷¾¹¤W¦P®É°µ¦n´X¥ó¨Æªº¤èªk¡C
·í±Ò°Ê¨t²Î¨ÃÅã¥Ü§¹©Ò¦³¶}¾÷°T®§¤§«á¡A±z´N·|¦b¿Ã¹õ¤W¬Ý¨ì¤@Ó
login ªº´£¥Ü²Å¸¹¡C¦b³oÓ®ÉÔ±z´N¥i¥H¿é¤J±zªº login name ¥H¤Î
password ¡AµM«á´N¥i¥H¦b²Ä¤@Ó virtual console ¤W¶}©l¤u§@¤F
(©ÎªÌ¶}©lª±¡I) ¡C
¦b¬Y¨Ç±¡ªp¤U¡A±z¥i¯à·|·Qn§@¨ä¥Lªº¤u§@¡A¨Ò¦p»¡¬O¬Ý¬Ý±z¥¿¦b
°õ¦æªºµ{¦¡ªº»¡©ú¤å¥ó¡A©Î¬O·í±z¦b FTP ¶Ç¿éªºµ¥«Ý®É¶¡¤¤¬Ý¬Ý±zªº
¶l¥ó¡C±z¥u»Ýn«ö Alt-F2 («ö¦í Alt Á䤣©ñ¡A¨Ã«ö¤U F2 Áä) ¡AµM«á
±z´N·|¦b²Ä¤GÓ virtual console
¤W¬Ý¨ì¤@Ó login
´£¥Ü²Å¸¹¡I·í±z·Qn¦^¨ìì¨Óªº¤u§@®É¡A½Ð«ö Alt-F1¡C
FreeBSD ¦b¦w¸Ë®Éªº¹w³]ȬO¨Ï¥Î¤TÓ virtual console
(3.3-RELEASE «á¬°¤KÓ)¡A±z¥i¥H¥Î Alt-F1¡AAlt-F2¡A¥H¤Î Alt-F3
¦b¥¦Ì¤§¶¡°µ¤Á´«¡C
¦pªG±z·Qn¦h¤@ÂI virtual console ªº¸Ü¡A±z¥u»Ýn½s¿è
/etc/ttys ³oÓÀÉ (½Ð°Ñ¦Ò &man.ttys.5;)¡A
¦b Virtual terminals
³oÓµù¸Ñ«á±¥[¤J
ttyv4 ¨ì ttyvc
ªºÄæ¦ì¡G
# Edit the existing entry for ttyv3 in /etc/ttys and change
# "off" to "on".
ttyv3 "/usr/libexec/getty Pc" cons25 on secure
ttyv4 "/usr/libexec/getty Pc" cons25 on secure
ttyv5 "/usr/libexec/getty Pc" cons25 on secure
ttyv6 "/usr/libexec/getty Pc" cons25 on secure
ttyv7 "/usr/libexec/getty Pc" cons25 on secure
ttyv8 "/usr/libexec/getty Pc" cons25 on secure
ttyv9 "/usr/libexec/getty Pc" cons25 on secure
ttyva "/usr/libexec/getty Pc" cons25 on secure
ttyvb "/usr/libexec/getty Pc" cons25 on secure
±z·Q¥Î´XÓ´N³]´XÓ¡C±z³]¶V¦h virtual terminal ¡A¥¦Ì´N¥Î±¼
¶V¦h¨t²Î¸ê·½¡F¦pªG±z¥u¦³¤£¨ì 8MB ªº°O¾ÐÅ骺¸Ü¡A³o¼vÅT´N¤j¤F¡C
±z¥i¯à¤]·|·Q§â secure ´«¦¨
insecure ¡C
¦pªG±z·Qn°õ¦æ X ªº¸Ü¡A±z ¥²¶·
¬°¥¦«O¯d (©ÎÃö±¼) ¦Ü¤Ö¤@Ó virtual terminal ¡C³o´N¬O»¡¡A¦pªG
±z·Q¦b«ö¤Q¤GÓ Alt ¥\¯àÁä®É³£¦³ login ´£¥Ü²Å¸¹¡A¦Ó¥B¤S¦b¦P¤@
³¡¹q¸£¤W¤]·Q°õ¦æ X ªº¸Ü¡A¨º»ò³o¯u¬O¤Ó¤£©¯¤F - ±z¥u¯à¥Î¤Q¤@Ó¡C
¨ú®ø¤@Ó console ³Ì²³æªº¤èªk´N¬O§â¥¦Ãö±¼¡CÁ|¨Ò¨Ó»¡¡A¦pªG
±z¹³¤W±Á¿ªº¤@¼Ë³]©w¤F¥þ³¡ªº 12 Ó terminal ¨Ã¥B·Qn°õ¦æ X ¡A
±z¥²»Ý§â virtual terminal 12 ±q¡G
ttyvb "/usr/libexec/getty Pc" cons25 on secure
³]¦¨¡G
ttyvb "/usr/libexec/getty Pc" cons25 off secure
¦pªG±zªºÁä½L¥u¦³ 10 Ó¥\¯àÁ䪺¸Ü¡A±z´Nn§ï¦¨³o¼Ë¡G
ttyv9 "/usr/libexec/getty Pc" cons25 off secure
ttyva "/usr/libexec/getty Pc" cons25 off secure
ttyvb "/usr/libexec/getty Pc" cons25 off secure
(±z¤]¥i¥Hª½±µ§â³o´X¦æ¬å±¼¡C)
¤@¥¹±z§ï¤F /etc/ttys ¡A¤U¤@Ó¨BÆJ´N¬On
½T©w±z¦³¨¬°÷ªº virtual terminal ¸Ë¸m¡C³Ì²³æªº¤èªk´N¬O¡G
&prompt.root; cd /dev
&prompt.root; sh MAKEDEV vty12
¦A¹L¨Ó¡A·Qn±Ò°Ê³o¨Ç virtual console ³Ì²³æ (¤]¬O³Ì°®²b)
ªº°µªk´N¬O«¶}¾÷¡CµM«á¡A¦pªG±z¤£·Q«¶}¾÷ªº¸Ü¡A±z¥i¥H§â X Window
Ãö±¼¡AµM«á¥Î root ªº¨¥÷°õ¦æ¤U¦C«ü¥O¡G
&prompt.root; kill -HUP 1
·í±z°õ¦æ³oÓ©R¥O«e¡A±z¤@©wn§¹¥þ§â X Window Ãö±¼¡C¦pªG
±z¤£³o»ò°µªº¸Ü¡A±zªº¨t²Î¥i¯à·|¦b±z°õ¦æ kill ©R¥O«á¥X²{·í±¼©Î
Âꦺªº±¡ªp¡C
§Ún«ç»ò±q X ¤Á´«¨ì virtual console¡H
½Ð¥Î
Ctrl
Alt
Fn
¥H¤Á¦^¦Ü virtual console¡C
Ctrl
Alt
F1
¥i¥H¤Á¦^¦Ü²Ä¤@Ó virtual console¡C
·í§A¤Á¦^¦Ü¤å¦r console «á¡A§A´N¥i¥H¨Ï¥Î¤@¯ë
Alt
Fn
«öÁä²Õ¦X¡A¦b¦U console ¤§¶¡¤Á´«¡C
n¦^¨ì X ªº¸Ü¡A§A¥²¶·¤Á¦^¦Ü°õ¦æ X ªº virtual console¡C
¦pªG§A¬O±q©R¥O¦C¸Ì°_°Ê X ªº¸Ü (¨Ò¦p¨Ï¥Î startx
«ü¥O)¡A¨º»ò X ·|¨Ìªþ¦b¤U¤@Ó¥¼¨Ï¥Îªº virtual console¡A¦Ó¤£¬O¥¦³Q
°_°Êªº¤å¦r console¡C¦pªG§A¦³¤KӨϥΤ¤ªº virtual terminal¡A¨º»ò
X ´N·|¦b²Ä¤EÓ¤W°õ¦æ¡A§A´N¥i¥H¨Ï¥Î
Alt
F9
¥Hªð¦^¦Ü X ¤¤¡C
§Ún«ç»ò°µ¤~¯à¦b¶}¾÷®É±Ò°Ê XDM¡H
¦³¨âºØ¤èªk¥i¥H±Ò°Ê
xdm ¡C¤@ºØ¤èªk¬O±q /etc/ttys ¨Ó±Ò°Ê¡A
¥i¥H°Ñ¦Ò &man.ttys.5; »¡©ú¤å¥ó¤¤ªº½d¨Ò¡F¥t¤@ºØ¤èªk¬O¦b
rc.local (½Ð°Ñ¦Ò &man.rc.8;) °õ¦æ xdm¡A©Î¬O
¦b /usr/local/etc/rc.d ©ñ¤@Ó
X.sh ¡C³o¨âºØ¤èªk³£¬O¦Xªkªº¡A¦pªG±z¸Õ¬Y¤@ºØ
¤èªkµL®Äªº¸Ü¡A±z¥i¥H¸Õ¸Õ¥t¥~¤@ºØ¡C³o¨âºØ¤èªkªºµ²ªG¬O¤@¼Ëªº¡GX
·|Åã¥Ü¤@ӹϧΤƪº login: ´£¥Ü¡C
¥Î ttys ªº¤èªkªºÀuÂI¡A¦b©ó«ü©ú¤F X ¦b±Ò°Ê®É¨ì©³¬O¥Î¨ºÓ vty¡A
¨Ã¥B±N logout ®É«·s±Ò°Ê X server ªº³d¥ô¥áµ¹ init¡C rc.local
ªº¤èªk«h¬O¦b·í±Ò°Ê X ¥X¤F°ÝÃD®É¡A¥i¥H«Ü»´ÃP¦a§â xdm ±þ±¼¨Ó¸Ñ¨M
°ÝÃD¡C
¦pªG¬O¥Î rc.local ªº¤èªk¡A¦b°õ¦æ xdm
®É±z¤£¯à¥[¥ô¦ó°Ñ¼Æ¡]¤]´N¬O¶]¦¨ daemon¡^¡C¥²¶·¦b getty °õ¦æ«á
¤~¯à±Ò°Ê xdm¡A§_«h getty ©M xdm ·|¤¬¬Û½Ä¬ð¦ÓÂê¦í console¡C³Ì¦nªº
¤è¦¡¬O¦b script ¤¤¥[Ó sleep¡AÅý¥¦¼È°± 10 ¬íÄÁ¥ª¥k¡A±µµÛ¤~°õ¦æ
xdm¡C
¦pªG§A¬O±q /etc/ttys ±Ò°Ê
xdm ¡Axdm »P &man.getty.8;
¤´¦³¾÷·|¤¬¬Û½Ä¬ð¡C¤@ÓÁקK¥¦ªº¤èªk¡A´N¬O¦b
/usr/X11R6/lib/X11/xdm/Xservers Àɮפ¤¥[¤J
vt ¼Æ¦r¡C
:0 local /usr/X11R6/bin/X vt4
¤W±ªº¨Ò¤l¤¤¡A·|«ü¥Ü X server ¦b /dev/ttyv3
¤¤°õ¦æ¡C½Ðª`·N¼Æ¦r¬O®t¤@ªº¡CX server ±q¤@¶}©l¼Æ
vty¡A¦Ó FreeBSD ®Ö¤ß«h¬O±q¹s¶}©l¼Æ vty ªº¡C
¬°¤°»ò·í§Ú°õ¦æ xconsole ®É¡Aµo¥Í¤F
Couldn't open console ªº¿ù»~¡H
¦pªG§A¬O¥Î startx ¨Ó±Ò°Ê startx
ªº¸Ü¡A/dev/console ªºÅv¨Ã
¤£·| §ïÅÜ¡Aµ²ªG´N¬O xterm -C
©M xconsole ³oÃþªºµ{¦¡µLªk
¥¿±`°õ¦æ¡C
³o¤@¤Áªº°ÝÃD¡A³£¬O¦]¬° console ªºÅv¬O±Ä¥Î¨t²Î¹w³]È¡C
¦b¤@Ó¦h¨Ï¥ÎªÌªº¨t²Î¸Ì¡A§Ṳ́£§Æ±æ¨CӨϥΪ̳£¥i¥Hª½±µ¼g¤J¨t²Î
console ¡C¦pªG¨Ï¥ÎªÌ¬O±q¾÷¾¹ªº VTY ª½±µ login ªº¸Ü¡A¨º»ò
&man.fbtab.5; ¥i¥H¸Ñ¨M³oÃþªº°ÝÃD¡C
²³æ¦a»¡¡A½Ð½T«O /etc/fbtab (½Ð°Ñ¦Ò
&man.fbtab.5;) ³oÓÀɮפ¤ªº³o¤@¦æ¨S¦³³Qµù¸Ñ±¼¡G
/dev/ttyv0 0600 /dev/console
³o¤@¦æ³]©wªº¦s¦b¥i¥H½T«O±q /dev/ttyv0
µn¤Jªº¨Ï¥ÎªÌ¥i¥H±±¨î console¡C
¥H«e§Ú¥i¥H¥H¤@¯ë¨Ï¥ÎªÌ°õ¦æ XFree86¡A¬°¤°»ò²{¦b¥¦»¡§Ú¤@©wn
¥H root ¤~¯à°õ¦æ¡H
©Ò¦³ªº X server ³£»Ýn¥H root ¨Ó°õ¦æ¡A
¤~¯àª½±µ¦s¨ú§Aªºµø°TµwÅé¡Cª©¥»ªº XFree86 (<= 3.3.6) ·|¦Û°Ê
±N©Òªþªº server ¥H§Q¥Î root ¨¥÷°õ¦æªº¤è¦¡
¦w¸Ë°_¨Ó (setuid ¬° root )¡C¥Ñ©ó X server
³£¬OÅé¿nÃe¤j¤S½ÆÂøªºµ{¦¡¡AÅã¦Ó©ö¨£¦a¡A³o¬O¤@Ó¦w¥þ¤Wªº¨aÃø¡C
¦]¬°³oÓì¦]¡A·sª©ªº XFree86 ´N¤£±N³o¨Ç server ¥H setuid ¬°
root ªº¤è¦¡¦w¸Ë¡C
«Ü©úÅã¦a¡A§Ú̧¹¥þµLªk±µ¨ü±N X server ¥H
root ªº¨¥÷°õ¦æ¡C°_½X´N¦w¥þ¤W¤£¬OÓ¦n¥D·N¡C
¦³¨âºØ¤èªk¥i¥H¥H¤@¯ë¨Ï¥ÎªÌªº¨¥÷¨Ï¥Î X¡C²Ä¤@¬O§Q¥Î
xdm ©Î¬O¨ä¥¦ªº display manager (¨Ò¦p
kdm )¡F²Ä¤G¬O§Q¥Î Xwrapper ¡C
xdm ¬O¤@Ó³B²z¹Ï§Î¬É±µn¤Jªº daemon¡C
¥¦³q±`¦b¶}¾÷®É°õ¦æ°_¨Ó¡A¦Ó¥Bt³d¹ï¨Ï¥ÎªÌ§@¨¥÷»{ÃÒ¡A¥H¤Î°_°Ê
¨Ï¥ÎªÌªº¤u§@Àô¹Ò¡F¥¦¥i»¡¬O¹Ï§ÎÀô¹Ò¤Uªº &man.getty.8; »P
&man.login.1; ªº¹ïÀ³µ{¦¡¡C·Q±oª¾§ó¦h¦³Ãö xdm
ªº¸ê°T¡A½Ð°Ñ¦Ò
XFree86 ¤å¥ó ¡A¥H¤Î¨ä FAQ
¶µ¥Ø¡C
Xwrapper ¬O X server ªº¥]¸Ëµ{¦¡¡F¥¦¥i¥H
Åý¤@¯ë¨Ï¥ÎªÌ¥i¥H¤â°Ê°_°Ê X server ªº¤p¤u¨ã¡A¦ÓÁÙ¯àºû«ù¤@©wªº¦w¥þ
Àô¹Ò¡C¥¦·|Àˬd¶Ç¤Jªº©R¥O¦C°Ñ¼Æ¡A¦pªG¨S°ÝÃDªº¸Ü¡A´N°_°Ê¾A·íªº
X server¡C¦pªG§A¦]¬°¬YºØ²z¥Ñ¦Ó¤£·Q°õ¦æ display manager ªº¸Ü¡A
¥¦¬O¬°§A¦Ó³]©wªº¡C¦pªG§A¦w¸Ë¤F§¹¾ãªº ports¡A§A¥i¥H¦b
/usr/ports/x11/wrapper ¤¤§ä¨ì¥¦¡C
§Úªº PS/2 ·Æ¹«¦b X ¤¤¦³ÂI¤£¥¿±`¡H
±zªº·Æ¹«©M±zªº·Æ¹«ÅX°Êµ{¦¡¥i¯à¦s¦b¦³¤£¦P¨Bªº²{¶H¡C
¦b 2.2.5 ¥H¤Î§ó¦ªº¨t²Î¸Ì¡A±q X ¤Á¨ì virtual terminal µM«á
¦A¤Á¦^¨Ó´N¥i¥H¨Ï¥¦Ì«·s°µ¦P¨Bªº°Ê§@¡C¦pªG³oÓ°ÝÃD±`±`µo¥Íªº¸Ü¡A
±z¥i¥H¦b±zªº®Ö¤ß³]©wÀɤ¤¥[¤J¤U±³oӿﶵµM«á«·s½sĶ¡G
options PSM_CHECKSYNC
¦pªG±z¨S¦³«Ø¥ß®Ö¤ßµ{¦¡ªº¸gÅç¡A½Ð¬Ý
¦Ûq®Ö¤ß ³o¤@¸`¡C
¥[¤W³oӿﶵ¥H«á¡A·Æ¹«©M·Æ¹«ÅX°Êµ{¦¡¶¡ªº¦P¨B°ÝÃDÀ³¸Ó´N¤ñ¸û
¤£·|¥X²{¤F¡C¦pªG³oÓ°ÝÃD¤´µM¦s¦bªº¸Ü¡A¦b²¾°Ê·Æ¹«®É«ö«ö·Æ¹««öÁä
¥i¥H¨Ï·Æ¹«©M·Æ¹«ÅX°Êµ{¦¡«·s°µ¦P¨Bªº°Ê§@¡C
¸Óª`·Nªº¬O³oӿﶵ¨Ã¤£¬O¹ï¨C¤@Ó¨t²Î³£¦³®Ä¡A¥¦¥i¯à·|Åý±µ¦b
PS/2 ·Æ¹«¦ì¸mªº ALPS GlidePoint ¸Ë¸m¥¢¥h tap
³o¶µ¥\¯à¡C
¦b 2.2.6 ¤Î¨ä«áªºª©¥»¡A¦P¨Bªº½T»{¤w¸g¦³¤F¸û¦nªº¸Ñ¨M¿ìªk¡A
¦Ó¥B³o¨Ç³£¤w¸g¬O PS/2 ·Æ¹«ÅX°Êµ{¦¡ªº¼Ð·Ç¤F¡C³oÓ¤èªk¤]¥i¥H¦b
GlidePoint ¤W¥¿±`¤u§@¡C (¦]¬°½T»{ªºµ{¦¡½X¤w¸g¦¨¬°¤@Ӽзǥ\¯à¡A
©Ò¥H¦b³o¨Çª©¥»¤¤§Ṳ́£¦b´£¨Ñ PSM_CHECKSYNC ªº¿ï¶µ¤F¡C) ¤£¹L¦b
·¥¤Ö¼Æªº®×¨Ò¤¤¡A³o¨ÇÅX°Êµ{¦¡·|»~³ø¦P¨B©Ê¿ù»~¡AµM«á±z´N·|¬Ý¨ì
³o¼Ëªº®Ö¤ß°T®§¡G
psmintr: out of sync (xxxx != yyyy)
µM«á±z´N·|µo²{±zªº·Æ¹«¤£¯à¥¿±`¹B§@¤F¡C
¦pªG±zµo¥Í¤F³o¼Ëªºª¬ªp¡A±z¥²¶·Âǥѧâ PS/2 ·Æ¹«ÅX°Êµ{¦¡ªº flag
³]¦¨ 0x100 ¨Ó§â¦P¨B½T»{ªºµ{¦¡½Xµ¹¨ú®ø±¼¡CµM«á¦b¶}¾÷´£¥Ü²Å¸¹®É¥Î
-c ¿ï¶µ¨Ó¶i¤J UserConfig ¡G
boot: -c
µM«á¡A¦b UserConfig ©R¥O¦C¤¤Áä¤J¡G
UserConfig> flags psm0 0x100
UserConfig> quit
§Úªº PS/2 ·Æ¹«¤£¯à³z¹L MouseSystem ¨Ó¹B§@¡H
¦³¤@¨Ç³ø§i«ü¥X¬Y¨Ç¼tµPªº PS/2 ·Æ¹«¥u¯à¦b
°ª¸ÑªR«×
ª¬ºA¤U¤~¯à¹B§@¡C¦pªG¤£¬Oªº¸Ü¡A·Æ¹«´å¼Ð
·|±`±`¶]¨ì¿Ã¹õªº¥ª¤W¨¤¥h¡C
«D±`¤£©¯ªº¡A³oÓ°ÝÃD¦b 2.0.X ©M 2.1.X ¤U¬OµL¸Ñªº¡C¦b 2.2
¨ì 2.2.5 ª©¡A±z¥i¥H¹ï /sys/i386/isa/psm.c
¨Ï¥Î¤U¦C patch µM«á««Ø±zªº®Ö¤ß¡C¦pªG±z¨S¦³«Ø¥ß®Ö¤ßµ{¦¡ªº¸gÅç¡A
½Ð¬Ý ¦Ûq®Ö¤ß ³o¸`¡C
@@ -766,6 +766,8 @@
if (verbose >= 2)
log(LOG_DEBUG, "psm%d: SET_DEFAULTS return code:%04x\n",
unit, i);
+ set_mouse_resolution(sc->kbdc, PSMD_RES_HIGH);
+
#if 0
set_mouse_scaling(sc->kbdc); /* 1:1 scaling */
set_mouse_mode(sc->kbdc); /* stream mode */
¦b 2.2.6 ¤Î¥H«áªºª©¥»¡A¦b PS/2 ·Æ¹«ÅX°Êµ{¦¡¤¤³]©w 0x04 ªº
flag ·|§â·Æ¹«³]¦¨°ª¸ÑªR«×¼Ò¦¡¡C¦b¶}¾÷´£¥Ü²Å¸¹®É¥Î
-c ¿ï¶µ¨Ó¶i¤J UserConfig ¡G
boot: -c
µM«á¡A¦b UserConfig ªº©R¥O¦C¤¤Áä¤J¡G
UserConfig> flags psm0 0x04
UserConfig> quit
«e¤@¸`¦³´£¨ì¥t¤@Ó¥i¯à¾ÉP·Æ¹«°ÝÃDªºì¦]¡C
·í§Ú«Ø¥ß X µ{¦¡®É¡Aimake »¡¥¦§ä¤£¨ì
Imake.tmpl ¡C¥¦¦bþ¨à¡H
Imake.tmpl ¬O Imake ®M¥óªº¤@³¡¥÷¡AImake
¬O¼Ð·Çªº«Ø¥ß X µ{¦¡ªº¤u¨ã¡C Imake.tmpl
©M¨ä¥L¼ÆÓ header file ¤@¼Ë¬O«Ø¥ß X µ{¦¡ªº¥²nÀɮסA±z¥i¥H¦b
X prog distribution ¤¤§ä¨ì¥¦Ì¡C±z¥i¥H¥Î sysinstall ¨Ó¦w¸Ë©Î¬O
ª½±µ±q X distribution ¤¤¤â°Ê¦w¸Ë¡C
§Ú¦b build ¤@Ó X À³¥Îµ{¦¡¡A¥¦»Ýn XFree86 3.3.x¡A¦ý¬O
§Ú¤w¸g¦w¸Ë XFree86 4.x ¤F¡C§Ú¸Ó«ç»ò¿ì¡H
n§i¶D port ¦b½sĶµ{¦¡®É¡A¨Ï¥Î XFree86 4.x ¨ç¦¡®w¡A§A¥i¥H
¦b /etc/make.conf ¸Ì (¦pªG§A¨S¦³³oÓÀÉ¡A
½Ð«Ø¥ß¥¦) ¥[¤W¤U±³o¤@¦æ¡G
XFREE86_VERSION= 4
§Ún«ç»ò°µ¤~¯à³]©w¥ªºJ¤l¥Îªº·Æ¹«¡H
¦b±zªº .xinitrc ©Î¬O
.xsession ¤¤°õ¦æ
xmodmap -e "pointer = 3 2 1" ªº«ü¥O¡C
n¦p¦ó¦w¸Ë splash ¹Ï§ÎÅã¥Üµ{¦¡¡H¨º¸Ì¥i¥H§ä±o¨ì©O¡H
´N¦bµo¦æ FreeBSD 3.1 ¤§«e¡A§ÚÌ¥[¶i¤F¦b¶}¾÷®ÉÅã¥Ü
splash
¹Ï§Îªº·s¥\¯à¡C¥Ø«e¥Î¨ÓÅã¥Ü¦b¿Ã¹õ¤WªºÀÉ®×
¥²¶·¬O 256 ¦âªºÂI¯x°}¹Ï§Î (*.BMP ) ©Î ZSoft
PCX(*.PCX ) ªº®æ¦¡¡C°£¦¹¤§¥~¡A¸ÑªR«×¤]¥²¶·¦b
320x200 ¥H¤U¡A¤~¯à©M¼Ð·Ç VGA Åã¥Ü¥d·f°t¨Ï¥Î¡C¦pªG±z½sĶ kernel
®É¦³¥[¤J VESA ¤ä´©¡A¨º»ò³Ì¤j¸ÑªR«×¥i¥H¨ì 1024x768¡Cª`·N VESA ªº
¤ä´©»Ýn¥[¤J VM86 ³oÓ kernel ¿ï¶µ¡CVESA
¤ä´©¹ê»Ú¤W¥i¥H¦b½sĶ kernel ®É¥[¤J VESA ¿ï¶µ¡B
©Î¸ü¤J VESA ªº kld module ¨Ó¹F¦¨¡C
±znקﱱ¨î FreeBSD ¶}¾÷¨BÆJªº³]©wÀÉ¡A¤~¯à¨Ï¥Î splash
Åã¥Ü¹Ï§Îªº¥\¯à¡C³]©wÀɦbµo¦æ FreeBSD 3.2 «e¦³¨Ç§ó°Ê¡A©Ò¥H²{¦b
¦³¨âÓ¤èªk¥i¥H¸ü¤J splash ªº¥\¯à¡G
FreeBSD 3.1
¥ý¿ï¥X¥Î¨ÓÅã¥Ü¦b¿Ã¹õ¤Wªº¹Ï§Î¡A3.1 ª©¥u¤ä´© Windows
ªºÂI¯x°}®æ¦¡¡C¿ï¦n¤F±znªº¹ÏÀÉ«á¡A±N¥¦«þ¨ì
/boot/splash.bmp ¡C±µµÛ§â¤U±´X¦æ¥[¤J
/boot/loader.rc ¤¤¡G
load kernel
load -t splash_image_data /boot/splash.bmp
load splash_bmp
autoboot
FreeBSD 3.2+
°£¤F¥[¤J¹ï PCX Àɮתº¤ä´©¥~¡AFreeBSD 3.2 ¤]§ï¶i¤F
¶}¾÷µ{§Çªº³]©w¤è¦¡¡C¦pªG±zÄ@·Nªº¸Ü¡A¥i¥H¥Î¤Wz FreeBSD 3.1
ªº¤èªk¡A±N splash_bmp ´«¦¨
splash_pcx ¨Ó¸ü¤J PCX ÀɮקY¥i¡C
¦pªG·Q¥Î·sªº³]©w¤è¦¡¡A±zªº /boot/loader.rc
¥²¶·¥]¬A³o´X¦æ¡G
include /boot/loader.4th
start
ÁÙ»Ýn¤@Ó¥]§t¥H¤U´X¦æªº /boot/loader.conf
¡G
splash_bmp_load="YES"
bitmap_load="YES"
³o¬O°²³]±z¥Î /boot/splash.bmp
¨Ó·í§@ splash ªº¿Ã¹õÅã¥Ü¡C¦pªG·Q¥Î PCX ªºÀɮסA§â¥¦«þ¦¨
/boot/splash.pcx ¡A¦p¤Wz°µ¥X
/boot/loader.rc ¡A¦A±N³o´X¦æ¥[¨ì
/boot/loader.conf ¤¤¡G
splash_pcx_load="YES"
bitmap_load="YES"
bitmap_name="/boot/splash.pcx"
²{¦b´N¥u³Ñ¤U splash ¥Î¨ÓÅã¥Üªº¹ÏÀÉ¡A±z¥i¥H¦b
http://www.baldwin.cx/splash/ §ä¨ì¦UºØ¼Ë«~¡C
§Ú¯à¦b X ¸Ì¨Ï¥ÎÁä½L¤Wªº Windows
¶Ü¡H
¥i¥H¡C§A©Òn§@ªº¡A´N¬O§Q¥Î &man.xmodmap.1; ¥h©w¸q§A·Q¨Ï¥Î
ªº¥\¯à¡C
°²³]©Ò¦³ªº Windows
³£¬O¼Ð·Çªº¡A
¨º¥¦Ìªº keycode ¤À§O¬°¡G
115 - Windows Áä¡A
¦b¥ª¤âªº Ctrl »P Alt Á䤧¶¡
116 - Windows Áä¡A
¦b Alt-Gr Áä¥kÃä
117 - ¿ï³æÁä¡A¥k¤âªº Ctrl Á䥪Ãä
nÅý¥ªÃ䪺 Windows
Áä¦L¥X¤@Ó³rÂI¡A¸Õ¸Õ³oÓ¡G
&prompt.root; xmodmap -e "keycode 115 = comma"
§A¥i¯àn«¶]§Aªº windows manager¡A¤~·|¦³°Ê§@¡C
nÅý Windows Áä
ªº¹ï¬M¦b¨C¦¸ X °_°Ê®É¦Û°Ê³]©w¦n¡A§A¥i¥H¦b§Aªº
~/.xinitrc ¸Ì¥[¤W xmodmap ¡A
©Î¬O³Ì¦n«Ø¥ß¤@Ó ~/.xmodmaprc ÀɮסA¸Ì±
¨C¤@¦æ´N¬O¤@Ó xmodmap ªº¿ï¶µ¡AµM«á¦b§Aªº
~/.xinitrc ¸Ì¥[¤W¡G
xmodmap $HOME/.xmodmaprc
³o¤@¦æ¡C
¨Ò¦p¡A§A·Qn±N³o¤TÓÁä¦U¹ï¬M¨ì F13¡BF14 ©M F15¡C³oÅý§A¯à
¦b§Aªºµ{¦¡©Î¬O window manager ¤º±N¨ä¹ïÀ³¨ì«K§Qªº¥\¯à¤W¡Aµ¥¤@¤U
§ÚÌ·|¥Ü½d¡C
§â³o¨Ç©ñ¶i ~/.xmodmaprc ¸Ì¡G
keycode 115 = F13
keycode 116 = F14
keycode 117 = F15
°²¦p§A¥Î fvwm2 ªº¸Ü¡A§A¥i¥H§@³o¼Ëªº¹ï¬M¡A
Åý F13 ¯à°÷Åý´å¼Ð©Ò¦bªºµøµ¡ÁY¦¨¤p¹Ï¥Ü (©Î¬O¤Ï¹L¨Ó)¡CF14 Åý´å¼Ð
©Ò¦bªºµøµ¡Åܦ¨³Ì¤W¼hªºµøµ¡¡A©Î¬O°h¨ì¤U¼h¥h (¦pªG¥¦¤w¸g¬O³Ì¤W¼h
¤Fªº¸Ü)¡CF15 «h±N Workplace (application) ¿ï³æ¥s¥X¨Ó¡A§Y¨Ï´å¼Ð
¤£¦b®à±¤W¡C·í§A¨S¦³¥i¨£ªº®à±°Ï°ì®É¡A³oÓ¥\¯à´N¬Û·í¦a¤è«K (¦Ó¥B
«öÁä¤Wªº¹Ï®×©M³oÓ¥\¯à¬Û§k¦X)¡C
¥H¤Uªº ~/.fvwmrc ³]©w¥i§@¥X«ezªº¥\¯à¡C
Key F13 FTIWS A Iconify
Key F14 FTIWS A RaiseLower
Key F15 A A Menu Workplace Nop
§Ún«ç»ò¼Ë¤~¯à±o¨ì OpenGL ªº 3D µwÅé¥[³t¥\¯à¡H
3D ¥[³t¥\¯àªº¦³µL¡Aµø§A©Ò¨Ï¥Îªº XFree86 ª©¥»»PÅã¥Ü´¹¤ù
ªº«¬¸¹¦Ó©w¡C¦pªG§Aªº¬O NVIDIA ´¹¤ùªº¸Ü¡A½Ð¥h
FreeBSD NVIDIA
Driver Initiative ºô¶¬Ý¬Ý¡A¨º¸Ì¦³¦b XFree86-4 ¤W¨Ï¥Î
NVIDIA ´¹¤ùªº 3D ¥[³t¥\¯àªº°Q½×¡CXFree86-4 ¤Wªº¨ä¥¦Åã¥Ü¥d¼tµP
µwÅé¥[³t¥\¯àªº¸ê°T¡A ¥]¬A Matrox G200/G400, ATI Rage 128/Radeon,
3dfx Voodoo 3, 4, 5, ¥H¤Î Banshee¡A¥i¦b XFree86-4
Direct Rendering on FreeBSD ºô¶¤W§ä¨ì¡CXFree 3.3 ªº
¨Ï¥ÎªÌ¥i¥H¨Ï¥Î Utah-GLX port¡A¥¦¥i¥H¦b
graphics/utah-glx §ä¨ì¡C
¨Ï¥Î¥¦¥i¥H¦b Matrox Gx00, ATI Rage Pro, SiS 6326, i810,
Savage, ¥H¤Îªº NVIDIA ¤W±o¨ì¦³ªº OpenGL ¥[³t¡C
Biing Jong
Lin
bjlin@stic.gov.tw
Networking
§ÚÀ³¸Ó¨ìþÃä§ä¦³ÃöµLºÏºÐ¶}¾÷
diskless booting
ªº¸ê®Æ¡H
Diskless booting
´N¬OÅý FreeBSD ¥D¾÷±qºô¸ô
¤W¶}¾÷¡A¨Ã¥B±qºô¸ô¤Wªº server ¤WŪ¨ú¨ä¥L¥²nªºÀɮסA¦Ó«D¥Ñ¥D¾÷
ªºµwºÐ¤W¨ú±o³o¨ÇÀɮסC¸Ô²Óªº¸ê®Æ¥i¥H°Ñ¦Ò FreeBSD ¤â¥UªºµLºÏºÐ¶}¾÷½g
¡C
FreeBSD ªº¥D¾÷¥i¥H·í§@¬YÓºô¸ô¤Wªº¸ô¥Ñ¾¹(router)¶Ü¡H
¬Oªº¡C½Ð°Ñ¦Ò FreeBSD ¤â¥Uªººô¸ô¶i¶¥½g advanced
networking ¡A¤×¨ä¬O¸ô¥Ñ»P¹h¹D¾¹ routing
and gateways ªº³¡¤À¡C
§Ú¥i¥H³z¹L FreeBSD ±N§Úªº Win95 ¾÷¾¹³s¤W Internet ¶Ü¡H
°ò¥»¤W¡A·|°Ý³oºØ°ÝÃDªº¤H¦b®a¸Ì¦Ü¤Ö¦³¨â¥x¹q¸£¡A¤@¥x¶] FreeBSD
¥t¥~¤@¥x¶] Win95¡F³oÓ·Qªk¬O±N FreeBSD ¥D¾÷³s¤W Internet¡AµM«á³z
¹L³o¥x FreeBSD ¥D¾÷¡AÅý¶] Win95 ªº¹q¸£¯à°÷¤Wºô¡C³oÓ°ÝÃDºâ¬O«e¤@
Ó°ÝÃDªº¤@Ó¯S¨Ò ... µª®×¬O¡G¥i¥Hªº¡I¦b FreeBSD 3.x
ª©¤¤¡A¨Ï¥ÎªÌ¼Ò¦¡(user-mode)ªº &man.ppp.8; ¥]§t¤F
-nat ¿ï¶µ¡C¦pªG§A¦b
/etc/rc.conf ¨Ï¥Î-nat ¿ï¶µ¨Ã
³]©w gateway_enable ¬° YES
¡A¥H³oºØ³]©w±Ò°Ê &man.ppp.8; ¡A¨Ã¥B¥¿½Tªº³]©w§Aªº Windows ¥D¾÷ªº
¸Ü¡A³oÓ°µªkÀ³¸Ó¬O¥i¥H¥¿±`¨Ï¥Îªº¡C
Ãö©ó¥»¥DÃD§ó¸Ô²Óªº¸ê®Æ¥i¥H°Ñ¦Ò Steve Sims ©Ò¼¶¼gªº Pedantic PPP Primer ¤@¤å¡C
¦pªG§A¨Ï¥Îªº¬O®Ö¤ß¼Ò¦¡ (kernel-mode) PPP¡A©ÎªÌ§A¦³°Ï°ì³s½u
(Ethernet connection) ¥i³q¹F Internet ªº¸Ü¡A§A±N»Ýn¨Ï¥Î
&man.natd.8;¡C½Ð¬d¾\ FAQ ¤¤Ãö©ó natd
ªº³¡¤À¡C
FreeBSD ¤ä´© SLIP ©M PPP ¶Ü¡H
¬Oªº¡C§A¥i¥H¬d¬d man pages ¤¤Ãö©ó &man.slattach.8;¡A
&man.sliplogin.8;¡A&man.ppp.8;¡A¥H¤Î &man.pppd.8; ªº³¡¤À¡C
&man.ppp.8; ¤Î &man.pppd.8; ´£¨Ñ¶i¥XÂù¦V³s½uªº¤ä´©¡A¥t¥~
&man.sliplogin.8; ±Mªù´£¨Ñ¶i¤J³s½uªº¤ä´©¡A¦Ó &man.slattach.8;
±Mªù´£¨Ñ¦V¥~³s½uªº¤ä´©¡C
¦pªG§A»Ýn§ó¶i¤@¨Bªº¸ê®Æªº¸Ü,½Ð¬d¾\ FreeBSD ¤â¥U¤¤Ãö©ó PPP »P SLIP
ªº»¡©ú ¡C
¦pªG§A¥u¯à°÷¹L shell account
³s½u¨ì Internet
ªº¸Ü¡A§A¤]³\¥i¥H¸Õ¸Õ net/slirp
³oÓ®M¥óµ{¦¡¡C³oÓ®M¥óµ{¦¡¥i¥H´£¨Ñ§Aªº¹q¸£ª½±µ³s¤W¬Y¨Ç(©wªº)ªA°È
³s½u¡A¦p ftp ¤Î http µ¥µ¥¡C
FreeBSD ¤ä´© NAT ©Î Masquerading ¶Ü¡H
¦pªG§A¦³¤@ÓªñºÝªº¤lºô¸ô(¦³¤@¥x¥H¤Wªº¾÷¾¹)¡A¦ý¬O§Aªº
Internet provider «o¥u¤À°t¤@Ó IP number µ¹§A(©ÎªÌ§A¥u¤À°t¨ì¤@Ó
°ÊºAªº IP number)¡A§A¥i¥H°Ñ¦Ò &man.natd.8; ³oÓµ{¦¡¡C &man.natd.8;
Åý§A¥i¥H³z¹L³o¤@Ó IP number Åý¾ãÓ¤lºô¸ôªº¹q¸£³£¯à³s¤W internet¡C
&man.ppp.8; ³oÓµ{¦¡¤]´£¨ÑÃþ¦üªº¥\¯à¡A¦pªG§A«ü©w
-nat ¿ï¶µ¡Calias library (&man.libalias.3;)
¦b³o¨âÓ³B²z¤è¦¡¤¤³£·|³Q¨Ï¥Î¨ì¡C
§Ú¦p¦ó±N¨â¥x FreeBSD ¥D¾÷¥Î¥¦æ°ð (parallel line) ³z¹L PLIP
³s½u¡H
½Ð°Ñ¦Ò¤â¥U¤¤Ãö©ó PLIP
section ªº³¡¤À¡C
§Ú¨S¦³¿ìªk«Ø¥ß /dev/ed0 ³oÓ device¡A
¬°¤°»ò¡H
¦]¬°¤£»Ýn¡I¦b Berkeley ºô¸ô¬[ºc¤¤¡A¥u¦³ kernel µ{¦¡½X¥i¥Hª½
±µ¦s¨úºô¸ô¬É±¥d¡C½Ð°Ñ¦Ò /etc/rc.network ³o
ÓÀɮשM manual pages ¨ú±o»P¨ä¥L¤£¦Pºô¸ôµ{¦¡¡C§ó¶i¤@¨Bªº¸ê°T¡G¦p
ªG§Aı±o§A§¹¥þ·d²V¤Fªº¸Ü¡A±zÀ³¸Ó§ä¤@¥»»P¨ä¥L BSD ¬ÛÃö§@·~¨t²Îºô¸ô
ºÞ²z¦³Ãö®Ñ¨Ó°Ñ¦Ò¡F°£¤F¤Ö¼ÆÅãµÛªº¤£¦P¥~¡AFreeBSD ªººô¸ôºÞ²z°ò¥»¤W©M
SunOS 4.0 ©M Ultrix ¬O¤@¼Ëªº¡C
§Ú¦p¦ó«Ø¥ß Ethernet aliases¡H
¦pªG§Aªº alias ¦ì§}¸ò§A¥Ø«eºô¸ô¤¶±ªº¦ì§}¦b¦P¤@Ó¤lºô¸ô¤Uªº
¸Ü¡A¥[¤J¤@Ó netmask 0xffffffff ¦b§Aªº
&man.ifconfig.8; command-line¡A½d¨Ò¦p¤U¡G
&prompt.root; ifconfig ed0 alias 192.0.2.2 netmask 0xffffffff
¤£µMªº¸Ü¡A´N¦p¦P¥[¤J¤@Ó·sªººô¸ô¦ì§}¤@¼Ë¿é¤J§Aªººô¸ô¦ì§}»P¤l
ºô¸ô¾B¸n¡G
&prompt.root; ifconfig ed0 alias 172.16.141.5 netmask 0xffffff00
§Ú¦p¦ó«ü©w§Úªº 3C503 ¨Ï¥Î¨ä¥L¤£¦Pªºªº network port¡H
¦pªG±z·Q¨Ï¥Î¨ä¥Lªº port¡A§A¥²¶·¦b &man.ifconfig.8; ªº©R¥O¤¤
«ü©wÃB¥~ªº°Ñ¼Æ¡C¤º©wªº port ¬O link0 ¡Cn¨Ï¥Î
AUI port ¥N´À BNC port ªº¸Ü¡A§ï¥Î link2 ¡C³o¨Ç
flags À³¸Ó§ïÅÜifconfig_* ªºÅܼƨӫü©w¡A §A¥i¥H¦b
/etc/rc.conf ³oÓÀɮ׸̱§ä¨ì (½Ð°Ñ¦Ò
&man.rc.conf.5;)¡C
¬°¤°»ò§Ú¦b¨Ï¥Î FreeBSD ªº NFS ®É¥X²{°ÝÃD¡H
§Ú̥Χt»W¤@ÂIªº»¡ªk¡A¬Y¨Ç PC ªººô¸ô¥d¤ñ¨ä¥Lªº¦n¡A³oºØª¬ªp¦b
³y¦¨ NFS ³oºØ¹ïºô¸ô±Ó·Pªºµ{¦¡¦³®É·|¥X²{°ÝÃD¡C
°Ñ¦Ò
the Handbook entry on NFS ¥HÀò±o³oÓ¥DÃDªº§ó¦h¸ê°T¡C
¬°¤°»ò§Ú¤£¯à NFS-mount Linux ªº¾÷¾¹¡H
¬Y¨Çª©¥»ªº Linux NFS µ{¦¡½X¥u±µ¨ü privileged port ªº
mount request¡F¸Õ¥Î³o¦æ«ü¥O¬Ý¬Ý
&prompt.root; mount -o -P linuxbox:/blah /mnt
¬°¤°»ò§Ú¤£¯à NFS-mount Sun ªº¾÷¾¹¡H
¶] SunOS 4.X ªº Sun ¤u§@¯¸¥u±µ¨ü¨Ó¦Û privileged port ªº
mount request¡F¸Õ¥Î³o¦æ«ü¥O¬Ý¬Ý
&prompt.root; mount -o -P sunbox:/blah /mnt
¬°¤°»ò mountd ¤@ª½°¥s»¡
can't change attributes ¦Ó¥B§Ú¤@ª½¬Ý¨ì
bad exports list ³oÓ°T®§¦b§Úªº FreeBSD NFS
¦øªA¾¹¤W¡H
³oÓ°ÝÃD³Ì±`µo¥Íªºì¦]¬O¦b©ó¤£¤F¸Ñ
/etc/exports ªº¥¿½T®æ¦¡¡C½Ð¸ÔŪ
&man.exports.5; ¥H¤Î¤â¥U¤¤Ãö©ó NFS ªº³¡¤À¡A¯S§O¬Oconfiguring
NFS ³o¤@¬q¡C
¬°¤°»ò§Ú¦b¨Ï¥Î PPP ³s½u¨ì NeXTStep ¾÷¾¹®É¦³°ÝÃD¡H
§â TCP extensions ¨ú®ø¡A³oÓ³]©w¦b
/etc/rc.conf ¸Ì±(°Ñ¦Ò &man.rc.conf.5;) §â
¥H¤U³oÓȳ]¦¨ NO¡G
tcp_extensions=NO
Xylogic ªº Annex ¥D¾÷¤]¦³¬Û¦Pªº°ÝÃD¡A±zn°µ¬Û¦Pªº×§ï¤~¯à³s
¤W³o¨Ç¥D¾÷¡C
§Ún«ç¼Ë¤~¯à§â IP multicast support ¥´¶}¡H
FreeBSD 2.0 ¥H«áªºª©¥»¤º©w³£¦³ ¤ä´© Multicast host ¾Þ§@¡C¦pªG
±z·Q±N±zªº¥D¾÷³]©w¦¨ multicast router ªº¸Ü¡A±z¥²¶·«·s compile ±z
ªº kernel¡A¥[¤J MROUTING ªº¿ï¶µ¡A¨Ã¥B°õ¦æ
&man.mrouted.8; FreeBSD 2.2 ¤Î¤§«áªºª©¥»·|¦b¶}¾÷®É°õ¦æ
&man.mrouted.8; ¦pªG¦b /etc/rc.conf ¤¤
mrouted_enable ³]©w¬° "YES"
MBONE ªº¦UºØ¤u¨ã¥i¥H¦b¥LÌ ports ¤U©ÒÄÝ¥s°µ mbone ¥Ø¿ý
¤¤§ä¨ì¡C¦pªG±z¦b§äµø°T·|ijªº¤u¨ã¦p vic ¥H¤Î
vat ªº¸Ü¡A¨ì¨ºÃä§ä§ä§a¡I
þ¨Çºô¸ô¥d¬O¨Ï¥Î DEC PCI chipset¡H
¥H¤U¬O Glen Foster gfoster@driver.nsta.org
´£¨Ñªº²M³æ¡G
Network cards based on the DEC PCI chipset
Vendor
Model
ASUS
PCI-L101-TB
Accton
ENI1203
Cogent
EM960PCI
Compex
ENET32-PCI
D-Link
DE-530
Dayna
DP1203, DP2100
DEC
DE435, DE450
Danpex
EN-9400P3
JCIS
Condor JC1260
Linksys
EtherPCI
Mylex
LNP101
SMC
EtherPower 10/100 (Model 9332)
SMC
EtherPower (Model 8432)
TopWare
TE-3500P
Znyx (2.2.x)
ZX312, ZX314, ZX342, ZX345, ZX346, ZX348
Znyx (3.x)
ZX345Q, ZX346Q, ZX348Q, ZX412Q, ZX414, ZX442, ZX444,
ZX474, ZX478, ZX212, ZX214 (10mbps/hd)
¬°¤°»òn¥Î FQDN ¤~¯à³s¨ì¨ä¥L¾÷¾¹¡H
§A¤]³\·|µo²{n³sªº¾÷¾¹¨ä¹ê¬O¦b¥t¤@Óºô°ì¡CÁ|Ó¨Ò¤l¡A°²³]§A¬O¦b
foo.bar.edu ³oÓºô°ì¤¤¡A·Qn³s¨ì¦b¤@¥x¥s mumble
ªº¥D¾÷¡A¥L¦b example.org ºô°ì¤U¡A
§A¥²¶·¥Î Fully-Qualified Domain Name mumble.example.org ¡A¦Ó¤£¬O¥u¥Î
mumble ¡C
¶Ç²Îªº BSD BIND resolver ¤¹³\¥Î³oºØ¤è¦¡¸Ñ¥X¾÷¾¹ªº¦ì§}¡A¦ý¬O
FreeBSD ¤ºªþ bind (see &man.named.8;)
ª©¥»¤º©w¤è¦¡¡A«h¬O°£¤F§A©Ò¦bªººô°ì¥H¥~¡A¤£¤ä´©¨ä¥L«D FQDN ªºÁY¼g¡C
©Ò¥H¦p mumble ¥²¶·¦b mumble.foo.example.org ¡A§_«h´N·|±qºô°ìªº³Ì©³
¼h¶}©l§ä¡C
³o©M¥ý«eªº°µªk¤£¦P¡A¤]´N¬O¤£¥Î
mumble.example.org ¡A©M
mumble.edu Ä~Äò·j´M¡C
¬Ý¤@¤U RFC 1535¡A¸Ì±¦³´£¨ì¬°¤°»ò¤§«eªº°µªk¤£¦n¡A¬Æ¦Üºâ¬OÓ¦w¥þ
º|¬}¡C
³o¸Ì¦³Ó¤£¿ùªº¸Ñªk, §A¥i¥H¥[¤J¤@¦æ
search foo.example.org example.org
instead of the previous
domain foo.example.org
¦b§Aªº /etc/resolv.conf Àɮפ¤ (½Ð°Ñ¦Ò
&man.resolv.conf.5;)¡C¦ý¬On½T©w·j´M¶¶§Ç¤£·|¹H¤Ï RFC 1535 ©Ò¿×ªº
boundary between local and public administration
¡C
¬°¤°»ò§Ú¦b³s½u®É¤@ª½¥X²{
Permission denied ªº¿ù»~°T®§¡H
¦pªG¦b½sĶ kernel ®É¥[¤J IPFIREWALL ¿ï¶µ¡A
½Ðª`·N 2.1.7R ¤º©w¬O©Úµ´©Ò¦³¥¼¸g®Ö㪺ºô¸ô«Ê¥](¦ý¦b¶}µo
2.1-STABLE ®É§ï±¼¤F)¡C
I¦pªG¤£¤p¤ß§Ë¿ù¤F firewall ªº³]©w¡A§A¥i¥H¥H
root °õ¦æ¥H¤U©R¥Oºô¸ô¥\¯à´N·|«ì´_¥¿±`¡G
&prompt.root; ipfw add 65534 allow all from any to any
¤]¥i¥H¦b /etc/rc.conf ¥[¤J
firewall_type="open" ªº¿ï¶µ¡C
¦pªG·Qª¾¹D¦p¦ó³]©w FreeBSD firewall¡A½Ð°Ñ¦Ò ¤â¥U¤¤¬ÛÃö³¹¸` ¡C
IPFW ·|³y¦¨¦h¤jªººô¸ô©µ¿ð¡H
½Ð°Ñ¦Ò¤â¥U¤¤ Firewalls ³¹¸`¡A¯S§O¬O
IPFW
Overhead & Optimization ³o¤@¬q¡C
¬°¤°»ò§Úªº ipfw fwd
redirect ³W«h±NªA°ÈÂà¦V¨ä¥L¾÷¾¹®ÉµLªk¥¿±`¹B§@¡H
¥i¯à¬O§A°£¤FÂà°e«Ê¥]¥H¥~ÁÙÃB¥~·Q¶i¦æ¦ì§}ÂàĶ
(network address translation, NAT)¡Afwd
³W«h©Ò¶i
¦æªº°Ê§@´N¦p¦P¦r±©Ò¥Ü¡F¶ÈÂà°e«Ê¥]¡A¥¦¨Ã¤£·|¥hקï«Ê¥]¤¤ªº¸ê®Æ¡C
°²³]§Ú̦³¦p¤Uªº³W«h¡G
01000 fwd 10.0.0.1 from any to foo 21
·í¤@Ó³q©¹¯S©w¥Ø¼Ð¦ì§} foo ªº«Ê¥]
°e¹F¥D¾÷®É¡A®Ú¾Ú³o±ø³W«h¡A«Ê¥]±N³QÂà°e¦Ü
10.0.0.1 ¡A¦ý¬O¥¦ªº¥Ø¼Ð¦ì§}«o¤´µM¬O
foo ¡I«Ê¥]ªº¥Ø¼Ð¦ì§}¨Ã
¨S¦³ §ó§ï¬°
10.0.0.1 ¡C¤j³¡¤Àªº¥D¾÷·|±N«Ê¥]¥á±ó¡A
¦]¬°¥L̨䣬O³oӥؼЦì§}¡C¦]¦¹¡A¨Ï¥Î fwd
³W«h
®É©¹©¹¤£¦p¨Ï¥ÎªÌ©Ò¹w´Áªº¨º¯ë¶¶§Q¡C³oºØ¦æ¬°¬O¨t²Î¯S©Ê¡A¦Ó«D¿ù»~¡C
°Ñ¦Ò Ãö©óªA°ÈÂà¦Vªº±`¨£°Ý
µª¶°¡A &man.natd.8; ¤â¥U¡A©ÎªÌ¬O¨Ï¥Î ports collection ¤¤³\
¦hªA°ÈÂà¦Vªº¤u¨ã¨Ó¥¿½Tªº§¹¦¨§A·Q¶i¦æªº¤u§@¡C
n¦p¦ó§â¹ï¬Y¥x¾÷¾¹ªººô¸ôªA°Èn¨D(service request)Âà¦V¨ì¥t¤@¥x¡H
¦b ports ¥Ø¿ýªºsysutils
¤ÀÃþ¤¤¦³Ó¥s
socket ªº®M¥ó¡A¥i¥HÀ°§AÂà¦V FTP ©Î¨ä¥LÃþ¦üªº
ºô¸ôªA°È¡C¥un§â¸Óºô¸ôªA°Èªº©R¥O§ï¦¨©I¥s socket §Y¥i¡A¦p¤U©Ò¥Ü¡G
ftp stream tcp nowait nobody /usr/local/bin/socket socket ftp.example.com ftp
¨ä¤¤ ftp.example.com »P
ftp ¤À§O¬O³QÂà¨ìªº¾÷¾¹©M port ¦WºÙ¡C
¨º¸Ì¥i¥H§ä¨ìºÞ²zÀW¼eªº¤u¨ã¡H
FreeBSD ¤W¦³¤T®MÀW¼eºÞ²z¤u¨ã¡G &man.dummynet.4; ¤w¸g¾ã¦X¶i¤J
FreeBSD ¨t²Î(§ó¸Ô²Óªº¥Î³~, &man.ipfw.4;); ALTQ
¥i¥H§K¶O¨Ï¥Î¡AEmerging Technologies
±À¥Xªº Bandwidth Manager «h¬O°Ó¥Î³nÅé¡C
«ç»ò·|¶]¥X
/dev/bpf0: device not configured ³oÓ°T®§¡H
§A°õ¦æ¤F¤@Ó»Ýn¬f§JµÜ«Ê¥]¹LÂo¾¹ (Berkeley Packet Filter) ªº
µ{¦¡ (&man.bpf.4;)¡A¦ý¬O§A¦b kernel ¤¤¨S¦³±Ò°Ê¥¦¡C§â¤U±³o¤@¦æ¥[
¤J kernel ³]©wÀɤ¤¡A½sĶ¤@Ó·sªº kernel¡G
pseudo-device bpf # Berkeley Packet Filter
¦b«·s¶}¾÷¤§«á¡AÁÙn°µ¥X device node¡A¦b
/dev ¤U°õ¦æ¡G
&prompt.root; sh MAKEDEV bpf0
¦pªG·Qn§ó¶i¤@¨Bª¾¹D¦p¦ó°µ¥X¦UºØ device node¡A½Ð°Ñ¾\ Handbook Ãö©ó¶gÃä¸`ÂIªº»¡©ú
¡C
§Ún«ç¼Ë¤~¯à±N Windows ¾÷¾¹¤¤ªººÏºÐ±¾¤J¨t²Î, ´N¹³ Linux ´£¨Ñ
ªº smbmount ¨º¼Ë¡H
¨Ï¥Î SMBFS ¤u¨ã²Õ¡C³o®M¤u¨ã²Õ¤¤
¥]§t¤F¤@¨t¦Cªº kernel קïÁÙ¦³¨Ï¥ÎªÌªº¤u¨ãµ{¦¡(userland programs)¡C
³o¨Çµ{¦¡©M¸ê°T¦b ports ¦¬Âä¤
net/smbfs ¤U¥i¥H§ä¨ì¡C¦b
4.5-RELEASE ¤§«áªºª©¥»«h¬O¨t²Î¤¤¤º«Ø¡C
§Ú¦b¨t²Î¤é»x¤¤µo²{¥H¤U°T®§¡G
icmp-response bandwidth limit 300/200 pps
¡A³o¬O
½¼¦Ì¸J¿|¡H
³o¬O¨t²Î®Ö¤ß§i¶D§A¦³¬Y¨Ç¬¡°Ê¤Þµo¥¦°e¥X¤ñ¥¦©Ò»{¬°À³¸Ó°e¥X§ó
¦hªº ICMP ©Î TCP «¸m°T®§ (RST)¡CICMP ¦^À³°T®§±`±`¬O¦]¬°¦³¤H¹Á
¸Õ³s±µ¥¼³Q¨Ï¥Îªº UDP ³q°T°ð¡CTCP «¸m°T®§«h¬O¦³¤H¹Á¸Õ³s±µ¥¼¶}
©ñ TCP ³q°T°ð³y¦¨ªºµ²ªG¡C¥H¤U³o¨Ç¬¡°Ê¥i¯à´N¬O³y¦¨³o¨Ç°T®§ªºì¦]¡G
¼É¤OªkªºªA°È²Õµ´§ðÀ»(DoS)¤è¦¡
(¬Û¸û©ó°w¹ï¯S®í®zÂI¨Ï¥Î³æ¤@«Ê¥]ªº§ðÀ»¤è¦¡)¡C
¤j¶qªº³q°T°ð±½´y(¬Û¸û©ó¶È¹Á¸Õ¤Ö¼Æªº±`¨£ªA°È³q°T°ð)¡C
¥X²{ªº¼Æ¦r¤¤²Ä¤@Ó¥Nªí®Ú¾Ú³o¨Ç¬y¶q kernel À³¸Ó°e¥Xªº«Ê¥]¼Æ¡A
²Ä¤GӼƦr«h¬O kernel ¥Ø«e¨î³Ì¤jµo°e¼Æ¡C§A¥i¥H§Q¥Î sysctl קï
net.inet.icmp.icmplim ÅܼÆȨӧó§ï³Ì¤jÈ¡CÁ|
¨Ò¨Ó»¡,¦pªG§Æ±æקï¨î¬° 300 packets per
second¡G
&prompt.root; sysctl -w net.inet.icmp.icmplim=300
¦pªG§A¤£·Q¦b¨t²Î¬ö¿ý¤¤¬Ý¨ì³o¨Ç°T®§¡A¦ý¬O¤´µM§Æ±æ«O«ù¦^À³ªº
¨îªº¸Ü¡A§A¥i¥H§Q¥Î sysctl קï
net.inet.icmp.icmplim_output ÅܼƨӨú®ø³o¨Ç°T
®§¡G
&prompt.root; sysctl -w net.inet.icmp.icmplim_output=0
³Ì«á¡A¦pªG§A·Q¨ú®ø³o¨Ç¨îªº¸Ü¡A§A¥i¥H³]©w
net.inet.icmp.icmplim (¦p¤W¨Ò©Ò¥Ü) ¬°
0 ¡C°ò©ó¤Wz²z¥Ñ¡A§Ṳ́£«Øij§A¨ú®ø³o¨Ç¨î¡C
³oÓ¿ù»~°T®§
arp: unknown hardware address format
¬O¤°»ò·N«ä¡H
³o¥Nªí§Aªº°Ï°ìºô¸ô³s½u¤W¦³¤@¨Ç³]³Æ¨Ï¥Î FreeBSD ¬Ý¤£À´±o MAC
®æ¦¡¡C³o³q±`¬O¥Nªí¦³¤H¦b§Aªº°Ï°ìºô¸ô¤W¶i¦æ¹êÅç¡A³Ì±`¨£ªº´N¬O
cable modem ªº³s½u¡C³o°T®§µL®`¡A¦Ó¥BÀ³¸Ó¤£¦Ü©ó¼vÅT¨ì FreeBSD ¥D
¾÷ªº®Ä¯à¡C
§Úèè¸Ë¦n CVSup ®M¥ó¡A¦ý¬O¦b¹Á¸Õ°õ¦æ®Éµo¥Í¤F¿ù»~¡An«ç»ò¿ì¡H
º¥ý¡A¬Ý¬Ý¿ù»~ªº°T®§¬O§_¦p¤U¡G
/usr/libexec/ld-elf.so.1: Shared object "libXaw.so.6" not found
³oºØ¿ù»~°T®§¥Nªí§A¥D¾÷¤W¦w¸Ëªº
net/cvsup ¨S¦³¥]§t
XFree86 ®M¥ó¡C¦pªG§A·Qn¨Ï¥Î
CVSup ¤º«Øªº¹Ï§Î¤¶±
GUI ªº¸Ü¡A§A»Ýn¦w¸Ë
XFree86 ¡C¦¹¥~¡A¦pªG§A¥u·Q¥H©R¥O¦C¤è
¦¡¨Ï¥Î CVSup ªº¸Ü¡A§AÀ³¸Ó¥ý²¾°£¤§«e
¦w¸Ëªº®M¥ó¡C¨Ã¦w¸Ë
net/cvsup-without-gui ³o®M
³nÅé¡C¦b FreeBSD ¤â¥U¤¤ CVSup
¬q¸¨¤¤¦³§ó¸Ô²Óªº»¡©ú¡C
Biing Jong
Lin
bjlin@stic.gov.tw
Security
FreeBSD 3.0 «áªºª©¥»¨Ï¥Î¤@Ó¯S®íªº BIND ª©¥»¡A³oÓª©¥»·|¨Ï
¥ÎÀH¾÷ªº°ª½s¸¹³q°T°ð¨Ó¦^À³¥~³¡ªº¬d¸ß¡C¦pªG§A¦]¬°n¾A¦X¨¾¤õÀðªº
³]©w©Î¬O³æ¯Âªº·QÅý¦Û¤v¬Ý¨ÓµÎªA¤@ÂI¦Ó·Q¥Î 53 ³q°T°ð¦^À³¥~³¡¬d¸ß¡A
¨º»ò§A¥i¥H¹Á¸Õ§ó§ï¥H¤UÀɮ׬ÛÃö¤º®e
/etc/namedb/named.conf ¡G
options {
query-source address * port 53;
};
§A¤]¥i¥H±N * §ó§ï¬°¯S©w IP address¡A
ÂÇ¥H¥[±j±±¨î±ø¥ó¡C
¶¶«K®¥³ß§A¡C¯à°÷Ū¨ú§A¨t²Î¤Wªº &man.sockstat.1; ³ø§i¨Ã¥Bª`·N
¤£¥¿±`ª¬ªp¬O¤@¥ó¦n¨Æ¡I
Sendmail °£¤F¦b¼Ð·Çªº³q°T°ð 25 ¥~¤]¦b³q°T°ð 587 ²âÅ¥¡I³o¬O«ç
»ò¦^¨Æ¡H
¸û·sª©¥»ªº Sendmail ¤ä´© mail submission ³o¶µ¥\¯à¡A¨Ã¥B¨Ï
¥Î³q°T°ð 587¡C³o¶µ¥\¯àÁÙ¨S¦³³Q¼sªx¤ä´©¦ý¬O¤ä´©ªº¼Æ¥Ø¥¿¦b¼Wªø
¤¤¡C
§Úµo²{¤F³oÓ UID 0 toor ±b¸¹¡A³o¬O¤°»ò
¸J¿|¡H§Ú³Q¶Â±¼¤F¶Ü¡H
©ñ¤ß¡Ctoor ¬O¤@Ó
alternative
ºÞ²zªÌ±b¸¹ (toor ¬O root ªºÂà¦V«÷ªk)¡C
¥H©¹¬O¸òÀH &man.bash.1; ¦w¸Ë¦Ó«Ø¨îªº¡A«á¨Ó«h¦¨¬°¨t²Î¤º©w«Ø¨îªº¤@
Ó±b¸¹¡C³oÓ±b¸¹±N¦ñÀH¤@Ó«D¼Ð·Çªº shell ´ú¸Õ¨Ï¥Î¡A Åý§A¤£»Ýn¥h
§ó§ï¨ì root ªº¤º«Ø shell¡C¦]¬°³o¨Ç¨ä¥Lªº shell
¨Ã¨S¦³¸òÀH¨t²Î¹w³]Ȧw¸Ë (Á|¨Ò¨Ó»¡¡A¬Y¨Ç¥Ñ ports ¦w¸Ëªº
shell package)¡A¦Ó³Q¤º©w¦w¸Ë¦b /usr/local/bin
¥Ø¿ý¤U¡A¦³¥i¯à¦s¦b¤£¦PªºÀɮרt²Î¤¤¡C ÕY root
ªº shell ³Q©ñ¦b /usr/local/bin ¡A¥B
/usr (©Î¬O¨ä¥L¥]§tµÛ
/usr/local/bin ³oÓ¤l¥Ø¿ýªºÀɮרt²Î)
¦]¬°¬Y¨Çì¦]¨Ã¨S¦³³Q¥¿±`ªº mount °_¨Óªº¸Ü¡Aroot
±NµLªk¥¿±`ªºµn¤J¨t²Î¶i¦æºû× (ÁöµM»¡§A«¶}¾÷¦¨³æ¤H¼Ò¦¡´N·|°Ý§An
¸ü¤JþÓ shell)¡C
¦³¨Ç¤H¨Ï¥Î toor ±b¸¹¶i¦æ¨C¤éªº
root ºûÅ@¤u§@¡A¦p¦¹¥i¥H¨Ï¥Î«D¼Ð·Çªº
shell¡A¦Ó root ¥i¥H«O¯d¼Ð·Ç shell¡A
¥H¦]À³³æ¤@¨Ï¥ÎªÌ¼Ò¦¡ (single user mode) ©Îºò«æª¬ªp³B²z¡C
¨Ì·Ó¨t²Î¤º©wÈ¡A§A±NµLªk¨Ï¥Î toor µn¤J¡A
¦]¬°³oÓ±b¸¹©|¥¼§ó§ï±K½X³]©w¡C¦]¦¹§A¦pªG§A·Q±Ò°Ê³oÓ±b¸¹¡A§A»Ýn
¨Ï¥Î root µn¤J¨t²Î¨Ã¥Bקï
toor ªº±K½X¡C
¬°¤°»ò suidperl µLªk¥¿±`¹B§@¡H
¦]¬°¬Y¨Ç¦w¥þªº¦Ò¡Asuidperl ¤º©wªº¦w¸Ë
¨Ã¨S¦³³]©w suid bit¡C¨t²ÎºÞ²zªÌ¥i¥H¨Ì·Ó¥H¤U©R¥O±Ò°Ê suid ³]©w¡C
&prompt.root; chmod u+s /usr/bin/suidperl
¦pªG§A·Qn¦b¥Ñ source ¤É¯Å®É suidperl ¤º©w
±Ò°Ê suid ¥\¯àªº¸Ü¡A½s¿è /etc/make.conf ¥[¤J
ENABLE_SUIDPERL=true µM«á°õ¦æ
make buildworld ¡C
PPP
I cannot make &man.ppp.8; work. What am I doing wrong?
You should first read the
&man.ppp.8;
man page and the
PPP section of the handbook . Enable logging with
the command
set log Phase Chat Connect Carrier lcp ipcp ccp command
This command may be typed at the
&man.ppp.8; command prompt or it may be
entered in the /etc/ppp/ppp.conf
configuration file (the start of the
default section is the best
place to put it). Make sure that
/etc/syslog.conf (see &man.syslog.conf.5;) contains the lines
!ppp
*.* /var/log/ppp.log
and that the file /var/log/ppp.log
exists. You can now find out a lot about what is going on
from the log file. Do not worry if it does not all make sense.
If you need to get help from someone, it may make sense to
them.
If your version of &man.ppp.8; does not understand the
set log command, you should download the
latest version . It will build on FreeBSD version
2.1.5 and higher.
Why does &man.ppp.8; hang when I run it?
This is usually because your hostname will not resolve.
The best way to fix this is to make sure that
/etc/hosts is consulted by your
resolver first by editing /etc/host.conf
and putting the hosts line first. Then,
simply put an entry in /etc/hosts for
your local machine. If you have no local network, change your
localhost line:
127.0.0.1 foo.bar.com foo localhost
Otherwise, simply add another entry for your host.
Consult the relevant man pages for more details.
You should be able to successfully
ping -c1 `hostname` when you are done.
Why will &man.ppp.8; not dial in -auto
mode?
First, check that you have got a default route. By running
netstat -rn (see &man.netstat.1;), you should see two entries like this:
Destination Gateway Flags Refs Use Netif Expire
default 10.0.0.2 UGSc 0 0 tun0
10.0.0.2 10.0.0.1 UH 0 0 tun0
This is assuming that you have used the addresses from the
handbook, the man page or from the ppp.conf.sample file.
If you do not have a default route, it may be because you are
running an old version of &man.ppp.8;
that does not understand the word HISADDR
in the ppp.conf file. If your version of
&man.ppp.8; is from before FreeBSD
2.2.5, change the
add 0 0 HISADDR
line to one saying
add 0 0 10.0.0.2
Another reason for the default route line being missing
is that you have mistakenly set up a default router in your
/etc/rc.conf (see &man.rc.conf.5;) file (this file was called
/etc/sysconfig prior to release 2.2.2),
and you have omitted the line saying
delete ALL
from ppp.conf . If this is the case,
go back to the
Final system configuration section of the
handbook.
What does No route to host mean?
This error is usually due to a missing
MYADDR:
delete ALL
add 0 0 HISADDR
section in your /etc/ppp/ppp.linkup
file. This is only necessary if you have a dynamic IP address
or do not know the address of your gateway. If you are using
interactive mode, you can type the following after entering
packet mode (packet mode is
indicated by the capitalized PPP in the
prompt):
delete ALL
add 0 0 HISADDR
Refer to the
PPP and Dynamic IP addresses section of the handbook
for further details.
Why does my connection drop after about 3 minutes?
The default PPP timeout is 3 minutes. This can be
adjusted with the line
set timeout NNN
where NNN is the number of
seconds of inactivity before the connection is closed. If
NNN is zero, the connection is never
closed due to a timeout. It is possible to put this command in
the ppp.conf file, or to type it at the
prompt in interactive mode. It is also possible to adjust it on
the fly while the line is active by connecting to
ppp s server socket using
&man.telnet.1; or &man.pppctl.8;.
Refer to the
&man.ppp.8; man
page for further details.
Why does my connection drop under heavy load?
If you have Link Quality Reporting (LQR) configured,
it is possible that too many LQR packets are lost between
your machine and the peer. Ppp deduces that the line must
therefore be bad, and disconnects. Prior to FreeBSD version
2.2.5, LQR was enabled by default. It is now disabled by
default. LQR can be disabled with the line
disable lqr
Why does my connection drop after a random amount of
time?
Sometimes, on a noisy phone line or even on a line with
call waiting enabled, your modem may hang up because it
thinks (incorrectly) that it lost carrier.
There is a setting on most modems for determining how
tolerant it should be to temporary losses of carrier. On a
USR Sportster for example, this is measured by the S10
register in tenths of a second. To make your modem more
forgiving, you could add the following send-expect sequence
to your dial string:
set dial "...... ATS10=10 OK ......"
Refer to your modem manual for details.
Why does my connection hang after a random amount of
time?
Many people experience hung connections with no apparent
explanation. The first thing to establish is which side of
the link is hung.
If you are using an external modem, you can simply try
using &man.ping.8; to see if the
TD light is flashing when you transmit data.
If it flashes (and the RD light does not),
the problem is with the remote end. If TD
does not flash, the problem is local. With an internal modem,
you will need to use the set server command in
your ppp.conf file. When the hang occurs,
connect to &man.ppp.8; using &man.pppctl.8;. If your network connection
suddenly revives (PPP was revived due to the activity on the
diagnostic socket) or if you cannot connect (assuming the
set socket command succeeded at startup
time), the problem is local. If you can connect and things are
still hung, enable local async logging with set log
local async and use &man.ping.8; from
another window or terminal to make use of the link. The async
logging will show you the data being transmitted and received
on the link. If data is going out and not coming back, the
problem is remote.
Having established whether the problem is local or remote,
you now have two possibilities:
The remote end is not responding. What can I do?
There is very little you can do about this. Most ISPs
will refuse to help if you are not running a Microsoft OS.
You can enable lqr in your
ppp.conf file, allowing &man.ppp.8; to detect
the remote failure and hang up, but this detection is
relatively slow and therefore not that useful. You may want to
avoid telling your ISP that you are running user-PPP...
First, try disabling all local compression by adding the
following to your configuration:
disable pred1 deflate deflate24 protocomp acfcomp shortseq vj
deny pred1 deflate deflate24 protocomp acfcomp shortseq vj
Then reconnect to ensure that this makes no difference.
If things improve or if the problem is solved completely,
determine which setting makes the difference through trial
and error. This will provide good ammunition when you contact
your ISP (although it may make it apparent that you are not
running a Microsoft product).
Before contacting your ISP, enable async logging locally
and wait until the connection hangs again. This may use up
quite a bit of disk space. The last data read from the port
may be of interest. It is usually ascii data, and may even
describe the problem
(Memory fault, core dumped
?).
If your ISP is helpful, they should be able to enable
logging on their end, then when the next link drop occurs,
they may be able to tell you why their side is having a
problem. Feel free to send the details to &a.brian;, or
even to ask your ISP to contact me directly.
&man.ppp.8; has hung. What can I do?
Your best bet here is to rebuild &man.ppp.8; by adding
CFLAGS+=-g and STRIP=
to the end of the Makefile, then doing a
make clean && make && make
install . When &man.ppp.8; hangs, find the &man.ppp.8; process id
with ps ajxww | fgrep ppp and run
gdb ppp PID .
From the gdb prompt, you can then use bt
to get a stack trace.
Send the results to brian@Awfulhak.org .
Why does nothing happen after the Login OK!
message?
Prior to FreeBSD version 2.2.5, once the link was
established, &man.ppp.8;
would wait for the peer to initiate the Line Control Protocol
(LCP). Many ISPs will not initiate negotiations and expect
the client to do so. To force
&man.ppp.8; to initiate the LCP, use the
following line:
set openmode active
It usually does no
harm if both sides initiate negotiation, so openmode is now
active by default. However, the next section explains when
it does do some harm.
I keep seeing errors about magic being the same. What does
it mean?
Occasionally, just after connecting, you may see messages
in the log that say magic is the same
.
Sometimes, these messages are harmless, and sometimes one side
or the other exits. Most PPP implementations cannot survive
this problem, and even if the link seems to come up, you will see
repeated configure requests and configure acknowledgments in
the log file until &man.ppp.8; eventually gives up and closes the
connection.
This normally happens on server machines with slow disks
that are spawning a getty on the port, and executing &man.ppp.8; from
a login script or program after login. I have also heard reports
of it happening consistently when using slirp. The reason is
that in the time taken between &man.getty.8; exiting and &man.ppp.8; starting,
the client-side &man.ppp.8; starts sending Line Control Protocol (LCP)
packets. Because ECHO is still switched on for the port on
the server, the client &man.ppp.8; sees these packets
reflect
back.
One part of the LCP negotiation is to establish a magic
number for each side of the link so that
reflections
can be detected. The protocol says
that when the peer tries to negotiate the same magic number, a
NAK should be sent and a new magic number should be chosen.
During the period that the server port has ECHO turned on, the
client &man.ppp.8; sends LCP packets, sees the same magic in the
reflected packet and NAKs it. It also sees the NAK reflect
(which also means &man.ppp.8; must change its magic). This produces a
potentially enormous number of magic number changes, all of
which are happily piling into the server's tty buffer. As soon
as &man.ppp.8; starts on the server, it is flooded with magic number
changes and almost immediately decides it has tried enough to
negotiate LCP and gives up. Meanwhile, the client, who no
longer sees the reflections, becomes happy just in time to see
a hangup from the server.
This can be avoided by allowing the peer to start
negotiating with the following line in your ppp.conf
file:
set openmode passive
This tells &man.ppp.8; to wait for the server to initiate LCP
negotiations. Some servers however may never initiate
negotiations. If this is the case, you can do something
like:
set openmode active 3
This tells &man.ppp.8; to be passive for 3 seconds, and then to
start sending LCP requests. If the peer starts sending
requests during this period, &man.ppp.8; will immediately respond
rather than waiting for the full 3 second period.
LCP negotiations continue until the connection is
closed. What is wrong?
There is currently an implementation mis-feature in
&man.ppp.8; where it does not associate
LCP, CCP & IPCP responses with their original requests. As
a result, if one PPP
implementation is more than 6 seconds slower than the other
side, the other side will send two additional LCP configuration
requests. This is fatal.
Consider two implementations,
A and
B . A starts
sending LCP requests immediately after connecting and
B takes 7 seconds to start. When
B starts, A
has sent 3 LCP REQs. We are assuming the line has ECHO switched
off, otherwise we would see magic number problems as described in
the previous section. B sends a
REQ, then an ACK to the first of
A 's REQs. This results in
A entering the OPENED
state and sending and ACK (the first) back to
B . In the meantime,
B sends back two more ACKs in response to
the two additional REQs sent by A
before B started up.
B then receives the first ACK from
A and enters the
OPENED state.
A receives the second ACK from
B and goes back to the
REQ-SENT state, sending another (forth) REQ
as per the RFC. It then receives the third ACK and enters the
OPENED state. In the meantime,
B receives the forth REQ from
A , resulting in it reverting to the
ACK-SENT state and sending
another (second) REQ and (forth) ACK as per the RFC.
A gets the REQ, goes into
REQ-SENT and sends another REQ. It
immediately receives the following ACK and enters
OPENED .
This goes on until one side figures out that they are
getting nowhere and gives up.
The best way to avoid this is to configure one side to be
passive - that is, make one side
wait for the other to start negotiating. This can be done
with the
set openmode passive
command. Care should be taken with this option. You
should also use the
set stopped N
command to limit the amount of time that
&man.ppp.8; waits for the peer to begin
negotiations. Alternatively, the
set openmode active N
command (where N is the
number of seconds to wait before starting negotiations) can be
used. Check the manual page for details.
Why does &man.ppp.8; lock up shortly after connection?
Prior to version 2.2.5 of FreeBSD, it was possible that
your link was disabled shortly after connection due to
&man.ppp.8; mis-handling Predictor1
compression negotiation. This would only happen if both sides
tried to negotiate different Compression Control Protocols
(CCP). This problem is now corrected, but if you are still
running an old version of &man.ppp.8;
the problem can be circumvented with the line
disable pred1
Why does &man.ppp.8; lock up when I shell out to test it?
When you execute the shell or
! command, &man.ppp.8; executes a
shell (or if you have passed any arguments,
&man.ppp.8; will execute those arguments). Ppp will
wait for the command to complete before continuing. If you
attempt to use the PPP link while running the command, the link
will appear to have frozen. This is because
&man.ppp.8; is waiting for the command to
complete.
If you wish to execute commands like this, use the
!bg command instead. This will execute
the given command in the background, and &man.ppp.8; can continue to
service the link.
Why does &man.ppp.8; over a null-modem cable never exit?
There is no way for &man.ppp.8; to
automatically determine that a direct connection has been
dropped. This is due to the lines that are used in a
null-modem serial cable. When using this sort of connection,
LQR should always be enabled with the line
enable lqr
LQR is accepted by default if negotiated by the peer.
Why does &man.ppp.8; dial for no reason in -auto mode?
If &man.ppp.8; is dialing
unexpectedly, you must determine the cause, and set up Dial
filters (dfilters) to prevent such dialing.
To determine the cause, use the following line:
set log +tcp/ip
This will log all traffic through the connection. The
next time the line comes up unexpectedly, you will see the
reason logged with a convenient timestamp next to it.
You can now disable dialing under these circumstances.
Usually, this sort of problem arises due to DNS lookups. To
prevent DNS lookups from establishing a connection (this will
not prevent
&man.ppp.8; from passing the packets
through an established connection), use the following:
set dfilter 1 deny udp src eq 53
set dfilter 2 deny udp dst eq 53
set dfilter 3 permit 0/0 0/0
This is not always suitable, as it will effectively break
your demand-dial capabilities - most programs will need a DNS
lookup before doing any other network related things.
In the DNS case, you should try to determine what is
actually trying to resolve a host name. A lot of the time,
&man.sendmail.8; is the culprit. You should make sure that
you tell sendmail not to do any DNS lookups in its
configuration file. See the section on
Mail Configuration for details
on how to create your own configuration file and what should
go into it. You may also want to add the following line to
your .mc file:
define(`confDELIVERY_MODE', `d')dnl
This will make sendmail queue everything until the queue
is run (usually, sendmail is invoked with
-bd -q30m , telling it to run the queue every
30 minutes) or until a sendmail -q is done
(perhaps from your ppp.linkup file).
What do these CCP errors mean?
I keep seeing the following errors in my log file:
CCP: CcpSendConfigReq
CCP: Received Terminate Ack (1) state = Req-Sent (6)
This is because &man.ppp.8; is trying to negotiate Predictor1
compression, and the peer does not want to negotiate any
compression at all. The messages are harmless, but if you
wish to remove them, you can disable Predictor1 compression
locally too:
disable pred1
Why does &man.ppp.8; lock up during file transfers with IO
errors?
Under FreeBSD 2.2.2 and before, there was a bug in the
tun driver that prevents incoming packets of a size larger
than the tun interface's MTU size. Receipt of a packet
greater than the MTU size results in an IO error being logged
via syslogd.
The PPP specification says that an MRU of 1500 should
always be accepted as a minimum,
despite any LCP negotiations, therefore it is possible that
should you decrease the MTU to less than 1500, your ISP will
transmit packets of 1500 regardless, and you will tickle this
non-feature - locking up your link.
The problem can be circumvented by never setting an MTU of
less than 1500 under FreeBSD 2.2.2 or before.
Why does &man.ppp.8; not log my connection speed?
In order to log all lines of your modem
conversation
, you must enable the
following:
set log +connect
This will make &man.ppp.8; log
everything up until the last requested expect
string.
If you wish to see your connect speed and are using PAP
or CHAP (and therefore do not have anything to
chat
after the CONNECT in the dial script - no
set login script), you must make sure that
you instruct &man.ppp.8; to expect
the whole CONNECT
line, something like this:
set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 4 \
\"\" ATZ OK-ATZ-OK ATDT\\T TIMEOUT 60 CONNECT \\c \\n"
Here, we get our CONNECT, send nothing, then expect a
line-feed, forcing &man.ppp.8; to read
the whole CONNECT response.
Why does &man.ppp.8; ignore the \ character
in my chat script?
Ppp parses each line in your config files so that it can
interpret strings such as
set phone "123 456 789" correctly (and
realize that the number is actually only
one argument. In order to specify a
" character, you must escape it
using a backslash (\ ).
When the chat interpreter parses each argument, it
re-interprets the argument in order to find any special
escape sequences such as \P or
\T (see the man page). As a result of this
double-parsing, you must remember to use the correct number of
escapes.
If you wish to actually send a \
character to (say) your modem, you would need something
like:
set dial "\"\" ATZ OK-ATZ-OK AT\\\\X OK"
resulting in the following sequence:
ATZ
OK
AT\X
OK
or
set phone 1234567
set dial "\"\" ATZ OK ATDT\\T"
resulting in the following sequence:
ATZ
OK
ATDT1234567
Why does &man.ppp.8; get a seg-fault, but I see no
ppp.core file?
Ppp (or any other program for that matter) should never
dump core. Because &man.ppp.8; runs with an effective user id of 0,
the operating system will not write &man.ppp.8;'s core image to disk
before terminating it. If, however &man.ppp.8;
is actually terminating due to a
segmentation violation or some other signal that normally
causes core to be dumped, and
you are sure you are using the latest version (see the start of
this section), then you should do the following:
&prompt.user; tar xfz ppp-*.src.tar.gz
&prompt.user; cd ppp*/ppp
&prompt.user; echo STRIP= >>Makefile
&prompt.user; echo CFLAGS+=-g >>Makefile
&prompt.user; make clean all
&prompt.user; su
&prompt.root; make install
&prompt.root; chmod 555 /usr/sbin/ppp
You will now have a debuggable version of &man.ppp.8; installed.
You will have to be root to run &man.ppp.8; as all of its privileges
have been revoked. When you start &man.ppp.8;, take a careful note
of what your current directory was at the time.
Now, if and when &man.ppp.8; receives the segmentation violation,
it will dump a core file called ppp.core . You should then do
the following:
&prompt.user; su
&prompt.root; gdb /usr/sbin/ppp ppp.core
(gdb) bt
.....
(gdb) f 0
....
(gdb) i args
....
(gdb) l
.....
All of this information should be given alongside your
question, making it possible to diagnose the problem.
If you are familiar with gdb, you may wish to find out some
other bits and pieces such as what actually caused the dump and
the addresses & values of the relevant variables.
Why does the process that forces a dial in auto mode never
connect?
This was a known problem with
&man.ppp.8; set up to negotiate a
dynamic local IP number with the peer in auto mode. It is
fixed in the latest version - search the man page for
iface .
The problem was that when that initial program calls
&man.connect.2;, the IP number of the tun interface is assigned
to the socket endpoint. The kernel creates the first outgoing
packet and writes it to the tun device.
&man.ppp.8; then reads the packet and
establishes a connection. If, as a result of
&man.ppp.8;'s dynamic IP assignment, the
interface address is changed, the original socket endpoint will
be invalid. Any subsequent packets sent to the peer will
usually be dropped. Even if they are not, any responses will
not route back to the originating machine as the IP number is
no longer owned by that machine.
There are several theoretical ways to approach this
problem. It would be nicest if the peer would re-assign the
same IP number if possible :-)
The current version of &man.ppp.8; does
this, but most other implementations do not.
The easiest method from our side would be to never change
the tun interface IP number, but instead to change all outgoing
packets so that the source IP number is changed from the
interface IP to the negotiated IP on the fly. This is
essentially what the iface-alias option in
the latest version of &man.ppp.8; is
doing (with the help of
&man.libalias.3; and &man.ppp.8;'s -nat switch) -
it is maintaining all previous interface addresses and NATing
them to the last negotiated address.
Another alternative (and probably the most reliable) would
be to implement a system call that changes all bound sockets
from one IP to another. &man.ppp.8; would
use this call to modify the sockets of all existing programs
when a new IP number is negotiated. The same system call could
be used by dhcp clients when they are forced to re-bind() their
sockets.
Yet another possibility is to allow an interface to be
brought up without an IP number. Outgoing packets would be
given an IP number of 255.255.255.255 up until the first
SIOCAIFADDR ioctl is done. This would result in fully binding
the socket. It would be up to &man.ppp.8;
to change the source IP number, but only if it is set to
255.255.255.255, and only the IP number and IP checksum would
need to change. This, however is a bit of a hack as the kernel
would be sending bad packets to an improperly configured
interface, on the assumption that some other mechanism is
capable of fixing things retrospectively.
Why do most games not work with the -nat switch?
The reason games and the like do not work when libalias
is in use is that the machine on the outside will try to open a
connection or send (unsolicited) UDP packets to the machine on
the inside. The NAT software does not know that it should send
these packets to the interior machine.
To make things work, make sure that the only thing
running is the software that you are having problems with, then
either run tcpdump on the tun interface of the gateway or
enable &man.ppp.8; tcp/ip logging (set log +tcp/ip )
on the gateway.
When you start the offending software, you should see
packets passing through the gateway machine. When something
comes back from the outside, it will be dropped (that is the
problem). Note the port number of these packets then shut down
the offending software. Do this a few times to see if the port
numbers are consistent. If they are, then the following line in
the relevant section of /etc/ppp/ppp.conf will make the
software functional:
nat port proto internalmachine :port port
where proto is either
tcp or udp ,
internalmachine is the machine that
you want the packets to be sent to and
port is the destination port number
of the packets.
You will not be able to use the software on other machines
without changing the above command, and running the software
on two internal machines at the same time is out of the question
- after all, the outside world is seeing your entire internal
network as being just a single machine.
If the port numbers are not consistent, there are three
more options:
Submit support in
libalias. Examples of special cases
can be found
in /usr/src/lib/libalias/alias_*.c
(alias_ftp.c is a good prototype). This
usually involves reading certain recognised outgoing packets,
identifying the instruction that tells the outside machine to
initiate a connection back to the internal machine on a
specific (random) port and setting up a route
in
the alias table so that the subsequent packets know where to
go.
This is the most difficult solution, but it is the best
and will make the software work with multiple machines.
Use a proxy. The
application may support socks5 for example, or (as in the
cvsup
case) may have a passive
option that avoids ever requesting that the peer open
connections back to the local machine.
Redirect everything to
the internal machine using nat addr . This
is the sledge-hammer approach.
Has anybody made a list of useful port numbers?
Not yet, but this is intended to grow into such a list
(if any interest is shown). In each example,
internal should be replaced with
the IP number of the machine playing the game.
Asheron's Call
nat port udp
internal
:65000 65000
Manually change the port number within the game to
65000. If you have got a number of machines that you wish
to play on assign a unique port number for each (i.e.
65001, 65002, etc) and add a nat port
line for each one.
Half Life
nat port udp
internal :27005
27015
PCAnywhere 8.0
nat port udp
internal :5632
5632
nat port tcp
internal :5631
5631
Quake
nat port udp
internal :6112
6112
Alternatively, you may want to take a look at
www.battle.net for Quake proxy support.
Quake 2
nat port udp
internal :27901
27910
nat port udp
internal :60021
60021
nat port udp
internal :60040
60040
Red Alert
nat port udp
internal :8675
8675
nat port udp
internal :5009
5009
What are FCS errors?
FCS stands for F rame
C heck
S equence. Each PPP packet
has a checksum attached to ensure that the data being
received is the data being sent. If the FCS of an incoming
packet is incorrect, the packet is dropped and the HDLC FCS
count is increased. The HDLC error values can be displayed
using the show hdlc command.
If your link is bad (or if your serial driver is dropping
packets), you will see the occasional FCS error. This is not
usually worth worrying about although it does slow down the
compression protocols substantially. If you have an external
modem, make sure your cable is properly shielded from
interference - this may eradicate the problem.
If your link freezes as soon as you have connected and you
see a large number of FCS errors, this may be because your link
is not 8 bit clean. Make sure your modem is not using software
flow control (XON/XOFF). If your datalink
must use software flow control, use the
command set accmap 0x000a0000 to tell
&man.ppp.8; to escape the ^Q and
^S characters.
Another reason for seeing too many FCS errors may be that
the remote end has stopped talking PPP . You
may want to enable async logging at this
point to determine if the incoming data is actually a login or
shell prompt. If you have a shell prompt at the remote end,
it is possible to terminate &man.ppp.8; without dropping the line by
using the close lcp command (a following
term command will reconnect you to the shell
on the remote machine.
If nothing in your log file indicates why the link might
have been terminated, you should ask the remote administrator
(your ISP?) why the session was terminated.
Why do MacOS and Windows 98 connections freeze when
running PPPoE on the gateway?
Thanks to Michael Wozniak
mwozniak@netcom.ca for figuring this out and
Dan Flemming danflemming@mac.com for the Mac
solution:
This is due to what is called a Black Hole
router. MacOS and Windows 98 (and maybe other Microsoft OSs)
send TCP packets with a requested segment size too big to fit
into a PPPoE frame (MTU is 1500 by default for Ethernet)
and have the do not
fragment
bit set (default of TCP) and the Telco router
is not sending ICMP must fragment
back to the
www site you are trying to load. (Alternatively, the router is
sending the ICMP packet correctly, but the firewall at the www
site is dropping it.) When the www server is sending
you frames that do not fit into the PPPoE pipe the Telco router
drops them on the floor and your page does not load (some
pages/graphics do as they are smaller than a MSS.) This seems
to be the default of most Telco PPPoE configurations (if only
they knew how to program a router... sigh...)
One fix is to use regedit on your 95/98 boxes to add the
following registry entry...
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\NetTrans\0000\MaxMTU
It should be a string with a value 1436
, as
some ADSL routers are reported to be unable to deal with packets
larger than this. This registry key has been changed to
Tcpip\Parameters\Interfaces\ID for adapter \MTU
in Windows 2000 and becomes a DWORD.
Refer to the Microsoft Knowledge Base documents Q158474
- Windows TCPIP Registry Entries and Q120642
- TCPIP & NBT Configuration Parameters for Windows
NT for more information on changing Windows MTU to
work with a NAT router.
Another regedit possibility under Windows 2000 is to
set the
Tcpip\Parameters\Interfaces\ID for
adapter \EnablePMTUBHDetect DWORD
to 1 as mentioned in the Microsoft document 120642
mentioned above.
Unfortunately, MacOS does not provide an interface for
changing TCP/IP settings. However, there is commercial software
available, such as OTAdvancedTuner (OT for OpenTransport, the
MacOS TCP/IP stack) by Sustainable Softworks ,
that will allow users to customize TCP/IP settings. MacOS NAT
users should select ip_interface_MTU from
the drop-down menu, enter 1450 instead of
1500 in the box, click the box next to
Save as Auto Configure , and click
Make Active .
The latest version of &man.ppp.8;
(2.3 or greater) has an enable tcpmssfixup
command that will automatically adjust the MSS to an appropriate
value. This facility is enabled by default. If you are stuck
with an older version of &man.ppp.8;, you
may want to look at the tcpmssd
port.
None of this helps - I am desperate! What can I do?
If all else fails, send as much information as you can,
including your config files, how you are starting
&man.ppp.8;, the relevant parts of your
log file and the output of the netstat -rn
command (before and after connecting) to the &a.questions; or
the
comp.unix.bsd.freebsd.misc news group, and someone
should point you in the right direction.
Serial Communications
This section answers common questions about serial
communications with FreeBSD. PPP and SLIP are covered in the
section.
How do I tell if FreeBSD found my serial ports?
As the FreeBSD kernel boots, it will probe for the serial
ports in your system for which the kernel was configured.
You can either watch your system closely for the messages it
prints or run the command
&prompt.user; dmesg | grep sio
after your system is up and running.
Here is some example output from the above command:
sio0 at 0x3f8-0x3ff irq 4 on isa
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
This shows two serial ports. The first is on irq 4, is
using port address 0x3f8 , and has a
16550A-type UART chip. The second uses the same kind of chip
but is on irq 3 and is at port address 0x2f8 .
Internal modem cards are treated just like serial ports---except
that they always have a modem attached
to the
port.
The GENERIC kernel includes support
for two serial ports using the same irq and port address
settings in the above example. If these settings are not
right for your system, or if you have added modem cards or have
more serial ports than your kernel is configured for, just
reconfigure your kernel. See section
about building a kernel for
more details.
How do I tell if FreeBSD found my modem cards?
Refer to the answer to the previous question.
I just upgraded to 2.0.5 and my
tty0X
are missing! How do I solve this problem?
Do not worry, they have been merged with the
ttydX devices. You will have to change
any old configuration files you have, though.
How do I access the serial ports on FreeBSD?
The third serial port,
sio2
(see &man.sio.4;, known as COM3 in DOS), is on /dev/cuaa2
for dial-out devices, and on /dev/ttyd2
for dial-in devices. What is the difference between these two
classes of devices?
You use ttydX for dial-ins. When
opening /dev/ttydX in blocking mode, a
process will wait for the corresponding
cuaaX device to become inactive, and then
wait for the carrier detect line to go active. When you open
the cuaaX device, it makes sure the serial
port is not already in use by the ttydX
device. If the port is available, it steals
it
from the ttydX device. Also, the
cuaaX device does not care about carrier
detect. With this scheme and an auto-answer modem, you can have
remote users log in and you can still dial out with the same
modem and the system will take care of all the
conflicts.
How do I enable support for a multiport serial
card?
Again, the section on kernel configuration provides
information about configuring your kernel. For a multiport
serial card, place an &man.sio.4; line
for each serial port on the card in the kernel configuration
file. But place the irq and vector specifiers on only one of
the entries. All of the ports on the card should share one irq.
For consistency, use the last serial port to specify the irq.
Also, specify the COM_MULTIPORT
option.
The following example is for an AST 4-port serial card on
irq 7:
options "COM_MULTIPORT"
device sio4 at isa? port 0x2a0 tty flags 0x781
device sio5 at isa? port 0x2a8 tty flags 0x781
device sio6 at isa? port 0x2b0 tty flags 0x781
device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr
The flags indicate that the master port has minor number 7
(0x700 ), diagnostics enabled during probe
(0x080 ), and all the ports share an irq
(0x001 ).
Can FreeBSD handle multiport serial cards sharing
irqs?
Not yet. You will have to use a different irq for each
card.
Can I set the default serial parameters for a
port?
The ttydX (or
cuaaX ) device is the regular device
you will want to open for your applications. When a process
opens the device, it will have a default set of terminal I/O
settings. You can see these settings with the command
&prompt.root; stty -a -f /dev/ttyd1
When you change the settings to this device, the settings
are in effect until the device is closed. When it is reopened,
it goes back to the default set. To make changes to the
default set, you can open and adjust the settings of the
initial state
device. For example, to turn on
CLOCAL mode, 8 bits, and
XON/XOFF flow control by default for
ttyd5, do:
&prompt.root; stty -f /dev/ttyid5 clocal cs8 ixon ixoff
A good place to do this is in
/etc/rc.serial . Now, an application will
have these settings by default when it opens
ttyd5 . It can still change these settings
to its liking, though.
You can also prevent certain settings from being changed
by an application by making adjustments to the
lock state
device. For example, to lock the
speed of ttyd5 to 57600 bps, do
&prompt.root; stty -f /dev/ttyld5 57600
Now, an application that opens ttyd5
and tries to change the speed of the port will be stuck with
57600 bps.
Naturally, you should make the initial state and lock state
devices writable only by root . The
&man.MAKEDEV.8;
script does NOT do this when it creates the
device entries.
How can I enable dialup logins on my modem?
So you want to become an Internet service provider, eh?
First, you will need one or more modems that can auto-answer.
Your modem will need to assert carrier-detect when it detects a
carrier and not assert it all the time. It will need to hang up
the phone and reset itself when the data terminal ready
(DTR ) line goes from on to off. It should
probably use RTS/CTS flow control or no
local flow control at all. Finally, it must use a constant
speed between the computer and itself, but (to be nice to your
callers) it should negotiate a speed between itself and the
remote modem.
For many Hayes command-set--compatible modems, this
command will make these settings and store them in
nonvolatile memory:
AT &C1 &D3 &K3 &Q6 S0=1 &W
See the section on sending AT
commands below for information on how to make these
settings without resorting to an MS-DOS terminal program.
Next, make an entry in
/etc/ttys (see &man.ttys.5;) for the modem. This file lists all the ports
on which the operating system will await logins. Add a line
that looks something like this:
ttyd1 "/usr/libexec/getty std.57600" dialup on insecure
This line indicates that the second serial port
(/dev/ttyd1 ) has a modem connected
running at 57600 bps and no parity
(std.57600 , which comes from the file
/etc/gettytab , see &man.gettytab.5;).
The terminal type for this port is dialup .
The port is on and is
insecure ---meaning root
logins on the port are not allowed. For dialin ports like this one,
use the ttydX
entry.
It is common practice to use dialup as
the terminal type. Many users set up in their .profile or
.login files a prompt for the actual terminal type if the
starting type is dialup. The example shows the port as
insecure. To become root on this port, you
have to login as a regular user, then &man.su.1; to become
root . If you use secure
then root can login in directly.
After making modifications to
/etc/ttys , you need to send a hangup or
HUP signal to the
&man.init.8; process:
&prompt.root; kill -HUP 1
This forces the &man.init.8; process to reread
/etc/ttys . The init process will then start getty
processes on all on ports. You can find
out if logins are available for your port by typing
&prompt.user; ps -ax | grep '[t]tyd1'
You should see something like:
747 ?? I 0:00.04 /usr/libexec/getty std.57600 ttyd1
How can I connect a dumb terminal to my FreeBSD
box?
If you are using another computer as a terminal into your
FreeBSD system, get a null modem cable to go between the two
serial ports. If you are using an actual terminal, see its
accompanying instructions.
Then, modify
/etc/ttys (see &man.ttys.5;), like above. For example, if you are
hooking up a WYSE-50 terminal to the fifth serial port,
use an entry like this:
ttyd4 "/usr/libexec/getty std.38400" wyse50 on secure
This example shows that the port on
/dev/ttyd4 has a wyse50 terminal
connected at 38400 bps with no parity
(std.38400 from
/etc/gettytab , see &man.gettytab.5;) and root logins are
allowed (secure ).
Why can I not run tip or
cu ?
On your system, the programs &man.tip.1;
and &man.cu.1;
are probably executable only by
uucp
and group dialer . You can use the group
dialer to control who has access to your
modem or remote systems. Just add yourself to group
dialer.
Alternatively, you can let everyone on your system
run &man.tip.1; and &man.cu.1; by
typing:
&prompt.root; chmod 4511 /usr/bin/cu
&prompt.root; chmod 4511 /usr/bin/tip
My stock Hayes modem is not supported---what
can I do?
Actually, the man page for &man.tip.1; is
out of date. There is a generic Hayes dialer already built in.
Just use at=hayes in your
/etc/remote (see &man.remote.5;) file.
The Hayes driver is not smart enough to recognize some of
the advanced features of newer modems---messages like
BUSY , NO DIALTONE , or
CONNECT 115200 will just confuse it. You
should turn those messages off when you use &man.tip.1;
(using ATX0&W ).
Also, the dial timeout for &man.tip.1; is 60
seconds. Your modem should use something less, or else tip
will think there is a communication problem. Try
ATS7=45&W .
Actually, as shipped &man.tip.1; does not yet
support it fully. The solution is to edit the file
tipconf.h in the directory
/usr/src/usr.bin/tip/tip . Obviously you
need the source distribution to do this.
Edit the line #define HAYES 0
to #define HAYES 1 . Then
make and make install .
Everything works nicely after that.
How am I expected to enter these AT commands?
Make what is called a direct
entry in your
/etc/remote file (see &man.remote.5;). For example, if your modem is hooked
up to the first serial port, /dev/cuaa0 ,
then put in the following line:
cuaa0:dv=/dev/cuaa0:br#19200:pa=none
Use the highest bps rate your modem supports in the br
capability. Then, type
tip cuaa0 (see &man.tip.1;)
and you will be connected to your modem.
If there is no /dev/cuaa0 on your
system, do this:
&prompt.root; cd /dev
&prompt.root; sh MAKEDEV cuaa0
Or use cu as root with the following command:
&prompt.root; cu -lline -sspeed
with line being the serial port (e.g.
/dev/cuaa0 ) and speed being the speed
(e.g.57600 ). When you are done entering
the AT commands hit ~. to exit.
Why does the <@> sign for the pn
capability not work?
The <@> sign in the phone number
capability tells tip to look in
/etc/phones for a phone number. But the
<@> sign is also a special character
in capability files like /etc/remote .
Escape it with a backslash:
pn=\@
How can I dial a phone number on the command
line?
Put what is called a generic
entry in your
/etc/remote file (see &man.remote.5;). For example:
tip115200|Dial any phone number at 115200 bps:\
:dv=/dev/cuaa0:br#115200:at=hayes:pa=none:du:
tip57600|Dial any phone number at 57600 bps:\
:dv=/dev/cuaa0:br#57600:at=hayes:pa=none:du:
Then you can do something like tip -115200
5551234 . If you prefer &man.cu.1;
over
&man.tip.1;, use a generic cu entry:
cu115200|Use cu to dial any number at 115200bps:\
:dv=/dev/cuaa1:br#57600:at=hayes:pa=none:du:
and type cu 5551234 -s 115200 .
Do I have to type in the bps rate every time I do
that?
Put in an entry for tip1200 or
cu1200 , but go ahead and use whatever bps
rate is appropriate with the br capability.
&man.tip.1;
thinks a good default is 1200 bps which is why it looks for
a tip1200 entry. You do not have to use 1200
bps, though.
How can I more easily access a number of hosts through a
terminal server?
Rather than waiting until you are connected and typing
CONNECT host
each time, use tip's cm capability. For
example, these entries in
/etc/remote (see &man.remote.5;):
pain|pain.deep13.com|Forrester's machine:\
:cm=CONNECT pain\n:tc=deep13:
muffin|muffin.deep13.com|Frank's machine:\
:cm=CONNECT muffin\n:tc=deep13:
deep13:Gizmonics Institute terminal server:\
:dv=/dev/cuaa2:br#38400:at=hayes:du:pa=none:pn=5551234:
will let you type tip pain or
tip muffin to connect to the hosts
pain or muffin ; and
tip deep13 to get to the terminal
server.
Can tip try more than one line for each site?
This is often a problem where a university has several
modem lines and several thousand students trying to use
them...
Make an entry for your university in
/etc/remote (see &man.remote.5;) and use <\@> for
the pn capability:
big-university:\
:pn=\@:tc=dialout
dialout:\
:dv=/dev/cuaa3:br#9600:at=courier:du:pa=none:
Then, list the phone numbers for the university in
/etc/phones (see &man.phones.5;):
big-university 5551111
big-university 5551112
big-university 5551113
big-university 5551114
&man.tip.1;
will try each one in the listed order, then give
up. If you want to keep retrying, run &man.tip.1;
in a while loop.
Why do I have to hit CTRL+P twice to send CTRL+P
once?
CTRL+P is the default force
character,
used to tell &man.tip.1;
that the next character is literal data. You can set the
force character to any other character with the
~s escape, which means set a
variable
.
Type ~sforce=single-char
followed by a newline.
single-char is any single character.
If you leave out single-char ,
then the force character is the nul character, which you can
get by typing CTRL+2 or CTRL+SPACE. A pretty good value for
single-char is SHIFT+CTRL+6, which
I have seen only used on some terminal servers.
You can have the force character be whatever you want by
specifying the following in your
$HOME/.tiprc file:
force=single-char
Why is everything I type suddenly in UPPER CASE?
You must have pressed CTRL+A, &man.tip.1;
raise character
, specially
designed for people with broken caps-lock keys. Use
~s as above and set the variable
raisechar
to something reasonable. In fact,
you can set it to the same as the force character, if you
never expect to use either of these features.
Here is a sample .tiprc file perfect for Emacs users who
need to type CTRL+2 and CTRL+A a lot:
force=^^
raisechar=^^
The ^^ is SHIFT+CTRL+6.
How can I do file transfers with
tip ?
If you are talking to another Unix system, you can send
and receive files with ~p (put) and
~t (take). These commands run
&man.cat.1; and
&man.echo.1; on the remote system to accept and send files.
The syntax is:
~p <local-file> [<remote-file>]
~t <remote-file> [<local-file>]
There is no error checking, so you probably should use
another protocol, like zmodem.
How can I run zmodem with
tip ?
First, install one of the zmodem programs from the
ports collection (such as one of the two from the comms
category, lrzsz or
rzsz .
To receive files, start the sending program on the
remote end. Then, press enter and type
~C rz (or ~C lrz if you
installed lrzsz ) to begin
receiving them locally.
To send files, start the receiving program on the remote
end. Then, press enter and type
~C sz files
(or ~C lsz files )
to send them to the remote system.
Why does FreeBSD not find my serial ports, even
when the settings are correct?
Motherboards and cards with Acer UARTs do not probe
properly under the FreeBSD sio probe. Obtain a patch from
www.lemis.com to fix your problem.
¨ä¥¦¦U¦¡¦U¼Ëªº°ÝÃD
¬°¬Æ»ò FreeBSD ¥Îªº¸m´«(swap)ªÅ¶¡¤ñ Linux ¦h¡H
FreeBSD¶È¬O¬Ý°_¨Ó¸m´«ªÅ¶¡(swap)¥Îªº¤ñLinux¦h¦Ó¤w¡C¦b¨Æ¹ê¤W¡A
¨Ã¤£µM¡C¥Dnªº®t²§¬O¦b©ó¡AFreeBSD¿n·¥ªº±N¶¢¸mµL¥Îªº¥D°O¾ÐÅ餺®e
±À¤J¸m´«ªÅ¶¡(swap)¤¤¡A¥H¨Ï±o¥D°O¾ÐÅé¥i¥H§ó¬°¦³®Ä²vªº³Q¨Ï¥Î¡C¦Ó
Linuxªºµ¦²¤¬O±N¸m´«ªÅ¶¡(swap)¥Î¨Ó§@¬°¸Ñ¨M°O¾ÐÅé°ÝÃDªº³Ì²×¤â¬q¡C
¸ûÀWÁcªº¨Ï¥Î¸m´«ªÅ¶¡(swap)¡C¬O¤@ºØ§ó¦³®Ä²vªº¨Ï¥Î¥D°O¾ÐÅ骺¤â¬q¡C
µù¡G·í¤@¤è±FreeBSD¿n·¥ªº¨Ï¥Î¸m´«ªÅ¶¡(swap)ªº¦P®É¡A§A¥²»Ýª`
·N¨ì¡AFreeBSD¨Ã¤£·|¥ô·Nªº±N©Ò¦³ªºªF¦è³£±À¤J¸m´«ªÅ¶¡(swap)¤¤¡C¦p¦¹¡A
§A¤~¤£·|¦b¤@©]±J¾K°_§É«áµo²{¡A¾ãÓ¨t²Î³£³Q˶i¤F¸m´«ªÅ¶¡(swap)¤§¤¤¡C
§Y¨Ï§Ú¥u¦³¹B¦æ¤Ö¼Æµ{¦¡¡A¬°¤°»ò top Åã¥Ü¥X
¨Óªº³Ñ¾l°O¾ÐÅéÁÙ¬O«Ü¤Ö¡H
²³æªºµª®×¬O¡A©Ò¦³¥¼¨Ï¥Î¨ìªº¶¢¸m°O¾ÐÅé³£¬O³Q®ö¶Oªº°O¾ÐÅé¡A
¥ô¦ó¥¼³Q§Aªºµ{¦¡©Ò§Q¥Î¨ìªº°O¾ÐÅé±N³Q®Ö¤ß(kernel)¥Î¨Ó·í
§@ºÏºÐ§Ö¨ú(disk cache)¡C¦Ó³oºØ°O¾ÐÅé³Q &man.top.1; ¼Ð°O¬°
¶¢¸mªº(Inact) ¡A§Ö¨ú(Cache) ¡A
¥H¤Î ½w½Ä°Ï(Buf) ¡A¨Ãt³d¦b¦UÓ¤£¦Pªº¦ì¸mt³d
¼È¦s¸ê®Æ¡C³Q¼È¦s(cached)ªº¸ê®Æ¥Nªí¨t²Î¤£»Ýn¥h¦s¨ú¸ûºCªººÏºÐ¸Ë¸m
´N¥i¥H±o¨ì¸ê®Æ¡A¦p¦¹¡A¥i¥H´£¤É¨t²Îªº®Ä¯à¡CÁ`¦Ó¨¥¤§¡A&man.top.1;
Åã¥Ü¥X¸û¤Öªº ¶¢¸m(Free) °O¾ÐÅé¬O¦nªº¡A¥unÅã¥Ü
¥X¨ÓªºÈ¤£¬O «D±` ªº§C¡C
¬°¬Æ»òn¥Î(¬Æ»ò¬O) a.out ©M ELF °õ¦æÀɮ榡¡H
n¤F¸Ñ¬°¤°»òFreebsd¨Ï¥Î ELF ®æ¦¡¡A§A¦³¥²
n¥ý»{ÃѤ@¤U¤TºØ¦b¥Ø«e Unix ¨t²Î¤¤³Ì³Q¼sªxÀ³¥Î¨ìªº°õ¦æÀɮ榡¡G
¦b FreeBSD 3.x ¤§«e¡AFreeBSD ¨Ï¥Î a.out ®æ¦¡¡C
&man.a.out.5;
³o¬O³Ì¦¡A¦P¬O¤]¬O ³Ì¨å«¬
ªºUnix¥ØªºÀÉ
®æ¦¡¡C³oºØ®æ¦¡ªºÀɮרϥΤ@ºØµu¥Bºò±KªºÀÉÀY¡A¦P®É¡A¦ñÀHµÛ¤@
ÓÅ]³N¼Æ¦r¥Î¨Ó¿ëÃѮ榡¡C(°Ñ¦Ò &man.a.out.5; ¦³§ó¦h¸Ô²Óªº»¡
©ú)¡C¥¦¥]§t¦³¤TÓ¸`°Ï¡G .text .data ¤Î .bss ¥[¤W¤@ӲŸ¹ªí
¤Î¦r¦êªí¡C
COFF
SVR3¥ØªºÀɮ榡¡CÀÉÀY¥]§t¤F¤@Ó¸`°Ïªí¡A©Ò¥H¥i¥H¨ã³Æ¤ñ
.text .data .bss ÁÙ¦hªº¸`°Ï¡C
ELF
ELF¬° COFF ®æ¦¡ªº«áÄ~ªÌ¡A¥Dnªº¯S¼x¬°
¥i¥H¨ã¦³½Æ¼Æ¸`°Ï¬q¡A¨Ã¥i¥H¨Ï¥Î32-bits©Î¬O64-bitsªº¼ÆÈ¡C
¥Dnªº¯ÊÂI¬°¡G ELF ®æ¦¡¬O¦b¨CÓ¨t²Î¤¤¥u
·|¦³¤@ºØ ABI ªº°²³]¬°«eÃD³Q³]p¥X¨Óªº¡C¦ý¬O¡A¦b¨Æ¹ê¤W¡A³oÓ
°²³]¿ùªºÂ÷ÃСC¦]¬°¡AÁa¨Ï¦b°Ó¥Îªº SYSV ¥@¬É¸Ì¡A¤]¦Ü¤Ö¦³ SVR4¡A
Solaris ©M SCO ¤TºØ ABI¡C
Ķµù¡GABI(Application Binary Interface)¡C¦pªG¤@©wn½Ķ¡A
´N¥s¥¦ À³¥Îµ{¦¡¤G¶i¦ì¤¶± ¦n¤F¡C ABI³Qµo
®i¥X¨Óªº¥Î·N¡A¬O¬°¤F«P¨Ï¦b¬Û¦PCPU©Òµo®i¥X¨ÓªºÀ³¥Îµ{¦¡¡A¯à°÷
¦b¤£¦Pªº¨t²Î¤W¡A§@¨ì¤G¤¸ÀÉ(Binary Code)¬Û®e¡C¤ñ¤è»¡¡A
Sun ©Ò´£¥Xªº Solaris ABI
¡A«OÃÒ°õ¦æÀɯà°÷¦b¬Û¦P CPU ªº Solaris ¨t²Î¤W°õ¦æ¡A¥t¤@Ó¨Ò¤l¬O
Windows ¨t²Î¡C¦PÄÝ©ó Intel x86 ª©¥»ªº°õ¦æÀɯà°÷¦Û¥Ñªº¦bWindows
9x/me¤ÎWindows NT/2k/XP¤§¶¡°õ¦æ¡C
FreeBSD´£¨Ñ¤@Ó¤½¥Îµ{¦¡±Nµ{¦¡©Ò»ÝªºABI¸ê°T¯O¤W¡AÂǦ¹¸ÕµÛ
¥h¸Ñ¨M³oÓ°ÝÃD¡C½Ð°Ñ¦Ò &man.brandelf.1; ¥H¨ú±o§ó¦h¸ê°T¡Ci
FreeBSD ¨Ó¦Û ¶Ç²Î
ªº°}Àç¡C¦b¶Ç²Î¤W¡AFreeBSD³£
¨Ï¥Î &man.a.out.5; ®æ¦¡¡A³o¼Ëªº§Þ³N¦b¦n´X¥Nªº BSD ³£³QÃÒ©ú¬O¥i¾aªº¡C
ÁöµM¡A¦bFreeBSD¤W¥i¥H«Ø¥ß¥H¤Î¥¿½Tªº°õ¦æì¥Í ELF
®æ¦¡ÀÉ®×(¥]§t®Ö¤ß)¡CµM¦Ó, FreeBSD¦b¤@¶}©l¤Ï¹ï±N¹w³]®æ¦¡Âà´«¬° ELF¡A
¬°¤°»ò©O¡H·íLinux¶}©lµhWªºÂà´«¦Ü ELF ®æ¦¡®É¡A
¨Ã«D¬O¬°¤Fn°kÂ÷ a.out ®æ¦¡¡C¬Û¤Ïªº¡A³o¬O¦]
¬°¤§«e Linuxªº¦@¨É¨ç¦¡®w(shared libraries)±Ä¥Î¥H¸õÅDªí®æ
(jump-table)¬°°ò¦ªº§Þ³N¥h³]p¡C³o¬O¤@ºØÅýµo®iªÌ·P¨ì§xÂZ¡A¥B«D±`
Ãø¥H¨Ï¥Î¡A¤£¨ã¨¬°÷¼u©Êªº¤èªk¡C¬JµM¡A¤w¸g¦s¦bªº
ELF ¤u¨ã´£¨Ñ¤F¦@¨É¨ç¦¡®w(shared libraries)ªº¸Ñ
¨M¤è®×¡A¦Ó¥B¡A¨º¬Ý°_¨Ó¬OÓ «e½Ãªº¤èªk
¡A¦]¦¹¡A©Ò»Ý
ªºÂà´«¥N»ù´N¥i±µ¨ü¦]¦ÓÂà´«¡C
¦bFreeBSDªºª¬ªp¤¤¡A§Ú̪º¦@¨É¨ç¦¡®w(shared libraries)¾÷¨î©M
SunOS ªº«¬¦¡«D±`¬Ûªñ¡A¥B©ö©ó¨Ï¥Î¡CµM¦Ó¡A
±q 3.0 ¶}©l¡AFreeBSD ¥¿¦¡±N ELF §ï¬°¹w³]®æ¦¡¡C
ÁöµM¡Aa.out ®æ¦¡¨Ì¦p¥H©¹¯ëªº¦n¡A¦ý¬O¡A§ÚÌ
½sĶ¤u¨ãªº¼¶¼gªÌ¡AGNU ªº¦¨û¡A¥L̤¤¤î¤F¹ï
a.out ®æ¦¡ªº¤ä´©»PºûÅ@¡C¦b³oºØª¬ªp¤U¡A¢¨Ï
§ÚÌ¥²¶·¦Û¦æºûÅ@¥t¤@¥÷ª©¥»ªº compiler ©M linker¡A¤]¨Ï±o§Ú̵Lªk
±q³Ì·sªº GNU µo®i¦¨ªG¤¤Àò±o¦n³B¡C¦¹¥~¡A¹ï ISO-C++ ªº»Ý¨D¡A¤×¨ä¬O
«Øºc¤l(constructors)©M¸Ñºc¤l(destructors)¡A¤]±a°Ê¥¼¨Óª©¥»¤¤¹ï
ELF ªºì¥Í¤ä´©¡C
¬Oªº, ¦ý¬O, ¬°¤°»ò·|¦³³o»ò¦h¤£¦P®æ¦¡ªº°õ¦æÀɦs¦b©O?
¦b¶Â·t¦Ó»»»·ªº¹L¥h¡A¶È¦³Â²®ªºµwÅé¦s¦b¡C¦Ó¦]¬°µwÅé²®¡A·íµM¤]
¥u¯à°õ¦æ¤p¦Ó²³æªº¨t²Î¡Ca.out ®æ¦¡¬O°ò©ó¨ºÓ®É¥N©Ò»Ýn¡A¦Ó³Q³Ð³y
¥X¨Óªº(¨Ò¦p¹³PDP-11)¡C¦b³o¤§«á¡A³\¦h¤H¸ÕµÛ±N Unix ²¾´Ó¨ì¨ä¥L¥¥x
®É¡A¥L̤]«O¯d¤F a.out ®æ¦¡ªº°õ¦æÀÉ¡C¦]¬°¡A³o¹ï¦´Áªº Motorola 68k¡A
VAXen ¤§Ãþªº¨t²Î¤w¸g¨¬°÷¨Ï¥Î¤F¡C
µM¦Ó¡A¤H¨Ã¤£·|º¡¨¬©ó²{ª¬¡C¤@¨ÇÁo©úªºµwÅé¤uµ{®v·Q¨ì¤F¡A¦pªG¯à
Åý³nÅé¦h³B²z¤@¨Ç¨Æ¡A¨º CPU ªº¹q´¹Åé¼Æ´N¯à¤Ö¤@ÂI¡A¨Ã¥B¶]±o§ó§Ö¡Cn
¦b³oºØ·s¦¡ªºµwÅé¤W¤u§@(²{¦bºÙ¬°RISC)¡Aa.out
³oºØ®æ¦¡´N¤£¦X¾A¤F¡C°ò©ó³o¼Ëªº²{¹ê©Ò»Ý¡A§ó¦hªº°õ¦æÀɮ榡³Qµo®i¥X
¨Ó¡A¥H´£¨Ñ¤ñ²³æ¥B¨ü¨ì³\¦h¨îªº a.out ®æ¦¡
§ó¦nªº®Ä¯à¡C¤ñ¤è¹³¬O COFF ¡A
ECOFF ¡A¤w¤Î¤@¨Ç¸û¤£¬°¤H©Ò©Pª¾ªº®æ¦¡¯É¯É³Q³Ð³y
¥X¨Ó¡C¦ý¬O¡A³o¨Ç®æ¦¡³£¤w¹F¨ì¦U¦Ûªº·¥¡Aª½¨ì¦³¤@¤Ñ
ELF ªº¥X²{¡C
¦¹¥~¡A·íµ{¦¡ªºÅé¿n¶V¨Ó¶V¤j¡A¦ÓºÏºÐªÅ¶¡©M¥D°O¾ÐÅé¬Û¹ï¨Ó»¡³£¸û
¤p®É¡A¦@¨É¨ç¦¡®w(shared libraries)ªºÆ[©À³Qµo®i¥X¨Ó¤F¡C¦b³o¦P®É¡A
µêÀÀ°O¾ÐÅé¨t²Î(VM System)¤]Åܱo¶V¨Ó¶Vºë¥©¡C·í¨C¤@ºØ¶i¨B³£¦b
a.out ®æ¦¡¤W³Qµo®i¥X¨Ó®É¡A¥¦ªº¥i¥Î©Ê¤]¦P®ÉÅÜ
±o¶V¨Ó¶V§C¡C¥t¥~¡A¤HÌÁ٧Ʊæµ{¦¡¯à¦b°õ¦æ´Á¶¡°ÊºA¸ü¤J¡A©Î¬O±N¤w¸g
°õ¦æ¹L¥B¨S¦³¥Îªºªì©l¤Æµ{¦¡½X¥á±ó¡AÂÇ¥H¸`¬Ù§ó¦hªº°O¾Ð¡Cµ{¦¡»y¨¥¦b
³oӮɴÁ¤]«K±o§óºë¥©¡A¤H̤]§Æ±æ¦b main ¤§«e¦Û°Êªº°õ¦æ§ó¦hªºªF¦è¡C
¦]¦¹¡A³\¦hÁcÂø¥B¥t¤H¹Ä¬°Æ[¤îªº§Þ¥©³Q¥Î¦b a.out
®æ¦¡¤W¥h¸Ñ¨M³o¨Ç°ÝÃD¡C¦ý¬O¡A¥Ñ©ó a.out ®æ¦¡
¥ý¤Ñªº¨î¡An¸Ñ¨M³o¨Ç°ÝÃD¥²»Ý¥I¥X§ó¦hªº¥N»ù¤Î®É¶¡¦¨¥»¡A¨ÃÅýµ{¦¡
ªº½ÆÂø«×¤j¬°´£¤É¡C¦Ó ELF ®æ¦¡¥i¥H¤@Á|¸Ñ¨M³o¤@
¤Á°ÝÃD¡C¦ý¬O¡An±N¾ãÓ¨t²Î±q®Ú¥»Âà´«¹L¥h¡A±N·|¦³¤£µuªº°}µh´Á¡A¦]
¦¹¡A ELF ®æ¦¡±N·|¦³¤@°}¤l»P
a.out ¨Ã¦s¡C
µM¦Ó¡AÀHµÛ®É¶¡ªº¹L¥h¡AFreeBSDªº build tools ºt¤Æ¦¨¥¦æªº¨âÓ
¤ä½u(¤×¨ä¬O²ÕĶ¾¹©M¸ü¤J¾¹)¡CFreeBSD³o±ø¸ô¥[¶i¤F¦@¨É¨ç¦¡®w
(shared libraries)¨Ã×¥¿¤F¤@¨Ç¿ù»~¡C¦Óì¨Óµo®i³o¨Çµ{¦¡ªº GNU ¦¨û
«h¬°¤F¦]À³²{ªp¡A«¼g¤F³o¨Çµ{¦¡¡A¥H§ó²³æªº¤è¦¡¹ï¸ó¥¥x½sĶ
(building cross compilers)¡A¥H¤Î¦hºØ®æ¦¡
(plugging in different formats) §@¥X¤F¤ä´©¡C³\¦h¤H·Q§@¥X¥H FreeBSD
¬°¥Øªº¥¥xªº¸ó¥¥x½sĶ¾¹¡C¦ý¤£©¯ªº¬O¡AFreeBSD ªº as ©M ld ¤£¯à§@
³o¶µ¤u§@¡C·sªº GNU ¤u¨ãµ{¦¡¥[¤J¤F¸ó¥¥x½sĶ (Cross Compiler)¡A
ELF ®æ¦¡¤ä´©¡A¦@¨É¨ç¦¡®w(shared libraries)¡A
C++ ªºÂX¥R... µ¥µ¥¡C¦¹¥~¡A³\¦h¼t°Ó¥H ELF ®æ¦¡
µo¦æ¨ä²£«~¡A¦pªG³o¨ÇªF¦è¯à¦b FreeBSD ¤W°õ¦æªº¸Ü·íµM¬O³Ì¦nªº¡C¬JµM¡A
¯à°÷°õ¦æ ELF ®æ¦¡ªº°õ¦æÀɤF¡A¬°¤°»òÁÙ¶·n
a.out ©O¡H¥¦¤w¸g¬O¤@¤Ç««««¦Ñ¨oªº°¨¤F¡A¦bºÜ¤O
ºÉ©¾ªº©^Äm³o»ò¦h¦~¤§«á¡A¸Ó¬OÅý¥¦¦bªª³õªÎ¨Uªº¯ó¦a¤W¦n¦n¥ð®§ªº®ÉÔ
¤F¡C
ELF ®æ¦¡¤ñ a.out ¨ã¦³§ó¨}¦nªº®i²{¯à¤O¡A¨Ã
¥B¦b©³¼h¨t²Î¤¤¨ã¦³§ó¦hªº¥iÂX®i©Ê¡CELF ¤u¨ãµ{¦¡
§ó®e©ö³QºûÅ@¡A¥B´£¨Ñ¸ó¥¥x½sĶªº¤ä´©¡A³o¤@ÂI¹ï«Ü¦h¤H¨Ó»¡¬O«Ü«n
ªº¡CELF ®æ¦¡¥i¯à¤ñ a.out ºC¤@ÂI¡A¦ý¬O¨ä®t²§«D
±`Ãø´ú¶q¥X¨Ó¡C³o¨âªÌ¶¡ÁÙ¦³³\¦h²Ó¸`¤Wªº¤£¦P¡A¤ñ¤è»¡¤À¶¹ïÀ³ªº¤è¦¡¡A
µ{¦¡½Xªì©l¤Æªº¤èªk...µ¥µ¥¡C³o¨Ç¨Ã¤£¬O«Ü«n¡A¦ý¬O¡A¨âªÌ´N¬O¤£¦P¡C
¥H«á¡AGENERIC ®Ö¤ß(kernel)±N·|²¾°£¹ï a.out
®æ¦¡¡C·í¤£¦b¦³°õ¦æ¶Ç²Î a.out µ{¦¡ªº¶·n®É¡A
±N·|±q®Ö¤ß(kernel)¤¤²¾°£¡C
¬°¬Æ»òchmod¤£·|§ïÅܲŸ¹³sµ²(symlink)ªº¦s¨úÅv¡H
Symlinks ¥»¨¨Ã¨S¦³¦s¨úÅv¡A¦P®É¡A¦b¹w³]ªºª¬ªp¤U¡A
&man.chmod.1; ±N¤£·|¸òÀHµÛ symlinks ¥h§ï«K¥Ø¼ÐÀɮתº¦s¨úÅv¡C¦]¦¹¡A
¦pªG§A¦³¤@ÓÀÉ®× foo ¡A¦P®É¡A¦³¤@Ó symlink
bar «ü¦V³oÓÀɮסA¥H¤U³oÓ©R¥O±N¥Ã»··|¦¨¥\
ªº³Q°õ¦æ¡C
&prompt.user; chmod g-w bar
µM¦Ó¡A¦b foo ¤Wªº¦s¨úÅv±N¤£·|³Q§ï
ÅÜ¡C
§A¥²»Ý¨Ï¥Î -H ©Î¬O±N -L
»P -R ¿ï¶µ¤@°_¨Ï¥Î¡A°Ñ¦Ò &man.chmod.1; ¥H¤Î
&man.symlink.7; ¥H¨ú±o§ó¦hªº¸ê°T¡C
¨Ï¥Î¿ï¶µ -R ·|Åý &man.chmod.1; ¥H
»¼°j(RECURSIVE) ªº¤è¦¡¤u§@¡C·í§A§â
&man.chmod.1; ¥Î¦b¥Ø¿ý©Î¬O³sµ²¨ì¥Ø¿ýªº²Å¸¹³sµ²®É§ón¤p¤ß¡C
¦pªG§An§ïÅܤ@ӲŸ¹³sµ²°Ñ¦Ò¨ìªº¥Ø¿ý¤§¦s¨úÅv &man.chmod.1; ¡A
¥Bª`·N¤£n¥[¤W¥ô¦ó¿ï¶µ¡A¨Ã¥B¦b symlink ªºµ²§À¥[¤W±×½u
(/ )¡CÁ|¨Ò¨Ó»¡¡A¦pªG
foo ³sµ²¨ì¥Ø¿ý bar ¡A
¦Ó§An§ó§ï foo (¹ê»Ú¤W¬O
bar )¡A¨º´N¨Ï¥Î¡G
&prompt.user; chmod 555 foo/
µ²§Àªº±×½u·|¨Ï±o &man.chmod.1; §ïÅÜ
foo ©Ò«ü¦Vªº¥Ø¿ý bar
ªºÅv¡C
¬°¤°»ò¦b FreeBSD 2.2.x ¤Î§ó¦ªºª©¥»¤¤¡Aµn¤J¦WºÙ(login names)
³Q¨î¦b¤KÓ¦r¤¸¥H¤U©O¡H
§A¥i¯à»{¬°×§ï UT_NAMESIZE «á¦b«·s½sĶ¾ãÓ
¨t²Î¬O«Ü®e©öªº¨Æ¡C¦Ó¥B¦b³o¤§«á¡A¨C¥ó¨Æ³£¥i¥H¹B§@ªº«Ü¦n¡C¤£©¯ªº¬O¡A
¦³³\¦hªºµ{¦¡©M¤u¨ã(¥]§t¨t²Î¤u¨ã)§â¼Æ¦r¼g¦º¦bµ{¦¡¸ÌÀY(¨Ã«DÁ`¬O
8 ©Î 9 ¡A¦³®É¥i¯à¬O¥j©Çªº
15 ©Î 20 )¡C³o¤£¶È¶È¬O·|±N
§Aªº¨t²Î°O¿ýÀɧËÃa¦Ó¤w(¨Ó¦Û©óÅܰʪø«×©M©T©wªø«×°O¿ýªº®t²§)¡A¦P®É
¤]·|¯}Ãa Sun ªº NIS Client ªº¹B§@¡C¦P®É¡A©M¨ä¥LªºUnix¨t²Î¤§¶¡¤]
¦³¥i¯à·|²£¥Í¥¼ª¾ªº°ÝÃD¡C
¦bFreeBSD 3.0 ¤Î¤§«áªºª©¥»¡A±b¸¹ªº³Ì¤jªø«×¼W¥[¨ì16Ó¦r¤¸¡A
¦P®É¡A¨º¨Ç±Nªø«×¼g¦ºªºµ{¦¡¤]³Q§ä¥X¨Ó¨Ã§@¤F¾A·íªº×¥¿¡C¥¿¦]¬°¼vÅT
¨t²Îªº½d³ò«Ü¼s¡A©Ò¥Hª½¨ì3.0ª©¤§«á¤~ºâ¤jP×¥¿§¹¦¨¡C
¦pªG§A¦³¦Û«H¦b¥X°ÝÃDªº®É«á¯à¦Û¦æ¸Ñ¨M¡A§A¥i¥H§Q¥Î¤U±ªº¤èªkÅý
¸û¦´Áªºª©¥»¤ä´©¸ûªøªº±b¸¹¡Cº¥ý¡Aקï
/usr/include/utmp.h ¤¤ªºUT_NAMESIZE¡C
µM«á¡A§A¥²¶·§â /usr/include/sys/param.h
¤¤ªº MAXLOGNAME §ï¦¨¸ò UT_NAMESIZE ¬Û¦P¡C³Ì«á¡A¦pªG§A¬O±qì©lµ{
¦¡«Ø¥ß¨t²Î, §O§Ñ¤F /usr/include ¨C¦¸³£·|³Q§ó·s¡C
קï /usr/src/.. ¤¤¾A·íªºÀɮסC
§Ú¯à¦bFreeBSD¤U°õ¦æDOSµ{¦¡¶Ü¡H
¬Oªº¡A¦Û3.0ª©°_§A¥i¥H¨Ï¥ÎBSDIªº
doscmd DOS ¼ÒÀÀ¾¹¡A¦pªG§A¹ï³oÓªF¦è
¦³¿³½ì¡A©Î¬O·Q¥[¤Jµo®i¦æ¦C¡A½Ð±H¤@«Ê¹q¤l¶l¥ó¨ì &a.emulation; ¡C
¹ï©ó3.0¤§«eªº¨t²Î¡A¦b ports ¤¤¦³¤@®M³nÅé¥i¥H¼Òèö 8088¡A¨Ã´£
¨Ñ¨¬°÷ªºBIOS¤¤Â_ªA°È¥H°õ¦æDOS¤å¦r¼Ò¦¡ªºµ{¦¡¡A³o®M³nÅé¥s°µ
pcemu ¡A¦P®É¡A¹B¦æ¥¦¶·n
X Windows(¥ÑXFree86´£¨Ñ)¡C
¦pªGn§âFreeBSD¤å¥ó½Ķ¦¨§Úªº¥À»y¡A§Ú»Ýn§@¤°»ò¡H
°Ñ¾\FreeBSD¤å¥ó¤¤ªº ½Ķ±`¨£°Ýµª ¡C
¬°¤°»ò§Ú±H¨ì FreeBSD.org ¬ÛÃö¦a§}ªº¹q¤l¶l¥ó³£³Q°h¦^¤F©O¡H
FreeBSD.org ªº¶l¥ó¨t²Î¹ï©ó¶i¨Óªº¶l¥ó±Ä¨úÄY®æªºÀˬd¡A¨Ã¥B°h¦^
©Ò¦³³]©w¤£¥¿½T¡A©Î¬O¼ç¦bªº©U§£¶l¥ó¡C§Aªº¶l¥ó³Q°h¦^¥i¯à¬O¦]¬°¤U¦C
ì¦]©Ò¤Þ°_¡G
³o«Ê¹q¤l¶l¥ó¨Ó¦Û¤wª¾ªº©U§£¶l¥ó°Ï°ì©Î¬OIP¤¤¡C
FreeBSD¶l¥ó¦øªA¾¹±N©Úµ´±µ¦¬¤wª¾ªº©U§£¶l¥ó¨Ó·½ªº¹q¤l¶l¥ó¡C
¦pªG´£¨Ñ§Aºô¸ôªA°Èªº¤½¥q©Î¬Oºô°ì¤¤¦³²£¥Í¹L©U§£¶l¥ó©Î¬O¦³©U§£
¶l¥óÂ༽¯¸¡A½Ð§A´«¤@ÓªA°È´£¨ÑªÌ¡A©Î¬O°®¯Ü©ñ±ó¡C
¹q¤l¶l¥óªº¥»¤å¶È¦³HTML¡C
¶l¥óÀ³¸Ó¤w¯Â¤å¦r®æ¦¡µo°e¡A½Ð³]©w§Aªº¹q¤l¶l¥ó³nÅé°e¥X¯Â¤å
¦r®æ¦¡¡C
FreeBSDªº¶l¥ó³B²zµ{¦¡µLªk¥ÑIP¤Ï¬d°e¥ó¥D¾÷ªºIP¡C
³]¸m DNS ¤Ï¬d¬O±µ¨ü¤@¥x¥D¾÷¶l¥óªº¤@ӼзÇn¨D¡A½Ð¬°±zªº¶l¥ó
¥D¾÷³]¸m DNS ¤Ï¬d¡C³\¦h´£¨Ñ®a®xºô¸ôªA°È (DSL¡Acable¡Adialup µ¥)
ªº¤½¥q¨Ã¤£´£¨Ñ³o¼ËªºªA°È¡C¦b³oºØ±¡ªp¤U¡A½Ð³z¹Lºô¸ôªA°È´£¨ÑªÌªº
¶l¥ó¦øªA¾¹°e¥X±zªº¹q¤l¶l¥ó¡C
¦b SMTP ¨Ï¥Î EHLO/HELO ©R¥O®É©Òµ¹¤©ªº hostname µLªk³Q¸ÑªR¨ì
¤@Ó IP ¦ì¸m¡C
¦b¶l¥ó³Q±µ¨ü¥H«e¡A¤@Ó¥R¤À¦X®æ¡A¥B¥i³Q¸ÑªRªº¥D¾÷¦WºÙ¦b
SMTP ¨ó©wªº¹ï½Í¤¤¬O¥²nªº¡C¦pªG§A¨S¦³¦b DNS ¦øªA¾¹¤¤µn°O§A
ªº¥D¾÷¦WºÙ¡A½Ð³z¹Lºô¸ôªA°È´£¨ÑªÌªº¶l¥ó¦øªA¾¹°e¥X±zªº¹q¤l¶l
¥ó¡C
§Aªº°T®§¤¤§¨±aµÛ¤@Ó message ID ¥H localhost
¦r¦êµ²§ô¡C
¬Y¨Ç¶l¥ó³nÅé²£¥Í¬Y¨Ç¤£¥¿½Tªº message ID¡A³o±N¤£³Q±µ¨ü¡C
§A¥²»Ý§ó§ï³]©wÅý§Aªº¶l¥ó³nÅé²£¥Í¥¿½Tªº message ID¡A¦pªG³oµL
ªk¸Ñ¨M¡A¦Ò¼{»¡ªA§Aªº¶l¥ó³nÅé§@ªÌ§ó·sµ{¦¡¥H³B²z³oÓ°ÝÃD¡C
§Ú¥i¥H¦bþ¸Ì§ä¨ì¤@Ó§K¶OªºFreeBSD±b¸¹¡H
FreeBSDªº¦øªA¾¹¥»¨¤£´£¨Ñ¥ô¦ó¹ï¥~ªºªA°È¡A¨ä¥Lªº³æ¦ì¤¤¡A
¦³¤H´£¨Ñ¶}©ñªº Unix ¨t²ÎªA°È¡C¨ä¤¤¦³¨Ç¥i¯àn¦¬¨ú¨Ç³\¶O¥Î¡C
Arbornet, Inc ¡A
¤]³QºÙ¬° M-Net¡A¦Û 1983 ¦~°_´N¶}©l´£¨Ñ Unix ¨t²ÎªA°È¡C¤@¶}©l¡A
¥L̨ϥΠAltos ¨Ã°õ¦æ System III¡C¥L̦b 1991 ¦~Âà´«¨t²Î¦¨¬°
BSD/OS¡C¦b 2000 ¦~¤»¤ë¡A¥L̦A«×§ó´«¦¨¬° FreeBSD¡CM-Net ¯àÅý¨Ï
¥ÎªÌ³z¹L SSH ¤Î telnet ³s½u¨ì¥D¾÷¡A¨Ã´£¨Ñ§¹¾ãªº FreeBSD ³nÅé¥H
¨Ñ¨Ï¥Î¡CµM¦Ó¡AM-Net §@¬°¤@Ó«D¬Õ§Q²Õ´¹B¦æ¡A¦s¨úÅv¥u©ó¦¨û©M
ÃÙ§UªÌ¡AM-Net ¤]´£¨Ñ BBS ¨t²Î©Mºô¸ô²á¤ÑªA°È¡C
Grex ´£¨Ñ¤F«D±`
Ãþ¦ü M-Net ªºªA°È¡A¥]¬A¤F BBS ¨t²Î©Mºô¸ô²á¤Ñ¡CµM¦Ó¡A¾÷¾¹¬O¨Ï¥Î
Sun 4M¡A¨Ã°õ¦æ SunOS¡C
¤°»ò¬O sup ¡A§Ú¸Ó¦p¦ó¨Ï¥Î¥¦¡H
SUP ªº·N«ä¬O Software Update Protocol¡A¥Ñ CMU µo®i¡A
¥Î¨Óºû«ù¾ãÓµo®iªº¦P¨B¡C§Ú̧Q¥Î¥¦«O«ù»·ºÝªº¯¸¥x©Mì©l¯¸¥x¤§¶¡
ªº¦P¨B¤u§@¡C
µM¦Ó¡ASUP ¦bÀW¼eªº¨Ï¥Î¤W¨Ã¤£¤Ó¤Íµ½¡A¦P®É¡A¥Ø«e¤]¤£¦A¨Ï¥Î¤F¡C
¥Ø«e«Øijºû«ùì©l½X¦P¨B§ó·sªº¤èªk¬O
CVSup ¡C
³oÓ¥i·Rªº¤p¬õ¤Hªº¦W¦r¬O¤°»ò¡H
¦ü¥G¡A¥L¨Ã¨S¦³¤@Ó¥¿¦¡ªº¦W¦r¡A©h¥B´NºÙ¨ä¬°
BSD ¤p´cÅ]
§a¡C¦pªG§A°õ·Nn¨Ï¥Î¤@Ó¦W¦r¡C¨º´N¥s¥L
¤p°Êª«(beastie)
§a¡Cµù¡Gbeastie
¦bŪµ¤W¸ò BSD
«Ü±µªñ¡C
§A¥i¥H¦bBSD¤p´cÅ]ªº ¥D¶
¤W¨ú±o§ó¦hªº¸ê°T¡C
§Ú¯à¨Ï¥ÎBSDªº¤p´cÅ]¹Ï®×¶Ü¡H
¤]³\§a¡A§Ú¤]¤£½T©w¡CBSD¤p´cÅ]¹Ï®×ªºª©Åv¬OÄÝ©ó°¨·²º¸Ä¬®æÄõ±Ð·|
(Marshall Kirk McKusick)©Ò¾Ö¦³¡C§A¥i¥H¸ÕµÛ¥h¬d¬Ýºô¶±ÔzÃö©óBSD¤p´cÅ]¨v¹³
¥H¨ú±o§ó¸Ô²ÓÃö©ó¨Ï¥Î¥Lªº¸ê°T¡C
Á`Âkªº¨Ó»¡¡A¦pªG§A¯Âºé¬°¤F¦Û¤v·QnŲ½à¡A¨º»ò¡A§A¥i¥H¦Û¥Ñªº¨Ï
¥Î¨v¹³¡C¦pªG§A¬OÓ¤H¨Ï¥Î¡A¥un±¡ªp¾A·í¡AÀ³¸Ó³£·|³Q³\¥i¡C¦pªG§A·Q
¦b°Ó·~¤W¨Ï¥Î¡A«h§A¥²»ÝÁpôĬ®æÄõ±Ð·|(Kirk McKusick)¥H¨ú±o³\¥i¡C
¦pªG§A»Ýn§ó¶i¤@¨B¸Ô²Óªº¸ê°T¡A½Ð°Ñ¦Ò BSD¤p´cÅ]ªºº¶ ¡C
§A¦³¥ô¦óªº BSD ¤p´cÅ]¹Ï®×¥i¥HÅý§Ú¨Ï¥Î¶Ü¡H
§A¥i¥H¦b /usr/share/examples/BSD_daemon/
µo²{ eps ¤Î Xfig ¨âºØ®æ¦¡ªº¹ÏÀÉ¡C
MFC ¥Nªí¤°»ò·N«ä¡H
MFC ¬O¤@ÓÁY¼g¡A¥¦¥Nªí¤F Merged From -CURRENT
¡C
¥¦³Q¨Ï¥Î¦b CVS logs ¤¤¡A¥Hªí¥Ü±q CURRENT ¤¤¾ã¦X¶i STABLE ¤À¤ä
ªº§ïÅÜ¡C
BSD ¨s³º¥Nªí¤°»ò·N«ä¡H
¥¦¬O¤@ºØ©Ó¶Ç¦Û¶Â·t®É¥Nªº¥j¦Ñ¯µ±K»y¨¥¡A¶È¶È¦b¤º³¡¦¨û¤§¤¤¡A
¥H¤f¦Õ¬Û¶Çªº¤è¦¡®¨®¨ªº¬y¶ÇµÛ¡C¥¦¥Î¨Ó¥Nªí¬Y¨Ç¯«¯¦ªºªF¦è¡A¦ý¬O¡A
§Ú̵Lªk¹ï³o¨ÇªF¦è¥H½T¹êªº¤å¦r¥[¥H±Ôz¨Ã¨ã¹³¤Æ¡A¥¦´X¥G¤£§@¥ô¦ó
ªºÂ½Ä¶»P¸ÑÄÀ¡C¦pªGµw¬On¥H¤HÃþ²{¦³ªº»y¨¥¥[¥H»¡©ú¡A¥u¯à»¡¥¦ªº·N
«ä¤j·§¤¶©ó ¤@¯Å¤èµ{¦¡Áɨ®(Formula-1 Racing Team)
¡A
¥øÃZ¬O¬ü¨ýªºÂI¤ß(Penguins are tasty snacks)
¡A¥H¤Î
§Ṳ́ñLinux§ó¨ã¦³«ÕÀq·P(We have a better sense of humor than Linux)
³o¤TªÌ¤§¶¡¡C:-)
¦n¤F¡A¤£¸ò§A¶}ª±¯º¤F¡C¥¿½Tªº»¡¡ABSD ¬O
Berkeley Software Distribution
ªºÁY¼g¡A³o¬O¥Ñ Berkeley
CSRG (Computer Systems Research Group)
¿ï¨Ó·í§@¥LÌ©Òµo¦æªº Unix ¦WºÙ¡C
POLA ¥Nªí¤°»ò·N«ä¡H
³Ì¤ÖÅå³Yì«h¡C³o¥Nªí¤F FreeBSD ªºµo®i¹Lµ{¡A¥ô¦óªº§ïÅܨì¤F¨Ï
¥ÎªÌºÝÀ³¸Ó«O«ù¤£Åý¨Ï¥ÎªÌ·P¨ìÅå³Y¡C¤ñ¤è»¡¡A±N
/etc/defaults/rc.conf ¤¤ªº¨t²Î±Ò°Ê¶¶§Ç¥ô·N
ªº§ó§ï±N¹H¤Ï³oÓì«h¡C
¤°»ò¬O repo-copy¡H
¤@¥÷ repo-copy (¥¦¬O repository copy
ªºµuªí®æ)
ª½±µ°Ñ¦Ò¨ìCVSÜ®w¤¤ªºÀɮסC
¨S¦³¤F¤@¥÷ repo-copy¡A¦pªG¤@ÓÀɮ׶·n³Q½Æ»s©Î¬O³Q·h²¾¨ìÜ®w
¤¤ªº¨ä¥L¦a¤è¡A½T»{ªÌ±N·|°õ¦æ cvs add ¥H§âÀÉ®×
©ñ¨ì·sªº¦a¤è¡A¦P®É¡A¹ïÂÂÀÉ®×°õ¦æ cvs rm ¡AÂÂÀÉ
®×±N³Q²¾°£¡C
³oÓ¤èªk¤£§Qªº¦a¤è¬O¡A¾ú¥vÀÉ®×(§Y¦b CVS °O¿ý¤¤)±N¤£·|³Q½Æ»s
¨ì·sªº¦aÂI¡C¦b FreeBSD Project ¤¤¦Ò¼{¨ì¡A³oÓ¾ú¥v°O¿ý¬O«Ü¦³¥Î³Bªº¡A
¤@Ó repository copy ¬O¸g±`³Q¥Î¨ìªº¡C³o¬O repository meisters
¤@ª½¨Ï¥Î¨Ó±NÀɮ׽ƻs¶iÜ®wªº¬yµ{¡A¦Ó«D¨Ï¥Î &man.cvs.1;¡C
¬°¤°»ò§Ú¸Ó¦b·N¸}½ñ¨®´×ªºÃC¦â¡H
¤@ӳ̵u³Ìµuªºµª®×¬O¡A§A¤£¸Ó¦b·N¡Cµy·Lªø¤@ÂIªºµª®×¬O¡AÁöµM
§A¦³¯à¤O¦Û¤v¥h«Ø³y¤@®y¸}½ñ¨®´×¡A¦ý¬O¡A³o¤£¥Nªí¦]¬°§A¤£³ßÅw²{¦b³o
Ó¸}½ñ¨®´×ªºÃC¦â¡A´N¤¤¤î¥Lªº«Ø¿v¡C³oÓ¤ñ³ëªº·N«ä¬O¡A§A¤£»Ýn¥hª§½×
¨C¤@Ó²Ó¶µ¯S¼x¡A¥u¦]¬°§A¦³¿ìªk¥h§@¥¦¡C¬Y¨Ç¤Hªºµû½×¬O¡AÂøµªº²£¥Í«×
¹ïÅܤƪº½ÆÂø©Ê¬Û¤Ï¦a¤ñ¨Ò¡C
§óªø¥B¸û§¹¾ãªºµª®×¬O¡A¦b¸g¹Lªø®É¶¡ª§½×Ãö©ó¬O§_¸Ó±N &man.sleep.1;
ªº¬í°Ñ¼Æ²¾°£¡A&a.phk;µoªí¤F¤@½gªø½× ¤@®y¦Û¦æ¨®½´ (¥ô¦óÃC¦âªº)¦b«C¯Üªº¯ó¦a¤W...
¡C
¨º«h°T®§³Q¾A·íªº³¡¤À³Q¤Þ¥Î¦b¤U±¡C
&a.phk; on freebsd-hackers, October
2, 1999
¤°»ò¬OÃö©ó³oÓ¸}½ñ¨®´×?
³¡¤Àªº¤H³o¼Ëªº¸ß
°Ý§Ú¡C
³o¬O¤@Ó«D±`ªø»·ªº¬G¨Æ¡A§_«h´N¬O¤@Ó¥j¦Ñªº¬G¨Æ¡C¦ý¬O¨Æ¹ê¤W¡A
³oÓ¬G¨Æ«D±`ªºµu¡CC. Northcote Parkinson ¦b1960¦~¥Nªì´Á¼g¤F¤@¥»
®Ñ¡A®Ñ¦W¬° Parkinson's Law
¡A¦b³o¥»®Ñ¤¤¥]§t¤F«Ü¦h
¨ã¦³¨ô¨£ªº°ÊºAºÞ²z¾Ç¡C
[¤Þz¤@ÂI¦b³o¥»®Ñ¤Wªºµû½×]
¦b³oÓ³Q±²¤J¸}½ñ¨®´×®×ªº¯S®í¨Ò¤l¡A¥Dnªºn¯À¬O®Ö¯àµo¹q³õ¡A
§Ú·Q¡A³o¨¬¥H»¡©ú³o¥»®Ñªº¦~ÄÖ¡C
Parkinson ®i¥Ü¤F§A¸Ó¦p¦ó¦b¸³¨Æ·|¤¤Ä¹±oÃÙ¦P¥h«Ø³y¤@®y¼Æ¦Ê¸U
©Î¬Æ¦Ü¤Q»õ¬ü¤¸ªº®Ö¯àµo¹q³õ¡A¦ý¬O¡A¦pªG§A·Qn¥h«Ø³y¤@®y¸}½ñ¨®´×¡A
§A±N·|³QªÈÄñ¦bµL½aµLºÉªº°Q½×¤§¤¤¡C
Parkinson ¸ÑÄÀ¡A³o¬O¦]¬°¤@Ó®Ö¯àµo¹q³õ¬O³o¼Ëªº¼sÁï¡A³o¼Ëªº
©ù¶Q¡A¨Ã¥B³o¼Ëªº½ÆÂø¡A¥H¦Ü©ó¤H̵Lªk´x´¤¥¦¡A¦Ó¨Ã«D¹Á¸Õ¡A¥LÌ«æ
¤Áªº§Æ±æ¦³¤H¯à°÷À°¥L̳B²z¨Ã¸Ñ¨M©Ò¦³º¾¸Hªº²Ó¶µ¡C
Richard P. Feynmann µ¹¤F¤@¨Ç¦³½ì¡A¥B«D±`¤@°w¨£¦åªº½×ÂI¡A¦b¥Lªº
®Ñ´£¨ì¤F Los Alamos ªº¨Ò¤l¡C
¥t¤@¤è±¡A¥ô¦ó¤H³£¯à¦Û¤v¦b¶g¥½²Õ¸Ë¤@®y¸}½ñ¨®´×¥X¨Ó¡A¨Ã¥B¤´
¦³¶¢²á¥i¥HÆ[½à¹qµø¤Îª±¹CÀ¸¡C¦]¦¹¡AµL½×§A§@¤F¦h»ò§¹µ½ªº·Ç³Æ¡A¤]
¤£ºÞ§A´£¥Xªº¤è®×¬O¦h»òªº¦X©y¡A¬Y¨Ç¤H¤´±N§ì¦í¾÷·|¶]¥X¨Ó§i¶D§A¡A
¥L¥¿¦b§@¦P¼Ëªº¨Æ¡A¥¿¦b¥I¥X§V¤O¡A¥L´N¦b
³o¸Ì ¡C
¦b¤¦³Á¡A§Ú̺ٳoÓ¥s§@
ªê¦º¯d¥Ö(setting your fingerprint)
¡C¥¦Ãö«Y¨ì§A
Ó¤HªºÅº¶Æ©MÁn±æ¡A³oÃö«Y¨ì§A¬O§_¥i¥H«üµÛ¬Y¦a«á¹ïµÛ§O¤H»¡
³o¸Ì! ³o¬O§Ú §@ªº¡C
³o¬O¬Fªv¤Hª««Ü«nªº¤@Ó¯S¼x¡C¦ý¬O¡A®É¾÷¬O¤j¦h¼Æ¤H¥Á©Ò½á»Pªº¡C
·Q·Q¨º¨Ç¯d¦b¤ôªd¦a¤Wªº¸}¦L§a¡C
Edward
Chuang
edwardc@firebird.org.tw
The FreeBSD Funnies
How cool is FreeBSD¡H
°Ý¡G¦³¤H°µ¹L FreeBSD °õ¦æ®Éªº·Å«×´ú¸Õ¶Ü¡H §Úª¾¹D Linux
¤ñ DOS ²D¡A¦ý¨SÅ¥¤H´£¹L FreeBSD¡A¦ü¥G«Ü¼ö¡C
µª¡G¨S¦³¡A¦ý¬O¦b¨ýı¤W¦³°µ¹LµL¼Æ¦¸´ú¸Õ¡C§ÚÌé¤W¦ÛÄ@¨ü¸ÕªÌªº
²´·ú¡A¨Æ¥ý¦Aµ¹¥L̪A¥Î 250 ²@§Jªº LSD-25 °g¤ÛÃÄ¡C35% ªº¨ü¸ÕªÌ»¡
FreeBSD ¹Á°_¨Ó¹³¾ï¤l¡A¦Ó Linux «h¬Oµµ¦âªººd¾ðªG¹ê¡C¾Ú§Ú©Òª¾¡A¨S
¦³¤@²Õ´£¨ì·Å«×¤W¯S§Oªº®t²§¡C«á¨Óµo²{¡A¦³¤Ó¦h¨ü¸ÕªÌ¦b´ú¸Õ®É¹Ú¹C¨«
¥X©Ð¶¡¼vÅT¨ì¼Æ¾Ú¡A³Ì«á¥u±o©ñ±ó¾ãÓ½Õ¬d¡C§Ú·Q¤j³¡¥÷ªº¨ü¸ÕªÌ²{¦b¦b
Apple ¤u§@¡AÄ~ Drag and Drop ¤§«á¡A¬ã¨s¥þ·sªº Scratch and
Sniff
¹Ï§Î¬É±¡CIt's a funny old business we're in¡I
¤£¶}ª±¯º¤F¡AFreeBSD ©M Linux ³£¨Ï¥Î HLT
(halt) «ü¥O¥H¦b¨t²Î¶¢¸m®É°§C¹q¤Oªº¨Ï¥Î¤]´î¤Ö¤F¼öªº²£¥Í¡C¦pªG¦³
³]©w APM (automatic power management)¡AFreeBSD ¤]¥i¥HÅý CPU ¶i
¤J§C¹q¤O¼Ò¦¡¡C
½Ö¦b§Úªº°O¾ÐÅé´¡¼Ñ¤¤¨F¨F§@ÅT¡H¡H
°Ý¡GFreeBSD ½sĶ®Ö¤ß®É¦³°µ¬Æ»ò ©_¯S
ªº¨Æ
Åý°O¾ÐÅé¨F¨F§@ÅT¶Ü¡H·í½sĶ®É(ÁÙ¦³¶}¾÷®É½T»{³nºÐ«áªºµu¼È®É¶¡)¡A
¤]ºØ¦ü¥G¨Ó¦Û°O¾ÐÅé´¡¼Ñªº©_©ÇÁnµ¡C
µª¡G¬Oªº¡I¦b BSD ªº¤å¥ó¤¤§A·|±`±`¬Ý¨ì I«áÆF
¡A
¤j³¡¥÷ªº¤H³£¤£ª¾¹D¨º¬O¤@ºØ¹ê»Ú¦s¦bªººë¯«Åé --- ´x±±µÛ§Aªº¹q¸£¡C
§AÅ¥¨ìªºÁnµ¬O³o¨ÇI«áÆF¥H°ªµ¤fï¦b·¾³q«ç¼Ë°µ³\¦hªº¨t²ÎºÞ²z¤u
§@¡C
¦pªG³o¨ÇÁnµ«Ü§xÂZ§A¡A¨Ó¦Û DOS ªº
fdisk /mbr ´N¯àÂ\²æ¡A¦ý¦pªG¦³¬Û¤Ïªº®ÄªG
¤]¤£nÅå³Y¡C¨Æ¹ê¤W¡A¦pªG¦b»ö¦¡¤¤Å¥¨ì Bill Gates ®£©ÆªºÁnµ±q¤º
«Øªº³â¥z¶Ç¨Ó¡A°¨¤W°k¦Ó¥B¤£n¦^ÀY¡I ±q BSD I«áÆF¤£¥¿Åªº¼vÅT¤¤
¸Ñ©ñ¡ADOS ©M Windows I«áÆF³q±`³£¯à«·s±±¨î¾ã¥x¾÷¾¹¨Ã¹ï§AªºÆF
»î¶A©G¡C¦pªG¦³¿ï¾Ü¡A§Ú·Q§Ú¹çÄ@²ßºD©_©ÇªºÁnµ¡C
n´XÓ FreeBSD hacker ¤~¯à´«±¼¤@Ó¹q¿Oªw¡H
¤@¤d¤@¦Ê¤C¤Q¤GÓ¡G
¤G¤Q¤TÓ¦b -current ¤W©ê«è¬Ý¤£¨ì¥ú¤F¡F
¥|ӫźٳo¬O³]©w¤Wªº°ÝÃD¡A©Ò¥H¹³³o¼Ëªº email À³¸Ó©ñ¦b
-questions¡F
¤TÓ submit PR¡A¨ä¤¤¤@Ó°e¿ù¨ì doc ¤U¡A¨Ã¥B¤º®e¥u
¦³¡¨³o¸Ì¦n·t¡¨¡F
¤@Ó commit ©|¥¼´ú¸Õªº¹q¿Oªw¡A³y¦¨¤£¯à buildworld¡A
¤¤ÀÄÁ«á¥L§âì¨Óªº¿Oªw´«¦^¨Ó¡F
¤KÓº´°_ flame war¡A³d©Ç°e¥X PR ªº¤H¨S¦³¥]¬A patch¡F
¤Ó®I«è buildworld Äê±¼¤F¡F
¤T¤Q¤@Ó»¡ buildworld ¥i¥H¥Î¡A¤£¯à¥Îªº¤H¤@©w¬O cvsup ªº
®É¾÷¤£¹ï¡F
¤@ӧ⴫¦¨·s¿Oªwªº patch ¥á¨ì -hackers ¤W¡F
¤@Ó»¡¥L¤T¦~«e´N°µ¥X¤F patch¡A¦ý°e¨ì -current «á«o³Q©¿²¤±¼¡A
©Ò¥H¥L¹ï¾ãÓ PR ¨t²Î¦³«Ü¤£¦nªº¦L¶H¡C¦¹¥~¡A¥L¤]»{¬°®³¥Xªº·s¿OªwµL
ªk¤Ï¥ú¡F
¤T¤Q¤CÓ©Hý»¡¹q¿Oªw¤£ÄÝ©ó°ò¥»¨t²Îªº¤@³¡¥÷¡A©Ò¥H committer
¤£¯à¤£¥ý¿Ô¸ß¾ãÓ Community ªº·N¨£´N³o¼Ë°µ¤U¥h¡CÁÙ¦³¡A-core
¨ì©³©M³o¥ó¨Æ¦³¤°»òÃö«Y¡H¡I
¨â¦Ê¤H©ê«è´«¿Oªw¤§«á¡A¸}½ñ¨®´×ªºÃC¦âÅܱo¦n©_©Ç¡F
¤TÓ«ü¥X¡A¥Î¨Ó´«¿Oªwªº patch ¤£²Å¦X &man.style.9; ªº³W©w¡F
¤Q¤CÓ®I«è®³¥X¨Óªº·s¿Oªw¬°¤°»ò¬O¥Î GPL¡F
¤¦Ê¤K¤Q¤»¤H³´¤J¤@³õ flame war¡A¦b GPL¡BBSD¡BMIT¡BNPL
¦UÓ license ©M FSF ¬Y¦ì¤£¨ã¦W³Ð¿ì¤H¤hÓ¤H½Ã¥Í¤§¶¡¡A¤ñ¸û©¼¦¹
ªºÀu¶Õ¡F
¤CÓ±N³o¤@¦ê°Q½×ªº¤£¦P³¡¥÷¤À§O²¾¨ì -chat ©M -advocacy¡F
´Nºâ´£¥Xªº·s¿Oªw¤ñªº·t¡AÁÙ¬O¦³¤@ӧ⥦ commit ¶i¨Ó¡F
¨âÓ´«¦^ì¥ýªº¿Oªw¡A¨Ã¥B¯d¤U·¥¬°¼««ãªº commit °T®§¡C¥LÌ»{¬°
»P¨äÅý FreeBSD ¥Î·t¿Oªw¡AÁÙ¤£¦p°®¯Ü«Ý¦b¶Â·t¤¤ºâ¤F¡F
¥|¤Q¤»¤H¹ï¨ú®ø¤£¥Î·t¿Oªw³o¥ó¨Æ¤jÁn¯e©I¡An¨D -core
¥ß¨è´£¥X¼á²M¡F
¤Q¤@Ón¨D´«¦¨¤p¤@ÂIªº¹q¿Oªw¡A¥H«K¥¼¨Ó FreeBSD ¦pªG²¾´Ó¨ì
¹q¤lÂû¤W«á·|§ó¬°¤è«K¡F
¤C¤Q¤T¤H©ê«è -hackers ©M -chat ¤Wªº SNR¡AÂÇ unsubscribe
¨Óªí¥Ü§Üij¡F
¤Q¤TÓ°e¥X¡¨unsubscribe¡¨¡B¡¨§Ún¦p¦ó unsubscribe¡¨©Î¡¨«ô°U§â
§Ú±q list ¦W³æ¤¤§R±¼¡¨¡A«Hªº³Ì«á±«h¬O¤@¯ë¥Ñ majordomo ¥[¤W¥h
ªº footer¡F
·í¨CÓ¤H¦£©ó©¼¦¹¥s½|®É¡A¦³Ó³Ã¥ë¶X¨S¤Hª`·N¡A§â¥i¥H¥Îªº¿Oªw°½
°½´«¤W¥h¡F
¤T¤Q¤@Ó«ü¥X¦pªG¥Î TenDRA ½sĶ·sªº¿Oªw¡A·|¤ñªº¨Ó±o«G
0.364%¡]ÁöµM¿Oªw·|³Q½sĶ¦¨¥¿¤»±Åé¡^¡A©Ò¥H FreeBSD ¤º©wªº½sĶ¾¹
À³¸Ó¬O TenDRA¡A¦Ó¤£¬O EGCS¡F
¦³Ó¤H»¡·s¿Oªw¯Ê¥F¬ü·P¡F
¤EÓ¤H¡]¥]¬Aì¥ý°e PR ªº¤H¡^°Ý¡¨¤°»ò¬O MFC¡H¡¨¡F
¤¤Q¤CÓ©ê«è¦Û±q´«¤F¿Oªw«á¡A¨âÓ¬P´Á³£¨S¦³¥ú¥X²{¡C
&a.nik; ¸Éª`¡G
è¬Ý¨ì®É¡A§Ú§Ö¯ºÂ½¤F¡C
µM«á·Q¨ì¡A¡¨µ¥¤@¤U¡A¤£¬OÀ³¸ÓÁÙ¦³¤@Ón±N³o¨Ç°O¦b
list ¤W¶Ü¡H¡¨
±µµÛ²×©ó¤F¸Ñ§Úªº¨Ï©R :-)
¼g¤J /dev/null ªº¸ê®Æ¶]¨ìþ¸Ì¥h¤F¡H
¦b CPU ¤¤¦³¤@ºØ¯S§Oªº¸ê®Æ´²¼ö¾¹¡A§Q¥Î±Æ¥X´²¼ö¤ù/·®°²Õ¦X®É¡A
Âà´«¦¨¼ö¯à¡D³o´N¬O¬°¤°»ò CPU §N«o¤éÁÍ«nªºì¦]¡F·í¤H̨ϥΧó§Ö
ªº³B²z¾¹®É¡A¥LÌÅܦ¨¤£¦b¥G¦³¶V¨Ó¶V¦h¥L̪º¸ê®Æ³£°e¶i¤F
/dev/null ¡A¦Ó¨Ïªº¥L̪º CPU ¹L¼ö¡D
¦pªG§A§R°£¤F /dev/null (¨º±N·|¦³®ÄªºÃö³¬
CPU ªº¸ê®Æ´²¼ö¾¹) §Aªº CPU ¤]³\·|°§C¤u§@·Å«×¡A¦ý¬O§Aªº¨t²Î±N
·|«Ü§Öªº¹³¬O¿©±w¤F«K¯µ¦ñÀHµÛ©Ò¦³¶W¥Xªº¸ê®Æ¶}©lÅܦ¨¦æ¬°¤£¥¿±`¡C
¦pªG§A¦³§Ö³tªººô¸ô³s½u¡A§A¥i¥H§Q¥ÎŪ¨ú
/dev/random ¨Ã±N¥LÀH·N¶Ç°e¦Ü¦U³B¡A
¨Ó°§C§A CPU ªº·Å«×¡FµM¦Ó§A±N³´¤J¨Ï§Aºô¸ô³s½u©Î
/ ¦³¹L¼öªº·ÀI©Î¬O·S´o§Aªº ISP¡A
¤j³¡¤Àªº¸ê®Æ³Ì²×±N·|¦b¥L̪º³]³Æ¤WÂà´«¦¨¼ö¡A¤£¹L¥L̳q±`³£¾Ö¦³
¦nªº´²¼ö¡A©Ò¥H¦pªG§A°µªº¤£¤Ó¹L¤À¡AÀ³¸Ó¬O¨S¤°»ò¤j¤£¤Fªº¡C
Paul Robinson ¸É¥R¡G
¤¤¤åª© FAQ ª`¡G¥H¤Uµu¤åÄÝ©ó¬ü¦¡«ÕÀq¡A®£Â½Ä¶«á³y¦¨»y²j¤£¸Ô¡A
»y·N¤£³qªº±¡§Î¡A©T«O¯dì¥Äì¨ýÅýŪªÌ¦Û¦æ«~À|¡C
There are other methods. As every good sysadmin knows,
it is part of standard practise to send data to the screen
of interesting variety to keep all the pixies that make up
your picture happy. Screen pixies (commonly mis-typed or
re-named as 'pixels') are categorised by the type of hat
they wear (red, green or blue) and will hide or appear
(thereby showing the colour of their hat) whenever they
receive a little piece of food. Video cards turn data into
pixie-food, and then send them to the pixies - the more
expensive the card, the better the food, so the better
behaved the pixies are. They also need constant simulation
- this is why screen savers exist.
To take your suggestions further, you could just throw
the random data to console, thereby letting the pixies
consume it. This causes no heat to be produced at all,
keeps the pixies happy and gets rid of your data quite
quickly, even if it does make things look a bit messy on
your screen.
Incidentally, as an ex-admin of a large ISP who
experienced many problems attempting to maintain a stable
temperature in a server room, I would strongly discourage
people sending the data they do not want out to the
network. The fairies who do the packet switching and
routing get annoyed by it as well.
En-Ran
Zhou
zhouer@tfcis.org
¶i¶¥¥DÃD
¦p¦ó¯à¾Ç²ß§ó¦h¦³Ãö FreeBSD ¤º³¡ªºªF¦è¡H
¥Ø«e¥«±¤WÁÙ¨S¦³±´°Q§@·~¨t²Î¤º³¡ªº®Ñ¬O±M¬° FreeBSD ¦Ó¼g
ªº¡CµM¦Ó¡A³\¦h¤@¯ëªº UNIX ª¾Ãѳ£¥i¥Hª½±µÀ³¥Î¦b FreeBSD ¤W¡Cªþ
¥[¤@ÂI¡A¤´µM¦³¬ÛÃöªº®Ñ¬O±M¬° BSD ©Ò¼gªº¡C
½Ð°Ñ¦Ò Handbook ªº§@·~¨t²Î¤º³¡¤§°Ñ¦Ò®Ñ¥Ø
¡C
¦p¦ó¯à¬° FreeBSD ¥X¤@¥÷¤O¡H
½Ð°Ñ¦Ò³o½g¤å³¹ Contributing
to FreeBSD ¨Ó´£¨Ñ±zªº«Øij¡C¦pªG±z¯àÀ°¦£¨º´N§óÅwªï¤F¡I
SNAP ©M RELEASE ¬O¤°»ò¡H
¥Ø«e¦³¤TÓ¬¡ÅD/¥b¬¡ÅDªº¤À¤ä¦b FreeBSD ªº CVS Repository
(RELENG_2 ¤À¤ä¤@¦~¤j·§§ó°Ê¨â¦¸¡A¥¿¬O¬°¦ó¥u¦³¤TÓ¬¡ÅDªºµo®i¤¤¤À¤ä)¡G
RELENG_2_2 §Y
2.2-STABLE
RELENG_3 §Y
3.X-STABLE
RELENG_4 §Y
4-STABLE
HEAD §Y
-CURRENT §Y
5.0-CURRENT
¦p¦P¨ä¥L¨âÓ¡AHEAD ¨Ã¤£¬O¯u¥¿
ªº branch tag¡A¥¦¥u¬O¤@ӲŸ¹±`¼Æ¡A«ü¦V current
(©|¥¼¤À¤äªºµo®i¤¤ª©¥»)
²°O¬°
-CURRENT
¡C
¥H²{¦b¨Ó»¡¡A-CURRENT
´Â¦V 5.0 µo®i¡A¦Ó
4-STABLE ¤À¤ä¡A¤]´N¬O
RELENG_4 ¡A¦b 2000 ¦~¤T¤ë±q
-CURRENT
¤À¤ä¥X¨Ó¡C
2.2-STABLE ³oÓ¤À¤ä¡A¤]´N¬O
RELENG_2_2 ¡A¦b 1996 ¦~¤Q¤@¤ë±q -CURRENT ¤À¤ä¥X
¨Ó¡A³oÓ¤À¤ä¥Ø«e¤w¸g§¹¥þ°h¥ð¤F¡C
n«ç»ò§@¥X¦Û¤vªº release¡H
½Ð°Ñ·Ó Release ¤uµ{
¤å³¹»¡©ú¡C
¬°¤°»ò make world §âì¨Ó¸Ëªº binary ÀÉ
³£´«±¼¤F¡H
¨S¿ù¡A´N¬O³o¼Ë¤l¡C¦p¦W¦r©Ò¥Ü¡Amake world
·|«·s½sĶ¨t²Î¤º«Øªº¨CÓ binary ÀÉ¡A³o¼Ë¦bµ²§ô®É´N¥i½T©w¦³Ó¤@P
¥B°®²bªºÀô¹Ò(©Ò¥Hnªá¤W¦n¤@¬q®É¶¡)¡C
¦b°õ¦æ make world ©Î
make install ®É¡A¦pªG¦³³]
DESTDIR ³oÓÀô¹ÒÅܼơA·s²£¥Íªº binary ±N·|¸Ë¦b
${DESTDIR} ¤U¦P¼Ëªº¥Ø¿ý¾ð¤¤¡C¦ý¦b¬Y¨Çקï
shared library ©M««Ø binary ªºµL¯S©w±¡ªp¤U¡A³o¼Ë°µ¥i¯à·|¨Ï
make world ¥¢±Ñ¡C
¦b¨t²Î¶}¾÷®É¡A¥X²{ (bus speed defaulted)
¡C
Adaptec 1542 SCSI ¥d¤¹³\¨Ï¥ÎªÌ¥Î³nÅé½Õ¾ã¶×¬y±Æªº¦s¨ú³t«×¡C
¦´Áªº 1542 ÅX°Êµ{¦¡¸Õ¹Ï±N¥¦³]¦¨¥i¥Îªº³Ì§Ö³t«×¡A¦ý«á¨Óµo²{¦b¤@
¨Ç¾÷¾¹¤W¤£¯à¥Î¡A©Ò¥H²{¦bn¦b kernel ³]©w¤¤¥[
TUNE_1542 ³oӿﶵ¨Ó±Ò°Ê³oÓ¥\¯à¡C¦b¤ä´©ªº¾÷¾¹
¤W¥Î³oӿﶵ·|¨ÏµwºÐ¦s¨ú§ó§Ö¡A¦ý¦b¤£¤ä´©ªº¾÷¾¹¤W¦³¥i¯à·|·´±¼¸ê®Æ¡C
¦bºô¸ôÀW¼e¦³ªº±¡ªp¤U¡A§Ú¤]¥i¥H¸ò¤W current ªºµo®i¶Ü¡H
¬Oªº¡AÂÇµÛ CTM
±z´N¥i¥H¤£¥Î ¤U¸ü¥þ³¡ªºµ{¦¡½X¡C
¬O«ç»ò§âµo¦æª©¥»¤¤ªºÀɮפÁ¦¨¤@ÓÓ 240k ªº¤pÀɮתº¡H
¥H BSD ¬°°ò¦ªº¸û·s¨t²Î¦³Ó -b ¿ï¶µ
¥i¥H§âÀÉ®×¥H¥ô·N¼Æ¥Ø byte ¤Á¶}¡C
³o¸Ì¬O /usr/src/Makefile ¤¤ªº¤@Ó
¨Ò¤l¡G
bin-tarball:
(cd ${DISTDIR}; \
tar cf - . \
gzip --no-name -9 -c | \
split -b 240640 - \
${RELEASEDIR}/tarballs/bindist/bin_tgz.)
§Ú¦b kernel ¤¤¥[¤F·s¥\¯à¡A§Ún§â¥¦±Hµ¹½Ö¡H
½Ð°Ñ¦Ò Contributing
to FreeBSD ¤¤ªº¤å³¹¡A¥H¤F¸Ñn¦p¦ó´£¨Ñ±zªºµ{¦¡½X¡C
¦P®É¤]ÁÂÁ±zªºÃö¤ß¡I
ISA ªºÀH´¡§Y¥Î¥d¬O¦p¦ó°»´ú¤Îªì©l¤Æªº¡H
¥Ñ Frank Durda IV ©Ò¼g¡G
uhclem@nemesis.lonestar.org
²³æªº»¡¡A·í¥D¾÷µo¥X¬O§_¦³ PnP ¥dªº¸ß°Ý°T¸¹®É¡A©Ò¦³ªº PnP ¥d
·|¦b´XÓ©T©wªº I/O port §@¦^À³¡C©Ò¥H·í°»´ú PnP ªºµ{¦¡¶}©l®É¡A¥¦
·|¥ý°Ý¦³¨S¦³ PnP ¥d¦b¡A±µµÛ©Ò¦³ PnP ¥d·|¦b¥¦Åªªº port ¥H¦Û¤vªº
«¬¸¹ # §@¦^µª¡A³o¼Ë°»´úµ{¦¡´N·|±o¨ì¤@Ó wired-OR yes
ªº¼Æ¦r¡A¨ä¤¤¦Ü¤Ö·|¦³¤@Ó bit ¬O¥´¶}ªº¡CµM«á°»´úµ{¦¡·|n¨D«¬¸¹
(¥Ñ Microsoft/Intel«ü©w)¤p©ó X ªº¥dÂ÷½u
¡C¦A¥h¬Ý¬O
§_ÁÙ¦³¥d¦^µª¦P¼Ëªº¸ß°Ý¡A¦pªG±o¨ì 0 ¡A´Nªí¥Ü¨S
¦³«¬¸¹¤j©ó X ªº¥d¡C ²{¦bµ{¦¡·|°Ý¬O§_¦³«¬¸¹¤p©ó X
ªº¥d¡A¦pªG¦³ªº¸Ü¡Aµ{¦¡¦An«¬¸¹¤j©ó X-(limit/4) ªº¥dÂ÷½u¡AµM«á«ÂÐ
¤W±ªº°Ê§@¡C¥Î«½Æ³oºØÃþ¦ü semi-binary search ªº¤èªk¡A¦b¬Y½d³ò¤º
§äÓ´X¦¸«á¡A´úµ{¦¡³Ì«á·|¦b¾÷¾¹¤¤°Ï¤À¥X©Ò¦³ªº PnP ¥d¡A·j´M¦¸¼Æ¤]
»·§C©ó¤@Óӧ䪺 2^64 ¦¸¡C
¤@±i¥dªº ID ¥Ñ¨âÓ 32-bit(©Ò¥H¤W±¬O 2ˆ64) + 8bit °»¿ù½X
²Õ¦¨¡A²Ä¤@Ó 32 bits ¬O¥Î¨Ó°Ï¤À¦U®a¼t°Óªº¡C³o¨Ç¼t°Ó±q¨Ó¨S¦³¥X¨Ó¼á
²M¹L¡A¦ý¬Ý¨ÓÀ³°²³]¦P¤@®a¥Xªº¤£¦PºØÃþªº¥dªº¼t°Ó ID ¦³¥i¯à¤£¦P¡C¥Î
32 bits ¥u¨Óªí¥Ü¤£¦P¼t°Óªº·Qªk¹ê¦b¦³ÂI¹LÀY¤F¡C
²Ä¤GÓ 32 bits «h¬O«¬¸¹ #¡B¤A¤Óºô¸ô¦ì§}¡B©Î¤@¨Ç¨Ï³o±i¥d¿W¯Sªº
¸ê®Æ¡C°£«D²Ä¤@Ó 32 bits ¤£¦P¡A§_«h¼t°Ó¤£¥i¯à§@¥X²Ä¤GÓ 32 bit ¬Û
¦Pªº¨â±i¥d¡C©Ò¥H¦b¤@¥x¾÷¾¹¤¤¥i¥H¦³¦P¼Ëªº¦n´X±i¥d¡AµM¦Ó¥L̾ãÓ
64 bits ÁÙ¬O·|³£¤£¤@¼Ë¡C
³o¨âÓ 32 bit µ´¹ï¤£¥i¥H¥þ¬°¹s¡A³o¤~¯à¨Ï±o³Ì¶}©l binary search
¤¤ªº wired-OR ·|±o¨ì¤@Ó«D¹s¼Æ¦r¡C
¤@¥¹¨t²Î°Ï¤À¥X©Ò¦³¥dªº ID¡A±µµÛ·|¸g¥Ñ¦P¼Ëªº I/O port ¤@ÓÓ«
·s±Ò°Ê¨C±i¥d¡A±µµÛ§ä¥X¤wª¾¤¶±¥d©Ò»Ýªº¸ê·½¡B¦³þ¨Ç¤¤Â_¥i¥H¨Ï¥Îµ¥
µ¥¡C©Ò¦³¥d³£·|³Q±½´y¤@¦¸¡A¨Ó¦¬¶°³o¨Ç¸ê®Æ¡C
³o¨Ç¸ê°T±µµÛ©MµwºÐ¤Wªº ECU ÀɮסB©Î MLB BIOS ¸Ìªº¸ê®Æµ²¦X¦b¤@
°_¡A³q±`¬Oºî¦X ECU ©M MLB ¸Ìªº BIOS PnP ¸ê®Æ¡A³o¨Ç¶gÃä¨Ã¤£¤ä´©¯u¥¿
ªº PnP¡AµM¦Ó°»´úµ{¦¡¦bÀˬd BIOS ©M ECU ¸ê®Æ«á¡A¥¦¥i¥HÁקK PnP ¶gÃä
©M¨º¨Ç°»´ú¤£¨ìªº¬Û½Ä¬ð¡C
±µµÛ¦A«×«ô³X³o¨Ç PnP ¶gÃä¡A³o¦¸·|§â¥i¥Îªº I/O¡BDMA¡BIRQ ©M°O¾Ð
Åé¬M®gªº¦ì§}³£«ü©wµ¹¥¦Ì¡C³o¨Ç¶gÃä´N·|¥X²{¦b©Ò«ü©wªº¦a¤è¡Aª½¨ì¤U¤@
¦¸«·s¶}¾÷¬°¤î¡A¤£¹L¤]¨S¦³¤H»¡¤£¯à§â¥¦ÌÀH®É²¾¨Ó²¾¥h¡C
¤W±¦³¬Û·í¦hªºÂ²¤Æ¡A¦ý§AÀ³¸Ó¤w¸g¤F¸Ñ¤jPªº¹Lµ{¡C
Microsoft §âªí¥Ü¦Lªí¾÷ª¬ºAªº´XÓ¥Dn port ®³¨Ó§@ PnP¡A¥L̪º
ÅÞ¿è¬O¨S¦³¤@±i¥d·|¦b³o¨Ç¦a¤è¸Ñ½X§@¬Û¤Ïªº I/O cycles¡C¦ý¬O§Ú§ä¨ì
¤@´Ú¦´Á¤´¦bµû¦ô PnP ´£®×®Éªº IBM ì¼t printer board¡A¥¦ªº½T¥h¸Ñ
¹ï³o¨Çª¬ºA port ªº¼g¤J¸ê®Æ¡A¦ý¬O MS »¡¤F´Nºâ
¡C©Ò¥H
¥¦Ìªº½T¦³¹ï¦Lªí¾÷ª¬ºA port ¼g¤J¡AÁÙ¦³Åª¨ú¸Ó¦ì§} +
0x800 ¡B©M¥t¤@Ó¦b 0x200 ¤Î
0x3ff ¤§¶¡ªº port¡C
§Ú¬°¬Y³]³Æ¼g¤FÅX°Êµ{¦¡¡A¯à¤£¯àµ¹¥¦¤@Ó major number¡H
³on¬Ý§A¬O§_¥´ºâ±N³oÓÅX°Êµ{¦¡¤½¶}¨Ï¥Î¡A¦pªG¬Oªº¸Ü¡A½Ð§â¥¦ªº
ì©l½X°e¤@¥÷µ¹§ÚÌ¡AÁÙ¦³ files.i386 ק諸
³¡¥÷¡Bkernel ³]©wÀɼ˥»¡B¥H¤Î¥Î¨Ó²£¥Í³]³ÆÀɪº &man.MAKEDEV.8;¡C
¦pªG§A¤£¥´ºâ¤½¶}¡B©Î¦]¬°ª©Åv°ÝÃD¦Ó¤£¯à¤½¶}ªº¸Ü¡A§Ú̦³¯S¦a«O¯d
character major number 32 ©M block major number 8 µ¹³o¤è±ªº¨Ï¥Î¡A
ª½±µ¥Î³o¨âÓ´N¦n¤F¡C¤£½×¦p¦ó¡A§Ú̳£·|«Ü·P¿E§A¯à¦b &a.hackers;
µoªíÅX°Êµ{¦¡ªº®ø®§¡C
Ãö©ó§ó°Ê¥Ø¿ý©ñ¸mªºì«h¡H
¦b¦^µªÃö©ó§ó°Ê¥Ø¿ý©ñ¸mªºì«h¤è±¡A§Ú¦b 1983 ¦~¼g¦n¥Ø«eªº§@ªk
«á´N¨S¦³¦A§ïÅܹL¡A³oºØ¤è¦¡¬O°w¹ïì¥ýªº FFS Àɮרt²Î¡A«á¨Ó¤]¨S¦³
¹ï¥¦§@¥ô¦ó§ó°Ê¡C¥¦¦bÁקK cylinder group ³Q¶ñº¡³o¤è±°µ±o¬Û·í¦¨¥\¡A
¦ý¬O´N¹³¦³¨Ç¤H¤w¸gª`·N¨ì¡A¥¦©M find ´N°t¦X±o¤£¤j¦n¡C¤j³¡¥÷ªºÀÉ®×
¨t²Î¬O¥Ñ¨º¨Ç¥Î depth first search(aka ftw) ²£¥Íªº archive »s³y¥X
¨Ó¡A¸Ñ¥X¨Óªº¥Ø¿ý inode ·|¾î¸ó¦n´XÓ cylinder group¡A¦pªG¥H«án°µ
depth first search ªº¸Ü¡A³o¬O³ÌÁV¿|ªº±¡ªp¤§¤@¡C¦pªG§Ú̪¾¹DÁ`¦@
·|²£¥Í¦h¤Ö¥Ø¿ýªº¸Ü¡A¸Ñªk¬O¦b°µ¥ô¦ó¦s¨ú/¼g¤J°Ê§@¤§«e¡A¦b¨CÓ
cylinder group ¤W¥ý³y¥X(©Ò¦³¥Ø¿ý¼Æ/cylinder greoup ªº¼Æ¥Ø)³o»ò¦h
ªº¥Ø¿ý¡C«Ü©úÅ㪺¡A§ÚÌ¥²¶·n¦³®Ú¾Ú¦a¥h²q³o ӼƦr¡A´Nºâ¤@Ó¹³ 10
ªº«Ü¤p©T©w¼Æ¥Ø¤]·|¨Ï®Ä²v¥H¯Å¼Æ¦¨ªø¡C°Ï¤À restore (§Y¸Ñ¶}¤Wzªº
archive) ©M¤@¯ëÀÉ®×¾Þ§@ªº¤èªk¥i¥H¬O(²{¦b¥Îªººtºâªk¥i¯àn§ó±Ó·P)¡G
¦pªG¤@¨Ç¥Ø¿ý(³Ì¦h 10 Ó)³£¦b 10 ¬í¤º²£ ¥Íªº¸Ü¡A¨º»ò´N§â³o¨Ç¥Ø¿ý
»E¶°¦b¦P¤@Ó cylinder group¡C¤£ºÞ«ç¼Ë¡A §Úªº¸gÅç«ü¥X³o¬O¤@Ó¤w¸g
¥R¥÷¹êÅç¹Lªº³¡¥÷¡C
Kirk McKusick, September 1998
¦p¦ó¦b kernel panics ®É±o¨ì³Ì¦hªº¸ê°T¡H
[³o¸`¬O±q &a.wpaul; ¦b freebsd-current mailing list ¤Wµoªíªº«H¤¤¸`¿ý¡A
&a.des; ×¥¿¤F¥´¦r¿ù»~¡B¦A¥[¤W¬A©·¸Ìªºª`¸Ñ¡C]
From: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Subject: Re: the fs fun never stops
To: Ben Rosengart
Date: Sun, 20 Sep 1998 15:22:50 -0400 (EDT)
Cc: current@FreeBSD.org
[Ben µoªí¤F¤U±ªº panic °T®§]
> Fatal trap 12: page fault while in kernel mode
> fault virtual address = 0x40
> fault code = supervisor read, page not present
> instruction pointer = 0x8:0xf014a7e5
^^^^^^^^^^
> stack pointer = 0x10:0xf4ed6f24
> frame pointer = 0x10:0xf4ed6f28
> code segment = base 0x0, limit 0xfffff, type 0x1b
> = DPL 0, pres 1, def32 1, gran 1
> processor eflags = interrupt enabled, resume, IOPL = 0
> current process = 80 (mount)
> interrupt mask =
> trap number = 12
> panic: page fault
·í§A¬Ý¨ì¹³³o¼Ëªº°T®§®É¡A¥u§â¥¦«þ¤@¥÷°e¤W¨Ó¬O¤£°÷ªº¡C§Ú¦b¤W±
¯S¦a¼Ð©úªº instruction pointer Ȭ۷í«n¡A¤£©¯ªº¬O¥¦·|¦]³]©w¦Ó
¤£¦P¡C´«¥y¸Ü»¡¡A³oÓÈ·|¸ò§A¥Îªº kernel image ÀɦÓÅÜ°Ê¡C¦pªG¬O¥Î
¬YÓ snapshot ª©¥»ªº GENERIC kernel¡A¤]³\¨ä¥L¤H¥i¥H°lÂܨì¥X°ÝÃD
ªº¨ç¦¡¡A¦ý¦pªG§A¬O¥Î¦Ûqªº kernel¡A¨º»ò¥u¦³
§A ¤~¯à§i¶D§ÚÌ°ÝÃD¥X¦b¨º¸Ì¡C
n°µªº¨Æ¥]¬A³o¨Ç¡G
§â instruction pointer ªºÈ°O¤U¨Ó¡Cª`·N¦b«e±ªº
0x8: ¦b³oÓ±¡ªp¤¤¨Ã¤£«n¡A§ÚÌnªº¬O
0xf0xxxxxx ¡C
·í¨t²Î«·s¶}¾÷«á¡A°õ¦æ³o¹D©R¥O¡G
&prompt.user; nm -n /(³y¦¨ panic ªº kernel ÀÉ®×) | grep f0xxxxxx
¨ä¤¤ f0xxxxxx ´N¬O°O¤U¨Óªº
instruction pointer È¡C¦³¥i¯à¤£·|è¦n§ä¨ì§¹¾ãªº³oÓ¦r¦ê¡A
³o¬O¦]¬° kernel symbol table ¸Ìªº¦UÓ symbol ¥u¬O¨ç¦¡ªº¶i
¤JÂI¡A¦ý instruction pointer ©Ò«üªº¦ì§}¦³¥i¯à¬O¦b¨ç¦¡¤ºªº
¬Y¤@³B¡A¦Ó¤£¤@©w¦b¶}ÀY¡C©Ò¥H¦pªG§ä¤£¨ì¾ãÓ¦r¦ê¡A¨º»ò§â
instruction pointer Ȫº³Ì«á¤@ӼƦr®³±¼¡A¦A¸Õ¤@¦¸¡G
&prompt.user; nm -n /(³y¦¨ panic ªº kernel ÀÉ®×) | grep f0xxxxx
¦pªG³o¼Ë¤]§ä¤£¨ì¡A¨º´N§â¥t¤@ӼƦr¥h±¼¦A§ä¡A¤@ª½«½Æ¨ì§ä¨ì
¬°¤î¡A µ²ªG¬O¤@¦ê¥i¯à³y¦¨ panic ªº¨ç¦¡¦Cªí¡C³o¼Ë¤ñª½±µ§ä¨ì
¥X°ÝÃDªº¨ç¦¡¨Ó±o®t¡A¦ý¦Ü¤Ö¦n¹L¤°»ò³£¨S¦³¡C
§Ú±`±`¬Ý¨ì¤HÌÅã¥Ü¤@¤j¤ù panic °T®§¡A¦ý«Ü¤Ö¬Ý¨ì¦³¤Hªá¤@ÂI®É¶¡
§â instruction pointer ©M kernel symbol table ¤¤ªº¨ç¦¡¤ñ¸û¤@¤U¡C
n°lÂÜ¥X³y¦¨ panic ì¦]ªº³Ì¦n¤èªk¬O¥ý°µ¥X crash dump¡AµM«á¥Î
&man.gdb.1; ¦b¤W±°µ stack trace¡C
¤£ºÞ¬O¨º¤@ºØ¡A§Ú³q±`¬O¥Î³oÓ¤èªk¡G
¼g¦n kernel ³]©wÀÉ¡C¦pªG§A»Ýn¥Î kernel debugger¡A¦b³]
©wÀɤ¤¥[¤W options DDB ³oӿﶵ¡C
(·í§ÚÃhºÃ¦³¥X²{µL½a°j°é®É¡A³q±`·|¥Î³oÓ¨Ó³]©w¤¤Â_ÂI¡C)
¥Î config -g
KERNELCONFIG
°µ¥X¥Î¨Ó½sĶªº¥Ø¿ý¡C
cd /sys/compile/
KERNELCONFIG ; make
µ¥«Ý kernel ½sĶµ²§ô¡C
make install
«·s¶}¾÷
&man.make.1; ±N·|»s³y¥X¨âÓ kernel¡Ckernel
ÁÙ¦³ kernel.debug ¡C
kernel ±N·|³Q¦w¸Ë¨ì
/kernel ¡A¦Ó kernel.debug
¥i¥Î¨Óµ¹ &man.gdb.1; ·í§@ debugging symbols ªº¨Ó·½¡C
n½T©w¯à§ì¨ì crash dump¡A¥ý½s¿è
/etc/rc.conf ±N dumpdev «ü
¨ì swap ¤À³Î°Ï¡C³o¼Ë &man.rc.8; ·|¥Î &man.dumpon.8; ¨Ó±Ò°Ê
crash dump¡A§A¤]¥i¥H¤â°Ê°õ¦æ &man.dumpon.8; ¦b panic ¤§«á¡A
crash dump ¥i¥H¥Î &man.savecore.8; ¦s°_¨Ó¡F¦pªG
/etc/rc.conf ¸Ì¦³³] dumpdev
¨º»ò«·s¶}¾÷«á &man.rc.8; ·|¦Û°Ê°õ¦æ &man.savecore.8; §â
crash dump ¦s¦b /var/crash ¡C
FreeBSD ªº crash dump ³q±`©M¾÷¾¹¸Ìªº¹ê»Ú°O¾ÐÅé¤@¼Ë¤j¡A´N
¹³¦pªG¦³ 64MB °O¾ÐÅé¡Acrash dump ¤j¤p´N¬O 64MB¡C©Ò¥Hn½T©w
/var/crash ¤U¦³¨¬°÷ªºªÅ¶¡¡A©Î¬O¥i¥H¤â
°Ê°õ¦æ &man.savecore.8; §â crash dump ©ñ¨ì¥t¤@ӪŶ¡¸û°÷ªº
¥Ø¿ý¤U¡C¥t¤@ºØ¤]³\¥i¥H¨î crash dump ªº¤èªk¡A¬O¦b kernel
³]©wÀɤ¤¥Î options MAXMEM=(foo) ¡A±N kernel
¥i¥Îªº°O¾ÐÅé¨î¦b¦X²zªº¤j¤p¡CÁ|¨Ò¨Ó»¡¡A¦pªG§A¦³ 128MB ªº°O¾Ð
Åé¡A¦ý¬O¥i¥H¨î kernel ¥u¯à¥Î 16MB ªº°O¾ÐÅé¡A³o¼Ë crash dump
´N¬O 16MB ¦Ó¤£¬O 128MB ¤F¡C
¤@¥¹µo²{¦³¤F crash dump¡A´N¥i¥H¥Î &man.gdb.1; ¨Ó°µ
stack trace ¡A¦p¤U©Ò¥Ü¡G
&prompt.user; gdb -k /sys/compile/KERNELCONFIG/kernel.debug /var/crash/vmcore.0
(gdb) where
nª`·N¥i¯à·|¥X²{¦n´Xӿùõªº¥i¥Î¸ê°T¡A§A¥i¥H¥Î &man.script.1;
§â©Ò¦³¿é¥X³£¦s°_¨Ó¡C¥Î¥]¬A©Ò¦³ debug symbol ªº kernel ¨Ó°£¿ù¡A³o
¼ËÀ³¸Ó¥i¥Hª½±µÅã¥Ü panic ¬Oµo¥Í¦b¨º¤@¦æ¡C³q±`¬O¥Ñ¤U©¹¤WŪ
stack strace¡A³o¼Ë¤~¯à¤@ÓÓ°lÂÜ¥X¦³þ¨Ç°Ê§@¤Þ¨ì crash¡C¤]¥i¥H¥Î
&man.gdb.1; §â¦UºØÅܼƩε²ºcªº¤º®e¦L¥X¨Ó¡A¥HÀˬd¨t²Î crash ®Éªº
¹ê»Úª¬ºA¡C
¦n°Õ¡A¦pªG§A¦³²Ä¤G¥x¹q¸£¦Ó¥B¦³°÷ºÆ¨g¡A¥i¥H±N &man.gdb.1; ³]©w
¦¨»·ºÝ°£¿ù¡C³o¼Ë§A¥i¥H¦b¤@¥x¾÷¾¹¤¤¥Î &man.gdb.1; ¥h°£¿ù¥t¤@¥x¸Ìªº
kernel¡A¥i¥H°õ¦æªº¥]¬A³]©w¤¤Â_ÂI¡B¦b kernel ì©l½X¤¤¤@¨B¨B°õ¦æµ¥
µ¥¡A´N¹³¦b¤@¯ë¨Ï¥ÎªÌµ{¦¡¤W°£¿ù¤@¼Ë¡C¥Ñ©ó¨S¦³¤°»ò¾÷·|¬°°£¿ù¦Ó³]¸m
¨â¥x¨Ã¾F¹q¸£¡A©Ò¥H§ÚÁÙ¨S¦³³o¼Ëª±¹L¡C
[Bill ¸É¥R¡G"§Ú§Ñ¤F´£¨ì¤@ÂI¡G¦pªG§A¦³±Ò°Ê DDB ¦Ó
kernel ¤]¤w¸g¶i¤J°£¿ù¾¹¡A¥i¥H¦b DDB ©R¥O¦C¤U¥´ 'panic'¡A±j¢²£¥Í
panic (ÁÙ¦³ crash dump)¡C¤]¦³¥i¯à¦b panic ¶¥¬q®É¦A¶i¤J°£¿ù¾¹¡A
¦pªG³o¼Ëªº¸Ü¡A¿é¤J 'continue'¡A±µµÛ¥¦´N·|§¹¦¨ crash dump¡C" -ed]
¬°¤°»ò dlsym() ¤£¯à¾Þ§@ ELF °õ¦æÀÉ¡H
¦b ELF ¤@¨t¦Cªº¤u¨ã¤¤¡A¤º©w¬O¤£·|Åý dynamic linker ¬Ý¨ì°õ¦æ
Àɸ̩w¸q¤Fþ¨Ç symbol¡C©Ò¥H dlsym() ¨S¦³¿ì
ªk¥ÎÂǥѩI¥s dlopen(NULL, flags) ¨ú±oªº
handle¡A¥Î¥¦¥h·j´M¦³¨º¨Ç symbol ¤@©w·|¥¢±Ñ¡C
¦pªG§A·Qn¥Î dlsym() §ä¥X¬YÓ process
ªº¥D°õ¦æÀɤ¤¦³þ¨Ç symbol¡A«hn¦b link ®É¹ï ELF linker (&man.ld.1;)
¥[¤W -export-dynamic ³oӰѼơC
§Ún¦p¦ó¼W¥[©Î´î¤Ö kernel ¯à©w§}ªºªÅ¶¡¡H
¹w³]ȬO¡AFreeBSD 3.x ªº kernel ¥i¥H©w§}ªºªÅ¶¡¬O 256 MB ¦Ó
FreeBSD 4.x ¥i¥H¨ì 1 GB¡C¦pªG¬Oºô¸ôt²ü¬Û·í«ªº¦øªA¾¹
(¨Ò¦p¤j«¬ FTP ©Î HTTP ¦øªA¾¹)¡A§A¤]³\·|µo²{ 256 MB ¥i¯à¤£¤j°÷¡C
©Ò¥H¡An¦p¦ó¼W¥[©w§}ªÅ¶¡©O¡Hn±q¨â¤è±µÛ¤â¡Cº¥ýº¥ý§i¶D
kernel ¥»¨n«O¯d¸û¤jªÅ¶¡µ¹¦Û¤v¡C¨ä¦¸¡A¬JµM¬O¦b©w§}ªÅ¶¡ªº³Ì¤W
±¸ü¤J kernel¡A©Ò¥HÁÙn½Õ§C¸ü¤Jªº¦ì§}¡A¤~¤£·|©M«e±©w§}ªº½d³ò
«Å|¡C
¼W¥[ src/sys/i386/include/pmap.h ¸Ìªº
NKPDE ´N¥i¥H¹F¦¨²Ä¤@ӥؼСC1 GB ªº©w§}ªÅ¶¡·|
¹³³o¼Ë¡G
#ifndef NKPDE
#ifdef SMP
#define NKPDE 254 /* addressable number of page tables/pde's */
#else
#define NKPDE 255 /* addressable number of page tables/pde's */
#endif /* SMP */
#endif
nºâ¥X NKPDE ªº¥¿½TÈ¡A±N·QnªºªÅ¶¡¤j¤p
(¥H megabyte ¬°³æ¦ì)°£¥H 4¡A±µµÛ³æ CPU ¾÷¾¹´î 1¡A
Âù CPU «h¬O´î 2¡C
n¸Ñ¨M²Ä¤GÓ°ÝÃD¡A¥²¶·¦Û¦æºâ¥X kernel ³Q¸ü¤Jªº¦ì§}¡G¨D¥X
0x100100000 ´î±¼©w§}ªÅ¶¡¤j¤pªºÈ(¥H byte ¬°³æ¦ì)¡A¦p 1 GB ¤j¤p´N¬O
0xc0100000¡C§âsrc/sys/i386/conf/Makefile.i386
¸Ìªº LOAD_ADDRESS ³]¦¨³oÓÈ¡Q±µµÛ¦b
src/sys/i386/conf/kernel.script ¤¤¡A±N
section ¦Cªí³Ì«e±ªº location counter ³]¦¨¬Û¦PªºÈ¡A¦p¤U¡G
OUTPUT_FORMAT("elf32-i386", "elf32-i386", "elf32-i386")
OUTPUT_ARCH(i386)
ENTRY(btext)
SEARCH_DIR(/usr/lib); SEARCH_DIR(/usr/obj/elf/home/src/tmp/usr/i386-unknown-freebsdelf/lib);
SECTIONS
{
/* Read-only sections, merged into text segment: */
. = 0xc0100000 + SIZEOF_HEADERS;
.interp : { *(.interp) }
µM«á«·s½sĶ±zªº kernel¡C±z¥i¯à·|¦b°õ¦æ &man.ps.1;¡B&man.top.1;
³oÃþªºµ{¦¡®É¸I¨ì°ÝÃD¡Qmake world À³¸Ó´N¥i¥H¸Ñ¨M
(©Î§â§ï¹Lªº pmap.h ½Æ»s¨ì
/usr/include/vm/ ¤U¡A¦A¤â°Ê½sĶ
libkvm ¡A&man.ps.1; ÁÙ¦³ &man.top.1;)¡C
ª`·N¡Gkernel ©Ò¯à©w§}ªºªÅ¶¡¤j¤p¥²¶·¬O 4 megabytes ªº¿¼Æ¡C
[&a.dg; ¸É¥R¡G§Ú»{¬° kernel ©w§}ªÅ¶¡¤j¤pÀ³¸Ón¬O 2
ªº¼¾¡A¦ý¤£¤j½T©w³o¤@ÂI¡Cªº±Ò°Êµ{¦¡·|°Ê¨ì
high order address bits¡A°O±o¥¦°²³]¦Ü¤Ö¦³ 256 MB¡C]
Vanilla
Shu
vanilla@FreeBSD.org
·PÁÂ
FreeBSD Core Team
°²¦p±z¦b³o¥÷ FAQ ¤¤§ä¨ì¿ù»~ªº¦a¤è¡A©Î¬O±z·Q¼W¥[¨Ç¬Æ»ò¡A
½Ð¼g«Ê«H¨ì &a.faq; ¡C§ÚÌ«D±`·PÁ±zªº«Øij¡A
¦]¬°±zªº«ØijÅý³o¥÷¤å¥óÅܱo§ó¦n¡I
&a.jkh;
¤£°±ªº§ó·s¹L®Éªº FAQ
&a.dwhite;
¸g±`¦b freebsd-questions ¤W¦^µª°ÝÃD
&a.joerg;
¸g±`¦b Usenet ¤W¦^µª°ÝÃD
&a.wollman;
Networking and formatting
Jim Lowe
Multicast information
&a.pds;
FreeBSD FAQ ³o¥÷¤å¥óªº¥´¦rW¤u
The FreeBSD Team
Kvetching, moaning, submitting data
¹ï©ó¨º¨Ç´¿¸g¹ï³o¥÷ FAQ ´£¨ÑÀ°§U¡A¦Ó§Ų́S´£¨ìªº¤HÌ¡A
§Ú̥ѰJªº·PÁ±z¡I
&bibliography;
diff --git a/zh_TW.Big5/share/sgml/bookinfo.ent b/zh_TW.Big5/share/sgml/bookinfo.ent
index 5587c3bebd..91df573fe3 100644
--- a/zh_TW.Big5/share/sgml/bookinfo.ent
+++ b/zh_TW.Big5/share/sgml/bookinfo.ent
@@ -1,12 +1,16 @@
+
+
+
+
diff --git a/zh_TW.Big5/share/sgml/glossary/freebsd-glossary.sgml b/zh_TW.Big5/share/sgml/glossary/freebsd-glossary.sgml
new file mode 100644
index 0000000000..7c77be771a
--- /dev/null
+++ b/zh_TW.Big5/share/sgml/glossary/freebsd-glossary.sgml
@@ -0,0 +1,1784 @@
+
+
+
+ &os; Glossary
+ This glossary contains terms and acronyms used within the &os;
+ community and documentation.
+
+
+ A
+
+
+ ACL
+
+
+
+
+ ACPI
+
+
+
+
+ AMD
+
+
+
+
+ AML
+
+
+
+
+ APIC
+
+
+
+
+ APM
+
+
+
+
+ APOP
+
+
+
+
+ ASL
+
+
+
+
+ ATA
+
+
+
+
+ ATM
+
+
+
+
+ ACPI Machine Language
+ AML
+
+ Pseudocode, interpreted by a virtual machine within an
+ ACPI -compliant operating system, providing a
+ layer between the underlying hardware and the documented
+ interface presented to the OS .
+
+
+
+
+ ACPI Source Language
+ ASL
+
+ The programming language AML is written in.
+
+
+
+
+ Access Control List
+ ACL
+
+
+
+
+
+
+ Advanced Configuration and Power Interface
+ ACPI
+
+ 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. ACPI
+ evolves and supercedes the functionality provided previously by
+ APM , PNPBIOS and other technologies, and
+ provides facilities for controlling power consumption, machine
+ suspension, device enabling and disabling, etc.
+
+
+
+
+ Advanced Power Management
+ APM
+
+
+
+
+
+
+ Advanced Programmable Interrupt Controller
+ APIC
+
+
+
+
+
+
+ Advanced Technology Attachment
+ ATA
+
+
+
+
+
+
+ Asynchronous Transfer Mode
+ ATM
+
+
+
+
+
+
+ Authenticated Post Office Protocol
+ APOP
+
+
+
+
+
+
+ Automatic Mount Daemon
+ AMD
+
+ A daemon that automatically mounts a filesystem when a file
+ or directory within that filesystem is accessed.
+
+
+
+
+
+ B
+
+
+ BIND
+
+
+
+
+ BIOS
+
+
+
+
+ BSD
+
+
+
+
+ Basic Input/Output System
+ BIOS
+
+
+
+
+
+
+ Berkeley Internet Name Domain
+ BIND
+
+
+
+
+
+
+ Berkeley Software Distribution
+ BSD
+
+ This is the name that the Computer Systems Research Group
+ (CSRG) at The University
+ of California at Berkeley
+ gave to their improvements and modifications to
+ AT&T's 32V &unix;.
+ &os; is a descendant of the CSRG work.
+
+
+
+
+ Bikeshed Building
+
+ A phenomenon whereby many people will give an opinion on
+ an uncomplicated topic, whilst a complex topic receives little
+ or no discussion. See the
+ FAQ for
+ the origin of the term.
+
+
+
+
+
+ C
+
+
+ CD
+
+
+
+
+ CHAP
+
+
+
+
+ CLIP
+
+
+
+
+ COFF
+
+
+
+
+ CPU
+
+
+
+
+ CTS
+
+
+
+
+ CVS
+
+
+
+
+ Carrier Detect
+ CD
+
+ An RS232C signal indicating that a carrier has been
+ detected.
+
+
+
+
+ Central Processing Unit
+ CPU
+
+
+
+
+
+
+ Challenge Handshake Authentication Protocol
+ CHAP
+
+
+
+
+
+
+ Classical IP over ATM
+ CLIP
+
+
+
+
+
+
+ Clear To Send
+ CTS
+
+ An RS232C signal giving the remote system
+ permission to send data.
+
+
+
+
+ Common Object File Format
+ COFF
+
+
+
+
+
+
+ Concurrent Versions System
+ CVS
+
+
+
+
+
+
+
+ D
+
+
+ DAC
+
+
+
+
+ DDB
+
+
+
+
+ DES
+
+
+
+
+ DHCP
+
+
+
+
+ DNS
+
+
+
+
+ DSDT
+
+
+
+
+ DSR
+
+
+
+
+ DTR
+
+
+
+
+ DVMRP
+
+
+
+
+ Discretionary Access Control
+ DAC
+
+
+
+
+
+
+ Data Encryption Standard
+ DES
+
+
+
+
+
+
+ Data Set Ready
+ DSR
+
+
+
+
+
+
+ Data Terminal Ready
+ DTR
+
+
+
+
+
+
+ Debugger
+ DDB
+
+
+
+
+
+
+ Differentiated System Description Table
+ DSDT
+
+
+
+
+
+
+ Distance-Vector Multicast Routing Protocol
+ DVMRP
+
+
+
+
+
+
+ Domain Name System
+ DNS
+
+
+
+
+
+
+ Dynamic Host Configuration Protocol
+ DHCP
+
+
+
+
+
+
+
+ E
+
+
+ ECOFF
+
+
+
+
+ ELF
+
+
+
+
+ ESP
+
+
+
+
+ Encapsulated Security Payload
+ ESP
+
+
+
+
+
+
+ Executable and Linking Format
+ ELF
+
+
+
+
+
+
+ Extended COFF
+ ECOFF
+
+
+
+
+
+
+
+ F
+
+
+ FADT
+
+
+
+
+ FAT
+
+
+
+
+ FAT16
+
+
+
+
+ FTP
+
+
+
+
+ File Allocation Table
+ FAT
+
+
+
+
+
+
+ File Allocation Table (16-bit)
+ FAT16
+
+
+
+
+
+
+ File Transfer Protocol
+ FTP
+
+
+
+
+
+
+ Fixed ACPI Description Table
+ FADT
+
+
+
+
+
+
+ G
+
+
+ GUI
+
+
+
+
+ Giant
+
+ The name of a mutual exclusion mechanism
+ (a sleep mutex ) 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.
+
+
+
+
+ Graphical User Interface
+ GUI
+
+ A system where the user and computer interact with
+ graphics.
+
+
+
+
+
+ H
+
+
+ HTML
+
+
+
+
+ HUP
+
+
+
+
+ HangUp
+ HUP
+
+
+
+
+
+
+ HyperText Markup Language
+ HTML
+
+ The markup language used to create web pages.
+
+
+
+
+
+ I
+
+
+ I/O
+
+
+
+
+ IASL
+
+
+
+
+ IMAP
+
+
+
+
+ IP
+
+
+
+
+ IPFW
+
+
+
+
+ IPP
+
+
+
+
+ IPv4
+
+
+
+
+ IPv6
+
+
+
+
+ ISP
+
+
+
+
+ IP Firewall
+ IPFW
+
+
+
+
+
+
+ IP Version 4
+ IPv4
+
+
+
+
+
+
+ IP Version 6
+ IPv6
+
+
+
+
+
+
+ Input/Output
+ I/O
+
+
+
+
+
+
+ Intel’s ASL compiler
+ IASL
+
+ Intel’s compiler for converting ASL into
+ AML .
+
+
+
+
+ Internet Message Access Protocol
+ IMAP
+
+
+
+
+
+
+ Internet Printing Protocol
+ IPP
+
+
+
+
+
+
+ Internet Protocol
+ IP
+
+
+
+
+
+
+ Internet Service Provider
+ ISP
+
+
+
+
+
+
+ K
+
+
+ KAME
+
+ Japanese for turtle
, the term KAME is used
+ in computing circles to refer to the KAME Project , who work on
+ an implementation of IPv6 .
+
+
+
+
+ KDC
+
+
+
+
+ KLD
+
+
+
+
+ KSE
+
+
+
+
+ KVA
+
+
+
+
+ Kbps
+
+
+
+
+ Kernel &man.ld.1;
+ KLD
+
+
+
+
+
+
+ Kernel Scheduler Entities
+ KSE
+
+ A kernel-supported threading system. See the project home page
+ for further details.
+
+
+
+
+ Kernel Virtual Address
+ KVA
+
+
+
+
+
+
+ Key Distribution Center
+ KDC
+
+
+
+
+
+
+ Kilo Bits Per Second
+ Kbps
+
+
+
+
+
+
+
+ L
+
+
+ LAN
+
+
+
+
+ LOR
+
+
+
+
+ LPD
+
+
+
+
+ Line Printer Daemon
+ LPD
+
+
+
+
+
+
+ Local Area Network
+ LAN
+
+
+
+
+
+
+ Lock Order Reversal
+ LOR
+
+ 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 if you were unlucky, a deadlock would
+ have happened here
.
+
+ True positive LORs tend to get fixed quickly, so
+ check &a.current.url; and the
+
+ LORs Seen page before posting to the mailing lists.
+
+
+
+
+
+ M
+
+
+ MAC
+
+
+
+
+ MADT
+
+
+
+
+ MFC
+
+
+
+
+ MFS
+
+
+
+
+ MIT
+
+
+
+
+ MLS
+
+
+
+
+ MOTD
+
+
+
+
+ MTA
+
+
+
+
+ MUA
+
+
+
+
+ Mail Transfer Agent
+ MTA
+
+
+
+
+
+
+ Mail User Agent
+ MUA
+
+
+
+
+
+
+ Mandatory Access Control
+ MAC
+
+
+
+
+
+
+ Massachusetts Institute of Technology
+ MIT
+
+
+
+
+
+
+ Merge From Current
+ MFC
+
+ To merge functionality or a patch from the -CURRENT
+ branch to another, most often -STABLE.
+
+
+
+
+ Merge From Stable
+ MFS
+
+ 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.
+
+ This term is also used when a patch is merged from -STABLE
+ to a security branch.
+
+
+
+
+
+ Message Of The Day
+ MOTD
+
+ A message, usually shown on login, often used to
+ distribute information to users of the system.
+
+
+
+
+ Multi-Level Security
+ MLS
+
+
+
+
+
+
+ Multiple APIC Description Table
+ MADT
+
+
+
+
+
+
+
+ N
+
+
+ NAT
+
+
+
+
+ NDISulator
+
+
+
+
+ NFS
+
+
+
+
+ NTFS
+
+
+
+
+ NTP
+
+
+
+
+ Network Address Translation
+ NAT
+
+
+
+
+
+
+ Network File System
+ NFS
+
+
+
+
+
+
+ New Technology File System
+ NTFS
+
+ A filesystem developed by Microsoft and available in its
+ New Technology
operating systems, such as
+ &windows2k;, &windowsnt; and &windowsxp;.
+
+
+
+
+ Network Time Protocol
+ NTP
+
+
+
+
+
+
+
+ O
+
+
+ OBE
+
+
+
+
+ ODMR
+
+
+
+
+ OS
+
+
+
+
+ On-Demand Mail Relay
+ ODMR
+
+
+
+
+
+
+ Operating System
+ OS
+
+
+
+
+
+
+ Overtaken By Events
+ OBE
+
+ 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.
+
+
+
+
+
+ P
+
+
+ PAE
+
+
+
+
+ PAM
+
+
+
+
+ PAP
+
+
+
+
+ PC
+
+
+
+
+ PCNSFD
+
+
+
+
+ PDF
+
+
+
+
+ PID
+
+
+
+
+ POLA
+
+
+
+
+ POP
+
+
+
+
+ POP3
+
+
+
+
+ PPD
+
+
+
+
+ PPP
+
+
+
+
+ PPPoA
+
+
+
+
+ PPPoE
+
+
+
+
+ PPP over ATM
+ PPPoA
+
+
+
+
+
+
+ PPP over Ethernet
+ PPPoE
+
+
+
+
+
+
+ PR
+
+
+
+
+ PXE
+
+
+
+
+ Password Authentication Protocol
+ PAP
+
+
+
+
+
+
+ Personal Computer
+ PC
+
+
+
+
+
+
+ Personal Computer Network File System Daemon
+ PCNFSD
+
+
+
+
+
+
+ Physical Address Extensions
+ PAE
+
+ A method of enabling access to up to 64 GB of RAM on
+ systems which only physically have a 32-bit wide address space
+ (and would therefore be limited to 4 GB without PAE).
+
+
+
+
+ Pluggable Authentication Modules
+ PAM
+
+
+
+
+
+
+ Point-to-Point Protocol
+ PPP
+
+
+
+
+
+
+ Pointy Hat
+
+ A mythical piece of headgear, much like a
+ dunce cap , 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.
+
+
+
+
+ Portable Document Format
+ PDF
+
+
+
+
+
+
+ Post Office Protocol
+ POP
+
+
+
+
+
+
+ Post Office Protocol Version 3
+ POP3
+
+
+
+
+
+
+ PostScript Printer Description
+ PPD
+
+
+
+
+
+
+ Preboot eXecution Environment
+ PXE
+
+
+
+
+
+
+ Principle Of Least Astonishment
+ POLA
+
+ As &os; evolves, changes visible to the user should be
+ kept as unsurprising as possible. For example, arbitrarily
+ rearranging system startup variables in
+ /etc/defaults/rc.conf violates
+ POLA . Developers consider
+ POLA when contemplating user-visible
+ system changes.
+
+
+
+
+ Problem Report
+ PR
+
+
+
+
+
+
+ Process ID
+ PID
+
+ A number, unique to a particular process on a system,
+ which identifies it and allows actions to be taken against it.
+
+
+
+
+ Project Evil
+
+ The working title for the NDISulator ,
+ 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
+ NDISulator 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 src/sys/compat/ndis/subr_ndis.c .
+
+
+
+
+
+ R
+
+
+ RA
+
+
+
+
+ RAID
+
+
+
+
+ RAM
+
+
+
+
+ RD
+
+
+
+
+ RFC
+
+
+
+
+ RISC
+
+
+
+
+ RPC
+
+
+
+
+ RS232C
+
+
+
+
+ RTS
+
+
+
+
+ Random Access Memory
+ RAM
+
+
+
+
+
+
+ Received Data
+ RD
+
+
+
+
+
+
+ Recommended Standard 232C
+ RS232C
+
+ A standard for communications between serial devices.
+
+
+
+
+ Reduced Instruction Set Computer
+ RISC
+
+
+
+
+
+
+ Redundant Array of Inexpensive Disks
+ RAID
+
+
+
+
+
+
+ Remote Procedure Call
+ RPC
+
+
+
+
+
+
+ Request For Comments
+ RFC
+
+
+
+
+
+
+ Request To Send
+ RTS
+
+
+
+
+
+
+ Router Advertisement
+ RA
+
+
+
+
+
+
+
+ S
+
+
+ SCI
+
+
+
+
+ SCSI
+
+
+
+
+ SG
+
+
+
+
+ SMB
+
+
+
+
+ SMP
+
+
+
+
+ SMTP
+
+
+
+
+ SMTP AUTH
+
+
+
+
+ SSH
+
+
+
+
+ STR
+
+
+
+
+ SMTP Authentication
+ SMTP AUTH
+
+
+
+
+
+
+ Server Message Block
+ SMB
+
+
+
+
+
+
+ Signal Ground
+ SG
+
+ An RS232 pin or wire that is the ground reference
+ for the signal.
+
+
+
+
+ Simple Mail Transfer Protocol
+ SMTP
+
+
+
+
+
+
+ Secure Shell
+ SSH
+
+
+
+
+
+
+ Small Computer System Interface
+ SCSI
+
+
+
+
+
+
+ Suspend To RAM
+ STR
+
+
+
+
+
+
+ Symmetric MultiProcessor
+ SMP
+
+
+
+
+
+
+ System Control Interrupt
+ SCI
+
+
+
+
+
+
+
+ T
+
+
+ TCP
+
+
+
+
+ TD
+
+
+
+
+ TFTP
+
+
+
+
+ TGT
+
+
+
+
+ TSC
+
+
+
+
+ Ticket-Granting Ticket
+ TGT
+
+
+
+
+
+
+ Time Stamp Counter
+ TSC
+
+
+ A profiling counter internal to modern &pentium; processors
+ that counts core frequency clock ticks.
+
+
+
+
+ Transmission Control Protocol
+ TCP
+
+
+
+
+
+
+ Transmitted Data
+ TD
+
+
+
+
+
+
+ Trivial FTP
+ TFTP
+
+
+
+
+
+
+
+ U
+
+
+ UDP
+
+
+
+
+ UFS1
+
+
+
+
+ UFS2
+
+
+
+
+ UID
+
+
+
+
+ URL
+
+
+
+
+ USB
+
+
+
+
+ Uniform Resource Locator
+ URL
+
+
+
+
+
+
+ Unix File System Version 1
+ UFS1
+
+
+
+
+
+
+ Unix File System Version 2
+ UFS2
+
+
+
+
+
+
+ Universal Serial Bus
+ USB
+
+
+
+
+
+
+ User ID
+ UID
+
+ A unique number assigned to each user of a computer,
+ by which the resources and permissions assigned to that
+ user can be identified.
+
+
+
+
+ User Datagram Protocol
+ UDP
+
+
+
+
+
+
+
+ V
+
+
+ VPN
+
+
+
+
+ Virtual Private Network
+ VPN
+
+
+
+
+
+