# 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: 2019-02-09 23:05+0000\n"
"PO-Revision-Date: 2005-07-18 14:56+0800\n"
"Last-Translator: Jhang, Jia-Wei<dreamcryer@gmail.com>\n"
"Language-Team: debian-chinese-big5 <debian-chinese-big5@lists.debian.org>\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
#: boot-installer.xml:4
#, no-c-format
msgid "Booting the Installation System"
msgstr "啟動安裝系統"

#. Tag: title
#: boot-installer.xml:9
#, no-c-format
msgid "Booting the Installer on &arch-title;"
msgstr "在 &arch-title; 上啟動安裝程式"

#. Tag: para
#: boot-installer.xml:15
#, no-c-format
msgid ""
"If you have any other operating systems on your system that you wish to keep "
"(dual boot setup), you should make sure that they have been properly shut "
"down <emphasis>before</emphasis> you boot the installer. Installing an "
"operating system while another operating system is in hibernation (has been "
"suspended to disk) could result in loss of, or damage to the state of the "
"suspended operating system which could cause problems when it is rebooted."
msgstr ""

#. Tag: para
#: boot-installer.xml:26
#, no-c-format
msgid ""
"For information on how to boot the graphical installer, see <xref linkend="
"\"graphical\"/>."
msgstr ""

#. Tag: title
#: boot-installer.xml:39
#, fuzzy, no-c-format
msgid "Boot image formats"
msgstr "從 OpenFirmware 開機 CHRP"

#. Tag: para
#: boot-installer.xml:40
#, no-c-format
msgid ""
"On ARM-based systems in most cases one of two formats for boot images is "
"used: a) standard Linux zImage-format kernels (<quote>vmlinuz</quote>) in "
"conjunction with standard Linux initial ramdisks (<quote>initrd.gz</quote>) "
"or b) uImage-format kernels (<quote>uImage</quote>) in conjunction with "
"corresponding initial ramdisks (<quote>uInitrd</quote>)."
msgstr ""

#. Tag: para
#: boot-installer.xml:48
#, no-c-format
msgid ""
"uImage/uInitrd are image formats designed for the U-Boot firmware that is "
"used on many ARM-based systems (mostly 32-bit ones). Older U-Boot versions "
"can only boot files in uImage/uInitrd format, so these are often used on "
"older armel systems. Newer U-Boot versions can - besides booting uImages/"
"uInitrds - also boot standard Linux kernels and ramdisk images, but the "
"command syntax to do that is slightly different from that for booting "
"uImages."
msgstr ""

#. Tag: para
#: boot-installer.xml:57
#, no-c-format
msgid ""
"For systems using a multiplatform kernel, besides kernel and initial ramdisk "
"a so-called device-tree file (or device-tree blob, <quote>dtb</quote>) is "
"needed. It is specific to each supported system and contains a description "
"of the particular hardware. The dtb should be supplied on the device by the "
"firmware, but in practice a newer one often needs to be loaded."
msgstr ""

#. Tag: title
#: boot-installer.xml:68 boot-installer.xml:86
#, fuzzy, no-c-format
#| msgid "Boot Configuration"
msgid "Console configuration"
msgstr "開機設定"

#. Tag: para
#: boot-installer.xml:69
#, no-c-format
msgid ""
"The netboot tarball (<xref linkend=\"boot-armhf-netboot.tar.gz\"/>), and the "
"installer SD-card images (<xref linkend=\"boot-installer-sd-image\"/>) use "
"the (platform-specific) default console that is defined by U-Boot in the "
"<quote>console</quote> variable. In most cases that is a serial console, so "
"on those platforms you by default need a serial console cable to use the "
"installer."
msgstr ""

#. Tag: para
#: boot-installer.xml:78
#, no-c-format
msgid ""
"On platforms which also support a video console, you can modify the U-Boot "
"<quote>console</quote> variable accordingly if you would like the installer "
"to start on the video console."
msgstr ""

#. Tag: para
#: boot-installer.xml:87
#, no-c-format
msgid ""
"The graphical installer is not enabled on the arm64 &d-i; images for stretch "
"so the serial console is used. The console device should be detected "
"automatically from the firmware, but if it is not then after you boot linux "
"from the GRUB menu you will see a <quote>Booting Linux</quote> message, then "
"nothing more."
msgstr ""

#. Tag: para
#: boot-installer.xml:94
#, no-c-format
msgid ""
"If you hit this issue you will need to set a specific console config on the "
"kernel command line. Hit <userinput>e</userinput> for <quote>Edit Kernel "
"command-line</quote> at the GRUB menu, and change "
"<informalexample><screen>--- quiet</screen></informalexample> to "
"<informalexample><screen>console=&lt;device&gt;,&lt;speed&gt;</screen></"
"informalexample> e.g. <informalexample><screen>console=ttyAMA0,115200n8</"
"screen></informalexample>. When finished hit <keycombo><keycap>Control</"
"keycap> <keycap>x</keycap></keycombo> to continue booting with new setting."
msgstr ""

#. Tag: title
#: boot-installer.xml:108
#, fuzzy, no-c-format
#| msgid "Submitting Installation Reports"
msgid "Juno Installation"
msgstr "回報安裝報告"

#. Tag: para
#: boot-installer.xml:109
#, no-c-format
msgid ""
"Juno has UEFI so the install is straightforward. The most practical method "
"is installing from USB stick. You need up to date firmware for USB-booting "
"to work. Builds from <ulink url=\"&url-juno-firmware;\">&url-juno-firmware;</"
"ulink> after March 2015 tested OK. Consult Juno documentation on firmware "
"updating."
msgstr ""

#. Tag: para
#: boot-installer.xml:116
#, no-c-format
msgid ""
"Prepare a standard arm64 CD image on a USB stick. Insert it in one of the "
"USB ports on the back. Plug a serial cable into the upper 9-pin serial port "
"on the back. If you need networking (netboot image) plug the ethernet cable "
"into the socket on the front of the machine."
msgstr ""

#. Tag: para
#: boot-installer.xml:123
#, no-c-format
msgid ""
"Run a serial console at 115200, 8bit no parity, and boot the Juno. It should "
"boot from the USB stick to a GRUB menu. The console config is not correctly "
"detected on Juno so just hitting &enterkey; will show no kernel output. Set "
"the console to <informalexample><screen>console=ttyAMA0,115200n8</screen></"
"informalexample> (as described in <xref linkend=\"arm64-console-setup\"/>). "
"<keycombo><keycap>Control</keycap> <keycap>x</keycap></keycombo> to boot "
"should show you the &d-i; screens, and allow you to proceed with a standard "
"installation."
msgstr ""

#. Tag: title
#: boot-installer.xml:136
#, no-c-format
msgid "Applied Micro Mustang Installation"
msgstr ""

#. Tag: para
#: boot-installer.xml:137
#, no-c-format
msgid ""
"UEFI is available for this machine but it is normally shipped with U-Boot so "
"you will need to either install UEFI firmware first then use standard boot/"
"install methods, or use U-Boot boot methods. You must use a serial console "
"to control the installation because the graphical installer is not enabled "
"on the arm64 architecture."
msgstr ""

#. Tag: para
#: boot-installer.xml:145
#, no-c-format
msgid ""
"The recommended install method is to copy the &d-i; kernel and initrd onto "
"the hard drive, using the openembedded system supplied with the machine, "
"then boot from that to run the installer. Alternatively use TFTP to get the "
"kernel/dtb/initrd copied over and booted (<xref linkend=\"boot-tftp-uboot\"/"
">). After installation, manual changes to boot from the installed image are "
"needed."
msgstr ""

#. Tag: para
#: boot-installer.xml:154
#, no-c-format
msgid ""
"Run a serial console at 115200, 8bit no parity, and boot the machine. Reboot "
"the machine and when you see <quote>Hit any key to stop autoboot:</quote> "
"hit a key to get a Mustang# prompt. Then use U-Boot commands to load and "
"boot the kernel, dtb and initrd."
msgstr ""

#. Tag: title
#: boot-installer.xml:163
#, fuzzy, no-c-format
#| msgid "Booting from TFTP"
msgid "Booting by TFTP"
msgstr "從 TFTP 開機"

# index.docbook:432, index.docbook:786, index.docbook:1338, index.docbook:1819, index.docbook:2242, index.docbook:2338
#. Tag: para
#: boot-installer.xml:169 boot-installer.xml:838 boot-installer.xml:1475
#: boot-installer.xml:1605 boot-installer.xml:1926 boot-installer.xml:2074
#, fuzzy, no-c-format
#| msgid ""
#| "Booting from the network requires that you have a network connection and "
#| "a TFTP network boot server (DHCP, RARP, or BOOTP)."
msgid ""
"Booting from the network requires that you have a network connection and a "
"TFTP network boot server (and probably also a DHCP, RARP, or BOOTP server "
"for automatic network configuration)."
msgstr ""
"要從網路開機，您的機器必須連接上網路和一台 TFTP 網路開機伺服器 (DHCP, RARP 以"
"及 BOOTP)。"

# index.docbook:437, index.docbook:791, index.docbook:1343, index.docbook:1824, index.docbook:2247, index.docbook:2343
#. Tag: para
#: boot-installer.xml:175 boot-installer.xml:844 boot-installer.xml:1481
#: boot-installer.xml:1611 boot-installer.xml:1932 boot-installer.xml:2080
#, no-c-format
msgid ""
"Older systems such as the 715 might require the use of an RBOOT server "
"instead of a BOOTP server."
msgstr "較早的系統如 715 也許需要使用一台 RBOOT 伺服器來取代 BOOTP 伺服器。"

# index.docbook:442, index.docbook:796, index.docbook:1348, index.docbook:1829, index.docbook:2252, index.docbook:2348
#. Tag: para
#: boot-installer.xml:180 boot-installer.xml:849 boot-installer.xml:1486
#: boot-installer.xml:1616 boot-installer.xml:1937 boot-installer.xml:2085
#, fuzzy, no-c-format
#| msgid ""
#| "The installation method to support network booting is described in <xref "
#| "linkend=\"install-tftp\"/>."
msgid ""
"The server-side setup to support network booting is described in <xref "
"linkend=\"install-tftp\"/>."
msgstr "支援的網路開機安裝方法在 <xref linkend=\"install-tftp\"/>。"

#. Tag: title
#: boot-installer.xml:189
#, no-c-format
msgid "TFTP-booting in U-Boot"
msgstr ""

#. Tag: para
#: boot-installer.xml:190
#, no-c-format
msgid ""
"Network booting on systems using the U-Boot firmware consists of three "
"steps: a) configuring the network, b) loading the images (kernel/initial "
"ramdisk/dtb) into memory and c) actually executing the previosly loaded code."
msgstr ""

#. Tag: para
#: boot-installer.xml:196
#, no-c-format
msgid ""
"First you have to configure the network, either automatically via DHCP by "
"running <informalexample><screen>\n"
"setenv autoload no\n"
"dhcp\n"
"</screen></informalexample> or manually by setting several environment "
"variables <informalexample><screen>\n"
"setenv ipaddr &lt;ip address of the client&gt;\n"
"setenv netmask &lt;netmask&gt;\n"
"setenv serverip &lt;ip address of the tftp server&gt;\n"
"setenv dnsip &lt;ip address of the nameserver&gt;\n"
"setenv gatewayip &lt;ip address of the default gateway&gt;\n"
"</screen></informalexample> If you prefer, you can make these settings "
"permanent by running"
msgstr ""

#. Tag: screen
#: boot-installer.xml:203
#, no-c-format
msgid "saveenv"
msgstr "saveenv"

#. Tag: para
#: boot-installer.xml:205
#, no-c-format
msgid ""
"Afterwards you need to load the images (kernel/initial ramdisk/dtb) into "
"memory. This is done with the tftpboot command, which has to be provided "
"with the address at which the image shall be stored in memory. Unfortunately "
"the memory map can vary from system to system, so there is no general rule "
"which addresses can be used for this."
msgstr ""

#. Tag: para
#: boot-installer.xml:213
#, no-c-format
msgid ""
"On some systems, U-Boot predefines a set of environment variables with "
"suitable load addresses: kernel_addr_r, ramdisk_addr_r and fdt_addr_r. You "
"can check whether they are defined by running <informalexample><screen>\n"
"printenv kernel_addr_r ramdisk_addr_r fdt_addr_r\n"
"</screen></informalexample> If they are not defined, you have to check your "
"system's documentation for appropriate values and set them manually. For "
"systems based on Allwinner SunXi SOCs (e.g. the Allwinner A10, architecture "
"name <quote>sun4i</quote> or the Allwinner A20, architecture name "
"<quote>sun7i</quote>), you can e.g. use the following values:"
msgstr ""

#. Tag: screen
#: boot-installer.xml:224
#, no-c-format
msgid ""
"setenv kernel_addr_r 0x46000000\n"
"setenv fdt_addr_r 0x47000000\n"
"setenv ramdisk_addr_r 0x48000000"
msgstr ""
"setenv kernel_addr_r 0x46000000\n"
"setenv fdt_addr_r 0x47000000\n"
"setenv ramdisk_addr_r 0x48000000"

#. Tag: para
#: boot-installer.xml:226
#, no-c-format
msgid ""
"When the load addresses are defined, you can load the images into memory "
"from the previously defined tftp server with"
msgstr ""

#. Tag: screen
#: boot-installer.xml:229
#, no-c-format
msgid ""
"tftpboot ${kernel_addr_r} &lt;filename of the kernel image&gt;\n"
"tftpboot ${fdt_addr_r} &lt;filename of the dtb&gt;\n"
"tftpboot ${ramdisk_addr_r} &lt;filename of the initial ramdisk image&gt;"
msgstr ""

#. Tag: para
#: boot-installer.xml:231
#, no-c-format
msgid ""
"The third part is setting the kernel commandline and actually executing the "
"loaded code. U-Boot passes the content of the <quote>bootargs</quote> "
"environment variable as commandline to the kernel, so any parameters for the "
"kernel and the installer - such as the console device (see <xref linkend="
"\"boot-console\"/>) or preseeding options (see <xref linkend=\"installer-args"
"\"/> and <xref linkend=\"appendix-preseed\"/>) - can be set with a command "
"like <informalexample><screen>\n"
"setenv bootargs console=ttyS0,115200 rootwait panic=10\n"
"</screen></informalexample> The exact command to execute the previously "
"loaded code depends on the image format used. With uImage/uInitrd, the "
"command is <informalexample><screen>\n"
"bootm ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}\n"
"</screen></informalexample> and with native Linux images it is"
msgstr ""

#. Tag: screen
#: boot-installer.xml:244
#, no-c-format
msgid "bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}"
msgstr "bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}"

#. Tag: para
#: boot-installer.xml:246
#, no-c-format
msgid ""
"Note: When booting standard linux images, it is important to load the "
"initial ramdisk image after the kernel and the dtb as U-Boot sets the "
"filesize variable to the size of the last file loaded and the bootz command "
"requires the size of the ramdisk image to work correctly. In case of booting "
"a platform-specific kernel, i.e. a kernel without device-tree, simply omit "
"the ${fdt_addr_r} parameter."
msgstr ""

#. Tag: title
#: boot-installer.xml:257
#, no-c-format
msgid "Pre-built netboot tarball"
msgstr ""

#. Tag: para
#: boot-installer.xml:258
#, no-c-format
msgid ""
"&debian; provides a pre-built tarball (&armmp-netboot-tarball;) that can "
"simply be unpacked on your tftp server and contains all files necessary for "
"netbooting. It also includes a boot script that automates all steps to load "
"the installer. Modern U-Boot versions contain a tftp autoboot feature that "
"becomes active if there is no bootable local storage device (MMC/SD, USB, "
"IDE/SATA/SCSI) and then loads this boot script from the tftp server. "
"Prerequisite for using this feature is that you have a dhcp server in your "
"network which provides the client with the address of the tftp server."
msgstr ""

#. Tag: para
#: boot-installer.xml:270
#, no-c-format
msgid ""
"If you would like to trigger the tftp autoboot feature from the U-Boot "
"commandline, you can use the follwing command:"
msgstr ""

#. Tag: screen
#: boot-installer.xml:273
#, no-c-format
msgid "run bootcmd_dhcp"
msgstr ""

#. Tag: para
#: boot-installer.xml:275
#, no-c-format
msgid ""
"To manually load the bootscript provided by the tarball, you can "
"alternatively issue the following commands at the U-Boot prompt:"
msgstr ""

#. Tag: screen
#: boot-installer.xml:279
#, no-c-format
msgid ""
"setenv autoload no\n"
"dhcp\n"
"tftpboot ${scriptaddr} /debian-installer/armhf/tftpboot.scr\n"
"source ${scriptaddr}"
msgstr ""

# index.docbook:700, index.docbook:2176
#. Tag: title
#: boot-installer.xml:287
#, fuzzy, no-c-format
#| msgid "Booting from USB Memory Stick"
msgid "Booting from USB Memory Stick with UEFI"
msgstr "從 USB 隨身碟開機"

#. Tag: para
#: boot-installer.xml:293 boot-installer.xml:555
#, fuzzy, no-c-format
#| msgid ""
#| "Let's assume you have prepared everything from <xref linkend=\"boot-dev-"
#| "select\"/> and <xref linkend=\"boot-usb-files\"/>. Now just plug your USB "
#| "stick into some free USB connector and reboot the computer. The system "
#| "should boot up, and you should be presented with the <prompt>boot:</"
#| "prompt> prompt. Here you can enter optional boot arguments, or just hit "
#| "&enterkey;."
msgid ""
"If your computer will boot from USB, this will probably be the easiest route "
"for installation. Assuming you have prepared everything from <phrase arch="
"\"any-x86\"><xref linkend=\"boot-dev-select-x86\"/></phrase><phrase arch="
"\"arm64\"><xref linkend=\"boot-dev-select-arm64\"/></phrase> and <xref "
"linkend=\"boot-usb-files\"/>, just plug your USB stick into some free USB "
"connector and reboot the computer. The system should boot up, and unless you "
"have used the flexible way to build the stick and not enabled it, you should "
"be presented with a graphical boot menu (on hardware that supports it). Here "
"you can select various installer options, or just hit &enterkey;."
msgstr ""
"假設您已經準備好了從 <xref linkend=\"boot-dev-select\"/> 到 <xref linkend="
"\"boot-usb-files\"/> 的所有步驟。現在只需要插入您的 USB 隨身碟到一個空的 USB "
"插槽並且重新啟動電腦。系統應該能夠開機，並且您會看到 <prompt>boot:</prompt> "
"提示符號。您可以輸入一些開機選項，或者只是按下 &enterkey;。"

# index.docbook:700, index.docbook:2176
#. Tag: title
#: boot-installer.xml:312
#, fuzzy, no-c-format
#| msgid "Booting from USB memory stick"
msgid "Booting from a USB stick in U-Boot"
msgstr "從 USB 隨身碟開機"

#. Tag: para
#: boot-installer.xml:313
#, no-c-format
msgid ""
"Many modern U-Boot versions have USB support and allow booting from USB mass "
"storage devices such as USB sticks. Unfortunately the exact steps required "
"to do that can vary quite a bit from device to device."
msgstr ""

#. Tag: para
#: boot-installer.xml:320
#, no-c-format
msgid ""
"U-Boot v2014.10 has introduced a common commandline handling and autoboot "
"framework. This allows building generic boot images that work on any system "
"implementing this framework. The &d-i; supports installation from a USB "
"stick on such systems, but unfortunately not all platforms have adopted this "
"new framework yet."
msgstr ""

#. Tag: para
#: boot-installer.xml:329
#, no-c-format
msgid ""
"To build a bootable USB stick for installing &debian;, unpack the hd-media "
"tarball (see <xref linkend=\"where-files\"/>) onto a USB stick formatted "
"with a filesystem supported by the U-Boot version on your device. For modern "
"U-Boot versions, any of FAT16 / FAT32 / ext2 / ext3 / ext4 usually works. "
"Then copy the ISO image file of the first &debian; installation CD or DVD "
"onto the stick."
msgstr ""

#. Tag: para
#: boot-installer.xml:339
#, no-c-format
msgid ""
"The autoboot framework in modern U-Boot versions works similar to the boot "
"ordering options in a PC BIOS, i.e. it checks a list of possible boot "
"devices for a valid boot image and starts the first one it finds. If there "
"is no operating system installed, plugging in the USB stick and powering up "
"the system should result in starting the installer. You can also initiate "
"the USB-boot process any time from the U-Boot prompt by entering the "
"<quote>run bootcmd_usb0</quote> command."
msgstr ""

#. Tag: para
#: boot-installer.xml:349
#, no-c-format
msgid ""
"One problem that can come up when booting from a USB stick while using a "
"serial console can be a console baudrate mismatch. If a console variable is "
"defined in U-Boot, the &d-i; boot script automatically passes it to the "
"kernel to set the primary console device and, if applicable, the console "
"baudrate. Unfortunately the handling of the console variable varies from "
"platform to platform - on some platforms, the console variable includes the "
"baudrate (as in <quote>console=ttyS0,115200</quote>), while on other "
"platforms the console variable contains only the device (as in "
"<quote>console=ttyS0</quote>). The latter case leads to a garbled console "
"output when the default baudrate differs between U-Boot and the kernel. "
"Modern U-Boot versions often use 115200 baud while the kernel still defaults "
"to the traditional 9600 baud. If this happens, you should manually set the "
"console variable to contain the correct baudrate for your system and then "
"start the installer with the <quote>run bootcmd_usb0</quote> command."
msgstr ""

#. Tag: title
#: boot-installer.xml:370
#, no-c-format
msgid "Using pre-built SD-card images with the installer"
msgstr ""

#. Tag: para
#: boot-installer.xml:371
#, no-c-format
msgid ""
"For a number of systems, Debian provides SD card images that contain both U-"
"Boot and the &d-i;. These images are provided in two variants - one for "
"downloading the software packages over the network (available at &armmp-"
"netboot-sd-img;) and one for offline installations using a Debian CD/DVD "
"(available at &armmp-hd-media-sd-img;). To save space and network bandwidth, "
"the images consist of two parts - a system-dependent part named "
"<quote>firmware.&lt;system-type&gt;.img.gz</quote>, and a system-independent "
"part named <quote>partition.img.gz</quote>."
msgstr ""

#. Tag: para
#: boot-installer.xml:382
#, no-c-format
msgid ""
"To create a complete image from the two parts on Linux systems, you can use "
"zcat as follows: <informalexample><screen>zcat firmware.&lt;system-type&gt;."
"img.gz partition.img.gz &gt; complete_image.img</screen></informalexample> "
"On Windows systems, you have to first decompress the two parts separately, "
"which can be done e.g. by using 7-Zip, and then concatenate the decompressed "
"parts together by running the command <informalexample><screen>copy /b "
"firmware.&lt;system-type&gt;.img + partition.img complete_image.img</"
"screen></informalexample> in a Windows CMD.exe window."
msgstr ""

#. Tag: para
#: boot-installer.xml:396
#, no-c-format
msgid ""
"Write the resulting image onto an SD card, e.g. by running the following "
"command on a Linux system: <informalexample><screen>cat complete_image.img "
"&gt; /dev/SD_CARD_DEVICE</screen></informalexample> After plugging the SD "
"card into the target system and powering the system up, the installer is "
"loaded from the SD card. If you use the hd-media variant for offline "
"installations, you must provide the installer with access to the first "
"&debian; CD/DVD on a separate medium, which can e.g. be a CD/DVD ISO image "
"on a USB stick."
msgstr ""

#. Tag: para
#: boot-installer.xml:408
#, no-c-format
msgid ""
"When you come to the partitioning step in the installer (see <xref linkend="
"\"di-partition\"/>), you can delete or replace any previous partitions on "
"the card. Once the installer is started, it runs completely in the system's "
"main memory and does not need to access the SD card anymore, so you can use "
"the full card for installing &debian;. The easiest way to create a proper "
"partition layout on the SD card is to let the installer automatically create "
"one for you (see <xref linkend=\"partman-auto\"/>)."
msgstr ""

# index.docbook:700, index.docbook:2176
#. Tag: title
#: boot-installer.xml:549
#, no-c-format
msgid "Booting from USB Memory Stick"
msgstr "從 USB 隨身碟開機"

# index.docbook:578, index.docbook:951, index.docbook:1764, index.docbook:2018, index.docbook:2372
#. Tag: title
#: boot-installer.xml:573 boot-installer.xml:1089 boot-installer.xml:1690
#: boot-installer.xml:2108
#, no-c-format
msgid "Booting from a CD-ROM"
msgstr "從光碟開機"

# index.docbook:531, index.docbook:584, index.docbook:957, index.docbook:1776, index.docbook:2024, index.docbook:2378
#. Tag: para
#: boot-installer.xml:579 boot-installer.xml:1095 boot-installer.xml:1696
#: boot-installer.xml:2114
#, no-c-format
msgid ""
"If you have a CD set, and if your machine supports booting directly off the "
"CD, great! Simply <phrase arch=\"x86\"> configure your system for booting "
"off a CD as described in <xref linkend=\"boot-dev-select-x86\"/>, </phrase> "
"insert your CD, reboot, and proceed to the next chapter."
msgstr ""
"對於大多數人來說，最快的途徑是使用一套 &debian; CD 光碟套件。如果您有此套件，"
"並且如果您的機器支援直接光碟開機，太棒了！只需要 <phrase arch=\"x86\"> 設定您"
"的系統以光碟開機，請參閱 <xref linkend=\"boot-dev-select-x86\"/>, </phrase> "
"插入您的光碟，重開機，然後繼續下一章。"

# index.docbook:542, index.docbook:595, index.docbook:968, index.docbook:1787, index.docbook:2035, index.docbook:2389
#. Tag: para
#: boot-installer.xml:589 boot-installer.xml:1105 boot-installer.xml:1706
#: boot-installer.xml:2124
#, no-c-format
msgid ""
"Note that certain CD drives may require special drivers, and thus be "
"inaccessible in the early installation stages. If it turns out the standard "
"way of booting off a CD doesn't work for your hardware, revisit this chapter "
"and read about alternate kernels and installation methods which may work for "
"you."
msgstr ""
"注意某些特定的光碟機需要一些特殊的驅動程式，因為他們可能在安裝的早期步驟中無"
"法被存取。如果標準的光碟開機的方法不能用於您的硬體，閱讀本章中關於其他種類的"
"核心以及安裝方法，它們有可能能解決問題。"

# index.docbook:550, index.docbook:603, index.docbook:976, index.docbook:1795, index.docbook:2043, index.docbook:2397
#. Tag: para
#: boot-installer.xml:597 boot-installer.xml:1113 boot-installer.xml:1714
#: boot-installer.xml:2132
#, fuzzy, no-c-format
#| msgid ""
#| "Even if you cannot boot from CD-ROM, you can probably install the "
#| "&debian; system components and any packages you want from CD-ROM. Simply "
#| "boot using a different media, such as floppies. When it's time to install "
#| "the operating system, base system, and any additional packages, point the "
#| "installation system at the CD-ROM drive."
msgid ""
"Even if you cannot boot from CD-ROM, you can probably install the &debian; "
"system components and any packages you want from CD-ROM. Simply boot using a "
"different medium and when it's time to install the operating system, base "
"system, and any additional packages, point the installation system at the CD-"
"ROM drive."
msgstr ""
"即便您不能從光碟開機，依然可以安裝光碟上面的 &debian; 系統組件和所有軟體套"
"件。只需要使用不同的媒介，例如軟碟來開機即可。當安裝作業系統、基礎系統和任意"
"附加的軟體套件時只需指向安裝系統至光碟機即可。"

# index.docbook:558, index.docbook:611, index.docbook:984, index.docbook:1803, index.docbook:2051, index.docbook:2405
#. Tag: para
#: boot-installer.xml:605 boot-installer.xml:1121 boot-installer.xml:1722
#: boot-installer.xml:2140
#, no-c-format
msgid ""
"If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
msgstr ""
"如果您遇到開機方面的問題，請參閱 <xref linkend=\"boot-troubleshooting\"/>。"

#. Tag: title
#: boot-installer.xml:615
#, fuzzy, no-c-format
msgid "Booting from Windows"
msgstr "從 OpenFirmware 開機 CHRP"

#. Tag: para
#: boot-installer.xml:616
#, no-c-format
msgid "To start the installer from Windows, you can either"
msgstr ""

#. Tag: para
#: boot-installer.xml:621
#, fuzzy, no-c-format
#| msgid ""
#| "To boot the installer from hard disk, you must first download and place "
#| "the needed files as described in <xref linkend=\"boot-drive-files\"/>."
msgid ""
"obtain CD-ROM/DVD-ROM<phrase condition=\"bootable-usb\"> or USB memory "
"stick</phrase> installation media as described in <xref linkend=\"official-"
"cdrom\"/><phrase condition=\"bootable-usb\"> respective <xref linkend=\"boot-"
"usb-files\"/></phrase> or"
msgstr ""
"為了從硬碟開機安裝程式，您首先必須按照要求下載並且放置所需的文件，請參閱 "
"<phrase condition=\"bootable-usb\"><xref linkend=\"boot-drive-files\"/></"
"phrase>。"

#. Tag: para
#: boot-installer.xml:629
#, no-c-format
msgid ""
"download a standalone Windows executable, which is available as <ulink url="
"\"&win32-loader-exe;\">tools/win32-loader/stable/win32-loader.exe</ulink> on "
"the &debian; mirrors."
msgstr ""

#. Tag: para
#: boot-installer.xml:638
#, no-c-format
msgid ""
"If you use an installation CD or DVD, a pre-installation program should be "
"launched automatically when you insert the disc. In case Windows does not "
"start it automatically, or if you are using a USB memory stick, you can run "
"it manually by accessing the device and executing <command>setup.exe</"
"command>."
msgstr ""

#. Tag: para
#: boot-installer.xml:646
#, no-c-format
msgid ""
"After the program has been started, a few preliminary questions will be "
"asked and the system will be prepared to reboot into the &debian-gnu; "
"installer."
msgstr ""

#. Tag: title
#: boot-installer.xml:656
#, fuzzy, no-c-format
#| msgid "Booting from MacOS"
msgid "Booting from DOS using loadlin"
msgstr "從 MacOS 開機"

#. Tag: para
#: boot-installer.xml:657
#, no-c-format
msgid ""
"Boot into DOS (not Windows). To do this, you can for instance boot from a "
"recovery or diagnostic disk."
msgstr ""

#. Tag: para
#: boot-installer.xml:662
#, no-c-format
msgid ""
"If you can access the installation CD, change the current drive to the CD-"
"ROM drive, e.g. <informalexample><screen>\n"
"d:\n"
"</screen></informalexample> else make sure you have first prepared your hard "
"disk as explained in <xref linkend=\"files-loadlin\"/>, and change the "
"current drive to it if needed."
msgstr ""

#. Tag: para
#: boot-installer.xml:672
#, no-c-format
msgid ""
"Enter the subdirectory for the flavor you chose, e.g., "
"<informalexample><screen>\n"
"cd \\&x86-install-dir;\n"
"</screen></informalexample> If you prefer using the graphical installer, "
"enter the <filename>gtk</filename> sub-directory. <informalexample><screen>\n"
"cd gtk\n"
"</screen></informalexample> Next, execute <command>install.bat</command>. "
"The kernel will load and launch the installer system."
msgstr ""

#. Tag: title
#: boot-installer.xml:690
#, no-c-format
msgid ""
"Booting from Linux using <command>LILO</command> or <command>GRUB</command>"
msgstr "使用 <command>LILO</command> 或 <command>GRUB</command> 啟動 Linux"

#. Tag: para
#: boot-installer.xml:693
#, no-c-format
msgid ""
"To boot the installer from hard disk, you must first download and place the "
"needed files as described in <xref linkend=\"boot-drive-files\"/>."
msgstr ""
"為了從硬碟開機安裝程式，您首先必須按照要求下載並且放置所需的文件，請參閱 "
"<xref linkend=\"boot-drive-files\"/>。"

#. Tag: para
#: boot-installer.xml:698
#, 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 <filename>netboot/"
"debian-installer/&architecture;/initrd.gz</filename> file and its "
"corresponding kernel <filename>netboot/debian-installer/&architecture;/"
"linux</filename>. This will allow you to repartition the hard disk from "
"which you boot the installer, although you should do so with care."
msgstr ""
"如果您只想用硬碟開機，然後從網路下載其他檔案，您需要下載 <filename>netboot/"
"debian-installer/i386/initrd.gz</filename> 及其對應的核心。這將允許您重新分割"
"您用於開機的硬碟。這裡需要小心操作。"

#. Tag: para
#: boot-installer.xml:708
#, 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 <filename>hd-"
#| "media/initrd.gz</filename> file and its kernel, as well as copy a CD iso "
#| "to the drive (make sure the file is named ending in <literal>.iso</"
#| "literal>). The installer can then boot from the drive and install from "
#| "the CD image, without needing the network."
msgid ""
"Alternatively, if you intend to keep an existing partition on the hard drive "
"unchanged during the install, you can download the <filename>hd-media/initrd."
"gz</filename> file and its kernel, as well as copy a CD (or DVD) iso to the "
"drive (make sure the file is named ending in <literal>.iso</literal>). The "
"installer can then boot from the drive and install from the CD/DVD image, "
"without needing the network."
msgstr ""
"或者，如果您想要保持安裝硬碟原有分割區，可以下載 <filename>hd-media/initrd."
"gz</filename> 檔案及其核心，複製一個光碟 iso 檔到硬碟上 (確保文件名結尾是 "
"<literal>.iso</literal>)。安裝程式就可以不使用網路而從硬碟開機，並且從光碟映"
"像檔上安裝。"

#. Tag: para
#: boot-installer.xml:717
#, no-c-format
msgid ""
"For <command>LILO</command>, you will need to configure two essential things "
"in <filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> to "
"load the <filename>initrd.gz</filename> installer at boot time; </para></"
"listitem> <listitem><para> have the <filename>vmlinuz</filename> kernel use "
"a RAM disk as its root partition. </para></listitem> </itemizedlist> Here is "
"a <filename>/etc/lilo.conf</filename> example:"
msgstr ""
"如果採用 <command>LILO</command>，您需要在 <filename>/etc/lilo.conf</"
"filename> 中設定兩件最基本的事情: <itemizedlist> <listitem><para> 在開機時載"
"入 <filename>initrd.gz</filename> 安裝程式﹔</para></listitem> "
"<listitem><para> 讓 <filename>vmlinuz</filename> 核心使用一個記憶體虛擬磁碟作"
"為它的根分割區。</para></listitem> </itemizedlist> 這裡是一個 <filename>/etc/"
"lilo.conf</filename> 的例子："

#. Tag: screen
#: boot-installer.xml:738
#, no-c-format
msgid ""
"image=/boot/newinstall/vmlinuz\n"
"       label=newinstall\n"
"       initrd=/boot/newinstall/initrd.gz"
msgstr ""
"image=/boot/newinstall/vmlinuz\n"
"       label=newinstall\n"
"       initrd=/boot/newinstall/initrd.gz"

#. Tag: para
#: boot-installer.xml:738
#, no-c-format
msgid ""
"For more details, refer to the <citerefentry><refentrytitle>initrd</"
"refentrytitle> <manvolnum>4</manvolnum></citerefentry> and "
"<citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</"
"manvolnum></citerefentry> man pages. Now run <userinput>lilo</userinput> and "
"reboot."
msgstr ""
"欲獲知更多細節，請參閱 <citerefentry><refentrytitle>initrd</refentrytitle> "
"<manvolnum>4</manvolnum></citerefentry> 和 <citerefentry><refentrytitle>lilo."
"conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> man 手冊。現在執"
"行 <userinput>lilo</userinput> 並且重新啟動。"

#. Tag: para
#: boot-installer.xml:747
#, fuzzy, no-c-format
msgid ""
"The procedure for <command>GRUB1</command> is quite similar. Locate your "
"<filename>menu.lst</filename> in the <filename>/boot/grub/</filename> "
"directory (or sometimes <filename>/boot/boot/grub/</filename>) and add an "
"entry for the installer, for example (assuming <filename>/boot</filename> is "
"on the first partition of the first disk in the system):"
msgstr ""
"採用 <command>GRUB</command> 的設定過程也很相似。在 <filename>/boot/grub/</"
"filename> 目錄下 (有時會是 <filename>/boot/boot/grub/</filename>) 找出您的 "
"<filename>menu.lst</filename>，加入幾行：<informalexample><screen>\n"
"title  New Install\n"
"kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 ramdisk_size=12000\n"
"initrd (hd0,0)/boot/newinstall/initrd.gz\n"
"</screen></informalexample> 並重開機。<phrase condition=\"sarge\">如果開機失"
"敗，您可以嘗試在 <quote>kernel</quote> 行添加 <userinput>devfs=mount,dall</"
"userinput>。</phrase>"

#. Tag: screen
#: boot-installer.xml:755
#, no-c-format
msgid ""
"title  New Install\n"
"root   (hd0,0)\n"
"kernel /boot/newinstall/vmlinuz\n"
"initrd /boot/newinstall/initrd.gz"
msgstr ""
"title  New Install\n"
"root   (hd0,0)\n"
"kernel /boot/newinstall/vmlinuz\n"
"initrd /boot/newinstall/initrd.gz"

#. Tag: para
#: boot-installer.xml:757
#, fuzzy, no-c-format
msgid ""
"The procedure for <command>GRUB2</command> is very similar. The file is "
"named <filename>grub.cfg</filename> instead of <filename>menu.lst</"
"filename>. An entry for the installer would be for instance for example:"
msgstr ""
"採用 <command>GRUB</command> 的設定過程也很相似。在 <filename>/boot/grub/</"
"filename> 目錄下 (有時會是 <filename>/boot/boot/grub/</filename>) 找出您的 "
"<filename>menu.lst</filename>，加入幾行：<informalexample><screen>\n"
"title  New Install\n"
"kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 ramdisk_size=12000\n"
"initrd (hd0,0)/boot/newinstall/initrd.gz\n"
"</screen></informalexample> 並重開機。<phrase condition=\"sarge\">如果開機失"
"敗，您可以嘗試在 <quote>kernel</quote> 行添加 <userinput>devfs=mount,dall</"
"userinput>。</phrase>"

#. Tag: screen
#: boot-installer.xml:763
#, no-c-format
msgid ""
"menuentry 'New Install' {\n"
"insmod part_msdos\n"
"insmod ext2\n"
"set root='(hd0,msdos1)'\n"
"linux /boot/newinstall/vmlinuz\n"
"initrd /boot/newinstall/initrd.gz\n"
"}"
msgstr ""
"menuentry 'New Install' {\n"
"insmod part_msdos\n"
"insmod ext2\n"
"set root='(hd0,msdos1)'\n"
"linux /boot/newinstall/vmlinuz\n"
"initrd /boot/newinstall/initrd.gz\n"
"}"

#. Tag: para
#: boot-installer.xml:765
#, no-c-format
msgid ""
"From here on, there should be no difference between <command>GRUB</command> "
"or <command>LILO</command>."
msgstr ""
"從此之後，採用 <command>GRUB</command> 或 <command>LILO</command> 都沒區別。"

# index.docbook:723, index.docbook:1876, index.docbook:2278, index.docbook:2426
#. Tag: title
#: boot-installer.xml:774 boot-installer.xml:1976
#, no-c-format
msgid "Booting from Floppies"
msgstr "從軟碟開機"

# index.docbook:724, index.docbook:2286
#. Tag: para
#: boot-installer.xml:775 boot-installer.xml:1984
#, no-c-format
msgid ""
"You will have already downloaded the floppy images you needed and created "
"floppies from the images in <xref linkend=\"create-floppy\"/>."
msgstr ""
"您可能已經下載了所需要得軟碟映像，並且根據這些映像建立了軟碟 <xref linkend="
"\"create-floppy\"/>。"

#. Tag: para
#: boot-installer.xml:782
#, no-c-format
msgid ""
"To boot from the installer boot floppy, place it in the primary floppy "
"drive, shut down the system as you normally would, then turn it back on."
msgstr ""
"從軟碟開機安裝程式需要放置軟碟至主軟碟機。按照您平時的習慣關閉系統，然後重新"
"啟動。"

#. Tag: para
#: boot-installer.xml:788
#, fuzzy, no-c-format
msgid ""
"For installing from an LS-120 drive (ATAPI version) with a set of floppies, "
"you need to specify the virtual location for the floppy device. This is done "
"with the <emphasis>root=</emphasis> boot argument, giving the device that "
"the ide-floppy driver maps the device to. For example, if your LS-120 drive "
"is connected as the first IDE device (master) on the second cable, you enter "
"<userinput>install root=/dev/hdc</userinput> at the boot prompt."
msgstr ""
"如果想在 LS-120 磁碟機 (ATAPI 版本) 使用這些軟碟，您需要指定這些軟碟設備的虛"
"擬位址。這個可以透過 <emphasis>root=</emphasis> 開機參數來指定映射的 ide-"
"floppy 磁碟機名稱來完成。例如，如果您的 LS-120 磁碟機連接到第二條排線上的第一"
"個 IDE 設備 (master)，那麼在提示符號下輸入 <userinput>linux root=/dev/hdc</"
"userinput>。從 LS-120 上安裝只為 2.4 及其以後版本的核心支援。"

#. Tag: para
#: boot-installer.xml:798
#, no-c-format
msgid ""
"Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</"
"keycap> <keycap>Delete</keycap></keycombo> does not properly reset the "
"machine, so a <quote>hard</quote> reboot is recommended. If you are "
"installing from an existing operating system (e.g., from a DOS box) you "
"don't have a choice. Otherwise, please do a hard reboot when booting."
msgstr ""
"注意有些機器使用，<keycombo><keycap>Control</keycap> <keycap>Alt</keycap> "
"<keycap>Delete</keycap></keycombo> 不能重新啟動系統，所以建議使用<quote>硬</"
"quote>重開機。如果您從一個既有的作業系統上安裝 (例如從 DOS 上) 您不需要這樣。"
"否則，請用硬重開機的方法來開機。"

#. Tag: para
#: boot-installer.xml:807
#, no-c-format
msgid ""
"The floppy disk will be accessed, and you should then see a screen that "
"introduces the boot floppy and ends with the <prompt>boot:</prompt> prompt."
msgstr ""
"讀完軟碟後，您將看到螢幕上有一段有關開機軟碟的介紹，並且結尾是 <prompt>boot:"
"</prompt> 提示符號。"

#. Tag: para
#: boot-installer.xml:813
#, no-c-format
msgid ""
"Once you press &enterkey;, you should see the message "
"<computeroutput>Loading...</computeroutput>, followed by "
"<computeroutput>Uncompressing Linux...</computeroutput>, and then a "
"screenfull or so of information about the hardware in your system. More "
"information on this phase of the boot process can be found below in <xref "
"linkend=\"kernel-msgs\"/>."
msgstr ""
"一旦您按下 &enterkey;，您應該能夠看到 <computeroutput>Loading...</"
"computeroutput> 消息，並且接下來是 <computeroutput>Uncompressing Linux...</"
"computeroutput>，然後是一些有關您系統的硬體資訊。想知道更多有關這段開機過程的"
"資訊，請參考 <xref linkend=\"kernel-msgs\"/>。"

#. Tag: para
#: boot-installer.xml:822
#, no-c-format
msgid ""
"After booting from the boot floppy, the root floppy is requested. Insert the "
"root floppy and press &enterkey;, and the contents are loaded into memory. "
"The installer program <command>debian-installer</command> is automatically "
"launched."
msgstr ""
"軟碟開機後需要根軟碟。請插入根軟碟並且輸入 &enterkey;，然後其中的內容會被載入"
"記憶體。安裝程式 <command>debian-installer</command> 會自動啟動。"

# index.docbook:274, index.docbook:780, index.docbook:1320, index.docbook:1813, index.docbook:1896, index.docbook:2236, index.docbook:2332
#. Tag: title
#: boot-installer.xml:832 boot-installer.xml:1457 boot-installer.xml:1599
#: boot-installer.xml:1920 boot-installer.xml:2068
#, no-c-format
msgid "Booting with TFTP"
msgstr "用 TFTP 開機"

#. Tag: para
#: boot-installer.xml:857
#, no-c-format
msgid "There are various ways to do a TFTP boot on i386."
msgstr "在 i386 架構上有很多方法用 TFTP 進行開機。"

#. Tag: title
#: boot-installer.xml:863
#, no-c-format
msgid "NIC or Motherboard that support PXE"
msgstr "支援 PXE 的網卡或者主機板"

#. Tag: para
#: boot-installer.xml:864
#, fuzzy, no-c-format
msgid ""
"It could be that your Network Interface Card or Motherboard provides PXE "
"boot functionality. This is a <trademark class=\"trade\">Intel</trademark> "
"re-implementation of TFTP boot. If so, you may be able to configure your "
"BIOS to boot from the network."
msgstr ""
"您的網卡或者主機板可能已經提供了 PXE 開機功能。這 <trademark class=\"trade"
"\">Intel</trademark> TFTP 開機的再實作。如果是這樣，也許可以能夠設定您的 "
"BIOS 來用網路進行開機。"

#. Tag: title
#: boot-installer.xml:875
#, no-c-format
msgid "NIC with Network BootROM"
msgstr "採用 Network BootROM 的網卡"

#. Tag: para
#: boot-installer.xml:876
#, no-c-format
msgid ""
"It could be that your Network Interface Card provides TFTP boot "
"functionality."
msgstr "您的網卡很有可能提供了 TFTP 開機功能。"

#. Tag: para
#: boot-installer.xml:881
#, no-c-format
msgid ""
"Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. "
"Please refer to this document."
msgstr ""
"請讓我們知道 (<email>&email-debian-boot-list;</email>) 您如何操作，並參考此文"
"件。"

#. Tag: title
#: boot-installer.xml:889
#, no-c-format
msgid "Etherboot"
msgstr "Etherboot"

#. Tag: para
#: boot-installer.xml:890
#, no-c-format
msgid ""
"The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> "
"provides bootdiskettes and even bootroms that do a TFTPboot."
msgstr ""
"<ulink url=\"http://www.etherboot.org\">etherboot project</ulink> 提供了為 "
"TFTP 開機所需要的開機軟碟甚至是開機 ROMS 。"

# index.docbook:1943, index.docbook:2477
#. Tag: title
#: boot-installer.xml:900
#, fuzzy, no-c-format
#| msgid "The Boot Prompt"
msgid "The Boot Screen"
msgstr "開機提示"

#. Tag: para
#: boot-installer.xml:901
#, no-c-format
msgid ""
"When the installer boots, you should be presented with a friendly graphical "
"screen showing the &debian; logo and a menu:"
msgstr ""

#. Tag: screen
#: boot-installer.xml:906
#, no-c-format
msgid ""
"&debian-gnu; installer boot menu\n"
"\n"
"Graphical install\n"
"Install\n"
"Advanced options             >\n"
"Help\n"
"Install with speech synthesis"
msgstr ""

#. Tag: para
#: boot-installer.xml:910
#, no-c-format
msgid ""
"This graphical screen will look very slightly different depending on how "
"your computer has booted (BIOS or UEFI), but the same options will be shown."
msgstr ""

#. Tag: para
#: boot-installer.xml:918
#, no-c-format
msgid ""
"Depending on the installation method you are using, the <quote>Graphical "
"install</quote> option may not be available. Bi-arch images additionally "
"have a 64 bit variant for each install option, right below it, thus almost "
"doubling the number of options."
msgstr ""

#. Tag: para
#: boot-installer.xml:925
#, no-c-format
msgid ""
"For a normal installation, select either the <quote>Graphical install</"
"quote> or the <quote>Install</quote> entry &mdash; using either the arrow "
"keys on your keyboard or by typing the first (highlighted) letter &mdash; "
"and press &enterkey; to boot the installer. The <quote>Graphical install</"
"quote> entry is already selected by default."
msgstr ""

#. Tag: para
#: boot-installer.xml:933
#, no-c-format
msgid ""
"The <quote>Advanced options</quote> entry gives access to a second menu that "
"allows to boot the installer in expert mode, in rescue mode and for "
"automated installs."
msgstr ""

#. Tag: para
#: boot-installer.xml:939
#, no-c-format
msgid ""
"If you wish or need to add any boot parameters for either the installer or "
"the kernel, press &tabkey; (BIOS boot), or &ekey; then &downkey; three times "
"then &endkey; (UEFI boot). This will bring the boot command for the selected "
"menu entry and allow you to edit it to suit your needs. Note that the "
"keyboard layout at this point is still QWERTY. The help screens (see below) "
"list some common possible options. Press &enterkey; (BIOS boot) or &f10key; "
"(UEFI boot) to boot the installer with your options; pressing &escapekey; "
"will return you to the boot menu and undo any changes you made."
msgstr ""

#. Tag: para
#: boot-installer.xml:952
#, no-c-format
msgid ""
"Choosing the <quote>Help</quote> entry will result in the first help screen "
"being displayed which gives an overview of all available help screens. To "
"return to the boot menu after the help screens have been displayed, type "
"'menu' at the boot prompt and press &enterkey;. All help screens have a boot "
"prompt at which the boot command can be typed: <informalexample><screen>\n"
"Press F1 for the help index, or ENTER to boot:\n"
"</screen></informalexample> At this boot prompt you can either just press "
"&enterkey; to boot the installer with default options or enter a specific "
"boot command and, optionally, boot parameters. A number of boot parameters "
"which might be useful can be found on the various help screens. If you do "
"add any parameters to the boot command line, be sure to first type the boot "
"method (the default is <userinput>install</userinput>) and a space before "
"the first parameter (e.g., <userinput>install fb=false</userinput>)."
msgstr ""

#. Tag: para
#: boot-installer.xml:970
#, no-c-format
msgid ""
"The keyboard is assumed to have a default American English layout at this "
"point. This means that if your keyboard has a different (language-specific) "
"layout, the characters that appear on the screen may be different from what "
"you'd expect when you type parameters. Wikipedia has a <ulink url=\"&url-us-"
"keymap;\">schema of the US keyboard layout</ulink> which can be used as a "
"reference to find the correct keys to use."
msgstr ""

#. Tag: para
#: boot-installer.xml:980
#, no-c-format
msgid ""
"If you are using a system that has the BIOS configured to use serial "
"console, you may not be able to see the initial graphical splash screen upon "
"booting the installer; you may even not see the boot menu. The same can "
"happen if you are installing the system via a remote management device that "
"provides a text interface to the VGA console. Examples of these devices "
"include the text console of Compaq's <quote>integrated Lights Out</quote> "
"(iLO) and HP's <quote>Integrated Remote Assistant</quote> (IRA)."
msgstr ""

#. Tag: para
#: boot-installer.xml:990
#, no-c-format
msgid ""
"To bypass the graphical boot screen you can either blindly press &escapekey; "
"to get a text boot prompt, or (equally blindly) press <quote>H</quote> "
"followed by &enterkey; to select the <quote>Help</quote> option described "
"above. After that your keystrokes should be echoed at the prompt. To prevent "
"the installer from using the framebuffer for the rest of the installation, "
"you will also want to add <userinput>vga=normal fb=false</userinput> to the "
"boot prompt, as described in the help text."
msgstr ""

#. Tag: title
#: boot-installer.xml:1006
#, no-c-format
msgid "The Graphical Installer"
msgstr ""

#. Tag: para
#: boot-installer.xml:1007
#, no-c-format
msgid ""
"The graphical version of the installer is only available for a limited "
"number of architectures, including &arch-title;. The functionality of the "
"graphical installer is essentially the same as that of the text-based "
"installer as it basically uses the same programs, but with a different "
"frontend."
msgstr ""

#. Tag: para
#: boot-installer.xml:1015
#, no-c-format
msgid ""
"Although the functionality is identical, the graphical installer still has a "
"few significant advantages. The main advantage is that it supports more "
"languages, namely those that use a character set that cannot be displayed "
"with the text-based <quote>newt</quote> frontend. It also has a few "
"usability advantages such as the option to use a mouse, and in some cases "
"several questions can be displayed on a single screen."
msgstr ""

#. Tag: para
#: boot-installer.xml:1024
#, no-c-format
msgid ""
"The graphical installer is available with all CD images and with the hd-"
"media installation method. To boot the graphical installer simply select the "
"relevant option from the boot menu. Expert and rescue mode for the graphical "
"installer can be selected from the <quote>Advanced options</quote> menu. The "
"previously used boot methods <userinput>installgui</userinput>, "
"<userinput>expertgui</userinput> and <userinput>rescuegui</userinput> can "
"still be used from the boot prompt which is shown after selecting the "
"<quote>Help</quote> option in the boot menu."
msgstr ""

#. Tag: para
#: boot-installer.xml:1035
#, no-c-format
msgid ""
"There is also a graphical installer image that can be netbooted. And there "
"is a special <quote>mini</quote> ISO image<footnote id=\"gtk-miniiso-x86\"> "
"<para> The mini ISO image can be downloaded from a &debian; mirror as "
"described in <xref linkend=\"downloading-files\"/>. Look for "
"<filename>netboot/gtk/mini.iso</filename>. </para> </footnote>, which is "
"mainly useful for testing."
msgstr ""

#. Tag: para
#: boot-installer.xml:1048
#, no-c-format
msgid ""
"For &arch-title;, currently only an experimental <quote>mini</quote> ISO "
"image is available<footnote id=\"gtk-miniiso-powerpc\"> <para> The mini ISO "
"image can be downloaded from a &debian; mirror as described in <xref linkend="
"\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. "
"</para> </footnote>. It should work on almost all PowerPC systems that have "
"an ATI graphical card, but is unlikely to work on other systems."
msgstr ""

#. Tag: para
#: boot-installer.xml:1062
#, no-c-format
msgid ""
"Just as with the text-based installer it is possible to add boot parameters "
"when starting the graphical installer."
msgstr ""

#. Tag: para
#: boot-installer.xml:1068
#, no-c-format
msgid ""
"The graphical installer requires significantly more memory to run than the "
"text-based installer: &minimum-memory-gtk;. If insufficient memory is "
"available, it will automatically fall back to the text-based <quote>newt</"
"quote> frontend."
msgstr ""

#. Tag: para
#: boot-installer.xml:1075
#, no-c-format
msgid ""
"If the amount of memory in your system is below &minimum-memory;, the "
"graphical installer may fail to boot at all while booting the text-based "
"installer would still work. Using the text-based installer is recommended "
"for systems with little available memory."
msgstr ""

#. Tag: title
#: boot-installer.xml:1129
#, no-c-format
msgid "CD Contents"
msgstr "光碟的內容"

#. Tag: para
#: boot-installer.xml:1131
#, no-c-format
msgid ""
"There are three basic variations of &debian; Install CDs. The "
"<emphasis>Business Card</emphasis> CD has a minimal installation that will "
"fit on the small form factor CD media. It requires a network connection in "
"order to install the rest of the base installation and make a usable system. "
"The <emphasis>Network Install</emphasis> CD has all of the packages for a "
"base install but requires a network connection to a &debian; mirror site in "
"order to install the extra packages one would want for a complete system . "
"The set of &debian; CDs can install a complete system from the wide range of "
"packages without needing access to the network."
msgstr ""
"有三種基本的 &debian; 安裝光碟衍生品：<emphasis>名片式</emphasis>光碟具有最少"
"量的安裝程式並且可以裝在一小張光碟上。它的安裝需要網路連接來安裝其他部分的基"
"本安裝程式以建立一個可用的系統。<emphasis>網路安裝</emphasis>光碟具有所有基礎"
"安裝所需要的套件但是它還是需要一個能連接到 &debian; 鏡像網站的網路連接來安裝"
"其他的軟體套件來建立一個完全的系統。&debian; 光碟套件則可以不透過網路就可以安"
"裝一個具有各種範圍軟體套件的完全系統。"

#. Tag: para
#: boot-installer.xml:1147
#, no-c-format
msgid ""
"The IA-64 architecture uses the next generation Extensible Firmware "
"Interface (EFI) from Intel. Unlike the traditional x86 BIOS which knows "
"little about the boot device other than the partition table and Master Boot "
"Record (MBR), EFI can read and write files from FAT16 or FAT32 formatted "
"disk partitions. This simplifies the often arcane process of starting a "
"system. The system boot loader and the EFI firmware that supports it have a "
"full filesystem to store the files necessary for booting the machine. This "
"means that the system disk on an IA-64 system has an additional disk "
"partition dedicated to EFI instead of the simple MBR or boot block on more "
"conventional systems."
msgstr ""
"IA-64 使用 Intel 最新的可拓展韌體界面 (Extensible Firmware Interface, EFI)。"
"與傳統的 x86 BIOS 只瞭解分割區表和主開機記錄 (MBR) 而不知道其他開機設備的特點"
"不同，EFI 可以 對 FAT16 和 FAT32 格式的硬碟分割區進行讀寫操作。這個特點簡化了"
"通常很難以理解的系統啟動過程。系統的 boot-loader 以及 EFI 韌體支援一個完全的"
"檔案系統來保存啟動機器所需要的所有檔案。這意味著在一個 IA-64 系統上的系統磁碟"
"具有一個附加的專門為 EFI 服務的磁碟分割區而不是像傳統系統上只是簡單的 MBR 或"
"者開機塊記錄。"

#. Tag: para
#: boot-installer.xml:1163
#, no-c-format
msgid ""
"The &debian; Installer CD contains a small EFI partition where the "
"<command>ELILO</command> bootloader, its configuration file, the installer's "
"kernel, and initial filesystem (initrd) are located. The running system also "
"contains an EFI partition where the necessary files for booting the system "
"reside. These files are readable from the EFI Shell as described below."
msgstr ""
"&debian; CD 包含了一個小型版本的 EFI 分割區來放置其設定檔<command>ELILO</"
"command>、安裝程式核心以及初始的檔案系統 (initrd)。運行的系統同時也包含了一"
"個 EFI 分割區用於放置開機系統所需要的必要檔案。這些檔案可以從 EFI Shell 讀"
"出，描述如下。"

#. Tag: para
#: boot-installer.xml:1172
#, no-c-format
msgid ""
"Most of the details of how <command>ELILO</command> actually loads and "
"starts a system are transparent to the system installer. However, the "
"installer must set up an EFI partition prior to installing the base system. "
"Otherwise, the installation of <command>ELILO</command> will fail, rendering "
"the system un-bootable. The EFI partition is allocated and formatted in the "
"partitioning step of the installation prior to loading any packages on the "
"system disk. The partitioning task also verifies that a suitable EFI "
"partition is present before allowing the installation to proceed."
msgstr ""
"大部分有關 <command>ELILO</command> 如何實際裝入和啟動系統的細節對系統安裝程"
"式是透明的。但是，安裝程式必須設置 EFI 分割區優先級來安裝基本系統。否則 "
"<command>ELILO</command> 的安裝將會失敗並且導致系統不可開機。EFI 分割區是是在"
"分割步驟中被分割出來且格式化的，之後安裝程式就會宰入系統磁碟的所有軟體套件。"
"分割步驟也會在繼續安裝步驟前檢查 EFI 分割區是否合適。"

#. Tag: para
#: boot-installer.xml:1184
#, no-c-format
msgid ""
"The EFI Boot Manager is presented as the last step of the firmware "
"initialization. It displays a menu list from which the user can select an "
"option. Depending on the model of system and what other software has been "
"loaded on the system, this menu may be different from one system to another. "
"There should be at least two menu items displayed, <command>Boot Option "
"Maintenance Menu</command> and <command>EFI Shell (Built-in)</command>. "
"Using the first option is preferred, however, if that option is not "
"available or the CD for some reason does not boot with it, use the second "
"option."
msgstr ""
"EFI Boot Manager 在韌體初始化的最後一步會被啟動。它顯示一個選單列表供使用者選"
"擇。取決於系統的型號並且是否有其他的軟體已經被裝入系統，這個選單在不同系統上"
"可能會不同。在每一個系統上，至少會有兩個選單項，<command>Boot Option "
"Maintenance Menu</command> 與 <command>EFI Shell (Built-in)</command>。建議使"
"用第一個，當然，若該選項不可用或者 CD 由於某種原因沒法啟動，使用第二個。"

#. Tag: title
#: boot-installer.xml:1203
#, no-c-format
msgid "IMPORTANT"
msgstr "重要"

#. Tag: para
#: boot-installer.xml:1204
#, no-c-format
msgid ""
"The EFI Boot Manager will select a default boot action, typically the first "
"menu choice, within a pre-set number of seconds. This is indicated by a "
"countdown at the bottom of the screen. Once the timer expires and the "
"systems starts the default action, you may have to reboot the machine in "
"order to continue the installation. If the default action is the EFI Shell, "
"you can return to the Boot Manager by running <command>exit</command> at the "
"shell prompt."
msgstr ""
"EFI Boot Manager 會在預設的幾秒鐘之後選擇預設的啟動方式，一般是第一選單項。在"
"螢幕底部會有倒計時顯示。時間一到，系統按預設方式啟動，這樣您也許需要重新啟動"
"才能繼續安裝。如果預設是 EFI Shell，您可在提示符號下執行 <command>exit</"
"command> 以返回 Boot Manager。"

#. Tag: title
#: boot-installer.xml:1216
#, no-c-format
msgid "Option 1: Booting from the Boot Option Maintenance Menu"
msgstr "選項 1: 從 Boot Option Maintenance Menu 啟動"

#. Tag: para
#: boot-installer.xml:1223
#, no-c-format
msgid ""
"Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
"display the EFI Boot Manager page and menu after it completes its system "
"initialization."
msgstr ""
"插入光碟到 DVD/CD 光碟機，然後重啟機器。韌體在完成系統初始化後會顯示 EFI "
"Boot Manager 頁面和選單。"

#. Tag: para
#: boot-installer.xml:1229
#, no-c-format
msgid ""
"Select <command>Boot Maintenance Menu</command> from the menu with the arrow "
"keys and press <command>ENTER</command>. This will display a new menu."
msgstr ""
"透過方向鍵選擇 <command>Boot Maintenance Menu</command> 然後按下 "
"<command>ENTER</command>。會顯示一個新選單。"

#. Tag: para
#: boot-installer.xml:1235
#, no-c-format
msgid ""
"Select <command>Boot From a File</command> from the menu with the arrow keys "
"and press <command>ENTER</command>. This will display a list of devices "
"probed by the firmware. You should see two menu lines containing either the "
"label <command>Debian Inst [Acpi ...</command> or <command>Removable Media "
"Boot</command>. If you examine the rest of the menu line, you will notice "
"that the device and controller information should be the same."
msgstr ""
"透過方向鍵選擇 <command>Boot From a File</command>，然後按下 <command>ENTER</"
"command>。將顯示韌體檢測到的設備列表。您會看到兩個選單行，它們包括 "
"<command>Debian Inst [Acpi ...</command> 或 <command>Removable Media Boot</"
"command>標籤。如果您檢查選單行其他部分，會看到對應的設備和控制器資訊。"

#. Tag: para
#: boot-installer.xml:1246
#, no-c-format
msgid ""
"You can choose either of the entries that refer to the CD/DVD drive. Select "
"your choice with the arrow keys and press <command>ENTER</command>. If you "
"choose <command>Removable Media Boot</command> the machine will immediately "
"start the boot load sequence. If you choose <command>Debian Inst [Acpi ...</"
"command> instead, it will display a directory listing of the bootable "
"portion of the CD, requiring you to proceed to the next (additional) step."
msgstr ""
"您可選擇指向 CD/DVD 光碟機的項目。透過方向鍵選擇並按下 <command>ENTER</"
"command>。如果您選擇 <command>Removable Media Boot</command> 機器將進入啟動步"
"驟。如果您選擇 <command>Debian Inst [Acpi ...</command>，它會顯示一個可啟動的"
"光碟目錄列表，要求您進行 (額外的) 下一步。"

#. Tag: para
#: boot-installer.xml:1257
#, no-c-format
msgid ""
"You will only need this step if you chose <command>Debian Inst [Acpi ...</"
"command>. The directory listing will also show <command>[Treat like "
"Removable Media Boot]</command> on the next to the last line. Select this "
"line with the arrow keys and press <command>ENTER</command>. This will start "
"the boot load sequence."
msgstr ""
"您只在選擇 <command>Debian Inst [Acpi ...</command> 時需要這個。目錄列表還會"
"顯示 <command>[Treat like Removable Media Boot]</command> 至最後一行。用方向"
"鍵選擇，並按下 <command>ENTER</command>。這將進入啟動步驟。"

#. Tag: para
#: boot-installer.xml:1269
#, no-c-format
msgid ""
"These steps start the &debian; boot loader which will display a menu page "
"for you to select a boot kernel and options. Proceed to selecting the boot "
"kernel and options."
msgstr ""
"這些步驟啟動的 &debian; boot-loader 會顯示一個選單頁以選擇啟動核心和選項。進"
"入選擇啟動核心和選項。"

#. Tag: title
#: boot-installer.xml:1279
#, no-c-format
msgid "Option 2: Booting from the EFI Shell"
msgstr "選項 2: 從 EFI Shell 啟動"

#. Tag: para
#: boot-installer.xml:1280
#, no-c-format
msgid ""
"If, for some reason, option 1 is not successful, reboot the machine and when "
"the EFI Boot Manager screen appears there should be one option called "
"<command>EFI Shell [Built-in]</command>. Boot the &debian; Installer CD with "
"the following steps:"
msgstr ""
"某些情況下，選項 1 無法成功，重新啟動機器然後在 EFI Boot Manager 畫面出現的時"
"候會有一個選項稱為 <command>EFI Shell [Built-in]</command>。 可以透過如下步驟"
"來啟動 &debian; 安裝程式："

#. Tag: para
#: boot-installer.xml:1291
#, no-c-format
msgid ""
"Insert the CD in the DVD/CD drive and reboot the machine. The firmware will "
"display the EFI Boot Manager page and menu after it completes system "
"initialization."
msgstr ""
"把光碟放入光碟機並重新開機。系統初始化之後韌體將會顯示 EFI Boot Manager 的主"
"頁和選單。"

#. Tag: para
#: boot-installer.xml:1297
#, no-c-format
msgid ""
"Select <command>EFI Shell</command> from the menu with the arrow keys and "
"press <command>ENTER</command>. The EFI Shell will scan all of the bootable "
"devices and display them to the console before displaying its command "
"prompt. The recognized bootable partitions on devices will show a device "
"name of <filename>fs<replaceable>n</replaceable>:</filename>. All other "
"recognized partitions will be named <filename>blk<replaceable>n</"
"replaceable>:</filename>. If you inserted the CD just before entering the "
"shell, this may take a few extra seconds as it initializes the CD drive."
msgstr ""
"選擇 <command>EFI Shell</command> 然後按下 <command>ENTER</command>。EFI "
"Shell 將掃瞄所有的可開機設備，並且在顯示其指令提示符號前在控制台列出它們。被"
"辨認出去有可開機分割區的設備將以 <filename>fs<replaceable>n</replaceable>:</"
"filename> 格式顯示。所有其他辨認出的分割區，將被命名為 "
"<filename>blk<replaceable>n</replaceable>:</filename>。如果您在進入介殼之前就"
"插入光碟，這將花費一些時間以初始化光碟機。"

#. Tag: para
#: boot-installer.xml:1311
#, no-c-format
msgid ""
"Examine the output from the shell looking for the CDROM drive. It is most "
"likely the <filename>fs0:</filename> device although other devices with "
"bootable partitions will also show up as <filename>fs<replaceable>n</"
"replaceable></filename>."
msgstr ""
"在檢查光碟機期間請查看介殼的輸出顯示。一般來說是 <filename>fs0:</filename> 其"
"他具有可開機分割區的設備上也會顯示成 <filename>fs<replaceable>n</"
"replaceable></filename>。"

#. Tag: para
#: boot-installer.xml:1318
#, no-c-format
msgid ""
"Enter <command>fs<replaceable>n</replaceable>:</command> and press "
"<command>ENTER</command> to select that device where <replaceable>n</"
"replaceable> is the partition number for the CDROM. The shell will now "
"display the partition number as its prompt."
msgstr ""
"進入 <command>fs<replaceable>n</replaceable>:</command> 然後按下 "
"<command>ENTER</command> 來選擇設備。這裡 <replaceable>n</replaceable> 是光碟"
"的分割區號。介殼將在提示符號下顯示分割區號。"

#. Tag: para
#: boot-installer.xml:1325
#, no-c-format
msgid ""
"Enter <command>elilo</command> and press <command>ENTER</command>. This will "
"start the boot load sequence."
msgstr ""
"進入 <command>elilo</command> 並按下 <command>ENTER</command>。這將進入啟動步"
"驟。"

#. Tag: para
#: boot-installer.xml:1332
#, no-c-format
msgid ""
"As with option 1, these steps start the &debian; boot loader which will "
"display a menu page for you to select a boot kernel and options. You can "
"also enter the shorter <command>fs<replaceable>n</replaceable>:elilo</"
"command> command at the shell prompt. Proceed to selecting the boot kernel "
"and options."
msgstr ""
"與選項 1 相同，這些步驟也會啟動 &debian; boot-loader，顯示一個選單頁供選擇啟"
"動核心和參數。您可在介殼提示符號下輸入 <command>fs<replaceable>n</"
"replaceable>:elilo</command>簡短指令。進入選擇啟動核心和選項。"

#. Tag: title
#: boot-installer.xml:1346
#, no-c-format
msgid "Installing using a Serial Console"
msgstr "使用序列埠控制台安裝"

#. Tag: para
#: boot-installer.xml:1348
#, no-c-format
msgid ""
"You may choose to perform an install using a monitor and keyboard or using a "
"serial connection. To use a monitor/keyboard setup, select an option "
"containing the string [VGA console]. To install over a serial connection, "
"choose an option containing the string [<replaceable>BAUD</replaceable> baud "
"serial console], where <replaceable>BAUD</replaceable> is the speed of your "
"serial console. Menu items for the most typical baud rate settings on the "
"ttyS0 device are preconfigured."
msgstr ""
"您可選擇使用顯示器與鍵盤或者序列埠連接來進行安裝。要使用顯示器/鍵盤配置，選擇"
"包含 [VGA console] 的選項。要透過序列埠連接，選擇包含 [<replaceable>BAUD</"
"replaceable> baud serial console] 的選項，其中 <replaceable>BAUD</"
"replaceable> 是序列連接速度。選單項裡有大多數常見鮑率的 ttyS0 設備都有預設。"

#. Tag: para
#: boot-installer.xml:1359
#, no-c-format
msgid ""
"In most circumstances, you will want the installer to use the same baud rate "
"as your connection to the EFI console. If you aren't sure what this setting "
"is, you can obtain it using the command <command>baud</command> at the EFI "
"shell."
msgstr ""
"大多時候，您會讓安裝程式使用與連接 EFI 控制台相同的鮑率。如果您不知如何設定，"
"可以在 EFI shell 透過 <command>baud</command> 指令取得。"

#. Tag: para
#: boot-installer.xml:1366
#, no-c-format
msgid ""
"If there is not an option available that is configured for the serial device "
"or baud rate you would like to use, you may override the console setting for "
"one of the existing menu options. For example, to use a 57600 baud console "
"over the ttyS1 device, enter <command>console=ttyS1,57600n8</command> into "
"the <classname>Boot:</classname> text window."
msgstr ""
"如果沒有序列配置的選項或者您要使用的鮑率，可以覆蓋某個選單項裡面的既有鮑率。"
"例如，使用 57600 鮑率覆蓋 ttyS1 設備，輸入 <command>console=ttyS1,57600n8</"
"command> 到 <classname>Boot:</classname> 文字視窗。"

#. Tag: para
#: boot-installer.xml:1377
#, no-c-format
msgid ""
"Most IA-64 boxes ship with a default console setting of 9600 baud. This "
"setting is rather slow, and the normal installation process will take a "
"significant time to draw each screen. You should consider either increasing "
"the baud rate used for performing the installation, or performing a Text "
"Mode installation. See the <classname>Params</classname> help menu for "
"instructions on starting the installer in Text Mode."
msgstr ""
"大多數 IA-64 機器配備預設 9600 鮑率的控制台。這個速率太慢，普通安裝過程將花費"
"明顯的時間來更新每個螢幕。您要麼透過提高鮑率以提升安裝效率，要麼使用文字模式"
"安裝。參考 <classname>Params</classname> 說明選單，取得啟動文字模式安裝的指"
"導。"

#. Tag: para
#: boot-installer.xml:1386
#, no-c-format
msgid ""
"If you select the wrong console type, you will be able to select the kernel "
"and enter parameters but both the display and your input will go dead as "
"soon as the kernel starts, requiring you to reboot before you can begin the "
"installation."
msgstr ""
"如果您選擇了錯誤的控制台類型，即便可以選擇核心和輸入參數，但顯示與輸入將在內"
"核啟動後死掉，只有重新啟動才能開始安裝。"

#. Tag: title
#: boot-installer.xml:1395
#, no-c-format
msgid "Selecting the Boot Kernel and Options"
msgstr "選擇啟動核心與選項"

#. Tag: para
#: boot-installer.xml:1397
#, no-c-format
msgid ""
"The boot loader will display a form with a menu list and a text window with "
"a <classname>Boot:</classname> prompt. The arrow keys select an item from "
"the menu and any text typed at the keyboard will appear in the text window. "
"There are also help screens which can be displayed by pressing the "
"appropriate function key. The <classname>General</classname> help screen "
"explains the menu choices and the <classname>Params</classname> screen "
"explains the common command line options."
msgstr ""
"開機程式會顯示一個表單，具有選單列與包含 <classname>Boot:</classname> 提示符"
"號的文字視窗。用方向鍵選擇選單項並且鍵盤輸入的字元將顯示在鮑率視窗。輸入適當"
"的功能鍵會顯示說明視窗。<classname>普通的</classname>說明視窗解釋選單選項，"
"<classname>Params</classname>視窗解釋命令列參數。"

#. Tag: para
#: boot-installer.xml:1409
#, no-c-format
msgid ""
"Consult the <classname>General</classname> help screen for the description "
"of the kernels and install modes most appropriate for your installation. You "
"should also consult <xref linkend=\"boot-parms\"/> below for any additional "
"parameters that you may want to set in the <classname>Boot:</classname> text "
"window. The kernel version you choose selects the kernel version that will "
"be used for both the installation process and the installed system. If you "
"encounter kernel problems with the installation, you may also have those "
"same problems with the system you install. The following two steps will "
"select and start the install:"
msgstr ""
"查詢 <classname>General</classname> 說明頁面，瞭解核心的說明和安裝對應的模"
"式。您還應該查詢 <xref linkend=\"boot-parms\"/>，瞭解在文字視窗中需要設置的額"
"外參數 <classname>Boot:</classname>，您選擇的核心版本將會用在安裝過程和安裝好"
"的系統中。如果安裝時碰到核心問題，在安裝好的系統中也會出現。以下兩步選擇和開"
"始安裝："

#. Tag: para
#: boot-installer.xml:1427
#, no-c-format
msgid ""
"Select the kernel version and installation mode most appropriate to your "
"needs with the arrow keys."
msgstr "使用方向鍵選擇您需要的核心版本和適合的安裝模式。"

#. Tag: para
#: boot-installer.xml:1432
#, no-c-format
msgid ""
"Enter any boot parameters by typing at the keyboard. The text will be "
"displayed directly in the text window. This is where kernel parameters (such "
"as serial console settings) are specified."
msgstr ""
"在鍵盤上輸入任何啟動參數。這些文字將直接顯示在文字視窗。這是核心參數 (如同序"
"列控制台) 指定的。"

#. Tag: para
#: boot-installer.xml:1439
#, no-c-format
msgid ""
"Press <command>ENTER</command>. This will load and start the kernel. The "
"kernel will display its usual initialization messages followed by the first "
"screen of the &debian; Installer."
msgstr ""
"按下 <command>ENTER</command>。會載入並啟動核心。核心在 &debian; 安裝程式的第"
"一個螢幕顯示常規的初始化資訊。"

#. Tag: para
#: boot-installer.xml:1448 boot-installer.xml:1585
#, no-c-format
msgid ""
"Proceed to the next chapter to continue the installation where you will set "
"up the language locale, network, and disk partitions."
msgstr "進入到下一章繼續安裝本地語言，網路和磁碟分割區。"

#. Tag: para
#: boot-installer.xml:1459
#, fuzzy, no-c-format
msgid ""
"Booting an IA-64 system from the network is similar to a CD boot. The only "
"difference is how the installation kernel is loaded. The EFI Boot Manager "
"can load and start programs from a server on the network. Once the "
"installation kernel is loaded and starts, the system install will proceed "
"through the same steps as the CD install with the exception that the "
"packages of the base install will be loaded from the network rather than the "
"CD drive."
msgstr ""
"在 IA64 系統上面從網路開機很像從光碟上開機。唯一的區別是如何裝入核心。EFI "
"Boot Manager 可以裝入並且從網路伺服器開始程式。一旦安裝核心被載入並且啟動，系"
"統的安裝將和光碟安裝步驟相同，只是基本軟體套件將從網路裝入而不是光碟機。"

#. Tag: para
#: boot-installer.xml:1494
#, fuzzy, no-c-format
msgid ""
"Network booting an IA-64 system requires two architecture-specific actions. "
"On the boot server, DHCP and TFTP must be configured to deliver "
"<command>elilo</command>. On the client a new boot option must be defined in "
"the EFI boot manager to enable loading over a network."
msgstr ""
"用網路將一台 IA64 系統開機需要兩個架構相關的操作。在開機伺服器上，DHCP 和 "
"TFTP 必須設定成可以傳送 <command>elilo</command>。在客戶端，必須在 EFI Boot "
"Manager 定義新的開機選項來啟動網路網路以下載核心。"

#. Tag: title
#: boot-installer.xml:1505
#, no-c-format
msgid "Configuring the Server"
msgstr "配置網路伺服器"

#. Tag: para
#: boot-installer.xml:1506
#, fuzzy, no-c-format
msgid ""
"A suitable TFTP entry for network booting an IA-64 system looks something "
"like this: <informalexample><screen>\n"
"host mcmuffin {\n"
"        hardware ethernet 00:30:6e:1e:0e:83;\n"
"        fixed-address 10.0.0.21;\n"
"        filename \"debian-installer/ia64/elilo.efi\";\n"
"}\n"
"</screen></informalexample> Note that the goal is to get <command>elilo.efi</"
"command> running on the client."
msgstr ""
"一個用於 ia64 系統的合適呵網路開機 TFTP 選項應該看起來像這樣： "
"<informalexample><screen>\n"
"host mcmuffin {\n"
"        hardware ethernet 00:30:6e:1e:0e:83;\n"
"        fixed-address 10.0.0.21;\n"
"        filename \"debian-installer/ia64/elilo.efi\";\n"
"}\n"
"</screen></informalexample> 注意到目標是讓 <command>elilo.efi</command> 在客"
"戶端運行。"

#. Tag: para
#: boot-installer.xml:1516
#, no-c-format
msgid ""
"Extract the <filename>netboot.tar.gz</filename> file into the directory used "
"as the root for your tftp server. Typical tftp root directories include "
"<filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. This "
"will create a <filename>debian-installer</filename> directory tree "
"containing the boot files for an IA-64 system."
msgstr ""
"使用 root 解壓縮 <filename>netboot.tar.gz</filename> 檔案到您的 tftp 伺服器。"
"典型的 tftp 根目錄包括 <filename>/var/lib/tftp</filename> 和 <filename>/"
"tftpboot</filename>。這將建立 <filename>debian-installer</filename> 目錄樹，"
"它包括 IA-64 系統需要的開機檔案。"

#. Tag: screen
#: boot-installer.xml:1526
#, no-c-format
msgid ""
"# cd /var/lib/tftp\n"
"# tar xvfz /home/user/netboot.tar.gz\n"
"./\n"
"./debian-installer/\n"
"./debian-installer/ia64/\n"
"[...]"
msgstr ""
"# cd /var/lib/tftp\n"
"# tar xvfz /home/user/netboot.tar.gz\n"
"./\n"
"./debian-installer/\n"
"./debian-installer/ia64/\n"
"[...]"

#. Tag: para
#: boot-installer.xml:1526
#, no-c-format
msgid ""
"The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</"
"filename> file that should work for most configurations. However, should you "
"need to make changes to this file, you can find it in the <filename>debian-"
"installer/ia64/</filename> directory. It is possible to have different "
"config files for different clients by naming them using the client's IP "
"address in hex with the suffix <filename>.conf</filename> instead of "
"<filename>elilo.conf</filename>. See documentation provided in the "
"<classname>elilo</classname> package for details."
msgstr ""
"<filename>netboot.tar.gz</filename> 包含 <filename>elilo.conf</filename> 可以"
"在大多數的設定下工作。另外，要修改這個檔案，您可以在 <filename>debian-"
"installer/ia64/</filename> 目錄中找到。這只需要按照客戶端 IP 位址的 16 進位命"
"名這些檔案並且以 <filename>.conf</filename> 為副檔名取代 <filename>elilo."
"conf</filename>。請查看 <classname>elilo</classname> 軟體套件附帶的文件以取得"
"細節。"

#. Tag: title
#: boot-installer.xml:1543
#, no-c-format
msgid "Configuring the Client"
msgstr "配置客戶端"

#. Tag: para
#: boot-installer.xml:1544
#, no-c-format
msgid ""
"To configure the client to support TFTP booting, start by booting to EFI and "
"entering the <guimenu>Boot Option Maintenance Menu</guimenu>. <itemizedlist> "
"<listitem><para> Add a boot option. </para></listitem> <listitem><para> You "
"should see one or more lines with the text <guimenuitem>Load File "
"[Acpi()/.../Mac()]</guimenuitem>. If more than one of these entries exist, "
"choose the one containing the MAC address of the interface from which you'll "
"be booting. Use the arrow keys to highlight your choice, then press enter. </"
"para></listitem> <listitem><para> Name the entry <userinput>Netboot</"
"userinput> or something similar, save, and exit back to the boot options "
"menu. </para></listitem> </itemizedlist> You should see the new boot option "
"you just created, and selecting it should initiate a DHCP query, leading to "
"a TFTP load of <filename>elilo.efi</filename> from the server."
msgstr ""
"如果要設定支援 TFTP 開機的客戶端，只需要開機至 EFI，然後進入 <guimenu>Boot "
"Option Maintenance Menu</guimenu>。<itemizedlist> <listitem><para> 加入一個開"
"機選項。</para></listitem> <listitem><para> 您會看到一行或多行含有 "
"<guimenuitem>Load File [Acpi()/.../Mac()]</guimenuitem> 的文字。如果存在一個"
"以上的選項，選擇您需要您要啟動的機器的 MAC 位址的選項。使用方向鍵反白選擇，然"
"後按 Enter。</para></listitem> <listitem><para> 為此選項命名，如 "
"<userinput>Netboot</userinput> 或者相似的，儲存然後退回至開機選項選單。</"
"para></listitem> </itemizedlist> 您現在應該能夠看到剛剛建立的新開機選項，選擇"
"後應該會初始化一個 DHCP 查詢，然後會從伺服器載入 <filename>elilo.efi</"
"filename>。"

#. Tag: para
#: boot-installer.xml:1576
#, no-c-format
msgid ""
"The boot loader will display its prompt after it has downloaded and "
"processed its configuration file. At this point, the installation proceeds "
"with the same steps as a CD install. Select a boot option as in above and "
"when the kernel has completed installing itself from the network, it will "
"start the &debian; Installer."
msgstr ""
"在下載並且處理設定檔後，boot-loader 將顯示它的提示符號。從這裡開始，安裝過程"
"將和光碟安裝是同樣的過程。完成從網路的自動安裝核心後，選擇一個如同前文提到的"
"開機選項，它將開始 &debian; 安裝程式。"

#. Tag: title
#: boot-installer.xml:1630
#, no-c-format
msgid "S/390 Limitations"
msgstr "S/390 的限制"

#. Tag: para
#: boot-installer.xml:1631
#, no-c-format
msgid ""
"In order to run the installation system a working network setup and ssh "
"session is needed on S/390."
msgstr "為了在 S/390 上安裝系統，需要網路來和 ssh 連線。"

#. Tag: para
#: boot-installer.xml:1636
#, no-c-format
msgid ""
"The booting process starts with a network setup that prompts you for several "
"network parameters. If the setup is successful, you will login to the system "
"by starting an ssh session which will launch the standard installation "
"system."
msgstr ""
"開機過程開始時候會要求一些參數來進行網路設定。如果設定成功，您將會透過ssh 連"
"線登錄進入系統，並且開始標準系統安裝。"

#. Tag: title
#: boot-installer.xml:1647
#, no-c-format
msgid "S/390 Boot Parameters"
msgstr "S/390 開機參數"

#. Tag: para
#: boot-installer.xml:1648
#, fuzzy, no-c-format
msgid ""
"On S/390 you can append boot parameters in the parm file. This file can "
"either be in ASCII or EBCDIC format. It needs to be fixed-width with 80 "
"characters per line. A sample parm file <filename>parmfile.debian</filename> "
"is provided with the installation images. If a parameter is too long to fit "
"into the 80 characters limit it can simply be continued in the first column "
"of the next line. All the lines are concatenated without spaces when being "
"passed to the kernel."
msgstr ""
"在 S/390 上您可以在參數檔案下面附加一些開機參數。這個檔案可以是 ASCII 或者 "
"EBCDIC 編碼。請閱讀 <ulink url=\"&url-s390-devices;\"> 設備驅動程式以及安裝命"
"令</ulink> 來取得更多有關 S/390 特定的開機參數。"

#. Tag: para
#: boot-installer.xml:1665
#, no-c-format
msgid ""
"If you boot the installer in a logical partition (LPAR) or virtual machine "
"(VM) where a lot of devices are visible, you can instruct the kernel to "
"restrict the list to a fixed set of devices. This is advised for the "
"installer's boot process if a lot of disks are visible, most likely in LPAR "
"mode. The <quote>cio_ignore</quote> option supports both a blacklist (to "
"only disallow a few devices) and a whitelist (to only allow specific "
"devices): <informalexample role=\"example\"><screen>\n"
" # blacklist: just ignore the two devices 300 and 301\n"
" cio_ignore=0.0.0300-0.0.0301\n"
" # whitelist: ignore everything but 1150, FD00, FD01 and FD02\n"
" cio_ignore=all,!0.0.1150,!0.0.fd00-0.0.fd02\n"
"</screen></informalexample> Please note that all devices numbers' hex digits "
"need to be specified in lower case. Furthermore if this boot parameter is "
"used all devices need to be listed: this includes at least disks, network "
"devices and the console. To be considered during the installer's boot "
"process the above option needs to be added to <filename>parmfile.debian</"
"filename>."
msgstr ""

#. Tag: para
#: boot-installer.xml:1729
#, fuzzy, no-c-format
msgid ""
"Currently, the only &arch-title; subarchitectures that support CD-ROM "
"booting are PReP/CHRP (though not all systems) and New World PowerMacs. On "
"PowerMacs, hold the <keycap>c</keycap> key, or else the combination of "
"<keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Shift</keycap>, "
"and <keycap>Delete</keycap> keys together while booting to boot from the "
"factory default CD/DVD drive."
msgstr ""
"目前來說，&arch-title; 下的子架構只有 PReP 和 New World PowerMacs 支援光碟開"
"機。在 PowerMacs 下從光碟上開機時，按住 <keycap>c</keycap> 鍵，或者組合鍵 "
"<keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Shift</keycap>, "
"和 <keycap>Delete</keycap> 。"

#. Tag: para
#: boot-installer.xml:1738
#, no-c-format
msgid ""
"To boot a PowerMac from an external Firewire CD/DVD drive invoke Open "
"Firmware prompt first (see <xref linkend=\"invoking-openfirmware\"/>), then "
"type <informalexample><screen>\n"
"0 &gt; boot fw/node/sbp-2/disk:,\\install\\yaboot\n"
"</screen></informalexample> for an alternative way to boot from the internal "
"factory default CD/DVD drive type"
msgstr ""

#. Tag: screen
#: boot-installer.xml:1749
#, no-c-format
msgid "0 &gt; boot cd:,\\install\\yaboot"
msgstr "0 &gt; boot cd:,\\install\\yaboot"

#. Tag: para
#: boot-installer.xml:1751
#, no-c-format
msgid ""
"OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers "
"relied on a Mac OS ROM CD boot driver to be present on the CD, and a free-"
"software version of this driver is not available. All OldWorld systems have "
"floppy drives, so use the floppy drive to launch the installer, and then "
"point the installer to the CD for the needed files."
msgstr ""
"OldWorld Powermacs 不能從 &debian; 光碟開機，因為 OldWorld 電腦要求光碟片上存"
"有 MacOSROM CD 開機驅動程式，但是目前還沒有自由的版本。所有的 OldWorld 系統具"
"有軟碟驅動程式，因此可以使用軟碟驅動程式來啟動安裝程式，然後讓安裝程式從 CD "
"上選擇所需要的文件。"

#. Tag: para
#: boot-installer.xml:1760
#, no-c-format
msgid ""
"To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key "
"immediately after pressing the power-on button, when SmartFirmware prompt "
"appears, type"
msgstr ""

#. Tag: screen
#: boot-installer.xml:1766
#, no-c-format
msgid "boot cd install/pegasos"
msgstr "boot cd install/pegasos"

#. Tag: para
#: boot-installer.xml:1768
#, no-c-format
msgid ""
"On YDL Powerstation machine, press <keycap>s</keycap> immediately after "
"<quote>Press 's' to enter Open Firmware</quote> message, when SLOF prompt "
"appears type"
msgstr ""

#. Tag: screen
#: boot-installer.xml:1773
#, no-c-format
msgid "0 &gt; boot cdrom"
msgstr "0 &gt; boot cdrom"

#. Tag: title
#: boot-installer.xml:1779
#, no-c-format
msgid "Booting from Hard Disk"
msgstr "從硬碟開機"

# index.docbook:1591, index.docbook:2097
#. Tag: para
#: boot-installer.xml:1785
#, no-c-format
msgid ""
"Booting from an existing operating system is often a convenient option; for "
"some systems it is the only supported method of installation."
msgstr ""
"從一個已存在的作業系統上開機通常是一個方便的選擇﹔對於一些系統來說，這則是唯"
"一支援的安裝方法。"

# index.docbook:1597, index.docbook:2103
#. Tag: para
#: boot-installer.xml:1791
#, fuzzy, no-c-format
#| msgid ""
#| "To boot the installer from hard disk, you will have already completed "
#| "downloading and placing the needed files in <xref linkend=\"boot-drive-"
#| "files\"/>."
msgid ""
"To boot the installer from hard disk, you will have already completed "
"downloading and placing the needed files as described in <xref linkend="
"\"boot-drive-files\"/>."
msgstr ""
"如果要從硬碟上啟動安裝程式，您也許已經在 <xref linkend=\"boot-drive-files\"/"
"> 處下載並且在 <xref linkend=\"boot-drive-files\"/> 安置了所需檔案。"

#. Tag: title
#: boot-installer.xml:1811
#, no-c-format
msgid "Booting OldWorld PowerMacs from MacOS"
msgstr "從 OldWorld PowerMacs 的 MacOS 上開機"

#. Tag: para
#: boot-installer.xml:1812
#, no-c-format
msgid ""
"If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to "
"boot into the installation system. Double click the <guiicon>BootX</guiicon> "
"application icon. Click on the <guibutton>Options</guibutton> button and "
"select <guilabel>Use Specified RAM Disk</guilabel>. This will give you the "
"chance to select the <filename>ramdisk.image.gz</filename> file. You may "
"need to select the <guilabel>No Video Driver</guilabel> checkbox, depending "
"on your hardware. Then click the <guibutton>Linux</guibutton> button to shut "
"down MacOS and launch the installer."
msgstr ""
"如果您在 <xref linkend=\"files-oldworld\"/> 中設定好了 BootX，您可以使用它啟"
"動並進入安裝系統。雙擊 <guiicon>BootX</guiicon> 應用程式圖示。點擊 "
"<guibutton>Options</guibutton> 按鈕並且選擇 <guilabel>Use Specified RAM "
"Disk</guilabel>。這將可以讓您選擇 <filename>ramdisk.image.gz</filename> 檔"
"案。也許根據您的硬體情況需要選擇 <guilabel>No Video Driver</guilabel> 選擇"
"框。然後點擊 <guibutton>Linux</guibutton> 按鈕，來關閉 MacOS 以及啟動安裝程"
"序。"

#. Tag: title
#: boot-installer.xml:1830
#, no-c-format
msgid "Booting NewWorld Macs from OpenFirmware"
msgstr "從 NewWorld Macs 的 OpenFirmware 開機"

#. Tag: para
#: boot-installer.xml:1831
#, fuzzy, no-c-format
#| msgid ""
#| "You will have already placed the <filename>vmlinux</filename>, "
#| "<filename>initrd.gz</filename>, <filename>yaboot</filename>, and "
#| "<filename>yaboot.conf</filename> files at the root level of your HFS "
#| "partition in <xref linkend=\"files-newworld\"/>. Restart the computer, "
#| "and immediately (during the chime) hold down the <keycap>Option</keycap>, "
#| "<keycap>Command (cloverleaf/Apple)</keycap>, <keycap>o</keycap>, and "
#| "<keycap>f</keycap> keys all together. After a few seconds you will be "
#| "presented with the Open Firmware prompt. At the prompt, type "
#| "<informalexample><screen>\n"
#| "0 &gt; boot hd:<replaceable>x</replaceable>,yaboot\n"
#| "</screen></informalexample> replacing <replaceable>x</replaceable> with "
#| "the partition number of the HFS partition where the kernel and yaboot "
#| "files were placed, followed by a &enterkey;. On some machines, you may "
#| "need to use <userinput>ide0:</userinput> instead of <userinput>hd:</"
#| "userinput>. In a few more seconds you will see a yaboot prompt "
#| "<informalexample><screen>\n"
#| "boot:\n"
#| "</screen></informalexample> At yaboot's <prompt>boot:</prompt> prompt, "
#| "type either <userinput>install</userinput> or <userinput>install "
#| "video=ofonly</userinput> followed by a &enterkey;. The "
#| "<userinput>video=ofonly</userinput> argument is for maximum "
#| "compatibility; you can try it if <userinput>install</userinput> doesn't "
#| "work. The Debian installation program should start."
msgid ""
"You will have already placed the <filename>vmlinux</filename>, "
"<filename>initrd.gz</filename>, <filename>yaboot</filename>, and "
"<filename>yaboot.conf</filename> files at the root level of your HFS "
"partition in <xref linkend=\"files-newworld\"/>. You will now have to boot "
"into OpenFirmware (see <xref linkend=\"invoking-openfirmware\"/>). At the "
"prompt, type <informalexample><screen>\n"
"0 &gt; boot hd:<replaceable>x</replaceable>,yaboot\n"
"</screen></informalexample> replacing <replaceable>x</replaceable> with the "
"partition number of the HFS partition where the kernel and yaboot files were "
"placed, followed by a &enterkey;. On some machines, you may need to use "
"<userinput>ide0:</userinput> instead of <userinput>hd:</userinput>. In a few "
"more seconds you will see a yaboot prompt <informalexample><screen>\n"
"boot:\n"
"</screen></informalexample> At yaboot's <prompt>boot:</prompt> prompt, type "
"either <userinput>install</userinput> or <userinput>install video=ofonly</"
"userinput> followed by a &enterkey;. The <userinput>video=ofonly</userinput> "
"argument is for maximum compatibility; you can try it if <userinput>install</"
"userinput> doesn't work. The &debian; installation program should start."
msgstr ""
"您也許已經按照 <filename>vmlinux</filename>, <filename>initrd.gz</filename>, "
"<filename>yaboot</filename> 和 <filename>yaboot.conf</filename> 在 HFS 分割區"
"的根層次放置好了 <xref linkend=\"files-newworld\"/> 檔案。請重新啟動電腦，並"
"且立即 (在發聲時) 同時按住 <keycap>Option</keycap>, <keycap>Command "
"(cloverleaf/Apple)</keycap>, <keycap>o</keycap>, 和 <keycap>f</keycap> 鍵。過"
"幾秒鐘後，將進入 Open Firmware 提示符號。在提示符號下，輸入： "
"<informalexample><screen>\n"
"0 &gt; boot hd:<replaceable>x</replaceable>,yaboot\n"
"</screen></informalexample> 以放置核心和 yaboot 檔案的 HFS 分割區號來代替 "
"<replaceable>x</replaceable> 然後按下 &enterkey;。在某些機器上，您也許需要時"
"用 <userinput>ide0:</userinput> 來代替 <userinput>hd:</userinput>，在接下來的"
"幾秒鐘內，將會看到一個提示符號 <informalexample><screen>\n"
"boot:\n"
"</screen></informalexample> 在 yaboot 的 <prompt>boot:</prompt> 提示符號下，"
"輸入 <userinput>install</userinput> 或者 <userinput>install video=ofonly</"
"userinput> 然後點擊 &enterkey;。 <userinput>video=ofonly</userinput> 參數是用"
"於最大可能的相容性﹔您可以在 <userinput>install</userinput> 無法運作的情況下"
"嘗試使用它。&debian; 安裝程式應該立刻啟動。"

# index.docbook:700, index.docbook:2176
#. Tag: title
#: boot-installer.xml:1863
#, no-c-format
msgid "Booting from USB memory stick"
msgstr "從 USB 隨身碟開機"

#. Tag: para
#: boot-installer.xml:1864
#, no-c-format
msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
msgstr "目前，New World PowerMac 系統支援從 USB 開機。"

#. Tag: para
#: boot-installer.xml:1870
#, fuzzy, no-c-format
#| msgid ""
#| "Make sure you have prepared everything from <xref linkend=\"boot-usb-files"
#| "\"/>. To boot a Macintosh system from a USB stick, you will need to use "
#| "the Open Firmware prompt, since Open Firmware does not search USB storage "
#| "devices by default. To get to the prompt, hold down "
#| "<keycombo><keycap>Command</keycap> <keycap>Option</keycap> <keycap>o</"
#| "keycap> <keycap>f</keycap></keycombo> all together while booting (see "
#| "<xref linkend=\"invoking-openfirmware\"/>)."
msgid ""
"Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/"
">. To boot a Macintosh system from a USB stick, you will need to use the "
"Open Firmware prompt, since Open Firmware does not search USB storage "
"devices by default. See <xref linkend=\"invoking-openfirmware\"/>."
msgstr ""
"確認您已經準備就緒 <xref linkend=\"boot-usb-files\"/>。要從 USB 隨身碟開機 "
"Macintosh 系統，即使 Open Firmware 預設不搜索 USB 隨身碟設備，您也需要使用 "
"Open Firmware 提示符號。要得到提示符號，在啟動時按住 "
"<keycombo><keycap>Command</keycap> <keycap>Option</keycap> <keycap>o</"
"keycap> <keycap>f</keycap></keycombo> (請參閱 <xref linkend=\"invoking-"
"openfirmware\"/>)。"

#. Tag: para
#: boot-installer.xml:1879
#, no-c-format
msgid ""
"You will need to work out where the USB storage device appears in the device "
"tree, since at the moment <command>ofpath</command> cannot work that out "
"automatically. Type <userinput>dev / ls</userinput> and <userinput>devalias</"
"userinput> at the Open Firmware prompt to get a list of all known devices "
"and device aliases. On the author's system with various types of USB stick, "
"paths such as <filename>usb0/disk</filename>, <filename>usb0/hub/disk</"
"filename>, <filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and "
"<filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work."
msgstr ""
"您還需要算出 USB 隨身碟設備在設備樹上的位置，因為現在 <command>ofpath</"
"command> 無法自動計算。鍵入 <userinput>dev / ls</userinput> 和 "
"<userinput>devalias</userinput> 到 Open Firmware 提示符號下，得到所有的已知設"
"備和設備別名。在筆者的系統上有各種 USB 隨身碟，路徑諸如 <filename>usb0/disk</"
"filename>, <filename>usb0/hub/disk</filename>, <filename>/pci@f2000000/"
"usb@1b,1/disk@1</filename>，和 <filename>/pci@f2000000/usb@1b,1/hub@1/"
"disk@1</filename> 。"

#. Tag: para
#: boot-installer.xml:1891
#, no-c-format
msgid ""
"Having worked out the device path, use a command like this to boot the "
"installer: <informalexample><screen>\n"
"boot <replaceable>usb0/disk</replaceable>:<replaceable>2</replaceable>,\\\\:"
"tbxi\n"
"</screen></informalexample> The <replaceable>2</replaceable> matches the "
"Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image "
"earlier, and the <userinput>,\\\\:tbxi</userinput> part instructs Open "
"Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. "
"<command>yaboot</command>) in the directory previously blessed with "
"<command>hattrib -b</command>."
msgstr ""
"得到設備路徑之後，用類似下面的指令啟動安裝程式： <informalexample><screen>\n"
"boot <replaceable>usb0/disk</replaceable>:<replaceable>2</replaceable>,\\\\:"
"tbxi\n"
"</screen></informalexample> <replaceable>2</replaceable> 吻合 Apple_HFS 或 "
"Apple_Bootstrap 分割區上，之前所複製啟動映像，<userinput>,\\\\:tbxi</"
"userinput> 部分指示 Open Firmware 從具有 ``tbxi'' 類型的 HFS 檔案開機(如 "
"<command>yaboot</command>) 位於前面使用 bless 目錄 <command>hattrib -b</"
"command>。"

#. Tag: para
#: boot-installer.xml:1905
#, no-c-format
msgid ""
"The system should now boot up, and you should be presented with the "
"<prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, "
"or just hit &enterkey;."
msgstr ""
"系統應該可以開機，然後您會看到 <prompt>boot:</prompt> 提示符號。這裡您可以輸"
"入啟動參數，或者只按下 &enterkey;。"

#. Tag: para
#: boot-installer.xml:1911
#, no-c-format
msgid ""
"This boot method is new, and may be difficult to get to work on some "
"NewWorld systems. If you have problems, please file an installation report, "
"as explained in <xref linkend=\"submit-bug\"/>."
msgstr ""
"這個是新的啟動方法，可能無法在一些 NewWorld 系統上工作。如果您遇到問題，請寫"
"下安裝報告，請參閱 <xref linkend=\"submit-bug\"/>。"

#. Tag: para
#: boot-installer.xml:1945
#, no-c-format
msgid "Currently, PReP and New World PowerMac systems support netbooting."
msgstr "目前來說，PReP 以及 New World PowerMac 系統支援網路開機。"

#. Tag: para
#: boot-installer.xml:1949
#, fuzzy, no-c-format
msgid ""
"On machines with Open Firmware, such as NewWorld Power Macs, enter the boot "
"monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command "
"<informalexample><screen>\n"
"0 &gt; boot enet:0\n"
"</screen></informalexample> If this doesn't work, you might have to add the "
"filename like this: <informalexample><screen>\n"
"0 &gt; boot enet:0,yaboot\n"
"</screen></informalexample> PReP and CHRP boxes may have different ways of "
"addressing the network. On a PReP machine, you should try "
"<informalexample><screen>\n"
"boot net:<replaceable>server_ipaddr</replaceable>,<replaceable>file</"
"replaceable>,<replaceable>client_ipaddr</replaceable>\n"
"</screen></informalexample> On some PReP systems (e.g. Motorola PowerStack "
"machines) the command <userinput>help boot</userinput> may give a "
"description of syntax and available options."
msgstr ""
"在 Open Firmware 機器上，例如 NewWorld Power Macs，進入開機監視器 (請參閱 "
"<xref linkend=\"invoking-openfirmware\"/>) 並且使用指令 <command>boot "
"enet:0</command>。PReP 以及 CHRP 可能使用不同的途徑來確認網路。在一台 PReP 機"
"器上，您應該嘗試 <userinput>boot <replaceable>server_ipaddr</replaceable>,"
"<replaceable>file</replaceable>,<replaceable>client_ipaddr</replaceable></"
"userinput>。"

#. Tag: para
#: boot-installer.xml:1977
#, no-c-format
msgid ""
"Booting from floppies is supported for &arch-title;, although it is "
"generally only applicable for OldWorld systems. NewWorld systems are not "
"equipped with floppy drives, and attached USB floppy drives are not "
"supported for booting."
msgstr ""
"&arch-title; 支援從軟碟開機，儘管它本來只適合 OldWorld 系統。NewWorld 系統並"
"沒有安裝軟碟機，而且加裝的 USB 軟碟並不支援開機。"

#. Tag: para
#: boot-installer.xml:1989
#, no-c-format
msgid ""
"To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it "
"in floppy drive after shutting the system down, and before pressing the "
"power-on button."
msgstr ""
"若需要從 <filename>boot-floppy-hfs.img</filename> 軟碟開機，請在關閉系統後、"
"按下電源開關前把它放到軟碟機內。"

#. Tag: para
#: boot-installer.xml:1995
#, no-c-format
msgid ""
"For those not familiar with Macintosh floppy operations: a floppy placed in "
"the machine prior to boot will be the first priority for the system to boot "
"from. A floppy without a valid boot system will be ejected, and the machine "
"will then check for bootable hard disk partitions."
msgstr ""
"對於不熟悉 Macintosh 軟碟操作的人來說：一個放在軟碟機的軟碟將取得第一優先開機"
"順序。一個沒有有效開機系統的軟碟將會被退出，並且機器將檢查硬碟分割區。"

#. Tag: para
#: boot-installer.xml:2002
#, no-c-format
msgid ""
"After booting, the <filename>root.bin</filename> floppy is requested. Insert "
"the root floppy and press &enterkey;. The installer program is automatically "
"launched after the root system has been loaded into memory."
msgstr ""
"開機之後需要含有 <filename>root.bin</filename> 的軟碟。插入開機軟碟並且按下 "
"&enterkey;。安裝程式將在根系統被裝入記憶體後自動啟動。"

#. Tag: title
#: boot-installer.xml:2013
#, no-c-format
msgid "PowerPC Boot Parameters"
msgstr "PowerPC 開機參數"

#. Tag: para
#: boot-installer.xml:2014
#, no-c-format
msgid ""
"Many older Apple monitors used a 640x480 67Hz mode. If your video appears "
"skewed on an older Apple monitor, try appending the boot argument "
"<userinput>video=atyfb:vmode:6</userinput> , which will select that mode for "
"most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to "
"<userinput>video=aty128fb:vmode:6</userinput> ."
msgstr ""
"許多比較老的 Apple 顯示器使用 640x480 67Hz 模式。如果您的畫面在這些老 Apple "
"顯示器上是扭曲的，請嘗試加入開機參數 <userinput>video=atyfb:vmode:6</"
"userinput> 。它將為大多數 Mach64 和 Rage 顯示設備選擇合適的模式。對於 Rage "
"128 來說，請改變其值為 <userinput>video=aty128fb:vmode:6</userinput> 。"

#. Tag: title
#: boot-installer.xml:2026
#, no-c-format
msgid "Booting a ppc64el machine"
msgstr ""

#. Tag: para
#: boot-installer.xml:2027
#, no-c-format
msgid "How to boot a ppc64el machine:"
msgstr ""

#. Tag: title
#: boot-installer.xml:2033
#, no-c-format
msgid "Petitboot"
msgstr "Petitboot"

#. Tag: para
#: boot-installer.xml:2034
#, no-c-format
msgid ""
"Petitboot is a platform independent bootloader based on the Linux kexec. "
"Petitboot supports loading kernel, initrd and device tree files from any "
"Linux mountable filesystem, plus can load files from the network using the "
"FTP, SFTP, TFTP, NFS, HTTP and HTTPS protocols. Petitboot can boot any "
"operating system that includes kexec boot support."
msgstr ""

#. Tag: para
#: boot-installer.xml:2042
#, no-c-format
msgid ""
"Petitboot looks for bootloader configuration files on mountable devices in "
"the system, and can also be configured to use boot information from a DHCP "
"server."
msgstr ""

#. Tag: para
#: boot-installer.xml:2093
#, fuzzy, no-c-format
msgid ""
"On machines with OpenBoot, simply enter the boot monitor on the machine "
"which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use "
"the command <userinput>boot net</userinput> to boot from a TFTP and RARP "
"server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:"
"dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server. You can pass "
"extra boot parameters to &d-i; at the end of the <userinput>boot</userinput> "
"command."
msgstr ""
"在有 OpenBoot 的機器上，簡單地進入安裝機器的開機監視器，(請參閱 <xref "
"linkend=\"invoking-openboot\"/>)。請使用指令 <userinput>boot net</userinput> "
"來從 TFTP 和 RARP 伺服器開機，或者也可以用 <userinput>boot net:bootp</"
"userinput> 或 <userinput>boot net:dhcp</userinput> 來從 TFTP 和 DHCP 服務器開"
"機。一些比較老的 OpenBoot 版本需要使用設備名稱， 例如 <userinput>boot le()</"
"userinput>﹔這些可能不支援 DHCP。"

#. Tag: para
#: boot-installer.xml:2147
#, fuzzy, no-c-format
msgid ""
"Most OpenBoot versions support the <userinput>boot cdrom</userinput> command "
"which is simply an alias to boot from the SCSI device on ID 6 (or the "
"secondary master for IDE based systems)."
msgstr ""
"大多數 OpenBoot 版本支援 <userinput>boot cdrom</userinput> 指令。它其實是從 "
"ID 為 6 的 SCSI 設備進行開機的一個別名。(對於 IDE 系統來說，它是第二個主硬"
"碟)。在較早的 OpenBoot 版本上，您可能必須使用實際的設備名稱，因為它們不支援這"
"個特殊的指令。注意據說在 Sun4m (例如 Sparc 10s 和 Sparc 20s) 系統上用光碟開機"
"有些問題。"

#. Tag: title
#: boot-installer.xml:2156
#, no-c-format
msgid "IDPROM Messages"
msgstr "IDPROM 訊息"

#. Tag: para
#: boot-installer.xml:2157
#, no-c-format
msgid ""
"If you cannot boot because you get messages about a problem with "
"<quote>IDPROM</quote>, then it's possible that your NVRAM battery, which "
"holds configuration information for you firmware, has run out. See the "
"<ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink> for more "
"information."
msgstr ""
"如果您由於得到一個有關 <quote>IDPROM</quote> 問題的消息並且不能開機，這可能"
"是 NVRAM 電池已經用光。通常它為韌體保持設定資訊。檢查 <ulink url=\"&url-sun-"
"nvram-faq;\">Sun NVRAM 常見問答集</ulink> 以取得更多資訊。"

#. Tag: title
#: boot-installer.xml:2176
#, no-c-format
msgid "Accessibility"
msgstr ""

#. Tag: para
#: boot-installer.xml:2177
#, no-c-format
msgid ""
"Some users may need specific support because of e.g. some visual impairment. "
"<phrase arch=\"ia64;powerpc;ppc64el;x86\">USB braille displays are detected "
"automatically (not serial displays connected via a serial-to-USB converter), "
"but most other</phrase> <phrase arch=\"arm;hppa;mips;mipsel;mips64el;sparc"
"\">Most</phrase> accessibility features have to be enabled manually. <phrase "
"arch=\"x86\">On machines that support it, the boot menu emits beeps when it "
"is ready to receive keystrokes. It beeps once on BIOS systems, and beeps "
"twice on UEFI systems.</phrase> Some boot parameters can <phrase arch="
"\"x86\">then</phrase> be appended to enable accessibility features<phrase "
"arch=\"x86\"> (see also <xref linkend=\"boot-screen\"/>)</phrase>. Note that "
"on most architectures the boot loader interprets your keyboard as a QWERTY "
"keyboard."
msgstr ""

#. Tag: title
#: boot-installer.xml:2197
#, no-c-format
msgid "Installer front-end"
msgstr ""

#. Tag: para
#: boot-installer.xml:2198
#, no-c-format
msgid ""
"The &debian; installer supports several front-ends for asking questions, "
"with varying convenience for accessibility: notably, <userinput>text</"
"userinput> uses plain text while <userinput>newt</userinput> uses text-based "
"dialog boxes. The choice can be made at the boot prompt, see the "
"documentation for <userinput>DEBIAN_FRONTEND</userinput> in <xref linkend="
"\"installer-args\"/>."
msgstr ""

#. Tag: title
#: boot-installer.xml:2210
#, no-c-format
msgid "USB Braille Displays"
msgstr ""

#. Tag: para
#: boot-installer.xml:2211
#, no-c-format
msgid ""
"USB braille displays should be automatically detected. A textual version of "
"the installer will then be automatically selected, and support for the "
"braille display will be automatically installed on the target system. You "
"can thus just press &enterkey; at the boot menu. Once <classname>brltty</"
"classname> is started, you can choose a braille table by entering the "
"preference menu. Documentation on key bindings for braille devices is "
"available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</"
"classname> website</ulink>."
msgstr ""

#. Tag: title
#: boot-installer.xml:2226
#, no-c-format
msgid "Serial Braille Displays"
msgstr ""

#. Tag: para
#: boot-installer.xml:2227
#, no-c-format
msgid ""
"Serial braille displays cannot safely be automatically detected (since that "
"may damage some of them). You thus need to append the "
"<userinput>brltty=<replaceable>driver</replaceable>,<replaceable>port</"
"replaceable></userinput> boot parameter to tell <classname>brltty</"
"classname> which driver and port it should use. <replaceable>driver</"
"replaceable> should be replaced by the two-letter driver code for your "
"terminal (see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>). "
"<replaceable>port</replaceable> should be replaced by the name of the serial "
"port the display is connected to, <userinput>ttyS0</userinput> is the "
"default, <userinput>ttyUSB0</userinput> can be typically used when using a "
"serial-to-USB converter. A third parameter can be provided, to choose the "
"name of the braille table to be used (see the <ulink url=\"&url-brltty-"
"manual;\">BRLTTY manual</ulink>); the English table is the default. Note "
"that the table can be changed later by entering the preference menu. A "
"fourth parameter can be provided to pass parameters to the braille driver, "
"such as <userinput>protocol=foo</userinput> which is needed for some rare "
"models. Documentation on key bindings for braille devices is available on "
"the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> "
"website</ulink>."
msgstr ""

#. Tag: title
#: boot-installer.xml:2254 boot-installer.xml:3309
#, no-c-format
msgid "Software Speech Synthesis"
msgstr ""

#. Tag: para
#: boot-installer.xml:2255
#, no-c-format
msgid ""
"Support for software speech synthesis is available on all installer images "
"which have the graphical installer, i.e. all netinst, CD and DVD images, and "
"the netboot gtk variant. It can be activated by selecting it in the boot "
"menu by typing <userinput>s</userinput> &enterkey;. The textual version of "
"the installer will then be automatically selected, and support for software "
"speech synthesis will be automatically installed on the target system."
msgstr ""

#. Tag: para
#: boot-installer.xml:2264
#, no-c-format
msgid ""
"If several sound cards are detected, you will be prompted to press "
"&enterkey; when you hear speech from the desired sound card."
msgstr ""

#. Tag: para
#: boot-installer.xml:2269
#, no-c-format
msgid ""
"The first question (language) is spoken in english, and the remainder of "
"installation is spoken in the selected language (if available in "
"<classname>espeak</classname>)."
msgstr ""

#. Tag: para
#: boot-installer.xml:2275
#, no-c-format
msgid ""
"The default speech rate is quite slow. To make it faster, press "
"<keycombo><keycap>CapsLock</keycap><keycap>6</keycap></keycombo>. To make it "
"slower, press <keycombo><keycap>CapsLock</keycap><keycap>5</keycap></"
"keycombo>. The default volume should be medium. To make it louder, press "
"<keycombo><keycap>CapsLock</keycap><keycap>2</keycap></keycombo>. To make it "
"quieter, press <keycombo><keycap>CapsLock</keycap><keycap>1</keycap></"
"keycombo>. To get more details on the browsing shortcuts, see the <ulink url="
"\"&url-speakup-guide;\">Speakup guide</ulink>. To just accept the default "
"answer for a question, simply press <keycap>Enter</keycap> at the prompt. To "
"provide an empty answer for a question, type <userinput>!</userinput> at the "
"prompt. To get back to the previous question, type <userinput>&lt;</"
"userinput> at the prompt."
msgstr ""

#. Tag: title
#: boot-installer.xml:2303
#, no-c-format
msgid "Hardware Speech Synthesis"
msgstr ""

#. Tag: para
#: boot-installer.xml:2304
#, no-c-format
msgid ""
"Support for hardware speech synthesis devices is available on all installer "
"images which have the graphical installer, i.e. all netinst, CD and DVD "
"images, and the netboot gtk variant. You thus need to select a "
"<quote>Graphical install</quote> entry in the boot menu."
msgstr ""

#. Tag: para
#: boot-installer.xml:2311
#, no-c-format
msgid ""
"Hardware speech synthesis devices cannot be automatically detected. You thus "
"need to append the <userinput>speakup.synth=<replaceable>driver</"
"replaceable></userinput> boot parameter to tell <classname>speakup</"
"classname> which driver it should use. <replaceable>driver</replaceable> "
"should be replaced by the driver code for your device (see <ulink url=\"&url-"
"speakup-guide;\">driver code list</ulink>). The textual version of the "
"installer will then be automatically selected, and support for the speech "
"synthesis device will be automatically installed on the target system."
msgstr ""

#. Tag: title
#: boot-installer.xml:2326
#, no-c-format
msgid "Board Devices"
msgstr ""

#. Tag: para
#: boot-installer.xml:2327
#, no-c-format
msgid ""
"Some accessibility devices are actual boards that are plugged inside the "
"machine and that read text directly from the video memory. To get them to "
"work framebuffer support must be disabled by using the <userinput arch="
"\"x86\">vga=normal</userinput> <userinput>fb=false</userinput> boot "
"parameter. This will however reduce the number of available languages."
msgstr ""

#. Tag: para
#: boot-installer.xml:2335
#, no-c-format
msgid ""
"If desired a textual version of the bootloader can be activated before "
"adding the boot parameter by typing <userinput>h</userinput> &enterkey;."
msgstr ""

#. Tag: title
#: boot-installer.xml:2343
#, no-c-format
msgid "High-Contrast Theme"
msgstr ""

#. Tag: para
#: boot-installer.xml:2344
#, no-c-format
msgid ""
"For users with low vision, the installer can use a high-contrast color theme "
"that makes it more readable. To enable it, you can use the <quote>Dark "
"theme</quote> entry from the boot screen with the <userinput>d</userinput> "
"shortcut, or append the <userinput>theme=dark</userinput> boot parameter."
msgstr ""

#. Tag: title
#: boot-installer.xml:2355
#, no-c-format
msgid "Zoom"
msgstr ""

#. Tag: para
#: boot-installer.xml:2356
#, no-c-format
msgid ""
"For users with low vision, the graphical installer has a very basic zoom "
"support: the <keycombo><keycap>Control</keycap> <keycap>+</keycap></"
"keycombo> and <keycombo><keycap>Control</keycap> <keycap>-</keycap></"
"keycombo> shortcuts increase and decrease the font size."
msgstr ""

#. Tag: title
#: boot-installer.xml:2366
#, no-c-format
msgid "Expert install, rescue mode, automated install"
msgstr ""

#. Tag: para
#: boot-installer.xml:2367
#, no-c-format
msgid ""
"Expert, Rescue, and Automated installation choices are also available with "
"accessibility support. To access them, one has to first enter the "
"<quote>Advanced options</quote> submenu from the boot menu by typing "
"<userinput>a</userinput>. When using a BIOS system (the boot menu will have "
"beeped only once), this has to be followed by &enterkey; ; for UEFI systems "
"(the boot menu will have beeped twice) that must not be done. Then, to "
"enable speech synthesis, <userinput>s</userinput> can optionally be pressed "
"(followed again by &enterkey; on BIOS systems but not on UEFI systems). From "
"there, various shortcuts can be used: <userinput>x</userinput> for expert "
"installation, <userinput>r</userinput> for rescue mode, or <userinput>a</"
"userinput> for automated installation. Again these need to be followed by "
"&enterkey; when using a BIOS system."
msgstr ""

#. Tag: para
#: boot-installer.xml:2382
#, no-c-format
msgid ""
"The automated install choice allows to install &debian; completely "
"automatically by using preseeding, whose source can be entered after "
"accessibility features get started. Preseeding itself is documented in <xref "
"linkend=\"appendix-preseed\"/>."
msgstr ""

#. Tag: title
#: boot-installer.xml:2392
#, no-c-format
msgid "Accessibility of the installed system"
msgstr ""

#. Tag: para
#: boot-installer.xml:2393
#, no-c-format
msgid ""
"Documentation on accessibility of the installed system is available on the "
"<ulink url=\"&url-debian-wiki-accessibility;\">Debian Accessibility wiki "
"page</ulink>."
msgstr ""

# index.docbook:1943, index.docbook:2477
#. Tag: title
#: boot-installer.xml:2407
#, no-c-format
msgid "Boot Parameters"
msgstr "開機參數"

#. Tag: para
#: boot-installer.xml:2408
#, no-c-format
msgid ""
"Boot parameters are Linux kernel parameters which are generally used to make "
"sure that peripherals are dealt with properly. For the most part, the kernel "
"can auto-detect information about your peripherals. However, in some cases "
"you'll have to help the kernel a bit."
msgstr ""
"開機參數是 Linux 核心的參數。一般用於確保周邊設備能夠正確地運行。對於其中的大"
"多數部分來說，核心可以自動檢查周邊設備的相關資訊。但是在某些情況下，您可能需"
"要給核心一點小小的幫助。"

#. Tag: para
#: boot-installer.xml:2415
#, no-c-format
msgid ""
"If this is the first time you're booting the system, try the default boot "
"parameters (i.e., don't try setting parameters) and see if it works "
"correctly. It probably will. If not, you can reboot later and look for any "
"special parameters that inform the system about your hardware."
msgstr ""
"如果這是您第一次開機系統，嘗試預設的開機參數 (即：不要輸入任何參數) 並且檢查"
"是否工作正確。大部分情況下應該如此，如果不是，可以重新啟動，並且檢查需要告訴"
"系統什麼樣的特定參數。"

#. Tag: para
#: boot-installer.xml:2422
#, no-c-format
msgid ""
"Information on many boot parameters can be found in the <ulink url=\"http://"
"www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, "
"including tips for obscure hardware. This section contains only a sketch of "
"the most salient parameters. Some common gotchas are included below in <xref "
"linkend=\"boot-troubleshooting\"/>."
msgstr ""
"有關很多開機參數的資訊可以參閱 <ulink url=\"http://www.tldp.org/HOWTO/"
"BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>，其中包括一些老舊硬體"
"的解決方法。這一節只描述一些對最常用的基本參數。一些常見的問題描述見 <xref "
"linkend=\"boot-troubleshooting\"/>。"

#. Tag: title
#: boot-installer.xml:2434
#, no-c-format
msgid "Boot console"
msgstr ""

#. Tag: para
#: boot-installer.xml:2436
#, fuzzy, no-c-format
#| msgid ""
#| "If you are booting with a serial console, generally the kernel will "
#| "autodetect this<phrase arch=\"mipsel\"> (although not on DECstations)</"
#| "phrase>. If you have a videocard (framebuffer) and a keyboard also "
#| "attached to the computer which you wish to boot via serial console, you "
#| "may have to pass the <userinput>console=<replaceable>device</"
#| "replaceable></userinput> argument to the kernel, where "
#| "<replaceable>device</replaceable> is your serial device, which is usually "
#| "something like <filename>ttyS0</filename>."
msgid ""
"If you are booting with a serial console, generally the kernel will "
"autodetect this. If you have a videocard (framebuffer) and a keyboard also "
"attached to the computer which you wish to boot via serial console, you may "
"have to pass the <userinput>console=<replaceable>device</replaceable></"
"userinput> argument to the kernel, where <replaceable>device</replaceable> "
"is your serial device, which is usually something like <filename>ttyS0</"
"filename>."
msgstr ""
"如果您透過序列控制台開機，一般來說核心將自動檢測 <phrase arch=\"mipsel\"> (盡"
"管不是在一台 DECstations 上面)</phrase>。如果您有一塊顯示卡 (framebuffer) 和"
"一塊鍵盤，透過序列埠附加於想開機的電腦上面，也許需要傳遞 "
"<userinput>console=<replaceable>device</replaceable></userinput> 參數給核"
"心， <replaceable>device</replaceable> 是序列埠設備。通常類似於 "
"<filename>ttyS0</filename>。"

#. Tag: para
#: boot-installer.xml:2448
#, no-c-format
msgid ""
"You may need to specify parameters for the serial port, such as speed and "
"parity, for instance <userinput>console=ttyS0,9600n8</userinput>; other "
"typical speeds may be 57600 or 115200. Be sure to specify this option after "
"<quote>---</quote>, so that it is copied into the bootloader configuration "
"for the installed system (if supported by the installer for the bootloader)."
msgstr ""

#. Tag: para
#: boot-installer.xml:2456
#, fuzzy, no-c-format
#| msgid ""
#| "If you are booting with a serial console, generally the kernel will "
#| "autodetect this<phrase arch=\"mipsel\"> (although not on DECstations)</"
#| "phrase>. If you have a videocard (framebuffer) and a keyboard also "
#| "attached to the computer which you wish to boot via serial console, you "
#| "may have to pass the <userinput>console=<replaceable>device</"
#| "replaceable></userinput> argument to the kernel, where "
#| "<replaceable>device</replaceable> is your serial device, which is usually "
#| "something like <filename>ttyS0</filename>."
msgid ""
"In order to ensure the terminal type used by the installer matches your "
"terminal emulator, the parameter <userinput>TERM=<replaceable>type</"
"replaceable></userinput> can be added. Note that the installer only supports "
"the following terminal types: <literal>linux</literal>, <literal>bterm</"
"literal>, <literal>ansi</literal>, <literal>vt102</literal> and "
"<literal>dumb</literal>. The default for serial console in &d-i; is "
"<userinput>vt102</userinput>. If you are using an IPMI console, or a "
"virtualization tool which does not provide conversion into such terminals "
"types itself, e.g. QEMU/KVM, you can start it inside a <command>screen</"
"command> session. That will indeed perform translation into the "
"<literal>screen</literal> terminal type, which is very close to "
"<literal>vt102</literal>."
msgstr ""
"如果您透過序列控制台開機，一般來說核心將自動檢測 <phrase arch=\"mipsel\"> (盡"
"管不是在一台 DECstations 上面)</phrase>。如果您有一塊顯示卡 (framebuffer) 和"
"一塊鍵盤，透過序列埠附加於想開機的電腦上面，也許需要傳遞 "
"<userinput>console=<replaceable>device</replaceable></userinput> 參數給核"
"心， <replaceable>device</replaceable> 是序列埠設備。通常類似於 "
"<filename>ttyS0</filename>。"

#. Tag: para
#: boot-installer.xml:2472
#, no-c-format
msgid ""
"For &arch-title; the serial devices are <filename>ttya</filename> or "
"<filename>ttyb</filename>. Alternatively, set the <envar>input-device</"
"envar> and <envar>output-device</envar> OpenPROM variables to "
"<filename>ttya</filename>."
msgstr ""
"對於 &arch-title; 序列埠設備名稱是 <filename>ttya</filename> 或 "
"<filename>ttyb</filename> 。或者，透過設置 <envar>input-device</envar> 和 "
"<envar>output-device</envar> OpenPROM 變數至 <filename>ttya</filename>。"

#. Tag: title
#: boot-installer.xml:2484
#, no-c-format
msgid "&debian; Installer Parameters"
msgstr "&debian; 安裝程式的參數"

#. Tag: para
#: boot-installer.xml:2485
#, fuzzy, no-c-format
msgid ""
"The installation system recognizes a few additional boot "
"parameters<footnote> <para> With current kernels (2.6.9 or newer) you can "
"use 32 command line options and 32 environment options. If these numbers are "
"exceeded, the kernel will panic. Also there is a limit of 255 characters for "
"the whole kernel command line, everything above this limit may be silently "
"truncated. </para> </footnote> which may be useful."
msgstr ""
"安裝系統確認一些附加的開機參數 <footnote> <para> 注意，核心最多可以接受 8 個"
"命令列參數和 8 個環境變數選項 (包括安裝程式預設使用的選項)。 如果超出，2.4 內"
"核會忽略過多的選項，2.6 核心則會當機。</para> </footnote>，也許比較有用。"

#. Tag: para
#: boot-installer.xml:2500
#, no-c-format
msgid ""
"A number of parameters have a <quote>short form</quote> that helps avoid the "
"limitations of the kernel command line options and makes entering the "
"parameters easier. If a parameter has a short form, it will be listed in "
"brackets behind the (normal) long form. Examples in this manual will "
"normally use the short form too."
msgstr ""

#. Tag: term
#: boot-installer.xml:2512
#, no-c-format
msgid "debconf/priority (priority)"
msgstr "debconf/priority (priority)"

#. Tag: para
#: boot-installer.xml:2513
#, fuzzy, no-c-format
msgid "This parameter sets the lowest priority of messages to be displayed."
msgstr "這些參數將顯示資訊設定為最低的級別。"

#. Tag: para
#: boot-installer.xml:2517
#, fuzzy, no-c-format
msgid ""
"The default installation uses <userinput>priority=high</userinput>. This "
"means that both high and critical priority messages are shown, but medium "
"and low priority messages are skipped. If problems are encountered, the "
"installer adjusts the priority as needed."
msgstr ""
"預設安裝使用 <userinput>debconf/priority=high</userinput>。這意味著高優先的和"
"至關重要的資訊將被顯示，但是中級和低級資訊將被跳過。如果其間出現了問題，安裝"
"程式將按照要求調整優先級別。"

#. Tag: para
#: boot-installer.xml:2524
#, fuzzy, no-c-format
msgid ""
"If you add <userinput>priority=medium</userinput> as boot parameter, you "
"will be shown the installation menu and gain more control over the "
"installation. When <userinput>priority=low</userinput> is used, all messages "
"are shown (this is equivalent to the <emphasis>expert</emphasis> boot "
"method). With <userinput>priority=critical</userinput>, the installation "
"system will display only critical messages and try to do the right thing "
"without fuss."
msgstr ""
"如果您加入 <userinput>debconf/priority=medium</userinput> 作為開機參數，將看"
"到安裝選單以及安裝過程中更多的控制選項。使用 <userinput>debconf/"
"priority=low</userinput>，將顯示所有的訊息 (這相當於採用 <emphasis>專家級</"
"emphasis> 開機方法)。透過 <userinput>debconf/priority=critical</userinput>，"
"安裝系統只會顯示至關重要的資訊，並且嘗試正確無誤地執行各項事宜。"

#. Tag: term
#: boot-installer.xml:2538
#, no-c-format
msgid "DEBIAN_FRONTEND"
msgstr "DEBIAN_FRONTEND"

#. Tag: para
#: boot-installer.xml:2539
#, fuzzy, no-c-format
msgid ""
"This boot parameter controls the type of user interface used for the "
"installer. The current possible parameter settings are: <itemizedlist> "
"<listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></"
"para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</"
"userinput></para> </listitem><listitem> "
"<para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </"
"listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> "
"</listitem> </itemizedlist> The default frontend is "
"<userinput>DEBIAN_FRONTEND=newt</userinput>. "
"<userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial "
"console installs. Some specialized types of install media may only offer a "
"limited selection of frontends, but the <userinput>newt</userinput> and "
"<userinput>text</userinput> frontends are available on most default install "
"media. On architectures that support it, the graphical installer uses the "
"<userinput>gtk</userinput> frontend."
msgstr ""
"這個開機參數控於安裝程式的使用者界面類型。目前可能參數設置可以是："
"<itemizedlist> <listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</"
"userinput></para> </listitem><listitem> "
"<para><userinput>DEBIAN_FRONTEND=text</userinput></para> </"
"listitem><listitem> <para><userinput>DEBIAN_FRONTEND=newt</userinput></para> "
"</listitem><listitem> <para><userinput>DEBIAN_FRONTEND=slang</userinput></"
"para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=ncurses</"
"userinput></para> </listitem><listitem> "
"<para><userinput>DEBIAN_FRONTEND=bogl</userinput></para> </"
"listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> "
"</listitem><listitem> <para><userinput>DEBIAN_FRONTEND=corba</userinput></"
"para> </listitem> </itemizedlist> 預設的前端是 "
"<userinput>DEBIAN_FRONTEND=newt</userinput>。 "
"<userinput>DEBIAN_FRONTEND=text</userinput> 可以用於序列埠控制台安裝。一般來"
"說在預設安裝媒介上只有 <userinput>newt</userinput> 前端，因此目前這個並非很有"
"用。"

#. Tag: term
#: boot-installer.xml:2570
#, no-c-format
msgid "BOOT_DEBUG"
msgstr "BOOT_DEBUG"

#. Tag: para
#: boot-installer.xml:2571
#, no-c-format
msgid ""
"Setting this boot parameter to 2 will cause the installer's boot process to "
"be verbosely logged. Setting it to 3 makes debug shells available at "
"strategic points in the boot process. (Exit the shells to continue the boot "
"process.)"
msgstr ""
"設定此開機參數為 2 將使得安裝程式的啟動程序寫下所有冗長的紀錄。設定為 3 使得"
"除錯介殼在決定性的時間點上能被使用。 (離開介殼後將繼續安裝程序。)"

#. Tag: userinput
#: boot-installer.xml:2580
#, no-c-format
msgid "BOOT_DEBUG=0"
msgstr "BOOT_DEBUG=0"

#. Tag: para
#: boot-installer.xml:2581
#, no-c-format
msgid "This is the default."
msgstr "此為預設。"

#. Tag: userinput
#: boot-installer.xml:2585
#, no-c-format
msgid "BOOT_DEBUG=1"
msgstr "BOOT_DEBUG=1"

#. Tag: para
#: boot-installer.xml:2586
#, no-c-format
msgid "More verbose than usual."
msgstr "更多的資訊。"

#. Tag: userinput
#: boot-installer.xml:2590
#, no-c-format
msgid "BOOT_DEBUG=2"
msgstr "BOOT_DEBUG=2"

#. Tag: para
#: boot-installer.xml:2591
#, no-c-format
msgid "Lots of debugging information."
msgstr "大量的除錯資訊。"

#. Tag: userinput
#: boot-installer.xml:2595
#, no-c-format
msgid "BOOT_DEBUG=3"
msgstr "BOOT_DEBUG=3"

#. Tag: para
#: boot-installer.xml:2596
#, no-c-format
msgid ""
"Shells are run at various points in the boot process to allow detailed "
"debugging. Exit the shell to continue the boot."
msgstr ""
"介殼腳本將在開機期間執行於不同的地方以允許細節上的調整。退出介殼將繼續開機過"
"程。"

#. Tag: term
#: boot-installer.xml:2610
#, no-c-format
msgid "INSTALL_MEDIA_DEV"
msgstr "INSTALL_MEDIA_DEV"

#. Tag: para
#: boot-installer.xml:2611
#, no-c-format
msgid ""
"The value of the parameter is the path to the device to load the &debian; "
"installer from. For example, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</"
"userinput>"
msgstr ""
"此參數值是載入 &debian; 安裝程式設備的路徑，例如： "
"<userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>"

#. Tag: para
#: boot-installer.xml:2617
#, fuzzy, no-c-format
msgid ""
"The boot floppy, which normally scans all floppies it can to find the root "
"floppy, can be overridden by this parameter to only look at the one device."
msgstr ""
"開機映像通常會掃瞄所有的軟碟和 USB 隨身碟設備來找到根軟碟。它也可以透過此參數"
"只查找一個設備。"

#. Tag: term
#: boot-installer.xml:2628
#, no-c-format
msgid "log_host"
msgstr ""

#. Tag: term
#: boot-installer.xml:2629
#, no-c-format
msgid "log_port"
msgstr ""

#. Tag: para
#: boot-installer.xml:2630
#, no-c-format
msgid ""
"Causes the installer to send log messages to a remote syslog on the "
"specified host and port as well as to a local file. If not specified, the "
"port defaults to the standard syslog port 514."
msgstr ""

#. Tag: term
#: boot-installer.xml:2641
#, no-c-format
msgid "lowmem"
msgstr "lowmem"

#. Tag: para
#: boot-installer.xml:2642
#, no-c-format
msgid ""
"Can be used to force the installer to a lowmem level higher than the one the "
"installer sets by default based on available memory. Possible values are 1 "
"and 2. See also <xref linkend=\"lowmem\"/>."
msgstr ""

#. Tag: term
#: boot-installer.xml:2652
#, no-c-format
msgid "noshell"
msgstr "noshell"

#. Tag: para
#: boot-installer.xml:2653
#, no-c-format
msgid ""
"Prevents the installer from offering interactive shells on tty2 and tty3. "
"Useful for unattended installations where physical security is limited."
msgstr ""

#. Tag: term
#: boot-installer.xml:2662
#, no-c-format
msgid "debian-installer/framebuffer (fb)"
msgstr "debian-installer/framebuffer (fb)"

#. Tag: para
#: boot-installer.xml:2663
#, fuzzy, no-c-format
msgid ""
"Some architectures use the kernel framebuffer to offer installation in a "
"number of languages. If framebuffer causes a problem on your system you can "
"disable the feature using the parameter <userinput arch=\"x86\">vga=normal</"
"userinput> <userinput>fb=false</userinput>. Problem symptoms are error "
"messages about bterm or bogl, a blank screen, or a freeze within a few "
"minutes after starting the install."
msgstr ""
"一些架構使用核心 framebuffer 以提供不同的語言安裝。如果 framebuffer 在您的系"
"統發生問題，您可以透過參數 <userinput>debian-installer/framebuffer=false</"
"userinput> 關閉這個功能。這方面問題的徵兆是 bterm 或者 bogl 的錯誤資訊、一個"
"空白的螢幕，或者在開始安裝的時候停止幾分鐘。"

#. Tag: para
#: boot-installer.xml:2672
#, no-c-format
msgid "Such problems have been reported on hppa."
msgstr "在 hppa 上面報告過存在這些問題。"

#. Tag: para
#: boot-installer.xml:2676
#, fuzzy, no-c-format
msgid ""
"Because of display problems on some systems, framebuffer support is "
"<emphasis>disabled by default</emphasis> for &arch-title;. This can result "
"in ugly display on systems that do properly support the framebuffer, like "
"those with ATI graphical cards. If you see display problems in the "
"installer, you can try booting with parameter <userinput>debian-installer/"
"framebuffer=true</userinput> or <userinput>fb=true</userinput> for short."
msgstr ""
"由於某些系統上顯示有問題，framebuffer 在 &arch-title; 上<emphasis>預設禁止使"
"用</emphasis>。\n"
"這將會使支援 framebuffer 良好的系統顯示很醜陋，例如採用 ATI 圖形卡的系統。\n"
"如果您在安裝程式中遇到顯示問題，可以試著採用開機參數 <userinput>debian-"
"installer/framebuffer=true</userinput>。"

#. Tag: term
#: boot-installer.xml:2690
#, no-c-format
msgid "debian-installer/theme (theme)"
msgstr "debian-installer/theme (theme)"

#. Tag: para
#: boot-installer.xml:2691
#, no-c-format
msgid ""
"A theme determines how the user interface of the installer looks (colors, "
"icons, etc.). What themes are available differs per frontend. Currently both "
"the newt and gtk frontends only have a <quote>dark</quote> theme that was "
"designed for visually impaired users. Set the theme by booting with "
"<userinput>theme=<replaceable>dark</replaceable></userinput>."
msgstr ""

#. Tag: term
#: boot-installer.xml:2703 boot-installer.xml:2936
#, no-c-format
msgid "netcfg/disable_autoconfig"
msgstr "netcfg/disable_autoconfig"

#. Tag: para
#: boot-installer.xml:2704
#, fuzzy, no-c-format
#| msgid ""
#| "By default, the &d-i; automatically probes for network configuration via "
#| "DHCP. If the probe succeeds, you won't have a chance to review and change "
#| "the obtained settings. You can get to the manual network setup only in "
#| "case the DHCP probe fails."
msgid ""
"By default, the &d-i; automatically probes for network configuration via "
"IPv6 autoconfiguration and DHCP. If the probe succeeds, you won't have a "
"chance to review and change the obtained settings. You can get to the manual "
"network setup only in case the automatic configuration fails."
msgstr ""
"預設情況下，&d-i; 會透過 DHCP 來自動偵測網路。如果檢測成功，您將不需要審視並"
"且改變其取得的設定。您可以在 DHCP 檢測失敗的情況下手動配置網路。"

#. Tag: para
#: boot-installer.xml:2711
#, fuzzy, no-c-format
#| msgid ""
#| "If you have a DHCP server on your local network, but want to avoid it "
#| "because e.g. it gives wrong answers, you can use the parameter "
#| "<userinput>netcfg/disable_autoconfig=true</userinput> to prevent "
#| "configuring the network with DHCP and to enter the information manually."
msgid ""
"If you have an IPv6 router or a DHCP server on your local network, but want "
"to avoid them because e.g. they give wrong answers, you can use the "
"parameter <userinput>netcfg/disable_autoconfig=true</userinput> to prevent "
"any automatic configuration of the network (neither v4 nor v6) and to enter "
"the information manually."
msgstr ""
"如果您的網路上面具備一台 DHCP 伺服器，但是不想使用它，例如，因為它給出錯誤的"
"答案。您可以使用參數 <userinput>netcfg/disable_autoconfig=true</userinput> 來"
"透過 DHCP 來設定網路並且手動輸入參數。"

#. Tag: term
#: boot-installer.xml:2722
#, no-c-format
msgid "hw-detect/start_pcmcia"
msgstr "hw-detect/start_pcmcia"

#. Tag: para
#: boot-installer.xml:2723
#, no-c-format
msgid ""
"Set to <userinput>false</userinput> to prevent starting PCMCIA services, if "
"that causes problems. Some laptops are well known for this misbehavior."
msgstr ""
"設定成 <userinput>false</userinput> 來阻止啟動 PCMCIA 服務，如果其引起各種問"
"題。有些筆記型電腦對此會有錯誤的行為。"

#. Tag: term
#: boot-installer.xml:2733
#, no-c-format
msgid "disk-detect/dmraid/enable (dmraid)"
msgstr "disk-detect/dmraid/enable (dmraid)"

#. Tag: para
#: boot-installer.xml:2734
#, no-c-format
msgid ""
"Set to <userinput>true</userinput> to enable support for Serial ATA RAID "
"(also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. Note "
"that this support is currently experimental. Additional information can be "
"found on the <ulink url=\"&url-d-i-wiki;\">&debian; Installer Wiki</ulink>."
msgstr ""

#. Tag: term
#: boot-installer.xml:2745
#, no-c-format
msgid "preseed/url (url)"
msgstr "preseed/url (url)"

#. Tag: para
#: boot-installer.xml:2746
#, fuzzy, no-c-format
msgid ""
"Specify the url to a preconfiguration file to download and use for "
"automating the install. See <xref linkend=\"automatic-install\"/>."
msgstr ""
"指定預設參數檔案的 URL，此檔案將在安裝中自動下載、掛載和使用。請參閱 <xref "
"linkend=\"automatic-install\"/>。"

#. Tag: term
#: boot-installer.xml:2755
#, no-c-format
msgid "preseed/file (file)"
msgstr "preseed/file (file)"

#. Tag: para
#: boot-installer.xml:2756
#, fuzzy, no-c-format
msgid ""
"Specify the path to a preconfiguration file to load for automating the "
"install. See <xref linkend=\"automatic-install\"/>."
msgstr ""
"指定預設參數檔案的路徑，在安裝中自動掛載和使用。請參閱 <xref linkend="
"\"automatic-install\"/>。"

#. Tag: term
#: boot-installer.xml:2765
#, no-c-format
msgid "preseed/interactive"
msgstr "preseed/interactive"

#. Tag: para
#: boot-installer.xml:2766
#, no-c-format
msgid ""
"Set to <userinput>true</userinput> to display questions even if they have "
"been preseeded. Can be useful for testing or debugging a preconfiguration "
"file. Note that this will have no effect on parameters that are passed as "
"boot parameters, but for those a special syntax can be used. See <xref "
"linkend=\"preseed-seenflag\"/> for details."
msgstr ""

#. Tag: term
#: boot-installer.xml:2778
#, no-c-format
msgid "auto-install/enable (auto)"
msgstr "auto-install/enable (auto)"

#. Tag: para
#: boot-installer.xml:2779
#, no-c-format
msgid ""
"Delay questions that are normally asked before preseeding is possible until "
"after the network is configured. See <xref linkend=\"preseed-auto\"/> for "
"details about using this to automate installs."
msgstr ""

#. Tag: term
#: boot-installer.xml:2790
#, no-c-format
msgid "finish-install/keep-consoles"
msgstr "finish-install/keep-consoles"

#. Tag: para
#: boot-installer.xml:2791
#, no-c-format
msgid ""
"During installations from serial or management console, the regular virtual "
"consoles (VT1 to VT6) are normally disabled in <filename>/etc/inittab</"
"filename>. Set to <userinput>true</userinput> to prevent this."
msgstr ""

#. Tag: term
#: boot-installer.xml:2802
#, no-c-format
msgid "cdrom-detect/eject"
msgstr "cdrom-detect/eject"

#. Tag: para
#: boot-installer.xml:2803
#, no-c-format
msgid ""
"By default, before rebooting, &d-i; automatically ejects the optical media "
"used during the installation. This can be unnecessary if the system does not "
"automatically boot off the CD. In some cases it may even be undesirable, for "
"example if the optical drive cannot reinsert the media itself and the user "
"is not there to do it manually. Many slot loading, slim-line, and caddy "
"style drives cannot reload media automatically."
msgstr ""
"在重開機前，&d-i; 預設會自動退出安裝時的光學媒介。如果系統不是自動從光碟開"
"機，這不是必要的動作。在某些情況下，這反而不便，例如，如果光碟機不能自動插入"
"光碟片，使用者又不在旁邊操作。許多 slot loading, slim-line 和 caddy 類型的光"
"碟機不能自動重新掛載媒介。"

#. Tag: para
#: boot-installer.xml:2812
#, no-c-format
msgid ""
"Set to <userinput>false</userinput> to disable automatic ejection, and be "
"aware that you may need to ensure that the system does not automatically "
"boot from the optical drive after the initial installation."
msgstr ""
"設為 <userinput>false</userinput> 可以禁止自動退出，但要小心確保系統在安裝完"
"後，不會自動從光碟開機。"

#. Tag: term
#: boot-installer.xml:2823
#, no-c-format
msgid "base-installer/install-recommends (recommends)"
msgstr "base-installer/install-recommends (recommends)"

#. Tag: para
#: boot-installer.xml:2824
#, no-c-format
msgid ""
"By setting this option to <userinput>false</userinput>, the package "
"management system will be configured to not automatically install "
"<quote>Recommends</quote>, both during the installation and for the "
"installed system. See also <xref linkend=\"di-install-base\"/>."
msgstr ""

#. Tag: para
#: boot-installer.xml:2831
#, no-c-format
msgid ""
"Note that this option allows to have a leaner system, but can also result in "
"features being missing that you might normally expect to be available. You "
"may have to manually install some of the recommended packages to obtain the "
"full functionality you want. This option should therefore only be used by "
"very experienced users."
msgstr ""

#. Tag: term
#: boot-installer.xml:2843
#, no-c-format
msgid "debian-installer/allow_unauthenticated"
msgstr "debian-installer/allow_unauthenticated"

#. Tag: para
#: boot-installer.xml:2844
#, no-c-format
msgid ""
"By default the installer requires that repositories be authenticated using a "
"known gpg key. Set to <userinput>true</userinput> to disable that "
"authentication. <emphasis role=\"bold\">Warning: insecure, not recommended.</"
"emphasis>"
msgstr ""

#. Tag: term
#: boot-installer.xml:2855
#, no-c-format
msgid "ramdisk_size"
msgstr "ramdisk_size"

#. Tag: para
#: boot-installer.xml:2856
#, no-c-format
msgid ""
"This parameter should already be set to a correct value where needed; set it "
"only it you see errors during the boot that indicate the ramdisk could not "
"be loaded completely. The value is in kB."
msgstr ""

#. Tag: term
#: boot-installer.xml:2866
#, no-c-format
msgid "rescue/enable"
msgstr "rescue/enable"

#. Tag: para
#: boot-installer.xml:2867
#, no-c-format
msgid ""
"Set to <userinput>true</userinput> to enter rescue mode rather than "
"performing a normal installation. See <xref linkend=\"rescue\"/>."
msgstr ""

#. Tag: title
#: boot-installer.xml:2880
#, no-c-format
msgid "Using boot parameters to answer questions"
msgstr ""

#. Tag: para
#: boot-installer.xml:2881
#, no-c-format
msgid ""
"With some exceptions, a value can be set at the boot prompt for any question "
"asked during the installation, though this is only really useful in specific "
"cases. General instructions how to do this can be found in <xref linkend="
"\"preseed-bootparms\"/>. Some specific examples are listed below."
msgstr ""

#. Tag: term
#: boot-installer.xml:2893
#, no-c-format
msgid "debian-installer/language (language)"
msgstr "debian-installer/language (language)"

#. Tag: term
#: boot-installer.xml:2894
#, no-c-format
msgid "debian-installer/country (country)"
msgstr "debian-installer/country (country)"

#. Tag: term
#: boot-installer.xml:2895
#, no-c-format
msgid "debian-installer/locale (locale)"
msgstr "debian-installer/locale (locale)"

#. Tag: para
#: boot-installer.xml:2896
#, no-c-format
msgid ""
"There are two ways to specify the language, country and locale to use for "
"the installation and the installed system."
msgstr ""

#. Tag: para
#: boot-installer.xml:2901
#, no-c-format
msgid ""
"The first and easiest is to pass only the parameter <literal>locale</"
"literal>. Language and country will then be derived from its value. You can "
"for example use <userinput>locale=de_CH</userinput> to select German as "
"language and Switzerland as country (<literal>de_CH.UTF-8</literal> will be "
"set as default locale for the installed system). Limitation is that not all "
"possible combinations of language, country and locale can be achieved this "
"way."
msgstr ""

#. Tag: para
#: boot-installer.xml:2910
#, no-c-format
msgid ""
"The second, more flexible option is to specify <literal>language</literal> "
"and <literal>country</literal> separately. In this case <literal>locale</"
"literal> can optionally be added to specify a specific default locale for "
"the installed system. Example: <userinput>language=en country=DE "
"locale=en_GB.UTF-8</userinput>."
msgstr ""

#. Tag: term
#: boot-installer.xml:2922
#, no-c-format
msgid "anna/choose_modules (modules)"
msgstr ""

#. Tag: para
#: boot-installer.xml:2923
#, no-c-format
msgid ""
"Can be used to automatically load installer components that are not loaded "
"by default. Examples of optional components that may be useful are "
"<classname>openssh-client-udeb</classname> (so you can use <command>scp</"
"command> during the installation)<phrase arch=\"not-s390\"> and "
"<classname>ppp-udeb</classname> (see <xref linkend=\"pppoe\"/>)</phrase>."
msgstr ""

#. Tag: para
#: boot-installer.xml:2937
#, no-c-format
msgid ""
"Set to <userinput>true</userinput> if you want to disable IPv6 "
"autoconfiguration and DHCP and instead force static network configuration."
msgstr ""

#. Tag: term
#: boot-installer.xml:2946
#, no-c-format
msgid "mirror/protocol (protocol)"
msgstr ""

#. Tag: para
#: boot-installer.xml:2947
#, no-c-format
msgid ""
"By default the installer will use the http protocol to download files from "
"&debian; mirrors and changing that to ftp is not possible during "
"installations at normal priority. By setting this parameter to "
"<userinput>ftp</userinput>, you can force the installer to use that protocol "
"instead. Note that you cannot select an ftp mirror from a list, you have to "
"enter the hostname manually."
msgstr ""

#. Tag: term
#: boot-installer.xml:2960
#, no-c-format
msgid "tasksel:tasksel/first (tasks)"
msgstr ""

#. Tag: para
#: boot-installer.xml:2961
#, no-c-format
msgid ""
"Can be used to select tasks that are not available from the interactive task "
"list, such as the <literal>kde-desktop</literal> task. See <xref linkend="
"\"pkgsel\"/> for additional information."
msgstr ""

#. Tag: title
#: boot-installer.xml:2975
#, no-c-format
msgid "Passing parameters to kernel modules"
msgstr ""

#. Tag: para
#: boot-installer.xml:2976
#, no-c-format
msgid ""
"If drivers are compiled into the kernel, you can pass parameters to them as "
"described in the kernel documentation. However, if drivers are compiled as "
"modules and because kernel modules are loaded a bit differently during an "
"installation than when booting an installed system, it is not possible to "
"pass parameters to modules as you would normally do. Instead, you need to "
"use a special syntax recognized by the installer which will then make sure "
"that the parameters are saved in the proper configuration files and will "
"thus be used when the modules are actually loaded. The parameters will also "
"be propagated automatically to the configuration for the installed system."
msgstr ""

#. Tag: para
#: boot-installer.xml:2989
#, no-c-format
msgid ""
"Note that it is now quite rare that parameters need to be passed to modules. "
"In most cases the kernel will be able to probe the hardware present in a "
"system and set good defaults that way. However, in some situations it may "
"still be needed to set parameters manually."
msgstr ""

#. Tag: para
#: boot-installer.xml:2996
#, no-c-format
msgid ""
"The syntax to use to set parameters for modules is: "
"<informalexample><screen>\n"
"<replaceable>module_name</replaceable>.<replaceable>parameter_name</"
"replaceable>=<replaceable>value</replaceable>\n"
"</screen></informalexample> If you need to pass multiple parameters to the "
"same or different modules, just repeat this. For example, to set an old 3Com "
"network interface card to use the BNC (coax) connector and IRQ 10, you would "
"pass:"
msgstr ""

#. Tag: screen
#: boot-installer.xml:3006
#, no-c-format
msgid "3c509.xcvr=3 3c509.irq=10"
msgstr "3c509.xcvr=3 3c509.irq=10"

#. Tag: title
#: boot-installer.xml:3012
#, no-c-format
msgid "Blacklisting kernel modules"
msgstr ""

#. Tag: para
#: boot-installer.xml:3013
#, no-c-format
msgid ""
"Sometimes it may be necessary to blacklist a module to prevent it from being "
"loaded automatically by the kernel and udev. One reason could be that a "
"particular module causes problems with your hardware. The kernel also "
"sometimes lists two different drivers for the same device. This can cause "
"the device to not work correctly if the drivers conflict or if the wrong "
"driver is loaded first."
msgstr ""

#. Tag: para
#: boot-installer.xml:3022
#, no-c-format
msgid ""
"You can blacklist a module using the following syntax: "
"<userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>. "
"This will cause the module to be blacklisted in <filename>/etc/modprobe.d/"
"blacklist.local</filename> both during the installation and for the "
"installed system."
msgstr ""

#. Tag: para
#: boot-installer.xml:3030
#, no-c-format
msgid ""
"Note that a module may still be loaded by the installation system itself. "
"You can prevent that from happening by running the installation in expert "
"mode and unselecting the module from the list of modules displayed during "
"the hardware detection phases."
msgstr ""

#. Tag: title
#: boot-installer.xml:3046
#, no-c-format
msgid "Troubleshooting the Installation Process"
msgstr "安裝過程中的障礙排除"

#. Tag: title
#: boot-installer.xml:3051
#, fuzzy, no-c-format
msgid "CD-ROM Reliability"
msgstr "軟碟的可靠性"

#. Tag: para
#: boot-installer.xml:3052
#, no-c-format
msgid ""
"Sometimes, especially with older CD-ROM drives, the installer may fail to "
"boot from a CD-ROM. The installer may also &mdash; even after booting "
"successfully from CD-ROM &mdash; fail to recognize the CD-ROM or return "
"errors while reading from it during the installation."
msgstr ""

#. Tag: para
#: boot-installer.xml:3059
#, no-c-format
msgid ""
"There are many different possible causes for these problems. We can only "
"list some common issues and provide general suggestions on how to deal with "
"them. The rest is up to you."
msgstr ""

#. Tag: para
#: boot-installer.xml:3065
#, no-c-format
msgid "There are two very simple things that you should try first."
msgstr ""

#. Tag: para
#: boot-installer.xml:3070
#, no-c-format
msgid ""
"If the CD-ROM does not boot, check that it was inserted correctly and that "
"it is not dirty."
msgstr ""

#. Tag: para
#: boot-installer.xml:3076
#, no-c-format
msgid ""
"If the installer fails to recognize a CD-ROM, try just running the option "
"<menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </"
"menuchoice> a second time. Some DMA related issues with very old CD-ROM "
"drives are known to be resolved in this way."
msgstr ""

#. Tag: para
#: boot-installer.xml:3086
#, no-c-format
msgid ""
"If this does not work, then try the suggestions in the subsections below. "
"Most, but not all, suggestions discussed there are valid for both CD-ROM and "
"DVD, but we'll use the term CD-ROM for simplicity."
msgstr ""

#. Tag: para
#: boot-installer.xml:3092
#, no-c-format
msgid ""
"If you cannot get the installation working from CD-ROM, try one of the other "
"installation methods that are available."
msgstr ""

#. Tag: title
#: boot-installer.xml:3100
#, no-c-format
msgid "Common issues"
msgstr ""

#. Tag: para
#: boot-installer.xml:3103
#, no-c-format
msgid ""
"Some older CD-ROM drives do not support reading from discs that were burned "
"at high speeds using a modern CD writer."
msgstr ""

#. Tag: para
#: boot-installer.xml:3120
#, no-c-format
msgid ""
"Some very old CD-ROM drives do not work correctly if <quote>direct memory "
"access</quote> (DMA) is enabled for them."
msgstr ""

#. Tag: title
#: boot-installer.xml:3131
#, no-c-format
msgid "How to investigate and maybe solve issues"
msgstr ""

#. Tag: para
#: boot-installer.xml:3132
#, no-c-format
msgid "If the CD-ROM fails to boot, try the suggestions listed below."
msgstr ""

#. Tag: para
#: boot-installer.xml:3137
#, no-c-format
msgid ""
"Check that your BIOS actually supports booting from CD-ROM (only an issue "
"for very old systems) and that CD booting is enabled in the BIOS."
msgstr ""

#. Tag: para
#: boot-installer.xml:3144
#, no-c-format
msgid ""
"If you downloaded an iso image, check that the md5sum of that image matches "
"the one listed for the image in the <filename>MD5SUMS</filename> file that "
"should be present in the same location as where you downloaded the image "
"from. <informalexample><screen>\n"
"$ md5sum <replaceable>debian-testing-i386-netinst.iso</replaceable>\n"
"a20391b12f7ff22ef705cee4059c6b92  <replaceable>debian-testing-i386-netinst."
"iso</replaceable>\n"
"</screen></informalexample> Next, check that the md5sum of the burned CD-ROM "
"matches as well. The following command should work. It uses the size of the "
"image to read the correct number of bytes from the CD-ROM."
msgstr ""

#. Tag: screen
#: boot-installer.xml:3157
#, no-c-format
msgid ""
"$ dd if=/dev/cdrom | \\\n"
"&gt; head -c `stat --format=%s <replaceable>debian-testing-i386-netinst.iso</"
"replaceable>` | \\\n"
"&gt; md5sum\n"
"a20391b12f7ff22ef705cee4059c6b92  -\n"
"262668+0 records in\n"
"262668+0 records out\n"
"134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s"
msgstr ""
"$ dd if=/dev/cdrom | \\\n"
"&gt; head -c `stat --format=%s <replaceable>debian-testing-i386-netinst.iso</"
"replaceable>` | \\\n"
"&gt; md5sum\n"
"a20391b12f7ff22ef705cee4059c6b92  -\n"
"262668+0 records in\n"
"262668+0 records out\n"
"134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s"

#. Tag: para
#: boot-installer.xml:3162
#, no-c-format
msgid ""
"If, after the installer has been booted successfully, the CD-ROM is not "
"detected, sometimes simply trying again may solve the problem. If you have "
"more than one CD-ROM drive, try changing the CD-ROM to the other drive. If "
"that does not work or if the CD-ROM is recognized but there are errors when "
"reading from it, try the suggestions listed below. Some basic knowledge of "
"&arch-kernel; is required for this. To execute any of the commands, you "
"should first switch to the second virtual console (VT2) and activate the "
"shell there."
msgstr ""

#. Tag: para
#: boot-installer.xml:3174
#, no-c-format
msgid ""
"Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> "
"(use <command>nano</command> as editor) to check for any specific error "
"messages. After that, also check the output of <command>dmesg</command>."
msgstr ""

#. Tag: para
#: boot-installer.xml:3181
#, no-c-format
msgid ""
"Check in the output of <command>dmesg</command> if your CD-ROM drive was "
"recognized. You should see something like (the lines do not necessarily have "
"to be consecutive): <informalexample><screen>\n"
"ata1.00: ATAPI: MATSHITADVD-RAM UJ-822S, 1.61, max UDMA/33\n"
"ata1.00: configured for UDMA/33\n"
"scsi 0:0:0:0: CD-ROM            MATSHITA DVD-RAM UJ-822S  1.61 PQ: 0 ANSI: "
"5\n"
"sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray\n"
"cdrom: Uniform CD-ROM driver Revision: 3.20\n"
"</screen></informalexample> If you don't see something like that, chances "
"are the controller your CD-ROM is connected to was not recognized or may be "
"not supported at all. If you know what driver is needed for the controller, "
"you can try loading it manually using <command>modprobe</command>."
msgstr ""

#. Tag: para
#: boot-installer.xml:3195
#, no-c-format
msgid ""
"Check that there is a device node for your CD-ROM drive under <filename>/dev/"
"</filename>. In the example above, this would be <filename>/dev/sr0</"
"filename>. There should also be a <filename>/dev/cdrom</filename>."
msgstr ""

#. Tag: para
#: boot-installer.xml:3203
#, no-c-format
msgid ""
"Use the <command>mount</command> command to check if the CD-ROM is already "
"mounted; if not, try mounting it manually: <informalexample><screen>\n"
"$ mount /dev/<replaceable>hdc</replaceable> /cdrom\n"
"</screen></informalexample> Check if there are any error messages after that "
"command."
msgstr ""

#. Tag: para
#: boot-installer.xml:3213
#, no-c-format
msgid ""
"Check if DMA is currently enabled: <informalexample><screen>\n"
"$ cd /proc/<replaceable>ide</replaceable>/<replaceable>hdc</replaceable>\n"
"$ grep using_dma settings\n"
"using_dma      1       0       1       rw\n"
"</screen></informalexample> A <quote>1</quote> in the first column after "
"<literal>using_dma</literal> means it is enabled. If it is, try disabling "
"it: <informalexample><screen>\n"
"$ echo -n \"using_dma:0\" &gt;settings\n"
"</screen></informalexample> Make sure that you are in the directory for the "
"device that corresponds to your CD-ROM drive."
msgstr ""

#. Tag: para
#: boot-installer.xml:3228
#, no-c-format
msgid ""
"If there are any problems during the installation, try checking the "
"integrity of the CD-ROM using the option near the bottom of the installer's "
"main menu. This option can also be used as a general test if the CD-ROM can "
"be read reliably."
msgstr ""

#. Tag: title
#: boot-installer.xml:3243
#, no-c-format
msgid "Floppy Disk Reliability"
msgstr "軟碟的可靠性"

#. Tag: para
#: boot-installer.xml:3245
#, no-c-format
msgid ""
"The biggest problem for people using floppy disks to install &debian; seems "
"to be floppy disk reliability."
msgstr ""
"對於第一次安裝 &debian; 的人來說，他們遇到的最大的問題很可能是軟碟的可靠性。"

#. Tag: para
#: boot-installer.xml:3250
#, fuzzy, no-c-format
msgid ""
"The boot floppy is the floppy with the worst problems, because it is read by "
"the hardware directly, before Linux boots. Often, the hardware doesn't read "
"as reliably as the Linux floppy disk driver, and may just stop without "
"printing an error message if it reads incorrect data. There can also be "
"failures in the driver floppies, most of which indicate themselves with a "
"flood of messages about disk I/O errors."
msgstr ""
"問題出現最嚴重的是糟糕的開機軟碟，因為他們由硬體直接讀出，然後才進入 Linux 開"
"機程序。很多情況下，硬體的讀取並不能像 Linux 軟碟驅動讀取那樣可靠，並且對於錯"
"誤的資料，它們只是停止執行而且沒有錯誤訊息。軟碟機也可能發生錯誤並且印出很多"
"有關的 I/O 錯誤。"

#. Tag: para
#: boot-installer.xml:3259
#, fuzzy, no-c-format
msgid ""
"If you are having the installation stall at a particular floppy, the first "
"thing you should do is write the image to a <emphasis>different</emphasis> "
"floppy and see if that solves the problem. Simply reformatting the old "
"floppy may not be sufficient, even if it appears that the floppy was "
"reformatted and written with no errors. It is sometimes useful to try "
"writing the floppy on a different system."
msgstr ""
"如果您在特定的軟碟上遇到麻煩，第一件要做的事情，是重新下載磁碟映像並且把它寫"
"到<emphasis>另外</emphasis>一張軟碟上。僅僅只是格式化老的軟碟是不夠的，有可能"
"的話甚至要在別的統上重寫這些軟碟。"

#. Tag: para
#: boot-installer.xml:3268
#, no-c-format
msgid ""
"One user reports he had to write the images to floppy <emphasis>three</"
"emphasis> times before one worked, and then everything was fine with the "
"third floppy."
msgstr ""
"一個使用者曾報告他不得不把映像往軟碟寫了<emphasis>三</emphasis>次，直到第四次"
"軟碟才算工作良好。"

#. Tag: para
#: boot-installer.xml:3274
#, no-c-format
msgid ""
"Normally you should not have to download a floppy image again, but if you "
"are experiencing problems it is always useful to verify that the images were "
"downloaded correctly by verifying their md5sums."
msgstr ""

#. Tag: para
#: boot-installer.xml:3280
#, no-c-format
msgid ""
"Other users have reported that simply rebooting a few times with the same "
"floppy in the floppy drive can lead to a successful boot. This is all due to "
"buggy hardware or firmware floppy drivers."
msgstr ""
"其他一些使用者報告過用同樣的軟碟重新啟動若干次才能有一次成功的開機。這都是因"
"為 硬體或者有缺陷的韌體軟碟驅動程式造成的。"

#. Tag: title
#: boot-installer.xml:3289
#, no-c-format
msgid "Boot Configuration"
msgstr "開機設定"

#. Tag: para
#: boot-installer.xml:3291
#, no-c-format
msgid ""
"If you have problems and the kernel hangs during the boot process, doesn't "
"recognize peripherals you actually have, or drives are not recognized "
"properly, the first thing to check is the boot parameters, as discussed in "
"<xref linkend=\"boot-parms\"/>."
msgstr ""
"如果在開機過程中您遇到了問題或者核心當掉、無法辨識存在的周邊設備或者辨識錯"
"誤，首先要做的事情是檢查開機參數，如同 <xref linkend=\"boot-parms\"/> 之中的"
"內容。"

#. Tag: para
#: boot-installer.xml:3300
#, no-c-format
msgid ""
"In some cases, malfunctions can be caused by missing device firmware (see "
"<xref linkend=\"hardware-firmware\"/> and <xref linkend=\"loading-firmware\"/"
">)."
msgstr ""

#. Tag: para
#: boot-installer.xml:3311
#, no-c-format
msgid ""
"If software speech synthesis does not work, there is most probably an issue "
"with your sound board, usually because either the driver for it is not "
"included in the installer, or because it has unusual mixer level names which "
"are set to muted by default. You should thus submit a bug report which "
"includes the output of the following commands, run on the same machine from "
"a Linux system which is known to have sound working (e.g., a live CD)."
msgstr ""

#. Tag: userinput
#: boot-installer.xml:3322
#, no-c-format
msgid "dmesg"
msgstr "dmesg"

#. Tag: userinput
#: boot-installer.xml:3324
#, no-c-format
msgid "lspci"
msgstr "lspci"

#. Tag: userinput
#: boot-installer.xml:3326
#, no-c-format
msgid "lsmod"
msgstr "lsmod"

#. Tag: userinput
#: boot-installer.xml:3328
#, no-c-format
msgid "amixer"
msgstr "amixer"

#. Tag: title
#: boot-installer.xml:3336 boot-installer.xml:3447
#, no-c-format
msgid "Common &arch-title; Installation Problems"
msgstr "常見的 &arch-title; 安裝問題"

#. Tag: para
#: boot-installer.xml:3337
#, no-c-format
msgid ""
"There are some common installation problems that can be solved or avoided by "
"passing certain boot parameters to the installer."
msgstr "傳入某些啟動參數可以解決或避免一些常見的安裝問題。"

#. Tag: para
#: boot-installer.xml:3388
#, fuzzy, no-c-format
msgid ""
"If your screen begins to show a weird picture while the kernel boots, eg. "
"pure white, pure black or colored pixel garbage, your system may contain a "
"problematic video card which does not switch to the framebuffer mode "
"properly. Then you can use the boot parameter <userinput>fb=false</"
"userinput> to disable the framebuffer console. Only a reduced set of "
"languages will be available during the installation due to limited console "
"features. See <xref linkend=\"boot-parms\"/> for details."
msgstr ""
"如果您的螢幕在核心開機的時候顯示一個奇怪的圖片 (例如，純白，純黑或者彩色的像"
"素塊)，則顯示卡可能有問題。它不能切換至 framebuffer 模式。您可以使用開機參數 "
"<userinput>debian-installer/framebuffer=false</userinput> 或 "
"<userinput>video=vga16:off</userinput> 來取消 framebuffer 控制台。在這種情況"
"下，由於控制台的限制，在安裝過程中只能用英語，請參閱 <xref linkend=\"boot-"
"parms\"/> 來取得細節資訊。"

#. Tag: title
#: boot-installer.xml:3402
#, no-c-format
msgid "System Freeze During the PCMCIA Configuration Phase"
msgstr "在 PCMCIA 段系統當機"

#. Tag: para
#: boot-installer.xml:3403
#, fuzzy, no-c-format
#| msgid ""
#| "Some laptop models produced by Dell are known to crash when PCMCIA device "
#| "detection tries to access some hardware addresses. Other laptops may "
#| "display similar problems. If you experience such a problem and you don't "
#| "need PCMCIA support during the installation, you can disable PCMCIA using "
#| "the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. "
#| "You can then configure PCMCIA after the installation is completed and "
#| "exclude the resource range causing the problems."
msgid ""
"Some very old laptop models produced by Dell are known to crash when PCMCIA "
"device detection tries to access some hardware addresses. Other laptops may "
"display similar problems. If you experience such a problem and you don't "
"need PCMCIA support during the installation, you can disable PCMCIA using "
"the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You "
"can then configure PCMCIA after the installation is completed and exclude "
"the resource range causing the problems."
msgstr ""
"某些型號的 Dell 筆記型電腦會在 PCMCIA 設備檢測程式嘗試存取一些硬體位址的時候"
"當機。其他筆記型電腦可能顯示類似的問題。如果您遇到那樣的問題，並且在安裝的時"
"候不需要 PCMCIA 的支援，可以用 <userinput>hw-detect/start_pcmcia=false</"
"userinput> 啟動參數來取消 PCMCIA 功能。您可以在安裝後，配定 PCMCIA 並且避開可"
"能引起問題的資源範圍。"

#. Tag: para
#: boot-installer.xml:3413
#, no-c-format
msgid ""
"Alternatively, you can boot the installer in expert mode. You will then be "
"asked to enter the resource range options your hardware needs. For example, "
"if you have one of the Dell laptops mentioned above, you should enter "
"<userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list "
"of some common resource range options in the <ulink url=\"http://pcmcia-cs."
"sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource "
"settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the "
"commas, if any, when you enter this value in the installer."
msgstr ""
"或者，您可以在啟動安裝程式時進入專家模式。您需要按照要求輸入硬體資源範圍選"
"項。例如，您如果有如上所說的 Dell 筆記型電腦問題，應該在這裡輸入 "
"<userinput>exclude port 0x800-0x8ff</userinput>。在 <ulink url=\"http://"
"pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System "
"resource settings section of the PCMCIA HOWTO</ulink> 處有一個列表，整理出一"
"些有問題的資源範圍選項。注意在安裝程式中，輸入這些值的時候必須忽略逗號。"

#. Tag: para
#: boot-installer.xml:3448
#, fuzzy, no-c-format
msgid "There are some common installation problems that are worth mentioning."
msgstr "傳入某些啟動參數可以解決或避免一些常見的安裝問題。"

#. Tag: title
#: boot-installer.xml:3454
#, no-c-format
msgid "Misdirected video output"
msgstr ""

#. Tag: para
#: boot-installer.xml:3455
#, no-c-format
msgid ""
"It is fairly common for &arch-title; to have two video cards in one machine, "
"for example an ATI card and a Sun Creator 3D. In some cases, this may result "
"in the video output getting misdirected soon after the system boots. In "
"typical cases, the display will only show: <informalexample><screen>\n"
"Remapping the kernel... done\n"
"Booting Linux...\n"
"</screen></informalexample> To work around this, you can either pull out one "
"of the video cards, or disable the one not used during the OpenProm boot "
"phase using a kernel parameter. For example, to disable an ATI card, you "
"should boot the installer with <userinput>video=atyfb:off</userinput>."
msgstr ""

#. Tag: para
#: boot-installer.xml:3469
#, no-c-format
msgid ""
"Note that you may also have to manually add this parameter to the silo "
"configuration (edit <filename>/target/etc/silo.conf</filename> before "
"rebooting) and, if you installed X11, modify the video driver in <filename>/"
"etc/X11/xorg.conf</filename>."
msgstr ""

#. Tag: title
#: boot-installer.xml:3480
#, fuzzy, no-c-format
msgid "Failure to Boot or Install from CD-ROM"
msgstr "從光碟開機"

#. Tag: para
#: boot-installer.xml:3481
#, no-c-format
msgid ""
"Some Sparc systems are notoriously difficult to boot from CD-ROM and even if "
"they do boot, there may be inexplicable failures during the installation. "
"Most problems have been reported with SunBlade systems."
msgstr ""

#. Tag: para
#: boot-installer.xml:3487
#, no-c-format
msgid "We recommend to install such systems by netbooting the installer."
msgstr ""

#. Tag: title
#: boot-installer.xml:3496
#, no-c-format
msgid "Interpreting the Kernel Startup Messages"
msgstr "解讀核心起始資訊"

#. Tag: para
#: boot-installer.xml:3498
#, fuzzy, no-c-format
msgid ""
"During the boot sequence, you may see many messages in the form "
"<computeroutput>can't find <replaceable>something</replaceable></"
"computeroutput>, or <computeroutput><replaceable>something</replaceable> not "
"present</computeroutput>, <computeroutput>can't initialize "
"<replaceable>something</replaceable></computeroutput>, or even "
"<computeroutput>this driver release depends on <replaceable>something</"
"replaceable></computeroutput>. Most of these messages are harmless. You see "
"them because the kernel for the installation system is built to run on "
"computers with many different peripheral devices. Obviously, no one computer "
"will have every possible peripheral device, so the operating system may emit "
"a few complaints while it looks for peripherals you don't own. You may also "
"see the system pause for a while. This happens when it is waiting for a "
"device to respond, and that device is not present on your system. If you "
"find the time it takes to boot the system unacceptably long, you can create "
"a custom kernel later <phrase arch=\"linux-any\">(see <xref linkend=\"kernel-"
"baking\"/>)</phrase>."
msgstr ""
"在開機期間，您可以看到很多資訊類似 <computeroutput>can't find "
"<replaceable>something</replaceable> </computeroutput>，或者 "
"<computeroutput> <replaceable>something</replaceable> not present</"
"computeroutput>， <computeroutput>can't initialize <replaceable>something</"
"replaceable> </computeroutput>，或者甚至 <computeroutput>this driver release "
"depends on <replaceable>something</replaceable> </computeroutput>。大多數這些"
"資訊都是無害的。您之所以看到它們，是因為安裝系統核心被設計成為可以在不同的電"
"腦上執行，並且擁有不同的周邊設備。顯然地，沒有一個電腦可能擁有所有的周邊設"
"備，因此作業系統可能在偵測一些您沒有的設備時送出一些警告。有時可以看到系統暫"
"停了一段時間。這是由於它在等待一台設備的回應，但是這台設備並沒有安裝在您的系"
"統上。如果您發現這段時間非常長，您可以之後重編自己的核心 <phrase arch="
"\"linux-any\">(請參閱 <xref linkend=\"kernel-baking\"/>)</phrase>。"

#. Tag: title
#: boot-installer.xml:3523
#, fuzzy, no-c-format
msgid "Reporting Installation Problems"
msgstr "常見的 &arch-title; 安裝問題"

#. Tag: para
#: boot-installer.xml:3524
#, fuzzy, no-c-format
msgid ""
"If you get through the initial boot phase but cannot complete the install, "
"the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. "
"It lets you store system error logs and configuration information from the "
"installer to a floppy, or download them using a web browser. This "
"information may provide clues as to what went wrong and how to fix it. If "
"you are submitting a bug report, you may want to attach this information to "
"the bug report."
msgstr ""
"如果您通過了初始化開機但是不能完成安裝，Bug Reporter 選單選項可能會很有用。它"
"會複製系統的錯誤記錄和設定資訊至一個使用者提供的軟碟中。這個資訊可能提供了一"
"些關於錯誤的原因和如何解決它的線索。如果您正在回報問題報告，您也許想附上這些"
"資訊。"

#. Tag: para
#: boot-installer.xml:3535
#, fuzzy, no-c-format
msgid ""
"Other pertinent installation messages may be found in <filename>/var/log/</"
"filename> during the installation, and <filename>/var/log/installer/</"
"filename> after the computer has been booted into the installed system."
msgstr ""
"其他相關安裝期間的安裝資訊可以在 <filename>/var/log/</filename> 找到，以及在"
"電腦已經啟動至安裝後的系統的 <filename>/var/log/debian-installer/</filename> "
"中。"

#. Tag: title
#: boot-installer.xml:3546
#, no-c-format
msgid "Submitting Installation Reports"
msgstr "回報安裝報告"

#. Tag: para
#: boot-installer.xml:3547
#, no-c-format
msgid ""
"If you still have problems, please submit an installation report. We also "
"encourage installation reports to be sent even if the installation is "
"successful, so that we can get as much information as possible on the "
"largest number of hardware configurations."
msgstr ""

#. Tag: para
#: boot-installer.xml:3554
#, no-c-format
msgid ""
"Note that your installation report will be published in the Debian Bug "
"Tracking System (BTS) and forwarded to a public mailing list. Make sure that "
"you use an e-mail address that you do not mind being made public."
msgstr ""

#. Tag: para
#: boot-installer.xml:3560
#, no-c-format
msgid ""
"If you have a working &debian; system, the easiest way to send an "
"installation report is to install the <classname>installation-report</"
"classname> and <classname>reportbug</classname> packages (<command>apt "
"install installation-report reportbug</command>), configure "
"<classname>reportbug</classname> as explained in <xref linkend=\"mail-"
"outgoing\"/>, and run the command <command>reportbug installation-reports</"
"command>."
msgstr ""

#. Tag: para
#: boot-installer.xml:3570
#, fuzzy, no-c-format
msgid ""
"Alternatively you can use this template when filling out installation "
"reports, and file the report as a bug report against the "
"<classname>installation-reports</classname> pseudo package, by sending it to "
"<email>submit@bugs.debian.org</email>. <informalexample><screen>\n"
"Package: installation-reports\n"
"\n"
"Boot method: &lt;How did you boot the installer? CD? floppy? network?&gt;\n"
"Image version: &lt;Full URL to image you downloaded is best&gt;\n"
"Date: &lt;Date and time of the install&gt;\n"
"\n"
"Machine: &lt;Description of machine (eg, IBM Thinkpad R32)&gt;\n"
"Processor:\n"
"Memory:\n"
"Partitions: &lt;df -Tl will do; the raw partition table is preferred&gt;\n"
"\n"
"Output of lspci -knn (or lspci -nn):\n"
"\n"
"Base System Installation Checklist:\n"
"[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n"
"\n"
"Initial boot:           [ ]\n"
"Detect network card:    [ ]\n"
"Configure network:      [ ]\n"
"Detect CD:              [ ]\n"
"Load installer modules: [ ]\n"
"Detect hard drives:     [ ]\n"
"Partition hard drives:  [ ]\n"
"Install base system:    [ ]\n"
"Clock/timezone setup:   [ ]\n"
"User/password setup:    [ ]\n"
"Install tasks:          [ ]\n"
"Install boot loader:    [ ]\n"
"Overall install:        [ ]\n"
"\n"
"Comments/Problems:\n"
"\n"
"&lt;Description of the install, in prose, and any thoughts, comments\n"
"      and ideas you had during the initial install.&gt;\n"
"</screen></informalexample> In the bug report, describe what the problem is, "
"including the last visible kernel messages in the event of a kernel hang. "
"Describe the steps that you did which brought the system into the problem "
"state."
msgstr ""
"如果您還是有問題，請回報臭蟲報告。即使您安裝成功，我們還是希望您能發一份安裝"
"報告，讓我們取得眾多硬體設定的更多資訊。請採用下列模板填寫安裝報告，並把這份"
"報告以 <classname>installation-reports</classname> 虛擬軟體套件之臭蟲報告的名"
"義，發送一封電子郵件至 <email>submit@bugs.debian.org</email>。 "
"<informalexample><screen>\n"
"Package: installation-reports\n"
"\n"
"Debian-installer-version: &lt;Fill in date and from where you got the "
"image&gt;\n"
"uname -a: &lt;The result of running uname -a on a shell prompt&gt;\n"
"Date: &lt;Date and time of the install&gt;\n"
"Method: &lt;How did you install?  What did you boot off?  If network\n"
"      install, from where?  Proxied?&gt;\n"
"\n"
"Machine: &lt;Description of machine (eg, IBM Thinkpad R32)&gt;\n"
"Processor:\n"
"Memory:\n"
"Root Device: &lt;IDE?  SCSI?  Name of device?&gt;\n"
"Root Size/partition table: &lt;Feel free to paste the full partition\n"
"      table, with notes on which partitions are mounted where.&gt;\n"
"Output of lspci and lspci -n:\n"
"\n"
"Base System Installation Checklist:\n"
"[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n"
"\n"
"Initial boot worked:    [ ]\n"
"Configure network HW:   [ ]\n"
"Config network:         [ ]\n"
"Detect CD:              [ ]\n"
"Load installer modules: [ ]\n"
"Detect hard drives:     [ ]\n"
"Partition hard drives:  [ ]\n"
"Create file systems:    [ ]\n"
"Mount partitions:       [ ]\n"
"Install base system:    [ ]\n"
"Install boot loader:    [ ]\n"
"Reboot:                 [ ]\n"
"\n"
"Comments/Problems:\n"
"\n"
"&lt;Description of the install, in prose, and any thoughts, comments\n"
"      and ideas you had during the initial install.&gt;\n"
"</screen></informalexample> 在臭蟲報告內，請描述問題，包括核心當住後見到的核"
"心訊息。請描述進入問題狀態前相關的步驟。"

# index.docbook:1899, index.docbook:1946
#, fuzzy
#~ msgid "SGI TFTP Booting"
#~ msgstr "SGI Indy 透過 TFTP 開機"

#, fuzzy
#~ msgid ""
#~ "After entering the command monitor use <informalexample><screen>\n"
#~ "bootp():\n"
#~ "</screen></informalexample> on SGI machines to boot linux and to begin "
#~ "installation of the &debian; Software. In order to make this work you may "
#~ "have to unset the <envar>netaddr</envar> environment variable. Type "
#~ "<informalexample><screen>\n"
#~ "unsetenv netaddr\n"
#~ "</screen></informalexample> in the command monitor to do this."
#~ msgstr ""
#~ "在進入指令監視器後使用 <informalexample><screen>\n"
#~ "bootp():\n"
#~ "</screen></informalexample> 在 SGI Indys 上啟動 Linux 及 &debian; 軟體的安"
#~ "裝。為了正常執行，您可能必須取消設定 <envar>netaddr</envar> 環境變數。輸"
#~ "入 <informalexample><screen>\n"
#~ "unsetenv netaddr\n"
#~ "</screen></informalexample> 到指令監視器。"

#, fuzzy
#~ msgid ""
#~ "On SGI machines you can append boot parameters to the <command>bootp():</"
#~ "command> command in the command monitor."
#~ msgstr ""
#~ "在 SGI Indys 上您可以在指令監視器下透過 <command>bootp():</command> 來附加"
#~ "開機參數。"

#~ msgid ""
#~ "Following the <command>bootp():</command> command you can give the path "
#~ "and name of the file to boot if you did not give an explicit name via "
#~ "your bootp/dhcp server. Example: <informalexample><screen>\n"
#~ "bootp():/boot/tftpboot.img\n"
#~ "</screen></informalexample> Further kernel parameters can be passed via "
#~ "<command>append</command>:"
#~ msgstr ""
#~ "如果您沒有透過 bootp/dhcp 伺服器提供清楚的名字檔名，在 <command>bootp():</"
#~ "command> 指令之後您可以給提供徑和檔案名稱來開機。例如 "
#~ "<informalexample><screen>\n"
#~ "bootp():/boot/tftpboot.img\n"
#~ "</screen></informalexample> 還有更多的核心參數傳遞可以用 <command>append</"
#~ "command>:"

#~ msgid "bootp(): append=\"root=/dev/sda1\""
#~ msgstr "bootp(): append=\"root=/dev/sda1\""

#, fuzzy
#~| msgid ""
#~| "When the installer boots, you should be presented with a friendly "
#~| "graphical screen showing the Debian logo and the boot prompt: "
#~| "<informalexample><screen>\n"
#~| "Press F1 for help, or ENTER to boot:\n"
#~| "</screen></informalexample> At the boot prompt you can either just press "
#~| "&enterkey; to boot the installer with default options or enter a "
#~| "specific boot method and, optionally, boot parameters."
#~ msgid ""
#~ "When the installer boots, you should be presented with a friendly "
#~ "graphical screen showing the &debian; logo and a menu: "
#~ "<informalexample><screen>\n"
#~ "Installer boot menu\n"
#~ "\n"
#~ "Install\n"
#~ "Graphical install\n"
#~ "Advanced options             >\n"
#~ "Help\n"
#~ "Install with speech synthesis\n"
#~ "\n"
#~ "Press ENTER to boot or TAB to edit a menu entry\n"
#~ "</screen></informalexample> Depending on the installation method you are "
#~ "using, the <quote>Graphical install</quote> option may not be available. "
#~ "Bi-arch images additionally have a 64 bit variant for each install "
#~ "option, right below it, thus almost doubling the number of options."
#~ msgstr ""
#~ "安裝程式啟動後，您應該會看到一個友善的畫面，顯示著 &debian; 的標誌，以及啟"
#~ "動提示：<informalexample><screen>\n"
#~ "Press F1 for help, or ENTER to boot:\n"
#~ "</screen></informalexample> 在提示號下您可以直接按下 &enterkey; 來使用預設"
#~ "選項啟動安裝程式，或者輸入參數以指定您要使用的啟動方式。"

#~ msgid "Booting from CD-ROM"
#~ msgstr "從光碟開機"

#, fuzzy
#~ msgid "Booting the SS4000-E"
#~ msgstr "採用 MILO 開機"

# index.docbook:1899, index.docbook:1946
#, fuzzy
#~ msgid "Cobalt TFTP Booting"
#~ msgstr "SGI Indy 透過 TFTP 開機"

#, fuzzy
#~ msgid ""
#~ "You cannot pass any boot parameters directly. Instead, you have to edit "
#~ "the <filename>/nfsroot/default.colo</filename> file on the NFS server and "
#~ "add your parameters to the <replaceable>args</replaceable> variable."
#~ msgstr ""
#~ "您不能從 CFE 提示符號直接傳遞啟動參數。而是編輯 TFTP 伺服器上的 "
#~ "<filename>/boot/sibyl.conf</filename> 文件並添加參數到 "
#~ "<replaceable>extra_args</replaceable> 變數。"

#~ msgid ""
#~ "When the kernel boots, a message <informalexample><screen>\n"
#~ "Memory:<replaceable>avail</replaceable>k/<replaceable>total</"
#~ "replaceable>k available\n"
#~ "</screen></informalexample> should be emitted early in the process. "
#~ "<replaceable>total</replaceable> should match the total amount of RAM, in "
#~ "kilobytes. If this doesn't match the actual amount of RAM you have "
#~ "installed, you need to use the <userinput>mem=<replaceable>ram</"
#~ "replaceable></userinput> parameter, where <replaceable>ram</replaceable> "
#~ "is set to the amount of memory, suffixed with <quote>k</quote> for "
#~ "kilobytes, or <quote>m</quote> for megabytes. For example, both "
#~ "<userinput>mem=65536k</userinput> and <userinput>mem=64m</userinput> mean "
#~ "64MB of RAM."
#~ msgstr ""
#~ "當核心開機的時候，一條訊息 <informalexample><screen>\n"
#~ "Memory:<replaceable>avail</replaceable>k/<replaceable>total</"
#~ "replaceable>k available \n"
#~ "</screen></informalexample> 應該會在開機過程的早期顯示。其中 "
#~ "<replaceable>total</replaceable> 應該符合您記憶體的總量，其中單位為多少 "
#~ "kb。如果此參數不符合您安裝的記憶體總數，需要使用 "
#~ "<userinput>mem=<replaceable>ram</replaceable></userinput> 參數。 這裡 "
#~ "<replaceable>ram</replaceable> 被設成記憶體的數量。如是 <quote>k</quote> "
#~ "為位元組，<quote>m</quote> 為兆位元組。例如，<userinput>mem=65536k</"
#~ "userinput> 和 <userinput>mem=64m</userinput> 表示 64MB 記憶體。"

#, fuzzy
#~ msgid ""
#~ "Often, problems can be solved by removing add-ons and peripherals, and "
#~ "then trying booting again. <phrase arch=\"any-x86\">Internal modems, "
#~ "sound cards, and Plug-n-Play devices can be especially problematic.</"
#~ "phrase>"
#~ msgstr ""
#~ "通稱，可以透過移除外掛硬體或者周邊設備來解決問題，然後再次重新開機。"
#~ "<phrase arch=\"any-x86\"> 內建的調變解調器、音效卡以及隨插即用的設備通常很"
#~ "容易引起問題。</phrase>"

#~ msgid ""
#~ "If you have a large amount of memory installed in your machine, more than "
#~ "512M, and the installer hangs when booting the kernel, you may need to "
#~ "include a boot argument to limit the amount of memory the kernel sees, "
#~ "such as <userinput>mem=512m</userinput>."
#~ msgstr ""
#~ "如果您的機器上裝有多於 512M 的大容量的記憶體，並且安裝程式在啟動核心時當"
#~ "住，您可能需要加入一個開機參數，來限制核心能夠看到的記憶體數量，例如 "
#~ "<userinput>mem=512m</userinput>。"

#~ msgid ""
#~ "Some systems have floppies with <quote>inverted DCLs</quote>. If you "
#~ "receive errors reading from the floppy, even when you know the floppy is "
#~ "good, try the parameter <userinput>floppy=thinkpad</userinput>."
#~ msgstr ""
#~ "一些系統的軟碟會有 ``inverted DCLs''。如果您在讀軟碟時遇到錯誤資訊，並且您"
#~ "可以確定軟碟是好的，嘗試參數 <userinput>floppy=thinkpad</userinput>。"

#~ msgid ""
#~ "On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 "
#~ "disk drivers), the IDE drive may not be properly recognized. Again, try "
#~ "it first without the parameters and see if the IDE drive is recognized "
#~ "properly. If not, determine your drive geometry (cylinders, heads, and "
#~ "sectors), and use the parameter <userinput>hd=<replaceable>cylinders</"
#~ "replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</"
#~ "replaceable></userinput>."
#~ msgstr ""
#~ "在一些系統上，例如 IBM PS/1 或者 ValuePoint (具有 ST-506 設備)，IDE 設備可"
#~ "能無法辨識。請首先嘗試沒有參數的開機情況下是否能夠被識別。如果不行，請確定"
#~ "設備的幾何參數 (柱面，磁頭還有磁區)。然後使用參數 "
#~ "<userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</"
#~ "replaceable>,<replaceable>sectors</replaceable></userinput>。"

#~ msgid ""
#~ "If you have a very old machine, and the kernel hangs after saying "
#~ "<computeroutput>Checking 'hlt' instruction...</computeroutput>, then you "
#~ "should try the <userinput>no-hlt</userinput> boot argument, which "
#~ "disables this test."
#~ msgstr ""
#~ "如果您有一台非常老的機器，並且核心在顯示 <computeroutput>Checking 'hlt' "
#~ "instruction...</computeroutput> 時中斷，需要嘗試 <userinput>no-hlt</"
#~ "userinput> 參數來取消這個測試。"

#, fuzzy
#~ msgid "System Freeze while Loading USB Modules"
#~ msgstr "在裝入 USB 模組時系統當機"

#, fuzzy
#~ msgid ""
#~ "The kernel normally tries to install USB modules and the USB keyboard "
#~ "driver in order to support some non-standard USB keyboards. However, "
#~ "there are some broken USB systems where the driver hangs on loading. A "
#~ "possible workaround may be disabling the USB controller in your mainboard "
#~ "BIOS setup. Another option is passing the <userinput>nousb</userinput> "
#~ "parameter at the boot prompt."
#~ msgstr ""
#~ "核心在正常情況下會嘗試安裝 USB 模組以及 USB 鍵盤驅動程式來支援一些非標準"
#~ "的 USB 鍵盤。但是，有些不完整的 USB 系統會在驅動程式載入時當機。一個可能的"
#~ "解決方法是在 BIOS 設置內禁用您的 USB 控制器。或者在開機提示符號處傳遞 "
#~ "<userinput>debian-installer/probe/usb=false</userinput> 參數，這將阻止載入"
#~ "此模組。"

#, fuzzy
#~ msgid "Booting the NSLU2"
#~ msgstr "採用 MILO 開機"

#~ msgid ""
#~ "If your system doesn't boot directly from CD-ROM, you can still use the "
#~ "CD-ROM to install the system. On NewWorlds, you can also use an "
#~ "OpenFirmware command to boot from the CD-ROM manually. Follow the "
#~ "instructions in <xref linkend=\"boot-newworld\"/> for booting from the "
#~ "hard disk, except use the path to <command>yaboot</command> on the CD at "
#~ "the OF prompt, such as"
#~ msgstr ""
#~ "如果您的系統不支援直接從光碟啟動，仍然可以採用光碟來安裝系統。在 "
#~ "NewWorlds 上面，可以使用一個 OpenFirmware 指令來手動光碟開機。除了在 OF 提"
#~ "示符號下使用光碟上的 <command>yaboot</command>，按照 <xref linkend=\"boot-"
#~ "newworld\"/> 的方法從硬碟來進行開機，例如："

#, fuzzy
#~ msgid ""
#~ "The <userinput>video=vga16:off</userinput> argument may also be used to "
#~ "disable the kernel's use of the framebuffer. Such problems have been "
#~ "reported on a Dell Inspiron with Mobile Radeon card."
#~ msgstr ""
#~ "<userinput>video=vga16:off</userinput> 參數可以被用來停用 framebuffer。這"
#~ "類問題的報告原於使用 Mobile Radeon 卡的 Dell Inspiron 上。"

#~ msgid "Alpha Console Firmware"
#~ msgstr "Alpha 控制台韌體"

#~ msgid ""
#~ "Console firmware is stored in a flash ROM and started when an Alpha "
#~ "system is powered up or reset. There are two different console "
#~ "specifications used on Alpha systems, and hence two classes of console "
#~ "firmware available:"
#~ msgstr ""
#~ "控制台韌體是儲存在一個快閃 ROM 中並且每次在 Alpha 系統開機或者重新啟動的時"
#~ "候啟動。在 Alpha 系統上有兩種規格的控制台，並且因此有兩類控制台韌體供使"
#~ "用。"

#~ msgid ""
#~ "<emphasis>SRM console</emphasis>, based on the Alpha Console Subsystem "
#~ "specification, which provides an operating environment for OpenVMS, Tru64 "
#~ "UNIX, and Linux operating systems."
#~ msgstr ""
#~ "<emphasis>SRM console</emphasis> 基於 Alpha 控制檯子系統。它為 OpenVMS， "
#~ "Tru64 Unix，以及 Linux 作業系統提供了一個操作環境。"

#~ msgid ""
#~ "<emphasis>ARC, AlphaBIOS, or ARCSBIOS console</emphasis>, based on the "
#~ "Advanced RISC Computing (ARC) specification, which provides an operating "
#~ "environment for Windows NT."
#~ msgstr ""
#~ "<emphasis>ARC, AlphaBIOS 或 ARCSBIOS console</emphasis> 以 Advanced RISC "
#~ "Computing (ARC) 為基礎，為 Windows NT 提供了一個操作環境。"

#~ msgid ""
#~ "From the user's perspective, the most important difference between SRM "
#~ "and ARC is that the choice of console constrains the possible disk-"
#~ "partitioning scheme for the hard disk which you wish to boot off of."
#~ msgstr ""
#~ "從使用者的角度看，SRM 和 ARC 最重要的區別是控制台的選擇，可能會影響到您開"
#~ "機磁碟的分割方式。"

#~ msgid ""
#~ "ARC requires that you use an MS-DOS partition table (as created by "
#~ "<command>cfdisk</command>) for the boot disk. Therefore MS-DOS partition "
#~ "tables are the <quote>native</quote> partition format when booting from "
#~ "ARC. In fact, since AlphaBIOS contains a disk partitioning utility, you "
#~ "may prefer to partition your disks from the firmware menus before "
#~ "installing Linux."
#~ msgstr ""
#~ "ARC 需要您在開機磁碟上建立一個 MS-DOS 分割表(用 <command>cfdisk</command> "
#~ "建立)。因此 MS-DOS 分割表是從 ARC 開機的``原始''分割區格式。事實上，由於 "
#~ "AlphaBIOS 包含了一個磁碟分割工具，您也許可以在安裝 Linux 時透過韌體選單對"
#~ "磁碟進行分割區。"

#~ msgid ""
#~ "Conversely, SRM is <emphasis>incompatible</emphasis><footnote> <para> "
#~ "Specifically, the bootsector format required by the Console Subsystem "
#~ "Specification conflicts with the placement of the DOS partition table. </"
#~ "para> </footnote> with MS-DOS partition tables. Since Tru64 Unix uses the "
#~ "BSD disklabel format, this is the <quote>native</quote> partition format "
#~ "for SRM installations."
#~ msgstr ""
#~ "保守地說，SRM 是<emphasis>不相容</emphasis>於 <footnote> <para> 具體來說，"
#~ "控制檯子系統規範與需要的開機磁區格式和 DOS 分割表表衝突。</para> </"
#~ "footnote> MS-DOS 分割表。由於 Tru64 Unix 使用的是 BSD 磁碟標記格式，對於 "
#~ "SRM 安裝來說，這是一個<quote>原始的</quote>分割區格式。"

#~ msgid ""
#~ "GNU/Linux is the only operating system on Alpha that can be booted from "
#~ "both console types, but &debian-gnu; &release; only supports booting on "
#~ "SRM-based systems. If you have an Alpha for which no version of SRM is "
#~ "available, if you will be dual-booting the system with Windows NT, or if "
#~ "your boot device requires ARC console support for BIOS initialization, "
#~ "you will not be able to use the &debian-gnu; &release; installer. You can "
#~ "still run &debian-gnu; &release; on such systems by using other install "
#~ "media; for instance, you can install Debian woody with MILO and upgrade."
#~ msgstr ""
#~ "由於 GNU/Linux 是唯一能夠透過兩種控制台格式開機的系統，但是 &debian-gnu; "
#~ "$release只支援從以 SRM 為基礎的系統開機。如果您的 Alpha 沒有任何版本的 "
#~ "SRM，如果您希望和 Windows NT 做雙重開機，或是您個開機設備需要 ARC 控制台支"
#~ "援 BIOS 的初始化，您無法使用 &debian-gnu; &release; 安裝程式。所有其他的 "
#~ "Unix 型作業系統 (Tru64 Unix，FreeBSD，OpenBSD，以及 NetBSD) 和 OpenVMS 只"
#~ "能從 SRM 上面開機，而 Windows NT 只能從 ARC 上面開機。"

#~ msgid ""
#~ "Because <command>MILO</command> is not available for any of the Alpha "
#~ "systems currently in production (as of February 2000), and because it is "
#~ "no longer necessary to buy an OpenVMS or Tru64 Unix license to have SRM "
#~ "firmware on your older Alpha, it is recommended that you use SRM when "
#~ "possible."
#~ msgstr ""
#~ "由於在目前生產的 Alpha 系統上並沒有實作 <command>MILO</command>(從 2000 年"
#~ "二月份開始)。而且購買一個 OpenVMS 和 Tru64 Unix 授權，來在老 Alpha 上裝上 "
#~ "SRM 韌體也是不必要的。我們建議在新的機器上使用 SRM。"

#~ msgid ""
#~ "The following table summarizes available and supported system type/"
#~ "console combinations (see <xref linkend=\"alpha-cpus\"/> for the system "
#~ "type names). The word <quote>ARC</quote> below denotes any of the ARC-"
#~ "compliant consoles."
#~ msgstr ""
#~ "下面表格總括了可用以及支援的系統類型/控制台組合 (系統類型名稱參閱 <xref "
#~ "linkend=\"alpha-cpus\"/> )。<quote>ARC</quote> 一詞表示任何和 ARC 相容的控"
#~ "制台。"

#~ msgid "System Type"
#~ msgstr "系統類型"

#~ msgid "Console Type Supported"
#~ msgstr "支援的控制台類型"

#~ msgid "alcor"
#~ msgstr "alcor"

# index.docbook:110, index.docbook:113, index.docbook:119, index.docbook:125, index.docbook:128, index.docbook:131, index.docbook:134, index.docbook:140, index.docbook:143, index.docbook:146, index.docbook:155, index.docbook:164, index.docbook:179, index.docbook:182, index.docbook:188
#~ msgid "ARC or SRM"
#~ msgstr "ARC or SRM"

#~ msgid "avanti"
#~ msgstr "avanti"

#~ msgid "book1"
#~ msgstr "book1"

# index.docbook:116, index.docbook:122, index.docbook:137, index.docbook:149, index.docbook:158, index.docbook:161, index.docbook:167, index.docbook:173, index.docbook:176
#~ msgid "SRM only"
#~ msgstr "SRM only"

#~ msgid "cabriolet"
#~ msgstr "cabriolet"

#~ msgid "dp264"
#~ msgstr "dp264"

#~ msgid "eb164"
#~ msgstr "eb164"

#~ msgid "eb64p"
#~ msgstr "eb64p"

#~ msgid "eb66"
#~ msgstr "eb66"

#~ msgid "eb66p"
#~ msgstr "eb66p"

#~ msgid "jensen"
#~ msgstr "jensen"

#~ msgid "lx164"
#~ msgstr "lx164"

#~ msgid "miata"
#~ msgstr "miata"

#~ msgid "mikasa"
#~ msgstr "mikasa"

#~ msgid "mikasa-p"
#~ msgstr "mikasa-p"

#~ msgid "nautilus"
#~ msgstr "nautilus"

#~ msgid "ARC (see motherboard manual) or SRM"
#~ msgstr "ARC (see motherboard manual) or SRM"

#~ msgid "noname"
#~ msgstr "noname"

#~ msgid "noritake"
#~ msgstr "noritake"

#~ msgid "noritake-p"
#~ msgstr "noritake-p"

#~ msgid "pc164"
#~ msgstr "pc164"

#~ msgid "rawhide"
#~ msgstr "rawhide"

#~ msgid "ruffian"
#~ msgstr "ruffian"

# index.docbook:170, index.docbook:185
#~ msgid "ARC only"
#~ msgstr "ARC only"

#~ msgid "sable"
#~ msgstr "sable"

#~ msgid "sable-g"
#~ msgstr "sable-g"

#~ msgid "sx164"
#~ msgstr "sx164"

#~ msgid "takara"
#~ msgstr "takara"

#~ msgid "<entry>xl</entry>"
#~ msgstr "<entry>xl</entry>"

#~ msgid "<entry>xlt</entry>"
#~ msgstr "<entry>xlt</entry>"

#~ msgid ""
#~ "Generally, none of these consoles can boot Linux directly, so the "
#~ "assistance of an intermediary bootloader is required. For the SRM "
#~ "console, <command>aboot</command>, a small, platform-independent "
#~ "bootloader, is used. See the (unfortunately outdated) <ulink url=\"&url-"
#~ "srm-howto;\">SRM HOWTO</ulink> for more information on <command>aboot</"
#~ "command>."
#~ msgstr ""
#~ "一般來說，這些控制台都不能直接以 Linux 開機，因此需要一個中繼的 boot-"
#~ "loader。SRM 控制台使用一個小型的、平台獨立的 boot-loader，<command>aboot</"
#~ "command>。請參閱 (抱歉的是它也有點過時了) <ulink url=\"&url-srm-howto;"
#~ "\">SRM HOWTO</ulink>來獲得更多有關資訊 <command>aboot</command>。"

#~ msgid ""
#~ "The following paragraphs are from the woody install manual, and are "
#~ "included here for reference; they may be useful to someone at a later "
#~ "date when Debian supports MILO-based installs again."
#~ msgstr ""
#~ "以下章節來自 woody 安裝手冊，放在這裡作為參考﹔如果以後 Debian 再支援基於 "
#~ "MILO 的安裝，它們或許對某些人有用。"

#~ msgid ""
#~ "Generally, none of these consoles can boot Linux directly, so the "
#~ "assistance of an intermediary bootloader is required. There are two "
#~ "mainstream Linux loaders: <command>MILO</command> and <command>aboot</"
#~ "command>."
#~ msgstr ""
#~ "一般來說，這些控制台都不能直接以 Linux 開機，因此需要一個中繼的 boot-"
#~ "loader。這裡有兩個主要的 Linux loader：<command>MILO</command> 和 "
#~ "<command>aboot</command>。"

#~ msgid ""
#~ "<command>MILO</command> is itself a console, which replaces ARC or SRM in "
#~ "memory. <command>MILO</command> can be booted from both ARC and SRM and "
#~ "is the only way to bootstrap Linux from the ARC console. <command>MILO</"
#~ "command> is platform-specific (a different <command>MILO</command> is "
#~ "needed for each system type) and exist only for those systems, for which "
#~ "ARC support is shown in the table above. See also the (unfortunately "
#~ "outdated) <ulink url=\"&url-milo-howto;\">MILO HOWTO</ulink>."
#~ msgstr ""
#~ "<command>MILO</command> 自己本身就是一個控制台，可以替換載入記憶體中的 "
#~ "ARC 和 SRM。<command>MILO</command> 能夠同時從 ARC 和 SRM 開機並且是唯一一"
#~ "種從 ARC 控制台啟動 Linux 的方法。<command>MILO</command> 是與平台相依的 "
#~ "(對於每種不同的系統需要不同的 <command>MILO</command>) 並且只適合這些平"
#~ "台。請參閱 (很遺憾有點過時) <ulink url=\"&url-milo-howto;\">MILO HOWTO</"
#~ "ulink>。"

#~ msgid ""
#~ "<command>aboot</command> is a small, platform-independent bootloader, "
#~ "which runs from SRM only. See the (also unfortunately outdated) <ulink "
#~ "url=\"&url-srm-howto;\">SRM HOWTO</ulink> for more information on "
#~ "<command>aboot</command>."
#~ msgstr ""
#~ "<command>aboot</command> 是一個小型的，平台獨立的 boot-loader，不過只運作"
#~ "於 SRM 上。請參閱 (遺憾的是它也有點過時了 ) <ulink url=\"&url-srm-howto;"
#~ "\">SRM HOWTO</ulink>來取得更多有關資訊 <command>aboot</command>。"

#~ msgid ""
#~ "Thus, three scenarios are generally possible, depending on the system's "
#~ "console firmware and whether or not <command>MILO</command> is available: "
#~ "<informalexample><screen>\n"
#~ "SRM -&gt; aboot\n"
#~ "SRM -&gt; MILO\n"
#~ "ARC -&gt; MILO\n"
#~ "</screen></informalexample> Because <command>MILO</command> is not "
#~ "available for any of the Alpha systems currently in production (as of "
#~ "February 2000), and because it is no longer necessary to buy an OpenVMS "
#~ "or Tru64 Unix license to have SRM firmware on your older Alpha, it is "
#~ "recommended that you use SRM and <command>aboot</command> on new "
#~ "installations of GNU/Linux, unless you wish to dual-boot with Windows NT."
#~ msgstr ""
#~ "因此，三種方案都是可行的，但取決與系統控制台韌體以及是否有可用的 "
#~ "<command>MILO</command>：<informalexample><screen>\n"
#~ "SRM -&gt; aboot\n"
#~ "SRM -&gt; MILO\n"
#~ "ARC -&gt; MILO\n"
#~ "</screen></informalexample> 由於 <command>MILO</command> 並沒有實作於目前"
#~ "生產的 Alpha 系統上(從 2000 年二月份開始)。而且也不需要購買 OpenVMS 和 "
#~ "Tru64 Unix 授權，來在老 Alpha 上裝上 SRM 韌體。除非您想採用 Windows NT 並"
#~ "且進行雙開機，我們建議在新的機器上使用 SRM 和 <command>aboot</command> 安"
#~ "裝 Linux。"

#~ msgid ""
#~ "The majority of AlphaServers and all current server and workstation "
#~ "products contain both SRM and AlphaBIOS in their firmware. For "
#~ "<quote>half-flash</quote> machines such as the various evaluation boards, "
#~ "it is possible to switch from one version to another by reflashing the "
#~ "firmware. Also, once SRM is installed, it is possible to run ARC/"
#~ "AlphaBIOS from a floppy disk (using the <command>arc</command> command). "
#~ "For the reasons mentioned above, we recommend switching to SRM before "
#~ "installing &debian-gnu;."
#~ msgstr ""
#~ "大部分 AlphaServers 以及目前所有的伺服器以及工作站產品韌體中都同時含有 "
#~ "SRM 和 AlphaBIOS 。對於具有不同試用主機板的 <quote>half-flash</quote> 機器"
#~ "來說。可以透過重寫韌體切換到另外一個版本。一旦 SRM 安裝完畢，從軟碟上運行 "
#~ "ARC/AlphaBIOS 也是可能的 (使用 <command>arc</command>)。基於上述理由，我們"
#~ "建議在安裝 &debian-gnu; 之前切換至 SRM。"

#~ msgid ""
#~ "As on other architectures, you should install the newest available "
#~ "revision of the firmware<footnote> <para> Except on Jensen, where Linux "
#~ "is not supported on firmware versions newer than 1.7 &mdash; see <ulink "
#~ "url=\"&url-jensen-howto;\"></ulink> for more information. </para> </"
#~ "footnote> before installing &debian-gnu;. For Alpha, firmware updates can "
#~ "be obtained from <ulink url=\"&url-alpha-firmware;\">Alpha Firmware "
#~ "Updates</ulink>."
#~ msgstr ""
#~ "和其他的架構一樣，您也應該在安裝 &debian-gnu; 之前安裝最新的韌體版本。但 "
#~ "<footnote><para> 不包括 Jensen 1.7 以上的韌體版本，其不支援 Linux &mdash; "
#~ "請參閱 <ulink url=\"&url-jensen-howto;\"></ulink> 以取得更多的資訊。</"
#~ "para> </footnote>。對於 Alpha 來說，韌體升級可以從 <ulink url=\"&url-"
#~ "alpha-firmware;\">Alpha Firmware Updates</ulink> 取得。"

#, fuzzy
#~ msgid ""
#~ "In SRM, Ethernet interfaces are named with the <userinput>ewa</userinput> "
#~ "prefix, and will be listed in the output of the <userinput>show dev</"
#~ "userinput> command, like this (edited slightly): "
#~ "<informalexample><screen>\n"
#~ "&gt;&gt;&gt; show dev\n"
#~ "ewa0.0.0.9.0               EWA0              08-00-2B-86-98-65\n"
#~ "ewb0.0.0.11.0              EWB0              08-00-2B-86-98-54\n"
#~ "ewc0.0.0.2002.0            EWC0              00-06-2B-01-32-B0\n"
#~ "</screen></informalexample> You first need to set the boot protocol: "
#~ "<informalexample><screen>\n"
#~ "&gt;&gt;&gt; set ewa0_protocols bootp\n"
#~ "</screen></informalexample> Then check the medium type is correct: "
#~ "<informalexample><screen>\n"
#~ "&gt;&gt;&gt; set ewa0_mode <replaceable>mode</replaceable>\n"
#~ "</screen></informalexample> You can get a listing of valid modes with "
#~ "<userinput>&gt;&gt;&gt;set ewa0_mode</userinput>."
#~ msgstr ""
#~ "在 SRM 上，以太網路介面名稱帶有 <userinput>ewa</userinput> 前綴，並可以用 "
#~ "<userinput>show dev</userinput> 命令列出，類似如下 (可能有一點不同)："
#~ "<informalexample><screen>\n"
#~ "&gt;&gt;&gt; show dev\n"
#~ "ewa0.0.0.9.0               EWA0              08-00-2B-86-98-65\n"
#~ "ewb0.0.0.11.0              EWB0              08-00-2B-86-98-54\n"
#~ "ewc0.0.0.2002.0            EWC0              00-06-2B-01-32-B0\n"
#~ "</screen></informalexample> 您首先需要設定開機協定： "
#~ "<informalexample><screen>\n"
#~ "&gt;&gt;&gt; set ewa0_protocol bootp\n"
#~ "</screen></informalexample> 然後檢查媒介類型是否正確： "
#~ "<informalexample><screen>\n"
#~ "&gt;&gt;&gt; set ewa0_mode <replaceable>mode</replaceable>\n"
#~ "</screen></informalexample> 您檢閱有效模式的列表 <userinput>&gt;&gt;&gt;"
#~ "set ewa0_mode</userinput>。"

#~ msgid ""
#~ "Then, to boot from the first Ethernet interface, you would type: "
#~ "<informalexample><screen>\n"
#~ "&gt;&gt;&gt; boot ewa0 -flags \"\"\n"
#~ "</screen></informalexample> This will boot using the default kernel "
#~ "parameters as included in the netboot image."
#~ msgstr ""
#~ "接下來，如果從第一個以太網路介面開機，您需要輸入："
#~ "<informalexample><screen>\n"
#~ "&gt;&gt;&gt; boot ewa0 -flags \"\"\n"
#~ "</screen></informalexample> 這會把 netboot 映像啟動，並使用預設的核心參"
#~ "數。"

#~ msgid ""
#~ "If you wish to use a serial console, you <emphasis>must</emphasis> pass "
#~ "the <userinput>console=</userinput> parameter to the kernel. This can be "
#~ "done using the <userinput>-flags</userinput> argument to the SRM "
#~ "<userinput>boot</userinput> command. The serial ports are named the same "
#~ "as their corresponding files in <userinput>/dev</userinput>. Also, when "
#~ "specifying additional kernel parameters, you must repeat certain default "
#~ "options that are needed by the &d-i; images. For example, to boot from "
#~ "<userinput>ewa0</userinput> and use a console on the first serial port, "
#~ "you would type:"
#~ msgstr ""
#~ "如果希望使用一個序列控制台，您<emphasis>必須</emphasis>傳遞 "
#~ "<userinput>console=</userinput> 參數給核心。這個工作可以使用SRM "
#~ "<userinput>boot</userinput> 指令加上 <userinput>-flags</userinput> 參數來"
#~ "完成。序列埠編號的命名和它們在目錄 <userinput>/dev</userinput> 中相同。另"
#~ "外，如有指定額外的核心參數，那麼連預設值也必須指定給 &d-i; 映像。例如，若"
#~ "需要從 <userinput>ewa0</userinput> 開機，並且在第一個序列埠使用控制台，您"
#~ "得輸入："

#~ msgid ""
#~ "&gt;&gt;&gt; boot ewa0 -flags &quot;root=/dev/ram ramdisk_size=16384 "
#~ "console=ttyS0&quot;"
#~ msgstr ""
#~ "&gt;&gt;&gt; boot ewa0 -flags &quot;root=/dev/ram ramdisk_size=16384 "
#~ "console=ttyS0&quot;"

#~ msgid "Booting from CD-ROM with the SRM Console"
#~ msgstr "透過 SRM 控制台來從光碟開機"

#~ msgid "Booting from CD-ROM with the ARC or AlphaBIOS Console"
#~ msgstr "透過 ARC 或者 AlphaBIOS 控制台來從光碟啟動"

#~ msgid ""
#~ "To boot a CD-ROM from the ARC console, find your sub-architecture code "
#~ "name (see <xref linkend=\"alpha-cpus\"/>), then enter <filename>\\milo"
#~ "\\linload.exe</filename> as the boot loader and <filename>\\milo"
#~ "\\<replaceable>subarch</replaceable></filename> (where "
#~ "<replaceable>subarch</replaceable> is the proper subarchitecture name) as "
#~ "the OS Path in the `OS Selection Setup' menu. Ruffians make an exception: "
#~ "You need to use <filename>\\milo\\ldmilo.exe</filename> as boot loader."
#~ msgstr ""
#~ "為了透過 ARC 控制台以光碟開機，找出您的子架構結構代碼名稱 (請參閱 <xref "
#~ "linkend=\"alpha-cpus\"/>)，然後輸入 <filename>\\milo\\linload.exe</"
#~ "filename> 作為 boot-loader 並且在 `OS Selection Setup' 選單下選擇 "
#~ "<filename>\\milo\\<replaceable>subarch</replaceable></filename> "
#~ "(<replaceable>subarch</replaceable> 是相應的子架構結構名稱) 作為作業系統路"
#~ "徑。Ruffians 則是一個例外：您需要使用 <filename>\\milo\\ldmilo.exe</"
#~ "filename> 作為 boot-loader 。"

#~ msgid "Booting from Floppies with the SRM Console"
#~ msgstr "透過 SRM 控制台從軟碟開機"

#~ msgid ""
#~ "At the SRM prompt (<prompt>&gt;&gt;&gt;</prompt>), issue the following "
#~ "command: <informalexample><screen>\n"
#~ "&gt;&gt;&gt; boot dva0 -flags 0\n"
#~ "</screen></informalexample> possibly replacing <filename>dva0</filename> "
#~ "with the actual device name. Usually, <filename>dva0</filename> is the "
#~ "floppy; type <informalexample><screen>\n"
#~ "&gt;&gt;&gt; show dev\n"
#~ "</screen></informalexample> to see the list of devices (e.g., if you want "
#~ "to boot from a CD). Note that if you are booting via MILO, <command>-"
#~ "flags</command> argument is ignored, so you can just type <command>boot "
#~ "dva0</command>. If everything works OK, you will eventually see the Linux "
#~ "kernel boot."
#~ msgstr ""
#~ "在 SRM 提示符號下 (<prompt>&gt;&gt;&gt;</prompt>)，使用如下指令："
#~ "<informalexample><screen>\n"
#~ "&gt;&gt;&gt; boot dva0 -flags 0\n"
#~ "</screen></informalexample> 可能要以實際的設備名稱來替換 <filename>dva0</"
#~ "filename>。一般狀況下，<filename>dva0</filename> 是軟碟﹔輸入 "
#~ "<informalexample><screen>\n"
#~ "&gt;&gt;&gt; show dev\n"
#~ "</screen></informalexample> 來查看設備列表 (例如，如果您想從光碟開機)。注"
#~ "意如果您想透過 MILO 開機，<command>-flags</command> 參數將被忽略，因此您可"
#~ "以只輸入 <command>boot dva0</command>。如果上面步驟正常執行，您最終將看到 "
#~ "Linux 核心啟動。"

#~ msgid ""
#~ "If you want to specify kernel parameters when booting via <command>aboot</"
#~ "command>, use the following command: <informalexample><screen>\n"
#~ "&gt;&gt;&gt; boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 "
#~ "load_ramdisk=1 arguments\"\n"
#~ "</screen></informalexample> (typed on one line), substituting, if "
#~ "necessary, the actual SRM boot device name for <filename>dva0</filename>, "
#~ "the Linux boot device name for <filename>fd0</filename>, and the desired "
#~ "kernel parameters for <filename>arguments</filename>."
#~ msgstr ""
#~ "如果您想在透過 <command>aboot</command> 開機的時候指定特定的核心參數，請使"
#~ "用如下指令：<informalexample><screen>\n"
#~ "&gt;&gt;&gt; boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 "
#~ "load_ramdisk=1 arguments\"\n"
#~ "</screen></informalexample> (以一行輸入)，如果有需要，替換 "
#~ "<filename>dva0</filename> 的真實 SRM 開機設備名稱，<filename>fd0</"
#~ "filename> 是 Linux 的開機設備名稱，而 <filename>arguments</filename> 是需"
#~ "要指定的核心參數。"

#~ msgid ""
#~ "If you want to specify kernel parameters when booting via <command>MILO</"
#~ "command>, you will have to interrupt bootstrap once you get into MILO. "
#~ "See <xref linkend=\"booting-from-milo\"/>."
#~ msgstr ""
#~ "如果您想在透過 <command>MILO</command> 開機時指定核心參數，您必須在進入 "
#~ "MILO 時中斷開機。請參閱 <xref linkend=\"booting-from-milo\"/>。"

#~ msgid "Booting from Floppies with the ARC or AlphaBIOS Console"
#~ msgstr "透過 ARC 或者 AlphaBISO 控制台從軟碟開機"

#~ msgid ""
#~ "In the OS Selection menu, set <command>linload.exe</command> as the boot "
#~ "loader, and <command>milo</command> as the OS Path. Bootstrap using the "
#~ "newly created entry."
#~ msgstr ""
#~ "在作業系統選擇選單內，設定 <command>linload.exe</command> 作為 boot-"
#~ "loader，並且將 <command>milo</command> 作為作業系統參數。然後使用這個最近"
#~ "建立的選項啟動。"

#~ msgid "Booting with MILO"
#~ msgstr "採用 MILO 開機"

#~ msgid ""
#~ "MILO contained on the bootstrap media is configured to proceed straight "
#~ "to Linux automatically. Should you wish to intervene, all you need is to "
#~ "press space during MILO countdown."
#~ msgstr ""
#~ "開機媒介上的 MILO 會自動進入 Linux 開機過程。如果您要對此有所控制，只需要"
#~ "在 MILO 倒計時時按下空格鍵。"

#~ msgid ""
#~ "If you want to specify all the bits explicitly (for example, to supply "
#~ "additional parameters), you can use a command like this: "
#~ "<informalexample><screen>\n"
#~ "MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 <!-- arguments --"
#~ ">\n"
#~ "</screen></informalexample> If you are booting from something other than "
#~ "a floppy, substitute <filename>fd0</filename> in the above example with "
#~ "the appropriate device name in Linux notation. The <command>help</"
#~ "command> command would give you a brief MILO command reference."
#~ msgstr ""
#~ "如果您確切想指定所有的位元 (例如，支援附加的參數)，您可以使用像下面的指"
#~ "令：<informalexample><screen>\n"
#~ "MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 <!-- arguments --"
#~ ">\n"
#~ "</screen></informalexample> 如果透過軟碟之外的方法開機，在 Linux 提示號下"
#~ "把上面例子中的 <filename>fd0</filename> 替換成合適的設備名稱。"
#~ "<command>help</command> 指令將列出簡單的 MILO 指令參考。"

#~ msgid "Choosing an Installation Method"
#~ msgstr "選擇安裝方法"

#~ msgid ""
#~ "Some &arch-title; subarchs have the option of booting using either a 2.4."
#~ "x or 2.2.x linux kernel. When such a choice exists, try the 2.4.x linux "
#~ "kernel. The installer should also require less memory when using a 2.4.x "
#~ "linux kernel as 2.2.x support requires a fixed-sized ramdisk and 2.4.x "
#~ "uses tmpfs."
#~ msgstr ""
#~ "一些 &arch-title; 子架構可以選擇使用從 2.4.x 或 2.2.x linux 核心啟動。如果"
#~ "以，請使用 2.4.x linux 核心。使用 2.4.x linux 核心的安裝程式要求較少的記憶"
#~ "體， 因為 2.2.x 支援需要固定大小的 ramdisk 而 2.4.x 使用 tmpfs。"

#, fuzzy
#~ msgid ""
#~ "If you are using a 2.2.x linux kernel, then you need to use the "
#~ "&ramdisksize; kernel parameter."
#~ msgstr "如果您在使用 2.2.x 核心，也許需要設定 &ramdisksize;。"

#~ msgid ""
#~ "Make sure <userinput>root=/dev/ram</userinput> is one of your kernel "
#~ "parameters."
#~ msgstr "確保 <userinput>root=/dev/ram</userinput> 使用您要用的核心。"

#~ msgid ""
#~ "If you're having trouble, check <ulink url=\"&url-m68k-cts-faq;\">cts's "
#~ "&arch-title; debian-installer FAQ</ulink>."
#~ msgstr ""
#~ "如果碰到麻煩，請參閱 <ulink url=\"&url-m68k-cts-faq;\">cts's &arch-title; "
#~ "debian-installer 常見問答集</ulink>。"

#~ msgid "Amiga"
#~ msgstr "Amiga"

#~ msgid ""
#~ "The only method of installation available to amiga is the hard drive (see "
#~ "<xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is "
#~ "not bootable.</emphasis>"
#~ msgstr ""
#~ "amiga 僅支援從硬碟安裝方式 (請參閱 <xref linkend=\"m68k-boot-hd\"/>)。 "
#~ "<emphasis>也就是說光碟機無法開機</emphasis>。"

#, fuzzy
#~ msgid ""
#~ "Amiga does not currently work with bogl, so if you are seeing bogl "
#~ "errors, you need to include the boot parameter <userinput>fb=false</"
#~ "userinput>."
#~ msgstr ""
#~ "目前 Amiga 不能與 bogl 一起工作，如果您看到 bogl 錯誤，您需要使用將下面核"
#~ "心參數 <userinput>debian-installer/framebuffer=false</userinput>。"

#~ msgid "Atari"
#~ msgstr "Atari"

#~ msgid ""
#~ "The installer for atari may be started from either the hard drive (see "
#~ "<xref linkend=\"m68k-boot-hd\"/>) or from floppies (see <xref linkend="
#~ "\"boot-from-floppies\"/>). <emphasis>In other words the cdrom is not "
#~ "bootable.</emphasis>"
#~ msgstr ""
#~ "Atari 安裝程式可以從硬碟 (請參閱 <xref linkend=\"m68k-boot-hd\"/>) 或軟碟 "
#~ "(請參閱 <xref linkend=\"boot-from-floppies\"/>)。<emphasis>也就是說光碟機"
#~ "無法開機</emphasis>。"

#, fuzzy
#~ msgid ""
#~ "Atari does not currently work with bogl, so if you are seeing bogl "
#~ "errors, you need to include the boot parameter <userinput>fb=false</"
#~ "userinput>."
#~ msgstr ""
#~ "目前 Atari 不能與 bogl 一起工作，如果您看到 bogl 錯誤，應該使用下面核心參"
#~ "數 <userinput>debian-installer/framebuffer=false</userinput>。"

#~ msgid "BVME6000"
#~ msgstr "BVME6000"

#~ msgid ""
#~ "The installer for BVME6000 may be started from a cdrom (see <xref linkend="
#~ "\"m68k-boot-cdrom\"/>), floppies (see <xref linkend=\"boot-from-floppies"
#~ "\"/>), or the net (see <xref linkend=\"boot-tftp\"/>)."
#~ msgstr ""
#~ "BVME6000 上安裝程式可以從光碟 (請參閱 <xref linkend=\"m68k-boot-cdrom\"/"
#~ ">)、軟碟 (請參閱 <xref linkend=\"boot-from-floppies\"/>)，或網路 (請參閱 "
#~ "<xref linkend=\"boot-tftp\"/>)。"

#~ msgid "Macintosh"
#~ msgstr "Macintosh"

#~ msgid ""
#~ "The only method of installation available to mac is from the hard drive "
#~ "(see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the "
#~ "cdrom is not bootable.</emphasis> Macs do not have a working 2.4.x kernel."
#~ msgstr ""
#~ "Mac 上啟動安裝的唯一方法是硬碟 (請參閱 <xref linkend=\"m68k-boot-hd\"/"
#~ ">)。 <emphasis>也就是說光碟無法開機</emphasis>。Macs 不能工作在 2.4 核心"
#~ "上。"

#, fuzzy
#~ msgid ""
#~ "If your hardware uses a 53c9x-based scsi bus, then you may need to "
#~ "include the kernel parameter <userinput>mac53c9x=1,0</userinput>. "
#~ "Hardware with two such scsi buses, such as the Quadra 950, will need "
#~ "<userinput>mac53c9x=2,0</userinput> instead. Alternatively, the parameter "
#~ "can be specified as <userinput>mac53c9x=-1,0</userinput> which will leave "
#~ "autodetection on, but which will disable SCSI disconnects. Note that "
#~ "specifying this parameter is only necessary if you have more than one "
#~ "hard disk; otherwise, the system will run faster if you do not specify it."
#~ msgstr ""
#~ "如果您的硬體中包括以 53c9x 為基礎的 scsi 排線，那麼您需要使用下面的核心參"
#~ "數 <userinput>mac53c9x=1</userinput>。裝有兩條這種 scsi 排線的硬體，如 "
#~ "Quadra 950，您需要使用 <userinput>mac53c9x=2</userinput> 參數。"

#~ msgid "MVME147 and MVME16x"
#~ msgstr "MVME147 和 MVME16x"

#~ msgid ""
#~ "The installer for MVME147 and MVME16x may be started from either floppies "
#~ "(see <xref linkend=\"boot-from-floppies\"/>) or the net (see <xref "
#~ "linkend=\"boot-tftp\"/>). <emphasis>In other words the cdrom is not "
#~ "bootable.</emphasis>"
#~ msgstr ""
#~ "MVEM147 和 MVEM16x 可以從軟碟 (請參閱 <xref linkend=\"boot-from-floppies"
#~ "\"/>) 或網路 (請參閱 <xref linkend=\"boot-tftp\"/>)。 <emphasis>也就是說光"
#~ "碟無法開機</emphasis>。"

#~ msgid "Q40/Q60"
#~ msgstr "Q40/Q60"

#~ msgid ""
#~ "The only method of installation available to Q40/Q60 is from the hard "
#~ "drive (see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words "
#~ "the cdrom is not bootable.</emphasis>"
#~ msgstr ""
#~ "Q40/Q60 只支援從硬碟安裝 (請參閱 <xref linkend=\"m68k-boot-hd\"/>)。"
#~ "<emphasis>也就是說光碟機無法啟動。</emphasis>"

#~ msgid "Booting from a Hard Disk"
#~ msgstr "從硬碟開機"

#~ msgid ""
#~ "At least six different ramdisks may be used to boot from the hard drive, "
#~ "three different types each with and without support for a 2.2.x linux "
#~ "kernel (see <ulink url=\"&disturl;/main/installer-&architecture;/current/"
#~ "images/MANIFEST\">MANIFEST</ulink> for details)."
#~ msgstr ""
#~ "至少有六種不同的 ramdisk 可以從硬碟啟動，三個不同的類型分別用於支援或不支"
#~ "援 2.2.x linux 核心 (請參閱 <ulink url=\"&disturl;/main/installer-"
#~ "&architecture;/current/images/MANIFEST\">MANIFEST</ulink> 以瞭解更多細"
#~ "節)。"

#~ msgid ""
#~ "The three different types of ramdisks are <filename>cdrom</filename>, "
#~ "<filename>hd-media</filename>, and <filename>nativehd</filename>. These "
#~ "ramdisks differ only in their source for installation packages. The "
#~ "<filename>cdrom</filename> ramdisk uses a cdrom to get debian-installer "
#~ "packages. The <filename>hd-media</filename> ramdisk uses an iso image "
#~ "file of a cdrom currently residing on a hard disk. Finally, the "
#~ "<filename>nativehd</filename> ramdisk uses the net to install packages."
#~ msgstr ""
#~ "這三種 ramdisk 類型為 <filename>cdrom</filename>、<filename>hd-media</"
#~ "filename> 和 <filename>nativehd</filename>。它們的區別僅在於安裝軟體套件的"
#~ "來源不同。<filename>cdrom</filename> ramdisk 使用光碟取得 debian-"
#~ "installer 軟體套件。<filename>hd-media</filename> ramdisk 使用硬碟上的 "
#~ "iso 映像檔。最後，<filename>nativehd</filename> ramdisk 使用網路安裝軟體套"
#~ "件。"

#~ msgid "Booting from AmigaOS"
#~ msgstr "從 AmigaOS 上開機"

#~ msgid ""
#~ "In the <command>Workbench</command>, start the Linux installation process "
#~ "by double-clicking on the <guiicon>StartInstall</guiicon> icon in the "
#~ "<filename>debian</filename> directory."
#~ msgstr ""
#~ "在 <command>Workbench</command> 下，雙擊 <guiicon>StartInstall</guiicon> "
#~ "圖示來啟動 Linux 安裝過程，它位於 <filename>debian</filename> 目錄中。"

#~ msgid ""
#~ "You may have to press the &enterkey; key twice after the Amiga installer "
#~ "program has output some debugging information into a window. After this, "
#~ "the screen will go grey, there will be a few seconds' delay. Next, a "
#~ "black screen with white text should come up, displaying all kinds of "
#~ "kernel debugging information. These messages may scroll by too fast for "
#~ "you to read, but that's OK. After a couple of seconds, the installation "
#~ "program should start automatically, so you can continue down at <xref "
#~ "linkend=\"d-i-intro\"/>."
#~ msgstr ""
#~ "Amiga 安裝程式會在一個視窗輸出一些除錯訊息，您可以按兩次 &enterkey; 。之後"
#~ "螢幕將變灰，這裡有一些很短的延遲。接下來，以黑底白字將顯示更多的除錯訊息。"
#~ "這些資訊可能捲動的非常快無法看到，但這沒有關係。在一些時間過後，安裝程式應"
#~ "該會自動安裝，因此您可以繼續參閱 <xref linkend=\"d-i-intro\"/>。"

#~ msgid "Booting from Atari TOS"
#~ msgstr "從 Atari TOS 開機"

#~ msgid ""
#~ "At the GEM desktop, start the Linux installation process by double-"
#~ "clicking on the <guiicon>bootstra.prg</guiicon> icon in the "
#~ "<filename>debian</filename> directory and clicking <guibutton>Ok</"
#~ "guibutton> at the program options dialog box."
#~ msgstr ""
#~ "在 GEM 桌面上，可以透過雙擊 <guiicon>bootstra.prg</guiicon> 圖示，它位於 "
#~ "<filename>debian</filename> 目錄下，並且在程式選項對話框內點擊 "
#~ "<guibutton>Ok</guibutton> 來開始啟動安裝過程。"

#~ msgid ""
#~ "You may have to press the &enterkey; key after the Atari bootstrap "
#~ "program has output some debugging information into a window. After this, "
#~ "the screen will go grey, there will be a few seconds' delay. Next, a "
#~ "black screen with white text should come up, displaying all kinds of "
#~ "kernel debugging information. These messages may scroll by too fast for "
#~ "you to read, but that's OK. After a couple of seconds, the installation "
#~ "program should start automatically, so you can continue below at <xref "
#~ "linkend=\"d-i-intro\"/>."
#~ msgstr ""
#~ "當 Atari 安裝程式在視窗輸出一些除錯資訊以後，您可能要按下 &enterkey;。之後"
#~ "螢幕將變灰，這裡有一些很短的延遲。接下來，一個黑屏白字將顯示更多的除錯信"
#~ "息。這些資訊可能捲動的非常快沒法看，但這沒有問題。在一些時間過後，安裝程式"
#~ "應該自動安裝，因此您可以繼續參閱 <xref linkend=\"d-i-intro\"/>。"

#~ msgid ""
#~ "You must retain the original Mac system and boot from it. It is "
#~ "<emphasis>essential</emphasis> that, when booting MacOS in preparation "
#~ "for booting the Penguin linux loader, you hold the <keycap>shift</keycap> "
#~ "key down to prevent extensions from loading. If you don't use MacOS "
#~ "except for loading linux, you can accomplish the same thing by removing "
#~ "all extensions and control panels from the Mac's System Folder. Otherwise "
#~ "extensions may be left running and cause random problems with the running "
#~ "linux kernel."
#~ msgstr ""
#~ "您必須有原來的 Mac 系統，並從它啟動。它是 <emphasis>必要的</emphasis>，當"
#~ "啟動 MacOS 準備啟動 Penguin linux loder 時，按住 <keycap>shift</keycap> 鍵"
#~ "阻止擴充套件繼續動作。如果您除了載入 linux 之外不使用 MacOS，您可以從 Mac "
#~ "的系統目錄下清除所有的擴充套件和控制面板來達到同樣的目的。否則擴充套件會"
#~ "使 linux 核心參數隨機出錯。"

#~ msgid ""
#~ "At the MacOS desktop, start the Linux installation process by double-"
#~ "clicking on the <guiicon>Penguin Prefs</guiicon> icon in the "
#~ "<filename>Penguin</filename> directory. The <command>Penguin</command> "
#~ "booter will start up. Go to the <guimenuitem>Settings</guimenuitem> item "
#~ "in the <guimenu>File</guimenu> menu, click the <guilabel>Kernel</"
#~ "guilabel> tab. Select the kernel (<filename>vmlinuz</filename>) and "
#~ "ramdisk (<filename>initrd.gz</filename>) images in the <filename>install</"
#~ "filename> directory by clicking on the corresponding buttons in the upper "
#~ "right corner, and navigating the file select dialogs to locate the files."
#~ msgstr ""
#~ "在 MacOS 桌面，啟動 Linux 安裝進行需要雙擊 <guiicon>Penguin Prefs</"
#~ "guiicon> 圖示，它位於 <filename>Penguin</filename> 目錄。"
#~ "<command>Penguin</command> 啟動將開始。進入到 <guimenuitem>Settings</"
#~ "guimenuitem> 項，它位於 <guimenu>File</guimenu>選單，點擊 "
#~ "<guilabel>Kernel</guilabel> 選項。選擇核心 (<filename>vmlinuz</filename>) "
#~ "和 ramdisk (<filename>initrd.gz</filename>) 映象，它位於 "
#~ "<filename>install</filename> 目錄，點擊右上角對應的按鈕，並在對話框中選擇"
#~ "檔案。"

#~ msgid ""
#~ "To set the boot parameters in Penguin, choose <guimenu>File</guimenu> -"
#~ "&gt; <guimenuitem>Settings...</guimenuitem>, then switch to the "
#~ "<guilabel>Options</guilabel> tab. Boot parameters may be typed in to the "
#~ "text entry area. If you will always want to use these settings, select "
#~ "<guimenu>File</guimenu> -&gt; <guimenuitem>Save Settings as Default</"
#~ "guimenuitem>."
#~ msgstr ""
#~ "要為 Penguin 設定啟動參數，請選擇 <guimenu>File</guimenu> -&gt; "
#~ "<guimenuitem>Settings...</guimenuitem>，然後切換到 <guilabel>Options</"
#~ "guilabel> 選項卡。啟動參數可以寫到文字區域。如果您要一直採用這些設置，選"
#~ "擇 <guimenu>File</guimenu> -&gt; <guimenuitem>儲存設定為預設</"
#~ "guimenuitem>。"

#~ msgid ""
#~ "Close the <guilabel>Settings</guilabel> dialog, save the settings and "
#~ "start the bootstrap using the <guimenuitem>Boot Now</guimenuitem> item in "
#~ "the <guimenu>File</guimenu> menu."
#~ msgstr ""
#~ "關閉 <guilabel>Settings</guilabel> 對話框，儲存設定然後用位於 "
#~ "<guimenu>File</guimenu> 選單的 <guimenuitem>Boot Now</guimenuitem> 選項開"
#~ "機。"

#~ msgid ""
#~ "The <command>Penguin</command> booter will output some debugging "
#~ "information into a window. After this, the screen will go grey, there "
#~ "will be a few seconds' delay. Next, a black screen with white text should "
#~ "come up, displaying all kinds of kernel debugging information. These "
#~ "messages may scroll by too fast for you to read, but that's OK. After a "
#~ "couple of seconds, the installation program should start automatically, "
#~ "so you can continue below at <xref linkend=\"d-i-intro\"/>."
#~ msgstr ""
#~ "<command>Penguin</command> 啟動將輸出一些除錯資訊到視窗。然後，螢幕變灰，"
#~ "會有數秒延遲。接著，帶有文字的黑底畫面出現，顯示各種核心除錯資訊。這些資訊"
#~ "可能捲動很快無法閱讀，這是正常的。再過一段時間，安裝程式就會自動執行，您可"
#~ "以按照下面步驟繼續 <xref linkend=\"d-i-intro\"/>。"

#~ msgid "Booting from Q40/Q60"
#~ msgstr "從 Q40/Q60 啟動"

#~ msgid "FIXME"
#~ msgstr "FIXME"

#~ msgid ""
#~ "The installation program should start automatically, so you can continue "
#~ "below at <xref linkend=\"d-i-intro\"/>."
#~ msgstr ""
#~ "安裝程式就會自動執行，您可以按下面步驟繼續 <xref linkend=\"d-i-intro\"/>。"

#~ msgid ""
#~ "Currently, the only &arch-title; subarchitecture that supports CD-ROM "
#~ "booting is the BVME6000."
#~ msgstr "目前唯一 &arch-title; 子架構支援光碟開機的是 BVME6000。"

#~ msgid ""
#~ "After booting the VMEbus systems you will be presented with the LILO "
#~ "<prompt>Boot:</prompt> prompt. At that prompt enter one of the following "
#~ "to boot Linux and begin installation proper of the Debian software using "
#~ "vt102 terminal emulation:"
#~ msgstr ""
#~ "在起動 VMEbus 系統後您應該看到 LILO <prompt>Boot:</prompt> 提示符號。在提"
#~ "示符號下輸入以下一種方法來啟動 Linux，並開始在一個 vt102 模擬終端下面安裝"
#~ "普通的 Debian 軟體。"

#~ msgid "type <screen>i6000 &enterkey;</screen> to install a BVME4000/6000"
#~ msgstr "輸入 <screen>i6000 &enterkey;</screen> 來安裝 BVME4000/6000"

#~ msgid "type <screen>i162 &enterkey;</screen> to install an MVME162"
#~ msgstr "輸入 <screen>i162 &enterkey;</screen> 來安裝 MVME162"

#~ msgid "type <screen>i167 &enterkey;</screen> to install an MVME166/167"
#~ msgstr "輸入 <screen>i167 &enterkey;</screen> 來安裝 MVME166/167"

#~ msgid ""
#~ "You may additionally append the string <screen>TERM=vt100</screen> to use "
#~ "vt100 terminal emulation, e.g., <screen>i6000 TERM=vt100 &enterkey;</"
#~ "screen>."
#~ msgstr ""
#~ "您也可以附加一個字串 <screen>TERM=vt100</screen> 來使用 vt100 終端模擬。比"
#~ "如,<screen>i6000 TERM=vt100 &enterkey;</screen>。"

#~ msgid ""
#~ "For most &arch-title; architectures, booting from a local filesystem is "
#~ "the recommended method."
#~ msgstr ""
#~ "對於大多數 m68k 架構來說，推薦方法是從一個本地檔案系統開機安裝程式。"

#~ msgid ""
#~ "Booting from the boot floppy is supported only for Atari and VME (with a "
#~ "SCSI floppy drive on VME) at this time."
#~ msgstr ""
#~ "從軟碟開機的方法目前只支援 Atari 以及 VME (VME 有一個 SCSI 軟碟機)。"

#~ msgid "Such problems have been reported on the Amiga 1200 and SE/30."
#~ msgstr "在 Amiga 1200 and SE/30 上面也有報告指出這方面的問題。"

# index.docbook:1919, index.docbook:1968
#, fuzzy
#~ msgid "Broadcom BCM91250A and BCM91480B TFTP Booting"
#~ msgstr "Broadcom BCM91250A TFTP 的啟動"

#, fuzzy
#~ msgid ""
#~ "On the Broadcom BCM91250A and BCM91480B evaluation boards, you have to "
#~ "load the SiByl boot loader via TFTP which will then load and start the "
#~ "Debian installer. In most cases, you will first obtain an IP address via "
#~ "DHCP but it is also possible to configure a static address. In order to "
#~ "use DHCP, you can enter the following command on the CFE prompt: "
#~ "<informalexample><screen>\n"
#~ "ifconfig eth0 -auto\n"
#~ "</screen></informalexample> Once you have obtained an IP address, you can "
#~ "load SiByl with the following command: <informalexample><screen>\n"
#~ "boot 192.168.1.1:/boot/sibyl\n"
#~ "</screen></informalexample> You need to substitute the IP address listed "
#~ "in this example with either the name or the IP address of your TFTP "
#~ "server. Once you issue this command, the installer will be loaded "
#~ "automatically."
#~ msgstr ""
#~ "在 Broadcom BCM91250A 試用主機板上，您不得不透過 TFTP 加載 SiByl 開機程"
#~ "式，它接著將載入和啟動 Debian 安裝程式。大多數情況下，您透過 DHCP 取得 IP "
#~ "位址，當然也可以指定靜態位址。要使用 DHCP，您可以在下面 CFE 提示符號下輸入"
#~ "指令： <informalexample><screen>\n"
#~ "ifconfig eth0 -auto\n"
#~ "</screen></informalexample> 一旦得到 IP 位址，就可以使用下面指令載入 "
#~ "SiByl： <informalexample><screen>\n"
#~ "boot 192.168.1.1:/boot/sibyl\n"
#~ "</screen></informalexample> 您必須以網域名稱或從 TFTP 伺服器上取得的 IP 位"
#~ "址替換上例中的 IP 位址。完成之後，安裝程式就會自動載入。"

#~ msgid ""
#~ "You cannot pass any boot parameters directly from the CFE prompt. "
#~ "Instead, you have to edit the <filename>/boot/sibyl.conf</filename> file "
#~ "on the TFTP server and add your parameters to the "
#~ "<replaceable>extra_args</replaceable> variable."
#~ msgstr ""
#~ "您不能從 CFE 提示符號直接傳遞啟動參數。而是編輯 TFTP 伺服器上的 "
#~ "<filename>/boot/sibyl.conf</filename> 文件並添加參數到 "
#~ "<replaceable>extra_args</replaceable> 變數。"

#, fuzzy
#~ msgid "Booting from TFTP on Netwinder"
#~ msgstr "從 NetWinder 上的 TFTP 開機"

#, fuzzy
#~ msgid ""
#~ "You need NeTTrom 2.2.1 or later to boot the installation system, and "
#~ "version 2.3.3 is recommended. Unfortunately, firmware files are currently "
#~ "not available for download because of license issues. If this situation "
#~ "changes, you may find new images at <ulink url=\"http//www.netwinder.org/"
#~ "\"></ulink>."
#~ msgstr ""
#~ "您需要 NeTTrom 2.2.1 或者較高的版本來啟動安裝系統。建議使用 NeTTrom "
#~ "2.3.3：請從下面網址取得 <ulink url=\"ftp://ftp.netwinder.org/pub/"
#~ "netwinder/firmware/\"></ulink>:"

#~ msgid "Booting from TFTP on CATS"
#~ msgstr "透過 CATS 上的 TFTP 開機"

#~ msgid ""
#~ "On CATS machines, use <command>boot de0:</command> or similar at the "
#~ "Cyclone prompt."
#~ msgstr ""
#~ "在 CATS 機器上，可以使用指令 <command>boot de0:</command> 或者在 Cyclone "
#~ "開機提示號輸入類似的指令。"

#~ msgid ""
#~ "To boot a CD-ROM from the Cyclone console prompt, use the command "
#~ "<command>boot cd0:cats.bin</command>"
#~ msgstr ""
#~ "如果需要在 Cyclone 控制台提示符號下從光碟下開機，請使用指令 <command>boot "
#~ "cd0:cats.bin</command>"

#~ msgid "Booting CHRP from OpenFirmware"
#~ msgstr "從 OpenFirmware 開機 CHRP"

#~ msgid "Not yet written."
#~ msgstr "還沒有完成"

#, fuzzy
#~ msgid ""
#~ "Information on available boot methods and on boot parameters which might "
#~ "be useful can be found by pressing <keycap>F2</keycap> through "
#~ "<keycap>F8</keycap>. If you add any parameters to the boot command line, "
#~ "be sure to type the boot method (the default is <userinput>install</"
#~ "userinput>) and a space before the first parameter (e.g., "
#~ "<userinput>install fb=false</userinput>)."
#~ msgstr ""
#~ "有關開機參數的資訊可能會很有用。它可以透過 <keycap>F3</keycap> 到 <phrase "
#~ "condition=\"sarge\"><keycap>F7</keycap></phrase><phrase condition=\"etch"
#~ "\"><keycap>F8</keycap></phrase> 來得知。如果您加入任何參數至開機命令列，請"
#~ "確保在開機方法 (預設是 <userinput>linux</userinput>) 和第一個參數之間有一"
#~ "個空格 (例如 <userinput>linux floppy=thinkpad</userinput>)。如果您只鍵入 "
#~ "&enterkey;，這等同於輸入 <userinput>linux</userinput> 不附帶任何參數。"

#, fuzzy
#~ msgid ""
#~ "If you are installing the system via a remote management device that "
#~ "provides a text interface to the VGA console, you may not be able to see "
#~ "the initial graphical splash screen upon booting the installer; you may "
#~ "even not see the boot prompt. Examples of these devices include the text "
#~ "console of Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's "
#~ "<quote>Integrated Remote Assistant</quote> (IRA). You can blindly press "
#~ "F1<footnote> <para> In some cases these devices will require special "
#~ "escape sequences to enact this keypress, for example the IRA uses "
#~ "<keycombo> <keycap>Ctrl</keycap> <keycap>F</keycap> </keycombo>,&nbsp;"
#~ "<keycap>1</keycap>. </para> </footnote> to bypass this screen and view "
#~ "the help text. Once you are past the splash screen and at the help text "
#~ "your keystrokes will be echoed at the prompt as expected. To prevent the "
#~ "installer from using the framebuffer for the rest of the installation, "
#~ "you will also want to add <userinput>fb=false</userinput> to the boot "
#~ "prompt, as described in the help text."
#~ msgstr ""
#~ "如果您透過提供 VGA 文字介面的遠端遙控設備來安裝系統，您可能無法看到安裝程"
#~ "式一開始顯示的版權圖形；您甚至可能看不到啟動提示號。這些設備例如康柏的 "
#~ "<quote>integrated Lights Out</quote> (iLO) 和 <quote>Integrated Remote "
#~ "Assistant</quote> (IRA) 的文字控制台。您可以直接按下 F1<footnote> <para> "
#~ "在某些狀況下，這些設備需要特殊的跳脫字串來啟用這個按鍵，例如 IRA 使用 "
#~ "<keycombo> <keycap>Ctrl</keycap> <keycap>F</keycap> </keycombo>,&nbsp;"
#~ "<keycap>1</keycap>. </para> </footnote> 來跳過這個畫面，並且顯示說明畫面。"
#~ "只要您離開了圖標畫面並進入了說明文字畫面，您的按下的按鍵就會顯示在螢幕上。"
#~ "為了防止安裝程式在之後的安裝步驟中使用 framebuffer，您可能會加入 "
#~ "<userinput>debian-installer/framebuffer=false</userinput> 到啟動參數中，如"
#~ "同說明文字中描述的。"

#, fuzzy
#~ msgid ""
#~ "To boot from floppy on a Sparc, use <informalexample><screen>\n"
#~ "Stop-A -&gt; OpenBoot: \"boot floppy\"\n"
#~ "</screen></informalexample> Be warned that the newer Sun4u (ultra) "
#~ "architecture does not support floppy booting. A typical error message is "
#~ "<computeroutput>Bad magic number in disk label - Can't open disk label "
#~ "package</computeroutput>."
#~ msgstr ""
#~ "在 SPARC 機器上用軟碟機開機，請使用 <informalexample><screen>\n"
#~ "Stop-A -&gt; OpenBoot: \"boot floppy\"\n"
#~ "</screen></informalexample> 注意較新的 Sun4u (ultra) 結構不支援軟碟機開"
#~ "機，一個標準的錯誤資訊是 <computeroutput>Bad magic number in disk label - "
#~ "Can't open disk label package</computeroutput>。甚至，一些 Sun4c 型號 (例"
#~ "如 IPX) 不支援磁碟上找到的壓縮映像，所以這些都不被支援。"

#~ msgid ""
#~ "Several Sparcs (e.g. Ultra 10) have an OBP bug that prevents them from "
#~ "booting (instead of not supporting booting at all). The appropriate OBP "
#~ "update can be downloaded as product ID 106121 from <ulink url=\"http://"
#~ "sunsolve.sun.com\"></ulink>."
#~ msgstr ""
#~ "不少 Sparcs (例如 Ultra 10) 有一個 OBP 缺陷。它阻止這些機器開機 (從而完全"
#~ "不支持開機)。合適的 OBP 更新可以從下面連接的 ID 106121 中取得，<ulink url="
#~ "\"http://sunsolve.sun.com\"></ulink>。"

#~ msgid ""
#~ "If you are booting from the floppy, and you see messages such as "
#~ "<informalexample><screen>\n"
#~ "Fatal error: Cannot read partition\n"
#~ "Illegal or malformed device name\n"
#~ "</screen></informalexample> then it is possible that floppy booting is "
#~ "simply not supported on your machine."
#~ msgstr ""
#~ "如果您正在從軟碟開機，並且看到如下資訊 <informalexample><screen>\n"
#~ "Fatal error: Cannot read partition\n"
#~ "Illegal or malformed device name\n"
#~ "</screen></informalexample> 那麼您的機器很可能不支援軟碟開機。"

#~ msgid "debian-installer/probe/usb"
#~ msgstr "debian-installer/probe/usb"

#~ msgid ""
#~ "Set to <userinput>false</userinput> to prevent probing for USB on boot, "
#~ "if that causes problems."
#~ msgstr ""
#~ "設定成 <userinput>false</userinput> 可以阻止在開機的時候禁止 USB 檢查來杜"
#~ "絕其所引起的問題。"

#~ msgid ""
#~ "Macs require the <command>Penguin</command> bootloader. If you do not "
#~ "have the tools to handle a <command>Stuffit</command> archive, &penguin19."
#~ "hfs; is an hfs disk image with <command>Penguin</command> unpacked. <xref "
#~ "linkend=\"create-floppy\"/> describes how to copy this image to a floppy."
#~ msgstr ""
#~ "Mac 需要 <command>Penguin</command> 這個 boot-loader。如果您沒有這個工具處"
#~ "理 <command>Stuffit</command> 檔案，&penguin19.hfs; 是一個 hfs 磁碟映像，"
#~ "含有 <command>Penguin</command> 壓縮檔。<xref linkend=\"create-floppy\"/> "
#~ "說明如何將該映像複製到軟碟。"

#~ msgid ""
#~ "Type <informalexample><screen>\n"
#~ "&gt;&gt;&gt; boot xxxx -flags 0\n"
#~ "</screen></informalexample> where <replaceable>xxxx</replaceable> is your "
#~ "CD-ROM drive in SRM notation."
#~ msgstr ""
#~ "輸入 <informalexample><screen>\n"
#~ "&gt;&gt;&gt; boot xxxx -flags 0\n"
#~ "</screen></informalexample> 上一行 <replaceable>xxxx</replaceable> 是光碟"
#~ "機在 SRM 裡的提示號。"

#~ msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;."
#~ msgstr "如果您在使用 2.2.x 核心，也許需要設定 &ramdisksize;。"

#~ msgid ""
#~ "If you are booting with your own kernel instead of the one supplied with "
#~ "the installer, be sure that <userinput>CONFIG_DEVFS</userinput> is set in "
#~ "your kernel. The installer requires <userinput>CONFIG_DEVFS</userinput>."
#~ msgstr ""
#~ "如果開機時使用的是您自己的核心，而不是安裝程式提供的核心，請確定您的核心編"
#~ "有 <userinput>CONFIG_DEVFS</userinput> 參數。安裝程式需要 "
#~ "<userinput>CONFIG_DEVFS</userinput>。"

#~ msgid "Bug Reporter"
#~ msgstr "Bug Reporter"

#~ msgid ""
#~ "Proceed to the next chapter to continue the installation where you will "
#~ "set up the language locale, network, and the disk partitions."
#~ msgstr "下一章將繼續安裝過程，在那裡您將設定語言區域，網路以及磁碟分割區。"

#~ msgid ""
#~ "In case your computer doesn't support booting from USB memory devices, "
#~ "you can still use a single floppy to do the initial boot and then switch "
#~ "to USB. Boot your system as described in <xref linkend=\"floppy-boot\"/>; "
#~ "the kernel on the boot floppy should detect your USB stick automatically. "
#~ "When it asks for the root floppy, simply press &enterkey;. You should see "
#~ "&d-i; starting."
#~ msgstr ""
#~ "如果您的電腦不支援從 USB 隨身碟設備開機，您也可以採用單張軟碟來開機並且切"
#~ "換至 USB。根據 <xref linkend=\"floppy-boot\"/>，開機軟碟中的核心應該能夠自"
#~ "動偵測您的 USB 隨身碟。當它要求根軟碟的時候，只需簡單敲入 &enterkey;。您應"
#~ "該看到 &d-i; 開始執行。"

#~ msgid ""
#~ "NetWinders have two network interfaces: The 10Mbps NE2000-compatible card "
#~ "is <filename>eth0</filename> and the 100Mbps Tulip card is "
#~ "<filename>eth1</filename>."
#~ msgstr ""
#~ "NetWinders 具有兩個網路界面：10Mbps NE2000 相容的網卡作為 <filename>eth0</"
#~ "filename> 以及 100Mbps Tulip 網卡作為 <filename>eth1</filename>。"

#~ msgid "nettrom-2.3-3.armv4l.rpm"
#~ msgstr "nettrom-2.3-3.armv4l.rpm"

#~ msgid "nettrom-2.3.3.bin"
#~ msgstr "nettrom-2.3.3.bin"

#~ msgid "nettrom-2.3.3.bin.md5sum"
#~ msgstr "nettrom-2.3.3.bin.md5sum"

#~ msgid ""
#~ "After rebooting and interrupting the boot process during the countdown, "
#~ "you must first configure the network either with a static address: "
#~ "<informalexample><screen>\n"
#~ "    NeTTrom command-&gt; setenv eth0_ip 192.168.0.10/24\n"
#~ "</screen></informalexample> where 24 is the number of set bits in the "
#~ "netmask, or a dynamic address: <informalexample><screen>\n"
#~ "    NeTTrom command-&gt; boot diskless\n"
#~ "</screen></informalexample> You may also need to configure the "
#~ "<userinput>route1</userinput> settings if the TFTP server is not on the "
#~ "local subnet. The rest of the config is pretty standard (the save-all "
#~ "step is optional): <informalexample><screen>\n"
#~ "    NeTTrom command-&gt; setenv kerntftpserver 192.168.0.1\n"
#~ "    NeTTrom command-&gt; setenv kerntftpfile boot.img\n"
#~ "    NeTTrom command-&gt; save-all\n"
#~ "    NeTTrom command-&gt; setenv netconfig_eth0 flash\n"
#~ "    NeTTrom command-&gt; setenv kernconfig tftp\n"
#~ "    NeTTrom command-&gt; setenv rootdev /dev/ram\n"
#~ "    NeTTrom command-&gt; setenv cmdappend root=/dev/ram\n"
#~ "</screen></informalexample> Only the last four of these interfere with "
#~ "normal disk booting, so it is safe to issue <command>save-all</command> "
#~ "right before them, which will store the network settings in case you need "
#~ "to boot from the network again. If you want to use the serial console to "
#~ "install your NetWinder, you also need the following setting: "
#~ "<informalexample><screen>\n"
#~ "    NeTTrom command-&gt; setenv cmdappend root=/dev/ram "
#~ "console=ttyS0,115200\n"
#~ "</screen></informalexample> Use the <command>printenv</command> command "
#~ "to review your environment settings. Finally, if your <envar>cmdappend</"
#~ "envar> NeTTrom variable has the <option>noinitrd</option> option, you "
#~ "must remove it so the downloaded kernel can boot with its attached "
#~ "ramdisk."
#~ msgstr ""
#~ "在重新開機並在倒數計時的時候中斷開機後，您必須設定靜態網路: "
#~ "<informalexample><screen>\n"
#~ "    NeTTrom command-&gt; setenv eth0_ip 192.168.0.10/24\n"
#~ "</screen></informalexample> 這裡 24 是網路遮罩，您也可以設定一個動態位"
#~ "址： <informalexample><screen>\n"
#~ "    NeTTrom command-&gt; boot diskless\n"
#~ "</screen></informalexample> 如果 TFTP 伺服器並不在子網域內， 您也可能需要"
#~ "設定 <userinput>route1</userinput>。其他的設定方法是非常標準的 (save-all "
#~ "這步是可選的)： <informalexample><screen>\n"
#~ "    NeTTrom command-&gt; setenv kerntftpserver 192.168.0.1\n"
#~ "    NeTTrom command-&gt; setenv kerntftpfile tftpboot.img\n"
#~ "    NeTTrom command-&gt; save-all\n"
#~ "    NeTTrom command-&gt; setenv netconfig_eth0 flash\n"
#~ "    NeTTrom command-&gt; setenv kernconfig tftp\n"
#~ "    NeTTrom command-&gt; setenv rootdev /dev/ram\n"
#~ "    NeTTrom command-&gt; setenv cmdappend root=/dev/ram\n"
#~ "</screen></informalexample> 只有最後四項會影響正常的磁碟開機，所以在此之前"
#~ "選擇 <command>save-all</command> 將儲存網路設定以免您需要再一次開機。如果"
#~ "您想用序列埠控制台安裝 netWinder，您需要如下設置:"
#~ "<informalexample><screen>\n"
#~ "    NeTTrom command-&gt; setenv cmdappend root=/dev/ram\n"
#~ "console=ttyS0,115200\n"
#~ "</screen></informalexample> 使用 <command>printenv</command> 可以檢查您的"
#~ "環境設定。最後，如果您的 <envar>cmdappend</envar> NeTTrom 參數具有 "
#~ "<option>noinitrd</option> 選項，您必須刪除它以確保下載的核心可以用其附帶的"
#~ "記憶體虛擬磁碟開機。"

#, fuzzy
#~ msgid ""
#~ "Also, if you are using a 2.2.x linux kernel, then you must make sure you "
#~ "are using a ramdisk built to accommodate it, see the <ulink url="
#~ "\"&disturl;/main/installer-&architecture;/current/images/MANIFEST"
#~ "\">MANIFEST</ulink>. In general, this means you need to use the initrd22."
#~ "gz ramdisk from the respective directory."
#~ msgstr ""
#~ "如果您使用 2.2.x linux 核心，那麼必須確保 ramdisk 滿足要求，請參閱 <ulink "
#~ "url=\"&disturl;/main/installer-&architecture;/current/images/MANIFEST"
#~ "\">MANIFEST</ulink>。您還需要使用 &ramdisksize; 核心參數。通常，這意味著您"
#~ "需要使用相同目錄下的 initrd22.gz ramdisk。"

#~ msgid ""
#~ "Passing this boot parameter will cause the boot to be more verbosely "
#~ "logged."
#~ msgstr "傳遞此參數將記錄最複雜的開機資訊。"

#~ msgid "i386 Boot Parameters"
#~ msgstr "i386 的開機參數"

#~ msgid ""
#~ "When the installer boots, you will be presented with the boot prompt, "
#~ "<prompt>boot:</prompt>. You can do two things at the <prompt>boot:</"
#~ "prompt> prompt. You can press the function keys <keycap>F1</keycap> "
#~ "through <keycap>F10</keycap> to view a few pages of helpful information, "
#~ "or you can press <keycap>Enter</keycap> to boot the system."
#~ msgstr ""
#~ "當安裝程式啟動後，您將看到一個 boot 提示符號 <prompt>boot:</prompt>。可以"
#~ "在<prompt>boot:</prompt> 開機提示號處做兩件事情。您可以按功能鍵 "
#~ "<keycap>F1</keycap> 到 <keycap>F10</keycap> 來查看一整頁的說明資訊，或者按"
#~ "下 <keycap>Enter</keycap> 來啟動系統。"