# Debian GNU/Linux Installation Guide msgid "" msgstr "" "Project-Id-Version: d-i-manual\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" "POT-Creation-Date: 2023-08-08 23:04+0000\n" "PO-Revision-Date: 2005-07-18 13:49+0800\n" "Last-Translator: Jhang, Jia-Wei\n" "Language-Team: debian-chinese-big5 \n" "Language: zh_TW\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #: preparing.xml:5 #, no-c-format msgid "Before Installing &debian-gnu;" msgstr "安裝 &debian-gnu; 之前" #. Tag: para #: preparing.xml:6 #, no-c-format msgid "" "This chapter deals with the preparation for installing &debian; before you " "even boot the installer. This includes backing up your data, gathering " "information about your hardware, and locating any necessary information." msgstr "" "本章用於處理在開機安裝程式以安裝 &debian; 之前的準備工作。這包括備份您的資" "料，搜集您的硬體資訊，以及取得其他一些必要的資料。" #. Tag: title #: preparing.xml:19 #, no-c-format msgid "Overview of the Installation Process" msgstr "安裝概述" #. Tag: para #: preparing.xml:20 #, no-c-format msgid "" "First, just a note about re-installations. With &debian;, a circumstance " "that will require a complete re-installation of your system is very rare; " "perhaps mechanical failure of the hard disk would be the most common case." msgstr "" "首先，提一下關於重新安裝的事情。使用 &debian; 時，必須進行完全重新安裝的情況" "非常少見，可能導致這種情況的大多是硬碟的物理故障。" #. Tag: para #: preparing.xml:27 #, no-c-format msgid "" "Many common operating systems may require a complete installation to be " "performed when critical failures take place or for upgrades to new OS " "versions. Even if a completely new installation isn't required, often the " "programs you use must be re-installed to operate properly in the new OS." msgstr "" "許多常見的作業系統在遇到嚴重錯誤或者要升級到新的版本時，必須進行重新安裝。就" "算不需要完全重新安裝，您通常還得把您的應用程式在新系統裡也再重新安裝一遍才" "行。" #. Tag: para #: preparing.xml:35 #, no-c-format msgid "" "Under &debian-gnu;, it is much more likely that your OS can be repaired " "rather than replaced if things go wrong. Upgrades never require a wholesale " "installation; you can always upgrade in-place. And the programs are almost " "always compatible with successive OS releases. If a new program version " "requires newer supporting software, the &debian; packaging system ensures " "that all the necessary software is automatically identified and installed. " "The point is, much effort has been put into avoiding the need for re-" "installation, so think of it as your very last option. The installer is " "not designed to re-install over an existing system." msgstr "" "在 &debian-gnu; 裡，如果作業系統遇到錯誤，大多數的時候您都能把它修復而不用重" "新安裝。在這裡，升級不再需要進行大規模的安裝動作，您可以就地升級它，而這些程" "式也總能和新版的作業系統和平共處。如果一個程式的新版本需要其他程式的更新來支" "援它，&debian; 軟體套件管理系統會自動幫您把所有必須的軟體一併安裝上。關鍵是，" "&debian; 為了避免重新安裝而做了大量努力，所以您盡可以不用去煩心這些問題：我們" "的安裝程式不是設計來重裝您的舊系統的。" #. Tag: para #: preparing.xml:48 #, no-c-format msgid "" "Here's a road map for the steps you will take during the installation " "process." msgstr "以下將帶領您走過安裝過程的每個步驟：" #. Tag: para #: preparing.xml:56 #, no-c-format msgid "" "Back up any existing data or documents on the hard disk where you plan to " "install." msgstr "把將要用來安裝系統的硬碟上的所有資料或者文件都備份下來﹔" #. Tag: para #: preparing.xml:62 #, no-c-format msgid "" "Gather information about your computer and any needed documentation, before " "starting the installation." msgstr "在開始安裝之前，收集您電腦的硬體資料和可能會用到的文件﹔" #. Tag: para #: preparing.xml:68 #, no-c-format msgid "Create partitionable space for &debian; on your hard disk." msgstr "在硬碟上為 &debian; 保留一塊可以用來建立分割區的空間﹔" #. Tag: para #: preparing.xml:73 #, fuzzy, no-c-format #| msgid "" #| "Locate and/or download the installer software and any specialized driver " #| "files your machine requires (except &debian; CD users)." msgid "" "Locate and/or download the installer software and any specialized driver or " "firmware files your machine requires." msgstr "" "如果您不是使用 &debian; 安裝光碟，請尋找和 (或) 下載安裝程式軟體，還有用於您" "電腦上特殊硬體的驅動程式﹔" #. Tag: para #: preparing.xml:79 #, no-c-format msgid "" "Set up boot media such as CDs/DVDs/USB sticks or provide a network boot " "infrastructure from which the installer can be booted." msgstr "" #. Tag: para #: preparing.xml:85 #, no-c-format msgid "Boot the installation system." msgstr "開機安裝系統﹔" #. Tag: para #: preparing.xml:90 #, fuzzy, no-c-format msgid "Select the installation language." msgstr "選擇要安裝的語言﹔" #. Tag: para #: preparing.xml:95 #, no-c-format msgid "Activate the ethernet network connection, if available." msgstr "如果可能，啟用網路連結﹔" #. Tag: para #: preparing.xml:101 #, no-c-format msgid "Configure one network interface." msgstr "設定一個網路介面﹔" # index.docbook:106, index.docbook:140 #. Tag: para #: preparing.xml:106 #, no-c-format msgid "Open an ssh connection to the new system." msgstr "開啟新系統的 ssh 連線﹔" #. Tag: para #: preparing.xml:111 #, no-c-format msgid "Attach one or more DASDs (Direct Access Storage Device)." msgstr "加上一個或多個直接存取儲存設備(Direct Access Storage Device, DASD)﹔" #. Tag: para #: preparing.xml:117 #, no-c-format msgid "" "If necessary, resize existing partitions on your target harddisk to make " "space for the installation." msgstr "" #. Tag: para #: preparing.xml:122 #, no-c-format msgid "Create and mount the partitions on which &debian; will be installed." msgstr "建立並掛載用來安裝 &debian; 的分割區﹔" #. Tag: para #: preparing.xml:127 #, no-c-format msgid "" "Watch the automatic download/install/setup of the base system." msgstr "等待自動化的下載、安裝和設置基本系統。" #. Tag: para #: preparing.xml:133 #, no-c-format msgid "Select and install additional software." msgstr "" #. Tag: para #: preparing.xml:138 #, no-c-format msgid "" "Install a boot loader which can start up &debian-gnu; " "and/or your existing system." msgstr "" "安裝boot loader，它負責開機 &debian-gnu; 和 (或) 已有" "的其他系統。" #. Tag: para #: preparing.xml:144 #, fuzzy, no-c-format msgid "Load the newly installed system for the first time." msgstr "第一次載入新安裝的系統，做一些系統初始設定﹔" #. Tag: para #: preparing.xml:151 #, no-c-format msgid "" "For &arch-title; you have the option of using a an experimental an experimental graphical version of the installation " "system. For more information about this graphical installer, see ." msgstr "" #. Tag: para #: preparing.xml:160 #, no-c-format msgid "" "If you have problems during the installation, it helps to know which " "packages are involved in which steps. Introducing the leading software " "actors in this installation drama:" msgstr "" "如果您在安裝過程中遇到問題，下面的資訊可以幫助您找到每個步驟裡牽涉到的軟體套" "件。有關這場安裝「戲劇」的「主角」的介紹：" #. Tag: para #: preparing.xml:166 #, fuzzy, no-c-format msgid "" "The installer software, debian-installer, is the " "primary concern of this manual. It detects hardware and loads appropriate " "drivers, uses dhcp-client to set up the network " "connection, runs debootstrap to install the base " "system packages, and runs tasksel to allow you to " "install certain additional software. Many more actors play smaller parts in " "this process, but debian-installer has completed its " "task when you load the new system for the first time." msgstr "" "安裝軟體，debian-installer，是本手冊的主要焦點。它將偵" "側硬體並掛載適當的驅動程式，使用 dhcp-client去設定網路" "連線，並且執行 debootstrap 去安裝基本系統的軟體套件。 " "在這個過程中，還有許多其他程式扮演著各自的角色，而 debian-" "installer 將一直到您第一次開機新系統時才完成它的使命。" #. Tag: para #: preparing.xml:178 #, no-c-format msgid "" "To tune the system to your needs, tasksel allows you " "to choose to install various predefined bundles of software like a Web " "server or a Desktop environment." msgstr "" #. Tag: para #: preparing.xml:184 #, no-c-format msgid "" "One important option during the installation is whether or not to install a " "graphical desktop environment, consisting of the X Window System and one of " "the available graphical desktop environments. If you choose not to select " "the Desktop environment task, you will only have a relatively " "basic, command line driven system. Installing the Desktop environment task " "is optional because in relation to a text-mode-only system it requires a " "comparatively large amount of disk space and because many &debian-gnu; " "systems are servers which don't really have any need for a graphical user " "interface to do their job." msgstr "" #. Tag: para #: preparing.xml:197 #, fuzzy, no-c-format msgid "" "Just be aware that the X Window System is completely separate from " "debian-installer, and in fact is much more " "complicated. Troubleshooting of the X Window System is not within the scope " "of this manual." msgstr "" "X 系統是與 debian-installer 完全分開的，實際上它複雜的" "多了 X 視窗安裝系統的安裝和問題解答不在本手冊所關注的範圍之內。" #. Tag: title #: preparing.xml:212 #, no-c-format msgid "Back Up Your Existing Data!" msgstr "備份您的所有資料！" #. Tag: para #: preparing.xml:213 #, fuzzy, no-c-format msgid "" "Before you start, make sure to back up every file that is now on your " "system. If this is the first time a non-native operating system is going to " "be installed on your computer, it is quite likely you will need to re-" "partition your disk to make room for &debian-gnu;. Anytime you partition " "your disk, you run a risk of losing everything on the disk, no matter what " "program you use to do it. The programs used in the installation of &debian-" "gnu; are quite reliable and most have seen years of use; but they are also " "quite powerful and a false move can cost you. Even after backing up, be " "careful and think about your answers and actions. Two minutes of thinking " "can save hours of unnecessary work." msgstr "" "開始安裝之前，請確定您已經對系統中所有資料都進行了備份。除了購買機器時預先安" "裝的作業系統以外，如果這是您電腦上的第一個非原始作業系統，很可能您得對硬碟進" "行重新分割，為 &debian; 騰出安裝的空間。不管您用什麼程式，分割區都會使硬碟上" "的所有資料消失。我們的安裝過程中使用的分割程式經過多年使用之後，被證明非常可" "靠，但它的功能也非常強大，您可能會為一次錯誤操作而付出代價。即使是已經備份過" "資料，您也要謹慎使用，最好在每次操作之前先認真考慮一下：兩分鐘的思考可能會為" "您節省幾個小時的不必要恢復工作。" #. Tag: para #: preparing.xml:226 #, fuzzy, no-c-format #| msgid "" #| "If you are creating a multi-boot system, make sure that you have the " #| "distribution media of any other present operating systems on hand. " #| "Especially if you repartition your boot drive, you might find that you " #| "have to reinstall your operating system's boot loader, or in many cases " #| "the whole operating system itself and all files on the affected " #| "partitions." msgid "" "If you are creating a multi-boot system, make sure that you have the " "distribution media of any other present operating systems on hand. Even " "though this is normally not necessary, there might be situations in which " "you could be required to reinstall your operating system's boot loader to " "make the system boot or in a worst case even have to reinstall the complete " "operating system and restore your previously made backup." msgstr "" "如果您想把電腦做成多重開機的系統，請先確定您手頭上有電腦裡已存在的作業系統的" "安裝媒介。特別是當您把開機磁碟重新分割以後，您可能會發現必須重新安裝原有作業" "系統的 boot-loader，某些情況下，還得重新安裝該作業系統並恢復受影響分割區上的" "檔案。" #. Tag: title #: preparing.xml:245 #, no-c-format msgid "Information You Will Need" msgstr "一些有用的資料" #. Tag: title #: preparing.xml:248 #, no-c-format msgid "Documentation" msgstr "文件" #. Tag: title #: preparing.xml:251 #, no-c-format msgid "Installation Manual" msgstr "安裝手冊" #. Tag: para #: preparing.xml:253 #, fuzzy, no-c-format msgid "This document you are now reading, in plain ASCII, HTML or PDF format." msgstr "這些文件以純文字、HTML 或者 PDF 格式發佈。" #. Tag: itemizedlist #: preparing.xml:259 #, no-c-format msgid "&list-install-manual-files;" msgstr "&list-install-manual-files;" #. Tag: para #: preparing.xml:265 #, no-c-format msgid "" "The document you are now reading, which is the official version of the " "Installation Guide for the &releasename; release of &debian;; available in " "various formats and " "translations." msgstr "" #. Tag: para #: preparing.xml:274 #, no-c-format msgid "" "The document you are now reading, which is a development version of the " "Installation Guide for the next release of &debian;; available in various formats and translations." msgstr "" #. Tag: title #: preparing.xml:286 #, no-c-format msgid "Hardware documentation" msgstr "硬體文件" #. Tag: para #: preparing.xml:287 #, no-c-format msgid "" "Often contains useful information on configuring or using your hardware." msgstr "通常包含設置和使用您的硬體的實用資料。" #. Tag: ulink #: preparing.xml:298 #, no-c-format msgid "The Debian Wiki hardware page" msgstr "" #. Tag: ulink #: preparing.xml:304 #, fuzzy, no-c-format msgid "Linux/MIPS website" msgstr "Linux/MIPS Howto" #. Tag: title #: preparing.xml:313 #, no-c-format msgid "&arch-title; Hardware References" msgstr "&arch-title; Hardware References" #. Tag: para #: preparing.xml:314 #, no-c-format msgid "" "Documentation of &arch-title;-specific boot sequence, commands and device " "drivers (e.g. DASD, XPRAM, Console, OSA, HiperSockets and z/VM interaction)" msgstr "" #. Tag: ulink #: preparing.xml:325 #, no-c-format msgid "Device Drivers, Features, and Commands (Linux Kernel 3.2)" msgstr "" #. Tag: para #: preparing.xml:330 #, no-c-format msgid "" "IBM Redbook describing how Linux can be combined with z/VM on zSeries and " "&arch-title; hardware." msgstr "" "IBM Redbook 描述如何將 Linux 與 zSeries 的 z/VM 和 &arch-title; 硬體結合。" #. Tag: ulink #: preparing.xml:340 #, no-c-format msgid "Linux for &arch-title;" msgstr "用於 &arch-title; 的 Linux" #. Tag: para #: preparing.xml:346 #, no-c-format msgid "" "IBM Redbook describing the Linux distributions available for the mainframe. " "It has no chapter about &debian; but the basic installation concepts are the " "same across all &arch-title; distributions." msgstr "" "IBM Redbook 介紹可用於大型主機的 Linux 發行套件。其中沒有關於 &debian; 的章" "節，但對於所有的 &arch-title; 發行套件，基本的安裝概念是相同的。" #. Tag: ulink #: preparing.xml:357 #, no-c-format msgid "Linux for IBM eServer zSeries and &arch-title;: Distributions" msgstr "IBM eServer zSeries and &arch-title; 的發行套件：" #. Tag: title #: preparing.xml:367 #, no-c-format msgid "Finding Sources of Hardware Information" msgstr "尋找硬體資訊來源" #. Tag: para #: preparing.xml:368 #, no-c-format msgid "" "In many cases, the installer will be able to automatically detect your " "hardware. But to be prepared, we do recommend familiarizing yourself with " "your hardware before the install." msgstr "" "許多情況下，安裝程式能自動檢測您的硬體。但作為預備，我們建議您還是在安裝之前" "熟悉一下您的硬體比較好。" #. Tag: para #: preparing.xml:374 #, no-c-format msgid "Hardware information can be gathered from:" msgstr "取得硬體資料的途徑有：" #. Tag: para #: preparing.xml:381 #, no-c-format msgid "The manuals that come with each piece of hardware." msgstr "每個硬體附帶的手冊。" #. Tag: para #: preparing.xml:386 #, fuzzy, no-c-format #| msgid "" #| "The BIOS setup screens of your computer. You can view these screens when " #| "you start your computer by pressing a combination of keys. Check your " #| "manual for the combination. Often, it is the Delete key." msgid "" "The BIOS/UEFI setup screens of your computer. You can view these screens " "when you start your computer by pressing a combination of keys. Check your " "manual for the combination. Often, it is the Delete or the " "F2 key, but some manufacturers use other keys or key " "combinations. Usually upon starting the computer there will be a message " "stating which key to press to enter the setup screen." msgstr "" "您電腦 BIOS 設定畫面。在電腦開機時，您可以透過按鍵組合查看這些畫面。請從您的" "手冊確認按鍵。通常，它是 Delete 鍵。" #. Tag: para #: preparing.xml:396 #, no-c-format msgid "The cases and boxes for each piece of hardware." msgstr "每個硬體的包裝盒。" #. Tag: para #: preparing.xml:402 #, no-c-format msgid "The System window in the Windows Control Panel." msgstr "Windows 控制台裡面的系統視窗。" #. Tag: para #: preparing.xml:408 #, no-c-format msgid "" "System commands or tools in another operating system, including file manager " "displays. This source is especially useful for information about RAM and " "hard drive memory." msgstr "" "其他作業系統裡面的系統指令或工具，包括檔案管理員的顯示。該資源對瞭解隨機存取" "記憶體和硬碟特別有用。" #. Tag: para #: preparing.xml:415 #, no-c-format msgid "" "Your system administrator or Internet Service Provider. These sources can " "tell you the settings you need to set up your networking and e-mail." msgstr "" "您的系統管理員或者網際網路服務提供商。他們可以告訴您所需的設定網路和電子郵件" "的相關資料。" #. Tag: title #: preparing.xml:427 #, fuzzy, no-c-format #| msgid "Hardware Information Needed for an Install" msgid "Hardware Information Helpful for an Install" msgstr "安裝所需的硬體資料" #. Tag: entry #: preparing.xml:431 #, no-c-format msgid "Hardware" msgstr "硬體" #. Tag: entry #: preparing.xml:431 #, no-c-format msgid "Information You Might Need" msgstr "您需要瞭解的資料" #. Tag: entry #: preparing.xml:437 #, no-c-format msgid "Hard Drives" msgstr "硬碟" #. Tag: entry #: preparing.xml:438 #, no-c-format msgid "How many you have." msgstr "您擁有的容量" #. Tag: entry #: preparing.xml:440 #, no-c-format msgid "Their order on the system." msgstr "它們在系統上的順序" #. Tag: entry #: preparing.xml:442 #, no-c-format msgid "Whether IDE (also known as PATA), SATA or SCSI." msgstr "" # index.docbook:445, index.docbook:497 #. Tag: entry #: preparing.xml:444 preparing.xml:493 #, no-c-format msgid "Available free space." msgstr "可用空間" #. Tag: entry #: preparing.xml:445 #, no-c-format msgid "Partitions." msgstr "分割區。" #. Tag: entry #: preparing.xml:447 #, no-c-format msgid "Partitions where other operating systems are installed." msgstr "安裝有其他作業系統的分割區。" #. Tag: entry #: preparing.xml:475 #, fuzzy, no-c-format #| msgid "Network Settings" msgid "Network interfaces" msgstr "網路設置" #. Tag: entry #: preparing.xml:476 #, fuzzy, no-c-format #| msgid "Configure one network interface." msgid "Type/model of available network interfaces." msgstr "設定一個網路介面﹔" #. Tag: entry #: preparing.xml:480 #, no-c-format msgid "Printer" msgstr "印表機" # index.docbook:453, index.docbook:473, index.docbook:479, index.docbook:485 #. Tag: entry #: preparing.xml:481 #, no-c-format msgid "Model and manufacturer." msgstr "型號與製造商。" #. Tag: entry #: preparing.xml:485 #, no-c-format msgid "Video Card" msgstr "顯示卡" # index.docbook:453, index.docbook:473, index.docbook:479, index.docbook:485 #. Tag: entry #: preparing.xml:486 #, fuzzy, no-c-format #| msgid "Model and manufacturer." msgid "Type/model and manufacturer." msgstr "型號與製造商。" #. Tag: entry #: preparing.xml:490 #, no-c-format msgid "DASD" msgstr "DASD" #. Tag: entry #: preparing.xml:491 #, no-c-format msgid "Device number(s)." msgstr "設備編號。" # index.docbook:472, index.docbook:500 #. Tag: entry #: preparing.xml:496 #, no-c-format msgid "Network" msgstr "網路" # index.docbook:475, index.docbook:501 #. Tag: entry #: preparing.xml:497 #, no-c-format msgid "Type of adapter." msgstr "適配器類型。" #. Tag: entry #: preparing.xml:499 #, no-c-format msgid "Device numbers." msgstr "設備編號。" #. Tag: entry #: preparing.xml:500 #, no-c-format msgid "Relative adapter number for OSA cards." msgstr "OSA 卡的相對應適配器編號。" #. Tag: title #: preparing.xml:508 #, no-c-format msgid "Hardware Compatibility" msgstr "硬體相容性" #. Tag: para #: preparing.xml:510 #, fuzzy, no-c-format msgid "" "Many products work without trouble on &arch-kernel;. Moreover, hardware " "support in &arch-kernel; is improving daily. However, &arch-kernel; still " "does not run as many different types of hardware as some operating systems." msgstr "" "多數品牌的產品在 &arch-kernel; 上運作不會遇到麻煩。而且，對 &arch-kernel; 的" "硬體支援每天都在改善。 然而，&arch-kernel; 仍然不能像某些作業系統那樣可以在各" "種不同的硬體上運行。" #. Tag: para #: preparing.xml:516 #, no-c-format msgid "" "Drivers in &arch-kernel; in most cases are not written for a certain " "product or brand from a specific manufacturer, " "but for a certain hardware/chipset. Many seemingly different products/brands " "are based on the same hardware design; it is not uncommon that chip " "manufacturers provide so-called reference designs for " "products based on their chips which are then used by several different " "device manufacturers and sold under lots of different product or brand names." msgstr "" #. Tag: para #: preparing.xml:527 #, no-c-format msgid "" "This has advantages and disadvantages. An advantage is that a driver for one " "chipset works with lots of different products from different manufacturers, " "as long as their product is based on the same chipset. The disadvantage is " "that it is not always easy to see which actual chipset is used in a certain " "product/brand. Unfortunately sometimes device manufacturers change the " "hardware base of their product without changing the product name or at least " "the product version number, so that when having two items of the same brand/" "product name bought at different times, they can sometimes be based on two " "different chipsets and therefore use two different drivers or there might be " "no driver at all for one of them." msgstr "" #. Tag: para #: preparing.xml:540 #, no-c-format msgid "" "For USB and PCI/PCI-Express/ExpressCard devices, a good way to find out on " "which chipset they are based is to look at their device IDs. All USB/PCI/PCI-" "Express/ExpressCard devices have so called vendor and " "product IDs, and the combination of these two is usually the " "same for any product based on the same chipset." msgstr "" #. Tag: para #: preparing.xml:548 #, no-c-format msgid "" "On Linux systems, these IDs can be read with the lsusb " "command for USB devices and with the lspci -nn command " "for PCI/PCI-Express/ExpressCard devices. The vendor and product IDs are " "usually given in the form of two hexadecimal numbers, separated by a colon, " "such as 1d6b:0001." msgstr "" #. Tag: para #: preparing.xml:556 #, no-c-format msgid "" "An example for the output of lsusb: Bus 001 Device " "001: ID 1d6b:0002 Linux Foundation 2.0 root hub, whereby 1d6b is the " "vendor ID and 0002 is the product ID." msgstr "" #. Tag: para #: preparing.xml:562 #, no-c-format msgid "" "An example for the output of lspci -nn for an Ethernet " "card: 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., " "Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev " "06). The IDs are given inside the rightmost square brackets, i.e. " "here 10ec is the vendor- and 8168 is the product ID." msgstr "" #. Tag: para #: preparing.xml:570 #, no-c-format msgid "" "As another example, a graphics card could give the following output: " "04:00.0 VGA compatible controller [0300]: Advanced Micro Devices " "[AMD] nee ATI RV710 [Radeon HD 4350] [1002:954f]." msgstr "" #. Tag: para #: preparing.xml:576 #, no-c-format msgid "" "On Windows systems, the IDs for a device can be found in the Windows device " "manager on the tab details, where the vendor ID is prefixed " "with VEN_ and the product ID is prefixed with DEV_. On newer Windows " "systems, you have to select the property Hardware IDs in the " "device manager's details tab to actually see the IDs, as they are not " "displayed by default." msgstr "" #. Tag: para #: preparing.xml:586 #, no-c-format msgid "" "Searching on the internet with the vendor/product ID, &arch-kernel; and driver as the search terms often results in " "information regarding the driver support status for a certain chipset. If a " "search for the vendor/product ID does not yield usable results, a search for " "the chip code names, which are also often provided by lsusb and lspci " "(RTL8111/RTL8168B in the network card example " "and RV710 in the graphics card example), can help." msgstr "" #. Tag: title #: preparing.xml:599 #, no-c-format msgid "Testing hardware compatibility with a Live-System" msgstr "" #. Tag: para #: preparing.xml:601 #, no-c-format msgid "" "&debian-gnu; is also available as a so-called live system for " "certain architectures. A live system is a preconfigured ready-to-use system " "in a compressed format that can be booted and used from a read-only medium " "like a CD or DVD. Using it by default does not create any permanent changes " "on your computer. You can change user settings and install additional " "programs from within the live system, but all this only happens in the " "computer's RAM, i.e. if you turn off the computer and boot the live system " "again, everything is reset to its defaults. If you want to see whether your " "hardware is supported by &debian-gnu;, the easiest way is to run a &debian; " "live system on it and try it out." msgstr "" #. Tag: para #: preparing.xml:614 #, no-c-format msgid "" "There are a few limitations in using a live system. The first is that as all " "changes you do within the live system must be held in your computer's RAM, " "this only works on systems with enough RAM to do that, so installing " "additional large software packages may fail due to memory constraints. " "Another limitation with regards to hardware compatibility testing is that " "the official &debian-gnu; live system contains only free components, i.e. " "there are no non-free firmware files included in it. Such non-free packages " "can of course be installed manually within the system, but there is no " "automatic detection of required firmware files like in the &d-i;, so " "installation of non-free components must be done manually if needed." msgstr "" #. Tag: para #: preparing.xml:627 #, no-c-format msgid "" "Information about the available variants of the &debian; live images can be " "found at the Debian Live Images website." msgstr "" #. Tag: title #: preparing.xml:641 #, no-c-format msgid "Network Settings" msgstr "網路設置" #. Tag: para #: preparing.xml:643 #, fuzzy, no-c-format #| msgid "" #| "If your computer is connected to a network 24 hours a day (i.e., an " #| "Ethernet or equivalent connection — not a PPP connection), you " #| "should ask your network's system administrator for this information." msgid "" "If your computer is connected to a fixed network (i.e. an Ethernet or " "equivalent connection — not a dialup/PPP connection) which is " "administered by somebody else, you should ask your network's system " "administrator for this information:" msgstr "" "如果您的電腦一天 24 小時都連在網上 (即以太網路或相等的連接 — 而不是撥號" "連接)，您需要向您的網路系統管理員咨詢這項資料。" #. Tag: para #: preparing.xml:651 #, no-c-format msgid "Your host name (you may be able to decide this on your own)." msgstr "您的主機名(也許可以自己決定)。" #. Tag: para #: preparing.xml:656 #, no-c-format msgid "Your domain name." msgstr "您的網網域名稱。" #. Tag: para #: preparing.xml:661 #, no-c-format msgid "Your computer's IP address." msgstr "您電腦的 IP 位址。" #. Tag: para #: preparing.xml:666 #, no-c-format msgid "The netmask to use with your network." msgstr "您網路的網路遮罩。" #. Tag: para #: preparing.xml:671 #, no-c-format msgid "" "The IP address of the default gateway system you should route to, if your " "network has a gateway." msgstr "" "預設路由閘道的 IP 位址，如果您的網路有閘道器的話。" #. Tag: para #: preparing.xml:677 #, no-c-format msgid "" "The system on your network that you should use as a DNS (Domain Name " "Service) server." msgstr "您的網路中作為 DNS (網域名稱稱服務) 伺服器的系統。" #. Tag: para #: preparing.xml:685 #, fuzzy, no-c-format #| msgid "" #| "On the other hand, if your administrator tells you that a DHCP server is " #| "available and is recommended, then you don't need this information " #| "because the DHCP server will provide it directly to your computer during " #| "the installation process." msgid "" "If the network you are connected to uses DHCP (Dynamic Host Configuration " "Protocol) for configuring network settings, you don't need this information " "because the DHCP server will provide it directly to your computer during the " "installation process." msgstr "" "另一方面，如果您的系統管理員告訴您有 DHCP 伺服器可用，並且建議使用，那麼您不" "需瞭解這項資料，因為 DHCP 伺服器會在安裝過程中直接提供。" #. Tag: para #: preparing.xml:692 #, no-c-format msgid "" "If you have internet access via DSL or cable modem (i.e. over a cable tv " "network) and have a router (often provided preconfigured by your phone or " "catv provider) which handles your network connectivity, DHCP is usually " "available by default." msgstr "" #. Tag: para #: preparing.xml:700 #, no-c-format msgid "" "As a rule of thumb: if you run a Windows system in your home network and did " "not have to manually perform any network settings there to achieve Internet " "access, network connectivity in &debian-gnu; will also be configured " "automatically." msgstr "" #. Tag: para #: preparing.xml:707 #, fuzzy, no-c-format #| msgid "If you use a wireless network, you should also find out:" msgid "If you use a WLAN/WiFi network, you should find out:" msgstr "如果您有一個無線網路，您應該找出：" #. Tag: para #: preparing.xml:712 #, fuzzy, no-c-format #| msgid "ESSID of your wireless network." msgid "The ESSID (network name) of your wireless network." msgstr "您無線網路的 ESSID。" #. Tag: para #: preparing.xml:717 #, fuzzy, no-c-format #| msgid "WEP security key (if applicable)." msgid "The WEP or WPA/WPA2 security key to access the network (if applicable)." msgstr "WEP 安全金鑰 (如果可用)。" #. Tag: title #: preparing.xml:734 #, no-c-format msgid "Meeting Minimum Hardware Requirements" msgstr "滿足最低的硬體要求" #. Tag: para #: preparing.xml:735 #, no-c-format msgid "" "Once you have gathered information about your computer's hardware, check " "that your hardware will let you do the type of installation that you want to " "do." msgstr "" "一旦您收集好您的電腦硬體配備的相關資料，再檢查一下您的硬體，就可以讓您如願以" "償的安裝系統。" #. Tag: para #: preparing.xml:741 #, no-c-format msgid "" "Depending on your needs, you might manage with less than some of the " "recommended hardware listed in the table below. However, most users risk " "being frustrated if they ignore these suggestions." msgstr "" "基於您的需求，您也許可以用低於下面表格所列的配備安裝系統。但是，如果無視這些" "建議的話，多數使用者會安裝失敗。" #. Tag: para #: preparing.xml:747 #, fuzzy, no-c-format msgid "" "A Pentium 4, 1GHz system is the minimum recommended for a desktop system." msgstr "" "Pentium 100 是桌面系統的最低建議配備，而 Pentium II-300 則是伺服器要求的最低" "建議配備。" #. Tag: title #: preparing.xml:763 #, no-c-format msgid "Recommended Minimum System Requirements" msgstr "建議的最低系統需求" #. Tag: entry #: preparing.xml:767 #, no-c-format msgid "Install Type" msgstr "安裝類別" #. Tag: entry #: preparing.xml:768 #, no-c-format msgid "RAM (minimum)" msgstr "" #. Tag: entry #: preparing.xml:769 #, no-c-format msgid "RAM (recommended)" msgstr "" #. Tag: entry #: preparing.xml:770 #, no-c-format msgid "Hard Drive" msgstr "硬碟" #. Tag: entry #: preparing.xml:776 #, no-c-format msgid "No desktop" msgstr "無桌面系統" #. Tag: entry #: preparing.xml:777 #, no-c-format msgid "&ref-no-desktop-ram-minimum;" msgstr "&ref-no-desktop-ram-minimum;" #. Tag: entry #: preparing.xml:778 #, no-c-format msgid "&ref-no-desktop-ram-recommend;" msgstr "&ref-no-desktop-ram-recommend;" #. Tag: entry #: preparing.xml:779 #, no-c-format msgid "&ref-no-desktop-hd;" msgstr "&ref-no-desktop-hd;" #. Tag: entry #: preparing.xml:781 #, no-c-format msgid "With Desktop" msgstr "有桌面系統" #. Tag: entry #: preparing.xml:782 #, no-c-format msgid "&ref-with-desktop-ram-minimum;" msgstr "&ref-with-desktop-ram-minimum;" #. Tag: entry #: preparing.xml:783 #, no-c-format msgid "&ref-with-desktop-ram-recommend;" msgstr "&ref-with-desktop-ram-recommend;" #. Tag: entry #: preparing.xml:784 #, no-c-format msgid "&ref-with-desktop-hd;" msgstr "&ref-with-desktop-hd;" #. Tag: para #: preparing.xml:789 #, no-c-format msgid "" "The minimum values assumes that swap will be enabled and a non-liveCD image " "is used. The No desktop value assumes that the text-based " "installer (not the graphical one) is used." msgstr "" #. Tag: para #: preparing.xml:795 #, no-c-format msgid "" "The actual minimum memory requirements are a lot less than the numbers " "listed in this table. With swap enabled, it is possible to install &debian; " "with as little as &minimum-memory-strict;. The same goes for the disk space " "requirements, especially if you pick and choose which applications to " "install; see for additional " "information on disk space requirements." msgstr "" #. Tag: para #: preparing.xml:805 #, no-c-format msgid "" "The installer normally automatically enables memory-saving tricks to be able " "to run on such low-memory system, but on architectures that are less tested " "it may miss doing so. It can however be enabled manually by appending the " "lowmem=1 or even lowmem=2 boot " "parameter (see also and )." msgstr "" #. Tag: para #: preparing.xml:814 #, no-c-format msgid "" "On &architecture; the lowmem levels have not been tested, so automatic " "detection is probably outdated and you thus probably need to pass the boot parameter if your system has little memory." msgstr "" #. Tag: para #: preparing.xml:820 #, no-c-format msgid "" "Installation on systems with less memory " "Installation images that support the graphical installer require more memory " "than images that support only the text-based installer and should not be " "used on systems with less than &minimum-memory; of memory. If there is a " "choice between booting the text-based and the graphical installer, the " "former should be selected on such systems. or disk space " "available may be possible but is only advised for experienced users." msgstr "" #. Tag: para #: preparing.xml:837 #, no-c-format msgid "" "It is possible to run a graphical desktop environment on older or low-end " "systems, but in that case it is recommended to install a window manager that " "is less resource-hungry than those of the GNOME or KDE Plasma desktop " "environments; alternatives include xfce4, " "icewm and wmaker, but there " "are others to choose from." msgstr "" #. Tag: para #: preparing.xml:846 #, no-c-format msgid "" "It is practically impossible to give general memory or disk space " "requirements for server installations as those very much depend on what the " "server is to be used for." msgstr "" #. Tag: para #: preparing.xml:852 #, no-c-format msgid "" "Remember that these sizes don't include all the other materials which are " "usually to be found, such as user files, mail, and data. It is always best " "to be generous when considering the space for your own files and data." msgstr "" #. Tag: para #: preparing.xml:859 #, fuzzy, no-c-format msgid "" "Disk space required for the smooth operation of the &debian-gnu; system " "itself is taken into account in these recommended system requirements. " "Notably, the /var partition contains a lot of state " "information specific to &debian; in addition to its regular contents, like " "logfiles. The dpkg files (with information on all " "installed packages) can easily consume 40MB. Also, apt " "puts downloaded packages here before they are installed. You should usually " "allocate at least 200MB for /var, and a lot more if you " "install a graphical desktop environment." msgstr "" "要提醒您的是上面所說的空間大小沒有把其它任何資料數據包含在內。這通常包含使用" "者的文件、信件或者使用者的資料。一般來說，最好在為您自己的檔案和資料分配空間" "時，規劃得寬裕一些。尤其是 /var 分割區裡裝有許多 " "&debian; 的特定狀態資料和類似日誌檔案這樣普通內容。dpkg 所" "用的文件 (含有所有已安裝軟體套件的資料) 很容易就會消耗掉 20MB。另外，" "apt-get 會在安裝前將下載的軟體套件放在這裡。您應當最少分" "配 100MB 的空間給 /var。" #. Tag: title #: preparing.xml:883 #, no-c-format msgid "Pre-Partitioning for Multi-Boot Systems" msgstr "為多重開機系統事先分割磁碟" #. Tag: para #: preparing.xml:884 #, no-c-format msgid "" "Partitioning your disk simply refers to the act of breaking up your disk " "into sections. Each section is then independent of the others. It's roughly " "equivalent to putting up walls inside a house; if you add furniture to one " "room it doesn't affect any other room." msgstr "" "分割您的硬碟指的僅是將您的硬碟空間切分成幾塊。分割之後，每一塊都是獨立於其餘" "部分的單獨空間。這和在一個大房幾里砌堵牆有幾分相似 如果您在其中一間房間裡安置" "傢俱，不會對其它房間有任何影響。" #. Tag: para #: preparing.xml:891 #, no-c-format msgid "" "Whenever this section talks about disks you should translate " "this into a DASD or VM minidisk in the &arch-title; world. Also a machine " "means an LPAR or VM guest in this case." msgstr "" "本節中所有提到硬碟的地方，您應當把它解讀為為 &arch-title; 世界" "中的 DASD 或者 VM minidisk。同時，在這裡，一台機器意指的是 LPAR 或者是 VM 訪" "客。" #. Tag: para #: preparing.xml:897 #, fuzzy, no-c-format msgid "" "If you already have an operating system on your system (Windows, OS/2, MacOS, Solaris, FreeBSD, …) (VM, z/OS, OS/390, …) which uses the whole " "disk and you want to stick &debian; on the same disk, you will need to " "repartition it. &debian; requires its own hard disk partitions. It cannot be " "installed on Windows or Mac OS X partitions. It may be able to share some " "partitions with other Unix systems, but that's not covered here. At the very " "least you will need a dedicated partition for the &debian; root filesystem." msgstr "" "如果您已經在您的機器中安裝作業系統 (Windows 9x, " "Windows NT/2000/XP/2003/Vista/7, OS/2, MacOS, Solaris, FreeBSD, …) (VM, z/OS, OS/390, …) ，同時" "也希望把 Linux 裝在同一顆硬碟上，那麼您就必須重新對硬碟進行分割。&debian; 需" "要它自己專用的硬碟分割區。它不能被安裝在 Windows 或者 MacOS 的分割區上。它可" "以與其它 Linux 系統共享一些分割區，但是我們在這裡不會對此進行說明。最起碼，您" "要為 &debian; 的根目錄準備一個專用的分割區。" #. Tag: para #: preparing.xml:916 #, fuzzy, no-c-format msgid "" "You can find information about your current partition setup by using a " "partitioning tool for your current operating system, such as the integrated Disk Manager in Windows, such as Disk Utility, Drive Setup, HD Toolkit, or MacTools, such as the VM diskmap. Partitioning " "tools always provide a way to show existing partitions without making " "changes." msgstr "" "您可以透過目前作業系統中的分割工具軟體來獲知您現在的分割區狀況，如 fdisk 和 PartitionMagic，如 " "Drive Setup、HD Toolkit 和 MacTools，如 VM " "diskmap分割工具軟體總會提供一種辦法讓您查看現有的分割區情況，而不作" "任何改動。" #. Tag: para #: preparing.xml:925 #, no-c-format msgid "" "In general, changing a partition with a file system already on it will " "destroy any information there. Thus you should always make backups before " "doing any repartitioning. Using the analogy of the house, you would probably " "want to move all the furniture out of the way before moving a wall or you " "risk destroying it." msgstr "" "在一般情況下，改動一個已經建立檔案系統的分割區，會導致其中的資料遭到損毀。因" "而，您每次都應當在重新分割之前先做好備份。繼續拿房幾作比喻，在移動牆壁時，您" "最好在把擋路的傢俱都移開，否則就要冒著傢俱被破壞的危險。" #. Tag: para #: preparing.xml:933 #, no-c-format msgid "" "Several modern operating systems offer the ability to move and resize " "certain existing partitions without destroying their contents. This allows " "making space for additional partitions without losing existing data. Even " "though this works quite well in most cases, making changes to the " "partitioning of a disk is an inherently dangerous action and should only be " "done after having made a full backup of all data. For FAT/FAT32 and NTFS partitions as used by Windows systems, the " "ability to move and resize them losslessly is provided both by &d-i; as well " "as by the integrated Disk Manager of Windows." msgstr "" #. Tag: para #: preparing.xml:947 #, no-c-format msgid "" "To losslessly resize an existing FAT or NTFS partition from within &d-i;, go " "to the partitioning step, select the option for manual partitioning, select " "the partition to resize, and simply specify its new size." msgstr "" #. Tag: title #: preparing.xml:1020 #, no-c-format msgid "Pre-Installation Hardware and Operating System Setup" msgstr "安裝前硬體和作業系統的相關設定" #. Tag: para #: preparing.xml:1021 #, fuzzy, no-c-format #| msgid "" #| "This section will walk you through pre-installation hardware setup, if " #| "any, that you will need to do prior to installing &debian;. Generally, " #| "this involves checking and possibly changing firmware settings for your " #| "system. The firmware is the core software used by the " #| "hardware; it is most critically invoked during the bootstrap process " #| "(after power-up). Known hardware issues affecting the reliability of " #| "&debian-gnu; on your system are also highlighted." msgid "" "This section will walk you through pre-installation hardware setup, if any, " "that you will need to do prior to installing &debian;. Generally, this " "involves checking and possibly changing BIOS/UEFI/system firmware settings " "for your system. The BIOS/UEFI or system firmware is the core software used by the hardware; it is most critically " "invoked during the bootstrap process (after power-up)." msgstr "" "在本節中，我們將討論安裝之前有關硬體設定的一些問題。如果這些問題的確存在，您" "就需要在安裝 &debian; 前先做一些準備工作了。一般來說，準備工作包括：檢查韌體" "(firmware)以及為您的系統修改韌體中的設定。所謂韌體就是硬體運行" "所需的核心軟體。它在系統開機過程中有至關重要的作用。我們同時也會著於重提出一" "些硬體問題，您系統上這些硬體問題在將會影響到 &debian-gnu; 的可靠性。" #. Tag: title #: preparing.xml:1036 #, fuzzy, no-c-format #| msgid "Invoking the BIOS Set-Up Menu" msgid "Invoking the BIOS/UEFI Set-Up Menu" msgstr "使用 BIOS 設定選單" #. Tag: para #: preparing.xml:1038 #, fuzzy, no-c-format #| msgid "" #| "BIOS provides the basic functions needed to boot your machine to allow " #| "your operating system to access your hardware. Your system probably " #| "provides a BIOS setup menu, which is used to configure the BIOS. Before " #| "installing, you must ensure that your BIOS is set up " #| "correctly; not doing so can lead to intermittent crashes or an inability " #| "to install &debian;." msgid "" "The BIOS/UEFI provides the basic functions needed to boot your machine and " "to allow your operating system to access your hardware. Your system provides " "a BIOS/UEFI setup menu, which is used to configure the BIOS/UEFI. To enter " "the BIOS/UEFI setup menu you have to press a key or key combination after " "turning on the computer. Often it is the Delete or the " "F2 key, but some manufacturers use other keys. Usually upon " "starting the computer there will be a message stating which key to press to " "enter the setup screen." msgstr "" "BIOS 為啟動您的機器提供了基本的幫助，進而能讓您的作業系統能存取您的硬體。您的" "系統應該會有 BIOS 的設定選單，透過它，我們就能配置 BIOS。在進行安裝前，您" "一定要確保您 BIOS 的設置是正確無誤的。否則，可能會導致經" "常性的系統當機或者根本無法安裝 &debian;。" # index.docbook:1522, index.docbook:1865 #. Tag: title #: preparing.xml:1052 preparing.xml:1477 #, no-c-format msgid "Boot Device Selection" msgstr "選擇開機設備" #. Tag: para #: preparing.xml:1054 #, no-c-format msgid "" "Within the BIOS/UEFI setup menu, you can select which devices shall be " "checked in which sequence for a bootable operating system. Possible choices " "usually include the internal harddisks, the CD/DVD-ROM drive and USB mass " "storage devices such as USB sticks or external USB harddisks. On modern " "systems there is also often a possibility to enable network booting via PXE." msgstr "" #. Tag: para #: preparing.xml:1062 #, no-c-format msgid "" "Depending on the installation media (CD/DVD ROM, USB stick, network boot) " "you have chosen you should enable the appropriate boot devices if they are " "not already enabled." msgstr "" #. Tag: para #: preparing.xml:1068 #, no-c-format msgid "" "Most BIOS/UEFI versions allow you to call up a boot menu on system startup " "in which you select from which device the computer should start for the " "current session. If this option is available, the BIOS/UEFI usually displays " "a short message like press F12 for boot menu " "on system startup. The actual key used to select this menu varies from " "system to system; commonly used keys are F12, F11 and F8. Choosing a device from this menu does not " "change the default boot order of the BIOS/UEFI, i.e. you can start once from " "a USB stick while having configured the internal harddisk as the normal " "primary boot device." msgstr "" #. Tag: para #: preparing.xml:1082 #, no-c-format msgid "" "If your BIOS/UEFI does not provide you with a boot menu to do ad-hoc choices " "of the current boot device, you will have to change your BIOS/UEFI setup to " "make the device from which the &d-i; shall be booted the primary boot device." msgstr "" #. Tag: para #: preparing.xml:1088 #, no-c-format msgid "" "Unfortunately some computers may contain buggy BIOS/UEFI versions. Booting " "&d-i; from a USB stick might not work even if there is an appropriate option " "in the BIOS/UEFI setup menu and the stick is selected as the primary boot " "device. On some of these systems using a USB stick as boot medium is " "impossible; others can be tricked into booting from the stick by changing " "the device type in the BIOS/UEFI setup from the default USB harddisk or USB stick to USB ZIP or USB " "CDROM. In particular if " "you use an isohybrid installation image on a USB stick (see ), changing the device type to USB CDROM helps on some BIOSes which will not boot from a USB stick in USB " "harddisk mode. You may need to configure your BIOS/UEFI to enable " "USB legacy support." msgstr "" #. Tag: para #: preparing.xml:1104 #, no-c-format msgid "" "If you cannot manipulate the BIOS/UEFI to boot directly from a USB stick you " "still have the option of using an ISO copied to the stick. Boot &d-i; using " " and, after scanning the hard drives for " "an installer ISO image, select the USB device and choose an installation " "image." msgstr "" #. Tag: title #: preparing.xml:1170 #, no-c-format msgid "How to update bare metal ppc64el firmware" msgstr "" #. Tag: para #: preparing.xml:1171 #, no-c-format msgid "" "This is an excerpt from IBM PowerKVM on " "IBM POWER8." msgstr "" #. Tag: para #: preparing.xml:1176 #, no-c-format msgid "" "Open Power Abstraction Layer (OPAL) is the system firmware in the stack of " "POWER processor-based server." msgstr "" #. Tag: para #: preparing.xml:1181 #, no-c-format msgid "" "There may be instances when the user might have to upgrade the Power Systems " "firmware to a more recent level to acquire new features or additional " "support for devices." msgstr "" #. Tag: para #: preparing.xml:1187 #, no-c-format msgid "Make sure that the following requirements are met:" msgstr "" #. Tag: para #: preparing.xml:1192 #, fuzzy, no-c-format #| msgid "Their order on the system." msgid "an OS to be running on the system;" msgstr "它們在系統上的順序" #. Tag: para #: preparing.xml:1194 #, no-c-format msgid "the .img file of the OPAL level that the user needs to update to;" msgstr "" #. Tag: para #: preparing.xml:1196 #, no-c-format msgid "the machine isn't under HMC control." msgstr "" #. Tag: para #: preparing.xml:1200 #, no-c-format msgid "" "Power Systems has two sides of flash to boot firmware from, namely permanent " "and temporary. This provides a way to test firmware updates on the temporary " "side of the flash before committing the tested changes to the permanent " "side, thereby committing the new updates." msgstr "" #. Tag: para #: preparing.xml:1207 #, no-c-format msgid "Perform the following steps for the update:" msgstr "" #. Tag: para #: preparing.xml:1212 #, no-c-format msgid "" "Save the level of the existing firmware before really updating. In ASM, in " "the system menu, click Service Aids -> Service Processor Command " "Line, and run the following command:" msgstr "" #. Tag: screen #: preparing.xml:1216 #, no-c-format msgid "cupdcmd -f" msgstr "cupdcmd -f" #. Tag: para #: preparing.xml:1217 #, no-c-format msgid "" "Download the .img file of the level of firmware to be updated to a location " "in the host filesystem. Refer to IBM Fix " "Central for downloading the image file." msgstr "" #. Tag: para #: preparing.xml:1222 #, no-c-format msgid "" "Verify the image downloaded by running the following command and save the " "output." msgstr "" #. Tag: screen #: preparing.xml:1225 #, no-c-format msgid "$update_flash -v -f <file_name.img>" msgstr "" #. Tag: para #: preparing.xml:1227 #, no-c-format msgid "Update the firmware by running the following command." msgstr "" #. Tag: screen #: preparing.xml:1229 #, no-c-format msgid "$update_flash -f <file_name.img>" msgstr "" #. Tag: para #: preparing.xml:1235 #, no-c-format msgid "" "The command reboots the system and therefore, sessions if any, would be lost." msgstr "" #. Tag: para #: preparing.xml:1238 #, no-c-format msgid "Do not reboot or switch off the system until it is back." msgstr "" #. Tag: para #: preparing.xml:1245 #, no-c-format msgid "" "Verify the updated firmware level of the temporary side of the flash as in " "step 1." msgstr "" #. Tag: para #: preparing.xml:1248 #, no-c-format msgid "" "In case the update has to be reverted, the user can do so by running this " "command: \n" " $update_flash -r\n" " Rejection would reject only the temporary side " "of the flash. Therefore, the new level should be committed to the permanent " "side only after thorough testing of the new firmware." msgstr "" #. Tag: para #: preparing.xml:1255 #, no-c-format msgid "" "The new updated level can be committed to the permanent side of the flash by " "running the following command." msgstr "" #. Tag: screen #: preparing.xml:1258 #, no-c-format msgid "$update_flash -c" msgstr "$update_flash -c" #. Tag: title #: preparing.xml:1266 #, no-c-format msgid "Updating KVM guest firmware (SLOF)" msgstr "" #. Tag: para #: preparing.xml:1267 #, no-c-format msgid "" "Slimline Open Firmware (SLOF) is an implementation of the IEEE 1275 " "standard. It can be used as partition firmware for pSeries machines running " "on QEMU or KVM." msgstr "" #. Tag: para #: preparing.xml:1274 #, no-c-format msgid "" "The package qemu-slof is, in fact, a dependency of package qemu-system-ppc " "(which also provides the virtual package qemu-system-ppc64), and can be " "installed or updated via apt tool on Debian-based " "distros. Like so: \n" "# apt install qemu-slof\n" " SLOF can also be installed into rpm-based " "distribution systems, given the proper repository or rpm package. " "Additionally, the upstream source code is available at ." msgstr "" #. Tag: para #: preparing.xml:1289 #, no-c-format msgid "" "Thus, one can use a different SLOF file rather than the default, when " "running qemu-system, by adding the command line argument " "-bios <slof_file> when starting qemu." msgstr "" #. Tag: title #: preparing.xml:1299 #, no-c-format msgid "Updating PowerKVM hypervisor" msgstr "" #. Tag: title #: preparing.xml:1300 #, no-c-format msgid "Instructions for Netboot installation" msgstr "" #. Tag: para #: preparing.xml:1301 #, no-c-format msgid "" "You will need a DHCP/TFTP (BOOTP) server, as well as a web server. After " "downloading ibm-powerkvm-*-ppc64-service-*.iso, mount loop it and unpack it " "into some directory within your HTTP server www root structure (say " "wwwroot): \n" "# cd <directory-where-the-iso-is>\n" "# mkdir ./iso\n" "# sudo mount -o loop ibm-powerkvm-*-ppc64-service-*.iso ./iso\n" "# cp -a ./iso/* <path-to-wwwroot>\n" " Create the petitboot.conf file in a directory " "under your tftproot, say /tftproot/powerkvm, with the following contents: " "\n" "label PowerKVM Automated Install\n" "kernel http://YOUR-SERVER-IP/SOME-PATH-TO-wwwroot/ppc/ppc64/vmlinuz\n" "initrd http://YOUR-SERVER-IP/SOME-PATH-TO-wwwroot/ppc/ppc64/initrd.img\n" "append root=live:http://YOUR-SERVER-IP/SOME-PATH-TO-wwwroot/LiveOS/squashfs." "img repo=http://YOUR-SERVER-IP/SOME-PATH-TO-wwwroot/packages rd.dm=0 rd.md=0 " "console=hvc0 console=tty0\n" " Editing your dhcpd.conf, set this directive at " "the beginning: \n" "option conf-file code 209 = text;\n" " Add the system directive: " "\n" "host <your-system> {\n" " hardware ethernet <system macaddr>\n" " fixed-address <system ip>;\n" " option host-name \"<system hostname>\";\n" " option conf-file \"<powerkvm/petitboot.conf>\";\n" " }\n" " Reboot the dhcp server." msgstr "" #. Tag: para #: preparing.xml:1325 #, no-c-format msgid "Boot your PowerLinux machine." msgstr "" #. Tag: para #: preparing.xml:1329 #, no-c-format msgid "" "There should be the following option at petitboot (select it): " "\n" "\"Power KVM Automated Install\" \n" " The installer menu should appear automatically." msgstr "" #. Tag: title #: preparing.xml:1340 #, no-c-format msgid "Instructions for DVD" msgstr "" #. Tag: para #: preparing.xml:1341 #, no-c-format msgid "" "Boot the ISO ibm-powerkvm-*-ppc64-service-*.iso (either burn a DVD or make " "it virtual if using QEMU) and simply wait for the boot." msgstr "" #. Tag: para #: preparing.xml:1344 #, no-c-format msgid "" "There should be the following option at petitboot (select it): " "\n" "\"POWERKVM_LIVECD\" \n" " The installer menu should appear automatically." msgstr "" #. Tag: title #: preparing.xml:1365 #, no-c-format msgid "BIOS Setup" msgstr "BIOS 設置" #. Tag: para #: preparing.xml:1366 #, fuzzy, no-c-format #| msgid "" #| "In order to install &debian-gnu; on a &arch-title; or zSeries machine you " #| "have first boot a kernel into the system. The boot mechanism of this " #| "platform is inherently different to other ones, especially from PC-like " #| "systems: there are no floppy devices available at all. You will notice " #| "another big difference while you work with this platform: most (if not " #| "all) of the time you will work remote, with the help of some client " #| "session software like telnet, or a browser. This is due to that special " #| "system architecture where the 3215/3270 console is line-based instead of " #| "character-based." msgid "" "In order to install &debian-gnu; on a &arch-title; or zSeries machine you " "have first boot a kernel into the system. The boot mechanism of this " "platform is inherently different to other ones, especially from PC-like " "systems, and you will notice a big difference while you work with this " "platform: most (if not all) of the time you will work remote, with the help " "of some client session software like telnet, or a browser. This is due to " "that special system architecture where the 3215/3270 console is line-based " "instead of character-based." msgstr "" "為了安裝 &debian-gnu; 到 &arch-title; 或者 zSeries 機器上，您首先要將核心載入" "系統。在此平台上的開機機制與其他類型，特別是類 PC 的系統，有著本質上的不同：" "它根本就沒有軟碟機。您還會注意到此平台上的另外一個顯著差異：大多數 (如果不是" "全部) 的時間，您將借助於一些客戶端連線軟體如 telnet 或者一個瀏覽器， 透過遙控" "的方式使用。這歸因於該系統上的 3215/3270 控制台是線性，而不是字元型的。" #. Tag: para #: preparing.xml:1378 #, fuzzy, no-c-format #| msgid "" #| "Linux on this platform runs either natively on the bare machine, in a so-" #| "called LPAR (Logical Partition) or in a virtual machine supplied by the " #| "VM system. You can use a boot tape on all of those systems; you may use " #| "some other boot media, too, but those may not be generally available. For " #| "example, you can use the virtual card reader of a virtual machine, or " #| "boot from the HMC (Hardware Management Console) of an LPAR if the HMC and " #| "this option is available for you." msgid "" "Linux on this platform runs either natively on the bare machine, in a so-" "called LPAR (Logical Partition) or in a virtual machine supplied by the VM " "system. Boot media differs depending on the runtime mode. For example, you " "can use the virtual card reader of a virtual machine, or boot from the HMC " "(Hardware Management Console) of an LPAR if the HMC and this option is " "available for you." msgstr "" "Linux 在該平台上可以所謂的 LPAR(Logical Partition)方式在本地的本機上運行，或" "者在 VM 系統提供的虛擬機器上運行。您可以在所有的系統上使用開機磁帶﹔您也可以" "使用其他的媒介，但並不一定都可使用。例如，您可以在虛擬機器上使用虛擬讀卡器，" "或者在 HMC (Hardware Management Console) 可用的情況下，從 LPAR 上的 HMC 開" "機。" #. Tag: para #: preparing.xml:1387 #, fuzzy, no-c-format msgid "" "Before you actually perform an installation, you have to go over some design " "and preparation steps. IBM has made documentation available about the whole " "process, e.g. how to prepare an installation medium and how actually to boot " "from that medium. Duplicating that information here is neither possible nor " "necessary. However, we will describe here which kind of &debian;-specific " "data is needed and where to find it. Using both sources of information, you " "have to prepare your machine and the installation medium before you can " "perform a boot from it. When you see the welcome message in your client " "session, return to this document to go through the &debian;-specific " "installation steps." msgstr "" "在真正進行安裝之前，您必須仔細檢查一些設計和準備步驟。IBM 已經有整個過程的文" "件，例如，如何準備安裝媒介和如何從該媒介開機。我們無須在此複製那些資料。但我" "們會在此說明需要哪些規格的 &debian; 資料，以及在哪裡能找到它們。根據資料您必" "須將您的機器和安裝媒介準備好並以之開機。當您在客戶端對話中看到歡迎畫面，再返" "回本文件查看 &debian; 規格的安裝步驟。" #. Tag: title #: preparing.xml:1404 #, no-c-format msgid "Native and LPAR installations" msgstr "本地的 (Native) 和 LPAR 安裝" #. Tag: para #: preparing.xml:1405 #, no-c-format msgid "" "Please refer to chapter 5 of the Linux for &arch-title; Redbook " "and chapter 3.2 of the Linux for IBM eServer zSeries and &arch-title;: " "Distributions Redbook on how to set up an LPAR for Linux." msgstr "" "請參考 Linux for &arch-title; Redbook 第 5 章和 Linux for IBM " "eServer zSeries and &arch-title;: Distributions Redbook 第 3.2 節有關" "如何為 Linux 建立 LPAR 的部分。" #. Tag: title #: preparing.xml:1419 #, no-c-format msgid "Installation as a VM guest" msgstr "以一個 VM guest 安裝" #. Tag: para #: preparing.xml:1421 #, no-c-format msgid "" "Please refer to chapter 6 of the Linux for &arch-title; Redbook " "and chapter 3.1 of the Linux for IBM eServer zSeries and &arch-title;: " "Distributions Redbook on how to set up a VM guest for running Linux." msgstr "" "請參考 Linux for &arch-title; Redbook 第 6 章和 Linux for IBM " "eServer zSeries and &arch-title;: Distributions Redbook 第 3.1 節有關" "如何為運行 Linux 建立 VM guest 的部分。" #. Tag: para #: preparing.xml:1431 #, fuzzy, no-c-format #| msgid "" #| "You need to copy all the files from the generic sub-" #| "directory to your CMS disk. Be sure to transfer kernel.debian and initrd.debian in binary mode with a " #| "fixed record length of 80 characters." msgid "" "You need to copy all the files from the generic sub-" "directory to your CMS disk. Be sure to transfer kernel.debian and initrd.debian in binary mode with a fixed " "record length of 80 characters (by specifying BINARY " "and LOCSITE FIX 80 in your FTP client). " "parmfile.debian can be in either ASCII or EBCDIC " "format. A sample debian.exec script, which will punch " "the files in the proper order, is included with the images." msgstr "" "您需要從 generic 子目錄複製所有的文件到您的 CMS 磁碟。請" "確認 kernel.debian 和 initrd.debian 是以固定 80 個字元長度的二進位形式進行傳輸。" #. Tag: title #: preparing.xml:1448 #, no-c-format msgid "Setting up an installation server" msgstr "設置安裝伺服器" #. Tag: para #: preparing.xml:1450 #, no-c-format msgid "" "If you don't have a connection to the Internet (either directly or via a web " "proxy) you need to create a local installation server that can be accessed " "from your S/390. This server keeps all the packages you want to install and " "must make them available using NFS, HTTP or FTP." msgstr "" "如果您沒有連接到網際網路 (直接或者間接透過網路代理)，您需要設置一個能從您的 " "S/390 存取的本地安裝伺服器。該伺服器包含所有您需要安裝的軟體套件，並可以透過 " "NFS，HTTP 或 FTP 存取。" #. Tag: para #: preparing.xml:1458 #, fuzzy, no-c-format msgid "" "The installation server needs to copy the exact directory structure from any " "&debian-gnu; mirror, but only the S/390 and architecture-independent files " "are required. You can also copy the contents of all installation images into " "such a directory tree." msgstr "" "安裝伺服器需要從任意 &debian-gnu; 鏡像複製精確的目錄結構，當然只需複製 S/390 " "相關和一些獨立於架構的檔案。您也可以複製所有的安裝光碟片到這樣的目錄樹中。" #. Tag: emphasis #: preparing.xml:1467 #, no-c-format msgid "FIXME: more information needed — from a Redbook?" msgstr "FIXME: more information needed — from a Redbook?" #. Tag: title #: preparing.xml:1484 #, no-c-format msgid "ARM firmware" msgstr "" #. Tag: para #: preparing.xml:1486 #, no-c-format msgid "" "As already mentioned before, there is unfortunately no standard for system " "firmware on ARM systems. Even the behaviour of different systems which use " "nominally the same firmware can be quite different. This results from the " "fact that a large part of the devices using the ARM architecture are " "embedded systems, for which the manufacturers usually build heavily " "customized firmware versions and include device-specific patches. " "Unfortunately the manufacturers often do not submit their changes and " "extensions back to the mainline firmware developers, so their changes are " "not integrated into newer versions of the original firmware." msgstr "" #. Tag: para #: preparing.xml:1498 #, no-c-format msgid "" "As a result even newly sold systems often use a firmware that is based on a " "years-old manufacturer-modified version of a firmware whose mainline " "codebase has evolved a lot further in the meantime and offers additional " "features or shows different behaviour in certain aspects. In addition to " "that, the naming of onboard devices is not consistent between different " "manufacturer-modified versions of the same firmware, therefore it is nearly " "impossible to provide usable product-independend instructions for ARM-based " "systems." msgstr "" #. Tag: title #: preparing.xml:1511 #, no-c-format msgid "Debian-provided U-Boot (system firmware) images" msgstr "" #. Tag: para #: preparing.xml:1512 #, no-c-format msgid "" "Debian provides U-Boot images for various armhf systems that can load their " "U-Boot from an SD card at &armmp-uboot-img;. The U-Boot builds are offered " "in two formats: raw U-Boot components and a ready-made card image that can " "easily be written onto an SD card. The raw U-Boot components are provided " "for advanced users; the generally recommended way is to use one of the ready-" "made SD card images. They are named <system-type>.sdcard.img.gz and " "can be written to a card e.g. with zcat <system-" "type>.sdcard.img.gz > /dev/SD_CARD_DEVICE " "As with all images, please be aware that writing the image to an SD card " "wipes all previous contents of the card!" msgstr "" #. Tag: para #: preparing.xml:1527 #, no-c-format msgid "" "If Debian provides a U-Boot image for your system, it is recommended that " "you use this image instead of the vendor-provided U-Boot, as the version in " "Debian is usually newer and has more features." msgstr "" #. Tag: title #: preparing.xml:1535 #, no-c-format msgid "Setting the ethernet MAC address in U-Boot" msgstr "" #. Tag: para #: preparing.xml:1536 #, no-c-format msgid "" "The MAC address of every ethernet interface should normally be globally " "unique, and it technically has to be unique within its ethernet broadcast " "domain. To achieve this, the manufacturer usually allocates a block of MAC " "addresses from a centrally-administered pool (for which a fee has to be " "paid) and preconfigures one of these addresses on each item sold." msgstr "" #. Tag: para #: preparing.xml:1544 #, no-c-format msgid "" "In the case of development boards, sometimes the manufacturer wants to avoid " "paying these fees and therefore provides no globally unique addresses. In " "these cases the users themselves have to define MAC addresses for their " "systems. When no MAC address is defined for an ethernet interface, some " "network drivers generate a random MAC address that can change on every boot, " "and if this happens, network access would be possible even when the user has " "not manually set an address, but e.g. assigning semi-static IP addresses by " "DHCP based on the MAC address of the requesting client would obviously not " "work reliably." msgstr "" #. Tag: para #: preparing.xml:1555 #, no-c-format msgid "" "To avoid conflicts with existing officially-assigned MAC addresses, there is " "an address pool which is reserved for so-called locally administered addresses. It is defined by the value of two specific bits in the " "first byte of the address (the article MAC address in the " "English language Wikipedia gives a good explanation). In practice this means " "that e.g. any address starting with hexadecimal ca (such as ca:ff:" "ee:12:34:56) can be used as a locally administered address." msgstr "" #. Tag: para #: preparing.xml:1565 #, no-c-format msgid "" "On systems using U-Boot as system firmware, the ethernet MAC address is " "placed in the ethaddr environment variable. It can be checked " "at the U-Boot command prompt with the command printenv ethaddr and can be set with the command setenv ethaddr ca:ff:" "ee:12:34:56. After setting the value, the command saveenv makes the assignment permanent." msgstr "" #. Tag: title #: preparing.xml:1576 #, no-c-format msgid "Kernel/Initrd/Device-Tree relocation issues in U-Boot" msgstr "" #. Tag: para #: preparing.xml:1577 #, no-c-format msgid "" "On some systems with older U-Boot versions there can be problems with " "properly relocating the Linux kernel, the initial ramdisk and the device-" "tree blob in memory during the boot process. In this case, U-Boot shows the " "message Starting kernel ..., but the system freezes " "afterwards without further output. These issues have been solved with newer " "U-Boot versions from v2014.07 onwards." msgstr "" #. Tag: para #: preparing.xml:1586 #, no-c-format msgid "" "If the system has originally used a U-Boot version older than v2014.07 and " "has been upgraded to a newer version later, the problem might still occur " "even after upgrading U-Boot. Upgrading U-Boot usually does not modify the " "existing U-Boot environment variables and the fix requires an additional " "environment variable (bootm_size) to be set, which U-Boot does automatically " "only on fresh installations without existing environment data. It is " "possible to manually set bootm_size to the new U-Boot's default value by " "running the command env default bootm_size; saveenv at the U-" "Boot prompt." msgstr "" #. Tag: para #: preparing.xml:1597 #, no-c-format msgid "" "Another possibility to circumvent relocation-related problems is to run the " "command setenv fdt_high ffffffff; setenv initrd_high 0xffffffff; " "saveenv at the U-Boot prompt to completely disable the relocation of " "the initial ramdisk and the device-tree blob." msgstr "" #. Tag: title #: preparing.xml:1607 #, no-c-format msgid "Systems with UEFI firmware" msgstr "" #. Tag: para #: preparing.xml:1608 #, no-c-format msgid "" "UEFI (Unified Extensible Firmware Interface) is a new kind of " "system firmware that is used on many modern systems and is - among other " "uses - intended to replace the classic PC BIOS." msgstr "" #. Tag: para #: preparing.xml:1614 #, no-c-format msgid "" "Currently most PC systems that use UEFI also have a so-called " "Compatibility Support Module (CSM) in the firmware, which " "provides exactly the same interfaces to an operating system as a classic PC " "BIOS, so that software written for the classic PC BIOS can be used " "unchanged. Nonetheless UEFI is intended to one day completely replace the " "old PC BIOS without being fully backwards-compatible and there are already a " "lot of systems with UEFI but without CSM." msgstr "" #. Tag: para #: preparing.xml:1624 #, no-c-format msgid "" "On systems with UEFI there are a few things to take into consideration when " "installing an operating system. The way the firmware loads an operating " "system is fundamentally different between the classic BIOS (or UEFI in CSM " "mode) and native UEFI. One major difference is the way the harddisk " "partitions are recorded on the harddisk. While the classic BIOS and UEFI in " "CSM mode use a DOS partition table, native UEFI uses a different " "partitioning scheme called GUID Partition Table (GPT). On a " "single disk, for all practical purposes only one of the two can be used and " "in case of a multi-boot setup with different operating systems on one disk, " "all of them must therefore use the same type of partition table. Booting " "from a disk with GPT is only possible in native UEFI mode, but using GPT " "becomes more and more common as hard disk sizes grow, because the classic " "DOS partition table cannot address disks larger than about 2 Terabytes while " "GPT allows for far larger disks. The other major difference between BIOS (or " "UEFI in CSM mode) and native UEFI is the location where boot code is stored " "and in which format it has to be. This means that different bootloaders are " "needed for each system." msgstr "" #. Tag: para #: preparing.xml:1644 #, no-c-format msgid "" "The latter becomes important when booting &d-i; on a UEFI system with CSM " "because &d-i; checks whether it was started on a BIOS- or on a native UEFI " "system and installs the corresponding bootloader. Normally this simply works " "but there can be a problem in multi-boot environments. On some UEFI systems " "with CSM the default boot mode for removable devices can be different from " "what is actually used when booting from hard disk, so when booting the " "installer from a USB stick in a different mode from what is used when " "booting another already installed operating system from the hard disk, the " "wrong bootloader might be installed and the system might be unbootable after " "finishing the installation. When choosing the boot device from a firmware " "boot menu, some systems offer two separate choices for each device, so that " "the user can select whether booting shall happen in CSM or in native UEFI " "mode." msgstr "" #. Tag: title #: preparing.xml:1663 #, no-c-format msgid "Secure boot" msgstr "" #. Tag: para #: preparing.xml:1664 #, no-c-format msgid "" "Another UEFI-related topic is the so-called secure boot " "mechanism. Secure boot means a function of UEFI implementations that allows " "the firmware to only load and execute code that is cryptographically signed " "with certain keys and thereby blocking any (potentially malicious) boot code " "that is unsigned or signed with unknown keys. In practice the only key " "accepted by default on most UEFI systems with secure boot is a key from " "Microsoft used for signing the Windows bootloader. Debian includes a " "shim bootloader signed by Microsoft, so should work correctly " "on systems with secure boot enabled." msgstr "" #. Tag: title #: preparing.xml:1679 #, no-c-format msgid "" "Disabling the Windows fast boot/fast startup " "feature" msgstr "" #. Tag: para #: preparing.xml:1680 #, no-c-format msgid "" "Windows offers a feature (called fast boot in Windows 8, " "fast startup in Windows 10) to cut down system startup time. " "Technically, when this feature is enabled, Windows does not do a real " "shutdown and a real cold boot afterwards when ordered to shut down, but " "instead does something resembling a partial suspend to disk to reduce the " "boot time. As long as Windows is the only operating system on " "the machine, this is unproblematic, but it can result in problems and data " "loss, when you have a dual boot setup, in which another operating system " "accesses the same filesystems as Windows does. In that case the real state " "of the filesystem can be different from what Windows believes it to be after " "the boot and this could cause filesystem corruption upon " "further write accesses to the filesystem. Therefore in a dual boot setup, to " "avoid filesystem corruption the fast boot/fast " "startup feature has to be disabled within Windows." msgstr "" #. Tag: para #: preparing.xml:1697 #, no-c-format msgid "" "Furthermore, the Windows Update mechanism has (sometimes) been known to " "automatically re-enable this feature, after it has been previously disabled " "by the user. It is suggested to re-check this setting periodically." msgstr "" #. Tag: para #: preparing.xml:1702 #, no-c-format msgid "" "It may also be necessary to disable fast boot to even allow " "access to UEFI setup to choose to boot another operating system or &d-i;. On " "some UEFI systems, the firmware will reduce boot time by not " "initialising the keyboard controller or USB hardware; in these cases, it is " "necessary to boot into Windows and disable this feature to allow for a " "change of boot order." msgstr "" #. Tag: title #: preparing.xml:1714 #, no-c-format msgid "Hardware Issues to Watch Out For" msgstr "需要留意的硬體問題" #. Tag: title #: preparing.xml:1717 #, no-c-format msgid "USB BIOS support and keyboards" msgstr "USB BIOS 支援與鍵盤" #. Tag: para #: preparing.xml:1718 #, fuzzy, no-c-format #| msgid "" #| "If you have no AT-style keyboard and only a USB model, you may need to " #| "enable legacy AT keyboard emulation in your BIOS setup. Only do this if " #| "the installation system fails to use your keyboard in USB mode. " #| "Conversely, for some systems (especially laptops) you may need to disable " #| "legacy USB support if your keyboard does not respond. Consult your main " #| "board manual and look in the BIOS for Legacy keyboard emulation or USB keyboard support options." msgid "" "If you have no PS/2-style keyboard, but only a USB model, on some very old " "PCs you may need to enable legacy keyboard emulation in your BIOS setup to " "be able to use your keyboard in the bootloader menu, but this is not an " "issue for modern systems. If your keyboard does not work in the bootloader " "menu, consult your mainboard manual and look in the BIOS for Legacy " "keyboard emulation or USB keyboard support options." msgstr "" "倘若您沒有 AT 鍵盤，只有一個 USB 的鍵盤的話，您需要在 BIOS 設定裡開啟老式 AT " "鍵盤模擬功能。這動作只在安裝系統使用 USB 模式失敗的情況下執行。 反之，對其他" "系統 (特別是筆記型電腦) 也許您的鍵盤沒有回應，這需要停用老式 USB 支援。請查閱" "您的主機板手冊並查看 BIOS 中的 Legacy keyboard emulation 或 " "USB keyboard support 選項。" #, fuzzy #~ msgid "256 megabytes" #~ msgstr "24 MB" #, fuzzy #~ msgid "512 megabytes" #~ msgstr "128 MB" #~ msgid "4 gigabytes" #~ msgstr "4 GB" #, fuzzy #~| msgid "1 gigabyte" #~ msgid "1 gigabytes" #~ msgstr "1 GB" #, fuzzy #~ msgid "2 gigabytes" #~ msgstr "1 GB" #, fuzzy #~| msgid "1 gigabyte" #~ msgid "10 gigabytes" #~ msgstr "1 GB" #~ msgid "Linux for SPARC Processors FAQ" #~ msgstr "Linux for SPARC Processors 常見問答集" #, fuzzy #~ msgid "Any OldWorld or NewWorld PowerPC can serve well as a desktop system." #~ msgstr "" #~ "任何一台 OldWorld 或 NewWorld PowerPC 都可以用來作為不錯的桌面系統。要是作" #~ "為伺服器的話，建議至少要 132 Mhz 的機器才行。" #~ msgid "FIXME: write about HP-UX disks?" #~ msgstr "FIXME: write about HP-UX disks?" #, fuzzy #~| msgid "" #~| "If you are going to install more than one operating system on the same " #~| "machine, you should install all other system(s) before proceeding with " #~| "&debian; installation. Windows and other OS installations may destroy " #~| "your ability to start &debian;, or encourage you to reformat non-native " #~| "partitions." #~ msgid "" #~ "If you are going to install more than one operating system on the same " #~ "machine, you should install all other system(s) before proceeding with " #~ "the &debian; installation. Windows and other OS installations may destroy " #~ "your ability to start &debian;, or encourage you to reformat non-native " #~ "partitions." #~ msgstr "" #~ "倘若您打算在同一台機器上安裝多個作業系統，您應當在安裝 &debian; 之前，先把" #~ "所有其它系統都裝好。Windows 和其它作業系統的安裝過程可能會讓您無法開機 " #~ "&debian;，也可能會慫恿您重新格式化不屬於它們自己的分割區。" #~ msgid "" #~ "You can recover from these actions or avoid them, but installing the " #~ "native system first saves you trouble." #~ msgstr "" #~ "儘管您可以在這些操作之後再恢復回來，也可以避免它們，但是首先安裝本地系統就" #~ "能夠幫您免除這些煩惱。" #, fuzzy #~| msgid "" #~| "In order for OpenFirmware to automatically boot &debian-gnu; the Linux " #~| "partitions should appear before all other partitions on the disk, " #~| "especially MacOS boot partitions. This should be kept in mind when pre-" #~| "partitioning; you should create a Linux placeholder partition to come " #~| "before the other bootable partitions on the disk. " #~| "(The small partitions dedicated to Apple disk drivers are not bootable.) " #~| "You can delete the placeholder with the Linux partition tools later " #~| "during the actual install, and replace it with Linux partitions." #~ msgid "" #~ "In order for OpenFirmware to automatically boot &debian-gnu; the &arch-" #~ "parttype; partitions should appear before all other partitions on the " #~ "disk, especially Mac OS X boot partitions. This should be kept in mind " #~ "when pre-partitioning; you should create a &arch-parttype; placeholder " #~ "partition to come before the other bootable " #~ "partitions on the disk. (The small partitions dedicated to Apple disk " #~ "drivers are not bootable.) You can delete the placeholder with the " #~ "&debian; partition tools later during the actual install, and replace it " #~ "with &arch-parttype; partitions." #~ msgstr "" #~ "為了能讓 OpemFirmware 自動開機，&debian-gnu; Linux 分割區必須被安置在其它" #~ "分割區之前，特別是 MacOS 的開機分割區。在分割之前時，這一點您必須牢記在" #~ "心。也就是說，您必須在其它可開機分割區之前為 Linux 預" #~ "留一個分割區。(專門留給 Apple 的硬碟驅動程式的那些小分割區並不是可開機" #~ "的。) 您可以在真正安裝時，用 Linux 的分割區工具來刪除當初預留的分割區，再" #~ "用 Linux 的分割區取而代之。" #~ msgid "Partitioning from SunOS" #~ msgstr "SunOS 下的分割" #, fuzzy #~ msgid "" #~ "It's perfectly fine to partition from SunOS; in fact, if you intend to " #~ "run both SunOS and &debian; on the same machine, it is recommended that " #~ "you partition using SunOS prior to installing &debian;. The Linux kernel " #~ "understands Sun disk labels, so there are no problems there. SILO " #~ "supports booting Linux and SunOS from any of EXT2 (Linux), UFS (SunOS), " #~ "romfs or iso9660 (CDROM) partitions." #~ msgstr "" #~ "從 SunOS 分割區是非常好的。事實上，如果您傾向在同一台電腦上使用 SunOS 和 " #~ "&debian;，我們建議在安裝 &debian; 之前使用 SunOS 進行分割區。Linux 核心可" #~ "以識別 Sun 的磁碟標籤，因此不會有任何問題。只需要在開機磁碟的首 1GB 範圍裡" #~ "面賦予 &debian; 根區留足夠空間即可。如果比設定根分割區的位置更簡單，您也可" #~ "以將核心映像放在 UFS 分割區裡。SILO 支援從 EXT2 (Linux)、UFS (SunOS)、" #~ "romfs 和 iso9660 (CDROM) 分割區開機 Linux 和 SunOS。" #~ msgid "Partitioning from Linux or another OS" #~ msgstr "Linux 或其他 OS 下的分割" #~ msgid "" #~ "Whatever system you are using to partition, make sure you create a " #~ "Sun disk label on your boot disk. This is the only kind of " #~ "partition scheme that the OpenBoot PROM understands, and so it's the only " #~ "scheme from which you can boot. In fdisk, the " #~ "s key is used to create Sun disk labels. You only need " #~ "to do this on drives that do not already have a Sun disk label. If you " #~ "are using a drive that was previously formatted using a PC (or other " #~ "architecture) you must create a new disk label, or problems with the disk " #~ "geometry will most likely occur." #~ msgstr "" #~ "無論使用什麼系統分割區，您要確保在您的開機磁碟上建立 Sun disk " #~ "label 標籤。這是 OpenBoot PROM 能識別的唯一分割區方案，也是您唯一" #~ "可以開機的方案。在 fdisk 裡面，s 鍵用" #~ "於建立 Sun 磁碟標籤。您只須在沒有 Sun 磁碟標籤的磁碟上執行這個動作。如果您" #~ "使用了一個被 PC (或其他架構)格式化過的磁碟，您必須建立新的磁碟標籤，不然會" #~ "有磁碟排列問題出現。" #~ msgid "" #~ "You will probably be using SILO as your boot loader " #~ "(the small program which runs the operating system kernel). " #~ "SILO has certain requirements for partition sizes and " #~ "location; see ." #~ msgstr "" #~ "您也許使用 SILO 作為您的 boot loader(執行作業系統核心的" #~ "小程式)。SILO 對分割區大小和位置有明確的要求，請參閱 " #~ "。" #, fuzzy #~| msgid "MacOS/OSX Partitioning" #~ msgid "Mac OS X Partitioning" #~ msgstr "MacOS/OSX 下的分割" #, fuzzy #~| msgid "" #~| "The Apple Drive Setup application can be " #~| "found in the Utilities folder on the MacOS CD. It " #~| "will not adjust existing partitions; it is limited to partitioning the " #~| "entire disk at once. The disk driver partitions don't show up in " #~| "Drive Setup." #~ msgid "" #~ "The Disk Utility application can be found " #~ "under the Utilities menu in Mac OS X Installer. It " #~ "will not adjust existing partitions; it is limited to partitioning the " #~ "entire disk at once." #~ msgstr "" #~ "Apple Drive Setup 程式可以在 MacOS CD 的 " #~ "Utilities 目錄裡面找到。它並不能調整已經存在的分割" #~ "區，而且僅限於一次性完成整個磁碟的分割區。硬碟分割區並不會出現在 " #~ "Drive Setup 中。" #~ msgid "" #~ "Remember to create a placeholder partition for GNU/Linux, preferably " #~ "positioned first in the disk layout. it doesn't matter what type it is, " #~ "it will be deleted and replaced later inside the &debian-gnu; installer." #~ msgstr "" #~ "記得要建立一個給 GNU/Linux 佔用的分割區，最好是磁碟分割中的第一個分割區。" #~ "它的類型無關緊要，在後面的 &debian-gnu; 安裝程式中，它會被刪除並替換。" #, fuzzy #~| msgid "" #~| "GNU/Linux is unable to access information on UFS partitions, but does " #~| "support HFS+ (aka MacOS Extended) partitions. OS X requires one of these " #~| "two types for its boot partition. MacOS 9 can be installed on either HFS " #~| "(aka MacOS Standard) or HFS+. To share information between the MacOS and " #~| "GNU/Linux systems, an exchange partition is handy. HFS, HFS+ and MS-DOS " #~| "FAT partitions are supported by both MacOS and Linux." #~ msgid "" #~ "GNU/Linux is unable to access information on UFS partitions, but can " #~ "access HFS+ (aka MacOS Extended) partitions. OS X requires one of these " #~ "two types for its boot partition. MacOS 9 can be installed on either HFS " #~ "(aka MacOS Standard) or HFS+. To share information between the Mac OS X " #~ "and GNU/Linux systems, an exchange partition is handy. HFS, HFS+ and MS-" #~ "DOS FAT file systems are supported by MacOS 9, Mac OS X and GNU/Linux." #~ msgstr "" #~ "GNU/Linux 不能讀取 UFS 分割區但是支援 HFS+ 分割區 (又稱 MacOS Extended)。" #~ "OS X 要求使用這兩個分割區類型之一作為開機分割區。MacOS 9 能安裝到 HFS (又" #~ "稱 MacOS Standard) 或 HFS+ 上。建一個交換資料分割區就可以很方便地在 MacOS " #~ "和 GNU/Linux 系統間共享資訊。HFS 和 MS-DOS FAT 分割區都能被 MacOS 和 " #~ "Linux 支援。" #~ msgid "Invoking OpenFirmware" #~ msgstr "使用 OpenFireware" #~ msgid "" #~ "There is normally no need to set up the BIOS (called OpenFirmware) on " #~ "&arch-title; systems. PReP and CHRP are equipped with OpenFirmware, but " #~ "unfortunately, the means you use to invoke it vary from manufacturer to " #~ "manufacturer. You'll have to consult the hardware documentation which " #~ "came with your machine." #~ msgstr "" #~ "通常在 &arch-title; 系統上不需要去設置 BIOS (稱為 OpenFirmware)。 " #~ "OpenFirmware 常常配備 PReP 與 CHRP，但這也意味著依不同廠商而不同。您必須參" #~ "閱電腦手冊中相關的硬體文件。" #, fuzzy #~| msgid "" #~| "On &arch-title; Macintoshes, you invoke OpenFirmware with " #~| "Command option O F while booting. Generally it will " #~| "check for these keystrokes after the chime, but the exact timing varies " #~| "from model to model. See for more hints." #~ msgid "" #~ "On &arch-title; Macintoshes, you invoke OpenFirmware with " #~ "Command (cloverleaf/Apple)Optionof while booting. " #~ "Generally it will check for these keystrokes after the chime, but the " #~ "exact timing varies from model to model. See for more hints." #~ msgstr "" #~ "在 &arch-title; 的 Macintoshe 機器上，開機時透過按下 " #~ "Command option O F 以啟動 OpenFirmware。一般情況下，它" #~ "會按時鐘順序檢驗按鍵，但也會與不同的型號有關。請參閱 取得更多提示。" #~ msgid "" #~ "The OpenFirmware prompt looks like this: \n" #~ "ok\n" #~ "0 >\n" #~ " Note that on older model &arch-title; Macs, " #~ "the default and sometimes hardwired I/O for OpenFirmware user interaction " #~ "is through the serial (modem) port. If you invoke OpenFirmware on one of " #~ "these machines, you will just see a black screen. In that case, a " #~ "terminal program running on another computer, connected to the modem " #~ "port, is needed to interact with OpenFirmware." #~ msgstr "" #~ "OpenFirmware 的提示看起來像：\n" #~ "ok\n" #~ "0 >\n" #~ "注意舊型號的 &arch-title; Mac 機器，" #~ "OpenFirmware 與使用者互動所用的預設實體 I/O 是透過序列 (調變解調器) 埠進行" #~ "的。如果您在這樣的機器上使用 OperFirmware，您只會看到黑色背景。在這種情況" #~ "下，需要通過調變解調器連接埠連接到另外一台電腦上的終端程式來與 " #~ "OpenFirmware 交互。" #, fuzzy #~ msgid "" #~ "The OpenFirmware on OldWorld Beige G3 machines, OF versions 2.0f1 and " #~ "2.4, is broken. These machines will most likely not be able to boot from " #~ "the hard drive unless the firmware is patched. A firmware patch is " #~ "included in the System Disk 2.3.1 utility, " #~ "available from Apple at . After " #~ "unpacking the utility in MacOS, and launching it, select the " #~ "Save button to have the firmware patches installed " #~ "to nvram." #~ msgstr "" #~ "運行在 OldWorld Beige G3 機器上的 OF 版本 2.0f1 和 2.4 的 OpenFirmware 是" #~ "損壞的。這些機器如果沒有使用韌體補丁，就不能夠從硬碟開機。韌體的補丁包括 " #~ "位於 Apple 的 System Disk " #~ "2.3.1 工具。在 MacOS 上解開並執行，選擇儲存按鈕使韌體補丁安" #~ "裝到 nvram。" #~ msgid "Invoking OpenBoot" #~ msgstr "使用 OpenBoot" #, fuzzy #~ msgid "" #~ "OpenBoot provides the basic functions needed to boot the &arch-title; " #~ "architecture. This is rather similar in function to the BIOS in the x86 " #~ "architecture, although much nicer. The Sun boot PROMs have a built-in " #~ "forth interpreter which lets you do quite a number of things with your " #~ "machine, such as diagnostics and simple scripts." #~ msgstr "" #~ "OpenBoot 提供了開機 &arch-title; 所需的基本功能。雖然做得比 x86 架構 BIOS " #~ "更好一些，但功能是非常接近的。Sun 的開機 PROM 內建了 forth 直譯器，可讓您" #~ "對電腦做很多事情如診斷，簡單腳本，等等。" #~ msgid "" #~ "To get to the boot prompt you need to hold down the Stop " #~ "key (on older type 4 keyboards, use the L1 key, if you " #~ "have a PC keyboard adapter, use the Break key) and press " #~ "the A key. The boot PROM will give you a prompt, either " #~ "ok or >. It is preferred " #~ "to have the ok prompt. So if you get the old style " #~ "prompt, hit the n key to get the new style prompt." #~ msgstr "" #~ "為了得到開機提示符號，您需要按住 Stop 鍵 (在老式的 type " #~ "4 鍵盤上，使用 L1 鍵，如果您有一個 PC 鍵盤適配器，使用 " #~ "Break 鍵) 並按下 A 鍵。啟動 PROM 將出現" #~ "提示符號，可能是 ok 或者 >。優先使用 ok 提示符號。如果您得到的是舊" #~ "風格的提示符號，按下 n 鍵得到新風格的提示符號。" #~ msgid "" #~ "If you are using a serial console, send a break to the machine. With " #~ "Minicom, use Ctrl-A F, with cu, hit Enter, then type %~break. Consult the " #~ "documentation of your terminal emulator if you are using a different " #~ "program." #~ msgstr "" #~ "如果您使用的是序列控制台，發送 break 到機器。在 Minicom 下，使用 " #~ "Ctrl-A F，在 cu 下，按下 Enter，然後鍵" #~ "入 %~break。如果您使用其他的程式，查看終端模擬器相" #~ "關的文件。" #, fuzzy #~ msgid "" #~ "You can use OpenBoot to boot from specific devices, and also to change " #~ "your default boot device. However, you need to know some details about " #~ "how OpenBoot names devices; it's considerably different from Linux device " #~ "naming, described in . Also, the command " #~ "will vary a bit, depending on what version of OpenBoot you have. More " #~ "information about OpenBoot can be found in the Sun OpenBoot Reference." #~ msgstr "" #~ "您可以使用 OpenBoot 指定開機設備，也可以能改變預設開機設備。但您需要瞭解 " #~ "OpenBoot 如何命名設備的細節，它與 Linux 命名方法有很大差別，說明在 。另外，該指令會依 OpenBoot 的版本不同而略有區" #~ "別。更多關於 OpenBoot 的資料請參閱 Sun " #~ "OpenBoot Reference。" #~ msgid "" #~ "To boot from a specific device, use the command boot " #~ "device. You can set this behavior " #~ "as the default using the setenv command. However, " #~ "the name of the variable to set changed between OpenBoot revisions. In " #~ "OpenBoot 1.x, use the command setenv boot-from " #~ "device. In later revisions of " #~ "OpenBoot, use the command setenv boot-device " #~ "device. Note, this is also " #~ "configurable using the eeprom command on Solaris, or " #~ "modifying the appropriate files in /proc/openprom/options/, for example under Linux: \n" #~ "# echo disk1:1 > /proc/openprom/options/boot-device\n" #~ " and under Solaris:" #~ msgstr "" #~ "要從指定的設備開機，請使用 boot device 指令。您可以透過 setenv 指" #~ "令將它設為預設方式。但變數的名稱在不同版本會有所改變。在 OpenBoot 1.x 中，" #~ "請使用 setenv boot-from device 指令。在稍後的 OpenBoot 修訂版本中，請使用 setenv " #~ "boot-device device 指令。注意，它也" #~ "可以透過使用 Solaris 上的 eeprom 指令或者修改 " #~ "/proc/openprom/options/ 中相應的檔案來進行設定，例" #~ "如，Linux 下使用： \n" #~ "# echo disk1:1 > /proc/openprom/options/boot-device\n" #~ " 或在 Solaris下執行：" #~ msgid "eeprom boot-device=disk1:1" #~ msgstr "eeprom boot-device=disk1:1" #, fuzzy #~ msgid "" #~ "Typically, with newer revisions, you can use OpenBoot devices such as " #~ "floppy, cdrom, net, " #~ "disk, or disk2. These have the obvious " #~ "meanings; the net device is for booting from the network. " #~ "Additionally, the device name can specify a particular partition of a " #~ "disk, such as disk2:a to boot disk2, first partition. Full " #~ "OpenBoot device names have the form: \n" #~ "driver-name@\n" #~ "unit-address:\n" #~ "device-arguments\n" #~ " In older revisions of OpenBoot, device naming " #~ "is a bit different: the floppy device is called /fd, and " #~ "SCSI disk devices are of the form sd(controller, disk-target-id, " #~ "disk-lun). The command show-" #~ "devs in newer OpenBoot revisions is useful for viewing the " #~ "currently configured devices. For full information, whatever your " #~ "revision, see the Sun OpenBoot Reference." #~ msgstr "" #~ "一般來說，在較新的修訂版中，您可以使用 OpenBoot 設備，如 floppy、cdrom、net、disk 或 " #~ "disk2。這些是顯而易見的，net 即指從網路開" #~ "機。另外，設備名可以明確指定磁碟分割區，如 disk2:a 將開機磁" #~ "碟 disk2 的第一個分割區。完整的 OpenBoot 設備命名形式為 " #~ "\n" #~ "driver-name@\n" #~ "unit-address:\n" #~ "device-arguments\n" #~ "。 在舊版的 OpenBoot 中，設備命名方式有些不同：" #~ "軟碟設備稱為 /fd，SCSI 磁碟形式是 sd " #~ "(controller, disk-target-id, disk-lun)。指令 " #~ "show-devs 在新版的 OpenBoot 中用於查看目前設定好的" #~ "設備。對於完整的資料，和您使用的版本，請參閱 Sun OpenBoot Reference。" #, fuzzy #~ msgid "128 megabytes" #~ msgstr "128 MB" #~ msgid "1 gigabyte" #~ msgstr "1 GB" #~ msgid "64 megabytes" #~ msgstr "64 MB" #~ msgid "" #~ "If you are planning to install both MacOS 9 and OS X, it is best to " #~ "create separate partitions for OS 9 and OS X. If they are installed on " #~ "the same partition, Startup Disk (and reboot) " #~ "must be used to select between the two; the choice between the two " #~ "systems can't be made at boot time. With separate partitions, separate " #~ "options for OS 9 and OS X will appear when holding the option key at boot time, and separate options can be installed in the " #~ "yaboot boot menu as well. Also, Startup Disk " #~ "will de-bless all other mountable partitions, which can affect GNU/Linux " #~ "booting. Both OS 9 and OS X partitions will be accessible from either OS " #~ "9 or OS X." #~ msgstr "" #~ "如果您計劃同時安裝 MacOS 9 與 OS X，最好為 OS 9 和 OS X 建立不同的分割區。" #~ "如果將它們安裝在同一分割區，就必須使用 Startup Disk (並重啟) 來選擇它們兩個，而在開機時是無法對兩個作業系統進行選" #~ "擇的。使用不同的分割區時，如果在開機時按住 option 鍵就可" #~ "以顯示出 OS 9 和 OS X 兩個不同的選項，而且這些分開的選項也可以被安裝到 " #~ "yaboot 開機選單裡面。還有，Startup Disk 將無法" #~ "保證其他可掛載的分割區的可靠性，這可能會影響 GNU/Linux 的開機。從 OS 9 和 " #~ "OS X 中都能讀取OS 9 和 OS X 分割區。" #~ msgid "" #~ "Set up boot tapes/floppies/USB sticks, or place boot files (most &debian; " #~ "CD users can boot from one of the CDs)." #~ msgstr "" #~ "設置從開機磁帶、軟碟、USB 隨身碟，或者其它存有系統開機檔案的設備 (對於大多" #~ "數 &debian; 安裝光碟的使用者來說，可以直接用這些光碟開機)﹔" #~ msgid "Linux Hardware Compatibility HOWTO" #~ msgstr "Linux 硬體相容指南" #~ msgid "Monitor" #~ msgstr "顯示器" #~ msgid "Resolutions supported." #~ msgstr "支援的解析度。" #~ msgid "Horizontal refresh rate." #~ msgstr "水平掃瞄頻率。" #~ msgid "Vertical refresh rate." #~ msgstr "垂直掃瞄頻率。" #~ msgid "Color depth (number of colors) supported." #~ msgstr "支援的顏色深度(顏色數)" #~ msgid "Screen size." #~ msgstr "螢幕大小。" #~ msgid "Mouse" #~ msgstr "滑鼠" #~ msgid "Type: serial, PS/2, or USB." #~ msgstr "類型：序列、PS/2 或 USB。" #~ msgid "Port." #~ msgstr "埠。" #~ msgid "Manufacturer." #~ msgstr "製造商。" #~ msgid "Number of buttons." #~ msgstr "按鍵數。" #~ msgid "Printing resolutions supported." #~ msgstr "支援的印表機解析度。" #~ msgid "Video RAM available." #~ msgstr "可用顯示記憶體" #~ msgid "" #~ "Resolutions and color depths supported (these should be checked against " #~ "your monitor's capabilities)." #~ msgstr "支援的解析度和顏色數 (還需檢驗您顯示器的能力)。" #~ msgid "" #~ "In particular, &arch-kernel; usually cannot run hardware that requires a " #~ "running version of Windows to work." #~ msgstr "" #~ "特別的是，&arch-kernel; 通常不能驅動那些需要在某些 Windows 版本上才能運作" #~ "的硬體。" #~ msgid "" #~ "Although some Windows-specific hardware can be made to run on Linux, " #~ "doing so usually requires extra effort. In addition, Linux drivers for " #~ "Windows-specific hardware are usually specific to one Linux kernel. " #~ "Therefore, they can quickly become obsolete." #~ msgstr "" #~ "雖然可以讓某些 Windows 規格的硬體運行在 Linux 上，但這通常需要額外的工作。" #~ "另外，對應 Windows 規格硬體的 Linux 驅動程式常指定在某一特定版本的 Linux " #~ "核心上。 因此，它們很快就會被廢棄。" #~ msgid "" #~ "So called win-modems are the most common type of this hardware. However, " #~ "printers and other equipment may also be Windows-specific." #~ msgstr "" #~ "所謂的 win-modem 設備是這類硬體的典型。但印表機和其他設備也有是 Windows 規" #~ "格的。" #~ msgid "You can check hardware compatibility by:" #~ msgstr "您可以透過以下方式檢驗硬體相容性：" #~ msgid "Checking manufacturers' web sites for new drivers." #~ msgstr "檢查製造商的網站來得到新的驅動程式。" #~ msgid "" #~ "Looking at web sites or manuals for information about emulation. Lesser " #~ "known brands can sometimes use the drivers or settings for better-known " #~ "ones." #~ msgstr "" #~ "查看網站或者手冊關於模擬的資料。不常見的品牌有時可以使用常見品牌設備的驅動" #~ "程式或設定。" #~ msgid "" #~ "Checking hardware compatibility lists for &arch-kernel; on web sites " #~ "dedicated to your architecture." #~ msgstr "檢查您電腦架構的 &arch-kernel; 相容性列表網站。" #~ msgid "Searching the Internet for other users' experiences." #~ msgstr "搜索網際網路尋找其他使用者的經驗。" #~ msgid "" #~ "If your computer has more than one hard disk, you may want to dedicate " #~ "one of the hard disks completely to &debian;. If so, you don't need to " #~ "partition that disk before booting the installation system; the " #~ "installer's included partitioning program can handle the job nicely." #~ msgstr "" #~ "如果您的電腦配有不只一塊硬碟，您或許可以考慮把其中一塊硬碟專門分配給 " #~ "&debian; 使用。這樣的話，您就不用在開機安裝系統前再對那塊硬碟進行分割區" #~ "了，安裝程式內建的分割區程式會漂亮地完成這個任務。" #, fuzzy #~ msgid "" #~ "If your machine has only one hard disk, and you would like to completely " #~ "replace the current operating system with &debian-gnu;, you also can wait " #~ "to partition as part of the installation process (), after you have booted the installation system. However " #~ "this only works if you plan to boot the installer system from tapes, CD-" #~ "ROM or files on a connected machine. Consider: if you boot from files " #~ "placed on the hard disk, and then partition that same hard disk within " #~ "the installation system, thus erasing the boot files, you'd better hope " #~ "the installation is successful the first time around. At the least in " #~ "this case, you should have some alternate means of reviving your machine " #~ "like the original system's installation tapes or CDs." #~ msgstr "" #~ "若是您的機器只有一顆硬碟，而且您願意把原來的作業系統全部替換成 &debian-" #~ "gnu;，那麼您可以在開機安裝系統後，等待安裝時再進行分割 ()。 但是，只有當您使用儲存於磁帶、光碟機或者網際網路上的機器" #~ "的安裝系統，並從它們開機安裝程式時，前述才適用於您的情形。試想一下：假如您" #~ "用放在硬碟上的檔案開機，再在安裝系統中對同一顆硬碟進行分割，這會清除那些開" #~ "機檔案，這時您恐怕只能祈求上蒼保佑第一次就安裝成功。在這種情況下，若要讓您" #~ "的機器恢復正常，至少您還可以有幾個辦法可選，例如原先系統的安裝磁帶或光碟。" #~ msgid "" #~ "If your machine already has multiple partitions, and enough space can be " #~ "provided by deleting and replacing one or more of them, then you too can " #~ "wait and use the &debian; installer's partitioning program. You should " #~ "still read through the material below, because there may be special " #~ "circumstances like the order of the existing partitions within the " #~ "partition map, that force you to partition before installing anyway." #~ msgstr "" #~ "倘若您的機器已經有多個分割區，並且透過刪除或替換它們其中的一個或多個就能為" #~ "安裝程式提供足夠的空間，那麼您一樣也可以把分割區操作延後，到安裝時再使用 " #~ "&debian; 安裝程式內建的分割工具。不過，您還是應該繼續讀完下面的文件，因為" #~ "可能會有些特殊情形。例如，分割表中現有分割區的順序問題，這也許會令您不得不" #~ "在安裝前先切割好分割區。" #~ msgid "" #~ "If your machine has a FAT or NTFS filesystem, as used by DOS and Windows, " #~ "you can wait and use &debian; installer's partitioning program to resize " #~ "the filesystem." #~ msgstr "" #~ "如果您的電腦上有被 DOS 和 Windows 使用的 FAT 或 NTFS 檔案系統，您可以等到" #~ "用 &debian; 安裝程式中的分割工具來重新調整檔案系統的大小。" #~ msgid "" #~ "If none of the above apply, you'll need to partition your hard disk " #~ "before starting the installation to create partitionable space for " #~ "&debian;. If some of the partitions will be owned by other operating " #~ "systems, you should create those partitions using native operating system " #~ "partitioning programs. We recommend that you do not " #~ "attempt to create partitions for &debian-gnu; using another operating " #~ "system's tools. Instead, you should just create the native operating " #~ "system's partitions you will want to retain." #~ msgstr "" #~ "如果您的情況不屬於上面任何一種，那麼您需要在開始安裝之前，事先為 &debian; " #~ "騰出可用於分割區的空間。要是有分割區是為其它作業系統準備的，您最好用該作業" #~ "系統自己的分割軟體來建立這些分割區。我們建議您不要用" #~ "其它作業系統裡的工具為 &debian; 建立 Linux 分割區。也就是說，您應當僅建立" #~ "要保留的作業系統自身的分割區。" #~ msgid "" #~ "If you currently have one hard disk with one partition (a common setup " #~ "for desktop computers), and you want to multi-boot the native operating " #~ "system and &debian;, you will need to:" #~ msgstr "" #~ "如果您現在有一塊硬碟，這塊硬碟上僅有一個分割區 (這是桌面電腦的常見設定)，" #~ "同時您希望能多重開機原有的作業系統和 &debian;，那麼您就需要：" #~ msgid "Back up everything on the computer." #~ msgstr "備份電腦裡所有的資料。" #~ msgid "" #~ "Boot from the native operating system installer media such as CD-ROM or " #~ "tapes. When booting from a MacOS CD, hold the " #~ "c key while booting to force the CD to become the active " #~ "MacOS system." #~ msgstr "" #~ "從原有作業系統的安裝媒介(如光碟和磁帶)開機。當從 " #~ "MacOS CD 開機時，按住 c 鍵不放，這樣就能以光碟開機作為目" #~ "前的 MacOS 系統。" #~ msgid "" #~ "Use the native partitioning tools to create native system partition(s). " #~ "Leave either a place holder partition or free space for &debian-gnu;." #~ msgstr "" #~ "使用原有系統裡的分割區工具來建立屬於原來系統的分割區。為 &debian-gnu; 預留" #~ "一個分割區，或者騰出一塊空間。" #~ msgid "Install the native operating system on its new partition." #~ msgstr "把原有作業系統安裝到屬於它的新分割區上。" #~ msgid "" #~ "Boot back into the native system to verify everything's OK, and to " #~ "download the &debian; installer boot files." #~ msgstr "" #~ "開機到原有作業系統，以確保一切正常，再下載 &debian; 安裝程式的開機檔案。" #~ msgid "Boot the &debian; installer to continue installing &debian;." #~ msgstr "啟動 &debian; 安裝程式，並繼續安裝 &debian;。" #~ msgid "Partitioning From DOS or Windows" #~ msgstr "DOS 或 Windows 下的分割" #~ msgid "" #~ "If you are manipulating existing FAT or NTFS partitions, it is " #~ "recommended that you either use the scheme below or native Windows or DOS " #~ "tools. Otherwise, it is not really necessary to partition from DOS or " #~ "Windows; the &debian; partitioning tools will generally do a better job." #~ msgstr "" #~ "如果您想在已有的 FAT 或 NTFS 分割區上動手，那麼建議您或者按照下面介紹的方" #~ "案操作，或者使用 Windows 或 DOS 自己的工具軟體。否則的話，真的沒必要從 " #~ "DOS 或者 Windows 分割，一般來說，&debian; 的分割軟體會做得更好。" #, fuzzy #~ msgid "" #~ "But if you have a large IDE disk, and are not using LBA addressing, " #~ "overlay drivers (sometimes provided by hard disk manufacturers), or a new " #~ "(post 1998) BIOS that supports large disk access extensions, then you " #~ "must locate your &debian; boot partition carefully. In this case, you " #~ "will have to put the boot partition into the first 1024 cylinders of your " #~ "hard disk (usually around 524 megabytes, without BIOS translation). This " #~ "may require that you move an existing FAT or NTFS partition." #~ msgstr "" #~ "但是，如果您有一顆 IDE 介面的大硬碟，而且使用的既不是 LBA 定址或 overlay " #~ "驅動程式 (有時候硬碟廠商會提供這種驅動)，也沒用新款 (1998 年以後) 支援大硬" #~ "碟追蹤擴展的 BIOS，那麼您必須小心地劃分 &debian; 的開機 (boot) 分割區。在" #~ "這種情形下，您一定要把開機分割區分在硬碟開始的前 1024 磁柱之內 (BIOS 不換" #~ "算的話，大約 524 MB)。為此，您可能需要移動硬碟上的 FAT 或 NTFS 分割區。" #~ msgid "Lossless Repartitioning When Starting From DOS, Win-32 or OS/2" #~ msgstr "在 DOS、Win-32 或者 OS/2 下的無害分割" #, fuzzy #~ msgid "" #~ "One of the most common installations is onto a system that already " #~ "contains DOS (including Windows 3.1), Win32 (such as Windows 95, 98, Me, " #~ "NT, 2000, XP, 2003, Vista, 7), or OS/2, and it is desired to put &debian; " #~ "onto the same disk without destroying the previous system. Note that the " #~ "installer supports resizing of FAT and NTFS filesystems as used by DOS " #~ "and Windows. Simply start the installer and when you get to the " #~ "partitioning step, select the option for " #~ "Manual partitioning, select the " #~ "partition to resize, and specify its new size. So in most cases you " #~ "should not need to use the method described below." #~ msgstr "" #~ "各常見的安裝中，其中有一種就是希望在已經安裝有 DOS (含 Windows 3.1)、 " #~ "Win32 (如 Windows 95、98、Me、NT、2000、XP、2003、Vista、7) 或者 OS/2 的系" #~ "統上加裝 &debian; 到同一顆硬碟的同時，還保留原有系統。注意，安裝程式支援重" #~ "新設定被 DOS 和 Windows 使用的 FAT 和 NTFS 檔案系統的容量大小。您只需開機" #~ "安裝程式，選擇 手動修改分割區表 " #~ " 選項，並選擇需要調整大小的分割區，指定新的大小。在多數情況下" #~ "您毋須使用下面說明的方法。" #~ msgid "" #~ "Before going any further, you should have decided how you will be " #~ "dividing up the disk. The method in this section will only split a " #~ "partition into two pieces. One will contain the original OS and the other " #~ "will be used for &debian;. During the installation of &debian;, you will " #~ "be given the opportunity to use the &debian; portion of the disk as you " #~ "see fit, i.e., as swap or as a file system." #~ msgstr "" #~ "在您繼續之前，您應該先想好如何分割硬碟。本節所述的方法只會把一個分割區一分" #~ "為二。分出來的其中一塊放至原來的作業系統，而另一塊則歸 &debian; 使用。在 " #~ "&debian; 的安裝過程中，您會有機會把您認為合適的那部分硬碟歸為 &debian; 使" #~ "用。例如，用作置換分割區或者放置檔案系統。" #~ msgid "" #~ "The idea is to move all the data on the partition to the beginning, " #~ "before changing the partition information, so that nothing will be lost. " #~ "It is important that you do as little as possible between the data " #~ "movement and repartitioning to minimize the chance of a file being " #~ "written near the end of the partition as this will decrease the amount of " #~ "space you can take from the partition." #~ msgstr "" #~ "辦法就是在更改分割區資料之前，把這個分割區中的所有的資料移到分割區的前面部" #~ "分，這樣資料就會分毫無損。有一點很重要，即在移動資料之後，和重新分割區之前" #~ "這段時間內，盡量不要往分割區的後端寫入資料。否則就會減少從能該分割區分割出" #~ "去的空間大小。" #, fuzzy #~| msgid "" #~| "The first thing needed is a copy of fips which is " #~| "available in the tools/ directory on your nearest " #~| "Debian mirror. Unzip the archive and copy the files RESTORRB." #~| "EXE, FIPS.EXE and ERRORS.TXT to a bootable floppy. A bootable floppy can be created using " #~| "the command sys a: under DOS. fips comes with very good documentation which you may want to read. " #~| "You will definitely need to read the documentation if you use a disk " #~| "compression driver or a disk manager. Create the disk and read the " #~| "documentation before you defragment the disk." #~ msgid "" #~ "The first thing needed is a copy of fips. Unzip the " #~ "archive and copy the files RESTORRB.EXE, " #~ "FIPS.EXE and ERRORS.TXT to a " #~ "bootable floppy. A bootable floppy can be created using the command " #~ "sys a: under DOS. fips comes with " #~ "very good documentation which you may want to read. You will definitely " #~ "need to read the documentation if you use a disk compression driver or a " #~ "disk manager. Create the disk and read the documentation " #~ "before you defragment the disk." #~ msgstr "" #~ "第一件需要的東西是一份 fips 的拷貝。您可以從離您最近的 " #~ "&debian; 鏡像裡的 tools/ 目錄下載它。解開這個 zip 壓" #~ "縮檔案，把 RESTORRB.EXE、FIPS.EXE 和 ERRORS.TXT 複製到一張開機軟碟裡。您可以" #~ "用在 DOS 下面用 sys a: 來製作開機磁片。" #~ "fips 含有相當不錯的文件，您也許會想看看。倘若您正在用磁" #~ "碟壓縮驅動程式或者磁碟管理員，那麼您絕對有必要讀一下這份文件。在您為這顆硬" #~ "碟清理零碎磁區之前請先做一張開機片並好好閱讀該文件。" #~ msgid "" #~ "The next thing needed is to move all the data to the beginning of the " #~ "partition. defrag, which comes standard with DOS 6.0 " #~ "and later, can easily do the job. See the fips " #~ "documentation for a list of other software that may do the trick. Note " #~ "that if you have Windows 9x, you must run defrag from " #~ "there, since DOS doesn't understand VFAT, which is used to support for " #~ "long filenames, used in Windows 95 and higher." #~ msgstr "" #~ "下一件要做的事，是把所有的資料移動到分割區的前面。DOS 自 6.0 後就包含了 " #~ "defrag 程式，它可以很方便地完成這個任務。請參閱 " #~ "fips 文件查看其他可用來執行此任務的軟體列表。要提醒的" #~ "是，如果您用的是 Windows 9x，那麼必須在 Windows 裡執行 defrag，原因是 DOS 不能識別 Windows 95 及其以後版本所使用的支援長檔名的 " #~ "VFAT 分割區。" #~ msgid "" #~ "After running the defragmenter (which can take a while on a large disk), " #~ "reboot with the fips disk you created in the floppy " #~ "drive. Simply type a:\\fips and follow the " #~ "directions." #~ msgstr "" #~ "零碎磁區清理程式 (defragmenter) 運行完畢後 (如果硬碟容量較大需要等比較" #~ "久)，用您在軟碟機裡製作的 fips 軟碟重新開機。只須輸入 " #~ "a:\\fips 然後按照提示操作。" #~ msgid "" #~ "Note that there are many other partition managers out there, in case " #~ "fips doesn't do the trick for you." #~ msgstr "" #~ "請注意，如果覺得 fips 不好用，還有許多其它的分割工具可" #~ "供差遣。" #~ msgid "Partitioning for DOS" #~ msgstr "DOS 下的分割" #~ msgid "" #~ "If you are partitioning for DOS drives, or changing the size of DOS " #~ "partitions, using &debian; tools, many people experience problems working " #~ "with the resulting FAT partitions. For instance, some have reported slow " #~ "performance, consistent problems with scandisk, or " #~ "other weird errors in DOS or Windows." #~ msgstr "" #~ "如果您用 &debian; 的工具軟體來為 DOS 硬碟分割區或更動了 DOS 分割區大小，請" #~ "注意，有許多人在這樣做了以後，於使用新分割出來的或者大小被改變的 FAT 分割" #~ "區的過程中發現各式各樣的問題。舉例來說，有些人回報發現性能下降，有的人則在" #~ "使用 scandisk 時發現有一致性 (consistent) 的問題， 還有" #~ "其它在 DOS 或 Windows 中發現的各種古怪的錯誤。" #, fuzzy #~ msgid "" #~ "Apparently, whenever you create or resize a partition for DOS use, it's a " #~ "good idea to fill the first few sectors with zeros. You should do this " #~ "prior to running DOS's format command by executing the " #~ "following command from &debian;:" #~ msgstr "" #~ "顯然地，當您為 DOS 建立新分割區或者更動分割區大小時，最好總是把第一個磁區" #~ "全部清除為零。執行 DOS 的 format 指令之前，於 &debian; " #~ "系統中，請這麼做：" #~ msgid "# dd if=/dev/zero of=/dev/hdXX bs=512 count=4" #~ msgstr "# dd if=/dev/zero of=/dev/hdXX bs=512 count=4" #~ msgid "" #~ "The rest of this section is lifted from the , answering the question, How do I enter the CMOS " #~ "configuration menu?. How you access the BIOS (or CMOS) configuration menu depends on who wrote your BIOS software:" #~ msgstr "" #~ "本節接下來的部分取自 中對如" #~ "何進入CMOS 設定選單一問的回答。您怎樣才能進入 BIOS(或CMOS) 設定選單取決於 BIOS 軟體的作者是誰：" #~ msgid "AMI BIOS" #~ msgstr "AMI BIOS" #~ msgid "Delete key during the POST (power on self test)" #~ msgstr "在 POST (開機自檢) 過程中按 Delete 鍵" #~ msgid "Award BIOS" #~ msgstr "Award BIOS" #~ msgid "" #~ " CtrlAltEsc " #~ ", or Delete key during the POST" #~ msgstr "" #~ "在 POST 過程中按 CtrlAltEsc ，或 Delete鍵" #~ msgid "DTK BIOS" #~ msgstr "DTK BIOS" #~ msgid "Esc key during the POST" #~ msgstr "在 POST 過程中按 Esc鍵" #~ msgid "IBM PS/2 BIOS" #~ msgstr "IBM PS/2 BIOS" #~ msgid "" #~ " CtrlAltInsert after CtrlAltDelete " #~ msgstr "" #~ " CtrlAltInsert 在按下面的組合鍵之後 CtrlAltDelete " #~ msgid "Phoenix BIOS" #~ msgstr "Phoenix BIOS" #~ msgid "" #~ " CtrlAltEsc " #~ " or CtrlAltS or F1" #~ msgstr "" #~ " CtrlAltEsc " #~ " 或 CtrlAltS 或 F1" #~ msgid "" #~ "Information on invoking other BIOS routines can be found in ." #~ msgstr "" #~ "若希望知道有關 BIOS 其它功能和設定的相關資料，您可以參閱 。" #~ msgid "" #~ "Some &arch-title; machines don't have a CMOS configuration menu in the " #~ "BIOS. They require a software CMOS setup program. If you don't have the " #~ "Installation and/or Diagnostics diskette for your machine, you can try " #~ "using a shareware/freeware program. Try looking in ." #~ msgstr "" #~ "有些 &arch-title; 架構的機器在 BIOS 中沒有包含 CMOS 設定選單。要對它們進行" #~ "設定，就需要有相應的 CMOS 設定軟體。如果您沒有與您機器對應的安裝或者診斷磁" #~ "片，那麼您不妨試一下共享軟體或自由軟體。請去以下網址找找看 。" #~ msgid "" #~ "Many BIOS setup menus allow you to select the devices that will be used " #~ "to bootstrap the system. Set this to look for a bootable operating system " #~ "on A: (the first floppy disk), then optionally the " #~ "first CD-ROM device (possibly appearing as D: or " #~ "E:), and then from C: (the " #~ "first hard disk). This setting enables you to boot from either a floppy " #~ "disk or a CD-ROM, which are the two most common boot devices used to " #~ "install &debian;." #~ msgstr "" #~ "許多 BIOS 的設定選單都能讓您選擇啟動系統的設備。讓它先在 A: (第一個軟碟機) 中找尋可開機的作業系統，不行的話，再在到第一個光" #~ "碟機設備 (有可能就是 D: 或 E:) " #~ "中尋找，然後接著在 C:(第一塊硬碟)尋找。照這樣設定的" #~ "話，就能讓您從軟碟或者光碟機開機。這是安裝 &debian; 最常用的兩個開機設備。" #~ msgid "" #~ "If you have a newer SCSI controller and you have a CD-ROM device attached " #~ "to it, you are usually able to boot from the CD-ROM. All you have to do " #~ "is enable booting from a CD-ROM in the SCSI-BIOS of your controller." #~ msgstr "" #~ "如果您有較新型號的 SCSI 控制器，而且您的光碟機是接在它上面的，那麼您很可" #~ "能 可以從這個光碟機開機。您所要做的僅僅是在您的控制器的 SCSI-BIOS 的設置中" #~ "允許從光碟機啟動系統。" #, fuzzy #~ msgid "" #~ "Another popular option is to boot from a USB storage device (also called " #~ "a USB memory stick or USB key). Some BIOSes can boot directly from a USB " #~ "storage device, but some cannot. You may need to configure your BIOS to " #~ "boot from a Removable drive or even from USB-ZIP to get it to boot from the USB device." #~ msgstr "" #~ "另外一個常見的選項是從 USB 隨身碟設備 (也叫 USB 隨身碟或者大姆碟)開機。有" #~ "些 BIOS 支援從 USB 隨身碟設備直接開機，有的則不行。如果要從 USB 設備啟動系" #~ "統的話，您可能需要在 BIOS 設定中，讓系統從 Removable drive " #~ "或者 USB-ZIP 開機。" #~ msgid "" #~ "Here are some details about how to set the boot order. Remember to reset " #~ "the boot order after &arch-kernel; is installed, so that you restart your " #~ "machine from the hard drive." #~ msgstr "" #~ "下面內容乃關於如何設置開機順序的一些細節。請記住，在安裝完 &arch-kernel; " #~ "後，要恢復原來的開機順序，這樣，您就能像以前一樣從硬碟開機了。" #~ msgid "Changing the Boot Order on IDE Computers" #~ msgstr "修改 IDE 介面電腦的開機順序" #~ msgid "" #~ "As your computer starts, press the keys to enter the BIOS utility. Often, " #~ "it is the Delete key. However, consult the hardware " #~ "documentation for the exact keystrokes." #~ msgstr "" #~ "當您的電腦開機時，可以按某些鍵進入 BIOS 的設定軟體。一般來說，按" #~ "Delete 鍵就可以了。若要知道按鍵的確切資料，可以參考硬體的" #~ "相關文件。" #~ msgid "" #~ "Find the boot sequence in the setup utility. Its location depends on your " #~ "BIOS, but you are looking for a field that lists drives." #~ msgstr "" #~ "在 BIOS 設定軟體中可以查看開機順序。在 BIOS 具體的什麼位置，和您的 BIOS 有" #~ "關。不管如何，您要找的是列有設備的欄位。" #~ msgid "Common entries on IDE machines are C, A, cdrom or A, C, cdrom." #~ msgstr "對 IDE 機器而言，列表裡常見的選項是 C、A、cdrom 或者 A、C、cdrom。" #~ msgid "C is the hard drive, and A is the floppy drive." #~ msgstr "C 就是硬碟，而 A 則是軟碟機。" #~ msgid "" #~ "Change the boot sequence setting so that the CD-ROM or the floppy is " #~ "first. Usually, the Page Up or Page Down keys cycle through the possible choices." #~ msgstr "" #~ "修改開機順序的設定，讓 CD-ROM 或者軟碟排在第一位。通常，用 Page " #~ "Up 或者 Page Down 鍵能夠循環地切換可能的選項。" #~ msgid "" #~ "Save your changes. Instructions on the screen tell you how to save the " #~ "changes on your computer." #~ msgstr "" #~ "然後，儲存您對設定的修改。螢幕上的提示會告訴您如何才能儲存您的設定。" #~ msgid "Changing the Boot Order on SCSI Computers" #~ msgstr "修改 SCSI 介面電腦的開機順序" #~ msgid "" #~ "As your computer starts, press the keys to enter the SCSI setup utility." #~ msgstr "當您的電腦開機時，可以按某些鍵進入 SCSI 的設定軟體。" #~ msgid "" #~ "You can start the SCSI setup utility after the memory check and the " #~ "message about how to start the BIOS utility displays when you start your " #~ "computer." #~ msgstr "" #~ "電腦開機過程中，您可以在記憶體檢測結束後，當螢幕出現如何進入 BIOS 設定程式" #~ "的提示的時候啟動 SCSI 設定軟體。" #~ msgid "" #~ "The keystrokes you need depend on the utility. Often, it is " #~ "CtrlF2. However, " #~ "consult your hardware documentation for the exact keystrokes." #~ msgstr "" #~ "您要按的按鍵通常因設定軟體而不同。一般來說，是按 CtrlF2。若要知道按鍵的確切資料，還是要參考" #~ "硬體的相關文件。" #~ msgid "Find the utility for changing the boot order." #~ msgstr "尋找用來修改開機順序的工具軟體。" #~ msgid "" #~ "Set the utility so that the SCSI ID of the CD drive is first on the list." #~ msgstr "透過這個工具軟體修改設定，讓光碟機的 SCSI ID 排在列表的首位。" #~ msgid "" #~ "Save your changes. Instructions on the screen tell you how to save the " #~ "changes on your computer. Often, you must press F10." #~ msgstr "" #~ "然後，儲存您對設定的修改。螢幕上的提示會告訴您如何才能儲存您的設定。通常，" #~ "您需要按 F10。" #~ msgid "Miscellaneous BIOS Settings" #~ msgstr "其餘的 BIOS 設定項目" #~ msgid "CD-ROM Settings" #~ msgstr "CD-ROM 的設定" #~ msgid "" #~ "Some BIOS systems (such as Award BIOS) allow you to automatically set the " #~ "CD speed. You should avoid that, and instead set it to, say, the lowest " #~ "speed. If you get seek failed error messages, this " #~ "may be your problem." #~ msgstr "" #~ "有些 BIOS 系統(如 Award BIOS)能讓您把光碟的讀取速度設定為自動。您應該盡量" #~ "不要那樣設定，相反，應該把它設成最低速。要是您碰到了 seek " #~ "failed 的錯誤提示，那麼就有可能是您的設定有問題。" #~ msgid "Extended vs. Expanded Memory" #~ msgstr "延伸記憶體與擴充記憶體" #~ msgid "" #~ "If your system provides both extended and " #~ "expanded memory, set it so that there is as much " #~ "extended and as little expanded memory as possible. &arch-kernel; " #~ "requires extended memory and cannot use expanded memory." #~ msgstr "" #~ "如果您的系統同時提供了延伸 (extended) 和擴" #~ "充 (expanded) 記憶體，那麼就把延伸記憶體設定得盡量大一些，而把" #~ "擴充記憶體設定得盡量小。&arch-kernel; 需要使用延伸記憶體，但無法利用擴充記" #~ "憶體。" #~ msgid "Virus Protection" #~ msgstr "病毒保護" #~ msgid "" #~ "Disable any virus-warning features your BIOS may provide. If you have a " #~ "virus-protection board or other special hardware, make sure it is " #~ "disabled or physically removed while running GNU/&arch-kernel;. These " #~ "aren't compatible with GNU/&arch-kernel;; moreover, due to the file " #~ "system permissions and protected memory of the &arch-kernel; kernel, " #~ "viruses are almost unheard of After installation you can " #~ "enable Boot Sector protection if you want. This offers no additional " #~ "security in &arch-kernel; but if you also run Windows it may prevent a " #~ "catastrophe. There is no need to tamper with the Master Boot Record (MBR) " #~ "after the boot manager has been set up. ." #~ msgstr "" #~ "停用您的 BIOS 提供的所有病毒警告功能。如果您安裝了防病毒卡或是其它特定的硬" #~ "件，請在運行 GNU/&arch-kernel; 期間，把它停用或者拆除。它們與 GNU/&arch-" #~ "kernel; 是不相容的。更進一步說，歸功於檔案系統的權限管理和 &arch-kernel; " #~ "核心的記憶體保護機制，病毒已然絕跡。 安裝完成之後，如果需" #~ "要，您可以啟用開機磁區保護。這對 &arch-kernel; 來說並不會提供更多的安全防" #~ "護，但是如果您同時還保有 Windows，它能夠防止否些災難發生。當 boot manager " #~ "安裝完成之後，您不需要再去修改主開機磁區 (MBR) " #~ msgid "Shadow RAM" #~ msgstr "記憶體映像" #~ msgid "" #~ "Your motherboard may provide shadow RAM or BIOS " #~ "caching. You may see settings for Video BIOS Shadow, " #~ "C800-CBFF Shadow, etc. Disable all " #~ "shadow RAM. Shadow RAM is used to accelerate access to the ROMs on your " #~ "motherboard and on some of the controller cards. &arch-kernel; does not " #~ "use these ROMs once it has booted because it provides its own faster 32-" #~ "bit software in place of the 16-bit programs in the ROMs. Disabling the " #~ "shadow RAM may make some of it available for programs to use as normal " #~ "memory. Leaving the shadow RAM enabled may interfere with &arch-kernel; " #~ "access to hardware devices." #~ msgstr "" #~ "您的主機或許會有記憶體映像(shadow RAM)或者 BIOS " #~ "caching 的功能。您可能會發現 Video BIOS Shadow、" #~ "C800-CBFF Shadow 等等的設定選項。停用" #~ "所有的記憶體映像。記憶體映像被用來提高對主機板上或某些控制卡上的 ROM 的存" #~ "取速度。一旦 &arch-kernel; 開機之後，它就不會再使用這些 ROM。&arch-" #~ "kernel; 棄之不用的原因是：&arch-kernel; 自己提供了更快的32位元的軟體來替代" #~ "了 ROM 中的16位元程式的功能。停用記憶體映像就可以讓程式能使用更多的常規記" #~ "憶體。而繼續開啟記憶體映像則有可能妨礙 &arch-kernel; 存取硬體設備。" #~ msgid "Memory Hole" #~ msgstr "記憶體空洞" #~ msgid "" #~ "If your BIOS offers something like 15–16 MB Memory Hole, please disable that. &arch-kernel; expects to find memory there " #~ "if you have that much RAM." #~ msgstr "" #~ "如果您的 BIOS 有類似 15–16 MB Memory Hole 的選項，請" #~ "停用它。如果您有那麼多記憶體的話，&arch-kernel; 就會認為在那兒應該能找到記" #~ "憶體區塊。" #~ msgid "" #~ "We have a report of an Intel Endeavor motherboard on which there is an " #~ "option called LFB or Linear Frame Buffer. " #~ "This had two settings: Disabled and 1 Megabyte. Set it to 1 Megabyte. When disabled, the " #~ "installation floppy was not read correctly, and the system eventually " #~ "crashed. At this writing we don't understand what's going on with this " #~ "particular device — it just worked with that setting and not " #~ "without it." #~ msgstr "" #~ "我們收到報告指稱，有一款 Intel 的主機的設定中有名為 LFB 或 " #~ "Linear Frame Buffer 的選項。該選項有兩個選擇：" #~ "Disabled 和 1 Megabyte。請把它設為 1 " #~ "Megabyte。如果停用它，那麼讀取安裝軟碟時將會出錯，而系統最後會當" #~ "機。在撰寫本文時，我們尚未弄清這個設備出了什麼問題。現在僅知道，如果這樣啟" #~ "用該設定，則一切正常，否則就不行。" #~ msgid "Advanced Power Management" #~ msgstr "進階電源管理" #~ msgid "" #~ "If your motherboard provides Advanced Power Management (APM), configure " #~ "it so that power management is controlled by APM. Disable the doze, " #~ "standby, suspend, nap, and sleep modes, and disable the hard disk's power-" #~ "down timer. &arch-kernel; can take over control of these modes, and can " #~ "do a better job of power-management than the BIOS." #~ msgstr "" #~ "倘若您的主機板提供了進階電源管理 (APM) 的支援，請設定讓 APM 來管理電源。請" #~ "同時停用 doze、standby、suspend、nap 和 sleep 模式，另外還要停用硬碟的電源" #~ "關閉定時器。&arch-kernel; 可以接管這些模式的控制權，而且能比 BIOS 的電源管" #~ "理做得更好。" #~ msgid "" #~ "Installation instructions and device drivers (DASD, XPRAM, Console, tape, " #~ "z90 crypto, chandev, network) for Linux on &arch-title; using kernel 2.4" #~ msgstr "" #~ "在 &arch-title; 上使用Linux 2.4 版核心的安裝指示和設備驅動程式 (DASD, " #~ "XPRAM, Console, tape, z90 crypto, chandev, network)" #~ msgid "Device Drivers and Installation Commands" #~ msgstr "設備驅動程式與安裝指令" #~ msgid "Linux/Alpha FAQ" #~ msgstr "Linux/Alpha 常見問答集" #~ msgid "Partitioning in Tru64 UNIX" #~ msgstr "Tru64 UNIX 下的分割" #~ msgid "" #~ "Tru64 UNIX, formerly known as Digital UNIX, which is in turn formerly " #~ "known as OSF/1, uses the partitioning scheme similar to the BSD " #~ "disk label, which allows for up to eight partitions per " #~ "disk drive. The partitions are numbered 1 through to " #~ "8 in Linux and lettered a " #~ "through to h in UNIX. Linux kernels 2.2 and higher always " #~ "correspond 1 to a, 2 to " #~ "b and so on. For example, rz0e in " #~ "Tru64 UNIX would most likely be called sda5 in Linux." #~ msgstr "" #~ "Tru64 UNIX 的前身是 Digital UNIX，更早是 OSF/1，採用的分割區方式類似於 " #~ "BSD 的 disk label，它允許每個磁碟上最多有八個分割區。分割區" #~ "命名在 Linux 下從 1 到 8，在 UNIX 下是按" #~ "字母次序從 a 到 h。Linux 核" #~ "心 2.2 或更高的版本是 1 對應 a，2 對應 b，依此類推。例如，rz0e 是" #~ "在 Tru64 UNIX 中的命名，而 sda5 是在 Linux 裡的名稱。" #~ msgid "" #~ "Partitions in a Tru64 disk label may overlap. Moreover, if this disk will " #~ "be used from Tru64, the c partition is required to span " #~ "the entire disk (thus overlapping all other non-empty partitions). Under " #~ "Linux this makes sda3 identical to sda (sdb3 to sdb, if " #~ "present, and so on). However, the partman partitioning tool used by &d-i; " #~ "cannot handle overlapping partitions at present. As a result, it is " #~ "currently not recommended to share disks between Tru64 and Debian. " #~ "Partitions on Tru64 disks can be mounted under Debian after installation " #~ "has been completed." #~ msgstr "" #~ "Tru64 磁碟標籤下的分割區可以重疊。此外，如果以前磁碟在 Tru64 下使用，" #~ "c 分割區會要求擴展到整個磁碟 (因此會覆蓋其他所有的非空分割" #~ "區)。在 Linux 下這使得 sda3 不同於 sda (sdb3 對應於 sdb，等" #~ "等)。然而，&d-i; 使用的 partman 分割工具目前尚不能處理重疊的分割區。 因" #~ "此，目前不建議在 Tru64 和 Debian 之間共享磁碟。完成安裝之後，Tru64 的磁碟" #~ "分割區可以掛載到 Debian 之下。" #~ msgid "" #~ "Another conventional requirement is for the a partition to " #~ "start from the beginning of the disk, so that it always includes the boot " #~ "block with the disk label. If you intend to boot Debian from that disk, " #~ "you need to size it at least 2MB to fit aboot and perhaps a kernel. Note " #~ "that this partition is only required for compatibility; you must not put " #~ "a file system onto it, or you'll destroy data." #~ msgstr "" #~ "另外一個約定俗成的要求是分割區 a 起始於磁碟開始處，因此它總" #~ "包含具有磁碟標籤的開機磁區。如果您從該磁碟開機 Debian，您至少需要給它 2MB " #~ "空間以在儲存 aboot 和核心。注意，此分割區僅為相容考慮﹔您千萬不要將檔案系" #~ "統置於其上，否則資料會破壞。" #~ msgid "" #~ "It is possible, and indeed quite reasonable, to share a swap partition " #~ "between UNIX and Linux. In this case it will be needed to do a " #~ "mkswap on that partition every time the system is " #~ "rebooted from UNIX into Linux, as UNIX will damage the swap signature. " #~ "You may want to run mkswap from the Linux start-up " #~ "scripts before adding swap space with swapon -a." #~ msgstr "" #~ "我們可以，也有理由讓 UNIX 和 Linux 共享置換分割區。這時就需要在該分割區上" #~ "使用 mkswap。因為 UNIX 將破壞 swap 標誌，所以每次從 " #~ "UNIX 到 Linux 重啟後都要重新執行一次。 您可以讓 mkswap " #~ "從 Linux 的開機腳本裡面執行，將之放置在 swapon -a 添加" #~ "置換分割區的指令之前。" #~ msgid "" #~ "If you want to mount UNIX partitions under Linux, note that Digital UNIX " #~ "can use two different file system types, UFS and AdvFS, of which Linux " #~ "only understands the former." #~ msgstr "" #~ "如果您想在 Linux 中掛載 UNIX 分割區，注意 Digital UNIX 可以使用兩種不同的" #~ "檔案系統類型，UFS 和 AdvFS，而 Linux 只能識別前者。" #~ msgid "Partitioning in Windows NT" #~ msgstr "Windows NT 下的分割" #, fuzzy #~ msgid "" #~ "Windows NT uses the PC-style partition table. If you are manipulating " #~ "existing FAT or NTFS partitions, it is recommended that you use the " #~ "native Windows NT tools (or, more conveniently, you can also repartition " #~ "your disk from the AlphaBIOS setup menu). Otherwise, it is not really " #~ "necessary to partition from Windows; the Linux partitioning tools will " #~ "generally do a better job. Note that when you run NT, the Disk " #~ "Administrator may offer to write a harmless signature on " #~ "non-Windows disks if you have any. Never let it do " #~ "that, as this signature will destroy the partition information." #~ msgstr "" #~ "Windows NT 使用 PC 風格的分割表。如果您要處理已存在的 FAT 或 NTFS 分割區，" #~ "建議使用 Windows NT 本身的工具 (或者，照慣例，您可以用 AlphaBIOS 設置選單" #~ "裡面的工具重新分割)。否則，真沒有必要從 Windows 來分割磁區，Linux 的分割區" #~ "工具可以做得更好。注意，如果您使用 NT，磁碟管理員也許會建議您寫一個" #~ "無害的簽章到您的非 Windows 的磁碟上。千萬別讓" #~ "它那樣做，這個標誌會破壞該分割區上的資料。" #~ msgid "" #~ "If you plan to boot Linux from an ARC/AlphaBIOS/ARCSBIOS console, you " #~ "will need a (small) FAT partition for MILO. 5 MB is quite sufficient. If " #~ "Windows NT is installed, its 6 MB bootstrap partition can be employed for " #~ "this purpose. Debian &releasename; does not support installing MILO. If " #~ "you already have MILO installed on your system, or install MILO from " #~ "other media, Debian can still be booted from ARC." #~ msgstr "" #~ "如果您計劃從 ARC/AlphaBIOS/ARCSBIOS 控制台開機 Linux，您也許需要給 MILO 一" #~ "個 (小的) FAT 分割區，5 Mb 就足夠了。 如果已經安裝了 Windows NT，它的 6 " #~ "Mb 開機分割區可以用來滿足此要求。Debian &releasename; 不支援安裝 MILO。如" #~ "果您的系統上已經有 MILO，或者從其他媒介安裝，Debian 仍然可以從 ARC 開機。" #~ msgid "" #~ "With the exception of the BVM and Motorola VMEbus computers, the only " #~ "supported installation method for m68k systems is booting from a local " #~ "disk or floppy using an AmigaOS/TOS/MacOS-based bootstrap, for these " #~ "machines you will need the original operating system in order to boot " #~ "Linux. In order to boot Linux on the BVM and Motorola VMEbus machines you " #~ "will need the BVMBug or 16xBug boot ROMs." #~ msgstr "" #~ "除了 BVM 和 Motorola VMEbus 系列的電腦，m68k 系統的電腦，唯一支援的安裝方" #~ "式就是用 AmigaOS、TOS 或 MacOS 的 boot-loader 從本地的硬碟或軟碟開機。所" #~ "以，對於這種類型的電腦，您必須要有原始作業系統來開機 Linux。而為了在 BVM " #~ "和 Motorola VMEbus 系列的電腦上開機 Linux，BVMBug 或 " #~ "`16xBug boot-loader 是必須的。" #~ msgid "Linux/m68k FAQ" #~ msgstr "Linux/m68k 常見問答集" #, fuzzy #~ msgid "Whether IDE or SCSI (most m68k computers are SCSI)." #~ msgstr "是 IDE 還是 SCSI(大多數電腦上是 IDE)" #~ msgid "" #~ "A 68030 or better processor is recommended for m68k installs. You may get " #~ "by with a little less drive space than shown." #~ msgstr "" #~ "在 m68k 機器上安裝，建議使用 68030 或更快的處理器。您可能用比建議稍小的硬" #~ "碟空間就能完成安裝。" #~ msgid "Partitioning in AmigaOS" #~ msgstr "AmigaOS 下的分割" #~ msgid "" #~ "If you are running AmigaOS, you can use the HDToolBox " #~ "program to adjust your native partitions prior to installation." #~ msgstr "" #~ "如果您執行 AmigaOS，您可以使用 HDToolBox 程式在安裝之前" #~ "調整您的分割區。" #~ msgid "Partitioning in Atari TOS" #~ msgstr "Atari TOS 下的分割" #~ msgid "" #~ "Atari partition IDs are three ASCII characters, use LNX " #~ "for data and SWP for swap partitions. If using the low " #~ "memory installation method, a small Minix partition is also needed (about " #~ "2 MB), for which the partition ID is MNX. Failure to set " #~ "the appropriate partition IDs not only prevents the Debian installation " #~ "process from recognizing the partitions, but also results in TOS " #~ "attempting to use the Linux partitions, which confuses the hard disk " #~ "driver and renders the whole disk inaccessible." #~ msgstr "" #~ "Atari 的分割區 ID 是三個 ASCII 字元，LNX 用於資料，" #~ "SWP 用於置換分割區。如果使用小記憶體安裝方式，還需要一個小" #~ "的 Minix 分割區(大約 2MB)，它的 ID 是``MNX''。錯誤的分割區 ID 不僅會因為 " #~ "Debian 無法識別分割區而中斷安裝進程，還會造成 TOS 使用 Linux 分割區，讓硬" #~ "碟驅動程式混亂，使得整個磁碟無法使用。" #~ msgid "" #~ "There are a multitude of third party partitioning tools available (the " #~ "Atari harddisk utility doesn't permit changing the " #~ "partition ID); this manual cannot give detailed descriptions for all of " #~ "them. The following description covers SCSITool (from " #~ "Hard+Soft GmBH)." #~ msgstr "" #~ "有很多第三方的分割工具(Atari harddisk 工具不允許修改分" #~ "割區 ID)，本手冊無法對它們進行詳細說明。下面為 SCSITool (來自 Hard+Soft GmBH)的說明。" #~ msgid "" #~ "Start SCSITool and select the disk you want to " #~ "partition (Disk menu, item select)." #~ msgstr "" #~ "啟動 SCSITool 然後選擇您要分割區的磁碟 (Disk 選單中的 select)。" #~ msgid "" #~ "From the Partition menu, select either " #~ "New to add new partitions or change the " #~ "existing partition sizes, or Change to change " #~ "one specific partition. Unless you have already created partitions with " #~ "the right sizes and only want to change the partition ID, " #~ "New is probably the best choice." #~ msgstr "" #~ "從 Partition 選單選擇 New 以" #~ "添加新分割區或者修改現有分割區的大小，或選擇 Change 來修改指定的分割區。除非您已經建立了大小合適的分割區並只想修" #~ "改分割區 ID，否則 New 大概是最佳選擇。" #~ msgid "" #~ "For the New choice, select existing in the dialog box prompting the initial settings. The next " #~ "window shows a list of existing partitions which you can adjust using the " #~ "scroll buttons, or by clicking in the bar graphs. The first column in the " #~ "partition list is the partition type; just click on the text field to " #~ "edit it. When you are finished changing partition settings, save the " #~ "changes by leaving the window with the OK button." #~ msgstr "" #~ "在 New 選項中，從提示初始設定的對話框裡選擇 " #~ "existing。接下來的視窗顯示的是現有分割區的列表，您可" #~ "以透過滑鼠滾動鈕進行調整，或者直接點擊長條圖。分割區列表的第一列是分割區類" #~ "型，點擊文字欄位就可以編輯它。當您完成分割區設定，用 OK 按鈕儲存並離開視窗。" #~ msgid "" #~ "For the Change option, select the partition to " #~ "change in the selection list, and select other systems in the dialog box. The next window lists detailed information " #~ "about the location of this partition, and lets you change the partition " #~ "ID. Save changes by leaving the window with the OK " #~ "button." #~ msgstr "" #~ "在 Change 選項中，從列表裡面選擇要修改的分割" #~ "區，然後在對話框中選擇 other systems。接下來的視窗會" #~ "列出該分割區位置的詳細資料，並讓您修改分割區 ID。用 OK 按鈕儲存並離開視窗。" #~ msgid "" #~ "Write down the Linux names for each of the partitions you created or " #~ "changed for use with Linux — see ." #~ msgstr "" #~ "記下您為了使用 Linux 而建立或修改的分割區的 Linux 名稱 — 請參考 " #~ "。" #~ msgid "" #~ "Quit SCSITool using the Quit item from the File menu. The computer " #~ "will reboot to make sure the changed partition table is used by TOS. If " #~ "you changed any TOS/GEM partitions, they will be invalidated and have to " #~ "be reinitialized (we told you to back up everything on the disk, didn't " #~ "we?)." #~ msgstr "" #~ "從 File 選單下使用 Quit 選項" #~ "退出 SCSITool。電腦將重新開機以確保 TOS 會使用修改過的" #~ "分割區表。如果您修改了任何 TOS/GEM 分割區，它們將會失效並要重新初始化 (我" #~ "們已經告訴過您需要備份磁碟上的所有資料，不是嗎？)。" #~ msgid "" #~ "There is a partitioning tool for Linux/m68k called atari-fdisk in the installation system, but for now we recommend you " #~ "partition your disk using a TOS partition editor or some disk tool. If " #~ "your partition editor doesn't have an option to edit the partition type, " #~ "you can do this crucial step at a later stage (from the booted temporary " #~ "install RAMdisk). SCSITool is only one of the " #~ "partition editors we know of which supports selection of arbitrary " #~ "partition types. There may be others; select the tool that suits your " #~ "needs." #~ msgstr "" #~ "Linux/m68k 中有一個分割工具，在安裝系統中被稱為 atari-fdisk，但是我們現在建議您使用 TOS 分割區編輯器或其他的磁碟工具來對硬碟" #~ "做分割。如果您的分割區編輯器沒有編輯分割區類型的選項，您可以在後續階段執行" #~ "這項重要工作(從開機臨時安裝 RAMdisk)。SCSITool 是我們所" #~ "知唯一支援任意選擇分割區類型的分割區編輯器。也許還有其他的，請選擇一個符合" #~ "您要求的工具。" #~ msgid "Partitioning in MacOS" #~ msgstr "MacOS 下的分割" #~ msgid "" #~ "Partitioning tools for Macintosh tested include pdisk, " #~ "HD SC Setup 7.3.5 (Apple), HDT 1.8 " #~ "(FWB), SilverLining (LaCie), and DiskTool (Tim Endres, GPL). Full versions are required for HDT and SilverLining. The Apple tool requires a " #~ "patch in order to recognize third-party disks (a description on how to " #~ "patch HD SC Setup using ResEdit can " #~ "be found at )." #~ msgstr "" #~ "Macintosh 下經過測試的分割工具包括 pdisk、HD " #~ "SC Setup 7.3.5 (Apple)、HDT 1.8 (FWB)、" #~ "SilverLining (LaCie) 和 DiskTool(Tim Endres, GPL)。對 HDT 和 " #~ "SilverLining 需要完整版才可完成工作。Apple 工具需要補丁" #~ "才能識別第三方的磁碟 (如何給 HD SC Setup 補丁(使用 " #~ "ResEdit)的說明位於 )。" #, fuzzy #~ msgid "" #~ "For IDE based Macs, you need to use Apple Drive Setup " #~ "to create empty space for the Linux partitions, and complete the " #~ "partitioning under Linux, or use the MacOS version of pdisk available for " #~ "download from Alsoft." #~ msgstr "" #~ "對於使用 IDE 的 Mac，您需要使用 Apple Drive Setup 來為 " #~ "Linux 分割區建立空間，然後在 Linux 下完成分割，或者使用 MacOS 版的 pdisk，" #~ "它可以從 MkLinux FTP 伺服器取得。" #~ msgid "Firmware Revisions and Existing OS Setup" #~ msgstr "韌體修訂版和既有的 OS 設定" #~ msgid "" #~ "&arch-title; machines are generally self-configuring and do not require " #~ "firmware configuration. However, you should make sure that you have the " #~ "appropriate ROM and system patches. On the Macintosh, MacOS version >= " #~ "7.1 is recommended because version 7.0.1 contains a bug in the video " #~ "drivers preventing the boot loader from deactivating the video " #~ "interrupts, resulting in a boot hang. On the BVM VMEbus systems you " #~ "should make sure you are using BVMBug revision G or higher boot ROMs. The " #~ "BVMBug boot ROMs do not come as standard on the BVM systems but are " #~ "available from BVM on request free of charge." #~ msgstr "" #~ "&arch-title; 機器通常會自行設定，不需要設定韌體。但是，您應該確定您用了適" #~ "宜的 ROM 和系統補丁。在 Macintosh 上，建議使用 MacOS >= 7.1 的版本，這是由" #~ "於版本 7.0.1 在顯示驅動方面包含臭蟲，它會阻擋 boot loader 禁止顯示中斷呼" #~ "叫，造成開機時當機。在 BVM VMEbus 系統上，您應該確定使用 BVMBug 修訂版 G " #~ "或更新的 boot ROM。BVMBug boot ROM 不屬於 BVM 系統的標準配置，但可用從 " #~ "BVM 免費取得。" #~ msgid "" #~ "Atari TT RAM boards are notorious for RAM problems under Linux; if you " #~ "encounter any strange problems, try running at least the kernel in ST-" #~ "RAM. Amiga users may need to exclude RAM using a booter memfile. FIXME: more description of this needed. " #~ msgstr "" #~ "Atari TT 記憶體以在 Linux 下的記憶體問題而獲臭名。無論您碰到了何種怪異的問" #~ "題，請至少試試換用 ST-RAM 來運作核心。Amiga 的使用者可能需要用 booter " #~ "menfile 來排除部分記憶體。 FIXME: " #~ "more description of this needed. " #~ msgid "Whether IDE or SCSI (most computers are IDE)." #~ msgstr "是 IDE 還是 SCSI(大多數電腦上是 IDE)" #, fuzzy #~ msgid "" #~ "When debian-installer finishes, before the first " #~ "system load, you have only a very basic command line driven system. The " #~ "graphical interface which displays windows on your monitor will not be " #~ "installed unless you select it with tasksel. It's " #~ "optional because many &debian-gnu; systems are servers which don't really " #~ "have any need for a graphical user interface to do their job." #~ msgstr "" #~ "當 debian-installer 程式執行結束、系統首次載入之" #~ "前，您只有一個非常簡單的命令列系統。除非您在最後一個步驟裡用 " #~ "tasksel 或 aptitude 選擇安裝" #~ "了能在您的顯示器上顯示視窗的圖形界面，否則它將不會被自動安裝。因為許多 " #~ "&debian-gnu; 系統是被用作伺服器，它們的工作根本不需要任何圖形化的使用者界" #~ "面，所以它在這裡只是一個選項。" #~ msgid "RAM" #~ msgstr "記憶體" #~ msgid "450 megabytes" #~ msgstr "450 MB" #~ msgid "Server" #~ msgstr "伺服器" #~ msgid "" #~ "Here is a sampling of some common Debian system configurations. You can " #~ "also get an idea of the disk space used by related groups of programs by " #~ "referring to ." #~ msgstr "" #~ "這裡有些一般 Debian 系統設定的樣本。您可以參閱 以瞭解各類軟體需要佔多大的硬碟空間。" #~ msgid "Standard Server" #~ msgstr "標準伺服器" #~ msgid "" #~ "This is a small server profile, useful for a stripped down server which " #~ "does not have a lot of niceties for shell users. It includes an FTP " #~ "server, a web server, DNS, NIS, and POP. For these 100MB of disk space " #~ "would suffice, and then you would need to add space for any data you " #~ "serve up." #~ msgstr "" #~ "這裡有一台小型伺服器範例，它適用於精簡型伺服器，即沒有為 shell 的使用者安" #~ "裝過多好用的軟體。這類伺服器裝有：FTP 伺服、web 伺服、DNS、NIS 以及 POP 服" #~ "務。這些服務總共需要 100MB 磁碟空間，您還需要另外算上服務所需資料所佔用的" #~ "空間。" #~ msgid "Desktop" #~ msgstr "桌面" #~ msgid "" #~ "A standard desktop box, including the X window system, full desktop " #~ "environments, sound, editors, etc. You'll need about 2GB using the " #~ "standard desktop task, though it can be done in far less." #~ msgstr "" #~ "標準的桌面用機器安裝有 X 視窗系統、完整的桌面環境、音效軟體、編輯器等。這" #~ "些軟體套件將總共需要約 2G 空間，儘管也可以不需要這麼多。" #~ msgid "Work Console" #~ msgstr "工作控制台" #~ msgid "" #~ "A more stripped-down user machine, without the X window system or X " #~ "applications. Possibly suitable for a laptop or mobile computer. The size " #~ "is around 140MB." #~ msgstr "" #~ "這是被高度精簡的使用者機器，它沒有安裝 X 視窗系統或者 X 軟體。可能適用於筆" #~ "記型電腦或者手提電腦。其所需空間約為 140MB。" #~ msgid "Developer" #~ msgstr "開發人員" #~ msgid "" #~ "A desktop setup with all the development packages, such as Perl, C, C++, " #~ "etc. Size is around 475MB. Assuming you are adding X11 and some " #~ "additional packages for other uses, you should plan around 800MB for this " #~ "type of machine." #~ msgstr "" #~ "這是包括所有開發軟體套件的桌面設置，例如 Perl、C、C++ 等。其所需空間約為 " #~ "475MB。若是您為了其它用途，而另行安裝了 X11 和其它的軟體套件，那麼您需要為" #~ "這類機器規劃出約 800MB 空間。" #~ msgid "" #~ "Many people have tried operating their 90 MHz CPU at 100 MHz, etc. It " #~ "sometimes works, but is sensitive to temperature and other factors and " #~ "can actually damage your system. One of the authors of this document over-" #~ "clocked his own system for a year, and then the system started aborting " #~ "the gcc program with an unexpected signal while it was " #~ "compiling the operating system kernel. Turning the CPU speed back down to " #~ "its rated value solved the problem." #~ msgstr "" #~ "有很多人嘗試過把他們的 90 MHz 的處理器超頻到 100 MHz 使用，以及其他諸如此" #~ "類的做法。這有時可行，但是這賴於外界的溫度和其他因素，而且超頻可能會損毀您" #~ "的系統。這份文件的作者之一曾把他的系統超頻使用了有一年，從那以後他在編譯操" #~ "作業系統核心時，gcc 總是會被意外的訊號中止。後來，把處" #~ "理器的頻率調回標準速度後，問題迎刃而解。" #~ msgid "" #~ "The gcc compiler is often the first thing to die from " #~ "bad memory modules (or other hardware problems that change data " #~ "unpredictably) because it builds huge data structures that it traverses " #~ "repeatedly. An error in these data structures will cause it to execute an " #~ "illegal instruction or access a non-existent address. The symptom of this " #~ "will be gcc dying from an unexpected signal." #~ msgstr "" #~ "如果記憶體模組有故障的話 (或者出現其他會使資料發生異變的硬體故障)，" #~ "gcc 編譯器經常是第一個停止工作的程式。因為它會生成龐大" #~ "的資料結構，並在記憶體中頻繁移動。一旦這些資料結構中有錯，就會導致程式執行" #~ "非法指令或者存取不存在的位址空間。症狀就是 gcc 被一個意" #~ "外的訊號中止執行。" #~ msgid "" #~ "If you do have true-parity RAM and your motherboard can handle it, be " #~ "sure to enable any BIOS settings that cause the motherboard to interrupt " #~ "on memory parity errors." #~ msgstr "" #~ "如果您配備有真奇偶檢驗的記憶體，而且您的主機板也支援這種記憶體，那麼請一定" #~ "要在 BIOS 的設定裡開啟相應的選項，好讓主機板在發現奇偶檢驗錯時送出中斷呼" #~ "叫。" #~ msgid "The Turbo Switch" #~ msgstr "加速 (Turbo) 開關" #~ msgid "" #~ "Many systems have a turbo switch that controls the " #~ "speed of the CPU. Select the high-speed setting. If your BIOS allows you " #~ "to disable software control of the turbo switch (or software control of " #~ "CPU speed), do so and lock the system in high-speed mode. We have one " #~ "report that on a particular system, while Linux is auto-probing (looking " #~ "for hardware devices) it can accidentally touch the software control for " #~ "the turbo switch." #~ msgstr "" #~ "有許多系統配有一個 turbo 開關，透過這個開關可以控制處" #~ "理器的運行速度。請把它調節到``高速''。如果您的 BIOS 能讓您停用讓軟體控制加" #~ "速開關的功能(或者對軟體對處理器速度的控制)，那麼就請停用它，這會將系統鎖定" #~ "為高速運行模式。我們曾受到過報告稱，在某特別的系統上， Linux 在自動檢測 " #~ "(搜尋硬體設備)時，會無意觸動加速開關的軟體控制。" #~ msgid "Cyrix CPUs and Floppy Disk Errors" #~ msgstr "Cyrix 處理器和軟碟錯誤" #~ msgid "" #~ "Many users of Cyrix CPUs have had to disable the cache in their systems " #~ "during installation, because the floppy disk has errors if they do not. " #~ "If you have to do this, be sure to re-enable your cache when you are " #~ "finished with installation, as the system runs much " #~ "slower with the cache disabled." #~ msgstr "" #~ "許多 Cyrix 處理器的使用者在安裝時，必須停用系統的高速快取 (cache)。如果不" #~ "如此，就會發生軟碟錯誤。如果您停用了高速快取，請在安裝完成後重新開啟它。因" #~ "為如果您繼續停用，系統會變慢很多。" #~ msgid "" #~ "We don't think this is necessarily the fault of the Cyrix CPU. It may be " #~ "something that Linux can work around. We'll continue to look into the " #~ "problem. For the technically curious, we suspect a problem with the cache " #~ "being invalid after a switch from 16-bit to 32-bit code." #~ msgstr "" #~ "我們並不認為這一定是 Cyrix 處理器的過錯。Linux 或許能想辦法避免它。我們將" #~ "繼續 關注這個問題。基於技術上的好奇，我們猜測這可能是系統從 16 位元切換到 " #~ "32 位元模式時，導致高速快取失效造成的。" #~ msgid "Peripheral Hardware Settings" #~ msgstr "周邊硬體的設置" #~ msgid "" #~ "You may have to change some settings or jumpers on your computer's " #~ "peripheral cards. Some cards have setup menus, while others rely on " #~ "jumpers. This document cannot hope to provide complete information on " #~ "every hardware device; what it hopes to provide is useful tips." #~ msgstr "" #~ "您也許必須得修改您周邊設備卡上的一些設定或跳線。有的卡有設定選單，而另一些" #~ "則使用跳線。本文件無意為您提供所有硬體設備的全面資料，只不過希望能提供一些" #~ "有用的提示。" #~ msgid "" #~ "If any cards provide mapped memory, the memory should be " #~ "mapped somewhere between 0xA0000 and 0xFFFFF (from 640K to just below 1 " #~ "megabyte) or at an address at least 1 megabyte greater than the total " #~ "amount of RAM in your system." #~ msgstr "" #~ "如果有周邊卡提供了記憶體映射 (mapped memory)，那麼這塊記憶" #~ "體應該被映射到介於 0xA0000 和 0xFFFFF (從 640K 到正好 1M) 的某個地方，也可" #~ "以映射到您系統中總記憶體 1 MB 以後的位址。" #~ msgid "More than 64 MB RAM" #~ msgstr "大於 64 MB 的記憶體" #~ msgid "" #~ "The Linux Kernel cannot always detect what amount of RAM you have. If " #~ "this is the case please look at ." #~ msgstr "" #~ "Linux 核心有時不能檢測出您系統中的記憶體大小。如果您遇到這種情況，請參閱 " #~ "。" #~ msgid "" #~ "The very best motherboards support parity RAM and will actually tell you " #~ "if your system has a single-bit error in RAM. Unfortunately, they don't " #~ "have a way to fix the error, thus they generally crash immediately after " #~ "they tell you about the bad RAM. Still, it's better to be told you have " #~ "bad memory than to have it silently insert errors in your data. Thus, the " #~ "best systems have motherboards that support parity and true-parity memory " #~ "modules; see ." #~ msgstr "" #~ "最好的主機板應該會支援奇偶檢驗記憶體 (parity RAM)，它會在發現記憶體中有一" #~ "個錯誤位元時向您報告。可惜的是，主機板並沒有辦法修正錯誤，因此它通常會在向" #~ "您報告記憶體錯誤之後立即當機。無論如何，有報告錯誤總比不聲不響地在您的資料" #~ "中插入錯誤數據來的好。所以，最好的系統應當配備支援奇偶檢驗和真奇偶檢驗 " #~ "(true-parity) 的記憶體。另外還可以參閱 。" #~ msgid "" #~ "Install additional software (tasks and/or " #~ "packages), at your discretion." #~ msgstr "" #~ "選擇安裝您要使用的其他的軟體(程式單元和/或" #~ "軟體套件)﹔" #~ msgid "" #~ "Upon loading the new base system, base-config " #~ "supervises adding users, setting a time zone (via tzsetup), and setting up the package installation system (using " #~ "apt-setup). It then launches tasksel which can be used to select large groups of related programs, " #~ "and in turn can run aptitude which allows you to " #~ "choose individual software packages." #~ msgstr "" #~ "在載入新裝的基本系統時，base-config 帶領您新增使用" #~ "者帳號、設定時區 (透過 tzsetup)，並進行軟體套件安裝" #~ "系統的配置 (使用 apt-setup)。然後，它將開機 " #~ "tasksel 程式來安裝以相互關聯分成的幾個軟體大組件，" #~ "或者 aptitude 程式來讓您挑選單獨的軟體套件。" #~ msgid "" #~ "After installation you can enable Boot Sector protection if you want. " #~ "This offers no additional security in Linux but if you also run Windows " #~ "it may prevent a catastrophe. There is no need to tamper with the Master " #~ "Boot Record (MBR) after the boot manager has been set up." #~ msgstr "" #~ "在安裝完成後，如果您願意的話，可以打開啟動磁區的保護。但這對於 Linux 來" #~ "說，並不會提高安全性。若是您同時也用 Windows，這也許能幫您避免一場災難。安" #~ "裝設置好開機管理員 (boot manager) 以後，就不用再去操心主開機區記錄 (MBR)。"