docs/99891: [UPDATE] zh_TW: Update to (20060707) svn#702
chinsan
chinsan.tw at gmail.com
Fri Jul 7 19:20:27 UTC 2006
>Number: 99891
>Category: docs
>Synopsis: [UPDATE] zh_TW: Update to (20060707) svn#702
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: update
>Submitter-Id: current-users
>Arrival-Date: Fri Jul 07 19:20:20 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator: chinsan
>Release: FreeBSD 6.1-STABLE i386
>Organization:
FreeBSD Taiwan
>Environment:
System: FreeBSD chinsan2.twbbs.org 6.1-STABLE FreeBSD 6.1-STABLE #1: Fri Jun 2 16:44:35 CST 2006 root at chinsan2.twbbs.org:/usr/obj/usr/src/sys/GENERIC i386
>Description:
- Update to (20060707) svn#702
(http://chinsan2.twbbs.org/chinsan/zh_TW.Big5.20060707.svn702.diff )
Thanks.
>How-To-Repeat:
>Fix:
--- zh_TW.Big5.20060707.svn702.diff begins here ---
diff -ruN zh_TW.Big5.org/books/handbook/config/chapter.sgml zh_TW.Big5/books/handbook/config/chapter.sgml
--- zh_TW.Big5.org/books/handbook/config/chapter.sgml Tue Jan 31 09:31:02 2006
+++ zh_TW.Big5/books/handbook/config/chapter.sgml Sat Jul 8 03:11:00 2006
@@ -38,50 +38,46 @@
<indexterm><primary>system configuration</primary></indexterm>
<indexterm><primary>system optimization</primary></indexterm>
- <para>One of the important aspects of &os; is system configuration.
- Correct system configuration will help prevent headaches during future upgrades.
- This chapter will explain much of the &os; configuration process,
- including some of the parameters which
- can be set to tune a &os; system.
+ <para>¦b &os; ¨Ï¥Î¹Lµ{¤¤¡A¬Û·í«nªºÀô¸`¤§¤@´N¬O¨t²Î³]©w³¡¤À¡C
+ ¥¿½Tªº¨t²Î³]©w¡A¥i¥HÅý§A´î»´¤é«á¤É¯ÅªºÀYµhÀ£¤O¡C
+ ¥»³¹µÛ«©ó¤¶²Ð &os; ªº¬ÛÃö«n³]©w¤W¡A¥]¬A¤@¨Ç¥i¥H½Õ¾ã &os; ®Ä¯àªº°Ñ¼Æ³]©w¡C
</para>
<para>Ū§¹³o³¹¡A±z±N¤F¸Ñ¡G</para>
<itemizedlist>
<listitem>
- <para>How to efficiently work with
- file systems and swap partitions.</para>
+ <para>¦p¦ó¦³®Ä¹B¥ÎÀɮרt²Î¥H¤Î swap ¤À³Î°Ï¡C</para>
</listitem>
<listitem>
- <para><filename>rc.conf</filename> ªº³]©w»P <filename>/usr/local/etc/rc.d</filename> ªº±Ò°Ê¬[ºc¡F</para>
+ <para><filename>rc.conf</filename> ªº³]©w»P <filename>/usr/local/etc/rc.d</filename> ªº±Ò°Ê¬[ºc¡C</para>
</listitem>
<listitem>
- <para>¦p¦ó³]©w¡B´ú¸Õºô¸ô¥d¡F</para>
+ <para>¦p¦ó³]©w¡B´ú¸Õºô¸ô¥d¡C</para>
</listitem>
<listitem>
- <para>How to configure virtual hosts on your network devices.</para>
+ <para>¦p¦ó³]©w virtual hosts¡C</para>
</listitem>
<listitem>
<para>¦p¦ó³]©w <filename>/etc</filename> ¤ºªº¦UºØ³]©wÀÉ¡C</para>
</listitem>
<listitem>
- <para>¦p¦ó¥H <command>sysctl</command> ¨Ó½Õ¾ã &os; ªº¨t²Î®Ä¯à¡F</para>
+ <para>¦p¦ó¥H <command>sysctl</command> ¨Ó½Õ¾ã &os; ªº¨t²Î®Ä¯à¡C</para>
</listitem>
<listitem>
<para>¦p¦ó½Õ¾ãµwºÐ®Ä¯à¡A¥H¤Î§ó§ï kernel ¨î¡C</para>
</listitem>
</itemizedlist>
- <para>¦b¾\Ū³o³¹¤§«e¡A±zÀ³·í¤F¸Ñ¡G</para>
+ <para>¦b¶}©l¾\Ū³o³¹¤§«e¡A±z»Ýn¡J</para>
<itemizedlist>
<listitem>
- <para>Understand &unix; and &os; basics (<xref
- linkend="basics">).</para>
+ <para>ÁA¸Ñ &unix; ¤Î &os; ¬ÛÃö°ò¥»·§©À(<xref
+ linkend="basics">)¡C</para>
</listitem>
<listitem>
- <para>Be familiar with the basics of kernel configuration/compilation
- (<xref linkend="kernelconfig">).</para>
+ <para>n¦³³]©w¡B½sĶ kernel ªº°ò¦·§©À(<xref linkend="kernelconfig">)¡C</para>
</listitem>
</itemizedlist>
</sect1>
@@ -106,57 +102,45 @@
<sect3>
<title>Base Partitions</title>
- <para>When laying out file systems with &man.disklabel.8;
- or &man.sysinstall.8;, remember that hard
- drives transfer data faster from the outer
- tracks to the inner.
- Thus smaller and heavier-accessed file systems
- should be closer to the outside of the drive, while
- larger partitions like <filename>/usr</filename> should be placed
- toward the inner. It is a good idea to create
- partitions in a similar order to: root, swap,
- <filename>/var</filename>, <filename>/usr</filename>.</para>
-
- <para>The size of <filename>/var</filename>
- reflects the intended machine usage.
- <filename>/var</filename> is used to hold
- mailboxes, log files, and printer spools. Mailboxes and log
- files can grow to unexpected sizes depending
- on how many users exist and how long log
- files are kept. Most users would never require a gigabyte,
- but remember that <filename>/var/tmp</filename>
- must be large enough to contain packages.
+ <para>¥Î &man.disklabel.8; ©Î &man.sysinstall.8; ¨Ó³W¹ºÀɮרt²Î®É¡A½Ð°O¦í¡G
+ µwºÐ¦b¶Ç¿é¸ê®Æ¤è±¡A(¥Ñ©óµ²ºc¬°ºÐ¤ù¦]¯À)¥~°é·|¤ñ¤º°é¨Ó±o§Ö¨Ç¡C
+ ¦]¦¹¡A«Øij§â¸û¤p¡B±`·|¦s¨úªº¤À³Î°Ï¾¨¶q©ñ¥~°é¡A¦Ó¸û¤jªº¤À³Î°Ï¹³¬O
+ <filename>/usr</filename> «hÀ³©ñ¦b¸û¤º°é¡C
+ «Øij«Ø¥ß¤À³Î°Ïªº¶¶§Ç¡A¥H¹³¬O¡Groot, swap,
+ <filename>/var</filename>, <filename>/usr</filename> ³o¼Ë¶¶§Ç¨Ó«Ø¥ß·|¸û§´¡C</para>
+
+ <para><filename>/var</filename> ªº¤j¤pnµø¾÷¾¹ªº¥Î³~¦Ó©w¡C
+ <filename>/var</filename> ¬O¥Î¨Ó©ñ
+ «H½c¡Blog ¬ö¿ýÀÉ¥H¤Î¦Lªí¾÷¦î¦C(spools)¡C «H½c¥H¤Î°O¿ýÀɪº¦¨ªø´T«×¥i¯àµLªk¹w¦ô¡A
+ ¦]¬°³o¨Ç¦¨ªø´T«×¤D¬O¨ú¨M©ó¦h¤Ö¥Î¤á¡Bn©ñ¦h¤[µ¥ºÞ²zì«h¦Ó©w¡C
+ ³q±`³o¨Ç¨Ï¥ÎªÌ¨Ã¨S¦³¥Î¨ì 1 GB ¥H¤W¡A¦ý½Ð¤Á°O¡G¦Ü¤Ön«O¯d¤@©wªÅ¶¡µ¹ <filename>/var/tmp</filename>
+ ¥H«K¦s©ñ packages¡C
</para>
- <para>The <filename>/usr</filename> partition holds much
- of the files required to support the system, the &man.ports.7;
- collection (recommended) and the source code (optional). Both
- of which are optional at install time.
- At least 2 gigabytes would be recommended for this partition.</para>
-
- <para>When selecting partition sizes, keep the space
- requirements in mind. Running out of space in
- one partition while barely using another can be a
- hassle.</para>
-
- <note><para>Some users have found that &man.sysinstall.8;'s
- <literal>Auto-defaults</literal> partition sizer will
- sometimes select smaller than adequate <filename>/var</filename>
- and <filename>/</filename> partitions. Partition wisely and
- generously.</para></note>
+ <para>¦Ó <filename>/usr</filename> ¤À³Î°Ï¥Dn¬O¥Î¨Ó©ñ¨t²Î¹B§@®É©Ò»ÝªºÀɮסB¤u¨ãµ{¦¡µ¥¡A¨Ò¦p¡G
+ &man.ports.7; collection(«Øij¦w¸Ë)¸ò source tree(optional)¡C
+ ¦b¦w¸Ë FreeBSD ®É¡A³o¨âªÌ³£¬O¥i¿ï¾Ü¸Ë»P¤£¸Ëªº¡C
+ ¤£¹L¡A³oÓ¤À³Î°Ï«Øij¦Ü¤Ön¦³ 2 GB ªÅ¶¡¥H¤W¤~°÷¥Î¡C</para>
+
+ <para>³W¹º¤À³Î°Ï¤j¤p®É¡A°O±o¦h«O¯d¨Ç¦¨ªøªÅ¶¡¡C
+ §_«hY¬YÓ¤À³Î°Ïº¡¤F¡A¦ý¥t¤@Ó¤À³Î°Ï«oÁٳѫܦhªÅ¶¡¡A´N·|¬Û·í§xµ~¡C</para>
+
+ <note><para>¦³¨Ç¤H¥i¯à·|µo²{ &man.sysinstall.8; ªº
+ <literal>Auto-defaults(¦Û°Ê¹w³]È)</literal> ©Ò°µªº¤À³Î°Ï¤j¤p¡A
+ ¦³®ÉÔ·|§â <filename>/var</filename> ¥H¤Î <filename>/</filename> ¤À³Î°Ï³]¤Ó¤p¤F¡C
+ §ÚÌ«Øij¬O¡G½Ð¨Ì¨Ï¥Î±¡ªp¥H¤Î»Ý¨D¡A¨Ó¤â°Ê½Õ¾ã¬ÛÃö¤À³Î°Ï¤j¤p¡C</para></note>
</sect3>
<sect3 id="swap-design">
- <title>Swap Partition</title>
+ <title>Swap ¤À³Î°Ï</title>
<indexterm><primary>swap sizing</primary></indexterm>
<indexterm><primary>swap partition</primary></indexterm>
- <para>As a rule of thumb, the swap partition should be
- about double the size of system memory (RAM). For example,
- if the machine has 128 megabytes of memory,
- the swap file should be 256 megabytes. Systems with
+ <para>®Ú¾Ú¸gÅçªk«h¡A³q±` swap ¤À³Î°ÏÀ³¸Ó³]¬°¨t²Î°O¾ÐÅé(RAM)¤j¤pªº¨â¿§Y¥i¡C
+ Á|¨Ò¨Ó»¡¡GY¾÷¾¹¦³ 128 MB RAM ªº¸Ü¡A¨º»ò
+ swap «hÀ³¸Ó³]¬° 256 MB¡C Systems with
less memory may perform better with more swap.
Less than 256 megabytes of swap is not recommended and
memory expansion should be considered.
diff -ruN zh_TW.Big5.org/books/handbook/eresources/chapter.sgml zh_TW.Big5/books/handbook/eresources/chapter.sgml
--- zh_TW.Big5.org/books/handbook/eresources/chapter.sgml Tue Jan 31 09:31:02 2006
+++ zh_TW.Big5/books/handbook/eresources/chapter.sgml Sat Jul 8 03:10:37 2006
@@ -2,27 +2,23 @@
The FreeBSD Documentation Project
$FreeBSD: doc/zh_TW.Big5/books/handbook/eresources/chapter.sgml,v 1.2 2006/01/31 01:31:02 vanilla Exp $
+ Take translation from Kang-min Liu <gugod at gugod.org>
Original revision: 1.175
-->
<appendix id="eresources">
- <title>Resources on the Internet</title>
+ <title>ºô»Úºô¸ô¤Wªº¸ê·½</title>
- <para>The rapid pace of FreeBSD progress makes print media impractical as a
- means of following the latest developments. Electronic resources are the
- best, if not often the only, way stay informed of the latest advances.
- Since FreeBSD is a volunteer effort, the user community itself also
- generally serves as a <quote>technical support department</quote> of sorts,
- with electronic mail and USENET news being the most effective way of
- reaching that community.</para>
+ <para>¶i®i¸§Öªº FreeBSD ¨Ï±o²{¦³ªº¦L¨ê¡B¥±´CÅé¸ò¤£¤W¥¦ªº³Ì·s¶i«×¡I
+ ¤Ï¦Ó¼Æ¦ìª©¥»ªº¸ê·½¡A¤]³\¦³®É¨Ã¤£¬O³Ì¦n¡A¦ý³q±`¬O°ß¤@¤@Ó¸ò¤W³Ì·s¶i®iªº¤è¦¡¡C
+ ¥¿¥Ñ©ó FreeBSD ¬O¨Ó¦Û©ó³\¦h§Ó¤uªº§V¤O¡A©Ò¥H¼s¤jªº¨Ï¥ÎªÌ¸s¤]³q±`§êºtµÛ <quote>IT§Þ³N¤ä´©³¡ªù</quote> ªº¨¤¦â¡C
+ ¥unµ½¥Î¹q¤l¶l¥ó©M USENET ·s»D¸s²Õ´N¥i¥H«Ü§Ö³t¦aÁpô³o¨ÇªÀ¸s¤F¡C</para>
- <para>The most important points of contact with the FreeBSD user community
- are outlined below. If you are aware of other resources not mentioned
- here, please send them to the &a.doc; so that they may also be
- included.</para>
+ <para>¥H¤U²¤¶»P FreeBSD ªÀ¸s·f¤W½uªº¥Dn¤è¦¡¡C
+ Y§AÁÙª¾¹D¨ä¥L³o¸Ì¨S¦³¦C¥Xªº¸ê·½¡A½Ð§iª¾ &a.doc;¡A¥H«K§Ú̧ó·s¡C</para>
<sect1 id="eresources-mail">
- <title>Mailing Lists</title>
+ <title>¶l»¼½×¾Â(Mailing Lists)</title>
<para>Though many of the FreeBSD development members read USENET, we
cannot always guarantee that we will get to your questions in a timely
diff -ruN zh_TW.Big5.org/books/handbook/install/chapter.sgml zh_TW.Big5/books/handbook/install/chapter.sgml
--- zh_TW.Big5.org/books/handbook/install/chapter.sgml Sat Jun 17 18:22:45 2006
+++ zh_TW.Big5/books/handbook/install/chapter.sgml Sat Jul 8 03:11:04 2006
@@ -483,11 +483,9 @@
&os; &rel.current;-RELEASE ¡A¨º»ò¥i¥H¨ì <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/floppies/"></ulink> ¤U¸ü¡C</para>
<para>¬M¹³ÀÉ(images)ªºªþÀɦW³£¬O <filename>.flp</filename> ¡C¦Ó
- <filename>floppies/</filename> ¥Ø¿ý¤º¥]§t¤@¨Ç¤£¦P¥Î³~ªº¬M¹³ÀÉ(images)¡A³o¨ú¨M©ó±zn¸Ëªº FreeBSD ª©¥»¡B»Ý¨D¡BµwÅé°t³Æ¬°¦ó¡C
- Yn¸Ëªº¬O
- FreeBSD 4.X ¨º»ò³q±`¥u»Ýn 2 Ó¬M¹³ÀÉ¡A¤]´N¬O <filename>kern.flp</filename> »P
- <filename>mfsroot.flp</filename>¡C¦ÓYn¸Ëªº¬O FreeBSD 5.X
- ¡A¨º»ò³q±`n 3 Ó¬M¹³ÀÉ¡A¤]´N¬O¡G <filename>boot.flp</filename>¡B
+ <filename>floppies/</filename> ¥Ø¿ý¤º¥]§t¤@¨Ç¤£¦P¥Î³~ªº¬M¹³ÀÉ(images)¡A
+ ³o¨ú¨M©ó±zn¸Ëªº FreeBSD ª©¥»¡B»Ý¨D¡BµwÅé°t³Æ¬°¦ó¡C
+ ³q±`n 3 Ó¬M¹³ÀÉ¡A¤]´N¬O¡G <filename>boot.flp</filename>¡B
<filename>kern1.flp</filename>¡B
<filename>kern2.flp</filename>¡CY¦³ºÃ°Ýªº¸Ü¡A½Ð½¾\¦P¤@¥Ø¿ý¤Uªº
<filename>README.TXT</filename> ¤å¥óÀÉ¡A¥HÁA¸Ñ¬ÛÃö³Ì·sª`·N¨Æ¶µ¡C</para>
@@ -677,8 +675,7 @@
<screen>Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [kernel] in 9 seconds... _</screen>
- <para>±z¥i¥Hµ¥«Ý 10 ¬í¡A©Î¬O«ö <keycap>Enter</keycap> Áä¡C
- (Y¬O &os; 4.X ªº¸Ü¡A«h±N¥X²{ kernel configuration ¿ï³æµe±)</para>
+ <para>±z¥i¥Hµ¥«Ý 10 ¬í¡A©Î¬O«ö <keycap>Enter</keycap> Áä¡C</para>
</step>
</procedure>
@@ -732,277 +729,6 @@
</sect2>
- <sect2 id="start-userconfig">
- <title>Kernel ªº³]©w</title>
-
- <note><para>±q FreeBSD 5.0 ª©¶}©l¡A§ï¥Î·sªº &man.device.hints.5; ¤è¦¡¡A¦Ó²^¨Oªº userconfig ¤è¦¡¡C
- Ãö©ó &man.device.hints.5; ¾÷¨îªº²Ó¸`¤¶²Ð¡A½Ð°Ñ¾\ <xref linkend="device-hints">¡C</para></note>
-
- <para><firstterm>kernel</firstterm> ¤D¬O§@·~¨t²Î¤¤ªº®Ö¤ß¡At³d³\¦h¨Æ±¡¡A¹³¬O¡G±±¨î¨t²Î¤W©Ò¦³³]³Æ¡A¤ñ¦pµwºÐ¡Bºô¸ô¥d¡Bµ®Ä¥dµ¥¡C
- ¨C¶µ FreeBSD ©Ò¤ä´©ªºµwÅé³£¦³¬Û¹ïÀ³ªºÅX°Êµ{¦¡¡C
- ¨CÓÅX°Êµ{¦¡¦WºÙ³£¦³ 2 ¨ì 3 Ó¦r¥À©Ò²Õ¦¨¡A¹³¬O <devicename>sa</devicename> ¥Nªí SCSI ÅX°Êµ{¦¡¡A¦Ó
- <devicename>sio</devicename> ¥Nªí Serial I/O ÅX°Êµ{¦¡(ºÞ COM ports ¥Îªº)¡C</para>
-
- <para>·í kernel ¶}©l±Ò°Ê®É¡A¨CÓÅX°Êµ{¦¡´N·|¥hÀˬd¨t²Î¤W¬O§_¦³¤ä´©ªºµwÅé¦s¦b¡A
- Y¦³ªº¸Ü¡AÅX°Êµ{¦¡´N·|§@¬ÛÃöµwÅé³]©w¡A¥H«KÅý kernel ¨Ï¥Î¸ÓµwÅé¡C</para>
-
- <para>¤WzªºÀˬd°Ê§@¡A§Ú̺٬° <firstterm>device probing(°»´úµwÅé)</firstterm>¡C
- ¦ý¬O¡A³o¼Ë¤lªº¤è¦¡¨Ã¤£¬O¥Ã»·³£¨º»ò¶¶§Q¡C
- ¦³¨ÇµwÅéÅX°Êµ{¦¡µLªk¦P®É¦@¦s¡A¦Ó¦³®ÉÔ°»´ú¬YµwÅé®É¡A¤S·|³y¦¨¥t¤@µwÅ餣åXºl¡C
- ³o°ÝÃD¡A¤D¬O¥Ñ©ó <acronym>PC</acronym> ¥»¨³]p¤W¤Ñ¥Íªº¨î©ÒP¡C</para>
-
- <para>Many older devices are called ISA devices—as opposed
- to PCI devices. The ISA specification requires each device to have
- some information hard coded into it, typically the Interrupt Request
- Line number (IRQ) and IO port address that the driver uses. This
- information is commonly set by using physical
- <firstterm>jumpers</firstterm> on the card, or by using a DOS based
- utility.</para>
-
- <para>This was often a source of problems, because it was not possible
- to have two devices that shared the same IRQ or port address.</para>
-
- <para>Newer devices follow the PCI specification, which does not require
- this, as the devices are supposed to cooperate with the BIOS, and are
- told which IRQ and IO port addresses to use.</para>
-
- <para>If you have any ISA devices in your computer then FreeBSD's
- driver for that device will need to be configured with the IRQ and
- port address that you have set the card to. This is why carrying out
- an inventory of your hardware (see <xref
- linkend="install-inventory">) can be useful.</para>
-
- <para>Unfortunately, the default IRQs and memory ports used by some
- drivers clash. This is because some ISA devices are shipped with IRQs
- or memory ports that clash. The defaults in FreeBSD's drivers are
- deliberately set to mirror the manufacturer's defaults, so that, out
- of the box, as many devices as possible will work.</para>
-
- <para>This is almost never an issue when running FreeBSD day-to-day.
- Your computer will not normally contain two pieces of hardware that
- clash, because one of them would not work (irrespective of the
- operating system you are using).</para>
-
- <para>It becomes an issue when you are installing FreeBSD for the first
- time because the kernel used to carry out the install has to contain
- as many drivers as possible, so that many different hardware
- configurations can be supported. This means that some of
- those drivers will have conflicting configurations. The devices are
- probed in a strict order, and if you own a device that is probed late
- in the process, but conflicted with an earlier probe, then your
- hardware might not function or be probed correctly when you install
- FreeBSD.</para>
-
- <para>Because of this, the first thing you have the opportunity to do
- when installing FreeBSD is look at the list of drivers that are
- configured into the kernel, and either disable some of them, if you
- do not own that device, or confirm (and alter) the driver's
- configuration if you do own the device but the defaults are
- wrong.</para>
-
- <para>This probably sounds much more complicated than it actually
- is.</para>
-
- <para><xref linkend="kernel-config"> shows the first kernel
- configuration menu. We recommend that you choose the
- <guimenuitem>Start kernel configuration in full-screen visual
- mode</guimenuitem> option, as it presents the easiest interface for
- the new user.</para>
-
- <figure id="kernel-config">
- <title>Kernel ³]©wµe±</title>
-
- <mediaobject>
- <imageobject>
- <imagedata fileref="install/userconfig" format="PNG">
- </imageobject>
-
- <textobject>
- <screen>&txt.install.userconfig;</screen>
- </textobject>
- </mediaobject>
- </figure>
-
- <para>The kernel configuration screen (<xref linkend="fig-userconfig">)
- is then divided into four sections:</para>
-
- <orderedlist>
- <listitem>
- <para>A collapsible list of all the drivers that are currently
- marked as <quote>active</quote>, subdivided into groups such as
- <literal>Storage</literal>, and <literal>Network</literal>. Each
- driver is shown as a description, its two or three letter driver
- name, and the IRQ and memory port used by that driver. In
- addition, if an active driver conflicts with another active driver
- then <literal>CONF</literal> is shown next to the driver name.
- This section also shows the total number of conflicting drivers
- that are currently active.</para>
- </listitem>
-
- <listitem>
- <para>Drivers that have been marked inactive. They remain in the
- kernel, but they will not probe for their device when the kernel
- starts. These are subdivided into groups in the same way as the
- active driver list.</para>
- </listitem>
-
- <listitem>
- <para>More detail about the currently selected driver, including its
- IRQ and memory port address.</para>
- </listitem>
-
- <listitem>
- <para>Information about the keystrokes that are valid at this point
- in time.</para>
- </listitem>
- </orderedlist>
-
- <figure id="fig-userconfig">
- <title>Kernel Device ªº³]©wµe±</title>
-
- <mediaobject>
- <imageobject>
- <imagedata fileref="install/userconfig2" format="PNG">
- </imageobject>
-
- <textobject>
- <screen>&txt.install.userconfig2;</screen>
- </textobject>
- </mediaobject>
- </figure>
-
- <para>Do not worry if any conflicts are listed,
- it is to be expected; all the drivers are enabled, and
- as has already been explained, some of them will conflict with one
- another.</para>
-
- <para>You now have to work through the list of drivers, resolving the
- conflicts.</para>
-
- <procedure>
- <title>¸Ñ°£¬Û½ÄªºÅX°Êµ{¦¡</title>
-
- <step>
- <para>Press <keycap>X</keycap>. This will completely expand the
- list of drivers, so you can see all of them. You will need to use
- the arrow keys to scroll back and forth through the active driver
- list.</para>
-
- <para><xref linkend="hardware-conflicts"> shows the result of
- pressing <keycap>X</keycap>.</para>
-
- <figure id="hardware-conflicts">
- <title>®i¶}ÅX°Êµ{¦¡¤@Äýªí</title>
-
- <mediaobject>
- <imageobject>
- <imagedata fileref="install/hdwrconf" format="PNG">
- </imageobject>
- </mediaobject>
- </figure>
- </step>
-
- <step>
- <para>Disable all the drivers for devices that you do not have. To
- disable a driver, highlight it with the arrow keys and press
- <keycap>Del</keycap>. The driver will be moved to the
- <literal>Inactive Drivers</literal> list.</para>
-
- <para>If you inadvertently disable a device that you need then press
- <keycap>Tab</keycap> to switch to the <literal>Inactive
- Drivers</literal> list, select the driver that you disabled, and
- press <keycap>Enter</keycap> to move it back to the active
- list.</para>
-
- <warning>
- <para>Do not disable <devicename>sc0</devicename>. This controls
- the screen, and you will need this unless you are installing
- over a serial cable.</para>
- </warning>
-
- <warning>
- <para>Only disable <devicename>atkbd0</devicename> if you are
- using a USB keyboard. If you have a normal keyboard then you
- must keep <devicename>atkbd0</devicename>.</para>
- </warning>
- </step>
-
- <step>
- <para>If there are no conflicts listed then you can skip this step.
- Otherwise, the remaining conflicts need to be examined. If they
- do not have the indication of an <quote>allowed conflict</quote>
- in the message area, then either the IRQ/address for device probe
- will need to be changed, <emphasis>or</emphasis> the IRQ/address
- on the hardware will need to be changed.</para>
-
- <para>To change the driver's configuration for IRQ and IO port
- address, select the device and press <keycap>Enter</keycap>. The
- cursor will move to the third section of the screen, and you can
- change the values. You should enter the values for IRQ and port
- address that you discovered when you made your hardware inventory.
- Press <keycap>Q</keycap> to finish editing the device's
- configuration and return to the active driver list.</para>
-
- <para>If you are not sure what these figures should be then you can
- try using <literal>-1</literal>. Some FreeBSD drivers can safely
- probe the hardware to discover what the correct value should be,
- and a value of <literal>-1</literal> configures them to do
- this.</para>
-
- <para>The procedure for changing the address on the hardware varies
- from device to device. For some devices you may need to
- physically remove the card from your computer and adjust jumper
- settings or DIP switches. Other cards may have come with a DOS
- floppy that contains the programs used to reconfigure the card.
- In any case, you should refer to the documentation that came with
- the device. This will obviously entail restarting your computer,
- so you will need to boot back into the FreeBSD installation
- routine when you have reconfigured the card.</para>
- </step>
-
- <step>
- <para>When all the conflicts have been resolved the screen will look
- similar to <xref linkend="userconfig-done">.</para>
-
- <figure id="userconfig-done">
- <title>¨S¦³½Ä¬ðªºÅX°Êµ{¦¡³]©w</title>
-
- <mediaobject>
- <imageobject>
- <imagedata fileref="install/probstart" format="PNG">
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>As you can see, the active driver list is now much smaller,
- with only drivers for the hardware that actually exists being
- listed.</para>
-
- <para>You can now save these changes, and move on to the next step
- of the install. Press <keycap>Q</keycap> to quit the device
- configuration interface. This message will appear:</para>
-
- <screen>Save these parameters before exiting? ([Y]es/[N]o/[C]ancel)</screen>
-
- <para>Answer <keycap>Y</keycap> to save the parameters to memory
- (it will be saved to disk if you finish the install) and the
- probing will start. After displaying the probe results in white
- on black text <application>sysinstall</application> will start
- and display its main menu
- (<xref linkend="sysinstall-main">).</para>
-
- <figure id="sysinstall-main">
- <title>Sysinstall ¥D¿ï³æ</title>
-
- <mediaobject>
- <imageobject>
- <imagedata fileref="install/main1" format="PNG">
- </imageobject>
- </mediaobject>
- </figure>
- </step>
- </procedure>
- </sect2>
<sect2 id="view-probe">
<title>¨ºn«ç»ò¥h½¾\°»´úµwÅ骺µ²ªG©O¡H</title>
@@ -1651,7 +1377,7 @@
to continue with the installation.</para>
</sect2>
- <sect2 id="disklabeleditor">
+ <sect2 id="bsdlabeleditor">
<title>¥H <application>Disklabel</application> ¨Ó«Ø¥ß¤À³Î°Ï(Partitions)
</title>
@@ -5117,8 +4843,8 @@
<xref linkend="ports">) as
necessary.</para>
- <para>Use the image of disc one if you want to install a
- &os; 4.<replaceable>X</replaceable> release and want
+ <para>Use the image of disc one if you want to install a &os;
+ release and want
a reasonable selection of third party packages on the disc
as well.</para>
@@ -5308,13 +5034,7 @@
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/base/">&rel.current;/base/</ulink>
directory.</para>
- <note>
- <para>In the 4.X and older releases of &os; the <quote>base</quote>
- distribution is called <quote>bin</quote>. Adjust the sample
- commands and URLs above accordingly, if you are using one of these
- versions.</para>
- </note>
-
+
<para>For as many distributions you wish to install from an &ms-dos;
partition (and you have the free space for), install each one
under <filename>c:\freebsd</filename> — the
diff -ruN zh_TW.Big5.org/books/handbook/introduction/chapter.sgml zh_TW.Big5/books/handbook/introduction/chapter.sgml
--- zh_TW.Big5.org/books/handbook/introduction/chapter.sgml Thu Jul 6 23:27:00 2006
+++ zh_TW.Big5/books/handbook/introduction/chapter.sgml Sat Jul 8 03:10:49 2006
@@ -655,76 +655,53 @@
<indexterm><primary>core team</primary></indexterm>
<listitem>
- <para><firstterm>FreeBSD core team</firstterm>
- ´Nµ¥©ó¸³¨Æ·| -- ¦pªG§â FreeBSD ¬Ý¦¨¬O¤@®a¤½¥qªº¸Ü¡C
+ <para>¦pªG§â FreeBSD ¬Ý¦¨¬O¤@®a¤½¥qªº¸Ü¡A<firstterm>FreeBSD core team</firstterm>
+ ´N¬Û·í©ó¡y¸³¨Æ·|(board of directors)¡z¡C
core team ªº¥Dn¾³d¦b©ó½T«O¦¹p¹º¦³¨}¦nªº¬[ºc¡A¥H´ÂµÛ¥¿½Tªº¤è¦Vµo®i¡C
¦¹¥~¡AÁܽмö¦å¥Bt³dªº³nÅé¶}µoªÌ¥[¤J committers ¦æ¦C¡A¥H¦bY¤z¦¨ûÂ÷¥h®É±o¥H¸É¥R·s¦å¡C
¥Ø«eªº core team ¬O¦b 2004 ¦~ 6 ¤ë committers Ô¿ï¤H¤¤¿ï¥X¨Óªº¡A¨C¨â¦~·|Á|¿ì¤@¦¸¿ïÁ|</para>
- <para>Some core team members also have specific areas of
- responsibility, meaning that they are committed to
- ensuring that some large portion of the system works as
- advertised. For a complete list of FreeBSD developers
- and their areas of responsibility, please see the <ulink
- url="&url.articles.contributors;/article.html">Contributors
- List</ulink></para>
+ <para>¦³¨Ç core team ¦¨ûÁÙt³d¬Y¨Ç¯S©w½d³ò¡A¤]´N¬O»¡¥LÌ¥²¶·ºÉ¶q½T«O¤@¨Ç¤l¨t²ÎªºÃ©w¡B®Ä¯à¡C
+ Ãö©ó FreeBSD ¶}µoªÌÌ¥H¤Î¦U¦Û³d¥ô½d³ò¡A½Ð°Ñ¾\ <ulink
+ url="&url.articles.contributors;/article.html">°^ÄmªÌ¦W³æ</ulink>¡C</para>
<note>
- <para>Most members of the core team are volunteers when it
- comes to FreeBSD development and do not benefit from the
- project financially, so <quote>commitment</quote> should
- also not be misconstrued as meaning <quote>guaranteed
- support.</quote> The <quote>board of directors</quote>
- analogy above is not very accurate, and it may be
- more suitable to say that these are the people who gave up
- their lives in favor of FreeBSD against their better
- judgment!</para>
+ <para>core team ¤j³¡¤À¦¨û¥[¤J FreeBSD ¶}µo³£¬O§Ó¤u©Ê½è¦Ó¤w¡A¨Ã¥¼±q¥»p¹º¤¤Àò±o¥ô¦óÁ~¹S¡A
+ ©Ò¥H¤£¸Ó§â <quote>commitment</quote> »~¸Ñ¬° <quote>guaranteed support</quote>
+ ¤~¹ï¡C è«e±©ÒÁ¿ªº¡y¸³¨Æ·|¡z¥i¯à¬O¤£«ê·íªºÃþ±À¡A©Î³\§ÚÌÀ³¸Ó»¡¡G
+ ¥L̬O¤@¸s¦ÛÄ@©ñ±ó쥻ªºÀu´ì¥Í¬¡¡BÓ¤H¨ä¥L»â°ì¦¨´N¡A¦Ó¿ï¾Ü§ë¤J FreeBSD ¶}µoªº¼ö¦å¦³¬°ªÌ¤~¹ï¡I</para>
</note>
</listitem>
</varlistentry>
<varlistentry>
- <term>Outside contributors</term>
+ <term>¨ä¥Lªº°^ÄmªÌ</term>
<indexterm><primary>contributors</primary></indexterm>
<listitem>
- <para>Last, but definitely not least, the largest group of
- developers are the users themselves who provide feedback and
- bug fixes to us on an almost constant basis. The primary
- way of keeping in touch with FreeBSD's more non-centralized
- development is to subscribe to the &a.hackers; where such
- things are discussed. See <xref
- linkend="eresources"> for more information about
- the various FreeBSD mailing lists.</para>
+ <para>³Ì«á¤@ÂI¡A¦ý³oÂIµ´«D³Ì¤£«nªº¡A³Ì¤jªº¶}µoªÌ¹Î¶¤´N¬O«ùÄò¬°§ÚÌ´£¨Ñ¦^õX¥H¤Î¿ù»~×¥¿ªº¨Ï¥ÎªÌ¦Û¤v¡C
+ »P FreeBSD «D®Ö¤ß¶}µoªÌ¤¬°Êªº¥Dn¤è¦¡¡A«K¬O³z¹Lq¾\ &a.hackers; ¨Ó¶i¦æ·¾³q¡A
+ ³o¤è±¥i°Ñ¦Ò¡A½Ð°Ñ¾\ <xref
+ linkend="eresources"> ¥HÁA¸Ñ¦U¦¡¤£¦Pªº FreeBSD ¶l»¼½×¾Â(mailing lists)¡C</para>
<para><citetitle><ulink
- url="&url.articles.contributors;/article.html">The
- FreeBSD Contributors List</ulink></citetitle> is a long
- and growing one, so why not join it by contributing
- something back to FreeBSD today?</para>
+ url="&url.articles.contributors;/article.html">FreeBSD °^ÄmªÌ¦W³æ</ulink></citetitle>
+ ¬Û·íªø¥B¤£Â_¦¨ªø¤¤¡A¥un¦³°^Äm´N·|³Q¦C¤J¨ä¤¤¡An¤£n¥ß§Y¦Ò¼{°^Äm FreeBSD ¤@¨Ç¦^õX©O¡H</para>
- <para>Providing code is not the only way of contributing to
- the project; for a more complete list of things that need
- doing, please refer to the <ulink
- url="&url.base;/index.html">FreeBSD Project web
- site</ulink>.</para>
+ <para>µM¦Ó¡A´£¨Ñì©l½X¨Ã«D¬°³oÓp¹º°µ°^Ämªº°ß¤@¤è¦¡¡F
+ ÁÙ»Ýn¤j®a§ë¤Jªº§¹¾ã¤u§@¦Cªí¡B»¡©ú¡A½Ð°Ñ¾\ <ulink
+ url="&url.base;/index.html">FreeBSD ©xºô</ulink>¡C</para>
</listitem>
</varlistentry>
</variablelist>
- <para>In summary, our development model is organized as a loose set
- of concentric circles. The centralized model is designed for the
- convenience of the <emphasis>users</emphasis> of FreeBSD, who are
- provided with an easy way of tracking one central code
- base, not to keep potential contributors out! Our desire is to
- present a stable operating system with a large set of coherent
- <link linkend="ports">application programs</link> that the users
- can easily install and use — this model works very well in
- accomplishing that.</para>
+ <para>²³æªº»¡¡A§Ú̪º¶}µo¼Ò¦¡´N¹³¬O¤@²Õ¨S¦³©ë§ôªº¦P¤ß¶ê¡C
+ ³oºØ¶°¤¤¶}µo¼Ò¦¡¬O¥H <emphasis>µ¹¨Ï¥ÎªÌ¤è«K</emphasis>¡A
+ ¦P®ÉÅý¥L̯à«Ü®e©ö¦a¦@¦PºûÅ@³nÅé¡A¦Ó¤£·|§â¼ç¦bªº°^ÄmªÌ±Æ°£¦b¥~¡I
+ §Ú̪º¥Ø¼Ð¬O´£¨Ñ§t¦³¤j¶q¤@P©Êªº <link linkend="ports">À³¥Î³nÅé(ports/packages)</link>
+ ¡A¥H«KÅý¨Ï¥ÎªÌ»´ÃP¦w¸Ë¡B¨Ï¥Îªº§@·~¨t²Î ¡X¡X ¦Ó³o¶}µo¼Ò¦¡¬Û·í²Å¦X¦¹¤@¥Ø¼Ð¡C</para>
- <para>All we ask of those who would join us as FreeBSD developers is
- some of the same dedication its current people have to its
- continued success!</para>
+ <para>§Ú̹ï©ó¨º¨Ç·Qn¥[¤J FreeBSD ¶}µoªÌªº´Á«Ý¬O¡G½Ð«O«ù¦p¦P«e¤H¤@¼Ëªº§ë¤J¡A¥H½T«OÄ~Äò¦¨¥\¡I</para>
</sect2>
<sect2 id="relnotes">
diff -ruN zh_TW.Big5.org/books/handbook/l10n/chapter.sgml zh_TW.Big5/books/handbook/l10n/chapter.sgml
--- zh_TW.Big5.org/books/handbook/l10n/chapter.sgml Thu Jul 6 23:27:00 2006
+++ zh_TW.Big5/books/handbook/l10n/chapter.sgml Sat Jul 8 03:11:07 2006
@@ -37,7 +37,7 @@
<para>Ū§¹³o³¹¡A±z±N¤F¸Ñ¡J</para>
<itemizedlist>
<listitem><para>¦UºØ¤£¦Pªº»y¨¥»P¦a°Ï³]©w¦p¦ó¦b§@·~¨t²Î¤W¶i¦æ½s½X¡C</para></listitem>
- <listitem><para>¦p¦ó³]©wµn¤J¥Îªº shell »y¨tÀô¹Ò¡C/para></listitem>
+ <listitem><para>¦p¦ó³]©wµn¤J¥Îªº shell »y¨tÀô¹Ò¡C</para></listitem>
<listitem><para>¦p¦ó±N§Aªº console ³]¬°^»y¥H¥~ªº»y¨t³]©w¡C</para></listitem>
<listitem><para>¦p¦ó¨Ï¥Î¤£¦P»y¨tªº³]©w¡A¨ÓÅý X Window ¹B§@§ó¿Ë¤Á¡C</para></listitem>
<listitem><para>þÃä¥i¥H§ä¨ì§ó¦h»P i18n ³W®æ¬Û®eªºÀ³¥Îµ{¦¡³W®æ¸ê®Æ¡C</para></listitem>
--- zh_TW.Big5.20060707.svn702.diff ends here ---
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-doc
mailing list