- Update to (20060707) svn#702
PR: docs/99891 Submitted by: chinsan.tw at gmail.com
This commit is contained in:
Vanilla I. Shu
parent
90e8e254b4
commit
e58c95c517
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=28215
5 changed files with 81 additions and 404 deletions
|
|
@ -38,50 +38,46 @@
|
|||
<indexterm><primary>system configuration</primary></indexterm>
|
||||
<indexterm><primary>system optimization</primary></indexterm>
|
||||
|
||||
<para>One of the important aspects of &os; is system configuration.
|
||||
Correct system configuration will help prevent headaches during future upgrades.
|
||||
This chapter will explain much of the &os; configuration process,
|
||||
including some of the parameters which
|
||||
can be set to tune a &os; system.
|
||||
<para>在 &os; 使用過程中，相當重要的環節之一就是系統設定部分。
|
||||
正確的系統設定，可以讓你減輕日後升級的頭痛壓力。
|
||||
本章著重於介紹 &os; 的相關重要設定上，包括一些可以調整 &os; 效能的參數設定。
|
||||
</para>
|
||||
|
||||
<para>讀完這章，您將了解：</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>How to efficiently work with
|
||||
file systems and swap partitions.</para>
|
||||
<para>如何有效運用檔案系統以及 swap 分割區。</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><filename>rc.conf</filename> 的設定與 <filename>/usr/local/etc/rc.d</filename> 的啟動架構；</para>
|
||||
<para><filename>rc.conf</filename> 的設定與 <filename>/usr/local/etc/rc.d</filename> 的啟動架構。</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>如何設定、測試網路卡；</para>
|
||||
<para>如何設定、測試網路卡。</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>How to configure virtual hosts on your network devices.</para>
|
||||
<para>如何設定 virtual hosts。</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>如何設定 <filename>/etc</filename> 內的各種設定檔。</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>如何以 <command>sysctl</command> 來調整 &os; 的系統效能；</para>
|
||||
<para>如何以 <command>sysctl</command> 來調整 &os; 的系統效能。</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>如何調整硬碟效能，以及更改 kernel 限制。</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>在閱讀這章之前，您應當了解：</para>
|
||||
<para>在開始閱讀這章之前，您需要︰</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Understand &unix; and &os; basics (<xref
|
||||
linkend="basics">).</para>
|
||||
<para>瞭解 &unix; 及 &os; 相關基本概念(<xref
|
||||
linkend="basics">)。</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Be familiar with the basics of kernel configuration/compilation
|
||||
(<xref linkend="kernelconfig">).</para>
|
||||
<para>要有設定、編譯 kernel 的基礎概念(<xref linkend="kernelconfig">)。</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</sect1>
|
||||
|
|
@ -106,57 +102,45 @@
|
|||
<sect3>
|
||||
<title>Base Partitions</title>
|
||||
|
||||
<para>When laying out file systems with &man.disklabel.8;
|
||||
or &man.sysinstall.8;, remember that hard
|
||||
drives transfer data faster from the outer
|
||||
tracks to the inner.
|
||||
Thus smaller and heavier-accessed file systems
|
||||
should be closer to the outside of the drive, while
|
||||
larger partitions like <filename>/usr</filename> should be placed
|
||||
toward the inner. It is a good idea to create
|
||||
partitions in a similar order to: root, swap,
|
||||
<filename>/var</filename>, <filename>/usr</filename>.</para>
|
||||
<para>用 &man.disklabel.8; 或 &man.sysinstall.8; 來規劃檔案系統時，請記住：
|
||||
硬碟在傳輸資料方面，(由於結構為碟片因素)外圈會比內圈來得快些。
|
||||
因此，建議把較小、常會存取的分割區儘量放外圈，而較大的分割區像是
|
||||
<filename>/usr</filename> 則應放在較內圈。
|
||||
建議建立分割區的順序，以像是：root, swap,
|
||||
<filename>/var</filename>, <filename>/usr</filename> 這樣順序來建立會較妥。</para>
|
||||
|
||||
<para>The size of <filename>/var</filename>
|
||||
reflects the intended machine usage.
|
||||
<filename>/var</filename> is used to hold
|
||||
mailboxes, log files, and printer spools. Mailboxes and log
|
||||
files can grow to unexpected sizes depending
|
||||
on how many users exist and how long log
|
||||
files are kept. Most users would never require a gigabyte,
|
||||
but remember that <filename>/var/tmp</filename>
|
||||
must be large enough to contain packages.
|
||||
<para><filename>/var</filename> 的大小要視機器的用途而定。
|
||||
<filename>/var</filename> 是用來放
|
||||
信箱、log 紀錄檔以及印表機佇列(spools)。 信箱以及記錄檔的成長幅度可能無法預估，
|
||||
因為這些成長幅度乃是取決於多少用戶、要放多久等管理原則而定。
|
||||
通常這些使用者並沒有用到 1 GB 以上，但請切記：至少要保留一定空間給 <filename>/var/tmp</filename>
|
||||
以便存放 packages。
|
||||
</para>
|
||||
|
||||
<para>The <filename>/usr</filename> partition holds much
|
||||
of the files required to support the system, the &man.ports.7;
|
||||
collection (recommended) and the source code (optional). Both
|
||||
of which are optional at install time.
|
||||
At least 2 gigabytes would be recommended for this partition.</para>
|
||||
<para>而 <filename>/usr</filename> 分割區主要是用來放系統運作時所需的檔案、工具程式等，例如：
|
||||
&man.ports.7; collection(建議安裝)跟 source tree(optional)。
|
||||
在安裝 FreeBSD 時，這兩者都是可選擇裝與不裝的。
|
||||
不過，這個分割區建議至少要有 2 GB 空間以上才夠用。</para>
|
||||
|
||||
<para>When selecting partition sizes, keep the space
|
||||
requirements in mind. Running out of space in
|
||||
one partition while barely using another can be a
|
||||
hassle.</para>
|
||||
<para>規劃分割區大小時，記得多保留些成長空間。
|
||||
否則若某個分割區滿了，但另一個分割區卻還剩很多空間，就會相當困窘。</para>
|
||||
|
||||
<note><para>Some users have found that &man.sysinstall.8;'s
|
||||
<literal>Auto-defaults</literal> partition sizer will
|
||||
sometimes select smaller than adequate <filename>/var</filename>
|
||||
and <filename>/</filename> partitions. Partition wisely and
|
||||
generously.</para></note>
|
||||
<note><para>有些人可能會發現 &man.sysinstall.8; 的
|
||||
<literal>Auto-defaults(自動預設值)</literal> 所做的分割區大小，
|
||||
有時候會把 <filename>/var</filename> 以及 <filename>/</filename> 分割區設太小了。
|
||||
我們建議是：請依使用情況以及需求，來手動調整相關分割區大小。</para></note>
|
||||
|
||||
</sect3>
|
||||
|
||||
<sect3 id="swap-design">
|
||||
<title>Swap Partition</title>
|
||||
<title>Swap 分割區</title>
|
||||
|
||||
<indexterm><primary>swap sizing</primary></indexterm>
|
||||
<indexterm><primary>swap partition</primary></indexterm>
|
||||
|
||||
<para>As a rule of thumb, the swap partition should be
|
||||
about double the size of system memory (RAM). For example,
|
||||
if the machine has 128 megabytes of memory,
|
||||
the swap file should be 256 megabytes. Systems with
|
||||
<para>根據經驗法則，通常 swap 分割區應該設為系統記憶體(RAM)大小的兩倍即可。
|
||||
舉例來說：若機器有 128 MB RAM 的話，那麼
|
||||
swap 則應該設為 256 MB。 Systems with
|
||||
less memory may perform better with more swap.
|
||||
Less than 256 megabytes of swap is not recommended and
|
||||
memory expansion should be considered.
|
||||
|
|
|
|||
|
|
@ -2,27 +2,23 @@
|
|||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD$
|
||||
Take translation from Kang-min Liu <gugod@gugod.org>
|
||||
Original revision: 1.175
|
||||
-->
|
||||
|
||||
<appendix id="eresources">
|
||||
<title>Resources on the Internet</title>
|
||||
<title>網際網路上的資源</title>
|
||||
|
||||
<para>The rapid pace of FreeBSD progress makes print media impractical as a
|
||||
means of following the latest developments. Electronic resources are the
|
||||
best, if not often the only, way stay informed of the latest advances.
|
||||
Since FreeBSD is a volunteer effort, the user community itself also
|
||||
generally serves as a <quote>technical support department</quote> of sorts,
|
||||
with electronic mail and USENET news being the most effective way of
|
||||
reaching that community.</para>
|
||||
<para>進展飛快的 FreeBSD 使得現有的印刷、平面媒體跟不上它的最新進度！
|
||||
反而數位版本的資源，也許有時並不是最好，但通常是唯一一個跟上最新進展的方式。
|
||||
正由於 FreeBSD 是來自於許多志工的努力，所以廣大的使用者群也通常扮演著 <quote>IT技術支援部門</quote> 的角色。
|
||||
只要善用電子郵件和 USENET 新聞群組就可以很快速地聯繫這些社群了。</para>
|
||||
|
||||
<para>The most important points of contact with the FreeBSD user community
|
||||
are outlined below. If you are aware of other resources not mentioned
|
||||
here, please send them to the &a.doc; so that they may also be
|
||||
included.</para>
|
||||
<para>以下簡介與 FreeBSD 社群搭上線的主要方式。
|
||||
若你還知道其他這裡沒有列出的資源，請告知 &a.doc;，以便我們更新。</para>
|
||||
|
||||
<sect1 id="eresources-mail">
|
||||
<title>Mailing Lists</title>
|
||||
<title>郵遞論壇(Mailing Lists)</title>
|
||||
|
||||
<para>Though many of the FreeBSD development members read USENET, we
|
||||
cannot always guarantee that we will get to your questions in a timely
|
||||
|
|
|
|||
|
|
@ -483,11 +483,9 @@ pqb0.0.1.4.0 PQB0 PCI EIDE</screen>
|
|||
&os; &rel.current;-RELEASE ，那麼可以到 <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/floppies/"></ulink> 下載。</para>
|
||||
|
||||
<para>映像檔(images)的附檔名都是 <filename>.flp</filename> 。而
|
||||
<filename>floppies/</filename> 目錄內包含一些不同用途的映像檔(images)，這取決於您要裝的 FreeBSD 版本、需求、硬體配備為何。
|
||||
若要裝的是
|
||||
FreeBSD 4.X 那麼通常只需要 2 個映像檔，也就是 <filename>kern.flp</filename> 與
|
||||
<filename>mfsroot.flp</filename>。而若要裝的是 FreeBSD 5.X
|
||||
，那麼通常要 3 個映像檔，也就是： <filename>boot.flp</filename>、
|
||||
<filename>floppies/</filename> 目錄內包含一些不同用途的映像檔(images)，
|
||||
這取決於您要裝的 FreeBSD 版本、需求、硬體配備為何。
|
||||
通常要 3 個映像檔，也就是： <filename>boot.flp</filename>、
|
||||
<filename>kern1.flp</filename>、
|
||||
<filename>kern2.flp</filename>。若有疑問的話，請翻閱同一目錄下的
|
||||
<filename>README.TXT</filename> 文件檔，以瞭解相關最新注意事項。</para>
|
||||
|
|
@ -677,8 +675,7 @@ Please insert MFS root floppy and press enter:</screen>
|
|||
<screen>Hit [Enter] to boot immediately, or any other key for command prompt.
|
||||
Booting [kernel] in 9 seconds... _</screen>
|
||||
|
||||
<para>您可以等待 10 秒，或是按 <keycap>Enter</keycap> 鍵。
|
||||
(若是 &os; 4.X 的話，則將出現 kernel configuration 選單畫面)</para>
|
||||
<para>您可以等待 10 秒，或是按 <keycap>Enter</keycap> 鍵。</para>
|
||||
</step>
|
||||
</procedure>
|
||||
|
||||
|
|
@ -732,277 +729,6 @@ Booting [kernel] in 9 seconds... _</screen>
|
|||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="start-userconfig">
|
||||
<title>Kernel 的設定</title>
|
||||
|
||||
<note><para>從 FreeBSD 5.0 版開始，改用新的 &man.device.hints.5; 方式，而淘汰舊的 userconfig 方式。
|
||||
關於 &man.device.hints.5; 機制的細節介紹，請參閱 <xref linkend="device-hints">。</para></note>
|
||||
|
||||
<para><firstterm>kernel</firstterm> 乃是作業系統中的核心，負責許多事情，像是：控制系統上所有設備，比如硬碟、網路卡、音效卡等。
|
||||
每項 FreeBSD 所支援的硬體都有相對應的驅動程式。
|
||||
每個驅動程式名稱都有 2 到 3 個字母所組成，像是 <devicename>sa</devicename> 代表 SCSI 驅動程式，而
|
||||
<devicename>sio</devicename> 代表 Serial I/O 驅動程式(管 COM ports 用的)。</para>
|
||||
|
||||
<para>當 kernel 開始啟動時，每個驅動程式就會去檢查系統上是否有支援的硬體存在，
|
||||
若有的話，驅動程式就會作相關硬體設定，以便讓 kernel 使用該硬體。</para>
|
||||
|
||||
<para>上述的檢查動作，我們稱為 <firstterm>device probing(偵測硬體)</firstterm>。
|
||||
但是，這樣子的方式並不是永遠都那麼順利。
|
||||
有些硬體驅動程式無法同時共存，而有時候偵測某硬體時，又會造成另一硬體不穩出槌。
|
||||
這問題，乃是由於 <acronym>PC</acronym> 本身設計上天生的限制所致。</para>
|
||||
|
||||
<para>Many older devices are called ISA devices—as opposed
|
||||
to PCI devices. The ISA specification requires each device to have
|
||||
some information hard coded into it, typically the Interrupt Request
|
||||
Line number (IRQ) and IO port address that the driver uses. This
|
||||
information is commonly set by using physical
|
||||
<firstterm>jumpers</firstterm> on the card, or by using a DOS based
|
||||
utility.</para>
|
||||
|
||||
<para>This was often a source of problems, because it was not possible
|
||||
to have two devices that shared the same IRQ or port address.</para>
|
||||
|
||||
<para>Newer devices follow the PCI specification, which does not require
|
||||
this, as the devices are supposed to cooperate with the BIOS, and are
|
||||
told which IRQ and IO port addresses to use.</para>
|
||||
|
||||
<para>If you have any ISA devices in your computer then FreeBSD's
|
||||
driver for that device will need to be configured with the IRQ and
|
||||
port address that you have set the card to. This is why carrying out
|
||||
an inventory of your hardware (see <xref
|
||||
linkend="install-inventory">) can be useful.</para>
|
||||
|
||||
<para>Unfortunately, the default IRQs and memory ports used by some
|
||||
drivers clash. This is because some ISA devices are shipped with IRQs
|
||||
or memory ports that clash. The defaults in FreeBSD's drivers are
|
||||
deliberately set to mirror the manufacturer's defaults, so that, out
|
||||
of the box, as many devices as possible will work.</para>
|
||||
|
||||
<para>This is almost never an issue when running FreeBSD day-to-day.
|
||||
Your computer will not normally contain two pieces of hardware that
|
||||
clash, because one of them would not work (irrespective of the
|
||||
operating system you are using).</para>
|
||||
|
||||
<para>It becomes an issue when you are installing FreeBSD for the first
|
||||
time because the kernel used to carry out the install has to contain
|
||||
as many drivers as possible, so that many different hardware
|
||||
configurations can be supported. This means that some of
|
||||
those drivers will have conflicting configurations. The devices are
|
||||
probed in a strict order, and if you own a device that is probed late
|
||||
in the process, but conflicted with an earlier probe, then your
|
||||
hardware might not function or be probed correctly when you install
|
||||
FreeBSD.</para>
|
||||
|
||||
<para>Because of this, the first thing you have the opportunity to do
|
||||
when installing FreeBSD is look at the list of drivers that are
|
||||
configured into the kernel, and either disable some of them, if you
|
||||
do not own that device, or confirm (and alter) the driver's
|
||||
configuration if you do own the device but the defaults are
|
||||
wrong.</para>
|
||||
|
||||
<para>This probably sounds much more complicated than it actually
|
||||
is.</para>
|
||||
|
||||
<para><xref linkend="kernel-config"> shows the first kernel
|
||||
configuration menu. We recommend that you choose the
|
||||
<guimenuitem>Start kernel configuration in full-screen visual
|
||||
mode</guimenuitem> option, as it presents the easiest interface for
|
||||
the new user.</para>
|
||||
|
||||
<figure id="kernel-config">
|
||||
<title>Kernel 設定畫面</title>
|
||||
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="install/userconfig" format="PNG">
|
||||
</imageobject>
|
||||
|
||||
<textobject>
|
||||
<screen>&txt.install.userconfig;</screen>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</figure>
|
||||
|
||||
<para>The kernel configuration screen (<xref linkend="fig-userconfig">)
|
||||
is then divided into four sections:</para>
|
||||
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>A collapsible list of all the drivers that are currently
|
||||
marked as <quote>active</quote>, subdivided into groups such as
|
||||
<literal>Storage</literal>, and <literal>Network</literal>. Each
|
||||
driver is shown as a description, its two or three letter driver
|
||||
name, and the IRQ and memory port used by that driver. In
|
||||
addition, if an active driver conflicts with another active driver
|
||||
then <literal>CONF</literal> is shown next to the driver name.
|
||||
This section also shows the total number of conflicting drivers
|
||||
that are currently active.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Drivers that have been marked inactive. They remain in the
|
||||
kernel, but they will not probe for their device when the kernel
|
||||
starts. These are subdivided into groups in the same way as the
|
||||
active driver list.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>More detail about the currently selected driver, including its
|
||||
IRQ and memory port address.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Information about the keystrokes that are valid at this point
|
||||
in time.</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
|
||||
<figure id="fig-userconfig">
|
||||
<title>Kernel Device 的設定畫面</title>
|
||||
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="install/userconfig2" format="PNG">
|
||||
</imageobject>
|
||||
|
||||
<textobject>
|
||||
<screen>&txt.install.userconfig2;</screen>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</figure>
|
||||
|
||||
<para>Do not worry if any conflicts are listed,
|
||||
it is to be expected; all the drivers are enabled, and
|
||||
as has already been explained, some of them will conflict with one
|
||||
another.</para>
|
||||
|
||||
<para>You now have to work through the list of drivers, resolving the
|
||||
conflicts.</para>
|
||||
|
||||
<procedure>
|
||||
<title>解除相衝的驅動程式</title>
|
||||
|
||||
<step>
|
||||
<para>Press <keycap>X</keycap>. This will completely expand the
|
||||
list of drivers, so you can see all of them. You will need to use
|
||||
the arrow keys to scroll back and forth through the active driver
|
||||
list.</para>
|
||||
|
||||
<para><xref linkend="hardware-conflicts"> shows the result of
|
||||
pressing <keycap>X</keycap>.</para>
|
||||
|
||||
<figure id="hardware-conflicts">
|
||||
<title>展開驅動程式一覽表</title>
|
||||
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="install/hdwrconf" format="PNG">
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
</figure>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>Disable all the drivers for devices that you do not have. To
|
||||
disable a driver, highlight it with the arrow keys and press
|
||||
<keycap>Del</keycap>. The driver will be moved to the
|
||||
<literal>Inactive Drivers</literal> list.</para>
|
||||
|
||||
<para>If you inadvertently disable a device that you need then press
|
||||
<keycap>Tab</keycap> to switch to the <literal>Inactive
|
||||
Drivers</literal> list, select the driver that you disabled, and
|
||||
press <keycap>Enter</keycap> to move it back to the active
|
||||
list.</para>
|
||||
|
||||
<warning>
|
||||
<para>Do not disable <devicename>sc0</devicename>. This controls
|
||||
the screen, and you will need this unless you are installing
|
||||
over a serial cable.</para>
|
||||
</warning>
|
||||
|
||||
<warning>
|
||||
<para>Only disable <devicename>atkbd0</devicename> if you are
|
||||
using a USB keyboard. If you have a normal keyboard then you
|
||||
must keep <devicename>atkbd0</devicename>.</para>
|
||||
</warning>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>If there are no conflicts listed then you can skip this step.
|
||||
Otherwise, the remaining conflicts need to be examined. If they
|
||||
do not have the indication of an <quote>allowed conflict</quote>
|
||||
in the message area, then either the IRQ/address for device probe
|
||||
will need to be changed, <emphasis>or</emphasis> the IRQ/address
|
||||
on the hardware will need to be changed.</para>
|
||||
|
||||
<para>To change the driver's configuration for IRQ and IO port
|
||||
address, select the device and press <keycap>Enter</keycap>. The
|
||||
cursor will move to the third section of the screen, and you can
|
||||
change the values. You should enter the values for IRQ and port
|
||||
address that you discovered when you made your hardware inventory.
|
||||
Press <keycap>Q</keycap> to finish editing the device's
|
||||
configuration and return to the active driver list.</para>
|
||||
|
||||
<para>If you are not sure what these figures should be then you can
|
||||
try using <literal>-1</literal>. Some FreeBSD drivers can safely
|
||||
probe the hardware to discover what the correct value should be,
|
||||
and a value of <literal>-1</literal> configures them to do
|
||||
this.</para>
|
||||
|
||||
<para>The procedure for changing the address on the hardware varies
|
||||
from device to device. For some devices you may need to
|
||||
physically remove the card from your computer and adjust jumper
|
||||
settings or DIP switches. Other cards may have come with a DOS
|
||||
floppy that contains the programs used to reconfigure the card.
|
||||
In any case, you should refer to the documentation that came with
|
||||
the device. This will obviously entail restarting your computer,
|
||||
so you will need to boot back into the FreeBSD installation
|
||||
routine when you have reconfigured the card.</para>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>When all the conflicts have been resolved the screen will look
|
||||
similar to <xref linkend="userconfig-done">.</para>
|
||||
|
||||
<figure id="userconfig-done">
|
||||
<title>沒有衝突的驅動程式設定</title>
|
||||
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="install/probstart" format="PNG">
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
</figure>
|
||||
|
||||
<para>As you can see, the active driver list is now much smaller,
|
||||
with only drivers for the hardware that actually exists being
|
||||
listed.</para>
|
||||
|
||||
<para>You can now save these changes, and move on to the next step
|
||||
of the install. Press <keycap>Q</keycap> to quit the device
|
||||
configuration interface. This message will appear:</para>
|
||||
|
||||
<screen>Save these parameters before exiting? ([Y]es/[N]o/[C]ancel)</screen>
|
||||
|
||||
<para>Answer <keycap>Y</keycap> to save the parameters to memory
|
||||
(it will be saved to disk if you finish the install) and the
|
||||
probing will start. After displaying the probe results in white
|
||||
on black text <application>sysinstall</application> will start
|
||||
and display its main menu
|
||||
(<xref linkend="sysinstall-main">).</para>
|
||||
|
||||
<figure id="sysinstall-main">
|
||||
<title>Sysinstall 主選單</title>
|
||||
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="install/main1" format="PNG">
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
</figure>
|
||||
</step>
|
||||
</procedure>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="view-probe">
|
||||
<title>那要怎麼去翻閱偵測硬體的結果呢？</title>
|
||||
|
|
@ -1651,7 +1377,7 @@ Mounting root from ufs:/dev/md0c
|
|||
to continue with the installation.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="disklabeleditor">
|
||||
<sect2 id="bsdlabeleditor">
|
||||
<title>以 <application>Disklabel</application> 來建立分割區(Partitions)
|
||||
</title>
|
||||
|
||||
|
|
@ -5117,8 +4843,8 @@ Please press any key to reboot.</screen>
|
|||
<xref linkend="ports">) as
|
||||
necessary.</para>
|
||||
|
||||
<para>Use the image of disc one if you want to install a
|
||||
&os; 4.<replaceable>X</replaceable> release and want
|
||||
<para>Use the image of disc one if you want to install a &os;
|
||||
release and want
|
||||
a reasonable selection of third party packages on the disc
|
||||
as well.</para>
|
||||
|
||||
|
|
@ -5308,13 +5034,7 @@ Please press any key to reboot.</screen>
|
|||
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/base/">&rel.current;/base/</ulink>
|
||||
directory.</para>
|
||||
|
||||
<note>
|
||||
<para>In the 4.X and older releases of &os; the <quote>base</quote>
|
||||
distribution is called <quote>bin</quote>. Adjust the sample
|
||||
commands and URLs above accordingly, if you are using one of these
|
||||
versions.</para>
|
||||
</note>
|
||||
|
||||
|
||||
<para>For as many distributions you wish to install from an &ms-dos;
|
||||
partition (and you have the free space for), install each one
|
||||
under <filename>c:\freebsd</filename> — the
|
||||
|
|
|
|||
|
|
@ -655,76 +655,53 @@
|
|||
|
||||
<indexterm><primary>core team</primary></indexterm>
|
||||
<listitem>
|
||||
<para><firstterm>FreeBSD core team</firstterm>
|
||||
就等於董事會 -- 如果把 FreeBSD 看成是一家公司的話。
|
||||
<para>如果把 FreeBSD 看成是一家公司的話，<firstterm>FreeBSD core team</firstterm>
|
||||
就相當於『董事會(board of directors)』。
|
||||
core team 的主要職責在於確保此計劃有良好的架構，以朝著正確的方向發展。
|
||||
此外，邀請熱血且負責的軟體開發者加入 committers 行列，以在若干成員離去時得以補充新血。
|
||||
目前的 core team 是在 2004 年 6 月 committers 候選人中選出來的，每兩年會舉辦一次選舉</para>
|
||||
|
||||
<para>Some core team members also have specific areas of
|
||||
responsibility, meaning that they are committed to
|
||||
ensuring that some large portion of the system works as
|
||||
advertised. For a complete list of FreeBSD developers
|
||||
and their areas of responsibility, please see the <ulink
|
||||
url="&url.articles.contributors;/article.html">Contributors
|
||||
List</ulink></para>
|
||||
<para>有些 core team 成員還負責某些特定範圍，也就是說他們必須盡量確保一些子系統的穩定、效能。
|
||||
關於 FreeBSD 開發者們以及各自責任範圍，請參閱 <ulink
|
||||
url="&url.articles.contributors;/article.html">貢獻者名單</ulink>。</para>
|
||||
|
||||
<note>
|
||||
<para>Most members of the core team are volunteers when it
|
||||
comes to FreeBSD development and do not benefit from the
|
||||
project financially, so <quote>commitment</quote> should
|
||||
also not be misconstrued as meaning <quote>guaranteed
|
||||
support.</quote> The <quote>board of directors</quote>
|
||||
analogy above is not very accurate, and it may be
|
||||
more suitable to say that these are the people who gave up
|
||||
their lives in favor of FreeBSD against their better
|
||||
judgment!</para>
|
||||
<para>core team 大部分成員加入 FreeBSD 開發都是志工性質而已，並未從本計劃中獲得任何薪酬，
|
||||
所以不該把 <quote>commitment</quote> 誤解為 <quote>guaranteed support</quote>
|
||||
才對。 剛前面所講的『董事會』可能是不恰當的類推，或許我們應該說：
|
||||
他們是一群自願放棄原本的優渥生活、個人其他領域成就，而選擇投入 FreeBSD 開發的熱血有為者才對！</para>
|
||||
</note>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>Outside contributors</term>
|
||||
<term>其他的貢獻者</term>
|
||||
|
||||
<indexterm><primary>contributors</primary></indexterm>
|
||||
<listitem>
|
||||
<para>Last, but definitely not least, the largest group of
|
||||
developers are the users themselves who provide feedback and
|
||||
bug fixes to us on an almost constant basis. The primary
|
||||
way of keeping in touch with FreeBSD's more non-centralized
|
||||
development is to subscribe to the &a.hackers; where such
|
||||
things are discussed. See <xref
|
||||
linkend="eresources"> for more information about
|
||||
the various FreeBSD mailing lists.</para>
|
||||
<para>最後一點，但這點絕非最不重要的，最大的開發者團隊就是持續為我們提供回饋以及錯誤修正的使用者自己。
|
||||
與 FreeBSD 非核心開發者互動的主要方式，便是透過訂閱 &a.hackers; 來進行溝通，
|
||||
這方面可參考，請參閱 <xref
|
||||
linkend="eresources"> 以瞭解各式不同的 FreeBSD 郵遞論壇(mailing lists)。</para>
|
||||
|
||||
<para><citetitle><ulink
|
||||
url="&url.articles.contributors;/article.html">The
|
||||
FreeBSD Contributors List</ulink></citetitle> is a long
|
||||
and growing one, so why not join it by contributing
|
||||
something back to FreeBSD today?</para>
|
||||
url="&url.articles.contributors;/article.html">FreeBSD 貢獻者名單</ulink></citetitle>
|
||||
相當長且不斷成長中，只要有貢獻就會被列入其中，要不要立即考慮貢獻 FreeBSD 一些回饋呢？</para>
|
||||
|
||||
<para>Providing code is not the only way of contributing to
|
||||
the project; for a more complete list of things that need
|
||||
doing, please refer to the <ulink
|
||||
url="&url.base;/index.html">FreeBSD Project web
|
||||
site</ulink>.</para>
|
||||
<para>然而，提供原始碼並非為這個計劃做貢獻的唯一方式；
|
||||
還需要大家投入的完整工作列表、說明，請參閱 <ulink
|
||||
url="&url.base;/index.html">FreeBSD 官網</ulink>。</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
<para>In summary, our development model is organized as a loose set
|
||||
of concentric circles. The centralized model is designed for the
|
||||
convenience of the <emphasis>users</emphasis> of FreeBSD, who are
|
||||
provided with an easy way of tracking one central code
|
||||
base, not to keep potential contributors out! Our desire is to
|
||||
present a stable operating system with a large set of coherent
|
||||
<link linkend="ports">application programs</link> that the users
|
||||
can easily install and use — this model works very well in
|
||||
accomplishing that.</para>
|
||||
<para>簡單的說，我們的開發模式就像是一組沒有拘束的同心圓。
|
||||
這種集中開發模式是以 <emphasis>給使用者方便</emphasis>，
|
||||
同時讓他們能很容易地共同維護軟體，而不會把潛在的貢獻者排除在外！
|
||||
我們的目標是提供含有大量一致性的 <link linkend="ports">應用軟體(ports/packages)</link>
|
||||
，以便讓使用者輕鬆安裝、使用的作業系統 —— 而這開發模式相當符合此一目標。</para>
|
||||
|
||||
<para>All we ask of those who would join us as FreeBSD developers is
|
||||
some of the same dedication its current people have to its
|
||||
continued success!</para>
|
||||
<para>我們對於那些想要加入 FreeBSD 開發者的期待是：請保持如同前人一樣的投入，以確保繼續成功！</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="relnotes">
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@
|
|||
<para>讀完這章，您將了解︰</para>
|
||||
<itemizedlist>
|
||||
<listitem><para>各種不同的語言與地區設定如何在作業系統上進行編碼。</para></listitem>
|
||||
<listitem><para>如何設定登入用的 shell 語系環境。/para></listitem>
|
||||
<listitem><para>如何設定登入用的 shell 語系環境。</para></listitem>
|
||||
<listitem><para>如何將你的 console 設為英語以外的語系設定。</para></listitem>
|
||||
<listitem><para>如何使用不同語系的設定，來讓 X Window 運作更親切。</para></listitem>
|
||||
<listitem><para>哪邊可以找到更多與 i18n 規格相容的應用程式規格資料。</para></listitem>
|
||||
|
|
|
|||
Loading…
Reference in a new issue