From owner-freebsd-doc@FreeBSD.ORG Wed Nov 23 12:00:42 2005 Return-Path: X-Original-To: freebsd-doc@hub.freebsd.org Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 73B9C16A47C for ; Wed, 23 Nov 2005 12:00:42 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BF7843D5C for ; Wed, 23 Nov 2005 12:00:38 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jANC0cA0031500 for ; Wed, 23 Nov 2005 12:00:38 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jANC0cNC031484; Wed, 23 Nov 2005 12:00:38 GMT (envelope-from gnats) Resent-Date: Wed, 23 Nov 2005 12:00:38 GMT Resent-Message-Id: <200511231200.jANC0cNC031484@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-doc@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, chinsan Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF69816A41F; Wed, 23 Nov 2005 11:50:20 +0000 (GMT) (envelope-from chinsan@smtp2.bc.hgc.com.tw) Received: from smtp2.bc.hgc.com.tw (smtp2.bc.hgc.com.tw [203.133.1.156]) by mx1.FreeBSD.org (Postfix) with ESMTP id 122B143D69; Wed, 23 Nov 2005 11:50:19 +0000 (GMT) (envelope-from chinsan@smtp2.bc.hgc.com.tw) Received: by smtp2.bc.hgc.com.tw (Postfix, from userid 1006) id 4E54D2E984; Wed, 23 Nov 2005 19:50:19 +0800 (CST) Message-Id: <20051123115019.4E54D2E984@smtp2.bc.hgc.com.tw> Date: Wed, 23 Nov 2005 19:50:19 +0800 (CST) From: chinsan To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 X-Mailman-Approved-At: Wed, 23 Nov 2005 12:43:33 +0000 Cc: vanilla@FreeBSD.org Subject: docs/89456: [UPDATE] zh_TW.Big5: update FAQ(Chapter 1 - Chapter 4) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: chinsan List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Nov 2005 12:00:42 -0000 >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 @@ %mailing-lists; + +%books.ent; + ]> - FreeBSD 2.X，3.X 及 4.X 常見問答集 + FreeBSD 4.X，5.X 及 6.X 常見問答集 FreeBSD 文件計畫 @@ -34,23 +37,50 @@ 2000 2001 2002 + 2003 + 2004 + 2005 FreeBSD 文件計畫 &bookinfo.legalnotice; + + &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; + + - 這份文件是 FreeBSD 2.X，3.X 及 4.X 的常見問答集。 - 除非有特別加註，否則這些項目目都適用於 FreeBSD 2.0.5 及以後的版本。 - 如果條目內容中有 <XXX> 則是尚未完成的部份。 如果您對協助本計畫 + 這份文件是 FreeBSD 4.X，5.X 及 6.X 的常見問答集。 + 除非有特別加註，否則這些項目目都適用於 FreeBSD 4.0 及以後的版本。 + (如果條目內容中有 <XXX> 則是尚未完成中譯的部份。) 如果您對協助本計畫 的進行有興趣的話，請寄一封電子郵件到FreeBSD 文件計畫的 mailing list - &a.doc;。您可以從 + &a.doc;。您可以從 FreeBSD World Wide Web 拿到這份文件的最新版本。 - 您也可以利用 HTTP 來下載一份龐大的 HTML + 也可以利用 HTTP 來下載一份龐大的 HTML 文件，或是經由 FreeBSD FTP 站 下載純文字，postscript，或 PDF 版本的檔案。 您也可以在這裡使用 - 搜尋資料 + 搜尋資料 的功能。 @@ -68,7 +98,7 @@ 前言 - 歡迎來到 FreeBSD 2.X-4.X FAQ! + 歡迎使用 FreeBSD 4.X-6.X FAQ! 跟其他 Usenet 上的 FAQ 一樣，這份文件涵蓋了有關 FreeBSD 這套作業 系統最常被問到的問題 (當然包括了回答！)。雖然說我們本來的目的是為了 @@ -76,7 +106,7 @@ 為是一種值得閱讀的文件資源。 我們已經儘可能地使這份 FAQ 更豐富了。如果您對如何使其更進步有任 - 何建議，請隨時寄電子郵件給 &a.faq;。 + 何建議，請隨時寄電子郵件給 &a.doc;。 @@ -85,24 +115,22 @@ - 簡單地來說，FreeBSD 是一套可以在 i386 和 Alpha/AXP 上執行的 + 簡單地來說，FreeBSD 是一套可以在 Alpha/AXP, AMD64 及 + &intel; EM64T, &i386; IA-64, PC-98, &ultrasparc; 上執行的 UN*X-like 作業系統，它是根據 U.C. Berkeley 所開發出來的 4.4BSD-Lite，並加上了許多 4.4BSD-Lite2 的增強功能。它同時也間接使用了 U.C. Berkeley 所開發出來並由 William Jolitz 移植到 i386 的 Net/2，也就是 386BSD，不過現在 386BSD 的程式碼只剩下極少數還留 存在 FreeBSD 中。您可以在 - FreeBSD 首頁找到有關 + FreeBSD 首頁找到有關 什麼是 FreeBSD 以及它可以幫您做些什麼的相關資訊。 FreeBSD 已被廣泛地被世界各地的公司行號，ISP，研究人員，電腦 - 專家，學生，以及家庭用戶所使用，用在工作，教育，以及娛樂上。您可 - 以在 - FreeBSD Gallery - 看到一些有關他們的資料。 + 專家，學生，以及家庭用戶所使用，用在工作，教育，以及娛樂上。 如果想看關於 FreeBSD 更深入的資料，請看 - FreeBSD 使用手冊。 + FreeBSD 使用手冊。 @@ -175,15 +203,14 @@ 的話，你就不能輕易地把它換掉，或者指望在 FreeBSD 上有很相似的應用 程式才有機會。如果你想要的是一個強健的辦公室或是網路伺服器，或是 一部穩定的工作站，或是想在不被中斷的環境下工作的話，FreeBSD 無疑 - 是您的最佳選擇。世界各地有很多使用者，包括初學或資深的 UNIX 管理 + 是您的最佳選擇。世界各地有很多使用者，包括初學或資深的 &unix; 管理 人員都選用 FreeBSD 當他們唯一的桌上作業系統。 - 如果你是從其他的 UNIX 環境轉換到 FreeBSD 的話，基本上是大同小 - 異的。但是如果你之前用的是圖形界面的作業系統例如說是 Windows 或是 - 比較古老的 Mac OS 的話，可能就要多花一點時間來學習怎麼用 UNIX 的 + 如果你是從其他的 &unix; 環境轉換到 FreeBSD 的話，基本上是大同小 + 異的。但是如果你之前用的是圖形界面的作業系統，例如說是 &windows; 或是 + 比較古老的 &macos; 的話，可能就要多花一點時間來學習怎麼用 &unix; 的 方法來做事。你可以從這份 FAQ 和 FreeBSD 使用手冊 來入 - 門。 + url="&url.books.handbook;/index.html">FreeBSD 使用手冊 來入門。 @@ -218,16 +245,49 @@ + + FreeBSD 及 NetBSD, OpenBSD 以及其他 + open source BSD 作業系統之間有何不同之處呢？ + + + + James Howard 在 DaemonNews + 上寫了 + The BSD Family Tree 的文件，裡面說明了這些歷史淵源及這些 *BSD + 家族計畫之間的差異。 + + + + 最新版的 FreeBSD 是那一版？ - - &rel.current; - 是目前最新的 RELEASE 版；它於 - &rel.current.date; 發行。它同時也是目前最新的 - STABLE 版。 + + + + 就 FreeBSD 目前的發展而言，有四個主要發展分支(其中三個已有 RELEASE)： + 由 4-STABLE 所發行(release)的 4.X 系列、 + 由 5-STABLE 所發行(release)的 5.X 系列、 + 由 6-STABLE 所發行(release)的 6.X 系列， + 以及 7-CURRENT 分支。 + + 在 5.3 release 之前，4.X 系列仍被視為是 -STABLE 之一。 + 自從 5.3 開始，5.X 開始規劃新的 -STABLE 發展重點， + 而 4.X 將只著重在重大問題上(比如：漏洞修補、安全維護)以及 "extended support" + ，不再會有新的突破性發展。 + + + 於 &rel.current.date; 所發行的&rel.current; + 版是目前最新的 6-STABLE 版； + 而於 &rel2.current.date; 所發行的&rel2.current; + 版則是目前最新的 &rel.current.date; 版。 簡單的說，-STABLE 的主要訴求對象是對於 穩定性及低變異性的需求遠勝過對最新 -CURRENT @@ -237,11 +297,14 @@ 容易更動這一點，才應該用 -CURRENT。 Release 版每幾個月才會發 - 行一次。雖然如此，有很多人和 FreeBSD 原程碼同步更新（詳見 + 行一次。雖然如此，有很多人和 FreeBSD 原始碼同步更新（詳見 FreeBSD-CURRENT 和 FreeBSD-STABLE 的相關問題)，但因為原始碼 是一直不斷地在變動的，所以如果要這麼做的話得要花上更多的精 力。 + + 其他更多相關 FreeBSD 發行情報，可由 FreeBSD 網站上的 Release Engineering 得知 @@ -252,12 +315,12 @@ FreeBSD-CURRENT + url="&url.books.handbook;/cutting-edge.html#CURRENT">FreeBSD-CURRENT 指的是正在發展中的作業系統版本，它終將在適當的時機成為 - 5.0-RELEASE。它實在是只適合給系統發展者以及有毅力的業餘愛好者使用 + &os.stable; 分支。它實在是只適合給系統發展者以及有毅力的業餘愛好者使用 。如果想要得到有關如何使用 -CURRENT 的深入資訊，請參考 使用手冊 的 相關部份。 + url="&url.books.handbook;/index.html">使用手冊 的 相關部份。 如果您對作業系統本身並不是很熟悉，或是您沒辦法分辨您遇到的問 @@ -270,7 +333,7 @@ 誤之類的問題的話，也許會被其他人輕視。 我們每天都會根據目前 -CURRENT 和 -STABLE 的狀況對這兩個分支各 - 發行一個snapshot + 發行一個snapshot 版。有的時候甚至還會發行可供取得的版本。發表這些 snapshot 的目的在於： @@ -295,17 +358,14 @@ - 我們不對 -CURRENT snapshot 做任合形式的品質保 + 我們不對 -CURRENT snapshot 做任何形式的品質保 證。如果你想要的是一個穩定且經過充分測試過的系統的話， 最好選擇使用完整 release 的版本，或是使用 -STABLE snapshots。 您可以直接從 - ftp://current.FreeBSD.org/pub/FreeBSD/ 取得 5.0-CURRENT 的 - snapshot release，而從 releng4.FreeBSD.org - 取得 4-STABLE 的 snapshots。在本文寫作的時候 - (2000 年 5 月) 就已經不再提供 3-STABLE 的 snapshots 了。 + URL="ftp://current.FreeBSD.org/pub/FreeBSD/snapshots/"> + ftp://current.FreeBSD.org/pub/FreeBSD/snapshots/ 取得 -CURRENT 的 + snapshot release 對每個有在活動的分支而言，平均每天都會產生一次 snapshots。 @@ -319,12 +379,17 @@ 回溯到 FreeBSD 2.0.5 剛發表的時候，我們決定把 FreeBSD 的發展 - 分成兩支。一支叫做 -STABLE - ，我們只對它做錯誤修正及小幅度的修改 (這是給 ISP 和商業 - 公司等對實驗中功能不感興趣的單位所使用的)。另外一支叫做 -CURRENT，從 - 2.0 版發行以後就不間斷地朝著 5.0-RELEASE (以及以後的版本) 前進 - 著。下面就是版本演進的示意圖： + 分成兩支。一支叫做 -STABLE + ，我們只對它做錯誤修正及小幅度的修改 (這是給 ISP 和商業公司等，對實驗中功能不感興趣的單位所使用的)。 + 另外一支叫做 -CURRENT，從 + 2.0 版發行以後，就不斷地朝著 6.0-RELEASE (含後續的版本)前進著。 + + 6-STABLE 分支是從 6.0-RELEASE 開始(5-STABLE 分支算是 5.3-RELEASE 之後才開始的)， + 然後原本的 &os.current; 就會成為 7-CURRENT。 + + + + 下面就是版本演進的示意圖： 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] + [7.0-CURRENT continues] 2.2-STABLE 這個分支隨著 2.2.8 的發表而功成身退。3-STABLE 這個 分支則是結束在 3.5.1 發表之後，它也是 3.X 的最後一次發表。之後除了 - 安全相關的修正之外，這兩個分支就幾乎沒有再更動過。 + 安全相關的修正之外，這兩個分支就幾乎沒有再更動過。4-STABLE 分支的支援 + 會持續到 2007/01/31，但主要焦點在於安全方面的漏洞、臭蟲及其他嚴重問題的修補。 - 4-STABLE 是目前正在發展中的 -STABLE 分支。4-STABLE 的最新的一 - 次發表是 &rel.current.date; 發行的 &rel.current;-RELEASE。 + 5-STABLE 是目前正在發展中的 -STABLE 分支。5-STABLE 的最新的一 + 次發表是在 &rel2.current.date; 發行的 &rel2.current;-RELEASE。 - 5-CURRENT 的這個分支目前正以緩慢的速度 5.0-RELEASE 以及之後的 - 版本邁進中。如果想要知道更多關於這個分支的資訊的話，請參考 什麼是 FreeBSD-CURRENT？。 + 6-STABLE 是目前正在發展中的 -STABLE 分支。6-STABLE 的最新的一 + 次發表是在 &rel.current.date; 發行的 &rel.current;-RELEASE。 + + 7-CURRENT 這個分支是 &os; 的 -CURRENT 分支，仍然不斷地在發展當中。 + 如果想要知道更多關於這個分支的資訊的話，請參考 什麼是 &os;-CURRENT？。 - 新的 FreeBSD 將於什麼時候推出？ + 每次新的 FreeBSD 將於什麼時候推出？ - 一般而言，當 FreeBSD core team 認為已經累積了足夠多的新功能 - 和錯誤修正，而且這些更動都已經完整地測試過且不會影響系統穩定度的 - 時候，他們才會推出新版的 FreeBSD。新版本的發表時程都會事先公告， - 相關的開發人員就知道什麼時候該把手邊的計劃完成並且測試過。雖然等 - 這些好東西進入 -STABLE 的時間令人有點沮喪，但是大多數的使用者都 - 認為這種謹慎的態度是 FreeBSD 最好的優點之一。 + 一般而言，&a.re; 平均每四個月發行一次 release，每次新版本的發表時程都會事先公告， + 相關的開發人員就會知道，什麼時候該先把手邊的計劃完成並且測試過， + 此外，這些更動都已經完整地測試過，且不會影響系統穩定度。 + 雖然，等這些好東西進入 -STABLE 的時間令人等得有些不耐煩， + 但是大多數的使用者都認為這種謹慎的態度是 FreeBSD 最好的優點之一。 - 平均而言，我們每四個月發行一次 release。 + 有關發行情報的更多細節部分(包括 release 的行程表、進度)，都可在 FreeBSD 網站上的 + 發行情報 上面獲得。 - 為了滿足那些需要 (或想要) 刺激的使用者，上面已經說過我們每天 - 都會發行 snapshots 版可供使用。 + 為了滿足那些需要 (或想要) 新鮮刺激感的使用者， + 上面(-CURRENT的部分)已經提到我們每天都會發行 snapshots 版可供使用。 @@ -397,15 +475,15 @@ 如果是一些有關 FreeBSD 計畫的關鍵性決定，像是整個計畫的走向 或是決定誰可以改 source tree 裡的程式碼這類的事，是由一個由 9 個 - 人所組成的 core - team 來決定。而有另一群超過 200 個人的 + 人所組成的 core + team 來決定。而有另一群超過 300 個人的 commiters 有權利可以直接修改 FreeBSD 的 source tree。 無論如何，大多數的改變都會事前在 - mailing lists 先討論過，而且每個人都可以參與討論。 + mailing lists 先討論過，而且不分角色，每個人都可以參與討論。 @@ -416,74 +494,86 @@ 每個 FreeBSD 的重要版本都可以經由匿名 ftp 從 FreeBSD FTP site - 取得： + url="ftp://ftp.FreeBSD.org/pub/FreeBSD/">FreeBSD FTP 站取得： - - - 如果要的是 3.X-STABLE 的最新版，也就是 3.5.1-RELEASE，請到 - 3.5.1-RELEASE 這個目錄。 - + + + 如果需要 6-STABLE 的最新版，也就是 &rel.current;-RELEASE，請到 &rel.current;-RELEASE 這個目錄 + - - 如果要的是 4-STABLE 的最新版，也就是 &rel.current;-RELEASE - ，請到 &rel.current;-RELEASE 這個目錄 - + + 7-CURRENT Snapshot + 通常也是每天都會做一份，這是從 -CURRENT 分支做出來的， + 主要是為了提供給那些熱心的測試者和開發人員。 + - - 4.X - snapshots 通常每天都會做一份。 - + + 如果需要 5-STABLE 的最新版，也就是 &rel2.current;-RELEASE，請到 &rel2.current;-RELEASE 這個目錄 + - - - 5.0 Snapshot 通常也是每天都會做一份，這是從 -CURRENT 分支做出來的，主要是為了服 - 務那些熱心的測試者和開發人員所提供的。 - + + 如果需要 4-STABLE 的最新版，也就是 4.11-RELEASE，請到 4.11-RELEASE 這個目錄 + + + + 4.X、5.X、6X snapshots + 通常每天都會做一份。 + - FreeBSD 的 CD，DVD，還有一些其他的東西的取得法可以在 使用手冊中找到解答。 + FreeBSD 的 CD、DVD，還有其他取得方式可以在 使用手冊 中找到解答。 + + 怎麼建立 FreeBSD 的映射(mirror)站台？ + + + + 有關如何建立 FreeBSD 映射站(mirror)的資料，可以參考 Mirroring FreeBSD 文章 + + + + - 我要如何去存取錯誤回報資料庫呢？ + 我要如何去查詢、提交問題回報(Problem Report)資料庫呢？ - 所有使用者的變更要求都可以經由我們網頁介面的 PR submission 及 + 所有使用者的變更要求都可以經由網頁介面的 PR - query 來查詢 (或是回報) 我們的錯誤回報資料庫。也可以利用 - &man.send-pr.1; 這個指令透過電子郵件來回報錯誤或是要求變更。 + 查詢介面 來察看 (或是回報) 我們的錯誤回報資料庫。 + + 也可以使用 &man.send-pr.1; 這個指令透過電子郵件來回報問題、要求變更。 + 或者是經由 網頁介面的 PR 來送出問題回報。 - 在回報錯誤之前，請先讀過 如何撰寫 - FreeBSD 的錯誤回報單，這是一篇告訴你怎樣才能寫出一篇有用的 - 錯誤回報單。 + 然而，在您回報問題之前，請先閱讀 如何撰寫 + FreeBSD 的問題回報單，這是一篇告訴你怎樣才能寫出一篇真正有用的 + 問題回報單。 - 要怎樣才能成為 FreeBSD 的網頁映射站台？ + 要怎樣才能成為 FreeBSD 的網頁映射(mirror)站台？ - 有很多方法可以映射我們的網頁。 + 有很多方法可以映射(mirror)我們的網頁。 您可以利用 net/cvsup 從 cvsup.FreeBSD.org 取得格式化過的檔案。 - /usr/share/examples/cvsup/www-supfile就 - 是一個教你怎樣做網頁映射的 CVSup 設定範例。 + /usr/share/examples/cvsup/www-supfile + 這檔就是一個教你怎樣做網頁映射的 CVSup 設定範例。 @@ -491,7 +581,7 @@ 您可以利用您喜歡的 ftp mirror 工具從 FreeBSD 的 FTP 站臺 中取得網頁的原始碼。但是要注意的是在你打算提供公開服務之前， 記得要先利用這些原始碼把網頁重建起來。請從 ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/www 開始抓取。 + url="ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/www"> 開始抓取。 @@ -512,60 +602,66 @@ - Documentation and Support + + + Chin-San + Huang + +
chinsan.tw@gmail.com
+ + + + + 文件與支援 - What good books are there about FreeBSD? + 關於 FreeBSD 有哪些好書可以推薦閱讀的嗎？ - The project produces a wide range of documentation, available - from this link: - http://www.FreeBSD.org/docs.html. + FreeBSD 文件計畫已陸續發表了相當廣泛範圍的文件，可在 取得。另外， + FreeBSD 本身的 manual(一般通稱的man)、doc也如同套件軟體一樣，可以輕鬆地裝在您系統上。 + - In addition, the Bibliography at the end of this FAQ, and the - one in the Handbook reference other recommended books. + 此外，也建議參閱本份 FAQ 最後所列的參考書目表(Bibliography)與《 FreeBSD 使用手冊》。 + - Is the documentation available in other formats, such as plain - text (ASCII), or Postscript? + 這些文件有其他格式的嗎？像是：純文字(ASCII)或 &postscript; 之類的格式？ - Yes. The documentation is available in a number of - different formats and compression schemes on the FreeBSD - FTP site, in the /pub/FreeBSD/doc/ - directory. + 有的。這些文件都分別以不同格式儲存以及壓縮處理，放在 + FTP 上面，可以從各 FreeBSD FTP 站的 /pub/FreeBSD/doc/ + 目錄內找到你要的。 - The documentation is categorized in a number of different - ways. These include: + 文件的分類方面主要是一些不同性質所組成： - The document's name, such as faq, or - handbook. + 文件名稱，比如：faq(常見問答集)或是 + handbook(FreeBSD 使用手冊)等等。 - The document's language and encoding. These are based on - the locale names you will find under - /usr/share/locale on your FreeBSD - system. The current languages and encodings that we have for - documentation are as follows: + 各國翻譯的的文件：這主要是由 locale 名稱來決定的 + (不清楚的話，可參考您的 FreeBSD 作業系統上的 /usr/share/locale) + 目前文件總共有下列幾種語言(及編碼)有翻譯： - + - Name + Locale 名稱 - Meaning + 說明(所代表的語系、編碼) @@ -573,72 +669,72 @@ en_US.ISO8859-1 - US English + 美式英文(US English) de_DE.ISO8859-1 - German + 德文(German) es_ES.ISO8859-1 - Spanish + 西班牙文(Spanish) fr_FR.ISO8859-1 - French + 法文(French) + + it_IT.ISO8859-15 + + 義大利文(Italian) + + ja_JP.eucJP - Japanese (EUC encoding) + 日文(Japanese，編碼方式：EUC) ru_RU.KOI8-R - Russian (KOI8-R encoding) + 俄文(Russian，編碼方式：KOI8-R) zh_TW.Big5 - Chinese (Big5 encoding) + 正體中文(Chinese，編碼方式：Big5) - Some documents may not be available in all - languages. + 上列的各國翻譯語系文件中，並非所有文件都有翻譯。 - 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: + 文件的格式：每份文件都以各種不同格式儲存，每種格式都各有好壞， + 有些格式適合線上閱讀，而有些則適合列印出美觀的文件。 + 我們都提供這些不同格式的文件，來確保無論是螢幕上、列印紙本，每個人都可以正常地閱讀內容， + 目前可供使用的格式如下: - + - Format + 格式 - Meaning + 說明 @@ -646,47 +742,45 @@ html-split - A collection of small, linked, HTML - files. + 章節模式 html - One large HTML file containing the entire - document + 完整模式 pdb - Palm Pilot database format, for use with the - iSilo - reader. + Palm Pilot 資料格式，使用 + iSilo + 程式來閱讀 pdf - Adobe's Portable Document Format + Adobe's PDF 格式 ps - Postscript + &postscript; 格式 rtf - Microsoft's Rich Text Format - Page numbers are not automatically updated - when loading this format in to Word. Press - CTRLA, - CTRLEND, - F9 after loading the document, to - update the page numbers. + Microsoft's RTF格式 + 當使用 MS Word 來開啟 RTF 格式的話，頁數顯示並不會自動更新。 + (在開啟文件後，要按 CTRLA, + CTRLEND, + F9，這樣子才會更新頁數的顯示。) @@ -694,7 +788,7 @@ txt - Plain text + 純文字(ASCII) @@ -702,33 +796,31 @@ - The compression and packaging scheme. There are three of - these currently in use. + 文件的壓縮、打包方式：目前有三種方式： - Where the format is html-split, the - files are bundled up using &man.tar.1;. The resulting - .tar file is then compressed using - the compression schemes detailed in the next point. + 當採用 + 章節模式(html-split)，章節模式所產生的各檔案會先使用 + &man.tar.1; 來壓縮。檔名結尾有 .tar 的檔案就是 tar 格式。 + 接著，會再以下列方式再壓縮。 + - All the other formats generate one file, called - book.format - (i.e., book.pdb, - book.html, and so on). - - These files are then compressed using three - compression schemes. + 其他格式的檔案都會是單一檔案，檔名通常會是： + book.格式 + (舉例： book.pdb， + book.html 等等..後面通常加上『.格式』). + 而這些檔案會分別以兩種壓縮型態進行壓縮，而存成兩種壓縮型態。 - + - Scheme + 格式 - Description + 說明 @@ -736,166 +828,137 @@ zip - The Zip format. If you want to uncompress - this on FreeBSD you will need to install the - archivers/unzip port - first. - - - - gz - - The GNU Zip format. Use &man.gunzip.1; to - uncompress these files, which is part of - FreeBSD. + Zip 格式，若要在 FreeBSD 上解壓 zip 檔，則必須先安裝 + chinese/unzip 或 + archivers/unzip。 + bz2 - The BZip2 format. Less widespread than the - others, but generally gives smaller files. - Install the archivers/bzip2 - port to uncompress these files. + BZip2 格式，雖然不如 zip 格式的廣泛使用，但是好處在於可壓縮成更小的檔案。 + 要解壓 bz2 格式的話，需先安裝 archivers/bzip2 + 。 - So the Postscript version of the Handbook, compressed - using BZip2 will be stored in a file called - book.ps.bz2 in the - handbook/ directory. - - - - The formatted documentation is also available as a - FreeBSD package, of which more later. + 所以像是 Handbook 的 &postscript; 版格式，會以 BZip2 格式壓縮， + 存放在 handbook/ 目錄內， + 檔名就是book.ps.bz2。 - 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 - package. - - 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;. - - 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 - packages. Each package file looks like - document-name.lang.encoding.format.tgz. - - For example, the FAQ, in English, formatted as PDF, is in the - package called - faq.en_US.ISO8859-1.pdf.tgz. - - Knowing this, you can use the following command to install the - English PDF FAQ package. + 選擇想要下載的文件格式與壓縮型態之後，則要決定是否以 FreeBSD 套件(package) + 型態來下載。 + + 下載、安裝『package』的好處在於：可以透過一般 FreeBSD + 套件管理方式來進行管理，比如 &man.pkg.add.1; 及 + &man.pkg.delete.1;。 - &prompt.root; pkg_add ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/packages/faq.en_US.ISO8859-1.pdf.tgz - Having done that, you can use &man.pkg.info.1; to determine - where the file has been installed. + 若決定好要下載、安裝『package』的話，必須要確認所要下載的檔名。 + 文件計畫的套件(package)通常是放在是 packages 的目錄內， + 每個文件計畫的套件檔名通常是： + 文件名稱.語系.編碼.格式.tgz + 。 - &prompt.root; pkg_info -f faq.en_US.ISO8859-1.pdf -Information for faq.en_US.ISO8859-1.pdf: + 舉個例子，英文版的 FAQ (格式選擇 PDF)在 package 就叫做 + faq.en_US.ISO8859-1.pdf.tgz。 + + 再舉個例子，中文版的 FAQ (格式選擇 PDF)在 package 就叫做 + faq.zh_TW.Big5.pdf.tgz。 + + 知道這點之後，就可以用下面指令來安裝中文版 FAQ 套件： + + &prompt.root; pkg_add ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/packages/faq.zh_TW.Big5.pdf.tgz + + 完成之後，可以用 &man.pkg.info.1; 來找出檔案裝在哪邊： + + &prompt.root; pkg_info -f faq.zh_TW.Big5.pdf +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) - As you can see, book.pdf will have been - installed in to - /usr/share/doc/en_US.ISO8859-1/books/faq. - + 如同您所看到的 book.pdf 會被安裝到 + /usr/share/doc/zh_TW.Big5/books/faq 內。 - 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. - - For example, the split HTML version of the FAQ, compressed - using &man.gzip.1;, can be found in the - doc/en_US.ISO8859-1/books/faq/book.html-split.tar.gz - file. To download and uncompress that file you would have to do - this. + 若不想用 package 方式安裝，那麼就需手動下載、解壓縮、複製到你想要擺放的位置去。 - &prompt.root; fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/faq/book.html-split.tar.gz -&prompt.root; gzip -d book.html-split.tar.gz + 舉例，章節模式(split HTML)版的英文 FAQ (壓縮為 &man.bzip2.1;)會放在 + doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2 + 要下載、解壓的話，則要打： + + &prompt.root; fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2 +&prompt.root; bzip2 -d book.html-split.tar.bz2 &prompt.root; tar xvf book.html-split.tar - You will be left with a collection of - .html files. The main one is called - index.html, 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. + 這時你會看到一堆 .html 的檔案， + 主要的目錄檔為 index.html + 內含主目錄及連結到其他文件。(若有需要的話，也可以複製或搬移這些檔案到同一目錄下) - Where do I find info on the FreeBSD mailing lists? + 哪裡有關於 FreeBSD 的郵遞論壇(mailing lists)呢？ - You can find full information in the Handbook - entry on mailing-lists. + 這個問題，可以從《 FreeBSD 使用手冊》上面的 郵遞論壇(mailing-lists) + 部分獲得答案。 - Where do I find the FreeBSD Y2K info? + 我該從哪邊得到有關 FreeBSD 在千禧蟲(Y2K)方面的資料呢? - You can find full information in the FreeBSD Y2K - page. + 這答案可以在 FreeBSD 千禧蟲(Y2K)上面獲得 - What FreeBSD news groups are available? + 有哪些可以使用的 FreeBSD 新聞群組(news groups)呢? - You can find full information in the Handbook entry on - newsgroups. + 這答案可以從《 FreeBSD 使用手冊》上面的 新聞群組(newsgroups) + 部分獲得答案。 - Are there FreeBSD IRC (Internet Relay Chat) - channels? + 有哪些 FreeBSD IRC (Internet Relay Chat)頻道呢？ - Yes, most major IRC networks host a FreeBSD chat - channel: + 有的，大部分的 IRC 主機都有 FreeBSD 聊天頻道： Channel #FreeBSD on - EFNet + EFNet 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 @@ Channel #FreeBSDhelp on - EFNet + EFNet is a channel dedicated to helping FreeBSD users. They - are much more sympathetic to questions then + are much more sympathetic to questions than #FreeBSD is. Channel #FreeBSD on - DALNET + DALNET is available at irc.dal.net in the US and irc.eu.dal.net in Europe. + Channel #FreeBSDHelp on + DALNET + is available at irc.dal.net in the + US and irc.eu.dal.net in Europe. + The channel owners also have a web page with useful + information about the channel and &os;, available at + . + + + Channel #FreeBSD on - UNDERNET + UNDERNET is available at us.undernet.org in the US and eu.undernet.org in Europe. Since it is a help channel, be prepared to read the documents you are referred to. - - - Channel #FreeBSD on HybNet. This channel - is a help channel. A list of servers - can be found on the HybNet web site. - Each of these channels are distinct and are not @@ -948,26 +1013,21 @@ - Where can I get commercial FreeBSD training and support? + 可以從哪邊獲得 FreeBSD 的商業課程訓練及技術支援呢？ - DaemonNews provides commercial training and support for - FreeBSD. More information can be found at their - BSD Mall - site. - - FreeBSD Services Ltd provide commercial support for FreeBSD - in the UK (as well as selling FreeBSD on DVD). See their - web site - for more information. - - The FreeBSD Mall provides commercial FreeBSD support. - You can get more information at their web site. + DaemonNews 有專門提供 FreeBSD 的商業課程訓練及技術支援。 + 詳情請到 BSD Mall + 察看，謝謝。 + + FreeBSD Mall 有提供商業化的 BSD 技術支援， + 詳情請到 FreeBSD Mall 察看，謝謝。 + - Any other organizations providing training and support should - contact the project in order to be listed here. + 其他任何有提供課程訓練及技術支援的組織、單位，若也想列表於此的話， + 請與 &a.doc; 聯絡，謝謝。 @@ -985,33 +1045,30 @@ - Installation + 安裝 - Which file do I download to get FreeBSD? + 若要用軟碟片開機來安裝 FreeBSD 的話，要下載哪些檔案呢？ - Prior to release 3.1, you only needed one floppy image to - install FreeBSD, namely floppies/boot.flp. - 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: - floppies/kernel.flp and - floppies/mfsroot.flp. These images need to - be copied onto floppies by tools like - fdimage or &man.dd.1;. - - If you need to download the distributions yourself (for a - DOS filesystem install, for instance), below are some - recommendations for distributions to grab: + &os; 4.X 的話，需要兩個 image 檔： + floppies/kernel.flp 及 + floppies/mfsroot.flp。image 檔必須用工具像是 + fdimage 或 &man.dd.1; 來傳送到磁片上。 + 若是在 &os; 5.3 (及之後版本)有重新規劃開機片架構，所以要抓的是 + floppies/boot.flp 以及 floppies/kernX + 檔案(目前 X 為 1 跟 2 兩個，加上floppies/boot.flp，總共是 3 個檔案)。 + + 若想自己下載 distributions 的話(比如以 &ms-dos; 檔案系統格式安裝)， + 以下是建議要抓的 distributions ： - bin/ + base/ (bin/ in 4.X) @@ -1032,61 +1089,50 @@ - Full instructions on this procedure and a little bit more - about installation issues in general can be found in the - Handbook entry on - installing FreeBSD. + 完整安裝步驟以及大部分的安裝問題，請參閱《 FreeBSD 使用手冊》的 + 安裝 FreeBSD 章節 - What do I do if the floppy images does not fit on a single - floppy? + 若磁片裝不下 image 檔的話，該怎麼辦呢？ - A 3.5 inch (1.44MB) floppy can accommodate 1474560 bytes - of data. The boot image is exactly 1474560 bytes in size. + 一張 3.5 英吋(1.44MB) 的磁碟片是可以裝上 1474560 bytes 的資料 + ，而開機片的 image 檔案大小實際上也是 1474560 bytes。 - Common mistakes when preparing the boot floppy are: + 在製作開機片時，常見錯誤有： - Not downloading the floppy image in - binary mode when using - FTP. - - - Some FTP clients default their transfer mode to - ascii 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 exactly that - on the server, then the download process is suspect. - - To workaround: type binary at the - FTP command prompt after getting connected to the server - and before starting the download of the image. + 使用 FTP 來下載檔案時， + 未選擇 binary 傳輸模式來下載。 + + + 有些 FTP client端程式，是預設將傳輸模式設定為 + ascii 模式，而且會修改接收到的檔案行尾字串為 client 端的作業系統方式 + ，比如 newline(&unix;格式) 到了作業系統為 &windows; 的 client 端會被改為 CR-LF(&ms-dos;格式)， + 這會使得 image 檔本身遭到修改而無法正常使用。因此，如果下載的 image + 檔案大小若與 FTP 主機上面的檔案 不一致 + 的話，請重新使用 binary 傳輸模式下載即可。 + + FTP 指令: 進入 FTP 之後，打 binary + 指令，即可切換到 binary 傳輸模式，然後再下載相關 image 檔案。 - Using the DOS copy command (or - equivalent GUI tool) to transfer the boot image to - floppy. - - Programs like copy 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 - raw, using the low-level tools (e.g. - fdimage or rawrite) - described in the installation guide to - FreeBSD. + 直接用 &ms-dos; 的 copy 指令(或類似 + 的 GUI 程式、或是視窗上直接複製)來複製開機用的 image 檔到磁片上。 + + + 不可以用像是 copy 這類程式直接將 image + 檔複製到磁片上，因為 image 檔本身包含了完整的磁軌資料，所以不能單純用複製方式， + 而必須使用低階工具程式(像是 fdimage 或 rawrite)， + 以 raw 方式傳送到磁片上。(這部分可參閱《 FreeBSD 使用手冊》上的 安裝 FreeBSD) @@ -1094,162 +1140,139 @@ - Where are the instructions for installing FreeBSD? + 可以在哪邊找到安裝 FreeBSD 的解說步驟呢？ - Installation instructions can be found in the - Handbook entry on installing FreeBSD. + 安裝步驟的解說，請參閱《 FreeBSD 使用手冊》上的 + 安裝 FreeBSD 章節部分。 - What do I need in order to run FreeBSD? + 要跑 FreeBSD 需要什麼的配備呢？ - 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. + &os; 5.X 之前的版本，硬體需求為 386 或更高級的 PC + ，記憶體(RAM)至少要 5 MB 或更多，硬碟空間至少要 60 MB 或更多。 + 不過，&os; 『系統安裝程式』的記憶體(RAM)需求為至少 16 MB。 + + 從 &os; 5.X 起，硬體需求為 486 或更高級的 PC + ，記憶體(RAM)至少要 24 MB 或更多，硬碟空間至少要 150 MB 或更多。 + - See also - + &os; 的所有版本都可以只用低階的 MDA 規格顯示卡，不過…要跑 X11R6 視窗的話， + 還是至少用 VGA 或更好規格的顯示卡來用吧。 + + 這部分也可參閱 。 - I have only 4 MB of RAM. Can I install FreeBSD? + 我電腦 RAM 只有 4MB 而已，可以裝 FreeBSD 嗎？ - 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. - - All versions of FreeBSD will run - 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. - - FreeBSD 2.1.7 will not install with 640 kB base + 3 MB - extended memory. If your motherboard can remap some of the - lost 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 - remap 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 upgrade option of the 2.1.7 - installation program. - - 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. + 安裝 &os; 4.X 的記憶體需求為至少 5 MB ，而 + 安裝 &os; 5.X (含之後版本) 則是至少要 8 MB 。 + + 在 5.X 之前的所有 &os; 版本，都可以只用 4 MB 的記憶體來 + 『運作』，不過，前面那節我們說過了『系統安裝程式』的話， + 則無法只用 4 MB 的記憶體來執行。因此，你可以先在『系統安裝程式』這步驟之前， + 先將記憶體加到 16 MB 以上，安裝完 FreeBSD 之後，就可以把多餘的記憶體拿下來。 + 或者是，先把要安裝的硬碟拿到有足夠記憶體的機器上先裝好， + 然後再把硬碟放回原機器。 + + 此外，只用 4 MB 的記憶體來運作的話，必須要自製 kernel(拿掉不必要的以及犧牲一些東西)。 + 也有人的 &os 成功只用 2 MB 的記憶體來開機(雖然這樣的系統幾乎等於廢了..) - How can I make my own custom install floppy? + 要怎樣才能自行打造專用的開機、安裝磁片呢？ - Currently there is no way to just - make a custom install floppy. You have to cut a whole new - release, which will include your install floppy. + 目前，還沒有辦法『只』自製專用的開機、安裝磁片。 + 必須透過自行打造完整作業系統的 release(發行)，這樣裡面才會包括自己的開機、安裝磁片。 - To make a custom release, follow the instructions in the - Release - Engineering article. + 若想自行打造、發行(release)一個完整的作業系統，請參閱這篇 + Release Engineering 文章。 - Can I have more than one operating system on my PC? + 我電腦上可以有多重作業系統嗎？ - Have a look at - - the multi-OS page. + 可以呀，請參閱 + + 多重作業系統 這篇文章。 - Can Windows 95/98 co-exist with FreeBSD? + &windows; 可以與 FreeBSD 共存於電腦上嗎？ - 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. + 先裝 &windows; 再裝 FreeBSD。 + 那麼 FreeBSD 開機管理員(boot manager)就會出現選單讓你選擇要以 &windows; 或 + FreeBSD 來開機。不過，若你是先裝 FreeBSD 再裝 &windows; 的話， + 那麼 &windows; 將會不問先宰，把 FreeBSD 的開機管理員(boot manager)蓋掉， + 當你遇上這種情況時，請參考下一節說明。 - Windows 95/98 killed my boot manager! - How do I get it back? + 嗚∼&windows; 把我的開機管理員(boot manager)拿掉了！我要怎麼救回來呢？ - You can reinstall the boot manager FreeBSD comes with in - one of three ways: + 可以用以下三種方式之一，來救回你的 FreeBSD 開機管理員(boot manager)： - Running DOS, go into the tools/ directory of your - FreeBSD distribution and look for - bootinst.exe. You run it like - so: + 可以從各 FreeBSD FTP 站的 /pub/FreeBSD/tools/ + 找到 bootinst.exe 及 boot.bin 這兩個檔， + 以 binary 傳輸模式下載後，複製到磁片上，再用 DOS 開機片開機， + 接著打類似下面的指令： - ...\TOOLS> bootinst.exe boot.bin + > bootinst.exe boot.bin - and the boot manager will be reinstalled. + 這樣開機管理員(boot manager)就會重裝完畢了。 - 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 Boot Manager. This will - re-write the boot manager to disk. Now quit out of the - installation menu and reboot off the hard disk as - normal. + 用 FreeBSD 開機片開機，然後選單那邊選 Custom installation(自訂安裝)， + 再選 Partition，接著選擇你要裝開機管理員(boot manager)的硬碟(通常是第一顆)， + 然後會出現 partition editor 的畫面，這時請不要做任何修改，直接按 W 儲存， + 這時程式就會問是否要確定 Write ，最後出現 Boot Manager 選擇畫面， + 記得要選 Boot Manager ，這樣就會重新將開機管理員(boot manager) + 安裝到硬碟上。現在，就大功告成可以離開安裝選單並重開機了。 - Boot the FreeBSD boot floppy (or CDROM) and choose the - Fixit menu item. Select either the Fixit - floppy or CDROM #2 (the live file system - option) as appropriate and enter the fixit shell. Then - execute the following command: + 用 FreeBSD 開機片或是開機光碟開機，然後選單那邊選 Fixit + ，或是以 Fixit 開機片或是光碟安裝的第二片(選擇 live filesystem + 選項)然後就會進入 fixit shell 了，接著打下列指令： Fixit# fdisk -B -b /boot/boot0 bootdevice - substituting bootdevice for - your real - boot device such as ad0 (first IDE - disk), ad4 (first IDE disk on - auxiliary controller), da0 (first - SCSI disk), etc. + 請將上面的 bootdevice 修改為您實際的開機硬碟代號 + 比如 ad0 (第一顆 IDE 硬碟) + ，或是ad4 (first IDE disk on + auxiliary controller), da0 (第一顆 + SCSI 硬碟)等等…。 @@ -1257,59 +1280,55 @@ - My A, T, or X series IBM Thinkpad locks up when I first - booted up my FreeBSD installation. How can I solve this? + 當裝完 FreeBSD 之後重開機，我的 IBM Thinkpad A系列、T系列或 X系列的筆記型電腦就趴了，該怎麼辦呢？ - 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. + 這些 IBM 機器上的 BIOS 早期版本有個臭蟲(bug)會把 FreeBSD 分割區誤認為 + FAT 格式分割區，然後當 BIOS 試著偵測 FreeBSD 分割區時，就會趴了。 - According to IBMIn an e-mail from Keith - Frechette - kfrechet@us.ibm.com., the - following model/BIOS release numbers incorporate the fix. + 根據 IBM 方面的說法一封來自 Keith + Frechette 的 e-mail kfrechet@us.ibm.com。 + ，以下型號/BIOS版本的機種，已經都有修正： - + - Model - BIOS revision + 型號 + BIOS 版本 T20 - IYET49WW or later + IYET49WW(含之後) T21 - KZET22WW or later + KZET22WW(含之後) A20p - IVET62WW or later + IVET62WW(含之後) A20m - IWET54WW or later + IWET54WW(含之後) A21p - KYET27WW or later + KYET27WW(含之後) A21m - KXET24WW or later + KXET24WW(含之後) @@ -1320,14 +1339,15 @@ - It has been reported that later IBM BIOS revisions may have - reintroduced the bug. This message - 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.. + It has been reported that later IBM BIOS revisions may + have reintroduced the bug. This + message 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. - If you have an earlier BIOS, and upgrading is not an option a + 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. @@ -1350,7 +1370,7 @@ Download boot1 and boot2 from http://people.FreeBSD.org/~bmah/ThinkPad/. + url="http://people.FreeBSD.org/~bmah/ThinkPad/">. Put these files somewhere you will be able to retrieve them later. @@ -1406,176 +1426,86 @@ - Can I install on a disk with bad blocks? - - - - Prior to 3.0, FreeBSD included a utility known as - bad144, which automatically remapped bad - blocks. Because modern IDE drives perform this function - themselves, bad144 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. - 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. - - If you have a SCSI drive with bad blocks, see - this answer. - - - - - - I have just upgraded from 3.X to 4.X, and my first boot - failed with bad sector table not - supported - - - - FreeBSD 3.X and earlier supported - bad144, which automatically remapped - bad blocks. FreeBSD 4.X and later do not support this, as - modern IDE drives include this functionality. See this question for - more information. - - 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. - - - - - - How do I tell if a drive has bad144 - information on it before I try to upgrade to FreeBSD 4.0 - and it fails? + 有壞軌的硬碟可以拿來裝 FreeBSD 嘛？ - Use &man.disklabel.8; for this. disklabel -r - drive device will - give you the contents of your disk label. Look for a - flags field. If you see - flags: badsect, this drive is using - bad144. For example, the following drive has - bad144 enabled.: - - &prompt.root; disklabel -r wd0 -# /dev/rwd0c: -type: ESDI -disk: wd0s1 -label: -flags: badsect -bytes/sector: 512 -sectors/track: 63 - - - - - - How do I remove bad144 from my - pre-4.X system so I can upgrade safely? - + (如果很堅持的話)也是可以，不過這想法顯然不太好。:( - - Use disklabel -e -rwd0 to edit the - disklabel in place. Just remove the word - badsect 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. + 如果在一般較新的 IDE 硬碟上看到有壞軌，很有可能代表：這顆硬碟即將掛點了。 + (因為目前所有較新的 IDE 硬碟，內部都有自動 remapping 壞軌的能力。 + 如果看到有壞軌，則表示它內部自動 remapping 功能失效，無法處理壞軌， + 也就是說這顆硬碟已經是嚴重損壞程度了。)我們建議買顆新硬碟比較乾脆些唷。 - We still recommend you purchase a new disk if you have - a large number of bad blocks. + 如果是 SCSI 硬碟有壞軌的話，請試著參考這個 + 解法。 - Strange things happen when I boot the install floppy! - What is happening? + 用安裝磁片開機時，卻有些怪現象發生！這是什麼情況呢？ - 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:- + 若看到一些怪異現象，像是開機片開機開到一半就當了，磁碟機完全沒任何動作、 + 或是不斷反覆重開機，請先檢查以下幾個線索： - 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)? + 請確定是否為全新、沒有磁軌錯誤的磁片？ + (最好使用新買的，而非雜誌、書本附贈的，甚至還藏在床底下三年了...) - 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!) + 請確定是否有用 binary(或image)傳輸模式來下載 image 檔？ + (不用覺得不好意思，即使是我們也曾意外以 ASCII 傳輸模式來下載 binary 檔案！) - If you are using Windows95 or Win98 did you run - fdimage or rawrite 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. + 若你是 &windows; 95/98/ME/NT/2000/XP/2003 來下載、製作開機磁片的話， + 請確定是否有在 DOS 模式使用 fdimage 或 + rawrite 這兩個工具程式？剛講的這些作業系統， + 都會影響程式去直接寫入硬體，像是製作開機片之類的動作。 + 有時候，在 GUI 介面上的 DOS shell 也可能會發生這樣的問題。 + - 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. + 此外，直接透過 &netscape; 瀏覽器下載 image 檔的話，也有類似現象。 + 所以，如果可以的話，請改用其他可以調整設定的 FTP client端程式來進行下載。 + (當然，要記得調 binary 傳輸模式) - I booted from my ATAPI CDROM, but the install program says no - CDROM is found. Where did it go? + 用光碟開機片來安裝，但光碟開機後，安裝程式說找不到光碟...這是怎麼了？ - 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. - - 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. + 通常問題在於光碟機設定錯誤。目前很多電腦的出廠標準配備都有光碟機，並且 + 會預先設定為 IDE 通道上面 Secondary 的 Slave 設備，而 Secondary 上面的 + 卻沒有 Master 設備。以 ATAPI 的規格而言，這是錯誤的設定，然而 &windows; 的作法 + 是不理會這些規格上的設定問題，而且開機時 BIOS 偵測也會略過這點。 + 這也就是為什麼 BIOS 可以看到光碟，並且可用光碟開機，但 FreeBSD + 無法正常抓到光碟以順利進行安裝。 + + 解法：重新設定系統，讓光碟成為它所連接那條 IDE 通道的 Master， + 或者只有一條 IDE 通道的話，那就讓光碟機成為 Slave + ，當然該 IDE 通道上至少要有 Master 設備。 - Can I install on my laptop over PLIP (Parallel Line - IP)? + 我可以用 PLIP(Parallel Line IP)方式來安裝 FreeBSD 到筆記型電腦上嗎？ - Yes. Use a standard Laplink cable. If necessary, you - can check out the PLIP - section of the Handbook for details on parallel - port networking. - - If you are running FreeBSD 3.X or earlier, also look at - the Mobile - Computing page. + 可以，用一條普通的 Laplink 線就可以囉。若有這方面需求的話，請參閱《 FreeBSD 使用手冊》中的 + PLIP + 章節 的細部設定 @@ -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. - + references. All that matters is the logical geometry. This is the answer that the BIOS gets when it @@ -1629,9 +1558,9 @@ If it is 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 (not - 64), and 255 heads, where 'M' is the disk capacity in MB + 64), and 255 heads, where M 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. @@ -1662,8 +1591,7 @@ - Yes. You must make sure that your root partition is below - 1024 + 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). @@ -1701,7 +1629,7 @@ - When I boot FreeBSD I get Missing Operating + When I boot FreeBSD for the first time after install I get Missing Operating System. What is happening? @@ -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 /usr/src directly, but rather in some other location with appropriate symbolic links to duplicate the top-level structure of the source - tree.) + tree). 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 @@ 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 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. + 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. - It is still recommended that you eventually build a new + 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. @@ -1786,28 +1716,31 @@ - Should I use DES, Blowfish, or MD5 passwords and how do I specify - which form my users receive? + Should I use DES, Blowfish, or MD5 passwords and how + do I specify which form my users receive? The default password format on FreeBSD is to use - MD5-based passwords. These are believed to - be more secure than the traditional Unix password format, which - used a scheme based on the DES 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 + MD5-based passwords. These are + believed to be more secure than the traditional &unix; + password format, which used a scheme based on the + DES 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 crypto 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 passwd_format login capability - in /etc/login.conf, which takes values of - des, blf (if these are available) or md5. - See the &man.login.conf.5; manual page for more information about login - capabilities. + 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 + passwd_format login capability in + /etc/login.conf, which takes values + of des, blf (if these are + available) or md5. See the + &man.login.conf.5; manual page for more information about + login capabilities. @@ -1819,7 +1752,7 @@ - If you have a IDE Zip or Jaz drive installed, remove it + 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. @@ -1833,79 +1766,57 @@ - 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 + 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. To fix the problem, do one of the following: - For FreeBSD 3.3 and later, reboot the system and hit - Enter at the Booting kernel - in 10 seconds; hit [Enter] to interrupt prompt. - This will drop you into the boot loader. + Reboot the system and hit Enter + at the Booting kernel in 10 seconds; hit + [Enter] to interrupt prompt. This will + drop you into the boot loader. Then type - set root_disk_unit="disk_number" + set + root_disk_unit="disk_number" . disk_number - will be 0 if FreeBSD is installed on - the master drive on the first IDE controller, - 1 if it is installed on the slave on - the first IDE controller, 2 if it is - installed on the master of the second IDE controller, and - 3 if it is installed on the slave of - the second IDE controller. - - Then type boot, and your system - should boot correctly. - - 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 - root_disk_unit="disk_number" in /boot/loader.conf.local + will be 0 if FreeBSD is installed + on the master drive on the first IDE controller, + 1 if it is installed on the slave + on the first IDE controller, 2 if + it is installed on the master of the second IDE + controller, and 3 if it is + installed on the slave of the second IDE + controller. + + Then type boot, and your + system should boot correctly. + + 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 + root_disk_unit="disk_number" + in /boot/loader.conf.local . - If using FreeBSD 3.2 or earlier, at the Boot: prompt, - enter 1:wd(2,a)kernel and press Enter. - If the system starts, then run the command - echo "1:wd(2,a)kernel" > /boot.config - to make it the default boot string. - - - - Move the FreeBSD disk onto the primary IDE controller, - so the hard disks are consecutive. - - - - Rebuild - your kernel, modify the wd configuration lines to - read: - - 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 - - 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. + Move the FreeBSD disk onto the primary IDE + controller, so the hard disks are + consecutive. @@ -1917,14 +1828,19 @@ - For memory, the limit is 4 gigabytes. This configuration - has been tested, see wcarchive's - configuration 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. + 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: + + options PAE + + &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). @@ -1941,20 +1857,16 @@ exist). The maximum size of a single ffs file is approximately 1G - blocks (4TB) if the block size is 4K. + blocks, or 4TB with a block size of 4K. Maximum file sizes - + fs block size - 2.2.7-stable - - 3.0-current - works should work @@ -1967,10 +1879,6 @@ 4T-1 - 4T-1 - - 4T-1 - >4T @@ -1979,10 +1887,6 @@ >32G - 8T-1 - - >32G - 32T-1 @@ -1991,10 +1895,6 @@ >128G - 16T-1 - - >128G - 32T-1 @@ -2003,10 +1903,6 @@ >512G - 32T-1 - - >512G - 64T-1 @@ -2015,10 +1911,6 @@ >2048G - 64T-1 - - >2048G - 128T-1 @@ -2035,14 +1927,10 @@ size is 4K.For block sizes of 8K and larger, everything should be - limited by the 2G-1 limit on fs block numbers, but is actually - limited by the 1G-1 limit on fs block numbers, except under - -STABLE triple indirect blocks are unreachable, so the limit is - the maximum fs block number that can be represented using - double indirect blocks (approx. (blocksize/4)^2 + - (blocksize/4)), and under -CURRENT exceeding this limit may - cause problems. Using the correct limit of 2G-1 blocks does - cause problems. + limited by the 2G-1 limit on fs block numbers, but is + actually limited by the 1G-1 limit on fs block numbers. + Using the correct limit of 2G-1 blocks does cause + problems. @@ -2055,44 +1943,14 @@ - You can boot by specifying the kernel directly at the second - stage, pressing any key when the | shows up before loader is - started. More specifically, you have upgraded the source for - your kernel, and installed a new kernel builtin from them - without making world. This is not - supported. Make world. - - - - - - How do I upgrade from 3.X -> 4.X? - - - - We strongly recommend that you use - binary snapshots to do this. 4-STABLE snapshots are available at - ftp://releng4.FreeBSD.org/. - - Because of the many changes between 3.X and 4-STABLE, - a direct upgrade from source will probably fail. A source - upgrade can be done, but only in stages. First, upgrade - to the latest 3-STABLE (RELENG_3). - Then upgrade to 4.1.1-RELEASE - (RELENG_4_1_1_RELEASE). Finally, - upgrade to 4-STABLE (RELENG_4). - - If you wish to upgrade using source, please see the FreeBSD - Handbook for more information. - - - Upgrading via source is never recommended for new - users, and upgrading from 3.X to 4.X is even less so; make sure - you have read the instructions carefully before attempting to - upgrade via source. - + Because your world and kernel are out of synch. This + is not supported. Be sure you use make + buildworld and make + buildkernel to update your kernel. + + You can boot by specifying the kernel directly at the + second stage, pressing any key when the | shows up before + loader is started. @@ -2106,9 +1964,9 @@ options that attempts to achieve the desired ratio of security to convenience by enabling and disabling certain programs and other settings. For full details, see the Security + url="&url.books.handbook;/install-post.html#SECURITYPROFILE">Security Profile section of the Handbook's post-install + url="&url.books.handbook;/install-post.html">post-install chapter. @@ -2119,31 +1977,10 @@ id="hardware"> Hardware compatibility - - - - Does FreeBSD support architectures other than the - x86? - - - - - Yes. FreeBSD currently runs on both Intel x86 and - DEC (now Compaq) Alpha architectures. Interest has also - been expressed in a port of FreeBSD to the SPARC architecture, - join the &a.sparc; if you are interested in joining that project. - Most recent additions to the list of upcoming platforms are - IA-64 and PowerPC, join the &a.ia64; and/or the &a.ppc; for more - information. For general discussion on new architectures, join - the &a.platforms;. - - If your machine has a different architecture and you need - something right now, we suggest you look at NetBSD or OpenBSD. - - + + General + I want to get a piece of hardware for my FreeBSD @@ -2154,10 +1991,12 @@ This is discussed continually on the FreeBSD mailing lists. Since hardware changes so quickly, however, we expect this. We still strongly - recommend that you read through the - Hardware Notes + recommend that you read through the Hardware notes for &os; + &rel.current; + or + &rel2.current; and search the mailing list - + archives before asking about the latest and greatest hardware. Chances are a discussion about the type of hardware you are looking for took place just last @@ -2171,6 +2010,66 @@ + + + + + Architectures and processors + + + + + Does FreeBSD support architectures other than the x86? + + + + + Yes. FreeBSD currently runs on the Intel x86 and DEC + (now Compaq) Alpha architectures. As of FreeBSD 5.0, the + AMD64 and Intel EM64T, IA-64, and &sparc64; architectures + are also supported. Upcoming platforms are &mips; and + &powerpc;, join the &a.ppc; or the &a.mips; respectively + for more information about ongoing work on these + platforms. For general discussion on new architectures, + join the &a.platforms;. + + If your machine has a different architecture and you + need something right now, we suggest you look at NetBSD or OpenBSD. + + + + + + Does FreeBSD support Symmetric Multiprocessing + (SMP)? + + + + Yes. SMP was enabled by default in the + GENERIC kernel as of &os; 5.2. + + The intention was also to enable it by default for + the &os; 5.3 release, but problems running the SMP kernel + on certain UP machines led to the decision to disable it + until those problems can be addressed. This is a priority + for &os; 5.4. + + In &os; 4.X, SMP is not enabled in the default kernel, + so you must recompile your kernel to enable SMP. Take a + look at /sys/i386/conf/LINT to learn + which options to put in your kernel config file. + + + + + + + Hard drives, tape drives, and CD and DVD drives + + + What kind of hard drives does FreeBSD support? @@ -2192,8 +2091,44 @@ - See the complete list in the current Hardware Notes. + See the complete list in the Hardware Notes for &os; + &rel.current; or + &rel2.current;. + + + + + + What types of tape drives are supported? + + + + + FreeBSD supports SCSI and QIC-36 (with a QIC-02 interface). + This includes 8-mm (aka Exabyte) and DAT drives. + + Some of the early 8-mm drives are not quite compatible + with SCSI-2, and may not work well with FreeBSD. + + + + + + Does FreeBSD support tape changers? + + + + FreeBSD supports SCSI changers using the &man.ch.4; + device and the &man.chio.1; command. The details of how you + actually control the changer can be found in the &man.chio.1; + manual page. + + If you are not using AMANDA + or some other product that already understands changers, + remember that they only know how to move a tape from one + point to another, so you need to keep track of which slot a + tape is in, and which slot the tape currently in the drive + needs to go back to. @@ -2235,8 +2170,9 @@ All non-SCSI cards are known to be extremely slow compared to SCSI drives, and some ATAPI CDROMs may not work. - As of 2.2 the FreeBSD CDROM from the FreeBSD Mall supports - booting directly from the CD. + The official FreeBSD CDROM ISO, and CDROMs from Daemon + News and FreeBSD Mall, support booting directly from the + CD. @@ -2247,9 +2183,7 @@ FreeBSD supports any ATAPI-compatible IDE CD-R or CD-RW - drive. For FreeBSD versions 4.0 and later, see the man page for - &man.burncd.8;. For earlier FreeBSD versions, see the examples - in /usr/share/examples/atapi. + drive. See &man.burncd.8; for details. FreeBSD also supports any SCSI CD-R or CD-RW drives. Install and use the cdrecord command from the @@ -2261,80 +2195,72 @@ - Does FreeBSD support ZIP drives? + Does FreeBSD support &iomegazip; drives? - FreeBSD supports the SCSI ZIP drive out of the box, of - course. The ZIP drive can only be set to run at SCSI target IDs - 5 or 6, but if your SCSI host adapter's BIOS supports it you - can even boot from it. It is not clear which host - adapters support booting from targets other than 0 or 1, - so you will have to consult your adapter's documentation - if you would like to use this feature. - - ATAPI (IDE) Zip drives are supported in FreeBSD 2.2.6 and - later releases. - - FreeBSD has contained support for Parallel Port Zip Drives - since version 3.0. If you are using a sufficiently up to date - version, then you should check that your kernel contains the - scbus0, da0, + FreeBSD supports SCSI and ATAPI (IDE) &iomegazip; drives out + of the box. SCSI ZIP drives can only be set to + run at SCSI target IDs 5 or 6, but if your SCSI host + adapter's BIOS supports it you can even boot from it. It + is not clear which host adapters support booting from + targets other than 0 or 1, so you will have to consult + your adapter's documentation if you would like to use this + feature. + + FreeBSD also supports Parallel Port Zip Drives. Check + that your kernel contains the + scbus0, + da0, ppbus0, and vp0 drivers (the GENERIC kernel - contains everything except vp0). With - all these drivers present, the Parallel Port drive should be - available as /dev/da0s4. Disks can be - mounted using mount /dev/da0s4 /mnt OR (for - dos disks) mount_msdos /dev/da0s4 /mnt as + contains everything except + vp0). With all these drivers + present, the Parallel Port drive should be available as + /dev/da0s4. Disks can be mounted + using mount /dev/da0s4 /mnt OR (for dos + disks) mount_msdos /dev/da0s4 /mnt as appropriate. - Also check out the FAQ on removable - drives later in this chapter, and the note on - formattingin the Administration chapter. + Also check out the FAQ on + removable drives later in this chapter, and the note on + formattingin the Administration + chapter. - Does FreeBSD support JAZ, EZ and other removable + Does FreeBSD support &jaz;, EZ and other removable drives? - Apart from the IDE version of the EZ drive, these are all - SCSI devices, so they should all look like SCSI disks to - FreeBSD, and the IDE EZ should look like an IDE drive. - - I am not sure how well FreeBSD supports - changing the media out while running. You will of course need - to dismount the drive before swapping media, and make sure that - any external units are powered on when you boot the system so - FreeBSD can see them. + They work. Most of these are SCSI devices, so they + look like SCSI disks to FreeBSD. The IDE EZ looks like an + IDE drive. + + Make sure that any external units are powered on when + booting the system. - See this note on - formatting. + To change the media while + running, check out &man.mount.8;, &man.umount.8;, and + &man.camcontrol.8; (for SCSI devices) or + &man.atacontrol.8; (for IDE devices), plus the discussion on using removable + drives later in the FAQ. - - - Which multi-port serial cards are supported by - FreeBSD? - + - - There is a list of these in the Miscellaneous - devices section of the handbook. + - Some unnamed clone cards have also been known to work, - especially those that claim to be AST compatible. + + Keyboards and mice - Check the &man.sio.4; - man page to get more information on configuring such cards. - - + @@ -2342,119 +2268,69 @@ - USB device support was added to FreeBSD 3.1. However, it - is still in preliminary state and may not always work as of - version 3.2. If you want to experiment with the USB keyboard - support, follow the procedure described below. + FreeBSD supports USB keyboards + out-of-the-box. Enable USB support in + /etc/rc.conf. - - - Use FreeBSD 3.2 or later. - + Once you have USB keyboard support enabled on your + system, the AT keyboard becomes + /dev/kbd0 and the USB keyboard + becomes /dev/kbd1, if both are + connected to the system. If there is the USB keyboard + only, it will be + /dev/ukbd0. - - Add the following lines to your kernel configuration - file, and rebuild the kernel. + If you want to use the USB keyboard in the console, + you have to explicitly tell the console driver to use the + existing USB keyboard. This can be done by running the + following command as a part of system + initialization. - device uhci -device ohci -device usb -device ukbd -options KBD_INSTALL_CDEV - - In versions of FreeBSD before 4.0, use this - instead: - - controller uhci0 -controller ohci0 -controller usb0 -controller ukbd0 -options KBD_INSTALL_CDEV - + &prompt.root; kbdcontrol -k /dev/kbd1 < /dev/ttyv0 > /dev/null - - Go to the /dev directory and create - device nodes as follows: + Note that if the USB keyboard is the only keyboard, it + is accessed as /dev/kbd0, thus, + the command should look like: - &prompt.root; cd /dev -&prompt.root; ./MAKEDEV kbd0 kbd1 + &prompt.root; kbdcontrol -k /dev/kbd0 < /dev/ttyv0 > /dev/null - - - - Edit /etc/rc.conf and add the - following lines: - - usbd_enable="YES" -usbd_flags="" - - - + /etc/rc.i386 is a good place to + add the above command. - After the system is rebooted, the AT keyboard becomes - /dev/kbd0 and the USB keyboard becomes - /dev/kbd1, if both are connected to the - system. If there is the USB keyboard only, it will be - /dev/ukbd0. + Once this is done, the USB keyboard should work in the + X environment as well without any special settings. - If you want to use the USB keyboard in the console, you - have to explicitly tell the console driver to use the existing - USB keyboard. This can be done by running the following - command as a part of system initialization. - - &prompt.root; kbdcontrol -k /dev/kbd1 < /dev/ttyv0 > /dev/null + Hot-plugging and unplugging of the USB keyboard may + not work quite right yet. We recommend connecting the + keyboard before starting the system and leaving it + connected until the system is shutdown to avoid + troubles. - Note that if the USB keyboard is the only keyboard, it is - accessed as /dev/kbd0, thus, the command - should look like: - - &prompt.root; kbdcontrol -k /dev/kbd0 < /dev/ttyv0 > /dev/null - - /etc/rc.i386 is a good place to add the - above command. - - Once this is done, the USB keyboard should work in the X - environment as well without any special settings. - - Hot-plugging and unplugging of the USB keyboard may not - work quite right yet. It is a good idea to connect the keyboard - before you start the system and leave it connected until the - system is shutdown to avoid troubles. - - See the &man.ukbd.4; man page for more information. + See the &man.ukbd.4; manual page for more information. - I have an unusual bus mouse. How do I set it up? + I have an unusual bus mouse. How do I set it + up? - FreeBSD supports the bus mouse and the InPort bus mouse - from such manufactures as Microsoft, Logitech and ATI. The bus - device driver is compiled in the GENERIC kernel by default in - FreeBSD versions 2.X, but not included in version 3.0 or later. - If you are building a custom kernel with the bus mouse driver, - make sure to add the following line to the kernel config - file - - In FreeBSD 3.0 or before, add: - - device mse0 at isa? port 0x23c tty irq5 vector mseintr - - In FreeBSD 3.X, the line should be: - - device mse0 at isa? port 0x23c tty irq5 - - And in FreeBSD 4.X and later, the line should read: + FreeBSD supports the bus mouse and the InPort bus + mouse from such manufacturers as Microsoft, Logitech and + ATI. The GENERIC kernel does not include the device + driver. To build a custom kernel with the bus mouse + driver, add the following line to the kernel config + file: device mse0 at isa? port 0x23c irq5 - Bus mice usually comes with dedicated interface cards. - These cards may allow you to set the port address and the IRQ - number other than shown above. Refer to the manual of your - mouse and the &man.mse.4; man page for more information. + Bus mice usually come with dedicated interface cards. + These cards may allow you to set the port address and the + IRQ number other than shown above. Refer to the manual of + your mouse and the &man.mse.4; manual page for more + information. @@ -2465,218 +2341,96 @@ - - If you are running a post-2.2.5 version of FreeBSD, the - necessary driver, psm, is included and - enabled in the kernel. The kernel should detect your PS/2 mouse - at boot time. - - If you are running a previous but relatively recent version - of FreeBSD (2.1.x or better) then you can simply enable it in - the kernel configuration menu at installation time, otherwise - later with at the boot: - prompt. It is disabled by default, so you will need to enable - it explicitly. - - If you are running an older version of FreeBSD then you will - have to add the following lines to your kernel configuration - file and compile a new kernel. - - In FreeBSD 3.0 or earlier, the line should be: - - device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr - - In FreeBSD 3.1 or later, the line should be: - - device psm0 at isa? tty irq 12 - - In FreeBSD 4.0 or later, the line should be: + The PS/2 mouse is supported out-of-the-box. The + necessary device driver, psm, is + included in the kernel. + + If your custom kernel does not have this, add the + following line to your kernel configuration and compile a + new kernel. device psm0 at atkbdc? irq 12 - See the Handbook entry on - configuring the kernel if you have no experience with - building kernels. - - Once you have a kernel detecting - psm0 correctly at boot time, make sure - that an entry for psm0 exists in - /dev. You can do this by typing: + Once the kernel detects psm0 + correctly at boot time, make sure that an entry for + psm0 exists in + /dev. You can create this entry by + typing: &prompt.root; cd /dev; sh MAKEDEV psm0 when logged in as root. - + + + You can omit this step if you are running FreeBSD + 5.0-RELEASE or newer with &man.devfs.5; enabled, + since the proper device nodes will be created automatically + under /dev. + + - Is it possible to make use of a mouse in any way outside - the X Window system? + Is it possible to use a mouse in any way outside the X + Window system? - If you are using the default console driver, syscons, you - can use a mouse pointer in text consoles to cut & paste - text. Run the mouse daemon, moused, and turn on the mouse - pointer in the virtual console: + If you are using the default console driver, + &man.syscons.4;, you can use a mouse pointer in text + consoles to cut & paste text. Run the mouse daemon, + &man.moused.8;, and turn on the mouse pointer in the + virtual console: &prompt.root; moused -p /dev/xxxx -t yyyy &prompt.root; vidcontrol -m on - Where xxxx is the mouse device - name and yyyy is a protocol type for - the mouse. See the &man.moused.8; man page for supported + Where xxxx is the mouse + device name and yyyy is a + protocol type for the mouse. The mouse daemon can + automatically determine the protocol type of most + mice, except old serial mice. Specify the + auto protocol to invoke automatic + detection. If automatic detection does not work, see the + &man.moused.8; manual page for a list of supported protocol types. - You may wish to run the mouse daemon automatically when the - system starts. In version 2.2.1, set the following variables in - /etc/sysconfig. - - mousedtype="yyyy" -mousedport="xxxx" -mousedflags="" - - In versions 2.2.2 to 3.0, set the following variables in - /etc/rc.conf. - - moused_type="yyyy" -moused_port="xxxx" -moused_flags="" - - In 3.1 and later, assuming you have a PS/2 mouse, all you - need to is add moused_enable="YES" to - /etc/rc.conf. - - In addition, if you would like to be able to use the mouse - daemon on all virtual terminals instead of just console at - boot-time, add the following to - /etc/rc.conf. - - allscreens_flags="-m on" - - Staring from FreeBSD 2.2.6, the mouse daemon is capable of - determining the correct protocol type automatically unless the - mouse is a relatively old serial mouse model. Specify - auto the protocol to invoke automatic - detection. + If you have a PS/2 mouse, just add + moused_enable="YES" to + /etc/rc.conf to start the mouse + daemon at boot-time. Additionally, if you would like to + use the mouse daemon on all virtual terminals instead of + just the console, add allscreens_flags="-m + on" to /etc/rc.conf. When the mouse daemon is running, access to the mouse - needs to be coordinated between the mouse daemon and other - programs such as the X Window. Refer to another section on this - issue. + must be coordinated between the mouse daemon and other + programs such as X Windows. Refer to the FAQ Why does my mouse not work with + X? for more details on this issue. - How do I cut and paste text with mouse in the text + How do I cut and paste text with a mouse in the text console? - Once you get the mouse daemon running (see - previous section), hold down the - button 1 (left button) and move the mouse to select a region of - text. Then, press the button 2 (middle button) or the button 3 - (right button) to paste it at the text cursor. - - In versions 2.2.6 and later, pressing the button 2 will - paste the text. Pressing the button 3 will - extend the selected region of text. If your - mouse does not have the middle button, you may wish to emulate - it or remap buttons using moused options. See the - &man.moused.8; man page for details. - - - - - - Does FreeBSD support any USB mice? - - - - - Preliminary USB device support was added to FreeBSD - 3.1. It did not always work through early versions of - 3.X. As of FreeBSD 4.0, USB devices should work out of - the box. If you want to experiment with the USB mouse - support under FreeBSD 3.X, follow the procedure described - below. - - - - Use FreeBSD 3.2 or later. - - - - Add the following lines to your kernel configuration - file, and rebuild the kernel. - - device uhci -device ohci -device usb -device ums - - In versions of FreeBSD before 4.0, use this - instead: - - controller uhci0 -controller ohci0 -controller usb0 -device ums0 - - - - Go to the /dev directory and - create a device node as follows: - - &prompt.root; cd /dev -&prompt.root; ./MAKEDEV ums0 - - - - Edit /etc/rc.conf and add the - following lines: - - moused_enable="YES" -moused_type="auto" -moused_port="/dev/ums0" -moused_flags="" -usbd_enable="YES" -usbd_flags="" - - See the previous section - for more detailed discussion on moused. - - - - In order to use the USB mouse in the X session, edit - XF86Config. If you are using XFree86 - 3.3.2 or later, be sure to have the following lines in the - Pointer section: - - Device "/dev/sysmouse" -Protocol "Auto" - - If you are using earlier versions of XFree86, be sure to - have the following lines in the Pointer - section: - - Device "/dev/sysmouse" -Protocol "SysMouse" - - - - Refer to another section - on the mouse support in the X environment. - - Hot-plugging and unplugging of the USB mouse may not work - quite right yet. It is a good idea connect the mouse before you - start the system and leave it connected until the system is - shutdown to avoid trouble. + Once you get the mouse daemon running (see the previous section), hold down the + button 1 (left button) and move the mouse to select a + region of text. Then, press the button 2 (middle button) + to paste it at the text cursor. Pressing button 3 (right + button) will extend the selected region of + text. + + If your mouse does not have a middle button, you may + wish to emulate one or remap buttons using mouse daemon + options. See the &man.moused.8; manual page for + details. @@ -2700,149 +2454,24 @@ - - Why does my wheel-equipped PS/2 mouse cause my mouse cursor - to jump around the screen? - - - - The PS/2 mouse driver psm in FreeBSD versions 3.2 or - earlier has difficulty with some wheel mice, including Logitech - model M-S48 and its OEM siblings. Apply the following patch to - /sys/i386/isa/psm.c and rebuild the - kernel. - - Index: psm.c -=================================================================== -RCS file: /src/CVS/src/sys/i386/isa/Attic/psm.c,v -retrieving revision 1.60.2.1 -retrieving revision 1.60.2.2 -diff -u -r1.60.2.1 -r1.60.2.2 ---- psm.c 1999/06/03 12:41:13 1.60.2.1 -+++ psm.c 1999/07/12 13:40:52 1.60.2.2 -@@ -959,14 +959,28 @@ - sc->mode.packetsize = vendortype[i].packetsize; - - /* set mouse parameters */ -+#if 0 -+ /* -+ * A version of Logitech FirstMouse+ won't report wheel movement, -+ * if SET_DEFAULTS is sent... Don't use this command. -+ * This fix was found by Takashi Nishida. -+ */ - i = send_aux_command(sc->kbdc, PSMC_SET_DEFAULTS); - if (verbose >= 2) - printf("psm%d: SET_DEFAULTS return code:%04x\n", unit, i); -+#endif - if (sc->config & PSM_CONFIG_RESOLUTION) { - sc->mode.resolution - = set_mouse_resolution(sc->kbdc, -- (sc->config & PSM_CONFIG_RESOLUTION) - 1); -+ (sc->config & PSM_CONFIG_RESOLUTION) - 1); -+ } else if (sc->mode.resolution >= 0) { -+ sc->mode.resolution -+ = set_mouse_resolution(sc->kbdc, sc->dflt_mode.resolution); -+ } -+ if (sc->mode.rate > 0) { -+ sc->mode.rate = set_mouse_sampling_rate(sc->kbdc, sc->dflt_mode.rate); - } -+ set_mouse_scaling(sc->kbdc, 1); - - /* request a data packet and extract sync. bits */ - if (get_mouse_status(sc->kbdc, stat, 1, 3) < 3) { - - Versions later than 3.2 should be all right. - - - - - How do I use the mouse/trackball/touchpad on my - laptop? + How do I use the mouse/trackball/touchpad on my laptop? Please refer to the answer to - the previous question. Also check out the Mobile - Computing page. - - - - - - What types of tape drives are supported? - - - - - FreeBSD supports SCSI and QIC-36 (with a QIC-02 interface). - This includes 8-mm (aka Exabyte) and DAT drives. - - Some of the early 8-mm drives are not quite compatible - with SCSI-2, and may not work well with FreeBSD. - - - - - - Does FreeBSD support tape changers? - - - - FreeBSD 2.2 supports SCSI changers using the - &man.ch.4; - device and the - &man.chio.1; - command. The details of how you actually control the changer - can be found in the - &man.chio.1; - man page. - - If you are not using AMANDA - or some other product that already understands changers, - remember that they only know how to move a tape from one - point to another, so you need to keep track of which slot a - tape is in, and which slot the tape currently in the drive - needs to go back to. + the previous question. - - - Which sound cards are supported by FreeBSD? - - - - FreeBSD supports the SoundBlaster, SoundBlaster Pro, - SoundBlaster 16, Pro Audio Spectrum 16, AdLib and Gravis - UltraSound sound cards. There is also limited support for - MPU-401 and compatible MIDI cards. Cards conforming to the - Microsoft Sound System specification are also supported through - the pcm driver. + - - This is only for sound! This driver does not support - CDROMs, SCSI or joysticks on these cards, except for the - SoundBlaster. The SoundBlaster SCSI interface and some - non-SCSI CDROMs are supported, but you cannot boot off this - device. - - - - - - - Workarounds for no sound from es1370 with pcm driver? - + - - You can run the following command every time the machine - booted up: + + Networking and serial devices - &prompt.root; mixer pcm 100 vol 100 cd 100 - - + @@ -2850,106 +2479,13 @@ - See the - Ethernet cards section of the handbook for a more + See the Hardware Notes supplied with each release of + FreeBSD for a more complete list. - - I do not have a math co-processor - is that bad? - - - - - This will only affect 386/486SX/486SLC owners - other - machines will have one built into the CPU. - - - In general this will not cause any problems, but there are - circumstances where you will take a hit, either in performance - or accuracy of the math emulation code (see the section on FP emulation). In particular, drawing - arcs in X will be VERY slow. It is highly recommended that you - buy a math co-processor; it is well worth it. - - - Some math co-processors are better than others. It - pains us to say it, but nobody ever got fired for buying - Intel. Unless you are sure it works with FreeBSD, beware of - clones. - - - - - - - What other devices does FreeBSD support? - - - - See the Handbook - for the list of other devices supported. - - - - - - - Does FreeBSD support power management on my laptop? - - - - FreeBSD supports APM on certain machines. Please look in - the LINT kernel config file, searching for - the - APM - keyword. Further information can be found in &man.apm.4;. - - - - - - - Why does my Micron system hang at boot time? - - - - 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. - - Disable the Plug and Play Operating System - flag in the BIOS to work around this problem. More information - can be found at - http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html#micron - - - - - - Why does FreeBSD not recognize my Adaptec SCSI - controller card? - - - - The newer AIC789x series Adaptec chips are supported under - the CAM SCSI framework which made its debut in 3.0. Patches - against 2.2-STABLE are in - ftp://ftp.FreeBSD.org/pub/FreeBSD/development/cam/. - A CAM-enhanced boot floppy is available at - http://people.FreeBSD.org/~abial/cam-boot/. - In both cases read the README before beginning. - - - - Why is FreeBSD not finding my internal Plug & Play modem? @@ -2980,8 +2516,7 @@ - Does FreeBSD support software modems, such as - Winmodems? + Does FreeBSD support software modems, such as Winmodems? @@ -2999,6 +2534,44 @@ + + Is there a native driver for the Broadcom 43xx cards? + + + + No, and there is not likely to be. + + Broadcom refuses to publically release programming + information for their wireless chipsets, most likely because + they use software controlled radios. In order to get FCC type + acceptance for their parts, they have to ensure that users + cannot arbitrarily set things like operating frequencies, + modulation parameters and power output. But without knowing + how to program the chipsets, it is nearly impossible to write + a driver. + + + + + + Which multi-port serial cards are supported by + FreeBSD? + + + + There is a list of these in the Miscellaneous + devices section of the handbook. + + Some unnamed clone cards have also been known to work, + especially those that claim to be AST compatible. + + Check the &man.sio.4; manual page to get more + information on configuring such cards. + + + + How do I get the boot: prompt to show on the serial console? @@ -3027,38 +2600,111 @@ + + + + + + Sound devices + + + - - Why does my 3Com PCI network card not work with my Micron - computer? + + Which sound cards are supported by FreeBSD? - 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. + &os; supports various sound cards including the &soundblaster;, + &soundblaster; Pro, &soundblaster; 16, Pro Audio Spectrum 16, + AdLib, and Gravis UltraSound sound cards (for more details, + see &os; Release Information + and the &man.snd.4; manual page). + There is also limited support for + MPU-401 and compatible MIDI cards. Cards conforming to the + µsoft; Sound System specification are also supported. - To work around this problem, disable the - Plug and Play Operating System flag in the - BIOS. + + This is only for sound! This driver does not support + CDROMs, SCSI or joysticks on these cards, except for the + &soundblaster;. The &soundblaster; SCSI interface and some + non-SCSI CDROMs are supported, but you cannot boot off this + device. + + + + + + + Workarounds for no sound from my &man.pcm.4; sound + card? + - More information on this problem is available at URL: - http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html#micron + + Some sound cards, such as the es1370, set their output + volume to 0 at every boot. Run the following command + every time the machine boots: + + &prompt.root; mixer pcm 100 vol 100 cd 100 + + + + + + Other hardware + + + - - Does FreeBSD support Symmetric Multiprocessing (SMP)? + + What other devices does FreeBSD support? - SMP is supported in 3.0-STABLE and later releases only. - SMP is not enabled in the GENERIC kernel, - so you will have to recompile your kernel to enable SMP. Take a - look at /sys/i386/conf/LINT to figure out - what options to put in your kernel config file. + See the Handbook + for the list of other devices supported. + + + + + + + Does FreeBSD support power management on my + laptop? + + + + FreeBSD 4.X and later support APM + on certain machines. Further information can be found in + &man.apm.4;. + + FreeBSD 5.X and later support the + ACPI features found in most modern + hardware. Further information can be found in + &man.acpi.4;. If a system supports both + APM and ACPI, either + can be used. We suggest you try both and choose the one + that best fits your needs. + + + + + + + Why does my Micron system hang at boot time? + + + + 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. + + Disable the Plug and Play Operating System + flag in the BIOS to work around this problem. @@ -3069,11 +2715,32 @@ - Go in to the BIOS setup and disable the boot virus + Go into the BIOS setup and disable the boot virus protection. + + + + Why does my &tm.3com; PCI network card not work with my Micron + computer? + + + + 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. + + To work around this problem, disable the + Plug and Play Operating System flag in the + BIOS. + + + + + @@ -5771,7 +5438,7 @@ Unmounting the device is simple: - &prompt.user; umount~/my-mount-point + &prompt.user; umount ~/my-mount-point Enabling vfs.usermount, 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 @@ --> + + + + 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 @@ + + + + &os; Glossary + This glossary contains terms and acronyms used within the &os; + community and documentation. + + + A + + + ACL + + + + + ACPI + + + + + AMD + + + + + AML + + + + + APIC + + + + + APM + + + + + APOP + + + + + ASL + + + + + ATA + + + + + ATM + + + + + ACPI Machine Language + AML + + Pseudocode, interpreted by a virtual machine within an + ACPI-compliant operating system, providing a + layer between the underlying hardware and the documented + interface presented to the OS. + + + + + ACPI Source Language + ASL + + The programming language AML is written in. + + + + + Access Control List + ACL + + + + + + + Advanced Configuration and Power Interface + ACPI + + 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. ACPI + evolves and supercedes the functionality provided previously by + APM, PNPBIOS and other technologies, and + provides facilities for controlling power consumption, machine + suspension, device enabling and disabling, etc. + + + + + Advanced Power Management + APM + + + + + + + Advanced Programmable Interrupt Controller + APIC + + + + + + + Advanced Technology Attachment + ATA + + + + + + + Asynchronous Transfer Mode + ATM + + + + + + + Authenticated Post Office Protocol + APOP + + + + + + + Automatic Mount Daemon + AMD + + A daemon that automatically mounts a filesystem when a file + or directory within that filesystem is accessed. + + + + + + B + + + BIND + + + + + BIOS + + + + + BSD + + + + + Basic Input/Output System + BIOS + + + + + + + Berkeley Internet Name Domain + BIND + + + + + + + Berkeley Software Distribution + BSD + + This is the name that the Computer Systems Research Group + (CSRG) at The University + of California at Berkeley + gave to their improvements and modifications to + AT&T's 32V &unix;. + &os; is a descendant of the CSRG work. + + + + + Bikeshed Building + + A phenomenon whereby many people will give an opinion on + an uncomplicated topic, whilst a complex topic receives little + or no discussion. See the + FAQ for + the origin of the term. + + + + + + C + + + CD + + + + + CHAP + + + + + CLIP + + + + + COFF + + + + + CPU + + + + + CTS + + + + + CVS + + + + + Carrier Detect + CD + + An RS232C signal indicating that a carrier has been + detected. + + + + + Central Processing Unit + CPU + + + + + + + Challenge Handshake Authentication Protocol + CHAP + + + + + + + Classical IP over ATM + CLIP + + + + + + + Clear To Send + CTS + + An RS232C signal giving the remote system + permission to send data. + + + + + Common Object File Format + COFF + + + + + + + Concurrent Versions System + CVS + + + + + + + + D + + + DAC + + + + + DDB + + + + + DES + + + + + DHCP + + + + + DNS + + + + + DSDT + + + + + DSR + + + + + DTR + + + + + DVMRP + + + + + Discretionary Access Control + DAC + + + + + + + Data Encryption Standard + DES + + + + + + + Data Set Ready + DSR + + + + + + + Data Terminal Ready + DTR + + + + + + + Debugger + DDB + + + + + + + Differentiated System Description Table + DSDT + + + + + + + Distance-Vector Multicast Routing Protocol + DVMRP + + + + + + + Domain Name System + DNS + + + + + + + Dynamic Host Configuration Protocol + DHCP + + + + + + + + E + + + ECOFF + + + + + ELF + + + + + ESP + + + + + Encapsulated Security Payload + ESP + + + + + + + Executable and Linking Format + ELF + + + + + + + Extended COFF + ECOFF + + + + + + + + F + + + FADT + + + + + FAT + + + + + FAT16 + + + + + FTP + + + + + File Allocation Table + FAT + + + + + + + File Allocation Table (16-bit) + FAT16 + + + + + + + File Transfer Protocol + FTP + + + + + + + Fixed ACPI Description Table + FADT + + + + + + + G + + + GUI + + + + + Giant + + The name of a mutual exclusion mechanism + (a sleep mutex) 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. + + + + + Graphical User Interface + GUI + + A system where the user and computer interact with + graphics. + + + + + + H + + + HTML + + + + + HUP + + + + + HangUp + HUP + + + + + + + HyperText Markup Language + HTML + + The markup language used to create web pages. + + + + + + I + + + I/O + + + + + IASL + + + + + IMAP + + + + + IP + + + + + IPFW + + + + + IPP + + + + + IPv4 + + + + + IPv6 + + + + + ISP + + + + + IP Firewall + IPFW + + + + + + + IP Version 4 + IPv4 + + + + + + + IP Version 6 + IPv6 + + + + + + + Input/Output + I/O + + + + + + + Intel’s ASL compiler + IASL + + Intel’s compiler for converting ASL into + AML. + + + + + Internet Message Access Protocol + IMAP + + + + + + + Internet Printing Protocol + IPP + + + + + + + Internet Protocol + IP + + + + + + + Internet Service Provider + ISP + + + + + + + K + + + KAME + + Japanese for turtle, the term KAME is used + in computing circles to refer to the KAME Project, who work on + an implementation of IPv6. + + + + + KDC + + + + + KLD + + + + + KSE + + + + + KVA + + + + + Kbps + + + + + Kernel &man.ld.1; + KLD + + + + + + + Kernel Scheduler Entities + KSE + + A kernel-supported threading system. See the project home page + for further details. + + + + + Kernel Virtual Address + KVA + + + + + + + Key Distribution Center + KDC + + + + + + + Kilo Bits Per Second + Kbps + + + + + + + + L + + + LAN + + + + + LOR + + + + + LPD + + + + + Line Printer Daemon + LPD + + + + + + + Local Area Network + LAN + + + + + + + Lock Order Reversal + LOR + + 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 if you were unlucky, a deadlock would + have happened here. + + True positive LORs tend to get fixed quickly, so + check &a.current.url; and the + + LORs Seen page before posting to the mailing lists. + + + + + + M + + + MAC + + + + + MADT + + + + + MFC + + + + + MFS + + + + + MIT + + + + + MLS + + + + + MOTD + + + + + MTA + + + + + MUA + + + + + Mail Transfer Agent + MTA + + + + + + + Mail User Agent + MUA + + + + + + + Mandatory Access Control + MAC + + + + + + + Massachusetts Institute of Technology + MIT + + + + + + + Merge From Current + MFC + + To merge functionality or a patch from the -CURRENT + branch to another, most often -STABLE. + + + + + Merge From Stable + MFS + + 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. + + This term is also used when a patch is merged from -STABLE + to a security branch. + + + + + + Message Of The Day + MOTD + + A message, usually shown on login, often used to + distribute information to users of the system. + + + + + Multi-Level Security + MLS + + + + + + + Multiple APIC Description Table + MADT + + + + + + + + N + + + NAT + + + + + NDISulator + + + + + NFS + + + + + NTFS + + + + + NTP + + + + + Network Address Translation + NAT + + + + + + + Network File System + NFS + + + + + + + New Technology File System + NTFS + + A filesystem developed by Microsoft and available in its + New Technology operating systems, such as + &windows2k;, &windowsnt; and &windowsxp;. + + + + + Network Time Protocol + NTP + + + + + + + + O + + + OBE + + + + + ODMR + + + + + OS + + + + + On-Demand Mail Relay + ODMR + + + + + + + Operating System + OS + + + + + + + Overtaken By Events + OBE + + 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. + + + + + + P + + + PAE + + + + + PAM + + + + + PAP + + + + + PC + + + + + PCNSFD + + + + + PDF + + + + + PID + + + + + POLA + + + + + POP + + + + + POP3 + + + + + PPD + + + + + PPP + + + + + PPPoA + + + + + PPPoE + + + + + PPP over ATM + PPPoA + + + + + + + PPP over Ethernet + PPPoE + + + + + + + PR + + + + + PXE + + + + + Password Authentication Protocol + PAP + + + + + + + Personal Computer + PC + + + + + + + Personal Computer Network File System Daemon + PCNFSD + + + + + + + Physical Address Extensions + PAE + + A method of enabling access to up to 64 GB of RAM on + systems which only physically have a 32-bit wide address space + (and would therefore be limited to 4 GB without PAE). + + + + + Pluggable Authentication Modules + PAM + + + + + + + Point-to-Point Protocol + PPP + + + + + + + Pointy Hat + + A mythical piece of headgear, much like a + dunce cap, 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. + + + + + Portable Document Format + PDF + + + + + + + Post Office Protocol + POP + + + + + + + Post Office Protocol Version 3 + POP3 + + + + + + + PostScript Printer Description + PPD + + + + + + + Preboot eXecution Environment + PXE + + + + + + + Principle Of Least Astonishment + POLA + + As &os; evolves, changes visible to the user should be + kept as unsurprising as possible. For example, arbitrarily + rearranging system startup variables in + /etc/defaults/rc.conf violates + POLA. Developers consider + POLA when contemplating user-visible + system changes. + + + + + Problem Report + PR + + + + + + + Process ID + PID + + A number, unique to a particular process on a system, + which identifies it and allows actions to be taken against it. + + + + + Project Evil + + The working title for the NDISulator, + 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 + NDISulator 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 src/sys/compat/ndis/subr_ndis.c. + + + + + + R + + + RA + + + + + RAID + + + + + RAM + + + + + RD + + + + + RFC + + + + + RISC + + + + + RPC + + + + + RS232C + + + + + RTS + + + + + Random Access Memory + RAM + + + + + + + Received Data + RD + + + + + + + Recommended Standard 232C + RS232C + + A standard for communications between serial devices. + + + + + Reduced Instruction Set Computer + RISC + + + + + + + Redundant Array of Inexpensive Disks + RAID + + + + + + + Remote Procedure Call + RPC + + + + + + + Request For Comments + RFC + + + + + + + Request To Send + RTS + + + + + + + Router Advertisement + RA + + + + + + + + S + + + SCI + + + + + SCSI + + + + + SG + + + + + SMB + + + + + SMP + + + + + SMTP + + + + + SMTP AUTH + + + + + SSH + + + + + STR + + + + + SMTP Authentication + SMTP AUTH + + + + + + + Server Message Block + SMB + + + + + + + Signal Ground + SG + + An RS232 pin or wire that is the ground reference + for the signal. + + + + + Simple Mail Transfer Protocol + SMTP + + + + + + + Secure Shell + SSH + + + + + + + Small Computer System Interface + SCSI + + + + + + + Suspend To RAM + STR + + + + + + + Symmetric MultiProcessor + SMP + + + + + + + System Control Interrupt + SCI + + + + + + + + T + + + TCP + + + + + TD + + + + + TFTP + + + + + TGT + + + + + TSC + + + + + Ticket-Granting Ticket + TGT + + + + + + + Time Stamp Counter + TSC + + + A profiling counter internal to modern &pentium; processors + that counts core frequency clock ticks. + + + + + Transmission Control Protocol + TCP + + + + + + + Transmitted Data + TD + + + + + + + Trivial FTP + TFTP + + + + + + + + U + + + UDP + + + + + UFS1 + + + + + UFS2 + + + + + UID + + + + + URL + + + + + USB + + + + + Uniform Resource Locator + URL + + + + + + + Unix File System Version 1 + UFS1 + + + + + + + Unix File System Version 2 + UFS2 + + + + + + + Universal Serial Bus + USB + + + + + + + User ID + UID + + A unique number assigned to each user of a computer, + by which the resources and permissions assigned to that + user can be identified. + + + + + User Datagram Protocol + UDP + + + + + + + + V + + + VPN + + + + + Virtual Private Network + VPN + + + + + + --- zh_TW4.diff ends here --- >Release-Note: >Audit-Trail: >Unformatted: