From chinsan.tw@gmail.com Sat Jul 8 19:34:25 2006 Return-Path: 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 Reply-To: chinsan 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 @@ + +%articles.ent; +]> + + + +
+ + 如何在 FreeBSD-questions mailing list 上得到正解 + + + Greg + Lehey + + +
grog@FreeBSD.org
+ + + + $FreeBSD$ + + + &tm-attrib.freebsd; + &tm-attrib.microsoft; + &tm-attrib.netscape; + &tm-attrib.opengroup; + &tm-attrib.qualcomm; + &tm-attrib.general; + + + + 本文主要是給準備寫信到 FreeBSD-questions mailing list 的人提供一些參考。 + 我們會給你一些發問的技巧與建議，以便讓你的答案得到更有用的答覆。 + + 本文會定期發到 FreeBSD-questions mailing list 上。 + + + + + 簡介 + + FreeBSD-questions is a mailing list maintained by + the FreeBSD project to help people who have questions about the normal + use of FreeBSD. Another group, FreeBSD-hackers, + discusses more advanced questions such as future development + work. + + + The term hacker has nothing to do with breaking + into other people's computers. The correct term for the latter + activity is cracker, 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 How To Become + A Hacker + + + This is a regular posting aimed to help both those seeking advice + from FreeBSD-questions (the newcomers), and also those + who answer the questions (the hackers). + + 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. + + 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. + + + + How to subscribe to FreeBSD-questions + + FreeBSD-questions is a mailing list, so you need mail access. Point + your WWW browser to the information page of the FreeBSD-questions mailing list. + In the section titled Subscribing to freebsd-questions fill + in the Your email address field; the other fields are optional. + + + + The password fields in the subscription form provide only mild + security, but should prevent others from messing with your + subscription. Do not use a valuable password as + it will occasionally be emailed back to you in cleartext. + + + You will receive a confirmation message from + mailman; follow the included instructions + to complete your subscription. + + Finally, when you get the Welcome message from + mailman telling you the details of the list + and subscription area password, please save it. + If you ever should want to leave the list, you will need the information + there. See the next section for more details. + + + + How to unsubscribe from FreeBSD-questions + + When you subscribed to FreeBSD-questions, you got a welcome message + from mailman. In this message, amongst + other things, it told you how to unsubscribe. Here is a typical + message: + + 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. + + From the URL specified in your Welcome message you + may visit the Account management page and enter a request + to Unsubscribe you from FreeBSD-questions mailing + list. + + A confirmation message will be sent to you from + mailman; follow the included instructions + to finish unsubscribing. + + If you have done this, and you still can not figure out what + is going on, send a message to + freebsd-questions-request@FreeBSD.org, and they will + sort things out for you. Do not send a message to + FreeBSD-questions: they can not help you. + + + + Should I ask <literal>-questions</literal> or + <literal>-hackers</literal>? + + Two mailing lists handle general questions about FreeBSD, + FreeBSD-questions and + FreeBSD-hackers. In some cases, it is not really + clear which group you should ask. The following criteria should help + for 99% of all questions, however: + + + + If the question is of a general nature, ask + FreeBSD-questions. Examples might be questions + about installing FreeBSD or the use of a particular &unix; + utility. + + + + 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 + FreeBSD-questions. + + + + If the question relates to a bug, and you are + sure 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 + FreeBSD-hackers. + + + + If the question relates to enhancements to FreeBSD, and you + can make suggestions about how to implement them, then send the + message to FreeBSD-hackers. + + + + There are also a number of other specialized mailing lists, for + example FreeBSD-isp, 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 FreeBSD-isp. 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. + + + + Before submitting a question + + You can (and should) do some things yourself before asking a question + on one of the mailing lists: + + + + 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. + + + + + Read the manual pages, and the FreeBSD documentation (either + installed in /usr/doc or accessible via WWW at + ), especially the + handbook + and the FAQ. + + + + + 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 + and + respectively. This can be done at other WWW sites as well, for example + at . + + + + + Use a search engine such as Google + or Yahoo to find answers to your question. + Google even has a BSD-specific search interface. + + + + + + + How to submit a question + + When submitting a question to FreeBSD-questions, consider the + following points: + + + + 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. + + + + 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. FreeBSD + problem or Help 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. + + + + 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. + + 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. + + A lot of badly formatted messages come from + bad mailers or badly + configured mailers. The following mailers are known to + send out badly formatted messages without you finding out about + them: + + + + cc:Mail + + + + &eudora; + + + + exmh + + + + µsoft; Exchange + + + + µsoft; Internet Mail + + + + µsoft; &outlook; + + + + &netscape; + + + + 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 MIME: a lot of people + use mailers which do not get on very well with + MIME. + + + + 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. + + + + 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. + + + + 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: + + + + 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. + + + With any problem which could 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? + + 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. + + + + If you get error messages, do not say I get error + messages, say (for example) I get the error + message 'No route to host'. + + + + If your system panics, do not say My system + panicked, say (for example) my system panicked + with the message 'free vnode isn't'. + + + + 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. + + + + 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? + + + + + + 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 /var/log/messages. 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, + + &prompt.user; dmesg > /tmp/dmesg.out + + This redirects the information to the file + /tmp/dmesg.out. + + + + 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. + + + + 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: + + + Message 1 + + 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. + + + + Message 2 + + 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 +Missing Operating System. + + + + + How to follow up to a question + + 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: + + + + You include the original message text, so people will know what + you are talking about. Do not forget to trim unnecessary text out, + though. + + + + 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. + + + + The message reference numbers in the header will refer to the + previous message. Some mailers, such as + mutt, can + thread messages, showing the exact + relationships between the messages. + + + + + + How to answer a question + + + Before you answer a question to FreeBSD-questions, consider: + + + + A lot of the points on submitting questions also apply to + answering questions. Read them. + + + + 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. + + 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. + + + + Do you have something to contribute beyond what has already been + said? In general, Yeah, me too 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 me too answer, you should + also include any further relevant information. + + + + 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. + + + + 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, 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?. + + + + Unless there is a good reason to do otherwise, reply to the + sender and to FreeBSD-questions. Many people on the + FreeBSD-questions are lurkers: 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. + + + + 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. + + + + Use some technique to identify which text came from the original + message, and which text you add. I personally find that prepending + > to the original message + works best. Leaving white space after the + > and leave empty lines + between your text and the original text both make the result more + readable. + + + + 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. + + + + Most mailers change the subject line on a reply by prepending a + text such as Re: . If your mailer does not do it + automatically, you should do it manually. + + + + If the submitter did not abide by format conventions (lines too + long, inappropriate subject line), please fix + it. In the case of an incorrect subject line (such as + HELP!!??), change the subject line to (say) + Re: Difficulties with sync PPP (was: HELP!!??). That + way other people trying to follow the thread will have less + difficulty following it. + + 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. + + 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. + + + +
+ + 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 @@ 郵遞論壇(Mailing Lists) - 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 - comp.unix.bsd.freebsd.* 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. - - The charters for the various lists are given at the bottom of this - document. Please read the charter before joining or sending - mail to any list. 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. - - When in doubt about what list to post a question to, see How to get best results from - the FreeBSD-questions mailing list. - - 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 - Mailing List Frequently Asked Questions (FAQ) document. - - Archives are kept for all of the mailing lists and can be searched - using the FreeBSD World - Wide Web server. The keyword searchable archive offers an - excellent way of finding answers to frequently asked questions and - should be consulted before posting a question. + 雖然，大部份的 FreeBSD 開發人員都有看 USENET 新聞群組， + 我們也不能保證我們永遠可以及時得知您的問題。 + 尤其是，若您只在 + comp.unix.bsd.freebsd.* 其中群組內發問的話。 + 建議您將問題發到適當的郵遞論壇(mailing list)上，不但可以同時讓 FreeBSD + 開發者和其他看倌們知道，通常也可以得到一個較好的(最起碼會比較快)的回應。 + + 本文後面介紹的是各式不同的郵遞論壇、討論規則(charter)。 + 在訂閱任何 list 之前，請先閱讀討論規則。 + 訂閱這些 list 的人們現在每天都會收到數百封 FreeBSD 相關信件。 + 而討論規則的制訂，則有助於提升彼此討論品質。 + 否則，這些討論 FreeBSD 的 list 終將陷入溝通不良，而失去其原本美意。 + + 對於該在哪個 list 發問覺得很疑惑的時候，就來看看 《如何在 FreeBSD-questions mailing list 上得到正解》 + 一文吧 + + 在發表問題、回覆到 list 之前，請先讀過 + + FreeBSD Mailing Lists 常見問答集(FAQ) 一文以學會如何善用 mailing list + ，才能避免像是經常重複的月經文、戰文之類的事情發生。 + + 全部的 mailing lists 討論記錄都可以在 + FreeBSD WWW主機 上找到。它提供了很棒的關鍵字搜尋功能，可讓您找到常用問答集(FAQ) + 。而在 mailing lists 上發問之前，也請先搜尋是否已有解答。 - List Summary + List 一覽表 - General lists: The following are general - lists which anyone is free (and encouraged) to join: + 一般論壇： 以下的 list 都是一般性質，而且大家可以自由地參與， + 我們也鼓勵大家訂閱： - List - Purpose + List 名稱 + 目的 &a.cvsall.name; - Changes made to the FreeBSD source tree + 所有的 FreeBSD 提交(commit)記錄 &a.advocacy.name; - FreeBSD Evangelism + FreeBSD 惡魔福音電台 &a.announce.name; - Important events and project milestones + 公布重要事件、計劃里程碑 &a.arch.name; - Architecture and design discussions + 架構研發討論 &a.bugbusters.name; - Discussions pertaining to the maintenance of the FreeBSD - problem report database and related tools + FreeBSD 問題回報(PR)資料庫的維護議題與工具 &a.bugs.name; - Bug reports + Bug 回報 &a.chat.name; - Non-technical items related to the FreeBSD - community + 非技術交流的 FreeBSD 社群聊天區 &a.current.name; - Discussion concerning the use of - &os.current; + 討論 &os.current; 版本的 FreeBSD &a.isp.name; - Issues for Internet Service Providers using - FreeBSD + FreeBSD 的 ISP 業者技術交流區 &a.jobs.name; - FreeBSD employment and consulting - opportunities + FreeBSD 人力銀行 &a.policy.name; - FreeBSD Core team policy decisions. Low volume, and - read-only + FreeBSD Core team 的 policy 方針討論區。這裡文章不多，且只限 core team 才可發言。 &a.questions.name; - User questions and technical support + 使用問題及技術支援 &a.security-notifications.name; - Security notifications + 安全漏洞通知 &a.stable.name; - Discussion concerning the use of - &os.stable; + 討論 &os.stable; 版本的 FreeBSD &a.test.name; - Where to send your test messages instead of one of - the actual lists + 論壇新手發表區，這裡可以讓你小試身手 - Technical lists: 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. + 技術論壇： 以下 list 主是要以探討技術問題為主， + 在加入訂閱及討論之前，請務必仔細閱讀每個 list 的版規(charter)， + 因為它們的討論內容都有很嚴謹的限制。 - List - Purpose + List 名稱 + 目的 &a.acpi.name; - ACPI and power management development + ACPI 以及電力管理議題 &a.afs.name; - Porting AFS to FreeBSD + 移植 AFS 到 FreeBSD &a.aic7xxx.name; - Developing drivers for the &adaptec; AIC 7xxx + 研發 &adaptec; AIC 7xxx 的驅動程式 &a.alpha.name; - Porting FreeBSD to the Alpha + 移植 FreeBSD 到 Alpha 系統架構 &a.amd64.name; - Porting FreeBSD to AMD64 systems + 移植 FreeBSD 到 AMD64 系統架構 &a.apache.name; - Discussion about Apache related ports + 探討 Apache 相關的 ports 議題 &a.arm.name; - Porting FreeBSD to &arm; processors + 移植 FreeBSD 到 &arm; CPU 架構 &a.atm.name; - Using ATM networking with FreeBSD + 在 FreeBSD 上使用 ATM 網路 &a.audit.name; - Source code audit project + Source code 的稽核(audit)計劃 &a.binup.name; - Design and development of the binary update system + 研發 binary 的升級方式 &a.bluetooth.name; - Using &bluetooth; technology in FreeBSD + 在 FreeBSD 中使用藍芽(&bluetooth;)技術 &a.cluster.name; - Using FreeBSD in a clustered environment + 把 FreeBSD 在叢集架構環境(clustered environment)的運用 &a.cvsweb.name; - CVSweb maintenance + CVSweb 的維護 &a.database.name; - Discussing database use and development under - FreeBSD + 討論各式資料庫在 FreeBSD 的研發、運用 &a.doc.name; - Creating FreeBSD related documents + 撰寫 FreeBSD 相關文件 &a.drivers.name; - Writing device drivers for &os; + 撰寫 &os; 用的驅動程式 &a.eclipse.name; - FreeBSD users of Eclipse IDE, tools, rich client - applications and ports. + FreeBSD 的 Eclipse IDE 工具愛用者交流 &a.emulation.name; - Emulation of other systems such as - Linux/&ms-dos;/&windows; + 在 FreeBSD 上模擬其他系統，如：Linux、&ms-dos;、&windows; &a.firewire.name; - FreeBSD &firewire; (iLink, IEEE 1394) technical - discussion + FreeBSD 的 &firewire; (iLink, IEEE 1394) 方面技術交流 &a.fs.name; - File systems + 檔案系統的探討、研發 &a.geom.name; - GEOM-specific discussions and implementations + GEOM 議題的探討、研發 &a.gnome.name; - Porting GNOME and GNOME applications + 移植 GNOME 及 GNOME 相關應用軟體 &a.hackers.name; - General technical discussion + 一般技術議題的探討 &a.hardware.name; - General discussion of hardware for running - FreeBSD + FreeBSD 上的各式硬體問題交流 &a.i18n.name; - FreeBSD Internationalization + FreeBSD 的多語化(Internationalization) &a.ia32.name; - FreeBSD on the IA-32 (&intel; x86) platform + FreeBSD 在 IA-32 (&intel; x86) 平台上的使用探討 &a.ia64.name; - Porting FreeBSD to &intel;'s upcoming IA64 systems + 移植 FreeBSD 到 &intel; 的未來 IA64 平台架構 &a.ipfw.name; - Technical discussion concerning the redesign of the IP - firewall code + 對 ipfw(IP firewall) 的技術探討 &a.isdn.name; - ISDN developers + ISDN 研發 &a.java.name; - &java; developers and people porting &jdk;s to - FreeBSD + &java; 程式開發者以及移植 &jdk;s 到 FreeBSD 上 &a.kde.name; - Porting KDE and KDE applications + 移植 KDE 以及 KDE 相關應用程式 &a.lfs.name; - Porting LFS to FreeBSD + 移植 LFS 到 FreeBSD &a.libh.name; - The second generation installation and package - system + 新世代的安裝、打包套件機制 &a.mips.name; - Porting FreeBSD to &mips; + 移植 FreeBSD 到 &mips; &a.mobile.name; - Discussions about mobile computing + 關於各類 mobile computing(比如：筆記型電腦)的研討 &a.mozilla.name; - Porting Mozilla to FreeBSD + 把 Mozilla 軟體移植到 FreeBSD &a.multimedia.name; - Multimedia applications + 各式影音運用、軟體 &a.newbus.name; - Technical discussions about bus architecture + 各式 bus 架構的技術探討 &a.net.name; - Networking discussion and TCP/IP source code + 網路運用探討與 TCP/IP source code &a.openoffice.name; - Porting OpenOffice.org and - &staroffice; to FreeBSD + 移植 OpenOffice.org 及 + &staroffice; 到 FreeBSD &a.performance.name; - Performance tuning questions for high - performance/load installations + 在高效能/負荷環境下的效能調校(tuning)議題 &a.perl.name; - Maintenance of a number of - Perl-related ports + 探討 Perl 相關 ports 的維護 &a.pf.name; - Discussion and questions about the packet filter - firewall system + pf(packet filter) 防火牆機制的探討 &a.platforms.name; - Concerning ports to non &intel; architecture - platforms + 討論著重於移植 port 到非 &intel; 架構平台的議題 &a.ports.name; - Discussion of the Ports Collection + 關於 Ports Collection 的運用、探討 &a.ports-bugs.name; - Discussion of the ports bugs/PRs + ports 相關的 bugs/PRs &a.ppc.name; - Porting FreeBSD to the &powerpc; + 移植 FreeBSD 到 &powerpc; 系統架構 &a.proliant.name; - Technical discussion of FreeBSD on HP ProLiant server platforms + FreeBSD 在 HP ProLiant 主機平台的使用交流 &a.python.name; - FreeBSD-specific Python issues + Python 在 FreeBSD 上使用的各式議題。 &a.qa.name; - Discussion of Quality Assurance, usually pending a release + QA(Quality Assurance)討論，通常會決定是否已經到達可以 release 的程度 &a.rc.name; - Discussion related to the rc.d system and its development + rc.d 機制的討論、研發 &a.realtime.name; - Development of realtime extensions to FreeBSD + FreeBSD 上 realtime extensions 的研發 &a.scsi.name; - The SCSI subsystem + SCSI 方面議題 &a.security.name; - Security issues affecting FreeBSD + FreeBSD 安全漏洞議題 &a.small.name; - Using FreeBSD in embedded applications + 在嵌入式硬體環境的應用、探討 &a.smp.name; - Design discussions for [A]Symmetric - MultiProcessing + CPU 對稱多工處理(SMP, [A]Symmetric Multiprocessing)的應用、研討 &a.sparc.name; - Porting FreeBSD to &sparc; based systems + 移植 FreeBSD 到 &sparc; 平台架構 &a.standards.name; - FreeBSD's conformance to the C99 and the &posix; - standards + FreeBSD 與 C99 及 &posix標準的相容議題 &a.threads.name; - Threading in FreeBSD + FreeBSD 上的 Threading 運用、探討 &a.testing.name; - FreeBSD Performance and Stability Tests + FreeBSD 的效能與穩定性測試 &a.tokenring.name; - Support Token Ring in FreeBSD + FreeBSD 的 Token Ring 支援的應用、探討 &a.usb.name; - Discussing &os; support for USB + &os; 的 USB 支援的應用、探討 &a.vuxml.name; - Discussion on VuXML infrastructure + VuXML 漏洞通報架構的探討 &a.x11.name; - Maintenance and support of X11 on FreeBSD + X11 在 FreeBSD 的運用 - Limited lists: 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. + 有訂閱限制的論壇： 以下的 lists 是針對一些特定要求的讀者而設， + 而且並不適合當成是一般的公開討論區。 + 您最好先在某些技術討論區參與一段時間的討論後，再選擇訂閱這些有限制的論壇。 + 因為如此一來，您可以了解到在這些討論區發言所須的禮儀。 - List - Purpose + List 名稱 + 目的 &a.hubs.name; - People running mirror sites (infrastructural - support) + 映射站台(mirror)的交流討論區 &a.usergroups.name; - User group coordination + 社群間的協調 @@ -541,29 +510,26 @@ &a.www.name; - Maintainers of www.FreeBSD.org + www.FreeBSD.org 的管理維護 - Digest lists: 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. - - CVS lists: The following lists are for people - interested in seeing the log messages for changes to various areas of - the source tree. They are Read-Only lists and - should not have mail sent to them. + 論壇的摘要版： 上述的各 lists 都有摘要版(digest)， + 在訂閱 list 之後，就可以先以自己帳號登入，然後個人訂閱選項那邊改為摘要版即可。 + + CVS lists: 以下的 lists 是提供給想要看各個 tree 的提交(commit)紀錄， + 請注意：他們是 唯讀(Read-Only) 性質的 list + ，而且不能寄信給這。 - List - Source area - Area Description (source for) + List 名稱 + Source 區域 + 本區簡介 (source for) @@ -571,31 +537,31 @@ &a.cvsall.name; /usr/(CVSROOT|doc|ports|projects|src) - All changes to any place in the tree (superset of other CVS commit lists) + 全部的變更記錄(包括各類 CVS commit) &a.cvs-doc.name; /usr/(doc|www) - All changes to the doc and www trees + doc 及 www trees 的所有變更紀錄 &a.cvs-ports.name; /usr/ports - All changes to the ports tree + ports tree 的所有變更紀錄 &a.cvs-projects.name; /usr/projects - All changes to the projects tree + projects tree 的所有變更紀錄 &a.cvs-src.name; /usr/src - All changes to the src tree + src tree 的所有變更紀錄 @@ -603,13 +569,11 @@ - How to Subscribe + 要如何訂閱 - 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. + 要訂閱 list 的話，請以滑鼠按下上述 list 名稱， + 或是到 &a.mailman.lists.link; 然後即可挑選有興趣的 list 來訂閱了， + 該網頁會指示你如何進行訂閱的步驟。 To actually post to a given list you simply send mail to listname@FreeBSD.org. 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 --> @@ -739,11 +739,8 @@ 然後就可以使用方向鍵，或是 PageUp、PageDown 鍵來上下翻閱。再按一次 Scroll Lock 鍵，就會停止畫面捲動。 - 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 , although the precise - text will differ depending on the devices that you have in your - computer. + 現在就請試試看，翻閱一下偵測硬體的畫面吧， + 你應該會看到類似 的畫面，真正畫面會依你的電腦設備而有所不同。
偵測硬體的例子 @@ -811,16 +808,12 @@ /stand/sysinstall running as init on vty0
- 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. - - If you need to make changes to the UserConfig device probing, - it is easy to exit the sysinstall program - and start over again. It is also a good way to become more familiar - with the process. + 請仔細檢查每項檢測結果，以確定 FreeBSD 有正確偵測到每項硬體。 + 若沒偵測到硬體的話，那畫面就不會列出來了。如果該硬體需要調 IRQ 及 + port address 的話，那麼請檢查是否設定正確。 + + 若想再改一些硬體的設定，那麼先退出 sysinstall 程式，再重頭來過即可。 + 這方式也有助你更熟悉這些流程。
離開 Sysinstall 程式 @@ -832,9 +825,7 @@
- Use the arrow keys to select - Exit Install from the Main - Install Screen menu. The following message will display: + 在主畫面選擇 Exit Install，接下來應該會出現以下訊息： User Confirmation Requested @@ -843,12 +834,9 @@ [ Yes ] No - The install program will start again if the CDROM is left - in the drive and &gui.yes; is selected. + 若按下 &gui.yes; 之後，卻忘了把光碟退出來的話，那麼等下重開機後又會再次啟動安裝程式了。 - If you are booting from floppies it will be necessary to remove - the mfsroot.flp floppy and replace it with - kern.flp before rebooting. + 若你是用磁片開機的話，那麼重開機之前，請記得退出開機片吧。 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 @@ 簡單的說，我們的開發模式就像是一組沒有拘束的同心圓。 - 這種集中開發模式是以 給使用者方便， + 這種集中開發模式是以 給使用者方便 為主， 同時讓他們能很容易地共同維護軟體，而不會把潛在的貢獻者排除在外！ 我們的目標是提供含有大量一致性的 應用軟體(ports/packages) ，以便讓使用者輕鬆安裝、使用的作業系統 —— 而這開發模式相當符合此一目標。 --- 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: