diff --git a/zh_TW.Big5/books/handbook/basics/chapter.sgml b/zh_TW.Big5/books/handbook/basics/chapter.sgml index 4ed225bafc..f570ed39a6 100644 --- a/zh_TW.Big5/books/handbook/basics/chapter.sgml +++ b/zh_TW.Big5/books/handbook/basics/chapter.sgml @@ -27,7 +27,7 @@ 如果您對這些內容熟悉的話，可以放心的跳過。 如果您剛接觸 FreeBSD，那您一定要仔細的讀完這章。 - 讀完這一章，您將會了解: + 讀完這章，您將了解： @@ -1815,92 +1815,87 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse Shells shells - command line + 命令列 command line - In FreeBSD, a lot of everyday work is done in a command line - interface called a shell. A shell's main job is to take commands - from the input channel and execute them. A lot of shells also have - built in functions to help everyday tasks such as file management, - file globbing, command line editing, command macros, and environment - variables. FreeBSD comes with a set of shells, such as - sh, the Bourne Shell, and tcsh, - the improved C-shell. Many other shells are available - from the FreeBSD Ports Collection, such as - zsh and bash. + 在 FreeBSD 中，很多日常的工作是在一個叫做 shell + 的文字介面中完成的。 + Shell 的主要工作就是從輸入中收到命令並執行它們。 + 許多 shell 也有內建一些有助於日常工作的指令， + 像是檔案管理、檔案比對、命令列編輯、指令巨集以及環境變數等。 + FreeBSD 有內附了幾個 shell，像是 sh， + Bourne Shell，以及 tcsh，改良版的 C-shell。 + 還有許多其他的 shell 可以從 FreeBSD Ports Collection + 中取得，像是 zsh 以及 bash + 等。 - Which shell do you use? It is really a matter of taste. If you - are a C programmer you might feel more comfortable with a C-like shell - such as tcsh. If you have come from Linux or are new - to a &unix; command line interface you might try bash. - The point is that each - shell has unique properties that may or may not work with your - preferred working environment, and that you have a choice of what - shell to use. + 您用哪個 shell 呢？ 其實每個人的喜好都不一樣。 + 如果您是一個 C 程式設計師，那對於使用像是 tcsh + 這種 C-like 的 shell 可能會感到相當愉快。 如果你是從 Linux + 跳過來的，或者您是一個 &unix; 新手，那您也許會想要用 + bash 來當作文字介面。 + 每一個 shell 都有自已獨特之處，至於這些特點能不能配合您的工作環境？ + 那就是您選擇 shell 的重點了。 - One common feature in a shell is filename completion. Given - the typing of the first few letters of a command or filename, you - can usually have the shell automatically complete the rest of the - command or filename by hitting the Tab key on the keyboard. Here is - an example. Suppose you have two files called - foobar and foo.bar. You - want to delete foo.bar. So what you would type - on the keyboard is: rm fo[Tab].[Tab]. - - The shell would print out rm - foo[BEEP].bar. - - The [BEEP] is the console bell, which is the shell telling me it - was unable to totally complete the filename because there is more - than one match. Both foobar and - foo.bar start with fo, but - it was able to complete to foo. If you type in - ., then hit Tab again, the shell would be able to - fill in the rest of the filename for you. + 檔名自動補齊就是常見的 shell 功能。 + 首先輸入指令或檔案的前幾個字母，這時通常您只需要按下 Tab + 鍵，接下來 shell 就會自動把指令或是檔案名稱剩餘的部份補齊。 + 假設您有兩個檔案分別叫作 foobar 及 + foo.bar。 現在要刪掉 + foo.bar，那麼可以輸入： + rm fo[Tab].[Tab] + + + Shell 會印出這個： rm foo[嗶].bar。 + + [嗶] 是 console 的響鈴，這嗶的一聲是 shell + 在告訴我說它沒有辦法完全自動補齊檔名，因為有不只一個檔名符合條件。 + foobar 和 foo.bar 都是 + fo 開頭的檔名，不過它至少可以補齊到 foo。 + 如果您接著輸入 . 然後再按 Tab + 一次，那 shell 就能夠替您把剩下的檔名填滿了。 + environment variables - Another feature of the shell is the use of environment variables. - Environment variables are a variable/key pair stored in the shell's - environment space. This space can be read by any program invoked by - the shell, and thus contains a lot of program configuration. Here - is a list of common environment variables and what they mean: + Shell 的另一項特點是使用了環境變數。 + 環境變數是以變數與鍵值（variable/key）的對應關係儲存於 shell + 的環境空間中，任何由 shell 所產生的程序都可以讀取此空間， + 因此這個空間儲存了許多程序的設定組態。在此附上 + 一份常見環境變數與其含意的列表： environment variables - Variable - Description + 變數 + 詳細說明 USER - Current logged in user's name. + 目前登入的使用者名稱。 PATH - Colon-separated list of directories to search for - binaries. + 以冒號（:）隔開的目錄列表，用以搜尋執行檔的路徑。 DISPLAY - Network name of the X11 display to connect to, if - available. + 若存在這個環境變數，則代表 X11 連結顯示器的網路名稱。 SHELL - The current shell. + 目前使用的 shell。 TERM - The name of the user's type of terminal. Used to determine - the capabilities of the terminal. + 使用者終端機的名稱，能藉由此變數判斷終端機的能力。 @@ -1911,59 +1906,56 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse OSTYPE - Type of operating system. e.g., FreeBSD. + 作業系統的種類，如：FreeBSD。 MACHTYPE - The CPU architecture that the system is running - on. + 目前系統所用的 CPU 架構。 EDITOR - The user's preferred text editor. + 使用者偏好的文字編輯器。 PAGER - The user's preferred text pager. + 使用者偏好的文字分頁器（text pager）。 MANPATH - Colon-separated list of directories to search for - manual pages. + 以冒號（:）隔開的目錄列表，用以搜尋 manual pages 的路徑。 Bourne shells - Setting an environment variable differs somewhat from - shell to shell. For example, in the C-Style shells such as - tcsh and csh, you would use - setenv to set environment variables. - Under Bourne shells such as sh and - bash, you would use - export to set your current environment - variables. For example, to set or modify the - EDITOR environment variable, under csh or - tcsh a - command like this would set EDITOR to - /usr/local/bin/emacs: + 在不同的 shell 底下設定環境變數的方式也有所不同。 + 舉例來說，在 C-Style 的 shell 底下，像是 + tcsh 和 csh，你必須使用 + setenv 來設定環境變數。 + 但在 Bourne shells 底下，像是 sh 和 + bash，你則必須使用 + export 來設定你所使用的環境變數。 + 再舉個例子來說，若要設定或是修改 + EDITOR 這個環境變數，在 csh 或 + tcsh 下設定 EDITOR 這個環境變數為 + /usr/local/bin/emacs 的指令是： &prompt.user; setenv EDITOR /usr/local/bin/emacs - Under Bourne shells: + 在 Bourne shells 下則是： &prompt.user; export EDITOR="/usr/local/bin/emacs" - You can also make most shells expand the environment variable by - placing a $ character in front of it on the - command line. For example, echo $TERM would - print out whatever $TERM is set to, because the shell - expands $TERM and passes it on to echo. + 大多數的 shell 都支援使用者在命令列中將 + $ 字元放在變數之前，以取得環境變數的值。 + 舉例來說，echo $TERM 會 + 顯示出 $TERM 的設定值，這是因為 shell 取得了 + $TERM 的設定值，並將他傳給 echo 顯示出來。 Shells treat a lot of special characters, called meta-characters as special representations of data. The most common one is the @@ -1983,22 +1975,17 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse is. - Changing Your Shell + 變更你的 Shell - The easiest way to change your shell is to use the - chsh command. Running chsh will - place you into the editor that is in your EDITOR - environment variable; if it is not set, you will be placed in - vi. Change the Shell: line - accordingly. + 變更 shell 最簡單的方法就是透過 chsh 命令。 + 執行 chsh 將會呼叫環境變數中 EDITOR 指定的 + 文字編輯器。如果沒有設定，則預設是 vi。依照需求去修改 + Shell: 的值。 + + 你也可以透過 chsh 的參數 ，這可以 + 直接設定你的 shell 而不需要透過任何文字編輯器。例如，假設你想將 shell 變更為 + bash，可以透過下列的方式： - You can also give chsh the - option; this will set your shell for you, - without requiring you to enter an editor. - For example, if you wanted to - change your shell to bash, the following should do the - trick: - &prompt.user; chsh -s /usr/local/bin/bash diff --git a/zh_TW.Big5/books/handbook/config/chapter.sgml b/zh_TW.Big5/books/handbook/config/chapter.sgml index 1a4597903c..4d488ad549 100644 --- a/zh_TW.Big5/books/handbook/config/chapter.sgml +++ b/zh_TW.Big5/books/handbook/config/chapter.sgml @@ -3,7 +3,7 @@ $FreeBSD$ Original revision: 1.213 - Chased revision: 1.217 + Chased revision: 1.221 --> @@ -141,42 +141,30 @@ 根據經驗法則，通常 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. - The kernel's VM paging algorithms are tuned to - perform best when the swap partition is at least two times the - size of main memory. Configuring too little swap can lead to - inefficiencies in the VM page scanning code and might create - issues later if more memory is added. + swap 則應該設為 256 MB。 記憶體較少的機器，可以透過增加更多 swap 空間來提昇效能。 + 我們建議 swap 空間不要設低於 256 MB，而且該考慮增加記憶體才是良策。 + 當 swap 最少為記憶體的兩倍大時，kernel 的 VM paging 演算法會把效能調整到最佳狀態。 + 但若是機器記憶體很大，但 swap 卻劃分太少的話，會導致 VM page 掃瞄的效率過低， + 此外日後若增加更多記憶體時，也會導致一些異常狀況發生。 - On larger systems with multiple SCSI disks (or - multiple IDE disks operating on different controllers), it is - recommend that a swap is configured on each drive (up - to four drives). The swap partitions should be - approximately the same size. The kernel can handle arbitrary - sizes but internal data structures scale to 4 times the - largest swap partition. Keeping the swap partitions near the - same size will allow the kernel to optimally stripe swap space - across disks. - Large swap sizes are fine, even if swap is not - used much. It might be easier to recover - from a runaway program before being forced to reboot. + 在較大型的機器內，通常會有多顆 SCSI 磁碟(或多顆 IDE 磁碟接在不同 IDE 匯流排上)， + 建議在每顆磁碟上都建立 swap(最多到四顆)。 + 而這些 swap 應該都大約一樣大小， + Kernel 可接受任意大小的 swap，但內部資料結構則是最大塊 swap 的 4 倍。 + 若有保持 swap 為同樣大小的話，則可讓 kernel 最佳化運用各磁碟之中的 swap 空間。 + 即使不太常會用到，分配大的 swap 也都還可接受， + 因為它可在強制重開機之前讓你更容易從當掉的程式中恢復正常。 為何要規劃 Partition？ - Several users think a single large partition will be fine, - but there are several reasons why this is a bad idea. - First, each partition has different operational - characteristics and separating them allows the file system to - tune accordingly. For example, the root - and /usr partitions are read-mostly, without - much writing. While a lot of reading and writing could - occur in /var and - /var/tmp. + 有些人覺得把硬碟就直接劃分一個大分割區就好了， + 但是事實上有些原因會證明為何這是個爛點子， + 首先，每個分割區都有不同的運作特性，把它們分開的話可以讓檔案系統來調整。 + 比如： / 以及 /usr 分割區大多只是讀取而已， + 比較少在寫入。 而讀寫都很頻繁的則是 /var 及 + /var/tmp。 By properly partitioning a system, fragmentation introduced in the smaller write heavy partitions @@ -261,28 +249,21 @@ 各式應用程式的設定檔 - Typically, installed applications have their own - configuration files, with their own syntax, etc. It is - important that these files be kept separate from the base - system, so that they may be easily located and managed by the - package management tools. + 原則上，安裝的軟體都會有其自有的設定檔，也會有自己的格式及語法。 + 因此，將其與系統分開獨立是件非常重要的事情。如此一來，套件管理工具將可以 + 很輕易的找出這些設定檔並管理這些設定檔。 /usr/local/etc - Typically, these files are installed in - /usr/local/etc. In the case where an - application has a large number of configuration files, a - subdirectory will be created to hold them. + 原則上，設定檔會被放置在 /usr/local/etc。 + 若某軟體的設定檔為數眾多，那將會其下建立一個目錄以供放置 - Normally, when a port or package is installed, sample - configuration files are also installed. These are usually - identified with a .default suffix. If there - are no existing - configuration files for the application, they will be created by - copying the .default files. + 通常，當一個 port 或 package 被安裝的同時，一些基本的設定範例 + 也會一併被安裝至此。這些範例通常會被用 .default 做為副檔名。 + 若安裝時沒有自行撰寫的軟體設定檔，那麼將會複製一份 .default 設定 + 做為預設設定檔 - For example, consider the contents of the directory - /usr/local/etc/apache: + 舉個例子，我們來看看 /usr/local/etc/apache： -rw-r--r-- 1 root wheel 2184 May 20 1998 access.conf -rw-r--r-- 1 root wheel 2184 May 20 1998 access.conf.default @@ -295,9 +276,8 @@ -rw-r--r-- 1 root wheel 7980 May 20 1998 srm.conf -rw-r--r-- 1 root wheel 7933 May 20 1998 srm.conf.default - The file sizes show that only the srm.conf - file has been changed. A later update of the Apache port would not - overwrite this changed file. + srm.conf 的檔案被修改過了，爾後 Apache 的更新 + 將不會對這個已修改過的設定檔做任何變動。 @@ -667,7 +647,7 @@ HOME=/var/log - 在 &os; 5.X (含之後) 使用 rc + 在 &os; 使用 rc 從 2002 年起，&os; 整合了 NetBSD 的 rc.d 機制來作為系統服務啟動機制。 可以到 /etc/rc.d 目錄下去看，很多檔案都是基本服務，可以用 , @@ -860,7 +840,7 @@ ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto The easiest way is to simply load a kernel module for - your network card with &man.kldload.8;. Not all NIC + your network card with &man.kldload.8;, or automatically at boot time by adding the appropriate line to the file /boot/loader.conf. Not all NIC drivers are available as modules; notable examples of devices for which modules do not exist are ISA cards. @@ -878,6 +858,128 @@ ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto not have to build a new kernel. + + + Using &windows; NDIS Drivers + + NDIS + NDISulator + &windows; drivers + Microsoft Windows + Microsoft Windows + device drivers + KLD (kernel loadable + object) + + + 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 &os; and other + operating systems are left two choices: develop the drivers + by a long and pain-staking process of reverse engineering or + using the existing driver binaries available for the + µsoft.windows; platforms. Most developers, including + those involved with &os;, have taken the latter + approach. + + Thanks to the contributions of Bill Paul (wpaul), as of + &os; 5.3-RELEASE there is native support + for the Network Driver Interface Specification (NDIS). The + &os; NDISulator (otherwise known as Project Evil) takes a + &windows; driver binary and basically tricks it into + thinking it is running on &windows;. Because the + &man.ndis.4; driver is using a &windows; binary, it is only + usable on &i386; and amd64 systems. + + + The &man.ndis.4; driver is designed to support mainly + PCI, CardBus and PCMCIA devices, USB devices are not yet + supported. + + + In order to use the NDISulator, you need three + things: + + + + Kernel sources + + + &windowsxp; driver binary + (.SYS extension) + + + &windowsxp; driver configuration file + (.INF extension) + + + + Locate the files for your specific card. Generally, + they can be found on the included CDs or at the vendors' + websites. In the following examples, we will use + W32DRIVER.SYS and + W32DRIVER.INF. + + + You can not use a &windows;/i386 driver with + &os;/amd64, you must get a &windows;/amd64 driver to make it + work properly. + + + The next step is to compile the driver binary into a + loadable kernel module. To accomplish this, as + root, use &man.ndisgen.8;: + + &prompt.root; ndisgen /path/to/W32DRIVER.INF /path/to/W32DRIVER.SYS + + The &man.ndisgen.8; utility is interactive and will + prompt for any extra information it requires; it will + produce a kernel module in the current directory which can + be loaded as follows: + + &prompt.root; kldload ./W32DRIVER.ko + + In addition to the generated kernel module, you must + load the ndis.ko and + if_ndis.ko modules. This should be + automatically done when you load any module that depends on + &man.ndis.4;. If you want to load them manually, use the + following commands: + + &prompt.root; kldload ndis +&prompt.root; kldload if_ndis + + The first command loads the NDIS miniport driver + wrapper, the second loads the actual network + interface. + + Now, check &man.dmesg.8; to see if there were any errors + loading. If all went well, you should get output resembling + the following: + + ndis0: <Wireless-G PCI Adapter> mem 0xf4100000-0xf4101fff irq 3 at device 8.0 on pci1 +ndis0: NDIS API version: 5.0 +ndis0: Ethernet address: 0a:b1:2c:d3:4e:f5 +ndis0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps +ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18Mbps 36Mbps 48Mbps 54Mbps + + From here you can treat the + ndis0 device like any other network + interface (e.g., dc0). + + You can configure the system to load the NDIS modules at + boot time in the same way as with any other module. First, + copy the generated module, + W32DRIVER.ko, to the /boot/modules directory. Then, + add the following line to + /boot/loader.conf: + + W32DRIVER_load="YES" + @@ -1988,7 +2090,8 @@ device_probe_and_attach: cbb0 attach returned 12 require many thousands of file descriptors, depending on the kind and number of services running concurrently. - kern.maxfile's default value is + In older FreeBSD releases, kern.maxfile's default + value is derived from the option in your dictated by the option in your kernel configuration file. kern.maxfiles grows proportionally to the value of . When @@ -1999,6 +2102,23 @@ device_probe_and_attach: cbb0 attach returned 12 connected at once, the resources needed may be similar to a high-scale web server. + As of FreeBSD 4.5, kern.maxusers is + automatically sized at boot based on the amount of memory available + in the system, and may be determined at run-time by inspecting the + value of the read-only kern.maxusers sysctl. + Some sites will require larger or smaller values of + kern.maxusers and may set it as a loader tunable; + values of 64, 128, and 256 are not uncommon. We do not recommend + going above 256 unless you need a huge number of file descriptors; + many of the tunable values set to their defaults by + kern.maxusers may be individually overridden at + boot-time or run-time in /boot/loader.conf (see + the &man.loader.conf.5; man page or the + /boot/defaults/loader.conf file for some hints) + or as described elsewhere in this document. Systems older than + FreeBSD 4.4 must set this value via the kernel &man.config.8; + option instead. + The system will auto-tune maxusers for you if you explicitly set it to 0 diff --git a/zh_TW.Big5/books/handbook/introduction/chapter.sgml b/zh_TW.Big5/books/handbook/introduction/chapter.sgml index 060e0df5dd..e92bcf7ddf 100644 --- a/zh_TW.Big5/books/handbook/introduction/chapter.sgml +++ b/zh_TW.Big5/books/handbook/introduction/chapter.sgml @@ -41,7 +41,7 @@ FreeBSD open-source 開發模式的基礎概念； - 當然囉，還有 FreeBSD 這名字的緣故。 + 當然囉，還有 FreeBSD 這名字的由來。 diff --git a/zh_TW.Big5/books/handbook/mail/chapter.sgml b/zh_TW.Big5/books/handbook/mail/chapter.sgml index b51cda2784..2937d5bacd 100644 --- a/zh_TW.Big5/books/handbook/mail/chapter.sgml +++ b/zh_TW.Big5/books/handbook/mail/chapter.sgml @@ -24,10 +24,10 @@ - Electronic Mail + 電子郵件 - Synopsis + 概述 email Electronic Mail, better known as email, is one of the diff --git a/zh_TW.Big5/books/handbook/printing/chapter.sgml b/zh_TW.Big5/books/handbook/printing/chapter.sgml index d54a94b620..1653805d08 100644 --- a/zh_TW.Big5/books/handbook/printing/chapter.sgml +++ b/zh_TW.Big5/books/handbook/printing/chapter.sgml @@ -1,8 +1,8 @@ @@ -25,95 +25,89 @@ - Printing + 列印 - Synopsis + 概述 LPD spooling system + LPD 緩衝系統 printing + 列印 - FreeBSD can be used to print with a wide variety of printers, from the - oldest impact printer to the latest laser printers, and everything in - between, allowing you to produce high-quality printed output from the - applications you run. + FreeBSD 可以和各式各樣的印表機搭配列印， + 從最老的撞針式印表機到最新的雷射印表機都沒問題， + 讓您的應用程式可以產生出高品質的文件列印輸出。 + + 也可以把 FreeBSD 設定成一台網路列印伺服器；這時候的 FreeBSD + 能接收其他電腦送來的列印工作，包括其他 FreeBSD 的電腦、&windows; + 的電腦以及 &macos; 的電腦。 FreeBSD + 會確保同時只有一件文件正在列印，而且可以統計哪個使用者及機器印得最多， + 還有就是印出接下來是誰的文件這類的標題頁等。 - FreeBSD can also be configured to act as a print server on a - network; in this capacity FreeBSD can receive print jobs from a variety - of other computers, including other FreeBSD computers, &windows; and &macos; - hosts. FreeBSD will ensure that one job at a time is printed, and can - keep statistics on which users and machines are doing the most printing, - produce banner pages showing who's printout is who's, and - more. - - After reading this chapter, you will know: + 讀完這章，您將了解： - How to configure the FreeBSD print spooler. + 如何設定 FreeBSD 的列印多工緩衝處理器。 - How to install print filters, to handle special print jobs - differently, including converting incoming documents to print - formats that your printers understand. + 如何安裝列印過濾器以分別處理特殊的列印工作， + 包括把收到的文件轉換成您的印表機看得懂的列印格式等。 - How to enable header, or banner pages on your printout. + 了解如何在您列印時順便印出頁首或標題。 - How to print with printers connected to other computers. + 如何利用別台電腦上的印表機列印。 - How to print with printers connected directly to the - network. + 如何利用直接接在網路上的印表機列印。 - How to control printer restrictions, including limiting the size - of print jobs, and preventing certain users from printing. + 如何控制印表機的權限，包括限制列印工作的檔案大小， + 以及不允許特定使用者列印等。 - How to keep printer statistics, and account for printer - usage. + 如何記下印表機的統計資料，以及各帳號的印表機使用量。 - How to troubleshoot printing problems. + 如何解決列印時遇到的問題。 - Before reading this chapter, you should: + 在開始閱讀這章之前，您需要︰ - Know how to configure and install a new kernel - (). + 要有設定、編譯 kernel 的基礎概念 + ()。 - Introduction + 介紹 - In order to use printers with FreeBSD, you may set - them up to work with the Berkeley line printer spooling system, - also known as the LPD spooling system, - or just LPD. - It is the standard printer control system in FreeBSD. This - chapter introduces LPD and - will guide you through its configuration. + 要在 FreeBSD 上使用印表機，您需要設定好 Berkeley + 行列式印表機列印緩衝系統，又稱為 LPD + 列印緩衝系統，或者就叫 LPD。 + 這是 FreeBSD 標準的印表機控制系統，本章會介紹並教您如何設定 + LPD - If you are already familiar with - LPD or another printer spooling - system, you may wish to skip to section Basic Setup. + 如果您已經對 LPD + 或是其他列印緩衝系統很熟悉了， + 您可以直接跳到基本設定。 + - LPD controls everything about a - host's printers. It is responsible for a number of things: + LPD 控制著主機上印表機的一切。 + 這些事情都是它在負責的： @@ -532,69 +526,14 @@ ppc0: FIFO with 16/16/8 bytes threshold follows. - - - Adding <filename>/dev</filename> Entries for the - Ports - - FreeBSD 5.0 includes the devfs - filesystem which automatically creates device nodes as - needed. If you are running a version of FreeBSD with - devfs enabled then you can safely skip - this section. - - Even though the kernel may support communication along a - serial or parallel port, you will still need a software - interface through which programs running on the system can - send and receive data. That is what entries in the - /dev directory are for. - - To add a /dev entry for a - port: - - - - Become root with the &man.su.1; command. - Enter the root password when prompted. - - - - Change to the /dev - directory: - - &prompt.root; cd /dev - - - - Type: - - &prompt.root; ./MAKEDEV port - - Where port is the device - entry for the port you want to make. Use - lpt0 for the printer on the first parallel port, - lpt1 for the printer on the second port, and so on; use - ttyd0 for the first serial port, - ttyd1 for the second, and so on. - - - - Type: - - &prompt.root; ls -l port - - to make sure the device entry got created. - - - - + Setting the Communication Mode for the Parallel Port When you are using the parallel interface, you can choose whether FreeBSD should use interrupt-driven or polled communication with the printer. The generic printer - device driver (&man.lpt.4;) on FreeBSD 4.X and 5.X + device driver (&man.lpt.4;) on FreeBSD uses the &man.ppbus.4; system, which controls the port chipset with the &man.ppc.4; driver. @@ -639,15 +578,7 @@ ppc0: FIFO with 16/16/8 bytes threshold - If you want interrupt-driven mode, for FreeBSD 4.X add the - irq specifier: - - device ppc0 at isa? irq N - - Where N is the IRQ - number for your computer's parallel port. - - For FreeBSD 5.X, edit the following line: + If you want interrupt-driven mode, edit the following line: hint.ppc.0.irq="N" @@ -661,22 +592,14 @@ ppc0: FIFO with 16/16/8 bytes threshold - If you want polled mode, do not add the - irq specifier: - - For FreeBSD 4.X, use the following line in - your kernel configuration file: - - device ppc0 at isa? - - For FreeBSD 5.X, simply remove in your + If you want polled mode, remove in your /boot/device.hints file, the following line: hint.ppc.0.irq="N" In some cases, this is not enough to put the - port in polled mode under FreeBSD 5.X. Most of + port in polled mode under FreeBSD. Most of time it comes from &man.acpi.4; driver, this latter is able to probe and attach devices, and therefore, control the access mode to the printer port. You @@ -721,9 +644,9 @@ ppc0: FIFO with 16/16/8 bytes threshold /etc/rc.local file to set the mode each time your system boots. See &man.lptcontrol.8; for more information. - + - + Checking Printer Communications Before proceeding to configure the spooling system, you @@ -762,7 +685,7 @@ showpage accommodations. - + Checking a Parallel Printer @@ -826,9 +749,9 @@ showpage You should see something print. Do not worry if the text does not look right; we will fix such things later. - + - + Checking a Serial Printer @@ -923,9 +846,8 @@ showpage You should see something print. Do not worry if the text does not look right; we will fix that later. - - - + + Enabling the Spooler: the <filename>/etc/printcap</filename> @@ -1196,8 +1118,8 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\ <sect4 id="printing-device"> <title>Identifying the Printer Device - In the Adding - /dev Entries for the Ports + In the + Entries for the Ports section, we identified which entry in the /dev directory FreeBSD will use to communicate with the printer. Now, we tell diff --git a/zh_TW.Big5/books/handbook/users/chapter.sgml b/zh_TW.Big5/books/handbook/users/chapter.sgml index 216229dc9e..59efb0be88 100644 --- a/zh_TW.Big5/books/handbook/users/chapter.sgml +++ b/zh_TW.Big5/books/handbook/users/chapter.sgml @@ -2,7 +2,7 @@ The FreeBSD Documentation Project $FreeBSD$ - Original revision: 1.54 + Original revision: 1.58 --> @@ -22,7 +22,8 @@ 概述 - FreeBSD 允許多個使用者同時使用電腦。當然，這並不是很多人同時坐在同一台電腦前 + FreeBSD 允許多個使用者同時使用電腦。 當然， + 這並不是很多人同時坐在同一台電腦前 Well..除非您連接 multiple terminals，這種情況我們會在 講到。 @@ -45,11 +46,13 @@ - 如何更改帳號的基本資料，像是帳號全名，或是使用的 shell 種類。 + 如何更改帳號的基本資料，像是帳號全名，或是使用的 shell + 種類。 - 如何針對帳號、群組來設限，比如：允許存取記憶體或 CPU 資源多寡等。 + 如何針對帳號、群組來設限，比如：允許存取記憶體或 CPU + 資源多寡等。 @@ -57,11 +60,11 @@ - 在閱讀這章之前，您應當了解： + 在開始閱讀這章之前，您需要： - 瞭解 &unix; 及 FreeBSD (瞭解 &unix; 及 FreeBSD ()的基礎概念。 @@ -70,155 +73,137 @@ 介紹 - 系統的所有存取是經由帳號來進行，而所有的程式 process 是由使用者來進行，所以 - 使用者及帳號管理，乃是 FreeBSD 系統上不可或缺的重點。 + 系統的所有存取是經由帳號來進行，而所有的程式 process + 是由使用者來進行，所以使用者及帳號的管理，乃是 FreeBSD + 系統上不可或缺的重點。 - Every account on a FreeBSD system has certain information associated - with it to identify the account. + 所有於 FreeBSD 系統中的帳號皆包含下列相關資訊用來辨識身份。 - User name + 使用者名稱 - The user name as it would be typed at the - login: prompt. User names must be unique across - the computer; you may not have two users with the same - user name. There are a number of rules for creating valid user - names, documented in &man.passwd.5;; you would typically use user - names that consist of eight or fewer all lower case - characters. + 使用者名稱要輸入在 login: 提示出現後。 + 使用者名稱必須是獨一無二， + 不能有重複的使用者名稱。 + 至於如何建立有效使用者名稱的規則，請參閱 &man.passwd.5; 說明， + 通常使用者名稱是以八個以內的小寫字母所組成。 - Password + 密碼 - Each account has a password associated with it. The password - may be blank, in which case no password will be required to access - the system. This is normally a very bad idea; every account - should have a password. + 每個帳號都可擁有一組密碼。 密碼也可以不設， + 如此就不需密碼即可登入系統，但通常這並非妙策， + 每個帳號都應設定一組密碼。 - User ID (UID) + 使用者代號 (User ID, UID) - The UID is a number, traditionally from 0 to 65535 - It is possible to use UID/GIDs as large as - 4294967295, but such IDs can cause serious problems - with software that makes assumptions about the values - of IDs. - , used to uniquely identify - the user to the system. Internally, FreeBSD uses the UID to - identify users—any FreeBSD commands that allow you to - specify a user name will convert it to the UID before working with - it. This means that you can have several accounts with different - user names but the same UID. As far as FreeBSD is concerned these - accounts are one user. It is unlikely you will ever need to do - this. + UID 是系統用來辨識使用者的數字，通常範圍是從 0 到 65535 + UID/GID 最大可使用至 4294967295，但這樣的 ID + 可能會對已假設範圍的軟體造成嚴重問題。 + 。 FreeBSD 內部是使用 UID 來辨識使用者 — + FreeBSD 在執行任何指定使用者的指令之前，都會先把使用者名稱轉換為 + UID。 也就是說，比如可以有數個不同的使用者名稱， + 但是都使用同一個 UID，對 FreeBSD 來說，這些帳號都只代表同一使用者。 + 不過，實際上需要這樣做的可能性不大。 - Group ID (GID) + 群組代號 (Group ID, GID) - The GID is a number, traditionally from 0 to 65535, used to uniquely identify - the primary group that the user belongs to. Groups are a - mechanism for controlling access to resources based on a user's - GID rather than their UID. This can significantly reduce the size - of some configuration files. A user may also be in more than one - group. + GID 是系統用來辨識使用者所屬群組的數字，通常範圍是從 0 到 65535 + 。 用群組來控制資源存取，可有效減少一些設定檔的大小。 + 此外，使用者還可以同時屬於多個不同的群組。 - Login class + 登入分類(Login classes) - Login classes are an extension to the group mechanism that - provide additional flexibility when tailoring the system to - different users. + + 登入分類是群組的延伸機制， + 提供了不同的使用者更彈性的。 - Password change time + 密碼變更期限 - By default FreeBSD does not force users to change their - passwords periodically. You can enforce this on a per-user basis, - forcing some or all of your users to change their passwords after - a certain amount of time has elapsed. + FreeBSD 預設並不要求使用者週期性的更改密碼。您可以強制某些或 + 全部的使用者在指定的期間過後必須更改密碼。 - Account expiry time + 帳號期限 + - By default FreeBSD does not expire accounts. If you are - creating accounts that you know have a limited lifespan, for - example, in a school where you have accounts for the students, - then you can specify when the account expires. After the expiry - time has elapsed the account cannot be used to log in to the - system, although the account's directories and files will - remain. + FreeBSD 的帳號沒有預設的期限，如果您已知道帳號的使用期限， + 例如，學校中提供學生使用的帳號，可在建立帳號時指定帳號的期限。 + 當帳號過期後會無法登入系統，但該帳號的目錄及檔案則會保留。 - User's full name + 使用者全名 - The user name uniquely identifies the account to FreeBSD, but - does not necessarily reflect the user's real name. This - information can be associated with the account. + FreeBSD 的帳號使用使用者名稱用來辨識，但使用者名稱並不一定代表 + 真實使用者的姓名。為帳號所需的相關資訊。 - Home directory + 家目錄 - The home directory is the full path to a directory on the - system in which the user will start when logging on to the - system. A common convention is to put all user home directories - under - /home/username - or /usr/home/username. - The user would store their personal files in their home directory, - and any directories they may create in there. + 家目錄為使用者登入系統時的所在目錄的完整路徑。 + 通常會將所有使用者的家目錄放置於 + /home/使用者名稱 + 或 /usr/home/使用者名稱。 + 使用者可以將其個人的資料放置於其家目錄之中，並可以在此目錄底下 + 建立新的目錄 - User shell + 使用者 Shell - The shell provides the default environment users use to - interact with the system. There are many different kinds of - shells, and experienced users will have their own preferences, - which can be reflected in their account settings. + Shell 提供預設的環境讓使用者與系統互動。 + Shell 擁有數種不同的種類, 可供進階使用者依使用習慣選擇。 - - There are three main types of accounts: the Superuser, system users, and user accounts. The Superuser - account, usually called root, is used to - manage the system with no limitations on privileges. System - users run services. Finally, user accounts are used by real - people, who log on, read mail, and so forth. + + 帳號主要分為下列三類: 系統管理者帳號, 系統帳號，及 使用者帳號。 系統管理者帳號的帳號 + 通常為 root，擁有最大的權限來管理系統。 + 系統帳號用來執行伺服器服務。最後，使用者帳號供真正的使用者使用， + 可登入、讀信等等。 - The Superuser Account + 系統管理者帳號 accounts @@ -251,7 +236,7 @@ - System Accounts + 系統帳號 accounts @@ -287,7 +272,7 @@ - User Accounts + 使用者帳號 accounts @@ -310,17 +295,16 @@ - Modifying Accounts + 更改帳號 accounts modifying - There are a variety of different commands available in the - &unix; environment to manipulate user accounts. The most common - commands are summarized below, followed by more detailed - examples of their usage. + 在 &unix; 的環境之中提供了各式不同的指令管理使用者帳號， + 以下為較常使用的指令摘要及更詳細的使用範例。 + @@ -329,34 +313,30 @@ - Command - Summary + 指令 + 摘要 &man.adduser.8; - The recommended command-line application for adding - new users. + 新增使用者。 &man.rmuser.8; - The recommended command-line application for - removing users. + 移除使用者。 &man.chpass.1; - A flexible tool to change user database information. + 更改使用者資料。 &man.passwd.1; - The simple command-line tool to change user - passwords. + 更改使用者密碼。 &man.pw.8; - A powerful and flexible tool to modify all aspects - of user accounts. + 修改使用者的各種資料。 @@ -376,109 +356,15 @@ /usr/share/skel skeleton directory - &man.adduser.8; is a simple program for - adding new users. It creates entries in the system - passwd and group - files. It will also create a home directory for the new user, - copy in the default configuration files (dotfiles) from - /usr/share/skel, and can optionally mail - the new user a welcome message. - - In &os; 5.0, &man.adduser.8; was rewritten from a - Perl script to a shell script that acts as wrapper around - &man.pw.8;, so its usage is slightly different on &os; 4.X - and &os; 5.X. - - To create the initial configuration file, use - adduser -s -config_create. - - The makes &man.adduser.8; - default to - quiet. We use later when we want to - change defaults. - - Next, we configure &man.adduser.8; - defaults, and create our first user account, since using - root for normal usage is evil and - nasty. + &man.adduser.8; 是一支新增使用者的簡單程式。 + 它會建立資料於系統的 passwd 與 + group + 檔案之中。 同時也會建立使用者的家目錄，從 + /usr/share/skel 複製預設的組態檔(dotfiles)， + 並可以選擇性的郵件通知新使用者歡迎訊息。 - Configuring <command>adduser</command> and adding a - user on &os; 4.X - - &prompt.root; adduser -v -Use option ``-silent'' if you don't want to see all warnings and questions. -Check /etc/shells -Check /etc/master.passwd -Check /etc/group -Enter your default shell: csh date no sh tcsh zsh [sh]: zsh -Your default shell is: zsh -> /usr/local/bin/zsh -Enter your default HOME partition: [/home]: -Copy dotfiles from: /usr/share/skel no [/usr/share/skel]: -Send message from file: /etc/adduser.message no -[/etc/adduser.message]: no -Do not send message -Use passwords (y/n) [y]: y - -Write your changes to /etc/adduser.conf? (y/n) [n]: y - -Ok, let's go. -Don't worry about mistakes. I will give you the chance later to correct any input. -Enter username [a-z0-9_-]: jru -Enter full name []: J. Random User -Enter shell csh date no sh tcsh zsh [zsh]: -Enter home directory (full path) [/home/jru]: -Uid [1001]: -Enter login class: default []: -Login group jru [jru]: -Login group is ``jru''. Invite jru into other groups: guest no -[no]: wheel -Enter password []: -Enter password again []: - -Name: jru -Password: **** -Fullname: J. Random User -Uid: 1001 -Gid: 1001 (jru) -Class: -Groups: jru wheel -HOME: /home/jru -Shell: /usr/local/bin/zsh -OK? (y/n) [y]: y -Added user ``jru'' -Copy files from /usr/share/skel to /home/jru -Add another user? (y/n) [y]: n -Goodbye! -&prompt.root; - - - In summary, we changed the default shell to - zsh (an additional shell found in - the Ports Collection), and turned off the sending of a welcome mail to - added users. We then saved the configuration, - created an account for jru, and made - sure jru is in wheel - group (so that she may assume the role of - root with the &man.su.1; - command.) - - - The password you type in is not echoed, nor are asterisks - displayed. Make sure that you do not mistype the password. - - - - - Just use &man.adduser.8; without arguments - from now on, and you will not have to go through changing the - defaults. If the program asks you to change the defaults, - exit the program, and try the - option. - - - - Adding a user on &os; 5.X + 在 &os; 內新增使用者 &prompt.root; adduser Username: jru @@ -510,6 +396,11 @@ Add another user? (yes/no): no Goodbye! &prompt.root; + + + 您輸入的密碼並不會回應到螢幕，所以不會以星號顯示 + 。 請確定您所輸入的密碼無誤。 + @@ -521,62 +412,50 @@ Goodbye! removing - You can use &man.rmuser.8; to - completely remove a user from the system. - &man.rmuser.8; performs the following - steps: + 您可以使用 &man.rmuser.8; 來將使用者從系統之中完全移除 + &man.rmuser.8; 會執行以下動作: - Removes the user's &man.crontab.1; entry (if - any). + 移除該使用者的 &man.crontab.1; 資料 (如果存在)。 - Removes any &man.at.1; jobs belonging to the - user. + 移除所有屬於該使用者的 &man.at.1; 工作。 - Kills all processes owned by the user. + 中止所有該使用者擁有的程序。 - Removes the user from the system's local password - file. + 移除系統本機密碼檔中該使用者的資料。 - Removes the user's home directory (if it is owned by - the user). + 移除該使用者的家目錄 (如果為該使用者所有)。 - Removes the incoming mail files belonging to the user - from /var/mail. + 移除 /var/mail 中屬於該使用者的郵件。 - Removes all files owned by the user from temporary - file storage areas such as /tmp. + 移除暫存空間 (如: /tmp) 中所有屬於該使用者的檔案。 - Finally, removes the username from all groups to which - it belongs in /etc/group. - + 最後，在 /etc/group 檔內移除該使用者帳號。 + + - If a group becomes empty and the group name is the - same as the username, the group is removed; this - complements the per-user unique groups created by - &man.adduser.8;. + 若該群組已無成員，或者是群組名稱與該使用者名稱相同時， + 則群組將會被移除； 此操作會與 &man.adduser.8; + 所建立的帳號群組相對應。 - - &man.rmuser.8; cannot be used to remove - superuser accounts, since that is almost always an indication - of massive destruction. + &man.rmuser.8; 無法移除系統管理者帳號帳號， + 因為這即代表嚴重的破壞行為。 - By default, an interactive mode is used, which attempts to - make sure you know what you are doing. + 為了確認您的操作，預設採互動模式。 - <command>rmuser</command> Interactive Account Removal + <command>rmuser</command> 帳號移除 &prompt.root; rmuser jru Matching password entry: @@ -597,27 +476,19 @@ Removing files belonging to jru from /var/tmp/vi.recover: done. <command>chpass</command> chpass - &man.chpass.1; changes user database - information such as passwords, shells, and personal - information. + &man.chpass.1; 可更改使用者資料如: 密碼、Shell及個人資訊。 - Only system administrators, as the superuser, may change - other users' information and passwords with - &man.chpass.1;. + 僅系統管理者即系統管理者帳號可利用 &man.chpass.1; 更改其他使用者的資訊及密碼 - When passed no options, aside from an optional username, - &man.chpass.1; displays an editor - containing user information. When the user exists from the - editor, the user database is updated with the new - information. + 除了指定使用者名稱，當不加參數時，&man.chpass.1; 會將使用者資訊顯示於編輯器當中。 + 並於使用者離開編輯器時更新使用者資訊。 - In &os; 5.X, you will be asked for your password - after exiting the editor if you are not the superuser. + 若您並非系統管理者帳號，在離開編輯器前會詢問您的密碼。 - Interactive <command>chpass</command> by Superuser + 系統管理者帳號 <command>chpass</command> #Changing user database information for jru. Login: jru @@ -636,11 +507,10 @@ Home Phone: Other information: - The normal user can change only a small subset of this - information, and only for themselves. + 一般使用者僅可更改自己的少部份資訊。 - Interactive <command>chpass</command> by Normal User + 一般使用者 <command>chpass</command> #Changing user database information for jru. Shell: /usr/local/bin/zsh @@ -652,14 +522,10 @@ Other information: - &man.chfn.1; and &man.chsh.1; are - just links to &man.chpass.1;, as - are &man.ypchpass.1;, - &man.ypchfn.1;, and - &man.ypchsh.1;. NIS support is automatic, so - specifying the yp before the command is - not necessary. If this is confusing to you, do not worry, NIS will - be covered in . + &man.chfn.1; 與 &man.chsh.1; 即為 &man.chpass.1;，也同 + &man.ypchpass.1;、&man.ypchfn.1; 與 &man.ypchsh.1;。 + NIS 支援是自動的，所以無需在指令前加上 yp。 + 若這會困擾您，請不必擔心， 將函蓋 NIS 的部份的說明。 @@ -670,17 +536,15 @@ Other information: accounts changing password - &man.passwd.1; is the usual way to - change your own password as a user, or another user's password - as the superuser. + &man.passwd.1; 是更改密碼常用的方式，除了超級管理者可更改其他使用者的密碼外 + 使用者僅能更改自己的密碼。 - To prevent accidental or unauthorized changes, the original - password must be entered before a new password can be set. + 為了避免意外或未經同意的修改，在更新密碼前需輸入原密碼。 - Changing Your Password + 更改您的密碼 &prompt.user; passwd Changing local password for jru. @@ -692,7 +556,7 @@ passwd: done - Changing Another User's Password as the Superuser + 以系統管理者帳號去更改其他使用者的密碼 &prompt.root; passwd jru Changing local password for jru. @@ -703,10 +567,8 @@ passwd: done - As with &man.chpass.1;, - &man.yppasswd.1; is just a link to - &man.passwd.1;, so NIS works with either - command. + &man.chpass.1;、 + &man.yppasswd.1; 即為 &man.passwd.1;，皆支援 NIS。 @@ -715,32 +577,32 @@ passwd: done <command>pw</command> pw - &man.pw.8; is a command line utility to create, remove, - modify, and display users and groups. It functions as a front - end to the system user and group files. &man.pw.8; - has a very powerful set of command line options that make it - suitable for use in shell scripts, but new users may find it - more complicated than the other commands presented - here. + &man.pw.8; 用來建立、移除、修改及查詢使用者及群組。 + 其功能即為系統使用者及群組檔案的前端。&man.pw.8; 擁有大量的指令參數 + 較適合使用於 shell script 中，對新手來說會此指令較其他指令複雜許多。 + - 對帳號的資源運用作限制 + 使用者資源限制 limiting users accounts limiting - If you have users, the ability to limit their system use may - have come to mind. FreeBSD provides - several ways an administrator can limit the amount of system - resources an individual may use. These limits are - divided into two sections: disk quotas, and other resource - limits. + + + 若您擁有許多使用者，接下會想到該如何限制使用的資源。 + FreeBSD 提供管理者許多方法來限制系統的資源給每個人使用。 + 這些限制分為兩個部份: 磁碟限額，以及其他資源限制。 + quotas @@ -748,59 +610,46 @@ passwd: done quotas disk quotas - Disk quotas limit disk usage to users, and - they - provide a way to quickly check that usage without - calculating it every time. Quotas are discussed in . + 磁碟限額可以限制使用者的磁碟用量， + 它提供了一種方法可以快速的檢查並計算用量 + 而不需每次重新計算， + 關於磁碟限額將於 會討論。 - The other resource limits include ways to limit the amount of - CPU, memory, and other resources a user may consume. These are - defined using login classes and are discussed here. + 其他資源限制包含了 CPU、記憶體、以及其他每個使用者可使用 + 的資源做限制，這些限制可使用 Login class 來定義並於在本章討論。 /etc/login.conf - Login classes are defined in - /etc/login.conf. The precise semantics are - beyond the scope of this section, but are described in detail in the - &man.login.conf.5; manual page. It is sufficient to say that each - user is assigned to a login class (default by - default), and that each login class has a set of login capabilities - associated with it. A login capability is a - name=value - pair, where name is a well-known - identifier and value is an arbitrary - string processed accordingly depending on the name. Setting up login - classes and capabilities is rather straight-forward and is also - described in &man.login.conf.5;. + Login class 定義於 + /etc/login.conf。 明確語意不會在本節說明 + 但詳細的描述會在 &man.login.conf.5; 文件中。 每使用者預設被 + 分配到一個 Login class 中 (預設為 default)， + 而每個 Login class 都有其資源的限制(Login capabilitiy)。 + Login capabilitiy 以 名稱=值 成對， + 名稱 代表資源的種類，而 值 + 為任意的字串，為對應名稱的參數。 設定 Login class 及 Login capability 相當簡單，並同樣在 + &man.login.conf.5; 中詳細說明。 - The system does not normally read the configuration in - /etc/login.conf directly, but reads the database - file /etc/login.conf.db which provides - faster lookups. - To generate /etc/login.conf.db from - /etc/login.conf, execute the following - command: + 系統不會直接讀取 /etc/login.conf 的組態 + 而是讀取提供查詢較快的 /etc/login.conf.db 資料庫檔。 + 要從 /etc/login.conf 產生 /etc/login.conf.db + 需要執行以下指令: &prompt.root; cap_mkdb /etc/login.conf - Resource limits are different from plain vanilla login - capabilities in two ways. First, for every limit, there is a soft - (current) and hard limit. A soft limit may be adjusted by the user - or application, but may be no higher than the hard limit. The latter - may be lowered by the user, but never raised. Second, most resource - limits apply per process to a specific user, not the user as a whole. - Note, however, that these differences are mandated by the specific - handling of the limits, not by the implementation of the login - capability framework (i.e., they are not really - a special case of login capabilities). + 資源限制於一般的 Login capability 有兩點不同。 + 第一，每種限制分為軟性限制及硬性限制。 + 軟性限制可由使用者或應用程式調整，但不能高於硬性限制。 + 後者限制可被使用者降低，但無法再提高。 + 第二，多數資源限制是針對每個使用者的個別行程限制，而不是使用者的所有行程。 + 注意，這些差異是由指定的限制程式托管，並非實作於 Login capability 的架構 + (例如，這些不是 真正 登入容量的特例)。 - And so, without further ado, below are the most commonly used - resource limits (the rest, along with all the other login - capabilities, may be found in &man.login.conf.5;). + 另外，為了避免麻煩，以下為幾個常用的資源限制 + (剩下及其他的 Login capability 可在 &man.login.conf.5; 中找到說明)。 @@ -833,7 +682,7 @@ passwd: done cputime This is the maximum amount of CPU time a user's process may - consume. Offending processes will be killed by the kernel. + consume. Offending processes will be killed by the kernel. This is a limit on CPU time @@ -844,7 +693,6 @@ passwd: done legitimate task—can easily use almost 100% of a CPU for some time. - @@ -1016,7 +864,7 @@ passwd: done - Groups + 群組 groups diff --git a/zh_TW.Big5/books/porters-handbook/book.sgml b/zh_TW.Big5/books/porters-handbook/book.sgml index 1611137383..90cf5ca7b7 100644 --- a/zh_TW.Big5/books/porters-handbook/book.sgml +++ b/zh_TW.Big5/books/porters-handbook/book.sgml @@ -675,7 +675,7 @@ DOS2UNIX_REGEX= .*\.(c|cpp|h) - Configuring + 設定 Include any additional customization commands in your configure script and save it in the @@ -8446,13 +8446,9 @@ etc/orbit.conf.sample &prompt.root; (cd /var/tmp/$(make -V PORTNAME) && find -d * -type d) | sort | comm -13 OLD-DIRS - | sort -r | sed -e 's#^#@dirrm #' >> pkg-plist - Finally, you need to tidy up the packing list by hand; it is not - all automated. Manual pages should be listed in - the port's Makefile under - MANn, and not in the - package list. User configuration files should be removed, or - installed as - filename.sample. + 最後，您應該手動整理檔案清單（這不是全部自動化處理的）。Man page 則應該利用 MANn 的方式 + 寫在 port 的 Makefile 而不是寫在檔案清單中。 + 使用者設定檔應該移除，或更名為filename.sample。 The info/dir file should not be listed and appropriate install-info lines should be added as noted in the info