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

2 files changed, 281 insertions, 239 deletions

diff --git a/po/pot/preseed.pot b/po/pot/preseed.pot
index 065edfe33..5548831af 100644
--- a/po/pot/preseed.pot
+++ b/po/pot/preseed.pot
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2008-09-10 00:09+0000\n"
+"POT-Creation-Date: 2008-09-26 00:09+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"
@@ -994,7 +994,7 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:835
 #, no-c-format
-msgid "You can also use preseeding to set up partitions on software RAID arrays. Supported are RAID levels 0, 1 and 5, creating degraded arrays and specifying spare devices. If you are using RAID 1, you can preseed grub to install to all devices used in the array; see <xref linkend=\"preseed-bootloader\"/>."
+msgid "You can also use preseeding to set up partitions on software RAID arrays. Supported are RAID levels 0, 1, 5, 6 and 10, creating degraded arrays and specifying spare devices. If you are using RAID 1, you can preseed grub to install to all devices used in the array; see <xref linkend=\"preseed-bootloader\"/>."
 msgstr ""
 
 #. Tag: para
@@ -1040,7 +1040,7 @@ msgid ""
       "# Parameters are:\n"
       "# &lt;raidtype&gt; &lt;devcount&gt; &lt;sparecount&gt; &lt;fstype&gt; &lt;mountpoint&gt; \\\n"
       "#          &lt;devices&gt; &lt;sparedevices&gt;\n"
-      "# RAID levels 0, 1 and 5 are supported; devices are separated using \"#\"\n"
+      "# RAID levels 0, 1, 5, 6 and 10 are supported; devices are separated using \"#\"\n"
       "#d-i partman-auto-raid/recipe string \\\n"
       "#    1 2 0 ext3 /                                           \\\n"
       "#          /dev/discs/disc0/part1#/dev/discs/disc1/part1    \\\n"
diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot
index 0dcbf99f1..6adfabf8a 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: 2008-05-30 00:09+0000\n"
+"POT-Creation-Date: 2008-09-26 00:09+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"
@@ -961,479 +961,521 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1168
 #, 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> </variablelist> To sum it up:"
+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:1246
+#: using-d-i.xml:1282
 #, no-c-format
 msgid "Type"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1247
+#: using-d-i.xml:1283
 #, no-c-format
 msgid "Minimum Devices"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1248
+#: using-d-i.xml:1284
 #, no-c-format
 msgid "Spare Device"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1249
+#: using-d-i.xml:1285
 #, no-c-format
 msgid "Survives disk failure?"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1250
+#: using-d-i.xml:1286
 #, no-c-format
 msgid "Available Space"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1256
+#: using-d-i.xml:1292
 #, no-c-format
 msgid "RAID0"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1257 using-d-i.xml:1265
+#: using-d-i.xml:1293 using-d-i.xml:1301 using-d-i.xml:1331
 #, no-c-format
 msgid "<entry>2</entry>"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1258 using-d-i.xml:1259
+#: using-d-i.xml:1294 using-d-i.xml:1295
 #, no-c-format
 msgid "<entry>no</entry>"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1260
+#: using-d-i.xml:1296
 #, no-c-format
 msgid "Size of the smallest partition multiplied by number of devices in RAID"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1264
+#: using-d-i.xml:1300
 #, no-c-format
 msgid "RAID1"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1266 using-d-i.xml:1274
+#: using-d-i.xml:1302 using-d-i.xml:1310 using-d-i.xml:1321 using-d-i.xml:1332
 #, no-c-format
 msgid "optional"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1267 using-d-i.xml:1275
+#: using-d-i.xml:1303 using-d-i.xml:1311 using-d-i.xml:1322 using-d-i.xml:1333
 #, no-c-format
 msgid "<entry>yes</entry>"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1268
+#: using-d-i.xml:1304
 #, no-c-format
 msgid "Size of the smallest partition in RAID"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1272
+#: using-d-i.xml:1308
 #, no-c-format
 msgid "RAID5"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1273
+#: using-d-i.xml:1309
 #, no-c-format
 msgid "<entry>3</entry>"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1276
+#: using-d-i.xml:1312
 #, 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:1319
+#, no-c-format
+msgid "RAID6"
+msgstr ""
+
+#. Tag: entry
+#: using-d-i.xml:1320
+#, no-c-format
+msgid "<entry>4</entry>"
+msgstr ""
+
+#. Tag: entry
+#: using-d-i.xml:1323
+#, 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:1330
+#, no-c-format
+msgid "RAID10"
+msgstr ""
+
+#. Tag: entry
+#: using-d-i.xml:1334
+#, 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:1284
+#: using-d-i.xml:1341
 #, 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:1289
+#: using-d-i.xml:1346
 #, no-c-format
 msgid "To create a 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:1298
+#: using-d-i.xml:1355
 #, 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:1310
+#: using-d-i.xml:1367
 #, 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:1319
+#: using-d-i.xml:1376
 #, 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:1332
+#: using-d-i.xml:1389
 #, 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:1339
+#: using-d-i.xml:1396
 #, 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 few seconds ago. Don't worry. If you make a mistake and select different number of partitions, the &d-i; won't let you continue until you correct the issue."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1351
+#: using-d-i.xml:1408
 #, no-c-format
 msgid "RAID5 has a similar setup procedure as RAID1 with the exception that you need to use at least <emphasis>three</emphasis> active partitions."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1359
+#: using-d-i.xml:1414
+#, no-c-format
+msgid "RAID6 also has a similar setup procedure as RAID1 except thatat least <emphasis>four</emphasis> active partitions are required."
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:1420
+#, no-c-format
+msgid "RAID10 again has a similar setup procedure as 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:1434
 #, 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:1368
+#: using-d-i.xml:1443
 #, no-c-format
 msgid "After you setup 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:1383
+#: using-d-i.xml:1458
 #, no-c-format
 msgid "Configuring the Logical Volume Manager (LVM)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1384
+#: using-d-i.xml:1459
 #, 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 with moving stuff around, symlinking, etc."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1392
+#: using-d-i.xml:1467
 #, 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:1402
+#: using-d-i.xml:1477
 #, 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:1413
+#: using-d-i.xml:1488
 #, 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:1422
+#: using-d-i.xml:1497
 #, 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:1433
+#: using-d-i.xml:1508
 #, 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:1438
+#: using-d-i.xml:1513
 #, no-c-format
 msgid "Create volume group"
 msgstr ""
 
 #. Tag: guimenuitem
-#: using-d-i.xml:1441
+#: using-d-i.xml:1516
 #, no-c-format
 msgid "Create logical volume"
 msgstr ""
 
 #. Tag: guimenuitem
-#: using-d-i.xml:1444
+#: using-d-i.xml:1519
 #, no-c-format
 msgid "Delete volume group"
 msgstr ""
 
 #. Tag: guimenuitem
-#: using-d-i.xml:1447
+#: using-d-i.xml:1522
 #, no-c-format
 msgid "Delete logical volume"
 msgstr ""
 
 #. Tag: guimenuitem
-#: using-d-i.xml:1450
+#: using-d-i.xml:1525
 #, no-c-format
 msgid "Extend volume group"
 msgstr ""
 
 #. Tag: guimenuitem
-#: using-d-i.xml:1453
+#: using-d-i.xml:1528
 #, no-c-format
 msgid "Reduce volume group"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1455
+#: using-d-i.xml:1530
 #, no-c-format
 msgid "<guimenuitem>Finish</guimenuitem>: return to the main <command>partman</command> screen"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1461
+#: using-d-i.xml:1536
 #, 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:1466
+#: using-d-i.xml:1541
 #, 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:1480
+#: using-d-i.xml:1555
 #, no-c-format
 msgid "Configuring Encrypted Volumes"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1481
+#: using-d-i.xml:1556
 #, 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:1493
+#: using-d-i.xml:1568
 #, 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:1508
+#: using-d-i.xml:1583
 #, 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:1515
+#: using-d-i.xml:1590
 #, 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:1526
+#: using-d-i.xml:1601
 #, 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."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1538
+#: using-d-i.xml:1613
 #, 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."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:1548
+#: using-d-i.xml:1623
 #, no-c-format
 msgid "Encryption: <userinput>aes</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1550
+#: using-d-i.xml:1625
 #, 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:1568
+#: using-d-i.xml:1643
 #, no-c-format
 msgid "Key size: <userinput>256</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1570
+#: using-d-i.xml:1645
 #, 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:1582
+#: using-d-i.xml:1657
 #, no-c-format
 msgid "IV algorithm: <userinput>cbc-essiv:sha256</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1584
+#: using-d-i.xml:1659
 #, 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:1594
+#: using-d-i.xml:1669
 #, 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."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:1606
+#: using-d-i.xml:1681
 #, no-c-format
 msgid "Encryption key: <userinput>Passphrase</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1608
+#: using-d-i.xml:1683
 #, no-c-format
 msgid "Here you can choose the type of the encryption key for this partition."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:1614
+#: using-d-i.xml:1689
 #, no-c-format
 msgid "Passphrase"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1615
+#: using-d-i.xml:1690
 #, 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:1630 using-d-i.xml:1723
+#: using-d-i.xml:1705 using-d-i.xml:1798
 #, no-c-format
 msgid "Random key"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1631
+#: using-d-i.xml:1706
 #, 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:1640
+#: using-d-i.xml:1715
 #, 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:1659 using-d-i.xml:1736
+#: using-d-i.xml:1734 using-d-i.xml:1811
 #, no-c-format
 msgid "Erase data: <userinput>yes</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1661
+#: using-d-i.xml:1736
 #, 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:1681
+#: using-d-i.xml:1756
 #, 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:1690
+#: using-d-i.xml:1765
 #, no-c-format
 msgid "Encryption: <userinput>AES256</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1692
+#: using-d-i.xml:1767
 #, 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:1702
+#: using-d-i.xml:1777
 #, no-c-format
 msgid "Encryption key: <userinput>Keyfile (GnuPG)</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1704
+#: using-d-i.xml:1779
 #, no-c-format
 msgid "Here you can select the type of the encryption key for this partition."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:1710
+#: using-d-i.xml:1785
 #, no-c-format
 msgid "Keyfile (GnuPG)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1711
+#: using-d-i.xml:1786
 #, 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:1724
+#: using-d-i.xml:1799
 #, no-c-format
 msgid "Please see the section on random keys above."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1738
+#: using-d-i.xml:1813
 #, no-c-format
 msgid "Please see the the section on erasing data above."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1747
+#: using-d-i.xml:1822
 #, 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:1757
+#: using-d-i.xml:1832
 #, 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:1766
+#: using-d-i.xml:1841
 #, 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:1779
+#: using-d-i.xml:1854
 #, 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:1795
+#: using-d-i.xml:1870
 #, 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"
@@ -1446,607 +1488,607 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1808
+#: using-d-i.xml:1883
 #, no-c-format
 msgid "One thing to note here are 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 ordinary boot process and boot process with encryption involved will be covered later in <xref linkend=\"mount-encrypted-volumes\"/>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1818
+#: using-d-i.xml:1893
 #, no-c-format
 msgid "Once you are satisfied with the partitioning scheme, continue with the installation."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:1829
+#: using-d-i.xml:1904
 #, no-c-format
 msgid "Installing the Base System"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1830
+#: using-d-i.xml:1905
 #, 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:1843
+#: using-d-i.xml:1918
 #, 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:1852
+#: using-d-i.xml:1927
 #, 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:1858
+#: using-d-i.xml:1933
 #, no-c-format
 msgid "As part of the installation, a Linux 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: title
-#: using-d-i.xml:1870
+#: using-d-i.xml:1945
 #, no-c-format
 msgid "Setting Up Users And Passwords"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1871
+#: using-d-i.xml:1946
 #, no-c-format
 msgid "After the base system has been installed, 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:1885
+#: using-d-i.xml:1960
 #, no-c-format
 msgid "Set the Root Password"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1889
+#: using-d-i.xml:1964
 #, 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:1897
+#: using-d-i.xml:1972
 #, 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:1905
+#: using-d-i.xml:1980
 #, 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:1915
+#: using-d-i.xml:1990
 #, no-c-format
 msgid "Create an Ordinary User"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1917
+#: using-d-i.xml:1992
 #, 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:1926
+#: using-d-i.xml:2001
 #, 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:1936
+#: using-d-i.xml:2011
 #, 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:1943
+#: using-d-i.xml:2018
 #, 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:1954
+#: using-d-i.xml:2029
 #, no-c-format
 msgid "Installing Additional Software"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1955
+#: using-d-i.xml:2030
 #, 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:1970
+#: using-d-i.xml:2045
 #, no-c-format
 msgid "Configuring apt"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1972
+#: using-d-i.xml:2047
 #, no-c-format
 msgid "One of the tools used to install packages on a &debian; 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."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1996
+#: using-d-i.xml:2071
 #, 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:2003
+#: using-d-i.xml:2078
 #, 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>volatile</quote> update service."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2012
+#: using-d-i.xml:2087
 #, 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 volatile update 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:2023
+#: using-d-i.xml:2098
 #, no-c-format
 msgid "Installing from more than one CD or DVD"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2025
+#: using-d-i.xml:2100
 #, 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:2032
+#: using-d-i.xml:2107
 #, 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:2040
+#: using-d-i.xml:2115
 #, 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:2047
+#: using-d-i.xml:2122
 #, 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:2056
+#: using-d-i.xml:2131
 #, no-c-format
 msgid "A good rule of thumb is that for a regular desktop installation (using the GNOME desktop environment) only the first three CDs are needed. For the alternative desktop environments (KDE or Xfce), additional CDs are needed. The first DVD easily covers all three desktop environments."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2064
+#: using-d-i.xml:2139
 #, 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:2077
+#: using-d-i.xml:2152
 #, no-c-format
 msgid "Using a network mirror"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2079
+#: using-d-i.xml:2154
 #, 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:2085
+#: using-d-i.xml:2160
 #, 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:2094
+#: using-d-i.xml:2169
 #, 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:2105
+#: using-d-i.xml:2180
 #, 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:2112
+#: using-d-i.xml:2187
 #, 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:2119
+#: using-d-i.xml:2194
 #, 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:2128
+#: using-d-i.xml:2203
 #, no-c-format
 msgid "the tasks you select in the next step of the installation,"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2133
+#: using-d-i.xml:2208
 #, no-c-format
 msgid "which packages are needed for those tasks,"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2138
+#: using-d-i.xml:2213
 #, 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:2143
+#: using-d-i.xml:2218
 #, 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 volatile updates)."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2152
+#: using-d-i.xml:2227
 #, 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 volatile update available for them and those services have been configured."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2168
+#: using-d-i.xml:2243
 #, no-c-format
 msgid "Selecting and Installing Software"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2170
+#: using-d-i.xml:2245
 #, 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:2179
+#: using-d-i.xml:2254
 #, 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:2206
+#: using-d-i.xml:2281
 #, 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:2213
+#: using-d-i.xml:2288
 #, no-c-format
 msgid "Unless you are using the special KDE or Xfce CDs, the <quote>Desktop environment</quote> task will install the GNOME desktop environment."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2220
+#: using-d-i.xml:2295
 #, no-c-format
 msgid "It is not possible to interactively select a different desktop during the installation. However, it <emphasis>is</emphasis> possible to get &d-i; to install a KDE desktop environment instead of GNOME by using preseeding (see <xref linkend=\"preseed-pkgsel\"/>) or by adding the parameter <literal>desktop=kde</literal> at the boot prompt when starting the installer. Alternatively the more lightweight Xfce desktop environment can be selected by using <literal>desktop=xfce</literal>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2230
+#: using-d-i.xml:2305
 #, no-c-format
 msgid "Note that this will only work if the packages needed for KDE or Xfce are actually available. If you are installing using a single full CD image, they will need to be downloaded from a mirror as most needed packages are only included on later CDs; installing KDE or Xfce this way should work fine if you are using a DVD image or any other installation method."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2238
+#: using-d-i.xml:2313
 #, 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>apache</classname>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2250
+#: using-d-i.xml:2325
 #, 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 tasks you've selected."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2257
+#: using-d-i.xml:2332
 #, 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:2263
+#: using-d-i.xml:2338
 #, 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:2272
+#: using-d-i.xml:2347
 #, 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: para
-#: using-d-i.xml:2281
+#: using-d-i.xml:2356
 #, no-c-format
 msgid "Each package you selected with <command>tasksel</command> is downloaded, unpacked and then installed in turn by the <command>apt-get</command> and <command>dpkg</command> programs. If a particular program needs more information from the user, it will prompt you during this process."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2294
+#: using-d-i.xml:2369
 #, no-c-format
 msgid "Making Your System Bootable"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2296
+#: using-d-i.xml:2371
 #, 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:2311
+#: using-d-i.xml:2386
 #, no-c-format
 msgid "Detecting other operating systems"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2313
+#: using-d-i.xml:2388
 #, 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:2321
+#: using-d-i.xml:2396
 #, 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:2339
+#: using-d-i.xml:2414
 #, no-c-format
 msgid "Install <command>aboot</command> on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2340
+#: using-d-i.xml:2415
 #, no-c-format
 msgid "If you have booted from SRM and you select this option, the installer will write <command>aboot</command> to the first sector of the disk on which you installed Debian. Be <emphasis>very</emphasis> careful &mdash; it is <emphasis>not</emphasis> possible to boot multiple operating systems (e.g. GNU/Linux, Free/Open/NetBSD, OSF/1 a.k.a. Digital Unix a.k.a. Tru64 Unix, or OpenVMS) from the same disk. If you also have a different operating system installed on the disk where you have installed Debian, you will have to boot GNU/Linux from a floppy instead."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2360
+#: using-d-i.xml:2435
 #, no-c-format
 msgid "<command>palo</command>-installer"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2361
+#: using-d-i.xml:2436
 #, 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:2370
+#: using-d-i.xml:2445
 #, no-c-format
 msgid "hppa FIXME ( need more info )"
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2382
+#: using-d-i.xml:2457
 #, no-c-format
 msgid "Install the <command>Grub</command> Boot Loader on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2384
+#: using-d-i.xml:2459
 #, 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:2390
+#: using-d-i.xml:2465
 #, 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:2396
+#: using-d-i.xml:2471
 #, 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:2409
+#: using-d-i.xml:2484
 #, no-c-format
 msgid "Install the <command>LILO</command> Boot Loader on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2411
+#: using-d-i.xml:2486
 #, 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:2421
+#: using-d-i.xml:2496
 #, 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:2429
+#: using-d-i.xml:2504
 #, 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:2436
+#: using-d-i.xml:2511
 #, no-c-format
 msgid "Master Boot Record (MBR)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2436
+#: using-d-i.xml:2511
 #, 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:2443
+#: using-d-i.xml:2518
 #, no-c-format
 msgid "new Debian partition"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2443
+#: using-d-i.xml:2518
 #, 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:2452
+#: using-d-i.xml:2527
 #, no-c-format
 msgid "Other choice"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2452
+#: using-d-i.xml:2527
 #, 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:2462
+#: using-d-i.xml:2537
 #, 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:2478
+#: using-d-i.xml:2553
 #, no-c-format
 msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2480
+#: using-d-i.xml:2555
 #, 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:2496
+#: using-d-i.xml:2571
 #, 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:2508
+#: using-d-i.xml:2583
 #, no-c-format
 msgid "Choose the correct partition!"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2510
+#: using-d-i.xml:2585
 #, no-c-format
 msgid "The criteria for selecting a partition is that it is 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:2525
+#: using-d-i.xml:2600
 #, no-c-format
 msgid "EFI Partition Contents"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2527
+#: using-d-i.xml:2602
 #, 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:2549
+#: using-d-i.xml:2624
 #, no-c-format
 msgid "elilo.conf"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2550
+#: using-d-i.xml:2625
 #, 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:2559
+#: using-d-i.xml:2634
 #, no-c-format
 msgid "elilo.efi"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2560
+#: using-d-i.xml:2635
 #, 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:2570
+#: using-d-i.xml:2645
 #, no-c-format
 msgid "initrd.img"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2571
+#: using-d-i.xml:2646
 #, 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:2583
+#: using-d-i.xml:2658
 #, no-c-format
 msgid "readme.txt"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2584
+#: using-d-i.xml:2659
 #, 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:2594
+#: using-d-i.xml:2669
 #, no-c-format
 msgid "vmlinuz"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2595
+#: using-d-i.xml:2670
 #, 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:2615
+#: using-d-i.xml:2690
 #, no-c-format
 msgid "<command>arcboot</command>-installer"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2616
+#: using-d-i.xml:2691
 #, 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"
@@ -2059,289 +2101,289 @@ msgid ""
 msgstr ""
 
 #. Tag: replaceable
-#: using-d-i.xml:2635
+#: using-d-i.xml:2710
 #, no-c-format
 msgid "scsi"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2636
+#: using-d-i.xml:2711
 #, 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:2644
+#: using-d-i.xml:2719
 #, no-c-format
 msgid "disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2645
+#: using-d-i.xml:2720
 #, 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:2653
+#: using-d-i.xml:2728
 #, no-c-format
 msgid "partnr"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2654
+#: using-d-i.xml:2729
 #, 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:2662
+#: using-d-i.xml:2737
 #, no-c-format
 msgid "config"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2663
+#: using-d-i.xml:2738
 #, 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:2684
+#: using-d-i.xml:2759
 #, no-c-format
 msgid "Install <command>Yaboot</command> on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2685
+#: using-d-i.xml:2760
 #, 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;."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2703
+#: using-d-i.xml:2778
 #, no-c-format
 msgid "Install <command>Quik</command> on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2704
+#: using-d-i.xml:2779
 #, 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:2720
+#: using-d-i.xml:2795
 #, no-c-format
 msgid "<command>zipl</command>-installer"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2721
+#: using-d-i.xml:2796
 #, 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:2738
+#: using-d-i.xml:2813
 #, no-c-format
 msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2740
+#: using-d-i.xml:2815
 #, 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:2765
+#: using-d-i.xml:2840
 #, no-c-format
 msgid "Continue Without Boot Loader"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2767
+#: using-d-i.xml:2842
 #, 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). <phrase arch=\"m68k\">This option is especially useful for Macintosh, Atari, and Amiga systems, where the original operating system must be maintained on the box and used to boot GNU/Linux.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2776
+#: using-d-i.xml:2851
 #, 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:2793
+#: using-d-i.xml:2868
 #, no-c-format
 msgid "Finishing the Installation"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2794
+#: using-d-i.xml:2869
 #, 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:2807
+#: using-d-i.xml:2882
 #, no-c-format
 msgid "Setting the System Clock"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2809
+#: using-d-i.xml:2884
 #, 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:2816
+#: using-d-i.xml:2891
 #, 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=\"m68k;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=\"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:2827
+#: using-d-i.xml:2902
 #, 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:2842
+#: using-d-i.xml:2917
 #, no-c-format
 msgid "Reboot the System"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2844
+#: using-d-i.xml:2919
 #, 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:2850
+#: using-d-i.xml:2925
 #, 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; from the DASD which you selected for the root filesystem during the first steps of the installation."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2863
+#: using-d-i.xml:2938
 #, no-c-format
 msgid "Miscellaneous"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2864
+#: using-d-i.xml:2939
 #, 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:2877
+#: using-d-i.xml:2952
 #, no-c-format
 msgid "Saving the installation logs"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2879
+#: using-d-i.xml:2954
 #, 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:2886
+#: using-d-i.xml:2961
 #, 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:2906
+#: using-d-i.xml:2981
 #, no-c-format
 msgid "Using the Shell and Viewing the Logs"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2908
+#: using-d-i.xml:2983
 #, 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 installer itself."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2926
+#: using-d-i.xml:3001
 #, no-c-format
 msgid "For the graphical installer see also <xref linkend=\"gtk-using\"/>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2930
+#: using-d-i.xml:3005
 #, 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:2938
+#: using-d-i.xml:3013
 #, 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:2947
+#: using-d-i.xml:3022
 #, 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:2954
+#: using-d-i.xml:3029
 #, 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:2960
+#: using-d-i.xml:3035
 #, 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:2975
+#: using-d-i.xml:3050
 #, no-c-format
 msgid "Installation Over the Network"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2977
+#: using-d-i.xml:3052
 #, 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:2987
+#: using-d-i.xml:3062
 #, 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:3000
+#: using-d-i.xml:3075
 #, 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:3005
+#: using-d-i.xml:3080
 #, 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 <quote>person who will continue the installation remotely</quote>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3017
+#: using-d-i.xml:3092
 #, 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:3023
+#: using-d-i.xml:3098
 #, 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"
@@ -2350,37 +2392,37 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3040
+#: using-d-i.xml:3115
 #, 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:3053
+#: using-d-i.xml:3128
 #, 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:3066
+#: using-d-i.xml:3141
 #, 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:3082
+#: using-d-i.xml:3157
 #, 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:3092
+#: using-d-i.xml:3167
 #, 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: para
-#: using-d-i.xml:3100
+#: using-d-i.xml:3175
 #, no-c-format
 msgid "Also, if you are running the SSH session from an X terminal, you should not resize the window as that will result in the connection being terminated."
 msgstr ""