Date: Thu, 26 Oct 2017 15:25:09 +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: r51147 - head/zh_TW.UTF-8/books/handbook Message-ID: <201710261525.v9QFP97k017797@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: rcyu Date: Thu Oct 26 15:25:09 2017 New Revision: 51147 URL: https://svnweb.freebsd.org/changeset/doc/51147 Log: - Update po file with newest handbook document. - Translated following chaptors or sectors: 28.7. Domain Name System (DNS) 28.8. Apache HTTP Server 28.9. File Transfer Protocol (FTP) 28.10. File and Print Services for Microsoft® Windows® Clients (Samba) 28.11. Clock Synchronization with NTP 29.1. Synopsis 29.2. Firewall Concepts Submitted by: cwlin@gmail.com Differential Revision: https://reviews.freebsd.org/D12756 Modified: head/zh_TW.UTF-8/books/handbook/book.xml head/zh_TW.UTF-8/books/handbook/zh_TW.po Modified: head/zh_TW.UTF-8/books/handbook/book.xml ============================================================================== --- head/zh_TW.UTF-8/books/handbook/book.xml Thu Oct 26 00:35:49 2017 (r51146) +++ head/zh_TW.UTF-8/books/handbook/book.xml Thu Oct 26 15:25:09 2017 (r51147) @@ -22,6 +22,7 @@ <!ENTITY pgpkey.acm SYSTEM "acm.key"> <!ENTITY pgpkey.adamw SYSTEM "adamw.key"> <!ENTITY pgpkey.adrian SYSTEM "adrian.key"> +<!ENTITY pgpkey.adridg SYSTEM "adridg.key"> <!ENTITY pgpkey.ae SYSTEM "ae.key"> <!ENTITY pgpkey.ahze SYSTEM "ahze.key"> <!ENTITY pgpkey.ak SYSTEM "ak.key"> @@ -72,6 +73,7 @@ <!ENTITY pgpkey.bf SYSTEM "bf.key"> <!ENTITY pgpkey.bhaga SYSTEM "bhaga.key"> <!ENTITY pgpkey.bhd SYSTEM "bhd.key"> +<!ENTITY pgpkey.bhughes SYSTEM "bhughes.key"> <!ENTITY pgpkey.billf SYSTEM "billf.key"> <!ENTITY pgpkey.bjk SYSTEM "bjk.key"> <!ENTITY pgpkey.bk SYSTEM "bk.key"> @@ -101,6 +103,7 @@ <!ENTITY pgpkey.ceri SYSTEM "ceri.key"> <!ENTITY pgpkey.cherry SYSTEM "cherry.key"> <!ENTITY pgpkey.chinsan SYSTEM "chinsan.key"> +<!ENTITY pgpkey.chuck SYSTEM "chuck.key"> <!ENTITY pgpkey.cjc SYSTEM "cjc.key"> <!ENTITY pgpkey.cjh SYSTEM "cjh.key"> <!ENTITY pgpkey.clement SYSTEM "clement.key"> @@ -131,6 +134,7 @@ <!ENTITY pgpkey.db SYSTEM "db.key"> <!ENTITY pgpkey.dbaio SYSTEM "dbaio.key"> <!ENTITY pgpkey.dbn SYSTEM "dbn.key"> +<!ENTITY pgpkey.dch SYSTEM "dch.key"> <!ENTITY pgpkey.dchagin SYSTEM "dchagin.key"> <!ENTITY pgpkey.dcs SYSTEM "dcs.key"> <!ENTITY pgpkey.dd SYSTEM "dd.key"> @@ -176,6 +180,7 @@ <!ENTITY pgpkey.fluffy SYSTEM "fluffy.key"> <!ENTITY pgpkey.flz SYSTEM "flz.key"> <!ENTITY pgpkey.foxfair SYSTEM "foxfair.key"> +<!ENTITY pgpkey.fsu SYSTEM "fsu.key"> <!ENTITY pgpkey.gabor SYSTEM "gabor.key"> <!ENTITY pgpkey.gad SYSTEM "gad.key"> <!ENTITY pgpkey.gahr SYSTEM "gahr.key"> @@ -270,9 +275,11 @@ <!ENTITY pgpkey.ken SYSTEM "ken.key"> <!ENTITY pgpkey.kensmith SYSTEM "kensmith.key"> <!ENTITY pgpkey.keramida SYSTEM "keramida.key"> +<!ENTITY pgpkey.kevans SYSTEM "kevans.key"> <!ENTITY pgpkey.kevlo SYSTEM "kevlo.key"> <!ENTITY pgpkey.keymaster SYSTEM "keymaster.key"> <!ENTITY pgpkey.kib SYSTEM "kib.key"> +<!ENTITY pgpkey.kibab SYSTEM "kibab.key"> <!ENTITY pgpkey.kmoore SYSTEM "kmoore.key"> <!ENTITY pgpkey.knu SYSTEM "knu.key"> <!ENTITY pgpkey.koitsu SYSTEM "koitsu.key"> @@ -288,6 +295,7 @@ <!ENTITY pgpkey.le SYSTEM "le.key"> <!ENTITY pgpkey.leeym SYSTEM "leeym.key"> <!ENTITY pgpkey.ler SYSTEM "ler.key"> +<!ENTITY pgpkey.leres SYSTEM "leres.key"> <!ENTITY pgpkey.lesi SYSTEM "lesi.key"> <!ENTITY pgpkey.lev SYSTEM "lev.key"> <!ENTITY pgpkey.lidl SYSTEM "lidl.key"> @@ -345,6 +353,7 @@ <!ENTITY pgpkey.miwi SYSTEM "miwi.key"> <!ENTITY pgpkey.mizhka SYSTEM "mizhka.key"> <!ENTITY pgpkey.mjg SYSTEM "mjg.key"> +<!ENTITY pgpkey.mjoras SYSTEM "mjoras.key"> <!ENTITY pgpkey.mlaier SYSTEM "mlaier.key"> <!ENTITY pgpkey.mm SYSTEM "mm.key"> <!ENTITY pgpkey.mmel SYSTEM "mmel.key"> @@ -357,6 +366,7 @@ <!ENTITY pgpkey.murray SYSTEM "murray.key"> <!ENTITY pgpkey.mux SYSTEM "mux.key"> <!ENTITY pgpkey.mva SYSTEM "mva.key"> +<!ENTITY pgpkey.mw SYSTEM "mw.key"> <!ENTITY pgpkey.mwlucas SYSTEM "mwlucas.key"> <!ENTITY pgpkey.naddy SYSTEM "naddy.key"> <!ENTITY pgpkey.nate SYSTEM "nate.key"> @@ -406,6 +416,7 @@ <!ENTITY pgpkey.pho SYSTEM "pho.key"> <!ENTITY pgpkey.pi SYSTEM "pi.key"> <!ENTITY pgpkey.pirzyk SYSTEM "pirzyk.key"> +<!ENTITY pgpkey.pizzamig SYSTEM "pizzamig.key"> <!ENTITY pgpkey.pjd SYSTEM "pjd.key"> <!ENTITY pgpkey.pkelsey SYSTEM "pkelsey.key"> <!ENTITY pgpkey.plosher SYSTEM "plosher.key"> @@ -428,6 +439,7 @@ <!ENTITY pgpkey.riggs SYSTEM "riggs.key"> <!ENTITY pgpkey.rik SYSTEM "rik.key"> <!ENTITY pgpkey.rink SYSTEM "rink.key"> +<!ENTITY pgpkey.rlibby SYSTEM "rlibby.key"> <!ENTITY pgpkey.rm SYSTEM "rm.key"> <!ENTITY pgpkey.rmacklem SYSTEM "rmacklem.key"> <!ENTITY pgpkey.rmh SYSTEM "rmh.key"> @@ -515,6 +527,7 @@ <!ENTITY pgpkey.twinterg SYSTEM "twinterg.key"> <!ENTITY pgpkey.tz SYSTEM "tz.key"> <!ENTITY pgpkey.ue SYSTEM "ue.key"> +<!ENTITY pgpkey.ultima SYSTEM "ultima.key"> <!ENTITY pgpkey.ume SYSTEM "ume.key"> <!ENTITY pgpkey.ups SYSTEM "ups.key"> <!ENTITY pgpkey.uqs SYSTEM "uqs.key"> @@ -544,6 +557,7 @@ <!ENTITY pgpkey.wxs SYSTEM "wxs.key"> <!ENTITY pgpkey.xmj SYSTEM "xmj.key"> <!ENTITY pgpkey.xride SYSTEM "xride.key"> +<!ENTITY pgpkey.ygy SYSTEM "ygy.key"> <!ENTITY pgpkey.yoichi SYSTEM "yoichi.key"> <!ENTITY pgpkey.yongari SYSTEM "yongari.key"> <!ENTITY pgpkey.yzlin SYSTEM "yzlin.key"> @@ -612,16 +626,25 @@ $FreeBSD$ -->]> -<book xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:lang="zh_TW"> +<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> + <its:rules xmlns:db="http://docbook.org/ns/docbook" version="1.0"> + + <its:translateRule translate="no" selector="//db:programlisting[@role='pgpfingerprint']"/> + + <its:translateRule translate="no" selector="//db:programlisting[@role='pgpkey']"/> + + <its:translateRule translate="no" selector="//db:sect2[starts-with(@xml:id,'pgpkey-')]"/> + </its:rules> + <title>FreeBSD 使用手冊</title> <author><orgname>FreeBSD 文件計劃</orgname></author> - <pubdate xml:lang="en">$FreeBSD$</pubdate> + <pubdate its:translate="no">$FreeBSD$</pubdate> - <releaseinfo xml:lang="en">$FreeBSD$</releaseinfo> + <releaseinfo its:translate="no">$FreeBSD$</releaseinfo> <copyright xml:lang="en"> <year>1995</year> @@ -724,9 +747,9 @@ </legalnotice> <abstract> - <para>歡迎使用 FreeBSD！ 本使用手冊涵蓋範圍包括了 <emphasis>FreeBSD 11.0-RELEASE</emphasis>, <emphasis>FreeBSD 10.3-RELEASE</emphasis> 以及 <emphasis>FreeBSD 9.3-RELEASE</emphasis> 的安裝與平日操作的說明。 這份使用手冊是很多人的集體創作，而且仍然『持續不斷』的進行中，因此部份章節可能尚未仍未完成，如果您有興趣協助本計畫的話，請寄電子郵件至 <link xlink:href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-doc">FreeBSD 文件專案郵遞論壇</link>。</para> + <para>歡迎使用 FreeBSD！ 本使用手冊涵蓋範圍包括了 <emphasis>FreeBSD 11.1-RELEASE</emphasis>, <emphasis>FreeBSD 11.0-RELEASE</emphasis> 與 <emphasis>FreeBSD 10.4-RELEASE</emphasis> 的安裝與平日操作的說明。 這份使用手冊是很多人的集體創作，而且仍然『持續不斷』的進行中，因此部份章節可能尚未仍未完成，如果您有興趣協助本計畫的話，請寄電子郵件至 <link xlink:href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-doc">FreeBSD 文件專案郵遞論壇</link>。</para> - <para>在 <link xlink:href="http://www.FreeBSD.org/">FreeBSD 網站</link> 可以找到本文件的最新版本，舊版文件可從 <uri xlink:href="http://docs.FreeBSD.org/doc/">http://docs.FreeBSD.org/doc/</uri>; 取得。本文件也提供各種格式與不同壓縮方式的版本可自 <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">FreeBSD FTP 伺服器</link> 或是其中一個 <link linkend="mirrors-ftp">鏡像網站</link> 下載。 列印出來的實體書面資料可在 <link xlink:href="http://www.freebsdmall.com/">FreeBSD 商城</link> 購買。 此外，您可在 <link xlink:href="@@URL_RELPREFIX@@/search/index.html">搜尋頁面</link> 中搜尋本文件或其他文件的資料。</para> + <para>在 <link xlink:href="https://www.FreeBSD.org/">FreeBSD 網站</link> 可以找到本文件的最新版本，舊版文件可從 <uri xlink:href="https://docs.FreeBSD.org/doc/">https://docs.FreeBSD.org/doc/</uri>; 取得。本文件也提供各種格式與不同壓縮方式的版本可自 <link xlink:href="https://download.freebsd.org/ftp/doc/">FreeBSD FTP 伺服器</link> 或是其中一個 <link linkend="mirrors-ftp">鏡像網站</link> 下載。 列印出來的實體書面資料可在 <link xlink:href="http://www.freebsdmall.com/">FreeBSD 商城</link> 購買。 此外，您可在 <link xlink:href="@@URL_RELPREFIX@@/search/index.html">搜尋頁面</link> 中搜尋本文件或其他文件的資料。</para> </abstract> </info> @@ -1346,7 +1369,7 @@ <indexterm xml:lang="en"><primary>4.4BSD-Lite</primary></indexterm> - <para>FreeBSD 是一個從 4.4BSD-Lite 衍生出而能在以 Intel (x86 與 <trademark class="registered">Itanium</trademark>), AMD64, Sun <trademark class="registered">UltraSPARC</trademark> 為基礎的電腦上執行的作業系統。同時，移植到其他平台的工作也在進行中。 對於本計劃歷史的介紹，請看 <link linkend="history">FreeBSD 歷史</link>， 對於 FreeBSD 的最新版本介紹，請看 <link xlink:href="@@URL_RELPREFIX@@/releases">最新的發行版</link>。 若打算對於 FreeBSD 計劃有所貢獻的話 (程式碼、硬體、經費)， 請看 <link xlink:href="@@URL_RELPREFIX@@/doc/zh_TW.UTF-8/articles/contributing/index.html">如何對 FreeBSD 貢獻</link>。</para> + <para>FreeBSD 是一個從 4.4BSD-Lite 衍生出而能在以 Intel (x86 與 <trademark class="registered">Itanium</trademark>), AMD64, <trademark class="registered">ARM</trademark>, Sun <trademark class="registered">UltraSPARC</trademark> 為基礎的電腦上執行的作業系統。同時，移植到其他平台的工作也在進行中。 對於本計劃歷史的介紹，請看 <link linkend="history">FreeBSD 歷史</link>， 對於 FreeBSD 的最新版本介紹，請看 <link xlink:href="@@URL_RELPREFIX@@/releases">最新的發行版</link>。 若打算對於 FreeBSD 計劃有所貢獻的話 (程式碼、硬體、經費)， 請看 <link xlink:href="@@URL_RELPREFIX@@/doc/zh_TW.UTF-8/articles/contributing/index.html">如何對 FreeBSD 貢獻</link>。</para> <sect2 xml:id="os-overview"> <title>FreeBSD 能做什麼？</title> @@ -1623,13 +1646,9 @@ </listitem> <listitem> - <para xml:lang="en"><link xlink:href="http://www.sandvine.com/">Sandvine</link>; - <indexterm xml:lang="en"> + <para><link xlink:href="http://www.sandvine.com/">Sandvine</link>; <indexterm> <primary>Sandvine</primary> - </indexterm> - Sandvine uses FreeBSD as the basis of their - high performance real-time network processing platforms - that make up their intelligent network policy control - products.</para> + </indexterm> - Sandvine 使用 FreeBSD 作為它的高性能即時網路處理平台的基礎來建立它們的智慧網路策略控制產品。</para> </listitem> <listitem> @@ -1732,7 +1751,7 @@ </listitem> <listitem> - <para><link xlink:href="http://www.pcbsd.org/">TrueOS</link>; <indexterm> + <para><link xlink:href="https://www.trueos.org">TrueOS</link>; <indexterm> <primary>TrueOS</primary> </indexterm> - 訂製版本的 FreeBSD，裝備了給桌面使用者使用的圖型化工具來展示 FreeBSD 強大的功能給所有使用者，專門設計來緩解使用者在 Windows 與 OS X 間的過渡。</para> </listitem> @@ -2029,7 +2048,7 @@ </varlistentry> </variablelist> - <para>此外，可在下列網址找到最新版 (也是更新最頻繁的版本)：<uri xlink:href="http://www.FreeBSD.org/">http://www.FreeBSD.org/</uri>。</para>; + <para>此外，可在下列網址找到最新版 (也是更新最頻繁的版本)：<uri xlink:href="https://www.FreeBSD.org/">https://www.FreeBSD.org/</uri>。</para>; </sect2> </sect1> </chapter> @@ -2167,7 +2186,7 @@ <listitem> <para>桌面電腦與筆記型電腦最常見的處理器類型，運用在近代的系統。<trademark class="registered">Intel</trademark> 稱該類型為 <acronym>Intel64</acronym>，其他製造商則稱該類型為 <acronym>x86-64</acronym>。</para> - <para>與 amd64 相容的處理器包含：<trademark>AMD Athlon</trademark>64, <trademark>AMD Opteron</trademark>, 多核心 <trademark class="registered">Intel</trademark> <trademark>Xeon</trademark> 以及 <trademark class="registered">Intel</trademark> <trademark>Core</trademark> 2 與之後的處理器。</para> + <para>與 amd64 相容的處理器範例包含：<trademark>AMD Athlon</trademark>64, <trademark>AMD Opteron</trademark>, 多核心 <trademark class="registered">Intel</trademark> <trademark>Xeon</trademark> 以及 <trademark class="registered">Intel</trademark> <trademark>Core</trademark> 2 與之後的處理器。</para> </listitem> </varlistentry> @@ -2287,9 +2306,9 @@ <step> <title>檢查 FreeBSD 勘誤表</title> - <para>儘管 FreeBSD Project 努力確保每個 FreeBSD 發行版能夠儘可能地穩定，但錯誤偶爾還是會悄悄出現，並有極小的可能會發生影響安裝流程的錯誤，當這些問題被發現並修正後，會被紀錄在 FreeBSD 網站的 FreeBSD 勘誤表 (<link xlink:href="@@URL_RELPREFIX@@/releases/11.0R/errata.html">http://www.freebsd.org/releases/11.0R/errata.html</link>) 安裝前先檢查勘誤表，以確保沒有會影響到安裝的問題。</para> + <para>儘管 FreeBSD 計劃努力確保每個 FreeBSD 發行版能夠儘可能地穩定，但錯誤偶爾還是會悄悄出現，並有極小的可能會發生影響安裝流程的錯誤，當這些問題被發現並修正後，會被紀錄在 FreeBSD 網站的 FreeBSD 勘誤表 (<link xlink:href="@@URL_RELPREFIX@@/releases/11.1R/errata.html">https://www.freebsd.org/releases/11.1R/errata.html</link>) 安裝前先檢查勘誤表，以確保沒有會影響到安裝的問題。</para> - <para>所有發行版的資訊和勘誤表可以在 FreeBSD 網站的發行資訊找到 (<link xlink:href="@@URL_RELPREFIX@@/releases/index.html">http://www.freebsd.org/releases/index.html</link>)。</para>; + <para>所有發行版的資訊和勘誤表可以在 FreeBSD 網站的發行資訊找到 (<link xlink:href="@@URL_RELPREFIX@@/releases/index.html">https://www.freebsd.org/releases/index.html</link>)。</para>; </step> </procedure> @@ -3696,7 +3715,7 @@ Starting sshd.</screen> </indexterm> <para>本節涵蓋基礎的安裝疑難排解，例如一些已有人回報的常見問題。</para> - <para>查看該 FreeBSD 版本的 Hardware Notes (<link xlink:href="@@URL_RELPREFIX@@/releases/index.html">http://www.freebsd.org/releases/index.html</link>) 文件來確認是否支援該硬體。若確定有支援該硬體但仍然卡住或發生其他問題，請依照 <xref linkend="kernelconfig"/> 的指示編譯自訂核心來加入未在 <filename>GENERIC</filename> 核心的裝置。預設的核心會假設大部份的硬體裝置會使用原廠預設的 <acronym>IRQ</acronym>s, <acronym>I/O</acronym> 位址，及 <acronym>DMA</acronym> 通道，若硬體已經被重新設定過，自訂的核心設定檔可以告訴 FreeBSD 到那找到這些裝置。</para> + <para>查看該 FreeBSD 版本的 Hardware Notes (<link xlink:href="@@URL_RELPREFIX@@/releases/index.html">https://www.freebsd.org/releases/index.html</link>) 文件來確認是否支援該硬體。若確定有支援該硬體但仍然卡住或發生其他問題，請依照 <xref linkend="kernelconfig"/> 的指示編譯自訂核心來加入未在 <filename>GENERIC</filename> 核心的裝置。預設的核心會假設大部份的硬體裝置會使用原廠預設的 <acronym>IRQ</acronym>s, <acronym>I/O</acronym> 位址，及 <acronym>DMA</acronym> 通道，若硬體已經被重新設定過，自訂的核心設定檔可以告訴 FreeBSD 到那找到這些裝置。</para> <note> <para>部份安裝問題可以透過更各種硬體元件的韌體來避免或緩解，特別是主機板。主機板的韌體通常稱為 <acronym>BIOS</acronym>，大部份主機板與電腦製造商會有網站可以取得升級程式與升級資訊。</para> @@ -6102,7 +6121,7 @@ Swap: 2048M Total, 2048M Free <itemizedlist> <listitem> - <para>FreeBSD 網站有維護一份可搜尋的最新應用程式清單，在 <link xlink:href="@@URL_RELPREFIX@@/ports/index.html">http://www.FreeBSD.org/ports/</link> 可以依應用程式名稱或軟體分類來搜尋 Port。</para> + <para>FreeBSD 網站有維護一份可搜尋的最新應用程式清單，在 <link xlink:href="@@URL_RELPREFIX@@/ports/index.html">https://www.FreeBSD.org/ports/</link> 可以依應用程式名稱或軟體分類來搜尋 Port。</para> </listitem> <listitem> @@ -6918,18 +6937,18 @@ ports-mgmt/pkg <para>雖然可以同時使用自訂的檔案庫與官方檔案庫，但有時關閉官方檔案庫會有幫助。這可以透過建立一個設定檔覆蓋並關閉官方的設定檔來完成。建立 <filename>/usr/local/etc/pkg/repos/FreeBSD.conf</filename> 包含以下內容：</para> - <screen xml:lang="en">FreeBSD: { + <programlisting xml:lang="en">FreeBSD: { enabled: no -}</screen> +}</programlisting> <para>通常最簡單要提供 poudriere 檔案庫給客戶端的方式是透過 HTTP。安裝一個網頁伺服器來提供套件目錄，通常會像：<filename>/usr/local/poudriere/data/packages/<replaceable>10amd64</replaceable></filename>，其中 <filename>10amd64</filename> 是編譯的名稱。</para> <para>若要連往套件檔案庫的 URL 是：<literal>http://pkg.example.com/10amd64</literal>，則 <filename>/usr/local/etc/pkg/repos/custom.conf</filename> 的檔案庫設定檔為：</para> - <screen xml:lang="en">custom: { + <programlisting xml:lang="en">custom: { url: "<replaceable>http://pkg.example.com/10amd64</replaceable>", enabled: yes, -}</screen> +}</programlisting> </sect2> </sect1> @@ -7931,7 +7950,7 @@ DisplayManager.requestPort: 0</screen> <title xml:lang="en">GNOME</title> <indexterm xml:lang="en"><primary>GNOME</primary></indexterm> - <para><application>GNOME</application> 是一個擁有友善使用者介面的的桌面環境，它包括用於啟動應用程式和顯示狀態的面板、一系列工具與應用程序及一套可讓應用程式更容易進行合作、相互一致的協定。更多有關 FreeBSD <application>GNOME</application> 的訊息可在 <link xlink:href="http://www.FreeBSD.org/gnome">http://www.FreeBSD.org/gnome</link>; 取得，該網站包含了有關在 FreeBSD 安裝、設定和管理 <application>GNOME</application> 的額外文件。</para> + <para><application>GNOME</application> 是一個擁有友善使用者介面的的桌面環境，它包括用於啟動應用程式和顯示狀態的面板、一系列工具與應用程序及一套可讓應用程式更容易進行合作、相互一致的協定。更多有關 FreeBSD <application>GNOME</application> 的訊息可在 <link xlink:href="https://www.FreeBSD.org/gnome">https://www.FreeBSD.org/gnome</link>; 取得，該網站包含了有關在 FreeBSD 安裝、設定和管理 <application>GNOME</application> 的額外文件。</para> <para>這套桌面環境可以從套件安裝：</para> @@ -8471,7 +8490,7 @@ EndSection</programlisting> <secondary>web</secondary> </indexterm> - <para>在 FreeBSD 中並未預先安裝好網頁瀏覽器。 但在 Port 套件集中的 <link xlink:href="http://www.FreeBSD.org/ports/www.html">www</link>; 分類中有許多瀏覽器可以採 Binary 套件安裝或自 Port 套件集編譯的方式安裝。</para> + <para>在 FreeBSD 中並未預先安裝好網頁瀏覽器。 但在 Port 套件集中的 <link xlink:href="https://www.FreeBSD.org/ports/www.html">www</link>; 分類中有許多瀏覽器可以採 Binary 套件安裝或自 Port 套件集編譯的方式安裝。</para> <para><application>KDE</application> 和 <application>GNOME</application> 桌面環境都有提供自有的 HTML 瀏覽器。請參考 <xref linkend="x11-wm"/> 來了解更多有關如何設定完整桌面環境的資訊。</para> @@ -8560,7 +8579,7 @@ EndSection</programlisting> <para>編譯 Port 時使用預設設定選項。</para> - <para>安裝完成時，啟動 <application>firefox</application>，在網址列輸入 <literal>about:plugins</literal> 並按 <keycap>Enter</keycap> 鍵。 會出現一個頁面列出已安裝的附加元件。 <application><trademark>Java</trademark></application> 附加元件應該會列在其中。</para> + <para>安裝完成後，啟動 <application>firefox</application>，在網址列輸入 <literal>about:plugins</literal> 並按 <keycap>Enter</keycap> 鍵，便會出現一個列出已安裝附加元件的頁面，清單中應該要有 <application><trademark>Java</trademark></application> 附加元件。</para> <para>若瀏覽器無法找到附加元件，每位使用者則須執行以下指令並重新執行瀏覽器：</para> @@ -8586,7 +8605,7 @@ EndSection</programlisting> </step> <step> - <para>自 Port 安裝 <package role="port">www/linux-c6-flashplugin11</package> ，受到授權條款的限制，該套件無 Binary 版本。</para> + <para>自 Port 安裝 <package role="port">www/linux-flashplayer</package> ，受到授權條款的限制，該套件無 Binary 版本。</para> </step> <step> @@ -8667,7 +8686,7 @@ EndSection</programlisting> <screen xml:lang="en"><prompt>#</prompt> <userinput>pkg install kwebkitpart</userinput></screen> - <para>由 Port 套件集安裝：</para> + <para>從 Port 套件集安裝：</para> <screen xml:lang="en"><prompt>#</prompt> <userinput>cd /usr/ports/www/kwebkitpart</userinput> <prompt>#</prompt> <userinput>make install clean</userinput></screen> @@ -8841,7 +8860,7 @@ EndSection</programlisting> <screen xml:lang="en"><prompt>#</prompt> <userinput>cd /usr/ports/graphics/gimp</userinput> <prompt>#</prompt> <userinput>make install clean</userinput></screen> - <para> 在 Port 套件集的 graphics 分類 (<link xlink:href="http://www.FreeBSD.org/ports/graphics.html">freebsd.org/ports/graphics.html</link>) 下也包含了許多 <application>GIMP</application> 相關的附加元件，說明檔及使用手冊。</para> + <para>在 Port 套件集的 graphics 分類 (<link xlink:href="https://www.FreeBSD.org/ports/graphics.html">freebsd.org/ports/graphics.html</link>) 下也包含了許多 <application>GIMP</application> 相關的附加元件，說明檔及使用手冊。</para> </sect2> @@ -8907,7 +8926,7 @@ EndSection</programlisting> <screen xml:lang="en"><prompt>#</prompt> <userinput>pkg install libreoffice</userinput></screen> - <para>Port 套件集的編輯器分類 (<link xlink:href="http://www.FreeBSD.org/ports/editors.html">freebsd.org/ports/editors.html</link>) 中含有數個 <application>LibreOffice</application> 的語系。安裝在地化套件時，請替換 <literal>libreoffice</literal> 為在地化套件的名稱。</para> + <para>Port 套件集的編輯器分類 (<link xlink:href="https://www.FreeBSD.org/ports/editors.html">freebsd.org/ports/editors.html</link>) 中含有數個 <application>LibreOffice</application> 的語系。安裝在地化套件時，請替換 <literal>libreoffice</literal> 為在地化套件的名稱。</para> <para>套件安裝之後，輸入以下指令來執行 <application>LibreOffice</application>：</para> @@ -8921,7 +8940,7 @@ EndSection</programlisting> <prompt>#</prompt> <userinput>make install clean</userinput></screen> <note> - <para>要編譯在地化版本，則需 <command>cd</command> 進入想要的語言 Port 目錄。支援的語言可在 Port 套件集的編輯器分類 (<link xlink:href="http://www.FreeBSD.org/ports/editors.html">freebsd.org/ports/editors.html</link>) 中找到。</para> + <para>要編譯在地化版本，則需 <command>cd</command> 進入想要的語言 Port 目錄。支援的語言可在 Port 套件集的編輯器分類 (<link xlink:href="https://www.FreeBSD.org/ports/editors.html">freebsd.org/ports/editors.html</link>) 中找到。</para> </note> </sect2> </sect1> @@ -9307,7 +9326,7 @@ EndSection</programlisting> <indexterm xml:lang="en"><primary>PCI</primary></indexterm> <indexterm xml:lang="en"><primary>sound cards</primary></indexterm> - <para>開始設定之前，必須先知道你的音效卡型號、晶片為何。 FreeBSD 支援許多種音效卡，請檢查支援的音效硬體表 <link xlink:href="http://www.FreeBSD.org/releases/11.0R/hardware.html">Hardware Notes</link>，以確認你的音效卡是否支援以及如何在 FreeBSD 上驅動。</para> + <para>開始設定之前，必須先知道你的音效卡型號、晶片為何。 FreeBSD 支援許多種音效卡，請檢查支援的音效硬體表 <link xlink:href="https://www.FreeBSD.org/releases/11.1R/hardware.html">Hardware Notes</link>，以確認你的音效卡是否支援以及如何在 FreeBSD 上驅動。</para> <indexterm xml:lang="en"> <primary>kernel</primary> @@ -9673,7 +9692,7 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digital> at cad provides an alternative, command-line <acronym>MP3</acronym> player. Once installed, specify the <acronym>MP3</acronym> file to play on the command line. If the system has multiple - audio devices, the sound device can also be specifed:</para> + audio devices, the sound device can also be specified:</para> <screen xml:lang="en"><prompt>#</prompt> <userinput>mpg123 <replaceable>-a /dev/dsp1.0 Foobar-GreatestHits.mp3</replaceable></userinput> High Performance MPEG 1.0/2.0/2.5 Audio Player for Layers 1, 2 and 3 @@ -10473,7 +10492,7 @@ bktr0: Pinnacle/Miro TV, Philips SECAM tuner.</program <screen xml:lang="en"><prompt>#</prompt> <userinput>pkg install mythtv</userinput></screen> - <para>或由 Port 套件集安裝：</para> + <para>或從 Port 套件集安裝：</para> <screen xml:lang="en"><prompt>#</prompt> <userinput>cd /usr/ports/multimedia/mythtv</userinput> <prompt>#</prompt> <userinput>make install</userinput></screen> @@ -10908,11 +10927,10 @@ ath0@pci0:3:0:0: class=0x020000 card=0x058a1014 <para>在 <citerefentry><refentrytitle>man</refentrytitle><manvolnum>1</manvolnum></citerefentry> 指令加上 <option>-k</option> 旗標可提供有用的資訊，例如，這可列出有包含指定裝置品牌或名稱的手冊頁面清單：</para> - <screen xml:lang="en"><prompt>#</prompt> <userinput>man -k <replaceable>Atheros</replaceable></userinput></screen> + <screen xml:lang="en"><prompt>#</prompt> <userinput>man -k <replaceable>Atheros</replaceable></userinput> +ath(4) - Atheros IEEE 802.11 wireless network driver +ath_hal(4) - Atheros Hardware Access Layer (HAL)</screen> - <programlisting xml:lang="en">ath(4) - Atheros IEEE 802.11 wireless network driver -ath_hal(4) - Atheros Hardware Access Layer (HAL)</programlisting> - <para>準備好硬體清單之後，參考該清單來確認已安裝的硬體驅動程式在編輯自訂核心設定時沒有被移除。</para> </sect1> @@ -12951,9 +12969,7 @@ lp: <para>在 FreeBSD 安裝基本的 <trademark class="registered">Linux</trademark> 程式庫和 Binary 最簡單的方式是安裝 <package>emulators/linux_base-c6</package> 套件或是 Port 。要安裝 Port：</para> - <screen xml:lang="en"><prompt>#</prompt> <userinput>printf "compat.linux.osrelease=2.6.18\n" >> /etc/sysctl.conf</userinput> -<prompt>#</prompt> <userinput>sysctl compat.linux.osrelease=2.6.18</userinput> -<prompt>#</prompt> <userinput>pkg install emulators/linux_base-c6</userinput></screen> + <screen xml:lang="en"><prompt>#</prompt> <userinput>pkg install emulators/linux_base-c6</userinput></screen> <para>要在開機時開啟 <trademark class="registered">Linux</trademark> 相容性，可以加入這行到 <filename>/etc/rc.conf</filename>：</para> @@ -12963,7 +12979,10 @@ lp: <indexterm><primary>核心選項</primary> <secondary>COMPAT_LINUX</secondary></indexterm> - <para>想要靜態連結 <trademark class="registered">Linux</trademark> Binary 相容性到自訂核心的使用者應加入 <literal>options COMPAT_LINUX</literal> 到自訂核心設定檔。 編譯並安裝新核心的方法，如 <xref linkend="kernelconfig"/> 所述。</para> + <para xml:lang="en">Since the Linux binary compatibility layer has gained support + for running both 32- and 64-bit Linux binaries (on 64-bit x86 hosts), + it is no longer possible to link the emulation functionality statically + into a custom kernel.</para> <sect2 xml:id="linuxemu-libs-manually"> <title>手動安裝其他程式庫</title> @@ -14211,7 +14230,7 @@ run_rc_command "$1"</programlisting> <programlisting xml:lang="en"># /etc/crontab - root's crontab for FreeBSD # -# $FreeBSD$ +# <phrase its:translate="no">$FreeBSD$</phrase> # <co xml:id="co-comments"/> SHELL=/bin/sh PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin <co xml:id="co-env"/> @@ -14809,7 +14828,7 @@ ifconfig_fxp0_alias7="inet 202.0.75.20 netmask 255.255 <para>此設定檔中一行代表一個動作，每一行的格式皆為一個選擇器欄位 (Selector field) 接著一個動作欄位 (Action field)。選擇器欄位的格式為 <replaceable>facility.level</replaceable> 可以用來比對來自 <replaceable>facility</replaceable> 於層級 <replaceable>level</replaceable> 或更高層的日誌訊息，也可以在層級前加入選擇性的比對旗標來更確切的指定記錄的內容。同樣一個動作可以使用多個選擇器欄位並使用分號 (<literal>;</literal>) 來分隔。用 <literal>*</literal> 可以比對任何東西。動作欄位可用來指定傳送日誌訊息的目標，如一個檔案或遠端日誌主機。範例為以下為 FreeBSD 預設的 <filename>syslog.conf</filename>：</para> - <programlisting xml:lang="en"># $FreeBSD$ + <programlisting xml:lang="en"># <phrase its:translate="no">$FreeBSD$</phrase> # # Spaces ARE valid field separators in this file. However, # other *nix-like systems still insist on using tabs as field @@ -14889,7 +14908,7 @@ cron.* /var/l <para><application>newsyslog</application> 會讀取其設定檔 <filename>/etc/newsyslog.conf</filename> 來決定其要採取的動作，每個要由 <application>newsyslog</application> 所管理的日誌檔案會在此設定檔中設定一行，每一行要說明檔案的擁有者、權限、何時要翻轉該檔案、選用的日誌翻轉旗標，如：壓縮，以及日誌翻轉時要通知的程式。以下為 FreeBSD 的預設設定：</para> <programlisting xml:lang="en"># configuration file for newsyslog -# $FreeBSD$ +# <phrase its:translate="no">$FreeBSD$</phrase> # # Entries which do not specify the '/pid_file' field will cause the # syslogd process to be signalled when that log file is rotated. This @@ -15306,7 +15325,7 @@ nameserver 147.11.100.30</programlisting> <para><filename>/etc/hosts</filename> 是簡單的文字資料庫，會與 <acronym>DNS</acronym> 及 <acronym>NIS</acronym> 一併使用來提供主機名稱與 <acronym>IP</acronym> 位址的對應。可將透過 <acronym>LAN</acronym> 所連結的在地電腦項目加入到這個檔案做最簡單的命名，來替代設定一個 <citerefentry><refentrytitle>named</refentrytitle><manvolnum>8</manvolnum></citerefentry> 伺服器。除此之外 <filename>/etc/hosts</filename> 可以用來提供本地的網際網路名稱記錄，來減少常用名稱向外部 <acronym>DNS</acronym> 伺服器查詢的需求。</para> - <programlisting xml:lang="en"># $FreeBSD$ + <programlisting xml:lang="en"># <phrase its:translate="no">$FreeBSD$</phrase> # # # Host Database @@ -17505,7 +17524,7 @@ Enter new password:</screen> <para><firstterm>rootkit</firstterm> 指的是嘗試未經授權取得系統 <systemitem class="username">root</systemitem> 存取權的軟體。一旦安裝之後，這個惡意軟體將可以光明正大的開啟給另一個給攻擊者進入的大門。現實上，一但系統已被 rootkit 滲透且執行了搜索動作之後，該系統就應該從頭重新安裝，因為即使非常謹真的資安或系統工程式也可能會遺漏攻擊者留下的動西。</para> - <para>rootkit 所做過的事可提供管理者一個非常有用的資訊：一但偵測到，便代表某處已經被滲透，但這類的應用程式躲藏的非常好，本節將會示範一個可以用來偵測 rootkit 的工具，<package>security/rkhunter</package>。</para> + <para>rootkit 對管理者而言唯一有幫助的是：一但偵測到，便代表某處已經被滲透，但這類型的應用程式躲藏的非常好，本節將會示範一個可以用來偵測 rootkit 的工具，<package>security/rkhunter</package>。</para> <para>安裝此套件或 Port 之後，系統便可使用以下指令檢查。該指令提供許多資訊且會需要手動按下 <keycap>ENTER</keycap> 確認：</para> @@ -18270,9 +18289,7 @@ kadmin><userinput> exit</userinput></screen> <programlisting xml:lang="en">GSSAPIAuthentication yes</programlisting> - <para xml:lang="en">After making this change, <citerefentry><refentrytitle>sshd</refentrytitle><manvolnum>8</manvolnum></citerefentry> must be restared - for the new configuration to take effect: - <command>service sshd restart</command>.</para> + <para>做完了這個變更之後，必須重新啟動 <citerefentry><refentrytitle>sshd</refentrytitle><manvolnum>8</manvolnum></citerefentry> 來使新的設定值生效：<command>service sshd restart</command>。</para> </sect2> <sect2> @@ -18941,9 +18958,7 @@ Connection closed by foreign host.</screen> information on the <acronym>IPsec</acronym> subsystem in FreeBSD.</para> - <para xml:lang="en">To add <acronym>IPsec</acronym> support to the kernel, add - the following options to the custom kernel configuration file - and rebuild the kernel using the instructions in <xref linkend="kernelconfig"/>:</para> + <para>在 FreeBSD 11 與之後的版本預設會開啟 <acronym>IPsec</acronym> 功能，先前版本的 FreeBSD 可在自訂核心設定檔中加入以下選項然後依 <xref linkend="kernelconfig"/> 的指示來重新編譯核心：</para> <indexterm><primary>核心選項</primary> <secondary>IPSEC</secondary></indexterm> @@ -19072,10 +19087,10 @@ round-trip min/avg/max/stddev = 28.106/94.594/154.524/ network. The following commands will achieve this goal:</para> - <screen xml:lang="en"><prompt>#</prompt> <userinput>corp-net# route add <replaceable>10.0.0.0 10.0.0.5 255.255.255.0</replaceable></userinput> -<prompt>#</prompt> <userinput>corp-net# route add net <replaceable>10.0.0.0: gateway 10.0.0.5</replaceable></userinput> -<prompt>#</prompt> <userinput>priv-net# route add <replaceable>10.246.38.0 10.246.38.1 255.255.255.0</replaceable></userinput> -<prompt>#</prompt> <userinput>priv-net# route add host <replaceable>10.246.38.0: gateway 10.246.38.1</replaceable></userinput></screen> + <screen xml:lang="en">corp-net<prompt>#</prompt> <userinput>route add <replaceable>10.0.0.0 10.0.0.5 255.255.255.0</replaceable></userinput> +corp-net<prompt>#</prompt> <userinput>route add net <replaceable>10.0.0.0: gateway 10.0.0.5</replaceable></userinput> +priv-net<prompt>#</prompt> <userinput>route add <replaceable>10.246.38.0 10.246.38.1 255.255.255.0</replaceable></userinput> +priv-net<prompt>#</prompt> <userinput>route add host <replaceable>10.246.38.0: gateway 10.246.38.1</replaceable></userinput></screen> <para xml:lang="en">At this point, internal machines should be reachable from each gateway as well as from machines behind the gateways. @@ -19386,8 +19401,8 @@ The key's randomart image is: <para>要在 Shell 使用 <command>ssh-agent</command>，使用 Shell 做為參數來啟動 <command>ssh-agent</command>。執行 <command>ssh-add</command> 來加入識別碼，然後輸入私鑰的密碼。使用者將可使用 <command>ssh</command> 連線到任何有安裝對應公鑰的主機，例如：</para> - <screen xml:lang="en"><prompt>%</prompt> ssh-agent <replaceable>csh</replaceable> -<prompt>%</prompt> ssh-add + <screen xml:lang="en"><prompt>%</prompt> <userinput>ssh-agent <replaceable>csh</replaceable></userinput> +<prompt>%</prompt> <userinput>ssh-add</userinput> Enter passphrase for key '/usr/home/user/.ssh/id_rsa': <co xml:id="co-ssh-agent-passphrase"/> Identity added: /usr/home/user/.ssh/id_rsa (/usr/home/user/.ssh/id_rsa) <prompt>%</prompt></screen> @@ -19777,7 +19792,7 @@ drwxr-xr-x 2 robert robert 512 Nov 10 11:54 public_ <programlisting xml:lang="en">Affected package: cups-base-1.1.22.0_1 Type of problem: cups-base -- HPGL buffer overflow vulnerability. -Reference: <http://www.FreeBSD.org/ports/portaudit/40a3bca2-6809-11d9-a9e7-0001020eed82.html> +Reference: <https://www.FreeBSD.org/ports/portaudit/40a3bca2-6809-11d9-a9e7-0001020eed82.html> 1 problem(s) in your installed packages found. @@ -19917,7 +19932,7 @@ b) Execute the following commands as root: # patch < /path/to/patch Recompile the operating system using buildworld and installworld as -described in <URL:http://www.FreeBSD.org/handbook/makeworld.html>. +described in <URL:https://www.FreeBSD.org/handbook/makeworld.html>. Restart the applicable daemons, or reboot the system. @@ -26311,7 +26326,7 @@ scsibus1: <para>在安全的地方保存這份列印結果與安裝媒體的複本，在緊急還原時可能會需要，接著開機進入安裝媒體並選擇 <literal>Live CD</literal> 以存取救援 Shell (Rescue shell)，這個救援模式可以用來檢視目前系統的狀態，若有需要，可重新格式化磁碟然後自備份還原資料。</para> <note> - <para>FreeBSD/i386 10.3-RELEASE 的安裝媒體未含救援 Shell，針對該版本，可改自 <uri xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/10.3/FreeBSD-10.3-RELEASE-i386-livefs.iso">ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/10.3/FreeBSD-10.3-RELEASE-i386-livefs.iso</uri>; 下載 <acronym>CD</acronym> 映像檔並燒錄。</para> + <para>FreeBSD/i386 10.4-RELEASE 的安裝媒體未含救援 Shell，針對該版本，可改自 <uri xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/10.4/FreeBSD-10.4-RELEASE-i386-livefs.iso">ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/10.4/FreeBSD-10.4-RELEASE-i386-livefs.iso</uri>; 下載 Livefs <acronym>CD</acronym> 映像檔並燒錄。</para> </note> <para>然後，測試救援 Shell 下的備份。記錄下整個程序，將這份記錄隨媒體、列印結果、備份檔一併保存，這份記錄可以避免在緊張壓力下做緊急還原時因不慎造成備份的毀壞。</para> @@ -26860,7 +26875,8 @@ Quotas for user test: <acronym>UFS</acronym> file system, set the sector_size to 2048:</para> - <screen xml:lang="en"><prompt>#</prompt> <userinput>gbde init /dev/ad4s1c -i -L /etc/gbde/ad4s1c.lock</userinput># $FreeBSD$ + <screen xml:lang="en"><prompt>#</prompt> <userinput>gbde init /dev/ad4s1c -i -L /etc/gbde/ad4s1c.lock</userinput> +# <phrase its:translate="no">$FreeBSD$</phrase> # # Sector size is the smallest unit of data which can be read or written. # Making it too small decreases performance and decreases available space. @@ -27292,7 +27308,7 @@ geli_da2_flags="-k /root/<replaceable>da2.key</replace </varlistentry> </variablelist> - <para xml:lang="en">This example configures an encryped swap partition using + <para xml:lang="en">This example configures an encrypted swap partition using the Blowfish algorithm with a key length of 128 bits and a sectorsize of 4 kilobytes:</para> @@ -30500,7 +30516,7 @@ errors: No known data errors</screen> <sect2 xml:id="zfs-zpool-import"> <title>匯入與匯出儲存池</title> - <para>儲存池在移動到其他系統之前需要做匯出 (<emphasis>Export</emphasis>)，會卸載所有的資料集，然後標記每個裝置為已匯出，為了避免被其他磁碟子系統存取，因此仍會鎖定這些裝置。這個動作讓儲存池可以在支援 <acronym>ZFS</acronym> 的其他機器、其他作業系統做匯入 (<emphasis>Import</emphasis>)，甚至是不同的硬體架構 (有一些注意事項，請參考 <citerefentry><refentrytitle>zpool</refentrytitle><manvolnum>8</manvolnum></citerefentry>)。當資料集有被開啟的檔案，可使用 <command> zpool export -f</command> 來強制匯出儲存池，使用這個指令需要小心，資料集是被強制卸載的，因此有可能造成在該資料集開啟檔案的應用程式發生無法預期的結果。</para> + <para>儲存池在移動到其他系統之前需要做匯出 (<emphasis>Export</emphasis>)，會卸載所有的資料集，然後標記每個裝置為已匯出，為了避免被其他磁碟子系統存取，因此仍會鎖定這些裝置。這個動作讓儲存池可以在支援 <acronym>ZFS</acronym> 的其他機器、其他作業系統做匯入 (<emphasis>Import</emphasis>)，甚至是不同的硬體架構 (有一些注意事項，請參考 <citerefentry><refentrytitle>zpool</refentrytitle><manvolnum>8</manvolnum></citerefentry>)。當資料集有被開啟的檔案，可使用 <command>zpool export -f</command> 來強制匯出儲存池，使用這個指令需要小心，資料集是被強制卸載的，因此有可能造成在該資料集開啟檔案的應用程式發生無法預期的結果。</para> <para>匯出未使用的儲存池：</para> @@ -30888,6 +30904,37 @@ NAME PROPERTY VALUE SOURCE tank custom:costcenter - - <prompt>#</prompt> <userinput>zfs get all <replaceable>tank</replaceable> | grep <replaceable>custom</replaceable>:<replaceable>costcenter</replaceable></userinput> <prompt>#</prompt></screen> + + <sect3 xml:id="zfs-zfs-set-share"> + <title>取得與設定共享屬性</title> + + <para xml:lang="en">Two commonly used and useful dataset properties are the + <acronym>NFS</acronym> and <acronym>SMB</acronym> share + options. Setting these define if and how + <acronym>ZFS</acronym> datasets may be shared on the network. + At present, only setting sharing via <acronym>NFS</acronym> is + supported on FreeBSD. To get the current status of + a share, enter:</para> + + <screen xml:lang="en"><prompt>#</prompt> <userinput>zfs get sharenfs <replaceable>mypool/usr/home</replaceable></userinput> +NAME PROPERTY VALUE SOURCE +mypool/usr/home sharenfs on local +<prompt>#</prompt> <userinput>zfs get sharesmb <replaceable>mypool/usr/home</replaceable></userinput> +NAME PROPERTY VALUE SOURCE +mypool/usr/home sharesmb off local</screen> + + <para xml:lang="en">To enable sharing of a dataset, enter:</para> + + <screen xml:lang="en"><prompt>#</prompt> <userinput> zfs set sharenfs=on <replaceable>mypool/usr/home</replaceable></userinput></screen> + + <para xml:lang="en">It is also possible to set additional options for sharing + datasets through <acronym>NFS</acronym>, such as + <option>-alldirs</option>, <option>-maproot</option> and + <option>-network</option>. To set additional options to a + dataset shared through NFS, enter:</para> + + <screen xml:lang="en"><prompt>#</prompt> <userinput> zfs set sharenfs="-alldirs,-maproot=<replaceable>root</replaceable>,-network=<replaceable>192.168.1.0/24</replaceable>" <replaceable>mypool/usr/home</replaceable></userinput></screen> + </sect3> </sect2> <sect2 xml:id="zfs-zfs-snapshot"> @@ -31036,17 +31083,16 @@ mypool/var/tmp 262K 93.2G 1 mypool/var/tmp@my_recursive_snapshot 88K - 152K - mypool/var/tmp@after_cp 53.5K - 118K - mypool/var/tmp@diff_snapshot 0 - 120K - -<prompt>%</prompt> <userinput>ls /var/tmp</userinput> -passwd passwd.copy -<prompt>%</prompt> <userinput>rm /var/tmp/passwd*</userinput> -<prompt>%</prompt> <userinput>ls /var/tmp</userinput> -vi.recover -<prompt>%</prompt></screen> +<prompt>#</prompt> <userinput>ls /var/tmp</userinput> +passwd passwd.copy vi.recover +<prompt>#</prompt> <userinput>rm /var/tmp/passwd*</userinput> +<prompt>#</prompt> <userinput>ls /var/tmp</userinput> +vi.recover</screen> <para>在此時，使用者發現到刪除了太多檔案並希望能夠還原。<acronym>ZFS</acronym> 提供了簡單的方可以取回檔案，便是使用還原 (Rollback)，但這只在有定期對重要的資料使用快照時可用。要拿回檔案並從最後一次快照重新開始，可執行以下指令：</para> <screen xml:lang="en"><prompt>#</prompt> <userinput>zfs rollback <replaceable>mypool/var/tmp@diff_snapshot</replaceable></userinput> -<prompt>%</prompt> <userinput>ls /var/tmp</userinput> +<prompt>#</prompt> <userinput>ls /var/tmp</userinput> passwd passwd.copy vi.recover</screen> <para>還原操作會將資料集還原為最後一次快照的狀態。這也可以還原到更早之前，有其他在其之後建立的快照。要這麼做時，<acronym>ZFS</acronym> 會發出這個警告：</para> @@ -31068,7 +31114,7 @@ mypool/var/tmp@diff_snapshot</screen> <prompt>#</prompt> <userinput>zfs list -rt snapshot <replaceable>mypool/var/tmp</replaceable></userinput> NAME USED AVAIL REFER MOUNTPOINT mypool/var/tmp@my_recursive_snapshot 8K - 152K - -<prompt>%</prompt> <userinput>ls /var/tmp</userinput> +<prompt>#</prompt> <userinput>ls /var/tmp</userinput> vi.recover</screen> <para>可從 <command>zfs list -t snapshot</command> 的結果來確認 <command>zfs rollback -r</command> 會移除的快照。</para> @@ -31082,16 +31128,16 @@ vi.recover</screen> <screen xml:lang="en"><prompt>#</prompt> <userinput>zfs get snapdir <replaceable>mypool/var/tmp</replaceable></userinput> NAME PROPERTY VALUE SOURCE mypool/var/tmp snapdir hidden default -<prompt>%</prompt> <userinput>ls -a /var/tmp</userinput> +<prompt>#</prompt> <userinput>ls -a /var/tmp</userinput> . .. passwd vi.recover <prompt>#</prompt> <userinput>zfs set snapdir=visible <replaceable>mypool/var/tmp</replaceable></userinput> -<prompt>%</prompt> <userinput>ls -a /var/tmp</userinput> +<prompt>#</prompt> <userinput>ls -a /var/tmp</userinput> . .. .zfs passwd vi.recover</screen> <para>要還原個別檔案到先前的狀態非常簡單，只要從快照中複製檔案到父資料集。在 <filename>.zfs/snapshot</filename> 目錄結構下有一個與先前所做的快照名稱相同的目錄，可以很容易的找到。在下個範例中，我們會示範從隱藏的 <filename>.zfs</filename> 目錄還原一個檔案，透過從含有該檔案的最新版快照複製：</para> <screen xml:lang="en"><prompt>#</prompt> <userinput>rm /var/tmp/passwd</userinput> -<prompt>%</prompt> <userinput>ls -a /var/tmp</userinput> +<prompt>#</prompt> <userinput>ls -a /var/tmp</userinput> . .. .zfs vi.recover <prompt>#</prompt> <userinput>ls /var/tmp/.zfs/snapshot</userinput> after_cp my_recursive_snapshot @@ -31277,18 +31323,18 @@ mypool@replica2 0 <listitem> <para>在傳送端系統上：</para> - <screen xml:lang="en"><prompt>#</prompt> <command>zfs allow -u someuser send,snapshot <replaceable>mypool</replaceable></command></screen> + <screen xml:lang="en"><prompt>#</prompt> <userinput>zfs allow -u someuser send,snapshot <replaceable>mypool</replaceable></userinput></screen> </listitem> <listitem> <para>要掛載儲存池，無權限的使用者必須擁有該目錄且必須允許一般的使用者掛載檔案系統。在接收端系統上：</para> - <screen xml:lang="en"><prompt>#</prompt> sysctl vfs.usermount=1 + <screen xml:lang="en"><prompt>#</prompt> <userinput>sysctl vfs.usermount=1</userinput> vfs.usermount: 0 -> 1 -<prompt>#</prompt> echo vfs.usermount=1 >> /etc/sysctl.conf +<prompt>#</prompt> <userinput>sysrc -f /etc/sysctl.conf vfs.usermount=1</userinput> <prompt>#</prompt> <userinput>zfs create <replaceable>recvpool/backup</replaceable></userinput> <prompt>#</prompt> <userinput>zfs allow -u <replaceable>someuser</replaceable> create,mount,receive <replaceable>recvpool/backup</replaceable></userinput> -<prompt>#</prompt> chown <replaceable>someuser</replaceable> <replaceable>/recvpool/backup</replaceable></screen> +<prompt>#</prompt> <userinput>chown <replaceable>someuser</replaceable> <replaceable>/recvpool/backup</replaceable></userinput></screen> </listitem> </itemizedlist> @@ -31406,7 +31452,7 @@ mypool/compressed_dataset compressratio 1.11x mypool/compressed_dataset compression lz4 local mypool/compressed_dataset logicalused 496G -</screen> - <para>資料集目前使用了 449 GB 的空間 (在 used 屬性)。在尚未壓縮前，該資料集應該會使用 496 GB 的空間 (於 <literal>logicallyused</literal> 屬性)，這個結果顯示目前的壓縮比為 1.11:1。</para> + <para>資料集目前使用了 449 GB 的空間 (在 used 屬性)。在尚未壓縮前，該資料集應該會使用 496 GB 的空間 (於 <literal>logicalused</literal> 屬性)，這個結果顯示目前的壓縮比為 1.11:1。</para> <para>壓縮功能在與使用者配額 (<link linkend="zfs-term-userquota">User Quota</link>) 一併使用時可能會產生無法預期的副作用。使用者配額會限制一個使用者在一個資料集上可以使用多少空間，但衡量的依據是以 <emphasis>壓縮後</emphasis> 所使用的空間，因此，若一個使用者有 10 GB 的配額，寫入了 10 GB 可壓縮的資料，使用者將還會有空間儲存額外的資料。若使用者在之後更新了一個檔案，例如一個資料庫，可能有更多或較少的可壓縮資料，那麼剩餘可用的空間量也會因此而改變，這可能會造成奇怪的現象便是，一個使用者雖然沒有增加實際的資料量 (於 <literal>logicalused</literal> 屬性)，但因為更改影響了壓縮率，導致使用者達到配額的上限。</para> @@ -31430,10 +31476,9 @@ pool 2.84G 2.19M 2.83G 0% 1.00x ONLINE -</screen> <para><literal>DEDUP</literal> 欄位會顯示儲存池的實際去重複率，數值為 <literal>1.00x</literal> 代表資料尚未被去重複。在下一個例子會在前面所建立的去重複儲存池中複製三份 Port 樹到不同的目錄中。</para> - <screen xml:lang="en"><prompt>#</prompt> <userinput>zpool list</userinput> -for d in dir1 dir2 dir3; do -for> mkdir $d && cp -R /usr/ports $d & -for> done</screen> + <screen xml:lang="en"><prompt>#</prompt> <userinput>for d in dir1 dir2 dir3; do</userinput> +> <userinput>mkdir $d && cp -R /usr/ports $d &</userinput> +> <userinput>done</userinput></screen> <para>已經偵測到重複的資料並做去重複：</para> @@ -32277,7 +32322,7 @@ vfs.zfs.vdev.cache.size="5M"</programlisting> <para>XXXTR: Though! The disks chapter, covers a bit of this and devfs under it's USB devices. It leaves a lot to be desired though, see: -http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/usb-disks.html +https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/usb-disks.html It may be better to flesh out that section a bit more. Add the word "camera" to it so that others can easily notice.</para> </sect1> @@ -32333,6 +32378,16 @@ http://www.freebsd.org/doc/en_US.ISO8859-1/books/handb <contrib>bhyve section by </contrib> </author> </authorgroup> + + <authorgroup> + <author xml:lang="en"> + <personname> + <firstname>Benedict</firstname> + <surname>Reuschling</surname> + </personname> + <contrib>Xen section by </contrib> + </author> + </authorgroup> </info> <sect1 xml:id="virtualization-synopsis"> @@ -32947,9 +33002,22 @@ perm vboxnetctl 0660</programlisting> <sect2 xml:id="virtualization-virtualbox-usb-support"> <title><trademark>VirtualBox</trademark> USB 支援</title> - <para><application><trademark>VirtualBox</trademark></application> 擴充包目前不支援 FreeBSD 主端系統，沒有這個擴充包，FreeBSD 主端系統無法傳遞 <acronym>USB</acronym> 埠給客端作業系統。</para> - </sect2> + <para xml:lang="en"><application><trademark>VirtualBox</trademark></application> can be configured + to pass <acronym>USB</acronym> devices through to the guest + operating system. The host controller of the OSE version is + limited to emulating <acronym>USB</acronym> 1.1 devices until + the extension pack supporting <acronym>USB</acronym> 2.0 and 3.0 + devices becomes available on FreeBSD.</para> + <para xml:lang="en">For <application><trademark>VirtualBox</trademark></application> to be + aware of <acronym>USB</acronym> devices attached to the + machine, the user needs to be a member of the <systemitem class="groupname">operator</systemitem> group.</para> + + <screen xml:lang="en"><prompt>#</prompt> <userinput>pw groupmod operator -m <replaceable>yourusername</replaceable></userinput></screen> + + <para>重新啟動登作階段與 <application><trademark>VirtualBox</trademark></application> 來讓這些變更生效，且建立必要的 <acronym>USB</acronym> 的過濾器。</para> + </sect2> + <sect2 xml:id="virtualization-virtualbox-host-dvd-cd-access"> <title><trademark>VirtualBox</trademark> Host <acronym>DVD</acronym>/<acronym>CD</acronym> 存取</title> @@ -33066,7 +33134,7 @@ FreeBSD-10.3-RELEASE-amd64-bootonly.iso 100% of machine, used to track the running machines. This example starts the virtual machine in installation mode:</para> - <screen xml:lang="en"><prompt>#</prompt> <userinput>sh /usr/share/examples/bhyve/vmrun.sh -c <replaceable>4</replaceable> -m <replaceable>1024M</replaceable> -t <replaceable>tap0</replaceable> -d <replaceable>guest.img</replaceable> -i -I <replaceable>FreeBSD-10.3-RELEASE-amd64-bootonly.iso</replaceable> <replaceable>guestname</replaceable></userinput></screen> + <screen xml:lang="en"><prompt>#</prompt> <userinput>sh /usr/share/examples/bhyve/vmrun.sh -c <replaceable>1</replaceable> -m <replaceable>1024M</replaceable> -t <replaceable>tap0</replaceable> -d <replaceable>guest.img</replaceable> -i -I <replaceable>FreeBSD-10.3-RELEASE-amd64-bootonly.iso</replaceable> <replaceable>guestname</replaceable></userinput></screen> <para xml:lang="en">The virtual machine will boot and start the installer. After installing a system in the virtual machine, when the @@ -33320,7 +33388,7 @@ crw------- 1 root wheel 0x1a1 Mar 17 12:19 othergu <para xml:lang="en">A specified virtual machine can be destroyed using <command>bhyvectl</command>:</para> - <screen xml:lang="en"><prompt>#</prompt> bhyvectl --destroy --vm=<replaceable>guestname</replaceable></screen> + <screen xml:lang="en"><prompt>#</prompt> <userinput>bhyvectl --destroy --vm=<replaceable>guestname</replaceable></userinput></screen> </sect2> <sect2 xml:id="virtualization-bhyve-onboot"> @@ -33355,18 +33423,332 @@ ifconfig_bridge0="addm <replaceable>igb0</replaceable> </step> </procedure> </sect2> -<!-- - Note: There is no working/end-user ready Xen support for FreeBSD as of 07-2010. - Hide all information regarding Xen under FreeBSD. + </sect1> - <sect2 id="virtualization-other"> - <title>Other Virtualization Options</title> + <sect1 xml:id="virtualization-host-xen"> + <title>以 FreeBSD 作為主端安裝 <trademark>Xen</trademark></title> - <para>There is ongoing work in getting - <application>&xen;</application> - to work as a host environment on &os;.</para> - </sect2> + <para xml:lang="en"><application>Xen</application> is a GPLv2-licensed <link xlink:href="https://en.wikipedia.org/wiki/Hypervisor#Classification">type + 1 hypervisor</link> for <trademark class="registered">Intel</trademark> and <trademark class="registered">ARM</trademark> architectures. FreeBSD + has included <trademark>i386</trademark> and <trademark class="registered">AMD</trademark> 64-Bit <link xlink:href="https://wiki.xenproject.org/wiki/DomU">DomU</link>; + and <link xlink:href="https://en.wikipedia.org/wiki/Amazon_Elastic_Compute_Cloud">Amazon + EC2</link> unprivileged domain (virtual machine) support since + FreeBSD 8.0 and includes Dom0 control domain (host) support in + FreeBSD 11.0. Support for para-virtualized (PV) domains has + been removed from FreeBSD 11 in favor of hardware virtualized + (HVM) domains, which provides better performance.</para> + + <para xml:lang="en"><trademark>Xen</trademark> is a bare-metal hypervisor, which means that it is the + first program loaded after the BIOS. A special privileged guest + called the Domain-0 (<literal>Dom0</literal> for short) is then + started. The Dom0 uses its special privileges to directly + access the underlying physical hardware, making it a + high-performance solution. It is able to access the disk + controllers and network adapters directly. The <trademark>Xen</trademark> management + tools to manage and control the <trademark>Xen</trademark> hypervisor are also used + by the Dom0 to create, list, and destroy VMs. Dom0 provides + virtual disks and networking for unprivileged domains, often + called <literal>DomU</literal>. <trademark>Xen</trademark> Dom0 can be compared to + the service console of other hypervisor solutions, while the + DomU is where individual guest VMs are run.</para> + +<!-- Hidden until the mode in which FreeBSD uses Xen is supported. + <para>Features of &xen; include GPU passthrough from the host + running the Dom0 into a DomU guest machine. This requires a + CPU, chipset, and BIOS with VT-D support and might require extra + patches or not work with all graphics cards. A list of adapters + can be found in the <link + xlink:href="https://wiki.xenproject.org/wiki/Xen_VGA_Passthrough_Tested_Adapters">Xen + Wiki</link>. Note that not all GPUs listed there are + supported on &os;. The &xen; hypervisor also supports PCI + passthrough to give a DomU guest full, direct access to a PCI + device like NIC, disk controller, or soundcard.</para> --> + <para xml:lang="en"><trademark>Xen</trademark> can migrate VMs between different <trademark>Xen</trademark> servers. When + the two xen hosts share the same underlying storage, the + migration can be done without having to shut the VM down first. + Instead, the migration is performed live while the DomU is + running and there is no need to restart it or plan a downtime. + This is useful in maintenance scenarios or upgrade windows to + ensure that the services provided by the DomU are still + provided. Many more features of <trademark>Xen</trademark> are listed on the <link xlink:href="https://wiki.xenproject.org/wiki/Category:Overview">Xen + Wiki Overview page</link>. Note that not all features are + supported on FreeBSD yet.</para> + + <sect2 xml:id="virtualization-host-xen-requirements"> + <title xml:lang="en">Hardware Requirements for <trademark>Xen</trademark> Dom0</title> + + <para xml:lang="en">To run the <trademark>Xen</trademark> hypervisor on a host, certain hardware + functionality is required. Hardware virtualized domains + require Extended Page Table (<link xlink:href="http://en.wikipedia.org/wiki/Extended_Page_Table">EPT</link>) + and Input/Output Memory Management Unit (<link xlink:href="http://en.wikipedia.org/wiki/List_of_IOMMU-supporting_hardware">IOMMU</link>) + support in the host processor.</para> + </sect2> + + <sect2 xml:id="virtualization-host-xen-dom0-setup"> + <title xml:lang="en"><trademark>Xen</trademark> Dom0 Control Domain Setup</title> + + <para xml:lang="en">The <package>emulators/xen</package> package works with + FreeBSD 11 amd64 binary snapshots and equivalent systems + built from source. This example assumes VNC output for + unprivileged domains which is accessed from a another system + using a tool such as <package>net/tightvnc</package>.</para> + + <para xml:lang="en">Install <package>emulators/xen</package>:</para> + + <screen xml:lang="en"><prompt>#</prompt> <userinput>pkg install xen</userinput></screen> + + <para xml:lang="en">Configuration files must be edited to prepare the host + for the Dom0 integration. An entry to + <filename>/etc/sysctl.conf</filename> disables the limit on + how many pages of memory are allowed to be wired. Otherwise, + DomU VMs with higher memory requirements will not run.</para> + + <screen xml:lang="en"><prompt>#</prompt> <userinput>sysrc -f /etc/sysctl.conf vm.max_wired=-1</userinput></screen> + + <para xml:lang="en">Another memory-related setting involves changing + <filename>/etc/login.conf</filename>, setting the + <literal>memorylocked</literal> option to + <literal>unlimited</literal>. Otherwise, creating DomU + domains may fail with <errorname>Cannot allocate + memory</errorname> errors. After making the change to + <filename>/etc/login.conf</filename>, run + <command>cap_mkdb</command> to update the capability database. + See <xref linkend="security-resourcelimits"/> for + details.</para> + + <screen xml:lang="en"><prompt>#</prompt> <userinput>sed -i '' -e 's/memorylocked=64K/memorylocked=unlimited/' /etc/login.conf</userinput> +<prompt>#</prompt> <userinput>cap_mkdb /etc/login.conf</userinput></screen> + + <para xml:lang="en">Add an entry for the <trademark>Xen</trademark> console to + <filename>/etc/ttys</filename>:</para> + + <screen xml:lang="en"><prompt>#</prompt> <userinput>echo 'xc0 "/usr/libexec/getty Pc" xterm on secure' >> /etc/ttys</userinput></screen> + + <para xml:lang="en">Selecting a <trademark>Xen</trademark> kernel in + <filename>/boot/loader.conf</filename> activates the Dom0. + <trademark>Xen</trademark> also requires resources like CPU and memory from the + host machine for itself and other DomU domains. How much CPU + and memory depends on the individual requirements and hardware + capabilities. In this example, 8 GB of memory and 4 + virtual CPUs are made available for the Dom0. The serial + console is also activated and logging options are + defined.</para> + + <screen xml:lang="en"><prompt>#</prompt> <userinput>sysrc -f /boot/loader.conf hw.pci.mcfg=0</userinput> +<prompt>#</prompt> <userinput>sysrc -f /boot/loader.conf xen_kernel="/boot/xen"</userinput> +<prompt>#</prompt> <userinput>sysrc -f /boot/loader.conf xen_cmdline="dom0_mem=<replaceable>8192M</replaceable> dom0_max_vcpus=<replaceable>4</replaceable> dom0pvh=1 console=com1,vga com1=115200,8n1 guest_loglvl=all loglvl=all"</userinput></screen> + + <para xml:lang="en">Log files that <trademark>Xen</trademark> creates for the Dom0 and DomU VMs + are stored in <filename>/var/log/xen</filename>. This + directory does not exist by default and must be + created.</para> + + <screen xml:lang="en"><prompt>#</prompt> <userinput>mkdir -p /var/log/xen</userinput> +<prompt>#</prompt> <userinput>chmod 644 /var/log/xen</userinput></screen> + + <para xml:lang="en"><trademark>Xen</trademark> provides a boot menu to activate and de-activate + the hypervisor on demand in + <filename>/boot/menu.rc.local</filename>:</para> + + <screen xml:lang="en"><prompt>#</prompt> <userinput>echo "try-include /boot/xen.4th" >> /boot/menu.rc.local</userinput></screen> + + <para xml:lang="en">Activate the xencommons service during system + startup:</para> + + <screen xml:lang="en"><prompt>#</prompt> <userinput>sysrc xencommons_enable=yes</userinput></screen> + + <para xml:lang="en">These settings are enough to start a Dom0-enabled + system. However, it lacks network functionality for the + DomU machines. To fix that, define a bridged interface with + the main NIC of the system which the DomU VMs can use to + connect to the network. Replace + <replaceable>igb0</replaceable> with the host network + interface name.</para> + + <screen xml:lang="en"><prompt>#</prompt> <userinput>sysrc autobridge_interfaces=bridge0</userinput> +<prompt>#</prompt> <userinput>sysrc autobridge_bridge0=<replaceable>igb0</replaceable></userinput> +<prompt>#</prompt> <userinput>sysrc ifconfig_bridge0=SYNCDHCP</userinput></screen> + + <para xml:lang="en">Restart the host to load the <trademark>Xen</trademark> kernel and start the + Dom0.</para> + + <screen xml:lang="en"><prompt>#</prompt> <userinput>reboot</userinput></screen> + + <para xml:lang="en">After successfully booting the <trademark>Xen</trademark> kernel and logging + into the system again, the <trademark>Xen</trademark> management tool + <command>xl</command> is used to show information about the + domains.</para> + + <screen xml:lang="en"><prompt>#</prompt> <userinput>xl list</userinput> +Name ID Mem VCPUs State Time(s) +Domain-0 0 8192 4 r----- 962.0</screen> + + <para xml:lang="en">The output confirms that the Dom0 (called + <literal>Domain-0</literal>) has the ID <literal>0</literal> + and is running. It also has the memory and virtual CPUs + that were defined in <filename>/boot/loader.conf</filename> + earlier. More information can be found in the <link xlink:href="https://www.xenproject.org/help/documentation.html"><trademark>Xen</trademark>; + Documentation</link>. DomU guest VMs can now be + created.</para> + </sect2> + + <sect2 xml:id="virtualization-host-xen-domu-setup"> + <title><trademark>Xen</trademark> DomU 客端 VM 設置</title> + + <para xml:lang="en">Unprivileged domains consist of a configuration file and + virtual or physical hard disks. Virtual disk storage for + the DomU can be files created by <citerefentry><refentrytitle>truncate</refentrytitle><manvolnum>1</manvolnum></citerefentry> or ZFS + volumes as described in <xref linkend="zfs-zfs-volume"/>. + In this example, a 20 GB volume is used. A VM is + created with the ZFS volume, a FreeBSD ISO image, 1 GB of + RAM and two virtual CPUs. The ISO installation file is + retrieved with <citerefentry><refentrytitle>fetch</refentrytitle><manvolnum>1</manvolnum></citerefentry> and saved locally in a file + called <filename>freebsd.iso</filename>.</para> + + <screen xml:lang="en"><prompt>#</prompt> <userinput>fetch <replaceable>ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.3/FreeBSD-10.3-RELEASE-amd64-bootonly.iso</replaceable>; -o <replaceable>freebsd.iso</replaceable></userinput></screen> + + <para xml:lang="en">A ZFS volume of 20 GB called + <filename>xendisk0</filename> is created to serve as the disk + space for the VM.</para> + + <screen xml:lang="en"><prompt>#</prompt> <userinput>zfs create -V20G -o volmode=dev zroot/xendisk0</userinput></screen> + + <para xml:lang="en">The new DomU guest VM is defined in a file. Some specific + definitions like name, keymap, and VNC connection details are + also defined. The following <filename>freebsd.cfg</filename> + contains a minimum DomU configuration for this example:</para> + + <screen xml:lang="en"><prompt>#</prompt> <userinput>cat freebsd.cfg</userinput> +builder = "hvm" <co xml:id="co-xen-builder"/> +name = "freebsd" <co xml:id="co-xen-name"/> +memory = 1024 <co xml:id="co-xen-memory"/> +vcpus = 2 <co xml:id="co-xen-vcpus"/> +vif = [ 'mac=00:16:3E:74:34:32,bridge=bridge0' ] <co xml:id="co-xen-vif"/> +disk = [ +'/dev/zvol/tank/xendisk0,raw,hda,rw', <co xml:id="co-xen-disk"/> +'/root/freebsd.iso,raw,hdc:cdrom,r' <co xml:id="co-xen-cdrom"/> + ] +vnc = 1 <co xml:id="co-xen-vnc"/> +vnclisten = "0.0.0.0" +serial = "pty" +usbdevice = "tablet"</screen> + + <para xml:lang="en">These lines are explained in more detail:</para> + + <calloutlist> + <callout arearefs="co-xen-builder"> + <para xml:lang="en">This defines what kind of virtualization to use. + <literal>hvm</literal> refers to hardware-assisted + virtualization or hardware virtual machine. Guest + operating systems can run unmodified on CPUs with + virtualization extensions, providing nearly the same + performance as running on physical hardware. + <literal>generic</literal> is the default value and + creates a PV domain.</para> + </callout> + + <callout arearefs="co-xen-name"> + <para xml:lang="en">Name of this virtual machine to distinguish it from + others running on the same Dom0. Required.</para> + </callout> + + <callout arearefs="co-xen-memory"> + <para xml:lang="en">Quantity of RAM in megabytes to make available to the + VM. This amount is subtracted from the hypervisor's total + available memory, not the memory of the Dom0.</para> + </callout> + + <callout arearefs="co-xen-vcpus"> + <para xml:lang="en">Number of virtual CPUs available to the guest VM. For + best performance, do not create guests with more virtual + CPUs than the number of physical CPUs on the host.</para> *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201710261525.v9QFP97k017797>