Date: Wed, 4 Jan 2017 08:47:27 +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: r49794 - head/zh_TW.UTF-8/books/handbook Message-ID: <201701040847.v048lROH086834@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: rcyu Date: Wed Jan 4 08:47:27 2017 New Revision: 49794 URL: https://svnweb.freebsd.org/changeset/doc/49794 Log: Update the po file of the zh_TW handbook to sync with the latest English version. Mainly translate the following sections: 11.2. Starting Services 11.3. Configuring cron(8) 11.4. Managing Services in FreeBSD 11.5. Setting Up Network Interface Cards 11.6. Virtual Hosts 11.7. Configuring System Logging (11.7.1, 11.7.2) 11.8. Configuration Files 11.9. Tuning with sysctl(8) 11.12. Adding Swap Space Update the zh_TW translation of the following chapters or sections: 6.2.1.3. Firefox and Swfdec Flash® Plugin 6.2.4. Chromium 6.3.1. Calligra 6.3.5. LibreOffice 6.4. Document Viewers 7.2. Setting Up the Sound Card 8.2. Why Build a Custom Kernel? 8.3. Finding the System Hardware 19. The Z File System (ZFS) Submitted by: cwlin0416@gmail.com Differential Revision: https://reviews.freebsd.org/D9040 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 Tue Jan 3 18:42:44 2017 (r49793) +++ head/zh_TW.UTF-8/books/handbook/book.xml Wed Jan 4 08:47:27 2017 (r49794) @@ -117,6 +117,7 @@ <!ENTITY pgpkey.csjp SYSTEM "csjp.key"> <!ENTITY pgpkey.culot SYSTEM "culot.key"> <!ENTITY pgpkey.cy SYSTEM "cy.key"> +<!ENTITY pgpkey.dab SYSTEM "dab.key"> <!ENTITY pgpkey.daichi SYSTEM "daichi.key"> <!ENTITY pgpkey.damien SYSTEM "damien.key"> <!ENTITY pgpkey.danfe SYSTEM "danfe.key"> @@ -134,6 +135,7 @@ <!ENTITY pgpkey.dd SYSTEM "dd.key"> <!ENTITY pgpkey.deb SYSTEM "deb.key"> <!ENTITY pgpkey.decke SYSTEM "decke.key"> +<!ENTITY pgpkey.def SYSTEM "def.key"> <!ENTITY pgpkey.deischen SYSTEM "deischen.key"> <!ENTITY pgpkey.delphij SYSTEM "delphij.key"> <!ENTITY pgpkey.demon SYSTEM "demon.key"> @@ -283,6 +285,7 @@ <!ENTITY pgpkey.lesi SYSTEM "lesi.key"> <!ENTITY pgpkey.lev SYSTEM "lev.key"> <!ENTITY pgpkey.lidl SYSTEM "lidl.key"> +<!ENTITY pgpkey.lifanov SYSTEM "lifanov.key"> <!ENTITY pgpkey.linimon SYSTEM "linimon.key"> <!ENTITY pgpkey.lioux SYSTEM "lioux.key"> <!ENTITY pgpkey.lippe SYSTEM "lippe.key"> @@ -332,6 +335,7 @@ <!ENTITY pgpkey.mich SYSTEM "mich.key"> <!ENTITY pgpkey.mikeh SYSTEM "mikeh.key"> <!ENTITY pgpkey.milki SYSTEM "milki.key"> +<!ENTITY pgpkey.misha SYSTEM "misha.key"> <!ENTITY pgpkey.miwi SYSTEM "miwi.key"> <!ENTITY pgpkey.mizhka SYSTEM "mizhka.key"> <!ENTITY pgpkey.mjg SYSTEM "mjg.key"> @@ -400,6 +404,7 @@ <!ENTITY pgpkey.plosher SYSTEM "plosher.key"> <!ENTITY pgpkey.pluknet SYSTEM "pluknet.key"> <!ENTITY pgpkey.portmgr-secretary SYSTEM "portmgr-secretary.key"> +<!ENTITY pgpkey.pstef SYSTEM "pstef.key"> <!ENTITY pgpkey.qingli SYSTEM "qingli.key"> <!ENTITY pgpkey.rafan SYSTEM "rafan.key"> <!ENTITY pgpkey.rakuco SYSTEM "rakuco.key"> @@ -629,6 +634,7 @@ <year>2013</year> <year>2014</year> <year>2015</year> + <year>2016</year> <holder>The FreeBSD Documentation Project</holder> </copyright> @@ -706,9 +712,9 @@ </legalnotice> <abstract> - <para>歡迎使用 FreeBSD！ 本使用手冊涵蓋範圍包括了 <emphasis>FreeBSD 9.3-RELEASE</emphasis> 與 <emphasis>FreeBSD 10.3-RELEASE</emphasis>。 這份使用手冊是很多人的集體創作，而且仍然『持續不斷』的進行中。 許多章節仍未完成，已完成的部份也有些需要更新。 如果您有興趣協助本計畫的話，請寄電子郵件至 <link xlink:href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-doc">FreeBSD 文件專案郵遞論壇</link>。</para> + <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>在 <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="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> </abstract> </info> @@ -1629,6 +1635,13 @@ </listitem> <listitem> + <para><link xlink:href="https://www.stormshield.eu">Stormshield</link>; <indexterm> + <primary>Stormshield</primary> + + </indexterm> - Stormshield 網路安全設備使用了硬體化版本的 FreeBSD 做為基礎，BSD 授權條款讓我們我們的智慧財產與系統可以整合，並同時回饋大量有趣的發展給社群。</para> + </listitem> + + <listitem> <para><link xlink:href="http://www.weather.com/">The Weather Channel</link> <indexterm> <primary>The Weather Channel</primary> @@ -2258,7 +2271,7 @@ <step> <title>檢查 FreeBSD 勘誤表</title> - <para>儘管 FreeBSD Project 努力確保每個 FreeBSD 發行版能夠儘可能地穩定，錯誤偶爾還是會悄悄出現。 有極小的機會錯誤會影響安裝過程。 當這些問題被發現並修正後，會被紀錄在 FreeBSD 網站的 FreeBSD 勘誤表 (<link xlink:href="@@URL_RELPREFIX@@/releases/10.3R/errata.html">http://www.freebsd.org/releases/10.3R/errata.html</link>) 安裝前要檢查勘誤表，確保沒有會影響到安裝的問題。</para> + <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 網站的發行資訊找到 (<link xlink:href="@@URL_RELPREFIX@@/releases/index.html">http://www.freebsd.org/releases/index.html</link>)。</para>; </step> @@ -2293,6 +2306,10 @@ <listitem> <para><literal>-memstick.img</literal>：這個檔案含有所有安裝 FreeBSD 所需的檔案，包含原始碼及 Port 套件集。這個檔案應依據以下操作指示寫入到 <acronym>USB</acronym> 隨身碟使用。</para> </listitem> + + <listitem> + <para><literal>-mini-memstick.img</literal>：類似 <literal>-bootonly.iso</literal>，但不含安裝檔 (可依所要下載)，安裝時需要網際網路連線，可依 <xref linkend="bsdinstall-usb"/> 的說明將此檔案寫入至 <acronym>USB</acronym> 隨身碟。</para> + </listitem> </itemizedlist> <para>映像檔下載完成之後，下載同一個目錄之中的 <filename>CHECKSUM.SHA256</filename>。FreeBSD 提供 <citerefentry><refentrytitle>sha256</refentrytitle><manvolnum>1</manvolnum></citerefentry> 可用來計算映像檔的 <firstterm>校驗碼 (Checksum)</firstterm>，使用方式為 <command>sha256 <replaceable>imagefilename</replaceable></command>，其他作業系統也會有類似的程式。</para> @@ -8595,7 +8612,7 @@ EndSection</programlisting> <primary><application>Chromium</application></primary> </indexterm> - <para><application>Chromium</application> 是一個開放源始碼的瀏覽器計劃，該計劃的目標是要建立一個安全、快速且更穩定的網頁瀏覽體驗。<application>Chromium</application> 的功能有頁籤式瀏覽、彈出視窗封鎖、擴充套件等等。<application>Chromium</application> 也是 Google Chrome 網頁瀏覽器所採用的基礎。</para> + <para><application>Chromium</application> 是一個開放源始碼的瀏覽器計劃，該計劃的目標是要建立一個安全、快速且更穩定的網頁瀏覽體驗。<application>Chromium</application> 的功能有頁籤式瀏覽、彈出視窗封鎖、擴充套件等等。</para> <para><application>Chromium</application> 可以使用套件來安裝，只要輸入：</para> @@ -9218,7 +9235,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/10.3R/hardware.html">Hardware Notes</link>，以確認你的音效卡是否支援以及如何在 FreeBSD 上驅動。</para> + <para>開始設定之前，必須先知道你的音效卡型號、晶片為何。 FreeBSD 支援許多種音效卡，請檢查支援的音效硬體表 <link xlink:href="http://www.FreeBSD.org/releases/11.0R/hardware.html">Hardware Notes</link>，以確認你的音效卡是否支援以及如何在 FreeBSD 上驅動。</para> <indexterm xml:lang="en"> <primary>kernel</primary> @@ -10726,7 +10743,7 @@ add path usb/0.2.0 mode 0666 group usb</ <para>早期的 FreeBSD 的核心 (Kernel) 被戲稱為 “巨石”。因為當時的核心是一個非常大的程式，且只支援固定的硬體裝置，如果您想改變核心的設定，就必須編譯一個新核心並重新開機，才能使用。</para> - <para>現在，大多數在 FreeBSD 核心的功能已採用模組 (Module) 的方式包裝，可以依據需求動態在核心載入或卸載。 這使得核心能夠快速採用新硬體環境的新功能，就叫做模組化核心 (Modular Kernel)。</para> + <para>現今，大多數在 FreeBSD 核心的功能已採用模組 (Module) 的方式包裝，並可依需求動態從核心載入或卸載。 這使得執行中的核心能夠快速適應新硬體環境並在核心開啟新的功能，這就是所謂模組化核心 (Modular Kernel)。</para> <para>儘管如此，還是有一些功能因使用到靜態的核心設定須要編譯，因為這些功能與核心緊密結合，無法將做成可動態載入的模組。且部份強調安全性的環境會盡量避免載入與卸載核心模組，且只要將需要的功能靜態的編譯到核心當中。</para> @@ -10802,7 +10819,7 @@ ath0@pci0:3:0:0: class=0x020000 c <para>以上輸出資訊說明 <filename>ath</filename> 驅動程式已經找到一個無線乙太網路裝置。</para> - <para>在 <citerefentry><refentrytitle>man</refentrytitle><manvolnum>1</manvolnum></citerefentry> 指令加上 <option>-k</option> 參數，可提供有用的資訊，例如，列出有包含指定關鍵字的手冊頁面清單：</para> + <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> @@ -14025,29 +14042,14 @@ export PATH</programlisting> <primary>services</primary> </indexterm> - <para xml:lang="en">Many users install third party software on FreeBSD from the - Ports Collection and require the installed services to be - started upon system initialization. Services, such as - <package>mail/postfix</package> or - <package>www/apache22</package> are just two of the many - software packages which may be started during system - initialization. This section explains the procedures available - for starting third party software.</para> + <para>許多使用者會使用 Port 套件集安裝第三方軟體到 FreeBSD 且需要安裝服務在系統初始化時可啟動該軟體。服務，例如 <package>mail/postfix</package> 或 <package>www/apache22</package> 僅只是在眾多需要在系統初始化時啟動的軟體之中的兩個。本章節將說明可用來啟動第三方軟體的程序。</para> - <para xml:lang="en">In FreeBSD, most included services, such as <citerefentry><refentrytitle>cron</refentrytitle><manvolnum>8</manvolnum></citerefentry>, are - started through the system start up scripts.</para> + <para>在 FreeBSD 大多數內建的服務，例如 <citerefentry><refentrytitle>cron</refentrytitle><manvolnum>8</manvolnum></citerefentry> 也是透過系統啟動 Script 來執行。</para> <sect2> <title>延伸應用程式設定</title> - <para xml:lang="en">Now that FreeBSD includes <filename>rc.d</filename>, - configuration of application startup is easier and provides - more features. Using the key words discussed in - <xref linkend="configtuning-rcd"/>, applications can be set to - start after certain other services and extra flags can be - passed through <filename>/etc/rc.conf</filename> in place of - hard coded flags in the start up script. A basic script may - look similar to the following:</para> + <para>現在 FreeBSD 會引用 <filename>rc.d</filename>，讓設定應用程式啟動程式更簡單且提供更多的功能。使用於 <xref linkend="configtuning-rcd"/> 所提到的關鍵字，可以設定應用程式在其他特定服務之後啟動且可以透過 <filename>/etc/rc.conf</filename> 來傳遞額外的旗標來取代寫死在啟動 Script 中的旗標。一個基本的 Script 可能會如下例所示：</para> <programlisting xml:lang="en">#!/bin/sh # @@ -14073,43 +14075,23 @@ pidfile=${utility_pidfile-"/var/run/util run_rc_command "$1"</programlisting> - <para xml:lang="en">This script will ensure that the provided - <literal>utility</literal> will be started after the - <literal>DAEMON</literal> pseudo-service. It also provides a - method for setting and tracking the process ID - (<acronym>PID</acronym>).</para> + <para>這個 Script 會確保要執行的 <literal>utility</literal> 會在虛構的服務 <literal>DAEMON</literal> 之後啟動，也同時提供設定與追蹤程序 ID (Process ID, <acronym>PID</acronym>) 的方法。</para> - <para xml:lang="en">This application could then have the following line placed - in <filename>/etc/rc.conf</filename>:</para> + <para>接著此應用程式便可將下行放到 <filename>/etc/rc.conf</filename> 中：</para> <programlisting xml:lang="en">utility_enable="YES"</programlisting> - <para xml:lang="en">This method allows for easier manipulation of command - line arguments, inclusion of the default functions provided - in <filename>/etc/rc.subr</filename>, compatibility with - <citerefentry><refentrytitle>rcorder</refentrytitle><manvolnum>8</manvolnum></citerefentry>, and provides for easier configuration via - <filename>rc.conf</filename>.</para> + <para>使用這種方式可以簡單的處理指令列參數、引用 <filename>/etc/rc.subr</filename> 所提供的預設函數、與 <citerefentry><refentrytitle>rcorder</refentrytitle><manvolnum>8</manvolnum></citerefentry> 相容並可在 <filename>rc.conf</filename> 簡單的設定。</para> </sect2> <sect2> <title>使用服務來啟動其他服務</title> - <para xml:lang="en">Other services can be started using <citerefentry><refentrytitle>inetd</refentrytitle><manvolnum>8</manvolnum></citerefentry>. - Working with <citerefentry><refentrytitle>inetd</refentrytitle><manvolnum>8</manvolnum></citerefentry> and its configuration is - described in depth in - <xref linkend="network-inetd"/>.</para> - - <para xml:lang="en">In some cases, it may make more sense to use - <citerefentry><refentrytitle>cron</refentrytitle><manvolnum>8</manvolnum></citerefentry> to start system services. This approach - has a number of advantages as <citerefentry><refentrytitle>cron</refentrytitle><manvolnum>8</manvolnum></citerefentry> runs these - processes as the owner of the <citerefentry><refentrytitle>crontab</refentrytitle><manvolnum>5</manvolnum></citerefentry>. This allows - regular users to start and maintain their own - applications.</para> - - <para xml:lang="en">The <literal>@reboot</literal> feature of <citerefentry><refentrytitle>cron</refentrytitle><manvolnum>8</manvolnum></citerefentry>, - may be used in place of the time specification. This causes - the job to run when <citerefentry><refentrytitle>cron</refentrytitle><manvolnum>8</manvolnum></citerefentry> is started, normally during - system initialization.</para> + <para>其他的服務可以使用 <citerefentry><refentrytitle>inetd</refentrytitle><manvolnum>8</manvolnum></citerefentry> 來啟動，在 <xref linkend="network-inetd"/> 有如何使用 <citerefentry><refentrytitle>inetd</refentrytitle><manvolnum>8</manvolnum></citerefentry> 以及其設定的深入說明。</para> + + <para>在某些情況更適合使用 <citerefentry><refentrytitle>cron</refentrytitle><manvolnum>8</manvolnum></citerefentry> 來啟動系統服務，由於 <citerefentry><refentrytitle>cron</refentrytitle><manvolnum>8</manvolnum></citerefentry> 會使用 <citerefentry><refentrytitle>crontab</refentrytitle><manvolnum>5</manvolnum></citerefentry> 的擁有者來執行這些程序，所以這個方法有不少優點，這讓一般的使用者也可以啟動與維護自己的應用程式。</para> + + <para><citerefentry><refentrytitle>cron</refentrytitle><manvolnum>8</manvolnum></citerefentry> 的 <literal>@reboot</literal> 功能，可用來替代指定詳細的時間，而該工作會在系統初始化時執行 <citerefentry><refentrytitle>cron</refentrytitle><manvolnum>8</manvolnum></citerefentry> 後執行。</para> </sect2> </sect1> @@ -14133,35 +14115,13 @@ run_rc_command "$1"</programlisting> <secondary>configuration</secondary> </indexterm> - <para xml:lang="en">One of the most useful utilities in FreeBSD is - <application>cron</application>. This utility runs in the - background and regularly checks - <filename>/etc/crontab</filename> for tasks to execute and - searches <filename>/var/cron/tabs</filename> for custom crontab - files. These files are used to schedule tasks which - <application>cron</application> runs at the specified times. - Each entry in a crontab defines a task to run and is known as a - <firstterm>cron job</firstterm>.</para> - - <para xml:lang="en">Two different types of configuration files are used: the - system crontab, which should not be modified, and user crontabs, - which can be created and edited as needed. The format used by - these files is documented in <citerefentry><refentrytitle>crontab</refentrytitle><manvolnum>5</manvolnum></citerefentry>. The format of the - system crontab, <filename>/etc/crontab</filename> includes a - <literal>who</literal> column which does not exist in user - crontabs. In the system crontab, - <application>cron</application> runs the command as the user - specified in this column. In a user crontab, all commands run - as the user who created the crontab.</para> - - <para xml:lang="en">User crontabs allow individual users to schedule their own - tasks. The <systemitem class="username">root</systemitem> user - can also have a user <filename>crontab</filename> which can be - used to schedule tasks that do not exist in the system - <filename>crontab</filename>.</para> + <para>在 FreeBSD 其中最有用的其中一項工具便是 <application>cron</application>，這個工具會在背景執行並且定期檢查 <filename>/etc/crontab</filename> 是否有要執行的工作然後搜尋 <filename>/var/cron/tabs</filename> 是否有自訂的 crontab 檔案，這些檔案用來安排要讓 <application>cron</application> 在指定的時間執行的工作，crontab 中的每一個項目定義了一個要執行的工作，又稱作 <firstterm>cron job</firstterm>。</para> - <para xml:lang="en">Here is a sample entry from the system crontab, - <filename>/etc/crontab</filename>:</para> + <para>這裡使用了兩種類型的設定檔：其一是系統 crontab，系統 crontab 不應該被修改，其二為使用者 crontab，使用者 crontab 可以依需要建立與編輯。這兩種檔案的格式在 <citerefentry><refentrytitle>crontab</refentrytitle><manvolnum>5</manvolnum></citerefentry> 有說明。系統 crontab <filename>/etc/crontab</filename> 的格式含有在使用者 crontab 所沒有的 <literal>who</literal> 欄位，在系統 crontab，<application>cron</application> 會依據該欄位所指定的使用者來執行指令，而在使用者 crontab，會以建立 crontab 的使用者來執行指令。</para> + + <para>使用者 crontab 讓個別使用者可以安排自己的工作，<systemitem class="username">root</systemitem> 使用者也可有自己的使用者 <filename>crontab</filename> 來安排不在系統 <filename>crontab</filename> 中的工作。</para> + + <para>以下為系統 crontab <filename>/etc/crontab</filename> 的範例項目：</para> <programlisting xml:lang="en"># /etc/crontab - root's crontab for FreeBSD # @@ -14176,115 +14136,58 @@ PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin <calloutlist> <callout arearefs="co-comments"> - <para xml:lang="en">Lines that begin with the <literal>#</literal> character - are comments. A comment can be placed in the file as a - reminder of what and why a desired action is performed. - Comments cannot be on the same line as a command or else - they will be interpreted as part of the command; they must - be on a new line. Blank lines are ignored.</para> + <para>以 <literal>#</literal> 字元為首的行代表註解。可在檔案中放置註解提醒要執行什麼動作及為何要執行。註解不可與指令同行，否則會被當做指令的一部份，註解必須在新的一行，空白行則會被忽略掉。</para> </callout> <callout arearefs="co-env"> - <para xml:lang="en">The equals (<literal>=</literal>) character is used to - define any environment settings. In this example, it is - used to define the <envar>SHELL</envar> and - <envar>PATH</envar>. If the <envar>SHELL</envar> is - omitted, <application>cron</application> will use the - default Bourne shell. If the <envar>PATH</envar> is - omitted, the full path must be given to the command or - script to run.</para> + <para>等號 (<literal>=</literal>) 字元用來定義任何環境設定。在這個例子當中，使用了等號來定義 <envar>SHELL</envar> 及 <envar>PATH</envar>。若 <envar>SHELL</envar> 被省略，<application>cron</application> 則會使用預設的 Bourne shell。若 <envar>PATH</envar> 被省略，則必須指定指令或 Script 的完整路徑才能執行。</para> </callout> <callout arearefs="co-field-descr"> - <para xml:lang="en">This line defines the seven fields used in a system - crontab: <literal>minute</literal>, <literal>hour</literal>, - <literal>mday</literal>, <literal>month</literal>, - <literal>wday</literal>, <literal>who</literal>, and - <literal>command</literal>. The <literal>minute</literal> - field is the time in minutes when the specified command will - be run, the <literal>hour</literal> is the hour when the - specified command will be run, the <literal>mday</literal> - is the day of the month, <literal>month</literal> is the - month, and <literal>wday</literal> is the day of the week. - These fields must be numeric values, representing the - twenty-four hour clock, or a <literal>*</literal>, - representing all values for that field. The - <literal>who</literal> field only exists in the system - crontab and specifies which user the command should be run - as. The last field is the command to be executed.</para> + <para>此行定義了在系統 crontab 會使用到的七個欄位：<literal>minute</literal>, <literal>hour</literal>, <literal>mday</literal>, <literal>month</literal>, <literal>wday</literal>, <literal>who</literal> 以及 <literal>command</literal>。<literal>minute</literal> 欄位是指定指令要執行的時間中的分，<literal>hour</literal> 指定指令要執行的時，<literal>mday</literal> 是月裡面的日，<literal>month</literal> 是月，以及 <literal>wday</literal> 是週裡面的日。這些欄位必須數值代表 24 小時制的時間或 <literal>*</literal> 來代表所有可能的值。<literal>who</literal> 這個欄位只有系統 crontab 才有，用來指定要用那一個使用者來執行指令。最後一個欄位則是要執行的指令。</para> </callout> <callout arearefs="co-main"> - <para xml:lang="en">This entry defines the values for this cron job. The - <literal>*/5</literal>, followed by several more - <literal>*</literal> characters, specifies that - <command>/usr/libexec/atrun</command> is invoked by - <systemitem class="username">root</systemitem> every five - minutes of every hour, of every day and day of the week, of - every month.</para> - - <para xml:lang="en">Commands can include any number of switches. However, - commands which extend to multiple lines need to be broken - with the backslash <quote>\</quote> continuation - character.</para> + <para>這個項目定義了該工作所使用的數值，<literal>*/5</literal> 後接著數個 <literal>*</literal> 字元指的是每個月的每一週的每一日的每個小時的每 5 分鐘會使用 <systemitem class="username">root</systemitem> 執行 <command>/usr/libexec/atrun</command>。</para> + + <para>指令可含任何數量的參數，但若指令要使用多行則需以反斜線 <quote>\</quote> 連線字元換行。</para> </callout> </calloutlist> <sect2 xml:id="configtuning-installcrontab"> <title>建立使用者的 Crontab</title> - <para xml:lang="en">To create a user crontab, invoke - <command>crontab</command> in editor mode:</para> + <para>要建立一個使用者 crontab 可使用編輯模式執行 <command>crontab</command>：</para> <screen xml:lang="en"><prompt>%</prompt> <userinput>crontab -e</userinput></screen> - <para xml:lang="en">This will open the user's crontab using the default text - editor. The first time a user runs this command, it will open - an empty file. Once a user creates a crontab, this command - will open that file for editing.</para> - - <para xml:lang="en">It is useful to add these lines to the top of the crontab - file in order to set the environment variables and to remember - the meanings of the fields in the crontab:</para> + <para>這樣會使用預設的文字編輯器來開啟使用者的 crontab，使用者第一次執行這個指令會開啟一個空的檔案，使用者建立 crontab 之後這個指令則會開啟已建立的 crontab 供編輯。</para> + + <para>加入這些行到 crontab 檔的最上方來設定環境變數以及備忘在 crontab 中欄位的意思非常有用：</para> <programlisting xml:lang="en">SHELL=/bin/sh PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin # Order of crontab fields # minute hour mday month wday command</programlisting> - <para xml:lang="en">Then add a line for each command or script to run, - specifying the time to run the command. This example runs the - specified custom Bourne shell script every day at two in the - afternoon. Since the path to the script is not specified in - <literal>PATH</literal>, the full path to the script is - given:</para> + <para>然後每一個要執行的指令或 Script 加入一行，指定要執行指令的時間。這個例子會每天在下午 2 點執行指定的自訂 Bourne shell script，由於沒有在 <literal>PATH</literal> 指定 Script 的路徑，所以必須給予完整的 Script 路徑：</para> <programlisting xml:lang="en">0 14 * * * /usr/home/dru/bin/mycustomscript.sh</programlisting> <tip> - <para xml:lang="en">Before using a custom script, make sure it is executable - and test it with the limited set of environment variables - set by cron. To replicate the environment that would be - used to run the above cron entry, use:</para> + <para>在使用自訂的 Script 之前，請先確定該 Script 可以執行並且使用 cron 在有限的環境變數下測試。要複製一個用來執行上述 cron 項目的環境可以使用：</para> <programlisting xml:lang="en">env -i SHELL=/bin/sh PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin HOME=/home/<replaceable>dru</replaceable> LOGNAME=<replaceable>dru</replaceable> <replaceable>/usr/home/dru/bin/mycustomscript.sh</replaceable></programlisting> - <para xml:lang="en">The environment set by cron is discussed in - <citerefentry><refentrytitle>crontab</refentrytitle><manvolnum>5</manvolnum></citerefentry>. Checking that scripts operate correctly in - a cron environment is especially important if they include - any commands that delete files using wildcards.</para> + <para>在 <citerefentry><refentrytitle>crontab</refentrytitle><manvolnum>5</manvolnum></citerefentry> 有討論 cron 使用的環境變數，若 Script 中含有任何會使用萬用字元刪除檔案的指令，那麼檢查 Script 可正常在 cron 的環境運作非常重要。</para> </tip> - <para xml:lang="en">When finished editing the crontab, save the file. It - will automatically be installed and - <application>cron</application> will read the crontab and run - its cron jobs at their specified times. To list the cron jobs - in a crontab, use this command:</para> + <para>編輯完成 crontab 之後儲存檔案，編輯完的 crontab 會被自動安裝且 <application>cron</application> 會讀取該 crontab 並在其指定的時指執行其 cron job。要列出 crontab 中有那一些 cron job 可以使用此指令：</para> <screen xml:lang="en"><prompt>%</prompt> <userinput>crontab -l</userinput> 0 14 * * * /usr/home/dru/bin/mycustomscript.sh</screen> - <para xml:lang="en">To remove all of the cron jobs in a user crontab:</para> + <para>要移除使用在使用者 crontab 中的 cron job 可：</para> <screen xml:lang="en"><prompt>%</prompt> <userinput>crontab -r</userinput> remove crontab for dru? <userinput>y</userinput></screen> @@ -14306,53 +14209,21 @@ remove crontab for dru? <userinput>y</us </authorgroup> </info> - <para xml:lang="en">FreeBSD uses the <citerefentry><refentrytitle>rc</refentrytitle><manvolnum>8</manvolnum></citerefentry> system of startup scripts during - system initialization and for managing services. The scripts - listed in <filename>/etc/rc.d</filename> provide basic services - which can be controlled with the <option>start</option>, - <option>stop</option>, and <option>restart</option> options to - <citerefentry><refentrytitle>service</refentrytitle><manvolnum>8</manvolnum></citerefentry>. For instance, <citerefentry><refentrytitle>sshd</refentrytitle><manvolnum>8</manvolnum></citerefentry> can be restarted - with the following command:</para> + <para>FreeBSD 在系統初始化時使用 <citerefentry><refentrytitle>rc</refentrytitle><manvolnum>8</manvolnum></citerefentry> 系統的啟動 Script。列於 <filename>/etc/rc.d</filename> 的 Script 提供了基本的服務可使用 <citerefentry><refentrytitle>service</refentrytitle><manvolnum>8</manvolnum></citerefentry> 加上 <option>start</option>, <option>stop</option> 以及 <option>restart</option> 選項來控制。例如，使用以下指令可以重新啟動 <citerefentry><refentrytitle>sshd</refentrytitle><manvolnum>8</manvolnum></citerefentry>：</para> <screen xml:lang="en"><prompt>#</prompt> <userinput>service sshd restart</userinput></screen> - <para xml:lang="en">This procedure can be used to start services on a running - system. Services will be started automatically at boot time - as specified in <citerefentry><refentrytitle>rc.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>. For example, to enable - <citerefentry><refentrytitle>natd</refentrytitle><manvolnum>8</manvolnum></citerefentry> at system startup, add the following line to - <filename>/etc/rc.conf</filename>:</para> + <para>這個程序可以用來在執行中的系統上啟動服務，而在 <citerefentry><refentrytitle>rc.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> 中有指定的服務則會在開機時自動啟動。例如，要在系統啟動時開啟 <citerefentry><refentrytitle>natd</refentrytitle><manvolnum>8</manvolnum></citerefentry>，可入下行到 <filename>/etc/rc.conf</filename>：</para> <programlisting xml:lang="en">natd_enable="YES"</programlisting> - <para xml:lang="en">If a <option>natd_enable="NO"</option> line is already - present, change the <literal>NO</literal> to - <literal>YES</literal>. The <citerefentry><refentrytitle>rc</refentrytitle><manvolnum>8</manvolnum></citerefentry> scripts will - automatically load any dependent services during the next boot, - as described below.</para> - - <para xml:lang="en">Since the <citerefentry><refentrytitle>rc</refentrytitle><manvolnum>8</manvolnum></citerefentry> system is primarily intended to start - and stop services at system startup and shutdown time, the - <option>start</option>, <option>stop</option> and - <option>restart</option> options will only perform their action - if the appropriate <filename>/etc/rc.conf</filename> variable - is set. For instance, <command>sshd restart</command> will - only work if <varname>sshd_enable</varname> is set to - <option>YES</option> in <filename>/etc/rc.conf</filename>. - To <option>start</option>, <option>stop</option> or - <option>restart</option> a service regardless of the settings - in <filename>/etc/rc.conf</filename>, these commands should be - prefixed with <quote>one</quote>. For instance, to restart - <citerefentry><refentrytitle>sshd</refentrytitle><manvolnum>8</manvolnum></citerefentry> regardless of the current - <filename>/etc/rc.conf</filename> setting, execute the following - command:</para> + <para>若 <option>natd_enable="NO"</option> 行已存在，則將 <literal>NO</literal> 更改為 <literal>YES</literal>，在下次開機時 <citerefentry><refentrytitle>rc</refentrytitle><manvolnum>8</manvolnum></citerefentry> script 便會自動載入任何相依的服務，詳細如下所述。</para> + + <para>由於 <citerefentry><refentrytitle>rc</refentrytitle><manvolnum>8</manvolnum></citerefentry> 系統主要用於在系統開機與關機時啟動與停止服務，只有當有服務的變數設定在 <filename>/etc/rc.conf</filename> 時 <option>start</option>, <option>stop</option> 以及 <option>restart</option> 才會有作用。例如 <command>sshd restart</command> 只會在 <filename>/etc/rc.conf</filename> 中的 <varname> sshd_enable</varname> 設為 <option>YES</option> 時才會運作，若要不透過 <filename>/etc/rc.conf</filename> 的設定來 <option>start</option>, <option>stop</option> 或 <option>restart</option> 一個服務則需要在指令前加上 <quote>one</quote>，例如要不透過目前在 <filename>/etc/rc.conf</filename> 的設定重新啟動 <citerefentry><refentrytitle>sshd</refentrytitle><manvolnum>8</manvolnum></citerefentry> 可執行以下指令：</para> <screen xml:lang="en"><prompt>#</prompt> <userinput>service sshd onerestart</userinput></screen> - <para xml:lang="en">To check if a service is enabled in - <filename>/etc/rc.conf</filename>, run the appropriate - <citerefentry><refentrytitle>rc</refentrytitle><manvolnum>8</manvolnum></citerefentry> script with <option>rcvar</option>. This example - checks to see if <citerefentry><refentrytitle>sshd</refentrytitle><manvolnum>8</manvolnum></citerefentry> is enabled in - <filename>/etc/rc.conf</filename>:</para> + <para>要檢查一個服務是否有在 <filename>/etc/rc.conf</filename> 開啟，可執行服務的 <citerefentry><refentrytitle>rc</refentrytitle><manvolnum>8</manvolnum></citerefentry> Script 加上 <option>rcvar</option>。這個例子會檢查 <citerefentry><refentrytitle>sshd</refentrytitle><manvolnum>8</manvolnum></citerefentry> 是否在 <filename>/etc/rc.conf</filename> 已經開啟：</para> <screen xml:lang="en"><prompt>#</prompt> <userinput>service sshd rcvar</userinput> # sshd @@ -14361,149 +14232,77 @@ sshd_enable="YES" # (default: "")</screen> <note> - <para xml:lang="en">The <literal># sshd</literal> line is output from the - above command, not a - <systemitem class="username">root</systemitem> console.</para> + <para>行 <literal># sshd</literal> 的輸出來自上述指令，而非 <systemitem class="username">root</systemitem> console。</para> </note> - <para xml:lang="en">To determine whether or not a service is running, use - <option>status</option>. For instance, to verify that - <citerefentry><refentrytitle>sshd</refentrytitle><manvolnum>8</manvolnum></citerefentry> is running:</para> + <para>要判斷是一個服務是否正在執行，可使用 <option>status</option>，例如要確認 <citerefentry><refentrytitle>sshd</refentrytitle><manvolnum>8</manvolnum></citerefentry> 是否正常在執行：</para> <screen xml:lang="en"><prompt>#</prompt> <userinput>service sshd status</userinput> sshd is running as pid 433.</screen> - <para xml:lang="en">In some cases, it is also possible to - <option>reload</option> a service. This attempts to send a - signal to an individual service, forcing the service to reload - its configuration files. In most cases, this means sending - the service a <literal>SIGHUP</literal> signal. Support for - this feature is not included for every service.</para> - - <para xml:lang="en">The <citerefentry><refentrytitle>rc</refentrytitle><manvolnum>8</manvolnum></citerefentry> system is used for network services and it - also contributes to most of the system initialization. For - instance, when the - <filename>/etc/rc.d/bgfsck</filename> script is executed, it - prints out the following message:</para> + <para>在某些情況，也可以 <option>reload</option> 一個服務。這個動作會嘗試發送一個信號給指定的服務，強制服務重新載入其設定檔，在大多數的情況下，發送給服務的信號是 <literal>SIGHUP</literal>。並不是每個服務都有支援此功能。</para> + + <para><citerefentry><refentrytitle>rc</refentrytitle><manvolnum>8</manvolnum></citerefentry> 系統會用在網路服務及也應用在大多數的系統初化 。例如執行 <filename>/etc/rc.d/bgfsck</filename> Script 會列印出以下訊息：</para> <screen xml:lang="en">Starting background file system checks in 60 seconds.</screen> - <para xml:lang="en">This script is used for background file system checks, - which occur only during system initialization.</para> + <para>這個 Script 用來在背景做檔案系統檢查，只有在系統初始化時要執行。</para> - <para xml:lang="en">Many system services depend on other services to function - properly. For example, <citerefentry><refentrytitle>yp</refentrytitle><manvolnum>8</manvolnum></citerefentry> and other - <acronym>RPC</acronym>-based services may fail to start until - after the <citerefentry><refentrytitle>rpcbind</refentrytitle><manvolnum>8</manvolnum></citerefentry> service has started. To resolve this - issue, information about dependencies and other meta-data is - included in the comments at the top of each startup script. - The <citerefentry><refentrytitle>rcorder</refentrytitle><manvolnum>8</manvolnum></citerefentry> program is used to parse these comments - during system initialization to determine the order in which - system services should be invoked to satisfy the - dependencies.</para> + <para>許多系統服務會相依其他服務來運作，例如 <citerefentry><refentrytitle>yp</refentrytitle><manvolnum>8</manvolnum></citerefentry> 及其他以 <acronym>RPC</acronym> 為基礎的服務在 <citerefentry><refentrytitle>rpcbind</refentrytitle><manvolnum>8</manvolnum></citerefentry> 服務啟動前可能會啟動失敗。要解決這種問題，就必須在啟動 Script 上方的註解中加入相依及其他 meta-data。在系統初始化時會用 <citerefentry><refentrytitle>rcorder</refentrytitle><manvolnum>8</manvolnum></citerefentry> 程式分析這些註解來決定要以什麼順序來執行系統服務以滿足相依。</para> - <para xml:lang="en">The following key word must be included in all startup - scripts as it is required by <citerefentry><refentrytitle>rc.subr</refentrytitle><manvolnum>8</manvolnum></citerefentry> to - <quote>enable</quote> the startup script:</para> + <para>因 <citerefentry><refentrytitle>rc.subr</refentrytitle><manvolnum>8</manvolnum></citerefentry> 的需要，以下的關鍵字必須加入到所有的啟動 Script 方可 <quote>enable</quote> 啟動 Script：</para> <itemizedlist> <listitem> - <para xml:lang="en"><literal>PROVIDE</literal>: Specifies the services this - file provides.</para> + <para><literal>PROVIDE</literal>: 設定此檔案所提供的服務。</para> </listitem> </itemizedlist> - <para xml:lang="en">The following key words may be included at the top of each - startup script. They are not strictly necessary, but are - useful as hints to <citerefentry><refentrytitle>rcorder</refentrytitle><manvolnum>8</manvolnum></citerefentry>:</para> + <para>以下關鍵字可能會在每個啟動 Script 的上方引用，雖然非必要，但是對於 <citerefentry><refentrytitle>rcorder</refentrytitle><manvolnum>8</manvolnum></citerefentry> 是非常有用的提示：</para> <itemizedlist> <listitem> - <para xml:lang="en"><literal>REQUIRE</literal>: Lists services which are - required for this service. The script containing this key - word will run <emphasis>after</emphasis> the specified - services.</para> + <para><literal>REQUIRE</literal>: 列出此服務需要引用的服務。有使用此關鍵字的 Script 會在指定服務啟動 <emphasis>之後</emphasis> 才執行。</para> </listitem> <listitem> - <para xml:lang="en"><literal>BEFORE</literal>: Lists services which depend - on this service. The script containing this key word will - run <emphasis>before</emphasis> the specified - services.</para> + <para><literal>BEFORE</literal>: 列出相依此服務的服務。有使用此關鍵字的 Script 會在指定的服務啟動 <emphasis>之前</emphasis> 執行。</para> </listitem> </itemizedlist> - <para xml:lang="en">By carefully setting these keywords for each startup script, - an administrator has a fine-grained level of control of the - startup order of the scripts, without the need for - <quote>runlevels</quote> used by some <trademark class="registered">UNIX</trademark> operating - systems.</para> + <para>透過仔細的設定每個啟動 Script 的這些關鍵字，管理者便可對 Script 的啟動順序進行微調，而不需使用到其他 <trademark class="registered">UNIX</trademark> 作業系統所使用的 <quote>runlevels</quote>。</para> - <para xml:lang="en">Additional information can be found in <citerefentry><refentrytitle>rc</refentrytitle><manvolnum>8</manvolnum></citerefentry> and - <citerefentry><refentrytitle>rc.subr</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Refer to <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/rc-scripting">this article</link> - for instructions on how to create custom <citerefentry><refentrytitle>rc</refentrytitle><manvolnum>8</manvolnum></citerefentry> - scripts.</para> + <para>額外的資訊可在 <citerefentry><refentrytitle>rc</refentrytitle><manvolnum>8</manvolnum></citerefentry> 以及 <citerefentry><refentrytitle>rc.subr</refentrytitle><manvolnum>8</manvolnum></citerefentry> 中找到。請參考 <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/rc-scripting">此文章</link> 來取得如何建立自訂 <citerefentry><refentrytitle>rc</refentrytitle><manvolnum>8</manvolnum></citerefentry> Script 的操作說明。</para> <sect2 xml:id="configtuning-core-configuration"> - <title>管理特定系統的設定</title> + <title>管理系統特定的設定</title> <indexterm xml:lang="en"> <primary>rc files</primary> <secondary><filename>rc.conf</filename></secondary> </indexterm> - <para xml:lang="en">The principal location for system configuration - information is <filename>/etc/rc.conf</filename>. This file - contains a wide range of configuration information and it is - read at system startup to configure the system. It provides - the configuration information for the - <filename>rc*</filename> files.</para> - - <para xml:lang="en">The entries in <filename>/etc/rc.conf</filename> override - the default settings in - <filename>/etc/defaults/rc.conf</filename>. The file - containing the default settings should not be edited. - Instead, all system-specific changes should be made to - <filename>/etc/rc.conf</filename>.</para> + <para>系統設定資訊的主要位於 <filename>/etc/rc.conf</filename>，這個檔案的設定資訊範圍非常廣且會在系統啟動時讀取來設定系統，它也提供設定資訊給 <filename>rc*</filename> 檔案使用。</para> + + <para>在 <filename>/etc/rc.conf</filename> 中的設定項目會覆蓋在 <filename>/etc/defaults/rc.conf</filename> 的預設設定，不應直接編輯該檔案中的預設設定，所有系統特定的設定應到 <filename>/etc/rc.conf</filename> 所修改。</para> - <para xml:lang="en">A number of strategies may be applied in clustered - applications to separate site-wide configuration from - system-specific configuration in order to reduce - administration overhead. The recommended approach is to place - system-specific configuration into - <filename>/etc/rc.conf.local</filename>. For example, these - entries in <filename>/etc/rc.conf</filename> apply to all - systems:</para> + <para>在叢集應用時要將系統特定的設定與各站特定的設定分開，藉此減少管理成本有好幾種方法，建議的方法是將系統特定的設定放置在 <filename>/etc/rc.conf.local</filename>，例如以下將要套用到所有系統的設定項目放在 <filename>/etc/rc.conf</filename>：</para> <programlisting xml:lang="en">sshd_enable="YES" keyrate="fast" defaultrouter="10.1.1.254"</programlisting> - <para xml:lang="en">Whereas these entries in - <filename>/etc/rc.conf.local</filename> apply to this system - only:</para> + <para>而只套用到此系統的設定放在 <filename>/etc/rc.conf.local</filename>：</para> <programlisting xml:lang="en">hostname="node1.example.org" ifconfig_fxp0="inet 10.1.1.1/8"</programlisting> - <para xml:lang="en">Distribute <filename>/etc/rc.conf</filename> to every - system using an application such as - <application>rsync</application> or - <application>puppet</application>, while - <filename>/etc/rc.conf.local</filename> remains - unique.</para> - - <para xml:lang="en">Upgrading the system will not overwrite - <filename>/etc/rc.conf</filename>, so system configuration - information will not be lost.</para> + <para>使用應用程式如 <application>rsync</application> 或 <application>puppet</application> 將 <filename>/etc/rc.conf</filename> 散布到每個系統，而在各系統保留自己的 <filename>/etc/rc.conf.local</filename>。</para> + + <para>升級系統並不會覆寫 <filename>/etc/rc.conf</filename>，所以系統設定資訊不會因此遺失。</para> <tip> - <para xml:lang="en">Both <filename>/etc/rc.conf</filename> and - <filename>/etc/rc.conf.local</filename> - are parsed by <citerefentry><refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum></citerefentry>. This allows system operators to - create complex configuration scenarios. Refer to - <citerefentry><refentrytitle>rc.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> for further information on this - topic.</para> + <para><filename>/etc/rc.conf</filename> 以及 <filename>/etc/rc.conf.local</filename> 兩個檔案都會使用 <citerefentry><refentrytitle>sh</refentrytitle><manvolnum>1</manvolnum></citerefentry> 解析，這讓系統操作者能夠建立較複雜的設定方案。請參考 <citerefentry><refentrytitle>rc.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> 來取得更多有關此主題的資訊。</para> </tip> </sect2> </sect1> @@ -14528,9 +14327,7 @@ ifconfig_fxp0="inet 10.1.1.1/8"</program <secondary>configuration</secondary> </indexterm> - <para xml:lang="en">Adding and configuring a network interface card - (<acronym>NIC</acronym>) is a common task for any FreeBSD - administrator.</para> + <para>對 FreeBSD 管理者來說加入與設定網路介面卡 (Network Interface Card, <acronym>NIC</acronym>) 會是一件常見的工作。</para> <sect2> <title>找到正確的驅動程式</title> @@ -14540,30 +14337,11 @@ ifconfig_fxp0="inet 10.1.1.1/8"</program <secondary>driver</secondary> </indexterm> - <para xml:lang="en">First, determine the model of the <acronym>NIC</acronym> - and the chip it uses. FreeBSD supports a wide variety of - <acronym>NIC</acronym>s. Check the Hardware Compatibility - List for the FreeBSD release to see if the <acronym>NIC</acronym> - is supported.</para> - - <para xml:lang="en">If the <acronym>NIC</acronym> is supported, determine - the name of the FreeBSD driver for the <acronym>NIC</acronym>. - Refer to <filename>/usr/src/sys/conf/NOTES</filename> and - <filename>/usr/src/sys/<replaceable>arch</replaceable>/conf/NOTES</filename> - for the list of <acronym>NIC</acronym> drivers with some - information about the supported chipsets. When in doubt, read - the manual page of the driver as it will provide more - information about the supported hardware and any known - limitations of the driver.</para> - - <para xml:lang="en">The drivers for common <acronym>NIC</acronym>s are already - present in the <filename>GENERIC</filename> kernel, meaning - the <acronym>NIC</acronym> should be probed during boot. The - system's boot messages can be viewed by typing - <command>more /var/run/dmesg.boot</command> and using the - spacebar to scroll through the text. In this example, two - Ethernet <acronym>NIC</acronym>s using the <citerefentry><refentrytitle>dc</refentrytitle><manvolnum>4</manvolnum></citerefentry> driver - are present on the system:</para> + <para>首先，要先確定 <acronym>NIC</acronym> 的型號及其使用的晶片。FreeBSD 支援各種 <acronym>NIC</acronym>，可檢查該 FreeBSD 發佈版本的硬體相容性清單來查看是否有支援該 <acronym>NIC</acronym>。</para> + + <para>若有支援該 <acronym>NIC</acronym>，接著要確定該 <acronym>NIC</acronym> 所要需要的 FreeBSD 驅動程式名稱。請參考 <filename>/usr/src/sys/conf/NOTES</filename> 及 <filename>/usr/src/sys/<replaceable>arch</replaceable>/conf/NOTES</filename> 來取得 <acronym>NIC</acronym> 驅動程式清單及其支援的晶片組相關資訊。當有疑問是，請閱讀該驅動程式的操作手冊，會有提供更多有關支援硬體及該驅動程式已知問題的資訊。</para> + + <para><filename>GENERIC</filename> 核心已有內含常見 <acronym>NIC</acronym> 的驅動程式 ，意思是在開機時應該會偵測到 <acronym>NIC</acronym>。可以輸入 <command>more /var/run/dmesg.boot</command> 來檢視系統的開機訊息並使用空白鍵捲動文字。在此例中，兩個乙太網路 <acronym>NIC</acronym> 使用系統已有的 <citerefentry><refentrytitle>dc</refentrytitle><manvolnum>4</manvolnum></citerefentry> 驅動程式：</para> <screen xml:lang="en">dc0: <82c169 PNIC 10/100BaseTX> port 0xa000-0xa0ff mem 0xd3800000-0xd38 000ff irq 15 at device 11.0 on pci0 @@ -14580,33 +14358,15 @@ bmtphy1: 10baseT, 10baseT-FDX, 100baseT dc1: Ethernet address: 00:a0:cc:da:da:db dc1: [ITHREAD]</screen> - <para xml:lang="en">If the driver for the <acronym>NIC</acronym> is not - present in <filename>GENERIC</filename>, but a driver is - available, the driver will need to be loaded before the - <acronym>NIC</acronym> can be configured and used. This may - be accomplished in one of two ways:</para> + <para>若在 <filename>GENERIC</filename> 中沒有該 <acronym>NIC</acronym> 的驅動程式，但有可用的驅動程式，那麼在設定及使用 <acronym>NIC</acronym> 前要先載入該驅動程式，有兩種方式可以完成這件事：</para> <itemizedlist> <listitem> - <para xml:lang="en">The easiest way is to load a kernel module for the - <acronym>NIC</acronym> using <citerefentry><refentrytitle>kldload</refentrytitle><manvolnum>8</manvolnum></citerefentry>. To also - automatically load the driver at boot time, add the - appropriate line to - <filename>/boot/loader.conf</filename>. Not all - <acronym>NIC</acronym> drivers are available as - modules.</para> + <para>最簡單的方式是使用 <citerefentry><refentrytitle>kldload</refentrytitle><manvolnum>8</manvolnum></citerefentry> 載入 <acronym>NIC</acronym> 要使用的核心模組。要在開機時自動載入，可加入適當的設定到 <filename>/boot/loader.conf</filename>。不是所有 <acronym>NIC</acronym> 驅動程式皆可當做模組使用。</para> </listitem> <listitem> - <para xml:lang="en">Alternatively, statically compile support for the - <acronym>NIC</acronym> into a custom kernel. Refer to - <filename>/usr/src/sys/conf/NOTES</filename>, - <filename>/usr/src/sys/<replaceable>arch</replaceable>/conf/NOTES</filename> - and the manual page of the driver to determine which line - to add to the custom kernel configuration file. For more - information about recompiling the kernel, refer to <xref linkend="kernelconfig"/>. If the <acronym>NIC</acronym> - was detected at boot, the kernel does not need to be - recompiled.</para> + <para>或者，靜態編譯對 <acronym>NIC</acronym> 的支援到自訂核心，請參考 <filename>/usr/src/sys/conf/NOTES</filename>, <filename>/usr/src/sys/<replaceable>arch</replaceable>/conf/NOTES</filename> 及驅動程式的操作手冊來了解要在自訂核心設定檔中要加入那些設定。要取得更多有關重新編譯核心的資訊可參考 <xref linkend="kernelconfig"/>。若在開機時有偵測到 <acronym>NIC</acronym>，就不需要再重新編譯核心。</para> </listitem> </itemizedlist> @@ -14634,85 +14394,46 @@ dc1: [ITHREAD]</screen> for it. Whatever is done must also be done to the same indexterm in linuxemu/chapter.xml --> - <para xml:lang="en">Unfortunately, there are still many vendors that do not - provide schematics for their drivers to the open source - community because they regard such information as trade - secrets. Consequently, the developers of FreeBSD and other - operating systems are left with two choices: develop the - drivers by a long and pain-staking process of reverse - engineering or using the existing driver binaries available - for <trademark class="registered">Microsoft</trademark> <trademark class="registered">Windows</trademark> platforms.</para> - - <para xml:lang="en">FreeBSD provides <quote>native</quote> support for the - Network Driver Interface Specification - (<acronym>NDIS</acronym>). It includes <citerefentry><refentrytitle>ndisgen</refentrytitle><manvolnum>8</manvolnum></citerefentry> - which can be used to convert a <trademark class="registered">Windows</trademark> XP driver into a - format that can be used on FreeBSD. Because the <citerefentry><refentrytitle>ndis</refentrytitle><manvolnum>4</manvolnum></citerefentry> - driver uses a <trademark class="registered">Windows</trademark> XP binary, it only runs on <trademark>i386</trademark> - and amd64 systems. <acronym>PCI</acronym>, CardBus, - <acronym>PCMCIA</acronym>, and <acronym>USB</acronym> - devices are supported.</para> + <para>很不幸的，仍有很多供應商並沒有提供它們驅動程式的技術文件給開源社群，因為這些文件有涉及商業機密。因此，FreeBSD 及其他作業系統的開發人員只剩下兩種方案可以選擇：透過長期與艱苦的過程做逆向工程來開發驅動程式或是使用現有供 <trademark class="registered">Microsoft</trademark> <trademark class="registered">Windows</trademark> 平台用的驅動程式 Binary。</para> + + <para>FreeBSD 對 Network Driver Interface Specification (<acronym>NDIS</acronym>) 有提供 <quote>原生</quote> 的支援，這包含了 <citerefentry><refentrytitle>ndisgen</refentrytitle><manvolnum>8</manvolnum></citerefentry> 可用來轉換 <trademark class="registered">Windows</trademark> XP 驅動程式成可在 FreeBSD 上使用的格式。由於 <citerefentry><refentrytitle>ndis</refentrytitle><manvolnum>4</manvolnum></citerefentry> 驅動程式使用的是 <trademark class="registered">Windows</trademark> XP binary，所以只能在 <trademark>i386</trademark> 及 amd64 系統上執行。<acronym>PCI</acronym>, CardBus, <acronym>PCMCIA</acronym> 以及 <acronym>USB</acronym> 裝置也都有支援。</para> - <para xml:lang="en">To use <citerefentry><refentrytitle>ndisgen</refentrytitle><manvolnum>8</manvolnum></citerefentry>, three things are needed:</para> + <para>要使用 <citerefentry><refentrytitle>ndisgen</refentrytitle><manvolnum>8</manvolnum></citerefentry> 需要三樣東西：</para> <orderedlist> <listitem> - <para xml:lang="en">FreeBSD kernel sources.</para> + <para>FreeBSD 核心原始碼。</para> </listitem> <listitem> - <para xml:lang="en">A <trademark class="registered">Windows</trademark> XP driver binary with a - <filename>.SYS</filename> extension.</para> + <para>一個 <filename>.SYS</filename> 附檔名的 <trademark class="registered">Windows</trademark> XP 驅動程式 Binary。</para> </listitem> <listitem> - <para xml:lang="en">A <trademark class="registered">Windows</trademark> XP driver configuration file with a - <filename>.INF</filename> extension.</para> + <para>一個 <filename>.INF</filename> 附檔名的 <trademark class="registered">Windows</trademark> XP 驅動程式設定檔。</para> </listitem> </orderedlist> - <para xml:lang="en">Download the <filename>.SYS</filename> and - <filename>.INF</filename> files for the specific - <acronym>NIC</acronym>. Generally, these can be found on - the driver CD or at the vendor's website. The following - examples use <filename>W32DRIVER.SYS</filename> and - <filename>W32DRIVER.INF</filename>.</para> - - <para xml:lang="en">The driver bit width must match the version of FreeBSD. - For FreeBSD/i386, use a <trademark class="registered">Windows</trademark> 32-bit driver. For - FreeBSD/amd64, a <trademark class="registered">Windows</trademark> 64-bit driver is needed.</para> - - <para xml:lang="en">The next step is to compile the driver binary into a - loadable kernel module. As - <systemitem class="username">root</systemitem>, use - <citerefentry><refentrytitle>ndisgen</refentrytitle><manvolnum>8</manvolnum></citerefentry>:</para> + <para>下載供指定 <acronym>NIC</acronym> 使用的 <filename>.SYS</filename> 及 <filename>.INF</filename> 檔。通常這些檔案可以在驅動程式 CD 或者供應商的網站上找到。以下範例會使用 <filename>W32DRIVER.SYS</filename> 及 <filename>W32DRIVER.INF</filename>。</para> + + <para>驅動程式的位元寬度必須與 FreeBSD 的版本相符。例如 FreeBSD/i386 需要使用 <trademark class="registered">Windows</trademark> 32-bit 驅動程式，而 FreeBSD/amd64 則需要使用 <trademark class="registered">Windows</trademark> 64-bit 驅動程式。</para> + + <para>下個步驟是編譯驅動程式 Binary 成可載入的核心模組。以 <systemitem class="username">root</systemitem> 身份使用 <citerefentry><refentrytitle>ndisgen</refentrytitle><manvolnum>8</manvolnum></citerefentry>：</para> <screen xml:lang="en"><prompt>#</prompt> <userinput>ndisgen <replaceable>/path/to/W32DRIVER.INF</replaceable> <replaceable>/path/to/W32DRIVER.SYS</replaceable></userinput></screen> - <para xml:lang="en">This command is interactive and prompts for any extra - information it requires. A new kernel module will be - generated in the current directory. Use <citerefentry><refentrytitle>kldload</refentrytitle><manvolnum>8</manvolnum></citerefentry> - to load the new module:</para> + <para>這個指令是互動式的，會提示輸入任何所需的額外資訊，新的核心模組會被產生在目前的目錄，使用 <citerefentry><refentrytitle>kldload</refentrytitle><manvolnum>8</manvolnum></citerefentry> 來載入新的模組：</para> <screen xml:lang="en"><prompt>#</prompt> <userinput>kldload <replaceable>./W32DRIVER_SYS.ko</replaceable></userinput></screen> - <para xml:lang="en">In addition to the generated kernel module, the - <filename>ndis.ko</filename> and - <filename>if_ndis.ko</filename> modules must be loaded. - This should happen automatically when any module that - depends on <citerefentry><refentrytitle>ndis</refentrytitle><manvolnum>4</manvolnum></citerefentry> is loaded. If not, load them - manually, using the following commands:</para> + <para>除了產生的核心模組之外，<filename>ndis.ko</filename> 以及 <filename>if_ndis.ko</filename> 也必須載入，會在任何有相依 <citerefentry><refentrytitle>ndis</refentrytitle><manvolnum>4</manvolnum></citerefentry> 的模組被載入時一併自動載入。若沒有自動載入，則需使用以下指令手動載入：</para> <screen xml:lang="en"><prompt>#</prompt> <userinput>kldload ndis</userinput> <prompt>#</prompt> <userinput>kldload if_ndis</userinput></screen> - <para xml:lang="en">The first command loads the <citerefentry><refentrytitle>ndis</refentrytitle><manvolnum>4</manvolnum></citerefentry> miniport driver - wrapper and the second loads the generated - <acronym>NIC</acronym> driver.</para> - - <para xml:lang="en">Check <citerefentry><refentrytitle>dmesg</refentrytitle><manvolnum>8</manvolnum></citerefentry> to see if there were any load - errors. If all went well, the output should be similar to - the following:</para> + <para>第一個指令會載入 <citerefentry><refentrytitle>ndis</refentrytitle><manvolnum>4</manvolnum></citerefentry> miniport 驅動程式包裝程式，而第二個指令會載入產生的 <acronym>NIC</acronym> 驅動程式。</para> + + <para>檢查 <citerefentry><refentrytitle>dmesg</refentrytitle><manvolnum>8</manvolnum></citerefentry> 查看是否有任何載入錯誤，若一切正常，輸出結果應會如下所示：</para> <screen xml:lang="en">ndis0: <Wireless-G PCI Adapter> mem 0xf4100000-0xf4101fff irq 3 at device 8.0 on pci1 ndis0: NDIS API version: 5.0 @@ -14720,14 +14441,9 @@ ndis0: Ethernet address: 0a:b1:2c:d3:4e: ndis0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18Mbps 36Mbps 48Mbps 54Mbps</screen> - <para xml:lang="en">From here, <filename>ndis0</filename> can be - configured like any other <acronym>NIC</acronym>.</para> + <para>到此之後 <filename>ndis0</filename> 可以像任何其他 <acronym>NIC</acronym> 設定使用。</para> - <para xml:lang="en">To configure the system to load the <citerefentry><refentrytitle>ndis</refentrytitle><manvolnum>4</manvolnum></citerefentry> modules - at boot time, copy the generated module, - <filename>W32DRIVER_SYS.ko</filename>, to - <filename>/boot/modules</filename>. Then, add the following - line to <filename>/boot/loader.conf</filename>:</para> + <para>要設定系統於開機時載入 <citerefentry><refentrytitle>ndis</refentrytitle><manvolnum>4</manvolnum></citerefentry> 模組，可複製產生的模組 <filename>W32DRIVER_SYS.ko</filename> 到 <filename>/boot/modules</filename>。然後加入下行到 <filename>/boot/loader.conf</filename>：</para> <programlisting xml:lang="en">W32DRIVER_SYS_load="YES"</programlisting> </sect3> @@ -14741,13 +14457,9 @@ ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18M <secondary>configuration</secondary> </indexterm> - <para xml:lang="en">Once the right driver is loaded for the - <acronym>NIC</acronym>, the card needs to be configured. It - may have been configured at installation time by - <citerefentry><refentrytitle>bsdinstall</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para> + <para>載入正確的 <acronym>NIC</acronym> 驅動程式之後，接著需要設定介面卡，這個動作可能在安裝時已經使用 <citerefentry><refentrytitle>bsdinstall</refentrytitle><manvolnum>8</manvolnum></citerefentry> 設定過了。</para> - <para xml:lang="en">To display the <acronym>NIC</acronym> configuration, - enter the following command:</para> + <para>要查看 <acronym>NIC</acronym> 設定可輸入以下指令：</para> <screen xml:lang="en"><prompt>%</prompt> <userinput>ifconfig</userinput> dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 @@ -14769,85 +14481,57 @@ lo0: flags=8049<UP,LOOPBACK,RUNNING,M inet 127.0.0.1 netmask 0xff000000 nd6 options=3<PERFORMNUD,ACCEPT_RTADV></screen> - <para xml:lang="en">In this example, the following devices were - displayed:</para> + <para>在這個例子中列出了以下裝置：</para> <itemizedlist> <listitem> - <para xml:lang="en"><filename>dc0</filename>: The first Ethernet - interface.</para> + <para><filename>dc0</filename>: 第一個乙太網路介面。</para> </listitem> <listitem> - <para xml:lang="en"><filename>dc1</filename>: The second Ethernet - interface.</para> + <para><filename>dc1</filename>: 第二個乙太網路介面。</para> </listitem> <listitem> - <para xml:lang="en"><filename>lo0</filename>: The loopback - device.</para> + <para><filename>lo0</filename>: Loopback 裝置。</para> </listitem> </itemizedlist> - <para xml:lang="en">FreeBSD uses the driver name followed by the order in which - the card is detected at boot to name the - <acronym>NIC</acronym>. For example, - <filename>sis2</filename> is the third - <acronym>NIC</acronym> on the system using the <citerefentry><refentrytitle>sis</refentrytitle><manvolnum>4</manvolnum></citerefentry> - driver.</para> + <para>FreeBSD 會使用驅動程式名稱接著開機時所偵測到的介面卡順序來命名 <acronym>NIC</acronym>。例如 <filename>sis2</filename> 是指在系統上使用 <citerefentry><refentrytitle>sis</refentrytitle><manvolnum>4</manvolnum></citerefentry> 驅動程式的第三個 <acronym>NIC</acronym>。</para> - <para xml:lang="en">In this example, <filename>dc0</filename> is up and - running. The key indicators are:</para> + <para>在此例中，<filename>dc0</filename> 已經上線並且執行中。主要的依據有：</para> <orderedlist> <listitem> - <para xml:lang="en"><literal>UP</literal> means that the card is - configured and ready.</para> + <para><literal>UP</literal> 代表介面卡已設定好並且準備就緒。</para> </listitem> <listitem> - <para xml:lang="en">The card has an Internet (<literal>inet</literal>) - address, <systemitem class="ipaddress">192.168.1.3</systemitem>.</para> + <para>介面卡有網際網路 (<literal>inet</literal>) 位址，<systemitem class="ipaddress">192.168.1.3</systemitem>。</para> </listitem> <listitem> - <para xml:lang="en">It has a valid subnet mask - (<literal>netmask</literal>), where - <systemitem class="netmask">0xffffff00</systemitem> is the - same as <systemitem class="netmask">255.255.255.0</systemitem>.</para> + <para>介面卡有一個有效的子網路遮罩 (<literal>netmask</literal>)，其中 <systemitem class="netmask">0xffffff00</systemitem> 等同於 <systemitem class="netmask">255.255.255.0</systemitem>。</para> </listitem> <listitem> - <para xml:lang="en">It has a valid broadcast address, <systemitem class="ipaddress">192.168.1.255</systemitem>.</para> + <para>介面卡有一個有效的廣播位址，<systemitem class="ipaddress">192.168.1.255</systemitem>。</para> </listitem> <listitem> - <para xml:lang="en">The <acronym>MAC</acronym> address of the card - (<literal>ether</literal>) is <systemitem class="etheraddress">00:a0:cc:da:da:da</systemitem>.</para> + <para>介面卡 (<literal>ether</literal>) 的 <acronym>MAC</acronym> 位址是 <systemitem class="etheraddress">00:a0:cc:da:da:da</systemitem>。</para> </listitem> <listitem> - <para xml:lang="en">The physical media selection is on autoselection mode - (<literal>media: Ethernet autoselect (100baseTX - <full-duplex>)</literal>). In this example, - <filename>dc1</filename> is configured to run with - <literal>10baseT/UTP</literal> media. For more - information on available media types for a driver, refer - to its manual page.</para> + <para>實體媒介選擇為自動選擇模式 (<literal>media: Ethernet autoselect (100baseTX <full-duplex>)</literal>)。在本例中 <filename>dc1</filename> 被設定使用 <literal>10baseT/UTP</literal> 媒介。要取得更多有關可用的驅動程式媒介類型請參考操作手冊。</para> </listitem> <listitem> - <para xml:lang="en">The status of the link (<literal>status</literal>) is - <literal>active</literal>, indicating that the carrier - signal is detected. For <filename>dc1</filename>, the - <literal>status: no carrier</literal> status is normal - when an Ethernet cable is not plugged into the - card.</para> + <para>連結的狀態 (<literal>status</literal>) 為使用中 (<literal>active</literal>)，代表有偵測到載波信號 (Carrier Signal)。若 <filename>dc1</filename> 所代表的介面卡未插入乙太網路線則狀態為 <literal>status: no carrier</literal> 是正常的。</para> </listitem> </orderedlist> - <para xml:lang="en">If the <citerefentry><refentrytitle>ifconfig</refentrytitle><manvolnum>8</manvolnum></citerefentry> output had shown something similar - to:</para> + <para>若 <citerefentry><refentrytitle>ifconfig</refentrytitle><manvolnum>8</manvolnum></citerefentry> 的輸出結果如下：</para> <screen xml:lang="en">dc0: flags=8843<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=80008<VLAN_MTU,LINKSTATE> @@ -14855,58 +14539,31 @@ lo0: flags=8049<UP,LOOPBACK,RUNNING,M media: Ethernet autoselect (100baseTX <full-duplex>) status: active</screen> - <para xml:lang="en">it would indicate the card has not been configured.</para> + <para>則代表尚未設定介面卡。</para> - <para xml:lang="en">The card must be configured as - <systemitem class="username">root</systemitem>. The - <acronym>NIC</acronym> configuration can be performed from the - command line with <citerefentry><refentrytitle>ifconfig</refentrytitle><manvolnum>8</manvolnum></citerefentry> but will not persist after - a reboot unless the configuration is also added to - <filename>/etc/rc.conf</filename>. If a - <acronym>DHCP</acronym> server is present on the LAN, - just add this line:</para> + <para>介面卡必須以 <systemitem class="username">root</systemitem> 來設定。<acronym>NIC</acronym> 的設定可在指令列執行 <citerefentry><refentrytitle>ifconfig</refentrytitle><manvolnum>8</manvolnum></citerefentry> 來完成，但重新開機之後變會消失，除非將設定也加到 <filename>/etc/rc.conf</filename>。若在 LAN 中有 <acronym>DHCP</acronym> 伺服器，則只需加入此行：</para> <programlisting xml:lang="en">ifconfig_dc0="DHCP"</programlisting> - <para xml:lang="en">Replace <replaceable>dc0</replaceable> with the correct value - for the system.</para> + <para>替換 <replaceable>dc0</replaceable> 為該系統的正確值。</para> - <para xml:lang="en">The line added, then, follow the instructions given in - <xref linkend="config-network-testing"/>.</para> + <para>加入這行之後，接著依據 <xref linkend="config-network-testing"/> 指示操作。</para> <note> - <para xml:lang="en">If the network was configured during installation, some - entries for the <acronym>NIC</acronym>(s) may be already - present. Double check <filename>/etc/rc.conf</filename> - before adding any lines.</para> + <para>若網路在安裝時已設定，可能會已經有 <acronym>NIC</acronym> 的設定項目。在加入任何設定前請再次檢查 <filename>/etc/rc.conf</filename>。 </para> </note> - <para xml:lang="en">In the case, there is no <acronym>DHCP</acronym> server, - the <acronym>NIC</acronym>(s) have to be configured manually. - Add a line for each <acronym>NIC</acronym> present on the - system, as seen in this example:</para> + <para>在這個例中，沒有 <acronym>DHCP</acronym> 伺服器，必須手動設定 <acronym>NIC</acronym>。提每一個在系統上的 <acronym>NIC</acronym> 加入一行設定，如此例：</para> <programlisting xml:lang="en">ifconfig_dc0="inet 192.168.1.3 netmask 255.255.255.0" ifconfig_dc1="inet 10.0.0.1 netmask 255.255.255.0 media 10baseT/UTP"</programlisting> - <para xml:lang="en">Replace <filename>dc0</filename> and - <filename>dc1</filename> and the <acronym>IP</acronym> - address information with the correct values for the system. - Refer to the man page for the driver, <citerefentry><refentrytitle>ifconfig</refentrytitle><manvolnum>8</manvolnum></citerefentry>, and - <citerefentry><refentrytitle>rc.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> for more details about the allowed options and - the syntax of <filename>/etc/rc.conf</filename>.</para> - - <para xml:lang="en">If the network is not using <acronym>DNS</acronym>, edit - <filename>/etc/hosts</filename> to add the names and - <acronym>IP</acronym> addresses of the hosts on the - <acronym>LAN</acronym>, if they are not already there. For - more information, refer to <citerefentry><refentrytitle>hosts</refentrytitle><manvolnum>5</manvolnum></citerefentry> and to *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201701040847.v048lROH086834>