[SILENT_COMMIT] Update of POT and PO files for the manual

1 files changed, 231 insertions, 231 deletions

diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot
index c7e5570d9..43cda8d76 100644
--- a/po/pot/boot-installer.pot
+++ b/po/pot/boot-installer.pot
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2007-02-18 19:51+0000\n"
+"POT-Creation-Date: 2007-02-27 20:31+0000\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"
@@ -344,7 +344,7 @@ msgid "As on other architectures, you should install the newest available revisi
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:290 boot-installer.xml:1015 boot-installer.xml:1506 boot-installer.xml:2001 boot-installer.xml:2083 boot-installer.xml:2172 boot-installer.xml:2522 boot-installer.xml:2621
+#: boot-installer.xml:290 boot-installer.xml:1015 boot-installer.xml:1506 boot-installer.xml:2003 boot-installer.xml:2085 boot-installer.xml:2174 boot-installer.xml:2524 boot-installer.xml:2623
 #, no-c-format
 msgid "Booting with TFTP"
 msgstr ""
@@ -493,19 +493,19 @@ msgid "Booting from TFTP"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:457 boot-installer.xml:1021 boot-installer.xml:1524 boot-installer.xml:2007 boot-installer.xml:2528 boot-installer.xml:2627
+#: boot-installer.xml:457 boot-installer.xml:1021 boot-installer.xml:1524 boot-installer.xml:2009 boot-installer.xml:2530 boot-installer.xml:2629
 #, 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:462 boot-installer.xml:1026 boot-installer.xml:1529 boot-installer.xml:2012 boot-installer.xml:2533 boot-installer.xml:2632
+#: boot-installer.xml:462 boot-installer.xml:1026 boot-installer.xml:1529 boot-installer.xml:2014 boot-installer.xml:2535 boot-installer.xml:2634
 #, 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:467 boot-installer.xml:1031 boot-installer.xml:1534 boot-installer.xml:2017 boot-installer.xml:2538 boot-installer.xml:2637
+#: boot-installer.xml:467 boot-installer.xml:1031 boot-installer.xml:1534 boot-installer.xml:2019 boot-installer.xml:2540 boot-installer.xml:2639
 #, no-c-format
 msgid "The installation method to support network booting is described in <xref linkend=\"install-tftp\"/>."
 msgstr ""
@@ -574,25 +574,25 @@ msgid "Booting from CD-ROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:562 boot-installer.xml:732 boot-installer.xml:1143 boot-installer.xml:1964 boot-installer.xml:2310 boot-installer.xml:2665
+#: boot-installer.xml:562 boot-installer.xml:732 boot-installer.xml:1143 boot-installer.xml:1966 boot-installer.xml:2312 boot-installer.xml:2667
 #, 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=\"x86\"> 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:573 boot-installer.xml:743 boot-installer.xml:1154 boot-installer.xml:1975 boot-installer.xml:2321 boot-installer.xml:2676
+#: boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1154 boot-installer.xml:1977 boot-installer.xml:2323 boot-installer.xml:2678
 #, 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:581 boot-installer.xml:751 boot-installer.xml:1162 boot-installer.xml:1983 boot-installer.xml:2329 boot-installer.xml:2684
+#: boot-installer.xml:581 boot-installer.xml:751 boot-installer.xml:1162 boot-installer.xml:1985 boot-installer.xml:2331 boot-installer.xml:2686
 #, 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:589 boot-installer.xml:759 boot-installer.xml:1170 boot-installer.xml:1991 boot-installer.xml:2337 boot-installer.xml:2692
+#: boot-installer.xml:589 boot-installer.xml:759 boot-installer.xml:1170 boot-installer.xml:1993 boot-installer.xml:2339 boot-installer.xml:2694
 #, no-c-format
 msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
 msgstr ""
@@ -673,7 +673,7 @@ msgid "There is <ulink url=\"http://www.everbesthk.com/8-download/sercomm/firmwa
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:726 boot-installer.xml:1137 boot-installer.xml:1952 boot-installer.xml:2304 boot-installer.xml:2659
+#: boot-installer.xml:726 boot-installer.xml:1137 boot-installer.xml:1954 boot-installer.xml:2306 boot-installer.xml:2661
 #, no-c-format
 msgid "Booting from a CD-ROM"
 msgstr ""
@@ -753,13 +753,13 @@ msgid "Let's assume you have prepared everything from <xref linkend=\"boot-dev-s
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:957 boot-installer.xml:2064 boot-installer.xml:2567 boot-installer.xml:2710
+#: boot-installer.xml:957 boot-installer.xml:2066 boot-installer.xml:2569 boot-installer.xml:2712
 #, no-c-format
 msgid "Booting from Floppies"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:958 boot-installer.xml:2575
+#: boot-installer.xml:958 boot-installer.xml:2577
 #, 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 ""
@@ -1291,13 +1291,13 @@ msgid "Booting from a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1779 boot-installer.xml:2383
+#: boot-installer.xml:1779 boot-installer.xml:2385
 #, 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:1785 boot-installer.xml:2389
+#: boot-installer.xml:1785 boot-installer.xml:2391
 #, 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 ""
@@ -1365,107 +1365,107 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:1880
 #, 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."
+msgid "Macs require the <command>Penguin</command> bootloader, which can be downloaded from <ulink url=\"&url-m68k-mac;\">the Linux/mac68k sourceforge.net project</ulink>. If you do not have the tools to handle a <command>Stuffit</command> archive, you can put it on a MacOS-formatted floppy using a second GNU/Linux machine of any architecture and the <command>hmount</command>, <command>hcopy</command>, and <command>humount</command> tools from the <classname>hfsutils</classname> suite."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1889
+#: boot-installer.xml:1891
 #, 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:1904
+#: boot-installer.xml:1906
 #, 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:1913
+#: boot-installer.xml:1915
 #, 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:1920
+#: boot-installer.xml:1922
 #, 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:1935
+#: boot-installer.xml:1937
 #, no-c-format
 msgid "Booting from Q40/Q60"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1937
+#: boot-installer.xml:1939
 #, no-c-format
 msgid "FIXME"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1941
+#: boot-installer.xml:1943
 #, 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:1953
+#: boot-installer.xml:1955
 #, no-c-format
 msgid "Currently, the only &arch-title; subarchitecture that supports CD-ROM booting is the BVME6000."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2025
+#: boot-installer.xml:2027
 #, 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:2036
+#: boot-installer.xml:2038
 #, no-c-format
 msgid "type <screen>i6000 &enterkey;</screen> to install a BVME4000/6000"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2041
+#: boot-installer.xml:2043
 #, no-c-format
 msgid "type <screen>i162 &enterkey;</screen> to install an MVME162"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2046
+#: boot-installer.xml:2048
 #, no-c-format
 msgid "type <screen>i167 &enterkey;</screen> to install an MVME166/167"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2053
+#: boot-installer.xml:2055
 #, 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:2065
+#: boot-installer.xml:2067
 #, no-c-format
 msgid "For most &arch-title; architectures, booting from a local filesystem is the recommended method."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2070
+#: boot-installer.xml:2072
 #, 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:2086 boot-installer.xml:2133
+#: boot-installer.xml:2088 boot-installer.xml:2135
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2087
+#: boot-installer.xml:2089
 #, no-c-format
 msgid ""
       "After entering the command monitor use <informalexample><screen>\n"
@@ -1476,13 +1476,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2106 boot-installer.xml:2155 boot-installer.xml:2210 boot-installer.xml:2249
+#: boot-installer.xml:2108 boot-installer.xml:2157 boot-installer.xml:2212 boot-installer.xml:2251
 #, no-c-format
 msgid "Broadcom BCM91250A and BCM91480B TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2107 boot-installer.xml:2211
+#: boot-installer.xml:2109 boot-installer.xml:2213
 #, no-c-format
 msgid ""
       "On the Broadcom BCM91250A and BCM91480B evaluation boards, you have to load the SiByl boot loader via TFTP which will then load and start the Debian installer. In most cases, you will first obtain an IP address via DHCP but it is also possible to configure a static address. In order to use DHCP, you can enter the following command on the CFE prompt: <informalexample><screen>\n"
@@ -1493,19 +1493,19 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2130 boot-installer.xml:2234 boot-installer.xml:2768
+#: boot-installer.xml:2132 boot-installer.xml:2236 boot-installer.xml:2770
 #, no-c-format
 msgid "Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2134
+#: boot-installer.xml:2136
 #, no-c-format
 msgid "On SGI machines you can append boot parameters to the <command>bootp():</command> command in the command monitor."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2139
+#: boot-installer.xml:2141
 #, 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"
@@ -1514,139 +1514,139 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:2149
+#: boot-installer.xml:2151
 #, no-c-format
 msgid "bootp(): append=\"root=/dev/sda1\""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2156 boot-installer.xml:2250
+#: boot-installer.xml:2158 boot-installer.xml:2252
 #, 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:2175 boot-installer.xml:2237
+#: boot-installer.xml:2177 boot-installer.xml:2239
 #, no-c-format
 msgid "Cobalt TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2176
+#: boot-installer.xml:2178
 #, no-c-format
 msgid "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to install an NFS server and put the installer files in <filename>/nfsroot</filename>. When you boot your Cobalt, you have to press the left and the right cursor buttons at the same time and the machine will boot via the network from NFS. It will then display several options on the display. There are the following two installation methods:"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2186
+#: boot-installer.xml:2188
 #, no-c-format
 msgid "Via SSH (default): In this case, the installer will configure the network via DHCP and start an SSH server. It will then display a random password and other login information (such as the IP address) on the Cobalt LCD. When you connect to the machine with an SSH client you can start with the installation."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2195
+#: boot-installer.xml:2197
 #, no-c-format
 msgid "Via serial console: Using a null modem cable, you can connect to the serial port of your Cobalt machine (using 115200 bps) and perform the installation this way. This option is not available on Qube 2700 (Qube1) machines since they have no serial port."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2238
+#: boot-installer.xml:2240
 #, no-c-format
 msgid "You cannot pass any boot parameters directly. Instead, you have to edit the <filename>/nfsroot/default.colo</filename> file on the NFS server and add your parameters to the <replaceable>args</replaceable> variable."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2266
+#: boot-installer.xml:2268
 #, no-c-format
 msgid "s390 Limitations"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2267
+#: boot-installer.xml:2269
 #, 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:2272
+#: boot-installer.xml:2274
 #, no-c-format
 msgid "The booting process starts with a network setup that prompts you for several network parameters. If the setup is successful, you will login to the system by starting an ssh session which will launch the standard installation system."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2283
+#: boot-installer.xml:2285
 #, no-c-format
 msgid "s390 Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2284
+#: boot-installer.xml:2286
 #, no-c-format
 msgid "On S/390 you can append boot parameters in the parm file. This file can either be in ASCII or EBCDIC format. A sample parm file <filename>parmfile.debian</filename> is provided with the installation images."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2344
+#: boot-installer.xml:2346
 #, no-c-format
 msgid "Currently, the only &arch-title; subarchitectures that support CD-ROM booting are PReP (though not all systems) and New World PowerMacs. On PowerMacs, hold the <keycap>c</keycap> key, or else the combination of <keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Shift</keycap>, and <keycap>Delete</keycap> keys together while booting to boot from the CD-ROM."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2353
+#: boot-installer.xml:2355
 #, 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:2362
+#: boot-installer.xml:2364
 #, 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:2371
+#: boot-installer.xml:2373
 #, no-c-format
 msgid "0 &gt; boot cd:,\\install\\yaboot"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2377
+#: boot-installer.xml:2379
 #, no-c-format
 msgid "Booting from Hard Disk"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2398
+#: boot-installer.xml:2400
 #, no-c-format
 msgid "Booting CHRP from OpenFirmware"
 msgstr ""
 
 #. Tag: emphasis
-#: boot-installer.xml:2402
+#: boot-installer.xml:2404
 #, no-c-format
 msgid "Not yet written."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2407
+#: boot-installer.xml:2409
 #, no-c-format
 msgid "Booting OldWorld PowerMacs from MacOS"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2408
+#: boot-installer.xml:2410
 #, 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:2426
+#: boot-installer.xml:2428
 #, no-c-format
 msgid "Booting NewWorld Macs from OpenFirmware"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2427
+#: boot-installer.xml:2429
 #, 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"
@@ -1657,31 +1657,31 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2462
+#: boot-installer.xml:2464
 #, no-c-format
 msgid "Booting from USB memory stick"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2463
+#: boot-installer.xml:2465
 #, no-c-format
 msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2469
+#: boot-installer.xml:2471
 #, 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:2481
+#: boot-installer.xml:2483
 #, 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:2493
+#: boot-installer.xml:2495
 #, no-c-format
 msgid ""
       "Having worked out the device path, use a command like this to boot the installer: <informalexample><screen>\n"
@@ -1690,85 +1690,85 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2507
+#: boot-installer.xml:2509
 #, 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:2513
+#: boot-installer.xml:2515
 #, 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:2546
+#: boot-installer.xml:2548
 #, no-c-format
 msgid "Currently, PReP and New World PowerMac systems support netbooting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2550
+#: boot-installer.xml:2552
 #, 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 net:<replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>,<replaceable>client_ipaddr</replaceable></userinput>. On some PReP systems (e.g. Motorola PowerStack machines) the command <userinput>help boot</userinput> may give a description of syntax and available options."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2568
+#: boot-installer.xml:2570
 #, 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:2580
+#: boot-installer.xml:2582
 #, 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:2586
+#: boot-installer.xml:2588
 #, 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:2593
+#: boot-installer.xml:2595
 #, 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:2604
+#: boot-installer.xml:2606
 #, no-c-format
 msgid "PowerPC Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2605
+#: boot-installer.xml:2607
 #, 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:2645
+#: boot-installer.xml:2647
 #, 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."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2699
+#: boot-installer.xml:2701
 #, no-c-format
 msgid "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command which is simply an alias to boot from the SCSI device on ID 6 (or the secondary master for IDE based systems)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2711
+#: boot-installer.xml:2713
 #, no-c-format
 msgid "Floppy images are currently only available for sparc32, but, for technical reasons, not for official releases. (The reason is that they can only be built as root, which is not supported by our build daemons.) Look under <quote>daily built images</quote> on the <ulink url=\"&url-d-i;\">Debian Installer project website</ulink> for links to floppy images for sparc32."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2720
+#: boot-installer.xml:2722
 #, no-c-format
 msgid ""
       "To boot from floppy on a Sparc, use <informalexample><screen>\n"
@@ -1777,13 +1777,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2730
+#: boot-installer.xml:2732
 #, 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:2737
+#: boot-installer.xml:2739
 #, no-c-format
 msgid ""
       "If you are booting from the floppy, and you see messages such as <informalexample><screen>\n"
@@ -1793,37 +1793,37 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2749
+#: boot-installer.xml:2751
 #, no-c-format
 msgid "IDPROM Messages"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2750
+#: boot-installer.xml:2752
 #, no-c-format
 msgid "If you cannot boot because you get messages about a problem with <quote>IDPROM</quote>, then it's possible that your NVRAM battery, which holds configuration information for you firmware, has run out. See the <ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink> for more information."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2769
+#: boot-installer.xml:2771
 #, 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:2776
+#: boot-installer.xml:2778
 #, 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:2783
+#: boot-installer.xml:2785
 #, 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:2792
+#: boot-installer.xml:2794
 #, no-c-format
 msgid ""
       "When the kernel boots, a message <informalexample><screen>\n"
@@ -1832,451 +1832,451 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2808
+#: boot-installer.xml:2810
 #, 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:2821
+#: boot-installer.xml:2823
 #, 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:2832
+#: boot-installer.xml:2834
 #, no-c-format
 msgid "Debian Installer Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2833
+#: boot-installer.xml:2835
 #, no-c-format
 msgid "The installation system recognizes a few additional boot parameters<footnote> <para> With current kernels (2.6.9 or newer) you can use 32 command line options and 32 environment options. If these numbers are exceeded, the kernel will panic. </para> </footnote> which may be useful."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2846
+#: boot-installer.xml:2848
 #, no-c-format
 msgid "A number of parameters have a <quote>short form</quote> that helps avoid the limitations of the kernel command line options and makes entering the parameters easier. If a parameter has a short form, it will be listed in brackets behind the (normal) long form. Examples in this manual will normally use the short form too."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2858
+#: boot-installer.xml:2860
 #, no-c-format
 msgid "debconf/priority (priority)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2859
+#: boot-installer.xml:2861
 #, no-c-format
 msgid "This parameter sets the lowest priority of messages to be displayed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2863
+#: boot-installer.xml:2865
 #, no-c-format
 msgid "The default installation uses <userinput>priority=high</userinput>. This means that both high and critical priority messages are shown, but medium and low priority messages are skipped. If problems are encountered, the installer adjusts the priority as needed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2870
+#: boot-installer.xml:2872
 #, no-c-format
 msgid "If you add <userinput>priority=medium</userinput> as boot parameter, you will be shown the installation menu and gain more control over the installation. When <userinput>priority=low</userinput> is used, all messages are shown (this is equivalent to the <emphasis>expert</emphasis> boot method). With <userinput>priority=critical</userinput>, the installation system will display only critical messages and try to do the right thing without fuss."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2884
+#: boot-installer.xml:2886
 #, no-c-format
 msgid "DEBIAN_FRONTEND"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2885
+#: boot-installer.xml:2887
 #, no-c-format
 msgid "This boot parameter controls the type of user interface used for the installer. The current possible parameter settings are: <itemizedlist> <listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> </listitem> </itemizedlist> The default frontend is <userinput>DEBIAN_FRONTEND=newt</userinput>. <userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial console installs. Generally, only the <userinput>newt</userinput> frontend is available on default install media. On architectures that support it, the graphical installer uses the <userinput>gtk</userinput> frontend."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2914
+#: boot-installer.xml:2916
 #, no-c-format
 msgid "BOOT_DEBUG"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2915
+#: boot-installer.xml:2917
 #, no-c-format
 msgid "Setting this boot parameter to 2 will cause the installer's boot process to be verbosely logged. Setting it to 3 makes debug shells available at strategic points in the boot process. (Exit the shells to continue the boot process.)"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2924
+#: boot-installer.xml:2926
 #, no-c-format
 msgid "BOOT_DEBUG=0"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2925
+#: boot-installer.xml:2927
 #, no-c-format
 msgid "This is the default."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2929
+#: boot-installer.xml:2931
 #, no-c-format
 msgid "BOOT_DEBUG=1"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2930
+#: boot-installer.xml:2932
 #, no-c-format
 msgid "More verbose than usual."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2934
+#: boot-installer.xml:2936
 #, no-c-format
 msgid "BOOT_DEBUG=2"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2935
+#: boot-installer.xml:2937
 #, no-c-format
 msgid "Lots of debugging information."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2939
+#: boot-installer.xml:2941
 #, no-c-format
 msgid "BOOT_DEBUG=3"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2940
+#: boot-installer.xml:2942
 #, 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:2954
+#: boot-installer.xml:2956
 #, no-c-format
 msgid "INSTALL_MEDIA_DEV"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2955
+#: boot-installer.xml:2957
 #, 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:2961
+#: boot-installer.xml:2963
 #, no-c-format
 msgid "The boot floppy, which normally scans all floppies it can to find the root floppy, can be overridden by this parameter to only look at the one device."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2971
+#: boot-installer.xml:2973
 #, no-c-format
 msgid "debian-installer/framebuffer (fb)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2972
+#: boot-installer.xml:2974
 #, 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>fb=false</userinput>. Problem symptoms are error messages about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2981
+#: boot-installer.xml:2983
 #, no-c-format
 msgid "The <userinput>video=vga16:off</userinput> argument may also be used to disable the kernel's use of the framebuffer. Such problems have been reported on a Dell Inspiron with Mobile Radeon card."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2987
+#: boot-installer.xml:2989
 #, no-c-format
 msgid "Such problems have been reported on the Amiga 1200 and SE/30."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2991
+#: boot-installer.xml:2993
 #, no-c-format
 msgid "Such problems have been reported on hppa."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2995
+#: boot-installer.xml:2997
 #, no-c-format
 msgid "Because of display problems on some systems, framebuffer support is <emphasis>disabled by default</emphasis> for &arch-title;. This can result in ugly display on systems that do properly support the framebuffer, like those with ATI graphical cards. If you see display problems in the installer, you can try booting with parameter <userinput>debian-installer/framebuffer=true</userinput> or <userinput>fb=true</userinput> for short."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3009
+#: boot-installer.xml:3011
 #, no-c-format
 msgid "debian-installer/theme (theme)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3010
+#: boot-installer.xml:3012
 #, no-c-format
 msgid "A theme determines how the user interface of the installer looks (colors, icons, etc.). What themes are available differs per frontend. Currently both the newt and gtk frontends only have a <quote>dark</quote> theme that was designed for visually impaired users. Set the theme by booting with <userinput>theme=<replaceable>dark</replaceable></userinput>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3022
+#: boot-installer.xml:3024
 #, no-c-format
 msgid "debian-installer/probe/usb"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3023
+#: boot-installer.xml:3025
 #, 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:3032 boot-installer.xml:3223
+#: boot-installer.xml:3034 boot-installer.xml:3225
 #, no-c-format
 msgid "netcfg/disable_dhcp"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3033
+#: boot-installer.xml:3035
 #, 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:3040
+#: boot-installer.xml:3042
 #, 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:3051
+#: boot-installer.xml:3053
 #, no-c-format
 msgid "hw-detect/start_pcmcia"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3052
+#: boot-installer.xml:3054
 #, 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:3062
+#: boot-installer.xml:3064
 #, no-c-format
 msgid "preseed/url (url)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3063
+#: boot-installer.xml:3065
 #, no-c-format
 msgid "Specify the url to a preconfiguration file to download and use for automating the install. See <xref linkend=\"automatic-install\"/>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3072
+#: boot-installer.xml:3074
 #, no-c-format
 msgid "preseed/file (file)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3073
+#: boot-installer.xml:3075
 #, no-c-format
 msgid "Specify the path to a preconfiguration file to load for automating the install. See <xref linkend=\"automatic-install\"/>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3082
+#: boot-installer.xml:3084
 #, no-c-format
 msgid "preseed/interactive"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3083
+#: boot-installer.xml:3085
 #, no-c-format
 msgid "Set to <userinput>true</userinput> to display questions even if they have been preseeded. Can be useful for testing or debugging a preconfiguration file. Note that this will have no effect on parameters that are passed as boot parameters, but for those a special syntax can be used. See <xref linkend=\"preseed-seenflag\"/> for details."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3095
+#: boot-installer.xml:3097
 #, no-c-format
 msgid "auto-install/enable (auto)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3096
+#: boot-installer.xml:3098
 #, no-c-format
 msgid "Delay questions that are normally asked before preseeding is possible until after the network is configured. See <xref linkend=\"preseed-auto\"/> for details about using this to automate installs."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3107
+#: boot-installer.xml:3109
 #, no-c-format
 msgid "cdrom-detect/eject"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3108
+#: boot-installer.xml:3110
 #, 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:3117
+#: boot-installer.xml:3119
 #, 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:3128
+#: boot-installer.xml:3130
 #, no-c-format
 msgid "debian-installer/allow_unauthenticated"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3129
+#: boot-installer.xml:3131
 #, no-c-format
 msgid "By default the installer requires that repositories be authenticated using a known gpg key. Set to <userinput>true</userinput> to disable that authentication. <emphasis role=\"bold\">Warning: insecure, not recommended.</emphasis>"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3140
+#: boot-installer.xml:3142
 #, no-c-format
 msgid "ramdisk_size"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3141
+#: boot-installer.xml:3143
 #, no-c-format
 msgid "This parameter should already be set to a correct value where needed; set it only it you see errors during the boot that indicate the ramdisk could not be loaded completely. The value is in kB."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3151
+#: boot-installer.xml:3153
 #, no-c-format
 msgid "mouse/left"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3152
+#: boot-installer.xml:3154
 #, no-c-format
 msgid "For the gtk frontend (graphical installer), users can switch the mouse to left-handed operation by setting this parameter to <userinput>true</userinput>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3161
+#: boot-installer.xml:3163
 #, no-c-format
 msgid "directfb/hw-accel"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3162
+#: boot-installer.xml:3164
 #, no-c-format
 msgid "For the gtk frontend (graphical installer), hardware acceleration in directfb is disabled by default. To enable it, set this parameter to <userinput>true</userinput> when booting the installer."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3172
+#: boot-installer.xml:3174
 #, no-c-format
 msgid "rescue/enable"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3173
+#: boot-installer.xml:3175
 #, no-c-format
 msgid "Set to <userinput>true</userinput> to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3184
+#: boot-installer.xml:3186
 #, no-c-format
 msgid "Using boot parameters to answer questions"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3185
+#: boot-installer.xml:3187
 #, no-c-format
 msgid "With some exceptions, a value can be set at the boot prompt for any question asked during the installation, though this is only really useful in specific cases. General instructions how to do this can be found in <xref linkend=\"preseed-bootparms\"/>. Some specific examples are listed below."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3197
+#: boot-installer.xml:3199
 #, no-c-format
 msgid "debian-installer/locale (locale)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3198
+#: boot-installer.xml:3200
 #, no-c-format
 msgid "Can be used to set both the language and country for the installation. This will only work if the locale is supported in Debian. For example, use <userinput>locale=de_CH</userinput> to select German as language and Switzerland as country."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3209
+#: boot-installer.xml:3211
 #, no-c-format
 msgid "anna/choose_modules (modules)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3210
+#: boot-installer.xml:3212
 #, no-c-format
 msgid "Can be used to automatically load installer components that are not loaded by default. Examples of optional components that may be useful are <classname>openssh-client-udeb</classname> (so you can use <command>scp</command> during the installation)<phrase arch=\"not-s390\"> and <classname>ppp-udeb</classname> (see <xref linkend=\"pppoe\"/>)</phrase>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3224
+#: boot-installer.xml:3226
 #, no-c-format
 msgid "Set to <userinput>true</userinput> if you want to disable DHCP and instead force static network configuration."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3233
+#: boot-installer.xml:3235
 #, no-c-format
 msgid "mirror/protocol (protocol)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3234
+#: boot-installer.xml:3236
 #, no-c-format
 msgid "By default the installer will use the http protocol to download files from Debian mirrors and changing that to ftp is not possible during installations at normal priority. By setting this parameter to <userinput>ftp</userinput>, you can force the installer to use that protocol instead. Note that you cannot select an ftp mirror from a list, you have to enter the hostname manually."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3247
+#: boot-installer.xml:3249
 #, no-c-format
 msgid "tasksel:tasksel/first (tasks)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3248
+#: boot-installer.xml:3250
 #, no-c-format
 msgid "Can be used to select tasks that are not available from the interactive task list, such as the <literal>kde-desktop</literal> task. See <xref linkend=\"pkgsel\"/> for additional information."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3262
+#: boot-installer.xml:3264
 #, no-c-format
 msgid "Passing parameters to kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3263
+#: boot-installer.xml:3265
 #, no-c-format
 msgid "If drivers are compiled into the kernel, you can pass parameters to them as described in the kernel documentation. However, if drivers are compiled as modules and because kernel modules are loaded a bit differently during an installation than when booting an installed system, it is not possible to pass parameters to modules as you would normally do. Instead, you need to use a special syntax recognized by the installer which will then make sure that the parameters are saved in the proper configuration files and will thus be used when the modules are actually loaded. The parameters will also be propagated automatically to the configuration for the installed system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3276
+#: boot-installer.xml:3278
 #, no-c-format
 msgid "Note that it is now quite rare that parameters need to be passed to modules. In most cases the kernel will be able to probe the hardware present in a system and set good defaults that way. However, in some situations it may still be needed to set parameters manually."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3283
+#: boot-installer.xml:3285
 #, no-c-format
 msgid ""
       "The syntax to use to set parameters for modules is: <informalexample><screen>\n"
@@ -2285,133 +2285,133 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:3293
+#: boot-installer.xml:3295
 #, no-c-format
 msgid "3c509.xcvr=3 3c509.irq=10"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3299
+#: boot-installer.xml:3301
 #, no-c-format
 msgid "Blacklisting kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3300
+#: boot-installer.xml:3302
 #, no-c-format
 msgid "Sometimes it may be necessary to blacklist a module to prevent it from being loaded automatically by the kernel and udev. One reason could be that a particular module causes problems with your hardware. The kernel also sometimes lists two different drivers for the same device. This can cause the device to not work correctly if the drivers conflict or if the wrong driver is loaded first."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3309
+#: boot-installer.xml:3311
 #, no-c-format
 msgid "You can blacklist a module using the following syntax: <userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>. This will cause the module to be blacklisted in <filename>/etc/modprobe.d/blacklist.local</filename> both during the installation and for the installed system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3317
+#: boot-installer.xml:3319
 #, no-c-format
 msgid "Note that a module may still be loaded by the installation system itself. You can prevent that from happening by running the installation in expert mode and unselecting the module from the list of modules displayed during the hardware detection phases."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3334
+#: boot-installer.xml:3336
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3339
+#: boot-installer.xml:3341
 #, no-c-format
 msgid "CD-ROM Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3340
+#: boot-installer.xml:3342
 #, no-c-format
 msgid "Sometimes, especially with older CD-ROM drives, the installer may fail to boot from a CD-ROM. The installer may also &mdash; even after booting successfully from CD-ROM &mdash; fail to recognize the CD-ROM or return errors while reading from it during the installation."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3347
+#: boot-installer.xml:3349
 #, no-c-format
 msgid "There are a many different possible causes for these problems. We can only list some common issues and provide general suggestions on how to deal with them. The rest is up to you."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3353
+#: boot-installer.xml:3355
 #, no-c-format
 msgid "There are two very simple things that you should try first."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3358
+#: boot-installer.xml:3360
 #, no-c-format
 msgid "If the CD-ROM does not boot, check that it was inserted correctly and that it is not dirty."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3364
+#: boot-installer.xml:3366
 #, no-c-format
 msgid "If the installer fails to recognize a CD-ROM, try just running the option <menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </menuchoice> a second time. Some DMA related issues with older CD-ROM drives are known to be resolved in this way."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3374
+#: boot-installer.xml:3376
 #, no-c-format
 msgid "If this does not work, then try the suggestions in the subsections below. Most, but not all, suggestions discussed there are valid for both CD-ROM and DVD, but we'll use the term CD-ROM for simplicity."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3380
+#: boot-installer.xml:3382
 #, no-c-format
 msgid "If you cannot get the installation working from CD-ROM, try one of the other installation methods that are available."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3388
+#: boot-installer.xml:3390
 #, no-c-format
 msgid "Common issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3391
+#: boot-installer.xml:3393
 #, no-c-format
 msgid "Some older CD-ROM drives do not support reading from discs that were burned at high speeds using a modern CD writer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3397
+#: boot-installer.xml:3399
 #, no-c-format
 msgid "If your system boots correctly from the CD-ROM, it does not necessarily mean that Linux also supports the CD-ROM (or, more correctly, the controller that your CD-ROM drive is connected to)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3404
+#: boot-installer.xml:3406
 #, no-c-format
 msgid "Some older CD-ROM drives do not work correctly if <quote>direct memory access</quote> (DMA) is enabled."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3415
+#: boot-installer.xml:3417
 #, no-c-format
 msgid "How to investigate and maybe solve issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3416
+#: boot-installer.xml:3418
 #, no-c-format
 msgid "If the CD-ROM fails to boot, try the suggestions listed below."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3421
+#: boot-installer.xml:3423
 #, no-c-format
 msgid "Check that your BIOS actually supports booting from CD-ROM (older systems possibly don't) and that your CD-ROM drive supports the media you are using."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3427
+#: boot-installer.xml:3429
 #, no-c-format
 msgid ""
       "If you downloaded an iso image, check that the md5sum of that image matches the one listed for the image in the <filename>MD5SUMS</filename> file that should be present in the same location as where you downloaded the image from. <informalexample><screen>\n"
@@ -2421,7 +2421,7 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:3440
+#: boot-installer.xml:3442
 #, no-c-format
 msgid ""
       "$ dd if=/dev/cdrom | \\\n"
@@ -2434,19 +2434,19 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3445
+#: boot-installer.xml:3447
 #, no-c-format
 msgid "If, after the installer has been booted successfully, the CD-ROM is not detected, sometimes simply trying again may solve the problem. If you have more than one CD-ROM drive, try changing the CD-ROM to the other drive. If that does not work or if the CD-ROM is recognized but there are errors when reading from it, try the suggestions listed below. Some basic knowledge of Linux is required for this. To execute any of the commands, you should first switch to the second virtual console (VT2) and activate the shell there."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3457
+#: boot-installer.xml:3459
 #, no-c-format
 msgid "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> (use <command>nano</command> as editor) to check for any specific error messages. After that, also check the output of <command>dmesg</command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3464
+#: boot-installer.xml:3466
 #, no-c-format
 msgid ""
       "Check in the output of <command>dmesg</command> if your CD-ROM drive was recognized. You should see something like (the lines do not necessarily have to be consecutive): <informalexample><screen>\n"
@@ -2459,13 +2459,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3478
+#: boot-installer.xml:3480
 #, no-c-format
 msgid "Check that there is a device node for your CD-ROM drive under <filename>/dev/</filename>. In the example above, this would be <filename>/dev/hdc</filename>. There should also be a <filename>/dev/cdroms/cdrom0</filename>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3486
+#: boot-installer.xml:3488
 #, no-c-format
 msgid ""
       "Use the <command>mount</command> command to check if the CD-ROM is already mounted; if not, try mounting it manually: <informalexample><screen>\n"
@@ -2474,7 +2474,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3496
+#: boot-installer.xml:3498
 #, no-c-format
 msgid ""
       "Check if DMA is currently enabled: <informalexample><screen>\n"
@@ -2487,157 +2487,157 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3511
+#: boot-installer.xml:3513
 #, no-c-format
 msgid "If there are any problems during the installation, try checking the integrity of the CD-ROM using the option near the bottom of the installer's main menu. This option can also be used as a general test if the CD-ROM can be read reliably."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3526
+#: boot-installer.xml:3528
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3528
+#: boot-installer.xml:3530
 #, no-c-format
 msgid "The biggest problem for people using floppy disks to install Debian seems to be floppy disk reliability."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3533
+#: boot-installer.xml:3535
 #, 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:3542
+#: boot-installer.xml:3544
 #, no-c-format
 msgid "If you are having the installation stall at a particular floppy, the first thing you should do is write the image to a <emphasis>different</emphasis> floppy and see if that solves the problem. Simply reformatting the old floppy may not be sufficient, even if it appears that the floppy was reformatted and written with no errors. It is sometimes useful to try writing the floppy on a different system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3551
+#: boot-installer.xml:3553
 #, no-c-format
 msgid "One user reports he had to write the images to floppy <emphasis>three</emphasis> times before one worked, and then everything was fine with the third floppy."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3557
+#: boot-installer.xml:3559
 #, no-c-format
 msgid "Normally you should not have to download a floppy image again, but if you are experiencing problems it is always useful to verify that the images were downloaded correctly by verifying their md5sums."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3563
+#: boot-installer.xml:3565
 #, no-c-format
 msgid "Other users have reported that simply rebooting a few times with the same floppy in the floppy drive can lead to a successful boot. This is all due to buggy hardware or firmware floppy drivers."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3572
+#: boot-installer.xml:3574
 #, no-c-format
 msgid "Boot Configuration"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3574
+#: boot-installer.xml:3576
 #, no-c-format
 msgid "If you have problems and the kernel hangs during the boot process, doesn't recognize peripherals you actually have, or drives are not recognized properly, the first thing to check is the boot parameters, as discussed in <xref linkend=\"boot-parms\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3581
+#: boot-installer.xml:3583
 #, no-c-format
 msgid "Often, problems can be solved by removing add-ons and peripherals, and then trying booting again. <phrase arch=\"x86\">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3587
+#: boot-installer.xml:3589
 #, no-c-format
 msgid "If you have a large amount of memory installed in your machine, more than 512M, and the installer hangs when booting the kernel, you may need to include a boot argument to limit the amount of memory the kernel sees, such as <userinput>mem=512m</userinput>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3598 boot-installer.xml:3683
+#: boot-installer.xml:3600 boot-installer.xml:3685
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3599
+#: boot-installer.xml:3601
 #, no-c-format
 msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3604
+#: boot-installer.xml:3606
 #, no-c-format
 msgid "Some systems have floppies with <quote>inverted DCLs</quote>. If you receive errors reading from the floppy, even when you know the floppy is good, try the parameter <userinput>floppy=thinkpad</userinput>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3610
+#: boot-installer.xml:3612
 #, 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:3619
+#: boot-installer.xml:3621
 #, 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:3626
+#: boot-installer.xml:3628
 #, no-c-format
 msgid "If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter <userinput>fb=false video=vga16:off</userinput> to disable the framebuffer console. Only a reduced set of languages will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3640
+#: boot-installer.xml:3642
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3641
+#: boot-installer.xml:3643
 #, 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:3651
+#: boot-installer.xml:3653
 #, 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:3668
+#: boot-installer.xml:3670
 #, no-c-format
 msgid "System Freeze while Loading USB Modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3669
+#: boot-installer.xml:3671
 #, 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: para
-#: boot-installer.xml:3684
+#: boot-installer.xml:3686
 #, no-c-format
 msgid "There are some common installation problems that are worth mentioning."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3690
+#: boot-installer.xml:3692
 #, no-c-format
 msgid "Misdirected video output"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3691
+#: boot-installer.xml:3693
 #, no-c-format
 msgid ""
       "It is fairly common for &arch-title; to have two video cards in one machine, for example an ATI card and a Sun Creator 3D. In some cases, this may result in the video output getting misdirected soon after the system boots. In typical cases, the display will only show: <informalexample><screen>\n"
@@ -2647,85 +2647,85 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3705
+#: boot-installer.xml:3707
 #, no-c-format
 msgid "Note that you may also have to manually add this parameter to the silo configuration (edit <filename>/target/etc/silo.conf</filename> before rebooting) and, if you installed X11, modify the video driver in <filename>/etc/X11/xorg.conf</filename>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3716
+#: boot-installer.xml:3718
 #, no-c-format
 msgid "Failure to Boot or Install from CD-ROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3717
+#: boot-installer.xml:3719
 #, no-c-format
 msgid "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if they do boot, there may be inexplicable failures during the installation. Most problems have been reported with SunBlade systems."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3723
+#: boot-installer.xml:3725
 #, no-c-format
 msgid "We recommend to install such systems by netbooting the installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3732
+#: boot-installer.xml:3734
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3734
+#: boot-installer.xml:3736
 #, no-c-format
 msgid "During the boot sequence, you may see many messages in the form <computeroutput>can't find <replaceable>something</replaceable></computeroutput>, or <computeroutput><replaceable>something</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>something</replaceable></computeroutput>, or even <computeroutput>this driver release depends on <replaceable>something</replaceable></computeroutput>. Most of these messages are harmless. You see them because the kernel for the installation system is built to run on computers with many different peripheral devices. Obviously, no one computer will have every possible peripheral device, so the operating system may emit a few complaints while it looks for peripherals you don't own. You may also see the system pause for a while. This happens when it is waiting for a device to respond, and that device is not present on your system. If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later (see <xref linkend=\"kernel-baking\"/>)."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3759
+#: boot-installer.xml:3761
 #, no-c-format
 msgid "Reporting Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3760
+#: boot-installer.xml:3762
 #, no-c-format
 msgid "If you get through the initial boot phase but cannot complete the install, the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them using a web browser. This information may provide clues as to what went wrong and how to fix it. If you are submitting a bug report, you may want to attach this information to the bug report."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3771
+#: boot-installer.xml:3773
 #, no-c-format
 msgid "Other pertinent installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/installer/</filename> after the computer has been booted into the installed system."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3782
+#: boot-installer.xml:3784
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3783
+#: boot-installer.xml:3785
 #, no-c-format
 msgid "If you still have problems, please submit an installation report. We also encourage installation reports to be sent even if the installation is successful, so that we can get as much information as possible on the largest number of hardware configurations."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3790
+#: boot-installer.xml:3792
 #, no-c-format
 msgid "Note that your installation report will be published in the Debian Bug Tracking System (BTS) and forwarded to a public mailing list. Make sure that you use an e-mail address that you do not mind being made public."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3796
+#: boot-installer.xml:3798
 #, no-c-format
 msgid "If you have a working Debian system, the easiest way to send an installation report is to install the <classname>installation-report</classname> and <classname>reportbug</classname> packages (<command>aptitude install installation-report reportbug</command>), configure <classname>reportbug</classname> as explained in <xref linkend=\"mail-outgoing\"/>, and run the command <command>reportbug installation-reports</command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3806
+#: boot-installer.xml:3808
 #, no-c-format
 msgid ""
       "Alternatively you can use this template when filling out installation reports, and file the report as a bug report against the <classname>installation-reports</classname> pseudo package, by sending it to <email>submit@bugs.debian.org</email>. <informalexample><screen>\n"