Date: Wed, 16 Jan 2019 14:48:21 +0000 (UTC) From: Ruey-Cherng Yu <rcyu@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52768 - head/zh_TW.UTF-8/books/faq Message-ID: <201901161448.x0GEmLeb002689@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: rcyu Date: Wed Jan 16 14:48:21 2019 New Revision: 52768 URL: https://svnweb.freebsd.org/changeset/doc/52768 Log: - Traditional Chinese translation of FAQ chapter 9 Submitted by: Chih-Chang Hsieh <cch@kmu.edu.tw> Sponsored by: Kaohsiung Medical University Modified: head/zh_TW.UTF-8/books/faq/book.xml head/zh_TW.UTF-8/books/faq/zh_TW.po Modified: head/zh_TW.UTF-8/books/faq/book.xml ============================================================================== --- head/zh_TW.UTF-8/books/faq/book.xml Mon Jan 14 19:44:20 2019 (r52767) +++ head/zh_TW.UTF-8/books/faq/book.xml Wed Jan 16 14:48:21 2019 (r52768) @@ -1,27 +1,55 @@ <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN" "http://www.FreeBSD.org/XML/share/xml/freebsd50.dtd" [ <!ENTITY bibliography SYSTEM "../../../share/xml/bibliography.xml"> -<!ENTITY rel.numbranch "3"> +<!ENTITY rel.numbranch "2"> <!-- number of branches that follow in this list --><!ENTITY rel.head "<emphasis xmlns='http://docbook.org/ns/docbook'>12-CURRENT</emphasis>">; -<!ENTITY rel.head.relx "12.<replaceable xmlns='http://docbook.org/ns/docbook'>X</replaceable>">; +<!ENTITY rel.head.relx "13.<replaceable xmlns='http://docbook.org/ns/docbook'>X</replaceable>">; <!ENTITY rel.head.releng "<symbol xmlns='http://docbook.org/ns/docbook'>head/</symbol>">; -<!ENTITY rel.relx "11.<replaceable xmlns='http://docbook.org/ns/docbook'>X</replaceable>">; -<!ENTITY rel.stable "<emphasis xmlns='http://docbook.org/ns/docbook'>11-STABLE</emphasis>">; -<!ENTITY rel.releng "<symbol xmlns='http://docbook.org/ns/docbook'>stable/11/</symbol>">; -<!ENTITY rel.relengdate "April 2016"> -<!ENTITY rel2.relx "10.<replaceable xmlns='http://docbook.org/ns/docbook'>X</replaceable>">; -<!ENTITY rel2.stable "<emphasis xmlns='http://docbook.org/ns/docbook'>10-STABLE</emphasis>">; -<!ENTITY rel2.releng "<symbol xmlns='http://docbook.org/ns/docbook'>stable/10/</symbol>">; -<!ENTITY rel2.relengdate "August 2015"> +<!ENTITY rel.relx "12.<replaceable xmlns='http://docbook.org/ns/docbook'>X</replaceable>">; +<!ENTITY rel.stable "<emphasis xmlns='http://docbook.org/ns/docbook'>12-STABLE</emphasis>">; +<!ENTITY rel.releng "<symbol xmlns='http://docbook.org/ns/docbook'>stable/12/</symbol>">; +<!ENTITY rel.relengdate "December 2018"> +<!ENTITY rel2.relx "11.<replaceable xmlns='http://docbook.org/ns/docbook'>X</replaceable>">; +<!ENTITY rel2.stable "<emphasis xmlns='http://docbook.org/ns/docbook'>11-STABLE</emphasis>">; +<!ENTITY rel2.releng "<symbol xmlns='http://docbook.org/ns/docbook'>stable/11/</symbol>">; +<!ENTITY rel2.relengdate "October 2016"> ]> <book xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:its="http://www.w3.org/2005/11/its" version="5.0" xml:lang="zh_TW"> <info> - <title>FreeBSD 10.<replaceable>X</replaceable> and 11.<replaceable>X</replaceable> 常見問答集</title> + <title xml:lang="en">Frequently Asked Questions for FreeBSD + 11.<replaceable>X</replaceable> and 12.<replaceable>X</replaceable></title> <author><orgname>FreeBSD 文件計畫</orgname></author> - <copyright><year>1995</year> <year>1996</year> <year>1997</year> <year>1998</year> <year>1999</year> <year>2000</year> <year>2001</year> <year>2002</year> <year>2003</year> <year>2004</year> <year>2005</year> <year>2006</year> <year>2007</year> <year>2008</year> <year>2009</year> <year>2010</year> <year>2011</year> <year>2012</year> <year>2013</year> <year>2014</year> <year>2015</year> <year>2016</year> <year>2017</year> <holder>The FreeBSD Documentation Project</holder></copyright> + <copyright xml:lang="en"> + <year>1995</year> + <year>1996</year> + <year>1997</year> + <year>1998</year> + <year>1999</year> + <year>2000</year> + <year>2001</year> + <year>2002</year> + <year>2003</year> + <year>2004</year> + <year>2005</year> + <year>2006</year> + <year>2007</year> + <year>2008</year> + <year>2009</year> + <year>2010</year> + <year>2011</year> + <year>2012</year> + <year>2013</year> + <year>2014</year> + <year>2015</year> + <year>2016</year> + <year>2017</year> + <year>2018</year> + <holder>The FreeBSD Documentation Project</holder> + </copyright> + <legalnotice xml:id="legalnotice"> <title>版權所有</title> @@ -82,7 +110,12 @@ <releaseinfo xml:lang="en">$FreeBSD$</releaseinfo> <abstract> - <para>這份文件是 FreeBSD 10.<replaceable>X</replaceable> 和 11.<replaceable>X</replaceable> 常見問答集 ( <acronym>(FAQ)</acronym> )。我們盡可能地讓這份 <acronym>FAQ</acronym> 提供有用的資訊 ; 如果您有任何改善建議，請寄到 <link xlink:href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-doc">FreeBSD 文件計畫郵件論壇</link>。</para> + <para xml:lang="en">This is the Frequently Asked Questions + <acronym>(FAQ)</acronym> for FreeBSD versions + 12.<replaceable>X</replaceable> and 11.<replaceable>X</replaceable>. Every effort has been made to + make this <acronym>FAQ</acronym> as informative as possible; + if you have any suggestions as to how it may be improved, send + them to the <link xlink:href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-doc">FreeBSD documentation project mailing list</link>.</para> <para>The latest version of this document is always available from the <link xlink:href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/index.html">FreeBSD website</link>. </para> </abstract> @@ -192,7 +225,12 @@ </question> <answer> - <para>James Howard 寫了一篇關於不同計畫的差異和歷史淵源的好文章叫 <link xlink:href="http://www.freebsdworld.gr/freebsd/bsd-family-tree.html">The BSD Family Tree</link> 可以回答這個問題。雖然有些資訊有點過時，但是關於歷史淵源的部份仍是相當正確的。</para> + <para xml:lang="en">James Howard wrote a good explanation of the history + and differences between the various projects, called <link xlink:href="https://jameshoward.us/archive/the-bsd-family-tree/">The + BSD Family Tree</link> 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.</para> <para>時至今日，大部分的 BSD 家族仍是共用修補和程式碼的。這些 BSD 家族有著共同的祖先。</para> @@ -220,11 +258,27 @@ </question> <answer> - <para>在 FreeBSD 開發的任何時間點，都有多個平行的分支。11.<replaceable>X</replaceable> releases 是從 <emphasis>11-STABLE</emphasis> 分支而來，而 10.<replaceable>X</replaceable> releases 是從 <emphasis>10-STABLE</emphasis> 分支而來。</para> + <para xml:lang="en">At any point in the development of FreeBSD, there can be + multiple parallel branches. 12.<replaceable>X</replaceable> releases are made + from the <emphasis>12-STABLE</emphasis> branch, and 11.<replaceable>X</replaceable> releases are + made from the <emphasis>11-STABLE</emphasis> branch.</para> - <para>在 9.0 之前，10.<replaceable>X</replaceable> 系列仍屬 <emphasis>-STABLE</emphasis>分支。 然而從12.<replaceable>X</replaceable> 發行開始，10.<replaceable>X</replaceable> 將只著重在重大問題上(比如：漏洞修補、安全維護)以及所謂的 <quote>extended support</quote> 。</para> + <para xml:lang="en">Up until the release of 9.0, the 11.<replaceable>X</replaceable> series + was the one known as <emphasis>-STABLE</emphasis>. + However, as of 13.<replaceable>X</replaceable>, the 11.<replaceable>X</replaceable> branch + will be designated for an <quote>extended support</quote> + status and receive only fixes for major problems, such as + security-related fixes. + <!--There will be no more releases made from the + &rel2.stable; branch, and it is considered a + <quote>legacy</quote> branch and most current work will only + become a part of &rel.stable; and &rel2.stable;.--></para> - <para>於 2017年七月所發行的 <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/i386/11.1-RELEASE/">11.1</link>; 是目前最新的 <emphasis>11-STABLE</emphasis> 分支。 於 2017年十月所發行的 <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/10.4-RELEASE/">10.4</link>是目前最新 <emphasis>10-STABLE</emphasis> 分支。</para> + <para xml:lang="en">Version <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/i386/12.0-RELEASE/">12.0</link>; + is the latest release from the <emphasis>12-STABLE</emphasis> branch; it was + released in December 2018. Version <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/10.4-RELEASE/">10.4</link>; + is the latest release from the <emphasis>11-STABLE</emphasis> branch; it + was released in October 2017.</para> <para>Releases 版 <link linkend="release-freq">每幾個月</link> 才會發行一次。 雖然如此，有很多人和 FreeBSD 原始碼同步更新 (詳見 <link linkend="current">FreeBSD-CURRENT</link> 和 <link linkend="stable">FreeBSD-STABLE</link>的相關問題) ，但因為原始碼是一直不斷地在變動的，所以如果要這麼做的話得要花上更多的精力。</para> @@ -276,9 +330,33 @@ </question> <answer> - <para>回溯到 FreeBSD 2.0.5 剛發表的時候，我們決定把 FreeBSD 的發展 分成兩支。一支叫做 <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/current-stable.html#stable">-STABLE</link>，另一支叫 <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/current-stable.html#current">-CURRENT</link>。主要發行版是由<emphasis>FreeBSD-STABLE</emphasis> 這個開發分支而來。他的變動較慢，而且一般來說假設他們都已經先在FreeBSD-CURRENT測試過了。然而在任何時候，FreeBSD-STABLE的原始碼仍有可能不一定適合一般用途，因為他可能包含在 FreeBSD-CURRENT 沒有發現到的錯誤。沒有能力和資源的使用者應該改使用 FreeBSD 正式發行版。<emphasis>FreeBSD-CURRENT</emphasis> 從2.0開始就是另一個分支，一直到11.1-RELEASE和之後的版本都還是。更多關於開發分支的資訊請見 <quote><link xlink:href="@@URL_RELPREFIX@@/doc/en_US.IS O8859-1/articles/releng/release-proc.html#rel-branch">FreeBSD Release Engineering: Creating the Release Branch</link></quote> ，分支的開發狀態和接下來的發行計畫時間表可以在 <link xlink:href="https://www.FreeBSD.org/releng">Release Engineering 資訊</link> 找到。</para> + <para xml:lang="en">Back when FreeBSD 2.0.5 was released, FreeBSD + development branched in two. One branch was named <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/current-stable.html#stable">-STABLE</link>, + one <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/current-stable.html#current">-CURRENT</link>. + <emphasis>FreeBSD-STABLE</emphasis> 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. + <emphasis>FreeBSD-CURRENT</emphasis>, 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 <quote><link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/releng/release-proc.html#rel-branch">FreeBSD + Release Engineering: Creating the Release + Branch</link></quote>, the status of the branches and + the upcoming release schedule can be found on the <link xlink:href="https://www.FreeBSD.org/releng">Release + Engineering Information</link> page.</para> - <para>11.1-STABLE 是目前正在發展中的 <emphasis>-STABLE</emphasis> 分支。最新的 11.1-STABLE 是在 2017年七月發行的 11.1-RELEASE。</para> + <para xml:lang="en">12.0-STABLE is the actively developed + <emphasis>-STABLE</emphasis> branch. The latest release + on the 12.0-STABLE branch is + 12.0-RELEASE, which was released in + December 2018.</para> <para><emphasis>12-CURRENT</emphasis> 這個分支是 FreeBSD 的 <emphasis>-CURRENT</emphasis> 分支，仍然不斷地在發展當中。 如果想要知道更多關於這個分支的資訊的話，請參考 <link linkend="current">什麼是 FreeBSD-CURRENT?</link> 。</para> </answer> @@ -316,11 +394,15 @@ </question> <answer> - <para>每個 FreeBSD 的重要版本都可以經由匿名 FTP 從 <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/">; FreeBSD FTP 站</link> 取得：</para> + <para xml:lang="en">Every significant release of FreeBSD is available via + anonymous FTP from the <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/">FreeBSD + FTP site</link>:</para> <itemizedlist> <listitem> - <para>最新版 <emphasis>11-STABLE</emphasis> , 也就是 11.1-RELEASE 請到 <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/i386/11.1-RELEASE/">11.1-RELEASE 這個目錄</link>。</para> + <para xml:lang="en">The latest <emphasis>12-STABLE</emphasis> release, + 12.0-RELEASE can be found in the <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/i386/12.0-RELEASE/">12.0-RELEASE + directory</link>.</para> </listitem> <listitem> @@ -328,7 +410,9 @@ </listitem> <listitem> - <para>最新版 <emphasis>10-STABLE</emphasis> , 也就是10.4-RELEASE 請到 <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/10.4-RELEASE/">10.4-RELEASE 這個目錄</link>。</para> + <para xml:lang="en">The latest <emphasis>11-STABLE</emphasis> release, + 10.4-RELEASE can be found in the <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/10.4-RELEASE/">10.4-RELEASE + directory</link>.</para> </listitem> </itemizedlist> @@ -362,7 +446,11 @@ </question> <answer> - <para>FreeBSD 文件計畫已陸續發表了相當廣泛範圍的文件，可在 <uri xlink:href="https://www.FreeBSD.org/docs.html">https://www.FreeBSD.org/docs.html</uri>; 取得。除此之外，也請參閱本篇。問與答最後的 <link linkend="bibliography">書目</link>，以及手冊中的 <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/bibliography.html">書目</link></para> + <para xml:lang="en">The project produces a wide range of documentation, + available online from this link: <uri xlink:href="https://www.FreeBSD.org/docs.html">https://www.FreeBSD.org/docs.html</uri>. + In addition, the <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/bibliography.html">the + bibliography in the Handbook</link> reference other + recommended books.</para> </answer> </qandaentry> @@ -456,6 +544,12 @@ </row> <row> + <entry xml:lang="en"><literal>ko_KR.UTF-8</literal></entry> + + <entry xml:lang="en">Korean (Korea, UTF-8 encoding)</entry> + </row> + + <row> <entry><literal>mn_MN.UTF-8</literal></entry> <entry>蒙古文 (蒙古, UTF-8 編碼)</entry> @@ -468,12 +562,6 @@ </row> <row> - <entry><literal>no_NO.ISO8859-1</literal></entry> - - <entry>Norwegian (Norway)</entry> - </row> - - <row> <entry><literal>pl_PL.ISO8859-2</literal></entry> <entry>波蘭文 (波蘭)</entry> @@ -492,12 +580,6 @@ </row> <row> - <entry><literal>sr_YU.ISO8859-2</literal></entry> - - <entry>賽爾維亞文 (賽爾維亞)</entry> - </row> - - <row> <entry><literal>tr_TR.ISO8859-9</literal></entry> <entry>土耳其文 (土耳其)</entry> @@ -586,7 +668,12 @@ <orderedlist> <listitem> - <para>當採用 <literal>html-split</literal> 格式時，檔案先透過 <citerefentry><refentrytitle>tar</refentrytitle><manvolnum>1</manvolnum></citerefentry> 工具來進行打包。接著在將產生出來的 <filename>.tar</filename> 檔接透過第二點所述的壓縮方式壓縮。</para> + <para xml:lang="en">Where the format is + <literal>html-split</literal>, the files are + bundled up using <citerefentry><refentrytitle>tar</refentrytitle><manvolnum>1</manvolnum></citerefentry>. The resulting + <filename>.tar</filename> is then compressed + using the compression schemes detailed in the next + point.</para> </listitem> <listitem> @@ -655,7 +742,8 @@ </listitem> </itemizedlist> - <para>FreeBSD 的維基百科有一份 IRC 頻道的 <link xlink:href="http://wiki.freebsd.org/IrcChannels">完整清單</link>。</para>; + <para xml:lang="en">The FreeBSD wiki has a <link xlink:href="https://wiki.freebsd.org/IRC/Channels">good + list</link> of IRC channels.</para> <para>每個頻道都是不同且互相獨立的。因為他們的聊天風格不同，您可以每個都試試看來找到適合您的頻道。</para> </answer> @@ -882,30 +970,6 @@ </qandaentry> <qandaentry> - <question xml:id="no-install-cdrom"> - <para xml:lang="en">I booted from a CD, but the install program - says no CD-ROM is found. Where did it go?</para> - </question> - - <answer> - <para xml:lang="en">The usual cause of this problem is a mis-configured - CD-ROM drive. Many PCs now ship with the CD-ROM as the - slave device on the secondary IDE controller, with no - master device on that controller. This is illegal - according to the ATAPI specification, but <trademark class="registered">Windows</trademark> plays - fast and loose with the specification, and the BIOS - ignores it when booting. This is why the BIOS was able to - see the CD-ROM to boot from it, but why FreeBSD cannot see it - to complete the install.</para> - - <para xml:lang="en">Reconfigure the system so that the CD-ROM is either - the master device on the IDE controller it is attached to, - or make sure that it is the slave on an IDE controller - that also has a master device.</para> - </answer> - </qandaentry> - - <qandaentry> <question xml:id="need-complete-sources"> <para>我需要安裝完整的原始碼嗎？</para> </question> @@ -944,11 +1008,11 @@ </question> <answer> - <para xml:lang="en">FreeBSD 9 and later use + <para xml:lang="en">FreeBSD uses <emphasis>SHA512</emphasis> by default. DES passwords are still available for backwards compatibility - with legacy operating systems which still + 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 @@ -1042,7 +1106,7 @@ <para xml:lang="en">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 <link xlink:href="https://www.FreeBSD.org/releases/11.1R/hardware.html">11.1</link>; + for FreeBSD <link xlink:href="https://www.FreeBSD.org/releases/12.0R/hardware.html">12.0</link>; or <link xlink:href="https://www.FreeBSD.org/releases/10.4R/hardware.html">10.4</link>; and search the mailing list <link xlink:href="https://www.FreeBSD.org/search/#mailinglists">archives</link>; before asking about the latest and greatest hardware. @@ -1231,7 +1295,7 @@ <answer> <para xml:lang="en">See the complete list in the Hardware Notes for FreeBSD - <link xlink:href="https://www.FreeBSD.org/releases/11.1R/hardware.html">11.1</link>; + <link xlink:href="https://www.FreeBSD.org/releases/12.0R/hardware.html">12.0</link>; or <link xlink:href="https://www.FreeBSD.org/releases/10.4R/hardware.html">10.4</link>.</para>; </answer> </qandaentry> @@ -1848,7 +1912,8 @@ kern.timecounter.hardware: TSC -> i8254</screen> </question> <answer> - <para xml:lang="en">This means that a process is trying to page memory to + <para xml:lang="en">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 @@ -1991,7 +2056,7 @@ kern.timecounter.hardware: TSC -> i8254</screen> <qandaentry> <question xml:id="how-do-download-ports-tree"> <para xml:lang="en">How do I download the Ports tree? Should I be using - SVN?</para> + Subversion?</para> </question> <answer> @@ -2004,7 +2069,7 @@ kern.timecounter.hardware: TSC -> i8254</screen> use this tool.</para> </listitem> <listitem> - <para xml:lang="en">Use SVN if custom patches to the + <para xml:lang="en">Use Subversion if custom patches to the ports tree are needed. Refer to <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/svn.html">Using Subversion</link> for details.</para> </listitem> @@ -2026,23 +2091,22 @@ kern.timecounter.hardware: TSC -> i8254</screen> <qandaentry> <question xml:id="ports-4x"> <para xml:lang="en">Why can I not build this port on my - 10.<replaceable>X</replaceable> -, or - 11.<replaceable>X</replaceable> -STABLE machine?</para> + 11.<replaceable>X</replaceable> -, or + 12.<replaceable>X</replaceable> -STABLE machine?</para> </question> <answer> - <para xml:lang="en">If the installed FreeBSD version lags - significantly behind <emphasis>-CURRENT</emphasis> or - <emphasis>-STABLE</emphasis>, update the - Ports Collection using the instructions in <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/ports-using.html">Using + <para xml:lang="en">If the installed FreeBSD version lags significantly + behind <emphasis>-CURRENT</emphasis> or + <emphasis>-STABLE</emphasis>, update the Ports Collection + using the instructions in <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/ports-using.html">Using the Ports Collection</link>. If the system is up-to-date, someone might have committed a change to the port which works for <emphasis>-CURRENT</emphasis> but which broke the port for <emphasis>-STABLE</emphasis>. <link xlink:href="https://bugs.FreeBSD.org/submit/">Submit</link>; a bug report, since the Ports Collection is supposed to - work - for both the <emphasis>-CURRENT</emphasis> and + work for both the <emphasis>-CURRENT</emphasis> and <emphasis>-STABLE</emphasis> branches.</para> </answer> </qandaentry> @@ -2062,11 +2126,10 @@ kern.timecounter.hardware: TSC -> i8254</screen> <para xml:lang="en">There are rare cases where <filename>INDEX</filename> will not build due to odd cases involving - <varname>WITH_<replaceable>*</replaceable></varname> or - <varname>WITHOUT_<replaceable>*</replaceable></varname> - variables being set in <filename>make.conf</filename>. If + <varname>OPTIONS_SET</varname> + being set in <filename>make.conf</filename>. If you suspect that this is the case, try to make - <filename>INDEX</filename> with those make variables + <filename>INDEX</filename> with those variables turned off before reporting it to <link xlink:href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-ports">FreeBSD ports mailing list</link>.</para> </answer> </qandaentry> @@ -2309,9 +2372,8 @@ kern.timecounter.hardware: TSC -> i8254</screen> </listitem> <listitem> - <para xml:lang="en">The <command>make - buildkernel</command> command did not complete - successfully. The <command>make + <para xml:lang="en">The <command>make buildkernel</command> did not + complete successfully. The <command>make buildkernel</command> target relies on files generated by the <command>make buildworld</command> target to complete its job correctly.</para> @@ -2599,10 +2661,7 @@ kern.sched.name: ULE</screen> <term xml:lang="en">ZFS</term> <listitem> - <para xml:lang="en">FreeBSD includes a port of <trademark>Sun</trademark>'s ZFS driver. The - current recommendation is to use it only on - amd64 platforms with sufficient memory. For - more information, see <citerefentry><refentrytitle>zfs</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para> + <para>FreeBSD 包含由 <trademark>Sun</trademark> 移植過來的 ZFS 驅動程式。 目前的建議是僅在記憶體充足的 amd64 平臺上使用它。有關更詳細資訊, 請參閱 <citerefentry><refentrytitle>zfs</refentrytitle><manvolnum>8</manvolnum></citerefentry>。</para> </listitem> </varlistentry> </variablelist> @@ -2957,8 +3016,8 @@ kern.sched.name: ULE</screen> </question> <answer> - <para xml:lang="en">This section <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/adding-swap-space.html">of the Handbook</link> - describes how to do this.</para> + <para xml:lang="en">This section <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/adding-swap-space.html">of + the Handbook</link> describes how to do this.</para> </answer> </qandaentry> @@ -3003,179 +3062,105 @@ kern.sched.name: ULE</screen> </answer> </qandaentry> + </qandaset> + </chapter> + + <chapter xml:id="all-about-zfs"> + <title xml:lang="en">ZFS</title> + + <qandaset> <qandaentry> - <question xml:id="slow-boot-memtest"> - <para xml:lang="en">Why does FreeBSD pause for a long time at boot when the - system has large amounts of ram?</para> + <question xml:id="how-much-ram-for-zfs"> + <para>使用 ZFS 最少需要多少記憶體？</para> </question> <answer> - <para xml:lang="en">FreeBSD 10.1 and earlier executes a memory test early - in the boot process. - When the system has a small amount of memory, the test - takes a few seconds. Computers with tens or hundreds of - gigabytes of memory can take several minutes to complete - the test. The memory test can be disabled by adding - <literal>hw.memtest.tests=0</literal> to - <filename>/boot/loader.conf</filename>.</para> - - <para xml:lang="en">For more details, see <citerefentry><refentrytitle>loader.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para> + <para>至少需要 4GB 的記憶體才能跑得順，但不同的工作負載可能會造成相當大的差異。</para> </answer> </qandaentry> - </qandaset> - </chapter> - <chapter xml:id="all-about-zfs"> - <title xml:lang="en">ZFS</title> + <qandaentry> + <question xml:id="what-is-zil"> + <para>ZIL 是什麼而又何時會被使用？</para> + </question> - <qandaset> - <qandaentry> - <question xml:id="how-much-ram-for-zfs"> - <para xml:lang="en">What is the minimum amount of RAM one should have to - run ZFS?</para> - </question> + <answer> + <para>The <acronym>ZIL</acronym> (<acronym>ZFS</acronym> 動向日誌) 是一個紀錄日誌，用以實現系統當機時 POSIX 寫入保證的語義，多個正常 ZFS 寫入動作會被分成多個交易處理群組，並在交易處理群組被填滿時寫入磁碟 (<quote>Transaction Group Commit</quote>)。然而像 <citerefentry><refentrytitle>fsync</refentrytitle><manvolnum>2</manvolnum></citerefentry> 這樣的系統呼叫，會要求該系統呼叫在返回前，能承諾已將資料寫入磁碟，ZIL 就是用來紀錄確認為已執行寫入的資料，但其實尚未存在於磁碟上，即尚未完成交易處理，交易處理群組具有時間戳記，在系統當機後，找到 ZIL 最後一個有效的時間戳記，即將遺失的資料再舍併至磁碟上。</para> + </answer> + </qandaentry> - <answer> - <para xml:lang="en">A minimum of 4GB of RAM is required for comfortable - usage, but individual workloads can vary widely.</para> - </answer> - </qandaentry> + <qandaentry> + <question xml:id="need-ssd-for-zil"> + <para>我需要用固態硬碟 (SSD) 來存 ZIL 嗎？</para> + </question> - <qandaentry> - <question xml:id="what-is-zil"> - <para xml:lang="en">What is the ZIL and when does it get used?</para> - </question> + <answer> + <para>ZFS 預設將 ZIL 儲存在包含所有資料的 zpool 中，如果應用程式的寫入負載很重，將 ZIL 儲存在同步速度非常快的獨立設備中，藉由循序寫入效能的提高可以改善整個系統的效能，對於其他類型的工作負載， 固態硬碟就不會有太大的助益。</para> + </answer> + </qandaentry> - <answer> - <para xml:lang="en">The <acronym>ZIL</acronym> (<acronym>ZFS</acronym> - 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 (<quote>Transaction Group - Commit</quote>). However syscalls like <citerefentry><refentrytitle>fsync</refentrytitle><manvolnum>2</manvolnum></citerefentry> - 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.</para> - </answer> - </qandaentry> + <qandaentry> + <question xml:id="what-is-l2arc"> + <para>L2ARC 是什麼？</para> + </question> - <qandaentry> - <question xml:id="need-ssd-for-zil"> - <para xml:lang="en">Do I need a SSD for ZIL?</para> - </question> + <answer> + <para>The <acronym>L2ARC</acronym> (Second Level Adaptive Replacement Cache) 是存於快速儲存設備 <acronym>SSD</acronym> 上的讀取快取，此快取在重新開機後會消失，請注意記憶體是第一層的快取，只有在記憶體不足的情況下才需要 L2ARC。</para> - <answer> - <para xml:lang="en">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.</para> - </answer> - </qandaentry> + <para>L2ARC 需要 ARC 的空間來為其製作索引，因此，有一種反常的情況，如果有一種工作集 (working set) 可以完美地剛好放入 ARC，一旦系統使用 L2ARC，該工作集的運作將不再完美，因為 ARC 需要用一部分空間來保存 L2ARC 的索引，以至於必須將工作集的一部分存入比記憶體慢的 L2ARC。</para> + </answer> + </qandaentry> - <qandaentry> - <question xml:id="what-is-l2arc"> - <para xml:lang="en">What is the L2ARC?</para> - </question> + <qandaentry> + <question xml:id="should-enable-dedup"> + <para>建議啟用去冗餘 (deduplication) 嗎？</para> + </question> - <answer> - <para xml:lang="en">The <acronym>L2ARC</acronym> is a read cache stored - on a fast device such as an <acronym>SSD</acronym>. - 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.</para> + <answer> + <para>一般而言，不建議這麼做。</para> - <para xml:lang="en">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.</para> - </answer> - </qandaentry> + <para>去冗餘需要相當多的記憶體，而且會讓讀寫磁碟所需的時間變長，除非磁碟上儲存了非常多重複的資料，例如：虛擬機的映像檔或者是使用者的備份資料，否則開啟去冗餘可能弊大於利。另一個需要考量的狀況是：啟用去冗餘功能之後再將其關閉，無法將磁碟上去冗餘的狀態立即逆轉，必須等到下次修改了之前被去冗餘的資料，變更的區塊才會再被複製一份。</para> - <qandaentry> - <question xml:id="should-enable-dedup"> - <para xml:lang="en">Is enabling deduplication advisable?</para> - </question> + <para>去冗餘也可能會導致某些非預期的情況，特別是刪除檔案時可能會慢很多。</para> + </answer> + </qandaentry> - <answer> - <para xml:lang="en">Generally speaking, no.</para> + <qandaentry> + <question xml:id="zpool-fully-full"> + <para>在我建立的 ZFS pool 中無法刪除和新增檔案，應該怎麼修復？</para> + </question> - <para xml:lang="en">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.</para> + <answer> + <para>這很有可能是該 pool 的空間使用率已達 100% 滿了，因 ZFS 需要儲存空間以將紀錄交易處理的輔助資料 (metadata) 寫入，為了讓該 pool 回復至可用狀態，必須用檔案切除的方法 (truncate 命令) 刪除不重要的檔案：</para> - <para xml:lang="en">Deduplication can also lead to some unexpected - situations. In particular, deleting files may become - much slower.</para> - </answer> - </qandaentry> + <screen><prompt>%</prompt> <userinput>truncate -s 0 unimportant-file</userinput></screen> - <qandaentry> - <question xml:id="zpool-fully-full"> - <para xml:lang="en">I cannot delete or create files on my ZFS pool. - How can I fix this?</para> - </question> + <para>因為檔案切除不需要建立交易處理紀錄，並能釋放出可使用的磁碟區塊。</para> - <answer> - <para xml:lang="en">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:</para> + <note> + <para>如果系統曾進行過額外的 ZFS dataset 調校，例如：去冗餘，釋放出來的空間也許不會立即可得。</para> + </note> + </answer> + </qandaentry> - <screen xml:lang="en"><prompt>%</prompt> <userinput>truncate -s 0 unimportant-file</userinput></screen> + <qandaentry> + <question xml:id="zfs-ssd-trim"> + <para>ZFS 支援固態硬碟 (SSD) 的 TRIM 功能嗎？</para> + </question> - <para xml:lang="en">File truncation works because a new transaction is - not started, new spare blocks are created - instead.</para> + <answer> + <para>自 FreeBSD 10-CURRENT 修定 r<revnumber>240868</revnumber> 開始，就支援 ZFS TRIM。ZFS TRIM 的支援分別已在 r<revnumber>252162</revnumber> 和 r<revnumber>251419</revnumber> 的修訂，加進所有 FreeBSD-STABLE 分支。</para> - <note> - <para xml:lang="en">On systems with additional ZFS dataset tuning, - such as deduplication, the space may not be - immediately available</para> - </note> - </answer> - </qandaentry> + <para>ZFS TRIM 預設就已開啟，也可以將其關閉，只要加入一行設定到 <filename>/etc/sysctl.conf</filename>:</para> - <qandaentry> - <question xml:id="zfs-ssd-trim"> - <para xml:lang="en">Does ZFS support TRIM for Solid State Drives?</para> - </question> + <programlisting>vfs.zfs.trim.enabled=0</programlisting> - <answer> - <para xml:lang="en">ZFS TRIM support was added to FreeBSD 10-CURRENT - with revision r<revnumber>240868</revnumber>. ZFS TRIM - support was added to all FreeBSD-STABLE branches in - r<revnumber>252162</revnumber> and - r<revnumber>251419</revnumber>, respectively.</para> - - <para xml:lang="en">ZFS TRIM is enabled by default, and can be turned - off by adding this line to - <filename>/etc/sysctl.conf</filename>:</para> - - <programlisting xml:lang="en">vfs.zfs.trim_disable=1</programlisting> - - <note> - <para xml:lang="en">ZFS TRIM may not work with all configurations, - such as a ZFS filesystem on a GELI-backed - device.</para> - </note> - </answer> - </qandaentry> - </qandaset> + <note> + <para>ZFS TRIM 也可能某些設定中會無效，例如：在採用 GELI 裝置上的 ZFS 檔案系統。</para> + </note> + </answer> + </qandaentry> + </qandaset> </chapter> <chapter xml:id="admin"> @@ -3290,15 +3275,15 @@ kern.sched.name: ULE</screen> <para xml:lang="en">Restart the system using <userinput>boot -s</userinput> at the loader prompt to enter single-user mode. When prompted for a shell pathname, press - <keycap>Enter</keycap> and run <command>mount - -urw /</command> to re-mount the root file system in + <keycap>Enter</keycap> and run <command>mount -urw + /</command> to re-mount the root file system in read/write mode. You may also need to run <command>mount -a -t ufs</command> 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 <citerefentry><refentrytitle>ed</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para> + 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 + <citerefentry><refentrytitle>ed</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para> <para xml:lang="en">In order to use a full screen editor such as <citerefentry><refentrytitle>vi</refentrytitle><manvolnum>1</manvolnum></citerefentry> or <citerefentry vendor="ports"><refentrytitle>emacs</refentrytitle><manvolnum>1</manvolnum></citerefentry>, run @@ -3323,7 +3308,7 @@ kern.sched.name: ULE</screen> <answer> <para xml:lang="en">See the <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/printing.html">Handbook entry on printing</link> for troubleshooting - tips.</para> + tips.</para> </answer> </qandaentry> @@ -3698,12 +3683,12 @@ options SYSVMSG # enable for messaging</pr <para xml:lang="en"><citerefentry><refentrytitle>rpc.statd</refentrytitle><manvolnum>8</manvolnum></citerefentry> maps its status file (resident on <filename>/var</filename>) into its address space; to save - worrying about remapping it later when it needs to grow, - it maps it with a generous size. This is very evident - from the source code, where one can see that the length - argument to <citerefentry><refentrytitle>mmap</refentrytitle><manvolnum>2</manvolnum></citerefentry> is <literal>0x10000000</literal>, - or one sixteenth of the address space on an IA32, or - exactly 256 MB.</para> + 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 <citerefentry><refentrytitle>mmap</refentrytitle><manvolnum>2</manvolnum></citerefentry> is + <literal>0x10000000</literal>, or one sixteenth of the + address space on an IA32, or exactly 256 MB.</para> </answer> </qandaentry> @@ -3714,11 +3699,11 @@ options SYSVMSG # enable for messaging</pr </question> <answer> - <para xml:lang="en">The system is running a securelevel greater than 0. - Lower the securelevel and try again. For - more information, see <link linkend="securelevel">the <acronym>FAQ</acronym> - entry on securelevel</link> and the <citerefentry><refentrytitle>init</refentrytitle><manvolnum>8</manvolnum></citerefentry> manual - page.</para> + <para xml:lang="en">The system is running at securelevel greater than 0. + Lower the securelevel and try again. For more + information, see <link linkend="securelevel">the + <acronym>FAQ</acronym> entry on securelevel</link> and + the <citerefentry><refentrytitle>init</refentrytitle><manvolnum>8</manvolnum></citerefentry> manual page.</para> </answer> </qandaentry> @@ -4014,7 +3999,7 @@ options SYSVMSG # enable for messaging</pr <filename>/etc/X11/xorg.conf</filename>, as seen in this example:</para> - <programlisting xml:lang="en">Section "InputDevice" + <programlisting xml:lang="en">Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Protocol" "auto" @@ -4023,9 +4008,9 @@ options SYSVMSG # enable for messaging</pr Option "ZAxisMapping" "4 5" EndSection</programlisting> - <para xml:lang="en">To use the mouse in - <application>Emacs</application>, also add the following - lines to<filename>~/.emacs</filename>:</para> + <para xml:lang="en">The mouse can be enabled in + <application>Emacs</application>by adding these + lines to <filename>~/.emacs</filename>:</para> <programlisting xml:lang="en">;; wheel mouse (global-set-key [mouse-4] 'scroll-down) @@ -4425,7 +4410,7 @@ Key F15 A A Menu Workplace Nop</p card is supported by which driver on their web site: <uri xlink:href="http://www.nvidia.com/object/IO_32667.html">http://www.nvidia.com/object/IO_32667.html</uri>.</para>; <para xml:lang="en">For Matrox G200/G400, check the - <package>x11-servers/mga_hal</package> + <package>x11-drivers/xf86-video-mga</package> port.</para> <para xml:lang="en">For ATI Rage 128 and Radeon see @@ -4825,6 +4810,22 @@ Key F15 A A Menu Workplace Nop</p to <literal>0</literal>.</para> </answer> </qandaentry> + + <qandaentry> + <question xml:id="ipv6-only"> + <para xml:lang="en">How do I compile an IPv6 only kernel?</para> + </question> + + <answer> + <para xml:lang="en">Configure your kernel with these settings: + + <screen xml:lang="en">include GENERIC +ident GENERIC-IPV6ONLY +makeoptions MKMODULESENV+="WITHOUT_INET_SUPPORT=" +nooptions INET +nodevice gre</screen></para> + </answer> + </qandaentry> </qandaset> </chapter> @@ -4998,7 +4999,8 @@ Key F15 A A Menu Workplace Nop</p <qandaentry> <question xml:id="extra-named-port"> - <para xml:lang="en">BIND (<command>named</command>) is listening on some + <para xml:lang="en"><application>BIND9</application> + (<command>named</command>) is listening on some high-numbered ports. What is going on?</para> </question> @@ -5018,7 +5020,8 @@ Key F15 A A Menu Workplace Nop</p <para xml:lang="en">If a port number (like 53) is specified via the <literal>query-source</literal> or <literal>query-source-v6</literal> options in - <filename>/etc/namedb/named.conf</filename>, randomized + <filename>/usr/local/etc/namedb/named.conf</filename>, + randomized port selection will not be used. It is strongly recommended that these options not be used to specify fixed port numbers.</para> @@ -5852,7 +5855,7 @@ ATDT1234567</programlisting> or run this command after the system is up and running:</para> - <screen xml:lang="en"><prompt>%</prompt> <userinput>dmesg | grep -E "^sio[0-9]"</userinput> + <screen xml:lang="en"><prompt>%</prompt> <userinput>grep -E '^(sio|uart)[0-9]' < /var/run/dmesg.boot</userinput> 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 @@ -6052,8 +6055,8 @@ hint.sio.7.irq="12"</programlisting> memory. Any memory that programs do not actively allocate is used within the FreeBSD kernel as disk cache. The values shown by <citerefentry><refentrytitle>top</refentrytitle><manvolnum>1</manvolnum></citerefentry> labeled as - <literal>Inact</literal>, <literal>Cache</literal>, and - <literal>Buf</literal> are all cached data at different + <literal>Inact</literal> and <literal>Laundry</literal> + 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 @@ -6144,8 +6147,8 @@ hint.sio.7.irq="12"</programlisting> <answer> <para xml:lang="en">See the <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/fdp-primer/translations.html">Translation - <acronym>FAQ</acronym></link> in the FreeBSD Documentation Project - Primer.</para> + <acronym>FAQ</acronym></link> in the FreeBSD Documentation + Project Primer.</para> </answer> </qandaentry> @@ -6157,11 +6160,10 @@ hint.sio.7.irq="12"</programlisting> <answer> <para xml:lang="en">The <systemitem class="fqdomainname">FreeBSD.org</systemitem> mail - system implements some - <application>Postfix</application> 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: </para> + system implements some <application>Postfix</application> + 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:</para> <itemizedlist> <listitem> @@ -6661,13 +6663,17 @@ hint.sio.7.irq="12"</programlisting> <qandaentry> <question xml:id="how-to-contribute"> - <para xml:lang="en">How can I contribute to FreeBSD?</para> + <para xml:lang="en">How can I contribute to FreeBSD? What can I do to + help?</para> </question> <answer> - <para xml:lang="en">See the article on <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/contributing/article.html">Contributing - to FreeBSD</link> for specific advice on how to do this. - Assistance is more than welcome!</para> + <para xml:lang="en">We accept all types of contributions: documentation, + code, and even art. See the article on <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/contributing/article.html">Contributing + to FreeBSD</link> for specific advice on how to do + this.</para> + + <para xml:lang="en">And thanks for the thought!</para> </answer> </qandaentry> @@ -6677,21 +6683,21 @@ hint.sio.7.irq="12"</programlisting> </question> <answer> - <para xml:lang="en">There are currently 3 active/semi-active + <para xml:lang="en">There are currently 2 active/semi-active branches in the FreeBSD <link xlink:href="http://svnweb.FreeBSD.org/base/">Subversion Repository</link>. (Earlier branches are only changed - very rarely, which is why there are only 3 + very rarely, which is why there are only 2 active branches of development):</para> <itemizedlist> <listitem> - <para xml:lang="en"><symbol>stable/10/</symbol> AKA - <emphasis>10-STABLE</emphasis></para> + <para xml:lang="en"><symbol>stable/11/</symbol> AKA + <emphasis>11-STABLE</emphasis></para> </listitem> <listitem> - <para xml:lang="en"><symbol>stable/11/</symbol> AKA - <emphasis>11-STABLE</emphasis></para> + <para xml:lang="en"><symbol>stable/12/</symbol> AKA + <emphasis>12-STABLE</emphasis></para> </listitem> <listitem> @@ -6708,29 +6714,15 @@ hint.sio.7.irq="12"</programlisting> <emphasis>-CURRENT</emphasis>.</para> <para xml:lang="en">Right now, <emphasis>-CURRENT</emphasis> is the - 12.<replaceable>X</replaceable> development stream; the <emphasis>11-STABLE</emphasis> - branch, <symbol>stable/11/</symbol>, forked off from - <emphasis>-CURRENT</emphasis> in April 2016 and the - <emphasis>10-STABLE</emphasis> branch, <symbol>stable/10/</symbol>, forked off from - <emphasis>-CURRENT</emphasis> in August 2015.</para> + 13.<replaceable>X</replaceable> development stream; the <emphasis>12-STABLE</emphasis> + branch, <symbol>stable/12/</symbol>, forked off from + <emphasis>-CURRENT</emphasis> in December 2018 and the + <emphasis>11-STABLE</emphasis> branch, <symbol>stable/11/</symbol>, forked off from + <emphasis>-CURRENT</emphasis> in October 2016.</para> </answer> </qandaentry> <qandaentry> - <question xml:id="submitting-kernel-extensions"> - <para xml:lang="en">I have written a kernel extension, who do I send it - to?</para> - </question> - - <answer> - <para xml:lang="en">Take a look at the article on <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/contributing/article.html">Contributing - to FreeBSD</link> to learn how to submit code.</para> - - <para xml:lang="en">And thanks for the thought!</para> - </answer> - </qandaentry> - - <qandaentry> <question xml:id="kernel-panic-troubleshooting"> <para xml:lang="en">How can I make the most of the data I see when my kernel panics?</para> @@ -6984,928 +6976,4 @@ panic: page fault</programlisting> them</link> in making this <acronym>FAQ</acronym> even better.</para> </chapter> - - -<!-- - $FreeBSD$ ---> -<bibliography version="5.0" xml:id="bibliography"> - <title xml:lang="en">Bibliography</title> - - <biblioentry xml:id="biblio-unleashed"> - <biblioset relation="book" xml:lang="en"> - <citetitle>FreeBSD Unleashed</citetitle> - - <authorgroup> - <author xml:lang="en"><personname><firstname>Michael</firstname><surname>Urban</surname></personname></author> - <author xml:lang="en"><personname><firstname>Brian</firstname><surname>Tiemann</surname></personname></author> - </authorgroup> - - <publisher> - <publishername xml:lang="en">Sams</publishername> - </publisher> - - <edition xml:lang="en">1st edition</edition> - - <pagenums xml:lang="en">992 pages</pagenums> - - <pubdate xml:lang="en">October 2001</pubdate> - - <biblioid class="isbn" xml:lang="en">ISBN 0-67232-206-4</biblioid> *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201901161448.x0GEmLeb002689>