po/pt/boot-installer.po

# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR Free Software Foundation, Inc.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2001-02-09 01:25+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: ENCODING\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 ""

#. Tag: title
#: boot-installer.xml:20
#, no-c-format
msgid "Alpha Console Firmware"
msgstr ""

#. 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 ""

#. Tag: para
#: boot-installer.xml:31
#, no-c-format
msgid ""
"<emphasis>SRM console</emphasis>, based on the Alpha Console Subsystem "
"specification, which provides an operating environment for OpenVMS, Tru64 "
"UNIX, and Linux operating systems."
msgstr ""

#. Tag: para
#: boot-installer.xml:38
#, no-c-format
msgid ""
"<emphasis>ARC, AlphaBIOS, or ARCSBIOS console</emphasis>, based on the "
"Advanced RISC Computing (ARC) specification, which provides an operating "
"environment for Windows NT."
msgstr ""

#. 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 ""

#. Tag: para
#: boot-installer.xml:54
#, no-c-format
msgid ""
"ARC requires that you use an MS-DOS partition table (as created by "
"<command>cfdisk</command>) for the boot disk. Therefore MS-DOS partition "
"tables are the ``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 ""

#. Tag: para
#: boot-installer.xml:63
#, no-c-format
msgid ""
"Conversely, SRM is <emphasis>incompatible</emphasis> with MS-DOS partition "
"tables. <footnote><para>Specifically, the bootsector format required by the "
"Console Subsystem Specification conflicts with the placement of the DOS "
"partition table.</para></footnote> Since Tru64 Unix uses the BSD disklabel "
"format, this is the ``native'' partition format for SRM installations."
msgstr ""

#. Tag: para
#: boot-installer.xml:71
#, 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 ""

#. Tag: para
#: boot-installer.xml:82
#, no-c-format
msgid ""
"Because <command>MILO</command> is not available for any of the Alpha "
"systems currently in production (as of February 2000), and because it is no "
"longer necessary to buy an OpenVMS or Tru64 Unix license to have SRM "
"firmware on your older Alpha, it is recommended that you use SRM when "
"possible."
msgstr ""

#. Tag: para
#: boot-installer.xml:90
#, no-c-format
msgid ""
"The following table summarizes available and supported system type/console "
"combinations (see <xref linkend=\"alpha-cpus\"/> for the system type names). "
"The word `ARC' below denotes any of the ARC-compliant consoles."
msgstr ""

#. Tag: entry
#: boot-installer.xml:102
#, no-c-format
msgid "System Type"
msgstr ""

#. Tag: entry
#: boot-installer.xml:103
#, no-c-format
msgid "Console Type Supported"
msgstr ""

#. Tag: entry
#: boot-installer.xml:109
#, no-c-format
msgid "alcor"
msgstr ""

#. Tag: entry
#: boot-installer.xml:110 boot-installer.xml:113 boot-installer.xml:119
#: boot-installer.xml:125 boot-installer.xml:128 boot-installer.xml:131
#: boot-installer.xml:134 boot-installer.xml:140 boot-installer.xml:143
#: boot-installer.xml:146 boot-installer.xml:155 boot-installer.xml:164
#: boot-installer.xml:179 boot-installer.xml:182
#, no-c-format
msgid "ARC or SRM"
msgstr ""

#. Tag: entry
#: boot-installer.xml:112
#, no-c-format
msgid "avanti"
msgstr ""

#. Tag: entry
#: boot-installer.xml:115
#, no-c-format
msgid "book1"
msgstr ""

#. Tag: entry
#: boot-installer.xml:116 boot-installer.xml:122 boot-installer.xml:137
#: boot-installer.xml:149 boot-installer.xml:158 boot-installer.xml:161
#: boot-installer.xml:167 boot-installer.xml:173 boot-installer.xml:176
#, no-c-format
msgid "SRM only"
msgstr ""

#. Tag: entry
#: boot-installer.xml:118
#, no-c-format
msgid "cabriolet"
msgstr ""

#. Tag: entry
#: boot-installer.xml:121
#, no-c-format
msgid "dp264"
msgstr ""

#. Tag: entry
#: boot-installer.xml:124
#, no-c-format
msgid "eb164"
msgstr ""

#. Tag: entry
#: boot-installer.xml:127
#, no-c-format
msgid "eb64p"
msgstr ""

#. Tag: entry
#: boot-installer.xml:130
#, no-c-format
msgid "eb66"
msgstr ""

#. Tag: entry
#: boot-installer.xml:133
#, no-c-format
msgid "eb66p"
msgstr ""

#. Tag: entry
#: boot-installer.xml:136
#, no-c-format
msgid "jensen"
msgstr ""

#. Tag: entry
#: boot-installer.xml:139
#, no-c-format
msgid "lx164"
msgstr ""

#. Tag: entry
#: boot-installer.xml:142
#, no-c-format
msgid "miata"
msgstr ""

#. Tag: entry
#: boot-installer.xml:145
#, no-c-format
msgid "mikasa"
msgstr ""

#. Tag: entry
#: boot-installer.xml:148
#, no-c-format
msgid "mikasa-p"
msgstr ""

#. Tag: entry
#: boot-installer.xml:151
#, no-c-format
msgid "nautilus"
msgstr ""

#. Tag: entry
#: boot-installer.xml:152
#, no-c-format
msgid "ARC (see motherboard manual) or SRM"
msgstr ""

#. Tag: entry
#: boot-installer.xml:154
#, no-c-format
msgid "noname"
msgstr ""

#. Tag: entry
#: boot-installer.xml:157
#, no-c-format
msgid "noritake"
msgstr ""

#. Tag: entry
#: boot-installer.xml:160
#, no-c-format
msgid "noritake-p"
msgstr ""

#. Tag: entry
#: boot-installer.xml:163
#, no-c-format
msgid "pc164"
msgstr ""

#. Tag: entry
#: boot-installer.xml:166
#, no-c-format
msgid "rawhide"
msgstr ""

#. Tag: entry
#: boot-installer.xml:169
#, no-c-format
msgid "ruffian"
msgstr ""

#. Tag: entry
#: boot-installer.xml:170 boot-installer.xml:185 boot-installer.xml:188
#, no-c-format
msgid "ARC only"
msgstr ""

#. Tag: entry
#: boot-installer.xml:172
#, no-c-format
msgid "sable"
msgstr ""

#. Tag: entry
#: boot-installer.xml:175
#, no-c-format
msgid "sable-g"
msgstr ""

#. Tag: entry
#: boot-installer.xml:178
#, no-c-format
msgid "sx164"
msgstr ""

#. Tag: entry
#: boot-installer.xml:181
#, no-c-format
msgid "takara"
msgstr ""

#. Tag: entry
#: boot-installer.xml:184
#, no-c-format
msgid "<entry>xl</entry>"
msgstr ""

#. Tag: entry
#: boot-installer.xml:187
#, no-c-format
msgid "<entry>xlt</entry>"
msgstr ""

#. Tag: para
#: boot-installer.xml:195
#, 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, "
"<command>aboot</command>, a small, platform-independent bootloader, is used. "
"See the (unfortunately outdated) <ulink url=\"&url-srm-howto;\">SRM HOWTO</"
"ulink> for more information on <command>aboot</command>."
msgstr ""

#. Tag: para
#: boot-installer.xml:204
#, 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 ""

#. Tag: para
#: boot-installer.xml:210
#, 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: <command>MILO</command> and <command>aboot</command>."
msgstr ""

#. Tag: para
#: boot-installer.xml:216
#, no-c-format
msgid ""
"<command>MILO</command> is itself a console, which replaces ARC or SRM in "
"memory. <command>MILO</command> can be booted from both ARC and SRM and is "
"the only way to bootstrap Linux from the ARC console. <command>MILO</"
"command> is platform-specific (a different <command>MILO</command> is needed "
"for each system type) and exist only for those systems, for which ARC "
"support is shown in the table above. See also the (unfortunately outdated) "
"<ulink url=\"&url-milo-howto;\">MILO HOWTO</ulink>."
msgstr ""

#. Tag: para
#: boot-installer.xml:227
#, no-c-format
msgid ""
"<command>aboot</command> is a small, platform-independent bootloader, which "
"runs from SRM only. See the (also unfortunately outdated) <ulink url=\"&url-"
"srm-howto;\">SRM HOWTO</ulink> for more information on <command>aboot</"
"command>."
msgstr ""

#. Tag: para
#: boot-installer.xml:234
#, no-c-format
msgid ""
"Thus, three scenarios are generally possible, depending on the system's "
"console firmware and whether or not <command>MILO</command> is available: "
"<informalexample><screen>\n"
"SRM -&gt; aboot\n"
"SRM -&gt; MILO\n"
"ARC -&gt; MILO\n"
"</screen></informalexample> Because <command>MILO</command> is not available "
"for any of the Alpha systems currently in production (as of February 2000), "
"and because it is no longer necessary to buy an OpenVMS or Tru64 Unix "
"license to have SRM firmware on your older Alpha, it is recommended that you "
"use SRM and <command>aboot</command> on new installations of GNU/Linux, "
"unless you wish to dual-boot with Windows NT."
msgstr ""

#. Tag: para
#: boot-installer.xml:249
#, 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 "
"<command>arc</command> command). For the reasons mentioned above, we "
"recommend switching to SRM before installing &debian;."
msgstr ""

#. Tag: para
#: boot-installer.xml:260
#, no-c-format
msgid ""
"As on other architectures, you should install the newest available revision "
"of the firmware <footnote><para>Except on Jensen, where Linux is not "
"supported on firmware versions newer than 1.7 &mdash; see <ulink url=\"&url-"
"jensen-howto;\"></ulink> for more information</para></footnote> before "
"installing &debian;. For Alpha, firmware updates can be obtained from <ulink "
"url=\"&url-alpha-firmware;\">Alpha Firmware Updates</ulink>."
msgstr ""

#. Tag: title
#: boot-installer.xml:274 boot-installer.xml:883 boot-installer.xml:1423
#: boot-installer.xml:1916 boot-installer.xml:1999 boot-installer.xml:2339
#: boot-installer.xml:2435
#, no-c-format
msgid "Booting with TFTP"
msgstr ""

#. Tag: para
#: boot-installer.xml:275
#, no-c-format
msgid ""
"In SRM, Ethernet interfaces are named with the <userinput>ewa</userinput> "
"prefix, and will be listed in the output of the <userinput>show dev</"
"userinput> command, like this (edited slightly): <informalexample><screen>\n"
"&gt;&gt;&gt; show dev\n"
"ewa0.0.0.9.0               EWA0              08-00-2B-86-98-65\n"
"ewb0.0.0.11.0              EWB0              08-00-2B-86-98-54\n"
"ewc0.0.0.2002.0            EWC0              00-06-2B-01-32-B0\n"
"</screen></informalexample> You first need to set the boot protocol: "
"<informalexample><screen>\n"
"&gt;&gt;&gt; set ewa0_protocol bootp\n"
"</screen></informalexample> Then check the medium type is correct: "
"<informalexample><screen>\n"
"&gt;&gt;&gt; set ewa0_mode <replaceable>mode</replaceable>\n"
"</screen></informalexample> You can get a listing of valid modes with "
"<userinput>&gt;&gt;&gt;set ewa0_mode</userinput>."
msgstr ""

#. Tag: para
#: boot-installer.xml:293
#, no-c-format
msgid ""
"Then, to boot from the first Ethernet interface, you would type: "
"<informalexample><screen>\n"
"&gt;&gt;&gt; boot ewa0 -flags \"\"\n"
"</screen></informalexample> This will boot using the default kernel "
"parameters as included in the netboot image."
msgstr ""

#. Tag: para
#: boot-installer.xml:302
#, no-c-format
msgid ""
"If you wish to use a serial console, you <emphasis>must</emphasis> pass the "
"<userinput>console=</userinput> parameter to the kernel. This can be done "
"using the <userinput>-flags</userinput> argument to the SRM <userinput>boot</"
"userinput> command. The serial ports are named the same as their "
"corresponding files in <userinput>/dev</userinput>. Also, when specifying "
"additional kernel parameters, you must repeat certain default options that "
"are needed by the &d-i; images. For example, to boot from <userinput>ewa0</"
"userinput> and use a console on the first serial port, you would type:"
msgstr ""

#. Tag: screen
#: boot-installer.xml:314
#, no-c-format
msgid ""
"&gt;&gt;&gt; boot ewa0 -flags &quot;root=/dev/ram ramdisk_size=16384 "
"console=ttyS0&quot;"
msgstr ""

#. Tag: title
#: boot-installer.xml:319
#, no-c-format
msgid "Booting from CD-ROM with the SRM Console"
msgstr ""

#. Tag: para
#: boot-installer.xml:320
#, no-c-format
msgid ""
"Type <informalexample><screen>\n"
"&gt;&gt;&gt; boot xxxx -flags 0\n"
"</screen></informalexample> where <replaceable>xxxx</replaceable> is your CD-"
"ROM drive in SRM notation."
msgstr ""

#. Tag: title
#: boot-installer.xml:332
#, no-c-format
msgid "Booting from CD-ROM with the ARC or AlphaBIOS Console"
msgstr ""

#. Tag: para
#: boot-installer.xml:333
#, no-c-format
msgid ""
"To boot a CD-ROM from the ARC console, find your sub-architecture code name "
"(see <xref linkend=\"alpha-cpus\"/>), then enter <filename>\\milo\\linload."
"exe</filename> as the boot loader and <filename>\\milo"
"\\<replaceable>subarch</replaceable></filename> (where <replaceable>subarch</"
"replaceable> is the proper subarchitecture name) as the OS Path in the `OS "
"Selection Setup' menu. Ruffians make an exception: You need to use <filename>"
"\\milo\\ldmilo.exe</filename> as boot loader."
msgstr ""

#. Tag: title
#: boot-installer.xml:349
#, no-c-format
msgid "Booting from Floppies with the SRM Console"
msgstr ""

#. Tag: para
#: boot-installer.xml:350
#, no-c-format
msgid ""
"At the SRM prompt (<prompt>&gt;&gt;&gt;</prompt>), issue the following "
"command: <informalexample><screen>\n"
"&gt;&gt;&gt; boot dva0 -flags 0\n"
"</screen></informalexample> possibly replacing <filename>dva0</filename> "
"with the actual device name. Usually, <filename>dva0</filename> is the "
"floppy; type <informalexample><screen>\n"
"&gt;&gt;&gt; show dev\n"
"</screen></informalexample> to see the list of devices (e.g., if you want to "
"boot from a CD). Note that if you are booting via MILO, <command>-flags</"
"command> argument is ignored, so you can just type <command>boot dva0</"
"command>. If everything works OK, you will eventually see the Linux kernel "
"boot."
msgstr ""

#. Tag: para
#: boot-installer.xml:367
#, no-c-format
msgid ""
"If you want to specify kernel parameters when booting via <command>aboot</"
"command>, use the following command: <informalexample><screen>\n"
"&gt;&gt;&gt; boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 "
"load_ramdisk=1 arguments\"\n"
"</screen></informalexample> (typed on one line), substituting, if necessary, "
"the actual SRM boot device name for <filename>dva0</filename>, the Linux "
"boot device name for <filename>fd0</filename>, and the desired kernel "
"parameters for <filename>arguments</filename>."
msgstr ""

#. Tag: para
#: boot-installer.xml:379
#, no-c-format
msgid ""
"If you want to specify kernel parameters when booting via <command>MILO</"
"command>, you will have to interrupt bootstrap once you get into MILO. See "
"<xref linkend=\"booting-from-milo\"/>."
msgstr ""

#. Tag: title
#: boot-installer.xml:389
#, no-c-format
msgid "Booting from Floppies with the ARC or AlphaBIOS Console"
msgstr ""

#. Tag: para
#: boot-installer.xml:391
#, no-c-format
msgid ""
"In the OS Selection menu, set <command>linload.exe</command> as the boot "
"loader, and <command>milo</command> as the OS Path. Bootstrap using the "
"newly created entry."
msgstr ""

#. Tag: title
#: boot-installer.xml:400
#, no-c-format
msgid "Booting with MILO"
msgstr ""

#. Tag: para
#: boot-installer.xml:401
#, 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 ""

#. Tag: para
#: boot-installer.xml:407
#, 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: "
"<informalexample><screen>\n"
"MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 <!-- arguments -->\n"
"</screen></informalexample> If you are booting from something other than a "
"floppy, substitute <filename>fd0</filename> in the above example with the "
"appropriate device name in Linux notation. The <command>help</command> "
"command would give you a brief MILO command reference."
msgstr ""

#. Tag: title
#: boot-installer.xml:426
#, no-c-format
msgid "Booting from TFTP"
msgstr ""

#. Tag: para
#: boot-installer.xml:432 boot-installer.xml:889 boot-installer.xml:1441
#: boot-installer.xml:1922 boot-installer.xml:2345 boot-installer.xml:2441
#, 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 ""

#. Tag: para
#: boot-installer.xml:437 boot-installer.xml:894 boot-installer.xml:1446
#: boot-installer.xml:1927 boot-installer.xml:2350 boot-installer.xml:2446
#, no-c-format
msgid ""
"Older systems such as the 715 might require the use of an RBOOT server "
"instead of a BOOTP server."
msgstr ""

#. Tag: para
#: boot-installer.xml:442 boot-installer.xml:899 boot-installer.xml:1451
#: boot-installer.xml:1932 boot-installer.xml:2355 boot-installer.xml:2451
#, no-c-format
msgid ""
"The installation method to support network booting is described in <xref "
"linkend=\"install-tftp\"/>."
msgstr ""

#. Tag: title
#: boot-installer.xml:450
#, no-c-format
msgid "Booting from TFTP on NetWinder"
msgstr ""

#. Tag: para
#: boot-installer.xml:452
#, no-c-format
msgid ""
"NetWinders have two network interfaces: The 10Mbps NE2000-compatible card is "
"<filename>eth0</filename> and the 100Mbps Tulip card is <filename>eth1</"
"filename>."
msgstr ""

#. Tag: para
#: boot-installer.xml:458
#, no-c-format
msgid ""
"You need NeTTrom 2.2.1 or later to boot the installation system. NeTTrom "
"2.3.3 is recommended: get these files from <ulink url=\"ftp://ftp.netwinder."
"org/pub/netwinder/firmware/\"></ulink>:"
msgstr ""

#. Tag: filename
#: boot-installer.xml:467
#, no-c-format
msgid "nettrom-2.3-3.armv4l.rpm"
msgstr ""

#. Tag: filename
#: boot-installer.xml:472
#, no-c-format
msgid "nettrom-2.3.3.bin"
msgstr ""

#. Tag: filename
#: boot-installer.xml:477
#, no-c-format
msgid "nettrom-2.3.3.bin.md5sum"
msgstr ""

#. Tag: para
#: boot-installer.xml:482
#, no-c-format
msgid ""
"After rebooting and interrupting the boot process during the countdown, you "
"must first configure the network either with a static address: "
"<informalexample><screen>\n"
"    NeTTrom command-&gt; setenv eth0_ip 192.168.0.10/24\n"
"</screen></informalexample> where 24 is the number of set bits in the "
"netmask, or a dynamic address: <informalexample><screen>\n"
"    NeTTrom command-&gt; boot diskless\n"
"</screen></informalexample> You may also need to configure the "
"<userinput>route1</userinput> settings if the TFTP server is not on the "
"local subnet. The rest of the config is pretty standard (the save-all step "
"is optional): <informalexample><screen>\n"
"    NeTTrom command-&gt; setenv kerntftpserver 192.168.0.1\n"
"    NeTTrom command-&gt; setenv kerntftpfile boot.img\n"
"    NeTTrom command-&gt; save-all\n"
"    NeTTrom command-&gt; setenv netconfig_eth0 flash\n"
"    NeTTrom command-&gt; setenv kernconfig tftp\n"
"    NeTTrom command-&gt; setenv rootdev /dev/ram\n"
"    NeTTrom command-&gt; setenv cmdappend root=/dev/ram\n"
"</screen></informalexample> Only the last four of these interfere with "
"normal disk booting, so it is safe to issue <command>save-all</command> "
"right before them, which will store the network settings in case you need to "
"boot from the network again. If you want to use the serial console to "
"install your NetWinder, you also need the following setting: "
"<informalexample><screen>\n"
"    NeTTrom command-&gt; setenv cmdappend root=/dev/ram "
"console=ttyS0,115200\n"
"</screen></informalexample> Use the <command>printenv</command> command to "
"review your environment settings. Finally, if your <envar>cmdappend</envar> "
"NeTTrom variable has the <option>noinitrd</option> option, you must remove "
"it so the downloaded kernel can boot with its attached ramdisk."
msgstr ""

#. Tag: title
#: boot-installer.xml:518
#, no-c-format
msgid "Booting from TFTP on CATS"
msgstr ""

#. Tag: para
#: boot-installer.xml:520
#, no-c-format
msgid ""
"On CATS machines, use <command>boot de0:</command> or similar at the Cyclone "
"prompt."
msgstr ""

#. Tag: title
#: boot-installer.xml:531
#, no-c-format
msgid "Booting from CD-ROM"
msgstr ""

#. Tag: para
#: boot-installer.xml:537 boot-installer.xml:590 boot-installer.xml:1060
#: boot-installer.xml:1879 boot-installer.xml:2127 boot-installer.xml:2481
#, 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 <phrase arch=\"i386\"> configure your system for booting off a "
"CD as described in <xref linkend=\"boot-dev-select\"/>, </phrase> insert "
"your CD, reboot, and proceed to the next chapter."
msgstr ""

#. Tag: para
#: boot-installer.xml:548 boot-installer.xml:601 boot-installer.xml:1071
#: boot-installer.xml:1890 boot-installer.xml:2138 boot-installer.xml:2492
#, 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 ""

#. Tag: para
#: boot-installer.xml:556 boot-installer.xml:609 boot-installer.xml:1079
#: boot-installer.xml:1898 boot-installer.xml:2146 boot-installer.xml:2500
#, 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 ""

#. Tag: para
#: boot-installer.xml:564 boot-installer.xml:617 boot-installer.xml:1087
#: boot-installer.xml:1906 boot-installer.xml:2154 boot-installer.xml:2508
#, no-c-format
msgid ""
"If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
msgstr ""

#. Tag: para
#: boot-installer.xml:571
#, no-c-format
msgid ""
"To boot a CD-ROM from the Cyclone console prompt, use the command "
"<command>boot cd0:cats.bin</command>"
msgstr ""

#. Tag: title
#: boot-installer.xml:584 boot-installer.xml:1054 boot-installer.xml:1867
#: boot-installer.xml:2121 boot-installer.xml:2475
#, no-c-format
msgid "Booting from a CD-ROM"
msgstr ""

#. Tag: title
#: boot-installer.xml:722
#, no-c-format
msgid ""
"Booting from linux using <command>LILO</command> or <command>GRUB</command>"
msgstr ""

#. Tag: para
#: boot-installer.xml:725
#, no-c-format
msgid ""
"To boot the installer from hard disk, you must first download and place the "
"needed files as described in <xref linkend=\"boot-drive-files\"/>."
msgstr ""

#. Tag: para
#: boot-installer.xml:730
#, no-c-format
msgid ""
"If you intend to use the hard drive only for booting and then download "
"everything over the network, you should download the <filename>netboot/"
"debian-installer/i386/initrd.gz</filename> file and its corresponding "
"kernel. This will allow you to repartition the hard disk from which you boot "
"the installer, although you should do so with care."
msgstr ""

#. Tag: para
#: boot-installer.xml:739
#, no-c-format
msgid ""
"Alternatively, if you intend to keep an existing partition on the hard drive "
"unchanged during the install, you can download the <filename>hd-media/initrd."
"gz</filename> file and its kernel, as well as copy a CD iso to the drive "
"(make sure the file is named ending in \".iso\"). The installer can then "
"boot from the drive and install from the CD image, without needing the "
"network."
msgstr ""

#. Tag: para
#: boot-installer.xml:748
#, no-c-format
msgid ""
"For <command>LILO</command>, you will need to configure two essential things "
"in <filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> to "
"load the <filename>initrd.gz</filename> installer at boot time; </para></"
"listitem> <listitem><para> have the <filename>vmlinuz</filename> kernel use "
"a RAM disk as its root partition. </para></listitem> </itemizedlist> Here is "
"a <filename>/etc/lilo.conf</filename> example:"
msgstr ""

#. Tag: screen
#: boot-installer.xml:769
#, no-c-format
msgid ""
"image=/boot/newinstall/vmlinuz\n"
"       label=newinstall\n"
"       initrd=/boot/newinstall/initrd.gz\n"
"       root=/dev/ram0\n"
"       append=\"devfs=mount,dall ramdisk_size=12000\""
msgstr ""

#. Tag: para
#: boot-installer.xml:769
#, no-c-format
msgid ""
"For more details, refer to the <citerefentry><refentrytitle>initrd</"
"refentrytitle> <manvolnum>4</manvolnum></citerefentry> and "
"<citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</"
"manvolnum></citerefentry> man pages. Now run <userinput>lilo</userinput> and "
"reboot."
msgstr ""

#. Tag: para
#: boot-installer.xml:778
#, no-c-format
msgid ""
"The procedure for <command>GRUB</command> is quite similar. Locate your "
"<filename>menu.lst</filename> in the <filename>/boot/grub/</filename> "
"directory (sometimes in the <filename>/boot/boot/grub/</filename>), add the "
"following lines: <informalexample><screen>\n"
"title  New Install\n"
"kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 ramdisk_size=12000\n"
"initrd (hd0,0)/boot/newinstall/initrd.gz\n"
"</screen></informalexample> and reboot. If the boot fails, you can try "
"adding <userinput>devfs=mount,dall</userinput> to the <quote>kernel</quote> "
"line."
msgstr ""

#. Tag: para
#: boot-installer.xml:790
#, no-c-format
msgid ""
"Note that the value of the <userinput>ramdisk_size</userinput> may need to "
"be adjusted for the size of the initrd image. From here on, there should be "
"no difference between <command>GRUB</command> or <command>LILO</command>."
msgstr ""

#. Tag: title
#: boot-installer.xml:801 boot-installer.xml:2279
#, no-c-format
msgid "Booting from USB memory stick"
msgstr ""

#. Tag: para
#: boot-installer.xml:802
#, no-c-format
msgid ""
"Let's assume you have prepared everything from <xref linkend=\"boot-dev-"
"select\"/> and <xref linkend=\"boot-usb-files\"/>. Now just plug your USB "
"stick into some free USB connector and reboot the computer. The system "
"should boot up, and you should be presented with the <prompt>boot:</prompt> "
"prompt. Here you can enter optional boot arguments, or just hit &enterkey;."
msgstr ""

#. Tag: para
#: boot-installer.xml:811
#, no-c-format
msgid ""
"In case your computer doesn't support booting from USB memory devices, you "
"can still use a single floppy to do the initial boot and then switch to USB. "
"Boot your system as described in <xref linkend=\"floppy-boot\"/>; the kernel "
"on the boot floppy should detect your USB stick automatically. When it asks "
"for the root floppy, simply press &enterkey;. You should see &d-i; starting."
msgstr ""

#. Tag: title
#: boot-installer.xml:824 boot-installer.xml:1979 boot-installer.xml:2381
#: boot-installer.xml:2529
#, no-c-format
msgid "Booting from Floppies"
msgstr ""

#. Tag: para
#: boot-installer.xml:825 boot-installer.xml:2389
#, no-c-format
msgid ""
"You will have already downloaded the floppy images you needed and created "
"floppies from the images in <xref linkend=\"create-floppy\"/>."
msgstr ""

#. Tag: para
#: boot-installer.xml:832
#, 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:838
#, no-c-format
msgid ""
"For installing from an LS-120 drive (ATAPI version) with a set of floppies, "
"you need to specify the virtual location for the floppy device. This is done "
"with the <emphasis>root=</emphasis> boot argument, giving the device that "
"the ide-floppy driver maps the device to. For example, if your LS-120 drive "
"is connected as the first IDE device (master) on the second cable, you enter "
"<userinput>linux root=/dev/hdc</userinput> at the boot prompt. Installation "
"from LS-120 is only supported by 2.4 and later kernels."
msgstr ""

#. Tag: para
#: boot-installer.xml:849
#, no-c-format
msgid ""
"Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</"
"keycap> <keycap>Delete</keycap></keycombo> does not properly reset the "
"machine, so a ``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 ""

#. Tag: para
#: boot-installer.xml:858
#, no-c-format
msgid ""
"The floppy disk will be accessed, and you should then see a screen that "
"introduces the boot floppy and ends with the <prompt>boot:</prompt> prompt."
msgstr ""

#. Tag: para
#: boot-installer.xml:864
#, no-c-format
msgid ""
"Once you press &enterkey;, you should see the message "
"<computeroutput>Loading...</computeroutput>, followed by "
"<computeroutput>Uncompressing Linux...</computeroutput>, and then a "
"screenfull or so of information about the hardware in your system. More "
"information on this phase of the boot process can be found below in <xref "
"linkend=\"kernel-msgs\"/>."
msgstr ""

#. Tag: para
#: boot-installer.xml:873
#, no-c-format
msgid ""
"After booting from the boot floppy, the root floppy is requested. Insert the "
"root floppy and press &enterkey;, and the contents are loaded into memory. "
"The installer program <command>debian-installer</command> is automatically "
"launched."
msgstr ""

#. Tag: para
#: boot-installer.xml:907
#, no-c-format
msgid "There are various ways to do a TFTP boot on i386."
msgstr ""

#. Tag: title
#: boot-installer.xml:913
#, no-c-format
msgid "NIC or Motherboard that support PXE"
msgstr ""

#. Tag: para
#: boot-installer.xml:914
#, no-c-format
msgid ""
"It could be that your Network Interface Card or Motherboard provides PXE "
"boot functionality. This is a <trademark class=\"trade\">Intel</trademark> "
"re-implemention of TFTP boot. If so you may be able to configure your BIOS "
"to boot from the network."
msgstr ""

#. Tag: title
#: boot-installer.xml:925
#, no-c-format
msgid "NIC with network bootROM"
msgstr ""

#. Tag: para
#: boot-installer.xml:926
#, no-c-format
msgid ""
"It could be that your Network Interface Card provides TFTP boot "
"functionality."
msgstr ""

#. Tag: para
#: boot-installer.xml:931
#, no-c-format
msgid ""
"Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. "
"Please refer to this document."
msgstr ""

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

#. Tag: para
#: boot-installer.xml:940
#, no-c-format
msgid ""
"The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> "
"provides bootdiskettes and even bootroms that do a TFTPboot."
msgstr ""

#. Tag: title
#: boot-installer.xml:949
#, no-c-format
msgid "i386 Boot Parameters"
msgstr ""

#. Tag: para
#: boot-installer.xml:950
#, no-c-format
msgid ""
"When the installer boots, you will be presented with the boot prompt, "
"<prompt>boot:</prompt>. You can do two things at the <prompt>boot:</prompt> "
"prompt. You can press the function keys <keycap>F1</keycap> through "
"<keycap>F10</keycap> to view a few pages of helpful information, or you can "
"press <keycap>Enter</keycap> to boot the system."
msgstr ""

#. Tag: para
#: boot-installer.xml:958
#, no-c-format
msgid ""
"Information on boot parameters which might be useful can be found by "
"pressing <keycap>F3</keycap> through <keycap>F7</keycap>. If you add any "
"parameters to the boot command line, be sure to type the boot method (the "
"default is <userinput>linux</userinput>) and a space before the first "
"parameter (e.g., <userinput>linux floppy=thinkpad</userinput>). If you "
"simply press &enterkey;, that's the same as typing <userinput>linux</"
"userinput> without any special parameters."
msgstr ""

#. Tag: para
#: boot-installer.xml:969
#, 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 <userinput>floppy=thinkpad</userinput>."
msgstr ""

#. Tag: para
#: boot-installer.xml:975
#, 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 <userinput>hd=<replaceable>cylinders</replaceable>,"
"<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></"
"userinput>."
msgstr ""

#. Tag: para
#: boot-installer.xml:984
#, no-c-format
msgid ""
"If you have a very old machine, and the kernel hangs after saying "
"<computeroutput>Checking 'hlt' instruction...</computeroutput>, then you "
"should try the <userinput>no-hlt</userinput> boot argument, which disables "
"this test."
msgstr ""

#. Tag: para
#: boot-installer.xml:991
#, no-c-format
msgid ""
"If your screen begins to show a weird picture while the kernel boots, eg. "
"pure white, pure black or colored pixel garbage, your system may contain a "
"problematic video card which does not switch to the framebuffer mode "
"properly. Then you can use the boot parameter <userinput>debian-installer/"
"framebuffer=false</userinput> or <userinput>video=vga16:off</userinput> to "
"disable the framebuffer console. Only the English language will be available "
"during the installation due to limited console features. See <xref linkend="
"\"boot-parms\"/> for details."
msgstr ""

#. Tag: title
#: boot-installer.xml:1008
#, no-c-format
msgid "System freeze during the PCMCIA configuration phase"
msgstr ""

#. Tag: para
#: boot-installer.xml:1010
#, no-c-format
msgid ""
"Some laptop models produced by Dell are known to crash when PCMCIA device "
"detection tries to access some hardware addresses. Other laptops may display "
"similar problems. If you experience such a problem and you don't need PCMCIA "
"support during the installation, you can disable PCMCIA using the "
"<userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can "
"then configure PCMCIA after the installation is completed and exclude the "
"resource range causing the problems."
msgstr ""

#. Tag: para
#: boot-installer.xml:1020
#, no-c-format
msgid ""
"Alternatively, you can boot the installer in expert mode. You will then be "
"asked to enter the resource range options your hardware needs. For example, "
"if you have one of the Dell laptops mentioned above, you should enter "
"<userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list "
"of some common resource range options in the <ulink url=\"http://pcmcia-cs."
"sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource "
"settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the "
"commas, if any, when you enter this value in the installer."
msgstr ""

#. Tag: title
#: boot-installer.xml:1037
#, no-c-format
msgid "System freeze while loading the USB modules"
msgstr ""

#. Tag: para
#: boot-installer.xml:1038
#, 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 <userinput>debian-installer/probe/usb=false</"
"userinput> parameter at the boot prompt, which will prevent the modules from "
"being loaded."
msgstr ""

#. Tag: title
#: boot-installer.xml:1095
#, no-c-format
msgid "CD Contents"
msgstr ""

#. Tag: para
#: boot-installer.xml:1097
#, no-c-format
msgid ""
"There are three basic variations of Debian Install CDs. The "
"<emphasis>Business Card</emphasis> CD has a minimal installation that will "
"fit on the small form factor CD media. It requires a network connection in "
"order to install the rest of the base installation and make a usable system. "
"The <emphasis>Network Install</emphasis> CD has all of the packages for a "
"base install but requires a network connection to a Debian mirror site in "
"order to install the extra packages one would want for a complete system . "
"The set of Debian CDs can install a complete system from the wide range of "
"packages without needing access to the network."
msgstr ""

#. Tag: para
#: boot-installer.xml:1113
#, 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 ""

#. Tag: para
#: boot-installer.xml:1129
#, no-c-format
msgid ""
"The Debian Installer CD contains a small EFI partition where the "
"<command>ELILO</command> bootloader, its configuration file, the installer's "
"kernel, and initial filesystem (initrd) are located. The running system also "
"contains an EFI partition where the necessary files for booting the system "
"reside. These files are readable from the EFI Shell as described below."
msgstr ""

#. Tag: para
#: boot-installer.xml:1138
#, no-c-format
msgid ""
"Most of the details of how <command>ELILO</command> actually loads and "
"starts a system are transparent to the system installer. However, the "
"installer must set up an EFI partition prior to installing the base system. "
"Otherwise, the installation of <command>ELILO</command> will fail, rendering "
"the system un-bootable. The EFI partition is allocated and formatted in the "
"partitioning step of the installation prior to loading any packages on the "
"system disk. The partitioning task also verifies that a suitable EFI "
"partition is present before allowing the installation to proceed."
msgstr ""

#. Tag: para
#: boot-installer.xml:1150
#, no-c-format
msgid ""
"The EFI Boot Manager is presented as the last step of the firmware "
"initialization. It displays a menu list from which the user can select an "
"option. Depending on the model of system and what other software has been "
"loaded on the system, this menu may be different from one system to another. "
"There should be at least two menu items displayed, <command>Boot Option "
"Maintenance Menu</command> and <command>EFI Shell (Built-in)</command>. "
"Using the first option is preferred, however, if that option is not "
"available or the CD for some reason does not boot with it, use the second "
"option."
msgstr ""

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

#. Tag: para
#: boot-installer.xml:1170
#, no-c-format
msgid ""
"The EFI Boot Manager will select a default boot action, typically the first "
"menu choice, within a pre-set number of seconds. This is indicated by a "
"countdown at the bottom of the screen. Once the timer expires and the "
"systems starts the default action, you may have to reboot the machine in "
"order to continue the installation. If the default action is the EFI Shell, "
"you can return to the Boot Manager by running <command>exit</command> at the "
"shell prompt."
msgstr ""

#. Tag: title
#: boot-installer.xml:1182
#, no-c-format
msgid "Option 1: Booting from the Boot Option Maintenance Menu"
msgstr ""

#. Tag: para
#: boot-installer.xml:1189
#, 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 ""

#. Tag: para
#: boot-installer.xml:1195
#, no-c-format
msgid ""
"Select <command>Boot Maintenance Menu</command> from the menu with the arrow "
"keys and press <command>ENTER</command>. This will display a new menu."
msgstr ""

#. Tag: para
#: boot-installer.xml:1201
#, no-c-format
msgid ""
"Select <command>Boot From a File</command> from the menu with the arrow keys "
"and press <command>ENTER</command>. This will display a list of devices "
"probed by the firmware. You should see two menu lines containing either the "
"label <command>Debian Inst [Acpi ...</command> or <command>Removable Media "
"Boot</command>. If you examine the rest of the menu line, you will notice "
"that the device and controller information should be the same."
msgstr ""

#. Tag: para
#: boot-installer.xml:1212
#, no-c-format
msgid ""
"You can choose either of the entries that refer to the CD/DVD drive. Select "
"your choice with the arrow keys and press <command>ENTER</command>. If you "
"choose <command>Removable Media Boot</command> the machine will immediately "
"start the boot load sequence. If you choose <command>Debian Inst [Acpi ...</"
"command> instead, it will display a directory listing of the bootable "
"portion of the CD, requiring you to proceed to the next (additional) step."
msgstr ""

#. Tag: para
#: boot-installer.xml:1223
#, no-c-format
msgid ""
"You will only need this step if you chose <command>Debian Inst [Acpi ...</"
"command>. The directory listing will also show <command>[Treat like "
"Removable Media Boot]</command> on the next to the last line. Select this "
"line with the arrow keys and press <command>ENTER</command>. This will start "
"the boot load sequence."
msgstr ""

#. Tag: para
#: boot-installer.xml:1235
#, 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 ""

#. Tag: title
#: boot-installer.xml:1245
#, no-c-format
msgid "Option 2: Booting from the EFI Shell"
msgstr ""

#. Tag: para
#: boot-installer.xml:1246
#, no-c-format
msgid ""
"If, for some reason, option 1 is not successful, reboot the machine and when "
"the EFI Boot Manager screen appears there should be one option called "
"<command>EFI Shell [Built-in]</command>. Boot the Debian Installer CD with "
"the following steps:"
msgstr ""

#. Tag: para
#: boot-installer.xml:1257
#, 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 ""

#. Tag: para
#: boot-installer.xml:1263
#, no-c-format
msgid ""
"Select <command>EFI Shell</command> from the menu with the arrow keys and "
"press <command>ENTER</command>. The EFI Shell will scan all of the bootable "
"devices and display them to the console before displaying its command "
"prompt. The recognized bootable partitions on devices will show a device "
"name of <filename>fs<replaceable>n</replaceable>:</filename>. All other "
"recognized partitions will be named <filename>blk<replaceable>n</"
"replaceable>:</filename>. If you inserted the CD just before entering the "
"shell, this may take a few extra seconds as it initializes the CD drive."
msgstr ""

#. Tag: para
#: boot-installer.xml:1277
#, no-c-format
msgid ""
"Examine the output from the shell looking for the CDROM drive. It is most "
"likely the <filename>fs0:</filename> device although other devices with "
"bootable partitions will also show up as <filename>fs<replaceable>n</"
"replaceable></filename>."
msgstr ""

#. Tag: para
#: boot-installer.xml:1284
#, no-c-format
msgid ""
"Enter <command>fs<replaceable>n</replaceable>:</command> and press "
"<command>ENTER</command> to select that device where <replaceable>n</"
"replaceable> is the partition number for the CDROM. The shell will now "
"display the partition number as its prompt."
msgstr ""

#. Tag: para
#: boot-installer.xml:1291
#, no-c-format
msgid ""
"Enter <command>elilo</command> and press <command>ENTER</command>. This will "
"start the boot load sequence."
msgstr ""

#. Tag: para
#: boot-installer.xml:1298
#, no-c-format
msgid ""
"As with option 1, these steps start the Debian boot loader which will "
"display a menu page for you to select a boot kernel and options. You can "
"also enter the shorter <command>fs<replaceable>n</replaceable>:elilo</"
"command> command at the shell prompt. Proceed to selecting the boot kernel "
"and options."
msgstr ""

#. Tag: title
#: boot-installer.xml:1312
#, no-c-format
msgid "Installing using a Serial Console"
msgstr ""

#. Tag: para
#: boot-installer.xml:1314
#, no-c-format
msgid ""
"You may choose to perform an install using a monitor and keyboard or using a "
"serial connection. To use a monitor/keyboard setup, select an option "
"containing the string [VGA console]. To install over a serial connection, "
"choose an option containing the string [<replaceable>BAUD</replaceable> baud "
"serial console], where <replaceable>BAUD</replaceable> is the speed of your "
"serial console. Menu items for the most typical baud rate settings on the "
"ttyS0 device are preconfigured."
msgstr ""

#. Tag: para
#: boot-installer.xml:1325
#, no-c-format
msgid ""
"In most circumstances, you will want the installer to use the same baud rate "
"as your connection to the EFI console. If you aren't sure what this setting "
"is, you can obtain it using the command <command>baud</command> at the EFI "
"shell."
msgstr ""

#. Tag: para
#: boot-installer.xml:1332
#, no-c-format
msgid ""
"If there is not an option available that is configured for the serial device "
"or baud rate you would like to use, you may override the console setting for "
"one of the existing menu options. For example, to use a 57600 baud console "
"over the ttyS1 device, enter <command>console=ttyS1,57600n8</command> into "
"the <classname>Boot:</classname> text window."
msgstr ""

#. Tag: para
#: boot-installer.xml:1343
#, no-c-format
msgid ""
"Most IA-64 boxes ship with a default console setting of 9600 baud. This "
"setting is rather slow, and the normal installation process will take a "
"significant time to draw each screen. You should consider either increasing "
"the baud rate used for performing the installation, or performing a Text "
"Mode installation. See the <classname>Params</classname> help menu for "
"instructions on starting the installer in Text Mode."
msgstr ""

#. Tag: para
#: boot-installer.xml:1352
#, 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:1361
#, no-c-format
msgid "Selecting the Boot Kernel and Options"
msgstr ""

#. Tag: para
#: boot-installer.xml:1363
#, no-c-format
msgid ""
"The boot loader will display a form with a menu list and a text window with "
"a <classname>Boot:</classname> prompt. The arrow keys select an item from "
"the menu and any text typed at the keyboard will appear in the text window. "
"There are also help screens which can be displayed by pressing the "
"appropriate function key. The <classname>General</classname> help screen "
"explains the menu choices and the <classname>Params</classname> screen "
"explains the common command line options."
msgstr ""

#. Tag: para
#: boot-installer.xml:1375
#, no-c-format
msgid ""
"Consult the <classname>General</classname> help screen for the description "
"of the kernels and install modes most appropriate for your installation. You "
"should also consult <xref linkend=\"boot-parms\"/> below for any additional "
"parameters that you may want to set in the <classname>Boot:</classname> text "
"window. The kernel version you choose selects the kernel version that will "
"be used for both the installation process and the installed system. If you "
"encounter kernel problems with the installation, you may also have those "
"same problems with the system you install. The following two steps will "
"select and start the install:"
msgstr ""

#. Tag: para
#: boot-installer.xml:1393
#, 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:1398
#, 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:1405
#, no-c-format
msgid ""
"Press <command>ENTER</command>. This will load and start the kernel. The "
"kernel will display its usual initialization messages followed by the first "
"screen of the Debian Installer."
msgstr ""

#. Tag: para
#: boot-installer.xml:1414
#, 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:1425
#, no-c-format
msgid ""
"Booting an IA64 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 ""

#. Tag: para
#: boot-installer.xml:1459
#, no-c-format
msgid ""
"Network booting an ia64 system requires two architecture-specific actions. "
"On the boot server, DHCP and TFTP must be configured to deliver "
"<command>elilo</command>. On the client a new boot option must be defined in "
"the EFI boot manager to enable loading over a network."
msgstr ""

#. Tag: title
#: boot-installer.xml:1470
#, no-c-format
msgid "Configuring the Server"
msgstr ""

#. Tag: para
#: boot-installer.xml:1471
#, no-c-format
msgid ""
"A suitable TFTP entry for network booting an ia64 system looks something "
"like this: <informalexample><screen>\n"
"host mcmuffin {\n"
"        hardware ethernet 00:30:6e:1e:0e:83;\n"
"        fixed-address 10.0.0.21;\n"
"        filename \"debian-installer/ia64/elilo.efi\";\n"
"}\n"
"</screen></informalexample> Note that the goal is to get <command>elilo.efi</"
"command> running on the client."
msgstr ""

#. Tag: para
#: boot-installer.xml:1481
#, no-c-format
msgid ""
"Extract the <filename>netboot.tar.gz</filename> file into the directory used "
"as the root for your tftp server. Typical tftp root directories include "
"<filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. This "
"will create a <filename>debian-installer</filename> directory tree "
"containing the boot files for an IA-64 system."
msgstr ""

#. Tag: screen
#: boot-installer.xml:1491
#, 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 ""

#. Tag: para
#: boot-installer.xml:1491
#, no-c-format
msgid ""
"The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</"
"filename> file that should work for most configurations. However, should you "
"need to make changes to this file, you can find it in the <filename>debian-"
"installer/ia64/</filename> directory. It is possible to have different "
"config files for different clients by naming them using the client's IP "
"address in hex with the suffix <filename>.conf</filename> instead of "
"<filename>elilo.conf</filename>. See documentation provided in the "
"<classname>elilo</classname> package for details."
msgstr ""

#. Tag: title
#: boot-installer.xml:1508
#, no-c-format
msgid "Configuring the Client"
msgstr ""

#. Tag: para
#: boot-installer.xml:1509
#, no-c-format
msgid ""
"To configure the client to support TFTP booting, start by booting to EFI and "
"entering the <guimenu>Boot Option Maintenance Menu</guimenu>. <itemizedlist> "
"<listitem><para> Add a boot option. </para></listitem> <listitem><para> You "
"should see one or more lines with the text <guimenuitem>Load File [Acpi"
"()/.../Mac()]</guimenuitem>. If more than one of these entries exist, choose "
"the one containing the MAC address of the interface from which you'll be "
"booting. Use the arrow keys to highlight your choice, then press enter. </"
"para></listitem> <listitem><para> Name the entry <userinput>Netboot</"
"userinput> or something similar, save, and exit back to the boot options "
"menu. </para></listitem> </itemizedlist> You should see the new boot option "
"you just created, and selecting it should initiate a DHCP query, leading to "
"a TFTP load of <filename>elilo.efi</filename> from the server."
msgstr ""

#. Tag: para
#: boot-installer.xml:1541
#, 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 ""

#. Tag: para
#: boot-installer.xml:1550
#, no-c-format
msgid ""
"Proceed to the next chapter to continue the installation where you will set "
"up the language locale, network, and the disk partitions."
msgstr ""

#. Tag: title
#: boot-installer.xml:1563
#, no-c-format
msgid "Choosing an Installation Method"
msgstr ""

#. Tag: para
#: boot-installer.xml:1565
#, 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 ""

#. Tag: para
#: boot-installer.xml:1573
#, no-c-format
msgid ""
"If you are using a 2.2.x linux kernel, then you must make sure you are using "
"a ramdisk built to accommodate it, see the <ulink url=\"&disturl;/main/"
"installer-&architecture;/current/images/MANIFEST\">MANIFEST</ulink>. You "
"will also need to use the &ramdisksize; kernel parameter. In general, this "
"means you need to use the initrd22.gz ramdisk from the respective directory."
msgstr ""

#. Tag: para
#: boot-installer.xml:1581
#, no-c-format
msgid ""
"Make sure <userinput>root=/dev/ram</userinput> is one of your kernel "
"parameters."
msgstr ""

#. Tag: para
#: boot-installer.xml:1586
#, no-c-format
msgid ""
"If you're having trouble, check <ulink url=\"&url-m68k-cts-faq;\">cts's "
"&arch-title; debian-installer FAQ</ulink>."
msgstr ""

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

#. Tag: para
#: boot-installer.xml:1604
#, no-c-format
msgid ""
"The only method of installation available to amiga is the hard drive (see "
"<xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not "
"bootable.</emphasis>"
msgstr ""

#. Tag: para
#: boot-installer.xml:1610
#, no-c-format
msgid ""
"Amiga does not currently work with bogl, so if you are seeing bogl errors, "
"you need to include the kernel parameter <userinput>debian-installer/"
"framebuffer=false</userinput>."
msgstr ""

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

#. Tag: para
#: boot-installer.xml:1620
#, no-c-format
msgid ""
"The installer for atari may be started from either the hard drive (see <xref "
"linkend=\"m68k-boot-hd\"/>) or from floppies (see <xref linkend=\"boot-from-"
"floppies\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>"
msgstr ""

#. Tag: para
#: boot-installer.xml:1627
#, no-c-format
msgid ""
"Atari does not currently work with bogl, so if you are seeing bogl errors, "
"you need to include the kernel parameter <userinput>debian-installer/"
"framebuffer=false</userinput>."
msgstr ""

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

#. Tag: para
#: boot-installer.xml:1637
#, no-c-format
msgid ""
"The installer for BVME6000 may be started from a cdrom (see <xref linkend="
"\"m68k-boot-cdrom\"/>), floppies (see <xref linkend=\"boot-from-floppies\"/"
">), or the net (see <xref linkend=\"boot-tftp\"/>)."
msgstr ""

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

#. Tag: para
#: boot-installer.xml:1648
#, no-c-format
msgid ""
"The only method of installation available to mac is from the hard drive (see "
"<xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not "
"bootable.</emphasis> Macs do not have a working 2.4.x kernel."
msgstr ""

#. Tag: para
#: boot-installer.xml:1655
#, no-c-format
msgid ""
"If your hardware uses a 53c9x-based scsi bus, then you may need to include "
"the kernel parameter <userinput>mac53c9x=1</userinput>. Hardware with two "
"such scsi buses, such as the Quadra 950, will need <userinput>mac53c9x=2</"
"userinput> instead."
msgstr ""

#. Tag: title
#: boot-installer.xml:1665
#, no-c-format
msgid "MVME147 and MVME16x"
msgstr ""

#. Tag: para
#: boot-installer.xml:1666
#, no-c-format
msgid ""
"The installer for MVME147 and MVME16x may be started from either floppies "
"(see <xref linkend=\"boot-from-floppies\"/>) or the net (see <xref linkend="
"\"boot-tftp\"/>). <emphasis>In other words the cdrom is not bootable.</"
"emphasis>"
msgstr ""

#. Tag: title
#: boot-installer.xml:1676
#, no-c-format
msgid "Q40/Q60"
msgstr ""

#. Tag: para
#: boot-installer.xml:1677
#, no-c-format
msgid ""
"The only method of installation available to Q40/Q60 is from the hard drive "
"(see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom "
"is not bootable.</emphasis>"
msgstr ""

#. Tag: title
#: boot-installer.xml:1688
#, no-c-format
msgid "Booting from a Hard Disk"
msgstr ""

#. Tag: para
#: boot-installer.xml:1694 boot-installer.xml:2200
#, 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 ""

#. Tag: para
#: boot-installer.xml:1700 boot-installer.xml:2206
#, no-c-format
msgid ""
"To boot the installer from hard disk, you will have already completed "
"downloading and placing the needed files in <xref linkend=\"boot-drive-files"
"\"/>."
msgstr ""

#. Tag: para
#: boot-installer.xml:1709
#, 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 <ulink url=\"&disturl;/main/installer-&architecture;/current/images/"
"MANIFEST\">MANIFEST</ulink> for details)."
msgstr ""

#. Tag: para
#: boot-installer.xml:1717
#, no-c-format
msgid ""
"The three different types of ramdisks are <filename>cdrom</filename>, "
"<filename>hd-media</filename>, and <filename>nativehd</filename>. These "
"ramdisks differ only in their source for installation packages. The "
"<filename>cdrom</filename> ramdisk uses a cdrom to get debian-installer "
"packages. The <filename>hd-media</filename> ramdisk uses an iso image file "
"of a cdrom currently residing on a hard disk. Finally, the "
"<filename>nativehd</filename> ramdisk uses the net to install packages."
msgstr ""

#. Tag: title
#: boot-installer.xml:1738
#, no-c-format
msgid "Booting from AmigaOS"
msgstr ""

#. Tag: para
#: boot-installer.xml:1739
#, no-c-format
msgid ""
"In the <command>Workbench</command>, start the Linux installation process by "
"double-clicking on the <guiicon>StartInstall</guiicon> icon in the "
"<filename>debian</filename> directory."
msgstr ""

#. Tag: para
#: boot-installer.xml:1745
#, 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 <xref linkend=\"d-i-"
"intro\"/>."
msgstr ""

#. Tag: title
#: boot-installer.xml:1760
#, no-c-format
msgid "Booting from Atari TOS"
msgstr ""

#. Tag: para
#: boot-installer.xml:1761
#, no-c-format
msgid ""
"At the GEM desktop, start the Linux installation process by double-clicking "
"on the <guiicon>bootstra.prg</guiicon> icon in the <filename>debian</"
"filename> directory and clicking <guibutton>Ok</guibutton> at the program "
"options dialog box."
msgstr ""

#. Tag: para
#: boot-installer.xml:1768
#, 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 <xref linkend=\"d-i-intro\"/>."
msgstr ""

#. Tag: title
#: boot-installer.xml:1783
#, no-c-format
msgid "Booting from MacOS"
msgstr ""

#. Tag: para
#: boot-installer.xml:1784
#, no-c-format
msgid ""
"You must retain the original Mac system and boot from it. It is "
"<emphasis>essential</emphasis> that, when booting MacOS in preparation for "
"booting the Penguin linux loader, you hold the <keycap>shift</keycap> key "
"down to prevent extensions from loading. If you don't use MacOS except for "
"loading linux, you can accomplish the same thing by removing all extensions "
"and control panels from the Mac's System Folder. Otherwise extensions may be "
"left running and cause random problems with the running linux kernel."
msgstr ""

#. Tag: para
#: boot-installer.xml:1795
#, no-c-format
msgid ""
"Macs require the <command>Penguin</command> bootloader. If you do not have "
"the tools to handle a <command>Stuffit</command> archive, &penguin19.hfs; is "
"an hfs disk image with <command>Penguin</command> unpacked. <xref linkend="
"\"create-floppy\"/> describes how to copy this image to a floppy."
msgstr ""

#. Tag: para
#: boot-installer.xml:1804
#, no-c-format
msgid ""
"At the MacOS desktop, start the Linux installation process by double-"
"clicking on the <guiicon>Penguin Prefs</guiicon> icon in the "
"<filename>Penguin</filename> directory. The <command>Penguin</command> "
"booter will start up. Go to the <guimenuitem>Settings</guimenuitem> item in "
"the <guimenu>File</guimenu> menu, click the <guilabel>Kernel</guilabel> tab. "
"Select the kernel (<filename>vmlinuz</filename>) and ramdisk "
"(<filename>initrd.gz</filename>) images in the <filename>install</filename> "
"directory by clicking on the corresponding buttons in the upper right "
"corner, and navigating the file select dialogs to locate the files."
msgstr ""

#. Tag: para
#: boot-installer.xml:1819
#, no-c-format
msgid ""
"To set the boot parameters in Penguin, choose <guimenu>File</guimenu> -&gt; "
"<guimenuitem>Settings...</guimenuitem>, then switch to the "
"<guilabel>Options</guilabel> tab. Boot parameters may be typed in to the "
"text entry area. If you will always want to use these settings, select "
"<guimenu>File</guimenu> -&gt; <guimenuitem>Save Settings as Default</"
"guimenuitem>."
msgstr ""

#. Tag: para
#: boot-installer.xml:1828
#, no-c-format
msgid ""
"Close the <guilabel>Settings</guilabel> dialog, save the settings and start "
"the bootstrap using the <guimenuitem>Boot Now</guimenuitem> item in the "
"<guimenu>File</guimenu> menu."
msgstr ""

#. Tag: para
#: boot-installer.xml:1835
#, no-c-format
msgid ""
"The <command>Penguin</command> booter will output some debugging information "
"into a window. After this, the screen will go grey, there will be a few "
"seconds' delay. Next, a black screen with white text should come up, "
"displaying all kinds of kernel debugging information. These messages may "
"scroll by too fast for you to read, but that's OK. After a couple of "
"seconds, the installation program should start automatically, so you can "
"continue below at <xref linkend=\"d-i-intro\"/>."
msgstr ""

#. Tag: title
#: boot-installer.xml:1850
#, no-c-format
msgid "Booting from Q40/Q60"
msgstr ""

#. Tag: para
#: boot-installer.xml:1852
#, no-c-format
msgid "FIXME"
msgstr ""

#. Tag: para
#: boot-installer.xml:1856
#, no-c-format
msgid ""
"The installation program should start automatically, so you can continue "
"below at <xref linkend=\"d-i-intro\"/>."
msgstr ""

#. Tag: para
#: boot-installer.xml:1868
#, no-c-format
msgid ""
"Currently, the only &arch-title; subarchitecture that supports CD-ROM "
"booting is the BVME6000."
msgstr ""

#. Tag: para
#: boot-installer.xml:1940
#, no-c-format
msgid ""
"After booting the VMEbus systems you will be presented with the LILO "
"<prompt>Boot:</prompt> prompt. At that prompt enter one of the following to "
"boot Linux and begin installation proper of the Debian software using vt102 "
"terminal emulation:"
msgstr ""

#. Tag: para
#: boot-installer.xml:1951
#, no-c-format
msgid "type <screen>i6000 &enterkey;</screen> to install a BVME4000/6000"
msgstr ""

#. Tag: para
#: boot-installer.xml:1956
#, no-c-format
msgid "type <screen>i162 &enterkey;</screen> to install an MVME162"
msgstr ""

#. Tag: para
#: boot-installer.xml:1961
#, no-c-format
msgid "type <screen>i167 &enterkey;</screen> to install an MVME166/167"
msgstr ""

#. Tag: para
#: boot-installer.xml:1968
#, no-c-format
msgid ""
"You may additionally append the string <screen>TERM=vt100</screen> to use "
"vt100 terminal emulation, e.g., <screen>i6000 TERM=vt100 &enterkey;</screen>."
msgstr ""

#. Tag: para
#: boot-installer.xml:1980
#, no-c-format
msgid ""
"For most &arch-title; architectures, booting from a local filesystem is the "
"recommended method."
msgstr ""

#. Tag: para
#: boot-installer.xml:1985
#, 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 ""

#. Tag: title
#: boot-installer.xml:2002 boot-installer.xml:2049
#, no-c-format
msgid "SGI Indys TFTP Booting"
msgstr ""

#. Tag: para
#: boot-installer.xml:2003
#, no-c-format
msgid ""
"After entering the command monitor use <informalexample><screen>\n"
"bootp():\n"
"</screen></informalexample> on SGI Indys to boot linux and to begin "
"installation of the Debian Software. In order to make this work you may have "
"to unset the <envar>netaddr</envar> environment variable. Type "
"<informalexample><screen>\n"
"unsetenv netaddr\n"
"</screen></informalexample> in the command monitor to do this."
msgstr ""

#. Tag: title
#: boot-installer.xml:2022 boot-installer.xml:2071
#, no-c-format
msgid "Broadcom BCM91250A TFTP Booting"
msgstr ""

#. Tag: para
#: boot-installer.xml:2023
#, no-c-format
msgid ""
"On the Broadcom BCM91250A evaluation board, you have to load the SiByl boot "
"loader via TFTP which will then load and start the Debian installer. In most "
"cases, you will first obtain an IP address via DHCP but it is also possible "
"to configure a static address. In order to use DHCP, you can enter the "
"following command on the CFE prompt: <informalexample><screen>\n"
"ifconfig eth0 -auto\n"
"</screen></informalexample> Once you have obtained an IP address, you can "
"load SiByl with the following command: <informalexample><screen>\n"
"boot 192.168.1.1:/boot/sibyl\n"
"</screen></informalexample> You need to substitute the IP address listed in "
"this example with either the name or the IP address of your TFTP server. "
"Once you issue this command, the installer will be loaded automatically."
msgstr ""

#. Tag: title
#: boot-installer.xml:2046 boot-installer.xml:2580
#, no-c-format
msgid "Boot Parameters"
msgstr ""

#. Tag: para
#: boot-installer.xml:2050
#, no-c-format
msgid ""
"On SGI Indys you can append boot parameters to the <command>bootp():</"
"command> command in the command monitor."
msgstr ""

#. Tag: para
#: boot-installer.xml:2055
#, no-c-format
msgid ""
"Following the <command>bootp():</command> command you can give the path and "
"name of the file to boot if you did not give an explicit name via your bootp/"
"dhcp server. Example: <informalexample><screen>\n"
"bootp():/boot/tftpboot.img\n"
"</screen></informalexample> Further kernel parameters can be passed via "
"<command>append</command>:"
msgstr ""

#. Tag: screen
#: boot-installer.xml:2065
#, no-c-format
msgid "bootp(): append=\"root=/dev/sda1\""
msgstr ""

#. Tag: para
#: boot-installer.xml:2072
#, no-c-format
msgid ""
"You cannot pass any boot parameters directly from the CFE prompt. Instead, "
"you have to edit the <filename>/boot/sibyl.conf</filename> file on the TFTP "
"server and add your parameters to the <replaceable>extra_args</replaceable> "
"variable."
msgstr ""

#. Tag: title
#: boot-installer.xml:2089
#, no-c-format
msgid "s390 Limitations"
msgstr ""

#. Tag: para
#: boot-installer.xml:2090
#, no-c-format
msgid ""
"In order to run the installation system a working network setup and ssh "
"session is needed on S/390."
msgstr ""

#. Tag: para
#: boot-installer.xml:2095
#, 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 a ssh session which will launch the standard installation system."
msgstr ""

#. Tag: title
#: boot-installer.xml:2106
#, no-c-format
msgid "s390 Boot Parameters"
msgstr ""

#. Tag: para
#: boot-installer.xml:2107
#, 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 <ulink url=\"&url-s390-"
"devices;\">Device Drivers and Installation Commands</ulink> for more "
"information about S/390-specific boot parameters."
msgstr ""

#. Tag: para
#: boot-installer.xml:2161
#, 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 <keycap>c</"
"keycap> key, or else the combination of <keycap>Command</keycap>, "
"<keycap>Option</keycap>, <keycap>Shift</keycap>, and <keycap>Delete</keycap> "
"keys together while booting to boot from the CD-ROM."
msgstr ""

#. Tag: para
#: boot-installer.xml:2170
#, 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 ""

#. Tag: para
#: boot-installer.xml:2179
#, 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 <xref "
"linkend=\"boot-newworld\"/> for booting from the hard disk, except use the "
"path to <command>yaboot</command> on the CD at the OF prompt, such as"
msgstr ""

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

#. Tag: title
#: boot-installer.xml:2194
#, no-c-format
msgid "Booting from Hard Disk"
msgstr ""

#. Tag: title
#: boot-installer.xml:2215
#, no-c-format
msgid "Booting CHRP from OpenFirmware"
msgstr ""

#. Tag: emphasis
#: boot-installer.xml:2219
#, no-c-format
msgid "Not yet written."
msgstr ""

#. Tag: title
#: boot-installer.xml:2224
#, no-c-format
msgid "Booting OldWorld PowerMacs from MacOS"
msgstr ""

#. Tag: para
#: boot-installer.xml:2225
#, no-c-format
msgid ""
"If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to "
"boot into the installation system. Double click the <guiicon>BootX</guiicon> "
"application icon. Click on the <guibutton>Options</guibutton> button and "
"select <guilabel>Use Specified RAM Disk</guilabel>. This will give you the "
"chance to select the <filename>ramdisk.image.gz</filename> file. You may "
"need to select the <guilabel>No Video Driver</guilabel> checkbox, depending "
"on your hardware. Then click the <guibutton>Linux</guibutton> button to shut "
"down MacOS and launch the installer."
msgstr ""

#. Tag: title
#: boot-installer.xml:2243
#, no-c-format
msgid "Booting NewWorld Macs from OpenFirmware"
msgstr ""

#. Tag: para
#: boot-installer.xml:2244
#, no-c-format
msgid ""
"You will have already placed the <filename>vmlinux</filename>, "
"<filename>initrd.gz</filename>, <filename>yaboot</filename>, and "
"<filename>yaboot.conf</filename> files at the root level of your HFS "
"partition in <xref linkend=\"files-newworld\"/>. Restart the computer, and "
"immediately (during the chime) hold down the <keycap>Option</keycap>, "
"<keycap>Command (cloverleaf/Apple)</keycap>, <keycap>o</keycap>, and "
"<keycap>f</keycap> keys all together. After a few seconds you will be "
"presented with the Open Firmware prompt. At the prompt, type "
"<informalexample><screen>\n"
"0 &gt; boot hd:<replaceable>x</replaceable>,yaboot\n"
"</screen></informalexample> replacing <replaceable>x</replaceable> with the "
"partition number of the HFS partition where the kernel and yaboot files were "
"placed, followed by a &enterkey;. On some machines, you may need to use "
"<userinput>ide0:</userinput> instead of <userinput>hd:</userinput>. In a few "
"more seconds you will see a yaboot prompt <informalexample><screen>\n"
"boot:\n"
"</screen></informalexample> At yaboot's <prompt>boot:</prompt> prompt, type "
"either <userinput>install</userinput> or <userinput>install video=ofonly</"
"userinput> followed by a &enterkey;. The <userinput>video=ofonly</userinput> "
"argument is for maximum compatibility; you can try it if <userinput>install</"
"userinput> doesn't work. The Debian installation program should start."
msgstr ""

#. Tag: para
#: boot-installer.xml:2280
#, no-c-format
msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
msgstr ""

#. Tag: para
#: boot-installer.xml:2286
#, no-c-format
msgid ""
"Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/"
">. To boot a Macintosh system from a USB stick, you will need to use the "
"Open Firmware prompt, since Open Firmware does not search USB storage "
"devices by default. To get to the prompt, hold down "
"<keycombo><keycap>Command</keycap> <keycap>Option</keycap> <keycap>o</"
"keycap> <keycap>f</keycap></keycombo> all together while booting (see <xref "
"linkend=\"invoking-openfirmware\"/>)."
msgstr ""

#. Tag: para
#: boot-installer.xml:2298
#, no-c-format
msgid ""
"You will need to work out where the USB storage device appears in the device "
"tree, since at the moment <command>ofpath</command> cannot work that out "
"automatically. Type <userinput>dev / ls</userinput> and <userinput>devalias</"
"userinput> at the Open Firmware prompt to get a list of all known devices "
"and device aliases. On the author's system with various types of USB stick, "
"paths such as <filename>usb0/disk</filename>, <filename>usb0/hub/disk</"
"filename>, <filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and "
"<filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work."
msgstr ""

#. Tag: para
#: boot-installer.xml:2310
#, no-c-format
msgid ""
"Having worked out the device path, use a command like this to boot the "
"installer: <informalexample><screen>\n"
"boot <replaceable>usb0/disk</replaceable>:<replaceable>2</replaceable>,\\\\:"
"tbxi\n"
"</screen></informalexample> The <replaceable>2</replaceable> matches the "
"Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image "
"earlier, and the <userinput>,\\\\:tbxi</userinput> part instructs Open "
"Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. "
"<command>yaboot</command>) in the directory previously blessed with "
"<command>hattrib -b</command>."
msgstr ""

#. Tag: para
#: boot-installer.xml:2324
#, no-c-format
msgid ""
"The system should now boot up, and you should be presented with the "
"<prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, "
"or just hit &enterkey;."
msgstr ""

#. Tag: para
#: boot-installer.xml:2330
#, no-c-format
msgid ""
"This boot method is new, and may be difficult to get to work on some "
"NewWorld systems. If you have problems, please file an installation report, "
"as explained in <xref linkend=\"submit-bug\"/>."
msgstr ""

#. Tag: para
#: boot-installer.xml:2363
#, no-c-format
msgid "Currently, PReP and New World PowerMac systems support netbooting."
msgstr ""

#. Tag: para
#: boot-installer.xml:2367
#, no-c-format
msgid ""
"On machines with Open Firmware, such as NewWorld Power Macs, enter the boot "
"monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command "
"<command>boot enet:0</command>. PReP and CHRP boxes may have different ways "
"of addressing the network. On a PReP machine, you should try <userinput>boot "
"<replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>,"
"<replaceable>client_ipaddr</replaceable></userinput>."
msgstr ""

#. Tag: para
#: boot-installer.xml:2382
#, 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 ""

#. Tag: para
#: boot-installer.xml:2394
#, no-c-format
msgid ""
"To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it "
"in floppy drive after shutting the system down, and before pressing the "
"power-on button."
msgstr ""

#. Tag: para
#: boot-installer.xml:2400
#, 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 ""

#. Tag: para
#: boot-installer.xml:2407
#, no-c-format
msgid ""
"After booting, the <filename>root.bin</filename> floppy is requested. Insert "
"the root floppy and press &enterkey;. The installer program is automatically "
"launched after the root system has been loaded into memory."
msgstr ""

#. Tag: title
#: boot-installer.xml:2418
#, no-c-format
msgid "PowerPC Boot Parameters"
msgstr ""

#. Tag: para
#: boot-installer.xml:2419
#, no-c-format
msgid ""
"Many older Apple monitors used a 640x480 67Hz mode. If your video appears "
"skewed on an older Apple monitor, try appending the boot argument "
"<userinput>video=atyfb:vmode:6</userinput> , which will select that mode for "
"most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to "
"<userinput>video=aty128fb:vmode:6</userinput> ."
msgstr ""

#. Tag: para
#: boot-installer.xml:2459
#, no-c-format
msgid ""
"On machines with OpenBoot, simply enter the boot monitor on the machine "
"which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use "
"the command <userinput>boot net</userinput> to boot from a TFTP and RARP "
"server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:"
"dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server. Some older "
"OpenBoot revisions require using the device name, such as <userinput>boot le"
"()</userinput>; these probably don't support BOOTP nor DHCP."
msgstr ""

#. Tag: para
#: boot-installer.xml:2515
#, no-c-format
msgid ""
"Most OpenBoot versions support the <userinput>boot cdrom</userinput> command "
"which is simply an alias to boot from the SCSI device on ID 6 (or the "
"secondary master for IDE based systems). 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 ""

#. Tag: para
#: boot-installer.xml:2530
#, no-c-format
msgid ""
"To boot from floppy on a Sparc, use <informalexample><screen>\n"
"Stop-A -&gt; OpenBoot: \"boot floppy\"\n"
"</screen></informalexample> Be warned that the newer Sun4u (ultra) "
"architecture does not support floppy booting. A typical error message is "
"<computeroutput>Bad magic number in disk label - Can't open disk label "
"package</computeroutput>. 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 ""

#. Tag: para
#: boot-installer.xml:2542
#, 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 <ulink url=\"http://"
"sunsolve.sun.com\"></ulink>."
msgstr ""

#. Tag: para
#: boot-installer.xml:2549
#, no-c-format
msgid ""
"If you are booting from the floppy, and you see messages such as "
"<informalexample><screen>\n"
"Fatal error: Cannot read partition\n"
"Illegal or malformed device name\n"
"</screen></informalexample> then it is possible that floppy booting is "
"simply not supported on your machine."
msgstr ""

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

#. Tag: para
#: boot-installer.xml:2562
#, 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 <ulink url=\"&url-sun-"
"nvram-faq;\">Sun NVRAM FAQ</ulink> for more information."
msgstr ""

#. Tag: para
#: boot-installer.xml:2581
#, 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 ""

#. Tag: para
#: boot-installer.xml:2588
#, 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:2595
#, no-c-format
msgid ""
"Information on many boot parameters can be found in the <ulink url=\"http://"
"www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, "
"including tips for obscure hardware. This section contains only a sketch of "
"the most salient parameters. Some common gotchas are included below in <xref "
"linkend=\"boot-troubleshooting\"/>."
msgstr ""

#. Tag: para
#: boot-installer.xml:2604
#, no-c-format
msgid ""
"When the kernel boots, a message <informalexample><screen>\n"
"Memory:<replaceable>avail</replaceable>k/<replaceable>total</replaceable>k "
"available \n"
"</screen></informalexample> should be emitted early in the process. "
"<replaceable>total</replaceable> should match the total amount of RAM, in "
"kilobytes. If this doesn't match the actual amount of RAM you have "
"installed, you need to use the <userinput>mem=<replaceable>ram</"
"replaceable></userinput> parameter, where <replaceable>ram</replaceable> is "
"set to the amount of memory, suffixed with ``k'' for kilobytes, or ``m'' for "
"megabytes. For example, both <userinput>mem=65536k</userinput> and "
"<userinput>mem=64m</userinput> mean 64MB of RAM."
msgstr ""

#. Tag: para
#: boot-installer.xml:2620
#, no-c-format
msgid ""
"If you are booting with a serial console, generally the kernel will "
"autodetect this<phrase arch=\"mipsel\"> (although not on DECstations)</"
"phrase>. If you have a videocard (framebuffer) and a keyboard also attached "
"to the computer which you wish to boot via serial console, you may have to "
"pass the <userinput>console=<replaceable>device</replaceable></userinput> "
"argument to the kernel, where <replaceable>device</replaceable> is your "
"serial device, which is usually something like <filename>ttyS0</filename>."
msgstr ""

#. Tag: para
#: boot-installer.xml:2633
#, no-c-format
msgid ""
"For &arch-title; the serial devices are <filename>ttya</filename> or "
"<filename>ttyb</filename>. Alternatively, set the <envar>input-device</"
"envar> and <envar>output-device</envar> OpenPROM variables to "
"<filename>ttya</filename>."
msgstr ""

#. Tag: title
#: boot-installer.xml:2644
#, no-c-format
msgid "Debian Installer Parameters"
msgstr ""

#. Tag: para
#: boot-installer.xml:2645
#, no-c-format
msgid ""
"The installation system recognizes a few additional boot "
"parameters<footnote> <para> Note that the kernel accepts a maximum of 8 "
"command line options and 8 environment options (including any options added "
"by default for the installer). If these numbers are exceeded, 2.4 kernels "
"will drop any excess options and 2.6 kernels will panic. </para> </footnote> "
"which may be useful."
msgstr ""

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

#. Tag: para
#: boot-installer.xml:2665
#, no-c-format
msgid "This parameter sets the lowest priority of messages to be displayed."
msgstr ""

#. Tag: para
#: boot-installer.xml:2669
#, no-c-format
msgid ""
"The default installation uses <userinput>debconf/priority=high</userinput>. "
"This means that both high and critical priority messages are shown, but "
"medium and low priority messages are skipped. If problems are encountered, "
"the installer adjusts the priority as needed."
msgstr ""

#. Tag: para
#: boot-installer.xml:2676
#, no-c-format
msgid ""
"If you add <userinput>debconf/priority=medium</userinput> as boot parameter, "
"you will be shown the installation menu and gain more control over the "
"installation. When <userinput>debconf/priority=low</userinput> is used, all "
"messages are shown (this is equivalent to the <emphasis>expert</emphasis> "
"boot method). With <userinput>debconf/priority=critical</userinput>, the "
"installation system will display only critical messages and try to do the "
"right thing without fuss."
msgstr ""

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

#. Tag: para
#: boot-installer.xml:2691
#, no-c-format
msgid ""
"This boot parameter controls the type of user interface used for the "
"installer. The current possible parameter settings are: <itemizedlist> "
"<listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></"
"para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</"
"userinput></para> </listitem><listitem> "
"<para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </"
"listitem><listitem> <para><userinput>DEBIAN_FRONTEND=slang</userinput></"
"para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=ncurses</"
"userinput></para> </listitem><listitem> "
"<para><userinput>DEBIAN_FRONTEND=bogl</userinput></para> </"
"listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> "
"</listitem><listitem> <para><userinput>DEBIAN_FRONTEND=corba</userinput></"
"para> </listitem> </itemizedlist> The default front end is "
"<userinput>DEBIAN_FRONTEND=newt</userinput>. "
"<userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial "
"console installs. Generally only the <userinput>newt</userinput> frontend is "
"available on default install media, so this is not very useful right now."
msgstr ""

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

#. Tag: para
#: boot-installer.xml:2728
#, no-c-format
msgid ""
"Passing this boot parameter will cause the boot to be more verbosely logged."
msgstr ""

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

#. Tag: para
#: boot-installer.xml:2736
#, no-c-format
msgid "This is the default."
msgstr ""

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

#. Tag: para
#: boot-installer.xml:2741
#, no-c-format
msgid "More verbose than usual."
msgstr ""

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

#. Tag: para
#: boot-installer.xml:2746
#, no-c-format
msgid "Lots of debugging information."
msgstr ""

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

#. Tag: para
#: boot-installer.xml:2751
#, no-c-format
msgid ""
"Shells are run at various points in the boot process to allow detailed "
"debugging. Exit the shell to continue the boot."
msgstr ""

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

#. Tag: para
#: boot-installer.xml:2766
#, no-c-format
msgid ""
"The value of the parameter is the path to the device to load the Debian "
"installer from. For example, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</"
"userinput>"
msgstr ""

#. Tag: para
#: boot-installer.xml:2772
#, no-c-format
msgid ""
"The boot floppy, which normally scans all floppies and USB storage devices "
"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:2782
#, no-c-format
msgid "debian-installer/framebuffer"
msgstr ""

#. Tag: para
#: boot-installer.xml:2783
#, 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 <userinput>debian-installer/"
"framebuffer=false</userinput>. Problem symptoms are error messages about "
"bterm or bogl, a blank screen, or a freeze within a few minutes after "
"starting the install."
msgstr ""

#. Tag: para
#: boot-installer.xml:2792
#, no-c-format
msgid ""
"The <userinput>video=vga16:off</userinput> argument may also be used to "
"disable the framebuffer. Such problems have been reported on a Dell Inspiron "
"with Mobile Radeon card."
msgstr ""

#. Tag: para
#: boot-installer.xml:2798
#, no-c-format
msgid "Such problems have been reported on the Amiga 1200 and SE/30."
msgstr ""

#. Tag: para
#: boot-installer.xml:2802
#, no-c-format
msgid "Such problems have been reported on hppa."
msgstr ""

#. Tag: para
#: boot-installer.xml:2806
#, no-c-format
msgid ""
"Because of display problems on some systems, framebuffer support is "
"<emphasis>disabled by default</emphasis> for &arch-title;. This can result "
"in ugly display on systems that do properly support the framebuffer, like "
"those with ATI graphical cards. If you see display problems in the "
"installer, you can try booting with parameter <userinput>debian-installer/"
"framebuffer=true</userinput>."
msgstr ""

#. Tag: term
#: boot-installer.xml:2819
#, no-c-format
msgid "debian-installer/probe/usb"
msgstr ""

#. Tag: para
#: boot-installer.xml:2820
#, no-c-format
msgid ""
"Set to <userinput>false</userinput> to prevent probing for USB on boot, if "
"that causes problems."
msgstr ""

#. Tag: term
#: boot-installer.xml:2829
#, no-c-format
msgid "netcfg/disable_dhcp"
msgstr ""

#. Tag: para
#: boot-installer.xml:2830
#, 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 ""

#. Tag: para
#: boot-installer.xml:2837
#, no-c-format
msgid ""
"If you have a DHCP server on your local network, but want to avoid it "
"because e.g. it gives wrong answers, you can use the parameter "
"<userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the "
"network with DHCP and to enter the information manually."
msgstr ""

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

#. Tag: para
#: boot-installer.xml:2849
#, no-c-format
msgid ""
"Set to <userinput>false</userinput> to prevent starting PCMCIA services, if "
"that causes problems. Some laptops are well known for this misbehavior."
msgstr ""

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

#. Tag: para
#: boot-installer.xml:2860
#, no-c-format
msgid ""
"Specify the url to a preconfiguration file to download and use in automating "
"the install. See <xref linkend=\"automatic-install\"/>."
msgstr ""

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

#. Tag: para
#: boot-installer.xml:2870
#, no-c-format
msgid ""
"Specify the url to a preconfiguration file to load to automating the "
"install. See <xref linkend=\"automatic-install\"/>."
msgstr ""

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

#. Tag: para
#: boot-installer.xml:2880
#, 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 ""

#. Tag: para
#: boot-installer.xml:2889
#, no-c-format
msgid ""
"Set to <userinput>false</userinput> to disable automatic ejection, and be "
"aware that you may need to ensure that the system does not automatically "
"boot from the optical drive after the initial installation."
msgstr ""

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

#. Tag: para
#: boot-installer.xml:2901
#, no-c-format
msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;."
msgstr ""

#. Tag: title
#: boot-installer.xml:2918
#, no-c-format
msgid "Troubleshooting the Install Process"
msgstr ""

#. Tag: title
#: boot-installer.xml:2923
#, no-c-format
msgid "Floppy Disk Reliability"
msgstr ""

#. Tag: para
#: boot-installer.xml:2925
#, no-c-format
msgid ""
"The biggest problem for people installing Debian for the first time seems to "
"be floppy disk reliability."
msgstr ""

#. Tag: para
#: boot-installer.xml:2930
#, 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 ""

#. Tag: para
#: boot-installer.xml:2939
#, no-c-format
msgid ""
"If you are having the installation stall at a particular floppy, the first "
"thing you should do is re-download the floppy disk image and write it to a "
"<emphasis>different</emphasis> floppy. 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:2949
#, no-c-format