# 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-30 23:04+0000\n" "PO-Revision-Date: 2005-07-18 12:10+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 #: install-methods.xml:5 #, no-c-format msgid "Obtaining System Installation Media" msgstr "取得系統安裝媒介" #. Tag: title #: install-methods.xml:12 #, fuzzy, no-c-format #| msgid "Official &debian-gnu; CD-ROM Sets" msgid "Official &debian-gnu; installation images" msgstr "&debian-gnu; 官方光碟套件" #. Tag: para #: install-methods.xml:13 #, fuzzy, no-c-format #| msgid "" #| "By far the easiest way to install &debian-gnu; is from an Official " #| "&debian; CD-ROM Set. You can buy a set from a vendor (see the CD vendors page). You may also " #| "download the CD-ROM images from a &debian; mirror and make your own set, " #| "if you have a fast network connection and a CD burner (see the Debian CD page for detailed instructions). If " #| "you have a &debian; CD set and CDs are bootable on your machine, you can " #| "skip right to ; much effort has been " #| "expended to ensure the files most people need are there on the CD. " #| "Although a full set of binary packages requires several CDs, it is " #| "unlikely you will need packages on the third CD and above. You may also " #| "consider using the DVD version, which saves a lot of space on your shelf " #| "and you avoid the CD shuffling marathon." msgid "" "By far the easiest way to install &debian-gnu; is from a set of official " "&debian; installation images. You can buy a set of CDs/DVDs from a vendor " "(see the CD vendors page). " "You may also download the installation images from a &debian; mirror and " "make your own set, if you have a fast network connection and a CD/DVD burner " "(see the Debian CD/DVD page and " "Debian CD FAQ for detailed " "instructions). If you have such optical installation media, and they are " "bootable on your machine, which is the case on all " "modern PCs, you can skip right to . Much effort has been expended to ensure the most-used files are on the " "first CD and DVD image, so that a basic desktop installation can be done " "with only the first DVD or - to a limited extent - even with only the first " "CD image." msgstr "" "目前安裝 &debian-gnu; 最容易的方法是使用一個官方的 &debian;光碟套件。您可以向" "零售商購買 (參閱 光碟零售商)。" "如果您有快速的網路連接和光碟燒錄機的話,也可以從 &debian; 鏡像站下載光碟映像" "檔然後自行燒錄光碟 (具體參閱 Debian 光碟網頁)。如果您有一套 &debian; 的光碟套件並且能在您的機器上開機這些光碟,您可" "以直接跳至 。我們已經做了很多努力來確保光碟" "中已經包含了大多數人所需要的文件。儘管一整套預先編譯的二進位軟體套件需要好幾" "張光碟,但是您可能不會用到第三張光碟以後的內容。您也可以可以考慮使用 DVD 版" "本,這將為您的書架節省很多光碟存放空間,並且您可以避免馬拉松式的光碟換片動" "作。" #. Tag: para #: install-methods.xml:30 #, no-c-format msgid "" "As CDs have a rather limited capacity by today's standards, not all " "graphical desktop environments are installable with only the first CD; for " "some desktop environments a CD installation requires either network " "connectivity during the installation to download the remaining files or " "additional CDs." msgstr "" #. Tag: para #: install-methods.xml:38 #, no-c-format msgid "" "Also, keep in mind: if the installation media you are using don't contain " "some packages you need, you can always install those packages afterwards " "from your running new Debian system (after the installation has finished). " "If you need to know on which installation image to find a specific package, " "visit https://cdimage-" "search.debian.org/." msgstr "" #. Tag: para #: install-methods.xml:46 #, fuzzy, no-c-format #| msgid "" #| "If your machine doesn't support CD booting, but you do have a CD set, you " #| "can use an alternative strategy such as floppy disk, tape, emulated " #| "tape, hard disk, " #| "usb stick, net boot, or manually loading the kernel from " #| "the CD to initially boot the system installer. The files you need for " #| "booting by another means are also on the CD; the &debian; network archive " #| "and CD folder organization are identical. So when archive file paths are " #| "given below for particular files you need for booting, look for those " #| "files in the same directories and subdirectories on your CD." msgid "" "If your machine doesn't support booting from optical media (only relevant on very old PC systems), but you do have a " "set of CD/DVD, you can use an alternative strategy such as VM reader, hard disk, usb stick, net boot, or manually loading the " "kernel from the disc to initially boot the system installer. The files you " "need for booting by another means are also on the disc; the &debian; network " "archive and folder organization on the disc are identical. So when archive " "file paths are given below for particular files you need for booting, look " "for those files in the same directories and subdirectories on your " "installation media." msgstr "" "如果您的機器不支援光碟開機,但是您有一套光碟套件,您可以使用其他的方法例如: " "軟碟、 磁帶、磁帶仿真、 硬碟、" " USB 隨身碟、 網路開機, 或者從光碟中手動載入核心來初" "始系統安裝程式。透過其他方法開機所需要的文件都包含在光碟之中;&debian; 的網路" "存檔和光碟的目錄組織方式是一致的。因此如果後文中有出現用於開機的特定檔案路徑" "時,請在光碟中同樣的目錄和子目錄下查找它們。" #. Tag: para #: install-methods.xml:67 #, fuzzy, no-c-format #| msgid "" #| "Once the installer is booted, it will be able to obtain all the other " #| "files it needs from the CD." msgid "" "Once the installer is booted, it will be able to obtain all the other files " "it needs from the disc." msgstr "安裝程式啟動一旦啟動,它將能夠取得光碟中其他所有必需的檔案。" #. Tag: para #: install-methods.xml:72 #, fuzzy, no-c-format #| msgid "" #| "If you don't have a CD set, then you will need to download the installer " #| "system files and place them on the installation " #| "tape floppy disk or hard disk or usb stick or a connected computer so they can be used to " #| "boot the installer." msgid "" "If you don't have an installation media set, then you will need to download " "the installer system files and place them on the VM " "minidisk hard disk or " "usb stick or a connected computer so they can be used to boot " "the installer." msgstr "" "如果您沒有光碟套件,則需下載安裝系統檔案並且把他們放到:安裝磁帶 軟碟、" " 硬碟、 USB 隨身碟或 一台有連接網路的電腦上,他們可以用來啟動安裝程式。" #. Tag: title #: install-methods.xml:96 #, no-c-format msgid "Downloading Files from &debian; Mirrors" msgstr "從 &debian; 鏡像伺服器下載檔案" #. Tag: para #: install-methods.xml:98 #, no-c-format msgid "" "To find the nearest (and thus probably the fastest) mirror, see the list of &debian; mirrors." msgstr "" "選擇離您較近的 (因此很可能也是最快的) 鏡像伺服器,請參閱 &debian; 鏡像列表。" #. Tag: title #: install-methods.xml:106 #, fuzzy, no-c-format #| msgid "Where to Find Installation Images" msgid "Where to Find Installation Files" msgstr "哪裡能找到安裝映像檔" #. Tag: para #: install-methods.xml:108 #, fuzzy, no-c-format #| msgid "" #| "The installation images are located on each &debian; mirror in the " #| "directory debian/dists/" #| "&releasename;/main/installer-&architecture;/current/images/ " #| "— the MANIFEST lists each image and its purpose." msgid "" "Various installation files can be found on each &debian; mirror in the " "directory debian/dists/" "&releasename;/main/installer-&architecture;/current/images/ — " "the MANIFEST " "lists each image and its purpose." msgstr "" "安裝映像檔位於每一個 &debian; 鏡像站的 debian/dists/&releasename;/main/installer-&architecture;/current/" "images/MANIFEST 文件列出每個映像檔及其用途。" #. Tag: title #: install-methods.xml:120 #, fuzzy, no-c-format #| msgid "RiscPC Installation Files" msgid "Kurobox Pro Installation Files" msgstr "RiscPC 的安裝檔案" #. Tag: para #: install-methods.xml:121 #, no-c-format msgid "" "The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the " "disk on which you intend to install &debian;. These images can be obtained " "from &kuroboxpro-firmware-img;." msgstr "" #. Tag: title #: install-methods.xml:131 #, fuzzy, no-c-format msgid "HP mv2120 Installation Files" msgstr "CATS 的安裝檔案" #. Tag: para #: install-methods.xml:132 #, no-c-format msgid "" "A firmware image is provided for the HP mv2120 which will automatically boot " "debian-installer. This image can be installed with " "uphpmvault on Linux and other systems and with the HP Media Vault Firmware " "Recovery Utility on Windows. The firmware image can be obtained from &mv2120-" "firmware-img;." msgstr "" #. Tag: title #: install-methods.xml:144 #, fuzzy, no-c-format #| msgid "CATS Installation Files" msgid "QNAP Turbo Station Installation Files" msgstr "CATS 的安裝檔案" #. Tag: para #: install-methods.xml:145 #, no-c-format msgid "" "The installation files for the QNAP Turbo Station consist of a kernel and " "ramdisk as well as a script to write these images to flash. You can obtain " "the installation files for QNAP TS-11x/TS-12x, HS-210, TS-21x/TS-22x and " "TS-41x/TS-42x models from &qnap-kirkwood-firmware-img;." msgstr "" #. Tag: title #: install-methods.xml:156 #, fuzzy, no-c-format msgid "Plug Computer and OpenRD Installation Files" msgstr "NetWinder 的安裝檔案" #. Tag: para #: install-methods.xml:157 #, no-c-format msgid "" "The installation files for plug computers (SheevaPlug, GuruPlug, DreamPlug " "etc) and OpenRD devices consist of a kernel and initrd for U-Boot. You can " "obtain these files from &kirkwood-marvell-firmware-img;." msgstr "" #. Tag: title #: install-methods.xml:167 #, fuzzy, no-c-format #| msgid "CATS Installation Files" msgid "LaCie NASes Installation Files" msgstr "CATS 的安裝檔案" #. Tag: para #: install-methods.xml:168 #, no-c-format msgid "" "The installation files for LaCie NASes (Network Space v2, Network Space Max " "v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2) " "consist of a kernel and initrd for U-Boot. You can obtain these files from " "&lacie-kirkwood-firmware-img;." msgstr "" #. Tag: title #: install-methods.xml:179 #, fuzzy, no-c-format #| msgid "Alpha Installation Files" msgid "Armhf Multiplatform Installation Files" msgstr "Alpha 的安裝檔案" #. Tag: para #: install-methods.xml:180 #, no-c-format msgid "" "The installation files for systems supported by the armhf multiplatform " "kernel (see ) consist of " "a standard Linux kernel image, a standard Linux initial ramdisk image and a " "system-specific device-tree blob. The kernel and the initial ramdisk image " "for tftp-booting can be obtained from &armmp-firmware-img; and the device-" "tree blob can be obtained from &armmp-dtb-img;. The tar archive for creating " "a bootable USB stick with the installer can be obtained from &armmp-hd-media-" "tarball;." msgstr "" #. Tag: para #: install-methods.xml:192 #, no-c-format msgid "" "U-boot images for various armhf platforms are available at &armmp-uboot-img;." msgstr "" #. Tag: title #: install-methods.xml:238 #, no-c-format msgid "Preparing Files for USB Memory Stick Booting" msgstr "準備從 USB 隨身碟開機的檔案" #. Tag: para #: install-methods.xml:240 #, fuzzy, no-c-format msgid "" "To prepare the USB stick, we recommend to use a system where GNU/Linux is " "already running and where USB is supported. With current GNU/Linux systems " "the USB stick should be automatically recognized when you insert it. If it " "is not you should check that the usb-storage kernel module is loaded. When " "the USB stick is inserted, it will be mapped to a device named /" "dev/sdX, where the X is a letter in the range a-z. " "You should be able to see to which device the USB stick was mapped by " "running the command lsblk before and after inserting it. " "(The output of dmesg (as root) is another possible method " "for that.) To write to your stick, you may have to turn off its write " "protection switch." msgstr "" "您需要一台運行支援 USB 的 GNU/Linux 系統來為 USB 隨身碟準備開機檔案。 您應該" "確定 usb-storage 核心模組已經被載入 (modprobe usb-storage) 然後嘗試找出 USB 隨身碟被映射到的哪個 SCSI 設備 (在此以 " "/dev/sda 為例)。為了寫入您的儲存,您可能需要關閉它的防寫" "保護開關。" #. Tag: para #: install-methods.xml:255 #, no-c-format msgid "" "The procedures described in this section will destroy anything already on " "the device! Make very sure that you use the correct device name for your USB " "stick. If you use the wrong device the result could be that all information " "on, for example, a hard disk is lost." msgstr "" #. Tag: title #: install-methods.xml:265 #, no-c-format msgid "Preparing a USB stick using a hybrid CD/DVD image" msgstr "" #. Tag: para #: install-methods.xml:266 #, no-c-format msgid "" "Debian installation images for this architecture are created using the " "isohybrid technology; that means they can be written " "directly to a USB stick, which is a very easy way to make an installation " "media. Simply choose an image (such as the netinst, CD or DVD-1) that will " "fit on your USB stick. See to get an " "installation image." msgstr "" #. Tag: para #: install-methods.xml:276 #, no-c-format msgid "" "The installation image you choose should be written directly to the USB " "stick, overwriting its current contents. For example, when using an existing " "GNU/Linux system, the image file can be written to a USB stick as follows, " "after having made sure that the stick is unmounted: " "\n" "# cp debian.iso /dev/" "sdX\n" "# sync\n" " Simply writing the installation image to USB " "like this should work fine for most users. For special needs there is this " "wiki " "page." msgstr "" #. Tag: para #: install-methods.xml:289 #, no-c-format msgid "" "Information about how to do this on other operating systems can be found in " "the Debian CD FAQ." msgstr "" #. Tag: para #: install-methods.xml:294 #, no-c-format msgid "" "The image must be written to the whole-disk device and not a partition, e." "g. /dev/sdb and not /dev/sdb1. Do not use tools like unetbootin which alter the image." msgstr "" #. Tag: title #: install-methods.xml:311 #, no-c-format msgid "Preparing Files for Hard Disk Booting" msgstr "準備從硬碟開機的檔案" #. Tag: para #: install-methods.xml:312 #, fuzzy, no-c-format #| msgid "" #| "The installer may be booted using boot files placed on an existing hard " #| "drive partition, either launched from another operating system or by " #| "invoking a boot loader directly from the BIOS." msgid "" "The installer may be booted using boot files placed on an existing hard " "drive partition, either launched from another operating system or by " "invoking a boot loader directly from the BIOS. On modern UEFI systems, the " "kernel may be booted directly from the UEFI partition without the need of a " "boot loader." msgstr "" "安裝程式可以從硬碟分割區上面用開機文件開機。它們可以在其它作業系統下面啟動," "或者直接使用 BIOS 提供的 boot-loader 直接啟動。" #. Tag: para #: install-methods.xml:320 #, fuzzy, no-c-format #| msgid "" #| "A full, pure network installation can be achieved using " #| "this technique. This avoids all hassles of removable media, like finding " #| "and burning CD images or struggling with too numerous and unreliable " #| "floppy disks." msgid "" "A full, pure network installation can be achieved using this " "technique. This avoids all hassles of removable media, like finding and " "burning CD/DVD images." msgstr "" "採用這個技術可以實現完全的純網路的安裝方式。這樣可以避免一些使" "用可移動媒介帶來的的缺點,例如尋找和燒錄光碟映像或是與大量且不可靠的軟碟糾纏" "不清。" #. Tag: title #: install-methods.xml:350 #, fuzzy, no-c-format #| msgid "" #| "Hard disk installer booting using LILO or " #| "GRUB" msgid "Hard disk installer booting from Linux using GRUB" msgstr "" "使用 LILOGRUB啟動硬碟安裝程式" #. Tag: para #: install-methods.xml:352 #, fuzzy, no-c-format #| msgid "" #| "This section explains how to add to or even replace an existing linux " #| "installation using either LILO or GRUB." msgid "" "This section explains how to add to or even replace an existing linux " "installation using GRUB." msgstr "" "這一節將解釋如何透過 LILOGRUB 增加" "或者甚至替換現有的 linux 安裝。" #. Tag: para #: install-methods.xml:358 #, fuzzy, no-c-format #| msgid "" #| "At boot time, both bootloaders support loading in memory not only the " #| "kernel, but also a disk image. This RAM disk can be used as the root file-" #| "system by the kernel." msgid "" "At boot time, GRUB supports loading in memory not only " "the kernel, but also a disk image. This RAM disk can be used as the root " "file-system by the kernel." msgstr "" "在開機時,兩種 boot-loader 都支援將核心和磁碟映像掛載到記憶體中。這個記憶體虛" "擬磁碟可以被用做核心的根檔案系統。" #. Tag: para #: install-methods.xml:364 #, fuzzy, no-c-format #| msgid "" #| "Copy the following files from the Debian archives to a convenient " #| "location on your hard drive, for instance to /boot/newinstall/." msgid "" "Copy the following files from the &debian; archives to a convenient location " "on your hard drive, for instance to /boot/newinstall/." msgstr "" "將以下檔案從 &debian; 檔案庫中拷貝到硬碟中比較方便的地方,例如 /" "boot/newinstall/。" #. Tag: para #: install-methods.xml:371 #, no-c-format msgid "vmlinuz (kernel binary)" msgstr "vmlinuz(核心二進位文件)" #. Tag: para #: install-methods.xml:376 #, no-c-format msgid "initrd.gz (ramdisk image)" msgstr "initrd.gz (記憶體虛擬磁碟映像)" #. Tag: para #: install-methods.xml:383 #, fuzzy, no-c-format msgid "" "If you intend to use the hard drive only for booting and then download " "everything over the network, you should download the &x86-netboot-initrd; " "file and its corresponding kernel &x86-netboot-linux;. This will allow you " "to repartition the hard disk from which you boot the installer, although you " "should do so with care." msgstr "" "如果您只想用硬碟開機,然後從網路下載其他檔案,您需要下載 &x86-netboot-" "initrd; 及其對應的核心。這將允許您重新分割您用於開機的硬碟。這裡需要小心操" "作。" #. Tag: para #: install-methods.xml:392 #, fuzzy, no-c-format msgid "" "Alternatively, if you intend to keep an existing partition on the hard drive " "unchanged during the install, you can download the &x86-hdmedia-initrd; file " "and its kernel &x86-hdmedia-vmlinuz;, as well as copy an installation image " "to the hard drive (make sure the file is named ending in .iso). The installer can then boot from the hard drive and install from " "the installation image, without needing the network." msgstr "" "或者,如果您想要保持安裝硬碟原有分割區,可以下載 &x86-hdmedia-initrd; 檔案及" "其核心,複製一個光碟 iso 檔到硬碟上 (確保文件名結尾是 .iso)。安裝程式就可以不使用網路而從硬碟開機,並且從光碟映像檔上安裝。" #. Tag: para #: install-methods.xml:400 #, no-c-format msgid "" "Finally, to configure the bootloader proceed to ." msgstr "最後,要設定 boot-loader,請進入 。" #. Tag: title #: install-methods.xml:415 #, no-c-format msgid "Preparing Files for TFTP Net Booting" msgstr "準備以 TFTP 網路開機用的檔案" #. Tag: para #: install-methods.xml:416 #, no-c-format msgid "" "If your machine is connected to a local area network, you may be able to " "boot it over the network from another machine, using TFTP. If you intend to " "boot the installation system from another machine, the boot files will need " "to be placed in specific locations on that machine, and the machine " "configured to support booting of your specific machine." msgstr "" "如果您的機器連接到了一個區域網路,您可以從網路上的另外一台機器上面透過 TFTP " "來開機。如果您傾向從另外一台機器上面啟動安裝系統,則開機檔案需要放在那台機器" "上面的某個特殊地方,並且設定您的機器從該機器進行開機。" #. Tag: para #: install-methods.xml:424 #, fuzzy, no-c-format msgid "" "You need to set up a TFTP server, and for many machines a DHCP server, or RARP server, or BOOTP server." msgstr "" "您需要設置一台 TFTP 伺服器,對於很多機器來說,還需要一台 BOOTP 伺服器 " ",或 RARP 伺服器 ,又或 DHCP 伺服器。" #. Tag: para #: install-methods.xml:431 #, fuzzy, no-c-format msgid "" "The Reverse Address Resolution Protocol " "(RARP) is one way to tell your client what IP address to use for itself. " "Another way is to use the BOOTP protocol. BOOTP is an IP protocol that informs a computer of its IP " "address and where on the network to obtain a boot image. The DHCP " "(Dynamic Host Configuration Protocol) is a more flexible, backwards-" "compatible extension of BOOTP. Some systems can only be configured via DHCP." msgstr "" "反向位址解析協議 (The Reverse Address " "Resolution Protocol, RARP) 是一種告訴您的客戶它自己 IP 位址的方法。另外一種方" "法是 BOOTP 通訊協定。 BOOTP 是" "一種 IP 通訊協定,用來告訴電腦它自己的 IP 位址以及從網路何處取得啟動映像。 DHCP (動態主機設定協定 Dynamic " "Host Configuration Protocol) 是一個更靈活,向後相容的 BOOTP 延伸。有一些系統" "只能透過 DHCP 來配置。" #. Tag: para #: install-methods.xml:457 #, no-c-format msgid "" "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to " "the client. Theoretically, any server, on any platform, which implements " "these protocols, may be used. In the examples in this section, we shall " "provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux." msgstr "" "普通檔案傳輸協定 (Trivial File Transfer Protocol, TFTP) 能為客戶端提供開機映" "像。理論上,任何伺服器,在任何平台上只要實做這些協定就都能夠被應用。在這一節" "的一些例子裡面,我們將提供在 SunOS 4.x、SunOS 5.x (即 Solaris) 和 GNU/Linux " "上面的一些操作例子。" #. Tag: para #: install-methods.xml:465 #, no-c-format msgid "" "For a &debian-gnu; server we recommend tftpd-hpa. " "It's written by the same author as the syslinux " "bootloader and is therefore least likely to cause issues. A good alternative " "is atftpd." msgstr "" #. Tag: title #: install-methods.xml:481 #, no-c-format msgid "Setting up RARP server" msgstr "設置 RARP 伺服器" #. Tag: para #: install-methods.xml:482 #, fuzzy, no-c-format #| msgid "" #| "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC " #| "address) of the client computers to be installed. If you don't know this " #| "information, you can pick it off the initial " #| "OpenPROM boot messages, use the OpenBoot .enet-addr command, or boot into Rescue mode (e." #| "g., from the rescue floppy) and use the command ip addr show " #| "dev eth0." msgid "" "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC " "address) of the client computers to be installed. If you don't know this " "information, you can boot into Rescue mode and use the " "command ip addr show dev eth0." msgstr "" "為了設置 RARP ,您需要知道欲安裝系統的客戶端的以太網卡位址 (網卡 MAC 位址)。 " "如果您還不知道這個資訊,可以從 OpenPROM 的初始化開機資" "訊中取得,請使用 OpenBoot .enet-addr 指令,或者開機進入 Rescue 模式 (例如使用回復軟碟) 並且使用 " "ip addr show dev eth0 指令。" #. Tag: para #: install-methods.xml:491 #, fuzzy, no-c-format msgid "" "On a RARP server system using a Linux kernel or Solaris/SunOS, you use the " "rarpd program. You need to ensure that the Ethernet " "hardware address for the client is listed in the ethers " "database (either in the /etc/ethers file, or via NIS/NIS" "+) and in the hosts database. Then you need to start the RARP " "daemon. Issue the command (as root): /usr/sbin/rarpd -a on most Linux systems and SunOS 5 (Solaris 2), /usr/" "sbin/in.rarpd -a on some other Linux systems, or /usr/" "etc/rarpd -a in SunOS 4 (Solaris 1)." msgstr "" "在 SunOS 裡, 您需要確定客戶端的以太網硬體位址已經列在 ethers " "資料庫(在 /etc/ethers 檔案中或者透過 NIS/NIS+)和 " "``hosts'' 資料庫中,然後您需要啟動 RARP 伺服程式,在 SunOS 4 裡,使用(以 " "root 身份): /usr/etc/rarpd -a 指令﹔在 SunOS 5 裡,則" "使用 /usr/sbin/rarpd -a 指令。" #. Tag: title #: install-methods.xml:512 #, no-c-format msgid "Setting up a DHCP server" msgstr "設置 DHCP 伺服器" #. Tag: para #: install-methods.xml:513 #, no-c-format msgid "" "One free software DHCP server is ISC dhcpd. For &debian-" "gnu;, the isc-dhcp-server package is recommended. " "Here is a sample configuration file for it (see /etc/dhcp/dhcpd." "conf):" msgstr "" #. Tag: screen #: install-methods.xml:520 #, fuzzy, no-c-format msgid "" "option domain-name \"example.com\";\n" "option domain-name-servers ns1.example.com;\n" "option subnet-mask 255.255.255.0;\n" "default-lease-time 600;\n" "max-lease-time 7200;\n" "server-name \"servername\";\n" "\n" "subnet 192.168.1.0 netmask 255.255.255.0 {\n" " range 192.168.1.200 192.168.1.253;\n" " option routers 192.168.1.1;\n" "}\n" "\n" "host clientname {\n" " filename \"/tftpboot.img\";\n" " server-name \"servername\";\n" " next-server servername;\n" " hardware ethernet 01:23:45:67:89:AB;\n" " fixed-address 192.168.1.90;\n" "}" msgstr "" "ISC dhcpd 是一種自由軟體 DHCP 伺服器。在 &debian-gnu; 裡," "它被包含在 dhcp 軟體套件中。這裡有它的一個設定檔的範例" "(通常是 /etc/dhcpd.conf):\n" "option domain-name \"example.com\";\n" "option domain-name-servers ns1.example.com;\n" "option subnet-mask 255.255.255.0;\n" "default-lease-time 600;\n" "max-lease-time 7200;\n" "server-name \"servername\";\n" "\n" "subnet 192.168.1.0 netmask 255.255.255.0 {\n" " range 192.168.1.200 192.168.1.253;\n" " option routers 192.168.1.1;\n" "}\n" "\n" "host clientname {\n" " filename \"/tftpboot.img\";\n" " server-name \"servername\";\n" " next-server servername;\n" " hardware ethernet 01:23:45:67:89:AB; \n" " fixed-address 192.168.1.90;\n" "}\n" " 註:新的(並且是建議的) dhcp3 軟體套件使用 /etc/dhcp/dhcpd.conf作為其設定" "檔。" #. Tag: para #: install-methods.xml:522 #, no-c-format msgid "" "In this example, there is one server servername " "which performs all of the work of DHCP server, TFTP server, and network " "gateway. You will almost certainly need to change the domain-name options, " "as well as the server name and client hardware address. The " "filename option should be the name of the file " "which will be retrieved via TFTP." msgstr "" "在這個例子中,一台伺服器 servername 負責執行包括 " "DHCP 伺服器、TFTP 伺服器和閘道器在內的所有工作。您需要修改網域名稱選項,以及" "伺服器名稱和客戶端硬體位址。filename 選項應是要從 " "TFTP 取得的檔案名稱。" #. Tag: para #: install-methods.xml:532 #, fuzzy, no-c-format msgid "" "After you have edited the dhcpd configuration file, " "restart it with /etc/init.d/isc-dhcp-server restart." msgstr "" "在編輯了 dhcpd 設定檔後,您需要使用下面的指令重新啟動它:" "/etc/init.d/dhcpd restart。" #. Tag: title #: install-methods.xml:540 #, no-c-format msgid "Enabling PXE Booting in the DHCP configuration" msgstr "在 DHCP 設定中打開 PXE 開機功能" #. Tag: para #: install-methods.xml:541 #, fuzzy, no-c-format msgid "" "Here is another example for a dhcp.conf using the Pre-" "boot Execution Environment (PXE) method of TFTP. \n" "option domain-name \"example.com\";\n" "\n" "default-lease-time 600;\n" "max-lease-time 7200;\n" "\n" "allow booting;\n" "allow bootp;\n" "\n" "# The next paragraph needs to be modified to fit your case\n" "subnet 192.168.1.0 netmask 255.255.255.0 {\n" " range 192.168.1.200 192.168.1.253;\n" " option broadcast-address 192.168.1.255;\n" "# the gateway address which can be different\n" "# (access to the internet for instance)\n" " option routers 192.168.1.1;\n" "# indicate the dns you want to use\n" " option domain-name-servers 192.168.1.3;\n" "}\n" "\n" "group {\n" " next-server 192.168.1.3;\n" " host tftpclient {\n" "# tftp client hardware address\n" " hardware ethernet 00:10:DC:27:6C:15;\n" " filename \"pxelinux.0\";\n" " }\n" "}\n" " Note that for PXE booting, the client filename " "pxelinux.0 is a boot loader, not a kernel image (see " " below)." msgstr "" "這是另外一個採用 TFTP Pre-boot Execution Environment (PXE) 方法的 " "dhcp.conf 配置範例。\n" "\n" "option domain-name \"example.com\";\n" "\n" "default-lease-time 600;\n" "max-lease-time 7200;\n" "\n" "allow booting;\n" "allow bootp;\n" "\n" "# 接下來的片段需要您自己修改成你所需要的\n" "subnet 192.168.1.0 netmask 255.255.255.0 {\n" " range 192.168.1.200 192.168.1.253;\n" " option subnet-mask 255.255.255.0;\n" " option broadcast-address 192.168.1.255;\n" "# 閘道的位址可以不一樣\n" "# (例如連到網際網路)\n" " option routers 192.168.1.1;\n" "# 設定您要使用的DNS\n" " option domain-name-servers 192.168.1.3;\n" "}\n" "\n" "group {\n" " next-server 192.168.1.3;\n" " host tftpclient {\n" "# tftp 客戶端的硬體位址\n" " hardware ethernet 00:10:DC:27:6C:15;\n" " filename \"pxelinux.0\";\n" " }\n" "}\n" " 注意對於 PXE 開機來說,客戶端檔案名 " "pxelinux.0 是一個 boot-loader,而非一個核心映像 (參閱下" "面的 )。" #. Tag: para #: install-methods.xml:551 #, no-c-format msgid "" "If your machine uses UEFI to boot, you will have to specify a boot loader " "appropriate for UEFI machines, for example" msgstr "" #. Tag: screen #: install-methods.xml:555 #, no-c-format msgid "" "group {\n" " next-server 192.168.1.3;\n" " host tftpclient {\n" "# tftp client hardware address\n" " hardware ethernet 00:10:DC:27:6C:15;\n" " filename \"debian-installer/amd64/bootnetx64.efi\";\n" " }\n" "}" msgstr "" #. Tag: title #: install-methods.xml:568 #, fuzzy, no-c-format msgid "Setting up a BOOTP server" msgstr "設置 BOOTP 伺服器" #. Tag: para #: install-methods.xml:569 #, fuzzy, no-c-format msgid "" "There are two BOOTP servers available for GNU/Linux. The first is CMU " "bootpd. The other is actually a DHCP server: ISC " "dhcpd. In &debian-gnu; these are contained in the " "bootp and isc-dhcp-server " "packages respectively." msgstr "" "在 GNU/Linux 下面有兩種 BOOTP 伺服器。他們是 CMU bootpd 和" "另外一種實際上是 DHCP 伺服器的程式 ISC dhcpd,他們被包含" "在 &debian-gnu; 的 bootpdhcp 軟體套件中。" #. Tag: para #: install-methods.xml:577 #, fuzzy, no-c-format msgid "" "To use CMU bootpd, you must first uncomment (or add) the " "relevant line in /etc/inetd.conf. On &debian-gnu;, you " "can run update-inetd --enable bootps, then " "/etc/init.d/inetd reload to do so. Just in case your " "BOOTP server does not run &debian;, the line in question should look like: " "\n" "bootps dgram udp wait root /usr/sbin/bootpd bootpd -i -t 120\n" " Now, you must create an /etc/bootptab file. This has the same sort of familiar and cryptic format as the " "good old BSD printcap, termcap, " "and disktab files. See the bootptab manual page for more information. For CMU bootpd, you will need to know the hardware (MAC) address of the client. " "Here is an example /etc/bootptab: " "\n" "client:\\\n" " hd=/tftpboot:\\\n" " bf=tftpboot.img:\\\n" " ip=192.168.1.90:\\\n" " sm=255.255.255.0:\\\n" " sa=192.168.1.1:\\\n" " ha=0123456789AB:\n" " You will need to change at least the ha option, which specifies the hardware address of the client. The " "bf option specifies the file a client should retrieve via " "TFTP; see for more details." msgstr "" "要使用 CMU bootpd,您必須先將 /etc/inetd.conf 中相關的註釋標記去掉 (或者加入一些新行)。在 &debian-gnu; 裡,您可以" "執行 update-inetd --enable bootps,然後執行 " "/etc/init.d/inetd reload 來完成此工作。在其它系統中," "這行設定應該看起來像這樣:\n" "bootps dgram udp wait root /usr/sbin/bootpd bootpd -i -t 120\n" " 現在,您必須建立一個 /etc/bootptab 檔案。它具有和一些老 BSD 檔案相似並使用相同的加密格式。這些檔案包" "括 printcaptermcap,和 " "disktab。請參閱 bootptab 的手冊以獲" "得更多的資訊。對於 CMU bootpd,您將需要知道客戶端硬的體 " "(MAC) 位址。這裡有一個範例 /etc/bootptab: " "\n" "client:\\\\n hd=/tftpboot:\\\\n bf=tftpboot.img:\\\\n ip=192.168.1.90:\\" "\\n sm=255.255.255.0:\\\\n sa=192.168.1.1:\\\\n ha=0123456789AB:\n" " 您至少需要修改 ha 選項,它指定了客" "戶端的硬體地址。bf 選項則指定了一個客戶端應該透過 TFTP 取得的" "檔案名稱。請從 處取得更多的資訊。 在 SGI Indys 上,您可以僅僅只是進入指令監視器然後輸入 " "printenveaddr 的值就是機器" "的 MAC 位址。 " #. Tag: para #: install-methods.xml:604 #, fuzzy, no-c-format msgid "" "By contrast, setting up BOOTP with ISC dhcpd is really " "easy, because it treats BOOTP clients as a moderately special case of DHCP " "clients. Some architectures require a complex configuration for booting " "clients via BOOTP. If yours is one of those, read the section . Otherwise you will probably be able to get away with simply " "adding the allow bootp directive to the configuration " "block for the subnet containing the client in /etc/dhcp/dhcpd." "conf, and restart dhcpd with /etc/" "init.d/isc-dhcp-server restart." msgstr "" "透過 ISC dhcpd 設定 BOOTP 反而非常容易。因為它把 BOOTP 客" "戶端程式看成一個特殊的 DHCP 客戶端。部分架構結構需要經過複雜的設定才能從 " "BOOTP 啟動客戶端。如果您的機器屬於這種情況,請閱讀 。否則,您大概只需要將 allow bootp 指令添加到包含客戶" "機的子網域的配定部分,並重新啟動 dhcpd 就可以了,重啟的指" "令是:/etc/init.d/dhcpd restart。" #. Tag: title #: install-methods.xml:623 #, no-c-format msgid "Enabling the TFTP Server" msgstr "啟用 TFTP 伺服器" #. Tag: para #: install-methods.xml:624 #, no-c-format msgid "" "To get the TFTP server ready to go, you should first make sure that " "tftpd is enabled." msgstr "" #. Tag: para #: install-methods.xml:629 #, no-c-format msgid "" "In the case of tftpd-hpa there are two ways the " "service can be run. It can be started on demand by the system's " "inetd daemon, or it can be set up to run as an " "independent daemon. Which of these methods is used is selected when the " "package is installed and can be changed by reconfiguring the package." msgstr "" #. Tag: para #: install-methods.xml:638 #, no-c-format msgid "" "Historically, TFTP servers used /tftpboot as directory " "to serve images from. However, &debian-gnu; packages may use other " "directories to comply with the Filesystem " "Hierarchy Standard. For example, tftpd-hpa by " "default uses /srv/tftp. You may have to adjust the " "configuration examples in this section accordingly." msgstr "" #. Tag: para #: install-methods.xml:648 #, no-c-format msgid "" "All in.tftpd alternatives available in &debian; should " "log TFTP requests to the system logs by default. Some of them support a " "-v argument to increase verbosity. It is recommended " "to check these log messages in case of boot problems as they are a good " "starting point for diagnosing the cause of errors." msgstr "" #. Tag: title #: install-methods.xml:660 #, no-c-format msgid "Move TFTP Images Into Place" msgstr "將 TFTP 映像放到適當的位置" #. Tag: para #: install-methods.xml:661 #, fuzzy, no-c-format msgid "" "Next, place the TFTP boot image you need, as found in , in the tftpd boot image directory. You may " "have to make a link from that file to the file which tftpd will use for booting a particular client. Unfortunately, the file " "name is determined by the TFTP client, and there are no strong standards." msgstr "" "接下來,將在 中找到的 TFTP 開機映像放到" "tftpd 開機映像目錄中。一般來說,這個目錄將是 /" "tftpboot。您必須將該檔案鏈結到 tftpd 用來啟動客" "戶端的檔案名稱。不幸的是,這個檔案名稱完全決定於 TFTP 客戶端程式,並且沒有一" "個強制的標準。" #. Tag: para #: install-methods.xml:712 #, fuzzy, no-c-format msgid "" "For PXE booting, everything you should need is set up in the " "netboot/netboot.tar.gz tarball. Simply extract this " "tarball into the tftpd boot image directory. Make sure " "your dhcp server is configured to pass pxelinux.0 to " "tftpd as the filename to boot. For UEFI machines, you " "will need to pass an appropriate EFI boot image name (such as /" "debian-installer/amd64/bootnetx64.efi)." msgstr "" "對於用 PXE 開機來說,您所需的只是設定 netboot/netboot.tar.gz 壓縮檔案。簡單地將此包解壓縮到 tftpd 開機映像目" "錄下。並確保您的 DHCP 伺服器的設定會把 pxelinux.0 以開機" "所需的檔案名傳遞至 tftpd。" #. Tag: title #: install-methods.xml:731 #, no-c-format msgid "Automatic Installation" msgstr "自動化安裝" #. Tag: para #: install-methods.xml:732 #, fuzzy, no-c-format #| msgid "" #| "For installing on multiple computers it's possible to do fully automatic " #| "installations. Debian packages intended for this include fai (which uses an install server), replicator, systemimager, autoinstall, and the Debian Installer itself." msgid "" "For installing on multiple computers it's possible to do fully automatic " "installations. &debian; packages intended for this include fai-" "quickstart, which can use an install server (have a look at the " "FAI home page for detailed " "information) and the &debian; Installer itself." msgstr "" "對於有多台電腦需要安裝的情況,可以採用全自動安裝的方式。用於此項工作的 " "&debian; 軟體套件有 fai (需要使用一台安裝伺服器), " "replicatorsystemimager、 " "autoinstall,以及 &debian; 安裝程式本身。" #. Tag: title #: install-methods.xml:744 #, no-c-format msgid "Automatic Installation Using the &debian; Installer" msgstr "使用 &debian; 安裝程式進行自動安裝" #. Tag: para #: install-methods.xml:745 #, fuzzy, no-c-format msgid "" "The &debian; Installer supports automating installs via preconfiguration " "files. A preconfiguration file can be loaded from the network or from " "removable media, and used to fill in answers to questions asked during the " "installation process." msgstr "" "&debian; 安裝程式支援透過預先設定檔進行自動安裝。一個預先設定檔可以從網路上或" "者可從移動媒介上載入,並且被用來在安裝過程中自動回答問題。" #. Tag: para #: install-methods.xml:752 #, fuzzy, no-c-format msgid "" "Full documentation on preseeding including a working example that you can " "edit is in ." msgstr "" "預先設定檔是按照 debconf-set-selections 指令的格式寫成的。這裡有一個具有詳盡" "註解並能正常工作的預先設定檔例子:。" #. Tag: title #: install-methods.xml:766 #, no-c-format msgid "Verifying the integrity of installation files" msgstr "" #. Tag: para #: install-methods.xml:768 #, no-c-format msgid "" "You can verify the integrity of downloaded files against checksums provided " "in SHA256SUMS or SHA512SUMS files " "on Debian mirrors. You can find them in the same places as the installation " "images itself. Visit the following locations:" msgstr "" #. Tag: para #: install-methods.xml:779 #, no-c-format msgid "" "checksum files for CD images," msgstr "" #. Tag: para #: install-methods.xml:785 #, no-c-format msgid "" "checksum files for DVD images," msgstr "" #. Tag: para #: install-methods.xml:791 #, no-c-format msgid "" "checksum files for BD images," msgstr "" #. Tag: para #: install-methods.xml:797 #, no-c-format msgid "" "checksum files for other " "installation files." msgstr "" #. Tag: para #: install-methods.xml:805 #, no-c-format msgid "" "To compute the checksum of a downloaded installation file, use " "\n" "sha256sum filename.iso\n" " respective \n" "sha512sum filename.iso\n" " and then compare the shown checksum against the " "corresponding one in the SHA256SUMS respective " "SHA512SUMS file." msgstr "" #. Tag: para #: install-methods.xml:818 #, no-c-format msgid "" "The Debian CD FAQ has more useful " "information on this topic (such as the script " "check_debian_iso, to semi-automate above procedure), as " "well as instructions, how to verify the integrity of the above checksum " "files themselves." msgstr "" #, fuzzy #~| msgid "Booting the USB stick" #~ msgid "Manually copying files to the USB stick" #~ msgstr "以 USB 隨身碟開機" #, fuzzy #~ msgid "" #~ "An alternative to the method described in is to manually copy the installer files, and also an " #~ "installation image to the stick. Note that the USB stick should be at " #~ "least 1 GB in size (smaller setups are possible using the files from " #~ "netboot, following )." #~ msgstr "" #~ "注意,USB 隨身碟應該至少有 128MB 的容量 (在更小的大小安裝也是可能的,請參" #~ "閱 )。" #, fuzzy #~ msgid "" #~ "There is an all-in-one file &hdmedia-boot-img; which contains all the " #~ "installer files (including the kernel) as well as " #~ "syslinux and its configuration file." #~ msgstr "" #~ "這裡有一個單一檔案 &hdmedia-boot-img;,其中包含了所有的安裝程式文件 (包括" #~ "核心),以及 syslinux 和它的設定檔案。您只需要把它直接解" #~ "壓縮到您的 USB 隨身碟內即可:\n" #~ "# zcat boot.img.gz > /dev/sda\n" #~ " 當然,這會刪除設備上現存的所有內容,因此請仔細" #~ "檢查您使用的是正確的 USB 隨身碟設備名稱。" #~ msgid "# zcat boot.img.gz > /dev/sdX" #~ msgstr "# zcat boot.img.gz > /dev/sdX" #, fuzzy #~ msgid "" #~ "After that, mount the USB memory stick (mount /dev/sdX /mnt), (mount /dev/" #~ "sdX2 /mnt), which will " #~ "now have a FAT filesystem an HFS filesystem on it, and copy a &debian; ISO " #~ "image (netinst or full CD; see ) to it. " #~ "Unmount the stick (umount /mnt) and you are done." #~ msgstr "" #~ "然後,掛載 USB 隨身碟 (mount /dev/" #~ "sda /dev/sda2 /" #~ "mnt),它上面應該已經具有一個 FAT 檔案系" #~ "統 一個 HFS 檔案系統,您再將一" #~ "個 &debian; netinst (網路安裝) 或 businesscard (名片型安裝) ISO 映像檔拷貝" #~ "到隨身碟上。請注意檔案名稱必須以 .iso 結尾。卸載隨身" #~ "碟 (umount /mnt) 後結束。" #, fuzzy #~| msgid "Copying the files — the flexible way" #~ msgid "Manually copying files to the USB stick — the flexible way" #~ msgstr "複製檔案 — 靈活的方法" #, fuzzy #~| msgid "" #~| "If you like more flexibility or just want to know what's going on, you " #~| "should use the following method to put the files on your stick." #~ msgid "" #~ "If you like more flexibility or just want to know what's going on, you " #~ "should use the following method to put the files on your stick. One " #~ "advantage of using this method is that — if the capacity of your " #~ "USB stick is large enough — you have the option of copying any ISO " #~ "image, even a DVD image, to it." #~ msgstr "" #~ "如果您需要更多的靈活性或者只是想瞭解其間發生了什麼,您應該使用下面的方法來" #~ "把檔案放到您的隨身碟上。" #~ msgid "" #~ "We will show how to set up the memory stick to use the first partition, " #~ "instead of the entire device." #~ msgstr "我們將展示如何使用隨身碟的第一個分割區,而不是整個設備。" #, fuzzy #~| msgid "" #~| "In order to start the kernel after booting from the USB stick, we will " #~| "put a boot loader on the stick. Although any boot loader (e.g. " #~| "lilo) should work, it's convenient to use " #~| "syslinux, since it uses a FAT16 partition and can " #~| "be reconfigured by just editing a text file. Any operating system which " #~| "supports the FAT file system can be used to make changes to the " #~| "configuration of the boot loader." #~ msgid "" #~ "In order to start the kernel after booting from the USB stick, we will " #~ "put a boot loader on the stick. Although any boot loader should work, " #~ "it's convenient to use syslinux, since it uses a " #~ "FAT16 partition and can be reconfigured by just editing a text file. Any " #~ "operating system which supports the FAT file system can be used to make " #~ "changes to the configuration of the boot loader." #~ msgstr "" #~ "為了能在 USB 隨身碟開機後啟動核心,我們要在 USB 隨身碟上放入一個 boot-" #~ "loader。儘管任何 boot-loader (例如 lilo) 都應該可以勝任" #~ "這個工作,不過還是使用 syslinux 更方便。主要原因是是它" #~ "可以使用 FAT16 分割區,而且只需要編輯一個文字檔案就能對其進行設定。任何支" #~ "援 FAT 檔案系統的操作系統可以用來改變 boot-loader 的設定檔案。" #, fuzzy #~ msgid "" #~ "Since most USB sticks come pre-configured with a single FAT16 partition, " #~ "you probably won't have to repartition or reformat the stick. If you have " #~ "to do that anyway, use cfdisk or any other " #~ "partitioning tool to create a FAT16 partition now Don't " #~ "forget to activate the bootable flag. , " #~ "and then install an MBR using: \n" #~ "# cat /usr/lib/syslinux/mbr/mbr.bin >/dev/sdX\n" #~ " Now create the filesystem using: " #~ "\n" #~ "# mkdosfs /dev/sdX1\n" #~ " Take care that you use the correct device " #~ "name for your USB stick. The mkdosfs command is " #~ "contained in the dosfstools &debian; package." #~ msgstr "" #~ "由於大多數 USB 隨身碟預先設置了一個單獨的 FAT16 分割區, 您可能不需要重新" #~ "分割或者格式化 USB 隨身碟。如果您必須這麼做,請使用 cfdisk 或者其他的分割工具來建立一個 FAT16 分割區並且輸入:" #~ "\n" #~ "# mkdosfs /dev/sda1\n" #~ " 注意使用正確的 USB 隨身碟設備名稱。 " #~ "mkdosfs 指令包含在 dosfstools " #~ "&debian; 套件中。" #, fuzzy #~| msgid "" #~| "To put syslinux on the FAT16 partition on your " #~| "USB stick, install the syslinux and " #~| "mtools packages on your system, and do: " #~| "\n" #~| "# syslinux /dev/sdX1\n" #~| " Again, take care that you use the correct " #~| "device name. The partition must not be mounted when starting " #~| "syslinux. This procedure writes a boot sector to the " #~| "partition and creates the file ldlinux.sys which " #~| "contains the boot loader code." #~ msgid "" #~ "Having a correctly partitioned USB stick (now), you need to put " #~ "syslinux on the FAT16 partition with: " #~ "\n" #~ "# syslinux /dev/sdX1\n" #~ " Again, take care that you use the correct " #~ "device name. The partition must not be mounted when starting " #~ "syslinux. This procedure writes a boot sector to the " #~ "partition and creates the file ldlinux.sys which " #~ "contains the boot loader code." #~ msgstr "" #~ "為了把 syslinux 放到您的 USB 隨身碟的 FAT16 分割區" #~ "上,請在您的系統中安裝 syslinux 和 " #~ "mtools 套件,然後執行:\n" #~ "# syslinux /dev/sdX1\n" #~ " 再提醒一次,請確認您使用的是正確的設備名稱。還" #~ "有,一定不能在啟動 syslinux 的時候掛載該分割區,因" #~ "為在操作過程中會向分割區的開機磁區寫入資料並且建立包含 boot-loader 代碼的 " #~ "ldlinux.sys 檔案。" #, fuzzy #~| msgid "Adding an ISO image" #~ msgid "Adding the installer files" #~ msgstr "添加 ISO 映像" #, fuzzy #~| msgid "" #~| "Mount the partition (mount /dev/sda1 /mnt) and " #~| "copy the following files from the Debian archives to the stick: " #~| " vmlinuz (kernel " #~| "binary) initrd.gz (initial ramdisk image) " #~| "syslinux.cfg (SYSLINUX configuration file) Optional kernel modules If you want to rename the files, please note that " #~| "SYSLINUX can only process DOS (8.3) file names." #~ msgid "" #~ "According to your choice, you have to download some installer files from " #~ "the hd-media or netboot subdirectory of debian/dists/&releasename;/main/installer-" #~ "&architecture;/current/images/ on any &debian; mirror: " #~ " vmlinuz or " #~ "linux (kernel binary) " #~ " initrd.gz (initial ramdisk image) You can choose between either the text-" #~ "based version of the installer (the files can be found directly in hd-" #~ "media or netboot) or the graphical version (look in the respective " #~ "gtk subdirectories)." #~ msgstr "" #~ "接下來就是掛載分割區 (mount /dev/sda1 /mnt) 以及將" #~ "下列檔案從 &debian; 檔案庫拷貝到儲存上: " #~ "vmlinuz (核心二進位檔案) " #~ " initrd.gz (初始化記憶體映像檔) syslinux.cfg " #~ "(SYSLINUX 設定檔案) 可選的核心模組 如果您想為這些檔名更名,請注意 " #~ "SYSLINUX 只能處理 DOS (8.3) 格式的檔案名稱。" #, fuzzy #~| msgid "" #~| "Mount the partition (mount /dev/sda2 /mnt) and " #~| "copy the following files from the Debian archives to the stick:" #~ msgid "" #~ "Then mount the partition (mount /dev/sdX1 /mnt) and copy the downloaded files to the root " #~ "directory of the stick." #~ msgstr "" #~ "接下來就是掛載分割區 (mount /dev/sda2 /mnt) 以及將" #~ "下列檔案從 &debian; 檔案庫拷貝到儲存上:" #, fuzzy #~ msgid "" #~ "Next you should create a text file named syslinux.cfg in the root directory of the stick as configuration file for " #~ "syslinux, which at a bare minimum should contain the following line: " #~ "\n" #~ "default vmlinuz initrd=initrd.gz\n" #~ " Change the name of the kernel binary to " #~ "linux if you used files from " #~ "netboot." #~ msgstr "" #~ "syslinux.cfg 設定檔案應該含有下列兩行: " #~ "\n" #~ "default vmlinuz initrd=initrd.gz ramdisk_size=12000 root=/dev/ram rw\n" #~ " 請注意,根據開機的映像大小,在必要的時候,您可" #~ "能需要增大 ramdisk_size 參數的數值。如果開機失敗,您可以嘗試添加 devfs=mount," #~ "dallappend 那一行。" #, fuzzy #~| msgid "" #~| "When you are done, unmount the USB memory stick (umount /mnt) and activate its write protection switch." #~ msgid "" #~ "When you are done, unmount the USB memory stick (umount /mnt)." #~ msgstr "" #~ "當您完成後,卸載 USB 隨身碟 (umount /mnt) 並打開防" #~ "寫保護。" #, fuzzy #~| msgid "" #~| "Hard disk installer booting using LILO or " #~| "GRUB" #~ msgid "" #~ "Hard disk installer booting from DOS using loadlin" #~ msgstr "" #~ "使用 LILOGRUB啟動硬碟安裝程式" #, fuzzy #~| msgid "" #~| "This section explains how to add to or even replace an existing linux " #~| "installation using either LILO or GRUB." #~ msgid "" #~ "This section explains how to prepare your hard drive for booting the " #~ "installer from DOS using loadlin." #~ msgstr "" #~ "這一節將解釋如何透過 LILOGRUB 增" #~ "加或者甚至替換現有的 linux 安裝。" #, fuzzy #~| msgid "" #~| "Copy the following files from the Debian archives to a convenient " #~| "location on your hard drive, for instance to /boot/newinstall/" #~| "." #~ msgid "" #~ "Copy the following directories from a &debian; installation image to " #~ "c:\\." #~ msgstr "" #~ "將以下檔案從 &debian; 檔案庫中拷貝到硬碟中比較方便的地方,例如 /" #~ "boot/newinstall/。" #, fuzzy #~| msgid "initrd.gz (initial ramdisk image)" #~ msgid "" #~ "/&x86-install-dir; (kernel binary and ramdisk image)" #~ msgstr "initrd.gz (初始化記憶體映像檔)" #, fuzzy #~| msgid "boot.msg (optional boot message)" #~ msgid "/tools (loadlin tool)" #~ msgstr "boot.msg (可選的啟動資訊)" #, fuzzy #~ msgid "" #~ "Create a partition of type \"Apple_Bootstrap\" on your USB stick using " #~ "mac-fdisk's C command and " #~ "extract the image directly to that:" #~ msgstr "" #~ "這裡有一個單一文件 hd-media/boot.img.gz ,其中包含了" #~ "所有的安裝程式文件(包括核心),以及 yaboot 和它的設定" #~ "檔。您可以使用 mac-fdiskC 指" #~ "令在您的 USB 隨身碟上建立一個類型為 ``Apple_Bootstrap'' 的分割區,然後直接" #~ "解開映像文件到: \n" #~ "# zcat boot.img.gz > /dev/sda2\n" #~ " 當然,這會刪除設備上現存的所有內容,因此請仔細" #~ "檢查您使用的是正確的 USB 隨身碟設備名稱。" #~ msgid "# zcat boot.img.gz > /dev/sdX2" #~ msgstr "# zcat boot.img.gz > /dev/sdX2" #, fuzzy #~| msgid "Booting the USB stick" #~ msgid "Partitioning the USB stick" #~ msgstr "以 USB 隨身碟開機" #~ msgid "" #~ "Most USB sticks do not come pre-configured in such a way that Open " #~ "Firmware can boot from them, so you will need to repartition the stick. " #~ "On Mac systems, run mac-fdisk /dev/sdX, initialise a new partition map using the " #~ "i command, and create a new partition of type " #~ "Apple_Bootstrap using the C command. (Note that " #~ "the first \"partition\" will always be the partition map itself.) Then " #~ "type \n" #~ "$ hformat /dev/sdX2\n" #~ " Take care that you use the correct device " #~ "name for your USB stick. The hformat command is " #~ "contained in the hfsutils &debian; package." #~ msgstr "" #~ "絕大多數 USB 隨身碟的預設設定都不能讓 Open Firmware 從該儲存進行開機,因此" #~ "您需要將儲存重新分割。在 Mac 系統上,執行 mac-fdisk /dev/" #~ "sdX,用 i 指" #~ "令初始化新的分割映射,然後使用 C 指令建立一個類型" #~ "為 Apple_Bootstrap 的新分割區。(要注意的是第一個分割區總是分割映射本身。) " #~ "然後鍵入 \n" #~ "$ hformat /dev/sdX2\n" #~ " 注意請使用正確的 USB 隨身碟設備名稱。 " #~ "hformat 指令包含在 hfsutils " #~ "&debian; 套件中。" #~ msgid "" #~ "In order to start the kernel after booting from the USB stick, we will " #~ "put a boot loader on the stick. The yaboot boot loader " #~ "can be installed on an HFS filesystem and can be reconfigured by just " #~ "editing a text file. Any operating system which supports the HFS file " #~ "system can be used to make changes to the configuration of the boot " #~ "loader." #~ msgstr "" #~ "為了能在 USB 隨身碟開機後啟動核心,我們要在 USB 隨身碟上放入一個 boot-" #~ "loader。yaboot boot-loader 可以被安裝到 HFS 檔案系統" #~ "上,而且只需要編輯一個純文字檔就能更改設定。任何支援 HFS 檔案系統的作業系" #~ "統可以用來改變 boot-loader 的設定檔。" #~ msgid "" #~ "The normal ybin tool that comes with yaboot does not yet understand USB storage devices, so you will have to " #~ "install yaboot by hand using the hfsutils tools. Type \n" #~ "$ hmount /dev/sdX2\n" #~ "$ hcopy -r /usr/lib/yaboot/yaboot :\n" #~ "$ hattrib -c UNIX -t tbxi :yaboot\n" #~ "$ hattrib -b :\n" #~ "$ humount\n" #~ " Again, take care that you use the correct " #~ "device name. The partition must not be otherwise mounted during this " #~ "procedure. This procedure writes the boot loader to the partition, and " #~ "uses the HFS utilities to mark it in such a way that Open Firmware will " #~ "boot it. Having done this, the rest of the USB stick may be prepared " #~ "using the normal Unix utilities." #~ msgstr "" #~ "包含於 yaboot 之中的常用工具 ybin 並" #~ "不能識別 USB 隨身碟設備,因此您不得不手動安裝 yaboot," #~ "這可以透過 hfsutils 工具來完成。用法如下: " #~ "\n" #~ "$ hmount /dev/sdX2\n" #~ "$ hcopy -r /usr/lib/yaboot/yaboot :\n" #~ "$ hattrib -c UNIX -t tbxi :yaboot\n" #~ "$ hattrib -b :\n" #~ "$ humount\n" #~ " 再提醒一次,請確認您使用的是正確的設備名稱。操" #~ "作過程中一定不能掛載此分割區。程式會把 boot-loader 寫入分割區,並使用 HFS " #~ "工具對其添加標記,使得 Open Fireware 可以以之開機。完成以上操作之後,USB " #~ "隨身碟的其他部分就可以用普通的 Unix 工具來處理了。" #, fuzzy #~| msgid "Adding an ISO image" #~ msgid "Adding the installer image" #~ msgstr "添加 ISO 映像" #, fuzzy #~| msgid "" #~| "Mount the partition (mount /dev/sda2 /mnt) and " #~| "copy the following files from the Debian archives to the stick:" #~ msgid "" #~ "Mount the partition (mount /dev/sdX2 /mnt) and copy the following installer image " #~ "files to the stick:" #~ msgstr "" #~ "接下來就是掛載分割區 (mount /dev/sda2 /mnt) 以及將" #~ "下列檔案從 &debian; 檔案庫拷貝到儲存上:" #~ msgid "vmlinux (kernel binary)" #~ msgstr "vmlinux (核心二進位文件)" #~ msgid "initrd.gz (initial ramdisk image)" #~ msgstr "initrd.gz (初始化記憶體映像檔)" #~ msgid "yaboot.conf (yaboot configuration file)" #~ msgstr "yaboot.conf (yaboot 設定檔案)" #~ msgid "boot.msg (optional boot message)" #~ msgstr "boot.msg (可選的啟動資訊)" #, fuzzy #~ msgid "" #~ "The yaboot.conf configuration file should contain " #~ "the following lines: \n" #~ "default=install\n" #~ "root=/dev/ram\n" #~ "\n" #~ "message=/boot.msg\n" #~ "\n" #~ "image=/vmlinux\n" #~ " label=install\n" #~ " initrd=/initrd.gz\n" #~ " initrd-size=10000\n" #~ " read-only\n" #~ " Please note that the initrd-size parameter may need to be increased, depending on the image you " #~ "are booting." #~ msgstr "" #~ "yaboot.conf 設定檔應該含有以下幾行:" #~ "\n" #~ "default=install\n" #~ "root=/dev/ram\n" #~ "\n" #~ "message=/boot.msg\n" #~ "\n" #~ "image=/vmlinux\n" #~ " label=install\n" #~ " initrd=/initrd.gz\n" #~ " initrd-size=10000\n" #~ " append=\"devfs=mount,dall --\"\n" #~ " read-only\n" #~ " 請注意,在必要的時候,您可能需要增大" #~ "initrd-size 參數的數值,這完全取決於您所使用的記憶" #~ "體映像的大小。" #~ msgid "" #~ "The installer cannot boot from files on an HFS+ file system. MacOS System " #~ "8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. " #~ "To determine whether your existing file system is HFS+, select " #~ "Get Info for the volume in question. HFS file " #~ "systems appear as Mac OS Standard, while HFS+ file " #~ "systems say Mac OS Extended. You must have an HFS " #~ "partition in order to exchange files between MacOS and Linux, in " #~ "particular the installation files you download." #~ msgstr "" #~ "安裝程式無法從 HFS+ 檔案系統進行開機。MacOS System 8.1 及之後的系統可能使 " #~ "用 HFS+ 檔案系統,NewWorld PowerMacs 則全部使用 HFS+。要確認您的系統是否" #~ "是 HFS+,請選擇 Get Info 來查看相關資訊。HFS 檔案系" #~ "統會顯示為 Mac OS Standard,而 HFS+ 檔案系統將顯示" #~ "為 Mac OS Extended。您必須使用一個 HFS 分割區來在 " #~ "MacOS 和 Linux 之間交換檔案,特別是那些您下載的安裝檔案。" #~ msgid "" #~ "Different programs are used for hard disk installation system booting, " #~ "depending on whether the system is a NewWorld or an " #~ "OldWorld model." #~ msgstr "" #~ "根據您的系統是 NewWorldOldWorld 型號,硬" #~ "碟安裝程式開機時將使用不同的安裝檔案。" #~ msgid "" #~ "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good " #~ "idea to use DHCP instead of BOOTP. Some of the latest machines are unable " #~ "to boot using BOOTP." #~ msgstr "" #~ "對於 PowerPC 來說,如果您有一台 NewWorld Power Macintosh 機器,使用 DHCP " #~ "來代替 BOOTP 比較好。有些最新的機器不能從 BOOTP 開機。" #, fuzzy #~ msgid "" #~ "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. " #~ "There is an rbootd package available in &debian;." #~ msgstr "" #~ "一些較早的 HPPA 機器 (例如 715/75) 使用 RBOOTD 而不是 BOOTP。在 parisc-" #~ "linux 網站上能夠找到 RBOOTD 軟體套件。" #, fuzzy #~ msgid "" #~ "If you intend to install &debian; on an SGI machine and your TFTP server " #~ "is a GNU/Linux box running Linux 2.4, you'll need to set the following on " #~ "your server: \n" #~ "# echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc\n" #~ " to turn off Path MTU discovery, otherwise the " #~ "SGI's PROM can't download the kernel. Furthermore, make sure TFTP packets " #~ "are sent from a source port no greater than 32767, or the download will " #~ "stall after the first packet. Again, it's Linux 2.4.X tripping this bug " #~ "in the PROM, and you can avoid it by setting \n" #~ "# echo \"2048 32767\" > /proc/sys/net/ipv4/ip_local_port_range\n" #~ " to adjust the range of source ports the Linux " #~ "TFTP server uses." #~ msgstr "" #~ "如果您想要在一台 SGI 上安裝 &debian; 並且您的 TFTP 伺服器是在 Linux 2.4 " #~ "的 GNU/Linux 上運作,您需要對伺服器進行如下設定:" #~ "\n" #~ "# echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc\n" #~ " 來關閉 Path MTU 查詢,否則 Indy 的 PROM 不能下" #~ "載核心。而且,您還要確保 TFTP 封包是從一個小於 32767 的連接埠送出,否則在" #~ "第一個封包之後,下載將停止。重申一下,這是由於 Linux 2.4.X 觸發了 PROM 裡" #~ "的一個 臭蟲。您可以透過如下設定:\n" #~ "# echo \"2048 32767\" > /proc/sys/net/ipv4/ip_local_port_range\n" #~ " 調整 Linux TFTP 伺服器使用的來源連接埠範圍以避" #~ "開這個錯誤。" #, fuzzy #~| msgid "" #~| "On NewWorld Power Macintosh machines, you will need to set up the " #~| "yaboot boot loader as the TFTP boot image. " #~| "Yaboot will then retrieve the kernel and RAMdisk " #~| "images via TFTP itself. For net booting, use the yaboot-" #~| "netboot.conf. Just rename this to yaboot.conf in the TFTP directory." #~ msgid "" #~ "On NewWorld Power Macintosh machines, you will need to set up the " #~ "yaboot boot loader as the TFTP boot image. " #~ "Yaboot will then retrieve the kernel and RAMdisk " #~ "images via TFTP itself. You will need to download the following files " #~ "from the netboot/ directory:" #~ msgstr "" #~ "在 NewWorld Power Macintosh 上,您需要設定 yaboot boot-" #~ "loader作為 TFTP 開機映像。接著,Yaboot 將透過 TFTP 來取" #~ "得核心和記憶體虛擬磁碟映像。對於網路開機,請使用 yaboot-netboot." #~ "conf。只需要將其更名為 yaboot.conf 並且放" #~ "入 TFTP 目錄。" #~ msgid "vmlinux" #~ msgstr "vmlinux" #~ msgid "initrd.gz" #~ msgstr "initrd.gz" #~ msgid "yaboot" #~ msgstr "yaboot" #~ msgid "yaboot.conf" #~ msgstr "yaboot.conf" #~ msgid "boot.msg" #~ msgstr "boot.msg" #~ msgid "" #~ "For PXE booting, everything you should need is set up in the " #~ "netboot/netboot.tar.gz tarball. Simply extract this " #~ "tarball into the tftpd boot image directory. Make sure " #~ "your dhcp server is configured to pass /debian-installer/ia64/" #~ "elilo.efi to tftpd as the filename to boot." #~ msgstr "" #~ "對於用 PXE 開機來說,您所需的只是設定 netboot/netboot.tar.gz 壓縮檔案。簡單地將此包解壓縮到 tftpd 開機映像" #~ "目錄下。 並確保您的 DHCP 伺服器設定會把 /debian-installer/ia64/" #~ "elilo.efi 以開機所需的檔案名傳遞至tftpd。" #~ msgid "SPARC TFTP Booting" #~ msgstr "SPARC TFTP 開機" #, fuzzy #~ msgid "" #~ "Some SPARC architectures add the subarchitecture names, such as " #~ "SUN4M or SUN4C, to the filename. Thus, if " #~ "your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the " #~ "filename would be C0A80103.SUN4C. However, there are " #~ "also subarchitectures where the file the client looks for is just " #~ "client-ip-in-hex. An easy way to determine the " #~ "hexadecimal code for the IP address is to enter the following command in " #~ "a shell (assuming the machine's intended IP is 10.0.0.4). " #~ "\n" #~ "$ printf '%.2x%.2x%.2x%.2x\\n' 10 0 0 4\n" #~ " To get to the correct filename, you will need " #~ "to change all letters to uppercase and if necessary append the " #~ "subarchitecture name." #~ msgstr "" #~ "SPARC 架構通常使用子架構名稱,例如 SUN4M 或者 " #~ "SUN4C。在某些情況下,架構名字被留為空白,這時客戶端所需要的" #~ "檔案僅僅是十六進位的客戶端 IP。因此,如果您的系統子架" #~ "構是 SUN4C,其 IP 是 192.168.1.3,則檔案名為 C0A80103.SUN4C。一個簡易的確認方法是在 shell 中輸入下列指令 (假設機器的 IP 為 " #~ "10.0.0.4)。 \n" #~ "$ printf '%.2x%.2x%.2x%.2x\\n' 10 0 0 4\n" #~ " 它將 IP 寫成十六進制。要得到正確的檔案名稱,您" #~ "應該將所有的字母改成大寫並在必要時加上子架構名。" #~ msgid "" #~ "You can also force some sparc systems to look for a specific file name by " #~ "adding it to the end of the OpenPROM boot command, such as " #~ "boot net my-sparc.image. This must still reside in " #~ "the directory that the TFTP server looks in." #~ msgstr "" #~ "您也可以透過把一個特定的檔案名稱附加到 OpenPROM boot 指令的結尾來強制某些 " #~ "SPARC 系統使用它。例如 boot net my-sparc.image。不" #~ "過它仍然必須被放置在 TFTP 伺服器要查找的目錄中。" #, fuzzy #~ msgid "SGI TFTP Booting" #~ msgstr "SGI Indys TFTP 開機" #, fuzzy #~ msgid "" #~ "On SGI machines you can rely on the bootpd to supply " #~ "the name of the TFTP file. It is given either as the bf= in /etc/bootptab or as the " #~ "filename= option in /etc/dhcpd.conf." #~ msgstr "" #~ "在 SGI Indys 上您可以採用 bootpd 來提供檔案名稱給 " #~ "TFTP。它既可以是在 /etc/bootptab 檔案中設定 " #~ "bf=,也可以是 /etc/dhcpd.conf " #~ "中的 filename=選項。" #~ msgid "" #~ "# mount /dev/sdX2 /mnt\n" #~ "# cd /mnt\n" #~ "# tar zxvf /path/to/firmware.tar.gz\n" #~ "# cd /\n" #~ "# umount /mnt" #~ msgstr "" #~ "# mount /dev/sdX2 /mnt\n" #~ "# cd /mnt\n" #~ "# tar zxvf /path/to/firmware.tar.gz\n" #~ "# cd /\n" #~ "# umount /mnt" #, fuzzy #~| msgid "" #~| "Hard disk installer booting using LILO or " #~| "GRUB" #~ msgid "" #~ "Hard disk installer booting from Linux using LILO or " #~ "GRUB" #~ msgstr "" #~ "使用 LILOGRUB啟動硬碟安裝程式" #~ msgid "Creating Floppies from Disk Images" #~ msgstr "利用軟碟映像檔建立開機磁片" #~ msgid "" #~ "Bootable floppy disks are generally used as a last resort to boot the " #~ "installer on hardware that cannot boot from CD or by other means." #~ msgstr "" #~ "可開機的磁片一般被視為是在那些不能從光碟或其它方式啟動的硬體上開機安裝程式" #~ "的最後一種方法。" #, fuzzy #~ msgid "" #~ "Booting the installer from floppy disk reportedly fails on Mac USB floppy " #~ "drives." #~ msgstr "有報告說 Mac USB 軟碟機不支援開機磁片。" #~ msgid "" #~ "Disk images are files containing the complete contents of a floppy disk " #~ "in raw form. Disk images, such as boot." #~ "img, cannot simply be copied to floppy drives. A special " #~ "program is used to write the image files to floppy disk in raw mode. This is required because these images are raw " #~ "representations of the disk; it is required to do a sector " #~ "copy of the data from the file onto the floppy." #~ msgstr "" #~ "軟碟映像檔是一些包含完整的原始磁片內容與格式的檔案。" #~ "類似 boot.img 這樣的軟碟映像檔不能直接拷貝到軟碟中。" #~ "必須使用特殊的程式將它們按原始模式寫入磁片。這是一個" #~ "必要的步驟,因為這些映像 文件是一些原始的磁碟保存方式。所以需要把文件的數" #~ "據 按磁區拷貝到軟碟中。" #, fuzzy #~ msgid "" #~ "There are different techniques for creating floppies from disk images. " #~ "This section describes how to create floppies from disk images on " #~ "different platforms." #~ msgstr "" #~ "根據平台的不同,有各種不同的方法來從軟碟映像檔建立開機磁片。這一節將描述如" #~ "何在不同平台上從從軟碟映像檔建立開機磁片。" #~ msgid "" #~ "No matter which method you use to create your floppies, you should " #~ "remember to flip the write-protect tab on the floppies once you have " #~ "written them, to ensure they are not damaged unintentionally." #~ msgstr "" #~ "無論您使用何種方法來建立開機磁片,您應該在建立以後記住打開防寫的開關,以確" #~ "保內容不會在無意間被清除。" #~ msgid "Writing Disk Images From a Linux or Unix System" #~ msgstr "從 Linux 或者 Unix 系統寫入軟碟映像檔" #, fuzzy #~ msgid "" #~ "To write the floppy disk image files to the floppy disks, you will " #~ "probably need root access to the system. Place a good, blank floppy in " #~ "the floppy drive. Next, use the command \n" #~ "$ dd if=filename of=/dev/fd0 bs=1024 " #~ "conv=sync ; sync\n" #~ " where filename is " #~ "one of the floppy disk image files. /dev/fd0 is a " #~ "commonly used name of the floppy disk device, it may be different on your " #~ "workstation (on Solaris, it is /dev/" #~ "fd/0). The command may return to the prompt before " #~ "Unix has finished writing the floppy disk, so look for the disk-in-use " #~ "light on the floppy drive and be sure that the light is out and the disk " #~ "has stopped revolving before you remove it from the drive. On some " #~ "systems, you'll have to run a command to eject the floppy from the drive " #~ " (on Solaris, use eject, see " #~ "the manual page)." #~ msgstr "" #~ "為了把軟碟映像檔寫入軟碟,您可能需要系統的 root 存取權限。在軟碟機中放入一" #~ "張優質的空白軟碟,然後使用指令 \n" #~ "$ dd if=filename of=/dev/fd0 bs=1024 " #~ "conv=sync ; sync\n" #~ " 其中 filename 是一" #~ "個軟碟映像檔案(請參閱 來獲知應該使用" #~ "哪個 filename)。/dev/fd0 " #~ "是一個常見的軟碟機設備名。可能在您的工作站上面有所不同 (在 Solaris 系統上是 /dev/fd/0)。" #~ "這個指令也許在寫入軟碟任務結束之前就會返回到指令提示號下。請觀察軟碟機上面" #~ "的使用燈,並且確保在您拔出軟碟的時候燈已熄滅。在某些系統上,您可能需要下指" #~ "令來退出磁片 (在 Solaris 系統中使用 " #~ "eject 命令,請參閱其手冊)。" #~ msgid "" #~ "Some systems attempt to automatically mount a floppy disk when you place " #~ "it in the drive. You might have to disable this feature before the " #~ "workstation will allow you to write a floppy in raw mode. Unfortunately, how to accomplish this will vary based on your " #~ "operating system. On Solaris, you can work around " #~ "volume management to get raw access to the floppy. First, make sure that " #~ "the floppy is auto-mounted (using volcheck or the " #~ "equivalent command in the file manager). Then use a dd " #~ "command of the form given above, just replace /dev/fd0 with /vol/rdsk/floppy_name, where floppy_name is " #~ "the name the floppy disk was given when it was formatted (unnamed " #~ "floppies default to the name unnamed_floppy). On " #~ "other systems, ask your system administrator. " #~ msgstr "" #~ "有些系統會在您放入軟碟時自動嘗試對其進行掛載。若要讓工作站允許您對軟碟進" #~ "行 原始模式寫入操作,您可能要關閉此功能。不幸的是,如" #~ "何關閉此功能的方法完全取決於作業系統。 在 Solaris " #~ "上,您可以利用磁碟設備管理程式來取得對軟碟機的原始存取權。首先,確信軟碟已" #~ "經被自動掛載 (使用 volcheck 或者檔案管理中的類似指令)。" #~ "然後安照上面給出的形式使用 dd 指令,只是把 /" #~ "dev/fd0 替換成 /vol/rdsk/floppy_name,這裡 floppy_name 是軟" #~ "碟在格式化時所定的名字。(未命名的軟碟預設使用 unnamed_floppy)。至於其他系統,請咨詢您的系統管理員)。" #~ msgid "" #~ "If writing a floppy on powerpc Linux, you will need to eject it. The " #~ "eject program handles this nicely; you might need to " #~ "install it." #~ msgstr "" #~ "如果想在 powerpc Linux 上寫入軟碟,您將必須將之退出。eject 指令能夠對此進行控制,當然您可能需要先安裝它。" #~ msgid "Writing Disk Images From DOS, Windows, or OS/2" #~ msgstr "在 DOS、Windows、或者 OS/2 下寫入磁碟映像檔" #, fuzzy #~ msgid "" #~ "If you have access to an i386 or amd64 machine, you can use one of the " #~ "following programs to copy images to floppies." #~ msgstr "" #~ "如果您能操作一台 i386 機器,您可以使用如下方法之一把映像檔拷貝到軟碟上。" #~ msgid "" #~ "The rawrite1 and rawrite2 programs " #~ "can be used under MS-DOS. To use these programs, first make sure that you " #~ "are booted into DOS. Trying to use these programs from within a DOS box " #~ "in Windows, or double-clicking on these programs from the Windows " #~ "Explorer is not expected to work." #~ msgstr "" #~ "rawrite1rawrite2 程式可在 MS-" #~ "DOS 下使用。如果想使用這些程式,首先要確定您是從 DOS 啟動。在 Windows 的 " #~ "DOS 視窗或者在檔案瀏覽器中雙擊使用這些程式是不能執行" #~ "的。" #~ msgid "" #~ "The rwwrtwin program runs on Windows 95, NT, 98, 2000, " #~ "ME, XP and probably later versions. To use it you will need to unpack " #~ "diskio.dll in the same directory." #~ msgstr "" #~ "rwwrtwin 程式可以在 Windows 95、NT、98、2000、ME、XP 甚" #~ "至最新的版本上運行。要使用它您需要解壓 diskio.dll 至相同目錄下。" #~ msgid "" #~ "These tools can be found on the Official &debian; CD-ROMs under the " #~ "/tools directory." #~ msgstr "" #~ "這些工具可以在官方 &debian;光碟中找到。他們位於 /tools 目錄下。" #~ msgid "Writing Disk Images From MacOS" #~ msgstr "在 MacOS 上寫入磁碟映像檔" #~ msgid "" #~ "An AppleScript, Make &debian; Floppy, is " #~ "available for burning floppies from the provided disk image files. It can " #~ "be downloaded from . To use it, " #~ "just unstuff it on your desktop, and then drag any floppy image file to " #~ "it. You must have Applescript installed and enabled in your extensions " #~ "manager. Disk Copy will ask you to confirm that you wish to erase the " #~ "floppy and proceed to write the file image to it." #~ msgstr "" #~ "這裡有一個名為 Make Debian Floppy 的 " #~ "AppleSrcipt 可以由磁碟映像檔製作磁片。您可從 處下載之。使用時只需要解壓縮檔案至桌面然後將您想燒錄的映像檔拖拉到" #~ "該程式。您必須安裝 Applescript 並在您的擴充套件管理員中開啟它。Disk Copy " #~ "會要求您確認清空磁碟並寫入磁碟映像檔。" #~ msgid "" #~ "You can also use the MacOS utility Disk Copy directly, " #~ "or the freeware utility suntar. The root." #~ "bin file is an example of a floppy image. Use one of the " #~ "following methods to create a floppy from the floppy image with these " #~ "utilities." #~ msgstr "" #~ "您也可以直接使用 MacOS 工具 Disk Copy ,或者免費軟體工" #~ "具 suntarroot.bin 是一個軟碟映像" #~ "檔範例。您可以使用這些工具和以下方法將磁碟映像寫入軟碟。" #~ msgid "Writing Disk Images with Disk Copy" #~ msgstr "寫入磁碟映像檔:使用Disk Copy" #~ msgid "" #~ "If you are creating the floppy image from files which were originally on " #~ "the official &debian-gnu; CD, then the Type and Creator are already set " #~ "correctly. The following Creator-Changer steps are " #~ "only necessary if you downloaded the image files from a &debian; mirror." #~ msgstr "" #~ "假如您是使用官方 &debian-gnu;光碟上的軟碟映像檔文件,那麼 Type 和 Creator " #~ "已經設置正確。 以下 Creator-Changer 步驟只針對從 " #~ "&debian; 鏡像站下載映像檔的情況。" #~ msgid "" #~ "Obtain Creator-Changer and use it to open the root.bin file." #~ msgstr "" #~ "取得 Creator-Changer " #~ "並且用它打開 root.bin 檔案。" #~ msgid "" #~ "Change the Creator to ddsk (Disk Copy), and the " #~ "Type to DDim (binary floppy image). The case is " #~ "sensitive for these fields." #~ msgstr "" #~ "將 Creator 改為 ddsk (Disk Copy),並將 Type 改為 " #~ "DDim (binary floppy image)。注意此處有大小寫區分。" #~ msgid "" #~ "Important: In the Finder, use Get Info to display the Finder information about the floppy image, and " #~ "X the File Locked check box so that " #~ "MacOS will be unable to remove the boot blocks if the image is " #~ "accidentally mounted." #~ msgstr "" #~ "注意: 在 Finder 中,使用 Get Info 來顯示軟碟映像檔的 Finder 資訊,並在 File Locked 複選欄中畫上 X。如此一來當映像檔被意外的掛載時 " #~ "MacOS 才不會刪除開機區。" #~ msgid "" #~ "Obtain Disk Copy; if you have a MacOS system or CD it " #~ "will very likely be there already, otherwise try ." #~ msgstr "" #~ "取得 Disk Copy。如果您已經擁有了 MacOS 系統或光碟,它多" #~ "半就已經被包含在其中,否則可以試試 。" #~ msgid "" #~ "Run Disk Copy, and select " #~ "Utilities Make a Floppy , then select the locked image file from " #~ "the resulting dialog. It will ask you to insert a floppy, then ask if you " #~ "really want to erase it. When done it should eject the floppy." #~ msgstr "" #~ "執行 Disk Copy,並且選擇 " #~ "Utilities Make a Floppy ,然後從對話框中選擇 locked 的映像檔。它會要求您插入一張磁片,然後詢問是否刪除它。完成後它應" #~ "該會退出磁片。" #~ msgid "Writing Disk Images with suntar" #~ msgstr "寫入磁碟映像檔:使用suntar" #~ msgid "" #~ "Obtain suntar from . Start the suntar program and select " #~ "Overwrite Sectors... from the Special menu." #~ msgstr "" #~ "取得 suntar,它在 " #~ " 中。執行 suntar 程式並且從 " #~ "Special 選單中選擇 Overwrite Sectors...。" #~ msgid "" #~ "Insert the floppy disk as requested, then hit &enterkey; (start at sector " #~ "0)." #~ msgstr "按照要求插入軟碟,然後按下 &enterkey; (從0磁區開始)。" #~ msgid "" #~ "Select the root.bin file in the file-opening dialog." #~ msgstr "在開啟檔案對話框中選擇 root.bin 檔案。" #~ msgid "" #~ "After the floppy has been created successfully, select " #~ "File Eject . " #~ "If there are any errors writing the floppy, simply toss that floppy and " #~ "try another." #~ msgstr "" #~ "當軟碟被成功寫入之後,選擇 File " #~ "Eject 。如果期間發生任何錯誤,請換" #~ "別的軟碟試試。" #~ msgid "" #~ "Before using the floppy you created, set the write protect tab! Otherwise if you accidentally mount it in MacOS, MacOS will " #~ "helpfully ruin it." #~ msgstr "" #~ "在使用您建立的軟碟之前,請設定防寫保護標籤!否則,如" #~ "果您偶然在 MacOS 中掛載了它,MacOS 將會將其毀壞。" #~ msgid "Hard Disk Installer Booting for OldWorld Macs" #~ msgstr "OldWorld Macs 上的硬碟開機安裝程式" #~ msgid "" #~ "The boot-floppy-hfs floppy uses miBoot to launch Linux installation, but miBoot cannot easily be used for hard disk booting. " #~ "BootX, launched from MacOS, supports booting " #~ "from files placed on the hard disk. BootX can " #~ "also be used to dual-boot MacOS and Linux after your &debian; " #~ "installation is complete. For the Performa 6360, it appears that " #~ "quik cannot make the hard disk bootable. So " #~ "BootX is required on that model." #~ msgstr "" #~ "boot-floppy-hfs 軟碟使用 miBoot 來啟動 Linux 安裝,但是 miBoot 不" #~ "易用於從硬碟開機。運作於 MacOS 的 BootX 支援從" #~ "硬碟上的檔案進行開機。BootX 也能在安裝完 " #~ "&debian; 後用於 MacOS 和 Linux 的雙重開機。對於 Performa 6360 來說," #~ "quik 看上去不能讓硬碟可開機。因此 BootX 對於該型號來說是必須的。" #~ msgid "" #~ "Download and unstuff the BootX distribution, " #~ "available from , or in the " #~ "dists/woody/main/disks-powerpc/current/powermac " #~ "directory on &debian; http/ftp mirrors and official &debian; CDs. Use " #~ "Stuffit Expander to extract it from its " #~ "archive. Within the package, there is an empty folder called " #~ "Linux Kernels. Download linux.bin and ramdisk.image.gz from the " #~ "disks-powerpc/current/powermac folder, and place " #~ "them in the Linux Kernels folder. Then place the " #~ "Linux Kernels folder in the active System Folder." #~ msgstr "" #~ "請下載並且解壓 BootX 發佈套件。它可以從 ,或者 &debian; http/ftp 鏡像以及官方 " #~ "&debian;光碟的 dists/woody/main/disks-powerpc/current/powermac 目錄下得到。可以用 Stuffit Expander " #~ "來把它從打包檔案中解開。在這個包中,有一個名為 Linux Kernels 的空目錄。請下載 linux.bin 和 " #~ "ramdisk.image.gz (位於 disks-powerpc/" #~ "current/powermac 目錄),然後把他們放到 Linux " #~ "Kernels 目錄中,然後把 Linux Kernels 目錄" #~ "放到活動的系統目錄中。" #~ msgid "Hard Disk Installer Booting for NewWorld Macs" #~ msgstr "NewWorld Macs 下啟動硬碟安裝程式" #~ msgid "" #~ "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, " #~ "as well as loading ELF binaries directly from the hard disk. These " #~ "machines will boot Linux directly via yaboot, which " #~ "supports loading a kernel and RAMdisk directly from an ext2 partition, as " #~ "well as dual-booting with MacOS. Hard disk booting of the installer is " #~ "particularly appropriate for newer machines without floppy drives. " #~ "BootX is not supported and must not be used on " #~ "NewWorld PowerMacs." #~ msgstr "" #~ "NewWorld PowerMacs 支援從網路或者 ISO9660 格式光碟進行開機,或者直接從硬碟" #~ "上載入 ELF 二進位文件。這類機器可以直接使用 yaboot 開" #~ "機。它既支援直接從 ext2 分割區中裝入核心和記憶體虛擬磁碟,也支援和 MacOS " #~ "的雙重開機。硬碟開機特別適合最新的沒有軟碟機的機器。BootX 則不被支援,也一定不能用在 NewWorld PowerMacs 上。" #~ msgid "" #~ "Copy (not move) the following four files which you " #~ "downloaded earlier from the &debian; archives, onto the root level of " #~ "your hard drive (this can be accomplished by option-" #~ "dragging each file to the hard drive icon)." #~ msgstr "" #~ "拷貝 (而非移動) 您早先從 &debian; 檔案庫下載的下列四" #~ "個檔案到您硬碟的根目錄上 (這個可以用按住 option 鍵然後拖" #~ "曳每個檔案到硬碟圖示的方法來完成)。" #, fuzzy #~ msgid "" #~ "Make a note of the partition number of the MacOS partition where you " #~ "place these files. If you have the MacOS pdisk " #~ "program, you can use the L command to check for the " #~ "partition number. You will need this partition number for the command you " #~ "type at the Open Firmware prompt when you boot the installer." #~ msgstr "" #~ "記下您存放這些文件的 MacOS 分割區號。如果您有 MacOS 的 pdisk 程式,您可以使用 L 指令檢查分割區號。當開機安裝程式的時候,您需要" #~ "這個分割區號碼用於在 Open Firmware 提示符號下面輸入指令。" #~ msgid "To boot the installer, proceed to ." #~ msgstr "要啟動安裝程式,請進入 。" #, fuzzy #~| msgid "" #~| "When downloading files from a Debian mirror, be sure to download the " #~| "files in binary mode, not text or automatic mode." #~ msgid "" #~ "When downloading files from a &debian; mirror using FTP, be sure to " #~ "download the files in binary mode, not text or " #~ "automatic mode." #~ msgstr "" #~ "當從 &debian; 鏡像伺服器下載檔案的時候,請確認以二進位模式下載,而不是文字或者自動模式。" #, fuzzy #~ msgid "Thecus N2100 Installation Files" #~ msgstr "CATS 的安裝檔案" #, fuzzy #~| msgid "CATS Installation Files" #~ msgid "GLAN Tank Installation Files" #~ msgstr "CATS 的安裝檔案" #~ msgid "Creating an IPL tape" #~ msgstr "建立 IPL 磁帶" #, fuzzy #~ msgid "" #~ "If you can't boot (IPL) from the CD-ROM and you are not using VM you need " #~ "to create an IPL tape first. This is described in section 3.4.3 in the " #~ " Linux for IBM eServer zSeries and S/390: Distributions " #~ "Redbook. The files you need to write to the tape are (in this order): " #~ "kernel.debian, parmfile.debian " #~ "and initrd.debian. The files can be downloaded from " #~ "the tape sub-directory, see ." #~ msgstr "" #~ "如果您不能從光碟開機 (IPL) 並且沒有使用 VM,您首先就需要建立一個 IPL 磁" #~ "帶。這在 Linux for IBM eServer zSeries and S/390: Distributions Redbook 的第 3.4.3 節中有描述。您需要寫到磁帶上的檔案有 (按以下順" #~ "序):kernel.debianparmfile.debianinitrd.debian。這些檔案可以從 " #~ "tape 子目錄下載,請參閱 ," #, fuzzy #~ msgid "NSLU2 Installation Files" #~ msgstr "CATS 的安裝檔案" #~ msgid "Copying the files — the easy way" #~ msgstr "複製檔案 — 簡單的方法" #~ msgid "" #~ "If your system refuses to boot from the memory stick, the stick may " #~ "contain an invalid master boot record (MBR). To fix this, use the " #~ "install-mbr command from the package mbr:" #~ msgstr "" #~ "如果您的系統拒絕從 USB 隨身碟開機,那麼可能是因為它含有無效的主開機磁區記" #~ "錄 (MBR)。您可以使用 install-mbr 指令來修復這個問題,該" #~ "指令來自 mbr 軟體套件:" #, fuzzy #~| msgid "# install-mbr /dev/sda" #~ msgid "# install-mbr /dev/sdX" #~ msgstr "# install-mbr /dev/sda" #~ msgid "The installer cannot boot from files on an NTFS file system." #~ msgstr "安裝程式無法在 NTFS 檔案系統上開機。" #~ msgid "" #~ "To use the Pre-boot Execution Environment (PXE) method of TFTP booting, " #~ "you will need a TFTP server with tsize support. On " #~ "a &debian-gnu; server, the atftpd and " #~ "tftpd-hpa packages qualify; we recommend " #~ "tftpd-hpa." #~ msgstr "" #~ "如果想用 TFTP 的 Pre-boot Execution Environment (PXE) 方式啟動,您將需要一" #~ "台支援 tsize 的 TFTP 伺服器。在 &debian-gnu; 伺服器" #~ "上,atftpdtftpd-hpa套件" #~ "符合此要求,我們建議使用 tftpd-hpa。" #~ msgid "" #~ "To get the TFTP server ready to go, you should first make sure that " #~ "tftpd is enabled. This is usually enabled by having " #~ "something like the following line in /etc/inetd.conf: \n" #~ "tftp dgram udp wait nobody /usr/sbin/tcpd in.tftpd /tftpboot\n" #~ " Debian packages will in general set this up " #~ "correctly by default when they are installed." #~ msgstr "" #~ "要準備好 TFTP 伺服器,您首先需要確定 tftpd 已經啟動。這" #~ "通常可以在 /etc/inetd.conf 加入下列設定來完成: " #~ "\n" #~ "tftp dgram udp wait nobody /usr/sbin/tcpd in.tftpd /tftpboot\n" #~ " Debian 套件通常在安裝後會自動把這條設定好。" #, fuzzy #~ msgid "" #~ "Look in /etc/inetd.conf and remember the directory " #~ "which is used as the argument of in.tftpd " #~ " All in.tftpd alternatives available in Debian " #~ "should log TFTP requests to the system logs by default. Some of them " #~ "support a -v argument to increase verbosity. It is " #~ "recommended to check these log messages in case of boot problems as they " #~ "are a good starting point for diagnosing the cause of errors. ; you'll need that below. If you've had to change /etc/" #~ "inetd.conf, you'll have to notify the running inetd process that the file has changed. On a Debian machine, run " #~ "/etc/init.d/inetd reload; on other machines, find " #~ "out the process ID for inetd, and run kill -" #~ "HUP inetd-pid." #~ msgstr "" #~ "檢查那個檔案並且記住被用作 in.tftpd 參數的目錄,您接下" #~ "來將會需要它。-l 參數能夠讓某些版本的 in." #~ "tftpd 將所有請求記錄到系統日誌中。這在檢查錯誤的時候會很有用。如" #~ "果您必須修改 /etc/inetd.conf,您將必須提醒正在運作的 " #~ "inetd 程序該檔案已經被改變。在 Debian 系統中,您應該執" #~ "行 /etc/init.d/inetd reload﹔而在其它系統中,找到 " #~ "inetd 所對應的程序 ID,並且執行 kill -HUP " #~ "inetd-pid。" #~ msgid "" #~ "If you choose to boot from ARC console firmware using MILO, you will also need to prepare a disk containing MILO and LINLOAD.EXE from the provided disk " #~ "images. See for more information on " #~ "Alpha firmware and boot loaders. The floppy images can be found in the " #~ "MILO directory as " #~ "milo_subarchitecture.bin." #~ msgstr "" #~ "如果您選擇透過 MILO 來從 ARC 控制台韌體開機,就需要從所" #~ "提供的磁碟映像中準備一張載有 MILOLINLOAD." #~ "EXE 的磁碟。有關 Alpha 韌體和 boot-loader 的更多資訊請參閱 " #~ " 。軟碟映像檔可以在 MILO 目錄下找到。其形式為:milo_子架構.bin。" #~ msgid "" #~ "Unfortunately, these MILO images could not be tested " #~ "and might not work for all subarchitectures. If you find it doesn't work " #~ "for you, try copying the appropriate MILO binary onto " #~ "the floppy (). Note that those MILOs don't support ext2 " #~ "sparse superblocks, so you can't use them to load kernels " #~ "from newly generated ext2 file systems. As a workaround, you can put your " #~ "kernel onto the FAT partition next to the MILO." #~ msgstr "" #~ "抱歉的是,這些 MILO 映像文件未經過足夠的測試,也許並不" #~ "是在所有的子架構下都能正常運行。 如果您發現它不能運行,請嘗試將合適的 " #~ "MILO 二進位檔案拷貝到軟碟中()。注意,這些 MILO 不支援 ext2 的 sparse superblocks,因此您不能從新" #~ "生成的 ext2 檔案系統中裝載核心。作為一個變通方法,您可以把核心放到 FAT 分" #~ "割區中,緊跟著 MILO。" #~ msgid "" #~ "MILO binaries are platform-specific. See to determine the appropriate MILO " #~ "image for your Alpha platform." #~ msgstr "" #~ "MILO 的二進位檔案是依賴於具體平台的,請參閱 來確認哪一個 MILO 映像檔適用於" #~ "您的 Alpha 平台。" #~ msgid "" #~ "Unlike the Open Firmware found on Sparc and PowerPC machines, the SRM " #~ "console will not use RARP to obtain its IP address, " #~ "and therefore you must use BOOTP for net booting your Alpha " #~ " Alpha systems can also be net-booted using the DECNet MOP " #~ "(Maintenance Operations Protocol), but this is not covered here. " #~ "Presumably, your local OpenVMS operator will be happy to assist you " #~ "should you have some burning need to use MOP to boot Linux on your Alpha. " #~ " . You can also enter the IP configuration for network " #~ "interfaces directly in the SRM console." #~ msgstr "" #~ "不像 Sparc 和 PowerPC 機器上的 Open Firmware , SRM 控制台將使用 RARP 來取得它的 IP 位址。因此您必須使用 BOOTP 來從網路啟動您" #~ "的 Alpha 機器。Alpha 系統也能使用 DECNet MOP " #~ "(Maintenance Operations Protocol) 來進行網路開機,但是這裡不使用此技術。相" #~ "信您的本地 OpenVMS 操作員樂於協助您燒錄,以便在您的 Alpha 機器上用 MOP 來" #~ "開機 Linux。 。您也可以直接在 SRM 控制台中直接輸入網路" #~ "介面的 IP 設定。" #~ msgid "Alpha TFTP Booting" #~ msgstr "Alpha TFTP 開機" #~ msgid "" #~ "On Alpha, you must specify the filename (as a relative path to the boot " #~ "image directory) using the -file argument to the " #~ "SRM boot command, or by setting the " #~ "BOOT_FILE environment variable. Alternatively, the " #~ "filename can be given via BOOTP (in ISC dhcpd, use the " #~ "filename directive). Unlike Open Firmware, there " #~ "is no default filename on SRM, so you " #~ "must specify a filename by either one of these " #~ "methods." #~ msgstr "" #~ "在 Alpha 上,您必須透過 -file 參數將檔案名 (與開機" #~ "映像目錄的相對路徑) 指定給 SRM 的 boot 指令,或者設" #~ "定 BOOT_FILE 環境變數。或者,也可以透過 BOOTP 提供" #~ "檔案名稱 (在 ISC 的 dhcpd 中,使用 " #~ "filename 指令)。與 Open Firmware 不同的是,這裡的 " #~ "SRM 沒有預設檔案名稱,因此您必須" #~ "透過以上方法之一來指定一個檔案名稱。" #~ msgid "Choosing a Kernel" #~ msgstr "選擇一個核心" #~ msgid "" #~ "Some m68k subarchs have a choice of kernels to install. In general we " #~ "recommend trying the most recent version first. If your subarch or " #~ "machine needs to use a 2.2.x kernel, make sure you choose one of the " #~ "images that supports 2.2.x kernels (see the MANIFEST)." #~ msgstr "" #~ "一些 m68k 子架構可以選擇要安裝的核心。一般來說我們建議您首先嘗試最新的版" #~ "本。 如果您的子架構系統或機器需要使用 2.2.x 版的核心,請確認您選擇的是一個" #~ "支援對應核心的映像檔。(請參閱 MANIFEST)。" #~ msgid "" #~ "All of the m68k images for use with 2.2.x kernels, require the kernel " #~ "parameter &ramdisksize;." #~ msgstr "" #~ "所有使用 2.2.x 核心的 m68k 的映像檔都要求使用 &ramdisksize; 核心參數。" #, fuzzy #~ msgid "" #~ "Booting the installer from floppy disk is not supported on Amigas or 68k " #~ "Macs." #~ msgstr "Amigas 或者 68k Macs 的軟碟開機也不被支援。" #~ msgid "Writing Disk Images on Atari Systems" #~ msgstr "在 Atari 系統上寫入磁碟映像檔" #~ msgid "" #~ "You'll find the &rawwrite.ttp; program in the same directory as the " #~ "floppy disk images. Start the program by double clicking on the program " #~ "icon, and type in the name of the floppy image file you want written to " #~ "the floppy at the TOS program command line dialog box." #~ msgstr "" #~ "您可以在與軟碟映像檔相同的目錄下找到 &rawwrite.ttp;。雙擊程式圖示,在 TOS " #~ "程式 指令列輸入框內鍵入您想寫入軟碟的軟碟映像檔名。" #~ msgid "Writing Disk Images on Macintosh Systems" #~ msgstr "在 Macintosh 系統上寫入磁碟映像檔" #, fuzzy #~ msgid "" #~ "Since the current release does not yet support booting from floppies to " #~ "start the installation, there would be no point in doing this on " #~ "Macintosh Systems. However, these files are needed for the installation " #~ "of the operating system and modules, later in the process." #~ msgstr "" #~ "沒有一個 MacOS 應用程式可以將映像檔寫到軟碟 (而且這也沒有什麼意義,因為您" #~ "也不能在 Macintosh 系統上用軟碟啟動安裝系統來安裝核心以及模組)。但是,後續" #~ "在安裝作業系統和模組時需要這些檔案。" #~ msgid "BVM/Motorola TFTP Booting" #~ msgstr "BVM/Motorola TFTP 開機" #~ msgid "" #~ "For BVM and Motorola VMEbus systems copy the files &bvme6000-tftp-files; " #~ "to /tftpboot/." #~ msgstr "" #~ "對於 BVM 以及 Motorola VMEbus 系統來說,請先將 &bvme6000-tftp-files; 檔案" #~ "拷貝到 /tftpboot/。" #~ msgid "" #~ "Next, configure your boot ROMs or BOOTP server to initially load the " #~ "tftplilo.bvme or tftplilo.mvme " #~ "files from the TFTP server. Refer to the tftplilo.txt file for your subarchitecture for additional system-specific " #~ "configuration information." #~ msgstr "" #~ "接下來,設定您的開機 ROM 或 BOOTP 伺服器,使其從 TFTP 伺服器載入 " #~ "tftplilo.bvme 或者 tftplilo.mvme 檔案。請閱讀 tftplilo.txt 文字檔來取得更多" #~ "的關於您所使用的子架構的系統特殊配置資訊。" #, fuzzy #~ msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" #~ msgstr "Broadcom BCM91250A TFTP 開機" #, fuzzy #~ msgid "" #~ "You don't have to configure DHCP in a special way because you'll pass the " #~ "full path of the file to be loaded to CFE." #~ msgstr "" #~ "您不需要透過特殊方法設定 DHCP,因為您要把要載入到 CFE 的檔案完全路徑傳送出" #~ "去。" #, fuzzy #~ msgid "" #~ "The easiest way to boot a Netwinder is over the network, using the " #~ "supplied TFTP image &netwinder-boot-img;." #~ msgstr "" #~ "啟動一台 NetWinder 最輕鬆的途徑是使用其提供的 TFTP 映像檔 &netwinder-boot-" #~ "img; 進行網路開機。" # index.docbook:645, index.docbook:739 #~ msgid "USB stick partitioning on &arch-title;" #~ msgstr "&arch-title; 上的 USB 隨身碟分割區" #~ msgid "Optional kernel modules" #~ msgstr "可選的核心模組" #, fuzzy #~ msgid "" #~ "The installer will look for a Debian ISO image on the stick as its source " #~ "for additional data needed for the installation. So your next step is to " #~ "copy a Debian ISO image (businesscard, netinst or even a full CD image) " #~ "onto your stick (be sure to select one that fits). The file name of the " #~ "image must end in .iso." #~ msgstr "" #~ "現在您需要把任意一個 Debian ISO 映像 (businesscard、netinst 或者甚至是完全" #~ "版) 放入您的 USB 隨身碟內 (如果它裝得下的話)。這樣的一個映像檔的副檔名必須" #~ "是 .iso。" #~ msgid "" #~ "If you want to install over the network, without using an ISO image, you " #~ "will of course skip the previous step. Moreover you will have to use the " #~ "initial ramdisk from the netboot directory instead " #~ "of the one from hd-media, because hd-media/" #~ "initrd.gz does not have network support." #~ msgstr "" #~ "如果您想直接透過網路安裝而不使用 ISO 映像,當然就可以跳過上述步驟。並且您" #~ "必須要使用 netboot 目錄中的初始化記憶體映像來取代來" #~ "自 hd-media 的相同檔案。這是因為 hd-media/" #~ "initrd.gz 並不包含網路支援。" #~ msgid "DECstation TFTP Images" #~ msgstr "DECstation TFTP 映像檔" #, fuzzy #~ msgid "" #~ "For DECstations, there are tftpimage files for each subarchitecture, " #~ "which contain both kernel and installer in one file. The naming " #~ "convention is subarchitecture/" #~ "netboot-boot.img. Copy the tftpimage file you would like to " #~ "use to /tftpboot/tftpboot.img if you work with the " #~ "example BOOTP/DHCP setups described above." #~ msgstr "" #~ "對於 DECstation 來說,對於每個子架構都有相應的 tftpimage 映像檔。這些單一" #~ "檔案包含了核心和安裝程式。命名規則是 subarchitecture/netboot-boot.img。如果您是按照上述 BOOTP/DHCP 設定範例進行操" #~ "作,請將想要使用的 tftpimage 檔案拷貝至 /tftpboot/tftpboot." #~ "img。" #~ msgid "" #~ "The DECstation firmware boots by TFTP with the command boot " #~ "#/tftp, where # is the number of the TurboChannel device from which to boot. " #~ "On most DECstations this is 3. If the BOOTP/DHCP server " #~ "does not supply the filename or you need to pass additional parameters, " #~ "they can optionally be appended with the following syntax:" #~ msgstr "" #~ "DECstation 透過 boot #/tftp 指令來使用 TFTP 進行韌體開機。這裡 # 是用於開機的 TurboChannel 設備編號。在大多數 DECstations 上," #~ "這個數字是 3。 如果 BOOTP/DHCP 伺服器不提供檔案名或者您需要" #~ "傳遞附加的參數,他們可以按照下列語法加入:" #~ msgid "boot #/tftp/filename param1=value1 param2=value2 ..." #~ msgstr "boot #/tftp/filename param1=value1 param2=value2 ..." #~ msgid "" #~ "Several DECstation firmware revisions show a problem with regard to net " #~ "booting: the transfer starts, but after some time it stops with an " #~ "a.out err. This can have several " #~ "reasons: The firmware does not respond to " #~ "ARP requests during a TFTP transfer. This leads to an ARP timeout and the " #~ "transfer stops. The solution is to add the MAC address of the Ethernet " #~ "card in the DECstation statically to the ARP table of the TFTP server. " #~ "This is done by running arp -s IP-address MAC-address as root " #~ "on the machine acting as TFTP server. The MAC-address of the DECstation " #~ "can be read out by entering cnfg at the DECstation " #~ "firmware prompt. The firmware has a " #~ "size limit on the files that can be booted by TFTP. There are also firmware revisions that cannot boot via TFTP " #~ "at all. An overview about the different firmware revisions can be found " #~ "at the NetBSD web pages: ." #~ msgstr "" #~ "一些 DECstation 韌體版本在網路開機中有一個問題:傳輸可以開始,但是過一段時" #~ "間它就會停止並且產生一個 a.out err。這可" #~ "能是由以下幾個原因所造成的: 韌體在一個 " #~ "TFTP 傳輸中沒有回應 ARP 請求,這導致一個 ARP 超時並且停止傳輸。解決方案是" #~ "將以太網卡的 MAC 位址靜態加入到 TFTP 伺服器的 ARP 列表中。想要作到這點可以" #~ "在 TFTP 伺服器上用 root 身份執行 arp -s IP-" #~ "address MAC-address。" #~ "DECstation 的 MAC 位址能夠透過在 DECstation 韌體提示符號下輸入 " #~ "cnfg 來取得。 韌體對" #~ "於這些能透過 TFTP 開機的檔案有一個大小限制。 有些韌體版本根本不能透過 TFTP 開機。您可以在 NetBSD 網頁上找" #~ "到關於不同韌體版本的概述:。" #~ msgid "" #~ "The RiscPC installer is booted initially from RISC OS. All the necessary " #~ "files are provided in one Zip archive, &rpc-install-kit;. Download this " #~ "file onto the RISC OS machine, copy the linloader.!Boot components into place, and run !dInstall." #~ msgstr "" #~ "RiscPC 安裝程式最初是從 RiSC OS 開機的。所有必需的文件都由一個名為 &rpc-" #~ "install-kit; 的檔案所提供,請將此檔案下載到 RISC OS 機器中,將 " #~ "linloader.!Boot 拷貝到合適的位置,然後執行 " #~ "!dInstall。" #~ msgid "" #~ "On a RARP server system using a Linux 2.2.x kernel, you need to populate " #~ "the kernel's RARP table. To do this, run the following commands: " #~ "\n" #~ "# /sbin/rarp -s\n" #~ "client-hostname\n" #~ "client-enet-addr\n" #~ "\n" #~ "# /usr/sbin/arp -s\n" #~ "client-ip\n" #~ "client-enet-addr\n" #~ " If you get \n" #~ "SIOCSRARP: Invalid argument\n" #~ " you probably need to load the RARP kernel " #~ "module or else recompile the kernel to support RARP. Try " #~ "modprobe rarp and then try the rarp command again." #~ msgstr "" #~ "在使用 Linux 2.2.x 核心的 RARP 伺服器系統上,您需要以下的指令來載入核心 " #~ "RARP 表: \n" #~ "# /sbin/rarp -s \n" #~ "client-hostname\n" #~ "client-enet-addr\n" #~ "\n" #~ "# /usr/sbin/arp -s \n" #~ "client-ip\n" #~ "client-enet-addr\n" #~ " 如果您得到如下資訊 \n" #~ "SIOCSRARP: Invalid argument\n" #~ " 您可能需要掛載 RARP 核心模組或重新編譯核心並使" #~ "之支援 RARP。試試在執行 modprobe rarp 指令後再嘗試" #~ "一遍 rarp 指令。" #~ msgid "" #~ "On a RARP server system using a Linux 2.4.x kernel, there is no RARP " #~ "module, and you should instead use the rarpd program. " #~ "The procedure is similar to that used under SunOS in the following " #~ "paragraph." #~ msgstr "" #~ "使用 Linux 2.4.x 核心的 RARP 伺服器系統上並沒有 RARP 模組,您應該使用 " #~ "rarpd 程式替代。操作過程很類似下面將提到的在 SunOS 上的" #~ "用法。" #~ msgid "" #~ "The only supported boot method for CATS is to use the combined image " #~ "&cats-boot-img;. This can be loaded from any device accessible to the " #~ "Cyclone bootloader." #~ msgstr "" #~ "在 CATS 上唯一被支援的開機方法是使用組合映像 &cats-boot-img;。它能從任何 " #~ "Cyclone boot-loader 可以存取的設備上被掛載。" #, fuzzy #~ msgid "" #~ "Although most dialogs used by &d-i; can be preseeded using this method, " #~ "there are some notable exceptions. You can (re)partition an entire disk " #~ "or use available free space on a disk; it is not possible to use existing " #~ "partitions. You currently cannot use preseeding to set up RAID and LVM. " #~ "Also, with the exception of network driver modules, it is not possible to " #~ "preconfigure kernel module parameters." #~ msgstr "" #~ "雖然大多 &d-i; 使用的對話框可以用這種方法預設,但還是有明顯的例外。目前還" #~ "無法預設 RAID 和 LVM。另外還有,網路驅動模組,也無法預先設置核心模組參數。" #~ msgid "" #~ "The preconfiguration file is in the format used by the debconf-set-" #~ "selections command. A well documented and working example that you can " #~ "edit is in ." #~ msgstr "" #~ "預先設定檔是按照 debconf-set-selections 指令的格式寫成的。這裡有一個具有詳" #~ "盡註解並能正常工作的預先設定檔例子:。" #~ msgid "" #~ "Alternatively, one way to get a complete file listing all the values that " #~ "can be preseeded is to do a manual install, and then use " #~ "debconf-get-selections, from the debconf-" #~ "utils package, to dump both the debconf database and the " #~ "cdebconf database in /var/log/debian-installer/cdebconf to a single file: " #~ "\n" #~ "$ debconf-get-selections --installer > file\n" #~ "$ debconf-get-selections >> file\n" #~ " However, a file generated in this manner will " #~ "have some items that should not be preseeded, and the file in is a better starting place for most users." #~ msgstr "" #~ "除此之外,要得到一個包含所有可被預設項目的完整文件,您可以進行手動安裝,然" #~ "後使用 debconf-get-selections 指令 (它來自 " #~ "debconf-utils軟體套件) 將 debconf 資料庫和位於 /" #~ "var/log/debian-installer/cdebconf 的資料庫的內容導出至一個單一的檔案:" #~ "\n" #~ "$ debconf-get-selections --installer > 檔案名稱\n" #~ "$ debconf-get-selections >> 檔案名稱\n" #~ " 但是,按照些方法生成的檔案將會包含一些不應該被" #~ "預先設定的項目,因此 中的檔案對於大多" #~ "數使用者來說是一個更好的起點。" #~ msgid "" #~ "Once you have a preconfiguration file, you can edit it if necessary, and " #~ "place it on a web server, or copy it onto the installer's boot media. " #~ "Wherever you place the file, you need to pass a parameter to the " #~ "installer at boot time to tell it to use the file." #~ msgstr "" #~ "一旦您有了一個預先設定檔,可以在需要時編輯它,並且上傳至網頁伺服器,或者拷" #~ "貝至安裝程式的開機媒介。無論您將此檔案放在哪裡,都需要傳遞一個參數給安裝程" #~ "式來使其使用個檔案。" #~ msgid "" #~ "To make the installer use a preconfiguration file downloaded from the " #~ "network, add preseed/url=http://url/to/preseed.cfg to the kernel boot " #~ "parameters. Of course the preconfiguration will not take effect until the " #~ "installer manages to set up the network to download the file, so this is " #~ "most useful if the installer can set up the network via DHCP without " #~ "asking any questions. You may want to set the installation priority to " #~ "critical to avoid any questions while the network is being configured. " #~ "See ." #~ msgstr "" #~ "要讓安裝程式使用一個從網路下載的預先設定檔,請將 preseed/url=http://url/" #~ "to/config 加入核心啟動參數。當然這個預先設定檔,只有安裝程式能夠管理網路並" #~ "下載檔案後才能起作用,因此如果安裝程式能夠透過 DHCP 設置網路而不需要詢問任" #~ "何問題的話,此方法會更有用。如果您已經設置好了網路,可能還會想將安裝優先順" #~ "序調至關鍵級來避免任何問題。請參閱 。" #~ msgid "" #~ "To place a preconfiguration file on a CD, you would need to remaster the " #~ "ISO image to include your preconfiguration file. See the manual page for " #~ "mkisofs for details. Alternatively, put the preseed file on a floppy, and " #~ "use preseed/file=/floppy/preseed.cfg" #~ msgstr "" #~ "要將預先設定檔放在光碟中,您將需要重新製作 ISO 映像把您的預先設定檔納入。" #~ "請閱讀 mkisofs 的手冊來取得細節資訊。另外,您也可以將預先設定檔放在一張軟" #~ "碟中,然後使用 preseed/file=/floppy/preseed.cfg 參數。" #~ msgid "" #~ "If you'll be booting from a USB memory stick, then you can simply copy " #~ "your preconfiguration file onto the memory stick's filesystem, and edit " #~ "the syslinux.cfg file to add preseed/file=/hd-media/preseed.cfg to the " #~ "kernel boot parameters." #~ msgstr "" #~ "如果您要從 USB 隨身碟上開機,那您可以簡單拷貝您的預先設定檔至儲存的檔案系" #~ "統中,並編輯 syslinux.cfg 檔案,加入 preseed/file=/hd-media/preseed.cfg 至" #~ "核心啟動參數。" #~ msgid "Using Preseeding to Change Default Values" #~ msgstr "使用預先設定來改變預設值" #~ msgid "" #~ "It is also possible to use preseeding to change the default answer for a " #~ "question, but still have the question asked. To do this the " #~ "seen flag must be reset to false " #~ "after setting the value for a template." #~ msgstr "" #~ "您也能使用預先設定來回答預設的對話框,對話框仍會秀出。想要使用此功能必須在" #~ "預先設定樣板之後把seen 設為 false" #~ msgid "" #~ "d-i foo/bar string value\n" #~ "d-i foo/bar seen false" #~ msgstr "" #~ "d-i foo/bar string value\n" #~ "d-i foo/bar seen false" #~ msgid "" #~ "Alpha systems can also be net-booted using the DECNet MOP (Maintenance " #~ "Operations Protocol), but this is not covered here. Presumably, your " #~ "local OpenVMS operator will be happy to assist you should you have some " #~ "burning need to use MOP to boot Linux on your Alpha." #~ msgstr "" #~ "Alpha 系統也能使用 DECNet MOP (Maintenance Operations Protocol) 來進行網路" #~ "開機,但是這裡不使用此技術。相信您的本地 OpenVMS 操作員樂於協助您燒錄,以" #~ "便在您的 Alpha 機器上用 MOP 來開機 Linux 。"