From chinsan.tw@gmail.com  Fri Jul  7 19:17:50 2006
Return-Path: <chinsan.tw@gmail.com>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4F33316A4DA;
	Fri,  7 Jul 2006 19:17:50 +0000 (UTC)
	(envelope-from chinsan.tw@gmail.com)
Received: from smtp2.bc.hgc.com.tw (smtp2.bc.hgc.com.tw [203.133.1.156])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 92AD843D45;
	Fri,  7 Jul 2006 19:17:49 +0000 (GMT)
	(envelope-from chinsan.tw@gmail.com)
Received: from smtp2.bc.hgc.com.tw (u14-109.u203-187.giga.net.tw [203.187.14.109])
	by smtp2.bc.hgc.com.tw (Postfix) with SMTP id 2918C2E970;
	Sat,  8 Jul 2006 03:17:47 +0800 (CST)
Received: by smtp2.bc.hgc.com.tw (sSMTP sendmail emulation); Sat,  8 Jul 2006 03:21:13 +0800
Message-Id: <20060707191747.2918C2E970@smtp2.bc.hgc.com.tw>
Date: Sat,  8 Jul 2006 03:21:13 +0800
From: chinsan <chinsan.tw@gmail.com>
Reply-To: chinsan <chinsan.tw@gmail.com>
To: FreeBSD-gnats-submit@freebsd.org
Cc: vanilla@FreeBSD.org
Subject: [UPDATE] zh_TW: Update to (20060707) svn#702
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         99891
>Category:       docs
>Synopsis:       [UPDATE] zh_TW: Update to (20060707) svn#702
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          update
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jul 07 19:20:20 GMT 2006
>Closed-Date:    Sat Jul 08 03:21:03 GMT 2006
>Last-Modified:  Sat Jul 08 03:21:03 GMT 2006
>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@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`@NOtγ]wC
+      Ttγ]wAiHAɯŪYhOC
+      ۭ󤶲 &os; n]wWA]A@ǥiHվ &os; į઺ѼƳ]wC
       </para>
 
     <para>ŪoAzNFѡ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> ]wP <filename>/usr/local/etc/rc.d</filename> Ұʬ[cF</para>
+	<para><filename>rc.conf</filename> ]wP <filename>/usr/local/etc/rc.d</filename> Ұʬ[cC</para>
       </listitem>
       <listitem>
-	<para>p]wBպdF</para>
+	<para>p]wBպdC</para>
       </listitem>
       <listitem>
-	<para>How to configure virtual hosts on your network devices.</para>
+	<para>p]w virtual hostsC</para>
       </listitem>
       <listitem>
 	<para>p]w <filename>/etc</filename> Uس]wɡC</para>
       </listitem>
       <listitem>
-        <para>pH <command>sysctl</command> ӽվ &os; tήįF</para>
+        <para>pH <command>sysctl</command> ӽվ &os; tήįC</para>
       </listitem>
       <listitem>
 	<para>pվwЮįAHΧ kernel C</para>
       </listitem>
     </itemizedlist>
 
-    <para>b\ŪoeAzFѡG</para>
+    <para>b}l\ŪoeAzݭnJ</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]wBsĶ 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аOG
+	  wЦbǿƤ譱A(ѩ󵲺cФ])~|񤺰ӱo֨ǡC
+	  ]AĳpB`|sΰϾq~AӸjΰϹO 
+	  <filename>/usr</filename> hbC
+	  ĳإߤΰϪǡAHOGroot, swap,
+	  <filename>/var</filename>, <filename>/usr</filename> o˶Ǩӫإ߷|C</para>
+
+	<para><filename>/var</filename> jpnγ~өwC
+	  <filename>/var</filename> OΨө
+	  HcBlog ɥHΦLC(spools)C  HcHΰOɪTץiLkwA
+	  ]oǦTפDOMh֥ΤBnh[޲zhөwC
+	  q`oǨϥΪ̨èSΨ 1 GB HWAФOGܤ֭nOd@wŶ <filename>/var/tmp</filename> 
+	  HKs packagesC
 	  </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> ΰϥDnOΨөtιB@ɩһݪɮסBu{AҦpG
+	  &man.ports.7; collection(ĳw) source tree(optional)C
+	  bw FreeBSD ɡAo̳Oiܸ˻P˪C
+	  LAoӤΰϫĳܤ֭n 2 GB ŶHW~ΡC</para>
+
+	<para>WΰϤjpɡAOohOdǦŶC
+	  _hYYӤΰϺFAt@ӤΰϫoٳѫܦhŶAN|۷x~C</para>
+
+	<note><para>ǤHi|o{ &man.sysinstall.8; 
+	    <literal>Auto-defaults(۰ʹw])</literal> ҰΰϤjpA
+	    ɭԷ| <filename>/var</filename> H <filename>/</filename> ΰϳ]ӤpFC
+	    ڭ̫ĳOGШ̨ϥαpHλݨDAӤʽվΰϤjpC</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&nbsp;megabytes of memory,
-	  the swap file should be 256&nbsp;megabytes.  Systems with
+	<para>ھڸgkhAq` swap ΰӳ]tΰO(RAM)jp⭿YiC
+	  |ҨӻGY 128&nbsp;MB RAM ܡA 
+	  swap hӳ] 256&nbsp;MBC  Systems with
 	  less memory may perform better with more swap.
 	  Less than 256&nbsp;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@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>ii֪ FreeBSD ϱo{LBC򤣤W̷siסI
+    ϦӼƦ쪩귽A]\ɨäO̦nAq`Oߤ@@ӸW̷sii覡C
+    ѩ FreeBSD OӦ۩\hӤuVOAҥHsjϥΪ̸s]q`t <quote>IT޳N䴩</quote> C
+    unιqllM USENET sDsմNiHܧֳtapôoǪsFC</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>HU²P FreeBSD sfWuDn覡C
+    YA٪DLǫSCX귽AЧi &a.doc;AHKڭ̧sC</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;&nbsp;&rel.current;-RELEASE AiH <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/floppies/"></ulink> UC</para>
 
 	  <para>M(images)ɦWO <filename>.flp</filename> C
-	    <filename>floppies/</filename> ؿ]t@ǤPγ~M(images)AoMzn˪ FreeBSD BݨDBwtƬC
-	    Yn˪O
-	    FreeBSD&nbsp;4.X q`uݭn 2 ӬMɡA]NO <filename>kern.flp</filename> P
-	    <filename>mfsroot.flp</filename>CӭYn˪O FreeBSD&nbsp;5.X
-	    Aq`n 3 ӬMɡA]NOG <filename>boot.flp</filename>B
+	    <filename>floppies/</filename> ؿ]t@ǤPγ~M(images)A
+	    oMzn˪ FreeBSD BݨDBwtƬC
+	    q`n 3 ӬMɡA]NOG <filename>boot.flp</filename>B
 	    <filename>kern1.flp</filename>B
 	    <filename>kern2.flp</filename>CYðݪܡA½\P@ؿU 
 	    <filename>README.TXT</filename> ɡAHAѬ̷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>ziH 10 AάO <keycap>Enter</keycap> C
-	    (YO &os;&nbsp;4.X ܡAhNX{ kernel configuration e)</para>
+	  <para>ziH 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 }lAη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> DO@~tΤ֤ߡAtd\hƱAOGtΤWҦ]ơApwСBdBĥdC
-	C FreeBSD Ҥ䴩w鳣۹Xʵ{C
-	CXʵ{Wٳ 2  3 ӦrҲզAO <devicename>sa</devicename> N SCSI Xʵ{A 
-	<devicename>sio</devicename> N Serial I/O Xʵ{( COM ports Ϊ)C</para>
-
-      <para> kernel }lҰʮɡACXʵ{N|hˬdtΤWO_䴩wsbA
-        YܡAXʵ{N|@w]wAHK kernel ϥθӵwC</para>
-
-      <para>Wzˬdʧ@Aڭ̺٬ <firstterm>device probing(w)</firstterm>C
-	  OAoˤl覡äOû򶶧QC
-	ǵwXʵ{LkPɦ@sAӦɭ԰YwɡAS|yt@w餣íXlC
-	oDADOѩ <acronym>PC</acronym> ]pWѥͪҭPC</para>
-
-      <para>Many older devices are called ISA devices&mdash;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 ]we</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 ]we</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>nh½\w骺GOH</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;&nbsp;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> &mdash; 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󸳨Ʒ| -- pG FreeBSD ݦO@aqܡC
+	    <para>pG FreeBSD ݦO@aqܡA<firstterm>FreeBSD core team</firstterm>
+	      N۷yƷ|(board of directors)zC
 	      core team Dn¾dbTOp}n[cAHµۥTVoiC
               ~AܽмBtdn}o̥[J committers CAHbYzhɱoHɥRsC
               ثe core team Ob 2004 ~ 6  committers ԿHXӪAC~||@|</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 ٭tdYǯSwdA]NOL̥ɶqTO@ǤltΪíwBįC
+	       FreeBSD }o̭̥HΦU۳ddAаѾ\ <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 }oOӤuʽӤwAåqpo~SA
+	        ҥHӧ <quote>commitment</quote> ~Ѭ <quote>guaranteed support</quote> 
+	        ~C eyƷ|ziOAγ\ڭӻG
+	        L̬O@s@쥻uͬBӤHL즨NAӿܧ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>̫@IAoID̤nA̤j}o̹ζNO򬰧ڭ̴Ѧ^XHο~ץϥΪ̦ۤvC
+	      P FreeBSD D֤߶}o̤ʪDn覡AKOzLq\ &a.hackers; Ӷi淾qA
+	      o譱iѦҡAаѾ\ <xref
+              linkend="eresources"> HAѦUP 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_Aun^mN|QCJ䤤AnnߧYҼ{^m FreeBSD @Ǧ^XOH</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ѭlXëDoӭp^mߤ@覡F
+	      ٻݭnjaJu@CBAаѾ\ <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 &mdash; this model works very well in
-	accomplishing that.</para>
+      <para>²檺Aڭ̪}oҦNO@ըSP߶C
+        oض}oҦOH <emphasis>ϥΪ̤K</emphasis>A
+        PL̯ܮea@P@nAӤ|b^m̱ưb~I
+	ڭ̪ؼЬOѧtjq@Pʪ <link linkend="ports">γn(ports/packages)</link>
+	AHKϥΪ̻PwˡBϥΪ@~t XX ӳ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̪ݬOGЫOpPeH@˪JAHTO~򦨥\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>ŪoAzNFѡJ</para>
     <itemizedlist>
       <listitem><para>UؤPyPaϳ]wpb@~tΤWisXC</para></listitem>
-      <listitem><para>p]wnJΪ shell ytҡC/para></listitem>
+      <listitem><para>p]wnJΪ shell ytҡC</para></listitem>
       <listitem><para>pNA console ]^yH~yt]wC</para></listitem>
       <listitem><para>pϥΤPyt]wA X Window B@ˤC</para></listitem>
       <listitem><para>iHhP i18n Wۮeε{WơC</para></listitem>
--- zh_TW.Big5.20060707.svn702.diff ends here ---


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: vanilla 
State-Changed-When: Sat Jul 8 03:21:02 UTC 2006 
State-Changed-Why:  
Committed, thanks. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=99891 
>Unformatted:
