閱讀文章 - 看板 FB_doc - 批踢踢實業坊

發信人chinsan.tw@gmail.com (chinsan),

看板FB_doc

標題docs/89456: [UPDATE] zh_TW.Big5: update FAQ(Chapter 1 - Chapter 4)

發信站NCTU CSIE FreeBSD Server (Thu Nov 24 04:44:08 2005)

轉信站ptt!FreeBSD.csie.NCTU!not-for-mail

>Number: 89456 >Category: docs >Synopsis: [UPDATE] zh_TW.Big5: update FAQ(Chapter 1 - Chapter 4) >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Nov 23 12:00:37 GMT 2005 >Closed-Date: >Last-Modified: >Originator: chinsan >Release: FreeBSD 4.11-RELEASE-p13 i386 >Organization: FreeBSD Taiwan >Environment: System: FreeBSD smtp2.bc.hgc.com.tw 4.11-RELEASE-p13 FreeBSD 4.11-RELEASE-p13 #2: Wed Oct 12 12:57:38 CST 2005 root@smtp2.bc.hgc.com.tw:/usr/obj/usr/src/sys/BCSMTP i386 >Description: update FAQ(Chapter 1 - Chapter 4) Thanks very much! :) >How-To-Repeat: >Fix: --- zh_TW4.diff begins here --- diff -ruN zh_TW.Big5.orig/books/faq/book.sgml zh_TW.Big5/books/faq/book.sgml --- zh_TW.Big5.orig/books/faq/book.sgml Tue Nov 22 09:25:02 2005 +++ zh_TW.Big5/books/faq/book.sgml Wed Nov 23 19:50:48 2005 @@ -14,12 +14,15 @@ <!ENTITY % mailing-lists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN"> %mailing-lists; +<!ENTITY % books.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Books Entity Set//EN"> +%books.ent; + <!ENTITY bibliography SYSTEM "../../../share/sgml/bibliography.sgml"> ]> <book> <bookinfo> - <title>FreeBSD 2.X，3.X 及 4.X 常見問答集</title> + <title>FreeBSD 4.X，5.X 及 6.X 常見問答集</title> <corpauthor>FreeBSD 文件計畫</corpauthor> @@ -34,23 +37,50 @@ <year>2000</year> <year>2001</year> <year>2002</year> + <year>2003</year> + <year>2004</year> + <year>2005</year> <holder>FreeBSD 文件計畫</holder> </copyright> &bookinfo.legalnotice; + <legalnotice id="trademarks" role="trademarks"> + &tm-attrib.freebsd; + &tm-attrib.3com; + &tm-attrib.adobe; + &tm-attrib.creative; + &tm-attrib.cvsup; + &tm-attrib.ibm; + &tm-attrib.ieee; + &tm-attrib.intel; + &tm-attrib.iomega; + &tm-attrib.linux; + &tm-attrib.microsoft; + &tm-attrib.mips; + &tm-attrib.netscape; + &tm-attrib.opengroup; + &tm-attrib.oracle; + &tm-attrib.sgi; + &tm-attrib.sparc; + &tm-attrib.sun; + &tm-attrib.usrobotics; + &tm-attrib.xfree86; + &tm-attrib.general; + </legalnotice> + <abstract> - <para>這份文件是 FreeBSD 2.X，3.X 及 4.X 的常見問答集。 - 除非有特別加註，否則這些項目目都適用於 FreeBSD 2.0.5 及以後的版本。 - 如果條目內容中有 <XXX> 則是尚未完成的部份。如果您對協助本計畫 + <para>這份文件是 FreeBSD 4.X，5.X 及 6.X 的常見問答集。 + 除非有特別加註，否則這些項目目都適用於 FreeBSD 4.0 及以後的版本。 + (如果條目內容中有 <XXX> 則是尚未完成中譯的部份。) 如果您對協助本計畫的進行有興趣的話，請寄一封電子郵件到FreeBSD 文件計畫的 mailing list - &a.doc;。您可以從 <ulink URL="../../../../index.html"> + &a.doc;。您可以從 <ulink URL="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/index.html"> FreeBSD World Wide Web</ulink> 拿到這份文件的最新版本。 - 您也可以利用 HTTP 來下載一份龐大的 <ulink URL="book.html">HTML</ulink> + 也可以利用 HTTP 來下載一份龐大的 <ulink URL="book.html">HTML</ulink> 文件，或是經由 <ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/"> FreeBSD FTP 站</ulink> 下載純文字，postscript，或 PDF 版本的檔案。您也可以在這裡使用 - <ulink URL="http://www.FreeBSD.org/search/search.html">搜尋資料</ulink> + <ulink URL="&url.base;/search/search.html">搜尋資料</ulink> 的功能。</para> </abstract> </bookinfo> @@ -68,7 +98,7 @@ <title>前言</title> - <para>歡迎來到 FreeBSD 2.X-4.X FAQ!</para> + <para>歡迎使用 FreeBSD 4.X-6.X FAQ!</para> <para>跟其他 Usenet 上的 FAQ 一樣，這份文件涵蓋了有關 FreeBSD 這套作業系統最常被問到的問題 (當然包括了回答！)。雖然說我們本來的目的是為了 @@ -76,7 +106,7 @@ 為是一種值得閱讀的文件資源。</para> <para>我們已經儘可能地使這份 FAQ 更豐富了。如果您對如何使其更進步有任 - 何建議，請隨時寄電子郵件給 &a.faq;。</para> + 何建議，請隨時寄電子郵件給 &a.doc;。</para> <qandaset> <qandaentry> @@ -85,24 +115,22 @@ </question> <answer> - <para>簡單地來說，FreeBSD 是一套可以在 i386 和 Alpha/AXP 上執行的 + <para>簡單地來說，FreeBSD 是一套可以在 Alpha/AXP, AMD64 及 + &intel; EM64T, &i386; IA-64, PC-98, &ultrasparc; 上執行的 UN*X-like 作業系統，它是根據 U.C. Berkeley 所開發出來的 <quote>4.4BSD-Lite</quote>，並加上了許多 <quote>4.4BSD-Lite2</quote> 的增強功能。它同時也間接使用了 U.C. Berkeley 所開發出來並由 William Jolitz 移植到 i386 的 <quote>Net/2</quote>，也就是 <quote>386BSD</quote>，不過現在 386BSD 的程式碼只剩下極少數還留存在 FreeBSD 中。您可以在 - <ulink URL="../../../../index.html">FreeBSD 首頁</ulink>找到有關 + <ulink URL="&url.base;/index.html">FreeBSD 首頁</ulink>找到有關什麼是 FreeBSD 以及它可以幫您做些什麼的相關資訊。</para> <para>FreeBSD 已被廣泛地被世界各地的公司行號，ISP，研究人員，電腦 - 專家，學生，以及家庭用戶所使用，用在工作，教育，以及娛樂上。您可 - 以在 - <ulink URL="../../../../gallery/index.html">FreeBSD Gallery</ulink> - 看到一些有關他們的資料。</para> + 專家，學生，以及家庭用戶所使用，用在工作，教育，以及娛樂上。</para> <para>如果想看關於 FreeBSD 更深入的資料，請看 - <ulink URL="../handbook/index.html">FreeBSD 使用手冊</ulink>。</para> + <ulink URL="&url.books.handbook;/index.html">FreeBSD 使用手冊</ulink>。</para> </answer> </qandaentry> @@ -175,15 +203,14 @@ 的話，你就不能輕易地把它換掉，或者指望在 FreeBSD 上有很相似的應用程式才有機會。如果你想要的是一個強健的辦公室或是網路伺服器，或是一部穩定的工作站，或是想在不被中斷的環境下工作的話，FreeBSD 無疑 - 是您的最佳選擇。世界各地有很多使用者，包括初學或資深的 UNIX 管理 + 是您的最佳選擇。世界各地有很多使用者，包括初學或資深的 &unix; 管理人員都選用 FreeBSD 當他們唯一的桌上作業系統。</para> - <para>如果你是從其他的 UNIX 環境轉換到 FreeBSD 的話，基本上是大同小 - 異的。但是如果你之前用的是圖形界面的作業系統例如說是 Windows 或是 - 比較古老的 Mac OS 的話，可能就要多花一點時間來學習怎麼用 UNIX 的 + <para>如果你是從其他的 &unix; 環境轉換到 FreeBSD 的話，基本上是大同小 + 異的。但是如果你之前用的是圖形界面的作業系統，例如說是 &windows; 或是 + 比較古老的 &macos; 的話，可能就要多花一點時間來學習怎麼用 &unix; 的方法來做事。你可以從這份 FAQ 和 <ulink - url="../handbook/index.html">FreeBSD 使用手冊</ulink> 來入 - 門。</para> + url="&url.books.handbook;/index.html">FreeBSD 使用手冊</ulink> 來入門。</para> </answer> </qandaentry> @@ -218,16 +245,49 @@ </qandaentry> <qandaentry> + <question id="differences-to-other-bsds"> + <para>FreeBSD 及 NetBSD, OpenBSD 以及其他 + open source BSD 作業系統之間有何不同之處呢？</para> + </question> + + <answer> + <para>James Howard 在 <ulink url="http://www.daemonnews.org/">DaemonNews</ulink> + 上寫了 <ulink url="http://ezine.daemonnews.org/200104/bsd_family.html"> + The BSD Family Tree</ulink> 的文件，裡面說明了這些歷史淵源及這些 *BSD + 家族計畫之間的差異。</para> + </answer> + </qandaentry> + + <qandaentry> <question id="latest-version"> <para>最新版的 FreeBSD 是那一版？</para> </question> - <answer> - <para><ulink - URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE">&rel.current;</ulink> - 是目前最新的 <emphasis>RELEASE</emphasis> 版；它於 - &rel.current.date; 發行。它同時也是目前最新的 - <emphasis>STABLE</emphasis> 版。</para> + + + <answer> + <para>就 FreeBSD 目前的發展而言，有四個主要發展分支(其中三個已有 RELEASE)： + 由 <emphasis>4-STABLE</emphasis> 所發行(release)的 4.X 系列、 + 由 <emphasis>5-STABLE</emphasis> 所發行(release)的 5.X 系列、 + 由 <emphasis>6-STABLE</emphasis> 所發行(release)的 6.X 系列， + 以及 <emphasis>7-CURRENT</emphasis> 分支。</para> + + <para>在 5.3 release 之前，4.X 系列仍被視為是 <emphasis>-STABLE</emphasis> 之一。 + 自從 5.3 開始，5.X 開始規劃新的 <emphasis>-STABLE</emphasis> 發展重點， + 而 4.X 將只著重在重大問題上(比如：漏洞修補、安全維護)以及 "extended support" + ，不再會有新的突破性發展。</para> + + + <para>於 &rel.current.date; 所發行的<ulink + url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE">&rel.current;</ulink> + 版是目前最新的 <emphasis>6-STABLE</emphasis> 版； + 而於 &rel2.current.date; 所發行的<ulink + url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel2.current;-RELEASE/">&rel2.current;</ulink> + 版則是目前最新的 <emphasis> &rel.current.date;</emphasis> 版。</para> <para>簡單的說，<emphasis>-STABLE</emphasis> 的主要訴求對象是對於穩定性及低變異性的需求遠勝過對最新 <emphasis>-CURRENT</emphasis> @@ -237,11 +297,14 @@ 容易更動這一點，才應該用 <emphasis>-CURRENT</emphasis>。</para> <para>Release 版<link linkend="release-freq">每幾個月</link>才會發 - 行一次。雖然如此，有很多人和 FreeBSD 原程碼同步更新（詳見 + 行一次。雖然如此，有很多人和 FreeBSD 原始碼同步更新（詳見 <link linkend="current">FreeBSD-CURRENT</link> 和 <link linkend="stable">FreeBSD-STABLE</link> 的相關問題)，但因為原始碼是一直不斷地在變動的，所以如果要這麼做的話得要花上更多的精力。</para> + + <para>其他更多相關 FreeBSD 發行情報，可由 FreeBSD 網站上的 <ulink + url="http://www.FreeBSD.org/releng/index.html"> Release Engineering</ulink> 得知</para> </answer> </qandaentry> @@ -252,12 +315,12 @@ <answer> <para><ulink - URL="../handbook/cutting-edge.html#CURRENT">FreeBSD-CURRENT</ulink> + url="&url.books.handbook;/cutting-edge.html#CURRENT">FreeBSD-CURRENT</ulink> 指的是正在發展中的作業系統版本，它終將在適當的時機成為 - 5.0-RELEASE。它實在是只適合給系統發展者以及有毅力的業餘愛好者使用 + &os.stable; 分支。它實在是只適合給系統發展者以及有毅力的業餘愛好者使用。如果想要得到有關如何使用 -CURRENT 的深入資訊，請參考 <ulink - URL="../handbook/index.html">使用手冊</ulink> 的 <ulink - URL="../handbook/cutting-edge.html#CURRENT">相關部份</ulink>。 + url="&url.books.handbook;/index.html">使用手冊</ulink> 的 <ulink + url="&url.books.handbook;/cutting-edge.html#CURRENT">相關部份</ulink>。 </para> <para>如果您對作業系統本身並不是很熟悉，或是您沒辦法分辨您遇到的問 @@ -270,7 +333,7 @@ 誤</quote>之類的問題的話，也許會被其他人輕視。</para> <para>我們每天都會根據目前 -CURRENT 和 -STABLE 的狀況對這兩個分支各 - 發行一個<ulink URL="../../../../releases/snapshots.html">snapshot + 發行一個<ulink URL="&url.base;/releases/snapshots.html">snapshot </ulink> 版。有的時候甚至還會發行可供取得的版本。發表這些 snapshot 的目的在於：</para> @@ -295,17 +358,14 @@ </listitem> </itemizedlist> - <para>我們不對 -CURRENT snapshot 做任合形式的<quote>品質保 + <para>我們不對 -CURRENT snapshot 做任何形式的<quote>品質保證</quote>。如果你想要的是一個穩定且經過充分測試過的系統的話，最好選擇使用完整 release 的版本，或是使用 -STABLE snapshots。</para> <para>您可以直接從 <ulink - URL="ftp://current.FreeBSD.org/pub/FreeBSD/"> - ftp://current.FreeBSD.org/pub/FreeBSD/</ulink> 取得 5.0-CURRENT 的 - snapshot release，而從 <ulink - URL="ftp://releng4.FreeBSD.org/pub/FreeBSD">releng4.FreeBSD.org - </ulink> 取得 4-STABLE 的 snapshots。在本文寫作的時候 - (2000 年 5 月) 就已經不再提供 3-STABLE 的 snapshots 了。</para> + URL="ftp://current.FreeBSD.org/pub/FreeBSD/snapshots/"> + ftp://current.FreeBSD.org/pub/FreeBSD/snapshots/</ulink> 取得 -CURRENT 的 + snapshot release</para> <para>對每個有在活動的分支而言，平均每天都會產生一次 snapshots。 </para> @@ -319,12 +379,17 @@ <answer> <para>回溯到 FreeBSD 2.0.5 剛發表的時候，我們決定把 FreeBSD 的發展 - 分成兩支。一支叫做 <ulink URL="../handbook/stable.html">-STABLE - </ulink>，我們只對它做錯誤修正及小幅度的修改 (這是給 ISP 和商業 - 公司等對實驗中功能不感興趣的單位所使用的)。另外一支叫做 <ulink - URL="../handbook/cutting-edge.html#CURRENT">-CURRENT</ulink>，從 - 2.0 版發行以後就不間斷地朝著 5.0-RELEASE (以及以後的版本) 前進 - 著。下面就是版本演進的示意圖：</para> + 分成兩支。一支叫做 <ulink url="&url.books.handbook;/current-stable.html#STABLE">-STABLE</ulink> + ，我們只對它做錯誤修正及小幅度的修改 (這是給 ISP 和商業公司等，對實驗中功能不感興趣的單位所使用的)。 + 另外一支叫做 <ulink url="&url.books.handbook;/current-stable.html#CURRENT">-CURRENT</ulink>，從 + 2.0 版發行以後，就不斷地朝著 6.0-RELEASE (含後續的版本)前進著。</para> + + <para>6-STABLE 分支是從 6.0-RELEASE 開始(5-STABLE 分支算是 5.3-RELEASE 之後才開始的)， + 然後原本的 &os.current; 就會成為 7-CURRENT。 + </para> + + + <para>下面就是版本演進的示意圖：</para> <programlisting> 2.0 | @@ -349,43 +414,56 @@ | (May 1999) (Sep 1999) (Dec 1999) (June 2000) (July 2000) | | [4.0-STABLE] - *BRANCH* 4.0 (Mar 2000) -> 4.1 -> 4.1.1 -> 4.2 -> 4.3 -> 4.4 -> ... future 4.x releases ... + *BRANCH* 4.0 (Mar 2000) -> 4.1 -> 4.1.1 -> 4.2 -> 4.3 -> 4.4 -> ... -> 4.11 + | + | (July 2000) (Sep 2000) (Nov 2000) (Jan 2005) + | + | [5.0-STABLE] + *BRANCH* 5.0 (2001) -> 5.1 -> 5.2 -> 5.3 -> 5.4 -> ... future 5.x releases... + | + | ( 2001) (Nov 2004) (May 2005) + | + | [6.0-STABLE] + *BRANCH* 6.0 (Nov 2005) ... future 6.x releases... | - | (July 2000) (Sep 2000) (Nov 2000) \|/ + - [5.0-CURRENT continues]</programlisting> + [7.0-CURRENT continues]</programlisting> <para>2.2-STABLE 這個分支隨著 2.2.8 的發表而功成身退。3-STABLE 這個分支則是結束在 3.5.1 發表之後，它也是 3.X 的最後一次發表。之後除了 - 安全相關的修正之外，這兩個分支就幾乎沒有再更動過。</para> + 安全相關的修正之外，這兩個分支就幾乎沒有再更動過。4-STABLE 分支的支援 + 會持續到 2007/01/31，但主要焦點在於安全方面的漏洞、臭蟲及其他嚴重問題的修補。</para> - <para>4-STABLE 是目前正在發展中的 -STABLE 分支。4-STABLE 的最新的一 - 次發表是 &rel.current.date; 發行的 &rel.current;-RELEASE。</para> + <para>5-STABLE 是目前正在發展中的 -STABLE 分支。5-STABLE 的最新的一 + 次發表是在 &rel2.current.date; 發行的 &rel2.current;-RELEASE。</para> - <para>5-CURRENT 的這個分支目前正以緩慢的速度 5.0-RELEASE 以及之後的 - 版本邁進中。如果想要知道更多關於這個分支的資訊的話，請參考 <link - linkend="current">什麼是 FreeBSD-CURRENT？</link>。</para> + <para>6-STABLE 是目前正在發展中的 -STABLE 分支。6-STABLE 的最新的一 + 次發表是在 &rel.current.date; 發行的 &rel.current;-RELEASE。</para> + + <para>7-CURRENT 這個分支是 &os; 的 -CURRENT 分支，仍然不斷地在發展當中。 + 如果想要知道更多關於這個分支的資訊的話，請參考 <link + linkend="current">什麼是 &os;-CURRENT？</link>。</para> </answer> </qandaentry> <qandaentry> <question id="release-freq"> - <para>新的 FreeBSD 將於什麼時候推出？</para> + <para>每次新的 FreeBSD 將於什麼時候推出？</para> </question> <answer> - <para>一般而言，當 FreeBSD core team 認為已經累積了足夠多的新功能 - 和錯誤修正，而且這些更動都已經完整地測試過且不會影響系統穩定度的 - 時候，他們才會推出新版的 FreeBSD。新版本的發表時程都會事先公告， - 相關的開發人員就知道什麼時候該把手邊的計劃完成並且測試過。雖然等 - 這些好東西進入 -STABLE 的時間令人有點沮喪，但是大多數的使用者都 - 認為這種謹慎的態度是 FreeBSD 最好的優點之一。</para> + <para>一般而言，&a.re; 平均每四個月發行一次 release，每次新版本的發表時程都會事先公告， + 相關的開發人員就會知道，什麼時候該先把手邊的計劃完成並且測試過， + 此外，這些更動都已經完整地測試過，且不會影響系統穩定度。 + 雖然，等這些好東西進入 -STABLE 的時間令人等得有些不耐煩， + 但是大多數的使用者都認為這種謹慎的態度是 FreeBSD 最好的優點之一。</para> - <para>平均而言，我們每四個月發行一次 release。</para> + <para>有關發行情報的更多細節部分(包括 release 的行程表、進度)，都可在 FreeBSD 網站上的 + <ulink url="http://www.FreeBSD.org/releng/index.html">發行情報</ulink> 上面獲得。</para> - <para>為了滿足那些需要 (或想要) 刺激的使用者，上面已經說過我們每天 - 都會發行 snapshots 版可供使用。</para> + <para>為了滿足那些需要 (或想要) 新鮮刺激感的使用者， + 上面(-CURRENT的部分)已經提到我們每天都會發行 snapshots 版可供使用。</para> </answer> </qandaentry> @@ -397,15 +475,15 @@ <answer> <para>如果是一些有關 FreeBSD 計畫的關鍵性決定，像是整個計畫的走向或是決定誰可以改 source tree 裡的程式碼這類的事，是由一個由 9 個 - 人所組成的 <ulink - URL="../../articles/contributors/article.html#STAFF-CORE">core - team</ulink> 來決定。而有另一群超過 200 個人的 <ulink - URL="../../articles/contributors/article.html#STAFF-COMMITTERS"> + 人所組成的 <ulink + url="&url.articles.contributors;/article.html#STAFF-CORE">core + team</ulink> 來決定。而有另一群超過 300 個人的 <ulink + url="&url.articles.contributors;/article.html#STAFF-COMMITTERS"> commiters</ulink> 有權利可以直接修改 FreeBSD 的 source tree。 </para> <para>無論如何，大多數的改變都會事前在 <link linkend="mailing"> - mailing lists</link> 先討論過，而且每個人都可以參與討論。</para> + mailing lists</link> 先討論過，而且不分角色，每個人都可以參與討論。</para> </answer> </qandaentry> @@ -416,74 +494,86 @@ <answer> <para>每個 FreeBSD 的重要版本都可以經由匿名 ftp 從 <ulink - URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/">FreeBSD FTP site</ulink> - 取得：</para> + url="ftp://ftp.FreeBSD.org/pub/FreeBSD/">FreeBSD FTP 站</ulink>取得：</para> - <itemizedlist> - <listitem> - <para>如果要的是 3.X-STABLE 的最新版，也就是 3.5.1-RELEASE，請到 - <ulink - URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/3.5.1-RELEASE/">3.5.1-RELEASE</ulink> 這個目錄。</para> - </listitem> + <itemizedlist> + <listitem> + <para>如果需要 6-STABLE 的最新版，也就是 &rel.current;-RELEASE，請到 <ulink + url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/">&rel.current;-RELEASE </ulink>這個目錄</para> + </listitem> - <listitem> - <para>如果要的是 4-STABLE 的最新版，也就是 &rel.current;-RELEASE - ，請到 <ulink - URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/">&rel.current;-RELEASE </ulink>這個目錄</para> - </listitem> + <listitem> + <para><ulink url="ftp://current.FreeBSD.org/pub/FreeBSD/">7-CURRENT Snapshot</ulink> + 通常也是每天都會做一份，這是從 <link linkend="current">-CURRENT</link> 分支做出來的， + 主要是為了提供給那些熱心的測試者和開發人員。</para> + </listitem> - <listitem> - <para><ulink - URL="ftp://releng4.FreeBSD.org/pub/FreeBSD/">4.X - snapshots</ulink> 通常每天都會做一份。</para> - </listitem> + <listitem> + <para>如果需要 5-STABLE 的最新版，也就是 &rel2.current;-RELEASE，請到 <ulink + url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel2.current;-RELEASE/">&rel2.current;-RELEASE </ulink>這個目錄</para> + </listitem> - <listitem> - <para><ulink - URL="ftp://current.FreeBSD.org/pub/FreeBSD/"> - 5.0 Snapshot</ulink> 通常也是每天都會做一份，這是從 <link - linkend="current">-CURRENT</link> 分支做出來的，主要是為了服 - 務那些熱心的測試者和開發人員所提供的。</para> - </listitem> + <listitem> + <para>如果需要 4-STABLE 的最新版，也就是 4.11-RELEASE，請到 <ulink + url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/4.11-RELEASE/">4.11-RELEASE </ulink>這個目錄</para> + </listitem> + + <listitem> + <para><ulink + url="ftp://current.FreeBSD.org/pub/FreeBSD/snapshots/">4.X、5.X、6X snapshots</ulink> + 通常每天都會做一份。</para> + </listitem> </itemizedlist> - <para>FreeBSD 的 CD，DVD，還有一些其他的東西的取得法可以在 <ulink url="../handbook/mirrors.html">使用手冊</ulink>中找到解答。</para> + <para>FreeBSD 的 CD、DVD，還有其他取得方式可以在 <ulink url="&url.books.handbook;/mirrors.html">使用手冊</ulink> 中找到解答。</para> </answer> </qandaentry> <qandaentry> + <question id="howto-mirror"> + <para>怎麼建立 FreeBSD 的映射(mirror)站台？</para> + </question> + + <answer> + <para>有關如何建立 FreeBSD 映射站(mirror)的資料，可以參考 <ulink + url="&url.articles.hubs;/">Mirroring FreeBSD</ulink> 文章</para> + </answer> + </qandaentry> + + <qandaentry> <question id="access-pr"> - <para>我要如何去存取錯誤回報資料庫呢？</para> + <para>我要如何去查詢、提交問題回報(Problem Report)資料庫呢？</para> </question> <answer> - <para>所有使用者的變更要求都可以經由我們網頁介面的 PR <ulink - URL="http://www.FreeBSD.org/send-pr.html">submission</ulink> 及 + <para>所有使用者的變更要求都可以經由網頁介面的 PR <ulink URL="http://www.FreeBSD.org/cgi/query-pr-summary.cgi?query"> - query</ulink> 來查詢 (或是回報) 我們的錯誤回報資料庫。也可以利用 - &man.send-pr.1; 這個指令透過電子郵件來回報錯誤或是要求變更。</para> + 查詢介面</ulink> 來察看 (或是回報) 我們的錯誤回報資料庫。</para> + + <para>也可以使用 &man.send-pr.1; 這個指令透過電子郵件來回報問題、要求變更。 + 或者是經由 <ulink url="http://www.FreeBSD.org/send-pr.html">網頁介面的 PR</ulink> 來送出問題回報。</para> - <para>在回報錯誤之前，請先讀過 <ulink - URL="../../articles/problem-reports/article.html">如何撰寫 - FreeBSD 的錯誤回報單</ulink>，這是一篇告訴你怎樣才能寫出一篇有用的 - 錯誤回報單。</para> + <para>然而，在您回報問題之前，請先閱讀 <ulink + URL="&url.articles.problem-reports;/article.html">如何撰寫 + FreeBSD 的問題回報單</ulink>，這是一篇告訴你怎樣才能寫出一篇真正有用的 + 問題回報單。</para> </answer> </qandaentry> <qandaentry> <question id="become-web-mirror"> - <para>要怎樣才能成為 FreeBSD 的網頁映射站台？</para> + <para>要怎樣才能成為 FreeBSD 的網頁映射(mirror)站台？</para> </question> <answer> - <para>有很多方法可以映射我們的網頁。</para> + <para>有很多方法可以映射(mirror)我們的網頁。</para> <itemizedlist> <listitem> <para>您可以利用 <filename role="package">net/cvsup</filename> 從 cvsup.FreeBSD.org 取得格式化過的檔案。 - <filename>/usr/share/examples/cvsup/www-supfile</filename>就 - 是一個教你怎樣做網頁映射的 CVSup 設定範例。 + <filename>/usr/share/examples/cvsup/www-supfile</filename> + 這檔就是一個教你怎樣做網頁映射的 CVSup 設定範例。 </para> </listitem> @@ -491,7 +581,7 @@ <para>您可以利用您喜歡的 ftp mirror 工具從 FreeBSD 的 FTP 站臺中取得網頁的原始碼。但是要注意的是在你打算提供公開服務之前，記得要先利用這些原始碼把網頁重建起來。請從 <ulink - URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/www">ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/www</ulink> 開始抓取。</para> + url="ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/www"></ulink> 開始抓取。</para> </listitem> </itemizedlist> </answer> @@ -512,60 +602,66 @@ </chapter> <chapter id="support"> - <title>Documentation and Support</title> + <chapterinfo> + <author> + <firstname>Chin-San</firstname> + <surname>Huang</surname> + <affiliation> + <address><email>chinsan.tw@gmail.com</email></address> + </affiliation> + </author> + </chapterinfo> + + <title>文件與支援</title> <qandaset> <qandaentry> <question id="books"> - <para>What good books are there about FreeBSD?</para> + <para>關於 FreeBSD 有哪些好書可以推薦閱讀的嗎？</para> </question> <answer> - <para>The project produces a wide range of documentation, available - from this link: - <ulink url="http://www.freebsd.org/docs.html">http://www.FreeBSD.org/docs.html</ulink>. + <para>FreeBSD 文件計畫已陸續發表了相當廣泛範圍的文件，可在 <ulink + url="http://www.FreeBSD.org/docs.html"></ulink> 取得。另外， + FreeBSD 本身的 manual(一般通稱的man)、doc也如同套件軟體一樣，可以輕鬆地裝在您系統上。 + </para> - In addition, the Bibliography at the end of this FAQ, and the - one in the Handbook reference other recommended books.</para> + <para>此外，也建議參閱本份 FAQ 最後所列的參考書目表(Bibliography)與《 FreeBSD 使用手冊》。 + </para> </answer> </qandaentry> <qandaentry> <question id="doc-formats"> - <para>Is the documentation available in other formats, such as plain - text (ASCII), or Postscript?</para> + <para>這些文件有其他格式的嗎？像是：純文字(ASCII)或 &postscript; 之類的格式？</para> </question> <answer> - <para>Yes. The documentation is available in a number of - different formats and compression schemes on the FreeBSD - FTP site, in the <ulink - URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">/pub/FreeBSD/doc/</ulink> - directory.</para> + <para>有的。這些文件都分別以不同格式儲存以及壓縮處理，放在 + FTP 上面，可以從各 FreeBSD FTP 站的 <ulink + url="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">/pub/FreeBSD/doc/</ulink> + 目錄內找到你要的。</para> - <para>The documentation is categorized in a number of different - ways. These include:</para> + <para>文件的分類方面主要是一些不同性質所組成：</para> <itemizedlist> <listitem> - <para>The document's name, such as <literal>faq</literal>, or - <literal>handbook</literal>.</para> + <para>文件名稱，比如：<literal>faq(常見問答集)</literal>或是 + <literal>handbook(FreeBSD 使用手冊)</literal>等等。</para> </listitem> <listitem> - <para>The document's language and encoding. These are based on - the locale names you will find under - <filename>/usr/share/locale</filename> on your FreeBSD - system. The current languages and encodings that we have for - documentation are as follows:</para> + <para>各國翻譯的的文件：這主要是由 locale 名稱來決定的 + (不清楚的話，可參考您的 FreeBSD 作業系統上的 <filename>/usr/share/locale</filename>) + 目前文件總共有下列幾種語言(及編碼)有翻譯：</para> - <informaltable frame="none"> + <informaltable frame="none" pgwide="1"> <tgroup cols="2"> <thead> <row> - <entry>Name</entry> + <entry>Locale 名稱</entry> - <entry>Meaning</entry> + <entry>說明(所代表的語系、編碼)</entry> </row> </thead> @@ -573,72 +669,72 @@ <row> <entry><literal>en_US.ISO8859-1</literal></entry> - <entry>US English</entry> + <entry>美式英文(US English)</entry> </row> <row> <entry><literal>de_DE.ISO8859-1</literal></entry> - <entry>German</entry> + <entry>德文(German)</entry> </row> <row> <entry><literal>es_ES.ISO8859-1</literal></entry> - <entry>Spanish</entry> + <entry>西班牙文(Spanish)</entry> </row> <row> <entry><literal>fr_FR.ISO8859-1</literal></entry> - <entry>French</entry> + <entry>法文(French)</entry> </row> + <row> + <entry><literal>it_IT.ISO8859-15</literal></entry> + + <entry>義大利文(Italian)</entry> + </row> + <row> <entry><literal>ja_JP.eucJP</literal></entry> - <entry>Japanese (EUC encoding)</entry> + <entry>日文(Japanese，編碼方式：EUC)</entry> </row> <row> <entry><literal>ru_RU.KOI8-R</literal></entry> - <entry>Russian (KOI8-R encoding)</entry> + <entry>俄文(Russian，編碼方式：KOI8-R)</entry> </row> <row> <entry><literal>zh_TW.Big5</literal></entry> - <entry>Chinese (Big5 encoding)</entry> + <entry>正體中文(Chinese，編碼方式：Big5)</entry> </row> </tbody> </tgroup> </informaltable> <note> - <para>Some documents may not be available in all - languages.</para> + <para>上列的各國翻譯語系文件中，並非所有文件都有翻譯。</para> </note> </listitem> <listitem> - <para>The document's format. We produce the documentation in a - number of different output formats. Each format has its own - advantages and disadvantages. Some formats are better suited - for online reading, while others are meant to be aesthetically - pleasing when printed on paper. Having the documentation - available in any of these formats ensures that our readers - will be able to read the parts they are interested in, either - on their monitor, or on paper after printing the documents. - The currently available formats are:</para> + <para>文件的格式：每份文件都以各種不同格式儲存，每種格式都各有好壞， + 有些格式適合線上閱讀，而有些則適合列印出美觀的文件。 + 我們都提供這些不同格式的文件，來確保無論是螢幕上、列印紙本，每個人都可以正常地閱讀內容， + 目前可供使用的格式如下:</para> - <informaltable frame="none"> + <informaltable frame="none" pgwide="1"> <tgroup cols="2"> <thead> <row> - <entry>Format</entry> + <entry>格式</entry> - <entry>Meaning</entry> + <entry>說明</entry> </row> </thead> @@ -646,47 +742,45 @@ <row> <entry><literal>html-split</literal></entry> - <entry>A collection of small, linked, HTML - files.</entry> + <entry>章節模式</entry> </row> <row> <entry><literal>html</literal></entry> - <entry>One large HTML file containing the entire - document</entry> + <entry>完整模式</entry> </row> <row> <entry><literal>pdb</literal></entry> - <entry>Palm Pilot database format, for use with the - <ulink URL="http://www.iSilo.com/">iSilo</ulink> - reader.</entry> + <entry>Palm Pilot 資料格式，使用 + <ulink url="http://www.iSilo.com/">iSilo</ulink> + 程式來閱讀</entry> </row> <row> <entry><literal>pdf</literal></entry> - <entry>Adobe's Portable Document Format</entry> + <entry>Adobe's PDF 格式</entry> </row> <row> <entry><literal>ps</literal></entry> - <entry>Postscript</entry> + <entry>&postscript; 格式</entry> </row> <row> <entry><literal>rtf</literal></entry> - <entry>Microsoft's Rich Text Format<footnote> - <para>Page numbers are not automatically updated - when loading this format in to Word. Press - <keycombo action="simul"><keycap>CTRL</keycap><keycap>A</keycap></keycombo>, - <keycombo action="simul"><keycap>CTRL</keycap><keycap>END</keycap></keycombo>, - <keycap>F9</keycap> after loading the document, to - update the page numbers.</para> + <entry>Microsoft's RTF格式<footnote> + <para>當使用 MS Word 來開啟 RTF 格式的話，頁數顯示並不會自動更新。 + (在開啟文件後，要按 <keycombo + action="simul"><keycap>CTRL</keycap><keycap>A</keycap></keycombo>, + <keycombo + action="simul"><keycap>CTRL</keycap><keycap>END</keycap></keycombo>, + <keycap>F9</keycap>，這樣子才會更新頁數的顯示。)</para> </footnote> </entry> </row> @@ -694,7 +788,7 @@ <row> <entry><literal>txt</literal></entry> - <entry>Plain text</entry> + <entry>純文字(ASCII)</entry> </row> </tbody> </tgroup> @@ -702,33 +796,31 @@ </listitem> <listitem> - <para>The compression and packaging scheme. There are three of - these currently in use.</para> + <para>文件的壓縮、打包方式：目前有三種方式：</para> <orderedlist> <listitem> - <para>Where the format is <literal>html-split</literal>, the - files are bundled up using &man.tar.1;. The resulting - <filename>.tar</filename> file is then compressed using - the compression schemes detailed in the next point.</para> + <para>當採用 + <literal>章節模式(html-split)</literal>，章節模式所產生的各檔案會先使用 + &man.tar.1; 來壓縮。檔名結尾有 <filename>.tar</filename> 的檔案就是 tar 格式。 + 接著，會再以下列方式再壓縮。 + </para> </listitem> <listitem> - <para>All the other formats generate one file, called - <filename>book.<replaceable>format</replaceable></filename> - (i.e., <filename>book.pdb</filename>, - <filename>book.html</filename>, and so on).</para> - - <para>These files are then compressed using three - compression schemes.</para> + <para>其他格式的檔案都會是單一檔案，檔名通常會是： + <filename>book.<replaceable>格式</replaceable></filename> + (舉例： <filename>book.pdb</filename>， + <filename>book.html</filename> 等等..後面通常加上『.格式』).</para> + <para>而這些檔案會分別以兩種壓縮型態進行壓縮，而存成兩種壓縮型態。</para> - <informaltable frame="none"> + <informaltable frame="none" pgwide="1"> <tgroup cols="2"> <thead> <row> - <entry>Scheme</entry> + <entry>格式</entry> - <entry>Description</entry> + <entry>說明</entry> </row> </thead> @@ -736,166 +828,137 @@ <row> <entry><literal>zip</literal></entry> - <entry>The Zip format. If you want to uncompress - this on FreeBSD you will need to install the - <filename role="package">archivers/unzip</filename> port - first.</entry> - </row> - - <row> - <entry><literal>gz</literal></entry> - - <entry>The GNU Zip format. Use &man.gunzip.1; to - uncompress these files, which is part of - FreeBSD.</entry> + <entry>Zip 格式，若要在 FreeBSD 上解壓 zip 檔，則必須先安裝 + <filename role="package">chinese/unzip</filename> 或 + <filename role="package">archivers/unzip</filename>。 + </entry> </row> <row> <entry><literal>bz2</literal></entry> - <entry>The BZip2 format. Less widespread than the - others, but generally gives smaller files. - Install the <filename role="package">archivers/bzip2</filename> - port to uncompress these files.</entry> + <entry>BZip2 格式，雖然不如 zip 格式的廣泛使用，但是好處在於可壓縮成更小的檔案。 + 要解壓 bz2 格式的話，需先安裝 <filename role="package">archivers/bzip2 + </filename>。</entry> </row> </tbody> </tgroup> </informaltable> - <para>So the Postscript version of the Handbook, compressed - using BZip2 will be stored in a file called - <filename>book.ps.bz2</filename> in the - <filename>handbook/</filename> directory.</para> - </listitem> - - <listitem> - <para>The formatted documentation is also available as a - FreeBSD package, of which more later.</para> + <para>所以像是 Handbook 的 &postscript; 版格式，會以 BZip2 格式壓縮， + 存放在 <filename>handbook/</filename> 目錄內， + 檔名就是<filename>book.ps.bz2</filename>。</para> </listitem> </orderedlist> </listitem> </itemizedlist> - <para>After choosing the format and compression mechanism that you - want to download, you must then decide whether or not you want to - download the document as a FreeBSD - <emphasis>package</emphasis>.</para> - - <para>The advantage of downloading and installing the package is - that the documentation can then be managed using the normal - FreeBSD package management comments, such as &man.pkg.add.1; and - &man.pkg.delete.1;.</para> - - <para>If you decide to download and install the package then you - must know the filename to download. The documentation-as-packages - files are stored in a directory called - <filename>packages</filename>. Each package file looks like - <filename><replaceable>document-name</replaceable>.<replaceable>lang</replaceable>.<replaceable>encoding</replaceable>.<replaceable>format</replaceable>.tgz</filename>.</para> - - <para>For example, the FAQ, in English, formatted as PDF, is in the - package called - <filename>faq.en_US.ISO8859-1.pdf.tgz</filename>.</para> - - <para>Knowing this, you can use the following command to install the - English PDF FAQ package.</para> + <para>選擇想要下載的文件格式與壓縮型態之後，則要決定是否以 FreeBSD <emphasis>套件(package)</emphasis> + 型態來下載。</para> + + <para>下載、安裝『package』的好處在於：可以透過一般 FreeBSD + 套件管理方式來進行管理，比如 &man.pkg.add.1; 及 + &man.pkg.delete.1;。</para> - <screen>&prompt.root; <userinput>pkg_add ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/packages/faq.en_US.ISO8859-1.pdf.tgz</userinput></screen> - <para>Having done that, you can use &man.pkg.info.1; to determine - where the file has been installed.</para> + <para>若決定好要下載、安裝『package』的話，必須要確認所要下載的檔名。 + 文件計畫的套件(package)通常是放在是 <filename>packages</filename> 的目錄內， + 每個文件計畫的套件檔名通常是： + <filename><replaceable>文件名稱</replaceable>.<replaceable>語系</replaceable>.<replaceable>編碼</replaceable>.<replaceable>格式</replaceable>.tgz</filename> + 。</para> - <screen>&prompt.root; <userinput>pkg_info -f faq.en_US.ISO8859-1.pdf</userinput> -Information for faq.en_US.ISO8859-1.pdf: + <para>舉個例子，英文版的 FAQ (格式選擇 PDF)在 package 就叫做 + <filename>faq.en_US.ISO8859-1.pdf.tgz</filename>。</para> + + <para>再舉個例子，中文版的 FAQ (格式選擇 PDF)在 package 就叫做 + <filename>faq.zh_TW.Big5.pdf.tgz</filename>。</para> + + <para>知道這點之後，就可以用下面指令來安裝中文版 FAQ 套件：</para> + + <screen>&prompt.root; <userinput>pkg_add ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/packages/faq.zh_TW.Big5.pdf.tgz</userinput></screen> + + <para>完成之後，可以用 &man.pkg.info.1; 來找出檔案裝在哪邊：</para> + + <screen>&prompt.root; <userinput>pkg_info -f faq.zh_TW.Big5.pdf</userinput> +Information for faq.zh_TW.Big5.pdf: Packing list: - Package name: faq.en_US.ISO8859-1.pdf - CWD to /usr/share/doc/en_US.ISO8859-1/books/faq + Package name: faq.zh_TW.Big5.pdf + CWD to /usr/share/doc/zh_TW.Big5/books/faq File: book.pdf CWD to . File: +COMMENT (ignored) File: +DESC (ignored)</screen> - <para>As you can see, <filename>book.pdf</filename> will have been - installed in to - <filename>/usr/share/doc/en_US.ISO8859-1/books/faq</filename>. - </para> + <para>如同您所看到的 <filename>book.pdf</filename> 會被安裝到 + <filename>/usr/share/doc/zh_TW.Big5/books/faq</filename> 內。</para> - <para>If you do not want to use the packages then you will have to - download the compressed files yourself, uncompress them, and then - copy the appropriate documents in to place.</para> - - <para>For example, the split HTML version of the FAQ, compressed - using &man.gzip.1;, can be found in the - <filename>doc/en_US.ISO8859-1/books/faq/book.html-split.tar.gz</filename> - file. To download and uncompress that file you would have to do - this.</para> + <para>若不想用 package 方式安裝，那麼就需手動下載、解壓縮、複製到你想要擺放的位置去。</para> - <screen>&prompt.root; <userinput>fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/faq/book.html-split.tar.gz</userinput> -&prompt.root; <userinput>gzip -d book.html-split.tar.gz</userinput> + <para>舉例，章節模式(split HTML)版的英文 FAQ (壓縮為 &man.bzip2.1;)會放在 + <filename>doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2</filename> + 要下載、解壓的話，則要打：</para> + + <screen>&prompt.root; <userinput>fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2</userinput> +&prompt.root; <userinput>bzip2 -d book.html-split.tar.bz2</userinput> &prompt.root; <userinput>tar xvf book.html-split.tar</userinput></screen> - <para>You will be left with a collection of - <filename>.html</filename> files. The main one is called - <filename>index.html</filename>, which will contain the table of - contents, introductory material, and links to the other parts of - the document. You can then copy or move these to their final - location as necessary.</para> + <para>這時你會看到一堆 <filename>.html</filename> 的檔案， + 主要的目錄檔為 <filename>index.html</filename> + 內含主目錄及連結到其他文件。(若有需要的話，也可以複製或搬移這些檔案到同一目錄下)</para> </answer> </qandaentry> <qandaentry> <question id="mailing"> - <para>Where do I find info on the FreeBSD mailing lists?</para> + <para>哪裡有關於 FreeBSD 的郵遞論壇(mailing lists)呢？</para> </question> <answer> - <para>You can find full information in the <ulink - URL="../handbook/eresources.html#ERESOURCES-MAIL">Handbook - entry on mailing-lists</ulink>.</para> + <para>這個問題，可以從《 FreeBSD 使用手冊》上面的 <ulink + url="&url.books.handbook;/eresources.html#ERESOURCES-MAIL">郵遞論壇(mailing-lists)</ulink> + 部分獲得答案。</para> </answer> </qandaentry> <qandaentry> <question id="y2k"> - <para>Where do I find the FreeBSD Y2K info?</para> + <para>我該從哪邊得到有關 FreeBSD 在千禧蟲(Y2K)方面的資料呢?</para> </question> <answer> - <para>You can find full information in the <ulink - URL="../../../../y2kbug.html">FreeBSD Y2K - page</ulink>.</para> + <para>這答案可以在 <ulink + url="&url.base;/y2kbug.html">FreeBSD 千禧蟲(Y2K)</ulink>上面獲得</para> </answer> </qandaentry> <qandaentry> <question id="newsgroups"> - <para>What FreeBSD news groups are available?</para> + <para>有哪些可以使用的 FreeBSD 新聞群組(news groups)呢?</para> </question> <answer> - <para>You can find full information in the <ulink - URL="../handbook/eresources-news.html">Handbook entry on - newsgroups</ulink>.</para> + <para>這答案可以從《 FreeBSD 使用手冊》上面的 <ulink + url="&url.books.handbook;/eresources-news.html">新聞群組(newsgroups)</ulink> + 部分獲得答案。</para> </answer> </qandaentry> <qandaentry> <question id="irc"> - <para>Are there FreeBSD IRC (Internet Relay Chat) - channels?</para> + <para>有哪些 FreeBSD IRC (Internet Relay Chat)頻道呢？</para> </question> <answer> - <para>Yes, most major IRC networks host a FreeBSD chat - channel:</para> + <para>有的，大部分的 IRC 主機都有 FreeBSD 聊天頻道：</para> <itemizedlist> <listitem> <para>Channel <literal>#FreeBSD</literal> on - <ulink URL="http://www.efnet.org/index.php">EFNet</ulink> + <ulink url="http://www.efnet.org/index.php">EFNet</ulink> is a FreeBSD forum, but do not go there for tech support or try to get folks there to help you avoid - the pain of reading man pages or doing your own research. + the pain of reading manual pages or doing your own research. It is a chat channel, first and foremost, and topics there are just as likely to involve sex, sports or nuclear weapons as they are FreeBSD. You Have Been Warned! @@ -904,35 +967,37 @@ <listitem> <para>Channel <literal>#FreeBSDhelp</literal> on - <ulink URL="http://www.efnet.org/index.php">EFNet</ulink> + <ulink url="http://www.efnet.org/index.php">EFNet</ulink> is a channel dedicated to helping FreeBSD users. They - are much more sympathetic to questions then + are much more sympathetic to questions than <literal>#FreeBSD</literal> is.</para> </listitem> <listitem> <para>Channel <literal>#FreeBSD</literal> on - <ulink URL="http://www.dal.net/">DALNET</ulink> + <ulink url="http://www.dal.net/">DALNET</ulink> is available at <hostid>irc.dal.net</hostid> in the US and <hostid>irc.eu.dal.net</hostid> in Europe.</para> </listitem> <listitem> + <para>Channel <literal>#FreeBSDHelp</literal> on + <ulink url="http://www.dal.net/">DALNET</ulink> + is available at <hostid>irc.dal.net</hostid> in the + US and <hostid>irc.eu.dal.net</hostid> in Europe. + The channel owners also have a web page with useful + information about the channel and &os;, available at + <ulink url="http://www.freebsdhelp.net/"></ulink>.</para> + </listitem> + + <listitem> <para>Channel <literal>#FreeBSD</literal> on - <ulink URL="http://www.undernet.org/">UNDERNET</ulink> + <ulink url="http://www.undernet.org/">UNDERNET</ulink> is available at <hostid>us.undernet.org</hostid> in the US and <hostid>eu.undernet.org</hostid> in Europe. Since it is a help channel, be prepared to read the documents you are referred to.</para> </listitem> - - <listitem> - <para>Channel <literal>#FreeBSD</literal> on <ulink - url="http://www.hybnet.net/">HybNet</ulink>. This channel - <emphasis>is</emphasis> a help channel. A list of servers - can be found on the <ulink - url="http://www.hybnet.net/">HybNet web site</ulink>.</para> - </listitem> </itemizedlist> <para>Each of these channels are distinct and are not @@ -948,26 +1013,21 @@ <qandaentry> <question id="training"> - <para>Where can I get commercial FreeBSD training and support?</para> + <para>可以從哪邊獲得 FreeBSD 的商業課程訓練及技術支援呢？</para> </question> <answer> - <para>DaemonNews provides commercial training and support for - FreeBSD. More information can be found at their - <ulink url="http://www.bsdmall.com/">BSD Mall</ulink> - site.</para> - - <para>FreeBSD Services Ltd provide commercial support for FreeBSD - in the UK (as well as selling FreeBSD on DVD). See their - <ulink url="http://www.freebsd-services.com">web site</ulink> - for more information.</para> - - <para>The FreeBSD Mall provides commercial FreeBSD support. - You can get more information at their <ulink - url="http://www.freebsdmall.com/">web site</ulink>.</para> + <para>DaemonNews 有專門提供 FreeBSD 的商業課程訓練及技術支援。 + 詳情請到 <ulink url="http://www.bsdmall.com/">BSD Mall</ulink> + 察看，謝謝。</para> + + <para>FreeBSD Mall 有提供商業化的 BSD 技術支援， + 詳情請到 <ulink + url="http://www.freebsdmall.com/">FreeBSD Mall</ulink> 察看，謝謝。</para> + - <para>Any other organizations providing training and support should - contact the project in order to be listed here.</para> + <para>其他任何有提供課程訓練及技術支援的組織、單位，若也想列表於此的話， + 請與 &a.doc; 聯絡，謝謝。</para> </answer> </qandaentry> </qandaset> @@ -985,33 +1045,30 @@ </author> </chapterinfo> - <title>Installation</title> + <title>安裝</title> <qandaset> <qandaentry> <question id="floppy-download"> - <para>Which file do I download to get FreeBSD?</para> + <para>若要用軟碟片開機來安裝 FreeBSD 的話，要下載哪些檔案呢？</para> </question> <answer> - <para>Prior to release 3.1, you only needed one floppy image to - install FreeBSD, namely <filename>floppies/boot.flp</filename>. - However, since release 3.1 the Project has added out-of-the-box - support for a wide variety of hardware, which takes up more - space. For 3.x and later you need two floppy images: - <filename>floppies/kernel.flp</filename> and - <filename>floppies/mfsroot.flp</filename>. These images need to - be copied onto floppies by tools like - <command>fdimage</command> or &man.dd.1;.</para> - - <para>If you need to download the distributions yourself (for a - DOS filesystem install, for instance), below are some - recommendations for distributions to grab:</para> + <para>&os; 4.X 的話，需要兩個 image 檔： + <filename>floppies/kernel.flp</filename> 及 + <filename>floppies/mfsroot.flp</filename>。image 檔必須用工具像是 + <command>fdimage</command> 或 &man.dd.1; 來傳送到磁片上。 + 若是在 &os; 5.3 (及之後版本)有重新規劃開機片架構，所以要抓的是 + <filename>floppies/boot.flp</filename> 以及 <filename>floppies/kern<replaceable>X</replaceable></filename> + 檔案(目前 X 為 1 跟 2 兩個，加上<filename>floppies/boot.flp</filename>，總共是 3 個檔案)。</para> + + <para>若想自己下載 distributions 的話(比如以 &ms-dos; 檔案系統格式安裝)， + 以下是建議要抓的 distributions ：</para> <itemizedlist> <listitem> - <para>bin/</para> + <para>base/ (bin/ in 4.X)</para> </listitem> <listitem> @@ -1032,61 +1089,50 @@ </itemizedlist> - <para>Full instructions on this procedure and a little bit more - about installation issues in general can be found in the - <ulink URL="../handbook/install.html">Handbook entry on - installing FreeBSD</ulink>.</para> + <para>完整安裝步驟以及大部分的安裝問題，請參閱《 FreeBSD 使用手冊》的 + <ulink url="&url.books.handbook;/install.html">安裝 FreeBSD</ulink> 章節</para> </answer> </qandaentry> <qandaentry> <question id="floppy-image-too-large"> - <para>What do I do if the floppy images does not fit on a single - floppy?</para> + <para>若磁片裝不下 image 檔的話，該怎麼辦呢？</para> </question> <answer> - <para>A 3.5 inch (1.44MB) floppy can accommodate 1474560 bytes - of data. The boot image is exactly 1474560 bytes in size.</para> + <para>一張 3.5 英吋(1.44MB) 的磁碟片是可以裝上 1474560 bytes 的資料 + ，而開機片的 image 檔案大小實際上也是 1474560 bytes。</para> - <para>Common mistakes when preparing the boot floppy are:</para> + <para>在製作開機片時，常見錯誤有：</para> <itemizedlist> <listitem> - <para>Not downloading the floppy image in - <emphasis>binary</emphasis> mode when using - <acronym>FTP</acronym>.</para> - - - <para>Some FTP clients default their transfer mode to - <emphasis>ascii</emphasis> and attempt to change any - end-of-line characters received to match the conventions - used by the client's system. This will almost invariably - corrupt the boot image. Check the size of the downloaded - boot image: if it is not <emphasis>exactly</emphasis> that - on the server, then the download process is suspect.</para> - - <para>To workaround: type <emphasis>binary</emphasis> at the - FTP command prompt after getting connected to the server - and before starting the download of the image.</para> + <para>使用 <acronym>FTP</acronym> 來下載檔案時， + 未選擇 <emphasis>binary</emphasis> 傳輸模式來下載。</para> + + + <para>有些 FTP client端程式，是預設將傳輸模式設定為 + <emphasis>ascii</emphasis> 模式，而且會修改接收到的檔案行尾字串為 client 端的作業系統方式 + ，比如 newline(&unix;格式) 到了作業系統為 &windows; 的 client 端會被改為 CR-LF(&ms-dos;格式)， + 這會使得 image 檔本身遭到修改而無法正常使用。因此，如果下載的 image + 檔案大小若與 FTP 主機上面的檔案 <emphasis>不一致</emphasis> + 的話，請重新使用 binary 傳輸模式下載即可。</para> + + <para>FTP 指令: 進入 FTP 之後，打 <emphasis>binary</emphasis> + 指令，即可切換到 binary 傳輸模式，然後再下載相關 image 檔案。</para> </listitem> <listitem> - <para>Using the DOS <command>copy</command> command (or - equivalent GUI tool) to transfer the boot image to - floppy.</para> - - <para>Programs like <command>copy</command> will not work as - the boot image has been created to be booted into directly. - The image has the complete content of the floppy, track for - track, and is not meant to be placed on the floppy as a - regular file. You have to transfer it to the floppy - <quote>raw</quote>, using the low-level tools (e.g. - <command>fdimage</command> or <command>rawrite</command>) - described in the <ulink - URL="../handbook/install.html">installation guide to - FreeBSD</ulink>.</para> + <para>直接用 &ms-dos; 的 <command>copy</command> 指令(或類似 + 的 GUI 程式、或是視窗上直接複製)來複製開機用的 image 檔到磁片上。 + </para> + + <para>不可以用像是 <command>copy</command> 這類程式直接將 image + 檔複製到磁片上，因為 image 檔本身包含了完整的磁軌資料，所以不能單純用複製方式， + 而必須使用低階工具程式(像是 <command>fdimage</command> 或 <command>rawrite</command>)， + 以 <quote>raw</quote> 方式傳送到磁片上。(這部分可參閱《 FreeBSD 使用手冊》上的 <ulink + url="&url.books.handbook;/install.html">安裝 FreeBSD</ulink>)</para> </listitem> </itemizedlist> </answer> @@ -1094,162 +1140,139 @@ <qandaentry> <question id="install-instructions-location"> - <para>Where are the instructions for installing FreeBSD?</para> + <para>可以在哪邊找到安裝 FreeBSD 的解說步驟呢？</para> </question> <answer> - <para>Installation instructions can be found in the - <ulink URL="../handbook/install.html">Handbook entry on installing FreeBSD</ulink>.</para> + <para>安裝步驟的解說，請參閱《 FreeBSD 使用手冊》上的 + <ulink url="&url.books.handbook;/install.html">安裝 FreeBSD</ulink> 章節部分。</para> </answer> </qandaentry> <qandaentry> <question id="need-to-run"> - <para>What do I need in order to run FreeBSD?</para> + <para>要跑 FreeBSD 需要什麼的配備呢？</para> </question> <answer> - <para>You will need a 386 or better PC, with 5 MB or more of RAM - and at least 60 MB of hard disk space. It can run with a low - end MDA graphics card but to run X11R6, a VGA or better video - card is needed.</para> + <para>&os; 5.X 之前的版本，硬體需求為 386 或更高級的 PC + ，記憶體(RAM)至少要 5 MB 或更多，硬碟空間至少要 60 MB 或更多。 + 不過，&os; 『系統安裝程式』的記憶體(RAM)需求為至少 16 MB。</para> + + <para>從 &os; 5.X 起，硬體需求為 486 或更高級的 PC + ，記憶體(RAM)至少要 24 MB 或更多，硬碟空間至少要 150 MB 或更多。 + </para> - <para>See also - <xref linkend="hardware"></para> + <para>&os; 的所有版本都可以只用低階的 MDA 規格顯示卡，不過…要跑 X11R6 視窗的話， + 還是至少用 VGA 或更好規格的顯示卡來用吧。</para> + + <para>這部分也可參閱 <xref linkend="hardware">。</para> </answer> </qandaentry> <qandaentry> <question id="four-meg-ram-install"> - <para>I have only 4 MB of RAM. Can I install FreeBSD?</para> + <para>我電腦 RAM 只有 4MB 而已，可以裝 FreeBSD 嗎？</para> </question> <answer> - <para>FreeBSD 2.1.7 was the last version of FreeBSD that - could be installed on a 4MB system. FreeBSD 2.2 and later - needs at least 5MB to install on a new system.</para> - - <para>All versions of FreeBSD will <emphasis>run</emphasis> - in 4MB of RAM, they just cannot run the installation - program in 4MB. You can add extra memory for the install - process, if you like, and then after the system is up and - running, go back to 4MB. Or you could swap your disk into - a system which has >4MB, install onto the disk and then - swap it back.</para> - - <para>FreeBSD 2.1.7 will not install with 640 kB base + 3 MB - extended memory. If your motherboard can remap some of the - <quote>lost</quote> memory out of the 640kB to 1MB region, - then you may still be able to get FreeBSD 2.1.7 up. Try - to go into your BIOS setup and look for a - <quote>remap</quote> option. Enable it. You may also - have to disable ROM shadowing. It may be easier to get 4 - more MB just for the install. Build a custom kernel with - only the options you need and then remove the 4MB out. - You can also install 2.0.5 and then upgrade your system to - 2.1.7 with the <quote>upgrade</quote> option of the 2.1.7 - installation program.</para> - - <para>After the installation, if you build a custom kernel, - it will run in 4 MB. Someone has even successfully booted - with 2 MB, although the system was almost unusable.</para> + <para>安裝 &os; 4.X 的記憶體需求為至少 5 MB ，而 + 安裝 &os; 5.X (含之後版本) 則是至少要 8 MB 。</para> + + <para>在 5.X 之前的所有 &os; 版本，都可以只用 4 MB 的記憶體來 + <emphasis>『運作』</emphasis>，不過，前面那節我們說過了『系統安裝程式』的話， + 則無法只用 4 MB 的記憶體來執行。因此，你可以先在『系統安裝程式』這步驟之前， + 先將記憶體加到 16 MB 以上，安裝完 FreeBSD 之後，就可以把多餘的記憶體拿下來。 + 或者是，先把要安裝的硬碟拿到有足夠記憶體的機器上先裝好， + 然後再把硬碟放回原機器。</para> + + <para>此外，只用 4 MB 的記憶體來運作的話，必須要自製 kernel(拿掉不必要的以及犧牲一些東西)。 + 也有人的 &os 成功只用 2 MB 的記憶體來開機(雖然這樣的系統幾乎等於廢了..)</para> </answer> </qandaentry> <qandaentry> <question id="custom-boot-floppy"> - <para>How can I make my own custom install floppy?</para> + <para>要怎樣才能自行打造專用的開機、安裝磁片呢？</para> </question> <answer> - <para>Currently there is no way to <emphasis>just</emphasis> - make a custom install floppy. You have to cut a whole new - release, which will include your install floppy.</para> + <para>目前，還沒有辦法<emphasis>『只』</emphasis>自製專用的開機、安裝磁片。 + 必須透過自行打造完整作業系統的 release(發行)，這樣裡面才會包括自己的開機、安裝磁片。</para> - <para>To make a custom release, follow the instructions in the - <ulink url="../../articles/releng/article.html">Release - Engineering</ulink> article.</para> + <para>若想自行打造、發行(release)一個完整的作業系統，請參閱這篇 + <ulink url="&url.articles.releng;/article.html">Release Engineering</ulink> 文章。</para> </answer> </qandaentry> <qandaentry> <question id="multiboot"> - <para>Can I have more than one operating system on my PC?</para> + <para>我電腦上可以有多重作業系統嗎？</para> </question> <answer> - <para>Have a look at - <ulink URL="../../articles/multi-os/index.html"> - the multi-OS page</ulink>.</para> + <para>可以呀，請參閱 + <ulink url="&url.articles.multi-os;/index.html"> + 多重作業系統</ulink> 這篇文章。</para> </answer> </qandaentry> <qandaentry> <question id="windows-coexist"> - <para>Can Windows 95/98 co-exist with FreeBSD?</para> + <para>&windows; 可以與 FreeBSD 共存於電腦上嗎？</para> </question> <answer> - <para>Install Windows 95/98 first, after that FreeBSD. - FreeBSD's boot manager will then manage to boot Win95/98 and - FreeBSD. If you install Windows 95/98 second, it will boorishly - overwrite your boot manager without even asking. If that - happens, see the next section.</para> + <para>先裝 &windows; 再裝 FreeBSD。 + 那麼 FreeBSD 開機管理員(boot manager)就會出現選單讓你選擇要以 &windows; 或 + FreeBSD 來開機。不過，若你是先裝 FreeBSD 再裝 &windows; 的話， + 那麼 &windows; 將會不問先宰，把 FreeBSD 的開機管理員(boot manager)蓋掉， + 當你遇上這種情況時，請參考下一節說明。</para> </answer> </qandaentry> <qandaentry> <question id="win95-damaged-boot-manager"> - <para>Windows 95/98 killed my boot manager! - How do I get it back?</para> + <para>嗚～&windows; 把我的開機管理員(boot manager)拿掉了！我要怎麼救回來呢？</para> </question> <answer> - <para>You can reinstall the boot manager FreeBSD comes with in - one of three ways:</para> + <para>可以用以下三種方式之一，來救回你的 FreeBSD 開機管理員(boot manager)：</para> <itemizedlist> <listitem> - <para>Running DOS, go into the tools/ directory of your - FreeBSD distribution and look for - <filename>bootinst.exe</filename>. You run it like - so:</para> + <para>可以從各 FreeBSD FTP 站的 <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">/pub/FreeBSD/tools/</ulink> + 找到 <filename>bootinst.exe</filename> 及 <filename>boot.bin</filename> 這兩個檔， + 以 binary 傳輸模式下載後，複製到磁片上，再用 DOS 開機片開機， + 接著打類似下面的指令：</para> - <screen><prompt>...\TOOLS></prompt> <userinput>bootinst.exe boot.bin</userinput></screen> + <screen><prompt>></prompt> <userinput>bootinst.exe boot.bin</userinput></screen> - <para>and the boot manager will be reinstalled.</para> + <para>這樣開機管理員(boot manager)就會重裝完畢了。</para> </listitem> <listitem> - <para>Boot the FreeBSD boot floppy again and go to the - Custom installation menu item. Choose Partition. Select the - drive which used to contain your boot manager (likely the - first one) and when you come to the partition editor for - it, as the very first thing (e.g. do not make any changes) - select (W)rite. This will ask for confirmation, say yes, - and when you get the Boot Manager selection prompt, be - sure to select <quote>Boot Manager</quote>. This will - re-write the boot manager to disk. Now quit out of the - installation menu and reboot off the hard disk as - normal.</para> + <para>用 FreeBSD 開機片開機，然後選單那邊選 Custom installation(自訂安裝)， + 再選 Partition，接著選擇你要裝開機管理員(boot manager)的硬碟(通常是第一顆)， + 然後會出現 partition editor 的畫面，這時請不要做任何修改，直接按 W 儲存， + 這時程式就會問是否要確定 Write ，最後出現 Boot Manager 選擇畫面， + 記得要選 <quote>Boot Manager</quote> ，這樣就會重新將開機管理員(boot manager) + 安裝到硬碟上。現在，就大功告成可以離開安裝選單並重開機了。</para> </listitem> <listitem> - <para>Boot the FreeBSD boot floppy (or CDROM) and choose the - <quote>Fixit</quote> menu item. Select either the Fixit - floppy or CDROM #2 (the <quote>live</quote> file system - option) as appropriate and enter the fixit shell. Then - execute the following command:</para> + <para>用 FreeBSD 開機片或是開機光碟開機，然後選單那邊選 <quote>Fixit</quote> + ，或是以 Fixit 開機片或是光碟安裝的第二片(選擇 <quote>live</quote> filesystem + 選項)然後就會進入 fixit shell 了，接著打下列指令：</para> <screen><prompt>Fixit#</prompt> <userinput>fdisk -B -b /boot/boot0 <replaceable>bootdevice</replaceable></userinput></screen> - <para>substituting <replaceable>bootdevice</replaceable> for - your real - boot device such as <devicename>ad0</devicename> (first IDE - disk), <devicename>ad4</devicename> (first IDE disk on - auxiliary controller), <devicename>da0</devicename> (first - SCSI disk), etc.</para> + <para>請將上面的 <replaceable>bootdevice</replaceable> 修改為您實際的開機硬碟代號 + 比如 <devicename>ad0</devicename> (第一顆 IDE 硬碟) + ，或是<devicename>ad4</devicename> (first IDE disk on + auxiliary controller), <devicename>da0</devicename> (第一顆 + SCSI 硬碟)等等…。</para> </listitem> </itemizedlist> </answer> @@ -1257,59 +1280,55 @@ <qandaentry> <question id="boot-on-thinkpad"> - <para>My A, T, or X series IBM Thinkpad locks up when I first - booted up my FreeBSD installation. How can I solve this?</para> + <para>當裝完 FreeBSD 之後重開機，我的 IBM Thinkpad A系列、T系列或 X系列的筆記型電腦就趴了，該怎麼辦呢？</para> </question> <answer> - <para>A bug in early revisions of IBM's BIOS on these machines - mistakenly identifies the FreeBSD partition as a potential FAT - suspend-to-disk partition. When the BIOS tries to parse the - FreeBSD partition it hangs.</para> + <para>這些 IBM 機器上的 BIOS 早期版本有個臭蟲(bug)會把 FreeBSD 分割區誤認為 + FAT 格式分割區，然後當 BIOS 試著偵測 FreeBSD 分割區時，就會趴了。</para> - <para>According to IBM<footnote><para>In an e-mail from Keith - Frechette - <email>kfrechet@us.ibm.com</email>.</para></footnote>, the - following model/BIOS release numbers incorporate the fix.</para> + <para>根據 IBM 方面的說法<footnote><para>一封來自 Keith + Frechette 的 e-mail <email>kfrechet@us.ibm.com</email>。</para></footnote> + ，以下型號/BIOS版本的機種，已經都有修正：</para> - <informaltable frame="none"> + <informaltable frame="none" pgwide="1"> <tgroup cols="2"> <thead> <row> - <entry>Model</entry> - <entry>BIOS revision</entry> + <entry>型號</entry> + <entry>BIOS 版本</entry> </row> </thead> <tbody> <row> <entry>T20</entry> - <entry>IYET49WW or later</entry> + <entry>IYET49WW(含之後)</entry> </row> <row> <entry>T21</entry> - <entry>KZET22WW or later</entry> + <entry>KZET22WW(含之後)</entry> </row> <row> <entry>A20p</entry> - <entry>IVET62WW or later</entry> + <entry>IVET62WW(含之後)</entry> </row> <row> <entry>A20m</entry> - <entry>IWET54WW or later</entry> + <entry>IWET54WW(含之後)</entry> </row> <row> <entry>A21p</entry> - <entry>KYET27WW or later</entry> + <entry>KYET27WW(含之後)</entry> </row> <row> <entry>A21m</entry> - <entry>KXET24WW or later</entry> + <entry>KXET24WW(含之後)</entry> </row> <row> @@ -1320,14 +1339,15 @@ </tgroup> </informaltable> - <para>It has been reported that later IBM BIOS revisions may have - reintroduced the bug. <ulink - url="http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=200565+208320+/usr/local/www/db/text/2001/freebsd-mobile/20010429.freebsd-mobile">This message</ulink> - from Jacques Vidrine to the &a.mobile; describes a procedure - which may work if your newer IBM laptop does not boot FreeBSD - properly, and you can upgrade or downgrade the BIOS..</para> + <para>It has been reported that later IBM BIOS revisions may + have reintroduced the bug. <ulink + url="http://docs.FreeBSD.org/cgi/mid.cgi?20010427133759.A71732">This + message</ulink> from Jacques Vidrine to the &a.mobile; + describes a procedure which may work if your newer IBM + laptop does not boot FreeBSD properly, and you can upgrade + or downgrade the BIOS.</para> - <para>If you have an earlier BIOS, and upgrading is not an option a + <para>If you have an earlier BIOS, and upgrading is not an option, a workaround is to install FreeBSD, change the partition ID FreeBSD uses, and install new boot blocks that can handle the different partition ID.</para> @@ -1350,7 +1370,7 @@ <step> <para>Download <filename>boot1</filename> and <filename>boot2</filename> from <ulink - url="http://people.FreeBSD.org/~bmah/ThinkPad/">http://people.FreeBSD.org/~bmah/ThinkPad/</ulink>. + url="http://people.FreeBSD.org/~bmah/ThinkPad/"></ulink>. Put these files somewhere you will be able to retrieve them later.</para> </step> @@ -1406,176 +1426,86 @@ <qandaentry> <question id="install-bad-blocks"> - <para>Can I install on a disk with bad blocks?</para> - </question> - - <answer> - <para>Prior to 3.0, FreeBSD included a utility known as - <command>bad144</command>, which automatically remapped bad - blocks. Because modern IDE drives perform this function - themselves, <command>bad144</command> has been removed from the - FreeBSD source tree. If you wish to install FreeBSD 3.0 or - later, we strongly suggest you purchase a newer disk drive. If - you do not wish to do this, you must run FreeBSD 2.x.</para> - <para>If you are seeing bad block errors with a modern IDE - drive, chances are the drive is going to die very soon (the - drive's internal remapping functions are no longer sufficient - to fix the bad blocks, which means the disk is heavily - corrupted); we suggest you buy a new hard drive.</para> - - <para>If you have a SCSI drive with bad blocks, see - <link linkend="awre">this answer</link>.</para> - </answer> - </qandaentry> - - <qandaentry> - <question id="bad144-3x-4x"> - <para>I have just upgraded from 3.X to 4.X, and my first boot - failed with <errorname>bad sector table not - supported</errorname></para> - </question> - - <answer> - <para>FreeBSD 3.X and earlier supported - <command>bad144</command>, which automatically remapped - bad blocks. FreeBSD 4.X and later do not support this, as - modern IDE drives include this functionality. See <link - linkend="install-bad-blocks">this question</link> for - more information.</para> - - <para>To fix this after an upgrade, you need to physically - place the drive in a working system and use - &man.disklabel.8; as discussed in the following - questions.</para> - </answer> - </qandaentry> - - <qandaentry> - <question id="find-bad144"> - <para>How do I tell if a drive has <command>bad144</command> - information on it before I try to upgrade to FreeBSD 4.0 - and it fails?</para> + <para>有壞軌的硬碟可以拿來裝 FreeBSD 嘛？</para> </question> <answer> - <para>Use &man.disklabel.8; for this. <command>disklabel -r - <replaceable>drive device</replaceable></command> will - give you the contents of your disk label. Look for a - <literal>flags</literal> field. If you see - <literal>flags: badsect</literal>, this drive is using - bad144. For example, the following drive has - <command>bad144</command> enabled.:</para> - - <screen>&prompt.root; disklabel -r wd0 -# /dev/rwd0c: -type: ESDI -disk: wd0s1 -label: -flags: badsect -bytes/sector: 512 -sectors/track: 63</screen> - </answer> - </qandaentry> - - <qandaentry> - <question id="disable-bad144"> - <para>How do I remove <command>bad144</command> from my - pre-4.X system so I can upgrade safely?</para> - </question> + <para>(如果很堅持的話)也是可以，不過這想法顯然不太好。:(</para> - <answer> - <para>Use <command>disklabel -e -rwd0 </command> to edit the - disklabel in place. Just remove the word - <literal>badsect</literal> from the flags field, save, and - exit. The bad144 file will still take up some space on - your drive, but the disk itself will be usable.</para> + <para>如果在一般較新的 IDE 硬碟上看到有壞軌，很有可能代表：這顆硬碟即將掛點了。 + (因為目前所有較新的 IDE 硬碟，內部都有自動 remapping 壞軌的能力。 + 如果看到有壞軌，則表示它內部自動 remapping 功能失效，無法處理壞軌， + 也就是說這顆硬碟已經是嚴重損壞程度了。)我們建議買顆新硬碟比較乾脆些唷。</para> - <para>We still recommend you purchase a new disk if you have - a large number of bad blocks.</para> + <para>如果是 SCSI 硬碟有壞軌的話，請試著參考這個 + <link linkend="awre">解法</link>。</para> </answer> </qandaentry> <qandaentry> <question id="boot-floppy-strangeness"> - <para>Strange things happen when I boot the install floppy! - What is happening?</para> + <para>用安裝磁片開機時，卻有些怪現象發生！這是什麼情況呢？</para> </question> <answer> - <para>If you are seeing things like the machine grinding to a halt - or spontaneously rebooting when you try to boot the install - floppy, here are three questions to ask yourself:-</para> + <para>若看到一些怪異現象，像是開機片開機開到一半就當了，磁碟機完全沒任何動作、 + 或是不斷反覆重開機，請先檢查以下幾個線索：</para> <orderedlist> <listitem> - <para>Did you use a new, freshly-formatted, error-free floppy - (preferably a brand-new one straight out of the box, as - opposed to the magazine cover disk that has been lying under - the bed for the last three years)?</para> + <para>請確定是否為全新、沒有磁軌錯誤的磁片？ + (最好使用新買的，而非雜誌、書本附贈的，甚至還藏在床底下三年了...)</para> </listitem> <listitem> - <para>Did you download the floppy image in binary (or image) - mode? (do not be embarrassed, even the best of us have - accidentally downloaded a binary file in ASCII mode at - least once!)</para> + <para>請確定是否有用 binary(或image)傳輸模式來下載 image 檔？ + (不用覺得不好意思，即使是我們也曾意外以 ASCII 傳輸模式來下載 binary 檔案！)</para> </listitem> <listitem> - <para>If you are using Windows95 or Win98 did you run - <command>fdimage</command> or <command>rawrite</command> in - pure DOS mode? These operating systems can interfere with programs that - write directly to hardware, which the disk creation program - does; even running it inside a DOS shell in the GUI can - cause this problem.</para> + <para>若你是 &windows; 95/98/ME/NT/2000/XP/2003 來下載、製作開機磁片的話， + 請確定是否有在 DOS 模式使用 <command>fdimage</command> 或 + <command>rawrite</command> 這兩個工具程式？剛講的這些作業系統， + 都會影響程式去直接寫入硬體，像是製作開機片之類的動作。 + 有時候，在 GUI 介面上的 DOS shell 也可能會發生這樣的問題。 + </para> </listitem> </orderedlist> - <para>There have also been reports of Netscape causing problems - when downloading the boot floppy, so it is probably best to use - a different FTP client if you can.</para> + <para>此外，直接透過 &netscape; 瀏覽器下載 image 檔的話，也有類似現象。 + 所以，如果可以的話，請改用其他可以調整設定的 FTP client端程式來進行下載。 + (當然，要記得調 binary 傳輸模式)</para> </answer> </qandaentry> <qandaentry> <question id="no-install-cdrom"> - <para>I booted from my ATAPI CDROM, but the install program says no - CDROM is found. Where did it go?</para> + <para>用光碟開機片來安裝，但光碟開機後，安裝程式說找不到光碟...這是怎麼了？</para> </question> <answer> - <para>The usual cause of this problem is a mis-configured CDROM - drive. Many PCs now ship with the CDROM as the slave device on - the secondary IDE controller, with no master device on that - controller. This is illegal according to the ATAPI specification, - but Windows plays fast and loose with the specification, and the - BIOS ignores it when booting. This is why the BIOS was able to - see the CDROM to boot from it, but why FreeBSD cannot see it to - complete the install.</para> - - <para>Reconfigure your system so that the CDROM is either the - master device on the IDE controller it is attached to, or make - sure that it is the slave on an IDE controller that also has a - master device.</para> + <para>通常問題在於光碟機設定錯誤。目前很多電腦的出廠標準配備都有光碟機，並且 + 會預先設定為 IDE 通道上面 Secondary 的 Slave 設備，而 Secondary 上面的 + 卻沒有 Master 設備。以 ATAPI 的規格而言，這是錯誤的設定，然而 &windows; 的作法 + 是不理會這些規格上的設定問題，而且開機時 BIOS 偵測也會略過這點。 + 這也就是為什麼 BIOS 可以看到光碟，並且可用光碟開機，但 FreeBSD + 無法正常抓到光碟以順利進行安裝。</para> + + <para>解法：重新設定系統，讓光碟成為它所連接那條 IDE 通道的 Master， + 或者只有一條 IDE 通道的話，那就讓光碟機成為 Slave + ，當然該 IDE 通道上至少要有 Master 設備。</para> </answer> </qandaentry> <qandaentry> <question id="install-PLIP"> - <para>Can I install on my laptop over PLIP (Parallel Line - IP)?</para> + <para>我可以用 PLIP(Parallel Line IP)方式來安裝 FreeBSD 到筆記型電腦上嗎？</para> </question> <answer> - <para>Yes. Use a standard Laplink cable. If necessary, you - can check out the <ulink url="../handbook/plip.html">PLIP - section of the Handbook</ulink> for details on parallel - port networking.</para> - - <para>If you are running FreeBSD 3.X or earlier, also look at - the <ulink - url="http://www.FreeBSD.org/docs.html#PAO">Mobile - Computing page</ulink>.</para> + <para>可以，用一條普通的 Laplink 線就可以囉。若有這方面需求的話，請參閱《 FreeBSD 使用手冊》中的 + <ulink url="&url.books.handbook;/network-plip.html">PLIP + 章節</ulink> 的細部設定</para> </answer> </qandaentry> @@ -1604,8 +1534,7 @@ geometry that they have determined wastes the least space. For IDE disks, FreeBSD does work in terms of C/H/S, but all modern drives internally convert this into block - references. - </para> + references.</para> <para>All that matters is the <emphasis>logical</emphasis> geometry. This is the answer that the BIOS gets when it @@ -1629,9 +1558,9 @@ <para>If it <emphasis>is</emphasis> turned on (it is often supplied this way to get around certain limitations in - MSDOS) and the disk capacity is more than 1GB, use M + &ms-dos;) and the disk capacity is more than 1GB, use M cylinders, 63 sectors per track (<emphasis>not</emphasis> - 64), and 255 heads, where 'M' is the disk capacity in MB + 64), and 255 heads, where <literal>M</literal> is the disk capacity in MB divided by 7.844238 (!). So our example 2GB drive would have 261 cylinders, 63 sectors per track and 255 heads.</para> @@ -1662,8 +1591,7 @@ </question> <answer> - <para>Yes. You must make sure that your root partition is below - 1024 + <para>Yes. You must make sure that your root partition is below 1024 cylinders so the BIOS can boot the kernel from it. (Note that this is a limitation in the PC's BIOS, not FreeBSD).</para> @@ -1701,7 +1629,7 @@ <qandaentry> <question id="missing-os"> - <para>When I boot FreeBSD I get <errorname>Missing Operating + <para>When I boot FreeBSD for the first time after install I get <errorname>Missing Operating System</errorname>. What is happening?</para> </question> @@ -1745,12 +1673,12 @@ except for the kernel-configuration program &man.config.8;. With the exception of the kernel sources, our build structure is set up so that you can read-only mount the sources from - elsewhere via NFS and still be able to make new binaries. - (Because of the kernel-source restriction, we recommend that + elsewhere via NFS and still be able to make new binaries + (due to the kernel-source restriction, we recommend that you not mount this on <filename>/usr/src</filename> directly, but rather in some other location with appropriate symbolic links to duplicate the top-level structure of the source - tree.)</para> + tree).</para> <para>Having the sources on-line and knowing how to build a system with them will make it much easier for you to upgrade @@ -1770,15 +1698,17 @@ <answer> <para>Building a new kernel was originally pretty much a required step in a FreeBSD installation, but more recent releases have - benefited from the introduction of a much friendlier kernel - configuration tool. When at the FreeBSD boot prompt (boot:), + benefited from the introduction of much friendlier kernel + configuration methods. In 4.X and earlier, when at the FreeBSD boot prompt (boot:), use the <option>-c</option> flag and you will be dropped into a visual configuration screen which allows you to configure the - kernel's settings for most common ISA cards.</para> + kernel's settings for most common ISA cards. In &os; 5.X and later + this has been replaced by much more flexible "hints" which + can be set from the loader prompt.</para> - <para>It is still recommended that you eventually build a new + <para>It may still be worthwhile building a new kernel containing just the drivers that you need, just to save a - bit of RAM, but it is no longer a strict requirement for most + bit of RAM, but it is no longer necessary for most systems.</para> </answer> @@ -1786,28 +1716,31 @@ <qandaentry> <question id="password-encryption"> - <para>Should I use DES, Blowfish, or MD5 passwords and how do I specify - which form my users receive?</para> + <para>Should I use DES, Blowfish, or MD5 passwords and how + do I specify which form my users receive?</para> </question> <answer> <para>The default password format on FreeBSD is to use - <emphasis>MD5</emphasis>-based passwords. These are believed to - be more secure than the traditional Unix password format, which - used a scheme based on the <emphasis>DES</emphasis> algorithm. - DES passwords are still available if you need to share your - password file with legacy operating systems which still use the - less secure password format (they are available if you choose + <emphasis>MD5</emphasis>-based passwords. These are + believed to be more secure than the traditional &unix; + password format, which used a scheme based on the + <emphasis>DES</emphasis> algorithm. DES passwords are + still available if you need to share your password file + with legacy operating systems which still use the less + secure password format (they are available if you choose to install the <quote>crypto</quote> distribution in - sysinstall, or by installing the crypto sources if building - from source). Installing the crypto libraries will also allow you - to use the Blowfish password format, which is more secure. - Which password format to use for new passwords is - controlled by the <quote>passwd_format</quote> login capability - in <filename>/etc/login.conf</filename>, which takes values of - <quote>des</quote>, <quote>blf</quote> (if these are available) or <quote>md5</quote>. - See the &man.login.conf.5; manual page for more information about login - capabilities.</para> + sysinstall, or by installing the crypto sources if + building from source). Installing the crypto libraries + will also allow you to use the Blowfish password format, + which is more secure. Which password format to use for + new passwords is controlled by the + <quote>passwd_format</quote> login capability in + <filename>/etc/login.conf</filename>, which takes values + of <quote>des</quote>, <quote>blf</quote> (if these are + available) or <quote>md5</quote>. See the + &man.login.conf.5; manual page for more information about + login capabilities.</para> </answer> </qandaentry> @@ -1819,7 +1752,7 @@ <answer> - <para>If you have a IDE Zip or Jaz drive installed, remove it + <para>If you have a IDE &iomegazip; or &jaz; drive installed, remove it and try again. The boot floppy can get confused by the drives. After the system is installed you can reconnect the drive. Hopefully this will be fixed in a later release.</para> @@ -1833,79 +1766,57 @@ </question> <answer> - <para>This error comes from confusion between the boot block's - and the kernel's understanding of the disk devices. The error - usually manifests on two-disk IDE systems, with the hard disks - arranged as the master or single device on separate IDE - controllers, with FreeBSD installed on the secondary IDE - controller. The boot blocks think the system is installed on - wd1 (the second BIOS disk) while the kernel assigns the first - disk on the secondary controller device wd2. After the device - probing, the kernel tries to mount what the boot blocks think - is the boot disk, wd1, while it is really wd2, and + <para>This error comes from confusion between the boot + block's and the kernel's understanding of the disk + devices. The error usually manifests on two-disk IDE + systems, with the hard disks arranged as the master or + single device on separate IDE controllers, with FreeBSD + installed on the secondary IDE controller. The boot blocks + think the system is installed on ad0 (the second BIOS + disk) while the kernel assigns the first disk on the + secondary controller device, ad2. After the device + probing, the kernel tries to mount what the boot blocks + think is the boot disk, ad0, while it is really ad2, and fails.</para> <para>To fix the problem, do one of the following:</para> <orderedlist> <listitem> - <para>For FreeBSD 3.3 and later, reboot the system and hit - <literal>Enter</literal> at the <literal>Booting kernel - in 10 seconds; hit [Enter] to interrupt</literal> prompt. - This will drop you into the boot loader.</para> + <para>Reboot the system and hit <keycap>Enter</keycap> + at the <literal>Booting kernel in 10 seconds; hit + [Enter] to interrupt</literal> prompt. This will + drop you into the boot loader.</para> <para>Then type <literal> - set root_disk_unit="<replaceable>disk_number</replaceable>" + set + root_disk_unit="<replaceable>disk_number</replaceable>" </literal>. <replaceable>disk_number</replaceable> - will be <literal>0</literal> if FreeBSD is installed on - the master drive on the first IDE controller, - <literal>1</literal> if it is installed on the slave on - the first IDE controller, <literal>2</literal> if it is - installed on the master of the second IDE controller, and - <literal>3</literal> if it is installed on the slave of - the second IDE controller.</para> - - <para>Then type <literal>boot</literal>, and your system - should boot correctly.</para> - - <para>To make this change permanent (ie so you do not have to - do this every time you reboot or turn on your FreeBSD - machine), put the line <literal> - root_disk_unit="<replaceable>disk_number</replaceable>"</literal> in <filename>/boot/loader.conf.local + will be <literal>0</literal> if FreeBSD is installed + on the master drive on the first IDE controller, + <literal>1</literal> if it is installed on the slave + on the first IDE controller, <literal>2</literal> if + it is installed on the master of the second IDE + controller, and <literal>3</literal> if it is + installed on the slave of the second IDE + controller.</para> + + <para>Then type <literal>boot</literal>, and your + system should boot correctly.</para> + + <para>To make this change permanent (ie so you do not + have to do this every time you reboot or turn on + your FreeBSD machine), put the line <literal> + root_disk_unit="<replaceable>disk_number</replaceable>"</literal> + in <filename>/boot/loader.conf.local </filename>.</para> </listitem> <listitem> - <para>If using FreeBSD 3.2 or earlier, at the Boot: prompt, - enter <literal>1:wd(2,a)kernel</literal> and press Enter. - If the system starts, then run the command - <command>echo "1:wd(2,a)kernel" > /boot.config</command> - to make it the default boot string.</para> - </listitem> - - <listitem> - <para>Move the FreeBSD disk onto the primary IDE controller, - so the hard disks are consecutive.</para> - </listitem> - - <listitem> - <para><ulink URL="../handbook/kernelconfig.html">Rebuild - your kernel,</ulink> modify the wd configuration lines to - read:</para> - - <programlisting>controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr -disk wd0 at wdc0 drive 0 -# disk wd1 at wdc0 drive 1 # comment out this line - -controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr -disk wd1 at wdc1 drive 0 # change from wd2 to wd1 -disk wd2 at wdc1 drive 1 # change from wd3 to wd2</programlisting> - - <para>Install the new kernel. If you moved your disks and - wish to restore the previous configuration, replace the - disks in the desired configuration and reboot. Your - system should boot successfully.</para> + <para>Move the FreeBSD disk onto the primary IDE + controller, so the hard disks are + consecutive.</para> </listitem> </orderedlist> </answer> @@ -1917,14 +1828,19 @@ </question> <answer> - <para>For memory, the limit is 4 gigabytes. This configuration - has been tested, see <ulink - URL="ftp://ftp.cdrom.com/archive-info/configuration">wcarchive's - configuration</ulink> for more details. If you plan to install - this much memory into a machine, you need to be careful. You will - probably want to use ECC memory and to reduce capacitive - loading use 9 chip memory modules versus 18 chip memory - modules.</para> + <para>The limit is 4 gigabytes on a standard &i386; install. + Beginning with &os; versions 4.9 and 5.1, more memory can be + supported through &man.pae.4;. This does require a kernel + recompile, with an extra option to enable PAE:</para> + + <programlisting>options PAE</programlisting> + + <para>&os;/pc98 has a limit of 4 GB memory, and PAE can not + be used with it. On &os;/alpha, the limit on memory depends + on the type of hardware in use - consult the Alpha Hardware + Release Notes for details. Other architectures + supported by &os; have much higher theoretical limits on + maximum memory (many terabytes).</para> </answer> </qandaentry> @@ -1941,20 +1857,16 @@ exist).</para> <para>The maximum size of a single ffs file is approximately 1G - blocks (4TB) if the block size is 4K.</para> + blocks, or 4TB with a block size of 4K.</para> <table> <title>Maximum file sizes</title> - <tgroup cols="5"> + <tgroup cols="3"> <thead> <row> <entry>fs block size</entry>

檔案過大！部分文章無法顯示

+ &man.apm.4;.</para> + + <para>FreeBSD 5.X and later support the + <acronym>ACPI</acronym> features found in most modern + hardware. Further information can be found in + &man.acpi.4;. If a system supports both + <acronym>APM</acronym> and <acronym>ACPI</acronym>, either + can be used. We suggest you try both and choose the one + that best fits your needs.</para> + + </answer> + </qandaentry> + + <qandaentry> + <question id="micron-hang-boot"> + <para>Why does my Micron system hang at boot time?</para> + </question> + + <answer> + <para>Certain Micron motherboards have a non-conforming PCI BIOS + implementation that causes grief when FreeBSD boots because PCI + devices do not get configured at their reported addresses.</para> + + <para>Disable the <quote>Plug and Play Operating System</quote> + flag in the BIOS to work around this problem.</para> </answer> </qandaentry> @@ -3069,11 +2715,32 @@ </question> <answer> - <para>Go in to the BIOS setup and disable the <quote>boot virus + <para>Go into the BIOS setup and disable the <quote>boot virus protection</quote>.</para> </answer> </qandaentry> + + <qandaentry> + <question id="micron-3comnic-failure"> + <para>Why does my &tm.3com; PCI network card not work with my Micron + computer?</para> + </question> + + <answer> + <para>Certain Micron motherboards have a non-conforming PCI BIOS + implementation that does not configure PCI devices at the + addresses reported. This causes grief when FreeBSD + boots.</para> + + <para>To work around this problem, disable the + <quote>Plug and Play Operating System</quote> flag in the + BIOS.</para> + </answer> + </qandaentry> </qandaset> + + </sect1> + </chapter> <chapter id="troubleshoot"> @@ -5771,7 +5438,7 @@ <para>Unmounting the device is simple:</para> - <screen>&prompt.user; <userinput>umount<filename>~/my-mount-point</filename></userinput></screen> + <screen>&prompt.user; <userinput>umount <filename>~/my-mount-point</filename></userinput></screen> <para>Enabling <varname>vfs.usermount</varname>, however, has negative security implications. A better way to access MSDOS diff -ruN zh_TW.Big5.orig/share/sgml/bookinfo.ent zh_TW.Big5/share/sgml/bookinfo.ent --- zh_TW.Big5.orig/share/sgml/bookinfo.ent Tue Nov 22 09:25:03 2005 +++ zh_TW.Big5/share/sgml/bookinfo.ent Tue Nov 22 09:25:48 2005 @@ -10,3 +10,7 @@ --> <!ENTITY bookinfo.legalnotice SYSTEM "legalnotice.sgml"> + +<!ENTITY bookinfo.trademarks SYSTEM "trademarks.sgml"> + +<!ENTITY bookinfo.freebsd-glossary SYSTEM "glossary/freebsd-glossary.sgml"> diff -ruN zh_TW.Big5.orig/share/sgml/glossary/freebsd-glossary.sgml zh_TW.Big5/share/sgml/glossary/freebsd-glossary.sgml --- zh_TW.Big5.orig/share/sgml/glossary/freebsd-glossary.sgml Thu Jan 1 08:00:00 1970 +++ zh_TW.Big5/share/sgml/glossary/freebsd-glossary.sgml Tue Nov 22 09:26:51 2005 @@ -0,0 +1,1784 @@ + + +<glossary status="draft" id="freebsd-glossary"> + <title>&os; Glossary</title> + <para>This glossary contains terms and acronyms used within the &os; + community and documentation.</para> + + <glossdiv> + <title>A</title> + + <glossentry> + <glossterm>ACL</glossterm> + <glosssee otherterm="acl-glossary"> + </glossentry> + + <glossentry> + <glossterm>ACPI</glossterm> + <glosssee otherterm="acpi-glossary"> + </glossentry> + + <glossentry> + <glossterm>AMD</glossterm> + <glosssee otherterm="amd-glossary"> + </glossentry> + + <glossentry> + <glossterm>AML</glossterm> + <glosssee otherterm="aml-glossary"> + </glossentry> + + <glossentry> + <glossterm>APIC</glossterm> + <glosssee otherterm="apic-glossary"> + </glossentry> + + <glossentry> + <glossterm>APM</glossterm> + <glosssee otherterm="apm-glossary"> + </glossentry> + + <glossentry> + <glossterm>APOP</glossterm> + <glosssee otherterm="apop-glossary"> + </glossentry> + + <glossentry> + <glossterm>ASL</glossterm> + <glosssee otherterm="asl-glossary"> + </glossentry> + + <glossentry> + <glossterm>ATA</glossterm> + <glosssee otherterm="ata-glossary"> + </glossentry> + + <glossentry> + <glossterm>ATM</glossterm> + <glosssee otherterm="atm-glossary"> + </glossentry> + + <glossentry id="aml-glossary"> + <glossterm><acronym>ACPI</acronym> Machine Language</glossterm> + <acronym>AML</acronym> + <glossdef> + <para>Pseudocode, interpreted by a virtual machine within an + <acronym>ACPI</acronym>-compliant operating system, providing a + layer between the underlying hardware and the documented + interface presented to the <acronym>OS</acronym>.</para> + </glossdef> + </glossentry> + + <glossentry id="asl-glossary"> + <glossterm><acronym>ACPI</acronym> Source Language</glossterm> + <acronym>ASL</acronym> + <glossdef> + <para>The programming language <acronym>AML</acronym> is written in.</para> + </glossdef> + </glossentry> + + <glossentry id="acl-glossary"> + <glossterm>Access Control List</glossterm> + <acronym>ACL</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="acpi-glossary"> + <glossterm>Advanced Configuration and Power Interface</glossterm> + <acronym>ACPI</acronym> + <glossdef> + <para>A specification which provides an abstraction of the + interface the hardware presents to the operating system, so + that the operating system should need to know nothing about + the underlying hardware to make the most of it. <acronym>ACPI</acronym> + evolves and supercedes the functionality provided previously by + <acronym>APM</acronym>, <acronym>PNPBIOS</acronym> and other technologies, and + provides facilities for controlling power consumption, machine + suspension, device enabling and disabling, etc.</para> + </glossdef> + </glossentry> + + <glossentry id="apm-glossary"> + <glossterm>Advanced Power Management</glossterm> + <acronym>APM</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="apic-glossary"> + <glossterm>Advanced Programmable Interrupt Controller</glossterm> + <acronym>APIC</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="ata-glossary"> + <glossterm>Advanced Technology Attachment</glossterm> + <acronym>ATA</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="atm-glossary"> + <glossterm>Asynchronous Transfer Mode</glossterm> + <acronym>ATM</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="apop-glossary"> + <glossterm>Authenticated Post Office Protocol</glossterm> + <acronym>APOP</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="amd-glossary"> + <glossterm>Automatic Mount Daemon</glossterm> + <acronym>AMD</acronym> + <glossdef> + <para>A daemon that automatically mounts a filesystem when a file + or directory within that filesystem is accessed.</para> + </glossdef> + </glossentry> + </glossdiv> + + <glossdiv> + <title>B</title> + + <glossentry> + <glossterm>BIND</glossterm> + <glosssee otherterm="bind-glossary"> + </glossentry> + + <glossentry> + <glossterm>BIOS</glossterm> + <glosssee otherterm="bios-glossary"> + </glossentry> + + <glossentry> + <glossterm>BSD</glossterm> + <glosssee otherterm="bsd-glossary"> + </glossentry> + + <glossentry id="bios-glossary"> + <glossterm>Basic Input/Output System</glossterm> + <acronym>BIOS</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="bind-glossary"> + <glossterm>Berkeley Internet Name Domain</glossterm> + <acronym>BIND</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="bsd-glossary"> + <glossterm>Berkeley Software Distribution</glossterm> + <acronym>BSD</acronym> + <glossdef> + <para>This is the name that the Computer Systems Research Group + (CSRG) at <ulink url="http://www.berkeley.edu">The University + of California at Berkeley</ulink> + gave to their improvements and modifications to + AT&T's 32V &unix;. + &os; is a descendant of the CSRG work.</para> + </glossdef> + </glossentry> + + <glossentry id="bikeshed-glossary"> + <glossterm>Bikeshed Building</glossterm> + <glossdef subject="FreeBSD"> + <para>A phenomenon whereby many people will give an opinion on + an uncomplicated topic, whilst a complex topic receives little + or no discussion. See the + <ulink url="&url.books.faq;/misc.html#BIKESHED-PAINTING">FAQ</ulink> for + the origin of the term.</para> + </glossdef> + </glossentry> + </glossdiv> + + <glossdiv> + <title>C</title> + + <glossentry> + <glossterm>CD</glossterm> + <glosssee otherterm="cd-glossary"> + </glossentry> + + <glossentry> + <glossterm>CHAP</glossterm> + <glosssee otherterm="chap-glossary"> + </glossentry> + + <glossentry> + <glossterm>CLIP</glossterm> + <glosssee otherterm="clip-glossary"> + </glossentry> + + <glossentry> + <glossterm>COFF</glossterm> + <glosssee otherterm="coff-glossary"> + </glossentry> + + <glossentry> + <glossterm>CPU</glossterm> + <glosssee otherterm="cpu-glossary"> + </glossentry> + + <glossentry> + <glossterm>CTS</glossterm> + <glosssee otherterm="cts-glossary"> + </glossentry> + + <glossentry> + <glossterm>CVS</glossterm> + <glosssee otherterm="cvs-glossary"> + </glossentry> + + <glossentry id="cd-glossary"> + <glossterm>Carrier Detect</glossterm> + <acronym>CD</acronym> + <glossdef> + <para>An RS232C signal indicating that a carrier has been + detected.</para> + </glossdef> + </glossentry> + + <glossentry id="cpu-glossary"> + <glossterm>Central Processing Unit</glossterm> + <acronym>CPU</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="chap-glossary"> + <glossterm>Challenge Handshake Authentication Protocol</glossterm> + <acronym>CHAP</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="clip-glossary"> + <glossterm>Classical <acronym>IP</acronym> over <acronym>ATM</acronym></glossterm> + <acronym>CLIP</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="cts-glossary"> + <glossterm>Clear To Send</glossterm> + <acronym>CTS</acronym> + <glossdef> + <para>An RS232C signal giving the remote system + permission to send data.</para> + </glossdef> + </glossentry> + + <glossentry id="coff-glossary"> + <glossterm>Common Object File Format</glossterm> + <acronym>COFF</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="cvs-glossary"> + <glossterm>Concurrent Versions System</glossterm> + <acronym>CVS</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + </glossdiv> + + <glossdiv> + <title>D</title> + + <glossentry> + <glossterm>DAC</glossterm> + <glosssee otherterm="dac-glossary"> + </glossentry> + + <glossentry> + <glossterm>DDB</glossterm> + <glosssee otherterm="ddb-glossary"> + </glossentry> + + <glossentry> + <glossterm>DES</glossterm> + <glosssee otherterm="des-glossary"> + </glossentry> + + <glossentry> + <glossterm>DHCP</glossterm> + <glosssee otherterm="dhcp-glossary"> + </glossentry> + + <glossentry> + <glossterm>DNS</glossterm> + <glosssee otherterm="dns-glossary"> + </glossentry> + + <glossentry> + <glossterm>DSDT</glossterm> + <glosssee otherterm="dsdt-glossary"> + </glossentry> + + <glossentry> + <glossterm>DSR</glossterm> + <glosssee otherterm="dsr-glossary"> + </glossentry> + + <glossentry> + <glossterm>DTR</glossterm> + <glosssee otherterm="dtr-glossary"> + </glossentry> + + <glossentry> + <glossterm>DVMRP</glossterm> + <glosssee otherterm="dvmrp-glossary"> + </glossentry> + + <glossentry id="dac-glossary"> + <glossterm>Discretionary Access Control</glossterm> + <acronym>DAC</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="des-glossary"> + <glossterm>Data Encryption Standard</glossterm> + <acronym>DES</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="dsr-glossary"> + <glossterm>Data Set Ready</glossterm> + <acronym>DSR</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="dtr-glossary"> + <glossterm>Data Terminal Ready</glossterm> + <acronym>DTR</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="ddb-glossary"> + <glossterm>Debugger</glossterm> + <acronym>DDB</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="dsdt-glossary"> + <glossterm>Differentiated System Description Table</glossterm> + <acronym>DSDT</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="dvmrp-glossary"> + <glossterm>Distance-Vector Multicast Routing Protocol</glossterm> + <acronym>DVMRP</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="dns-glossary"> + <glossterm>Domain Name System</glossterm> + <acronym>DNS</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="dhcp-glossary"> + <glossterm>Dynamic Host Configuration Protocol</glossterm> + <acronym>DHCP</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + </glossdiv> + + <glossdiv> + <title>E</title> + + <glossentry> + <glossterm>ECOFF</glossterm> + <glosssee otherterm="ecoff-glossary"> + </glossentry> + + <glossentry> + <glossterm>ELF</glossterm> + <glosssee otherterm="elf-glossary"> + </glossentry> + + <glossentry> + <glossterm>ESP</glossterm> + <glosssee otherterm="esp-glossary"> + </glossentry> + + <glossentry id="esp-glossary"> + <glossterm>Encapsulated Security Payload</glossterm> + <acronym>ESP</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="elf-glossary"> + <glossterm>Executable and Linking Format</glossterm> + <acronym>ELF</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="ecoff-glossary"> + <glossterm>Extended <acronym>COFF</acronym></glossterm> + <acronym>ECOFF</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + </glossdiv> + + <glossdiv> + <title>F</title> + + <glossentry> + <glossterm>FADT</glossterm> + <glosssee otherterm="fadt-glossary"> + </glossentry> + + <glossentry> + <glossterm>FAT</glossterm> + <glosssee otherterm="fat-glossary"> + </glossentry> + + <glossentry> + <glossterm>FAT16</glossterm> + <glosssee otherterm="fat16-glossary"> + </glossentry> + + <glossentry> + <glossterm>FTP</glossterm> + <glosssee otherterm="ftp-glossary"> + </glossentry> + + <glossentry id="fat-glossary"> + <glossterm>File Allocation Table</glossterm> + <acronym>FAT</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="fat16-glossary"> + <glossterm>File Allocation Table (16-bit)</glossterm> + <acronym>FAT16</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="ftp-glossary"> + <glossterm>File Transfer Protocol</glossterm> + <acronym>FTP</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="fadt-glossary"> + <glossterm>Fixed <acronym>ACPI</acronym> Description Table</glossterm> + <acronym>FADT</acronym> + <glossdef> + <para></para> + </glossdef> + </glossdiv> + + <glossdiv> + <title>G</title> + + <glossentry> + <glossterm>GUI</glossterm> + <glosssee otherterm="gui-glossary"> + </glossentry> + + <glossentry id="giant-glossary"> + <glossterm>Giant</glossterm> + <glossdef subject="FreeBSD"> + <para>The name of a mutual exclusion mechanism + (a <literal>sleep mutex</literal>) that protects a large + set of kernel resources. Although a simple locking mechanism + was adequate in the days where a machine might have only + a few dozen processes, one networking card, and certainly + only one processor, in current times it is an unacceptable + performance bottleneck. &os; developers are actively working + to replace it with locks that protect individual resources, + which will allow a much greater degree of parallelism for + both single-processor and multi-processor machines.</para> + </glossdef> + </glossentry> + + <glossentry id="gui-glossary"> + <glossterm>Graphical User Interface</glossterm> + <acronym>GUI</acronym> + <glossdef> + <para>A system where the user and computer interact with + graphics.</para> + </glossdef> + </glossentry> + </glossdiv> + + <glossdiv> + <title>H</title> + + <glossentry> + <glossterm>HTML</glossterm> + <glosssee otherterm="html-glossary"> + </glossentry> + + <glossentry> + <glossterm>HUP</glossterm> + <glosssee otherterm="hup-glossary"> + </glossentry> + + <glossentry id="hup-glossary"> + <glossterm>HangUp</glossterm> + <acronym>HUP</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="html-glossary"> + <glossterm>HyperText Markup Language</glossterm> + <acronym>HTML</acronym> + <glossdef> + <para>The markup language used to create web pages.</para> + </glossdef> + </glossentry> + </glossdiv> + + <glossdiv> + <title>I</title> + + <glossentry> + <glossterm>I/O</glossterm> + <glosssee otherterm="io-glossary"> + </glossentry> + + <glossentry> + <glossterm>IASL</glossterm> + <glosssee otherterm="iasl-glossary"> + </glossentry> + + <glossentry> + <glossterm>IMAP</glossterm> + <glosssee otherterm="imap-glossary"> + </glossentry> + + <glossentry> + <glossterm>IP</glossterm> + <glosssee otherterm="ip-glossary"> + </glossentry> + + <glossentry> + <glossterm>IPFW</glossterm> + <glosssee otherterm="ipfw-glossary"> + </glossentry> + + <glossentry> + <glossterm>IPP</glossterm> + <glosssee otherterm="ipp-glossary"> + </glossentry> + + <glossentry> + <glossterm>IPv4</glossterm> + <glosssee otherterm="ipv4-glossary"> + </glossentry> + + <glossentry> + <glossterm>IPv6</glossterm> + <glosssee otherterm="ipv6-glossary"> + </glossentry> + + <glossentry> + <glossterm>ISP</glossterm> + <glosssee otherterm="isp-glossary"> + </glossentry> + + <glossentry id="ipfw-glossary"> + <glossterm><acronym>IP</acronym> Firewall</glossterm> + <acronym>IPFW</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="ipv4-glossary"> + <glossterm><acronym>IP</acronym> Version 4</glossterm> + <acronym>IPv4</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="ipv6-glossary"> + <glossterm><acronym>IP</acronym> Version 6</glossterm> + <acronym>IPv6</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="io-glossary"> + <glossterm>Input/Output</glossterm> + <acronym>I/O</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="iasl-glossary"> + <glossterm>Intel’s <acronym>ASL</acronym> compiler</glossterm> + <acronym>IASL</acronym> + <glossdef> + <para>Intel’s compiler for converting <acronym>ASL</acronym> into + <acronym>AML</acronym>.</para> + </glossdef> + </glossentry> + + <glossentry id="imap-glossary"> + <glossterm>Internet Message Access Protocol</glossterm> + <acronym>IMAP</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="ipp-glossary"> + <glossterm>Internet Printing Protocol</glossterm> + <acronym>IPP</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="ip-glossary"> + <glossterm>Internet Protocol</glossterm> + <acronym>IP</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="isp-glossary"> + <glossterm>Internet Service Provider</glossterm> + <acronym>ISP</acronym> + <glossdef> + <para></para> + </glossdef> + </glossdiv> + + <glossdiv> + <title>K</title> + + <glossentry id="kame-glossary"> + <glossterm>KAME</glossterm> + <glossdef> + <para>Japanese for <quote>turtle</quote>, the term KAME is used + in computing circles to refer to the <ulink + url="http://www.kame.net/">KAME Project</ulink>, who work on + an implementation of <acronym>IPv6</acronym>.</para> + </glossdef> + </glossentry> + + <glossentry> + <glossterm>KDC</glossterm> + <glosssee otherterm="kdc-glossary"> + </glossentry> + + <glossentry> + <glossterm>KLD</glossterm> + <glosssee otherterm="kld-glossary"> + </glossentry> + + <glossentry> + <glossterm>KSE</glossterm> + <glosssee otherterm="kse-glossary"> + </glossentry> + + <glossentry> + <glossterm>KVA</glossterm> + <glosssee otherterm="kva-glossary"> + </glossentry> + + <glossentry> + <glossterm>Kbps</glossterm> + <glosssee otherterm="kbps-glossary"> + </glossentry> + + <glossentry id="kld-glossary"> + <glossterm>Kernel &man.ld.1;</glossterm> + <acronym>KLD</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="kse-glossary"> + <glossterm>Kernel Scheduler Entities</glossterm> + <acronym>KSE</acronym> + <glossdef> + <para>A kernel-supported threading system. See the <ulink + url="http://www.FreeBSD.org/kse">project home page</ulink> + for further details.</para> + </glossdef> + </glossentry> + + <glossentry id="kva-glossary"> + <glossterm>Kernel Virtual Address</glossterm> + <acronym>KVA</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="kdc-glossary"> + <glossterm>Key Distribution Center</glossterm> + <acronym>KDC</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="kbps-glossary"> + <glossterm>Kilo Bits Per Second</glossterm> + <acronym>Kbps</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + </glossdiv> + + <glossdiv> + <title>L</title> + + <glossentry> + <glossterm>LAN</glossterm> + <glosssee otherterm="lan-glossary"> + </glossentry> + + <glossentry> + <glossterm>LOR</glossterm> + <glosssee otherterm="lor-glossary"> + </glossentry> + + <glossentry> + <glossterm>LPD</glossterm> + <glosssee otherterm="lpd-glossary"> + </glossentry> + + <glossentry id="lpd-glossary"> + <glossterm>Line Printer Daemon</glossterm> + <acronym>LPD</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="lan-glossary"> + <glossterm>Local Area Network</glossterm> + <acronym>LAN</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="lor-glossary"> + <glossterm>Lock Order Reversal</glossterm> + <acronym>LOR</acronym> + <glossdef> + <para>The &os; kernel uses a number of resource locks to + arbitrate contention for those resources. A run-time + lock diagnostic system found in &os.current; kernels + (but removed for releases), called &man.witness.4;, + detects the potential for deadlocks due to locking errors. + (&man.witness.4; is actually slightly conservative, so + it is possible to get false positives.) A true positive + report indicates that <quote>if you were unlucky, a deadlock would + have happened here</quote>.</para> + + <para>True positive LORs tend to get fixed quickly, so + check &a.current.url; and the + <ulink url="http://sources.zabbadoz.net/freebsd/lor.html"> + LORs Seen</ulink> page before posting to the mailing lists.</para> + </glossdef> + </glossentry> + </glossdiv> + + <glossdiv> + <title>M</title> + + <glossentry> + <glossterm>MAC</glossterm> + <glosssee otherterm="mac-glossary"> + </glossentry> + + <glossentry> + <glossterm>MADT</glossterm> + <glosssee otherterm="madt-glossary"> + </glossentry> + + <glossentry> + <glossterm>MFC</glossterm> + <glosssee otherterm="mfc-glossary"> + </glossentry> + + <glossentry> + <glossterm>MFS</glossterm> + <glosssee otherterm="mfs-glossary"> + </glossentry> + + <glossentry> + <glossterm>MIT</glossterm> + <glosssee otherterm="mit-glossary"> + </glossentry> + + <glossentry> + <glossterm>MLS</glossterm> + <glosssee otherterm="mls-glossary"> + </glossentry> + + <glossentry> + <glossterm>MOTD</glossterm> + <glosssee otherterm="motd-glossary"> + </glossentry> + + <glossentry> + <glossterm>MTA</glossterm> + <glosssee otherterm="mta-glossary"> + </glossentry> + + <glossentry> + <glossterm>MUA</glossterm> + <glosssee otherterm="mua-glossary"> + </glossentry> + + <glossentry id="mta-glossary"> + <glossterm>Mail Transfer Agent</glossterm> + <acronym>MTA</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="mua-glossary"> + <glossterm>Mail User Agent</glossterm> + <acronym>MUA</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="mac-glossary"> + <glossterm>Mandatory Access Control</glossterm> + <acronym>MAC</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="mit-glossary"> + <glossterm>Massachusetts Institute of Technology</glossterm> + <acronym>MIT</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="mfc-glossary"> + <glossterm>Merge From Current</glossterm> + <acronym>MFC</acronym> + <glossdef subject="FreeBSD"> + <para>To merge functionality or a patch from the -CURRENT + branch to another, most often -STABLE.</para> + </glossdef> + </glossentry> + + <glossentry id="mfs-glossary"> + <glossterm>Merge From Stable</glossterm> + <acronym>MFS</acronym> + <glossdef subject="FreeBSD"> + <para>In the normal course of FreeBSD development, a change will + be committed to the -CURRENT branch for testing before being + merged to -STABLE. On rare occasions, a change will go into + -STABLE first and then be merged to -CURRENT.</para> + + <para>This term is also used when a patch is merged from -STABLE + to a security branch.</para> + <glossseealso otherterm="mfc-glossary"> + </glossdef> + </glossentry> + + <glossentry id="motd-glossary"> + <glossterm>Message Of The Day</glossterm> + <acronym>MOTD</acronym> + <glossdef> + <para>A message, usually shown on login, often used to + distribute information to users of the system.</para> + </glossdef> + </glossentry> + + <glossentry id="mls-glossary"> + <glossterm>Multi-Level Security</glossterm> + <acronym>MLS</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="madt-glossary"> + <glossterm>Multiple <acronym>APIC</acronym> Description Table</glossterm> + <acronym>MADT</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + </glossdiv> + + <glossdiv> + <title>N</title> + + <glossentry> + <glossterm>NAT</glossterm> + <glosssee otherterm="nat-glossary"> + </glossentry> + + <glossentry> + <glossterm>NDISulator</glossterm> + <glosssee otherterm="projectevil-glossary"> + </glossentry> + + <glossentry> + <glossterm>NFS</glossterm> + <glosssee otherterm="nfs-glossary"> + </glossentry> + + <glossentry> + <glossterm>NTFS</glossterm> + <glosssee otherterm="ntfs-glossary"> + </glossentry> + + <glossentry> + <glossterm>NTP</glossterm> + <glosssee otherterm="ntp-glossary"> + </glossentry> + + <glossentry id="nat-glossary"> + <glossterm>Network Address Translation</glossterm> + <acronym>NAT</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="nfs-glossary"> + <glossterm>Network File System</glossterm> + <acronym>NFS</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="ntfs-glossary"> + <glossterm>New Technology File System</glossterm> + <acronym>NTFS</acronym> + <glossdef> + <para>A filesystem developed by Microsoft and available in its + <quote>New Technology</quote> operating systems, such as + &windows2k;, &windowsnt; and &windowsxp;.</para> + </glossdef> + </glossentry> + + <glossentry id="ntp-glossary"> + <glossterm>Network Time Protocol</glossterm> + <acronym>NTP</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + </glossdiv> + + <glossdiv> + <title>O</title> + + <glossentry> + <glossterm>OBE</glossterm> + <glosssee otherterm="obe-glossary"> + </glossentry> + + <glossentry> + <glossterm>ODMR</glossterm> + <glosssee otherterm="odmr-glossary"> + </glossentry> + + <glossentry> + <glossterm>OS</glossterm> + <glosssee otherterm="os-glossary"> + </glossentry> + + <glossentry id="odmr-glossary"> + <glossterm>On-Demand Mail Relay</glossterm> + <acronym>ODMR</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="os-glossary"> + <glossterm>Operating System</glossterm> + <acronym>OS</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="obe-glossary"> + <glossterm>Overtaken By Events</glossterm> + <acronym>OBE</acronym> + <glossdef> + <para>Indicates a suggested change (such as a Problem Report + or a feature request) which is no longer relevant or + applicable due to such things as later changes to &os;, + changes in networking standards, the affected hardware + having since become obsolete, and so forth.</para> + </glossdef> + </glossentry> + </glossdiv> + + <glossdiv> + <title>P</title> + + <glossentry> + <glossterm>PAE</glossterm> + <glosssee otherterm="pae-glossary"> + </glossentry> + + <glossentry> + <glossterm>PAM</glossterm> + <glosssee otherterm="pam-glossary"> + </glossentry> + + <glossentry> + <glossterm>PAP</glossterm> + <glosssee otherterm="pap-glossary"> + </glossentry> + + <glossentry> + <glossterm>PC</glossterm> + <glosssee otherterm="pc-glossary"> + </glossentry> + + <glossentry> + <glossterm>PCNSFD</glossterm> + <glosssee otherterm="pcnfsd-glossary"> + </glossentry> + + <glossentry> + <glossterm>PDF</glossterm> + <glosssee otherterm="pdf-glossary"> + </glossentry> + + <glossentry> + <glossterm>PID</glossterm> + <glosssee otherterm="pid-glossary"> + </glossentry> + + <glossentry> + <glossterm>POLA</glossterm> + <glosssee otherterm="pola-glossary"> + </glossentry> + + <glossentry> + <glossterm>POP</glossterm> + <glosssee otherterm="pop-glossary"> + </glossentry> + + <glossentry> + <glossterm>POP3</glossterm> + <glosssee otherterm="pop3-glossary"> + </glossentry> + + <glossentry> + <glossterm>PPD</glossterm> + <glosssee otherterm="ppd-glossary"> + </glossentry> + + <glossentry> + <glossterm>PPP</glossterm> + <glosssee otherterm="ppp-glossary"> + </glossentry> + + <glossentry> + <glossterm>PPPoA</glossterm> + <glosssee otherterm="pppoa-glossary"> + </glossentry> + + <glossentry> + <glossterm>PPPoE</glossterm> + <glosssee otherterm="pppoe-glossary"> + </glossentry> + + <glossentry id="pppoa-glossary"> + <glossterm><acronym>PPP</acronym> over <acronym>ATM</acronym></glossterm> + <acronym>PPPoA</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="pppoe-glossary"> + <glossterm><acronym>PPP</acronym> over <acronym>Ethernet</acronym></glossterm> + <acronym>PPPoE</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry> + <glossterm>PR</glossterm> + <glosssee otherterm="pr-glossary"> + </glossentry> + + <glossentry> + <glossterm>PXE</glossterm> + <glosssee otherterm="pxe-glossary"> + </glossentry> + + <glossentry id="pap-glossary"> + <glossterm>Password Authentication Protocol</glossterm> + <acronym>PAP</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="pc-glossary"> + <glossterm>Personal Computer</glossterm> + <acronym>PC</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="pcnfsd-glossary"> + <glossterm>Personal Computer Network File System Daemon</glossterm> + <acronym>PCNFSD</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="pae-glossary"> + <glossterm>Physical Address Extensions</glossterm> + <acronym>PAE</acronym> + <glossdef> + <para>A method of enabling access to up to 64 GB of <acronym>RAM</acronym> on + systems which only physically have a 32-bit wide address space + (and would therefore be limited to 4 GB without PAE).</para> + </glossdef> + </glossentry> + + <glossentry id="pam-glossary"> + <glossterm>Pluggable Authentication Modules</glossterm> + <acronym>PAM</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="ppp-glossary"> + <glossterm>Point-to-Point Protocol</glossterm> + <acronym>PPP</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="pointyhat"> + <glossterm>Pointy Hat</glossterm> + <glossdef subject="FreeBSD"> + <para>A mythical piece of headgear, much like a + <literal>dunce cap</literal>, awarded to any &os; + committer who breaks the build, makes revision numbers + go backwards, or creates any other kind of havoc in + the source base. Any committer worth his or her salt + will soon accumulate a large collection. The usage is + (almost always?) humorous.</para> + </glossdef> + </glossentry> + + <glossentry id="pdf-glossary"> + <glossterm>Portable Document Format</glossterm> + <acronym>PDF</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="pop-glossary"> + <glossterm>Post Office Protocol</glossterm> + <acronym>POP</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="pop3-glossary"> + <glossterm>Post Office Protocol Version 3</glossterm> + <acronym>POP3</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="ppd-glossary"> + <glossterm>PostScript Printer Description</glossterm> + <acronym>PPD</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="pxe-glossary"> + <glossterm>Preboot eXecution Environment</glossterm> + <acronym>PXE</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="pola-glossary"> + <glossterm>Principle Of Least Astonishment</glossterm> + <acronym>POLA</acronym> + <glossdef> + <para>As &os; evolves, changes visible to the user should be + kept as unsurprising as possible. For example, arbitrarily + rearranging system startup variables in + <filename>/etc/defaults/rc.conf</filename> violates + <acronym>POLA</acronym>. Developers consider + <acronym>POLA</acronym> when contemplating user-visible + system changes.</para> + </glossdef> + </glossentry> + + <glossentry id="pr-glossary"> + <glossterm>Problem Report</glossterm> + <acronym>PR</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="pid-glossary"> + <glossterm>Process ID</glossterm> + <acronym>PID</acronym> + <glossdef> + <para>A number, unique to a particular process on a system, + which identifies it and allows actions to be taken against it.</para> + </glossdef> + </glossentry> + + <glossentry id="projectevil-glossary"> + <glossterm>Project Evil</glossterm> + <glossdef subject="FreeBSD"> + <para>The working title for the <acronym>NDISulator</acronym>, + written by Bill Paul, who named it referring to how awful + it is (from a philosophical standpoint) to need to have + something like this in the first place. The + <acronym>NDISulator</acronym> is a special compatibility + module to allow Microsoft Windows™ NDIS miniport + network drivers to be used with &os;/i386. This is usually + the only way to use cards where the driver is closed-source. + See <filename>src/sys/compat/ndis/subr_ndis.c</filename>.</para> + </glossdef> + </glossentry> + </glossdiv> + + <glossdiv> + <title>R</title> + + <glossentry> + <glossterm>RA</glossterm> + <glosssee otherterm="ra-glossary"> + </glossentry> + + <glossentry> + <glossterm>RAID</glossterm> + <glosssee otherterm="raid-glossary"> + </glossentry> + + <glossentry> + <glossterm>RAM</glossterm> + <glosssee otherterm="ram-glossary"> + </glossentry> + + <glossentry> + <glossterm>RD</glossterm> + <glosssee otherterm="rd-glossary"> + </glossentry> + + <glossentry> + <glossterm>RFC</glossterm> + <glosssee otherterm="rfc-glossary"> + </glossentry> + + <glossentry> + <glossterm>RISC</glossterm> + <glosssee otherterm="risc-glossary"> + </glossentry> + + <glossentry> + <glossterm>RPC</glossterm> + <glosssee otherterm="rpc-glossary"> + </glossentry> + + <glossentry> + <glossterm>RS232C</glossterm> + <glosssee otherterm="rs232c-glossary"> + </glossentry> + + <glossentry> + <glossterm>RTS</glossterm> + <glosssee otherterm="rts-glossary"> + </glossentry> + + <glossentry id="ram-glossary"> + <glossterm>Random Access Memory</glossterm> + <acronym>RAM</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="rd-glossary"> + <glossterm>Received Data</glossterm> + <acronym>RD</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="rs232c-glossary"> + <glossterm>Recommended Standard 232C</glossterm> + <acronym>RS232C</acronym> + <glossdef> + <para>A standard for communications between serial devices.</para> + </glossdef> + </glossentry> + + <glossentry id="risc-glossary"> + <glossterm>Reduced Instruction Set Computer</glossterm> + <acronym>RISC</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="raid-glossary"> + <glossterm>Redundant Array of Inexpensive Disks</glossterm> + <acronym>RAID</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="rpc-glossary"> + <glossterm>Remote Procedure Call</glossterm> + <acronym>RPC</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="rfc-glossary"> + <glossterm>Request For Comments</glossterm> + <acronym>RFC</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="rts-glossary"> + <glossterm>Request To Send</glossterm> + <acronym>RTS</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="ra-glossary"> + <glossterm>Router Advertisement</glossterm> + <acronym>RA</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + </glossdiv> + + <glossdiv> + <title>S</title> + + <glossentry> + <glossterm>SCI</glossterm> + <glosssee otherterm="sci-glossary"> + </glossentry> + + <glossentry> + <glossterm>SCSI</glossterm> + <glosssee otherterm="scsi-glossary"> + </glossentry> + + <glossentry> + <glossterm>SG</glossterm> + <glosssee otherterm="sg-glossary"> + </glossentry> + + <glossentry> + <glossterm>SMB</glossterm> + <glosssee otherterm="smb-glossary"> + </glossentry> + + <glossentry> + <glossterm>SMP</glossterm> + <glosssee otherterm="smp-glossary"> + </glossentry> + + <glossentry> + <glossterm>SMTP</glossterm> + <glosssee otherterm="smtp-glossary"> + </glossentry> + + <glossentry> + <glossterm>SMTP AUTH</glossterm> + <glosssee otherterm="smtpauth-glossary"> + </glossentry> + + <glossentry> + <glossterm>SSH</glossterm> + <glosssee otherterm="ssh-glossary"> + </glossentry> + + <glossentry> + <glossterm>STR</glossterm> + <glosssee otherterm="str-glossary"> + </glossentry> + + <glossentry id="smtpauth-glossary"> + <glossterm><acronym>SMTP</acronym> Authentication</glossterm> + <acronym>SMTP AUTH</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="smb-glossary"> + <glossterm>Server Message Block</glossterm> + <acronym>SMB</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="sg-glossary"> + <glossterm>Signal Ground</glossterm> + <acronym>SG</acronym> + <glossdef> + <para>An RS232 pin or wire that is the ground reference + for the signal.</para> + </glossdef> + </glossentry> + + <glossentry id="smtp-glossary"> + <glossterm>Simple Mail Transfer Protocol</glossterm> + <acronym>SMTP</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="ssh-glossary"> + <glossterm>Secure Shell</glossterm> + <acronym>SSH</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="scsi-glossary"> + <glossterm>Small Computer System Interface</glossterm> + <acronym>SCSI</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="str-glossary"> + <glossterm>Suspend To <acronym>RAM</acronym></glossterm> + <acronym>STR</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="smp-glossary"> + <glossterm>Symmetric MultiProcessor</glossterm> + <acronym>SMP</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="sci-glossary"> + <glossterm>System Control Interrupt</glossterm> + <acronym>SCI</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + </glossdiv> + + <glossdiv> + <title>T</title> + + <glossentry> + <glossterm>TCP</glossterm> + <glosssee otherterm="tcp-glossary"> + </glossentry> + + <glossentry> + <glossterm>TD</glossterm> + <glosssee otherterm="td-glossary"> + </glossentry> + + <glossentry> + <glossterm>TFTP</glossterm> + <glosssee otherterm="tftp-glossary"> + </glossentry> + + <glossentry> + <glossterm>TGT</glossterm> + <glosssee otherterm="tgt-glossary"> + </glossentry> + + <glossentry> + <glossterm>TSC</glossterm> + <glosssee otherterm="tsc-glossary"> + </glossentry> + + <glossentry id="tgt-glossary"> + <glossterm>Ticket-Granting Ticket</glossterm> + <acronym>TGT</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="tsc-glossary"> + <glossterm>Time Stamp Counter</glossterm> + <acronym>TSC</acronym> +  + <glossdef> + <para>A profiling counter internal to modern &pentium; processors + that counts core frequency clock ticks.</para> + </glossdef> + </glossentry> + + <glossentry id="tcp-glossary"> + <glossterm>Transmission Control Protocol</glossterm> + <acronym>TCP</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="td-glossary"> + <glossterm>Transmitted Data</glossterm> + <acronym>TD</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="tftp-glossary"> + <glossterm>Trivial <acronym>FTP</acronym></glossterm> + <acronym>TFTP</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + </glossdiv> + + <glossdiv> + <title>U</title> + + <glossentry> + <glossterm>UDP</glossterm> + <glosssee otherterm="udp-glossary"> + </glossentry> + + <glossentry> + <glossterm>UFS1</glossterm> + <glosssee otherterm="ufs1-glossary"> + </glossentry> + + <glossentry> + <glossterm>UFS2</glossterm> + <glosssee otherterm="ufs2-glossary"> + </glossentry> + + <glossentry> + <glossterm>UID</glossterm> + <glosssee otherterm="uid-glossary"> + </glossentry> + + <glossentry> + <glossterm>URL</glossterm> + <glosssee otherterm="url-glossary"> + </glossentry> + + <glossentry> + <glossterm>USB</glossterm> + <glosssee otherterm="usb-glossary"> + </glossentry> + + <glossentry id="url-glossary"> + <glossterm>Uniform Resource Locator</glossterm> + <acronym>URL</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="ufs1-glossary"> + <glossterm>Unix File System Version 1</glossterm> + <acronym>UFS1</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="ufs2-glossary"> + <glossterm>Unix File System Version 2</glossterm> + <acronym>UFS2</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="usb-glossary"> + <glossterm>Universal Serial Bus</glossterm> + <acronym>USB</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + + <glossentry id="uid-glossary"> + <glossterm>User ID</glossterm> + <acronym>UID</acronym> + <glossdef> + <para>A unique number assigned to each user of a computer, + by which the resources and permissions assigned to that + user can be identified.</para> + </glossdef> + </glossentry> + + <glossentry id="udp-glossary"> + <glossterm>User Datagram Protocol</glossterm> + <acronym>UDP</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + </glossdiv> + + <glossdiv> + <title>V</title> + + <glossentry> + <glossterm>VPN</glossterm> + <glosssee otherterm="vpn-glossary"> + </glossentry> + + <glossentry id="vpn-glossary"> + <glossterm>Virtual Private Network</glossterm> + <acronym>VPN</acronym> + <glossdef> + <para></para> + </glossdef> + </glossentry> + </glossdiv> +</glossary> --- zh_TW4.diff ends here --- >Release-Note: >Audit-Trail: >Unformatted: _______________________________________________ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org"