Update of POT and PO files for the manual

5 files changed, 252 insertions, 246 deletions

diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot
index bd522f006..88cc51497 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-07-25 21:39+0000\n"
+"POT-Creation-Date: 2006-07-30 15:28+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"
@@ -1990,305 +1990,305 @@ msgstr ""
 #. Tag: para
 #: boot-installer.xml:2971
 #, 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>."
+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:2985
 #, no-c-format
 msgid "debian-installer/probe/usb"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2985
+#: boot-installer.xml:2986
 #, 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:2994
+#: boot-installer.xml:2995
 #, no-c-format
 msgid "netcfg/disable_dhcp"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2995
+#: boot-installer.xml:2996
 #, 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:3002
+#: boot-installer.xml:3003
 #, 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:3013
+#: boot-installer.xml:3014
 #, no-c-format
 msgid "hw-detect/start_pcmcia"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3014
+#: boot-installer.xml:3015
 #, 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:3024
+#: boot-installer.xml:3025
 #, no-c-format
 msgid "preseed/url"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3025
+#: boot-installer.xml:3026
 #, 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:3035
+#: boot-installer.xml:3036
 #, no-c-format
 msgid "preseed/file"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3036
+#: boot-installer.xml:3037
 #, 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:3046
+#: boot-installer.xml:3047
 #, no-c-format
 msgid "cdrom-detect/eject"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3047
+#: boot-installer.xml:3048
 #, 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:3056
+#: boot-installer.xml:3057
 #, 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:3067
+#: boot-installer.xml:3068
 #, no-c-format
 msgid "ramdisk_size"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3068
+#: boot-installer.xml:3069
 #, 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:3076
+#: boot-installer.xml:3077
 #, no-c-format
 msgid "rescue/enable"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3077
+#: boot-installer.xml:3078
 #, 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:3095
+#: boot-installer.xml:3096
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3100
+#: boot-installer.xml:3101
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3102
+#: boot-installer.xml:3103
 #, 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:3107
+#: boot-installer.xml:3108
 #, 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:3116
+#: boot-installer.xml:3117
 #, 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."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3126
+#: boot-installer.xml:3127
 #, 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:3132
+#: boot-installer.xml:3133
 #, 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:3141
+#: boot-installer.xml:3142
 #, no-c-format
 msgid "Boot Configuration"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3143
+#: boot-installer.xml:3144
 #, 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:3150
+#: boot-installer.xml:3151
 #, 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:3157
+#: boot-installer.xml:3158
 #, no-c-format
 msgid "Often, problems can be solved by removing add-ons and peripherals, and then trying booting again. <phrase arch=\"i386\">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3163
+#: boot-installer.xml:3164
 #, 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:3174
+#: boot-installer.xml:3175
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3175
+#: boot-installer.xml:3176
 #, 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:3180
+#: boot-installer.xml:3181
 #, 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:3186
+#: boot-installer.xml:3187
 #, 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:3195
+#: boot-installer.xml:3196
 #, 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:3202
+#: boot-installer.xml:3203
 #, 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:3216
+#: boot-installer.xml:3217
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3217
+#: boot-installer.xml:3218
 #, 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:3227
+#: boot-installer.xml:3228
 #, 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:3244
+#: boot-installer.xml:3245
 #, no-c-format
 msgid "System Freeze while Loading the USB Modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3245
+#: boot-installer.xml:3246
 #, 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:3259
+#: boot-installer.xml:3260
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3261
+#: boot-installer.xml:3262
 #, 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:3286
+#: boot-installer.xml:3287
 #, no-c-format
 msgid "Bug Reporter"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3287
+#: boot-installer.xml:3288
 #, 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:3298
+#: boot-installer.xml:3299
 #, 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:3309
+#: boot-installer.xml:3310
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3310
+#: boot-installer.xml:3311
 #, 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:3317
+#: boot-installer.xml:3318
 #, 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:3324
+#: boot-installer.xml:3325
 #, 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"
diff --git a/po/pot/partitioning.pot b/po/pot/partitioning.pot
index 90c02a82b..ed65c120b 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-07-25 21:39+0000\n"
+"POT-Creation-Date: 2006-07-30 15:28+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"
@@ -257,371 +257,383 @@ msgstr ""
 #. Tag: filename
 #: partitioning.xml:133
 #, no-c-format
-msgid "<filename>opt</filename>"
+msgid "<filename>srv</filename>"
 msgstr ""
 
 #. Tag: entry
 #: partitioning.xml:134
 #, no-c-format
+msgid "Data for services provided by the system"
+msgstr ""
+
+#. Tag: filename
+#: partitioning.xml:136
+#, no-c-format
+msgid "<filename>opt</filename>"
+msgstr ""
+
+#. Tag: entry
+#: partitioning.xml:137
+#, no-c-format
 msgid "Add-on application software packages"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:139
+#: partitioning.xml:142
 #, no-c-format
 msgid "The following is a list of important considerations regarding directories and partitions. Note that disk usage varies widely given system configuration and specific usage patterns. The recommendations here are general guidelines and provide a starting point for partitioning."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:149
+#: partitioning.xml:152
 #, no-c-format
-msgid "The root partition <filename>/</filename> must always physically contain <filename>/etc</filename>, <filename>/bin</filename>, <filename>/sbin</filename>, <filename>/lib</filename> and <filename>/dev</filename>, otherwise you won't be able to boot. Typically 150&ndash;250 MB is needed for the root partition."
+msgid "The root partition <filename>/</filename> must always physically contain <filename>/etc</filename>, <filename>/bin</filename>, <filename>/sbin</filename>, <filename>/lib</filename> and <filename>/dev</filename>, otherwise you won't be able to boot. Typically 150&ndash;250MB is needed for the root partition."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:158
+#: partitioning.xml:161
 #, no-c-format
-msgid "<filename>/usr</filename>: contains all user programs (<filename>/usr/bin</filename>), libraries (<filename>/usr/lib</filename>), documentation (<filename>/usr/share/doc</filename>), etc. This is the part of the file system that generally takes up most space. You should provide at least 500 MB of disk space. This amount should be increased depending on the number and type of packages you plan to install. A generous workstation or server installation should allow 4-6 GB."
+msgid "<filename>/usr</filename>: contains all user programs (<filename>/usr/bin</filename>), libraries (<filename>/usr/lib</filename>), documentation (<filename>/usr/share/doc</filename>), etc. This is the part of the file system that generally takes up most space. You should provide at least 500MB of disk space. This amount should be increased depending on the number and type of packages you plan to install. A generous workstation or server installation should allow 4&ndash;6GB."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:171
+#: partitioning.xml:174
 #, no-c-format
-msgid "<filename>/var</filename>: variable data like news articles, e-mails, web sites, databases, the packaging system cache, etc. will be placed under this directory. The size of this directory depends greatly on the usage of your system, but for most people will be dictated by the package management tool's overhead. If you are going to do a full installation of just about everything Debian has to offer, all in one session, setting aside 2 or 3 gigabyte of space for <filename>/var</filename> should be sufficient. If you are going to install in pieces (that is to say, install services and utilities, followed by text stuff, then X, ...), you can get away with 300&ndash;500 MB. If hard drive space is at a premium and you don't plan on doing major system updates, you can get by with as little as 30 or 40 MB."
+msgid "<filename>/var</filename>: variable data like news articles, e-mails, web sites, databases, the packaging system cache, etc. will be placed under this directory. The size of this directory depends greatly on the usage of your system, but for most people will be dictated by the package management tool's overhead. If you are going to do a full installation of just about everything Debian has to offer, all in one session, setting aside 2 or 3 GB of space for <filename>/var</filename> should be sufficient. If you are going to install in pieces (that is to say, install services and utilities, followed by text stuff, then X, ...), you can get away with 300&ndash;500 MB. If hard drive space is at a premium and you don't plan on doing major system updates, you can get by with as little as 30 or 40 MB."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:187
+#: partitioning.xml:190
 #, no-c-format
-msgid "<filename>/tmp</filename>: temporary data created by programs will most likely go in this directory. 40&ndash;100 MB should usually be enough. Some applications &mdash; including archive manipulators, CD/DVD authoring tools, and multimedia software &mdash; may use <filename>/tmp</filename> to temporarily store image files. If you plan to use such applications, you should adjust the space available in <filename>/tmp</filename> accordingly."
+msgid "<filename>/tmp</filename>: temporary data created by programs will most likely go in this directory. 40&ndash;100MB should usually be enough. Some applications &mdash; including archive manipulators, CD/DVD authoring tools, and multimedia software &mdash; may use <filename>/tmp</filename> to temporarily store image files. If you plan to use such applications, you should adjust the space available in <filename>/tmp</filename> accordingly."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:198
+#: partitioning.xml:201
 #, no-c-format
-msgid "<filename>/home</filename>: every user will put his personal data into a subdirectory of this directory. Its size depends on how many users will be using the system and what files are to be stored in their directories. Depending on your planned usage you should reserve about 100 MB for each user, but adapt this value to your needs. Reserve a lot more space if you plan to save a lot of multimedia files (pictures, MP3, movies) in your home directory."
+msgid "<filename>/home</filename>: every user will put his personal data into a subdirectory of this directory. Its size depends on how many users will be using the system and what files are to be stored in their directories. Depending on your planned usage you should reserve about 100MB for each user, but adapt this value to your needs. Reserve a lot more space if you plan to save a lot of multimedia files (pictures, MP3, movies) in your home directory."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:219
+#: partitioning.xml:222
 #, no-c-format
 msgid "Recommended Partitioning Scheme"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:220
+#: partitioning.xml:223
 #, no-c-format
 msgid "For new users, personal Debian boxes, home systems, and other single-user setups, a single <filename>/</filename> partition (plus swap) is probably the easiest, simplest way to go. However, if your partition is larger than around 6GB, choose ext3 as your partition type. Ext2 partitions need periodic file system integrity checking, and this can cause delays during booting when the partition is large."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:229
+#: partitioning.xml:232
 #, no-c-format
 msgid "For multi-user systems or systems with lots of disk space, it's best to put <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, and <filename>/home</filename> each on their own partitions separate from the <filename>/</filename> partition."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:237
+#: partitioning.xml:240
 #, no-c-format
-msgid "You might need a separate <filename>/usr/local</filename> partition if you plan to install many programs that are not part of the Debian distribution. If your machine will be a mail server, you might need to make <filename>/var/mail</filename> a separate partition. Often, putting <filename>/tmp</filename> on its own partition, for instance 20 to 50MB, is a good idea. If you are setting up a server with lots of user accounts, it's generally good to have a separate, large <filename>/home</filename> partition. In general, the partitioning situation varies from computer to computer depending on its uses."
+msgid "You might need a separate <filename>/usr/local</filename> partition if you plan to install many programs that are not part of the Debian distribution. If your machine will be a mail server, you might need to make <filename>/var/mail</filename> a separate partition. Often, putting <filename>/tmp</filename> on its own partition, for instance 20&ndash;50MB, is a good idea. If you are setting up a server with lots of user accounts, it's generally good to have a separate, large <filename>/home</filename> partition. In general, the partitioning situation varies from computer to computer depending on its uses."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:249
+#: partitioning.xml:252
 #, no-c-format
 msgid "For very complex systems, you should see the <ulink url=\"&url-multidisk-howto;\"> Multi Disk HOWTO</ulink>. This contains in-depth information, mostly of interest to ISPs and people setting up servers."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:256
+#: partitioning.xml:259
 #, no-c-format
 msgid "With respect to the issue of swap partition size, there are many views. One rule of thumb which works well is to use as much swap as you have system memory. It also shouldn't be smaller than 16MB, in most cases. Of course, there are exceptions to these rules. If you are trying to solve 10000 simultaneous equations on a machine with 256MB of memory, you may need a gigabyte (or more) of swap."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:265
+#: partitioning.xml:268
 #, no-c-format
 msgid "On the other hand, Atari Falcons and Macs feel pain when swapping, so instead of making a large swap partition, get as much RAM as possible."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:270
+#: partitioning.xml:273
 #, no-c-format
 msgid "On 32-bit architectures (i386, m68k, 32-bit SPARC, and PowerPC), the maximum size of a swap partition is 2GB. That should be enough for nearly any installation. However, if your swap requirements are this high, you should probably try to spread the swap across different disks (also called <quote>spindles</quote>) and, if possible, different SCSI or IDE channels. The kernel will balance swap usage between multiple swap partitions, giving better performance."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:280
+#: partitioning.xml:283
 #, no-c-format
 msgid "As an example, an older home machine might have 32MB of RAM and a 1.7GB IDE drive on <filename>/dev/hda</filename>. There might be a 500MB partition for another operating system on <filename>/dev/hda1</filename>, a 32MB swap partition on <filename>/dev/hda3</filename> and about 1.2GB on <filename>/dev/hda2</filename> as the Linux partition."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:289
+#: partitioning.xml:292
 #, no-c-format
 msgid "For an idea of the space taken by tasks you might be interested in adding after your system installation is complete, check <xref linkend=\"tasksel-size-list\"/>."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:305
+#: partitioning.xml:308
 #, no-c-format
 msgid "Device Names in Linux"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:306
+#: partitioning.xml:309
 #, no-c-format
 msgid "Linux disks and partition names may be different from other operating systems. You need to know the names that Linux uses when you create and mount partitions. Here's the basic naming scheme:"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:314
+#: partitioning.xml:317
 #, no-c-format
 msgid "The first floppy drive is named <filename>/dev/fd0</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:319
+#: partitioning.xml:322
 #, no-c-format
 msgid "The second floppy drive is named <filename>/dev/fd1</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:324
+#: partitioning.xml:327
 #, no-c-format
 msgid "The first SCSI disk (SCSI ID address-wise) is named <filename>/dev/sda</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:330
+#: partitioning.xml:333
 #, no-c-format
 msgid "The second SCSI disk (address-wise) is named <filename>/dev/sdb</filename>, and so on."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:336
+#: partitioning.xml:339
 #, no-c-format
 msgid "The first SCSI CD-ROM is named <filename>/dev/scd0</filename>, also known as <filename>/dev/sr0</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:342
+#: partitioning.xml:345
 #, no-c-format
 msgid "The master disk on IDE primary controller is named <filename>/dev/hda</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:348
+#: partitioning.xml:351
 #, no-c-format
 msgid "The slave disk on IDE primary controller is named <filename>/dev/hdb</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:354
+#: partitioning.xml:357
 #, no-c-format
 msgid "The master and slave disks of the secondary controller can be called <filename>/dev/hdc</filename> and <filename>/dev/hdd</filename>, respectively. Newer IDE controllers can actually have two channels, effectively acting like two controllers. <phrase arch=\"m68k\"> The letters may differ from what shows in the mac program pdisk (i.e. what shows up as <filename>/dev/hdc</filename> on pdisk may show up as <filename>/dev/hda</filename> in Debian). </phrase>"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:369
+#: partitioning.xml:372
 #, no-c-format
 msgid "The first XT disk is named <filename>/dev/xda</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:374
+#: partitioning.xml:377
 #, no-c-format
 msgid "The second XT disk is named <filename>/dev/xdb</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:379
+#: partitioning.xml:382
 #, no-c-format
 msgid "The first ACSI device is named <filename>/dev/ada</filename>, the second is named <filename>/dev/adb</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:388
+#: partitioning.xml:391
 #, no-c-format
 msgid "The first DASD device is named <filename>/dev/dasda</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:394
+#: partitioning.xml:397
 #, no-c-format
 msgid "The second DASD device is named <filename>/dev/dasdb</filename>, and so on."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:402
+#: partitioning.xml:405
 #, no-c-format
 msgid "The partitions on each disk are represented by appending a decimal number to the disk name: <filename>sda1</filename> and <filename>sda2</filename> represent the first and second partitions of the first SCSI disk drive in your system."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:409
+#: partitioning.xml:412
 #, no-c-format
 msgid "Here is a real-life example. Let's assume you have a system with 2 SCSI disks, one at SCSI address 2 and the other at SCSI address 4. The first disk (at address 2) is then named <filename>sda</filename>, and the second <filename>sdb</filename>. If the <filename>sda</filename> drive has 3 partitions on it, these will be named <filename>sda1</filename>, <filename>sda2</filename>, and <filename>sda3</filename>. The same applies to the <filename>sdb</filename> disk and its partitions."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:420
+#: partitioning.xml:423
 #, no-c-format
 msgid "Note that if you have two SCSI host bus adapters (i.e., controllers), the order of the drives can get confusing. The best solution in this case is to watch the boot messages, assuming you know the drive models and/or capacities."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:427
+#: partitioning.xml:430
 #, no-c-format
 msgid "Linux represents the primary partitions as the drive name, plus the numbers 1 through 4. For example, the first primary partition on the first IDE drive is <filename>/dev/hda1</filename>. The logical partitions are numbered starting at 5, so the first logical partition on that same drive is <filename>/dev/hda5</filename>. Remember that the extended partition, that is, the primary partition holding the logical partitions, is not usable by itself. This applies to SCSI disks as well as IDE disks."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:438
+#: partitioning.xml:441
 #, no-c-format
 msgid "VMEbus systems using the TEAC FC-1 SCSI floppy drive will see it as normal SCSI disk. To make identification of the drive simpler the installation software will create a symbolic link to the appropriate device and name it <filename>/dev/sfd0</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:445
+#: partitioning.xml:448
 #, no-c-format
 msgid "Sun disk partitions allow for 8 separate partitions (or slices). The third partition is usually (and is preferred to have) the <quote>Whole Disk</quote> partition. This partition references all of the sectors of the disk, and is used by the boot loader (either SILO, or Sun's)."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:452
+#: partitioning.xml:455
 #, no-c-format
 msgid "The partitions on each disk are represented by appending a decimal number to the disk name: <filename>dasda1</filename> and <filename>dasda2</filename> represent the first and second partitions of the first DASD device in your system."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:467
+#: partitioning.xml:470
 #, no-c-format
 msgid "Debian Partitioning Programs"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:468
+#: partitioning.xml:471
 #, no-c-format
 msgid "Several varieties of partitioning programs have been adapted by Debian developers to work on various types of hard disks and computer architectures. Following is a list of the program(s) applicable for your architecture."
 msgstr ""
 
 #. Tag: command
-#: partitioning.xml:480
+#: partitioning.xml:483
 #, no-c-format
 msgid "partman"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:481
+#: partitioning.xml:484
 #, no-c-format
 msgid "Recommended partitioning tool in Debian. This Swiss army knife can also resize partitions, create filesystems <phrase arch=\"i386\"> (<quote>format</quote> in Windows speak)</phrase> and assign them to the mountpoints."
 msgstr ""
 
 #. Tag: command
-#: partitioning.xml:492
+#: partitioning.xml:495
 #, no-c-format
 msgid "fdisk"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:493
+#: partitioning.xml:496
 #, no-c-format
 msgid "The original Linux disk partitioner, good for gurus."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:497
+#: partitioning.xml:500
 #, no-c-format
-msgid "Be careful if you have existing FreeBSD partitions on your machine. The installation kernels include support for these partitions, but the way that <command>fdisk</command> represents them (or not) can make the device names differ. See the <ulink url=\"&url-linux-freebsd;\">Linux+FreeBSD HOWTO</ulink>"
+msgid "Be careful if you have existing FreeBSD partitions on your machine. The installation kernels include support for these partitions, but the way that <command>fdisk</command> represents them (or not) can make the device names differ. See the <ulink url=\"&url-linux-freebsd;\">Linux+FreeBSD HOWTO</ulink>."
 msgstr ""
 
 #. Tag: command
-#: partitioning.xml:509
+#: partitioning.xml:512
 #, no-c-format
 msgid "cfdisk"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:510
+#: partitioning.xml:513
 #, no-c-format
 msgid "A simple-to-use, full-screen disk partitioner for the rest of us."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:514
+#: partitioning.xml:517
 #, no-c-format
 msgid "Note that <command>cfdisk</command> doesn't understand FreeBSD partitions at all, and, again, device names may differ as a result."
 msgstr ""
 
 #. Tag: command
-#: partitioning.xml:523
+#: partitioning.xml:526
 #, no-c-format
 msgid "atari-fdisk"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:524
+#: partitioning.xml:527
 #, no-c-format
 msgid "Atari-aware version of <command>fdisk</command>."
 msgstr ""
 
 #. Tag: command
-#: partitioning.xml:532
+#: partitioning.xml:535
 #, no-c-format
 msgid "amiga-fdisk"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:533
+#: partitioning.xml:536
 #, no-c-format
 msgid "Amiga-aware version of <command>fdisk</command>."
 msgstr ""
 
 #. Tag: command
-#: partitioning.xml:541
+#: partitioning.xml:544
 #, no-c-format
 msgid "mac-fdisk"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:542
+#: partitioning.xml:545
 #, no-c-format
 msgid "Mac-aware version of <command>fdisk</command>."
 msgstr ""
 
 #. Tag: command
-#: partitioning.xml:550
+#: partitioning.xml:553
 #, no-c-format
 msgid "pmac-fdisk"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:551
+#: partitioning.xml:554
 #, no-c-format
 msgid "PowerMac-aware version of <command>fdisk</command>, also used by BVM and Motorola VMEbus systems."
 msgstr ""
 
 #. Tag: command
-#: partitioning.xml:560
+#: partitioning.xml:563
 #, no-c-format
 msgid "fdasd"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:561
+#: partitioning.xml:564
 #, no-c-format
 msgid "&arch-title; version of <command>fdisk</command>; Please read the fdasd manual page or chapter 13 in <ulink url=\"http://oss.software.ibm.com/developerworks/opensource/linux390/docu/l390dd08.pdf\"> Device Drivers and Installation Commands</ulink> for details."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:572
+#: partitioning.xml:575
 #, no-c-format
 msgid "One of these programs will be run by default when you select <guimenuitem>Partition disks</guimenuitem> (or similar). It may be possible to use a different partitioning tool from the command line on VT2, but this is not recommended."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:579
+#: 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"
@@ -638,127 +650,127 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:598
+#: partitioning.xml:601
 #, 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:614 partitioning.xml:674 partitioning.xml:698 partitioning.xml:794 partitioning.xml:913 partitioning.xml:990
+#: partitioning.xml:617 partitioning.xml:677 partitioning.xml:701 partitioning.xml:798 partitioning.xml:912 partitioning.xml:989
 #, no-c-format
 msgid "Partitioning for &arch-title;"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:615
+#: partitioning.xml:618
 #, 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 partman can convert it to use a disk label."
+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:626
+#: partitioning.xml:629
 #, 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:633
+#: partitioning.xml:636
 #, 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), it is suggested that you do <emphasis>not</emphasis> make the third partition contain the whole disk. This is not required by <command>aboot</command>, and in fact, it may lead to confusion since the <command>swriteboot</command> utility used to install <command>aboot</command> in the boot sector will complain about a partition overlapping with the boot block."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:644
+#: partitioning.xml:647
 #, 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:656
+#: partitioning.xml:659
 #, 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:675
+#: partitioning.xml:678
 #, 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:699
+#: partitioning.xml:702
 #, 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 to partition manually and then simply select an existing partition and change its size."
+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>Manually edit partition table</guimenuitem> and then simply select an existing partition and change its size."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:708
+#: partitioning.xml:712
 #, 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:719
+#: partitioning.xml:723
 #, 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:730
+#: partitioning.xml:734
 #, 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:740
+#: partitioning.xml:744
 #, 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:748
+#: partitioning.xml:752
 #, 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:762
+#: partitioning.xml:766
 #, 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:774
+#: partitioning.xml:778
 #, 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:796
+#: partitioning.xml:799
 #, 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 is properly configured for a successful installation. It actually uses the <command>parted</command> to do the on-disk partitioning."
+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:808
+#: partitioning.xml:811
 #, no-c-format
 msgid "EFI Recognized Formats"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:809
+#: partitioning.xml:812
 #, 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 the <command>cfdisk</command>, you should only use the <ulink url=\"parted.txt\"> <command>parted</command></ulink> because only it can manage both GPT and MS-DOS tables correctly."
+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:821
+#: partitioning.xml:824
 #, 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:829
+#: partitioning.xml:832
 #, 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"
@@ -773,31 +785,31 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:854
+#: partitioning.xml:857
 #, no-c-format
 msgid "Boot Loader Partition Requirements"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:856
+#: partitioning.xml:858
 #, 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:865
+#: partitioning.xml:867
 #, 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:880
+#: partitioning.xml:882
 #, 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:889
+#: partitioning.xml:890
 #, no-c-format
 msgid "EFI Diagnostic Partitions"
 msgstr ""
@@ -809,61 +821,61 @@ msgid "The EFI firmware is significantly more sophisticated than the usual BIOS
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:914
+#: partitioning.xml:913
 #, 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:930
 #, no-c-format
 msgid "Partitioning Newer PowerMacs"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:932
+#: partitioning.xml:931
 #, 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:944
 #, 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:951
 #, 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:961
 #, 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:973
 #, 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:990
 #, 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:998
 #, 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:1009
 #, 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 19d4e3b58..b1db4d438 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-07-25 21:39+0000\n"
+"POT-Creation-Date: 2006-07-30 15:28+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"
@@ -968,14 +968,23 @@ msgstr ""
 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:784
+#, 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:786
+#: preseed.xml:794
 #, no-c-format
 msgid ""
       "tasksel tasksel/first multiselect standard, desktop\n"
       "#tasksel tasksel/first multiselect standard, web-server\n"
       "#tasksel tasksel/first multiselect standard, kde-desktop\n"
       "\n"
+      "# Individual additional packages to install\n"
+      "#d-i pkgsel/include string openssh-server build-essential\n"
+      "\n"
       "# Some versions of the installer can report back on what software you have\n"
       "# installed, and what software you use. The default is not to report back,\n"
       "# but sending reports helps the project determine what software is most\n"
@@ -984,13 +993,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:791
+#: preseed.xml:799
 #, no-c-format
 msgid "Finishing up the first stage install"
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:793
+#: preseed.xml:801
 #, no-c-format
 msgid ""
       "# Avoid that last message about the install being complete.\n"
@@ -1002,19 +1011,19 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:798
+#: preseed.xml:806
 #, no-c-format
 msgid "Mailer configuration"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:799
+#: preseed.xml:807
 #, 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:806
+#: preseed.xml:814
 #, no-c-format
 msgid ""
       "exim4-config exim4/dc_eximconfig_configtype \\\n"
@@ -1025,19 +1034,19 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:811
+#: preseed.xml:819
 #, no-c-format
 msgid "X configuration"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:812
+#: preseed.xml:820
 #, 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:820
+#: preseed.xml:828
 #, no-c-format
 msgid ""
       "# X can detect the right driver for some cards, but if you're preseeding,\n"
@@ -1063,13 +1072,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:825
+#: preseed.xml:833
 #, no-c-format
 msgid "Preseeding other packages"
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:827
+#: preseed.xml:835
 #, no-c-format
 msgid ""
       "# Depending on what software you choose to install, or if things go wrong\n"
@@ -1082,19 +1091,19 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:833
+#: preseed.xml:841
 #, no-c-format
 msgid "Advanced options"
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:836
+#: preseed.xml:844
 #, no-c-format
 msgid "Shell commands"
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:838
+#: preseed.xml:846
 #, no-c-format
 msgid ""
       "# d-i preseeding is inherently not secure. Nothing in the installer checks\n"
@@ -1116,19 +1125,19 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:843
+#: preseed.xml:851
 #, no-c-format
 msgid "Chainloading preconfiguration files"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:844
+#: preseed.xml:852
 #, 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:854
+#: preseed.xml:862
 #, 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 c31211d1a..d709b412f 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-07-25 21:39+0000\n"
+"POT-Creation-Date: 2006-07-30 15:28+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"
@@ -337,7 +337,7 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:148
 #, no-c-format
-msgid "If gpm is disabled or not installed with some reason, make sure to set X to read directly from the mouse device such as /dev/psaux. For details, refer to the 3-Button Mouse mini-Howto at <filename>/usr/share/doc/HOWTO/en-txt/mini/3-Button-Mouse.gz</filename>, <userinput>man gpm</userinput>, <filename>/usr/share/doc/gpm/FAQ.gz</filename>, and <ulink url=\"&url-xorg;current/doc/html/mouse.html\">README.mouse</ulink>."
+msgid "If gpm is disabled or not installed for some reason, make sure to set X to read directly from a mouse device such as /dev/psaux. For details, refer to the 3-Button Mouse mini-Howto at <filename>/usr/share/doc/HOWTO/en-txt/mini/3-Button-Mouse.gz</filename>, <userinput>man gpm</userinput>, <filename>/usr/share/doc/gpm/FAQ.gz</filename>, and <ulink url=\"&url-xorg;current/doc/html/mouse.html\">README.mouse</ulink>."
 msgstr ""
 
 #. Tag: para
@@ -579,7 +579,7 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:274
 #, 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 both the GNOME and KDE desktop environments."
 msgstr ""
 
 #. Tag: para
@@ -622,7 +622,7 @@ msgstr ""
 #: random-bits.xml:330
 #, no-c-format
 msgid ""
-      "To 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"
+      "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"
       "# mke2fs -j /dev/hda6\n"
       "</screen></informalexample> To create an ext2 file system instead, omit <userinput>-j</userinput>."
 msgstr ""
@@ -661,7 +661,7 @@ msgstr ""
 #. Tag: para
 #: random-bits.xml:366
 #, no-c-format
-msgid "The tool that the Debian installer uses, which is 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>."
+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
@@ -874,20 +874,20 @@ msgstr ""
 #: random-bits.xml:564
 #, no-c-format
 msgid ""
-      "To configure your locale settings to use a language other than English, install the locales support package and configure it: <informalexample><screen>\n"
-      "# apt-get install locales\n"
+      "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"
+      "# aptitude install locales\n"
       "# dpkg-reconfigure locales\n"
-      "</screen></informalexample> NOTE: Apt must be configured beforehand by creating a sources.list and running apt-get update. Before using locales with character sets other than ASCII or latin1, please consult the appropriate localization HOWTO."
+      "</screen></informalexample> NOTE: <classname>apt</classname> must be configured beforehand by creating a sources.list and running <command>aptitude update</command>. Before using locales with character sets other than ASCII or latin1, please consult the appropriate localization HOWTO."
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:581
+#: random-bits.xml:582
 #, no-c-format
 msgid "Install a Kernel"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:582
+#: random-bits.xml:583
 #, 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"
@@ -896,37 +896,37 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:591
+#: random-bits.xml:592
 #, no-c-format
-msgid "# apt-get install <phrase condition=\"classic-kpkg\">kernel</phrase><phrase condition=\"common-kpkg\">linux</phrase>-image-<replaceable>&kernelversion;-arch-etc</replaceable>"
+msgid "# aptitude install <phrase condition=\"classic-kpkg\">kernel</phrase><phrase condition=\"common-kpkg\">linux</phrase>-image-<replaceable>&kernelversion;-arch-etc</replaceable>"
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:597
+#: random-bits.xml:598
 #, no-c-format
 msgid "Set up the Boot Loader"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:598
+#: random-bits.xml:599
 #, 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 debootstrap does not install a boot loader, though you can use apt-get inside your Debian chroot to do so."
+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:605
+#: random-bits.xml:606
 #, 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:616
+#: random-bits.xml:617
 #, no-c-format
 msgid "Here is a basic <filename>/etc/lilo.conf</filename> as an example:"
 msgstr ""
 
 #. Tag: screen
-#: random-bits.xml:620
+#: random-bits.xml:621
 #, no-c-format
 msgid ""
       "boot=/dev/hda6\n"
@@ -939,13 +939,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:622
+#: random-bits.xml:623
 #, 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:632
+#: random-bits.xml:633
 #, no-c-format
 msgid ""
       "Here is a basic <filename>/etc/yaboot.conf</filename> as an example: <informalexample><screen>\n"
@@ -961,79 +961,79 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:650
+#: random-bits.xml:651
 #, no-c-format
 msgid "Installing &debian; over Parallel Line IP (PLIP)"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:652
+#: random-bits.xml:653
 #, no-c-format
-msgid "This section explains how to install &debian; on a computer without 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)."
+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:660
+#: random-bits.xml:661
 #, 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:668
+#: random-bits.xml:669
 #, 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:673
+#: random-bits.xml:674
 #, 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:683
+#: random-bits.xml:684
 #, no-c-format
 msgid "Requirements"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:686
+#: random-bits.xml:687
 #, no-c-format
 msgid "A target computer, called <emphasis>target</emphasis>, where Debian will be installed."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:692
+#: random-bits.xml:693
 #, no-c-format
 msgid "System installation media; see <xref linkend=\"installation-media\"/>."
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:697
+#: random-bits.xml:698
 #, 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:703
+#: random-bits.xml:704
 #, 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:715
+#: random-bits.xml:716
 #, no-c-format
 msgid "Setting up source"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:716
+#: random-bits.xml:717
 #, 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:721
+#: random-bits.xml:722
 #, no-c-format
 msgid ""
       "#!/bin/sh\n"
@@ -1054,91 +1054,76 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: random-bits.xml:727
+#: random-bits.xml:728
 #, no-c-format
 msgid "Installing target"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:728
+#: random-bits.xml:729
 #, 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. Below are the answers that should be given during various stages of the installation."
+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 paramenters 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"
+      "expert parport_pc.io=<replaceable>0x378</replaceable> parport_pc.irq=<replaceable>7</replaceable>\n"
+      "</screen></informalexample> Below are the answers that should be given during various stages of the installation."
 msgstr ""
 
 #. Tag: guimenuitem
-#: random-bits.xml:740
+#: random-bits.xml:748
 #, no-c-format
 msgid "Load installer components"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:742
+#: random-bits.xml:750
 #, 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:750
+#: random-bits.xml:758
 #, no-c-format
 msgid "Detect network hardware"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:755
+#: random-bits.xml:763
 #, 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:764
-#, no-c-format
-msgid "Prompt for module parameters: Yes"
-msgstr ""
-
-#. Tag: para
-#: random-bits.xml:769
+#: random-bits.xml:772
 #, 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: para
-#: random-bits.xml:776
-#, no-c-format
-msgid "Additional parameters for module parport_pc: <userinput><replaceable>io=0x378 irq=7</replaceable></userinput>"
-msgstr ""
-
-#. Tag: para
-#: random-bits.xml:782
-#, no-c-format
-msgid "Additional parameters for module plip: leave empty"
-msgstr ""
-
 #. Tag: guimenuitem
-#: random-bits.xml:792
+#: random-bits.xml:784
 #, no-c-format
 msgid "Configure the network"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:795
+#: random-bits.xml:787
 #, no-c-format
 msgid "Auto-configure network with DHCP: No"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:800
+#: random-bits.xml:792
 #, no-c-format
 msgid "IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:805
+#: random-bits.xml:797
 #, no-c-format
 msgid "Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></userinput>"
 msgstr ""
 
 #. Tag: para
-#: random-bits.xml:811
+#: random-bits.xml:803
 #, 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 38508ab79..92c4133c3 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-07-25 21:39+0000\n"
+"POT-Creation-Date: 2006-07-30 15:28+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"
@@ -1084,7 +1084,7 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:1334
 #, no-c-format
-msgid "First, let's have a look at available options available when you select <userinput>Device-mapper (dm-crypt)</userinput> as the encryption method. As always: when in doubt, use the defaults, because they have been carefully chosen with security in mind."
+msgid "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