Update of POT and PO files for the manual

6 files changed, 848 insertions, 680 deletions

diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot
index dcdbedb50..0de9c3ea7 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: 2006-10-17 08:26+0000\n"
+"POT-Creation-Date: 2006-10-29 14:49+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"
@@ -1840,486 +1840,640 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:2804
 #, no-c-format
-msgid "The installation system recognizes a few additional boot parameters<footnote> <para> Note that the 2.4 kernel accepts a maximum of 8 command line options and 8 environment options (including any options added by default for the installer). If these numbers are exceeded, 2.4 kernels will drop any excess options. With kernel 2.6.9 or newer, you can use 32 command line options and 32 environment options. </para> </footnote> which may be useful."
+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: term
-#: boot-installer.xml:2824
+#: boot-installer.xml:2821
 #, no-c-format
 msgid "debconf/priority"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2825
+#: boot-installer.xml:2822
 #, no-c-format
 msgid "This parameter sets the lowest priority of messages to be displayed. Short form: <userinput>priority</userinput>"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2830
+#: boot-installer.xml:2827
 #, 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:2837
+#: boot-installer.xml:2834
 #, 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:2851
+#: boot-installer.xml:2848
 #, no-c-format
 msgid "DEBIAN_FRONTEND"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2852
+#: boot-installer.xml:2849
 #, 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=slang</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=ncurses</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=bogl</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=corba</userinput></para> </listitem> </itemizedlist> The default front end is <userinput>DEBIAN_FRONTEND=newt</userinput>. <userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial console installs. Generally only the <userinput>newt</userinput> frontend is available on default install media, so this is not very useful right now."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2888
+#: boot-installer.xml:2885
 #, no-c-format
 msgid "BOOT_DEBUG"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2889
+#: boot-installer.xml:2886
 #, 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:2898
+#: boot-installer.xml:2895
 #, no-c-format
 msgid "BOOT_DEBUG=0"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2899
+#: boot-installer.xml:2896
 #, no-c-format
 msgid "This is the default."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2903
+#: boot-installer.xml:2900
 #, no-c-format
 msgid "BOOT_DEBUG=1"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2904
+#: boot-installer.xml:2901
 #, no-c-format
 msgid "More verbose than usual."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2908
+#: boot-installer.xml:2905
 #, no-c-format
 msgid "BOOT_DEBUG=2"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2909
+#: boot-installer.xml:2906
 #, no-c-format
 msgid "Lots of debugging information."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2913
+#: boot-installer.xml:2910
 #, no-c-format
 msgid "BOOT_DEBUG=3"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2914
+#: boot-installer.xml:2911
 #, 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:2928
+#: boot-installer.xml:2925
 #, no-c-format
 msgid "INSTALL_MEDIA_DEV"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2929
+#: boot-installer.xml:2926
 #, 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:2935
+#: boot-installer.xml:2932
 #, 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:2945
+#: boot-installer.xml:2942
 #, no-c-format
 msgid "debian-installer/framebuffer"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2946
+#: boot-installer.xml:2943
 #, no-c-format
 msgid "Some architectures use the kernel framebuffer to offer installation in a number of languages. If framebuffer causes a problem on your system you can disable the feature by the parameter <userinput>debian-installer/framebuffer=false</userinput>, or <userinput>fb=false</userinput> for short. 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:2956
+#: boot-installer.xml:2953
 #, no-c-format
 msgid "The <userinput>video=vga16:off</userinput> argument may also be used to disable the kernel's use of the framebuffer. Such problems have been reported on a Dell Inspiron with Mobile Radeon card."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2962
+#: boot-installer.xml:2959
 #, no-c-format
 msgid "Such problems have been reported on the Amiga 1200 and SE/30."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2966
+#: boot-installer.xml:2963
 #, no-c-format
 msgid "Such problems have been reported on hppa."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2970
+#: boot-installer.xml:2967
 #, 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:2984
+#: boot-installer.xml:2981
 #, no-c-format
 msgid "debian-installer/theme"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2985
+#: boot-installer.xml:2982
 #, 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 parameter <userinput>debian-installer/theme=<replaceable>dark</replaceable></userinput> or <userinput>theme=<replaceable>dark</replaceable></userinput>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2998
+#: boot-installer.xml:2995
 #, no-c-format
 msgid "debian-installer/probe/usb"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2999
+#: boot-installer.xml:2996
 #, no-c-format
 msgid "Set to <userinput>false</userinput> to prevent probing for USB on boot, if that causes problems."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3008
+#: boot-installer.xml:3005
 #, no-c-format
 msgid "netcfg/disable_dhcp"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3009
+#: boot-installer.xml:3006
 #, no-c-format
 msgid "By default, the &d-i; automatically probes for network configuration via DHCP. If the probe succeeds, you won't have a chance to review and change the obtained settings. You can get to the manual network setup only in case the DHCP probe fails."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3016
+#: boot-installer.xml:3013
 #, no-c-format
 msgid "If you have a DHCP server on your local network, but want to avoid it because e.g. it gives wrong answers, you can use the parameter <userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the network with DHCP and to enter the information manually."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3027
+#: boot-installer.xml:3024
 #, no-c-format
 msgid "hw-detect/start_pcmcia"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3028
+#: boot-installer.xml:3025
 #, 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:3038
+#: boot-installer.xml:3035
 #, no-c-format
 msgid "preseed/url"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3039
+#: boot-installer.xml:3036
 #, no-c-format
 msgid "Specify the url to a preconfiguration file to download and use in automating the install. See <xref linkend=\"automatic-install\"/>. Short form: <userinput>url</userinput>"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3049
+#: boot-installer.xml:3046
 #, no-c-format
 msgid "preseed/file"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3050
+#: boot-installer.xml:3047
 #, no-c-format
 msgid "Specify the path to a preconfiguration file to load to automating the install. See <xref linkend=\"automatic-install\"/>. Short form: <userinput>file</userinput>"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3060
+#: boot-installer.xml:3057
 #, no-c-format
 msgid "cdrom-detect/eject"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3061
+#: boot-installer.xml:3058
 #, 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:3070
+#: boot-installer.xml:3067
 #, 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:3081
+#: boot-installer.xml:3078
 #, no-c-format
 msgid "ramdisk_size"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3082
+#: boot-installer.xml:3079
 #, no-c-format
 msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3090
+#: boot-installer.xml:3087
 #, no-c-format
 msgid "directfb/hw-accel"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3091
+#: boot-installer.xml:3088
 #, no-c-format
 msgid "For the gtk frontend (graphical installer), hardware acceleration in directfb is disabled by default. To enable it, set this parameter to <userinput>true</userinput> when booting the installer."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3101
+#: boot-installer.xml:3098
 #, no-c-format
 msgid "rescue/enable"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3102
+#: boot-installer.xml:3099
 #, 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:3120
+#: boot-installer.xml:3117
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3125
+#: boot-installer.xml:3122
+#, no-c-format
+msgid "CD-ROM Reliability"
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:3123
+#, 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:3130
+#, no-c-format
+msgid "There are a many different possible causes for these problems. We can only list some common issues and provide general suggestions on how to deal with them. The rest is up to you."
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:3136
+#, 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:3144
+#, no-c-format
+msgid "Common issues"
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:3147
+#, 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:3153
+#, no-c-format
+msgid "If your system boots correctly from the CD-ROM, it does not necessarily mean that Linux also supports the CD-ROM (or, more correctly, the controller that your CD-ROM drive is connected to)."
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:3160
+#, no-c-format
+msgid "Some older CD-ROM drives do not work correctly if <quote>direct memory access</quote> (DMA) is enabled."
+msgstr ""
+
+#. Tag: title
+#: boot-installer.xml:3171
+#, no-c-format
+msgid "How to investigate and maybe solve issues"
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:3172
+#, no-c-format
+msgid "If the CD-ROM fails to boot, try the suggestions listed below."
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:3177
+#, no-c-format
+msgid "Check that your BIOS actually supports booting from CD-ROM (older systems possibly don't) and that your CD-ROM drive supports the media you are using."
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:3183
+#, 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"
+      "$ md5sum <replaceable>debian-testing-i386-netinst.iso</replaceable>\n"
+      "a20391b12f7ff22ef705cee4059c6b92  <replaceable>debian-testing-i386-netinst.iso</replaceable>\n"
+      "</screen></informalexample> Next, check that the md5sum of the burned CD-ROM matches as well. The following command should work. It uses the size of the image to read the correct number of bytes from the CD-ROM."
+msgstr ""
+
+#. Tag: screen
+#: boot-installer.xml:3196
+#, no-c-format
+msgid ""
+      "$ dd if=/dev/cdrom | \\\n"
+      "> head -c `stat --format=%s <replaceable>debian-testing-i386-netinst.iso</replaceable>` | \\\n"
+      "> md5sum\n"
+      "a20391b12f7ff22ef705cee4059c6b92  -\n"
+      "262668+0 records in\n"
+      "262668+0 records out\n"
+      "134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s"
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:3201
+#, no-c-format
+msgid "If, after the installer has been booted successfully, the CD-ROM is not detected, sometimes simply trying again may solve the problem. If you have more than one CD-ROM drive, try changing the CD-ROM to the other drive. If that does not work or if the CD-ROM is recognized but there are errors when reading from it, try the suggestions listed below. Some basic knowledge of Linux is required for this. To execute any of the commands, you should first switch to the second virtual console (VT2) and activate the shell there."
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:3213
+#, 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:3220
+#, 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"
+      "Probing IDE interface ide1...\n"
+      "hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n"
+      "ide1 at 0x170-0x177,0x376 on irq 15\n"
+      "hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n"
+      "Uniform CD-ROM driver Revision: 3.20\n"
+      "</screen></informalexample> If you don't see something like that, chances are the controller your CD-ROM is connected to was not recognized or may be not supported at all. If you know what driver is needed for the drive, you can try loading it manually using <command>modprobe</command>."
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:3234
+#, no-c-format
+msgid "Check that there is a device node for your CD-ROM drive under <filename>/dev/</filename>. In the example above, this would be <filename>/dev/hdc</filename>. There should also be a <filename>/dev/cdroms/cdrom0</filename>."
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:3242
+#, 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"
+      "$ mount /dev/<replaceable>hdc</replaceable> /cdrom\n"
+      "</screen></informalexample> Check if there are any error messages after that command."
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:3252
+#, no-c-format
+msgid ""
+      "Check if DMA is currently enabled: <informalexample><screen>\n"
+      "$ cd /proc/<replaceable>ide</replaceable>/<replaceable>hdc</replaceable>\n"
+      "$ grep dma settings\n"
+      "using_dma      1       0       1       rw\n"
+      "</screen></informalexample> A <quote>1</quote> means it is enabled. If it is, try disabling it: <informalexample><screen>\n"
+      "$ echo -n \"using_dma:0\" >settings\n"
+      "</screen></informalexample> Make sure that you are in the directory for the device that corresponds to your CD-ROM drive."
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:3266
+#, 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:3281
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3127
+#: boot-installer.xml:3283
 #, 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:3132
+#: boot-installer.xml:3288
 #, 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:3141
+#: boot-installer.xml:3297
+#, no-c-format
+msgid "If you are having the installation stall at a particular floppy, the first thing you should write it to a <emphasis>different</emphasis> floppy. 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:3306
 #, no-c-format
-msgid "If you are having the installation stall at a particular floppy, the first thing you should do is re-download the floppy disk image and write it to a <emphasis>different</emphasis> floppy. 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."
+msgid "Normally you should not have 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:3151
+#: boot-installer.xml:3312
 #, 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:3157
+#: boot-installer.xml:3318
 #, 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:3166
+#: boot-installer.xml:3327
 #, no-c-format
 msgid "Boot Configuration"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3168
+#: boot-installer.xml:3329
 #, 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:3175
+#: boot-installer.xml:3336
 #, no-c-format
 msgid "If you are booting with your own kernel instead of the one supplied with the installer, be sure that <userinput>CONFIG_DEVFS</userinput> is set in your kernel. The installer requires <userinput>CONFIG_DEVFS</userinput>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3182
+#: boot-installer.xml:3343
 #, no-c-format
 msgid "Often, problems can be solved by removing add-ons and peripherals, and then trying booting again. <phrase arch=\"x86\">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3188
+#: boot-installer.xml:3349
 #, no-c-format
 msgid "If you have a large amount of memory installed in your machine, more than 512M, and the installer hangs when booting the kernel, you may need to include a boot argument to limit the amount of memory the kernel sees, such as <userinput>mem=512m</userinput>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3199
+#: boot-installer.xml:3360
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3200
+#: boot-installer.xml:3361
 #, 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:3205
+#: boot-installer.xml:3366
 #, no-c-format
 msgid "Some systems have floppies with <quote>inverted DCLs</quote>. If you receive errors reading from the floppy, even when you know the floppy is good, try the parameter <userinput>floppy=thinkpad</userinput>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3211
+#: boot-installer.xml:3372
 #, no-c-format
 msgid "On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk drivers), the IDE drive may not be properly recognized. Again, try it first without the parameters and see if the IDE drive is recognized properly. If not, determine your drive geometry (cylinders, heads, and sectors), and use the parameter <userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3220
+#: boot-installer.xml:3381
 #, no-c-format
 msgid "If you have a very old machine, and the kernel hangs after saying <computeroutput>Checking 'hlt' instruction...</computeroutput>, then you should try the <userinput>no-hlt</userinput> boot argument, which disables this test."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3227
+#: boot-installer.xml:3388
 #, no-c-format
 msgid "If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter <userinput>fb=false video=vga16:off</userinput> to disable the framebuffer console. Only the English language will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3241
+#: boot-installer.xml:3402
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3242
+#: boot-installer.xml:3403
 #, no-c-format
 msgid "Some laptop models produced by Dell are known to crash when PCMCIA device detection tries to access some hardware addresses. Other laptops may display similar problems. If you experience such a problem and you don't need PCMCIA support during the installation, you can disable PCMCIA using the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can then configure PCMCIA after the installation is completed and exclude the resource range causing the problems."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3252
+#: boot-installer.xml:3413
 #, no-c-format
 msgid "Alternatively, you can boot the installer in expert mode. You will then be asked to enter the resource range options your hardware needs. For example, if you have one of the Dell laptops mentioned above, you should enter <userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list of some common resource range options in the <ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the commas, if any, when you enter this value in the installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3269
+#: boot-installer.xml:3430
 #, no-c-format
 msgid "System Freeze while Loading the USB Modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3270
+#: boot-installer.xml:3431
 #, no-c-format
 msgid "The kernel normally tries to install USB modules and the USB keyboard driver in order to support some non-standard USB keyboards. However, there are some broken USB systems where the driver hangs on loading. A possible workaround may be disabling the USB controller in your mainboard BIOS setup. Another option is passing the <userinput>debian-installer/probe/usb=false</userinput> parameter at the boot prompt, which will prevent the modules from being loaded."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3284
+#: boot-installer.xml:3445
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3286
+#: boot-installer.xml:3447
 #, no-c-format
 msgid "During the boot sequence, you may see many messages in the form <computeroutput>can't find <replaceable>something</replaceable> </computeroutput>, or <computeroutput> <replaceable>something</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>something</replaceable> </computeroutput>, or even <computeroutput>this driver release depends on <replaceable>something</replaceable> </computeroutput>. Most of these messages are harmless. You see them because the kernel for the installation system is built to run on computers with many different peripheral devices. Obviously, no one computer will have every possible peripheral device, so the operating system may emit a few complaints while it looks for peripherals you don't own. You may also see the system pause for a while. This happens when it is waiting for a device to respond, and that device is not present on your system. If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later (see <xref linkend=\"kernel-baking\"/>)."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3311
+#: boot-installer.xml:3472
 #, no-c-format
 msgid "Bug Reporter"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3312
+#: boot-installer.xml:3473
 #, no-c-format
 msgid "If you get through the initial boot phase but cannot complete the install, the bug reporter menu choice may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them in 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:3323
+#: boot-installer.xml:3484
 #, 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:3334
+#: boot-installer.xml:3495
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3335
+#: boot-installer.xml:3496
 #, 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:3342
+#: boot-installer.xml:3503
 #, no-c-format
 msgid "If you have a working Debian system, the easiest way to send an installation report is to install the installation-report and reportbug packages (<command>apt-get install installation-report reportbug</command>) and run the command <command>reportbug installation-report</command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3349
+#: boot-installer.xml:3510
 #, no-c-format
 msgid ""
       "Please 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"
       "Package: installation-reports\n"
       "\n"
       "Boot method: &lt;How did you boot the installer? CD? floppy? network?&gt;\n"
-      "Image version: &lt;Fill in date and from where you got the image&gt;\n"
+      "Image version: &lt;Full URL to image you downloaded is best&gt;\n"
       "Date: &lt;Date and time of the install&gt;\n"
       "\n"
       "Machine: &lt;Description of machine (eg, IBM Thinkpad R32)&gt;\n"
@@ -2327,23 +2481,24 @@ msgid ""
       "Memory:\n"
       "Partitions: &lt;df -Tl will do; the raw partition table is preferred&gt;\n"
       "\n"
-      "Output of lspci and lspci -n:\n"
+      "Output of lspci -nn and lspci -vnn:\n"
       "\n"
       "Base System Installation Checklist:\n"
       "[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n"
       "\n"
-      "Initial boot worked:    [ ]\n"
-      "Configure network HW:   [ ]\n"
-      "Config network:         [ ]\n"
+      "Initial boot:           [ ]\n"
+      "Detect network card:    [ ]\n"
+      "Configure network:      [ ]\n"
       "Detect CD:              [ ]\n"
       "Load installer modules: [ ]\n"
       "Detect hard drives:     [ ]\n"
       "Partition hard drives:  [ ]\n"
-      "Create file systems:    [ ]\n"
-      "Mount partitions:       [ ]\n"
       "Install base system:    [ ]\n"
+      "Clock/timezone setup:   [ ]\n"
+      "User/password setup:    [ ]\n"
+      "Install tasks:          [ ]\n"
       "Install boot loader:    [ ]\n"
-      "Reboot:                 [ ]\n"
+      "Overall install:        [ ]\n"
       "\n"
       "Comments/Problems:\n"
       "\n"
diff --git a/po/pot/installation-howto.pot b/po/pot/installation-howto.pot
index 6784e69c5..b3007d84d 100644
--- a/po/pot/installation-howto.pot
+++ b/po/pot/installation-howto.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: 2006-10-19 11:21+0000\n"
+"POT-Creation-Date: 2006-10-29 14:49+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"
@@ -191,101 +191,101 @@ msgstr ""
 #. Tag: para
 #: installation-howto.xml:212
 #, no-c-format
-msgid "Once the installer starts, you will be greeted with an initial screen. Press &enterkey; to boot, or read the instructions for other boot methods and parameters (see <xref linkend=\"boot-parms\"/>). <phrase arch=\"i386\"> If you want a 2.4 kernel, type <userinput>install24</userinput> at the <prompt>boot:</prompt> prompt. The 2.6 kernel is the default. </phrase>"
+msgid "Once the installer starts, you will be greeted with an initial screen. Press &enterkey; to boot, or read the instructions for other boot methods and parameters (see <xref linkend=\"boot-parms\"/>)."
 msgstr ""
 
 #. Tag: para
-#: installation-howto.xml:222
+#: installation-howto.xml:218
 #, no-c-format
 msgid "After a while you will be asked to select your language. Use the arrow keys to pick a language and press &enterkey; to continue. Next you'll be asked to select your country, with the choices including countries where your language is spoken. If it's not on the short list, a list of all the countries in the world is available."
 msgstr ""
 
 #. Tag: para
-#: installation-howto.xml:230
+#: installation-howto.xml:226
 #, no-c-format
 msgid "You may be asked to confirm your keyboard layout. Choose the default unless you know better."
 msgstr ""
 
 #. Tag: para
-#: installation-howto.xml:235
+#: installation-howto.xml:231
 #, no-c-format
 msgid "Now sit back while debian-installer detects some of your hardware, and loads the rest of itself from CD, floppy, USB, etc."
 msgstr ""
 
 #. Tag: para
-#: installation-howto.xml:240
+#: installation-howto.xml:236
 #, no-c-format
 msgid "Next the installer will try to detect your network hardware and set up networking by DHCP. If you are not on a network or do not have DHCP, you will be given the opportunity to configure the network manually."
 msgstr ""
 
 #. Tag: para
-#: installation-howto.xml:246
+#: installation-howto.xml:242
 #, no-c-format
 msgid "Now it is time to partition your disks. First you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive (guided partitioning). This is recommended for new users or anyone in a hurry. If you do not want to autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu."
 msgstr ""
 
 #. Tag: para
-#: installation-howto.xml:254
+#: installation-howto.xml:250
 #, no-c-format
 msgid "If you have an existing DOS or Windows partition that you want to preserve, be very careful with automatic partitioning. If you choose manual partitioning, you can use the installer to resize existing FAT or NTFS partitions to create room for the Debian install: simply select the partition and specify its new size."
 msgstr ""
 
 #. Tag: para
-#: installation-howto.xml:261
+#: installation-howto.xml:257
 #, no-c-format
 msgid "On the next screen you will see your partition table, how the partitions will be formatted, and where they will be mounted. Select a partition to modify or delete it. If you did automatic partitioning, you should just be able to choose <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the menu to use what it set up. Remember to assign at least one partition for swap space and to mount a partition on <filename>/</filename>. <xref linkend=\"partitioning\"/> has more information about partitioning."
 msgstr ""
 
 #. Tag: para
-#: installation-howto.xml:271
+#: installation-howto.xml:267
 #, no-c-format
 msgid "Now &d-i; formats your partitions and starts to install the base system, which can take a while. That is followed by installing a kernel."
 msgstr ""
 
 #. Tag: para
-#: installation-howto.xml:276
+#: installation-howto.xml:272
 #, no-c-format
 msgid "The last step is to install a boot loader. If the installer detects other operating systems on your computer, it will add them to the boot menu and let you know. <phrase arch=\"x86\">By default GRUB will be installed to the master boot record of the first harddrive, which is generally a good choice. You'll be given the opportunity to override that choice and install it elsewhere. </phrase>"
 msgstr ""
 
 #. Tag: para
-#: installation-howto.xml:286
+#: installation-howto.xml:282
 #, no-c-format
 msgid "&d-i; will now tell you that the installation has finished. Remove the cdrom or other boot media and hit &enterkey; to reboot your machine. It should boot up into the next stage of the install process, which is explained in <xref linkend=\"boot-new\"/>."
 msgstr ""
 
 #. Tag: para
-#: installation-howto.xml:293
+#: installation-howto.xml:289
 #, no-c-format
 msgid "If you need more information on the install process, see <xref linkend=\"d-i-intro\"/>."
 msgstr ""
 
 #. Tag: title
-#: installation-howto.xml:302
+#: installation-howto.xml:298
 #, no-c-format
 msgid "Send us an installation report"
 msgstr ""
 
 #. Tag: para
-#: installation-howto.xml:303
+#: installation-howto.xml:299
 #, no-c-format
 msgid "If you successfully managed an installation with &d-i;, please take time to provide us with a report. The simplest way to do so is to install the reportbug package (<command>apt-get install reportbug</command>), and run <command>reportbug installation-report</command>."
 msgstr ""
 
 #. Tag: para
-#: installation-howto.xml:311
+#: installation-howto.xml:307
 #, no-c-format
 msgid "If you did not complete the install, you probably found a bug in debian-installer. To improve the installer it is necessary that we know about them, so please take the time to report them. You can use an installation report to report problems; if the install completely fails, see <xref linkend=\"problem-report\"/>."
 msgstr ""
 
 #. Tag: title
-#: installation-howto.xml:323
+#: installation-howto.xml:319
 #, no-c-format
 msgid "And finally.."
 msgstr ""
 
 #. Tag: para
-#: installation-howto.xml:324
+#: installation-howto.xml:320
 #, no-c-format
 msgid "We hope that your Debian installation is pleasant and that you find Debian useful. You might want to read <xref linkend=\"post-install\"/>."
 msgstr ""
diff --git a/po/pot/partitioning.pot b/po/pot/partitioning.pot
index 0e0ff072a..3db5390c4 100644
--- a/po/pot/partitioning.pot
+++ b/po/pot/partitioning.pot
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2006-10-26 16:20+0000\n"
+"POT-Creation-Date: 2006-10-29 14:49+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"
@@ -635,142 +635,131 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:582
 #, no-c-format
-msgid ""
-      "If you will be working with more than 20 partitions on your ide disk, you will need to create devices for partitions 21 and beyond. The next step of initializing the partition will fail unless a proper device is present. As an example, here are commands you can use in <userinput>tty2</userinput> or under <guimenuitem>Execute a shell</guimenuitem> to add a device so the 21st partition can be initialized: <informalexample><screen>\n"
-      "# cd /dev\n"
-      "# mknod hda21 b 3 21\n"
-      "# chgrp disk hda21\n"
-      "# chmod 660 hda21\n"
-      "</screen></informalexample> Booting into the new system will fail unless proper devices are present on the target system. After installing the kernel and modules, execute: <informalexample><screen>\n"
-      "# cd /target/dev\n"
-      "# mknod hda21 b 3 21\n"
-      "# chgrp disk hda21\n"
-      "# chmod 660 hda21\n"
-      "</screen></informalexample> <phrase arch=\"x86\">Remember to mark your boot partition as <quote>Bootable</quote>.</phrase>"
+msgid "Remember to mark your boot partition as <quote>Bootable</quote>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:601
+#: partitioning.xml:585
 #, no-c-format
 msgid "One key point when partitioning for Mac type disks is that the swap partition is identified by its name; it must be named <quote>swap</quote>. All Mac linux partitions are the same partition type, Apple_UNIX_SRV2. Please read the fine manual. We also suggest reading the <ulink url=\"&url-mac-fdisk-tutorial;\">mac-fdisk Tutorial</ulink>, which includes steps you should take if you are sharing your disk with MacOS."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:617 partitioning.xml:678 partitioning.xml:702 partitioning.xml:799 partitioning.xml:913 partitioning.xml:990
+#: partitioning.xml:601 partitioning.xml:662 partitioning.xml:686 partitioning.xml:783 partitioning.xml:897 partitioning.xml:974
 #, no-c-format
 msgid "Partitioning for &arch-title;"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:618
+#: partitioning.xml:602
 #, no-c-format
 msgid "Booting Debian from the SRM console (the only disk boot method supported by &releasename;) requires you to have a BSD disk label, not a DOS partition table, on your boot disk. (Remember, the SRM boot block is incompatible with MS-DOS partition tables &mdash; see <xref linkend=\"alpha-firmware\"/>.) As a result, <command>partman</command> creates BSD disk labels when running on &architecture;, but if your disk has an existing DOS partition table the existing partitions will need to be deleted before <command>partman</command> can convert it to use a disk label."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:629
+#: partitioning.xml:613
 #, no-c-format
 msgid "If you have chosen to use <command>fdisk</command> to partition your disk, and the disk that you have selected for partitioning does not already contain a BSD disk label, you must use the <quote>b</quote> command to enter disk label mode."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:636
+#: partitioning.xml:620
 #, no-c-format
 msgid "Unless you wish to use the disk you are partitioning from Tru64 Unix or one of the free 4.4BSD-Lite derived operating systems (FreeBSD, OpenBSD, or NetBSD), you should <emphasis>not</emphasis> create the third partition as a <quote>whole disk</quote> partition (i.e. with start and end sectors to span the whole disk), as this renders the disk incompatible with the tools used to make it bootable with aboot. This means that the disk configured by the installer for use as the Debian boot disk will be inaccessible to the operating systems mentioned earlier."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:648
+#: partitioning.xml:632
 #, no-c-format
 msgid "Also, because <command>aboot</command> is written to the first few sectors of the disk (currently it occupies about 70 kilobytes, or 150 sectors), you <emphasis>must</emphasis> leave enough empty space at the beginning of the disk for it. In the past, it was suggested that you make a small partition at the beginning of the disk, to be left unformatted. For the same reason mentioned above, we now suggest that you do not do this on disks that will only be used by GNU/Linux. When using <command>partman</command>, a small partition will still be created for <command>aboot</command> for convenience reasons."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:660
+#: partitioning.xml:644
 #, no-c-format
 msgid "For ARC installations, you should make a small FAT partition at the beginning of the disk to contain <command>MILO</command> and <command>linload.exe</command> &mdash; 5 megabytes should be sufficient, see <xref linkend=\"non-debian-partitioning\"/>. Unfortunately, making FAT file systems from the menu is not yet supported, so you'll have to do it manually from the shell using <command>mkdosfs</command> before attempting to install the boot loader."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:679
+#: partitioning.xml:663
 #, no-c-format
 msgid "PALO, the HPPA boot loader, requires a partition of type <quote>F0</quote> somewhere in the first 2GB. This is where the boot loader and an optional kernel and RAMdisk will be stored, so make it big enough for that &mdash; at least 4Mb (I like 8&ndash;16MB). An additional requirement of the firmware is that the Linux kernel must reside within the first 2GB of the disk. This is typically achieved by making the root ext2 partition fit entirely within the first 2GB of the disk. Alternatively you can create a small ext2 partition near the start of the disk and mount that on <filename>/boot</filename>, since that is the directory where the Linux kernel(s) will be stored. <filename>/boot</filename> needs to be big enough to hold whatever kernels (and backups) you might wish to load; 25&ndash;50MB is generally sufficient."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:703
+#: partitioning.xml:687
 #, no-c-format
 msgid "If you have an existing other operating system such as DOS or Windows and you want to preserve that operating system while installing Debian, you may need to resize its partition to free up space for the Debian installation. The installer supports resizing of both FAT and NTFS filesystems; when you get to the installer's partitioning step, select the option <guimenuitem>Manual</guimenuitem> and then simply select an existing partition and change its size."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:713
+#: partitioning.xml:697
 #, no-c-format
 msgid "The PC BIOS generally adds additional constraints for disk partitioning. There is a limit to how many <quote>primary</quote> and <quote>logical</quote> partitions a drive can contain. Additionally, with pre 1994&ndash;98 BIOSes, there are limits to where on the drive the BIOS can boot from. More information can be found in the <ulink url=\"&url-partition-howto;\">Linux Partition HOWTO</ulink> and the <ulink url=\"&url-phoenix-bios-faq-large-disk;\">Phoenix BIOS FAQ</ulink>, but this section will include a brief overview to help you plan most situations."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:724
+#: partitioning.xml:708
 #, no-c-format
 msgid "<quote>Primary</quote> partitions are the original partitioning scheme for PC disks. However, there can only be four of them. To get past this limitation, <quote>extended</quote> and <quote>logical</quote> partitions were invented. By setting one of your primary partitions as an extended partition, you can subdivide all the space allocated to that partition into logical partitions. You can create up to 60 logical partitions per extended partition; however, you can only have one extended partition per drive."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:735
+#: partitioning.xml:719
 #, no-c-format
 msgid "Linux limits the partitions per drive to 15 partitions for SCSI disks (3 usable primary partitions, 12 logical partitions), and 63 partitions on an IDE drive (3 usable primary partitions, 60 logical partitions). However the normal &debian; system provides only 20 devices for partitions, so you may not install on partitions higher than 20 unless you first manually create devices for those partitions."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:745
+#: partitioning.xml:729
 #, no-c-format
 msgid "If you have a large IDE disk, and are using neither LBA addressing, nor overlay drivers (sometimes provided by hard disk manufacturers), then the boot partition (the partition containing your kernel image) must be placed within the first 1024 cylinders of your hard drive (usually around 524 megabytes, without BIOS translation)."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:753
+#: partitioning.xml:737
 #, no-c-format
 msgid "This restriction doesn't apply if you have a BIOS newer than around 1995&ndash;98 (depending on the manufacturer) that supports the <quote>Enhanced Disk Drive Support Specification</quote>. Both Lilo, the Linux loader, and Debian's alternative <command>mbr</command> must use the BIOS to read the kernel from the disk into RAM. If the BIOS int 0x13 large disk access extensions are found to be present, they will be utilized. Otherwise, the legacy disk access interface is used as a fall-back, and it cannot be used to address any location on the disk higher than the 1023rd cylinder. Once Linux is booted, no matter what BIOS your computer has, these restrictions no longer apply, since Linux does not use the BIOS for disk access."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:767
+#: partitioning.xml:751
 #, no-c-format
 msgid "If you have a large disk, you might have to use cylinder translation techniques, which you can set from your BIOS setup program, such as LBA (Logical Block Addressing) or CHS translation mode (<quote>Large</quote>). More information about issues with large disks can be found in the <ulink url=\"&url-large-disk-howto;\">Large Disk HOWTO</ulink>. If you are using a cylinder translation scheme, and the BIOS does not support the large disk access extensions, then your boot partition has to fit within the <emphasis>translated</emphasis> representation of the 1024th cylinder."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:779
+#: partitioning.xml:763
 #, no-c-format
 msgid "The recommended way of accomplishing this is to create a small (25&ndash;50MB should suffice) partition at the beginning of the disk to be used as the boot partition, and then create whatever other partitions you wish to have, in the remaining area. This boot partition <emphasis>must</emphasis> be mounted on <filename>/boot</filename>, since that is the directory where the Linux kernel(s) will be stored. This configuration will work on any system, regardless of whether LBA or large disk CHS translation is used, and regardless of whether your BIOS supports the large disk access extensions."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:800
+#: partitioning.xml:784
 #, no-c-format
 msgid "The <command>partman</command> disk partitioner is the default partitioning tool for the installer. It manages the set of partitions and their mount points to ensure that the disks and filesystems are properly configured for a successful installation. It actually uses <command>parted</command> to do the on-disk partitioning."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:812
+#: partitioning.xml:796
 #, no-c-format
 msgid "EFI Recognized Formats"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:813
+#: partitioning.xml:797
 #, no-c-format
 msgid "The IA64 EFI firmware supports two partition table (or disk label) formats, GPT and MS-DOS. MS-DOS, the format typically used on i386 PCs, is no longer recommended for IA64 systems. Although the installer also provides <command>cfdisk</command>, you should only use <ulink url=\"parted.txt\"> <command>parted</command></ulink> because only it can manage both GPT and MS-DOS tables correctly."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:825
+#: partitioning.xml:809
 #, no-c-format
 msgid "The automatic partitioning recipes for <command>partman</command> allocate an EFI partition as the first partition on the disk. You can also set up the partition under the <guimenuitem>Guided partitioning</guimenuitem> from the main menu in a manner similar to setting up a <emphasis>swap</emphasis> partition."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:833
+#: partitioning.xml:817
 #, no-c-format
 msgid ""
       "The <command>partman</command> partitioner will handle most disk layouts. For those rare cases where it is necessary to manually set up a disk, you can use the shell as described above and run the <command>parted</command> utility directly using its command line interface. Assuming that you want to erase your whole disk and create a GPT table and some partitions, then something similar to the following command sequence could be used: <informalexample><screen>\n"
@@ -785,97 +774,97 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:858
+#: partitioning.xml:842
 #, no-c-format
 msgid "Boot Loader Partition Requirements"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:859
+#: partitioning.xml:843
 #, no-c-format
 msgid "ELILO, the ia64 boot loader, requires a partition containing a FAT file system with the <userinput>boot</userinput> flag set. The partition must be big enough to hold the boot loader and any kernels or RAMdisks you may wish to boot. A minimum size would be about 20MB, but if you expect to run with multiple kernels, then 128MB might be a better size."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:868
+#: partitioning.xml:852
 #, no-c-format
 msgid "The EFI Boot Manager and the EFI Shell fully support the GPT table so the boot partition does not necessarily have to be the first partition or even on the same disk. This is convenient if you should forget to allocate the partition and only find out after you have formatted the other partitions on your disk(s). The <command>partman</command> partitioner checks for an EFI partition at the same time it checks for a properly set up <emphasis>root</emphasis> partition. This gives you an opportunity to correct the disk layout before the package install begins. The easiest way to correct this omission is to shrink the last partition of the disk to make enough free space for adding an EFI partition."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:883
+#: partitioning.xml:867
 #, no-c-format
 msgid "It is strongly recommended that you allocate the EFI boot partition on the same disk as the <emphasis>root</emphasis> filesystem."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:891
+#: partitioning.xml:875
 #, no-c-format
 msgid "EFI Diagnostic Partitions"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:892
+#: partitioning.xml:876
 #, no-c-format
 msgid "The EFI firmware is significantly more sophisticated than the usual BIOS seen on most x86 PCs. Some system vendors take advantage of the ability of the EFI to access files and run programs from a hard disk filesystem to store diagnostics and EFI based system management utilities on the hard disk. This is a separate FAT format filesystem on the system disk. Consult the system documentation and accessories that come with the system for details. The easiest time to set up a diagnostics partition is at the same time you set up the EFI boot partition."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:914
+#: partitioning.xml:898
 #, no-c-format
 msgid "SGI machines require an SGI disk label in order to make the system bootable from hard disk. It can be created in the fdisk expert menu. The thereby created volume header (partition number 9) should be at least 3MB large. If the volume header created is too small, you can simply delete partition number 9 and re-add it with a different size. Note that the volume header must start at sector 0."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:931
+#: partitioning.xml:915
 #, no-c-format
 msgid "Partitioning Newer PowerMacs"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:932
+#: partitioning.xml:916
 #, no-c-format
 msgid "If you are installing onto a NewWorld PowerMac you must create a special bootstrap partition to hold the boot loader. The size of this partition must be 800KB and its partition type must be <emphasis>Apple_Bootstrap</emphasis>. If the bootstrap partition is not created with the <emphasis>Apple_Bootstrap</emphasis> type your machine cannot be made bootable from the hard disk. This partition can easily be created by creating a new partition in <command>partman</command> and telling it to use it as a <quote>NewWorld boot partition</quote>, or in <command>mac-fdisk</command> using the <userinput>b</userinput> command."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:945
+#: partitioning.xml:929
 #, no-c-format
 msgid "The special partition type Apple_Bootstrap is required to prevent MacOS from mounting and damaging the bootstrap partition, as there are special modifications made to it in order for OpenFirmware to boot it automatically."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:952
+#: partitioning.xml:936
 #, no-c-format
 msgid "Note that the bootstrap partition is only meant to hold 3 very small files: the <command>yaboot</command> binary, its configuration <filename>yaboot.conf</filename>, and a first stage OpenFirmware loader <command>ofboot.b</command>. It need not and must not be mounted on your file system nor have kernels or anything else copied to it. The <command>ybin</command> and <command>mkofboot</command> utilities are used to manipulate this partition."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:962
+#: partitioning.xml:946
 #, no-c-format
 msgid "In order for OpenFirmware to automatically boot &debian; the bootstrap partition should appear before other boot partitions on the disk, especially MacOS boot partitions. The bootstrap partition should be the first one you create. However, if you add a bootstrap partition later, you can use <command>mac-fdisk</command>'s <userinput>r</userinput> command to reorder the partition map so the bootstrap partition comes right after the map (which is always partition 1). It's the logical map order, not the physical address order, that counts."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:974
+#: partitioning.xml:958
 #, no-c-format
 msgid "Apple disks normally have several small driver partitions. If you intend to dual boot your machine with MacOSX, you should retain these partitions and a small HFS partition (800k is the minimum size). That is because MacOSX, on every boot, offers to initialize any disks which do not have active MacOS partitions and driver partitions."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:991
+#: partitioning.xml:975
 #, no-c-format
 msgid "Make sure you create a <quote>Sun disk label</quote> on your boot disk. This is the only kind of partition scheme that the OpenBoot PROM understands, and so it's the only scheme from which you can boot. The <keycap>s</keycap> key is used in <command>fdisk</command> to create Sun disk labels."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:999
+#: partitioning.xml:983
 #, no-c-format
 msgid "Furthermore, on &arch-title; disks, make sure your first partition on your boot disk starts at cylinder 0. While this is required, it also means that the first partition will contain the partition table and the boot block, which are the first two sectors of the disk. You must <emphasis>not</emphasis> put swap on the first partition of the boot drive, since swap partitions do not preserve the first few sectors of the partition. You can put Ext2 or UFS partitions there; these will leave the partition table and the boot block alone."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:1010
+#: partitioning.xml:994
 #, no-c-format
 msgid "It is also advised that the third partition should be of type <quote>Whole disk</quote> (type 5), and contain the entire disk (from the first cylinder to the last). This is simply a convention of Sun disk labels, and helps the <command>SILO</command> boot loader keep its bearings."
 msgstr ""
diff --git a/po/pot/preseed.pot b/po/pot/preseed.pot
index 3e3f2413d..8fbf77ec0 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: 2006-10-26 16:19+0000\n"
+"POT-Creation-Date: 2006-10-29 14:48+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"
@@ -27,7 +27,7 @@ msgid "This appendix explains the intricacies of preseeding answers to questions
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:23 preseed.xml:504
+#: preseed.xml:23 preseed.xml:508
 #, no-c-format
 msgid "The configuration fragments used in this appendix are also available as an example preconfiguration file from &urlset-example-preseed;."
 msgstr ""
@@ -347,89 +347,89 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:374
 #, no-c-format
-msgid "A <quote>--</quote> in the boot options has special meaning. Kernel parameters that appear after it will be copied into the installed bootloader configuration (if supported by the installer for the bootloader). Note that the <quote>--</quote> may already be present in the default boot parameters."
+msgid "A <quote>--</quote> in the boot options has special meaning. Kernel parameters that appear after the last <quote>--</quote> will be copied into the installed bootloader configuration (if supported by the installer for the bootloader). Note that the <quote>--</quote> may already be present in the default boot parameters, which means that unless you add another <quote>--</quote> all parameters specified at the boot prompt will be copied. That being the case, you should specify any preconfiguration options before any options required by the hardware in order to boot, and separate them with a <quote>--</quote> to ensure that only the latter are copied onto the target system."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:383
+#: preseed.xml:388
 #, no-c-format
-msgid "The 2.4 kernel accepts a maximum of 8 command line options and 8 environment options (including any options added by default for the installer). If these numbers are exceeded, 2.4 kernels will drop any excess options and 2.6 kernels will panic. For kernel 2.6.9 and later, you can use 32 command line options and 32 environment options."
+msgid "Current linux kernels (2.6.9 and later) accept a maximum of 32 command line options and 32 environment options, including any options added by default for the installer. If these numbers are exceeded, the kernel will panic (crash). (For earlier kernels, these numbers were lower.)"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:392
+#: preseed.xml:396
 #, no-c-format
 msgid "For most installations some of the default options in your bootloader configuration file, like <literal>vga=normal</literal>, may be safely removed which may allow you to add more options for preseeding."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:399
+#: preseed.xml:403
 #, no-c-format
 msgid "It may not always be possible to specify values with spaces for boot parameters, even if you delimit them with quotes."
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:409
+#: preseed.xml:413
 #, no-c-format
 msgid "Creating a preconfiguration file"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:410
+#: preseed.xml:414
 #, no-c-format
 msgid "The preconfiguration file is in the format used by the <command>debconf-set-selections</command> command. The general format of a line in a preconfiguration file is:"
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:416
+#: preseed.xml:420
 #, no-c-format
 msgid "&lt;owner&gt; &lt;question name&gt; &lt;question type&gt; &lt;value&gt;"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:418
+#: preseed.xml:422
 #, no-c-format
 msgid "There are a few rules to keep in mind when writing a preconfiguration file."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:425
+#: preseed.xml:429
 #, no-c-format
 msgid "Put only a single space or tab between type and value: any additional whitespace will be interpreted as belonging to the value."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:429
+#: preseed.xml:433
 #, no-c-format
 msgid "A line can be split into multiple lines by appending a backslash (<quote><literal>\\</literal></quote>) as the line continuation character. A good place to split a line is after the question name; a bad place is between type and value."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:435
+#: preseed.xml:439
 #, no-c-format
 msgid "Most questions need to be preseeded using the values valid in English and not the translated values. However, there are some questions (for example in <classname>partman</classname>) where the translated values need to be used."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:441
+#: preseed.xml:445
 #, no-c-format
 msgid "Some questions take a code as value instead of the English text that is shown during installation."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:447
+#: preseed.xml:451
 #, no-c-format
 msgid "The easiest way to create a preconfiguration file is to use the example file linked in <xref linkend=\"preseed-contents\"/> as basis and work from there."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:452
+#: preseed.xml:456
 #, no-c-format
 msgid "An alternative method is to do a manual installation and then, after rebooting, use the <command>debconf-get-selections</command> from the <classname>debconf-utils</classname> package to dump both the debconf database and the installer's cdebconf database to a single file:"
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:459
+#: preseed.xml:463
 #, no-c-format
 msgid ""
       "$ debconf-get-selections --installer &gt; <replaceable>file</replaceable>\n"
@@ -437,67 +437,67 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:461
+#: preseed.xml:465
 #, no-c-format
 msgid "However, a file generated in this manner will have some items that should not be preseeded, and the example file is a better starting place for most users."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:469
+#: preseed.xml:473
 #, no-c-format
 msgid "This method relies on the fact that, at the end of the installation, the installer's cdebconf database is saved to the installed system in <filename>/var/log/installer/cdebconf</filename>. However, because the database may contain sensitive information, by default the files are only readable by root."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:477
+#: preseed.xml:481
 #, no-c-format
 msgid "The directory <filename>/var/log/installer</filename> and all files in it will be deleted from your system if you purge the package <classname>installation-report</classname>."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:485
+#: preseed.xml:489
 #, no-c-format
 msgid "To check possible values for questions, you can use <command>nano</command> to examine the files in <filename>/var/lib/cdebconf</filename> while an installation is in progress. View <filename>templates.dat</filename> for the raw templates and <filename>questions.dat</filename> for the current values and for the values assigned to variables."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:493
+#: preseed.xml:497
 #, no-c-format
 msgid "To check if the format of your preconfiguration file is valid before performing an install, you can use the command <command>debconf-set-selections -c <replaceable>preseed.cfg</replaceable></command>."
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:503
+#: preseed.xml:507
 #, no-c-format
 msgid "Contents of the preconfiguration file"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:509
+#: preseed.xml:513
 #, no-c-format
 msgid "Note that this example is based on an installation for the Intel x86 architecture. If you are installing a different architecture, some of the examples (like keyboard selection and bootloader installation) may not be relevant and will need to be replaced by debconf settings appropriate for your architecture."
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:520
+#: preseed.xml:524
 #, no-c-format
 msgid "Localization"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:521
+#: preseed.xml:525
 #, no-c-format
 msgid "Setting localization values will only work if you are using initrd preseeding. With all other methods the preconfiguration file will only be loaded after these questions have been asked."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:527
+#: preseed.xml:531
 #, no-c-format
 msgid "The locale can be used to specify both language and country. To specify the locale as a boot parameter, use <userinput>locale=<replaceable>en_US</replaceable></userinput>."
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:533
+#: preseed.xml:537
 #, no-c-format
 msgid ""
       "# Locale sets language and country.\n"
@@ -505,13 +505,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:535
+#: preseed.xml:539
 #, no-c-format
 msgid "Keyboard configuration consists of selecting a keyboard architecture and a keymap. In most cases the correct keyboard architecture is selected by default, so there's normally no need to preseed it. The keymap must be valid for the selected keyboard architecture."
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:542
+#: preseed.xml:546
 #, no-c-format
 msgid ""
       "# Keyboard selection.\n"
@@ -522,43 +522,43 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:544
+#: preseed.xml:548
 #, no-c-format
 msgid "To skip keyboard configuration, preseed <classname>console-tools/archs</classname> with <userinput>skip-config</userinput>. This will result in the kernel keymap remaining active."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:553
+#: preseed.xml:557
 #, no-c-format
 msgid "The changes in the input layer for 2.6 kernels have made the keyboard architecture virtually obsolete. For 2.6 kernels normally a <quote>PC</quote> (<userinput>at</userinput>) keymap should be selected."
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:563
+#: preseed.xml:567
 #, no-c-format
 msgid "Network configuration"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:564
+#: preseed.xml:568
 #, no-c-format
 msgid "Of course, preseeding the network configuration won't work if you're loading your preconfiguration file from the network. But it's great when you're booting from CD or USB stick. If you are loading preconfiguration files from the network, you can pass network config parameters by using kernel boot parameters."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:572
+#: preseed.xml:576
 #, no-c-format
 msgid "If you need to pick a particular interface when netbooting before loading a preconfiguration file from the network, use a boot parameter such as <userinput>interface=<replaceable>eth1</replaceable></userinput>."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:578
+#: preseed.xml:582
 #, no-c-format
 msgid "Although preseeding the network configuration is normally not possible when using network preseeding (using <quote>preseed/url</quote>), you can use the following hack to work around that, for example if you'd like to set a static address for the network interface. The hack is to force the network configuration to run again after the preconfiguration file has been loaded by creating a <quote>preseed/run</quote> script containing the following lines:"
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:588
+#: preseed.xml:592
 #, no-c-format
 msgid ""
       "killall.sh dhclient\n"
@@ -566,7 +566,7 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:592
+#: preseed.xml:596
 #, no-c-format
 msgid ""
       "# netcfg will choose an interface that has link if possible. This makes it\n"
@@ -610,31 +610,31 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:597
+#: preseed.xml:601
 #, no-c-format
 msgid "Mirror settings"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:598
+#: preseed.xml:602
 #, no-c-format
 msgid "Depending on the installation method you use, a mirror may be used both to download additional components of the installer, the base system and to set up the <filename>/etc/apt/sources.list</filename> for the installed system."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:605
+#: preseed.xml:609
 #, no-c-format
 msgid "The parameter <classname>mirror/suite</classname> determines the suite for the installed system."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:610
+#: preseed.xml:614
 #, no-c-format
 msgid "The parameter <classname>mirror/udeb/suite</classname> determines the suite for additional components for the installer. It is only useful to set this if components are actually downloaded over the network and should match the suite that was used to build the initrd for the installation method used for the installation. By default the value for <classname>mirror/udeb/suite</classname> is the same as <classname>mirror/suite</classname>."
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:622
+#: preseed.xml:626
 #, no-c-format
 msgid ""
       "d-i mirror/country string enter information manually\n"
@@ -649,25 +649,25 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:627
+#: preseed.xml:631
 #, no-c-format
 msgid "Partitioning"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:628
+#: preseed.xml:632
 #, no-c-format
 msgid "Using preseeding to partition the harddisk is very much limited to what is supported by <classname>partman-auto</classname>. You can choose to either partition existing free space on a disk or a whole disk. The layout of the disk can be determined by using a predefined recipe, a custom recipe from a recipe file or a recipe included in the preconfiguration file. It is currently not possible to partition multiple disks using preseeding."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:639
+#: preseed.xml:643
 #, no-c-format
 msgid "The identification of disks is dependent on the order in which their drivers are loaded. If there are multiple disks in the system, make very sure the correct one will be selected before using preseeding."
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:647
+#: preseed.xml:651
 #, no-c-format
 msgid ""
       "# If the system has free space you can choose to only partition that space.\n"
@@ -733,31 +733,31 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:652
+#: preseed.xml:656
 #, no-c-format
 msgid "Partitioning using RAID"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:653
+#: preseed.xml:657
 #, 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\"/>."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:663
+#: preseed.xml:667
 #, no-c-format
 msgid "This type of automated partitioning is easy to get wrong. It is also a very new component that may still have some bugs or missing error handling. The responsibility to get the various recipes right (so they make sense and don't conflict) lies with the user. Check <filename>/var/log/syslog</filename> if you run into problems."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:671
+#: preseed.xml:675
 #, no-c-format
 msgid "Note that only RAID 0 and RAID 1 have been tested by the developers of the component. RAID 5 is untested. Advanced RAID setup with degraded arrays or spare devices has only been tested lightly."
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:679
+#: preseed.xml:683
 #, no-c-format
 msgid ""
       "# NOTE: this option is of beta release quality and should be used carefully\n"
@@ -808,13 +808,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:684
+#: preseed.xml:688
 #, no-c-format
 msgid "Clock and time zone setup"
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:686
+#: preseed.xml:690
 #, no-c-format
 msgid ""
       "# Controls whether or not the hardware clock is set to UTC.\n"
@@ -826,19 +826,19 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:691
+#: preseed.xml:695
 #, no-c-format
 msgid "Apt setup"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:692
+#: preseed.xml:696
 #, no-c-format
 msgid "Setup of the <filename>/etc/apt/sources.list</filename> and basic configuration options is fully automated based on your installation method and answers to earlier questions. You can optionally add other (local) repositories."
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:700
+#: preseed.xml:704
 #, no-c-format
 msgid ""
       "# You can choose to install non-free and contrib software.\n"
@@ -859,25 +859,25 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:705
+#: preseed.xml:709
 #, no-c-format
 msgid "Account setup"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:706
+#: preseed.xml:710
 #, no-c-format
 msgid "The password for the root account and name and password for a first regular user's account can be preseeded. For the passwords you can use either clear text values or MD5 <emphasis>hashes</emphasis>."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:713
+#: preseed.xml:717
 #, no-c-format
 msgid "Be aware that preseeding passwords is not completely secure as everyone with access to the preconfiguration file will have the knowledge of these passwords. Using MD5 hashes is considered slightly better in terms of security but it might also give a false sense of security as access to a MD5 hash allows for brute force attacks."
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:723
+#: preseed.xml:727
 #, no-c-format
 msgid ""
       "# Skip creation of a root account (normal user account will be able to\n"
@@ -903,37 +903,37 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:725
+#: preseed.xml:729
 #, no-c-format
 msgid "The <classname>passwd/root-password-crypted</classname> and <classname>passwd/user-password-crypted</classname> variables can also be preseeded with <quote>!</quote> as their value. In that case, the corresponding account is disabled. This may be convenient for the root account, provided of course that an alternative method is setup to allow administrative activities or root login (for instance by using SSH key authentication or <command>sudo</command>)."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:735
+#: preseed.xml:739
 #, no-c-format
 msgid "An MD5 hash for a password can be generated using the following command."
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:739
+#: preseed.xml:743
 #, no-c-format
 msgid "$ echo \"r00tme\" | mkpasswd -s -H MD5"
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:745
+#: preseed.xml:749
 #, no-c-format
 msgid "Base system installation"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:746
+#: preseed.xml:750
 #, no-c-format
 msgid "There is actually not very much that can be preseeded for this stage of the installation. The only questions asked concern the installation of the kernel."
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:753
+#: preseed.xml:757
 #, no-c-format
 msgid ""
       "# Select the initramfs generator used to generate the initrd for 2.6 kernels.\n"
@@ -941,13 +941,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:758
+#: preseed.xml:762
 #, no-c-format
 msgid "Boot loader installation"
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:760
+#: preseed.xml:764
 #, no-c-format
 msgid ""
       "# Grub is the default boot loader (for x86). If you want lilo installed\n"
@@ -972,97 +972,97 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:765
+#: preseed.xml:769
 #, no-c-format
 msgid "Package selection"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:766
+#: preseed.xml:770
 #, no-c-format
 msgid "You can choose to install any combination of tasks that are available. Available tasks as of this writing include:"
 msgstr ""
 
 #. Tag: userinput
-#: preseed.xml:775
+#: preseed.xml:779
 #, no-c-format
 msgid "standard"
 msgstr ""
 
 #. Tag: userinput
-#: preseed.xml:778
+#: preseed.xml:782
 #, no-c-format
 msgid "desktop"
 msgstr ""
 
 #. Tag: userinput
-#: preseed.xml:781
+#: preseed.xml:785
 #, no-c-format
 msgid "gnome-desktop"
 msgstr ""
 
 #. Tag: userinput
-#: preseed.xml:784
+#: preseed.xml:788
 #, no-c-format
 msgid "kde-desktop"
 msgstr ""
 
 #. Tag: userinput
-#: preseed.xml:787
+#: preseed.xml:791
 #, no-c-format
 msgid "web-server"
 msgstr ""
 
 #. Tag: userinput
-#: preseed.xml:790
+#: preseed.xml:794
 #, no-c-format
 msgid "print-server"
 msgstr ""
 
 #. Tag: userinput
-#: preseed.xml:793
+#: preseed.xml:797
 #, no-c-format
 msgid "dns-server"
 msgstr ""
 
 #. Tag: userinput
-#: preseed.xml:796
+#: preseed.xml:800
 #, no-c-format
 msgid "file-server"
 msgstr ""
 
 #. Tag: userinput
-#: preseed.xml:799
+#: preseed.xml:803
 #, no-c-format
 msgid "mail-server"
 msgstr ""
 
 #. Tag: userinput
-#: preseed.xml:802
+#: preseed.xml:806
 #, no-c-format
 msgid "sql-database"
 msgstr ""
 
 #. Tag: userinput
-#: preseed.xml:805
+#: preseed.xml:809
 #, no-c-format
 msgid "laptop"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:809
+#: preseed.xml:813
 #, no-c-format
 msgid "You can also choose to install no tasks, and force the installation of a set of packages in some other way. We recommend always including the <userinput>standard</userinput> task."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:815
+#: preseed.xml:819
 #, no-c-format
 msgid "If you want to install some individual packages in addition to packages installed by tasks, you can use the parameter <classname>pkgsel/include</classname>. The value of this parameter can be either comma-separated or space-separated, so you can also use it easily on the kernel command line."
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:825
+#: preseed.xml:829
 #, no-c-format
 msgid ""
       "tasksel tasksel/first multiselect standard, desktop\n"
@@ -1080,13 +1080,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:830
+#: preseed.xml:834
 #, no-c-format
 msgid "Finishing up the first stage install"
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:832
+#: preseed.xml:836
 #, no-c-format
 msgid ""
       "# Avoid that last message about the install being complete.\n"
@@ -1098,19 +1098,19 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:837
+#: preseed.xml:841
 #, no-c-format
 msgid "Mailer configuration"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:838
+#: preseed.xml:842
 #, no-c-format
 msgid "During a normal install, exim asks only a few questions. Here's how to avoid even those. More complicated preseeding is possible."
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:845
+#: preseed.xml:849
 #, no-c-format
 msgid ""
       "exim4-config exim4/dc_eximconfig_configtype \\\n"
@@ -1121,19 +1121,19 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:850
+#: preseed.xml:854
 #, no-c-format
 msgid "X configuration"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:851
+#: preseed.xml:855
 #, no-c-format
 msgid "Preseeding Debian's X config is possible, but you probably need to know some details about the video hardware of the machine, since Debian's X configurator does not do fully automatic configuration of everything."
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:859
+#: preseed.xml:863
 #, no-c-format
 msgid ""
       "# X can detect the right driver for some cards, but if you're preseeding,\n"
@@ -1159,13 +1159,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:864
+#: preseed.xml:868
 #, no-c-format
 msgid "Preseeding other packages"
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:866
+#: preseed.xml:870
 #, no-c-format
 msgid ""
       "# Depending on what software you choose to install, or if things go wrong\n"
@@ -1178,19 +1178,19 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:872
+#: preseed.xml:876
 #, no-c-format
 msgid "Advanced options"
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:875
+#: preseed.xml:879
 #, no-c-format
 msgid "Shell commands"
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:877
+#: preseed.xml:881
 #, no-c-format
 msgid ""
       "# d-i preseeding is inherently not secure. Nothing in the installer checks\n"
@@ -1212,19 +1212,19 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:882
+#: preseed.xml:886
 #, no-c-format
 msgid "Chainloading preconfiguration files"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:883
+#: preseed.xml:887
 #, no-c-format
 msgid "It is possible to include other preconfiguration files from a preconfiguration file. Any settings in those files will override pre-existing settings from files loaded earlier. This makes it possible to put, for example, general networking settings for your location in one file and more specific settings for certain configurations in other files."
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:893
+#: preseed.xml:897
 #, no-c-format
 msgid ""
       "# More that one file can be listed, separated by spaces; all will be\n"
diff --git a/po/pot/random-bits.pot b/po/pot/random-bits.pot
index af9180681..dfd41571d 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: 2006-10-11 02:03+0000\n"
+"POT-Creation-Date: 2006-10-29 14:49+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"
@@ -375,251 +375,275 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:189
 #, no-c-format
-msgid "The base installation for i386 using the default 2.4 kernel, including all standard packages, requires 573MB of disk space."
+msgid "The base installation for i386 using the default 2.6 kernel, including all standard packages, requires 585MB of disk space. A minimal base installation, without the standard task selected, will take 365MB."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:194
+#: random-bits.xml:196
 #, no-c-format
 msgid "The following table lists sizes reported by aptitude for the tasks listed in tasksel. Note that some tasks have overlapping constituents, so the total installed size for two tasks together may be less than the total obtained by adding up the numbers."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:201
+#: random-bits.xml:203
 #, no-c-format
 msgid "Note that you will need to add the sizes listed in the table to the size of the base installation when determining the size of partitions. Most of the size listed as <quote>Installed size</quote> will end up in <filename>/usr</filename>; the size listed as <quote>Download size</quote> is (temporarily) required in <filename>/var</filename>."
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:214
+#: random-bits.xml:216
 #, no-c-format
 msgid "Task"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:215
+#: random-bits.xml:217
 #, no-c-format
 msgid "Installed size (MB)"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:216
+#: random-bits.xml:218
 #, no-c-format
 msgid "Download size (MB)"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:217
+#: random-bits.xml:219
 #, no-c-format
 msgid "Space needed to install (MB)"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:223
+#: random-bits.xml:225
 #, no-c-format
 msgid "Desktop"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:224
+#: random-bits.xml:226
 #, no-c-format
-msgid "1392"
+msgid "1258"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:225
+#: random-bits.xml:227
 #, no-c-format
-msgid "<entry>460</entry>"
+msgid "<entry>418</entry>"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:226
+#: random-bits.xml:228
 #, no-c-format
-msgid "1852"
+msgid "1676"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:230
+#: random-bits.xml:232
 #, no-c-format
-msgid "Web server"
+msgid "Laptop"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:231
+#: random-bits.xml:233 random-bits.xml:242
 #, no-c-format
-msgid "<entry>36</entry>"
+msgid "<entry>46</entry>"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:232
+#: random-bits.xml:234
 #, no-c-format
-msgid "<entry>12</entry>"
+msgid "<entry>16</entry>"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:233
+#: random-bits.xml:235
 #, no-c-format
-msgid "<entry>48</entry>"
+msgid "<entry>62</entry>"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:237
+#: random-bits.xml:239
+#, no-c-format
+msgid "Web server"
+msgstr ""
+
+#. Tag: entry
+#: random-bits.xml:240
+#, no-c-format
+msgid "<entry>35</entry>"
+msgstr ""
+
+#. Tag: entry
+#: random-bits.xml:241
+#, no-c-format
+msgid "<entry>11</entry>"
+msgstr ""
+
+#. Tag: entry
+#: random-bits.xml:246
 #, no-c-format
 msgid "Print server"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:238
+#: random-bits.xml:247
 #, no-c-format
-msgid "<entry>168</entry>"
+msgid "<entry>326</entry>"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:239
+#: random-bits.xml:248
 #, no-c-format
-msgid "<entry>58</entry>"
+msgid "<entry>95</entry>"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:240
+#: random-bits.xml:249
 #, no-c-format
-msgid "<entry>226</entry>"
+msgid "<entry>421</entry>"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:244
+#: random-bits.xml:253
 #, no-c-format
 msgid "DNS server"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:245
+#: random-bits.xml:254
 #, no-c-format
 msgid "<entry>2</entry>"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:246
+#: random-bits.xml:255
 #, no-c-format
 msgid "<entry>1</entry>"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:247 random-bits.xml:260
+#: random-bits.xml:256
 #, no-c-format
 msgid "<entry>3</entry>"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:251
+#: random-bits.xml:260
 #, no-c-format
 msgid "File server"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:252
+#: random-bits.xml:261
 #, no-c-format
-msgid "<entry>47</entry>"
+msgid "<entry>50</entry>"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:253
+#: random-bits.xml:262
 #, no-c-format
-msgid "<entry>24</entry>"
+msgid "<entry>21</entry>"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:254
+#: random-bits.xml:263
 #, no-c-format
 msgid "<entry>71</entry>"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:258
+#: random-bits.xml:267
 #, no-c-format
 msgid "Mail server"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:259
+#: random-bits.xml:268
+#, no-c-format
+msgid "<entry>13</entry>"
+msgstr ""
+
+#. Tag: entry
+#: random-bits.xml:269
 #, no-c-format
-msgid "<entry>10</entry>"
+msgid "<entry>5</entry>"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:261
+#: random-bits.xml:270
 #, no-c-format
-msgid "<entry>13</entry>"
+msgid "<entry>18</entry>"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:265
+#: random-bits.xml:274
 #, no-c-format
 msgid "SQL database"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:266
+#: random-bits.xml:275
 #, no-c-format
-msgid "<entry>66</entry>"
+msgid "<entry>24</entry>"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:267
+#: random-bits.xml:276
 #, no-c-format
-msgid "<entry>21</entry>"
+msgid "<entry>8</entry>"
 msgstr ""
 
 #. Tag: entry
-#: random-bits.xml:268
+#: random-bits.xml:277
 #, no-c-format
-msgid "<entry>87</entry>"
+msgid "<entry>32</entry>"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:274
+#: random-bits.xml:283
 #, no-c-format
-msgid "The <emphasis>Desktop</emphasis> task will install both the GNOME and KDE desktop environments."
+msgid "The <emphasis>Desktop</emphasis> task will install the GNOME desktop environment."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:281
+#: random-bits.xml:290
 #, no-c-format
 msgid "If you install in a language other than English, <command>tasksel</command> may automatically install a <firstterm>localization task</firstterm>, if one is available for your language. Space requirements differ per language; you should allow up to 200MB in total for download and installation."
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:296
+#: random-bits.xml:305
 #, no-c-format
 msgid "Installing &debian; from a Unix/Linux System"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:298
+#: random-bits.xml:307
 #, no-c-format
 msgid "This section explains how to install &debian; from an existing Unix or Linux system, without using the menu-driven installer as explained in the rest of the manual. This <quote>cross-install</quote> HOWTO has been requested by users switching to &debian; from Red Hat, Mandrake, and SUSE. In this section some familiarity with entering *nix commands and navigating the file system is assumed. In this section, <prompt>$</prompt> symbolizes a command to be entered in the user's current system, while <prompt>#</prompt> refers to a command entered in the Debian chroot."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:310
+#: random-bits.xml:319
 #, no-c-format
 msgid "Once you've got the new Debian system configured to your preference, you can migrate your existing user data (if any) to it, and keep on rolling. This is therefore a <quote>zero downtime</quote> &debian; install. It's also a clever way for dealing with hardware that otherwise doesn't play friendly with various boot or installation media."
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:322
+#: random-bits.xml:331
 #, no-c-format
 msgid "Getting Started"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:323
+#: random-bits.xml:332
 #, no-c-format
 msgid "With your current *nix partitioning tools, repartition the hard drive as needed, creating at least one filesystem plus swap. You need at least 150MB of space available for a console only install, or at least 300MB if you plan to install X."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:330
+#: random-bits.xml:339
 #, no-c-format
 msgid ""
       "Create file systems on your partitions. For example, to create an ext3 file system on partition <filename>/dev/hda6</filename> (that's our example root partition): <informalexample><screen>\n"
@@ -628,7 +652,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:340
+#: random-bits.xml:349
 #, no-c-format
 msgid ""
       "Initialize and activate swap (substitute the partition number for your intended Debian swap partition): <informalexample><screen>\n"
@@ -639,7 +663,7 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:352
+#: random-bits.xml:361
 #, no-c-format
 msgid ""
       "# mkdir /mnt/debinst\n"
@@ -647,25 +671,25 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:355
+#: random-bits.xml:364
 #, no-c-format
 msgid "If you want to have parts of the filesystem (e.g. /usr) mounted on separate partitions, you will need to create and mount these directories manually before proceding with the next stage."
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:365
+#: random-bits.xml:374
 #, no-c-format
 msgid "Install <command>debootstrap</command>"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:366
+#: random-bits.xml:375
 #, no-c-format
 msgid "The utility used by the Debian installer, and recognized as the official way to install a Debian base system, is <command>debootstrap</command>. It uses <command>wget</command> and <command>ar</command>, but otherwise depends only on <classname>/bin/sh</classname> and basic Unix/Linux tools<footnote> <para> These include the GNU core utilities and commands like <command>sed</command>, <command>grep</command>, <command>tar</command> and <command>gzip</command>. </para> </footnote>. Install <command>wget</command> and <command>ar</command> if they aren't already on your current system, then download and install <command>debootstrap</command>."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:396
+#: random-bits.xml:405
 #, no-c-format
 msgid ""
       "Or, you can use the following procedure to install it manually. Make a work folder for extracting the .deb into: <informalexample><screen>\n"
@@ -675,7 +699,7 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:411
+#: random-bits.xml:420
 #, no-c-format
 msgid ""
       "# ar -x debootstrap_0.X.X_all.deb\n"
@@ -684,31 +708,31 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:417
+#: random-bits.xml:426
 #, no-c-format
 msgid "Run <command>debootstrap</command>"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:418
+#: random-bits.xml:427
 #, no-c-format
 msgid "<command>debootstrap</command> can download the needed files directly from the archive when you run it. You can substitute any Debian archive mirror for <userinput>http.us.debian.org/debian</userinput> in the command example below, preferably a mirror close to you network-wise. Mirrors are listed at <ulink url=\"http://www.debian.org/misc/README.mirrors\"></ulink>."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:427
+#: random-bits.xml:436
 #, no-c-format
 msgid "If you have a &releasename; &debian; CD mounted at <filename>/cdrom</filename>, you could substitute a file URL instead of the http URL: <userinput>file:/cdrom/debian/</userinput>"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:433
+#: random-bits.xml:442
 #, no-c-format
 msgid "Substitute one of the following for <replaceable>ARCH</replaceable> in the <command>debootstrap</command> command: <userinput>alpha</userinput>, <userinput>arm</userinput>, <userinput>hppa</userinput>, <userinput>i386</userinput>, <userinput>ia64</userinput>, <userinput>m68k</userinput>, <userinput>mips</userinput>, <userinput>mipsel</userinput>, <userinput>powerpc</userinput>, <userinput>s390</userinput>, or <userinput>sparc</userinput>."
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:450
+#: random-bits.xml:459
 #, no-c-format
 msgid ""
       "# /usr/sbin/debootstrap --arch ARCH &releasename; \\\n"
@@ -716,31 +740,31 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:456
+#: random-bits.xml:465
 #, no-c-format
 msgid "Configure The Base System"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:457
+#: random-bits.xml:466
 #, no-c-format
 msgid "Now you've got a real Debian system, though rather lean, on disk. <command>Chroot</command> into it:"
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:462
+#: random-bits.xml:471
 #, no-c-format
 msgid "# LANG= chroot /mnt/debinst /bin/bash"
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:467
+#: random-bits.xml:476
 #, no-c-format
 msgid "Mount Partitions"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:468
+#: random-bits.xml:477
 #, no-c-format
 msgid ""
       "You need to create <filename>/etc/fstab</filename>. <informalexample><screen>\n"
@@ -768,55 +792,55 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:488
+#: random-bits.xml:497
 #, no-c-format
 msgid "# mount -t proc proc /proc"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:490
+#: random-bits.xml:499
 #, no-c-format
 msgid "The command <userinput>ls /proc</userinput> should now show a non-empty directory. Should this fail, you may be able to mount proc from outside the chroot:"
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:496
+#: random-bits.xml:505
 #, no-c-format
 msgid "# mount -t proc proc /mnt/debinst/proc"
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:502
+#: random-bits.xml:511
 #, no-c-format
 msgid "Configure Keyboard"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:503
+#: random-bits.xml:512
 #, no-c-format
 msgid "To configure your keyboard:"
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:507
+#: random-bits.xml:516
 #, no-c-format
 msgid "# dpkg-reconfigure console-data"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:509
+#: random-bits.xml:518
 #, no-c-format
 msgid "Note that the keyboard cannot be set while in the chroot, but will be configured for the next reboot."
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:518
+#: random-bits.xml:527
 #, no-c-format
 msgid "Configure Networking"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:519
+#: random-bits.xml:528
 #, no-c-format
 msgid ""
       "To configure networking, edit <filename>/etc/network/interfaces</filename>, <filename>/etc/resolv.conf</filename>, <filename>/etc/hostname</filename> and <filename>/etc/hosts</filename>. <informalexample><screen>\n"
@@ -859,13 +883,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:556
+#: random-bits.xml:565
 #, no-c-format
 msgid "Configure Locales"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:557
+#: random-bits.xml:566
 #, no-c-format
 msgid ""
       "To configure your locale settings to use a language other than English, install the <classname>locales</classname> support package and configure it: <informalexample><screen>\n"
@@ -875,13 +899,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:575
+#: random-bits.xml:584
 #, no-c-format
 msgid "Install a Kernel"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:576
+#: random-bits.xml:585
 #, no-c-format
 msgid ""
       "If you intend to boot this system, you probably want a Linux kernel and a boot loader. Identify available pre-packaged kernels with <informalexample><screen>\n"
@@ -890,37 +914,37 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:585
+#: random-bits.xml:594
 #, no-c-format
 msgid "# aptitude install linux-image-<replaceable>&kernelversion;-arch-etc</replaceable>"
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:591
+#: random-bits.xml:600
 #, no-c-format
 msgid "Set up the Boot Loader"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:592
+#: random-bits.xml:601
 #, no-c-format
 msgid "To make your &debian; system bootable, set up your boot loader to load the installed kernel with your new root partition. Note that <command>debootstrap</command> does not install a boot loader, though you can use <command>aptitude</command> inside your Debian chroot to do so."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:599
+#: random-bits.xml:608
 #, no-c-format
 msgid "Check <userinput>info grub</userinput> or <userinput>man lilo.conf</userinput> for instructions on setting up the bootloader. If you are keeping the system you used to install Debian, just add an entry for the Debian install to your existing grub <filename>menu.lst</filename> or <filename>lilo.conf</filename>. For <filename>lilo.conf</filename>, you could also copy it to the new system and edit it there. After you are done editing, call lilo (remember it will use <filename>lilo.conf</filename> relative to the system you call it from)."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:610
+#: random-bits.xml:619
 #, no-c-format
 msgid "Here is a basic <filename>/etc/lilo.conf</filename> as an example:"
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:614
+#: random-bits.xml:623
 #, no-c-format
 msgid ""
       "boot=/dev/hda6\n"
@@ -933,13 +957,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:616
+#: random-bits.xml:625
 #, no-c-format
 msgid "Check <userinput>man yaboot.conf</userinput> for instructions on setting up the bootloader. If you are keeping the system you used to install Debian, just add an entry for the Debian install to your existing <filename>yaboot.conf</filename>. You could also copy it to the new system and edit it there. After you are done editing, call ybin (remember it will use <filename>yaboot.conf</filename> relative to the system you call it from)."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:626
+#: random-bits.xml:635
 #, no-c-format
 msgid ""
       "Here is a basic <filename>/etc/yaboot.conf</filename> as an example: <informalexample><screen>\n"
@@ -955,79 +979,79 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:644
+#: random-bits.xml:653
 #, no-c-format
 msgid "Installing &debian; over Parallel Line IP (PLIP)"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:646
+#: random-bits.xml:655
 #, no-c-format
 msgid "This section explains how to install &debian; 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:654
+#: random-bits.xml:663
 #, 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:662
+#: random-bits.xml:671
 #, 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:667
+#: random-bits.xml:676
 #, 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:677
+#: random-bits.xml:686
 #, no-c-format
 msgid "Requirements"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:680
+#: random-bits.xml:689
 #, no-c-format
 msgid "A target computer, called <emphasis>target</emphasis>, where Debian will be installed."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:686
+#: random-bits.xml:695
 #, no-c-format
 msgid "System installation media; see <xref linkend=\"installation-media\"/>."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:691
+#: random-bits.xml:700
 #, 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:697
+#: random-bits.xml:706
 #, 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:709
+#: random-bits.xml:718
 #, no-c-format
 msgid "Setting up source"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:710
+#: random-bits.xml:719
 #, 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:715
+#: random-bits.xml:724
 #, no-c-format
 msgid ""
       "#!/bin/sh\n"
@@ -1048,13 +1072,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:721
+#: random-bits.xml:730
 #, no-c-format
 msgid "Installing target"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:722
+#: random-bits.xml:731
 #, 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"
@@ -1063,61 +1087,61 @@ msgid ""
 msgstr ""
 
 #. Tag: guimenuitem
-#: random-bits.xml:741
+#: random-bits.xml:750
 #, no-c-format
 msgid "Load installer components from CD"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:743
+#: random-bits.xml:752
 #, 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:751
+#: random-bits.xml:760
 #, no-c-format
 msgid "Detect network hardware"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:756
+#: random-bits.xml:765
 #, 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:765
+#: random-bits.xml:774
 #, 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:777
+#: random-bits.xml:786
 #, no-c-format
 msgid "Configure the network"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:780
+#: random-bits.xml:789
 #, no-c-format
 msgid "Auto-configure network with DHCP: No"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:785
+#: random-bits.xml:794
 #, no-c-format
 msgid "IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:790
+#: random-bits.xml:799
 #, no-c-format
 msgid "Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></userinput>"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:796
+#: random-bits.xml:805
 #, no-c-format
 msgid "Name server addresses: you can enter the same addresses used on source (see <filename>/etc/resolv.conf</filename>)"
 msgstr ""
diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot
index 210d06330..0fa122853 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: 2006-10-26 16:20+0000\n"
+"POT-Creation-Date: 2006-10-29 14:49+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"
@@ -548,242 +548,242 @@ msgstr ""
 msgid "There are two keyboard layouts for US keyboards; the qwerty/mac-usb-us (Apple USB) layout will place the Alt function on the <keycap>Command/Apple</keycap> key (in the keyboard position next to the <keycap>space</keycap> key similar to <keycap>Alt</keycap> on PC keyboards), while the qwerty/us (Standard) layout will place the Alt function on the <keycap>Option</keycap> key (engraved with 'alt' on most Mac keyboards). In other respects the two layouts are similar."
 msgstr ""
 
-#. Tag: para
-#: using-d-i.xml:564
-#, no-c-format
-msgid "If you are installing on a system that has a Sun USB keyboard and have booted the installer with the default 2.4 kernel, the keyboard will not be identified correctly by the installation system. The installer will show you a list of Sun type keymaps to choose from, but selecting one of these will result in a non-working keyboard. If you are installing with the 2.6 kernel, there is no problem."
-msgstr ""
-
-#. Tag: para
-#: using-d-i.xml:573
-#, no-c-format
-msgid "To get a working keyboard, you should boot the installer with parameter <userinput>priority=medium</userinput>. When you get to keyboard selection<footnote> <para> If you are installing at default priority you should use the <userinput>Go Back</userinput> button to return to the installer menu when you are shown the list of Sun type keymaps. </para> </footnote>, choose <quote>No keyboard to configure</quote> if you have a keyboard with an American (US) layout, or choose <quote>USB keyboard</quote> if you have a keyboard with a localized layout. Selecting <quote>No keyboard to configure</quote> will leave the kernel keymap in place, which is correct for US keyboards."
-msgstr ""
-
 #. Tag: title
-#: using-d-i.xml:611
+#: using-d-i.xml:582
 #, no-c-format
 msgid "Looking for the Debian Installer ISO Image"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:612
+#: using-d-i.xml:583
 #, 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:619
+#: using-d-i.xml:590
 #, 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:636
+#: using-d-i.xml:607
 #, 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:643
+#: using-d-i.xml:614
 #, 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:664
+#: using-d-i.xml:635
 #, no-c-format
 msgid "Configuring Network"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:666
+#: using-d-i.xml:637
 #, 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: para
-#: using-d-i.xml:677
+#: using-d-i.xml:648
 #, no-c-format
 msgid "By default, &d-i; tries to configure your computer's network automatically via DHCP. If the DHCP probe succeeds, you are done. If the probe fails, it may be caused by many factors ranging from unplugged network cable, to a misconfigured DHCP setup. Or maybe you don't have a DHCP server in your local network at all. For further explanation check the error messages on the third console. In any case, you will be asked if you want to retry, or if you want to perform manual setup. DHCP servers are sometimes really slow in their responses, so if you are sure everything is in place, try again."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:689
+#: using-d-i.xml:660
 #, 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> and a <computeroutput>WEP key</computeroutput>. Fill in the answers from <xref linkend=\"needed-info\"/>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:703
+#: using-d-i.xml:674
 #, 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. It will guess the broadcast address is 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 system's guesses &mdash; you can change them once the system has been installed, if necessary, by editing <filename>/etc/network/interfaces</filename>. Alternatively, you can install <classname>etherconf</classname>, which will step you through your network setup."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:742
+#: using-d-i.xml:713
 #, no-c-format
 msgid "Partitioning and Mount Point Selection"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:743
+#: using-d-i.xml:714
 #, 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 issues like LVM or RAID devices."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:765
+#: using-d-i.xml:736
 #, no-c-format
 msgid "Partitioning Your Disks"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:767
+#: using-d-i.xml:738
 #, no-c-format
 msgid "Now it is time to partition your disks. If you are uncomfortable with partitioning, or just want to know more details, see <xref linkend=\"partitioning\"/>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:773
+#: using-d-i.xml:744
 #, 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: para
-#: using-d-i.xml:780
+#: using-d-i.xml:751
 #, 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. Note: the option to use (encrypted) LVM may not be available on all architectures."
+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:788
+#: using-d-i.xml:766
+#, no-c-format
+msgid "The option to use (encrypted) LVM may not be available on all architectures."
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:771
 #, 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:798
+#: using-d-i.xml:780
+#, 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:789
 #, 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:808
+#: using-d-i.xml:799
 #, no-c-format
 msgid "If you choose guided partitioning (either classic or using (encrypted) LVM) 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:817
+#: using-d-i.xml:808
 #, 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. 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."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:825
+#: using-d-i.xml:816
 #, 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:841
+#: using-d-i.xml:832
 #, no-c-format
 msgid "Partitioning scheme"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:842
+#: using-d-i.xml:833
 #, no-c-format
 msgid "Minimum space"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:843
+#: using-d-i.xml:834
 #, no-c-format
 msgid "Created partitions"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:849
+#: using-d-i.xml:840
 #, no-c-format
 msgid "All files in one partition"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:850
+#: using-d-i.xml:841
 #, no-c-format
 msgid "600MB"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:851
+#: using-d-i.xml:842
 #, no-c-format
 msgid "<filename>/</filename>, swap"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:853
+#: using-d-i.xml:844
 #, no-c-format
 msgid "Separate /home partition"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:854
+#: using-d-i.xml:845
 #, no-c-format
 msgid "500MB"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:855
+#: using-d-i.xml:846
 #, no-c-format
 msgid "<filename>/</filename>, <filename>/home</filename>, swap"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:859
+#: using-d-i.xml:850
 #, no-c-format
 msgid "Separate /home, /usr, /var and /tmp partitions"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:860
+#: using-d-i.xml:851
 #, no-c-format
 msgid "<entry>1GB</entry>"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:861
+#: using-d-i.xml:852
 #, 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:870
+#: using-d-i.xml:861
 #, 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, except for the swap partition, will be created inside the LVM partition."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:876
+#: using-d-i.xml:867
 #, no-c-format
 msgid "If you choose guided partitioning for your IA64 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:884
+#: using-d-i.xml:875
 #, no-c-format
 msgid "If you choose guided partitioning for your Alpha system, an additional, unformatted partition will be allocated at the beginning of your disk to reserve this space for the aboot boot loader."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:890
+#: using-d-i.xml:881
 #, 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:896
+#: using-d-i.xml:887
 #, no-c-format
 msgid ""
       "The list of partitions might look like this: <informalexample><screen>\n"
@@ -806,559 +806,559 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:909
+#: using-d-i.xml:900
 #, 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: para
-#: using-d-i.xml:919
+#: using-d-i.xml:910
 #, 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 setup 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:927
+#: using-d-i.xml:918
 #, no-c-format
 msgid "If you select a pristine disk which has neither partitions nor free space on it, you will be offered to create a new partition table (this is needed so you can create new partitions). After this a new line entitled <quote>FREE SPACE</quote> should appear under the selected disk."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:935
+#: using-d-i.xml:926
 #, no-c-format
 msgid "If you select some free space, you will be offered to create 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 detailed overview of your new partition. There are options like mountpoint, mount options, bootable flag, or way of usage. 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 different filesystem for this partition including the possibility to use the partition for swap, software RAID, LVM, or not use it at all. Other nice feature is the possibility to copy data from existing partition onto this one. When you are satisfied with your new partition, select <guimenuitem>Done setting up the partition</guimenuitem> and you will be thrown back to <command>partman</command>'s main screen."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:953
+#: using-d-i.xml:944
 #, 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. Because this is the same screen like when creating a new partition, you can change the same set of options. One thing which might 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:964
+#: using-d-i.xml:955
 #, 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:972
+#: using-d-i.xml:963
 #, 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:978
+#: using-d-i.xml:969
 #, 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:986
+#: using-d-i.xml:977
 #, 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:1014
+#: using-d-i.xml:1005
 #, no-c-format
 msgid "Configuring Multidisk Device (Software RAID)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1015
+#: using-d-i.xml:1006
 #, no-c-format
 msgid "If you have more than one harddrive<footnote><para> To be honest, you can construct MD device even from partitions residing on single physical drive, but that won't bring you anything useful. </para></footnote> in your computer, you can use <command>mdcfg</command> to setup 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:1029
+#: using-d-i.xml:1020
 #, 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:1037
+#: using-d-i.xml:1028
 #, no-c-format
 msgid "The benefit you gain depends on a type of a 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 loose <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 incomming data into stripes and distributes them equally on all but one disks (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 similar degree of reliability like RAID1 while achieving less redundancy. On the other hand it might be a bit slower on write operation than RAID0 due to computation of parity information. </para></listitem> </varlistentry> </variablelist> To sum it up:"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1115
+#: using-d-i.xml:1106
 #, no-c-format
 msgid "Type"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1116
+#: using-d-i.xml:1107
 #, no-c-format
 msgid "Minimum Devices"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1117
+#: using-d-i.xml:1108
 #, no-c-format
 msgid "Spare Device"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1118
+#: using-d-i.xml:1109
 #, no-c-format
 msgid "Survives disk failure?"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1119
+#: using-d-i.xml:1110
 #, no-c-format
 msgid "Available Space"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1125
+#: using-d-i.xml:1116
 #, no-c-format
 msgid "RAID0"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1126 using-d-i.xml:1134
+#: using-d-i.xml:1117 using-d-i.xml:1125
 #, no-c-format
 msgid "<entry>2</entry>"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1127 using-d-i.xml:1128
+#: using-d-i.xml:1118 using-d-i.xml:1119
 #, no-c-format
 msgid "<entry>no</entry>"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1129
+#: using-d-i.xml:1120
 #, no-c-format
 msgid "Size of the smallest partition multiplied by number of devices in RAID"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1133
+#: using-d-i.xml:1124
 #, no-c-format
 msgid "RAID1"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1135 using-d-i.xml:1143
+#: using-d-i.xml:1126 using-d-i.xml:1134
 #, no-c-format
 msgid "optional"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1136 using-d-i.xml:1144
+#: using-d-i.xml:1127 using-d-i.xml:1135
 #, no-c-format
 msgid "<entry>yes</entry>"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1137
+#: using-d-i.xml:1128
 #, no-c-format
 msgid "Size of the smallest partition in RAID"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1141
+#: using-d-i.xml:1132
 #, no-c-format
 msgid "RAID5"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1142
+#: using-d-i.xml:1133
 #, no-c-format
 msgid "<entry>3</entry>"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1145
+#: using-d-i.xml:1136
 #, no-c-format
 msgid "Size of the smallest partition multiplied by (number of devices in RAID minus one)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1153
+#: using-d-i.xml:1144
 #, no-c-format
 msgid "If you want to know the whole truth about Software RAID, have a look at <ulink url=\"&url-software-raid-howto;\">Software RAID HOWTO</ulink>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1158
+#: using-d-i.xml:1149
 #, 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:1167
+#: using-d-i.xml:1158
 #, 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>) filesystem. 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:1176
+#: using-d-i.xml:1167
 #, 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:1189
+#: using-d-i.xml:1180
 #, 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:1196
+#: using-d-i.xml:1187
 #, 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:1208
+#: using-d-i.xml:1199
 #, no-c-format
 msgid "RAID5 has 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:1216
+#: using-d-i.xml:1207
 #, 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 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:1225
+#: using-d-i.xml:1216
 #, 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:1240
+#: using-d-i.xml:1231
 #, no-c-format
 msgid "Configuring the Logical Volume Manager (LVM)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1241
+#: using-d-i.xml:1232
 #, 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:1249
+#: using-d-i.xml:1240
 #, 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:1259
+#: using-d-i.xml:1250
 #, 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:1270
+#: using-d-i.xml:1261
 #, 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:1279
+#: using-d-i.xml:1270
 #, 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:1290
+#: using-d-i.xml:1281
 #, 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:1295
+#: using-d-i.xml:1286
 #, no-c-format
 msgid "Create volume group"
 msgstr ""
 
 #. Tag: guimenuitem
-#: using-d-i.xml:1298
+#: using-d-i.xml:1289
 #, no-c-format
 msgid "Create logical volume"
 msgstr ""
 
 #. Tag: guimenuitem
-#: using-d-i.xml:1301
+#: using-d-i.xml:1292
 #, no-c-format
 msgid "Delete volume group"
 msgstr ""
 
 #. Tag: guimenuitem
-#: using-d-i.xml:1304
+#: using-d-i.xml:1295
 #, no-c-format
 msgid "Delete logical volume"
 msgstr ""
 
 #. Tag: guimenuitem
-#: using-d-i.xml:1307
+#: using-d-i.xml:1298
 #, no-c-format
 msgid "Extend volume group"
 msgstr ""
 
 #. Tag: guimenuitem
-#: using-d-i.xml:1310
+#: using-d-i.xml:1301
 #, no-c-format
 msgid "Reduce volume group"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1312
+#: using-d-i.xml:1303
 #, no-c-format
 msgid "<guimenuitem>Finish</guimenuitem>: return to the main <command>partman</command> screen"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1318
+#: using-d-i.xml:1309
 #, 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:1324
+#: using-d-i.xml:1315
 #, no-c-format
 msgid "You can also use this menu to delete an existing LVM configuration from your hard disk before choosing <quote>Guided partitioning using LVM</quote>. Guided partitioning using LVM is not possible if there already are volume groups defined, but by removing them you can get a clean start."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1332
+#: using-d-i.xml:1323
 #, 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:1346
+#: using-d-i.xml:1337
 #, no-c-format
 msgid "Configuring Encrypted Volumes"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1347
+#: using-d-i.xml:1338
 #, 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:1359
+#: using-d-i.xml:1350
 #, 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:1374
+#: using-d-i.xml:1365
 #, 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:1381
+#: using-d-i.xml:1372
 #, 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 setting</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:1392
+#: using-d-i.xml:1383
 #, 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:1404
+#: using-d-i.xml:1395
 #, 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:1414
+#: using-d-i.xml:1405
 #, no-c-format
 msgid "Encryption: <userinput>aes</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1416
+#: using-d-i.xml:1407
 #, 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:1434
+#: using-d-i.xml:1425
 #, no-c-format
 msgid "Key size: <userinput>256</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1436
+#: using-d-i.xml:1427
 #, 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:1448
+#: using-d-i.xml:1439
 #, no-c-format
 msgid "IV algorithm: <userinput>cbc-essiv:sha256</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1450
+#: using-d-i.xml:1441
 #, 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:1460
+#: using-d-i.xml:1451
 #, 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:1472
+#: using-d-i.xml:1463
 #, no-c-format
 msgid "Encryption key: <userinput>Passphrase</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1474
+#: using-d-i.xml:1465
 #, no-c-format
 msgid "Here you can choose the type of the encryption key for this partition."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:1480
+#: using-d-i.xml:1471
 #, no-c-format
 msgid "Passphrase"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1481
+#: using-d-i.xml:1472
 #, 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:1496 using-d-i.xml:1589
+#: using-d-i.xml:1487 using-d-i.xml:1580
 #, no-c-format
 msgid "Random key"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1497
+#: using-d-i.xml:1488
 #, 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:1506
+#: using-d-i.xml:1497
 #, 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:1525 using-d-i.xml:1602
+#: using-d-i.xml:1516 using-d-i.xml:1593
 #, no-c-format
 msgid "Erase data: <userinput>yes</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1527
+#: using-d-i.xml:1518
 #, 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:1547
+#: using-d-i.xml:1538
 #, 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:1556
+#: using-d-i.xml:1547
 #, no-c-format
 msgid "Encryption: <userinput>AES256</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1558
+#: using-d-i.xml:1549
 #, 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:1568
+#: using-d-i.xml:1559
 #, no-c-format
 msgid "Encryption key: <userinput>Keyfile (GnuPG)</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1570
+#: using-d-i.xml:1561
 #, no-c-format
 msgid "Here you can select the type of the encryption key for this partition."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:1576
+#: using-d-i.xml:1567
 #, no-c-format
 msgid "Keyfile (GnuPG)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1577
+#: using-d-i.xml:1568
 #, 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:1590
+#: using-d-i.xml:1581
 #, no-c-format
 msgid "Please see the the section on random keys above."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1604
+#: using-d-i.xml:1595
 #, no-c-format
 msgid "Please see the the section on erasing data above."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1613
+#: using-d-i.xml:1604
 #, no-c-format
 msgid "Please note that the <emphasis>graphical</emphasis> version of the installer still has some limitations when compared to the textual one. For cryptography it means you can set up only volumes using <emphasis>passphrases</emphasis> as the encryption keys."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1620
+#: using-d-i.xml:1611
 #, 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:1631
+#: using-d-i.xml:1622
 #, 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:1640
+#: using-d-i.xml:1631
 #, 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:1653
+#: using-d-i.xml:1644
 #, 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:1669
+#: using-d-i.xml:1660
 #, 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"
@@ -1371,577 +1371,577 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1682
+#: using-d-i.xml:1673
 #, 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:1692
+#: using-d-i.xml:1683
 #, no-c-format
 msgid "Once you are satisfied with the partitioning scheme, continue with the installation."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:1703
+#: using-d-i.xml:1694
 #, no-c-format
 msgid "Setting up the System"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1704
+#: using-d-i.xml:1695
 #, no-c-format
 msgid "After partitioning the installer asks a few more questions that will be used to set up the system it is about to install."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:1716
+#: using-d-i.xml:1707
 #, no-c-format
 msgid "Configuring Your Time Zone"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1718
+#: using-d-i.xml:1709
 #, no-c-format
 msgid "Depending on the location selected at the beginning of the installation process, you might be shown a list of timezones relevant for that location. If your location has only one time zone, you will not be asked anything and the system will assume that time zone."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:1734
+#: using-d-i.xml:1725
 #, no-c-format
 msgid "Configuring the Clock"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1736
+#: using-d-i.xml:1727
 #, no-c-format
 msgid "The installer might 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:1743
+#: using-d-i.xml:1734
 #, 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 GMT.</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 GMT.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1754
+#: using-d-i.xml:1745
 #, no-c-format
 msgid "Note that the installer does not currently allow you to actually set the time in the computer's clock. You can set the clock to the current time after you have installed, if it is incorrect or if it was previously not set to UTC."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:1770
+#: using-d-i.xml:1761
 #, no-c-format
 msgid "Setting Up Users And Passwords"
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:1773
+#: using-d-i.xml:1764
 #, no-c-format
 msgid "Set the Root Password"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1775
+#: using-d-i.xml:1766
 #, 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:1783
+#: using-d-i.xml:1774
 #, 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:1791
+#: using-d-i.xml:1782
 #, 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:1801
+#: using-d-i.xml:1792
 #, no-c-format
 msgid "Create an Ordinary User"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1803
+#: using-d-i.xml:1794
 #, 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:1810
+#: using-d-i.xml:1801
 #, 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:1820
+#: using-d-i.xml:1811
 #, 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:1827
+#: using-d-i.xml:1818
 #, 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:1839
+#: using-d-i.xml:1830
 #, no-c-format
 msgid "Installing the Base System"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1840
+#: using-d-i.xml:1831
 #, 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: title
-#: using-d-i.xml:1854
+#: using-d-i.xml:1845
 #, no-c-format
 msgid "Base System Installation"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1856
+#: using-d-i.xml:1847
 #, no-c-format
 msgid "During the Base installation, 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:1866
+#: using-d-i.xml:1857
 #, no-c-format
 msgid "The unpack/setup messages generated by the base installation are saved in <filename>/var/log/syslog</filename> when the installation is performed over a serial console."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1872
+#: using-d-i.xml:1863
 #, 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:1885
+#: using-d-i.xml:1876
 #, no-c-format
 msgid "Installing Additional Software"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1886
+#: using-d-i.xml:1877
 #, no-c-format
 msgid "After the base system is installed, you have a usable but limited system. Most users will want to add additional software to the system to tune it to their needs, and the installer lets you do so. This step can take even longer than installing the base system if you have a slow computer or network."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:1900
+#: using-d-i.xml:1891
 #, no-c-format
 msgid "Configuring apt"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1902
+#: using-d-i.xml:1893
 #, no-c-format
 msgid "The main means that people use to install packages on their system is via a program called <command>apt-get</command>, from the <classname>apt</classname> package.<footnote> <para> Note that the actual program that installs 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 as it will invoke <command>dpkg</command> as appropriate and also because it knows to install other packages which are required for the package you're trying to install, as well as how to retrieve the package from your CD, the network, or wherever. </para> </footnote> Other front-ends for package management, like <command>aptitude</command> and <command>synaptic</command> are also in use and depend on <command>apt-get</command>. 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:1926
+#: using-d-i.xml:1917
 #, no-c-format
 msgid "<command>apt</command> must be configured so that it knows where to retrieve packages from. The installer largely takes care of this automatically based on what it knows about your installation medium. The results of this configuration are written to the file <filename>/etc/apt/sources.list</filename>, and you can examine and edit it to your liking after the install is complete."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:1942
+#: using-d-i.xml:1933
 #, no-c-format
 msgid "Selecting and Installing Software"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1944
+#: using-d-i.xml:1935
 #, 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:1953
+#: using-d-i.xml:1944
 #, 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 (or remove) more packages, 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:1978
+#: using-d-i.xml:1969
 #, no-c-format
 msgid "Once you've selected your tasks, select <guibutton>Ok</guibutton>. At this point, <command>aptitude</command> will install the packages you've selected."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1985
+#: using-d-i.xml:1976
 #, 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:1992
+#: using-d-i.xml:1983
 #, no-c-format
 msgid "Note that some tasks may be pre-selected based on the characteristics of the computer you are installing. If you disagree with these selections you can un-select the tasks. You can even opt to install no tasks at all at this point."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2000
+#: using-d-i.xml:1991
 #, 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:2009
+#: using-d-i.xml:2000
 #, no-c-format
 msgid "Configuring Your Mail Transport Agent"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2011
+#: using-d-i.xml:2002
 #, no-c-format
 msgid "Today, email is a very important part of many people's life, so it's no surprise Debian lets you configure your mail system right as a part of the installation process. The standard mail transport agent in Debian is <command>exim4</command>, which is relatively small, flexible, and easy to learn."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2019
+#: using-d-i.xml:2010
 #, no-c-format
 msgid "You may ask if this is needed even if your computer is not connected to any network. The short answer is: Yes. The longer explanation: Some system utilities (like <command>cron</command>, <command>quota</command>, <command>aide</command>, &hellip;) may send you important notices via email."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2027
+#: using-d-i.xml:2018
 #, no-c-format
 msgid "So on the first screen you will be presented with several common mail scenarios. Choose the one that most closely resembles your needs:"
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:2036
+#: using-d-i.xml:2027
 #, no-c-format
 msgid "internet site"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2037
+#: using-d-i.xml:2028
 #, no-c-format
 msgid "Your system is connected to a network and your mail is sent and received directly using SMTP. On the following screens you will be asked a few basic questions, like your machine's mail name, or a list of domains for which you accept or relay mail."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:2048
+#: using-d-i.xml:2039
 #, no-c-format
 msgid "mail sent by smarthost"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2049
+#: using-d-i.xml:2040
 #, no-c-format
 msgid "In this scenario is your outgoing mail forwarded to another machine, called a <quote>smarthost</quote>, which does the actual job for you. Smarthost also usually stores incoming mail addressed to your computer, so you don't need to be permanently online. That also means you have to download your mail from the smarthost via programs like fetchmail. This option is suitable for dial-up users."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:2062
+#: using-d-i.xml:2053
 #, no-c-format
 msgid "local delivery only"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2063
+#: using-d-i.xml:2054
 #, no-c-format
 msgid "Your system is not on a network and mail is sent or received only between local users. Even if you don't plan to send any messages, this option is highly recommended, because some system utilities may send you various alerts from time to time (e.g. beloved <quote>Disk quota exceeded</quote>). This option is also convenient for new users, because it doesn't ask any further questions."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:2076
+#: using-d-i.xml:2067
 #, no-c-format
 msgid "no configuration at this time"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2077
+#: using-d-i.xml:2068
 #, no-c-format
 msgid "Choose this if you are absolutely convinced you know what you are doing. This will leave you with an unconfigured mail system &mdash; until you configure it, you won't be able to send or receive any mail and you may miss some important messages from your system utilities."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2088
+#: using-d-i.xml:2079
 #, no-c-format
 msgid "If none of these scenarios suits your needs, or if you need a finer setup, you will need to edit configuration files under the <filename>/etc/exim4</filename> directory after the installation is complete. More information about <command>exim4</command> may be found under <filename>/usr/share/doc/exim4</filename>."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2103
+#: using-d-i.xml:2094
 #, no-c-format
 msgid "Making Your System Bootable"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2105
+#: using-d-i.xml:2096
 #, 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 the OpenBoot to boot from the network by default; see <xref linkend=\"boot-dev-select-sun\"/>.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2113
+#: using-d-i.xml:2104
 #, no-c-format
 msgid "Note that multiple operating systems booting on a single machine is still something of a black art. This document does not even attempt to document the various boot managers, which vary by architecture and even by subarchitecture. You should see your boot manager's documentation for more information."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2128
+#: using-d-i.xml:2119
 #, no-c-format
 msgid "Detecting other operating systems"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2130
+#: using-d-i.xml:2121
 #, 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:2138
+#: using-d-i.xml:2129
 #, 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:2156
+#: using-d-i.xml:2147
 #, no-c-format
 msgid "Install <command>aboot</command> on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2157
+#: using-d-i.xml:2148
 #, no-c-format
 msgid "If you have booted from SRM, if 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:2177
+#: using-d-i.xml:2168
 #, no-c-format
 msgid "<command>palo</command>-installer"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2178
+#: using-d-i.xml:2169
 #, 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:2187
+#: using-d-i.xml:2178
 #, no-c-format
 msgid "hppa FIXME ( need more info )"
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2199
+#: using-d-i.xml:2190
 #, no-c-format
 msgid "Install the <command>Grub</command> Boot Loader on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2201
+#: using-d-i.xml:2192
 #, 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 newbies and old hands alike."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2207
+#: using-d-i.xml:2198
 #, 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:2213
+#: using-d-i.xml:2204
 #, no-c-format
 msgid "If you do not want to install grub at all, use the Back 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:2227
+#: using-d-i.xml:2218
 #, no-c-format
 msgid "Install the <command>LILO</command> Boot Loader on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2229
+#: using-d-i.xml:2220
 #, 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:2239
+#: using-d-i.xml:2230
 #, 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:2247
+#: using-d-i.xml:2238
 #, no-c-format
 msgid "&d-i; presents you three choices where to install the <command>LILO</command> boot loader:"
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:2254
+#: using-d-i.xml:2245
 #, no-c-format
 msgid "Master Boot Record (MBR)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2254
+#: using-d-i.xml:2245
 #, 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:2261
+#: using-d-i.xml:2252
 #, no-c-format
 msgid "new Debian partition"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2261
+#: using-d-i.xml:2252
 #, 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:2270
+#: using-d-i.xml:2261
 #, no-c-format
 msgid "Other choice"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2270
+#: using-d-i.xml:2261
 #, 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 devfs style names, such as those that start with <filename>/dev/ide</filename>, <filename>/dev/scsi</filename>, and <filename>/dev/discs</filename>, as well as traditional names, such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2282
+#: using-d-i.xml:2273
 #, 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! For more information on this please read <xref linkend=\"reactivating-win\"/>."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2299
+#: using-d-i.xml:2290
 #, no-c-format
 msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2301
+#: using-d-i.xml:2292
 #, 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 file 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 actually do the work of loading and starting the Linux kernel."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2317
+#: using-d-i.xml:2308
 #, 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:2329
+#: using-d-i.xml:2320
 #, no-c-format
 msgid "Choose the correct partition!"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2331
+#: using-d-i.xml:2322
 #, 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, the <command>elilo</command> may format the partition during the installation, erasing any previous contents!"
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2346
+#: using-d-i.xml:2337
 #, no-c-format
 msgid "EFI Partition Contents"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2348
+#: using-d-i.xml:2339
 #, 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:2370
+#: using-d-i.xml:2361
 #, no-c-format
 msgid "elilo.conf"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2371
+#: using-d-i.xml:2362
 #, 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:2380
+#: using-d-i.xml:2371
 #, no-c-format
 msgid "elilo.efi"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2381
+#: using-d-i.xml:2372
 #, 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:2391
+#: using-d-i.xml:2382
 #, no-c-format
 msgid "initrd.img"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2392
+#: using-d-i.xml:2383
 #, 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:2404
+#: using-d-i.xml:2395
 #, no-c-format
 msgid "readme.txt"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2405
+#: using-d-i.xml:2396
 #, 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:2415
+#: using-d-i.xml:2406
 #, no-c-format
 msgid "vmlinuz"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2416
+#: using-d-i.xml:2407
 #, 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:2436
+#: using-d-i.xml:2427
 #, no-c-format
 msgid "<command>arcboot</command>-installer"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2437
+#: using-d-i.xml:2428
 #, 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"
@@ -1954,61 +1954,61 @@ msgid ""
 msgstr ""
 
 #. Tag: replaceable
-#: using-d-i.xml:2456
+#: using-d-i.xml:2447
 #, no-c-format
 msgid "scsi"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2457
+#: using-d-i.xml:2448
 #, 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:2465
+#: using-d-i.xml:2456
 #, no-c-format
 msgid "disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2466
+#: using-d-i.xml:2457
 #, 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:2474 using-d-i.xml:2543
+#: using-d-i.xml:2465 using-d-i.xml:2534
 #, no-c-format
 msgid "partnr"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2475
+#: using-d-i.xml:2466
 #, 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:2483
+#: using-d-i.xml:2474
 #, no-c-format
 msgid "config"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2484
+#: using-d-i.xml:2475
 #, 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:2505
+#: using-d-i.xml:2496
 #, no-c-format
 msgid "<command>delo</command>-installer"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2506
+#: using-d-i.xml:2497
 #, no-c-format
 msgid ""
       "The boot loader on DECstations is <command>DELO</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). DELO supports different configurations which are set up in <filename>/etc/delo.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After DELO has been installed, the system can be booted from hard disk by entering <informalexample><screen>\n"
@@ -2017,247 +2017,247 @@ msgid ""
 msgstr ""
 
 #. Tag: replaceable
-#: using-d-i.xml:2525
+#: using-d-i.xml:2516
 #, no-c-format
 msgid "<replaceable>#</replaceable>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2526
+#: using-d-i.xml:2517
 #, no-c-format
 msgid "is the TurboChannel device to be booted from, on most DECstations this is <userinput>3</userinput> for the onboard controllers"
 msgstr ""
 
 #. Tag: replaceable
-#: using-d-i.xml:2534
+#: using-d-i.xml:2525
 #, no-c-format
 msgid "<replaceable>id</replaceable>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2535
+#: using-d-i.xml:2526
 #, no-c-format
 msgid "is the SCSI ID of the hard disk on which <command>DELO</command> is installed"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2544
+#: using-d-i.xml:2535
 #, no-c-format
 msgid "is the number of the partition on which <filename>/etc/delo.conf</filename> resides"
 msgstr ""
 
 #. Tag: replaceable
-#: using-d-i.xml:2552
+#: using-d-i.xml:2543
 #, no-c-format
 msgid "name"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2553
+#: using-d-i.xml:2544
 #, no-c-format
 msgid "is the name of the configuration entry in <filename>/etc/delo.conf</filename>, which is <quote>linux</quote> by default."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2563
+#: using-d-i.xml:2554
 #, no-c-format
 msgid "In case <filename>/etc/delo.conf</filename> is on the first partition on the disk and the default configuration shall be booted, it is sufficient to use"
 msgstr ""
 
 #. Tag: screen
-#: using-d-i.xml:2569
+#: using-d-i.xml:2560
 #, no-c-format
 msgid "<userinput>boot #/rz<replaceable>id</replaceable></userinput>"
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2579
+#: using-d-i.xml:2570
 #, no-c-format
 msgid "Install <command>Yaboot</command> on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2580
+#: using-d-i.xml:2571
 #, 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:2598
+#: using-d-i.xml:2589
 #, no-c-format
 msgid "Install <command>Quik</command> on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2599
+#: using-d-i.xml:2590
 #, 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:2615
+#: using-d-i.xml:2606
 #, no-c-format
 msgid "<command>zipl</command>-installer"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2616
+#: using-d-i.xml:2607
 #, 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:2633
+#: using-d-i.xml:2624
 #, no-c-format
 msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2635
+#: using-d-i.xml:2626
 #, 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:2660
+#: using-d-i.xml:2651
 #, no-c-format
 msgid "Continue Without Boot Loader"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2662
+#: using-d-i.xml:2653
 #, 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:2671
+#: using-d-i.xml:2662
 #, 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:2688
+#: using-d-i.xml:2679
 #, no-c-format
 msgid "Finishing the Installation"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2689
+#: using-d-i.xml:2680
 #, no-c-format
 msgid "These are the last bits to do before rebooting to your new system. It mostly consists of tidying up after the &d-i;."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2701
+#: using-d-i.xml:2692
 #, no-c-format
 msgid "Finish the Installation and Reboot"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2703
+#: using-d-i.xml:2694
 #, no-c-format
 msgid "This is the last step in the initial Debian installation process. You will be prompted to remove the boot media (CD, floppy, etc) that you used to boot the installer. The installer will do any last minute tasks, and then reboot into your new Debian system."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2710
+#: using-d-i.xml:2701
 #, no-c-format
 msgid "Select the <guimenuitem>Finish the installation</guimenuitem> menu item which will halt the system because rebooting is not supported on &arch-title; in this case. You then need to IPL GNU/Linux from the DASD which you selected for the root filesystem during the first steps of the installation."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2724
+#: using-d-i.xml:2715
 #, no-c-format
 msgid "Miscellaneous"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2725
+#: using-d-i.xml:2716
 #, 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:2738
+#: using-d-i.xml:2729
 #, no-c-format
 msgid "Saving the installation logs"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2740
+#: using-d-i.xml:2731
 #, 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:2747
+#: using-d-i.xml:2738
 #, 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:2767
+#: using-d-i.xml:2758
 #, no-c-format
 msgid "Using the Shell and Viewing the Logs"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2770
+#: using-d-i.xml:2761
 #, no-c-format
 msgid "There is an <guimenuitem>Execute a Shell</guimenuitem> item on the menu. If the menu is not available when you need to use the shell, press <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap> </keycombo>) to switch to the second <emphasis>virtual console</emphasis>. That's 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. This is a separate window running a Bourne shell clone called <command>ash</command>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2782
+#: using-d-i.xml:2773
 #, 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 text editor is <command>nano</command>. The shell has some nice features like autocompletion and history."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2791
+#: using-d-i.xml:2782
 #, no-c-format
 msgid "Use the menus to perform any task that they are able to do &mdash; the shell and commands are only there in case something goes wrong. In particular, you should always use the menus, not the shell, to activate your swap partition, because the menu software can't detect that you've done this from the shell. Press <keycombo><keycap>Left Alt</keycap> <keycap>F1</keycap></keycombo> to get back to menus, or type <command>exit</command> if you used a menu item to open the shell."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2810
+#: using-d-i.xml:2801
 #, no-c-format
 msgid "Installation Over the Network"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2812
+#: using-d-i.xml:2803
 #, 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:2822
+#: using-d-i.xml:2813
 #, 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:2835
+#: using-d-i.xml:2826
 #, 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:2840
+#: using-d-i.xml:2831
 #, 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:2852
+#: using-d-i.xml:2843
 #, 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:2858
+#: using-d-i.xml:2849
 #, 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"
@@ -2266,25 +2266,25 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2875
+#: using-d-i.xml:2866
 #, 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> and try again."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2884
+#: using-d-i.xml:2875
 #, 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:2894
+#: using-d-i.xml:2885
 #, 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:2902
+#: using-d-i.xml:2893
 #, 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 ""