Index: head/zh_TW.UTF-8/books/faq/book.xml =================================================================== --- head/zh_TW.UTF-8/books/faq/book.xml (revision 53450) +++ head/zh_TW.UTF-8/books/faq/book.xml (revision 53451) @@ -1,6979 +1,6946 @@ 12-CURRENT"> X"> head/"> X"> 12-STABLE"> stable/12/"> X"> 11-STABLE"> stable/11/"> ]> - Frequently Asked Questions for FreeBSD - 11.<replaceable>X</replaceable> and 12.<replaceable>X</replaceable> + FreeBSD 11.<replaceable>X</replaceable> and 12.<replaceable>X</replaceable> 常見問答集 FreeBSD 文件計畫 - - 1995 - 1996 - 1997 - 1998 - 1999 - 2000 - 2001 - 2002 - 2003 - 2004 - 2005 - 2006 - 2007 - 2008 - 2009 - 2010 - 2011 - 2012 - 2013 - 2014 - 2015 - 2016 - 2017 - 2018 + 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 The FreeBSD Documentation Project - The FreeBSD Documentation Project - - 版權所有 Redistribution and use in source (XML DocBook) and 'compiled' forms (XML, HTML, PDF, PostScript, RTF and so forth) with or without modification, are permitted provided that the following conditions are met: Redistributions of source code (XML DocBook) must retain the above copyright notice, this list of conditions and the following disclaimer as the first lines of this file unmodified. Redistributions in compiled form (transformed to other DTDs, converted to PDF, PostScript, RTF and other formats) must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS DOCUMENTATION IS PROVIDED BY THE FREEBSD DOCUMENTATION PROJECT "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FREEBSD DOCUMENTATION PROJECT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. FreeBSD 是 FreeBSD基金會的註冊商標。 Adobe, Acrobat, Acrobat Reader, 以及 PostScript 是 Adobe Systems Incorporated 在美國和/或其他國家的商標或註冊商標。 IBM, AIX, OS/2, PowerPC, PS/2, S/390, 和 ThinkPad 是 國際商用機器公司在美國和其他國家的註冊商標或商標。 IEEE, POSIX, 和 802 是 Institute of Electrical and Electronics Engineers, Inc. 在美國的註冊商標。 Intel, Celeron, Centrino, Core, EtherExpress, i386, i486, Itanium, Pentium, 和 Xeon 是 Intel Corporation 及其分支機構在美國和其他國家的商標或註冊商標。 Linux 是 Linus Torvalds 的註冊商標。 Microsoft, IntelliMouse, MS-DOS, Outlook, Windows, Windows Media, 和 Windows NT 是 Microsoft Corporation 在美國和/或其他國家的商標或註冊商標。 NetBSD 是 NetBSD基金會的註冊商標。 Motif, OSF/1, and UNIX are registered trademarks and IT DialTone and The Open Group 是 The Open Group 在美國和其他國家的商標。 Silicon Graphics, SGI, 和 OpenGL 是 Silicon Graphics, Inc. 在美國和/或其他國家的註冊商標。 Sun, Sun Microsystems, Java, Java Virtual Machine, JDK, JRE, JSP, JVM, Netra, OpenJDK, Solaris, StarOffice, SunOS and VirtualBox 是 Sun Microsystems, Inc. 在美國和其他國家的註冊商標。 許多製造商和經銷商使用一些稱為商標的圖案或文字設計來彰顯自己的產品。 本文中出現的眾多商標，以及 FreeBSD Project 本身廣所人知的商標，後面將以™ 或 ® 符號來標註。 $FreeBSD$ - This is the Frequently Asked Questions - (FAQ) for FreeBSD versions - 12.X and 11.X. Every effort has been made to - make this FAQ as informative as possible; - if you have any suggestions as to how it may be improved, send - them to the FreeBSD documentation project mailing list. + 這份文件是 FreeBSD 12.X 和 11.X 常見問答集 ( (FAQ) )。我們盡可能地讓這份 FAQ 提供有用的資訊 ; 如果您有任何改善建議，請寄到 FreeBSD 文件計畫郵件論壇。 - The latest version of this document is always available from the FreeBSD website. + 本文件的最新版本可由 FreeBSD 網站取得。 也可以由 FreeBSD FTP 伺服器 以 HTTP 下載單一大型 HTML 檔或是其他格式的檔案。 前言 什麼是 FreeBSD？ FreeBSD 是一個使用於桌機、筆電、伺服器與嵌入式系統平台的現代作業系統，支援多種平台。 它是根據 U.C. Berkeley 所開發出來的 4.4BSD-Lite ，並加上了許多 4.4BSD-Lite2 的增強功能。它同時也間接使用了 U.C. Berkeley 所開發出來並由 William Jolitz 移植到 i386 的 Net/2，也就是 386BSD，不過現在 386BSD 的程式碼只剩下極少數還留 存在 FreeBSD 中。 FreeBSD 已被廣泛地被世界各地的公司行號、ISP、研究人員、電腦 專家、學生，以及家庭用戶所使用，用在工作、教育以及娛樂上。 如果想看關於 FreeBSD 更深入的資料，請看 FreeBSD 使用手冊。 發展 FreeBSD 計畫的目的是什麼？ FreeBSD 計畫的目的是提供可以任意使用且沒有限制的穩定快速與一般用途的作業系統。 FreeBSD 版權有任何限制嗎？ 有的。但是這並不是限制你怎麼去使用這些程式碼，而是你怎麼看待 FreeBSD 這個計畫。可以在此閱讀 版權本文，簡單來說總結如下: 請勿宣稱是您寫了這個程式。 如果它出問題了，不要控告我們。 不要移除和修改版權 我們許多人在這個計畫投入很多心血，並不會介意獲得一些財務上的報酬，但是我們並沒有堅持一定要有。我們相信我們首要的任務是將程式碼提供給所有使用者，無論他們有任何的目的，這麼一來，這些程式碼才能被用在最多地方，也才能發揮它們最大的利益。我們相信這就是自由軟體最基本的目標之一，而且我們會盡全力去支持它。 在我們 source tree 中有部份的程式碼是採用所謂的GNU General Public License (GPL) 或 GNU Library General Public License (LGPL)版權宣告，雖然這些版權宣告是用來保障而非限制使用者的權 利，畢竟是不那麼自由了些。由於這些 GPL 的軟體在商業使用上會引起 非常複雜的版權問題，因此只要有機會，我們會盡量以採用比較鬆的 FreeBSD 版權 的軟體來取代這些 GPL 版權宣告的軟體。 FreeBSD 可以取代我現在在用的作業系統嗎？ 對大部份的人來說是這樣沒錯，但事實上這問題並沒有這麼好回答。 大部份的人並不是真正在使用一個作業系統。他們使用的是應用程式 ；而那些應用程式才是真正用到作業系統的東西。FreeBSD 是設計用來提供一個強韌且功能完整的作業環境給應用程式來執行。它支援了多種瀏覽器，辦公室套件軟體，電子郵件閱讀軟體，繪圖程式，程式設計環境，網路伺服器軟體，以及幾乎所有你想要的東西。大部份的程式都可以靠 Ports Collection 來管理。 但是如果你想要使用的應用程式只能在某個特定的作業系統上面執行 的話，你就不能輕易地把它換掉，或者指望在 FreeBSD 上有很相似的應用程式才有機會。如果你想要的是一個強健的辦公室或是網路伺服器，或是一部穩定的工作站，FreeBSD 無疑是您的最佳選擇。世界各地有很多使用者，包括初學或資深的 UNIX 管理人員都選用 FreeBSD 當他們唯一的桌上作業系統。 如果你是從其他的 UNIX-like 環境轉換到 FreeBSD 的話會很熟悉。 Windows 或是 Mac OS 的使用者可能會對 TrueOS 有興趣，他是基於 FreeBSD 的一個桌面環境發行版，非UNIX 使用者可能就要多花一點時間來學習怎麼用 UNIX 的 方法來做事。你可以從這份 FAQ 和 FreeBSD 使用手冊 來入門。 為什麼要叫做 FreeBSD？ 您可以免費使用它，即使是用於商業用途。 整個 FreeBSD 作業系統完整的原始程式都可以免費取得，而且不管是在使用，散佈或是整合進其他程式等各方面也只受到最小的限制 (不論是否用於商業用途)。 任何人都可以自由地把他對系統的改良或錯誤修正的程式碼加入 source tree 之中 (當然要符合幾個先決條件)。 特別值得注意的是這裡的 “free” 出現了兩次，而且它們 的意思是不一樣的：一種代表 “免費”，另一種代表 “自由”。您可以拿 FreeBSD 去做任何您想要做的事，除了一些例外，例如您宣稱 FreeBSD 是您寫的。 FreeBSD 及 NetBSD, OpenBSD 以及其他 open source BSD 作業系統之間有何不同之處呢？ James Howard wrote a good explanation of the history and differences between the various projects, called The BSD Family Tree which goes a fair way to answering this question. Some of the information is out of date, but the history portion in particular remains accurate. 時至今日，大部分的 BSD 家族仍是共用修補和程式碼的。這些 BSD 家族有著共同的祖先。 FreeBSD 的設計目的如 所述。其他 BSD 家族的設計目的如下所述： OpenBSD 目標在作業系統的安全性。OpenBSD團隊寫的 ssh1 和 pf4 都移植到了 FreeBSD。 NetBSD 目標在易於移植到其他的硬體平台。 DragonFly BSD 是 FreeBSD 4.8 的一個分支，發展出許多有趣的特色，包括 HAMMER 檔案系統和支援 vkernels 使用者模式。 最新版的 FreeBSD 是那一版？ At any point in the development of FreeBSD, there can be multiple parallel branches. 12.X releases are made from the 12-STABLE branch, and 11.X releases are made from the 11-STABLE branch. Up until the release of 9.0, the 11.X series was the one known as -STABLE. However, as of 13.X, the 11.X branch will be designated for an extended support status and receive only fixes for major problems, such as security-related fixes. - Version 12.0 + Version 12.0 is the latest release from the 12-STABLE branch; it was - released in December 2018. Version 10.4 + released in December 2018. Version 11.2 is the latest release from the 11-STABLE branch; it - was released in October 2017. + was released in June 2018. Releases 版 每幾個月 才會發行一次。 雖然如此，有很多人和 FreeBSD 原始碼同步更新 (詳見 FreeBSD-CURRENT 和 FreeBSD-STABLE的相關問題) ，但因為原始碼是一直不斷地在變動的，所以如果要這麼做的話得要花上更多的精力。 其他更多相關 FreeBSD 發行情報，可由 FreeBSD 網站上的 Release Engineering 頁面 和 release7得知。 什麼是 FreeBSD-CURRENT? FreeBSD-CURRENT 指的是正在發展中的作業系統版本，它終將在適當的時機成為 FreeBSD-STABLE 分支。它實在是只適合給系統發展者以及有毅力的業餘愛好者使用 。如果想要得到有關如何使用-CURRENT的深入資訊，請參考使用手冊的相關部份。 如果您對 FreeBSD 本身並不是很熟悉那麼您就不應該使用FreeBSD-CURRENT。 這個分支的程式碼有時候變動得很快，而且可能會因此 而使您有好幾天的時間無法更新您的系統。我們假設使用 FreeBSD-CURRENT 的使用者都有能力去分析他們所遇到的問題，除錯，並且回報問題。 我們每天都會根據目前 -CURRENT 和 -STABLE 的狀況對這兩個分支各發行一個 snapshot 版。發表這些 snapshot 的目的在於： 測試最新版的安裝程式。 提供一個簡單的方法給那些喜歡使用 -CURRENT 或是 -STABLE 但是沒有時間和頻寬去每天昇級的使用者。 為了替我們發展中的程式保留一個固定的參考點，以防止我們未來不幸搞砸了。(雖然一般而言 Subversion 可以防止類似這種的可怕事件) 為了確保所有需要測試的新功能或修正都可以得到最多的測試。 我們不對 -CURRENT snapshot 做任何目的的 品質保證 。如果你想要的是一個穩定且經過充分測試過的系統的話， 最好選擇使用完整 releases. 您可以直接從 snapshot 取得 -CURRENT 的 snapshot release。 對每個有在活動的分支而言，都會定期產生一次 snapshots。 什麼是 FreeBSD-STABLE ? Back when FreeBSD 2.0.5 was released, FreeBSD development branched in two. One branch was named -STABLE, one -CURRENT. FreeBSD-STABLE is the development branch from which major releases are made. Changes go into this branch at a slower pace and with the general assumption that they have first been tested in FreeBSD-CURRENT. However, at any given time, the sources for FreeBSD-STABLE may or may not be suitable for general use, as it may uncover bugs and corner cases that were not yet found in FreeBSD-CURRENT. Users who do not have the resources to perform testing should instead run the most recent release of FreeBSD. FreeBSD-CURRENT, on the other hand, has been one unbroken line since 2.0 was released, leading towards 12.0-RELEASE and beyond. For more detailed information on branches see FreeBSD Release Engineering: Creating the Release Branch, the status of the branches and the upcoming release schedule can be found on the Release Engineering Information page. 12.0-STABLE is the actively developed -STABLE branch. The latest release on the 12.0-STABLE branch is 12.0-RELEASE, which was released in December 2018. 12-CURRENT 這個分支是 FreeBSD 的 -CURRENT 分支，仍然不斷地在發展當中。 如果想要知道更多關於這個分支的資訊的話，請參考 什麼是 FreeBSD-CURRENT? 。 每次新的 FreeBSD 將於什麼時候推出？ 一般而言，Release Engineering Team re@FreeBSD.org 約每18個月發行一次主要發行版本，約平均每8個月發行一次次要發行版本。每次新版本的發表時程都會事先公告， 相關的開發人員就會知道，什麼時候該先把手邊的計劃完成並且測試過， 此外，這些更動都已經完整地測試過，確保新功能不會影響系統的穩定度。 雖然，等這些好東西進入-STABLE 的時間令人等得有些不耐煩， 但是大多數的使用者都認為這種謹慎的態度是 FreeBSD 最好的優點之一。 有關發行情報的更多細節部分(包括 release 的行程表、進度)，都可在 FreeBSD 網站上的 發行情報 上面獲得。 為了滿足那些需要 (或想要) 新鮮刺激感的使用者， 上面已經提到我們每周都會發行 snapshots 版可供使用。 誰負責 FreeBSD 的發展？ 如果是一些有關 FreeBSD 計畫的關鍵性決定，像是整個計畫的走向 或是決定誰可以改 source tree 裡的程式碼這類的事，是由一個由 9 個 人所組成的 core team 來決定。而有另一群超過 350 個人的 committers 有權利可以直接修改 FreeBSD 的 source tree。 無論如何，大多數的改變都會事前在 郵件論壇先討論過，而且不分角色，每個人都可以參與討論。 我要如何取得 FreeBSD？ Every significant release of FreeBSD is available via - anonymous FTP from the FreeBSD + anonymous FTP from the FreeBSD FTP site: The latest 12-STABLE release, - 12.0-RELEASE can be found in the 12.0-RELEASE + 12.0-RELEASE can be found in the 12.0-RELEASE directory. -CURRENT 和 -STABLE 分支的Snapshot版本通常每個月會做一次， 主要是為了提供給那些熱心的測試者和開發人員。 The latest 11-STABLE release, - 10.4-RELEASE can be found in the 10.4-RELEASE + 11.2-RELEASE can be found in the 11.2-RELEASE directory. FreeBSD 的 CD、DVD，還有其他取得方式可以在 the Handbook 中找到解答。 我要如何去查詢、提交問題回報(Problem Report，簡稱PR)資料庫呢？ 所有使用者的變更要求都可以經由網頁版的 PR 查詢 界面來察看。 可以使用瀏覽器經由網頁版的 PR 界面 來傳送問題回報 然而，在您回報問題之前，請先閱讀 如何撰寫 FreeBSD 的問題回報單，這是一篇告訴你怎樣才能寫出一篇真正有用的問題回報單。 文件與技術支援 名稱 The project produces a wide range of documentation, available online from this link: https://www.FreeBSD.org/docs.html. In addition, the the bibliography in the Handbook reference other recommended books. 這些文件有其他格式的嗎？像是：純文字(ASCII)或 PostScript 之類的格式？ 有的。這些文件都分別以不同格式儲存以及壓縮處理並放在 FTP 上面，可以從各個 FreeBSD FTP 站的 /pub/FreeBSD/doc/ 目錄內找到你要的。 文件以幾種不同的方式分類。包括： 文件名稱，例如：faq (常見問答集)或是 handbook (FreeBSD 使用手冊)等等。 文件的語言與編碼。他們是基於 FreeBSD 系統中 /usr/share/locale 裡所見到的語系名稱。目前包含的語言與編碼如下： 語系名稱 說明 en_US.ISO8859-1 英文 (美國) bn_BD.ISO10646-1 孟加拉文 (孟加拉) da_DK.ISO8859-1 丹麥文 (丹麥) de_DE.ISO8859-1 德文 (德國) el_GR.ISO8859-7 希臘文 (希臘) es_ES.ISO8859-1 西班牙文 (西班牙) fr_FR.ISO8859-1 法文 (法國) hu_HU.ISO8859-2 匈牙利文 (匈牙利) it_IT.ISO8859-15 義大利文 (義大利) ja_JP.eucJP 日文 (日本, EUC 編碼) ko_KR.UTF-8 Korean (Korea, UTF-8 encoding) mn_MN.UTF-8 蒙古文 (蒙古, UTF-8 編碼) nl_NL.ISO8859-1 荷蘭文 (荷蘭) pl_PL.ISO8859-2 波蘭文 (波蘭) pt_BR.ISO8859-1 葡萄牙文 (巴西) ru_RU.KOI8-R 俄文 (俄羅斯, KOI8-R 編碼) tr_TR.ISO8859-9 土耳其文 (土耳其) zh_CN.UTF-8 簡體中文 (中國, UTF-8 編碼) zh_TW.UTF-8 正體中文 (台灣, UTF-8 編碼) 上列的各國翻譯語系文件中，並非所有文件都有翻譯。 文件的格式。我們的每份文件都提供許多不同的格式，每種格式各有利弊， 有些格式適合線上閱讀，有些則適合列印出美觀的文件。 這些不同格式的文件能夠確保我們的讀者們，無論是在螢幕上閱讀或是列印成紙本，都能夠閱讀他們感興趣的內容，目前有提供的格式如下： 格式 說明 html-split 依章節區分成多個小的、互相連結的 HTML 檔案 html 所有內容包含在單一個 HTML 檔案 pdf Adobe's PDF 格式 ps PostScript rtf Microsoft 的 RTF 格式 txt 純文字 當用 Word 讀取 RTF 格式時，頁碼並不會被自動更新。在開啟檔案後按下CtrlA, CtrlEnd, F9 來更新頁碼。 壓縮和打包方式 Where the format is html-split, the files are bundled up using tar1. The resulting .tar is then compressed using the compression schemes detailed in the next point. 其他的格式都是單一個檔案。例如 article.pdf、book.html ，以此類推。 這些檔案接著透過 zip 或 bz2 來壓縮。 tar1 工具可用來解壓縮這些檔案。 因此 PostScript 版本的手冊經過 bzip2 壓縮後會存成一個叫做 book.ps.bz2 的檔案，並位於 handbook/ 資料夾。 在選取格式與壓縮方式後，下載壓縮後的檔案並解壓縮，再把文件複製到想要的地方。 舉例來說，透過 bzip21 壓縮的英文問與答的章節分割 HTML 版本，可以在 doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2 中找到。若要下載並解壓縮這個檔案，請輸入 # fetch https://download.freebsd.org/ftp/doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2 # tar xvf book.html-split.tar.bz2 如果檔案被壓縮過的話，tar 會自動偵測正確的格式並解壓縮出一堆 .html 檔案。主要的檔案是 index.html，包含了主目錄跟介紹以及連接到文件其他部份的連結。 哪裡有關於 FreeBSD 的郵遞論壇(mailing lists)呢？ 有哪些可以使用的 FreeBSD 新聞群組(news groups)呢? 請參考FreeBSD 使用手冊上的 郵件論壇 (mailing-lists) 。 有 FreeBSD IRC (Internet Relay Chat)頻道嗎？ 有的，大部分的 IRC 主機都有 FreeBSD 聊天頻道： EFNet 上的 #FreeBSDhelp 頻道專門用來幫助 FreeBSD 使用著 Freenode 上的 #FreeBSD 頻道是一個有許多使用者的一般求助頻道。這個頻道時常聊一些題外話，但主要還是讓使用者問 FreeBSD 相關問題的地方。其他使用者可以協助解答一些基本的問題，並請盡量提供使用手冊的參考或是提供連結來提供更深入的資訊。雖然這個頻道有來自世界各地的使用者，但這是一個英文為主的頻道。非母語人士應該以英文提問，並在必要的時候移駕到 ##freebsd-lang 頻道。 DALNET 的#FreeBSD 頻道，可由 irc.dal.net （位於美國）及irc.eu.dal.net （位於歐洲）進入。 UNDERNET 上的 #FreeBSD 頻道可由 us.undernet.org（位於美國）及 eu.undernet.org （位於歐洲）進入。由於這是個輔助新手用的頻道， 請記得閱讀別人向你提及的連結或檔案。 RUSNET 上的 #FreeBSD 頻道是俄語國家的 FreeBSD 使用者頻道。 這裡同時也是一般交流的討論好去處。 Freenode 上的 #bsdchat 頻道是一個正體中文（UTF-8 編碼）頻道專門用來幫助 FreeBSD 使用著。這裡也歡迎一般非技術的交流討論。 The FreeBSD wiki has a good list of IRC channels. 每個頻道都是不同且互相獨立的。因為他們的聊天風格不同，您可以每個都試試看來找到適合您的頻道。 有沒有任何網頁形式的 FreeBSD 論壇呢？ 官方的 FreeBSD 論壇位於 https://forums.FreeBSD.org/。 可以從哪邊獲得商業化的 FreeBSD 的教育課程及技術支援呢？ iXsystems, Inc.， FreeBSD 商城的母公司，提供 FreeBSD 開發與調校解決方案與 FreeBSD 與 TrueOS 的軟體 支援。 BSD Certification Group, Inc. 提供 DragonFly BSD、FreeBSD、NetBSD 與 OpenBSD 的系統管理認證。請參閱 他們的網站 來獲得更多資訊。 如果有其他組織提供技術訓練或技術支援，請聯絡 FreeBSD 計畫來加入以上清單。 安裝 Nik Clayton
nik@FreeBSD.org
Which platform should I download? I have a 64 bit capable Intel CPU, but I only see amd64. amd64 is the term FreeBSD uses for 64-bit compatible x86 architectures (also known as "x86-64" or "x64"). Most modern computers should use amd64. Older hardware should use i386. When installing on a non-x86-compatible architecture, select the platform which best matches the hardware. Which file do I download to get FreeBSD? On the Getting FreeBSD page, select [iso] next to the architecture that matches the hardware. Any of the following can be used: 檔案 描述 disc1.iso Contains enough to install FreeBSD and a minimal set of packages. dvd1.iso Similar to disc1.iso but with additional packages. memstick.img A bootable image sufficient for writing to a USB stick. bootonly.iso A minimal image that requires network access during installation to completely install FreeBSD. 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. What do I do if the install image does not boot? This can be caused by not downloading the 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 SHA-256 checksum of the downloaded boot image: if it is not exactly that on the server, then the download process is suspect. When using a command line FTP client, type binary at the FTP command prompt after getting connected to the server and before starting the download of the image. 可以在哪邊找到安裝 FreeBSD 的解說步驟呢？ Installation instructions can be found at Handbook entry on installing FreeBSD. 要跑 FreeBSD 至少需要什麼樣的配備呢？ FreeBSD requires a 486 or better PC, 64 MB or more of RAM, and at least 1.1 GB of hard disk space. 要怎樣才能自行打造專用的安裝磁片呢？ Customized FreeBSD installation media can be created by building a custom release. Follow the instructions in the Release Engineering article. Windows 可以與 FreeBSD 共存嗎？ If Windows is installed first, then yes. FreeBSD's boot manager will then manage to boot Windows and FreeBSD. If Windows is installed afterwards, it will overwrite the boot manager. If that happens, see the next section. Another operating system destroyed my Boot Manager. How do I get it back? This depends upon the boot manager. The FreeBSD boot selection menu can be reinstalled using boot0cfg8. For example, to restore the boot menu onto the disk ada0: # boot0cfg -B ada0 The non-interactive MBR bootloader can be installed using gpart8: # gpart bootcode -b /boot/mbr ada0 For more complex situations, including GPT disks, see gpart8. 我需要安裝完整的原始碼嗎？ In general, no. There is nothing in the base system which requires the presence of the source to operate. Some ports, like sysutils/lsof, will not build unless the source is installed. In particular, if the port builds a kernel module or directly operates on kernel structures, the source must be installed. 需要重新 build kernel 嗎？ Usually not. The supplied GENERIC kernel contains the drivers an ordinary computer will need. freebsd-update8, the FreeBSD binary upgrade tool, cannot upgrade custom kernels, another reason to stick with the GENERIC kernel when possible. For computers with very limited RAM, such as embedded systems, it may be worthwhile to build a smaller custom kernel containing just the required drivers. Should I use DES, Blowfish, or MD5 passwords and how do I specify which form my users receive? FreeBSD uses SHA512 by default. DES passwords are still available for backwards compatibility with operating systems that still use the less secure password format. FreeBSD also supports the Blowfish and MD5 password formats. 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 login.conf5 manual page for more information about login capabilities. What are the limits for FFS file systems? For FFS file systems, the largest file system is practically limited by the amount of memory required to fsck8 the file system. fsck8 requires one bit per fragment, which with the default fragment size of 4 KB equates to 32 MB of memory per TB of disk. This does mean that on architectures which limit userland processes to 2 GB (e.g., i386), the maximum fsck8'able filesystem is ~60 TB. If there was not a fsck8 memory limit the maximum filesystem size would be 2 ^ 64 (blocks) * 32 KB => 16 Exa * 32 KB => 512 ZettaBytes. The maximum size of a single FFS file is approximately 2 PB with the default block size of 32 KB. Each 32 KB block can point to 4096 blocks. With triple indirect blocks, the calculation is 32 KB * 12 + 32 KB * 4096 + 32 KB * 4096^2 + 32 KB * 4096^3. Increasing the block size to 64 KB will increase the max file size by a factor of 16. Why do I get an error message, readin failed after compiling and booting a new kernel? The world and kernel are out of sync. This is not supported. Be sure to use make buildworld and make buildkernel to update the kernel. Boot the system by specifying the kernel directly at the second stage, pressing any key when the | shows up before loader is started. Is there a tool to perform post-installation configuration tasks? Yes. bsdconfig provides a nice interface to configure FreeBSD post-installation. 硬體相容性 一般問題 I want to get a piece of hardware for my FreeBSD system. Which model/brand/type is best? This is discussed continually on the FreeBSD mailing lists but is to be expected since hardware changes so quickly. Read through the Hardware Notes for FreeBSD 12.0 - or 10.4 + or 11.2 and search the mailing list archives before asking about the latest and greatest hardware. Chances are a discussion about that type of hardware took place just last week. Before purchasing a laptop, check the archives for FreeBSD laptop computer mailing list and FreeBSD general questions mailing list, or possibly a specific mailing list for a particular hardware type. What are the limits for memory? Does FreeBSD support more than 4 GB of memory (RAM)? More than 16 GB? More than 48 GB? FreeBSD as an operating system generally supports as much physical memory (RAM) as the platform it is running on does. Keep in mind that different platforms have different limits for memory; for example i386 without PAE supports at most 4 GB of memory (and usually less than that because of PCI address space) and i386 with PAE supports at most 64 GB memory. As of FreeBSD 10, AMD64 platforms support up to 4 TB of physical memory. Why does FreeBSD report less than 4 GB memory when installed on an i386 machine? The total address space on i386 machines is 32-bit, meaning that at most 4 GB of memory is addressable (can be accessed). Furthermore, some addresses in this range are reserved by hardware for different purposes, for example for using and controlling PCI devices, for accessing video memory, and so on. Therefore, the total amount of memory usable by the operating system for its kernel and applications is limited to significantly less than 4 GB. Usually, 3.2 GB to 3.7 GB is the maximum usable physical memory in this configuration. To access more than 3.2 GB to 3.7 GB of installed memory (meaning up to 4 GB but also more than 4 GB), a special tweak called PAE must be used. PAE stands for Physical Address Extension and is a way for 32-bit x86 CPUs to address more than 4 GB of memory. It remaps the memory that would otherwise be overlaid by address reservations for hardware devices above the 4 GB range and uses it as additional physical memory (see pae4). Using PAE has some drawbacks; this mode of memory access is a little bit slower than the normal (without PAE) mode and loadable modules (see kld4) are not supported. This means all drivers must be compiled into the kernel. The most common way to enable PAE is to build a new kernel with the special ready-provided kernel configuration file called PAE, which is already configured to build a safe kernel. Note that some entries in this kernel configuration file are too conservative and some drivers marked as unready to be used with PAE are actually usable. A rule of thumb is that if the driver is usable on 64-bit architectures (like AMD64), it is also usable with PAE. When creating a custom kernel configuration file, PAE can be enabled by adding the following line: options PAE PAE is not much used nowadays because most new x86 hardware also supports running in 64-bit mode, known as AMD64 or Intel 64. It has a much larger address space and does not need such tweaks. FreeBSD supports AMD64 and it is recommended that this version of FreeBSD be used instead of the i386 version if 4 GB or more memory is required. Architectures and Processors Does FreeBSD support architectures other than the x86? Yes. FreeBSD divides support into multiple tiers. Tier 1 architectures, such as i386 or amd64; are fully supported. Tiers 2 and 3 are supported on a best-effort basis. A full explanation of the tier system is available in the Committer's Guide. A complete list of supported architectures can be found on the platforms page. Does FreeBSD support Symmetric Multiprocessing (SMP)? FreeBSD supports symmetric multi-processor (SMP) on all non-embedded platforms (e.g, i386, amd64, etc.). SMP is also supported in arm and MIPS kernels, although some CPUs may not support this. FreeBSD's SMP implementation uses fine-grained locking, and performance scales nearly linearly with number of CPUs. smp4 has more details. What is microcode? How do I install Intel CPU microcode updates? Microcode is a method of programmatically implementing hardware level instructions. This allows for CPU bugs to be fixed without replacing the on board chip. Install sysutils/devcpu-data, then add: microcode_update_enable="YES" to /etc/rc.conf Hard Drives, Tape Drives, and CD and DVD Drives What kind of hard drives does FreeBSD support? FreeBSD supports EIDE, SATA, SCSI, and SAS drives (with a compatible controller; see the next section), and all drives using the original Western Digital interface (MFM, RLL, ESDI, and of course IDE). A few ESDI controllers that use proprietary interfaces may not work: stick to WD1002/3/6/7 interfaces and clones. Which SCSI or SAS controllers are supported? See the complete list in the Hardware Notes for FreeBSD 12.0 - or 10.4. + or 11.2. What types of tape drives are supported? FreeBSD supports all standard SCSI tape interfaces. Does FreeBSD support tape changers? FreeBSD supports SCSI changers using the ch4 device and the chio1 command. The details of how to control the changer can be found in chio1. While AMANDA and some other products already understands changers, other applications only know how to move a tape from one point to another. In this case, keep track of which slot a tape is in and which slot the tape currently in the drive needs to go back to. Which CD-ROM and CD-RW drives are supported by FreeBSD? Any SCSI drive connected to a supported controller is supported. Most ATAPI compatible IDE CD-ROMs are supported. FreeBSD supports any ATAPI-compatible IDE CD-R or CD-RW drive. FreeBSD also supports any SCSI CD-R or CD-RW drives. Install the sysutils/cdrtools port or package, then use cdrecord. Keyboards and Mice Is it possible to use a mouse outside the X Window system? The default console driver, syscons4, provides the ability to use a mouse pointer in text consoles to cut & paste text. Run the mouse daemon, moused8, and turn on the mouse pointer in the virtual console: # moused -p /dev/xxxx -t yyyy # vidcontrol -m on 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 moused8 manual page for a list of supported protocol types. For a PS/2 mouse, add moused_enable="YES" to /etc/rc.conf to start the mouse daemon at boot time. Additionally, 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 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 a mouse in the text console? It is not possible to remove data using the mouse. However, it is possible to copy and paste. Once the mouse daemon is running as described in the previous question, hold down button 1 (left button) and move the mouse to select a region of text. Then, press button 2 (middle button) to paste it at the text cursor. Pressing button 3 (right button) will extend the selected region of text. If the mouse does not have a middle button, it is possible to emulate one or remap buttons using mouse daemon options. See the moused8 manual page for details. My mouse has a fancy wheel and buttons. Can I use them in FreeBSD? The answer is, unfortunately, It depends. These mice with additional features require specialized driver in most cases. Unless the mouse device driver or the user program has specific support for the mouse, it will act just like a standard two, or three button mouse. For the possible usage of wheels in the X Window environment, refer to that section. How do I use my delete key in sh and csh? For the Bourne Shell, add the following lines to ~/.shrc. See sh1 and editrc5. bind ^? ed-delete-next-char # for console bind ^[[3~ ed-delete-next-char # for xterm For the C Shell, add the following lines to ~/.cshrc. See csh1. bindkey ^? delete-char # for console bindkey ^[[3~ delete-char # for xterm For more information, see this page. Other Hardware Workarounds for no sound from my pcm4 sound card? Some sound cards set their output volume to 0 at every boot. Run the following command every time the machine boots: # mixer pcm 100 vol 100 cd 100 Does FreeBSD support power management on my laptop? FreeBSD supports the ACPI features found in modern hardware. Further information can be found in acpi4. Troubleshooting Why is FreeBSD finding the wrong amount of memory on i386 hardware? The most likely reason is the difference between physical memory addresses and virtual addresses. The convention for most PC hardware is to use the memory area between 3.5 GB and 4 GB for a special purpose (usually for PCI). This address space is used to access PCI hardware. As a result real, physical memory cannot be accessed by that address space. What happens to the memory that should appear in that location is hardware dependent. Unfortunately, some hardware does nothing and the ability to use that last 500 MB of RAM is entirely lost. Luckily, most hardware remaps the memory to a higher location so that it can still be used. However, this can cause some confusion when watching the boot messages. On a 32-bit version of FreeBSD, the memory appears lost, since it will be remapped above 4 GB, which a 32-bit kernel is unable to access. In this case, the solution is to build a PAE enabled kernel. See the entry on memory limits for more information. On a 64-bit version of FreeBSD, or when running a PAE-enabled kernel, FreeBSD will correctly detect and remap the memory so it is usable. During boot, however, it may seem as if FreeBSD is detecting more memory than the system really has, due to the described remapping. This is normal and the available memory will be corrected as the boot process completes. Why do my programs occasionally die with Signal 11 errors? Signal 11 errors are caused when a process has attempted to access memory which the operating system has not granted it access to. If something like this is happening at seemingly random intervals, start investigating the cause. These problems can usually be attributed to either: If the problem is occurring only in a specific custom application, it is probably a bug in the code. If it is a problem with part of the base FreeBSD system, it may also be buggy code, but more often than not these problems are found and fixed long before us general FAQ readers get to use these bits of code (that is what -CURRENT is for). It is probably not a FreeBSD bug if the problem occurs compiling a program, but the activity that the compiler is carrying out changes each time. For example, if make buildworld fails while trying to compile ls.c into ls.o and, when run again, it fails in the same place, this is a broken build. Try updating source and try again. If the compile fails elsewhere, it is almost certainly due to hardware. In the first case, use a debugger such as gdb1 to find the point in the program which is attempting to access a bogus address and fix it. In the second case, verify which piece of hardware is at fault. Common causes of this include: The hard disks might be overheating: Check that the fans are still working, as the disk and other hardware might be overheating. The processor running is overheating: This might be because the processor has been overclocked, or the fan on the processor might have died. In either case, ensure that the hardware is running at what it is specified to run at, at least while trying to solve this problem. If it is not, clock it back to the default settings.) Regarding overclocking, it is far cheaper to have a slow system than a fried system that needs replacing! Also the community is not sympathetic to problems on overclocked systems. Dodgy memory: if multiple memory SIMMS/DIMMS are installed, pull them all out and try running the machine with each SIMM or DIMM individually to narrow the problem down to either the problematic DIMM/SIMM or perhaps even a combination. Over-optimistic motherboard settings: the BIOS settings, and some motherboard jumpers, provide options to set various timings. The defaults are often sufficient, but sometimes setting the wait states on RAM too low, or setting the RAM Speed: Turbo option will cause strange behavior. A possible idea is to set to BIOS defaults, after noting the current settings first. Unclean or insufficient power to the motherboard. Remove any unused I/O boards, hard disks, or CD-ROMs, or disconnect the power cable from them, to see if the power supply can manage a smaller load. Or try another power supply, preferably one with a little more power. For instance, if the current power supply is rated at 250 Watts, try one rated at 300 Watts. Read the section on Signal 11 for a further explanation and a discussion on how memory testing software or hardware can still pass faulty memory. There is an extensive FAQ on this at the SIG11 problem FAQ. Finally, if none of this has helped, it is possibly a bug in FreeBSD. Follow these instructions to send a problem report. My system crashes with either Fatal trap 12: page fault in kernel mode, or panic:, and spits out a bunch of information. What should I do? The FreeBSD developers are interested in these errors, but need more information than just the error message. Copy the full crash message. Then consult the FAQ section on kernel panics, build a debugging kernel, and get a backtrace. This might sound difficult, but does not require any programming skills. Just follow the instructions. What is the meaning of the error maxproc limit exceeded by uid %i, please see tuning(7) and login.conf(5)? The FreeBSD kernel will only allow a certain number of processes to exist at one time. The number is based on the kern.maxusers sysctl8 variable. kern.maxusers also affects various other in-kernel limits, such as network buffers. If the machine is heavily loaded, increase kern.maxusers. This will increase these other system limits in addition to the maximum number of processes. To adjust the kern.maxusers value, see the File/Process Limits section of the Handbook. While that section refers to open files, the same limits apply to processes. If the machine is lightly loaded but running a very large number of processes, adjust the kern.maxproc tunable by defining it in /boot/loader.conf. The tunable will not get adjusted until the system is rebooted. For more information about tuning tunables, see loader.conf5. If these processes are being run by a single user, adjust kern.maxprocperuid to be one less than the new kern.maxproc value. It must be at least one less because one system program, init8, must always be running. Why do full screen applications on remote machines misbehave? The remote machine may be setting the terminal type to something other than xterm which is required by the FreeBSD console. Alternatively the kernel may have the wrong values for the width and height of the terminal. Check the value of the TERM environment variable is xterm. If the remote machine does not support that try vt100. Run stty -a to check what the kernel thinks the terminal dimensions are. If they are incorrect, they can be changed by running stty rows RR cols CC. Alternatively, if the client machine has x11/xterm installed, then running resize will query the terminal for the correct dimensions and set them. Why does it take so long to connect to my computer via ssh or telnet? The symptom: there is a long delay between the time the TCP connection is established and the time when the client software asks for a password (or, in telnet1's case, when a login prompt appears). The problem: more likely than not, the delay is caused by the server software trying to resolve the client's IP address into a hostname. Many servers, including the Telnet and SSH servers that come with FreeBSD, do this to store the hostname in a log file for future reference by the administrator. The remedy: if the problem occurs whenever connecting the client computer to any server, the problem is with the client. If the problem only occurs when someone connects to the server computer, the problem is with the server. If the problem is with the client, the only remedy is to fix the DNS so the server can resolve it. If this is on a local network, consider it a server problem and keep reading. If this is on the Internet, contact your ISP. If the problem is with the server on a local network, configure the server to resolve address-to-hostname queries for the local address range. See hosts5 and named8 for more information. If this is on the Internet, the problem may be that the local server's resolver is not functioning correctly. To check, try to look up another host such as www.yahoo.com. If it does not work, that is the problem. Following a fresh install of FreeBSD, it is also possible that domain and name server information is missing from /etc/resolv.conf. This will often cause a delay in SSH, as the option UseDNS is set to yes by default in /etc/ssh/sshd_config. If this is causing the problem, either fill in the missing information in /etc/resolv.conf or set UseDNS to no in sshd_config as a temporary workaround. Why does file: table is full show up repeatedly in dmesg8? This error message indicates that the number of available file descriptors have been exhausted on the system. Refer to the kern.maxfiles section of the Tuning Kernel Limits section of the Handbook for a discussion and solution. Why does the clock on my computer keep incorrect time? The computer has two or more clocks, and FreeBSD has chosen to use the wrong one. Run dmesg8, and check for lines that contain Timecounter. The one with the highest quality value that FreeBSD chose. # dmesg | grep Timecounter Timecounter "i8254" frequency 1193182 Hz quality 0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 Timecounter "TSC" frequency 2998570050 Hz quality 800 Timecounters tick every 1.000 msec Confirm this by checking the kern.timecounter.hardware sysctl3. # sysctl kern.timecounter.hardware kern.timecounter.hardware: ACPI-fast It may be a broken ACPI timer. The simplest solution is to disable the ACPI timer in /boot/loader.conf: debug.acpi.disabled="timer" Or the BIOS may modify the TSC clock—perhaps to change the speed of the processor when running from batteries, or going into a power saving mode, but FreeBSD is unaware of these adjustments, and appears to gain or lose time. In this example, the i8254 clock is also available, and can be selected by writing its name to the kern.timecounter.hardware sysctl3. # sysctl kern.timecounter.hardware=i8254 kern.timecounter.hardware: TSC -> i8254 The computer should now start keeping more accurate time. To have this change automatically run at boot time, add the following line to /etc/sysctl.conf: kern.timecounter.hardware=i8254 What does the error swap_pager: indefinite wait buffer: mean? This means that a process is trying to page memory from disk, and the page attempt has hung trying to access the disk for more than 20 seconds. It might be caused by bad blocks on the disk drive, disk wiring, cables, or any other disk I/O-related hardware. If the drive itself is bad, disk errors will appear in /var/log/messages and in the output of dmesg. Otherwise, check the cables and connections. What is a lock order reversal? The FreeBSD kernel uses a number of resource locks to arbitrate contention for certain resources. When multiple kernel threads try to obtain multiple resource locks, there's always the potential for a deadlock, where two threads have each obtained one of the locks and blocks forever waiting for the other thread to release one of the other locks. This sort of locking problem can be avoided if all threads obtain the locks in the same order. A run-time lock diagnostic system called witness4, enabled in FreeBSD-CURRENT and disabled by default for stable branches and releases, detects the potential for deadlocks due to locking errors, including errors caused by obtaining multiple resource locks with a different order from different parts of the kernel. The witness4 framework tries to detect this problem as it happens, and reports it by printing a message to the system console about a lock order reversal (often referred to also as LOR). It is possible to get false positives, as witness4 is conservative. A true positive report does not mean that a system is dead-locked; instead it should be understood as a warning that a deadlock could have happened here. Problematic LORs tend to get fixed quickly, so check the FreeBSD-CURRENT mailing list before posting to it. What does Called ... with the following non-sleepable locks held mean? This means that a function that may sleep was called while a mutex (or other unsleepable) lock was held. The reason this is an error is because mutexes are not intended to be held for long periods of time; they are supposed to only be held to maintain short periods of synchronization. This programming contract allows device drivers to use mutexes to synchronize with the rest of the kernel during interrupts. Interrupts (under FreeBSD) may not sleep. Hence it is imperative that no subsystem in the kernel block for an extended period while holding a mutex. To catch such errors, assertions may be added to the kernel that interact with the witness4 subsystem to emit a warning or fatal error (depending on the system configuration) when a potentially blocking call is made while holding a mutex. In summary, such warnings are non-fatal, however with unfortunate timing they could cause undesirable effects ranging from a minor blip in the system's responsiveness to a complete system lockup. For additional information about locking in FreeBSD see locking9. Why does buildworld/installworld die with the message touch: not found? This error does not mean that the touch1 utility is missing. The error is instead probably due to the dates of the files being set sometime in the future. If the CMOS clock is set to local time, run adjkerntz -i to adjust the kernel clock when booting into single-user mode. User Applications Where are all the user applications? Refer to the ports page for info on software packages ported to FreeBSD. The list currently tops 24,000 and is growing daily, so come back to check often or subscribe to the FreeBSD announcements mailing list for periodic updates on new entries. Most ports should work on all supported versions of FreeBSD. Those that do not are specifically marked as such. Each time a FreeBSD release is made, a snapshot of the ports tree at the time of release in also included in the ports/ directory. FreeBSD supports compressed binary packages to easily install and uninstall ports. Use pkg7 to control the installation of packages. How do I download the Ports tree? Should I be using Subversion? Any of the methods listed here work: Use portsnap for most use cases. Refer to Using the Ports Collection for instructions on how to use this tool. Use Subversion if custom patches to the ports tree are needed. Refer to Using Subversion for details. Does FreeBSD support Java? Yes. Refer to https://www.FreeBSD.org/java/ for more information. Why can I not build this port on my 11.X -, or 12.X -STABLE machine? If the installed FreeBSD version lags significantly behind -CURRENT or -STABLE, update the Ports Collection using the instructions in Using the Ports Collection. If the system is up-to-date, someone might have committed a change to the port which works for -CURRENT but which broke the port for -STABLE. Submit a bug report, since the Ports Collection is supposed to work for both the -CURRENT and -STABLE branches. I just tried to build INDEX using make index, and it failed. Why? First, make sure that the Ports Collection is up-to-date. Errors that affect building INDEX from an up-to-date copy of the Ports Collection are high-visibility and are thus almost always fixed immediately. There are rare cases where INDEX will not build due to odd cases involving OPTIONS_SET being set in make.conf. If you suspect that this is the case, try to make INDEX with those variables turned off before reporting it to FreeBSD ports mailing list. I updated the sources, now how do I update my installed ports? FreeBSD does not include a port upgrading tool, but it does have some tools to make the upgrade process somewhat easier. Additional tools are available to simplify port handling and are described the Upgrading Ports section in the FreeBSD Handbook. Do I need to recompile every port each time I perform a major version update? Yes! While a recent system will run with software compiled under an older release, things will randomly crash and fail to work once other ports are installed or updated. When the system is upgraded, various shared libraries, loadable modules, and other parts of the system will be replaced with newer versions. Applications linked against the older versions may fail to start or, in other cases, fail to function properly. For more information, see the section on upgrades in the FreeBSD Handbook. Do I need to recompile every port each time I perform a minor version update? In general, no. FreeBSD developers do their utmost to guarantee binary compatibility across all releases with the same major version number. Any exceptions will be documented in the Release Notes, and advice given there should be followed. Why is /bin/sh so minimal? Why does FreeBSD not use bash or another shell? Many people need to write shell scripts which will be portable across many systems. That is why POSIX specifies the shell and utility commands in great detail. Most scripts are written in Bourne shell (sh1), and because several important programming interfaces (make1, system3, popen3, and analogues in higher-level scripting languages like Perl and Tcl) are specified to use the Bourne shell to interpret commands. Because the Bourne shell is so often and widely used, it is important for it to be quick to start, be deterministic in its behavior, and have a small memory footprint. The existing implementation is our best effort at meeting as many of these requirements simultaneously as we can. To keep /bin/sh small, we have not provided many of the convenience features that other shells have. That is why other more featureful shells like bash, scsh, tcsh1, and zsh are available. Compare the memory utilization of these shells by looking at the VSZ and RSS columns in a ps -u listing. How do I create audio CDs from my MIDI files? To create audio CDs from MIDI files, first install audio/timidity++ from ports then install manually the GUS patches set by Eric A. Welsh, available at http://alleg.sourceforge.net/digmid.html. After TiMidity++ has been installed properly, MIDI files may be converted to WAV files with the following command line: % timidity -Ow -s 44100 -o /tmp/juke/01.wav 01.mid The WAV files can then be converted to other formats or burned onto audio CDs, as described in the FreeBSD Handbook. Kernel Configuration I would like to customize my kernel. Is it difficult? Not at all! Check out the kernel config section of the Handbook. The new kernel will be installed to the /boot/kernel directory along with its modules, while the old kernel and its modules will be moved to the /boot/kernel.old directory. If a mistake is made in the configuration, simply boot the previous version of the kernel. Why is my kernel so big? GENERIC kernels shipped with FreeBSD are compiled in debug mode. Kernels built in debug mode contain debug data in separate files that are used for debugging. FreeBSD releases prior to 11.0 store these debug files in the same directory as the kernel itself, /boot/kernel/. In FreeBSD 11.0 and later the debug files are stored in /usr/lib/debug/boot/kernel/. Note that there will be little or no performance loss from running a debug kernel, and it is useful to keep one around in case of a system panic. When running low on disk space, there are different options to reduce the size of /boot/kernel/ and /usr/lib/debug/. To not install the symbol files, make sure the following line exists in /etc/src.conf: WITHOUT_KERNEL_SYMBOLS=yes For more information see src.conf5. If you want to avoid building debug files altogether, make sure that both of the following are true: This line does not exist in the kernel configuration file: makeoptions DEBUG=-g Do not run config8 with . Either of the above settings will cause the kernel to be built in debug mode. To build and install only the specified modules, list them in /etc/make.conf: MODULES_OVERRIDE= accf_http ipfw Replace accf_httpd ipfw with a list of needed modules. Only the listed modules will be built. This reduces the size of the kernel directory and decreases the amount of time needed to build the kernel. For more information, read /usr/share/examples/etc/make.conf. Unneeded devices can be removed from the kernel to further reduce the size. See for more information. To put any of these options into effect, follow the instructions to build and install the new kernel. For reference, the FreeBSD 11 amd64 kernel (/boot/kernel/kernel) is approximately 25 MB. Why does every kernel I try to build fail to compile, even GENERIC? There are a number of possible causes for this problem: The source tree is different from the one used to build the currently running system. When attempting an upgrade, read /usr/src/UPDATING, paying particular attention to the COMMON ITEMS section at the end. The make buildkernel did not complete successfully. The make buildkernel target relies on files generated by the make buildworld target to complete its job correctly. Even when building FreeBSD-STABLE, it is possible that the source tree was fetched at a time when it was either being modified or it was broken. Only releases are guaranteed to be buildable, although FreeBSD-STABLE builds fine the majority of the time. Try re-fetching the source tree and see if the problem goes away. Try using a different mirror in case the previous one is having problems. Which scheduler is in use on a running system? The name of the scheduler currently being used is directly available as the value of the kern.sched.name sysctl: % sysctl kern.sched.name kern.sched.name: ULE What is kern.sched.quantum? kern.sched.quantum is the maximum number of ticks a process can run without being preempted in the 4BSD scheduler. Disks, File Systems, and Boot Loaders How can I add my new hard disk to my FreeBSD system? See the Adding Disks section in the FreeBSD Handbook. How do I move my system over to my huge new disk? The best way is to reinstall the operating system on the new disk, then move the user data over. This is highly recommended when tracking -STABLE for more than one release or when updating a release instead of installing a new one. Install booteasy on both disks with boot0cfg8 and dual boot until you are happy with the new configuration. Skip the next paragraph to find out how to move the data after doing this. Alternatively, partition and label the new disk with either sade8 or gpart8. If the disks are MBR-formatted, booteasy can be installed on both disks with boot0cfg8 so that the computer can dual boot to the old or new system after the copying is done. Once the new disk set up, the data cannot just be copied. Instead, use tools that understand device files and system flags, such as dump8. Although it is recommended to move the data while in single-user mode, it is not required. When the disks are formatted with UFS, never use anything but dump8 and restore8 to move the root file system. These commands should also be used when moving a single partition to another empty partition. The sequence of steps to use dump to move the data from one UFS partitions to a new partition is: newfs the new partition. mount it on a temporary mount point. cd to that directory. dump the old partition, piping output to the new one. For example, to move /dev/ada1s1a with /mnt as the temporary mount point, type: # newfs /dev/ada1s1a # mount /dev/ada1s1a /mnt # cd /mnt # dump 0af - / | restore rf - Rearranging partitions with dump takes a bit more work. To merge a partition like /var into its parent, create the new partition large enough for both, move the parent partition as described above, then move the child partition into the empty directory that the first move created: # newfs /dev/ada1s1a # mount /dev/ada1s1a /mnt # cd /mnt # dump 0af - / | restore rf - # cd var # dump 0af - /var | restore rf - To split a directory from its parent, say putting /var on its own partition when it was not before, create both partitions, then mount the child partition on the appropriate directory in the temporary mount point, then move the old single partition: # newfs /dev/ada1s1a # newfs /dev/ada1s1d # mount /dev/ada1s1a /mnt # mkdir /mnt/var # mount /dev/ada1s1d /mnt/var # cd /mnt # dump 0af - / | restore rf - The cpio1 and pax1 utilities are also available for moving user data. These are known to lose file flag information, so use them with caution. Which partitions can safely use Soft Updates? I have heard that Soft Updates on / can cause problems. What about Journaled Soft Updates? Short answer: Soft Updates can usually be safely used on all partitions. Long answer: Soft Updates has two characteristics that may be undesirable on certain partitions. First, a Soft Updates partition has a small chance of losing data during a system crash. The partition will not be corrupted as the data will simply be lost. Second, Soft Updates can cause temporary space shortages. When using Soft Updates, the kernel can take up to thirty seconds to write changes to the physical disk. When a large file is deleted the file still resides on disk until the kernel actually performs the deletion. This can cause a very simple race condition. Suppose one large file is deleted and another large file is immediately created. The first large file is not yet actually removed from the physical disk, so the disk might not have enough room for the second large file. This will produce an error that the partition does not have enough space, even though a large chunk of space has just been released. A few seconds later, the file creation works as expected. If a system should crash after the kernel accepts a chunk of data for writing to disk, but before that data is actually written out, data could be lost. This risk is extremely small, but generally manageable. These issues affect all partitions using Soft Updates. So, what does this mean for the root partition? Vital information on the root partition changes very rarely. If the system crashed during the thirty-second window after such a change is made, it is possible that data could be lost. This risk is negligible for most applications, but be aware that it exists. If the system cannot tolerate this much risk, do not use Soft Updates on the root file system! / is traditionally one of the smallest partitions. If /tmp is on /, there may be intermittent space problems. Symlinking /tmp to /var/tmp will solve this problem. Finally, dump8 does not work in live mode (-L) on a filesystem, with Journaled Soft Updates (SU+J). Can I mount other foreign file systems under FreeBSD? FreeBSD supports a variety of other file systems. UFS UFS CD-ROMs can be mounted directly on FreeBSD. Mounting disk partitions from Digital UNIX and other systems that support UFS may be more complex, depending on the details of the disk partitioning for the operating system in question. ext2/ext3 FreeBSD supports ext2fs and ext3fs partitions. See ext2fs5 for more information. NTFS FUSE based NTFS support is available as a port (sysutils/fusefs-ntfs). For more information see ntfs-3g. FAT FreeBSD includes a read-write FAT driver. For more information, see mount_msdosfs8. ZFS FreeBSD 包含由 Sun 移植過來的 ZFS 驅動程式。 目前的建議是僅在記憶體充足的 amd64 平臺上使用它。有關更詳細資訊, 請參閱 zfs8。 FreeBSD includes the Network File System NFS and the FreeBSD Ports Collection provides several FUSE applications to support many other file systems. How do I mount a secondary DOS partition? The secondary DOS partitions are found after all the primary partitions. For example, if E is the second DOS partition on the second SCSI drive, there will be a device file for slice 5 in /dev. To mount it: # mount -t msdosfs /dev/da1s5 /dos/e Is there a cryptographic file system for FreeBSD? Yes, gbde8 and geli8. See the Encrypting Disk Partitions section of the FreeBSD Handbook. How do I boot FreeBSD and Linux using GRUB? To boot FreeBSD using GRUB, add the following to either /boot/grub/menu.lst or /boot/grub/grub.conf, depending upon which is used by the Linux distribution. title FreeBSD 9.1 root (hd0,a) kernel /boot/loader Where hd0,a points to the root partition on the first disk. To specify the slice number, use something like this (hd0,2,a). By default, if the slice number is omitted, GRUB searches the first slice which has the a partition. How do I boot FreeBSD and Linux using BootEasy? Install LILO at the start of the Linux boot partition instead of in the Master Boot Record. You can then boot LILO from BootEasy. This is recommended when running Windows and Linux as it makes it simpler to get Linux booting again if Windows is reinstalled. How do I change the boot prompt from ??? to something more meaningful? This cannot be accomplished with the standard boot manager without rewriting it. There are a number of other boot managers in the sysutils category of the Ports Collection. How do I use a new removable drive? If the drive already has a file system on it, use a command like this: # mount -t msdosfs /dev/da0s1 /mnt If the drive will only be used with FreeBSD systems, partition it with UFS or ZFS. This will provide long filename support, improvement in performance, and stability. If the drive will be used by other operating systems, a more portable choice, such as msdosfs, is better. # dd if=/dev/zero of=/dev/da0 count=2 # gpart create -s GPT /dev/da0 # gpart add -t freebsd-ufs /dev/da0 Finally, create a new file system: # newfs /dev/da0p1 and mount it: # mount /dev/da0s1 /mnt It is a good idea to add a line to /etc/fstab (see fstab5) so you can just type mount /mnt in the future: /dev/da0p1 /mnt ufs rw,noauto 0 0 Why do I get Incorrect super block when mounting a CD? The type of device to mount must be specified. This is described in the Handbook section on Using Data CDs. Why do I get Device not configured when mounting a CD? This generally means that there is no CD in the drive, or the drive is not visible on the bus. Refer to the Using Data CDs section of the Handbook for a detailed discussion of this issue. Why do all non-English characters in filenames show up as ? on my CDs when mounted in FreeBSD? The CD probably uses the Joliet extension for storing information about files and directories. This is discussed in the Handbook section on Using Data CD-ROMs. A CD burned under FreeBSD cannot be read under any other operating system. Why? This means a raw file was burned to the CD, rather than creating an ISO 9660 file system. Take a look at the Handbook section on Using Data CDs. How can I create an image of a data CD? This is discussed in the Handbook section on Writing Data to an ISO File System. For more on working with CD-ROMs, see the Creating CDs Section in the Storage chapter in the Handbook. Why can I not mount an audio CD? Trying to mount an audio CD will produce an error like cd9660: /dev/cd0: Invalid argument. This is because mount only works on file systems. Audio CDs do not have file systems; they just have data. Instead, use a program that reads audio CDs, such as the audio/xmcd package or port. How do I mount a multi-session CD? By default, mount8 will attempt to mount the last data track (session) of a CD. To load an earlier session, use the command line argument. Refer to mount_cd96608 for specific examples. How do I let ordinary users mount CD-ROMs, DVDs, USB drives, and other removable media? As root set the sysctl variable vfs.usermount to 1. # sysctl vfs.usermount=1 To make this persist across reboots, add the line vfs.usermount=1 to /etc/sysctl.conf so that it is reset at system boot time. Users can only mount devices they have read permissions to. To allow users to mount a device permissions must be set in /etc/devfs.conf. For example, to allow users to mount the first USB drive add: # Allow all users to mount a USB drive. own /dev/da0 root:operator perm /dev/da0 0666 All users can now mount devices they could read onto a directory that they own: % mkdir ~/my-mount-point % mount -t msdosfs /dev/da0 ~/my-mount-point Unmounting the device is simple: % umount ~/my-mount-point Enabling vfs.usermount, however, has negative security implications. A better way to access MS-DOS formatted media is to use the emulators/mtools package in the Ports Collection. The device name used in the previous examples must be changed according to the configuration. The du and df commands show different amounts of disk space available. What is going on? This is due to how these commands actually work. du goes through the directory tree, measures how large each file is, and presents the totals. df just asks the file system how much space it has left. They seem to be the same thing, but a file without a directory entry will affect df but not du. When a program is using a file, and the file is deleted, the file is not really removed from the file system until the program stops using it. The file is immediately deleted from the directory listing, however. As an example, consider a file large enough to affect the output of du and df. A file being viewed with more can be deleted wihout causing an error. The entry is removed from the directory so no other program or user can access it. However, du shows that it is gone as it has walked the directory tree and the file is not listed. df shows that it is still there, as the file system knows that more is still using that space. Once the more session ends, du and df will agree. This situation is common on web servers. Many people set up a FreeBSD web server and forget to rotate the log files. The access log fills up /var. The new administrator deletes the file, but the system still complains that the partition is full. Stopping and restarting the web server program would free the file, allowing the system to release the disk space. To prevent this from happening, set up newsyslog8. Note that Soft Updates can delay the freeing of disk space and it can take up to 30 seconds for the change to be visible. How can I add more swap space? This section of the Handbook describes how to do this. Why does FreeBSD see my disk as smaller than the manufacturer says it is? Disk manufacturers calculate gigabytes as a billion bytes each, whereas FreeBSD calculates them as 1,073,741,824 bytes each. This explains why, for example, FreeBSD's boot messages will report a disk that supposedly has 80 GB as holding 76,319 MB. Also note that FreeBSD will (by default) reserve 8% of the disk space. How is it possible for a partition to be more than 100% full? A portion of each UFS partition (8%, by default) is reserved for use by the operating system and the root user. df1 does not count that space when calculating the Capacity column, so it can exceed 100%. Notice that the Blocks column is always greater than the sum of the Used and Avail columns, usually by a factor of 8%. For more details, look up in tunefs8. ZFS 使用 ZFS 最少需要多少記憶體？ 至少需要 4GB 的記憶體才能跑得順，但不同的工作負載可能會造成相當大的差異。 ZIL 是什麼而又何時會被使用？ The ZIL (ZFS 動向日誌) 是一個紀錄日誌，用以實現系統當機時 POSIX 寫入保證的語義，多個正常 ZFS 寫入動作會被分成多個交易處理群組，並在交易處理群組被填滿時寫入磁碟 (Transaction Group Commit)。然而像 fsync2 這樣的系統呼叫，會要求該系統呼叫在返回前，能承諾已將資料寫入磁碟，ZIL 就是用來紀錄確認為已執行寫入的資料，但其實尚未存在於磁碟上，即尚未完成交易處理，交易處理群組具有時間戳記，在系統當機後，找到 ZIL 最後一個有效的時間戳記，即將遺失的資料再舍併至磁碟上。 我需要用固態硬碟 (SSD) 來存 ZIL 嗎？ ZFS 預設將 ZIL 儲存在包含所有資料的 zpool 中，如果應用程式的寫入負載很重，將 ZIL 儲存在同步速度非常快的獨立設備中，藉由循序寫入效能的提高可以改善整個系統的效能，對於其他類型的工作負載， 固態硬碟就不會有太大的助益。 L2ARC 是什麼？ The L2ARC (Second Level Adaptive Replacement Cache) 是存於快速儲存設備 SSD 上的讀取快取，此快取在重新開機後會消失，請注意記憶體是第一層的快取，只有在記憶體不足的情況下才需要 L2ARC。 L2ARC 需要 ARC 的空間來為其製作索引，因此，有一種反常的情況，如果有一種工作集 (working set) 可以完美地剛好放入 ARC，一旦系統使用 L2ARC，該工作集的運作將不再完美，因為 ARC 需要用一部分空間來保存 L2ARC 的索引，以至於必須將工作集的一部分存入比記憶體慢的 L2ARC。 建議啟用去冗餘 (deduplication) 嗎？ 一般而言，不建議這麼做。 去冗餘需要相當多的記憶體，而且會讓讀寫磁碟所需的時間變長，除非磁碟上儲存了非常多重複的資料，例如：虛擬機的映像檔或者是使用者的備份資料，否則開啟去冗餘可能弊大於利。另一個需要考量的狀況是：啟用去冗餘功能之後再將其關閉，無法將磁碟上去冗餘的狀態立即逆轉，必須等到下次修改了之前被去冗餘的資料，變更的區塊才會再被複製一份。 去冗餘也可能會導致某些非預期的情況，特別是刪除檔案時可能會慢很多。 在我建立的 ZFS pool 中無法刪除和新增檔案，應該怎麼修復？ 這很有可能是該 pool 的空間使用率已達 100% 滿了，因 ZFS 需要儲存空間以將紀錄交易處理的輔助資料 (metadata) 寫入，為了讓該 pool 回復至可用狀態，必須用檔案切除的方法 (truncate 命令) 刪除不重要的檔案： % truncate -s 0 unimportant-file 因為檔案切除不需要建立交易處理紀錄，並能釋放出可使用的磁碟區塊。 如果系統曾進行過額外的 ZFS dataset 調校，例如：去冗餘，釋放出來的空間也許不會立即可得。 ZFS 支援固態硬碟 (SSD) 的 TRIM 功能嗎？ 自 FreeBSD 10-CURRENT 修定 r240868 開始，就支援 ZFS TRIM。ZFS TRIM 的支援分別已在 r252162 和 r251419 的修訂，加進所有 FreeBSD-STABLE 分支。 ZFS TRIM 預設就已開啟，也可以將其關閉，只要加入一行設定到 /etc/sysctl.conf: vfs.zfs.trim.enabled=0 ZFS TRIM 也可能某些設定中會無效，例如：在採用 GELI 裝置上的 ZFS 檔案系統。 System Administration Where are the system start-up configuration files? The primary configuration file is /etc/defaults/rc.conf which is described in rc.conf5. System startup scripts such as /etc/rc and /etc/rc.d, which are described in rc8, include this file. Do not edit this file! Instead, to edit an entry in /etc/defaults/rc.conf, copy the line into /etc/rc.conf and change it there. For example, if to start named8, the included DNS server: # echo 'named_enable="YES"' >> /etc/rc.conf To start up local services, place shell scripts in the /usr/local/etc/rc.d directory. These shell scripts should be set executable, the default file mode is 555. How do I add a user easily? Use the adduser8 command, or the pw8 command for more complicated situations. To remove the user, use the rmuser8 command or, if necessary, pw8. Why do I keep getting messages like root: not found after editing /etc/crontab? This is normally caused by editing the system crontab. This is not the correct way to do things as the system crontab has a different format to the per-user crontabs. The system crontab has an extra field, specifying which user to run the command as. cron8 assumes this user is the first word of the command to execute. Since no such command exists, this error message is displayed. To delete the extra, incorrect crontab: # crontab -r Why do I get the error, you are not in the correct group to su root when I try to su to root? This is a security feature. In order to su to root, or any other account with superuser privileges, the user account must be a member of the wheel group. If this feature were not there, anybody with an account on a system who also found out root's password would be able to gain superuser level access to the system. To allow someone to su to root, put them in the wheel group using pw: # pw groupmod wheel -m lisa The above example will add user lisa to the group wheel. I made a mistake in rc.conf, or another startup file, and now I cannot edit it because the file system is read-only. What should I do? Restart the system using boot -s at the loader prompt to enter single-user mode. When prompted for a shell pathname, press Enter and run mount -urw / to re-mount the root file system in read/write mode. You may also need to run mount -a -t ufs to mount the file system where your favorite editor is defined. If that editor is on a network file system, either configure the network manually before mounting the network file systems, or use an editor which resides on a local file system, such as ed1. In order to use a full screen editor such as vi1 or emacs1, run export TERM=xterm so that these editors can load the correct data from the termcap5 database. After performing these steps, edit /etc/rc.conf to fix the syntax error. The error message displayed immediately after the kernel boot messages should indicate the number of the line in the file which is at fault. Why am I having trouble setting up my printer? See the Handbook entry on printing for troubleshooting tips. How can I correct the keyboard mappings for my system? Refer to the Handbook section on using localization, specifically the section on console setup. Why can I not get user quotas to work properly? It is possible that the kernel is not configured to use quotas. In this case, add the following line to the kernel configuration file and recompile the kernel: options QUOTA Refer to the Handbook entry on quotas for full details. Do not turn on quotas on /. Put the quota file on the file system that the quotas are to be enforced on: File System Quota file /usr /usr/admin/quotas /home /home/admin/quotas … … Does FreeBSD support System V IPC primitives? Yes, FreeBSD supports System V-style IPC, including shared memory, messages and semaphores, in the GENERIC kernel. With a custom kernel, support may be loaded with the sysvshm.ko, sysvsem.ko and sysvmsg.ko kernel modules, or enabled in the custom kernel by adding the following lines to the kernel configuration file: options SYSVSHM # enable shared memory options SYSVSEM # enable for semaphores options SYSVMSG # enable for messaging Recompile and install the kernel. What other mail-server software can I use instead of Sendmail? The Sendmail server is the default mail-server software for FreeBSD, but it can be replaced with another MTA installed from the Ports Collection. Available ports include mail/exim, mail/postfix, and mail/qmail. Search the mailing lists for discussions regarding the advantages and disadvantages of the available MTAs. I have forgotten the root password! What do I do? Do not panic! Restart the system, type boot -s at the Boot: prompt to enter single-user mode. At the question about the shell to use, hit Enter which will display a # prompt. Enter mount -urw / to remount the root file system read/write, then run mount -a to remount all the file systems. Run passwd root to change the root password then run exit1 to continue booting. If you are still prompted to give the root password when entering the single-user mode, it means that the console has been marked as insecure in /etc/ttys. In this case, it will be required to boot from a FreeBSD installation disk, choose the Live CD or Shell at the beginning of the install process and issue the commands mentioned above. Mount the specific partition in this case and then chroot to it. For example, replace mount -urw / with mount /dev/ada0p1 /mnt; chroot /mnt for a system on ada0p1. If the root partition cannot be mounted from single-user mode, it is possible that the partitions are encrypted and it is impossible to mount them without the access keys. For more information see the section about encrypted disks in the FreeBSD Handbook. How do I keep ControlAltDelete from rebooting the system? When using syscons4, the default console driver, build and install a new kernel with this line in the configuration file: options SC_DISABLE_REBOOT This can also be done by setting the following sysctl8 which does not require a reboot or kernel recompile: # sysctl hw.syscons.kbd_reboot=0 The above two methods are exclusive: The sysctl8 does not exist if the kernel is compiled with SC_DISABLE_REBOOT. How do I reformat DOS text files to UNIX ones? Use this perl1 command: % perl -i.bak -npe 's/\r\n/\n/g' file(s) where file(s) is one or more files to process. The modification is done in-place, with the original file stored with a .bak extension. Alternatively, use tr1: % tr -d '\r' < dos-text-file > unix-file dos-text-file is the file containing DOS text while unix-file will contain the converted output. This can be quite a bit faster than using perl. Yet another way to reformat DOS text files is to use the converters/dosunix port from the Ports Collection. Consult its documentation about the details. How do I re-read /etc/rc.conf and re-start /etc/rc without a reboot? Go into single-user mode and then back to multi-user mode: # shutdown now # return # exit I tried to update my system to the latest -STABLE, but got -BETAx, -RC or -PRERELEASE! What is going on? Short answer: it is just a name. RC stands for Release Candidate. It signifies that a release is imminent. In FreeBSD, -PRERELEASE is typically synonymous with the code freeze before a release. (For some releases, the -BETA label was used in the same way as -PRERELEASE.) Long answer: FreeBSD derives its releases from one of two places. Major, dot-zero, releases, such as 9.0-RELEASE are branched from the head of the development stream, commonly referred to as -CURRENT. Minor releases, such as 6.3-RELEASE or 5.2-RELEASE, have been snapshots of the active -STABLE branch. Starting with 4.3-RELEASE, each release also now has its own branch which can be tracked by people requiring an extremely conservative rate of development (typically only security advisories). When a release is about to be made, the branch from which it will be derived from has to undergo a certain process. Part of this process is a code freeze. When a code freeze is initiated, the name of the branch is changed to reflect that it is about to become a release. For example, if the branch used to be called 6.2-STABLE, its name will be changed to 6.3-PRERELEASE to signify the code freeze and signify that extra pre-release testing should be happening. Bug fixes can still be committed to be part of the release. When the source code is in shape for the release the name will be changed to 6.3-RC to signify that a release is about to be made from it. Once in the RC stage, only the most critical bugs found can be fixed. Once the release (6.3-RELEASE in this example) and release branch have been made, the branch will be renamed to 6.3-STABLE. For more information on version numbers and the various Subversion branches, refer to the Release Engineering article. I tried to install a new kernel, and the chflags1 failed. How do I get around this? Short answer: the security level is greater than 0. Reboot directly to single-user mode to install the kernel. Long answer: FreeBSD disallows changing system flags at security levels greater than 0. To check the current security level: # sysctl kern.securelevel The security level cannot be lowered in multi-user mode, so boot to single-user mode to install the kernel, or change the security level in /etc/rc.conf then reboot. See the init8 manual page for details on securelevel, and see /etc/defaults/rc.conf and the rc.conf5 manual page for more information on rc.conf. I cannot change the time on my system by more than one second! How do I get around this? Short answer: the system is at a security level greater than 1. Reboot directly to single-user mode to change the date. Long answer: FreeBSD disallows changing the time by more that one second at security levels greater than 1. To check the security level: # sysctl kern.securelevel The security level cannot be lowered in multi-user mode. Either boot to single-user mode to change the date or change the security level in /etc/rc.conf and reboot. See the init8 manual page for details on securelevel, and see /etc/defaults/rc.conf and the rc.conf5 manual page for more information on rc.conf. Why is rpc.statd using 256 MB of memory? No, there is no memory leak, and it is not using 256 MB of memory. For convenience, rpc.statd maps an obscene amount of memory into its address space. There is nothing terribly wrong with this from a technical standpoint; it just throws off things like top1 and ps1. rpc.statd8 maps its status file (resident on /var) into its address space; to save worrying about remapping the status file later when it needs to grow, it maps the status file with a generous size. This is very evident from the source code, where one can see that the length argument to mmap2 is 0x10000000, or one sixteenth of the address space on an IA32, or exactly 256 MB. Why can I not unset the schg file flag? The system is running at securelevel greater than 0. Lower the securelevel and try again. For more information, see the FAQ entry on securelevel and the init8 manual page. What is vnlru? vnlru flushes and frees vnodes when the system hits the kern.maxvnodes limit. This kernel thread sits mostly idle, and only activates when there is a huge amount of RAM and users are accessing tens of thousands of tiny files. What do the various memory states displayed by top mean? Active: pages recently statistically used. Inactive: pages recently statistically unused. Cache: (most often) pages that have percolated from inactive to a status where they maintain their data, but can often be immediately reused (either with their old association, or reused with a new association). There can be certain immediate transitions from active to cache state if the page is known to be clean (unmodified), but that transition is a matter of policy, depending upon the algorithm choice of the VM system maintainer. Free: pages without data content, and can be immediately used in certain circumstances where cache pages might be ineligible. Free pages can be reused at interrupt or process state. Wired: pages that are fixed into memory, usually for kernel purposes, but also sometimes for special use in processes. Pages are most often written to disk (sort of a VM sync) when they are in the inactive state, but active pages can also be synced. This depends upon the CPU tracking of the modified bit being available, and in certain situations there can be an advantage for a block of VM pages to be synced, whether they are active or inactive. In most common cases, it is best to think of the inactive queue to be a queue of relatively unused pages that might or might not be in the process of being written to disk. Cached pages are already synced, not mapped, but available for immediate process use with their old association or with a new association. Free pages are available at interrupt level, but cached or free pages can be used at process state for reuse. Cache pages are not adequately locked to be available at interrupt level. There are some other flags (e.g., busy flag or busy count) that might modify some of the described rules. How much free memory is available? There are a couple of kinds of free memory. One kind is the amount of memory immediately available without paging anything else out. That is approximately the size of cache queue + size of free queue (with a derating factor, depending upon system tuning). Another kind of free memory is the total amount of VM space. That can be complex, but is dependent upon the amount of swap space and memory. Other kinds of free memory descriptions are also possible, but it is relatively useless to define these, but rather it is important to make sure that the paging rate is kept low, and to avoid running out of swap space. What is /var/empty? /var/empty is a directory that the sshd8 program uses when performing privilege separation. The /var/empty directory is empty, owned by root and has the schg flag set. This directory should not be deleted. I just changed /etc/newsyslog.conf. How can I check if it does what I expect? To see what newsyslog8 will do, use the following: % newsyslog -nrvv My time is wrong, how can I change the timezone? Use tzsetup8. The X Window System and Virtual Consoles What is the X Window System? The X Window System (commonly X11) is the most widely available windowing system capable of running on UNIX or UNIX like systems, including FreeBSD. The X.Org Foundation administers the X protocol standards, with the current reference implementation, version 11 release 7.7, so references are often shortened to X11. Many implementations are available for different architectures and operating systems. An implementation of the server-side code is properly known as an X server. I want to run Xorg, how do I go about it? To install Xorg do one of the following: Use the x11/xorg meta-port, which builds and installs every Xorg component. Use x11/xorg-minimal, which builds and installs only the necessary Xorg components. Install Xorg from FreeBSD packages: # pkg install xorg After the installation of Xorg, follow the instructions from the X11 Configuration section of the FreeBSD Handbook. I tried to run X, but I get a No devices detected. error when I type startx. What do I do now? The system is probably running at a raised securelevel. It is not possible to start X at a raised securelevel because X requires write access to io4. For more information, see at the init8 manual page. There are two solutions to the problem: set the securelevel back down to zero or run xdm1 (or an alternative display manager) at boot time before the securelevel is raised. See for more information about running xdm1 at boot time. Why does my mouse not work with X? When using syscons4, the default console driver, FreeBSD can be configured to support a mouse pointer on each virtual screen. To avoid conflicting with X, syscons4 supports a virtual device called /dev/sysmouse. All mouse events received from the real mouse device are written to the sysmouse4 device via moused8. To use the mouse on one or more virtual consoles, and use X, see and set up moused8. Then edit /etc/X11/xorg.conf and make sure the following lines exist: Section "InputDevice" Option "Protocol" "SysMouse" Option "Device" "/dev/sysmouse" ..... Starting with Xorg version 7.4, the InputDevice sections in xorg.conf are ignored in favor of autodetected devices. To restore the old behavior, add the following line to the ServerLayout or ServerFlags section: Option "AutoAddDevices" "false" Some people prefer to use /dev/mouse under X. To make this work, /dev/mouse should be linked to /dev/sysmouse (see sysmouse4) by adding the following line to /etc/devfs.conf (see devfs.conf5): link sysmouse mouse This link can be created by restarting devfs5 with the following command (as root): # service devfs restart My mouse has a fancy wheel. Can I use it in X? Yes, if X is configured for a 5 button mouse. To do this, add the lines Buttons 5 and ZAxisMapping 4 5 to the InputDevice section of /etc/X11/xorg.conf, as seen in this example: Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" Option "Buttons" "5" Option "ZAxisMapping" "4 5" EndSection The mouse can be enabled in Emacsby adding these lines to ~/.emacs: ;; wheel mouse (global-set-key [mouse-4] 'scroll-down) (global-set-key [mouse-5] 'scroll-up) My laptop has a Synaptics touchpad. Can I use it in X? Yes, after configuring a few things to make it work. In order to use the Xorg synaptics driver, first remove moused_enable from rc.conf. To enable synaptics, add the following line to /boot/loader.conf: hw.psm.synaptics_support="1" Add the following to /etc/X11/xorg.conf: Section "InputDevice" Identifier "Touchpad0" Driver "synaptics" Option "Protocol" "psm" Option "Device" "/dev/psm0" EndSection And be sure to add the following into the ServerLayout section: InputDevice "Touchpad0" "SendCoreEvents" How do I use remote X displays? For security reasons, the default setting is to not allow a machine to remotely open a window. To enable this feature, start X with the optional argument: % startx -listen_tcp What is a virtual console and how do I make more? Virtual consoles provide several simultaneous sessions on the same machine without doing anything complicated like setting up a network or running X. When the system starts, it will display a login prompt on the monitor after displaying all the boot messages. Type in your login name and password to start working on the first virtual console. To start another session, perhaps to look at documentation for a program or to read mail while waiting for an FTP transfer to finish, hold down Alt and press F2. This will display the login prompt for the second virtual console. To go back to the original session, press AltF1. The default FreeBSD installation has eight virtual consoles enabled. AltF1, AltF2, AltF3, and so on will switch between these virtual consoles. To enable more of virtual consoles, edit /etc/ttys (see ttys5) and add entries for ttyv8 to ttyvc, after the comment on Virtual terminals: # Edit the existing entry for ttyv8 in /etc/ttys and change # "off" to "on". ttyv8 "/usr/libexec/getty Pc" xterm on secure ttyv9 "/usr/libexec/getty Pc" xterm on secure ttyva "/usr/libexec/getty Pc" xterm on secure ttyvb "/usr/libexec/getty Pc" xterm on secure The more virtual terminals, the more resources that are used. This can be problematic on systems with 8 MB RAM or less. Consider changing secure to insecure. In order to run an X server, at least one virtual terminal must be left to off for it to use. This means that only eleven of the Alt-function keys can be used as virtual consoles so that one is left for the X server. For example, to run X and eleven virtual consoles, the setting for virtual terminal 12 should be: ttyvb "/usr/libexec/getty Pc" xterm off secure The easiest way to activate the virtual consoles is to reboot. How do I access the virtual consoles from X? Use CtrlAltFn to switch back to a virtual console. Press CtrlAltF1 to return to the first virtual console. Once at a text console, use AltFn to move between them. To return to the X session, switch to the virtual console running X. If X was started from the command line using startx, the X session will attach to the next unused virtual console, not the text console from which it was invoked. For eight active virtual terminals, X will run on the ninth, so use AltF9. How do I start XDM on boot? There are two schools of thought on how to start xdm1. One school starts xdm from /etc/ttys (see ttys5) using the supplied example, while the other runs xdm from rc.local (see rc8) or from an X script in /usr/local/etc/rc.d. Both are equally valid, and one may work in situations where the other does not. In both cases the result is the same: X will pop up a graphical login prompt. The ttys5 method has the advantage of documenting which vty X will start on and passing the responsibility of restarting the X server on logout to init8. The rc8 method makes it easy to kill xdm if there is a problem starting the X server. If loaded from rc8, xdm should be started without any arguments. xdm must start after getty8 runs, or else getty and xdm will conflict, locking out the console. The best way around this is to have the script sleep 10 seconds or so then launch xdm. When starting xdm from /etc/ttys, there still is a chance of conflict between xdm and getty8. One way to avoid this is to add the vt number in /usr/local/lib/X11/xdm/Xservers: :0 local /usr/local/bin/X vt4 The above example will direct the X server to run in /dev/ttyv3. Note the number is offset by one. The X server counts the vty from one, whereas the FreeBSD kernel numbers the vty from zero. Why do I get Couldn't open console when I run xconsole? When X is started with startx, the permissions on /dev/console will not get changed, resulting in things like xterm -C and xconsole not working. This is because of the way console permissions are set by default. On a multi-user system, one does not necessarily want just any user to be able to write on the system console. For users who are logging directly onto a machine with a VTY, the fbtab5 file exists to solve such problems. In a nutshell, make sure an uncommented line of the form is in /etc/fbtab (see fbtab5): /dev/ttyv0 0600 /dev/console It will ensure that whomever logs in on /dev/ttyv0 will own the console. Why does my PS/2 mouse misbehave under X? The mouse and the mouse driver may have become out of synchronization. In rare cases, the driver may also erroneously report synchronization errors: psmintr: out of sync (xxxx != yyyy) If this happens, disable the synchronization check code by setting the driver flags for the PS/2 mouse driver to 0x100. This can be easiest achieved by adding hint.psm.0.flags="0x100" to /boot/loader.conf and rebooting. How do I reverse the mouse buttons? Type xmodmap -e "pointer = 3 2 1". Add this command to ~/.xinitrc or ~/.xsession to make it happen automatically. How do I install a splash screen and where do I find them? The detailed answer for this question can be found in the Boot Time Splash Screens section of the FreeBSD Handbook. Can I use the Windows keys on my keyboard in X? Yes. Use xmodmap1 to define which functions the keys should perform. Assuming all Windows keyboards are standard, the keycodes for these three keys are the following: 115 — Windows key, between the left-hand Ctrl and Alt keys 116 — Windows key, to the right of AltGr 117 — Menu, to the left of the right-hand Ctrl To have the left Windows key print a comma, try this. # xmodmap -e "keycode 115 = comma" To have the Windows key-mappings enabled automatically every time X is started, either put the xmodmap commands in ~/.xinitrc or, preferably, create a ~/.xmodmaprc and include the xmodmap options, one per line, then add the following line to ~/.xinitrc: xmodmap $HOME/.xmodmaprc For example, to map the 3 keys to be F13, F14, and F15, respectively. This would make it easy to map them to useful functions within applications or the window manager. To do this, put the following in ~/.xmodmaprc. keycode 115 = F13 keycode 116 = F14 keycode 117 = F15 For the x11-wm/fvwm2 desktop manager, one could map the keys so that F13 iconifies or de-iconifies the window the cursor is in, F14 brings the window the cursor is in to the front or, if it is already at the front, pushes it to the back, and F15 pops up the main Workplace menu even if the cursor is not on the desktop, which is useful when no part of the desktop is visible. The following entries in ~/.fvwmrc implement the aforementioned setup: Key F13 FTIWS A Iconify Key F14 FTIWS A RaiseLower Key F15 A A Menu Workplace Nop How can I get 3D hardware acceleration for OpenGL? The availability of 3D acceleration depends on the version of Xorg and the type of video chip. For an nVidia chip, use the binary drivers provided for FreeBSD by installing one of the following ports: The latest versions of nVidia cards are supported by the x11/nvidia-driver port. Older drivers are available as x11/nvidia-driver-### nVidia provides detailed information on which card is supported by which driver on their web site: http://www.nvidia.com/object/IO_32667.html. For Matrox G200/G400, check the x11-drivers/xf86-video-mga port. For ATI Rage 128 and Radeon see ati4, r1284 and radeon4. Networking Where can I get information on diskless booting? Diskless booting means that the FreeBSD box is booted over a network, and reads the necessary files from a server instead of its hard disk. For full details, see the Handbook entry on diskless booting. Can a FreeBSD box be used as a dedicated network router? Yes. Refer to the Handbook entry on advanced networking, specifically the section on routing and gateways. Can I connect my Windows box to the Internet via FreeBSD? Typically, people who ask this question have two PCs at home, one with FreeBSD and one with some version of Windows the idea is to use the FreeBSD box to connect to the Internet and then be able to access the Internet from the Windows box through the FreeBSD box. This is really just a special case of the previous question and works perfectly well. Dialup users must use and set gateway_enable to YES in /etc/rc.conf. For more information, refer to ppp8 or the Handbook entry on user PPP. If the connection to the Internet is over Ethernet, use natd8. A tutorial can be found in the natd section of the Handbook. Does FreeBSD support PPP? Yes. ppp8 provides support for both incoming and outgoing connections. For more information on how to use this, refer to the Handbook chapter on PPP. Does FreeBSD support NAT or Masquerading? Yes. For instructions on how to use NAT over a PPP connection, see the Handbook entry on PPP. To use NAT over some other sort of network connection, look at the natd section of the Handbook. How can I set up Ethernet aliases? If the alias is on the same subnet as an address already configured on the interface, add netmask 0xffffffff to this command: # ifconfig ed0 alias 192.0.2.2 netmask 0xffffffff Otherwise, specify the network address and netmask as usual: # ifconfig ed0 alias 172.16.141.5 netmask 0xffffff00 More information can be found in the FreeBSD Handbook. Why can I not NFS-mount from a Linux box? Some versions of the Linux NFS code only accept mount requests from a privileged port; try to issue the following command: # mount -o -P linuxbox:/blah /mnt Why does mountd keep telling me it can't change attributes and that I have a bad exports list on my FreeBSD NFS server? The most frequent problem is not understanding the correct format of /etc/exports. Review exports5 and the NFS entry in the Handbook, especially the section on configuring NFS. How do I enable IP multicast support? Install the net/mrouted package or port and add mrouted_enable="YES" to /etc/rc.conf start this service at boot time. Why do I have to use the FQDN for hosts on my site? See the answer in the FreeBSD Handbook. Why do I get an error, Permission denied, for all networking operations? If the kernel is compiled with the IPFIREWALL option, be aware that the default policy is to deny all packets that are not explicitly allowed. If the firewall is unintentionally misconfigured, restore network operability by typing the following as root: # ipfw add 65534 allow all from any to any Consider setting firewall_type="open" in /etc/rc.conf. For further information on configuring this firewall, see the Handbook chapter. Why is my ipfw fwd rule to redirect a service to another machine not working? Possibly because network address translation (NAT) is needed instead of just forwarding packets. A fwd rule only forwards packets, it does not actually change the data inside the packet. Consider this rule: 01000 fwd 10.0.0.1 from any to foo 21 When a packet with a destination address of foo arrives at the machine with this rule, the packet is forwarded to 10.0.0.1, but it still has the destination address of foo. The destination address of the packet is not changed to 10.0.0.1. Most machines would probably drop a packet that they receive with a destination address that is not their own. Therefore, using a fwd rule does not often work the way the user expects. This behavior is a feature and not a bug. See the FAQ about redirecting services, the natd8 manual, or one of the several port redirecting utilities in the Ports Collection for a correct way to do this. How can I redirect service requests from one machine to another? FTP and other service requests can be redirected with the sysutils/socket package or port. Replace the entry for the service in /etc/inetd.conf to call socket, as seen in this example for ftpd: ftp stream tcp nowait nobody /usr/local/bin/socket socket ftp.example.com ftp where ftp.example.com and ftp are the host and port to redirect to, respectively. Where can I get a bandwidth management tool? There are three bandwidth management tools available for FreeBSD. dummynet4 is integrated into FreeBSD as part of ipfw4. ALTQ has been integrated into FreeBSD as part of pf4. Bandwidth Manager from Emerging Technologies is a commercial product. Why do I get /dev/bpf0: device not configured? The running application requires the Berkeley Packet Filter (bpf4), but it was removed from a custom kernel. Add this to the kernel config file and build a new kernel: device bpf # Berkeley Packet Filter How do I mount a disk from a Windows machine that is on my network, like smbmount in Linux? Use the SMBFS toolset. It includes a set of kernel modifications and a set of userland programs. The programs and information are available as mount_smbfs8 in the base system. What are these messages about: Limiting icmp/open port/closed port response in my log files? This kernel message indicates that some activity is provoking it to send a large amount of ICMP or TCP reset (RST) responses. ICMP responses are often generated as a result of attempted connections to unused UDP ports. TCP resets are generated as a result of attempted connections to unopened TCP ports. Among others, these are the kinds of activities which may cause these messages: Brute-force denial of service (DoS) attacks (as opposed to single-packet attacks which exploit a specific vulnerability). Port scans which attempt to connect to a large number of ports (as opposed to only trying a few well-known ports). The first number in the message indicates how many packets the kernel would have sent if the limit was not in place, and the second indicates the limit. This limit is controlled using net.inet.icmp.icmplim. This example sets the limit to 300 packets per second: # sysctl net.inet.icmp.icmplim=300 To disable these messages without disabling response limiting, use net.inet.icmp.icmplim_output to disable the output: # sysctl net.inet.icmp.icmplim_output=0 Finally, to disable response limiting completely, set net.inet.icmp.icmplim to 0. Disabling response limiting is discouraged for the reasons listed above. What are these arp: unknown hardware address format error messages? This means that some device on the local Ethernet is using a MAC address in a format that FreeBSD does not recognize. This is probably caused by someone experimenting with an Ethernet card somewhere else on the network. This is most commonly seen on cable modem networks. It is harmless, and should not affect the performance of the FreeBSD system. Why do I keep seeing messages like: 192.168.0.10 is on fxp1 but got reply from 00:15:17:67:cf:82 on rl0, and how do I disable it? Because a packet is coming from outside the network unexpectedly. To disable them, set net.link.ether.inet.log_arp_wrong_iface to 0. How do I compile an IPv6 only kernel? Configure your kernel with these settings: include GENERIC ident GENERIC-IPV6ONLY makeoptions MKMODULESENV+="WITHOUT_INET_SUPPORT=" nooptions INET nodevice gre Security What is a sandbox? Sandbox is a security term. It can mean two things: A process which is placed inside a set of virtual walls that are designed to prevent someone who breaks into the process from being able to break into the wider system. The process is only able to run inside the walls. Since nothing the process does in regards to executing code is supposed to be able to breach the walls, a detailed audit of its code is not needed in order to be able to say certain things about its security. The walls might be a user ID, for example. This is the definition used in the security7 and named8 man pages. Take the ntalk service, for example (see inetd8). This service used to run as user ID root. Now it runs as user ID tty. The tty user is a sandbox designed to make it more difficult for someone who has successfully hacked into the system via ntalk from being able to hack beyond that user ID. A process which is placed inside a simulation of the machine. It means that someone who is able to break into the process may believe that he can break into the wider machine but is, in fact, only breaking into a simulation of that machine and not modifying any real data. The most common way to accomplish this is to build a simulated environment in a subdirectory and then run the processes in that directory chrooted so that / for that process is this directory, not the real / of the system). Another common use is to mount an underlying file system read-only and then create a file system layer on top of it that gives a process a seemingly writeable view into that file system. The process may believe it is able to write to those files, but only the process sees the effects — other processes in the system do not, necessarily. An attempt is made to make this sort of sandbox so transparent that the user (or hacker) does not realize that he is sitting in it. UNIX implements two core sandboxes. One is at the process level, and one is at the userid level. Every UNIX process is completely firewalled off from every other UNIX process. One process cannot modify the address space of another. A UNIX process is owned by a particular userid. If the user ID is not the root user, it serves to firewall the process off from processes owned by other users. The user ID is also used to firewall off on-disk data. What is securelevel? securelevel is a security mechanism implemented in the kernel. When the securelevel is positive, the kernel restricts certain tasks; not even the superuser (root) is allowed to do them. The securelevel mechanism limits the ability to: Unset certain file flags, such as schg (the system immutable flag). Write to kernel memory via /dev/mem and /dev/kmem. Load kernel modules. Alter firewall rules. To check the status of the securelevel on a running system: # sysctl -n kern.securelevel The output contains the current value of the securelevel. If it is greater than 0, at least some of the securelevel's protections are enabled. The securelevel of a running system cannot be lowered as this would defeat its purpose. If a task requires that the securelevel be non-positive, change the kern_securelevel and kern_securelevel_enable variables in /etc/rc.conf and reboot. For more information on securelevel and the specific things all the levels do, consult init8. Securelevel is not a silver bullet; it has many known deficiencies. More often than not, it provides a false sense of security. One of its biggest problems is that in order for it to be at all effective, all files used in the boot process up until the securelevel is set must be protected. If an attacker can get the system to execute their code prior to the securelevel being set (which happens quite late in the boot process since some things the system must do at start-up cannot be done at an elevated securelevel), its protections are invalidated. While this task of protecting all files used in the boot process is not technically impossible, if it is achieved, system maintenance will become a nightmare since one would have to take the system down, at least to single-user mode, to modify a configuration file. This point and others are often discussed on the mailing lists, particularly the FreeBSD security mailing list. Search the archives here for an extensive discussion. A more fine-grained mechanism is preferred. BIND9 (named) is listening on some high-numbered ports. What is going on? BIND uses a random high-numbered port for outgoing queries. Recent versions of it choose a new, random UDP port for each query. This may cause problems for some network configurations, especially if a firewall blocks incoming UDP packets on particular ports. To get past that firewall, try the avoid-v4-udp-ports and avoid-v6-udp-ports options to avoid selecting random port numbers within a blocked range. If a port number (like 53) is specified via the query-source or query-source-v6 options in /usr/local/etc/namedb/named.conf, randomized port selection will not be used. It is strongly recommended that these options not be used to specify fixed port numbers. Congratulations, by the way. It is good practice to read sockstat1 output and notice odd things! The Sendmail daemon is listening on port 587 as well as the standard port 25! What is going on? Recent versions of Sendmail support a mail submission feature that runs over port 587. This is not yet widely supported, but is growing in popularity. What is this UID 0 toor account? Have I been compromised? Do not worry. toor is an alternative superuser account, where toor is root spelled backwards. It is intended to be used with a non-standard shell so the default shell for root does not need to change. This is important as shells which are not part of the base distribution, but are instead installed from ports or packages, are installed in /usr/local/bin which, by default, resides on a different file system. If root's shell is located in /usr/local/bin and the file system containing /usr/local/bin) is not mounted, root will not be able to log in to fix a problem and will have to reboot into single-user mode in order to enter the path to a shell. Some people use toor for day-to-day root tasks with a non-standard shell, leaving root, with a standard shell, for single-user mode or emergencies. By default, a user cannot log in using toor as it does not have a password, so log in as root and set a password for toor before using it to login. PPP I cannot make ppp8 work. What am I doing wrong? First, read ppp8 and the PPP section of the Handbook. To assist in troubleshooting, enable logging with the following command: set log Phase Chat Connect Carrier lcp ipcp ccp command This command may be typed at the ppp8 command prompt or it may be entered at the start of the default section in /etc/ppp/ppp.conf. Make sure that /etc/syslog.conf contains the lines below and the file /var/log/ppp.log exists: !ppp *.* /var/log/ppp.log A lot about what is going can be learned from the log file. Do not worry if it does not all make sense as it may make sense to someone else. Why does ppp8 hang when I run it? This is usually because the hostname will not resolve. The best way to fix this is to make sure that /etc/hosts is read first by the by ensuring that the hosts line is listed first in /etc/host.conf. Then, put an entry in /etc/hosts for the local machine. If there is no local network, change the localhost line: 127.0.0.1 foo.example.com foo localhost Otherwise, add another entry for the host. Consult the relevant manual pages for more details. When finished, verify that this command is successful: ping -c1 `hostname`. Why will ppp8 not dial in -auto mode? First, check that a default route exists. This command should display two entries: Destination Gateway Flags Refs Use Netif Expire default 10.0.0.2 UGSc 0 0 tun0 10.0.0.2 10.0.0.1 UH 0 0 tun0 If a default route is not listed, make sure that the HISADDR line has been added to /etc/ppp/ppp.conf. Another reason for the default route line being missing is that a default route has been added to /etc/rc.conf and this line is missing from /etc/ppp/ppp.conf: delete ALL If this is the case, go back to the Final System Configuration section of the Handbook. What does No route to host mean? This error is usually because the following section is missing in /etc/ppp/ppp.linkup: MYADDR: delete ALL add 0 0 HISADDR This is only necessary for a dynamic IP address or when the address of the default gateway is unknown. When using interactive mode, the following can be typed in after entering packet mode. Packet mode is indicated by the capitalized PPP in the prompt: delete ALL add 0 0 HISADDR Refer to the PPP and Dynamic IP addresses section of the Handbook for further details. Why does my connection drop after about 3 minutes? The default PPP timeout is 3 minutes. This can be adjusted with the following line: set timeout NNN where NNN is the number of seconds of inactivity before the connection is closed. If NNN is zero, the connection is never closed due to a timeout. It is possible to put this command in ppp.conf, or to type it at the prompt in interactive mode. It is also possible to adjust it on the fly while the line is active by connecting to ppp's server socket using telnet1 or pppctl8. Refer to the ppp8 man page for further details. Why does my connection drop under heavy load? If Link Quality Reporting (LQR) is configured, it is possible that too many LQR packets are lost between the FreeBSD system and the peer. ppp8 deduces that the line must therefore be bad, and disconnects. LQR is disabled by default and can be enabled with the following line: enable lqr Why does my connection drop after a random amount of time? Sometimes, on a noisy phone line or even on a line with call waiting enabled, the modem may hang up because it incorrectly thinks that it lost carrier. There is a setting on most modems for determining how tolerant it should be to temporary losses of carrier. Refer to the modem manual for details. Why does my connection hang after a random amount of time? Many people experience hung connections with no apparent explanation. The first thing to establish is which side of the link is hung. When using an external modem, try using ping8 to see if the TD light is flashing when data is transmitted. If it flashes but the RD light does not, the problem is with the remote end. If TD does not flash, the problem is local. With an internal modem, use the set server command in ppp.conf. When the hang occurs, connect to ppp8 using pppctl8. If the network connection suddenly revives due to the activity on the diagnostic socket, or if it will not connect but the set socket command succeeded at startup time, the problem is local. If it can connect but things are still hung, enable local logging with set log local async and use ping8 from another window or terminal to make use of the link. The async logging will show the data being transmitted and received on the link. If data is going out and not coming back, the problem is remote. Having established whether the problem is local or remote, there are now two possibilities: If the problem is remote, read on entry . If the problem is local, read on entry . The remote end is not responding. What can I do? There is very little that can be done about this. Many ISPs will refuse to help users not running a Microsoft OS. Add enable lqr to /etc/ppp/ppp.conf, allowing ppp8 to detect the remote failure and hang up. This detection is relatively slow and therefore not that useful. First, try disabling all local compression by adding the following to the configuration: disable pred1 deflate deflate24 protocomp acfcomp shortseq vj deny pred1 deflate deflate24 protocomp acfcomp shortseq vj Then reconnect to ensure that this makes no difference. If things improve or if the problem is solved completely, determine which setting makes the difference through trial and error. This is good information for the ISP, although it may make it apparent that it is not a Microsoft system. Before contacting the ISP, enable async logging locally and wait until the connection hangs again. This may use up quite a bit of disk space. The last data read from the port may be of interest. It is usually ASCII data, and may even describe the problem (Memory fault, Core dumped). If the ISP is helpful, they should be able to enable logging on their end, then when the next link drop occurs, they may be able to tell why their side is having a problem. ppp8 has hung. What can I do? In this case, rebuild ppp8 with debugging information, and then use gdb1 to grab a stack trace from the ppp process that is stuck. To rebuild the ppp utility with debugging information, type: # cd /usr/src/usr.sbin/ppp # env DEBUG_FLAGS='-g' make clean # env DEBUG_FLAGS='-g' make install Then, restart ppp and wait until it hangs again. When the debug build of ppp hangs, start gdb on the stuck process by typing: # gdb ppp `pgrep ppp` At the gdb prompt, use the bt or where commands to get a stack trace. Save the output of the gdb session, and detach from the running process by typing quit. I keep seeing errors about magic being the same. What does it mean? Occasionally, just after connecting, there may be messages in the log that say Magic is same. Sometimes, these messages are harmless, and sometimes one side or the other exits. Most PPP implementations cannot survive this problem, and even if the link seems to come up, there will be repeated configure requests and configure acknowledgments in the log file until ppp8 eventually gives up and closes the connection. This normally happens on server machines with slow disks that are spawning a getty8 on the port, and executing ppp8 from a login script or program after login. There were reports of it happening consistently when using slirp. The reason is that in the time taken between getty8 exiting and ppp8 starting, the client-side ppp8 starts sending Line Control Protocol (LCP) packets. Because ECHO is still switched on for the port on the server, the client ppp8 sees these packets reflect back. One part of the LCP negotiation is to establish a magic number for each side of the link so that reflections can be detected. The protocol says that when the peer tries to negotiate the same magic number, a NAK should be sent and a new magic number should be chosen. During the period that the server port has ECHO turned on, the client ppp8 sends LCP packets, sees the same magic in the reflected packet and NAKs it. It also sees the NAK reflect (which also means ppp8 must change its magic). This produces a potentially enormous number of magic number changes, all of which are happily piling into the server's tty buffer. As soon as ppp8 starts on the server, it is flooded with magic number changes and almost immediately decides it has tried enough to negotiate LCP and gives up. Meanwhile, the client, who no longer sees the reflections, becomes happy just in time to see a hangup from the server. This can be avoided by allowing the peer to start negotiating with the following line in ppp.conf: set openmode passive This tells ppp8 to wait for the server to initiate LCP negotiations. Some servers however may never initiate negotiations. In this case, try something like: set openmode active 3 This tells ppp8 to be passive for 3 seconds, and then to start sending LCP requests. If the peer starts sending requests during this period, ppp8 will immediately respond rather than waiting for the full 3 second period. LCP negotiations continue until the connection is closed. What is wrong? There is currently an implementation mis-feature in ppp8 where it does not associate LCP, CCP & IPCP responses with their original requests. As a result, if one PPP implementation is more than 6 seconds slower than the other side, the other side will send two additional LCP configuration requests. This is fatal. Consider two implementations, A and B. A starts sending LCP requests immediately after connecting and B takes 7 seconds to start. When B starts, A has sent 3 LCP REQs. We are assuming the line has ECHO switched off, otherwise we would see magic number problems as described in the previous section. B sends a REQ, then an ACK to the first of A's REQs. This results in A entering the OPENED state and sending and ACK (the first) back to B. In the meantime, B sends back two more ACKs in response to the two additional REQs sent by A before B started up. B then receives the first ACK from A and enters the OPENED state. A receives the second ACK from B and goes back to the REQ-SENT state, sending another (forth) REQ as per the RFC. It then receives the third ACK and enters the OPENED state. In the meantime, B receives the forth REQ from A, resulting in it reverting to the ACK-SENT state and sending another (second) REQ and (forth) ACK as per the RFC. A gets the REQ, goes into REQ-SENT and sends another REQ. It immediately receives the following ACK and enters OPENED. This goes on until one side figures out that they are getting nowhere and gives up. The best way to avoid this is to configure one side to be passive — that is, make one side wait for the other to start negotiating. This can be done with the following command: set openmode passive Care should be taken with this option. This command can also be used to limit the amount of time that ppp8 waits for the peer to begin negotiations: set stopped N Alternatively, the following command (where N is the number of seconds to wait before starting negotiations) can be used: set openmode active N Check the manual page for details. Why does ppp8 lock up when I shell out to test it? When using shell or !, ppp8 executes a shell or the passed arguments. The ppp program will wait for the command to complete before continuing. Any attempt to use the PPP link while running the command will appear as a frozen link. This is because ppp8 is waiting for the command to complete. To execute commands like this, use !bg instead. This will execute the given command in the background, and ppp8 can continue to service the link. Why does ppp8 over a null-modem cable never exit? There is no way for ppp8 to automatically determine that a direct connection has been dropped. This is due to the lines that are used in a null-modem serial cable. When using this sort of connection, LQR should always be enabled with the following line: enable lqr LQR is accepted by default if negotiated by the peer. Why does ppp8 dial for no reason in mode? If ppp8 is dialing unexpectedly, determine the cause, and set up dial filters to prevent such dialing. To determine the cause, use the following line: set log +tcp/ip This will log all traffic through the connection. The next time the line comes up unexpectedly, the reason will be logged with a convenient timestamp next to it. Next, disable dialing under these circumstances. Usually, this sort of problem arises due to DNS lookups. To prevent DNS lookups from establishing a connection (this will not prevent ppp8 from passing the packets through an established connection), use the following: set dfilter 1 deny udp src eq 53 set dfilter 2 deny udp dst eq 53 set dfilter 3 permit 0/0 0/0 This is not always suitable, as it will effectively break demand-dial capabilities. Most programs will need a DNS lookup before doing any other network related things. In the DNS case, try to determine what is actually trying to resolve a host name. A lot of the time, Sendmail is the culprit. Make sure to configure Sendmail not to do any DNS lookups in its configuration file. See the section on using email with a dialup connection in the FreeBSD Handbook for details. You may also want to add the following line to .mc: define(`confDELIVERY_MODE', `d')dnl This will make Sendmail queue everything until the queue is run, usually, every 30 minutes, or until a sendmail -q is done, perhaps from /etc/ppp/ppp.linkup. What do these CCP errors mean? I keep seeing the following errors in my log file: CCP: CcpSendConfigReq CCP: Received Terminate Ack (1) state = Req-Sent (6) This is because ppp8 is trying to negotiate Predictor1 compression, but the peer does not want to negotiate any compression at all. The messages are harmless, but can be silenced by disabling the compression: disable pred1 Why does ppp8 not log my connection speed? To log all lines of the modem conversation, enable the following: set log +connect This will make ppp8 log everything up until the last requested expect string. To see the connect speed when using PAP or CHAP, make sure to configure ppp8 to expect the whole CONNECT line, using something like this: set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 4 \ \"\" ATZ OK-ATZ-OK ATDT\\T TIMEOUT 60 CONNECT \\c \\n" This gets the CONNECT, sends nothing, then expects a line-feed, forcing ppp8 to read the whole CONNECT response. Why does ppp8 ignore the \ character in my chat script? The ppp utility parses each line in its configuration files so that it can interpret strings such as set phone "123 456 789" correctly and realize that the number is actually only one argument. To specify a " character, escape it using a backslash (\). When the chat interpreter parses each argument, it re-interprets the argument to find any special escape sequences such as \P or \T. As a result of this double-parsing, remember to use the correct number of escapes. To actually send a \ character, do something like: set dial "\"\" ATZ OK-ATZ-OK AT\\\\X OK" It will result in the following sequence: ATZ OK AT\X OK Or: set phone 1234567 set dial "\"\" ATZ OK ATDT\\T" It will result in the following sequence: ATZ OK ATDT1234567 What are FCS errors? FCS stands for Frame Check Sequence. Each PPP packet has a checksum attached to ensure that the data being received is the data being sent. If the FCS of an incoming packet is incorrect, the packet is dropped and the HDLC FCS count is increased. The HDLC error values can be displayed using the show hdlc command. If the link is bad or if the serial driver is dropping packets, it will produce the occasional FCS error. This is not usually worth worrying about although it does slow down the compression protocols substantially. If the link freezes as soon as it connects and produces a large number of FCS errors, make sure the modem is not using software flow control (XON/XOFF). If the link must use software flow control, use set accmap 0x000a0000 to tell ppp8 to escape the ^Q and ^S characters. Another reason for too many FCS errors may be that the remote end has stopped talking PPP. In this case, enable async logging to determine if the incoming data is actually a login or shell prompt. If it is a shell prompt at the remote end, it is possible to terminate ppp8 without dropping the line by using close lcp followed by term) to reconnect to the shell on the remote machine. If nothing in the log file indicates why the link was terminated, ask the remote administrator or ISP why the session was terminated. None of this helps — I am desperate! What can I do? If all else fails, send the details of the error, the configuration files, how ppp8 is being started, the relevant parts of the log file, and the output of netstat -rn, before and after connecting, to the FreeBSD general questions mailing list. Serial Communications This section answers common questions about serial communications with FreeBSD. PPP is covered in the Networking section. Which multi-port serial cards are supported by FreeBSD? There is a list of these in the Serial Communications chapter of the Handbook. Most multi-port PCI cards that are based on 16550 or clones are supported with no extra effort. Some unnamed clone cards have also been known to work, especially those that claim to be AST compatible. Check uart4 and sio4 to get more information on configuring such cards. How do I get the boot: prompt to show on the serial console? See this section of the Handbook. How do I tell if FreeBSD found my serial ports or modem cards? As the FreeBSD kernel boots, it will probe for the serial ports for which the kernel is configured. Either watch the boot messages closely or run this command after the system is up and running: % grep -E '^(sio|uart)[0-9]' < /var/run/dmesg.boot sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A This example shows two serial ports. The first is on IRQ4, port address 0x3f8, and has a 16550A-type UART chip. The second uses the same kind of chip but is on IRQ3 and is at port address 0x2f8. Internal modem cards are treated just like serial ports, except that they always have a modem attached to the port. The GENERIC kernel includes support for two serial ports using the same IRQ and port address settings in the above example. If these settings are not right for the system, or if there are more modem cards or serial ports than the kernel is configured for, reconfigure using the instructions in building a kernel for more details. How do I access the serial ports on FreeBSD? The third serial port, sio2, or COM3, is on /dev/cuad2 for dial-out devices, and on /dev/ttyd2 for dial-in devices. What is the difference between these two classes of devices? When opening /dev/ttydX in blocking mode, a process will wait for the corresponding cuadX device to become inactive, and then wait for the carrier detect line to go active. When the cuadX device is opened, it makes sure the serial port is not already in use by the ttydX device. If the port is available, it steals it from the ttydX device. Also, the cuadX device does not care about carrier detect. With this scheme and an auto-answer modem, remote users can log in and local users can still dial out with the same modem and the system will take care of all the conflicts. How do I enable support for a multi-port serial card? The section on kernel configuration provides information about configuring the kernel. For a multi-port serial card, place an sio4 line for each serial port on the card in the device.hints5 file. But place the IRQ specifiers on only one of the entries. All of the ports on the card should share one IRQ. For consistency, use the last serial port to specify the IRQ. Also, specify the following option in the kernel configuration file: options COM_MULTIPORT The following /boot/device.hints example is for an AST 4-port serial card on IRQ 12: hint.sio.4.at="isa" hint.sio.4.port="0x2a0" hint.sio.4.flags="0x701" hint.sio.5.at="isa" hint.sio.5.port="0x2a8" hint.sio.5.flags="0x701" hint.sio.6.at="isa" hint.sio.6.port="0x2b0" hint.sio.6.flags="0x701" hint.sio.7.at="isa" hint.sio.7.port="0x2b8" hint.sio.7.flags="0x701" hint.sio.7.irq="12" The flags indicate that the master port has minor number 7 (0x700), and all the ports share an IRQ (0x001). Can I set the default serial parameters for a port? See the Serial Communications section in the FreeBSD Handbook. How can I enable dialup logins on my modem? Refer to the section about Dial-in Services in the FreeBSD Handbook. How can I connect a dumb terminal to my FreeBSD box? This information is in the Terminals section of the FreeBSD Handbook. Why can I not run tip or cu? The built-in tip1 and cu1 utilities can only access the /var/spool/lock directory via user uucp and group dialer. Use the dialer group to control who has access to the modem or remote systems by adding user accounts to dialer. Alternatively, everyone can be configured to run tip1 and cu1 by typing: # chmod 4511 /usr/bin/cu # chmod 4511 /usr/bin/tip Miscellaneous Questions FreeBSD uses a lot of swap space even when the computer has free memory left. Why? FreeBSD will proactively move entirely idle, unused pages of main memory into swap in order to make more main memory available for active use. This heavy use of swap is balanced by using the extra free memory for caching. Note that while FreeBSD is proactive in this regard, it does not arbitrarily decide to swap pages when the system is truly idle. Thus, the system will not be all paged out after leaving it idle overnight. Why does top show very little free memory even when I have very few programs running? The simple answer is that free memory is wasted memory. Any memory that programs do not actively allocate is used within the FreeBSD kernel as disk cache. The values shown by top1 labeled as Inact and Laundry are cached data at different aging levels. This cached data means the system does not have to access a slow disk again for data it has accessed recently, thus increasing overall performance. In general, a low value shown for Free memory in top1 is good, provided it is not very low. Why will chmod not change the permissions on symlinks? Symlinks do not have permissions, and by default, chmod1 will follow symlinks to change the permissions on the source file, if possible. For the file, foo with a symlink named bar, this command will always succeed. % chmod g-w bar However, the permissions on bar will not have changed. When changing modes of the file hierarchies rooted in the files instead of the files themselves, use either or together with to make this work. See chmod1 and symlink7 for more information. does a recursive chmod1. Be careful about specifying directories or symlinks to directories to chmod1. To change the permissions of a directory referenced by a symlink, use chmod1 without any options and follow the symlink with a trailing slash (/). For example, if foo is a symlink to directory bar, to change the permissions of foo (actually bar), do something like: % chmod 555 foo/ With the trailing slash, chmod1 will follow the symlink, foo, to change the permissions of the directory, bar. Can I run DOS binaries under FreeBSD? Yes. A DOS emulation program, emulators/doscmd, is available in the FreeBSD Ports Collection. If doscmd will not suffice, emulators/pcemu emulates an 8088 and enough BIOS services to run many DOS text-mode applications. It requires the X Window System. The Ports Collection also has emulators/dosbox. The main focus of this application is emulating old DOS games using the local file system for files. What do I need to do to translate a FreeBSD document into my native language? See the Translation FAQ in the FreeBSD Documentation Project Primer. Why does my email to any address at FreeBSD.org bounce? The FreeBSD.org mail system implements some Postfix checks on incoming mail and rejects mail that is either from misconfigured relays or otherwise appears likely to be spam. Some of the specific requirements are: The IP address of the SMTP client must "reverse-resolve" to a forward confirmed hostname. The fully-qualified hostname given in the SMTP conversation (either HELO or EHLO) must resolve to the IP address of the client. Other advice to help mail reach its destination include: Mail should be sent in plain text, and messages sent to mailing lists should generally be no more than 200KB in length. Avoid excessive cross posting. Choose one mailing list which seems most relevant and send it there. If you still have trouble with email infrastructure at FreeBSD.org, send a note with the details to postmaster@freebsd.org; Include a date/time interval so that logs may be reviewed — and note that we only keep one week's worth of mail logs. (Be sure to specify the time zone or offset from UTC.) Where can I find a free FreeBSD account? While FreeBSD does not provide open access to any of their servers, others do provide open access UNIX systems. The charge varies and limited services may be available. Arbornet, Inc, also known as M-Net, has been providing open access to UNIX systems since 1983. Starting on an Altos running System III, the site switched to BSD/OS in 1991. In June of 2000, the site switched again to FreeBSD. M-Net can be accessed via telnet and SSH and provides basic access to the entire FreeBSD software suite. However, network access is limited to members and patrons who donate to the system, which is run as a non-profit organization. M-Net also provides an bulletin board system and interactive chat. What is the cute little red guy's name? He does not have one, and is just called the BSD daemon. If you insist upon using a name, call him beastie. Note that beastie is pronounced BSD. More about the BSD daemon is available on his home page. Can I use the BSD daemon image? Perhaps. The BSD daemon is copyrighted by Marshall Kirk McKusick. Check his Statement on the Use of the BSD Daemon Figure for detailed usage terms. In summary, the image can be used in a tasteful manner, for personal use, so long as appropriate credit is given. Before using the logo commercially, contact Kirk McKusick mckusick@FreeBSD.org for permission. More details are available on the BSD Daemon's home page. Do you have any BSD daemon images I could use? Xfig and eps drawings are available under /usr/share/examples/BSD_daemon/. I have seen an acronym or other term on the mailing lists and I do not understand what it means. Where should I look? Refer to the FreeBSD Glossary. Why should I care what color the bikeshed is? The really, really short answer is that you should not. The somewhat longer answer is that just because you are capable of building a bikeshed does not mean you should stop others from building one just because you do not like the color they plan to paint it. This is a metaphor indicating that you need not argue about every little feature just because you know enough to do so. Some people have commented that the amount of noise generated by a change is inversely proportional to the complexity of the change. The longer and more complete answer is that after a very long argument about whether sleep1 should take fractional second arguments, Poul-Henning Kamp phk@FreeBSD.org posted a long message entitled A bike shed (any color will do) on greener grass.... The appropriate portions of that message are quoted below.
Poul-Henning Kamp phk@FreeBSD.org on freebsd-hackers, October 2, 1999 What is it about this bike shed? Some of you have asked me. It is a long story, or rather it is an old story, but it is quite short actually. C. Northcote Parkinson wrote a book in the early 1960s, called Parkinson's Law, which contains a lot of insight into the dynamics of management. [snip a bit of commentary on the book] In the specific example involving the bike shed, the other vital component is an atomic power-plant, I guess that illustrates the age of the book. Parkinson shows how you can go into the board of directors and get approval for building a multi-million or even billion dollar atomic power plant, but if you want to build a bike shed you will be tangled up in endless discussions. Parkinson explains that this is because an atomic plant is so vast, so expensive and so complicated that people cannot grasp it, and rather than try, they fall back on the assumption that somebody else checked all the details before it got this far. Richard P. Feynmann gives a couple of interesting, and very much to the point, examples relating to Los Alamos in his books. A bike shed on the other hand. Anyone can build one of those over a weekend, and still have time to watch the game on TV. So no matter how well prepared, no matter how reasonable you are with your proposal, somebody will seize the chance to show that he is doing his job, that he is paying attention, that he is here. In Denmark we call it setting your fingerprint. It is about personal pride and prestige, it is about being able to point somewhere and say There! I did that. It is a strong trait in politicians, but present in most people given the chance. Just think about footsteps in wet cement.
The FreeBSD Funnies How cool is FreeBSD? Q. Has anyone done any temperature testing while running FreeBSD? I know Linux runs cooler than DOS, but have never seen a mention of FreeBSD. It seems to run really hot. A. No, but we have done numerous taste tests on blindfolded volunteers who have also had 250 micrograms of LSD-25 administered beforehand. 35% of the volunteers said that FreeBSD tasted sort of orange, whereas Linux tasted like purple haze. Neither group mentioned any significant variances in temperature. We eventually had to throw the results of this survey out entirely anyway when we found that too many volunteers were wandering out of the room during the tests, thus skewing the results. We think most of the volunteers are at Apple now, working on their new scratch and sniff GUI. It is a funny old business we are in! Seriously, FreeBSD uses the HLT (halt) instruction when the system is idle thus lowering its energy consumption and therefore the heat it generates. Also if you have ACPI (Advanced Configuration and Power Interface) configured, then FreeBSD can also put the CPU into a low power mode. Who is scratching in my memory banks?? Q. Is there anything odd that FreeBSD does when compiling the kernel which would cause the memory to make a scratchy sound? When compiling (and for a brief moment after recognizing the floppy drive upon startup, as well), a strange scratchy sound emanates from what appears to be the memory banks. A. Yes! You will see frequent references to daemons in the BSD documentation, and what most people do not know is that this refers to genuine, non-corporeal entities that now possess your computer. The scratchy sound coming from your memory is actually high-pitched whispering exchanged among the daemons as they best decide how to deal with various system administration tasks. If the noise gets to you, a good fdisk /mbr from DOS will get rid of them, but do not be surprised if they react adversely and try to stop you. In fact, if at any point during the exercise you hear the satanic voice of Bill Gates coming from the built-in speaker, take off running and do not ever look back! Freed from the counterbalancing influence of the BSD daemons, the twin demons of DOS and Windows are often able to re-assert total control over your machine to the eternal damnation of your soul. Now that you know, given a choice you would probably prefer to get used to the scratchy noises, no? How many FreeBSD hackers does it take to change a lightbulb? One thousand, one hundred and sixty-nine: Twenty-three to complain to -CURRENT about the lights being out; Four to claim that it is a configuration problem, and that such matters really belong on -questions; Three to submit PRs about it, one of which is misfiled under doc and consists only of it's dark; One to commit an untested lightbulb which breaks buildworld, then back it out five minutes later; Eight to flame the PR originators for not including patches in their PRs; Five to complain about buildworld being broken; Thirty-one to answer that it works for them, and they must have updated at a bad time; One to post a patch for a new lightbulb to -hackers; One to complain that he had patches for this three years ago, but when he sent them to -CURRENT they were just ignored, and he has had bad experiences with the PR system; besides, the proposed new lightbulb is non-reflexive; Thirty-seven to scream that lightbulbs do not belong in the base system, that committers have no right to do things like this without consulting the Community, and WHAT IS -CORE DOING ABOUT IT!? Two hundred to complain about the color of the bicycle shed; Three to point out that the patch breaks style9; Seventeen to complain that the proposed new lightbulb is under GPL; Five hundred and eighty-six to engage in a flame war about the comparative advantages of the GPL, the BSD license, the MIT license, the NPL, and the personal hygiene of unnamed FSF founders; Seven to move various portions of the thread to -chat and -advocacy; One to commit the suggested lightbulb, even though it shines dimmer than the old one; Two to back it out with a furious flame of a commit message, arguing that FreeBSD is better off in the dark than with a dim lightbulb; Forty-six to argue vociferously about the backing out of the dim lightbulb and demanding a statement from -core; Eleven to request a smaller lightbulb so it will fit their Tamagotchi if we ever decide to port FreeBSD to that platform; Seventy-three to complain about the SNR on -hackers and -chat and unsubscribe in protest; Thirteen to post unsubscribe, How do I unsubscribe?, or Please remove me from the list, followed by the usual footer; One to commit a working lightbulb while everybody is too busy flaming everybody else to notice; Thirty-one to point out that the new lightbulb would shine 0.364% brighter if compiled with TenDRA (although it will have to be reshaped into a cube), and that FreeBSD should therefore switch to TenDRA instead of GCC; One to complain that the new lightbulb lacks fairings; Nine (including the PR originators) to ask what is MFC?; Fifty-seven to complain about the lights being out two weeks after the bulb has been changed. Nik Clayton nik@FreeBSD.org adds: I was laughing quite hard at this. And then I thought, Hang on, shouldn't there be '1 to document it.' in that list somewhere? And then I was enlightened :-) Thomas Abthorpe tabthorpe@FreeBSD.org says: None, real FreeBSD hackers are not afraid of the dark! Where does data written to /dev/null go? It goes into a special data sink in the CPU where it is converted to heat which is vented through the heatsink / fan assembly. This is why CPU cooling is increasingly important; as people get used to faster processors, they become careless with their data and more and more of it ends up in /dev/null, overheating their CPUs. If you delete /dev/null (which effectively disables the CPU data sink) your CPU may run cooler but your system will quickly become constipated with all that excess data and start to behave erratically. If you have a fast network connection you can cool down your CPU by reading data out of /dev/random and sending it off somewhere; however you run the risk of overheating your network connection and / or angering your ISP, as most of the data will end up getting converted to heat by their equipment, but they generally have good cooling, so if you do not overdo it you should be OK. Paul Robinson adds: There are other methods. As every good sysadmin knows, it is part of standard practice to send data to the screen of interesting variety to keep all the pixies that make up your picture happy. Screen pixies (commonly mis-typed or re-named as pixels) are categorized by the type of hat they wear (red, green or blue) and will hide or appear (thereby showing the color of their hat) whenever they receive a little piece of food. Video cards turn data into pixie-food, and then send them to the pixies — the more expensive the card, the better the food, so the better behaved the pixies are. They also need constant stimulation — this is why screen savers exist. To take your suggestions further, you could just throw the random data to console, thereby letting the pixies consume it. This causes no heat to be produced at all, keeps the pixies happy and gets rid of your data quite quickly, even if it does make things look a bit messy on your screen. Incidentally, as an ex-admin of a large ISP who experienced many problems attempting to maintain a stable temperature in a server room, I would strongly discourage people sending the data they do not want out to the network. The fairies who do the packet switching and routing get annoyed by it as well. My colleague sits at the computer too much, how can I prank her? Install games/sl and wait for her to mistype sl for ls. Advanced Topics How can I learn more about FreeBSD's internals? See the FreeBSD Architecture Handbook. Additionally, much general UNIX knowledge is directly applicable to FreeBSD. How can I contribute to FreeBSD? What can I do to help? We accept all types of contributions: documentation, code, and even art. See the article on Contributing to FreeBSD for specific advice on how to do this. And thanks for the thought! What are snapshots and releases? There are currently 2 active/semi-active branches in the FreeBSD Subversion Repository. (Earlier branches are only changed very rarely, which is why there are only 2 active branches of development): stable/11/ AKA 11-STABLE stable/12/ AKA 12-STABLE head/ AKA -CURRENT AKA 12-CURRENT HEAD is not an actual branch tag. It is a symbolic constant for the current, non-branched development stream known as -CURRENT. Right now, -CURRENT is the 13.X development stream; the 12-STABLE branch, stable/12/, forked off from -CURRENT in December 2018 and the 11-STABLE branch, stable/11/, forked off from -CURRENT in October 2016. How can I make the most of the data I see when my kernel panics? Here is typical kernel panic: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x40 fault code = supervisor read, page not present instruction pointer = 0x8:0xf014a7e5 stack pointer = 0x10:0xf4ed6f24 frame pointer = 0x10:0xf4ed6f28 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 80 (mount) interrupt mask = trap number = 12 panic: page fault This message is not enough. While the instruction pointer value is important, it is also configuration dependent as it varies depending on the kernel image. If it is a GENERIC kernel image from one of the snapshots, it is possible for somebody else to track down the offending function, but for a custom kernel, only you can tell us where the fault occurred. To proceed: Write down the instruction pointer value. Note that the 0x8: part at the beginning is not significant in this case: it is the 0xf0xxxxxx part that we want. When the system reboots, do the following: % nm -n kernel.that.caused.the.panic | grep f0xxxxxx where f0xxxxxx is the instruction pointer value. The odds are you will not get an exact match since the symbols in the kernel symbol table are for the entry points of functions and the instruction pointer address will be somewhere inside a function, not at the start. If you do not get an exact match, omit the last digit from the instruction pointer value and try again: % nm -n kernel.that.caused.the.panic | grep f0xxxxx If that does not yield any results, chop off another digit. Repeat until there is some sort of output. The result will be a possible list of functions which caused the panic. This is a less than exact mechanism for tracking down the point of failure, but it is better than nothing. However, the best way to track down the cause of a panic is by capturing a crash dump, then using kgdb1 to generate a stack trace on the crash dump. In any case, the method is this: Make sure that the following line is included in the kernel configuration file: makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols Change to the /usr/src directory: # cd /usr/src Compile the kernel: # make buildkernel KERNCONF=MYKERNEL Wait for make1 to finish compiling. # make installkernel KERNCONF=MYKERNEL Reboot. If KERNCONF is not included, the GENERIC kernel will instead be built and installed. The make1 process will have built two kernels. /usr/obj/usr/src/sys/MYKERNEL/kernel and /usr/obj/usr/src/sys/MYKERNEL/kernel.debug. kernel was installed as /boot/kernel/kernel, while kernel.debug can be used as the source of debugging symbols for kgdb1. To capture a crash dump, edit /etc/rc.conf and set dumpdev to point to either the swap partition or AUTO. This will cause the rc8 scripts to use the dumpon8 command to enable crash dumps. This command can also be run manually. After a panic, the crash dump can be recovered using savecore8; if dumpdev is set in /etc/rc.conf, the rc8 scripts will run savecore8 automatically and put the crash dump in /var/crash. FreeBSD crash dumps are usually the same size as physical RAM. Therefore, make sure there is enough space in /var/crash to hold the dump. Alternatively, run savecore8 manually and have it recover the crash dump to another directory with more room. It is possible to limit the size of the crash dump by using options MAXMEM=N where N is the size of kernel's memory usage in KBs. For example, for 1 GB of RAM, limit the kernel's memory usage to 128 MB, so that the crash dump size will be 128 MB instead of 1 GB. Once the crash dump has been recovered , get a stack trace as follows: % kgdb /usr/obj/usr/src/sys/MYKERNEL/kernel.debug /var/crash/vmcore.0 (kgdb) backtrace Note that there may be several screens worth of information. Ideally, use script1 to capture all of them. Using the unstripped kernel image with all the debug symbols should show the exact line of kernel source code where the panic occurred. The stack trace is usually read from the bottom up to trace the exact sequence of events that lead to the crash. kgdb1 can also be used to print out the contents of various variables or structures to examine the system state at the time of the crash. If a second computer is available, kgdb1 can be configured to do remote debugging, including setting breakpoints and single-stepping through the kernel code. If DDB is enabled and the kernel drops into the debugger, a panic and a crash dump can be forced by typing panic at the ddb prompt. It may stop in the debugger again during the panic phase. If it does, type continue and it will finish the crash dump. Why has dlsym() stopped working for ELF executables? The ELF toolchain does not, by default, make the symbols defined in an executable visible to the dynamic linker. Consequently dlsym() searches on handles obtained from calls to dlopen(NULL, flags) will fail to find such symbols. To search, using dlsym(), for symbols present in the main executable of a process, link the executable using the option to the ELF linker (ld1). How can I increase or reduce the kernel address space on i386? By default, the kernel address space is 1 GB (2 GB for PAE) for i386. When running a network-intensive server or using ZFS, this will probably not be enough. Add the following line to the kernel configuration file to increase available space and rebuild the kernel: options KVA_PAGES=N To find the correct value of N, divide the desired address space size (in megabytes) by four. (For example, it is 512 for 2 GB.) Acknowledgments This innocent little Frequently Asked Questions document has been written, rewritten, edited, folded, spindled, mutilated, eviscerated, contemplated, discombobulated, cogitated, regurgitated, rebuilt, castigated, and reinvigorated over the last decade, by a cast of hundreds if not thousands. Repeatedly. We wish to thank every one of the people responsible, and we encourage you to join them in making this FAQ even better. Index: head/zh_TW.UTF-8/books/faq/zh_TW.po =================================================================== --- head/zh_TW.UTF-8/books/faq/zh_TW.po (revision 53450) +++ head/zh_TW.UTF-8/books/faq/zh_TW.po (revision 53451) @@ -1,7857 +1,7855 @@ # $FreeBSD$ msgid "" msgstr "" "Project-Id-Version: \n" -"POT-Creation-Date: 2019-01-17 06:22+0800\n" -"PO-Revision-Date: 2019-01-16 22:40+0800\n" +"POT-Creation-Date: 2019-10-03 17:21+0800\n" +"PO-Revision-Date: 2019-10-03 18:38+0800\n" "Last-Translator: \n" "Language-Team: \n" "Language: zh_TW\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"X-Generator: Poedit 1.8.11\n" +"X-Generator: Poedit 2.2.4\n" #. Put one translator per line, in the form NAME , YEAR1, YEAR2 msgctxt "_" msgid "translator-credits" msgstr "translator-credits" #. (itstool) path: info/title #: book.translate.xml:19 -#, fuzzy msgid "Frequently Asked Questions for FreeBSD 11.X and 12.X" -msgstr "FreeBSD 10.X and 11.X 常見問答集" +msgstr "FreeBSD 11.X and 12.X 常見問答集" #. (itstool) path: info/author #: book.translate.xml:22 msgid "The FreeBSD Documentation Project" msgstr "FreeBSD 文件計畫" #. (itstool) path: info/copyright #: book.translate.xml:24 -#, fuzzy msgid "" "1995 1996 1997 1998 1999 2000 2001 2002 " "2003 2004 2005 2006 2007 2008 2009 2010 " "2011 2012 2013 2014 2015 2016 2017 2018 " -"The FreeBSD Documentation Project" +"2019 The FreeBSD Documentation Project" msgstr "" "1995 1996 1997 1998 1999 2000 2001 2002 " "2003 2004 2005 2006 2007 2008 2009 2010 " -"2011 2012 2013 2014 2015 2016 2017 The FreeBSD " -"Documentation Project" +"2011 2012 2013 2014 2015 2016 2017 2018 " +"2019 The FreeBSD Documentation Project" #. (itstool) path: legalnotice/title -#: book.translate.xml:55 +#: book.translate.xml:56 msgid "Copyright" msgstr "版權所有" #. (itstool) path: legalnotice/para -#: book.translate.xml:57 +#: book.translate.xml:58 msgid "" "Redistribution and use in source (XML DocBook) and 'compiled' forms (XML, HTML, PDF, PostScript, RTF and so forth) with or without modification, are " "permitted provided that the following conditions are met:" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:64 +#: book.translate.xml:65 msgid "" "Redistributions of source code (XML DocBook) must retain the above copyright notice, this list of conditions and the following disclaimer as the first " "lines of this file unmodified." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:70 +#: book.translate.xml:71 msgid "" "Redistributions in compiled form (transformed to other DTDs, converted to PDF, PostScript, RTF and other formats) must reproduce the above copyright " "notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution." msgstr "" #. (itstool) path: important/para -#: book.translate.xml:79 +#: book.translate.xml:80 msgid "" "THIS DOCUMENTATION IS PROVIDED BY THE FREEBSD DOCUMENTATION PROJECT \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE " "IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FREEBSD DOCUMENTATION PROJECT BE " "LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE " "GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT " "LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBILITY OF " "SUCH DAMAGE." msgstr "" #. (itstool) path: legalnotice/para -#: book.translate.xml:96 +#: book.translate.xml:97 msgid "FreeBSD is a registered trademark of the FreeBSD Foundation." msgstr "FreeBSD 是 FreeBSD基金會的註冊商標。" #. (itstool) path: legalnotice/para -#: book.translate.xml:98 +#: book.translate.xml:99 msgid "" "Adobe, Acrobat, Acrobat Reader, Flash and PostScript are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States " "and/or other countries." msgstr "Adobe, Acrobat, Acrobat Reader, 以及 PostScript 是 Adobe Systems Incorporated 在美國和/或其他國家的商標或註冊商標。" #. (itstool) path: legalnotice/para -#: book.translate.xml:102 +#: book.translate.xml:103 msgid "" "IBM, AIX, OS/2, PowerPC, PS/2, S/390, and ThinkPad are trademarks of International Business Machines Corporation in the United States, other countries, " "or both." msgstr "IBM, AIX, OS/2, PowerPC, PS/2, S/390, 和 ThinkPad 是 國際商用機器公司在美國和其他國家的註冊商標或商標。" #. (itstool) path: legalnotice/para -#: book.translate.xml:106 +#: book.translate.xml:107 msgid "IEEE, POSIX, and 802 are registered trademarks of Institute of Electrical and Electronics Engineers, Inc. in the United States." msgstr "IEEE, POSIX, 和 802 是 Institute of Electrical and Electronics Engineers, Inc. 在美國的註冊商標。" #. (itstool) path: legalnotice/para -#: book.translate.xml:109 +#: book.translate.xml:110 msgid "" "Intel, Celeron, Centrino, Core, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or registered trademarks of Intel Corporation or " "its subsidiaries in the United States and other countries." msgstr "" "Intel, Celeron, Centrino, Core, EtherExpress, i386, i486, Itanium, Pentium, 和 Xeon 是 Intel Corporation 及其分支機構在美國和其他國家的商標或註冊商標。" #. (itstool) path: legalnotice/para -#: book.translate.xml:113 +#: book.translate.xml:114 msgid "Linux is a registered trademark of Linus Torvalds." msgstr "Linux 是 Linus Torvalds 的註冊商標。" #. (itstool) path: legalnotice/para -#: book.translate.xml:115 +#: book.translate.xml:116 msgid "" "Microsoft, IntelliMouse, MS-DOS, Outlook, Windows, Windows Media and Windows NT are either registered trademarks or trademarks of Microsoft Corporation " "in the United States and/or other countries." msgstr "Microsoft, IntelliMouse, MS-DOS, Outlook, Windows, Windows Media, 和 Windows NT 是 Microsoft Corporation 在美國和/或其他國家的商標或註冊商標。" #. (itstool) path: legalnotice/para -#: book.translate.xml:119 +#: book.translate.xml:120 msgid "NetBSD is a registered trademark of the NetBSD Foundation." msgstr "NetBSD 是 NetBSD基金會的註冊商標。" #. (itstool) path: legalnotice/para -#: book.translate.xml:121 +#: book.translate.xml:122 msgid "" "Motif, OSF/1, and UNIX are registered trademarks and IT DialTone and The Open Group are trademarks of The Open Group in the United States and other " "countries." msgstr "Motif, OSF/1, and UNIX are registered trademarks and IT DialTone and The Open Group 是 The Open Group 在美國和其他國家的商標。" #. (itstool) path: legalnotice/para -#: book.translate.xml:125 +#: book.translate.xml:126 msgid "Silicon Graphics, SGI, and OpenGL are registered trademarks of Silicon Graphics, Inc., in the United States and/or other countries worldwide." msgstr "Silicon Graphics, SGI, 和 OpenGL 是 Silicon Graphics, Inc. 在美國和/或其他國家的註冊商標。" #. (itstool) path: legalnotice/para -#: book.translate.xml:128 +#: book.translate.xml:129 msgid "" "Sun, Sun Microsystems, Java, Java Virtual Machine, JDK, JRE, JSP, JVM, Netra, OpenJDK, Solaris, StarOffice, SunOS and VirtualBox are trademarks or " "registered trademarks of Sun Microsystems, Inc. in the United States and other countries." msgstr "" "Sun, Sun Microsystems, Java, Java Virtual Machine, JDK, JRE, JSP, JVM, Netra, OpenJDK, Solaris, StarOffice, SunOS and VirtualBox 是 Sun Microsystems, " "Inc. 在美國和其他國家的註冊商標。" #. (itstool) path: legalnotice/para -#: book.translate.xml:133 +#: book.translate.xml:134 msgid "" "Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in " "this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the ™ or the ® symbol." msgstr "" "許多製造商和經銷商使用一些稱為商標的圖案或文字設計來彰顯自己的產品。 本文中出現的眾多商標，以及 FreeBSD Project 本身廣所人知的商標，後面將以™ 或 ® 符號來標註。" #. (itstool) path: info/releaseinfo -#: book.translate.xml:141 +#: book.translate.xml:142 #, fuzzy msgid "$FreeBSD$" msgstr "$FreeBSD$" #. (itstool) path: abstract/para -#: book.translate.xml:144 -#, fuzzy +#: book.translate.xml:145 msgid "" "This is the Frequently Asked Questions (FAQ) for FreeBSD versions 12.X and 11.X. Every effort has been made to make this FAQ as informative as possible; if you have any suggestions as to how it may " "be improved, send them to the FreeBSD documentation project mailing list." msgstr "" -"這份文件是 FreeBSD 10.X 和 11.X 常見問答集 ( (FAQ) )。我們盡可能地讓這份 " +"這份文件是 FreeBSD 12.X 和 11.X 常見問答集 ( (FAQ) )。我們盡可能地讓這份 " "FAQ 提供有用的資訊 ; 如果您有任何改善建議，請寄到 FreeBSD " "文件計畫郵件論壇。" #. (itstool) path: abstract/para -#: book.translate.xml:151 +#: book.translate.xml:152 msgid "" "The latest version of this document is always available from the FreeBSD website. It may also be downloaded as one large HTML file with HTTP or as a variety of other " "formats from the FreeBSD FTP server." msgstr "" -"The latest version of this document is always available from the FreeBSD website. " +"本文件的最新版本可由 FreeBSD 網站取得。 也可以由 FreeBSD FTP 伺服器 以 HTTP 下載單一大型 HTML 檔或是其他格" +"式的檔案。" #. (itstool) path: chapter/title -#: book.translate.xml:161 +#: book.translate.xml:162 msgid "Introduction" msgstr "前言" #. (itstool) path: question/para -#: book.translate.xml:166 +#: book.translate.xml:167 msgid "What is FreeBSD?" msgstr "什麼是 FreeBSD？" #. (itstool) path: answer/para -#: book.translate.xml:170 +#: book.translate.xml:171 msgid "" "FreeBSD is a modern operating system for desktops, laptops, servers, and embedded systems with support for a large number of platforms." msgstr "" "FreeBSD 是一個使用於桌機、筆電、伺服器與嵌入式系統平台的現代作業系統，支援多種平台。" #. (itstool) path: answer/para -#: book.translate.xml:174 +#: book.translate.xml:175 msgid "" "It is based on U.C. Berkeley's 4.4BSD-Lite release, with some 4.4BSD-Lite2 enhancements. It is also based indirectly on " "William Jolitz's port of U.C. Berkeley's Net/2 to the i386, known as 386BSD, though very little of " "the 386BSD code remains." msgstr "" "它是根據 U.C. Berkeley 所開發出來的 4.4BSD-Lite ，並加上了許多 4.4BSD-Lite2 的增強功能。它同時也間接使用了 U.C. Berkeley " "所開發出來並由 William Jolitz 移植到 i386 的 Net/2，也就是 386BSD，不過現在 386BSD 的程式碼只剩下極" "少數還留 存在 FreeBSD 中。" #. (itstool) path: answer/para -#: book.translate.xml:182 +#: book.translate.xml:183 msgid "" "FreeBSD is used by companies, Internet Service Providers, researchers, computer professionals, students and home users all over the world in their " "work, education and recreation." msgstr "FreeBSD 已被廣泛地被世界各地的公司行號、ISP、研究人員、電腦 專家、學生，以及家庭用戶所使用，用在工作、教育以及娛樂上。" #. (itstool) path: answer/para -#: book.translate.xml:187 +#: book.translate.xml:188 msgid "" "For more detailed information on FreeBSD, refer to the FreeBSD " "Handbook." msgstr "" "如果想看關於 FreeBSD 更深入的資料，請看 FreeBSD 使用手冊。" #. (itstool) path: question/para -#: book.translate.xml:195 +#: book.translate.xml:196 msgid "What is the goal of the FreeBSD Project?" msgstr "發展 FreeBSD 計畫的目的是什麼？" #. (itstool) path: answer/para -#: book.translate.xml:199 +#: book.translate.xml:200 msgid "" "The goal of the FreeBSD Project is to provide a stable and fast general purpose operating system that may be used for any purpose without strings " "attached." msgstr "FreeBSD 計畫的目的是提供可以任意使用且沒有限制的穩定快速與一般用途的作業系統。" #. (itstool) path: question/para -#: book.translate.xml:207 +#: book.translate.xml:208 msgid "Does the FreeBSD license have any restrictions?" msgstr "FreeBSD 版權有任何限制嗎？" #. (itstool) path: answer/para -#: book.translate.xml:211 +#: book.translate.xml:212 msgid "" "Yes. Those restrictions do not control how the code is used, but how to treat the FreeBSD Project itself. The license itself is available at license and can be summarized like this:" msgstr "" "有的。但是這並不是限制你怎麼去使用這些程式碼，而是你怎麼看待 FreeBSD 這個計畫。可以在此閱讀 版權本文，簡單來說總結如下:" #. (itstool) path: listitem/para -#: book.translate.xml:219 +#: book.translate.xml:220 msgid "Do not claim that you wrote this." msgstr "請勿宣稱是您寫了這個程式。" #. (itstool) path: listitem/para -#: book.translate.xml:223 +#: book.translate.xml:224 msgid "Do not sue us if it breaks." msgstr "如果它出問題了，不要控告我們。" #. (itstool) path: listitem/para -#: book.translate.xml:227 +#: book.translate.xml:228 msgid "Do not remove or modify the license." msgstr "不要移除和修改版權" #. (itstool) path: answer/para -#: book.translate.xml:231 +#: book.translate.xml:232 msgid "" "Many of us have a significant investment in the project and would certainly not mind a little financial compensation now and then, but we definitely do " "not insist on it. We believe that our first and foremost mission is to provide code to any and all comers, and for whatever purpose, so " "that the code gets the widest possible use and provides the widest possible benefit. This, we believe, is one of the most fundamental goals of Free " "Software and one that we enthusiastically support." msgstr "" "我們許多人在這個計畫投入很多心血，並不會介意獲得一些財務上的報酬，但是我們並沒有堅持一定要有。我們相信我們首要的任務是將程式碼提供給所有" "使用者，無論他們有任何的目的，這麼一來，這些程式碼才能被用在最多地方，也才能發揮它們最大的利益。我們相信這就是自由軟體最基本的目標之一，而且我們會盡全力" "去支持它。" #. (itstool) path: answer/para -#: book.translate.xml:242 +#: book.translate.xml:243 msgid "" "Code in our source tree which falls under the GNU General Public License (GPL) or " "GNU Library General Public License (LGPL) comes with slightly more strings " "attached, though at least on the side of enforced access rather than the usual opposite. Due to the additional complexities that can evolve in the " "commercial use of GPL software, we do, however, endeavor to replace such software with submissions under the more relaxed FreeBSD license whenever possible." msgstr "" "在我們 source tree 中有部份的程式碼是採用所謂的GNU General Public License (GPL) " "或 GNU Library General Public License (LGPL)版權宣告，雖然這些版權宣告是用來保" "障而非限制使用者的權 利，畢竟是不那麼自由了些。由於這些 GPL 的軟體在商業使用上會引起 非常複雜的版權問題，因此只要有機會，我們會盡量以採用比較鬆的 FreeBSD 版權 的軟體來取代這些 GPL 版權宣告的軟體。" #. (itstool) path: question/para -#: book.translate.xml:257 +#: book.translate.xml:258 msgid "Can FreeBSD replace my current operating system?" msgstr "FreeBSD 可以取代我現在在用的作業系統嗎？" #. (itstool) path: answer/para -#: book.translate.xml:261 +#: book.translate.xml:262 msgid "For most people, yes. But this question is not quite that cut-and-dried." msgstr "對大部份的人來說是這樣沒錯，但事實上這問題並沒有這麼好回答。" #. (itstool) path: answer/para -#: book.translate.xml:264 +#: book.translate.xml:265 msgid "" "Most people do not actually use an operating system. They use applications. The applications are what really use the operating system. FreeBSD is " "designed to provide a robust and full-featured environment for applications. It supports a wide variety of web browsers, office suites, email readers, " "graphics programs, programming environments, network servers, and much more. Most of these applications can be managed through the Ports Collection." msgstr "" "大部份的人並不是真正在使用一個作業系統。他們使用的是應用程式 ；而那些應用程式才是真正用到作業系統的東西。FreeBSD 是設計用來提供一個強韌且功能完整的作業" "環境給應用程式來執行。它支援了多種瀏覽器，辦公室套件軟體，電子郵件閱讀軟體，繪圖程式，程式設計環境，網路伺服器軟體，以及幾乎所有你想要的東西。大部份的程" "式都可以靠 Ports Collection 來管理。" #. (itstool) path: answer/para -#: book.translate.xml:275 +#: book.translate.xml:276 msgid "" "If an application is only available on one operating system, that operating system cannot just be replaced. Chances are, there is a very similar " "application on FreeBSD, however. As a solid office or Internet server or a reliable workstation, FreeBSD will almost certainly do everything you need. " "Many computer users across the world, including both novices and experienced UNIX administrators, use " "FreeBSD as their only desktop operating system." msgstr "" "但是如果你想要使用的應用程式只能在某個特定的作業系統上面執行 的話，你就不能輕易地把它換掉，或者指望在 FreeBSD 上有很相似的應用程式才有機會。如果你想要的" "是一個強健的辦公室或是網路伺服器，或是一部穩定的工作站，FreeBSD 無疑是您的最佳選擇。世界各地有很多使用者，包括初學或資深的 UNIX 管理人員都選用 FreeBSD 當他們唯一的桌上作業系統。" #. (itstool) path: answer/para -#: book.translate.xml:285 +#: book.translate.xml:286 msgid "" "Users migrating to FreeBSD from another UNIX-like environment will find FreeBSD to be similar. Windows and Mac OS users may be interested in instead using TrueOS, a FreeBSD-based desktop distribution. Non-UNIX users should " "expect to invest some additional time learning the UNIX way of doing things. This FAQ " "and the FreeBSD Handbook are excellent places to start." msgstr "" "如果你是從其他的 UNIX-like 環境轉換到 FreeBSD 的話會很熟悉。 Windows 或是 Mac OS 的使用者可能會對 TrueOS 有興趣，他" "是基於 FreeBSD 的一個桌面環境發行版，非UNIX 使用者可能就要多花一點時間來學習怎麼用 UNIX 的 方法來做事。你可以從這份 FAQ 和 FreeBSD 使用手冊 來入門。" #. (itstool) path: question/para -#: book.translate.xml:299 +#: book.translate.xml:300 msgid "Why is it called FreeBSD?" msgstr "為什麼要叫做 FreeBSD？" #. (itstool) path: listitem/para -#: book.translate.xml:305 +#: book.translate.xml:306 msgid "It may be used free of charge, even by commercial users." msgstr "您可以免費使用它，即使是用於商業用途。" #. (itstool) path: listitem/para -#: book.translate.xml:310 +#: book.translate.xml:311 msgid "" "Full source for the operating system is freely available, and the minimum possible restrictions have been placed upon its use, distribution and " "incorporation into other work (commercial or non-commercial)." msgstr "整個 FreeBSD 作業系統完整的原始程式都可以免費取得，而且不管是在使用，散佈或是整合進其他程式等各方面也只受到最小的限制 (不論是否用於商業用途)。" #. (itstool) path: listitem/para -#: book.translate.xml:318 +#: book.translate.xml:319 msgid "" "Anyone who has an improvement or bug fix is free to submit their code and have it added to the source tree (subject to one or two obvious provisions)." msgstr "任何人都可以自由地把他對系統的改良或錯誤修正的程式碼加入 source tree 之中 (當然要符合幾個先決條件)。" #. (itstool) path: answer/para -#: book.translate.xml:325 +#: book.translate.xml:326 msgid "" "It is worth pointing out that the word free is being used in two ways here: one meaning at no cost and the other meaning " "do whatever you like. Apart from one or two things you cannot do with the FreeBSD code, for example pretending you " "wrote it, you can really do whatever you like with it." msgstr "" "特別值得注意的是這裡的 “free” 出現了兩次，而且它們 的意思是不一樣的：一種代表 “免費”，另一種代表 “自由”。您可以拿 FreeBSD 去做任何您想要做的事，除了一些" "例外，例如您宣稱 FreeBSD 是您寫的。" #. (itstool) path: question/para -#: book.translate.xml:337 +#: book.translate.xml:338 msgid "What are the differences between FreeBSD and NetBSD, OpenBSD, and other open source BSD operating systems?" msgstr "FreeBSD 及 NetBSD, OpenBSD 以及其他 open source BSD 作業系統之間有何不同之處呢？" #. (itstool) path: answer/para -#: book.translate.xml:343 +#: book.translate.xml:344 #, fuzzy msgid "" "James Howard wrote a good explanation of the history and differences between the various projects, called The BSD Family Tree which goes a fair way to answering this question. Some of the information is out of date, but " "the history portion in particular remains accurate." msgstr "" "James Howard 寫了一篇關於不同計畫的差異和歷史淵源的好文章叫 The BSD Family " "Tree 可以回答這個問題。雖然有些資訊有點過時，但是關於歷史淵源的部份仍是相當正確的。" #. (itstool) path: answer/para -#: book.translate.xml:350 +#: book.translate.xml:351 msgid "Most of the BSDs share patches and code, even today. All of the BSDs have common ancestry." msgstr "時至今日，大部分的 BSD 家族仍是共用修補和程式碼的。這些 BSD 家族有著共同的祖先。" #. (itstool) path: answer/para -#: book.translate.xml:353 +#: book.translate.xml:354 msgid "" "The design goals of FreeBSD are described in , above. The design goals of the other most popular BSDs may be " "summarized as follows:" msgstr " FreeBSD 的設計目的如 所述。其他 BSD 家族的設計目的如下所述：" #. (itstool) path: listitem/para -#: book.translate.xml:359 +#: book.translate.xml:360 msgid "" "OpenBSD aims for operating system security above all else. The OpenBSD team wrote ssh1 and pf4, which have both been ported to " "FreeBSD." msgstr "" "OpenBSD 目標在作業系統的安全性。OpenBSD團隊寫的 ssh1 和 " "pf4 都移植到了 FreeBSD。" #. (itstool) path: listitem/para -#: book.translate.xml:366 +#: book.translate.xml:367 msgid "NetBSD aims to be easily ported to other hardware platforms." msgstr "NetBSD 目標在易於移植到其他的硬體平台。" #. (itstool) path: listitem/para -#: book.translate.xml:371 +#: book.translate.xml:372 msgid "" "DragonFly BSD is a fork of FreeBSD 4.8 that has since developed many interesting features of its own, including the HAMMER file system and support for " "user-mode vkernels." msgstr "DragonFly BSD 是 FreeBSD 4.8 的一個分支，發展出許多有趣的特色，包括 HAMMER 檔案系統和支援 vkernels 使用者模式。" #. (itstool) path: question/para -#: book.translate.xml:382 +#: book.translate.xml:383 msgid "What is the latest version of FreeBSD?" msgstr "最新版的 FreeBSD 是那一版？" #. (itstool) path: answer/para -#: book.translate.xml:386 +#: book.translate.xml:387 #, fuzzy msgid "" "At any point in the development of FreeBSD, there can be multiple parallel branches. 12.X releases are made from the " "12-STABLE branch, and 11.X releases are made from the 11-STABLE branch." msgstr "" "在 FreeBSD 開發的任何時間點，都有多個平行的分支。11.X releases 是從 11-STABLE 分支而來，而 10." "X releases 是從 10-STABLE 分支而來。" #. (itstool) path: answer/para -#: book.translate.xml:391 +#: book.translate.xml:392 #, fuzzy msgid "" "Up until the release of 9.0, the 11.X series was the one known as -STABLE. However, as of 13." "X, the 11.X branch will be designated for an extended support status and receive " "only fixes for major problems, such as security-related fixes." msgstr "" "在 9.0 之前，10.X 系列仍屬 -STABLE分支。 然而從12.X 發行開始，10." "X 將只著重在重大問題上(比如：漏洞修補、安全維護)以及所謂的 extended support 。" #. (itstool) path: answer/para -#: book.translate.xml:402 +#: book.translate.xml:403 #, fuzzy msgid "" -"Version 12.0 is the latest release from the 12-" -"STABLE branch; it was released in December 2018. Version 10.4 is the latest release from the 11-STABLE branch; it was released in October 2017." +"Version 12.0 is the latest release from the " +"12-STABLE branch; it was released in December 2018. Version 11.2 is the latest release from the 11-STABLE branch; it was released in June 2018." msgstr "" "於 2017年七月所發行的 11.1 是目前最新的 11-" "STABLE 分支。 於 2017年十月所發行的 10.4是目前最新" "的 10-STABLE 分支。" #. (itstool) path: answer/para -#: book.translate.xml:408 +#: book.translate.xml:409 msgid "" "Releases are made every few months. While many people stay more up-to-date with the FreeBSD sources (see the " "questions on FreeBSD-CURRENT and FreeBSD-STABLE) than that, doing so is more of a " "commitment, as the sources are a moving target." msgstr "" "Releases 版 每幾個月 才會發行一次。 雖然如此，有很多人和 FreeBSD 原始碼同步更新 (詳見 FreeBSD-CURRENT 和 FreeBSD-STABLE的相關問題) ，但因為原始碼是一直不斷地在變動的，所以如果要這麼做的話得要花上" "更多的精力。" #. (itstool) path: answer/para -#: book.translate.xml:415 +#: book.translate.xml:416 msgid "" "More information on FreeBSD releases can be found on the Release " "Engineering page and in release7." msgstr "" "其他更多相關 FreeBSD 發行情報，可由 FreeBSD 網站上的 Release Engineering " "頁面 和 release7得知。" #. (itstool) path: question/para -#: book.translate.xml:423 +#: book.translate.xml:424 msgid "What is FreeBSD-CURRENT?" msgstr "什麼是 FreeBSD-CURRENT?" #. (itstool) path: answer/para -#: book.translate.xml:427 +#: book.translate.xml:428 msgid "" "FreeBSD-CURRENT is the development version " "of the operating system, which will in due course become the new FreeBSD-STABLE branch. As such, it is really only of interest to developers working on " "the system and die-hard hobbyists. See the relevant section in the Handbook for details on " "running -CURRENT." msgstr "" "FreeBSD-CURRENT 指的是正在發展中的作業系統版" "本，它終將在適當的時機成為 FreeBSD-STABLE 分支。它實在是只適合給系統發展者以及有毅力的業餘愛好者使用 。如果想要得到有關如何使用-CURRENT的深入資訊，請參考使用手冊的相關部份。" #. (itstool) path: answer/para -#: book.translate.xml:436 +#: book.translate.xml:437 msgid "" "Users not familiar with FreeBSD should not use FreeBSD-CURRENT. This branch sometimes evolves quite quickly and due to mistake can be un-buildable at " "times. People that use FreeBSD-CURRENT are expected to be able to analyze, debug, and report problems." msgstr "" "如果您對 FreeBSD 本身並不是很熟悉那麼您就不應該使用FreeBSD-CURRENT。 這個分支的程式碼有時候變動得很快，而且可能會因此 而使您有好幾天的時間無法更新您的系" "統。我們假設使用 FreeBSD-CURRENT 的使用者都有能力去分析他們所遇到的問題，除錯，並且回報問題。" #. (itstool) path: answer/para -#: book.translate.xml:442 +#: book.translate.xml:443 msgid "" "FreeBSD snapshot releases are made based on the current state of the -CURRENT and -STABLE branches. The goals behind each snapshot release are:" msgstr "" "我們每天都會根據目前 -CURRENT 和 -STABLE 的狀況對這兩個分支各發行一個 snapshot 版。發表這些 snapshot 的目的在於：" #. (itstool) path: listitem/para -#: book.translate.xml:450 +#: book.translate.xml:451 msgid "To test the latest version of the installation software." msgstr "測試最新版的安裝程式。" #. (itstool) path: listitem/para -#: book.translate.xml:455 +#: book.translate.xml:456 msgid "" "To give people who would like to run -CURRENT or -STABLE but who do not have the time or bandwidth to follow " "it on a day-to-day basis an easy way of bootstrapping it onto their systems." msgstr "提供一個簡單的方法給那些喜歡使用 -CURRENT 或是 -STABLE 但是沒有時間和頻寬去每天昇級的使用者。" #. (itstool) path: listitem/para -#: book.translate.xml:464 +#: book.translate.xml:465 msgid "" "To preserve a fixed reference point for the code in question, just in case we break something really badly later. (Although Subversion normally " "prevents anything horrible like this happening.)" msgstr "為了替我們發展中的程式保留一個固定的參考點，以防止我們未來不幸搞砸了。(雖然一般而言 Subversion 可以防止類似這種的可怕事件)" #. (itstool) path: listitem/para -#: book.translate.xml:471 +#: book.translate.xml:472 msgid "To ensure that all new features and fixes in need of testing have the greatest possible number of potential testers." msgstr "為了確保所有需要測試的新功能或修正都可以得到最多的測試。" #. (itstool) path: answer/para -#: book.translate.xml:477 +#: book.translate.xml:478 msgid "" "No claims are made that any -CURRENT snapshot can be considered production quality for any purpose. If a stable and " "fully tested system is needed, stick to full releases." msgstr "" "我們不對 -CURRENT snapshot 做任何目的的 品質保證 。如果你想要的是一個穩定且經過充分測試過的系統的話， 最好選擇使用完" "整 releases." #. (itstool) path: answer/para -#: book.translate.xml:483 +#: book.translate.xml:484 msgid "Snapshot releases are directly available from snapshot." msgstr "您可以直接從 snapshot 取得 -CURRENT 的 snapshot release。" #. (itstool) path: answer/para -#: book.translate.xml:485 +#: book.translate.xml:486 msgid "Official snapshots are generated on a regular basis for all actively developed branches." msgstr "對每個有在活動的分支而言，都會定期產生一次 snapshots。" #. (itstool) path: question/para -#: book.translate.xml:492 +#: book.translate.xml:493 msgid "What is the FreeBSD-STABLE concept?" msgstr "什麼是 FreeBSD-STABLE ?" #. (itstool) path: answer/para -#: book.translate.xml:497 +#: book.translate.xml:498 #, fuzzy msgid "" "Back when FreeBSD 2.0.5 was released, FreeBSD development branched in two. One branch was named -STABLE, one -CURRENT. FreeBSD-STABLE is the development branch from which major releases are made. " "Changes go into this branch at a slower pace and with the general assumption that they have first been tested in FreeBSD-CURRENT. However, at any given " "time, the sources for FreeBSD-STABLE may or may not be suitable for general use, as it may uncover bugs and corner cases that were not yet found in " "FreeBSD-CURRENT. Users who do not have the resources to perform testing should instead run the most recent release of FreeBSD. FreeBSD-" "CURRENT, on the other hand, has been one unbroken line since 2.0 was released, leading towards 12.0-RELEASE and beyond. For more detailed " "information on branches see FreeBSD " "Release Engineering: Creating the Release Branch, the status of the branches and the upcoming release schedule can be found on the Release Engineering Information page." msgstr "" "回溯到 FreeBSD 2.0.5 剛發表的時候，我們決定把 FreeBSD 的發展 分成兩支。一支叫做 -STABLE，另一支叫 -CURRENT。主要發行版是由FreeBSD-STABLE 這個開發分支而來。他的變動較慢，而且一般來說假設他們都已經先在FreeBSD-" "CURRENT測試過了。然而在任何時候，FreeBSD-STABLE的原始碼仍有可能不一定適合一般用途，因為他可能包含在 FreeBSD-CURRENT 沒有發現到的錯誤。沒有能力和資源的使" "用者應該改使用 FreeBSD 正式發行版。FreeBSD-CURRENT 從2.0開始就是另一個分支，一直到11.1-RELEASE和之後的版本都還是。更多關於開發分支" "的資訊請見 FreeBSD Release Engineering: " "Creating the Release Branch ，分支的開發狀態和接下來的發行計畫時間表可以在 Release " "Engineering 資訊 找到。" #. (itstool) path: answer/para -#: book.translate.xml:519 +#: book.translate.xml:520 #, fuzzy msgid "" "12.0-STABLE is the actively developed -STABLE branch. The latest release on the 12.0-STABLE branch is 12.0-RELEASE, which was " "released in December 2018." msgstr "11.1-STABLE 是目前正在發展中的 -STABLE 分支。最新的 11.1-STABLE 是在 2017年七月發行的 11.1-RELEASE。" #. (itstool) path: answer/para -#: book.translate.xml:525 +#: book.translate.xml:526 msgid "" "The 12-CURRENT branch is the actively developed -CURRENT branch toward the next generation of FreeBSD. See " "What is FreeBSD-CURRENT? for more information on this branch." msgstr "" "12-CURRENT 這個分支是 FreeBSD 的 -CURRENT 分支，仍然不斷地在發展當中。 如果想要知道更多關於這個分支的資訊的" "話，請參考 什麼是 FreeBSD-CURRENT? 。" #. (itstool) path: question/para -#: book.translate.xml:535 +#: book.translate.xml:536 msgid "When are FreeBSD releases made?" msgstr "每次新的 FreeBSD 將於什麼時候推出？" #. (itstool) path: answer/para -#: book.translate.xml:539 +#: book.translate.xml:540 msgid "" "The Release Engineering Team re@FreeBSD.org releases a new major version of FreeBSD about every 18 months and a new minor version about " "every 8 months, on average. Release dates are announced well in advance, so that the people working on the system know when their projects need to be " "finished and tested. A testing period precedes each release, to ensure that the addition of new features does not compromise the stability of the " "release. Many users regard this caution as one of the best things about FreeBSD, even though waiting for all the latest goodies to reach -" "STABLE can be a little frustrating." msgstr "" "一般而言，Release Engineering Team re@FreeBSD.org 約每18個月發行一次主要發行版本，約平均每8個月發行一次次要發行版本。每次新版本的發表時程" "都會事先公告， 相關的開發人員就會知道，什麼時候該先把手邊的計劃完成並且測試過， 此外，這些更動都已經完整地測試過，確保新功能不會影響系統的穩定度。 雖" "然，等這些好東西進入-STABLE 的時間令人等得有些不耐煩， 但是大多數的使用者都認為這種謹慎的態度是 FreeBSD 最好的優點之一。" #. (itstool) path: answer/para -#: book.translate.xml:551 +#: book.translate.xml:552 msgid "" "More information on the release engineering process (including a schedule of upcoming releases) can be found on the release engineering pages on the FreeBSD Web site." msgstr "" "有關發行情報的更多細節部分(包括 release 的行程表、進度)，都可在 FreeBSD 網站上的 發行情報" " 上面獲得。" #. (itstool) path: answer/para -#: book.translate.xml:556 +#: book.translate.xml:557 msgid "For people who need or want a little more excitement, binary snapshots are made weekly as discussed above." msgstr "為了滿足那些需要 (或想要) 新鮮刺激感的使用者， 上面已經提到我們每周都會發行 snapshots 版可供使用。" #. (itstool) path: question/para -#: book.translate.xml:564 +#: book.translate.xml:565 msgid "Who is responsible for FreeBSD?" msgstr "誰負責 FreeBSD 的發展？" #. (itstool) path: answer/para -#: book.translate.xml:568 +#: book.translate.xml:569 msgid "" "The key decisions concerning the FreeBSD project, such as the overall direction of the project and who is allowed to add code to the source tree, are " "made by a core team of 9 people. There is a much larger team of more than 350 " "committers who are authorized to " "make changes directly to the FreeBSD source tree." msgstr "" "如果是一些有關 FreeBSD 計畫的關鍵性決定，像是整個計畫的走向 或是決定誰可以改 source tree 裡的程式碼這類的事，是由一個由 9 個 人所組成的 core team 來決定。而有另一群超過 350 個人的 committers 有權利可以直接修改 FreeBSD 的 source tree。" #. (itstool) path: answer/para -#: book.translate.xml:576 +#: book.translate.xml:577 msgid "" "However, most non-trivial changes are discussed in advance in the mailing lists, and there are no restrictions on who " "may take part in the discussion." msgstr "無論如何，大多數的改變都會事前在 郵件論壇先討論過，而且不分角色，每個人都可以參與討論。" #. (itstool) path: question/para -#: book.translate.xml:585 +#: book.translate.xml:586 msgid "Where can I get FreeBSD?" msgstr "我要如何取得 FreeBSD？" #. (itstool) path: answer/para -#: book.translate.xml:589 +#: book.translate.xml:590 #, fuzzy msgid "" -"Every significant release of FreeBSD is available via anonymous FTP from the FreeBSD FTP site:" +"Every significant release of FreeBSD is available via anonymous FTP from the FreeBSD " +"FTP site:" msgstr "每個 FreeBSD 的重要版本都可以經由匿名 FTP 從 FreeBSD FTP 站 取得：" #. (itstool) path: listitem/para -#: book.translate.xml:595 +#: book.translate.xml:596 #, fuzzy msgid "" -"The latest 12-STABLE release, 12.0-RELEASE can be found in the 12.0-RELEASE directory." +"The latest 12-STABLE release, 12.0-RELEASE can be found in the 12.0-RELEASE directory." msgstr "" "最新版 11-STABLE , 也就是 11.1-RELEASE 請到 11.1-RELEASE 這個目錄。" #. (itstool) path: listitem/para -#: book.translate.xml:601 +#: book.translate.xml:602 msgid "" "Snapshot releases are made monthly for the -CURRENT and -STABLE branch, these being of service purely to bleeding-edge testers and developers." msgstr "" "-CURRENT 和 -STABLE 分支的Snapshot版本通常每個月會做一次， 主要是為了提供給那些熱心的測試者和開發人員。" #. (itstool) path: listitem/para -#: book.translate.xml:608 +#: book.translate.xml:609 #, fuzzy msgid "" -"The latest 11-STABLE release, 10.4-RELEASE can be found in the 10.4-RELEASE directory." +"The latest 11-STABLE release, 11.2-RELEASE can be found in the 11.2-RELEASE directory." msgstr "" "最新版 10-STABLE , 也就是10.4-RELEASE 請到 10.4-" "RELEASE 這個目錄。" #. (itstool) path: answer/para -#: book.translate.xml:614 +#: book.translate.xml:615 msgid "" "Information about obtaining FreeBSD on CD, DVD, and other media can be found in the Handbook." msgstr "" "FreeBSD 的 CD、DVD，還有其他取得方式可以在 the Handbook 中找到" "解答。" #. (itstool) path: question/para -#: book.translate.xml:622 +#: book.translate.xml:623 msgid "How do I access the Problem Report database?" msgstr "我要如何去查詢、提交問題回報(Problem Report，簡稱PR)資料庫呢？" #. (itstool) path: answer/para -#: book.translate.xml:626 +#: book.translate.xml:627 msgid "" "The Problem Report database of all user change requests may be queried by using our web-based PR query interface." msgstr "所有使用者的變更要求都可以經由網頁版的 PR 查詢 界面來察看。" #. (itstool) path: answer/para -#: book.translate.xml:630 +#: book.translate.xml:631 msgid "" "The web-based problem report submission interface can be used to submit problem " "reports through a web browser." msgstr "可以使用瀏覽器經由網頁版的 PR 界面 來傳送問題回報" #. (itstool) path: answer/para -#: book.translate.xml:634 +#: book.translate.xml:635 msgid "" "Before submitting a problem report, read Writing " "FreeBSD Problem Reports, an article on how to write good problem reports." msgstr "" "然而，在您回報問題之前，請先閱讀 如何撰寫 FreeBSD 的問" "題回報單，這是一篇告訴你怎樣才能寫出一篇真正有用的問題回報單。" #. (itstool) path: chapter/title -#: book.translate.xml:643 +#: book.translate.xml:644 msgid "Documentation and Support" msgstr "文件與技術支援" #. (itstool) path: question/para -#: book.translate.xml:648 +#: book.translate.xml:649 msgid "What good books are there about FreeBSD?" msgstr "名稱" #. (itstool) path: answer/para -#: book.translate.xml:652 +#: book.translate.xml:653 #, fuzzy msgid "" "The project produces a wide range of documentation, available online from this link: https://www." "FreeBSD.org/docs.html. In addition, the the " "bibliography in the Handbook reference other recommended books." msgstr "" "FreeBSD 文件計畫已陸續發表了相當廣泛範圍的文件，可在 https://www.FreeBSD.org/docs.html 取" "得。除此之外，也請參閱本篇。問與答最後的 書目，以及手冊中的 書目" #. (itstool) path: question/para -#: book.translate.xml:662 +#: book.translate.xml:663 msgid "Is the documentation available in other formats, such as plain text (ASCII), or PostScript?" msgstr "這些文件有其他格式的嗎？像是：純文字(ASCII)或 PostScript 之類的格式？" #. (itstool) path: answer/para -#: book.translate.xml:667 +#: book.translate.xml:668 msgid "" "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." msgstr "" "有的。這些文件都分別以不同格式儲存以及壓縮處理並放在 FTP 上面，可以從各個 FreeBSD FTP 站的 /" "pub/FreeBSD/doc/ 目錄內找到你要的。" #. (itstool) path: answer/para -#: book.translate.xml:672 +#: book.translate.xml:673 msgid "The documentation is categorized in a number of different ways. These include:" msgstr "文件以幾種不同的方式分類。包括：" #. (itstool) path: listitem/para -#: book.translate.xml:677 +#: book.translate.xml:678 msgid "The document's name, such as faq, or handbook." msgstr "文件名稱，例如：faq (常見問答集)或是 handbook (FreeBSD 使用手冊)等等。" #. (itstool) path: listitem/para -#: book.translate.xml:683 +#: book.translate.xml:684 msgid "" "The document's language and encoding. These are based on the locale names found under /usr/share/locale on a FreeBSD system. The " "current languages and encodings are as follows:" msgstr "文件的語言與編碼。他們是基於 FreeBSD 系統中 /usr/share/locale 裡所見到的語系名稱。目前包含的語言與編碼如下：" #. (itstool) path: row/entry -#: book.translate.xml:693 +#: book.translate.xml:694 msgid "Name" msgstr "語系名稱" #. (itstool) path: row/entry -#: book.translate.xml:695 book.translate.xml:845 +#: book.translate.xml:696 book.translate.xml:846 msgid "Meaning" msgstr "說明" #. (itstool) path: row/entry -#: book.translate.xml:701 +#: book.translate.xml:702 msgid "en_US.ISO8859-1" msgstr "en_US.ISO8859-1" #. (itstool) path: row/entry -#: book.translate.xml:703 +#: book.translate.xml:704 msgid "English (United States)" msgstr "英文 (美國)" #. (itstool) path: row/entry -#: book.translate.xml:707 +#: book.translate.xml:708 msgid "bn_BD.ISO10646-1" msgstr "bn_BD.ISO10646-1" #. (itstool) path: row/entry -#: book.translate.xml:709 +#: book.translate.xml:710 msgid "Bengali or Bangla (Bangladesh)" msgstr "孟加拉文 (孟加拉)" #. (itstool) path: row/entry -#: book.translate.xml:713 +#: book.translate.xml:714 msgid "da_DK.ISO8859-1" msgstr "da_DK.ISO8859-1" #. (itstool) path: row/entry -#: book.translate.xml:715 +#: book.translate.xml:716 msgid "Danish (Denmark)" msgstr "丹麥文 (丹麥)" #. (itstool) path: row/entry -#: book.translate.xml:719 +#: book.translate.xml:720 msgid "de_DE.ISO8859-1" msgstr "de_DE.ISO8859-1" #. (itstool) path: row/entry -#: book.translate.xml:721 +#: book.translate.xml:722 msgid "German (Germany)" msgstr "德文 (德國)" #. (itstool) path: row/entry -#: book.translate.xml:725 +#: book.translate.xml:726 msgid "el_GR.ISO8859-7" msgstr "el_GR.ISO8859-7" #. (itstool) path: row/entry -#: book.translate.xml:727 +#: book.translate.xml:728 msgid "Greek (Greece)" msgstr "希臘文 (希臘)" #. (itstool) path: row/entry -#: book.translate.xml:731 +#: book.translate.xml:732 msgid "es_ES.ISO8859-1" msgstr "es_ES.ISO8859-1" #. (itstool) path: row/entry -#: book.translate.xml:733 +#: book.translate.xml:734 msgid "Spanish (Spain)" msgstr "西班牙文 (西班牙)" #. (itstool) path: row/entry -#: book.translate.xml:737 +#: book.translate.xml:738 msgid "fr_FR.ISO8859-1" msgstr "fr_FR.ISO8859-1" #. (itstool) path: row/entry -#: book.translate.xml:739 +#: book.translate.xml:740 msgid "French (France)" msgstr "法文 (法國)" #. (itstool) path: row/entry -#: book.translate.xml:743 +#: book.translate.xml:744 msgid "hu_HU.ISO8859-2" msgstr "hu_HU.ISO8859-2" #. (itstool) path: row/entry -#: book.translate.xml:745 +#: book.translate.xml:746 msgid "Hungarian (Hungary)" msgstr "匈牙利文 (匈牙利)" #. (itstool) path: row/entry -#: book.translate.xml:749 +#: book.translate.xml:750 msgid "it_IT.ISO8859-15" msgstr "it_IT.ISO8859-15" #. (itstool) path: row/entry -#: book.translate.xml:751 +#: book.translate.xml:752 msgid "Italian (Italy)" msgstr "義大利文 (義大利)" #. (itstool) path: row/entry -#: book.translate.xml:755 +#: book.translate.xml:756 msgid "ja_JP.eucJP" msgstr "ja_JP.eucJP" #. (itstool) path: row/entry -#: book.translate.xml:757 +#: book.translate.xml:758 msgid "Japanese (Japan, EUC encoding)" msgstr "日文 (日本, EUC 編碼)" #. (itstool) path: row/entry -#: book.translate.xml:761 +#: book.translate.xml:762 #, fuzzy msgid "ko_KR.UTF-8" msgstr "mn_MN.UTF-8" #. (itstool) path: row/entry -#: book.translate.xml:763 +#: book.translate.xml:764 #, fuzzy msgid "Korean (Korea, UTF-8 encoding)" msgstr "蒙古文 (蒙古, UTF-8 編碼)" #. (itstool) path: row/entry -#: book.translate.xml:767 +#: book.translate.xml:768 msgid "mn_MN.UTF-8" msgstr "mn_MN.UTF-8" #. (itstool) path: row/entry -#: book.translate.xml:769 +#: book.translate.xml:770 msgid "Mongolian (Mongolia, UTF-8 encoding)" msgstr "蒙古文 (蒙古, UTF-8 編碼)" #. (itstool) path: row/entry -#: book.translate.xml:774 +#: book.translate.xml:775 msgid "nl_NL.ISO8859-1" msgstr "nl_NL.ISO8859-1" #. (itstool) path: row/entry -#: book.translate.xml:776 +#: book.translate.xml:777 msgid "Dutch (Netherlands)" msgstr "荷蘭文 (荷蘭)" #. (itstool) path: row/entry -#: book.translate.xml:780 +#: book.translate.xml:781 msgid "pl_PL.ISO8859-2" msgstr "pl_PL.ISO8859-2" #. (itstool) path: row/entry -#: book.translate.xml:782 +#: book.translate.xml:783 msgid "Polish (Poland)" msgstr "波蘭文 (波蘭)" #. (itstool) path: row/entry -#: book.translate.xml:786 +#: book.translate.xml:787 msgid "pt_BR.ISO8859-1" msgstr "pt_BR.ISO8859-1" #. (itstool) path: row/entry -#: book.translate.xml:788 +#: book.translate.xml:789 msgid "Portuguese (Brazil)" msgstr "葡萄牙文 (巴西)" #. (itstool) path: row/entry -#: book.translate.xml:792 +#: book.translate.xml:793 msgid "ru_RU.KOI8-R" msgstr "ru_RU.KOI8-R" #. (itstool) path: row/entry -#: book.translate.xml:794 +#: book.translate.xml:795 msgid "Russian (Russia, KOI8-R encoding)" msgstr "俄文 (俄羅斯, KOI8-R 編碼)" #. (itstool) path: row/entry -#: book.translate.xml:798 +#: book.translate.xml:799 msgid "tr_TR.ISO8859-9" msgstr "tr_TR.ISO8859-9" #. (itstool) path: row/entry -#: book.translate.xml:800 +#: book.translate.xml:801 msgid "Turkish (Turkey)" msgstr "土耳其文 (土耳其)" #. (itstool) path: row/entry -#: book.translate.xml:804 +#: book.translate.xml:805 msgid "zh_CN.UTF-8" msgstr "zh_CN.UTF-8" #. (itstool) path: row/entry -#: book.translate.xml:806 +#: book.translate.xml:807 msgid "Simplified Chinese (China, UTF-8 encoding)" msgstr "簡體中文 (中國, UTF-8 編碼)" #. (itstool) path: row/entry -#: book.translate.xml:811 +#: book.translate.xml:812 msgid "zh_TW.UTF-8" msgstr "zh_TW.UTF-8" #. (itstool) path: row/entry -#: book.translate.xml:813 +#: book.translate.xml:814 msgid "Traditional Chinese (Taiwan, UTF-8 encoding)" msgstr "正體中文 (台灣, UTF-8 編碼)" #. (itstool) path: note/para -#: book.translate.xml:821 +#: book.translate.xml:822 msgid "Some documents may not be available in all languages." msgstr "上列的各國翻譯語系文件中，並非所有文件都有翻譯。" #. (itstool) path: listitem/para -#: book.translate.xml:827 +#: book.translate.xml:828 msgid "" "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:" msgstr "" "文件的格式。我們的每份文件都提供許多不同的格式，每種格式各有利弊， 有些格式適合線上閱讀，有些則適合列印出美觀的文件。 這些不同格式的文件能夠確保我們的讀" "者們，無論是在螢幕上閱讀或是列印成紙本，都能夠閱讀他們感興趣的內容，目前有提供的格式如下：" #. (itstool) path: row/entry -#: book.translate.xml:843 +#: book.translate.xml:844 msgid "Format" msgstr "格式" #. (itstool) path: row/entry -#: book.translate.xml:851 +#: book.translate.xml:852 msgid "html-split" msgstr "html-split" #. (itstool) path: row/entry -#: book.translate.xml:853 +#: book.translate.xml:854 msgid "A collection of small, linked, HTML files." msgstr "依章節區分成多個小的、互相連結的 HTML 檔案" #. (itstool) path: row/entry -#: book.translate.xml:858 +#: book.translate.xml:859 msgid "html" msgstr "html" #. (itstool) path: row/entry -#: book.translate.xml:860 +#: book.translate.xml:861 msgid "One large HTML file containing the entire document" msgstr "所有內容包含在單一個 HTML 檔案" #. (itstool) path: row/entry -#: book.translate.xml:865 +#: book.translate.xml:866 msgid "pdf" msgstr "pdf" #. (itstool) path: row/entry -#: book.translate.xml:867 +#: book.translate.xml:868 msgid "Adobe's Portable Document Format" msgstr " \tAdobe's PDF 格式" #. (itstool) path: row/entry -#: book.translate.xml:871 +#: book.translate.xml:872 msgid "ps" msgstr "ps" #. (itstool) path: row/entry -#: book.translate.xml:873 +#: book.translate.xml:874 msgid "PostScript" msgstr "PostScript" #. (itstool) path: row/entry -#: book.translate.xml:877 +#: book.translate.xml:878 msgid "rtf" msgstr "rtf" #. (itstool) path: row/entry -#: book.translate.xml:879 +#: book.translate.xml:880 msgid "Microsoft's Rich Text Format" msgstr "Microsoft 的 RTF 格式" #. (itstool) path: row/entry -#: book.translate.xml:883 +#: book.translate.xml:884 msgid "txt" msgstr "txt" #. (itstool) path: row/entry -#: book.translate.xml:885 +#: book.translate.xml:886 msgid "Plain text" msgstr " \t純文字" #. (itstool) path: note/para -#: book.translate.xml:892 +#: book.translate.xml:893 msgid "" "Page numbers are not automatically updated when loading Rich Text Format into Word. Press CtrlA, CtrlEnd, F9 after loading the document, to " "update the page numbers." msgstr "" "當用 Word 讀取 RTF 格式時，頁碼並不會被自動更新。在開啟檔案後按下CtrlA, " "CtrlEnd, F9 來更新頁碼。" #. (itstool) path: listitem/para -#: book.translate.xml:901 +#: book.translate.xml:902 msgid "The compression and packaging scheme." msgstr "壓縮和打包方式" #. (itstool) path: listitem/para -#: book.translate.xml:905 +#: book.translate.xml:906 #, fuzzy msgid "" "Where the format is html-split, the files are bundled up using tar1. The resulting .tar is then compressed using the compression schemes detailed in the next point." msgstr "" "當採用 html-split 格式時，檔案先透過 tar1 工具來進" "行打包。接著在將產生出來的 .tar 檔接透過第二點所述的壓縮方式壓縮。" #. (itstool) path: listitem/para -#: book.translate.xml:914 +#: book.translate.xml:915 msgid "All the other formats generate one file. For example, article.pdf, book.html, and so on." msgstr "其他的格式都是單一個檔案。例如 article.pdf、book.html ，以此類推。" #. (itstool) path: listitem/para -#: book.translate.xml:919 +#: book.translate.xml:920 msgid "" "These files are then compressed using either the zip or bz2 compression schemes. " "tar1 can be used to uncompress these files." msgstr "" "這些檔案接著透過 zip 或 bz2 來壓縮。 tar1 工具可用來解壓縮這些檔案。" #. (itstool) path: listitem/para -#: book.translate.xml:925 +#: book.translate.xml:926 msgid "" "So the PostScript version of the Handbook, compressed using bzip2 will be stored in a " "file called book.ps.bz2 in the handbook/ directory." msgstr "" "因此 PostScript 版本的手冊經過 bzip2 壓縮後會存成一個叫做 book.ps.bz2 的檔案，並位於 handbook/ 資料夾。" #. (itstool) path: answer/para -#: book.translate.xml:935 +#: book.translate.xml:936 msgid "" "After choosing the format and compression mechanism, download the compressed files, uncompress them, and then copy the appropriate documents into place." msgstr "在選取格式與壓縮方式後，下載壓縮後的檔案並解壓縮，再把文件複製到想要的地方。" #. (itstool) path: answer/para -#: book.translate.xml:940 +#: book.translate.xml:941 msgid "" "For example, the split HTML version of the FAQ, compressed using bzip21, can be found in doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2 To download and uncompress that " "file, type:" msgstr "" "舉例來說，透過 bzip21 壓縮的英文問與答的章節分割 HTML 版本，可以在 " "doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2 中找到。若要下載並解壓縮這個檔案，請輸入" #. (itstool) path: answer/screen -#: book.translate.xml:946 +#: book.translate.xml:947 #, no-wrap msgid "" "# fetch https://download.freebsd.org/ftp/doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2\n" "# tar xvf book.html-split.tar.bz2" msgstr "" "# fetch https://download.freebsd.org/ftp/doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2\n" "# tar xvf book.html-split.tar.bz2" #. (itstool) path: answer/para -#: book.translate.xml:949 +#: book.translate.xml:950 msgid "" "If the file is compressed, tar will automatically detect the appropriate format and decompress it correctly, resulting in 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." msgstr "" "如果檔案被壓縮過的話，tar 會自動偵測正確的格式並解壓縮出一堆 .html 檔案。主要的檔案是 index." "html，包含了主目錄跟介紹以及連接到文件其他部份的連結。" #. (itstool) path: question/para -#: book.translate.xml:962 +#: book.translate.xml:963 msgid "Where do I find info on the FreeBSD mailing lists? What FreeBSD news groups are available?" msgstr "哪裡有關於 FreeBSD 的郵遞論壇(mailing lists)呢？ 有哪些可以使用的 FreeBSD 新聞群組(news groups)呢?" #. (itstool) path: answer/para -#: book.translate.xml:967 +#: book.translate.xml:968 msgid "" "Refer to the Handbook entry on mailing-lists and the Handbook entry on newsgroups." msgstr "" "請參考FreeBSD 使用手冊上的 郵件論壇 (mailing-" "lists) 。" #. (itstool) path: question/para -#: book.translate.xml:975 +#: book.translate.xml:976 msgid "Are there FreeBSD IRC (Internet Relay Chat) channels?" msgstr "有 FreeBSD IRC (Internet Relay Chat)頻道嗎？" #. (itstool) path: answer/para -#: book.translate.xml:980 +#: book.translate.xml:981 msgid "Yes, most major IRC networks host a FreeBSD chat channel:" msgstr "有的，大部分的 IRC 主機都有 FreeBSD 聊天頻道：" #. (itstool) path: listitem/para -#: book.translate.xml:985 +#: book.translate.xml:986 msgid "" "Channel #FreeBSDhelp on EFNet is a channel dedicated to helping FreeBSD " "users." msgstr "EFNet 上的 #FreeBSDhelp 頻道專門用來幫助 FreeBSD 使用著" #. (itstool) path: listitem/para -#: book.translate.xml:990 +#: book.translate.xml:991 msgid "" "Channel #FreeBSD on Freenode is a general help channel with many users at any time. " "The conversations have been known to run off-topic for a while, but priority is given to users with FreeBSD questions. Other users can help with the " "basics, referring to the Handbook whenever possible and providing links for learning more about a particular topic. This is primarily an English " "speaking channel, though it does have users from all over the world. Non-native English speakers should try to ask the question in English first and " "then relocate to ##freebsd-lang as appropriate." msgstr "" "Freenode 上的 #FreeBSD 頻道是一個有許多使用者的一般求助頻道。這個頻道時常聊一些題外" "話，但主要還是讓使用者問 FreeBSD 相關問題的地方。其他使用者可以協助解答一些基本的問題，並請盡量提供使用手冊的參考或是提供連結來提供更深入的資訊。雖然這" "個頻道有來自世界各地的使用者，但這是一個英文為主的頻道。非母語人士應該以英文提問，並在必要的時候移駕到 ##freebsd-lang 頻道。" #. (itstool) path: listitem/para -#: book.translate.xml:1006 +#: book.translate.xml:1007 msgid "" "Channel #FreeBSD on DALNET is available at irc.dal.net in " "the US and irc.eu.dal.net in Europe." msgstr "" "DALNET 的#FreeBSD 頻道，可由 irc.dal.net （位於美國）及" "irc.eu.dal.net （位於歐洲）進入。" #. (itstool) path: listitem/para -#: book.translate.xml:1013 +#: book.translate.xml:1014 msgid "" "Channel #FreeBSD on 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." msgstr "" "UNDERNET 上的 #FreeBSD 頻道可由 us.undernet.org（位於美" "國）及 eu.undernet.org （位於歐洲）進入。由於這是個輔助新手用的頻道， 請記得閱讀別人向你提及的連結或檔案。" #. (itstool) path: listitem/para -#: book.translate.xml:1022 +#: book.translate.xml:1023 msgid "" "Channel #FreeBSD on RUSNET is a Russian language channel dedicated to helping " "FreeBSD users. This is also good place for non-technical discussions." msgstr "" "RUSNET 上的 #FreeBSD 頻道是俄語國家的 FreeBSD 使用者頻道。 這裡同時也是一般交流" "的討論好去處。" #. (itstool) path: listitem/para -#: book.translate.xml:1029 +#: book.translate.xml:1030 msgid "" "Channel #bsdchat on Freenode is a Traditional Chinese (UTF-8 encoding) language " "channel dedicated to helping FreeBSD users. This is also good place for non-technical discussions." msgstr "" "Freenode 上的 #bsdchat 頻道是一個正體中文（UTF-8 編碼）頻道專門用來幫助 FreeBSD 使用" "著。這裡也歡迎一般非技術的交流討論。" #. (itstool) path: answer/para -#: book.translate.xml:1037 +#: book.translate.xml:1038 #, fuzzy msgid "The FreeBSD wiki has a good list of IRC channels." msgstr "FreeBSD 的維基百科有一份 IRC 頻道的 完整清單。" #. (itstool) path: answer/para -#: book.translate.xml:1040 +#: book.translate.xml:1041 msgid "" "Each of these channels are distinct and are not connected to each other. Since their chat styles differ, try each to find one suited to your chat style." msgstr "每個頻道都是不同且互相獨立的。因為他們的聊天風格不同，您可以每個都試試看來找到適合您的頻道。" #. (itstool) path: question/para -#: book.translate.xml:1049 +#: book.translate.xml:1050 msgid "Are there any web based forums to discuss FreeBSD?" msgstr "有沒有任何網頁形式的 FreeBSD 論壇呢？" #. (itstool) path: answer/para -#: book.translate.xml:1052 +#: book.translate.xml:1053 msgid "The official FreeBSD forums are located at https://forums.FreeBSD.org/." msgstr "官方的 FreeBSD 論壇位於 https://forums.FreeBSD.org/。" #. (itstool) path: question/para -#: book.translate.xml:1058 +#: book.translate.xml:1059 msgid "Where can I get commercial FreeBSD training and support?" msgstr "可以從哪邊獲得商業化的 FreeBSD 的教育課程及技術支援呢？" #. (itstool) path: answer/para -#: book.translate.xml:1063 +#: book.translate.xml:1064 msgid "" "iXsystems, Inc., parent company of the FreeBSD " "Mall, provides commercial FreeBSD and TrueOS software support, in addition to " "FreeBSD development and tuning solutions." msgstr "" "iXsystems, Inc.， FreeBSD 商城的母公司，提" "供 FreeBSD 開發與調校解決方案與 FreeBSD 與 TrueOS 的軟體 支援。" #. (itstool) path: answer/para -#: book.translate.xml:1070 +#: book.translate.xml:1071 msgid "" "BSD Certification Group, Inc. provides system administration certifications for DragonFly BSD, FreeBSD, NetBSD, and OpenBSD. Refer to their site for more information." msgstr "" "BSD Certification Group, Inc. 提供 DragonFly BSD、FreeBSD、NetBSD 與 OpenBSD 的系統管理認證。請參閱 他們的網站 來獲得更多資訊。" #. (itstool) path: answer/para -#: book.translate.xml:1075 +#: book.translate.xml:1076 msgid "Any other organizations providing training and support should contact the Project to be listed here." msgstr "如果有其他組織提供技術訓練或技術支援，請聯絡 FreeBSD 計畫來加入以上清單。" #. (itstool) path: info/title -#: book.translate.xml:1084 +#: book.translate.xml:1085 msgid "Installation" msgstr "安裝" #. (itstool) path: affiliation/address -#: book.translate.xml:1092 +#: book.translate.xml:1093 #, no-wrap msgid "" "\n" "\t nik@FreeBSD.org\n" "\t " msgstr "" "\n" "\t nik@FreeBSD.org\n" "\t " #. (itstool) path: info/author -#: book.translate.xml:1086 +#: book.translate.xml:1087 msgid " Nik Clayton <_:address-1/> " msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1103 +#: book.translate.xml:1104 msgid "" "Which platform should I download? I have a 64 bit capable Intel CPU, but I only see amd64." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1109 +#: book.translate.xml:1110 msgid "" "amd64 is the term FreeBSD uses for 64-bit compatible x86 architectures (also known as \"x86-64\" or \"x64\"). Most modern computers should use amd64. " "Older hardware should use i386. When installing on a non-x86-compatible architecture, select the platform which best matches the hardware." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1120 +#: book.translate.xml:1121 msgid "Which file do I download to get FreeBSD?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1124 +#: book.translate.xml:1125 msgid "" "On the Getting FreeBSD page, select [iso] next to the architecture " "that matches the hardware." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1128 +#: book.translate.xml:1129 msgid "Any of the following can be used:" msgstr "" #. (itstool) path: row/entry -#: book.translate.xml:1134 +#: book.translate.xml:1135 msgid "file" msgstr "檔案" #. (itstool) path: row/entry -#: book.translate.xml:1135 +#: book.translate.xml:1136 msgid "description" msgstr "描述" #. (itstool) path: row/entry -#: book.translate.xml:1141 +#: book.translate.xml:1142 msgid "disc1.iso" msgstr "disc1.iso" #. (itstool) path: row/entry -#: book.translate.xml:1142 +#: book.translate.xml:1143 msgid "Contains enough to install FreeBSD and a minimal set of packages." msgstr "" #. (itstool) path: row/entry -#: book.translate.xml:1147 +#: book.translate.xml:1148 msgid "dvd1.iso" msgstr "dvd1.iso" #. (itstool) path: row/entry -#: book.translate.xml:1148 +#: book.translate.xml:1149 msgid "Similar to disc1.iso but with additional packages." msgstr "" #. (itstool) path: row/entry -#: book.translate.xml:1153 +#: book.translate.xml:1154 msgid "memstick.img" msgstr "memstick.img" #. (itstool) path: row/entry -#: book.translate.xml:1154 +#: book.translate.xml:1155 msgid "A bootable image sufficient for writing to a USB stick." msgstr "" #. (itstool) path: row/entry -#: book.translate.xml:1159 +#: book.translate.xml:1160 msgid "bootonly.iso" msgstr "bootonly.iso" #. (itstool) path: row/entry -#: book.translate.xml:1160 +#: book.translate.xml:1161 msgid "A minimal image that requires network access during installation to completely install FreeBSD." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1168 +#: book.translate.xml:1169 msgid "" "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." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1177 +#: book.translate.xml:1178 msgid "What do I do if the install image does not boot?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1182 +#: book.translate.xml:1183 msgid "This can be caused by not downloading the image in binary mode when using FTP." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1186 +#: book.translate.xml:1187 msgid "" "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 SHA-256 checksum of the downloaded boot image: " "if it is not exactly that on the server, then the download process is suspect." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1195 +#: book.translate.xml:1196 msgid "" "When using a command line FTP client, type binary at the FTP command prompt after getting connected to the server and before " "starting the download of the image." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1204 +#: book.translate.xml:1205 msgid "Where are the instructions for installing FreeBSD?" msgstr "可以在哪邊找到安裝 FreeBSD 的解說步驟呢？" #. (itstool) path: answer/para -#: book.translate.xml:1208 +#: book.translate.xml:1209 msgid "" "Installation instructions can be found at Handbook entry on " "installing FreeBSD." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1216 +#: book.translate.xml:1217 msgid "What are the minimum requirements to run FreeBSD?" msgstr "要跑 FreeBSD 至少需要什麼樣的配備呢？" #. (itstool) path: answer/para -#: book.translate.xml:1220 +#: book.translate.xml:1221 msgid "FreeBSD requires a 486 or better PC, 64 MB or more of RAM, and at least 1.1 GB of hard disk space." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1228 +#: book.translate.xml:1229 msgid "How can I make my own custom release or install disk?" msgstr "要怎樣才能自行打造專用的安裝磁片呢？" #. (itstool) path: answer/para -#: book.translate.xml:1233 +#: book.translate.xml:1234 msgid "" "Customized FreeBSD installation media can be created by building a custom release. Follow the instructions in the Release Engineering article." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1242 +#: book.translate.xml:1243 msgid "Can Windows co-exist with FreeBSD?" msgstr "Windows 可以與 FreeBSD 共存嗎？" #. (itstool) path: answer/para -#: book.translate.xml:1246 +#: book.translate.xml:1247 msgid "" "If Windows is installed first, then yes. FreeBSD's boot manager will then manage to boot Windows and FreeBSD. If Windows is installed afterwards, it will overwrite the " "boot manager. If that happens, see the next section." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1256 +#: book.translate.xml:1257 msgid "Another operating system destroyed my Boot Manager. How do I get it back?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1261 +#: book.translate.xml:1262 msgid "" "This depends upon the boot manager. The FreeBSD boot selection menu can be reinstalled using boot0cfg8. For example, to restore the boot menu onto the disk ada0:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:1266 +#: book.translate.xml:1267 #, no-wrap msgid "# boot0cfg -B ada0" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1268 +#: book.translate.xml:1269 msgid "" "The non-interactive MBR bootloader can be installed using gpart8:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:1271 +#: book.translate.xml:1272 #, no-wrap msgid "# gpart bootcode -b /boot/mbr ada0" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1273 +#: book.translate.xml:1274 msgid "For more complex situations, including GPT disks, see gpart8." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1280 +#: book.translate.xml:1281 msgid "Do I need to install the source?" msgstr "我需要安裝完整的原始碼嗎？" #. (itstool) path: answer/para -#: book.translate.xml:1284 +#: book.translate.xml:1285 msgid "" "In general, no. There is nothing in the base system which requires the presence of the source to operate. Some ports, like sysutils/lsof, will not build unless the source is installed. In particular, if the port builds a kernel module or directly operates on kernel structures, " "the source must be installed." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1295 +#: book.translate.xml:1296 msgid "Do I need to build a kernel?" msgstr "需要重新 build kernel 嗎？" #. (itstool) path: answer/para -#: book.translate.xml:1299 +#: book.translate.xml:1300 msgid "" "Usually not. The supplied GENERIC kernel contains the drivers an ordinary computer will need. freebsd-" "update8, the FreeBSD binary upgrade tool, cannot upgrade custom kernels, another reason to stick " "with the GENERIC kernel when possible. For computers with very limited RAM, such as embedded systems, it may be worthwhile to build " "a smaller custom kernel containing just the required drivers." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1312 +#: book.translate.xml:1313 msgid "Should I use DES, Blowfish, or MD5 passwords and how do I specify which form my users receive?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1317 +#: book.translate.xml:1318 msgid "" "FreeBSD uses SHA512 by default. DES passwords are still available for backwards compatibility with operating systems that still " "use the less secure password format. FreeBSD also supports the Blowfish and MD5 password formats. 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 login.conf5 manual page for more information about login capabilities." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1336 +#: book.translate.xml:1337 msgid "What are the limits for FFS file systems?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1340 +#: book.translate.xml:1341 msgid "" "For FFS file systems, the largest file system is practically limited by the amount of memory required to fsck8 the file system. fsck8 requires one bit per fragment, which with the default fragment size of 4 KB equates to 32 MB of memory per TB of disk. This does mean " "that on architectures which limit userland processes to 2 GB (e.g., i386), the maximum fsck8'able filesystem is ~60 TB." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1349 +#: book.translate.xml:1350 msgid "" "If there was not a fsck8 memory limit the maximum filesystem size " "would be 2 ^ 64 (blocks) * 32 KB => 16 Exa * 32 KB => 512 ZettaBytes." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1354 +#: book.translate.xml:1355 msgid "" "The maximum size of a single FFS file is approximately 2 PB with the default block size of 32 KB. Each 32 KB block can point to 4096 blocks. With " "triple indirect blocks, the calculation is 32 KB * 12 + 32 KB * 4096 + 32 KB * 4096^2 + 32 KB * 4096^3. Increasing the block size to 64 KB will " "increase the max file size by a factor of 16." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1366 +#: book.translate.xml:1367 msgid "Why do I get an error message, readin failed after compiling and booting a new kernel?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1372 +#: book.translate.xml:1373 msgid "" "The world and kernel are out of sync. This is not supported. Be sure to use make buildworld and make buildkernel " "to update the kernel." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1377 +#: book.translate.xml:1378 msgid "" "Boot the system by specifying the kernel directly at the second stage, pressing any key when the | shows up before loader is started." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1386 +#: book.translate.xml:1387 msgid "Is there a tool to perform post-installation configuration tasks?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1391 +#: book.translate.xml:1392 msgid "Yes. bsdconfig provides a nice interface to configure FreeBSD post-installation." msgstr "" #. (itstool) path: chapter/title -#: book.translate.xml:1399 +#: book.translate.xml:1400 msgid "Hardware Compatibility" msgstr "硬體相容性" #. (itstool) path: sect1/title -#: book.translate.xml:1402 +#: book.translate.xml:1403 msgid "General" msgstr "一般問題" #. (itstool) path: question/para -#: book.translate.xml:1407 +#: book.translate.xml:1408 msgid "I want to get a piece of hardware for my FreeBSD system. Which model/brand/type is best?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1412 +#: book.translate.xml:1413 msgid "" "This is discussed continually on the FreeBSD mailing lists but is to be expected since hardware changes so quickly. Read through the Hardware Notes for " "FreeBSD 12.0 or 10.4 and search the mailing list archives11.2 and search the mailing list archives before asking about the latest and greatest hardware. Chances are a discussion about that type of hardware took place just last week." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1422 +#: book.translate.xml:1423 msgid "" "Before purchasing a laptop, check the archives for FreeBSD laptop " "computer mailing list and FreeBSD general questions mailing " "list, or possibly a specific mailing list for a particular hardware type." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1430 +#: book.translate.xml:1431 msgid "What are the limits for memory? Does FreeBSD support more than 4 GB of memory (RAM)? More than 16 GB? More than 48 GB?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1437 +#: book.translate.xml:1438 msgid "" "FreeBSD as an operating system generally supports as much physical memory (RAM) as the platform it is running on does. Keep in mind that different " "platforms have different limits for memory; for example i386 without PAE supports at most 4 GB of memory (and " "usually less than that because of PCI address space) and i386 with PAE supports at most 64 GB memory. As of FreeBSD 10, AMD64 " "platforms support up to 4 TB of physical memory." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1452 +#: book.translate.xml:1453 msgid "Why does FreeBSD report less than 4 GB memory when installed on an i386 machine?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1457 +#: book.translate.xml:1458 msgid "" "The total address space on i386 machines is 32-bit, meaning that at most 4 GB of memory is addressable (can be accessed). " "Furthermore, some addresses in this range are reserved by hardware for different purposes, for example for using and controlling PCI devices, for " "accessing video memory, and so on. Therefore, the total amount of memory usable by the operating system for its kernel and applications is limited to " "significantly less than 4 GB. Usually, 3.2 GB to 3.7 GB is the maximum usable physical memory in this configuration." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1469 +#: book.translate.xml:1470 msgid "" "To access more than 3.2 GB to 3.7 GB of installed memory (meaning up to 4 GB but also more than 4 GB), a special tweak called PAE " "must be used. PAE stands for Physical Address Extension and is a way for 32-bit x86 CPUs to address more than 4 GB of memory. It remaps the memory that " "would otherwise be overlaid by address reservations for hardware devices above the 4 GB range and uses it as additional physical memory (see " "pae4). Using PAE has some drawbacks; this mode of memory access is a " "little bit slower than the normal (without PAE) mode and loadable modules (see kld4) are not supported. This means all drivers must be compiled into the kernel." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1484 +#: book.translate.xml:1485 msgid "" "The most common way to enable PAE is to build a new kernel with the special ready-provided kernel configuration file called PAE, " "which is already configured to build a safe kernel. Note that some entries in this kernel configuration file are too conservative and some drivers " "marked as unready to be used with PAE are actually usable. A rule of thumb is that if the driver is usable on 64-bit architectures (like AMD64), it is " "also usable with PAE. When creating a custom kernel configuration file, PAE can be enabled by adding the following line:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:1497 +#: book.translate.xml:1498 #, no-wrap msgid "options PAE" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1499 +#: book.translate.xml:1500 msgid "" "PAE is not much used nowadays because most new x86 hardware also supports running in 64-bit mode, known as AMD64 or Intel 64. It has a much larger address space and does not need such tweaks. FreeBSD supports AMD64 and it is recommended that this " "version of FreeBSD be used instead of the i386 version if 4 GB or more memory is required." msgstr "" #. (itstool) path: sect1/title -#: book.translate.xml:1512 +#: book.translate.xml:1513 msgid "Architectures and Processors" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1517 +#: book.translate.xml:1518 msgid "Does FreeBSD support architectures other than the x86?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1522 +#: book.translate.xml:1523 msgid "" "Yes. FreeBSD divides support into multiple tiers. Tier 1 architectures, such as i386 or amd64; are fully supported. Tiers 2 and 3 are supported on a " "best-effort basis. A full explanation of the tier system is available in the Committer's Guide." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1529 +#: book.translate.xml:1530 msgid "A complete list of supported architectures can be found on the platforms page." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1537 +#: book.translate.xml:1538 msgid "Does FreeBSD support Symmetric Multiprocessing (SMP)?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1542 +#: book.translate.xml:1543 msgid "" "FreeBSD supports symmetric multi-processor (SMP) on all non-embedded platforms (e.g, i386, amd64, etc.). SMP is also supported in arm and MIPS kernels, " "although some CPUs may not support this. FreeBSD's SMP implementation uses fine-grained locking, and performance scales nearly linearly with number of " "CPUs." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1550 +#: book.translate.xml:1551 msgid "smp4 has more details." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1556 +#: book.translate.xml:1557 msgid "What is microcode? How do I install Intel CPU microcode updates?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1561 +#: book.translate.xml:1562 msgid "" "Microcode is a method of programmatically implementing hardware level instructions. This allows for CPU bugs to be fixed without replacing the on board " "chip." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1566 +#: book.translate.xml:1567 msgid "Install sysutils/devcpu-data, then add:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:1569 +#: book.translate.xml:1570 #, no-wrap msgid "microcode_update_enable=\"YES\"" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1571 +#: book.translate.xml:1572 msgid "to /etc/rc.conf" msgstr "" #. (itstool) path: sect1/title -#: book.translate.xml:1578 +#: book.translate.xml:1579 msgid "Hard Drives, Tape Drives, and CD and DVD Drives" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1583 +#: book.translate.xml:1584 msgid "What kind of hard drives does FreeBSD support?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1587 +#: book.translate.xml:1588 msgid "" "FreeBSD supports EIDE, SATA, SCSI, and SAS drives (with a compatible controller; see the next section), and all drives using the original " "Western Digital interface (MFM, RLL, ESDI, and of course IDE). A few ESDI controllers that use proprietary interfaces may not work: " "stick to WD1002/3/6/7 interfaces and clones." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1599 +#: book.translate.xml:1600 msgid "Which SCSI or SAS controllers are supported?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1603 +#: book.translate.xml:1604 msgid "" "See the complete list in the Hardware Notes for FreeBSD 12.0 or 10.4." +"xlink:href=\"https://www.FreeBSD.org/releases/11.2R/hardware.html\">11.2." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1611 +#: book.translate.xml:1612 msgid "What types of tape drives are supported?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1615 +#: book.translate.xml:1616 msgid "FreeBSD supports all standard SCSI tape interfaces." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1622 +#: book.translate.xml:1623 msgid "Does FreeBSD support tape changers?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1626 +#: book.translate.xml:1627 msgid "" "FreeBSD supports SCSI changers using the ch4 device and the " "chio1 command. The details of how to control the changer can be " "found in chio1." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1631 +#: book.translate.xml:1632 msgid "" "While AMANDA and some other products already understands changers, other applications only know how to move a tape from one " "point to another. In this case, keep track of which slot a tape is in and which slot the tape currently in the drive needs to go back to." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1643 +#: book.translate.xml:1644 msgid "Which CD-ROM and CD-RW drives are supported by FreeBSD?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1648 +#: book.translate.xml:1649 msgid "Any SCSI drive connected to a supported controller is supported. Most ATAPI compatible IDE CD-ROMs are supported." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1652 +#: book.translate.xml:1653 msgid "FreeBSD supports any ATAPI-compatible IDE CD-R or CD-RW drive." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1655 +#: book.translate.xml:1656 msgid "" "FreeBSD also supports any SCSI CD-R or CD-RW drives. Install the sysutils/cdrtools port or package, then use cdrecord." msgstr "" #. (itstool) path: sect1/title -#: book.translate.xml:1664 +#: book.translate.xml:1665 msgid "Keyboards and Mice" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1669 +#: book.translate.xml:1670 msgid "Is it possible to use a mouse outside the X Window system?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1674 +#: book.translate.xml:1675 msgid "" "The default console driver, syscons4, provides the ability to use a " "mouse pointer in text consoles to cut & paste text. Run the mouse daemon, moused8, and turn on the mouse pointer in the virtual console:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:1680 +#: book.translate.xml:1681 #, no-wrap msgid "" "# moused -p /dev/xxxx -t yyyy\n" "# vidcontrol -m on" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1683 +#: book.translate.xml:1684 msgid "" "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 moused8 " "manual page for a list of supported protocol types." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1693 +#: book.translate.xml:1694 msgid "" "For a PS/2 mouse, add moused_enable=\"YES\" to /etc/rc.conf to start the mouse daemon at boot time. " "Additionally, to use the mouse daemon on all virtual terminals instead of just the console, add allscreens_flags=\"-m on\" to " "/etc/rc.conf." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1702 +#: book.translate.xml:1703 msgid "" "When the mouse daemon is running, access to the mouse 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." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1713 +#: book.translate.xml:1714 msgid "How do I cut and paste text with a mouse in the text console?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1718 +#: book.translate.xml:1719 msgid "" "It is not possible to remove data using the mouse. However, it is possible to copy and paste. Once the mouse daemon is running as described in the " "previous question, hold down button 1 (left button) and move the mouse to select a region of text. Then, press button 2 " "(middle button) to paste it at the text cursor. Pressing button 3 (right button) will extend the selected region of text." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1727 +#: book.translate.xml:1728 msgid "" "If the mouse does not have a middle button, it is possible to emulate one or remap buttons using mouse daemon options. See the " "moused8 manual page for details." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1736 +#: book.translate.xml:1737 msgid "My mouse has a fancy wheel and buttons. Can I use them in FreeBSD?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1741 +#: book.translate.xml:1742 msgid "" "The answer is, unfortunately, It depends. These mice with additional features require specialized driver in most cases. Unless the mouse " "device driver or the user program has specific support for the mouse, it will act just like a standard two, or three button mouse." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1748 +#: book.translate.xml:1749 msgid "For the possible usage of wheels in the X Window environment, refer to that section." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1755 +#: book.translate.xml:1756 msgid "How do I use my delete key in sh and csh?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1760 +#: book.translate.xml:1761 msgid "" "For the Bourne Shell, add the following lines to ~/.shrc. See sh1 and editrc5." msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:1764 +#: book.translate.xml:1765 #, no-wrap msgid "" "bind ^? ed-delete-next-char # for console\n" "bind ^[[3~ ed-delete-next-char # for xterm" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1767 +#: book.translate.xml:1768 msgid "" "For the C Shell, add the following lines to ~/.cshrc. See csh1." msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:1771 +#: book.translate.xml:1772 #, no-wrap msgid "" "bindkey ^? delete-char # for console\n" "bindkey ^[[3~ delete-char # for xterm" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1774 +#: book.translate.xml:1775 msgid "For more information, see this page." msgstr "" #. (itstool) path: sect1/title -#: book.translate.xml:1782 +#: book.translate.xml:1783 msgid "Other Hardware" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1787 +#: book.translate.xml:1788 msgid "Workarounds for no sound from my pcm4 sound card?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1792 +#: book.translate.xml:1793 msgid "Some sound cards set their output volume to 0 at every boot. Run the following command every time the machine boots:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:1796 +#: book.translate.xml:1797 #, no-wrap msgid "# mixer pcm 100 vol 100 cd 100" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1802 +#: book.translate.xml:1803 msgid "Does FreeBSD support power management on my laptop?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1807 +#: book.translate.xml:1808 msgid "" "FreeBSD supports the ACPI features found in modern hardware. Further information can be found in acpi4." msgstr "" #. (itstool) path: chapter/title -#: book.translate.xml:1817 +#: book.translate.xml:1818 msgid "Troubleshooting" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1822 +#: book.translate.xml:1823 msgid "Why is FreeBSD finding the wrong amount of memory on i386 hardware?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1827 +#: book.translate.xml:1828 msgid "The most likely reason is the difference between physical memory addresses and virtual addresses." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1830 +#: book.translate.xml:1831 msgid "" "The convention for most PC hardware is to use the memory area between 3.5 GB and 4 GB for a special purpose (usually for PCI). This address space is " "used to access PCI hardware. As a result real, physical memory cannot be accessed by that address space." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1836 +#: book.translate.xml:1837 msgid "" "What happens to the memory that should appear in that location is hardware dependent. Unfortunately, some hardware does nothing and the ability to use " "that last 500 MB of RAM is entirely lost." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1841 +#: book.translate.xml:1842 msgid "" "Luckily, most hardware remaps the memory to a higher location so that it can still be used. However, this can cause some confusion when watching the " "boot messages." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1846 +#: book.translate.xml:1847 msgid "" "On a 32-bit version of FreeBSD, the memory appears lost, since it will be remapped above 4 GB, which a 32-bit kernel is unable to access. In this case, " "the solution is to build a PAE enabled kernel. See the entry on memory limits for more information." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1852 +#: book.translate.xml:1853 msgid "" "On a 64-bit version of FreeBSD, or when running a PAE-enabled kernel, FreeBSD will correctly detect and remap the memory so it is usable. During boot, " "however, it may seem as if FreeBSD is detecting more memory than the system really has, due to the described remapping. This is normal and the " "available memory will be corrected as the boot process completes." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1864 +#: book.translate.xml:1865 msgid "Why do my programs occasionally die with Signal 11 errors?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1869 +#: book.translate.xml:1870 msgid "" "Signal 11 errors are caused when a process has attempted to access memory which the operating system has not granted it access to. If something like " "this is happening at seemingly random intervals, start investigating the cause." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1875 +#: book.translate.xml:1876 msgid "These problems can usually be attributed to either:" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:1880 +#: book.translate.xml:1881 msgid "If the problem is occurring only in a specific custom application, it is probably a bug in the code." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:1886 +#: book.translate.xml:1887 msgid "" "If it is a problem with part of the base FreeBSD system, it may also be buggy code, but more often than not these problems are found and fixed long " "before us general FAQ readers get to use these bits of code (that is what -CURRENT is for)." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1895 +#: book.translate.xml:1896 msgid "It is probably not a FreeBSD bug if the problem occurs compiling a program, but the activity that the compiler is carrying out changes each time." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1901 +#: book.translate.xml:1902 msgid "" "For example, if make buildworld fails while trying to compile ls.c into ls.o and, when run " "again, it fails in the same place, this is a broken build. Try updating source and try again. If the compile fails elsewhere, it is almost certainly " "due to hardware." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1909 +#: book.translate.xml:1910 msgid "" "In the first case, use a debugger such as gdb1 to find the point in " "the program which is attempting to access a bogus address and fix it." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1914 +#: book.translate.xml:1915 msgid "In the second case, verify which piece of hardware is at fault." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1917 +#: book.translate.xml:1918 msgid "Common causes of this include:" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:1921 +#: book.translate.xml:1922 msgid "The hard disks might be overheating: Check that the fans are still working, as the disk and other hardware might be overheating." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:1927 +#: book.translate.xml:1928 msgid "" "The processor running is overheating: This might be because the processor has been overclocked, or the fan on the processor might have died. In either " "case, ensure that the hardware is running at what it is specified to run at, at least while trying to solve this problem. If it is not, clock it back " "to the default settings.)" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:1935 +#: book.translate.xml:1936 msgid "" "Regarding overclocking, it is far cheaper to have a slow system than a fried system that needs replacing! Also the community is not sympathetic to " "problems on overclocked systems." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:1942 +#: book.translate.xml:1943 msgid "" "Dodgy memory: if multiple memory SIMMS/DIMMS are installed, pull them all out and try running the machine with each SIMM or DIMM individually to narrow " "the problem down to either the problematic DIMM/SIMM or perhaps even a combination." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:1951 +#: book.translate.xml:1952 msgid "" "Over-optimistic motherboard settings: the BIOS settings, and some motherboard jumpers, provide options to set various timings. The defaults are often " "sufficient, but sometimes setting the wait states on RAM too low, or setting the RAM Speed: Turbo option will cause strange behavior. A " "possible idea is to set to BIOS defaults, after noting the current settings first." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:1963 +#: book.translate.xml:1964 msgid "" "Unclean or insufficient power to the motherboard. Remove any unused I/O boards, hard disks, or CD-ROMs, or disconnect the power cable from them, to see " "if the power supply can manage a smaller load. Or try another power supply, preferably one with a little more power. For instance, if the current power " "supply is rated at 250 Watts, try one rated at 300 Watts." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1975 +#: book.translate.xml:1976 msgid "" "Read the section on Signal 11 for a further explanation and a discussion on how memory testing software or hardware " "can still pass faulty memory. There is an extensive FAQ on this at the SIG11 " "problem FAQ." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1982 +#: book.translate.xml:1983 msgid "" "Finally, if none of this has helped, it is possibly a bug in FreeBSD. Follow these instructions to send a problem " "report." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:1991 +#: book.translate.xml:1992 msgid "" "My system crashes with either Fatal trap 12: page fault in kernel mode, or panic:, and spits out a bunch " "of information. What should I do?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:1998 +#: book.translate.xml:1999 msgid "" "The FreeBSD developers are interested in these errors, but need more information than just the error message. Copy the full crash message. Then consult " "the FAQ section on kernel panics, build a debugging kernel, and get a " "backtrace. This might sound difficult, but does not require any programming skills. Just follow the instructions." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2011 +#: book.translate.xml:2012 msgid "What is the meaning of the error maxproc limit exceeded by uid %i, please see tuning(7) and login.conf(5)?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2017 +#: book.translate.xml:2018 msgid "" "The FreeBSD kernel will only allow a certain number of processes to exist at one time. The number is based on the kern.maxusers " "sysctl8 variable. kern.maxusers also affects " "various other in-kernel limits, such as network buffers. If the machine is heavily loaded, increase kern.maxusers. This will " "increase these other system limits in addition to the maximum number of processes." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2027 +#: book.translate.xml:2028 msgid "" "To adjust the kern.maxusers value, see the File/Process Limits section of the Handbook. While that section refers to open files, the same limits apply " "to processes." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2033 +#: book.translate.xml:2034 msgid "" "If the machine is lightly loaded but running a very large number of processes, adjust the kern.maxproc tunable by defining it in " "/boot/loader.conf. The tunable will not get adjusted until the system is rebooted. For more information about tuning tunables, see " "loader.conf5. If these processes are being run by a single user, " "adjust kern.maxprocperuid to be one less than the new kern.maxproc value. It must be at least one less because " "one system program, init8, must always be running." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2050 +#: book.translate.xml:2051 msgid "Why do full screen applications on remote machines misbehave?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2055 +#: book.translate.xml:2056 msgid "" "The remote machine may be setting the terminal type to something other than xterm which is required by the FreeBSD console. " "Alternatively the kernel may have the wrong values for the width and height of the terminal." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2061 +#: book.translate.xml:2062 msgid "" "Check the value of the TERM environment variable is xterm. If the remote machine does not support that try " "vt100." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2066 +#: book.translate.xml:2067 msgid "" "Run stty -a to check what the kernel thinks the terminal dimensions are. If they are incorrect, they can be changed by running " "stty rows RR cols CC." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2072 +#: book.translate.xml:2073 msgid "" "Alternatively, if the client machine has x11/xterm installed, then running resize will query the terminal for the " "correct dimensions and set them." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2081 +#: book.translate.xml:2082 msgid "Why does it take so long to connect to my computer via ssh or telnet?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2087 +#: book.translate.xml:2088 msgid "" "The symptom: there is a long delay between the time the TCP connection is established and the time when the client software asks for a password (or, in " "telnet1's case, when a login prompt appears)." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2093 +#: book.translate.xml:2094 msgid "" "The problem: more likely than not, the delay is caused by the server software trying to resolve the client's IP address into a hostname. Many servers, " "including the Telnet and SSH servers that come with FreeBSD, do this to store the hostname in a " "log file for future reference by the administrator." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2101 +#: book.translate.xml:2102 msgid "" "The remedy: if the problem occurs whenever connecting the client computer to any server, the problem is with the client. If the problem only occurs " "when someone connects to the server computer, the problem is with the server." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2107 +#: book.translate.xml:2108 msgid "" "If the problem is with the client, the only remedy is to fix the DNS so the server can resolve it. If this is on a local network, consider it a server " "problem and keep reading. If this is on the Internet, contact your ISP." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2113 +#: book.translate.xml:2114 msgid "" "If the problem is with the server on a local network, configure the server to resolve address-to-hostname queries for the local address range. See " "hosts5 and named8 for more information. If this is on the Internet, the problem may be that the local server's " "resolver is not functioning correctly. To check, try to look up another host such as www.yahoo.com. If it does not work, that " "is the problem." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2124 +#: book.translate.xml:2125 msgid "" "Following a fresh install of FreeBSD, it is also possible that domain and name server information is missing from /etc/resolv.conf. This will often cause a delay in SSH, as the option UseDNS is set to yes by " "default in /etc/ssh/sshd_config. If this is causing the problem, either fill in the missing information in /etc/resolv." "conf or set UseDNS to no in sshd_config as a temporary workaround." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2142 +#: book.translate.xml:2143 msgid "" "Why does file: table is full show up repeatedly in dmesg8?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2147 +#: book.translate.xml:2148 msgid "" "This error message indicates that the number of available file descriptors have been exhausted on the system. Refer to the kern.maxfiles section of the Tuning Kernel Limits section of the Handbook for a " "discussion and solution." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2158 +#: book.translate.xml:2159 msgid "Why does the clock on my computer keep incorrect time?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2163 +#: book.translate.xml:2164 msgid "The computer has two or more clocks, and FreeBSD has chosen to use the wrong one." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2166 +#: book.translate.xml:2167 msgid "" "Run dmesg8, and check for lines that contain Timecounter. The one with the highest quality value that FreeBSD chose." msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:2170 +#: book.translate.xml:2171 #, no-wrap msgid "" "# dmesg | grep Timecounter\n" "Timecounter \"i8254\" frequency 1193182 Hz quality 0\n" "Timecounter \"ACPI-fast\" frequency 3579545 Hz quality 1000\n" "Timecounter \"TSC\" frequency 2998570050 Hz quality 800\n" "Timecounters tick every 1.000 msec" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2176 +#: book.translate.xml:2177 msgid "" "Confirm this by checking the kern.timecounter.hardware sysctl3." msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:2180 +#: book.translate.xml:2181 #, no-wrap msgid "" "# sysctl kern.timecounter.hardware\n" "kern.timecounter.hardware: ACPI-fast" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2183 +#: book.translate.xml:2184 msgid "It may be a broken ACPI timer. The simplest solution is to disable the ACPI timer in /boot/loader.conf:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:2187 +#: book.translate.xml:2188 #, no-wrap msgid "debug.acpi.disabled=\"timer\"" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2189 +#: book.translate.xml:2190 msgid "" "Or the BIOS may modify the TSC clock—perhaps to change the speed of the processor when running from batteries, or going into a power saving mode, but " "FreeBSD is unaware of these adjustments, and appears to gain or lose time." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2195 +#: book.translate.xml:2196 msgid "" "In this example, the i8254 clock is also available, and can be selected by writing its name to the kern.timecounter." "hardware sysctl3." msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:2200 +#: book.translate.xml:2201 #, no-wrap msgid "" "# sysctl kern.timecounter.hardware=i8254\n" "kern.timecounter.hardware: TSC -> i8254" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2203 +#: book.translate.xml:2204 msgid "The computer should now start keeping more accurate time." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2206 +#: book.translate.xml:2207 msgid "To have this change automatically run at boot time, add the following line to /etc/sysctl.conf:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:2210 +#: book.translate.xml:2211 #, no-wrap msgid "kern.timecounter.hardware=i8254" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2216 +#: book.translate.xml:2217 msgid "What does the error swap_pager: indefinite wait buffer: mean?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2221 +#: book.translate.xml:2222 msgid "" "This means that a process is trying to page memory from disk, and the page attempt has hung trying to access the disk for more than 20 seconds. It " "might be caused by bad blocks on the disk drive, disk wiring, cables, or any other disk I/O-related hardware. If the drive itself is bad, disk errors " "will appear in /var/log/messages and in the output of dmesg. Otherwise, check the cables and connections." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2236 +#: book.translate.xml:2237 msgid "What is a lock order reversal?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2241 +#: book.translate.xml:2242 msgid "" "The FreeBSD kernel uses a number of resource locks to arbitrate contention for certain resources. When multiple kernel threads try to obtain multiple " "resource locks, there's always the potential for a deadlock, where two threads have each obtained one of the locks and blocks forever waiting for the " "other thread to release one of the other locks. This sort of locking problem can be avoided if all threads obtain the locks in the same order." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2250 +#: book.translate.xml:2251 msgid "" "A run-time lock diagnostic system called witness4, enabled in " "FreeBSD-CURRENT and disabled by default for stable branches and releases, detects the potential for deadlocks due to locking errors, including errors " "caused by obtaining multiple resource locks with a different order from different parts of the kernel. The witness4 framework tries to detect this problem as it happens, and reports it by printing a message to the " "system console about a lock order reversal (often referred to also as LOR)." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2262 +#: book.translate.xml:2263 msgid "" "It is possible to get false positives, as witness4 is conservative. " "A true positive report does not mean that a system is dead-locked; instead it should be understood as a warning that a deadlock " "could have happened here." msgstr "" #. (itstool) path: note/para -#: book.translate.xml:2269 +#: book.translate.xml:2270 msgid "" "Problematic LORs tend to get fixed quickly, so check the FreeBSD-CURRENT mailing list before posting to it." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2278 +#: book.translate.xml:2279 msgid "What does Called ... with the following non-sleepable locks held mean?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2283 +#: book.translate.xml:2284 msgid "This means that a function that may sleep was called while a mutex (or other unsleepable) lock was held." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2286 +#: book.translate.xml:2287 msgid "" "The reason this is an error is because mutexes are not intended to be held for long periods of time; they are supposed to only be held to maintain " "short periods of synchronization. This programming contract allows device drivers to use mutexes to synchronize with the rest of the kernel during " "interrupts. Interrupts (under FreeBSD) may not sleep. Hence it is imperative that no subsystem in the kernel block for an extended period while holding " "a mutex." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2296 +#: book.translate.xml:2297 msgid "" "To catch such errors, assertions may be added to the kernel that interact with the witness4 subsystem to emit a warning or fatal error (depending on the system configuration) when a potentially blocking call is made " "while holding a mutex." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2302 +#: book.translate.xml:2303 msgid "" "In summary, such warnings are non-fatal, however with unfortunate timing they could cause undesirable effects ranging from a minor blip in the system's " "responsiveness to a complete system lockup." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2307 +#: book.translate.xml:2308 msgid "" "For additional information about locking in FreeBSD see locking9." msgstr "" #. (itstool) path: para/buildtarget -#: book.translate.xml:2315 +#: book.translate.xml:2316 msgid "buildworld" msgstr "" #. (itstool) path: para/buildtarget -#: book.translate.xml:2315 +#: book.translate.xml:2316 msgid "installworld" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2314 +#: book.translate.xml:2315 msgid "Why does <_:buildtarget-1/>/<_:buildtarget-2/> die with the message touch: not found?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2321 +#: book.translate.xml:2322 msgid "" "This error does not mean that the touch1 utility is missing. The " "error is instead probably due to the dates of the files being set sometime in the future. If the CMOS clock is set to local time, run " "adjkerntz -i to adjust the kernel clock when booting into single-user mode." msgstr "" #. (itstool) path: chapter/title -#: book.translate.xml:2334 +#: book.translate.xml:2335 msgid "User Applications" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2339 +#: book.translate.xml:2340 msgid "Where are all the user applications?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2343 +#: book.translate.xml:2344 msgid "" "Refer to the ports page for info on software packages ported to FreeBSD. The list " "currently tops 24,000 and is growing daily, so come back to check often or subscribe to the FreeBSD announcements mailing list for periodic updates on new entries." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2350 +#: book.translate.xml:2351 msgid "" "Most ports should work on all supported versions of FreeBSD. Those that do not are specifically marked as such. Each time a FreeBSD release is made, a " "snapshot of the ports tree at the time of release in also included in the ports/ directory." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2356 +#: book.translate.xml:2357 msgid "" "FreeBSD supports compressed binary packages to easily install and uninstall ports. Use pkg7 to control the installation of packages." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2364 +#: book.translate.xml:2365 msgid "How do I download the Ports tree? Should I be using Subversion?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2369 +#: book.translate.xml:2370 msgid "Any of the methods listed here work:" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:2373 +#: book.translate.xml:2374 msgid "" "Use portsnap for most use cases. Refer to Using the Ports " "Collection for instructions on how to use this tool." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:2378 +#: book.translate.xml:2379 #, fuzzy msgid "" "Use Subversion if custom patches to the ports tree are needed. Refer to Using Subversion for details." msgstr "" "如果想看關於 FreeBSD 更深入的資料，請看 FreeBSD 使用手冊。" #. (itstool) path: question/para -#: book.translate.xml:2388 +#: book.translate.xml:2389 msgid "Does FreeBSD support Java?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2392 +#: book.translate.xml:2393 msgid "Yes. Refer to https://www.FreeBSD.org/java/ for more information." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2399 +#: book.translate.xml:2400 #, fuzzy msgid "Why can I not build this port on my 11.X -, or 12.X -STABLE machine?" msgstr "FreeBSD 10.X and 11.X 常見問答集" #. (itstool) path: answer/para -#: book.translate.xml:2405 +#: book.translate.xml:2406 msgid "" "If the installed FreeBSD version lags significantly behind -CURRENT or -STABLE, update the Ports Collection " "using the instructions in Using the Ports Collection. " "If the system is up-to-date, someone might have committed a change to the port which works for -CURRENT but which broke the port " "for -STABLE. Submit a bug report, since the Ports Collection is " "supposed to work for both the -CURRENT and -STABLE branches." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2422 +#: book.translate.xml:2423 msgid "I just tried to build INDEX using make index, and it failed. Why?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2427 +#: book.translate.xml:2428 msgid "" "First, make sure that the Ports Collection is up-to-date. Errors that affect building INDEX from an up-to-date copy of the Ports " "Collection are high-visibility and are thus almost always fixed immediately." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2433 +#: book.translate.xml:2434 msgid "" "There are rare cases where INDEX will not build due to odd cases involving OPTIONS_SET being set in " "make.conf. If you suspect that this is the case, try to make INDEX with those variables turned off before " "reporting it to FreeBSD ports mailing list." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2445 +#: book.translate.xml:2446 msgid "I updated the sources, now how do I update my installed ports?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2450 +#: book.translate.xml:2451 msgid "" "FreeBSD does not include a port upgrading tool, but it does have some tools to make the upgrade process somewhat easier. Additional tools are available " "to simplify port handling and are described the Upgrading " "Ports section in the FreeBSD Handbook." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2460 +#: book.translate.xml:2461 msgid "Do I need to recompile every port each time I perform a major version update?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2465 +#: book.translate.xml:2466 msgid "" "Yes! While a recent system will run with software compiled under an older release, things will randomly crash and fail to work once other ports are " "installed or updated." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2470 +#: book.translate.xml:2471 msgid "" "When the system is upgraded, various shared libraries, loadable modules, and other parts of the system will be replaced with newer versions. " "Applications linked against the older versions may fail to start or, in other cases, fail to function properly." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2476 +#: book.translate.xml:2477 msgid "" "For more information, see the section on upgrades in the FreeBSD Handbook." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2483 +#: book.translate.xml:2484 msgid "Do I need to recompile every port each time I perform a minor version update?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2488 +#: book.translate.xml:2489 msgid "" "In general, no. FreeBSD developers do their utmost to guarantee binary compatibility across all releases with the same major version number. Any " "exceptions will be documented in the Release Notes, and advice given there should be followed." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2498 +#: book.translate.xml:2499 msgid "Why is /bin/sh so minimal? Why does FreeBSD not use bash or another shell?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2504 +#: book.translate.xml:2505 msgid "" "Many people need to write shell scripts which will be portable across many systems. That is why POSIX " "specifies the shell and utility commands in great detail. Most scripts are written in Bourne shell (sh1), and because several important programming interfaces (make1, system3, " "popen3, and analogues in higher-level scripting languages like Perl " "and Tcl) are specified to use the Bourne shell to interpret commands. Because the Bourne shell is so often and widely used, it is important for it to " "be quick to start, be deterministic in its behavior, and have a small memory footprint." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2517 +#: book.translate.xml:2518 msgid "" "The existing implementation is our best effort at meeting as many of these requirements simultaneously as we can. To keep /bin/sh " "small, we have not provided many of the convenience features that other shells have. That is why other more featureful shells like bash, scsh, tcsh1, and zsh " "are available. Compare the memory utilization of these shells by looking at the VSZ and RSS columns in a ps -u listing." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2533 +#: book.translate.xml:2534 msgid "How do I create audio CDs from my MIDI files?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2537 +#: book.translate.xml:2538 msgid "" "To create audio CDs from MIDI files, first install audio/timidity++ from ports then install manually the GUS patches set by Eric A. " "Welsh, available at http://alleg.sourceforge.net/digmid.html. After " "TiMidity++ has been installed properly, MIDI files may be converted to WAV files with the following command line:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:2545 +#: book.translate.xml:2546 #, no-wrap msgid "% timidity -Ow -s 44100 -o /tmp/juke/01.wav 01.mid" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2547 +#: book.translate.xml:2548 msgid "" "The WAV files can then be converted to other formats or burned onto audio CDs, as described in the FreeBSD Handbook." msgstr "" #. (itstool) path: chapter/title -#: book.translate.xml:2556 +#: book.translate.xml:2557 msgid "Kernel Configuration" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2561 +#: book.translate.xml:2562 msgid "I would like to customize my kernel. Is it difficult?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2566 +#: book.translate.xml:2567 msgid "" "Not at all! Check out the kernel config section of the " "Handbook." msgstr "" #. (itstool) path: note/para -#: book.translate.xml:2570 +#: book.translate.xml:2571 msgid "" "The new kernel will be installed to the /boot/kernel directory along with its modules, while the old kernel " "and its modules will be moved to the /boot/kernel.old directory. If a mistake is made in the configuration, simply boot the " "previous version of the kernel." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2584 +#: book.translate.xml:2585 msgid "Why is my kernel so big?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2588 +#: book.translate.xml:2589 msgid "" "GENERIC kernels shipped with FreeBSD are compiled in debug mode. Kernels built in debug mode contain debug data " "in separate files that are used for debugging. FreeBSD releases prior to 11.0 store these debug files in the same directory as the kernel itself, " "/boot/kernel/. In FreeBSD 11.0 and later the debug files are stored in /usr/lib/debug/boot/kernel/. Note that " "there will be little or no performance loss from running a debug kernel, and it is useful to keep one around in case of a system panic." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2601 +#: book.translate.xml:2602 msgid "" "When running low on disk space, there are different options to reduce the size of /boot/kernel/ and /usr/lib/debug/." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2606 +#: book.translate.xml:2607 msgid "To not install the symbol files, make sure the following line exists in /etc/src.conf:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:2610 +#: book.translate.xml:2611 #, no-wrap msgid "WITHOUT_KERNEL_SYMBOLS=yes" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2612 +#: book.translate.xml:2613 msgid "For more information see src.conf5." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2614 +#: book.translate.xml:2615 msgid "If you want to avoid building debug files altogether, make sure that both of the following are true:" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:2619 +#: book.translate.xml:2620 msgid "This line does not exist in the kernel configuration file:" msgstr "" #. (itstool) path: listitem/programlisting -#: book.translate.xml:2622 +#: book.translate.xml:2623 #, no-wrap msgid "makeoptions DEBUG=-g" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:2626 +#: book.translate.xml:2627 msgid "Do not run config8 with ." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2631 +#: book.translate.xml:2632 msgid "Either of the above settings will cause the kernel to be built in debug mode." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2634 +#: book.translate.xml:2635 msgid "To build and install only the specified modules, list them in /etc/make.conf:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:2638 +#: book.translate.xml:2639 #, no-wrap msgid "MODULES_OVERRIDE= accf_http ipfw" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2640 +#: book.translate.xml:2641 msgid "" "Replace accf_httpd ipfw with a list of needed modules. Only the listed modules will be built. This reduces the size of the kernel " "directory and decreases the amount of time needed to build the kernel. For more information, read /usr/share/examples/etc/make.conf." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2647 +#: book.translate.xml:2648 msgid "Unneeded devices can be removed from the kernel to further reduce the size. See for more information." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2650 +#: book.translate.xml:2651 msgid "" "To put any of these options into effect, follow the instructions to build and install the new kernel." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2654 +#: book.translate.xml:2655 msgid "For reference, the FreeBSD 11 amd64 kernel (/boot/kernel/kernel) is approximately 25 MB." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2662 +#: book.translate.xml:2663 msgid "Why does every kernel I try to build fail to compile, even GENERIC?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2667 +#: book.translate.xml:2668 msgid "There are a number of possible causes for this problem:" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:2672 +#: book.translate.xml:2673 msgid "" "The source tree is different from the one used to build the currently running system. When attempting an upgrade, read /usr/src/UPDATING, paying particular attention to the COMMON ITEMS section at the end." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:2681 +#: book.translate.xml:2682 msgid "" "The make buildkernel did not complete successfully. The make buildkernel target relies on files generated by the " "make buildworld target to complete its job correctly." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:2689 +#: book.translate.xml:2690 msgid "" "Even when building FreeBSD-STABLE, it is possible that the source tree was fetched at a time when it was either being " "modified or it was broken. Only releases are guaranteed to be buildable, although FreeBSD-STABLE builds fine the " "majority of the time. Try re-fetching the source tree and see if the problem goes away. Try using a different mirror in case the previous one is having " "problems." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2705 +#: book.translate.xml:2706 msgid "Which scheduler is in use on a running system?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2710 +#: book.translate.xml:2711 msgid "The name of the scheduler currently being used is directly available as the value of the kern.sched.name sysctl:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:2714 +#: book.translate.xml:2715 #, no-wrap msgid "" "% sysctl kern.sched.name\n" "kern.sched.name: ULE" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2721 +#: book.translate.xml:2722 msgid "What is kern.sched.quantum?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2725 +#: book.translate.xml:2726 msgid "kern.sched.quantum is the maximum number of ticks a process can run without being preempted in the 4BSD scheduler." msgstr "" #. (itstool) path: chapter/title -#: book.translate.xml:2734 +#: book.translate.xml:2735 msgid "Disks, File Systems, and Boot Loaders" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2739 +#: book.translate.xml:2740 msgid "How can I add my new hard disk to my FreeBSD system?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2744 +#: book.translate.xml:2745 msgid "" "See the Adding Disks section in the FreeBSD Handbook." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2751 +#: book.translate.xml:2752 msgid "How do I move my system over to my huge new disk?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2756 +#: book.translate.xml:2757 msgid "" "The best way is to reinstall the operating system on the new disk, then move the user data over. This is highly recommended when tracking -" "STABLE for more than one release or when updating a release instead of installing a new one. Install booteasy on both disks with " "boot0cfg8 and dual boot until you are happy with the new " "configuration. Skip the next paragraph to find out how to move the data after doing this." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2766 +#: book.translate.xml:2767 msgid "" "Alternatively, partition and label the new disk with either sade8 or " "gpart8. If the disks are MBR-formatted, booteasy can be installed on " "both disks with boot0cfg8 so that the computer can dual boot to the " "old or new system after the copying is done." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2772 +#: book.translate.xml:2773 msgid "" "Once the new disk set up, the data cannot just be copied. Instead, use tools that understand device files and system flags, such as " "dump8. Although it is recommended to move the data while in single-" "user mode, it is not required." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2779 +#: book.translate.xml:2780 msgid "" "When the disks are formatted with UFS, never use anything but dump8 and restore8 to move the root file system. " "These commands should also be used when moving a single partition to another empty partition. The sequence of steps to use dump to " "move the data from one UFS partitions to a new partition is:" msgstr "" #. (itstool) path: step/para -#: book.translate.xml:2790 +#: book.translate.xml:2791 msgid "newfs the new partition." msgstr "" #. (itstool) path: step/para -#: book.translate.xml:2794 +#: book.translate.xml:2795 msgid "mount it on a temporary mount point." msgstr "" #. (itstool) path: step/para -#: book.translate.xml:2799 +#: book.translate.xml:2800 msgid "cd to that directory." msgstr "" #. (itstool) path: step/para -#: book.translate.xml:2803 +#: book.translate.xml:2804 msgid "dump the old partition, piping output to the new one." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2808 +#: book.translate.xml:2809 msgid "For example, to move /dev/ada1s1a with /mnt as the temporary mount point, type:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:2813 +#: book.translate.xml:2814 #, no-wrap msgid "" "# newfs /dev/ada1s1a\n" "# mount /dev/ada1s1a /mnt\n" "# cd /mnt\n" "# dump 0af - / | restore rf -" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2818 +#: book.translate.xml:2819 msgid "" "Rearranging partitions with dump takes a bit more work. To merge a partition like /var into its parent, create " "the new partition large enough for both, move the parent partition as described above, then move the child partition into the empty directory that the " "first move created:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:2826 +#: book.translate.xml:2827 #, no-wrap msgid "" "# newfs /dev/ada1s1a\n" "# mount /dev/ada1s1a /mnt\n" "# cd /mnt\n" "# dump 0af - / | restore rf -\n" "# cd var\n" "# dump 0af - /var | restore rf -" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2833 +#: book.translate.xml:2834 msgid "" "To split a directory from its parent, say putting /var on its own partition when it was not before, create both partitions, then " "mount the child partition on the appropriate directory in the temporary mount point, then move the old single partition:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:2839 +#: book.translate.xml:2840 #, no-wrap msgid "" "# newfs /dev/ada1s1a\n" "# newfs /dev/ada1s1d\n" "# mount /dev/ada1s1a /mnt\n" "# mkdir /mnt/var\n" "# mount /dev/ada1s1d /mnt/var\n" "# cd /mnt\n" "# dump 0af - / | restore rf -" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2847 +#: book.translate.xml:2848 msgid "" "The cpio1 and pax1 utilities are also available for moving user data. These are known to lose file flag information, " "so use them with caution." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2855 +#: book.translate.xml:2856 msgid "" "Which partitions can safely use Soft Updates? I have heard that Soft Updates on / can cause problems. What about Journaled Soft " "Updates?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2861 +#: book.translate.xml:2862 msgid "Short answer: Soft Updates can usually be safely used on all partitions." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2864 +#: book.translate.xml:2865 msgid "" "Long answer: Soft Updates has two characteristics that may be undesirable on certain partitions. First, a Soft Updates partition has a small chance of " "losing data during a system crash. The partition will not be corrupted as the data will simply be lost. Second, Soft Updates can cause temporary space " "shortages." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2871 +#: book.translate.xml:2872 msgid "" "When using Soft Updates, the kernel can take up to thirty seconds to write changes to the physical disk. When a large file is deleted the file still " "resides on disk until the kernel actually performs the deletion. This can cause a very simple race condition. Suppose one large file is deleted and " "another large file is immediately created. The first large file is not yet actually removed from the physical disk, so the disk might not have enough " "room for the second large file. This will produce an error that the partition does not have enough space, even though a large chunk of space has just " "been released. A few seconds later, the file creation works as expected." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2885 +#: book.translate.xml:2886 msgid "" "If a system should crash after the kernel accepts a chunk of data for writing to disk, but before that data is actually written out, data could be " "lost. This risk is extremely small, but generally manageable." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2890 +#: book.translate.xml:2891 msgid "These issues affect all partitions using Soft Updates. So, what does this mean for the root partition?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2893 +#: book.translate.xml:2894 msgid "" "Vital information on the root partition changes very rarely. If the system crashed during the thirty-second window after such a change is made, it is " "possible that data could be lost. This risk is negligible for most applications, but be aware that it exists. If the system cannot tolerate this much " "risk, do not use Soft Updates on the root file system!" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2901 +#: book.translate.xml:2902 msgid "" "/ is traditionally one of the smallest partitions. If /tmp is on /, there may be " "intermittent space problems. Symlinking /tmp to /var/tmp will solve this problem." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2909 +#: book.translate.xml:2910 msgid "" "Finally, dump8 does not work in live mode (-L) on a filesystem, with " "Journaled Soft Updates (SU+J)." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2917 +#: book.translate.xml:2918 msgid "Can I mount other foreign file systems under FreeBSD?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2922 +#: book.translate.xml:2923 msgid "FreeBSD supports a variety of other file systems." msgstr "" #. (itstool) path: varlistentry/term -#: book.translate.xml:2926 +#: book.translate.xml:2927 msgid "UFS" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:2929 +#: book.translate.xml:2930 msgid "" "UFS CD-ROMs can be mounted directly on FreeBSD. Mounting disk partitions from Digital UNIX and other systems that support UFS may be more complex, " "depending on the details of the disk partitioning for the operating system in question." msgstr "" #. (itstool) path: varlistentry/term -#: book.translate.xml:2938 +#: book.translate.xml:2939 msgid "ext2/ext3" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:2941 +#: book.translate.xml:2942 msgid "" "FreeBSD supports ext2fs and ext3fs partitions. See ext2fs5 for more information." msgstr "" #. (itstool) path: varlistentry/term -#: book.translate.xml:2948 +#: book.translate.xml:2949 msgid "NTFS" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:2951 +#: book.translate.xml:2952 msgid "" "FUSE based NTFS support is available as a port (sysutils/fusefs-ntfs). For more information see ntfs-3g." msgstr "" #. (itstool) path: varlistentry/term -#: book.translate.xml:2958 +#: book.translate.xml:2959 msgid "FAT" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:2961 +#: book.translate.xml:2962 msgid "" "FreeBSD includes a read-write FAT driver. For more information, see mount_msdosfs8." msgstr "" #. (itstool) path: varlistentry/term #. (itstool) path: chapter/title -#: book.translate.xml:2967 book.translate.xml:3378 +#: book.translate.xml:2968 book.translate.xml:3379 msgid "ZFS" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:2970 +#: book.translate.xml:2971 msgid "" "FreeBSD includes a port of Sun's ZFS driver. The current recommendation is to use it only on amd64 platforms with sufficient " "memory. For more information, see zfs8." msgstr "" "FreeBSD 包含由 Sun 移植過來的 ZFS 驅動程式。 目前的建議是僅在記憶體充足的 amd64 平臺上使用它。有關更詳細資訊, 請參閱 " "zfs8。" #. (itstool) path: answer/para -#: book.translate.xml:2978 +#: book.translate.xml:2979 msgid "" "FreeBSD includes the Network File System NFS and the FreeBSD Ports Collection provides several FUSE applications to support many " "other file systems." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:2987 +#: book.translate.xml:2988 msgid "How do I mount a secondary DOS partition?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:2991 +#: book.translate.xml:2992 msgid "" "The secondary DOS partitions are found after all the primary partitions. For example, if E is the second DOS " "partition on the second SCSI drive, there will be a device file for slice 5 in /dev. To mount it:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:2998 +#: book.translate.xml:2999 #, no-wrap msgid "# mount -t msdosfs /dev/da1s5 /dos/e" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3004 +#: book.translate.xml:3005 msgid "Is there a cryptographic file system for FreeBSD?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3008 +#: book.translate.xml:3009 msgid "" "Yes, gbde8 and geli8. See the Encrypting Disk Partitions section of the FreeBSD Handbook." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3017 +#: book.translate.xml:3018 msgid "How do I boot FreeBSD and Linux using GRUB?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3022 +#: book.translate.xml:3023 msgid "" "To boot FreeBSD using GRUB, add the following to either /boot/grub/menu.lst or /boot/grub/" "grub.conf, depending upon which is used by the Linux distribution." msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:3028 +#: book.translate.xml:3029 #, no-wrap msgid "" "title FreeBSD 9.1\n" "\troot (hd0,a)\n" "\tkernel /boot/loader" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3032 +#: book.translate.xml:3033 msgid "" "Where hd0,a points to the root partition on the first disk. To specify the slice number, use something like this " "(hd0,2,a). By default, if the slice number is omitted, GRUB searches the first slice which has " "the a partition." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3044 +#: book.translate.xml:3045 msgid "How do I boot FreeBSD and Linux using BootEasy?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3049 +#: book.translate.xml:3050 msgid "" "Install LILO at the start of the Linux boot partition instead of in the Master Boot Record. You can then " "boot LILO from BootEasy." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3054 +#: book.translate.xml:3055 msgid "" "This is recommended when running Windows and Linux as it makes " "it simpler to get Linux booting again if Windows is reinstalled." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3062 +#: book.translate.xml:3063 msgid "How do I change the boot prompt from ??? to something more meaningful?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3068 +#: book.translate.xml:3069 msgid "" "This cannot be accomplished with the standard boot manager without rewriting it. There are a number of other boot managers in the sysutils category of the Ports Collection." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3077 +#: book.translate.xml:3078 msgid "How do I use a new removable drive?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3081 +#: book.translate.xml:3082 msgid "If the drive already has a file system on it, use a command like this:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:3084 +#: book.translate.xml:3085 #, no-wrap msgid "# mount -t msdosfs /dev/da0s1 /mnt" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3086 +#: book.translate.xml:3087 msgid "" "If the drive will only be used with FreeBSD systems, partition it with UFS or ZFS. This will provide long " "filename support, improvement in performance, and stability. If the drive will be used by other operating systems, a more portable choice, such as " "msdosfs, is better." msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:3093 +#: book.translate.xml:3094 #, no-wrap msgid "" "# dd if=/dev/zero of=/dev/da0 count=2\n" "# gpart create -s GPT /dev/da0\n" "# gpart add -t freebsd-ufs /dev/da0" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3097 +#: book.translate.xml:3098 msgid "Finally, create a new file system:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:3099 +#: book.translate.xml:3100 #, no-wrap msgid "# newfs /dev/da0p1" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3101 +#: book.translate.xml:3102 msgid "and mount it:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:3103 +#: book.translate.xml:3104 #, no-wrap msgid "# mount /dev/da0s1 /mnt" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3105 +#: book.translate.xml:3106 msgid "" "It is a good idea to add a line to /etc/fstab (see fstab5) so you can just type mount /mnt in the future:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:3110 +#: book.translate.xml:3111 #, no-wrap msgid "/dev/da0p1 /mnt ufs rw,noauto 0 0" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3116 +#: book.translate.xml:3117 msgid "Why do I get Incorrect super block when mounting a CD?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3121 +#: book.translate.xml:3122 msgid "" "The type of device to mount must be specified. This is described in the Handbook section on Using Data CDs." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3129 +#: book.translate.xml:3130 msgid "Why do I get Device not configured when mounting a CD?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3134 +#: book.translate.xml:3135 msgid "" "This generally means that there is no CD in the drive, or the drive is not visible on the bus. Refer to the Using Data CDs section of the Handbook for a detailed discussion of this issue." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3144 +#: book.translate.xml:3145 msgid "Why do all non-English characters in filenames show up as ? on my CDs when mounted in FreeBSD?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3149 +#: book.translate.xml:3150 msgid "" "The CD probably uses the Joliet extension for storing information about files and directories. This is discussed in the Handbook section " "on Using Data CD-ROMs." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3159 +#: book.translate.xml:3160 msgid "A CD burned under FreeBSD cannot be read under any other operating system. Why?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3164 +#: book.translate.xml:3165 msgid "" "This means a raw file was burned to the CD, rather than creating an ISO 9660 file system. Take a look at the Handbook section on Using Data CDs." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3173 +#: book.translate.xml:3174 msgid "How can I create an image of a data CD?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3177 +#: book.translate.xml:3178 msgid "" "This is discussed in the Handbook section on Writing Data to an ISO File System. For more on working with CD-ROMs, see the Creating CDs Section in the Storage chapter in the Handbook." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3187 +#: book.translate.xml:3188 msgid "Why can I not mount an audio CD?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3192 +#: book.translate.xml:3193 msgid "" "Trying to mount an audio CD will produce an error like cd9660: /dev/cd0: Invalid argument. This is because mount only works on file systems. Audio CDs do not have file systems; they just have data. Instead, use a program that reads audio CDs, such as the " "audio/xmcd package or port." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3204 +#: book.translate.xml:3205 msgid "How do I mount a multi-session CD?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3209 +#: book.translate.xml:3210 msgid "" "By default, mount8 will attempt to mount the last data track " "(session) of a CD. To load an earlier session, use the command line argument. Refer to mount_cd96608 for specific examples." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3219 +#: book.translate.xml:3220 msgid "How do I let ordinary users mount CD-ROMs, DVDs, USB drives, and other removable media?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3224 +#: book.translate.xml:3225 msgid "As root set the sysctl variable vfs.usermount to 1." msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:3228 +#: book.translate.xml:3229 #, no-wrap msgid "# sysctl vfs.usermount=1" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3230 +#: book.translate.xml:3231 msgid "" "To make this persist across reboots, add the line vfs.usermount=1 to /etc/sysctl.conf so that it is reset at " "system boot time." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3235 +#: book.translate.xml:3236 msgid "" "Users can only mount devices they have read permissions to. To allow users to mount a device permissions must be set in /etc/devfs.conf." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3240 +#: book.translate.xml:3241 msgid "For example, to allow users to mount the first USB drive add:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:3243 +#: book.translate.xml:3244 #, no-wrap msgid "" "# Allow all users to mount a USB drive.\n" "\t own /dev/da0 root:operator\n" "\t perm /dev/da0 0666" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3247 +#: book.translate.xml:3248 msgid "All users can now mount devices they could read onto a directory that they own:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:3250 +#: book.translate.xml:3251 #, no-wrap msgid "" "% mkdir ~/my-mount-point\n" "% mount -t msdosfs /dev/da0 ~/my-mount-point" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3253 +#: book.translate.xml:3254 msgid "Unmounting the device is simple:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:3255 +#: book.translate.xml:3256 #, no-wrap msgid "% umount ~/my-mount-point" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3257 +#: book.translate.xml:3258 msgid "" "Enabling vfs.usermount, however, has negative security implications. A better way to access MS-DOS formatted media is to use the emulators/mtools package in the Ports Collection." msgstr "" #. (itstool) path: note/para -#: book.translate.xml:3264 +#: book.translate.xml:3265 msgid "The device name used in the previous examples must be changed according to the configuration." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3272 +#: book.translate.xml:3273 msgid "The du and df commands show different amounts of disk space available. What is going on?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3278 +#: book.translate.xml:3279 msgid "" "This is due to how these commands actually work. du goes through the directory tree, measures how large each file is, and presents " "the totals. df just asks the file system how much space it has left. They seem to be the same thing, but a file without a directory " "entry will affect df but not du." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3287 +#: book.translate.xml:3288 msgid "" "When a program is using a file, and the file is deleted, the file is not really removed from the file system until the program stops using it. The file " "is immediately deleted from the directory listing, however. As an example, consider a file large enough to affect the output of du " "and df. A file being viewed with more can be deleted wihout causing an error. The entry is removed from the " "directory so no other program or user can access it. However, du shows that it is gone as it has walked the directory tree and the " "file is not listed. df shows that it is still there, as the file system knows that more is still using that " "space. Once the more session ends, du and df will agree." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3307 +#: book.translate.xml:3308 msgid "" "This situation is common on web servers. Many people set up a FreeBSD web server and forget to rotate the log files. The access log fills up /" "var. The new administrator deletes the file, but the system still complains that the partition is full. Stopping and restarting the web " "server program would free the file, allowing the system to release the disk space. To prevent this from happening, set up " "newsyslog8." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3316 +#: book.translate.xml:3317 msgid "Note that Soft Updates can delay the freeing of disk space and it can take up to 30 seconds for the change to be visible." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3324 +#: book.translate.xml:3325 msgid "How can I add more swap space?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3328 +#: book.translate.xml:3329 msgid "" "This section of the Handbook describes how to " "do this." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3335 +#: book.translate.xml:3336 msgid "Why does FreeBSD see my disk as smaller than the manufacturer says it is?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3340 +#: book.translate.xml:3341 msgid "" "Disk manufacturers calculate gigabytes as a billion bytes each, whereas FreeBSD calculates them as 1,073,741,824 bytes each. This explains why, for " "example, FreeBSD's boot messages will report a disk that supposedly has 80 GB as holding 76,319 MB." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3347 +#: book.translate.xml:3348 msgid "Also note that FreeBSD will (by default) reserve 8% of the disk space." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3354 +#: book.translate.xml:3355 msgid "How is it possible for a partition to be more than 100% full?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3359 +#: book.translate.xml:3360 msgid "" "A portion of each UFS partition (8%, by default) is reserved for use by the operating system and the root " "user. df1 does not count that space when calculating the " "Capacity column, so it can exceed 100%. Notice that the Blocks column is always greater than the sum of the " "Used and Avail columns, usually by a factor of 8%." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3369 +#: book.translate.xml:3370 msgid "For more details, look up in tunefs8." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3383 +#: book.translate.xml:3384 msgid "What is the minimum amount of RAM one should have to run ZFS?" msgstr "使用 ZFS 最少需要多少記憶體？" #. (itstool) path: answer/para -#: book.translate.xml:3388 +#: book.translate.xml:3389 msgid "A minimum of 4GB of RAM is required for comfortable usage, but individual workloads can vary widely." msgstr "至少需要 4GB 的記憶體才能跑得順，但不同的工作負載可能會造成相當大的差異。" #. (itstool) path: question/para -#: book.translate.xml:3395 +#: book.translate.xml:3396 msgid "What is the ZIL and when does it get used?" msgstr "ZIL 是什麼而又何時會被使用？" #. (itstool) path: answer/para -#: book.translate.xml:3399 +#: book.translate.xml:3400 msgid "" "The ZIL (ZFS intent log) is a write log used to implement posix write commitment semantics across crashes. " "Normally writes are bundled up into transaction groups and written to disk when filled (Transaction Group Commit). However syscalls like " "fsync2 require a commitment that the data is written to stable " "storage before returning. The ZIL is needed for writes that have been acknowledged as written but which are not yet on disk as part of a transaction. " "The transaction groups are timestamped. In the event of a crash the last valid timestamp is found and missing data is merged in from the ZIL." msgstr "" "The ZIL (ZFS 動向日誌) 是一個紀錄日誌，用以實現系統當機時 POSIX 寫入保證的語義，多個正常 ZFS 寫入動作會被分成多個" "交易處理群組，並在交易處理群組被填滿時寫入磁碟 (Transaction Group Commit)。然而像 fsync2 這樣的系統呼叫，會要求該系統呼叫在返回前，能承諾已將資料寫入磁碟，ZIL 就是用來紀錄確認為已執行寫入" "的資料，但其實尚未存在於磁碟上，即尚未完成交易處理，交易處理群組具有時間戳記，在系統當機後，找到 ZIL 最後一個有效的時間戳記，即將遺失的資料再舍併至磁碟" "上。" #. (itstool) path: question/para -#: book.translate.xml:3417 +#: book.translate.xml:3418 msgid "Do I need a SSD for ZIL?" msgstr "我需要用固態硬碟 (SSD) 來存 ZIL 嗎？" #. (itstool) path: answer/para -#: book.translate.xml:3421 +#: book.translate.xml:3422 msgid "" "By default, ZFS stores the ZIL in the pool with all the data. If an application has a heavy write load, storing the ZIL in a separate device that has " "very fast synchronous, sequential write performance can improve overall system. For other workloads, a SSD is unlikely to make much of an improvement." msgstr "" "ZFS 預設將 ZIL 儲存在包含所有資料的 zpool 中，如果應用程式的寫入負載很重，將 ZIL 儲存在同步速度非常快的獨立設備中，藉由循序寫入效能的提高可以改善整個系" "統的效能，對於其他類型的工作負載， 固態硬碟就不會有太大的助益。" #. (itstool) path: question/para -#: book.translate.xml:3432 +#: book.translate.xml:3433 msgid "What is the L2ARC?" msgstr "L2ARC 是什麼？" #. (itstool) path: answer/para -#: book.translate.xml:3436 +#: book.translate.xml:3437 msgid "" "The L2ARC is a read cache stored on a fast device such as an SSD. This cache is not persistent across reboots. " "Note that RAM is used as the first layer of cache and the L2ARC is only needed if there is insufficient RAM." msgstr "" "The L2ARC (Second Level Adaptive Replacement Cache) 是存於快速儲存設備 SSD 上的讀取快取，此快取在重新開機後會消" "失，請注意記憶體是第一層的快取，只有在記憶體不足的情況下才需要 L2ARC。" #. (itstool) path: answer/para -#: book.translate.xml:3442 +#: book.translate.xml:3443 msgid "" "L2ARC needs space in the ARC to index it. So, perversely, a working set that fits perfectly in the ARC will not fit perfectly any more if a L2ARC is " "used because part of the ARC is holding the L2ARC index, pushing part of the working set into the L2ARC which is slower than RAM." msgstr "" "L2ARC 需要 ARC 的空間來為其製作索引，因此，有一種反常的情況，如果有一種工作集 (working set) 可以完美地剛好放入 ARC，一旦系統使用 L2ARC，該工作集的運作將" "不再完美，因為 ARC 需要用一部分空間來保存 L2ARC 的索引，以至於必須將工作集的一部分存入比記憶體慢的 L2ARC。" #. (itstool) path: question/para -#: book.translate.xml:3453 +#: book.translate.xml:3454 msgid "Is enabling deduplication advisable?" msgstr "建議啟用去冗餘 (deduplication) 嗎？" #. (itstool) path: answer/para -#: book.translate.xml:3457 +#: book.translate.xml:3458 msgid "Generally speaking, no." msgstr "一般而言，不建議這麼做。" #. (itstool) path: answer/para -#: book.translate.xml:3459 +#: book.translate.xml:3460 msgid "" "Deduplication takes up a significant amount of RAM and may slow down read and write disk access times. Unless one is storing data that is very heavily " "duplicated, such as virtual machine images or user backups, it is possible that deduplication will do more harm than good. Another consideration is the " "inability to revert deduplication status. If data is written when deduplication is enabled, disabling dedup will not cause those blocks which were " "deduplicated to be replicated until they are next modified." msgstr "" "去冗餘需要相當多的記憶體，而且會讓讀寫磁碟所需的時間變長，除非磁碟上儲存了非常多重複的資料，例如：虛擬機的映像檔或者是使用者的備份資料，否則開啟去冗餘可" "能弊大於利。另一個需要考量的狀況是：啟用去冗餘功能之後再將其關閉，無法將磁碟上去冗餘的狀態立即逆轉，必須等到下次修改了之前被去冗餘的資料，變更的區塊才會" "再被複製一份。" #. (itstool) path: answer/para -#: book.translate.xml:3470 +#: book.translate.xml:3471 msgid "Deduplication can also lead to some unexpected situations. In particular, deleting files may become much slower." msgstr "去冗餘也可能會導致某些非預期的情況，特別是刪除檔案時可能會慢很多。" #. (itstool) path: question/para -#: book.translate.xml:3478 +#: book.translate.xml:3479 msgid "I cannot delete or create files on my ZFS pool. How can I fix this?" msgstr "在我建立的 ZFS pool 中無法刪除和新增檔案，應該怎麼修復？" #. (itstool) path: answer/para -#: book.translate.xml:3483 +#: book.translate.xml:3484 msgid "" "This could happen because the pool is 100% full. ZFS requires space on the disk to write transaction metadata. To restore the pool to a usable state, " "truncate the file to delete:" msgstr "" "這很有可能是該 pool 的空間使用率已達 100% 滿了，因 ZFS 需要儲存空間以將紀錄交易處理的輔助資料 (metadata) 寫入，為了讓該 pool 回復至可用狀態，必須用檔案" "切除的方法 (truncate 命令) 刪除不重要的檔案：" #. (itstool) path: answer/screen -#: book.translate.xml:3488 +#: book.translate.xml:3489 #, no-wrap msgid "% truncate -s 0 unimportant-file" msgstr "% truncate -s 0 unimportant-file" #. (itstool) path: answer/para -#: book.translate.xml:3490 +#: book.translate.xml:3491 msgid "File truncation works because a new transaction is not started, new spare blocks are created instead." msgstr "因為檔案切除不需要建立交易處理紀錄，並能釋放出可使用的磁碟區塊。" #. (itstool) path: note/para -#: book.translate.xml:3494 +#: book.translate.xml:3495 msgid "On systems with additional ZFS dataset tuning, such as deduplication, the space may not be immediately available" msgstr "如果系統曾進行過額外的 ZFS dataset 調校，例如：去冗餘，釋放出來的空間也許不會立即可得。" #. (itstool) path: question/para -#: book.translate.xml:3503 +#: book.translate.xml:3504 msgid "Does ZFS support TRIM for Solid State Drives?" msgstr "ZFS 支援固態硬碟 (SSD) 的 TRIM 功能嗎？" #. (itstool) path: answer/para -#: book.translate.xml:3507 +#: book.translate.xml:3508 msgid "" "ZFS TRIM support was added to FreeBSD 10-CURRENT with revision r240868. ZFS TRIM support was added to all FreeBSD-STABLE " "branches in r252162 and r251419, respectively." msgstr "" "自 FreeBSD 10-CURRENT 修定 r240868 開始，就支援 ZFS TRIM。ZFS TRIM 的支援分別已在 r252162 和 " "r251419 的修訂，加進所有 FreeBSD-STABLE 分支。" #. (itstool) path: answer/para -#: book.translate.xml:3513 +#: book.translate.xml:3514 msgid "ZFS TRIM is enabled by default, and can be turned off by adding this line to /etc/sysctl.conf:" msgstr "ZFS TRIM 預設就已開啟，也可以將其關閉，只要加入一行設定到 /etc/sysctl.conf:" #. (itstool) path: answer/programlisting -#: book.translate.xml:3517 +#: book.translate.xml:3518 #, no-wrap msgid "vfs.zfs.trim.enabled=0" msgstr "vfs.zfs.trim.enabled=0" #. (itstool) path: note/para -#: book.translate.xml:3520 +#: book.translate.xml:3521 msgid "ZFS TRIM may not work with all configurations, such as a ZFS filesystem on a GELI-backed device." msgstr "ZFS TRIM 也可能某些設定中會無效，例如：在採用 GELI 裝置上的 ZFS 檔案系統。" #. (itstool) path: chapter/title -#: book.translate.xml:3529 +#: book.translate.xml:3530 msgid "System Administration" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3534 +#: book.translate.xml:3535 msgid "Where are the system start-up configuration files?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3539 +#: book.translate.xml:3540 msgid "" "The primary configuration file is /etc/defaults/rc.conf which is described in rc.conf5. System startup scripts such as /etc/rc and /etc/rc.d, " "which are described in rc8, include this file. Do not edit " "this file! Instead, to edit an entry in /etc/defaults/rc.conf, copy the line into /etc/rc.conf and " "change it there." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3550 +#: book.translate.xml:3551 msgid "For example, if to start named8, the included DNS server:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:3553 +#: book.translate.xml:3554 #, no-wrap msgid "# echo 'named_enable=\"YES\"' >> /etc/rc.conf" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3555 +#: book.translate.xml:3556 msgid "" "To start up local services, place shell scripts in the /usr/local/etc/rc.d directory. These shell scripts should be set " "executable, the default file mode is 555." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3564 +#: book.translate.xml:3565 msgid "How do I add a user easily?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3568 +#: book.translate.xml:3569 msgid "" "Use the adduser8 command, or the pw8 command for more complicated situations." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3571 +#: book.translate.xml:3572 msgid "" "To remove the user, use the rmuser8 command or, if necessary, " "pw8." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3578 +#: book.translate.xml:3579 msgid "Why do I keep getting messages like root: not found after editing /etc/crontab?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3584 +#: book.translate.xml:3585 msgid "" "This is normally caused by editing the system crontab. This is not the correct way to do things as the system crontab has a different format to the per-" "user crontabs. The system crontab has an extra field, specifying which user to run the command as. cron8 assumes this user is the first word of the command to execute. Since no such command exists, this " "error message is displayed." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3593 +#: book.translate.xml:3594 msgid "To delete the extra, incorrect crontab:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:3595 +#: book.translate.xml:3596 #, no-wrap msgid "# crontab -r" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3601 +#: book.translate.xml:3602 msgid "" "Why do I get the error, you are not in the correct group to su root when I try to su to root?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3607 +#: book.translate.xml:3608 msgid "" "This is a security feature. In order to su to root, or any other account with superuser " "privileges, the user account must be a member of the wheel group. If this feature were not there, anybody " "with an account on a system who also found out root's password would be able to gain superuser level access " "to the system." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3617 +#: book.translate.xml:3618 msgid "" "To allow someone to su to root, put them in the wheel group using pw:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:3622 +#: book.translate.xml:3623 #, no-wrap msgid "# pw groupmod wheel -m lisa" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3624 +#: book.translate.xml:3625 msgid "The above example will add user lisa to the group wheel." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3631 +#: book.translate.xml:3632 msgid "" "I made a mistake in rc.conf, or another startup file, and now I cannot edit it because the file system is read-only. What should I " "do?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3637 +#: book.translate.xml:3638 msgid "" "Restart the system using boot -s at the loader prompt to enter single-user mode. When prompted for a shell pathname, press " "Enter and run mount -urw / to re-mount the root file system in read/write mode. You may also need to run " "mount -a -t ufs to mount the file system where your favorite editor is defined. If that editor is on a network file system, either " "configure the network manually before mounting the network file systems, or use an editor which resides on a local file system, such as " "ed1." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3650 +#: book.translate.xml:3651 msgid "" "In order to use a full screen editor such as vi1 or emacs1, run export TERM=xterm so that these " "editors can load the correct data from the termcap5 database." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3656 +#: book.translate.xml:3657 msgid "" "After performing these steps, edit /etc/rc.conf to fix the syntax error. The error message displayed immediately after the kernel " "boot messages should indicate the number of the line in the file which is at fault." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3667 +#: book.translate.xml:3668 msgid "Why am I having trouble setting up my printer?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3671 +#: book.translate.xml:3672 msgid "" "See the Handbook entry on printing for troubleshooting " "tips." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3679 +#: book.translate.xml:3680 msgid "How can I correct the keyboard mappings for my system?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3684 +#: book.translate.xml:3685 msgid "" "Refer to the Handbook section on using localization, specifically the section on console setup." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3692 +#: book.translate.xml:3693 msgid "Why can I not get user quotas to work properly?" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:3698 +#: book.translate.xml:3699 msgid "" "It is possible that the kernel is not configured to use quotas. In this case, add the following line to the kernel configuration file and recompile the " "kernel:" msgstr "" #. (itstool) path: listitem/programlisting -#: book.translate.xml:3703 +#: book.translate.xml:3704 #, no-wrap msgid "options QUOTA" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:3705 +#: book.translate.xml:3706 msgid "" "Refer to the Handbook entry on quotas for full details." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:3710 +#: book.translate.xml:3711 msgid "Do not turn on quotas on /." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:3715 +#: book.translate.xml:3716 msgid "Put the quota file on the file system that the quotas are to be enforced on:" msgstr "" #. (itstool) path: row/entry -#: book.translate.xml:3722 +#: book.translate.xml:3723 msgid "File System" msgstr "" #. (itstool) path: row/entry -#: book.translate.xml:3724 +#: book.translate.xml:3725 msgid "Quota file" msgstr "" #. (itstool) path: row/entry -#: book.translate.xml:3730 +#: book.translate.xml:3731 msgid "/usr" msgstr "" #. (itstool) path: row/entry -#: book.translate.xml:3732 +#: book.translate.xml:3733 msgid "/usr/admin/quotas" msgstr "" #. (itstool) path: row/entry -#: book.translate.xml:3736 +#: book.translate.xml:3737 msgid "/home" msgstr "" #. (itstool) path: row/entry -#: book.translate.xml:3738 +#: book.translate.xml:3739 msgid "/home/admin/quotas" msgstr "" #. (itstool) path: row/entry -#: book.translate.xml:3742 book.translate.xml:3744 +#: book.translate.xml:3743 book.translate.xml:3745 msgid "…" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3756 +#: book.translate.xml:3757 msgid "Does FreeBSD support System V IPC primitives?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3760 +#: book.translate.xml:3761 msgid "" "Yes, FreeBSD supports System V-style IPC, including shared memory, messages and semaphores, in the GENERIC kernel. With a custom " "kernel, support may be loaded with the sysvshm.ko, sysvsem.ko and sysvmsg.ko kernel " "modules, or enabled in the custom kernel by adding the following lines to the kernel configuration file:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:3770 +#: book.translate.xml:3771 #, no-wrap msgid "" "options SYSVSHM # enable shared memory\n" "options SYSVSEM # enable for semaphores\n" "options SYSVMSG # enable for messaging" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3774 +#: book.translate.xml:3775 msgid "Recompile and install the kernel." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3780 +#: book.translate.xml:3781 msgid "What other mail-server software can I use instead of Sendmail?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3785 +#: book.translate.xml:3786 msgid "" "The Sendmail server is the default mail-server software for FreeBSD, " "but it can be replaced with another MTA installed from the Ports Collection. Available ports include mail/exim, mail/" "postfix, and mail/qmail. Search the mailing lists for discussions regarding the advantages and disadvantages of the " "available MTAs." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3799 +#: book.translate.xml:3800 msgid "I have forgotten the root password! What do I do?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3804 +#: book.translate.xml:3805 msgid "" "Do not panic! Restart the system, type boot -s at the Boot: prompt to enter single-user mode. At the question " "about the shell to use, hit Enter which will display a # prompt. Enter mount -urw / to remount the " "root file system read/write, then run mount -a to remount all the file systems. Run passwd root to change the " "root password then run exit1 to continue booting." msgstr "" #. (itstool) path: note/para -#: book.translate.xml:3817 +#: book.translate.xml:3818 msgid "" "If you are still prompted to give the root password when entering the single-user mode, it means that the " "console has been marked as insecure in /etc/ttys. In this case, it will be required to boot from a FreeBSD " "installation disk, choose the Live CD or Shell at the beginning of the install process and issue " "the commands mentioned above. Mount the specific partition in this case and then chroot to it. For example, replace mount -urw / " "with mount /dev/ada0p1 /mnt; chroot /mnt for a system on ada0p1." msgstr "" #. (itstool) path: note/para -#: book.translate.xml:3834 +#: book.translate.xml:3835 msgid "" "If the root partition cannot be mounted from single-user mode, it is possible that the partitions are encrypted and it is impossible to mount them " "without the access keys. For more information see the section about encrypted disks in the FreeBSD Handbook." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3845 +#: book.translate.xml:3846 msgid "How do I keep ControlAltDelete from rebooting the system?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3850 +#: book.translate.xml:3851 msgid "" "When using syscons4, the default console driver, build and install a " "new kernel with this line in the configuration file:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:3854 +#: book.translate.xml:3855 #, no-wrap msgid "options SC_DISABLE_REBOOT" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3856 +#: book.translate.xml:3857 msgid "" "This can also be done by setting the following sysctl8 which does " "not require a reboot or kernel recompile:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:3860 +#: book.translate.xml:3861 #, no-wrap msgid "# sysctl hw.syscons.kbd_reboot=0" msgstr "" #. (itstool) path: note/para -#: book.translate.xml:3863 +#: book.translate.xml:3864 msgid "" "The above two methods are exclusive: The sysctl8 does not exist if " "the kernel is compiled with SC_DISABLE_REBOOT." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3872 +#: book.translate.xml:3873 msgid "How do I reformat DOS text files to UNIX ones?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3877 +#: book.translate.xml:3878 msgid "Use this perl1 command:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:3879 +#: book.translate.xml:3880 #, no-wrap msgid "% perl -i.bak -npe 's/\\r\\n/\\n/g' file(s)" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3881 +#: book.translate.xml:3882 msgid "" "where file(s) is one or more files to process. The modification is done in-place, with the original file stored with a " ".bak extension." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3886 +#: book.translate.xml:3887 msgid "Alternatively, use tr1:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:3888 +#: book.translate.xml:3889 #, no-wrap msgid "% tr -d '\\r' < dos-text-file > unix-file" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3890 +#: book.translate.xml:3891 msgid "" "dos-text-file is the file containing DOS text while unix-file will contain the converted output. " "This can be quite a bit faster than using perl." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3896 +#: book.translate.xml:3897 msgid "" "Yet another way to reformat DOS text files is to use the converters/dosunix port from the Ports Collection. Consult its " "documentation about the details." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3905 +#: book.translate.xml:3906 msgid "How do I re-read /etc/rc.conf and re-start /etc/rc without a reboot?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3911 +#: book.translate.xml:3912 msgid "Go into single-user mode and then back to multi-user mode:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:3914 +#: book.translate.xml:3915 #, no-wrap msgid "" "# shutdown now\n" "# return\n" "# exit" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3922 +#: book.translate.xml:3923 msgid "" "I tried to update my system to the latest -STABLE, but got -BETAx, -RC or -PRERELEASE! What is going on?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3931 +#: book.translate.xml:3932 msgid "" "Short answer: it is just a name. RC stands for Release Candidate. It signifies that a release is imminent. In " "FreeBSD, -PRERELEASE is typically synonymous with the code freeze before a release. (For some releases, the -BETA label was used in the same way as -PRERELEASE.)" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3940 +#: book.translate.xml:3941 msgid "" "Long answer: FreeBSD derives its releases from one of two places. Major, dot-zero, releases, such as 9.0-RELEASE are branched from the head of the " "development stream, commonly referred to as -CURRENT. Minor releases, such as 6.3-RELEASE or 5.2-RELEASE, have been " "snapshots of the active -STABLE branch. Starting with 4.3-RELEASE, each release also now has its own branch which can " "be tracked by people requiring an extremely conservative rate of development (typically only security advisories)." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3951 +#: book.translate.xml:3952 msgid "" "When a release is about to be made, the branch from which it will be derived from has to undergo a certain process. Part of this process is a code " "freeze. When a code freeze is initiated, the name of the branch is changed to reflect that it is about to become a release. For example, if the branch " "used to be called 6.2-STABLE, its name will be changed to 6.3-PRERELEASE to signify the code freeze and signify that extra pre-release testing should " "be happening. Bug fixes can still be committed to be part of the release. When the source code is in shape for the release the name will be changed to " "6.3-RC to signify that a release is about to be made from it. Once in the RC stage, only the most critical bugs found can be fixed. Once the release " "(6.3-RELEASE in this example) and release branch have been made, the branch will be renamed to 6.3-STABLE." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3968 +#: book.translate.xml:3969 msgid "" "For more information on version numbers and the various Subversion branches, refer to the Release Engineering article." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:3976 +#: book.translate.xml:3977 msgid "" "I tried to install a new kernel, and the chflags1 failed. How do I " "get around this?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3981 +#: book.translate.xml:3982 msgid "Short answer: the security level is greater than 0. Reboot directly to single-user mode to install the kernel." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3985 +#: book.translate.xml:3986 msgid "Long answer: FreeBSD disallows changing system flags at security levels greater than 0. To check the current security level:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:3989 book.translate.xml:4018 +#: book.translate.xml:3990 book.translate.xml:4019 #, no-wrap msgid "# sysctl kern.securelevel" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:3991 +#: book.translate.xml:3992 msgid "" "The security level cannot be lowered in multi-user mode, so boot to single-user mode to install the kernel, or change the security level in /" "etc/rc.conf then reboot. See the init8 manual page for " "details on securelevel, and see /etc/defaults/rc.conf and the rc.conf5 manual page for more information on rc.conf." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4005 +#: book.translate.xml:4006 msgid "I cannot change the time on my system by more than one second! How do I get around this?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4010 +#: book.translate.xml:4011 msgid "Short answer: the system is at a security level greater than 1. Reboot directly to single-user mode to change the date." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4014 +#: book.translate.xml:4015 msgid "Long answer: FreeBSD disallows changing the time by more that one second at security levels greater than 1. To check the security level:" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4020 +#: book.translate.xml:4021 msgid "" "The security level cannot be lowered in multi-user mode. Either boot to single-user mode to change the date or change the security level in /" "etc/rc.conf and reboot. See the init8 manual page for " "details on securelevel, and see /etc/defaults/rc.conf and the rc.conf5 manual page for more information on rc.conf." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4034 +#: book.translate.xml:4035 msgid "Why is rpc.statd using 256 MB of memory?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4039 +#: book.translate.xml:4040 msgid "" "No, there is no memory leak, and it is not using 256 MB of memory. For convenience, rpc.statd maps an obscene amount of memory into " "its address space. There is nothing terribly wrong with this from a technical standpoint; it just throws off things like " "top1 and ps1." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4046 +#: book.translate.xml:4047 msgid "" "rpc.statd8 maps its status file (resident on /var) into its address space; to save worrying about remapping the status file later when it needs to grow, it maps the status file with a " "generous size. This is very evident from the source code, where one can see that the length argument to mmap2 is 0x10000000, or one sixteenth of the address space on an IA32, or exactly " "256 MB." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4059 +#: book.translate.xml:4060 msgid "Why can I not unset the schg file flag?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4064 +#: book.translate.xml:4065 msgid "" "The system is running at securelevel greater than 0. Lower the securelevel and try again. For more information, see the " "FAQ entry on securelevel and the init8 " "manual page." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4074 +#: book.translate.xml:4075 msgid "What is vnlru?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4078 +#: book.translate.xml:4079 msgid "" "vnlru flushes and frees vnodes when the system hits the kern.maxvnodes limit. This kernel thread sits mostly " "idle, and only activates when there is a huge amount of RAM and users are accessing tens of thousands of tiny files." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4088 +#: book.translate.xml:4089 msgid "What do the various memory states displayed by top mean?" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:4096 +#: book.translate.xml:4097 msgid "Active: pages recently statistically used." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:4101 +#: book.translate.xml:4102 msgid "Inactive: pages recently statistically unused." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:4106 +#: book.translate.xml:4107 msgid "" "Cache: (most often) pages that have percolated from inactive to a status where they maintain their data, but can often be " "immediately reused (either with their old association, or reused with a new association). There can be certain immediate transitions from " "active to cache state if the page is known to be clean (unmodified), but that transition is a matter of policy, " "depending upon the algorithm choice of the VM system maintainer." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:4119 +#: book.translate.xml:4120 msgid "" "Free: pages without data content, and can be immediately used in certain circumstances where cache pages might be ineligible. Free " "pages can be reused at interrupt or process state." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:4127 +#: book.translate.xml:4128 msgid "Wired: pages that are fixed into memory, usually for kernel purposes, but also sometimes for special use in processes." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4133 +#: book.translate.xml:4134 msgid "" "Pages are most often written to disk (sort of a VM sync) when they are in the inactive state, but active pages can also be synced. This depends upon " "the CPU tracking of the modified bit being available, and in certain situations there can be an advantage for a block of VM pages to be synced, whether " "they are active or inactive. In most common cases, it is best to think of the inactive queue to be a queue of relatively unused pages that might or " "might not be in the process of being written to disk. Cached pages are already synced, not mapped, but available for immediate process use with their " "old association or with a new association. Free pages are available at interrupt level, but cached or free pages can be used at process state for " "reuse. Cache pages are not adequately locked to be available at interrupt level." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4150 +#: book.translate.xml:4151 msgid "There are some other flags (e.g., busy flag or busy count) that might modify some of the described rules." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4158 +#: book.translate.xml:4159 msgid "How much free memory is available?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4163 +#: book.translate.xml:4164 msgid "" "There are a couple of kinds of free memory. One kind is the amount of memory immediately available without paging anything else out. " "That is approximately the size of cache queue + size of free queue (with a derating factor, depending upon system tuning). Another kind of free " "memory is the total amount of VM space. That can be complex, but is dependent upon the amount of swap space and memory. " "Other kinds of free memory descriptions are also possible, but it is relatively useless to define these, but rather it is important to " "make sure that the paging rate is kept low, and to avoid running out of swap space." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4181 +#: book.translate.xml:4182 msgid "What is /var/empty?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4185 +#: book.translate.xml:4186 msgid "" "/var/empty is a directory that the sshd8 " "program uses when performing privilege separation. The /var/empty directory is empty, owned by root and has the schg flag set. This directory should not be deleted." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4196 +#: book.translate.xml:4197 msgid "I just changed /etc/newsyslog.conf. How can I check if it does what I expect?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4202 +#: book.translate.xml:4203 msgid "To see what newsyslog8 will do, use the following:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:4205 +#: book.translate.xml:4206 #, no-wrap msgid "% newsyslog -nrvv" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4211 +#: book.translate.xml:4212 msgid "My time is wrong, how can I change the timezone?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4216 +#: book.translate.xml:4217 msgid "Use tzsetup8." msgstr "" #. (itstool) path: chapter/title -#: book.translate.xml:4223 +#: book.translate.xml:4224 msgid "The X Window System and Virtual Consoles" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4228 +#: book.translate.xml:4229 msgid "What is the X Window System?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4232 +#: book.translate.xml:4233 msgid "" "The X Window System (commonly X11) is the most widely available windowing system capable of running on UNIX or UNIX like systems, including FreeBSD. The X.Org Foundation administers the X protocol standards, with the current reference implementation, version 11 release 7.7, so references are often shortened to X11." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4242 +#: book.translate.xml:4243 msgid "" "Many implementations are available for different architectures and operating systems. An implementation of the server-side code is properly known as an " "X server." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4251 +#: book.translate.xml:4252 msgid "I want to run Xorg, how do I go about it?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4255 +#: book.translate.xml:4256 msgid "To install Xorg do one of the following:" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4257 +#: book.translate.xml:4258 msgid "Use the x11/xorg meta-port, which builds and installs every Xorg component." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4261 +#: book.translate.xml:4262 msgid "Use x11/xorg-minimal, which builds and installs only the necessary Xorg components." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4264 +#: book.translate.xml:4265 msgid "Install Xorg from FreeBSD packages:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:4266 +#: book.translate.xml:4267 #, no-wrap msgid "# pkg install xorg" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4268 +#: book.translate.xml:4269 msgid "" "After the installation of Xorg, follow the instructions from the X11 Configuration section of the FreeBSD Handbook." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4277 +#: book.translate.xml:4278 msgid "" "I tried to run X, but I get a No devices detected. error when I type startx. What do I " "do now?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4283 +#: book.translate.xml:4284 msgid "" "The system is probably running at a raised securelevel. It is not possible to start X at a raised securelevel " "because X requires write access to io4. For more information, see at " "the init8 manual page." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4289 +#: book.translate.xml:4290 msgid "" "There are two solutions to the problem: set the securelevel back down to zero or run xdm1 (or an alternative display manager) at boot time before the " "securelevel is raised." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4295 +#: book.translate.xml:4296 msgid "" "See for more information about running xdm1 at boot time." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4302 +#: book.translate.xml:4303 msgid "Why does my mouse not work with X?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4306 +#: book.translate.xml:4307 msgid "" "When using syscons4, the default console driver, FreeBSD can be " "configured to support a mouse pointer on each virtual screen. To avoid conflicting with X, syscons4 supports a virtual device called /dev/sysmouse. All mouse events received " "from the real mouse device are written to the sysmouse4 device via " "moused8. To use the mouse on one or more virtual consoles, " "and use X, see and set up moused8." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4317 +#: book.translate.xml:4318 msgid "Then edit /etc/X11/xorg.conf and make sure the following lines exist:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:4320 +#: book.translate.xml:4321 #, no-wrap msgid "" "Section \"InputDevice\"\n" " Option \"Protocol\" \"SysMouse\"\n" " Option \"Device\" \"/dev/sysmouse\"\n" "....." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4325 +#: book.translate.xml:4326 msgid "" "Starting with Xorg version 7.4, the InputDevice sections in xorg.conf are ignored in favor of autodetected " "devices. To restore the old behavior, add the following line to the ServerLayout or ServerFlags section:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:4332 +#: book.translate.xml:4333 #, no-wrap msgid "Option \"AutoAddDevices\" \"false\"" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4334 +#: book.translate.xml:4335 msgid "" "Some people prefer to use /dev/mouse under X. To make this work, /dev/mouse should be linked to /" "dev/sysmouse (see sysmouse4) by adding the following line " "to /etc/devfs.conf (see devfs.conf5):" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:4342 +#: book.translate.xml:4343 #, no-wrap msgid "link sysmouse mouse" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4344 +#: book.translate.xml:4345 msgid "" "This link can be created by restarting devfs5 " "with the following command (as root):" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:4347 +#: book.translate.xml:4348 #, no-wrap msgid "# service devfs restart" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4353 +#: book.translate.xml:4354 msgid "My mouse has a fancy wheel. Can I use it in X?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4357 +#: book.translate.xml:4358 msgid "" "Yes, if X is configured for a 5 button mouse. To do this, add the lines Buttons 5 and ZAxisMapping 4 5 to the " "InputDevice section of /etc/X11/xorg.conf, as seen in this example:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:4364 +#: book.translate.xml:4365 #, no-wrap msgid "" "Section \"InputDevice\"\n" " Identifier \"Mouse1\"\n" " Driver \"mouse\"\n" " Option \"Protocol\" \"auto\"\n" " Option \"Device\" \"/dev/sysmouse\"\n" " Option \"Buttons\" \"5\"\n" " Option \"ZAxisMapping\" \"4 5\"\n" "EndSection" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4373 +#: book.translate.xml:4374 msgid "The mouse can be enabled in Emacsby adding these lines to ~/.emacs:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:4377 +#: book.translate.xml:4378 #, no-wrap msgid "" ";; wheel mouse\n" "(global-set-key [mouse-4] 'scroll-down)\n" "(global-set-key [mouse-5] 'scroll-up)" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4385 +#: book.translate.xml:4386 msgid "My laptop has a Synaptics touchpad. Can I use it in X?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4390 +#: book.translate.xml:4391 msgid "Yes, after configuring a few things to make it work." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4393 +#: book.translate.xml:4394 msgid "In order to use the Xorg synaptics driver, first remove moused_enable from rc.conf." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4397 +#: book.translate.xml:4398 msgid "To enable synaptics, add the following line to /boot/loader.conf:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:4400 +#: book.translate.xml:4401 #, no-wrap msgid "hw.psm.synaptics_support=\"1\"" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4402 +#: book.translate.xml:4403 msgid "Add the following to /etc/X11/xorg.conf:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:4405 +#: book.translate.xml:4406 #, no-wrap msgid "" "Section \"InputDevice\"\n" "Identifier \"Touchpad0\"\n" "Driver \"synaptics\"\n" "Option \"Protocol\" \"psm\"\n" "Option \"Device\" \"/dev/psm0\"\n" "EndSection" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4412 +#: book.translate.xml:4413 msgid "And be sure to add the following into the ServerLayout section:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:4415 +#: book.translate.xml:4416 #, no-wrap msgid "InputDevice \"Touchpad0\" \"SendCoreEvents\"" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4421 +#: book.translate.xml:4422 msgid "How do I use remote X displays?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4425 +#: book.translate.xml:4426 msgid "For security reasons, the default setting is to not allow a machine to remotely open a window." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4428 +#: book.translate.xml:4429 msgid "To enable this feature, start X with the optional argument:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:4432 +#: book.translate.xml:4433 #, no-wrap msgid "% startx -listen_tcp" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4438 +#: book.translate.xml:4439 msgid "What is a virtual console and how do I make more?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4443 +#: book.translate.xml:4444 msgid "" "Virtual consoles provide several simultaneous sessions on the same machine without doing anything complicated like setting up a network or running X." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4448 +#: book.translate.xml:4449 msgid "" "When the system starts, it will display a login prompt on the monitor after displaying all the boot messages. Type in your login name and password to " "start working on the first virtual console." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4454 +#: book.translate.xml:4455 msgid "" "To start another session, perhaps to look at documentation for a program or to read mail while waiting for an FTP transfer to finish, hold down " "Alt and press F2. This will display the login prompt for the second virtual console. To go back to the original " "session, press AltF1." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4464 +#: book.translate.xml:4465 msgid "" "The default FreeBSD installation has eight virtual consoles enabled. AltF1, " "AltF2, AltF3, and so on will switch between these virtual consoles." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4471 +#: book.translate.xml:4472 msgid "" "To enable more of virtual consoles, edit /etc/ttys (see ttys5) and add entries for ttyv8 to ttyvc, after the comment on Virtual terminals:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:4477 +#: book.translate.xml:4478 #, no-wrap msgid "" "# Edit the existing entry for ttyv8 in /etc/ttys and change\n" "# \"off\" to \"on\".\n" "ttyv8 \"/usr/libexec/getty Pc\" xterm on secure\n" "ttyv9 \"/usr/libexec/getty Pc\" xterm on secure\n" "ttyva \"/usr/libexec/getty Pc\" xterm on secure\n" "ttyvb \"/usr/libexec/getty Pc\" xterm on secure" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4484 +#: book.translate.xml:4485 msgid "" "The more virtual terminals, the more resources that are used. This can be problematic on systems with 8 MB RAM or less. Consider changing " "secure to insecure." msgstr "" #. (itstool) path: important/para -#: book.translate.xml:4491 +#: book.translate.xml:4492 msgid "" "In order to run an X server, at least one virtual terminal must be left to off for it to use. This means that only eleven of the Alt-" "function keys can be used as virtual consoles so that one is left for the X server." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4498 +#: book.translate.xml:4499 msgid "For example, to run X and eleven virtual consoles, the setting for virtual terminal 12 should be:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:4501 +#: book.translate.xml:4502 #, no-wrap msgid "ttyvb \"/usr/libexec/getty Pc\" xterm off secure" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4503 +#: book.translate.xml:4504 msgid "The easiest way to activate the virtual consoles is to reboot." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4510 +#: book.translate.xml:4511 msgid "How do I access the virtual consoles from X?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4514 +#: book.translate.xml:4515 msgid "" "Use CtrlAltFn to switch back to a " "virtual console. Press CtrlAltF1 to return to the first " "virtual console." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4518 +#: book.translate.xml:4519 msgid "" "Once at a text console, use AltFn to move between " "them." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4522 +#: book.translate.xml:4523 msgid "" "To return to the X session, switch to the virtual console running X. If X was started from the command line using startx, the X " "session will attach to the next unused virtual console, not the text console from which it was invoked. For eight active virtual terminals, X will run " "on the ninth, so use AltF9." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4534 +#: book.translate.xml:4535 msgid "How do I start XDM on boot?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4539 +#: book.translate.xml:4540 msgid "" "There are two schools of thought on how to start xdm1. One school starts xdm from /etc/ttys (see ttys5) using the supplied example, while the other runs xdm from rc.local (see rc8) or from an X script in " "/usr/local/etc/rc.d. Both are equally valid, and one may work in situations where the other does not. In both cases the result is " "the same: X will pop up a graphical login prompt." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4551 +#: book.translate.xml:4552 msgid "" "The ttys5 method has the advantage of documenting which vty X will " "start on and passing the responsibility of restarting the X server on logout to init8. The rc8 method makes it easy to " "kill xdm if there is a problem starting the X server." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4558 +#: book.translate.xml:4559 msgid "" "If loaded from rc8, xdm should be started without " "any arguments. xdm must start after getty8 runs, or else getty and xdm will conflict, locking out the console. The best way around this is to " "have the script sleep 10 seconds or so then launch xdm." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4567 +#: book.translate.xml:4568 msgid "" "When starting xdm from /etc/ttys, there still is a chance of conflict between xdm and " "getty8. One way to avoid this is to add the vt " "number in /usr/local/lib/X11/xdm/Xservers:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:4574 +#: book.translate.xml:4575 #, no-wrap msgid ":0 local /usr/local/bin/X vt4" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4576 +#: book.translate.xml:4577 msgid "" "The above example will direct the X server to run in /dev/ttyv3. Note the number is offset by one. The X server counts the vty " "from one, whereas the FreeBSD kernel numbers the vty from zero." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4585 +#: book.translate.xml:4586 msgid "Why do I get Couldn't open console when I run xconsole?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4591 +#: book.translate.xml:4592 msgid "" "When X is started with startx, the permissions on /dev/console will not get changed, resulting in things like xterm -C and xconsole not working." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4598 +#: book.translate.xml:4599 msgid "" "This is because of the way console permissions are set by default. On a multi-user system, one does not necessarily want just any user to be able to " "write on the system console. For users who are logging directly onto a machine with a VTY, the fbtab5 file exists to solve such problems." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4605 +#: book.translate.xml:4606 msgid "" "In a nutshell, make sure an uncommented line of the form is in /etc/fbtab (see fbtab5):" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:4609 +#: book.translate.xml:4610 #, no-wrap msgid "/dev/ttyv0 0600 /dev/console" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4611 +#: book.translate.xml:4612 msgid "It will ensure that whomever logs in on /dev/ttyv0 will own the console." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4619 +#: book.translate.xml:4620 msgid "Why does my PS/2 mouse misbehave under X?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4623 +#: book.translate.xml:4624 msgid "" "The mouse and the mouse driver may have become out of synchronization. In rare cases, the driver may also erroneously report synchronization errors:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:4627 +#: book.translate.xml:4628 #, no-wrap msgid "psmintr: out of sync (xxxx != yyyy)" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4629 +#: book.translate.xml:4630 msgid "" "If this happens, disable the synchronization check code by setting the driver flags for the PS/2 mouse driver to 0x100. This can be " "easiest achieved by adding hint.psm.0.flags=\"0x100\" to /boot/loader.conf and rebooting." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4640 +#: book.translate.xml:4641 msgid "How do I reverse the mouse buttons?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4644 +#: book.translate.xml:4645 msgid "" "Type xmodmap -e \"pointer = 3 2 1\". Add this command to ~/.xinitrc or ~/.xsession to make " "it happen automatically." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4654 +#: book.translate.xml:4655 msgid "How do I install a splash screen and where do I find them?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4659 +#: book.translate.xml:4660 msgid "" "The detailed answer for this question can be found in the Boot Time Splash Screens section of the FreeBSD Handbook." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4668 +#: book.translate.xml:4669 msgid "Can I use the Windows keys on my keyboard in X?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4673 +#: book.translate.xml:4674 msgid "" "Yes. Use xmodmap1 to define which functions the " "keys should perform." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4676 +#: book.translate.xml:4677 msgid "Assuming all Windows keyboards are standard, the keycodes for these three keys are the following:" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:4682 +#: book.translate.xml:4683 msgid "115 — Windows key, between the left-hand Ctrl and Alt keys" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:4689 +#: book.translate.xml:4690 msgid "116 — Windows key, to the right of AltGr" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:4695 +#: book.translate.xml:4696 msgid "117 — Menu, to the left of the right-hand Ctrl" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4701 +#: book.translate.xml:4702 msgid "To have the left Windows key print a comma, try this." msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:4704 +#: book.translate.xml:4705 #, no-wrap msgid "# xmodmap -e \"keycode 115 = comma\"" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4706 +#: book.translate.xml:4707 msgid "" "To have the Windows key-mappings enabled automatically every time X is started, either put the xmodmap commands in " "~/.xinitrc or, preferably, create a ~/.xmodmaprc and include the xmodmap options, one per " "line, then add the following line to ~/.xinitrc:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:4715 +#: book.translate.xml:4716 #, no-wrap msgid "xmodmap $HOME/.xmodmaprc" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4717 +#: book.translate.xml:4718 msgid "" "For example, to map the 3 keys to be F13, F14, and F15, respectively. This would make it easy to map " "them to useful functions within applications or the window manager." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4723 +#: book.translate.xml:4724 msgid "To do this, put the following in ~/.xmodmaprc." msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:4726 +#: book.translate.xml:4727 #, no-wrap msgid "" "keycode 115 = F13\n" "keycode 116 = F14\n" "keycode 117 = F15" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4730 +#: book.translate.xml:4731 msgid "" "For the x11-wm/fvwm2 desktop manager, one could map the keys so that F13 iconifies or de-iconifies the window the " "cursor is in, F14 brings the window the cursor is in to the front or, if it is already at the front, pushes it to the back, and " "F15 pops up the main Workplace menu even if the cursor is not on the desktop, which is useful when no part of the desktop is visible." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4741 +#: book.translate.xml:4742 msgid "The following entries in ~/.fvwmrc implement the aforementioned setup:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:4745 +#: book.translate.xml:4746 #, no-wrap msgid "" "Key F13 FTIWS A Iconify\n" "Key F14 FTIWS A RaiseLower\n" "Key F15 A A Menu Workplace Nop" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4753 +#: book.translate.xml:4754 msgid "How can I get 3D hardware acceleration for OpenGL?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4758 +#: book.translate.xml:4759 msgid "" "The availability of 3D acceleration depends on the version of Xorg and the type of video chip. For an nVidia chip, use the binary drivers provided for " "FreeBSD by installing one of the following ports:" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4764 +#: book.translate.xml:4765 msgid "The latest versions of nVidia cards are supported by the x11/nvidia-driver port." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4768 +#: book.translate.xml:4769 msgid "Older drivers are available as x11/nvidia-driver-###" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4771 +#: book.translate.xml:4772 msgid "" "nVidia provides detailed information on which card is supported by which driver on their web site: http://www.nvidia.com/object/IO_32667.html." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4774 +#: book.translate.xml:4775 msgid "For Matrox G200/G400, check the x11-drivers/xf86-video-mga port." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4778 +#: book.translate.xml:4779 msgid "" "For ATI Rage 128 and Radeon see ati4, r1284 and radeon4." msgstr "" #. (itstool) path: chapter/title -#: book.translate.xml:4786 +#: book.translate.xml:4787 msgid "Networking" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4791 +#: book.translate.xml:4792 msgid "Where can I get information on diskless booting?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4796 +#: book.translate.xml:4797 msgid "" "Diskless booting means that the FreeBSD box is booted over a network, and reads the necessary files from a server instead of its hard " "disk. For full details, see the Handbook entry on " "diskless booting." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4806 +#: book.translate.xml:4807 msgid "Can a FreeBSD box be used as a dedicated network router?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4811 +#: book.translate.xml:4812 msgid "" "Yes. Refer to the Handbook entry on advanced " "networking, specifically the section on routing " "and gateways." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4819 +#: book.translate.xml:4820 msgid "Can I connect my Windows box to the Internet via FreeBSD?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4824 +#: book.translate.xml:4825 msgid "" "Typically, people who ask this question have two PCs at home, one with FreeBSD and one with some version of Windows the idea is to use the FreeBSD box to connect to the Internet and then be able to access the Internet from the Windows box through the FreeBSD box. This is really just a special case of the previous question and works perfectly well." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4832 +#: book.translate.xml:4833 msgid "" "Dialup users must use and set gateway_enable to YES in /etc/rc.conf. " "For more information, refer to ppp8 or the Handbook entry on user PPP." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4839 +#: book.translate.xml:4840 msgid "" "If the connection to the Internet is over Ethernet, use natd8. A " "tutorial can be found in the natd " "section of the Handbook." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4847 +#: book.translate.xml:4848 msgid "Does FreeBSD support PPP?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4851 +#: book.translate.xml:4852 msgid "" "Yes. ppp8 provides support for both incoming and outgoing " "connections." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4854 +#: book.translate.xml:4855 msgid "" "For more information on how to use this, refer to the Handbook chapter on PPP." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4862 +#: book.translate.xml:4863 msgid "Does FreeBSD support NAT or Masquerading?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4866 +#: book.translate.xml:4867 msgid "" "Yes. For instructions on how to use NAT over a PPP connection, see the Handbook entry on PPP. To use NAT over some other sort of network connection, look at the natd section of the Handbook." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4877 +#: book.translate.xml:4878 msgid "How can I set up Ethernet aliases?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4881 +#: book.translate.xml:4882 msgid "If the alias is on the same subnet as an address already configured on the interface, add netmask 0xffffffff to this command:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:4886 +#: book.translate.xml:4887 #, no-wrap msgid "# ifconfig ed0 alias 192.0.2.2 netmask 0xffffffff" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4888 +#: book.translate.xml:4889 msgid "Otherwise, specify the network address and netmask as usual:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:4891 +#: book.translate.xml:4892 #, no-wrap msgid "# ifconfig ed0 alias 172.16.141.5 netmask 0xffffff00" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4893 +#: book.translate.xml:4894 msgid "" "More information can be found in the FreeBSD Handbook." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4899 +#: book.translate.xml:4900 msgid "Why can I not NFS-mount from a Linux box?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4903 +#: book.translate.xml:4904 msgid "" "Some versions of the Linux NFS code only accept mount requests from a privileged port; try to issue the " "following command:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:4907 +#: book.translate.xml:4908 #, no-wrap msgid "# mount -o -P linuxbox:/blah /mnt" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4913 +#: book.translate.xml:4914 msgid "" "Why does mountd keep telling me it can't change attributes and that I have a bad exports list on my FreeBSD NFS server?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4920 +#: book.translate.xml:4921 msgid "" "The most frequent problem is not understanding the correct format of /etc/exports. Review exports5 and the NFS entry in the Handbook, especially the section on configuring NFS." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4930 +#: book.translate.xml:4931 msgid "How do I enable IP multicast support?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4934 +#: book.translate.xml:4935 msgid "" "Install the net/mrouted package or port and add mrouted_enable=\"YES\" to /etc/rc.conf start " "this service at boot time." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4944 +#: book.translate.xml:4945 msgid "Why do I have to use the FQDN for hosts on my site?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4949 +#: book.translate.xml:4950 msgid "See the answer in the FreeBSD Handbook." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4955 +#: book.translate.xml:4956 msgid "Why do I get an error, Permission denied, for all networking operations?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4961 +#: book.translate.xml:4962 msgid "" "If the kernel is compiled with the IPFIREWALL option, be aware that the default policy is to deny all packets that are not " "explicitly allowed." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4966 +#: book.translate.xml:4967 msgid "" "If the firewall is unintentionally misconfigured, restore network operability by typing the following as root:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:4970 +#: book.translate.xml:4971 #, no-wrap msgid "# ipfw add 65534 allow all from any to any" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4972 +#: book.translate.xml:4973 msgid "Consider setting firewall_type=\"open\" in /etc/rc.conf." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4976 +#: book.translate.xml:4977 msgid "" "For further information on configuring this firewall, see the Handbook chapter." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:4984 +#: book.translate.xml:4985 msgid "Why is my ipfw fwd rule to redirect a service to another machine not working?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4990 +#: book.translate.xml:4991 msgid "" "Possibly because network address translation (NAT) is needed instead of just forwarding packets. A fwd rule only forwards packets, it " "does not actually change the data inside the packet. Consider this rule:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:4996 +#: book.translate.xml:4997 #, no-wrap msgid "01000 fwd 10.0.0.1 from any to foo 21" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:4998 +#: book.translate.xml:4999 msgid "" "When a packet with a destination address of foo arrives at the machine with this rule, the packet is forwarded to " "10.0.0.1, but it still has the destination address of foo. The destination address of the packet " "is not changed to 10.0.0.1. Most machines would probably drop a packet that they receive with a destination address that is " "not their own. Therefore, using a fwd rule does not often work the way the user expects. This behavior is a feature and not a bug." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5012 +#: book.translate.xml:5013 msgid "" "See the FAQ about redirecting services, the natd8 manual, or one of the several port redirecting utilities in the Ports Collection for a correct way to do this." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5021 +#: book.translate.xml:5022 msgid "How can I redirect service requests from one machine to another?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5026 +#: book.translate.xml:5027 msgid "" "FTP and other service requests can be redirected with the sysutils/socket package or port. Replace the entry for the service in " "/etc/inetd.conf to call socket, as seen in this example for ftpd:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:5033 +#: book.translate.xml:5034 #, no-wrap msgid "ftp stream tcp nowait nobody /usr/local/bin/socket socket ftp.example.com ftp" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5035 +#: book.translate.xml:5036 msgid "where ftp.example.com and ftp are the host and port to redirect to, respectively." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5043 +#: book.translate.xml:5044 msgid "Where can I get a bandwidth management tool?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5047 +#: book.translate.xml:5048 msgid "" "There are three bandwidth management tools available for FreeBSD. dummynet4 is integrated into FreeBSD as part of ipfw4. ALTQ has been integrated into FreeBSD as part of " "pf4. Bandwidth Manager from Emerging Technologies is a commercial product." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5058 +#: book.translate.xml:5059 msgid "Why do I get /dev/bpf0: device not configured?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5063 +#: book.translate.xml:5064 msgid "" "The running application requires the Berkeley Packet Filter (bpf4), " "but it was removed from a custom kernel. Add this to the kernel config file and build a new kernel:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:5068 +#: book.translate.xml:5069 #, no-wrap msgid "device bpf # Berkeley Packet Filter" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5074 +#: book.translate.xml:5075 msgid "" "How do I mount a disk from a Windows machine that is on my network, like smbmount in Linux?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5079 +#: book.translate.xml:5080 msgid "" "Use the SMBFS toolset. It includes a set of kernel modifications and a set of userland programs. The programs and " "information are available as mount_smbfs8 in the base system." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5089 +#: book.translate.xml:5090 msgid "What are these messages about: Limiting icmp/open port/closed port response in my log files?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5095 +#: book.translate.xml:5096 msgid "" "This kernel message indicates that some activity is provoking it to send a large amount of ICMP or TCP reset (RST) responses. ICMP responses are often " "generated as a result of attempted connections to unused UDP ports. TCP resets are generated as a result of attempted connections to unopened TCP " "ports. Among others, these are the kinds of activities which may cause these messages:" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:5106 +#: book.translate.xml:5107 msgid "Brute-force denial of service (DoS) attacks (as opposed to single-packet attacks which exploit a specific vulnerability)." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:5112 +#: book.translate.xml:5113 msgid "Port scans which attempt to connect to a large number of ports (as opposed to only trying a few well-known ports)." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5118 +#: book.translate.xml:5119 msgid "" "The first number in the message indicates how many packets the kernel would have sent if the limit was not in place, and the second indicates the " "limit. This limit is controlled using net.inet.icmp.icmplim. This example sets the limit to 300 packets per " "second:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:5126 +#: book.translate.xml:5127 #, no-wrap msgid "# sysctl net.inet.icmp.icmplim=300" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5128 +#: book.translate.xml:5129 msgid "To disable these messages without disabling response limiting, use net.inet.icmp.icmplim_output to disable the output:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:5134 +#: book.translate.xml:5135 #, no-wrap msgid "# sysctl net.inet.icmp.icmplim_output=0" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5136 +#: book.translate.xml:5137 msgid "" "Finally, to disable response limiting completely, set net.inet.icmp.icmplim to 0. Disabling response limiting is " "discouraged for the reasons listed above." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5145 +#: book.translate.xml:5146 msgid "What are these arp: unknown hardware address format error messages?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5150 +#: book.translate.xml:5151 msgid "" "This means that some device on the local Ethernet is using a MAC address in a format that FreeBSD does not recognize. This is probably caused by " "someone experimenting with an Ethernet card somewhere else on the network. This is most commonly seen on cable modem networks. It is harmless, and " "should not affect the performance of the FreeBSD system." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5162 +#: book.translate.xml:5163 msgid "" "Why do I keep seeing messages like: 192.168.0.10 is on fxp1 but got reply from 00:15:17:67:cf:82 on rl0, and how do I disable it?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5169 +#: book.translate.xml:5170 msgid "" "Because a packet is coming from outside the network unexpectedly. To disable them, set net.link.ether.inet.log_arp_wrong_iface to " "0." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5178 +#: book.translate.xml:5179 msgid "How do I compile an IPv6 only kernel?" msgstr "" #. (itstool) path: para/screen -#: book.translate.xml:5184 +#: book.translate.xml:5185 #, no-wrap msgid "" "include GENERIC\n" "ident GENERIC-IPV6ONLY\n" "makeoptions MKMODULESENV+=\"WITHOUT_INET_SUPPORT=\"\n" "nooptions INET\n" "nodevice gre" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5182 +#: book.translate.xml:5183 msgid "Configure your kernel with these settings: <_:screen-1/>" msgstr "" #. (itstool) path: chapter/title -#: book.translate.xml:5195 +#: book.translate.xml:5196 msgid "Security" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5200 +#: book.translate.xml:5201 msgid "What is a sandbox?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5203 +#: book.translate.xml:5204 msgid "Sandbox is a security term. It can mean two things:" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:5208 +#: book.translate.xml:5209 msgid "" "A process which is placed inside a set of virtual walls that are designed to prevent someone who breaks into the process from being able to break into " "the wider system." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:5213 +#: book.translate.xml:5214 msgid "" "The process is only able to run inside the walls. Since nothing the process does in regards to executing code is supposed to be able to breach the " "walls, a detailed audit of its code is not needed in order to be able to say certain things about its security." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:5220 +#: book.translate.xml:5221 msgid "" "The walls might be a user ID, for example. This is the definition used in the security7 and named8 man pages." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:5224 +#: book.translate.xml:5225 msgid "" "Take the ntalk service, for example (see inetd8). " "This service used to run as user ID root. Now it runs as user ID tty. The tty user is a sandbox designed to make it more difficult for someone who has successfully " "hacked into the system via ntalk from being able to hack beyond that user ID." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:5235 +#: book.translate.xml:5236 msgid "" "A process which is placed inside a simulation of the machine. It means that someone who is able to break into the process may believe that he can break " "into the wider machine but is, in fact, only breaking into a simulation of that machine and not modifying any real data." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:5242 +#: book.translate.xml:5243 msgid "" "The most common way to accomplish this is to build a simulated environment in a subdirectory and then run the processes in that directory chrooted so " "that / for that process is this directory, not the real / of the system)." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:5249 +#: book.translate.xml:5250 msgid "" "Another common use is to mount an underlying file system read-only and then create a file system layer on top of it that gives a process a seemingly " "writeable view into that file system. The process may believe it is able to write to those files, but only the process sees the effects — other " "processes in the system do not, necessarily." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:5257 +#: book.translate.xml:5258 msgid "An attempt is made to make this sort of sandbox so transparent that the user (or hacker) does not realize that he is sitting in it." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5263 +#: book.translate.xml:5264 msgid "UNIX implements two core sandboxes. One is at the process level, and one is at the userid level." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5266 +#: book.translate.xml:5267 msgid "" "Every UNIX process is completely firewalled off from every other UNIX process. One process cannot modify the address space of another." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5270 +#: book.translate.xml:5271 msgid "" "A UNIX process is owned by a particular userid. If the user ID is not the root user, it serves to firewall the process off from processes owned by other users. The user ID is also used to firewall off on-disk " "data." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5280 +#: book.translate.xml:5281 msgid "What is securelevel?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5284 +#: book.translate.xml:5285 msgid "" "securelevel is a security mechanism implemented in the kernel. When the securelevel is positive, the kernel restricts certain tasks; " "not even the superuser (root) is allowed to do them. The securelevel mechanism limits the ability to:" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:5293 +#: book.translate.xml:5294 msgid "Unset certain file flags, such as schg (the system immutable flag)." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:5299 +#: book.translate.xml:5300 msgid "Write to kernel memory via /dev/mem and /dev/kmem." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:5305 +#: book.translate.xml:5306 msgid "Load kernel modules." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:5309 +#: book.translate.xml:5310 msgid "Alter firewall rules." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5313 +#: book.translate.xml:5314 msgid "To check the status of the securelevel on a running system:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:5316 +#: book.translate.xml:5317 #, no-wrap msgid "# sysctl -n kern.securelevel" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5318 +#: book.translate.xml:5319 msgid "The output contains the current value of the securelevel. If it is greater than 0, at least some of the securelevel's protections are enabled." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5323 +#: book.translate.xml:5324 msgid "" "The securelevel of a running system cannot be lowered as this would defeat its purpose. If a task requires that the securelevel be non-positive, change " "the kern_securelevel and kern_securelevel_enable variables in /etc/rc.conf and reboot." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5330 +#: book.translate.xml:5331 msgid "" "For more information on securelevel and the specific things all the levels do, consult init8." msgstr "" #. (itstool) path: warning/para -#: book.translate.xml:5334 +#: book.translate.xml:5335 msgid "Securelevel is not a silver bullet; it has many known deficiencies. More often than not, it provides a false sense of security." msgstr "" #. (itstool) path: warning/para -#: book.translate.xml:5338 +#: book.translate.xml:5339 msgid "" "One of its biggest problems is that in order for it to be at all effective, all files used in the boot process up until the securelevel is set must be " "protected. If an attacker can get the system to execute their code prior to the securelevel being set (which happens quite late in the boot process " "since some things the system must do at start-up cannot be done at an elevated securelevel), its protections are invalidated. While this task of " "protecting all files used in the boot process is not technically impossible, if it is achieved, system maintenance will become a nightmare since one " "would have to take the system down, at least to single-user mode, to modify a configuration file." msgstr "" #. (itstool) path: warning/para -#: book.translate.xml:5353 +#: book.translate.xml:5354 msgid "" "This point and others are often discussed on the mailing lists, particularly the FreeBSD security mailing list. Search the archives here for an " "extensive discussion. A more fine-grained mechanism is preferred." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5364 +#: book.translate.xml:5365 msgid "BIND9 (named) is listening on some high-numbered ports. What is going on?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5370 +#: book.translate.xml:5371 msgid "" "BIND uses a random high-numbered port for outgoing queries. Recent versions of it choose a new, random UDP port for each query. This may cause problems " "for some network configurations, especially if a firewall blocks incoming UDP packets on particular ports. To get past that firewall, try the " "avoid-v4-udp-ports and avoid-v6-udp-ports options to avoid selecting random port numbers within a blocked range." msgstr "" #. (itstool) path: warning/para -#: book.translate.xml:5382 +#: book.translate.xml:5383 msgid "" "If a port number (like 53) is specified via the query-source or query-source-v6 options in /usr/local/" "etc/namedb/named.conf, randomized port selection will not be used. It is strongly recommended that these options not be used to specify " "fixed port numbers." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5392 +#: book.translate.xml:5393 msgid "" "Congratulations, by the way. It is good practice to read sockstat1 " "output and notice odd things!" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5400 +#: book.translate.xml:5401 msgid "The Sendmail daemon is listening on port 587 as well as the standard port 25! What is going on?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5406 +#: book.translate.xml:5407 msgid "" "Recent versions of Sendmail support a mail submission feature that runs over port 587. This is not yet widely supported, but " "is growing in popularity." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5415 +#: book.translate.xml:5416 msgid "What is this UID 0 toor account? Have I been compromised?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5420 +#: book.translate.xml:5421 msgid "" "Do not worry. toor is an alternative superuser account, where toor is root spelled " "backwards. It is intended to be used with a non-standard shell so the default shell for root does not need " "to change. This is important as shells which are not part of the base distribution, but are instead installed from ports or packages, are installed in " "/usr/local/bin which, by default, resides on a different file system. If root's shell " "is located in /usr/local/bin and the file system containing /usr/local/bin) is not mounted, root will not be able to log in to fix a problem and will have to reboot into single-user mode in order to enter the path to " "a shell." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5437 +#: book.translate.xml:5438 msgid "" "Some people use toor for day-to-day root tasks with a non-" "standard shell, leaving root, with a standard shell, for single-user mode or emergencies. By default, a " "user cannot log in using toor as it does not have a password, so log in as root and set a password for toor before using it to login." msgstr "" #. (itstool) path: chapter/title -#: book.translate.xml:5451 +#: book.translate.xml:5452 msgid "PPP" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5456 +#: book.translate.xml:5457 msgid "I cannot make ppp8 work. What am I doing wrong?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5461 +#: book.translate.xml:5462 msgid "" "First, read ppp8 and the PPP section of the Handbook. To assist in troubleshooting, enable logging with the " "following command:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:5467 +#: book.translate.xml:5468 #, no-wrap msgid "set log Phase Chat Connect Carrier lcp ipcp ccp command" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5469 +#: book.translate.xml:5470 msgid "" "This command may be typed at the ppp8 command prompt or it may be " "entered at the start of the default section in /etc/ppp/ppp.conf. Make sure that /etc/syslog.conf contains the lines below and the file /var/log/ppp.log exists:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:5477 +#: book.translate.xml:5478 #, no-wrap msgid "" "!ppp\n" "*.* /var/log/ppp.log" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5480 +#: book.translate.xml:5481 msgid "A lot about what is going can be learned from the log file. Do not worry if it does not all make sense as it may make sense to someone else." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5488 +#: book.translate.xml:5489 msgid "Why does ppp8 hang when I run it?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5492 +#: book.translate.xml:5493 msgid "" "This is usually because the hostname will not resolve. The best way to fix this is to make sure that /etc/hosts is read first by " "the by ensuring that the hosts line is listed first in /etc/host.conf. Then, put an entry in /etc/" "hosts for the local machine. If there is no local network, change the localhost line:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:5501 +#: book.translate.xml:5502 #, no-wrap msgid "127.0.0.1 foo.example.com foo localhost" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5503 +#: book.translate.xml:5504 msgid "Otherwise, add another entry for the host. Consult the relevant manual pages for more details." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5506 +#: book.translate.xml:5507 msgid "When finished, verify that this command is successful: ping -c1 `hostname`." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5513 +#: book.translate.xml:5514 msgid "Why will ppp8 not dial in -auto mode?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5518 +#: book.translate.xml:5519 msgid "First, check that a default route exists. This command should display two entries:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:5521 +#: book.translate.xml:5522 #, no-wrap msgid "" "Destination Gateway Flags Refs Use Netif Expire\n" "default 10.0.0.2 UGSc 0 0 tun0\n" "10.0.0.2 10.0.0.1 UH 0 0 tun0" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5525 +#: book.translate.xml:5526 msgid "If a default route is not listed, make sure that the HISADDR line has been added to /etc/ppp/ppp.conf." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5530 +#: book.translate.xml:5531 msgid "" "Another reason for the default route line being missing is that a default route has been added to /etc/rc.conf and this line is " "missing from /etc/ppp/ppp.conf:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:5536 +#: book.translate.xml:5537 #, no-wrap msgid "delete ALL" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5538 +#: book.translate.xml:5539 msgid "" "If this is the case, go back to the Final System " "Configuration section of the Handbook." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5546 +#: book.translate.xml:5547 msgid "What does No route to host mean?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5551 +#: book.translate.xml:5552 msgid "This error is usually because the following section is missing in /etc/ppp/ppp.linkup:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:5555 +#: book.translate.xml:5556 #, no-wrap msgid "" "MYADDR:\n" " delete ALL\n" " add 0 0 HISADDR" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5559 +#: book.translate.xml:5560 msgid "" "This is only necessary for a dynamic IP address or when the address of the default gateway is unknown. When using interactive mode, the following can " "be typed in after entering packet mode. Packet mode is indicated by the capitalized PPP in the prompt:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:5566 +#: book.translate.xml:5567 #, no-wrap msgid "" "delete ALL\n" "add 0 0 HISADDR" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5569 +#: book.translate.xml:5570 msgid "" "Refer to the PPP and Dynamic IP addresses section of the Handbook for further details." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5577 +#: book.translate.xml:5578 msgid "Why does my connection drop after about 3 minutes?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5582 +#: book.translate.xml:5583 msgid "The default PPP timeout is 3 minutes. This can be adjusted with the following line:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:5585 +#: book.translate.xml:5586 #, no-wrap msgid "set timeout NNN" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5587 +#: book.translate.xml:5588 msgid "" "where NNN is the number of seconds of inactivity before the connection is closed. If NNN is zero, " "the connection is never closed due to a timeout. It is possible to put this command in ppp.conf, or to type it at the prompt in " "interactive mode. It is also possible to adjust it on the fly while the line is active by connecting to ppp's server socket " "using telnet1 or pppctl8. Refer to the ppp8 man page for further details." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5602 +#: book.translate.xml:5603 msgid "Why does my connection drop under heavy load?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5606 +#: book.translate.xml:5607 msgid "" "If Link Quality Reporting (LQR) is configured, it is possible that too many LQR packets are lost between the " "FreeBSD system and the peer. ppp8 deduces that the line must " "therefore be bad, and disconnects. LQR is disabled by default and can be enabled with the following line:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:5614 book.translate.xml:5940 +#: book.translate.xml:5615 book.translate.xml:5941 #, no-wrap msgid "enable lqr" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5620 +#: book.translate.xml:5621 msgid "Why does my connection drop after a random amount of time?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5625 +#: book.translate.xml:5626 msgid "" "Sometimes, on a noisy phone line or even on a line with call waiting enabled, the modem may hang up because it incorrectly thinks that it lost carrier." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5629 +#: book.translate.xml:5630 msgid "There is a setting on most modems for determining how tolerant it should be to temporary losses of carrier. Refer to the modem manual for details." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5637 +#: book.translate.xml:5638 msgid "Why does my connection hang after a random amount of time?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5642 +#: book.translate.xml:5643 msgid "Many people experience hung connections with no apparent explanation. The first thing to establish is which side of the link is hung." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5646 +#: book.translate.xml:5647 msgid "" "When using an external modem, try using ping8 to see if the " "TD light is flashing when data is transmitted. If it flashes but the RD light does not, the problem is with the " "remote end. If TD does not flash, the problem is local. With an internal modem, use the set server command in " "ppp.conf. When the hang occurs, connect to ppp8 " "using pppctl8. If the network connection suddenly revives due to the " "activity on the diagnostic socket, or if it will not connect but the set socket command succeeded at startup time, the problem is " "local. If it can connect but things are still hung, enable local logging with set log local async and use " "ping8 from another window or terminal to make use of the link. The " "async logging will show the data being transmitted and received on the link. If data is going out and not coming back, the problem is remote." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5668 +#: book.translate.xml:5669 msgid "Having established whether the problem is local or remote, there are now two possibilities:" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:5673 +#: book.translate.xml:5674 msgid "If the problem is remote, read on entry ." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:5677 +#: book.translate.xml:5678 msgid "If the problem is local, read on entry ." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5685 +#: book.translate.xml:5686 msgid "The remote end is not responding. What can I do?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5690 +#: book.translate.xml:5691 msgid "" "There is very little that can be done about this. Many ISPs will refuse to help users not running a Microsoft OS. Add enable lqr to /etc/ppp/ppp.conf, allowing ppp8 to detect the remote failure and hang up. This detection is relatively slow and therefore not " "that useful." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5698 +#: book.translate.xml:5699 msgid "First, try disabling all local compression by adding the following to the configuration:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:5701 +#: book.translate.xml:5702 #, no-wrap msgid "" "disable pred1 deflate deflate24 protocomp acfcomp shortseq vj\n" "deny pred1 deflate deflate24 protocomp acfcomp shortseq vj" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5704 +#: book.translate.xml:5705 msgid "" "Then reconnect to ensure that this makes no difference. If things improve or if the problem is solved completely, determine which setting makes the " "difference through trial and error. This is good information for the ISP, although it may make it apparent that it is not a Microsoft system." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5711 +#: book.translate.xml:5712 msgid "" "Before contacting the ISP, enable async logging locally and wait until the connection hangs again. This may use up quite a bit of disk space. The last " "data read from the port may be of interest. It is usually ASCII data, and may even describe the problem (Memory fault, " "Core dumped)." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5719 +#: book.translate.xml:5720 msgid "" "If the ISP is helpful, they should be able to enable logging on their end, then when the next link drop occurs, they may be able to tell why their side " "is having a problem." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5728 +#: book.translate.xml:5729 msgid "ppp8 has hung. What can I do?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5732 +#: book.translate.xml:5733 msgid "" "In this case, rebuild ppp8 with debugging information, and then use " "gdb1 to grab a stack trace from the ppp " "process that is stuck. To rebuild the ppp utility with debugging information, type:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:5739 +#: book.translate.xml:5740 #, no-wrap msgid "" "# cd /usr/src/usr.sbin/ppp\n" "# env DEBUG_FLAGS='-g' make clean\n" "# env DEBUG_FLAGS='-g' make install" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5743 +#: book.translate.xml:5744 msgid "" "Then, restart ppp and wait until it hangs again. When the debug build of ppp hangs, start " "gdb on the stuck process by typing:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:5749 +#: book.translate.xml:5750 #, no-wrap msgid "# gdb ppp `pgrep ppp`" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5751 +#: book.translate.xml:5752 msgid "" "At the gdb prompt, use the bt or where commands to get a stack trace. Save the output " "of the gdb session, and detach from the running process by typing quit." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5762 +#: book.translate.xml:5763 msgid "I keep seeing errors about magic being the same. What does it mean?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5767 +#: book.translate.xml:5768 msgid "" "Occasionally, just after connecting, there may be messages in the log that say Magic is same. Sometimes, these messages are " "harmless, and sometimes one side or the other exits. Most PPP implementations cannot survive this problem, and even if the link seems to come up, there " "will be repeated configure requests and configure acknowledgments in the log file until ppp8 eventually gives up and closes the connection." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5777 +#: book.translate.xml:5778 msgid "" "This normally happens on server machines with slow disks that are spawning a getty8 on the port, and executing ppp8 from a " "login script or program after login. There were reports of it happening consistently when using slirp. The reason is that in the time taken between " "getty8 exiting and ppp8 starting, the client-side ppp8 starts sending Line Control Protocol (LCP) packets. Because ECHO is still switched on for the port on the server, the client " "ppp8 sees these packets reflect back." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5788 +#: book.translate.xml:5789 msgid "" "One part of the LCP negotiation is to establish a magic number for each side of the link so that reflections can be detected. The " "protocol says that when the peer tries to negotiate the same magic number, a NAK should be sent and a new magic number should be chosen. During the " "period that the server port has ECHO turned on, the client ppp8 " "sends LCP packets, sees the same magic in the reflected packet and NAKs it. It also sees the NAK reflect (which also means " "ppp8 must change its magic). This produces a potentially enormous " "number of magic number changes, all of which are happily piling into the server's tty buffer. As soon as ppp8 starts on the server, it is flooded with magic number changes and almost immediately decides it " "has tried enough to negotiate LCP and gives up. Meanwhile, the client, who no longer sees the reflections, becomes happy just in time to see a hangup " "from the server." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5806 +#: book.translate.xml:5807 msgid "This can be avoided by allowing the peer to start negotiating with the following line in ppp.conf:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:5810 book.translate.xml:5885 +#: book.translate.xml:5811 book.translate.xml:5886 #, no-wrap msgid "set openmode passive" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5812 +#: book.translate.xml:5813 msgid "" "This tells ppp8 to wait for the server to initiate LCP negotiations. " "Some servers however may never initiate negotiations. In this case, try something like:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:5817 +#: book.translate.xml:5818 #, no-wrap msgid "set openmode active 3" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5819 +#: book.translate.xml:5820 msgid "" "This tells ppp8 to be passive for 3 seconds, and then to start " "sending LCP requests. If the peer starts sending requests during this period, ppp8 will immediately respond rather than waiting for the full 3 second period." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5829 +#: book.translate.xml:5830 msgid "LCP negotiations continue until the connection is closed. What is wrong?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5834 +#: book.translate.xml:5835 msgid "" "There is currently an implementation mis-feature in ppp8 where it " "does not associate LCP, CCP & IPCP responses with their original requests. As a result, if one PPP implementation is more than 6 seconds slower " "than the other side, the other side will send two additional LCP configuration requests. This is fatal." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5842 +#: book.translate.xml:5843 msgid "" "Consider two implementations, A and B. A starts sending LCP requests " "immediately after connecting and B takes 7 seconds to start. When B starts, A has sent 3 LCP REQs. We are assuming the line has ECHO switched off, otherwise we would see magic number problems as described in the " "previous section. B sends a REQ, then an ACK to the first of A's REQs. This results in A entering the OPENED state and sending and ACK (the first) back to B. In the meantime, " "B sends back two more ACKs in response to the two additional REQs sent by A before B started up. B then receives the first ACK from A and enters the OPENED " "state. A receives the second ACK from B and goes back to the REQ-SENT state, " "sending another (forth) REQ as per the RFC. It then receives the third ACK and enters the OPENED state. In the meantime, " "B receives the forth REQ from A, resulting in it reverting to the ACK-SENT state " "and sending another (second) REQ and (forth) ACK as per the RFC. A gets the REQ, goes into REQ-SENT and " "sends another REQ. It immediately receives the following ACK and enters OPENED." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5877 +#: book.translate.xml:5878 msgid "This goes on until one side figures out that they are getting nowhere and gives up." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5880 +#: book.translate.xml:5881 msgid "" "The best way to avoid this is to configure one side to be passive — that is, make one side wait for the other to start negotiating. " "This can be done with the following command:" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5887 +#: book.translate.xml:5888 msgid "" "Care should be taken with this option. This command can also be used to limit the amount of time that ppp8 waits for the peer to begin negotiations:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:5892 +#: book.translate.xml:5893 #, no-wrap msgid "set stopped N" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5894 +#: book.translate.xml:5895 msgid "" "Alternatively, the following command (where N is the number of seconds to wait before starting negotiations) can be used:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:5898 +#: book.translate.xml:5899 #, no-wrap msgid "set openmode active N" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5900 +#: book.translate.xml:5901 msgid "Check the manual page for details." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5906 +#: book.translate.xml:5907 msgid "Why does ppp8 lock up when I shell out to test it?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5911 +#: book.translate.xml:5912 msgid "" "When using shell or !, ppp8 " "executes a shell or the passed arguments. The ppp program will wait for the command to complete before continuing. Any " "attempt to use the PPP link while running the command will appear as a frozen link. This is because ppp8 is waiting for the command to complete." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5920 +#: book.translate.xml:5921 msgid "" "To execute commands like this, use !bg instead. This will execute the given command in the background, and " "ppp8 can continue to service the link." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5929 +#: book.translate.xml:5930 msgid "Why does ppp8 over a null-modem cable never exit?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5934 +#: book.translate.xml:5935 msgid "" "There is no way for ppp8 to automatically determine that a direct " "connection has been dropped. This is due to the lines that are used in a null-modem serial cable. When using this sort of connection, LQR should always " "be enabled with the following line:" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5942 +#: book.translate.xml:5943 msgid "LQR is accepted by default if negotiated by the peer." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:5949 +#: book.translate.xml:5950 msgid "" "Why does ppp8 dial for no reason in mode?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5954 +#: book.translate.xml:5955 msgid "" "If ppp8 is dialing unexpectedly, determine the cause, and set up " "dial filters to prevent such dialing." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5958 +#: book.translate.xml:5959 msgid "To determine the cause, use the following line:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:5960 +#: book.translate.xml:5961 #, no-wrap msgid "set log +tcp/ip" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5962 +#: book.translate.xml:5963 msgid "" "This will log all traffic through the connection. The next time the line comes up unexpectedly, the reason will be logged with a convenient timestamp " "next to it." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5967 +#: book.translate.xml:5968 msgid "" "Next, disable dialing under these circumstances. Usually, this sort of problem arises due to DNS lookups. To prevent DNS lookups from establishing a " "connection (this will not prevent ppp8 from " "passing the packets through an established connection), use the following:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:5974 +#: book.translate.xml:5975 #, no-wrap msgid "" "set dfilter 1 deny udp src eq 53\n" "set dfilter 2 deny udp dst eq 53\n" "set dfilter 3 permit 0/0 0/0" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5978 +#: book.translate.xml:5979 msgid "" "This is not always suitable, as it will effectively break demand-dial capabilities. Most programs will need a DNS lookup before doing any other network " "related things." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5983 +#: book.translate.xml:5984 msgid "" "In the DNS case, try to determine what is actually trying to resolve a host name. A lot of the time, Sendmail is the " "culprit. Make sure to configure Sendmail not to do any DNS lookups in its configuration file. See the section on using email with a dialup connection in the FreeBSD Handbook for " "details. You may also want to add the following line to .mc:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:5994 +#: book.translate.xml:5995 #, no-wrap msgid "define(`confDELIVERY_MODE', `d')dnl" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:5996 +#: book.translate.xml:5997 msgid "" "This will make Sendmail queue everything until the queue is run, usually, every 30 minutes, or until a sendmail -q is done, perhaps from /etc/ppp/ppp.linkup." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6006 +#: book.translate.xml:6007 msgid "What do these CCP errors mean?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6010 +#: book.translate.xml:6011 msgid "I keep seeing the following errors in my log file:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:6013 +#: book.translate.xml:6014 #, no-wrap msgid "" "CCP: CcpSendConfigReq\n" "CCP: Received Terminate Ack (1) state = Req-Sent (6)" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6016 +#: book.translate.xml:6017 msgid "" "This is because ppp8 is trying to negotiate Predictor1 compression, " "but the peer does not want to negotiate any compression at all. The messages are harmless, but can be silenced by disabling the compression:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:6022 +#: book.translate.xml:6023 #, no-wrap msgid "disable pred1" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6028 +#: book.translate.xml:6029 msgid "Why does ppp8 not log my connection speed?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6033 +#: book.translate.xml:6034 msgid "To log all lines of the modem conversation, enable the following:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:6037 +#: book.translate.xml:6038 #, no-wrap msgid "set log +connect" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6039 +#: book.translate.xml:6040 msgid "" "This will make ppp8 log everything up until the last requested " "expect string." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6042 +#: book.translate.xml:6043 msgid "" "To see the connect speed when using PAP or CHAP, make sure to configure ppp8 to expect the whole CONNECT line, using something like this:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:6048 +#: book.translate.xml:6049 #, no-wrap msgid "" "set dial \"ABORT BUSY ABORT NO\\\\sCARRIER TIMEOUT 4 \\\n" " \\\"\\\" ATZ OK-ATZ-OK ATDT\\\\T TIMEOUT 60 CONNECT \\\\c \\\\n\"" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6051 +#: book.translate.xml:6052 msgid "" "This gets the CONNECT, sends nothing, then expects a line-feed, forcing ppp8 to read the whole CONNECT response." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6059 +#: book.translate.xml:6060 msgid "" "Why does ppp8 ignore the \\ character in my chat " "script?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6064 +#: book.translate.xml:6065 msgid "" "The ppp utility parses each line in its configuration files so that it can interpret strings such as set phone " "\"123 456 789\" correctly and realize that the number is actually only one argument. To specify a \" character, escape it " "using a backslash (\\)." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6072 +#: book.translate.xml:6073 msgid "" "When the chat interpreter parses each argument, it re-interprets the argument to find any special escape sequences such as \\P or " "\\T. As a result of this double-parsing, remember to use the correct number of escapes." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6079 +#: book.translate.xml:6080 msgid "To actually send a \\ character, do something like:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:6083 +#: book.translate.xml:6084 #, no-wrap msgid "set dial \"\\\"\\\" ATZ OK-ATZ-OK AT\\\\\\\\X OK\"" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6085 book.translate.xml:6097 +#: book.translate.xml:6086 book.translate.xml:6098 msgid "It will result in the following sequence:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:6087 +#: book.translate.xml:6088 #, no-wrap msgid "" "ATZ\n" "OK\n" "AT\\X\n" "OK" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6092 +#: book.translate.xml:6093 msgid "Or:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:6094 +#: book.translate.xml:6095 #, no-wrap msgid "" "set phone 1234567\n" "set dial \"\\\"\\\" ATZ OK ATDT\\\\T\"" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:6099 +#: book.translate.xml:6100 #, no-wrap msgid "" "ATZ\n" "OK\n" "ATDT1234567" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6107 +#: book.translate.xml:6108 msgid "What are FCS errors?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6111 +#: book.translate.xml:6112 msgid "" "FCS stands for Frame Check Sequence. Each PPP packet has a checksum attached to ensure that the data being received is the data being sent. If the FCS " "of an incoming packet is incorrect, the packet is dropped and the HDLC FCS count is increased. The HDLC error values can be displayed using the " "show hdlc command." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6119 +#: book.translate.xml:6120 msgid "" "If the link is bad or if the serial driver is dropping packets, it will produce the occasional FCS error. This is not usually worth worrying about " "although it does slow down the compression protocols substantially." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6124 +#: book.translate.xml:6125 msgid "" "If the link freezes as soon as it connects and produces a large number of FCS errors, make sure the modem is not using software flow control (XON/" "XOFF). If the link must use software flow control, use set accmap 0x000a0000 to tell ppp8 to escape the ^Q and ^S characters." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6132 +#: book.translate.xml:6133 msgid "" "Another reason for too many FCS errors may be that the remote end has stopped talking PPP. In this case, enable async logging to determine if the incoming data is actually a login or shell prompt. If it is a shell prompt at the remote end, it is possible to " "terminate ppp8 without dropping the line by using close " "lcp followed by term) to reconnect to the shell on the remote machine." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6143 +#: book.translate.xml:6144 msgid "If nothing in the log file indicates why the link was terminated, ask the remote administrator or ISP why the session was terminated." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6152 +#: book.translate.xml:6153 msgid "None of this helps — I am desperate! What can I do?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6157 +#: book.translate.xml:6158 msgid "" "If all else fails, send the details of the error, the configuration files, how ppp8 is being started, the relevant parts of the log file, and the output of netstat -rn, before and after " "connecting, to the FreeBSD general questions mailing list." msgstr "" #. (itstool) path: chapter/title -#: book.translate.xml:6168 +#: book.translate.xml:6169 msgid "Serial Communications" msgstr "" #. (itstool) path: chapter/para -#: book.translate.xml:6170 +#: book.translate.xml:6171 msgid "" "This section answers common questions about serial communications with FreeBSD. PPP is covered in the Networking " "section." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6176 +#: book.translate.xml:6177 msgid "Which multi-port serial cards are supported by FreeBSD?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6181 +#: book.translate.xml:6182 msgid "" "There is a list of these in the Serial Communications " "chapter of the Handbook." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6184 +#: book.translate.xml:6185 msgid "Most multi-port PCI cards that are based on 16550 or clones are supported with no extra effort." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6187 +#: book.translate.xml:6188 msgid "Some unnamed clone cards have also been known to work, especially those that claim to be AST compatible." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6190 +#: book.translate.xml:6191 msgid "" "Check uart4 and sio4 to get more information on configuring such cards." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6197 +#: book.translate.xml:6198 msgid "How do I get the boot: prompt to show on the serial console?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6202 +#: book.translate.xml:6203 msgid "See this section of the Handbook." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6209 +#: book.translate.xml:6210 msgid "How do I tell if FreeBSD found my serial ports or modem cards?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6214 +#: book.translate.xml:6215 msgid "" "As the FreeBSD kernel boots, it will probe for the serial ports for which the kernel is configured. Either watch the boot messages closely or run this " "command after the system is up and running:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:6220 +#: book.translate.xml:6221 #, no-wrap msgid "" "% grep -E '^(sio|uart)[0-9]' < /var/run/dmesg.boot\n" "sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0\n" "sio0: type 16550A\n" "sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0\n" "sio1: type 16550A" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6226 +#: book.translate.xml:6227 msgid "" "This example shows two serial ports. The first is on IRQ4, port address 0x3f8, and has a 16550A-type UART chip. The second uses the " "same kind of chip but is on IRQ3 and is at port address 0x2f8. Internal modem cards are treated just like serial ports, except that " "they always have a modem attached to the port." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6236 +#: book.translate.xml:6237 msgid "" "The GENERIC kernel includes support for two serial ports using the same IRQ and port address settings in the above example. If " "these settings are not right for the system, or if there are more modem cards or serial ports than the kernel is configured for, reconfigure using the " "instructions in building a kernel for more details." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6249 +#: book.translate.xml:6250 msgid "How do I access the serial ports on FreeBSD?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6253 +#: book.translate.xml:6254 msgid "" "The third serial port, sio2, or COM3, is on /dev/cuad2 for dial-out devices, and on " "/dev/ttyd2 for dial-in devices. What is the difference between these two classes of devices?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6260 +#: book.translate.xml:6261 msgid "" "When opening /dev/ttydX in blocking mode, a process will wait for the corresponding cuadX device to become " "inactive, and then wait for the carrier detect line to go active. When the cuadX device is opened, it makes sure the serial port " "is not already in use by the ttydX device. If the port is available, it steals it from the ttydX device. " "Also, the cuadX device does not care about carrier detect. With this scheme and an auto-answer modem, remote users can log in and " "local users can still dial out with the same modem and the system will take care of all the conflicts." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6280 +#: book.translate.xml:6281 msgid "How do I enable support for a multi-port serial card?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6285 +#: book.translate.xml:6286 msgid "" "The section on kernel configuration provides information about configuring the kernel. For a multi-port serial card, place an " "sio4 line for each serial port on the card in the device.hints5 file. But place the IRQ specifiers on only one of " "the entries. All of the ports on the card should share one IRQ. For consistency, use the last serial port to specify the IRQ. Also, specify the " "following option in the kernel configuration file:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:6295 +#: book.translate.xml:6296 #, no-wrap msgid "options COM_MULTIPORT" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6297 +#: book.translate.xml:6298 msgid "The following /boot/device.hints example is for an AST 4-port serial card on IRQ 12:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:6301 +#: book.translate.xml:6302 #, no-wrap msgid "" "hint.sio.4.at=\"isa\"\n" "hint.sio.4.port=\"0x2a0\"\n" "hint.sio.4.flags=\"0x701\"\n" "hint.sio.5.at=\"isa\"\n" "hint.sio.5.port=\"0x2a8\"\n" "hint.sio.5.flags=\"0x701\"\n" "hint.sio.6.at=\"isa\"\n" "hint.sio.6.port=\"0x2b0\"\n" "hint.sio.6.flags=\"0x701\"\n" "hint.sio.7.at=\"isa\"\n" "hint.sio.7.port=\"0x2b8\"\n" "hint.sio.7.flags=\"0x701\"\n" "hint.sio.7.irq=\"12\"" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6315 +#: book.translate.xml:6316 msgid "" "The flags indicate that the master port has minor number 7 (0x700), and all the ports share an IRQ " "(0x001)." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6324 +#: book.translate.xml:6325 msgid "Can I set the default serial parameters for a port?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6329 +#: book.translate.xml:6330 msgid "" "See the Serial Communications section in " "the FreeBSD Handbook." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6337 +#: book.translate.xml:6338 msgid "How can I enable dialup logins on my modem?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6341 +#: book.translate.xml:6342 msgid "" "Refer to the section about Dial-in Services in the FreeBSD " "Handbook." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6348 +#: book.translate.xml:6349 msgid "How can I connect a dumb terminal to my FreeBSD box?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6353 +#: book.translate.xml:6354 msgid "" "This information is in the Terminals section of the FreeBSD " "Handbook." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6360 +#: book.translate.xml:6361 msgid "Why can I not run tip or cu?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6365 +#: book.translate.xml:6366 msgid "" "The built-in tip1 and cu1 utilities can only access the /var/spool/lock directory via user uucp and group dialer. Use the dialer group to control who has access to the modem or remote systems by adding user accounts to dialer." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6374 +#: book.translate.xml:6375 msgid "" "Alternatively, everyone can be configured to run tip1 and " "cu1 by typing:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:6377 +#: book.translate.xml:6378 #, no-wrap msgid "" "# chmod 4511 /usr/bin/cu\n" "# chmod 4511 /usr/bin/tip" msgstr "" #. (itstool) path: chapter/title -#: book.translate.xml:6385 +#: book.translate.xml:6386 msgid "Miscellaneous Questions" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6390 +#: book.translate.xml:6391 msgid "FreeBSD uses a lot of swap space even when the computer has free memory left. Why?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6395 +#: book.translate.xml:6396 msgid "" "FreeBSD will proactively move entirely idle, unused pages of main memory into swap in order to make more main memory available for active use. This " "heavy use of swap is balanced by using the extra free memory for caching." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6401 +#: book.translate.xml:6402 msgid "" "Note that while FreeBSD is proactive in this regard, it does not arbitrarily decide to swap pages when the system is truly idle. Thus, the system will " "not be all paged out after leaving it idle overnight." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6411 +#: book.translate.xml:6412 msgid "Why does top show very little free memory even when I have very few programs running?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6416 +#: book.translate.xml:6417 msgid "" "The simple answer is that free memory is wasted memory. Any memory that programs do not actively allocate is used within the FreeBSD kernel as disk " "cache. The values shown by top1 labeled as Inact " "and Laundry are cached data at different aging levels. This cached data means the system does not have to access a slow disk again " "for data it has accessed recently, thus increasing overall performance. In general, a low value shown for Free memory in " "top1 is good, provided it is not very low." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6433 +#: book.translate.xml:6434 msgid "Why will chmod not change the permissions on symlinks?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6438 +#: book.translate.xml:6439 msgid "" "Symlinks do not have permissions, and by default, chmod1 will follow " "symlinks to change the permissions on the source file, if possible. For the file, foo with a symlink named bar, this command will always succeed." msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:6445 +#: book.translate.xml:6446 #, no-wrap msgid "% chmod g-w bar" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6447 +#: book.translate.xml:6448 msgid "However, the permissions on bar will not have changed." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6450 +#: book.translate.xml:6451 msgid "" "When changing modes of the file hierarchies rooted in the files instead of the files themselves, use either or " "together with to make this work. See chmod1 and " "symlink7 for more information." msgstr "" #. (itstool) path: warning/para -#: book.translate.xml:6458 +#: book.translate.xml:6459 msgid "" " does a recursive chmod1. Be " "careful about specifying directories or symlinks to directories to chmod1. To change the permissions of a directory referenced by a symlink, use chmod1 without any options and follow the symlink with a trailing slash (/). For example, if foo is a symlink to directory bar, to change the permissions of foo (actually bar), do something like:" msgstr "" #. (itstool) path: warning/screen -#: book.translate.xml:6471 +#: book.translate.xml:6472 #, no-wrap msgid "% chmod 555 foo/" msgstr "" #. (itstool) path: warning/para -#: book.translate.xml:6473 +#: book.translate.xml:6474 msgid "" "With the trailing slash, chmod1 will follow the symlink, " "foo, to change the permissions of the directory, bar." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6483 +#: book.translate.xml:6484 msgid "Can I run DOS binaries under FreeBSD?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6487 +#: book.translate.xml:6488 msgid "Yes. A DOS emulation program, emulators/doscmd, is available in the FreeBSD Ports Collection." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6491 +#: book.translate.xml:6492 msgid "" "If doscmd will not suffice, emulators/pcemu emulates an 8088 and enough BIOS services to run many DOS " "text-mode applications. It requires the X Window System." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6497 +#: book.translate.xml:6498 msgid "" "The Ports Collection also has emulators/dosbox. The main focus of this application is emulating old DOS games using the local file " "system for files." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6506 +#: book.translate.xml:6507 msgid "What do I need to do to translate a FreeBSD document into my native language?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6511 +#: book.translate.xml:6512 msgid "" "See the Translation FAQ in the " "FreeBSD Documentation Project Primer." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6519 +#: book.translate.xml:6520 msgid "Why does my email to any address at FreeBSD.org bounce?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6524 +#: book.translate.xml:6525 msgid "" "The FreeBSD.org mail system implements some Postfix checks on incoming mail " "and rejects mail that is either from misconfigured relays or otherwise appears likely to be spam. Some of the specific requirements are:" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:6532 +#: book.translate.xml:6533 msgid "The IP address of the SMTP client must \"reverse-resolve\" to a forward confirmed hostname." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:6538 +#: book.translate.xml:6539 msgid "The fully-qualified hostname given in the SMTP conversation (either HELO or EHLO) must resolve to the IP address of the client." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6544 +#: book.translate.xml:6545 msgid "Other advice to help mail reach its destination include:" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:6549 +#: book.translate.xml:6550 msgid "Mail should be sent in plain text, and messages sent to mailing lists should generally be no more than 200KB in length." msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:6555 +#: book.translate.xml:6556 msgid "Avoid excessive cross posting. Choose one mailing list which seems most relevant and send it there." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6561 +#: book.translate.xml:6562 msgid "" "If you still have trouble with email infrastructure at FreeBSD.org, send a note with the details to " "postmaster@freebsd.org; Include a date/time interval so that logs may be reviewed — and note that we only keep one week's worth of mail " "logs. (Be sure to specify the time zone or offset from UTC.)" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6574 +#: book.translate.xml:6575 msgid "Where can I find a free FreeBSD account?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6578 +#: book.translate.xml:6579 msgid "" "While FreeBSD does not provide open access to any of their servers, others do provide open access UNIX " "systems. The charge varies and limited services may be available." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6583 +#: book.translate.xml:6584 msgid "" "Arbornet, Inc, also known as M-Net, has been providing open access to " "UNIX systems since 1983. Starting on an Altos running System III, the site switched to BSD/OS in 1991. In " "June of 2000, the site switched again to FreeBSD. M-Net can be accessed via telnet and " "SSH and provides basic access to the entire FreeBSD software suite. However, network access is limited to members and " "patrons who donate to the system, which is run as a non-profit organization. M-Net also provides an bulletin board system and " "interactive chat." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6601 +#: book.translate.xml:6602 msgid "What is the cute little red guy's name?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6605 +#: book.translate.xml:6606 msgid "" "He does not have one, and is just called the BSD daemon. If you insist upon using a name, call him beastie. Note that " "beastie is pronounced BSD." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6611 +#: book.translate.xml:6612 msgid "More about the BSD daemon is available on his home page." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6618 +#: book.translate.xml:6619 msgid "Can I use the BSD daemon image?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6622 +#: book.translate.xml:6623 msgid "" "Perhaps. The BSD daemon is copyrighted by Marshall Kirk McKusick. Check his Statement on the Use of the BSD Daemon Figure for detailed usage terms." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6627 +#: book.translate.xml:6628 msgid "" "In summary, the image can be used in a tasteful manner, for personal use, so long as appropriate credit is given. Before using the logo commercially, " "contact Kirk McKusick mckusick@FreeBSD.org for permission. More details are available on the BSD Daemon's home page." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6638 +#: book.translate.xml:6639 msgid "Do you have any BSD daemon images I could use?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6642 +#: book.translate.xml:6643 msgid "Xfig and eps drawings are available under /usr/share/examples/BSD_daemon/." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6649 +#: book.translate.xml:6650 msgid "I have seen an acronym or other term on the mailing lists and I do not understand what it means. Where should I look?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6655 +#: book.translate.xml:6656 msgid "Refer to the FreeBSD Glossary." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6662 +#: book.translate.xml:6663 msgid "Why should I care what color the bikeshed is?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6666 +#: book.translate.xml:6667 msgid "" "The really, really short answer is that you should not. The somewhat longer answer is that just because you are capable of building a bikeshed does not " "mean you should stop others from building one just because you do not like the color they plan to paint it. This is a metaphor indicating that you need " "not argue about every little feature just because you know enough to do so. Some people have commented that the amount of noise generated by a change " "is inversely proportional to the complexity of the change." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6677 +#: book.translate.xml:6678 msgid "" "The longer and more complete answer is that after a very long argument about whether sleep1 should take fractional second arguments, Poul-Henning Kamp phk@FreeBSD.org posted a long message entitled " "A bike shed (any color will do) on greener grass.... The appropriate portions of " "that message are quoted below." msgstr "" #. (itstool) path: blockquote/attribution -#: book.translate.xml:6686 +#: book.translate.xml:6687 msgid "" "Poul-Henning Kamp phk@FreeBSD.org on freebsd-hackers, October 2, 1999" msgstr "" #. (itstool) path: blockquote/para -#: book.translate.xml:6689 +#: book.translate.xml:6690 msgid "What is it about this bike shed? Some of you have asked me." msgstr "" #. (itstool) path: blockquote/para -#: book.translate.xml:6692 +#: book.translate.xml:6693 msgid "" "It is a long story, or rather it is an old story, but it is quite short actually. C. Northcote Parkinson wrote a book in the early 1960s, called " "Parkinson's Law, which contains a lot of insight into the dynamics of management." msgstr "" #. (itstool) path: blockquote/para -#: book.translate.xml:6698 +#: book.translate.xml:6699 msgid "[snip a bit of commentary on the book]" msgstr "" #. (itstool) path: blockquote/para -#: book.translate.xml:6701 +#: book.translate.xml:6702 msgid "In the specific example involving the bike shed, the other vital component is an atomic power-plant, I guess that illustrates the age of the book." msgstr "" #. (itstool) path: blockquote/para -#: book.translate.xml:6705 +#: book.translate.xml:6706 msgid "" "Parkinson shows how you can go into the board of directors and get approval for building a multi-million or even billion dollar atomic power plant, but " "if you want to build a bike shed you will be tangled up in endless discussions." msgstr "" #. (itstool) path: blockquote/para -#: book.translate.xml:6711 +#: book.translate.xml:6712 msgid "" "Parkinson explains that this is because an atomic plant is so vast, so expensive and so complicated that people cannot grasp it, and rather than try, " "they fall back on the assumption that somebody else checked all the details before it got this far. Richard P. Feynmann gives a couple of interesting, " "and very much to the point, examples relating to Los Alamos in his books." msgstr "" #. (itstool) path: blockquote/para -#: book.translate.xml:6720 +#: book.translate.xml:6721 msgid "" "A bike shed on the other hand. Anyone can build one of those over a weekend, and still have time to watch the game on TV. So no matter how well " "prepared, no matter how reasonable you are with your proposal, somebody will seize the chance to show that he is doing his job, that he is paying " "attention, that he is here." msgstr "" #. (itstool) path: blockquote/para -#: book.translate.xml:6728 +#: book.translate.xml:6729 msgid "" "In Denmark we call it setting your fingerprint. It is about personal pride and prestige, it is about being able to point somewhere and " "say There! I did that. It is a strong trait in politicians, but present in most people given the chance. Just think " "about footsteps in wet cement." msgstr "" #. (itstool) path: chapter/title -#: book.translate.xml:6742 +#: book.translate.xml:6743 msgid "The FreeBSD Funnies" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6747 +#: book.translate.xml:6748 msgid "How cool is FreeBSD?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6751 +#: book.translate.xml:6752 msgid "" "Q. Has anyone done any temperature testing while running FreeBSD? I know Linux runs cooler than DOS, but " "have never seen a mention of FreeBSD. It seems to run really hot." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6756 +#: book.translate.xml:6757 msgid "" "A. No, but we have done numerous taste tests on blindfolded volunteers who have also had 250 micrograms of LSD-25 administered beforehand. 35% of the " "volunteers said that FreeBSD tasted sort of orange, whereas Linux tasted like purple haze. Neither group " "mentioned any significant variances in temperature. We eventually had to throw the results of this survey out entirely anyway when we found that too " "many volunteers were wandering out of the room during the tests, thus skewing the results. We think most of the volunteers are at Apple now, working on " "their new scratch and sniff GUI. It is a funny old business we are in!" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6769 +#: book.translate.xml:6770 msgid "" "Seriously, FreeBSD uses the HLT (halt) instruction when the system is idle thus lowering its energy consumption and therefore the " "heat it generates. Also if you have ACPI (Advanced Configuration and Power Interface) configured, then FreeBSD can also put the CPU " "into a low power mode." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6780 +#: book.translate.xml:6781 msgid "Who is scratching in my memory banks??" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6784 +#: book.translate.xml:6785 msgid "" "Q. Is there anything odd that FreeBSD does when compiling the kernel which would cause the memory to make a scratchy sound? When " "compiling (and for a brief moment after recognizing the floppy drive upon startup, as well), a strange scratchy sound emanates from what appears to be " "the memory banks." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6791 +#: book.translate.xml:6792 msgid "" "A. Yes! You will see frequent references to daemons in the BSD documentation, and what most people do not know is that this refers to " "genuine, non-corporeal entities that now possess your computer. The scratchy sound coming from your memory is actually high-pitched whispering " "exchanged among the daemons as they best decide how to deal with various system administration tasks." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6800 +#: book.translate.xml:6801 msgid "" "If the noise gets to you, a good fdisk /mbr from DOS will get rid of them, but do not be surprised if they react adversely and try " "to stop you. In fact, if at any point during the exercise you hear the satanic voice of Bill Gates coming from the built-in speaker, take off running " "and do not ever look back! Freed from the counterbalancing influence of the BSD daemons, the twin demons of DOS and Windows are often able to re-assert total control over your machine to the eternal damnation of your soul. Now that you know, given a " "choice you would probably prefer to get used to the scratchy noises, no?" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6817 +#: book.translate.xml:6818 msgid "How many FreeBSD hackers does it take to change a lightbulb?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6822 +#: book.translate.xml:6823 msgid "One thousand, one hundred and sixty-nine:" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6824 +#: book.translate.xml:6825 msgid "Twenty-three to complain to -CURRENT about the lights being out;" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6827 +#: book.translate.xml:6828 msgid "Four to claim that it is a configuration problem, and that such matters really belong on -questions;" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6830 +#: book.translate.xml:6831 msgid "Three to submit PRs about it, one of which is misfiled under doc and consists only of it's dark;" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6834 +#: book.translate.xml:6835 msgid "One to commit an untested lightbulb which breaks buildworld, then back it out five minutes later;" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6837 +#: book.translate.xml:6838 msgid "Eight to flame the PR originators for not including patches in their PRs;" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6840 +#: book.translate.xml:6841 msgid "Five to complain about buildworld being broken;" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6842 +#: book.translate.xml:6843 msgid "Thirty-one to answer that it works for them, and they must have updated at a bad time;" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6845 +#: book.translate.xml:6846 msgid "One to post a patch for a new lightbulb to -hackers;" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6848 +#: book.translate.xml:6849 msgid "" "One to complain that he had patches for this three years ago, but when he sent them to -CURRENT they were just ignored, and he has had bad experiences " "with the PR system; besides, the proposed new lightbulb is non-reflexive;" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6854 +#: book.translate.xml:6855 msgid "" "Thirty-seven to scream that lightbulbs do not belong in the base system, that committers have no right to do things like this without consulting the " "Community, and WHAT IS -CORE DOING ABOUT IT!?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6859 +#: book.translate.xml:6860 msgid "Two hundred to complain about the color of the bicycle shed;" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6862 +#: book.translate.xml:6863 msgid "Three to point out that the patch breaks style9;" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6865 +#: book.translate.xml:6866 msgid "Seventeen to complain that the proposed new lightbulb is under GPL;" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6868 +#: book.translate.xml:6869 msgid "" "Five hundred and eighty-six to engage in a flame war about the comparative advantages of the GPL, the BSD license, the MIT license, the NPL, and the " "personal hygiene of unnamed FSF founders;" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6873 +#: book.translate.xml:6874 msgid "Seven to move various portions of the thread to -chat and -advocacy;" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6876 +#: book.translate.xml:6877 msgid "One to commit the suggested lightbulb, even though it shines dimmer than the old one;" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6879 +#: book.translate.xml:6880 msgid "Two to back it out with a furious flame of a commit message, arguing that FreeBSD is better off in the dark than with a dim lightbulb;" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6883 +#: book.translate.xml:6884 msgid "Forty-six to argue vociferously about the backing out of the dim lightbulb and demanding a statement from -core;" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6887 +#: book.translate.xml:6888 msgid "Eleven to request a smaller lightbulb so it will fit their Tamagotchi if we ever decide to port FreeBSD to that platform;" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6891 +#: book.translate.xml:6892 msgid "Seventy-three to complain about the SNR on -hackers and -chat and unsubscribe in protest;" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6894 +#: book.translate.xml:6895 msgid "" "Thirteen to post unsubscribe, How do I unsubscribe?, or Please remove me from the list, followed by the " "usual footer;" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6899 +#: book.translate.xml:6900 msgid "One to commit a working lightbulb while everybody is too busy flaming everybody else to notice;" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6902 +#: book.translate.xml:6903 msgid "" "Thirty-one to point out that the new lightbulb would shine 0.364% brighter if compiled with TenDRA (although it will have to be reshaped into a cube), " "and that FreeBSD should therefore switch to TenDRA instead of GCC;" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6907 +#: book.translate.xml:6908 msgid "One to complain that the new lightbulb lacks fairings;" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6910 +#: book.translate.xml:6911 msgid "Nine (including the PR originators) to ask what is MFC?;" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6913 +#: book.translate.xml:6914 msgid "Fifty-seven to complain about the lights being out two weeks after the bulb has been changed." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6916 +#: book.translate.xml:6917 msgid "Nik Clayton nik@FreeBSD.org adds:" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6918 +#: book.translate.xml:6919 msgid "I was laughing quite hard at this." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6921 +#: book.translate.xml:6922 msgid "And then I thought, Hang on, shouldn't there be '1 to document it.' in that list somewhere?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6925 +#: book.translate.xml:6926 msgid "And then I was enlightened :-)" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6928 +#: book.translate.xml:6929 msgid "" "Thomas Abthorpe tabthorpe@FreeBSD.org says: None, real FreeBSD hackers are not afraid " "of the dark!" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6936 +#: book.translate.xml:6937 msgid "Where does data written to /dev/null go?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6941 +#: book.translate.xml:6942 msgid "" "It goes into a special data sink in the CPU where it is converted to heat which is vented through the heatsink / fan assembly. This is why CPU cooling " "is increasingly important; as people get used to faster processors, they become careless with their data and more and more of it ends up in /" "dev/null, overheating their CPUs. If you delete /dev/null (which effectively disables the CPU data sink) your CPU may " "run cooler but your system will quickly become constipated with all that excess data and start to behave erratically. If you have a fast network " "connection you can cool down your CPU by reading data out of /dev/random and sending it off somewhere; however you run the risk of " "overheating your network connection and / or angering your ISP, as most of the data will end up getting converted to heat by their " "equipment, but they generally have good cooling, so if you do not overdo it you should be OK." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6961 +#: book.translate.xml:6962 msgid "Paul Robinson adds:" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6963 +#: book.translate.xml:6964 msgid "" "There are other methods. As every good sysadmin knows, it is part of standard practice to send data to the screen of interesting variety to keep all " "the pixies that make up your picture happy. Screen pixies (commonly mis-typed or re-named as pixels) are categorized by the type of hat " "they wear (red, green or blue) and will hide or appear (thereby showing the color of their hat) whenever they receive a little piece of food. Video " "cards turn data into pixie-food, and then send them to the pixies — the more expensive the card, the better the food, so the better behaved the pixies " "are. They also need constant stimulation — this is why screen savers exist." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6977 +#: book.translate.xml:6978 msgid "" "To take your suggestions further, you could just throw the random data to console, thereby letting the pixies consume it. This causes no heat to be " "produced at all, keeps the pixies happy and gets rid of your data quite quickly, even if it does make things look a bit messy on your screen." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:6984 +#: book.translate.xml:6985 msgid "" "Incidentally, as an ex-admin of a large ISP who experienced many problems attempting to maintain a stable temperature in a server room, I would " "strongly discourage people sending the data they do not want out to the network. The fairies who do the packet switching and routing get annoyed by it " "as well." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:6995 +#: book.translate.xml:6996 msgid "My colleague sits at the computer too much, how can I prank her?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:7000 +#: book.translate.xml:7001 msgid "Install games/sl and wait for her to mistype sl for ls." msgstr "" #. (itstool) path: chapter/title -#: book.translate.xml:7009 +#: book.translate.xml:7010 msgid "Advanced Topics" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:7014 +#: book.translate.xml:7015 msgid "How can I learn more about FreeBSD's internals?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:7018 +#: book.translate.xml:7019 msgid "See the FreeBSD Architecture Handbook." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:7021 +#: book.translate.xml:7022 msgid "Additionally, much general UNIX knowledge is directly applicable to FreeBSD." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:7028 +#: book.translate.xml:7029 msgid "How can I contribute to FreeBSD? What can I do to help?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:7033 +#: book.translate.xml:7034 #, fuzzy msgid "" "We accept all types of contributions: documentation, code, and even art. See the article on Contributing to FreeBSD for specific advice on how to do this." msgstr "" "然而，在您回報問題之前，請先閱讀 如何撰寫 FreeBSD 的問" "題回報單，這是一篇告訴你怎樣才能寫出一篇真正有用的問題回報單。" #. (itstool) path: answer/para -#: book.translate.xml:7038 +#: book.translate.xml:7039 msgid "And thanks for the thought!" msgstr "" #. (itstool) path: question/para -#: book.translate.xml:7044 +#: book.translate.xml:7045 msgid "What are snapshots and releases?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:7048 +#: book.translate.xml:7049 msgid "" "There are currently 2 active/semi-active branches in the FreeBSD Subversion Repository. " "(Earlier branches are only changed very rarely, which is why there are only 2 active branches of development):" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:7056 +#: book.translate.xml:7057 msgid "stable/11/ AKA 11-STABLE" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:7061 +#: book.translate.xml:7062 msgid "stable/12/ AKA 12-STABLE" msgstr "" #. (itstool) path: listitem/para -#: book.translate.xml:7066 +#: book.translate.xml:7067 msgid "head/ AKA -CURRENT AKA 12-CURRENT" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:7072 +#: book.translate.xml:7073 msgid "" "HEAD is not an actual branch tag. It is a symbolic constant for the current, non-branched development stream known as -" "CURRENT." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:7078 +#: book.translate.xml:7079 msgid "" "Right now, -CURRENT is the 13.X development stream; the 12-STABLE branch, " "stable/12/, forked off from -CURRENT in December 2018 and the 11-STABLE branch, " "stable/11/, forked off from -CURRENT in October 2016." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:7089 +#: book.translate.xml:7090 msgid "How can I make the most of the data I see when my kernel panics?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:7094 +#: book.translate.xml:7095 msgid "Here is typical kernel panic:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:7096 +#: book.translate.xml:7097 #, no-wrap msgid "" "Fatal trap 12: page fault while in kernel mode\n" "fault virtual address = 0x40\n" "fault code = supervisor read, page not present\n" "instruction pointer = 0x8:0xf014a7e5\n" "stack pointer = 0x10:0xf4ed6f24\n" "frame pointer = 0x10:0xf4ed6f28\n" "code segment = base 0x0, limit 0xfffff, type 0x1b\n" " = DPL 0, pres 1, def32 1, gran 1\n" "processor eflags = interrupt enabled, resume, IOPL = 0\n" "current process = 80 (mount)\n" "interrupt mask =\n" "trap number = 12\n" "panic: page fault" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:7110 +#: book.translate.xml:7111 msgid "" "This message is not enough. While the instruction pointer value is important, it is also configuration dependent as it varies depending on the kernel " "image. If it is a GENERIC kernel image from one of the snapshots, it is possible for somebody else to track down the offending " "function, but for a custom kernel, only you can tell us where the fault occurred." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:7119 +#: book.translate.xml:7120 msgid "To proceed:" msgstr "" #. (itstool) path: step/para -#: book.translate.xml:7123 +#: book.translate.xml:7124 msgid "" "Write down the instruction pointer value. Note that the 0x8: part at the beginning is not significant in this case: it is the " "0xf0xxxxxx part that we want." msgstr "" #. (itstool) path: step/para -#: book.translate.xml:7131 +#: book.translate.xml:7132 msgid "When the system reboots, do the following:" msgstr "" #. (itstool) path: step/screen -#: book.translate.xml:7133 +#: book.translate.xml:7134 #, no-wrap msgid "% nm -n kernel.that.caused.the.panic | grep f0xxxxxx" msgstr "" #. (itstool) path: step/para -#: book.translate.xml:7135 +#: book.translate.xml:7136 msgid "" "where f0xxxxxx is the instruction pointer value. The odds are you will not get an exact match since the symbols in the kernel symbol " "table are for the entry points of functions and the instruction pointer address will be somewhere inside a function, not at the start. If you do not " "get an exact match, omit the last digit from the instruction pointer value and try again:" msgstr "" #. (itstool) path: step/screen -#: book.translate.xml:7144 +#: book.translate.xml:7145 #, no-wrap msgid "% nm -n kernel.that.caused.the.panic | grep f0xxxxx" msgstr "" #. (itstool) path: step/para -#: book.translate.xml:7146 +#: book.translate.xml:7147 msgid "" "If that does not yield any results, chop off another digit. Repeat until there is some sort of output. The result will be a possible list of functions " "which caused the panic. This is a less than exact mechanism for tracking down the point of failure, but it is better than nothing." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:7155 +#: book.translate.xml:7156 msgid "" "However, the best way to track down the cause of a panic is by capturing a crash dump, then using kgdb1 to generate a stack trace on the crash dump." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:7160 +#: book.translate.xml:7161 msgid "In any case, the method is this:" msgstr "" #. (itstool) path: step/para -#: book.translate.xml:7164 +#: book.translate.xml:7165 msgid "Make sure that the following line is included in the kernel configuration file:" msgstr "" #. (itstool) path: step/programlisting -#: book.translate.xml:7167 +#: book.translate.xml:7168 #, no-wrap msgid "makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols" msgstr "" #. (itstool) path: step/para -#: book.translate.xml:7171 +#: book.translate.xml:7172 msgid "Change to the /usr/src directory:" msgstr "" #. (itstool) path: step/screen -#: book.translate.xml:7174 +#: book.translate.xml:7175 #, no-wrap msgid "# cd /usr/src" msgstr "" #. (itstool) path: step/para -#: book.translate.xml:7178 +#: book.translate.xml:7179 msgid "Compile the kernel:" msgstr "" #. (itstool) path: step/screen -#: book.translate.xml:7180 +#: book.translate.xml:7181 #, no-wrap msgid "# make buildkernel KERNCONF=MYKERNEL" msgstr "" #. (itstool) path: step/para -#: book.translate.xml:7184 +#: book.translate.xml:7185 msgid "Wait for make1 to finish compiling." msgstr "" #. (itstool) path: step/screen -#: book.translate.xml:7188 +#: book.translate.xml:7189 #, no-wrap msgid "# make installkernel KERNCONF=MYKERNEL" msgstr "" #. (itstool) path: step/para -#: book.translate.xml:7192 +#: book.translate.xml:7193 msgid "Reboot." msgstr "" #. (itstool) path: note/para -#: book.translate.xml:7197 +#: book.translate.xml:7198 msgid "If KERNCONF is not included, the GENERIC kernel will instead be built and installed." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:7202 +#: book.translate.xml:7203 msgid "" "The make1 process will have built two kernels. /usr/obj/" "usr/src/sys/MYKERNEL/kernel and /usr/obj/usr/src/sys/MYKERNEL/kernel.debug. kernel was installed " "as /boot/kernel/kernel, while kernel.debug can be used as the source of debugging symbols for " "kgdb1." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:7211 +#: book.translate.xml:7212 msgid "" "To capture a crash dump, edit /etc/rc.conf and set dumpdev to point to either the swap partition or " "AUTO. This will cause the rc8 scripts to use the " "dumpon8 command to enable crash dumps. This command can also be run " "manually. After a panic, the crash dump can be recovered using savecore8; if dumpdev is set in /etc/rc.conf, the rc8 scripts will run savecore8 automatically and put the crash dump in /var/crash." msgstr "" #. (itstool) path: note/para -#: book.translate.xml:7224 +#: book.translate.xml:7225 msgid "" "FreeBSD crash dumps are usually the same size as physical RAM. Therefore, make sure there is enough space in /var/crash to hold " "the dump. Alternatively, run savecore8 manually and have it recover " "the crash dump to another directory with more room. It is possible to limit the size of the crash dump by using options MAXMEM=N " "where N is the size of kernel's memory usage in KBs. For example, for 1 GB of RAM, limit the kernel's memory usage to " "128 MB, so that the crash dump size will be 128 MB instead of 1 GB." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:7239 +#: book.translate.xml:7240 msgid "Once the crash dump has been recovered , get a stack trace as follows:" msgstr "" #. (itstool) path: answer/screen -#: book.translate.xml:7242 +#: book.translate.xml:7243 #, no-wrap msgid "" "% kgdb /usr/obj/usr/src/sys/MYKERNEL/kernel.debug /var/crash/vmcore.0\n" "(kgdb) backtrace" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:7245 +#: book.translate.xml:7246 msgid "" "Note that there may be several screens worth of information. Ideally, use script1 to capture all of them. Using the unstripped kernel image with all the debug symbols should show the exact line of kernel source code " "where the panic occurred. The stack trace is usually read from the bottom up to trace the exact sequence of events that lead to the crash. " "kgdb1 can also be used to print out the contents of various " "variables or structures to examine the system state at the time of the crash." msgstr "" #. (itstool) path: tip/para -#: book.translate.xml:7257 +#: book.translate.xml:7258 msgid "" "If a second computer is available, kgdb1 can be configured to do " "remote debugging, including setting breakpoints and single-stepping through the kernel code." msgstr "" #. (itstool) path: note/para -#: book.translate.xml:7264 +#: book.translate.xml:7265 msgid "" "If DDB is enabled and the kernel drops into the debugger, a panic and a crash dump can be forced by typing panic " "at the ddb prompt. It may stop in the debugger again during the panic phase. If it does, type continue and it " "will finish the crash dump." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:7278 +#: book.translate.xml:7279 msgid "Why has dlsym() stopped working for ELF executables?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:7283 +#: book.translate.xml:7284 msgid "" "The ELF toolchain does not, by default, make the symbols defined in an executable visible to the dynamic linker. Consequently dlsym() searches on handles obtained from calls to dlopen(NULL, flags) will fail to find such symbols." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:7290 +#: book.translate.xml:7291 msgid "" "To search, using dlsym(), for symbols present in the main executable of a process, link the executable using the option to the ELF linker (ld1)." msgstr "" #. (itstool) path: question/para -#: book.translate.xml:7300 +#: book.translate.xml:7301 msgid "How can I increase or reduce the kernel address space on i386?" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:7305 +#: book.translate.xml:7306 msgid "" "By default, the kernel address space is 1 GB (2 GB for PAE) for i386. When running a network-intensive server or using ZFS, this will probably not be " "enough." msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:7311 +#: book.translate.xml:7312 msgid "Add the following line to the kernel configuration file to increase available space and rebuild the kernel:" msgstr "" #. (itstool) path: answer/programlisting -#: book.translate.xml:7315 +#: book.translate.xml:7316 #, no-wrap msgid "options KVA_PAGES=N" msgstr "" #. (itstool) path: answer/para -#: book.translate.xml:7317 +#: book.translate.xml:7318 msgid "" "To find the correct value of N, divide the desired address space size (in megabytes) by four. (For example, it is " "512 for 2 GB.)" msgstr "" #. (itstool) path: chapter/title -#: book.translate.xml:7327 +#: book.translate.xml:7328 msgid "Acknowledgments" msgstr "" #. (itstool) path: chapter/para -#: book.translate.xml:7329 +#: book.translate.xml:7330 msgid "" "This innocent little Frequently Asked Questions document has been written, rewritten, edited, folded, spindled, mutilated, eviscerated, contemplated, " "discombobulated, cogitated, regurgitated, rebuilt, castigated, and reinvigorated over the last decade, by a cast of hundreds if not thousands. " "Repeatedly." msgstr "" #. (itstool) path: chapter/para -#: book.translate.xml:7336 +#: book.translate.xml:7337 msgid "" "We wish to thank every one of the people responsible, and we encourage you to join them in making this FAQ even better." msgstr ""