From chinsan.tw@gmail.com  Sat Jul  8 19:34:25 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 C9A4816A4E1;
	Sat,  8 Jul 2006 19:34:25 +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 C6A7143D45;
	Sat,  8 Jul 2006 19:34:24 +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 16FA72E970;
	Sun,  9 Jul 2006 03:34:22 +0800 (CST)
Received: by smtp2.bc.hgc.com.tw (sSMTP sendmail emulation); Sun,  9 Jul 2006 03:37:54 +0800
Message-Id: <20060708193422.16FA72E970@smtp2.bc.hgc.com.tw>
Date: Sun,  9 Jul 2006 03:37:54 +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 to 20060708 (SVN#721)
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         99924
>Category:       docs
>Synopsis:       Update to 20060708 (SVN#721)
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          update
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jul 08 19:40:11 GMT 2006
>Closed-Date:    Sun Jul 09 03:19:28 GMT 2006
>Last-Modified:  Sun Jul 09 03:19:28 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 20060708 (SVN#721)
( http://chinsan2.twbbs.org/chinsan/zh_TW.Big5.20060708.svn721.diff )

Thanks.

>How-To-Repeat:
>Fix:

--- zh_TW.Big5.200607008.svn721.diff begins here ---
diff -ruN zh_TW.Big5.orig/articles/Makefile zh_TW.Big5/articles/Makefile
--- zh_TW.Big5.orig/articles/Makefile	Sat Jun 17 18:22:42 2006
+++ zh_TW.Big5/articles/Makefile	Sun Jul  9 03:21:26 2006
@@ -3,6 +3,7 @@
 SUBDIR =
 SUBDIR+= contributing
 SUBDIR+= cvs-freebsd
+SUBDIR+= freebsd-questions
 SUBDIR+= hubs
 SUBDIR+= mailing-list-faq
 SUBDIR+= pr-guidelines
diff -ruN zh_TW.Big5.orig/articles/freebsd-questions/Makefile zh_TW.Big5/articles/freebsd-questions/Makefile
--- zh_TW.Big5.orig/articles/freebsd-questions/Makefile	Thu Jan  1 08:00:00 1970
+++ zh_TW.Big5/articles/freebsd-questions/Makefile	Sun Jul  9 03:21:26 2006
@@ -0,0 +1,22 @@
+#
+# $FreeBSD$
+# Original revision: 1.6
+#
+# Article: How to get best results from the FreeBSD-questions mailing list
+
+MAINTAINER=chinsan.tw@gmail.com
+
+DOC?= article
+
+FORMATS?= html
+WITH_ARTICLE_TOC?= YES
+
+INSTALL_COMPRESSED?= gz
+INSTALL_ONLY_COMPRESSED?=
+
+SRCS=	article.sgml
+
+URL_RELPREFIX?=	../../../..
+DOC_PREFIX?= ${.CURDIR}/../../..
+
+.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff -ruN zh_TW.Big5.orig/articles/freebsd-questions/article.sgml zh_TW.Big5/articles/freebsd-questions/article.sgml
--- zh_TW.Big5.orig/articles/freebsd-questions/article.sgml	Thu Jan  1 08:00:00 1970
+++ zh_TW.Big5/articles/freebsd-questions/article.sgml	Sun Jul  9 03:21:26 2006
@@ -0,0 +1,627 @@
+<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
+<!ENTITY % articles.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN">
+%articles.ent;
+]>
+
+<!--
+  Original revision: 1.24
+-->
+
+<article>
+  <articleinfo>
+    <title>pb FreeBSD-questions mailing list Wo쥿</title>
+
+    <author>
+      <firstname>Greg</firstname>
+      <surname>Lehey</surname>
+
+      <affiliation>
+	<address><email>grog@FreeBSD.org</email></address>
+      </affiliation>
+    </author>
+
+    <pubdate>$FreeBSD$</pubdate>
+
+    <legalnotice id="trademarks" role="trademarks">
+      &tm-attrib.freebsd;
+      &tm-attrib.microsoft;
+      &tm-attrib.netscape;
+      &tm-attrib.opengroup;
+      &tm-attrib.qualcomm;
+      &tm-attrib.general;
+    </legalnotice>
+
+    <abstract>
+      <para>DnOǳƼgH FreeBSD-questions mailing list HѤ@ǰѦҡC
+        ڭ̷|A@ǵoݪޥPĳAHKAױo󦳥ΪСC</para>
+
+      <para>|wo FreeBSD-questions mailing list WC</para>
+    </abstract>
+  </articleinfo>
+  
+  <sect1>
+    <title id="Introduction">²</title>
+    
+    <para><literal>FreeBSD-questions</literal> is a mailing list maintained by
+      the FreeBSD project to help people who have questions about the normal
+      use of FreeBSD.  Another group, <literal>FreeBSD-hackers</literal>,
+      discusses more advanced questions such as future development
+      work.</para>
+
+    <note>
+      <para>The term <quote>hacker</quote> has nothing to do with breaking
+	into other people's computers.  The correct term for the latter
+	activity is <quote>cracker</quote>, but the popular press has not found
+	out yet.  The FreeBSD hackers disapprove strongly of cracking
+	security, and have nothing to do with it.  For a longer description of
+	hackers, see Eric Raymond's <ulink
+	url="http://www.catb.org/~esr/faqs/hacker-howto.html">How To Become
+	A Hacker</ulink></para>
+    </note>
+    
+    <para>This is a regular posting aimed to help both those seeking advice
+      from FreeBSD-questions (the <quote>newcomers</quote>), and also those
+      who answer the questions (the <quote>hackers</quote>).</para>
+
+    <para>Inevitably there is some friction, which stems from the different
+      viewpoints of the two groups.  The newcomers accuse the hackers of being
+      arrogant, stuck-up, and unhelpful, while the hackers accuse the
+      newcomers of being stupid, unable to read plain English, and expecting
+      everything to be handed to them on a silver platter.  Of course, there is
+      an element of truth in both these claims, but for the most part these
+      viewpoints come from a sense of frustration.</para>
+
+    <para>In this document, I would like to do something to relieve this
+      frustration and help everybody get better results from
+      FreeBSD-questions.  In the following section, I recommend how to submit
+      a question; after that, we will look at how to answer one.</para>
+  </sect1>
+  
+  <sect1>
+    <title id="subscribe">How to subscribe to FreeBSD-questions</title>
+
+    <para>FreeBSD-questions is a mailing list, so you need mail access.  Point
+      your WWW browser to the <ulink url="&a.questions.url;">information page of the FreeBSD-questions mailing list</ulink>.
+      In the section titled <quote>Subscribing to freebsd-questions</quote> fill
+      in the <quote>Your email address</quote> field; the other fields are optional.
+    </para>
+
+    <note>
+      <para>The password fields in the subscription form provide only mild
+        security, but should prevent others from messing with your
+        subscription.  <emphasis>Do not use a valuable password</emphasis> as
+        it will occasionally be emailed back to you in cleartext.</para>
+    </note>
+
+    <para>You will receive a confirmation message from
+      <application>mailman</application>; follow the included instructions
+      to complete your subscription.</para>
+
+    <para>Finally, when you get the <quote>Welcome</quote> message from
+      <application>mailman</application> telling you the details of the list
+      and subscription area password, <emphasis>please save it</emphasis>.
+      If you ever should want to leave the list, you will need the information
+      there.  See the next section for more details.</para>
+  </sect1>
+  
+  <sect1>
+    <title id="unsubscribe">How to unsubscribe from FreeBSD-questions</title>
+
+    <para>When you subscribed to FreeBSD-questions, you got a welcome message
+      from <application>mailman</application>.  In this message, amongst
+      other things, it told you how to unsubscribe.  Here is a typical
+      message:</para>
+
+    <literallayout class="monospaced">Welcome to the freebsd-questions@freebsd.org mailing list!
+
+To post to this list, send your email to:
+
+  freebsd-questions@freebsd.org
+
+General information about the mailing list is at:
+
+  http://lists.freebsd.org/mailman/listinfo/freebsd-questions
+
+If you ever want to unsubscribe or change your options (e.g., switch to
+or from digest mode, change your password, etc.), visit your
+subscription page at:
+                                                                                
+http://lists.freebsd.org/mailman/options/freebsd-questions/grog%40lemsi.de
+
+You can also make such adjustments via email by sending a message to:
+
+  freebsd-questions-request@freebsd.org
+
+with the word `help' in the subject or body (don't include the
+quotes), and you will get back a message with instructions.
+
+You must know your password to change your options (including changing
+the password, itself) or to unsubscribe.  It is:
+
+  12345
+
+Normally, Mailman will remind you of your freebsd.org mailing list
+passwords once every month, although you can disable this if you
+prefer.  This reminder will also include instructions on how to
+unsubscribe or change your account options.  There is also a button on
+your options page that will email your current password to you.</literallayout>
+
+    <para>From the URL specified in your <quote>Welcome</quote> message you
+      may visit the <quote>Account management page</quote> and enter a request
+      to <quote>Unsubscribe</quote> you from FreeBSD-questions mailing
+      list.</para>
+
+    <para>A confirmation message will be sent to you from
+      <application>mailman</application>; follow the included instructions
+      to finish unsubscribing.</para>
+
+    <para>If you have done this, and you still can not figure out what
+      is going on, send a message to
+      <email>freebsd-questions-request@FreeBSD.org</email>, and they will
+      sort things out for you.  <emphasis>Do not</emphasis> send a message to
+      FreeBSD-questions: they can not help you.</para>
+  </sect1>
+
+  <sect1>
+    <title id="askwho">Should I ask <literal>-questions</literal> or
+      <literal>-hackers</literal>?</title>
+
+    <para>Two mailing lists handle general questions about FreeBSD,
+      <literal>FreeBSD-questions</literal> and
+      <literal>FreeBSD-hackers</literal>.  In some cases, it is not really
+      clear which group you should ask.  The following criteria should help
+      for 99% of all questions, however:</para>
+    
+    <orderedlist>
+      <listitem>
+	<para>If the question is of a general nature, ask
+	  <literal>FreeBSD-questions</literal>.  Examples might be questions
+	  about installing FreeBSD or the use of a particular &unix;
+	  utility.</para>
+      </listitem>
+      
+      <listitem>
+	<para>If you think the question relates to a bug, but you are not sure,
+	  or you do not know how to look for it, send the message to
+	  <literal>FreeBSD-questions</literal>.</para>
+      </listitem>
+      
+      <listitem>
+	<para>If the question relates to a bug, and you are
+	  <emphasis>sure</emphasis> that it is a bug (for example, you can
+	  pinpoint the place in the code where it happens, and you maybe have
+	  a fix), then send the message to
+	  <literal>FreeBSD-hackers</literal>.</para>
+      </listitem>
+
+      <listitem>
+	<para>If the question relates to enhancements to FreeBSD, and you
+	  can make suggestions about how to implement them, then send the
+	  message to <literal>FreeBSD-hackers</literal>.</para>
+      </listitem>
+    </orderedlist>
+
+    <para>There are also a number of other specialized mailing lists, for
+      example <literal>FreeBSD-isp</literal>, which caters to the interests of
+      ISPs (Internet Service Providers) who run FreeBSD.  If you happen to be
+      an ISP, this does not mean you should automatically send your questions
+      to <literal>FreeBSD-isp</literal>.  The criteria above still apply, and
+      it is in your interest to stick to them, since you are more likely to get
+      good results that way.</para>
+  </sect1>
+
+  <sect1>
+    <title id="before">Before submitting a question</title>
+    
+    <para>You can (and should) do some things yourself before asking a question
+      on one of the mailing lists:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>Try solving the problem on your own.  If you post a question which
+	  shows that you have tried to solve the problem, your question will
+	  generally attract more positive attention from people reading it.
+	  Trying to solve the problem yourself will also enhance your understanding
+	  of FreeBSD, and will eventually let you use your knowledge to help others
+	  by answering questions posted to the mailing lists.
+	</para>
+      </listitem>
+
+      <listitem>
+        <para>Read the manual pages, and the FreeBSD documentation (either
+	  installed in <filename>/usr/doc</filename> or accessible via WWW at
+	  <ulink url="http://www.FreeBSD.org"></ulink>), especially the
+	  <ulink url="&url.books.handbook;/index.html">handbook</ulink>
+	  and the <ulink url="&url.books.faq;/index.html">FAQ</ulink>.
+	</para>
+      </listitem>
+
+      <listitem>
+        <para>Browse and/or search the archives for the mailing list, to see if your
+	  question or a similar one has been asked (and possibly answered) on the
+	  list.  You can browse and/or search the mailing list archives
+	  at <ulink url="http://www.FreeBSD.org/mail"></ulink>
+	  and <ulink url="http://www.FreeBSD.org/search/search.html#mailinglists"></ulink>
+	  respectively.  This can be done at other WWW sites as well, for example
+	  at <ulink url="http://marc.theaimsgroup.com"></ulink>.
+	</para>
+      </listitem>
+
+      <listitem>
+        <para>Use a search engine such as <ulink url="http://www.google.com">Google</ulink>
+          or <ulink url="http://www.yahoo.com">Yahoo</ulink> to find answers to your question.
+	  Google even has a <ulink
+	  url="http://www.google.com/bsd">BSD-specific search interface</ulink>.
+        </para>
+      </listitem>
+    </itemizedlist>
+  </sect1>
+  
+  <sect1>
+    <title id="submit">How to submit a question</title>
+  
+    <para>When submitting a question to FreeBSD-questions, consider the
+      following points:</para>
+
+    <itemizedlist>
+      <listitem>
+	<para>Remember that nobody gets paid for answering a FreeBSD
+	  question. They do it of their own free will.  You can influence this
+	  free will positively by submitting a well-formulated question
+	  supplying as much relevant information as possible.  You can
+	  influence this free will negatively by submitting an incomplete,
+	  illegible, or rude question. It is perfectly possible to send a
+	  message to FreeBSD-questions and not get an answer even if you
+	  follow these rules.  It is much more possible to not get an answer if
+	  you do not.  In the rest of this document, we will look at how to get
+	  the most out of your question to FreeBSD-questions.</para>
+      </listitem>
+      
+      <listitem>
+	<para>Not everybody who answers FreeBSD questions reads every message:
+	  they look at the subject line and decide whether it interests them.
+	  Clearly, it is in your interest to specify a subject. <quote>FreeBSD
+	  problem</quote> or <quote>Help</quote> are not enough.  If you provide no subject at
+	  all, many people will not bother reading it.  If your subject is not
+	  specific enough, the people who can answer it may not read
+	  it.</para>
+      </listitem>
+
+      <listitem>
+	<para>Format your message so that it is	legible, and
+	    PLEASE DO NOT SHOUT!!!!!.  We appreciate that a lot of people do not
+	    speak English as their first language, and we try to make
+	    allowances for that, but it is really painful to try to read a
+	    message written full of typos or without any line breaks.</para>
+	
+	<para>Do not underestimate the effect that a poorly formatted mail
+	  message has, not just on the FreeBSD-questions mailing list.
+	  Your mail message is all people see of you, and if it is poorly
+	  formatted, one line per paragraph, badly spelt, or full of
+	  errors, it will give people a poor impression of you.</para>
+
+	<para>A lot of badly formatted messages come from
+	  <ulink url="http://www.lemis.com/email.html">bad mailers or badly
+	  configured mailers</ulink>.  The following mailers are known to
+	  send out badly formatted messages without you finding out about
+	  them:</para>
+
+	<itemizedlist>
+	  <listitem>
+	    <para>cc:Mail</para>
+	  </listitem>
+
+	  <listitem>
+	    <para>&eudora;</para>
+	  </listitem>
+
+	  <listitem>
+	    <para>exmh</para>
+	  </listitem>
+
+	  <listitem>
+	    <para>&microsoft; Exchange</para>
+	  </listitem>
+
+	  <listitem>
+	    <para>&microsoft; Internet Mail</para>
+	  </listitem>
+
+	  <listitem>
+	    <para>&microsoft; &outlook;</para>
+	  </listitem>
+
+	  <listitem>
+	    <para>&netscape;</para>
+	  </listitem>
+	</itemizedlist>
+
+	<para>As you can see, the mailers in the Microsoft world are frequent
+	  offenders.  If at all possible, use a &unix; mailer. If you must use a
+	  mailer under Microsoft environments, make sure it is set up
+	  correctly. Try not to use <acronym>MIME</acronym>: a lot of people
+	  use mailers which do not get on very well with
+	  <acronym>MIME</acronym>.</para>
+      </listitem>
+      
+      <listitem>
+	<para>Make sure your time and time zone are set correctly.  This may
+	  seem a little silly, since your message still gets there, but many
+	  of the people you are trying to reach get several hundred messages a
+	  day.  They frequently sort the incoming messages by subject and by
+	  date, and if your message does not come before the first answer, they
+	  may assume they missed it and not bother to look.</para>
+      </listitem>
+
+      <listitem>
+	<para>Do not include unrelated questions in the same message.  Firstly,
+	  a long message tends to scare people off, and secondly, it is more
+	  difficult to get all the people who can answer all the questions to
+	  read the message.</para>
+      </listitem>
+
+      <listitem>
+	<para>Specify as much information as possible. This is a difficult
+	  area, and we need to expand on what information you need to submit,
+	  but here is a start:</para>
+
+	<itemizedlist>
+	  <listitem>
+	    <para>In nearly every case, it is important to know the version of
+	      FreeBSD you are running.  This is particularly the case for
+	      FreeBSD-CURRENT, where you should also specify the date of the
+	      sources, though of course you should not be sending questions
+	      about -CURRENT to FreeBSD-questions.</para>
+	  </listitem>
+	  
+	  <listitem><para>With any problem which <emphasis>could</emphasis> be
+	      hardware related, tell us about your hardware.  In case of
+	      doubt, assume it is possible that it is hardware.  What kind of
+	      CPU are you using?  How fast?  What motherboard?  How much
+	      memory?  What peripherals?</para>
+
+	    <para>There is a judgement call here, of course, but the output of
+	      the &man.dmesg.8; command can frequently be very useful, since it
+	      tells not just what hardware you are running, but what version of
+	      FreeBSD as well.</para>
+	  </listitem>
+	  
+	  <listitem>
+	    <para>If you get error messages, do not say <quote>I get error
+		messages</quote>, say (for example) <quote>I get the error
+		message 'No route to host'</quote>.</para>
+	  </listitem>
+
+	  <listitem>
+	    <para>If your system panics, do not say <quote>My system
+		panicked</quote>, say (for example) <quote>my system panicked
+		with the message 'free vnode isn't'</quote>.</para>
+	  </listitem>
+
+	  <listitem>
+	    <para>If you have difficulty installing FreeBSD, please tell us
+	      what hardware you have.  In particular, it is important to know
+	      the IRQs and I/O addresses of the boards installed in your
+	      machine.</para>
+	  </listitem>
+
+	  <listitem>
+	    <para>If you have difficulty getting PPP to run, describe the
+	      configuration.  Which version of PPP do you use?  What kind of
+	      authentication do you have?  Do you have a static or dynamic IP
+	      address?  What kind of messages do you get in the log
+	      file?</para>
+	  </listitem>
+	</itemizedlist>
+      </listitem>
+
+      <listitem>
+          <para>A lot of the information you need to supply is the output of
+	  programs, such as &man.dmesg.8;, or console messages, which usually
+	  appear in <filename>/var/log/messages</filename>.  Do not try to copy
+	  this information by typing it in again; it is a real pain, and you are
+	  bound to make a mistake. To send log file contents, either make a
+	  copy of the file and use an editor to trim the information to what
+	  is relevant, or cut and paste into your message.  For the output of
+	  programs like &man.dmesg.8;, redirect the output to a file and
+	  include that.  For example,</para>
+
+	<screen>&prompt.user; <userinput>dmesg &gt; /tmp/dmesg.out</userinput></screen>
+
+	<para>This redirects the information to the file
+	  <filename>/tmp/dmesg.out</filename>.</para>
+      </listitem>
+      
+      <listitem>
+	<para>If you do all this, and you still do not get an answer, there
+	  could be other reasons.  For example, the problem is so complicated
+	  that nobody knows the answer, or the person who does know the answer
+	  was offline.  If you do not get an answer after, say, a week, it
+	  might help to re-send the message.  If you do not get an answer to
+	  your second message, though, you are probably not going to get one
+	  from this forum.  Resending the same message again and again will
+	  only make you unpopular.</para>
+      </listitem>
+    </itemizedlist>
+    
+    <para>To summarize, let's assume you know the answer to the following
+      question (yes, it is the same one in each case).
+      You choose which of these two questions you would be more prepared to
+      answer:</para>
+
+    <example>
+      <title>Message 1</title>
+
+      <literallayout class="monospaced">Subject: HELP!!?!??
+I just can't get hits damn silly FereBSD system to
+workd, and Im really good at this tsuff, but I have never seen
+anythign sho difficult to install, it jst wont work whatever I try
+so why don't you guys tell me what I doing wrong.</literallayout>
+    </example>
+
+    <example>
+      <title>Message 2</title>
+
+    <literallayout class="monospaced">Subject: Problems installing FreeBSD
+
+I've just got the FreeBSD 2.1.5 CDROM from Walnut Creek, and I'm having a lot
+of difficulty installing it.  I have a 66 MHz 486 with 16 MB of
+memory and an Adaptec 1540A SCSI board, a 1.2GB Quantum Fireball
+disk and a Toshiba 3501XA CDROM drive.  The installation works just
+fine, but when I try to reboot the system, I get the message
+<quote>Missing Operating System</quote>.</literallayout>
+    </example>
+  </sect1>
+
+  <sect1>
+    <title id="followup">How to follow up to a question</title>
+
+    <para>Often you will want to send in additional information to a question
+      you have already sent.  The best way to do this is to reply to your
+      original message.  This has three advantages:</para>
+
+    <orderedlist>
+      <listitem>
+	<para>You include the original message text, so people will know what
+	  you are talking about.  Do not forget to trim unnecessary text out,
+	  though.</para>
+      </listitem>
+      
+      <listitem>
+	<para>The text in the subject line stays the same (you did remember to
+	  put one in, did you not?).  Many mailers will sort messages by
+	  subject. This helps group messages together.</para>
+      </listitem>
+
+      <listitem>
+	<para>The message reference numbers in the header will refer to the
+	  previous message.  Some mailers, such as
+	  <ulink url="http://www.mutt.org/">mutt</ulink>, can
+	  <emphasis>thread</emphasis> messages, showing the exact
+	  relationships between the messages.</para>
+      </listitem>
+    </orderedlist>
+  </sect1>
+  
+  <sect1>
+    <title id="answer">How to answer a question</title>
+
+
+    <para>Before you answer a question to FreeBSD-questions, consider:</para>
+
+    <orderedlist>
+      <listitem>
+	<para>A lot of the points on submitting questions also apply to
+	  answering questions.  Read them.</para>
+      </listitem>
+
+      <listitem>
+	<para>Has somebody already answered the question?  The easiest way to
+	  check this is to sort your incoming mail by subject: then
+	  (hopefully) you will see the question followed by any answers, all
+	  together.</para>
+	
+	<para>If somebody has already answered it, it does not automatically
+	  mean that you should not send another answer.  But it makes sense to
+	  read all the other answers first.</para>
+      </listitem>
+
+      <listitem>
+	<para>Do you have something to contribute beyond what has already been
+	  said?  In general, <quote>Yeah, me too</quote> answers do not help
+	  much, although there are exceptions, like when somebody is
+	  describing a problem he is having, and he does not know whether it is
+	  his fault or whether there is something wrong with the hardware or
+	  software.  If you do send a <quote>me too</quote> answer, you should
+	  also include any further relevant information.</para>
+      </listitem>
+
+      <listitem>
+	<para>Are you sure you understand the question?  Very frequently, the
+	  person who asks the question is confused or does not express himself
+	  very well.  Even with the best understanding of the system, it is
+	  easy to send a reply which does not answer the question.  This
+	  does not help: you will leave the person who submitted the question
+	  more frustrated or confused than ever.  If nobody else answers, and
+	  you are not too sure either, you can always ask for more
+	  information.</para>
+      </listitem>
+
+      <listitem>
+	<para>Are you sure your answer is correct?
+	If not, wait a day or so. If nobody else comes up with a
+	better answer, you can still reply and say, for example, <quote>I
+	do not know if this is correct, but since nobody else has
+	replied, why don't you try replacing your ATAPI CDROM with
+	a frog?</quote>.</para>
+      </listitem>
+
+      <listitem>
+	<para>Unless there is a good reason to do otherwise, reply to the
+	  sender and to FreeBSD-questions. Many people on the
+	  FreeBSD-questions are <quote>lurkers</quote>: they learn by reading
+	  messages sent and replied to by others. If you take a message which
+	  is of general interest off the list, you are depriving these people
+	  of their information. Be careful with group replies; lots of people
+	  send messages with hundreds of CCs. If this is the case, be sure to
+	  trim the Cc: lines appropriately.</para>
+      </listitem>
+      
+      <listitem>
+	<para>Include relevant text from the original message. Trim it to the
+	  minimum, but do not overdo it.  It should still be possible for
+	  somebody who did not read the original message to understand what
+	  you are talking about.</para>
+      </listitem>
+      
+      <listitem>
+	<para>Use some technique to identify which text came from the original
+	  message, and which text you add.  I personally find that prepending
+	  <quote><literal>&gt; </literal></quote> to the original message
+	  works best.  Leaving white space after the
+	  <quote><literal>&gt; </literal></quote> and leave empty lines
+	  between your text and the original text both make the result more
+	  readable.</para>
+      </listitem>
+
+      <listitem>
+	<para>Put your response in the correct place (after the text to which
+	  it replies).  It is very difficult to read a thread of responses
+	  where each reply comes before the text to which it replies.</para>
+      </listitem>
+
+      <listitem>
+	<para>Most mailers change the subject line on a reply by prepending a
+	  text such as <quote>Re: </quote>.  If your mailer does not do it
+	  automatically, you should do it manually.</para>
+      </listitem>
+      
+      <listitem>
+	<para>If the submitter did not abide by format conventions (lines too
+	  long, inappropriate subject line), <emphasis>please</emphasis> fix
+	  it. In the case of an incorrect subject line (such as
+	  <quote>HELP!!??</quote>), change the subject line to (say)
+	  <quote>Re: Difficulties with sync PPP (was: HELP!!??)</quote>.  That
+	  way other people trying to follow the thread will have less
+	  difficulty following it.</para>
+
+	<para>In such cases, it is appropriate to say what you did and why you
+	  did it, but try not to be rude.  If you find you can not answer
+	  without being rude, do not answer.</para>
+
+	<para>If you just want to reply to a message because of its bad
+	  format, just reply to the submitter, not to the list.  You can just
+	  send him this message in reply, if you like.</para>
+      </listitem>
+    </orderedlist>
+  </sect1>
+</article>
+
+<!-- 
+     Local Variables:
+     mode: sgml
+     sgml-indent-data: t
+     sgml-omittag: nil
+     sgml-always-quote-attributes: t
+     End:
+-->
diff -ruN zh_TW.Big5.orig/books/handbook/eresources/chapter.sgml zh_TW.Big5/books/handbook/eresources/chapter.sgml
--- zh_TW.Big5.orig/books/handbook/eresources/chapter.sgml	Sat Jul  8 11:01:13 2006
+++ zh_TW.Big5/books/handbook/eresources/chapter.sgml	Sun Jul  9 03:22:18 2006
@@ -20,518 +20,487 @@
   <sect1 id="eresources-mail">
     <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
-      fashion (or at all) if you post them only to one of the
-      <literal>comp.unix.bsd.freebsd.*</literal> groups.  By addressing your
-      questions to the appropriate mailing list you will reach both us and a
-      concentrated FreeBSD audience, invariably assuring a better (or at least
-      faster) response.</para>
-
-    <para>The charters for the various lists are given at the bottom of this
-      document.  <emphasis>Please read the charter before joining or sending
-	mail to any list</emphasis>.  Most of our list subscribers now receive
-      many hundreds of FreeBSD related messages every day, and by setting down
-      charters and rules for proper use we are striving to keep the
-      signal-to-noise ratio of the lists high. To do less would see the
-      mailing lists ultimately fail as an effective communications medium for
-      the project.</para>
-
-    <para>When in doubt about what list to post a question to, see <ulink
-      url="&url.articles.freebsd-questions;">How to get best results from
-        the FreeBSD-questions mailing list</ulink>.</para>
-
-    <para>Before posting to any list, please learn about how to best use
-      the mailing lists, such as how to help avoid frequently-repeated
-      discussions, by reading the <ulink url="&url.articles.mailing-list-faq;">
-        Mailing List Frequently Asked Questions</ulink> (FAQ) document.</para>
-
-    <para>Archives are kept for all of the mailing lists and can be searched
-      using the <ulink url="&url.base;/search/index.html">FreeBSD World
-	Wide Web server</ulink>.  The keyword searchable archive offers an
-      excellent way of finding answers to frequently asked questions and
-      should be consulted before posting a question.</para>
+    <para>MAj FreeBSD }oH USENET sDsաA
+      ڭ̤]Oҧڭ̥ûiHήɱozDC
+      רOAYzub 
+      <literal>comp.unix.bsd.freebsd.*</literal> 䤤sդoݪܡC
+      ĳzNDoAl׾(mailing list)WAiHP FreeBSD 
+      }o̩MLݭ̪DAq`]iHo@Ӹn(̰_X|)^C</para>
+
+    <para>᭱ЪOUPl׾¡BQ׳Wh(charter)C
+      <emphasis>bq\ list eAХ\ŪQ׳WhC</emphasis>
+      q\o list H̲{bCѳ|Ʀʫ FreeBSD HC
+      ӰQ׳WhqAhU󴣤ɩQ׫~C
+      _hAoǰQ FreeBSD  list ױNJq}Aӥh쥻NC</para>
+
+    <para>Ӧb list oıoܺôbɭԡANӬݬ <ulink
+      url="&url.articles.freebsd-questions;">mpb FreeBSD-questions mailing list Wo쥿ѡn
+      </ulink> @a</para>
+
+    <para>boDB^Ш list eAХŪL
+        <ulink url="&url.articles.mailing-list-faq;">
+        FreeBSD Mailing Lists `ݵ(FAQ)</ulink> @HǷ|p󵽥 mailing list 
+        A~קKOg`ƪgBԤ大Ʊo͡C</para>
+
+    <para> mailing lists QװOiHb <ulink url="&url.base;/search/index.html">
+      FreeBSD WWWD</ulink> WCѤFܴΪrjM\Aiz`ΰݵ(FAQ)
+      CӦb mailing lists WoݤeA]ХjMO_wѵC</para>
 
     <sect2 id="eresources-summary">
-      <title>List Summary</title>
+      <title>List @</title>
 
-      <para><emphasis>General lists:</emphasis> The following are general
-	lists which anyone is free (and encouraged) to join:</para>
+      <para><emphasis>@׾¡G</emphasis> HU list O@ʽAӥBjaiHۥѦaѻPA
+        ڭ̤]yjaq\G</para>
 
       <informaltable frame="none" pgwide="1">
 	<tgroup cols="2">
 	  <thead>
 	    <row>
-	      <entry>List</entry>
-	      <entry>Purpose</entry>
+	      <entry>List W</entry>
+	      <entry>ت</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry>&a.cvsall.name;</entry>
-	      <entry>Changes made to the FreeBSD source tree</entry>
+	      <entry>Ҧ FreeBSD (commit)O</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.advocacy.name;</entry>
-	      <entry>FreeBSD Evangelism</entry>
+	      <entry>FreeBSD c]֭qx</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.announce.name;</entry>
-	      <entry>Important events and project milestones</entry>
+	      <entry>nƥBp{O</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.arch.name;</entry>
-	      <entry>Architecture and design discussions</entry>
+	      <entry>[coQ</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.bugbusters.name;</entry>
-	      <entry>Discussions pertaining to the maintenance of the FreeBSD
-		problem report database and related tools</entry>
+	      <entry>FreeBSD D^(PR)Ʈw@ĳDPu</entry>
 	    </row>
 
     	    <row>
 	      <entry>&a.bugs.name;</entry>
-	      <entry>Bug reports</entry>
+	      <entry>Bug ^</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.chat.name;</entry>
-	      <entry>Non-technical items related to the FreeBSD
-		community</entry>
+	      <entry>D޳Ny FreeBSD sѰ</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.current.name;</entry>
-	      <entry>Discussion concerning the use of
-		&os.current;</entry>
+	      <entry>Q &os.current;  FreeBSD</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.isp.name;</entry>
-	      <entry>Issues for Internet Service Providers using
-		FreeBSD</entry>
+	      <entry>FreeBSD  ISP ~̧޳Ny</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.jobs.name;</entry>
-	      <entry>FreeBSD employment and consulting
-		opportunities</entry>
+	      <entry>FreeBSD HOȦ</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.policy.name;</entry>
-	      <entry>FreeBSD Core team policy decisions.  Low volume, and
-		read-only</entry>
+	      <entry>FreeBSD Core team  policy wQװϡCo̤峹hABu core team ~ioC</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.questions.name;</entry>
-	      <entry>User questions and technical support</entry>
+	      <entry>ϥΰDΧ޳N䴩</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.security-notifications.name;</entry>
-	      <entry>Security notifications</entry>
+	      <entry>w|}q</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.stable.name;</entry>
-	      <entry>Discussion concerning the use of
-		&os.stable;</entry>
+	      <entry>Q &os.stable;  FreeBSD</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.test.name;</entry>
-	      <entry>Where to send your test messages instead of one of
-		the actual lists</entry>
+	      <entry>׾·soϡAo̥iHApը</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
 
-      <para><emphasis>Technical lists:</emphasis> The following lists are for
-	technical discussion.  You should read the charter for each list
-	carefully before joining or sending mail to one as there are firm
-	guidelines for their use and content.</para>
+      <para><emphasis>޳N׾¡G</emphasis> HU list DOnHQ޳NDDA
+        b[Jq\ΰQפeAаȥJӾ\ŪC list W(charter)A
+        ]̪QפeYԪC</para>
 
       <informaltable frame="none" pgwide="1">
 	<tgroup cols="2">
 	  <thead>
 	    <row>
-	      <entry>List</entry>
-	      <entry>Purpose</entry>
+	      <entry>List W</entry>
+	      <entry>ت</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry>&a.acpi.name;</entry>
-	      <entry>ACPI and power management development</entry>
+	      <entry>ACPI HιqO޲zĳD</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.afs.name;</entry>
-	      <entry>Porting AFS to FreeBSD</entry>
+	      <entry> AFS  FreeBSD</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.aic7xxx.name;</entry>
-	      <entry>Developing drivers for the &adaptec; AIC 7xxx</entry>
+	      <entry>o &adaptec; AIC 7xxx Xʵ{</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.alpha.name;</entry>
-	      <entry>Porting FreeBSD to the Alpha</entry>
+	      <entry> FreeBSD  Alpha tά[c</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.amd64.name;</entry>
-	      <entry>Porting FreeBSD to AMD64 systems</entry>
+	      <entry> FreeBSD  AMD64 tά[c</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.apache.name;</entry>
-	      <entry>Discussion about <application>Apache</application> related ports</entry>
+	      <entry>Q <application>Apache</application>  ports ĳD</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.arm.name;</entry>
-	      <entry>Porting FreeBSD to &arm; processors</entry>
+	      <entry> FreeBSD  &arm; CPU [c</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.atm.name;</entry>
-	      <entry>Using ATM networking with FreeBSD</entry>
+	      <entry>b FreeBSD Wϥ ATM </entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.audit.name;</entry>
-	      <entry>Source code audit project</entry>
+	      <entry>Source code ](audit)p</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.binup.name;</entry>
-	      <entry>Design and development of the binary update system</entry>
+	      <entry>o binary ɯŤ覡</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.bluetooth.name;</entry>
-	      <entry>Using &bluetooth; technology in FreeBSD</entry>
+	      <entry>b FreeBSD ϥŪ(&bluetooth;)޳N</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.cluster.name;</entry>
-	      <entry>Using FreeBSD in a clustered environment</entry>
+	      <entry> FreeBSD bO[c(clustered environment)B</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.cvsweb.name;</entry>
-	      <entry>CVSweb maintenance</entry>
+	      <entry>CVSweb @</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.database.name;</entry>
-	      <entry>Discussing database use and development under
-		FreeBSD</entry>
+	      <entry>QצUƮwb FreeBSD oBB</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.doc.name;</entry>
-	      <entry>Creating FreeBSD related documents</entry>
+	      <entry>g FreeBSD </entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.drivers.name;</entry>
-	      <entry>Writing device drivers for &os;</entry>
+	      <entry>g &os; ΪXʵ{</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.eclipse.name;</entry>
-	      <entry>FreeBSD users of Eclipse IDE, tools, rich client
-	       applications and ports.</entry>
+	      <entry>FreeBSD  Eclipse IDE uRΪ̥y</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.emulation.name;</entry>
-	      <entry>Emulation of other systems such as
-		Linux/&ms-dos;/&windows;</entry>
+	      <entry>b FreeBSD WLtΡApGLinuxB&ms-dos;B&windows;</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.firewire.name;</entry>
-	      <entry>FreeBSD &firewire; (iLink, IEEE 1394) technical
-		discussion</entry>
+	      <entry>FreeBSD  &firewire; (iLink, IEEE 1394) 譱޳Ny</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.fs.name;</entry>
-	      <entry>File systems</entry>
+	      <entry>ɮרtΪQBo</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.geom.name;</entry>
-	      <entry>GEOM-specific discussions and implementations</entry>
+	      <entry>GEOM ĳDQBo</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.gnome.name;</entry>
-	      <entry>Porting <application>GNOME</application> and <application>GNOME</application> applications</entry>
+	      <entry> <application>GNOME</application>  <application>GNOME</application> γn</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.hackers.name;</entry>
-	      <entry>General technical discussion</entry>
+	      <entry>@޳NĳDQ</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.hardware.name;</entry>
-	      <entry>General discussion of hardware for running
-		FreeBSD</entry>
+	      <entry>FreeBSD WUwDy</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.i18n.name;</entry>
-	      <entry>FreeBSD Internationalization</entry>
+	      <entry>FreeBSD hy(Internationalization)</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.ia32.name;</entry>
-	      <entry>FreeBSD on the IA-32 (&intel; x86) platform</entry>
+	      <entry>FreeBSD b IA-32 (&intel; x86) xWϥαQ</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.ia64.name;</entry>
-	      <entry>Porting FreeBSD to &intel;'s upcoming IA64 systems</entry>
+	      <entry> FreeBSD  &intel;  IA64 x[c</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.ipfw.name;</entry>
-	      <entry>Technical discussion concerning the redesign of the IP
-		firewall code</entry>
+	      <entry> ipfw(IP firewall) ޳NQ</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.isdn.name;</entry>
-	      <entry>ISDN developers</entry>
+	      <entry>ISDN o</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.java.name;</entry>
-	      <entry>&java; developers and people porting &jdk;s to
-		FreeBSD</entry>
+	      <entry>&java; {}o̥Hβ &jdk;s  FreeBSD W</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.kde.name;</entry>
-	      <entry>Porting <application>KDE</application> and <application>KDE</application> applications</entry>
+	      <entry> <application>KDE</application> H <application>KDE</application> ε{</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.lfs.name;</entry>
-	      <entry>Porting LFS to FreeBSD</entry>
+	      <entry> LFS  FreeBSD</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.libh.name;</entry>
-	      <entry>The second generation installation and package
-	         system</entry>
+	      <entry>s@NwˡB]M</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.mips.name;</entry>
-	      <entry>Porting FreeBSD to &mips;</entry>
+	      <entry> FreeBSD  &mips;</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.mobile.name;</entry>
-	      <entry>Discussions about mobile computing</entry>
+	      <entry>U mobile computing(pGOq)Q</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.mozilla.name;</entry>
-	      <entry>Porting <application>Mozilla</application> to FreeBSD</entry>
+	      <entry> <application>Mozilla</application> n鲾Ө FreeBSD</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.multimedia.name;</entry>
-	      <entry>Multimedia applications</entry>
+	      <entry>UvBΡBn</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.newbus.name;</entry>
-	      <entry>Technical discussions about bus architecture</entry>
+	      <entry>U bus [c޳NQ</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.net.name;</entry>
-	      <entry>Networking discussion and TCP/IP source code</entry>
+	      <entry>BαQP TCP/IP source code</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.openoffice.name;</entry>
-	      <entry>Porting <application>OpenOffice.org</application> and
-		<application>&staroffice;</application> to FreeBSD</entry>
+	      <entry> <application>OpenOffice.org</application> 
+		<application>&staroffice;</application>  FreeBSD</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.performance.name;</entry>
-	      <entry>Performance tuning questions for high
-		performance/load installations</entry>
+	      <entry>bį/tҤUįծ(tuning)ĳD</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.perl.name;</entry>
-	      <entry>Maintenance of a number of
-		Perl-related ports</entry>
+	      <entry>Q Perl  ports @</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.pf.name;</entry>
-	      <entry>Discussion and questions about the packet filter
-		firewall system</entry>
+	      <entry>pf(packet filter) Q</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.platforms.name;</entry>
-	      <entry>Concerning ports to non &intel; architecture
-		platforms</entry>
+	      <entry>Q׵ۭ󲾴 port D &intel; [cxĳD</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.ports.name;</entry>
-	      <entry>Discussion of the Ports Collection</entry>
+	      <entry> Ports Collection BΡBQ</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.ports-bugs.name;</entry>
-	      <entry>Discussion of the ports bugs/PRs</entry>
+	      <entry>ports  bugs/PRs</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.ppc.name;</entry>
-	      <entry>Porting FreeBSD to the &powerpc;</entry>
+	      <entry> FreeBSD  &powerpc; tά[c</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.proliant.name;</entry>
-	      <entry>Technical discussion of FreeBSD on HP ProLiant server platforms</entry>
+	      <entry>FreeBSD b HP ProLiant DxϥΥy</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.python.name;</entry>
-	      <entry>FreeBSD-specific Python issues</entry>
+	      <entry>Python b FreeBSD WϥΪUĳDC</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.qa.name;</entry>
-	      <entry>Discussion of Quality Assurance, usually pending a release</entry>
+	      <entry>QA(Quality Assurance)QסAq`|MwO_wgFiH release {</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.rc.name;</entry>
-	      <entry>Discussion related to the <filename>rc.d</filename> system and its development</entry>
+	      <entry><filename>rc.d</filename> QסBo</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.realtime.name;</entry>
-	      <entry>Development of realtime extensions to FreeBSD</entry>
+	      <entry>FreeBSD W realtime extensions o</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.scsi.name;</entry>
-	      <entry>The SCSI subsystem</entry>
+	      <entry>SCSI 譱ĳD</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.security.name;</entry>
-	      <entry>Security issues affecting FreeBSD</entry>
+	      <entry>FreeBSD w|}ĳD</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.small.name;</entry>
-	      <entry>Using FreeBSD in embedded applications</entry>
+	      <entry>bOJwҪΡBQ</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.smp.name;</entry>
-	      <entry>Design discussions for [A]Symmetric
-		MultiProcessing</entry>
+	      <entry>CPU ٦huBz(SMP, [A]Symmetric Multiprocessing)ΡBQ</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.sparc.name;</entry>
-	      <entry>Porting FreeBSD to &sparc; based systems</entry>
+	      <entry> FreeBSD  &sparc; x[c</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.standards.name;</entry>
-	      <entry>FreeBSD's conformance to the C99 and the &posix;
-		standards</entry>
+	      <entry>FreeBSD P C99  &posixзǪۮeĳD</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.threads.name;</entry>
-	      <entry>Threading in FreeBSD</entry>
+	      <entry>FreeBSD W Threading BΡBQ</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.testing.name;</entry>
-	      <entry>FreeBSD Performance and Stability Tests</entry>
+	      <entry>FreeBSD įPíwʴ</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.tokenring.name;</entry>
-	      <entry>Support Token Ring in FreeBSD</entry>
+	      <entry>FreeBSD  Token Ring 䴩ΡBQ</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.usb.name;</entry>
-	      <entry>Discussing &os; support for USB</entry>
+	      <entry>&os;  USB 䴩ΡBQ</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.vuxml.name;</entry>
-	      <entry>Discussion on VuXML infrastructure</entry>
+	      <entry>VuXML |}q[cQ</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.x11.name;</entry>
-	      <entry>Maintenance and support of X11 on FreeBSD</entry>
+	      <entry>X11 b FreeBSD B</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
 
-      <para><emphasis>Limited lists:</emphasis> The following lists are for
-	more specialized (and demanding) audiences and are probably not of
-        interest to the general public.  It is also a good idea to establish a
-        presence in the technical lists before joining one of these limited
-        lists so that you will understand the communications etiquette involved.</para>
+      <para><emphasis>q\׾¡G</emphasis> HU lists Ow@ǯSwnDŪ̦ӳ]A
+        ӥBäAXO@몺}QװϡC
+        z̦nbYǧ޳NQװϰѻP@qɶQ׫AAܭq\oǦ׾¡C
+        ]p@ӡAziHFѨboǰQװϵoҶ§C</para>
 
       <informaltable frame="none" pgwide="1">
 	<tgroup cols="2">
 	  <thead>
 	    <row>
-	      <entry>List</entry>
-	      <entry>Purpose</entry>
+	      <entry>List W</entry>
+	      <entry>ت</entry>
 	    </row>
 	  </thead>
 
 	  <tbody>
 	    <row>
 	      <entry>&a.hubs.name;</entry>
-	      <entry>People running mirror sites (infrastructural
-		support)</entry>
+	      <entry>Mgx(mirror)yQװ</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.usergroups.name;</entry>
-	      <entry>User group coordination</entry>
+	      <entry>s</entry>
 	    </row>
 
 	    <row>
@@ -541,29 +510,26 @@
 
 	    <row>
 	      <entry>&a.www.name;</entry>
-	      <entry>Maintainers of <ulink url="&url.base;/index.html">www.FreeBSD.org</ulink></entry>
+	      <entry><ulink url="&url.base;/index.html">www.FreeBSD.org</ulink> ޲z@</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
       </informaltable>
 
-      <para><emphasis>Digest lists:</emphasis> All of the above lists
-	are available in a digest format.  Once subscribed to a list,
-	you can change your digest options in your account options
-	section.</para>
-
-      <para><emphasis>CVS lists:</emphasis> The following lists are for people
-	interested in seeing the log messages for changes to various areas of
-	the source tree.  They are <emphasis>Read-Only</emphasis> lists and
-	should not have mail sent to them.</para>
+      <para><emphasis>׾ªKnG</emphasis> WzU lists Kn(digest)A
+        bq\ list ANiHHۤvbnJAMӤHq\ﶵאּKnYiC</para>
+
+      <para><emphasis>CVS lists:</emphasis> HU lists OѵQnݦU tree (commit)A
+	Ъ`NGL̬O <emphasis>Ū(Read-Only)</emphasis> ʽ誺 list
+	AӥBHHoC</para>
 
       <informaltable frame="none" pgwide="1">
 	<tgroup cols="3">
 	  <thead>
 	    <row>
-	      <entry>List</entry>
-	      <entry>Source area</entry>
-	      <entry>Area Description (source for)</entry>
+	      <entry>List W</entry>
+	      <entry>Source ϰ</entry>
+	      <entry>² (source for)</entry>
 	    </row>
 	  </thead>
 
@@ -571,31 +537,31 @@
 	    <row>
 	      <entry>&a.cvsall.name;</entry>
 	      <entry><filename>/usr/(CVSROOT|doc|ports|projects|src)</filename></entry>
-	      <entry>All changes to any place in the tree (superset of other CVS commit lists)</entry>
+	      <entry>ܧO(]AU CVS commit)</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.cvs-doc.name;</entry>
 	      <entry><filename>/usr/(doc|www)</filename></entry>
-	      <entry>All changes to the doc and www trees</entry>
+	      <entry>doc  www trees Ҧܧ</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.cvs-ports.name;</entry>
 	      <entry><filename>/usr/ports</filename></entry>
-	      <entry>All changes to the ports tree</entry>
+	      <entry>ports tree Ҧܧ</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.cvs-projects.name;</entry>
 	      <entry><filename>/usr/projects</filename></entry>
-	      <entry>All changes to the projects tree</entry>
+	      <entry>projects tree Ҧܧ</entry>
 	    </row>
 
 	    <row>
 	      <entry>&a.cvs-src.name;</entry>
 	      <entry><filename>/usr/src</filename></entry>
-	      <entry>All changes to the src tree</entry>
+	      <entry>src tree Ҧܧ</entry>
 	    </row>
 	  </tbody>
 	</tgroup>
@@ -603,13 +569,11 @@
     </sect2>
 
     <sect2 id="eresources-subscribe">
-      <title>How to Subscribe</title>
+      <title>npq\</title>
 
-      <para>To subscribe to a list, click on the list name above or
-        go to &a.mailman.lists.link;
-        and click on the list that you are interested in.  The list
-        page should contain all of the necessary subscription
-        instructions.</para>
+      <para>nq\ list ܡAХHƹUWz list W١A
+        άO &a.mailman.lists.link; MYiD靈쪺 list ӭq\FA
+        Ӻ|ܧApiq\BJC</para>
 
       <para>To actually post to a given list you simply send mail to
 	<email><replaceable>listname</replaceable>@FreeBSD.org</email>.  It will then
diff -ruN zh_TW.Big5.orig/books/handbook/install/chapter.sgml zh_TW.Big5/books/handbook/install/chapter.sgml
--- zh_TW.Big5.orig/books/handbook/install/chapter.sgml	Sat Jul  8 11:01:14 2006
+++ zh_TW.Big5/books/handbook/install/chapter.sgml	Sun Jul  9 03:22:43 2006
@@ -2,7 +2,7 @@
      The FreeBSD Documentation Project
 
      $FreeBSD: doc/zh_TW.Big5/books/handbook/install/chapter.sgml,v 1.5 2006/07/08 03:01:14 vanilla Exp $
-     Original revision: 1.331
+     Original revision: 1.333
 -->
 
 <chapter id="install">
@@ -739,11 +739,8 @@
 	MNiHϥΤVAάO <keycap>PageUp</keycap>B<keycap>PageDown</keycap>
 	ӤWU½\CA@ <keycap>Scroll Lock</keycap> AN|eʡC</para>
 
-      <para>Do this now, to review the text that scrolled off the screen when
-	the kernel was carrying out the device probes.  You will see text
-	similar to <xref linkend="install-dev-probe">, although the precise
-	text will differ depending on the devices that you have in your
-	computer.</para>
+      <para>{bNиոլݡA½\@Uw骺eaA
+	Aӷ|ݨ <xref linkend="install-dev-probe"> eAue|̧Aq]ƦӦҤPC</para>
 
       <figure id="install-dev-probe">
 	<title>w骺Ҥl</title>
@@ -811,16 +808,12 @@
 /stand/sysinstall running as init on vty0</screen>
       </figure>
 
-      <para>Check the probe results carefully to make sure that FreeBSD found
-	all the devices you expected.  If a device was not found, then it will
-	not be listed.  If the device's driver required configuring
-	with the IRQ and port address then you should check that you entered
-	them correctly.</para>
-
-      <para>If you need to make changes to the UserConfig device probing,
-	it is easy to exit the <application>sysinstall</application> program
-	and start over again.  It is also a good way to become more familiar
-	with the process.</para>
+      <para>ХJˬdC˴GAHTw FreeBSD TCwC
+	YSw骺ܡAeN|CXӤFCpGӵwݭn IRQ  
+	port address ܡAˬdO_]wTC</para>
+
+      <para>YQA@ǵw骺]wAhX <application>sysinstall</application> {AAYӹLYiC
+	o覡]UAxoǬy{C</para>
 
       <figure id="sysinstall-exit">
 	<title>} Sysinstall {</title>
@@ -832,9 +825,7 @@
 	</mediaobject>
       </figure>
 
-      <para>Use the arrow keys to select 
-	<guimenuitem>Exit Install</guimenuitem> from the Main
-	Install Screen menu.  The following message will display:</para>
+      <para>bDe <guimenuitem>Exit Install</guimenuitem>AUӷ|X{HUTG</para>
 
 
       <screen>                      User Confirmation Requested 
@@ -843,12 +834,9 @@
 
                             [ Yes ]    No</screen>
 
-      <para>The install program will start again if the CDROM is left
-	in the drive and &gui.yes; is selected.</para>
+      <para>YU &gui.yes; AoѤFаhXӪܡA򵥤U}S|AҰʦw˵{FC</para>
 
-      <para>If you are booting from floppies it will be necessary to remove
-	the <filename>mfsroot.flp</filename> floppy and replace it with
-	<filename>kern.flp</filename> before rebooting.</para>
+      <para>YAOκϤ}ܡA򭫶}eAаOohX}aC</para>
     </sect2>
   </sect1>
 
diff -ruN zh_TW.Big5.orig/books/handbook/introduction/chapter.sgml zh_TW.Big5/books/handbook/introduction/chapter.sgml
--- zh_TW.Big5.orig/books/handbook/introduction/chapter.sgml	Sat Jul  8 11:01:14 2006
+++ zh_TW.Big5/books/handbook/introduction/chapter.sgml	Sun Jul  9 03:22:30 2006
@@ -696,7 +696,7 @@
       </variablelist>
     
       <para>²檺Aڭ̪}oҦNO@ըSP߶C
-        oض}oҦOH <emphasis>ϥΪ̤K</emphasis>A
+        oض}oҦOH <emphasis>ϥΪ̤K</emphasis> DA
         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>
--- zh_TW.Big5.200607008.svn721.diff ends here ---


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: vanilla 
State-Changed-When: Sun Jul 9 03:19:27 UTC 2006 
State-Changed-Why:  
Committed, thanks. 

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