Refresh po and pot files after changings in en

6 files changed, 918 insertions, 987 deletions

diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot
index 6f95ebfad..b6ae6c268 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-03 08:11+0000\n"
+"POT-Creation-Date: 2014-08-26 20:40+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:1172 boot-installer.xml:1356 boot-installer.xml:1679 boot-installer.xml:1789
+#: boot-installer.xml:70 boot-installer.xml:630 boot-installer.xml:1252 boot-installer.xml:1436 boot-installer.xml:1759 boot-installer.xml:1869
 #, 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:1178 boot-installer.xml:1362 boot-installer.xml:1685 boot-installer.xml:1795
+#: boot-installer.xml:76 boot-installer.xml:636 boot-installer.xml:1258 boot-installer.xml:1442 boot-installer.xml:1765 boot-installer.xml:1875
 #, 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:1183 boot-installer.xml:1367 boot-installer.xml:1690 boot-installer.xml:1800
+#: boot-installer.xml:81 boot-installer.xml:641 boot-installer.xml:1263 boot-installer.xml:1447 boot-installer.xml:1770 boot-installer.xml:1880
 #, no-c-format
 msgid "The server-side setup to support network booting is described in <xref linkend=\"install-tftp\"/>."
 msgstr ""
@@ -183,31 +183,31 @@ msgid "Note: When booting standard linux images, it is important to load the ini
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:286 boot-installer.xml:785 boot-installer.xml:1442 boot-installer.xml:1823
+#: boot-installer.xml:286 boot-installer.xml:865 boot-installer.xml:1522 boot-installer.xml:1903
 #, no-c-format
 msgid "Booting from a CD-ROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:292 boot-installer.xml:791 boot-installer.xml:1448 boot-installer.xml:1829
+#: boot-installer.xml:292 boot-installer.xml:871 boot-installer.xml:1528 boot-installer.xml:1909
 #, 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:802 boot-installer.xml:1459 boot-installer.xml:1840
+#: boot-installer.xml:303 boot-installer.xml:882 boot-installer.xml:1539 boot-installer.xml:1920
 #, 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:810 boot-installer.xml:1467 boot-installer.xml:1848
+#: boot-installer.xml:311 boot-installer.xml:890 boot-installer.xml:1547 boot-installer.xml:1928
 #, 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:818 boot-installer.xml:1475 boot-installer.xml:1856
+#: boot-installer.xml:319 boot-installer.xml:898 boot-installer.xml:1555 boot-installer.xml:1936
 #, no-c-format
 msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
 msgstr ""
@@ -379,13 +379,13 @@ msgid "Let's assume you have prepared everything from <xref linkend=\"boot-dev-s
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:566 boot-installer.xml:1729
+#: boot-installer.xml:566 boot-installer.xml:1809
 #, no-c-format
 msgid "Booting from Floppies"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:567 boot-installer.xml:1737
+#: boot-installer.xml:567 boot-installer.xml:1817
 #, 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 ""
@@ -427,7 +427,7 @@ msgid "After booting from the boot floppy, the root floppy is requested. Insert
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:624 boot-installer.xml:1154 boot-installer.xml:1296 boot-installer.xml:1350 boot-installer.xml:1673 boot-installer.xml:1783
+#: boot-installer.xml:624 boot-installer.xml:1234 boot-installer.xml:1376 boot-installer.xml:1430 boot-installer.xml:1753 boot-installer.xml:1863
 #, no-c-format
 msgid "Booting with TFTP"
 msgstr ""
@@ -506,7 +506,7 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:705
 #, no-c-format
-msgid "For a normal installation, select either the <quote>Install</quote> or the <quote>Graphical install</quote> entry &mdash; using either the arrow keys on your keyboard or by typing the first (highlighted) letter, the <quote>Install</quote> entry is already selected by default &mdash; and press &enterkey; to boot the installer."
+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
@@ -549,241 +549,295 @@ msgid "To bypass the graphical boot screen you can either blindly press &escapek
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:826
+#: boot-installer.xml:782
+#, no-c-format
+msgid "The Graphical Installer"
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:783
+#, 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
+#, 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
+#, 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
+#, 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
+#, 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
+#, 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
+#, 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
+#, 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
 #, no-c-format
 msgid "CD Contents"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:828
+#: boot-installer.xml:908
 #, 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:844
+#: boot-installer.xml:924
 #, 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:860
+#: boot-installer.xml:940
 #, 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:869
+#: boot-installer.xml:949
 #, 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:881
+#: boot-installer.xml:961
 #, 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:900
+#: boot-installer.xml:980
 #, no-c-format
 msgid "IMPORTANT"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:901
+#: boot-installer.xml:981
 #, 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:913
+#: boot-installer.xml:993
 #, no-c-format
 msgid "Option 1: Booting from the Boot Option Maintenance Menu"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:920
+#: boot-installer.xml:1000
 #, 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:926
+#: boot-installer.xml:1006
 #, 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:932
+#: boot-installer.xml:1012
 #, 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:943
+#: boot-installer.xml:1023
 #, 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:954
+#: boot-installer.xml:1034
 #, 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:966
+#: boot-installer.xml:1046
 #, 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:976
+#: boot-installer.xml:1056
 #, no-c-format
 msgid "Option 2: Booting from the EFI Shell"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:977
+#: boot-installer.xml:1057
 #, 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:988
+#: boot-installer.xml:1068
 #, 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:994
+#: boot-installer.xml:1074
 #, 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:1008
+#: boot-installer.xml:1088
 #, 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:1015
+#: boot-installer.xml:1095
 #, 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:1022
+#: boot-installer.xml:1102
 #, 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:1029
+#: boot-installer.xml:1109
 #, 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:1043
+#: boot-installer.xml:1123
 #, no-c-format
 msgid "Installing using a Serial Console"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1045
+#: boot-installer.xml:1125
 #, 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:1056
+#: boot-installer.xml:1136
 #, 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:1063
+#: boot-installer.xml:1143
 #, 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:1074
+#: boot-installer.xml:1154
 #, 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:1083
+#: boot-installer.xml:1163
 #, 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:1092
+#: boot-installer.xml:1172
 #, no-c-format
 msgid "Selecting the Boot Kernel and Options"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1094
+#: boot-installer.xml:1174
 #, 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:1106
+#: boot-installer.xml:1186
 #, 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:1124
+#: boot-installer.xml:1204
 #, 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:1129
+#: boot-installer.xml:1209
 #, 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:1136
+#: boot-installer.xml:1216
 #, 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:1145 boot-installer.xml:1282
+#: boot-installer.xml:1225 boot-installer.xml:1362
 #, 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:1156
+#: boot-installer.xml:1236
 #, 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:1191
+#: boot-installer.xml:1271
 #, 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:1202
+#: boot-installer.xml:1282
 #, no-c-format
 msgid "Configuring the Server"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1203
+#: boot-installer.xml:1283
 #, no-c-format
 msgid ""
       "A suitable TFTP entry for network booting an IA-64 system looks something like this: <informalexample><screen>\n"
@@ -796,13 +850,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1213
+#: boot-installer.xml:1293
 #, 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:1223
+#: boot-installer.xml:1303
 #, no-c-format
 msgid ""
       "# cd /var/lib/tftp\n"
@@ -814,37 +868,37 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1223
+#: boot-installer.xml:1303
 #, 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:1240
+#: boot-installer.xml:1320
 #, no-c-format
 msgid "Configuring the Client"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1241
+#: boot-installer.xml:1321
 #, 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:1273
+#: boot-installer.xml:1353
 #, 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:1299 boot-installer.xml:1323
+#: boot-installer.xml:1379 boot-installer.xml:1403
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1300
+#: boot-installer.xml:1380
 #, no-c-format
 msgid ""
       "After entering the command monitor use <informalexample><screen>\n"
@@ -855,19 +909,19 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1320 boot-installer.xml:2075
+#: boot-installer.xml:1400 boot-installer.xml:2155
 #, no-c-format
 msgid "Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1324
+#: boot-installer.xml:1404
 #, 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:1329
+#: boot-installer.xml:1409
 #, 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"
@@ -876,43 +930,43 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1339
+#: boot-installer.xml:1419
 #, no-c-format
 msgid "bootp(): append=\"root=/dev/sda1\""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1382
+#: boot-installer.xml:1462
 #, no-c-format
 msgid "s390 Limitations"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1383
+#: boot-installer.xml:1463
 #, 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:1388
+#: boot-installer.xml:1468
 #, 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:1399
+#: boot-installer.xml:1479
 #, no-c-format
 msgid "s390 Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1400
+#: boot-installer.xml:1480
 #, 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:1417
+#: boot-installer.xml:1497
 #, 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"
@@ -924,13 +978,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1482
+#: boot-installer.xml:1562
 #, 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:1491
+#: boot-installer.xml:1571
 #, 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"
@@ -939,79 +993,79 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:1502
+#: boot-installer.xml:1582
 #, no-c-format
 msgid "0 &gt; boot cd:,\\install\\yaboot"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1504
+#: boot-installer.xml:1584
 #, 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:1513
+#: boot-installer.xml:1593
 #, 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:1519
+#: boot-installer.xml:1599
 #, no-c-format
 msgid "boot cd install/pegasos"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1521
+#: boot-installer.xml:1601
 #, 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:1526
+#: boot-installer.xml:1606
 #, no-c-format
 msgid "0 > boot cdrom"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1532
+#: boot-installer.xml:1612
 #, no-c-format
 msgid "Booting from Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1538
+#: boot-installer.xml:1618
 #, 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:1544
+#: boot-installer.xml:1624
 #, 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:1564
+#: boot-installer.xml:1644
 #, no-c-format
 msgid "Booting OldWorld PowerMacs from MacOS"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1565
+#: boot-installer.xml:1645
 #, 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:1583
+#: boot-installer.xml:1663
 #, no-c-format
 msgid "Booting NewWorld Macs from OpenFirmware"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1584
+#: boot-installer.xml:1664
 #, 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"
@@ -1022,31 +1076,31 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1616
+#: boot-installer.xml:1696
 #, no-c-format
 msgid "Booting from USB memory stick"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1617
+#: boot-installer.xml:1697
 #, no-c-format
 msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1623
+#: boot-installer.xml:1703
 #, 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:1632
+#: boot-installer.xml:1712
 #, 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:1644
+#: boot-installer.xml:1724
 #, no-c-format
 msgid ""
       "Having worked out the device path, use a command like this to boot the installer: <informalexample><screen>\n"
@@ -1055,25 +1109,25 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1658
+#: boot-installer.xml:1738
 #, 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:1664
+#: boot-installer.xml:1744
 #, 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:1698
+#: boot-installer.xml:1778
 #, no-c-format
 msgid "Currently, PReP and New World PowerMac systems support netbooting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1702
+#: boot-installer.xml:1782
 #, 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"
@@ -1086,751 +1140,751 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1730
+#: boot-installer.xml:1810
 #, 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:1742
+#: boot-installer.xml:1822
 #, 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:1748
+#: boot-installer.xml:1828
 #, 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:1755
+#: boot-installer.xml:1835
 #, 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:1766
+#: boot-installer.xml:1846
 #, no-c-format
 msgid "PowerPC Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1767
+#: boot-installer.xml:1847
 #, 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:1808
+#: boot-installer.xml:1888
 #, 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:1863
+#: boot-installer.xml:1943
 #, 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:1872
+#: boot-installer.xml:1952
 #, no-c-format
 msgid "IDPROM Messages"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1873
+#: boot-installer.xml:1953
 #, 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:1892
+#: boot-installer.xml:1972
 #, no-c-format
 msgid "Accessibility"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1893
+#: boot-installer.xml:1973
 #, 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:1913
+#: boot-installer.xml:1993
 #, no-c-format
 msgid "Installer front-end"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1914
+#: boot-installer.xml:1994
 #, 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:1926
+#: boot-installer.xml:2006
 #, no-c-format
 msgid "USB Braille Displays"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1927
+#: boot-installer.xml:2007
 #, 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:1942
+#: boot-installer.xml:2022
 #, no-c-format
 msgid "Serial Braille Displays"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1943
+#: boot-installer.xml:2023
 #, 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:1966 boot-installer.xml:2973
+#: boot-installer.xml:2046 boot-installer.xml:3053
 #, no-c-format
 msgid "Software Speech Synthesis"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1967
+#: boot-installer.xml:2047
 #, 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:1976
+#: boot-installer.xml:2056
 #, 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:1982
+#: boot-installer.xml:2062
 #, 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:2001
+#: boot-installer.xml:2081
 #, no-c-format
 msgid "Hardware Speech Synthesis"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2002
+#: boot-installer.xml:2082
 #, 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:2009
+#: boot-installer.xml:2089
 #, 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:2024
+#: boot-installer.xml:2104
 #, no-c-format
 msgid "Board Devices"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2025
+#: boot-installer.xml:2105
 #, 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:2033
+#: boot-installer.xml:2113
 #, 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:2041
+#: boot-installer.xml:2121
 #, no-c-format
 msgid "High-Contrast Theme"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2042
+#: boot-installer.xml:2122
 #, 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:2051
+#: boot-installer.xml:2131
 #, no-c-format
 msgid "Preseeding"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2052
+#: boot-installer.xml:2132
 #, 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:2060
+#: boot-installer.xml:2140
 #, no-c-format
 msgid "Accessibility of the installed system"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2061
+#: boot-installer.xml:2141
 #, 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:2076
+#: boot-installer.xml:2156
 #, 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:2083
+#: boot-installer.xml:2163
 #, 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:2090
+#: boot-installer.xml:2170
 #, 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:2102
+#: boot-installer.xml:2182
 #, no-c-format
 msgid "Boot console"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2104
+#: boot-installer.xml:2184
 #, 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:2116
+#: boot-installer.xml:2196
 #, 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."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2122
+#: boot-installer.xml:2202
 #, 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:2138
+#: boot-installer.xml:2218
 #, 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:2150
+#: boot-installer.xml:2230
 #, no-c-format
 msgid "&debian; Installer Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2151
+#: boot-installer.xml:2231
 #, 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:2164
+#: boot-installer.xml:2244
 #, 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:2176
+#: boot-installer.xml:2256
 #, no-c-format
 msgid "debconf/priority (priority)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2177
+#: boot-installer.xml:2257
 #, no-c-format
 msgid "This parameter sets the lowest priority of messages to be displayed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2181
+#: boot-installer.xml:2261
 #, 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:2188
+#: boot-installer.xml:2268
 #, 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:2202
+#: boot-installer.xml:2282
 #, no-c-format
 msgid "DEBIAN_FRONTEND"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2203
+#: boot-installer.xml:2283
 #, 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:2234
+#: boot-installer.xml:2314
 #, no-c-format
 msgid "BOOT_DEBUG"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2235
+#: boot-installer.xml:2315
 #, 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:2244
+#: boot-installer.xml:2324
 #, no-c-format
 msgid "BOOT_DEBUG=0"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2245
+#: boot-installer.xml:2325
 #, no-c-format
 msgid "This is the default."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2249
+#: boot-installer.xml:2329
 #, no-c-format
 msgid "BOOT_DEBUG=1"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2250
+#: boot-installer.xml:2330
 #, no-c-format
 msgid "More verbose than usual."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2254
+#: boot-installer.xml:2334
 #, no-c-format
 msgid "BOOT_DEBUG=2"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2255
+#: boot-installer.xml:2335
 #, no-c-format
 msgid "Lots of debugging information."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2259
+#: boot-installer.xml:2339
 #, no-c-format
 msgid "BOOT_DEBUG=3"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2260
+#: boot-installer.xml:2340
 #, 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:2274
+#: boot-installer.xml:2354
 #, no-c-format
 msgid "INSTALL_MEDIA_DEV"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2275
+#: boot-installer.xml:2355
 #, 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:2281
+#: boot-installer.xml:2361
 #, 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:2292
+#: boot-installer.xml:2372
 #, no-c-format
 msgid "log_host"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2293
+#: boot-installer.xml:2373
 #, no-c-format
 msgid "log_port"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2294
+#: boot-installer.xml:2374
 #, 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:2305
+#: boot-installer.xml:2385
 #, no-c-format
 msgid "lowmem"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2306
+#: boot-installer.xml:2386
 #, 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:2316
+#: boot-installer.xml:2396
 #, no-c-format
 msgid "noshell"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2317
+#: boot-installer.xml:2397
 #, 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:2326
+#: boot-installer.xml:2406
 #, no-c-format
 msgid "debian-installer/framebuffer (fb)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2327
+#: boot-installer.xml:2407
 #, 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:2336
+#: boot-installer.xml:2416
 #, no-c-format
 msgid "Such problems have been reported on hppa."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2340
+#: boot-installer.xml:2420
 #, 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:2354
+#: boot-installer.xml:2434
 #, no-c-format
 msgid "debian-installer/theme (theme)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2355
+#: boot-installer.xml:2435
 #, 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:2367 boot-installer.xml:2600
+#: boot-installer.xml:2447 boot-installer.xml:2680
 #, no-c-format
 msgid "netcfg/disable_autoconfig"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2368
+#: boot-installer.xml:2448
 #, 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:2375
+#: boot-installer.xml:2455
 #, 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:2386
+#: boot-installer.xml:2466
 #, no-c-format
 msgid "hw-detect/start_pcmcia"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2387
+#: boot-installer.xml:2467
 #, 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:2397
+#: boot-installer.xml:2477
 #, no-c-format
 msgid "disk-detect/dmraid/enable (dmraid)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2398
+#: boot-installer.xml:2478
 #, 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:2409
+#: boot-installer.xml:2489
 #, no-c-format
 msgid "preseed/url (url)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2410
+#: boot-installer.xml:2490
 #, 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:2419
+#: boot-installer.xml:2499
 #, no-c-format
 msgid "preseed/file (file)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2420
+#: boot-installer.xml:2500
 #, 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:2429
+#: boot-installer.xml:2509
 #, no-c-format
 msgid "preseed/interactive"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2430
+#: boot-installer.xml:2510
 #, 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:2442
+#: boot-installer.xml:2522
 #, no-c-format
 msgid "auto-install/enable (auto)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2443
+#: boot-installer.xml:2523
 #, 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:2454
+#: boot-installer.xml:2534
 #, no-c-format
 msgid "finish-install/keep-consoles"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2455
+#: boot-installer.xml:2535
 #, 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:2466
+#: boot-installer.xml:2546
 #, no-c-format
 msgid "cdrom-detect/eject"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2467
+#: boot-installer.xml:2547
 #, 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:2476
+#: boot-installer.xml:2556
 #, 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:2487
+#: boot-installer.xml:2567
 #, no-c-format
 msgid "base-installer/install-recommends (recommends)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2488
+#: boot-installer.xml:2568
 #, 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:2495
+#: boot-installer.xml:2575
 #, 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:2507
+#: boot-installer.xml:2587
 #, no-c-format
 msgid "debian-installer/allow_unauthenticated"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2508
+#: boot-installer.xml:2588
 #, 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:2519
+#: boot-installer.xml:2599
 #, no-c-format
 msgid "ramdisk_size"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2520
+#: boot-installer.xml:2600
 #, 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:2530
+#: boot-installer.xml:2610
 #, no-c-format
 msgid "rescue/enable"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2531
+#: boot-installer.xml:2611
 #, 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:2544
+#: boot-installer.xml:2624
 #, no-c-format
 msgid "Using boot parameters to answer questions"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2545
+#: boot-installer.xml:2625
 #, 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:2557
+#: boot-installer.xml:2637
 #, no-c-format
 msgid "debian-installer/language (language)"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2558
+#: boot-installer.xml:2638
 #, no-c-format
 msgid "debian-installer/country (country)"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2559
+#: boot-installer.xml:2639
 #, no-c-format
 msgid "debian-installer/locale (locale)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2560
+#: boot-installer.xml:2640
 #, 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:2565
+#: boot-installer.xml:2645
 #, 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:2574
+#: boot-installer.xml:2654
 #, 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:2586
+#: boot-installer.xml:2666
 #, no-c-format
 msgid "anna/choose_modules (modules)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2587
+#: boot-installer.xml:2667
 #, 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:2601
+#: boot-installer.xml:2681
 #, 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:2610
+#: boot-installer.xml:2690
 #, no-c-format
 msgid "mirror/protocol (protocol)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2611
+#: boot-installer.xml:2691
 #, 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:2624
+#: boot-installer.xml:2704
 #, no-c-format
 msgid "tasksel:tasksel/first (tasks)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2625
+#: boot-installer.xml:2705
 #, 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:2639
+#: boot-installer.xml:2719
 #, no-c-format
 msgid "Passing parameters to kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2640
+#: boot-installer.xml:2720
 #, 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:2653
+#: boot-installer.xml:2733
 #, 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:2660
+#: boot-installer.xml:2740
 #, no-c-format
 msgid ""
       "The syntax to use to set parameters for modules is: <informalexample><screen>\n"
@@ -1839,127 +1893,127 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:2670
+#: boot-installer.xml:2750
 #, no-c-format
 msgid "3c509.xcvr=3 3c509.irq=10"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2676
+#: boot-installer.xml:2756
 #, no-c-format
 msgid "Blacklisting kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2677
+#: boot-installer.xml:2757
 #, 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:2686
+#: boot-installer.xml:2766
 #, 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:2694
+#: boot-installer.xml:2774
 #, 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:2710
+#: boot-installer.xml:2790
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2715
+#: boot-installer.xml:2795
 #, no-c-format
 msgid "CD-ROM Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2716
+#: boot-installer.xml:2796
 #, 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:2723
+#: boot-installer.xml:2803
 #, 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:2729
+#: boot-installer.xml:2809
 #, no-c-format
 msgid "There are two very simple things that you should try first."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2734
+#: boot-installer.xml:2814
 #, 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:2740
+#: boot-installer.xml:2820
 #, 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:2750
+#: boot-installer.xml:2830
 #, 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:2756
+#: boot-installer.xml:2836
 #, 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:2764
+#: boot-installer.xml:2844
 #, no-c-format
 msgid "Common issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2767
+#: boot-installer.xml:2847
 #, 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:2784
+#: boot-installer.xml:2864
 #, 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:2795
+#: boot-installer.xml:2875
 #, no-c-format
 msgid "How to investigate and maybe solve issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2796
+#: boot-installer.xml:2876
 #, no-c-format
 msgid "If the CD-ROM fails to boot, try the suggestions listed below."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2801
+#: boot-installer.xml:2881
 #, 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:2808
+#: boot-installer.xml:2888
 #, 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"
@@ -1969,7 +2023,7 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:2821
+#: boot-installer.xml:2901
 #, no-c-format
 msgid ""
       "$ dd if=/dev/cdrom | \\\n"
@@ -1982,19 +2036,19 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2826
+#: boot-installer.xml:2906
 #, 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:2838
+#: boot-installer.xml:2918
 #, 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:2845
+#: boot-installer.xml:2925
 #, 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"
@@ -2007,13 +2061,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2859
+#: boot-installer.xml:2939
 #, 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:2867
+#: boot-installer.xml:2947
 #, 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"
@@ -2022,7 +2076,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2877
+#: boot-installer.xml:2957
 #, no-c-format
 msgid ""
       "Check if DMA is currently enabled: <informalexample><screen>\n"
@@ -2035,151 +2089,151 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2892
+#: boot-installer.xml:2972
 #, 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:2907
+#: boot-installer.xml:2987
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2909
+#: boot-installer.xml:2989
 #, 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:2914
+#: boot-installer.xml:2994
 #, 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:2923
+#: boot-installer.xml:3003
 #, 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:2932
+#: boot-installer.xml:3012
 #, 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:2938
+#: boot-installer.xml:3018
 #, 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:2944
+#: boot-installer.xml:3024
 #, 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:2953
+#: boot-installer.xml:3033
 #, no-c-format
 msgid "Boot Configuration"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2955
+#: boot-installer.xml:3035
 #, 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:2964
+#: boot-installer.xml:3044
 #, 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:2975
+#: boot-installer.xml:3055
 #, 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:2986
+#: boot-installer.xml:3066
 #, no-c-format
 msgid "dmesg"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2988
+#: boot-installer.xml:3068
 #, no-c-format
 msgid "lspci"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2990
+#: boot-installer.xml:3070
 #, no-c-format
 msgid "lsmod"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2992
+#: boot-installer.xml:3072
 #, no-c-format
 msgid "amixer"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3000 boot-installer.xml:3111
+#: boot-installer.xml:3080 boot-installer.xml:3191
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3001
+#: boot-installer.xml:3081
 #, 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:3052
+#: boot-installer.xml:3132
 #, 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:3066
+#: boot-installer.xml:3146
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3067
+#: boot-installer.xml:3147
 #, 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:3077
+#: boot-installer.xml:3157
 #, 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:3112
+#: boot-installer.xml:3192
 #, no-c-format
 msgid "There are some common installation problems that are worth mentioning."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3118
+#: boot-installer.xml:3198
 #, no-c-format
 msgid "Misdirected video output"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3119
+#: boot-installer.xml:3199
 #, 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"
@@ -2189,85 +2243,85 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3133
+#: boot-installer.xml:3213
 #, 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:3144
+#: boot-installer.xml:3224
 #, no-c-format
 msgid "Failure to Boot or Install from CD-ROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3145
+#: boot-installer.xml:3225
 #, 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:3151
+#: boot-installer.xml:3231
 #, no-c-format
 msgid "We recommend to install such systems by netbooting the installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3160
+#: boot-installer.xml:3240
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3162
+#: boot-installer.xml:3242
 #, 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:3187
+#: boot-installer.xml:3267
 #, no-c-format
 msgid "Reporting Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3188
+#: boot-installer.xml:3268
 #, 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:3199
+#: boot-installer.xml:3279
 #, 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:3210
+#: boot-installer.xml:3290
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3211
+#: boot-installer.xml:3291
 #, 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:3218
+#: boot-installer.xml:3298
 #, 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:3224
+#: boot-installer.xml:3304
 #, 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:3234
+#: boot-installer.xml:3314
 #, 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/boot-new.pot b/po/pot/boot-new.pot
index ed8d2658a..4dd59fa11 100644
--- a/po/pot/boot-new.pot
+++ b/po/pot/boot-new.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-01-29 10:50+0000\n"
+"POT-Creation-Date: 2014-08-26 20:40+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"
@@ -125,17 +125,11 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:147
 #, no-c-format
-msgid "If you created encrypted volumes during the installation and assigned them mount points, you will be asked to enter the passphrase for each of these volumes during the boot. The actual procedure differs slightly between dm-crypt and loop-AES."
-msgstr ""
-
-#. Tag: title
-#: boot-new.xml:157
-#, no-c-format
-msgid "dm-crypt"
+msgid "If you created encrypted volumes during the installation and assigned them mount points, you will be asked to enter the passphrase for each of these volumes during the boot."
 msgstr ""
 
 #. Tag: para
-#: boot-new.xml:159
+#: boot-new.xml:155
 #, no-c-format
 msgid ""
       "For partitions encrypted using dm-crypt you will be shown the following prompt during the boot: <informalexample><screen>\n"
@@ -145,13 +139,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-new.xml:182
+#: boot-new.xml:178
 #, no-c-format
 msgid "The prompt may look somewhat different when an encrypted root file system is mounted. This depends on which initramfs generator was used to generate the initrd used to boot the system. The example below is for an initrd generated using <classname>initramfs-tools</classname>:"
 msgstr ""
 
 #. Tag: screen
-#: boot-new.xml:189
+#: boot-new.xml:185
 #, no-c-format
 msgid ""
       "Begin: Mounting <emphasis>root file system</emphasis>... ...\n"
@@ -160,119 +154,94 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-new.xml:191 boot-new.xml:216
+#: boot-new.xml:187
 #, no-c-format
 msgid "No characters (even asterisks) will be shown while entering the passphrase. If you enter the wrong passphrase, you have two more tries to correct it. After the third try the boot process will skip this volume and continue to mount the next filesystem. Please see <xref linkend=\"crypto-troubleshooting\"/> for further information."
 msgstr ""
 
 #. Tag: para
-#: boot-new.xml:199 boot-new.xml:224
+#: boot-new.xml:195
 #, no-c-format
 msgid "After entering all passphrases the boot should continue as usual."
 msgstr ""
 
 #. Tag: title
-#: boot-new.xml:207
-#, no-c-format
-msgid "loop-AES"
-msgstr ""
-
-#. Tag: para
-#: boot-new.xml:209
-#, no-c-format
-msgid "For partitions encrypted using loop-AES you will be shown the following prompt during the boot:"
-msgstr ""
-
-#. Tag: screen
-#: boot-new.xml:214
-#, no-c-format
-msgid ""
-      "Checking loop-encrypted file systems.\n"
-      "Setting up /dev/loop<replaceable>X</replaceable> (/<replaceable>mountpoint</replaceable>)\n"
-      "Password:"
-msgstr ""
-
-#. Tag: title
-#: boot-new.xml:232
+#: boot-new.xml:202
 #, no-c-format
 msgid "Troubleshooting"
 msgstr ""
 
 #. Tag: para
-#: boot-new.xml:234
+#: boot-new.xml:204
 #, no-c-format
 msgid "If some of the encrypted volumes could not be mounted because a wrong passphrase was entered, you will have to mount them manually after the boot. There are several cases."
 msgstr ""
 
 #. Tag: para
-#: boot-new.xml:243
+#: boot-new.xml:213
 #, no-c-format
 msgid "The first case concerns the root partition. When it is not mounted correctly, the boot process will halt and you will have to reboot the computer to try again."
 msgstr ""
 
 #. Tag: para
-#: boot-new.xml:250
+#: boot-new.xml:220
 #, no-c-format
-msgid ""
-      "The easiest case is for encrypted volumes holding data like <filename>/home</filename> or <filename>/srv</filename>. You can simply mount them manually after the boot. For loop-AES this is a one-step operation: <informalexample><screen>\n"
-      "<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></userinput>\n"
-      "<prompt>Password:</prompt>\n"
-      "</screen></informalexample> where <replaceable>/mount_point</replaceable> should be replaced by the particular directory (e.g. <filename>/home</filename>). The only difference from an ordinary mount is that you will be asked to enter the passphrase for this volume."
+msgid "The easiest case is for encrypted volumes holding data like <filename>/home</filename> or <filename>/srv</filename>. You can simply mount them manually after the boot."
 msgstr ""
 
 #. Tag: para
-#: boot-new.xml:264
+#: boot-new.xml:226
 #, no-c-format
 msgid ""
-      "For dm-crypt this is a bit trickier. First you need to register the volumes with <application>device mapper</application> by running: <informalexample><screen>\n"
+      "However for dm-crypt this is a bit tricky. First you need to register the volumes with <application>device mapper</application> by running: <informalexample><screen>\n"
       "<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>\n"
       "</screen></informalexample> This will scan all volumes mentioned in <filename>/etc/crypttab</filename> and will create appropriate devices under the <filename>/dev</filename> directory after entering the correct passphrases. (Already registered volumes will be skipped, so you can repeat this command several times without worrying.) After successful registration you can simply mount the volumes the usual way:"
 msgstr ""
 
 #. Tag: screen
-#: boot-new.xml:279
+#: boot-new.xml:241
 #, no-c-format
 msgid "<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></userinput>"
 msgstr ""
 
 #. Tag: para
-#: boot-new.xml:282
+#: boot-new.xml:244
 #, no-c-format
 msgid "If any volume holding noncritical system files could not be mounted (<filename>/usr</filename> or <filename>/var</filename>), the system should still boot and you should be able to mount the volumes manually like in the previous case. However, you will also need to (re)start any services usually running in your default runlevel because it is very likely that they were not started. The easiest way is to just reboot the computer."
 msgstr ""
 
 #. Tag: title
-#: boot-new.xml:300
+#: boot-new.xml:262
 #, no-c-format
 msgid "Log In"
 msgstr ""
 
 #. Tag: para
-#: boot-new.xml:302
+#: boot-new.xml:264
 #, no-c-format
 msgid "Once your system boots, you'll be presented with the login prompt. Log in using the personal login and password you selected during the installation process. Your system is now ready for use."
 msgstr ""
 
 #. Tag: para
-#: boot-new.xml:308
+#: boot-new.xml:270
 #, no-c-format
 msgid "If you are a new user, you may want to explore the documentation which is already installed on your system as you start to use it. There are currently several documentation systems, work is proceeding on integrating the different types of documentation. Here are a few starting points."
 msgstr ""
 
 #. Tag: para
-#: boot-new.xml:316
+#: boot-new.xml:278
 #, no-c-format
 msgid "Documentation accompanying programs you have installed can be found in <filename>/usr/share/doc/</filename>, under a subdirectory named after the program (or, more precise, the &debian; package that contains the program). However, more extensive documentation is often packaged separately in special documentation packages that are mostly not installed by default. For example, documentation about the package management tool <command>apt</command> can be found in the packages <classname>apt-doc</classname> or <classname>apt-howto</classname>."
 msgstr ""
 
 #. Tag: para
-#: boot-new.xml:327
+#: boot-new.xml:289
 #, no-c-format
 msgid "In addition, there are some special folders within the <filename>/usr/share/doc/</filename> hierarchy. Linux HOWTOs are installed in <emphasis>.gz</emphasis> (compressed) format, in <filename>/usr/share/doc/HOWTO/en-txt/</filename>. After installing <classname>dhelp</classname>, you will find a browsable index of documentation in <filename>/usr/share/doc/HTML/index.html</filename>."
 msgstr ""
 
 #. Tag: para
-#: boot-new.xml:336
+#: boot-new.xml:298
 #, no-c-format
 msgid ""
       "One easy way to view these documents using a text based browser is to enter the following commands: <informalexample><screen>\n"
@@ -282,13 +251,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-new.xml:346
+#: boot-new.xml:308
 #, no-c-format
 msgid "If you have a graphical desktop environment installed, you can also use its web browser. Start the web browser from the application menu and enter <userinput>/usr/share/doc/</userinput> in the address bar."
 msgstr ""
 
 #. Tag: para
-#: boot-new.xml:352
+#: boot-new.xml:314
 #, no-c-format
 msgid "You can also type <userinput>info <replaceable>command</replaceable></userinput> or <userinput>man <replaceable>command</replaceable></userinput> to see documentation on most commands available at the command prompt. Typing <userinput>help</userinput> will display help on shell commands. And typing a command followed by <userinput>--help</userinput> will usually display a short summary of the command's usage. If a command's results scroll past the top of the screen, type <userinput>|&nbsp;more</userinput> after the command to cause the results to pause before scrolling past the top of the screen. To see a list of all commands available which begin with a certain letter, type the letter and then two tabs."
 msgstr ""
diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot
index 76a1dedfd..e39f72fc9 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-08-06 21:29+0000\n"
+"POT-Creation-Date: 2014-08-26 20:40+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"
@@ -1943,6 +1943,6 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:2134
 #, no-c-format
-msgid "Installation on systems with less memory<footnote condition=\"gtk\"> <para> Installation images that support the graphical installer require more memory than images that support only the textual installer and should not be used on systems with less than &minimum-memory; of memory. If there is a choice between booting the regular and the graphical installer, the former should be selected. </para> </footnote> or disk space available may be possible but is only advised for experienced users."
+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 585d16d19..f88592689 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-08-05 21:38+0000\n"
+"POT-Creation-Date: 2014-08-26 20:40+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"
@@ -501,7 +501,7 @@ msgstr ""
 #. Tag: para
 #: install-methods.xml:673
 #, 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 a full CD ISO image to it."
+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
@@ -551,7 +551,7 @@ msgstr ""
 #. Tag: para
 #: install-methods.xml:746
 #, no-c-format
-msgid "Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /mnt</userinput>) and copy the following installer image files to the stick: <itemizedlist> <listitem><para> <filename>vmlinuz</filename> or <filename>linux</filename> (kernel binary) </para></listitem> <listitem><para> <filename>initrd.gz</filename> (initial ramdisk image) </para></listitem> </itemizedlist> You can choose between either the regular version or the graphical version of the installer. The latter can be found in the <filename>gtk</filename> subdirectory. If you want to rename the files, please note that <classname>syslinux</classname> can only process DOS (8.3) file names."
+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
diff --git a/po/pot/random-bits.pot b/po/pot/random-bits.pot
index 2897cef15..050e3c147 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-08-05 21:38+0000\n"
+"POT-Creation-Date: 2014-08-26 20:40+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"
@@ -1215,31 +1215,44 @@ msgstr ""
 #. Tag: title
 #: random-bits.xml:826
 #, no-c-format
-msgid "Remote access: Installing SSH and setting a password"
+msgid "Remote access: Installing SSH and setting up access"
 msgstr ""
 
 #. Tag: para
 #: random-bits.xml:827
 #, 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 a password for root:"
+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"
+      "# aptitude install ssh\n"
+      "</screen></informalexample> Root login with password is disabled by default, so setting up access can be done by setting a password and re-enable root login with password: <informalexample><screen>\n"
+      "# passwd\n"
+      "# editor /etc/ssh/sshd_config\n"
+      "</screen></informalexample> This is the option to be enabled: <informalexample><screen>\n"
+      "PermitRootLogin yes\n"
+      "</screen></informalexample> Access can also be set up by adding an ssh key to the root account: <informalexample><screen>\n"
+      "# mkdir /root/.ssh\n"
+      "# cat &lt;&lt; EOF &gt; /root/.ssh/authorized_keys\n"
+      "ssh-rsa ....\n"
+      "EOF\n"
+      "</screen></informalexample> Lastly, access can be set up by adding a non-root user and setting a password:"
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:833
+#: random-bits.xml:851
 #, no-c-format
 msgid ""
-      "# aptitude install ssh\n"
-      "# passwd"
+      "# adduser joe\n"
+      "# passwd joe"
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:838
+#: random-bits.xml:856
 #, no-c-format
 msgid "Finishing touches"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:839
+#: random-bits.xml:857
 #, 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"
@@ -1248,91 +1261,91 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:850
+#: random-bits.xml:868
 #, 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:856
+#: random-bits.xml:874
 #, no-c-format
 msgid "# aptitude clean"
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:867
+#: random-bits.xml:885
 #, no-c-format
 msgid "Installing &debian-gnu; over Parallel Line IP (PLIP)"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:869
+#: random-bits.xml:887
 #, 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:877
+#: random-bits.xml:895
 #, 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:885
+#: random-bits.xml:903
 #, 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:890
+#: random-bits.xml:908
 #, 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:900
+#: random-bits.xml:918
 #, no-c-format
 msgid "Requirements"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:903
+#: random-bits.xml:921
 #, no-c-format
 msgid "A target computer, called <emphasis>target</emphasis>, where &debian; will be installed."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:909
+#: random-bits.xml:927
 #, no-c-format
 msgid "System installation media; see <xref linkend=\"installation-media\"/>."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:914
+#: random-bits.xml:932
 #, 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:920
+#: random-bits.xml:938
 #, 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:932
+#: random-bits.xml:950
 #, no-c-format
 msgid "Setting up source"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:933
+#: random-bits.xml:951
 #, 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:938
+#: random-bits.xml:956
 #, no-c-format
 msgid ""
       "#!/bin/sh\n"
@@ -1353,13 +1366,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:944
+#: random-bits.xml:962
 #, no-c-format
 msgid "Installing target"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:945
+#: random-bits.xml:963
 #, 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"
@@ -1368,218 +1381,134 @@ msgid ""
 msgstr ""
 
 #. Tag: guimenuitem
-#: random-bits.xml:964
+#: random-bits.xml:982
 #, no-c-format
 msgid "Load installer components from CD"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:966
+#: random-bits.xml:984
 #, 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:974
+#: random-bits.xml:992
 #, no-c-format
 msgid "Detect network hardware"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:979
+#: random-bits.xml:997
 #, 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:988
+#: random-bits.xml:1006
 #, 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:1000
+#: random-bits.xml:1018
 #, no-c-format
 msgid "Configure the network"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1003
+#: random-bits.xml:1021
 #, no-c-format
 msgid "Auto-configure network with DHCP: No"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1008
+#: random-bits.xml:1026
 #, no-c-format
 msgid "IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1013
+#: random-bits.xml:1031
 #, no-c-format
 msgid "Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></userinput>"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1019
+#: random-bits.xml:1037
 #, 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:1038
+#: random-bits.xml:1056
 #, no-c-format
 msgid "Installing &debian-gnu; using PPP over Ethernet (PPPoE)"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:1040
+#: random-bits.xml:1058
 #, 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:1048
+#: random-bits.xml:1066
 #, 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:1053
+#: random-bits.xml:1071
 #, 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:1060
+#: random-bits.xml:1078
 #, 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:1068
+#: random-bits.xml:1086
 #, 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:1083
+#: random-bits.xml:1101
 #, 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:1102
+#: random-bits.xml:1120
 #, 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:1108
+#: random-bits.xml:1126
 #, 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:1114
+#: random-bits.xml:1132
 #, 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:1123
+#: random-bits.xml:1141
 #, 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:1129
+#: random-bits.xml:1147
 #, no-c-format
 msgid "At this point the installer will use the provided information to establish the PPPoE connection. If the correct information was provided, the PPPoE connection should be configured and the installer should be able to use it to connect to the Internet and retrieve packages over it (if needed). If the login information is not correct or some error appears, the installer will stop, but the configuration can be attempted again by selecting the menu entry <guimenuitem>Configure and start a PPPoE connection</guimenuitem>."
 msgstr ""
 
-#. Tag: title
-#: random-bits.xml:1149
-#, no-c-format
-msgid "The Graphical Installer"
-msgstr ""
-
-#. Tag: para
-#: random-bits.xml:1150
-#, no-c-format
-msgid "The graphical version of the installer is only available for a limited number of architectures, including &arch-title;. The functionality of the graphical installer is essentially the same as that of the regular installer as it basically uses the same programs, but with a different frontend."
-msgstr ""
-
-#. Tag: para
-#: random-bits.xml:1158
-#, no-c-format
-msgid "Although the functionality is identical, the graphical installer still has a few significant advantages. The main advantage is that it supports more languages, namely those that use a character set that cannot be displayed with the regular <quote>newt</quote> frontend. It also has a few usability advantages such as the option to use a mouse, and in some cases several questions can be displayed on a single screen."
-msgstr ""
-
-#. Tag: para
-#: random-bits.xml:1167
-#, no-c-format
-msgid "The graphical installer is available with all CD images and with the hd-media installation method. To boot the graphical installer simply select the relevant option from the boot menu. Expert and rescue mode for the graphical installer can be selected from the <quote>Advanced options</quote> menu. The previously used boot methods <userinput>installgui</userinput>, <userinput>expertgui</userinput> and <userinput>rescuegui</userinput> can still be used from the boot prompt which is shown after selecting the <quote>Help</quote> option in the boot menu."
-msgstr ""
-
-#. Tag: para
-#: random-bits.xml:1178
-#, no-c-format
-msgid "There is also a graphical installer image that can be netbooted. And there is a special <quote>mini</quote> ISO image<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a &debian; mirror as described in <xref linkend=\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. </para> </footnote>, which is mainly useful for testing."
-msgstr ""
-
-#. Tag: para
-#: random-bits.xml:1191
-#, no-c-format
-msgid "For &arch-title;, currently only an experimental <quote>mini</quote> ISO image is available<footnote id=\"gtk-miniiso\"> <para> The mini ISO image can be downloaded from a &debian; mirror as described in <xref linkend=\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. </para> </footnote>. It should work on almost all PowerPC systems that have an ATI graphical card, but is unlikely to work on other systems."
-msgstr ""
-
-#. Tag: para
-#: random-bits.xml:1205
-#, no-c-format
-msgid "Just as with the regular installer it is possible to add boot parameters when starting the graphical installer."
-msgstr ""
-
-#. Tag: para
-#: random-bits.xml:1211
-#, no-c-format
-msgid "The graphical installer requires significantly more memory to run than the regular installer: &minimum-memory-gtk;. If insufficient memory is available, it will automatically fall back to the regular <quote>newt</quote> frontend."
-msgstr ""
-
-#. Tag: para
-#: random-bits.xml:1218
-#, no-c-format
-msgid "If the amount of memory in your system is below &minimum-memory;, the graphical installer may fail to boot at all while booting the regular installer would still work. Using the regular installer is recommended for systems with little available memory."
-msgstr ""
-
-#. Tag: title
-#: random-bits.xml:1228
-#, no-c-format
-msgid "Using the graphical installer"
-msgstr ""
-
-#. Tag: para
-#: random-bits.xml:1229
-#, no-c-format
-msgid "As already mentioned, the graphical installer basically works the same as the regular installer and thus the rest of this manual can be used to guide you through the installation process."
-msgstr ""
-
-#. Tag: para
-#: random-bits.xml:1235
-#, no-c-format
-msgid "If you prefer using the keyboard over the mouse, there are two things you need to know. To expand a collapsed list (used for example for the selection of countries within continents), you can use the <keycap>+</keycap> and <keycap>-</keycap> keys. For questions where more than one item can be selected (e.g. task selection), you first need to tab to the &BTN-CONT; button after making your selections; hitting enter will toggle a selection, not activate &BTN-CONT;."
-msgstr ""
-
-#. Tag: para
-#: random-bits.xml:1245
-#, no-c-format
-msgid "If a dialog offers additional help information, a <guibutton>Help</guibutton> button will be displayed. The help information can be accessed either by activating the button or by pressing the <keycap>F1</keycap> key."
-msgstr ""
-
-#. Tag: para
-#: random-bits.xml:1251
-#, no-c-format
-msgid "To switch to another console, you will also need to use the <keycap>Ctrl</keycap> key, just as with the X Window System. For example, to switch to VT2 (the first debug shell) you would use: <keycombo> <keycap>Ctrl</keycap> <keycap>Left Alt</keycap> <keycap>F2</keycap> </keycombo>. The graphical installer itself runs on VT5, so you can use <keycombo> <keycap>Left Alt</keycap> <keycap>F5</keycap> </keycombo> to switch back."
-msgstr ""
-
diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot
index a0ef262dc..19c0ad97a 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-08-03 08:11+0000\n"
+"POT-Creation-Date: 2014-08-26 20:40+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"
@@ -65,779 +65,815 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:60
 #, no-c-format
-msgid "For this architecture the &d-i; supports two different user interfaces: a character-based one and a graphical one. The character-based interface is used by default unless you selected the <quote>Graphical install</quote> option in the initial boot menu. For more information about the graphical installer, please refer to <xref linkend=\"graphical\"/>."
+msgid "For this architecture the &d-i; supports two different user interfaces: a graphical one and a character-based one. The graphical interface is used by default unless you select an <quote>Install</quote> option in the boot menu. For more information about the graphical installer, please refer to <xref linkend=\"graphical\"/>."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:68
 #, no-c-format
+msgid "For this architecture the &d-i; supports two different user interfaces: a character-based one and a graphical one. The character-based interface is used by default unless you select the <quote>Graphical install</quote> option on purpose. For more information about the graphical installer, please refer to <xref linkend=\"graphical\"/>."
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:76
+#, no-c-format
 msgid "For this architecture the installer uses a character-based user interface. A graphical user interface is currently not available."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:73
+#: using-d-i.xml:81
 #, no-c-format
 msgid "In the character-based environment the use of a mouse is not supported. Here are the keys you can use to navigate within the various dialogs. The <keycap>Tab</keycap> or <keycap>right</keycap> arrow keys move <quote>forward</quote>, and the <keycombo> <keycap>Shift</keycap> <keycap>Tab</keycap> </keycombo> or <keycap>left</keycap> arrow keys move <quote>backward</quote> between displayed buttons and selections. The <keycap>up</keycap> and <keycap>down</keycap> arrow select different items within a scrollable list, and also scroll the list itself. In addition, in long lists, you can type a letter to cause the list to scroll directly to the section with items starting with the letter you typed and use <keycap>Pg-Up</keycap> and <keycap>Pg-Down</keycap> to scroll the list in sections. The <keycap>space bar</keycap> selects an item such as a checkbox. Use &enterkey; to activate choices."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:90
+#: using-d-i.xml:98
 #, no-c-format
 msgid "Some dialogs may offer additional help information. If help is available this will be indicated on the bottom line of the screen by displaying that help information can be accessed by pressing the <keycap>F1</keycap> key."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:96
+#: using-d-i.xml:104
 #, no-c-format
 msgid "S/390 does not support virtual consoles. You may open a second and third ssh session to view the logs described below."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:101
+#: using-d-i.xml:109
 #, no-c-format
 msgid "Error messages and logs are redirected to the fourth console. You can access this console by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo> (hold the left <keycap>Alt</keycap> key while pressing the <keycap>F4</keycap> function key); get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:111
+#: using-d-i.xml:119
 #, no-c-format
 msgid "These messages can also be found in <filename>/var/log/syslog</filename>. After installation, this log is copied to <filename>/var/log/installer/syslog</filename> on your new system. Other 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
-#: using-d-i.xml:125
+#: using-d-i.xml:132
+#, no-c-format
+msgid "Using the graphical installer"
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:133
+#, no-c-format
+msgid "The graphical installer basically works the same as the text-based installer and thus the rest of this manual can be used to guide you through the installation process."
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:139
+#, no-c-format
+msgid "If you prefer using the keyboard over the mouse, there are two things you need to know. To expand a collapsed list (used for example for the selection of countries within continents), you can use the <keycap>+</keycap> and <keycap>-</keycap> keys. For questions where more than one item can be selected (e.g. task selection), you first need to tab to the &BTN-CONT; button after making your selections; hitting enter will toggle a selection, not activate &BTN-CONT;."
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:149
+#, no-c-format
+msgid "If a dialog offers additional help information, a <guibutton>Help</guibutton> button will be displayed. The help information can be accessed either by activating the button or by pressing the <keycap>F1</keycap> key."
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:155
+#, no-c-format
+msgid "To switch to another console, you will also need to use the <keycap>Ctrl</keycap> key, just as with the X Window System. For example, to switch to VT2 (the first debug shell) you would use: <keycombo> <keycap>Ctrl</keycap> <keycap>Left Alt</keycap> <keycap>F2</keycap> </keycombo>. The graphical installer itself runs on VT5, so you can use <keycombo> <keycap>Left Alt</keycap> <keycap>F5</keycap> </keycombo> to switch back."
+msgstr ""
+
+#. Tag: title
+#: using-d-i.xml:169
 #, no-c-format
 msgid "Components Introduction"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:126
+#: using-d-i.xml:170
 #, no-c-format
 msgid "Here is a list of installer components with a brief description of each component's purpose. Details you might need to know about using a particular component are in <xref linkend=\"module-details\"/>."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:137
+#: using-d-i.xml:181
 #, no-c-format
 msgid "main-menu"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:137
+#: using-d-i.xml:181
 #, no-c-format
 msgid "Shows the list of components to the user during installer operation, and starts a component when it is selected. Main-menu's questions are set to priority medium, so if your priority is set to high or critical (high is the default), you will not see the menu. On the other hand, if there is an error which requires your intervention, the question priority may be downgraded temporarily to allow you to resolve the problem, and in that case the menu may appear."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:147
+#: using-d-i.xml:191
 #, no-c-format
 msgid "You can get to the main menu by selecting the &BTN-GOBACK; button repeatedly to back all the way out of the currently running component."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:156
+#: using-d-i.xml:200
 #, no-c-format
 msgid "localechooser"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:156
+#: using-d-i.xml:200
 #, no-c-format
 msgid "Allows the user to select localization options for the installation and the installed system: language, country and locales. The installer will display messages in the selected language, unless the translation for that language is not complete in which case some messages may be shown in English."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:168
+#: using-d-i.xml:212
 #, no-c-format
 msgid "console-setup"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:168
+#: using-d-i.xml:212
 #, no-c-format
 msgid "Shows a list of keyboards, from which the user chooses the model which matches his own."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:177
+#: using-d-i.xml:221
 #, no-c-format
 msgid "hw-detect"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:177
+#: using-d-i.xml:221
 #, no-c-format
 msgid "Automatically detects most of the system's hardware, including network cards, disk drives, and PCMCIA."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:186
+#: using-d-i.xml:230
 #, no-c-format
 msgid "cdrom-detect"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:186
+#: using-d-i.xml:230
 #, no-c-format
 msgid "Looks for and mounts a &debian; installation CD."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:194
+#: using-d-i.xml:238
 #, no-c-format
 msgid "netcfg"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:194
+#: using-d-i.xml:238
 #, no-c-format
 msgid "Configures the computer's network connections so it can communicate over the internet."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:203
+#: using-d-i.xml:247
 #, no-c-format
 msgid "iso-scan"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:203
+#: using-d-i.xml:247
 #, no-c-format
 msgid "Searches for ISO images (<filename>.iso</filename> files) on hard drives."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:211
+#: using-d-i.xml:255
 #, no-c-format
 msgid "choose-mirror"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:211
+#: using-d-i.xml:255
 #, no-c-format
 msgid "Presents a list of &debian; archive mirrors. The user may choose the source of his installation packages."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:220
+#: using-d-i.xml:264
 #, no-c-format
 msgid "cdrom-checker"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:220
+#: using-d-i.xml:264
 #, no-c-format
 msgid "Checks integrity of a CD-ROM. This way, the user may assure him/herself that the installation CD-ROM was not corrupted."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:229
+#: using-d-i.xml:273
 #, no-c-format
 msgid "lowmem"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:229
+#: using-d-i.xml:273
 #, no-c-format
 msgid "Lowmem tries to detect systems with low memory and then does various tricks to remove unnecessary parts of &d-i; from the memory (at the cost of some features)."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:239
+#: using-d-i.xml:283
 #, no-c-format
 msgid "anna"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:239
+#: using-d-i.xml:283
 #, no-c-format
 msgid "Anna's Not Nearly APT. Installs packages which have been retrieved from the chosen mirror or CD."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:248
+#: using-d-i.xml:292
 #, no-c-format
 msgid "user-setup"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:248
+#: using-d-i.xml:292
 #, no-c-format
 msgid "Sets up the root password, and adds a non-root user."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:256
+#: using-d-i.xml:300
 #, no-c-format
 msgid "clock-setup"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:256
+#: using-d-i.xml:300
 #, no-c-format
 msgid "Updates the system clock and determines whether the clock is set to UTC or not."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:265
+#: using-d-i.xml:309
 #, no-c-format
 msgid "tzsetup"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:265
+#: using-d-i.xml:309
 #, no-c-format
 msgid "Selects the time zone, based on the location selected earlier."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:273
+#: using-d-i.xml:317
 #, no-c-format
 msgid "partman"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:273
+#: using-d-i.xml:317
 #, no-c-format
 msgid "Allows the user to partition disks attached to the system, create file systems on the selected partitions, and attach them to the mountpoints. Included are also interesting features like a fully automatic mode or LVM support. This is the preferred partitioning tool in &debian;."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:285
+#: using-d-i.xml:329
 #, no-c-format
 msgid "partitioner"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:285
+#: using-d-i.xml:329
 #, no-c-format
 msgid "Allows the user to partition disks attached to the system. A partitioning program appropriate to your computer's architecture is chosen."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:295
+#: using-d-i.xml:339
 #, no-c-format
 msgid "partconf"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:295
+#: using-d-i.xml:339
 #, no-c-format
 msgid "Displays a list of partitions, and creates file systems on the selected partitions according to user instructions."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:304
+#: using-d-i.xml:348
 #, no-c-format
 msgid "lvmcfg"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:304
+#: using-d-i.xml:348
 #, no-c-format
 msgid "Helps the user with the configuration of the <firstterm>LVM</firstterm> (Logical Volume Manager)."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:313
+#: using-d-i.xml:357
 #, no-c-format
 msgid "mdcfg"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:313
+#: using-d-i.xml:357
 #, no-c-format
 msgid "Allows the user to set up Software <firstterm>RAID</firstterm> (Redundant Array of Inexpensive Disks). This Software RAID is usually superior to the cheap IDE (pseudo hardware) RAID controllers found on newer motherboards."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:324
+#: using-d-i.xml:368
 #, no-c-format
 msgid "base-installer"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:324
+#: using-d-i.xml:368
 #, no-c-format
 msgid "Installs the most basic set of packages which would allow the computer to operate under &debian-gnu; when rebooted."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:333
+#: using-d-i.xml:377
 #, no-c-format
 msgid "apt-setup"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:333
+#: using-d-i.xml:377
 #, no-c-format
 msgid "Configures apt, mostly automatically, based on what media the installer is running from."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:342
+#: using-d-i.xml:386
 #, no-c-format
 msgid "pkgsel"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:342
+#: using-d-i.xml:386
 #, no-c-format
 msgid "Uses <classname>tasksel</classname> to select and install additional software."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:350
+#: using-d-i.xml:394
 #, no-c-format
 msgid "os-prober"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:350
+#: using-d-i.xml:394
 #, no-c-format
 msgid "Detects currently installed operating systems on the computer and passes this information to the bootloader-installer, which may offer you an ability to add discovered operating systems to the bootloader's start menu. This way the user could easily choose at the boot time which operating system to start."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:362
+#: using-d-i.xml:406
 #, no-c-format
 msgid "bootloader-installer"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:362
+#: using-d-i.xml:406
 #, no-c-format
 msgid "The various bootloader installers each install a boot loader program on the hard disk, which is necessary for the computer to start up using &arch-kernel; without using a floppy or CD-ROM. Many boot loaders allow the user to choose an alternate operating system each time the computer boots."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:373
+#: using-d-i.xml:417
 #, no-c-format
 msgid "shell"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:373
+#: using-d-i.xml:417
 #, no-c-format
 msgid "Allows the user to execute a shell from the menu, or in the second console."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:382
+#: using-d-i.xml:426
 #, no-c-format
 msgid "save-logs"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:382
+#: using-d-i.xml:426
 #, no-c-format
 msgid "Provides a way for the user to record information on a floppy disk, network, hard disk, or other media when trouble is encountered, in order to accurately report installer software problems to &debian; developers later."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:400
+#: using-d-i.xml:444
 #, no-c-format
 msgid "Using Individual Components"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:401
+#: using-d-i.xml:445
 #, no-c-format
 msgid "In this section we will describe each installer component in detail. The components have been grouped into stages that should be recognizable for users. They are presented in the order they appear during the install. Note that not all modules will be used for every installation; which modules are actually used depends on the installation method you use and on your hardware."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:413
+#: using-d-i.xml:457
 #, no-c-format
 msgid "Setting up &debian; Installer and Hardware Configuration"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:414
+#: using-d-i.xml:458
 #, no-c-format
 msgid "Let's assume the &debian; Installer has booted and you are facing its first screen. At this time, the capabilities of &d-i; are still quite limited. It doesn't know much about your hardware, preferred language, or even the task it should perform. Don't worry. Because &d-i; is quite clever, it can automatically probe your hardware, locate the rest of its components and upgrade itself to a capable installation system. However, you still need to help &d-i; with some information it can't determine automatically (like selecting your preferred language, keyboard layout or desired network mirror)."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:427
+#: using-d-i.xml:471
 #, no-c-format
 msgid "You will notice that &d-i; performs <firstterm>hardware detection</firstterm> several times during this stage. The first time is targeted specifically at the hardware needed to load installer components (e.g. your CD-ROM or network card). As not all drivers may be available during this first run, hardware detection needs to be repeated later in the process."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:435
+#: using-d-i.xml:479
 #, no-c-format
 msgid "During hardware detection &d-i; checks if any of the drivers for the hardware devices in your system require firmware to be loaded. If any firmware is requested but unavailable, a dialog will be displayed that allows the missing firmware to be loaded from a removable medium. See <xref linkend=\"loading-firmware\"/> for further details."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:450
+#: using-d-i.xml:494
 #, no-c-format
 msgid "Check available memory / low memory mode"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:452
+#: using-d-i.xml:496
 #, no-c-format
 msgid "One of the first things &d-i; does, is to check available memory. If the available memory is limited, this component will make some changes in the installation process which hopefully will allow you to install &debian-gnu; on your system."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:459
+#: using-d-i.xml:503
 #, no-c-format
 msgid "The first measure taken to reduce memory consumption by the installer is to disable translations, which means that the installation can only be done in English. Of course, you can still localize the installed system after the installation has completed."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:466
+#: using-d-i.xml:510
 #, no-c-format
 msgid "If that is not sufficient, the installer will further reduce memory consumption by loading only those components essential to complete a basic installation. This reduces the functionality of the installation system. You will be given the opportunity to load additional components manually, but you should be aware that each component you select will use additional memory and thus may cause the installation to fail."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:475
+#: using-d-i.xml:519
 #, no-c-format
 msgid "If the installer runs in low memory mode, it is recommended to create a relatively large swap partition (64&ndash;128MB). The swap partition will be used as virtual memory and thus increases the amount of memory available to the system. The installer will activate the swap partition as early as possible in the installation process. Note that heavy use of swap will reduce performance of your system and may lead to high disk activity."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:485
+#: using-d-i.xml:529
 #, no-c-format
 msgid "Despite these measures, it is still possible that your system freezes, that unexpected errors occur or that processes are killed by the kernel because the system runs out of memory (which will result in <quote>Out of memory</quote> messages on VT4 and in the syslog)."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:492
+#: using-d-i.xml:536
 #, no-c-format
 msgid "For example, it has been reported that creating a big ext3 file system fails in low memory mode when there is insufficient swap space. If a larger swap doesn't help, try creating the file system as ext2 (which is an essential component of the installer) instead. It is possible to change an ext2 partition to ext3 after the installation."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:500
+#: using-d-i.xml:544
 #, no-c-format
 msgid "It is possible to force the installer to use a higher lowmem level than the one based on available memory by using the boot parameter <quote>lowmem</quote> as described in <xref linkend=\"installer-args\"/>."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:515
+#: using-d-i.xml:559
 #, no-c-format
 msgid "Selecting Localization Options"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:517
+#: using-d-i.xml:561
 #, no-c-format
 msgid "In most cases the first questions you will be asked concern the selection of localization options to be used both for the installation and for the installed system. The localization options consist of language, location and locales."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:524
+#: using-d-i.xml:568
 #, no-c-format
 msgid "The language you choose will be used for the rest of the installation process, provided a translation of the different dialogs is available. If no valid translation is available for the selected language, the installer will default to English."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:531
+#: using-d-i.xml:575
 #, no-c-format
 msgid "The selected geographic location (in most cases a country) will be used later in the installation process to select the correct time zone and a &debian; mirror appropriate for that country. Language and country together will help determine the default locale for your system and select the correct keyboard layout."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:539
+#: using-d-i.xml:583
 #, no-c-format
 msgid "You will first be asked to select your preferred language. The language names are listed both in English (left side) and in the language itself (right side); the names on the right side are also shown in the proper script for the language. The list is sorted on the English names. At the top of the list is an extra option that allows you to select the <quote>C</quote> locale instead of a language. Choosing the <quote>C</quote> locale will result in the installation proceding in English; the installed system will have no localization support as the <classname>locales</classname> package will not be installed."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:551
+#: using-d-i.xml:595
 #, no-c-format
 msgid "Next you will be asked to select your geographic location. If you selected a language that is recognized as an official language for more than one country<footnote> <para> In technical terms: where multiple locales exist for that language with differing country codes. </para> </footnote>, you will be shown a list of only those countries. To select a country that is not in that list, choose <guimenuitem>other</guimenuitem> (the last option). You will then be presented with a list of continents; selecting a continent will lead to a list of relevant countries on that continent."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:568
+#: using-d-i.xml:612
 #, no-c-format
 msgid "If the language has only one country associated with it, a list of countries will be displayed for the continent or region the country belongs to, with that country selected as the default. Use the <guibutton>Go Back</guibutton> option to select countries on a different continent."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:575
+#: using-d-i.xml:619
 #, no-c-format
 msgid "It is important to select the country where you live or where you are located as it determines the time zone that will be configured for the installed system."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:581
+#: using-d-i.xml:625
 #, no-c-format
 msgid "If you selected a combination of language and country for which no locale is defined and there exist multiple locales for the language, then the installer will allow you to choose which of those locales you prefer as the default locale for the installed system<footnote> <para> At medium and low priority you can always select your preferred locale from those available for the selected language (if there's more than one). </para> </footnote>. In all other cases a default locale will be selected based on the selected language and country."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:596
+#: using-d-i.xml:640
 #, no-c-format
 msgid "Any default locale selected as described in the previous paragraph will use <firstterm>UTF-8</firstterm> as character encoding."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:601
+#: using-d-i.xml:645
 #, no-c-format
 msgid "If you are installing at low priority, you will have the option of selecting additional locales, including so-called <quote>legacy</quote> locales<footnote> <para> Legacy locales are locales which do not use UTF-8, but one of the older standards for character encoding such as ISO&nbsp;8859-1 (used by West European languages) or EUC-JP (used by Japanese). </para> </footnote>, to be generated for the installed system; if you do, you will be asked which of the selected locales should be the default for the installed system."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:625
+#: using-d-i.xml:669
 #, no-c-format
 msgid "Choosing a Keyboard"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:627
+#: using-d-i.xml:671
 #, no-c-format
 msgid "Keyboards are often tailored to the characters used in a language. Select a layout that conforms to the keyboard you are using, or select something close if the keyboard layout you want isn't represented. Once the system installation is complete, you'll be able to select a keyboard layout from a wider range of choices (run <command>dpkg-reconfigure keyboard-configuration</command> as root after you have completed the installation)."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:637
+#: using-d-i.xml:681
 #, no-c-format
 msgid "Move the highlight to the keyboard selection you desire and press &enterkey;. Use the arrow keys to move the highlight &mdash; they are in the same place in all national language keyboard layouts, so they are independent of the keyboard configuration."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:664
+#: using-d-i.xml:708
 #, no-c-format
 msgid "Looking for the &debian; Installer ISO Image"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:665
+#: using-d-i.xml:709
 #, no-c-format
 msgid "When installing via the <emphasis>hd-media</emphasis> method, there will be a moment where you need to find and mount the &debian; Installer iso image in order to get the rest of the installation files. The component <command>iso-scan</command> does exactly this."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:672
+#: using-d-i.xml:716
 #, no-c-format
 msgid "At first, <command>iso-scan</command> automatically mounts all block devices (e.g. partitions) which have some known filesystem on them and sequentially searches for filenames ending with <filename>.iso</filename> (or <filename>.ISO</filename> for that matter). Beware that the first attempt scans only files in the root directory and in the first level of subdirectories (i.e. it finds <filename>/<replaceable>whatever</replaceable>.iso</filename>, <filename>/data/<replaceable>whatever</replaceable>.iso</filename>, but not <filename>/data/tmp/<replaceable>whatever</replaceable>.iso</filename>). After an iso image has been found, <command>iso-scan</command> checks its content to determine if the image is a valid &debian; iso image or not. In the former case we are done, in the latter <command>iso-scan</command> seeks for another image."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:689
+#: using-d-i.xml:733
 #, no-c-format
 msgid "In case the previous attempt to find an installer iso image fails, <command>iso-scan</command> will ask you whether you would like to perform a more thorough search. This pass doesn't just look into the topmost directories, but really traverses whole filesystem."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:696
+#: using-d-i.xml:740
 #, no-c-format
 msgid "If <command>iso-scan</command> does not discover your installer iso image, reboot back to your original operating system and check if the image is named correctly (ending in <filename>.iso</filename>), if it is placed on a filesystem recognizable by &d-i;, and if it is not corrupted (verify the checksum). Experienced Unix users could do this without rebooting on the second console."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:717
+#: using-d-i.xml:761
 #, no-c-format
 msgid "Configuring the Network"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:719
+#: using-d-i.xml:763
 #, no-c-format
 msgid "As you enter this step, if the system detects that you have more than one network device, you'll be asked to choose which device will be your <emphasis>primary</emphasis> network interface, i.e. the one which you want to use for installation. The other interfaces won't be configured at this time. You may configure additional interfaces after installation is complete; see the <citerefentry> <refentrytitle>interfaces</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> man page."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:733
+#: using-d-i.xml:777
 #, no-c-format
 msgid "Automatic network configuration"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:734
+#: using-d-i.xml:778
 #, no-c-format
 msgid "By default, &d-i; tries to configure your computer's network automatically as far as possible. If the automatic configuration fails, that may be caused by many factors ranging from an unplugged network cable to missing infrastructure for automatic configuration. For further explanation in case of errors, check the error messages on the fourth console. In any case, you will be asked if you want to retry, or if you want to perform a manual setup. Sometimes the network services used for autoconfiguration can be slow in their responses, so if you are sure everything is in place, simply start the autoconfiguration attempt again. If autoconfiguration fails repeatedly, you can instead choose the manual network setup."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:753
+#: using-d-i.xml:797
 #, no-c-format
 msgid "Manual network configuration"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:754
+#: using-d-i.xml:798
 #, no-c-format
 msgid "The manual network setup in turn asks you a number of questions about your network, notably <computeroutput>IP address</computeroutput>, <computeroutput>Netmask</computeroutput>, <computeroutput>Gateway</computeroutput>, <computeroutput>Name server addresses</computeroutput>, and a <computeroutput>Hostname</computeroutput>. Moreover, if you have a wireless network interface, you will be asked to provide your <computeroutput>Wireless ESSID</computeroutput> (<quote>wireless network name</quote>) and a <computeroutput>WEP key</computeroutput> or <computeroutput>WPA/WPA2 passphrase</computeroutput>. Fill in the answers from <xref linkend=\"needed-info\"/>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:770
+#: using-d-i.xml:814
 #, no-c-format
 msgid "Some technical details you might, or might not, find handy: the program assumes the network IP address is the bitwise-AND of your system's IP address and your netmask. The default broadcast address is calculated as the bitwise OR of your system's IP address with the bitwise negation of the netmask. It will also guess your gateway. If you can't find any of these answers, use the offered defaults &mdash; if necessary, you can change them by editing <filename>/etc/network/interfaces</filename> once the system has been installed."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:785
+#: using-d-i.xml:829
 #, no-c-format
 msgid "IPv4 and IPv6"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:786
+#: using-d-i.xml:830
 #, no-c-format
 msgid "From &debian-gnu; 7.0 (<quote>Wheezy</quote>) onwards, &d-i; supports IPv6 as well as the <quote>classic</quote> IPv4. All combinations of IPv4 and IPv6 (IPv4-only, IPv6-only and dual-stack configurations) are supported."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:792
+#: using-d-i.xml:836
 #, no-c-format
 msgid "Autoconfiguration for IPv4 is done via DHCP (Dynamic Host Configuration Protocol). Autoconfiguration for IPv6 supports stateless autoconfiguration using NDP (Neighbor Discovery Protocol, including recursive DNS server (RDNSS) assignment), stateful autoconfiguration via DHCPv6 and mixed stateless/stateful autoconfiguration (address configuration via NDP, additional parameters via DHCPv6)."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:838
+#: using-d-i.xml:882
 #, no-c-format
 msgid "Configuring the Clock and Time Zone"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:840
+#: using-d-i.xml:884
 #, no-c-format
 msgid "The installer will first attempt to connect to a time server on the Internet (using the <firstterm>NTP</firstterm> protocol) in order to correctly set the system time. If this does not succeed, the installer will assume the time and date obtained from the system clock when the installation system was booted are correct. It is not possible to manually set the system time during the installation process."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:849
+#: using-d-i.xml:893
 #, no-c-format
 msgid "The installer does not modify the system clock on the s390 platform."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:862
+#: using-d-i.xml:906
 #, no-c-format
 msgid "Depending on the location selected earlier in the installation process, you may be shown a list of time zones relevant for that location. If your location has only one time zone and you are doing a default installation, you will not be asked anything and the system will assume that time zone."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:870
+#: using-d-i.xml:914
 #, no-c-format
 msgid "In expert mode or when installing at medium priority, you will have the additional option to select <quote>Coordinated Universal Time</quote> (UTC) as time zone."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:876
+#: using-d-i.xml:920
 #, no-c-format
 msgid "If for some reason you wish to set a time zone for the installed system that does <emphasis>not</emphasis> match the selected location, there are two options."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:887
+#: using-d-i.xml:931
 #, no-c-format
 msgid "The simplest option is to just select a different time zone after the installation has been completed and you've booted into the new system. The command to do this is:"
 msgstr ""
 
 #. Tag: screen
-#: using-d-i.xml:893
+#: using-d-i.xml:937
 #, no-c-format
 msgid "# dpkg-reconfigure tzdata"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:899
+#: using-d-i.xml:943
 #, no-c-format
 msgid "Alternatively, the time zone can be set at the very start of the installation by passing the parameter <userinput>time/zone=<replaceable>value</replaceable></userinput> when you boot the installation system. The value should of course be a valid time zone, for example <userinput>Europe/London</userinput> or <userinput>UTC</userinput>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:913
+#: using-d-i.xml:957
 #, no-c-format
 msgid "For automated installations the time zone can be set to any desired value using preseeding."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:927
+#: using-d-i.xml:971
 #, no-c-format
 msgid "Setting Up Users And Passwords"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:928
+#: using-d-i.xml:972
 #, no-c-format
 msgid "Just before configuring the clock, the installer will allow you to set up the <quote>root</quote> account and/or an account for the first user. Other user accounts can be created after the installation has been completed."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:942
+#: using-d-i.xml:986
 #, no-c-format
 msgid "Set the Root Password"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:946
+#: using-d-i.xml:990
 #, no-c-format
 msgid "The <emphasis>root</emphasis> account is also called the <emphasis>super-user</emphasis>; it is a login that bypasses all security protection on your system. The root account should only be used to perform system administration, and only used for as short a time as possible."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:954
+#: using-d-i.xml:998
 #, no-c-format
 msgid "Any password you create should contain at least 6 characters, and should contain both upper- and lower-case characters, as well as punctuation characters. Take extra care when setting your root password, since it is such a powerful account. Avoid dictionary words or use of any personal information which could be guessed."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:962
+#: using-d-i.xml:1006
 #, no-c-format
 msgid "If anyone ever tells you they need your root password, be extremely wary. You should normally never give your root password out, unless you are administering a machine with more than one system administrator."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:972
+#: using-d-i.xml:1016
 #, no-c-format
 msgid "Create an Ordinary User"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:974
+#: using-d-i.xml:1018
 #, no-c-format
 msgid "The system will ask you whether you wish to create an ordinary user account at this point. This account should be your main personal log-in. You should <emphasis>not</emphasis> use the root account for daily use or as your personal login."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:983
+#: using-d-i.xml:1027
 #, no-c-format
 msgid "Why not? Well, one reason to avoid using root's privileges is that it is very easy to do irreparable damage as root. Another reason is that you might be tricked into running a <emphasis>Trojan-horse</emphasis> program &mdash; that is a program that takes advantage of your super-user powers to compromise the security of your system behind your back. Any good book on Unix system administration will cover this topic in more detail &mdash; consider reading one if it is new to you."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:993
+#: using-d-i.xml:1037
 #, no-c-format
 msgid "You will first be prompted for the user's full name. Then you'll be asked for a name for the user account; generally your first name or something similar will suffice and indeed will be the default. Finally, you will be prompted for a password for this account."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1000
+#: using-d-i.xml:1044
 #, no-c-format
 msgid "If at any point after installation you would like to create another account, use the <command>adduser</command> command."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:1011
+#: using-d-i.xml:1055
 #, no-c-format
 msgid "Partitioning and Mount Point Selection"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1012
+#: using-d-i.xml:1056
 #, no-c-format
 msgid "At this time, after hardware detection has been executed a final time, &d-i; should be at its full strength, customized for the user's needs and ready to do some real work. As the title of this section indicates, the main task of the next few components lies in partitioning your disks, creating filesystems, assigning mountpoints and optionally configuring closely related options like RAID, LVM or encrypted devices."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1033
+#: using-d-i.xml:1077
 #, no-c-format
 msgid "If you are uncomfortable with partitioning, or just want to know more details, see <xref linkend=\"partitioning\"/>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1039
+#: using-d-i.xml:1083
 #, no-c-format
 msgid ""
       "If a hard disk has previously used under Solaris, the partitioner may not detect the size of the drive correctly. Creating a new partition table does not fix this issue. What does help, is to <quote>zero</quote> the first few sectors of the drive: <informalexample><screen>\n"
@@ -846,355 +882,355 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1052
+#: using-d-i.xml:1096
 #, no-c-format
 msgid "First you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive. This is also called <quote>guided</quote> partitioning. If you do not want to autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:1062
+#: using-d-i.xml:1106
 #, no-c-format
 msgid "Supported partitioning options"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1063
+#: using-d-i.xml:1107
 #, no-c-format
 msgid "The partitioner used in &d-i; is fairly versatile. It allows to create many different partitioning schemes, using various partition tables, file systems and advanced block devices."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1069
+#: using-d-i.xml:1113
 #, no-c-format
 msgid "Exactly which options are available depends mainly on the architecture, but also on other factors. For example, on systems with limited internal memory some options may not be available. Defaults may vary as well. The type of partition table used by default can for example be different for large capacity hard disks than for smaller hard disks. Some options can only be changed when installing at medium or low debconf priority; at higher priorities sensible defaults will be used."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1080
+#: using-d-i.xml:1124
 #, no-c-format
 msgid "The installer supports various forms of advanced partitioning and use of storage devices, which in many cases can be used in combination."
 msgstr ""
 
 #. Tag: emphasis
-#: using-d-i.xml:1087
+#: using-d-i.xml:1131
 #, no-c-format
 msgid "Logical Volume Management (LVM)"
 msgstr ""
 
 #. Tag: emphasis
-#: using-d-i.xml:1090
+#: using-d-i.xml:1134
 #, no-c-format
 msgid "Software RAID"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1091
+#: using-d-i.xml:1135
 #, no-c-format
 msgid "Supported are RAID levels 0, 1, 4, 5, 6 and 10."
 msgstr ""
 
 #. Tag: emphasis
-#: using-d-i.xml:1095
+#: using-d-i.xml:1139
 #, no-c-format
 msgid "Encryption"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1097
+#: using-d-i.xml:1141
 #, no-c-format
 msgid "<emphasis>Serial ATA RAID</emphasis> (using <classname>dmraid</classname>)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1099
+#: using-d-i.xml:1143
 #, no-c-format
 msgid "Also called <quote>fake RAID</quote> or <quote>BIOS RAID</quote>. Support for Serial ATA RAID is currently only available if enabled when the installer is booted. Further information is available on <ulink url=\"&url-d-i-sataraid;\">our Wiki</ulink>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1105
+#: using-d-i.xml:1149
 #, no-c-format
 msgid "<emphasis>Multipath</emphasis> (experimental)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1107
+#: using-d-i.xml:1151
 #, no-c-format
 msgid "See <ulink url=\"&url-d-i-multipath;\">our Wiki</ulink> for information. Support for multipath is currently only available if enabled when the installer is booted."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1114
+#: using-d-i.xml:1158
 #, no-c-format
 msgid "The following file systems are supported."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1119
+#: using-d-i.xml:1163
 #, no-c-format
 msgid "<phrase arch=\"arm;mipsel\"><emphasis>ext2r0</emphasis>,</phrase> <emphasis>ext2</emphasis>, <phrase arch=\"linux-any\"><emphasis>ext3</emphasis>,</phrase> <phrase arch=\"linux-any\"><emphasis>ext4</emphasis></phrase>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1124
+#: using-d-i.xml:1168
 #, no-c-format
 msgid "The default file system selected in most cases is ext4; for <filename>/boot</filename> partitions ext2 will be selected by default when guided partitioning is used."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1129
+#: using-d-i.xml:1173
 #, no-c-format
 msgid "<emphasis>jfs</emphasis> (not available on all architectures)"
 msgstr ""
 
 #. Tag: emphasis
-#: using-d-i.xml:1133
+#: using-d-i.xml:1177
 #, no-c-format
 msgid "<emphasis>ufs</emphasis>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1134
+#: using-d-i.xml:1178
 #, no-c-format
 msgid "The default file system is UFS."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1137
+#: using-d-i.xml:1181
 #, no-c-format
 msgid "<emphasis>xfs</emphasis> (not available on all architectures)"
 msgstr ""
 
 #. Tag: emphasis
-#: using-d-i.xml:1141
+#: using-d-i.xml:1185
 #, no-c-format
 msgid "<emphasis>zfs</emphasis>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1142
+#: using-d-i.xml:1186
 #, no-c-format
 msgid "As ZFS support in the installer is still in development, only a basic subset of ZFS features are supported. Some of them can be enabled manually after the initial install, but there are some caveats:"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1147
+#: using-d-i.xml:1191
 #, no-c-format
 msgid "Each ZFS pool will host only one filesystem. After install is finished, more filesystems can be created on this pool by using the <quote>zfs create</quote> command."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1152
+#: using-d-i.xml:1196
 #, no-c-format
 msgid "Each ZFS pool will be composed of exactly one partition. After install is finished, a single-device ZFS pool can be converted into a multi-device pool by using the <quote>zpool add</quote> command, or into a mirrored pool by using the <quote>zpool attach</quote> command. However, you shouldn't do this on the pool that hosts root filesystem, as it would prevent GRUB from booting your system."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1160
+#: using-d-i.xml:1204
 #, no-c-format
 msgid "Compression is not currently supported. After the install is finished, compression can be enabled by setting the <quote>compression</quote> property via the <quote>zfs set</quote> command. However, if a compression algorithm other than the default (lzjb) is used on the pool that hosts your root filesystem, this may prevent GRUB from booting your system."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1169
+#: using-d-i.xml:1213
 #, no-c-format
 msgid "<emphasis>reiserfs</emphasis> (optional; not available on all architectures)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1171
+#: using-d-i.xml:1215
 #, no-c-format
 msgid "Support for the Reiser file system is no longer available by default. When the installer is running at medium or low debconf priority it can be enabled by selecting the <classname>partman-reiserfs</classname> component. Only version 3 of the file system is supported."
 msgstr ""
 
 #. Tag: emphasis
-#: using-d-i.xml:1178
+#: using-d-i.xml:1222
 #, no-c-format
 msgid "jffs2"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1179
+#: using-d-i.xml:1223
 #, no-c-format
 msgid "Used on some systems to read flash memory. It is not possible to create new jffs2 partitions."
 msgstr ""
 
 #. Tag: emphasis
-#: using-d-i.xml:1184
+#: using-d-i.xml:1228
 #, no-c-format
 msgid "qnx4"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1185
+#: using-d-i.xml:1229
 #, no-c-format
 msgid "Existing partitions will be recognized and it is possible to assign mount points for them. It is not possible to create new qnx4 partitions."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1189
+#: using-d-i.xml:1233
 #, no-c-format
 msgid "<emphasis>FAT16</emphasis>, <emphasis>FAT32</emphasis>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1192
+#: using-d-i.xml:1236
 #, no-c-format
 msgid "<emphasis>NTFS</emphasis> (read-only)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1194
+#: using-d-i.xml:1238
 #, no-c-format
 msgid "Existing NTFS partitions can be resized and it is possible to assign mount points for them. It is not possible to create new NTFS partitions."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:1204
+#: using-d-i.xml:1248
 #, no-c-format
 msgid "Guided Partitioning"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1205
+#: using-d-i.xml:1249
 #, no-c-format
 msgid "If you choose guided partitioning, you may have three options: to create partitions directly on the hard disk (classic method), or to create them using Logical Volume Management (LVM), or to create them using encrypted LVM<footnote> <para> The installer will encrypt the LVM volume group using a 256 bit AES key and makes use of the kernel's <quote>dm-crypt</quote> support. </para> </footnote>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1220
+#: using-d-i.xml:1264
 #, no-c-format
 msgid "The option to use (encrypted) LVM may not be available on all architectures."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1225
+#: using-d-i.xml:1269
 #, no-c-format
 msgid "When using LVM or encrypted LVM, the installer will create most partitions inside one big partition; the advantage of this method is that partitions inside this big partition can be resized relatively easily later. In the case of encrypted LVM the big partition will not be readable without knowing a special key phrase, thus providing extra security of your (personal) data."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1234
+#: using-d-i.xml:1278
 #, no-c-format
 msgid "When using encrypted LVM, the installer will also automatically erase the disk by writing random data to it. This further improves security (as it makes it impossible to tell which parts of the disk are in use and also makes sure that any traces of previous installations are erased), but may take some time depending on the size of your disk."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1243
+#: using-d-i.xml:1287
 #, no-c-format
 msgid "If you choose guided partitioning using LVM or encrypted LVM, some changes in the partition table will need to be written to the selected disk while LVM is being set up. These changes effectively erase all data that is currently on the selected hard disk and you will not be able to undo them later. However, the installer will ask you to confirm these changes before they are written to disk."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1253
+#: using-d-i.xml:1297
 #, no-c-format
 msgid "If you choose guided partitioning<phrase arch=\"linux-any\"> (either classic or using (encrypted) LVM)</phrase> for a whole disk, you will first be asked to select the disk you want to use. Check that all your disks are listed and, if you have several disks, make sure you select the correct one. The order they are listed in may differ from what you are used to. The size of the disks may help to identify them."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1262
+#: using-d-i.xml:1306
 #, no-c-format
 msgid "Any data on the disk you select will eventually be lost, but you will always be asked to confirm any changes before they are written to the disk. <phrase arch=\"linux-any\"> If you have selected the classic method of partitioning, you will be able to undo any changes right until the end; when using (encrypted) LVM this is not possible. </phrase>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1272
+#: using-d-i.xml:1316
 #, no-c-format
 msgid "Next, you will be able to choose from the schemes listed in the table below. All schemes have their pros and cons, some of which are discussed in <xref linkend=\"partitioning\"/>. If you are unsure, choose the first one. Bear in mind that guided partitioning needs a certain minimal amount of free space to operate with. If you don't give it at least about 1GB of space (depends on chosen scheme), guided partitioning will fail."
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1288
+#: using-d-i.xml:1332
 #, no-c-format
 msgid "Partitioning scheme"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1289
+#: using-d-i.xml:1333
 #, no-c-format
 msgid "Minimum space"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1290
+#: using-d-i.xml:1334
 #, no-c-format
 msgid "Created partitions"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1296
+#: using-d-i.xml:1340
 #, no-c-format
 msgid "All files in one partition"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1297
+#: using-d-i.xml:1341
 #, no-c-format
 msgid "600MB"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1298
+#: using-d-i.xml:1342
 #, no-c-format
 msgid "<filename>/</filename>, swap"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1300
+#: using-d-i.xml:1344
 #, no-c-format
 msgid "Separate /home partition"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1301
+#: using-d-i.xml:1345
 #, no-c-format
 msgid "500MB"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1302
+#: using-d-i.xml:1346
 #, no-c-format
 msgid "<filename>/</filename>, <filename>/home</filename>, swap"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1306
+#: using-d-i.xml:1350
 #, no-c-format
 msgid "Separate /home, /usr, /var and /tmp partitions"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1307
+#: using-d-i.xml:1351
 #, no-c-format
 msgid "<entry>1GB</entry>"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1308
+#: using-d-i.xml:1352
 #, no-c-format
 msgid "<filename>/</filename>, <filename>/home</filename>, <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1317
+#: using-d-i.xml:1361
 #, no-c-format
 msgid "If you choose guided partitioning using (encrypted) LVM, the installer will also create a separate <filename>/boot</filename> partition. The other partitions, including the swap partition, will be created inside the LVM partition."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1323
+#: using-d-i.xml:1367
 #, no-c-format
 msgid "If you choose guided partitioning for your IA-64 system, there will be an additional partition, formatted as a FAT16 bootable filesystem, for the EFI boot loader. There is also an additional menu item in the formatting menu to manually set up a partition as an EFI boot partition."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1331
+#: using-d-i.xml:1375
 #, no-c-format
 msgid "After selecting a scheme, the next screen will show your new partition table, including information on whether and how partitions will be formatted and where they will be mounted."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1337
+#: using-d-i.xml:1381
 #, no-c-format
 msgid ""
       "The list of partitions might look like this: <informalexample><screen>\n"
@@ -1217,1184 +1253,1127 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1350
+#: using-d-i.xml:1394
 #, no-c-format
 msgid "This concludes the guided partitioning. If you are satisfied with the generated partition table, you can choose <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the menu to implement the new partition table (as described at the end of this section). If you are not happy, you can choose to <guimenuitem>Undo changes to partitions</guimenuitem> and run guided partitioning again, or modify the proposed changes as described below for manual partitioning."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:1364
+#: using-d-i.xml:1408
 #, no-c-format
 msgid "Manual Partitioning"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1365
+#: using-d-i.xml:1409
 #, no-c-format
 msgid "A similar screen to the one shown just above will be displayed if you choose manual partitioning except that your existing partition table will be shown and without the mount points. How to manually set up your partition table and the usage of partitions by your new &debian; system will be covered in the remainder of this section."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1373
+#: using-d-i.xml:1417
 #, no-c-format
 msgid "If you select a pristine disk which has neither partitions nor free space on it, you will be asked if a new partition table should be created (this is needed so you can create new partitions). After this, a new line entitled <quote>FREE SPACE</quote> should appear in the table under the selected disk."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1381
+#: using-d-i.xml:1425
 #, no-c-format
 msgid "If you select some free space, you will have the opportunity to create a new partition. You will have to answer a quick series of questions about its size, type (primary or logical), and location (beginning or end of the free space). After this, you will be presented with a detailed overview of your new partition. The main setting is <guimenuitem>Use as:</guimenuitem>, which determines if the partition will have a file system on it, or be used for swap,<phrase arch=\"linux-any\"> software RAID, LVM, an encrypted file system,</phrase> or not be used at all. Other settings include mountpoint, mount options, and bootable flag; which settings are shown depends on how the partition is to be used. If you don't like the preselected defaults, feel free to change them to your liking. E.g. by selecting the option <guimenuitem>Use as:</guimenuitem>, you can choose a different filesystem for this partition, including options to use the partition for swap,<phrase arch=\"linux-any\"> software RAID, LVM,</phrase> or not use it at all. When you are satisfied with your new partition, select <guimenuitem>Done setting up the partition</guimenuitem> and you will return to <command>partman</command>'s main screen."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1402
+#: using-d-i.xml:1446
 #, no-c-format
 msgid "If you decide you want to change something about your partition, simply select the partition, which will bring you to the partition configuration menu. This is the same screen as is used when creating a new partition, so you can change the same settings. One thing that may not be very obvious at a first glance is that you can resize the partition by selecting the item displaying the size of the partition. Filesystems known to work are at least fat16, fat32, ext2, ext3 and swap. This menu also allows you to delete a partition."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1413
+#: using-d-i.xml:1457
 #, no-c-format
 msgid "Be sure to create at least two partitions: one for the <emphasis>root</emphasis> filesystem (which must be mounted as <filename>/</filename>) and one for <emphasis>swap</emphasis>. If you forget to mount the root filesystem, <command>partman</command> won't let you continue until you correct this issue."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1421
+#: using-d-i.xml:1465
 #, no-c-format
 msgid "If you forget to select and format an EFI boot partition, <command>partman</command> will detect this and will not let you continue until you allocate one."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1427
+#: using-d-i.xml:1471
 #, no-c-format
 msgid "Capabilities of <command>partman</command> can be extended with installer modules, but are dependent on your system's architecture. So if you can't see all promised goodies, check if you have loaded all required modules (e.g. <filename>partman-ext3</filename>, <filename>partman-xfs</filename>, or <filename>partman-lvm</filename>)."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1435
+#: using-d-i.xml:1479
 #, no-c-format
 msgid "After you are satisfied with partitioning, select <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the partitioning menu. You will be presented with a summary of changes made to the disks and asked to confirm that the filesystems should be created as requested."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:1463
+#: using-d-i.xml:1507
 #, no-c-format
 msgid "Configuring Multidisk Devices (Software RAID)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1464
+#: using-d-i.xml:1508
 #, no-c-format
 msgid "If you have more than one harddrive<footnote><para> To be honest, you can construct an MD device even from partitions residing on single physical drive, but that won't give any benefits. </para></footnote> in your computer, you can use <command>mdcfg</command> to set up your drives for increased performance and/or better reliability of your data. The result is called <firstterm>Multidisk Device</firstterm> (or after its most famous variant <firstterm>software RAID</firstterm>)."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1477
+#: using-d-i.xml:1521
 #, no-c-format
 msgid "MD is basically a bunch of partitions located on different disks and combined together to form a <emphasis>logical</emphasis> device. This device can then be used like an ordinary partition (i.e. in <command>partman</command> you can format it, assign a mountpoint, etc.)."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1485
+#: using-d-i.xml:1529
 #, no-c-format
 msgid "What benefits this brings depends on the type of MD device you are creating. Currently supported are: <variablelist> <varlistentry> <term>RAID0</term><listitem><para> Is mainly aimed at performance. RAID0 splits all incoming data into <firstterm>stripes</firstterm> and distributes them equally over each disk in the array. This can increase the speed of read/write operations, but when one of the disks fails, you will lose <emphasis>everything</emphasis> (part of the information is still on the healthy disk(s), the other part <emphasis>was</emphasis> on the failed disk). </para><para> The typical use for RAID0 is a partition for video editing. </para></listitem> </varlistentry> <varlistentry> <term>RAID1</term><listitem><para> Is suitable for setups where reliability is the first concern. It consists of several (usually two) equally-sized partitions where every partition contains exactly the same data. This essentially means three things. First, if one of your disks fails, you still have the data mirrored on the remaining disks. Second, you can use only a fraction of the available capacity (more precisely, it is the size of the smallest partition in the RAID). Third, file-reads are load-balanced among the disks, which can improve performance on a server, such as a file server, that tends to be loaded with more disk reads than writes. </para><para> Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para></listitem> </varlistentry> <varlistentry> <term>RAID5</term><listitem><para> Is a good compromise between speed, reliability and data redundancy. RAID5 splits all incoming data into stripes and distributes them equally on all but one disk (similar to RAID0). Unlike RAID0, RAID5 also computes <firstterm>parity</firstterm> information, which gets written on the remaining disk. The parity disk is not static (that would be called RAID4), but is changing periodically, so the parity information is distributed equally on all disks. When one of the disks fails, the missing part of information can be computed from remaining data and its parity. RAID5 must consist of at least three active partitions. Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para><para> As you can see, RAID5 has a similar degree of reliability to RAID1 while achieving less redundancy. On the other hand, it might be a bit slower on write operations than RAID0 due to computation of parity information. </para></listitem> </varlistentry> <varlistentry> <term>RAID6</term><listitem><para> Is similar to RAID5 except that it uses two parity devices instead of one. </para><para> A RAID6 array can survive up to two disk failures. </para></listitem> </varlistentry> <varlistentry> <term>RAID10</term><listitem><para> RAID10 combines striping (as in RAID0) and mirroring (as in RAID1). It creates <replaceable>n</replaceable> copies of incoming data and distributes them across the partitions so that none of the copies of the same data are on the same device. The default value of <replaceable>n</replaceable> is 2, but it can be set to something else in expert mode. The number of partitions used must be at least <replaceable>n</replaceable>. RAID10 has different layouts for distributing the copies. The default is near copies. Near copies have all of the copies at about the same offset on all of the disks. Far copies have the copies at different offsets on the disks. Offset copies copy the stripe, not the individual copies. </para><para> RAID10 can be used to achieve reliability and redundancy without the drawback of having to calculate parity. </para></listitem> </varlistentry> </variablelist> To sum it up:"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1599
+#: using-d-i.xml:1643
 #, no-c-format
 msgid "Type"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1600
+#: using-d-i.xml:1644
 #, no-c-format
 msgid "Minimum Devices"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1601
+#: using-d-i.xml:1645
 #, no-c-format
 msgid "Spare Device"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1602
+#: using-d-i.xml:1646
 #, no-c-format
 msgid "Survives disk failure?"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1603
+#: using-d-i.xml:1647
 #, no-c-format
 msgid "Available Space"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1609
+#: using-d-i.xml:1653
 #, no-c-format
 msgid "RAID0"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1610 using-d-i.xml:1618 using-d-i.xml:1648
+#: using-d-i.xml:1654 using-d-i.xml:1662 using-d-i.xml:1692
 #, no-c-format
 msgid "<entry>2</entry>"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1611 using-d-i.xml:1612
+#: using-d-i.xml:1655 using-d-i.xml:1656
 #, no-c-format
 msgid "<entry>no</entry>"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1613
+#: using-d-i.xml:1657
 #, no-c-format
 msgid "Size of the smallest partition multiplied by number of devices in RAID"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1617
+#: using-d-i.xml:1661
 #, no-c-format
 msgid "RAID1"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1619 using-d-i.xml:1627 using-d-i.xml:1638 using-d-i.xml:1649
+#: using-d-i.xml:1663 using-d-i.xml:1671 using-d-i.xml:1682 using-d-i.xml:1693
 #, no-c-format
 msgid "optional"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1620 using-d-i.xml:1628 using-d-i.xml:1639 using-d-i.xml:1650
+#: using-d-i.xml:1664 using-d-i.xml:1672 using-d-i.xml:1683 using-d-i.xml:1694
 #, no-c-format
 msgid "<entry>yes</entry>"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1621
+#: using-d-i.xml:1665
 #, no-c-format
 msgid "Size of the smallest partition in RAID"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1625
+#: using-d-i.xml:1669
 #, no-c-format
 msgid "RAID5"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1626
+#: using-d-i.xml:1670
 #, no-c-format
 msgid "<entry>3</entry>"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1629
+#: using-d-i.xml:1673
 #, no-c-format
 msgid "Size of the smallest partition multiplied by (number of devices in RAID minus one)"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1636
+#: using-d-i.xml:1680
 #, no-c-format
 msgid "RAID6"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1637
+#: using-d-i.xml:1681
 #, no-c-format
 msgid "<entry>4</entry>"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1640
+#: using-d-i.xml:1684
 #, no-c-format
 msgid "Size of the smallest partition multiplied by (number of devices in RAID minus two)"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1647
+#: using-d-i.xml:1691
 #, no-c-format
 msgid "RAID10"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1651
+#: using-d-i.xml:1695
 #, no-c-format
 msgid "Total of all partitions divided by the number of chunk copies (defaults to two)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1658
+#: using-d-i.xml:1702
 #, no-c-format
 msgid "If you want to know more about Software RAID, have a look at <ulink url=\"&url-software-raid-howto;\">Software RAID HOWTO</ulink>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1663
+#: using-d-i.xml:1707
 #, no-c-format
 msgid "To create an MD device, you need to have the desired partitions it should consist of marked for use in a RAID. (This is done in <command>partman</command> in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for RAID</guimenuitem> </menuchoice>.)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1672
+#: using-d-i.xml:1716
 #, no-c-format
 msgid "Make sure that the system can be booted with the partitioning scheme you are planning. In general it will be necessary to create a separate file system for <filename>/boot</filename> when using RAID for the root (<filename>/</filename>) file system. Most boot loaders <phrase arch=\"x86\">(including lilo and grub)</phrase> do support mirrored (not striped!) RAID1, so using for example RAID5 for <filename>/</filename> and RAID1 for <filename>/boot</filename> can be an option."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1684
+#: using-d-i.xml:1728
 #, no-c-format
 msgid "Support for MD is a relatively new addition to the installer. You may experience problems for some RAID levels and in combination with some bootloaders if you try to use MD for the root (<filename>/</filename>) file system. For experienced users, it may be possible to work around some of these problems by executing some configuration or installation steps manually from a shell."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1693
+#: using-d-i.xml:1737
 #, no-c-format
 msgid "Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> from the main <command>partman</command> menu. (The menu will only appear after you mark at least one partition for use as <guimenuitem>physical volume for RAID</guimenuitem>.) On the first screen of <command>mdcfg</command> simply select <guimenuitem>Create MD device</guimenuitem>. You will be presented with a list of supported types of MD devices, from which you should choose one (e.g. RAID1). What follows depends on the type of MD you selected."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1706
+#: using-d-i.xml:1750
 #, no-c-format
 msgid "RAID0 is simple &mdash; you will be issued with the list of available RAID partitions and your only task is to select the partitions which will form the MD."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1713
+#: using-d-i.xml:1757
 #, no-c-format
 msgid "RAID1 is a bit more tricky. First, you will be asked to enter the number of active devices and the number of spare devices which will form the MD. Next, you need to select from the list of available RAID partitions those that will be active and then those that will be spare. The count of selected partitions must be equal to the number provided earlier. Don't worry. If you make a mistake and select a different number of partitions, &d-i; won't let you continue until you correct the issue."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1725
+#: using-d-i.xml:1769
 #, no-c-format
 msgid "RAID5 has a setup procedure similar to RAID1 with the exception that you need to use at least <emphasis>three</emphasis> active partitions."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1731
+#: using-d-i.xml:1775
 #, no-c-format
 msgid "RAID6 also has a setup procedure similar to RAID1 except that at least <emphasis>four</emphasis> active partitions are required."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1737
+#: using-d-i.xml:1781
 #, no-c-format
 msgid "RAID10 again has a setup procedure similar to RAID1 except in expert mode. In expert mode, &d-i; will ask you for the layout. The layout has two parts. The first part is the layout type. It is either <literal>n</literal> (for near copies), <literal>f</literal> (for far copies), or <literal>o</literal> (for offset copies). The second part is the number of copies to make of the data. There must be at least that many active devices so that all of the copies can be distributed onto different disks."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1751
+#: using-d-i.xml:1795
 #, no-c-format
 msgid "It is perfectly possible to have several types of MD at once. For example, if you have three 200 GB hard drives dedicated to MD, each containing two 100 GB partitions, you can combine the first partitions on all three disks into the RAID0 (fast 300 GB video editing partition) and use the other three partitions (2 active and 1 spare) for RAID1 (quite reliable 100 GB partition for <filename>/home</filename>)."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1760
+#: using-d-i.xml:1804
 #, no-c-format
 msgid "After you set up MD devices to your liking, you can <guimenuitem>Finish</guimenuitem> <command>mdcfg</command> to return back to the <command>partman</command> to create filesystems on your new MD devices and assign them the usual attributes like mountpoints."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:1775
+#: using-d-i.xml:1819
 #, no-c-format
 msgid "Configuring the Logical Volume Manager (LVM)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1776
+#: using-d-i.xml:1820
 #, no-c-format
 msgid "If you are working with computers at the level of system administrator or <quote>advanced</quote> user, you have surely seen the situation where some disk partition (usually the most important one) was short on space, while some other partition was grossly underused and you had to manage this situation by moving stuff around, symlinking, etc."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1784
+#: using-d-i.xml:1828
 #, no-c-format
 msgid "To avoid the described situation you can use Logical Volume Manager (LVM). Simply said, with LVM you can combine your partitions (<firstterm>physical volumes</firstterm> in LVM lingo) to form a virtual disk (so called <firstterm>volume group</firstterm>), which can then be divided into virtual partitions (<firstterm>logical volumes</firstterm>). The point is that logical volumes (and of course underlying volume groups) can span across several physical disks."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1794
+#: using-d-i.xml:1838
 #, no-c-format
 msgid "Now when you realize you need more space for your old 160GB <filename>/home</filename> partition, you can simply add a new 300GB disk to the computer, join it with your existing volume group and then resize the logical volume which holds your <filename>/home</filename> filesystem and voila &mdash; your users have some room again on their renewed 460GB partition. This example is of course a bit oversimplified. If you haven't read it yet, you should consult the <ulink url=\"&url-lvm-howto;\">LVM HOWTO</ulink>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1805
+#: using-d-i.xml:1849
 #, no-c-format
 msgid "LVM setup in &d-i; is quite simple and completely supported inside <command>partman</command>. First, you have to mark the partition(s) to be used as physical volumes for LVM. This is done in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for LVM</guimenuitem> </menuchoice>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1814
+#: using-d-i.xml:1858
 #, no-c-format
 msgid "When you return to the main <command>partman</command> screen, you will see a new option <guimenuitem>Configure the Logical Volume Manager</guimenuitem>. When you select that, you will first be asked to confirm pending changes to the partition table (if any) and after that the LVM configuration menu will be shown. Above the menu a summary of the LVM configuration is shown. The menu itself is context sensitive and only shows valid actions. The possible actions are:"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1825
+#: using-d-i.xml:1869
 #, no-c-format
 msgid "<guimenuitem>Display configuration details</guimenuitem>: shows LVM device structure, names and sizes of logical volumes and more"
 msgstr ""
 
 #. Tag: guimenuitem
-#: using-d-i.xml:1830
+#: using-d-i.xml:1874
 #, no-c-format
 msgid "Create volume group"
 msgstr ""
 
 #. Tag: guimenuitem
-#: using-d-i.xml:1833
+#: using-d-i.xml:1877
 #, no-c-format
 msgid "Create logical volume"
 msgstr ""
 
 #. Tag: guimenuitem
-#: using-d-i.xml:1836
+#: using-d-i.xml:1880
 #, no-c-format
 msgid "Delete volume group"
 msgstr ""
 
 #. Tag: guimenuitem
-#: using-d-i.xml:1839
+#: using-d-i.xml:1883
 #, no-c-format
 msgid "Delete logical volume"
 msgstr ""
 
 #. Tag: guimenuitem
-#: using-d-i.xml:1842
+#: using-d-i.xml:1886
 #, no-c-format
 msgid "Extend volume group"
 msgstr ""
 
 #. Tag: guimenuitem
-#: using-d-i.xml:1845
+#: using-d-i.xml:1889
 #, no-c-format
 msgid "Reduce volume group"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1847
+#: using-d-i.xml:1891
 #, no-c-format
 msgid "<guimenuitem>Finish</guimenuitem>: return to the main <command>partman</command> screen"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1853
+#: using-d-i.xml:1897
 #, no-c-format
 msgid "Use the options in that menu to first create a volume group and then create your logical volumes inside it."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1858
+#: using-d-i.xml:1902
 #, no-c-format
 msgid "After you return to the main <command>partman</command> screen, any created logical volumes will be displayed in the same way as ordinary partitions (and you should treat them as such)."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:1872
+#: using-d-i.xml:1916
 #, no-c-format
 msgid "Configuring Encrypted Volumes"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1873
+#: using-d-i.xml:1917
 #, no-c-format
 msgid "&d-i; allows you to set up encrypted partitions. Every file you write to such a partition is immediately saved to the device in encrypted form. Access to the encrypted data is granted only after entering the <firstterm>passphrase</firstterm> used when the encrypted partition was originally created. This feature is useful to protect sensitive data in case your laptop or hard drive gets stolen. The thief might get physical access to the hard drive, but without knowing the right passphrase, the data on the hard drive will look like random characters."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1885
+#: using-d-i.xml:1929
 #, no-c-format
 msgid "The two most important partitions to encrypt are: the home partition, where your private data resides, and the swap partition, where sensitive data might be stored temporarily during operation. Of course, nothing prevents you from encrypting any other partitions that might be of interest. For example <filename>/var</filename> where database servers, mail servers or print servers store their data, or <filename>/tmp</filename> which is used by various programs to store potentially interesting temporary files. Some people may even want to encrypt their whole system. The only exception is the <filename>/boot</filename> partition which must remain unencrypted, because currently there is no way to load the kernel from an encrypted partition."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1900
+#: using-d-i.xml:1944
 #, no-c-format
 msgid "Please note that the performance of encrypted partitions will be less than that of unencrypted ones because the data needs to be decrypted or encrypted for every read or write. The performance impact depends on your CPU speed, chosen cipher and a key length."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1907
+#: using-d-i.xml:1951
 #, no-c-format
 msgid "To use encryption, you have to create a new partition by selecting some free space in the main partitioning menu. Another option is to choose an existing partition (e.g. a regular partition, an LVM logical volume or a RAID volume). In the <guimenu>Partition settings</guimenu> menu, you need to select <guimenuitem>physical volume for encryption</guimenuitem> at the <menuchoice> <guimenu>Use as:</guimenu> </menuchoice> option. The menu will then change to include several cryptographic options for the partition."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1918
+#: using-d-i.xml:1962
 #, no-c-format
-msgid "&d-i; supports several encryption methods. The default method is <firstterm>dm-crypt</firstterm> (included in newer Linux kernels, able to host LVM physical volumes), the other is <firstterm>loop-AES</firstterm> (older, maintained separately from the Linux kernel tree). Unless you have compelling reasons to do otherwise, it is recommended to use the default."
+msgid "The encryption method supported by &d-i; is <firstterm>dm-crypt</firstterm> (included in newer Linux kernels, able to host LVM physical volumes)."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1930
+#: using-d-i.xml:1971
 #, no-c-format
-msgid "First, let's have a look at the options available when you select <userinput>Device-mapper (dm-crypt)</userinput> as the encryption method. As always: when in doubt, use the defaults, because they have been carefully chosen with security in mind."
+msgid "Let's have a look at the options available when you select encryption via <userinput>Device-mapper (dm-crypt)</userinput>. As always: when in doubt, use the defaults, because they have been carefully chosen with security in mind."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:1940
+#: using-d-i.xml:1981
 #, no-c-format
 msgid "Encryption: <userinput>aes</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1942
+#: using-d-i.xml:1983
 #, no-c-format
 msgid "This option lets you select the encryption algorithm (<firstterm>cipher</firstterm>) which will be used to encrypt the data on the partition. &d-i; currently supports the following block ciphers: <firstterm>aes</firstterm>, <firstterm>blowfish</firstterm>, <firstterm>serpent</firstterm>, and <firstterm>twofish</firstterm>. It is beyond the scope of this document to discuss the qualities of these different algorithms, however, it might help your decision to know that in 2000, <emphasis>AES</emphasis> was chosen by the American National Institute of Standards and Technology as the standard encryption algorithm for protecting sensitive information in the 21st century."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:1960
+#: using-d-i.xml:2001
 #, no-c-format
 msgid "Key size: <userinput>256</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1962
+#: using-d-i.xml:2003
 #, no-c-format
 msgid "Here you can specify the length of the encryption key. With a larger key size, the strength of the encryption is generally improved. On the other hand, increasing the length of the key usually has a negative impact on performance. Available key sizes vary depending on the cipher."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:1974
+#: using-d-i.xml:2015
 #, no-c-format
-msgid "IV algorithm: <userinput>cbc-essiv:sha256</userinput>"
+msgid "IV algorithm: <userinput>xts-plain64</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1976
+#: using-d-i.xml:2017
 #, no-c-format
 msgid "The <firstterm>Initialization Vector</firstterm> or <firstterm>IV</firstterm> algorithm is used in cryptography to ensure that applying the cipher on the same <firstterm>clear text</firstterm> data with the same key always produces a unique <firstterm>cipher text</firstterm>. The idea is to prevent the attacker from deducing information from repeated patterns in the encrypted data."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1986
+#: using-d-i.xml:2027
 #, no-c-format
-msgid "From the provided alternatives, the default <userinput>cbc-essiv:sha256</userinput> is currently the least vulnerable to known attacks. Use the other alternatives only when you need to ensure compatibility with some previously installed system that is not able to use newer algorithms."
+msgid "From the provided alternatives, the default <userinput>xts-plain64</userinput> is currently the least vulnerable to known attacks. Use the other alternatives only when you need to ensure compatibility with some previously installed system that is not able to use newer algorithms."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:1998
+#: using-d-i.xml:2039
 #, no-c-format
 msgid "Encryption key: <userinput>Passphrase</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2000
+#: using-d-i.xml:2041
 #, no-c-format
 msgid "Here you can choose the type of the encryption key for this partition."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:2006
+#: using-d-i.xml:2047
 #, no-c-format
 msgid "Passphrase"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2007
+#: using-d-i.xml:2048
 #, no-c-format
 msgid "The encryption key will be computed<footnote> <para> Using a passphrase as the key currently means that the partition will be set up using <ulink url=\"&url-luks;\">LUKS</ulink>. </para></footnote> on the basis of a passphrase which you will be able to enter later in the process."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:2022 using-d-i.xml:2115
+#: using-d-i.xml:2063
 #, no-c-format
 msgid "Random key"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2023
+#: using-d-i.xml:2064
 #, no-c-format
 msgid "A new encryption key will be generated from random data each time you try to bring up the encrypted partition. In other words: on every shutdown the content of the partition will be lost as the key is deleted from memory. (Of course, you could try to guess the key with a brute force attack, but unless there is an unknown weakness in the cipher algorithm, it is not achievable in our lifetime.)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2032
+#: using-d-i.xml:2073
 #, no-c-format
 msgid "Random keys are useful for swap partitions because you do not need to bother yourself with remembering the passphrase or wiping sensitive information from the swap partition before shutting down your computer. However, it also means that you will <emphasis>not</emphasis> be able to use the <quote>suspend-to-disk</quote> functionality offered by newer Linux kernels as it will be impossible (during a subsequent boot) to recover the suspended data written to the swap partition."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:2051 using-d-i.xml:2128
+#: using-d-i.xml:2092
 #, no-c-format
 msgid "Erase data: <userinput>yes</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2053
-#, no-c-format
-msgid "Determines whether the content of this partition should be overwritten with random data before setting up the encryption. This is recommended because it might otherwise be possible for an attacker to discern which parts of the partition are in use and which are not. In addition, this will make it harder to recover any leftover data from previous installations<footnote><para> It is believed that the guys from three-letter agencies can restore the data even after several rewrites of the magnetooptical media, though. </para></footnote>."
-msgstr ""
-
-#. Tag: para
-#: using-d-i.xml:2073
-#, no-c-format
-msgid "If you select <menuchoice> <guimenu>Encryption method:</guimenu> <guimenuitem>Loopback (loop-AES)</guimenuitem> </menuchoice>, the menu changes to provide the following options:"
-msgstr ""
-
-#. Tag: term
-#: using-d-i.xml:2082
-#, no-c-format
-msgid "Encryption: <userinput>AES256</userinput>"
-msgstr ""
-
-#. Tag: para
-#: using-d-i.xml:2084
-#, no-c-format
-msgid "For loop-AES, unlike dm-crypt, the options for cipher and key size are combined, so you can select both at the same time. Please see the above sections on ciphers and key sizes for further information."
-msgstr ""
-
-#. Tag: term
 #: using-d-i.xml:2094
 #, no-c-format
-msgid "Encryption key: <userinput>Keyfile (GnuPG)</userinput>"
-msgstr ""
-
-#. Tag: para
-#: using-d-i.xml:2096
-#, no-c-format
-msgid "Here you can select the type of the encryption key for this partition."
-msgstr ""
-
-#. Tag: term
-#: using-d-i.xml:2102
-#, no-c-format
-msgid "Keyfile (GnuPG)"
-msgstr ""
-
-#. Tag: para
-#: using-d-i.xml:2103
-#, no-c-format
-msgid "The encryption key will be generated from random data during the installation. Moreover this key will be encrypted with <application>GnuPG</application>, so to use it, you will need to enter the proper passphrase (you will be asked to provide one later in the process)."
-msgstr ""
-
-#. Tag: para
-#: using-d-i.xml:2116
-#, no-c-format
-msgid "Please see the section on random keys above."
-msgstr ""
-
-#. Tag: para
-#: using-d-i.xml:2130
-#, no-c-format
-msgid "Please see the section on erasing data above."
+msgid "Determines whether the content of this partition should be overwritten with random data before setting up the encryption. This is recommended because it might otherwise be possible for an attacker to discern which parts of the partition are in use and which are not. In addition, this will make it harder to recover any leftover data from previous installations<footnote><para> It is believed that the guys from three-letter agencies can restore the data even after several rewrites of the magnetooptical media, though. </para></footnote>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2139
+#: using-d-i.xml:2115
 #, no-c-format
 msgid "After you have selected the desired parameters for your encrypted partitions, return back to the main partitioning menu. There should now be a new menu item called <guimenu>Configure encrypted volumes</guimenu>. After you select it, you will be asked to confirm the deletion of data on partitions marked to be erased and possibly other actions such as writing a new partition table. For large partitions this might take some time."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2149
+#: using-d-i.xml:2125
 #, no-c-format
 msgid "Next you will be asked to enter a passphrase for partitions configured to use one. Good passphrases should be longer than 8 characters, should be a mixture of letters, numbers and other characters and should not contain common dictionary words or information easily associable with you (such as birthdates, hobbies, pet names, names of family members or relatives, etc.)."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2158
+#: using-d-i.xml:2134
 #, no-c-format
 msgid "Before you input any passphrases, you should have made sure that your keyboard is configured correctly and generates the expected characters. If you are unsure, you can switch to the second virtual console and type some text at the prompt. This ensures that you won't be surprised later, e.g. by trying to input a passphrase using a qwerty keyboard layout when you used an azerty layout during the installation. This situation can have several causes. Maybe you switched to another keyboard layout during the installation, or the selected keyboard layout might not have been set up yet when entering the passphrase for the root file system."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2171
+#: using-d-i.xml:2147
 #, no-c-format
 msgid "If you selected to use methods other than a passphrase to create encryption keys, they will be generated now. Because the kernel may not have gathered a sufficient amount of entropy at this early stage of the installation, the process may take a long time. You can help speed up the process by generating entropy: e.g. by pressing random keys, or by switching to the shell on the second virtual console and generating some network and disk traffic (downloading some files, feeding big files into <filename>/dev/null</filename>, etc.). This will be repeated for each partition to be encrypted."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2187
+#: using-d-i.xml:2163
 #, no-c-format
 msgid ""
-      "After returning to the main partitioning menu, you will see all encrypted volumes as additional partitions which can be configured in the same way as ordinary partitions. The following example shows two different volumes. The first one is encrypted via dm-crypt, the second one via loop-AES. <informalexample><screen>\n"
+      "After returning to the main partitioning menu, you will see all encrypted volumes as additional partitions which can be configured in the same way as ordinary partitions. The following example shows a volume encrypted via dm-crypt. <informalexample><screen>\n"
       "Encrypted volume (<replaceable>sda2_crypt</replaceable>) - 115.1 GB Linux device-mapper\n"
       "     #1 115.1 GB  F ext3\n"
-      "\n"
-      "Loopback (<replaceable>loop0</replaceable>) - 515.2 MB AES256 keyfile\n"
-      "     #1 515.2 MB  F ext3\n"
       "</screen></informalexample> Now is the time to assign mount points to the volumes and optionally change the file system types if the defaults do not suit you."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2200
+#: using-d-i.xml:2175
 #, no-c-format
-msgid "Pay attention to the identifiers in parentheses (<replaceable>sda2_crypt</replaceable> and <replaceable>loop0</replaceable> in this case) and the mount points you assigned to each encrypted volume. You will need this information later when booting the new system. The differences between the ordinary boot process and the boot process with encryption involved will be covered later in <xref linkend=\"mount-encrypted-volumes\"/>."
+msgid "Pay attention to the identifiers in parentheses (<replaceable>sda2_crypt</replaceable> in this case) and the mount points you assigned to each encrypted volume. You will need this information later when booting the new system. The differences between the ordinary boot process and the boot process with encryption involved will be covered later in <xref linkend=\"mount-encrypted-volumes\"/>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2210
+#: using-d-i.xml:2185
 #, no-c-format
 msgid "Once you are satisfied with the partitioning scheme, continue with the installation."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2221
+#: using-d-i.xml:2196
 #, no-c-format
 msgid "Installing the Base System"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2222
+#: using-d-i.xml:2197
 #, no-c-format
 msgid "Although this stage is the least problematic, it consumes a significant fraction of the install because it downloads, verifies and unpacks the whole base system. If you have a slow computer or network connection, this could take some time."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2235
+#: using-d-i.xml:2210
 #, no-c-format
 msgid "During installation of the base system, package unpacking and setup messages are redirected to <userinput>tty4</userinput>. You can access this terminal by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo>; get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2244
+#: using-d-i.xml:2219
 #, no-c-format
 msgid "The unpack/setup messages generated during this phase are also saved in <filename>/var/log/syslog</filename>. You can check them there if the installation is performed over a serial console."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2250
+#: using-d-i.xml:2225
 #, no-c-format
 msgid "As part of the installation, a &arch-kernel; kernel will be installed. At the default priority, the installer will choose one for you that best matches your hardware. In lower priority modes, you will be able to choose from a list of available kernels."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2257
+#: using-d-i.xml:2232
 #, no-c-format
 msgid "When packages are installed using the package management system, it will by default also install packages that are recommended by those packages. Recommended packages are not strictly required for the core functionality of the selected software, but they do enhance that software and should, in the view of the package maintainers, normally be installed together with that software."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2267
+#: using-d-i.xml:2242
 #, no-c-format
 msgid "For technical reasons packages installed during the installation of the base system are installed without their <quote>Recommends</quote>. The rule described above only takes effect after this point in the installation process."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2279
+#: using-d-i.xml:2254
 #, no-c-format
 msgid "Installing Additional Software"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2280
+#: using-d-i.xml:2255
 #, no-c-format
 msgid "At this point you have a usable but limited system. Most users will want to install additional software on the system to tune it to their needs, and the installer allows you do so. This step can take even longer than installing the base system if you have a slow computer or network connection."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2295
+#: using-d-i.xml:2270
 #, no-c-format
 msgid "Configuring apt"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2297
+#: using-d-i.xml:2272
 #, no-c-format
-msgid "One of the tools used to install packages on a &debian-gnu; system is a program called <command>apt-get</command>, from the <classname>apt</classname> package<footnote> <para> Note that the program which actually installs the packages is called <command>dpkg</command>. However, this program is more of a low-level tool. <command>apt-get</command> is a higher-level tool, which will invoke <command>dpkg</command> as appropriate. It knows how to retrieve packages from your CD, the network, or wherever. It is also able to automatically install other packages which are required to make the package you're trying to install work correctly. </para> </footnote>. Other front-ends for package management, like <command>aptitude</command> and <command>synaptic</command>, are also in use. These front-ends are recommended for new users, since they integrate some additional features (package searching and status checks) in a nice user interface. In fact, <command>aptitude</command> is now the recommended utility for package management."
+msgid "One of the tools used to install packages on a &debian-gnu; system is a program called <command>apt-get</command>, from the <classname>apt</classname> package<footnote> <para> Note that the program which actually installs the packages is called <command>dpkg</command>. However, this program is more of a low-level tool. <command>apt-get</command> is a higher-level tool, which will invoke <command>dpkg</command> as appropriate. It knows how to retrieve packages from your CD, the network, or wherever. It is also able to automatically install other packages which are required to make the package you're trying to install work correctly. </para> </footnote>. Other front-ends for package management, like <command>aptitude</command> and <command>synaptic</command>, are also in use. These front-ends are recommended for new users, since they integrate some additional features (package searching and status checks) in a nice user interface."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2321
+#: using-d-i.xml:2295
 #, no-c-format
 msgid "<command>apt</command> must be configured so that it knows from where to retrieve packages. The results of this configuration are written to the file <filename>/etc/apt/sources.list</filename>. You can examine and edit this file to your liking after the installation is complete."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2328
+#: using-d-i.xml:2302
 #, no-c-format
 msgid "If you are installing at default priority, the installer will largely take care of the configuration automatically, based on the installation method you are using and possibly using choices made earlier in the installation. In most cases the installer will automatically add a security mirror and, if you are installing the stable distribution, a mirror for the <quote>stable-updates</quote> service."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2337
+#: using-d-i.xml:2311
 #, no-c-format
 msgid "If you are installing at a lower priority (e.g. in expert mode), you will be able to make more decisions yourself. You can choose whether or not to use the security and/or stable-updates services, and you can choose to add packages from the <quote>contrib</quote> and <quote>non-free</quote> sections of the archive."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2348
+#: using-d-i.xml:2322
 #, no-c-format
 msgid "Installing from more than one CD or DVD"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2350
+#: using-d-i.xml:2324
 #, no-c-format
 msgid "If you are installing from a CD or a DVD that is part of a larger set, the installer will ask if you want to scan additional CDs or DVDs. If you have additional CDs or DVDs available, you probably want to do this so the installer can use the packages included on them."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2357
+#: using-d-i.xml:2331
 #, no-c-format
 msgid "If you do not have any additional CDs or DVDs, that is no problem: using them is not required. If you also do not use a network mirror (as explained in the next section), it can mean that not all packages belonging to the tasks you select in the next step of the installation can be installed."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2365
+#: using-d-i.xml:2339
 #, no-c-format
 msgid "Packages are included on CDs (and DVDs) in the order of their popularity. This means that for most uses only the first CDs in a set are needed and that only very few people actually use any of the packages included on the last CDs in a set."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2372
+#: using-d-i.xml:2346
 #, no-c-format
 msgid "It also means that buying or downloading and burning a full CD set is just a waste of money as you'll never use most of them. In most cases you are better off getting only the first 3 to 8 CDs and installing any additional packages you may need from the Internet by using a mirror. The same goes for DVD sets: the first DVD, or maybe the first two DVDs will cover most needs."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2382
+#: using-d-i.xml:2356
 #, no-c-format
 msgid "If you do scan multiple CDs or DVDs, the installer will prompt you to exchange them when it needs packages from another CD/DVD than the one currently in the drive. Note that only CDs or DVDs that belong to the same set should be scanned. The order in which they are scanned does not really matter, but scanning them in ascending order will reduce the chance of mistakes."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2395
+#: using-d-i.xml:2369
 #, no-c-format
 msgid "Using a network mirror"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2397
+#: using-d-i.xml:2371
 #, no-c-format
 msgid "One question that will be asked during most installs is whether or not to use a network mirror as a source for packages. In most cases the default answer should be fine, but there are some exceptions."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2403
+#: using-d-i.xml:2377
 #, no-c-format
 msgid "If you are <emphasis>not</emphasis> installing from a full CD or DVD or using a full CD/DVD image, you really should use a network mirror as otherwise you will end up with only a very minimal system. However, if you have a limited Internet connection it is best <emphasis>not</emphasis> to select the <literal>desktop</literal> task in the next step of the installation."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2412
+#: using-d-i.xml:2386
 #, no-c-format
 msgid "If you are installing from a single full CD or using a full CD image, using a network mirror is not required, but is still strongly recommended because a single CD contains only a fairly limited number of packages. If you have a limited Internet connection it may still be best to <emphasis>not</emphasis> select a network mirror here, but to finish the installation using only what's available on the CD and selectively install additional packages after the installation (i.e. after you have rebooted into the new system)."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2423
+#: using-d-i.xml:2397
 #, no-c-format
 msgid "If you are installing from a DVD or using a DVD image, any packages needed during the installation should be present on the first DVD. The same is true if you have scanned multiple CDs as explained in the previous section. Use of a network mirror is optional."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2430
+#: using-d-i.xml:2404
 #, no-c-format
 msgid "One advantage of adding a network mirror is that updates that have occurred since the CD/DVD set was created and have been included in a point release, will become available for installation, thus extending the life of your CD/DVD set without compromising the security or stability of the installed system."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2437
+#: using-d-i.xml:2411
 #, no-c-format
 msgid "In summary: selecting a network mirror is generally a good idea, except if you do not have a good Internet connection. If the current version of a package is available from CD/DVD, the installer will always use that. The amount of data that will be downloaded if you do select a mirror thus depends on"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2446
+#: using-d-i.xml:2420
 #, no-c-format
 msgid "the tasks you select in the next step of the installation,"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2451
+#: using-d-i.xml:2425
 #, no-c-format
 msgid "which packages are needed for those tasks,"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2456
+#: using-d-i.xml:2430
 #, no-c-format
 msgid "which of those packages are present on the CDs or DVDs you have scanned, and"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2461
+#: using-d-i.xml:2435
 #, no-c-format
 msgid "whether any updated versions of packages included on the CDs or DVDs are available from a mirror (either a regular package mirror, or a mirror for security or stable-updates)."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2470
+#: using-d-i.xml:2444
 #, no-c-format
 msgid "Note that the last point means that, even if you choose not to use a network mirror, some packages may still be downloaded from the Internet if there is a security or stable-updates update available for them and those services have been configured."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2481
+#: using-d-i.xml:2455
 #, no-c-format
 msgid "Choosing a network mirror"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2482
+#: using-d-i.xml:2456
 #, no-c-format
 msgid "If you have selected to use a network mirror during the installation (optional for CD/DVD installs, required for netboot images), you will be presented with a list of geographically nearby (and therefore hopefully fast) network mirrors, based upon your country selection earlier in the installation process. Choosing the offered default is usually fine."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2490
+#: using-d-i.xml:2464
 #, no-c-format
 msgid "A mirror can also be specified by hand by choosing <quote>enter information manually</quote> . You can then specify a mirror host name and an optional port number. As of Wheezy, that actually has to be a URL base, i.e. when specifying an IPv6 address, one has to add square brackets around it, for instance <quote>[2001:db8::1]</quote>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2498
+#: using-d-i.xml:2472
 #, no-c-format
 msgid "If your computer is on an IPv6-only network (which is probably not the case for the vast majority of users), using the default mirror for your country might not work. All the mirrors in the list are reachable via IPv4, but only some of them can be used via IPv6. As connectivity of individual mirrors can change over time, this information is not available in the installer. If there is no IPv6 connectivity for the default mirror for your country, you can either try some of the other mirrors offered to you or choose the <quote>enter information manually</quote> option. You can then specify <quote>ftp.ipv6.debian.org</quote> as the mirror name, which is an alias for a mirror available via IPv6, although it will probably not be the fastest possible one."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2512
+#: using-d-i.xml:2486
 #, no-c-format
 msgid "Another option when choosing to specify the mirror manually is to use <quote>http.debian.net</quote> as your mirror. <quote>http.debian.net</quote> is not a physical mirror but a mirror redirection service, i.e. it automatically refers your system to a real mirror near you in terms of network topology. It takes into account by which protocol you connect to it, i.e. if you use IPv6, it will refer you to an IPv6-capable mirror near you."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2531
+#: using-d-i.xml:2505
 #, no-c-format
 msgid "Selecting and Installing Software"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2533
+#: using-d-i.xml:2507
 #, no-c-format
 msgid "During the installation process, you are given the opportunity to select additional software to install. Rather than picking individual software packages from the &num-of-distrib-pkgs; available packages, this stage of the installation process focuses on selecting and installing predefined collections of software to quickly set up your computer to perform various tasks."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2542
+#: using-d-i.xml:2516
 #, no-c-format
 msgid "So, you have the ability to choose <emphasis>tasks</emphasis> first, and then add on more individual packages later. These tasks loosely represent a number of different jobs or things you want to do with your computer, such as <quote>Desktop environment</quote>, <quote>Web server</quote>, or <quote>Print server</quote><footnote> <para> You should know that to present this list, the installer is merely invoking the <command>tasksel</command> program. It can be run at any time after installation to install more packages (or remove them), or you can use a more fine-grained tool such as <command>aptitude</command>. If you are looking for a specific single package, after installation is complete, simply run <userinput>aptitude install <replaceable>package</replaceable></userinput>, where <replaceable>package</replaceable> is the name of the package you are looking for. </para> </footnote>. <xref linkend=\"tasksel-size-list\"/> lists the space requirements for the available tasks."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2569
+#: using-d-i.xml:2543
 #, no-c-format
 msgid "Some tasks may be pre-selected based on the characteristics of the computer you are installing. If you disagree with these selections you can deselect them. You can even opt to install no tasks at all at this point."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2576
+#: using-d-i.xml:2550
 #, no-c-format
 msgid "In the standard user interface of the installer, you can use the space bar to toggle selection of a task."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2582
+#: using-d-i.xml:2556
 #, no-c-format
 msgid "The <quote>Desktop environment</quote> task will install a graphical desktop environment."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2587
+#: 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>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2601
+#: 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:2612
+#: using-d-i.xml:2586
 #, 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:2622
+#: using-d-i.xml:2596
 #, 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>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2633
+#: using-d-i.xml:2607
 #, 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:2641
+#: using-d-i.xml:2615
 #, 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:2651
+#: using-d-i.xml:2625
 #, 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:2658
+#: using-d-i.xml:2632
 #, 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:2667
+#: using-d-i.xml:2641
 #, 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:2682
+#: using-d-i.xml:2656
 #, no-c-format
 msgid "Making Your System Bootable"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2684
+#: using-d-i.xml:2658
 #, 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:2699
+#: using-d-i.xml:2673
 #, no-c-format
 msgid "Detecting other operating systems"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2701
+#: using-d-i.xml:2675
 #, 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:2709
+#: using-d-i.xml:2683
 #, 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:2727
+#: using-d-i.xml:2701
 #, no-c-format
 msgid "<command>palo</command>-installer"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2728
+#: using-d-i.xml:2702
 #, 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:2737
+#: using-d-i.xml:2711
 #, no-c-format
 msgid "hppa FIXME ( need more info )"
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2749
+#: using-d-i.xml:2723
 #, no-c-format
 msgid "Install the <command>Grub</command> Boot Loader on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2751
+#: using-d-i.xml:2725
 #, 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:2757
+#: using-d-i.xml:2731
 #, 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:2763
+#: using-d-i.xml:2737
 #, 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:2776
+#: using-d-i.xml:2750
 #, no-c-format
 msgid "Install the <command>LILO</command> Boot Loader on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2778
+#: using-d-i.xml:2752
 #, 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:2788
+#: using-d-i.xml:2762
 #, 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:2796
+#: using-d-i.xml:2770
 #, 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:2803
+#: using-d-i.xml:2777
 #, no-c-format
 msgid "Master Boot Record (MBR)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2803
+#: using-d-i.xml:2777
 #, 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:2810
+#: using-d-i.xml:2784
 #, no-c-format
 msgid "new &debian; partition"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2810
+#: using-d-i.xml:2784
 #, 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:2819
+#: using-d-i.xml:2793
 #, no-c-format
 msgid "Other choice"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2819
+#: using-d-i.xml:2793
 #, 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:2829
+#: using-d-i.xml:2803
 #, 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:2845
+#: using-d-i.xml:2819
 #, no-c-format
 msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2847
+#: using-d-i.xml:2821
 #, 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:2863
+#: using-d-i.xml:2837
 #, 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:2875
+#: using-d-i.xml:2849
 #, no-c-format
 msgid "Choose the correct partition!"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2877
+#: using-d-i.xml:2851
 #, 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:2892
+#: using-d-i.xml:2866
 #, no-c-format
 msgid "EFI Partition Contents"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2894
+#: using-d-i.xml:2868
 #, 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:2916
+#: using-d-i.xml:2890
 #, no-c-format
 msgid "elilo.conf"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2917
+#: using-d-i.xml:2891
 #, 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:2926
+#: using-d-i.xml:2900
 #, no-c-format
 msgid "elilo.efi"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2927
+#: using-d-i.xml:2901
 #, 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:2937
+#: using-d-i.xml:2911
 #, no-c-format
 msgid "initrd.img"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2938
+#: using-d-i.xml:2912
 #, 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:2950
+#: using-d-i.xml:2924
 #, no-c-format
 msgid "readme.txt"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2951
+#: using-d-i.xml:2925
 #, 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:2961
+#: using-d-i.xml:2935
 #, no-c-format
 msgid "vmlinuz"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2962
+#: using-d-i.xml:2936
 #, 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:2982
+#: using-d-i.xml:2956
 #, no-c-format
 msgid "<command>arcboot</command>-installer"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2983
+#: using-d-i.xml:2957
 #, 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"
@@ -2407,289 +2386,289 @@ msgid ""
 msgstr ""
 
 #. Tag: replaceable
-#: using-d-i.xml:3002
+#: using-d-i.xml:2976
 #, no-c-format
 msgid "scsi"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3003
+#: using-d-i.xml:2977
 #, 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:3011
+#: using-d-i.xml:2985
 #, no-c-format
 msgid "disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3012
+#: using-d-i.xml:2986
 #, 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:3020
+#: using-d-i.xml:2994
 #, no-c-format
 msgid "partnr"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3021
+#: using-d-i.xml:2995
 #, 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:3029
+#: using-d-i.xml:3003
 #, no-c-format
 msgid "config"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3030
+#: using-d-i.xml:3004
 #, 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:3051
+#: using-d-i.xml:3025
 #, no-c-format
 msgid "Install <command>Yaboot</command> on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3052
+#: using-d-i.xml:3026
 #, 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:3070
+#: using-d-i.xml:3044
 #, no-c-format
 msgid "Install <command>Quik</command> on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3071
+#: using-d-i.xml:3045
 #, 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:3087
+#: using-d-i.xml:3061
 #, no-c-format
 msgid "<command>zipl</command>-installer"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3088
+#: using-d-i.xml:3062
 #, 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:3105
+#: using-d-i.xml:3079
 #, no-c-format
 msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3107
+#: using-d-i.xml:3081
 #, 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:3132
+#: using-d-i.xml:3106
 #, no-c-format
 msgid "Continue Without Boot Loader"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3134
+#: using-d-i.xml:3108
 #, 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:3141
+#: using-d-i.xml:3115
 #, 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:3158
+#: using-d-i.xml:3132
 #, no-c-format
 msgid "Finishing the Installation"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3159
+#: using-d-i.xml:3133
 #, 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:3172
+#: using-d-i.xml:3146
 #, no-c-format
 msgid "Setting the System Clock"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3174
+#: using-d-i.xml:3148
 #, 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:3181
+#: using-d-i.xml:3155
 #, 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:3192
+#: using-d-i.xml:3166
 #, 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:3207
+#: using-d-i.xml:3181
 #, no-c-format
 msgid "Reboot the System"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3209
+#: using-d-i.xml:3183
 #, 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:3215
+#: using-d-i.xml:3189
 #, 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:3228
+#: using-d-i.xml:3202
 #, no-c-format
 msgid "Troubleshooting"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3229
+#: using-d-i.xml:3203
 #, 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:3242
+#: using-d-i.xml:3216
 #, no-c-format
 msgid "Saving the installation logs"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3244
+#: using-d-i.xml:3218
 #, 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:3251
+#: using-d-i.xml:3225
 #, 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:3271
+#: using-d-i.xml:3245
 #, no-c-format
 msgid "Using the Shell and Viewing the Logs"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3273
+#: using-d-i.xml:3247
 #, 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:3291
+#: using-d-i.xml:3265
 #, no-c-format
 msgid "For the graphical installer see also <xref linkend=\"gtk-using\"/>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3295
+#: using-d-i.xml:3269
 #, 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:3303
+#: using-d-i.xml:3277
 #, 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:3312
+#: using-d-i.xml:3286
 #, 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:3319
+#: using-d-i.xml:3293
 #, 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:3325
+#: using-d-i.xml:3299
 #, 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:3341
+#: using-d-i.xml:3315
 #, no-c-format
 msgid "Installation Over the Network"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3343
+#: using-d-i.xml:3317
 #, 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:3353
+#: using-d-i.xml:3327
 #, 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:3366
+#: using-d-i.xml:3340
 #, 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:3371
+#: using-d-i.xml:3345
 #, 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:3383
+#: using-d-i.xml:3357
 #, 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:3389
+#: using-d-i.xml:3363
 #, 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"
@@ -2698,127 +2677,127 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3406
+#: using-d-i.xml:3380
 #, 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:3419
+#: using-d-i.xml:3393
 #, 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:3432
+#: using-d-i.xml:3406
 #, 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:3448
+#: using-d-i.xml:3422
 #, 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:3458
+#: using-d-i.xml:3432
 #, 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:3477
+#: using-d-i.xml:3451
 #, no-c-format
 msgid "Loading Missing Firmware"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3478
+#: using-d-i.xml:3452
 #, 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:3486
+#: using-d-i.xml:3460
 #, 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:3496
+#: using-d-i.xml:3470
 #, 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:3506
+#: using-d-i.xml:3480
 #, 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:3512
+#: using-d-i.xml:3486
 #, 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:3526
+#: using-d-i.xml:3500
 #, no-c-format
 msgid "Preparing a medium"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3527
+#: using-d-i.xml:3501
 #, 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:3540
+#: using-d-i.xml:3514
 #, 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:3554
+#: using-d-i.xml:3528
 #, 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:3568
+#: using-d-i.xml:3542
 #, 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:3577
+#: using-d-i.xml:3551
 #, no-c-format
 msgid "Firmware and the Installed System"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3578
+#: using-d-i.xml:3552
 #, 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:3587
+#: using-d-i.xml:3561
 #, 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:3595
+#: using-d-i.xml:3569
 #, 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:3602
+#: using-d-i.xml:3576
 #, 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 ""