# Debian GNU/Linux Installation Guide msgid "" msgstr "" "Project-Id-Version: d-i-manual\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" "POT-Creation-Date: 2006-12-26 01:54+0000\n" "PO-Revision-Date: 2006-11-27 09:30+0800\n" "Last-Translator: Ji YongGang\n" "Language-Team: debian-chinese-gb \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Tag: title #: boot-installer.xml:4 #, no-c-format msgid "Booting the Installation System" msgstr "用安装系统启动" #. Tag: title #: boot-installer.xml:9 #, no-c-format msgid "Booting the Installer on &arch-title;" msgstr "在 &arch-title; 上引导安装程序" #. Tag: title #: boot-installer.xml:20 #, no-c-format msgid "Alpha Console Firmware" msgstr "Alpha 控制台固件" #. Tag: para #: boot-installer.xml:21 #, no-c-format msgid "" "Console firmware is stored in a flash ROM and started when an Alpha system " "is powered up or reset. There are two different console specifications used " "on Alpha systems, and hence two classes of console firmware available:" msgstr "" "控制台固件是保存在一个闪存 ROM 中并且每次在 Alpha 系统加电或者重启的时候启" "动。在 Alpha 系统上有两种规格的控制台,并且因此有两类控制台固件供使用。" #. Tag: para #: boot-installer.xml:31 #, no-c-format msgid "" "SRM console, based on the Alpha Console Subsystem " "specification, which provides an operating environment for OpenVMS, Tru64 " "UNIX, and Linux operating systems." msgstr "" "SRM console 基于 Alpha 控制台子系统规范。它为 OpenVMS," "Tru64 Unix,以及 Linux 操作系统提供了一个操作环境。" #. Tag: para #: boot-installer.xml:38 #, no-c-format msgid "" "ARC, AlphaBIOS, or ARCSBIOS console, based on the " "Advanced RISC Computing (ARC) specification, which provides an operating " "environment for Windows NT." msgstr "" "ARC, AlphaBIOS 或 ARCSBIOS console 基于 Advanced RISC " "Computing (ARC) 规范。它为 Windows NT 提供了一个操作环境。" #. Tag: para #: boot-installer.xml:47 #, no-c-format msgid "" "From the user's perspective, the most important difference between SRM and " "ARC is that the choice of console constrains the possible disk-partitioning " "scheme for the hard disk which you wish to boot off of." msgstr "" "按照用户的角度看,SRM 和 ARC 最重要的区别,是控制台的选择,可能会影响到您需要" "引导的磁盘分区方法。" #. Tag: para #: boot-installer.xml:54 #, no-c-format msgid "" "ARC requires that you use an MS-DOS partition table (as created by " "cfdisk) for the boot disk. Therefore MS-DOS partition " "tables are the native partition format when booting from ARC. " "In fact, since AlphaBIOS contains a disk partitioning utility, you may " "prefer to partition your disks from the firmware menus before installing " "Linux." msgstr "" "ARC 需要您为引导磁盘使用一个 MS-DOS 分区表(用 cfdisk 创" "建)。因此从 ARC 引导则 MS-DOS 分区表是作为原始的分区格式 ARC。" "事实上,由于 AlphaBIOS 包含了一个磁盘分区工具,您也许可以在安装 Linux 时,通" "过固件菜单对磁盘进行分区。" #. Tag: para #: boot-installer.xml:63 #, no-c-format msgid "" "Conversely, SRM is incompatible " "Specifically, the bootsector format required by the Console Subsystem " "Specification conflicts with the placement of the DOS partition table. with MS-DOS partition tables. Since Tru64 Unix uses the " "BSD disklabel format, this is the native partition format for " "SRM installations." msgstr "" "保守地说,SRM 是 不兼容 MS-DOS 分区表。 " "具体来说,控制台子系统规范与需要的引导扇区格式和 DOS 分区表有冲突。由于 Tru64 Unix 使用的是 BSD 磁盘标记格式,对于SRM 安装来说,这是一" "个原始的分区格式。" #. Tag: para #: boot-installer.xml:76 #, no-c-format msgid "" "GNU/Linux is the only operating system on Alpha that can be booted from both " "console types, but &debian; &release; only supports booting on SRM-based " "systems. If you have an Alpha for which no version of SRM is available, if " "you will be dual-booting the system with Windows NT, or if your boot device " "requires ARC console support for BIOS initialization, you will not be able " "to use the &debian; &release; installer. You can still run &debian; " "&release; on such systems by using other install media; for instance, you " "can install Debian woody with MILO and upgrade." msgstr "" "由于 GNU/Linux 是唯一能够通过两种控制台格式引导的系统,这个问题就取决于您想在" "机器上面运行什么样的其他操作系统。所有的其他 Unix 型的操作系统 (Tru64 Unix," "FreeBSD,OpenBSD,以及 NetBSD) 和 OpenVMS 只能从 SRM 上面引导,而 Windows NT " "只能从 ARC 上面引导。" #. Tag: para #: boot-installer.xml:87 #, no-c-format msgid "" "Because MILO is not available for any of the Alpha " "systems currently in production (as of February 2000), and because it is no " "longer necessary to buy an OpenVMS or Tru64 Unix license to have SRM " "firmware on your older Alpha, it is recommended that you use SRM when " "possible." msgstr "" "由于 MILO 在当前生产型 Alpha 系统上并没有实现(从 2000 年二" "月份开始)。并且也不需要购买一个 OpenVMS 和 Tru64 Unix 授权,来在老 Alpha 上装" "上 SRM 固件。我们推荐在新的机器上使用 SRM。" #. Tag: para #: boot-installer.xml:95 #, no-c-format msgid "" "The following table summarizes available and supported system type/console " "combinations (see for the system type names). " "The word ARC below denotes any of the ARC-compliant consoles." msgstr "" "下面表格总结了可用以及支持的系统类型/控制台组合(系统类型名称参见 )。单词 ARC 注明任何和 ARC 兼容的控制" "台。" #. Tag: entry #: boot-installer.xml:107 #, no-c-format msgid "System Type" msgstr "系统类型" #. Tag: entry #: boot-installer.xml:108 #, no-c-format msgid "Console Type Supported" msgstr "支持的控制台类型" #. Tag: entry #: boot-installer.xml:114 #, no-c-format msgid "alcor" msgstr "alcor" # index.docbook:110, index.docbook:113, index.docbook:119, index.docbook:125, index.docbook:128, index.docbook:131, index.docbook:134, index.docbook:140, index.docbook:143, index.docbook:146, index.docbook:155, index.docbook:164, index.docbook:179, index.docbook:182, index.docbook:188 #. Tag: entry #: boot-installer.xml:115 boot-installer.xml:118 boot-installer.xml:124 #: boot-installer.xml:130 boot-installer.xml:133 boot-installer.xml:136 #: boot-installer.xml:139 boot-installer.xml:145 boot-installer.xml:148 #: boot-installer.xml:151 boot-installer.xml:160 boot-installer.xml:169 #: boot-installer.xml:184 boot-installer.xml:187 #, no-c-format msgid "ARC or SRM" msgstr "ARC or SRM" #. Tag: entry #: boot-installer.xml:117 #, no-c-format msgid "avanti" msgstr "avanti" #. Tag: entry #: boot-installer.xml:120 #, no-c-format msgid "book1" msgstr "book1" # index.docbook:116, index.docbook:122, index.docbook:137, index.docbook:149, index.docbook:158, index.docbook:161, index.docbook:167, index.docbook:173, index.docbook:176 #. Tag: entry #: boot-installer.xml:121 boot-installer.xml:127 boot-installer.xml:142 #: boot-installer.xml:154 boot-installer.xml:163 boot-installer.xml:166 #: boot-installer.xml:172 boot-installer.xml:178 boot-installer.xml:181 #, no-c-format msgid "SRM only" msgstr "SRM only" #. Tag: entry #: boot-installer.xml:123 #, no-c-format msgid "cabriolet" msgstr "cabriolet" #. Tag: entry #: boot-installer.xml:126 #, no-c-format msgid "dp264" msgstr "dp264" #. Tag: entry #: boot-installer.xml:129 #, no-c-format msgid "eb164" msgstr "eb164" #. Tag: entry #: boot-installer.xml:132 #, no-c-format msgid "eb64p" msgstr "eb64p" #. Tag: entry #: boot-installer.xml:135 #, no-c-format msgid "eb66" msgstr "eb66" #. Tag: entry #: boot-installer.xml:138 #, no-c-format msgid "eb66p" msgstr "eb66p" #. Tag: entry #: boot-installer.xml:141 #, no-c-format msgid "jensen" msgstr "jensen" #. Tag: entry #: boot-installer.xml:144 #, no-c-format msgid "lx164" msgstr "lx164" #. Tag: entry #: boot-installer.xml:147 #, no-c-format msgid "miata" msgstr "miata" #. Tag: entry #: boot-installer.xml:150 #, no-c-format msgid "mikasa" msgstr "mikasa" #. Tag: entry #: boot-installer.xml:153 #, no-c-format msgid "mikasa-p" msgstr "mikasa-p" #. Tag: entry #: boot-installer.xml:156 #, no-c-format msgid "nautilus" msgstr "nautilus" #. Tag: entry #: boot-installer.xml:157 #, no-c-format msgid "ARC (see motherboard manual) or SRM" msgstr "ARC (see motherboard manual) or SRM" #. Tag: entry #: boot-installer.xml:159 #, no-c-format msgid "noname" msgstr "noname" #. Tag: entry #: boot-installer.xml:162 #, no-c-format msgid "noritake" msgstr "noritake" #. Tag: entry #: boot-installer.xml:165 #, no-c-format msgid "noritake-p" msgstr "noritake-p" #. Tag: entry #: boot-installer.xml:168 #, no-c-format msgid "pc164" msgstr "pc164" #. Tag: entry #: boot-installer.xml:171 #, no-c-format msgid "rawhide" msgstr "rawhide" #. Tag: entry #: boot-installer.xml:174 #, no-c-format msgid "ruffian" msgstr "ruffian" # index.docbook:170, index.docbook:185 #. Tag: entry #: boot-installer.xml:175 boot-installer.xml:190 boot-installer.xml:193 #, no-c-format msgid "ARC only" msgstr "ARC only" #. Tag: entry #: boot-installer.xml:177 #, no-c-format msgid "sable" msgstr "sable" #. Tag: entry #: boot-installer.xml:180 #, no-c-format msgid "sable-g" msgstr "sable-g" #. Tag: entry #: boot-installer.xml:183 #, no-c-format msgid "sx164" msgstr "sx164" #. Tag: entry #: boot-installer.xml:186 #, no-c-format msgid "takara" msgstr "takara" #. Tag: entry #: boot-installer.xml:189 #, no-c-format msgid "xl" msgstr "xl" #. Tag: entry #: boot-installer.xml:192 #, no-c-format msgid "xlt" msgstr "xlt" #. Tag: para #: boot-installer.xml:200 #, no-c-format msgid "" "Generally, none of these consoles can boot Linux directly, so the assistance " "of an intermediary bootloader is required. For the SRM console, " "aboot, a small, platform-independent bootloader, is used. " "See the (unfortunately outdated) SRM HOWTO for more information on aboot." msgstr "" "一般来说,这些控制台都不能直接引导 Linux ,因此需要一个中间引导装载程序。对" "于 SRM 控制台,aboot,小型的,平台独立的引导装载器。参见" "(抱歉的是它也有点过时了)SRM HOWTO 来获" "得更多有关信息 aboot。" #. Tag: para #: boot-installer.xml:209 #, no-c-format msgid "" "The following paragraphs are from the woody install manual, and are included " "here for reference; they may be useful to someone at a later date when " "Debian supports MILO-based installs again." msgstr "" "以下章节来自 woody 安装手册,放在这里作为参考;如果以后 Debian 再支持基于 " "MILO 的安装,它们对某些人或许有用。" #. Tag: para #: boot-installer.xml:215 #, no-c-format msgid "" "Generally, none of these consoles can boot Linux directly, so the assistance " "of an intermediary bootloader is required. There are two mainstream Linux " "loaders: MILO and aboot." msgstr "" "一般来说,这些控制台都不能直接引导 Linux,因此需要一个中间引导装载程序。这里" "有两个主要的 Linux 装载程序: MILOaboot。" #. Tag: para #: boot-installer.xml:221 #, no-c-format msgid "" "MILO is itself a console, which replaces ARC or SRM in " "memory. MILO can be booted from both ARC and SRM and is " "the only way to bootstrap Linux from the ARC console. MILO is platform-specific (a different MILO is needed " "for each system type) and exist only for those systems, for which ARC " "support is shown in the table above. See also the (unfortunately outdated) " "MILO HOWTO." msgstr "" "MILO 自己本身是一个用来替换载入内存中的 ARC 和 SRM 的控制" "台。MILO 能够同时从 ARC 和 SRM 引导并且是唯一一种方法从 " "ARC 控制台引导 Linux。MILO 取决与具体的平台。(对于每种不同" "的系统类型需要不同的 MILO 并且只适合这些系统。参见(很遗憾" "有点过时)MILO HOWTO。" #. Tag: para #: boot-installer.xml:231 #, no-c-format msgid "" "aboot is a small, platform-independent bootloader, which " "runs from SRM only. See the (also unfortunately outdated) SRM HOWTO for more information on aboot." msgstr "" "aboot 是一个小型的,平台独立的引导装载器,不过只运行与 " "SRM 上。参见 (抱歉的是它也有点过时了 ) SRM " "HOWTO来获得更多有关信息 aboot。" #. Tag: para #: boot-installer.xml:238 #, no-c-format msgid "" "Thus, three scenarios are generally possible, depending on the system's " "console firmware and whether or not MILO is available: " "\n" "SRM -> aboot\n" "SRM -> MILO\n" "ARC -> MILO\n" " Because MILO is not available " "for any of the Alpha systems currently in production (as of February 2000), " "and because it is no longer necessary to buy an OpenVMS or Tru64 Unix " "license to have SRM firmware on your older Alpha, it is recommended that you " "use SRM and aboot on new installations of GNU/Linux, " "unless you wish to dual-boot with Windows NT." msgstr "" "因此,三种方案都是可行的,取决与系统控制台固件以及是否有相应的 " "MILO\n" "SRM -> aboot\n" "SRM -> MILO\n" "ARC -> MILO\n" " 由于 MILO 在当前生产型 Alpha " "系统上并没有实现(从 2000 年二月份开始)。并且也不需要购买一个 OpenVMS 和 " "Tru64 Unix 授权,来在老 Alpha 上装上 SRM 固件。除非您想采用 Windows NT 并且进" "行双引导,我们推荐在新的机器上使用 SRM 和 aboot 安装 " "Linux。" #. Tag: para #: boot-installer.xml:253 #, no-c-format msgid "" "The majority of AlphaServers and all current server and workstation products " "contain both SRM and AlphaBIOS in their firmware. For half-flash machines such as the various evaluation boards, it is possible to " "switch from one version to another by reflashing the firmware. Also, once " "SRM is installed, it is possible to run ARC/AlphaBIOS from a floppy disk " "(using the arc command). For the reasons mentioned above, " "we recommend switching to SRM before installing &debian;." msgstr "" "大部分 AlphaServers 以及目前所有的服务器以及工作站产品固件中都同时含有 SRM " "和 AlphaBIOS。对于具有不同开发板的 half-flash 机器来说。可以通" "过重刷固件 来从一个版本切换到另外一个版本。并且一旦 SRM 安装完毕,从软盘上运" "行 ARC/AlphaBIOS 也是可能的(使用 arc)。基于上述的理由,我" "们推荐在安装 &debian; 之前切换至 SRM。" #. Tag: para #: boot-installer.xml:264 #, no-c-format msgid "" "As on other architectures, you should install the newest available revision " "of the firmware Except on Jensen, where Linux is not " "supported on firmware versions newer than 1.7 — see for more information. before " "installing &debian;. For Alpha, firmware updates can be obtained from Alpha Firmware Updates." msgstr "" "和另外的体系结构一样,您也应该在安装 &debian; 之前安装最新版本的固件" "不包括 Jensen,1.7 以上版本的固件不支持 Linux — 查看 " " 以获得更多的信息。。对于 Alpha 来说,固件升级可以通过 Alpha Firmware Updates取得。" # 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:283 boot-installer.xml:999 boot-installer.xml:1490 #: boot-installer.xml:1985 boot-installer.xml:2067 boot-installer.xml:2156 #: boot-installer.xml:2500 boot-installer.xml:2596 #, no-c-format msgid "Booting with TFTP" msgstr "用 TFTP 引导" #. Tag: para #: boot-installer.xml:284 #, no-c-format msgid "" "In SRM, Ethernet interfaces are named with the ewa " "prefix, and will be listed in the output of the show dev command, like this (edited slightly): \n" ">>> show dev\n" "ewa0.0.0.9.0 EWA0 08-00-2B-86-98-65\n" "ewb0.0.0.11.0 EWB0 08-00-2B-86-98-54\n" "ewc0.0.0.2002.0 EWC0 00-06-2B-01-32-B0\n" " You first need to set the boot protocol: " "\n" ">>> set ewa0_protocols bootp\n" " Then check the medium type is correct: " "\n" ">>> set ewa0_mode mode\n" " You can get a listing of valid modes with " ">>>set ewa0_mode." msgstr "" "在 SRM 上,以太网界面名字带有 ewa 前缀,并可以用 " "show dev 命令列出,类似如下显示(可能有一点不同): " "\n" ">>> show dev\n" "ewa0.0.0.9.0 EWA0 08-00-2B-86-98-65\n" "ewb0.0.0.11.0 EWB0 08-00-2B-86-98-54\n" "ewc0.0.0.2002.0 EWC0 00-06-2B-01-32-B0\n" " 您首先需要设置引导协议: " "\n" ">>> set ewa0_protocol bootp\n" " 然后检查媒介类型是否正确: " "\n" ">>> set ewa0_mode mode\n" " 获得一个有效模式的列表 >>>" "set ewa0_mode。" #. Tag: para #: boot-installer.xml:302 #, no-c-format msgid "" "Then, to boot from the first Ethernet interface, you would type: " "\n" ">>> boot ewa0 -flags \"\"\n" " This will boot using the default kernel " "parameters as included in the netboot image." msgstr "" "接下来,如果从第一个以太网界面引导,您需要输入: \n" ">>> boot ewa0 -flags \"\"\n" " 这将 netboot 映象启动,并使用默认的内核参数。" #. Tag: para #: boot-installer.xml:311 #, no-c-format msgid "" "If you wish to use a serial console, you must pass the " "console= parameter to the kernel. This can be done " "using the -flags argument to the SRM boot command. The serial ports are named the same as their " "corresponding files in /dev. Also, when specifying " "additional kernel parameters, you must repeat certain default options that " "are needed by the &d-i; images. For example, to boot from ewa0 and use a console on the first serial port, you would type:" msgstr "" "如果希望使用一个串行控制台,您 必须 给内核传递 " "console= 参数。这个工作可以使用附带 -" "flags 参数的 SRM boot 命令来完成。串口号的" "命名和它们在目录 /dev 中相同。另外,如有指定额外的内核" "参数,也必须给 &d-i; 映象重复指定。比如,如果需要从 ewa0 引导,并且在第一个串口使用控制台,您需要输入:" #. Tag: screen #: boot-installer.xml:323 #, no-c-format msgid "" ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " "console=ttyS0"" msgstr "" ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " "console=ttyS0"" #. Tag: title #: boot-installer.xml:328 #, no-c-format msgid "Booting from CD-ROM with the SRM Console" msgstr "采用 SRM 控制台来从 CD 光盘上引导" #. Tag: para #: boot-installer.xml:329 #, no-c-format msgid "" "Type \n" ">>> boot xxxx -flags 0\n" " where xxxx is your CD-" "ROM drive in SRM notation." msgstr "" "输入 \n" ">>> boot xxxx -flags 0\n" " 这里 xxxx 是您的光盘驱" "动器在 SRM 的符号。" #. Tag: title #: boot-installer.xml:341 #, no-c-format msgid "Booting from CD-ROM with the ARC or AlphaBIOS Console" msgstr "通过 ARC 或者 AlphaBIOS 控制台来从 CD 光盘上启动" #. Tag: para #: boot-installer.xml:342 #, no-c-format msgid "" "To boot a CD-ROM from the ARC console, find your sub-architecture code name " "(see ), then enter \\milo\\linload." "exe as the boot loader and \\milo" "\\subarch (where subarch is the proper subarchitecture name) as the OS Path in the `OS " "Selection Setup' menu. Ruffians make an exception: You need to use " "\\milo\\ldmilo.exe as boot loader." msgstr "" "为了从 ARC 控制台引导 CD 光盘,找出您的子体系结构代码名称(参见 ),然后输入 \\milo\\linload.exe 作为引导" "装载器并且在 `OS Selection Setup' 菜单下选择 \\milo" "\\subarch (这里 subarch 是相应的子体系结构名称)作为操作系统路径。Ruffians 则是一个例外:" "您需要使用 \\milo\\ldmilo.exe 作为引导装载器。" #. Tag: title #: boot-installer.xml:358 #, no-c-format msgid "Booting from Floppies with the SRM Console" msgstr "通过 SRM 控制台从软盘引导" #. Tag: para #: boot-installer.xml:359 #, no-c-format msgid "" "At the SRM prompt (>>>), issue the following " "command: \n" ">>> boot dva0 -flags 0\n" " possibly replacing dva0 " "with the actual device name. Usually, dva0 is the " "floppy; type \n" ">>> show dev\n" " to see the list of devices (e.g., if you want to " "boot from a CD). Note that if you are booting via MILO, -flags argument is ignored, so you can just type boot dva0. If everything works OK, you will eventually see the Linux kernel " "boot." msgstr "" "在 SRM 提示符下 (>>>),使用如下命令: " "\n" ">>> boot dva0 -flags 0\n" " 可以用实际的设备名称来替换 dva0。通常情况下,dva0 是软盘;输入 " "\n" ">>> show dev\n" " 来查看设备列表(比如,如果您想从一张 CD 上面引" "导)。注意如果您想通过 MILO 引导 -flags 参数将被忽略,因此" "您可以只需输入 boot dva0。如果上面步骤工作正常,您将最终看" "到 Linux 内核引导。" #. Tag: para #: boot-installer.xml:376 #, no-c-format msgid "" "If you want to specify kernel parameters when booting via aboot, use the following command: \n" ">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " "load_ramdisk=1 arguments\"\n" " (typed on one line), substituting, if necessary, " "the actual SRM boot device name for dva0, the Linux " "boot device name for fd0, and the desired kernel " "parameters for arguments." msgstr "" "如果您想在通过 aboot 引导的时候指定特定的内核参数,请使用" "如下命令: \n" ">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " "load_ramdisk=1 arguments\"\n" " (输入到一行),如果需要,替换 dva0 的真实 SRM 引导设备名 dva0fd0 的 Linux 引导设备名,arguments 需要的内核参" "数。" #. Tag: para #: boot-installer.xml:388 #, no-c-format msgid "" "If you want to specify kernel parameters when booting via MILO, you will have to interrupt bootstrap once you get into MILO. See " "." msgstr "" "如果您想在通过 MILO 启动时指定内核参数,您必须在进入 MILO " "时中断引导。参阅 。" #. Tag: title #: boot-installer.xml:398 #, no-c-format msgid "Booting from Floppies with the ARC or AlphaBIOS Console" msgstr "在 ARC 或者 AlphaBISO 控制台下从软盘引导" #. Tag: para #: boot-installer.xml:400 #, no-c-format msgid "" "In the OS Selection menu, set linload.exe as the boot " "loader, and milo as the OS Path. Bootstrap using the " "newly created entry." msgstr "" "在操作系统选择菜单内,设置 linload.exe 作为引导装载器,并" "且 milo 作为操作系统参数。然后使用这个最近建立的选项启动。" #. Tag: title #: boot-installer.xml:409 #, no-c-format msgid "Booting with MILO" msgstr "采用 MILO 引导" #. Tag: para #: boot-installer.xml:410 #, no-c-format msgid "" "MILO contained on the bootstrap media is configured to proceed straight to " "Linux automatically. Should you wish to intervene, all you need is to press " "space during MILO countdown." msgstr "" "自我启动介质上的 MILO 会自动直接进入 Linux 引导过程。如果您要对此有所控制,只" "需要在 MILO 倒计时时按下空格键。" #. Tag: para #: boot-installer.xml:416 #, no-c-format msgid "" "If you want to specify all the bits explicitly (for example, to supply " "additional parameters), you can use a command like this: " "\n" "MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" " If you are booting from something other than a " "floppy, substitute fd0 in the above example with the " "appropriate device name in Linux notation. The help " "command would give you a brief MILO command reference." msgstr "" "如果您想显式指定所有的位(比如,支持附加的参数),您可以使用像下面形式的命令: " "\n" "MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" " 如果通过软盘之外别的方法引导,在 Linux 标记下把上" "面例子中的 fd0 替换成合适的设备名称。help 命令将给出一个简单的 MILO 命令参考。" #. Tag: title #: boot-installer.xml:435 #, no-c-format msgid "Booting from 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:441 boot-installer.xml:1005 boot-installer.xml:1508 #: boot-installer.xml:1991 boot-installer.xml:2506 boot-installer.xml:2602 #, no-c-format msgid "" "Booting from the network requires that you have a network connection and a " "TFTP network boot server (DHCP, RARP, or BOOTP)." msgstr "" "从网络引导需要您已经具备网络的连接和一台 TFTP 网络引导服务器(DHCP, RARP 以及 " "BOOTP)。" # index.docbook:437, index.docbook:791, index.docbook:1343, index.docbook:1824, index.docbook:2247, index.docbook:2343 #. Tag: para #: boot-installer.xml:446 boot-installer.xml:1010 boot-installer.xml:1513 #: boot-installer.xml:1996 boot-installer.xml:2511 boot-installer.xml:2607 #, no-c-format msgid "" "Older systems such as the 715 might require the use of an RBOOT server " "instead of a BOOTP server." msgstr "较早的系统比如 715 也许需要使用一台 RBOOT 服务器来取代 BOOTP 服务器。" # index.docbook:442, index.docbook:796, index.docbook:1348, index.docbook:1829, index.docbook:2252, index.docbook:2348 #. Tag: para #: boot-installer.xml:451 boot-installer.xml:1015 boot-installer.xml:1518 #: boot-installer.xml:2001 boot-installer.xml:2516 boot-installer.xml:2612 #, no-c-format msgid "" "The installation method to support network booting is described in ." msgstr "支持的网络引导安装方法在 。" #. Tag: title #: boot-installer.xml:459 #, no-c-format msgid "Booting from TFTP on Netwinder" msgstr "从 Netwinder 上的 TFTP 上引导" #. Tag: para #: boot-installer.xml:460 #, no-c-format msgid "" "Netwinders have two network interfaces: A 10Mbps NE2000-compatible card " "(which is generally referred to as eth0) and a 100Mbps " "Tulip card. There may be problems loading the image via TFTP using the " "100Mbps card so it is recommended that you use the 10Mbps interface (the one " "labeled with 10 Base-T)." msgstr "" "Netwinder 有两个网络接口:一个 10Mbps NE2000 兼容卡 (通常作为 eth0) 和一个 100Mbps Tulip 卡。使用 100Mbps 卡通过 TFTP 加载映像可能会出" "现问题,所以建议使用 10Mbps 的接口 (标记为 10 Base-T)。" #. Tag: para #: boot-installer.xml:469 #, no-c-format msgid "" "You need NeTTrom 2.2.1 or later to boot the installation system, and version " "2.3.3 is recommended. Unfortunately, firmware files are currently not " "available for download because of license issues. If this situation changes, " "you may find new images at ." msgstr "" "您需要 NeTTrom 2.2.1 或者较高的版本来引导安装系统,推荐使用 NeTTrom 2.3.3。不" "幸的是,由于许可证的原因,固件的文件现在无法下载。如果情况有所改变,您可以从 " "找到新映像。" #. Tag: para #: boot-installer.xml:477 #, no-c-format msgid "" "When you boot your Netwinder you have to interrupt the boot process during " "the countdown. This allows you to set a number of firmware settings needed " "in order to boot the installer. First of all, start by loading the default " "settings: \n" " NeTTrom command-> load-defaults\n" " Furthermore, you must configure the network, " "either with a static address: \n" " NeTTrom command-> setenv netconfig_eth0 flash\n" " NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" " where 24 is the number of set bits in the " "netmask, or a dynamic address: \n" " NeTTrom command-> setenv netconfig_eth0 dhcp\n" " You may also need to configure the " "route1 settings if the TFTP server is not on the " "local subnet. Following these settings, you have to specify the TFTP server " "and the location of the image. You can then store your settings to flash. " "\n" " NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" " NeTTrom command-> setenv kerntftpfile boot.img\n" " NeTTrom command-> save-all\n" " Now you have to tell the firmware that the TFTP " "image should be booted: \n" " NeTTrom command-> setenv kernconfig tftp\n" " NeTTrom command-> setenv rootdev /dev/ram\n" " If you use a serial console to install your " "Netwinder, you need to add the following setting: \n" " NeTTrom command-> setenv cmdappend root=/dev/ram " "console=ttyS0,115200\n" " Alternatively, for installations using a " "keyboard and monitor you have to set: \n" " NeTTrom command-> setenv cmdappend root=/dev/ram\n" " You can use the printenv " "command to review your environment settings. After you have verified that " "the settings are correct, you can load the image: \n" " NeTTrom command-> boot\n" " In case you run into any problems, a detailed HOWTO is available." msgstr "" "启动 Netwinder 时,您必须在倒数时中断引导过程。这让您可以进行一些固件的设置用" "于启动安装程序。首先,加载默认设置:\n" " NeTTrom command-> load-defaults\n" " 接着,您必须配置网络,可以是一个静态地址:" "\n" " NeTTrom command-> setenv netconfig_eth0 flash\n" " NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" " 其中 24 是网络掩码位数,或者是一个动态地址:" "\n" " NeTTrom command-> setenv netconfig_eth0 dhcp\n" " 如果 TFTP 服务器不在子网内,您还必须配置 " "route1 设置。下面的设置,要指定 TFTP 服务器和映像的位" "置。您可以将设置保存到 U 盘里。\n" " NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" " NeTTrom command-> setenv kerntftpfile boot.img\n" " NeTTrom command-> save-all\n" " 现在您要告诉固件将要引导的 TFTP 映像:" "\n" " NeTTrom command-> setenv kernconfig tftp\n" " NeTTrom command-> setenv rootdev /dev/ram\n" " 如果您通过串口控制台安装 Netwinder,需要加入下面" "设置:\n" " NeTTrom command-> setenv cmdappend root=/dev/ram " "console=ttyS0,115200\n" " 另外,对于安装时使用的键盘和监视器需要设置:" "\n" " NeTTrom command-> setenv cmdappend root=/dev/ram\n" " 您可以使用 printenv 命令回顾环" "境设置。在确认设置正确之后,您可以加载映像:\n" " NeTTrom command-> boot\n" " 万一您遇到问题,有一个 detailed HOWTO 可以參考。" #. Tag: title #: boot-installer.xml:529 #, no-c-format msgid "Booting from TFTP on CATS" msgstr "在 CATS 上的 TFTP 引导" #. Tag: para #: boot-installer.xml:530 #, no-c-format msgid "" "On CATS machines, use boot de0: or similar at the Cyclone " "prompt." msgstr "" "在 CATS 机器上,可以使用命令 boot de0: 或者在 Cyclone 引导" "符下类似的命令。" #. Tag: title #: boot-installer.xml:540 #, no-c-format msgid "Booting from CD-ROM" msgstr "从 CD 光盘上引导" # index.docbook:531, index.docbook:584, index.docbook:957, index.docbook:1776, index.docbook:2024, index.docbook:2378 #. Tag: para #: boot-installer.xml:546 boot-installer.xml:716 boot-installer.xml:1127 #: boot-installer.xml:1948 boot-installer.xml:2288 boot-installer.xml:2642 #, no-c-format msgid "" "The easiest route for most people will be to use a set of Debian CDs. If you " "have a CD set, and if your machine supports booting directly off the CD, " "great! Simply configure your system for booting off a " "CD as described in , insert " "your CD, reboot, and proceed to the next chapter." msgstr "" "对于大多数人来说,最快的途径是使用一套 Debian CD 光盘套件。如果您有此套件,并" "且如果您的机器支持直接 CD 引导,太棒了!只需要配置您的系" "统可以用 CD 启动,参见 , 插入您" "的 CD,重启,然后继续下一章。" # index.docbook:542, index.docbook:595, index.docbook:968, index.docbook:1787, index.docbook:2035, index.docbook:2389 #. Tag: para #: boot-installer.xml:557 boot-installer.xml:727 boot-installer.xml:1138 #: boot-installer.xml:1959 boot-installer.xml:2299 boot-installer.xml:2653 #, no-c-format msgid "" "Note that certain CD drives may require special drivers, and thus be " "inaccessible in the early installation stages. If it turns out the standard " "way of booting off a CD doesn't work for your hardware, revisit this chapter " "and read about alternate kernels and installation methods which may work for " "you." msgstr "" "注意某些特定的 CD 驱动器需要一些特殊的驱动程序,由此他们可能在安装的早期不能" "被访问。如果标准的从 CD 引导的方法不能用于您的硬件,阅读本章中关于其他种类的" "内核以及安装方法,它们有可能能解决问题。" # index.docbook:550, index.docbook:603, index.docbook:976, index.docbook:1795, index.docbook:2043, index.docbook:2397 #. Tag: para #: boot-installer.xml:565 boot-installer.xml:735 boot-installer.xml:1146 #: boot-installer.xml:1967 boot-installer.xml:2307 boot-installer.xml:2661 #, no-c-format msgid "" "Even if you cannot boot from CD-ROM, you can probably install the Debian " "system components and any packages you want from CD-ROM. Simply boot using a " "different media, such as floppies. When it's time to install the operating " "system, base system, and any additional packages, point the installation " "system at the CD-ROM drive." msgstr "" "即便您不能从 CD 光盘引导,依然可以安装 CD 光盘上面的 Debian 系统组件和所有软" "件包。只需要使用不同的媒介,比如软盘引导系统。当安装操作系统,基础系统和任意" "附加的软件包时只需指向安装系统至光盘驱动器即可。" # index.docbook:558, index.docbook:611, index.docbook:984, index.docbook:1803, index.docbook:2051, index.docbook:2405 #. Tag: para #: boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1154 #: boot-installer.xml:1975 boot-installer.xml:2315 boot-installer.xml:2669 #, no-c-format msgid "" "If you have problems booting, see ." msgstr "" "如果您遇到引导方面的问题,请参见 。" #. Tag: para #: boot-installer.xml:580 #, no-c-format msgid "" "To boot a CD-ROM from the Cyclone console prompt, use the command " "boot cd0:cats.bin" msgstr "" "如果需要在 Cyclone 控制台提示符下从 CD 光盘下引导,请使用命令 boot " "cd0:cats.bin" #. Tag: title #: boot-installer.xml:589 #, no-c-format msgid "Booting from Firmware" msgstr "从固件引导" #. Tag: para #: boot-installer.xml:595 #, no-c-format 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 "" "有越来越多的消费设备可以直接从设备上的闪存启动。安装程序可以被写入闪存,这样" "当您重启机器的时候就能自动运行。" #. Tag: para #: boot-installer.xml:601 #, no-c-format 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 "" "多数情况下,修改嵌入设备的固件将使质保作废。有时如果稍有差错,您将无法复原您" "的设备。所以要特别小心并精确地进行下面的步骤。" #. Tag: title #: boot-installer.xml:612 #, no-c-format msgid "Booting the NSLU2" msgstr "引导 NSLU2" #. Tag: para #: boot-installer.xml:613 #, no-c-format msgid "There are three ways how to put the installer firmware into flash:" msgstr "有三种方式可以将安装程序的固件放入闪存:" #. Tag: title #: boot-installer.xml:619 #, no-c-format msgid "Using the NSLU2 web interface" msgstr "使用 NSLU2 的 web 界面" #. Tag: para #: boot-installer.xml:620 #, no-c-format msgid "" "Go to the administration section and choose the menu item Upgrade. You can then browse your disk for the installer image you have " "previously downloaded. Then press the Start Upgrade " "button, confirm, wait for a few minutes and confirm again. The system will " "then boot straight into the installer." msgstr "" "进入管理部分然后选择菜单项 Upgrade。接着从您的磁盘上找到前" "面下载安装程序映像。然后按下 Start Upgrade 按钮,确认,等" "几分钟再次确认。系统将直接启动进入安装程序。" #. Tag: title #: boot-installer.xml:631 #, no-c-format msgid "Via the network using Linux/Unix" msgstr "通过网络使用 Linux/Unix" #. Tag: para #: boot-installer.xml:632 #, no-c-format msgid "" "You can use upslug2 from any Linux or Unix machine to " "upgrade the machine via the network. This software is packaged for Debian. " "First, you have to put your NSLU2 in upgrade mode: " " Disconnect any disks and/or devices from the USB ports. Power off the NSLU2 " " Press and hold the reset button (accessible through the " "small hole on the back just above the power input). " " Press and release the power button to power on the NSLU2. Wait for 10 seconds watching the ready/" "status LED. After 10 seconds it will change from amber to red. Immediately " "release the reset button. The NSLU2 " "ready/status LED will flash alternately red/green (there is a 1 second delay " "before the first green). The NSLU2 is now in upgrade mode. See the NSLU2-Linux pages if you have " "problems with this. Once your NSLU2 is in upgrade mode, you can flash the " "new image: \n" "sudo upslug2 -i di-nslu2.bin\n" " Note that the tool also shows the MAC address of " "your NSLU2, which may come in handy to configure your DHCP server. After the " "whole image has been written and verified, the system will automatically " "reboot. Make sure you connect your USB disk again now, otherwise the " "installer won't be able to find it." msgstr "" "您可以从任一 Linux 或 Unix 机器上使用 upslug2 通过网络来升" "级机器。Debian 下有该软件包。首先,您必须将 NSLU2 置于升级模式: " " 去除所有连接在 USB 口上的磁盘和/或设备。 关闭 NSLU2 电源 " " 按住复位按钮 (位于后面电源输入上方的小孔)。 按下和松开开关键打开 NSLU2。 " " 等待 10 秒监视就绪/状态 LED。 10 秒钟后它会从琥珀色变成红" "色。立即松开复位按钮。 NSLU2 就绪/状态 " "LED 将会红/绿交替闪烁 (在首次出现绿色时会有 1 秒钟的延迟)。NSLU2 现在处于升级" "模式。 如果您遇到问题,请参考 NSLU2-Linux " "pages。一旦 NSLU2 处于升级模式,您就可以刷人新的映像:" "\n" "sudo upslug2 -i di-nslu2.bin\n" " 注意,该工具还会显示 NSLU2 的 MAC 地址,它可以用" "来配置 DHCP 服务器。整个映像写入和检验后,系统将自动重启。确保 USB 磁盘再次连" "接,否则将无法找到安装程序。" #. Tag: title #: boot-installer.xml:693 #, no-c-format msgid "Via the network using Windows" msgstr "通过网络使用 Windows" #. Tag: para #: boot-installer.xml:694 #, no-c-format msgid "" "There is a tool for Windows to upgrade the firmware " "via the network." msgstr "" "有一个 工具 用于 Windows 通过网络升级固件。" # index.docbook:578, index.docbook:951, index.docbook:1764, index.docbook:2018, index.docbook:2372 #. Tag: title #: boot-installer.xml:710 boot-installer.xml:1121 boot-installer.xml:1936 #: boot-installer.xml:2282 boot-installer.xml:2636 #, no-c-format msgid "Booting from a CD-ROM" msgstr "从 CD-ROM 启动" #. Tag: title #: boot-installer.xml:848 #, no-c-format msgid "" "Booting from Linux Using LILO or GRUB" msgstr "引导 Linux 使用 LILOGRUB" #. Tag: para #: boot-installer.xml:851 #, 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:856 #, fuzzy, no-c-format msgid "" "If you intend to use the hard drive only for booting and then download " "everything over the network, you should download the netboot/" "debian-installer/i386/initrd.gz file and its corresponding kernel " "netboot/debian-installer/i386/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/i386/initrd.gz 及其对应的内核。这将允许您重新分区" "您用于引导的硬盘。这里需要小心操作。" #. Tag: para #: boot-installer.xml:866 #, no-c-format msgid "" "Alternatively, if you intend to keep an existing partition on the hard drive " "unchanged during the install, you can download the hd-media/initrd." "gz file and its kernel, as well as copy a CD 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 image, " "without needing the network." msgstr "" "或者,如果您愿意保持安装时硬盘原有分区不变,可以下载 hd-media/" "initrd.gz 文件及其内核,以及复制一个 CD 光盘 iso 文件到硬盘上(确保" "文件名结尾是.iso)。安装程序就可以无网络从硬盘引导,并且从 " "CD 映像文件上安装。" #. Tag: para #: boot-installer.xml:875 #, no-c-format msgid "" "For LILO, you will need to configure two essential things " "in /etc/lilo.conf: to " "load the initrd.gz installer at boot time; have the vmlinuz kernel use " "a RAM disk as its root partition. Here is " "a /etc/lilo.conf example:" msgstr "" "如果采用 LILO,您需要在 /etc/lilo.conf 中配置两件最基本的事情: 在引导时装" "入 initrd.gz 安装程序; " "vmlinuz 内核使用一个内存虚拟磁盘作为" "它的根分区。 这里是一个 /etc/" "lilo.conf 的例子:" #. Tag: screen #: boot-installer.xml:896 #, no-c-format msgid "" "image=/boot/newinstall/vmlinuz\n" " label=newinstall\n" " initrd=/boot/newinstall/initrd.gz\n" " root=/dev/ram0\n" " append=\"ramdisk_size=12000\"" msgstr "" "image=/boot/newinstall/vmlinuz\n" " label=newinstall\n" " initrd=/boot/newinstall/initrd.gz\n" " root=/dev/ram0\n" " append=\"ramdisk_size=12000\"" #. Tag: para #: boot-installer.xml:896 #, no-c-format msgid "" "For more details, refer to the initrd 4 and " "lilo.conf 5 man pages. Now run lilo and " "reboot." msgstr "" "欲获知更多细节,请参阅 initrd " "4lilo." "conf 5 man 手册。现在运" "行 lilo 并且重新启动。" #. Tag: para #: boot-installer.xml:905 #, no-c-format msgid "" "The procedure for GRUB is quite similar. Locate your " "menu.lst in the /boot/grub/ " "directory (sometimes in the /boot/boot/grub/), add the " "following lines: \n" "title New Install\n" "kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 ramdisk_size=12000\n" "initrd (hd0,0)/boot/newinstall/initrd.gz\n" " and reboot." msgstr "" "使用 GRUB 的过程也类似。在 /boot/grub/ 目录下找到 menu.lst (有时位于 /boot/" "boot/grub/),加入下面几行:\n" "title New Install\n" "kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 ramdisk_size=12000\n" "initrd (hd0,0)/boot/newinstall/initrd.gz\n" " 然后重启。" #. Tag: para #: boot-installer.xml:916 #, no-c-format msgid "" "Note that the value of the ramdisk_size may need to " "be adjusted for the size of the initrd image. From here on, there should be " "no difference between GRUB or LILO." msgstr "" "注意 ramdisk_size 的值也许需要调整至 initrd 映像的大" "小。从这里开始,没什么区别,即采用 GRUBLILO。" # index.docbook:700, index.docbook:2176 #. Tag: title #: boot-installer.xml:927 #, no-c-format msgid "Booting from USB Memory Stick" msgstr "从 USB 闪盘引导" #. Tag: para #: boot-installer.xml:928 #, no-c-format msgid "" "Let's assume you have prepared everything from and . Now just plug your USB " "stick into some free USB connector and reboot the computer. The system " "should boot up, and you should be presented with the boot: " "prompt. Here you can enter optional boot arguments, or just hit &enterkey;." msgstr "" "假设您已经准备好了从 的所有步骤。现在只需要插入您的 USB 盘到一个空闲的 USB 插" "槽并且重启计算机。系统应该重新引导,并且您将得到一个 boot: " "提示符。这里您可以输入一些引导选项,或者只是敲击 &enterkey;。" # index.docbook:723, index.docbook:1876, index.docbook:2278, index.docbook:2426 #. Tag: title #: boot-installer.xml:941 boot-installer.xml:2048 boot-installer.xml:2542 #: boot-installer.xml:2690 #, no-c-format msgid "Booting from Floppies" msgstr "从软盘引导" # index.docbook:724, index.docbook:2286 #. Tag: para #: boot-installer.xml:942 boot-installer.xml:2550 #, no-c-format msgid "" "You will have already downloaded the floppy images you needed and created " "floppies from the images in ." msgstr "" "您可能已经下载了所需要的软盘映像,并且根据这些映像创建了软盘 。" #. Tag: para #: boot-installer.xml:949 #, no-c-format msgid "" "To boot from the installer boot floppy, place it in the primary floppy " "drive, shut down the system as you normally would, then turn it back on." msgstr "" "从软盘引导安装程序需要放置软盘至主软驱。按照您平时的习惯关闭系统,然后重新打" "开。" #. Tag: para #: boot-installer.xml:955 #, no-c-format msgid "" "For installing from an LS-120 drive (ATAPI version) with a set of floppies, " "you need to specify the virtual location for the floppy device. This is done " "with the root= boot argument, giving the device that " "the ide-floppy driver maps the device to. For example, if your LS-120 drive " "is connected as the first IDE device (master) on the second cable, you enter " "linux root=/dev/hdc at the boot prompt." msgstr "" "要想在 LS-120 驱动器(ATAPI 版本)使用这些软盘,您需指定这些软盘设备的虚拟地" "址。这可以通过 root= 引导参数来指定映射的 ide-floppy 驱" "动器设备名来完成。比如,您的 LS-120 驱动器连接到第二根线第一个 IDE 设备" "(master),那么在提示符下输入 linux root=/dev/hdc。" #. Tag: para #: boot-installer.xml:965 #, no-c-format msgid "" "Note that on some machines, Control Alt Delete does not properly reset the " "machine, so a hard reboot is recommended. If you are " "installing from an existing operating system (e.g., from a DOS box) you " "don't have a choice. Otherwise, please do a hard reboot when booting." msgstr "" "注意有些机器上,Control Alt " "Delete 不能正常地重启系统,所以推荐使用硬" "启动。如果您正从已有的操作系统上安装(比如在 DOS 系统上)您将没有这样的" "选择。在其它情况下,请在引导时使用硬重启。" #. Tag: para #: boot-installer.xml:974 #, no-c-format msgid "" "The floppy disk will be accessed, and you should then see a screen that " "introduces the boot floppy and ends with the boot: prompt." msgstr "" "读完软盘后,您将看到屏幕上有一个有关引导软盘的介绍,并且结尾是 boot:" " 提示符。" #. Tag: para #: boot-installer.xml:980 #, no-c-format msgid "" "Once you press &enterkey;, you should see the message " "Loading..., followed by " "Uncompressing Linux..., and then a " "screenfull or so of information about the hardware in your system. More " "information on this phase of the boot process can be found below in ." msgstr "" "一旦您敲入 &enterkey;,您应该能够看到 Loading... 消息,并且接下来是 Uncompressing Linux...,然后是一些有关您系统的硬件信息。想知道更多有关这段引导过程的" "信息,可以在下面 。" #. Tag: para #: boot-installer.xml:989 #, no-c-format msgid "" "After booting from the boot floppy, the root floppy is requested. Insert the " "root floppy and press &enterkey;, and the contents are loaded into memory. " "The installer program debian-installer is automatically " "launched." msgstr "" "软盘引导后需要根软盘。请插入根软盘并且输入 &enterkey;,然后其中的内容会被装入" "内存。安装程序 debian-installer 会自动启动。" #. Tag: para #: boot-installer.xml:1023 #, no-c-format msgid "There are various ways to do a TFTP boot on i386." msgstr "在 i386 体系上有很多方法用 TFTP 进行引导。" #. Tag: title #: boot-installer.xml:1029 #, no-c-format msgid "NIC or Motherboard that support PXE" msgstr "支持 PXE 的网卡或者主板" #. Tag: para #: boot-installer.xml:1030 #, no-c-format msgid "" "It could be that your Network Interface Card or Motherboard provides PXE " "boot functionality. This is a Intel " "re-implementation of TFTP boot. If so you may be able to configure your BIOS " "to boot from the network." msgstr "" "您的网卡或者主板可能已经提供了 PXE 引导功能。这是一个 IntelTFTP 引导的实现。如果是这样,也许可以能够配置您的 " "BIOS 来用网络进行引导。" #. Tag: title #: boot-installer.xml:1041 #, no-c-format msgid "NIC with Network BootROM" msgstr "网络 BootROM 的网卡" #. Tag: para #: boot-installer.xml:1042 #, no-c-format msgid "" "It could be that your Network Interface Card provides TFTP boot " "functionality." msgstr "很有可能是您的网卡提供了 TFTP 引导功能。" #. Tag: para #: boot-installer.xml:1047 #, 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:1055 #, no-c-format msgid "Etherboot" msgstr "Etherboot" #. Tag: para #: boot-installer.xml:1056 #, no-c-format msgid "" "The etherboot project " "provides bootdiskettes and even bootroms that do a TFTPboot." msgstr "" "etherboot project 提供了为 " "TFTP 引导所需要的引导软盘甚至是引导 ROMS 。" # index.docbook:1943, index.docbook:2477 #. Tag: title #: boot-installer.xml:1065 #, no-c-format msgid "The Boot Prompt" msgstr "引导提示" #. Tag: para #: boot-installer.xml:1066 #, no-c-format msgid "" "When the installer boots, you should be presented with a friendly graphical " "screen showing the Debian logo and the boot prompt: " "\n" "Press F1 for help, or ENTER to boot:\n" " At the boot prompt you can either just press " "&enterkey; to boot the installer with default options or enter a specific " "boot method and, optionally, boot parameters." msgstr "" "安装系统引导时,您应该看到友好的图形画面,显示着 Debian 标志和引导提示: " "Press F1 for help, or ENTER to boot: 您可以按 &enterkey; 键使用默认的选项引导,或者输入一个可选的" "引导参数来指定引导的方式。" #. Tag: para #: boot-installer.xml:1078 #, no-c-format msgid "" "Information on available boot methods and on boot parameters which might be " "useful can be found by pressing F2 through F8. If you add any parameters to the boot command line, be sure to type " "the boot method (the default is linux) and a space " "before the first parameter (e.g., linux fb=false)." msgstr "" "使用 F2F8 键,可以查看可用的引导方法和" "引导参数的信息。如果您在引导命令行上添加任何参数,确保引导方法(默认是 " "linux)和第一个参数之间有一个空格(例如," "linux fb=false)。" #. Tag: para #: boot-installer.xml:1087 #, no-c-format msgid "" "If you are installing the system via a remote management device that " "provides a text interface to the VGA console, you may not be able to see the " "initial graphical splash screen upon booting the installer; you may even not " "see the boot prompt. Examples of these devices include the text console of " "Compaq's integrated Lights Out (iLO) and HP's " "Integrated Remote Assistant (IRA). You can blindly press " "F1 In some cases these devices will require special escape " "sequences to enact this keypress, for example the IRA uses " "Ctrl F 1. to bypass this screen and view the help text. " "Once you are past the splash screen and at the help text your keystrokes " "will be echoed at the prompt as expected. To prevent the installer from " "using the framebuffer for the rest of the installation, you will also want " "to add fb=false to the boot prompt, as described in " "the help text." msgstr "" "如果您通过远程设备安装系统,而该设备在 VGA 控制台提供文本界面,您可能不会看到" "安装程序开始的图形启动画面; 甚至不会看到引导提示。像 Compaq 的 " "integrated Lights Out (iLO) 和 HP 的 Integrated Remote " "Assistant (IRA) 就是这类设备。您可以什么都看不见地按下 F1 " "有些情况下这些设备特别的转义次序按键,例如 IRA 使用 " "Ctrl F 1 跳过该画面切换到帮助文档。一旦通过启动画面,在帮" "助文档按下的键会回显在提示符上。为了阻止安装程序在后续安装中使用 " "framebuffer,如帮助文档所述,您也可在引导提示后面加上 fb=false。" #. Tag: title #: boot-installer.xml:1162 #, no-c-format msgid "CD Contents" msgstr "CD 的内容" #. Tag: para #: boot-installer.xml:1164 #, no-c-format msgid "" "There are three basic variations of Debian Install CDs. The " "Business Card CD has a minimal installation that will " "fit on the small form factor CD media. It requires a network connection in " "order to install the rest of the base installation and make a usable system. " "The Network Install CD has all of the packages for a " "base install but requires a network connection to a Debian mirror site in " "order to install the extra packages one would want for a complete system . " "The set of Debian CDs can install a complete system from the wide range of " "packages without needing access to the network." msgstr "" "有三种基本的 Debian 安装光盘 CD 衍生品:名片式(Business Card) CD 有一个微型的安装程序,并且可以储存在一小张 CD 介质上。它需要借助" "网络连接来安装基本系统的其他部分,才能建立起一个可用的系统。网络安" "装(Network Install) CD 光盘具有基本系统需的所有包,但是它还是需要" "网络连接到 Debian 的镜像,安装其他的软件包建立一个完整的系统。Debian CD 光盘" "套件,则可以不使用网络就能安装大量软件包,建立完整的系统。" #. Tag: para #: boot-installer.xml:1180 #, no-c-format msgid "" "The IA-64 architecture uses the next generation Extensible Firmware " "Interface (EFI) from Intel. Unlike the traditional x86 BIOS which knows " "little about the boot device other than the partition table and Master Boot " "Record (MBR), EFI can read and write files from FAT16 or FAT32 formatted " "disk partitions. This simplifies the often arcane process of starting a " "system. The system boot loader and the EFI firmware that supports it have a " "full filesystem to store the files necessary for booting the machine. This " "means that the system disk on an IA-64 system has an additional disk " "partition dedicated to EFI instead of the simple MBR or boot block on more " "conventional systems." msgstr "" "IA-64 使用 Intel 最新的可拓展固件界面(Extensible Firmware Interface (EFI))。" "与传统的 x86 BIOS 只了解分区表和主引导记录(MBR)而不知道其他引导设备的特点不" "同,EFI 可以对 FAT16 和 FAT32 格式的硬盘分区进行读写操作。这个特点简化了通常" "很难以理解的系统启动过程。系统引导装载器以及 EFI 固件支持一个完全的文件系统," "来保存引导一个机器所需要得所有文件。这意味着在一个 IA-64 系统上的系统磁盘,具" "有一个附加的专门为 EFI 服务的磁盘分区,而不是像传统系统上只是简单的 MBR 或者" "引导块记录。" #. Tag: para #: boot-installer.xml:1196 #, no-c-format msgid "" "The Debian Installer CD contains a small EFI partition where the " "ELILO bootloader, its configuration file, the installer's " "kernel, and initial filesystem (initrd) are located. The running system also " "contains an EFI partition where the necessary files for booting the system " "reside. These files are readable from the EFI Shell as described below." msgstr "" "Debian CD 包含了一个小型版本的 EFI 分区来放置 ELILO,它的" "配置文件,安装程序内核以及初始的文件系统(initrd)。运行的系统同时也包含了一个 " "EFI 分区用于放置引导系统所需要的必要文件。这些文件可以从 EFI Shell 读出,说明" "如下。" #. Tag: para #: boot-installer.xml:1205 #, no-c-format msgid "" "Most of the details of how ELILO actually loads and " "starts a system are transparent to the system installer. However, the " "installer must set up an EFI partition prior to installing the base system. " "Otherwise, the installation of ELILO will fail, rendering " "the system un-bootable. The EFI partition is allocated and formatted in the " "partitioning step of the installation prior to loading any packages on the " "system disk. The partitioning task also verifies that a suitable EFI " "partition is present before allowing the installation to proceed." msgstr "" "大部分有关如何 ELILO 实际装入和开始一个系统的细节是对系统" "安装程序透明的。但是,安装程序必须设置 EFI 分区优先级来安装基本系统。否则 " "ELILO 的安装将会失败并且导致系统不可引导。EFI 分区是分配并" "且格式 化与分区步骤以装入系统磁盘的所有软件包。分区任务也需要为接下来的安装检" "查一个 EFI 分区是否合适。" #. Tag: para #: boot-installer.xml:1217 #, no-c-format msgid "" "The EFI Boot Manager is presented as the last step of the firmware " "initialization. It displays a menu list from which the user can select an " "option. Depending on the model of system and what other software has been " "loaded on the system, this menu may be different from one system to another. " "There should be at least two menu items displayed, Boot Option " "Maintenance Menu and EFI Shell (Built-in). " "Using the first option is preferred, however, if that option is not " "available or the CD for some reason does not boot with it, use the second " "option." msgstr "" "EFI Boot Manager 在固件初始化的最后一步会被启动。它显示一个菜单列表供用户选" "择。取决于系统的型号并且是否有其他的软件已经被装入系统,这个菜单可能在不同系" "统上有不同表现。在每一个系统上,至少有两个菜单项显示,Boot Option " "Maintenance MenuEFI Shell (Built-in)。推荐使" "用第一个,当然,该选项不可用或者 CD 由于某种原因没法启动,使用第二个。" #. Tag: title #: boot-installer.xml:1236 #, no-c-format msgid "IMPORTANT" msgstr "重要" #. Tag: para #: boot-installer.xml:1237 #, no-c-format msgid "" "The EFI Boot Manager will select a default boot action, typically the first " "menu choice, within a pre-set number of seconds. This is indicated by a " "countdown at the bottom of the screen. Once the timer expires and the " "systems starts the default action, you may have to reboot the machine in " "order to continue the installation. If the default action is the EFI Shell, " "you can return to the Boot Manager by running exit at the " "shell prompt." msgstr "" "EFI Boot Manager 会在预设的几秒钟之后选择默认的启动方式,一般是第一菜单项。在" "屏幕底部会有倒计时显示。时间一到,系统按默认方式启动,这样您也许需要重新启动" "才能继续安装。如果默认是 EFI Shell,您可在提示符下执行 exit返回 Boot Manager。" #. Tag: title #: boot-installer.xml:1249 #, no-c-format msgid "Option 1: Booting from the Boot Option Maintenance Menu" msgstr "选项 1: 从 Boot Option Maintenance Menu 启动" #. Tag: para #: boot-installer.xml:1256 #, no-c-format msgid "" "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will " "display the EFI Boot Manager page and menu after it completes its system " "initialization." msgstr "" "插入 CD 到 DVD/CD 驱动器,然后重启机器。固件在完成系统初始化后会显示 EFI " "Boot Manager 页面和菜单。" #. Tag: para #: boot-installer.xml:1262 #, no-c-format msgid "" "Select Boot Maintenance Menu from the menu with the arrow " "keys and press ENTER. This will display a new menu." msgstr "" "选择 Boot Maintenance Menu 通过方向键然后按下 " "ENTER。会显示一个新菜单。" #. Tag: para #: boot-installer.xml:1268 #, no-c-format msgid "" "Select Boot From a File from the menu with the arrow keys " "and press ENTER. This will display a list of devices " "probed by the firmware. You should see two menu lines containing either the " "label Debian Inst [Acpi ... or Removable Media " "Boot. If you examine the rest of the menu line, you will notice " "that the device and controller information should be the same." msgstr "" "选择 Boot From a File 通过方向键,然后按下 " "ENTER。将显示固件检测到的设备列表。您会看到两个菜单行,它" "们包括 Debian Inst [Acpi ...Removable Media " "Boot标签。如果您检查菜单行其他部分,会看到对应的设备和控制器信息。" #. Tag: para #: boot-installer.xml:1279 #, no-c-format msgid "" "You can choose either of the entries that refer to the CD/DVD drive. Select " "your choice with the arrow keys and press ENTER. If you " "choose Removable Media Boot the machine will immediately " "start the boot load sequence. If you choose Debian Inst [Acpi ... instead, it will display a directory listing of the bootable " "portion of the CD, requiring you to proceed to the next (additional) step." msgstr "" "您可选择指向 CD/DVD 驱动的入口。通过方向键选择并按下 ENTER。如果您选择 Removable Media Boot 机器将进入启动步" "骤。如果您选择 Debian Inst [Acpi ...,它会显示一个可启动" "的 CD 目录列表,要求您进行(额外的)下一步。" #. Tag: para #: boot-installer.xml:1290 #, no-c-format msgid "" "You will only need this step if you chose Debian Inst [Acpi .... The directory listing will also show [Treat like " "Removable Media Boot] on the next to the last line. Select this " "line with the arrow keys and press ENTER. This will start " "the boot load sequence." msgstr "" "您只在选择 Debian Inst [Acpi ... 时需要。目录列表还会显示 " "[Treat like Removable Media Boot] 至最后一行。用方向键选" "择,并按下 ENTER。这将进入启动步骤。" #. Tag: para #: boot-installer.xml:1302 #, no-c-format msgid "" "These steps start the Debian boot loader which will display a menu page for " "you to select a boot kernel and options. Proceed to selecting the boot " "kernel and options." msgstr "" "这些步骤启动的 Debian 引导器会显示一个菜单页用于选择启动内核和选项。进入选择" "启动内核和选项。" #. Tag: title #: boot-installer.xml:1312 #, no-c-format msgid "Option 2: Booting from the EFI Shell" msgstr "选项 2: 从 EFI Shell 启动" #. Tag: para #: boot-installer.xml:1313 #, no-c-format msgid "" "If, for some reason, option 1 is not successful, reboot the machine and when " "the EFI Boot Manager screen appears there should be one option called " "EFI Shell [Built-in]. Boot the Debian Installer CD with " "the following steps:" msgstr "" "某些情况下,选项 1 无法成功,重新启动机器然后在 EFI Boot Manager 画面出现的时" "候会有一个选项称为 EFI Shell [Built-in]。可以通过如下步骤" "来引导 Debian 安装程序 CD :" #. Tag: para #: boot-installer.xml:1324 #, no-c-format msgid "" "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will " "display the EFI Boot Manager page and menu after it completes system " "initialization." msgstr "把 CD 放入 DVD/CD 驱动器。" #. Tag: para #: boot-installer.xml:1330 #, no-c-format msgid "" "Select EFI Shell from the menu with the arrow keys and " "press ENTER. The EFI Shell will scan all of the bootable " "devices and display them to the console before displaying its command " "prompt. The recognized bootable partitions on devices will show a device " "name of fsn:. All other " "recognized partitions will be named blkn:. If you inserted the CD just before entering the " "shell, this may take a few extra seconds as it initializes the CD drive." msgstr "" "选择 EFI Shell 然后按下 ENTER。EFI " "Shell 将扫描所有的可引导设备,并且在显示其命令提示符前在控制台列出它们。在设" "备上被辨认出的可引导分区,将显示成 fsn:" "。所有其他辨认出的分区,将被命名为 blkn:。如果您在进入 Shell 之前就插入 CD,这将花费一些时间" "用于初始化 CD 驱动器。" #. Tag: para #: boot-installer.xml:1344 #, no-c-format msgid "" "Examine the output from the shell looking for the CDROM drive. It is most " "likely the fs0: device although other devices with " "bootable partitions will also show up as fsn." msgstr "" "在检查 CD 驱动器期间请查看 Shell 的输出显示。一般来说是 fs0: 并且其他具有可引导分区的设备上也会显示成 " "fsn。" #. Tag: para #: boot-installer.xml:1351 #, no-c-format msgid "" "Enter fsn: and press " "ENTER to select that device where n is the partition number for the CDROM. The shell will now " "display the partition number as its prompt." msgstr "" "进入 fsn: 然后按下 " "ENTER 来选择设备。这里 n 是 CD " "光盘的分区号。Shell 现在将在提示符下显示分区号。" #. Tag: para #: boot-installer.xml:1358 #, no-c-format msgid "" "Enter elilo and press ENTER. This will " "start the boot load sequence." msgstr "" "进入 elilo 并按下 ENTER。这将进入启动步" "骤。" #. Tag: para #: boot-installer.xml:1365 #, no-c-format msgid "" "As with option 1, these steps start the Debian boot loader which will " "display a menu page for you to select a boot kernel and options. You can " "also enter the shorter fsn:elilo command at the shell prompt. Proceed to selecting the boot kernel " "and options." msgstr "" "与选项 1 相同,这些步骤也会启动 Debian 引导器,显示一个菜单页供选择启动内核和" "参数。您可在 shell 提示符下输入 fsn:" "elilo简短命令。进入选择启动内核和选项。" #. Tag: title #: boot-installer.xml:1379 #, no-c-format msgid "Installing using a Serial Console" msgstr "使用串口控制台安装" #. Tag: para #: boot-installer.xml:1381 #, no-c-format msgid "" "You may choose to perform an install using a monitor and keyboard or using a " "serial connection. To use a monitor/keyboard setup, select an option " "containing the string [VGA console]. To install over a serial connection, " "choose an option containing the string [BAUD baud " "serial console], where BAUD is the speed of your " "serial console. Menu items for the most typical baud rate settings on the " "ttyS0 device are preconfigured." msgstr "" "您可选择使用显示器与键盘或者串口连接来进行安装。要使用显示器/键盘配置,选择包" "含 [VGA console] 的选项。要通过串口连接,选择包含 [BAUD baud serial console] 的选项,其中 BAUD 是串行连接速度。对于大多数常见的波特率的 ttyS0 设备菜单项已经预" "置。" #. Tag: para #: boot-installer.xml:1392 #, no-c-format msgid "" "In most circumstances, you will want the installer to use the same baud rate " "as your connection to the EFI console. If you aren't sure what this setting " "is, you can obtain it using the command baud at the EFI " "shell." msgstr "" "大多时候,您会让安装程序使用与连接 EFI 控制台相同的波特率。如果您不知如何设" "置,可以通过命令 baud 在 EFI shell 获得。" #. Tag: para #: boot-installer.xml:1399 #, no-c-format msgid "" "If there is not an option available that is configured for the serial device " "or baud rate you would like to use, you may override the console setting for " "one of the existing menu options. For example, to use a 57600 baud console " "over the ttyS1 device, enter console=ttyS1,57600n8 into " "the Boot: text window." msgstr "" "如果没有串行配置的选项或者您要使用的波特率,可以覆盖某个已有菜单项里面的波特" "率。例如,使用 57600 波特率覆盖 ttyS1 设备,输入 " "console=ttyS1,57600n8Boot: 文本" "窗口。" #. Tag: para #: boot-installer.xml:1410 #, no-c-format msgid "" "Most IA-64 boxes ship with a default console setting of 9600 baud. This " "setting is rather slow, and the normal installation process will take a " "significant time to draw each screen. You should consider either increasing " "the baud rate used for performing the installation, or performing a Text " "Mode installation. See the Params help menu for " "instructions on starting the installer in Text Mode." msgstr "" "大多数 IA-64 机器配备默认 9600 波特率的控制台。这样设太慢,普通安装过程将花费" "明显的时间刷新每个屏幕。您要么通过提高波特率提升安装效率,要么使用文本模式安" "装。参考 Params 帮助菜单,获得启动文本模式安装的指导。" #. Tag: para #: boot-installer.xml:1419 #, no-c-format msgid "" "If you select the wrong console type, you will be able to select the kernel " "and enter parameters but both the display and your input will go dead as " "soon as the kernel starts, requiring you to reboot before you can begin the " "installation." msgstr "" "如果您选择了错误的控制台类型,即便可以选择内核和输入参数,但显示与输入将在内" "核启动后死掉,只有重新启动才能开始安装。" #. Tag: title #: boot-installer.xml:1428 #, no-c-format msgid "Selecting the Boot Kernel and Options" msgstr "选择启动内核与选项" #. Tag: para #: boot-installer.xml:1430 #, no-c-format msgid "" "The boot loader will display a form with a menu list and a text window with " "a Boot: prompt. The arrow keys select an item from " "the menu and any text typed at the keyboard will appear in the text window. " "There are also help screens which can be displayed by pressing the " "appropriate function key. The General help screen " "explains the menu choices and the Params screen " "explains the common command line options." msgstr "" "引导程序会显示一个表单,具有菜单列与包含 Boot: 提示符" "的文本窗口。用方向键选择菜单项并且键盘输入的字符将显示在文本窗口。输入适当的" "功能键会显示帮助窗口。普通的帮助窗口解释菜单选项," "Params窗口解释命令行参数。" #. Tag: para #: boot-installer.xml:1442 #, no-c-format msgid "" "Consult the General help screen for the description " "of the kernels and install modes most appropriate for your installation. You " "should also consult below for any additional " "parameters that you may want to set in the Boot: text " "window. The kernel version you choose selects the kernel version that will " "be used for both the installation process and the installed system. If you " "encounter kernel problems with the installation, you may also have those " "same problems with the system you install. The following two steps will " "select and start the install:" msgstr "" "查询 General 帮助页面,了解内核的说明和安装对应的模" "式。您还应该查询 ,了解在文本窗口中需要设置的额" "外参数 Boot:,您选择的内核版本将会用在安装过程和安装好" "的系统中。如果安装时碰到内核问题,在安装好的系统中也会出现。以下两步选择和开" "始安装:" #. Tag: para #: boot-installer.xml:1460 #, no-c-format msgid "" "Select the kernel version and installation mode most appropriate to your " "needs with the arrow keys." msgstr "使用方向键选择您需要的内核版本和适合的安装模式。" #. Tag: para #: boot-installer.xml:1465 #, no-c-format msgid "" "Enter any boot parameters by typing at the keyboard. The text will be " "displayed directly in the text window. This is where kernel parameters (such " "as serial console settings) are specified." msgstr "" "在键盘上输入任何启动参数。这些文字将直接显示在文本窗口。这是内核参数(如同串口" "控制台)指定的。" #. Tag: para #: boot-installer.xml:1472 #, no-c-format msgid "" "Press ENTER. This will load and start the kernel. The " "kernel will display its usual initialization messages followed by the first " "screen of the Debian Installer." msgstr "" "按下 ENTER。会加载并启动内核。内核在 Debian 安装程序的第一" "个屏幕显示常规的初始化信息。" #. Tag: para #: boot-installer.xml:1481 boot-installer.xml:1617 #, no-c-format msgid "" "Proceed to the next chapter to continue the installation where you will set " "up the language locale, network, and disk partitions." msgstr "进入到下一章继续安装本地语言,网络和磁盘分区。" #. Tag: para #: boot-installer.xml:1492 #, fuzzy, no-c-format msgid "" "Booting an IA-64 system from the network is similar to a CD boot. The only " "difference is how the installation kernel is loaded. The EFI Boot Manager " "can load and start programs from a server on the network. Once the " "installation kernel is loaded and starts, the system install will proceed " "thru the same steps as the CD install with the exception that the packages " "of the base install will be loaded from the network rather than the CD drive." msgstr "" "在 IA64 系统上面从网络引导很像从 CD 上引导。唯一的区别是如何装入内核。EFI " "Boot Manager 可以装入并且从网络服务器开始程序。一旦安装内核被装入并且启动,系" "统 的安装将和 CD 安装步骤相同,只是基本软件包将从网络装入而不是 CD 光盘驱动" "器。" #. Tag: para #: boot-installer.xml:1526 #, fuzzy, no-c-format msgid "" "Network booting an IA-64 system requires two architecture-specific actions. " "On the boot server, DHCP and TFTP must be configured to deliver " "elilo. On the client a new boot option must be defined in " "the EFI boot manager to enable loading over a network." msgstr "" "网络引导一台 IA64 系统需要两个体系相关的操作。在引导服务器上,DHCP 和 TFTP 必" "须配置成可以传送 elilo。在客户端,一个新的引导选项必须在 " "EFI Boot Manager 下定义来打开网络的装入。" #. Tag: title #: boot-installer.xml:1537 #, no-c-format msgid "Configuring the Server" msgstr "配置网络服务器" #. Tag: para #: boot-installer.xml:1538 #, fuzzy, no-c-format msgid "" "A suitable TFTP entry for network booting an IA-64 system looks something " "like this: \n" "host mcmuffin {\n" " hardware ethernet 00:30:6e:1e:0e:83;\n" " fixed-address 10.0.0.21;\n" " filename \"debian-installer/ia64/elilo.efi\";\n" "}\n" " Note that the goal is to get elilo.efi running on the client." msgstr "" "一个合适的用于 ia64 系统网络引导的 TFTP 选项应该看起来像这样: " "\n" "host mcmuffin {\n" " hardware ethernet 00:30:6e:1e:0e:83;\n" " fixed-address 10.0.0.21;\n" " filename \"debian-installer/ia64/elilo.efi\";\n" "}\n" " 注明的是,目标是让 elilo.efi " "在客户端运行。" #. Tag: para #: boot-installer.xml:1548 #, no-c-format msgid "" "Extract the netboot.tar.gz file into the directory used " "as the root for your tftp server. Typical tftp root directories include " "/var/lib/tftp and /tftpboot. This " "will create a debian-installer directory tree " "containing the boot files for an IA-64 system." msgstr "" "使用 root 解压 netboot.tar.gz 文件到您的 tftp 服务器。典" "型的 tftp 根目录包括 /var/lib/tftp/" "tftpboot。这将创建 debian-installer 目录树," "它包括 IA-64 系统需要的启动文件。" #. Tag: screen #: boot-installer.xml:1558 #, no-c-format msgid "" "# cd /var/lib/tftp\n" "# tar xvfz /home/user/netboot.tar.gz\n" "./\n" "./debian-installer/\n" "./debian-installer/ia64/\n" "[...]" msgstr "" "# cd /var/lib/tftp\n" "# tar xvfz /home/user/netboot.tar.gz\n" "./\n" "./debian-installer/\n" "./debian-installer/ia64/\n" "[...]" #. Tag: para #: boot-installer.xml:1558 #, no-c-format msgid "" "The netboot.tar.gz contains an elilo.conf file that should work for most configurations. However, should you " "need to make changes to this file, you can find it in the debian-" "installer/ia64/ directory. It is possible to have different " "config files for different clients by naming them using the client's IP " "address in hex with the suffix .conf instead of " "elilo.conf. See documentation provided in the " "elilo package for details." msgstr "" "netboot.tar.gz 包含 elilo.conf 可以" "工作在大多数的配置下。另外,要修改这个文件,您可以在 debian-" "installer/ia64/ 目录中找到。这只需要按照客户机 IP 地址的16进制命名" "这些文件并且给出 .conf 后缀取代 elilo.conf。请查看 elilo 软件包附带的文档以获得细节。" #. Tag: title #: boot-installer.xml:1575 #, no-c-format msgid "Configuring the Client" msgstr "配置客户机" #. Tag: para #: boot-installer.xml:1576 #, no-c-format msgid "" "To configure the client to support TFTP booting, start by booting to EFI and " "entering the Boot Option Maintenance Menu. " " Add a boot option. You " "should see one or more lines with the text Load File [Acpi" "()/.../Mac()]. If more than one of these entries exist, choose " "the one containing the MAC address of the interface from which you'll be " "booting. Use the arrow keys to highlight your choice, then press enter. Name the entry Netboot or something similar, save, and exit back to the boot options " "menu. You should see the new boot option " "you just created, and selecting it should initiate a DHCP query, leading to " "a TFTP load of elilo.efi from the server." msgstr "" "如果要配置支持 TFTP 引导的客户机,只需要引导至 EFI,然后进入 Boot " "Option Maintenance Menu 加入一个引" "导选项。 您会看到一行或多行带有 " "Load File [Acpi()/.../Mac()] 文字。如果多于一个入" "口存在,选择您需要启动的包含 MAC 地址的网卡。使用方向键高亮选择,然后按回车。" " 给此选项起名,如 Netboot 或者相似的,保存然后退回至引导选项菜单。 您现在应该能够看到刚刚创建的新引导选项,选择后应该会初始化一个 " "DHCP 查询,然后会从服务器装入 elilo.efi。" #. Tag: para #: boot-installer.xml:1608 #, no-c-format msgid "" "The boot loader will display its prompt after it has downloaded and " "processed its configuration file. At this point, the installation proceeds " "with the same steps as a CD install. Select a boot option as in above and " "when the kernel has completed installing itself from the network, it will " "start the Debian Installer." msgstr "" "在下载并且处理配置文件后,引导装载程序将显示它的提示符。从这里开始,安装过程" "将和 CD 安装是 同样的过程。在内核已经完成从网络的自我安装后选择一个像上面提到" "的引导选项,它将开始 Debian 安装程序。" #. Tag: title #: boot-installer.xml:1630 #, no-c-format msgid "Choosing an Installation Method" msgstr "选择安装方法" #. Tag: para #: boot-installer.xml:1632 #, no-c-format msgid "" "Some &arch-title; subarchs have the option of booting using either a 2.4.x " "or 2.2.x linux kernel. When such a choice exists, try the 2.4.x linux " "kernel. The installer should also require less memory when using a 2.4.x " "linux kernel as 2.2.x support requires a fixed-sized ramdisk and 2.4.x uses " "tmpfs." msgstr "" "一些 &arch-title; 子体系可以选择使用从 2.4.x 或 2.2.x linux 内核启动。如果可" "以这样选取,请使用 2.4.x linux 内核。使用 2.4.x linux 内核的安装程序要求较少" "的内存,因为 2.2.x 支持需要固定尺寸的 ramdisk 而 2.4.x 使用 tmpfs。" #. Tag: para #: boot-installer.xml:1640 #, no-c-format msgid "" "If you are using a 2.2.x linux kernel, then you need to use the " "&ramdisksize; kernel parameter." msgstr "如果您在使用 2.2.x 内核,那么需要设置 &ramdisksize; 内核参数。" #. Tag: para #: boot-installer.xml:1645 #, no-c-format msgid "" "Make sure root=/dev/ram is one of your kernel " "parameters." msgstr "确保 root=/dev/ram 在内核参数中。" #. Tag: para #: boot-installer.xml:1650 #, no-c-format msgid "" "If you're having trouble, check cts's " "&arch-title; debian-installer FAQ." msgstr "" "如果碰到麻烦,检查 cts's &arch-title; " "debian-installer FAQ。" #. Tag: title #: boot-installer.xml:1667 #, no-c-format msgid "Amiga" msgstr "Amiga" #. Tag: para #: boot-installer.xml:1668 #, no-c-format msgid "" "The only method of installation available to amiga is the hard drive (see " "). In other words the cdrom is not " "bootable." msgstr "" "amiga 仅支持从硬盘安装方式(参阅 )。" "也就是说 cdrom 无法启动。" #. Tag: para #: boot-installer.xml:1674 #, no-c-format msgid "" "Amiga does not currently work with bogl, so if you are seeing bogl errors, " "you need to include the boot parameter fb=false." msgstr "" "当前 Amiga 不能与 bogl 一起工作,如果您看到 bogl 错误,您应该包含下面内核参" "数 fb=false。" #. Tag: title #: boot-installer.xml:1683 #, no-c-format msgid "Atari" msgstr "Atari" #. Tag: para #: boot-installer.xml:1684 #, no-c-format msgid "" "The installer for atari may be started from either the hard drive (see ) or from floppies (see ). In other words the cdrom is not bootable." msgstr "" "atari 安装程序可以从硬盘(参阅 ) 或软盘 (参阅 " ")。也就是说 cdrom 无法启动。" "" #. Tag: para #: boot-installer.xml:1691 #, no-c-format msgid "" "Atari does not currently work with bogl, so if you are seeing bogl errors, " "you need to include the boot parameter fb=false." msgstr "" "当前 Atari 不能与 bogl 一起工作,如果您看到 bogl 错误,应该包含下面内核参数 " "fb=false。" #. Tag: title #: boot-installer.xml:1700 #, no-c-format msgid "BVME6000" msgstr "BVME6000" #. Tag: para #: boot-installer.xml:1701 #, no-c-format msgid "" "The installer for BVME6000 may be started from a cdrom (see ), floppies (see ), or the net (see )." msgstr "" "BVME6000 上安装程序可以从 cdrom (参阅 ), " "软盘(参阅 ),或网络(参阅 )。" #. Tag: title #: boot-installer.xml:1711 #, no-c-format msgid "Macintosh" msgstr "Macintosh" #. Tag: para #: boot-installer.xml:1712 #, no-c-format msgid "" "The only method of installation available to mac is from the hard drive (see " "). In other words the cdrom is not " "bootable. Macs do not have a working 2.4.x kernel." msgstr "" "mac 上启动的唯一方法是硬盘(参阅 )。" "也就是说 cdrom 无法启动。 Macs 不能工作在 2.4 内核上。" #. Tag: para #: boot-installer.xml:1719 #, no-c-format msgid "" "If your hardware uses a 53c9x-based scsi bus, then you may need to include " "the kernel parameter mac53c9x=1,0. Hardware with two " "such scsi buses, such as the Quadra 950, will need mac53c9x=2,0 instead. Alternatively, the parameter can be specified as " "mac53c9x=-1,0 which will leave autodetection on, but " "which will disable SCSI disconnects. Note that specifying this parameter is " "only necessary if you have more than one hard disk; otherwise, the system " "will run faster if you do not specify it." msgstr "" "如果您的硬件中包括基于 53c9x 的 scsi 总线,那么您需要包括下面的内核参数 " "mac53c9x=1,0。带有两个这种 scsi 总线的硬件,如 Quadra " "950,您需要 mac53c9x=2,0 参数。另外,参数指定为 " "mac53c9x=-1,0 可打开自动侦测,但却禁止了 SCSI 断开。注" "意,使用这种参数仅用于不止一个硬盘的情况下; 如果不指定,您的系统将运行得更" "快。" #. Tag: title #: boot-installer.xml:1734 #, no-c-format msgid "MVME147 and MVME16x" msgstr "MVME147 and MVME16x" #. Tag: para #: boot-installer.xml:1735 #, no-c-format msgid "" "The installer for MVME147 and MVME16x may be started from either floppies " "(see ) or the net (see ). In other words the cdrom is not bootable." msgstr "" "MVEM147 和 MVEM16x 可以从软盘(参阅 )或" "网络(参阅 )。也就是说 cdrom 无法启动。" "" #. Tag: title #: boot-installer.xml:1745 #, no-c-format msgid "Q40/Q60" msgstr "Q40/Q60" #. Tag: para #: boot-installer.xml:1746 #, no-c-format msgid "" "The only method of installation available to Q40/Q60 is from the hard drive " "(see ). In other words the cdrom " "is not bootable." msgstr "" "Q40/Q60 只支持从硬盘安装(参阅 )。也" "就是说 cdrom 无法启动。" #. Tag: title #: boot-installer.xml:1757 #, no-c-format msgid "Booting from a Hard Disk" msgstr "从硬盘引导" # index.docbook:1591, index.docbook:2097 #. Tag: para #: boot-installer.xml:1763 boot-installer.xml:2361 #, no-c-format msgid "" "Booting from an existing operating system is often a convenient option; for " "some systems it is the only supported method of installation." msgstr "" "从一个以存在的操作系统上引导通常是一个方便的选择;对于一些系统来说,这则是唯" "一支持的 安装方法。" # index.docbook:1597, index.docbook:2103 #. Tag: para #: boot-installer.xml:1769 boot-installer.xml:2367 #, no-c-format msgid "" "To boot the installer from hard disk, you will have already completed " "downloading and placing the needed files in ." msgstr "" "如果要从硬盘上引导安装程序,您也许已经在 处下载并且在 安置了所需文件。" #. Tag: para #: boot-installer.xml:1778 #, no-c-format msgid "" "At least six different ramdisks may be used to boot from the hard drive, " "three different types each with and without support for a 2.2.x linux kernel " "(see MANIFEST for details)." msgstr "" "至少有六中不同的 ramdisk 可以从硬盘启动,三个不同的类型分别用于支持或不支持 " "2.2.x linux 内核(参阅 MANIFEST 了解更多细节)。" #. Tag: para #: boot-installer.xml:1786 #, no-c-format msgid "" "The three different types of ramdisks are cdrom, " "hd-media, and nativehd. These " "ramdisks differ only in their source for installation packages. The " "cdrom ramdisk uses a cdrom to get debian-installer " "packages. The hd-media ramdisk uses an iso image file " "of a cdrom currently residing on a hard disk. Finally, the " "nativehd ramdisk uses the net to install packages." msgstr "" "这三种 ramdisk 类型为 cdrom, hd-media,和 nativehd。它们的区别仅在于安装软件包的源不" "同。cdrom ramdisk 使用 cdrom 获取 debian-installer 软件" "包。hd-media ramdisk 使用硬盘上的 iso 映象文件。最后," "nativehd ramdisk 使用网络安装软件包。" #. Tag: title #: boot-installer.xml:1807 #, no-c-format msgid "Booting from AmigaOS" msgstr "从 AmigaOS 上引导" #. Tag: para #: boot-installer.xml:1808 #, no-c-format msgid "" "In the Workbench, start the Linux installation process by " "double-clicking on the StartInstall icon in the " "debian directory." msgstr "" "在 Workbench 下,双击 StartInstall 图标" "来启动 Linux 安装过程,它位于 debian 目录中。" #. Tag: para #: boot-installer.xml:1814 #, no-c-format msgid "" "You may have to press the &enterkey; key twice after the Amiga installer " "program has output some debugging information into a window. After this, the " "screen will go grey, there will be a few seconds' delay. Next, a black " "screen with white text should come up, displaying all kinds of kernel " "debugging information. These messages may scroll by too fast for you to " "read, but that's OK. After a couple of seconds, the installation program " "should start automatically, so you can continue down at ." msgstr "" "在 Amiga 安装程序在一个窗口已经输出一些调试信息,您也可以按下 &enterkey; 两" "次。之后屏幕将变灰,这里有一些很短的延迟。接下来,一个黑屏白字将显示更多的调" "试信息。这些 信息可能上翻的非常快无法看到,但这没有问题。在一些时间过后,安装" "程序应该自动安装,因此您可以继续参阅 。" #. Tag: title #: boot-installer.xml:1829 #, no-c-format msgid "Booting from Atari TOS" msgstr "从 Atari TOS 引导" #. Tag: para #: boot-installer.xml:1830 #, no-c-format msgid "" "At the GEM desktop, start the Linux installation process by double-clicking " "on the bootstra.prg icon in the debian directory and clicking Ok at the program " "options dialog box." msgstr "" "在 GEM 桌面上,可以通过双击 bootstra.prg 图标,它位于 " "debian 目录下,并且在程序选项对话框内点击 " "Ok 来开始启动安装过程。" #. Tag: para #: boot-installer.xml:1837 #, no-c-format msgid "" "You may have to press the &enterkey; key after the Atari bootstrap program " "has output some debugging information into a window. After this, the screen " "will go grey, there will be a few seconds' delay. Next, a black screen with " "white text should come up, displaying all kinds of kernel debugging " "information. These messages may scroll by too fast for you to read, but " "that's OK. After a couple of seconds, the installation program should start " "automatically, so you can continue below at ." msgstr "" "当 Atari 安装程序在一个窗口输出一些调试信息以后,您可能必须按下 &enterkey;。" "之后屏幕将变灰,这里有一些很短的延迟。接下来,一个黑屏白字将显示更多的调试信" "息。这些信息可能上翻的非常快没法看,但这没有问题。在一些时间过后,安装程序应" "该自动安装,因此您可以继续参阅 。" #. Tag: title #: boot-installer.xml:1852 #, no-c-format msgid "Booting from MacOS" msgstr "从 MacOS 引导" #. Tag: para #: boot-installer.xml:1853 #, no-c-format msgid "" "You must retain the original Mac system and boot from it. It is " "essential that, when booting MacOS in preparation for " "booting the Penguin linux loader, you hold the shift key " "down to prevent extensions from loading. If you don't use MacOS except for " "loading linux, you can accomplish the same thing by removing all extensions " "and control panels from the Mac's System Folder. Otherwise extensions may be " "left running and cause random problems with the running linux kernel." msgstr "" "您必须有原来的 Mac 系统,并从它启动。它是 必要的,当启" "动 MacOS 准备启动 Penguin linux 加载器时,按住 shift 键阻止" "加载扩展。如果除了加载 linux 不使用 MacOS,您可以从 Mac 的系统文件夹下清除所" "有的扩展和控制面板达到同样的目的。否则扩展会运行使运行的 linux 内核参数随机错" "误。" #. Tag: para #: boot-installer.xml:1864 #, no-c-format msgid "" "Macs require the Penguin bootloader. If you do not have " "the tools to handle a Stuffit archive, &penguin19.hfs; is " "an hfs disk image with Penguin unpacked. describes how to copy this image to a floppy." msgstr "" "Mac 要求 Penguin 加载器。如果您没有这个工具,要把 " "Stuffit 归档,&penguin19.hfs; 是一个 hfs 磁盘映象,带有 " "Penguin 解压包。 说明如何" "将该映象复制到软盘。" #. Tag: para #: boot-installer.xml:1873 #, no-c-format msgid "" "At the MacOS desktop, start the Linux installation process by double-" "clicking on the Penguin Prefs icon in the " "Penguin directory. The Penguin " "booter will start up. Go to the Settings item in " "the File menu, click the Kernel tab. " "Select the kernel (vmlinuz) and ramdisk " "(initrd.gz) images in the install " "directory by clicking on the corresponding buttons in the upper right " "corner, and navigating the file select dialogs to locate the files." msgstr "" "在 MacOS 桌面,启动 Linux 安装进行需要双击 Penguin Prefs " "图标,它位于 Penguin 目录。Penguin 引" "导将开始。进入到 Settings 项,它位于 " "File菜单,点击 Kernel 选项卡。选择内" "核(vmlinuz)和 ramdisk (initrd.gz) " "映象,它位于 install 目录,点击右上角对应的按钮,引导文" "件选择对话框至文件。" #. Tag: para #: boot-installer.xml:1888 #, no-c-format msgid "" "To set the boot parameters in Penguin, choose File -> " "Settings..., then switch to the " "Options tab. Boot parameters may be typed in to the " "text entry area. If you will always want to use these settings, select " "File -> Save Settings as Default." msgstr "" "为 Penguin 设置启动参数,选择 File -> " "Settings...,然后切换到 Options 选项卡。启动参数可以写到文本区域。如果您要一直采用这些设置,选择 " "File -> 保存设置为默认。" #. Tag: para #: boot-installer.xml:1897 #, no-c-format msgid "" "Close the Settings dialog, save the settings and start " "the bootstrap using the Boot Now item in the " "File menu." msgstr "" "关闭 Settings 对话框,保存设置然后开始引导用 " "Boot Now 项,它位于 File 菜单。" #. Tag: para #: boot-installer.xml:1904 #, no-c-format msgid "" "The Penguin booter will output some debugging information " "into a window. After this, the screen will go grey, there will be a few " "seconds' delay. Next, a black screen with white text should come up, " "displaying all kinds of kernel debugging information. These messages may " "scroll by too fast for you to read, but that's OK. After a couple of " "seconds, the installation program should start automatically, so you can " "continue below at ." msgstr "" "Penguin 启动将输出一些调试信息到窗口。然后,屏幕变灰,会有" "数秒延迟。接着,带有文本的黑屏出现,显示各种内核调试信息。这些信息可能滚动很" "快无法阅读,这是正常的。再过一段时间,安装程序就会自动运行,您可以按下面步骤" "继续 。" #. Tag: title #: boot-installer.xml:1919 #, no-c-format msgid "Booting from Q40/Q60" msgstr "从 Q40/Q60 启动" #. Tag: para #: boot-installer.xml:1921 #, no-c-format msgid "FIXME" msgstr "FIXME" #. Tag: para #: boot-installer.xml:1925 #, no-c-format msgid "" "The installation program should start automatically, so you can continue " "below at ." msgstr "" "安装程序就会自动运行,您可以按下面步骤继续 。" #. Tag: para #: boot-installer.xml:1937 #, no-c-format msgid "" "Currently, the only &arch-title; subarchitecture that supports CD-ROM " "booting is the BVME6000." msgstr "目前唯一 &arch-title; 子体系结构支持 CD 光盘引导的是 BVME6000。" #. Tag: para #: boot-installer.xml:2009 #, no-c-format msgid "" "After booting the VMEbus systems you will be presented with the LILO " "Boot: prompt. At that prompt enter one of the following to " "boot Linux and begin installation proper of the Debian software using vt102 " "terminal emulation:" msgstr "" "在引导 VMEbus 系统后您应该看到 LILO Boot: 提示符。在提示符下" "输入以下一种方法来引导 Linux,并开始在一个 vt102 仿真终端下面安装普通的 " "Debian 软件。" #. Tag: para #: boot-installer.xml:2020 #, no-c-format msgid "type i6000 &enterkey; to install a BVME4000/6000" msgstr "输入 i6000 &enterkey; 来安装 BVME4000/6000" #. Tag: para #: boot-installer.xml:2025 #, no-c-format msgid "type i162 &enterkey; to install an MVME162" msgstr "输入 i162 &enterkey; 来安装 MVME162" #. Tag: para #: boot-installer.xml:2030 #, no-c-format msgid "type i167 &enterkey; to install an MVME166/167" msgstr "输入 i167 &enterkey; 来安装 MVME166/167" #. Tag: para #: boot-installer.xml:2037 #, no-c-format msgid "" "You may additionally append the string TERM=vt100 to use " "vt100 terminal emulation, e.g., i6000 TERM=vt100 &enterkey;." msgstr "" "您也可以附加一个字符串 TERM=vt100 来使用 vt100 终端模拟。比" "如,i6000 TERM=vt100 &enterkey;。" #. Tag: para #: boot-installer.xml:2049 #, no-c-format msgid "" "For most &arch-title; architectures, booting from a local filesystem is the " "recommended method." msgstr "对于大多数 m68k 体系来说,推荐方法是从一个本地文件系统引导安装程序。" #. Tag: para #: boot-installer.xml:2054 #, no-c-format msgid "" "Booting from the boot floppy is supported only for Atari and VME (with a " "SCSI floppy drive on VME) at this time." msgstr "从软盘引导的方法目前只支持 Atari 以及 VME (VME 有一个 SCSI 软驱)。" # index.docbook:1899, index.docbook:1946 #. Tag: title #: boot-installer.xml:2070 boot-installer.xml:2117 #, no-c-format msgid "SGI TFTP Booting" msgstr "SGI TFTP 引导" #. Tag: para #: boot-installer.xml:2071 #, no-c-format 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" " 可以达到此目的。" # index.docbook:1919, index.docbook:1968 #. Tag: title #: boot-installer.xml:2090 boot-installer.xml:2139 boot-installer.xml:2194 #: boot-installer.xml:2233 #, no-c-format msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" msgstr "Broadcom BCM91250A 与 BCM91480B TFTP 引导" #. Tag: para #: boot-installer.xml:2091 boot-installer.xml:2195 #, no-c-format msgid "" "On the Broadcom BCM91250A and BCM91480B evaluation boards, you have to load " "the SiByl boot loader via TFTP which will then load and start the Debian " "installer. In most cases, you will first obtain an IP address via DHCP but " "it is also possible to configure a static address. In order to use DHCP, you " "can enter the following command on the CFE prompt: " "\n" "ifconfig eth0 -auto\n" " Once you have obtained an IP address, you can " "load SiByl with the following command: \n" "boot 192.168.1.1:/boot/sibyl\n" " You need to substitute the IP address listed in " "this example with either the name or the IP address of your TFTP server. " "Once you issue this command, the installer will be loaded automatically." msgstr "" "在 Broadcom BCM91250A 和 BCM91480B 开发板上,您不得不通过 TFTP 加载 SiByl 引" "导程序,它接着将加载和启动 Debian 安装程序。大多数情况下,您通过 DHCP 获得 " "IP 地址,当然也可以指定静态地址。要使用 DHCP,您可以在下面 CFE 提示符下输入命" "令: \n" "ifconfig eth0 -auto\n" " 一旦得到 IP 地址,就可以使用下面命令加载 SiByl: " "\n" "boot 192.168.1.1:/boot/sibyl\n" " 您要用 TFTP 服务器的 IP 地址或域名替换上面例子中" "的 IP 地址。输入以后,安装程序就会自动加载。" # index.docbook:1943, index.docbook:2477 #. Tag: title #: boot-installer.xml:2114 boot-installer.xml:2218 boot-installer.xml:2741 #, no-c-format msgid "Boot Parameters" msgstr "引导参数" #. Tag: para #: boot-installer.xml:2118 #, no-c-format msgid "" "On SGI machines you can append boot parameters to the bootp(): command in the command monitor." msgstr "" "在 SGI 上您可以在命令监视器下给 bootp(): 命令附加一个引导" "参数。" #. Tag: para #: boot-installer.xml:2123 #, no-c-format 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:" #. Tag: screen #: boot-installer.xml:2133 #, no-c-format msgid "bootp(): append=\"root=/dev/sda1\"" msgstr "bootp(): append=\"root=/dev/sda1\"" #. Tag: para #: boot-installer.xml:2140 boot-installer.xml:2234 #, no-c-format msgid "" "You cannot pass any boot parameters directly from the CFE prompt. Instead, " "you have to edit the /boot/sibyl.conf file on the TFTP " "server and add your parameters to the extra_args " "variable." msgstr "" "您不能从 CFE 提示符直接传递启动参数。而是编辑 TFTP 服务器上的 /" "boot/sibyl.conf 文件并添加参数到 extra_args 变量。" # index.docbook:1899, index.docbook:1946 #. Tag: title #: boot-installer.xml:2159 boot-installer.xml:2221 #, no-c-format msgid "Cobalt TFTP Booting" msgstr "Cobalt TFTP 引导" #. Tag: para #: boot-installer.xml:2160 #, no-c-format 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 网络启动。它会在显示器上显示几个选项。有下面两种安装方法:" #. Tag: para #: boot-installer.xml:2170 #, no-c-format 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 连接" "到机器就可以开始安装。" #. Tag: para #: boot-installer.xml:2179 #, no-c-format 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. This option is not available on Qube 2700 (Qube1) machines since " "they have no serial port." msgstr "" "通过串口控制台:使用 null modem 线,您可以连接到 Cobalt 机器的串口 (使用 " "115200 bps) 然后进行安装。此选项不会出现在 Qube 2700 (Qube1) 机器上,因为它没" "有串口。" #. Tag: para #: boot-installer.xml:2222 #, no-c-format 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 变量。" #. Tag: title #: boot-installer.xml:2250 #, no-c-format msgid "s390 Limitations" msgstr "s390 的限制" #. Tag: para #: boot-installer.xml:2251 #, 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:2256 #, 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:2267 #, no-c-format msgid "s390 Boot Parameters" msgstr "s390 引导参数" #. Tag: para #: boot-installer.xml:2268 #, 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. Please read Device Drivers and Installation Commands for more " "information about S/390-specific boot parameters." msgstr "" "在 S/390 上您可以在参数文件下面附加一些引导参数。这个文件可以是 ASCII 或者 " "EBCDIC格式的。请阅读 设备驱动程序以及安装命" "令 来获得更多有关 S/390 特定的引导参数。" #. Tag: para #: boot-installer.xml:2322 #, no-c-format msgid "" "Currently, the only &arch-title; subarchitectures that support CD-ROM " "booting are PReP 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 CD-ROM." msgstr "" "当前来说,&arch-title; 下的子体系结构只有 PReP 和 New World PowerMacs 支持 " "CD 光盘引导。在 PowerMacs 下 在从 CD 光盘上引导时,按住 c " "键,或者组合键 Command, Option, " "Shift, 和 Delete 。" #. Tag: para #: boot-installer.xml:2331 #, no-c-format msgid "" "OldWorld PowerMacs will not boot a Debian CD, because OldWorld computers " "relied on a Mac OS ROM CD boot driver to be present on the CD, and a free-" "software version of this driver is not available. All OldWorld systems have " "floppy drives, so use the floppy drive to launch the installer, and then " "point the installer to the CD for the needed files." msgstr "" "OldWorld Powermacs 不能从一张 Debian CD 上引导,因为 OldWorld 计算机需要在 " "CD 上安装一个 MacOSROM CD 引导驱动程序但是目前还没有自由的版本。所有的 " "OldWorld 系统具有软盘驱动程序,因此可以使用软盘驱动程序来启动安装程序,然后让" "安装程序 从 CD 上选择所需要的文件。" #. Tag: para #: boot-installer.xml:2340 #, no-c-format msgid "" "If your system doesn't boot directly from CD-ROM, you can still use the CD-" "ROM to install the system. On NewWorlds, you can also use an OpenFirmware " "command to boot from the CD-ROM manually. Follow the instructions in for booting from the hard disk, except use the " "path to yaboot on the CD at the OF prompt, such as" msgstr "" "如果您的系统不支持直接从 CD 光盘启动,仍然可以采用 CD 光盘来安装系统。在 " "NewWorlds 上面,可以使用一个 OpenFirmware 命令来手工从 CD 光盘引导。按照 " " 的方法从硬盘来进行引导,只是在 OF 提示符下" "使用 CD 上的 yaboot 路径,比如:" #. Tag: screen #: boot-installer.xml:2349 #, no-c-format msgid "0 > boot cd:,\\install\\yaboot" msgstr "0 > boot cd:,\\install\\yaboot" #. Tag: title #: boot-installer.xml:2355 #, no-c-format msgid "Booting from Hard Disk" msgstr "从硬盘引导" #. Tag: title #: boot-installer.xml:2376 #, no-c-format msgid "Booting CHRP from OpenFirmware" msgstr "从 OpenFirmware 引导 CHRP" #. Tag: emphasis #: boot-installer.xml:2380 #, no-c-format msgid "Not yet written." msgstr "还没有完成" #. Tag: title #: boot-installer.xml:2385 #, no-c-format msgid "Booting OldWorld PowerMacs from MacOS" msgstr "从 OldWorld PowerMacs 的 MacOS 上引导" #. Tag: para #: boot-installer.xml:2386 #, no-c-format msgid "" "If you set up BootX in , you can use it to " "boot into the installation system. Double click the BootX " "application icon. Click on the Options button and " "select Use Specified RAM Disk. This will give you the " "chance to select the ramdisk.image.gz file. You may " "need to select the No Video Driver checkbox, depending " "on your hardware. Then click the Linux button to shut " "down MacOS and launch the installer." msgstr "" "如果您在 中设置好了 BootX,您可以使用它引" "导进入安装系统。双击 BootX 应用程序图标。点击 " "Options 按钮并且选择 Use Specified RAM " "Disk。这将可以让您选择 ramdisk.image.gz 文" "件。也许根据您的硬件情况需要选择 No Video Driver 选择" "框。然后点击 Linux 按钮,来关闭 MacOS 以及启动安装程" "序。" #. Tag: title #: boot-installer.xml:2404 #, no-c-format msgid "Booting NewWorld Macs from OpenFirmware" msgstr "从 NewWorld Macs 的 OpenFirmware 引导" #. Tag: para #: boot-installer.xml:2405 #, no-c-format msgid "" "You will have already placed the vmlinux, " "initrd.gz, yaboot, and " "yaboot.conf files at the root level of your HFS " "partition in . Restart the computer, and " "immediately (during the chime) hold down the Option, " "Command (cloverleaf/Apple), o, and " "f keys all together. After a few seconds you will be " "presented with the Open Firmware prompt. 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 "" "您也许已经按照 vmlinux, initrd.gz, " "yabootyaboot.conf 在 HFS 分区的" "根层次放置好了 文件。请重新启动计算机,并" "且立即(在发声时)同时按住 Option, Command " "(cloverleaf/Apple), o, 和 f 键。过" "几秒钟后,将进入 Open Firmware 提示符。在提示符下,输入: " "\n" "0 > boot hd:x,yaboot\n" " 用放置内核和 yaboot 文件的 HFS 分区号来替换 " "x 然后按下 &enterkey;。在某些机器上,您也许需要时" "用 ide0: 来替换 hd:,在接下来的" "几秒钟内,将会看到一个提示符 \n" "boot:\n" " 在 yaboot 的 boot: 提示符下,输" "入 install 或者 install video=ofonly 然后点击 &enterkey;。video=ofonly 参数是用" "于最大可能性的兼容性;您可以在 install 不工作的情况下" "尝试使用它。Debian 安装程序应该立刻启动。" # index.docbook:700, index.docbook:2176 #. Tag: title #: boot-installer.xml:2440 #, no-c-format msgid "Booting from USB memory stick" msgstr "从 USB 闪盘引导" #. Tag: para #: boot-installer.xml:2441 #, no-c-format msgid "Currently, NewWorld PowerMac systems are known to support USB booting." msgstr "当前,New World PowerMac 系统支持从 USB 引导。" #. Tag: para #: boot-installer.xml:2447 #, no-c-format msgid "" "Make sure you have prepared everything from . To boot a Macintosh system from a USB stick, you will need to use the " "Open Firmware prompt, since Open Firmware does not search USB storage " "devices by default. To get to the prompt, hold down " "Command Option o f all together while booting (see )." msgstr "" "确认您已经准备就绪 。要从 USB 记忆棒引导 " "Macintosh 系统,即使 Open Firmware 默认不搜索 USB 存储设备,您也需要使用 " "Open Firmware 提示符。要得到提示符,在启动时按住 Command Option o f (参考 )。" #. Tag: para #: boot-installer.xml:2459 #, no-c-format msgid "" "You will need to work out where the USB storage device appears in the device " "tree, since at the moment ofpath cannot work that out " "automatically. Type dev / ls and devalias at the Open Firmware prompt to get a list of all known devices " "and device aliases. On the author's system with various types of USB stick, " "paths such as usb0/disk, usb0/hub/disk, /pci@f2000000/usb@1b,1/disk@1, and " "/pci@f2000000/usb@1b,1/hub@1/disk@1 work." msgstr "" "您还需要算出 USB 存储设备在设备树上的位置,因为现在 ofpath 无法自动计算。键入 dev / ls 和 " "devalias 到 Open Firmware 提示符下,得到所有的已知设备" "和设备别名。在笔者的系统上有各种 USB 记忆棒,路径诸如 usb0/disk, usb0/hub/disk, /pci@f2000000/" "usb@1b,1/disk@1,和 /pci@f2000000/usb@1b,1/hub@1/" "disk@1 。" #. Tag: para #: boot-installer.xml:2471 #, no-c-format msgid "" "Having worked out the device path, use a command like this to boot the " "installer: \n" "boot usb0/disk:2,\\\\:" "tbxi\n" " The 2 matches the " "Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image " "earlier, and the ,\\\\:tbxi part instructs Open " "Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. " "yaboot) in the directory previously blessed with " "hattrib -b." msgstr "" "得到设备路径之后,用类似下面的命令启动安装程序: \n" "boot usb0/disk:2,\\\\:" "tbxi\n" " 2 匹配前面复制启动映象" "所在的 Apple_HFS 或 Apple_Bootstrap 分区,,\\\\:tbxi " "部分指示 Open Firmware 从具有 \"tbxi\" 类型的 HFS 文件引导(如 " "yaboot) 位于前面使用 bless 目录 hattrib -b。" #. Tag: para #: boot-installer.xml:2485 #, no-c-format msgid "" "The system should now boot up, and you should be presented with the " "boot: prompt. Here you can enter optional boot arguments, " "or just hit &enterkey;." msgstr "" "系统应该可以引导,然后您看到 boot: 提示符。这里您可以输入启" "动参数,或者只按下 &enterkey;。" #. Tag: para #: boot-installer.xml:2491 #, no-c-format msgid "" "This boot method is new, and may be difficult to get to work on some " "NewWorld systems. If you have problems, please file an installation report, " "as explained in ." msgstr "" "这个是新的启动方法,可能无法在一些 NewWorld 系统上工作。如果您遇到问题,请写" "下安装报告,参阅 。" #. Tag: para #: boot-installer.xml:2524 #, no-c-format msgid "Currently, PReP and New World PowerMac systems support netbooting." msgstr "目前来说,PReP 以及 New World PowerMac 系统支持网络引导。" #. Tag: para #: boot-installer.xml:2528 #, no-c-format msgid "" "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot " "monitor (see ) and use the command " "boot enet:0. PReP and CHRP boxes may have different ways " "of addressing the network. On a PReP machine, you should try boot " "server_ipaddr,file," "client_ipaddr." msgstr "" "在 Open Firmware 机器上,比如 NewWorld Power Macs,进入引导监视器(参阅 ) 并且使用命令 boot enet:0。PReP 以及 CHRP 可能使用不同的途径来确认网络。在一台 PReP 机器上,您" "应该尝试 boot server_ipaddr," "file,client_ipaddr。" #. Tag: para #: boot-installer.xml:2543 #, no-c-format msgid "" "Booting from floppies is supported for &arch-title;, although it is " "generally only applicable for OldWorld systems. NewWorld systems are not " "equipped with floppy drives, and attached USB floppy drives are not " "supported for booting." msgstr "" "&arch-title; 支持从软盘引导,尽管它本来只适合 OldWorld 系统。NewWorld 系统并" "没有安装 软盘驱动器,并且附带的 USB 软盘并不支持引导。" #. Tag: para #: boot-installer.xml:2555 #, no-c-format msgid "" "To boot from the boot-floppy-hfs.img floppy, place it " "in floppy drive after shutting the system down, and before pressing the " "power-on button." msgstr "" "若需要从 boot-floppy-hfs.img 软盘引导,请在关闭系统后在" "按下电源开关前把它放到软盘驱动器内。" #. Tag: para #: boot-installer.xml:2561 #, no-c-format msgid "" "For those not familiar with Macintosh floppy operations: a floppy placed in " "the machine prior to boot will be the first priority for the system to boot " "from. A floppy without a valid boot system will be ejected, and the machine " "will then check for bootable hard disk partitions." msgstr "" "对于不熟悉 Macintosh 软盘操作的人来说:一个放在软驱的软盘将获得第一优先引导顺" "序。一个 没有有效引导系统的软盘将回被弹出,并且机器将检查硬盘分区。" #. Tag: para #: boot-installer.xml:2568 #, no-c-format msgid "" "After booting, the root.bin floppy is requested. Insert " "the root floppy and press &enterkey;. The installer program is automatically " "launched after the root system has been loaded into memory." msgstr "" "引导之后需要含有 root.bin 的软盘。插入引导软盘并且按下 " "&enterkey;。安装程序将在根系统被装入内存后自动启动。" #. Tag: title #: boot-installer.xml:2579 #, no-c-format msgid "PowerPC Boot Parameters" msgstr "PowerPC 引导参数" #. Tag: para #: boot-installer.xml:2580 #, no-c-format msgid "" "Many older Apple monitors used a 640x480 67Hz mode. If your video appears " "skewed on an older Apple monitor, try appending the boot argument " "video=atyfb:vmode:6 , which will select that mode for " "most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to " "video=aty128fb:vmode:6 ." msgstr "" "许多比较老的 Apple 显示器使用 640x480 67Hz 模式。如果您的显示在这些老 Apple " "显示器上是扭曲的,请尝试加入引导参数 video=atyfb:vmode:6 。它将为大多数 Mach64 和 Rage 显示设备选择合适的模式。对于 Rage " "128 来说,请改变其值为 video=aty128fb:vmode:6 。" #. Tag: para #: boot-installer.xml:2620 #, no-c-format msgid "" "On machines with OpenBoot, simply enter the boot monitor on the machine " "which is being installed (see ). Use " "the command boot net to boot from a TFTP and RARP " "server, or try boot net:bootp or boot net:" "dhcp to boot from a TFTP and BOOTP or DHCP server. Some older " "OpenBoot revisions require using the device name, such as boot le" "(); these probably don't support BOOTP nor DHCP." msgstr "" "在有 OpenBoot 的机器上,简单地进入安装机器的引导监视器, (参见 )。请使用命令 boot net 来从一" "个 TFTP 和 RARP 服务器上引导,或者也可以用 boot net:bootpboot net:dhcp 来从一个 TFTP 和 DHCP 服务" "器上引导。一些比较老的 OpenBoot 版本需要使用设备名称,例如 boot le" "();这些可能不支持 DHCP。" #. Tag: para #: boot-installer.xml:2676 #, no-c-format msgid "" "Most OpenBoot versions support the boot cdrom command " "which is simply an alias to boot from the SCSI device on ID 6 (or the " "secondary master for IDE based systems). You may have to use the actual " "device name for older OpenBoot versions that don't support this special " "command. Note that some problems have been reported on Sun4m (e.g., Sparc " "10s and Sparc 20s) systems booting from CD-ROM." msgstr "" "大多数 OpenBoot 版本支持 boot cdrom 命令。它其实是从 " "ID 为 6 的 SCSI 设备进行引导的一个别名。(对于 IDE 系统来说,它是第二个主硬" "盘)。在较早的 OpenBoot 版本上,您可能必须使用实际的设备名称,因为它们不支持这" "个特殊的命令。注意在 Sun4m (比如 Sparc 10s 和 Sparc 20s) 系统上用 CD 光盘引导" "据说有些问题。" #. Tag: para #: boot-installer.xml:2691 #, no-c-format msgid "" "To boot from floppy on a Sparc, use \n" "Stop-A -> OpenBoot: \"boot floppy\"\n" " Be warned that the newer Sun4u (ultra) " "architecture does not support floppy booting. A typical error message is " "Bad magic number in disk label - Can't open disk label " "package. Furthermore, a number of Sun4c models (such as the " "IPX) do not support the compressed images found on the disks, so also are " "not supported." msgstr "" "在 SPARC 机器上用软驱引导,请使用 \n" "Stop-A -> OpenBoot: \"boot floppy\"\n" " 注意更新的 Sun4u (ultra) 结构不支持软驱引导,一个" "标准的错误信息是 Bad magic number in disk label - Can't open " "disk label package。甚至,一些 Sun4c 型号 (比如 IPX) 不支持" "磁盘上找到的压缩 映像,所以这些都不被支持。" #. Tag: para #: boot-installer.xml:2703 #, no-c-format msgid "" "Several Sparcs (e.g. Ultra 10) have an OBP bug that prevents them from " "booting (instead of not supporting booting at all). The appropriate OBP " "update can be downloaded as product ID 106121 from ." msgstr "" "不少 Sparcs (比如 Ultra 10) 有一个 OBP 缺陷。它阻止这些机器引导 (从而完全不支" "持引导)。合适的 OBP 更新可以从下面连接的 ID 106121 中获得,。" #. Tag: para #: boot-installer.xml:2710 #, no-c-format msgid "" "If you are booting from the floppy, and you see messages such as " "\n" "Fatal error: Cannot read partition\n" "Illegal or malformed device name\n" " then it is possible that floppy booting is " "simply not supported on your machine." msgstr "" "如果您正在从软盘引导,并且看到如下信息 \n" "Fatal error: Cannot read partition\n" "Illegal or malformed device name\n" " 那么很可能您的机器不支持软盘引导。" #. Tag: title #: boot-installer.xml:2722 #, no-c-format msgid "IDPROM Messages" msgstr "IDPROM 消息" #. Tag: para #: boot-installer.xml:2723 #, no-c-format msgid "" "If you cannot boot because you get messages about a problem with " "IDPROM, then it's possible that your NVRAM battery, which " "holds configuration information for you firmware, has run out. See the " "Sun NVRAM FAQ for more " "information." msgstr "" "如果您由于得到一个有关IDPROM问题的消息而不能引导,这可能是 " "NVRAM 电池已经用光。通常它为固件保持配置信息。请查阅 Sun NVRAM FAQ 以获得更多信息。" #. Tag: para #: boot-installer.xml:2742 #, 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:2749 #, 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:2756 #, 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: para #: boot-installer.xml:2765 #, no-c-format msgid "" "When the kernel boots, a message \n" "Memory:availk/totalk " "available\n" " should be emitted early in the process. " "total should match the total amount of RAM, in " "kilobytes. If this doesn't match the actual amount of RAM you have " "installed, you need to use the mem=ram parameter, where ram is " "set to the amount of memory, suffixed with k for kilobytes, " "or m for megabytes. For example, both mem=65536k and mem=64m mean 64MB of RAM." msgstr "" "当内核引导的时候,有一条消息 \n" "Memory:availk/totalk " "available \n" " 应该显示在引导过程的早期。其中 " "total 应该符合您内存的总量,单位为千字节。如果此参" "数不符合您实际的内存总数,需要使用 mem=ram 参数。这里 ram 被设置为内" "存的数量。如是k则为千字节,m为兆字节。例如," "mem=65536kmem=64m 标明 " "64MB 内存。" #. Tag: para #: boot-installer.xml:2781 #, no-c-format msgid "" "If you are booting with a serial console, generally the kernel will " "autodetect this (although not on DECstations). If you have a videocard (framebuffer) and a keyboard also attached " "to the computer which you wish to boot via serial console, you may have to " "pass the console=device " "argument to the kernel, where device is your " "serial device, which is usually something like ttyS0." msgstr "" "如果您通过一个串行控制台引导,一般来说内核将自动检测" "(尽管不是在一台 DECstations 上面)。如果您有一块显示卡(framebuffer)和" "一个键盘,通过串口附加于想引导的计算机上面,也许需要传递 " "console=device 参数给内核," "这里 device 是串口设备。通常类似于 " "ttyS0。" #. Tag: para #: boot-installer.xml:2794 #, no-c-format msgid "" "For &arch-title; the serial devices are ttya or " "ttyb. Alternatively, set the input-device and output-device OpenPROM variables to " "ttya." msgstr "" "对于 &arch-title; 串口设备名称是 ttya 或 " "ttyb 。或者,通过设置input-device 和 " "output-device OpenPROM 变量至 ttya。" #. Tag: title #: boot-installer.xml:2805 #, no-c-format msgid "Debian Installer Parameters" msgstr "Debian 安装程序的参数" #. Tag: para #: boot-installer.xml:2806 #, no-c-format msgid "" "The installation system recognizes a few additional boot " "parameters With current kernels (2.6.9 or newer) you can " "use 32 command line options and 32 environment options. If these numbers are " "exceeded, the kernel will panic. which may be useful." msgstr "" "安装系统能识别一些额外的引导参数 当前的内核(2.6.9 或更新)," "您可以使用 32 个命令行参数和 32 个环境变量选项。如果超出,内核将会崩溃。 ,它们很有用。" #. Tag: term #: boot-installer.xml:2823 #, no-c-format msgid "debconf/priority" msgstr "debconf/priority" #. Tag: para #: boot-installer.xml:2824 #, no-c-format msgid "" "This parameter sets the lowest priority of messages to be displayed. Short " "form: priority" msgstr "" "这些参数设置将设置显示的信息为最低的级别。简写: priority" #. Tag: para #: boot-installer.xml:2829 #, 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:2836 #, 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,将显" "示所有的消息(这相当于采用 export 引导方法)。通过 " "priority=critical,安装系统只会显示至关重要的信息,并" "且尝试正确无误地执行各项事宜。" #. Tag: term #: boot-installer.xml:2850 #, no-c-format msgid "DEBIAN_FRONTEND" msgstr "DEBIAN_FRONTEND" #. Tag: para #: boot-installer.xml:2851 #, fuzzy, 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. Generally only the newt frontend is " "available on default install media. On architectures which support it, the " "graphical installer uses the gtk frontend." msgstr "" "这个引导参数控制用于安装程序的用户界面的类型。当前可能参数设置可以是: " " DEBIAN_FRONTEND=noninteractive " "DEBIAN_FRONTEND=text DEBIAN_FRONTEND=newt " " DEBIAN_FRONTEND=slang DEBIAN_FRONTEND=ncurses " "DEBIAN_FRONTEND=bogl DEBIAN_FRONTEND=gtk " " DEBIAN_FRONTEND=corba 缺省的前端是 " "DEBIAN_FRONTEND=newt。" "DEBIAN_FRONTEND=text 可以用于串口控制台的安装。一般来" "说在缺省安装介质上只有 newt 前端,因此目前这个并非很有" "用。" #. Tag: term #: boot-installer.xml:2880 #, no-c-format msgid "BOOT_DEBUG" msgstr "BOOT_DEBUG" #. Tag: para #: boot-installer.xml:2881 #, 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:2890 #, no-c-format msgid "BOOT_DEBUG=0" msgstr "BOOT_DEBUG=0" #. Tag: para #: boot-installer.xml:2891 #, no-c-format msgid "This is the default." msgstr "此为默认。" #. Tag: userinput #: boot-installer.xml:2895 #, no-c-format msgid "BOOT_DEBUG=1" msgstr "BOOT_DEBUG=1" #. Tag: para #: boot-installer.xml:2896 #, no-c-format msgid "More verbose than usual." msgstr "更多的信息。" #. Tag: userinput #: boot-installer.xml:2900 #, no-c-format msgid "BOOT_DEBUG=2" msgstr "BOOT_DEBUG=2" #. Tag: para #: boot-installer.xml:2901 #, no-c-format msgid "Lots of debugging information." msgstr "大量的调试信息。" #. Tag: userinput #: boot-installer.xml:2905 #, no-c-format msgid "BOOT_DEBUG=3" msgstr "BOOT_DEBUG=3" #. Tag: para #: boot-installer.xml:2906 #, no-c-format msgid "" "Shells are run at various points in the boot process to allow detailed " "debugging. Exit the shell to continue the boot." msgstr "" "在引导过程中,安装程序将在多处不同地方运行 Shell,以进行细节上的调试。退出 " "Shell 将继续引导过程。" #. Tag: term #: boot-installer.xml:2920 #, no-c-format msgid "INSTALL_MEDIA_DEV" msgstr "INSTALL_MEDIA_DEV" #. Tag: para #: boot-installer.xml:2921 #, no-c-format msgid "" "The value of the parameter is the path to the device to load the Debian " "installer from. For example, INSTALL_MEDIA_DEV=/dev/floppy/0" msgstr "" "参数的值将为用来装入 Debian 安装程序的设备路径,例如: " "INSTALL_MEDIA_DEV=/dev/floppy/0" #. Tag: para #: boot-installer.xml:2927 #, no-c-format msgid "" "The boot floppy, which normally scans all floppies it can to find the root " "floppy, can be overridden by this parameter to only look at the one device." msgstr "" "引导软盘,它通常会扫描所有的软盘来找到根软盘,可以通过此参数设置只查找一个设" "备。" #. Tag: term #: boot-installer.xml:2937 #, no-c-format msgid "debian-installer/framebuffer" msgstr "debian-installer/framebuffer" #. Tag: para #: boot-installer.xml:2938 #, 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 by the parameter debian-installer/" "framebuffer=false, or fb=false for short. " "Problem symptoms are error messages about bterm or bogl, a blank screen, or " "a freeze within a few minutes after starting the install." msgstr "" "一些体系使用内核帧缓存以提供不同的语言安装。如果帧缓存在您的系统上面有问题," "您可以通过参数 framebuffer=false,简写 " "fb=false 关闭这个特性。这方面问题的特征是有关 bterm 或" "者 bogl 的错误信息,一个空白的屏幕,或者在开始安装几分钟后停止。" #. Tag: para #: boot-installer.xml:2948 #, no-c-format msgid "" "The video=vga16:off argument may also be used to " "disable the kernel's use of the framebuffer. Such problems have been " "reported on a Dell Inspiron with Mobile Radeon card." msgstr "" "video=vga16:off 参数可以被用来取消帧缓存。这些问题在使" "用 Mobile Radeon 卡的 Dell Inspiron 上面被发现。" #. Tag: para #: boot-installer.xml:2954 #, no-c-format msgid "Such problems have been reported on the Amiga 1200 and SE/30." msgstr "在 Amiga 1200 and SE/30 上面报告过具有有这些方面的问题。" #. Tag: para #: boot-installer.xml:2958 #, no-c-format msgid "Such problems have been reported on hppa." msgstr "在 hppa 上面报告过存在这些问题。" #. Tag: para #: boot-installer.xml:2962 #, no-c-format msgid "" "Because of display problems on some systems, framebuffer support is " "disabled by default for &arch-title;. This can result " "in ugly display on systems that do properly support the framebuffer, like " "those with ATI graphical cards. If you see display problems in the " "installer, you can try booting with parameter debian-installer/" "framebuffer=true or fb=true for short." msgstr "" "由于某些系统上显示有问题,framebuffer 的支持在 &arch-title; 上默认" "是禁止的。这让能良好支持 framebuffer 的系统显示得很丑陋,比如那些" "采用 ATI 图形卡的系统。如果您在安装程序中遇到显示问题,可以试着在引导时使用参" "数 debian-installer/framebuffer=true 或简写为 " "fb=true。" #. Tag: term #: boot-installer.xml:2976 #, no-c-format msgid "debian-installer/theme" msgstr "debian-installer/theme" #. Tag: para #: boot-installer.xml:2977 #, no-c-format msgid "" "A theme determines how the user interface of the installer looks (colors, " "icons, etc.). What themes are available differs per frontend. Currently both " "the newt and gtk frontends only have a dark theme that was " "designed for visually impaired users. Set the theme by booting with " "parameter debian-installer/theme=dark or theme=dark." msgstr "" "theme 决定安装程序用户界面的外观(颜色,图标等。)。不同的前端(frontend)有不同" "的 theme。当前 newt 和 gtk 前端只有一个 dark theme 提供给视觉" "受损的用户。them 可以在启动的时候通过 debian-installer/" "theme=dark 或 " "theme=dark 设置。" #. Tag: term #: boot-installer.xml:2990 #, no-c-format msgid "debian-installer/probe/usb" msgstr "debian-installer/probe/usb" #. Tag: para #: boot-installer.xml:2991 #, no-c-format msgid "" "Set to false to prevent probing for USB on boot, if " "that causes problems." msgstr "" "设置成 false 可以阻止在引导的时候进行 USB 探测来杜绝引" "起的问题。" #. Tag: term #: boot-installer.xml:3000 boot-installer.xml:3167 #, no-c-format msgid "netcfg/disable_dhcp" msgstr "netcfg/disable_dhcp" #. Tag: para #: boot-installer.xml:3001 #, no-c-format msgid "" "By default, the &d-i; automatically probes for network configuration via " "DHCP. If the probe succeeds, you won't have a chance to review and change " "the obtained settings. You can get to the manual network setup only in case " "the DHCP probe fails." msgstr "" "缺省情况下,&d-i; 会通过 DHCP 来自动检测网络。如果检测成功的话,您将不需要审" "视并且改变其获得的设定。您可以在 DHCP 检测失败的情况下手工配置网络。" #. Tag: para #: boot-installer.xml:3008 #, no-c-format msgid "" "If you have a DHCP server on your local network, but want to avoid it " "because e.g. it gives wrong answers, you can use the parameter " "netcfg/disable_dhcp=true to prevent configuring the " "network with DHCP and to enter the information manually." msgstr "" "如果您的网络上面具备一台 DHCP 服务器,但是不想使用它,比如,因为它给出错误的" "答案。您可以使用参数 netcfg/disable_dhcp=true 来通过 " "DHCP 来配置网络并且手工输入参数。" #. Tag: term #: boot-installer.xml:3019 #, no-c-format msgid "hw-detect/start_pcmcia" msgstr "hw-detect/start_pcmcia" #. Tag: para #: boot-installer.xml:3020 #, 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:3030 #, no-c-format msgid "preseed/url" msgstr "preseed/url" #. Tag: para #: boot-installer.xml:3031 #, fuzzy, no-c-format msgid "" "Specify the url to a preconfiguration file to download and use in automating " "the install. See . Short form: " "url." msgstr "" "指定 url 到预设文件,在安装中自动下载和使用。参阅 。简写: url。" #. Tag: term #: boot-installer.xml:3041 #, no-c-format msgid "preseed/file" msgstr "preseed/file" #. Tag: para #: boot-installer.xml:3042 #, fuzzy, no-c-format msgid "" "Specify the path to a preconfiguration file to load to automating the " "install. See . Short form: " "file." msgstr "" "指定路径至预设文件,加载自动化安装。参阅 。简写: file" #. Tag: term #: boot-installer.xml:3052 #, no-c-format msgid "auto-install/enabled" msgstr "auto-install/enabled" #. Tag: para #: boot-installer.xml:3053 #, no-c-format msgid "" "Delay questions that are normally asked before preseeding is possible until " "after the network is configured. Short form: auto=true See for details about using this " "to automate installs." msgstr "" "延迟通常在预置之前的提问,到网络设置完毕。简单形式:auto=true 参阅 了解自动安装的详细信息。" #. Tag: term #: boot-installer.xml:3064 #, no-c-format msgid "cdrom-detect/eject" msgstr "cdrom-detect/eject" #. Tag: para #: boot-installer.xml:3065 #, no-c-format msgid "" "By default, before rebooting, &d-i; automatically ejects the optical media " "used during the installation. This can be unnecessary if the system does not " "automatically boot off the CD. In some cases it may even be undesirable, for " "example if the optical drive cannot reinsert the media itself and the user " "is not there to do it manually. Many slot loading, slim-line, and caddy " "style drives cannot reload media automatically." msgstr "" "在重启前,&d-i; 默认自动弹出安装时的光学媒介。如果系统不是自动从 CD 引导,这" "不是必要的操作。在某些情况下,这反而不便,例如,如果光驱不能自动插入盘片,用" "户又不在旁边操作。许多 slot loading, slim-line 和 caddy 类型的驱动器不能自动" "重新加载介质。" #. Tag: para #: boot-installer.xml:3074 #, 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:3085 #, no-c-format msgid "ramdisk_size" msgstr "ramdisk_size" #. Tag: para #: boot-installer.xml:3086 #, no-c-format msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;." msgstr "如果您在使用 2.2.x 内核,也许需要设置 &ramdisksize;。" #. Tag: term #: boot-installer.xml:3094 #, no-c-format msgid "mouse/left" msgstr "mouse/left" #. Tag: para #: boot-installer.xml:3095 #, no-c-format msgid "" "For the gtk frontend (graphical installer), users can switch the mouse to " "left-handed operation by setting this parameter to true." msgstr "" "对于 gtk 前端(图形界面安装程序),用户可以通过将此参数设置为 true 切换成左手使用鼠标。" #. Tag: term #: boot-installer.xml:3104 #, no-c-format msgid "directfb/hw-accel" msgstr "directfb/hw-accel" #. Tag: para #: boot-installer.xml:3105 #, no-c-format msgid "" "For the gtk frontend (graphical installer), hardware acceleration in " "directfb is disabled by default. To enable it, set this parameter to " "true when booting the installer." msgstr "" "对于 gtk 前端(图形界面安装程序),默认时 directfb 的图形加速关闭。要打开它,可" "以在启动安装程序的时候设置参数为 true。" #. Tag: term #: boot-installer.xml:3115 #, no-c-format msgid "rescue/enable" msgstr "rescue/enable" #. Tag: para #: boot-installer.xml:3116 #, no-c-format msgid "" "Set to true to enter rescue mode rather than " "performing a normal installation. See ." msgstr "" "设为 true 进入 rescue 模式,而不是执行普通安装。参阅 " "。" #. Tag: title #: boot-installer.xml:3127 #, fuzzy, no-c-format msgid "Using boot parameters to answer questions" msgstr "给内核模块传递参数" #. Tag: para #: boot-installer.xml:3128 #, 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:3140 #, fuzzy, no-c-format msgid "debian-installer/locale" msgstr "debian-installer/theme" #. Tag: para #: boot-installer.xml:3141 #, no-c-format msgid "" "Can be used to set both the language and country for the installation. This " "will only work if the locale is supported in Debian. Short form: " "locale. For example, use locale=de_CH to select German as language and Switzerland as country." msgstr "" #. Tag: term #: boot-installer.xml:3153 #, no-c-format msgid "anna/choose_modules" msgstr "" #. Tag: para #: boot-installer.xml:3154 #, no-c-format msgid "" "Can be used to automatically load installer components that are not loaded " "by default. Short form: modules. Examples of optional " "components that may be useful are openssh-client-udeb " "(so you can use scp during the installation) and " "ppp-udeb (which supports PPPoE configuration)." msgstr "" #. Tag: para #: boot-installer.xml:3168 #, no-c-format msgid "" "Set to true if you want to disable DHCP and instead " "force static network configuration." msgstr "" #. Tag: term #: boot-installer.xml:3177 #, no-c-format msgid "tasksel:tasksel/first" msgstr "" #. Tag: para #: boot-installer.xml:3178 #, 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. Short form: tasks." msgstr "" #. Tag: title #: boot-installer.xml:3192 #, no-c-format msgid "Passing parameters to kernel modules" msgstr "给内核模块传递参数" #. Tag: para #: boot-installer.xml:3193 #, 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:3206 #, 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:3213 #, no-c-format msgid "" "The syntax to use to set parameters for modules is: " "\n" "module_name.parameter_name=value\n" " If you need to pass multiple parameters to the " "same or different modules, just repeat this. For example, to set an old 3Com " "network interface card to use the BNC (coax) connector and IRQ 10, you would " "pass:" msgstr "" "设置模块参数的语法为:\n" "module_name.parameter_name=value\n" " 如果您需要传递多个参数给相同或不同的模块,重复上" "面内容即可。例如,设置老式的 3Com 网卡要使用 BNC (coax) 端子和 IRQ 10,要使" "用:" #. Tag: screen #: boot-installer.xml:3223 #, no-c-format msgid "3c509.xcvr=3 3c509.irq=10" msgstr "3c509.xcvr=3 3c509.irq=10" #. Tag: title #: boot-installer.xml:3235 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "安装过程中的故障修复" #. Tag: title #: boot-installer.xml:3240 #, no-c-format msgid "CD-ROM Reliability" msgstr "CD-ROM 的可靠性" #. Tag: para #: boot-installer.xml:3241 #, no-c-format msgid "" "Sometimes, especially with older CD-ROM drives, the installer may fail to " "boot from a CD-ROM. The installer may also — even after booting " "successfully from CD-ROM — fail to recognize the CD-ROM or return " "errors while reading from it during the installation." msgstr "" "有时,特别是旧的 CD-ROM 驱动器,安装将无法从 CD-ROM 引导。安装程序可能 " "— 即使是从 CD-ROM 成功引导 — 无法识别 CD-ROM 或在安装时读取错误。" #. Tag: para #: boot-installer.xml:3248 #, no-c-format msgid "" "There are a 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:3254 #, no-c-format msgid "There are two very simple things that you should try first." msgstr "您首先应试试两种最简单的方法。" #. Tag: para #: boot-installer.xml:3259 #, no-c-format msgid "" "If the CD-ROM does not boot, check that it was inserted correctly and that " "it is not dirty." msgstr "如果 CD-ROM 没有引导,检查一下它是否放好,并且没有弄脏。" #. Tag: para #: boot-installer.xml:3265 #, no-c-format msgid "" "If the installer fails to recognize a CD-ROM, try just running the option " " Detect and mount CD-ROM a second time. Some DMA related issues with older CD-ROM drives " "are known to be resolved in this way." msgstr "" "如果安装程序无法识别 CD-ROM,再次运行 Detect and " "mount CD-ROM 选项。有些旧 CD-ROM 驱动器 DMA 相关" "的问题可以用这种方法解决。" #. Tag: para #: boot-installer.xml:3275 #, no-c-format msgid "" "If this does not work, then try the suggestions in the subsections below. " "Most, but not all, suggestions discussed there are valid for both CD-ROM and " "DVD, but we'll use the term CD-ROM for simplicity." msgstr "" "如果还无法工作,试试下一节建议的方法。多数情况下,但非全部,那里的建议适用于 " "CD-ROM 和 DVD,为了简单,只说了 CD-ROM。" #. Tag: para #: boot-installer.xml:3281 #, no-c-format msgid "" "If you cannot get the installation working from CD-ROM, try one of the other " "installation methods that are available." msgstr "如果您用 CD-ROM 无法安装,试试其他可用的安装方法。" #. Tag: title #: boot-installer.xml:3289 #, no-c-format msgid "Common issues" msgstr "常见问题" #. Tag: para #: boot-installer.xml:3292 #, 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:3298 #, no-c-format msgid "" "If your system boots correctly from the CD-ROM, it does not necessarily mean " "that Linux also supports the CD-ROM (or, more correctly, the controller that " "your CD-ROM drive is connected to)." msgstr "" "如果您的系统可以从 CD-ROM 引导,这并不是说 Linux 就能支持该 CD-ROM (或者,更" "准确一点,CD-ROM 驱动器所连接的控制器)。" #. Tag: para #: boot-installer.xml:3305 #, no-c-format msgid "" "Some older CD-ROM drives do not work correctly if direct memory " "access (DMA) is enabled." msgstr "" "一些老式的 CD-ROM 驱动器在 direct memory access (DMA) 下无法正" "常工作。" #. Tag: title #: boot-installer.xml:3316 #, no-c-format msgid "How to investigate and maybe solve issues" msgstr "如何调查研究或许可以解决问题" #. Tag: para #: boot-installer.xml:3317 #, no-c-format msgid "If the CD-ROM fails to boot, try the suggestions listed below." msgstr "如果从 CD-ROM 引导失败,试试下面所列的建议。" #. Tag: para #: boot-installer.xml:3322 #, no-c-format msgid "" "Check that your BIOS actually supports booting from CD-ROM (older systems " "possibly don't) and that your CD-ROM drive supports the media you are using." msgstr "" "检查您的 BIOS 的确支持从 CD-ROM 启动(旧的系统可能不行),并且 CD-ROM 驱动器支" "持您所使用的介质。" #. Tag: para #: boot-installer.xml:3328 #, no-c-format msgid "" "If you downloaded an iso image, check that the md5sum of that image matches " "the one listed for the image in the MD5SUMS file that " "should be present in the same location as where you downloaded the image " "from. \n" "$ md5sum debian-testing-i386-netinst.iso\n" "a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst." "iso\n" " Next, check that the md5sum of the burned CD-ROM " "matches as well. The following command should work. It uses the size of the " "image to read the correct number of bytes from the CD-ROM." msgstr "" "如果您下载的是 iso 映像,检查映像的 md5sum 是否与 MD5SUMS 文件所列相同,该文件和您下载的映像在同一个地方。" "\n" "$ md5sum debian-testing-i386-netinst.iso\n" "a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst." "iso\n" " 然后,检验所刻录 CD-ROM 的 md5sum 也匹配。可以使" "用下面的命令。它使用映像的尺寸从 CD-ROM 读取正确的字节数。" #. Tag: screen #: boot-installer.xml:3341 #, 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:3346 #, no-c-format msgid "" "If, after the installer has been booted successfully, the CD-ROM is not " "detected, sometimes simply trying again may solve the problem. If you have " "more than one CD-ROM drive, try changing the CD-ROM to the other drive. If " "that does not work or if the CD-ROM is recognized but there are errors when " "reading from it, try the suggestions listed below. Some basic knowledge of " "Linux is required for this. To execute any of the commands, you should first " "switch to the second virtual console (VT2) and activate the shell there." msgstr "" "假如在安装程序正常的引导之后,无法识别 CD-ROM,有时只需再试一次就能解决问题。" "如果您有多个 CD-ROM 驱动器,将 CD-ROM 放到其他的驱动器。如果无法工作,或者可" "以识别 CD-ROM 但读取的时候有错误,试试下面所列的建议。这里需要一些基本的 " "Linux 知识。要执行命令,您应该首先切换到第二虚拟控制台(VT2),并激活 shell。" #. Tag: para #: boot-installer.xml:3358 #, 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:3365 #, fuzzy, no-c-format msgid "" "Check in the output of dmesg if your CD-ROM drive was " "recognized. You should see something like (the lines do not necessarily have " "to be consecutive): \n" "Probing IDE interface ide1...\n" "hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" "ide1 at 0x170-0x177,0x376 on irq 15\n" "hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" "Uniform CD-ROM driver Revision: 3.20\n" " If you don't see something like that, chances " "are the controller your CD-ROM is connected to was not recognized or may be " "not supported at all. If you know what driver is needed for the controller, " "you can try loading it manually using modprobe." msgstr "" "如果您的 CD-ROM 驱动器可以识别,检查 dmesg 的输出。您可以" "看到类似的信息(这些行不必是连续出现的):\n" "Probing IDE interface ide1...\n" "hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" "ide1 at 0x170-0x177,0x376 on irq 15\n" "hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" "Uniform CD-ROM driver Revision: 3.20\n" " 如果您看不到这些,估计是您的 CD-ROM 驱动器所连的" "控制器无法被识别,或者不完全支持。如果您知道驱动器所需的驱动程序,可以使用 " "modprobe 手动加载。" #. Tag: para #: boot-installer.xml:3379 #, no-c-format msgid "" "Check that there is a device node for your CD-ROM drive under /dev/" ". In the example above, this would be /dev/hdc. There should also be a /dev/cdroms/cdrom0." msgstr "" "检查 /dev/ 下面您 CD-ROM 驱动器对应的设备节点。上面的例" "子中,它是 /dev/hdc。也会是 /dev/cdroms/" "cdrom0。" #. Tag: para #: boot-installer.xml:3387 #, no-c-format msgid "" "Use the mount command to check if the CD-ROM is already " "mounted; if not, try mounting it manually: \n" "$ mount /dev/hdc /cdrom\n" " Check if there are any error messages after that " "command." msgstr "" "用 mount 命令检查 the CD-ROM 是否已经挂载;如果没有,使用" "手动挂载:\n" "$ mount /dev/hdc /cdrom\n" " 检查命令后面是否有什么错误信息。" #. Tag: para #: boot-installer.xml:3397 #, fuzzy, no-c-format msgid "" "Check if DMA is currently enabled: \n" "$ cd /proc/ide/hdc\n" "$ grep using_dma settings\n" "using_dma 1 0 1 rw\n" " A 1 in the first column after " "using_dma means it is enabled. If it is, try disabling " "it: \n" "$ echo -n \"using_dma:0\" >settings\n" " Make sure that you are in the directory for the " "device that corresponds to your CD-ROM drive." msgstr "" "简单当前 DMA 已经打开:\n" "$ cd /proc/ide/hdc\n" "$ grep dma settings\n" "using_dma 1 0 1 rw\n" " 1 意味着打开。如果是这样,将其关" "闭:\n" "$ echo -n \"using_dma:0\" >settings\n" " 确保您所处的目录对应 CD-ROM 驱动器。" #. Tag: para #: boot-installer.xml:3412 #, no-c-format msgid "" "If there are any problems during the installation, try checking the " "integrity of the CD-ROM using the option near the bottom of the installer's " "main menu. This option can also be used as a general test if the CD-ROM can " "be read reliably." msgstr "" "如果安装过程中有什么问题,用接近安装程序主菜单底部的选项检查 CD-ROM 的完整" "性。如果 CD-ROM 可以读,该选项可以对其进行测试。" #. Tag: title #: boot-installer.xml:3427 #, no-c-format msgid "Floppy Disk Reliability" msgstr "软盘的可靠性" #. Tag: para #: boot-installer.xml:3429 #, no-c-format msgid "" "The biggest problem for people using floppy disks to install Debian seems to " "be floppy disk reliability." msgstr "" "对于用软盘安装 Debian 的人来说,他们遇到的最大的问题很可能是软盘的可靠性。" #. Tag: para #: boot-installer.xml:3434 #, no-c-format msgid "" "The boot floppy is the floppy with the worst problems, because it is read by " "the hardware directly, before Linux boots. Often, the hardware doesn't read " "as reliably as the Linux floppy disk driver, and may just stop without " "printing an error message if it reads incorrect data. There can also be " "failures in the driver floppies, most of which indicate themselves with a " "flood of messages about disk I/O errors." msgstr "" "因为引导软盘是在 Linux 引导之前由硬件直接读取,是问题最多的软盘。通常,硬件的" "读取并不能像 Linux 软盘驱动那样可靠,并且对读到错误的数据,它们只会停止运行," "连条错误消息也不会显示。驱动软盘也会出错,很多时候只是打印出一堆 I/O 错误信" "息。" #. Tag: para #: boot-installer.xml:3443 #, no-c-format msgid "" "If you are having the installation stall at a particular floppy, the first " "thing you should do is write the image to a different " "floppy and see if that solves the problem. Simply reformatting the old " "floppy may not be sufficient, even if it appears that the floppy was " "reformatted and written with no errors. It is sometimes useful to try " "writing the floppy on a different system." msgstr "" "如果在某个软盘上遇到安装停止,您首先要做的,是把映像重新写到另外一张软盘上,看看是否解决问题。仅格式化旧软盘是不够的,即使它重新格式" "化以后看起来没有错误。如果可能,在别的统上重写这些软盘更好一些。" #. Tag: para #: boot-installer.xml:3452 #, no-c-format msgid "" "One user reports he had to write the images to floppy three times before one worked, and then everything was fine with the " "third floppy." msgstr "" "一个用户报告过他不得不把映像往软盘写次,只有最后一次的" "软盘才算工作良好。" #. Tag: para #: boot-installer.xml:3458 #, no-c-format msgid "" "Normally you should not have to download a floppy image again, but if you " "are experiencing problems it is always useful to verify that the images were " "downloaded correctly by verifying their md5sums." msgstr "" "一般情况下,您不必重新下载软盘映像,但如果一直有问题,可以通过它们的 md5sum " "来检验下载的映像是否正确。" #. Tag: para #: boot-installer.xml:3464 #, no-c-format msgid "" "Other users have reported that simply rebooting a few times with the same " "floppy in the floppy drive can lead to a successful boot. This is all due to " "buggy hardware or firmware floppy drivers." msgstr "" "其他一些用户报告过,用同样的软盘重新启动若干次才有一次能成功引导。这都是由于" "有缺陷的硬件或固件软盘驱动器驱动程序造成的。" #. Tag: title #: boot-installer.xml:3473 #, no-c-format msgid "Boot Configuration" msgstr "引导配置" #. Tag: para #: boot-installer.xml:3475 #, 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:3482 #, no-c-format msgid "" "If you are booting with your own kernel instead of the one supplied with the " "installer, be sure that CONFIG_DEVFS is set in your " "kernel. The installer requires CONFIG_DEVFS." msgstr "" "如果引导的是您自己的内核,而不是安装程序提供的内核,请确定 " "CONFIG_DEVFS 已被设置到内核。安装程序需要 " "CONFIG_DEVFS。" #. Tag: para #: boot-installer.xml:3489 #, no-c-format msgid "" "Often, problems can be solved by removing add-ons and peripherals, and then " "trying booting again. Internal modems, sound cards, and " "Plug-n-Play devices can be especially problematic." msgstr "" "通常,可以通过移除外挂硬件或者外围设备来解决问题,然后再次重新引导。内置调制解调器、声卡以及即插即用设备特别容易引起问题。" #. Tag: para #: boot-installer.xml:3495 #, no-c-format msgid "" "If you have a large amount of memory installed in your machine, more than " "512M, and the installer hangs when booting the kernel, you may need to " "include a boot argument to limit the amount of memory the kernel sees, such " "as mem=512m." msgstr "" "如果您的机器上装有多于 512M 的大容量的内存,并且安装程序在引导内核时停止,您" "可能需要加入一个引导参数,来限制内核能够看到的内存数量,比如 " "mem=512m。" #. Tag: title #: boot-installer.xml:3506 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "&arch-title; 常见安装问题" #. Tag: para #: boot-installer.xml:3507 #, 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:3512 #, no-c-format msgid "" "Some systems have floppies with inverted DCLs. If you receive " "errors reading from the floppy, even when you know the floppy is good, try " "the parameter floppy=thinkpad." msgstr "" "一些系统的软盘会有 inverted DCLs。如果您在读软盘时遇到错误信" "息,并且知道软盘是好的,请尝试 floppy=thinkpad 参数。" #. Tag: para #: boot-installer.xml:3518 #, no-c-format msgid "" "On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk " "drivers), the IDE drive may not be properly recognized. Again, try it first " "without the parameters and see if the IDE drive is recognized properly. If " "not, determine your drive geometry (cylinders, heads, and sectors), and use " "the parameter hd=cylinders," "heads,sectors." msgstr "" "在一些系统上,比如 IBM PS/1 或者 ValuePoint (具有 ST-506 驱动器),IDE 驱动器" "可能不被识别。请首先尝试没有参数的的引导是否能够被识别。如果不行,请确定驱动" "器几何参数(柱面,磁头还有扇区)。然后使用参数 " "hd=cylinders,heads,sectors。" #. Tag: para #: boot-installer.xml:3527 #, no-c-format msgid "" "If you have a very old machine, and the kernel hangs after saying " "Checking 'hlt' instruction..., then you " "should try the no-hlt boot argument, which disables " "this test." msgstr "" "如果您有一台非常老的机器,并且内核在显示 Checking 'hlt' " "instruction... 时中断,需要尝试 no-hlt 参数来取消这个测试。" #. Tag: para #: boot-installer.xml:3534 #, 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 " "video=vga16:off to disable the framebuffer console. Only the " "English language will be available during the installation due to limited " "console features. See for details." msgstr "" "如果您的显示屏在内核引导的时候显示一个奇怪的图片(比如,纯白,纯黑或者彩色的像" "素块),系统可能含有一块有问题的显示卡。它不能切换至帧缓存模式。您可以使用引导" "参数 fb=falsevideo=vga16:off 来取消帧缓存控制台。在这种情况下,由于控制台的限制,在安装过程中只" "能用英语,请参见 来获得细节信息。" #. Tag: title #: boot-installer.xml:3548 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "在 PCMCIA 配置阶段系统停止" #. Tag: para #: boot-installer.xml:3549 #, no-c-format msgid "" "Some laptop models produced by Dell are known to crash when PCMCIA device " "detection tries to access some hardware addresses. Other laptops may display " "similar problems. If you experience such a problem and you don't need PCMCIA " "support during the installation, you can disable PCMCIA using the " "hw-detect/start_pcmcia=false boot parameter. You can " "then configure PCMCIA after the installation is completed and exclude the " "resource range causing the problems." msgstr "" "Dell 笔记本的一些型号,会在 PCMCIA 设备检测程序尝试访问一些硬件地址的时候死" "机。其他笔记本可能显示类似的问题。如果您遇到那样的问题,并且在安装的时候不需" "要 PCMCIA 的支持,可以用 hw-detect/start_pcmcia=false " "启动参数来取消 PCMCIA 功能。您可以在安装后配置 PCMCIA,去掉造成问题的资源区" "段。" #. Tag: para #: boot-installer.xml:3559 #, 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 "" "或者,您可以启动安装程序时进入高级模式。您需要按照要求输入硬件资源范围选项。" "比如,您如果有如上所说的 Dell 笔记本问题,应该在这里输入 exclude " "port 0x800-0x8ff。在 System resource settings section of " "the PCMCIA HOWTO 处有一个列表,列出了一些问题的资源范围选项。注意在安" "装程序中,输入这些值的时候必须忽略逗号。" #. Tag: title #: boot-installer.xml:3576 #, no-c-format msgid "System Freeze while Loading the USB Modules" msgstr "在装入 USB 模块时系统停止" #. Tag: para #: boot-installer.xml:3577 #, no-c-format msgid "" "The kernel normally tries to install USB modules and the USB keyboard driver " "in order to support some non-standard USB keyboards. However, there are some " "broken USB systems where the driver hangs on loading. A possible workaround " "may be disabling the USB controller in your mainboard BIOS setup. Another " "option is passing the debian-installer/probe/usb=false parameter at the boot prompt, which will prevent the modules from " "being loaded." msgstr "" "内核正常情况下会尝试安装 USB 模块以及 USB 键盘驱动来支持一些非标准的 USB 键" "盘。但是,有些不完整的 USB 系统会在驱动程序装入时死机。一个可能的解决方法是" "在 BIOS 设置内禁止您的 USB 控制器。或者在引导提示符处传递 debian-" "installer/probe/usb=false 参数,这将阻止装入此模块。" #. Tag: title #: boot-installer.xml:3591 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "内核起始信息注解" #. Tag: para #: boot-installer.xml:3593 #, no-c-format msgid "" "During the boot sequence, you may see many messages in the form " "can't find something , or something " "not present, can't initialize " "something , or even " "this driver release depends on something . Most of these messages are harmless. You see " "them because the kernel for the installation system is built to run on " "computers with many different peripheral devices. Obviously, no one computer " "will have every possible peripheral device, so the operating system may emit " "a few complaints while it looks for peripherals you don't own. You may also " "see the system pause for a while. This happens when it is waiting for a " "device to respond, and that device is not present on your system. If you " "find the time it takes to boot the system unacceptably long, you can create " "a custom kernel later (see )." msgstr "" "在引导期间,您可以看到很多信息类似 can't find " "something ,或者 " " something not presentcan't initialize something ,或者甚至 this driver release " "depends on something 。大多数这些" "信息都是无害的。您之所以看到它们,是因为安装系统内核被设计成为可以运行在不同" "的计算机,并且拥有不同的外围设备。显然地,没有一个计算机可能拥有所有的外围设" "备,因此操作系统可能在查找一些您没有的设备上有一些报怨。有时可以看到系统暂停" "了一段时间。这是由于它在等待一台设备的回应,但是这台设备并没有安装在您的系统" "上。如果您发现这个时间非常长,您可以一会创建一个自己的内核(参见 )。" #. Tag: title #: boot-installer.xml:3618 #, fuzzy, no-c-format msgid "Reporting Installation Problems" msgstr "&arch-title; 常见安装问题" #. Tag: para #: boot-installer.xml:3619 #, fuzzy, no-c-format msgid "" "If you get through the initial boot phase but cannot complete the install, " "the menu option Save debug logs may be helpful. " "It lets you store system error logs and configuration information from the " "installer to a floppy, or download them using a web browser. This " "information may provide clues as to what went wrong and how to fix it. If " "you are submitting a bug report you may want to attach this information to " "the bug report." msgstr "" "如果您过了初始化引导阶段,但还是不能安装,可以借助于 bug 报告菜单选项。它让您" "保存安装程序的系统错误记录和配置信息到软盘,或者用网络浏览器下载。该信息或许" "可以提供了一些关于错误的起因和如何解决它的线索。如果您正在提交一个 bug 报告," "可以报告里附上该信息。" #. Tag: para #: boot-installer.xml:3630 #, 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:3641 #, no-c-format msgid "Submitting Installation Reports" msgstr "提交缺陷报告" #. Tag: para #: boot-installer.xml:3642 #, no-c-format msgid "" "If you still have problems, please submit an installation report. We also " "encourage installation reports to be sent even if the installation is " "successful, so that we can get as much information as possible on the " "largest number of hardware configurations." msgstr "" "如果仍有问题,请提交安装报告。即使已经安装成功,我们也鼓励您发一份安装报告," "这让我们可以尽可能多地了解硬件的配置数量。" #. Tag: para #: boot-installer.xml:3649 #, no-c-format msgid "" "Note that your installation report will be published in the Debian Bug " "Tracking System (BTS) and forwarded to a public mailing list. Make sure that " "you use an E-Mail address that you do not mind being made public." msgstr "" #. Tag: para #: boot-installer.xml:3655 #, 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-get install installation-report reportbug) and run " "the command reportbug installation-report." msgstr "" "如果您有一个可以运转的 Debian 系统,发送安装报告最简单的方法是安装 " "installation-report 和 reportbug 软件包(apt-get install " "installation-report reportbug),然后执行 reportbug " "installation-report 命令。" #. Tag: para #: boot-installer.xml:3662 #, fuzzy, no-c-format msgid "" "Alternatively you can use this template when filling out installation " "reports, and file the report as a bug report against the " "installation-reports pseudo package, by sending it to " "submit@bugs.debian.org. \n" "Package: installation-reports\n" "\n" "Boot method: <How did you boot the installer? CD? floppy? network?>\n" "Image version: <Full URL to image you downloaded is best>\n" "Date: <Date and time of the install>\n" "\n" "Machine: <Description of machine (eg, IBM Thinkpad R32)>\n" "Processor:\n" "Memory:\n" "Partitions: <df -Tl will do; the raw partition table is preferred>\n" "\n" "Output of lspci -nn and lspci -vnn:\n" "\n" "Base System Installation Checklist:\n" "[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n" "\n" "Initial boot: [ ]\n" "Detect network card: [ ]\n" "Configure network: [ ]\n" "Detect CD: [ ]\n" "Load installer modules: [ ]\n" "Detect hard drives: [ ]\n" "Partition hard drives: [ ]\n" "Install base system: [ ]\n" "Clock/timezone setup: [ ]\n" "User/password setup: [ ]\n" "Install tasks: [ ]\n" "Install boot loader: [ ]\n" "Overall install: [ ]\n" "\n" "Comments/Problems:\n" "\n" "<Description of the install, in prose, and any thoughts, comments\n" " and ideas you had during the initial install.>\n" " In the bug report, describe what the problem is, " "including the last visible kernel messages in the event of a kernel hang. " "Describe the steps that you did which brought the system into the problem " "state." msgstr "" "请采用下列模板填写安装报告,并发邮件到 submit@bugs.debian.org " "给 installation-reports 虚拟软件包发送 bug 报告。" "\n" "Package: installation-reports\n" "\n" "Boot method: <How did you boot the installer? CD? floppy? network?>\n" "Image version: <Full URL to image you downloaded is best>\n" "Date: <Date and time of the install>\n" "\n" "Machine: <Description of machine (eg, IBM Thinkpad R32)>\n" "Processor:\n" "Memory:\n" "Partitions: <df -Tl will do; the raw partition table is preferred>\n" "\n" "Output of lspci -nn and lspci -vnn:\n" "\n" "Base System Installation Checklist:\n" "[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n" "\n" "Initial boot: [ ]\n" "Detect network card: [ ]\n" "Configure network: [ ]\n" "Detect CD: [ ]\n" "Load installer modules: [ ]\n" "Detect hard drives: [ ]\n" "Partition hard drives: [ ]\n" "Install base system: [ ]\n" "Clock/timezone setup: [ ]\n" "User/password setup: [ ]\n" "Install tasks: [ ]\n" "Install boot loader: [ ]\n" "Overall install: [ ]\n" "\n" "Comments/Problems:\n" "\n" "<Description of the install, in prose, and any thoughts, comments\n" " and ideas you had during the initial install.>\n" " 在 bug 报告内,请说明问题所在,包括内核挂起后最后" "见到的内核消息。描述进入问题状态所进行的步骤。" #~ msgid "Bug Reporter" #~ msgstr "Bug Reporter" #~ msgid "" #~ "Proceed to the next chapter to continue the installation where you will " #~ "set up the language locale, network, and the disk partitions." #~ msgstr "下一章将继续安装过程,在那里您将设置语言区域,网络以及磁盘分区。"