Refresh po and pot files after changings in en

7 files changed, 1202 insertions, 1104 deletions

diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot
index b6ae6c268..d623d2952 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: 2014-08-26 20:40+0000\n"
+"POT-Creation-Date: 2015-01-09 19:07+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"
@@ -69,19 +69,19 @@ msgid "Booting by TFTP"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:70 boot-installer.xml:630 boot-installer.xml:1252 boot-installer.xml:1436 boot-installer.xml:1759 boot-installer.xml:1869
+#: boot-installer.xml:70 boot-installer.xml:689 boot-installer.xml:1311 boot-installer.xml:1495 boot-installer.xml:1818 boot-installer.xml:1928
 #, no-c-format
 msgid "Booting from the network requires that you have a network connection and a TFTP network boot server (and probably also a DHCP, RARP, or BOOTP server for automatic network configuration)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:76 boot-installer.xml:636 boot-installer.xml:1258 boot-installer.xml:1442 boot-installer.xml:1765 boot-installer.xml:1875
+#: boot-installer.xml:76 boot-installer.xml:695 boot-installer.xml:1317 boot-installer.xml:1501 boot-installer.xml:1824 boot-installer.xml:1934
 #, 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:81 boot-installer.xml:641 boot-installer.xml:1263 boot-installer.xml:1447 boot-installer.xml:1770 boot-installer.xml:1880
+#: boot-installer.xml:81 boot-installer.xml:700 boot-installer.xml:1322 boot-installer.xml:1506 boot-installer.xml:1829 boot-installer.xml:1939
 #, no-c-format
 msgid "The server-side setup to support network booting is described in <xref linkend=\"install-tftp\"/>."
 msgstr ""
@@ -183,85 +183,121 @@ msgid "Note: When booting standard linux images, it is important to load the ini
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:286 boot-installer.xml:865 boot-installer.xml:1522 boot-installer.xml:1903
+#: boot-installer.xml:160
+#, no-c-format
+msgid "Booting from a USB stick in u-boot"
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:161
+#, no-c-format
+msgid "Many modern u-boot versions have USB support and allow booting from USB mass storage devices such as USB sticks. Unfortunately the exact steps required to do that can vary quite a bit from device to device."
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:168
+#, no-c-format
+msgid "U-Boot v2014.10 has introduced a common commandline handling and autoboot framework. This allows building generic boot images that work on any system implementing this framework. The &d-i; supports installation from a USB stick on such systems, but unfortunately not all platforms have adopted this new framework yet."
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:177
+#, no-c-format
+msgid "To build a bootable USB stick for installing &debian;, unpack the hd-media tarball (see <xref linkend=\"where-files\"/>) onto a USB stick formatted with a filesystem supported by the u-boot version on your device. For modern u-boot versions, any of FAT16 / FAT32 / ext2 / ext3 / ext4 usually works. Then copy the ISO image file of the first &debian; installation CD or DVD onto the stick."
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:187
+#, no-c-format
+msgid "The autoboot framework in modern u-boot versions works similar to the boot ordering options in a PC BIOS, i.e. it checks a list of possible boot devices for a valid boot image and starts the first one it finds. If there is no operating system installed, plugging in the USB stick and powering up the system should result in starting the installer. You can also initiate the USB-boot process any time from the u-boot prompt by entering the <quote>run usb_boot</quote> command."
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:197
+#, no-c-format
+msgid "One problem that can come up when booting from a USB stick while using a serial console can be a console baudrate mismatch. If a console variable is defined in u-boot, the &d-i; boot script automatically passes it to the kernel to set the primary console device and, if applicable, the console baudrate. Unfortunately the handling of the console variable varies from platform to platform - on some platforms, the console variable includes the baudrate (as in <quote>console=ttyS0,115200</quote>), while on other platforms the console variable contains only the device (as in <quote>console=ttyS0</quote>). The latter case leads to a garbled console output when the default baudrate differs between u-boot and the kernel. Modern u-boot versions often use 115200 baud while the kernel still defaults to the traditional 9600 baud. If this happens, you should manually set the console variable to contain the correct baudrate for your system and then start the installer with the <quote>run usb_boot</quote> command."
+msgstr ""
+
+#. Tag: title
+#: boot-installer.xml:345 boot-installer.xml:924 boot-installer.xml:1581 boot-installer.xml:1962
 #, no-c-format
 msgid "Booting from a CD-ROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:292 boot-installer.xml:871 boot-installer.xml:1528 boot-installer.xml:1909
+#: boot-installer.xml:351 boot-installer.xml:930 boot-installer.xml:1587 boot-installer.xml:1968
 #, 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:303 boot-installer.xml:882 boot-installer.xml:1539 boot-installer.xml:1920
+#: boot-installer.xml:362 boot-installer.xml:941 boot-installer.xml:1598 boot-installer.xml:1979
 #, 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:311 boot-installer.xml:890 boot-installer.xml:1547 boot-installer.xml:1928
+#: boot-installer.xml:370 boot-installer.xml:949 boot-installer.xml:1606 boot-installer.xml:1987
 #, 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 medium and 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:319 boot-installer.xml:898 boot-installer.xml:1555 boot-installer.xml:1936
+#: boot-installer.xml:378 boot-installer.xml:957 boot-installer.xml:1614 boot-installer.xml:1995
 #, no-c-format
 msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:393
+#: boot-installer.xml:452
 #, no-c-format
 msgid "Booting from Windows"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:394
+#: boot-installer.xml:453
 #, no-c-format
 msgid "To start the installer from Windows, you can either"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:399
+#: boot-installer.xml:458
 #, no-c-format
 msgid "obtain CD-ROM/DVD-ROM<phrase condition=\"bootable-usb\"> or USB memory stick</phrase> installation media as described in <xref linkend=\"official-cdrom\"/><phrase condition=\"bootable-usb\"> respective <xref linkend=\"boot-usb-files\"/></phrase> or"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:407
+#: boot-installer.xml:466
 #, no-c-format
 msgid "download a standalone Windows executable, which is available as tools/win32-loader/stable/win32-loader.exe on the &debian; mirrors,"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:415
+#: boot-installer.xml:474
 #, no-c-format
 msgid "If you use an installation CD or DVD, a pre-installation program should be launched automatically when you insert the disc. In case Windows does not start it automatically, or if you are using a USB memory stick, you can run it manually by accessing the device and executing <command>setup.exe</command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:423
+#: boot-installer.xml:482
 #, no-c-format
 msgid "After the program has been started, a few preliminary questions will be asked and the system will be prepared to reboot into the &debian-gnu; installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:433
+#: boot-installer.xml:492
 #, no-c-format
 msgid "Booting from DOS using loadlin"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:434
+#: boot-installer.xml:493
 #, no-c-format
 msgid "Boot into DOS (not Windows). To do this, you can for instance boot from a recovery or diagnostic disk."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:439
+#: boot-installer.xml:498
 #, no-c-format
 msgid ""
       "If you can access the installation CD, change the current drive to the CD-ROM drive, e.g. <informalexample><screen>\n"
@@ -270,7 +306,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:449
+#: boot-installer.xml:508
 #, no-c-format
 msgid ""
       "Enter the subdirectory for the flavor you chose, e.g., <informalexample><screen>\n"
@@ -281,37 +317,37 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:467
+#: boot-installer.xml:526
 #, no-c-format
 msgid "Booting from Linux using <command>LILO</command> or <command>GRUB</command>"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:470
+#: boot-installer.xml:529
 #, no-c-format
 msgid "To boot the installer from hard disk, you must first download and place the needed files as described in <xref linkend=\"boot-drive-files\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:475
+#: boot-installer.xml:534
 #, no-c-format
 msgid "If you intend to use the hard drive only for booting and then download everything over the network, you should download the <filename>netboot/debian-installer/&architecture;/initrd.gz</filename> file and its corresponding kernel <filename>netboot/debian-installer/&architecture;/linux</filename>. This will allow you to repartition the hard disk from which you boot the installer, although you should do so with care."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:485
+#: boot-installer.xml:544
 #, no-c-format
 msgid "Alternatively, if you intend to keep an existing partition on the hard drive unchanged during the install, you can download the <filename>hd-media/initrd.gz</filename> file and its kernel, as well as copy a CD (or DVD) iso to the drive (make sure the file is named ending in <literal>.iso</literal>). The installer can then boot from the drive and install from the CD/DVD image, without needing the network."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:494
+#: boot-installer.xml:553
 #, no-c-format
 msgid "For <command>LILO</command>, you will need to configure two essential things in <filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> to load the <filename>initrd.gz</filename> installer at boot time; </para></listitem> <listitem><para> have the <filename>vmlinuz</filename> kernel use a RAM disk as its root partition. </para></listitem> </itemizedlist> Here is a <filename>/etc/lilo.conf</filename> example:"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:515
+#: boot-installer.xml:574
 #, no-c-format
 msgid ""
       "image=/boot/newinstall/vmlinuz\n"
@@ -320,19 +356,19 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:515
+#: boot-installer.xml:574
 #, no-c-format
 msgid "For more details, refer to the <citerefentry><refentrytitle>initrd</refentrytitle> <manvolnum>4</manvolnum></citerefentry> and <citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> man pages. Now run <userinput>lilo</userinput> and reboot."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:524
+#: boot-installer.xml:583
 #, no-c-format
 msgid "The procedure for <command>GRUB1</command> is quite similar. Locate your <filename>menu.lst</filename> in the <filename>/boot/grub/</filename> directory (or sometimes <filename>/boot/boot/grub/</filename>) and add an entry for the installer, for example (assuming <filename>/boot</filename> is on the first partition of the first disk in the system):"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:532
+#: boot-installer.xml:591
 #, no-c-format
 msgid ""
       "title  New Install\n"
@@ -342,13 +378,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:534
+#: boot-installer.xml:593
 #, no-c-format
 msgid "The procedure for <command>GRUB2</command> is very similar. The file is named <filename>grub.cfg</filename> instead of <filename>menu.lst</filename>. An entry for the installer would be for instance for example:"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:540
+#: boot-installer.xml:599
 #, no-c-format
 msgid ""
       "menuentry 'New Install' {\n"
@@ -361,133 +397,133 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:542
+#: boot-installer.xml:601
 #, no-c-format
 msgid "From here on, there should be no difference between <command>GRUB</command> or <command>LILO</command>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:551
+#: boot-installer.xml:610
 #, no-c-format
 msgid "Booting from USB Memory Stick"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:552
+#: boot-installer.xml:611
 #, 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 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:566 boot-installer.xml:1809
+#: boot-installer.xml:625 boot-installer.xml:1868
 #, no-c-format
 msgid "Booting from Floppies"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:567 boot-installer.xml:1817
+#: boot-installer.xml:626 boot-installer.xml:1876
 #, 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:574
+#: boot-installer.xml:633
 #, 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:580
+#: boot-installer.xml:639
 #, 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:590
+#: boot-installer.xml:649
 #, 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:599
+#: boot-installer.xml:658
 #, 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:605
+#: boot-installer.xml:664
 #, 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:614
+#: boot-installer.xml:673
 #, 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:624 boot-installer.xml:1234 boot-installer.xml:1376 boot-installer.xml:1430 boot-installer.xml:1753 boot-installer.xml:1863
+#: boot-installer.xml:683 boot-installer.xml:1293 boot-installer.xml:1435 boot-installer.xml:1489 boot-installer.xml:1812 boot-installer.xml:1922
 #, no-c-format
 msgid "Booting with TFTP"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:649
+#: boot-installer.xml:708
 #, no-c-format
 msgid "There are various ways to do a TFTP boot on i386."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:655
+#: boot-installer.xml:714
 #, no-c-format
 msgid "NIC or Motherboard that support PXE"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:656
+#: boot-installer.xml:715
 #, 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:667
+#: boot-installer.xml:726
 #, no-c-format
 msgid "NIC with Network BootROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:668
+#: boot-installer.xml:727
 #, no-c-format
 msgid "It could be that your Network Interface Card provides TFTP boot functionality."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:673
+#: boot-installer.xml:732
 #, 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:681
+#: boot-installer.xml:740
 #, no-c-format
 msgid "Etherboot"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:682
+#: boot-installer.xml:741
 #, 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:692
+#: boot-installer.xml:751
 #, no-c-format
 msgid "The Boot Screen"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:693
+#: boot-installer.xml:752
 #, 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"
@@ -504,25 +540,25 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:705
+#: boot-installer.xml:764
 #, no-c-format
 msgid "For a normal installation, select either the <quote>Graphical install</quote> or the <quote>Install</quote> entry &mdash; using either the arrow keys on your keyboard or by typing the first (highlighted) letter &mdash; and press &enterkey; to boot the installer. The <quote>Graphical install</quote> entry is already selected by default."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:713
+#: boot-installer.xml:772
 #, 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:719
+#: boot-installer.xml:778
 #, 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:728
+#: boot-installer.xml:787
 #, 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. To return to the boot menu after the help screens have been displayed, type 'menu' at the boot prompt and press &enterkey;. All help screens have a boot prompt at which the boot command can be typed: <informalexample><screen>\n"
@@ -531,313 +567,313 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:746
+#: boot-installer.xml:805
 #, 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:756
+#: boot-installer.xml:815
 #, 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:766
+#: boot-installer.xml:825
 #, 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:782
+#: boot-installer.xml:841
 #, no-c-format
 msgid "The Graphical Installer"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:783
+#: boot-installer.xml:842
 #, no-c-format
 msgid "The graphical version of the installer is only available for a limited number of architectures, including &arch-title;. The functionality of the graphical installer is essentially the same as that of the text-based installer as it basically uses the same programs, but with a different frontend."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:791
+#: boot-installer.xml:850
 #, no-c-format
 msgid "Although the functionality is identical, the graphical installer still has a few significant advantages. The main advantage is that it supports more languages, namely those that use a character set that cannot be displayed with the text-based <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
-#: boot-installer.xml:800
+#: boot-installer.xml:859
 #, 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
-#: boot-installer.xml:811
+#: boot-installer.xml:870
 #, 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
-#: boot-installer.xml:824
+#: boot-installer.xml:883
 #, 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
-#: boot-installer.xml:838
+#: boot-installer.xml:897
 #, no-c-format
 msgid "Just as with the text-based installer it is possible to add boot parameters when starting the graphical installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:844
+#: boot-installer.xml:903
 #, no-c-format
 msgid "The graphical installer requires significantly more memory to run than the text-based installer: &minimum-memory-gtk;. If insufficient memory is available, it will automatically fall back to the text-based <quote>newt</quote> frontend."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:851
+#: boot-installer.xml:910
 #, no-c-format
 msgid "If the amount of memory in your system is below &minimum-memory;, the graphical installer may fail to boot at all while booting the text-based installer would still work. Using the text-based installer is recommended for systems with little available memory."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:906
+#: boot-installer.xml:965
 #, no-c-format
 msgid "CD Contents"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:908
+#: boot-installer.xml:967
 #, 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:924
+#: boot-installer.xml:983
 #, 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:940
+#: boot-installer.xml:999
 #, 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:949
+#: boot-installer.xml:1008
 #, 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:961
+#: boot-installer.xml:1020
 #, 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:980
+#: boot-installer.xml:1039
 #, no-c-format
 msgid "IMPORTANT"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:981
+#: boot-installer.xml:1040
 #, 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:993
+#: boot-installer.xml:1052
 #, no-c-format
 msgid "Option 1: Booting from the Boot Option Maintenance Menu"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1000
+#: boot-installer.xml:1059
 #, 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:1006
+#: boot-installer.xml:1065
 #, 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:1012
+#: boot-installer.xml:1071
 #, 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:1023
+#: boot-installer.xml:1082
 #, 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:1034
+#: boot-installer.xml:1093
 #, 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:1046
+#: boot-installer.xml:1105
 #, 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:1056
+#: boot-installer.xml:1115
 #, no-c-format
 msgid "Option 2: Booting from the EFI Shell"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1057
+#: boot-installer.xml:1116
 #, 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:1068
+#: boot-installer.xml:1127
 #, 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:1074
+#: boot-installer.xml:1133
 #, 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:1088
+#: boot-installer.xml:1147
 #, 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:1095
+#: boot-installer.xml:1154
 #, 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:1102
+#: boot-installer.xml:1161
 #, 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:1109
+#: boot-installer.xml:1168
 #, 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:1123
+#: boot-installer.xml:1182
 #, no-c-format
 msgid "Installing using a Serial Console"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1125
+#: boot-installer.xml:1184
 #, 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:1136
+#: boot-installer.xml:1195
 #, 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:1143
+#: boot-installer.xml:1202
 #, 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:1154
+#: boot-installer.xml:1213
 #, 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:1163
+#: boot-installer.xml:1222
 #, 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:1172
+#: boot-installer.xml:1231
 #, no-c-format
 msgid "Selecting the Boot Kernel and Options"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1174
+#: boot-installer.xml:1233
 #, 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:1186
+#: boot-installer.xml:1245
 #, 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:1204
+#: boot-installer.xml:1263
 #, 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:1209
+#: boot-installer.xml:1268
 #, 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:1216
+#: boot-installer.xml:1275
 #, 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:1225 boot-installer.xml:1362
+#: boot-installer.xml:1284 boot-installer.xml:1421
 #, 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:1236
+#: boot-installer.xml:1295
 #, 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:1271
+#: boot-installer.xml:1330
 #, 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:1282
+#: boot-installer.xml:1341
 #, no-c-format
 msgid "Configuring the Server"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1283
+#: boot-installer.xml:1342
 #, no-c-format
 msgid ""
       "A suitable TFTP entry for network booting an IA-64 system looks something like this: <informalexample><screen>\n"
@@ -850,13 +886,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1293
+#: boot-installer.xml:1352
 #, 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:1303
+#: boot-installer.xml:1362
 #, no-c-format
 msgid ""
       "# cd /var/lib/tftp\n"
@@ -868,37 +904,37 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1303
+#: boot-installer.xml:1362
 #, 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:1320
+#: boot-installer.xml:1379
 #, no-c-format
 msgid "Configuring the Client"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1321
+#: boot-installer.xml:1380
 #, 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:1353
+#: boot-installer.xml:1412
 #, 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:1379 boot-installer.xml:1403
+#: boot-installer.xml:1438 boot-installer.xml:1462
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1380
+#: boot-installer.xml:1439
 #, no-c-format
 msgid ""
       "After entering the command monitor use <informalexample><screen>\n"
@@ -909,19 +945,19 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1400 boot-installer.xml:2155
+#: boot-installer.xml:1459 boot-installer.xml:2214
 #, no-c-format
 msgid "Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1404
+#: boot-installer.xml:1463
 #, 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:1409
+#: boot-installer.xml:1468
 #, 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"
@@ -930,43 +966,43 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1419
+#: boot-installer.xml:1478
 #, no-c-format
 msgid "bootp(): append=\"root=/dev/sda1\""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1462
+#: boot-installer.xml:1521
 #, no-c-format
 msgid "s390 Limitations"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1463
+#: boot-installer.xml:1522
 #, 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:1468
+#: boot-installer.xml:1527
 #, 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:1479
+#: boot-installer.xml:1538
 #, no-c-format
 msgid "s390 Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1480
+#: boot-installer.xml:1539
 #, no-c-format
 msgid "On S/390 you can append boot parameters in the parm file. This file can either be in ASCII or EBCDIC format. It needs to be fixed-width with 80 characters per line. A sample parm file <filename>parmfile.debian</filename> is provided with the installation images. If a parameter is too long to fit into the 80 characters limit it can simply be continued in the first column of the next line. All the lines are concatenated without spaces when being passed to the kernel."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1497
+#: boot-installer.xml:1556
 #, no-c-format
 msgid ""
       "If you boot the installer in a logical partition (LPAR) or virtual machine (VM) where a lot of devices are visible, you can instruct the kernel to restrict the list to a fixed set of devices. This is advised for the installer's boot process if a lot of disks are visible, most likely in LPAR mode. The <quote>cio_ignore</quote> option supports both a blacklist (to only disallow a few devices) and a whitelist (to only allow specific devices): <informalexample role=\"example\"><screen>\n"
@@ -978,13 +1014,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1562
+#: boot-installer.xml:1621
 #, 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:1571
+#: boot-installer.xml:1630
 #, 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"
@@ -993,79 +1029,79 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1582
+#: boot-installer.xml:1641
 #, no-c-format
 msgid "0 &gt; boot cd:,\\install\\yaboot"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1584
+#: boot-installer.xml:1643
 #, 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:1593
+#: boot-installer.xml:1652
 #, 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:1599
+#: boot-installer.xml:1658
 #, no-c-format
 msgid "boot cd install/pegasos"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1601
+#: boot-installer.xml:1660
 #, no-c-format
 msgid "On YDL Powerstation machine, pres <keycap>s</keycap> immediately after <quote>Press 's' to enter Open Firmware</quote> message, when SLOF prompt appears type"
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1606
+#: boot-installer.xml:1665
 #, no-c-format
 msgid "0 > boot cdrom"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1612
+#: boot-installer.xml:1671
 #, no-c-format
 msgid "Booting from Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1618
+#: boot-installer.xml:1677
 #, 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:1624
+#: boot-installer.xml:1683
 #, 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:1644
+#: boot-installer.xml:1703
 #, no-c-format
 msgid "Booting OldWorld PowerMacs from MacOS"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1645
+#: boot-installer.xml:1704
 #, 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:1663
+#: boot-installer.xml:1722
 #, no-c-format
 msgid "Booting NewWorld Macs from OpenFirmware"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1664
+#: boot-installer.xml:1723
 #, 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"
@@ -1076,31 +1112,31 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1696
+#: boot-installer.xml:1755
 #, no-c-format
 msgid "Booting from USB memory stick"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1697
+#: boot-installer.xml:1756
 #, no-c-format
 msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1703
+#: boot-installer.xml:1762
 #, 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:1712
+#: boot-installer.xml:1771
 #, 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:1724
+#: boot-installer.xml:1783
 #, no-c-format
 msgid ""
       "Having worked out the device path, use a command like this to boot the installer: <informalexample><screen>\n"
@@ -1109,25 +1145,25 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1738
+#: boot-installer.xml:1797
 #, 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:1744
+#: boot-installer.xml:1803
 #, 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:1778
+#: boot-installer.xml:1837
 #, no-c-format
 msgid "Currently, PReP and New World PowerMac systems support netbooting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1782
+#: boot-installer.xml:1841
 #, 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"
@@ -1140,751 +1176,751 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1810
+#: boot-installer.xml:1869
 #, 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:1822
+#: boot-installer.xml:1881
 #, 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:1828
+#: boot-installer.xml:1887
 #, 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:1835
+#: boot-installer.xml:1894
 #, 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:1846
+#: boot-installer.xml:1905
 #, no-c-format
 msgid "PowerPC Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1847
+#: boot-installer.xml:1906
 #, 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:1888
+#: boot-installer.xml:1947
 #, 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:1943
+#: boot-installer.xml:2002
 #, 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:1952
+#: boot-installer.xml:2011
 #, no-c-format
 msgid "IDPROM Messages"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1953
+#: boot-installer.xml:2012
 #, 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:1972
+#: boot-installer.xml:2031
 #, no-c-format
 msgid "Accessibility"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1973
+#: boot-installer.xml:2032
 #, 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:1993
+#: boot-installer.xml:2052
 #, no-c-format
 msgid "Installer front-end"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1994
+#: boot-installer.xml:2053
 #, no-c-format
 msgid "The &debian; installer supports several front-ends for asking questions, with varying convenience for accessibility: notably, <userinput>text</userinput> uses plain text while <userinput>newt</userinput> uses text-based dialog boxes. The choice can be made at the boot prompt, see the documentation for <userinput>DEBIAN_FRONTEND</userinput> in <xref linkend=\"installer-args\"/>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2006
+#: boot-installer.xml:2065
 #, no-c-format
 msgid "USB Braille Displays"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2007
+#: boot-installer.xml:2066
 #, 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:2022
+#: boot-installer.xml:2081
 #, no-c-format
 msgid "Serial Braille Displays"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2023
+#: boot-installer.xml:2082
 #, 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:2046 boot-installer.xml:3053
+#: boot-installer.xml:2105 boot-installer.xml:3114
 #, no-c-format
 msgid "Software Speech Synthesis"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2047
+#: boot-installer.xml:2106
 #, no-c-format
 msgid "Support for software speech synthesis is available on all installer images which have the graphical installer, i.e. all netinst, CD and DVD images, and the netboot gtk variant. It can be activated by selecting it in the boot menu by typing <userinput>s</userinput> &enterkey;. The textual version of the installer will then be automatically selected, and support for software speech synthesis will be automatically installed on the target system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2056
+#: boot-installer.xml:2115
 #, no-c-format
 msgid "The first question (language) is spoken in english, and the remainder of installation is spoken in the selected language (if available in <classname>espeak</classname>)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2062
+#: boot-installer.xml:2121
 #, no-c-format
 msgid "The default speech rate is quite slow. To make it faster, press <keycombo><keycap>CapsLock</keycap><keycap>6</keycap></keycombo>. To make it slower, press <keycombo><keycap>CapsLock</keycap><keycap>5</keycap></keycombo>. The default volume should be medium. To make it louder, press <keycombo><keycap>CapsLock</keycap><keycap>2</keycap></keycombo>. To make it quieter, press <keycombo><keycap>CapsLock</keycap><keycap>1</keycap></keycombo>. To get more details on the browsing shortcuts, see the <ulink url=\"&url-speakup-guide;\">Speakup guide</ulink>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2081
+#: boot-installer.xml:2140
 #, no-c-format
 msgid "Hardware Speech Synthesis"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2082
+#: boot-installer.xml:2141
 #, no-c-format
 msgid "Support for hardware speech synthesis devices is available on all installer images which have the graphical installer, i.e. all netinst, CD and DVD images, and the netboot gtk variant. You thus need to select a <quote>Graphical install</quote> entry in the boot menu."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2089
+#: boot-installer.xml:2148
 #, 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-guide;\">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:2104
+#: boot-installer.xml:2163
 #, no-c-format
 msgid "Board Devices"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2105
+#: boot-installer.xml:2164
 #, 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:2113
+#: boot-installer.xml:2172
 #, 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:2121
+#: boot-installer.xml:2180
 #, no-c-format
 msgid "High-Contrast Theme"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2122
+#: boot-installer.xml:2181
 #, no-c-format
 msgid "For users with low vision, the installer can use a high-contrast color theme that makes it more readable. To enable it, append the <userinput>theme=dark</userinput> boot parameter."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2131
+#: boot-installer.xml:2190
 #, no-c-format
 msgid "Preseeding"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2132
+#: boot-installer.xml:2191
 #, no-c-format
 msgid "Alternatively, &debian; can be installed completely automatically by using preseeding. This is documented in <xref linkend=\"appendix-preseed\"/>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2140
+#: boot-installer.xml:2199
 #, no-c-format
 msgid "Accessibility of the installed system"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2141
+#: boot-installer.xml:2200
 #, no-c-format
 msgid "Documentation on accessibility of the installed system is available on the <ulink url=\"&url-debian-wiki-accessibility;\">Debian Accessibility wiki page</ulink>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2156
+#: boot-installer.xml:2215
 #, 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:2163
+#: boot-installer.xml:2222
 #, 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:2170
+#: boot-installer.xml:2229
 #, 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: title
-#: boot-installer.xml:2182
+#: boot-installer.xml:2241
 #, no-c-format
 msgid "Boot console"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2184
+#: boot-installer.xml:2243
 #, 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>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2196
+#: boot-installer.xml:2255
 #, no-c-format
-msgid "You may need to specify parameters for the serial port, such as speed and parity, for instance <userinput>console=ttyS0,9600n8</userinput>; other typical speeds may be 57600 or 115200."
+msgid "You may need to specify parameters for the serial port, such as speed and parity, for instance <userinput>console=ttyS0,9600n8</userinput>; other typical speeds may be 57600 or 115200. Be sure to specify this option after <quote>---</quote>, so that it is copied into the bootloader configuration for the installed system (if supported by the installer for the bootloader)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2202
+#: boot-installer.xml:2263
 #, no-c-format
 msgid "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>. If you are using a virtualization tool which does not provide conversion into such terminals types itself, e.g. QEMU/KVM, you can start it inside a <command>screen</command> session. That will indeed perform translation into the <literal>screen</literal> terminal type, which is very close to <literal>vt102</literal>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2218
+#: boot-installer.xml:2279
 #, 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:2230
+#: boot-installer.xml:2291
 #, no-c-format
 msgid "&debian; Installer Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2231
+#: boot-installer.xml:2292
 #, 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:2244
+#: boot-installer.xml:2305
 #, 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:2256
+#: boot-installer.xml:2317
 #, no-c-format
 msgid "debconf/priority (priority)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2257
+#: boot-installer.xml:2318
 #, no-c-format
 msgid "This parameter sets the lowest priority of messages to be displayed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2261
+#: boot-installer.xml:2322
 #, 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:2268
+#: boot-installer.xml:2329
 #, 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:2282
+#: boot-installer.xml:2343
 #, no-c-format
 msgid "DEBIAN_FRONTEND"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2283
+#: boot-installer.xml:2344
 #, 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:2314
+#: boot-installer.xml:2375
 #, no-c-format
 msgid "BOOT_DEBUG"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2315
+#: boot-installer.xml:2376
 #, 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:2324
+#: boot-installer.xml:2385
 #, no-c-format
 msgid "BOOT_DEBUG=0"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2325
+#: boot-installer.xml:2386
 #, no-c-format
 msgid "This is the default."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2329
+#: boot-installer.xml:2390
 #, no-c-format
 msgid "BOOT_DEBUG=1"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2330
+#: boot-installer.xml:2391
 #, no-c-format
 msgid "More verbose than usual."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2334
+#: boot-installer.xml:2395
 #, no-c-format
 msgid "BOOT_DEBUG=2"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2335
+#: boot-installer.xml:2396
 #, no-c-format
 msgid "Lots of debugging information."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2339
+#: boot-installer.xml:2400
 #, no-c-format
 msgid "BOOT_DEBUG=3"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2340
+#: boot-installer.xml:2401
 #, 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:2354
+#: boot-installer.xml:2415
 #, no-c-format
 msgid "INSTALL_MEDIA_DEV"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2355
+#: boot-installer.xml:2416
 #, 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:2361
+#: boot-installer.xml:2422
 #, 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:2372
+#: boot-installer.xml:2433
 #, no-c-format
 msgid "log_host"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2373
+#: boot-installer.xml:2434
 #, no-c-format
 msgid "log_port"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2374
+#: boot-installer.xml:2435
 #, 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:2385
+#: boot-installer.xml:2446
 #, no-c-format
 msgid "lowmem"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2386
+#: boot-installer.xml:2447
 #, 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:2396
+#: boot-installer.xml:2457
 #, no-c-format
 msgid "noshell"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2397
+#: boot-installer.xml:2458
 #, 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:2406
+#: boot-installer.xml:2467
 #, no-c-format
 msgid "debian-installer/framebuffer (fb)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2407
+#: boot-installer.xml:2468
 #, 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:2416
+#: boot-installer.xml:2477
 #, no-c-format
 msgid "Such problems have been reported on hppa."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2420
+#: boot-installer.xml:2481
 #, 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:2434
+#: boot-installer.xml:2495
 #, no-c-format
 msgid "debian-installer/theme (theme)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2435
+#: boot-installer.xml:2496
 #, 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:2447 boot-installer.xml:2680
+#: boot-installer.xml:2508 boot-installer.xml:2741
 #, no-c-format
 msgid "netcfg/disable_autoconfig"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2448
+#: boot-installer.xml:2509
 #, no-c-format
 msgid "By default, the &d-i; automatically probes for network configuration via IPv6 autoconfiguration and DHCP. If the probe succeeds, you won't have a chance to review and change the obtained settings. You can get to the manual network setup only in case the automatic configuration fails."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2455
+#: boot-installer.xml:2516
 #, no-c-format
 msgid "If you have an IPv6 router or a DHCP server on your local network, but want to avoid them because e.g. they give wrong answers, you can use the parameter <userinput>netcfg/disable_autoconfig=true</userinput> to prevent any automatic configuration of the network (neither v4 nor v6) and to enter the information manually."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2466
+#: boot-installer.xml:2527
 #, no-c-format
 msgid "hw-detect/start_pcmcia"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2467
+#: boot-installer.xml:2528
 #, 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:2477
+#: boot-installer.xml:2538
 #, no-c-format
 msgid "disk-detect/dmraid/enable (dmraid)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2478
+#: boot-installer.xml:2539
 #, 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:2489
+#: boot-installer.xml:2550
 #, no-c-format
 msgid "preseed/url (url)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2490
+#: boot-installer.xml:2551
 #, 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:2499
+#: boot-installer.xml:2560
 #, no-c-format
 msgid "preseed/file (file)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2500
+#: boot-installer.xml:2561
 #, 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:2509
+#: boot-installer.xml:2570
 #, no-c-format
 msgid "preseed/interactive"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2510
+#: boot-installer.xml:2571
 #, 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:2522
+#: boot-installer.xml:2583
 #, no-c-format
 msgid "auto-install/enable (auto)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2523
+#: boot-installer.xml:2584
 #, 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:2534
+#: boot-installer.xml:2595
 #, no-c-format
 msgid "finish-install/keep-consoles"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2535
+#: boot-installer.xml:2596
 #, 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:2546
+#: boot-installer.xml:2607
 #, no-c-format
 msgid "cdrom-detect/eject"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2547
+#: boot-installer.xml:2608
 #, 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:2556
+#: boot-installer.xml:2617
 #, 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:2567
+#: boot-installer.xml:2628
 #, no-c-format
 msgid "base-installer/install-recommends (recommends)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2568
+#: boot-installer.xml:2629
 #, 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:2575
+#: boot-installer.xml:2636
 #, 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:2587
+#: boot-installer.xml:2648
 #, no-c-format
 msgid "debian-installer/allow_unauthenticated"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2588
+#: boot-installer.xml:2649
 #, 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:2599
+#: boot-installer.xml:2660
 #, no-c-format
 msgid "ramdisk_size"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2600
+#: boot-installer.xml:2661
 #, 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:2610
+#: boot-installer.xml:2671
 #, no-c-format
 msgid "rescue/enable"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2611
+#: boot-installer.xml:2672
 #, 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:2624
+#: boot-installer.xml:2685
 #, no-c-format
 msgid "Using boot parameters to answer questions"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2625
+#: boot-installer.xml:2686
 #, 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:2637
+#: boot-installer.xml:2698
 #, no-c-format
 msgid "debian-installer/language (language)"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2638
+#: boot-installer.xml:2699
 #, no-c-format
 msgid "debian-installer/country (country)"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2639
+#: boot-installer.xml:2700
 #, no-c-format
 msgid "debian-installer/locale (locale)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2640
+#: boot-installer.xml:2701
 #, 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:2645
+#: boot-installer.xml:2706
 #, 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:2654
+#: boot-installer.xml:2715
 #, 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:2666
+#: boot-installer.xml:2727
 #, no-c-format
 msgid "anna/choose_modules (modules)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2667
+#: boot-installer.xml:2728
 #, 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:2681
+#: boot-installer.xml:2742
 #, no-c-format
 msgid "Set to <userinput>true</userinput> if you want to disable IPv6 autoconfiguration and DHCP and instead force static network configuration."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2690
+#: boot-installer.xml:2751
 #, no-c-format
 msgid "mirror/protocol (protocol)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2691
+#: boot-installer.xml:2752
 #, 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:2704
+#: boot-installer.xml:2765
 #, no-c-format
 msgid "tasksel:tasksel/first (tasks)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2705
+#: boot-installer.xml:2766
 #, 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:2719
+#: boot-installer.xml:2780
 #, no-c-format
 msgid "Passing parameters to kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2720
+#: boot-installer.xml:2781
 #, 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:2733
+#: boot-installer.xml:2794
 #, 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:2740
+#: boot-installer.xml:2801
 #, no-c-format
 msgid ""
       "The syntax to use to set parameters for modules is: <informalexample><screen>\n"
@@ -1893,127 +1929,127 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:2750
+#: boot-installer.xml:2811
 #, no-c-format
 msgid "3c509.xcvr=3 3c509.irq=10"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2756
+#: boot-installer.xml:2817
 #, no-c-format
 msgid "Blacklisting kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2757
+#: boot-installer.xml:2818
 #, 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:2766
+#: boot-installer.xml:2827
 #, 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:2774
+#: boot-installer.xml:2835
 #, 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:2790
+#: boot-installer.xml:2851
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2795
+#: boot-installer.xml:2856
 #, no-c-format
 msgid "CD-ROM Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2796
+#: boot-installer.xml:2857
 #, 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:2803
+#: boot-installer.xml:2864
 #, 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:2809
+#: boot-installer.xml:2870
 #, no-c-format
 msgid "There are two very simple things that you should try first."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2814
+#: boot-installer.xml:2875
 #, 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:2820
+#: boot-installer.xml:2881
 #, 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 very old CD-ROM drives are known to be resolved in this way."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2830
+#: boot-installer.xml:2891
 #, 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:2836
+#: boot-installer.xml:2897
 #, 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:2844
+#: boot-installer.xml:2905
 #, no-c-format
 msgid "Common issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2847
+#: boot-installer.xml:2908
 #, 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:2864
+#: boot-installer.xml:2925
 #, no-c-format
 msgid "Some very old CD-ROM drives do not work correctly if <quote>direct memory access</quote> (DMA) is enabled for them."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2875
+#: boot-installer.xml:2936
 #, no-c-format
 msgid "How to investigate and maybe solve issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2876
+#: boot-installer.xml:2937
 #, no-c-format
 msgid "If the CD-ROM fails to boot, try the suggestions listed below."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2881
+#: boot-installer.xml:2942
 #, no-c-format
 msgid "Check that your BIOS actually supports booting from CD-ROM (only an issue for very old systems) and that CD booting is enabled in the BIOS."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2888
+#: boot-installer.xml:2949
 #, 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"
@@ -2023,7 +2059,7 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:2901
+#: boot-installer.xml:2962
 #, no-c-format
 msgid ""
       "$ dd if=/dev/cdrom | \\\n"
@@ -2036,19 +2072,19 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2906
+#: boot-installer.xml:2967
 #, 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:2918
+#: boot-installer.xml:2979
 #, 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:2925
+#: boot-installer.xml:2986
 #, 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"
@@ -2061,13 +2097,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2939
+#: boot-installer.xml:3000
 #, 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:2947
+#: boot-installer.xml:3008
 #, 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"
@@ -2076,7 +2112,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2957
+#: boot-installer.xml:3018
 #, no-c-format
 msgid ""
       "Check if DMA is currently enabled: <informalexample><screen>\n"
@@ -2089,151 +2125,151 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2972
+#: boot-installer.xml:3033
 #, 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:2987
+#: boot-installer.xml:3048
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2989
+#: boot-installer.xml:3050
 #, 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:2994
+#: boot-installer.xml:3055
 #, 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:3003
+#: boot-installer.xml:3064
 #, 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:3012
+#: boot-installer.xml:3073
 #, 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:3018
+#: boot-installer.xml:3079
 #, 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:3024
+#: boot-installer.xml:3085
 #, 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:3033
+#: boot-installer.xml:3094
 #, no-c-format
 msgid "Boot Configuration"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3035
+#: boot-installer.xml:3096
 #, 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:3044
+#: boot-installer.xml:3105
 #, no-c-format
 msgid "In some cases, malfunctions can be caused by missing device firmware (see <xref linkend=\"hardware-firmware\"/> and <xref linkend=\"loading-firmware\"/>)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3055
+#: boot-installer.xml:3116
 #, 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:3066
+#: boot-installer.xml:3127
 #, no-c-format
 msgid "dmesg"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:3068
+#: boot-installer.xml:3129
 #, no-c-format
 msgid "lspci"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:3070
+#: boot-installer.xml:3131
 #, no-c-format
 msgid "lsmod"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:3072
+#: boot-installer.xml:3133
 #, no-c-format
 msgid "amixer"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3080 boot-installer.xml:3191
+#: boot-installer.xml:3141 boot-installer.xml:3252
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3081
+#: boot-installer.xml:3142
 #, 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:3132
+#: boot-installer.xml:3193
 #, 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:3146
+#: boot-installer.xml:3207
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3147
+#: boot-installer.xml:3208
 #, no-c-format
 msgid "Some very old laptop models produced by Dell are known to crash when PCMCIA device detection tries to access some hardware addresses. Other laptops may display similar problems. If you experience such a problem and you don't need PCMCIA support during the installation, you can disable PCMCIA using the <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:3157
+#: boot-installer.xml:3218
 #, 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: para
-#: boot-installer.xml:3192
+#: boot-installer.xml:3253
 #, no-c-format
 msgid "There are some common installation problems that are worth mentioning."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3198
+#: boot-installer.xml:3259
 #, no-c-format
 msgid "Misdirected video output"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3199
+#: boot-installer.xml:3260
 #, 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"
@@ -2243,85 +2279,85 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3213
+#: boot-installer.xml:3274
 #, 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:3224
+#: boot-installer.xml:3285
 #, no-c-format
 msgid "Failure to Boot or Install from CD-ROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3225
+#: boot-installer.xml:3286
 #, 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:3231
+#: boot-installer.xml:3292
 #, no-c-format
 msgid "We recommend to install such systems by netbooting the installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3240
+#: boot-installer.xml:3301
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3242
+#: boot-installer.xml:3303
 #, 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:3267
+#: boot-installer.xml:3328
 #, no-c-format
 msgid "Reporting Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3268
+#: boot-installer.xml:3329
 #, 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:3279
+#: boot-installer.xml:3340
 #, 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:3290
+#: boot-installer.xml:3351
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3291
+#: boot-installer.xml:3352
 #, 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:3298
+#: boot-installer.xml:3359
 #, 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:3304
+#: boot-installer.xml:3365
 #, 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:3314
+#: boot-installer.xml:3375
 #, 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 32b55ccca..701abb9db 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: 2014-10-05 18:15+0000\n"
+"POT-Creation-Date: 2015-01-09 19:07+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"
@@ -405,7 +405,7 @@ msgid "Both AMD64 and Intel 64 processors are supported."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:282 hardware.xml:603 hardware.xml:622 hardware.xml:701 hardware.xml:759 hardware.xml:789
+#: hardware.xml:282 hardware.xml:627 hardware.xml:646 hardware.xml:704 hardware.xml:762 hardware.xml:792
 #, no-c-format
 msgid "CPU, Main Boards, and Video Support"
 msgstr ""
@@ -581,1391 +581,1409 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:497
 #, no-c-format
-msgid "LinkSprite pcDuino"
+msgid "LeMaker Banana Pi"
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:500
 #, no-c-format
-msgid "Mele A1000"
+msgid "LinkSprite pcDuino"
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:503
 #, no-c-format
-msgid "Miniand Hackberry"
+msgid "Mele A1000"
 msgstr ""
 
 #. Tag: para
 #: hardware.xml:506
 #, no-c-format
-msgid "Olimex A10-Olinuxino-LIME / A10s-Olinuxino Micro / A13-Olinuxino / A13-Olinuxino Micro / A20-Olinuxino Micro"
+msgid "Miniand Hackberry"
+msgstr ""
+
+#. Tag: para
+#: hardware.xml:509
+#, no-c-format
+msgid "Olimex A10-Olinuxino-LIME / A10s-Olinuxino Micro / A13-Olinuxino / A13-Olinuxino Micro / A20-Olinuxino-LIME / A20-Olinuxino Micro"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:510
+#: hardware.xml:514
 #, no-c-format
 msgid "PineRiver Mini X-Plus"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:516
+#: hardware.xml:520
 #, no-c-format
 msgid "System support for Allwinner sunXi-based devices is limited to drivers and device-tree information available in the mainline Linux kernel. The android-derived linux-sunxi.org 3.4 kernel series is not supported by Debian."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:522
+#: hardware.xml:526
 #, no-c-format
 msgid "The mainline Linux kernel generally supports serial console, ethernet, SATA, USB and MMC/SD-cards on Allwinner A10 and A20 SOCs, but it does not have local display (HDMI/VGA/LVDS) and audio support. The NAND flash memory that is built into some sunXi-based systems is not supported."
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:533
+#: hardware.xml:537
 #, no-c-format
 msgid "SolidRun Cubox-i2eX / Cubox-i4Pro"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:535
+#: hardware.xml:539
 #, no-c-format
-msgid "The Cubox-i series is a set of small, cubical-shaped systems based on the Freescale i.MX6 SOC family. System support for the Cubox-i series is limited to drivers and device-tree information available in the mainline Linux kernel; the Freescale 3.0 kernel series for the Cubox-i is not supported by Debian. Available drivers in the mainline kernel include serial console, ethernet, USB, MMC/SD-card and basic local display support over HDMI."
+msgid "The Cubox-i series is a set of small, cubical-shaped systems based on the Freescale i.MX6 SOC family. System support for the Cubox-i series is limited to drivers and device-tree information available in the mainline Linux kernel; the Freescale 3.0 kernel series for the Cubox-i is not supported by Debian. Available drivers in the mainline kernel include serial console, ethernet, USB, MMC/SD-card and display support over HDMI (console and X11). In addition to that, the eSATA port on the Cubox-i4Pro is supported."
+msgstr ""
+
+#. Tag: term
+#: hardware.xml:554
+#, no-c-format
+msgid "Wandboard Quad"
+msgstr ""
+
+#. Tag: para
+#: hardware.xml:556
+#, no-c-format
+msgid "The Wandboard Quad is a development board based on the Freescale i.MX6 Quad SoC. System support for it is limited to drivers and device-tree information available in the mainline Linux kernel; the wandboard-specific 3.0 and 3.10 kernel series from wandboard.org are not supported by Debian. The mainline kernel includes driver support for serial console, display via HDMI (console and X11), ethernet, USB, MMC/SD and SATA. Support for the onboard audio options (analog, S/PDIF, HDMI-Audio) and for the onboard WLAN/Bluetooth module is not available in &debian; 8."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:550
+#: hardware.xml:574
 #, no-c-format
 msgid "Generally, the ARM multiplatform support in the Linux kernel allows running &d-i; on armhf systems not explicitly listed above, as long as the kernel used by &d-i; has support for the target system's components and a device-tree file for the target is available. In these cases, the installer can usually provide a working userland installation, but it probably cannot automatically make the system bootable, as doing that in many cases requires device-specific information."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:561
+#: hardware.xml:585
 #, no-c-format
 msgid "When using &d-i; on such systems, you have to manually make the system bootable at the end of the installation, e.g. by running the required commands in a shell started from within &d-i;."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:570
+#: hardware.xml:594
 #, no-c-format
 msgid "Platforms no longer supported by Debian/armhf"
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:574
+#: hardware.xml:598
 #, no-c-format
 msgid "EfikaMX"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:575
+#: hardware.xml:599
 #, no-c-format
 msgid "The EfikaMX platform (Genesi Efika Smartbook and Genesi EfikaMX nettop) has been supported in &debian; 7 with a platform-specific kernel, but is not supported anymore from &debian; 8 onwards. The code required to build the formerly used platform-specific kernel has been removed from the upstream Linux kernel source in 2012, so Debian cannot provide newer builds."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:583
+#: hardware.xml:607
 #, no-c-format
 msgid "Using the armmp multiplatform kernel on the EfikaMX platform would require device-tree support for it, which is currently not available."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:604
+#: hardware.xml:628
 #, 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:623
+#: hardware.xml:647
 #, 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:631 hardware.xml:736
+#: hardware.xml:655 hardware.xml:739
 #, no-c-format
 msgid "<title>CPU</title>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:632
+#: hardware.xml:656
 #, 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:639
+#: hardware.xml:663
 #, 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>."
+msgid "However, &debian; GNU/Linux &releasename; will <emphasis>not</emphasis> run on 486 or earlier processors. Despite the architecture name \"i386\", support for actual 80386 and 80486 processors (and their clones) was dropped with the Sarge (r3.1) and Squeeze (r6.0) releases of &debian;, respectively. The Intel Pentium and clones, including those without an FPU (Floating-Point Unit or math coprocessor), are supported. The Intel Quark is <emphasis>not</emphasis> supported, due to hardware errata."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:672
+#: hardware.xml:675
 #, no-c-format
 msgid "If your system has a 64-bit processor from the AMD64 or Intel 64 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:681
+#: hardware.xml:684
 #, no-c-format
 msgid "I/O Bus"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:682
+#: hardware.xml:685
 #, 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:702
+#: hardware.xml:705
 #, 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:737
+#: hardware.xml:740
 #, 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:743
+#: hardware.xml:746
 #, 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:760
+#: hardware.xml:763
 #, no-c-format
 msgid "&debian; on &arch-title; supports the following platforms: <itemizedlist> <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:790
+#: hardware.xml:793
 #, 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:811
+#: hardware.xml:814
 #, no-c-format
 msgid "Kernel Flavours"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:813
+#: hardware.xml:816
 #, no-c-format
 msgid "There are two flavours of the powerpc kernel in &debian;, based on the CPU type:"
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:820
+#: hardware.xml:823
 #, no-c-format
 msgid "<term>powerpc</term>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:821
+#: hardware.xml:824
 #, no-c-format
 msgid "This kernel flavour 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:831
+#: hardware.xml:834
 #, no-c-format
 msgid "powerpc-smp"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:832
+#: hardware.xml:835
 #, no-c-format
 msgid "All Apple PowerMac G4 SMP machines."
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:840
+#: hardware.xml:843
 #, no-c-format
 msgid "power64"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:841
+#: hardware.xml:844
 #, no-c-format
 msgid "The power64 kernel flavour supports the following CPUs:"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:845
+#: hardware.xml:848
 #, 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:851
+#: hardware.xml:854
 #, 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:856
+#: hardware.xml:859
 #, no-c-format
 msgid "Systems using the PPC970 processor (Apple G5, YDL PowerStation, IBM Intellistation POWER 185) are also based on the POWER4 architecture, and use this kernel flavour."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:862
+#: hardware.xml:865
 #, no-c-format
 msgid "Newer IBM systems using POWER5, POWER6, and POWER7 processors."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:895
+#: hardware.xml:898
 #, no-c-format
 msgid "Power Macintosh (pmac) subarchitecture"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:897
+#: hardware.xml:900
 #, 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:904
+#: hardware.xml:907
 #, 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:912
+#: hardware.xml:915
 #, 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:920
+#: hardware.xml:923
 #, 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:936 hardware.xml:1071 hardware.xml:1115 hardware.xml:1148
+#: hardware.xml:939 hardware.xml:1074 hardware.xml:1118 hardware.xml:1151
 #, no-c-format
 msgid "Model Name/Number"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:937
+#: hardware.xml:940
 #, no-c-format
 msgid "Generation"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:943
+#: hardware.xml:946
 #, no-c-format
 msgid "Apple"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:944
+#: hardware.xml:947
 #, no-c-format
 msgid "iMac Bondi Blue, 5 Flavors, Slot Loading"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:945 hardware.xml:948 hardware.xml:951 hardware.xml:954 hardware.xml:957 hardware.xml:960 hardware.xml:963 hardware.xml:966 hardware.xml:969 hardware.xml:972 hardware.xml:975 hardware.xml:978 hardware.xml:981 hardware.xml:984 hardware.xml:987 hardware.xml:990
+#: hardware.xml:948 hardware.xml:951 hardware.xml:954 hardware.xml:957 hardware.xml:960 hardware.xml:963 hardware.xml:966 hardware.xml:969 hardware.xml:972 hardware.xml:975 hardware.xml:978 hardware.xml:981 hardware.xml:984 hardware.xml:987 hardware.xml:990 hardware.xml:993
 #, no-c-format
 msgid "NewWorld"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:947
+#: hardware.xml:950
 #, no-c-format
 msgid "iMac Summer 2000, Early 2001"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:950
+#: hardware.xml:953
 #, no-c-format
 msgid "iMac G5"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:953
+#: hardware.xml:956
 #, no-c-format
 msgid "iBook, iBook SE, iBook Dual USB"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:956
+#: hardware.xml:959
 #, no-c-format
 msgid "iBook2"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:959
+#: hardware.xml:962
 #, no-c-format
 msgid "iBook G4"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:962
+#: hardware.xml:965
 #, no-c-format
 msgid "Power Macintosh Blue and White (B&amp;W) G3"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:965
+#: hardware.xml:968
 #, no-c-format
 msgid "Power Macintosh G4 PCI, AGP, Cube"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:968
+#: hardware.xml:971
 #, no-c-format
 msgid "Power Macintosh G4 Gigabit Ethernet"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:971
+#: hardware.xml:974
 #, no-c-format
 msgid "Power Macintosh G4 Digital Audio, Quicksilver"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:974
+#: hardware.xml:977
 #, no-c-format
 msgid "Power Macintosh G5"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:977
+#: hardware.xml:980
 #, no-c-format
 msgid "PowerBook G3 FireWire Pismo (2000)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:980
+#: hardware.xml:983
 #, no-c-format
 msgid "PowerBook G3 Lombard (1999)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:983
+#: hardware.xml:986
 #, no-c-format
 msgid "PowerBook G4 Titanium"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:986
+#: hardware.xml:989
 #, no-c-format
 msgid "PowerBook G4 Aluminum"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:989
+#: hardware.xml:992
 #, no-c-format
 msgid "Xserve G5"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:992
+#: hardware.xml:995
 #, no-c-format
 msgid "Performa 4400, 54xx, 5500"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:993 hardware.xml:996 hardware.xml:999 hardware.xml:1002 hardware.xml:1005 hardware.xml:1008 hardware.xml:1011 hardware.xml:1014 hardware.xml:1017 hardware.xml:1020 hardware.xml:1023 hardware.xml:1026 hardware.xml:1032 hardware.xml:1035 hardware.xml:1041 hardware.xml:1047 hardware.xml:1053
+#: hardware.xml:996 hardware.xml:999 hardware.xml:1002 hardware.xml:1005 hardware.xml:1008 hardware.xml:1011 hardware.xml:1014 hardware.xml:1017 hardware.xml:1020 hardware.xml:1023 hardware.xml:1026 hardware.xml:1029 hardware.xml:1035 hardware.xml:1038 hardware.xml:1044 hardware.xml:1050 hardware.xml:1056
 #, no-c-format
 msgid "OldWorld"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:995
+#: hardware.xml:998
 #, no-c-format
 msgid "Performa 6360, 6400, 6500"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:998
+#: hardware.xml:1001
 #, no-c-format
 msgid "Power Macintosh 4400, 5400"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1001
+#: hardware.xml:1004
 #, no-c-format
 msgid "Power Macintosh 7200, 7300, 7500, 7600"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1004
+#: hardware.xml:1007
 #, no-c-format
 msgid "Power Macintosh 8200, 8500, 8600"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1007
+#: hardware.xml:1010
 #, no-c-format
 msgid "Power Macintosh 9500, 9600"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1010
+#: hardware.xml:1013
 #, no-c-format
 msgid "Power Macintosh (Beige) G3 Minitower"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1013
+#: hardware.xml:1016
 #, no-c-format
 msgid "Power Macintosh (Beige) Desktop, All-in-One"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1016
+#: hardware.xml:1019
 #, no-c-format
 msgid "PowerBook 2400, 3400, 3500"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1019
+#: hardware.xml:1022
 #, no-c-format
 msgid "PowerBook G3 Wallstreet (1998)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1022
+#: hardware.xml:1025
 #, no-c-format
 msgid "Twentieth Anniversary Macintosh"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1025
+#: hardware.xml:1028
 #, no-c-format
 msgid "Workgroup Server 7250, 7350, 8550, 9650, G3"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1030
+#: hardware.xml:1033
 #, no-c-format
 msgid "Power Computing"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1031
+#: hardware.xml:1034
 #, no-c-format
 msgid "PowerBase, PowerTower / Pro, PowerWave"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1034
+#: hardware.xml:1037
 #, no-c-format
 msgid "PowerCenter / Pro, PowerCurve"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1039
+#: hardware.xml:1042
 #, no-c-format
 msgid "UMAX"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1040
+#: hardware.xml:1043
 #, no-c-format
 msgid "C500, C600, J700, S900"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1045
+#: hardware.xml:1048
 #, no-c-format
 msgid "<entry>APS</entry>"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1046
+#: hardware.xml:1049
 #, no-c-format
 msgid "APS Tech M*Power 604e/2000"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1051 hardware.xml:1077
+#: hardware.xml:1054 hardware.xml:1080
 #, no-c-format
 msgid "Motorola"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1052
+#: hardware.xml:1055
 #, no-c-format
 msgid "Starmax 3000, 4000, 5000, 5500"
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1061
+#: hardware.xml:1064
 #, no-c-format
 msgid "PReP subarchitecture"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1078
+#: hardware.xml:1081
 #, no-c-format
 msgid "Firepower, PowerStack Series E, PowerStack II"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1080
+#: hardware.xml:1083
 #, no-c-format
 msgid "MPC 7xx, 8xx"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1082
+#: hardware.xml:1085
 #, no-c-format
 msgid "MTX, MTX+"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1084
+#: hardware.xml:1087
 #, no-c-format
 msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1086
+#: hardware.xml:1089
 #, no-c-format
 msgid "MCP(N)750"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1090 hardware.xml:1121
+#: hardware.xml:1093 hardware.xml:1124
 #, no-c-format
 msgid "IBM RS/6000"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1091
+#: hardware.xml:1094
 #, no-c-format
 msgid "40P, 43P"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1093
+#: hardware.xml:1096
 #, no-c-format
 msgid "Power 830/850/860 (6070, 6050)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1095
+#: hardware.xml:1098
 #, no-c-format
 msgid "6030, 7025, 7043"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1097
+#: hardware.xml:1100
 #, no-c-format
 msgid "p640"
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1105
+#: hardware.xml:1108
 #, no-c-format
 msgid "CHRP subarchitecture"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1122
+#: hardware.xml:1125
 #, no-c-format
 msgid "B50, 43P-150, 44P"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1125
+#: hardware.xml:1128
 #, no-c-format
 msgid "Genesi"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1126
+#: hardware.xml:1129
 #, no-c-format
 msgid "Pegasos I, Pegasos II"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1129
+#: hardware.xml:1132
 #, no-c-format
 msgid "Fixstars"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1130
+#: hardware.xml:1133
 #, no-c-format
 msgid "YDL PowerStation"
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1138
+#: hardware.xml:1141
 #, no-c-format
 msgid "APUS subarchitecture (unsupported)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1154
+#: hardware.xml:1157
 #, no-c-format
 msgid "Amiga Power-UP Systems (APUS)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1155
+#: hardware.xml:1158
 #, no-c-format
 msgid "A1200, A3000, A4000"
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1163
+#: hardware.xml:1166
 #, no-c-format
 msgid "Nubus PowerMac subarchitecture (unsupported)"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1165
+#: hardware.xml:1168
 #, 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:1202
+#: hardware.xml:1205
 #, no-c-format
 msgid "Non-PowerPC Macs"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1204
+#: hardware.xml:1207
 #, 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:1213
+#: hardware.xml:1216
 #, 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:1221
+#: hardware.xml:1224
 #, 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:1237
+#: hardware.xml:1240
 #, no-c-format
 msgid "zSeries and System z machine types"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1238
+#: hardware.xml:1241
 #, 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:1255
+#: hardware.xml:1258
 #, no-c-format
 msgid "PAV and HyperPAV"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1256
+#: hardware.xml:1259
 #, 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:1272
+#: hardware.xml:1275
 #, no-c-format
 msgid "CPU and Main Boards Support"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1273
+#: hardware.xml:1276
 #, 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:1284
+#: hardware.xml:1287
 #, no-c-format
 msgid "sun4, sun4c, sun4d, sun4m"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1286
+#: hardware.xml:1289
 #, 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:1293
+#: hardware.xml:1296
 #, 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:1303
+#: hardware.xml:1306
 #, no-c-format
 msgid "sun4u"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1305
+#: hardware.xml:1308
 #, 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:1318
+#: hardware.xml:1321
 #, no-c-format
 msgid "sun4v"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1320
+#: hardware.xml:1323
 #, 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:1331
+#: hardware.xml:1334
 #, 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:1340
+#: hardware.xml:1343
 #, no-c-format
 msgid "Laptops"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1341
+#: hardware.xml:1344
 #, no-c-format
 msgid "From a technical point of view, laptops are normal PCs, so all information regarding PC systems applies to laptops as well. Installations on laptops nowadays usually work out of the box, including things like automatically suspending the system on closing the lid and laptop specfic hardware buttons like those for disabling the wifi interfaces (<quote>airplane mode</quote>). Nonetheless sometimes the hardware vendors use specialized or proprietary hardware for some laptop-specific functions which might 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:1358 hardware.xml:1378 hardware.xml:1405 hardware.xml:1428
+#: hardware.xml:1361 hardware.xml:1381 hardware.xml:1408 hardware.xml:1431
 #, no-c-format
 msgid "Multiple Processors"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1359
+#: hardware.xml:1362
 #, no-c-format
 msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture. Having multiple processors in a computer was originally only an issue for high-end server systems but has become common in recent years nearly everywhere with the introduction of so called <quote>multi-core</quote> processors. These contain two or more processor units, called <quote>cores</quote>, in one physical chip."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1369
+#: hardware.xml:1372
 #, no-c-format
 msgid "The standard &debian; &release; kernel image has been compiled with SMP support. It is also usable on non-SMP systems without problems."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1380
+#: hardware.xml:1383
 #, 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:1389
+#: hardware.xml:1392
 #, no-c-format
 msgid "Having multiple processors in a computer was originally only an issue for high-end server systems but has become common in recent years nearly everywhere with the introduction of so called <quote>multi-core</quote> processors. These contain two or more processor units, called <quote>cores</quote>, in one physical chip."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1396
+#: hardware.xml:1399
 #, no-c-format
 msgid "The 586 flavour of the &debian; kernel image packages for &arch-title; is not compiled with SMP support."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1406
+#: hardware.xml:1409
 #, 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 only the first CPU."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1415
+#: hardware.xml:1418
 #, 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:1429
+#: hardware.xml:1432
 #, 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:1439
+#: hardware.xml:1442
 #, 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:1445
+#: hardware.xml:1448
 #, 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:1456
+#: hardware.xml:1459
 #, no-c-format
 msgid "Graphics Card Support"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1457
+#: hardware.xml:1460
 #, no-c-format
 msgid "&debian;'s support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. On modern PCs, having a graphical display usually works out of the box. Whether advanced graphics card features such as 3D-hardware acceleration or hardware-accelerated video are available, depends on the actual graphics hardware used in the system and in some cases on the installation of additional <quote>firmware</quote> images (see <xref linkend=\"hardware-firmware\"/>). In very few cases there have been reports about hardware on which installation of additional graphics card firmware was required even for basic graphics support, but these have been rare exceptions."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1470
+#: hardware.xml:1473
 #, no-c-format
 msgid "Details on supported graphics cards 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:1475
+#: hardware.xml:1478
 #, 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:1480
+#: hardware.xml:1483
 #, 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:1490
+#: hardware.xml:1493
 #, 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:1512
+#: hardware.xml:1515
 #, no-c-format
 msgid "Network Connectivity Hardware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1513
+#: hardware.xml:1516
 #, no-c-format
 msgid "Almost any network interface card (NIC) supported by the &arch-kernel; kernel should also be supported by the installation system; drivers should normally be loaded automatically. <phrase arch=\"x86\">This includes most PCI/PCI-Express cards as well as PCMCIA/Express Cards on laptops.</phrase> <phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1523
+#: hardware.xml:1526
 #, 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:1529
+#: hardware.xml:1532
 #, no-c-format
 msgid "Sun LANCE"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1534
+#: hardware.xml:1537
 #, no-c-format
 msgid "Sun Happy Meal"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1539
+#: hardware.xml:1542
 #, no-c-format
 msgid "Sun BigMAC"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1544
+#: hardware.xml:1547
 #, no-c-format
 msgid "Sun QuadEthernet"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1549
+#: hardware.xml:1552
 #, no-c-format
 msgid "MyriCOM Gigabit Ethernet"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1556
+#: hardware.xml:1559
 #, no-c-format
 msgid "The list of supported network devices is:"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1561
+#: hardware.xml:1564
 #, no-c-format
 msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1566
+#: hardware.xml:1569
 #, no-c-format
 msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1571
+#: hardware.xml:1574
 #, no-c-format
 msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1580
+#: hardware.xml:1583
 #, 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:1585
+#: hardware.xml:1588
 #, no-c-format
 msgid "ISDN is supported, but not during the installation."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1592
+#: hardware.xml:1595
 #, no-c-format
 msgid "Wireless Network Cards"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1593
+#: hardware.xml:1596
 #, 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."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1600
+#: hardware.xml:1603
 #, no-c-format
 msgid "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:1605
+#: hardware.xml:1608
 #, 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:1610
+#: hardware.xml:1613
 #, 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:1620
+#: hardware.xml:1623
 #, 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:1634
+#: hardware.xml:1637
 #, no-c-format
 msgid "Known Issues for &arch-title;"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1635
+#: hardware.xml:1638
 #, no-c-format
 msgid "There are a couple of issues with specific network cards that are worth mentioning here."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1642
+#: hardware.xml:1645
 #, no-c-format
 msgid "Conflict between tulip and dfme drivers"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1644
+#: hardware.xml:1647
 #, 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:1654
+#: hardware.xml:1657
 #, 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:1662
+#: hardware.xml:1665
 #, 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:1675
+#: hardware.xml:1678
 #, no-c-format
 msgid "Sun B100 blade"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1677
+#: hardware.xml:1680
 #, no-c-format
 msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1692
+#: hardware.xml:1695
 #, no-c-format
 msgid "Braille Displays"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1693
+#: hardware.xml:1696
 #, 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:1707
+#: hardware.xml:1710
 #, no-c-format
 msgid "Hardware Speech Synthesis"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1708
+#: hardware.xml:1711
 #, 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:1728
+#: hardware.xml:1731
 #, no-c-format
 msgid "Peripherals and Other Hardware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1729
+#: hardware.xml:1732
 #, no-c-format
 msgid "&arch-kernel; supports a large variety of hardware devices such as mice, printers, scanners, PCMCIA/CardBus/ExpressCard and USB devices. However, most of these devices are not required while installing the system."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1735
+#: hardware.xml:1738
 #, no-c-format
 msgid "USB hardware generally works fine. On some very old PC systems some USB keyboards may require additional configuration (see <xref linkend=\"hardware-issues\"/>). On modern PCs, USB keyboards and mice work without requiring any specific configuration."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1744
+#: hardware.xml:1747
 #, 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: title
-#: hardware.xml:1757
+#: hardware.xml:1760
 #, no-c-format
 msgid "Devices Requiring Firmware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1758
+#: hardware.xml:1761
 #, 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. With many graphics cards, basic functionality is available without additional firmware, but the use of advanced features requires an appropriate firmware file to be installed in the system."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1769
+#: hardware.xml:1772
 #, no-c-format
 msgid "On many older devices which require firmware to work, the firmware file was permanently placed in an EEPROM/Flash chip on the device itself by the manufacturer. Nowadays most new devices do not have the firmware embedded this way anymore, so the firmware file must be uploaded into the device by the host operating system every time the system boots."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1777
+#: hardware.xml:1780
 #, 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:1786
+#: hardware.xml:1789
 #, 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 USB stick. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware files or packages during the installation."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1795
+#: hardware.xml:1798
 #, no-c-format
 msgid "If the &d-i; prompts for a firmware file and you do not have this firmware file available or do not want to install a non-free firmware file on your system, you can try to proceed without loading the firmware. There are several cases where a driver prompts for additional firmware because it may be needed under certain circumstances, but the device does work without it on most systems (this e.g. happens with certain network cards using the tg3 driver)."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1812
+#: hardware.xml:1815
 #, no-c-format
 msgid "Purchasing Hardware Specifically for GNU/&arch-kernel;"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1814
+#: hardware.xml:1817
 #, 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:1822
+#: hardware.xml:1825
 #, 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:1830
+#: hardware.xml:1833
 #, 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:1841
+#: hardware.xml:1844
 #, no-c-format
 msgid "Avoid Proprietary or Closed Hardware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1842
+#: hardware.xml:1845
 #, 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 driver's source code, which is one of the central elements of free software. Since we haven't been granted access to usable documentation on these devices, they simply won't work under &arch-kernel;."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1852
+#: hardware.xml:1855
 #, no-c-format
 msgid "In many cases there are standards (or at least some de-facto standards) describing how an operating system and its device drivers communicate with a certain class of devices. All devices which comply to such a (de-facto-)standard can be used with a single generic device driver and no device-specific drivers are required. With some kinds of hardware (e.g. USB <quote>Human Interface Devices</quote>, i.e. keyboards, mice, etc., and USB mass storage devices like USB flash disks and memory card readers) this works very well and practically every device sold in the market is standards-compliant."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1864
+#: hardware.xml:1867
 #, no-c-format
 msgid "In other fields, among them e.g. printers, this is unfortunately not the case. While there are many printers which can be addressed via a small set of (de-facto-)standard control languages and therefore can be made to work without problems in any operating system, there are quite a few models which only understand proprietary control commands for which no usable documentation is available and therefore either cannot be used at all on free operating systems or can only be used with a vendor-supplied closed-source driver."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1875
+#: hardware.xml:1878
 #, no-c-format
 msgid "Even if there is a vendor-provided closed-source driver for such hardware when purchasing the device, the practical lifespan of the device is limited by driver availability. Nowadays product cycles have become short and it is not uncommon that a short time after a consumer device has ceased production, no driver updates get made available any more by the manufacturer. If the old closed-source driver does not work anymore after a system update, an otherwise perfectly working device becomes unusable due to lacking driver support and there is nothing that can be done in this case. You should therefore avoid buying closed hardware in the first place, regardless of the operating system you want to use it with."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1888
+#: hardware.xml:1891
 #, no-c-format
 msgid "You can help improve this situation by encouraging manufacturers of closed hardware to release the documentation and other resources necessary for us to provide free drivers for their hardware."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1903
+#: hardware.xml:1906
 #, no-c-format
 msgid "Installation Media"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1905
+#: hardware.xml:1908
 #, 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:1915
+#: hardware.xml:1918
 #, no-c-format
 msgid "Floppies"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1916
+#: hardware.xml:1919
 #, 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:1922
+#: hardware.xml:1925
 #, no-c-format
 msgid "For CHRP, floppy support is currently broken."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1929
+#: hardware.xml:1932
 #, no-c-format
 msgid "CD-ROM/DVD-ROM"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1931
+#: hardware.xml:1934
 #, 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."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1937
+#: hardware.xml:1940
 #, no-c-format
 msgid "CD-ROM based installation is supported for most architectures."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1941
+#: hardware.xml:1944
 #, no-c-format
 msgid "On PCs SATA, IDE/ATAPI and SCSI CD-ROMs are supported."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1945
+#: hardware.xml:1948
 #, 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:1950
+#: hardware.xml:1953
 #, no-c-format
 msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1954
+#: hardware.xml:1957
 #, 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:1968
+#: hardware.xml:1971
 #, no-c-format
 msgid "USB Memory Stick"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1970
+#: hardware.xml:1973
 #, no-c-format
 msgid "USB flash disks a.k.a. USB memory sticks have become a commonly used and cheap storage device. Most modern computer systems also allow booting the &d-i; from such a stick. Many modern computer systems, in particular netbooks and thin laptops, do not have a CD/DVD-ROM drive anymore at all and booting from USB media ist the standard way of installing a new operating system on them."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1982
+#: hardware.xml:1985
 #, no-c-format
 msgid "Network"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1984
+#: hardware.xml:1987
 #, 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:1994
+#: hardware.xml:1997
 #, no-c-format
 msgid "You can also <emphasis>boot</emphasis> the installation system over the network without needing any local media like CDs/DVDs or USB sticks. If you already have a netboot-infrastructure available (i.e. you are already running DHCP and TFTP services in your network), this allows an easy and fast deployment of a large number of machines. Setting up the necessary infrastructure requires a certain level of technical experience, so this is not recommended for novice users. <phrase arch=\"mips;mipsel\">This is the preferred installation technique for &arch-title;.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2007
+#: hardware.xml:2010
 #, 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:2016
+#: hardware.xml:2019
 #, no-c-format
 msgid "Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2018
+#: hardware.xml:2021
 #, 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. This method is only recommended for special cases when no other installation method is available."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2025
+#: hardware.xml:2028
 #, 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:2034
+#: hardware.xml:2037
 #, no-c-format
 msgid "Un*x or GNU system"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2036
+#: hardware.xml:2039
 #, 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\"/>. This installation method is only recommended for advanced users when no other installation method is available."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:2049
+#: hardware.xml:2052
 #, no-c-format
 msgid "Supported Storage Systems"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2051
+#: hardware.xml:2054
 #, no-c-format
 msgid "The &debian; installer contains a kernel which is built to maximize the number of systems it runs on."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2055
+#: hardware.xml:2058
 #, no-c-format
 msgid "Generally, the &debian; installation system includes support for IDE (also known as PATA) drives, 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:2072
+#: hardware.xml:2075
 #, 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:2105
+#: hardware.xml:2108
 #, 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:2111
+#: hardware.xml:2114
 #, 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:2117
+#: hardware.xml:2120
 #, no-c-format
 msgid "Any storage system supported by the Linux kernel is also supported by the boot system."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2122
+#: hardware.xml:2125
 #, 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:2139
+#: hardware.xml:2142
 #, no-c-format
 msgid "Memory and Disk Space Requirements"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2141
+#: hardware.xml:2144
 #, 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:2148
+#: hardware.xml:2151
 #, 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 text-based 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 53d7a6ad9..50ce81ebf 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: 2014-10-05 18:15+0000\n"
+"POT-Creation-Date: 2015-01-09 19:07+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"
@@ -155,59 +155,59 @@ msgstr ""
 #. Tag: para
 #: install-methods.xml:211
 #, no-c-format
-msgid "The installation files for systems supported by the armhf multiplatform kernel (see <xref linkend=\"armhf-armmp-supported-platforms\"/>) consist of a standard Linux kernel image, a standard Linux initial ramdisk image and a system-specific device-tree blob. The kernel and the initial ramdisk image can be obtained from &armmp-firmware-img; and the device-tree blob can be obtained from &armmp-dtb-img;."
+msgid "The installation files for systems supported by the armhf multiplatform kernel (see <xref linkend=\"armhf-armmp-supported-platforms\"/>) consist of a standard Linux kernel image, a standard Linux initial ramdisk image and a system-specific device-tree blob. The kernel and the initial ramdisk image for tftp-booting can be obtained from &armmp-firmware-img; and the device-tree blob can be obtained from &armmp-dtb-img;. The tar archive for creating a bootable USB stick with the installer can be obtained from &armmp-hd-media-tarball;."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:263
+#: install-methods.xml:265
 #, no-c-format
 msgid "Creating Floppies from Disk Images"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:264
+#: install-methods.xml:266
 #, no-c-format
 msgid "Bootable floppy disks are generally used as a last resort to boot the installer on hardware that cannot boot from CD or by other means."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:269
+#: install-methods.xml:271
 #, no-c-format
 msgid "Booting the installer from floppy disk reportedly fails on Mac USB floppy drives."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:274
+#: install-methods.xml:276
 #, no-c-format
 msgid "Disk images are files containing the complete contents of a floppy disk in <emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</filename>, cannot simply be copied to floppy drives. A special program is used to write the image files to floppy disk in <emphasis>raw</emphasis> mode. This is required because these images are raw representations of the disk; it is required to do a <emphasis>sector copy</emphasis> of the data from the file onto the floppy."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:285
+#: install-methods.xml:287
 #, no-c-format
 msgid "There are different techniques for creating floppies from disk images. This section describes how to create floppies from disk images on different platforms."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:291
+#: install-methods.xml:293
 #, no-c-format
 msgid "Before you can create the floppies, you will first need to download them from one of the &debian; mirrors, as explained in <xref linkend=\"downloading-files\"/>. <phrase arch=\"i386\">If you already have an installation CD-ROM or DVD, the floppy images may also be included on the CD/DVD.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:299
+#: install-methods.xml:301
 #, no-c-format
 msgid "No matter which method you use to create your floppies, you should remember to flip the write-protect tab on the floppies once you have written them, to ensure they are not damaged unintentionally."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:307
+#: install-methods.xml:309
 #, no-c-format
 msgid "Writing Disk Images From a Linux or Unix System"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:308
+#: install-methods.xml:310
 #, no-c-format
 msgid ""
       "To write the floppy disk image files to the floppy disks, you will probably need root access to the system. Place a good, blank floppy in the floppy drive. Next, use the command <informalexample><screen>\n"
@@ -216,187 +216,187 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:329
+#: install-methods.xml:331
 #, no-c-format
 msgid "Some systems attempt to automatically mount a floppy disk when you place it in the drive. You might have to disable this feature before the workstation will allow you to write a floppy in <emphasis>raw mode</emphasis>. Unfortunately, how to accomplish this will vary based on your operating system. <phrase arch=\"sparc\"> On Solaris, you can work around volume management to get raw access to the floppy. First, make sure that the floppy is auto-mounted (using <command>volcheck</command> or the equivalent command in the file manager). Then use a <command>dd</command> command of the form given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/rdsk/<replaceable>floppy_name</replaceable></filename>, where <replaceable>floppy_name</replaceable> is the name the floppy disk was given when it was formatted (unnamed floppies default to the name <filename>unnamed_floppy</filename>). On other systems, ask your system administrator. </phrase>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:350
+#: install-methods.xml:352
 #, no-c-format
 msgid "If writing a floppy on powerpc Linux, you will need to eject it. The <command>eject</command> program handles this nicely; you might need to install it."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:368
+#: install-methods.xml:370
 #, no-c-format
 msgid "Writing Disk Images From DOS, Windows, or OS/2"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:370
+#: install-methods.xml:372
 #, no-c-format
 msgid "If you have access to an i386 or amd64 machine, you can use one of the following programs to copy images to floppies."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:375
+#: install-methods.xml:377
 #, no-c-format
 msgid "The <command>rawrite1</command> and <command>rawrite2</command> programs can be used under MS-DOS. To use these programs, first make sure that you are booted into DOS. Trying to use these programs from within a DOS box in Windows, or double-clicking on these programs from the Windows Explorer is <emphasis>not</emphasis> expected to work."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:383
+#: install-methods.xml:385
 #, no-c-format
 msgid "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, ME, XP and probably later versions. To use it you will need to unpack diskio.dll in the same directory."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:389
+#: install-methods.xml:391
 #, no-c-format
 msgid "These tools can be found on the Official &debian; CD-ROMs under the <filename>/tools</filename> directory."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:402
+#: install-methods.xml:404
 #, no-c-format
 msgid "Writing Disk Images From MacOS"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:403
+#: install-methods.xml:405
 #, no-c-format
 msgid "An AppleScript, <application>Make &debian; Floppy</application>, is available for burning floppies from the provided disk image files. It can be downloaded from <ulink url=\"ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/debian-imac/MakeDebianFloppy.sit\"></ulink>. To use it, just unstuff it on your desktop, and then drag any floppy image file to it. You must have Applescript installed and enabled in your extensions manager. Disk Copy will ask you to confirm that you wish to erase the floppy and proceed to write the file image to it."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:414
+#: install-methods.xml:416
 #, no-c-format
 msgid "You can also use the MacOS utility <command>Disk Copy</command> directly, or the freeware utility <command>suntar</command>. The <filename>root.bin</filename> file is an example of a floppy image. Use one of the following methods to create a floppy from the floppy image with these utilities."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:425
+#: install-methods.xml:427
 #, no-c-format
 msgid "Writing Disk Images with <command>Disk Copy</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:426
+#: install-methods.xml:428
 #, no-c-format
 msgid "If you are creating the floppy image from files which were originally on the official &debian-gnu; CD, then the Type and Creator are already set correctly. The following <command>Creator-Changer</command> steps are only necessary if you downloaded the image files from a &debian; mirror."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:435
+#: install-methods.xml:437
 #, no-c-format
 msgid "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> and use it to open the <filename>root.bin</filename> file."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:442
+#: install-methods.xml:444
 #, no-c-format
 msgid "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type to <userinput>DDim</userinput> (binary floppy image). The case is sensitive for these fields."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:449
+#: install-methods.xml:451
 #, no-c-format
 msgid "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</userinput> to display the Finder information about the floppy image, and <quote>X</quote> the <userinput>File Locked</userinput> check box so that MacOS will be unable to remove the boot blocks if the image is accidentally mounted."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:458
+#: install-methods.xml:460
 #, no-c-format
 msgid "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it will very likely be there already, otherwise try <ulink url=\"&url-powerpc-diskcopy;\"></ulink>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:465
+#: install-methods.xml:467
 #, no-c-format
 msgid "Run <command>Disk Copy</command>, and select <menuchoice> <guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> </menuchoice>, then select the <emphasis>locked</emphasis> image file from the resulting dialog. It will ask you to insert a floppy, then ask if you really want to erase it. When done it should eject the floppy."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:480
+#: install-methods.xml:482
 #, no-c-format
 msgid "Writing Disk Images with <command>suntar</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:484
+#: install-methods.xml:486
 #, no-c-format
 msgid "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </ulink>. Start the <command>suntar</command> program and select <quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> menu."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:492
+#: install-methods.xml:494
 #, no-c-format
 msgid "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:498
+#: install-methods.xml:500
 #, no-c-format
 msgid "Select the <filename>root.bin</filename> file in the file-opening dialog."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:503
+#: install-methods.xml:505
 #, no-c-format
 msgid "After the floppy has been created successfully, select <menuchoice> <guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. If there are any errors writing the floppy, simply toss that floppy and try another."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:511
+#: install-methods.xml:513
 #, no-c-format
 msgid "Before using the floppy you created, <emphasis>set the write protect tab</emphasis>! Otherwise if you accidentally mount it in MacOS, MacOS will helpfully ruin it."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:530
+#: install-methods.xml:532
 #, no-c-format
 msgid "Preparing Files for USB Memory Stick Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:532
+#: install-methods.xml:534
 #, no-c-format
 msgid "To prepare the USB stick, you will need a system where GNU/Linux is already running and where USB is supported. With current GNU/Linux systems the USB stick should be automatically recognized when you insert it. If it is not you should check that the usb-storage kernel module is loaded. When the USB stick is inserted, it will be mapped to a device named <filename>/dev/sdX</filename>, where the <quote>X</quote> is a letter in the range a-z. You should be able to see to which device the USB stick was mapped by running the command <command>dmesg</command> after inserting it. To write to your stick, you may have to turn off its write protection switch."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:545
+#: install-methods.xml:547
 #, no-c-format
 msgid "The procedures described in this section will destroy anything already on the device! Make very sure that you use the correct device name for your USB stick. If you use the wrong device the result could be that all information on for example a hard disk could be lost."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:555
+#: install-methods.xml:557
 #, no-c-format
 msgid "Preparing a USB stick using a hybrid CD or DVD image"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:556
+#: install-methods.xml:558
 #, no-c-format
 msgid "Debian CD and DVD images can now be written directly a USB stick, which is a very easy way to make a bootable USB stick. Simply choose a CD or DVD image that will fit on your USB stick. See <xref linkend=\"official-cdrom\"/> to get a CD or DVD image."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:563
+#: install-methods.xml:565
 #, no-c-format
 msgid "Alternatively, for very small USB sticks, only a few megabytes in size, you can download the <filename>mini.iso</filename> image from the <filename>netboot</filename> directory (at the location mentioned in <xref linkend=\"where-files\"/>)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:570
+#: install-methods.xml:572
 #, no-c-format
 msgid "The CD or DVD image you choose should be written directly to the USB stick, overwriting its current contents. For example, when using an existing GNU/Linux system, the CD or DVD image file can be written to a USB stick as follows, after having made sure that the stick is unmounted:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:577
+#: install-methods.xml:579
 #, no-c-format
 msgid ""
       "<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/<replaceable>sdX</replaceable></userinput>\n"
@@ -404,31 +404,31 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:579
+#: install-methods.xml:581
 #, no-c-format
 msgid "The image must be written to the whole-disk device and not a partition, e.g. /dev/sdb and not /dev/sdb1."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:584
+#: install-methods.xml:586
 #, no-c-format
 msgid "Simply writing the CD or DVD image to USB like this should work fine for most users. The other options below are more complex, mainly for people with specialised needs."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:592
+#: install-methods.xml:594
 #, no-c-format
 msgid "The hybrid image on the stick does not occupy all the storage space, so it may be worth considering using the free space to hold firmware files or packages or any other files of your choice. This could be useful if you have only one stick or just want to keep everything you need on one device."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:600
+#: install-methods.xml:602
 #, no-c-format
 msgid "Create a second, FAT partition on the stick, mount the partition and copy or unpack the firmware onto it. For example:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:605
+#: install-methods.xml:607
 #, no-c-format
 msgid ""
       "# mount /dev/<replaceable>sdX2</replaceable> /mnt\n"
@@ -439,91 +439,91 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:607
+#: install-methods.xml:609
 #, no-c-format
 msgid "You might have written the <filename>mini.iso</filename> to the USB stick. In this case the second partition doesn't have to be created as, very nicely, it will already be present. Unplugging and replugging the USB stick should make the two partitions visible."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:621
+#: install-methods.xml:623
 #, no-c-format
 msgid "Manually copying files to the USB stick"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:622
+#: install-methods.xml:624
 #, no-c-format
 msgid "An alternative way to set up your USB stick is to manually copy the installer files, and also a CD image to it. Note that the USB stick should be at least 1 GB in size (smaller setups are possible if you follow <xref linkend=\"usb-copy-flexible\"/>)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:629
+#: install-methods.xml:631
 #, no-c-format
 msgid "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which contains all the installer files (including the kernel) <phrase arch=\"x86\">as well as <classname>syslinux</classname> and its configuration file</phrase> <phrase arch=\"powerpc\">as well as <classname>yaboot</classname> and its configuration file</phrase>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:638
+#: install-methods.xml:640
 #, no-c-format
 msgid "Note that, although convenient, this method does have one major disadvantage: the logical size of the device will be limited to 1 GB, even if the capacity of the USB stick is larger. You will need to repartition the USB stick and create new file systems to get its full capacity back if you ever want to use it for some different purpose."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:646
+#: install-methods.xml:648
 #, no-c-format
 msgid "To use this image simply extract it directly to your USB stick:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:650
+#: install-methods.xml:652
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:652
+#: install-methods.xml:654
 #, no-c-format
 msgid "Create a partition of type \"Apple_Bootstrap\" on your USB stick using <command>mac-fdisk</command>'s <userinput>C</userinput> command and extract the image directly to that:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:658
+#: install-methods.xml:660
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:660
+#: install-methods.xml:662
 #, no-c-format
 msgid "After that, mount the USB memory stick <phrase arch=\"x86\">(<userinput>mount /dev/<replaceable>sdX</replaceable> /mnt</userinput>),</phrase> <phrase arch=\"powerpc\">(<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>),</phrase> which will now have <phrase arch=\"x86\">a FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS filesystem</phrase> on it, and copy a &debian; ISO image (netinst or full CD) to it. Unmount the stick (<userinput>umount /mnt</userinput>) and you are done."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:677
+#: install-methods.xml:679
 #, no-c-format
 msgid "Manually copying files to the USB stick &mdash; the flexible way"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:678
+#: install-methods.xml:680
 #, no-c-format
 msgid "If you like more flexibility or just want to know what's going on, you should use the following method to put the files on your stick. One advantage of using this method is that &mdash; if the capacity of your USB stick is large enough &mdash; you have the option of copying any ISO image, even a DVD image, to it."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:693 install-methods.xml:815
+#: install-methods.xml:695 install-methods.xml:817
 #, no-c-format
 msgid "Partitioning the USB stick"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:694
+#: install-methods.xml:696
 #, no-c-format
 msgid "We will show how to set up the memory stick to use the first partition, instead of the entire device."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:699
+#: install-methods.xml:701
 #, 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>, install an MBR using: <informalexample><screen>\n"
@@ -534,13 +534,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:723
+#: install-methods.xml:725
 #, 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:733
+#: install-methods.xml:735
 #, 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"
@@ -549,19 +549,19 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:750 install-methods.xml:862
+#: install-methods.xml:752 install-methods.xml:864
 #, no-c-format
 msgid "Adding the installer image"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:751
+#: install-methods.xml:753
 #, 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 text-based 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:775
+#: install-methods.xml:777
 #, 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"
@@ -571,19 +571,19 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:787
+#: install-methods.xml:789
 #, 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:792 install-methods.xml:902
+#: install-methods.xml:794 install-methods.xml:904
 #, 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 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:816
+#: install-methods.xml:818
 #, 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"
@@ -592,13 +592,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:833
+#: install-methods.xml:835
 #, 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:842
+#: install-methods.xml:844
 #, 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"
@@ -611,37 +611,37 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:863
+#: install-methods.xml:865
 #, 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:870
+#: install-methods.xml:872
 #, no-c-format
 msgid "<filename>vmlinux</filename> (kernel binary)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:875
+#: install-methods.xml:877
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (initial ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:880
+#: install-methods.xml:882
 #, no-c-format
 msgid "<filename>yaboot.conf</filename> (yaboot configuration file)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:885
+#: install-methods.xml:887
 #, no-c-format
 msgid "<filename>boot.msg</filename> (optional boot message)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:892
+#: install-methods.xml:894
 #, no-c-format
 msgid ""
       "The <filename>yaboot.conf</filename> configuration file should contain the following lines: <informalexample><screen>\n"
@@ -659,259 +659,259 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:930
+#: install-methods.xml:932
 #, no-c-format
 msgid "Preparing Files for Hard Disk Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:931
+#: install-methods.xml:933
 #, 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:937
+#: install-methods.xml:939
 #, 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:944
+#: install-methods.xml:946
 #, 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:955
+#: install-methods.xml:957
 #, 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:964
+#: install-methods.xml:966
 #, no-c-format
 msgid "Hard disk installer booting from Linux using <command>LILO</command> or <command>GRUB</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:966
+#: install-methods.xml:968
 #, 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:972
+#: install-methods.xml:974
 #, 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:978
+#: install-methods.xml:980
 #, 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:986
+#: install-methods.xml:988
 #, no-c-format
 msgid "<filename>vmlinuz</filename> (kernel binary)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:991
+#: install-methods.xml:993
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:998
+#: install-methods.xml:1000
 #, no-c-format
 msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1008
+#: install-methods.xml:1010
 #, no-c-format
 msgid "Hard disk installer booting from DOS using <command>loadlin</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1009
+#: install-methods.xml:1011
 #, 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:1014
+#: install-methods.xml:1016
 #, no-c-format
 msgid "Copy the following directories from a &debian; CD image to <filename>c:\\</filename>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1019
+#: install-methods.xml:1021
 #, no-c-format
 msgid "<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1024
+#: install-methods.xml:1026
 #, no-c-format
 msgid "<filename>/tools</filename> (loadlin tool)"
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1037
+#: install-methods.xml:1039
 #, no-c-format
 msgid "Hard Disk Installer Booting for OldWorld Macs"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1038
+#: install-methods.xml:1040
 #, 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:1051
+#: install-methods.xml:1053
 #, 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:1071
+#: install-methods.xml:1073
 #, no-c-format
 msgid "Hard Disk Installer Booting for NewWorld Macs"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1072
+#: install-methods.xml:1074
 #, 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:1083
+#: install-methods.xml:1085
 #, 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:1093 install-methods.xml:1419
+#: install-methods.xml:1095 install-methods.xml:1421
 #, no-c-format
 msgid "vmlinux"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1098 install-methods.xml:1424
+#: install-methods.xml:1100 install-methods.xml:1426
 #, no-c-format
 msgid "initrd.gz"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1103 install-methods.xml:1429
+#: install-methods.xml:1105 install-methods.xml:1431
 #, no-c-format
 msgid "yaboot"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1108 install-methods.xml:1434
+#: install-methods.xml:1110 install-methods.xml:1436
 #, no-c-format
 msgid "yaboot.conf"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1113
+#: install-methods.xml:1115
 #, 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:1121
+#: install-methods.xml:1123
 #, no-c-format
 msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1134
+#: install-methods.xml:1136
 #, no-c-format
 msgid "Preparing Files for TFTP Net Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1135
+#: install-methods.xml:1137
 #, 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:1143
+#: install-methods.xml:1145
 #, 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:1150
+#: install-methods.xml:1152
 #, 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:1164
+#: install-methods.xml:1166
 #, 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:1170
+#: install-methods.xml:1172
 #, 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:1175
+#: install-methods.xml:1177
 #, 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:1183
+#: install-methods.xml:1185
 #, 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:1199
+#: install-methods.xml:1201
 #, no-c-format
 msgid "Setting up RARP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1200
+#: install-methods.xml:1202
 #, 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:1212
+#: install-methods.xml:1214
 #, no-c-format
 msgid "On a RARP server system using a Linux 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:1233
+#: install-methods.xml:1235
 #, no-c-format
 msgid "Setting up a DHCP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1234
+#: install-methods.xml:1236
 #, no-c-format
 msgid "One free software DHCP server is ISC <command>dhcpd</command>. For &debian-gnu;, the <classname>isc-dhcp-server</classname> package is recommended. Here is a sample configuration file for it (see <filename>/etc/dhcp/dhcpd.conf</filename>):"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:1241
+#: install-methods.xml:1243
 #, no-c-format
 msgid ""
       "option domain-name \"example.com\";\n"
@@ -936,25 +936,25 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1243
+#: install-methods.xml:1245
 #, 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:1253
+#: install-methods.xml:1255
 #, no-c-format
 msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/isc-dhcp-server restart</userinput>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1261
+#: install-methods.xml:1263
 #, no-c-format
 msgid "Enabling PXE Booting in the DHCP configuration"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1262
+#: install-methods.xml:1264
 #, 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"
@@ -989,19 +989,19 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1282
+#: install-methods.xml:1284
 #, no-c-format
 msgid "Setting up a BOOTP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1283
+#: install-methods.xml:1285
 #, 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>isc-dhcp-server</classname> packages respectively."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1291
+#: install-methods.xml:1293
 #, 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"
@@ -1018,43 +1018,43 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1324
+#: install-methods.xml:1326
 #, 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/dhcp/dhcpd.conf</filename>, and restart <command>dhcpd</command> with <userinput>/etc/init.d/isc-dhcp-server restart</userinput>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1343
+#: install-methods.xml:1345
 #, no-c-format
 msgid "Enabling the TFTP Server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1344
+#: install-methods.xml:1346
 #, 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:1349
+#: install-methods.xml:1351
 #, 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:1358
+#: install-methods.xml:1360
 #, 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:1368
+#: install-methods.xml:1370
 #, 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:1376
+#: install-methods.xml:1378
 #, 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"
@@ -1065,49 +1065,49 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1398
+#: install-methods.xml:1400
 #, no-c-format
 msgid "Move TFTP Images Into Place"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1399
+#: install-methods.xml:1401
 #, 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:1408
+#: install-methods.xml:1410
 #, 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:1439
+#: install-methods.xml:1441
 #, no-c-format
 msgid "boot.msg"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1444
+#: install-methods.xml:1446
 #, 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:1452
+#: install-methods.xml:1454
 #, 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:1464
+#: install-methods.xml:1466
 #, no-c-format
 msgid "SPARC TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1465
+#: install-methods.xml:1467
 #, 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"
@@ -1116,55 +1116,55 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1481
+#: install-methods.xml:1483
 #, 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:1488
+#: install-methods.xml:1490
 #, 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:1499
+#: install-methods.xml:1501
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1500
+#: install-methods.xml:1502
 #, 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:1608
+#: install-methods.xml:1610
 #, no-c-format
 msgid "Automatic Installation"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1609
+#: install-methods.xml:1611
 #, 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:1621
+#: install-methods.xml:1623
 #, no-c-format
 msgid "Automatic Installation Using the &debian; Installer"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1622
+#: install-methods.xml:1624
 #, 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:1629
+#: install-methods.xml:1631
 #, 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/partitioning.pot b/po/pot/partitioning.pot
index ae78e04ff..1a78d1584 100644
--- a/po/pot/partitioning.pot
+++ b/po/pot/partitioning.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: 2014-08-05 21:38+0000\n"
+"POT-Creation-Date: 2015-01-09 19:07+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"
@@ -305,359 +305,365 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:177
 #, no-c-format
+msgid "It is now recommended to have <filename>/usr</filename> on the root partition <filename>/</filename>, otherwise it could cause some trouble at boot time. This means that you should provide at least 600&ndash;750MB of disk space for the root partition including <filename>/usr</filename>, or 5&ndash;6GB for a workstation or a server installation."
+msgstr ""
+
+#. Tag: para
+#: partitioning.xml:187
+#, no-c-format
 msgid "<filename>/var</filename>: variable data like news articles, e-mails, web sites, databases, the packaging system cache, etc. will be placed under this directory. The size of this directory depends greatly on the usage of your system, but for most people will be dictated by the package management tool's overhead. If you are going to do a full installation of just about everything &debian; has to offer, all in one session, setting aside 2 or 3 GB of space for <filename>/var</filename> should be sufficient. If you are going to install in pieces (that is to say, install services and utilities, followed by text stuff, then X, ...), you can get away with 300&ndash;500 MB. If hard drive space is at a premium and you don't plan on doing major system updates, you can get by with as little as 30 or 40 MB."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:193
+#: partitioning.xml:203
 #, no-c-format
 msgid "<filename>/tmp</filename>: temporary data created by programs will most likely go in this directory. 40&ndash;100MB should usually be enough. Some applications &mdash; including archive manipulators, CD/DVD authoring tools, and multimedia software &mdash; may use <filename>/tmp</filename> to temporarily store image files. If you plan to use such applications, you should adjust the space available in <filename>/tmp</filename> accordingly."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:204
+#: partitioning.xml:214
 #, no-c-format
 msgid "<filename>/home</filename>: every user will put his personal data into a subdirectory of this directory. Its size depends on how many users will be using the system and what files are to be stored in their directories. Depending on your planned usage you should reserve about 100MB for each user, but adapt this value to your needs. Reserve a lot more space if you plan to save a lot of multimedia files (pictures, MP3, movies) in your home directory."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:225
+#: partitioning.xml:235
 #, no-c-format
 msgid "Recommended Partitioning Scheme"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:226
+#: partitioning.xml:236
 #, no-c-format
 msgid "For new users, personal &debian; boxes, home systems, and other single-user setups, a single <filename>/</filename> partition (plus swap) is probably the easiest, simplest way to go. However, if your partition is larger than around 6GB, choose ext3 as your partition type. Ext2 partitions need periodic file system integrity checking, and this can cause delays during booting when the partition is large."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:235
+#: partitioning.xml:245
 #, no-c-format
-msgid "For multi-user systems or systems with lots of disk space, it's best to put <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, and <filename>/home</filename> each on their own partitions separate from the <filename>/</filename> partition."
+msgid "For multi-user systems or systems with lots of disk space, it's best to put <filename>/var</filename>, <filename>/tmp</filename>, and <filename>/home</filename> each on their own partitions separate from the <filename>/</filename> partition."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:243
+#: partitioning.xml:253
 #, no-c-format
 msgid "You might need a separate <filename>/usr/local</filename> partition if you plan to install many programs that are not part of the &debian; distribution. If your machine will be a mail server, you might need to make <filename>/var/mail</filename> a separate partition. Often, putting <filename>/tmp</filename> on its own partition, for instance 20&ndash;50MB, is a good idea. If you are setting up a server with lots of user accounts, it's generally good to have a separate, large <filename>/home</filename> partition. In general, the partitioning situation varies from computer to computer depending on its uses."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:255
+#: partitioning.xml:265
 #, no-c-format
 msgid "For very complex systems, you should see the <ulink url=\"&url-multidisk-howto;\"> Multi Disk HOWTO</ulink>. This contains in-depth information, mostly of interest to ISPs and people setting up servers."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:262
+#: partitioning.xml:272
 #, no-c-format
 msgid "With respect to the issue of swap partition size, there are many views. One rule of thumb which works well is to use as much swap as you have system memory. It also shouldn't be smaller than 16MB, in most cases. Of course, there are exceptions to these rules. If you are trying to solve 10000 simultaneous equations on a machine with 256MB of memory, you may need a gigabyte (or more) of swap."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:271
+#: partitioning.xml:281
 #, no-c-format
 msgid "On some 32-bit architectures (m68k and PowerPC), the maximum size of a swap partition is 2GB. That should be enough for nearly any installation. However, if your swap requirements are this high, you should probably try to spread the swap across different disks (also called <quote>spindles</quote>) and, if possible, different SCSI or IDE channels. The kernel will balance swap usage between multiple swap partitions, giving better performance."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:281
+#: partitioning.xml:291
 #, no-c-format
 msgid "As an example, an older home machine might have 32MB of RAM and a 1.7GB IDE drive on <filename>/dev/hda</filename>. There might be a 500MB partition for another operating system on <filename>/dev/hda1</filename>, a 32MB swap partition on <filename>/dev/hda3</filename> and about 1.2GB on <filename>/dev/hda2</filename> as the Linux partition."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:290
+#: partitioning.xml:300
 #, no-c-format
 msgid "For an idea of the space taken by tasks you might be interested in adding after your system installation is complete, check <xref linkend=\"tasksel-size-list\"/>."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:306
+#: partitioning.xml:316
 #, no-c-format
 msgid "Device Names in Linux"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:307
+#: partitioning.xml:317
 #, no-c-format
 msgid "Linux disks and partition names may be different from other operating systems. You need to know the names that Linux uses when you create and mount partitions. Here's the basic naming scheme:"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:315
+#: partitioning.xml:325
 #, no-c-format
 msgid "The first floppy drive is named <filename>/dev/fd0</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:320
+#: partitioning.xml:330
 #, no-c-format
 msgid "The second floppy drive is named <filename>/dev/fd1</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:325
+#: partitioning.xml:335
 #, no-c-format
 msgid "The first SCSI disk (SCSI ID address-wise) is named <filename>/dev/sda</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:331
+#: partitioning.xml:341
 #, no-c-format
 msgid "The second SCSI disk (address-wise) is named <filename>/dev/sdb</filename>, and so on."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:337
+#: partitioning.xml:347
 #, no-c-format
 msgid "The first SCSI CD-ROM is named <filename>/dev/scd0</filename>, also known as <filename>/dev/sr0</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:343
+#: partitioning.xml:353
 #, no-c-format
 msgid "The master disk on IDE primary controller is named <filename>/dev/hda</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:349
+#: partitioning.xml:359
 #, no-c-format
 msgid "The slave disk on IDE primary controller is named <filename>/dev/hdb</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:355
+#: partitioning.xml:365
 #, no-c-format
 msgid "The master and slave disks of the secondary controller can be called <filename>/dev/hdc</filename> and <filename>/dev/hdd</filename>, respectively. Newer IDE controllers can actually have two channels, effectively acting like two controllers."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:366
+#: partitioning.xml:376
 #, no-c-format
 msgid "The first DASD device is named <filename>/dev/dasda</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:372
+#: partitioning.xml:382
 #, no-c-format
 msgid "The second DASD device is named <filename>/dev/dasdb</filename>, and so on."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:380
+#: partitioning.xml:390
 #, no-c-format
 msgid "The partitions on each disk are represented by appending a decimal number to the disk name: <filename>sda1</filename> and <filename>sda2</filename> represent the first and second partitions of the first SCSI disk drive in your system."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:387
+#: partitioning.xml:397
 #, no-c-format
 msgid "Here is a real-life example. Let's assume you have a system with 2 SCSI disks, one at SCSI address 2 and the other at SCSI address 4. The first disk (at address 2) is then named <filename>sda</filename>, and the second <filename>sdb</filename>. If the <filename>sda</filename> drive has 3 partitions on it, these will be named <filename>sda1</filename>, <filename>sda2</filename>, and <filename>sda3</filename>. The same applies to the <filename>sdb</filename> disk and its partitions."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:398
+#: partitioning.xml:408
 #, no-c-format
 msgid "Note that if you have two SCSI host bus adapters (i.e., controllers), the order of the drives can get confusing. The best solution in this case is to watch the boot messages, assuming you know the drive models and/or capacities."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:405
+#: partitioning.xml:415
 #, no-c-format
 msgid "Linux represents the primary partitions as the drive name, plus the numbers 1 through 4. For example, the first primary partition on the first IDE drive is <filename>/dev/hda1</filename>. The logical partitions are numbered starting at 5, so the first logical partition on that same drive is <filename>/dev/hda5</filename>. Remember that the extended partition, that is, the primary partition holding the logical partitions, is not usable by itself. This applies to SCSI disks as well as IDE disks."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:416
+#: partitioning.xml:426
 #, no-c-format
 msgid "Sun disk partitions allow for 8 separate partitions (or slices). The third partition is usually (and is preferred to have) the <quote>Whole Disk</quote> partition. This partition references all of the sectors of the disk, and is used by the boot loader (either SILO, or Sun's)."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:423
+#: partitioning.xml:433
 #, no-c-format
 msgid "The partitions on each disk are represented by appending a decimal number to the disk name: <filename>dasda1</filename> and <filename>dasda2</filename> represent the first and second partitions of the first DASD device in your system."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:438
+#: partitioning.xml:448
 #, no-c-format
 msgid "&debian; Partitioning Programs"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:439
+#: partitioning.xml:449
 #, no-c-format
 msgid "Several varieties of partitioning programs have been adapted by &debian; developers to work on various types of hard disks and computer architectures. Following is a list of the program(s) applicable for your architecture."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:452
+#: partitioning.xml:462
 #, no-c-format
 msgid "Recommended partitioning tool in &debian;. This Swiss army knife can also resize partitions, create filesystems <phrase arch=\"any-x86\"> (<quote>format</quote> in Windows speak)</phrase> and assign them to the mountpoints."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:464
+#: partitioning.xml:474
 #, no-c-format
 msgid "The original Linux disk partitioner, good for gurus."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:468
+#: partitioning.xml:478
 #, no-c-format
 msgid "Be careful if you have existing FreeBSD partitions on your machine. The installation kernels include support for these partitions, but the way that <command>fdisk</command> represents them (or not) can make the device names differ. See the <ulink url=\"&url-linux-freebsd;\">Linux+FreeBSD HOWTO</ulink>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:481
+#: partitioning.xml:491
 #, no-c-format
 msgid "A simple-to-use, full-screen disk partitioner for the rest of us."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:485
+#: partitioning.xml:495
 #, no-c-format
 msgid "Note that <command>cfdisk</command> doesn't understand FreeBSD partitions at all, and, again, device names may differ as a result."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:495
+#: partitioning.xml:505
 #, no-c-format
 msgid "Atari-aware version of <command>fdisk</command>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:504
+#: partitioning.xml:514
 #, no-c-format
 msgid "Amiga-aware version of <command>fdisk</command>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:513
+#: partitioning.xml:523
 #, no-c-format
 msgid "Mac-aware version of <command>fdisk</command>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:522
+#: partitioning.xml:532
 #, no-c-format
 msgid "PowerMac-aware version of <command>fdisk</command>, also used by BVM and Motorola VMEbus systems."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:532
+#: partitioning.xml:542
 #, no-c-format
 msgid "&arch-title; version of <command>fdisk</command>; Please read the fdasd manual page or chapter 13 in <ulink url=\"http://oss.software.ibm.com/developerworks/opensource/linux390/docu/l390dd08.pdf\"> Device Drivers and Installation Commands</ulink> for details."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:543
+#: partitioning.xml:553
 #, no-c-format
 msgid "One of these programs will be run by default when you select <guimenuitem>Partition disks</guimenuitem> (or similar). It may be possible to use a different partitioning tool from the command line on VT2, but this is not recommended."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:550
+#: partitioning.xml:560
 #, no-c-format
 msgid "Remember to mark your boot partition as <quote>Bootable</quote>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:553
+#: partitioning.xml:563
 #, no-c-format
 msgid "One key point when partitioning for Mac type disks is that the swap partition is identified by its name; it must be named <quote>swap</quote>. All Mac linux partitions are the same partition type, Apple_UNIX_SRV2. Please read the fine manual. We also suggest reading the <ulink url=\"&url-mac-fdisk-tutorial;\">mac-fdisk Tutorial</ulink>, which includes steps you should take if you are sharing your disk with MacOS."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:569 partitioning.xml:593 partitioning.xml:689 partitioning.xml:803 partitioning.xml:880
+#: partitioning.xml:579 partitioning.xml:603 partitioning.xml:699 partitioning.xml:813 partitioning.xml:890
 #, no-c-format
 msgid "Partitioning for &arch-title;"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:570
+#: partitioning.xml:580
 #, no-c-format
 msgid "PALO, the HPPA boot loader, requires a partition of type <quote>F0</quote> somewhere in the first 2GB. This is where the boot loader and an optional kernel and RAMdisk will be stored, so make it big enough for that &mdash; at least 4Mb (I like 8&ndash;16MB). An additional requirement of the firmware is that the Linux kernel must reside within the first 2GB of the disk. This is typically achieved by making the root ext2 partition fit entirely within the first 2GB of the disk. Alternatively you can create a small ext2 partition near the start of the disk and mount that on <filename>/boot</filename>, since that is the directory where the Linux kernel(s) will be stored. <filename>/boot</filename> needs to be big enough to hold whatever kernels (and backups) you might wish to load; 25&ndash;50MB is generally sufficient."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:594
+#: partitioning.xml:604
 #, no-c-format
 msgid "If you have an existing other operating system such as DOS or Windows and you want to preserve that operating system while installing &debian;, you may need to resize its partition to free up space for the &debian; installation. The installer supports resizing of both FAT and NTFS filesystems; when you get to the installer's partitioning step, select the option <guimenuitem>Manual</guimenuitem> and then simply select an existing partition and change its size."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:604
+#: partitioning.xml:614
 #, no-c-format
 msgid "The PC BIOS generally adds additional constraints for disk partitioning. There is a limit to how many <quote>primary</quote> and <quote>logical</quote> partitions a drive can contain. Additionally, with pre 1994&ndash;98 BIOSes, there are limits to where on the drive the BIOS can boot from. More information can be found in the <ulink url=\"&url-partition-howto;\">Linux Partition HOWTO</ulink>, but this section will include a brief overview to help you plan most situations."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:614
+#: partitioning.xml:624
 #, no-c-format
 msgid "<quote>Primary</quote> partitions are the original partitioning scheme for PC disks. However, there can only be four of them. To get past this limitation, <quote>extended</quote> and <quote>logical</quote> partitions were invented. By setting one of your primary partitions as an extended partition, you can subdivide all the space allocated to that partition into logical partitions. You can create up to 60 logical partitions per extended partition; however, you can only have one extended partition per drive."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:625
+#: partitioning.xml:635
 #, no-c-format
 msgid "Linux limits the partitions per drive to 255 partitions for SCSI disks (3 usable primary partitions, 252 logical partitions), and 63 partitions on an IDE drive (3 usable primary partitions, 60 logical partitions). However the normal &debian-gnu; system provides only 20 devices for partitions, so you may not install on partitions higher than 20 unless you first manually create devices for those partitions."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:635
+#: partitioning.xml:645
 #, no-c-format
 msgid "If you have a large IDE disk, and are using neither LBA addressing, nor overlay drivers (sometimes provided by hard disk manufacturers), then the boot partition (the partition containing your kernel image) must be placed within the first 1024 cylinders of your hard drive (usually around 524 megabytes, without BIOS translation)."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:643
+#: partitioning.xml:653
 #, no-c-format
 msgid "This restriction doesn't apply if you have a BIOS newer than around 1995&ndash;98 (depending on the manufacturer) that supports the <quote>Enhanced Disk Drive Support Specification</quote>. Both Lilo, the Linux loader, and &debian;'s alternative <command>mbr</command> must use the BIOS to read the kernel from the disk into RAM. If the BIOS int 0x13 large disk access extensions are found to be present, they will be utilized. Otherwise, the legacy disk access interface is used as a fall-back, and it cannot be used to address any location on the disk higher than the 1023rd cylinder. Once &arch-kernel; is booted, no matter what BIOS your computer has, these restrictions no longer apply, since &arch-kernel; does not use the BIOS for disk access."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:657
+#: partitioning.xml:667
 #, no-c-format
 msgid "If you have a large disk, you might have to use cylinder translation techniques, which you can set from your BIOS setup program, such as LBA (Logical Block Addressing) or CHS translation mode (<quote>Large</quote>). More information about issues with large disks can be found in the <ulink url=\"&url-large-disk-howto;\">Large Disk HOWTO</ulink>. If you are using a cylinder translation scheme, and the BIOS does not support the large disk access extensions, then your boot partition has to fit within the <emphasis>translated</emphasis> representation of the 1024th cylinder."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:669
+#: partitioning.xml:679
 #, no-c-format
 msgid "The recommended way of accomplishing this is to create a small (25&ndash;50MB should suffice) partition at the beginning of the disk to be used as the boot partition, and then create whatever other partitions you wish to have, in the remaining area. This boot partition <emphasis>must</emphasis> be mounted on <filename>/boot</filename>, since that is the directory where the &arch-kernel; kernel(s) will be stored. This configuration will work on any system, regardless of whether LBA or large disk CHS translation is used, and regardless of whether your BIOS supports the large disk access extensions."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:690
+#: partitioning.xml:700
 #, no-c-format
 msgid "The <command>partman</command> disk partitioner is the default partitioning tool for the installer. It manages the set of partitions and their mount points to ensure that the disks and filesystems are properly configured for a successful installation. It actually uses <command>parted</command> to do the on-disk partitioning."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:702
+#: partitioning.xml:712
 #, no-c-format
 msgid "EFI Recognized Formats"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:703
+#: partitioning.xml:713
 #, no-c-format
 msgid "The IA-64 EFI firmware supports two partition table (or disk label) formats, GPT and MS-DOS. MS-DOS, the format typically used on i386 PCs, is no longer recommended for IA-64 systems. Although the installer also provides <command>cfdisk</command>, you should only use <ulink url=\"parted.txt\"> <command>parted</command></ulink> because only it can manage both GPT and MS-DOS tables correctly."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:715
+#: partitioning.xml:725
 #, no-c-format
 msgid "The automatic partitioning recipes for <command>partman</command> allocate an EFI partition as the first partition on the disk. You can also set up the partition under the <guimenuitem>Guided partitioning</guimenuitem> from the main menu in a manner similar to setting up a <emphasis>swap</emphasis> partition."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:723
+#: partitioning.xml:733
 #, no-c-format
 msgid ""
       "The <command>partman</command> partitioner will handle most disk layouts. For those rare cases where it is necessary to manually set up a disk, you can use the shell as described above and run the <command>parted</command> utility directly using its command line interface. Assuming that you want to erase your whole disk and create a GPT table and some partitions, then something similar to the following command sequence could be used: <informalexample><screen>\n"
@@ -672,97 +678,97 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:748
+#: partitioning.xml:758
 #, no-c-format
 msgid "Boot Loader Partition Requirements"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:749
+#: partitioning.xml:759
 #, no-c-format
 msgid "ELILO, the IA-64 boot loader, requires a partition containing a FAT file system with the <userinput>boot</userinput> flag set. The partition must be big enough to hold the boot loader and any kernels or RAMdisks you may wish to boot. A minimum size would be about 20MB, but if you expect to run with multiple kernels, then 128MB might be a better size."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:758
+#: partitioning.xml:768
 #, no-c-format
 msgid "The EFI Boot Manager and the EFI Shell fully support the GPT table so the boot partition does not necessarily have to be the first partition or even on the same disk. This is convenient if you should forget to allocate the partition and only find out after you have formatted the other partitions on your disk(s). The <command>partman</command> partitioner checks for an EFI partition at the same time it checks for a properly set up <emphasis>root</emphasis> partition. This gives you an opportunity to correct the disk layout before the package install begins. The easiest way to correct this omission is to shrink the last partition of the disk to make enough free space for adding an EFI partition."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:773
+#: partitioning.xml:783
 #, no-c-format
 msgid "It is strongly recommended that you allocate the EFI boot partition on the same disk as the <emphasis>root</emphasis> filesystem."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:781
+#: partitioning.xml:791
 #, no-c-format
 msgid "EFI Diagnostic Partitions"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:782
+#: partitioning.xml:792
 #, no-c-format
 msgid "The EFI firmware is significantly more sophisticated than the usual BIOS seen on most x86 PCs. Some system vendors take advantage of the ability of the EFI to access files and run programs from a hard disk filesystem to store diagnostics and EFI based system management utilities on the hard disk. This is a separate FAT format filesystem on the system disk. Consult the system documentation and accessories that come with the system for details. The easiest time to set up a diagnostics partition is at the same time you set up the EFI boot partition."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:804
+#: partitioning.xml:814
 #, no-c-format
 msgid "SGI machines require an SGI disk label in order to make the system bootable from hard disk. It can be created in the fdisk expert menu. The thereby created volume header (partition number 9) should be at least 3MB large. If the volume header created is too small, you can simply delete partition number 9 and re-add it with a different size. Note that the volume header must start at sector 0."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:821
+#: partitioning.xml:831
 #, no-c-format
 msgid "Partitioning Newer PowerMacs"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:822
+#: partitioning.xml:832
 #, no-c-format
 msgid "If you are installing onto a NewWorld PowerMac you must create a special bootstrap partition to hold the boot loader. The size of this partition must have at least 819200 bytes and its partition type must be <emphasis>Apple_Bootstrap</emphasis>. If the bootstrap partition is not created with the <emphasis>Apple_Bootstrap</emphasis> type your machine cannot be made bootable from the hard disk. This partition can easily be created by creating a new partition in <command>partman</command> and telling it to use it as a <quote>NewWorld boot partition</quote>, or in <command>mac-fdisk</command> using the <userinput>b</userinput> command."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:835
+#: partitioning.xml:845
 #, no-c-format
 msgid "The special partition type Apple_Bootstrap is required to prevent MacOS from mounting and damaging the bootstrap partition, as there are special modifications made to it in order for OpenFirmware to boot it automatically."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:842
+#: partitioning.xml:852
 #, no-c-format
 msgid "Note that the bootstrap partition is only meant to hold 3 very small files: the <command>yaboot</command> binary, its configuration <filename>yaboot.conf</filename>, and a first stage OpenFirmware loader <command>ofboot.b</command>. It need not and must not be mounted on your file system nor have kernels or anything else copied to it. The <command>ybin</command> and <command>mkofboot</command> utilities are used to manipulate this partition."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:852
+#: partitioning.xml:862
 #, no-c-format
 msgid "In order for OpenFirmware to automatically boot &debian-gnu; the bootstrap partition should appear before other boot partitions on the disk, especially MacOS boot partitions. The bootstrap partition should be the first one you create. However, if you add a bootstrap partition later, you can use <command>mac-fdisk</command>'s <userinput>r</userinput> command to reorder the partition map so the bootstrap partition comes right after the map (which is always partition 1). It's the logical map order, not the physical address order, that counts."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:864
+#: partitioning.xml:874
 #, no-c-format
 msgid "Apple disks normally have several small driver partitions. If you intend to dual boot your machine with MacOSX, you should retain these partitions and a small HFS partition (800k is the minimum size). That is because MacOSX, on every boot, offers to initialize any disks which do not have active MacOS partitions and driver partitions."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:881
+#: partitioning.xml:891
 #, no-c-format
 msgid "Make sure you create a <quote>Sun disk label</quote> on your boot disk. This is the only kind of partition scheme that the OpenBoot PROM understands, and so it's the only scheme from which you can boot. The <keycap>s</keycap> key is used in <command>fdisk</command> to create Sun disk labels."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:889
+#: partitioning.xml:899
 #, no-c-format
 msgid "Furthermore, on &arch-title; disks, make sure your first partition on your boot disk starts at cylinder 0. While this is required, it also means that the first partition will contain the partition table and the boot block, which are the first two sectors of the disk. You must <emphasis>not</emphasis> put swap on the first partition of the boot drive, since swap partitions do not preserve the first few sectors of the partition. You can put Ext2 or UFS partitions there; these will leave the partition table and the boot block alone."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:900
+#: partitioning.xml:910
 #, no-c-format
 msgid "It is also advised that the third partition should be of type <quote>Whole disk</quote> (type 5), and contain the entire disk (from the first cylinder to the last). This is simply a convention of Sun disk labels, and helps the <command>SILO</command> boot loader keep its bearings."
 msgstr ""
diff --git a/po/pot/preseed.pot b/po/pot/preseed.pot
index 4cad60572..24315baab 100644
--- a/po/pot/preseed.pot
+++ b/po/pot/preseed.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: 2014-08-03 08:11+0000\n"
+"POT-Creation-Date: 2015-01-09 19:07+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"
@@ -238,6 +238,9 @@ msgid ""
       "- if you're netbooting:\n"
       "  preseed/url=http://host/path/to/preseed.cfg\n"
       "  preseed/url/checksum=5da499872becccfeda2c4872f9171c3d\n"
+      "- or\n"
+      "  preseed/url=tftp://host/path/to/preseed.cfg\n"
+      "  preseed/url/checksum=5da499872becccfeda2c4872f9171c3d\n"
       "\n"
       "- if you're booting a remastered CD:\n"
       "  preseed/file=/cdrom/preseed.cfg\n"
@@ -294,7 +297,7 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:349
 #, no-c-format
-msgid "A <quote>--</quote> in the boot options has special meaning. Kernel parameters that appear after the last <quote>--</quote> may be copied into the bootloader configuration for the installed system (if supported by the installer for the bootloader). The installer will automatically filter out any options (like preconfiguration options) that it recognizes."
+msgid "A <quote>---</quote> in the boot options has special meaning. Kernel parameters that appear after the last <quote>---</quote> may be copied into the bootloader configuration for the installed system (if supported by the installer for the bootloader). The installer will automatically filter out any options (like preconfiguration options) that it recognizes."
 msgstr ""
 
 #. Tag: para
@@ -633,7 +636,7 @@ msgstr ""
 #. Tag: entry
 #: preseed.xml:548
 #, no-c-format
-msgid "<entry>desktop</entry>"
+msgid "desktop"
 msgstr ""
 
 #. Tag: entry
@@ -1229,7 +1232,7 @@ msgid ""
       "# You can choose one of the three predefined partitioning recipes:\n"
       "# - atomic: all files in one partition\n"
       "# - home:   separate /home partition\n"
-      "# - multi:  separate /home, /usr, /var, and /tmp partitions\n"
+      "# - multi:  separate /home, /var, and /tmp partitions\n"
       "d-i partman-auto/choose_recipe select atomic\n"
       "\n"
       "# Or provide a recipe of your own...\n"
@@ -1464,70 +1467,70 @@ msgstr ""
 msgid "You can choose to install any combination of tasks that are available. Available tasks as of this writing include:"
 msgstr ""
 
-#. Tag: userinput
-#: preseed.xml:1051
+#. Tag: para
+#: preseed.xml:1050
 #, no-c-format
-msgid "standard"
+msgid "<userinput>standard</userinput> (standard tools)"
 msgstr ""
 
-#. Tag: userinput
-#: preseed.xml:1054
+#. Tag: para
+#: preseed.xml:1053
 #, no-c-format
-msgid "<userinput>desktop</userinput>"
+msgid "<userinput>desktop</userinput> (graphical desktop)"
 msgstr ""
 
-#. Tag: userinput
-#: preseed.xml:1057
+#. Tag: para
+#: preseed.xml:1056
 #, no-c-format
-msgid "gnome-desktop"
+msgid "<userinput>gnome-desktop</userinput> (Gnome desktop)"
 msgstr ""
 
-#. Tag: userinput
-#: preseed.xml:1060
+#. Tag: para
+#: preseed.xml:1059
 #, no-c-format
-msgid "kde-desktop"
+msgid "<userinput>xfce-desktop</userinput> (XFCE desktop)"
 msgstr ""
 
-#. Tag: userinput
-#: preseed.xml:1063
+#. Tag: para
+#: preseed.xml:1062
 #, no-c-format
-msgid "web-server"
+msgid "<userinput>kde-desktop</userinput> (KDE desktop)"
 msgstr ""
 
-#. Tag: userinput
-#: preseed.xml:1066
+#. Tag: para
+#: preseed.xml:1065
 #, no-c-format
-msgid "print-server"
+msgid "<userinput>cinnamon-desktop</userinput> (Cinnamon desktop)"
 msgstr ""
 
-#. Tag: userinput
-#: preseed.xml:1069
+#. Tag: para
+#: preseed.xml:1068
 #, no-c-format
-msgid "dns-server"
+msgid "<userinput>mate-desktop</userinput> (MATE desktop)"
 msgstr ""
 
-#. Tag: userinput
-#: preseed.xml:1072
+#. Tag: para
+#: preseed.xml:1071
 #, no-c-format
-msgid "file-server"
+msgid "<userinput>lxde-desktop</userinput> (LXDE desktop)"
 msgstr ""
 
-#. Tag: userinput
-#: preseed.xml:1075
+#. Tag: para
+#: preseed.xml:1074
 #, no-c-format
-msgid "mail-server"
+msgid "<userinput>web-server</userinput> (web server)"
 msgstr ""
 
-#. Tag: userinput
-#: preseed.xml:1078
+#. Tag: para
+#: preseed.xml:1077
 #, no-c-format
-msgid "sql-database"
+msgid "<userinput>print-server</userinput> (print server)"
 msgstr ""
 
-#. Tag: userinput
-#: preseed.xml:1081
+#. Tag: para
+#: preseed.xml:1080
 #, no-c-format
-msgid "laptop"
+msgid "<userinput>ssh-server</userinput> (SSH server)"
 msgstr ""
 
 #. Tag: para
@@ -1546,10 +1549,7 @@ msgstr ""
 #: preseed.xml:1101
 #, no-c-format
 msgid ""
-      "#tasksel tasksel/first multiselect standard, web-server\n"
-      "# If the desktop task is selected, install the kde and xfce desktops\n"
-      "# instead of the default gnome desktop.\n"
-      "#tasksel tasksel/desktop multiselect kde, xfce\n"
+      "#tasksel tasksel/first multiselect standard, web-server, kde-desktop\n"
       "\n"
       "# Individual additional packages to install\n"
       "#d-i pkgsel/include string openssh-server build-essential\n"
@@ -1600,6 +1600,8 @@ msgid ""
       "#d-i grub-installer/bootdev  string (hd0,0) (hd1,0) (hd2,0)\n"
       "# To install to a particular device:\n"
       "#d-i grub-installer/bootdev  string /dev/sda\n"
+      "# To install to the first device:\n"
+      "#d-i grub-installer/bootdev  string default\n"
       "\n"
       "# Optional password for grub, either in clear text\n"
       "#d-i grub-installer/password password r00tme\n"
diff --git a/po/pot/random-bits.pot b/po/pot/random-bits.pot
index 5ce7122ab..86a259732 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: 2014-10-05 18:15+0000\n"
+"POT-Creation-Date: 2015-01-09 19:07+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"
@@ -515,151 +515,193 @@ msgid "&task-desktop-lxde-tot;"
 msgstr ""
 
 #. Tag: entry
+#: random-bits.xml:283
+#, no-c-format
+msgid "&nbsp;&nbsp;&bull;&nbsp;MATE"
+msgstr ""
+
+#. Tag: entry
 #: random-bits.xml:284
 #, no-c-format
-msgid "Laptop"
+msgid "&task-desktop-mate-inst;"
 msgstr ""
 
-#. Tag: para
+#. Tag: entry
+#: random-bits.xml:285
+#, no-c-format
+msgid "&task-desktop-mate-dl;"
+msgstr ""
+
+#. Tag: entry
 #: random-bits.xml:286
 #, no-c-format
-msgid "There is some overlap of the Laptop task with the Desktop environment task. If you install both, the Laptop task will only require a few MB additional disk space."
+msgid "&task-desktop-mate-tot;"
+msgstr ""
+
+#. Tag: entry
+#: random-bits.xml:289
+#, no-c-format
+msgid "&nbsp;&nbsp;&bull;&nbsp;Cinnamon"
+msgstr ""
+
+#. Tag: entry
+#: random-bits.xml:290
+#, no-c-format
+msgid "&task-desktop-cinnamon-inst;"
+msgstr ""
+
+#. Tag: entry
+#: random-bits.xml:291
+#, no-c-format
+msgid "&task-desktop-cinnamon-dl;"
+msgstr ""
+
+#. Tag: entry
+#: random-bits.xml:292
+#, no-c-format
+msgid "&task-desktop-cinnamon-tot;"
+msgstr ""
+
+#. Tag: entry
+#: random-bits.xml:296
+#, no-c-format
+msgid "Laptop"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:293
+#: random-bits.xml:297
 #, no-c-format
 msgid "&task-laptop-inst;"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:294
+#: random-bits.xml:298
 #, no-c-format
 msgid "&task-laptop-dl;"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:295
+#: random-bits.xml:299
 #, no-c-format
 msgid "&task-laptop-tot;"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:299
+#: random-bits.xml:303
 #, no-c-format
 msgid "Web server"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:300
+#: random-bits.xml:304
 #, no-c-format
 msgid "&task-web-inst;"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:301
+#: random-bits.xml:305
 #, no-c-format
 msgid "&task-web-dl;"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:302
+#: random-bits.xml:306
 #, no-c-format
 msgid "&task-web-tot;"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:306
+#: random-bits.xml:310
 #, no-c-format
 msgid "Print server"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:307
+#: random-bits.xml:311
 #, no-c-format
 msgid "&task-print-inst;"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:308
+#: random-bits.xml:312
 #, no-c-format
 msgid "&task-print-dl;"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:309
+#: random-bits.xml:313
 #, no-c-format
 msgid "&task-print-tot;"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:341
+#: random-bits.xml:317
 #, no-c-format
 msgid "SSH server"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:342
+#: random-bits.xml:318
 #, no-c-format
 msgid "&task-ssh-inst;"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:343
+#: random-bits.xml:319
 #, no-c-format
 msgid "&task-ssh-dl;"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:344
+#: random-bits.xml:320
 #, no-c-format
 msgid "&task-ssh-tot;"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:350
+#: random-bits.xml:326
 #, no-c-format
 msgid "If you install in a language other than English, <command>tasksel</command> may automatically install a <firstterm>localization task</firstterm>, if one is available for your language. Space requirements differ per language; you should allow up to 350MB in total for download and installation."
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:365
+#: random-bits.xml:341
 #, no-c-format
 msgid "Installing &debian-gnu; from a Unix/Linux System"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:367
+#: random-bits.xml:343
 #, no-c-format
 msgid "This section explains how to install &debian-gnu; from an existing Unix or Linux system, without using the menu-driven installer as explained in the rest of the manual. This <quote>cross-install</quote> HOWTO has been requested by users switching to &debian-gnu; from Red Hat, Mandriva, and SUSE. In this section some familiarity with entering *nix commands and navigating the file system is assumed. In this section, <prompt>$</prompt> symbolizes a command to be entered in the user's current system, while <prompt>#</prompt> refers to a command entered in the &debian; chroot."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:379
+#: random-bits.xml:355
 #, no-c-format
 msgid "Once you've got the new &debian; system configured to your preference, you can migrate your existing user data (if any) to it, and keep on rolling. This is therefore a <quote>zero downtime</quote> &debian-gnu; install. It's also a clever way for dealing with hardware that otherwise doesn't play friendly with various boot or installation media."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:390
+#: random-bits.xml:366
 #, no-c-format
 msgid "As this is a mostly manual procedure, you should bear in mind that you will need to do a lot of basic configuration of the system yourself, which will also require more knowledge of &debian; and of &arch-kernel; in general than performing a regular installation. You cannot expect this procedure to result in a system that is identical to a system from a regular installation. You should also keep in mind that this procedure only gives the basic steps to set up a system. Additional installation and/or configuration steps may be needed."
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:404
+#: random-bits.xml:380
 #, no-c-format
 msgid "Getting Started"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:405
+#: random-bits.xml:381
 #, no-c-format
 msgid "With your current *nix partitioning tools, repartition the hard drive as needed, creating at least one filesystem plus swap. You need around &base-system-size;MB of space available for a console only install, or about &task-desktop-lxde-inst;MB if you plan to install X (more if you intend to install desktop environments like GNOME or KDE)."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:413
+#: random-bits.xml:389
 #, no-c-format
 msgid ""
       "Next, create file systems on the partitions. For example, to create an ext3 file system on partition <filename>/dev/hda6</filename> (that's our example root partition): <informalexample><screen>\n"
@@ -668,7 +710,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:423
+#: random-bits.xml:399
 #, no-c-format
 msgid ""
       "Initialize and activate swap (substitute the partition number for your intended &debian; swap partition): <informalexample><screen>\n"
@@ -679,7 +721,7 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:435
+#: random-bits.xml:411
 #, no-c-format
 msgid ""
       "# mkdir /mnt/debinst\n"
@@ -687,25 +729,25 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:438
+#: random-bits.xml:414
 #, no-c-format
 msgid "If you want to have parts of the filesystem (e.g. /usr) mounted on separate partitions, you will need to create and mount these directories manually before proceding with the next stage."
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:448
+#: random-bits.xml:424
 #, no-c-format
 msgid "Install <command>debootstrap</command>"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:449
+#: random-bits.xml:425
 #, no-c-format
 msgid "The utility used by the &debian; installer, and recognized as the official way to install a &debian; base system, is <command>debootstrap</command>. It uses <command>wget</command> and <command>ar</command>, but otherwise depends only on <classname>/bin/sh</classname> and basic Unix/Linux tools<footnote> <para> These include the GNU core utilities and commands like <command>sed</command>, <command>grep</command>, <command>tar</command> and <command>gzip</command>. </para> </footnote>. Install <command>wget</command> and <command>ar</command> if they aren't already on your current system, then download and install <command>debootstrap</command>."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:479
+#: random-bits.xml:455
 #, no-c-format
 msgid ""
       "Or, you can use the following procedure to install it manually. Make a work folder for extracting the .deb into: <informalexample><screen>\n"
@@ -715,7 +757,7 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:494
+#: random-bits.xml:470
 #, no-c-format
 msgid ""
       "# ar -x debootstrap_0.X.X_all.deb\n"
@@ -724,31 +766,31 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:500
+#: random-bits.xml:476
 #, no-c-format
 msgid "Run <command>debootstrap</command>"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:501
+#: random-bits.xml:477
 #, no-c-format
 msgid "<command>debootstrap</command> can download the needed files directly from the archive when you run it. You can substitute any &debian; archive mirror for <userinput>&archive-mirror;/debian</userinput> in the command example below, preferably a mirror close to you network-wise. Mirrors are listed at <ulink url=\"http://www.debian.org/mirror/list\"></ulink>."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:510
+#: random-bits.xml:486
 #, no-c-format
 msgid "If you have a &releasename; &debian-gnu; CD mounted at <filename>/cdrom</filename>, you could substitute a file URL instead of the http URL: <userinput>file:/cdrom/debian/</userinput>"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:516
+#: random-bits.xml:492
 #, no-c-format
 msgid "Substitute one of the following for <replaceable>ARCH</replaceable> in the <command>debootstrap</command> command: <userinput>amd64</userinput>, <userinput>arm64</userinput>, <userinput>armel</userinput>, <userinput>armhf</userinput>, <userinput>i386</userinput>, <userinput>mips</userinput>, <userinput>mipsel</userinput>, <userinput>powerpc</userinput>, <userinput>ppc64el</userinput>, or <userinput>s390x</userinput>."
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:532
+#: random-bits.xml:508
 #, no-c-format
 msgid ""
       "# /usr/sbin/debootstrap --arch ARCH &releasename; \\\n"
@@ -756,13 +798,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:538
+#: random-bits.xml:514
 #, no-c-format
 msgid "Configure The Base System"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:539
+#: random-bits.xml:515
 #, 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"
@@ -773,31 +815,31 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:557
+#: random-bits.xml:533
 #, no-c-format
 msgid "Create device files"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:558
+#: random-bits.xml:534
 #, 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:544
 #, no-c-format
 msgid "A few of the available options are:"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:573
+#: random-bits.xml:549
 #, 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:553
 #, no-c-format
 msgid ""
       "# apt-get install makedev\n"
@@ -807,25 +849,25 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:580
+#: random-bits.xml:556
 #, no-c-format
 msgid "manually create only specific device files using <command>MAKEDEV</command>"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:585
+#: random-bits.xml:561
 #, 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:574
 #, no-c-format
 msgid "Mount Partitions"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:599
+#: random-bits.xml:575
 #, no-c-format
 msgid ""
       "You need to create <filename>/etc/fstab</filename>. <informalexample><screen>\n"
@@ -859,31 +901,31 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:625
+#: random-bits.xml:601
 #, no-c-format
 msgid "# mount -t proc proc /proc"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:627
+#: random-bits.xml:603
 #, 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:609
 #, no-c-format
 msgid "# mount -t proc proc /mnt/debinst/proc"
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:639
+#: random-bits.xml:615
 #, no-c-format
 msgid "Setting Timezone"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:640
+#: random-bits.xml:616
 #, no-c-format
 msgid ""
       "Setting the third line of the file <filename>/etc/adjtime</filename> to <quote>UTC</quote> or <quote>LOCAL</quote> determines whether the system will interpret the hardware clock as being set to UTC respective local time. The following command allows you to set that. <informalexample><screen>\n"
@@ -896,19 +938,19 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:654
+#: random-bits.xml:630
 #, no-c-format
 msgid "# dpkg-reconfigure tzdata"
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:660
+#: random-bits.xml:636
 #, no-c-format
 msgid "Configure Networking"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:661
+#: random-bits.xml:637
 #, 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"
@@ -962,13 +1004,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:702
+#: random-bits.xml:678
 #, no-c-format
 msgid "Configure Apt"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:703
+#: random-bits.xml:679
 #, 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"
@@ -980,13 +1022,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:719
+#: random-bits.xml:695
 #, no-c-format
 msgid "Configure Locales and Keyboard"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:720
+#: random-bits.xml:696
 #, 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"
@@ -996,7 +1038,7 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:730
+#: random-bits.xml:706
 #, no-c-format
 msgid ""
       "# aptitude install console-setup\n"
@@ -1004,61 +1046,61 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:732
+#: random-bits.xml:708
 #, 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:742
+#: random-bits.xml:718
 #, no-c-format
 msgid "Install a Kernel"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:743
+#: random-bits.xml:719
 #, 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:748
+#: random-bits.xml:724
 #, no-c-format
 msgid "# apt-cache search &kernelpackage;"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:750
+#: random-bits.xml:726
 #, no-c-format
 msgid "Then install the kernel package of your choice using its package name."
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:754
+#: random-bits.xml:730
 #, no-c-format
 msgid "# aptitude install &kernelpackage;-<replaceable>arch-etc</replaceable>"
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:760
+#: random-bits.xml:736
 #, no-c-format
 msgid "Set up the Boot Loader"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:761
+#: random-bits.xml:737
 #, 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:768
+#: random-bits.xml:744
 #, 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:780
+#: random-bits.xml:756
 #, no-c-format
 msgid ""
       "Installing and setting up <classname>grub2</classname> is as easy as: <informalexample><screen>\n"
@@ -1069,19 +1111,19 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:790
+#: random-bits.xml:766
 #, 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:796
+#: random-bits.xml:772
 #, no-c-format
 msgid "Here is a basic <filename>/etc/lilo.conf</filename> as an example:"
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:800
+#: random-bits.xml:776
 #, no-c-format
 msgid ""
       "boot=/dev/<replaceable>hda6</replaceable>\n"
@@ -1095,13 +1137,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:802
+#: random-bits.xml:778
 #, 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:812
+#: random-bits.xml:788
 #, no-c-format
 msgid ""
       "Here is a basic <filename>/etc/yaboot.conf</filename> as an example: <informalexample><screen>\n"
@@ -1117,13 +1159,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:825
+#: random-bits.xml:801
 #, no-c-format
 msgid "Remote access: Installing SSH and setting up access"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:826
+#: random-bits.xml:802
 #, no-c-format
 msgid ""
       "In case you can login to the system via console, you can skip this section. If the system should be accessible via the network later on, you need to install SSH and set up access. <informalexample><screen>\n"
@@ -1142,7 +1184,7 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:850
+#: random-bits.xml:826
 #, no-c-format
 msgid ""
       "# adduser joe\n"
@@ -1150,13 +1192,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:855
+#: random-bits.xml:831
 #, no-c-format
 msgid "Finishing touches"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:856
+#: random-bits.xml:832
 #, 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"
@@ -1165,91 +1207,91 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:867
+#: random-bits.xml:843
 #, 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:873
+#: random-bits.xml:849
 #, no-c-format
 msgid "# aptitude clean"
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:884
+#: random-bits.xml:860
 #, no-c-format
 msgid "Installing &debian-gnu; over Parallel Line IP (PLIP)"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:886
+#: random-bits.xml:862
 #, 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:894
+#: random-bits.xml:870
 #, 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:902
+#: random-bits.xml:878
 #, 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:907
+#: random-bits.xml:883
 #, 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:917
+#: random-bits.xml:893
 #, no-c-format
 msgid "Requirements"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:920
+#: random-bits.xml:896
 #, no-c-format
 msgid "A target computer, called <emphasis>target</emphasis>, where &debian; will be installed."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:926
+#: random-bits.xml:902
 #, no-c-format
 msgid "System installation media; see <xref linkend=\"installation-media\"/>."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:931
+#: random-bits.xml:907
 #, 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:937
+#: random-bits.xml:913
 #, 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:949
+#: random-bits.xml:925
 #, no-c-format
 msgid "Setting up source"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:950
+#: random-bits.xml:926
 #, 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:955
+#: random-bits.xml:931
 #, no-c-format
 msgid ""
       "#!/bin/sh\n"
@@ -1270,13 +1312,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:961
+#: random-bits.xml:937
 #, no-c-format
 msgid "Installing target"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:962
+#: random-bits.xml:938
 #, 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"
@@ -1285,133 +1327,133 @@ msgid ""
 msgstr ""
 
 #. Tag: guimenuitem
-#: random-bits.xml:981
+#: random-bits.xml:957
 #, no-c-format
 msgid "Load installer components from CD"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:983
+#: random-bits.xml:959
 #, 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:991
+#: random-bits.xml:967
 #, no-c-format
 msgid "Detect network hardware"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:996
+#: random-bits.xml:972
 #, 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:1005
+#: random-bits.xml:981
 #, 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:1017
+#: random-bits.xml:993
 #, no-c-format
 msgid "Configure the network"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1020
+#: random-bits.xml:996
 #, no-c-format
 msgid "Auto-configure network with DHCP: No"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1025
+#: random-bits.xml:1001
 #, no-c-format
 msgid "IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1030
+#: random-bits.xml:1006
 #, no-c-format
 msgid "Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></userinput>"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1036
+#: random-bits.xml:1012
 #, 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:1055
+#: random-bits.xml:1031
 #, no-c-format
 msgid "Installing &debian-gnu; using PPP over Ethernet (PPPoE)"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1057
+#: random-bits.xml:1033
 #, 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:1065
+#: random-bits.xml:1041
 #, 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:1070
+#: random-bits.xml:1046
 #, 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:1077
+#: random-bits.xml:1053
 #, 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:1085
+#: random-bits.xml:1061
 #, 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:1100
+#: random-bits.xml:1076
 #, 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:1119
+#: random-bits.xml:1095
 #, 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:1125
+#: random-bits.xml:1101
 #, 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:1131
+#: random-bits.xml:1107
 #, 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:1140
+#: random-bits.xml:1116
 #, 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:1146
+#: random-bits.xml:1122
 #, 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 ""
diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot
index d78b84def..c0a58390b 100644
--- a/po/pot/using-d-i.pot
+++ b/po/pot/using-d-i.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: 2014-10-05 18:15+0000\n"
+"POT-Creation-Date: 2015-01-09 19:07+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"
@@ -1196,7 +1196,7 @@ msgstr ""
 #. Tag: entry
 #: using-d-i.xml:1350
 #, no-c-format
-msgid "Separate /home, /usr, /var and /tmp partitions"
+msgid "Separate /home, /var and /tmp partitions"
 msgstr ""
 
 #. Tag: entry
@@ -1208,7 +1208,7 @@ msgstr ""
 #. Tag: entry
 #: using-d-i.xml:1352
 #, no-c-format
-msgid "<filename>/</filename>, <filename>/home</filename>, <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap"
+msgid "<filename>/</filename>, <filename>/home</filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap"
 msgstr ""
 
 #. Tag: para
@@ -2075,305 +2075,299 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2561
 #, no-c-format
-msgid "By default, &d-i; installs the Xfce desktop environment. It is not possible to interactively select a different desktop environment during the installation, however, it <emphasis>is</emphasis> possible to have the installer install a different desktop environment by using preseeding (see <xref linkend=\"preseed-pkgsel\"/>) or by adding the parameter <literal>desktop=name_of_the_desktop_environment</literal> at the boot prompt when starting the installer. Possible variants in this case are <literal>desktop=gnome</literal>, <literal>desktop=kde</literal>, <literal>desktop=lxde</literal> or <literal>desktop=xfce</literal>."
+msgid "By default, &d-i; installs the <phrase arch=\"x86\">Gnome</phrase> <phrase arch=\"non-x86\">Xfce</phrase> desktop environment. It is possible to interactively select a different desktop environment during the installation. It is also possible to install multiple desktops, but some combinations of desktop may not be co-installable."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2575
-#, no-c-format
-msgid "If you use the special GNOME-, KDE- or LXDE-variant of the first CD in the full CD set, the installer installs the respective desktop environment instead of the default. Some CD images (netinst and DVD) also allow selection of the desired desktop environment from the graphical boot menu. Select the <quote>Advanced options</quote> option in the main menu and look for <quote>Alternative desktop environments</quote>."
-msgstr ""
-
-#. Tag: para
-#: using-d-i.xml:2586
+#: using-d-i.xml:2569
 #, no-c-format
 msgid "Note that this will only work if the packages needed for the desired desktop environment are actually available. If you are installing using a single full CD image, they will possibly need to be downloaded from a network mirror as some of the needed packages for your choice might only be included on later CDs. Installing any of the available desktop environments this way should work fine if you are using a DVD image or any other installation method."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2596
+#: using-d-i.xml:2579
 #, no-c-format
-msgid "The various server tasks will install software roughly as follows. DNS server: <classname>bind9</classname>; File server: <classname>samba</classname>, <classname>nfs</classname>; Mail server: <classname>exim4</classname>, <classname>spamassassin</classname>, <classname>uw-imap</classname>; Print server: <classname>cups</classname>; SQL database: <classname>postgresql</classname>; Web server: <classname>apache2</classname>."
+msgid "The various server tasks will install software roughly as follows. Web server: <classname>apache2</classname>; Print server: <classname>cups</classname>; SSH server: <classname>openssh</classname>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2607
+#: using-d-i.xml:2586
 #, no-c-format
 msgid "The <quote>Standard system</quote> task will install any package that has a priority <quote>standard</quote>. This includes a lot of common utilities that are normally available on any Linux or Unix system. You should leave this task selected unless you know what you are doing and want a really minimal system."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2615
+#: using-d-i.xml:2594
 #, no-c-format
 msgid "If during language selection a default locale other than the <quote>C</quote> locale was selected, <command>tasksel</command> will check if any localization tasks are defined for that locale and will automatically try to install relevant localization packages. This includes for example packages containing word lists or special fonts for your language. If a desktop environment was selected, it will also install appropriate localization packages for that (if available)."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2625
+#: using-d-i.xml:2604
 #, no-c-format
 msgid "Once you've selected your tasks, select &BTN-CONT;. At this point, <command>aptitude</command> will install the packages that are part of the selected tasks. If a particular program needs more information from the user, it will prompt you during this process."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2632
+#: using-d-i.xml:2611
 #, no-c-format
 msgid "You should be aware that especially the Desktop task is very large. Especially when installing from a normal CD-ROM in combination with a mirror for packages not on the CD-ROM, the installer may want to retrieve a lot of packages over the network. If you have a relatively slow Internet connection, this can take a long time. There is no option to cancel the installation of packages once it has started."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2641
+#: using-d-i.xml:2620
 #, no-c-format
 msgid "Even when packages are included on the CD-ROM, the installer may still retrieve them from the mirror if the version available on the mirror is more recent than the one included on the CD-ROM. If you are installing the stable distribution, this can happen after a point release (an update of the original stable release); if you are installing the testing distribution this will happen if you are using an older image."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2656
+#: using-d-i.xml:2635
 #, no-c-format
 msgid "Making Your System Bootable"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2658
+#: using-d-i.xml:2637
 #, no-c-format
 msgid "If you are installing a diskless workstation, obviously, booting off the local disk isn't a meaningful option, and this step will be skipped. <phrase arch=\"sparc\">You may wish to set OpenBoot to boot from the network by default; see <xref linkend=\"boot-dev-select-sun\"/>.</phrase>"
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2673
+#: using-d-i.xml:2652
 #, no-c-format
 msgid "Detecting other operating systems"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2675
+#: using-d-i.xml:2654
 #, no-c-format
 msgid "Before a boot loader is installed, the installer will attempt to probe for other operating systems which are installed on the machine. If it finds a supported operating system, you will be informed of this during the boot loader installation step, and the computer will be configured to boot this other operating system in addition to &debian;."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2683
+#: using-d-i.xml:2662
 #, no-c-format
 msgid "Note that multiple operating systems booting on a single machine is still something of a black art. The automatic support for detecting and setting up boot loaders to boot other operating systems varies by architecture and even by subarchitecture. If it does not work you should consult your boot manager's documentation for more information."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2701
+#: using-d-i.xml:2680
 #, no-c-format
 msgid "<command>palo</command>-installer"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2702
+#: using-d-i.xml:2681
 #, no-c-format
 msgid "The bootloader on PA-RISC is <quote>palo</quote>. <command>PALO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>PALO</command> allows you to boot any kernel image on your boot partition. This is because <command>PALO</command> can actually read Linux partitions."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2711
+#: using-d-i.xml:2690
 #, no-c-format
 msgid "hppa FIXME ( need more info )"
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2723
+#: using-d-i.xml:2702
 #, no-c-format
 msgid "Install the <command>Grub</command> Boot Loader on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2725
+#: using-d-i.xml:2704
 #, no-c-format
 msgid "The main &architecture; boot loader is called <quote>grub</quote>. Grub is a flexible and robust boot loader and a good default choice for new users and old hands alike."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2731
+#: using-d-i.xml:2710
 #, no-c-format
 msgid "By default, grub will be installed into the Master Boot Record (MBR), where it will take over complete control of the boot process. If you prefer, you can install it elsewhere. See the grub manual for complete information."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2737
+#: using-d-i.xml:2716
 #, no-c-format
 msgid "If you do not want to install grub, use the &BTN-GOBACK; button to get to the main menu, and from there select whatever bootloader you would like to use."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2750
+#: using-d-i.xml:2729
 #, no-c-format
 msgid "Install the <command>LILO</command> Boot Loader on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2752
+#: using-d-i.xml:2731
 #, no-c-format
 msgid "The second &architecture; boot loader is called <quote>LILO</quote>. It is an old complex program which offers lots of functionality, including DOS, Windows, and OS/2 boot management. Please carefully read the instructions in the directory <filename>/usr/share/doc/lilo/</filename> if you have special needs; also see the <ulink url=\"&url-lilo-howto;\">LILO mini-HOWTO</ulink>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2762
+#: using-d-i.xml:2741
 #, no-c-format
 msgid "Currently the LILO installation will only create menu entries for other operating systems if these can be <firstterm>chainloaded</firstterm>. This means you may have to manually add a menu entry for operating systems like GNU/Linux and GNU/Hurd after the installation."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2770
+#: using-d-i.xml:2749
 #, no-c-format
 msgid "&d-i; offers you three choices on where to install the <command>LILO</command> boot loader:"
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:2777
+#: using-d-i.xml:2756
 #, no-c-format
 msgid "Master Boot Record (MBR)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2777
+#: using-d-i.xml:2756
 #, no-c-format
 msgid "This way the <command>LILO</command> will take complete control of the boot process."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:2784
+#: using-d-i.xml:2763
 #, no-c-format
 msgid "new &debian; partition"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2784
+#: using-d-i.xml:2763
 #, no-c-format
 msgid "Choose this if you want to use another boot manager. <command>LILO</command> will install itself at the beginning of the new &debian; partition and it will serve as a secondary boot loader."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:2793
+#: using-d-i.xml:2772
 #, no-c-format
 msgid "Other choice"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2793
+#: using-d-i.xml:2772
 #, no-c-format
 msgid "Useful for advanced users who want to install <command>LILO</command> somewhere else. In this case you will be asked for desired location. You can use traditional device names such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2803
+#: using-d-i.xml:2782
 #, no-c-format
 msgid "If you can no longer boot into Windows 9x (or DOS) after this step, you'll need to use a Windows 9x (MS-DOS) boot disk and use the <userinput>fdisk /mbr</userinput> command to reinstall the MS-DOS master boot record &mdash; however, this means that you'll need to use some other way to get back into &debian;!"
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2819
+#: using-d-i.xml:2798
 #, no-c-format
 msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2821
+#: using-d-i.xml:2800
 #, no-c-format
 msgid "The &architecture; boot loader is called <quote>elilo</quote>. It is modeled on the <quote>lilo</quote> boot loader for the x86 architecture and uses a similar configuration file. However, instead of writing an MBR or partition boot record to the disk, it copies the necessary files to a separate FAT formatted disk partition and modifies the <guimenuitem>EFI Boot Manager</guimenuitem> menu in the firmware to point to the files in the EFI partition. The <command>elilo</command> boot loader is really in two parts. The <filename>/usr/sbin/elilo</filename> command manages the partition and copies files into it. The <filename>elilo.efi</filename> program is copied into the EFI partition and then run by the <quote>EFI Boot Manager</quote> to do the actual work of loading and starting the Linux kernel."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2837
+#: using-d-i.xml:2816
 #, no-c-format
 msgid "The <quote>elilo</quote> configuration and installation is done as the last step of installing the packages of the base installation. &d-i; will present you with a list of potential disk partitions that it has found suitable for an EFI partition. Select the partition you set up earlier in the installation, typically a partition on the same disk that contains your <emphasis>root</emphasis> filesystem."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2849
+#: using-d-i.xml:2828
 #, no-c-format
 msgid "Choose the correct partition!"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2851
+#: using-d-i.xml:2830
 #, no-c-format
 msgid "The criterion for selecting a partition is that it must be a FAT format filesystem with its <emphasis>boot</emphasis> flag set. &d-i; may show multiple choices depending on what it finds from scanning all of the disks of the system including EFI partitions of other system disks and EFI diagnostic partitions. Remember, <command>elilo</command> may format the partition during the installation, erasing any previous contents!"
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2866
+#: using-d-i.xml:2845
 #, no-c-format
 msgid "EFI Partition Contents"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2868
+#: using-d-i.xml:2847
 #, no-c-format
 msgid "The EFI partition is a FAT filesystem format partition on one of the hard disks of the system, usually the same disk that contains the <emphasis>root</emphasis> filesystem. It is normally not mounted on a running system as it is only needed by the <quote>EFI Boot Manager</quote> to load the system and the installer part of the <command>elilo</command> writes to the filesystem directly. The <command>/usr/sbin/elilo</command> utility writes the following files into the <filename>efi/debian</filename> directory of the EFI partition during the installation. Note that the <quote>EFI Boot Manager</quote> would find these files using the path <filename>fs<replaceable>n</replaceable>:\\efi\\debian</filename>. There may be other files in this filesystem as well over time as the system is updated or re-configured."
 msgstr ""
 
 #. Tag: filename
-#: using-d-i.xml:2890
+#: using-d-i.xml:2869
 #, no-c-format
 msgid "elilo.conf"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2891
+#: using-d-i.xml:2870
 #, no-c-format
 msgid "This is the configuration file read by the boot loader when it starts. It is a copy of the <filename>/etc/elilo.conf</filename> with the filenames re-written to refer to files in the EFI partition."
 msgstr ""
 
 #. Tag: filename
-#: using-d-i.xml:2900
+#: using-d-i.xml:2879
 #, no-c-format
 msgid "elilo.efi"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2901
+#: using-d-i.xml:2880
 #, no-c-format
 msgid "This is the boot loader program that the <quote>EFI Boot Manager</quote> runs to boot the system. It is the program behind the <guimenuitem>&debian; GNU/Linux</guimenuitem> menu item of the <quote>EFI Boot Manager</quote> command menu."
 msgstr ""
 
 #. Tag: filename
-#: using-d-i.xml:2911
+#: using-d-i.xml:2890
 #, no-c-format
 msgid "initrd.img"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2912
+#: using-d-i.xml:2891
 #, no-c-format
 msgid "This is the initial root filesystem used to boot the kernel. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard &debian; installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/initrd.img</filename>."
 msgstr ""
 
 #. Tag: filename
-#: using-d-i.xml:2924
+#: using-d-i.xml:2903
 #, no-c-format
 msgid "readme.txt"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2925
+#: using-d-i.xml:2904
 #, no-c-format
 msgid "This is a small text file warning you that the contents of the directory are managed by the <command>elilo</command> and that any local changes would be lost at the next time <filename>/usr/sbin/elilo</filename> is run."
 msgstr ""
 
 #. Tag: filename
-#: using-d-i.xml:2935
+#: using-d-i.xml:2914
 #, no-c-format
 msgid "vmlinuz"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2936
+#: using-d-i.xml:2915
 #, no-c-format
 msgid "This is the compressed kernel itself. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard &debian; installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/vmlinuz</filename>."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2956
+#: using-d-i.xml:2935
 #, no-c-format
 msgid "<command>arcboot</command>-installer"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2957
+#: using-d-i.xml:2936
 #, no-c-format
 msgid ""
       "The boot loader on SGI machines is <command>arcboot</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). Arcboot supports different configurations which are set up in <filename>/etc/arcboot.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After arcboot has been installed, the system can be booted from hard disk by setting some firmware environment variables entering <informalexample><screen>\n"
@@ -2386,313 +2380,313 @@ msgid ""
 msgstr ""
 
 #. Tag: replaceable
-#: using-d-i.xml:2976
+#: using-d-i.xml:2955
 #, no-c-format
 msgid "scsi"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2977
+#: using-d-i.xml:2956
 #, no-c-format
 msgid "is the SCSI bus to be booted from, this is <userinput>0</userinput> for the onboard controllers"
 msgstr ""
 
 #. Tag: replaceable
-#: using-d-i.xml:2985
+#: using-d-i.xml:2964
 #, no-c-format
 msgid "disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2986
+#: using-d-i.xml:2965
 #, no-c-format
 msgid "is the SCSI ID of the hard disk on which <command>arcboot</command> is installed"
 msgstr ""
 
 #. Tag: replaceable
-#: using-d-i.xml:2994
+#: using-d-i.xml:2973
 #, no-c-format
 msgid "partnr"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2995
+#: using-d-i.xml:2974
 #, no-c-format
 msgid "is the number of the partition on which <filename>/etc/arcboot.conf</filename> resides"
 msgstr ""
 
 #. Tag: replaceable
-#: using-d-i.xml:3003
+#: using-d-i.xml:2982
 #, no-c-format
 msgid "config"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3004
+#: using-d-i.xml:2983
 #, no-c-format
 msgid "is the name of the configuration entry in <filename>/etc/arcboot.conf</filename>, which is <quote>linux</quote> by default."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:3025
+#: using-d-i.xml:3004
 #, no-c-format
 msgid "Install <command>Yaboot</command> on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3026
+#: using-d-i.xml:3005
 #, no-c-format
 msgid "Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as their boot loader. The installer will set up <command>yaboot</command> automatically, so all you need is a small 820k partition named <quote>bootstrap</quote> with type <emphasis>Apple_Bootstrap</emphasis> created back in the partitioning component. If this step completes successfully then your disk should now be bootable and OpenFirmware will be set to boot &debian-gnu;."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:3044
+#: using-d-i.xml:3023
 #, no-c-format
 msgid "Install <command>Quik</command> on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3045
+#: using-d-i.xml:3024
 #, no-c-format
 msgid "The boot loader for OldWorld Power Macintosh machines is <command>quik</command>. You can also use it on CHRP. The installer will attempt to set up <command>quik</command> automatically. The setup has been known to work on 7200, 7300, and 7600 Powermacs, and on some Power Computing clones."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:3061
+#: using-d-i.xml:3040
 #, no-c-format
 msgid "<command>zipl</command>-installer"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3062
+#: using-d-i.xml:3041
 #, no-c-format
 msgid "The boot loader on &arch-title; is <quote>zipl</quote>. <command>ZIPL</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. Please take a look at <quote>LINUX for &arch-title; Device Drivers and Installation Commands</quote> from IBM's developerWorks web site if you want to know more about <command>ZIPL</command>."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:3079
+#: using-d-i.xml:3058
 #, no-c-format
 msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3081
+#: using-d-i.xml:3060
 #, no-c-format
 msgid "The standard &architecture; boot loader is called <quote>silo</quote>. It is documented in <filename>/usr/share/doc/silo/</filename>. <command>SILO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>SILO</command> allows you to boot any kernel image on your drive, even if it is not listed in <filename>/etc/silo.conf</filename>. This is because <command>SILO</command> can actually read Linux partitions. Also, <filename>/etc/silo.conf</filename> is read at boot time, so there is no need to rerun <command>silo</command> after installing a new kernel like you would with <command>LILO</command>. <command>SILO</command> can also read UFS partitions, which means it can boot SunOS/Solaris partitions as well. This is useful if you want to install GNU/Linux alongside an existing SunOS/Solaris install."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:3106
+#: using-d-i.xml:3085
 #, no-c-format
 msgid "Making the system bootable with flash-kernel"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3107
+#: using-d-i.xml:3086
 #, no-c-format
 msgid "As there is no common firmware interface on all ARM platforms, the steps required to make the system bootable on ARM devices are highly device-dependent. &debian; uses a tool called <command>flash-kernel </command> to take care of this. Flash-kernel contains a database which describes the particular operations that are required to make the system bootable on various devices. It detects whether the current device is supported, and if yes, performs the necessary operations."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3118
+#: using-d-i.xml:3097
 #, no-c-format
 msgid "On devices which boot from internal NOR- or NAND-flash memory, flash-kernel writes the kernel and the initial ramdisk to this internal memory. This method is particularly common on older armel devices. Please note that most of these devices do not allow having multiple kernels and ramdisks in their internal flash memory, i.e. running flash-kernel on them usually overwrites the previous contents of the flash memory!"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3128
+#: using-d-i.xml:3107
 #, no-c-format
 msgid "For ARM systems that use u-boot as their system firmware and boot the kernel and the initial ramdisk from external storage media (such as MMC/SD-cards, USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an appropriate boot script to allow autobooting without user interaction."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:3144
+#: using-d-i.xml:3123
 #, no-c-format
 msgid "Continue Without Boot Loader"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3146
+#: using-d-i.xml:3125
 #, no-c-format
 msgid "This option can be used to complete the installation even when no boot loader is to be installed, either because the arch/subarch doesn't provide one, or because none is desired (e.g. you will use existing boot loader)."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3153
+#: using-d-i.xml:3132
 #, no-c-format
 msgid "If you plan to manually configure your bootloader, you should check the name of the installed kernel in <filename>/target/boot</filename>. You should also check that directory for the presence of an <firstterm>initrd</firstterm>; if one is present, you will probably have to instruct your bootloader to use it. Other information you will need are the disk and partition you selected for your <filename>/</filename> filesystem and, if you chose to install <filename>/boot</filename> on a separate partition, also your <filename>/boot</filename> filesystem."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:3170
+#: using-d-i.xml:3149
 #, no-c-format
 msgid "Finishing the Installation"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3171
+#: using-d-i.xml:3150
 #, no-c-format
 msgid "This is the last step in the &debian; installation process during which the installer will do any last minute tasks. It mostly consists of tidying up after the &d-i;."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:3184
+#: using-d-i.xml:3163
 #, no-c-format
 msgid "Setting the System Clock"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3186
+#: using-d-i.xml:3165
 #, no-c-format
 msgid "The installer may ask you if the computer's clock is set to UTC. Normally this question is avoided if possible and the installer tries to work out whether the clock is set to UTC based on things like what other operating systems are installed."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3193
+#: using-d-i.xml:3172
 #, no-c-format
 msgid "In expert mode you will always be able to choose whether or not the clock is set to UTC. <phrase arch=\"powerpc\">Macintosh hardware clocks are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase> <phrase arch=\"any-x86\">Systems that (also) run Dos or Windows are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3204
+#: using-d-i.xml:3183
 #, no-c-format
 msgid "At this point &d-i; will also attempt to save the current time to the system's hardware clock. This will be done either in UTC or local time, depending on the selection that was just made."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:3219
+#: using-d-i.xml:3198
 #, no-c-format
 msgid "Reboot the System"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3221
+#: using-d-i.xml:3200
 #, no-c-format
 msgid "You will be prompted to remove the boot media (CD, floppy, etc) that you used to boot the installer. After that the system will be rebooted into your new &debian; system."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3227
+#: using-d-i.xml:3206
 #, no-c-format
 msgid "After a final prompt the system will be halted because rebooting is not supported on &arch-title;. You then need to IPL &debian-gnu; from the DASD which you selected for the root filesystem during the first steps of the installation."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:3240
+#: using-d-i.xml:3219
 #, no-c-format
 msgid "Troubleshooting"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3241
+#: using-d-i.xml:3220
 #, no-c-format
 msgid "The components listed in this section are usually not involved in the installation process, but are waiting in the background to help the user in case something goes wrong."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:3254
+#: using-d-i.xml:3233
 #, no-c-format
 msgid "Saving the installation logs"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3256
+#: using-d-i.xml:3235
 #, no-c-format
 msgid "If the installation is successful, the logfiles created during the installation process will be automatically saved to <filename>/var/log/installer/</filename> on your new &debian; system."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3263
+#: using-d-i.xml:3242
 #, no-c-format
 msgid "Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu allows you to save the log files to a floppy disk, network, hard disk, or other media. This can be useful if you encounter fatal problems during the installation and wish to study the logs on another system or attach them to an installation report."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:3283
+#: using-d-i.xml:3262
 #, no-c-format
 msgid "Using the Shell and Viewing the Logs"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3285
+#: using-d-i.xml:3264
 #, no-c-format
 msgid "There are several methods you can use to get a shell while running an installation. On most systems, and if you are not installing over serial console, the easiest method is to switch to the second <emphasis>virtual console</emphasis> by pressing <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo><footnote> <para> That is: press the <keycap>Alt</keycap> key on the left-hand side of the <keycap>space bar</keycap> and the <keycap>F2</keycap> function key at the same time. </para> </footnote> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap></keycombo>). Use <keycombo><keycap>Left Alt</keycap> <keycap>F1</keycap></keycombo> to switch back to the installer itself."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3303
+#: using-d-i.xml:3282
 #, no-c-format
 msgid "For the graphical installer see also <xref linkend=\"gtk-using\"/>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3307
+#: using-d-i.xml:3286
 #, no-c-format
 msgid "If you cannot switch consoles, there is also an <guimenuitem>Execute a Shell</guimenuitem> item on the main menu that can be used to start a shell. You can get to the main menu from most dialogs by using the &BTN-GOBACK; button one or more times. Type <userinput>exit</userinput> to close the shell and return to the installer."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3315
+#: using-d-i.xml:3294
 #, no-c-format
 msgid "At this point you are booted from the RAM disk, and there is a limited set of Unix utilities available for your use. You can see what programs are available with the command <command>ls /bin /sbin /usr/bin /usr/sbin</command> and by typing <command>help</command>. The shell is a Bourne shell clone called <command>ash</command> and has some nice features like autocompletion and history."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3324
+#: using-d-i.xml:3303
 #, no-c-format
 msgid "To edit and view files, use the text editor <command>nano</command>. Log files for the installation system can be found in the <filename>/var/log</filename> directory."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3331
+#: using-d-i.xml:3310
 #, no-c-format
 msgid "Although you can do basically anything in a shell that the available commands allow you to do, the option to use a shell is really only there in case something goes wrong and for debugging."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3337
+#: using-d-i.xml:3316
 #, no-c-format
 msgid "Doing things manually from the shell may interfere with the installation process and result in errors or an incomplete installation. In particular, you should always use let the installer activate your swap partition and not do this yourself from a shell."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:3353
+#: using-d-i.xml:3332
 #, no-c-format
 msgid "Installation Over the Network"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3355
+#: using-d-i.xml:3334
 #, no-c-format
 msgid "One of the more interesting components is <firstterm>network-console</firstterm>. It allows you to do a large part of the installation over the network via SSH. The use of the network implies you will have to perform the first steps of the installation from the console, at least to the point of setting up the networking. (Although you can automate that part with <xref linkend=\"automatic-install\"/>.)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3365
+#: using-d-i.xml:3344
 #, no-c-format
 msgid "This component is not loaded into the main installation menu by default, so you have to explicitly ask for it. If you are installing from CD, you need to boot with medium priority or otherwise invoke the main installation menu and choose <guimenuitem>Load installer components from CD</guimenuitem> and from the list of additional components select <guimenuitem>network-console: Continue installation remotely using SSH</guimenuitem>. Successful load is indicated by a new menu entry called <guimenuitem>Continue installation remotely using SSH</guimenuitem>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3378
+#: using-d-i.xml:3357
 #, no-c-format
 msgid "For installations on &arch-title;, this is the default method after setting up the network."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3383
+#: using-d-i.xml:3362
 #, no-c-format
 msgid "<phrase arch=\"not-s390\">After selecting this new entry, you</phrase> <phrase arch=\"s390\">You</phrase> will be asked for a new password to be used for connecting to the installation system and for its confirmation. That's all. Now you should see a screen which instructs you to login remotely as the user <emphasis>installer</emphasis> with the password you just provided. Another important detail to notice on this screen is the fingerprint of this system. You need to transfer the fingerprint securely to the person who will continue the installation remotely."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3395
+#: using-d-i.xml:3374
 #, no-c-format
 msgid "Should you decide to continue with the installation locally, you can always press &enterkey;, which will bring you back to the main menu, where you can select another component."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3401
+#: using-d-i.xml:3380
 #, no-c-format
 msgid ""
       "Now let's switch to the other side of the wire. As a prerequisite, you need to configure your terminal for UTF-8 encoding, because that is what the installation system uses. If you do not, remote installation will be still possible, but you may encounter strange display artefacts like destroyed dialog borders or unreadable non-ascii characters. Establishing a connection with the installation system is as simple as typing: <informalexample><screen>\n"
@@ -2701,127 +2695,127 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3418
+#: using-d-i.xml:3397
 #, no-c-format
 msgid "The <command>ssh</command> server in the installer uses a default configuration that does not send keep-alive packets. In principle, a connection to the system being installed should be kept open indefinitely. However, in some situations &mdash; depending on your local network setup &mdash; the connection may be lost after some period of inactivity. One common case where this can happen is when there is some form of Network Address Translation (NAT) somewhere between the client and the system being installed. Depending on at which point of the installation the connection was lost, you may or may not be able to resume the installation after reconnecting."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3431
+#: using-d-i.xml:3410
 #, no-c-format
 msgid "You may be able to avoid the connection being dropped by adding the option <userinput>-o&nbsp;ServerAliveInterval=<replaceable>value</replaceable></userinput> when starting the <command>ssh</command> connection, or by adding that option in your <command>ssh</command> configuration file. Note however that in some cases adding this option may also <emphasis>cause</emphasis> a connection to be dropped (for example if keep-alive packets are sent during a brief network outage, from which <command>ssh</command> would otherwise have recovered), so it should only be used when needed."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3444
+#: using-d-i.xml:3423
 #, no-c-format
 msgid "If you install several computers in turn and they happen to have the same IP address or hostname, <command>ssh</command> will refuse to connect to such host. The reason is that it will have different fingerprint, which is usually a sign of a spoofing attack. If you are sure this is not the case, you will need to delete the relevant line from <filename>~/.ssh/known_hosts</filename><footnote> <para> The following command will remove an existing entry for a host: <command>ssh-keygen -R &lt;<replaceable>hostname</replaceable>|<replaceable>IP&nbsp;address</replaceable>&gt;</command>. </para> </footnote> and try again."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3460
+#: using-d-i.xml:3439
 #, no-c-format
 msgid "After the login you will be presented with an initial screen where you have two possibilities called <guimenuitem>Start menu</guimenuitem> and <guimenuitem>Start shell</guimenuitem>. The former brings you to the main installer menu, where you can continue with the installation as usual. The latter starts a shell from which you can examine and possibly fix the remote system. You should only start one SSH session for the installation menu, but may start multiple sessions for shells."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3470
+#: using-d-i.xml:3449
 #, no-c-format
 msgid "After you have started the installation remotely over SSH, you should not go back to the installation session running on the local console. Doing so may corrupt the database that holds the configuration of the new system. This in turn may result in a failed installation or problems with the installed system."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:3489
+#: using-d-i.xml:3468
 #, no-c-format
 msgid "Loading Missing Firmware"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3490
+#: using-d-i.xml:3469
 #, no-c-format
 msgid "As described in <xref linkend=\"hardware-firmware\"/>, some devices require firmware to be loaded. In most cases the device will not work at all if the firmware is not available; sometimes basic functionality is not impaired if it is missing and the firmware is only needed to enable additional features."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3498
+#: using-d-i.xml:3477
 #, no-c-format
 msgid "If a device driver requests firmware that is not available, &d-i; will display a dialog offering to load the missing firmware. If this option is selected, &d-i; will scan available devices for either loose firmware files or packages containing firmware. If found, the firmware will be copied to the correct location (<filename>/lib/firmware</filename>) and the driver module will be reloaded."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3508
+#: using-d-i.xml:3487
 #, no-c-format
 msgid "Which devices are scanned and which file systems are supported depends on the architecture, the installation method and the stage of the installation. Especially during the early stages of the installation, loading the firmware is most likely to succeed from a FAT-formatted floppy disk or USB stick. <phrase arch=\"x86\">On i386 and amd64 firmware can also be loaded from an MMC or SD card.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3518
+#: using-d-i.xml:3497
 #, no-c-format
 msgid "Note that it is possible to skip loading the firmware if you know the device will also function without it, or if the device is not needed during the installation."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3524
+#: using-d-i.xml:3503
 #, no-c-format
 msgid "&d-i; only prompts for firmware needed by kernel modules loaded during the installation. Not all drivers are included in &d-i;, in particular radeon is not, so this implies that the capabilities of some devices may be no different at the end of the installation from what they were at the beginning. Consequently, some of your hardware may not be being used to its full potential. If you suspect this is the case, or are just curious, it is not a bad idea to check the output of the <command>dmesg</command> command on the newly booted system and search for <quote>firmware</quote>."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:3538
+#: using-d-i.xml:3517
 #, no-c-format
 msgid "Preparing a medium"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3539
+#: using-d-i.xml:3518
 #, no-c-format
 msgid "Official CD images do not include non-free firmware. The most common method to load such firmware is from some removable medium such as a USB stick. Alternatively, unofficial CD builds containing non-free firmware can be found at <ulink url=\"&url-firmware-cds;\"></ulink>. To prepare a USB stick (or other medium like a hard drive partition, or floppy disk), the firmware files or packages must be placed in either the root directory or a directory named <filename>/firmware</filename> of the file system on the medium. The recommended file system to use is FAT as that is most certain to be supported during the early stages of the installation."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3552
+#: using-d-i.xml:3531
 #, no-c-format
 msgid "Tarballs and zip files containing current packages for the most common firmware are available from: <itemizedlist> <listitem><para> <ulink url=\"&url-firmware-tarballs;\"></ulink> </para></listitem> </itemizedlist> Just download the tarball or zip file for the correct release and unpack it to the file system on the medium."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3566
+#: using-d-i.xml:3545
 #, no-c-format
 msgid "If the firmware you need is not included in the tarball, you can also download specific firmware packages from the (non-free section of the) archive. The following overview should list most available firmware packages but is not guaranteed to be complete and may also contain non-firmware packages:"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3580
+#: using-d-i.xml:3559
 #, no-c-format
 msgid "It is also possible to copy individual firmware files to the medium. Loose firmware could be obtained for example from an already installed system or from a hardware vendor."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:3589
+#: using-d-i.xml:3568
 #, no-c-format
 msgid "Firmware and the Installed System"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3590
+#: using-d-i.xml:3569
 #, no-c-format
 msgid "Any firmware loaded during the installation will be copied automatically to the installed system. In most cases this will ensure that the device that requires the firmware will also work correctly after the system is rebooted into the installed system. However, if the installed system runs a different kernel version from the installer there is a slight chance that the firmware cannot be loaded due to version skew."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3599
+#: using-d-i.xml:3578
 #, no-c-format
 msgid "If the firmware was loaded from a firmware package, &d-i; will also install this package for the installed system and will automatically add the non-free section of the package archive in APT's <filename>sources.list</filename>. This has the advantage that the firmware should be updated automatically if a new version becomes available."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3607
+#: using-d-i.xml:3586
 #, no-c-format
 msgid "If loading the firmware was skipped during the installation, the relevant device will probably not work with the installed system until the firmware (package) is installed manually."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3614
+#: using-d-i.xml:3593
 #, no-c-format
 msgid "If the firmware was loaded from loose firmware files, the firmware copied to the installed system will <emphasis>not</emphasis> be automatically updated unless the corresponding firmware package (if available) is installed after the installation is completed."
 msgstr ""