Unix System Administrator Handbook 翻譯 - Linux

以下內容版權所屬於:

Prentice Hall，純屬個人興趣翻譯該原文內容。不觸及任何商業利益。

也歡迎有興趣的版友一起討論。

1. where to start

We set out to write a book that could be a system administrator’s trusty
companion, providing the practical advice , comfort, and basic system
administration theory that you can’t get from reading manual pages. As a
result, this book is designed to complement not replace your system’s
documentation.

我們寫這本書的目的在於，可以讓這本書變成系統管理員的可靠夥伴，提供實用的建議，
以及閱讀上的舒適性基本的系統管理理論，這些在文件中是無法取得的。因此，設計這本
書的目的是補充文件上的不足並非是要取代系統的文件。

We think this book will help you in five ways:
我們認為這本書將能在五個方向提供您協助：

It will give you an overview of the major administrative systems, identifying
the different pieces of each and explaining how they work together.
它能提供主要的管理系統概論以及介紹各種不同的原件如何協同工作。

It will introduce general administrative techniques that we have found,
through experience, to be worthwhile.
它將會介紹一般的管理技術，而且我們發現透過這樣的介紹管理技術的經驗是非常值得的
。
It will help you choose solutions that continue to work well as your site
grows in size and complexity.

它將會幫助您當您的網站的規模增長或者複雜性增加時可以提供解決的方案讓您的工作不
間斷。

It will help you sort good ideas from bad and educate you bout various
atrocities of taste committed by operating system developers.

它將會在書中每個階段教導並且協助你釐清思緒去分辨出當身為系統開發者時如何選擇好
與不好的方式。

It will summarize common procedures so that you don’t have to dig through
the excessive detail of the manuals to accomplish simple tasks.

它會概述常見的程序，讓您不必閱讀過多的細節來完成簡單的工作。

It’s impossible to perform these functions with perfect objectivity, but we
think we’ve made our biases fairly clear throughout the text. One of the
interesting things about system administration is the fact that reasonable
people can have dramatically different notions of what constitute the most
appropriate policies and procedures. We offer our subjective opinions to you
as raw data. You’ll have to decide for yourself how much to accept and to
what extent our comments apply to your environment.

客觀的來說不可能實現這些功能與完美的客觀性，但我們認為我們已經非常清楚我們在本
書中的看法。其中一個有趣的事實是當有關系統管理時，系統管理者通常有顯著不同的概
念並且了解是什麼構成了最適當的規則和程序。我們為我們的主觀意見，作為你原始數據
。你必須自己決定多少以及在多大程度上接受我們的意見並且適用於您的環境。

1.1 suggested background
We assume in this book that you have a certain amount of UNIX experience. In
particular, you should have a general concept of how UNIX looks and feels
from the user’s perspective before jumping into administration. There are
several good books that can get you up to speed; see the reading list on
page11.

我們假設在您在翻閱這本書之前，你已經有一定使用UNIX的經驗。比較特別的是，並且在
跳進管理面之前先從用戶的角度來看，你應該有一個基礎的認知對UNIX的使用概念以及
UNIX的外觀和感覺，有些很好的書籍，可以讓你加快學習的速度，詳情請翻閱第11頁上的
閱讀清單。

You perform most administrative tasks by editing configuration files and
writing scripts, so you must be familiar with a text editor. We strongly
recommend that you learn vi. It is standard on all UNIX systems, and though
it may appear a bit pale when compared with glitzier offerings such as emacs,
it is perfectly usable. If you become addicted to another editor, you may
soon tire of dragging it along with you install on every new systems. To the
dismay of many, using Microsoft Word as one’s only text editor is a
significant impediment to effective system administration.

在您執行大多數管理任務以及編輯配置文件撰寫腳本前，您必須熟悉且了解文字編輯器。
我們強烈建議您學習 vi。它可以應用在在所有UNIX系統，雖然它可能顯得有點蒼白單調
但可以達到有效的管理系統。glitzier產品，或者emacs，這些都是文字編輯器的產品。
如果你已經習慣使用其他編輯器，你可能會因為隨時都需要安裝在每個新的系統而感覺到
疲憊，例如使用Microsoft Word作為自己的唯一的文字編輯器就會是一個很不好的選擇。

One of the mainstays of UNIX administration (and a theme that runs throughout
this book)is the use of scripts to automate administrative tasks. To be an
effective administrator, you must be able to read and modify sh scripts.
Scripts that you write from scratch can be written in the shell or scripting
language of your choice.

在UNIX管理中（一個慣穿本書的核心重點）使用腳本來自動化管理是非常重要的一件事情
。要成為一個有效的管理者，你必須能夠讀取和修改SH 程式。在你開始寫腳本時可以選
擇shell或者其他的腳本語言。

For new scripting projects, we recommend Perl. As a programming language, it
is a little strange(OK, more than a little). However, it does include many
features that are indispensable for administrators. The O’Reilly book
Programming Perl by Larry Wall et al. is the standard text; it’s also model
of good technical writing. A full citation is given on page 11.

對於一個新的腳本我們建議使用Perl來進行編寫程式，雖然這是一個陌生的程式語言(或
許大多數人不曾用過)但不管怎樣Perl包括許多不同的功能，對一個系統管理者而言是一
個不可或缺的工具。在O’Reilly出版編寫程式語言的書中其中一本由Larry Wall等人編
寫的一本關於Perl的書籍是一個非常標準的文件。它同時也是一個非常好的範本，在本書
中的第11頁對於Larry Wall有更詳細的介紹。

We also recommend that you learn expect, which is discussed in a bit more
detail starting on page 519. you will most likely pick up expect quite
rapidly.

另外在519頁有更多的細節將被討論到，我們也建議您在翻閱到519頁的同時詳細的閱讀一
下。這些細節的部分可以更加速您學習的速度。

1.2 Example UNIX systems
In this book, we have chosen for popular UNIX variants as our
examples:Sloaris 2.7,Hp-UX 11.00, Red Hat Linux 6.2, and FreeBSD 3.4. these
systems are representative of the overall UNIX marketplace, and they are all
so common that it’s hard to find a UNIX site that doesn’t use at least one
of them.

在本書中我們選擇幾個比較流行、在目前的較常使用到的系統作為本書中的範例，如：
Sloaris 2.7,Hp-UX 11.00, Red Hat Linux 6.2, and FreeBSD 3.4。這些系統幾乎是當
前UNIX市場上最常見到的系統，普遍性高；很少有系統並不是使用上述系統的其中之一。

Sun Microsystems’ Solaris is a system V derivative with many extensions. Sun
UNIX(yes, that’s what it was called in the mid-80s)was originally the
progeny of Berkeley UNIX, but a (now historic)corporate partnership between
Sun and AT&T forced a change of platform.
HP’s HP-UX is a hybrid of the System V and Berkeley UNIX trees, but with odd
surprises of its own.
Several free UNIX systems are available for Intel hardware, and of these
Linux is currently the most popular. Linux itself is just kernel; you must
add on a full complement of commands, utilities, and daemons to form a
complete UNIX system. The various Linux “distributions” bundle the kernel
with the other components needed for a full installation. Linux distributors
make many choices while assembling their companies(including Red Hat, SuSE,
and Corel)provide production-grade

distributions with full support.

FreeBSD is a system based on Berkeley’s 4.4BSD-Lite release. Like Linux, it
runs on a variety of Intel platforms. A commercially supported version is
available from BBDI.
(歷史部分就不翻譯了)


1.4 NOTATION AND TYPOGRAPHICAL CONVENTIONS
In this book, filenames, commands, and literal arguments to commands are
shown in boldface. Placeholders(e.g., command arguments that should not be
taken literally)are in italics. For example, in the command.
cp file directory
you are supposed to replace file and directory with the names of an actual
file and an actual directory.

在本書中，檔案名稱、指令以及指令參數皆使用粗體顯示Placeholders使用斜體表示(佔
位符號數學表達式或邏輯表達式中的符號,可用某一集合中任一元素的名稱來代替.)(例如
：指令參數就不該只有看字面上)佔位符號應該接在指令的後面。
如上述範例(cp file directory)就應該要使用一個實際文件以及實際的檔案名稱來替換
。
(這段其實翻的不是很好，站位符號是我很混亂的地方，希望有鄉民可以提出指正)

Excerpts from configuration files and terminal sessions are shown in a
fixed-width font. Sometimes, we annotate interactive sessions with italic
text. For example.

引用下面的範例在設定檔中以及終端機對話視窗會呈現為一個固定大小的視窗，
有時候我們會在檔案中使用斜線加上星號來做一個註解。如下圖所顯示：
%grep Bob /pub/phonelis /* Look up Bob’s phone # */
Bob Knowles 555-2934
Bob Smith 555-2311

Outside of these specific cases, we have tried to keep special fonts and
formatting conventions to a minimum so long as we could do so without
compromising intelligibility. Fro example, we often talk about entities such
as the UNIX group daemon and the printer anchor-lw with no special formatting
at all.

在實體情況下我們在本書中盡量以最低限度中保持這些特殊的字體和格式以避免影響到本
書與實際機上的差異性以及清晰度。舉例來說在UNIX中群組格式以及列印格式。

In general, we use the same conventions as the UNIX manual pages for
indicating the syntax of commands:

一般來說我們習慣使用UNIX手冊中的語法來作為一個標準：
(這邊說的應該是man page and info page)


Anything between square brackets (“[“ and “]”) is optional
任何在[]方括號中的.參數都是可以選擇使用的

Anything followed by an ellipsis(“….”) can be repeated.
任何在省略號（“... ...。”）之後的是可以重複

Curly braces (“[“ and “]”) indicate that you should select one of the
items separated by vertical bars (“|”).
大括號（“[”and“]”）表示，你應該選擇其中一個項目或者同時使用時要用分隔豎線
("|")

For example, the specification
Bork [-x] [on] [off] filename …..
簡單的來說就如同下面所顯示的規格一樣

Would match any of the following commands:
可以選擇使用上述方式在下列命命之中
Bork on /etc/passwd
Bork –x off /etc/passwd /etc/termcap
Bork off /usr/lib/tmac

2. Actually, it’s not really a fixed-width font, but it looks like on, we
liked it better than the real fixed-width fonts that we tried. That’s why
the columns in some examples may not all line up perfectly.

事實上，我們並無法完全達到一個看起來為固定寬度的字體。但是至少看起像是有，我們
會更喜歡實際上為固定寬度的字體。雖然我們已經盡力嚐試但有些地方還是有美中不足的
地方，這就是為什麼在某一些範例上看起來並不會排列的非常完美。


We use shell-style globbing characters for pattern matching:
● A star (*) matches zero or more characters.
● A question mark(?) matches one character.
● A tilde or “twiddle” (~) means the home directory of the current user.
● ~user means the home directory of user.

我們使用shell的風格配合字形符號來作為一個選擇：
●星號（*）表示零個或多個字串或者符號。
●一個問號（？）搭配一個字串或者符號。
●一個波浪或“旋轉”（～）指家目錄中的當前用戶。
●～是指使用者用戶的主目錄。

For example, we sometimes refer to the BSD startup scripts/etc/rc,
/etc/rc.boot, and /etc/rc.local with the shorthand pattern /etc/rc*

以簡單的例子來說，我們有時候指的是BSD的啟動腳本，如/etc/rc, /etc/rc.boot, and
/etc/rc.local但是可以換個較為快速的方式，如/etc/rc*

Text within quotation marks often has a precise technical meaning. In these
cases, we ignore the normal rules of English and put punctuation outside the
quotation marks so that there can be no confusion about what’s not.

通常在引號內的文字都代表著一個相對應的意義，可是在這種情況下我們會忽略了在英語
語法中正常的規則；來避免對引號中的文字所具有的意義造成混淆。

System-specific information
Information in this book generally applies to all four of our example systems
unless a specific attribution is given. Details particular to one system are
marked with the vendor’s logo:

在本書中的資訊一般適用於各種UNIX系統，除非在我們的例子中有較為特別的例子；我們
會以該系統商的商標作為一個辨識的方式。
Solaris 2.7 HP-UX 11.00
Red Hat Linux 6.2 FreeBSD 3.4

到這邊是1.4的內容，希望有對這本有興趣的鄉民可以一起來討論。

--