# Debian GNU/Linux Installation Guide - translation into Chinese (simplified) # Yangfl , 2017. # tao wang , 2020. # wangling12 , 2020. # tao wang , 2020. # Boyuan Yang <073plan@gmail.com>, 2021. # 吕文彬 , 2021. # msgid "" msgstr "" "Project-Id-Version: d-i-manual\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" "POT-Creation-Date: 2024-01-07 23:04+0000\n" "PO-Revision-Date: 2024-02-05 11:03+0000\n" "Last-Translator: Li Zelin \n" "Language-Team: \n" "Language: zh_CN\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=1; plural=0;\n" "X-Generator: Weblate 5.4-dev\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:14 #, 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:25 #, no-c-format msgid "" "For information on how to boot the graphical installer, see ." msgstr "关于如何引导图形安装程序的信息,请参见。" #. Tag: title #: boot-installer.xml:38 #, no-c-format msgid "Boot image formats" msgstr "引导映像的格式" #. Tag: para #: boot-installer.xml:39 #, 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 "" "在基于 ARM 的系统中,大多数情况下使用两种格式的引导映像之一:a)标准的 Linux " "zImage 格式内核(vmlinuz)与标准的 Linux 初始虚拟硬盘" "(initrd.gz)结合使用,或 b)uImage 格式的内核" "(uImage)与相应的初始虚拟硬盘(uInitrd)结合使" "用。" #. Tag: para #: boot-installer.xml:47 #, 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 "" "uImage/uInitrd 是为 U-Boot 固件设计的映像格式,用在基于 ARM 的系统(大多数为 " "32 位系统)上。较旧的 U-Boot 版本只能引导 uImage/uInitrd 格式的引导文件,因此" "通常在较旧的 armel 系统上使用。除了引导 uImage/uInitrd 外,较新的 U-Boot 版本" "还可以引导标准的 Linux 内核和虚拟硬盘映像,但是这样做的命令语法与引导 uImage " "的略有不同。" #. Tag: para #: boot-installer.xml:56 #, 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 "" "对于使用多平台内核的系统,除内核和初始虚拟硬盘之外,还需要一个所谓的设备树文" "件(或设备树 blob,dtb)。它对每个被支持的系统是特定的,并包含" "特定硬件的描述。dtb应该由固件在设备上提供,但实际上通常需要加载较新版本的 " "dtb。" #. Tag: title #: boot-installer.xml:67 boot-installer.xml:85 #, no-c-format msgid "Console configuration" msgstr "控制台配置" #. Tag: para #: boot-installer.xml:68 #, 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 "" "网络启动 tarball()和安装程序" "的 SD 卡映像()使用 U-Boot 在 " "console 变量中定义的(针对特定平台的)默认控制台。大多数情况" "下,这是一个串行控制台,所以在这些平台上,默认需要使用串行控制台电缆来使用安" "装程序。" #. Tag: para #: boot-installer.xml:77 #, 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 "" "在同样支持视频控制台的平台上,如果希望安装程序在视频控制台上启动,那么可以修" "改对应的 U-Boot console 变量。" #. Tag: para #: boot-installer.xml:86 #, no-c-format msgid "" "The graphical installer is (experimentally) enabled on the arm64 &d-i; " "images, but on some devices you may still have to use the serial console. " "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 "" "arm64 的 &d-i; 映像支持图形安装程序(虽然是实验性的),但对于某些设备,您可能" "仍需要使用串口控制台。控制台设备应该会被固件自动检测到,但如果没有,那么从 " "GRUB 菜单引导 linux 后,您将看到一个 Booting Linux (正在引导 " "Linux)的消息,然后就没了。" #. Tag: para #: boot-installer.xml:93 #, 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 "" "如果遇到此问题,那么您需要在内核命令行上设置特定的控制台配置。在 GRUB 菜单中" "按 e,以编辑内核命令行,然后将 " "--- quiet 更改为 " "console=<device>,<speed>,例如 console=ttyAMA0,115200n8。完成后,按组合键 Control x 来使用新设置继续引导。" #. Tag: title #: boot-installer.xml:107 #, no-c-format msgid "Juno Installation" msgstr "Juno 安装" #. Tag: para #: boot-installer.xml:108 #, 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 "" "Juno 有 UEFI,所以安装很直接。最实际的方法是从 U 盘安装。您需要更新固件来使 " "USB-booting 工作。从 2015 年 3 月后的 &url-juno-firmware; 版本测试成功了。关于固件的更新请咨询 Juno 文" "档。" #. Tag: para #: boot-installer.xml:115 #, no-c-format msgid "" "Prepare a standard arm64 CD/DVD 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 "" "在 U 盘上准备一个标准的 arm64 的 CD/DVD 镜像。将其插入背面的一个 USB 端口。将" "串口线插入背面的 9 针串口。如果你需要联网(netboot 映像),请将以太网线插入机" "器前面的插口。" #. Tag: para #: boot-installer.xml:122 #, 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 "" "运行串行控制台,波特率 115200,8 位,无奇偶校验位,并引导 Juno。它应会从 U 盘" "引导到 GRUB 菜单。在 Juno 上检测不到正确的控制台配置,所以只是按下 " "&enterkey; 将显示没有内核输出。将控制台设为 " "console=ttyAMA0,115200n8(如在 中所述)。" "Control x 启动,应该会" "显示 &d-i; 屏幕,然后您可以继续进行标准安装过程。" #. Tag: title #: boot-installer.xml:135 #, no-c-format msgid "Applied Micro Mustang Installation" msgstr "Applied Micro Mustang 安装" #. Tag: para #: boot-installer.xml:136 #, 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 "" "UEFI 可用于此机器,但通常随 U-Boot 一起提供,因此您首先需要安装 UEFI 固件,然" "后使用标准的引导/安装方法,或使用 U-Boot 引导方法。您必须使用串行控制台来控制" "安装,因为 arm64 架构上未启用图形安装程序。" #. Tag: para #: boot-installer.xml:144 #, 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 "" "推荐的安装方法是使用随机附带的 openembedded 系统,将 &d-i; 内核和 initrd 复制" "到硬盘驱动器上,然后从中引导以运行安装程序。或者替换使用 TFTP 来复制 kernel/" "dtb/initrd 并引导()。在安装后,需要进行" "手动更改,从安装的映像来引导。" #. Tag: para #: boot-installer.xml:153 #, 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 "" "运行串行控制台,波特率 115200,8 位,无奇偶校验位,并引导机器。重新引导机器," "当看到 Hit any key to stop autoboot: (按任意键停止自动引" "导:)时,按下任意键来获得 Mustang# 提示符。然后使用 U-Boot 命令来加载并引导" "内核、dtb 及 initrd。" #. Tag: title #: boot-installer.xml:162 #, 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:168 boot-installer.xml:650 #, no-c-format 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:442, index.docbook:796, index.docbook:1348, index.docbook:1829, index.docbook:2252, index.docbook:2348 #. Tag: para #: boot-installer.xml:176 boot-installer.xml:658 #, no-c-format msgid "" "The server-side setup to support network booting is described in ." msgstr "" "用于支持网络引导的服务器端设置在 中描述。" #. Tag: title #: boot-installer.xml:185 #, no-c-format msgid "TFTP-booting in U-Boot" msgstr "在 U-Boot 中引导 TFTP" #. Tag: para #: boot-installer.xml:186 #, 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 "" "在系统上使用 U-Boot 固件进行网络引导包括三个步骤:a)配置网络,b)将映像(内" "核/初始虚拟硬盘/dtb)加载到内存中,以及 c)实际执行预加载的代码。" #. Tag: para #: boot-installer.xml:192 #, 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 "" "首先,您必须配置网络,或者通过运行\n" "setenv autoload no\n" "dhcp\n" "由 DHCP 来自动配置,或者手动设置环境变量" "\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" "。如果您愿意的话,可以永久设置它们,通过运行" #. Tag: screen #: boot-installer.xml:199 #, no-c-format msgid "saveenv" msgstr "saveenv" #. Tag: para #: boot-installer.xml:201 #, 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 "" "之后需要将映像(内核/初始虚拟硬盘/dtb)加载到内存中。这可以通过 tftpboot 命令" "来完成,该命令必须提供映像在内存中存储的地址。不幸的是,由于内存映射因系统而" "异,所以没有关于内存可以使用哪些地址的一般规则。" #. Tag: para #: boot-installer.xml:209 #, 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 "" "在某些系统上, U-Boot 预定义了一组带有适当的加载地址的环境变量:" "kernel_addr_r、ramdisk_addr_r和fdt_addr_r。您可以运行" "\n" "printenv kernel_addr_r ramdisk_addr_r fdt_addr_r\n" " 来检查它们是否已定义。如果未定义,则必须查看系统" "文档以获取适当的值并手动设置。对于基于 Allwinner SunXi SOC 的系统(例如 " "Allwinner A10,架构名称为 sun4i 或 Allwinner A20,架构名称为 " "sun7i),您可以使用例如下面的值:" #. Tag: screen #: boot-installer.xml:220 #, 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:222 #, 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 "定义加载地址后,将映像从之前定义的 tftp 服务器中加载到内存,可以使用" #. Tag: screen #: boot-installer.xml:225 #, 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 "" "tftpboot ${kernel_addr_r} <内核映像文件名>\n" "tftpboot ${fdt_addr_r} <dtb 文件名>\n" "tftpboot ${ramdisk_addr_r} <初始化内存盘映像文件名>" #. Tag: para #: boot-installer.xml:227 #, 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 "" "第三部分是设置内核命令行并实际执行加载的代码。U-Boot 将 bootargs 环境变量的内容作为命令行传递给内核,因此内核和安装程序的任何参数——如控" "制台设备(请参见 )或预设选项(请参见 )——可以" "使用命令如 \n" "setenv bootargs console=ttyS0,115200 rootwait panic=10\n" " 来设置。执行先前加载的代码的确切命令取决于所使用" "的映像格式。要使用 uImage/uInitrd,命令是\n" "bootm ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}\n" " 而要使用原生 Linux 映像,则是" #. Tag: screen #: boot-installer.xml:240 #, 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:242 #, 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 "" "注意:当引导标准的 linux 映像时,重要的是在内核和 dtb 之后加载初始虚拟硬盘映" "像,因为 U-Boot 将 filesize 变量设置为最后一个加载的文件的大小,并且 bootz 命" "令需要虚拟硬盘映像的大小才能正常工作。在引导特定平台的内核时,也就是没有设备" "树的内核时,省略 ${fdt_addr_r} 参数即可。" #. Tag: title #: boot-installer.xml:253 #, no-c-format msgid "Pre-built netboot tarball" msgstr "预构建的网络引导 tarball" #. Tag: para #: boot-installer.xml:254 #, 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 "" "&debian; 提供了一个预构建的 tarball(&armmp-netboot-tarball;),可以直接在 " "tftp 服务器上解压,其中包含了网络引导所需的所有文件。它还包括一个引导脚本,可" "自动执行加载安装程序的所有步骤。现代的 U-Boot 版本包含了 tftp 自动引导功能," "当没有可供引导的本地存储设备(MMC/SD、USB、IDE/SATA/SCSI)时会自动启动,然后" "从 tftp 服务器加载该引导脚本。使用此功能的先决条件是您的网络中有 dhcp 服务" "器,可为客户端提供 tftp 服务器的地址。" #. Tag: para #: boot-installer.xml:266 #, no-c-format msgid "" "If you would like to trigger the tftp autoboot feature from the U-Boot " "commandline, you can use the following command:" msgstr "如果要从 U-Boot 命令行使用 tftp 自动启动功能,可以使用以下命令:" #. Tag: screen #: boot-installer.xml:269 #, no-c-format msgid "run bootcmd_dhcp" msgstr "run bootcmd_dhcp" #. Tag: para #: boot-installer.xml:271 #, 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 "" "要手动加载 tarball 提供的引导脚本,您还可以在 U-Boot 提示符执行以下命令:" #. Tag: screen #: boot-installer.xml:275 #, no-c-format msgid "" "setenv autoload no\n" "dhcp\n" "tftpboot ${scriptaddr} /debian-installer/armhf/tftpboot.scr\n" "source ${scriptaddr}" msgstr "" "setenv autoload no\n" "dhcp\n" "tftpboot ${scriptaddr} /debian-installer/armhf/tftpboot.scr\n" "source ${scriptaddr}" # index.docbook:700, index.docbook:2176 #. Tag: title #: boot-installer.xml:283 #, no-c-format msgid "Booting from USB Memory Stick with UEFI" msgstr "在 UEFI 下从 U 盘引导" #. Tag: para #: boot-installer.xml:289 boot-installer.xml:550 #, no-c-format 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 "" "如果您的计算机可以从 USB 引导,那么这可能是最简单的安装方法。假设已经从 " " 准备好了所有步骤,那么只需将 U " "盘插入一个空的 USB 口并重新引导计算机。系统应该引导,除非使用了灵活方式创建 " "U 盘并且不启用,应该(在支持的硬件上)看到图形引导菜单。这里可以选择各种安装" "程序选项,或只是按 &enterkey; 按键。" # index.docbook:700, index.docbook:2176 #. Tag: title #: boot-installer.xml:308 #, no-c-format msgid "Booting from a USB stick in U-Boot" msgstr "在 U-Boot 下从 U 盘引导" #. Tag: para #: boot-installer.xml:309 #, 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 "" "许多现代 U-Boot 版本支持 USB ,并允许从 USB 大容量存储设备如 U 盘来启动。但不" "幸的是,这样做的确切步骤可能因设备的不同而会有非常大差别。" #. Tag: para #: boot-installer.xml:316 #, 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 "" "U-Boot v2014.10 引入了通用的命令行处理和自动引导框架。这允许构建任何系统上都" "能工作的通用引导映像。&d-i; 支持在这样的系统上从 U 盘安装,但不幸的是,并不是" "所有的平台都采用了这个新框架。" #. Tag: para #: boot-installer.xml:325 #, 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 "" "要构建用于安装 debian 的可引导 U 盘,请将 hd-media tarball(请参见)解压到 U 盘上,此 U 盘已经用您设备上 U-Boot 版本所" "支持的文件系统来格式化。对于现代的 U-Boot 版本而言,FAT16 / FAT32 / ext2 / " "ext3 / ext4 通常都可以正常工作。然后将第一个 &debian; 安装 CD 或 DVD 上的 " "ISO 映像文件复制到 U 盘上。" #. Tag: para #: boot-installer.xml:335 #, no-c-format msgid "" "The autoboot framework in modern U-Boot versions works similar to the boot " "ordering options in a PC BIOS/UEFI, 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 "" "现代 U-Boot 版本中的自动引导框架的工作原理类似于PC BIOS/UEFI 中的引导顺序选" "项,即它会检查可能的引导设备列表,以找到有效的引导镜像,并启动第一个找到的设" "备。如果没有安装操作系统,那么插上 U 盘并给系统上电应该会启动安装程序。也可以" "在任何时候从 U-Boot 提示符输入 run bootcmd_usb0 命令来启动 " "USB-boot 进程。" #. Tag: para #: boot-installer.xml:345 #, 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 "" "使用串行控制台从 U 盘启动时,一个可能出现的问题是控制台波特率不匹配。如果在 " "U-Boot 中定义了控制台变量,那么 &d-i; 引导脚本会自动将其传递给内核,来设置控" "制台设备,以及如果合适的话,设置控制台波特率。不幸的是,对控制台变量的处理因" "平台而异——在某些平台上,控制台变量包含波特率(如在 " "console=ttyS0,115200 中),而在其它平台上,控制台变量只包含设" "备(如在 console=ttyS0 中)。当 U-Boot 与内核之间的默认波特率" "不同时,后一种情况将导致控制台输出乱码。现代 U-Boot 版本通常使用 115200 波特" "率,而内核仍默认为传统的 9600 波特率。如果发生这种情况,应该手动设置控制台变" "量,来为您的系统包含正确的波特率,然后使用 run bootcmd_usb0 命" "令来启动安装程序。" #. Tag: title #: boot-installer.xml:366 #, no-c-format msgid "Using pre-built SD-card images with the installer" msgstr "使用带有安装程序的预构建 SD 卡映像" #. Tag: para #: boot-installer.xml:367 #, 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 "" "对于许多系统,Debian 还提供 SD 卡映像,其中包含 U-Boot 和 &d-i;。这些映像有两" "种变体—— 一种用于通过网络下载软件包(可在 &armmp-netboot-sd-img; 上获得),另" "一种使用 Debian CD/DVD 进行离线安装(可在 &armmp-hd-media-sd-img; 上获得)。" "为了节省空间和网络带宽,映像由两部分组成——系统相关部分,名为 firmware." "<system-type>.img.gz,和与系统无关的部分,名为 " "partition.img.gz。" #. Tag: para #: boot-installer.xml:378 #, 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 "" "要在 Linux 系统上从两个部分创建一个完整的映像,可以使用 zcat,如下所示:" "zcat firmware.<system-type>.img.gz partition." "img.gz > complete_image.img。在 Windows 系统" "上,您必须首先分别解压这两个部分,可使用例如 7-Zip 来完成,然后在 Windows " "CMD.exe 窗口中运行命令 copy /b firmware.<system-" "type>.img + partition.img complete_image.img," "将解压的两个部分连接起来。" #. Tag: para #: boot-installer.xml:392 #, 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 "" "将生成的映像写入 SD 卡,例如在 Linux 系统上运行以下命令:" "cat complete_image.img > /dev/SD_CARD_DEVICE。将 SD 卡插入目标系统并为系统上电后,安装程序将从 " "SD 卡中加载。如果使用 hd-media 变体进行离线安装,则必须在单独的介质上向安装程" "序提供第一个 &debian; CD/DVD,例如可以是 U 盘上的 CD/DVD ISO 映像。" #. Tag: para #: boot-installer.xml:404 #, 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 "" "当进入安装程序中的分区步骤(请参见)时,可以" "删除或替换卡上任何先前的分区。一旦安装程序启动,它将完全在系统的主内存中运" "行,不需要再访问 SD 卡,所以可以使用用于安装 &debian; 的整个 SD卡。要在 SD 卡" "上创建正确的分区布局,最简单的方法是让安装程序为您自动创建一个(请参见)。" # index.docbook:700, index.docbook:2176 #. Tag: title #: boot-installer.xml:544 #, 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:568 #, no-c-format msgid "Booting from optical disc (CD/DVD)" msgstr "从光盘(CD/DVD)引导" # index.docbook:531, index.docbook:584, index.docbook:957, index.docbook:1776, index.docbook:2024, index.docbook:2378 #. Tag: para #: boot-installer.xml:574 #, no-c-format msgid "" "If you have a set of optical discs, and your machine supports booting " "directly off those, great! Simply configure your " "system for booting off an optical disc as described in , insert the disc, reboot, and proceed to the " "next chapter." msgstr "" "如果您有一套光盘,并且您的机器支持直接从这些光盘上引导,那就太好了!只需 " " 按这个说明配置您的系统,使其能够从光盘上引导,如在 " "中所描述的,插入光盘,然后重" "新引导,再进行到下一章。" # index.docbook:542, index.docbook:595, index.docbook:968, index.docbook:1787, index.docbook:2035, index.docbook:2389 #. Tag: para #: boot-installer.xml:584 #, no-c-format msgid "" "Note that certain optical drives may require special drivers, and thus be " "inaccessible in the early installation stages. If it turns out the standard " "way of booting off an optical disc doesn't work for your hardware, revisit " "this chapter and read about alternate kernels and installation methods which " "may work for you." msgstr "" "注意,某些特定的光盘驱动器会需要一些特殊的驱动程序,这样它们可能在安装阶段的" "早期不能访问。如果从光盘引导的标准方法不能用于您的硬件,那么重新阅读本章中关" "于其它种类的内核以及安装方法,它们有可能会解决问题。" # index.docbook:550, index.docbook:603, index.docbook:976, index.docbook:1795, index.docbook:2043, index.docbook:2397 #. Tag: para #: boot-installer.xml:592 #, no-c-format msgid "" "Even if you cannot boot from optical disc, you can probably install the " "&debian; system components and any packages you want from such disc. 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 optical drive." msgstr "" "即便您不能从光盘引导,可能依然可以从光盘上安装 &debian; 系统组件和想要安装的" "任何软件包。只要使用不同的媒介来引导,并当安装操作系统、基础系统和任意附加的" "软件包时,只需将安装系统指向光盘驱动器即可。" # index.docbook:558, index.docbook:611, index.docbook:984, index.docbook:1803, index.docbook:2051, index.docbook:2405 #. Tag: para #: boot-installer.xml:600 #, no-c-format msgid "" "If you have problems booting, see ." msgstr "如果引导出现问题,请参见 。" #. Tag: title #: boot-installer.xml:610 #, no-c-format msgid "Booting from Linux using GRUB" msgstr "从 Linux 使用 GRUB 来引导" #. Tag: para #: boot-installer.xml:613 #, 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:618 #, no-c-format msgid "" "For GRUB2, you will need to configure two essential " "things in /boot/grub/grub.cfg:" msgstr "" "对于 GRUB2,您将需要在 /boot/grub/grub.cfg 中配置两个基本内容:" #. Tag: para #: boot-installer.xml:622 #, no-c-format msgid "to load the initrd.gz installer at boot time;" msgstr "在启动时加载 initrd.gz 安装程序;" #. Tag: para #: boot-installer.xml:627 #, no-c-format msgid "" "have the vmlinuz kernel use a RAM disk as its root " "partition." msgstr "让 vmlinuz 内核使用 RAM 磁盘作为其根分区。" #. Tag: para #: boot-installer.xml:635 #, no-c-format msgid "An entry for the installer would be for example:" msgstr "例如,安装程序的条目是:" #. Tag: screen #: boot-installer.xml:639 #, 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" "}" # 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:644 #, no-c-format msgid "Booting with TFTP" msgstr "用 TFTP 引导" #. Tag: para #: boot-installer.xml:666 #, no-c-format msgid "There are various ways to do a TFTP boot on i386." msgstr "在 i386 体系上有很多方法用 TFTP 进行引导。" #. Tag: title #: boot-installer.xml:672 #, no-c-format msgid "NIC or Motherboard that support PXE" msgstr "支持 PXE 的网卡或者主板" #. Tag: para #: boot-installer.xml:673 #, 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/UEFI to boot from the network." msgstr "" "您的网卡或者主板可能已经提供了 PXE 引导功能。它是 Intel TFTP 引导的再实现。如果是这样的话,您能够配置 BIOS/UEFI " "而从网络进行引导。" #. Tag: title #: boot-installer.xml:684 #, no-c-format msgid "NIC with Network BootROM" msgstr "带有网络 BootROM 的网卡" #. Tag: para #: boot-installer.xml:685 #, no-c-format msgid "" "It could be that your Network Interface Card provides TFTP boot " "functionality." msgstr "您的网卡可能已经提供了 TFTP 引导功能。" #. Tag: para #: boot-installer.xml:690 #, 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:698 #, no-c-format msgid "Etherboot" msgstr "Etherboot" #. Tag: para #: boot-installer.xml:699 #, no-c-format msgid "" "The etherboot project " "provides bootdiskettes and even bootroms that do a TFTPboot." msgstr "" "etherboot project " "(etherboot 项目)提供了进行 TFTP 引导所需要的引导软盘甚至是引导 ROMs。" # index.docbook:1943, index.docbook:2477 #. Tag: title #: boot-installer.xml:709 #, no-c-format msgid "The Boot Screen" msgstr "引导屏幕" #. Tag: para #: boot-installer.xml:710 #, 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 "当安装程序引导时,您应该看到友好的图形屏幕,显示 &debian; 标志和菜单:" #. Tag: screen #: boot-installer.xml:715 #, no-c-format msgid "" "&debian-gnu; installer boot menu\n" "\n" "Graphical install\n" "Install\n" "Advanced options >\n" "Accessible dark contrast installer menu >\n" "Help\n" "Install with speech synthesis" msgstr "" "&debian-gnu; installer boot menu\n" "\n" "Graphical install\n" "Install\n" "Advanced options >\n" "Accessible dark contrast installer menu >\n" "Help\n" "Install with speech synthesis" #. Tag: para #: boot-installer.xml:719 #, 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 "" "根据计算机的引导方式(BIOS 或 UEFI)不同,此图形屏幕将看起来略有不同,但会显" "示相同的选项。" #. Tag: para #: boot-installer.xml:727 #, 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 "" "根据您使用的安装方法,Graphical install(图形安装)选项可能不" "可用。另外,双架构映像在每个安装选项下还会有它的 64 位变体,因此选项数量几乎" "会翻倍。" #. Tag: para #: boot-installer.xml:734 #, no-c-format 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 "" "普通安装时,可以使用键盘方向键或者键入(高亮的)首字母 —,并按下 " "&enterkey;,来选择Graphical install(图形安装)或" "Install(图形安装)入口,从而引导安装程序。默认已经选择了" "Graphical install(图形安装)入口。" #. Tag: para #: boot-installer.xml:742 #, 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(高级选项)用于访问第二层菜单,引导安装程序进" "入专家模式、救援模式和自动安装。" #. Tag: para #: boot-installer.xml:748 #, no-c-format msgid "" "If you wish or need to add any boot parameters for either the installer or " "the kernel, press &tabkey; (BIOS boot), or &ekey; then &downkey; three times " "then &endkey;, to edit the linux line of the boot entry (UEFI " "boot). This will bring the boot command for the selected menu entry and " "allow you to edit it to suit your needs. Note that the keyboard layout at " "this point is still QWERTY. The help screens (see below) list some common " "possible options. Press &enterkey; (BIOS boot) or &f10key; (UEFI boot) to " "boot the installer with your options; pressing &escapekey; will return you " "to the boot menu and undo any changes you made." msgstr "" "如果您希望或者需要为安装程序或内核添加引导参数,那么按下 &tabkey;(BIOS 引" "导),或者按 &ekey;,然后按 &downkey; 3 次,然后按 &endkey; 来编辑引导条目中" "的 linux 一行(UEFI 引导)。这将使引导命令显示所选择的菜单入" "口,并允许编辑来适合您的需要。注意这时的键盘布局仍然为 QWERTY。帮助屏幕(请参" "见下方)列出一些可能的选项。按下 &enterkey;(BIOS 引导)或 &f10key;(UEFI 引" "导),将使用您的选项来引导安装程序;按下 &escapekey; 将返回引导菜单并放弃您所" "做的更改。" #. Tag: para #: boot-installer.xml:761 #, 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:779 #, 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:789 #, 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:799 #, 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 选项。此后的输入就会在提示符后面显示。要防止安装程" "序为余下的安装使用帧缓冲区,还需要在启动提示符后添加 vga=normal " "fb=false,这在帮助文本中有说明。" #. Tag: title #: boot-installer.xml:818 #, no-c-format msgid "S/390 Limitations" msgstr "S/390 的限制" #. Tag: para #: boot-installer.xml:819 #, 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:824 #, 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:835 #, no-c-format msgid "S/390 Boot Parameters" msgstr "S/390 引导参数" #. Tag: para #: boot-installer.xml:836 #, no-c-format msgid "" "On S/390 you can append boot parameters in the parm file. This file can " "either be in ASCII or EBCDIC format. It needs to be fixed-width with 80 " "characters per line. A sample parm file 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 上可以在 parm(参数)文件中添加引导参数。这个文件可以是 ASCII 或者 " "EBCDIC 格式的。要求它需要是每行 80 字符固定宽度的。parm(参数)文件的示例 " "parmfile.debian 提供有安装映像。如果参数太长无法与 80 个" "字符的限制匹配,那么可以简单地在下一行第一列继续。当传输到内核时所有的行都去" "掉空格连接在一起。" #. Tag: para #: boot-installer.xml:853 #, 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 "" "如果您在逻辑分区(LPAR)或能看到很多设备的虚拟机(VM)上引导安装程序,则可以" "指示内核将列表限制固定的一组设备上。如果大量磁盘可见,更可能是在 LPAR 模式" "中,建议在安装程序的引导过程中使用。cio_ignore 选项支持黑名单" "(仅禁用少数设备)和白名单(仅允许特定设备):\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" "请注意,所有设备编号的十六进制数字需要以小写形式指" "定。进一步,如果使用此引导参数,则需要列出所有设备:至少包括磁盘、网络设备和" "控制台。为了安装程序引导过程,上述选项需要添加到 parmfile.debian 中。" #. Tag: title #: boot-installer.xml:1138 #, no-c-format msgid "Booting a ppc64el machine" msgstr "引导 ppc64el 机器" #. Tag: para #: boot-installer.xml:1139 #, no-c-format msgid "How to boot a ppc64el machine:" msgstr "如何引导 ppc64el 机器:" #. Tag: title #: boot-installer.xml:1145 #, no-c-format msgid "Petitboot" msgstr "Petitboot" #. Tag: para #: boot-installer.xml:1146 #, 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 "" "Petitboot 是基于 Linux kexec 而独立于平台的引导加载程序。Petitboot 支持从任" "何 Linux 可挂载的文件系统加载内核、initrd 和设备树文件,还可以使用FTP、SFTP、" "TFTP、NFS、HTTP 和 HTTPS 协议从网络加载文件。Petitboot 可以引导任何包含 " "kexec 引导支持的操作系统。" #. Tag: para #: boot-installer.xml:1154 #, 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 "" "Petitboot 在系统中的可挂载设备上查找引导加载程序配置文件,还可以配置来使用 " "DHCP 服务器的引导信息。" #. Tag: title #: boot-installer.xml:1181 #, no-c-format msgid "The Graphical Installer" msgstr "图形安装程序" #. Tag: para #: boot-installer.xml:1182 #, 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 "" "安装程序的图形版本仅适用于有限数量的架构,包括 &arch-title;。图形安装程序的功" "能被之上与基于文本的安装程序功能相同,因为它基本使用相同的程序,只是前端不" "同。" #. Tag: para #: boot-installer.xml:1190 #, 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 "" "虽然功能相同,图形安装程序仍然有一些显著优点。主要优点在于它支持更多的语言," "即在基于文本的 newt 前端上无法显示的字符集的语言也可以使用。它" "还具有一些可用性上的优点,如可以使用鼠标,并且在某些情况下还可以在单个屏幕上" "显示多个问题。" #. Tag: para #: boot-installer.xml:1199 #, no-c-format msgid "" "The graphical installer is available with all CD/DVD 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 "" "图形安装程序可以在 CD/DVD 映像以及hd-media安装方法中获得。要引导图形安装程" "序,只需简单地从引导菜单中选择相关选项即可。可以从高级选项菜单" "中选择图形安装程序的专家和救援模式。以前使用的引导方法 " "installguiexpertgui 和 " " rescuegui,仍然可以在选择帮助选项后从" "引导提示符来使用。" #. Tag: para #: boot-installer.xml:1230 #, 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:1236 #, 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 "" "与基于文本的安装程序相比,图形安装程序需要更多的内存才能运行:&minimum-" "memory-gtk;。如果内存不足,它将自动返回到基于文本的 newt 前" "端。" #. Tag: para #: boot-installer.xml:1243 #, 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 "" "如果系统中的内存量低于 &minimum-memory;,图形安装程序可能无法启动,而基于文本" "的安装程序可能仍可以工作。对于可用内存很小的系统,推荐使用基于文本的安装程" "序。" #. Tag: title #: boot-installer.xml:1261 #, no-c-format msgid "Accessibility" msgstr "辅助功能" #. Tag: para #: boot-installer.xml:1262 #, 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 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 转换口转换的串行显示器)盲文点字显示器可以自动检" "测到,但多数情况下其它的 多数辅" "助功能不得不手动启用。在可以支持的机器上,当准备好接收输" "入时引导菜单会发出哔声。在 BIOS 系统中会发出一声哔声,而在 UEFI 系统中会发出" "两声哔声。 一些引导参数可以 接着 被添" "加来启用辅助功能(请参见。注意:在多数架构下引导加载程序会将您的键盘视为 QWERTY 布局的键" "盘。" #. Tag: title #: boot-installer.xml:1282 #, no-c-format msgid "Installer front-end" msgstr "安装程序前端" #. Tag: para #: boot-installer.xml:1283 #, 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 "" "&debian; 安装程序支持使用多个前端提出问题,可访问性各有不同:特别是 " "text 使用纯文本,而 newt 使用基" "于文本的对话框。可以在启动提示符下进行选择,请参见中的 DEBIAN_FRONTEND 文档。" #. Tag: para #: boot-installer.xml:1291 #, no-c-format msgid "" "With the newt front-end (used mostly with braille), " "one mostly just selects answers with arrow keys and presses &enterkey; to " "validate the choice. Pressing &tabkey; or &shiftkey; - &tabkey; allows to " "switch between dialog elements, and notably to access the Go " "Back button, which brings back again to previous questions. Some " "dialogs contain check boxes, which can be ticked on and off by pressing " "&spacekey;." msgstr "" "使用 newt 前端时(通常和盲文同时使用),可以使用方向键" "选择答案,然后按 &enterkey; 确认选择。按下 &tabkey; 或 &shiftkey; - &tabkey; " "可以在对话框的元素之间进行切换,更关键的是,还可以选择返回按钮,可以返回到之前的问题。有些对话框包含复选框,可以使用 " "&spacekey; 勾选或取消勾选。" #. Tag: para #: boot-installer.xml:1301 #, no-c-format msgid "" "With the text front-end (used mostly with speech), " "one mostly selects answers either by typing their number followed by " "pressing &enterkey;, or by selecting an answer with arrow keys, and pressing " "&enterkey; to validate the choice. One can also not type anything and just " "press &enterkey; to simply accept the default value. Typing < and pressing &enterkey; brings back again to previous questions. " "When a selection of choices has to be made (e.g. during task selection), one " "can type ! to express an empty selection." msgstr "" "使用 text 前端时(通常和语音合成同时使用),可以输入数" "字并按下 &enterkey; 来选择答案,或者,通过方向键选择并按下 &enterkey; 来确认" "答案。不输入任何内容直接按 &enterkey; 可以选择默认值。输入 < 并按下 &enterkey; 可以返回到之前的问题。当需要选择一组项目作为答案" "时(例如在选择任务时),可以输入 ! 表示不选择任何项" "目。" #. Tag: title #: boot-installer.xml:1316 #, no-c-format msgid "USB Braille Displays" msgstr "USB 盲文点字显示器" #. Tag: para #: boot-installer.xml:1317 #, 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 启动,就可以通过进入首选项菜单来选择盲文表" "了。在 brltty " "website 可以找到盲文点字显示器的键绑定文档。" #. Tag: title #: boot-installer.xml:1332 #, no-c-format msgid "Serial Braille Displays" msgstr "串口盲文点字显示器" #. Tag: para #: boot-installer.xml:1333 #, 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 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 "" "系统无法安全地检测到串口盲文点字显示器(因为这可能会损坏某s些设备)。这样需要" "添加引导参数 brltty=driver," "port,table,来告知 brltty 该使用哪个驱动程序和端口。" "driver(驱动器)应该替换为您终端使用的两个字母的驱" "动器代码(请参见 BRLTTY manual(手册))。port(端口) 应该替换为显示器所连接的串" "口名称,默认为 ttyS0,当使用串口转 USB 转接口时,可以" "典型地使用 ttyUSB0。可以提供第三方参数,来选择所使用的" "盲文表的名称(请参见 BRLTTY manual(手册)" ");默认为英语表。注意,可以在后面进入首选项菜单来更换该表。可以提供" "第四个参数,来将参数传递给盲文驱动程序,如一些少见的型号所需的 " "protocol=foo。盲文设备的键绑定文档可以在 brltty website(网站) 找到。" #. Tag: title #: boot-installer.xml:1360 boot-installer.xml:2316 #, no-c-format msgid "Software Speech Synthesis" msgstr "软件语音合成" #. Tag: para #: boot-installer.xml:1361 #, no-c-format msgid "" "Support for software speech synthesis is available on all installer images " "which have the graphical installer, i.e. all netinst 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 "" "在具有图形安装程序的所有安装程序影像中,即在所有的网络安装 CD 和 DVD 映像,以" "及上网本 gtk 变种中,可以获得对软件语音合成的支持。可以通过在引导菜单输入" "s&enterkey; 来选择激活它。然后会自动选择文本版本的安装" "程序,并且对软件语音合成的支持将自动安装在目标系统上。" #. Tag: para #: boot-installer.xml:1370 #, no-c-format msgid "" "If several sound cards are detected, you will be prompted to press " "&enterkey; when you hear speech from the desired sound card." msgstr "" "如果检测到几个声卡,那么会提示从所需要的声卡听到语音时,按下 &enterkey; 键。" #. Tag: para #: boot-installer.xml:1375 #, no-c-format msgid "" "The first question (language) is spoken in english, and the remainder of " "installation is spoken in the selected language (if available in " "espeak)." msgstr "" "第一个问题(语言)以英语讲出,而安装的其余部分以所选择的语言讲出(如果在 " "espeak中可用的话)。" #. Tag: para #: boot-installer.xml:1381 #, 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 "" "默认语速很慢。要使其更快,请按 CapsLock " "6 组合键。要使其更慢,请按 " "CapsLock 5 组合键。默认音量应该" "是中等的。要更大声,请按 CapsLock 2 组合键。要使其更安静,请按 CapsLock 1 组合键。要获取有关浏览快捷方式的更多详" "细信息,请参见 Speakup guide(语音向导)。要接受问题的默认答案,只需在提示符下按 Enter 键即" "可。要为问题提供空答案,请在提示符下键入。要返回上一" "个问题,请在提示符下键入 <。" #. Tag: title #: boot-installer.xml:1409 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "硬件语音合成 (Hardware Speech Synthesis)" #. Tag: para #: boot-installer.xml:1410 #, no-c-format msgid "" "Support for hardware speech synthesis devices is available on all installer " "images which have the graphical installer, i.e. all netinst and DVD images, " "and the netboot gtk variant. You thus need to select a Graphical " "install entry in the boot menu." msgstr "" "对于硬件语音合成设备的支持只在具有图形安装程序的安装映像中有效,也就是所有的" "网络安装 CD 和 DVD 映像,以及上网本 gtk 变体中。这样您需要在引导菜单中选择 " "Graphical install(图形安装) 入口。" #. Tag: para #: boot-installer.xml:1417 #, 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:1432 #, no-c-format msgid "Board Devices" msgstr "板卡设备" #. Tag: para #: boot-installer.xml:1433 #, 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:1441 #, 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 "" "如果需要,在输入 h &enterkey; 来添加引导参数前,可以激" "活文本版本的引导加载程序。" #. Tag: title #: boot-installer.xml:1449 #, no-c-format msgid "High-Contrast Theme" msgstr "高对比度的主题" #. Tag: para #: boot-installer.xml:1450 #, no-c-format msgid "" "For users with low vision, the installer can use a high-contrast color theme " "that makes it more readable. To enable it, you can use the Accessible " "high contrast entry from the boot screen with the d shortcut, or append the theme=dark boot " "parameter." msgstr "" "对于视力弱的用户,安装程序可以使用高对比度的彩色主题来增加可读性。为了启用" "它,可以从引导屏幕上通过d 快捷键,或者添加 " "theme=dark 引导参数,来使用Accessible high " "contrast(使用高对比读)入口。" #. Tag: title #: boot-installer.xml:1461 #, no-c-format msgid "Zoom" msgstr "缩放" #. Tag: para #: boot-installer.xml:1462 #, 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 "" "对于低视力的用户,图形安装程序有非常基本的缩放支持: " "Control + 组合快捷键和 " " Control - 组合快捷" "键,用于增减与减小字体的尺寸。" #. Tag: title #: boot-installer.xml:1472 #, no-c-format msgid "Expert install, rescue mode, automated install" msgstr "专家安装、救援模式、自动安装" #. Tag: para #: boot-installer.xml:1473 #, 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; ; for UEFI systems " "(the boot menu will have beeped twice) that must not be done. Then, to " "enable speech synthesis, s can optionally be pressed " "(followed again by &enterkey; on BIOS systems but not on UEFI systems). From " "there, various shortcuts can be used: x for expert " "installation, r for rescue mode, or a for automated installation. Again these need to be followed by " "&enterkey; when using a BIOS system." msgstr "" "专家、救援和自动安装选则也可以提供有辅助功能。要访问它们,必须在引导菜单中键" "入 a,来进入Advanced option(高级选项)" "子菜单。当使用 BIOS 系统时(引导菜单只有一次蜂鸣音),之后必须按下 " "&enterkey; 按键;对于 UEFI 系统(引导菜单会有两次蜂鸣音),必须不能这样做。然" "后,要启用语音合成,可以选择按下 s 按键(使用 BIOS 系" "统而不是 UEFI 系统时,紧接着再按下 &enterkey; 按键)。从那里可以使用各种快捷" "方式:用于专家安装的 x,用于救援模式的 r 或用于自动安装的 a。当使用 BIOS 系统时,必" "须再次紧接着按下 &enterkey; 按键。" #. Tag: para #: boot-installer.xml:1488 #, no-c-format msgid "" "The automated install choice allows to install &debian; completely " "automatically by using preseeding, whose source can be entered after " "accessibility features get started. Preseeding itself is documented in ." msgstr "" "自动安装选择允许使用预置来完全自动地安装 &debian;,它的源可以在启动辅助特性后" "进入。预置本身在 中归档。" #. Tag: title #: boot-installer.xml:1498 #, no-c-format msgid "Accessibility of the installed system" msgstr "已安装系统的辅助功能" #. Tag: para #: boot-installer.xml:1499 #, no-c-format msgid "" "Documentation on accessibility of the installed system is available on the " "Debian Accessibility wiki " "page." msgstr "" "可在 Debian Accessibility " "wiki page(Debian 辅助功能维基页面)中找到有关已安装系统的辅助功能的" "文档。" # index.docbook:1943, index.docbook:2477 #. Tag: title #: boot-installer.xml:1513 #, no-c-format msgid "Boot Parameters" msgstr "引导参数" #. Tag: para #: boot-installer.xml:1514 #, 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:1521 #, 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:1528 #, 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:1540 #, no-c-format msgid "Boot serial console" msgstr "引导串口控制台" #. Tag: para #: boot-installer.xml:1542 #, 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 a serial device of the target, which is usually something like " "ttyS0." msgstr "" "假如用串口控制台来引导,那么内核通常会自动检测到。如果在通过串口控制台引导的" "计算机上还连接有视频卡(帧缓存的)和键盘,那么必须将 " "console=device 参数传递给内" "核,其中 device 是目标的串口设备,通常是像 " "ttyS0 的形式。" #. Tag: para #: boot-installer.xml:1554 #, 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 "" "可能需要指定串口的参数,如波特率和奇偶校验位,例如 console = " "ttyS0,9600n8;其它典型的波特率会是 57600 或 115200。请确保在 " "---之后指定此选项,以便已安装的系统能将其复制到引导加载程序的" "配置中(如果引导加载程序的安装程序支持的话)。" #. Tag: para #: boot-installer.xml:1562 #, 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 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。如" "果使用 IPMI 控制台,或者本身不提供转换为这样的终端类型的虚拟工具,例如 QEMU/" "KVM,那么可以在 screen 会话中启动。这会真正地将其转换成 " "screen 终端类型,它非常接近于 vt102 类" "型。" #. Tag: title #: boot-installer.xml:1580 #, no-c-format msgid "&debian; Installer Parameters" msgstr "&debian; 安装程序的参数" #. Tag: para #: boot-installer.xml:1581 #, 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. Also there is a limit of 255 characters for " "the whole kernel command line, everything above this limit may be silently " "truncated. which may be useful." msgstr "" "安装系统能识别一些会有用的额外的引导参数 在当前的内核" "(2.6.9 或更新),您可以使用 32 个命令行参数和 32 个环境变量选项。如果超出内" "核将会崩溃。同样,整个内核命令行有 255 个字符的限制,超出这个限制的任何内容将" "被截掉而不会有提示。 。" #. Tag: para #: boot-installer.xml:1596 #, 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:1608 #, no-c-format msgid "debconf/priority (priority)" msgstr "debconf/priority (priority)" #. Tag: para #: boot-installer.xml:1609 #, no-c-format msgid "This parameter sets the lowest priority of messages to be displayed." msgstr "这个参数将显示的消息设置为最低的优先级。" #. Tag: para #: boot-installer.xml:1613 #, 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:1620 #, 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:1634 #, no-c-format msgid "DEBIAN_FRONTEND" msgstr "DEBIAN_FRONTEND" #. Tag: para #: boot-installer.xml:1635 #, 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:1666 #, no-c-format msgid "BOOT_DEBUG" msgstr "BOOT_DEBUG" #. Tag: para #: boot-installer.xml:1667 #, 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:1676 #, no-c-format msgid "BOOT_DEBUG=0" msgstr "BOOT_DEBUG=0" #. Tag: para #: boot-installer.xml:1677 #, no-c-format msgid "This is the default." msgstr "此为默认。" #. Tag: userinput #: boot-installer.xml:1681 #, no-c-format msgid "BOOT_DEBUG=1" msgstr "BOOT_DEBUG=1" #. Tag: para #: boot-installer.xml:1682 #, no-c-format msgid "More verbose than usual." msgstr "比一般情况更多的信息。" #. Tag: userinput #: boot-installer.xml:1686 #, no-c-format msgid "BOOT_DEBUG=2" msgstr "BOOT_DEBUG=2" #. Tag: para #: boot-installer.xml:1687 #, no-c-format msgid "Lots of debugging information." msgstr "大量的调试信息。" #. Tag: userinput #: boot-installer.xml:1691 #, no-c-format msgid "BOOT_DEBUG=3" msgstr "BOOT_DEBUG=3" #. Tag: para #: boot-installer.xml:1692 #, 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 "" "在引导过程的各个点上运行 Shells,以进行细节上的调试。退出 Shell 会将引导过程" "继续。" #. Tag: term #: boot-installer.xml:1706 #, no-c-format msgid "log_host" msgstr "log_host" #. Tag: term #: boot-installer.xml:1707 #, no-c-format msgid "log_port" msgstr "log_port" #. Tag: para #: boot-installer.xml:1708 #, 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:1719 #, no-c-format msgid "lowmem" msgstr "lowmem" #. Tag: para #: boot-installer.xml:1720 #, 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 "" "可以根据可用的内存,将安装程序强制在高于安装程序默认设置的 lowmem 等级上。该" "值可设为 1 和 2。还请参见 。" #. Tag: term #: boot-installer.xml:1730 #, no-c-format msgid "noshell" msgstr "noshell" #. Tag: para #: boot-installer.xml:1731 #, 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 上提供交互式 shells。这对于物理安全有限时的无人职" "守安装很有用。" #. Tag: term #: boot-installer.xml:1740 #, no-c-format msgid "debian-installer/framebuffer (fb)" msgstr "debian-installer/framebuffer (fb)" #. Tag: para #: boot-installer.xml:1741 #, 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 "" "一些架构使用内核帧缓存来以多种语言提供安装。如果帧缓存使您的系统出现问题,可" "以通过使用参数 vga=normal " "fb=false 来关闭这个特性。这类问题的症状是关于 bterm 或" "者 bogl 的错误消息、空白的屏幕,或者在开始安装后几分钟内死机。" #. Tag: term #: boot-installer.xml:1754 #, no-c-format msgid "debian-installer/theme (theme)" msgstr "debian-installer/theme (theme)" #. Tag: para #: boot-installer.xml:1755 #, no-c-format msgid "" "A theme determines how the user interface of the installer looks (colors, " "icons, etc.). Which themes are available may differ per frontend. Currently " "both the newt and gtk frontend have (apart from the default look) only one " "additional theme named dark theme, which was designed for " "visually impaired users. Set this theme by booting with " "theme=dark (there is also " "the keyboard shortcut d for this in the boot menu)." msgstr "" "界面方案(theme)决定了安装程序的用户界面的外观(颜色、图标等)。不同的前端会" "有不同的界面方案。当前 newt 和 gtk 前端(除了默认的界面)都有另外一个被称为 " "dark 的界面方案,为视觉受损的用户而设计。可以通过以 " "theme=dark 引导来设置这个界" "面方案(在引导菜单中也可以用键盘快捷方式 d 来执行)。" #. Tag: term #: boot-installer.xml:1770 boot-installer.xml:1991 #, no-c-format msgid "netcfg/disable_autoconfig" msgstr "netcfg/disable_autoconfig" #. Tag: para #: boot-installer.xml:1771 #, no-c-format 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; 默认自动检测 IPv6的网络配置和 DHCP。如果检测成功的话,将没有机会回顾并" "且更改已经获得的设定。只能在自动检测失败的情况下手工配置网络。" #. Tag: para #: boot-installer.xml:1778 #, no-c-format 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 "" "如果本地网络上有IPv6路由器或 DHCP 服务器,但是因为例如它们给出错误的答案而不" "想使用它,那么可以使用参数 netcfg/disable_autoconfig=true 来防止网络进行任何自动配置,并手动输入信息。" #. Tag: term #: boot-installer.xml:1789 #, no-c-format msgid "hw-detect/start_pcmcia" msgstr "hw-detect/start_pcmcia" #. Tag: para #: boot-installer.xml:1790 #, 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:1800 #, no-c-format msgid "preseed/url (url)" msgstr "preseed/url (url)" #. Tag: para #: boot-installer.xml:1801 #, 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:1810 #, no-c-format msgid "preseed/file (file)" msgstr "preseed/file (file)" #. Tag: para #: boot-installer.xml:1811 #, no-c-format msgid "" "Specify the path to a preconfiguration file to load for automating the " "install. See ." msgstr "" "将路径指定到要加载的预设置文件,用于使安装自动化。请参见 。" #. Tag: term #: boot-installer.xml:1820 #, no-c-format msgid "preseed/interactive" msgstr "preseed/interactive" #. Tag: para #: boot-installer.xml:1821 #, 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:1833 #, no-c-format msgid "auto-install/enable (auto)" msgstr "auto-install/enable (auto)" #. Tag: para #: boot-installer.xml:1834 #, 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:1845 #, no-c-format msgid "finish-install/keep-consoles" msgstr "finish-install/keep-consoles" #. Tag: para #: boot-installer.xml:1846 #, 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 "" "从串口或者管理控制台安装的过程中,通常在 /etc/inittab 中" "禁止了常规的虚拟控制台(VT1 到 VT6)。将其设置 true 来" "将它们启用。" #. Tag: term #: boot-installer.xml:1857 #, no-c-format msgid "cdrom-detect/eject" msgstr "cdrom-detect/eject" #. Tag: para #: boot-installer.xml:1858 #, 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 such media. 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; 默认自动弹出安装时使用的光学介质。如果系统不是自动从这样" "的介质来引导,那么这是不必要的操作。在某些情况下甚至更为不便,例如,在光盘驱" "动器自己不能重新插入介质,而用户又不在旁边的情况。许多通过插口装入光盘的超薄" "型 caddy 风格的驱动器不能自动重新加载介质。" #. Tag: para #: boot-installer.xml:1867 #, 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:1878 #, no-c-format msgid "base-installer/install-recommends (recommends)" msgstr "base-installer/install-recommends (recommends)" #. Tag: para #: boot-installer.xml:1879 #, 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:1886 #, 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:1898 #, no-c-format msgid "debian-installer/allow_unauthenticated" msgstr "debian-installer/allow_unauthenticated" #. Tag: para #: boot-installer.xml:1899 #, 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:1910 #, no-c-format msgid "ramdisk_size" msgstr "ramdisk_size" #. Tag: para #: boot-installer.xml:1911 #, 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 "" "该参数应该已经设置为所需的正确值;只有在引导过程中您看错误,指示了虚拟不能完" "全加载时才设置它。该值的单位是 kB。" #. Tag: term #: boot-installer.xml:1921 #, no-c-format msgid "rescue/enable" msgstr "rescue/enable" #. Tag: para #: boot-installer.xml:1922 #, no-c-format msgid "" "Set to true to enter rescue mode rather than " "performing a normal installation. See ." msgstr "" "设置为 true 来进入救援模式,而不是执行普通安装。请参" "见 。" #. Tag: title #: boot-installer.xml:1935 #, no-c-format msgid "Using boot parameters to answer questions" msgstr "使用引导参数来回答问题" #. Tag: para #: boot-installer.xml:1936 #, 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:1948 #, no-c-format msgid "debian-installer/language (language)" msgstr "debian-installer/language (language)" #. Tag: term #: boot-installer.xml:1949 #, no-c-format msgid "debian-installer/country (country)" msgstr "debian-installer/country (country)" #. Tag: term #: boot-installer.xml:1950 #, no-c-format msgid "debian-installer/locale (locale)" msgstr "debian-installer/locale (locale)" #. Tag: para #: boot-installer.xml:1951 #, no-c-format msgid "" "There are two ways to specify the language, country and locale to use for " "the installation and the installed system." msgstr "有两种方法为安装过程和安装好的系统来指定所使用的语言、国家和区域设置。" #. Tag: para #: boot-installer.xml:1956 #, 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.UTF-8 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.UTF-8 选择语言为德语,瑞士为国家(安装好的系统中默认将 de_CH." "UTF-8 设置为默认的区域设置)。该方法的限制是,并非所有的语言、国家" "和区域设置的组合可以以这种方式实现。" #. Tag: para #: boot-installer.xml:1965 #, 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(区域设置)可以可选地添加,为安装好的系统指定默认的区域设置。示例:" "language=en country=DE locale=en_GB.UTF-8。" #. Tag: term #: boot-installer.xml:1977 #, no-c-format msgid "anna/choose_modules (modules)" msgstr "anna/choose_modules (modules)" #. Tag: para #: boot-installer.xml:1978 #, 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 (使您可以在安装过程中使用 " "scpppp-udeb(请参见 。" #. Tag: para #: boot-installer.xml:1992 #, no-c-format msgid "" "Set to true if you want to disable IPv6 " "autoconfiguration and DHCP and instead force static network configuration." msgstr "" "如果您想禁止IPv6自动配置和 DHCP,并强制使用静态网络设置来代替,那么将它设为 " "true。" #. Tag: term #: boot-installer.xml:2001 #, no-c-format msgid "mirror/protocol (protocol)" msgstr "mirror/protocol (protocol)" #. Tag: para #: boot-installer.xml:2002 #, 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:2015 #, no-c-format msgid "tasksel:tasksel/first (tasks)" msgstr "tasksel:tasksel/first (tasks)" #. Tag: para #: boot-installer.xml:2016 #, 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:2030 #, no-c-format msgid "Passing parameters to kernel modules" msgstr "将参数传递给内核模块" #. Tag: para #: boot-installer.xml:2031 #, 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:2044 #, 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:2051 #, 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 (同轴)端子和 IRQ " "10,则需要传递:" #. Tag: screen #: boot-installer.xml:2061 #, no-c-format msgid "3c509.xcvr=3 3c509.irq=10" msgstr "3c509.xcvr=3 3c509.irq=10" #. Tag: title #: boot-installer.xml:2067 #, no-c-format msgid "Blacklisting kernel modules" msgstr "内核模块黑名单" #. Tag: para #: boot-installer.xml:2068 #, 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:2077 #, 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:2085 #, no-c-format msgid "" "Note that a module may still be loaded by the installation system itself. " "You can prevent that from happening by running the installation in expert " "mode and unselecting the module from the list of modules displayed during " "the hardware detection phases." msgstr "" "注意,安装系统自己仍然会加载模块。要阻止这种情况,可以以专家模式来运行安装程" "序,并且在硬件检测阶段中从显示的模块列表中取消该模块。" #. Tag: title #: boot-installer.xml:2101 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "安装过程中的故障修复" #. Tag: title #: boot-installer.xml:2106 #, no-c-format msgid "Reliability of optical media" msgstr "光盘媒体的可靠性" #. Tag: para #: boot-installer.xml:2107 #, no-c-format msgid "" "Sometimes, especially with older drives, the installer may fail to boot from " "an optical disc. The installer may also — even after booting " "successfully from such disc — fail to recognize the disc or return " "errors while reading from it during the installation." msgstr "" "有时,特别是较旧的驱动器,安装程序无法从光盘引导。安装程序还可能 — 即使" "是从这样的光盘成功引导 — 在安装时也无法识别光盘或读取时返回错误。" #. Tag: para #: boot-installer.xml:2114 #, 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:2120 #, no-c-format msgid "There are two very simple things that you should try first." msgstr "首先应试试两种最简单的方法。" #. Tag: para #: boot-installer.xml:2125 #, no-c-format msgid "" "If the disc does not boot, check that it was inserted correctly and that it " "is not dirty." msgstr "如果光盘没有引导,那么检查一下它正确地放置好,并且没有弄脏。" #. Tag: para #: boot-installer.xml:2131 #, no-c-format msgid "" "If the installer fails to recognize the disc, try just running the option " " Detect and mount installation media " " a second time. Some DMA related issues with very old CD-ROM " "drives are known to be resolved in this way." msgstr "" "如果安装程序无法识别光盘,那么再次尝试运行 Detect " "and mount installation media (检测并挂载安装介" "质)选项。有些非常老的 CD-ROM 驱动器的 DMA 相关问题可以用这种方法解决。" #. Tag: para #: boot-installer.xml:2141 #, 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 CD-ROM and DVD." msgstr "" "如果还无法工作,那么尝试下一节建议的方法。多数情况下,但非全部,那里的建议适" "用于 CD-ROM 和 DVD。" #. Tag: para #: boot-installer.xml:2146 #, no-c-format msgid "" "If you cannot get the installation working from optical disc, try one of the " "other installation methods that are available." msgstr "如果您用光盘无法安装,尝试其它可用的安装方法。" #. Tag: title #: boot-installer.xml:2154 #, no-c-format msgid "Common issues" msgstr "常见问题" #. Tag: para #: boot-installer.xml:2157 #, 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:2174 #, no-c-format msgid "" "Some very old CD-ROM drives do not work correctly if direct memory " "access (DMA) is enabled for them." msgstr "" "如果启用 direct memory access(DMA),那么一些非常老的 CD-ROM " "驱动器会无法正常工作。" #. Tag: title #: boot-installer.xml:2185 #, no-c-format msgid "How to investigate and maybe solve issues" msgstr "如何调查研究或许可以解决问题" #. Tag: para #: boot-installer.xml:2186 #, no-c-format msgid "If the optical disc fails to boot, try the suggestions listed below." msgstr "如果从光盘引导失败,那么尝试下面所列的建议。" #. Tag: para #: boot-installer.xml:2191 #, no-c-format msgid "" "Check that your BIOS/UEFI actually supports booting from optical disc (only " "an issue for very old systems) and that booting from such media is enabled " "in the BIOS/UEFI." msgstr "" "检查您的 BIOS/UEFI 真正支持从光盘引导(仅有个别非常老的系统不行),并且在 " "BIOS/UEFI 中启用了从这样的媒体来引导。" #. Tag: para #: boot-installer.xml:2198 #, 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 disc " "matches as well. The following command should work. It uses the size of the " "image to read the correct number of bytes from the disc." msgstr "" "如果您下载的是 iso 映像,那么检查映像的 md5sum 是否与 MD5SUMS 文件中的影响所列的相同,该文件应该位于您下载的映像的相同位置。" "\n" "$ md5sum debian-testing-i386-netinst.iso\n" "a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst." "iso\n" " 然后,检验所刻录光盘的 md5sum 也匹配。可以使用下" "面的命令。它使用映像的尺寸来从光盘读取正确的字节数。" #. Tag: screen #: boot-installer.xml:2211 #, 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:2216 #, no-c-format msgid "" "If, after the installer has been booted successfully, the disc is not " "detected, sometimes simply trying again may solve the problem. If you have " "more than one optical drive, try changing the disc to the other drive. If " "that does not work or if the disc 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 "" "假如在安装程序成功引导之后,没有检测到光盘,那么有时可能简单地再试一次就能解" "决问题。如果有多个光盘驱动器,那么尝试将光盘放到其它驱动器中。如果无法工作," "或者可以识别光盘但读取的时候有错误,那么尝试下面所列的建议。这里需要一些 " "&arch-kernel; 的基本知识。要执行任何命令,应该首先切换到第二虚拟控制台" "(VT2),并在那里激活 shell。" #. Tag: para #: boot-installer.xml:2228 #, 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:2235 #, no-c-format msgid "" "Check in the output of dmesg if your optical drive was " "recognized. You should see something like (the lines do not necessarily have " "to be consecutive): \n" "ata1.00: ATAPI: MATSHITADVD-RAM UJ-822S, 1.61, max UDMA/33\n" "ata1.00: configured for UDMA/33\n" "scsi 0:0:0:0: CD-ROM MATSHITA DVD-RAM UJ-822S 1.61 PQ: 0 ANSI: " "5\n" "sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray\n" "cdrom: Uniform CD-ROM driver Revision: 3.20\n" " If you don't see something like that, chances " "are the controller your drive 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 "" "如果可以识别您的光盘驱动器,那么检查 dmesg 的输出。应该可" "以看到像下面的信息(这些行不必是连续出现的):\n" "ata1.00: ATAPI: MATSHITADVD-RAM UJ-822S, 1.61, max UDMA/33\n" "ata1.00: configured for UDMA/33\n" "scsi 0:0:0:0: CD-ROM MATSHITA DVD-RAM UJ-822S 1.61 PQ: 0 ANSI: " "5\n" "sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray\n" "cdrom: Uniform CD-ROM driver Revision: 3.20\n" " 如果看不到类似的信息,估计是光盘驱动器所连接的控" "制器无法被识别,或者完全不被支持。如果知道控制器所需的驱动程序,可以使用 " "modprobe 来尝试手动加载。" #. Tag: para #: boot-installer.xml:2249 #, no-c-format msgid "" "Check that there is a device node for your optical drive under /" "dev/. In the example above, this would be /dev/sr0. There should also be a /dev/cdrom." msgstr "" "检查在 /dev/ 下面有您光盘驱动器对应的设备节点。上面的示" "例中,它是 /dev/sr0。还会有 /dev/cdrom。" #. Tag: para #: boot-installer.xml:2257 #, no-c-format msgid "" "Use the mount command to check if the optical disc 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 命令来检查光盘是否已经挂载;如果没有,尝试手动" "挂载:\n" "$ mount /dev/hdc /cdrom\n" " 检查命令后面是否有什么错误消息。" #. Tag: para #: boot-installer.xml:2267 #, 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 optical drive." msgstr "" "检查当前 DMA 是否已经启用:\n" "$ cd /proc/ide/hdc\n" "$ grep using_dma settings\n" "using_dma 1 0 1 rw\n" " using_dma 之后第一列的 " "1 意味着将其启用。如果是这样,那么尝试将其禁止:" "\n" "$ echo -n \"using_dma:0\" >settings\n" " 确保您处在与光盘驱动器对应设备的目录中。" #. Tag: para #: boot-installer.xml:2282 #, no-c-format msgid "" "If there are any problems during the installation, try checking the " "integrity of the installation media using the option near the bottom of the " "installer's main menu. This option can also be used as a general test if the " "disc can be read reliably." msgstr "" "如果在安装过程中有什么问题,那么尝试使用靠近安装程序主菜单底部的选项,来检查" "安装介质的完整性。如果光盘可以可靠地读取,那么该选项可以用作通用测试。" #. Tag: title #: boot-installer.xml:2296 #, no-c-format msgid "Boot Configuration" msgstr "引导配置" #. Tag: para #: boot-installer.xml:2298 #, 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:2307 #, no-c-format msgid "" "In some cases, malfunctions can be caused by missing device firmware (see " " and )." msgstr "" "在有些情况下,故障可能由于设备固件的丢失而造成(请参见 )。" #. Tag: para #: boot-installer.xml:2318 #, 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:2329 #, no-c-format msgid "dmesg" msgstr "dmesg" #. Tag: userinput #: boot-installer.xml:2331 #, no-c-format msgid "lspci" msgstr "lspci" #. Tag: userinput #: boot-installer.xml:2333 #, no-c-format msgid "lsmod" msgstr "lsmod" #. Tag: userinput #: boot-installer.xml:2335 #, no-c-format msgid "amixer" msgstr "amixer" #. Tag: title #: boot-installer.xml:2343 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "常见的 &arch-title; 安装问题" #. Tag: para #: boot-installer.xml:2344 #, 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:2389 #, 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 "" "如果您的显示屏在内核引导的时候显示一个奇怪的图片,例如纯白、纯黑或者彩色的像" "素块,那么您的系统可能含有一块有问题的显示卡,它不能切换至帧缓存模式。那么可" "以使用引导参数 fb=false 来禁止使用帧缓存控制台。由于受" "限制的控制台特性,在安装过程中只能使用少数的几种语言,细节请参见 。" #. Tag: title #: boot-installer.xml:2403 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "在 PCMCIA 配置阶段系统死机" #. Tag: para #: boot-installer.xml:2404 #, 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 "" "一些由戴尔生产的非常老的笔记本型号,已知当 PCMCIA 设备检测程序尝试访问某些硬" "件地址的时候崩溃。其它笔记本可能显示类似的问题。如果您遇到那样的问题,并且在" "安装的时候不需要 PCMCIA 的支持,可以用 hw-detect/" "start_pcmcia=false 引导参数来禁止 PCMCIA。然后可以在安装完成后配" "置 PCMCIA,并去掉造成问题的资源区段。" #. Tag: para #: boot-installer.xml:2414 #, 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 "" "或者,可以以专家模式引导安装程序。然后要求您输入硬件所需的资源范围选项。例" "如,如果有如上所说的戴尔笔记本,那么应该在这里输入 exclude port " "0x800-0x8ff。在 System resource settings section of the " "PCMCIA HOWTO 中还列出了一些资源范围选项。注意,在安装程序中输入这个值" "的时候,必须忽略逗号。" #. Tag: title #: boot-installer.xml:2433 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "内核起始消息的注解" #. Tag: para #: boot-installer.xml:2435 #, 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 present(什么东西不见了),can't initialize " "something(什么东西不能初始化)," "或者甚至 this driver release depends on " "something(这个驱动程序版本依赖于" "什么东西)。大多数这些消息都是无害的。之所以看到它们,是因为安装系统的内核被" "构建为运行在具有很多不同外围设备的计算机上。显然,没有一个计算机可能拥有所有" "的外围设备,因此操作系统可能在查找一些您没有的设备时发出一些报怨。有时可以看" "到系统暂停了一段时间。这是由于它在等待一台设备的响应,而这台设备并没有出现在" "您的系统上。如果您发现这个时间长得无法接受,那么以后可以创建一个定制的内核" "(请参见 。" #. Tag: title #: boot-installer.xml:2460 #, no-c-format msgid "Reporting Installation Problems" msgstr "报告安装问题" #. Tag: para #: boot-installer.xml:2461 #, 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 on a storage medium, 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 (存储调试日志)菜单选项。它让您将" "来自安装程序的系统错误日志和配置信息保存到存储介质上,或者用 web 浏览器下载。" "该信息或许提供了一些关于哪里出错和如何修复的线索。如果您正在提交一个 bug 报" "告,可以报告里附上该信息。" #. Tag: para #: boot-installer.xml:2472 #, 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:2483 #, no-c-format msgid "Submitting Installation Reports" msgstr "提交安装报告" #. Tag: para #: boot-installer.xml:2484 #, no-c-format msgid "" "If you still have problems, please submit an installation report (in English " "please, whenever possible). 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:2492 #, 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,即 Debian Bug 跟" "踪系统)上,并转发到公共的邮件列表。请确定您使用的邮件地址可以被公开。" #. Tag: para #: boot-installer.xml:2498 #, 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 (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:2508 #, 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/DVD? USB stick? 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 media: [ ]\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" "\n" "Please make sure that any installation logs that you think would\n" "be useful are attached to this report. (You can find them in the installer\n" "system in /var/log/ and later on the installed system under\n" "/var/log/installer.) Please compress large files using gzip.\n" "\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 "" "另外,在填写安装报告时,您可以采用下列模板,并将其发送到 submit@bugs." "debian.org,也就是通过向 installation-reports " "伪软件包提交 bug 报告的方式提交安装报告。\n" "Package: installation-reports\n" "\n" "Boot method: <How did you boot the installer? CD/DVD? USB stick? 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 media: [ ]\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" "\n" "Please make sure that any installation logs that you think would\n" "be useful are attached to this report. (You can find them in the installer\n" "system in /var/log/ and later on the installed system under\n" "/var/log/installer.) Please compress large files using gzip.\n" "\n" " 在 bug 报告中,请说明问题所在,包括内核挂起时最后" "见到的内核消息。描述进入问题状态所进行的步骤。" #~ msgid "disk-detect/dmraid/enable (dmraid)" #~ msgstr "disk-detect/dmraid/enable (dmraid)" #~ 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(&debian; 安装程序维基)上找到。" #~ msgid "Booting from Windows" #~ msgstr "从 Windows 引导" #~ msgid "To start the installer from Windows, you can either" #~ msgstr "从 Windows 启动安装程序,您可以" #~ msgid "" #~ "obtain installation media as described in or or" #~ msgstr "" #~ "或者按照 中描述的获取安装介" #~ "质," #~ 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。" #~ msgid "" #~ "If you use optical installation media, 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 "" #~ "如果您使用的安装媒介是光盘,那么插入盘片的时候,预安装程序会自动加载。如" #~ "果 Windows 没有自动启动与安装程序,或者在您使用 U 盘的情况下,您可以访问该" #~ "设备并执行 setup.exe 程序来手动启动。" #~ 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; " #~ "安装程序。" #~ msgid "Booting from DOS using loadlin" #~ msgstr "从 DOS 使用 loadlin 引导" #~ msgid "" #~ "Boot into DOS (not Windows). To do this, you can for instance boot from a " #~ "recovery or diagnostic disk." #~ msgstr "引导到 DOS(非 Windows)。您可以从例如恢复或诊断的磁盘来引导。" #~ 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" #~ ",或者确认您已依照 的指引准备好了硬盘,然后根据需要将当前驱动器切换到该硬盘。" #~ 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 "" #~ "进入您选择的子目录,例如 \n" #~ "cd \\&x86-install-dir;\n" #~ "。如果您希望使用图形安装程序,请进入 " #~ "gtk 子目录。\n" #~ "cd gtk\n" #~ "。然后,执行 install.bat。内" #~ "核将会加载并运行安装程序系统。" #~ 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 "" #~ "还有一个可用于网络引导的图形安装程序映像。还有一个特殊的迷你 ISO 映像 迷你 ISO 映像可以" #~ "从 &debian; 镜像下载,这个镜像在 中" #~ "描述。请查找 netboot/gtk/mini.iso ,它主要用于测试。" # index.docbook:437, index.docbook:791, index.docbook:1343, index.docbook:1824, index.docbook:2247, index.docbook:2343 #~ 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:578, index.docbook:951, index.docbook:1764, index.docbook:2018, index.docbook:2372 #~ msgid "Booting from a CD-ROM" #~ msgstr "从 CD-ROM 引导" #~ msgid "CD Contents" #~ msgstr "CD 的内容" #~ 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 组不需要访问网络,就能从大范围的软件包中安装完整的系统。" #~ 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 的下一代可扩展固件界面(EFI)。与传统的 x86 BIOS 只了" #~ "解分区表和主引导记录(MBR)而不知道引导设备不同,EFI 可以对 FAT16 和 " #~ "FAT32 格式化的硬盘分区进行读写操作。这个简化了通常启动系统的神秘过程。系统" #~ "引导加载程序以及支持它的 EFI 固件具有完全的文件系统,来保存引导机器所需的" #~ "必要文件。这意味着在一个 IA-64 系统上的系统磁盘具有一个附加的专用于 EFI 的" #~ "磁盘分区,而不是更传统的系统上简单的 MBR 或者引导块。" #~ 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 读出,说明如下。" #~ 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 分区。" #~ 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 Option " #~ "Maintenance Menu(引导选项维护菜单)EFI Shell " #~ "(Built-in,即内置的)。推荐使用第一个,当然如果该选项不可用,或" #~ "者 CD 由于某种原因没法引导,则使用第二个选项。" #~ msgid "IMPORTANT" #~ msgstr "重要" #~ 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 引导管理程序会在预设的几秒钟后选择默认的启动动作,一般是第一个菜单选" #~ "项。在屏幕底部会有倒计时来指示。一旦超时并且系统开始默认动作,那么会不得不" #~ "重新引导机器来继续安装。如果默认的动作是 EFI Shell,那么可在 shell 提示符" #~ "下运行 exit 来返回引导管理程序。" #~ msgid "Option 1: Booting from the Boot Option Maintenance Menu" #~ msgstr "选项 1:从 Boot Option Maintenance Menu(引导选项维护菜单)引导" #~ 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 (EFI 引导管理程序)页面和菜单。" #~ 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 键。会显示一个新菜单。" #~ 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(可移动介质引导)标签。如果您检查" #~ "菜单行其它部分,会注意到对应的设备和控制器信息应该相同。" #~ 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 的可引导目录列表,要求进行下面的(额" #~ "外)步骤。" #~ 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 键。这将启动引导载入步骤。" #~ 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; 引导程序,它会显示一个菜单页面用于选择启动内核和选" #~ "项。继续来选择启动内核和选项。" #~ msgid "Option 2: Booting from the EFI Shell" #~ msgstr "选项 2:从 EFI Shell 启动" #~ 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 引导管理程序)画面时应当会有个被称为 EFI Shell " #~ "[Built-in](内置) 的选项。按如下步骤来引导 &debian; 安装程序 " #~ "CD:" #~ 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 驱动器,并重新引导机器。固件会在完成系统初始化后,显示 " #~ "EFI Boot Manager(EFI 引导管理程序)页面和菜单。" #~ 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 驱" #~ "动器。" #~ 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 "" #~ "对 shell 查找 CD 驱动器的输出进行检查。它很可能是 fs0: 设备,尽管具有可引导分区的其它设备也会显示成为 " #~ "fsn。" #~ 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 " #~ "是 CDROM 的分区号。Shell 现在将在提示符下显示分区号。" #~ msgid "" #~ "Enter elilo and press ENTER. This " #~ "will start the boot load sequence." #~ msgstr "" #~ "进入 elilo 并按下 ENTER 键。这将启动" #~ "引导步骤。" #~ 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; 引导加载程序,它显示菜单页面供您选择" #~ "引导内核和选项。还可以在 shell 提示符下输入更短的 " #~ "fsn:elilo 命令。继续来选择引" #~ "导内核和选项。" #~ msgid "Installing using a Serial Console" #~ msgstr "使用串口控制台来安装" #~ 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] (VGA 控制台)的选项。要通过串口连接来安装,则选" #~ "择包含 [BAUD baud serial console] (波特串行控" #~ "制台)的选项,其中 BAUD 是串行控制台的连接速" #~ "度。ttyS0 设备上的多数典型波特率设置的菜单项已经预置了。" #~ 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 控制台相同的波特率。如果您不确" #~ "定这个设置是什么,可以在 EFI shell 使用命令 baud 来获" #~ "得。" #~ 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 "" #~ "如果没有想要使用的串行设备或波特率的选项,那么可以用一个现有的菜单选项来覆" #~ "盖控制台设置。例如,要在 ttyS1 设备上使用 57600 波特率,要将 " #~ "console=ttyS1,57600n8 输入到 Boot: 文本窗口。" #~ 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 帮助菜单。" #~ 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 "" #~ "如果选择了错误的控制台类型,那么即便可以选择内核并输入参数,但一旦内核启动" #~ "显示与输入就死掉,就需要在开始安装前重新引导。" #~ msgid "Selecting the Boot Kernel and Options" #~ msgstr "选择引导内核与选项" #~ 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: " #~ "提示符的文本窗口。用方向键从菜单上选择菜单项,并且在键盘上输入的任何字符将" #~ "显示在文本窗口中。输入适当的功能键会显示帮助屏幕。General(一般" #~ "的)帮助屏幕解释了菜单选项,而 Params " #~ "屏幕解释了命令行选项。" #~ 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: 文本窗口中设置的任何另外的参" #~ "数,您选择的内核版本将会用在安装过程和安装好的系统中。如果安装时碰到内核问" #~ "题,在安装好的系统中也会出现。以下两步会选择并开始安装:" #~ msgid "" #~ "Select the kernel version and installation mode most appropriate to your " #~ "needs with the arrow keys." #~ msgstr "使用方向键来选择与您的需要最适合的内核版本与安装模式。" #~ 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 "" #~ "在键盘上输入任何引导参数。这些文本将直接显示在文本窗口中。这是内核参数特定" #~ "的(如串口控制台设置)。" #~ 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; 安装程序的第一个屏幕画面。" #~ msgid "" #~ "Proceed to the next chapter to continue the installation where you will " #~ "set up the language locale, network, and disk partitions." #~ msgstr "继续进入下一章,继续安装来设置语言区域设置、网络和磁盘分区。" #~ 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 驱动器加载。" #~ 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 系统需要两个架构特定的动作。在引导服务器上,必须配置 DHCP " #~ "和 TFTP 来传送 elilo。在客户端的 EFI 引导管理程序中必须" #~ "定义新的引导选项,从而允许在网络上加载。" #~ msgid "Configuring the Server" #~ msgstr "配置服务器" #~ 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。" #~ 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 "" #~ "将 netboot.tar.gz 文件解压到用作您 tftp 服务器的根的" #~ "目录中。典型的 tftp 根目录包括 /var/lib/tftp 和 " #~ "/tftpboot。这将创建 debian-installer 目录树,它包含 IA-64 系统的引导文件。" #~ 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" #~ "[...]" #~ 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/ 目录中找到。可以使不同的客" #~ "户端具有不同的配置文件,只要通过带有.conf 后缀而非 " #~ "elilo.conf 后缀的16进制客户端 IP 地址来命名这些文件即" #~ "可 。细节请查看 elilo 软件包中提供的文档。" #~ msgid "Configuring the Client" #~ msgstr "配置客户端" #~ 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(引导选项维护菜单) 来开始。" #~ " Add a boot option(添加引导选项)。 您会看到一行或多行 Load " #~ "File [Acpi()/.../Mac()] 文本。如果多于一个入口存在,那么选择" #~ "一个网卡,它包含您想要从中引导 MAC 地址。使用方向键使您的选择高亮,然后按" #~ "回车。 Name the entry(命名入口为)" #~ "Netboot 或相似,保存然后退回至引导选项菜单。 您现在应该能够看到刚刚创建的新引导选项," #~ "选择它应该会初始化一个 DHCP 查询,导致从服务器上进行 elilo.efi 的 TFTP 加载。" #~ 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 "" #~ "在下载并且处理配置文件后,引导加载程序将显示它的提示符。从这里开始,安装过" #~ "程将以 CD 安装同样的步骤进行。如上选择引导选项,并且内核已经完成从网络上的" #~ "自我安装后,将开始 &debian; 安装程序。" #~ 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:" #~ "bootpboot net:dhcp 从一个 TFTP 和 " #~ "BOOTP 或 DHCP 服务器上引导。您可以在 boot 命令结束" #~ "后将额外的引导参数传递给 &d-i;。" #~ 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 的系统的第二主硬" #~ "盘)。" #~ msgid "IDPROM Messages" #~ msgstr "IDPROM 消息" #~ 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。" #~ 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 "" #~ "对于 &arch-title;,目前只有一个实验性的迷你 ISO镜像可用" #~ " 迷你 ISO 映像可以从 &debian; " #~ "镜像下载,这个镜像在 中描述。请查找 " #~ "netboot/gtk/mini.iso 。它应该可以" #~ "在几乎所有具有 ATI 显卡的 PowerPC 系统上工作,但不太可能在其它系统上工作。" #~ 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。" #~ msgid "Such problems have been reported on hppa." #~ msgstr "已经在 hppa 上面报告过这样的问题。" #~ 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 "" #~ "由于某些系统上的显示问题,帧缓存的支持在 &arch-title; 上默认是禁" #~ "止的。这导致对帧缓存支持良好的的系统显示得很丑陋,如那些采用 " #~ "ATI 显卡的系统。如果在安装程序中遇到显示问题,可以尝试以参数 " #~ "debian-installer/framebuffer=true 或简写为 " #~ "fb=true 来引导。" #~ msgid "" #~ "There are some common installation problems that are worth mentioning." #~ msgstr "有一些常见的安装问题值得解释一下。" #~ msgid "Misdirected video output" #~ msgstr "错误的视频输出" #~ 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 来引导安装程序。" #~ 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 中的视频驱动程序。" #~ msgid "Failure to Boot or Install from CD-ROM" #~ msgstr "从 CD-ROM 上引导或安装失败" #~ 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 系统被报告了很多问题。" #~ msgid "We recommend to install such systems by netbooting the installer." #~ msgstr "我们推荐通过网络引导安装程序来安装这些系统。" #~ 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。这将允许您重新分区用于引导的硬盘,需要小心操作。" #, fuzzy #~| 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." #~ 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 an " #~ "installation image to the hard drive (make sure the file is named ending " #~ "in .iso). The installer can then boot from the hard " #~ "drive and install from the installation image, without needing the " #~ "network." #~ msgstr "" #~ "另一种方法,可以在安装时保持原硬盘的分区不变,您需要下载 hd-" #~ "media/initrd.gz 文件以及对应的内核,还需要一个 CD(或者 DVD) " #~ "iso 文件的副本放在硬盘上(确认文件名是以 .iso 结尾" #~ "的)。这样安装程序就可以从硬盘引导,并从 CD/DVD 映像文件上安装,而不使用网" #~ "络。" #~ 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 的例子:" #~ 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" #~ msgid "" #~ "For more details, refer to the initrd 4 and " #~ "lilo.conf 5 man pages. Now run lilo " #~ "and reboot." #~ msgstr "" #~ "欲获知更多细节,请参见 initrd 4 和 " #~ "lilo.conf 5 man 手册。现在运行 lilo " #~ "并且重新启动。" #~ 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 位于系统中第一个磁盘的第一个分区上面):" #~ 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" #~ 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 文件。安装程序的入口,例如:" #~ msgid "" #~ "From here on, there should be no difference between GRUB or LILO." #~ msgstr "" #~ "从这里开始,下面采用 GRUBLILO 将" #~ "没有什么差别。" #~ msgid "CD-ROM Reliability" #~ msgstr "CD-ROM 的可靠性" # index.docbook:723, index.docbook:1876, index.docbook:2278, index.docbook:2426 #~ msgid "Booting from Floppies" #~ msgstr "从软盘引导" # index.docbook:724, index.docbook:2286 #~ msgid "" #~ "You will have already downloaded the floppy images you needed and created " #~ "floppies from the images in ." #~ msgstr "" #~ "您可能已经下载了所需要的软盘映像,并且根据从映像创建了软盘。" #~ 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 "" #~ "从软盘引导安装程序需要放置软盘至主软驱。按照您平时的习惯关闭系统,然后重新" #~ "打开。" #~ 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 设备,那么在提示符下输入 install root=/dev/hdc。" #~ 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 系统上),将没" #~ "有这样的选择。在其它情况下,请在引导时使用硬重启。" #~ 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: 提示符。" #~ 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..." #~ ",然后是一些有关系统硬件的信息。更多有关这段引导过程的信" #~ "息,在下面的可以找到。" #~ 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 会自动加载。" #~ 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 键,或者 CommandOption、" #~ "ShiftDelete 组合键引导出厂默认的 CD/" #~ "DVD 驱动器。" #~ 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 驱动器,键入" #~ msgid "0 > boot cd:,\\install\\yaboot" #~ msgstr "0 > boot cd:,\\install\\yaboot" #~ 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 上选择所需要的文件。" #~ 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 提示符后,键入" #~ msgid "boot cd install/pegasos" #~ msgstr "boot cd install/pegasos" #~ 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 提示符后,键入" #~ msgid "0 > boot cdrom" #~ msgstr "0 > boot cdrom" #~ msgid "Booting from Hard Disk" #~ msgstr "从硬盘引导" # index.docbook:1591, index.docbook:2097 #~ 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 #~ msgid "" #~ "To boot the installer from hard disk, you will have already completed " #~ "downloading and placing the needed files as described in ." #~ msgstr "" #~ "如果要从硬盘上引导安装程序,您需要参考 下载并且安置所需文件。" #~ msgid "Booting OldWorld PowerMacs from MacOS" #~ msgstr "从 OldWorld PowerMacs 的 MacOS 上引导" #~ 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 以及启动安装" #~ "程序。" #~ msgid "Booting NewWorld Macs from OpenFirmware" #~ msgstr "从 NewWorld Macs 的 OpenFirmware 引导" #~ 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.gzyabootyaboot.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 #~ msgid "Booting from USB memory stick" #~ msgstr "从 U 盘引导" #~ msgid "" #~ "Currently, NewWorld PowerMac systems are known to support USB booting." #~ msgstr "当前,New World PowerMac 系统支持从 USB 引导。" #~ 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 提示符。参阅 。" #~ 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。" #~ 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。" #~ 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;。" #~ 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 系统上工作。如果您遇到问题,请" #~ "写下安装报告,参阅 。" #~ msgid "Currently, PReP and New World PowerMac systems support netbooting." #~ msgstr "目前来说,PReP 以及 New World PowerMac 系统支持网络引导。" #~ 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 命令可以给出语法和选项的说明。" #~ 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 软盘并不支持引导。" #~ 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 软盘引导,请在关闭系统后" #~ "在按下电源开关前把它放到软盘驱动器内。" #~ 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 软盘操作的人来说:一个放在软驱的软盘将获得第一优先引" #~ "导顺序。一个没有有效引导系统的软盘将回被弹出,并且机器将检查硬盘分区。" #~ 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;。安装程序将在根系统被装入内存后自动启动。" #~ msgid "PowerPC Boot Parameters" #~ msgstr "PowerPC 引导参数" #~ 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。" #~ msgid "INSTALL_MEDIA_DEV" #~ msgstr "INSTALL_MEDIA_DEV" #~ 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" #~ 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 "" #~ "引导软盘通常会扫描所有的软盘来找到根软盘,可以通过此参数设置只查找一个设" #~ "备。" #~ msgid "Floppy Disk Reliability" #~ msgstr "软盘的可靠性" #~ msgid "" #~ "The biggest problem for people using floppy disks to install &debian; " #~ "seems to be floppy disk reliability." #~ msgstr "" #~ "对于用软盘安装 &debian; 的人来说,他们遇到的最大的问题很可能是软盘的可靠" #~ "性。" #~ 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 错误信息。" #~ 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 "" #~ "如果在某个软盘上遇到安装停止,您首先要做的,是把映像重新写到另外" #~ "一张软盘上,看看是否解决问题。仅格式化旧软盘是不够的,即使它重" #~ "新格式化以后看起来没有错误。如果可能,在别的统上重写这些软盘更好一些。" #~ 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 "" #~ "有一个用户报告他不得不把映像往软盘写次,只有最后一" #~ "次的软盘才算工作良好。" #~ 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 来检验下载的映像是否正确。" #~ 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 "" #~ "其他一些用户报告过,用同样的软盘重新启动若干次才有一次能成功引导。这都是由" #~ "于有缺陷的硬件或固件软盘驱动器驱动程序造成的。" #~ 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 变量。"