Regenarate pot files.

4 files changed, 825 insertions, 781 deletions

diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot
index ef9c72778..9a4dd11f0 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: 2012-07-01 14:46+0000\n"
+"POT-Creation-Date: 2012-07-20 14:12+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"
@@ -45,19 +45,19 @@ msgid "Booting from TFTP"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:43 boot-installer.xml:583 boot-installer.xml:1125 boot-installer.xml:1626 boot-installer.xml:1735
+#: boot-installer.xml:43 boot-installer.xml:584 boot-installer.xml:1126 boot-installer.xml:1627 boot-installer.xml:1736
 #, 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:48 boot-installer.xml:588 boot-installer.xml:1130 boot-installer.xml:1631 boot-installer.xml:1740
+#: boot-installer.xml:48 boot-installer.xml:589 boot-installer.xml:1131 boot-installer.xml:1632 boot-installer.xml:1741
 #, 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:53 boot-installer.xml:593 boot-installer.xml:1135 boot-installer.xml:1636 boot-installer.xml:1745
+#: boot-installer.xml:53 boot-installer.xml:594 boot-installer.xml:1136 boot-installer.xml:1637 boot-installer.xml:1746
 #, no-c-format
 msgid "The installation method to support network booting is described in <xref linkend=\"install-tftp\"/>."
 msgstr ""
@@ -69,25 +69,25 @@ msgid "Booting from CD-ROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:744 boot-installer.xml:1402 boot-installer.xml:1774
+#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:745 boot-installer.xml:1403 boot-installer.xml:1775
 #, 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:81 boot-installer.xml:259 boot-installer.xml:755 boot-installer.xml:1413 boot-installer.xml:1785
+#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:756 boot-installer.xml:1414 boot-installer.xml:1786
 #, 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:89 boot-installer.xml:267 boot-installer.xml:763 boot-installer.xml:1421 boot-installer.xml:1793
+#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:764 boot-installer.xml:1422 boot-installer.xml:1794
 #, 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:97 boot-installer.xml:275 boot-installer.xml:771 boot-installer.xml:1429 boot-installer.xml:1801
+#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:772 boot-installer.xml:1430 boot-installer.xml:1802
 #, no-c-format
 msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
 msgstr ""
@@ -216,7 +216,7 @@ msgid "The installer will now start as usual."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:242 boot-installer.xml:738 boot-installer.xml:1396 boot-installer.xml:1768
+#: boot-installer.xml:242 boot-installer.xml:739 boot-installer.xml:1397 boot-installer.xml:1769
 #, no-c-format
 msgid "Booting from a CD-ROM"
 msgstr ""
@@ -384,119 +384,119 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:506
 #, 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;."
+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 unless you have used the flexible way to build the stick and not enabled it, you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:519 boot-installer.xml:1675
+#: boot-installer.xml:520 boot-installer.xml:1676
 #, no-c-format
 msgid "Booting from Floppies"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:520 boot-installer.xml:1683
+#: boot-installer.xml:521 boot-installer.xml:1684
 #, 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:527
+#: boot-installer.xml:528
 #, 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:533
+#: boot-installer.xml:534
 #, 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>install root=/dev/hdc</userinput> at the boot prompt."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:543
+#: boot-installer.xml:544
 #, 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 <quote>hard</quote> 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:552
+#: boot-installer.xml:553
 #, 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:558
+#: boot-installer.xml:559
 #, 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:567
+#: boot-installer.xml:568
 #, 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: title
-#: boot-installer.xml:577 boot-installer.xml:1107 boot-installer.xml:1248 boot-installer.xml:1302 boot-installer.xml:1620 boot-installer.xml:1729
+#: boot-installer.xml:578 boot-installer.xml:1108 boot-installer.xml:1249 boot-installer.xml:1303 boot-installer.xml:1621 boot-installer.xml:1730
 #, no-c-format
 msgid "Booting with TFTP"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:601
+#: boot-installer.xml:602
 #, no-c-format
 msgid "There are various ways to do a TFTP boot on i386."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:607
+#: boot-installer.xml:608
 #, no-c-format
 msgid "NIC or Motherboard that support PXE"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:608
+#: boot-installer.xml:609
 #, 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-implementation of TFTP boot. If so, you may be able to configure your BIOS to boot from the network."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:619
+#: boot-installer.xml:620
 #, no-c-format
 msgid "NIC with Network BootROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:620
+#: boot-installer.xml:621
 #, no-c-format
 msgid "It could be that your Network Interface Card provides TFTP boot functionality."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:625
+#: boot-installer.xml:626
 #, 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:633
+#: boot-installer.xml:634
 #, no-c-format
 msgid "Etherboot"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:634
+#: boot-installer.xml:635
 #, 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:644
+#: boot-installer.xml:645
 #, no-c-format
 msgid "The Boot Screen"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:645
+#: boot-installer.xml:646
 #, no-c-format
 msgid ""
       "When the installer boots, you should be presented with a friendly graphical screen showing the &debian; logo and a menu: <informalexample><screen>\n"
@@ -513,25 +513,25 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:657
+#: boot-installer.xml:658
 #, no-c-format
 msgid "For a normal installation, select either the <quote>Install</quote> or the <quote>Graphical install</quote> entry &mdash; using either the arrow keys on your keyboard or by typing the first (highlighted) letter, the <quote>Install</quote> entry is already selected by default &mdash; and press &enterkey; to boot the installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:665
+#: boot-installer.xml:666
 #, no-c-format
 msgid "The <quote>Advanced options</quote> entry gives access to a second menu that allows to boot the installer in expert mode, in rescue mode and for automated installs."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:671
+#: boot-installer.xml:672
 #, no-c-format
 msgid "If you wish or need to add any boot parameters for either the installer or the kernel, press &tabkey;. This will display the default boot command for the selected menu entry and allow to add additional options. The help screens (see below) list some common possible options. Press &enterkey; to boot the installer with your options; pressing &escapekey; will return you to the boot menu and undo any changes you made."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:680
+#: boot-installer.xml:681
 #, no-c-format
 msgid ""
       "Choosing the <quote>Help</quote> entry will result in the first help screen being displayed which gives an overview of all available help screens. Note that it is not possible to return to the boot menu after the help screens have been displayed. However, the F3 and F4 help screens list commands that are equivalent to the boot methods listed in the menu. All help screens have a boot prompt at which the boot command can be typed: <informalexample><screen>\n"
@@ -540,259 +540,259 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:699
+#: boot-installer.xml:700
 #, no-c-format
 msgid "The keyboard is assumed to have a default American English layout at this point. This means that if your keyboard has a different (language-specific) layout, the characters that appear on the screen may be different from what you'd expect when you type parameters. Wikipedia has a <ulink url=\"&url-us-keymap;\">schema of the US keyboard layout</ulink> which can be used as a reference to find the correct keys to use."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:709
+#: boot-installer.xml:710
 #, no-c-format
 msgid "If you are using a system that has the BIOS configured to use serial console, you may not be able to see the initial graphical splash screen upon booting the installer; you may even not see the boot menu. The same can happen if you are installing the system via a remote management device that provides a text interface to the VGA console. Examples of these devices include the text console of Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's <quote>Integrated Remote Assistant</quote> (IRA)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:719
+#: boot-installer.xml:720
 #, no-c-format
 msgid "To bypass the graphical boot screen you can either blindly press &escapekey; to get a text boot prompt, or (equally blindly) press <quote>H</quote> followed by &enterkey; to select the <quote>Help</quote> option described above. After that your keystrokes should be echoed at the prompt. To prevent the installer from using the framebuffer for the rest of the installation, you will also want to add <userinput>vga=normal fb=false</userinput> to the boot prompt, as described in the help text."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:779
+#: boot-installer.xml:780
 #, no-c-format
 msgid "CD Contents"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:781
+#: boot-installer.xml:782
 #, 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:797
+#: boot-installer.xml:798
 #, 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:813
+#: boot-installer.xml:814
 #, 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:822
+#: boot-installer.xml:823
 #, 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:834
+#: boot-installer.xml:835
 #, 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:853
+#: boot-installer.xml:854
 #, no-c-format
 msgid "IMPORTANT"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:854
+#: boot-installer.xml:855
 #, 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:866
+#: boot-installer.xml:867
 #, no-c-format
 msgid "Option 1: Booting from the Boot Option Maintenance Menu"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:873
+#: boot-installer.xml:874
 #, 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:879
+#: boot-installer.xml:880
 #, 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:885
+#: boot-installer.xml:886
 #, 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:896
+#: boot-installer.xml:897
 #, 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:907
+#: boot-installer.xml:908
 #, 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:919
+#: boot-installer.xml:920
 #, 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:929
+#: boot-installer.xml:930
 #, no-c-format
 msgid "Option 2: Booting from the EFI Shell"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:930
+#: boot-installer.xml:931
 #, 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:941
+#: boot-installer.xml:942
 #, 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:947
+#: boot-installer.xml:948
 #, 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:961
+#: boot-installer.xml:962
 #, 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:968
+#: boot-installer.xml:969
 #, 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:975
+#: boot-installer.xml:976
 #, 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:982
+#: boot-installer.xml:983
 #, 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:996
+#: boot-installer.xml:997
 #, no-c-format
 msgid "Installing using a Serial Console"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:998
+#: boot-installer.xml:999
 #, 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:1009
+#: boot-installer.xml:1010
 #, 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:1016
+#: boot-installer.xml:1017
 #, 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:1027
+#: boot-installer.xml:1028
 #, 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:1036
+#: boot-installer.xml:1037
 #, 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:1045
+#: boot-installer.xml:1046
 #, no-c-format
 msgid "Selecting the Boot Kernel and Options"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1047
+#: boot-installer.xml:1048
 #, 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:1059
+#: boot-installer.xml:1060
 #, 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:1077
+#: boot-installer.xml:1078
 #, 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:1082
+#: boot-installer.xml:1083
 #, 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:1089
+#: boot-installer.xml:1090
 #, 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:1098 boot-installer.xml:1234
+#: boot-installer.xml:1099 boot-installer.xml:1235
 #, 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:1109
+#: boot-installer.xml:1110
 #, no-c-format
 msgid "Booting an IA-64 system from the network is similar to a CD boot. The only difference is how the installation kernel is loaded. The EFI Boot Manager can load and start programs from a server on the network. Once the installation kernel is loaded and starts, the system install will proceed through the same steps as the CD install with the exception that the packages of the base install will be loaded from the network rather than the CD drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1143
+#: boot-installer.xml:1144
 #, no-c-format
 msgid "Network booting an IA-64 system requires two architecture-specific actions. On the boot server, DHCP and TFTP must be configured to deliver <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:1154
+#: boot-installer.xml:1155
 #, no-c-format
 msgid "Configuring the Server"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1155
+#: boot-installer.xml:1156
 #, no-c-format
 msgid ""
       "A suitable TFTP entry for network booting an IA-64 system looks something like this: <informalexample><screen>\n"
@@ -805,13 +805,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1165
+#: boot-installer.xml:1166
 #, 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:1175
+#: boot-installer.xml:1176
 #, no-c-format
 msgid ""
       "# cd /var/lib/tftp\n"
@@ -823,37 +823,37 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1175
+#: boot-installer.xml:1176
 #, 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:1192
+#: boot-installer.xml:1193
 #, no-c-format
 msgid "Configuring the Client"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1193
+#: boot-installer.xml:1194
 #, 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:1225
+#: boot-installer.xml:1226
 #, 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: title
-#: boot-installer.xml:1251 boot-installer.xml:1275
+#: boot-installer.xml:1252 boot-installer.xml:1276
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1252
+#: boot-installer.xml:1253
 #, no-c-format
 msgid ""
       "After entering the command monitor use <informalexample><screen>\n"
@@ -864,19 +864,19 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1272 boot-installer.xml:1339 boot-installer.xml:1973
+#: boot-installer.xml:1273 boot-installer.xml:1340 boot-installer.xml:1974
 #, no-c-format
 msgid "Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1276
+#: boot-installer.xml:1277
 #, 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:1281
+#: boot-installer.xml:1282
 #, 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"
@@ -885,79 +885,79 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1291
+#: boot-installer.xml:1292
 #, no-c-format
 msgid "bootp(): append=\"root=/dev/sda1\""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1305 boot-installer.xml:1342
+#: boot-installer.xml:1306 boot-installer.xml:1343
 #, no-c-format
 msgid "Cobalt TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1306
+#: boot-installer.xml:1307
 #, 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:1316
+#: boot-installer.xml:1317
 #, 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:1325
+#: boot-installer.xml:1326
 #, 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."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1343
+#: boot-installer.xml:1344
 #, 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:1358
+#: boot-installer.xml:1359
 #, no-c-format
 msgid "s390 Limitations"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1359
+#: boot-installer.xml:1360
 #, 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:1364
+#: boot-installer.xml:1365
 #, 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:1375
+#: boot-installer.xml:1376
 #, no-c-format
 msgid "s390 Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1376
+#: boot-installer.xml:1377
 #, 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:1436
+#: boot-installer.xml:1437
 #, no-c-format
 msgid "Currently, the only &arch-title; subarchitectures that support CD-ROM booting are PReP/CHRP (though not all systems) and New World PowerMacs. On PowerMacs, hold the <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 factory default CD/DVD drive."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1445
+#: boot-installer.xml:1446
 #, no-c-format
 msgid ""
       "To boot a PowerMac from an external Firewire CD/DVD drive invoke Open Firmware prompt first (see <xref linkend=\"invoking-openfirmware\"/>), then type <informalexample><screen>\n"
@@ -966,67 +966,67 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1456
+#: boot-installer.xml:1457
 #, no-c-format
 msgid "0 &gt; boot cd:,\\install\\yaboot"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1458
+#: boot-installer.xml:1459
 #, 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:1467
+#: boot-installer.xml:1468
 #, no-c-format
 msgid "To boot &debian; CD/DVD on Pegasos II machine, hold <keycap>Esc</keycap> key immediately after pressing the power-on button, when SmartFirmware prompt appears, type"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1473
+#: boot-installer.xml:1474
 #, no-c-format
 msgid "boot cd install/pegasos"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1479
+#: boot-installer.xml:1480
 #, no-c-format
 msgid "Booting from Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1485
+#: boot-installer.xml:1486
 #, 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:1491
+#: boot-installer.xml:1492
 #, no-c-format
 msgid "To boot the installer from hard disk, you will have already completed downloading and placing the needed files as described in <xref linkend=\"boot-drive-files\"/>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1511
+#: boot-installer.xml:1512
 #, no-c-format
 msgid "Booting OldWorld PowerMacs from MacOS"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1512
+#: boot-installer.xml:1513
 #, 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:1530
+#: boot-installer.xml:1531
 #, no-c-format
 msgid "Booting NewWorld Macs from OpenFirmware"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1531
+#: boot-installer.xml:1532
 #, 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\"/>. You will now have to boot into OpenFirmware (see <xref linkend=\"invoking-openfirmware\"/>). At the prompt, type <informalexample><screen>\n"
@@ -1037,31 +1037,31 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1563
+#: boot-installer.xml:1564
 #, no-c-format
 msgid "Booting from USB memory stick"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1564
+#: boot-installer.xml:1565
 #, no-c-format
 msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1570
+#: boot-installer.xml:1571
 #, 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. See <xref linkend=\"invoking-openfirmware\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1579
+#: boot-installer.xml:1580
 #, 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:1591
+#: boot-installer.xml:1592
 #, no-c-format
 msgid ""
       "Having worked out the device path, use a command like this to boot the installer: <informalexample><screen>\n"
@@ -1070,25 +1070,25 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1605
+#: boot-installer.xml:1606
 #, 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:1611
+#: boot-installer.xml:1612
 #, 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:1644
+#: boot-installer.xml:1645
 #, no-c-format
 msgid "Currently, PReP and New World PowerMac systems support netbooting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1648
+#: boot-installer.xml:1649
 #, 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 <informalexample><screen>\n"
@@ -1101,193 +1101,193 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1676
+#: boot-installer.xml:1677
 #, 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:1688
+#: boot-installer.xml:1689
 #, 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:1694
+#: boot-installer.xml:1695
 #, 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:1701
+#: boot-installer.xml:1702
 #, 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:1712
+#: boot-installer.xml:1713
 #, no-c-format
 msgid "PowerPC Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1713
+#: boot-installer.xml:1714
 #, 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:1753
+#: boot-installer.xml:1754
 #, 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. You can pass extra boot parameters to &d-i; at the end of the <userinput>boot</userinput> command."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1808
+#: boot-installer.xml:1809
 #, 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: title
-#: boot-installer.xml:1817
+#: boot-installer.xml:1818
 #, no-c-format
 msgid "IDPROM Messages"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1818
+#: boot-installer.xml:1819
 #, 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: title
-#: boot-installer.xml:1837
+#: boot-installer.xml:1838
 #, no-c-format
 msgid "Accessibility"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1838
+#: boot-installer.xml:1839
 #, no-c-format
 msgid "Some users may need specific support because of e.g. some visual impairment. <phrase arch=\"ia64;powerpc;x86\">USB braille displays are detected automatically (not serial displays connected via a serial-to-USB converter), but most other</phrase> <phrase arch=\"arm;hppa;mips;mipsel;sparc\">Most</phrase> accessibility features have to be enabled manually. <phrase arch=\"x86\">On machines that support it, the boot menu emits a beep when it is ready to receive keystrokes.</phrase> Some boot parameters can <phrase arch=\"x86\">then</phrase> be appended to enable accessibility features<phrase arch=\"x86\"> (see also <xref linkend=\"boot-screen\"/>)</phrase>. Note that on most architectures the boot loader interprets your keyboard as a QWERTY keyboard."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1858
+#: boot-installer.xml:1859
 #, no-c-format
 msgid "USB Braille Displays"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1859
+#: boot-installer.xml:1860
 #, no-c-format
 msgid "USB braille displays should be automatically detected. A textual version of the installer will then be automatically selected, and support for the braille display will be automatically installed on the target system. You can thus just press &enterkey; at the boot menu. Once <classname>brltty</classname> is started, you can choose a braille table by entering the preference menu. Documentation on key bindings for braille devices is available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> website</ulink>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1874
+#: boot-installer.xml:1875
 #, no-c-format
 msgid "Serial Braille Displays"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1875
+#: boot-installer.xml:1876
 #, no-c-format
 msgid "Serial braille displays cannot safely be automatically detected (since that may damage some of them). You thus need to append the <userinput>brltty=<replaceable>driver</replaceable>,<replaceable>port</replaceable>,<replaceable>table</replaceable></userinput> boot parameter to tell <classname>brltty</classname> which driver it should use. <replaceable>driver</replaceable> should be replaced by the two-letter driver code for your terminal (see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>). <replaceable>port</replaceable> should be replaced by the name of the serial port the display is connected to, <userinput>ttyS0</userinput> is the default, <userinput>ttyUSB0</userinput> can be typically used when using a serial-to-USB converter. <replaceable>table</replaceable> is the name of the braille table to be used (see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>); the English table is the default. Note that the table can be changed later by entering the preference menu. Documentation on key bindings for braille devices is available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> website</ulink>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1897 boot-installer.xml:2872
+#: boot-installer.xml:1898 boot-installer.xml:2873
 #, no-c-format
 msgid "Software Speech Synthesis"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1898
+#: boot-installer.xml:1899
 #, no-c-format
 msgid "Support for software speech synthesis can be activated by selecting it in the boot menu by typing <userinput>s</userinput> &enterkey;. The first question (language) is spoken in english, and the remainder of installation is spoken in the selected language (if available in <classname>espeak</classname>)."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1909
+#: boot-installer.xml:1910
 #, no-c-format
 msgid "Hardware Speech Synthesis"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1910
+#: boot-installer.xml:1911
 #, no-c-format
 msgid "Support for hardware speech synthesis devices is available only alongside support for graphical installer. You thus need to select a <quote>Graphical install</quote> entry in the boot menu."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1916
+#: boot-installer.xml:1917
 #, no-c-format
 msgid "Hardware speech synthesis devices cannot be automatically detected. You thus need to append the <userinput>speakup.synth=<replaceable>driver</replaceable></userinput> boot parameter to tell <classname>speakup</classname> which driver it should use. <replaceable>driver</replaceable> should be replaced by the driver code for your device (see <ulink url=\"&url-speakup-driver-codes;\">driver code list</ulink>). The textual version of the installer will then be automatically selected, and support for the speech synthesis device will be automatically installed on the target system."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1931
+#: boot-installer.xml:1932
 #, no-c-format
 msgid "Board Devices"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1932
+#: boot-installer.xml:1933
 #, no-c-format
 msgid "Some accessibility devices are actual boards that are plugged inside the machine and that read text directly from the video memory. To get them to work framebuffer support must be disabled by using the <userinput arch=\"x86\">vga=normal</userinput> <userinput>fb=false</userinput> boot parameter. This will however reduce the number of available languages."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1940
+#: boot-installer.xml:1941
 #, no-c-format
 msgid "If desired a textual version of the bootloader can be activated before adding the boot parameter by typing <userinput>h</userinput> &enterkey;."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1948
+#: boot-installer.xml:1949
 #, no-c-format
 msgid "High-Contrast Theme"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1949
+#: boot-installer.xml:1950
 #, no-c-format
 msgid "For users with low vision, the installer can use a high-contrast theme that makes it more readable. To enable it, append the <userinput>theme=dark</userinput> boot parameter."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1958
+#: boot-installer.xml:1959
 #, no-c-format
 msgid "Preseeding"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1959
+#: boot-installer.xml:1960
 #, no-c-format
 msgid "Alternatively, &debian; can be installed completely automatically by using preseeding. This is documented in <xref linkend=\"appendix-preseed\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1974
+#: boot-installer.xml:1975
 #, 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:1981
+#: boot-installer.xml:1982
 #, 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:1988
+#: boot-installer.xml:1989
 #, 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:1997
+#: boot-installer.xml:1998
 #, no-c-format
 msgid ""
       "When the kernel boots, a message <informalexample><screen>\n"
@@ -1296,511 +1296,511 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2013
+#: boot-installer.xml:2014
 #, no-c-format
 msgid "If you are booting with a serial console, generally the kernel will autodetect this. If you have a videocard (framebuffer) and a keyboard also attached to the computer which you wish to boot via serial console, you may have to pass the <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><footnote> <para> In order to ensure the terminal type used by the installer matches your terminal emulator, the parameter <userinput>TERM=<replaceable>type</replaceable></userinput> can be added. Note that the installer only supports the following terminal types: <literal>linux</literal>, <literal>bterm</literal>, <literal>ansi</literal>, <literal>vt102</literal> and <literal>dumb</literal>. The default for serial console in &d-i; is <userinput>vt102</userinput>. </para> </footnote>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2037
+#: boot-installer.xml:2038
 #, 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:2048
+#: boot-installer.xml:2049
 #, no-c-format
 msgid "&debian; Installer Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2049
+#: boot-installer.xml:2050
 #, 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:2062
+#: boot-installer.xml:2063
 #, 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:2074
+#: boot-installer.xml:2075
 #, no-c-format
 msgid "debconf/priority (priority)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2075
+#: boot-installer.xml:2076
 #, no-c-format
 msgid "This parameter sets the lowest priority of messages to be displayed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2079
+#: boot-installer.xml:2080
 #, 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:2086
+#: boot-installer.xml:2087
 #, 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:2100
+#: boot-installer.xml:2101
 #, no-c-format
 msgid "DEBIAN_FRONTEND"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2101
+#: boot-installer.xml:2102
 #, 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. Some specialized types of install media may only offer a limited selection of frontends, but the <userinput>newt</userinput> and <userinput>text</userinput> frontends are available on most default install media. On architectures that support it, the graphical installer uses the <userinput>gtk</userinput> frontend."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2132
+#: boot-installer.xml:2133
 #, no-c-format
 msgid "BOOT_DEBUG"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2133
+#: boot-installer.xml:2134
 #, 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:2142
+#: boot-installer.xml:2143
 #, no-c-format
 msgid "BOOT_DEBUG=0"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2143
+#: boot-installer.xml:2144
 #, no-c-format
 msgid "This is the default."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2147
+#: boot-installer.xml:2148
 #, no-c-format
 msgid "BOOT_DEBUG=1"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2148
+#: boot-installer.xml:2149
 #, no-c-format
 msgid "More verbose than usual."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2152
+#: boot-installer.xml:2153
 #, no-c-format
 msgid "BOOT_DEBUG=2"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2153
+#: boot-installer.xml:2154
 #, no-c-format
 msgid "Lots of debugging information."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2157
+#: boot-installer.xml:2158
 #, no-c-format
 msgid "BOOT_DEBUG=3"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2158
+#: boot-installer.xml:2159
 #, 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:2172
+#: boot-installer.xml:2173
 #, no-c-format
 msgid "INSTALL_MEDIA_DEV"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2173
+#: boot-installer.xml:2174
 #, 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:2179
+#: boot-installer.xml:2180
 #, 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:2190
+#: boot-installer.xml:2191
 #, no-c-format
 msgid "log_host"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2191
+#: boot-installer.xml:2192
 #, no-c-format
 msgid "log_port"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2192
+#: boot-installer.xml:2193
 #, no-c-format
 msgid "Causes the installer to send log messages to a remote syslog on the specified host and port as well as to a local file. If not specified, the port defaults to the standard syslog port 514."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2203
+#: boot-installer.xml:2204
 #, no-c-format
 msgid "lowmem"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2204
+#: boot-installer.xml:2205
 #, no-c-format
 msgid "Can be used to force the installer to a lowmem level higher than the one the installer sets by default based on available memory. Possible values are 1 and 2. See also <xref linkend=\"lowmem\"/>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2214
+#: boot-installer.xml:2215
 #, no-c-format
 msgid "noshell"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2215
+#: boot-installer.xml:2216
 #, no-c-format
 msgid "Prevents the installer from offering interactive shells on tty2 and tty3. Useful for unattended installations where physical security is limited."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2224
+#: boot-installer.xml:2225
 #, no-c-format
 msgid "debian-installer/framebuffer (fb)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2225
+#: boot-installer.xml:2226
 #, no-c-format
 msgid "Some architectures use the kernel framebuffer to offer installation in a number of languages. If framebuffer causes a problem on your system you can disable the feature using the parameter <userinput arch=\"x86\">vga=normal</userinput> <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:2234
+#: boot-installer.xml:2235
 #, no-c-format
 msgid "Such problems have been reported on hppa."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2238
+#: boot-installer.xml:2239
 #, 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:2252
+#: boot-installer.xml:2253
 #, no-c-format
 msgid "debian-installer/theme (theme)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2253
+#: boot-installer.xml:2254
 #, 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:2265 boot-installer.xml:2498
+#: boot-installer.xml:2266 boot-installer.xml:2499
 #, no-c-format
 msgid "netcfg/disable_dhcp"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2266
+#: boot-installer.xml:2267
 #, 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:2273
+#: boot-installer.xml:2274
 #, 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:2284
+#: boot-installer.xml:2285
 #, no-c-format
 msgid "hw-detect/start_pcmcia"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2285
+#: boot-installer.xml:2286
 #, 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:2295
+#: boot-installer.xml:2296
 #, no-c-format
 msgid "disk-detect/dmraid/enable (dmraid)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2296
+#: boot-installer.xml:2297
 #, no-c-format
 msgid "Set to <userinput>true</userinput> to enable support for Serial ATA RAID (also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. Note that this support is currently experimental. Additional information can be found on the <ulink url=\"&url-d-i-wiki;\">&debian; Installer Wiki</ulink>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2307
+#: boot-installer.xml:2308
 #, no-c-format
 msgid "preseed/url (url)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2308
+#: boot-installer.xml:2309
 #, 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:2317
+#: boot-installer.xml:2318
 #, no-c-format
 msgid "preseed/file (file)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2318
+#: boot-installer.xml:2319
 #, 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:2327
+#: boot-installer.xml:2328
 #, no-c-format
 msgid "preseed/interactive"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2328
+#: boot-installer.xml:2329
 #, 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:2340
+#: boot-installer.xml:2341
 #, no-c-format
 msgid "auto-install/enable (auto)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2341
+#: boot-installer.xml:2342
 #, 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:2352
+#: boot-installer.xml:2353
 #, no-c-format
 msgid "finish-install/keep-consoles"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2353
+#: boot-installer.xml:2354
 #, no-c-format
 msgid "During installations from serial or management console, the regular virtual consoles (VT1 to VT6) are normally disabled in <filename>/etc/inittab</filename>. Set to <userinput>true</userinput> to prevent this."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2364
+#: boot-installer.xml:2365
 #, no-c-format
 msgid "cdrom-detect/eject"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2365
+#: boot-installer.xml:2366
 #, 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:2374
+#: boot-installer.xml:2375
 #, 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:2385
+#: boot-installer.xml:2386
 #, no-c-format
 msgid "base-installer/install-recommends (recommends)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2386
+#: boot-installer.xml:2387
 #, no-c-format
 msgid "By setting this option to <userinput>false</userinput>, the package management system will be configured to not automatically install <quote>Recommends</quote>, both during the installation and for the installed system. See also <xref linkend=\"di-install-base\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2393
+#: boot-installer.xml:2394
 #, no-c-format
 msgid "Note that this option allows to have a leaner system, but can also result in features being missing that you might normally expect to be available. You may have to manually install some of the recommended packages to obtain the full functionality you want. This option should therefore only be used by very experienced users."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2405
+#: boot-installer.xml:2406
 #, no-c-format
 msgid "debian-installer/allow_unauthenticated"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2406
+#: boot-installer.xml:2407
 #, 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:2417
+#: boot-installer.xml:2418
 #, no-c-format
 msgid "ramdisk_size"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2418
+#: boot-installer.xml:2419
 #, 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:2428
+#: boot-installer.xml:2429
 #, no-c-format
 msgid "rescue/enable"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2429
+#: boot-installer.xml:2430
 #, 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:2442
+#: boot-installer.xml:2443
 #, no-c-format
 msgid "Using boot parameters to answer questions"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2443
+#: boot-installer.xml:2444
 #, 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:2455
+#: boot-installer.xml:2456
 #, no-c-format
 msgid "debian-installer/language (language)"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2456
+#: boot-installer.xml:2457
 #, no-c-format
 msgid "debian-installer/country (country)"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2457
+#: boot-installer.xml:2458
 #, no-c-format
 msgid "debian-installer/locale (locale)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2458
+#: boot-installer.xml:2459
 #, no-c-format
 msgid "There are two ways to specify the language, country and locale to use for the installation and the installed system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2463
+#: boot-installer.xml:2464
 #, no-c-format
 msgid "The first and easiest is to pass only the parameter <literal>locale</literal>. Language and country will then be derived from its value. You can for example use <userinput>locale=de_CH</userinput> to select German as language and Switzerland as country (<literal>de_CH.UTF-8</literal> will be set as default locale for the installed system). Limitation is that not all possible combinations of language, country and locale can be achieved this way."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2472
+#: boot-installer.xml:2473
 #, no-c-format
 msgid "The second, more flexible option is to specify <literal>language</literal> and <literal>country</literal> separately. In this case <literal>locale</literal> can optionally be added to specify a specific default locale for the installed system. Example: <userinput>language=en country=DE locale=en_GB.UTF-8</userinput>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2484
+#: boot-installer.xml:2485
 #, no-c-format
 msgid "anna/choose_modules (modules)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2485
+#: boot-installer.xml:2486
 #, 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:2499
+#: boot-installer.xml:2500
 #, 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:2508
+#: boot-installer.xml:2509
 #, no-c-format
 msgid "mirror/protocol (protocol)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2509
+#: boot-installer.xml:2510
 #, 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:2522
+#: boot-installer.xml:2523
 #, no-c-format
 msgid "tasksel:tasksel/first (tasks)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2523
+#: boot-installer.xml:2524
 #, 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:2537
+#: boot-installer.xml:2538
 #, no-c-format
 msgid "Passing parameters to kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2538
+#: boot-installer.xml:2539
 #, 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:2551
+#: boot-installer.xml:2552
 #, 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:2558
+#: boot-installer.xml:2559
 #, no-c-format
 msgid ""
       "The syntax to use to set parameters for modules is: <informalexample><screen>\n"
@@ -1809,133 +1809,133 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:2568
+#: boot-installer.xml:2569
 #, no-c-format
 msgid "3c509.xcvr=3 3c509.irq=10"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2574
+#: boot-installer.xml:2575
 #, no-c-format
 msgid "Blacklisting kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2575
+#: boot-installer.xml:2576
 #, 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:2584
+#: boot-installer.xml:2585
 #, 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:2592
+#: boot-installer.xml:2593
 #, 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:2608
+#: boot-installer.xml:2609
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2613
+#: boot-installer.xml:2614
 #, no-c-format
 msgid "CD-ROM Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2614
+#: boot-installer.xml:2615
 #, 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:2621
+#: boot-installer.xml:2622
 #, no-c-format
 msgid "There are many different possible causes for these problems. We can only list some common issues and provide general suggestions on how to deal with them. The rest is up to you."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2627
+#: boot-installer.xml:2628
 #, no-c-format
 msgid "There are two very simple things that you should try first."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2632
+#: boot-installer.xml:2633
 #, 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:2638
+#: boot-installer.xml:2639
 #, 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:2648
+#: boot-installer.xml:2649
 #, 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:2654
+#: boot-installer.xml:2655
 #, 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:2662
+#: boot-installer.xml:2663
 #, no-c-format
 msgid "Common issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2665
+#: boot-installer.xml:2666
 #, 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:2671
+#: boot-installer.xml:2672
 #, no-c-format
 msgid "If your system boots correctly from the CD-ROM, it does not necessarily mean that &arch-kernel; also supports the CD-ROM (or, more correctly, the controller that your CD-ROM drive is connected to)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2678
+#: boot-installer.xml:2679
 #, 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:2689
+#: boot-installer.xml:2690
 #, no-c-format
 msgid "How to investigate and maybe solve issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2690
+#: boot-installer.xml:2691
 #, no-c-format
 msgid "If the CD-ROM fails to boot, try the suggestions listed below."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2695
+#: boot-installer.xml:2696
 #, 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:2701
+#: boot-installer.xml:2702
 #, 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"
@@ -1945,7 +1945,7 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:2714
+#: boot-installer.xml:2715
 #, no-c-format
 msgid ""
       "$ dd if=/dev/cdrom | \\\n"
@@ -1958,19 +1958,19 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2719
+#: boot-installer.xml:2720
 #, no-c-format
 msgid "If, after the installer has been booted successfully, the CD-ROM is not detected, sometimes simply trying again may solve the problem. If you have more than one CD-ROM drive, try changing the CD-ROM to the other drive. If that does not work or if the CD-ROM is recognized but there are errors when reading from it, try the suggestions listed below. Some basic knowledge of &arch-kernel; is required for this. To execute any of the commands, you should first switch to the second virtual console (VT2) and activate the shell there."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2731
+#: boot-installer.xml:2732
 #, 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:2738
+#: boot-installer.xml:2739
 #, 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"
@@ -1983,13 +1983,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2752
+#: boot-installer.xml:2753
 #, 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/cdrom</filename>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2760
+#: boot-installer.xml:2761
 #, 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"
@@ -1998,7 +1998,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2770
+#: boot-installer.xml:2771
 #, no-c-format
 msgid ""
       "Check if DMA is currently enabled: <informalexample><screen>\n"
@@ -2011,193 +2011,193 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2785
+#: boot-installer.xml:2786
 #, 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:2800
+#: boot-installer.xml:2801
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2802
+#: boot-installer.xml:2803
 #, 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:2807
+#: boot-installer.xml:2808
 #, 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:2816
+#: boot-installer.xml:2817
 #, 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:2825
+#: boot-installer.xml:2826
 #, 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:2831
+#: boot-installer.xml:2832
 #, 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:2837
+#: boot-installer.xml:2838
 #, 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:2846
+#: boot-installer.xml:2847
 #, no-c-format
 msgid "Boot Configuration"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2848
+#: boot-installer.xml:2849
 #, 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:2855
+#: boot-installer.xml:2856
 #, no-c-format
 msgid "Often, problems can be solved by removing add-ons and peripherals, and then trying booting again. <phrase arch=\"any-x86\">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2861
+#: boot-installer.xml:2862
 #, 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: para
-#: boot-installer.xml:2874
+#: boot-installer.xml:2875
 #, no-c-format
 msgid "If software speech synthesis does not work, there is most probably an issue with your sound board, usually because either the driver for it is not included in the installer, or because it has unusual mixer level names which are set to muted by default. You should thus submit a bug report which includes the output of the following commands, run on the same machine from a Linux system which is known to have sound working (e.g., a live CD)."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2885
+#: boot-installer.xml:2886
 #, no-c-format
 msgid "dmesg"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2887
+#: boot-installer.xml:2888
 #, no-c-format
 msgid "lspci"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2889
+#: boot-installer.xml:2890
 #, no-c-format
 msgid "lsmod"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2891
+#: boot-installer.xml:2892
 #, no-c-format
 msgid "amixer"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2899 boot-installer.xml:3001
+#: boot-installer.xml:2900 boot-installer.xml:3002
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2900
+#: boot-installer.xml:2901
 #, 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:2905
+#: boot-installer.xml:2906
 #, 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:2911
+#: boot-installer.xml:2912
 #, 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:2920
+#: boot-installer.xml:2921
 #, 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:2927
+#: boot-installer.xml:2928
 #, no-c-format
 msgid "Some systems (especially laptops) that have a native resolution that is not a 4:3 ratio (i.e. not for example 800x600 or 1024x768) may have a blank display after the installer has been booted. In that case adding the boot parameter <userinput>vga=788</userinput><footnote> <para> The parameter <userinput>vga=788</userinput> will activate the VESA framebuffer with a resolution of 800x600. This will probably work, but may not be the optimal resolution for your system. A list of supported resolutions can be obtained by using <userinput>vga=ask</userinput>, but you should be aware that list may not be complete. </para> </footnote> may help. If that does not work, try adding the boot parameter <userinput>fb=false</userinput>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2945
+#: boot-installer.xml:2946
 #, 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</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:2959
+#: boot-installer.xml:2960
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2960
+#: boot-installer.xml:2961
 #, 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:2970
+#: boot-installer.xml:2971
 #, 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:2987
+#: boot-installer.xml:2988
 #, no-c-format
 msgid "System Freeze while Loading USB Modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2988
+#: boot-installer.xml:2989
 #, 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>nousb</userinput> parameter at the boot prompt."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3002
+#: boot-installer.xml:3003
 #, no-c-format
 msgid "There are some common installation problems that are worth mentioning."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3008
+#: boot-installer.xml:3009
 #, no-c-format
 msgid "Misdirected video output"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3009
+#: boot-installer.xml:3010
 #, 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"
@@ -2207,85 +2207,85 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3023
+#: boot-installer.xml:3024
 #, 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:3034
+#: boot-installer.xml:3035
 #, no-c-format
 msgid "Failure to Boot or Install from CD-ROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3035
+#: boot-installer.xml:3036
 #, 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:3041
+#: boot-installer.xml:3042
 #, no-c-format
 msgid "We recommend to install such systems by netbooting the installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3050
+#: boot-installer.xml:3051
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3052
+#: boot-installer.xml:3053
 #, 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 <phrase arch=\"linux-any\">(see <xref linkend=\"kernel-baking\"/>)</phrase>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3077
+#: boot-installer.xml:3078
 #, no-c-format
 msgid "Reporting Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3078
+#: boot-installer.xml:3079
 #, 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:3089
+#: boot-installer.xml:3090
 #, 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:3100
+#: boot-installer.xml:3101
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3101
+#: boot-installer.xml:3102
 #, 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:3108
+#: boot-installer.xml:3109
 #, 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:3114
+#: boot-installer.xml:3115
 #, 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:3124
+#: boot-installer.xml:3125
 #, 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"
diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot
index 7bd602da0..04a62e56b 100644
--- a/po/pot/hardware.pot
+++ b/po/pot/hardware.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: 2012-06-22 15:03+0000\n"
+"POT-Creation-Date: 2012-07-20 14:12+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"
@@ -57,13 +57,13 @@ msgid "&debian; GNU/Linux &release; supports eleven major architectures and seve
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:53 hardware.xml:179
+#: hardware.xml:53 hardware.xml:196
 #, no-c-format
 msgid "Architecture"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:53 hardware.xml:179
+#: hardware.xml:53 hardware.xml:196
 #, no-c-format
 msgid "&debian; Designation"
 msgstr ""
@@ -81,7 +81,7 @@ msgid "Flavor"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:60 hardware.xml:185
+#: hardware.xml:60 hardware.xml:202
 #, no-c-format
 msgid "Intel x86-based"
 msgstr ""
@@ -93,7 +93,7 @@ msgid "i386"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:67 hardware.xml:190
+#: hardware.xml:67 hardware.xml:207
 #, no-c-format
 msgid "AMD64 &amp; Intel EM64T"
 msgstr ""
@@ -179,1643 +179,1679 @@ msgstr ""
 #. Tag: entry
 #: hardware.xml:93
 #, no-c-format
-msgid "HP PA-RISC"
+msgid "ARM with hardware FPU"
 msgstr ""
 
 #. Tag: entry
 #: hardware.xml:94
 #, no-c-format
-msgid "hppa"
+msgid "armhf"
 msgstr ""
 
 #. Tag: entry
 #: hardware.xml:95
 #, no-c-format
-msgid "PA-RISC 1.1"
+msgid "Freescale"
 msgstr ""
 
 #. Tag: entry
 #: hardware.xml:96
 #, no-c-format
+msgid "<entry>mx5</entry>"
+msgstr ""
+
+#. Tag: entry
+#: hardware.xml:100
+#, no-c-format
+msgid "HP PA-RISC"
+msgstr ""
+
+#. Tag: entry
+#: hardware.xml:101
+#, no-c-format
+msgid "hppa"
+msgstr ""
+
+#. Tag: entry
+#: hardware.xml:102
+#, no-c-format
+msgid "PA-RISC 1.1"
+msgstr ""
+
+#. Tag: entry
+#: hardware.xml:103
+#, no-c-format
 msgid "<entry>32</entry>"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:98
+#: hardware.xml:105
 #, no-c-format
 msgid "PA-RISC 2.0"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:99
+#: hardware.xml:106
 #, no-c-format
 msgid "<entry>64</entry>"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:103
+#: hardware.xml:110
 #, no-c-format
 msgid "Intel IA-64"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:104
+#: hardware.xml:111
 #, no-c-format
 msgid "ia64"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:110
+#: hardware.xml:117
 #, no-c-format
 msgid "MIPS (big endian)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:111
+#: hardware.xml:118
 #, no-c-format
 msgid "mips"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:112
+#: hardware.xml:119
 #, no-c-format
 msgid "SGI IP22 (Indy/Indigo 2)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:113
+#: hardware.xml:120
 #, no-c-format
 msgid "r4k-ip22"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:115
+#: hardware.xml:122
 #, no-c-format
 msgid "SGI IP32 (O2)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:116
+#: hardware.xml:123
 #, no-c-format
 msgid "r5k-ip32"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:118 hardware.xml:131
+#: hardware.xml:125 hardware.xml:138
 #, no-c-format
 msgid "MIPS Malta (32 bit)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:119 hardware.xml:132
+#: hardware.xml:126 hardware.xml:139
 #, no-c-format
 msgid "4kc-malta"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:121 hardware.xml:134
+#: hardware.xml:128 hardware.xml:141
 #, no-c-format
 msgid "MIPS Malta (64 bit)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:122 hardware.xml:135
+#: hardware.xml:129 hardware.xml:142
 #, no-c-format
 msgid "5kc-malta"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:126
+#: hardware.xml:133
 #, no-c-format
 msgid "MIPS (little endian)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:127
+#: hardware.xml:134
 #, no-c-format
 msgid "mipsel"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:128
+#: hardware.xml:135
 #, no-c-format
 msgid "Cobalt"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:129
+#: hardware.xml:136
 #, no-c-format
 msgid "cobalt"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:139
+#: hardware.xml:146
 #, no-c-format
 msgid "IBM/Motorola PowerPC"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:140
+#: hardware.xml:147
 #, no-c-format
 msgid "<entry morerows=\"1\">powerpc</entry>"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:141
+#: hardware.xml:148
 #, no-c-format
 msgid "PowerMac"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:142
+#: hardware.xml:149
 #, no-c-format
 msgid "pmac"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:144
+#: hardware.xml:151
 #, no-c-format
 msgid "PReP"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:145
+#: hardware.xml:152
 #, no-c-format
 msgid "prep"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:149
+#: hardware.xml:156
 #, no-c-format
 msgid "Sun SPARC"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:150
+#: hardware.xml:157
 #, no-c-format
 msgid "sparc"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:151
+#: hardware.xml:158
 #, no-c-format
 msgid "<entry>sun4u</entry>"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:152
+#: hardware.xml:159
 #, no-c-format
 msgid "sparc64"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:154
+#: hardware.xml:161
 #, no-c-format
 msgid "<entry>sun4v</entry>"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:158
+#: hardware.xml:165
 #, no-c-format
 msgid "IBM S/390"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:159
+#: hardware.xml:166
 #, no-c-format
 msgid "s390"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:160
+#: hardware.xml:167 hardware.xml:177
 #, no-c-format
 msgid "IPL from VM-reader and DASD"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:161
+#: hardware.xml:168 hardware.xml:178
 #, no-c-format
 msgid "generic"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:163
+#: hardware.xml:170 hardware.xml:180
 #, no-c-format
 msgid "IPL from tape"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:164
+#: hardware.xml:171 hardware.xml:181
 #, no-c-format
 msgid "tape"
 msgstr ""
 
+#. Tag: entry
+#: hardware.xml:175
+#, no-c-format
+msgid "64bit IBM S/390"
+msgstr ""
+
+#. Tag: entry
+#: hardware.xml:176
+#, no-c-format
+msgid "s390x"
+msgstr ""
+
 #. Tag: para
-#: hardware.xml:169
+#: hardware.xml:186
 #, no-c-format
 msgid "&debian; GNU/kFreeBSD &release; supports two architectures."
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:186
+#: hardware.xml:203
 #, no-c-format
 msgid "kfreebsd-i386"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:191
+#: hardware.xml:208
 #, no-c-format
 msgid "kfreebsd-amd64"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:196
+#: hardware.xml:213
 #, no-c-format
 msgid "This document covers installation for the <emphasis>&arch-title;</emphasis> architecture using the <emphasis>&arch-kernel;</emphasis> kernel. If you are looking for information on any of the other &debian;-supported architectures take a look at the <ulink url=\"http://www.debian.org/ports/\">&debian;-Ports</ulink> pages."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:206
+#: hardware.xml:223
 #, no-c-format
 msgid "The &arch-title; architecture only supports Intel Itanium processors and not the much more common 64-bit processors from the EM64T family (including e.g. the Pentium&nbsp;D and the Core2&nbsp;Duo). Those systems are supported by the <emphasis>amd64</emphasis> architecture or, if you prefer a 32-bit userland, the <emphasis>i386</emphasis> architecture."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:216
+#: hardware.xml:233
 #, no-c-format
 msgid "This is the first official release of &debian-gnu; for the &arch-title; architecture. We feel that it has proven itself sufficiently to be released. However, because it has not had the exposure (and hence testing by users) that some other architectures have had, you may encounter a few bugs. Use our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any problems; make sure to mention the fact that the bug is on the &arch-title; platform using the <emphasis>&arch-kernel;</emphasis> kernel. It can be necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink> as well."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:239 hardware.xml:275 hardware.xml:364 hardware.xml:383 hardware.xml:466 hardware.xml:524 hardware.xml:577
+#: hardware.xml:256 hardware.xml:292 hardware.xml:381 hardware.xml:400 hardware.xml:483 hardware.xml:541 hardware.xml:594
 #, no-c-format
 msgid "CPU, Main Boards, and Video Support"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:240 hardware.xml:384
+#: hardware.xml:257 hardware.xml:401
 #, no-c-format
 msgid "Complete information concerning supported peripherals can be found at <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. This section merely outlines the basics."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:248 hardware.xml:392 hardware.xml:501
+#: hardware.xml:265 hardware.xml:409 hardware.xml:518
 #, no-c-format
 msgid "<title>CPU</title>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:249
+#: hardware.xml:266
 #, no-c-format
 msgid "Both AMD64 and Intel EM64T processors are supported."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:277
+#: hardware.xml:294
 #, no-c-format
 msgid "Each distinct ARM architecture requires its own kernel. Because of this the standard &debian; distribution only supports installation on a number of the most common platforms. The &debian; userland however may be used by <emphasis>any</emphasis> ARM CPU."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:286
+#: hardware.xml:303
 #, no-c-format
 msgid "Most ARM CPUs may be run in either endian mode (big or little). However, the majority of current system implementation uses little-endian mode. &debian; currently only supports little-endian ARM systems."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:294
+#: hardware.xml:311
 #, no-c-format
 msgid "The supported platforms are:"
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:301
+#: hardware.xml:318
 #, no-c-format
 msgid "IOP32x"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:302
+#: hardware.xml:319
 #, no-c-format
 msgid "Intel's I/O Processor (IOP) line is found in a number of products related to data storage and processing. &debian; currently supports the IOP32x platform, featuring the IOP 80219 and 32x chips commonly found in Network Attached Storage (NAS) devices. &debian; explicitly supports two such devices: the <ulink url=\"&url-arm-cyrius-glantank;\">GLAN Tank</ulink> from IO-Data and the <ulink url=\"&url-arm-cyrius-n2100;\">Thecus N2100</ulink>."
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:315
+#: hardware.xml:332
 #, no-c-format
 msgid "Kirkwood"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:316
+#: hardware.xml:333
 #, no-c-format
 msgid "Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. We currently support the following Kirkwood based devices: OpenRD (OpenRD-Base, OpenRD-Client and OpenRD-Ultimate), <ulink url=\"&url-arm-cyrius-sheevaplug;\">plug computers (SheevaPlug and GuruPlug)</ulink>, and <ulink url=\"&url-arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (all TS-11x, TS-21x and TS-41x models)."
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:330
+#: hardware.xml:347
 #, no-c-format
 msgid "Orion5x"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:331
+#: hardware.xml:348
 #, no-c-format
 msgid "Orion is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. There are many Network Attached Storage (NAS) devices on the market that are based on an Orion chip. We currently support the following Orion based devices: <ulink url=\"&url-arm-cyrius-kuroboxpro;\">Buffalo Kurobox</ulink>, <ulink url=\"&url-arm-cyrius-dns323;\">D-Link DNS-323</ulink> and <ulink url=\"&url-arm-cyrius-mv2120;\">HP mv2120</ulink>."
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:345
+#: hardware.xml:362
 #, no-c-format
 msgid "<term>Versatile</term>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:346
+#: hardware.xml:363
 #, no-c-format
 msgid "The Versatile platform is emulated by QEMU and is therefore a nice way to test and run &debian; on ARM if you don't have the hardware."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:365
+#: hardware.xml:382
 #, no-c-format
 msgid "There are two major support <emphasis>&architecture;</emphasis> flavors: PA-RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at 32-bit processors whereas the 2.0 architecture is targeted to the 64-bit processors. Some systems are able to run either kernel. In both cases, the userland is 32-bit. There is the possibility of a 64-bit userland in the future."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:393
+#: hardware.xml:410
 #, no-c-format
 msgid "Nearly all x86-based (IA-32) processors still in use in personal computers are supported, including all varieties of Intel's \"Pentium\" series. This also includes 32-bit AMD and VIA (former Cyrix) processors, and processors like the Athlon XP and Intel P4 Xeon."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:400
+#: hardware.xml:417
 #, no-c-format
 msgid "However, &debian; GNU/Linux &releasename; will <emphasis>not</emphasis> run on 386 or earlier processors. Despite the architecture name \"i386\", support for actual 80386 processors (and their clones) was dropped with the Sarge (r3.1) release of &debian;<footnote> <para> We have long tried to avoid this, but in the end it was necessary due a unfortunate series of issues with the compiler and the kernel, starting with an bug in the C++ ABI provided by GCC. You should still be able to run &debian; GNU/Linux on actual 80386 processors if you compile your own kernel and compile all packages from source, but that is beyond the scope of this manual. </para> </footnote>. (No version of Linux has ever supported the 286 or earlier chips in the series.) All i486 and later processors are still supported<footnote> <para> Many &debian; packages will actually run slightly faster on modern computers as a positive side effect of dropping support for these old chips. The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the i386, introduced in 1986, did not have. Previously, these could not be easily used by most &debian; packages; now they can. </para> </footnote>."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:433
+#: hardware.xml:450
 #, no-c-format
 msgid "If your system has a 64-bit processor from the AMD64 or Intel EM64T families, you will probably want to use the installer for the amd64 architecture instead of the installer for the (32-bit) i386 architecture."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:442
+#: hardware.xml:459
 #, no-c-format
 msgid "I/O Bus"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:443
+#: hardware.xml:460
 #, no-c-format
 msgid "The system bus is the part of the motherboard which allows the CPU to communicate with peripherals such as storage devices. Your computer must use the ISA, EISA, PCI, PCIe, PCI-X, or VESA Local Bus (VLB, sometimes called the VL bus). Essentially all personal computers sold in recent years use one of these."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:467
+#: hardware.xml:484
 #, no-c-format
 msgid "&debian; on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> SGI IP22: this platform includes the SGI machines Indy, Indigo 2 and Challenge S. Since these machines are very similar, whenever this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. </para></listitem> <listitem><para> SGI IP32: this platform is generally known as SGI O2. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run &debian; on MIPS if you don't have the hardware. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the &debian; installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:502
+#: hardware.xml:519
 #, no-c-format
 msgid "On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and R5000 processors are supported by the &debian; installation system on big endian MIPS. On SGI IP32, currently only systems based on the R5000 are supported."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:508
+#: hardware.xml:525
 #, no-c-format
 msgid "Some MIPS machines can be operated in both big and little endian mode. For little endian MIPS, please read the documentation for the mipsel architecture."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:525
+#: hardware.xml:542
 #, no-c-format
 msgid "&debian; on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run &debian; on MIPS if you don't have the hardware. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the &debian; installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:553
+#: hardware.xml:570
 #, no-c-format
 msgid "CPU/Machine types"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:555
+#: hardware.xml:572
 #, no-c-format
 msgid "All MIPS based Cobalt machines are supported with the exception of the Qube 2700 (Qube 1)."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:563
+#: hardware.xml:580
 #, no-c-format
 msgid "Supported console options"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:564
+#: hardware.xml:581
 #, no-c-format
 msgid "Cobalt machines use 115200 bps."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:578
+#: hardware.xml:595
 #, no-c-format
 msgid "For &debian-gnu; &release; only the PMac (Power-Macintosh or PowerMac) and PreP subarchitectures are supported."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:599
+#: hardware.xml:616
 #, no-c-format
 msgid "Kernel Flavours"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:601
+#: hardware.xml:618
 #, no-c-format
 msgid "There are two flavours of the powerpc kernel in &debian;, based on the CPU type:"
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:608
+#: hardware.xml:625
 #, no-c-format
 msgid "<term>powerpc</term>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:609
+#: hardware.xml:626
 #, no-c-format
 msgid "Most systems use this kernel flavour, which supports the PowerPC 601, 603, 604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and including the one marketed as G4 use one of these processors."
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:619
+#: hardware.xml:636
 #, no-c-format
 msgid "power64"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:620
+#: hardware.xml:637
 #, no-c-format
 msgid "The power64 kernel flavour supports the following CPUs:"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:624
+#: hardware.xml:641
 #, no-c-format
 msgid "The POWER3 processor is used in older IBM 64-bit server systems: known models include the IntelliStation POWER Model 265, the pSeries 610 and 640, and the RS/6000 7044-170, 7043-260, and 7044-270."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:630
+#: hardware.xml:647
 #, no-c-format
 msgid "The POWER4 processor is used in more recent IBM 64-bit server systems: known models include the pSeries 615, 630, 650, 655, 670, and 690."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:635
+#: hardware.xml:652
 #, no-c-format
 msgid "Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 architecture, and use this kernel flavour."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:669
+#: hardware.xml:686
 #, no-c-format
 msgid "Power Macintosh (pmac) subarchitecture"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:671
+#: hardware.xml:688
 #, no-c-format
 msgid "Apple (and briefly a few other manufacturers &mdash; Power Computing, for example) made a series of Macintosh computers based on the PowerPC processor. For purposes of architecture support, they are categorized as NuBus (not supported by &debian;), OldWorld, and NewWorld."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:678
+#: hardware.xml:695
 #, no-c-format
 msgid "OldWorld systems are most Power Macintoshes with a floppy drive and a PCI bus. Most 603, 603e, 604, and 604e based Power Macintoshes are OldWorld machines. Those pre-iMac PowerPC models from Apple use a four digit naming scheme, except for the beige colored G3 systems, which are also OldWorld."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:686
+#: hardware.xml:703
 #, no-c-format
 msgid "The so called NewWorld PowerMacs are any PowerMacs in translucent colored plastic cases and later models. That includes all iMacs, iBooks, G4 systems, blue colored G3 systems, and most PowerBooks manufactured in and after 1999. The NewWorld PowerMacs are also known for using the <quote>ROM in RAM</quote> system for MacOS, and were manufactured from mid-1998 onwards."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:694
+#: hardware.xml:711
 #, no-c-format
 msgid "Specifications for Apple hardware are available at <ulink url=\"http://www.info.apple.com/support/applespec.html\">AppleSpec</ulink>, and, for older hardware, <ulink url=\"http://www.info.apple.com/support/applespec.legacy/index.html\">AppleSpec Legacy</ulink>."
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:710 hardware.xml:845 hardware.xml:889 hardware.xml:918
+#: hardware.xml:727 hardware.xml:862 hardware.xml:906 hardware.xml:935
 #, no-c-format
 msgid "Model Name/Number"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:711
+#: hardware.xml:728
 #, no-c-format
 msgid "Generation"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:717
+#: hardware.xml:734
 #, no-c-format
 msgid "Apple"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:718
+#: hardware.xml:735
 #, no-c-format
 msgid "iMac Bondi Blue, 5 Flavors, Slot Loading"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:719 hardware.xml:722 hardware.xml:725 hardware.xml:728 hardware.xml:731 hardware.xml:734 hardware.xml:737 hardware.xml:740 hardware.xml:743 hardware.xml:746 hardware.xml:749 hardware.xml:752 hardware.xml:755 hardware.xml:758 hardware.xml:761 hardware.xml:764
+#: hardware.xml:736 hardware.xml:739 hardware.xml:742 hardware.xml:745 hardware.xml:748 hardware.xml:751 hardware.xml:754 hardware.xml:757 hardware.xml:760 hardware.xml:763 hardware.xml:766 hardware.xml:769 hardware.xml:772 hardware.xml:775 hardware.xml:778 hardware.xml:781
 #, no-c-format
 msgid "NewWorld"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:721
+#: hardware.xml:738
 #, no-c-format
 msgid "iMac Summer 2000, Early 2001"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:724
+#: hardware.xml:741
 #, no-c-format
 msgid "iMac G5"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:727
+#: hardware.xml:744
 #, no-c-format
 msgid "iBook, iBook SE, iBook Dual USB"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:730
+#: hardware.xml:747
 #, no-c-format
 msgid "iBook2"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:733
+#: hardware.xml:750
 #, no-c-format
 msgid "iBook G4"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:736
+#: hardware.xml:753
 #, no-c-format
 msgid "Power Macintosh Blue and White (B&amp;W) G3"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:739
+#: hardware.xml:756
 #, no-c-format
 msgid "Power Macintosh G4 PCI, AGP, Cube"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:742
+#: hardware.xml:759
 #, no-c-format
 msgid "Power Macintosh G4 Gigabit Ethernet"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:745
+#: hardware.xml:762
 #, no-c-format
 msgid "Power Macintosh G4 Digital Audio, Quicksilver"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:748
+#: hardware.xml:765
 #, no-c-format
 msgid "Power Macintosh G5"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:751
+#: hardware.xml:768
 #, no-c-format
 msgid "PowerBook G3 FireWire Pismo (2000)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:754
+#: hardware.xml:771
 #, no-c-format
 msgid "PowerBook G3 Lombard (1999)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:757
+#: hardware.xml:774
 #, no-c-format
 msgid "PowerBook G4 Titanium"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:760
+#: hardware.xml:777
 #, no-c-format
 msgid "PowerBook G4 Aluminum"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:763
+#: hardware.xml:780
 #, no-c-format
 msgid "Xserve G5"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:766
+#: hardware.xml:783
 #, no-c-format
 msgid "Performa 4400, 54xx, 5500"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:767 hardware.xml:770 hardware.xml:773 hardware.xml:776 hardware.xml:779 hardware.xml:782 hardware.xml:785 hardware.xml:788 hardware.xml:791 hardware.xml:794 hardware.xml:797 hardware.xml:800 hardware.xml:806 hardware.xml:809 hardware.xml:815 hardware.xml:821 hardware.xml:827
+#: hardware.xml:784 hardware.xml:787 hardware.xml:790 hardware.xml:793 hardware.xml:796 hardware.xml:799 hardware.xml:802 hardware.xml:805 hardware.xml:808 hardware.xml:811 hardware.xml:814 hardware.xml:817 hardware.xml:823 hardware.xml:826 hardware.xml:832 hardware.xml:838 hardware.xml:844
 #, no-c-format
 msgid "OldWorld"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:769
+#: hardware.xml:786
 #, no-c-format
 msgid "Performa 6360, 6400, 6500"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:772
+#: hardware.xml:789
 #, no-c-format
 msgid "Power Macintosh 4400, 5400"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:775
+#: hardware.xml:792
 #, no-c-format
 msgid "Power Macintosh 7200, 7300, 7500, 7600"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:778
+#: hardware.xml:795
 #, no-c-format
 msgid "Power Macintosh 8200, 8500, 8600"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:781
+#: hardware.xml:798
 #, no-c-format
 msgid "Power Macintosh 9500, 9600"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:784
+#: hardware.xml:801
 #, no-c-format
 msgid "Power Macintosh (Beige) G3 Minitower"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:787
+#: hardware.xml:804
 #, no-c-format
 msgid "Power Macintosh (Beige) Desktop, All-in-One"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:790
+#: hardware.xml:807
 #, no-c-format
 msgid "PowerBook 2400, 3400, 3500"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:793
+#: hardware.xml:810
 #, no-c-format
 msgid "PowerBook G3 Wallstreet (1998)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:796
+#: hardware.xml:813
 #, no-c-format
 msgid "Twentieth Anniversary Macintosh"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:799
+#: hardware.xml:816
 #, no-c-format
 msgid "Workgroup Server 7250, 7350, 8550, 9650, G3"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:804
+#: hardware.xml:821
 #, no-c-format
 msgid "Power Computing"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:805
+#: hardware.xml:822
 #, no-c-format
 msgid "PowerBase, PowerTower / Pro, PowerWave"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:808
+#: hardware.xml:825
 #, no-c-format
 msgid "PowerCenter / Pro, PowerCurve"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:813
+#: hardware.xml:830
 #, no-c-format
 msgid "UMAX"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:814
+#: hardware.xml:831
 #, no-c-format
 msgid "C500, C600, J700, S900"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:819
+#: hardware.xml:836
 #, no-c-format
 msgid "<entry>APS</entry>"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:820
+#: hardware.xml:837
 #, no-c-format
 msgid "APS Tech M*Power 604e/2000"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:825 hardware.xml:851
+#: hardware.xml:842 hardware.xml:868
 #, no-c-format
 msgid "Motorola"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:826
+#: hardware.xml:843
 #, no-c-format
 msgid "Starmax 3000, 4000, 5000, 5500"
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:835
+#: hardware.xml:852
 #, no-c-format
 msgid "PReP subarchitecture"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:852
+#: hardware.xml:869
 #, no-c-format
 msgid "Firepower, PowerStack Series E, PowerStack II"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:854
+#: hardware.xml:871
 #, no-c-format
 msgid "MPC 7xx, 8xx"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:856
+#: hardware.xml:873
 #, no-c-format
 msgid "MTX, MTX+"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:858
+#: hardware.xml:875
 #, no-c-format
 msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:860
+#: hardware.xml:877
 #, no-c-format
 msgid "MCP(N)750"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:864 hardware.xml:895
+#: hardware.xml:881 hardware.xml:912
 #, no-c-format
 msgid "IBM RS/6000"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:865
+#: hardware.xml:882
 #, no-c-format
 msgid "40P, 43P"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:867
+#: hardware.xml:884
 #, no-c-format
 msgid "Power 830/850/860 (6070, 6050)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:869
+#: hardware.xml:886
 #, no-c-format
 msgid "6030, 7025, 7043"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:871
+#: hardware.xml:888
 #, no-c-format
 msgid "p640"
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:879
+#: hardware.xml:896
 #, no-c-format
 msgid "CHRP subarchitecture (unsupported)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:896
+#: hardware.xml:913
 #, no-c-format
 msgid "B50, 43P-150, 44P"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:899
+#: hardware.xml:916
 #, no-c-format
 msgid "Genesi"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:900
+#: hardware.xml:917
 #, no-c-format
 msgid "Pegasos I, Pegasos II"
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:908
+#: hardware.xml:925
 #, no-c-format
 msgid "APUS subarchitecture (unsupported)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:924
+#: hardware.xml:941
 #, no-c-format
 msgid "Amiga Power-UP Systems (APUS)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:925
+#: hardware.xml:942
 #, no-c-format
 msgid "A1200, A3000, A4000"
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:933
+#: hardware.xml:950
 #, no-c-format
 msgid "Nubus PowerMac subarchitecture (unsupported)"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:935
+#: hardware.xml:952
 #, no-c-format
 msgid "NuBus systems are not currently supported by &debian;/powerpc. The monolithic Linux/PPC kernel architecture does not have support for these machines; instead, one must use the MkLinux Mach microkernel, which &debian; does not yet support. These include the following: <itemizedlist> <listitem><para> Power Macintosh 6100, 7100, 8100 </para></listitem> <listitem><para> Performa 5200, 6200, 6300 </para></listitem> <listitem><para> Powerbook 1400, 2300, and 5300 </para></listitem> <listitem><para> Workgroup Server 6150, 8150, 9150 </para></listitem> </itemizedlist> A linux kernel for these machines and limited support is available at <ulink url=\"http://nubus-pmac.sourceforge.net/\"></ulink>."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:972
+#: hardware.xml:989
 #, no-c-format
 msgid "Non-PowerPC Macs"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:974
+#: hardware.xml:991
 #, no-c-format
 msgid "Macintosh computers using the 680x0 series of processors are <emphasis>not</emphasis> in the PowerPC family but are instead m68k machines. Those models start with <quote>Mac II</quote> series, go on to the <quote>LC</quote> family, then the Centris series, and culminate in the Quadras and Performas. These models usually have a Roman numeral or 3-digit model number such as Mac IIcx, LCIII or Quadra 950."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:983
+#: hardware.xml:1000
 #, no-c-format
 msgid "This model range started with the Mac II (Mac II, IIx, IIcx, IIci, IIsi, IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, 550, 575, 580, 630), then the Mac TV, then the Centris (610, 650, 660AV), the Quadra (605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950), and finally the Performa 200-640CD."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:991
+#: hardware.xml:1008
 #, no-c-format
 msgid "In laptops, it started with the Mac Portable, then the PowerBook 100-190cs and the PowerBook Duo 210-550c (excluding PowerBook 500 which is Nubus, please see the section above)."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1007
+#: hardware.xml:1024
 #, no-c-format
 msgid "zSeries and System z machine types"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1008
+#: hardware.xml:1025
 #, no-c-format
 msgid "Since &debian; Squeeze, support for booting in ESA/390 mode was dropped. Your machine needs to support the z/Architecture, 64-bit support is mandatory. The userland of the s390 port is still compiled for ESA/390, though. All zSeries and System z hardware is fully supported. &arch-title; support software is included from the kernel 3.1 development stream. The most current information about IBM's Linux support can be found at the <ulink url=\"http://www.ibm.com/developerworks/linux/linux390/development_technical.html\"> Linux on <trademark class=\"registered\">System z</trademark> page on developerWorks</ulink>."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1025
+#: hardware.xml:1042
 #, no-c-format
 msgid "PAV and HyperPAV"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1026
+#: hardware.xml:1043
 #, no-c-format
 msgid "PAV and HyperPAV are supported transparently, multipathing is not needed to take advantage of these storage system features. Be sure to configure the devices during DASD device selection. The alias devices will not be offered neither for formatting, partitioning nor direct use."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1042
+#: hardware.xml:1059
 #, no-c-format
 msgid "CPU and Main Boards Support"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1043
+#: hardware.xml:1060
 #, no-c-format
 msgid "Sparc-based hardware is divided into a number of different subarchitectures, identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u or sun4v. The following list describes what machines they include and what level of support may be expected for each of them."
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:1054
+#: hardware.xml:1071
 #, no-c-format
 msgid "sun4, sun4c, sun4d, sun4m"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1056
+#: hardware.xml:1073
 #, no-c-format
 msgid "None of these 32-bit sparc subarchitectures (sparc32) is supported. For a complete list of machines belonging to these subarchitectures, please consult the <ulink url=\"http://en.wikipedia.org/wiki/SPARCstation\">Wikipedia SPARCstation page</ulink>."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1063
+#: hardware.xml:1080
 #, no-c-format
 msgid "The last &debian; release to support sparc32 was Etch, but even then only for sun4m systems. Support for the other 32-bits subarchitectures had already been discontinued after earlier releases."
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:1073
+#: hardware.xml:1090
 #, no-c-format
 msgid "<term>sun4u</term>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1075
+#: hardware.xml:1092
 #, no-c-format
 msgid "This subarchitecture includes all 64-bit machines (sparc64) based on the UltraSparc processor and its clones. Most of the machines are well supported, even though for some you may experience problems booting from CD due to firmware or bootloader bugs (this problem may be worked around by using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP configurations respectively."
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:1088
+#: hardware.xml:1105
 #, no-c-format
 msgid "<term>sun4v</term>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1090
+#: hardware.xml:1107
 #, no-c-format
 msgid "This is the newest addition to the Sparc family, which includes machines based on the Niagara multi-core CPUs. At the moment such CPUs are only available in T1000 and T2000 servers by Sun, and are well supported. Use the sparc64-smp kernel."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1101
+#: hardware.xml:1118
 #, no-c-format
 msgid "Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are not supported due to lack of support in the Linux kernel."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1110
+#: hardware.xml:1127
 #, no-c-format
 msgid "Laptops"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1111
+#: hardware.xml:1128
 #, no-c-format
 msgid "Laptops are also supported and nowadays most laptops work out of the box. In case a laptop contains specialized or proprietary hardware, some specific functions may not be supported. To see if your particular laptop works well with GNU/Linux, see for example the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1123 hardware.xml:1146 hardware.xml:1166 hardware.xml:1189
+#: hardware.xml:1140 hardware.xml:1163 hardware.xml:1183 hardware.xml:1206
 #, no-c-format
 msgid "Multiple Processors"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1124
+#: hardware.xml:1141
 #, no-c-format
 msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture. The standard &debian; &release; kernel image has been compiled with SMP support. The standard kernel is also usable on non-SMP systems, but has a slight overhead which will cause a small reduction in performance. For normal system use this will hardly be noticable."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1133
+#: hardware.xml:1150
 #, no-c-format
 msgid "In order to optimize the kernel for single CPU systems, you'll have to replace the standard &debian; kernel.<phrase arch=\"linux-any\"> You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you disable SMP is to deselect <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1148
+#: hardware.xml:1165
 #, no-c-format
 msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture. The standard &debian; &release; kernel image has been compiled with <firstterm>SMP-alternatives</firstterm> support. This means that the kernel will detect the number of processors (or processor cores) and will automatically deactivate SMP on uniprocessor systems."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1157
+#: hardware.xml:1174
 #, no-c-format
 msgid "The 486 flavour of the &debian; kernel image packages for &arch-title; is not compiled with SMP support."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1167
+#: hardware.xml:1184
 #, no-c-format
 msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture. However, the standard &debian; &release; kernel image does not support SMP. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1176
+#: hardware.xml:1193
 #, no-c-format
 msgid "In order to take advantage of multiple processors, you'll have to replace the standard &debian; kernel.<phrase arch=\"linux-any\"> You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1190
+#: hardware.xml:1207
 #, no-c-format
 msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture, and is supported by a precompiled &debian; kernel image. Depending on your install media, this SMP-capable kernel may or may not be installed by default. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1200
+#: hardware.xml:1217
 #, no-c-format
 msgid "In order to take advantage of multiple processors, you should check to see if a kernel package that supports SMP is installed, and if not, choose an appropriate kernel package."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1206
+#: hardware.xml:1223
 #, no-c-format
 msgid "You can also build your own customized kernel to support SMP.<phrase arch=\"linux-any\"> You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config.</phrase>"
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1217
+#: hardware.xml:1234
 #, no-c-format
 msgid "Graphics Card Support"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1218
+#: hardware.xml:1235
 #, no-c-format
 msgid "You should be using a VGA-compatible display interface for the console terminal. Nearly every modern display card is compatible with VGA. Ancient standards such CGA, MDA, or HGA should also work, assuming you do not require X11 support. Note that X11 is not used during the installation process described in this document unless the graphical installer was explicitly selected."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1227
+#: hardware.xml:1244
 #, no-c-format
 msgid "&debian;'s support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. Most AGP, PCI, PCIe, and PCI-X video cards work under X.Org. Details on supported graphics buses, cards, monitors, and pointing devices can be found at <ulink url=\"&url-xorg;\"></ulink>. &debian; &release; ships with X.Org version &x11ver;."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1236
+#: hardware.xml:1253
 #, no-c-format
 msgid "The X.Org X Window System is only supported on the SGI Indy and the O2."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1241
+#: hardware.xml:1258
 #, no-c-format
 msgid "Most graphics options commonly found on Sparc-based machines are supported. X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards (glint driver). To use an Elite3D card with X.org you additionally need to install the <classname>afbinit</classname> package, and read the documentation included with it on how to activate the card."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1251
+#: hardware.xml:1268
 #, no-c-format
 msgid "It is not uncommon for a Sparc machine to have two graphics cards in a default configuration. In such a case there is a possibility that the Linux kernel will not direct its output to the card initially used by the firmware. The lack of output on the graphical console may then be mistaken for a hang (usually the last message seen on console is 'Booting Linux...'). One possible solution is to physically remove one of the video cards; another option is to disable one of the cards using a kernel boot parameter. Also, if graphical output is not required or desired, serial console may be used as an alternative. On some systems use of serial console can be activated automatically by disconnecting the keyboard before booting the system."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1273
+#: hardware.xml:1290
 #, no-c-format
 msgid "Network Connectivity Hardware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1274
+#: hardware.xml:1291
 #, no-c-format
 msgid "Almost any network interface card (NIC) supported by the &arch-kernel; kernel should also be supported by the installation system; modular drivers should normally be loaded automatically. <phrase arch=\"x86\">This includes most PCI and PCMCIA cards.</phrase> <phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1283
+#: hardware.xml:1300
 #, no-c-format
 msgid "This includes a lot of generic PCI cards (for systems that have PCI) and the following NICs from Sun:"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1289
+#: hardware.xml:1306
 #, no-c-format
 msgid "Sun LANCE"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1294
+#: hardware.xml:1311
 #, no-c-format
 msgid "Sun Happy Meal"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1299
+#: hardware.xml:1316
 #, no-c-format
 msgid "Sun BigMAC"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1304
+#: hardware.xml:1321
 #, no-c-format
 msgid "Sun QuadEthernet"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1309
+#: hardware.xml:1326
 #, no-c-format
 msgid "MyriCOM Gigabit Ethernet"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1316
+#: hardware.xml:1333
 #, no-c-format
 msgid "The list of supported network devices is:"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1321
+#: hardware.xml:1338
 #, no-c-format
 msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1326
+#: hardware.xml:1343
 #, no-c-format
 msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1331
+#: hardware.xml:1348
 #, no-c-format
 msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1340
+#: hardware.xml:1357
 #, no-c-format
 msgid "On &arch-title;, most built-in Ethernet devices are supported and modules for additional PCI and USB devices are provided."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1345
+#: hardware.xml:1362
 #, no-c-format
 msgid "ISDN is supported, but not during the installation."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1352
+#: hardware.xml:1369
 #, no-c-format
 msgid "Wireless Network Cards"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1353
+#: hardware.xml:1370
 #, no-c-format
 msgid "Wireless networking is in general supported as well and a growing number of wireless adapters are supported by the official &arch-kernel; kernel, although many of them do require firmware to be loaded. If firmware is needed, the installer will prompt you to load firmware. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware during the installation."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1361
+#: hardware.xml:1378
 #, no-c-format
 msgid "Wireless NICs that are not supported by the official &arch-kernel; kernel can generally be made to work under &debian-gnu;, but are not supported during the installation."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1366
+#: hardware.xml:1383
 #, no-c-format
 msgid "If there is a problem with wireless and there is no other NIC you can use during the installation, it is still possible to install &debian-gnu; using a full CD-ROM or DVD image. Select the option to not configure a network and install using only the packages available from the CD/DVD. You can then install the driver and firmware you need after the installation is completed (after the reboot) and configure your network manually."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1376
+#: hardware.xml:1393
 #, no-c-format
 msgid "In some cases the driver you need may not be available as a &debian; package. You will then have to look if there is source code available in the internet and compile the driver yourself. How to do this is outside the scope of this manual. <phrase arch=\"x86\">If no Linux driver is available, your last resort is to use the <classname>ndiswrapper</classname> package, which allows you to use a Windows driver.</phrase>"
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1390
+#: hardware.xml:1407
 #, no-c-format
 msgid "Known Issues for &arch-title;"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1391
+#: hardware.xml:1408
 #, no-c-format
 msgid "There are a couple of issues with specific network cards that are worth mentioning here."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1398
+#: hardware.xml:1415
 #, no-c-format
 msgid "Conflict between tulip and dfme drivers"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1400
+#: hardware.xml:1417
 #, no-c-format
 msgid "There are various PCI network cards that have the same PCI identification, but are supported by related, but different drivers. Some cards work with the <literal>tulip</literal> driver, others with the <literal>dfme</literal> driver. Because they have the same identification, the kernel cannot distinguish between them and it is not certain which driver will be loaded. If this happens to be the wrong one, the NIC may not work, or work badly."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1410
+#: hardware.xml:1427
 #, no-c-format
 msgid "This is a common problem on Netra systems with a Davicom (DEC-Tulip compatible) NIC. In that case the <literal>tulip</literal> driver is probably the correct one. You can prevent this issue by blacklisting the wrong driver module as described in <xref linkend=\"module-blacklist\"/>."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1418
+#: hardware.xml:1435
 #, no-c-format
 msgid "An alternative solution during the installation is to switch to a shell and unload the wrong driver module using <userinput>modprobe -r <replaceable>module</replaceable></userinput> (or both, if they are both loaded). After that you can load the correct module using <userinput>modprobe <replaceable>module</replaceable></userinput>. Note that the wrong module may then still be loaded when the system is rebooted."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1431
+#: hardware.xml:1448
 #, no-c-format
 msgid "Sun B100 blade"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1433
+#: hardware.xml:1450
 #, no-c-format
 msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1448
+#: hardware.xml:1465
 #, no-c-format
 msgid "Braille Displays"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1449
+#: hardware.xml:1466
 #, no-c-format
 msgid "Support for braille displays is determined by the underlying support found in <classname>brltty</classname>. Most displays work under <classname>brltty</classname>, connected via either a serial port, USB or bluetooth. Details on supported braille devices can be found on the <ulink url=\"&url-brltty;\"><classname>brltty</classname> website</ulink>. &debian-gnu; &release; ships with <classname>brltty</classname> version &brlttyver;."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1463
+#: hardware.xml:1480
 #, no-c-format
 msgid "Hardware Speech Synthesis"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1464
+#: hardware.xml:1481
 #, no-c-format
 msgid "Support for hardware speech synthesis devices is determined by the underlying support found in <classname>speakup</classname>. <classname>speakup</classname> only supports integrated boards and external devices connected to a serial port (no USB, serial-to-USB or PCI adapters are supported). Details on supported hardware speech synthesis devices can be found on the <ulink url=\"&url-speakup;\"><classname>speakup</classname> website</ulink>. &debian-gnu; &release; ships with <classname>speakup</classname> version &speakupver;."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1484
+#: hardware.xml:1501
 #, no-c-format
 msgid "Peripherals and Other Hardware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1485
+#: hardware.xml:1502
 #, no-c-format
 msgid "&arch-kernel; supports a large variety of hardware devices such as mice, printers, scanners, PCMCIA and USB devices. However, most of these devices are not required while installing the system."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1491
+#: hardware.xml:1508
 #, no-c-format
 msgid "USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend=\"hardware-issues\"/>)."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1497
+#: hardware.xml:1514
 #, no-c-format
 msgid "Again, see the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> to determine whether your specific hardware is supported by Linux."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1503
+#: hardware.xml:1520
 #, no-c-format
 msgid "Package installations from XPRAM and tape are not supported by this system. All packages that you want to install need to be available on a DASD or over the network using NFS, HTTP or FTP."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1509
+#: hardware.xml:1526
 #, no-c-format
 msgid "The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1521
+#: hardware.xml:1538
 #, no-c-format
 msgid "Devices Requiring Firmware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1522
+#: hardware.xml:1539
 #, no-c-format
 msgid "Besides the availability of a device driver, some hardware also requires so-called <firstterm>firmware</firstterm> or <firstterm>microcode</firstterm> to be loaded into the device before it can become operational. This is most common for network interface cards (especially wireless NICs), but for example some USB devices and even some hard disk controllers also require firmware."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1530
+#: hardware.xml:1547
 #, no-c-format
 msgid "In most cases firmware is non-free according to the criteria used by the &debian-gnu; project and thus cannot be included in the main distribution or in the installation system. If the device driver itself is included in the distribution and if &debian-gnu; legally can distribute the firmware, it will often be available as a separate package from the non-free section of the archive."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1539
+#: hardware.xml:1556
 #, no-c-format
 msgid "However, this does not mean that such hardware cannot be used during an installation. Starting with &debian-gnu; 5.0, &d-i; supports loading firmware files or packages containing firmware from a removable medium, such as a floppy disk or USB stick. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware files or packages during the installation."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1555
+#: hardware.xml:1572
 #, no-c-format
 msgid "Purchasing Hardware Specifically for GNU/&arch-kernel;"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1557
+#: hardware.xml:1574
 #, no-c-format
 msgid "There are several vendors, who ship systems with &debian; or other distributions of GNU/Linux <ulink url=\"&url-pre-installed;\">pre-installed</ulink>. You might pay more for the privilege, but it does buy a level of peace of mind, since you can be sure that the hardware is well-supported by GNU/Linux."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1565
+#: hardware.xml:1582
 #, no-c-format
 msgid "If you do have to buy a machine with Windows bundled, carefully read the software license that comes with Windows; you may be able to reject the license and obtain a rebate from your vendor. Searching the Internet for <quote>windows refund</quote> may get you some useful information to help with that."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1573
+#: hardware.xml:1590
 #, no-c-format
 msgid "Whether or not you are purchasing a system with &arch-kernel; bundled, or even a used system, it is still important to check that your hardware is supported by the &arch-kernel; kernel. Check if your hardware is listed in the references found above. Let your salesperson (if any) know that you're shopping for a &arch-kernel; system. Support &arch-kernel;-friendly hardware vendors."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1584
+#: hardware.xml:1601
 #, no-c-format
 msgid "Avoid Proprietary or Closed Hardware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1585
+#: hardware.xml:1602
 #, no-c-format
 msgid "Some hardware manufacturers simply won't tell us how to write drivers for their hardware. Others won't allow us access to the documentation without a non-disclosure agreement that would prevent us from releasing the &arch-kernel; source code."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1592
+#: hardware.xml:1609
 #, no-c-format
 msgid "Since we haven't been granted access to the documentation on these devices, they simply won't work under &arch-kernel;. You can help by asking the manufacturers of such hardware to release the documentation. If enough people ask, they will realize that the free software community is an important market."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1604
+#: hardware.xml:1621
 #, no-c-format
 msgid "Windows-specific Hardware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1605
+#: hardware.xml:1622
 #, no-c-format
 msgid "A disturbing trend is the proliferation of Windows-specific modems and printers. In some cases these are specially designed to be operated by the Microsoft Windows operating system and bear the legend <quote>WinModem</quote> or <quote>Made especially for Windows-based computers</quote>. This is generally done by removing the embedded processors of the hardware and shifting the work they do over to a Windows driver that is run by your computer's main CPU. This strategy makes the hardware less expensive, but the savings are often <emphasis>not</emphasis> passed on to the user and this hardware may even be more expensive than equivalent devices that retain their embedded intelligence."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1618
+#: hardware.xml:1635
 #, no-c-format
 msgid "You should avoid Windows-specific hardware for two reasons. The first is that the manufacturers do not generally make the resources available to write a &arch-kernel; driver. Generally, the hardware and software interface to the device is proprietary, and documentation is not available without a non-disclosure agreement, if it is available at all. This precludes it being used for free software, since free software writers disclose the source code of their programs. The second reason is that when devices like these have had their embedded processors removed, the operating system must perform the work of the embedded processors, often at <emphasis>real-time</emphasis> priority, and thus the CPU is not available to run your programs while it is driving these devices. Since the typical Windows user does not multi-process as intensively as a &arch-kernel; user, the manufacturers hope that the Windows user simply won't notice the burden this hardware places on their CPU. However, any multi-processing operating system, even Windows 2000 or XP, suffers from degraded performance when peripheral manufacturers skimp on the embedded processing power of their hardware."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1639
+#: hardware.xml:1656
 #, no-c-format
 msgid "You can help improve this situation by encouraging these manufacturers to release the documentation and other resources necessary for us to program their hardware, but the best strategy is simply to avoid this sort of hardware<phrase arch=\"linux-any\"> until it is listed as working in the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink></phrase>."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1657
+#: hardware.xml:1674
 #, no-c-format
 msgid "Installation Media"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1659
+#: hardware.xml:1676
 #, no-c-format
 msgid "This section will help you determine which different media types you can use to install &debian;. There is a whole chapter devoted to media, <xref linkend=\"install-methods\"/>, which lists the advantages and disadvantages of each media type. You may want to refer back to this page once you reach that section."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1669
+#: hardware.xml:1686
 #, no-c-format
 msgid "Floppies"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1670
+#: hardware.xml:1687
 #, no-c-format
 msgid "In some cases, you'll have to do your first boot from floppy disks. Generally, all you will need is a high-density (1440 kilobytes) 3.5 inch floppy drive."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1676
+#: hardware.xml:1693
 #, no-c-format
 msgid "For CHRP, floppy support is currently broken."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1683
+#: hardware.xml:1700
 #, no-c-format
 msgid "CD-ROM/DVD-ROM"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1685
+#: hardware.xml:1702
 #, no-c-format
 msgid "Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both CD-ROMs and DVD-ROMs, because both technologies are really the same from the operating system's point of view, except for some very old nonstandard CD-ROM drives which are neither SCSI nor IDE/ATAPI."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1692
+#: hardware.xml:1709
 #, no-c-format
 msgid "CD-ROM based installation is supported for some architectures. On machines which support bootable CD-ROMs, you should be able to do a completely <phrase arch=\"not-s390\">floppy-less</phrase> <phrase arch=\"s390\">tape-less</phrase> installation. Even if your system doesn't support booting from a CD-ROM, you can use the CD-ROM in conjunction with the other techniques to install your system, once you've booted up by other means; see <xref linkend=\"boot-installer\"/>."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1704
+#: hardware.xml:1721
 #, no-c-format
 msgid "SCSI, SATA and IDE/ATAPI CD-ROMs are supported. The <ulink url=\"&url-cd-howto;\">Linux CD-ROM HOWTO</ulink> contains in-depth information on using CD-ROMs with Linux."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1710
+#: hardware.xml:1727
 #, no-c-format
 msgid "USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1715
+#: hardware.xml:1732
 #, no-c-format
 msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1719
+#: hardware.xml:1736
 #, no-c-format
 msgid "On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. To start the install, simply choose the <quote>System installation</quote> entry in the firmware."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1733
+#: hardware.xml:1750
 #, no-c-format
 msgid "Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1735
+#: hardware.xml:1752
 #, no-c-format
 msgid "Booting the installation system directly from a hard disk is another option for many architectures. This will require some other operating system to load the installer onto the hard disk."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1741
+#: hardware.xml:1758
 #, no-c-format
 msgid "Although the &arch-title; does not allow booting from SunOS (Solaris), you can install from a SunOS partition (UFS slices)."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1749
+#: hardware.xml:1766
 #, no-c-format
 msgid "USB Memory Stick"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1751
+#: hardware.xml:1768
 #, no-c-format
 msgid "Many &debian; boxes need their floppy and/or CD-ROM drives only for setting up the system and for rescue purposes. If you operate some servers, you will probably already have thought about omitting those drives and using an USB memory stick for installing and (when necessary) for recovering the system. This is also useful for small systems which have no room for unnecessary drives."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1763
+#: hardware.xml:1780
 #, no-c-format
 msgid "Network"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1765
+#: hardware.xml:1782
 #, no-c-format
 msgid "The network can be used during the installation to retrieve files needed for the installation. Whether the network is used or not depends on the installation method you choose and your answers to certain questions that will be asked during the installation. The installation system supports most types of network connections (including PPPoE, but not ISDN or PPP), via either HTTP or FTP. After the installation is completed, you can also configure your system to use ISDN and PPP."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1775
+#: hardware.xml:1792
 #, no-c-format
 msgid "You can also <emphasis>boot</emphasis> the installation system over the network. <phrase arch=\"mips;mipsel\">This is the preferred installation technique for &arch-title;.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1781
+#: hardware.xml:1798
 #, no-c-format
 msgid "Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1789
+#: hardware.xml:1806
 #, no-c-format
 msgid "Un*x or GNU system"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1791
+#: hardware.xml:1808
 #, no-c-format
 msgid "If you are running another Unix-like system, you could use it to install &debian-gnu; without using the &d-i; described in the rest of this manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the <xref linkend=\"linux-upgrade\"/>."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1803
+#: hardware.xml:1820
 #, no-c-format
 msgid "Supported Storage Systems"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1805
+#: hardware.xml:1822
 #, no-c-format
 msgid "The &debian; boot disks contain a kernel which is built to maximize the number of systems it runs on. Unfortunately, this makes for a larger kernel, which includes many drivers that won't be used for your machine<phrase arch=\"linux-any\"> (see <xref linkend=\"kernel-baking\"/> to learn how to build your own kernel)</phrase>. Support for the widest possible range of devices is desirable in general, to ensure that &debian; can be installed on the widest array of hardware."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1815
+#: hardware.xml:1832
 #, no-c-format
 msgid "Generally, the &debian; installation system includes support for floppies, IDE (also known as PATA) drives, IDE floppies, parallel port IDE devices, SATA and SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1822
+#: hardware.xml:1839
 #, no-c-format
 msgid "Disk interfaces that emulate the <quote>AT</quote> hard disk interface &mdash; often called MFM, RLL, IDE, or PATA &mdash; are supported. SATA and SCSI disk controllers from many different manufacturers are supported. See the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> for more details."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1830
+#: hardware.xml:1847
 #, no-c-format
 msgid "Any storage system supported by the Linux kernel is also supported by the boot system. The following SCSI drivers are supported in the default kernel: <itemizedlist> <listitem><para> Sparc ESP </para></listitem> <listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></listitem> </itemizedlist> IDE systems (such as the UltraSPARC 5) are also supported. See <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors FAQ</ulink> for more information on SPARC hardware supported by the Linux kernel."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1863
+#: hardware.xml:1880
 #, no-c-format
 msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support floppies on CHRP systems at all."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1869
+#: hardware.xml:1886
 #, no-c-format
 msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support the floppy drive."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1875
+#: hardware.xml:1892
 #, no-c-format
 msgid "Any storage system supported by the Linux kernel is also supported by the boot system."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1880
+#: hardware.xml:1897
 #, no-c-format
 msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This means that FBA and ECKD DASDs are supported with the old Linux disk layout (ldl) and the new common S/390 disk layout (cdl)."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1897
+#: hardware.xml:1914
 #, no-c-format
 msgid "Memory and Disk Space Requirements"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1899
+#: hardware.xml:1916
 #, no-c-format
 msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space to perform a normal installation. Note that these are fairly minimal numbers. For more realistic figures, see <xref linkend=\"minimum-hardware-reqts\"/>."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1906
+#: hardware.xml:1923
 #, no-c-format
 msgid "Installation on systems with less memory<footnote condition=\"gtk\"> <para> Installation images that support the graphical installer require more memory than images that support only the textual installer and should not be used on systems with less than &minimum-memory; of memory. If there is a choice between booting the regular and the graphical installer, the former should be selected. </para> </footnote> or disk space available may be possible but is only advised for experienced users."
 msgstr ""
diff --git a/po/pot/install-methods.pot b/po/pot/install-methods.pot
index 66d281790..30f85686c 100644
--- a/po/pot/install-methods.pot
+++ b/po/pot/install-methods.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: 2012-06-16 09:12+0000\n"
+"POT-Creation-Date: 2012-07-20 14:12+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"
@@ -499,7 +499,7 @@ msgid "If you like more flexibility or just want to know what's going on, you sh
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:665 install-methods.xml:777
+#: install-methods.xml:665 install-methods.xml:787
 #, no-c-format
 msgid "Partitioning the USB stick"
 msgstr ""
@@ -514,19 +514,21 @@ msgstr ""
 #: install-methods.xml:671
 #, no-c-format
 msgid ""
-      "Since most USB sticks come pre-configured with a single FAT16 partition, you probably won't have to repartition or reformat the stick. If you have to do that anyway, use <command>cfdisk</command> or any other partitioning tool to create a FAT16 partition<footnote> <para> Don't forget to set the <quote>bootable</quote> bootable flag. </para> </footnote>, and then create the filesystem using: <informalexample><screen>\n"
+      "Since most USB sticks come pre-configured with a single FAT16 partition, you probably won't have to repartition or reformat the stick. If you have to do that anyway, use <command>cfdisk</command> or any other partitioning tool to create a FAT16 partition<footnote> <para> Don't forget to set the <quote>bootable</quote> bootable flag. </para> </footnote>, install an MBR using: <informalexample><screen>\n"
+      "# install-mbr /dev/<replaceable>sdX</replaceable>\n"
+      "</screen></informalexample> The <command>install-mbr</command> command is contained in the <classname>mbr</classname> &debian; package. Then create the filesystem using: <informalexample><screen>\n"
       "# mkdosfs /dev/<replaceable>sdX1</replaceable>\n"
       "</screen></informalexample> Take care that you use the correct device name for your USB stick. The <command>mkdosfs</command> command is contained in the <classname>dosfstools</classname> &debian; package."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:690
+#: install-methods.xml:695
 #, no-c-format
 msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. Although any boot loader (e.g. <classname>lilo</classname>) should work, it's convenient to use <classname>syslinux</classname>, since it uses a FAT16 partition and can be reconfigured by just editing a text file. Any operating system which supports the FAT file system can be used to make changes to the configuration of the boot loader."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:700
+#: install-methods.xml:705
 #, no-c-format
 msgid ""
       "To put <classname>syslinux</classname> on the FAT16 partition on your USB stick, install the <classname>syslinux</classname> and <classname>mtools</classname> packages on your system, and do: <informalexample><screen>\n"
@@ -535,35 +537,41 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:717 install-methods.xml:824
+#: install-methods.xml:722 install-methods.xml:834
 #, no-c-format
 msgid "Adding the installer image"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:718
+#: install-methods.xml:723
 #, no-c-format
 msgid "Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /mnt</userinput>) and copy the following installer image files to the stick: <itemizedlist> <listitem><para> <filename>vmlinuz</filename> or <filename>linux</filename> (kernel binary) </para></listitem> <listitem><para> <filename>initrd.gz</filename> (initial ramdisk image) </para></listitem> </itemizedlist> You can choose between either the regular version or the graphical version of the installer. The latter can be found in the <filename>gtk</filename> subdirectory. If you want to rename the files, please note that <classname>syslinux</classname> can only process DOS (8.3) file names."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:742
+#: install-methods.xml:747
 #, no-c-format
 msgid ""
       "Next you should create a <filename>syslinux.cfg</filename> configuration file, which at a bare minimum should contain the following two lines (change the name of the kernel binary to <quote><filename>linux</filename></quote> if you used a <filename>netboot</filename> image): <informalexample><screen>\n"
       "default vmlinuz\n"
       "append initrd=initrd.gz\n"
-      "</screen></informalexample> For the graphical installer you should add <userinput>vga=788</userinput> to the second line."
+      "</screen></informalexample> For the graphical installer you should add <userinput>vga=788</userinput> to the second line. Other parameters can be appended as desired."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:754 install-methods.xml:864
+#: install-methods.xml:759
+#, no-c-format
+msgid "To enable the boot prompt to permit further parameter appending, add a <userinput>prompt 1</userinput> line."
+msgstr ""
+
+#. Tag: para
+#: install-methods.xml:764 install-methods.xml:874
 #, no-c-format
 msgid "If you used an <filename>hd-media</filename> image, you should now copy the ISO file of a &debian; ISO image<footnote> <para> You can use either a businesscard, a netinst or a full CD image (see <xref linkend=\"official-cdrom\"/>). Be sure to select one that fits. Note that the <quote>netboot <filename>mini.iso</filename></quote> image is not usable for this purpose. </para> </footnote> onto the stick. When you are done, unmount the USB memory stick (<userinput>umount /mnt</userinput>)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:778
+#: install-methods.xml:788
 #, no-c-format
 msgid ""
       "Most USB sticks do not come pre-configured in such a way that Open Firmware can boot from them, so you will need to repartition the stick. On Mac systems, run <userinput>mac-fdisk /dev/<replaceable>sdX</replaceable></userinput>, initialise a new partition map using the <userinput>i</userinput> command, and create a new partition of type Apple_Bootstrap using the <userinput>C</userinput> command. (Note that the first \"partition\" will always be the partition map itself.) Then type <informalexample><screen>\n"
@@ -572,13 +580,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:795
+#: install-methods.xml:805
 #, no-c-format
 msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. The <command>yaboot</command> boot loader can be installed on an HFS filesystem and can be reconfigured by just editing a text file. Any operating system which supports the HFS file system can be used to make changes to the configuration of the boot loader."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:804
+#: install-methods.xml:814
 #, no-c-format
 msgid ""
       "The normal <command>ybin</command> tool that comes with <command>yaboot</command> does not yet understand USB storage devices, so you will have to install <command>yaboot</command> by hand using the <classname>hfsutils</classname> tools. Type <informalexample><screen>\n"
@@ -591,37 +599,37 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:825
+#: install-methods.xml:835
 #, no-c-format
 msgid "Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>) and copy the following installer image files to the stick:"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:832
+#: install-methods.xml:842
 #, no-c-format
 msgid "<filename>vmlinux</filename> (kernel binary)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:837
+#: install-methods.xml:847
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (initial ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:842
+#: install-methods.xml:852
 #, no-c-format
 msgid "<filename>yaboot.conf</filename> (yaboot configuration file)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:847
+#: install-methods.xml:857
 #, no-c-format
 msgid "<filename>boot.msg</filename> (optional boot message)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:854
+#: install-methods.xml:864
 #, no-c-format
 msgid ""
       "The <filename>yaboot.conf</filename> configuration file should contain the following lines: <informalexample><screen>\n"
@@ -639,259 +647,259 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:892
+#: install-methods.xml:902
 #, no-c-format
 msgid "Preparing Files for Hard Disk Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:893
+#: install-methods.xml:903
 #, no-c-format
 msgid "The installer may be booted using boot files placed on an existing hard drive partition, either launched from another operating system or by invoking a boot loader directly from the BIOS."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:899
+#: install-methods.xml:909
 #, no-c-format
 msgid "A full, <quote>pure network</quote> installation can be achieved using this technique. This avoids all hassles of removable media, like finding and burning CD images or struggling with too numerous and unreliable floppy disks."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:906
+#: install-methods.xml:916
 #, no-c-format
 msgid "The installer cannot boot from files on an HFS+ file system. MacOS System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. To determine whether your existing file system is HFS+, select <userinput>Get Info</userinput> for the volume in question. HFS file systems appear as <userinput>Mac OS Standard</userinput>, while HFS+ file systems say <userinput>Mac OS Extended</userinput>. You must have an HFS partition in order to exchange files between MacOS and Linux, in particular the installation files you download."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:917
+#: install-methods.xml:927
 #, no-c-format
 msgid "Different programs are used for hard disk installation system booting, depending on whether the system is a <quote>NewWorld</quote> or an <quote>OldWorld</quote> model."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:926
+#: install-methods.xml:936
 #, no-c-format
 msgid "Hard disk installer booting using <command>LILO</command> or <command>GRUB</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:928
+#: install-methods.xml:938
 #, no-c-format
 msgid "This section explains how to add to or even replace an existing linux installation using either <command>LILO</command> or <command>GRUB</command>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:934
+#: install-methods.xml:944
 #, no-c-format
 msgid "At boot time, both bootloaders support loading in memory not only the kernel, but also a disk image. This RAM disk can be used as the root file-system by the kernel."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:940
+#: install-methods.xml:950
 #, no-c-format
 msgid "Copy the following files from the &debian; archives to a convenient location on your hard drive (note that LILO can not boot from files on an NTFS file system), for instance to <filename>/boot/newinstall/</filename>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:948
+#: install-methods.xml:958
 #, no-c-format
 msgid "<filename>vmlinuz</filename> (kernel binary)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:953
+#: install-methods.xml:963
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:960
+#: install-methods.xml:970
 #, no-c-format
 msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:970
+#: install-methods.xml:980
 #, no-c-format
 msgid "Hard disk installer booting using <command>loadlin</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:971
+#: install-methods.xml:981
 #, no-c-format
 msgid "This section explains how to prepare your hard drive for booting the installer from DOS using <command>loadlin</command>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:976
+#: install-methods.xml:986
 #, no-c-format
 msgid "Copy the following directories from a &debian; CD image to <filename>c:\\</filename>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:981
+#: install-methods.xml:991
 #, no-c-format
 msgid "<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:986
+#: install-methods.xml:996
 #, no-c-format
 msgid "<filename>/tools</filename> (loadlin tool)"
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:999
+#: install-methods.xml:1009
 #, no-c-format
 msgid "Hard Disk Installer Booting for OldWorld Macs"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1000
+#: install-methods.xml:1010
 #, no-c-format
 msgid "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</application> to launch Linux installation, but <application>miBoot</application> cannot easily be used for hard disk booting. <application>BootX</application>, launched from MacOS, supports booting from files placed on the hard disk. <application>BootX</application> can also be used to dual-boot MacOS and Linux after your &debian; installation is complete. For the Performa 6360, it appears that <command>quik</command> cannot make the hard disk bootable. So <application>BootX</application> is required on that model."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1013
+#: install-methods.xml:1023
 #, no-c-format
 msgid "Download and unstuff the <application>BootX</application> distribution, available from <ulink url=\"&url-powerpc-bootx;\"></ulink>, or in the <filename>dists/woody/main/disks-powerpc/current/powermac</filename> directory on &debian; http/ftp mirrors and official &debian; CDs. Use <application>Stuffit Expander</application> to extract it from its archive. Within the package, there is an empty folder called <filename>Linux Kernels</filename>. Download <filename>linux.bin</filename> and <filename>ramdisk.image.gz</filename> from the <filename>disks-powerpc/current/powermac</filename> folder, and place them in the <filename>Linux Kernels</filename> folder. Then place the <filename>Linux Kernels</filename> folder in the active System Folder."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1033
+#: install-methods.xml:1043
 #, no-c-format
 msgid "Hard Disk Installer Booting for NewWorld Macs"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1034
+#: install-methods.xml:1044
 #, no-c-format
 msgid "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as well as loading ELF binaries directly from the hard disk. These machines will boot Linux directly via <command>yaboot</command>, which supports loading a kernel and RAMdisk directly from an ext2 partition, as well as dual-booting with MacOS. Hard disk booting of the installer is particularly appropriate for newer machines without floppy drives. <command>BootX</command> is not supported and must not be used on NewWorld PowerMacs."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1045
+#: install-methods.xml:1055
 #, no-c-format
 msgid "<emphasis>Copy</emphasis> (not move) the following four files which you downloaded earlier from the &debian; archives, onto the root level of your hard drive (this can be accomplished by <keycap>option</keycap>-dragging each file to the hard drive icon)."
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1055 install-methods.xml:1381
+#: install-methods.xml:1065 install-methods.xml:1391
 #, no-c-format
 msgid "vmlinux"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1060 install-methods.xml:1386
+#: install-methods.xml:1070 install-methods.xml:1396
 #, no-c-format
 msgid "initrd.gz"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1065 install-methods.xml:1391
+#: install-methods.xml:1075 install-methods.xml:1401
 #, no-c-format
 msgid "yaboot"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1070 install-methods.xml:1396
+#: install-methods.xml:1080 install-methods.xml:1406
 #, no-c-format
 msgid "yaboot.conf"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1075
+#: install-methods.xml:1085
 #, no-c-format
 msgid "Make a note of the partition number of the MacOS partition where you place these files. If you have the MacOS <command>pdisk</command> program, you can use the <command>L</command> command to check for the partition number. You will need this partition number for the command you type at the Open Firmware prompt when you boot the installer."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1083
+#: install-methods.xml:1093
 #, no-c-format
 msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1096
+#: install-methods.xml:1106
 #, no-c-format
 msgid "Preparing Files for TFTP Net Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1097
+#: install-methods.xml:1107
 #, no-c-format
 msgid "If your machine is connected to a local area network, you may be able to boot it over the network from another machine, using TFTP. If you intend to boot the installation system from another machine, the boot files will need to be placed in specific locations on that machine, and the machine configured to support booting of your specific machine."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1105
+#: install-methods.xml:1115
 #, no-c-format
 msgid "You need to set up a TFTP server, and for many machines a DHCP server<phrase condition=\"supports-rarp\">, or RARP server</phrase><phrase condition=\"supports-bootp\">, or BOOTP server</phrase>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1112
+#: install-methods.xml:1122
 #, no-c-format
 msgid "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol (RARP) is one way to tell your client what IP address to use for itself. Another way is to use the BOOTP protocol.</phrase> <phrase condition=\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP address and where on the network to obtain a boot image.</phrase> The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1126
+#: install-methods.xml:1136
 #, no-c-format
 msgid "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good idea to use DHCP instead of BOOTP. Some of the latest machines are unable to boot using BOOTP."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1132
+#: install-methods.xml:1142
 #, no-c-format
 msgid "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There is an <classname>rbootd</classname> package available in &debian;."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1137
+#: install-methods.xml:1147
 #, no-c-format
 msgid "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to the client. Theoretically, any server, on any platform, which implements these protocols, may be used. In the examples in this section, we shall provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1145
+#: install-methods.xml:1155
 #, no-c-format
 msgid "For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. It's written by the same author as the <classname>syslinux</classname> bootloader and is therefore least likely to cause issues. A good alternative is <classname>atftpd</classname>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1161
+#: install-methods.xml:1171
 #, no-c-format
 msgid "Setting up RARP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1162
+#: install-methods.xml:1172
 #, no-c-format
 msgid "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC address) of the client computers to be installed. If you don't know this information, you can <phrase arch=\"sparc\"> pick it off the initial OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the command <userinput>ip addr show dev eth0</userinput>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1174
+#: install-methods.xml:1184
 #, no-c-format
 msgid "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, you use the <command>rarpd</command> program. You need to ensure that the Ethernet hardware address for the client is listed in the <quote>ethers</quote> database (either in the <filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start the RARP daemon. Issue the command (as root): <userinput>/usr/sbin/rarpd -a</userinput> on most Linux systems and SunOS 5 (Solaris 2), <userinput>/usr/sbin/in.rarpd -a</userinput> on some other Linux systems, or <userinput>/usr/etc/rarpd -a</userinput> in SunOS 4 (Solaris 1)."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1195
+#: install-methods.xml:1205
 #, no-c-format
 msgid "Setting up a DHCP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1196
+#: install-methods.xml:1206
 #, no-c-format
 msgid "One free software DHCP server is ISC <command>dhcpd</command>. For &debian-gnu;, the <classname>dhcp3-server</classname> package is recommended. Here is a sample configuration file for it (see <filename>/etc/dhcp3/dhcpd.conf</filename>):"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:1203
+#: install-methods.xml:1213
 #, no-c-format
 msgid ""
       "option domain-name \"example.com\";\n"
@@ -916,25 +924,25 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1205
+#: install-methods.xml:1215
 #, no-c-format
 msgid "In this example, there is one server <replaceable>servername</replaceable> which performs all of the work of DHCP server, TFTP server, and network gateway. You will almost certainly need to change the domain-name options, as well as the server name and client hardware address. The <replaceable>filename</replaceable> option should be the name of the file which will be retrieved via TFTP."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1215
+#: install-methods.xml:1225
 #, no-c-format
 msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/dhcp3-server restart</userinput>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1223
+#: install-methods.xml:1233
 #, no-c-format
 msgid "Enabling PXE Booting in the DHCP configuration"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1224
+#: install-methods.xml:1234
 #, no-c-format
 msgid ""
       "Here is another example for a <filename>dhcp.conf</filename> using the Pre-boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n"
@@ -969,19 +977,19 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1244
+#: install-methods.xml:1254
 #, no-c-format
 msgid "Setting up a BOOTP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1245
+#: install-methods.xml:1255
 #, no-c-format
 msgid "There are two BOOTP servers available for GNU/Linux. The first is CMU <command>bootpd</command>. The other is actually a DHCP server: ISC <command>dhcpd</command>. In &debian-gnu; these are contained in the <classname>bootp</classname> and <classname>dhcp3-server</classname> packages respectively."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1253
+#: install-methods.xml:1263
 #, no-c-format
 msgid ""
       "To use CMU <command>bootpd</command>, you must first uncomment (or add) the relevant line in <filename>/etc/inetd.conf</filename>. On &debian-gnu;, you can run <userinput>update-inetd --enable bootps</userinput>, then <userinput>/etc/init.d/inetd reload</userinput> to do so. Just in case your BOOTP server does not run &debian;, the line in question should look like: <informalexample><screen>\n"
@@ -998,43 +1006,43 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1286
+#: install-methods.xml:1296
 #, no-c-format
 msgid "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really easy, because it treats BOOTP clients as a moderately special case of DHCP clients. Some architectures require a complex configuration for booting clients via BOOTP. If yours is one of those, read the section <xref linkend=\"dhcpd\"/>. Otherwise you will probably be able to get away with simply adding the <userinput>allow bootp</userinput> directive to the configuration block for the subnet containing the client in <filename>/etc/dhcp3/dhcpd.conf</filename>, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcp3-server restart</userinput>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1305
+#: install-methods.xml:1315
 #, no-c-format
 msgid "Enabling the TFTP Server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1306
+#: install-methods.xml:1316
 #, no-c-format
 msgid "To get the TFTP server ready to go, you should first make sure that <command>tftpd</command> is enabled."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1311
+#: install-methods.xml:1321
 #, no-c-format
 msgid "In the case of <classname>tftpd-hpa</classname> there are two ways the service can be run. It can be started on demand by the system's <classname>inetd</classname> daemon, or it can be set up to run as an independent daemon. Which of these methods is used is selected when the package is installed and can be changed by reconfiguring the package."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1320
+#: install-methods.xml:1330
 #, no-c-format
 msgid "Historically, TFTP servers used <filename>/tftpboot</filename> as directory to serve images from. However, &debian-gnu; packages may use other directories to comply with the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink>. For example, <classname>tftpd-hpa</classname> by default uses <filename>/srv/tftp</filename>. You may have to adjust the configuration examples in this section accordingly."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1330
+#: install-methods.xml:1340
 #, no-c-format
 msgid "All <command>in.tftpd</command> alternatives available in &debian; should log TFTP requests to the system logs by default. Some of them support a <userinput>-v</userinput> argument to increase verbosity. It is recommended to check these log messages in case of boot problems as they are a good starting point for diagnosing the cause of errors."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1338
+#: install-methods.xml:1348
 #, no-c-format
 msgid ""
       "If you intend to install &debian; on an SGI machine and your TFTP server is a GNU/Linux box running Linux 2.4, you'll need to set the following on your server: <informalexample><screen>\n"
@@ -1045,49 +1053,49 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1360
+#: install-methods.xml:1370
 #, no-c-format
 msgid "Move TFTP Images Into Place"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1361
+#: install-methods.xml:1371
 #, no-c-format
 msgid "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-files\"/>, in the <command>tftpd</command> boot image directory. You may have to make a link from that file to the file which <command>tftpd</command> will use for booting a particular client. Unfortunately, the file name is determined by the TFTP client, and there are no strong standards."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1370
+#: install-methods.xml:1380
 #, no-c-format
 msgid "On NewWorld Power Macintosh machines, you will need to set up the <command>yaboot</command> boot loader as the TFTP boot image. <command>Yaboot</command> will then retrieve the kernel and RAMdisk images via TFTP itself. You will need to download the following files from the <filename>netboot/</filename> directory:"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1401
+#: install-methods.xml:1411
 #, no-c-format
 msgid "boot.msg"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1406
+#: install-methods.xml:1416
 #, no-c-format
 msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>pxelinux.0</filename> to <command>tftpd</command> as the filename to boot."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1414
+#: install-methods.xml:1424
 #, no-c-format
 msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/debian-installer/ia64/elilo.efi</filename> to <command>tftpd</command> as the filename to boot."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1426
+#: install-methods.xml:1436
 #, no-c-format
 msgid "SPARC TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1427
+#: install-methods.xml:1437
 #, no-c-format
 msgid ""
       "Some SPARC architectures add the subarchitecture names, such as <quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename would be <filename>C0A80103.SUN4C</filename>. However, there are also subarchitectures where the file the client looks for is just <filename>client-ip-in-hex</filename>. An easy way to determine the hexadecimal code for the IP address is to enter the following command in a shell (assuming the machine's intended IP is 10.0.0.4). <informalexample><screen>\n"
@@ -1096,55 +1104,55 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1443
+#: install-methods.xml:1453
 #, no-c-format
 msgid "If you've done all this correctly, giving the command <userinput>boot net</userinput> from the OpenPROM should load the image. If the image cannot be found, try checking the logs on your tftp server to see which image name is being requested."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1450
+#: install-methods.xml:1460
 #, no-c-format
 msgid "You can also force some sparc systems to look for a specific file name by adding it to the end of the OpenPROM boot command, such as <userinput>boot net my-sparc.image</userinput>. This must still reside in the directory that the TFTP server looks in."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1461
+#: install-methods.xml:1471
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1462
+#: install-methods.xml:1472
 #, no-c-format
 msgid "On SGI machines you can rely on the <command>bootpd</command> to supply the name of the TFTP file. It is given either as the <userinput>bf=</userinput> in <filename>/etc/bootptab</filename> or as the <userinput>filename=</userinput> option in <filename>/etc/dhcpd.conf</filename>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1570
+#: install-methods.xml:1580
 #, no-c-format
 msgid "Automatic Installation"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1571
+#: install-methods.xml:1581
 #, no-c-format
 msgid "For installing on multiple computers it's possible to do fully automatic installations. &debian; packages intended for this include <classname>fai-quickstart</classname> (which can use an install server) and the &debian; Installer itself. Have a look at the <ulink url=\"http://fai-project.org\">FAI home page</ulink> for detailed information."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1583
+#: install-methods.xml:1593
 #, no-c-format
 msgid "Automatic Installation Using the &debian; Installer"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1584
+#: install-methods.xml:1594
 #, no-c-format
 msgid "The &debian; Installer supports automating installs via preconfiguration files. A preconfiguration file can be loaded from the network or from removable media, and used to fill in answers to questions asked during the installation process."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1591
+#: install-methods.xml:1601
 #, no-c-format
 msgid "Full documentation on preseeding including a working example that you can edit is in <xref linkend=\"appendix-preseed\"/>."
 msgstr ""
diff --git a/po/pot/random-bits.pot b/po/pot/random-bits.pot
index dd3156080..323ec4c38 100644
--- a/po/pot/random-bits.pot
+++ b/po/pot/random-bits.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: 2012-06-16 09:12+0000\n"
+"POT-Creation-Date: 2012-07-20 14:12+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"
@@ -840,11 +840,11 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:516
 #, no-c-format
-msgid "Substitute one of the following for <replaceable>ARCH</replaceable> in the <command>debootstrap</command> command: <userinput>alpha</userinput>, <userinput>amd64</userinput>, <userinput>arm</userinput>, <userinput>armel</userinput>, <userinput>hppa</userinput>, <userinput>i386</userinput>, <userinput>ia64</userinput>, <userinput>m68k</userinput>, <userinput>mips</userinput>, <userinput>mipsel</userinput>, <userinput>powerpc</userinput>, <userinput>s390</userinput>, or <userinput>sparc</userinput>."
+msgid "Substitute one of the following for <replaceable>ARCH</replaceable> in the <command>debootstrap</command> command: <userinput>amd64</userinput>, <userinput>armel</userinput>, <userinput>armhf</userinput>, <userinput>i386</userinput>, <userinput>ia64</userinput>, <userinput>mips</userinput>, <userinput>mipsel</userinput>, <userinput>powerpc</userinput>, <userinput>s390</userinput>, <userinput>s390x</userinput>, or <userinput>sparc</userinput>."
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:535
+#: random-bits.xml:533
 #, no-c-format
 msgid ""
       "# /usr/sbin/debootstrap --arch ARCH &releasename; \\\n"
@@ -852,13 +852,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:541
+#: random-bits.xml:539
 #, no-c-format
 msgid "Configure The Base System"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:542
+#: random-bits.xml:540
 #, no-c-format
 msgid ""
       "Now you've got a real &debian; system, though rather lean, on disk. <command>chroot</command> into it: <informalexample><screen>\n"
@@ -867,37 +867,37 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:552
+#: random-bits.xml:550
 #, no-c-format
 msgid "# export TERM=<replaceable>xterm-color</replaceable>"
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:557
+#: random-bits.xml:555
 #, no-c-format
 msgid "Create device files"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:558
+#: random-bits.xml:556
 #, no-c-format
 msgid "At this point <filename>/dev/</filename> only contains very basic device files. For the next steps of the installation additional device files may be needed. There are different ways to go about this and which method you should use depends on the host system you are using for the installation, on whether you intend to use a modular kernel or not, and on whether you intend to use dynamic (e.g. using <classname>udev</classname>) or static device files for the new system."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:568
+#: random-bits.xml:566
 #, no-c-format
 msgid "A few of the available options are:"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:573
+#: random-bits.xml:571
 #, no-c-format
 msgid "install the makedev package, and create a default set of static device files using (after chrooting)"
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:577
+#: random-bits.xml:575
 #, no-c-format
 msgid ""
       "# apt-get install makedev\n"
@@ -906,25 +906,25 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:580
+#: random-bits.xml:578
 #, no-c-format
 msgid "manually create only specific device files using <command>MAKEDEV</command>"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:585
+#: random-bits.xml:583
 #, no-c-format
 msgid "bind mount /dev from your host system on top of /dev in the target system; note that the postinst scripts of some packages may try to create device files, so this option should only be used with care"
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:598
+#: random-bits.xml:596
 #, no-c-format
 msgid "Mount Partitions"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:599
+#: random-bits.xml:597
 #, no-c-format
 msgid ""
       "You need to create <filename>/etc/fstab</filename>. <informalexample><screen>\n"
@@ -958,37 +958,37 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:625
+#: random-bits.xml:623
 #, no-c-format
 msgid "# mount -t proc proc /proc"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:627
+#: random-bits.xml:625
 #, no-c-format
 msgid "The command <userinput>ls /proc</userinput> should now show a non-empty directory. Should this fail, you may be able to mount proc from outside the chroot:"
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:633
+#: random-bits.xml:631
 #, no-c-format
 msgid "# mount -t proc proc /mnt/debinst/proc"
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:639
+#: random-bits.xml:637
 #, no-c-format
 msgid "Setting Timezone"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:640
+#: random-bits.xml:638
 #, no-c-format
 msgid "An option in the file <filename>/etc/default/rcS</filename> determines whether the system will interpret the hardware clock as being set to UTC or local time. The following command allows you to set that and choose your timezone."
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:647
+#: random-bits.xml:645
 #, no-c-format
 msgid ""
       "# editor /etc/default/rcS\n"
@@ -996,13 +996,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:653
+#: random-bits.xml:651
 #, no-c-format
 msgid "Configure Networking"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:654
+#: random-bits.xml:652
 #, no-c-format
 msgid ""
       "To configure networking, edit <filename>/etc/network/interfaces</filename>, <filename>/etc/resolv.conf</filename>, <filename>/etc/hostname</filename> and <filename>/etc/hosts</filename>. <informalexample><screen>\n"
@@ -1056,13 +1056,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:695
+#: random-bits.xml:693
 #, no-c-format
 msgid "Configure Apt"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:696
+#: random-bits.xml:694
 #, no-c-format
 msgid ""
       "Debootstrap will have created a very basic <filename>/etc/apt/sources.list</filename> that will allow installing additional packages. However, you may want to add some additional sources, for example for source packages and security updates: <informalexample><screen>\n"
@@ -1074,13 +1074,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:712
+#: random-bits.xml:710
 #, no-c-format
 msgid "Configure Locales and Keyboard"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:713
+#: random-bits.xml:711
 #, no-c-format
 msgid ""
       "To configure your locale settings to use a language other than English, install the <classname>locales</classname> support package and configure it. Currently the use of UTF-8 locales is recommended. <informalexample><screen>\n"
@@ -1090,7 +1090,7 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:723
+#: random-bits.xml:721
 #, no-c-format
 msgid ""
       "# aptitude install console-setup\n"
@@ -1098,61 +1098,61 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:725
+#: random-bits.xml:723
 #, no-c-format
 msgid "Note that the keyboard cannot be set while in the chroot, but will be configured for the next reboot."
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:735
+#: random-bits.xml:733
 #, no-c-format
 msgid "Install a Kernel"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:736
+#: random-bits.xml:734
 #, no-c-format
 msgid "If you intend to boot this system, you probably want a &arch-kernel; kernel and a boot loader. Identify available pre-packaged kernels with:"
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:741
+#: random-bits.xml:739
 #, no-c-format
 msgid "# apt-cache search &kernelpackage;"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:743
+#: random-bits.xml:741
 #, no-c-format
 msgid "Then install the kernel package of your choice using its package name."
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:747
+#: random-bits.xml:745
 #, no-c-format
 msgid "# aptitude install &kernelpackage;-<replaceable>&kernelversion;-arch-etc</replaceable>"
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:753
+#: random-bits.xml:751
 #, no-c-format
 msgid "Set up the Boot Loader"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:754
+#: random-bits.xml:752
 #, no-c-format
 msgid "To make your &debian-gnu; system bootable, set up your boot loader to load the installed kernel with your new root partition. Note that <command>debootstrap</command> does not install a boot loader, though you can use <command>aptitude</command> inside your &debian; chroot to do so."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:761
+#: random-bits.xml:759
 #, no-c-format
 msgid "Check <userinput>info grub</userinput> <phrase arch=\"x86\">or <userinput>man lilo.conf</userinput></phrase> for instructions on setting up the bootloader. If you are keeping the system you used to install &debian;, just add an entry for the &debian; install to your existing grub2 <filename>grub.cfg</filename><phrase arch=\"x86\">or <filename>lilo.conf</filename>. For <filename>lilo.conf</filename>, you could also copy it to the new system and edit it there. After you are done editing, call <command>lilo</command> (remember it will use <filename>lilo.conf</filename> relative to the system you call it from)</phrase>."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:773
+#: random-bits.xml:771
 #, no-c-format
 msgid ""
       "Installing and setting up <classname>grub2</classname> is as easy as: <informalexample><screen>\n"
@@ -1163,19 +1163,19 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:783
+#: random-bits.xml:781
 #, no-c-format
 msgid "Note that this assumes that a <filename>/dev/hda</filename> device file has been created. There are alternative methods to install <command>grub2</command>, but those are outside the scope of this appendix."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:789
+#: random-bits.xml:787
 #, no-c-format
 msgid "Here is a basic <filename>/etc/lilo.conf</filename> as an example:"
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:793
+#: random-bits.xml:791
 #, no-c-format
 msgid ""
       "boot=/dev/<replaceable>hda6</replaceable>\n"
@@ -1189,13 +1189,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:795
+#: random-bits.xml:793
 #, no-c-format
 msgid "Check <userinput>man yaboot.conf</userinput> for instructions on setting up the bootloader. If you are keeping the system you used to install &debian;, just add an entry for the &debian; install to your existing <filename>yaboot.conf</filename>. You could also copy it to the new system and edit it there. After you are done editing, call ybin (remember it will use <filename>yaboot.conf</filename> relative to the system you call it from)."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:805
+#: random-bits.xml:803
 #, no-c-format
 msgid ""
       "Here is a basic <filename>/etc/yaboot.conf</filename> as an example: <informalexample><screen>\n"
@@ -1211,13 +1211,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:818
+#: random-bits.xml:816
 #, no-c-format
 msgid "Finishing touches"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:819
+#: random-bits.xml:817
 #, no-c-format
 msgid ""
       "As mentioned earlier, the installed system will be very basic. If you would like to make the system a bit more mature, there is an easy method to install all packages with <quote>standard</quote> priority: <informalexample><screen>\n"
@@ -1226,91 +1226,91 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:830
+#: random-bits.xml:828
 #, no-c-format
 msgid "After the installation there will be a lot of downloaded packages in <filename>/var/cache/apt/archives/</filename>. You can free up some diskspace by running:"
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:836
+#: random-bits.xml:834
 #, no-c-format
 msgid "# aptitude clean"
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:847
+#: random-bits.xml:845
 #, no-c-format
 msgid "Installing &debian-gnu; over Parallel Line IP (PLIP)"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:849
+#: random-bits.xml:847
 #, no-c-format
 msgid "This section explains how to install &debian-gnu; on a computer without an Ethernet card, but with just a remote gateway computer attached via a Null-Modem cable (also called Null-Printer cable). The gateway computer should be connected to a network that has a &debian; mirror on it (e.g. to the Internet)."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:857
+#: random-bits.xml:855
 #, no-c-format
 msgid "In the example in this appendix we will set up a PLIP connection using a gateway connected to the Internet over a dial-up connection (ppp0). We will use IP addresses 192.168.0.1 and 192.168.0.2 for the PLIP interfaces on the target system and the source system respectively (these addresses should be unused within your network address space)."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:865
+#: random-bits.xml:863
 #, no-c-format
 msgid "The PLIP connection set up during the installation will also be available after the reboot into the installed system (see <xref linkend=\"boot-new\"/>)."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:870
+#: random-bits.xml:868
 #, no-c-format
 msgid "Before you start, you will need to check the BIOS configuration (IO base address and IRQ) for the parallel ports of both the source and target systems. The most common values are <literal>io=0x378</literal>, <literal>irq=7</literal>."
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:880
+#: random-bits.xml:878
 #, no-c-format
 msgid "Requirements"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:883
+#: random-bits.xml:881
 #, no-c-format
 msgid "A target computer, called <emphasis>target</emphasis>, where &debian; will be installed."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:889
+#: random-bits.xml:887
 #, no-c-format
 msgid "System installation media; see <xref linkend=\"installation-media\"/>."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:894
+#: random-bits.xml:892
 #, no-c-format
 msgid "Another computer connected to the Internet, called <emphasis>source</emphasis>, that will function as the gateway."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:900
+#: random-bits.xml:898
 #, no-c-format
 msgid "A DB-25 Null-Modem cable. See the <ulink url=\"&url-plip-install-howto;\">PLIP-Install-HOWTO</ulink> for more information on this cable and instructions how to make your own."
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:912
+#: random-bits.xml:910
 #, no-c-format
 msgid "Setting up source"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:913
+#: random-bits.xml:911
 #, no-c-format
 msgid "The following shell script is a simple example of how to configure the source computer as a gateway to the Internet using ppp0."
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:918
+#: random-bits.xml:916
 #, no-c-format
 msgid ""
       "#!/bin/sh\n"
@@ -1331,13 +1331,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:924
+#: random-bits.xml:922
 #, no-c-format
 msgid "Installing target"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:925
+#: random-bits.xml:923
 #, no-c-format
 msgid ""
       "Boot the installation media. The installation needs to be run in expert mode; enter <userinput>expert</userinput> at the boot prompt. If you need to set parameters for kernel modules, you also need to do this at the boot prompt. For example, to boot the installer and set values for the <quote>io</quote> and <quote>irq</quote> options for the parport_pc module, enter the following at the boot prompt: <informalexample><screen>\n"
@@ -1346,217 +1346,217 @@ msgid ""
 msgstr ""
 
 #. Tag: guimenuitem
-#: random-bits.xml:944
+#: random-bits.xml:942
 #, no-c-format
 msgid "Load installer components from CD"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:946
+#: random-bits.xml:944
 #, no-c-format
 msgid "Select the <userinput>plip-modules</userinput> option from the list; this will make the PLIP drivers available to the installation system."
 msgstr ""
 
 #. Tag: guimenuitem
-#: random-bits.xml:954
+#: random-bits.xml:952
 #, no-c-format
 msgid "Detect network hardware"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:959
+#: random-bits.xml:957
 #, no-c-format
 msgid "If target <emphasis>does</emphasis> have a network card, a list of driver modules for detected cards will be shown. If you want to force &d-i; to use plip instead, you have to deselect all listed driver modules. Obviously, if target doesn't have a network card, the installer will not show this list."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:968
+#: random-bits.xml:966
 #, no-c-format
 msgid "Because no network card was detected/selected earlier, the installer will ask you to select a network driver module from a list. Select the <userinput>plip</userinput> module."
 msgstr ""
 
 #. Tag: guimenuitem
-#: random-bits.xml:980
+#: random-bits.xml:978
 #, no-c-format
 msgid "Configure the network"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:983
+#: random-bits.xml:981
 #, no-c-format
 msgid "Auto-configure network with DHCP: No"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:988
+#: random-bits.xml:986
 #, no-c-format
 msgid "IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:993
+#: random-bits.xml:991
 #, no-c-format
 msgid "Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></userinput>"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:999
+#: random-bits.xml:997
 #, no-c-format
 msgid "Name server addresses: you can enter the same addresses used on source (see <filename>/etc/resolv.conf</filename>)"
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:1018
+#: random-bits.xml:1016
 #, no-c-format
 msgid "Installing &debian-gnu; using PPP over Ethernet (PPPoE)"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1020
+#: random-bits.xml:1018
 #, no-c-format
 msgid "In some countries PPP over Ethernet (PPPoE) is a common protocol for broadband (ADSL or cable) connections to an Internet Service Provider. Setting up a network connection using PPPoE is not supported by default in the installer, but can be made to work very simply. This section explains how."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1028
+#: random-bits.xml:1026
 #, no-c-format
 msgid "The PPPoE connection set up during the installation will also be available after the reboot into the installed system (see <xref linkend=\"boot-new\"/>)."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1033
+#: random-bits.xml:1031
 #, no-c-format
 msgid "To have the option of setting up and using PPPoE during the installation, you will need to install using one of the CD-ROM/DVD images that are available. It is not supported for other installation methods (e.g. netboot<phrase condition=\"supports-floppy-boot\"> or floppy</phrase>)."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1040
+#: random-bits.xml:1038
 #, no-c-format
 msgid "Installing over PPPoE is mostly the same as any other installation. The following steps explain the differences."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1048
+#: random-bits.xml:1046
 #, no-c-format
 msgid "Boot the installer with the boot parameter <userinput>modules=ppp-udeb</userinput><footnote arch=\"x86\"> <para> See <xref linkend=\"boot-screen\"/> for information on how to add a boot parameter. </para> </footnote>. This will ensure the component responsible for the setup of PPPoE (<classname>ppp-udeb</classname>) will be loaded and run automatically."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1063
+#: random-bits.xml:1061
 #, no-c-format
 msgid "Follow the regular initial steps of the installation (language, country and keyboard selection; the loading of additional installer components<footnote> <para> The <classname>ppp-udeb</classname> component is loaded as one of the additional components in this step. If you want to install at medium or low priority (expert mode), you can also manually select the <classname>ppp-udeb</classname> instead of entering the <quote>modules</quote> parameter at the boot prompt. </para> </footnote>)."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1082
+#: random-bits.xml:1080
 #, no-c-format
 msgid "The next step is the detection of network hardware, in order to identify any Ethernet cards present in the system."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1088
+#: random-bits.xml:1086
 #, no-c-format
 msgid "After this the actual setup of PPPoE is started. The installer will probe all the detected Ethernet interfaces in an attempt to find a PPPoE concentrator (a type of server which handles PPPoE connections)."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1094
+#: random-bits.xml:1092
 #, no-c-format
 msgid "It is possible that the concentrator will not to be found at the first attempt. This can happen occasionally on slow or loaded networks or with faulty servers. In most cases a second attempt to detect the concentrator will be successful; to retry, select <guimenuitem>Configure and start a PPPoE connection</guimenuitem> from the main menu of the installer."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1103
+#: random-bits.xml:1101
 #, no-c-format
 msgid "After a concentrator is found, the user will be prompted to type the login information (the PPPoE username and password)."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1109
+#: random-bits.xml:1107
 #, no-c-format
 msgid "At this point the installer will use the provided information to establish the PPPoE connection. If the correct information was provided, the PPPoE connection should be configured and the installer should be able to use it to connect to the Internet and retrieve packages over it (if needed). If the login information is not correct or some error appears, the installer will stop, but the configuration can be attempted again by selecting the menu entry <guimenuitem>Configure and start a PPPoE connection</guimenuitem>."
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:1129
+#: random-bits.xml:1127
 #, no-c-format
 msgid "The Graphical Installer"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1130
+#: random-bits.xml:1128
 #, no-c-format
 msgid "The graphical version of the installer is only available for a limited number of architectures, including &arch-title;. The functionality of the graphical installer is essentially the same as that of the regular installer as it basically uses the same programs, but with a different frontend."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1138
+#: random-bits.xml:1136
 #, no-c-format
 msgid "Although the functionality is identical, the graphical installer still has a few significant advantages. The main advantage is that it supports more languages, namely those that use a character set that cannot be displayed with the regular <quote>newt</quote> frontend. It also has a few usability advantages such as the option to use a mouse, and in some cases several questions can be displayed on a single screen."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1147
+#: random-bits.xml:1145
 #, no-c-format
 msgid "The graphical installer is available with all CD images and with the hd-media installation method. To boot the graphical installer simply select the relevant option from the boot menu. Expert and rescue mode for the graphical installer can be selected from the <quote>Advanced options</quote> menu. The previously used boot methods <userinput>installgui</userinput>, <userinput>expertgui</userinput> and <userinput>rescuegui</userinput> can still be used from the boot prompt which is shown after selecting the <quote>Help</quote> option in the boot menu."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1158
+#: random-bits.xml:1156
 #, no-c-format
 msgid "There is also a graphical installer image that can be netbooted. And there is a special <quote>mini</quote> ISO image<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a &debian; mirror as described in <xref linkend=\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. </para> </footnote>, which is mainly useful for testing."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1171
+#: random-bits.xml:1169
 #, no-c-format
 msgid "For &arch-title;, currently only an experimental <quote>mini</quote> ISO image is available<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a &debian; mirror as described in <xref linkend=\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. </para> </footnote>. It should work on almost all PowerPC systems that have an ATI graphical card, but is unlikely to work on other systems."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1185
+#: random-bits.xml:1183
 #, no-c-format
 msgid "Just as with the regular installer it is possible to add boot parameters when starting the graphical installer."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1191
+#: random-bits.xml:1189
 #, no-c-format
 msgid "The graphical installer requires significantly more memory to run than the regular installer: &minimum-memory-gtk;. If insufficient memory is available, it will automatically fall back to the regular <quote>newt</quote> frontend."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1198
+#: random-bits.xml:1196
 #, no-c-format
 msgid "If the amount of memory in your system is below &minimum-memory;, the graphical installer may fail to boot at all while booting the regular installer would still work. Using the regular installer is recommended for systems with little available memory."
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:1208
+#: random-bits.xml:1206
 #, no-c-format
 msgid "Using the graphical installer"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1209
+#: random-bits.xml:1207
 #, no-c-format
 msgid "As already mentioned, the graphical installer basically works the same as the regular installer and thus the rest of this manual can be used to guide you through the installation process."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1215
+#: random-bits.xml:1213
 #, no-c-format
 msgid "If you prefer using the keyboard over the mouse, there are two things you need to know. To expand a collapsed list (used for example for the selection of countries within continents), you can use the <keycap>+</keycap> and <keycap>-</keycap> keys. For questions where more than one item can be selected (e.g. task selection), you first need to tab to the &BTN-CONT; button after making your selections; hitting enter will toggle a selection, not activate &BTN-CONT;."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1225
+#: random-bits.xml:1223
 #, no-c-format
 msgid "If a dialog offers additional help information, a <guibutton>Help</guibutton> button will be displayed. The help information can be accessed either by activating the button or by pressing the <keycap>F1</keycap> key."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1231
+#: random-bits.xml:1229
 #, no-c-format
 msgid "To switch to another console, you will also need to use the <keycap>Ctrl</keycap> key, just as with the X Window System. For example, to switch to VT2 (the first debug shell) you would use: <keycombo> <keycap>Ctrl</keycap> <keycap>Left Alt</keycap> <keycap>F2</keycap> </keycombo>. The graphical installer itself runs on VT5, so you can use <keycombo> <keycap>Left Alt</keycap> <keycap>F5</keycap> </keycombo> to switch back."
 msgstr ""