# 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: 2017-04-19 20:02+0000\n" "PO-Revision-Date: 2015-03-21 18:13+0100\n" "Last-Translator: Ji YongGang \n" "Language-Team: debian-chinese-gb \n" "Language: zh_CN\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 before 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 ." msgstr "关于如何引导图形安装程序,请参阅 。" #. Tag: title #: boot-installer.xml:39 #, fuzzy, no-c-format #| msgid "Booting from Firmware" msgid "Boot image formats" msgstr "从固件引导" #. 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 (vmlinuz) in " "conjunction with standard Linux initial ramdisks (initrd.gz) " "or b) uImage-format kernels (uImage) in conjunction with " "corresponding initial ramdisks (uInitrd)." 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, dtb) 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 (), and the " "installer SD-card images () use " "the (platform-specific) default console that is defined by U-Boot in the " "console 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 " "console 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 Booting Linux 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 e for Edit Kernel " "command-line at the GRUB menu, and change " "--- quiet to " "console=<device>,<speed> e.g. console=ttyAMA0,115200n8. When finished hit Control x 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 &url-juno-firmware; 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 console=ttyAMA0,115200n8 (as described in ). " "Control x 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 (). 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 Hit any key to stop autoboot: " "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 #, no-c-format 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:831 boot-installer.xml:1467 #: boot-installer.xml:1597 boot-installer.xml:1918 boot-installer.xml:2066 #, 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:837 boot-installer.xml:1473 #: boot-installer.xml:1603 boot-installer.xml:1924 boot-installer.xml:2072 #, 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:842 boot-installer.xml:1478 #: boot-installer.xml:1608 boot-installer.xml:1929 boot-installer.xml:2077 #, fuzzy, no-c-format #| msgid "" #| "The installation method to support network booting is described in ." msgid "" "The server-side setup to support network booting is described in ." msgstr "支持的网络引导安装方法在 。" #. 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 \n" "setenv autoload no\n" "dhcp\n" " or manually by setting several environment " "variables \n" "setenv ipaddr <ip address of the client>\n" "setenv netmask <netmask>\n" "setenv serverip <ip address of the tftp server>\n" "setenv dnsip <ip address of the nameserver>\n" "setenv gatewayip <ip address of the default gateway>\n" " 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 \n" "printenv kernel_addr_r ramdisk_addr_r fdt_addr_r\n" " 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 sun4i or the Allwinner A20, architecture name " "sun7i), 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} <filename of the kernel image>\n" "tftpboot ${fdt_addr_r} <filename of the dtb>\n" "tftpboot ${ramdisk_addr_r} <filename of the initial ramdisk image>" 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 bootargs " "environment variable as commandline to the kernel, so any parameters for the " "kernel and the installer - such as the console device (see ) or preseeding options (see and ) - can be set with a command " "like \n" "setenv bootargs console=ttyS0,115200 rootwait panic=10\n" " The exact command to execute the previously " "loaded code depends on the image format used. With uImage/uInitrd, the " "command is \n" "bootm ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}\n" " 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 "从 U 盘引导" #. Tag: para #: boot-installer.xml:293 boot-installer.xml:552 #, fuzzy, no-c-format #| msgid "" #| "Let's assume you have prepared everything from and . Now 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 the boot: 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 and , 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 "" "假设您已经准备好了从 的所有步骤。现在只需插入 U 盘到一个空的 USB 插槽并重启。" "除非您使用了灵活方式创建 U 盘并不激活,系统应该引导,并看到一个 boot:" " 提示符。此时您可以输入一些引导选项,也可以直接按 &enterkey;。" # index.docbook:700, index.docbook:2176 #. Tag: title #: boot-installer.xml:309 #, fuzzy, no-c-format #| msgid "Booting from USB memory stick" msgid "Booting from a USB stick in U-Boot" msgstr "从 U 盘引导" #. Tag: para #: boot-installer.xml:310 #, 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:317 #, 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:326 #, no-c-format msgid "" "To build a bootable USB stick for installing &debian;, unpack the hd-media " "tarball (see ) 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:336 #, 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 " "run bootcmd_usb0 command." msgstr "" #. Tag: para #: boot-installer.xml:346 #, 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 console=ttyS0,115200), while on other " "platforms the console variable contains only the device (as in " "console=ttyS0). 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 run bootcmd_usb0 command." msgstr "" #. Tag: title #: boot-installer.xml:367 #, no-c-format msgid "Using pre-built SD-card images with the installer" msgstr "" #. Tag: para #: boot-installer.xml:368 #, 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 " "firmware.<system-type>.img.gz, and a system-independent " "part named partition.img.gz." msgstr "" #. Tag: para #: boot-installer.xml:379 #, no-c-format msgid "" "To create a complete image from the two parts on Linux systems, you can use " "zcat as follows: zcat firmware.<system-type>." "img.gz partition.img.gz > complete_image.img " "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 copy /b " "firmware.<system-type>.img + partition.img complete_image.img in a Windows CMD.exe window." msgstr "" #. Tag: para #: boot-installer.xml:393 #, no-c-format msgid "" "Write the resulting image onto an SD card, e.g. by running the following " "command on a Linux system: cat complete_image.img " "> /dev/SD_CARD_DEVICE 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:405 #, no-c-format msgid "" "When you come to the partitioning step in the installer (see ), 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 )." msgstr "" # index.docbook:700, index.docbook:2176 #. Tag: title #: boot-installer.xml:546 #, no-c-format msgid "Booting from USB Memory Stick" msgstr "从 U 盘引导" # index.docbook:578, index.docbook:951, index.docbook:1764, index.docbook:2018, index.docbook:2372 #. Tag: title #: boot-installer.xml:567 boot-installer.xml:1081 boot-installer.xml:1682 #: boot-installer.xml:2100 #, no-c-format msgid "Booting from a CD-ROM" msgstr "从 CD-ROM 启动" # index.docbook:531, index.docbook:584, index.docbook:957, index.docbook:1776, index.docbook:2024, index.docbook:2378 #. Tag: para #: boot-installer.xml:573 boot-installer.xml:1087 boot-installer.xml:1688 #: boot-installer.xml:2106 #, no-c-format msgid "" "If you have a CD set, and if your machine supports booting directly off the " "CD, great! Simply configure your system for booting " "off a CD as described in , " "insert your CD, reboot, and proceed to the next chapter." msgstr "" "如果您有此套件,并且如果您的机器支持直接 CD 引导,太棒了!只需要配置您的系统可以用 CD 启动,参见 , 插入您的 CD,重启,然后继续下一章。" # index.docbook:542, index.docbook:595, index.docbook:968, index.docbook:1787, index.docbook:2035, index.docbook:2389 #. Tag: para #: boot-installer.xml:583 boot-installer.xml:1097 boot-installer.xml:1698 #: boot-installer.xml:2116 #, 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 "" "注意某些特定的 CD 驱动器需要一些特殊的驱动程序,因此他们可能在安装的早期不能" "被访问。如果从 CD 引导的标准方法不能用于您的硬件,阅读本章中关于其他种类的内" "核以及安装方法,它们有可能能解决问题。" # index.docbook:550, index.docbook:603, index.docbook:976, index.docbook:1795, index.docbook:2043, index.docbook:2397 #. Tag: para #: boot-installer.xml:591 boot-installer.xml:1105 boot-installer.xml:1706 #: boot-installer.xml:2124 #, 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 "" "即便您不能从 CD-ROM 引导,依然可以安装 CD-ROM 上面的 &debian; 系统组件和所有" "软件包。这只要使用不同的媒介引导,比如软盘。当安装操作系统、基础系统和任意附" "加的软件包时,只需将安装系统指向 CD-ROM 驱动器即可。" # index.docbook:558, index.docbook:611, index.docbook:984, index.docbook:1803, index.docbook:2051, index.docbook:2405 #. Tag: para #: boot-installer.xml:599 boot-installer.xml:1113 boot-installer.xml:1714 #: boot-installer.xml:2132 #, no-c-format msgid "" "If you have problems booting, see ." msgstr "" "如果您遇到引导方面的问题,请参见 。" #. Tag: title #: boot-installer.xml:609 #, no-c-format msgid "Booting from Windows" msgstr "从 Windows 引导" #. Tag: para #: boot-installer.xml:610 #, no-c-format msgid "To start the installer from Windows, you can either" msgstr "从 Windows 下启动安装程序,您可以" #. Tag: para #: boot-installer.xml:615 #, no-c-format msgid "" "obtain CD-ROM/DVD-ROM or USB memory " "stick installation media as described in respective or" msgstr "" "从 以" "及 获取 CD-ROM/DVD-ROM 或 U 盘 安装介质,或" #. Tag: para #: boot-installer.xml:623 #, no-c-format msgid "" "download a standalone Windows executable, which is available as tools/win32-" "loader/stable/win32-loader.exe on the &debian; mirrors." msgstr "" "下载独立的 Windows 可执行程序,它位于 &debian; 镜像网站 tools/win32-loader/" "stable/win32-loader.exe." #. Tag: para #: boot-installer.xml:631 #, 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 setup.exe." msgstr "" "假如您使用的是安装 CD 或 DVD,在插入盘片的时候,预安装程序会自动加载。如果 " "Windows 没有自动运行,或者您使用的是 USB 存储卡,您可以访问该设备手动执行 " "setup.exe 程序。" #. Tag: para #: boot-installer.xml:639 #, 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 "" "程序运行后,会先询问一些预备问题,接着系统就准备重启进入 &debian-gnu; 安装程" "序。" #. Tag: title #: boot-installer.xml:649 #, fuzzy, no-c-format #| msgid "Booting from DOS" msgid "Booting from DOS using loadlin" msgstr "从 DOS 引导" #. Tag: para #: boot-installer.xml:650 #, no-c-format msgid "" "Boot into DOS (not Windows). To do this, you can for instance boot from a " "recovery or diagnostic disk." msgstr "要启动到 DOS (非 Windows),您可以从一个用于恢复或诊断的磁盘引导。" #. Tag: para #: boot-installer.xml:655 #, no-c-format msgid "" "If you can access the installation CD, change the current drive to the CD-" "ROM drive, e.g. \n" "d:\n" " else make sure you have first prepared your hard " "disk as explained in , and change the " "current drive to it if needed." msgstr "" "如果您可以使用安装 CD, 请切换到 CD-ROM 驱动器,例如. " "\n" "d:\n" " ,或者确认您已依照 指引准备好了硬盘, 然后切换到该磁盘。" #. Tag: para #: boot-installer.xml:665 #, no-c-format msgid "" "Enter the subdirectory for the flavor you chose, e.g., " "\n" "cd \\&x86-install-dir;\n" " If you prefer using the graphical installer, " "enter the gtk sub-directory. \n" "cd gtk\n" " Next, execute install.bat. " "The kernel will load and launch the installer system." msgstr "" "进入您选择的 flavor 子目录,如, \n" "cd \\&x86-install-dir;\n" " 如果您希望使用图形安装程序,请进入 " "gtk 子目录。\n" "cd gtk\n" " 然后,执行 install.bat。内核将" "会加载并运行安装程序。" #. Tag: title #: boot-installer.xml:683 #, no-c-format msgid "" "Booting from Linux using LILO or GRUB" msgstr "引导 Linux 使用 LILOGRUB" #. Tag: para #: boot-installer.xml:686 #, no-c-format msgid "" "To boot the installer from hard disk, you must first download and place the " "needed files as described in ." msgstr "" "为了从硬盘引导安装程序,您首先必须按照要求下载并且放置所需的文件,请参见 " "。" #. Tag: para #: boot-installer.xml:691 #, 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 netboot/" "debian-installer/&architecture;/initrd.gz file and its " "corresponding kernel netboot/debian-installer/&architecture;/" "linux. This will allow you to repartition the hard disk from " "which you boot the installer, although you should do so with care." msgstr "" "如果您只愿意使用硬盘引导,然后从网络下载其他文件,需要下载 netboot/" "debian-installer/&architecture;/initrd.gz 文件及其对应的内核 " "netboot/debian-installer/&architecture;/linux。这将允许" "您重新分区用于引导的硬盘,需要小心操作。" #. Tag: para #: boot-installer.xml:701 #, 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 hd-media/initrd." "gz file and its kernel, as well as copy a CD (or DVD) iso to the " "drive (make sure the file is named ending in .iso). The " "installer can then boot from the drive and install from the CD/DVD image, " "without needing the network." msgstr "" "另一种方法,可以在安装时保持原硬盘的分区不变,您需要下载 hd-media/" "initrd.gz 文件以及对应的内核,还需要一个 CD(或者 DVD) iso 文件的副" "本放在硬盘上(确认文件名是以 .iso 结尾的)。这样安装程序就可" "以从硬盘引导,并从 CD/DVD 映像文件上安装,而不使用网络。" #. Tag: para #: boot-installer.xml:710 #, no-c-format msgid "" "For LILO, you will need to configure two essential things " "in /etc/lilo.conf: to " "load the initrd.gz installer at boot time; have the vmlinuz kernel use " "a RAM disk as its root partition. Here is " "a /etc/lilo.conf example:" msgstr "" "如果采用 LILO,您需要在 /etc/lilo.conf 中配置两件最基本的事情: 在引导时装" "入 initrd.gz 安装程序; " "vmlinuz 内核使用一个内存虚拟磁盘作为" "它的根分区。 这里是一个 /etc/" "lilo.conf 的例子:" #. Tag: screen #: boot-installer.xml:731 #, 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:731 #, no-c-format msgid "" "For more details, refer to the initrd 4 and " "lilo.conf 5 man pages. Now run lilo and " "reboot." msgstr "" "欲获知更多细节,请参阅 initrd " "4lilo." "conf 5 man 手册。现在运" "行 lilo 并且重新启动。" #. Tag: para #: boot-installer.xml:740 #, no-c-format msgid "" "The procedure for GRUB1 is quite similar. Locate your " "menu.lst in the /boot/grub/ " "directory (or sometimes /boot/boot/grub/) and add an " "entry for the installer, for example (assuming /boot is " "on the first partition of the first disk in the system):" msgstr "" "使用 GRUB1 的过程也类似。在 /boot/grub/ 目录下找到 menu.lst (或者位于 /boot/" "boot/grub/),然后给安装程序增添一个入口,例如(假设 /" "boot 位于系统中第一个磁盘的第一个分区上面):" #. Tag: screen #: boot-installer.xml:748 #, 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:750 #, no-c-format msgid "" "The procedure for GRUB2 is very similar. The file is " "named grub.cfg instead of menu.lst. An entry for the installer would be for instance for example:" msgstr "" "使用 GRUB2 的过程类似。它使用 grub.cfg 替代 menu.lst 文件。安装程序的入口,例如:" #. Tag: screen #: boot-installer.xml:756 #, 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:758 #, no-c-format msgid "" "From here on, there should be no difference between GRUB " "or LILO." msgstr "" "从这里开始,下面采用 GRUBLILO 将没" "有什么差别。" # index.docbook:723, index.docbook:1876, index.docbook:2278, index.docbook:2426 #. Tag: title #: boot-installer.xml:767 boot-installer.xml:1968 #, no-c-format msgid "Booting from Floppies" msgstr "从软盘引导" # index.docbook:724, index.docbook:2286 #. Tag: para #: boot-installer.xml:768 boot-installer.xml:1976 #, no-c-format msgid "" "You will have already downloaded the floppy images you needed and created " "floppies from the images in ." msgstr "" "您可能已经下载了所需要的软盘映像,并且根据这些映像创建了软盘 。" #. Tag: para #: boot-installer.xml:775 #, 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:781 #, 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 root= 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 " "install root=/dev/hdc at the boot prompt." msgstr "" "要想在 LS-120 驱动器(ATAPI 版本)使用这些软盘,您需指定这些软盘设备的虚拟地" "址。这可以通过 root= 引导参数来指定映射的 ide-floppy 驱" "动器设备名来完成。比如,您的 LS-120 驱动器连接到第二根线第一个 IDE 设备" "(master),那么在提示符下输入 install root=/dev/hdc。" #. Tag: para #: boot-installer.xml:791 #, no-c-format msgid "" "Note that on some machines, Control Alt Delete does not properly reset the " "machine, so a hard 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 "" "注意有些机器上,Control Alt " "Delete 不能正常地重启系统,所以推荐使用硬" "启动。如果您正从已有的操作系统上安装(比如在 DOS 系统上),将没有这样的" "选择。在其它情况下,请在引导时使用硬重启。" #. Tag: para #: boot-installer.xml:800 #, 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 boot: prompt." msgstr "" "读完软盘后,您将看到屏幕上有一个有关引导软盘的介绍,并且结尾是 boot:" " 提示符。" #. Tag: para #: boot-installer.xml:806 #, no-c-format msgid "" "Once you press &enterkey;, you should see the message " "Loading..., followed by " "Uncompressing Linux..., 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 ." msgstr "" "一旦敲入 &enterkey;,您应该能够看到 Loading... 消息,并且接下来是 Uncompressing Linux...,然后是一些有关系统硬件的信息。更多有关这段引导过程的信息,在" "下面 可以找到。" #. Tag: para #: boot-installer.xml:815 #, 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 debian-installer is automatically " "launched." msgstr "" "从引导软盘启动后需要根软盘。请插入根软盘并且输入 &enterkey;,其中的内容会被装" "入内存。安装程序 debian-installer 会自动加载。" # 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:825 boot-installer.xml:1449 boot-installer.xml:1591 #: boot-installer.xml:1912 boot-installer.xml:2060 #, no-c-format msgid "Booting with TFTP" msgstr "用 TFTP 引导" #. Tag: para #: boot-installer.xml:850 #, no-c-format msgid "There are various ways to do a TFTP boot on i386." msgstr "在 i386 体系上有很多方法用 TFTP 进行引导。" #. Tag: title #: boot-installer.xml:856 #, no-c-format msgid "NIC or Motherboard that support PXE" msgstr "支持 PXE 的网卡或者主板" #. Tag: para #: boot-installer.xml:857 #, no-c-format msgid "" "It could be that your Network Interface Card or Motherboard provides PXE " "boot functionality. This is a Intel " "re-implementation of TFTP boot. If so, you may be able to configure your " "BIOS to boot from the network." msgstr "" "您的网卡或者主板可能已经提供了 PXE 引导功能。它是 Intel TFTP 引导的实现。如果是这样,您可以配置 BIOS 用网络进行" "引导。" #. Tag: title #: boot-installer.xml:868 #, no-c-format msgid "NIC with Network BootROM" msgstr "网络 BootROM 的网卡" #. Tag: para #: boot-installer.xml:869 #, no-c-format msgid "" "It could be that your Network Interface Card provides TFTP boot " "functionality." msgstr "您的网卡很有可能提供了 TFTP 引导功能。" #. Tag: para #: boot-installer.xml:874 #, no-c-format msgid "" "Let us (&email-debian-boot-list;) know how did you manage it. " "Please refer to this document." msgstr "" "让我们知道(&email-debian-boot-list;)您如何来操作它的。请参阅此" "文档。" #. Tag: title #: boot-installer.xml:882 #, no-c-format msgid "Etherboot" msgstr "Etherboot" #. Tag: para #: boot-installer.xml:883 #, no-c-format msgid "" "The etherboot project " "provides bootdiskettes and even bootroms that do a TFTPboot." msgstr "" "etherboot project 提供了为 " "TFTP 引导所需要的引导软盘甚至是引导 ROMS 。" # index.docbook:1943, index.docbook:2477 #. Tag: title #: boot-installer.xml:893 #, no-c-format msgid "The Boot Screen" msgstr "引导界面" #. Tag: para #: boot-installer.xml:894 #, 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:899 #, 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:903 #, 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:911 #, no-c-format msgid "" "Depending on the installation method you are using, the Graphical " "install 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:918 #, fuzzy, no-c-format #| msgid "" #| "For a normal installation, select either the Install or " #| "the Graphical install entry — using either the arrow " #| "keys on your keyboard or by typing the first (highlighted) letter, the " #| "Install entry is already selected by default — and " #| "press &enterkey; to boot the installer." msgid "" "For a normal installation, select either the Graphical install or the Install entry — using either the arrow " "keys on your keyboard or by typing the first (highlighted) letter — " "and press &enterkey; to boot the installer. The Graphical install entry is already selected by default." msgstr "" "普通安装时,选择 InstallGraphical install " "入口 — 可以使用键盘方向键或者键入(高亮的)首字母,默认 Install 入口已经选中 — 然后按下 &enterkey; 引导安装程序。" #. Tag: para #: boot-installer.xml:926 #, no-c-format msgid "" "The Advanced options entry gives access to a second menu that " "allows to boot the installer in expert mode, in rescue mode and for " "automated installs." msgstr "" "Advanced options 选项用于访问第二层菜单,引导安装程序进入 " "expert 模式、rescue 模式和自动安装。" #. Tag: para #: boot-installer.xml:932 #, fuzzy, no-c-format #| msgid "" #| "If you wish or need to add any boot parameters for either the installer " #| "or the kernel, press &tabkey;. This will display the default boot command " #| "for the selected menu entry and allow to add additional options. The help " #| "screens (see below) list some common possible options. Press &enterkey; " #| "to boot the installer with your options; pressing &escapekey; will return " #| "you to the boot menu and undo any changes you made." 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. 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 "" "如果您希望或者需要添加引导参数给安装程序或内核,按下 &tabkey;。将显示对应菜单" "项的默认引导命令,并允许添加额外的选项。帮助界面(下方)列出一些可能的选项。按" "下 &enterkey; 将使用您的选项引导安装程序;按下 &escapekey; 返回引导菜单并放弃" "您所做的修改。" #. Tag: para #: boot-installer.xml:944 #, no-c-format msgid "" "Choosing the Help 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: \n" "Press F1 for the help index, or ENTER to boot:\n" " 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 install) and a space before " "the first parameter (e.g., install fb=false)." msgstr "" "选择 Help 项将进入第一个帮助界面,显示可用的帮助界面概要。当出" "现帮助界面后要返回引导菜单,需要在引导提示符后输入 'menu' 并按 &enterkey;。所" "有的帮助界面在引导命令可以输入的地方都有一个引导提示: " "\n" "Press F1 for the help index, or ENTER to boot:\n" " 在这个引导提示的地方您可以按下 &enterkey; 使用默" "认的选项引导安装程序,或者输入指定的引导命令以及引导参数。一些可用的引导参数" "可能会在多个帮助界面看到。假如您要添加任何参数到引导命令行,确保首先输入的是" "引导方法(默认为 install),然后在第一个参数前要有空格" "(例如:install fb=false)。" #. Tag: para #: boot-installer.xml:962 #, 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 schema of the US keyboard layout which can be used as a " "reference to find the correct keys to use." msgstr "" "此时键盘假设使用的是默认美式英文布局。这意味着如果您的键盘使用不同的(特定语言" "的)布局,显示在屏幕上的字符可能与您键入参数时希望的不同。维基百科里面有一个 " "schema of the US keyboard layout 条目" "说明了如何找到要使用正确的键。" #. Tag: para #: boot-installer.xml:972 #, 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 integrated Lights Out " "(iLO) and HP's Integrated Remote Assistant (IRA)." msgstr "" "如果您使用 BIOS 配置为串口控制台的系统,可能在启动安装程序的时候无法看到起始" "图形界面;甚至无法看到引导菜单。这种情况同样会发生在您使用远程管理设备安装系" "统,并且这些设备提供了字符界面到 VGA 控制台的情况下。比如 Compaq 的 " "integrated Lights Out (iLO) 和 HP 的 Integrated Remote " "Assistant (IRA)。" #. Tag: para #: boot-installer.xml:982 #, 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 H " "followed by &enterkey; to select the Help 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 vga=normal fb=false to the " "boot prompt, as described in the help text." msgstr "" "要跳过图形引导界面,您可以在没有任何显示时按下 &escapekey; 得到字符引导提示" "符,或者(同样没有任何显示)按下 &enterkey; 和 H 选择上面描述的 " "Help 选项。以后输入就会在提示符后面显示。要防止余下的安装仍使" "用 framebuffer,您还需要在启动提示后添加 vga=normal fb=false,这在帮助里面有说明。" #. Tag: title #: boot-installer.xml:998 #, no-c-format msgid "The Graphical Installer" msgstr "" #. Tag: para #: boot-installer.xml:999 #, 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:1007 #, 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 newt 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:1016 #, 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 Advanced options menu. The " "previously used boot methods installgui, " "expertgui and rescuegui can " "still be used from the boot prompt which is shown after selecting the " "Help option in the boot menu." msgstr "" #. Tag: para #: boot-installer.xml:1027 #, no-c-format msgid "" "There is also a graphical installer image that can be netbooted. And there " "is a special mini ISO image " " The mini ISO image can be downloaded from a &debian; mirror as " "described in . Look for " "netboot/gtk/mini.iso. , which is " "mainly useful for testing." msgstr "" #. Tag: para #: boot-installer.xml:1040 #, no-c-format msgid "" "For &arch-title;, currently only an experimental mini ISO " "image is available The mini ISO image " "can be downloaded from a &debian; mirror as described in . Look for netboot/gtk/mini.iso. " " . 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:1054 #, 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:1060 #, 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 newt frontend." msgstr "" #. Tag: para #: boot-installer.xml:1067 #, 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:1121 #, no-c-format msgid "CD Contents" msgstr "CD 的内容" #. Tag: para #: boot-installer.xml:1123 #, no-c-format msgid "" "There are three basic variations of &debian; Install CDs. The " "Business Card 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 Network Install 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; 安装光盘 CD 衍生品:名片式(Business Card) CD 有一个微型的安装程序,并且可以储存在一小张 CD 介质上。它需要借助" "网络连接来安装基本系统的其他部分,才能建立起一个可用的系统。网络安" "装(Network Install) CD 光盘具有基本系统需的所有包,但是它还是需要" "网络连接到 &debian; 的镜像,安装其他的软件包建立一个完整的系统。&debian; CD " "光盘套件,则可以不使用网络就能安装大量软件包,建立完整的系统。" #. Tag: para #: boot-installer.xml:1139 #, 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:1155 #, no-c-format msgid "" "The &debian; Installer CD contains a small EFI partition where the " "ELILO 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 分区来放置 ELILO,它" "的配置文件,安装程序内核以及初始的文件系统(initrd)。运行的系统同时也包含了一" "个 EFI 分区用于放置引导系统所需要的必要文件。这些文件可以从 EFI Shell 读出," "说明如下。" #. Tag: para #: boot-installer.xml:1164 #, no-c-format msgid "" "Most of the details of how ELILO 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 ELILO 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 "" "大部分有关如何 ELILO 实际装入和开始一个系统的细节是对系统" "安装程序透明的。但是,安装程序必须设置 EFI 分区优先级来安装基本系统。否则 " "ELILO 的安装将会失败并且导致系统不可引导。EFI 分区是分配并" "且格式 化与分区步骤以装入系统磁盘的所有软件包。分区任务也需要为接下来的安装检" "查一个 EFI 分区是否合适。" #. Tag: para #: boot-installer.xml:1176 #, 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, Boot Option " "Maintenance Menu and EFI Shell (Built-in). " "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 在固件初始化的最后一步会被启动。它显示一个菜单列表供用户选" "择。取决于系统的型号并且是否有其他的软件已经被装入系统,这个菜单可能在不同系" "统上有不同表现。在每一个系统上,至少有两个菜单项显示,Boot Option " "Maintenance MenuEFI Shell (Built-in)。推荐使" "用第一个,当然,该选项不可用或者 CD 由于某种原因没法启动,使用第二个。" #. Tag: title #: boot-installer.xml:1195 #, no-c-format msgid "IMPORTANT" msgstr "重要" #. Tag: para #: boot-installer.xml:1196 #, 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 exit at the " "shell prompt." msgstr "" "EFI Boot Manager 会在预设的几秒钟之后选择默认的启动方式,一般是第一菜单项。在" "屏幕底部会有倒计时显示。时间一到,系统按默认方式启动,这样您也许需要重新启动" "才能继续安装。如果默认是 EFI Shell,您可在提示符下执行 exit返回 Boot Manager。" #. Tag: title #: boot-installer.xml:1208 #, no-c-format msgid "Option 1: Booting from the Boot Option Maintenance Menu" msgstr "选项 1: 从 Boot Option Maintenance Menu 启动" #. Tag: para #: boot-installer.xml:1215 #, 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 "" "插入 CD 到 DVD/CD 驱动器,然后重启机器。固件在完成系统初始化后会显示 EFI " "Boot Manager 页面和菜单。" #. Tag: para #: boot-installer.xml:1221 #, no-c-format msgid "" "Select Boot Maintenance Menu from the menu with the arrow " "keys and press ENTER. This will display a new menu." msgstr "" "选择 Boot Maintenance Menu 通过方向键然后按下 " "ENTER。会显示一个新菜单。" #. Tag: para #: boot-installer.xml:1227 #, no-c-format msgid "" "Select Boot From a File from the menu with the arrow keys " "and press ENTER. This will display a list of devices " "probed by the firmware. You should see two menu lines containing either the " "label Debian Inst [Acpi ... or Removable Media " "Boot. If you examine the rest of the menu line, you will notice " "that the device and controller information should be the same." msgstr "" "选择 Boot From a File 通过方向键,然后按下 " "ENTER。将显示固件检测到的设备列表。您会看到两个菜单行,它" "们包括 Debian Inst [Acpi ...Removable Media " "Boot标签。如果您检查菜单行其他部分,会看到对应的设备和控制器信息。" #. Tag: para #: boot-installer.xml:1238 #, 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 ENTER. If you " "choose Removable Media Boot the machine will immediately " "start the boot load sequence. If you choose Debian Inst [Acpi ... 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 驱动的入口。通过方向键选择并按下 ENTER。如果您选择 Removable Media Boot 机器将进入启动步" "骤。如果您选择 Debian Inst [Acpi ...,它会显示一个可启动" "的 CD 目录列表,要求您进行(额外的)下一步。" #. Tag: para #: boot-installer.xml:1249 #, no-c-format msgid "" "You will only need this step if you chose Debian Inst [Acpi .... The directory listing will also show [Treat like " "Removable Media Boot] on the next to the last line. Select this " "line with the arrow keys and press ENTER. This will start " "the boot load sequence." msgstr "" "您只在选择 Debian Inst [Acpi ... 时需要。目录列表还会显示 " "[Treat like Removable Media Boot] 至最后一行。用方向键选" "择,并按下 ENTER。这将进入启动步骤。" #. Tag: para #: boot-installer.xml:1261 #, 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:1271 #, no-c-format msgid "Option 2: Booting from the EFI Shell" msgstr "选项 2: 从 EFI Shell 启动" #. Tag: para #: boot-installer.xml:1272 #, 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 " "EFI Shell [Built-in]. Boot the &debian; Installer CD with " "the following steps:" msgstr "" "某些情况下,选项 1 无法成功,重新启动机器然后在 EFI Boot Manager 画面出现的时" "候会有一个选项称为 EFI Shell [Built-in]。可以通过如下步骤" "来引导 &debian; 安装程序 CD :" #. Tag: para #: boot-installer.xml:1283 #, 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 "把 CD 放入 DVD/CD 驱动器。" #. Tag: para #: boot-installer.xml:1289 #, no-c-format msgid "" "Select EFI Shell from the menu with the arrow keys and " "press ENTER. 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 fsn:. All other " "recognized partitions will be named blkn:. If you inserted the CD just before entering the " "shell, this may take a few extra seconds as it initializes the CD drive." msgstr "" "选择 EFI Shell 然后按下 ENTER。EFI " "Shell 将扫描所有的可引导设备,并且在显示其命令提示符前在控制台列出它们。在设" "备上被辨认出的可引导分区,将显示成 fsn:" "。所有其他辨认出的分区,将被命名为 blkn:。如果您在进入 Shell 之前就插入 CD,这将花费一些时间" "用于初始化 CD 驱动器。" #. Tag: para #: boot-installer.xml:1303 #, no-c-format msgid "" "Examine the output from the shell looking for the CDROM drive. It is most " "likely the fs0: device although other devices with " "bootable partitions will also show up as fsn." msgstr "" "在检查 CD 驱动器期间请查看 Shell 的输出显示。一般来说是 fs0: 并且其他具有可引导分区的设备上也会显示成 " "fsn。" #. Tag: para #: boot-installer.xml:1310 #, no-c-format msgid "" "Enter fsn: and press " "ENTER to select that device where n is the partition number for the CDROM. The shell will now " "display the partition number as its prompt." msgstr "" "进入 fsn: 然后按下 " "ENTER 来选择设备。这里 n 是 CD " "光盘的分区号。Shell 现在将在提示符下显示分区号。" #. Tag: para #: boot-installer.xml:1317 #, no-c-format msgid "" "Enter elilo and press ENTER. This will " "start the boot load sequence." msgstr "" "进入 elilo 并按下 ENTER。这将进入启动步" "骤。" #. Tag: para #: boot-installer.xml:1324 #, 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 fsn:elilo command at the shell prompt. Proceed to selecting the boot kernel " "and options." msgstr "" "与选项 1 相同,这些步骤也会启动 &debian; boot loader,显示一个菜单页供选择启" "动内核和参数。您可在 shell 提示符下输入 fsn:elilo简短命令。进入选择启动内核和选项。" #. Tag: title #: boot-installer.xml:1338 #, no-c-format msgid "Installing using a Serial Console" msgstr "使用串口控制台安装" #. Tag: para #: boot-installer.xml:1340 #, 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 [BAUD baud " "serial console], where BAUD 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] 的选项。要通过串口连接,选择包含 [BAUD baud serial console] 的选项,其中 BAUD 是串行连接速度。对于大多数常见的波特率的 ttyS0 设备菜单项已经预" "置。" #. Tag: para #: boot-installer.xml:1351 #, 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 baud at the EFI " "shell." msgstr "" "大多时候,您会让安装程序使用与连接 EFI 控制台相同的波特率。如果您不知如何设" "置,可以通过命令 baud 在 EFI shell 获得。" #. Tag: para #: boot-installer.xml:1358 #, 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 console=ttyS1,57600n8 into " "the Boot: text window." msgstr "" "如果没有串行配置的选项或者您要使用的波特率,可以覆盖某个已有菜单项里面的波特" "率。例如,使用 57600 波特率覆盖 ttyS1 设备,输入 " "console=ttyS1,57600n8Boot: 文本" "窗口。" #. Tag: para #: boot-installer.xml:1369 #, 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 Params help menu for " "instructions on starting the installer in Text Mode." msgstr "" "大多数 IA-64 机器配备默认 9600 波特率的控制台。这样设太慢,普通安装过程将花费" "明显的时间刷新每个屏幕。您要么通过提高波特率提升安装效率,要么使用文本模式安" "装。参考 Params 帮助菜单,获得启动文本模式安装的指导。" #. Tag: para #: boot-installer.xml:1378 #, 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:1387 #, no-c-format msgid "Selecting the Boot Kernel and Options" msgstr "选择启动内核与选项" #. Tag: para #: boot-installer.xml:1389 #, no-c-format msgid "" "The boot loader will display a form with a menu list and a text window with " "a Boot: 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 General help screen " "explains the menu choices and the Params screen " "explains the common command line options." msgstr "" "引导程序会显示一个表单,具有菜单列与包含 Boot: 提示符" "的文本窗口。用方向键选择菜单项并且键盘输入的字符将显示在文本窗口。输入适当的" "功能键会显示帮助窗口。普通的帮助窗口解释菜单选项," "Params窗口解释命令行参数。" #. Tag: para #: boot-installer.xml:1401 #, no-c-format msgid "" "Consult the General help screen for the description " "of the kernels and install modes most appropriate for your installation. You " "should also consult below for any additional " "parameters that you may want to set in the Boot: 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 "" "查询 General 帮助页面,了解内核的说明和安装对应的模" "式。您还应该查询 ,了解在文本窗口中需要设置的额" "外参数 Boot:,您选择的内核版本将会用在安装过程和安装好" "的系统中。如果安装时碰到内核问题,在安装好的系统中也会出现。以下两步选择和开" "始安装:" #. Tag: para #: boot-installer.xml:1419 #, 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:1424 #, 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:1431 #, no-c-format msgid "" "Press ENTER. 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 "" "按下 ENTER。会加载并启动内核。内核在 &debian; 安装程序的第" "一个屏幕显示常规的初始化信息。" #. Tag: para #: boot-installer.xml:1440 boot-installer.xml:1577 #, 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:1451 #, 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 "" "在 IA-64 系统上面从网络引导很像从 CD 上引导。惟一的区别是如何装入内核。EFI " "Boot Manager 可以装入并且从网络服务器启动程序。一旦安装内核被装入并且启动,系" "统的安装将和 CD 安装步骤相同,只是基本软件包将从网络装入而不是 CD 光盘驱动" "器。" #. Tag: para #: boot-installer.xml:1486 #, 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 " "elilo. On the client a new boot option must be defined in " "the EFI boot manager to enable loading over a network." msgstr "" "网络引导一台 IA-64 系统需要两个体系相关的操作。在 boot 服务器上,DHCP 和 " "TFTP 必须配置成可以传送 elilo。在客户端,一个新的引导选项" "必须在 EFI boot manager 下定义来打开网络的装入。" #. Tag: title #: boot-installer.xml:1497 #, no-c-format msgid "Configuring the Server" msgstr "配置网络服务器" #. Tag: para #: boot-installer.xml:1498 #, no-c-format msgid "" "A suitable TFTP entry for network booting an IA-64 system looks something " "like this: \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" " Note that the goal is to get elilo.efi running on the client." msgstr "" "一个合适的用于 IA-64 系统网络引导的 TFTP 选项应该看起来像这样: " "\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" " 注明的是,目标是让 elilo.efi " "在客户端运行。" #. Tag: para #: boot-installer.xml:1508 #, no-c-format msgid "" "Extract the netboot.tar.gz file into the directory used " "as the root for your tftp server. Typical tftp root directories include " "/var/lib/tftp and /tftpboot. This " "will create a debian-installer directory tree " "containing the boot files for an IA-64 system." msgstr "" "使用 root 解压 netboot.tar.gz 文件到您的 tftp 服务器。典" "型的 tftp 根目录包括 /var/lib/tftp/" "tftpboot。这将创建 debian-installer 目录树," "它包括 IA-64 系统需要的启动文件。" #. Tag: screen #: boot-installer.xml:1518 #, 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:1518 #, no-c-format msgid "" "The netboot.tar.gz contains an elilo.conf file that should work for most configurations. However, should you " "need to make changes to this file, you can find it in the debian-" "installer/ia64/ 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 .conf instead of " "elilo.conf. See documentation provided in the " "elilo package for details." msgstr "" "netboot.tar.gz 包含 elilo.conf 可以" "工作在大多数的配置下。另外,要修改这个文件,您可以在 debian-" "installer/ia64/ 目录中找到。这只需要按照客户机 IP 地址的16进制命名" "这些文件并且给出 .conf 后缀取代 elilo.conf。请查看 elilo 软件包附带的文档以获得细节。" #. Tag: title #: boot-installer.xml:1535 #, no-c-format msgid "Configuring the Client" msgstr "配置客户机" #. Tag: para #: boot-installer.xml:1536 #, no-c-format msgid "" "To configure the client to support TFTP booting, start by booting to EFI and " "entering the Boot Option Maintenance Menu. " " Add a boot option. You " "should see one or more lines with the text Load File " "[Acpi()/.../Mac()]. 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. Name the entry Netboot or something similar, save, and exit back to the boot options " "menu. You should see the new boot option " "you just created, and selecting it should initiate a DHCP query, leading to " "a TFTP load of elilo.efi from the server." msgstr "" "如果要配置支持 TFTP 引导的客户机,只需要引导至 EFI,然后进入 Boot " "Option Maintenance Menu 加入一个引" "导选项。 您会看到一行或多行带有 " "Load File [Acpi()/.../Mac()] 文字。如果多于一个入" "口存在,选择您需要启动的包含 MAC 地址的网卡。使用方向键高亮选择,然后按回车。" " 给此选项起名,如 Netboot 或者相似的,保存然后退回至引导选项菜单。 您现在应该能够看到刚刚创建的新引导选项,选择后应该会初始化一个 " "DHCP 查询,然后会从服务器装入 elilo.efi。" #. Tag: para #: boot-installer.xml:1568 #, 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 将显示它的提示符。从这里开始,安装过程" "将和 CD 安装是 同样的过程。在内核已经完成从网络的自我安装后选择一个像上面提到" "的引导选项,它将开始 &debian; 安装程序。" #. Tag: title #: boot-installer.xml:1622 #, no-c-format msgid "s390 Limitations" msgstr "s390 的限制" #. Tag: para #: boot-installer.xml:1623 #, 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:1628 #, 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:1639 #, no-c-format msgid "s390 Boot Parameters" msgstr "s390 引导参数" #. Tag: para #: boot-installer.xml:1640 #, 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. A sample parm file " #| "parmfile.debian is provided with the installation " #| "images." 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 parmfile.debian " "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 格式的。参数文件的示例 parmfile.debian 提供了安装" "映像。" #. Tag: para #: boot-installer.xml:1657 #, 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 cio_ignore option supports both a blacklist (to " "only disallow a few devices) and a whitelist (to only allow specific " "devices): \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" " 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 parmfile.debian." msgstr "" #. Tag: para #: boot-installer.xml:1721 #, 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 c key, or else the combination of " "Command, Option, Shift, " "and Delete keys together while booting to boot from the " "factory default CD/DVD drive." msgstr "" "目前,&arch-title; 下的子体系只有 PReP/CHRP (并非所有系统)和 New World " "PowerMacs 支持 CD-ROM 引导。在 PowerMacs 上,启动时按住 c " "键,或者 CommandOptionShiftDelete 组合键引导出厂默认的 CD/DVD 驱动器。" #. Tag: para #: boot-installer.xml:1730 #, no-c-format msgid "" "To boot a PowerMac from an external Firewire CD/DVD drive invoke Open " "Firmware prompt first (see ), then " "type \n" "0 > boot fw/node/sbp-2/disk:,\\install\\yaboot\n" " for an alternative way to boot from the internal " "factory default CD/DVD drive type" msgstr "" "从外置固件 CD/DVD 驱动器引导 PowerMac 首先打开 Open Firmware 提示符 (参见 " "),然后键入 " "\n" "0 > boot fw/node/sbp-2/disk:,\\install\\yaboot\n" " 另一种方法引导出厂默认的 CD/DVD 驱动器,键入" #. Tag: screen #: boot-installer.xml:1741 #, no-c-format msgid "0 > boot cd:,\\install\\yaboot" msgstr "0 > boot cd:,\\install\\yaboot" #. Tag: para #: boot-installer.xml:1743 #, 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; CD 上引导,因为 OldWorld 计算机需要在 " "CD 上安装一个 MacOSROM CD 引导驱动程序但是目前还没有自由的版本。所有的 " "OldWorld 系统具有软盘驱动程序,因此可以使用软盘驱动程序来启动安装程序,然后让" "安装程序 从 CD 上选择所需要的文件。" #. Tag: para #: boot-installer.xml:1752 #, no-c-format msgid "" "To boot &debian; CD/DVD on Pegasos II machine, hold Esc key " "immediately after pressing the power-on button, when SmartFirmware prompt " "appears, type" msgstr "" "要在 Pegasos II 机器上引导 &debian; CD/DVD,按下电源按钮同时按住 " "Esc 键,出现 SmartFirmware 提示符后,键入" #. Tag: screen #: boot-installer.xml:1758 #, no-c-format msgid "boot cd install/pegasos" msgstr "boot cd install/pegasos" #. Tag: para #: boot-installer.xml:1760 #, fuzzy, no-c-format #| msgid "" #| "To boot &debian; CD/DVD on Pegasos II machine, hold Esc " #| "key immediately after pressing the power-on button, when SmartFirmware " #| "prompt appears, type" msgid "" "On YDL Powerstation machine, press s immediately after " "Press 's' to enter Open Firmware message, when SLOF prompt " "appears type" msgstr "" "要在 Pegasos II 机器上引导 &debian; CD/DVD,按下电源按钮同时按住 " "Esc 键,出现 SmartFirmware 提示符后,键入" #. Tag: screen #: boot-installer.xml:1765 #, no-c-format msgid "0 > boot cdrom" msgstr "0 > boot cdrom" #. Tag: title #: boot-installer.xml:1771 #, no-c-format msgid "Booting from Hard Disk" msgstr "从硬盘引导" # index.docbook:1591, index.docbook:2097 #. Tag: para #: boot-installer.xml:1777 #, 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:1783 #, no-c-format msgid "" "To boot the installer from hard disk, you will have already completed " "downloading and placing the needed files as described in ." msgstr "" "如果要从硬盘上引导安装程序,您需要参考 " "下载并且安置所需文件。" #. Tag: title #: boot-installer.xml:1803 #, no-c-format msgid "Booting OldWorld PowerMacs from MacOS" msgstr "从 OldWorld PowerMacs 的 MacOS 上引导" #. Tag: para #: boot-installer.xml:1804 #, no-c-format msgid "" "If you set up BootX in , you can use it to " "boot into the installation system. Double click the BootX " "application icon. Click on the Options button and " "select Use Specified RAM Disk. This will give you the " "chance to select the ramdisk.image.gz file. You may " "need to select the No Video Driver checkbox, depending " "on your hardware. Then click the Linux button to shut " "down MacOS and launch the installer." msgstr "" "如果您在 中设置好了 BootX,您可以使用它引" "导进入安装系统。双击 BootX 应用程序图标。点击 " "Options 按钮并且选择 Use Specified RAM " "Disk。这将可以让您选择 ramdisk.image.gz 文" "件。也许根据您的硬件情况需要选择 No Video Driver 选择" "框。然后点击 Linux 按钮,来关闭 MacOS 以及启动安装程" "序。" #. Tag: title #: boot-installer.xml:1822 #, no-c-format msgid "Booting NewWorld Macs from OpenFirmware" msgstr "从 NewWorld Macs 的 OpenFirmware 引导" #. Tag: para #: boot-installer.xml:1823 #, no-c-format msgid "" "You will have already placed the vmlinux, " "initrd.gz, yaboot, and " "yaboot.conf files at the root level of your HFS " "partition in . You will now have to boot " "into OpenFirmware (see ). At the " "prompt, type \n" "0 > boot hd:x,yaboot\n" " replacing x 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 " "ide0: instead of hd:. In a few " "more seconds you will see a yaboot prompt \n" "boot:\n" " At yaboot's boot: prompt, type " "either install or install video=ofonly followed by a &enterkey;. The video=ofonly " "argument is for maximum compatibility; you can try it if install doesn't work. The &debian; installation program should start." msgstr "" "您应该已经将 vmlinuxinitrd.gz、 " "yabootyaboot.conf 文件在 HFS 分" "区的根层次放置好了 。现在必须引导进入 Open " "Firmware (参阅 )。在提示符下,输" "入: \n" "0 > boot hd:x,yaboot\n" " 用放置内核和 yaboot 文件的 HFS 分区号来替换 " "x, 然后按下 &enterkey;。在某些机器上,您也许需要时" "用 ide0: 来替换 hd:,在接下来的" "几秒钟内,将会看到一个提示符 \n" "boot:\n" " 在 yaboot 的 boot: 提示符下,输" "入 install 或者 install video=ofonly 然后按下 &enterkey;。video=ofonly 参数是用" "于最大可能性的兼容性;您可以在 install 不工作的情况下" "尝试使用它。&debian; 安装程序将会启动。" # index.docbook:700, index.docbook:2176 #. Tag: title #: boot-installer.xml:1855 #, no-c-format msgid "Booting from USB memory stick" msgstr "从 U 盘引导" #. Tag: para #: boot-installer.xml:1856 #, no-c-format msgid "Currently, NewWorld PowerMac systems are known to support USB booting." msgstr "当前,New World PowerMac 系统支持从 USB 引导。" #. Tag: para #: boot-installer.xml:1862 #, no-c-format msgid "" "Make sure you have prepared everything from . 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 ." msgstr "" "确认您已经准备就绪 。要从 USB 记忆棒引导 " "Macintosh 系统,即使 Open Firmware 默认不搜索 USB 存储设备,您也需要使用 " "Open Firmware 提示符。参阅 。" #. Tag: para #: boot-installer.xml:1871 #, no-c-format msgid "" "You will need to work out where the USB storage device appears in the device " "tree, since at the moment ofpath cannot work that out " "automatically. Type dev / ls and devalias 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 usb0/disk, usb0/hub/disk, /pci@f2000000/usb@1b,1/disk@1, and " "/pci@f2000000/usb@1b,1/hub@1/disk@1 work." msgstr "" "您还需要算出 USB 存储设备在设备树上的位置,因为现在 ofpath 无法自动计算。键入 dev / ls 和 " "devalias 到 Open Firmware 提示符下,得到所有的已知设备" "和设备别名。在笔者的系统上有各种 USB 记忆棒,路径诸如 usb0/disk, usb0/hub/disk, /pci@f2000000/" "usb@1b,1/disk@1,和 /pci@f2000000/usb@1b,1/hub@1/" "disk@1 。" #. Tag: para #: boot-installer.xml:1883 #, no-c-format msgid "" "Having worked out the device path, use a command like this to boot the " "installer: \n" "boot usb0/disk:2,\\\\:" "tbxi\n" " The 2 matches the " "Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image " "earlier, and the ,\\\\:tbxi part instructs Open " "Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. " "yaboot) in the directory previously blessed with " "hattrib -b." msgstr "" "得到设备路径之后,用类似下面的命令启动安装程序: \n" "boot usb0/disk:2,\\\\:" "tbxi\n" " 2 匹配前面复制启动映象" "所在的 Apple_HFS 或 Apple_Bootstrap 分区,,\\\\:tbxi " "部分指示 Open Firmware 从具有 \"tbxi\" 类型的 HFS 文件引导(如 " "yaboot) 位于前面使用 bless 目录 hattrib -b。" #. Tag: para #: boot-installer.xml:1897 #, no-c-format msgid "" "The system should now boot up, and you should be presented with the " "boot: prompt. Here you can enter optional boot arguments, " "or just hit &enterkey;." msgstr "" "系统应该可以引导,然后您看到 boot: 提示符。这里您可以输入启" "动参数,或者只按下 &enterkey;。" #. Tag: para #: boot-installer.xml:1903 #, 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 ." msgstr "" "这个是新的启动方法,可能无法在一些 NewWorld 系统上工作。如果您遇到问题,请写" "下安装报告,参阅 。" #. Tag: para #: boot-installer.xml:1937 #, no-c-format msgid "Currently, PReP and New World PowerMac systems support netbooting." msgstr "目前来说,PReP 以及 New World PowerMac 系统支持网络引导。" #. Tag: para #: boot-installer.xml:1941 #, no-c-format msgid "" "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot " "monitor (see ) and use the command " "\n" "0 > boot enet:0\n" " If this doesn't work, you might have to add the " "filename like this: \n" "0 > boot enet:0,yaboot\n" " PReP and CHRP boxes may have different ways of " "addressing the network. On a PReP machine, you should try " "\n" "boot net:server_ipaddr,file,client_ipaddr\n" " On some PReP systems (e.g. Motorola PowerStack " "machines) the command help boot may give a " "description of syntax and available options." msgstr "" "在 Open Firmware 机器上,比如 NewWorld Power Macs,进入引导监视器(参阅 ) 并使用命令 \n" "0 > boot enet:0\n" " 如果无效,您也许该添加文件名,比如:" "\n" "0 > boot enet:0,yaboot\n" " 可能使用不同的途径来确认网络。在一台 PReP 机器" "上,您应该尝试 \n" "boot net:server_ipaddr,file,client_ipaddr\n" " 在有些 PReP 系统上(比如 Motorola PowerStack), " "help boot 命令可以给出语法和选项的说明。" #. Tag: para #: boot-installer.xml:1969 #, 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:1981 #, no-c-format msgid "" "To boot from the boot-floppy-hfs.img floppy, place it " "in floppy drive after shutting the system down, and before pressing the " "power-on button." msgstr "" "若需要从 boot-floppy-hfs.img 软盘引导,请在关闭系统后在" "按下电源开关前把它放到软盘驱动器内。" #. Tag: para #: boot-installer.xml:1987 #, 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:1994 #, no-c-format msgid "" "After booting, the root.bin 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 "" "引导之后需要含有 root.bin 的软盘。插入引导软盘并且按下 " "&enterkey;。安装程序将在根系统被装入内存后自动启动。" #. Tag: title #: boot-installer.xml:2005 #, no-c-format msgid "PowerPC Boot Parameters" msgstr "PowerPC 引导参数" #. Tag: para #: boot-installer.xml:2006 #, 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 " "video=atyfb:vmode:6 , which will select that mode for " "most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to " "video=aty128fb:vmode:6 ." msgstr "" "许多比较老的 Apple 显示器使用 640x480 67Hz 模式。如果您的显示在这些老 Apple " "显示器上是扭曲的,请尝试加入引导参数 video=atyfb:vmode:6 。它将为大多数 Mach64 和 Rage 显示设备选择合适的模式。对于 Rage " "128 来说,请改变其值为 video=aty128fb:vmode:6 。" #. Tag: title #: boot-installer.xml:2018 #, no-c-format msgid "Booting a ppc64el machine" msgstr "" #. Tag: para #: boot-installer.xml:2019 #, no-c-format msgid "How to boot a ppc64el machine:" msgstr "" #. Tag: title #: boot-installer.xml:2025 #, no-c-format msgid "Petitboot" msgstr "Petitboot" #. Tag: para #: boot-installer.xml:2026 #, 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:2034 #, 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:2085 #, no-c-format msgid "" "On machines with OpenBoot, simply enter the boot monitor on the machine " "which is being installed (see ). Use " "the command boot net to boot from a TFTP and RARP " "server, or try boot net:bootp or boot net:" "dhcp to boot from a TFTP and BOOTP or DHCP server. You can pass " "extra boot parameters to &d-i; at the end of the boot " "command." msgstr "" "在有 OpenBoot 的机器上,直接进入安装机器引导监视器(参阅 )。使用命令 boot net 从一个 " "TFTP 和 RARP 服务器上引导,或者用 boot net:bootp 或 " "boot net:dhcp 从一个 TFTP 和 BOOTP 或 DHCP 服务器上引" "导。您可以在 boot 命令后面传递额外的引导参数给 &d-" "i; 。" #. Tag: para #: boot-installer.xml:2139 #, no-c-format msgid "" "Most OpenBoot versions support the boot cdrom 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 支持 boot cdrom 命令。它其实是" "从 ID 为 6 的 SCSI 设备进行引导的一个别名(对于 IDE 系统来说,它是第二个主硬" "盘)。" #. Tag: title #: boot-installer.xml:2148 #, no-c-format msgid "IDPROM Messages" msgstr "IDPROM 消息" #. Tag: para #: boot-installer.xml:2149 #, no-c-format msgid "" "If you cannot boot because you get messages about a problem with " "IDPROM, then it's possible that your NVRAM battery, which " "holds configuration information for you firmware, has run out. See the " "Sun NVRAM FAQ for more " "information." msgstr "" "如果您由于得到一个有关IDPROM问题的消息而不能引导,这可能是 " "NVRAM 电池已经用光。通常它为固件保持配置信息。请查阅 Sun NVRAM FAQ 以获得更多信息。" #. Tag: title #: boot-installer.xml:2168 #, no-c-format msgid "Accessibility" msgstr "辅助功能" #. Tag: para #: boot-installer.xml:2169 #, fuzzy, no-c-format #| msgid "" #| "Some users may need specific support because of e.g. some visual " #| "impairment. USB braille " #| "displays are detected automatically (not serial displays connected via a " #| "serial-to-USB converter), but most other Most accessibility features have to be " #| "enabled manually. On machines that support it, the " #| "boot menu emits a beep when it is ready to receive keystrokes. " #| "Some boot parameters can then be appended " #| "to enable accessibility features (see also ). Note that on most architectures the " #| "boot loader interprets your keyboard as a QWERTY keyboard." msgid "" "Some users may need specific support because of e.g. some visual impairment. " "USB braille displays are detected " "automatically (not serial displays connected via a serial-to-USB converter), " "but most other Most accessibility features have to be enabled manually. 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. Some boot parameters can then be appended to enable accessibility features (see also ). Note that " "on most architectures the boot loader interprets your keyboard as a QWERTY " "keyboard." msgstr "" "一些用户,比如有视觉障碍的,可能需要特别的支持。USB(不含通过串口 USB 转换口转换的) 盲文点字显示器(braille " "displays)可以自动检测到,但多数情况下其他的 多数情况下辅助功能不得不通过手动进行设置。" "在可以支持的机器上,可以接收输入的时候,引导菜单会哔一" "声。 一些引导参数可以 接着 被添加到后" "面打开这些辅助功能 (参阅 )。需要注意在大多数架构下 boot loader 将视您的键盘为 QWERTY 布局。" #. Tag: title #: boot-installer.xml:2189 #, no-c-format msgid "Installer front-end" msgstr "" #. Tag: para #: boot-installer.xml:2190 #, no-c-format msgid "" "The &debian; installer supports several front-ends for asking questions, " "with varying convenience for accessibility: notably, text uses plain text while newt uses text-based " "dialog boxes. The choice can be made at the boot prompt, see the " "documentation for DEBIAN_FRONTEND in ." msgstr "" #. Tag: title #: boot-installer.xml:2202 #, no-c-format msgid "USB Braille Displays" msgstr "USB 盲文点显器" #. Tag: para #: boot-installer.xml:2203 #, 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 brltty is started, you can choose a braille table by entering the " "preference menu. Documentation on key bindings for braille devices is " "available on the brltty website." msgstr "" "系统应该可以自动检测到 USB 盲文点显器。然后自动选取安装程序的文本界面,该设备" "也会被自动安装到最终系统中。您只需要在引导菜单中按下 &enterkey; 键。一旦 " "brltty 启动,您就可以通过菜单选择 braille table。在 " "brltty " "website 可以找到盲文点显器的键绑定文档。" #. Tag: title #: boot-installer.xml:2218 #, no-c-format msgid "Serial Braille Displays" msgstr "串口盲文点显器" #. Tag: para #: boot-installer.xml:2219 #, fuzzy, 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 " #| "brltty=driver,port,table boot parameter " #| "to tell brltty which driver it should use. " #| "driver should be replaced by the two-letter " #| "driver code for your terminal (see the BRLTTY manual). port should be " #| "replaced by the name of the serial port the display is connected to, " #| "ttyS0 is the default, ttyUSB0 can be typically used when using a serial-to-USB converter. " #| "table is the name of the braille table to be " #| "used (see the BRLTTY manual); " #| "the English table is the default. Note that the table can be changed " #| "later by entering the preference menu. Documentation on key bindings for " #| "braille devices is available on the brltty website." msgid "" "Serial braille displays cannot safely be automatically detected (since that " "may damage some of them). You thus need to append the " "brltty=driver,port boot parameter to tell brltty which driver and port it should use. driver should be replaced by the two-letter driver code for your " "terminal (see the BRLTTY manual). " "port should be replaced by the name of the serial " "port the display is connected to, ttyS0 is the " "default, ttyUSB0 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 BRLTTY manual); 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 protocol=foo which is needed for some rare " "models. Documentation on key bindings for braille devices is available on " "the brltty " "website." msgstr "" "系统无法安全地检测到串口盲文点显器(因为这可能会导致某些损坏)。您需要添加 " "brltty=driver,port,table 引导参数指明 " "brltty 该使用哪个驱动程序。driver 应该替换为您终端的两个字母的驱动程序代码(参阅 BRLTTY manual). port 应该" "替换为该设备连接使用的串口名,默认为 ttyS0 ,如果通过" "串口转 USB 转接应使用 ttyUSB0table 是使用的 braille table 名 (参阅 BRLTTY manual); 默认为英语。注意该表可以在后续菜单中选择修改。该设" "备的键绑定文档可以在 brltty website 找到。" #. Tag: title #: boot-installer.xml:2246 boot-installer.xml:3291 #, no-c-format msgid "Software Speech Synthesis" msgstr "软件语音合成(Software Speech Synthesis)" #. Tag: para #: boot-installer.xml:2247 #, fuzzy, no-c-format #| msgid "" #| "Support for hardware speech synthesis devices is available only alongside " #| "support for graphical installer. You thus need to select a " #| "Graphical install entry in the boot menu." 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 s &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 "" "对于硬件语音合成设备的支持只在图形界面安装程序下有效。您需要在引导菜单里面选" "择 Graphical install 项。" #. Tag: para #: boot-installer.xml:2256 #, fuzzy, no-c-format #| msgid "" #| "Support for software speech synthesis can be activated by selecting it in " #| "the boot menu by typing s &enterkey;. The first " #| "question (language) is spoken in english, and the remainder of " #| "installation is spoken in the selected language (if available in " #| "espeak)." msgid "" "The first question (language) is spoken in english, and the remainder of " "installation is spoken in the selected language (if available in " "espeak)." msgstr "" "要支持软件语音合成,可以在引导菜单键入 s &enterkey; 激" "活。第一个问题(语言)使用英语发音,其余的问题则根据所选的语言来发音(如果存在 " "espeak)。" #. Tag: para #: boot-installer.xml:2262 #, no-c-format msgid "" "The default speech rate is quite slow. To make it faster, press " "CapsLock6. To make it " "slower, press CapsLock5. The default volume should be medium. To make it louder, press " "CapsLock2. To make it " "quieter, press CapsLock1. To get more details on the browsing shortcuts, see the Speakup guide. To just accept the default " "answer for a question, simply press Enter at the prompt. To " "provide an empty answer for a question, type ! at the " "prompt. To get back to the previous question, type < at the prompt." msgstr "" #. Tag: title #: boot-installer.xml:2290 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "硬件语音合成(Hardware Speech Synthesis)" #. Tag: para #: boot-installer.xml:2291 #, fuzzy, no-c-format #| msgid "" #| "Support for hardware speech synthesis devices is available only alongside " #| "support for graphical installer. You thus need to select a " #| "Graphical install entry in the boot menu." 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 " "Graphical install entry in the boot menu." msgstr "" "对于硬件语音合成设备的支持只在图形界面安装程序下有效。您需要在引导菜单里面选" "择 Graphical install 项。" #. Tag: para #: boot-installer.xml:2298 #, no-c-format msgid "" "Hardware speech synthesis devices cannot be automatically detected. You thus " "need to append the speakup.synth=driver boot parameter to tell speakup which driver it should use. driver " "should be replaced by the driver code for your device (see driver code list). 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 "" "硬件语音合成设备无法自动识别。您需要添加 speakup." "synth=driver 引导参数告诉 " "speakup 使用哪种驱动程序。driver 应替换为该设备的驱动程序代码(参阅 driver code list)。接着安装程序的文本界面自动被选中,对于语" "音合成设备的支持也会被自动安装到最终系统里面。" #. Tag: title #: boot-installer.xml:2313 #, no-c-format msgid "Board Devices" msgstr "板卡设备" #. Tag: para #: boot-installer.xml:2314 #, 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 vga=normal fb=false boot " "parameter. This will however reduce the number of available languages." msgstr "" "一些辅助设备实际上是插入计算机里面的板卡,它们直接从显存里面读取字符。要让它" "们工作,需要使用引导参数 vga=normal " "fb=false 禁止使用 framebuffer。然而这会减少可用语言的" "数量。" #. Tag: para #: boot-installer.xml:2322 #, no-c-format msgid "" "If desired a textual version of the bootloader can be activated before " "adding the boot parameter by typing h &enterkey;." msgstr "" "假如希望使用字符界面的 bootloader,可以在添加引导参数前输入 h &enterkey;。" #. Tag: title #: boot-installer.xml:2330 #, no-c-format msgid "High-Contrast Theme" msgstr "高亮主题" #. Tag: para #: boot-installer.xml:2331 #, fuzzy, no-c-format #| msgid "" #| "For users with low vision, the installer can use a high-contrast theme " #| "that makes it more readable. To enable it, append the " #| "theme=dark boot parameter." msgid "" "For users with low vision, the installer can use a high-contrast color theme " "that makes it more readable. To enable it, append the theme=dark boot parameter." msgstr "" "对于视力弱的用户,安装程序可以使用高亮主题增加可读性。打开它,设置 " "theme=dark 引导参数即可。" #. Tag: title #: boot-installer.xml:2340 #, no-c-format msgid "Zoom" msgstr "" #. Tag: para #: boot-installer.xml:2341 #, no-c-format msgid "" "For users with low vision, the graphical installer has a very basic zoom " "support: the Control + and Control - shortcuts increase and decrease the font size." msgstr "" #. Tag: title #: boot-installer.xml:2351 #, no-c-format msgid "Expert install, rescue mode, automated install" msgstr "" #. Tag: para #: boot-installer.xml:2352 #, 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 " "Advanced options submenu from the boot menu by typing " "a. When using a BIOS system (the boot menu will have " "beeped only once), this has to be followed by &enterkey;. Then, to enable " "speech synthesis, s can optionally be pressed " "(followed again by &enterkey; when using a BIOS system). From there, various " "shortcuts can be used: x for expert installation, " "r for rescue mode, or a for " "automated installation. When using a BIOS system, they must be followed by " "&enterkey;." msgstr "" #. Tag: para #: boot-installer.xml:2366 #, fuzzy, no-c-format #| msgid "" #| "Alternatively, &debian; can be installed completely automatically by " #| "using preseeding. This is documented in ." 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 ." msgstr "" "另外,&debian; 可以使用预置进行完全自动安装。相关文档参见 。" #. Tag: title #: boot-installer.xml:2376 #, no-c-format msgid "Accessibility of the installed system" msgstr "" #. Tag: para #: boot-installer.xml:2377 #, no-c-format msgid "" "Documentation on accessibility of the installed system is available on the " "Debian Accessibility wiki " "page." msgstr "" # index.docbook:1943, index.docbook:2477 #. Tag: title #: boot-installer.xml:2391 #, no-c-format msgid "Boot Parameters" msgstr "引导参数" #. Tag: para #: boot-installer.xml:2392 #, 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:2399 #, 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:2406 #, no-c-format msgid "" "Information on many boot parameters can be found in the Linux BootPrompt HOWTO, " "including tips for obscure hardware. This section contains only a sketch of " "the most salient parameters. Some common gotchas are included below in ." msgstr "" "有关很多引导参数的信息可以查看 Linux BootPrompt HOWTO,其中包括一些老旧硬件" "的解决方法。这一节只描述一些最常用的基本参数。一些常见的问题描述见 。" #. Tag: title #: boot-installer.xml:2418 #, no-c-format msgid "Boot console" msgstr "" #. Tag: para #: boot-installer.xml:2420 #, no-c-format 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 console=device argument to the kernel, where device " "is your serial device, which is usually something like ttyS0." msgstr "" "假如您用串口控制台引导,通常内核可以自动检测到。如果在串口引导的计算机上有视" "频卡(framebuffer)和键盘,您必须传递 console=device 参数给内核,其中 device " "是串口设备,通常是 ttyS0 形式。" #. Tag: para #: boot-installer.xml:2432 #, no-c-format msgid "" "You may need to specify parameters for the serial port, such as speed and " "parity, for instance console=ttyS0,9600n8; other " "typical speeds may be 57600 or 115200. Be sure to specify this option after " "---, 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:2440 #, fuzzy, no-c-format #| msgid "" #| "In order to ensure the terminal type used by the installer matches your " #| "terminal emulator, the parameter TERM=type can be added. Note that the installer only " #| "supports the following terminal types: linux, " #| "bterm, ansi, vt102 and dumb. The default for serial console in " #| "&d-i; is vt102. If you are using a virtualization " #| "tool which does not provide conversion into such terminals types itself, " #| "e.g. QEMU/KVM, you can start it inside a screen " #| "session. That will indeed perform translation into the screen terminal type, which is very close to vt102." msgid "" "In order to ensure the terminal type used by the installer matches your " "terminal emulator, the parameter TERM=type can be added. Note that the installer only supports " "the following terminal types: linux, bterm, ansi, vt102 and " "dumb. The default for serial console in &d-i; is " "vt102. 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 screen session. That will indeed perform translation into the " "screen terminal type, which is very close to " "vt102." msgstr "" "为了确保安装程序使用的终端类型与您的终端模拟程序匹配,可以添加一个 " "TERM=type 参数。注意,安装" "程序仅支持下列终端类型: linuxbterm、" "ansivt102dumb。 &d-i; 中默认的串口控制台终端类型是 vt102。" "如果您使用的虚拟工具,比如 QEMU/KVM,不支持转换成这些终端类型,您可以从一个 " "screen 会话中启动。这会将其转换成 screen 终端类型,而它又非常接近于 vt102 类型。" #. Tag: para #: boot-installer.xml:2456 #, no-c-format msgid "" "For &arch-title; the serial devices are ttya or " "ttyb. Alternatively, set the input-device and output-device OpenPROM variables to " "ttya." msgstr "" "对于 &arch-title; 串口设备名称是 ttya 或 " "ttyb 。或者,通过设置input-device 和 " "output-device OpenPROM 变量至 ttya。" #. Tag: title #: boot-installer.xml:2468 #, no-c-format msgid "&debian; Installer Parameters" msgstr "&debian; 安装程序的参数" #. Tag: para #: boot-installer.xml:2469 #, no-c-format msgid "" "The installation system recognizes a few additional boot " "parameters 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. which may be useful." msgstr "" "安装系统能识别一些额外的引导参数 当前的内核(2.6.9 或更新)," "您可以使用 32 个命令行参数和 32 个环境变量选项。如果超出,内核将会崩溃。 ,它们很有用。" #. Tag: para #: boot-installer.xml:2482 #, no-c-format msgid "" "A number of parameters have a short form 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:2494 #, no-c-format msgid "debconf/priority (priority)" msgstr "debconf/priority (priority)" #. Tag: para #: boot-installer.xml:2495 #, no-c-format msgid "This parameter sets the lowest priority of messages to be displayed." msgstr "这些参数设置将设置显示的信息为最低的级别。" #. Tag: para #: boot-installer.xml:2499 #, no-c-format msgid "" "The default installation uses priority=high. 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 "" "缺省安装使用 priority=high 。这意味着高优先级的和至关" "重要的信息将被显示,但是中级和低级信息将被跳过。如果其间出现了问题,安装程序" "将按照要求调整优先级别。" #. Tag: para #: boot-installer.xml:2506 #, no-c-format msgid "" "If you add priority=medium as boot parameter, you " "will be shown the installation menu and gain more control over the " "installation. When priority=low is used, all messages " "are shown (this is equivalent to the expert boot " "method). With priority=critical, the installation " "system will display only critical messages and try to do the right thing " "without fuss." msgstr "" "如果您加入 priority=medium 作为引导参数,将看到安装菜" "单以及安装过程中更多的控制。当使用 priority=low,将显" "示所有的消息(这相当于采用 expert 引导方法)。通过 " "priority=critical,安装系统只会显示至关重要的信息,并" "且尝试正确无误地执行各项事宜。" #. Tag: term #: boot-installer.xml:2520 #, no-c-format msgid "DEBIAN_FRONTEND" msgstr "DEBIAN_FRONTEND" #. Tag: para #: boot-installer.xml:2521 #, no-c-format msgid "" "This boot parameter controls the type of user interface used for the " "installer. The current possible parameter settings are: " " DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text " "DEBIAN_FRONTEND=newt DEBIAN_FRONTEND=gtk " " The default frontend is " "DEBIAN_FRONTEND=newt. " "DEBIAN_FRONTEND=text may be preferable for serial " "console installs. Some specialized types of install media may only offer a " "limited selection of frontends, but the newt and " "text frontends are available on most default install " "media. On architectures that support it, the graphical installer uses the " "gtk frontend." msgstr "" "这个引导参数控制用于安装程序的用户界面的类型。当前可能参数设置有:" " DEBIAN_FRONTEND=noninteractive " "DEBIAN_FRONTEND=text DEBIAN_FRONTEND=newt " " DEBIAN_FRONTEND=gtk 缺省的前端是 " "DEBIAN_FRONTEND=newt。 " "DEBIAN_FRONTEND=text 可以用于串口控制台的安装。一些特" "殊类型的安装介质可能只含有限的几个前端,但是 newt 和 " "text 在多少安装介质上都是默认采用。图形安装程序可以在" "所支持的平台上使用 gtk 前端。" #. Tag: term #: boot-installer.xml:2552 #, no-c-format msgid "BOOT_DEBUG" msgstr "BOOT_DEBUG" #. Tag: para #: boot-installer.xml:2553 #, 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 会在引导过程的特定位置调出 " "debug shell。(退出 shell 以后会继续引导过程。)" #. Tag: userinput #: boot-installer.xml:2562 #, no-c-format msgid "BOOT_DEBUG=0" msgstr "BOOT_DEBUG=0" #. Tag: para #: boot-installer.xml:2563 #, no-c-format msgid "This is the default." msgstr "此为默认。" #. Tag: userinput #: boot-installer.xml:2567 #, no-c-format msgid "BOOT_DEBUG=1" msgstr "BOOT_DEBUG=1" #. Tag: para #: boot-installer.xml:2568 #, no-c-format msgid "More verbose than usual." msgstr "更多的信息。" #. Tag: userinput #: boot-installer.xml:2572 #, no-c-format msgid "BOOT_DEBUG=2" msgstr "BOOT_DEBUG=2" #. Tag: para #: boot-installer.xml:2573 #, no-c-format msgid "Lots of debugging information." msgstr "大量的调试信息。" #. Tag: userinput #: boot-installer.xml:2577 #, no-c-format msgid "BOOT_DEBUG=3" msgstr "BOOT_DEBUG=3" #. Tag: para #: boot-installer.xml:2578 #, 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 "" "在引导过程中,安装程序将在多处不同地方运行 Shell,以进行细节上的调试。退出 " "Shell 将继续引导过程。" #. Tag: term #: boot-installer.xml:2592 #, no-c-format msgid "INSTALL_MEDIA_DEV" msgstr "INSTALL_MEDIA_DEV" #. Tag: para #: boot-installer.xml:2593 #, no-c-format msgid "" "The value of the parameter is the path to the device to load the &debian; " "installer from. For example, INSTALL_MEDIA_DEV=/dev/floppy/0" msgstr "" "参数的值是装入 &debian; 安装程序的设备路径,例如:" "INSTALL_MEDIA_DEV=/dev/floppy/0" #. Tag: para #: boot-installer.xml:2599 #, 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 "" "引导软盘通常会扫描所有的软盘来找到根软盘,可以通过此参数设置只查找一个设备。" #. Tag: term #: boot-installer.xml:2610 #, no-c-format msgid "log_host" msgstr "log_host" #. Tag: term #: boot-installer.xml:2611 #, no-c-format msgid "log_port" msgstr "log_port" #. Tag: para #: boot-installer.xml:2612 #, 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 "" "使得安装程序可以在本地记录同时发送日志到指定主机和端口的远端 syslog。如果不指" "定,默认端口是 syslog 标准端口 514。" #. Tag: term #: boot-installer.xml:2623 #, no-c-format msgid "lowmem" msgstr "lowmem" #. Tag: para #: boot-installer.xml:2624 #, 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 ." msgstr "" "可以强制安装程序设置高于安装程序根据实际内存默认的 lomem 等级。该值可设为 1 " "和 2。参阅 。" #. Tag: term #: boot-installer.xml:2634 #, no-c-format msgid "noshell" msgstr "noshell" #. Tag: para #: boot-installer.xml:2635 #, 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 "" "禁止 tty2 和 tty3 上的交互式安装。这对于物理安全限制下的无人职守安装很有用" "处。" #. Tag: term #: boot-installer.xml:2644 #, no-c-format msgid "debian-installer/framebuffer (fb)" msgstr "debian-installer/framebuffer (fb)" #. Tag: para #: boot-installer.xml:2645 #, 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 vga=normal fb=false. 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 使您的系" "统出现问题,可以通过参数 vga=normal " "fb=false 关闭这个特性。这类问题的特征是 bterm 或者 " "bogl 的相关错误信息、一个空白的屏幕,或者在开始安装几分钟后停止。" #. Tag: para #: boot-installer.xml:2654 #, no-c-format msgid "Such problems have been reported on hppa." msgstr "在 hppa 上面报告过存在这些问题。" #. Tag: para #: boot-installer.xml:2658 #, no-c-format msgid "" "Because of display problems on some systems, framebuffer support is " "disabled by default 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 debian-installer/" "framebuffer=true or fb=true for short." msgstr "" "由于某些系统上显示有问题,framebuffer 的支持在 &arch-title; 上默认" "是禁止的。这让能良好支持 framebuffer 的系统显示得很丑陋,比如那些" "采用 ATI 图形卡的系统。如果您在安装程序中遇到显示问题,可以试着在引导时使用参" "数 debian-installer/framebuffer=true 或简写为 " "fb=true。" #. Tag: term #: boot-installer.xml:2672 #, no-c-format msgid "debian-installer/theme (theme)" msgstr "debian-installer/theme (theme)" #. Tag: para #: boot-installer.xml:2673 #, 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 dark theme that was " "designed for visually impaired users. Set the theme by booting with " "theme=dark." msgstr "" "界面方案(theme)决定安装程序用户界面的外观(颜色、图标等)。不同的前端(frontend)" "有不同的界面方案。当前 newt 和 gtk 前端只有一个 dark 界面方案" "提供给视觉受损的用户。界面方案可以在引导的时候通过 " "theme=dark 设置。" #. Tag: term #: boot-installer.xml:2685 boot-installer.xml:2918 #, no-c-format msgid "netcfg/disable_autoconfig" msgstr "netcfg/disable_autoconfig" #. Tag: para #: boot-installer.xml:2686 #, 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:2693 #, 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 " #| "netcfg/disable_autoconfig=true 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 netcfg/disable_autoconfig=true to prevent " "any automatic configuration of the network (neither v4 nor v6) and to enter " "the information manually." msgstr "" "如果您的网络上面具备一台 DHCP 服务器,但是不想使用它,比如,因为它给出错误的" "答案。您可以使用参数 netcfg/disable_autoconfig=true 来" "阻止通过 DHCP 配置网络,并手工输入信息。" #. Tag: term #: boot-installer.xml:2704 #, no-c-format msgid "hw-detect/start_pcmcia" msgstr "hw-detect/start_pcmcia" #. Tag: para #: boot-installer.xml:2705 #, no-c-format msgid "" "Set to false to prevent starting PCMCIA services, if " "that causes problems. Some laptops are well known for this misbehavior." msgstr "" "设置成 false 来阻止启动 PCMCIA 服务造成的麻烦。有些便" "携机会有这种现象。" #. Tag: term #: boot-installer.xml:2715 #, no-c-format msgid "disk-detect/dmraid/enable (dmraid)" msgstr "disk-detect/dmraid/enable (dmraid)" #. Tag: para #: boot-installer.xml:2716 #, no-c-format msgid "" "Set to true 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 &debian; Installer Wiki." msgstr "" "设为 true 可以打开安装程序中对 Serial ATA RAID (也称" "为 ATA RAID、BIOS RAID 或 fake RAID)磁盘的支持。注意,这种支持当前是实验性" "的。更多的信息可以在 &debian; Installer Wiki 找到。" #. Tag: term #: boot-installer.xml:2727 #, no-c-format msgid "preseed/url (url)" msgstr "preseed/url (url)" #. Tag: para #: boot-installer.xml:2728 #, no-c-format msgid "" "Specify the url to a preconfiguration file to download and use for " "automating the install. See ." msgstr "" "指定 url 到预设文件,在安装中自动下载和使用。参阅 。" #. Tag: term #: boot-installer.xml:2737 #, no-c-format msgid "preseed/file (file)" msgstr "preseed/file (file)" #. Tag: para #: boot-installer.xml:2738 #, no-c-format msgid "" "Specify the path to a preconfiguration file to load for automating the " "install. See ." msgstr "" "指定路径至预设文件,加载自动化安装。参阅 。" #. Tag: term #: boot-installer.xml:2747 #, no-c-format msgid "preseed/interactive" msgstr "preseed/interactive" #. Tag: para #: boot-installer.xml:2748 #, no-c-format msgid "" "Set to true 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 for details." msgstr "" "设为 true,让已经预置的也可以显示提问。用于测试和调试" "预置的文件。注意,使用引导参数进行预置时无效,但可以使用一种特殊的语法。参阅 " " 了解详细信息。" #. Tag: term #: boot-installer.xml:2760 #, no-c-format msgid "auto-install/enable (auto)" msgstr "auto-install/enable (auto)" #. Tag: para #: boot-installer.xml:2761 #, no-c-format msgid "" "Delay questions that are normally asked before preseeding is possible until " "after the network is configured. See for " "details about using this to automate installs." msgstr "" "延迟那些通常在预置之前的提问,直到网络设置完毕。参阅 了解自动安装的详细信息。" #. Tag: term #: boot-installer.xml:2772 #, no-c-format msgid "finish-install/keep-consoles" msgstr "finish-install/keep-consoles" #. Tag: para #: boot-installer.xml:2773 #, no-c-format msgid "" "During installations from serial or management console, the regular virtual " "consoles (VT1 to VT6) are normally disabled in /etc/inittab. Set to true to prevent this." msgstr "" "从串口或者管理控制台安装时,虚拟控制台(VT1 到 VT6)一般在 /etc/" "inittab 里已经关掉。将其改为 true 打开。" #. Tag: term #: boot-installer.xml:2784 #, no-c-format msgid "cdrom-detect/eject" msgstr "cdrom-detect/eject" #. Tag: para #: boot-installer.xml:2785 #, 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; 默认自动弹出安装时的光学媒介。如果系统不是自动从 CD 引导,这" "是不必要的操作。在某些情况下,反而不便。例如,如果光驱不能自动插入盘片,用户" "又不在旁边操作。许多 slot loading、slim-line 和 caddy 类型的驱动器不能自动重" "新加载介质。" #. Tag: para #: boot-installer.xml:2794 #, no-c-format msgid "" "Set to false 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 "" "设为 false 可以禁止自动弹出,但要小心确保系统在安装完" "后,不会自动从光盘引导。" #. Tag: term #: boot-installer.xml:2805 #, no-c-format msgid "base-installer/install-recommends (recommends)" msgstr "base-installer/install-recommends (recommends)" #. Tag: para #: boot-installer.xml:2806 #, no-c-format msgid "" "By setting this option to false, the package " "management system will be configured to not automatically install " "Recommends, both during the installation and for the " "installed system. See also ." msgstr "" "通过设置 false 选项,在安装过程和以后的系统中,包管理" "系统将配置设为不自动安装这些推荐的软件包(Recommends)。参阅 " "。" #. Tag: para #: boot-installer.xml:2813 #, 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:2825 #, no-c-format msgid "debian-installer/allow_unauthenticated" msgstr "debian-installer/allow_unauthenticated" #. Tag: para #: boot-installer.xml:2826 #, no-c-format msgid "" "By default the installer requires that repositories be authenticated using a " "known gpg key. Set to true to disable that " "authentication. Warning: insecure, not recommended." msgstr "" "安装程序默认需要使用一个已知的 gpg 密钥认证仓库。设为 true 可以禁止认证。警告:不安全,不推荐使用。" #. Tag: term #: boot-installer.xml:2837 #, no-c-format msgid "ramdisk_size" msgstr "ramdisk_size" #. Tag: para #: boot-installer.xml:2838 #, 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 "" "该参数应设置为所需的正确值;它只在您看到 ramdisk 无法正确完成加载的错误时才设" "置。该值的单位是 kB。" #. Tag: term #: boot-installer.xml:2848 #, no-c-format msgid "rescue/enable" msgstr "rescue/enable" #. Tag: para #: boot-installer.xml:2849 #, no-c-format msgid "" "Set to true to enter rescue mode rather than " "performing a normal installation. See ." msgstr "" "设为 true 进入 rescue 模式,而不是执行普通安装。参阅 " "。" #. Tag: title #: boot-installer.xml:2862 #, no-c-format msgid "Using boot parameters to answer questions" msgstr "使用内核模块参数回答提问" #. Tag: para #: boot-installer.xml:2863 #, 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 . Some specific examples are listed below." msgstr "" "对于一些例外,可以在引导提示符后设置值来回答安装过程中的提问,在某些情况下," "它是惟一真正有效的。有关如何操作的说明可以在 找到。下面是一些具体的例子。" #. Tag: term #: boot-installer.xml:2875 #, no-c-format msgid "debian-installer/language (language)" msgstr "debian-installer/language (language)" #. Tag: term #: boot-installer.xml:2876 #, no-c-format msgid "debian-installer/country (country)" msgstr "debian-installer/country (country)" #. Tag: term #: boot-installer.xml:2877 #, no-c-format msgid "debian-installer/locale (locale)" msgstr "debian-installer/locale (locale)" #. Tag: para #: boot-installer.xml:2878 #, 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 "" "有两种方法可以指定安装过程和安装后系统中所使用的语言(language)、国家(country)" "和地方(locale)。" #. Tag: para #: boot-installer.xml:2883 #, no-c-format msgid "" "The first and easiest is to pass only the parameter locale. Language and country will then be derived from its value. You can " "for example use locale=de_CH to select German as " "language and Switzerland as country (de_CH.UTF-8 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 "" "第一种和最简单的方法为只设置 locale 参数。语言和国家将依据" "该值产生。例如,您可以使用 locale=de_CH 选择语言为德" "语,瑞士为国家(安装后的系统中默认的 locale 将设置为 de_CH.UTF-8 )。该方法有一个缺陷,因为并不是所有的语言、国家和地方可以采用这种方" "式组合。" #. Tag: para #: boot-installer.xml:2892 #, no-c-format msgid "" "The second, more flexible option is to specify language " "and country separately. In this case locale can optionally be added to specify a specific default locale for " "the installed system. Example: language=en country=DE " "locale=en_GB.UTF-8." msgstr "" "第二种更具弹性的方法,是分开指定 language 和 " "country。这种方式下 locale 可以作为选项" "来指定安装后系统中默认的 locale 值。例如: language=en country=DE " "locale=en_GB.UTF-8。" #. Tag: term #: boot-installer.xml:2904 #, no-c-format msgid "anna/choose_modules (modules)" msgstr "anna/choose_modules (modules)" #. Tag: para #: boot-installer.xml:2905 #, 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 " "openssh-client-udeb (so you can use scp during the installation) and " "ppp-udeb (see )." msgstr "" "可用来自动加载那些默认不加载的安装程序模块。比如一些有用的可选模块 " "openssh-client-udeb (使您可以在安装过程中使用 " "scp) ppp-udeb (参阅 )。" #. Tag: para #: boot-installer.xml:2919 #, fuzzy, no-c-format #| msgid "" #| "Set to true if you want to disable DHCP and " #| "instead force static network configuration." msgid "" "Set to true if you want to disable IPv6 " "autoconfiguration and DHCP and instead force static network configuration." msgstr "" "如果您想禁止 DHCP 使用静态网络设置,将它设为 true。" #. Tag: term #: boot-installer.xml:2928 #, no-c-format msgid "mirror/protocol (protocol)" msgstr "mirror/protocol (protocol)" #. Tag: para #: boot-installer.xml:2929 #, 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 " "ftp, 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 "" "默认情况下,安装程序会使用 http 协议从 &debian; 镜像下载文件,在普通优先级下" "不能修改协议为 ftp。设置该参数为 ftp,您可以强制安装程" "序使用该协议。注意,必须手动输入主机名,而不是从列表中选择 ftp 镜像。" #. Tag: term #: boot-installer.xml:2942 #, no-c-format msgid "tasksel:tasksel/first (tasks)" msgstr "tasksel:tasksel/first (tasks)" #. Tag: para #: boot-installer.xml:2943 #, no-c-format msgid "" "Can be used to select tasks that are not available from the interactive task " "list, such as the kde-desktop task. See for additional information." msgstr "" "可以用来选择不在交互式任务列表中出现的任务,例如 kde-desktop 任务。参阅 了解详细信息。" #. Tag: title #: boot-installer.xml:2957 #, no-c-format msgid "Passing parameters to kernel modules" msgstr "给内核模块传递参数" #. Tag: para #: boot-installer.xml:2958 #, 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:2971 #, 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:2978 #, no-c-format msgid "" "The syntax to use to set parameters for modules is: " "\n" "module_name.parameter_name=value\n" " 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 "" "设置模块参数的语法为:\n" "module_name.parameter_name=value\n" " 如果您需要传递多个参数给相同或不同的模块,重复上" "面内容即可。例如,设置老式的 3Com 网卡要使用 BNC (coax) 端子和 IRQ 10,要使" "用:" #. Tag: screen #: boot-installer.xml:2988 #, no-c-format msgid "3c509.xcvr=3 3c509.irq=10" msgstr "3c509.xcvr=3 3c509.irq=10" #. Tag: title #: boot-installer.xml:2994 #, no-c-format msgid "Blacklisting kernel modules" msgstr "内核模块黑名单" #. Tag: para #: boot-installer.xml:2995 #, 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 "" "有时需要将一个模块加入黑名单阻止内核和 udev 自动加载。其中一个原因是有的模块" "会与您的硬件产生问题。内核有时会给同一硬件列出两个不同的驱动程序。如果驱动之" "间冲突或者错误的驱动先加载,将造成设备无法正常工作。" #. Tag: para #: boot-installer.xml:3004 #, no-c-format msgid "" "You can blacklist a module using the following syntax: " "module_name.blacklist=yes. " "This will cause the module to be blacklisted in /etc/modprobe.d/" "blacklist.local both during the installation and for the " "installed system." msgstr "" "您可以使用下面的语法将模块加入黑名单:module_name.blacklist=yes。这会让该模块在安装和安装后的系统都加" "入 /etc/modprobe.d/blacklist.local 文件的黑名单中。" #. Tag: para #: boot-installer.xml:3012 #, 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 "" "注意,安装系统自己仍然会加载模块。要阻止这种情况,您可以在 expert 模式下,硬" "件检查过程中从显示的模块列表中取消该模块。" #. Tag: title #: boot-installer.xml:3028 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "安装过程中的故障修复" #. Tag: title #: boot-installer.xml:3033 #, no-c-format msgid "CD-ROM Reliability" msgstr "CD-ROM 的可靠性" #. Tag: para #: boot-installer.xml:3034 #, 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 — even after booting " "successfully from CD-ROM — fail to recognize the CD-ROM or return " "errors while reading from it during the installation." msgstr "" "有时,特别是旧的 CD-ROM 驱动器,安装程序无法从 CD-ROM 引导。安装程序还可能 " "— 即使是从 CD-ROM 成功引导 — 无法识别 CD-ROM 或在安装时读取错误。" #. Tag: para #: boot-installer.xml:3041 #, 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:3047 #, no-c-format msgid "There are two very simple things that you should try first." msgstr "您首先应试试两种最简单的方法。" #. Tag: para #: boot-installer.xml:3052 #, no-c-format msgid "" "If the CD-ROM does not boot, check that it was inserted correctly and that " "it is not dirty." msgstr "如果 CD-ROM 没有引导,检查一下它是否放好,并且没有弄脏。" #. Tag: para #: boot-installer.xml:3058 #, no-c-format msgid "" "If the installer fails to recognize a CD-ROM, try just running the option " " Detect and mount CD-ROM a second time. Some DMA related issues with very old CD-ROM " "drives are known to be resolved in this way." msgstr "" "如果安装程序无法识别 CD-ROM,再次运行 Detect and " "mount CD-ROM 选项。有些非常老的 CD-ROM 驱动器 " "DMA 相关的问题可以用这种方法解决。" #. Tag: para #: boot-installer.xml:3068 #, 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 "" "如果还无法工作,试试下一节建议的方法。多数情况下,但非全部,那里的建议适用于 " "CD-ROM 和 DVD,为了方便,只提到 CD-ROM。" #. Tag: para #: boot-installer.xml:3074 #, 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 "如果您用 CD-ROM 无法安装,试试其他可用的安装方法。" #. Tag: title #: boot-installer.xml:3082 #, no-c-format msgid "Common issues" msgstr "常见问题" #. Tag: para #: boot-installer.xml:3085 #, 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 "有些老 CD-ROM 驱动器不能读取新 CD 刻录机的高速模式下刻录的光盘。" #. Tag: para #: boot-installer.xml:3102 #, no-c-format msgid "" "Some very old CD-ROM drives do not work correctly if direct memory " "access (DMA) is enabled for them." msgstr "" "一些非常老的 CD-ROM 驱动器在 direct memory access (DMA) 下无法" "正常工作。" #. Tag: title #: boot-installer.xml:3113 #, no-c-format msgid "How to investigate and maybe solve issues" msgstr "如何调查研究或许可以解决问题" #. Tag: para #: boot-installer.xml:3114 #, no-c-format msgid "If the CD-ROM fails to boot, try the suggestions listed below." msgstr "如果从 CD-ROM 引导失败,试试下面所列的建议。" #. Tag: para #: boot-installer.xml:3119 #, 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 "" "检查您的 BIOS 的确支持从 CD-ROM 启动(仅有个别非常老的系统不行),并且 BIOS 打" "开支持从 CD 引导。" #. Tag: para #: boot-installer.xml:3126 #, 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 MD5SUMS file that " "should be present in the same location as where you downloaded the image " "from. \n" "$ md5sum debian-testing-i386-netinst.iso\n" "a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst." "iso\n" " 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 "" "如果您下载的是 iso 映像,检查映像的 md5sum 是否与 MD5SUMS 文件所列相同,该文件和您下载的映像在同一个地方。" "\n" "$ md5sum debian-testing-i386-netinst.iso\n" "a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst." "iso\n" " 然后,检验所刻录 CD-ROM 的 md5sum 也匹配。可以使" "用下面的命令。它使用映像的尺寸从 CD-ROM 读取正确的字节数。" #. Tag: screen #: boot-installer.xml:3139 #, no-c-format msgid "" "$ dd if=/dev/cdrom | \\\n" "> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" "> 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" "> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" "> 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:3144 #, 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 "" "假如在安装程序正常的引导之后,无法识别 CD-ROM,有时只需再试一次就能解决问题。" "如果您有多个 CD-ROM 驱动器,将 CD-ROM 放到其他的驱动器。如果无法工作,或者可" "以识别 CD-ROM 但读取的时候有错误,试试下面所列的建议。这里需要一些基本的 " "&arch-kernel; 知识。要执行命令,您应该首先切换到第二虚拟控制台(VT2),并激活 " "shell。" #. Tag: para #: boot-installer.xml:3156 #, no-c-format msgid "" "Switch to VT4 or view the contents of /var/log/syslog " "(use nano as editor) to check for any specific error " "messages. After that, also check the output of dmesg." msgstr "" "切换到 VT4 或查看 /var/log/syslog 的内容(使用 " "nano 作为编辑器)来检查任何特定的错误信息。之后,再检查 " "dmesg 的输出。" #. Tag: para #: boot-installer.xml:3163 #, no-c-format msgid "" "Check in the output of dmesg if your CD-ROM drive was " "recognized. You should see something like (the lines do not necessarily have " "to be consecutive): \n" "Probing IDE interface ide1...\n" "hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" "ide1 at 0x170-0x177,0x376 on irq 15\n" "hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" "Uniform CD-ROM driver Revision: 3.20\n" " 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 modprobe." msgstr "" "如果您的 CD-ROM 驱动器可以识别,检查 dmesg 的输出。可以看" "到类似的信息(这些行不必是连续出现的):\n" "Probing IDE interface ide1...\n" "hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" "ide1 at 0x170-0x177,0x376 on irq 15\n" "hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" "Uniform CD-ROM driver Revision: 3.20\n" " 如果您看不到这些,估计是 CD-ROM 驱动器所连接的控" "制器无法被识别,或者完全不被支持。如果您知道控制器所需的驱动程序,可以使用 " "modprobe 手动加载。" #. Tag: para #: boot-installer.xml:3177 #, no-c-format msgid "" "Check that there is a device node for your CD-ROM drive under /dev/" ". In the example above, this would be /dev/hdc. There should also be a /dev/cdrom." msgstr "" "检查 /dev/ 下面您 CD-ROM 驱动器对应的设备节点。上面的例" "子中,它是 /dev/hdc。也会是 /dev/cdroms/" "cdrom0。" #. Tag: para #: boot-installer.xml:3185 #, no-c-format msgid "" "Use the mount command to check if the CD-ROM is already " "mounted; if not, try mounting it manually: \n" "$ mount /dev/hdc /cdrom\n" " Check if there are any error messages after that " "command." msgstr "" "用 mount 命令检查 the CD-ROM 是否已经挂载;如果没有,使用" "手动挂载:\n" "$ mount /dev/hdc /cdrom\n" " 检查命令后面是否有什么错误信息。" #. Tag: para #: boot-installer.xml:3195 #, no-c-format msgid "" "Check if DMA is currently enabled: \n" "$ cd /proc/ide/hdc\n" "$ grep using_dma settings\n" "using_dma 1 0 1 rw\n" " A 1 in the first column after " "using_dma means it is enabled. If it is, try disabling " "it: \n" "$ echo -n \"using_dma:0\" >settings\n" " Make sure that you are in the directory for the " "device that corresponds to your CD-ROM drive." msgstr "" "确认当前 DMA 已经打开:\n" "$ cd /proc/ide/hdc\n" "$ grep dma settings\n" "using_dma 1 0 1 rw\n" " using_dma 之后的第一列 " "1 意味着打开。如果是这样,将其关闭:" "\n" "$ echo -n \"using_dma:0\" >settings\n" " 确保您所处的目录对应 CD-ROM 驱动器。" #. Tag: para #: boot-installer.xml:3210 #, 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 "" "如果安装过程中有什么问题,用接近安装程序主菜单底部的选项检查 CD-ROM 的完整" "性。如果 CD-ROM 可以读,该选项可以对其进行测试。" #. Tag: title #: boot-installer.xml:3225 #, no-c-format msgid "Floppy Disk Reliability" msgstr "软盘的可靠性" #. Tag: para #: boot-installer.xml:3227 #, 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:3232 #, 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:3241 #, 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 different " "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 "" "如果在某个软盘上遇到安装停止,您首先要做的,是把映像重新写到另外一张软盘上,看看是否解决问题。仅格式化旧软盘是不够的,即使它重新格式" "化以后看起来没有错误。如果可能,在别的统上重写这些软盘更好一些。" #. Tag: para #: boot-installer.xml:3250 #, no-c-format msgid "" "One user reports he had to write the images to floppy three times before one worked, and then everything was fine with the " "third floppy." msgstr "" "有一个用户报告他不得不把映像往软盘写次,只有最后一次的" "软盘才算工作良好。" #. Tag: para #: boot-installer.xml:3256 #, 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 "" "一般情况下,您不必重新下载软盘映像,但如果一直有问题,可以通过它们的 md5sum " "来检验下载的映像是否正确。" #. Tag: para #: boot-installer.xml:3262 #, 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:3271 #, no-c-format msgid "Boot Configuration" msgstr "引导配置" #. Tag: para #: boot-installer.xml:3273 #, 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 " "." msgstr "" "如果在引导过程中您遇到了问题或者内核挂起,不识别实际拥有的外围设备,或者驱动" "不能被正确识别,首先要做的事情是检查引导参数,见 讨论。" #. Tag: para #: boot-installer.xml:3282 #, no-c-format msgid "" "In some cases, malfunctions can be caused by missing device firmware (see " " and )." msgstr "" "有些情况下,设备固件的丢失可能会造成故障 (参阅 )。" #. Tag: para #: boot-installer.xml:3293 #, 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 "" "如果软件语音合成不工作,最大可能是由声卡所致,通常要么是驱动没有被包含到安装" "程序,要么是不常见的合成器默认设置为静音。您可以提交一份 bug 报告,并包含同一" "台机器上声音可以正常工作的 Linux 系统上(比如,live CD),运行下面命令的输出。" #. Tag: userinput #: boot-installer.xml:3304 #, no-c-format msgid "dmesg" msgstr "dmesg" #. Tag: userinput #: boot-installer.xml:3306 #, no-c-format msgid "lspci" msgstr "lspci" #. Tag: userinput #: boot-installer.xml:3308 #, no-c-format msgid "lsmod" msgstr "lsmod" #. Tag: userinput #: boot-installer.xml:3310 #, no-c-format msgid "amixer" msgstr "amixer" #. Tag: title #: boot-installer.xml:3318 boot-installer.xml:3429 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "&arch-title; 常见安装问题" #. Tag: para #: boot-installer.xml:3319 #, 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:3370 #, 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 fb=false to disable the framebuffer console. Only a reduced set of " "languages will be available during the installation due to limited console " "features. See for details." msgstr "" "如果您的显示屏在内核引导的时候显示一个奇怪的图片(比如,纯白、纯黑或者彩色的像" "素块),系统可能含有一块有问题的显示卡。它不能切换至 framebuffer 模式。您可以" "使用引导参数 fb=false 来禁止使用 framebuffer 控制台。" "由于控制台的限制,在安装过程中只能使用少数的几种语言,参阅 来获得细节信息。" #. Tag: title #: boot-installer.xml:3384 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "在 PCMCIA 配置阶段系统停止" #. Tag: para #: boot-installer.xml:3385 #, no-c-format 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 hw-detect/start_pcmcia=false boot parameter. You " "can then configure PCMCIA after the installation is completed and exclude " "the resource range causing the problems." msgstr "" "一些非常老的 Dell 笔记本型号,会在 PCMCIA 设备检测程序尝试访问某些硬件地址的" "时候死机。其他笔记本可能显示类似的问题。如果您遇到那样的问题,并且在安装的时" "候不需要 PCMCIA 的支持,可以用 hw-detect/start_pcmcia=false 启动参数来取消 PCMCIA 功能。您可以在安装后配置 PCMCIA,去掉造成问" "题的资源区段。" #. Tag: para #: boot-installer.xml:3395 #, 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 " "exclude port 0x800-0x8ff here. There is also a list " "of some common resource range options in the System resource " "settings section of the PCMCIA HOWTO. Note that you have to omit the " "commas, if any, when you enter this value in the installer." msgstr "" "或者,可以启动安装程序时进入 expert 模式。您需要按照要求输入硬件资源范围选" "项。比如,如果有如上所说的 Dell 笔记本问题,应该在这里输入 " "exclude port 0x800-0x8ff。在 System " "resource settings section of the PCMCIA HOWTO 处列出了一些资源范围选" "项。注意您在安装程序中,输入这些值的时候必须忽略逗号。" #. Tag: para #: boot-installer.xml:3430 #, no-c-format msgid "There are some common installation problems that are worth mentioning." msgstr "有一些常见的安装问题值得解释一下。" #. Tag: title #: boot-installer.xml:3436 #, no-c-format msgid "Misdirected video output" msgstr "错误的视频输出" #. Tag: para #: boot-installer.xml:3437 #, 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: \n" "Remapping the kernel... done\n" "Booting Linux...\n" " 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 video=atyfb:off." msgstr "" "对于 &arch-title; ,一台机器有两个视频卡很常见,例如一个 ATI 卡和一个 Sun " "Creator 3D。有时,系统启动后,视频输出到错误的地方。典型的例子是,显示器只显" "示:\n" "Remapping the kernel... done\n" "Booting Linux...\n" " 要正常工作,您可以取下一块视频卡,或者在 " "OpenProm 引导阶段使用内核参数禁止一个。例如,禁止 ATI 卡,您应该使用 " "video=atyfb:off 启动安装程序。" #. Tag: para #: boot-installer.xml:3451 #, no-c-format msgid "" "Note that you may also have to manually add this parameter to the silo " "configuration (edit /target/etc/silo.conf before " "rebooting) and, if you installed X11, modify the video driver in /" "etc/X11/xorg.conf." msgstr "" "注意,您可能必需手动添加该参数到 silo 设置(重启前编辑 /target/etc/" "silo.conf),并且,如果您安装了 X11,还要修改 /etc/X11/" "xorg.conf 中的视频驱动。" #. Tag: title #: boot-installer.xml:3462 #, no-c-format msgid "Failure to Boot or Install from CD-ROM" msgstr "从 CD-ROM 上引导或安装失败" #. Tag: para #: boot-installer.xml:3463 #, 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 "" "一些 Sparc 系统出了名的难从 CD-ROM 启动,而且,即使启动,安装过程中也会有令人" "费解的错误。SunBlade 系统被报告了很多问题。" #. Tag: para #: boot-installer.xml:3469 #, no-c-format msgid "We recommend to install such systems by netbooting the installer." msgstr "我们建议从网络安装这些系统。" #. Tag: title #: boot-installer.xml:3478 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "内核起始信息注解" #. Tag: para #: boot-installer.xml:3480 #, no-c-format msgid "" "During the boot sequence, you may see many messages in the form " "can't find something, or something not " "present, can't initialize " "something, or even " "this driver release depends on something. 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 (see )." msgstr "" "在引导期间,您可以看到很多信息类似 can't find " "something,或者 " "something not presentcan't initialize something,或者甚至 this driver release " "depends on something。大多数这些" "信息都是无害的。之所以看到它们,是因为安装系统内核被设计成为可以运行在具有不" "同外围设备的计算机。显然,没有一个计算机可能拥有所有的外围设备,因此操作系统" "可能在查找一些您没有的设备上有一些报怨。您有时可以看到系统暂停了一段时间。这" "是由于它在等待一台设备的回应,但是这台设备并没有安装在系统上。如果您发现这个" "时间非常长,以后可以创建一个定制的内核(参见 )。" #. Tag: title #: boot-installer.xml:3505 #, no-c-format msgid "Reporting Installation Problems" msgstr "报告安装问题" #. Tag: para #: boot-installer.xml:3506 #, no-c-format msgid "" "If you get through the initial boot phase but cannot complete the install, " "the menu option Save debug logs 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 "" "如果您过了初始化引导阶段,但还是不能安装,可以借助于 Save debug " "logs 菜单选项。它让您保存安装程序的系统错误记录和配置信息到软" "盘,或者用网络浏览器下载。该信息或许提供了一些关于错误的起因和如何解决它的线" "索。如果您正在提交一个 bug 报告,可以报告里附上该信息。" #. Tag: para #: boot-installer.xml:3517 #, no-c-format msgid "" "Other pertinent installation messages may be found in /var/log/ during the installation, and /var/log/installer/ after the computer has been booted into the installed system." msgstr "" "其他安装期间相关的信息可以在 /var/log/ 内找到,计算机用" "新安装的系统启动后,放在 /var/log/debian-installer/ 里。" #. Tag: title #: boot-installer.xml:3528 #, no-c-format msgid "Submitting Installation Reports" msgstr "提交缺陷报告" #. Tag: para #: boot-installer.xml:3529 #, 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:3536 #, 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 "" "注意,您的安装包括将公布在 Debian Bug Tracking System (BTS) 并转发到公共的邮" "件列表。确保您使用的邮件地址可以被公开。" #. Tag: para #: boot-installer.xml:3542 #, fuzzy, no-c-format #| msgid "" #| "If you have a working &debian; system, the easiest way to send an " #| "installation report is to install the installation-report and reportbug packages " #| "(aptitude install installation-report reportbug), " #| "configure reportbug as explained in , and run the command reportbug installation-" #| "reports." msgid "" "If you have a working &debian; system, the easiest way to send an " "installation report is to install the installation-report and reportbug packages (apt " "install installation-report reportbug), configure " "reportbug as explained in , and run the command reportbug installation-reports." msgstr "" "如果您有一个可以运转的 &debian; 系统,发送安装报告最简单的方法是安装 " "installation-reportreportbug 软件包(aptitude install installation-report reportbug),配置 reportbug 的说明参阅 ,然后执行 reportbug installation-reports 命令。" #. Tag: para #: boot-installer.xml:3552 #, 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 " "installation-reports pseudo package, by sending it to " "submit@bugs.debian.org. \n" "Package: installation-reports\n" "\n" "Boot method: <How did you boot the installer? CD? floppy? network?>\n" "Image version: <Full URL to image you downloaded is best>\n" "Date: <Date and time of the install>\n" "\n" "Machine: <Description of machine (eg, IBM Thinkpad R32)>\n" "Processor:\n" "Memory:\n" "Partitions: <df -Tl will do; the raw partition table is preferred>\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" "<Description of the install, in prose, and any thoughts, comments\n" " and ideas you had during the initial install.>\n" " 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 "" "另外,您可以采用下列模板填写安装报告,并将它当作 installation-" "reports 虚拟软件包的 bug 报告,发送到 submit@bugs.debian." "org\n" "Package: installation-reports\n" "\n" "Boot method: <How did you boot the installer? CD? floppy? network?>\n" "Image version: <Full URL to image you downloaded is best>\n" "Date: <Date and time of the install>\n" "\n" "Machine: <Description of machine (eg, IBM Thinkpad R32)>\n" "Processor:\n" "Memory:\n" "Partitions: <df -Tl will do; the raw partition table is preferred>\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" "<Description of the install, in prose, and any thoughts, comments\n" " and ideas you had during the initial install.>\n" " 在 bug 报告中,请说明问题所在,包括内核挂起时最后" "见到的内核消息。描述进入问题状态所进行的步骤。" #~ msgid "Preseeding" #~ msgstr "预置" # index.docbook:1899, index.docbook:1946 #~ msgid "SGI TFTP Booting" #~ msgstr "SGI TFTP 引导" #~ msgid "" #~ "After entering the command monitor use \n" #~ "bootp():\n" #~ " 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 netaddr environment variable. Type " #~ "\n" #~ "unsetenv netaddr\n" #~ " in the command monitor to do this." #~ msgstr "" #~ "SGI 上引导 linux 要在进入命令监视器后使用 \n" #~ "bootp():\n" #~ " 来开始 &debian; 软件的安装。为了让它运行,您可" #~ "能必须取消 netaddr 环境变量的设置。通过命令监视器上输入 " #~ "\n" #~ "unsetenv netaddr\n" #~ " 可以达到此目的。" #~ msgid "" #~ "On SGI machines you can append boot parameters to the bootp(): command in the command monitor." #~ msgstr "" #~ "在 SGI 上您可以在命令监视器下给 bootp(): 命令附加一个引" #~ "导参数。" #~ msgid "" #~ "Following the bootp(): 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: \n" #~ "bootp():/boot/tftpboot.img\n" #~ " Further kernel parameters can be passed via " #~ "append:" #~ msgstr "" #~ "如果您没有通过 bootp/dhcp 服务器给出一个清楚的名字,接着 bootp():" #~ " 命令,您可以给出路径和文件名称来引导。例如 " #~ "\n" #~ "bootp():/boot/tftpboot.img\n" #~ " 更多的内核参数传递可以用 append:" #~ msgid "bootp(): append=\"root=/dev/sda1\"" #~ msgstr "bootp(): append=\"root=/dev/sda1\"" #~ msgid "" #~ "When the installer boots, you should be presented with a friendly " #~ "graphical screen showing the &debian; logo and a menu: " #~ "\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" #~ " Depending on the installation method you are " #~ "using, the Graphical install 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; 图标和菜单:" #~ "\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" #~ " 根据您使用的不同安装方法,Graphical " #~ "install 选项可能不会出现。双体系(bi-arch)映像会额外有一个 64 位安" #~ "装选项,在其下方,因此会有双倍的选项。" #~ msgid "Booting from CD-ROM" #~ msgstr "从 CD 光盘上引导" #~ msgid "" #~ "There is an increasing number of consumer devices that directly boot from " #~ "a flash chip on the device. The installer can be written to flash so it " #~ "will automatically start when you reboot your machines." #~ msgstr "" #~ "有越来越多的消费设备可以直接从设备上的闪存启动。安装程序可以被写入闪存,这" #~ "样当您重启机器的时候就能自动运行。" #~ msgid "" #~ "In many cases, changing the firmware of an embedded device voids your " #~ "warranty. Sometimes you are also not able to recover your device if there " #~ "are problems during the flashing process. Therefore, please take care and " #~ "follow the steps precisely." #~ msgstr "" #~ "多数情况下,修改嵌入设备的固件将使质保作废。有时如果稍有差错,您将无法复原" #~ "您的设备。所以要特别小心并精确地进行下面的步骤。" #~ msgid "Booting the SS4000-E" #~ msgstr "引导 SS4000-E" #~ msgid "" #~ "Due to limitations in the SS4000-E firmware, it unfortunately is not " #~ "possible to boot the installer without the use of a serial port at this " #~ "time. To boot the installer, you will need a serial nullmodem cable; a " #~ "computer with a serial port A USB " #~ "serial converter will also work. ; and a ribbon cable " #~ "with a male DB9 connector at one end, and a 10-pin .1\" IDC header at the " #~ "other This cable is often found in " #~ "older desktop machines with builtin 9-pin serial ports. ." #~ msgstr "" #~ "由于 SS4000-E 固件限制,当前除了使用串口还无法启动安装程序。为了启动安装程" #~ "序,您需要一条串口 nullmodem 线; 一台带有串口的计算机 USB 串口转换器也可以工作。 ; 以及一" #~ "端为公 DB9 口,另一端为 10-pin .1\" IDC 头的扁平电缆 这种电缆过去常用在桌面电脑内置的 9 针串口上。 。" #~ msgid "" #~ "To boot the SS4000-E, use your serial nullmodem cable and the ribbon " #~ "cable to connect to the serial port of the SS4000-E, and reboot the " #~ "machine. You need to use a serial terminal application to communicate " #~ "with the machine; a good option on a &debian; GNU/Linux is to use the " #~ "cu program, in the package of the same name. Assuming " #~ "the serial port on your computer is to be found on /dev/ttyS0, use the following command line:" #~ msgstr "" #~ "要启动 SS4000-E,请使用您的串行 nullmodem 线和 ribbon 线连接到 SS4000-E 的" #~ "串口,然后重新启动机器。您需要用一个串行终端程序与此机器通讯; &debian; " #~ "GNU/Linux 上可以使用 cu 程序,软件包和该程序同名。假设" #~ "您计算机上的串口是 /dev/ttyS0,请使用下列命令行:" #~ msgid "cu -lttyS0 -s115200" #~ msgstr "cu -lttyS0 -s115200" #~ msgid "" #~ "If using Windows, you may want to consider using the program " #~ "hyperterminal. Use a baud rate of 115200, 8 bits " #~ "word length, no stop bits, and one parity bit." #~ msgstr "" #~ "如果是在 Windows 下,您可以考虑使用 hyperterminal。" #~ "设置波特率为 115200、8 位字长、无停止位和一个奇偶校验位。" #~ msgid "When the machine boots, you will see the following line of output:" #~ msgstr "机器引导后,您可以看到下列输出内容:" #~ msgid "" #~ "No network interfaces found\n" #~ "\n" #~ "EM-7210 ver.T04 2005-12-12 (For ver.AA)\n" #~ "== Executing boot script in 1.000 seconds - enter ^C to abort" #~ msgstr "" #~ "No network interfaces found\n" #~ "\n" #~ "EM-7210 ver.T04 2005-12-12 (For ver.AA)\n" #~ "== Executing boot script in 1.000 seconds - enter ^C to abort" #~ msgid "" #~ "At this point, hit Control-C to interrupt the boot loader Note that you have only one second to do so; if " #~ "you miss this window, just powercycle the machine and try again. " #~ ". This will give you the RedBoot prompt. Enter the following " #~ "commands:" #~ msgstr "" #~ "此时,按下 Control-C 中断 boot loader " #~ " 注意,您只有一秒钟来选择;如果错过了,重新开机再试一次。 。接着出现 RedBoot 提示符,键入下面命令:" #~ msgid "" #~ "load -v -r -b 0x01800000 -m ymodem ramdisk.gz\n" #~ "load -v -r -b 0x01008000 -m ymodem zImage\n" #~ "exec -c \"console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000\" -r " #~ "0x01800000" #~ msgstr "" #~ "load -v -r -b 0x01800000 -m ymodem ramdisk.gz\n" #~ "load -v -r -b 0x01008000 -m ymodem zImage\n" #~ "exec -c \"console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000\" -r " #~ "0x01800000" #~ msgid "" #~ "After every load command, the system will expect a " #~ "file to be transmitted using the YMODEM protocol. When using cu, make " #~ "sure you have the package lrzsz installed, then " #~ "hit enter, followed by the ~< escape sequence to start " #~ "an external program, and run sb initrd.gz or " #~ "sb vmlinuz." #~ msgstr "" #~ "在每一个 load 命令后面,系统系统使用 YMODEM 协议传输文" #~ "件。如果使用的是 cu,确认您已经安装了 lrzsz 软件" #~ "包,然后键入回车,在 ~< 字符后面启动外部程序,然后运行 " #~ "sb initrd.gzsb vmlinuz。" #~ msgid "" #~ "Alternatively, it is possible to load the kernel and ramdisk using HTTP " #~ "rather than YMODEM. This is faster, but requires a working HTTP server on " #~ "the network. To do so, first switch the bootloader to RAM mode:" #~ msgstr "" #~ "另外一种方法,可以通过 HTTP 而不是 YMODEM 加载内核和 ramdisk。这会更快,但" #~ "要求网络内有一台 HTTP 服务器。做法是,首先将 bootloader 切换到 RAM 模式:" #~ msgid "" #~ "fis load rammode\n" #~ "g" #~ msgstr "" #~ "fis load rammode\n" #~ "g" #~ msgid "" #~ "This will seemingly restart the machine; but in reality, it loads redboot " #~ "to RAM and restarts it from there. Not doing this step will cause the " #~ "system to hang in the necessary ip_address step that comes next." #~ msgstr "" #~ "表面上看这在重新启动机器;但实际上是加载 redboot 到 RAM,让它来重新启动。" #~ "不进行这一步将导致系统在接下来需要 ip_address 时挂起。" #~ msgid "" #~ "You will need to hit Ctrl-C again to interrupt the boot. Then: " #~ "\n" #~ "ip_address -l 192.168.2.249 -h " #~ "192.168.2.4\n" #~ "load -v -r -b 0x01800000 -m http /initrd.gz\n" #~ "load -v -r -b 0x01008000 -m http /zImage\n" #~ "exec -c \"console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000\" -r " #~ "0x01800000\n" #~ " Where 192.168.2.249 is the IP address of the installed system and " #~ "192.168.2.4 the IP address of the HTTP server " #~ "containing the kernel and ramdisk files." #~ msgstr "" #~ "您需要再次按下 Ctrl-C 中断启动。然后: \n" #~ "ip_address -l 192.168.2.249 -h " #~ "192.168.2.4\n" #~ "load -v -r -b 0x01800000 -m http /initrd.gz\n" #~ "load -v -r -b 0x01008000 -m http /zImage\n" #~ "exec -c \"console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000\" -r " #~ "0x01800000\n" #~ " 其中 192.168.2.249 " #~ "是安装好系统的 IP 地址, 192.168.2.4 为含有内核" #~ "和 ramdisk 文件的 HTTP 服务器 IP 地址。" #~ msgid "The installer will now start as usual." #~ msgstr "安装程序将正常启动。" # index.docbook:1899, index.docbook:1946 #~ msgid "Cobalt TFTP Booting" #~ msgstr "Cobalt TFTP 引导" #~ msgid "" #~ "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to " #~ "install an NFS server and put the installer files in /nfsroot. When you boot your Cobalt, you have to press the left and the " #~ "right cursor buttons at the same time and the machine will boot via the " #~ "network from NFS. It will then display several options on the display. " #~ "There are the following two installation methods:" #~ msgstr "" #~ "严格地说,Cobalt 并不支持 NFS 启动。您需要安装 NFS 服务器并将安装程序文件" #~ "放入 /nfsroot。当启动 Cobalt 时,您必须同时按下左右光" #~ "标键,机器就从 NFS 网络启动。它会在显示器上显示几个选项。有下面两种安装方" #~ "法:" #~ msgid "" #~ "Via SSH (default): In this case, the installer will configure the network " #~ "via DHCP and start an SSH server. It will then display a random password " #~ "and other login information (such as the IP address) on the Cobalt LCD. " #~ "When you connect to the machine with an SSH client you can start with the " #~ "installation." #~ msgstr "" #~ "通过 SSH (默认):这种情况下,安装程序将通过 DHCP 配置网络并启动 SSH 服务" #~ "器。它将在 LCD 上显示一个随机的密码和其他的登录信息 (如 IP 地址)。当您用 " #~ "SSH 连接到机器就可以开始安装。" #~ msgid "" #~ "Via serial console: Using a null modem cable, you can connect to the " #~ "serial port of your Cobalt machine (using 115200 bps) and perform the " #~ "installation this way." #~ msgstr "" #~ "通过串口控制台:使用 null modem 线,您可以连接到 Cobalt 机器的串口 (使用 " #~ "115200 bps) 然后进行安装。" #~ msgid "" #~ "You cannot pass any boot parameters directly. Instead, you have to edit " #~ "the /nfsroot/default.colo file on the NFS server and " #~ "add your parameters to the args variable." #~ msgstr "" #~ "您不能直接传递引导参数。而不得不编辑位于 NFS 服务器上的 /" #~ "nfsroot/default.colo 文件,将参数给 args 变量。"