Update of POT and PO files for the manual

10 files changed, 1623 insertions, 2367 deletions

diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot
index a44db59b2..6754a04b3 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"
-"POT-Creation-Date: 2005-12-03 10:28+0000\n"
+"POT-Creation-Date: 2006-01-03 19:55+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 ""
 msgid "As on other architectures, you should install the newest available revision of the firmware<footnote> <para> Except on Jensen, where Linux is not supported on firmware versions newer than 1.7 &mdash; see <ulink url=\"&url-jensen-howto;\"></ulink> for more information. </para> </footnote> before installing &debian;. For Alpha, firmware updates can be obtained from <ulink url=\"&url-alpha-firmware;\">Alpha Firmware Updates</ulink>."
 msgstr ""
 
-#: boot-installer.xml:283 boot-installer.xml:892 boot-installer.xml:1384 boot-installer.xml:1889 boot-installer.xml:1971 boot-installer.xml:2311 boot-installer.xml:2407
+#: boot-installer.xml:283 boot-installer.xml:890 boot-installer.xml:1381 boot-installer.xml:1876 boot-installer.xml:1958 boot-installer.xml:2298 boot-installer.xml:2394
 #, no-c-format
 #. Tag: title
 msgid "Booting with TFTP"
@@ -478,19 +478,19 @@ msgstr ""
 msgid "Booting from TFTP"
 msgstr ""
 
-#: boot-installer.xml:441 boot-installer.xml:898 boot-installer.xml:1402 boot-installer.xml:1895 boot-installer.xml:2317 boot-installer.xml:2413
+#: boot-installer.xml:441 boot-installer.xml:896 boot-installer.xml:1399 boot-installer.xml:1882 boot-installer.xml:2304 boot-installer.xml:2400
 #, no-c-format
 #. Tag: para
 msgid "Booting from the network requires that you have a network connection and a TFTP network boot server (DHCP, RARP, or BOOTP)."
 msgstr ""
 
-#: boot-installer.xml:446 boot-installer.xml:903 boot-installer.xml:1407 boot-installer.xml:1900 boot-installer.xml:2322 boot-installer.xml:2418
+#: boot-installer.xml:446 boot-installer.xml:901 boot-installer.xml:1404 boot-installer.xml:1887 boot-installer.xml:2309 boot-installer.xml:2405
 #, no-c-format
 #. Tag: para
 msgid "Older systems such as the 715 might require the use of an RBOOT server instead of a BOOTP server."
 msgstr ""
 
-#: boot-installer.xml:451 boot-installer.xml:908 boot-installer.xml:1412 boot-installer.xml:1905 boot-installer.xml:2327 boot-installer.xml:2423
+#: boot-installer.xml:451 boot-installer.xml:906 boot-installer.xml:1409 boot-installer.xml:1892 boot-installer.xml:2314 boot-installer.xml:2410
 #, no-c-format
 #. Tag: para
 msgid "The installation method to support network booting is described in <xref linkend=\"install-tftp\"/>."
@@ -571,25 +571,25 @@ msgstr ""
 msgid "Booting from CD-ROM"
 msgstr ""
 
-#: boot-installer.xml:546 boot-installer.xml:599 boot-installer.xml:1021 boot-installer.xml:1852 boot-installer.xml:2099 boot-installer.xml:2453
+#: boot-installer.xml:546 boot-installer.xml:599 boot-installer.xml:1018 boot-installer.xml:1839 boot-installer.xml:2086 boot-installer.xml:2440
 #, no-c-format
 #. Tag: para
 msgid "The easiest route for most people will be to use a set of Debian CDs. If you have a CD set, and if your machine supports booting directly off the CD, great! Simply <phrase arch=\"i386\"> configure your system for booting off a CD as described in <xref linkend=\"boot-dev-select\"/>, </phrase> insert your CD, reboot, and proceed to the next chapter."
 msgstr ""
 
-#: boot-installer.xml:557 boot-installer.xml:610 boot-installer.xml:1032 boot-installer.xml:1863 boot-installer.xml:2110 boot-installer.xml:2464
+#: boot-installer.xml:557 boot-installer.xml:610 boot-installer.xml:1029 boot-installer.xml:1850 boot-installer.xml:2097 boot-installer.xml:2451
 #, no-c-format
 #. Tag: para
 msgid "Note that certain CD drives may require special drivers, and thus be inaccessible in the early installation stages. If it turns out the standard way of booting off a CD doesn't work for your hardware, revisit this chapter and read about alternate kernels and installation methods which may work for you."
 msgstr ""
 
-#: boot-installer.xml:565 boot-installer.xml:618 boot-installer.xml:1040 boot-installer.xml:1871 boot-installer.xml:2118 boot-installer.xml:2472
+#: boot-installer.xml:565 boot-installer.xml:618 boot-installer.xml:1037 boot-installer.xml:1858 boot-installer.xml:2105 boot-installer.xml:2459
 #, no-c-format
 #. Tag: para
 msgid "Even if you cannot boot from CD-ROM, you can probably install the Debian system components and any packages you want from CD-ROM. Simply boot using a different media, such as floppies. When it's time to install the operating system, base system, and any additional packages, point the installation system at the CD-ROM drive."
 msgstr ""
 
-#: boot-installer.xml:573 boot-installer.xml:626 boot-installer.xml:1048 boot-installer.xml:1879 boot-installer.xml:2126 boot-installer.xml:2480
+#: boot-installer.xml:573 boot-installer.xml:626 boot-installer.xml:1045 boot-installer.xml:1866 boot-installer.xml:2113 boot-installer.xml:2467
 #, no-c-format
 #. Tag: para
 msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
@@ -601,7 +601,7 @@ msgstr ""
 msgid "To boot a CD-ROM from the Cyclone console prompt, use the command <command>boot cd0:cats.bin</command>"
 msgstr ""
 
-#: boot-installer.xml:593 boot-installer.xml:1015 boot-installer.xml:1840 boot-installer.xml:2093 boot-installer.xml:2447
+#: boot-installer.xml:593 boot-installer.xml:1012 boot-installer.xml:1827 boot-installer.xml:2080 boot-installer.xml:2434
 #, no-c-format
 #. Tag: title
 msgid "Booting from a CD-ROM"
@@ -645,7 +645,7 @@ msgid ""
       "       label=newinstall\n"
       "       initrd=/boot/newinstall/initrd.gz\n"
       "       root=/dev/ram0\n"
-      "       append=\"<phrase condition=\"sarge\">devfs=mount,dall </phrase>ramdisk_size=12000\""
+      "       append=\"ramdisk_size=12000\""
 msgstr ""
 
 #: boot-installer.xml:777
@@ -662,136 +662,136 @@ msgid ""
       "title  New Install\n"
       "kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 ramdisk_size=12000\n"
       "initrd (hd0,0)/boot/newinstall/initrd.gz\n"
-      "</screen></informalexample> and reboot. <phrase condition=\"sarge\">If the boot fails, you can try adding <userinput>devfs=mount,dall</userinput> to the <quote>kernel</quote> line. </phrase>"
+      "</screen></informalexample> and reboot."
 msgstr ""
 
-#: boot-installer.xml:799
+#: boot-installer.xml:797
 #, no-c-format
 #. Tag: para
 msgid "Note that the value of the <userinput>ramdisk_size</userinput> may need to be adjusted for the size of the initrd image. From here on, there should be no difference between <command>GRUB</command> or <command>LILO</command>."
 msgstr ""
 
-#: boot-installer.xml:810
+#: boot-installer.xml:808
 #, no-c-format
 #. Tag: title
 msgid "Booting from USB Memory Stick"
 msgstr ""
 
-#: boot-installer.xml:811
+#: boot-installer.xml:809
 #, no-c-format
 #. Tag: para
 msgid "Let's assume you have prepared everything from <xref linkend=\"boot-dev-select\"/> and <xref linkend=\"boot-usb-files\"/>. Now just plug your USB stick into some free USB connector and reboot the computer. The system should boot up, and you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;."
 msgstr ""
 
-#: boot-installer.xml:820
+#: boot-installer.xml:818
 #, no-c-format
 #. Tag: para
 msgid "In case your computer doesn't support booting from USB memory devices, you can still use a single floppy to do the initial boot and then switch to USB. Boot your system as described in <xref linkend=\"floppy-boot\"/>; the kernel on the boot floppy should detect your USB stick automatically. When it asks for the root floppy, simply press &enterkey;. You should see &d-i; starting."
 msgstr ""
 
-#: boot-installer.xml:833 boot-installer.xml:1952 boot-installer.xml:2353 boot-installer.xml:2501
+#: boot-installer.xml:831 boot-installer.xml:1939 boot-installer.xml:2340 boot-installer.xml:2488
 #, no-c-format
 #. Tag: title
 msgid "Booting from Floppies"
 msgstr ""
 
-#: boot-installer.xml:834 boot-installer.xml:2361
+#: boot-installer.xml:832 boot-installer.xml:2348
 #, no-c-format
 #. Tag: para
 msgid "You will have already downloaded the floppy images you needed and created floppies from the images in <xref linkend=\"create-floppy\"/>."
 msgstr ""
 
-#: boot-installer.xml:841
+#: boot-installer.xml:839
 #, no-c-format
 #. Tag: para
 msgid "To boot from the installer boot floppy, place it in the primary floppy drive, shut down the system as you normally would, then turn it back on."
 msgstr ""
 
-#: boot-installer.xml:847
+#: boot-installer.xml:845
 #, no-c-format
 #. Tag: para
 msgid "For installing from an LS-120 drive (ATAPI version) with a set of floppies, you need to specify the virtual location for the floppy device. This is done with the <emphasis>root=</emphasis> boot argument, giving the device that the ide-floppy driver maps the device to. For example, if your LS-120 drive is connected as the first IDE device (master) on the second cable, you enter <userinput>linux root=/dev/hdc</userinput> at the boot prompt. Installation from LS-120 is only supported by 2.4 and later kernels."
 msgstr ""
 
-#: boot-installer.xml:858
+#: boot-installer.xml:856
 #, no-c-format
 #. Tag: para
 msgid "Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> does not properly reset the machine, so a <quote>hard</quote> reboot is recommended. If you are installing from an existing operating system (e.g., from a DOS box) you don't have a choice. Otherwise, please do a hard reboot when booting."
 msgstr ""
 
-#: boot-installer.xml:867
+#: boot-installer.xml:865
 #, no-c-format
 #. Tag: para
 msgid "The floppy disk will be accessed, and you should then see a screen that introduces the boot floppy and ends with the <prompt>boot:</prompt> prompt."
 msgstr ""
 
-#: boot-installer.xml:873
+#: boot-installer.xml:871
 #, no-c-format
 #. Tag: para
 msgid "Once you press &enterkey;, you should see the message <computeroutput>Loading...</computeroutput>, followed by <computeroutput>Uncompressing Linux...</computeroutput>, and then a screenfull or so of information about the hardware in your system. More information on this phase of the boot process can be found below in <xref linkend=\"kernel-msgs\"/>."
 msgstr ""
 
-#: boot-installer.xml:882
+#: boot-installer.xml:880
 #, no-c-format
 #. Tag: para
 msgid "After booting from the boot floppy, the root floppy is requested. Insert the root floppy and press &enterkey;, and the contents are loaded into memory. The installer program <command>debian-installer</command> is automatically launched."
 msgstr ""
 
-#: boot-installer.xml:916
+#: boot-installer.xml:914
 #, no-c-format
 #. Tag: para
 msgid "There are various ways to do a TFTP boot on i386."
 msgstr ""
 
-#: boot-installer.xml:922
+#: boot-installer.xml:920
 #, no-c-format
 #. Tag: title
 msgid "NIC or Motherboard that support PXE"
 msgstr ""
 
-#: boot-installer.xml:923
+#: boot-installer.xml:921
 #, no-c-format
 #. Tag: para
 msgid "It could be that your Network Interface Card or Motherboard provides PXE boot functionality. This is a <trademark class=\"trade\">Intel</trademark> re-implementation of TFTP boot. If so you may be able to configure your BIOS to boot from the network."
 msgstr ""
 
-#: boot-installer.xml:934
+#: boot-installer.xml:932
 #, no-c-format
 #. Tag: title
 msgid "NIC with Network BootROM"
 msgstr ""
 
-#: boot-installer.xml:935
+#: boot-installer.xml:933
 #, no-c-format
 #. Tag: para
 msgid "It could be that your Network Interface Card provides TFTP boot functionality."
 msgstr ""
 
-#: boot-installer.xml:940
+#: boot-installer.xml:938
 #, no-c-format
 #. Tag: para
 msgid "Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. Please refer to this document."
 msgstr ""
 
-#: boot-installer.xml:948
+#: boot-installer.xml:946
 #, no-c-format
 #. Tag: title
 msgid "Etherboot"
 msgstr ""
 
-#: boot-installer.xml:949
+#: boot-installer.xml:947
 #, no-c-format
 #. Tag: para
 msgid "The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> provides bootdiskettes and even bootroms that do a TFTPboot."
 msgstr ""
 
-#: boot-installer.xml:958
+#: boot-installer.xml:956
 #, no-c-format
 #. Tag: title
 msgid "The Boot Prompt"
 msgstr ""
 
-#: boot-installer.xml:959
+#: boot-installer.xml:957
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -800,253 +800,253 @@ msgid ""
       "</screen></informalexample> At the boot prompt you can either just press &enterkey; to boot the installer with default options or enter a specific boot method and, optionally, boot parameters."
 msgstr ""
 
-#: boot-installer.xml:971
+#: boot-installer.xml:969
 #, no-c-format
 #. Tag: para
-msgid "Information on available boot methods and on boot parameters which might be useful can be found by pressing <keycap>F2</keycap> through <phrase condition=\"sarge\"><keycap>F7</keycap></phrase><phrase condition=\"etch\"><keycap>F8</keycap></phrase>. If you add any parameters to the boot command line, be sure to type the boot method (the default is <userinput>linux</userinput>) and a space before the first parameter (e.g., <userinput>linux debconf/priority=medium</userinput>)."
+msgid "Information on available boot methods and on boot parameters which might be useful can be found by pressing <keycap>F2</keycap> through <keycap>F8</keycap>. If you add any parameters to the boot command line, be sure to type the boot method (the default is <userinput>linux</userinput>) and a space before the first parameter (e.g., <userinput>linux debconf/priority=medium</userinput>)."
 msgstr ""
 
-#: boot-installer.xml:981
+#: boot-installer.xml:978
 #, no-c-format
 #. Tag: para
 msgid "If you are installing the system via a remote management device that provides a text interface to the VGA console, you may not be able to see the initial graphical splash screen upon booting the installer; you may even not see the boot prompt. Examples of these devices include the text console of Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's <quote>Integrated Remote Assistant</quote> (IRA). You can blindly press F1<footnote> <para> In some cases these devices will require special escape sequences to enact this keypress, for example the IRA uses <keycombo> <keycap>Ctrl</keycap> <keycap>F</keycap> </keycombo>,&nbsp;<keycap>1</keycap>. </para> </footnote> to bypass this screen and view the help text. Once you are past the splash screen and at the help text your keystrokes will be echoed at the prompt as expected. To prevent the installer from using the framebuffer for the rest of the installation, you will also want to add <userinput>debian-installer/framebuffer=false</userinput> to the boot prompt, as described in the help text."
 msgstr ""
 
-#: boot-installer.xml:1056
+#: boot-installer.xml:1053
 #, no-c-format
 #. Tag: title
 msgid "CD Contents"
 msgstr ""
 
-#: boot-installer.xml:1058
+#: boot-installer.xml:1055
 #, no-c-format
 #. Tag: para
 msgid "There are three basic variations of Debian Install CDs. The <emphasis>Business Card</emphasis> CD has a minimal installation that will fit on the small form factor CD media. It requires a network connection in order to install the rest of the base installation and make a usable system. The <emphasis>Network Install</emphasis> CD has all of the packages for a base install but requires a network connection to a Debian mirror site in order to install the extra packages one would want for a complete system . The set of Debian CDs can install a complete system from the wide range of packages without needing access to the network."
 msgstr ""
 
-#: boot-installer.xml:1074
+#: boot-installer.xml:1071
 #, no-c-format
 #. Tag: para
 msgid "The IA-64 architecture uses the next generation Extensible Firmware Interface (EFI) from Intel. Unlike the traditional x86 BIOS which knows little about the boot device other than the partition table and Master Boot Record (MBR), EFI can read and write files from FAT16 or FAT32 formatted disk partitions. This simplifies the often arcane process of starting a system. The system boot loader and the EFI firmware that supports it have a full filesystem to store the files necessary for booting the machine. This means that the system disk on an IA-64 system has an additional disk partition dedicated to EFI instead of the simple MBR or boot block on more conventional systems."
 msgstr ""
 
-#: boot-installer.xml:1090
+#: boot-installer.xml:1087
 #, no-c-format
 #. Tag: para
 msgid "The Debian Installer CD contains a small EFI partition where the <command>ELILO</command> bootloader, its configuration file, the installer's kernel, and initial filesystem (initrd) are located. The running system also contains an EFI partition where the necessary files for booting the system reside. These files are readable from the EFI Shell as described below."
 msgstr ""
 
-#: boot-installer.xml:1099
+#: boot-installer.xml:1096
 #, no-c-format
 #. Tag: para
 msgid "Most of the details of how <command>ELILO</command> actually loads and starts a system are transparent to the system installer. However, the installer must set up an EFI partition prior to installing the base system. Otherwise, the installation of <command>ELILO</command> will fail, rendering the system un-bootable. The EFI partition is allocated and formatted in the partitioning step of the installation prior to loading any packages on the system disk. The partitioning task also verifies that a suitable EFI partition is present before allowing the installation to proceed."
 msgstr ""
 
-#: boot-installer.xml:1111
+#: boot-installer.xml:1108
 #, no-c-format
 #. Tag: para
 msgid "The EFI Boot Manager is presented as the last step of the firmware initialization. It displays a menu list from which the user can select an option. Depending on the model of system and what other software has been loaded on the system, this menu may be different from one system to another. There should be at least two menu items displayed, <command>Boot Option Maintenance Menu</command> and <command>EFI Shell (Built-in)</command>. Using the first option is preferred, however, if that option is not available or the CD for some reason does not boot with it, use the second option."
 msgstr ""
 
-#: boot-installer.xml:1130
+#: boot-installer.xml:1127
 #, no-c-format
 #. Tag: title
 msgid "IMPORTANT"
 msgstr ""
 
-#: boot-installer.xml:1131
+#: boot-installer.xml:1128
 #, no-c-format
 #. Tag: para
 msgid "The EFI Boot Manager will select a default boot action, typically the first menu choice, within a pre-set number of seconds. This is indicated by a countdown at the bottom of the screen. Once the timer expires and the systems starts the default action, you may have to reboot the machine in order to continue the installation. If the default action is the EFI Shell, you can return to the Boot Manager by running <command>exit</command> at the shell prompt."
 msgstr ""
 
-#: boot-installer.xml:1143
+#: boot-installer.xml:1140
 #, no-c-format
 #. Tag: title
 msgid "Option 1: Booting from the Boot Option Maintenance Menu"
 msgstr ""
 
-#: boot-installer.xml:1150
+#: boot-installer.xml:1147
 #, no-c-format
 #. Tag: para
 msgid "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will display the EFI Boot Manager page and menu after it completes its system initialization."
 msgstr ""
 
-#: boot-installer.xml:1156
+#: boot-installer.xml:1153
 #, no-c-format
 #. Tag: para
 msgid "Select <command>Boot Maintenance Menu</command> from the menu with the arrow keys and press <command>ENTER</command>. This will display a new menu."
 msgstr ""
 
-#: boot-installer.xml:1162
+#: boot-installer.xml:1159
 #, no-c-format
 #. Tag: para
 msgid "Select <command>Boot From a File</command> from the menu with the arrow keys and press <command>ENTER</command>. This will display a list of devices probed by the firmware. You should see two menu lines containing either the label <command>Debian Inst [Acpi ...</command> or <command>Removable Media Boot</command>. If you examine the rest of the menu line, you will notice that the device and controller information should be the same."
 msgstr ""
 
-#: boot-installer.xml:1173
+#: boot-installer.xml:1170
 #, no-c-format
 #. Tag: para
 msgid "You can choose either of the entries that refer to the CD/DVD drive. Select your choice with the arrow keys and press <command>ENTER</command>. If you choose <command>Removable Media Boot</command> the machine will immediately start the boot load sequence. If you choose <command>Debian Inst [Acpi ...</command> instead, it will display a directory listing of the bootable portion of the CD, requiring you to proceed to the next (additional) step."
 msgstr ""
 
-#: boot-installer.xml:1184
+#: boot-installer.xml:1181
 #, no-c-format
 #. Tag: para
 msgid "You will only need this step if you chose <command>Debian Inst [Acpi ...</command>. The directory listing will also show <command>[Treat like Removable Media Boot]</command> on the next to the last line. Select this line with the arrow keys and press <command>ENTER</command>. This will start the boot load sequence."
 msgstr ""
 
-#: boot-installer.xml:1196
+#: boot-installer.xml:1193
 #, no-c-format
 #. Tag: para
 msgid "These steps start the Debian boot loader which will display a menu page for you to select a boot kernel and options. Proceed to selecting the boot kernel and options."
 msgstr ""
 
-#: boot-installer.xml:1206
+#: boot-installer.xml:1203
 #, no-c-format
 #. Tag: title
 msgid "Option 2: Booting from the EFI Shell"
 msgstr ""
 
-#: boot-installer.xml:1207
+#: boot-installer.xml:1204
 #, no-c-format
 #. Tag: para
 msgid "If, for some reason, option 1 is not successful, reboot the machine and when the EFI Boot Manager screen appears there should be one option called <command>EFI Shell [Built-in]</command>. Boot the Debian Installer CD with the following steps:"
 msgstr ""
 
-#: boot-installer.xml:1218
+#: boot-installer.xml:1215
 #, no-c-format
 #. Tag: para
 msgid "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will display the EFI Boot Manager page and menu after it completes system initialization."
 msgstr ""
 
-#: boot-installer.xml:1224
+#: boot-installer.xml:1221
 #, no-c-format
 #. Tag: para
 msgid "Select <command>EFI Shell</command> from the menu with the arrow keys and press <command>ENTER</command>. The EFI Shell will scan all of the bootable devices and display them to the console before displaying its command prompt. The recognized bootable partitions on devices will show a device name of <filename>fs<replaceable>n</replaceable>:</filename>. All other recognized partitions will be named <filename>blk<replaceable>n</replaceable>:</filename>. If you inserted the CD just before entering the shell, this may take a few extra seconds as it initializes the CD drive."
 msgstr ""
 
-#: boot-installer.xml:1238
+#: boot-installer.xml:1235
 #, no-c-format
 #. Tag: para
 msgid "Examine the output from the shell looking for the CDROM drive. It is most likely the <filename>fs0:</filename> device although other devices with bootable partitions will also show up as <filename>fs<replaceable>n</replaceable></filename>."
 msgstr ""
 
-#: boot-installer.xml:1245
+#: boot-installer.xml:1242
 #, no-c-format
 #. Tag: para
 msgid "Enter <command>fs<replaceable>n</replaceable>:</command> and press <command>ENTER</command> to select that device where <replaceable>n</replaceable> is the partition number for the CDROM. The shell will now display the partition number as its prompt."
 msgstr ""
 
-#: boot-installer.xml:1252
+#: boot-installer.xml:1249
 #, no-c-format
 #. Tag: para
 msgid "Enter <command>elilo</command> and press <command>ENTER</command>. This will start the boot load sequence."
 msgstr ""
 
-#: boot-installer.xml:1259
+#: boot-installer.xml:1256
 #, no-c-format
 #. Tag: para
 msgid "As with option 1, these steps start the Debian boot loader which will display a menu page for you to select a boot kernel and options. You can also enter the shorter <command>fs<replaceable>n</replaceable>:elilo</command> command at the shell prompt. Proceed to selecting the boot kernel and options."
 msgstr ""
 
-#: boot-installer.xml:1273
+#: boot-installer.xml:1270
 #, no-c-format
 #. Tag: title
 msgid "Installing using a Serial Console"
 msgstr ""
 
-#: boot-installer.xml:1275
+#: boot-installer.xml:1272
 #, no-c-format
 #. Tag: para
 msgid "You may choose to perform an install using a monitor and keyboard or using a serial connection. To use a monitor/keyboard setup, select an option containing the string [VGA console]. To install over a serial connection, choose an option containing the string [<replaceable>BAUD</replaceable> baud serial console], where <replaceable>BAUD</replaceable> is the speed of your serial console. Menu items for the most typical baud rate settings on the ttyS0 device are preconfigured."
 msgstr ""
 
-#: boot-installer.xml:1286
+#: boot-installer.xml:1283
 #, no-c-format
 #. Tag: para
 msgid "In most circumstances, you will want the installer to use the same baud rate as your connection to the EFI console. If you aren't sure what this setting is, you can obtain it using the command <command>baud</command> at the EFI shell."
 msgstr ""
 
-#: boot-installer.xml:1293
+#: boot-installer.xml:1290
 #, no-c-format
 #. Tag: para
 msgid "If there is not an option available that is configured for the serial device or baud rate you would like to use, you may override the console setting for one of the existing menu options. For example, to use a 57600 baud console over the ttyS1 device, enter <command>console=ttyS1,57600n8</command> into the <classname>Boot:</classname> text window."
 msgstr ""
 
-#: boot-installer.xml:1304
+#: boot-installer.xml:1301
 #, no-c-format
 #. Tag: para
 msgid "Most IA-64 boxes ship with a default console setting of 9600 baud. This setting is rather slow, and the normal installation process will take a significant time to draw each screen. You should consider either increasing the baud rate used for performing the installation, or performing a Text Mode installation. See the <classname>Params</classname> help menu for instructions on starting the installer in Text Mode."
 msgstr ""
 
-#: boot-installer.xml:1313
+#: boot-installer.xml:1310
 #, no-c-format
 #. Tag: para
 msgid "If you select the wrong console type, you will be able to select the kernel and enter parameters but both the display and your input will go dead as soon as the kernel starts, requiring you to reboot before you can begin the installation."
 msgstr ""
 
-#: boot-installer.xml:1322
+#: boot-installer.xml:1319
 #, no-c-format
 #. Tag: title
 msgid "Selecting the Boot Kernel and Options"
 msgstr ""
 
-#: boot-installer.xml:1324
+#: boot-installer.xml:1321
 #, no-c-format
 #. Tag: para
 msgid "The boot loader will display a form with a menu list and a text window with a <classname>Boot:</classname> prompt. The arrow keys select an item from the menu and any text typed at the keyboard will appear in the text window. There are also help screens which can be displayed by pressing the appropriate function key. The <classname>General</classname> help screen explains the menu choices and the <classname>Params</classname> screen explains the common command line options."
 msgstr ""
 
-#: boot-installer.xml:1336
+#: boot-installer.xml:1333
 #, no-c-format
 #. Tag: para
 msgid "Consult the <classname>General</classname> help screen for the description of the kernels and install modes most appropriate for your installation. You should also consult <xref linkend=\"boot-parms\"/> below for any additional parameters that you may want to set in the <classname>Boot:</classname> text window. The kernel version you choose selects the kernel version that will be used for both the installation process and the installed system. If you encounter kernel problems with the installation, you may also have those same problems with the system you install. The following two steps will select and start the install:"
 msgstr ""
 
-#: boot-installer.xml:1354
+#: boot-installer.xml:1351
 #, no-c-format
 #. Tag: para
 msgid "Select the kernel version and installation mode most appropriate to your needs with the arrow keys."
 msgstr ""
 
-#: boot-installer.xml:1359
+#: boot-installer.xml:1356
 #, no-c-format
 #. Tag: para
 msgid "Enter any boot parameters by typing at the keyboard. The text will be displayed directly in the text window. This is where kernel parameters (such as serial console settings) are specified."
 msgstr ""
 
-#: boot-installer.xml:1366
+#: boot-installer.xml:1363
 #, no-c-format
 #. Tag: para
 msgid "Press <command>ENTER</command>. This will load and start the kernel. The kernel will display its usual initialization messages followed by the first screen of the Debian Installer."
 msgstr ""
 
-#: boot-installer.xml:1375
+#: boot-installer.xml:1372
 #, no-c-format
 #. Tag: para
 msgid "Proceed to the next chapter to continue the installation where you will set up the language locale, network, and disk partitions."
 msgstr ""
 
-#: boot-installer.xml:1386
+#: boot-installer.xml:1383
 #, no-c-format
 #. Tag: para
 msgid "Booting an IA64 system from the network is similar to a CD boot. The only difference is how the installation kernel is loaded. The EFI Boot Manager can load and start programs from a server on the network. Once the installation kernel is loaded and starts, the system install will proceed thru the same steps as the CD install with the exception that the packages of the base install will be loaded from the network rather than the CD drive."
 msgstr ""
 
-#: boot-installer.xml:1420
+#: boot-installer.xml:1417
 #, no-c-format
 #. Tag: para
 msgid "Network booting an ia64 system requires two architecture-specific actions. On the boot server, DHCP and TFTP must be configured to deliver <command>elilo</command>. On the client a new boot option must be defined in the EFI boot manager to enable loading over a network."
 msgstr ""
 
-#: boot-installer.xml:1431
+#: boot-installer.xml:1428
 #, no-c-format
 #. Tag: title
 msgid "Configuring the Server"
 msgstr ""
 
-#: boot-installer.xml:1432
+#: boot-installer.xml:1429
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1059,13 +1059,13 @@ msgid ""
       "</screen></informalexample> Note that the goal is to get <command>elilo.efi</command> running on the client."
 msgstr ""
 
-#: boot-installer.xml:1442
+#: boot-installer.xml:1439
 #, no-c-format
 #. Tag: para
 msgid "Extract the <filename>netboot.tar.gz</filename> file into the directory used as the root for your tftp server. Typical tftp root directories include <filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. This will create a <filename>debian-installer</filename> directory tree containing the boot files for an IA-64 system."
 msgstr ""
 
-#: boot-installer.xml:1452
+#: boot-installer.xml:1449
 #, no-c-format
 #. Tag: screen
 msgid ""
@@ -1077,343 +1077,337 @@ msgid ""
       "[...]"
 msgstr ""
 
-#: boot-installer.xml:1452
+#: boot-installer.xml:1449
 #, no-c-format
 #. Tag: para
 msgid "The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</filename> file that should work for most configurations. However, should you need to make changes to this file, you can find it in the <filename>debian-installer/ia64/</filename> directory. It is possible to have different config files for different clients by naming them using the client's IP address in hex with the suffix <filename>.conf</filename> instead of <filename>elilo.conf</filename>. See documentation provided in the <classname>elilo</classname> package for details."
 msgstr ""
 
-#: boot-installer.xml:1469
+#: boot-installer.xml:1466
 #, no-c-format
 #. Tag: title
 msgid "Configuring the Client"
 msgstr ""
 
-#: boot-installer.xml:1470
+#: boot-installer.xml:1467
 #, no-c-format
 #. Tag: para
 msgid "To configure the client to support TFTP booting, start by booting to EFI and entering the <guimenu>Boot Option Maintenance Menu</guimenu>. <itemizedlist> <listitem><para> Add a boot option. </para></listitem> <listitem><para> You should see one or more lines with the text <guimenuitem>Load File [Acpi()/.../Mac()]</guimenuitem>. If more than one of these entries exist, choose the one containing the MAC address of the interface from which you'll be booting. Use the arrow keys to highlight your choice, then press enter. </para></listitem> <listitem><para> Name the entry <userinput>Netboot</userinput> or something similar, save, and exit back to the boot options menu. </para></listitem> </itemizedlist> You should see the new boot option you just created, and selecting it should initiate a DHCP query, leading to a TFTP load of <filename>elilo.efi</filename> from the server."
 msgstr ""
 
-#: boot-installer.xml:1502
+#: boot-installer.xml:1499
 #, no-c-format
 #. Tag: para
 msgid "The boot loader will display its prompt after it has downloaded and processed its configuration file. At this point, the installation proceeds with the same steps as a CD install. Select a boot option as in above and when the kernel has completed installing itself from the network, it will start the Debian Installer."
 msgstr ""
 
-#: boot-installer.xml:1511
+#: boot-installer.xml:1508
 #, no-c-format
 #. Tag: para
 msgid "Proceed to the next chapter to continue the installation where you will set up the language locale, network, and the disk partitions."
 msgstr ""
 
-#: boot-installer.xml:1524
+#: boot-installer.xml:1521
 #, no-c-format
 #. Tag: title
 msgid "Choosing an Installation Method"
 msgstr ""
 
-#: boot-installer.xml:1526
+#: boot-installer.xml:1523
 #, no-c-format
 #. Tag: para
 msgid "Some &arch-title; subarchs have the option of booting using either a 2.4.x or 2.2.x linux kernel. When such a choice exists, try the 2.4.x linux kernel. The installer should also require less memory when using a 2.4.x linux kernel as 2.2.x support requires a fixed-sized ramdisk and 2.4.x uses tmpfs."
 msgstr ""
 
-#: boot-installer.xml:1534
+#: boot-installer.xml:1531
 #, no-c-format
 #. Tag: para
 msgid "If you are using a 2.2.x linux kernel, then you need to use the &ramdisksize; kernel parameter."
 msgstr ""
 
-#: boot-installer.xml:1541
-#, no-c-format
-#. Tag: para
-msgid "Also, if you are using a 2.2.x linux kernel, then you must make sure you are using a ramdisk built to accommodate it, see the <ulink url=\"&disturl;/main/installer-&architecture;/current/images/MANIFEST\">MANIFEST</ulink>. In general, this means you need to use the initrd22.gz ramdisk from the respective directory."
-msgstr ""
-
-#: boot-installer.xml:1549
+#: boot-installer.xml:1536
 #, no-c-format
 #. Tag: para
 msgid "Make sure <userinput>root=/dev/ram</userinput> is one of your kernel parameters."
 msgstr ""
 
-#: boot-installer.xml:1554
+#: boot-installer.xml:1541
 #, no-c-format
 #. Tag: para
 msgid "If you're having trouble, check <ulink url=\"&url-m68k-cts-faq;\">cts's &arch-title; debian-installer FAQ</ulink>."
 msgstr ""
 
-#: boot-installer.xml:1571
+#: boot-installer.xml:1558
 #, no-c-format
 #. Tag: title
 msgid "Amiga"
 msgstr ""
 
-#: boot-installer.xml:1572
+#: boot-installer.xml:1559
 #, no-c-format
 #. Tag: para
 msgid "The only method of installation available to amiga is the hard drive (see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>"
 msgstr ""
 
-#: boot-installer.xml:1578
+#: boot-installer.xml:1565
 #, no-c-format
 #. Tag: para
 msgid "Amiga does not currently work with bogl, so if you are seeing bogl errors, you need to include the kernel parameter <userinput>debian-installer/framebuffer=false</userinput>."
 msgstr ""
 
-#: boot-installer.xml:1587
+#: boot-installer.xml:1574
 #, no-c-format
 #. Tag: title
 msgid "Atari"
 msgstr ""
 
-#: boot-installer.xml:1588
+#: boot-installer.xml:1575
 #, no-c-format
 #. Tag: para
 msgid "The installer for atari may be started from either the hard drive (see <xref linkend=\"m68k-boot-hd\"/>) or from floppies (see <xref linkend=\"boot-from-floppies\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>"
 msgstr ""
 
-#: boot-installer.xml:1595
+#: boot-installer.xml:1582
 #, no-c-format
 #. Tag: para
 msgid "Atari does not currently work with bogl, so if you are seeing bogl errors, you need to include the kernel parameter <userinput>debian-installer/framebuffer=false</userinput>."
 msgstr ""
 
-#: boot-installer.xml:1604
+#: boot-installer.xml:1591
 #, no-c-format
 #. Tag: title
 msgid "BVME6000"
 msgstr ""
 
-#: boot-installer.xml:1605
+#: boot-installer.xml:1592
 #, no-c-format
 #. Tag: para
 msgid "The installer for BVME6000 may be started from a cdrom (see <xref linkend=\"m68k-boot-cdrom\"/>), floppies (see <xref linkend=\"boot-from-floppies\"/>), or the net (see <xref linkend=\"boot-tftp\"/>)."
 msgstr ""
 
-#: boot-installer.xml:1615
+#: boot-installer.xml:1602
 #, no-c-format
 #. Tag: title
 msgid "Macintosh"
 msgstr ""
 
-#: boot-installer.xml:1616
+#: boot-installer.xml:1603
 #, no-c-format
 #. Tag: para
 msgid "The only method of installation available to mac is from the hard drive (see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis> Macs do not have a working 2.4.x kernel."
 msgstr ""
 
-#: boot-installer.xml:1623
+#: boot-installer.xml:1610
 #, no-c-format
 #. Tag: para
 msgid "If your hardware uses a 53c9x-based scsi bus, then you may need to include the kernel parameter <userinput>mac53c9x=1,0</userinput>. Hardware with two such scsi buses, such as the Quadra 950, will need <userinput>mac53c9x=2,0</userinput> instead. Alternatively, the parameter can be specified as <userinput>mac53c9x=-1,0</userinput> which will leave autodetection on, but which will disable SCSI disconnects. Note that specifying this parameter is only necessary if you have more than one hard disk; otherwise, the system will run faster if you do not specify it."
 msgstr ""
 
-#: boot-installer.xml:1638
+#: boot-installer.xml:1625
 #, no-c-format
 #. Tag: title
 msgid "MVME147 and MVME16x"
 msgstr ""
 
-#: boot-installer.xml:1639
+#: boot-installer.xml:1626
 #, no-c-format
 #. Tag: para
 msgid "The installer for MVME147 and MVME16x may be started from either floppies (see <xref linkend=\"boot-from-floppies\"/>) or the net (see <xref linkend=\"boot-tftp\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>"
 msgstr ""
 
-#: boot-installer.xml:1649
+#: boot-installer.xml:1636
 #, no-c-format
 #. Tag: title
 msgid "Q40/Q60"
 msgstr ""
 
-#: boot-installer.xml:1650
+#: boot-installer.xml:1637
 #, no-c-format
 #. Tag: para
 msgid "The only method of installation available to Q40/Q60 is from the hard drive (see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>"
 msgstr ""
 
-#: boot-installer.xml:1661
+#: boot-installer.xml:1648
 #, no-c-format
 #. Tag: title
 msgid "Booting from a Hard Disk"
 msgstr ""
 
-#: boot-installer.xml:1667 boot-installer.xml:2172
+#: boot-installer.xml:1654 boot-installer.xml:2159
 #, no-c-format
 #. Tag: para
 msgid "Booting from an existing operating system is often a convenient option; for some systems it is the only supported method of installation."
 msgstr ""
 
-#: boot-installer.xml:1673 boot-installer.xml:2178
+#: boot-installer.xml:1660 boot-installer.xml:2165
 #, no-c-format
 #. Tag: para
 msgid "To boot the installer from hard disk, you will have already completed downloading and placing the needed files in <xref linkend=\"boot-drive-files\"/>."
 msgstr ""
 
-#: boot-installer.xml:1682
+#: boot-installer.xml:1669
 #, no-c-format
 #. Tag: para
 msgid "At least six different ramdisks may be used to boot from the hard drive, three different types each with and without support for a 2.2.x linux kernel (see <ulink url=\"&disturl;/main/installer-&architecture;/current/images/MANIFEST\">MANIFEST</ulink> for details)."
 msgstr ""
 
-#: boot-installer.xml:1690
+#: boot-installer.xml:1677
 #, no-c-format
 #. Tag: para
 msgid "The three different types of ramdisks are <filename>cdrom</filename>, <filename>hd-media</filename>, and <filename>nativehd</filename>. These ramdisks differ only in their source for installation packages. The <filename>cdrom</filename> ramdisk uses a cdrom to get debian-installer packages. The <filename>hd-media</filename> ramdisk uses an iso image file of a cdrom currently residing on a hard disk. Finally, the <filename>nativehd</filename> ramdisk uses the net to install packages."
 msgstr ""
 
-#: boot-installer.xml:1711
+#: boot-installer.xml:1698
 #, no-c-format
 #. Tag: title
 msgid "Booting from AmigaOS"
 msgstr ""
 
-#: boot-installer.xml:1712
+#: boot-installer.xml:1699
 #, no-c-format
 #. Tag: para
 msgid "In the <command>Workbench</command>, start the Linux installation process by double-clicking on the <guiicon>StartInstall</guiicon> icon in the <filename>debian</filename> directory."
 msgstr ""
 
-#: boot-installer.xml:1718
+#: boot-installer.xml:1705
 #, no-c-format
 #. Tag: para
 msgid "You may have to press the &enterkey; key twice after the Amiga installer program has output some debugging information into a window. After this, the screen will go grey, there will be a few seconds' delay. Next, a black screen with white text should come up, displaying all kinds of kernel debugging information. These messages may scroll by too fast for you to read, but that's OK. After a couple of seconds, the installation program should start automatically, so you can continue down at <xref linkend=\"d-i-intro\"/>."
 msgstr ""
 
-#: boot-installer.xml:1733
+#: boot-installer.xml:1720
 #, no-c-format
 #. Tag: title
 msgid "Booting from Atari TOS"
 msgstr ""
 
-#: boot-installer.xml:1734
+#: boot-installer.xml:1721
 #, no-c-format
 #. Tag: para
 msgid "At the GEM desktop, start the Linux installation process by double-clicking on the <guiicon>bootstra.prg</guiicon> icon in the <filename>debian</filename> directory and clicking <guibutton>Ok</guibutton> at the program options dialog box."
 msgstr ""
 
-#: boot-installer.xml:1741
+#: boot-installer.xml:1728
 #, no-c-format
 #. Tag: para
 msgid "You may have to press the &enterkey; key after the Atari bootstrap program has output some debugging information into a window. After this, the screen will go grey, there will be a few seconds' delay. Next, a black screen with white text should come up, displaying all kinds of kernel debugging information. These messages may scroll by too fast for you to read, but that's OK. After a couple of seconds, the installation program should start automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>."
 msgstr ""
 
-#: boot-installer.xml:1756
+#: boot-installer.xml:1743
 #, no-c-format
 #. Tag: title
 msgid "Booting from MacOS"
 msgstr ""
 
-#: boot-installer.xml:1757
+#: boot-installer.xml:1744
 #, no-c-format
 #. Tag: para
 msgid "You must retain the original Mac system and boot from it. It is <emphasis>essential</emphasis> that, when booting MacOS in preparation for booting the Penguin linux loader, you hold the <keycap>shift</keycap> key down to prevent extensions from loading. If you don't use MacOS except for loading linux, you can accomplish the same thing by removing all extensions and control panels from the Mac's System Folder. Otherwise extensions may be left running and cause random problems with the running linux kernel."
 msgstr ""
 
-#: boot-installer.xml:1768
+#: boot-installer.xml:1755
 #, no-c-format
 #. Tag: para
 msgid "Macs require the <command>Penguin</command> bootloader. If you do not have the tools to handle a <command>Stuffit</command> archive, &penguin19.hfs; is an hfs disk image with <command>Penguin</command> unpacked. <xref linkend=\"create-floppy\"/> describes how to copy this image to a floppy."
 msgstr ""
 
-#: boot-installer.xml:1777
+#: boot-installer.xml:1764
 #, no-c-format
 #. Tag: para
 msgid "At the MacOS desktop, start the Linux installation process by double-clicking on the <guiicon>Penguin Prefs</guiicon> icon in the <filename>Penguin</filename> directory. The <command>Penguin</command> booter will start up. Go to the <guimenuitem>Settings</guimenuitem> item in the <guimenu>File</guimenu> menu, click the <guilabel>Kernel</guilabel> tab. Select the kernel (<filename>vmlinuz</filename>) and ramdisk (<filename>initrd.gz</filename>) images in the <filename>install</filename> directory by clicking on the corresponding buttons in the upper right corner, and navigating the file select dialogs to locate the files."
 msgstr ""
 
-#: boot-installer.xml:1792
+#: boot-installer.xml:1779
 #, no-c-format
 #. Tag: para
 msgid "To set the boot parameters in Penguin, choose <guimenu>File</guimenu> -&gt; <guimenuitem>Settings...</guimenuitem>, then switch to the <guilabel>Options</guilabel> tab. Boot parameters may be typed in to the text entry area. If you will always want to use these settings, select <guimenu>File</guimenu> -&gt; <guimenuitem>Save Settings as Default</guimenuitem>."
 msgstr ""
 
-#: boot-installer.xml:1801
+#: boot-installer.xml:1788
 #, no-c-format
 #. Tag: para
 msgid "Close the <guilabel>Settings</guilabel> dialog, save the settings and start the bootstrap using the <guimenuitem>Boot Now</guimenuitem> item in the <guimenu>File</guimenu> menu."
 msgstr ""
 
-#: boot-installer.xml:1808
+#: boot-installer.xml:1795
 #, no-c-format
 #. Tag: para
 msgid "The <command>Penguin</command> booter will output some debugging information into a window. After this, the screen will go grey, there will be a few seconds' delay. Next, a black screen with white text should come up, displaying all kinds of kernel debugging information. These messages may scroll by too fast for you to read, but that's OK. After a couple of seconds, the installation program should start automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>."
 msgstr ""
 
-#: boot-installer.xml:1823
+#: boot-installer.xml:1810
 #, no-c-format
 #. Tag: title
 msgid "Booting from Q40/Q60"
 msgstr ""
 
-#: boot-installer.xml:1825
+#: boot-installer.xml:1812
 #, no-c-format
 #. Tag: para
 msgid "FIXME"
 msgstr ""
 
-#: boot-installer.xml:1829
+#: boot-installer.xml:1816
 #, no-c-format
 #. Tag: para
 msgid "The installation program should start automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>."
 msgstr ""
 
-#: boot-installer.xml:1841
+#: boot-installer.xml:1828
 #, no-c-format
 #. Tag: para
 msgid "Currently, the only &arch-title; subarchitecture that supports CD-ROM booting is the BVME6000."
 msgstr ""
 
-#: boot-installer.xml:1913
+#: boot-installer.xml:1900
 #, no-c-format
 #. Tag: para
 msgid "After booting the VMEbus systems you will be presented with the LILO <prompt>Boot:</prompt> prompt. At that prompt enter one of the following to boot Linux and begin installation proper of the Debian software using vt102 terminal emulation:"
 msgstr ""
 
-#: boot-installer.xml:1924
+#: boot-installer.xml:1911
 #, no-c-format
 #. Tag: para
 msgid "type <screen>i6000 &enterkey;</screen> to install a BVME4000/6000"
 msgstr ""
 
-#: boot-installer.xml:1929
+#: boot-installer.xml:1916
 #, no-c-format
 #. Tag: para
 msgid "type <screen>i162 &enterkey;</screen> to install an MVME162"
 msgstr ""
 
-#: boot-installer.xml:1934
+#: boot-installer.xml:1921
 #, no-c-format
 #. Tag: para
 msgid "type <screen>i167 &enterkey;</screen> to install an MVME166/167"
 msgstr ""
 
-#: boot-installer.xml:1941
+#: boot-installer.xml:1928
 #, no-c-format
 #. Tag: para
 msgid "You may additionally append the string <screen>TERM=vt100</screen> to use vt100 terminal emulation, e.g., <screen>i6000 TERM=vt100 &enterkey;</screen>."
 msgstr ""
 
-#: boot-installer.xml:1953
+#: boot-installer.xml:1940
 #, no-c-format
 #. Tag: para
 msgid "For most &arch-title; architectures, booting from a local filesystem is the recommended method."
 msgstr ""
 
-#: boot-installer.xml:1958
+#: boot-installer.xml:1945
 #, no-c-format
 #. Tag: para
 msgid "Booting from the boot floppy is supported only for Atari and VME (with a SCSI floppy drive on VME) at this time."
 msgstr ""
 
-#: boot-installer.xml:1974 boot-installer.xml:2021
+#: boot-installer.xml:1961 boot-installer.xml:2008
 #, no-c-format
 #. Tag: title
 msgid "SGI Indys TFTP Booting"
 msgstr ""
 
-#: boot-installer.xml:1975
+#: boot-installer.xml:1962
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1424,13 +1418,13 @@ msgid ""
       "</screen></informalexample> in the command monitor to do this."
 msgstr ""
 
-#: boot-installer.xml:1994 boot-installer.xml:2043
+#: boot-installer.xml:1981 boot-installer.xml:2030
 #, no-c-format
 #. Tag: title
 msgid "Broadcom BCM91250A TFTP Booting"
 msgstr ""
 
-#: boot-installer.xml:1995
+#: boot-installer.xml:1982
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1441,19 +1435,19 @@ msgid ""
       "</screen></informalexample> You need to substitute the IP address listed in this example with either the name or the IP address of your TFTP server. Once you issue this command, the installer will be loaded automatically."
 msgstr ""
 
-#: boot-installer.xml:2018 boot-installer.xml:2552
+#: boot-installer.xml:2005 boot-installer.xml:2539
 #, no-c-format
 #. Tag: title
 msgid "Boot Parameters"
 msgstr ""
 
-#: boot-installer.xml:2022
+#: boot-installer.xml:2009
 #, no-c-format
 #. Tag: para
 msgid "On SGI Indys you can append boot parameters to the <command>bootp():</command> command in the command monitor."
 msgstr ""
 
-#: boot-installer.xml:2027
+#: boot-installer.xml:2014
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1462,109 +1456,109 @@ msgid ""
       "</screen></informalexample> Further kernel parameters can be passed via <command>append</command>:"
 msgstr ""
 
-#: boot-installer.xml:2037
+#: boot-installer.xml:2024
 #, no-c-format
 #. Tag: screen
 msgid "bootp(): append=\"root=/dev/sda1\""
 msgstr ""
 
-#: boot-installer.xml:2044
+#: boot-installer.xml:2031
 #, no-c-format
 #. Tag: para
 msgid "You cannot pass any boot parameters directly from the CFE prompt. Instead, you have to edit the <filename>/boot/sibyl.conf</filename> file on the TFTP server and add your parameters to the <replaceable>extra_args</replaceable> variable."
 msgstr ""
 
-#: boot-installer.xml:2061
+#: boot-installer.xml:2048
 #, no-c-format
 #. Tag: title
 msgid "s390 Limitations"
 msgstr ""
 
-#: boot-installer.xml:2062
+#: boot-installer.xml:2049
 #, no-c-format
 #. Tag: para
 msgid "In order to run the installation system a working network setup and ssh session is needed on S/390."
 msgstr ""
 
-#: boot-installer.xml:2067
+#: boot-installer.xml:2054
 #, no-c-format
 #. Tag: para
 msgid "The booting process starts with a network setup that prompts you for several network parameters. If the setup is successful, you will login to the system by starting a ssh session which will launch the standard installation system."
 msgstr ""
 
-#: boot-installer.xml:2078
+#: boot-installer.xml:2065
 #, no-c-format
 #. Tag: title
 msgid "s390 Boot Parameters"
 msgstr ""
 
-#: boot-installer.xml:2079
+#: boot-installer.xml:2066
 #, no-c-format
 #. Tag: para
 msgid "On S/390 you can append boot parameters in the parm file. This file can either be in ASCII or EBCDIC format. Please read <ulink url=\"&url-s390-devices;\">Device Drivers and Installation Commands</ulink> for more information about S/390-specific boot parameters."
 msgstr ""
 
-#: boot-installer.xml:2133
+#: boot-installer.xml:2120
 #, no-c-format
 #. Tag: para
 msgid "Currently, the only &arch-title; subarchitectures that support CD-ROM booting are PReP and New World PowerMacs. On PowerMacs, hold the <keycap>c</keycap> key, or else the combination of <keycap>Command</keycap>, <keycap>Option</keycap>, <keycap>Shift</keycap>, and <keycap>Delete</keycap> keys together while booting to boot from the CD-ROM."
 msgstr ""
 
-#: boot-installer.xml:2142
+#: boot-installer.xml:2129
 #, no-c-format
 #. Tag: para
 msgid "OldWorld PowerMacs will not boot a Debian CD, because OldWorld computers relied on a Mac OS ROM CD boot driver to be present on the CD, and a free-software version of this driver is not available. All OldWorld systems have floppy drives, so use the floppy drive to launch the installer, and then point the installer to the CD for the needed files."
 msgstr ""
 
-#: boot-installer.xml:2151
+#: boot-installer.xml:2138
 #, no-c-format
 #. Tag: para
 msgid "If your system doesn't boot directly from CD-ROM, you can still use the CD-ROM to install the system. On NewWorlds, you can also use an OpenFirmware command to boot from the CD-ROM manually. Follow the instructions in <xref linkend=\"boot-newworld\"/> for booting from the hard disk, except use the path to <command>yaboot</command> on the CD at the OF prompt, such as"
 msgstr ""
 
-#: boot-installer.xml:2160
+#: boot-installer.xml:2147
 #, no-c-format
 #. Tag: screen
 msgid "0 &gt; boot cd:,\\install\\yaboot"
 msgstr ""
 
-#: boot-installer.xml:2166
+#: boot-installer.xml:2153
 #, no-c-format
 #. Tag: title
 msgid "Booting from Hard Disk"
 msgstr ""
 
-#: boot-installer.xml:2187
+#: boot-installer.xml:2174
 #, no-c-format
 #. Tag: title
 msgid "Booting CHRP from OpenFirmware"
 msgstr ""
 
-#: boot-installer.xml:2191
+#: boot-installer.xml:2178
 #, no-c-format
 #. Tag: emphasis
 msgid "Not yet written."
 msgstr ""
 
-#: boot-installer.xml:2196
+#: boot-installer.xml:2183
 #, no-c-format
 #. Tag: title
 msgid "Booting OldWorld PowerMacs from MacOS"
 msgstr ""
 
-#: boot-installer.xml:2197
+#: boot-installer.xml:2184
 #, no-c-format
 #. Tag: para
 msgid "If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to boot into the installation system. Double click the <guiicon>BootX</guiicon> application icon. Click on the <guibutton>Options</guibutton> button and select <guilabel>Use Specified RAM Disk</guilabel>. This will give you the chance to select the <filename>ramdisk.image.gz</filename> file. You may need to select the <guilabel>No Video Driver</guilabel> checkbox, depending on your hardware. Then click the <guibutton>Linux</guibutton> button to shut down MacOS and launch the installer."
 msgstr ""
 
-#: boot-installer.xml:2215
+#: boot-installer.xml:2202
 #, no-c-format
 #. Tag: title
 msgid "Booting NewWorld Macs from OpenFirmware"
 msgstr ""
 
-#: boot-installer.xml:2216
+#: boot-installer.xml:2203
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1575,31 +1569,31 @@ msgid ""
       "</screen></informalexample> At yaboot's <prompt>boot:</prompt> prompt, type either <userinput>install</userinput> or <userinput>install video=ofonly</userinput> followed by a &enterkey;. The <userinput>video=ofonly</userinput> argument is for maximum compatibility; you can try it if <userinput>install</userinput> doesn't work. The Debian installation program should start."
 msgstr ""
 
-#: boot-installer.xml:2251
+#: boot-installer.xml:2238
 #, no-c-format
 #. Tag: title
 msgid "Booting from USB memory stick"
 msgstr ""
 
-#: boot-installer.xml:2252
+#: boot-installer.xml:2239
 #, no-c-format
 #. Tag: para
 msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
 msgstr ""
 
-#: boot-installer.xml:2258
+#: boot-installer.xml:2245
 #, no-c-format
 #. Tag: para
 msgid "Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/>. To boot a Macintosh system from a USB stick, you will need to use the Open Firmware prompt, since Open Firmware does not search USB storage devices by default. To get to the prompt, hold down <keycombo><keycap>Command</keycap> <keycap>Option</keycap> <keycap>o</keycap> <keycap>f</keycap></keycombo> all together while booting (see <xref linkend=\"invoking-openfirmware\"/>)."
 msgstr ""
 
-#: boot-installer.xml:2270
+#: boot-installer.xml:2257
 #, no-c-format
 #. Tag: para
 msgid "You will need to work out where the USB storage device appears in the device tree, since at the moment <command>ofpath</command> cannot work that out automatically. Type <userinput>dev / ls</userinput> and <userinput>devalias</userinput> at the Open Firmware prompt to get a list of all known devices and device aliases. On the author's system with various types of USB stick, paths such as <filename>usb0/disk</filename>, <filename>usb0/hub/disk</filename>, <filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and <filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work."
 msgstr ""
 
-#: boot-installer.xml:2282
+#: boot-installer.xml:2269
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1608,79 +1602,79 @@ msgid ""
       "</screen></informalexample> The <replaceable>2</replaceable> matches the Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image earlier, and the <userinput>,\\\\:tbxi</userinput> part instructs Open Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. <command>yaboot</command>) in the directory previously blessed with <command>hattrib -b</command>."
 msgstr ""
 
-#: boot-installer.xml:2296
+#: boot-installer.xml:2283
 #, no-c-format
 #. Tag: para
 msgid "The system should now boot up, and you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;."
 msgstr ""
 
-#: boot-installer.xml:2302
+#: boot-installer.xml:2289
 #, no-c-format
 #. Tag: para
 msgid "This boot method is new, and may be difficult to get to work on some NewWorld systems. If you have problems, please file an installation report, as explained in <xref linkend=\"submit-bug\"/>."
 msgstr ""
 
-#: boot-installer.xml:2335
+#: boot-installer.xml:2322
 #, no-c-format
 #. Tag: para
 msgid "Currently, PReP and New World PowerMac systems support netbooting."
 msgstr ""
 
-#: boot-installer.xml:2339
+#: boot-installer.xml:2326
 #, no-c-format
 #. Tag: para
 msgid "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command <command>boot enet:0</command>. PReP and CHRP boxes may have different ways of addressing the network. On a PReP machine, you should try <userinput>boot <replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>,<replaceable>client_ipaddr</replaceable></userinput>."
 msgstr ""
 
-#: boot-installer.xml:2354
+#: boot-installer.xml:2341
 #, no-c-format
 #. Tag: para
 msgid "Booting from floppies is supported for &arch-title;, although it is generally only applicable for OldWorld systems. NewWorld systems are not equipped with floppy drives, and attached USB floppy drives are not supported for booting."
 msgstr ""
 
-#: boot-installer.xml:2366
+#: boot-installer.xml:2353
 #, no-c-format
 #. Tag: para
 msgid "To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it in floppy drive after shutting the system down, and before pressing the power-on button."
 msgstr ""
 
-#: boot-installer.xml:2372
+#: boot-installer.xml:2359
 #, no-c-format
 #. Tag: para
 msgid "For those not familiar with Macintosh floppy operations: a floppy placed in the machine prior to boot will be the first priority for the system to boot from. A floppy without a valid boot system will be ejected, and the machine will then check for bootable hard disk partitions."
 msgstr ""
 
-#: boot-installer.xml:2379
+#: boot-installer.xml:2366
 #, no-c-format
 #. Tag: para
 msgid "After booting, the <filename>root.bin</filename> floppy is requested. Insert the root floppy and press &enterkey;. The installer program is automatically launched after the root system has been loaded into memory."
 msgstr ""
 
-#: boot-installer.xml:2390
+#: boot-installer.xml:2377
 #, no-c-format
 #. Tag: title
 msgid "PowerPC Boot Parameters"
 msgstr ""
 
-#: boot-installer.xml:2391
+#: boot-installer.xml:2378
 #, no-c-format
 #. Tag: para
 msgid "Many older Apple monitors used a 640x480 67Hz mode. If your video appears skewed on an older Apple monitor, try appending the boot argument <userinput>video=atyfb:vmode:6</userinput> , which will select that mode for most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to <userinput>video=aty128fb:vmode:6</userinput> ."
 msgstr ""
 
-#: boot-installer.xml:2431
+#: boot-installer.xml:2418
 #, no-c-format
 #. Tag: para
 msgid "On machines with OpenBoot, simply enter the boot monitor on the machine which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use the command <userinput>boot net</userinput> to boot from a TFTP and RARP server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server. Some older OpenBoot revisions require using the device name, such as <userinput>boot le()</userinput>; these probably don't support BOOTP nor DHCP."
 msgstr ""
 
-#: boot-installer.xml:2487
+#: boot-installer.xml:2474
 #, no-c-format
 #. Tag: para
 msgid "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command which is simply an alias to boot from the SCSI device on ID 6 (or the secondary master for IDE based systems). You may have to use the actual device name for older OpenBoot versions that don't support this special command. Note that some problems have been reported on Sun4m (e.g., Sparc 10s and Sparc 20s) systems booting from CD-ROM."
 msgstr ""
 
-#: boot-installer.xml:2502
+#: boot-installer.xml:2489
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1689,13 +1683,13 @@ msgid ""
       "</screen></informalexample> Be warned that the newer Sun4u (ultra) architecture does not support floppy booting. A typical error message is <computeroutput>Bad magic number in disk label - Can't open disk label package</computeroutput>. Furthermore, a number of Sun4c models (such as the IPX) do not support the compressed images found on the disks, so also are not supported."
 msgstr ""
 
-#: boot-installer.xml:2514
+#: boot-installer.xml:2501
 #, no-c-format
 #. Tag: para
 msgid "Several Sparcs (e.g. Ultra 10) have an OBP bug that prevents them from booting (instead of not supporting booting at all). The appropriate OBP update can be downloaded as product ID 106121 from <ulink url=\"http://sunsolve.sun.com\"></ulink>."
 msgstr ""
 
-#: boot-installer.xml:2521
+#: boot-installer.xml:2508
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1705,37 +1699,37 @@ msgid ""
       "</screen></informalexample> then it is possible that floppy booting is simply not supported on your machine."
 msgstr ""
 
-#: boot-installer.xml:2533
+#: boot-installer.xml:2520
 #, no-c-format
 #. Tag: title
 msgid "IDPROM Messages"
 msgstr ""
 
-#: boot-installer.xml:2534
+#: boot-installer.xml:2521
 #, no-c-format
 #. Tag: para
 msgid "If you cannot boot because you get messages about a problem with <quote>IDPROM</quote>, then it's possible that your NVRAM battery, which holds configuration information for you firmware, has run out. See the <ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink> for more information."
 msgstr ""
 
-#: boot-installer.xml:2553
+#: boot-installer.xml:2540
 #, no-c-format
 #. Tag: para
 msgid "Boot parameters are Linux kernel parameters which are generally used to make sure that peripherals are dealt with properly. For the most part, the kernel can auto-detect information about your peripherals. However, in some cases you'll have to help the kernel a bit."
 msgstr ""
 
-#: boot-installer.xml:2560
+#: boot-installer.xml:2547
 #, no-c-format
 #. Tag: para
 msgid "If this is the first time you're booting the system, try the default boot parameters (i.e., don't try setting parameters) and see if it works correctly. It probably will. If not, you can reboot later and look for any special parameters that inform the system about your hardware."
 msgstr ""
 
-#: boot-installer.xml:2567
+#: boot-installer.xml:2554
 #, no-c-format
 #. Tag: para
 msgid "Information on many boot parameters can be found in the <ulink url=\"http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, including tips for obscure hardware. This section contains only a sketch of the most salient parameters. Some common gotchas are included below in <xref linkend=\"boot-troubleshooting\"/>."
 msgstr ""
 
-#: boot-installer.xml:2576
+#: boot-installer.xml:2563
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1744,475 +1738,475 @@ msgid ""
       "</screen></informalexample> should be emitted early in the process. <replaceable>total</replaceable> should match the total amount of RAM, in kilobytes. If this doesn't match the actual amount of RAM you have installed, you need to use the <userinput>mem=<replaceable>ram</replaceable></userinput> parameter, where <replaceable>ram</replaceable> is set to the amount of memory, suffixed with <quote>k</quote> for kilobytes, or <quote>m</quote> for megabytes. For example, both <userinput>mem=65536k</userinput> and <userinput>mem=64m</userinput> mean 64MB of RAM."
 msgstr ""
 
-#: boot-installer.xml:2592
+#: boot-installer.xml:2579
 #, no-c-format
 #. Tag: para
 msgid "If you are booting with a serial console, generally the kernel will autodetect this<phrase arch=\"mipsel\"> (although not on DECstations)</phrase>. If you have a videocard (framebuffer) and a keyboard also attached to the computer which you wish to boot via serial console, you may have to pass the <userinput>console=<replaceable>device</replaceable></userinput> argument to the kernel, where <replaceable>device</replaceable> is your serial device, which is usually something like <filename>ttyS0</filename>."
 msgstr ""
 
-#: boot-installer.xml:2605
+#: boot-installer.xml:2592
 #, no-c-format
 #. Tag: para
 msgid "For &arch-title; the serial devices are <filename>ttya</filename> or <filename>ttyb</filename>. Alternatively, set the <envar>input-device</envar> and <envar>output-device</envar> OpenPROM variables to <filename>ttya</filename>."
 msgstr ""
 
-#: boot-installer.xml:2616
+#: boot-installer.xml:2603
 #, no-c-format
 #. Tag: title
 msgid "Debian Installer Parameters"
 msgstr ""
 
-#: boot-installer.xml:2617
+#: boot-installer.xml:2604
 #, no-c-format
 #. Tag: para
-msgid "The installation system recognizes a few additional boot parameters<footnote> <para> Note that the 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. <phrase condition=\"etch\">With kernel 2.6.9 or newer, you can use 32 command line options and 32 environment options.</phrase> </para> </footnote> which may be useful."
+msgid "The installation system recognizes a few additional boot parameters<footnote> <para> Note that the 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. With kernel 2.6.9 or newer, you can use 32 command line options and 32 environment options. </para> </footnote> which may be useful."
 msgstr ""
 
-#: boot-installer.xml:2638
+#: boot-installer.xml:2624
 #, no-c-format
 #. Tag: term
 msgid "debconf/priority"
 msgstr ""
 
-#: boot-installer.xml:2639
+#: boot-installer.xml:2625
 #, no-c-format
 #. Tag: para
 msgid "This parameter sets the lowest priority of messages to be displayed."
 msgstr ""
 
-#: boot-installer.xml:2643
+#: boot-installer.xml:2629
 #, no-c-format
 #. Tag: para
 msgid "The default installation uses <userinput>debconf/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 ""
 
-#: boot-installer.xml:2650
+#: boot-installer.xml:2636
 #, no-c-format
 #. Tag: para
 msgid "If you add <userinput>debconf/priority=medium</userinput> as boot parameter, you will be shown the installation menu and gain more control over the installation. When <userinput>debconf/priority=low</userinput> is used, all messages are shown (this is equivalent to the <emphasis>expert</emphasis> boot method). With <userinput>debconf/priority=critical</userinput>, the installation system will display only critical messages and try to do the right thing without fuss."
 msgstr ""
 
-#: boot-installer.xml:2664
+#: boot-installer.xml:2650
 #, no-c-format
 #. Tag: term
 msgid "DEBIAN_FRONTEND"
 msgstr ""
 
-#: boot-installer.xml:2665
+#: boot-installer.xml:2651
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: boot-installer.xml:2701
+#: boot-installer.xml:2687
 #, no-c-format
 #. Tag: term
 msgid "BOOT_DEBUG"
 msgstr ""
 
-#: boot-installer.xml:2702
+#: boot-installer.xml:2688
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: boot-installer.xml:2711
+#: boot-installer.xml:2697
 #, no-c-format
 #. Tag: userinput
 msgid "BOOT_DEBUG=0"
 msgstr ""
 
-#: boot-installer.xml:2712
+#: boot-installer.xml:2698
 #, no-c-format
 #. Tag: para
 msgid "This is the default."
 msgstr ""
 
-#: boot-installer.xml:2716
+#: boot-installer.xml:2702
 #, no-c-format
 #. Tag: userinput
 msgid "BOOT_DEBUG=1"
 msgstr ""
 
-#: boot-installer.xml:2717
+#: boot-installer.xml:2703
 #, no-c-format
 #. Tag: para
 msgid "More verbose than usual."
 msgstr ""
 
-#: boot-installer.xml:2721
+#: boot-installer.xml:2707
 #, no-c-format
 #. Tag: userinput
 msgid "BOOT_DEBUG=2"
 msgstr ""
 
-#: boot-installer.xml:2722
+#: boot-installer.xml:2708
 #, no-c-format
 #. Tag: para
 msgid "Lots of debugging information."
 msgstr ""
 
-#: boot-installer.xml:2726
+#: boot-installer.xml:2712
 #, no-c-format
 #. Tag: userinput
 msgid "BOOT_DEBUG=3"
 msgstr ""
 
-#: boot-installer.xml:2727
+#: boot-installer.xml:2713
 #, no-c-format
 #. Tag: para
 msgid "Shells are run at various points in the boot process to allow detailed debugging. Exit the shell to continue the boot."
 msgstr ""
 
-#: boot-installer.xml:2741
+#: boot-installer.xml:2727
 #, no-c-format
 #. Tag: term
 msgid "INSTALL_MEDIA_DEV"
 msgstr ""
 
-#: boot-installer.xml:2742
+#: boot-installer.xml:2728
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: boot-installer.xml:2748
+#: boot-installer.xml:2734
 #, no-c-format
 #. Tag: para
 msgid "The boot floppy, which normally scans all floppies and USB storage devices it can to find the root floppy, can be overridden by this parameter to only look at the one device."
 msgstr ""
 
-#: boot-installer.xml:2758
+#: boot-installer.xml:2744
 #, no-c-format
 #. Tag: term
 msgid "debian-installer/framebuffer"
 msgstr ""
 
-#: boot-installer.xml:2759
+#: boot-installer.xml:2745
 #, no-c-format
 #. Tag: para
 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>. Problem symptoms are error messages about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install."
 msgstr ""
 
-#: boot-installer.xml:2768
+#: boot-installer.xml:2754
 #, no-c-format
 #. Tag: para
 msgid "The <userinput>video=vga16:off</userinput> argument may also be used to disable the framebuffer. Such problems have been reported on a Dell Inspiron with Mobile Radeon card."
 msgstr ""
 
-#: boot-installer.xml:2774
+#: boot-installer.xml:2760
 #, no-c-format
 #. Tag: para
 msgid "Such problems have been reported on the Amiga 1200 and SE/30."
 msgstr ""
 
-#: boot-installer.xml:2778
+#: boot-installer.xml:2764
 #, no-c-format
 #. Tag: para
 msgid "Such problems have been reported on hppa."
 msgstr ""
 
-#: boot-installer.xml:2782
+#: boot-installer.xml:2768
 #, no-c-format
 #. Tag: para
 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>."
 msgstr ""
 
-#: boot-installer.xml:2795
+#: boot-installer.xml:2781
 #, no-c-format
 #. Tag: term
 msgid "debian-installer/probe/usb"
 msgstr ""
 
-#: boot-installer.xml:2796
+#: boot-installer.xml:2782
 #, no-c-format
 #. Tag: para
 msgid "Set to <userinput>false</userinput> to prevent probing for USB on boot, if that causes problems."
 msgstr ""
 
-#: boot-installer.xml:2805
+#: boot-installer.xml:2791
 #, no-c-format
 #. Tag: term
 msgid "netcfg/disable_dhcp"
 msgstr ""
 
-#: boot-installer.xml:2806
+#: boot-installer.xml:2792
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: boot-installer.xml:2813
+#: boot-installer.xml:2799
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: boot-installer.xml:2824
+#: boot-installer.xml:2810
 #, no-c-format
 #. Tag: term
 msgid "hw-detect/start_pcmcia"
 msgstr ""
 
-#: boot-installer.xml:2825
+#: boot-installer.xml:2811
 #, no-c-format
 #. Tag: para
 msgid "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if that causes problems. Some laptops are well known for this misbehavior."
 msgstr ""
 
-#: boot-installer.xml:2835
+#: boot-installer.xml:2821
 #, no-c-format
 #. Tag: term
 msgid "preseed/url"
 msgstr ""
 
-#: boot-installer.xml:2836
+#: boot-installer.xml:2822
 #, no-c-format
 #. Tag: para
 msgid "Specify the url to a preconfiguration file to download and use in automating the install. See <xref linkend=\"automatic-install\"/>."
 msgstr ""
 
-#: boot-installer.xml:2845
+#: boot-installer.xml:2831
 #, no-c-format
 #. Tag: term
 msgid "preseed/file"
 msgstr ""
 
-#: boot-installer.xml:2846
+#: boot-installer.xml:2832
 #, no-c-format
 #. Tag: para
 msgid "Specify the path to a preconfiguration file to load to automating the install. See <xref linkend=\"automatic-install\"/>."
 msgstr ""
 
-#: boot-installer.xml:2855
+#: boot-installer.xml:2841
 #, no-c-format
 #. Tag: term
 msgid "cdrom-detect/eject"
 msgstr ""
 
-#: boot-installer.xml:2856
+#: boot-installer.xml:2842
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: boot-installer.xml:2865
+#: boot-installer.xml:2851
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: boot-installer.xml:2876
+#: boot-installer.xml:2862
 #, no-c-format
 #. Tag: term
 msgid "ramdisk_size"
 msgstr ""
 
-#: boot-installer.xml:2877
+#: boot-installer.xml:2863
 #, no-c-format
 #. Tag: para
 msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;."
 msgstr ""
 
-#: boot-installer.xml:2885
+#: boot-installer.xml:2871
 #, no-c-format
 #. Tag: term
 msgid "rescue/enable"
 msgstr ""
 
-#: boot-installer.xml:2886
+#: boot-installer.xml:2872
 #, no-c-format
 #. Tag: para
 msgid "Set to <userinput>true</userinput> to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>."
 msgstr ""
 
-#: boot-installer.xml:2904
+#: boot-installer.xml:2890
 #, no-c-format
 #. Tag: title
 msgid "Troubleshooting the Installation Process"
 msgstr ""
 
-#: boot-installer.xml:2909
+#: boot-installer.xml:2895
 #, no-c-format
 #. Tag: title
 msgid "Floppy Disk Reliability"
 msgstr ""
 
-#: boot-installer.xml:2911
+#: boot-installer.xml:2897
 #, no-c-format
 #. Tag: para
 msgid "The biggest problem for people using floppy disks to install Debian seems to be floppy disk reliability."
 msgstr ""
 
-#: boot-installer.xml:2916
+#: boot-installer.xml:2902
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: boot-installer.xml:2925
+#: boot-installer.xml:2911
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: boot-installer.xml:2935
+#: boot-installer.xml:2921
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: boot-installer.xml:2941
+#: boot-installer.xml:2927
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: boot-installer.xml:2950
+#: boot-installer.xml:2936
 #, no-c-format
 #. Tag: title
 msgid "Boot Configuration"
 msgstr ""
 
-#: boot-installer.xml:2952
+#: boot-installer.xml:2938
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: boot-installer.xml:2959
+#: boot-installer.xml:2945
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: boot-installer.xml:2966
+#: boot-installer.xml:2952
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: boot-installer.xml:2972
+#: boot-installer.xml:2958
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: boot-installer.xml:2983
+#: boot-installer.xml:2969
 #, no-c-format
 #. Tag: title
 msgid "Common &arch-title; Installation Problems"
 msgstr ""
 
-#: boot-installer.xml:2984
+#: boot-installer.xml:2970
 #, no-c-format
 #. Tag: para
 msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer."
 msgstr ""
 
-#: boot-installer.xml:2989
+#: boot-installer.xml:2975
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: boot-installer.xml:2995
+#: boot-installer.xml:2981
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: boot-installer.xml:3004
+#: boot-installer.xml:2990
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: boot-installer.xml:3011
+#: boot-installer.xml:2997
 #, no-c-format
 #. Tag: para
 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>debian-installer/framebuffer=false</userinput> or <userinput>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 ""
 
-#: boot-installer.xml:3026
+#: boot-installer.xml:3012
 #, no-c-format
 #. Tag: title
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr ""
 
-#: boot-installer.xml:3027
+#: boot-installer.xml:3013
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: boot-installer.xml:3037
+#: boot-installer.xml:3023
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: boot-installer.xml:3054
+#: boot-installer.xml:3040
 #, no-c-format
 #. Tag: title
 msgid "System Freeze while Loading the USB Modules"
 msgstr ""
 
-#: boot-installer.xml:3055
+#: boot-installer.xml:3041
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: boot-installer.xml:3069
+#: boot-installer.xml:3055
 #, no-c-format
 #. Tag: title
 msgid "Interpreting the Kernel Startup Messages"
 msgstr ""
 
-#: boot-installer.xml:3071
+#: boot-installer.xml:3057
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: boot-installer.xml:3096
+#: boot-installer.xml:3082
 #, no-c-format
 #. Tag: title
 msgid "Bug Reporter"
 msgstr ""
 
-#: boot-installer.xml:3097
+#: boot-installer.xml:3083
 #, no-c-format
 #. Tag: para
-msgid "If you get through the initial boot phase but cannot complete the install, the bug reporter menu choice may be helpful. <phrase condition=\"sarge\"> It copies system error logs and configuration information to a user-supplied floppy. </phrase> <phrase condition=\"etch\"> It lets you store system error logs and configuration information from the installer to a floppy, or download them in a web browser. </phrase> 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."
+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 ""
 
-#: boot-installer.xml:3114
+#: boot-installer.xml:3094
 #, no-c-format
 #. Tag: para
-msgid "Other pertinent installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/debian-installer/</filename> after the computer has been booted into the installed system."
+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 ""
 
-#: boot-installer.xml:3125
+#: boot-installer.xml:3105
 #, no-c-format
 #. Tag: title
 msgid "Submitting Installation Reports"
 msgstr ""
 
-#: boot-installer.xml:3126
+#: boot-installer.xml:3106
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: boot-installer.xml:3133
+#: boot-installer.xml:3113
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: boot-installer.xml:3140
+#: boot-installer.xml:3120
 #, no-c-format
 #. Tag: para
 msgid ""
diff --git a/po/pot/boot-new.pot b/po/pot/boot-new.pot
index e3af5957d..7fdb5b033 100644
--- a/po/pot/boot-new.pot
+++ b/po/pot/boot-new.pot
@@ -6,7 +6,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2005-12-03 10:28+0000\n"
+"POT-Creation-Date: 2006-01-03 19:55+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"
@@ -35,604 +35,178 @@ msgstr ""
 #: boot-new.xml:13
 #, no-c-format
 #. Tag: para
-msgid "If you are booting directly into Debian, and the system doesn't start up, either use your original installation boot media, or insert the custom boot floppy if you have one, and reset your system. This way, you will probably need to add some boot arguments like <userinput>root=<replaceable>root</replaceable></userinput>, where <replaceable>root</replaceable> is your root partition, such as <filename>/dev/sda1</filename>. <phrase condition=\"etch\"> Alternatively, see <xref linkend=\"rescue\"/> for instructions on using the installer's built-in rescue mode. </phrase>"
+msgid "If you are booting directly into Debian, and the system doesn't start up, either use your original installation boot media, or insert the custom boot floppy if you have one, and reset your system. This way, you will probably need to add some boot arguments like <userinput>root=<replaceable>root</replaceable></userinput>, where <replaceable>root</replaceable> is your root partition, such as <filename>/dev/sda1</filename>. Alternatively, see <xref linkend=\"rescue\"/> for instructions on using the installer's built-in rescue mode."
 msgstr ""
 
-#: boot-new.xml:29
+#: boot-new.xml:27
 #, no-c-format
 #. Tag: title
 msgid "BVME 6000 Booting"
 msgstr ""
 
-#: boot-new.xml:30
+#: boot-new.xml:28
 #, no-c-format
 #. Tag: para
 msgid "If you have just performed a diskless install on a BVM or Motorola VMEbus machine: once the system has loaded the <command>tftplilo</command> program from the TFTP server, from the <prompt>LILO Boot:</prompt> prompt enter one of:"
 msgstr ""
 
-#: boot-new.xml:38
+#: boot-new.xml:36
 #, no-c-format
 #. Tag: para
 msgid "<userinput>b6000</userinput> followed by &enterkey; to boot a BVME 4000/6000"
 msgstr ""
 
-#: boot-new.xml:43
+#: boot-new.xml:41
 #, no-c-format
 #. Tag: para
 msgid "<userinput>b162</userinput> followed by &enterkey; to boot an MVME162"
 msgstr ""
 
-#: boot-new.xml:48
+#: boot-new.xml:46
 #, no-c-format
 #. Tag: para
 msgid "<userinput>b167</userinput> followed by &enterkey; to boot an MVME166/167"
 msgstr ""
 
-#: boot-new.xml:60
+#: boot-new.xml:58
 #, no-c-format
 #. Tag: title
 msgid "Macintosh Booting"
 msgstr ""
 
-#: boot-new.xml:62
+#: boot-new.xml:60
 #, no-c-format
 #. Tag: para
 msgid "Go to the directory containing the installation files and start up the <command>Penguin</command> booter, holding down the <keycap>command</keycap> key. Go to the <userinput>Settings</userinput> dialogue (<keycombo> <keycap>command</keycap> <keycap>T</keycap> </keycombo>), and locate the kernel options line which should look like <userinput>root=/dev/ram video=font:VGA8x16</userinput> or similar."
 msgstr ""
 
-#: boot-new.xml:72
+#: boot-new.xml:70
 #, no-c-format
 #. Tag: para
 msgid "You need to change the entry to <userinput>root=/dev/<replaceable>yyyy</replaceable></userinput>. Replace the <replaceable>yyyy</replaceable> with the Linux name of the partition onto which you installed the system (e.g. <filename>/dev/sda1</filename>); you wrote this down earlier. The <userinput>video=font:VGA8x8</userinput> is recommended especially for users with tiny screens. The kernel would pick a prettier (6x11) font but the console driver for this font can hang the machine, so using 8x16 or 8x8 is safer at this stage. You can change this at any time."
 msgstr ""
 
-#: boot-new.xml:85
+#: boot-new.xml:83
 #, no-c-format
 #. Tag: para
 msgid "If you don't want to start GNU/Linux immediately each time you start, uncheck the <userinput>Auto Boot</userinput> option. Save your settings in the <filename>Prefs</filename> file using the <userinput>Save Settings As Default</userinput> option."
 msgstr ""
 
-#: boot-new.xml:92
+#: boot-new.xml:90
 #, no-c-format
 #. Tag: para
 msgid "Now select <userinput>Boot Now</userinput> (<keycombo> <keycap>command</keycap> <keycap>B</keycap> </keycombo>) to start your freshly installed GNU/Linux instead of the RAMdisk installer system."
 msgstr ""
 
-#: boot-new.xml:98
+#: boot-new.xml:96
 #, no-c-format
 #. Tag: para
 msgid "Debian should boot, and you should see the same messages as when you first booted the installation system, followed by some new messages."
 msgstr ""
 
-#: boot-new.xml:108
+#: boot-new.xml:106
 #, no-c-format
 #. Tag: title
 msgid "OldWorld PowerMacs"
 msgstr ""
 
-#: boot-new.xml:109
+#: boot-new.xml:107
 #, no-c-format
 #. Tag: para
 msgid "If the machine fails to boot after completing the installation, and stops with a <prompt>boot:</prompt> prompt, try typing <userinput>Linux</userinput> followed by &enterkey;. (The default boot configuration in <filename>quik.conf</filename> is labeled Linux). The labels defined in <filename>quik.conf</filename> will be displayed if you press the <keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt. You can also try booting back into the installer, and editing the <filename>/target/etc/quik.conf</filename> placed there by the <guimenuitem>Install Quik on a Hard Disk</guimenuitem> step. Clues for dealing with <command>quik</command> are available at <ulink url=\"&url-powerpc-quik-faq;\"></ulink>."
 msgstr ""
 
-#: boot-new.xml:123
+#: boot-new.xml:121
 #, no-c-format
 #. Tag: para
 msgid "To boot back into MacOS without resetting the nvram, type <userinput>bye</userinput> at the OpenFirmware prompt (assuming MacOS has not been removed from the machine). To obtain an OpenFirmware prompt, hold down the <keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>o</keycap> <keycap>f</keycap> </keycombo> keys while cold booting the machine. If you need to reset the OpenFirmware nvram changes to the MacOS default in order to boot back to MacOS, hold down the <keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </keycombo> keys while cold booting the machine."
 msgstr ""
 
-#: boot-new.xml:136
+#: boot-new.xml:134
 #, no-c-format
 #. Tag: para
 msgid "If you use <command>BootX</command> to boot into the installed system, just select your desired kernel in the <filename>Linux Kernels</filename> folder, un-choose the ramdisk option, and add a root device corresponding to your installation; e.g. <userinput>/dev/hda8</userinput>."
 msgstr ""
 
-#: boot-new.xml:148
+#: boot-new.xml:146
 #, no-c-format
 #. Tag: title
 msgid "NewWorld PowerMacs"
 msgstr ""
 
-#: boot-new.xml:149
+#: boot-new.xml:147
 #, no-c-format
 #. Tag: para
 msgid "On G4 machines and iBooks, you can hold down the <keycap>option</keycap> key and get a graphical screen with a button for each bootable OS, &debian; will be a button with a small penguin icon."
 msgstr ""
 
-#: boot-new.xml:156
+#: boot-new.xml:154
 #, no-c-format
 #. Tag: para
 msgid "If you kept MacOS and at some point it changes the OpenFirmware <envar>boot-device</envar> variable you should reset OpenFirmware to its default configuration. To do this hold down the <keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </keycombo> keys while cold booting the machine."
 msgstr ""
 
-#: boot-new.xml:164
+#: boot-new.xml:162
 #, no-c-format
 #. Tag: para
 msgid "The labels defined in <filename>yaboot.conf</filename> will be displayed if you press the <keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt."
 msgstr ""
 
-#: boot-new.xml:170
+#: boot-new.xml:168
 #, no-c-format
 #. Tag: para
 msgid "Resetting OpenFirmware on G3 or G4 hardware will cause it to boot &debian; by default (if you correctly partitioned and placed the Apple_Bootstrap partition first). If you have &debian; on a SCSI disk and MacOS on an IDE disk this may not work and you will have to enter OpenFirmware and set the <envar>boot-device</envar> variable, <command>ybin</command> normally does this automatically."
 msgstr ""
 
-#: boot-new.xml:179
+#: boot-new.xml:177
 #, no-c-format
 #. Tag: para
 msgid "After you boot &debian; for the first time you can add any additional options you desire (such as dual boot options) to <filename>/etc/yaboot.conf</filename> and run <command>ybin</command> to update your boot partition with the changed configuration. Please read the <ulink url=\"&url-powerpc-yaboot-faq;\">yaboot HOWTO</ulink> for more information."
 msgstr ""
 
-#: boot-new.xml:193
-#, no-c-format
-#. Tag: title
-msgid "Debian Post-Boot (Base) Configuration"
-msgstr ""
-
-#: boot-new.xml:195
-#, no-c-format
-#. Tag: para
-msgid "After booting, you will be prompted to complete the configuration of your basic system, and then to select what additional packages you wish to install. The application which guides you through this process is called <classname>base-config</classname>. Its concept is very similar to the &d-i; from the first stage. Indeed, <classname>base-config</classname> consists of a number of specialized components, where each component handles one configuration task, contains <quote>hidden menu in the background</quote> and also uses the same navigation system."
-msgstr ""
-
-#: boot-new.xml:207
-#, no-c-format
-#. Tag: para
-msgid "If you wish to re-run the <classname>base-config</classname> at any point after installation is complete, as root run <userinput>base-config</userinput>."
-msgstr ""
-
-#: boot-new.xml:220
-#, no-c-format
-#. Tag: title
-msgid "Configuring Your Time Zone"
-msgstr ""
-
-#: boot-new.xml:222
-#, no-c-format
-#. Tag: para
-msgid "After a welcome screen, you will be prompted to configure your time zone. First select whether the hardware clock of your system is set to local time or Greenwich Mean Time (GMT or UTC). The time displayed in the dialog may help you decide on the correct option. <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=\"i386\">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 ""
-
-#: boot-new.xml:235
-#, no-c-format
-#. Tag: para
-msgid "Depending on the location selected at the beginning of the installation process, you will next be shown either a single timezone or a list of timezones relevant for that location. If a single timezone is shown, choose <guibutton>Yes</guibutton> to confirm or choose <guibutton>No</guibutton> to select from the full list of timezones. If a list is shown, select your timezone from the list, or select Other for the full list."
-msgstr ""
-
-#: boot-new.xml:252
-#, no-c-format
-#. Tag: title
-msgid "Setting Up Users And Passwords"
-msgstr ""
-
-#: boot-new.xml:255
-#, no-c-format
-#. Tag: title
-msgid "Set the Root Password"
-msgstr ""
-
-#: boot-new.xml:257
-#, no-c-format
-#. Tag: para
-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 ""
-
-#: boot-new.xml:265
-#, no-c-format
-#. Tag: para
-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 ""
-
-#: boot-new.xml:273
-#, no-c-format
-#. Tag: para
-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 ""
-
-#: boot-new.xml:283
-#, no-c-format
-#. Tag: title
-msgid "Create an Ordinary User"
-msgstr ""
-
-#: boot-new.xml:285
-#, no-c-format
-#. Tag: para
-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 ""
-
-#: boot-new.xml:292
-#, no-c-format
-#. Tag: para
-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 ""
-
-#: boot-new.xml:302
-#, no-c-format
-#. Tag: para
-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 ""
-
-#: boot-new.xml:309
-#, no-c-format
-#. Tag: para
-msgid "If at any point after installation you would like to create another account, use the <command>adduser</command> command."
-msgstr ""
-
-#: boot-new.xml:323
-#, no-c-format
-#. Tag: title
-msgid "Setting Up PPP"
-msgstr ""
-
-#: boot-new.xml:325
-#, no-c-format
-#. Tag: para
-msgid "If no network was configured during the first stage of the installation, you will next be asked whether you wish to install the rest of the system using PPP. PPP is a protocol used to establish dialup connections with modems. If you configure the modem at this point, the installation system will be able to download additional packages or security updates from the Internet during the next steps of the installation. If you don't have a modem in your computer or if you prefer to configure your modem after the installation, you can skip this step."
-msgstr ""
-
-#: boot-new.xml:336
-#, no-c-format
-#. Tag: para
-msgid "In order to configure your PPP connection, you will need some information from your Internet Service Provider (ISP), including phone number, username, password and DNS servers (optional). Some ISPs provide installation guidelines for Linux distributions. You can use that information even if they don't specifically target Debian since most of the configuration parameters (and software) is similar amongst Linux distributions."
-msgstr ""
-
-#: boot-new.xml:345
-#, no-c-format
-#. Tag: para
-msgid "If you do choose to configure PPP at this point, a program named <command>pppconfig</command> will be run. This program helps you configure your PPP connection. <emphasis>Make sure, when it asks you for the name of your dialup connection, that you name it <userinput>provider</userinput>.</emphasis>"
-msgstr ""
-
-#: boot-new.xml:353
-#, no-c-format
-#. Tag: para
-msgid "Hopefully, the <command>pppconfig</command> program will walk you through a trouble-free PPP connection setup. However, if it does not work for you, see below for detailed instructions."
-msgstr ""
-
-#: boot-new.xml:359
-#, no-c-format
-#. Tag: para
-msgid "In order to setup PPP, you'll need to know the basics of file viewing and editing in GNU/Linux. To view files, you should use <command>more</command>, and <command>zmore</command> for compressed files with a <userinput>.gz</userinput> extension. For example, to view <filename>README.debian.gz</filename>, type <userinput>zmore README.debian.gz</userinput>. The base system comes with an editor named <command>nano</command>, which is very simple to use, but does not have a lot of features. You will probably want to install more full-featured editors and viewers later, such as <command>jed</command>, <command>nvi</command>, <command>less</command>, and <command>emacs</command>."
-msgstr ""
-
-#: boot-new.xml:373
-#, no-c-format
-#. Tag: para
-msgid "Edit <filename>/etc/ppp/peers/provider</filename> and replace <userinput>/dev/modem</userinput> with <userinput>/dev/ttyS<replaceable>&num;</replaceable></userinput> where <replaceable>&num;</replaceable> stands for the number of your serial port. In Linux, serial ports are counted from 0; your first serial port <phrase arch=\"i386\">(i.e., <userinput>COM1</userinput>)</phrase> is <filename>/dev/ttyS0</filename> under Linux. <phrase arch=\"powerpc;m68k\">On Macintoshes with serial ports, the modem port is <filename>/dev/ttyS0</filename> and the printer port is <filename>/dev/ttyS1</filename>.</phrase> The next step is to edit <filename>/etc/chatscripts/provider</filename> and insert your provider's phone number, your user-name and password. Please do not delete the <quote>\\q</quote> that precedes the password. It hides the password from appearing in your log files."
-msgstr ""
-
-#: boot-new.xml:393
-#, no-c-format
-#. Tag: para
-msgid "Many providers use PAP or CHAP for login sequence instead of text mode authentication. Others use both. If your provider requires PAP or CHAP, you'll need to follow a different procedure. Comment out everything below the dialing string (the one that starts with <quote>ATDT</quote>) in <filename>/etc/chatscripts/provider</filename>, modify <filename>/etc/ppp/peers/provider</filename> as described above, and add <userinput>user <replaceable>name</replaceable></userinput> where <replaceable>name</replaceable> stands for your user-name for the provider you are trying to connect to. Next, edit <filename>/etc/ppp/pap-secrets</filename> or <filename>/etc/ppp/chap-secrets</filename> and enter your password there."
-msgstr ""
-
-#: boot-new.xml:409
-#, no-c-format
-#. Tag: para
-msgid "You will also need to edit <filename>/etc/resolv.conf</filename> and add your provider's name server (DNS) IP addresses. The lines in <filename>/etc/resolv.conf</filename> are in the following format: <userinput>nameserver <replaceable>xxx.xxx.xxx.xxx</replaceable></userinput> where the <replaceable>x</replaceable>s stand for numbers in your IP address. Optionally, you could add the <userinput>usepeerdns</userinput> option to the <filename>/etc/ppp/peers/provider</filename> file, which will enable automatic choosing of appropriate DNS servers, using settings the remote host usually provides."
-msgstr ""
-
-#: boot-new.xml:423
-#, no-c-format
-#. Tag: para
-msgid "Unless your provider has a login sequence different from the majority of ISPs, you are done! Start the PPP connection by typing <command>pon</command> as root, and monitor the process using <command>plog</command> command. To disconnect, use <command>poff</command>, again, as root."
-msgstr ""
-
-#: boot-new.xml:431
-#, no-c-format
-#. Tag: para
-msgid "Read <filename>/usr/share/doc/ppp/README.Debian.gz</filename> file for more information on using PPP on Debian."
-msgstr ""
-
-#: boot-new.xml:436
-#, no-c-format
-#. Tag: para
-msgid "For static SLIP connections, you will need to add the <userinput>slattach</userinput> command (from the <classname>net-tools</classname> package) into <filename>/etc/init.d/network</filename>. Dynamic SLIP will require the <classname>gnudip</classname> package."
-msgstr ""
-
-#: boot-new.xml:447
-#, no-c-format
-#. Tag: title
-msgid "Setting Up PPP over Ethernet (PPPOE)"
-msgstr ""
-
-#: boot-new.xml:449
-#, no-c-format
-#. Tag: para
-msgid "PPPOE is a protocol related to PPP used for some broadband connections. There is currently no support in base configuration to help you set this up. However, the necessary software has been installed, which means you can configure PPPOE manually at this stage of the installation by switching to VT2 and running <command>pppoeconf</command>."
-msgstr ""
-
-#: boot-new.xml:467
-#, no-c-format
-#. Tag: title
-msgid "Configuring APT"
-msgstr ""
-
-#: boot-new.xml:469
-#, no-c-format
-#. Tag: para
-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 package 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>, <command>synaptic</command> and the older <command>dselect</command> also 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 ""
-
-#: boot-new.xml:493
-#, no-c-format
-#. Tag: para
-msgid "APT must be configured so that it knows where to retrieve packages from. The helper application which assists in this task is called <command>apt-setup</command>."
-msgstr ""
-
-#: boot-new.xml:499
-#, no-c-format
-#. Tag: para
-msgid "The next step in your configuration process is to tell APT where other Debian packages can be found. Note that you can re-run this tool at any point after installation by running <command>apt-setup</command>, or by manually editing <filename>/etc/apt/sources.list</filename>."
-msgstr ""
-
-#: boot-new.xml:506
-#, no-c-format
-#. Tag: para
-msgid "If an official CD-ROM is in the drive at this point, then that CD-ROM should automatically be configured as an apt source without prompting. You will notice this because you will see the CD-ROM being scanned."
-msgstr ""
-
-#: boot-new.xml:512
-#, no-c-format
-#. Tag: para
-msgid "For users without an official CD-ROM, you will be offered an array of choices for how Debian packages are accessed: FTP, HTTP, CD-ROM, or a local file system."
-msgstr ""
-
-#: boot-new.xml:518
-#, no-c-format
-#. Tag: para
-msgid "You should know that it's perfectly acceptable to have a number of different APT sources, even for the same Debian archive. <command>apt-get</command> will automatically pick the package with the highest version number given all the available versions. Or, for instance, if you have both an HTTP and a CD-ROM APT source, <command>apt-get</command> should automatically use the local CD-ROM when possible, and only resort to HTTP if a newer version is available there. However, it is not a good idea to add unnecessary APT sources, since this will tend to slow down the process of checking the network archives for new versions."
-msgstr ""
-
-#: boot-new.xml:534
-#, no-c-format
-#. Tag: title
-msgid "Configuring Network Package Sources"
-msgstr ""
-
-#: boot-new.xml:536
-#, no-c-format
-#. Tag: para
-msgid "If you plan on installing the rest of your system via the network, the most common option is to select the <userinput>http</userinput> source. The <userinput>ftp</userinput> source is also acceptable, but tends to be somewhat slower making connections."
-msgstr ""
-
-#: boot-new.xml:543
-#, no-c-format
-#. Tag: para
-msgid "The next step during the configuration of network package sources is to tell <command>apt-setup</command> which country you live in. This configures which of the official Debian Internet mirrors you will connect to. Depending on which country you select, you will be presented with a list of possible servers. It's generally fine to pick the one at the top of the list, but any of them should work. Note however that the mirror list provided by the installation was generated when this version of Debian was released and some mirrors may no longer be available."
-msgstr ""
-
-#: boot-new.xml:554
-#, no-c-format
-#. Tag: para
-msgid "After you have selected a mirror, you will be asked if a proxy server should be used. A proxy server is a server that will forward all your HTTP and/or FTP requests to the Internet and is most often used to regulate and optimize access to the Internet on corporate networks. In some networks only the proxy server is allowed access to the Internet, in which case you will have to enter the name of the proxy server. You may also have to include an user name and password. Most home users will not need to specify a proxy server, although some ISPs may provide proxy servers for their users."
-msgstr ""
-
-#: boot-new.xml:566
-#, no-c-format
-#. Tag: para
-msgid "After you select a mirror, your new network package source will be tested. If all goes well, you will be prompted whether you want to add another package source. If you have any problems using the package source you selected, try using a different mirror (either from your country list or from the global list), or try using a different network package source."
-msgstr ""
-
-#: boot-new.xml:583
-#, no-c-format
-#. Tag: title
-msgid "Package Installation"
-msgstr ""
-
-#: boot-new.xml:585
-#, no-c-format
-#. Tag: para
-msgid "Next you will be offered a number of pre-rolled software configurations offered by Debian. You could always choose, package by package, what you want to install on your new machine. This is the purpose of the <command>aptitude</command> program, described below. But this can be a long task with around &num-of-distrib-pkgs; packages available in Debian!"
-msgstr ""
-
-#: boot-new.xml:594
-#, no-c-format
-#. Tag: para
-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, <command>base-config</command> is merely invoking the <command>tasksel</command> program. For manual package selection, the <command>aptitude</command> program is being run. Any of these can be run at any time after installation to install (or remove) more packages. 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 ""
-
-#: boot-new.xml:621
-#, no-c-format
-#. Tag: para
-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 ""
-
-#: boot-new.xml:628
-#, no-c-format
-#. Tag: para
-msgid "Even if you did not select any tasks at all, any standard, important, or required priority packages that are not yet present on your system will be installed. This functionality is the same as running <userinput>tasksel -ris</userinput> at the command line, and currently involves a download of about 37M of archives. You will be shown the number of packages to be installed, and how many kilobytes of packages, if any, need to be downloaded."
-msgstr ""
-
-#: boot-new.xml:641
-#, no-c-format
-#. Tag: para
-msgid "If you do want to choose what to install on a package by package basis, select the <quote>manual package selection</quote> option in <command>tasksel</command>. If you select one or more tasks alongside this option, <command>aptitude</command> will be called with the <command>--visual-preview</command> option. This means you will be able to review<footnote> <para> You can also change the default selections. If you would like to select any additional package, use <menuchoice> <guimenu>View</guimenu> <guimenuitem>New Package View</guimenuitem> </menuchoice>. </para> </footnote> the packages that are to be installed. If you do not select any tasks, the normal <command>aptitude</command> screen will be displayed. After making your selections you should press <quote><userinput>g</userinput></quote> to start the download and installation of packages."
-msgstr ""
-
-#: boot-new.xml:662
-#, no-c-format
-#. Tag: para
-msgid "If you choose <quote>manual package selection</quote> <emphasis>without</emphasis> selecting any tasks, no packages will be installed by default. This means you can use this option if you want to install a minimal system, but also that the responsibility for selecting any packages not installed as part of the base system (before the reboot) that might be required for your system lies with you."
-msgstr ""
-
-#: boot-new.xml:673
-#, no-c-format
-#. Tag: para
-msgid "Of the &num-of-distrib-pkgs; packages available in Debian, only a small minority are covered by tasks offered in the Task Installer. To see information on more packages, either use <userinput>apt-cache search <replaceable>search-string</replaceable></userinput> for some given search string (see the <citerefentry> <refentrytitle>apt-cache</refentrytitle> <manvolnum>8</manvolnum> </citerefentry> man page), or run <command>aptitude</command> as described below."
-msgstr ""
-
-#: boot-new.xml:687
-#, no-c-format
-#. Tag: title
-msgid "Advanced Package Selection with <command>aptitude</command>"
-msgstr ""
-
-#: boot-new.xml:689
-#, no-c-format
-#. Tag: para
-msgid "<command>Aptitude</command> is a modern program for managing packages. <command>aptitude</command> allows you to select individual packages, set of packages matching given criteria (for advanced users), or whole tasks."
-msgstr ""
-
-#: boot-new.xml:696
-#, no-c-format
-#. Tag: para
-msgid "The most basic keybindings are: <informaltable> <tgroup cols=\"2\"> <thead> <row> <entry>Key</entry><entry>Action</entry> </row> </thead> <tbody> <row> <entry><keycap>Up</keycap>, <keycap>Down</keycap></entry> <entry>Move selection up or down.</entry> </row><row> <entry>&enterkey;</entry> <entry>Open/collapse/activate item.</entry> </row><row> <entry><keycap>+</keycap></entry> <entry>Mark package for installation.</entry> </row><row> <entry><keycap>-</keycap></entry> <entry>Mark package for removal.</entry> </row><row> <entry><keycap>d</keycap></entry> <entry>Show package dependencies.</entry> </row><row> <entry><keycap>g</keycap></entry> <entry>Actually download/install/remove packages.</entry> </row><row> <entry><keycap>q</keycap></entry> <entry>Quit current view.</entry> </row><row> <entry><keycap>F10</keycap></entry> <entry>Activate menu.</entry> </row> </tbody></tgroup></informaltable> For more commands see the online help under the <keycap>?</keycap> key."
-msgstr ""
-
-#: boot-new.xml:747
-#, no-c-format
-#. Tag: title
-msgid "Prompts During Software Installation"
-msgstr ""
-
-#: boot-new.xml:749
-#, no-c-format
-#. Tag: para
-msgid "Each package you selected with <command>tasksel</command> or <command>aptitude</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. You might also want to keep an eye on the output during the process, to watch for any installation errors (although you will be asked to acknowledge errors which prevented a package's installation)."
-msgstr ""
-
-#: boot-new.xml:764
-#, no-c-format
-#. Tag: title
-msgid "Settings for the X Server"
-msgstr ""
-
-#: boot-new.xml:766
-#, no-c-format
-#. Tag: para
-msgid "On iMacs, and some older Macintoshes as well, the X Server software doesn't calculate appropriate video settings. You will need to choose the <guimenuitem>Advanced</guimenuitem> option during configuration of the video settings. For the monitor's horizontal sync range, enter 59&ndash;63. You can leave the default for vertical refresh range."
-msgstr ""
-
-#: boot-new.xml:774
-#, no-c-format
-#. Tag: para
-msgid "The mouse device should be set to <userinput>/dev/input/mice</userinput>."
-msgstr ""
-
-#: boot-new.xml:788
-#, no-c-format
-#. Tag: title
-msgid "Configuring Your Mail Transport Agent"
-msgstr ""
-
-#: boot-new.xml:790
-#, no-c-format
-#. Tag: para
-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 ""
-
-#: boot-new.xml:798
-#, no-c-format
-#. Tag: para
-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 ""
-
-#: boot-new.xml:806
-#, no-c-format
-#. Tag: para
-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 ""
-
-#: boot-new.xml:815
-#, no-c-format
-#. Tag: term
-msgid "internet site"
-msgstr ""
-
-#: boot-new.xml:816
-#, no-c-format
-#. Tag: para
-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 ""
-
-#: boot-new.xml:827
-#, no-c-format
-#. Tag: term
-msgid "mail sent by smarthost"
-msgstr ""
-
-#: boot-new.xml:828
-#, no-c-format
-#. Tag: para
-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 ""
-
-#: boot-new.xml:841
-#, no-c-format
-#. Tag: term
-msgid "local delivery only"
-msgstr ""
-
-#: boot-new.xml:842
-#, no-c-format
-#. Tag: para
-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 ""
-
-#: boot-new.xml:855
-#, no-c-format
-#. Tag: term
-msgid "no configuration at this time"
-msgstr ""
-
-#: boot-new.xml:856
-#, no-c-format
-#. Tag: para
-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 ""
-
-#: boot-new.xml:867
-#, no-c-format
-#. Tag: para
-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 ""
-
-#: boot-new.xml:882
+#: boot-new.xml:191
 #, no-c-format
 #. Tag: title
 msgid "Log In"
 msgstr ""
 
-#: boot-new.xml:884
+#: boot-new.xml:193
 #, no-c-format
 #. Tag: para
-msgid "After you've installed packages, you'll be presented with the login prompt. Log in using the personal login and password you selected. Your system is now ready to use."
+msgid "Once your system boots, you'll be presented with the login prompt. Log in using the personal login and password you selected during the installation process. Your system is now ready to use."
 msgstr ""
 
-#: boot-new.xml:890
+#: boot-new.xml:199
 #, no-c-format
 #. Tag: para
 msgid "If you are a new user, you may want to explore the documentation which is already installed on your system as you start to use it. There are currently several documentation systems, work is proceeding on integrating the different types of documentation. Here are a few starting points."
 msgstr ""
 
-#: boot-new.xml:898
+#: boot-new.xml:207
 #, no-c-format
 #. Tag: para
 msgid "Documentation accompanying programs you have installed is in <filename>/usr/share/doc/</filename>, under a subdirectory named after the program. For example, the APT User's Guide for using <command>apt</command> to install other programs on your system, is located in <filename>/usr/share/doc/apt/guide.html/index.html</filename>."
 msgstr ""
 
-#: boot-new.xml:907
+#: boot-new.xml:216
 #, no-c-format
 #. Tag: para
 msgid "In addition, there are some special folders within the <filename>/usr/share/doc/</filename> hierarchy. Linux HOWTOs are installed in <emphasis>.gz</emphasis> format, in <filename>/usr/share/doc/HOWTO/en-txt/</filename>. After installing <command>dhelp</command> you will find a browse-able index of documentation in <filename>/usr/share/doc/HTML/index.html</filename>."
 msgstr ""
 
-#: boot-new.xml:917
+#: boot-new.xml:226
 #, no-c-format
 #. Tag: para
 msgid "One easy way to view these documents is to <userinput>cd /usr/share/doc/</userinput>, and type <userinput>lynx</userinput> followed by a space and a dot (the dot stands for the current directory)."
 msgstr ""
 
-#: boot-new.xml:924
+#: boot-new.xml:233
 #, no-c-format
 #. Tag: para
 msgid "You can also type <userinput>info <replaceable>command</replaceable></userinput> or <userinput>man <replaceable>command</replaceable></userinput> to see documentation on most commands available at the command prompt. Typing <userinput>help</userinput> will display help on shell commands. And typing a command followed by <userinput>--help</userinput> will usually display a short summary of the command's usage. If a command's results scroll past the top of the screen, type <userinput>| more</userinput> after the command to cause the results to pause before scrolling past the top of the screen. To see a list of all commands available which begin with a certain letter, type the letter and then two tabs."
 msgstr ""
 
-#: boot-new.xml:939
+#: boot-new.xml:248
 #, no-c-format
 #. Tag: para
 msgid "For a more complete introduction to Debian and GNU/Linux, see <filename>/usr/share/doc/debian-guide/html/noframes/index.html</filename>."
diff --git a/po/pot/install-methods.pot b/po/pot/install-methods.pot
index 2e1c363df..5949a86e9 100644
--- a/po/pot/install-methods.pot
+++ b/po/pot/install-methods.pot
@@ -6,7 +6,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2005-12-03 10:28+0000\n"
+"POT-Creation-Date: 2006-01-03 19:55+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"
@@ -461,7 +461,7 @@ msgstr ""
 msgid "If you like more flexibility or just want to know what's going on, you should use the following method to put the files on your stick."
 msgstr ""
 
-#: install-methods.xml:650 install-methods.xml:746
+#: install-methods.xml:650 install-methods.xml:742
 #, no-c-format
 #. Tag: title
 msgid "USB stick partitioning on &arch-title;"
@@ -510,10 +510,10 @@ msgid ""
       "The <filename>syslinux.cfg</filename> configuration file should contain the following two lines: <informalexample><screen>\n"
       "default vmlinuz\n"
       "append initrd=initrd.gz ramdisk_size=12000 root=/dev/ram rw\n"
-      "</screen></informalexample> Please note that the <userinput>ramdisk_size</userinput> parameter may need to be increased, depending on the image you are booting. <phrase condition=\"sarge\"> If the boot fails, you can try adding <userinput>devfs=mount,dall</userinput> to the <quote>append</quote> line. </phrase>"
+      "</screen></informalexample> Please note that the <userinput>ramdisk_size</userinput> parameter may need to be increased, depending on the image you are booting."
 msgstr ""
 
-#: install-methods.xml:747
+#: install-methods.xml:743
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -522,13 +522,13 @@ msgid ""
       "</screen></informalexample> Take care that you use the correct device name for your USB stick. The <command>hformat</command> command is contained in the <classname>hfsutils</classname> Debian package."
 msgstr ""
 
-#: install-methods.xml:763
+#: install-methods.xml:759
 #, no-c-format
 #. Tag: para
 msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. The <command>yaboot</command> boot loader can be installed on an HFS filesystem and can be reconfigured by just editing a text file. Any operating system which supports the HFS file system can be used to make changes to the configuration of the boot loader."
 msgstr ""
 
-#: install-methods.xml:772
+#: install-methods.xml:768
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -541,43 +541,43 @@ msgid ""
       "</screen></informalexample> Again, take care that you use the correct device name. The partition must not be otherwise mounted during this procedure. This procedure writes the boot loader to the partition, and uses the HFS utilities to mark it in such a way that Open Firmware will boot it. Having done this, the rest of the USB stick may be prepared using the normal Unix utilities."
 msgstr ""
 
-#: install-methods.xml:788
+#: install-methods.xml:784
 #, no-c-format
 #. Tag: para
 msgid "Mount the partition (<userinput>mount /dev/sda2 /mnt</userinput>) and copy the following files from the Debian archives to the stick:"
 msgstr ""
 
-#: install-methods.xml:794
+#: install-methods.xml:790
 #, no-c-format
 #. Tag: para
 msgid "<filename>vmlinux</filename> (kernel binary)"
 msgstr ""
 
-#: install-methods.xml:799
+#: install-methods.xml:795
 #, no-c-format
 #. Tag: para
 msgid "<filename>initrd.gz</filename> (initial ramdisk image)"
 msgstr ""
 
-#: install-methods.xml:804
+#: install-methods.xml:800
 #, no-c-format
 #. Tag: para
 msgid "<filename>yaboot.conf</filename> (yaboot configuration file)"
 msgstr ""
 
-#: install-methods.xml:809
+#: install-methods.xml:805
 #, no-c-format
 #. Tag: para
 msgid "<filename>boot.msg</filename> (optional boot message)"
 msgstr ""
 
-#: install-methods.xml:814
+#: install-methods.xml:810
 #, no-c-format
 #. Tag: para
 msgid "Optional kernel modules"
 msgstr ""
 
-#: install-methods.xml:821
+#: install-methods.xml:817
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -590,271 +590,270 @@ msgid ""
       "image=/vmlinux\n"
       "        label=install\n"
       "        initrd=/initrd.gz\n"
-      "        initrd-size=10000<phrase condition=\"sarge\">\n"
-      "        append=\"devfs=mount,dall --\"</phrase>\n"
+      "        initrd-size=10000\n"
       "        read-only\n"
       "</screen></informalexample> Please note that the <userinput>initrd-size</userinput> parameter may need to be increased, depending on the image you are booting."
 msgstr ""
 
-#: install-methods.xml:836
+#: install-methods.xml:832
 #, no-c-format
 #. Tag: title
 msgid "Adding an ISO image"
 msgstr ""
 
-#: install-methods.xml:837
+#: install-methods.xml:833
 #, no-c-format
 #. Tag: para
 msgid "Now you should put any Debian ISO image (businesscard, netinst or even a full one) onto your stick (if it fits). The file name of such an image must end in <filename>.iso</filename>."
 msgstr ""
 
-#: install-methods.xml:843
+#: install-methods.xml:839
 #, no-c-format
 #. Tag: para
 msgid "If you want to install over the network, without using an ISO image, you will of course skip the previous step. Moreover you will have to use the initial ramdisk from the <filename>netboot</filename> directory instead of the one from <filename>hd-media</filename>, because <filename>hd-media/initrd.gz</filename> does not have network support."
 msgstr ""
 
-#: install-methods.xml:852
+#: install-methods.xml:848
 #, no-c-format
 #. Tag: para
 msgid "When you are done, unmount the USB memory stick (<userinput>umount /mnt</userinput>) and activate its write protection switch."
 msgstr ""
 
-#: install-methods.xml:862
+#: install-methods.xml:858
 #, no-c-format
 #. Tag: title
 msgid "Booting the USB stick"
 msgstr ""
 
-#: install-methods.xml:863
+#: install-methods.xml:859
 #, no-c-format
 #. Tag: para
 msgid "If your system refuses to boot from the memory stick, the stick may contain an invalid master boot record (MBR). To fix this, use the <command>install-mbr</command> command from the package <classname>mbr</classname>:"
 msgstr ""
 
-#: install-methods.xml:870
+#: install-methods.xml:866
 #, no-c-format
 #. Tag: screen
 msgid "# install-mbr /dev/<replaceable>sda</replaceable>"
 msgstr ""
 
-#: install-methods.xml:882
+#: install-methods.xml:878
 #, no-c-format
 #. Tag: title
 msgid "Preparing Files for Hard Disk Booting"
 msgstr ""
 
-#: install-methods.xml:883
+#: install-methods.xml:879
 #, no-c-format
 #. Tag: para
 msgid "The installer may be booted using boot files placed on an existing hard drive partition, either launched from another operating system or by invoking a boot loader directly from the BIOS."
 msgstr ""
 
-#: install-methods.xml:889
+#: install-methods.xml:885
 #, no-c-format
 #. Tag: para
 msgid "A full, <quote>pure network</quote> installation can be achieved using this technique. This avoids all hassles of removable media, like finding and burning CD images or struggling with too numerous and unreliable floppy disks."
 msgstr ""
 
-#: install-methods.xml:896
+#: install-methods.xml:892
 #, no-c-format
 #. Tag: para
 msgid "The installer cannot boot from files on an NTFS file system."
 msgstr ""
 
-#: install-methods.xml:900
+#: install-methods.xml:896
 #, no-c-format
 #. Tag: para
 msgid "The installer cannot boot from files on an HFS+ file system. MacOS System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. To determine whether your existing file system is HFS+, select <userinput>Get Info</userinput> for the volume in question. HFS file systems appear as <userinput>Mac OS Standard</userinput>, while HFS+ file systems say <userinput>Mac OS Extended</userinput>. You must have an HFS partition in order to exchange files between MacOS and Linux, in particular the installation files you download."
 msgstr ""
 
-#: install-methods.xml:911
+#: install-methods.xml:907
 #, no-c-format
 #. Tag: para
 msgid "Different programs are used for hard disk installation system booting, depending on whether the system is a <quote>NewWorld</quote> or an <quote>OldWorld</quote> model."
 msgstr ""
 
-#: install-methods.xml:920
+#: install-methods.xml:916
 #, no-c-format
 #. Tag: title
 msgid "Hard disk installer booting using <command>LILO</command> or <command>GRUB</command>"
 msgstr ""
 
-#: install-methods.xml:922
+#: install-methods.xml:918
 #, no-c-format
 #. Tag: para
 msgid "This section explains how to add to or even replace an existing linux installation using either <command>LILO</command> or <command>GRUB</command>."
 msgstr ""
 
-#: install-methods.xml:928
+#: install-methods.xml:924
 #, no-c-format
 #. Tag: para
 msgid "At boot time, both bootloaders support loading in memory not only the kernel, but also a disk image. This RAM disk can be used as the root file-system by the kernel."
 msgstr ""
 
-#: install-methods.xml:934
+#: install-methods.xml:930
 #, no-c-format
 #. Tag: para
 msgid "Copy the following files from the Debian archives to a convenient location on your hard drive, for instance to <filename>/boot/newinstall/</filename>."
 msgstr ""
 
-#: install-methods.xml:941
+#: install-methods.xml:937
 #, no-c-format
 #. Tag: para
 msgid "<filename>vmlinuz</filename> (kernel binary)"
 msgstr ""
 
-#: install-methods.xml:946
+#: install-methods.xml:942
 #, no-c-format
 #. Tag: para
 msgid "<filename>initrd.gz</filename> (ramdisk image)"
 msgstr ""
 
-#: install-methods.xml:953
+#: install-methods.xml:949
 #, no-c-format
 #. Tag: para
 msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>."
 msgstr ""
 
-#: install-methods.xml:963
+#: install-methods.xml:959
 #, no-c-format
 #. Tag: title
 msgid "Hard Disk Installer Booting for OldWorld Macs"
 msgstr ""
 
-#: install-methods.xml:964
+#: install-methods.xml:960
 #, no-c-format
 #. Tag: para
 msgid "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</application> to launch Linux installation, but <application>miBoot</application> cannot easily be used for hard disk booting. <application>BootX</application>, launched from MacOS, supports booting from files placed on the hard disk. <application>BootX</application> can also be used to dual-boot MacOS and Linux after your Debian installation is complete. For the Performa 6360, it appears that <command>quik</command> cannot make the hard disk bootable. So <application>BootX</application> is required on that model."
 msgstr ""
 
-#: install-methods.xml:977
+#: install-methods.xml:973
 #, no-c-format
 #. Tag: para
 msgid "Download and unstuff the <application>BootX</application> distribution, available from <ulink url=\"&url-powerpc-bootx;\"></ulink>, or in the <filename>dists/woody/main/disks-powerpc/current/powermac</filename> directory on Debian http/ftp mirrors and official Debian CDs. Use <application>Stuffit Expander</application> to extract it from its archive. Within the package, there is an empty folder called <filename>Linux Kernels</filename>. Download <filename>linux.bin</filename> and <filename>ramdisk.image.gz</filename> from the <filename>disks-powerpc/current/powermac</filename> folder, and place them in the <filename>Linux Kernels</filename> folder. Then place the <filename>Linux Kernels</filename> folder in the active System Folder."
 msgstr ""
 
-#: install-methods.xml:997
+#: install-methods.xml:993
 #, no-c-format
 #. Tag: title
 msgid "Hard Disk Installer Booting for NewWorld Macs"
 msgstr ""
 
-#: install-methods.xml:998
+#: install-methods.xml:994
 #, no-c-format
 #. Tag: para
 msgid "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as well as loading ELF binaries directly from the hard disk. These machines will boot Linux directly via <command>yaboot</command>, which supports loading a kernel and RAMdisk directly from an ext2 partition, as well as dual-booting with MacOS. Hard disk booting of the installer is particularly appropriate for newer machines without floppy drives. <command>BootX</command> is not supported and must not be used on NewWorld PowerMacs."
 msgstr ""
 
-#: install-methods.xml:1009
+#: install-methods.xml:1005
 #, no-c-format
 #. Tag: para
 msgid "<emphasis>Copy</emphasis> (not move) the following four files which you downloaded earlier from the Debian archives, onto the root level of your hard drive (this can be accomplished by <keycap>option</keycap>-dragging each file to the hard drive icon)."
 msgstr ""
 
-#: install-methods.xml:1019
+#: install-methods.xml:1015
 #, no-c-format
 #. Tag: filename
 msgid "vmlinux"
 msgstr ""
 
-#: install-methods.xml:1024
+#: install-methods.xml:1020
 #, no-c-format
 #. Tag: filename
 msgid "initrd.gz"
 msgstr ""
 
-#: install-methods.xml:1029
+#: install-methods.xml:1025
 #, no-c-format
 #. Tag: filename
 msgid "yaboot"
 msgstr ""
 
-#: install-methods.xml:1034
+#: install-methods.xml:1030
 #, no-c-format
 #. Tag: filename
 msgid "yaboot.conf"
 msgstr ""
 
-#: install-methods.xml:1039
+#: install-methods.xml:1035
 #, no-c-format
 #. Tag: para
 msgid "Make a note of the partition number of the MacOS partition where you place these files. If you have the MacOS <command>pdisk</command> program, you can use the L command to check for the partition number. You will need this partition number for the command you type at the Open Firmware prompt when you boot the installer."
 msgstr ""
 
-#: install-methods.xml:1047
+#: install-methods.xml:1043
 #, no-c-format
 #. Tag: para
 msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>."
 msgstr ""
 
-#: install-methods.xml:1060
+#: install-methods.xml:1056
 #, no-c-format
 #. Tag: title
 msgid "Preparing Files for TFTP Net Booting"
 msgstr ""
 
-#: install-methods.xml:1061
+#: install-methods.xml:1057
 #, no-c-format
 #. Tag: para
 msgid "If your machine is connected to a local area network, you may be able to boot it over the network from another machine, using TFTP. If you intend to boot the installation system from another machine, the boot files will need to be placed in specific locations on that machine, and the machine configured to support booting of your specific machine."
 msgstr ""
 
-#: install-methods.xml:1069
+#: install-methods.xml:1065
 #, no-c-format
 #. Tag: para
 msgid "You need to setup a TFTP server, and for many machines, a BOOTP server <phrase condition=\"supports-rarp\">, or RARP server</phrase> <phrase condition=\"supports-dhcp\">, or DHCP server</phrase>."
 msgstr ""
 
-#: install-methods.xml:1075
+#: install-methods.xml:1071
 #, no-c-format
 #. Tag: para
 msgid "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol (RARP) is one way to tell your client what IP address to use for itself. Another way is to use the BOOTP protocol. </phrase> <phrase condition=\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP address and where on the network to obtain a boot image. </phrase> <phrase arch=\"m68k\"> Yet another alternative exists on VMEbus systems: the IP address can be manually configured in boot ROM. </phrase> <phrase condition=\"supports-dhcp\">The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP. </phrase>"
 msgstr ""
 
-#: install-methods.xml:1092
+#: install-methods.xml:1088
 #, no-c-format
 #. Tag: para
 msgid "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good idea to use DHCP instead of BOOTP. Some of the latest machines are unable to boot using BOOTP."
 msgstr ""
 
-#: install-methods.xml:1098
+#: install-methods.xml:1094
 #, no-c-format
 #. Tag: para
 msgid "Unlike the Open Firmware found on Sparc and PowerPC machines, the SRM console will <emphasis>not</emphasis> use RARP to obtain its IP address, and therefore you must use BOOTP for net booting your Alpha<footnote> <para> Alpha systems can also be net-booted using the DECNet MOP (Maintenance Operations Protocol), but this is not covered here. Presumably, your local OpenVMS operator will be happy to assist you should you have some burning need to use MOP to boot Linux on your Alpha. </para> </footnote>. You can also enter the IP configuration for network interfaces directly in the SRM console."
 msgstr ""
 
-#: install-methods.xml:1115
+#: install-methods.xml:1111
 #, no-c-format
 #. Tag: para
 msgid "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There is an <classname>rbootd</classname> package available in Debian."
 msgstr ""
 
-#: install-methods.xml:1120
+#: install-methods.xml:1116
 #, no-c-format
 #. Tag: para
 msgid "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to the client. Theoretically, any server, on any platform, which implements these protocols, may be used. In the examples in this section, we shall provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux."
 msgstr ""
 
-#: install-methods.xml:1128
+#: install-methods.xml:1124
 #, no-c-format
 #. Tag: para
 msgid "To use the Pre-boot Execution Environment (PXE) method of TFTP booting, you will need a TFTP server with <userinput>tsize</userinput> support. On a &debian; server, the <classname>atftpd</classname> and <classname>tftpd-hpa</classname> packages qualify; we recommend <classname>tftpd-hpa</classname>."
 msgstr ""
 
-#: install-methods.xml:1146
+#: install-methods.xml:1142
 #, no-c-format
 #. Tag: title
 msgid "Setting up RARP server"
 msgstr ""
 
-#: install-methods.xml:1147
+#: install-methods.xml:1143
 #, no-c-format
 #. Tag: para
 msgid "To setup RARP, you need to know the Ethernet address (a.k.a. the MAC address) of the client computers to be installed. If you don't know this information, you can <phrase arch=\"sparc\"> pick it off the initial OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the command <userinput>/sbin/ifconfig eth0</userinput>."
 msgstr ""
 
-#: install-methods.xml:1159
+#: install-methods.xml:1155
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -871,31 +870,31 @@ msgid ""
       "</screen></informalexample> you probably need to load the RARP kernel module or else recompile the kernel to support RARP. Try <userinput>modprobe rarp</userinput> and then try the <command>rarp</command> command again."
 msgstr ""
 
-#: install-methods.xml:1175
+#: install-methods.xml:1171
 #, no-c-format
 #. Tag: para
 msgid "On a RARP server system using a Linux 2.4.x kernel, there is no RARP module, and you should instead use the <command>rarpd</command> program. The procedure is similar to that used under SunOS in the following paragraph."
 msgstr ""
 
-#: install-methods.xml:1183
+#: install-methods.xml:1179
 #, no-c-format
 #. Tag: para
 msgid "Under SunOS, you need to ensure that the Ethernet hardware address for the client is listed in the <quote>ethers</quote> database (either in the <filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start the RARP daemon. In SunOS 4, issue the command (as root): <userinput>/usr/etc/rarpd -a</userinput>; in SunOS 5, use <userinput>/usr/sbin/rarpd -a</userinput>."
 msgstr ""
 
-#: install-methods.xml:1202
+#: install-methods.xml:1198
 #, no-c-format
 #. Tag: title
 msgid "Setting up BOOTP server"
 msgstr ""
 
-#: install-methods.xml:1203
+#: install-methods.xml:1199
 #, no-c-format
 #. Tag: para
 msgid "There are two BOOTP servers available for GNU/Linux, the CMU <command>bootpd</command> and the other is actually a DHCP server, ISC <command>dhcpd</command>, which are contained in the <classname>bootp</classname> and <classname>dhcp</classname> packages in &debian;."
 msgstr ""
 
-#: install-methods.xml:1211
+#: install-methods.xml:1207
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -912,19 +911,19 @@ msgid ""
       "</screen></informalexample> You will need to change at least the <quote>ha</quote> option, which specifies the hardware address of the client. The <quote>bf</quote> option specifies the file a client should retrieve via TFTP; see <xref linkend=\"tftp-images\"/> for more details. <phrase arch=\"mips\"> On SGI Indys you can just enter the command monitor and type <userinput>printenv</userinput>. The value of the <userinput>eaddr</userinput> variable is the machine's MAC address. </phrase>"
 msgstr ""
 
-#: install-methods.xml:1244
+#: install-methods.xml:1240
 #, no-c-format
 #. Tag: para
 msgid "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really easy, because it treats BOOTP clients as a moderately special case of DHCP clients. Some architectures require a complex configuration for booting clients via BOOTP. If yours is one of those, read the section <xref linkend=\"dhcpd\"/>. Otherwise, you will probably be able to get away with simply adding the <userinput>allow bootp</userinput> directive to the configuration block for the subnet containing the client, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcpd restart</userinput>."
 msgstr ""
 
-#: install-methods.xml:1265
+#: install-methods.xml:1261
 #, no-c-format
 #. Tag: title
 msgid "Setting up a DHCP server"
 msgstr ""
 
-#: install-methods.xml:1266
+#: install-methods.xml:1262
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -951,25 +950,25 @@ msgid ""
       "</screen></informalexample> Note: the new (and preferred) <classname>dhcp3</classname> package uses <filename>/etc/dhcp3/dhcpd.conf</filename>."
 msgstr ""
 
-#: install-methods.xml:1278
+#: install-methods.xml:1274
 #, no-c-format
 #. Tag: para
 msgid "In this example, there is one server <replaceable>servername</replaceable> which performs all of the work of DHCP server, TFTP server, and network gateway. You will almost certainly need to change the domain-name options, as well as the server name and client hardware address. The <replaceable>filename</replaceable> option should be the name of the file which will be retrieved via TFTP."
 msgstr ""
 
-#: install-methods.xml:1288
+#: install-methods.xml:1284
 #, no-c-format
 #. Tag: para
 msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/dhcpd restart</userinput>."
 msgstr ""
 
-#: install-methods.xml:1296
+#: install-methods.xml:1292
 #, no-c-format
 #. Tag: title
 msgid "Enabling PXE Booting in the DHCP configuration"
 msgstr ""
 
-#: install-methods.xml:1297
+#: install-methods.xml:1293
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1004,13 +1003,13 @@ msgid ""
       "</screen></informalexample> Note that for PXE booting, the client filename <filename>pxelinux.0</filename> is a boot loader, not a kernel image (see <xref linkend=\"tftp-images\"/> below)."
 msgstr ""
 
-#: install-methods.xml:1313
+#: install-methods.xml:1309
 #, no-c-format
 #. Tag: title
 msgid "Enabling the TFTP Server"
 msgstr ""
 
-#: install-methods.xml:1314
+#: install-methods.xml:1310
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1019,13 +1018,13 @@ msgid ""
       "</screen></informalexample> Debian packages will in general set this up correctly by default when they are installed."
 msgstr ""
 
-#: install-methods.xml:1325
+#: install-methods.xml:1321
 #, no-c-format
 #. Tag: para
 msgid "Look in that file and remember the directory which is used as the argument of <command>in.tftpd</command>; you'll need that below. The <userinput>-l</userinput> argument enables some versions of <command>in.tftpd</command> to log all requests to the system logs; this is useful for diagnosing boot errors. If you've had to change <filename>/etc/inetd.conf</filename>, you'll have to notify the running <command>inetd</command> process that the file has changed. On a Debian machine, run <userinput>/etc/init.d/inetd reload</userinput>; on other machines, find out the process ID for <command>inetd</command>, and run <userinput>kill -HUP <replaceable>inetd-pid</replaceable></userinput>."
 msgstr ""
 
-#: install-methods.xml:1339
+#: install-methods.xml:1335
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1036,85 +1035,85 @@ msgid ""
       "</screen></informalexample> to adjust the range of source ports the Linux TFTP server uses."
 msgstr ""
 
-#: install-methods.xml:1361
+#: install-methods.xml:1357
 #, no-c-format
 #. Tag: title
 msgid "Move TFTP Images Into Place"
 msgstr ""
 
-#: install-methods.xml:1362
+#: install-methods.xml:1358
 #, no-c-format
 #. Tag: para
 msgid "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-files\"/>, in the <command>tftpd</command> boot image directory. Generally, this directory will be <filename>/tftpboot</filename>. You'll have to make a link from that file to the file which <command>tftpd</command> will use for booting a particular client. Unfortunately, the file name is determined by the TFTP client, and there are no strong standards."
 msgstr ""
 
-#: install-methods.xml:1372
+#: install-methods.xml:1368
 #, no-c-format
 #. Tag: para
 msgid "On NewWorld Power Macintosh machines, you will need to set up the <command>yaboot</command> boot loader as the TFTP boot image. <command>Yaboot</command> will then retrieve the kernel and RAMdisk images via TFTP itself. For net booting, use the <filename>yaboot-netboot.conf</filename>. Just rename this to <filename>yaboot.conf</filename> in the TFTP directory."
 msgstr ""
 
-#: install-methods.xml:1381
+#: install-methods.xml:1377
 #, no-c-format
 #. Tag: para
 msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/pxelinux.0</filename> to <command>tftpd</command> as the filename to boot."
 msgstr ""
 
-#: install-methods.xml:1389
+#: install-methods.xml:1385
 #, no-c-format
 #. Tag: para
 msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/debian-installer/ia64/elilo.efi</filename> to <command>tftpd</command> as the filename to boot."
 msgstr ""
 
-#: install-methods.xml:1401
+#: install-methods.xml:1397
 #, no-c-format
 #. Tag: title
 msgid "DECstation TFTP Images"
 msgstr ""
 
-#: install-methods.xml:1402
+#: install-methods.xml:1398
 #, no-c-format
 #. Tag: para
 msgid "For DECstations, there are tftpimage files for each subarchitecture, which contain both kernel and installer in one file. The naming convention is <replaceable>subarchitecture</replaceable>/netboot-boot.img. Copy the tftpimage file you would like to use to <userinput>/tftpboot/tftpboot.img</userinput> if you work with the example BOOTP/DHCP setups described above."
 msgstr ""
 
-#: install-methods.xml:1411
+#: install-methods.xml:1407
 #, no-c-format
 #. Tag: para
 msgid "The DECstation firmware boots by TFTP with the command <userinput>boot <replaceable>#</replaceable>/tftp</userinput>, where <replaceable>#</replaceable> is the number of the TurboChannel device from which to boot. On most DECstations this is <quote>3</quote>. If the BOOTP/DHCP server does not supply the filename or you need to pass additional parameters, they can optionally be appended with the following syntax:"
 msgstr ""
 
-#: install-methods.xml:1423
+#: install-methods.xml:1419
 #, no-c-format
 #. Tag: userinput
 msgid "boot #/tftp/filename param1=value1 param2=value2 ..."
 msgstr ""
 
-#: install-methods.xml:1425
+#: install-methods.xml:1421
 #, no-c-format
 #. Tag: para
 msgid "Several DECstation firmware revisions show a problem with regard to net booting: the transfer starts, but after some time it stops with an <computeroutput>a.out err</computeroutput>. This can have several reasons: <orderedlist> <listitem><para> The firmware does not respond to ARP requests during a TFTP transfer. This leads to an ARP timeout and the transfer stops. The solution is to add the MAC address of the Ethernet card in the DECstation statically to the ARP table of the TFTP server. This is done by running <userinput>arp -s <replaceable>IP-address</replaceable> <replaceable>MAC-address</replaceable></userinput> as root on the machine acting as TFTP server. The MAC-address of the DECstation can be read out by entering <command>cnfg</command> at the DECstation firmware prompt. </para></listitem> <listitem><para> The firmware has a size limit on the files that can be booted by TFTP. </para></listitem> </orderedlist> There are also firmware revisions that cannot boot via TFTP at all. An overview about the different firmware revisions can be found at the NetBSD web pages: <ulink url=\"http://www.netbsd.org/Ports/pmax/board-list.html#proms\"></ulink>."
 msgstr ""
 
-#: install-methods.xml:1463
+#: install-methods.xml:1459
 #, no-c-format
 #. Tag: title
 msgid "Alpha TFTP Booting"
 msgstr ""
 
-#: install-methods.xml:1464
+#: install-methods.xml:1460
 #, no-c-format
 #. Tag: para
 msgid "On Alpha, you must specify the filename (as a relative path to the boot image directory) using the <userinput>-file</userinput> argument to the SRM <userinput>boot</userinput> command, or by setting the <userinput>BOOT_FILE</userinput> environment variable. Alternatively, the filename can be given via BOOTP (in ISC <command>dhcpd</command>, use the <userinput>filename</userinput> directive). Unlike Open Firmware, there is <emphasis>no default filename</emphasis> on SRM, so you <emphasis>must</emphasis> specify a filename by either one of these methods."
 msgstr ""
 
-#: install-methods.xml:1479
+#: install-methods.xml:1475
 #, no-c-format
 #. Tag: title
 msgid "SPARC TFTP Booting"
 msgstr ""
 
-#: install-methods.xml:1480
+#: install-methods.xml:1476
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1123,127 +1122,81 @@ msgid ""
       "</screen></informalexample> This will spit out the IP in hexadecimal; to get to the correct filename, you will need to change all letters to uppercase and if necessary append the subarchitecture name."
 msgstr ""
 
-#: install-methods.xml:1497
+#: install-methods.xml:1493
 #, no-c-format
 #. Tag: para
 msgid "You can also force some sparc systems to look for a specific file name by adding it to the end of the OpenPROM boot command, such as <userinput>boot net my-sparc.image</userinput>. This must still reside in the directory that the TFTP server looks in."
 msgstr ""
 
-#: install-methods.xml:1508
+#: install-methods.xml:1504
 #, no-c-format
 #. Tag: title
 msgid "BVM/Motorola TFTP Booting"
 msgstr ""
 
-#: install-methods.xml:1509
+#: install-methods.xml:1505
 #, no-c-format
 #. Tag: para
 msgid "For BVM and Motorola VMEbus systems copy the files &bvme6000-tftp-files; to <filename>/tftpboot/</filename>."
 msgstr ""
 
-#: install-methods.xml:1514
+#: install-methods.xml:1510
 #, no-c-format
 #. Tag: para
 msgid "Next, configure your boot ROMs or BOOTP server to initially load the <filename>tftplilo.bvme</filename> or <filename>tftplilo.mvme</filename> files from the TFTP server. Refer to the <filename>tftplilo.txt</filename> file for your subarchitecture for additional system-specific configuration information."
 msgstr ""
 
-#: install-methods.xml:1526
+#: install-methods.xml:1522
 #, no-c-format
 #. Tag: title
 msgid "SGI Indys TFTP Booting"
 msgstr ""
 
-#: install-methods.xml:1527
+#: install-methods.xml:1523
 #, no-c-format
 #. Tag: para
 msgid "On SGI Indys you can rely on the <command>bootpd</command> to supply the name of the TFTP file. It is given either as the <userinput>bf=</userinput> in <filename>/etc/bootptab</filename> or as the <userinput>filename=</userinput> option in <filename>/etc/dhcpd.conf</filename>."
 msgstr ""
 
-#: install-methods.xml:1539
+#: install-methods.xml:1535
 #, no-c-format
 #. Tag: title
 msgid "Broadcom BCM91250A TFTP Booting"
 msgstr ""
 
-#: install-methods.xml:1540
+#: install-methods.xml:1536
 #, no-c-format
 #. Tag: para
 msgid "You don't have to configure DHCP in a special way because you'll pass the full path of the file to the loaded to CFE."
 msgstr ""
 
-#: install-methods.xml:1645
+#: install-methods.xml:1641
 #, no-c-format
 #. Tag: title
 msgid "Automatic Installation"
 msgstr ""
 
-#: install-methods.xml:1646
+#: install-methods.xml:1642
 #, no-c-format
 #. Tag: para
 msgid "For installing on multiple computers it's possible to do fully automatic installations. Debian packages intended for this include <classname>fai</classname> (which uses an install server), <classname>replicator</classname>, <classname>systemimager</classname>, <classname>autoinstall</classname>, and the Debian Installer itself."
 msgstr ""
 
-#: install-methods.xml:1659
+#: install-methods.xml:1655
 #, no-c-format
 #. Tag: title
 msgid "Automatic Installation Using the Debian Installer"
 msgstr ""
 
-#: install-methods.xml:1660
+#: install-methods.xml:1656
 #, no-c-format
 #. Tag: para
 msgid "The Debian Installer supports automating installs via preconfiguration files. A preconfiguration file can be loaded from the network or from removable media, and used to fill in answers to questions asked during the installation process."
 msgstr ""
 
-#: install-methods.xml:1667
+#: install-methods.xml:1663
 #, no-c-format
 #. Tag: para
 msgid "Full documentation on preseeding including a working example that you can edit is in <xref linkend=\"appendix-preseed\"/>."
 msgstr ""
 
-#: install-methods.xml:1672
-#, no-c-format
-#. Tag: para
-msgid "Although most dialogs used by &d-i; can be preseeded using this method, there are some notable exceptions. You can (re)partition an entire disk or use available free space on a disk; it is not possible to use existing partitions. You currently cannot use preseeding to set up RAID and LVM. Also, with the exception of network driver modules, it is not possible to preconfigure kernel module parameters."
-msgstr ""
-
-#: install-methods.xml:1681
-#, no-c-format
-#. Tag: para
-msgid "The preconfiguration file is in the format used by the debconf-set-selections command. A well documented and working example that you can edit is in <xref linkend=\"example-preseed\"/>."
-msgstr ""
-
-#: install-methods.xml:1687
-#, no-c-format
-#. Tag: para
-msgid ""
-      "Alternatively, one way to get a complete file listing all the values that can be preseeded is to do a manual install, and then use <filename>debconf-get-selections</filename>, from the <classname>debconf-utils</classname> package, to dump both the debconf database and the cdebconf database in /var/log/debian-installer/cdebconf to a single file: <informalexample><screen>\n"
-      "$ debconf-get-selections --installer &gt; <replaceable>file</replaceable>\n"
-      "$ debconf-get-selections &gt;&gt; <replaceable>file</replaceable>\n"
-      "</screen></informalexample> However, a file generated in this manner will have some items that should not be preseeded, and the file in <xref linkend=\"example-preseed\"/> is a better starting place for most users."
-msgstr ""
-
-#: install-methods.xml:1702
-#, no-c-format
-#. Tag: para
-msgid "Once you have a preconfiguration file, you can edit it if necessary, and place it on a web server, or copy it onto the installer's boot media. Wherever you place the file, you need to pass a parameter to the installer at boot time to tell it to use the file."
-msgstr ""
-
-#: install-methods.xml:1709
-#, no-c-format
-#. Tag: para
-msgid "To make the installer use a preconfiguration file downloaded from the network, add preseed/url=http://url/to/preseed.cfg to the kernel boot parameters. Of course the preconfiguration will not take effect until the installer manages to set up the network to download the file, so this is most useful if the installer can set up the network via DHCP without asking any questions. You may want to set the installation priority to critical to avoid any questions while the network is being configured. See <xref linkend=\"installer-args\"/>."
-msgstr ""
-
-#: install-methods.xml:1720
-#, no-c-format
-#. Tag: para
-msgid "To place a preconfiguration file on a CD, you would need to remaster the ISO image to include your preconfiguration file. See the manual page for mkisofs for details. Alternatively, put the preseed file on a floppy, and use preseed/file=/floppy/preseed.cfg"
-msgstr ""
-
-#: install-methods.xml:1727
-#, no-c-format
-#. Tag: para
-msgid "If you'll be booting from a USB memory stick, then you can simply copy your preconfiguration file onto the memory stick's filesystem, and edit the syslinux.cfg file to add preseed/file=/hd-media/preseed.cfg to the kernel boot parameters."
-msgstr ""
-
diff --git a/po/pot/installation-howto.pot b/po/pot/installation-howto.pot
index 57ebf8ca0..1324cb668 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"
-"POT-Creation-Date: 2005-12-03 10:28+0000\n"
+"POT-Creation-Date: 2006-01-03 19:55+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,100 +191,100 @@ msgstr ""
 #: installation-howto.xml:212
 #, no-c-format
 #. Tag: para
-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\"> <phrase condition=\"sarge\"> If you want a 2.6 kernel, type <userinput>linux26</userinput> at the <prompt>boot:</prompt> prompt. </phrase> <phrase condition=\"etch\"> If you want a 2.4 kernel, type <userinput>install24</userinput> at the <prompt>boot:</prompt> prompt. </phrase> <footnote><para> <phrase condition=\"sarge\"> The 2.6 kernel is available for most boot methods, but not when booting from a floppy. </phrase> <phrase condition=\"etch\"> The 2.6 kernel is the default for most boot methods, but is not available when booting from a floppy. </phrase> </para></footnote> </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\"/>). <phrase arch=\"i386\"> If you want a 2.4 kernel, type <userinput>install24</userinput> at the <prompt>boot:</prompt> prompt. <footnote><para> The 2.6 kernel is the default for most boot methods, but is not available when booting from a floppy. </para></footnote> </phrase>"
 msgstr ""
 
-#: installation-howto.xml:240
+#: installation-howto.xml:228
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: installation-howto.xml:248
+#: installation-howto.xml:236
 #, no-c-format
 #. Tag: para
 msgid "You may be asked to confirm your keyboard layout. Choose the default unless you know better."
 msgstr ""
 
-#: installation-howto.xml:253
+#: installation-howto.xml:241
 #, no-c-format
 #. Tag: para
 msgid "Now sit back while debian-installer detects some of your hardware, and loads the rest of itself from CD, floppy, USB, etc."
 msgstr ""
 
-#: installation-howto.xml:258
+#: installation-howto.xml:246
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: installation-howto.xml:264
+#: installation-howto.xml:252
 #, no-c-format
 #. Tag: para
 msgid "Now it is time to partition your disks. First you will be given the opportunity to automatically partition either an entire drive, or free space on a drive. This is recommended for new users or anyone in a hurry, but if you do not want to autopartition, choose manual from the menu."
 msgstr ""
 
-#: installation-howto.xml:271
+#: installation-howto.xml:259
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: installation-howto.xml:278
+#: installation-howto.xml:266
 #, no-c-format
 #. Tag: para
 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>Finished partitioning</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 ""
 
-#: installation-howto.xml:288
+#: installation-howto.xml:276
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: installation-howto.xml:293
+#: installation-howto.xml:281
 #, no-c-format
 #. Tag: para
 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=\"i386\">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 ""
 
-#: installation-howto.xml:303
+#: installation-howto.xml:291
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: installation-howto.xml:310
+#: installation-howto.xml:298
 #, no-c-format
 #. Tag: para
 msgid "If you need more information on the install process, see <xref linkend=\"d-i-intro\"/>."
 msgstr ""
 
-#: installation-howto.xml:319
+#: installation-howto.xml:307
 #, no-c-format
 #. Tag: title
 msgid "Send us an installation report"
 msgstr ""
 
-#: installation-howto.xml:320
+#: installation-howto.xml:308
 #, no-c-format
 #. Tag: para
-msgid "If you successfully managed an installation with &d-i;, please take time to provide us with a report. <phrase condition=\"sarge\"> There is a template named <filename>install-report.template</filename> in the <filename>/root</filename> directory of a freshly installed system. Please fill it out and file it as a bug against the package <classname>installation-reports</classname>, as explained in <xref linkend=\"submit-bug\"/>. </phrase> <phrase condition=\"etch\"> 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>. </phrase>"
+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 ""
 
-#: installation-howto.xml:338
+#: installation-howto.xml:316
 #, no-c-format
 #. Tag: para
-msgid "If you did not reach base-config or ran into other trouble, 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\"/>."
+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 ""
 
-#: installation-howto.xml:350
+#: installation-howto.xml:328
 #, no-c-format
 #. Tag: title
 msgid "And finally.."
 msgstr ""
 
-#: installation-howto.xml:351
+#: installation-howto.xml:329
 #, no-c-format
 #. Tag: para
 msgid "We hope that your Debian installation is pleasant and that you find Debian useful. You might want to read <xref linkend=\"post-install\"/>."
diff --git a/po/pot/post-install.pot b/po/pot/post-install.pot
index c329e04cb..e68631af3 100644
--- a/po/pot/post-install.pot
+++ b/po/pot/post-install.pot
@@ -6,7 +6,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2005-12-03 10:28+0000\n"
+"POT-Creation-Date: 2006-01-03 19:55+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"
@@ -302,52 +302,52 @@ msgstr ""
 #: post-install.xml:454
 #, no-c-format
 #. Tag: para
-msgid "<phrase condition=\"etch\">For more information on Debian kernels and kernel compilation, see the <ulink url=\"&url-kernel-handbook;\">Debian Linux Kernel Handbook</ulink>.</phrase> For more information on <classname>kernel-package</classname>, read the fine documentation in <filename>/usr/share/doc/kernel-package</filename>."
+msgid "For more information on Debian kernels and kernel compilation, see the <ulink url=\"&url-kernel-handbook;\">Debian Linux Kernel Handbook</ulink>. For more information on <classname>kernel-package</classname>, read the fine documentation in <filename>/usr/share/doc/kernel-package</filename>."
 msgstr ""
 
-#: post-install.xml:471
+#: post-install.xml:470
 #, no-c-format
 #. Tag: title
 msgid "Recovering a Broken System"
 msgstr ""
 
-#: post-install.xml:472
+#: post-install.xml:471
 #, no-c-format
 #. Tag: para
 msgid "Sometimes, things go wrong, and the system you've carefully installed is no longer bootable. Perhaps the boot loader configuration broke while trying out a change, or perhaps a new kernel you installed won't boot, or perhaps cosmic rays hit your disk and flipped a bit in <filename>/sbin/init</filename>. Regardless of the cause, you'll need to have a system to work from while you fix it, and rescue mode can be useful for this."
 msgstr ""
 
-#: post-install.xml:482
+#: post-install.xml:481
 #, no-c-format
 #. Tag: para
 msgid "To access rescue mode, type <userinput>rescue</userinput> at the <prompt>boot:</prompt> prompt, or boot with the <userinput>rescue/enable=true</userinput> boot parameter. You'll be shown the first few screens of the installer, with a note in the corner of the display to indicate that this is rescue mode, not a full installation. Don't worry, your system is not about to be overwritten! Rescue mode simply takes advantage of the hardware detection facilities available in the installer to ensure that your disks, network devices, and so on are available to you while repairing your system."
 msgstr ""
 
-#: post-install.xml:497
+#: post-install.xml:496
 #, no-c-format
 #. Tag: para
 msgid "Instead of the partitioning tool, you should now be presented with a list of the partitions on your system, and asked to select one of them. Normally, you should select the partition containing the root file system that you need to repair. You may select partitions on RAID and LVM devices as well as those created directly on disks."
 msgstr ""
 
-#: post-install.xml:505
+#: post-install.xml:504
 #, no-c-format
 #. Tag: para
 msgid "If possible, the installer will now present you with a shell prompt in the file system you selected, which you can use to perform any necessary repairs. <phrase arch=\"i386\"> For example, if you need to reinstall the GRUB boot loader into the master boot record of the first hard disk, you could enter the command <userinput>grub-install '(hd0)'</userinput> to do so. </phrase>"
 msgstr ""
 
-#: post-install.xml:517
+#: post-install.xml:516
 #, no-c-format
 #. Tag: para
 msgid "If the installer cannot run a usable shell in the root file system you selected, perhaps because the file system is corrupt, then it will issue a warning and offer to give you a shell in the installer environment instead. You may not have as many tools available in this environment, but they will often be enough to repair your system anyway. The root file system you selected will be mounted on the <filename>/target</filename> directory."
 msgstr ""
 
-#: post-install.xml:526
+#: post-install.xml:525
 #, no-c-format
 #. Tag: para
 msgid "In either case, after you exit the shell, the system will reboot."
 msgstr ""
 
-#: post-install.xml:530
+#: post-install.xml:529
 #, no-c-format
 #. Tag: para
 msgid "Finally, note that repairing broken systems can be difficult, and this manual does not attempt to go into all the things that might have gone wrong or how to fix them. If you have problems, consult an expert."
diff --git a/po/pot/preparing.pot b/po/pot/preparing.pot
index 92abaf249..17ab4ea6b 100644
--- a/po/pot/preparing.pot
+++ b/po/pot/preparing.pot
@@ -6,7 +6,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2005-12-03 10:28+0000\n"
+"POT-Creation-Date: 2006-01-03 19:55+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"
@@ -110,7 +110,7 @@ msgstr ""
 msgid "Configure one network interface."
 msgstr ""
 
-#: preparing.xml:106 preparing.xml:140
+#: preparing.xml:106
 #, no-c-format
 #. Tag: para
 msgid "Open a ssh connection to the new system."
@@ -143,1510 +143,1504 @@ msgstr ""
 #: preparing.xml:134
 #, no-c-format
 #. Tag: para
-msgid "Load the newly installed system for the first time, and make some initial system settings."
+msgid "Load the newly installed system for the first time."
 msgstr ""
 
-#: preparing.xml:145
-#, no-c-format
-#. Tag: para
-msgid "Install additional software (<firstterm>tasks</firstterm> and/or <firstterm>packages</firstterm>), at your discretion."
-msgstr ""
-
-#: preparing.xml:153
+#: preparing.xml:141
 #, no-c-format
 #. Tag: para
 msgid "If you have problems during the installation, it helps to know which packages are involved in which steps. Introducing the leading software actors in this installation drama:"
 msgstr ""
 
-#: preparing.xml:159
+#: preparing.xml:147
 #, no-c-format
 #. Tag: para
 msgid "The installer software, <classname>debian-installer</classname>, is the primary concern of this manual. It detects hardware and loads appropriate drivers, uses <classname>dhcp-client</classname> to set up the network connection, and runs <classname>debootstrap</classname> to install the base system packages. Many more actors play smaller parts in this process, but <classname>debian-installer</classname> has completed its task when you load the new system for the first time."
 msgstr ""
 
-#: preparing.xml:169
+#: preparing.xml:157
 #, no-c-format
 #. Tag: para
-msgid "Upon loading the new base system, <classname>base-config</classname> supervises adding users, setting a time zone (via <classname>tzsetup</classname>), and setting up the package installation system (using <classname>apt-setup</classname>). It then launches <classname>tasksel</classname> which can be used to select large groups of related programs, and in turn can run <classname>aptitude</classname> which allows you to choose individual software packages."
+msgid "To tune the system to your needs, <classname>tasksel</classname> allows you to choose to install various predefined bundles of software like a Web server or a Desktop environment."
 msgstr ""
 
-#: preparing.xml:179
+#: preparing.xml:163
 #, no-c-format
 #. Tag: para
-msgid "When <classname>debian-installer</classname> finishes, before the first system load, you have only a very basic command line driven system. The graphical interface which displays windows on your monitor will not be installed unless you select it during the final steps, with either <classname>tasksel</classname> or <classname>aptitude</classname>. It's optional because many &debian; systems are servers which don't really have any need for a graphical user interface to do their job."
+msgid "When <classname>debian-installer</classname> finishes, before the first system load, you have only a very basic command line driven system. The graphical interface which displays windows on your monitor will not be installed unless you select it with <classname>tasksel</classname>. It's optional because many &debian; systems are servers which don't really have any need for a graphical user interface to do their job."
 msgstr ""
 
-#: preparing.xml:190
+#: preparing.xml:172
 #, no-c-format
 #. Tag: para
 msgid "Just be aware that the X system is completely separate from <classname>debian-installer</classname>, and in fact is much more complicated. Installation and trouble shooting of the X window installation is not within the scope of this manual."
 msgstr ""
 
-#: preparing.xml:206
+#: preparing.xml:188
 #, no-c-format
 #. Tag: title
 msgid "Back Up Your Existing Data!"
 msgstr ""
 
-#: preparing.xml:207
+#: preparing.xml:189
 #, no-c-format
 #. Tag: para
 msgid "Before you start, make sure to back up every file that is now on your system. If this is the first time a non-native operating system has been installed on your computer, it's quite likely you will need to re-partition your disk to make room for &debian;. Anytime you partition your disk, you should count on losing everything on the disk, no matter what program you use to do it. The programs used in installation are quite reliable and most have seen years of use; but they are also quite powerful and a false move can cost you. Even after backing up be careful and think about your answers and actions. Two minutes of thinking can save hours of unnecessary work."
 msgstr ""
 
-#: preparing.xml:220
+#: preparing.xml:202
 #, no-c-format
 #. Tag: para
 msgid "If you are creating a multi-boot system, make sure that you have the distribution media of any other present operating systems on hand. Especially if you repartition your boot drive, you might find that you have to reinstall your operating system's boot loader, or in many cases the whole operating system itself and all files on the affected partitions."
 msgstr ""
 
-#: preparing.xml:231
+#: preparing.xml:213
 #, no-c-format
 #. Tag: para
 msgid "With the exception of the BVM and Motorola VMEbus computers, the only supported installation method for m68k systems is booting from a local disk or floppy using an AmigaOS/TOS/MacOS-based bootstrap, for these machines you will need the original operating system in order to boot Linux. In order to boot Linux on the BVM and Motorola VMEbus machines you will need the <quote>BVMBug</quote> or <quote>16xBug</quote> boot ROMs."
 msgstr ""
 
-#: preparing.xml:249
+#: preparing.xml:231
 #, no-c-format
 #. Tag: title
 msgid "Information You Will Need"
 msgstr ""
 
-#: preparing.xml:252
+#: preparing.xml:234
 #, no-c-format
 #. Tag: title
 msgid "Documentation"
 msgstr ""
 
-#: preparing.xml:255
+#: preparing.xml:237
 #, no-c-format
 #. Tag: title
 msgid "Installation Manual"
 msgstr ""
 
-#: preparing.xml:257
+#: preparing.xml:239
 #, no-c-format
 #. Tag: para
 msgid "This document you are now reading, in plain ASCII, HTML or PDF format."
 msgstr ""
 
-#: preparing.xml:263
+#: preparing.xml:245
 #, no-c-format
 #. Tag: itemizedlist
 msgid "&list-install-manual-files;"
 msgstr ""
 
-#: preparing.xml:269
+#: preparing.xml:251
 #, no-c-format
 #. Tag: para
 msgid "The document you are now reading, which is the official version of the Installation Guide for the &releasename; release of Debian; available in <ulink url=\"&url-release-area;/installmanual\">various formats and translations</ulink>."
 msgstr ""
 
-#: preparing.xml:278
+#: preparing.xml:260
 #, no-c-format
 #. Tag: para
 msgid "The document you are now reading, which is a development version of the Installation Guide for the next release of Debian; available in <ulink url=\"&url-d-i-alioth-manual;\">various formats and translations</ulink>."
 msgstr ""
 
-#: preparing.xml:290
+#: preparing.xml:272
 #, no-c-format
 #. Tag: title
 msgid "Hardware documentation"
 msgstr ""
 
-#: preparing.xml:291
+#: preparing.xml:273
 #, no-c-format
 #. Tag: para
 msgid "Often contains useful information on configuring or using your hardware."
 msgstr ""
 
-#: preparing.xml:302
+#: preparing.xml:284
 #, no-c-format
 #. Tag: ulink
 msgid "Linux Hardware Compatibility HOWTO"
 msgstr ""
 
-#: preparing.xml:308
+#: preparing.xml:290
 #, no-c-format
 #. Tag: ulink
 msgid "Linux/m68k FAQ"
 msgstr ""
 
-#: preparing.xml:314
+#: preparing.xml:296
 #, no-c-format
 #. Tag: ulink
 msgid "Linux/Alpha FAQ"
 msgstr ""
 
-#: preparing.xml:320
+#: preparing.xml:302
 #, no-c-format
 #. Tag: ulink
 msgid "Linux for SPARC Processors FAQ"
 msgstr ""
 
-#: preparing.xml:326
+#: preparing.xml:308
 #, no-c-format
 #. Tag: ulink
 msgid "Linux/Mips website"
 msgstr ""
 
-#: preparing.xml:335
+#: preparing.xml:317
 #, no-c-format
 #. Tag: title
 msgid "&arch-title; Hardware References"
 msgstr ""
 
-#: preparing.xml:336
+#: preparing.xml:318
 #, no-c-format
 #. Tag: para
 msgid "Installation instructions and device drivers (DASD, XPRAM, Console, tape, z90 crypto, chandev, network) for Linux on &arch-title; using kernel 2.4"
 msgstr ""
 
-#: preparing.xml:348
+#: preparing.xml:330
 #, no-c-format
 #. Tag: ulink
 msgid "Device Drivers and Installation Commands"
 msgstr ""
 
-#: preparing.xml:353
+#: preparing.xml:335
 #, no-c-format
 #. Tag: para
 msgid "IBM Redbook describing how Linux can be combined with z/VM on zSeries and &arch-title; hardware."
 msgstr ""
 
-#: preparing.xml:363
+#: preparing.xml:345
 #, no-c-format
 #. Tag: ulink
 msgid "Linux for &arch-title;"
 msgstr ""
 
-#: preparing.xml:369
+#: preparing.xml:351
 #, no-c-format
 #. Tag: para
 msgid "IBM Redbook describing the Linux distributions available for the mainframe. It has no chapter about Debian but the basic installation concepts are the same across all &arch-title; distributions."
 msgstr ""
 
-#: preparing.xml:380
+#: preparing.xml:362
 #, no-c-format
 #. Tag: ulink
 msgid "Linux for IBM eServer zSeries and &arch-title;: Distributions"
 msgstr ""
 
-#: preparing.xml:390
+#: preparing.xml:372
 #, no-c-format
 #. Tag: title
 msgid "Finding Sources of Hardware Information"
 msgstr ""
 
-#: preparing.xml:391
+#: preparing.xml:373
 #, no-c-format
 #. Tag: para
 msgid "In many cases, the installer will be able to automatically detect your hardware. But to be prepared, we do recommend familiarizing yourself with your hardware before the install."
 msgstr ""
 
-#: preparing.xml:397
+#: preparing.xml:379
 #, no-c-format
 #. Tag: para
 msgid "Hardware information can be gathered from:"
 msgstr ""
 
-#: preparing.xml:404
+#: preparing.xml:386
 #, no-c-format
 #. Tag: para
 msgid "The manuals that come with each piece of hardware."
 msgstr ""
 
-#: preparing.xml:409
+#: preparing.xml:391
 #, no-c-format
 #. Tag: para
 msgid "The BIOS setup screens of your computer. You can view these screens when you start your computer by pressing a combination of keys. Check your manual for the combination. Often, it is the <keycap>Delete</keycap> key."
 msgstr ""
 
-#: preparing.xml:416
+#: preparing.xml:398
 #, no-c-format
 #. Tag: para
 msgid "The cases and boxes for each piece of hardware."
 msgstr ""
 
-#: preparing.xml:422
+#: preparing.xml:404
 #, no-c-format
 #. Tag: para
 msgid "The System window in the Windows Control Panel."
 msgstr ""
 
-#: preparing.xml:428
+#: preparing.xml:410
 #, no-c-format
 #. Tag: para
 msgid "System commands or tools in another operating system, including file manager displays. This source is especially useful for information about RAM and hard drive memory."
 msgstr ""
 
-#: preparing.xml:435
+#: preparing.xml:417
 #, no-c-format
 #. Tag: para
 msgid "Your system administrator or Internet Service Provider. These sources can tell you the settings you need to set up your networking and e-mail."
 msgstr ""
 
-#: preparing.xml:447
+#: preparing.xml:429
 #, no-c-format
 #. Tag: title
 msgid "Hardware Information Needed for an Install"
 msgstr ""
 
-#: preparing.xml:451
+#: preparing.xml:433
 #, no-c-format
 #. Tag: entry
 msgid "Hardware"
 msgstr ""
 
-#: preparing.xml:451
+#: preparing.xml:433
 #, no-c-format
 #. Tag: entry
 msgid "Information You Might Need"
 msgstr ""
 
-#: preparing.xml:457
+#: preparing.xml:439
 #, no-c-format
 #. Tag: entry
 msgid "Hard Drives"
 msgstr ""
 
-#: preparing.xml:458
+#: preparing.xml:440
 #, no-c-format
 #. Tag: entry
 msgid "How many you have."
 msgstr ""
 
-#: preparing.xml:460
+#: preparing.xml:442
 #, no-c-format
 #. Tag: entry
 msgid "Their order on the system."
 msgstr ""
 
-#: preparing.xml:462
+#: preparing.xml:444
 #, no-c-format
 #. Tag: entry
 msgid "Whether IDE or SCSI (most computers are IDE)."
 msgstr ""
 
-#: preparing.xml:464 preparing.xml:516
+#: preparing.xml:446 preparing.xml:498
 #, no-c-format
 #. Tag: entry
 msgid "Available free space."
 msgstr ""
 
-#: preparing.xml:465
+#: preparing.xml:447
 #, no-c-format
 #. Tag: entry
 msgid "Partitions."
 msgstr ""
 
-#: preparing.xml:467
+#: preparing.xml:449
 #, no-c-format
 #. Tag: entry
 msgid "Partitions where other operating systems are installed."
 msgstr ""
 
-#: preparing.xml:471
+#: preparing.xml:453
 #, no-c-format
 #. Tag: entry
 msgid "Monitor"
 msgstr ""
 
-#: preparing.xml:472 preparing.xml:492 preparing.xml:498 preparing.xml:504
+#: preparing.xml:454 preparing.xml:474 preparing.xml:480 preparing.xml:486
 #, no-c-format
 #. Tag: entry
 msgid "Model and manufacturer."
 msgstr ""
 
-#: preparing.xml:474
+#: preparing.xml:456
 #, no-c-format
 #. Tag: entry
 msgid "Resolutions supported."
 msgstr ""
 
-#: preparing.xml:475
+#: preparing.xml:457
 #, no-c-format
 #. Tag: entry
 msgid "Horizontal refresh rate."
 msgstr ""
 
-#: preparing.xml:476
+#: preparing.xml:458
 #, no-c-format
 #. Tag: entry
 msgid "Vertical refresh rate."
 msgstr ""
 
-#: preparing.xml:478
+#: preparing.xml:460
 #, no-c-format
 #. Tag: entry
 msgid "Color depth (number of colors) supported."
 msgstr ""
 
-#: preparing.xml:480
+#: preparing.xml:462
 #, no-c-format
 #. Tag: entry
 msgid "Screen size."
 msgstr ""
 
-#: preparing.xml:483
+#: preparing.xml:465
 #, no-c-format
 #. Tag: entry
 msgid "Mouse"
 msgstr ""
 
-#: preparing.xml:484
+#: preparing.xml:466
 #, no-c-format
 #. Tag: entry
 msgid "Type: serial, PS/2, or USB."
 msgstr ""
 
-#: preparing.xml:486
+#: preparing.xml:468
 #, no-c-format
 #. Tag: entry
 msgid "Port."
 msgstr ""
 
-#: preparing.xml:487
+#: preparing.xml:469
 #, no-c-format
 #. Tag: entry
 msgid "Manufacturer."
 msgstr ""
 
-#: preparing.xml:488
+#: preparing.xml:470
 #, no-c-format
 #. Tag: entry
 msgid "Number of buttons."
 msgstr ""
 
-#: preparing.xml:491 preparing.xml:519
+#: preparing.xml:473 preparing.xml:501
 #, no-c-format
 #. Tag: entry
 msgid "Network"
 msgstr ""
 
-#: preparing.xml:494 preparing.xml:520
+#: preparing.xml:476 preparing.xml:502
 #, no-c-format
 #. Tag: entry
 msgid "Type of adapter."
 msgstr ""
 
-#: preparing.xml:497
+#: preparing.xml:479
 #, no-c-format
 #. Tag: entry
 msgid "Printer"
 msgstr ""
 
-#: preparing.xml:500
+#: preparing.xml:482
 #, no-c-format
 #. Tag: entry
 msgid "Printing resolutions supported."
 msgstr ""
 
-#: preparing.xml:503
+#: preparing.xml:485
 #, no-c-format
 #. Tag: entry
 msgid "Video Card"
 msgstr ""
 
-#: preparing.xml:506
+#: preparing.xml:488
 #, no-c-format
 #. Tag: entry
 msgid "Video RAM available."
 msgstr ""
 
-#: preparing.xml:508
+#: preparing.xml:490
 #, no-c-format
 #. Tag: entry
 msgid "Resolutions and color depths supported (these should be checked against your monitor's capabilities)."
 msgstr ""
 
-#: preparing.xml:513
+#: preparing.xml:495
 #, no-c-format
 #. Tag: entry
 msgid "DASD"
 msgstr ""
 
-#: preparing.xml:514
+#: preparing.xml:496
 #, no-c-format
 #. Tag: entry
 msgid "Device number(s)."
 msgstr ""
 
-#: preparing.xml:522
+#: preparing.xml:504
 #, no-c-format
 #. Tag: entry
 msgid "Device numbers."
 msgstr ""
 
-#: preparing.xml:523
+#: preparing.xml:505
 #, no-c-format
 #. Tag: entry
 msgid "Relative adapter number for OSA cards."
 msgstr ""
 
-#: preparing.xml:531
+#: preparing.xml:513
 #, no-c-format
 #. Tag: title
 msgid "Hardware Compatibility"
 msgstr ""
 
-#: preparing.xml:533
+#: preparing.xml:515
 #, no-c-format
 #. Tag: para
 msgid "Many brand name products work without trouble on Linux. Moreover, hardware for Linux is improving daily. However, Linux still does not run as many different types of hardware as some operating systems."
 msgstr ""
 
-#: preparing.xml:539
+#: preparing.xml:521
 #, no-c-format
 #. Tag: para
 msgid "In particular, Linux usually cannot run hardware that requires a running version of Windows to work."
 msgstr ""
 
-#: preparing.xml:544
+#: preparing.xml:526
 #, no-c-format
 #. Tag: para
 msgid "Although some Windows-specific hardware can be made to run on Linux, doing so usually requires extra effort. In addition, Linux drivers for Windows-specific hardware are usually specific to one Linux kernel. Therefore, they can quickly become obsolete."
 msgstr ""
 
-#: preparing.xml:551
+#: preparing.xml:533
 #, no-c-format
 #. Tag: para
 msgid "So called win-modems are the most common type of this hardware. However, printers and other equipment may also be Windows-specific."
 msgstr ""
 
-#: preparing.xml:556
+#: preparing.xml:538
 #, no-c-format
 #. Tag: para
 msgid "You can check hardware compatibility by:"
 msgstr ""
 
-#: preparing.xml:561
+#: preparing.xml:543
 #, no-c-format
 #. Tag: para
 msgid "Checking manufacturers' web sites for new drivers."
 msgstr ""
 
-#: preparing.xml:566
+#: preparing.xml:548
 #, no-c-format
 #. Tag: para
 msgid "Looking at web sites or manuals for information about emulation. Lesser known brands can sometimes use the drivers or settings for better-known ones."
 msgstr ""
 
-#: preparing.xml:573
+#: preparing.xml:555
 #, no-c-format
 #. Tag: para
 msgid "Checking hardware compatibility lists for Linux on web sites dedicated to your architecture."
 msgstr ""
 
-#: preparing.xml:579
+#: preparing.xml:561
 #, no-c-format
 #. Tag: para
 msgid "Searching the Internet for other users' experiences."
 msgstr ""
 
-#: preparing.xml:590
+#: preparing.xml:572
 #, no-c-format
 #. Tag: title
 msgid "Network Settings"
 msgstr ""
 
-#: preparing.xml:592
+#: preparing.xml:574
 #, no-c-format
 #. Tag: para
 msgid "If your computer is connected to a network 24 hours a day (i.e., an Ethernet or equivalent connection &mdash; not a PPP connection), you should ask your network's system administrator for this information."
 msgstr ""
 
-#: preparing.xml:599
+#: preparing.xml:581
 #, no-c-format
 #. Tag: para
 msgid "Your host name (you may be able to decide this on your own)."
 msgstr ""
 
-#: preparing.xml:604
+#: preparing.xml:586
 #, no-c-format
 #. Tag: para
 msgid "Your domain name."
 msgstr ""
 
-#: preparing.xml:609
+#: preparing.xml:591
 #, no-c-format
 #. Tag: para
 msgid "Your computer's IP address."
 msgstr ""
 
-#: preparing.xml:614
+#: preparing.xml:596
 #, no-c-format
 #. Tag: para
 msgid "The netmask to use with your network."
 msgstr ""
 
-#: preparing.xml:619
+#: preparing.xml:601
 #, no-c-format
 #. Tag: para
 msgid "The IP address of the default gateway system you should route to, if your network <emphasis>has</emphasis> a gateway."
 msgstr ""
 
-#: preparing.xml:625
+#: preparing.xml:607
 #, no-c-format
 #. Tag: para
 msgid "The system on your network that you should use as a DNS (Domain Name Service) server."
 msgstr ""
 
-#: preparing.xml:633
+#: preparing.xml:615
 #, no-c-format
 #. Tag: para
 msgid "On the other hand, if your administrator tells you that a DHCP server is available and is recommended, then you don't need this information because the DHCP server will provide it directly to your computer during the installation process."
 msgstr ""
 
-#: preparing.xml:640
+#: preparing.xml:622
 #, no-c-format
 #. Tag: para
 msgid "If you use a wireless network, you should also find out:"
 msgstr ""
 
-#: preparing.xml:645
+#: preparing.xml:627
 #, no-c-format
 #. Tag: para
 msgid "ESSID of your wireless network."
 msgstr ""
 
-#: preparing.xml:650
+#: preparing.xml:632
 #, no-c-format
 #. Tag: para
 msgid "WEP security key (if applicable)."
 msgstr ""
 
-#: preparing.xml:667
+#: preparing.xml:649
 #, no-c-format
 #. Tag: title
 msgid "Meeting Minimum Hardware Requirements"
 msgstr ""
 
-#: preparing.xml:668
+#: preparing.xml:650
 #, no-c-format
 #. Tag: para
 msgid "Once you have gathered information about your computer's hardware, check that your hardware will let you do the type of installation that you want to do."
 msgstr ""
 
-#: preparing.xml:674
+#: preparing.xml:656
 #, no-c-format
 #. Tag: para
 msgid "Depending on your needs, you might manage with less than some of the recommended hardware listed in the table below. However, most users risk being frustrated if they ignore these suggestions."
 msgstr ""
 
-#: preparing.xml:680
+#: preparing.xml:662
 #, no-c-format
 #. Tag: para
 msgid "A Pentium 100 is the minimum recommended for desktop systems, and a Pentium II-300 for a Server."
 msgstr ""
 
-#: preparing.xml:685
+#: preparing.xml:667
 #, no-c-format
 #. Tag: para
 msgid "A 68030 or better processor is recommended for m68k installs. You may get by with a little less drive space than shown."
 msgstr ""
 
-#: preparing.xml:690
+#: preparing.xml:672
 #, no-c-format
 #. Tag: para
 msgid "Any OldWorld or NewWorld PowerPC can serve well as a Desktop System. For servers, a minimum 132-Mhz machine is recommended."
 msgstr ""
 
-#: preparing.xml:699
+#: preparing.xml:681
 #, no-c-format
 #. Tag: title
 msgid "Recommended Minimum System Requirements"
 msgstr ""
 
-#: preparing.xml:703
+#: preparing.xml:685
 #, no-c-format
 #. Tag: entry
 msgid "Install Type"
 msgstr ""
 
-#: preparing.xml:703
+#: preparing.xml:685
 #, no-c-format
 #. Tag: entry
 msgid "<entry>RAM</entry>"
 msgstr ""
 
-#: preparing.xml:703
+#: preparing.xml:685
 #, no-c-format
 #. Tag: entry
 msgid "Hard Drive"
 msgstr ""
 
-#: preparing.xml:709
+#: preparing.xml:691
 #, no-c-format
 #. Tag: entry
 msgid "No desktop"
 msgstr ""
 
-#: preparing.xml:710
+#: preparing.xml:692
 #, no-c-format
 #. Tag: entry
 msgid "24 megabytes"
 msgstr ""
 
-#: preparing.xml:711
+#: preparing.xml:693
 #, no-c-format
 #. Tag: entry
 msgid "450 megabytes"
 msgstr ""
 
-#: preparing.xml:713
+#: preparing.xml:695
 #, no-c-format
 #. Tag: entry
 msgid "With Desktop"
 msgstr ""
 
-#: preparing.xml:714
+#: preparing.xml:696
 #, no-c-format
 #. Tag: entry
 msgid "64 megabytes"
 msgstr ""
 
-#: preparing.xml:715
+#: preparing.xml:697
 #, no-c-format
 #. Tag: entry
 msgid "1 gigabyte"
 msgstr ""
 
-#: preparing.xml:717
+#: preparing.xml:699
 #, no-c-format
 #. Tag: entry
 msgid "Server"
 msgstr ""
 
-#: preparing.xml:718
+#: preparing.xml:700
 #, no-c-format
 #. Tag: entry
 msgid "128 megabytes"
 msgstr ""
 
-#: preparing.xml:719
+#: preparing.xml:701
 #, no-c-format
 #. Tag: entry
 msgid "4 gigabytes"
 msgstr ""
 
-#: preparing.xml:724
+#: preparing.xml:706
 #, no-c-format
 #. Tag: para
 msgid "Here is a sampling of some common Debian system configurations. You can also get an idea of the disk space used by related groups of programs by referring to <xref linkend=\"tasksel-size-list\"/>."
 msgstr ""
 
-#: preparing.xml:734
+#: preparing.xml:716
 #, no-c-format
 #. Tag: term
 msgid "Standard Server"
 msgstr ""
 
-#: preparing.xml:735
+#: preparing.xml:717
 #, no-c-format
 #. Tag: para
 msgid "This is a small server profile, useful for a stripped down server which does not have a lot of niceties for shell users. It includes an FTP server, a web server, DNS, NIS, and POP. For these 100MB of disk space would suffice, and then you would need to add space for any data you serve up."
 msgstr ""
 
-#: preparing.xml:747
+#: preparing.xml:729
 #, no-c-format
 #. Tag: term
 msgid "Desktop"
 msgstr ""
 
-#: preparing.xml:748
+#: preparing.xml:730
 #, no-c-format
 #. Tag: para
 msgid "A standard desktop box, including the X window system, full desktop environments, sound, editors, etc. You'll need about 2GB using the standard desktop task, though it can be done in far less."
 msgstr ""
 
-#: preparing.xml:758
+#: preparing.xml:740
 #, no-c-format
 #. Tag: term
 msgid "Work Console"
 msgstr ""
 
-#: preparing.xml:759
+#: preparing.xml:741
 #, no-c-format
 #. Tag: para
 msgid "A more stripped-down user machine, without the X window system or X applications. Possibly suitable for a laptop or mobile computer. The size is around 140MB."
 msgstr ""
 
-#: preparing.xml:769
+#: preparing.xml:751
 #, no-c-format
 #. Tag: term
 msgid "Developer"
 msgstr ""
 
-#: preparing.xml:770
+#: preparing.xml:752
 #, no-c-format
 #. Tag: para
 msgid "A desktop setup with all the development packages, such as Perl, C, C++, etc. Size is around 475MB. Assuming you are adding X11 and some additional packages for other uses, you should plan around 800MB for this type of machine."
 msgstr ""
 
-#: preparing.xml:780
+#: preparing.xml:762
 #, no-c-format
 #. Tag: para
 msgid "Remember that these sizes don't include all the other materials which are usually to be found, such as user files, mail, and data. It is always best to be generous when considering the space for your own files and data. Notably, the <filename>/var</filename> partition contains a lot of state information specific to Debian in addition to its regular contents like logfiles. The <command>dpkg</command> files (with information on all installed packages) can easily consume 20MB. Also, <command>apt-get</command> puts downloaded packages here before they are installed. You should usually allocate at least 100MB for <filename>/var</filename>."
 msgstr ""
 
-#: preparing.xml:804
+#: preparing.xml:786
 #, no-c-format
 #. Tag: title
 msgid "Pre-Partitioning for Multi-Boot Systems"
 msgstr ""
 
-#: preparing.xml:805
+#: preparing.xml:787
 #, no-c-format
 #. Tag: para
 msgid "Partitioning your disk simply refers to the act of breaking up your disk into sections. Each section is then independent of the others. It's roughly equivalent to putting up walls inside a house; if you add furniture to one room it doesn't affect any other room."
 msgstr ""
 
-#: preparing.xml:812
+#: preparing.xml:794
 #, no-c-format
 #. Tag: para
 msgid "Whenever this section talks about <quote>disks</quote> you should translate this into a DASD or VM minidisk in the &arch-title; world. Also a machine means an LPAR or VM guest in this case."
 msgstr ""
 
-#: preparing.xml:818
+#: preparing.xml:800
 #, no-c-format
 #. Tag: para
 msgid "If you already have an operating system on your system <phrase arch=\"i386\"> (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, &hellip;) </phrase> <phrase arch=\"alpha\"> (Tru64 (Digital UNIX), OpenVMS, Windows NT, FreeBSD, &hellip;) </phrase> <phrase arch=\"s390\"> (VM, z/OS, OS/390, &hellip;) </phrase> <phrase arch=\"m68k\"> (Amiga OS, Atari TOS, Mac OS, &hellip;) </phrase> and want to stick Linux on the same disk, you will need to repartition the disk. Debian requires its own hard disk partitions. It cannot be installed on Windows or MacOS partitions. It may be able to share some partitions with other Linux systems, but that's not covered here. At the very least you will need a dedicated partition for the Debian root."
 msgstr ""
 
-#: preparing.xml:845
+#: preparing.xml:827
 #, no-c-format
 #. Tag: para
 msgid "You can find information about your current partition setup by using a partitioning tool for your current operating system<phrase arch=\"i386\">, such as fdisk or PartitionMagic</phrase><phrase arch=\"powerpc\">, such as Drive Setup, HD Toolkit, or MacTools</phrase><phrase arch=\"m68k\">, such as HD SC Setup, HDToolBox, or SCSITool</phrase><phrase arch=\"s390\">, such as the VM diskmap</phrase>. Partitioning tools always provide a way to show existing partitions without making changes."
 msgstr ""
 
-#: preparing.xml:855
+#: preparing.xml:837
 #, no-c-format
 #. Tag: para
 msgid "In general, changing a partition with a file system already on it will destroy any information there. Thus you should always make backups before doing any repartitioning. Using the analogy of the house, you would probably want to move all the furniture out of the way before moving a wall or you risk destroying it."
 msgstr ""
 
-#: preparing.xml:865
+#: preparing.xml:847
 #, no-c-format
 #. Tag: emphasis
 msgid "FIXME: write about HP-UX disks?"
 msgstr ""
 
-#: preparing.xml:867
+#: preparing.xml:849
 #, no-c-format
 #. Tag: para
 msgid "If your computer has more than one hard disk, you may want to dedicate one of the hard disks completely to Debian. If so, you don't need to partition that disk before booting the installation system; the installer's included partitioning program can handle the job nicely."
 msgstr ""
 
-#: preparing.xml:874
+#: preparing.xml:856
 #, no-c-format
 #. Tag: para
 msgid "If your machine has only one hard disk, and you would like to completely replace the current operating system with &debian;, you also can wait to partition as part of the installation process (<xref linkend=\"partman\"/>), after you have booted the installation system. However this only works if you plan to boot the installer system from tapes, CD-ROM or files on a connected machine. Consider: if you boot from files placed on the hard disk, and then partition that same hard disk within the installation system, thus erasing the boot files, you'd better hope the installation is successful the first time around. At the least in this case, you should have some alternate means of reviving your machine like the original system's installation tapes or CDs."
 msgstr ""
 
-#: preparing.xml:889
+#: preparing.xml:871
 #, no-c-format
 #. Tag: para
 msgid "If your machine already has multiple partitions, and enough space can be provided by deleting and replacing one or more of them, then you too can wait and use the Debian installer's partitioning program. You should still read through the material below, because there may be special circumstances like the order of the existing partitions within the partition map, that force you to partition before installing anyway."
 msgstr ""
 
-#: preparing.xml:899
+#: preparing.xml:881
 #, no-c-format
 #. Tag: para
 msgid "If your machine has a FAT or NTFS filesystem, as used by DOS and Windows, you can wait and use Debian installer's partitioning program to resize the filesystem."
 msgstr ""
 
-#: preparing.xml:905
+#: preparing.xml:887
 #, no-c-format
 #. Tag: para
 msgid "If none of the above apply, you'll need to partition your hard disk before starting the installation to create partition-able space for Debian. If some of the partitions will be owned by other operating systems, you should create those partitions using native operating system partitioning programs. We recommend that you do <emphasis>not</emphasis> attempt to create partitions for &debian; using another operating system's tools. Instead, you should just create the native operating system's partitions you will want to retain."
 msgstr ""
 
-#: preparing.xml:917
+#: preparing.xml:899
 #, no-c-format
 #. Tag: para
 msgid "If you are going to install more than one operating system on the same machine, you should install all other system(s) before proceeding with Linux installation. Windows and other OS installations may destroy your ability to start Linux, or encourage you to reformat non-native partitions."
 msgstr ""
 
-#: preparing.xml:925
+#: preparing.xml:907
 #, no-c-format
 #. Tag: para
 msgid "You can recover from these actions or avoid them, but installing the native system first saves you trouble."
 msgstr ""
 
-#: preparing.xml:930
+#: preparing.xml:912
 #, no-c-format
 #. Tag: para
 msgid "In order for OpenFirmware to automatically boot &debian; the Linux partitions should appear before all other partitions on the disk, especially MacOS boot partitions. This should be kept in mind when pre-partitioning; you should create a Linux placeholder partition to come <emphasis>before</emphasis> the other bootable partitions on the disk. (The small partitions dedicated to Apple disk drivers are not bootable.) You can delete the placeholder with the Linux partition tools later during the actual install, and replace it with Linux partitions."
 msgstr ""
 
-#: preparing.xml:942
+#: preparing.xml:924
 #, no-c-format
 #. Tag: para
 msgid "If you currently have one hard disk with one partition (a common setup for desktop computers), and you want to multi-boot the native operating system and Debian, you will need to:"
 msgstr ""
 
-#: preparing.xml:949
+#: preparing.xml:931
 #, no-c-format
 #. Tag: para
 msgid "Back up everything on the computer."
 msgstr ""
 
-#: preparing.xml:954
+#: preparing.xml:936
 #, no-c-format
 #. Tag: para
 msgid "Boot from the native operating system installer media such as CD-ROM or tapes. <phrase arch=\"powerpc\">When booting from a MacOS CD, hold the <keycap>c</keycap> key while booting to force the CD to become the active MacOS system.</phrase>"
 msgstr ""
 
-#: preparing.xml:964
+#: preparing.xml:946
 #, no-c-format
 #. Tag: para
 msgid "Use the native partitioning tools to create native system partition(s). Leave either a place holder partition or free space for &debian;."
 msgstr ""
 
-#: preparing.xml:971
+#: preparing.xml:953
 #, no-c-format
 #. Tag: para
 msgid "Install the native operating system on its new partition."
 msgstr ""
 
-#: preparing.xml:976
+#: preparing.xml:958
 #, no-c-format
 #. Tag: para
 msgid "Boot back into the native system to verify everything's OK, and to download the Debian installer boot files."
 msgstr ""
 
-#: preparing.xml:982
+#: preparing.xml:964
 #, no-c-format
 #. Tag: para
 msgid "Boot the Debian installer to continue installing Debian."
 msgstr ""
 
-#: preparing.xml:996
+#: preparing.xml:978
 #, no-c-format
 #. Tag: title
 msgid "Partitioning in Tru64 UNIX"
 msgstr ""
 
-#: preparing.xml:997
+#: preparing.xml:979
 #, no-c-format
 #. Tag: para
 msgid "Tru64 UNIX, formerly known as Digital UNIX, which is in turn formerly known as OSF/1, uses the partitioning scheme similar to the BSD <quote>disk label</quote>, which allows for up to eight partitions per disk drive. The partitions are numbered <quote>1</quote> through to <quote>8</quote> in Linux and <quote>lettered</quote> <quote>a</quote> through to <quote>h</quote> in UNIX. Linux kernels 2.2 and higher always correspond <quote>1</quote> to <quote>a</quote>, <quote>2</quote> to <quote>b</quote> and so on. For example, <filename>rz0e</filename> in Tru64 UNIX would most likely be called <filename>sda5</filename> in Linux."
 msgstr ""
 
-#: preparing.xml:1009
+#: preparing.xml:991
 #, no-c-format
 #. Tag: para
 msgid "Partitions in a Tru64 disk label may overlap. Moreover, if this disk will be used from Tru64, the <quote>c</quote> partition is required to span the entire disk (thus overlapping all other non-empty partitions). Under Linux this makes <filename>sda3</filename> identical to <filename>sda</filename> (<filename>sdb3</filename> to <filename>sdb</filename>, if present, and so on). However, the partman partitioning tool used by &d-i; cannot handle overlapping partitions at present. As a result, it is currently not recommended to share disks between Tru64 and Debian. Partitions on Tru64 disks can be mounted under Debian after installation has been completed."
 msgstr ""
 
-#: preparing.xml:1022
+#: preparing.xml:1004
 #, no-c-format
 #. Tag: para
 msgid "Another conventional requirement is for the <quote>a</quote> partition to start from the beginning of the disk, so that it always includes the boot block with the disk label. If you intend to boot Debian from that disk, you need to size it at least 2MB to fit aboot and perhaps a kernel. Note that this partition is only required for compatibility; you must not put a file system onto it, or you'll destroy data."
 msgstr ""
 
-#: preparing.xml:1031
+#: preparing.xml:1013
 #, no-c-format
 #. Tag: para
 msgid "It is possible, and indeed quite reasonable, to share a swap partition between UNIX and Linux. In this case it will be needed to do a <command>mkswap</command> on that partition every time the system is rebooted from UNIX into Linux, as UNIX will damage the swap signature. You may want to run <command>mkswap</command> from the Linux start-up scripts before adding swap space with <command>swapon -a</command>."
 msgstr ""
 
-#: preparing.xml:1040
+#: preparing.xml:1022
 #, no-c-format
 #. Tag: para
 msgid "If you want to mount UNIX partitions under Linux, note that Digital UNIX can use two different file system types, UFS and AdvFS, of which Linux only understands the former."
 msgstr ""
 
-#: preparing.xml:1049
+#: preparing.xml:1031
 #, no-c-format
 #. Tag: title
 msgid "Partitioning in Windows NT"
 msgstr ""
 
-#: preparing.xml:1051
+#: preparing.xml:1033
 #, no-c-format
 #. Tag: para
 msgid "Windows NT uses the PC-style partition table. If you are manipulating existing FAT or NTFS partitions, it is recommended that you use the native Windows NT tools (or, more conveniently, you can also repartition your disk from the AlphaBIOS setup menu). Otherwise, it is not really necessary to partition from Windows; the Linux partitioning tools will generally do a better job. Note that when you run NT, the Disk Administrator may offer you to write a <quote>harmless signature</quote> on non-Windows disks if you have any. <emphasis>Never</emphasis> let it do that, as this signature will destroy the partition information."
 msgstr ""
 
-#: preparing.xml:1064
+#: preparing.xml:1046
 #, no-c-format
 #. Tag: para
 msgid "If you plan to boot Linux from an ARC/AlphaBIOS/ARCSBIOS console, you will need a (small) FAT partition for MILO. 5 MB is quite sufficient. If Windows NT is installed, its 6 MB bootstrap partition can be employed for this purpose. Debian &releasename; does not support installing MILO. If you already have MILO installed on your system, or install MILO from other media, Debian can still be booted from ARC."
 msgstr ""
 
-#: preparing.xml:1081
+#: preparing.xml:1063
 #, no-c-format
 #. Tag: title
 msgid "Partitioning From DOS or Windows"
 msgstr ""
 
-#: preparing.xml:1082
+#: preparing.xml:1064
 #, no-c-format
 #. Tag: para
 msgid "If you are manipulating existing FAT or NTFS partitions, it is recommended that you either use the scheme below or native Windows or DOS tools. Otherwise, it is not really necessary to partition from DOS or Windows; the Linux partitioning tools will generally do a better job."
 msgstr ""
 
-#: preparing.xml:1090
+#: preparing.xml:1072
 #, no-c-format
 #. Tag: para
 msgid "But if you have a large IDE disk, and are using neither LBA addressing, overlay drivers (sometimes provided by hard disk manufacturers), nor a new (post 1998) BIOS that supports large disk access extensions, then you must locate your Debian boot partition carefully. In this case, you will have to put the boot partition into the first 1024 cylinders of your hard drive (usually around 524 megabytes, without BIOS translation). This may require that you move an existing FAT or NTFS partition."
 msgstr ""
 
-#: preparing.xml:1104
+#: preparing.xml:1086
 #, no-c-format
 #. Tag: title
 msgid "Lossless Repartitioning When Starting From DOS, Win-32 or OS/2"
 msgstr ""
 
-#: preparing.xml:1107
+#: preparing.xml:1089
 #, no-c-format
 #. Tag: para
 msgid "One of the most common installations is onto a system that already contains DOS (including Windows 3.1), Win32 (such as Windows 95, 98, Me, NT, 2000, XP), or OS/2, and it is desired to put Debian onto the same disk without destroying the previous system. Note that the installer supports resizing of FAT and NTFS filesystems as used by DOS and Windows. Simply start the installer, select the option to <menuchoice> <guimenuitem>Manually edit partition table</guimenuitem> </menuchoice>, select the partition to resize, and specify its new size. So in most cases you should not need to use the method described below."
 msgstr ""
 
-#: preparing.xml:1119
+#: preparing.xml:1101
 #, no-c-format
 #. Tag: para
 msgid "Before going any further, you should have decided how you will be dividing up the disk. The method in this section will only split a partition into two pieces. One will contain the original OS and the other will be used for Debian. During the installation of Debian, you will be given the opportunity to use the Debian portion of the disk as you see fit, i.e., as swap or as a file system."
 msgstr ""
 
-#: preparing.xml:1128
+#: preparing.xml:1110
 #, no-c-format
 #. Tag: para
 msgid "The idea is to move all the data on the partition to the beginning, before changing the partition information, so that nothing will be lost. It is important that you do as little as possible between the data movement and repartitioning to minimize the chance of a file being written near the end of the partition as this will decrease the amount of space you can take from the partition."
 msgstr ""
 
-#: preparing.xml:1137
+#: preparing.xml:1119
 #, no-c-format
 #. Tag: para
 msgid "The first thing needed is a copy of <command>fips</command> which is available in the <filename>tools/</filename> directory on your nearest Debian mirror. Unzip the archive and copy the files <filename>RESTORRB.EXE</filename>, <filename>FIPS.EXE</filename> and <filename>ERRORS.TXT</filename> to a bootable floppy. A bootable floppy can be created using the command <filename>sys a:</filename> under DOS. <command>fips</command> comes with very good documentation which you may want to read. You will definitely need to read the documentation if you use a disk compression driver or a disk manager. Create the disk and read the documentation <emphasis>before</emphasis> you defragment the disk."
 msgstr ""
 
-#: preparing.xml:1150
+#: preparing.xml:1132
 #, no-c-format
 #. Tag: para
 msgid "The next thing needed is to move all the data to the beginning of the partition. <command>defrag</command>, which comes standard with DOS 6.0 and later, can easily do the job. See the <command>fips</command> documentation for a list of other software that may do the trick. Note that if you have Windows 9x, you must run <command>defrag</command> from there, since DOS doesn't understand VFAT, which is used to support for long filenames, used in Windows 95 and higher."
 msgstr ""
 
-#: preparing.xml:1160
+#: preparing.xml:1142
 #, no-c-format
 #. Tag: para
 msgid "After running the defragmenter (which can take a while on a large disk), reboot with the <command>fips</command> disk you created in the floppy drive. Simply type <filename>a:\\fips</filename> and follow the directions."
 msgstr ""
 
-#: preparing.xml:1166
+#: preparing.xml:1148
 #, no-c-format
 #. Tag: para
 msgid "Note that there are many other partition managers out there, in case <command>fips</command> doesn't do the trick for you."
 msgstr ""
 
-#: preparing.xml:1174
+#: preparing.xml:1156
 #, no-c-format
 #. Tag: title
 msgid "Partitioning for DOS"
 msgstr ""
 
-#: preparing.xml:1176
+#: preparing.xml:1158
 #, no-c-format
 #. Tag: para
 msgid "If you are partitioning for DOS drives, or changing the size of DOS partitions, using Linux tools, many people experience problems working with the resulting FAT partitions. For instance, some have reported slow performance, consistent problems with <command>scandisk</command>, or other weird errors in DOS or Windows."
 msgstr ""
 
-#: preparing.xml:1184
+#: preparing.xml:1166
 #, no-c-format
 #. Tag: para
 msgid "Apparently, whenever you create or resize a partition for DOS use, it's a good idea to fill the first few sectors with zeros. Do this prior to running DOS's <command>format</command> command, from Linux:"
 msgstr ""
 
-#: preparing.xml:1190
+#: preparing.xml:1172
 #, no-c-format
 #. Tag: screen
 msgid "# dd if=/dev/zero of=/dev/hdXX bs=512 count=4"
 msgstr ""
 
-#: preparing.xml:1201
+#: preparing.xml:1183
 #, no-c-format
 #. Tag: title
 msgid "Partitioning in AmigaOS"
 msgstr ""
 
-#: preparing.xml:1202
+#: preparing.xml:1184
 #, no-c-format
 #. Tag: para
 msgid "If you are running AmigaOS, you can use the <command>HDToolBox</command> program to adjust your native partitions prior to installation."
 msgstr ""
 
-#: preparing.xml:1210
+#: preparing.xml:1192
 #, no-c-format
 #. Tag: title
 msgid "Partitioning in Atari TOS"
 msgstr ""
 
-#: preparing.xml:1211
+#: preparing.xml:1193
 #, no-c-format
 #. Tag: para
 msgid "Atari partition IDs are three ASCII characters, use <quote>LNX</quote> for data and <quote>SWP</quote> for swap partitions. If using the low memory installation method, a small Minix partition is also needed (about 2 MB), for which the partition ID is <quote>MNX</quote>. Failure to set the appropriate partition IDs not only prevents the Debian installation process from recognizing the partitions, but also results in TOS attempting to use the Linux partitions, which confuses the hard disk driver and renders the whole disk inaccessible."
 msgstr ""
 
-#: preparing.xml:1222
+#: preparing.xml:1204
 #, no-c-format
 #. Tag: para
 msgid "There are a multitude of third party partitioning tools available (the Atari <command>harddisk</command> utility doesn't permit changing the partition ID); this manual cannot give detailed descriptions for all of them. The following description covers <command>SCSITool</command> (from Hard+Soft GmBH)."
 msgstr ""
 
-#: preparing.xml:1231
+#: preparing.xml:1213
 #, no-c-format
 #. Tag: para
 msgid "Start <command>SCSITool</command> and select the disk you want to partition (<guimenu>Disk</guimenu> menu, item <guimenuitem>select</guimenuitem>)."
 msgstr ""
 
-#: preparing.xml:1237
+#: preparing.xml:1219
 #, no-c-format
 #. Tag: para
 msgid "From the <guimenu>Partition</guimenu> menu, select either <guimenuitem>New</guimenuitem> to add new partitions or change the existing partition sizes, or <guimenuitem>Change</guimenuitem> to change one specific partition. Unless you have already created partitions with the right sizes and only want to change the partition ID, <guimenuitem>New</guimenuitem> is probably the best choice."
 msgstr ""
 
-#: preparing.xml:1247
+#: preparing.xml:1229
 #, no-c-format
 #. Tag: para
 msgid "For the <guimenuitem>New</guimenuitem> choice, select <guilabel>existing</guilabel> in the dialog box prompting the initial settings. The next window shows a list of existing partitions which you can adjust using the scroll buttons, or by clicking in the bar graphs. The first column in the partition list is the partition type; just click on the text field to edit it. When you are finished changing partition settings, save the changes by leaving the window with the <guibutton>OK</guibutton> button."
 msgstr ""
 
-#: preparing.xml:1259
+#: preparing.xml:1241
 #, no-c-format
 #. Tag: para
 msgid "For the <guimenuitem>Change</guimenuitem> option, select the partition to change in the selection list, and select <guilabel>other systems</guilabel> in the dialog box. The next window lists detailed information about the location of this partition, and lets you change the partition ID. Save changes by leaving the window with the <guibutton>OK</guibutton> button."
 msgstr ""
 
-#: preparing.xml:1269
+#: preparing.xml:1251
 #, no-c-format
 #. Tag: para
 msgid "Write down the Linux names for each of the partitions you created or changed for use with Linux &mdash; see <xref linkend=\"device-names\"/>."
 msgstr ""
 
-#: preparing.xml:1275
+#: preparing.xml:1257
 #, no-c-format
 #. Tag: para
 msgid "Quit <command>SCSITool</command> using the <guimenuitem>Quit</guimenuitem> item from the <guimenu>File</guimenu> menu. The computer will reboot to make sure the changed partition table is used by TOS. If you changed any TOS/GEM partitions, they will be invalidated and have to be reinitialized (we told you to back up everything on the disk, didn't we?)."
 msgstr ""
 
-#: preparing.xml:1287
+#: preparing.xml:1269
 #, no-c-format
 #. Tag: para
 msgid "There is a partitioning tool for Linux/m68k called <command>atari-fdisk</command> in the installation system, but for now we recommend you partition your disk using a TOS partition editor or some disk tool. If your partition editor doesn't have an option to edit the partition type, you can do this crucial step at a later stage (from the booted temporary install RAMdisk). <command>SCSITool</command> is only one of the partition editors we know of which supports selection of arbitrary partition types. There may be others; select the tool that suits your needs."
 msgstr ""
 
-#: preparing.xml:1302
+#: preparing.xml:1284
 #, no-c-format
 #. Tag: title
 msgid "Partitioning in MacOS"
 msgstr ""
 
-#: preparing.xml:1303
+#: preparing.xml:1285
 #, no-c-format
 #. Tag: para
 msgid "Partitioning tools for Macintosh tested include <command>pdisk</command>, <command>HD SC Setup</command> 7.3.5 (Apple), <command>HDT</command> 1.8 (FWB), <command>SilverLining</command> (LaCie), and <command>DiskTool</command> (Tim Endres, GPL). Full versions are required for <command>HDT</command> and <command>SilverLining</command>. The Apple tool requires a patch in order to recognize third-party disks (a description on how to patch <command>HD SC Setup</command> using <command>ResEdit</command> can be found at <ulink url=\"http://www.euronet.nl/users/ernstoud/patch.html\"></ulink>)."
 msgstr ""
 
-#: preparing.xml:1314
+#: preparing.xml:1296
 #, no-c-format
 #. Tag: para
 msgid "For IDE based Macs, you need to use <command>Apple Drive Setup</command> to create empty space for the Linux partitions, and complete the partitioning under Linux, or use the MacOS version of pdisk available from the MkLinux FTP server."
 msgstr ""
 
-#: preparing.xml:1330
+#: preparing.xml:1312
 #, no-c-format
 #. Tag: title
 msgid "Partitioning from SunOS"
 msgstr ""
 
-#: preparing.xml:1332
+#: preparing.xml:1314
 #, no-c-format
 #. Tag: para
 msgid "It's perfectly fine to partition from SunOS; in fact, if you intend to run both SunOS and Debian on the same machine, it is recommended that you partition using SunOS prior to installing Debian. The Linux kernel understands Sun disk labels, so there are no problems there. Just make sure you leave room for the Debian root partition within the first 1GB area of the boot disk. You can also place the kernel image on a UFS partition if that is easier than putting the root partition there. SILO supports booting Linux and SunOS from either EXT2 (Linux), UFS (SunOS), romfs and iso9660 (CDROM) partitions."
 msgstr ""
 
-#: preparing.xml:1347
+#: preparing.xml:1329
 #, no-c-format
 #. Tag: title
 msgid "Partitioning from Linux or another OS"
 msgstr ""
 
-#: preparing.xml:1349
+#: preparing.xml:1331
 #, no-c-format
 #. Tag: para
 msgid "Whatever system you are using to partition, 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. In <command>fdisk</command>, the <keycap>s</keycap> key is used to create Sun disk labels. You only need to do this on drives that do not already have a Sun disk label. If you are using a drive that was previously formatted using a PC (or other architecture) you must create a new disk label, or problems with the disk geometry will most likely occur."
 msgstr ""
 
-#: preparing.xml:1361
+#: preparing.xml:1343
 #, no-c-format
 #. Tag: para
 msgid "You will probably be using <command>SILO</command> as your boot loader (the small program which runs the operating system kernel). <command>SILO</command> has certain requirements for partition sizes and location; see <xref linkend=\"partitioning\"/>."
 msgstr ""
 
-#: preparing.xml:1376
+#: preparing.xml:1358
 #, no-c-format
 #. Tag: title
 msgid "MacOS/OSX Partitioning"
 msgstr ""
 
-#: preparing.xml:1378
+#: preparing.xml:1360
 #, no-c-format
 #. Tag: para
 msgid "The <application>Apple Drive Setup</application> application can be found in the <filename>Utilities</filename> folder on the MacOS CD. It will not adjust existing partitions; it is limited to partitioning the entire disk at once. The disk driver partitions don't show up in <application>Drive Setup</application>."
 msgstr ""
 
-#: preparing.xml:1385
+#: preparing.xml:1367
 #, no-c-format
 #. Tag: para
 msgid "Remember to create a placeholder partition for GNU/Linux, preferably positioned first in the disk layout. it doesn't matter what type it is, it will be deleted and replaced later inside the &debian; installer."
 msgstr ""
 
-#: preparing.xml:1391
+#: preparing.xml:1373
 #, no-c-format
 #. Tag: para
 msgid "If you are planning to install both MacOS 9 and OS X, it is best to create separate partitions for OS 9 and OS X. If they are installed on the same partition, <application>Startup Disk</application> (and reboot) must be used to select between the two; the choice between the two systems can't be made at boot time. With separate partitions, separate options for OS 9 and OS X will appear when holding the <keycap>option</keycap> key at boot time, and separate options can be installed in the <application>yaboot</application> boot menu as well. Also, Startup Disk will de-bless all other mountable partitions, which can affect GNU/Linux booting. Both OS 9 and OS X partitions will be accessible from either OS 9 or OS X."
 msgstr ""
 
-#: preparing.xml:1404
+#: preparing.xml:1386
 #, no-c-format
 #. Tag: para
 msgid "GNU/Linux is unable to access information on UFS partitions, but does support HFS+ (aka MacOS Extended) partitions. OS X requires one of these two types for its boot partition. MacOS 9 can be installed on either HFS (aka MacOS Standard) or HFS+. To share information between the MacOS and GNU/Linux systems, an exchange partition is handy. HFS, HFS+ and MS-DOS FAT partitions are supported by both MacOS and Linux."
 msgstr ""
 
-#: preparing.xml:1424
+#: preparing.xml:1406
 #, no-c-format
 #. Tag: title
 msgid "Pre-Installation Hardware and Operating System Setup"
 msgstr ""
 
-#: preparing.xml:1425
+#: preparing.xml:1407
 #, no-c-format
 #. Tag: para
 msgid "This section will walk you through pre-installation hardware setup, if any, that you will need to do prior to installing Debian. Generally, this involves checking and possibly changing firmware settings for your system. The <quote>firmware</quote> is the core software used by the hardware; it is most critically invoked during the bootstrap process (after power-up). Known hardware issues affecting the reliability of &debian; on your system are also highlighted."
 msgstr ""
 
-#: preparing.xml:1442
+#: preparing.xml:1424
 #, no-c-format
 #. Tag: title
 msgid "Invoking the BIOS Set-Up Menu"
 msgstr ""
 
-#: preparing.xml:1444
+#: preparing.xml:1426
 #, no-c-format
 #. Tag: para
 msgid "BIOS provides the basic functions needed to boot your machine to allow your operating system to access your hardware. Your system probably provides a BIOS set-up menu, which is used to configure the BIOS. Before installing, you <emphasis>must</emphasis> ensure that your BIOS is setup correctly; not doing so can lead to intermittent crashes or an inability to install Debian."
 msgstr ""
 
-#: preparing.xml:1453
+#: preparing.xml:1435
 #, no-c-format
 #. Tag: para
 msgid "The rest of this section is lifted from the <ulink url=\"&url-pc-hw-faq;\"></ulink>, answering the question, <quote>How do I enter the CMOS configuration menu?</quote>. How you access the BIOS (or <quote>CMOS</quote>) configuration menu depends on who wrote your BIOS software:"
 msgstr ""
 
-#: preparing.xml:1467
+#: preparing.xml:1449
 #, no-c-format
 #. Tag: term
 msgid "AMI BIOS"
 msgstr ""
 
-#: preparing.xml:1468
+#: preparing.xml:1450
 #, no-c-format
 #. Tag: para
 msgid "<keycap>Delete</keycap> key during the POST (power on self test)"
 msgstr ""
 
-#: preparing.xml:1476
+#: preparing.xml:1458
 #, no-c-format
 #. Tag: term
 msgid "Award BIOS"
 msgstr ""
 
-#: preparing.xml:1477
+#: preparing.xml:1459
 #, no-c-format
 #. Tag: para
 msgid "<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap> </keycombo>, or <keycap>Delete</keycap> key during the POST"
 msgstr ""
 
-#: preparing.xml:1486
+#: preparing.xml:1468
 #, no-c-format
 #. Tag: term
 msgid "DTK BIOS"
 msgstr ""
 
-#: preparing.xml:1487
+#: preparing.xml:1469
 #, no-c-format
 #. Tag: para
 msgid "<keycap>Esc</keycap> key during the POST"
 msgstr ""
 
-#: preparing.xml:1494
+#: preparing.xml:1476
 #, no-c-format
 #. Tag: term
 msgid "IBM PS/2 BIOS"
 msgstr ""
 
-#: preparing.xml:1495
+#: preparing.xml:1477
 #, no-c-format
 #. Tag: para
 msgid "<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Insert</keycap> </keycombo> after <keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Delete</keycap> </keycombo>"
 msgstr ""
 
-#: preparing.xml:1509
+#: preparing.xml:1491
 #, no-c-format
 #. Tag: term
 msgid "Phoenix BIOS"
 msgstr ""
 
-#: preparing.xml:1510
+#: preparing.xml:1492
 #, no-c-format
 #. Tag: para
 msgid "<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap> </keycombo> or <keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>S</keycap> </keycombo> or <keycap>F1</keycap>"
 msgstr ""
 
-#: preparing.xml:1526
+#: preparing.xml:1508
 #, no-c-format
 #. Tag: para
 msgid "Information on invoking other BIOS routines can be found in <ulink url=\"&url-invoking-bios-info;\"></ulink>."
 msgstr ""
 
-#: preparing.xml:1531
+#: preparing.xml:1513
 #, no-c-format
 #. Tag: para
 msgid "Some &arch-title; machines don't have a CMOS configuration menu in the BIOS. They require a software CMOS setup program. If you don't have the Installation and/or Diagnostics diskette for your machine, you can try using a shareware/freeware program. Try looking in <ulink url=\"&url-simtel;\"></ulink>."
 msgstr ""
 
-#: preparing.xml:1542 preparing.xml:1885
+#: preparing.xml:1524 preparing.xml:1867
 #, no-c-format
 #. Tag: title
 msgid "Boot Device Selection"
 msgstr ""
 
-#: preparing.xml:1544
+#: preparing.xml:1526
 #, no-c-format
 #. Tag: para
 msgid "Many BIOS set-up menus allow you to select the devices that will be used to bootstrap the system. Set this to look for a bootable operating system on <filename>A:</filename> (the first floppy disk), then optionally the first CD-ROM device (possibly appearing as <filename>D:</filename> or <filename>E:</filename>), and then from <filename>C:</filename> (the first hard disk). This setting enables you to boot from either a floppy disk or a CD-ROM, which are the two most common boot devices used to install Debian."
 msgstr ""
 
-#: preparing.xml:1555
+#: preparing.xml:1537
 #, no-c-format
 #. Tag: para
 msgid "If you have a newer SCSI controller and you have a CD-ROM device attached to it, you are usually able to boot from the CD-ROM. All you have to do is enable booting from a CD-ROM in the SCSI-BIOS of your controller."
 msgstr ""
 
-#: preparing.xml:1562
+#: preparing.xml:1544
 #, no-c-format
 #. Tag: para
 msgid "Other popular option is to boot from a USB storage (also called USB memory stick or USB key). Some BIOSes can boot USB storage directly, and some cannot. You may need to configure your BIOS to boot from a <quote>Removable drive</quote> or even a <quote>USB-ZIP</quote> to get it to boot from the USB device."
 msgstr ""
 
-#: preparing.xml:1570
+#: preparing.xml:1552
 #, no-c-format
 #. Tag: para
 msgid "Here are some details about how to set the boot order. Remember to reset the boot order after Linux is installed, so that you restart your machine from the hard drive."
 msgstr ""
 
-#: preparing.xml:1579
+#: preparing.xml:1561
 #, no-c-format
 #. Tag: title
 msgid "Changing the Boot Order on IDE Computers"
 msgstr ""
 
-#: preparing.xml:1582
+#: preparing.xml:1564
 #, no-c-format
 #. Tag: para
 msgid "As your computer starts, press the keys to enter the BIOS utility. Often, it is the <keycap>Delete</keycap> key. However, consult the hardware documentation for the exact keystrokes."
 msgstr ""
 
-#: preparing.xml:1589
+#: preparing.xml:1571
 #, no-c-format
 #. Tag: para
 msgid "Find the boot sequence in the setup utility. Its location depends on your BIOS, but you are looking for a field that lists drives."
 msgstr ""
 
-#: preparing.xml:1594
+#: preparing.xml:1576
 #, no-c-format
 #. Tag: para
 msgid "Common entries on IDE machines are C, A, cdrom or A, C, cdrom."
 msgstr ""
 
-#: preparing.xml:1599
+#: preparing.xml:1581
 #, no-c-format
 #. Tag: para
 msgid "C is the hard drive, and A is the floppy drive."
 msgstr ""
 
-#: preparing.xml:1605
+#: preparing.xml:1587
 #, no-c-format
 #. Tag: para
 msgid "Change the boot sequence setting so that the CD-ROM or the floppy is first. Usually, the <keycap>Page Up</keycap> or <keycap>Page Down</keycap> keys cycle through the possible choices."
 msgstr ""
 
-#: preparing.xml:1613
+#: preparing.xml:1595
 #, no-c-format
 #. Tag: para
 msgid "Save your changes. Instructions on the screen tell you how to save the changes on your computer."
 msgstr ""
 
-#: preparing.xml:1623
+#: preparing.xml:1605
 #, no-c-format
 #. Tag: title
 msgid "Changing the Boot Order on SCSI Computers"
 msgstr ""
 
-#: preparing.xml:1627
+#: preparing.xml:1609
 #, no-c-format
 #. Tag: para
 msgid "As your computer starts, press the keys to enter the SCSI setup utility."
 msgstr ""
 
-#: preparing.xml:1632
+#: preparing.xml:1614
 #, no-c-format
 #. Tag: para
 msgid "You can start the SCSI setup utility after the memory check and the message about how to start the BIOS utility displays when you start your computer."
 msgstr ""
 
-#: preparing.xml:1638
+#: preparing.xml:1620
 #, no-c-format
 #. Tag: para
 msgid "The keystrokes you need depend on the utility. Often, it is <keycombo><keycap>Ctrl</keycap><keycap>F2</keycap></keycombo>. However, consult your hardware documentation for the exact keystrokes."
 msgstr ""
 
-#: preparing.xml:1646
+#: preparing.xml:1628
 #, no-c-format
 #. Tag: para
 msgid "Find the utility for changing the boot order."
 msgstr ""
 
-#: preparing.xml:1651
+#: preparing.xml:1633
 #, no-c-format
 #. Tag: para
 msgid "Set the utility so that the SCSI ID of the CD drive is first on the list."
 msgstr ""
 
-#: preparing.xml:1657
+#: preparing.xml:1639
 #, no-c-format
 #. Tag: para
 msgid "Save your changes. Instructions on the screen tell you how to save the changes on your computer. Often, you must press <keycap>F10</keycap>."
 msgstr ""
 
-#: preparing.xml:1671
+#: preparing.xml:1653
 #, no-c-format
 #. Tag: title
 msgid "Miscellaneous BIOS Settings"
 msgstr ""
 
-#: preparing.xml:1673
+#: preparing.xml:1655
 #, no-c-format
 #. Tag: title
 msgid "CD-ROM Settings"
 msgstr ""
 
-#: preparing.xml:1674
+#: preparing.xml:1656
 #, no-c-format
 #. Tag: para
 msgid "Some BIOS systems (such as Award BIOS) allow you to automatically set the CD speed. You should avoid that, and instead set it to, say, the lowest speed. If you get <userinput>seek failed</userinput> error messages, this may be your problem."
 msgstr ""
 
-#: preparing.xml:1684
+#: preparing.xml:1666
 #, no-c-format
 #. Tag: title
 msgid "Extended vs. Expanded Memory"
 msgstr ""
 
-#: preparing.xml:1685
+#: preparing.xml:1667
 #, no-c-format
 #. Tag: para
 msgid "If your system provides both ex<emphasis>ten</emphasis>ded and ex<emphasis>pan</emphasis>ded memory, set it so that there is as much extended and as little expanded memory as possible. Linux requires extended memory and cannot use expanded memory."
 msgstr ""
 
-#: preparing.xml:1695
+#: preparing.xml:1677
 #, no-c-format
 #. Tag: title
 msgid "Virus Protection"
 msgstr ""
 
-#: preparing.xml:1696
+#: preparing.xml:1678
 #, no-c-format
 #. Tag: para
 msgid "Disable any virus-warning features your BIOS may provide. If you have a virus-protection board or other special hardware, make sure it is disabled or physically removed while running GNU/Linux. These aren't compatible with GNU/Linux; moreover, due to the file system permissions and protected memory of the Linux kernel, viruses are almost unheard of<footnote> <para> After installation you can enable Boot Sector protection if you want. This offers no additional security in Linux but if you also run Windows it may prevent a catastrophe. There is no need to tamper with the Master Boot Record (MBR) after the boot manager has been set up. </para> </footnote>."
 msgstr ""
 
-#: preparing.xml:1717
+#: preparing.xml:1699
 #, no-c-format
 #. Tag: title
 msgid "Shadow RAM"
 msgstr ""
 
-#: preparing.xml:1718
+#: preparing.xml:1700
 #, no-c-format
 #. Tag: para
 msgid "Your motherboard may provide <emphasis>shadow RAM</emphasis> or BIOS caching. You may see settings for <quote>Video BIOS Shadow</quote>, <quote>C800-CBFF Shadow</quote>, etc. <emphasis>Disable</emphasis> all shadow RAM. Shadow RAM is used to accelerate access to the ROMs on your motherboard and on some of the controller cards. Linux does not use these ROMs once it has booted because it provides its own faster 32-bit software in place of the 16-bit programs in the ROMs. Disabling the shadow RAM may make some of it available for programs to use as normal memory. Leaving the shadow RAM enabled may interfere with Linux access to hardware devices."
 msgstr ""
 
-#: preparing.xml:1735
+#: preparing.xml:1717
 #, no-c-format
 #. Tag: title
 msgid "Memory Hole"
 msgstr ""
 
-#: preparing.xml:1736
+#: preparing.xml:1718
 #, no-c-format
 #. Tag: para
 msgid "If your BIOS offers something like <quote>15&ndash;16 MB Memory Hole</quote>, please disable that. Linux expects to find memory there if you have that much RAM."
 msgstr ""
 
-#: preparing.xml:1742
+#: preparing.xml:1724
 #, no-c-format
 #. Tag: para
 msgid "We have a report of an Intel Endeavor motherboard on which there is an option called <quote>LFB</quote> or <quote>Linear Frame Buffer</quote>. This had two settings: <quote>Disabled</quote> and <quote>1 Megabyte</quote>. Set it to <quote>1 Megabyte</quote>. When disabled, the installation floppy was not read correctly, and the system eventually crashed. At this writing we don't understand what's going on with this particular device &mdash; it just worked with that setting and not without it."
 msgstr ""
 
-#: preparing.xml:1758
+#: preparing.xml:1740
 #, no-c-format
 #. Tag: title
 msgid "Advanced Power Management"
 msgstr ""
 
-#: preparing.xml:1759
+#: preparing.xml:1741
 #, no-c-format
 #. Tag: para
 msgid "If your motherboard provides Advanced Power Management (APM), configure it so that power management is controlled by APM. Disable the doze, standby, suspend, nap, and sleep modes, and disable the hard disk's power-down timer. Linux can take over control of these modes, and can do a better job of power-management than the BIOS."
 msgstr ""
 
-#: preparing.xml:1777
+#: preparing.xml:1759
 #, no-c-format
 #. Tag: title
 msgid "Firmware Revisions and Existing OS Setup"
 msgstr ""
 
-#: preparing.xml:1779
+#: preparing.xml:1761
 #, no-c-format
 #. Tag: para
 msgid "&arch-title; machines are generally self-configuring and do not require firmware configuration. However, you should make sure that you have the appropriate ROM and system patches. On the Macintosh, MacOS version >= 7.1 is recommended because version 7.0.1 contains a bug in the video drivers preventing the boot loader from deactivating the video interrupts, resulting in a boot hang. On the BVM VMEbus systems you should make sure you are using BVMBug revision G or higher boot ROMs. The BVMBug boot ROMs do not come as standard on the BVM systems but are available from BVM on request free of charge."
 msgstr ""
 
-#: preparing.xml:1802
+#: preparing.xml:1784
 #, no-c-format
 #. Tag: title
 msgid "Invoking OpenFirmware"
 msgstr ""
 
-#: preparing.xml:1803
+#: preparing.xml:1785
 #, no-c-format
 #. Tag: para
 msgid "There is normally no need to set up the BIOS (called OpenFirmware) on &arch-title; systems. PReP and CHRP are equipped with OpenFirmware, but unfortunately, the means you use to invoke it vary from manufacturer to manufacturer. You'll have to consult the hardware documentation which came with your machine."
 msgstr ""
 
-#: preparing.xml:1811
+#: preparing.xml:1793
 #, no-c-format
 #. Tag: para
 msgid "On &arch-title; Macintoshes, you invoke OpenFirmware with <keycombo><keycap>Command</keycap> <keycap>option</keycap> <keycap>O</keycap> <keycap>F</keycap></keycombo> while booting. Generally it will check for these keystrokes after the chime, but the exact timing varies from model to model. See <ulink url=\"&url-netbsd-powerpc-faq;\"></ulink> for more hints."
 msgstr ""
 
-#: preparing.xml:1820
+#: preparing.xml:1802
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1656,43 +1650,43 @@ msgid ""
       "</screen></informalexample> Note that on older model &arch-title; Macs, the default and sometimes hardwired I/O for OpenFirmware user interaction is through the serial (modem) port. If you invoke OpenFirmware on one of these machines, you will just see a black screen. In that case, a terminal program running on another computer, connected to the modem port, is needed to interact with OpenFirmware."
 msgstr ""
 
-#: preparing.xml:1833
+#: preparing.xml:1815
 #, no-c-format
 #. Tag: para
 msgid "The OpenFirmware on OldWorld Beige G3 machines, OF versions 2.0f1 and 2.4, is broken. These machines will most likely not be able to boot from the hard drive unless the firmware is patched. A firmware patch is included in the <application>System Disk 2.3.1</application> utility, available from Apple at <ulink url=\"ftp://ftp.apple.com/developer/macosxserver/utilities/SystemDisk2.3.1.smi.bin\"></ulink>. After unpacking the utility in MacOS, and launching it, select the Save button to have the firmware patches installed to nvram."
 msgstr ""
 
-#: preparing.xml:1852
+#: preparing.xml:1834
 #, no-c-format
 #. Tag: title
 msgid "Invoking OpenBoot"
 msgstr ""
 
-#: preparing.xml:1854
+#: preparing.xml:1836
 #, no-c-format
 #. Tag: para
 msgid "OpenBoot provides the basic functions needed to boot the &arch-title; architecture. This is rather similar in function to the BIOS in the x86 architecture, although much nicer. The Sun boot PROMs have a built-in forth interpreter which lets you do quite a number of things with your machine, such as diagnostics, simple scripts, etc."
 msgstr ""
 
-#: preparing.xml:1862
+#: preparing.xml:1844
 #, no-c-format
 #. Tag: para
 msgid "To get to the boot prompt you need to hold down the <keycap>Stop</keycap> key (on older type 4 keyboards, use the <keycap>L1</keycap> key, if you have a PC keyboard adapter, use the <keycap>Break</keycap> key) and press the <keycap>A</keycap> key. The boot PROM will give you a prompt, either <userinput>ok</userinput> or <userinput>&gt;</userinput>. It is preferred to have the <userinput>ok</userinput> prompt. So if you get the old style prompt, hit the <keycap>n</keycap> key to get the new style prompt."
 msgstr ""
 
-#: preparing.xml:1874
+#: preparing.xml:1856
 #, no-c-format
 #. Tag: para
 msgid "If you are using a serial console, send a break to the machine. With Minicom, use <keycap>Ctrl-A F</keycap>, with cu, hit <keycap>Enter</keycap>, then type <userinput>%~break</userinput>. Consult the documentation of your terminal emulator if you are using a different program."
 msgstr ""
 
-#: preparing.xml:1887
+#: preparing.xml:1869
 #, no-c-format
 #. Tag: para
 msgid "You can use OpenBoot to boot from specific devices, and also to change your default boot device. However, you need to know some details about how OpenBoot names devices; it's much different from Linux device naming, described in <xref linkend=\"device-names\"/>. Also, the command will vary a bit, depending on what version of OpenBoot you have. More information about OpenBoot can be found in the <ulink url=\"&url-openboot;\">Sun OpenBoot Reference</ulink>."
 msgstr ""
 
-#: preparing.xml:1897
+#: preparing.xml:1879
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1703,7 +1697,7 @@ msgid ""
       "</screen></informalexample>. In older revisions of OpenBoot, device naming is a bit different: the floppy device is called <quote>/fd</quote>, and SCSI disk devices are of the form <quote>sd(<replaceable>controller</replaceable>, <replaceable>disk-target-id</replaceable>, <replaceable>disk-lun</replaceable>)</quote>. The command <userinput>show-devs</userinput> in newer OpenBoot revisions is useful for viewing the currently configured devices. For full information, whatever your revision, see the <ulink url=\"&url-openboot;\">Sun OpenBoot Reference</ulink>."
 msgstr ""
 
-#: preparing.xml:1920
+#: preparing.xml:1902
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1712,193 +1706,193 @@ msgid ""
       "</screen></informalexample> and under Solaris:"
 msgstr ""
 
-#: preparing.xml:1939
+#: preparing.xml:1921
 #, no-c-format
 #. Tag: screen
 msgid "eeprom boot-device=disk1:1"
 msgstr ""
 
-#: preparing.xml:1949
+#: preparing.xml:1931
 #, no-c-format
 #. Tag: title
 msgid "BIOS Setup"
 msgstr ""
 
-#: preparing.xml:1950
+#: preparing.xml:1932
 #, no-c-format
 #. Tag: para
 msgid "In order to install &debian; on a &arch-title; or zSeries machine you have first boot a kernel into the system. The boot mechanism of this platform is inherently different to other ones, especially from PC-like systems: there are no floppy devices available at all. You will notice another big difference while you work with this platform: most (if not all) of the time you will work remote, with the help of some client session software like telnet, or a browser. This is due to that special system architecture where the 3215/3270 console is line-based instead of character-based."
 msgstr ""
 
-#: preparing.xml:1962
+#: preparing.xml:1944
 #, no-c-format
 #. Tag: para
 msgid "Linux on this platform runs either natively on the bare machine, in a so-called LPAR (Logical Partition) or in a virtual machine supplied by the VM system. You can use a boot tape on all of those systems; you may use some other boot media, too, but those may not be generally available. For example, you can use the virtual card reader of a virtual machine, or boot from the HMC (Hardware Management Console) of an LPAR if the HMC and this option is available for you."
 msgstr ""
 
-#: preparing.xml:1972
+#: preparing.xml:1954
 #, no-c-format
 #. Tag: para
 msgid "Before you actually perform an installation, you have to go over some design and preparation steps. IBM has made documentation available about the whole process, e.g. how to prepare an installation medium and how actually boot from that medium. Duplicating that information here is neither possible nor necessary. However, we will describe here which kind of Debian-specific data is needed and where do you find them. Based on both sources of information you have to prepare your machine and the installation medium and to perform a boot from it. When you see the welcome message in your client session join this document again for the Debian-specific installation steps."
 msgstr ""
 
-#: preparing.xml:1989
+#: preparing.xml:1971
 #, no-c-format
 #. Tag: title
 msgid "Native and LPAR installations"
 msgstr ""
 
-#: preparing.xml:1990
+#: preparing.xml:1972
 #, no-c-format
 #. Tag: para
 msgid "Please refer to chapter 5 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf\"> Linux for &arch-title;</ulink> Redbook and chapter 3.2 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and &arch-title;: Distributions</ulink> Redbook on how to set up an LPAR for Linux."
 msgstr ""
 
-#: preparing.xml:2004
+#: preparing.xml:1986
 #, no-c-format
 #. Tag: title
 msgid "Installation as a VM guest"
 msgstr ""
 
-#: preparing.xml:2006
+#: preparing.xml:1988
 #, no-c-format
 #. Tag: para
 msgid "Please refer to chapter 6 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf\"> Linux for &arch-title;</ulink> Redbook and chapter 3.1 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and &arch-title;: Distributions</ulink> Redbook on how to set up a VM guest for running Linux."
 msgstr ""
 
-#: preparing.xml:2016
+#: preparing.xml:1998
 #, no-c-format
 #. Tag: para
 msgid "You need to copy all the files from the <filename>generic</filename> sub-directory to your CMS disk. Be sure to transfer <filename>kernel.debian</filename> and <filename>initrd.debian</filename> in binary mode with a fixed record length of 80 characters."
 msgstr ""
 
-#: preparing.xml:2028
+#: preparing.xml:2010
 #, no-c-format
 #. Tag: title
 msgid "Setting up an installation server"
 msgstr ""
 
-#: preparing.xml:2030
+#: preparing.xml:2012
 #, no-c-format
 #. Tag: para
 msgid "If you don't have a connection to the Internet (either directly or via a web proxy) you need to create a local installation server that can be accessed from your S/390. This server keeps all the packages you want to install and must make them available using NFS, HTTP or FTP."
 msgstr ""
 
-#: preparing.xml:2038
+#: preparing.xml:2020
 #, no-c-format
 #. Tag: para
 msgid "The installation server needs to copy the exact directory structure from any &debian; mirror but of only the s390 and architecture-independent files are required. You can also copy the contents of all installation CDs into such a directory tree."
 msgstr ""
 
-#: preparing.xml:2047
+#: preparing.xml:2029
 #, no-c-format
 #. Tag: emphasis
 msgid "FIXME: more information needed &mdash; from a Redbook?"
 msgstr ""
 
-#: preparing.xml:2053
+#: preparing.xml:2035
 #, no-c-format
 #. Tag: title
 msgid "Hardware Issues to Watch Out For"
 msgstr ""
 
-#: preparing.xml:2054
+#: preparing.xml:2036
 #, no-c-format
 #. Tag: para
 msgid "Many people have tried operating their 90 MHz CPU at 100 MHz, etc. It sometimes works, but is sensitive to temperature and other factors and can actually damage your system. One of the authors of this document over-clocked his own system for a year, and then the system started aborting the <command>gcc</command> program with an unexpected signal while it was compiling the operating system kernel. Turning the CPU speed back down to its rated value solved the problem."
 msgstr ""
 
-#: preparing.xml:2064
+#: preparing.xml:2046
 #, no-c-format
 #. Tag: para
 msgid "The <command>gcc</command> compiler is often the first thing to die from bad memory modules (or other hardware problems that change data unpredictably) because it builds huge data structures that it traverses repeatedly. An error in these data structures will cause it to execute an illegal instruction or access a non-existent address. The symptom of this will be <command>gcc</command> dying from an unexpected signal."
 msgstr ""
 
-#: preparing.xml:2074
+#: preparing.xml:2056
 #, no-c-format
 #. Tag: para
 msgid "Atari TT RAM boards are notorious for RAM problems under Linux; if you encounter any strange problems, try running at least the kernel in ST-RAM. Amiga users may need to exclude RAM using a booter memfile. <phrase condition=\"FIXME\"><emphasis> FIXME: more description of this needed. </emphasis></phrase>"
 msgstr ""
 
-#: preparing.xml:2086
+#: preparing.xml:2068
 #, no-c-format
 #. Tag: para
 msgid "The very best motherboards support parity RAM and will actually tell you if your system has a single-bit error in RAM. Unfortunately, they don't have a way to fix the error, thus they generally crash immediately after they tell you about the bad RAM. Still, it's better to be told you have bad memory than to have it silently insert errors in your data. Thus, the best systems have motherboards that support parity and true-parity memory modules; see <xref linkend=\"Parity-RAM\"/>."
 msgstr ""
 
-#: preparing.xml:2097
+#: preparing.xml:2079
 #, no-c-format
 #. Tag: para
 msgid "If you do have true-parity RAM and your motherboard can handle it, be sure to enable any BIOS settings that cause the motherboard to interrupt on memory parity errors."
 msgstr ""
 
-#: preparing.xml:2105
+#: preparing.xml:2087
 #, no-c-format
 #. Tag: title
 msgid "The Turbo Switch"
 msgstr ""
 
-#: preparing.xml:2106
+#: preparing.xml:2088
 #, no-c-format
 #. Tag: para
 msgid "Many systems have a <emphasis>turbo</emphasis> switch that controls the speed of the CPU. Select the high-speed setting. If your BIOS allows you to disable software control of the turbo switch (or software control of CPU speed), do so and lock the system in high-speed mode. We have one report that on a particular system, while Linux is auto-probing (looking for hardware devices) it can accidentally touch the software control for the turbo switch."
 msgstr ""
 
-#: preparing.xml:2119
+#: preparing.xml:2101
 #, no-c-format
 #. Tag: title
 msgid "Cyrix CPUs and Floppy Disk Errors"
 msgstr ""
 
-#: preparing.xml:2120
+#: preparing.xml:2102
 #, no-c-format
 #. Tag: para
 msgid "Many users of Cyrix CPUs have had to disable the cache in their systems during installation, because the floppy disk has errors if they do not. If you have to do this, be sure to re-enable your cache when you are finished with installation, as the system runs <emphasis>much</emphasis> slower with the cache disabled."
 msgstr ""
 
-#: preparing.xml:2128
+#: preparing.xml:2110
 #, no-c-format
 #. Tag: para
 msgid "We don't think this is necessarily the fault of the Cyrix CPU. It may be something that Linux can work around. We'll continue to look into the problem. For the technically curious, we suspect a problem with the cache being invalid after a switch from 16-bit to 32-bit code."
 msgstr ""
 
-#: preparing.xml:2138
+#: preparing.xml:2120
 #, no-c-format
 #. Tag: title
 msgid "Peripheral Hardware Settings"
 msgstr ""
 
-#: preparing.xml:2139
+#: preparing.xml:2121
 #, no-c-format
 #. Tag: para
 msgid "You may have to change some settings or jumpers on your computer's peripheral cards. Some cards have setup menus, while others rely on jumpers. This document cannot hope to provide complete information on every hardware device; what it hopes to provide is useful tips."
 msgstr ""
 
-#: preparing.xml:2146
+#: preparing.xml:2128
 #, no-c-format
 #. Tag: para
 msgid "If any cards provide <quote>mapped memory</quote>, the memory should be mapped somewhere between 0xA0000 and 0xFFFFF (from 640K to just below 1 megabyte) or at an address at least 1 megabyte greater than the total amount of RAM in your system."
 msgstr ""
 
-#: preparing.xml:2157
+#: preparing.xml:2139
 #, no-c-format
 #. Tag: title
 msgid "USB BIOS support and keyboards"
 msgstr ""
 
-#: preparing.xml:2158
+#: preparing.xml:2140
 #, no-c-format
 #. Tag: para
 msgid "If you have no AT-style keyboard and only a USB model, you may need to enable legacy AT keyboard emulation in your BIOS setup. Only do this if the installation system fails to use your keyboard in USB mode. Conversely, for some systems (especially laptops) you may need to disable legacy USB support if your keyboard does not respond. Consult your main board manual and look in the BIOS for <quote>Legacy keyboard emulation</quote> or <quote>USB keyboard support</quote> options."
 msgstr ""
 
-#: preparing.xml:2171
+#: preparing.xml:2153
 #, no-c-format
 #. Tag: title
 msgid "More than 64 MB RAM"
 msgstr ""
 
-#: preparing.xml:2172
+#: preparing.xml:2154
 #, no-c-format
 #. Tag: para
 msgid "The Linux Kernel cannot always detect what amount of RAM you have. If this is the case please look at <xref linkend=\"boot-parms\"/>."
diff --git a/po/pot/preseed.pot b/po/pot/preseed.pot
index 83dd82f80..17e10f6ff 100644
--- a/po/pot/preseed.pot
+++ b/po/pot/preseed.pot
@@ -6,7 +6,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2005-12-03 10:27+0000\n"
+"POT-Creation-Date: 2006-01-03 19:55+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"
@@ -26,7 +26,7 @@ msgstr ""
 msgid "This appendix explains the intricacies of preseeding answers to questions in &d-i; to automate your installation."
 msgstr ""
 
-#: preseed.xml:23 preseed.xml:411
+#: preseed.xml:23 preseed.xml:398
 #, no-c-format
 #. Tag: para
 msgid "The configuration fragments used in this appendix are also available as an example preseed file from &urlset-example-preseed;."
@@ -41,184 +41,166 @@ msgstr ""
 #: preseed.xml:32
 #, no-c-format
 #. Tag: para
-msgid "Preseeding provides a way to set answers to questions without having to manually enter the answers while the installation is running. This makes it possible to fully automate most types of installation and even offers some features not available during normal installations."
+msgid "Preseeding provides a way to set answers to questions asked during the installation process, without having to manually enter the answers while the installation is running. This makes it possible to fully automate most types of installation and even offers some features not available during normal installations."
 msgstr ""
 
-#: preseed.xml:39
-#, no-c-format
-#. Tag: para
-msgid "Using preseeding it is possible to fill in answers to questions asked during both the first stage of the installation (before the reboot into the new system) and the second stage."
-msgstr ""
-
-#: preseed.xml:48
+#: preseed.xml:43
 #, no-c-format
 #. Tag: title
 msgid "Preseeding methods"
 msgstr ""
 
-#: preseed.xml:49
+#: preseed.xml:44
 #, no-c-format
 #. Tag: para
 msgid "There are three methods that can be used for preseeding: <firstterm>initrd</firstterm>, <firstterm>file</firstterm> and <firstterm>network</firstterm>. Initrd preseeding will work with any installation method and supports preseeding of more things, but it requires the most preparation. File and network preseeding each can be used with different installation methods. With file and network preseeding the first few installer questions cannot be preseeded because the preseed configuration file is only loaded after they have been asked."
 msgstr ""
 
-#: preseed.xml:60
+#: preseed.xml:55
 #, no-c-format
 #. Tag: para
 msgid "The following table shows which preseeding methods can be used with which installation methods."
 msgstr ""
 
-#: preseed.xml:69
+#: preseed.xml:64
 #, no-c-format
 #. Tag: entry
 msgid "Installation method"
 msgstr ""
 
-#: preseed.xml:69
+#: preseed.xml:64
 #, no-c-format
 #. Tag: entry
 msgid "initrd"
 msgstr ""
 
-#: preseed.xml:70
+#: preseed.xml:65
 #, no-c-format
 #. Tag: entry
 msgid "file"
 msgstr ""
 
-#: preseed.xml:70
+#: preseed.xml:65
 #, no-c-format
 #. Tag: entry
 msgid "network"
 msgstr ""
 
-#: preseed.xml:76
+#: preseed.xml:71
 #, no-c-format
 #. Tag: entry
 msgid "CD/DVD"
 msgstr ""
 
-#: preseed.xml:77 preseed.xml:78 preseed.xml:82 preseed.xml:84 preseed.xml:87 preseed.xml:88 preseed.xml:92 preseed.xml:93 preseed.xml:97 preseed.xml:99 preseed.xml:102 preseed.xml:104
+#: preseed.xml:72 preseed.xml:73 preseed.xml:77 preseed.xml:79 preseed.xml:82 preseed.xml:83 preseed.xml:87 preseed.xml:88 preseed.xml:92 preseed.xml:94 preseed.xml:97 preseed.xml:99
 #, no-c-format
 #. Tag: entry
 msgid "<entry>yes</entry>"
 msgstr ""
 
-#: preseed.xml:79 preseed.xml:83 preseed.xml:89 preseed.xml:94 preseed.xml:98 preseed.xml:103
+#: preseed.xml:74 preseed.xml:78 preseed.xml:84 preseed.xml:89 preseed.xml:93 preseed.xml:98
 #, no-c-format
 #. Tag: entry
 msgid "<entry>no</entry>"
 msgstr ""
 
-#: preseed.xml:81
+#: preseed.xml:76
 #, no-c-format
 #. Tag: entry
 msgid "netboot"
 msgstr ""
 
-#: preseed.xml:86
+#: preseed.xml:81
 #, no-c-format
 #. Tag: entry
 msgid "hd-media <phrase condition=\"bootable-usb\">(including usb-stick)</phrase>"
 msgstr ""
 
-#: preseed.xml:91
+#: preseed.xml:86
 #, no-c-format
 #. Tag: entry
 msgid "floppy based (cd-drivers)"
 msgstr ""
 
-#: preseed.xml:96
+#: preseed.xml:91
 #, no-c-format
 #. Tag: entry
 msgid "floppy based (net-drivers)"
 msgstr ""
 
-#: preseed.xml:101
+#: preseed.xml:96
 #, no-c-format
 #. Tag: entry
 msgid "generic/tape"
 msgstr ""
 
-#: preseed.xml:110
+#: preseed.xml:105
 #, no-c-format
 #. Tag: para
 msgid "An important difference between the preseeding methods is the point at which the preseed configuration file is loaded and processed. For initrd preseeding this is right at the start of the installation, before the first question is even asked. For file preseeding this is after the CD or CD image has been loaded. For network preseeding it is only after the network has been configured."
 msgstr ""
 
-#: preseed.xml:119
+#: preseed.xml:114
 #, no-c-format
 #. Tag: para
 msgid "In practical terms this means for file and network preseeding that the questions about language, country and keyboard selection will already have been asked. For network preseeding add to that any questions related to network configuration. Some other questions that are only displayed at medium or low priority (like the first hardware detection run) will also already have been processed."
 msgstr ""
 
-#: preseed.xml:128
+#: preseed.xml:123
 #, no-c-format
 #. Tag: para
 msgid "Obviously, any questions that have been processed before the preseeding configuration file is loaded, cannot be preseeded. <xref linkend=\"preseed-bootparms\"/> offers a way to avoid these questions being asked."
 msgstr ""
 
-#: preseed.xml:139
+#: preseed.xml:134
 #, no-c-format
 #. Tag: title
 msgid "Limitations"
 msgstr ""
 
-#: preseed.xml:140
+#: preseed.xml:135
 #, no-c-format
 #. Tag: para
 msgid "Although most questions used by &d-i; can be preseeded using this method, there are some notable exceptions. You must (re)partition an entire disk or use available free space on a disk; it is not possible to use existing partitions. You currently cannot use preseeding to set up RAID and LVM."
 msgstr ""
 
-#: preseed.xml:212
+#: preseed.xml:207
 #, no-c-format
 #. Tag: title
 msgid "Running custom commands during the installation"
 msgstr ""
 
-#: preseed.xml:213
+#: preseed.xml:208
 #, no-c-format
 #. Tag: para
 msgid "A very powerfull and flexible option offered by the preseeding tools is the ability to run commands or scripts at certain points in the installation. See <xref linkend=\"preseed-shell\"/> for details."
 msgstr ""
 
-#: preseed.xml:222
+#: preseed.xml:217
 #, no-c-format
 #. Tag: para
 msgid "<userinput>preseed/early_command</userinput>: is run as soon as the the preseeding configuration file has been loaded"
 msgstr ""
 
-#: preseed.xml:226
+#: preseed.xml:221
 #, no-c-format
 #. Tag: para
-msgid "<userinput>preseed/late_command</userinput>: is run just before the reboot at the end of the first stage of the installation, but before the <filename>/target</filename> filesystem has been unmounted"
+msgid "<userinput>preseed/late_command</userinput>: is run just before the reboot at the end of the install, but before the <filename>/target</filename> filesystem has been unmounted"
 msgstr ""
 
 #: preseed.xml:231
 #, no-c-format
-#. Tag: para
-msgid "<userinput>base-config/early_command</userinput>: is run early in the second stage of the installation when <command>base-config</command> is starting up"
-msgstr ""
-
-#: preseed.xml:235
-#, no-c-format
-#. Tag: para
-msgid "<userinput>base-config/late_command</userinput>: is run at the end of <command>base-config</command>, just before the login prompt"
-msgstr ""
-
-#: preseed.xml:244
-#, no-c-format
 #. Tag: title
 msgid "Using preseeding to change default values"
 msgstr ""
 
-#: preseed.xml:245
+#: preseed.xml:232
 #, no-c-format
 #. Tag: para
 msgid "It is possible to use preseeding to change the default answer for a question, but still have the question asked. To do this the <firstterm>seen</firstterm> flag must be reset to <quote>false</quote> after setting the value for a template."
 msgstr ""
 
-#: preseed.xml:254
+#: preseed.xml:241
 #, no-c-format
 #. Tag: screen
 msgid ""
@@ -226,55 +208,55 @@ msgid ""
       "d-i foo/bar seen false"
 msgstr ""
 
-#: preseed.xml:260
+#: preseed.xml:247
 #, no-c-format
 #. Tag: title
 msgid "Using preseeding"
 msgstr ""
 
-#: preseed.xml:261
+#: preseed.xml:248
 #, no-c-format
 #. Tag: para
 msgid "Of course you will first need to create a preseed file and place it in the location from where you want to use it. Creating the preseed file is covered later in this appendix. Putting it in the correct location is fairly straightforward for network preseeding or if you want to read the file off a floppy or usb-stick. If you want to include the file on a CD or DVD, you will have to remaster the ISO image. How to get the preseed file included in the initrd is outside the scope of this document; please consult the developers documentation for &d-i;."
 msgstr ""
 
-#: preseed.xml:272
+#: preseed.xml:259
 #, no-c-format
 #. Tag: para
 msgid "An example preseed file that you can use as basis for your preseed file is available from &urlset-example-preseed;. This file is based on the configuration fragments included in this appendix."
 msgstr ""
 
-#: preseed.xml:281
+#: preseed.xml:268
 #, no-c-format
 #. Tag: title
 msgid "Loading the preseed file"
 msgstr ""
 
-#: preseed.xml:282
+#: preseed.xml:269
 #, no-c-format
 #. Tag: para
 msgid "If you are using initrd preseeding, you only have to make sure a file named <filename>preseed.cfg</filename> is included in the root directory of the initrd. The installer will automatically check if this file is present and load it."
 msgstr ""
 
-#: preseed.xml:289
+#: preseed.xml:276
 #, no-c-format
 #. Tag: para
 msgid "For the other preseeding methods you need to tell the installer what file to use when you boot it. This is done by passing the kernel a boot parameter, either manually at boot time or by editing the bootloader configuration file (e.g. <filename>syslinux.cfg</filename>) and adding the parameter to the end of the append line(s) for the kernel."
 msgstr ""
 
-#: preseed.xml:297
+#: preseed.xml:284
 #, no-c-format
 #. Tag: para
 msgid "If you do specify the preseed file in the bootloader configuration, you might change the configuration so you don't need to hit enter to boot the installer. For syslinux this means setting the timeout to 1 in <filename>syslinux.cfg</filename>."
 msgstr ""
 
-#: preseed.xml:304
+#: preseed.xml:291
 #, no-c-format
 #. Tag: para
 msgid "To make sure the installer gets the right preseed file, you can optionally specify a checksum for the file. Currently this needs to be a md5sum, and if specified it must match the preseed file or the installer will refuse to use it."
 msgstr ""
 
-#: preseed.xml:312
+#: preseed.xml:299
 #, no-c-format
 #. Tag: screen
 msgid ""
@@ -293,139 +275,139 @@ msgid ""
       "  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d"
 msgstr ""
 
-#: preseed.xml:314
+#: preseed.xml:301
 #, no-c-format
 #. Tag: para
 msgid "While you're at it, you may want to add a boot parameter <userinput>debconf/priority=critical</userinput>. This will avoid most questions even if the preseeding below misses some."
 msgstr ""
 
-#: preseed.xml:324
+#: preseed.xml:311
 #, no-c-format
 #. Tag: title
 msgid "Using boot parameters to supplement preseeding"
 msgstr ""
 
-#: preseed.xml:325
+#: preseed.xml:312
 #, no-c-format
 #. Tag: para
 msgid "Some parts of the installation process cannot be automated using some forms of preseeding because the questions are asked before the preseed file is loaded. For example, if the preseed file is downloaded over the network, the network setup must be done first. One reason to use initrd preseeding is that it allows preseeding of even these early steps of the installation process."
 msgstr ""
 
-#: preseed.xml:334
+#: preseed.xml:321
 #, no-c-format
 #. Tag: para
 msgid "If a preseed file cannot be used to preseed some steps, the install can still be fully automated, since you can pass preseed values to the kernel on the command line. Just pass <userinput>path/to/var=value</userinput> for any of the preseed variables listed in the examples."
 msgstr ""
 
-#: preseed.xml:342
+#: preseed.xml:329
 #, no-c-format
 #. Tag: para
 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."
 msgstr ""
 
-#: preseed.xml:351
+#: preseed.xml:338
 #, no-c-format
 #. Tag: para
 msgid "For most installations some of the default options in your bootloader configuration file, like 'vga=normal', may be safely removed which may allow you to add more options for preseeding."
 msgstr ""
 
-#: preseed.xml:358
+#: preseed.xml:345
 #, no-c-format
 #. Tag: para
 msgid "It may not always be possible to specify values with spaces for boot parameters, even if you delimit them with quotes."
 msgstr ""
 
-#: preseed.xml:368
+#: preseed.xml:355
 #, no-c-format
 #. Tag: title
 msgid "Creating a preseed file"
 msgstr ""
 
-#: preseed.xml:369
+#: preseed.xml:356
 #, no-c-format
 #. Tag: para
 msgid "The preconfiguration file is in the format used by the <command>debconf-set-selections</command> command."
 msgstr ""
 
-#: preseed.xml:377
+#: preseed.xml:364
 #, no-c-format
 #. Tag: para
 msgid "File format"
 msgstr ""
 
-#: preseed.xml:380
+#: preseed.xml:367
 #, no-c-format
 #. Tag: para
 msgid "Only single space allowed between template type and value"
 msgstr ""
 
-#: preseed.xml:383
+#: preseed.xml:370
 #, no-c-format
 #. Tag: para
 msgid "Relation with /var/lib/(c)debconf/templates"
 msgstr ""
 
-#: preseed.xml:386
+#: preseed.xml:373
 #, no-c-format
 #. Tag: para
 msgid "Types of templates and how to provide values for them"
 msgstr ""
 
-#: preseed.xml:389
+#: preseed.xml:376
 #, no-c-format
 #. Tag: para
 msgid "Most values need to be in English or codes"
 msgstr ""
 
-#: preseed.xml:392
+#: preseed.xml:379
 #, no-c-format
 #. Tag: para
 msgid "Using a manual installation as base"
 msgstr ""
 
-#: preseed.xml:395
+#: preseed.xml:382
 #, no-c-format
 #. Tag: para
 msgid "Finding other possible values"
 msgstr ""
 
-#: preseed.xml:400
+#: preseed.xml:387
 #, no-c-format
 #. Tag: para
 msgid "To check if the format of your preseed file is valid before performing an install, you can use the command <command>debconf-set-selections -c <replaceable>preseed.cfg</replaceable></command>."
 msgstr ""
 
-#: preseed.xml:410
+#: preseed.xml:397
 #, no-c-format
 #. Tag: title
-msgid "Preseeding the first stage of the installation"
+msgid "Contents of the preseed file"
 msgstr ""
 
-#: preseed.xml:416
+#: preseed.xml:403
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: preseed.xml:427
+#: preseed.xml:414
 #, no-c-format
 #. Tag: title
 msgid "Localization"
 msgstr ""
 
-#: preseed.xml:428
+#: preseed.xml:415
 #, no-c-format
 #. Tag: para
 msgid "Setting localization values will only work if you are using initrd preseeding. With all other methods the preseed file will only be loaded after these questions have been asked."
 msgstr ""
 
-#: preseed.xml:434
+#: preseed.xml:421
 #, no-c-format
 #. Tag: para
 msgid "The locale can be used to specify both language and country. To specify the locale as a boot parameter, use <userinput>debian-installer/locale=<replaceable>en_US</replaceable></userinput>."
 msgstr ""
 
-#: preseed.xml:440
+#: preseed.xml:427
 #, no-c-format
 #. Tag: screen
 msgid ""
@@ -433,13 +415,13 @@ msgid ""
       "d-i debian-installer/locale string en_US"
 msgstr ""
 
-#: preseed.xml:442
+#: preseed.xml:429
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: preseed.xml:449
+#: preseed.xml:436
 #, no-c-format
 #. Tag: screen
 msgid ""
@@ -450,31 +432,31 @@ msgid ""
       "#d-i console-keymaps-usb/keymap select mac-usb-us"
 msgstr ""
 
-#: preseed.xml:451
+#: preseed.xml:438
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: preseed.xml:460
+#: preseed.xml:447
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: preseed.xml:470
+#: preseed.xml:457
 #, no-c-format
 #. Tag: title
 msgid "Network configuration"
 msgstr ""
 
-#: preseed.xml:471
+#: preseed.xml:458
 #, no-c-format
 #. Tag: para
 msgid "Of course, preseeding the network configuration won't work if you're loading your preseed file from the network. But it's great when you're booting from CD or USB stick. If you are loading preseed files from the network, you can pass network config parameters in using kernel boot parameters."
 msgstr ""
 
-#: preseed.xml:481
+#: preseed.xml:468
 #, no-c-format
 #. Tag: screen
 msgid ""
@@ -506,31 +488,31 @@ msgid ""
       "#d-i netcfg/dhcp_hostname string radish"
 msgstr ""
 
-#: preseed.xml:486
+#: preseed.xml:473
 #, no-c-format
 #. Tag: title
 msgid "Mirror settings"
 msgstr ""
 
-#: preseed.xml:487
+#: preseed.xml:474
 #, no-c-format
 #. Tag: para
 msgid "Depending on the installation method you use, a mirror may 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 ""
 
-#: preseed.xml:494
+#: preseed.xml:481
 #, no-c-format
 #. Tag: para
 msgid "The parameter <classname>mirror/suite</classname> determines the suite for the installed system."
 msgstr ""
 
-#: preseed.xml:499
+#: preseed.xml:486
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: preseed.xml:511
+#: preseed.xml:498
 #, no-c-format
 #. Tag: screen
 msgid ""
@@ -545,25 +527,25 @@ msgid ""
       "#d-i mirror/udeb/suite string testing"
 msgstr ""
 
-#: preseed.xml:516
+#: preseed.xml:503
 #, no-c-format
 #. Tag: title
 msgid "Partitioning"
 msgstr ""
 
-#: preseed.xml:517
+#: preseed.xml:504
 #, no-c-format
 #. Tag: para
 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 preseed file. It is currently not possible to partition multiple disks using preseeding nor to set up RAID or LVM."
 msgstr ""
 
-#: preseed.xml:529
+#: preseed.xml:516
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: preseed.xml:537
+#: preseed.xml:524
 #, no-c-format
 #. Tag: screen
 msgid ""
@@ -617,13 +599,13 @@ msgid ""
       "d-i partman/confirm boolean true"
 msgstr ""
 
-#: preseed.xml:542
+#: preseed.xml:529
 #, no-c-format
 #. Tag: title
 msgid "Clock and time zone setup"
 msgstr ""
 
-#: preseed.xml:544
+#: preseed.xml:531
 #, no-c-format
 #. Tag: screen
 msgid ""
@@ -635,46 +617,49 @@ msgid ""
       "d-i time/zone string US/Eastern"
 msgstr ""
 
-#: preseed.xml:549
+#: preseed.xml:536
 #, no-c-format
 #. Tag: title
 msgid "Apt setup"
 msgstr ""
 
-#: preseed.xml:550
+#: preseed.xml:537
 #, no-c-format
 #. Tag: para
-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. Only the two variables below are relevant for preseeding."
+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. Only the three variables below are relevant for preseeding."
 msgstr ""
 
-#: preseed.xml:558
+#: preseed.xml:545
 #, no-c-format
 #. Tag: screen
 msgid ""
       "# You can choose to install non-free and contrib software.\n"
       "#d-i apt-setup/non-free boolean true\n"
-      "#d-i apt-setup/contrib boolean true"
+      "#d-i apt-setup/contrib boolean true\n"
+      "# To avoid adding security sources, or to use a different server\n"
+      "# than security.debian.org.\n"
+      "#d-i apt-setup/security_host string"
 msgstr ""
 
-#: preseed.xml:563
+#: preseed.xml:550
 #, no-c-format
 #. Tag: title
 msgid "Account setup"
 msgstr ""
 
-#: preseed.xml:564
+#: preseed.xml:551
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: preseed.xml:571
+#: preseed.xml:558
 #, no-c-format
 #. Tag: para
 msgid "Be aware that preseeding passwords is not completely secure as everyone with access to the preseed 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 ""
 
-#: preseed.xml:581
+#: preseed.xml:568
 #, no-c-format
 #. Tag: screen
 msgid ""
@@ -697,31 +682,31 @@ msgid ""
       "#passwd passwd/user-password-crypted password [MD5 hash]"
 msgstr ""
 
-#: preseed.xml:583
+#: preseed.xml:570
 #, no-c-format
 #. Tag: para
 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 alternate method is setup to allow administrative activities or root login (for instance by using SSH key authentication or sudo)."
 msgstr ""
 
-#: preseed.xml:593
+#: preseed.xml:580
 #, no-c-format
 #. Tag: para
 msgid "An MD5 hash for a password can be generated using the following command."
 msgstr ""
 
-#: preseed.xml:597
+#: preseed.xml:584
 #, no-c-format
 #. Tag: screen
 msgid "$ echo \"r00tme\" | mkpasswd -s -H MD5"
 msgstr ""
 
-#: preseed.xml:603
+#: preseed.xml:590
 #, no-c-format
 #. Tag: title
 msgid "Boot loader installation"
 msgstr ""
 
-#: preseed.xml:605
+#: preseed.xml:592
 #, no-c-format
 #. Tag: screen
 msgid ""
@@ -744,155 +729,123 @@ msgid ""
       "#d-i grub-installer/with_other_os boolean false"
 msgstr ""
 
-#: preseed.xml:610
-#, no-c-format
-#. Tag: title
-msgid "Finishing up the first stage install"
-msgstr ""
-
-#: preseed.xml:612
-#, no-c-format
-#. Tag: screen
-msgid ""
-      "# Avoid that last message about the install being complete.\n"
-      "d-i prebaseconfig/reboot_in_progress note\n"
-      "\n"
-      "# This will prevent the installer from ejecting the CD during the reboot,\n"
-      "# which is useful in some situations.\n"
-      "#d-i cdrom-detect/eject boolean false"
-msgstr ""
-
-#: preseed.xml:618
-#, no-c-format
-#. Tag: title
-msgid "Preseeding the second stage of the installation"
-msgstr ""
-
-#: preseed.xml:621
-#, no-c-format
-#. Tag: title
-msgid "Base config"
-msgstr ""
-
-#: preseed.xml:623
-#, no-c-format
-#. Tag: screen
-msgid ""
-      "# Avoid the introductory message.\n"
-      "base-config base-config/intro note\n"
-      "\n"
-      "# Avoid the final message.\n"
-      "base-config base-config/login note\n"
-      "\n"
-      "# If you installed a display manager, but don't want to start it immediately\n"
-      "# after base-config finishes.\n"
-      "#base-config base-config/start-display-manager boolean false\n"
-      "\n"
-      "# Some versions of the installer can report back on what you've installed.\n"
-      "# The default is not to report back, but sending reports helps the project\n"
-      "# determine what software is most popular and include it on CDs.\n"
-      "#popularity-contest popularity-contest/participate boolean false"
-msgstr ""
-
-#: preseed.xml:628
+#: preseed.xml:597
 #, no-c-format
 #. Tag: title
 msgid "Package selection"
 msgstr ""
 
-#: preseed.xml:629
+#: preseed.xml:598
 #, no-c-format
 #. Tag: para
 msgid "You can choose to install any combination of tasks that are available. Available tasks as of this writing include:"
 msgstr ""
 
-#: preseed.xml:638
+#: preseed.xml:607
 #, no-c-format
 #. Tag: userinput
 msgid "Standard system"
 msgstr ""
 
-#: preseed.xml:641
+#: preseed.xml:610
 #, no-c-format
 #. Tag: userinput
 msgid "Desktop environment"
 msgstr ""
 
-#: preseed.xml:644
+#: preseed.xml:613
 #, no-c-format
 #. Tag: userinput
 msgid "Web server"
 msgstr ""
 
-#: preseed.xml:647
+#: preseed.xml:616
 #, no-c-format
 #. Tag: userinput
 msgid "Print server"
 msgstr ""
 
-#: preseed.xml:650
+#: preseed.xml:619
 #, no-c-format
 #. Tag: userinput
 msgid "DNS server"
 msgstr ""
 
-#: preseed.xml:653
+#: preseed.xml:622
 #, no-c-format
 #. Tag: userinput
 msgid "File server"
 msgstr ""
 
-#: preseed.xml:656
+#: preseed.xml:625
 #, no-c-format
 #. Tag: userinput
 msgid "Mail server"
 msgstr ""
 
-#: preseed.xml:659
+#: preseed.xml:628
 #, no-c-format
 #. Tag: userinput
 msgid "SQL database"
 msgstr ""
 
-#: preseed.xml:662
+#: preseed.xml:631
 #, no-c-format
 #. Tag: userinput
 msgid "Laptop"
 msgstr ""
 
-#: preseed.xml:665
+#: preseed.xml:635
 #, no-c-format
-#. Tag: userinput
-msgid "manual package selection"
+#. Tag: para
+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 system</userinput> task."
 msgstr ""
 
-#: preseed.xml:669
+#: preseed.xml:643
 #, no-c-format
-#. Tag: para
-msgid "The last of these will run aptitude. 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 system</userinput> task."
+#. Tag: screen
+msgid ""
+      "tasksel tasksel/first multiselect Standard system, Desktop environment\n"
+      "#tasksel tasksel/first multiselect Standard system, Web server\n"
+      "\n"
+      "# Some versions of the installer can report back on what software you have\n"
+      "# installed, and what software you ue. The default is not to report back,\n"
+      "# but sending reports helps the project determine what software is most\n"
+      "# popular and include it on CDs.\n"
+      "#popularity-contest popularity-contest/participate boolean false"
 msgstr ""
 
-#: preseed.xml:677
+#: preseed.xml:648
+#, no-c-format
+#. Tag: title
+msgid "Finishing up the first stage install"
+msgstr ""
+
+#: preseed.xml:650
 #, no-c-format
 #. Tag: screen
 msgid ""
-      "tasksel tasksel/first multiselect Standard system, Desktop environment\n"
-      "#tasksel tasksel/first multiselect Standard system, Web server"
+      "# Avoid that last message about the install being complete.\n"
+      "d-i prebaseconfig/reboot_in_progress note\n"
+      "\n"
+      "# This will prevent the installer from ejecting the CD during the reboot,\n"
+      "# which is useful in some situations.\n"
+      "#d-i cdrom-detect/eject boolean false"
 msgstr ""
 
-#: preseed.xml:682
+#: preseed.xml:655
 #, no-c-format
 #. Tag: title
 msgid "Mailer configuration"
 msgstr ""
 
-#: preseed.xml:683
+#: preseed.xml:656
 #, no-c-format
 #. Tag: para
 msgid "During a normal install, exim asks only a few questions. Here's how to avoid even those. More complicated preseeding is possible."
 msgstr ""
 
-#: preseed.xml:690
+#: preseed.xml:663
 #, no-c-format
 #. Tag: screen
 msgid ""
@@ -903,19 +856,19 @@ msgid ""
       "exim4-config exim4/dc_postmaster string"
 msgstr ""
 
-#: preseed.xml:695
+#: preseed.xml:668
 #, no-c-format
 #. Tag: title
 msgid "X configuration"
 msgstr ""
 
-#: preseed.xml:696
+#: preseed.xml:669
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: preseed.xml:704
+#: preseed.xml:677
 #, no-c-format
 #. Tag: screen
 msgid ""
@@ -941,13 +894,13 @@ msgid ""
       "       select 1024x768 @ 60 Hz"
 msgstr ""
 
-#: preseed.xml:709
+#: preseed.xml:682
 #, no-c-format
 #. Tag: title
 msgid "Preseeding other packages"
 msgstr ""
 
-#: preseed.xml:711
+#: preseed.xml:684
 #, no-c-format
 #. Tag: screen
 msgid ""
@@ -960,19 +913,19 @@ msgid ""
       "#   debconf-get-selections >> file"
 msgstr ""
 
-#: preseed.xml:717
+#: preseed.xml:690
 #, no-c-format
 #. Tag: title
 msgid "Advanced options"
 msgstr ""
 
-#: preseed.xml:720
+#: preseed.xml:693
 #, no-c-format
 #. Tag: title
 msgid "Shell commands"
 msgstr ""
 
-#: preseed.xml:722
+#: preseed.xml:695
 #, no-c-format
 #. Tag: screen
 msgid ""
@@ -988,32 +941,25 @@ msgid ""
       "#d-i preseed/early_command string anna-install some-udeb\n"
       "\n"
       "# This command is run just before the install finishes, but when there is\n"
-      "# still a usable /target directory.\n"
-      "#d-i preseed/late_command string echo foo > /target/etc/bar\n"
-      "\n"
-      "# This command is run just as base-config is starting up.\n"
-      "#base-config base-config/early_command string echo hi mom\n"
-      "\n"
-      "# This command is run after base-config is done, just before the login:\n"
-      "# prompt. This is a good way to install a set of packages you want, or to\n"
-      "# tweak the configuration of the system.\n"
-      "#base-config base-config/late_command \\\n"
-      "#      string apt-get install zsh; chsh -s /bin/zsh"
+      "# still a usable /target directory. You can chroot to /target and use it\n"
+      "# directly, or use the apt-install and in-target commands to easily install\n"
+      "# packages and run commands in the target system.\n"
+      "#d-i preseed/late_command string apt-install zsh; in-target chsh -s /bin/zsh"
 msgstr ""
 
-#: preseed.xml:727
+#: preseed.xml:700
 #, no-c-format
 #. Tag: title
 msgid "Chainloading preseed files"
 msgstr ""
 
-#: preseed.xml:728
+#: preseed.xml:701
 #, no-c-format
 #. Tag: para
 msgid "It is possible to include other preseed files from a preseed 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 ""
 
-#: preseed.xml:738
+#: preseed.xml:711
 #, no-c-format
 #. Tag: screen
 msgid ""
diff --git a/po/pot/random-bits.pot b/po/pot/random-bits.pot
index ea2421416..b0ab6df2d 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"
-"POT-Creation-Date: 2005-12-03 10:28+0000\n"
+"POT-Creation-Date: 2006-01-03 19:55+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"
@@ -23,689 +23,298 @@ msgstr ""
 #: random-bits.xml:11
 #, no-c-format
 #. Tag: title
-msgid "Preconfiguration File Example"
-msgstr ""
-
-#: random-bits.xml:13
-#, no-c-format
-#. Tag: para
-msgid "This is a complete working example of a preconfiguration file for an automated install. Its use is explained in <xref linkend=\"automatic-install\"/>. You may want to uncomment some of the lines before using the file."
-msgstr ""
-
-#: random-bits.xml:21
-#, no-c-format
-#. Tag: para
-msgid "In order to be able to properly present this example in the manual, we've had to split some lines. This is indicated by the use of the line-continuation-character <quote>\\</quote> and extra indentation in the next line. In a real preconfiguration file, these split lines have to be joined into <emphasis>one single line</emphasis>. If you do not, preconfiguration will fail with unpredictable results."
-msgstr ""
-
-#: random-bits.xml:29
-#, no-c-format
-#. Tag: para
-msgid "A <quote>clean</quote> example file is available from &urlset-example-preseed;."
-msgstr ""
-
-#: random-bits.xml:41
-#, no-c-format
-#. Tag: screen
-msgid ""
-      "#### Startup.\n"
-      "\n"
-      "# To use a preseed file, you'll first need to boot the installer,\n"
-      "# and tell it what preseed file to use. This is done by passing the\n"
-      "# kernel a boot parameter, either manually at boot or by editing the\n"
-      "# syslinux.cfg (or similar) file and adding the parameter to the end\n"
-      "# of the append line(s) for the kernel.\n"
-      "#\n"
-      "# If you're netbooting, use this:\n"
-      "#   preseed/url=http://host/path/to/preseed\n"
-      "# If you're remastering a CD, you could use this:\n"
-      "#   preseed/file=/cdrom/preseed\n"
-      "# If you're installing from USB media, use this, and put the preseed file\n"
-      "# in the toplevel directory of the USB stick.\n"
-      "#   preseed/file=/hd-media/preseed\n"
-      "# Be sure to copy this file to the location you specify.\n"
-      "#\n"
-      "# Some parts of the installation process cannot be automated using\n"
-      "# some forms of preseeding, because the questions are asked before\n"
-      "# the preseed file is loaded. For example, if the preseed file is\n"
-      "# downloaded over the network, the network setup must be done first.\n"
-      "# One reason to use initrd preseeding is that it allows preseeding\n"
-      "# of even these early steps of the installation process.\n"
-      "#\n"
-      "# If a preseed file cannot be used to preseed some steps, the install can\n"
-      "# still be fully automated, since you can pass preseed values to the kernel\n"
-      "# on the command line. Just pass path/to/var=value for any of the preseed\n"
-      "# variables listed below.\n"
-      "#\n"
-      "# While you're at it, you may want to throw a debconf/priority=critical in\n"
-      "# there, to avoid most questions even if the preseeding below misses some.\n"
-      "# And you might set the timeout to 1 in syslinux.cfg to avoid needing to hit\n"
-      "# enter to boot the installer.\n"
-      "#\n"
-      "# Note that the kernel accepts a maximum of 8 command line options and\n"
-      "# 8 environment options (including any options added by default for the\n"
-      "# installer). If these numbers are exceeded, 2.4 kernels will drop any\n"
-      "# excess options and 2.6 kernels will panic. With kernel 2.6.9 or newer,\n"
-      "# you can use 32 command line options and 32 environment options.\n"
-      "#\n"
-      "# Some of the default options, like 'vga=normal' may be safely removed\n"
-      "# for most installations, which may allow you to add more options for\n"
-      "# preseeding.\n"
-      "\n"
-      "# It is not possible to use preseeding to set language, country, and\n"
-      "# keyboard. Instead you should use kernel parameters. Example:\n"
-      "# languagechooser/language-name=English\n"
-      "# countrychooser/shortlist=US\n"
-      "# console-keymaps-at/keymap=us\n"
-      "\n"
-      "#### Network configuration.\n"
-      "\n"
-      "# Of course, this won't work if you're loading your preseed file from the\n"
-      "# network! But it's great if you're booting from CD or USB stick. You can\n"
-      "# also pass network config parameters in on the kernel params if you are\n"
-      "# loading preseed files from the network.\n"
-      "\n"
-      "# netcfg will choose an interface that has link if possible. This makes it\n"
-      "# skip displaying a list if there is more than one interface.\n"
-      "d-i netcfg/choose_interface select auto\n"
-      "\n"
-      "# If you have a slow dhcp server and the installer times out waiting for\n"
-      "# it, this might be useful.\n"
-      "#d-i netcfg/dhcp_timeout string 60\n"
-      "\n"
-      "# If you prefer to configure the network manually, here's how:\n"
-      "#d-i netcfg/disable_dhcp boolean true\n"
-      "#d-i netcfg/get_nameservers string 192.168.1.1\n"
-      "#d-i netcfg/get_ipaddress string 192.168.1.42\n"
-      "#d-i netcfg/get_netmask string 255.255.255.0\n"
-      "#d-i netcfg/get_gateway string 192.168.1.1\n"
-      "#d-i netcfg/confirm_static boolean true\n"
-      "\n"
-      "# Note that any hostname and domain names assigned from dhcp take\n"
-      "# precedence over values set here. However, setting the values still\n"
-      "# prevents the questions from being shown even if values come from dhcp.\n"
-      "d-i netcfg/get_hostname string unassigned-hostname\n"
-      "d-i netcfg/get_domain string unassigned-domain\n"
-      "\n"
-      "# Disable that annoying WEP key dialog.\n"
-      "d-i netcfg/wireless_wep string\n"
-      "# The wacky dhcp hostname that some ISPs use as a password of sorts.\n"
-      "#d-i netcfg/dhcp_hostname string radish\n"
-      "\n"
-      "#### Mirror settings.\n"
-      "\n"
-      "d-i mirror/country string enter information manually\n"
-      "d-i mirror/http/hostname string http.us.debian.org\n"
-      "d-i mirror/http/directory string /debian\n"
-      "d-i mirror/suite string testing\n"
-      "d-i mirror/http/proxy string\n"
-      "\n"
-      "#### Partitioning.\n"
-      "\n"
-      "# If the system has free space you can choose to only partition that space.\n"
-      "#d-i partman-auto/init_automatically_partition \\\n"
-      "#    select Use the largest continuous free space\n"
-      "\n"
-      "# Alternatively, you can specify a disk to partition. The device name can\n"
-      "# be given in either devfs or traditional non-devfs format.\n"
-      "# For example, to use the first disk devfs knows of:\n"
-      "d-i partman-auto/disk string /dev/discs/disc0/disc\n"
-      "\n"
-      "# You can choose from any of the predefined partitioning recipes:\n"
-      "d-i partman-auto/choose_recipe select \\\n"
-      "     All files in one partition (recommended for new users)\n"
-      "#d-i partman-auto/choose_recipe select Desktop machine\n"
-      "#d-i partman-auto/choose_recipe select Multi-user workstation\n"
-      "\n"
-      "# Or provide a recipe of your own...\n"
-      "# The recipe format is documented in the file devel/partman-auto-recipe.txt.\n"
-      "# If you have a way to get a recipe file into the d-i environment, you can\n"
-      "# just point at it.\n"
-      "#d-i partman-auto/expert_recipe_file string /hd-media/recipe\n"
-      "\n"
-      "# If not, you can put an entire recipe in one line. This example creates\n"
-      "# a small /boot partition, suitable swap, and uses the rest of the space\n"
-      "# for the root partition:\n"
-      "#d-i partman-auto/expert_recipe string boot-root :: \\\n"
-      "#    20 50 100 ext3 $primary{ } $bootable{ } method{ format } format{ } \\\n"
-      "#    use_filesystem{ } filesystem{ ext3 } mountpoint{ /boot } . \\\n"
-      "#    500 10000 1000000000 ext3 method{ format } format{ } \\\n"
-      "#    use_filesystem{ } filesystem{ ext3 } mountpoint{ / } . \\\n"
-      "#    64 512 300% linux-swap method{ swap } format{ } .\n"
-      "# For reference, here is that same recipe in a more readable form:\n"
-      "#    boot-root ::\n"
-      "#       40 50 100 ext3\n"
-      "#          $primary{ } $bootable{ }\n"
-      "#          method{ format } format{ }\n"
-      "#          use_filesystem{ } filesystem{ ext3 }\n"
-      "#          mountpoint{ /boot }\n"
-      "#       .\n"
-      "#       500 10000 1000000000 ext3\n"
-      "#          method{ format } format{ }\n"
-      "#          use_filesystem{ } filesystem{ ext3 }\n"
-      "#          mountpoint{ / }\n"
-      "#       .\n"
-      "#       64 512 300% linux-swap\n"
-      "#          method{ swap } format{ }\n"
-      "#       .\n"
-      "\n"
-      "# This makes partman automatically partition without confirmation.\n"
-      "d-i partman/confirm_write_new_label boolean true\n"
-      "d-i partman/choose_partition select \\\n"
-      "    Finish partitioning and write changes to disk\n"
-      "d-i partman/confirm boolean true\n"
-      "\n"
-      "#### Boot loader installation.\n"
-      "\n"
-      "# Grub is the default boot loader (for x86). If you want lilo installed\n"
-      "# instead, uncomment this:\n"
-      "#d-i grub-installer/skip boolean true\n"
-      "\n"
-      "# This is fairly safe to set, it makes grub install automatically to the MBR\n"
-      "# if no other operating system is detected on the machine.\n"
-      "d-i grub-installer/only_debian boolean true\n"
-      "\n"
-      "# This one makes grub-installer install to the MBR if if finds some other OS\n"
-      "# too, which is less safe as it might not be able to boot that other OS.\n"
-      "d-i grub-installer/with_other_os boolean true\n"
-      "\n"
-      "# Alternatively, if you want to install to a location other than the mbr,\n"
-      "# uncomment and edit these lines:\n"
-      "#d-i grub-installer/bootdev  string (hd0,0)\n"
-      "#d-i grub-installer/only_debian boolean false\n"
-      "#d-i grub-installer/with_other_os boolean false\n"
-      "\n"
-      "#### Finishing up the first stage install.\n"
-      "\n"
-      "# Avoid that last message about the install being complete.\n"
-      "d-i prebaseconfig/reboot_in_progress note\n"
-      "\n"
-      "#### Shell commands.\n"
-      "\n"
-      "# d-i preseeding is inherently not secure. Nothing in the installer checks\n"
-      "# for attempts at buffer overflows or other exploits of the values of a\n"
-      "# preseed file like this one. Only use preseed files from trusted\n"
-      "# locations! To drive that home, and because it's generally useful, here's\n"
-      "# a way to run any shell command you'd like inside the installer,\n"
-      "# automatically.\n"
-      "\n"
-      "# This first command is run as early as possible, just after\n"
-      "# preseeding is read.\n"
-      "#d-i preseed/early_command string anna-install some-udeb\n"
-      "\n"
-      "# This command is run just before the install finishes, but when there is\n"
-      "# still a usable /target directory.\n"
-      "#d-i preseed/late_command string echo foo > /target/etc/bar\n"
-      "\n"
-      "# This command is run just as base-config is starting up.\n"
-      "#base-config base-config/early_command string echo hi mom\n"
-      "\n"
-      "# This command is run after base-config is done, just before the login:\n"
-      "# prompt. This is a good way to install a set of packages you want, or to\n"
-      "# tweak the configuration of the system.\n"
-      "#base-config base-config/late_command string \\\n"
-      "#    apt-get install zsh; chsh -s /bin/zsh\n"
-      "\n"
-      "###### Preseeding the 2nd stage of the installation.\n"
-      "\n"
-      "#### Preseeding base-config.\n"
-      "\n"
-      "# Avoid the introductory message.\n"
-      "base-config base-config/intro note\n"
-      "\n"
-      "# Avoid the final message.\n"
-      "base-config base-config/login note\n"
-      "\n"
-      "# If you installed a display manager, but don't want to start it immediately\n"
-      "# after base-config finishes.\n"
-      "#base-config base-config/start-display-manager boolean false\n"
-      "\n"
-      "# Some versions of the installer can report back on what you've installed.\n"
-      "# The default is not to report back, but sending reports helps the project\n"
-      "# determine what software is most popular and include it on CDs.\n"
-      "#popularity-contest popularity-contest/participate boolean false\n"
-      "\n"
-      "#### Clock and time zone setup.\n"
-      "\n"
-      "# Controls whether or not the hardware clock is set to UTC.\n"
-      "#base-config tzconfig/gmt boolean true\n"
-      "# If you told the installer that you're in the United States, then you\n"
-      "# can set the time zone using this variable.\n"
-      "# (Choices are: Eastern, Central, Mountain, Pacific, Alaska, Hawaii,\n"
-      "# Aleutian, Arizona East-Indiana, Indiana-Starke, Michigan, Samoa, other)\n"
-      "#base-config tzconfig/choose_country_zone/US select Eastern\n"
-      "# If you told it you're in Canada.\n"
-      "# (Choices are: Newfoundland, Atlantic, Eastern, Central,\n"
-      "# East-Saskatchewan, Saskatchewan, Mountain, Pacific, Yukon, other)\n"
-      "#base-config tzconfig/choose_country_zone/CA select Eastern\n"
-      "# If you told it you're in Brazil. (Choices are: East, West, Acre,\n"
-      "# DeNoronha, other)\n"
-      "#base-config tzconfig/choose_country_zone/BR select East\n"
-      "# Many countries have only one time zone. If you told the installer you're\n"
-      "# in one of those countries, you can choose its standard time zone via this\n"
-      "# question.\n"
-      "#base-config tzconfig/choose_country_zone_single boolean true\n"
-      "# This question is asked as a fallback for countries other than those\n"
-      "# listed above, which have more than one time zone. You can preseed one of\n"
-      "# the time zones, or \"other\".\n"
-      "#base-config tzconfig/choose_country_zone_multiple select\n"
-      "\n"
-      "#### Account setup.\n"
-      "\n"
-      "# To preseed the root password, you have to put it in the clear in this\n"
-      "# file. That is not a very good idea, use caution!\n"
-      "#passwd passwd/root-password password r00tme\n"
-      "#passwd passwd/root-password-again password r00tme\n"
-      "\n"
-      "# If you want to skip creation of a normal user account.\n"
-      "#passwd passwd/make-user boolean false\n"
-      "\n"
-      "# Alternatively, you can preseed the user's name and login.\n"
-      "#passwd passwd/user-fullname string Debian User\n"
-      "#passwd passwd/username string debian\n"
-      "# And their password, but use caution!\n"
-      "#passwd passwd/user-password password insecure\n"
-      "#passwd passwd/user-password-again password insecure\n"
-      "\n"
-      "#### Apt setup.\n"
-      "\n"
-      "# This question controls what source the second stage installation uses\n"
-      "# for packages. Choices are cdrom, http, ftp, filesystem, edit sources list\n"
-      "# by hand\n"
-      "base-config apt-setup/uri_type select http\n"
-      "\n"
-      "# If you choose ftp or http, you'll be asked for a country and a mirror.\n"
-      "base-config apt-setup/country select enter information manually\n"
-      "base-config apt-setup/hostname string http.us.debian.org\n"
-      "base-config apt-setup/directory string /debian\n"
-      "# Stop after choosing one mirror.\n"
-      "base-config apt-setup/another boolean false\n"
-      "\n"
-      "# You can choose to install non-free and contrib software.\n"
-      "#base-config apt-setup/non-free boolean true\n"
-      "#base-config apt-setup/contrib boolean true\n"
-      "\n"
-      "# Do enable security updates.\n"
-      "base-config apt-setup/security-updates boolean true\n"
-      "\n"
-      "#### Package selection.\n"
-      "\n"
-      "# You can choose to install any combination of tasks that are available.\n"
-      "# Available tasks as of this writing include: Desktop environment,\n"
-      "# Web server, Print server, DNS server, File server, Mail server,\n"
-      "# SQL database, Laptop, Standard system, manual package selection. The\n"
-      "# last of those will run aptitude. You can also choose to install no\n"
-      "# tasks, and force the installation of a set of packages in some other\n"
-      "# way. We recommend always including the Standard system task.\n"
-      "tasksel tasksel/first multiselect Desktop environment, Standard system\n"
-      "#tasksel tasksel/first multiselect Web server, Standard system\n"
-      "\n"
-      "#### Mailer configuration.\n"
-      "\n"
-      "# During a normal install, exim asks only a few questions. Here's how to\n"
-      "# avoid even those. More complicated preseeding is possible.\n"
-      "exim4-config exim4/dc_eximconfig_configtype \\\n"
-      "    select no configuration at this time\n"
-      "exim4-config exim4/no_config boolean true\n"
-      "exim4-config exim4/no_config boolean true\n"
-      "\n"
-      "# It's a good idea to set this to whatever user account you choose to\n"
-      "# create. Leaving the value blank results in postmaster mail going to\n"
-      "# /var/mail/mail.\n"
-      "exim4-config exim4/dc_postmaster string\n"
-      "\n"
-      "#### X Configuration.\n"
-      "\n"
-      "# Preseeding Debian's X config is possible, but you probably need to know\n"
-      "# some details about the video hardware of the machine, since Debian's X\n"
-      "# configurator does not do fully automatic configuration of everything.\n"
-      "\n"
-      "# X can detect the right driver for some cards, but if you're preseeding,\n"
-      "# you override whatever it chooses. Still, vesa will work most places.\n"
-      "#xserver-xfree86 xserver-xfree86/config/device/driver select vesa\n"
-      "\n"
-      "# A caveat with mouse autodetection is that if it fails, X will retry it\n"
-      "# over and over. So if it's preseeded to be done, there is a possibility of\n"
-      "# an infinite loop if the mouse is not autodetected.\n"
-      "#xserver-xfree86 xserver-xfree86/autodetect_mouse boolean true\n"
-      "\n"
-      "# Monitor autodetection is recommended.\n"
-      "xserver-xfree86 xserver-xfree86/autodetect_monitor boolean true\n"
-      "# Uncomment if you have an LCD display.\n"
-      "#xserver-xfree86 xserver-xfree86/config/monitor/lcd boolean true\n"
-      "# X has three configuration paths for the monitor. Here's how to preseed\n"
-      "# the \"medium\" path, which is always available. The \"simple\" path may not\n"
-      "# be available, and the \"advanced\" path asks too many questions.\n"
-      "xserver-xfree86 xserver-xfree86/config/monitor/selection-method \\\n"
-      "    select medium\n"
-      "xserver-xfree86 xserver-xfree86/config/monitor/mode-list \\\n"
-      "    select 1024x768 @ 60 Hz\n"
-      "\n"
-      "#### Everything else.\n"
-      "\n"
-      "# Depending on what software you choose to install, or if things go wrong\n"
-      "# during the installation process, it's possible that other questions may\n"
-      "# be asked. You can preseed those too, of course. To get a list of every\n"
-      "# possible question that could be asked during an install, do an\n"
-      "# installation, and then run these commands:\n"
-      "#   debconf-get-selections --installer > file\n"
-      "#   debconf-get-selections >> file\n"
-      "\n"
-      "# If you like, you can include other preseed files into this one.\n"
-      "# Any settings in those files will override pre-existing settings from this\n"
-      "# file. More that one file can be listed, separated by spaces; all will be\n"
-      "# loaded. The included files can have preseed/include directives of their\n"
-      "# own as well. Note that if the filenames are relative, they are taken from\n"
-      "# the same directory as the preseed file that includes them.\n"
-      "#d-i preseed/include string x.cfg\n"
-      "\n"
-      "# More flexibly, this runs a shell command and if it outputs the names of\n"
-      "# preseed files, includes those files. For example, to switch configs based\n"
-      "# on a particular usb storage device (in this case, a built-in card reader):\n"
-      "#d-i preseed/include_command string \\\n"
-      "#    if $(grep -q \"GUID: 0aec3050aec305000001a003\" /proc/scsi/usb-storage-*/*); \\\n"
-      "#    then echo kraken.cfg; else echo otherusb.cfg; fi\n"
-      "\n"
-      "# To check the format of your preseed file before performing an install,\n"
-      "# you can use debconf-set-selections:\n"
-      "#   debconf-set-selections -c preseed.cfg"
-msgstr ""
-
-#: random-bits.xml:52
-#, no-c-format
-#. Tag: title
 msgid "Linux Devices"
 msgstr ""
 
-#: random-bits.xml:53
+#: random-bits.xml:12
 #, no-c-format
 #. Tag: para
 msgid "In Linux you have various special files in <filename>/dev</filename>. These files are called device files. In the Unix world accessing hardware is different. There you have a special file which actually runs a driver which in turn accesses the hardware. The device file is an interface to the actual system component. Files under <filename>/dev</filename> also behave differently than ordinary files. Below are the most important device files listed."
 msgstr ""
 
-#: random-bits.xml:68
+#: random-bits.xml:27
 #, no-c-format
 #. Tag: filename
 msgid "<filename>fd0</filename>"
 msgstr ""
 
-#: random-bits.xml:69
+#: random-bits.xml:28
 #, no-c-format
 #. Tag: entry
 msgid "First Floppy Drive"
 msgstr ""
 
-#: random-bits.xml:71
+#: random-bits.xml:30
 #, no-c-format
 #. Tag: filename
 msgid "<filename>fd1</filename>"
 msgstr ""
 
-#: random-bits.xml:72
+#: random-bits.xml:31
 #, no-c-format
 #. Tag: entry
 msgid "Second Floppy Drive"
 msgstr ""
 
-#: random-bits.xml:78
+#: random-bits.xml:37
 #, no-c-format
 #. Tag: filename
 msgid "<filename>hda</filename>"
 msgstr ""
 
-#: random-bits.xml:79
+#: random-bits.xml:38
 #, no-c-format
 #. Tag: entry
 msgid "IDE Hard disk / CD-ROM on the first IDE port (Master)"
 msgstr ""
 
-#: random-bits.xml:81
+#: random-bits.xml:40
 #, no-c-format
 #. Tag: filename
 msgid "<filename>hdb</filename>"
 msgstr ""
 
-#: random-bits.xml:82
+#: random-bits.xml:41
 #, no-c-format
 #. Tag: entry
 msgid "IDE Hard disk / CD-ROM on the first IDE port (Slave)"
 msgstr ""
 
-#: random-bits.xml:84
+#: random-bits.xml:43
 #, no-c-format
 #. Tag: filename
 msgid "<filename>hdc</filename>"
 msgstr ""
 
-#: random-bits.xml:85
+#: random-bits.xml:44
 #, no-c-format
 #. Tag: entry
 msgid "IDE Hard disk / CD-ROM on the second IDE port (Master)"
 msgstr ""
 
-#: random-bits.xml:87
+#: random-bits.xml:46
 #, no-c-format
 #. Tag: filename
 msgid "<filename>hdd</filename>"
 msgstr ""
 
-#: random-bits.xml:88
+#: random-bits.xml:47
 #, no-c-format
 #. Tag: entry
 msgid "IDE Hard disk / CD-ROM on the second IDE port (Slave)"
 msgstr ""
 
-#: random-bits.xml:90
+#: random-bits.xml:49
 #, no-c-format
 #. Tag: filename
 msgid "hda1"
 msgstr ""
 
-#: random-bits.xml:91
+#: random-bits.xml:50
 #, no-c-format
 #. Tag: entry
 msgid "First partition of the first IDE hard disk"
 msgstr ""
 
-#: random-bits.xml:93
+#: random-bits.xml:52
 #, no-c-format
 #. Tag: filename
 msgid "hdd15"
 msgstr ""
 
-#: random-bits.xml:94
+#: random-bits.xml:53
 #, no-c-format
 #. Tag: entry
 msgid "Fifteenth partition of the fourth IDE hard disk"
 msgstr ""
 
-#: random-bits.xml:100
+#: random-bits.xml:59
 #, no-c-format
 #. Tag: filename
 msgid "<filename>sda</filename>"
 msgstr ""
 
-#: random-bits.xml:101
+#: random-bits.xml:60
 #, no-c-format
 #. Tag: entry
 msgid "SCSI Hard disk with lowest SCSI ID (e.g. 0)"
 msgstr ""
 
-#: random-bits.xml:103
+#: random-bits.xml:62
 #, no-c-format
 #. Tag: filename
 msgid "<filename>sdb</filename>"
 msgstr ""
 
-#: random-bits.xml:104
+#: random-bits.xml:63
 #, no-c-format
 #. Tag: entry
 msgid "SCSI Hard disk with next higher SCSI ID (e.g. 1)"
 msgstr ""
 
-#: random-bits.xml:106
+#: random-bits.xml:65
 #, no-c-format
 #. Tag: filename
 msgid "<filename>sdc</filename>"
 msgstr ""
 
-#: random-bits.xml:107
+#: random-bits.xml:66
 #, no-c-format
 #. Tag: entry
 msgid "SCSI Hard disk with next higher SCSI ID (e.g. 2)"
 msgstr ""
 
-#: random-bits.xml:109
+#: random-bits.xml:68
 #, no-c-format
 #. Tag: filename
 msgid "sda1"
 msgstr ""
 
-#: random-bits.xml:110
+#: random-bits.xml:69
 #, no-c-format
 #. Tag: entry
 msgid "First partition of the first SCSI hard disk"
 msgstr ""
 
-#: random-bits.xml:112
+#: random-bits.xml:71
 #, no-c-format
 #. Tag: filename
 msgid "sdd10"
 msgstr ""
 
-#: random-bits.xml:113
+#: random-bits.xml:72
 #, no-c-format
 #. Tag: entry
 msgid "Tenth partition of the fourth SCSI hard disk"
 msgstr ""
 
-#: random-bits.xml:119
+#: random-bits.xml:78
 #, no-c-format
 #. Tag: filename
 msgid "<filename>sr0</filename>"
 msgstr ""
 
-#: random-bits.xml:120
+#: random-bits.xml:79
 #, no-c-format
 #. Tag: entry
 msgid "SCSI CD-ROM with the lowest SCSI ID"
 msgstr ""
 
-#: random-bits.xml:122
+#: random-bits.xml:81
 #, no-c-format
 #. Tag: filename
 msgid "<filename>sr1</filename>"
 msgstr ""
 
-#: random-bits.xml:123
+#: random-bits.xml:82
 #, no-c-format
 #. Tag: entry
 msgid "SCSI CD-ROM with the next higher SCSI ID"
 msgstr ""
 
-#: random-bits.xml:129
+#: random-bits.xml:88
 #, no-c-format
 #. Tag: filename
 msgid "ttyS0"
 msgstr ""
 
-#: random-bits.xml:130
+#: random-bits.xml:89
 #, no-c-format
 #. Tag: entry
 msgid "Serial port 0, COM1 under MS-DOS"
 msgstr ""
 
-#: random-bits.xml:132
+#: random-bits.xml:91
 #, no-c-format
 #. Tag: filename
 msgid "ttyS1"
 msgstr ""
 
-#: random-bits.xml:133
+#: random-bits.xml:92
 #, no-c-format
 #. Tag: entry
 msgid "Serial port 1, COM2 under MS-DOS"
 msgstr ""
 
-#: random-bits.xml:135
+#: random-bits.xml:94
 #, no-c-format
 #. Tag: filename
 msgid "psaux"
 msgstr ""
 
-#: random-bits.xml:136
+#: random-bits.xml:95
 #, no-c-format
 #. Tag: entry
 msgid "PS/2 mouse device"
 msgstr ""
 
-#: random-bits.xml:138
+#: random-bits.xml:97
 #, no-c-format
 #. Tag: filename
 msgid "gpmdata"
 msgstr ""
 
-#: random-bits.xml:139
+#: random-bits.xml:98
 #, no-c-format
 #. Tag: entry
 msgid "Pseudo device, repeater data from GPM (mouse) daemon"
 msgstr ""
 
-#: random-bits.xml:145
+#: random-bits.xml:104
 #, no-c-format
 #. Tag: filename
 msgid "cdrom"
 msgstr ""
 
-#: random-bits.xml:146
+#: random-bits.xml:105
 #, no-c-format
 #. Tag: entry
 msgid "Symbolic link to the CD-ROM drive"
 msgstr ""
 
-#: random-bits.xml:148
+#: random-bits.xml:107
 #, no-c-format
 #. Tag: filename
 msgid "mouse"
 msgstr ""
 
-#: random-bits.xml:149
+#: random-bits.xml:108
 #, no-c-format
 #. Tag: entry
 msgid "Symbolic link to the mouse device file"
 msgstr ""
 
-#: random-bits.xml:155
+#: random-bits.xml:114
 #, no-c-format
 #. Tag: filename
 msgid "null"
 msgstr ""
 
-#: random-bits.xml:156
+#: random-bits.xml:115
 #, no-c-format
 #. Tag: entry
 msgid "Everything pointed to this device will disappear"
 msgstr ""
 
-#: random-bits.xml:158
+#: random-bits.xml:117
 #, no-c-format
 #. Tag: filename
 msgid "zero"
 msgstr ""
 
-#: random-bits.xml:159
+#: random-bits.xml:118
 #, no-c-format
 #. Tag: entry
 msgid "One can endlessly read zeros out of this device"
 msgstr ""
 
-#: random-bits.xml:166
+#: random-bits.xml:125
 #, no-c-format
 #. Tag: title
 msgid "Setting Up Your Mouse"
 msgstr ""
 
-#: random-bits.xml:168
+#: random-bits.xml:127
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -716,7 +325,7 @@ msgid ""
       "</screen></informalexample> Set the repeater protocol to be raw (in <filename>/etc/gpm.conf</filename>) while setting X to the original mouse protocol in <filename>/etc/X11/XF86Config</filename> or <filename>/etc/X11/XF86Config-4</filename>."
 msgstr ""
 
-#: random-bits.xml:180
+#: random-bits.xml:139
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -725,25 +334,25 @@ msgid ""
       "</screen></informalexample> will re-connect the mouse in software without restarting X."
 msgstr ""
 
-#: random-bits.xml:189
+#: random-bits.xml:148
 #, no-c-format
 #. Tag: para
 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-xfree86;current/mouse.html\">README.mouse</ulink>."
 msgstr ""
 
-#: random-bits.xml:199
+#: random-bits.xml:158
 #, no-c-format
 #. Tag: para
 msgid "For PowerPC, in <filename>/etc/X11/XF86Config</filename> or <filename>/etc/X11/XF86Config-4</filename>, set the mouse device to <userinput>\"/dev/input/mice\"</userinput>."
 msgstr ""
 
-#: random-bits.xml:205
+#: random-bits.xml:164
 #, no-c-format
 #. Tag: para
 msgid "Modern kernels give you the capability to emulate a three-button mouse when your mouse only has one button. Just add the following lines to <filename>/etc/sysctl.conf</filename> file."
 msgstr ""
 
-#: random-bits.xml:211
+#: random-bits.xml:170
 #, no-c-format
 #. Tag: screen
 msgid ""
@@ -757,259 +366,259 @@ msgid ""
       "# For different keys, use showkey to tell you what the code is."
 msgstr ""
 
-#: random-bits.xml:218
+#: random-bits.xml:177
 #, no-c-format
 #. Tag: title
 msgid "Disk Space Needed for Tasks"
 msgstr ""
 
-#: random-bits.xml:230
+#: random-bits.xml:189
 #, no-c-format
 #. Tag: para
 msgid "The base installation for i386 using the default 2.4 kernel, including all standard packages, requires 573MB of disk space."
 msgstr ""
 
-#: random-bits.xml:235
+#: random-bits.xml:194
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: random-bits.xml:242
+#: random-bits.xml:201
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: random-bits.xml:255
+#: random-bits.xml:214
 #, no-c-format
 #. Tag: entry
 msgid "Task"
 msgstr ""
 
-#: random-bits.xml:256
+#: random-bits.xml:215
 #, no-c-format
 #. Tag: entry
 msgid "Installed size (MB)"
 msgstr ""
 
-#: random-bits.xml:257
+#: random-bits.xml:216
 #, no-c-format
 #. Tag: entry
 msgid "Download size (MB)"
 msgstr ""
 
-#: random-bits.xml:258
+#: random-bits.xml:217
 #, no-c-format
 #. Tag: entry
 msgid "Space needed to install (MB)"
 msgstr ""
 
-#: random-bits.xml:264
+#: random-bits.xml:223
 #, no-c-format
 #. Tag: entry
 msgid "Desktop"
 msgstr ""
 
-#: random-bits.xml:265
+#: random-bits.xml:224
 #, no-c-format
 #. Tag: entry
 msgid "1392"
 msgstr ""
 
-#: random-bits.xml:266
+#: random-bits.xml:225
 #, no-c-format
 #. Tag: entry
 msgid "<entry>460</entry>"
 msgstr ""
 
-#: random-bits.xml:267
+#: random-bits.xml:226
 #, no-c-format
 #. Tag: entry
 msgid "1852"
 msgstr ""
 
-#: random-bits.xml:271
+#: random-bits.xml:230
 #, no-c-format
 #. Tag: entry
 msgid "Web server"
 msgstr ""
 
-#: random-bits.xml:272
+#: random-bits.xml:231
 #, no-c-format
 #. Tag: entry
 msgid "<entry>36</entry>"
 msgstr ""
 
-#: random-bits.xml:273
+#: random-bits.xml:232
 #, no-c-format
 #. Tag: entry
 msgid "<entry>12</entry>"
 msgstr ""
 
-#: random-bits.xml:274
+#: random-bits.xml:233
 #, no-c-format
 #. Tag: entry
 msgid "<entry>48</entry>"
 msgstr ""
 
-#: random-bits.xml:278
+#: random-bits.xml:237
 #, no-c-format
 #. Tag: entry
 msgid "Print server"
 msgstr ""
 
-#: random-bits.xml:279
+#: random-bits.xml:238
 #, no-c-format
 #. Tag: entry
 msgid "<entry>168</entry>"
 msgstr ""
 
-#: random-bits.xml:280
+#: random-bits.xml:239
 #, no-c-format
 #. Tag: entry
 msgid "<entry>58</entry>"
 msgstr ""
 
-#: random-bits.xml:281
+#: random-bits.xml:240
 #, no-c-format
 #. Tag: entry
 msgid "<entry>226</entry>"
 msgstr ""
 
-#: random-bits.xml:285
+#: random-bits.xml:244
 #, no-c-format
 #. Tag: entry
 msgid "DNS server"
 msgstr ""
 
-#: random-bits.xml:286
+#: random-bits.xml:245
 #, no-c-format
 #. Tag: entry
 msgid "<entry>2</entry>"
 msgstr ""
 
-#: random-bits.xml:287
+#: random-bits.xml:246
 #, no-c-format
 #. Tag: entry
 msgid "<entry>1</entry>"
 msgstr ""
 
-#: random-bits.xml:288 random-bits.xml:301
+#: random-bits.xml:247 random-bits.xml:260
 #, no-c-format
 #. Tag: entry
 msgid "<entry>3</entry>"
 msgstr ""
 
-#: random-bits.xml:292
+#: random-bits.xml:251
 #, no-c-format
 #. Tag: entry
 msgid "File server"
 msgstr ""
 
-#: random-bits.xml:293
+#: random-bits.xml:252
 #, no-c-format
 #. Tag: entry
 msgid "<entry>47</entry>"
 msgstr ""
 
-#: random-bits.xml:294
+#: random-bits.xml:253
 #, no-c-format
 #. Tag: entry
 msgid "<entry>24</entry>"
 msgstr ""
 
-#: random-bits.xml:295
+#: random-bits.xml:254
 #, no-c-format
 #. Tag: entry
 msgid "<entry>71</entry>"
 msgstr ""
 
-#: random-bits.xml:299
+#: random-bits.xml:258
 #, no-c-format
 #. Tag: entry
 msgid "Mail server"
 msgstr ""
 
-#: random-bits.xml:300
+#: random-bits.xml:259
 #, no-c-format
 #. Tag: entry
 msgid "<entry>10</entry>"
 msgstr ""
 
-#: random-bits.xml:302
+#: random-bits.xml:261
 #, no-c-format
 #. Tag: entry
 msgid "<entry>13</entry>"
 msgstr ""
 
-#: random-bits.xml:306
+#: random-bits.xml:265
 #, no-c-format
 #. Tag: entry
 msgid "SQL database"
 msgstr ""
 
-#: random-bits.xml:307
+#: random-bits.xml:266
 #, no-c-format
 #. Tag: entry
 msgid "<entry>66</entry>"
 msgstr ""
 
-#: random-bits.xml:308
+#: random-bits.xml:267
 #, no-c-format
 #. Tag: entry
 msgid "<entry>21</entry>"
 msgstr ""
 
-#: random-bits.xml:309
+#: random-bits.xml:268
 #, no-c-format
 #. Tag: entry
 msgid "<entry>87</entry>"
 msgstr ""
 
-#: random-bits.xml:315
+#: random-bits.xml:274
 #, no-c-format
 #. Tag: para
 msgid "The <emphasis>Desktop</emphasis> task will install both the Gnome and KDE desktop environments."
 msgstr ""
 
-#: random-bits.xml:322
+#: random-bits.xml:281
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: random-bits.xml:337
+#: random-bits.xml:296
 #, no-c-format
 #. Tag: title
 msgid "Installing &debian; from a Unix/Linux System"
 msgstr ""
 
-#: random-bits.xml:339
+#: random-bits.xml:298
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: random-bits.xml:351
+#: random-bits.xml:310
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: random-bits.xml:363
+#: random-bits.xml:322
 #, no-c-format
 #. Tag: title
 msgid "Getting Started"
 msgstr ""
 
-#: random-bits.xml:364
+#: random-bits.xml:323
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: random-bits.xml:371
+#: random-bits.xml:330
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1018,7 +627,7 @@ msgid ""
       "</screen></informalexample> To create an ext2 file system instead, omit <userinput>-j</userinput>."
 msgstr ""
 
-#: random-bits.xml:381
+#: random-bits.xml:340
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1029,7 +638,7 @@ msgid ""
       "</screen></informalexample> Mount one partition as <filename>/mnt/debinst</filename> (the installation point, to be the root (<filename>/</filename>) filesystem on your new system). The mount point name is strictly arbitrary, it is referenced later below."
 msgstr ""
 
-#: random-bits.xml:393
+#: random-bits.xml:352
 #, no-c-format
 #. Tag: screen
 msgid ""
@@ -1037,31 +646,31 @@ msgid ""
       "# mount /dev/hda6 /mnt/debinst"
 msgstr ""
 
-#: random-bits.xml:396
+#: random-bits.xml:355
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: random-bits.xml:406
+#: random-bits.xml:365
 #, no-c-format
 #. Tag: title
 msgid "Install <command>debootstrap</command>"
 msgstr ""
 
-#: random-bits.xml:407
+#: random-bits.xml:366
 #, no-c-format
 #. Tag: para
 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>. 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 ""
 
-#: random-bits.xml:417
+#: random-bits.xml:376
 #, no-c-format
 #. Tag: para
 msgid "If you have an rpm-based system, you can use alien to convert the .deb into .rpm, or download an rpm-ized version at <ulink url=\"http://people.debian.org/~blade/install/debootstrap\"></ulink>"
 msgstr ""
 
-#: random-bits.xml:423
+#: random-bits.xml:382
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1071,7 +680,7 @@ msgid ""
       "</screen></informalexample> The <command>debootstrap</command> binary is located in the Debian archive (be sure to select the proper file for your architecture). Download the <command>debootstrap</command> .deb from the <ulink url=\"http://ftp.debian.org/debian/pool/main/d/debootstrap/\"> pool</ulink>, copy the package to the work folder, and extract the binary files from it. You will need to have root privileges to install the binaries."
 msgstr ""
 
-#: random-bits.xml:438
+#: random-bits.xml:397
 #, no-c-format
 #. Tag: screen
 msgid ""
@@ -1080,37 +689,37 @@ msgid ""
       "# zcat /full-path-to-work/work/data.tar.gz | tar xv"
 msgstr ""
 
-#: random-bits.xml:440
+#: random-bits.xml:399
 #, no-c-format
 #. Tag: para
 msgid "Note that running <command>debootstrap</command> may require you to have a minimal version of <classname>glibc</classname> installed (currently GLIBC_2.3). <command>debootstrap</command> itself is a shell script, but it calls various utilities that require <classname>glibc</classname>."
 msgstr ""
 
-#: random-bits.xml:451
+#: random-bits.xml:410
 #, no-c-format
 #. Tag: title
 msgid "Run <command>debootstrap</command>"
 msgstr ""
 
-#: random-bits.xml:452
+#: random-bits.xml:411
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: random-bits.xml:461
+#: random-bits.xml:420
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: random-bits.xml:467
+#: random-bits.xml:426
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: random-bits.xml:484
+#: random-bits.xml:443
 #, no-c-format
 #. Tag: screen
 msgid ""
@@ -1118,31 +727,31 @@ msgid ""
       "     /mnt/debinst http://http.us.debian.org/debian"
 msgstr ""
 
-#: random-bits.xml:490
+#: random-bits.xml:449
 #, no-c-format
 #. Tag: title
 msgid "Configure The Base System"
 msgstr ""
 
-#: random-bits.xml:491
+#: random-bits.xml:450
 #, no-c-format
 #. Tag: para
 msgid "Now you've got a real Debian system, though rather lean, on disk. <command>Chroot</command> into it:"
 msgstr ""
 
-#: random-bits.xml:496
+#: random-bits.xml:455
 #, no-c-format
 #. Tag: screen
 msgid "# LANG= chroot /mnt/debinst /bin/bash"
 msgstr ""
 
-#: random-bits.xml:501
+#: random-bits.xml:460
 #, no-c-format
 #. Tag: title
 msgid "Mount Partitions"
 msgstr ""
 
-#: random-bits.xml:502
+#: random-bits.xml:461
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1170,55 +779,55 @@ msgid ""
       "</screen></informalexample> You can mount the proc file system multiple times and to arbitrary locations, though <filename>/proc</filename> is customary. If you didn't use <userinput>mount -a</userinput>, be sure to mount proc before continuing:"
 msgstr ""
 
-#: random-bits.xml:522
+#: random-bits.xml:481
 #, no-c-format
 #. Tag: screen
 msgid "# mount -t proc proc /proc"
 msgstr ""
 
-#: random-bits.xml:524
+#: random-bits.xml:483
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: random-bits.xml:530
+#: random-bits.xml:489
 #, no-c-format
 #. Tag: screen
 msgid "# mount -t proc proc /mnt/debinst/proc"
 msgstr ""
 
-#: random-bits.xml:536
+#: random-bits.xml:495
 #, no-c-format
 #. Tag: title
 msgid "Configure Keyboard"
 msgstr ""
 
-#: random-bits.xml:537
+#: random-bits.xml:496
 #, no-c-format
 #. Tag: para
 msgid "To configure your keyboard:"
 msgstr ""
 
-#: random-bits.xml:541
+#: random-bits.xml:500
 #, no-c-format
 #. Tag: screen
 msgid "# dpkg-reconfigure console-data"
 msgstr ""
 
-#: random-bits.xml:543
+#: random-bits.xml:502
 #, no-c-format
 #. Tag: para
 msgid "Note that the keyboard cannot be set while in the chroot, but will be configured for the next reboot."
 msgstr ""
 
-#: random-bits.xml:552
+#: random-bits.xml:511
 #, no-c-format
 #. Tag: title
 msgid "Configure Networking"
 msgstr ""
 
-#: random-bits.xml:553
+#: random-bits.xml:512
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1261,47 +870,29 @@ msgid ""
       "</screen></informalexample> If you have multiple network cards, you should arrange the names of driver modules in the <filename>/etc/modules</filename> file into the desired order. Then during boot, each card will be associated with the interface name (eth0, eth1, etc.) that you expect."
 msgstr ""
 
-#: random-bits.xml:589
-#, no-c-format
-#. Tag: title
-msgid "Configure Timezone, Users, and APT"
-msgstr ""
-
-#: random-bits.xml:590
-#, no-c-format
-#. Tag: para
-msgid "Set your timezone, add a normal user, and choose your <command>apt</command> sources by running"
-msgstr ""
-
-#: random-bits.xml:595
-#, no-c-format
-#. Tag: screen
-msgid "# /usr/sbin/base-config new"
-msgstr ""
-
-#: random-bits.xml:601
+#: random-bits.xml:548
 #, no-c-format
 #. Tag: title
 msgid "Configure Locales"
 msgstr ""
 
-#: random-bits.xml:602
+#: random-bits.xml:549
 #, no-c-format
 #. Tag: para
 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"
       "# dpkg-reconfigure locales\n"
-      "</screen></informalexample> NOTE: Apt must be configured before, ie. during the base-config phase. Before using locales with character sets other than ASCII or latin1, please consult the appropriate localization HOWTO."
+      "</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."
 msgstr ""
 
-#: random-bits.xml:618
+#: random-bits.xml:566
 #, no-c-format
 #. Tag: title
 msgid "Install a Kernel"
 msgstr ""
 
-#: random-bits.xml:619
+#: random-bits.xml:567
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1310,37 +901,37 @@ msgid ""
       "</screen></informalexample> Then install your choice using its package name."
 msgstr ""
 
-#: random-bits.xml:628
+#: random-bits.xml:576
 #, no-c-format
 #. Tag: screen
 msgid "# apt-get install kernel-image-<replaceable>2.X.X-arch-etc</replaceable>"
 msgstr ""
 
-#: random-bits.xml:634
+#: random-bits.xml:582
 #, no-c-format
 #. Tag: title
 msgid "Set up the Boot Loader"
 msgstr ""
 
-#: random-bits.xml:635
+#: random-bits.xml:583
 #, no-c-format
 #. Tag: para
 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."
 msgstr ""
 
-#: random-bits.xml:642
+#: random-bits.xml:590
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: random-bits.xml:653
+#: random-bits.xml:601
 #, no-c-format
 #. Tag: para
 msgid "Here is a basic <filename>/etc/lilo.conf</filename> as an example:"
 msgstr ""
 
-#: random-bits.xml:657
+#: random-bits.xml:605
 #, no-c-format
 #. Tag: screen
 msgid ""
@@ -1353,13 +944,13 @@ msgid ""
       "label=Debian"
 msgstr ""
 
-#: random-bits.xml:659
+#: random-bits.xml:607
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: random-bits.xml:669
+#: random-bits.xml:617
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1375,79 +966,79 @@ msgid ""
       "</screen></informalexample> On some machines, you may need to use <userinput>ide0:</userinput> instead of <userinput>hd:</userinput>."
 msgstr ""
 
-#: random-bits.xml:687
+#: random-bits.xml:635
 #, no-c-format
 #. Tag: title
 msgid "Installing &debian; over Parallel Line IP (PLIP)"
 msgstr ""
 
-#: random-bits.xml:689
+#: random-bits.xml:637
 #, no-c-format
 #. Tag: para
 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)."
 msgstr ""
 
-#: random-bits.xml:697
+#: random-bits.xml:645
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: random-bits.xml:705
+#: random-bits.xml:653
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: random-bits.xml:710
+#: random-bits.xml:658
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: random-bits.xml:720
+#: random-bits.xml:668
 #, no-c-format
 #. Tag: title
 msgid "Requirements"
 msgstr ""
 
-#: random-bits.xml:723
+#: random-bits.xml:671
 #, no-c-format
 #. Tag: para
 msgid "A target computer, called <emphasis>target</emphasis>, where Debian will be installed."
 msgstr ""
 
-#: random-bits.xml:729
+#: random-bits.xml:677
 #, no-c-format
 #. Tag: para
 msgid "System installation media; see <xref linkend=\"installation-media\"/>."
 msgstr ""
 
-#: random-bits.xml:734
+#: random-bits.xml:682
 #, no-c-format
 #. Tag: para
 msgid "Another computer connected to the Internet, called <emphasis>source</emphasis>, that will function as the gateway."
 msgstr ""
 
-#: random-bits.xml:740
+#: random-bits.xml:688
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: random-bits.xml:752
+#: random-bits.xml:700
 #, no-c-format
 #. Tag: title
 msgid "Setting up source"
 msgstr ""
 
-#: random-bits.xml:753
+#: random-bits.xml:701
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: random-bits.xml:758
+#: random-bits.xml:706
 #, no-c-format
 #. Tag: screen
 msgid ""
@@ -1468,91 +1059,91 @@ msgid ""
       "echo 1 > /proc/sys/net/ipv4/ip_forward"
 msgstr ""
 
-#: random-bits.xml:764
+#: random-bits.xml:712
 #, no-c-format
 #. Tag: title
 msgid "Installing target"
 msgstr ""
 
-#: random-bits.xml:765
+#: random-bits.xml:713
 #, no-c-format
 #. Tag: para
 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."
 msgstr ""
 
-#: random-bits.xml:777
+#: random-bits.xml:725
 #, no-c-format
 #. Tag: guimenuitem
 msgid "Load installer components"
 msgstr ""
 
-#: random-bits.xml:779
+#: random-bits.xml:727
 #, no-c-format
 #. Tag: para
 msgid "Select the <userinput>plip-modules</userinput> option from the list; this will make the PLIP drivers available to the installation system."
 msgstr ""
 
-#: random-bits.xml:787
+#: random-bits.xml:735
 #, no-c-format
 #. Tag: guimenuitem
 msgid "Detect network hardware"
 msgstr ""
 
-#: random-bits.xml:792
+#: random-bits.xml:740
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: random-bits.xml:801
+#: random-bits.xml:749
 #, no-c-format
 #. Tag: para
 msgid "Prompt for module parameters: Yes"
 msgstr ""
 
-#: random-bits.xml:806
+#: random-bits.xml:754
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: random-bits.xml:813
+#: random-bits.xml:761
 #, no-c-format
 #. Tag: para
 msgid "Additional parameters for module parport_pc: <userinput><replaceable>io=0x378 irq=7</replaceable></userinput>"
 msgstr ""
 
-#: random-bits.xml:819
+#: random-bits.xml:767
 #, no-c-format
 #. Tag: para
 msgid "Additional parameters for module plip: leave empty"
 msgstr ""
 
-#: random-bits.xml:829
+#: random-bits.xml:777
 #, no-c-format
 #. Tag: guimenuitem
 msgid "Configure the network"
 msgstr ""
 
-#: random-bits.xml:832
+#: random-bits.xml:780
 #, no-c-format
 #. Tag: para
 msgid "Auto-configure network with DHCP: No"
 msgstr ""
 
-#: random-bits.xml:837
+#: random-bits.xml:785
 #, no-c-format
 #. Tag: para
 msgid "IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>"
 msgstr ""
 
-#: random-bits.xml:842
+#: random-bits.xml:790
 #, no-c-format
 #. Tag: para
 msgid "Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></userinput>"
 msgstr ""
 
-#: random-bits.xml:848
+#: random-bits.xml:796
 #, no-c-format
 #. Tag: para
 msgid "Name server addresses: you can enter the same addresses used on source (see <filename>/etc/resolv.conf</filename>)"
diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot
index b5dd00082..f4c142710 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"
-"POT-Creation-Date: 2005-12-03 10:28+0000\n"
+"POT-Creation-Date: 2006-01-03 19:55+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"
@@ -77,13 +77,13 @@ msgstr ""
 #: using-d-i.xml:82
 #, no-c-format
 #. Tag: para
-msgid "Error messages are redirected to the third console. You can access this console by pressing <keycombo><keycap>Left Alt</keycap><keycap>F3</keycap></keycombo> (hold the left <keycap>Alt</keycap> key while pressing the <keycap>F3</keycap> function key); get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>."
+msgid "Error messages and logs are redirected to the fourth console. You can access this console by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo> (hold the left <keycap>Alt</keycap> key while pressing the <keycap>F4</keycap> function key); get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>."
 msgstr ""
 
 #: using-d-i.xml:92
 #, no-c-format
 #. Tag: para
-msgid "These messages can also be found in <filename>/var/log/messages</filename>. After installation, this log is copied to <filename>/var/log/debian-installer/messages</filename> on your new system. Other installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/debian-installer/</filename> after the computer has been booted into the installed system."
+msgid "These messages can also be found in <filename>/var/log/syslog</filename>. After installation, this log is copied to <filename>/var/log/installer/syslog</filename> on your new system. Other installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/debian/</filename> after the computer has been booted into the installed system."
 msgstr ""
 
 #: using-d-i.xml:106
@@ -119,652 +119,634 @@ msgstr ""
 #: using-d-i.xml:137
 #, no-c-format
 #. Tag: term
-msgid "languagechooser"
-msgstr ""
-
-#: using-d-i.xml:137
-#, no-c-format
-#. Tag: para
-msgid "Shows a list of languages and language variants. The installer will display messages in the chosen language, unless the translation for that language is not complete. When a translation is not complete, English messages are shown."
-msgstr ""
-
-#: using-d-i.xml:148
-#, no-c-format
-#. Tag: term
-msgid "countrychooser"
-msgstr ""
-
-#: using-d-i.xml:148
-#, no-c-format
-#. Tag: para
-msgid "Shows a list of countries. The user may choose the country he lives in."
-msgstr ""
-
-#: using-d-i.xml:157
-#, no-c-format
-#. Tag: term
 msgid "localechooser"
 msgstr ""
 
-#: using-d-i.xml:157
+#: using-d-i.xml:137
 #, no-c-format
 #. Tag: para
 msgid "Allows the user to select localization options for the installation and the installed system: language, country and locales. The installer will display messages in the selected language, unless the translation for that language is not complete in which case some messages may be shown in English."
 msgstr ""
 
-#: using-d-i.xml:169
+#: using-d-i.xml:149
 #, no-c-format
 #. Tag: term
 msgid "kbd-chooser"
 msgstr ""
 
-#: using-d-i.xml:169
+#: using-d-i.xml:149
 #, no-c-format
 #. Tag: para
 msgid "Shows a list of keyboards, from which the user chooses the model which matches his own."
 msgstr ""
 
-#: using-d-i.xml:178
+#: using-d-i.xml:158
 #, no-c-format
 #. Tag: term
 msgid "hw-detect"
 msgstr ""
 
-#: using-d-i.xml:178
+#: using-d-i.xml:158
 #, no-c-format
 #. Tag: para
 msgid "Automatically detects most of the system's hardware, including network cards, disk drives, and PCMCIA."
 msgstr ""
 
-#: using-d-i.xml:187
+#: using-d-i.xml:167
 #, no-c-format
 #. Tag: term
 msgid "cdrom-detect"
 msgstr ""
 
-#: using-d-i.xml:187
+#: using-d-i.xml:167
 #, no-c-format
 #. Tag: para
 msgid "Looks for and mounts a Debian installation CD."
 msgstr ""
 
-#: using-d-i.xml:195
+#: using-d-i.xml:175
 #, no-c-format
 #. Tag: term
 msgid "netcfg"
 msgstr ""
 
-#: using-d-i.xml:195
+#: using-d-i.xml:175
 #, no-c-format
 #. Tag: para
 msgid "Configures the computer's network connections so it can communicate over the internet."
 msgstr ""
 
-#: using-d-i.xml:204
+#: using-d-i.xml:184
 #, no-c-format
 #. Tag: term
 msgid "iso-scan"
 msgstr ""
 
-#: using-d-i.xml:204
+#: using-d-i.xml:184
 #, no-c-format
 #. Tag: para
 msgid "Looks for ISO file systems, which may be on a CD-ROM or on the hard drive."
 msgstr ""
 
-#: using-d-i.xml:213
+#: using-d-i.xml:193
 #, no-c-format
 #. Tag: term
 msgid "choose-mirror"
 msgstr ""
 
-#: using-d-i.xml:213
+#: using-d-i.xml:193
 #, no-c-format
 #. Tag: para
 msgid "Presents a list of Debian archive mirrors. The user may choose the source of his installation packages."
 msgstr ""
 
-#: using-d-i.xml:222
+#: using-d-i.xml:202
 #, no-c-format
 #. Tag: term
 msgid "cdrom-checker"
 msgstr ""
 
-#: using-d-i.xml:222
+#: using-d-i.xml:202
 #, no-c-format
 #. Tag: para
 msgid "Checks integrity of a CD-ROM. This way the user may assure him/herself that the installation CD-ROM was not corrupted."
 msgstr ""
 
-#: using-d-i.xml:231
+#: using-d-i.xml:211
 #, no-c-format
 #. Tag: term
 msgid "lowmem"
 msgstr ""
 
-#: using-d-i.xml:231
+#: using-d-i.xml:211
 #, no-c-format
 #. Tag: para
 msgid "Lowmem tries to detect systems with low memory and then does various tricks to remove unnecessary parts of &d-i; from the memory (at the cost of some features)."
 msgstr ""
 
-#: using-d-i.xml:241
+#: using-d-i.xml:221
 #, no-c-format
 #. Tag: term
 msgid "anna"
 msgstr ""
 
-#: using-d-i.xml:241
+#: using-d-i.xml:221
 #, no-c-format
 #. Tag: para
 msgid "Anna's Not Nearly APT. Installs packages which have been retrieved from the chosen mirror or CD."
 msgstr ""
 
-#: using-d-i.xml:250
+#: using-d-i.xml:230
 #, no-c-format
 #. Tag: term
 msgid "partman"
 msgstr ""
 
-#: using-d-i.xml:250
+#: using-d-i.xml:230
 #, no-c-format
 #. Tag: para
 msgid "Allows the user to partition disks attached to the system, create file systems on the selected partitions, and attach them to the mountpoints. Included are also interesting features like a fully automatic mode or LVM support. This is the preferred partitioning tool in Debian."
 msgstr ""
 
-#: using-d-i.xml:262
+#: using-d-i.xml:242
 #, no-c-format
 #. Tag: term
 msgid "autopartkit"
 msgstr ""
 
-#: using-d-i.xml:262
+#: using-d-i.xml:242
 #, no-c-format
 #. Tag: para
 msgid "Automatically partitions an entire disk according to preset user preferences."
 msgstr ""
 
-#: using-d-i.xml:271
+#: using-d-i.xml:251
 #, no-c-format
 #. Tag: term
 msgid "partitioner"
 msgstr ""
 
-#: using-d-i.xml:271
+#: using-d-i.xml:251
 #, no-c-format
 #. Tag: para
 msgid "Allows the user to partition disks attached to the system. A partitioning program appropriate to your computer's architecture is chosen."
 msgstr ""
 
-#: using-d-i.xml:281
+#: using-d-i.xml:261
 #, no-c-format
 #. Tag: term
 msgid "partconf"
 msgstr ""
 
-#: using-d-i.xml:281
+#: using-d-i.xml:261
 #, no-c-format
 #. Tag: para
 msgid "Displays a list of partitions, and creates file systems on the selected partitions according to user instructions."
 msgstr ""
 
-#: using-d-i.xml:290
+#: using-d-i.xml:270
 #, no-c-format
 #. Tag: term
 msgid "lvmcfg"
 msgstr ""
 
-#: using-d-i.xml:290
+#: using-d-i.xml:270
 #, no-c-format
 #. Tag: para
 msgid "Helps the user with the configuration of the <firstterm>LVM</firstterm> (Logical Volume Manager)."
 msgstr ""
 
-#: using-d-i.xml:299
+#: using-d-i.xml:279
 #, no-c-format
 #. Tag: term
 msgid "mdcfg"
 msgstr ""
 
-#: using-d-i.xml:299
+#: using-d-i.xml:279
 #, no-c-format
 #. Tag: para
 msgid "Allows the user to setup Software <firstterm>RAID</firstterm> (Redundant Array of Inexpensive Disks). This Software RAID is usually superior to the cheap IDE (pseudo hardware) RAID controllers found on newer motherboards."
 msgstr ""
 
-#: using-d-i.xml:310
+#: using-d-i.xml:290
 #, no-c-format
 #. Tag: term
-msgid "base-installer"
+msgid "tzsetup"
 msgstr ""
 
-#: using-d-i.xml:310
+#: using-d-i.xml:290
 #, no-c-format
 #. Tag: para
-msgid "Installs the most basic set of packages which would allow the computer to operate under Linux when rebooted."
+msgid "Selects the time zone, based on the location selected earlier"
 msgstr ""
 
-#: using-d-i.xml:319
+#: using-d-i.xml:298
 #, no-c-format
 #. Tag: term
-msgid "os-prober"
+msgid "clock-setup"
 msgstr ""
 
-#: using-d-i.xml:319
+#: using-d-i.xml:298
 #, no-c-format
 #. Tag: para
-msgid "Detects currently installed operating systems on the computer and passes this information to the bootloader-installer, which may offer you an ability to add discovered operating systems to the bootloader's start menu. This way the user could easily choose at the boot time which operating system to start."
+msgid "Determines whether the clock is set to UTC or not."
 msgstr ""
 
-#: using-d-i.xml:331
+#: using-d-i.xml:306
 #, no-c-format
 #. Tag: term
-msgid "bootloader-installer"
+msgid "user-setup"
 msgstr ""
 
-#: using-d-i.xml:331
+#: using-d-i.xml:306
 #, no-c-format
 #. Tag: para
-msgid "Installs a boot loader program on the hard disk, which is necessary for the computer to start up using Linux without using a floppy or CD-ROM. Many boot loaders allow the user to choose an alternate operating system each time the computer boots."
+msgid "Sets up the root password, and adds a non-root user."
 msgstr ""
 
-#: using-d-i.xml:342
+#: using-d-i.xml:314
 #, no-c-format
 #. Tag: term
-msgid "base-config"
+msgid "base-installer"
 msgstr ""
 
-#: using-d-i.xml:342
+#: using-d-i.xml:314
 #, no-c-format
 #. Tag: para
-msgid "Provides dialogs for setting up the base system packages according to user preferences. This is normally done after rebooting the computer; it is the <quote>first run</quote> of the new Debian system."
+msgid "Installs the most basic set of packages which would allow the computer to operate under Linux when rebooted."
 msgstr ""
 
-#: using-d-i.xml:352
+#: using-d-i.xml:323
 #, no-c-format
 #. Tag: term
-msgid "shell"
+msgid "apt-setup"
 msgstr ""
 
-#: using-d-i.xml:352
+#: using-d-i.xml:323
 #, no-c-format
 #. Tag: para
-msgid "Allows the user to execute a shell from the menu, or in the second console."
+msgid "Configures apt, mostly automatically, based on what media the installer is running from."
 msgstr ""
 
-#: using-d-i.xml:361
+#: using-d-i.xml:332
 #, no-c-format
 #. Tag: term
-msgid "bugreporter"
+msgid "pkgsel"
+msgstr ""
+
+#: using-d-i.xml:332
+#, no-c-format
+#. Tag: para
+msgid "Uses tasksel to select and install additional software."
 msgstr ""
 
-#: using-d-i.xml:361
+#: using-d-i.xml:340
 #, no-c-format
 #. Tag: term
-msgid "save-logs"
+msgid "os-prober"
 msgstr ""
 
-#: using-d-i.xml:361
+#: using-d-i.xml:340
 #, no-c-format
 #. Tag: para
-msgid "Provides a way for the user to record information on a floppy disk<phrase condition=\"etch\">, network, hard disk, or other media</phrase> when trouble is encountered, in order to accurately report installer software problems to Debian developers later."
+msgid "Detects currently installed operating systems on the computer and passes this information to the bootloader-installer, which may offer you an ability to add discovered operating systems to the bootloader's start menu. This way the user could easily choose at the boot time which operating system to start."
 msgstr ""
 
-#: using-d-i.xml:380
+#: using-d-i.xml:352
 #, no-c-format
-#. Tag: title
-msgid "Using Individual Components"
+#. Tag: term
+msgid "bootloader-installer"
 msgstr ""
 
-#: using-d-i.xml:381
+#: using-d-i.xml:352
 #, no-c-format
 #. Tag: para
-msgid "In this section we will describe each installer component in detail. The components have been grouped into stages that should be recognizable for users. They are presented in the order they appear during the install. Note that not all modules will be used for every installation; which modules are actually used depends on the installation method you use and on your hardware."
+msgid "The various bootloader installers each install a boot loader program on the hard disk, which is necessary for the computer to start up using Linux without using a floppy or CD-ROM. Many boot loaders allow the user to choose an alternate operating system each time the computer boots."
 msgstr ""
 
-#: using-d-i.xml:393
+#: using-d-i.xml:363
 #, no-c-format
-#. Tag: title
-msgid "Setting up Debian Installer and Hardware Configuration"
+#. Tag: term
+msgid "shell"
 msgstr ""
 
-#: using-d-i.xml:394
+#: using-d-i.xml:363
 #, no-c-format
 #. Tag: para
-msgid "Let's assume the Debian Installer has booted and you are facing its first screen. At this time, the capabilities of &d-i; are still quite limited. It doesn't know much about your hardware, preferred language, or even the task it should perform. Don't worry. Because &d-i; is quite clever, it can automatically probe your hardware, locate the rest of its components and upgrade itself to a capable installation system. However, you still need to help &d-i; with some information it can't determine automatically (like selecting your preferred language, keyboard layout or desired network mirror)."
+msgid "Allows the user to execute a shell from the menu, or in the second console."
 msgstr ""
 
-#: using-d-i.xml:407
+#: using-d-i.xml:372
 #, no-c-format
-#. Tag: para
-msgid "You will notice that &d-i; performs <firstterm>hardware detection</firstterm> several times during this stage. The first time is targeted specifically at the hardware needed to load installer components (e.g. your CD-ROM or network card). As not all drivers may be available during this first run, hardware detection needs to be repeated later in the process."
+#. Tag: term
+msgid "save-logs"
 msgstr ""
 
-#: using-d-i.xml:422
+#: using-d-i.xml:372
 #, no-c-format
-#. Tag: title
-msgid "Check available memory"
+#. Tag: para
+msgid "Provides a way for the user to record information on a floppy disk, network, hard disk, or other media when trouble is encountered, in order to accurately report installer software problems to Debian developers later."
 msgstr ""
 
-#: using-d-i.xml:424
+#: using-d-i.xml:390
 #, no-c-format
-#. Tag: para
-msgid "One of the first things &d-i; does, is to check available memory. If the available memory is limited, this component will make some changes in the installation process which hopefully will allow you to install &debian; on your system."
+#. Tag: title
+msgid "Using Individual Components"
 msgstr ""
 
-#: using-d-i.xml:431
+#: using-d-i.xml:391
 #, no-c-format
 #. Tag: para
-msgid "During a low memory install, not all components will be available. One of the limitations is that you won't be able to choose a language for the installation."
+msgid "In this section we will describe each installer component in detail. The components have been grouped into stages that should be recognizable for users. They are presented in the order they appear during the install. Note that not all modules will be used for every installation; which modules are actually used depends on the installation method you use and on your hardware."
 msgstr ""
 
-#: using-d-i.xml:446
+#: using-d-i.xml:403
 #, no-c-format
 #. Tag: title
-msgid "Language selection"
+msgid "Setting up Debian Installer and Hardware Configuration"
 msgstr ""
 
-#: using-d-i.xml:448
+#: using-d-i.xml:404
 #, no-c-format
 #. Tag: para
-msgid "As the first step of the installation, select the language in which you want the installation process to proceed. The language names are listed in both English (left side) and in the language itself (right side); the names on the right side are also shown in the proper script for the language. The list is sorted on the English names."
+msgid "Let's assume the Debian Installer has booted and you are facing its first screen. At this time, the capabilities of &d-i; are still quite limited. It doesn't know much about your hardware, preferred language, or even the task it should perform. Don't worry. Because &d-i; is quite clever, it can automatically probe your hardware, locate the rest of its components and upgrade itself to a capable installation system. However, you still need to help &d-i; with some information it can't determine automatically (like selecting your preferred language, keyboard layout or desired network mirror)."
 msgstr ""
 
-#: using-d-i.xml:456
+#: using-d-i.xml:417
 #, no-c-format
 #. Tag: para
-msgid "The language you choose will be used for the rest of the installation process, provided a translation of the different dialogs is available. If no valid translation is available for the selected language, the installer will default to English. The selected language will also be used to help select a suitable keyboard layout."
+msgid "You will notice that &d-i; performs <firstterm>hardware detection</firstterm> several times during this stage. The first time is targeted specifically at the hardware needed to load installer components (e.g. your CD-ROM or network card). As not all drivers may be available during this first run, hardware detection needs to be repeated later in the process."
 msgstr ""
 
-#: using-d-i.xml:473
+#: using-d-i.xml:432
 #, no-c-format
 #. Tag: title
-msgid "Country selection"
+msgid "Check available memory"
 msgstr ""
 
-#: using-d-i.xml:475
+#: using-d-i.xml:434
 #, no-c-format
 #. Tag: para
-msgid "If you selected a language in <xref linkend=\"lang-chooser\"/> which has more than one country associated with it (true for Chinese, English, French, and many other languages), you can specify the country here. If you choose <guimenuitem>Other</guimenuitem> at the bottom of the list, you will be presented with a list of all countries, grouped by continent."
+msgid "One of the first things &d-i; does, is to check available memory. If the available memory is limited, this component will make some changes in the installation process which hopefully will allow you to install &debian; on your system."
 msgstr ""
 
-#: using-d-i.xml:483
+#: using-d-i.xml:441
 #, no-c-format
 #. Tag: para
-msgid "This selection will be used later in the installation process to pick the default timezone and a Debian mirror appropriate for your geographic location. If the defaults proposed by the installer are not suitable, you can make a different choice. The selected country, together with the selected language, may also affect locale settings for your new Debian system."
+msgid "During a low memory install, not all components will be available. One of the limitations is that you won't be able to choose a language for the installation."
 msgstr ""
 
-#: using-d-i.xml:500
+#: using-d-i.xml:456
 #, no-c-format
 #. Tag: title
 msgid "Selecting Localization Options"
 msgstr ""
 
-#: using-d-i.xml:502
+#: using-d-i.xml:458
 #, no-c-format
 #. Tag: para
 msgid "In most cases the first questions you will be asked concern the selection of localization options to be used both for the installation and for the installed system. The localization options consist of language, country and locales."
 msgstr ""
 
-#: using-d-i.xml:509
+#: using-d-i.xml:465
 #, no-c-format
 #. Tag: para
 msgid "The language you choose will be used for the rest of the installation process, provided a translation of the different dialogs is available. If no valid translation is available for the selected language, the installer will default to English."
 msgstr ""
 
-#: using-d-i.xml:516
+#: using-d-i.xml:472
 #, no-c-format
 #. Tag: para
 msgid "The selected country will be used later in the installation process to pick the default timezone and a Debian mirror appropriate for your geographic location. Language and country together will be used to set the default locale for your system and to help select your keyboard."
 msgstr ""
 
-#: using-d-i.xml:523
+#: using-d-i.xml:479
 #, no-c-format
 #. Tag: para
 msgid "You will first be asked to select your preferred language. The language names are listed in both English (left side) and in the language itself (right side); the names on the right side are also shown in the proper script for the language. The list is sorted on the English names. At the top of the list is an extra option that allows you to select the <quote>C</quote> locale instead of a language. Choosing the <quote>C</quote> locale will result in the installation proceding in English; the installed system will have no localization support as the <classname>locales</classname> package will not be installed."
 msgstr ""
 
-#: using-d-i.xml:535
+#: using-d-i.xml:491
 #, no-c-format
 #. Tag: para
 msgid "If you selected a language that is recognized as an official language for more than one country<footnote> <para> In technical terms: where multiple locales exist for that language with differing country codes. </para> </footnote>, you will next be asked to select a country. If you choose <guimenuitem>Other</guimenuitem> at the bottom of the list, you will be presented with a list of all countries, grouped by continent. If the language has only one country associated with it, that country will be selected automatically."
 msgstr ""
 
-#: using-d-i.xml:553
+#: using-d-i.xml:509
 #, no-c-format
 #. Tag: para
 msgid "A default locale will be selected based on the selected language and country. If you are installing at medium or low priority, you will have the option of selecting a different default locale and of selecting additional locales to be generated for the installed system."
 msgstr ""
 
-#: using-d-i.xml:568
+#: using-d-i.xml:524
 #, no-c-format
 #. Tag: title
 msgid "Choosing a Keyboard"
 msgstr ""
 
-#: using-d-i.xml:570
+#: using-d-i.xml:526
 #, no-c-format
 #. Tag: para
 msgid "Keyboards are often tailored to the characters used in a language. Select a layout that conforms to the keyboard you are using, or select something close if the keyboard layout you want isn't represented. Once the system installation is complete, you'll be able to select a keyboard layout from a wider range of choices (run <command>kbdconfig</command> as root after you have completed the installation)."
 msgstr ""
 
-#: using-d-i.xml:580
+#: using-d-i.xml:536
 #, no-c-format
 #. Tag: para
 msgid "Move the highlight to the keyboard selection you desire and press &enterkey;. Use the arrow keys to move the highlight &mdash; they are in the same place in all national language keyboard layouts, so they are independent of the keyboard configuration. An 'extended' keyboard is one with <keycap>F1</keycap> through <keycap>F10</keycap> keys along the top row."
 msgstr ""
 
-#: using-d-i.xml:589
+#: using-d-i.xml:545
 #, no-c-format
 #. Tag: para
 msgid "On DECstations there is currently no loadable keymap available, so you have to skip the keyboard selection and keep the default kernel keymap (LK201 US). This may change in the future as it depends on further Linux/MIPS kernel development."
 msgstr ""
 
-#: using-d-i.xml:596
+#: using-d-i.xml:552
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:608
+#: using-d-i.xml:564
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:617
+#: using-d-i.xml:573
 #, no-c-format
 #. Tag: para
 msgid "To get a working keyboard, you should boot the installer with parameter <userinput>debconf/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 ""
 
-#: using-d-i.xml:655
+#: using-d-i.xml:611
 #, no-c-format
 #. Tag: title
 msgid "Looking for the Debian Installer ISO Image"
 msgstr ""
 
-#: using-d-i.xml:656
+#: using-d-i.xml:612
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:663
+#: using-d-i.xml:619
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:680
+#: using-d-i.xml:636
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:687
+#: using-d-i.xml:643
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:708
+#: using-d-i.xml:664
 #, no-c-format
 #. Tag: title
 msgid "Configuring Network"
 msgstr ""
 
-#: using-d-i.xml:710
+#: using-d-i.xml:666
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:721
+#: using-d-i.xml:677
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:733
+#: using-d-i.xml:689
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:747
+#: using-d-i.xml:703
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:786
+#: using-d-i.xml:742
 #, no-c-format
 #. Tag: title
 msgid "Partitioning and Mount Point Selection"
 msgstr ""
 
-#: using-d-i.xml:787
+#: using-d-i.xml:743
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:809
+#: using-d-i.xml:765
 #, no-c-format
 #. Tag: title
 msgid "Partitioning Your Disks"
 msgstr ""
 
-#: using-d-i.xml:811
+#: using-d-i.xml:767
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:817
+#: using-d-i.xml:773
 #, no-c-format
 #. Tag: para
 msgid "First you will be given the opportunity to automatically partition either an entire drive, or free space on a drive. This is also called <quote>guided</quote> partitioning. If you do not want to autopartition, choose <guimenuitem>Manually edit partition table</guimenuitem> from the menu."
 msgstr ""
 
-#: using-d-i.xml:825
+#: using-d-i.xml:781
 #, no-c-format
 #. Tag: para
 msgid "If you choose guided partitioning, 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 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 ""
 
-#: using-d-i.xml:841
+#: using-d-i.xml:797
 #, no-c-format
 #. Tag: entry
 msgid "Partitioning scheme"
 msgstr ""
 
-#: using-d-i.xml:842
+#: using-d-i.xml:798
 #, no-c-format
 #. Tag: entry
 msgid "Minimum space"
 msgstr ""
 
-#: using-d-i.xml:843
+#: using-d-i.xml:799
 #, no-c-format
 #. Tag: entry
 msgid "Created partitions"
 msgstr ""
 
-#: using-d-i.xml:849
+#: using-d-i.xml:805
 #, no-c-format
 #. Tag: entry
 msgid "All files in one partition"
 msgstr ""
 
-#: using-d-i.xml:850
+#: using-d-i.xml:806
 #, no-c-format
 #. Tag: entry
 msgid "600MB"
 msgstr ""
 
-#: using-d-i.xml:851
+#: using-d-i.xml:807
 #, no-c-format
 #. Tag: entry
 msgid "<filename>/</filename>, swap"
 msgstr ""
 
-#: using-d-i.xml:853
+#: using-d-i.xml:809
 #, no-c-format
 #. Tag: entry
 msgid "Desktop machine"
 msgstr ""
 
-#: using-d-i.xml:854
+#: using-d-i.xml:810
 #, no-c-format
 #. Tag: entry
 msgid "500MB"
 msgstr ""
 
-#: using-d-i.xml:855
+#: using-d-i.xml:811
 #, no-c-format
 #. Tag: entry
 msgid "<filename>/</filename>, <filename>/home</filename>, swap"
 msgstr ""
 
-#: using-d-i.xml:859
+#: using-d-i.xml:815
 #, no-c-format
 #. Tag: entry
 msgid "Multi-user workstation"
 msgstr ""
 
-#: using-d-i.xml:860
+#: using-d-i.xml:816
 #, no-c-format
 #. Tag: entry
 msgid "<entry>1GB</entry>"
 msgstr ""
 
-#: using-d-i.xml:861
+#: using-d-i.xml:817
 #, no-c-format
 #. Tag: entry
 msgid "<filename>/</filename>, <filename>/home</filename>, <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap"
 msgstr ""
 
-#: using-d-i.xml:870
+#: using-d-i.xml:826
 #, no-c-format
 #. Tag: para
 msgid "If you chose an automatic 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 ""
 
-#: using-d-i.xml:878
+#: using-d-i.xml:834
 #, no-c-format
 #. Tag: para
 msgid "If you chose an automatic 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 ""
 
-#: using-d-i.xml:884
+#: using-d-i.xml:840
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:890
+#: using-d-i.xml:846
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -787,601 +769,829 @@ msgid ""
       "</screen></informalexample> This example shows two IDE harddrives divided into several partitions; the first disk has some free space. Each partition line consists of the partition number, its type, size, optional flags, file system, and mountpoint (if any)."
 msgstr ""
 
-#: using-d-i.xml:902
+#: using-d-i.xml:858
 #, no-c-format
 #. Tag: para
 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>, to run guided partitioning again or modify the proposed changes as described below for manual partitioning."
 msgstr ""
 
-#: using-d-i.xml:912
+#: using-d-i.xml:868
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:920
+#: using-d-i.xml:876
 #, no-c-format
 #. Tag: para
 msgid "If you select a pristine disk which doesn't have 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 ""
 
-#: using-d-i.xml:928
+#: using-d-i.xml:884
 #, no-c-format
 #. Tag: para
 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 the <command>partman</command>'s main screen."
 msgstr ""
 
-#: using-d-i.xml:946
+#: using-d-i.xml:902
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:957
+#: using-d-i.xml:913
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:965
+#: using-d-i.xml:921
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:971
+#: using-d-i.xml:927
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:979
+#: using-d-i.xml:935
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1007
+#: using-d-i.xml:963
 #, no-c-format
 #. Tag: title
 msgid "Configuring Logical Volume Manager (LVM)"
 msgstr ""
 
-#: using-d-i.xml:1008
+#: using-d-i.xml:964
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1016
+#: using-d-i.xml:972
 #, no-c-format
 #. Tag: para
 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 disc (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 discs."
 msgstr ""
 
-#: using-d-i.xml:1026
+#: using-d-i.xml:982
 #, no-c-format
 #. Tag: para
 msgid "Now when you realize you need more space for your old 160GB <filename>/home</filename> partition, you can simply add a new 300GB disc 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 ""
 
-#: using-d-i.xml:1037
+#: using-d-i.xml:993
 #, no-c-format
 #. Tag: para
 msgid "LVM setup in &d-i; is quite simple. At first, you have to mark your partitions to be used as physical volumes for LVM. (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 LVM</guimenuitem> </menuchoice>.) Then start the <command>lvmcfg</command> module (either directly from <command>partman</command> or from the &d-i;'s main menu) and combine physical volumes to volume group(s) under the <guimenuitem>Modify volume groups (VG)</guimenuitem> menu. After that, you should create logical volumes on the top of volume groups from the menu <guimenuitem>Modify logical volumes (LV)</guimenuitem>."
 msgstr ""
 
-#: using-d-i.xml:1052
-#, no-c-format
-#. Tag: para
-msgid "There is no widely accepted standard to identify partitions containing LVM data on Apple Power Macintosh hardware. On this particular hardware, the above procedure for creating physical volumes and volume groups will not work. There is a good workaround for this limitation, provided you are familiar with the underlying LVM tools."
-msgstr ""
-
-#: using-d-i.xml:1060
-#, no-c-format
-#. Tag: para
-msgid "To install using logical volumes on Power Macintosh hardware you should create all the disk partitions for your logical volumes as usual. In the <guimenu>Partition settings</guimenu> menu you should choose <menuchoice><guimenu>Use as:</guimenu> <guimenuitem>Do Not Use</guimenuitem></menuchoice> for these partitions (you will not be offered the option to use the partition as a physical volume). When you are done with creating all your partitions, you should start the logical volume manager as usual. However, since no physical volumes have been created you must now access the command shell available on the second virtual terminal (see <xref linkend=\"shell\"/>) and create them manually."
-msgstr ""
-
-#: using-d-i.xml:1074
-#, no-c-format
-#. Tag: para
-msgid "Use the <command>pvcreate</command> command at the shell command prompt to create a physical volume on each of your chosen partitions. Then use the <command>vgcreate</command> command to create each volume group you want. You can safely ignore any errors about incorrect metadata area header checksums and fsync failures while doing this. When you have finished creating all your volume groups, you should go back to the first virtual terminal and skip directly to the <command>lvmcfg</command> menu items for logical volume management. You will see your volume groups and you can create the logical volumes you need as usual."
-msgstr ""
-
-#: using-d-i.xml:1089
+#: using-d-i.xml:1008
 #, no-c-format
 #. Tag: para
 msgid "After returning from <command>lvmcfg</command> back to <command>partman</command>, you will see any created logical volumes in the same way as ordinary partitions (and you should treat them like that)."
 msgstr ""
 
-#: using-d-i.xml:1104
+#: using-d-i.xml:1023
 #, no-c-format
 #. Tag: title
 msgid "Configuring Multidisk Device (Software RAID)"
 msgstr ""
 
-#: using-d-i.xml:1105
+#: using-d-i.xml:1024
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1119
+#: using-d-i.xml:1038
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1127
+#: using-d-i.xml:1046
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1205
+#: using-d-i.xml:1124
 #, no-c-format
 #. Tag: entry
 msgid "Type"
 msgstr ""
 
-#: using-d-i.xml:1206
+#: using-d-i.xml:1125
 #, no-c-format
 #. Tag: entry
 msgid "Minimum Devices"
 msgstr ""
 
-#: using-d-i.xml:1207
+#: using-d-i.xml:1126
 #, no-c-format
 #. Tag: entry
 msgid "Spare Device"
 msgstr ""
 
-#: using-d-i.xml:1208
+#: using-d-i.xml:1127
 #, no-c-format
 #. Tag: entry
 msgid "Survives disk failure?"
 msgstr ""
 
-#: using-d-i.xml:1209
+#: using-d-i.xml:1128
 #, no-c-format
 #. Tag: entry
 msgid "Available Space"
 msgstr ""
 
-#: using-d-i.xml:1215
+#: using-d-i.xml:1134
 #, no-c-format
 #. Tag: entry
 msgid "RAID0"
 msgstr ""
 
-#: using-d-i.xml:1216 using-d-i.xml:1224
+#: using-d-i.xml:1135 using-d-i.xml:1143
 #, no-c-format
 #. Tag: entry
 msgid "<entry>2</entry>"
 msgstr ""
 
-#: using-d-i.xml:1217 using-d-i.xml:1218
+#: using-d-i.xml:1136 using-d-i.xml:1137
 #, no-c-format
 #. Tag: entry
 msgid "<entry>no</entry>"
 msgstr ""
 
-#: using-d-i.xml:1219
+#: using-d-i.xml:1138
 #, no-c-format
 #. Tag: entry
 msgid "Size of the smallest partition multiplied by number of devices in RAID"
 msgstr ""
 
-#: using-d-i.xml:1223
+#: using-d-i.xml:1142
 #, no-c-format
 #. Tag: entry
 msgid "RAID1"
 msgstr ""
 
-#: using-d-i.xml:1225 using-d-i.xml:1233
+#: using-d-i.xml:1144 using-d-i.xml:1152
 #, no-c-format
 #. Tag: entry
 msgid "optional"
 msgstr ""
 
-#: using-d-i.xml:1226 using-d-i.xml:1234
+#: using-d-i.xml:1145 using-d-i.xml:1153
 #, no-c-format
 #. Tag: entry
 msgid "<entry>yes</entry>"
 msgstr ""
 
-#: using-d-i.xml:1227
+#: using-d-i.xml:1146
 #, no-c-format
 #. Tag: entry
 msgid "Size of the smallest partition in RAID"
 msgstr ""
 
-#: using-d-i.xml:1231
+#: using-d-i.xml:1150
 #, no-c-format
 #. Tag: entry
 msgid "RAID5"
 msgstr ""
 
-#: using-d-i.xml:1232
+#: using-d-i.xml:1151
 #, no-c-format
 #. Tag: entry
 msgid "<entry>3</entry>"
 msgstr ""
 
-#: using-d-i.xml:1235
+#: using-d-i.xml:1154
 #, no-c-format
 #. Tag: entry
 msgid "Size of the smallest partition multiplied by (number of devices in RAID minus one)"
 msgstr ""
 
-#: using-d-i.xml:1243
+#: using-d-i.xml:1162
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1248
-#, no-c-format
-#. Tag: para
-msgid "There is no widely accepted standard to identify partitions containing RAID data on Apple Power Macintosh hardware. This means that &d-i; currently does not support setting up RAID on this platform."
-msgstr ""
-
-#: using-d-i.xml:1256
+#: using-d-i.xml:1167
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1265
+#: using-d-i.xml:1176
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1274
+#: using-d-i.xml:1185
 #, no-c-format
 #. Tag: para
 msgid "Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> from the main <command>partman</command> menu. 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 ""
 
-#: using-d-i.xml:1285
+#: using-d-i.xml:1196
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1292
+#: using-d-i.xml:1203
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1304
+#: using-d-i.xml:1215
 #, no-c-format
 #. Tag: para
 msgid "RAID5 has similar setup procedure as RAID1 with the exception that you need to use at least <emphasis>three</emphasis> active partitions."
 msgstr ""
 
-#: using-d-i.xml:1312
+#: using-d-i.xml:1223
 #, no-c-format
 #. Tag: para
 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 disk 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 ""
 
-#: using-d-i.xml:1321
+#: using-d-i.xml:1232
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1334
+#: using-d-i.xml:1245
+#, no-c-format
+#. Tag: title
+msgid "Setting up the System"
+msgstr ""
+
+#: using-d-i.xml:1246
+#, no-c-format
+#. Tag: para
+msgid "After partitioning the installer asks a few more questions that will be used to set up the system is is about the install."
+msgstr ""
+
+#: using-d-i.xml:1258
+#, no-c-format
+#. Tag: title
+msgid "Configuring Your Time Zone"
+msgstr ""
+
+#: using-d-i.xml:1260
+#, no-c-format
+#. Tag: para
+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 ""
+
+#: using-d-i.xml:1276
+#, no-c-format
+#. Tag: title
+msgid "Configuring the Clock"
+msgstr ""
+
+#: using-d-i.xml:1278
+#, no-c-format
+#. Tag: para
+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 ""
+
+#: using-d-i.xml:1285
+#, no-c-format
+#. Tag: para
+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=\"i386\">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 ""
+
+#: using-d-i.xml:1296
+#, no-c-format
+#. Tag: para
+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 ""
+
+#: using-d-i.xml:1312
+#, no-c-format
+#. Tag: title
+msgid "Setting Up Users And Passwords"
+msgstr ""
+
+#: using-d-i.xml:1315
+#, no-c-format
+#. Tag: title
+msgid "Set the Root Password"
+msgstr ""
+
+#: using-d-i.xml:1317
+#, no-c-format
+#. Tag: para
+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 ""
+
+#: using-d-i.xml:1325
+#, no-c-format
+#. Tag: para
+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 ""
+
+#: using-d-i.xml:1333
+#, no-c-format
+#. Tag: para
+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 ""
+
+#: using-d-i.xml:1343
+#, no-c-format
+#. Tag: title
+msgid "Create an Ordinary User"
+msgstr ""
+
+#: using-d-i.xml:1345
+#, no-c-format
+#. Tag: para
+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 ""
+
+#: using-d-i.xml:1352
+#, no-c-format
+#. Tag: para
+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 ""
+
+#: using-d-i.xml:1362
+#, no-c-format
+#. Tag: para
+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 ""
+
+#: using-d-i.xml:1369
+#, no-c-format
+#. Tag: para
+msgid "If at any point after installation you would like to create another account, use the <command>adduser</command> command."
+msgstr ""
+
+#: using-d-i.xml:1381
 #, no-c-format
 #. Tag: title
 msgid "Installing the Base System"
 msgstr ""
 
-#: using-d-i.xml:1335
+#: using-d-i.xml:1382
 #, no-c-format
 #. Tag: para
-msgid "Although this stage is the least problematic, it consumes most time 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."
+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 ""
 
-#: using-d-i.xml:1349
+#: using-d-i.xml:1396
 #, no-c-format
 #. Tag: title
 msgid "Base System Installation"
 msgstr ""
 
-#: using-d-i.xml:1351
+#: using-d-i.xml:1398
 #, no-c-format
 #. Tag: para
-msgid "During the Base installation, package unpacking and setup messages are redirected to <userinput>tty3</userinput>. You can access this terminal by pressing <keycombo><keycap>Left Alt</keycap><keycap>F3</keycap></keycombo>; get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>."
+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 ""
 
-#: using-d-i.xml:1361
+#: using-d-i.xml:1408
 #, no-c-format
 #. Tag: para
-msgid "The unpack/setup messages generated by the base installation are saved in <filename>/var/log/messages</filename> when the installation is performed over a serial console."
+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 ""
 
-#: using-d-i.xml:1367
+#: using-d-i.xml:1414
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1380
+#: using-d-i.xml:1427
+#, no-c-format
+#. Tag: title
+msgid "Installing Additional Software"
+msgstr ""
+
+#: using-d-i.xml:1428
+#, no-c-format
+#. Tag: para
+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 ""
+
+#: using-d-i.xml:1442
+#, no-c-format
+#. Tag: title
+msgid "Configuring apt"
+msgstr ""
+
+#: using-d-i.xml:1444
+#, no-c-format
+#. Tag: para
+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 ""
+
+#: using-d-i.xml:1468
+#, no-c-format
+#. Tag: para
+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 /etc/apt/sources.list, and you can examine and edit it to your liking after the install is complete."
+msgstr ""
+
+#: using-d-i.xml:1485
+#, no-c-format
+#. Tag: title
+msgid "Selecting and Installing Software"
+msgstr ""
+
+#: using-d-i.xml:1487
+#, no-c-format
+#. Tag: para
+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 ""
+
+#: using-d-i.xml:1496
+#, no-c-format
+#. Tag: para
+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 ""
+
+#: using-d-i.xml:1521
+#, no-c-format
+#. Tag: para
+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 ""
+
+#: using-d-i.xml:1528
+#, no-c-format
+#. Tag: para
+msgid "In the standard user interface of the installer, you can use the space bar to toggle selection of a task."
+msgstr ""
+
+#: using-d-i.xml:1535
+#, no-c-format
+#. Tag: para
+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 ""
+
+#: using-d-i.xml:1543
+#, no-c-format
+#. Tag: para
+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 ""
+
+#: using-d-i.xml:1552
+#, no-c-format
+#. Tag: title
+msgid "Configuring Your Mail Transport Agent"
+msgstr ""
+
+#: using-d-i.xml:1554
+#, no-c-format
+#. Tag: para
+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 ""
+
+#: using-d-i.xml:1562
+#, no-c-format
+#. Tag: para
+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 ""
+
+#: using-d-i.xml:1570
+#, no-c-format
+#. Tag: para
+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 ""
+
+#: using-d-i.xml:1579
+#, no-c-format
+#. Tag: term
+msgid "internet site"
+msgstr ""
+
+#: using-d-i.xml:1580
+#, no-c-format
+#. Tag: para
+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 ""
+
+#: using-d-i.xml:1591
+#, no-c-format
+#. Tag: term
+msgid "mail sent by smarthost"
+msgstr ""
+
+#: using-d-i.xml:1592
+#, no-c-format
+#. Tag: para
+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 ""
+
+#: using-d-i.xml:1605
+#, no-c-format
+#. Tag: term
+msgid "local delivery only"
+msgstr ""
+
+#: using-d-i.xml:1606
+#, no-c-format
+#. Tag: para
+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 ""
+
+#: using-d-i.xml:1619
+#, no-c-format
+#. Tag: term
+msgid "no configuration at this time"
+msgstr ""
+
+#: using-d-i.xml:1620
+#, no-c-format
+#. Tag: para
+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 ""
+
+#: using-d-i.xml:1631
+#, no-c-format
+#. Tag: para
+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 ""
+
+#: using-d-i.xml:1646
 #, no-c-format
 #. Tag: title
 msgid "Making Your System Bootable"
 msgstr ""
 
-#: using-d-i.xml:1382
+#: using-d-i.xml:1648
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1390
+#: using-d-i.xml:1656
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1405
+#: using-d-i.xml:1671
 #, no-c-format
 #. Tag: title
 msgid "Detecting other operating systems"
 msgstr ""
 
-#: using-d-i.xml:1407
+#: using-d-i.xml:1673
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1415
+#: using-d-i.xml:1681
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1427
-#, no-c-format
-#. Tag: para
-msgid "The installer may fail to detect other operating systems if the partitions on which they reside are mounted when the detection takes place. This may occur if you select a mountpoint (e.g. /win) for a partition containing another operating system in <command>partman</command>, or if you have mounted partitions manually from a console."
-msgstr ""
-
-#: using-d-i.xml:1444
+#: using-d-i.xml:1699
 #, no-c-format
 #. Tag: title
 msgid "Install <command>aboot</command> on a Hard Disk"
 msgstr ""
 
-#: using-d-i.xml:1445
+#: using-d-i.xml:1700
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1465
+#: using-d-i.xml:1720
 #, no-c-format
 #. Tag: title
 msgid "<command>palo</command>-installer"
 msgstr ""
 
-#: using-d-i.xml:1466
+#: using-d-i.xml:1721
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1475
+#: using-d-i.xml:1730
 #, no-c-format
 #. Tag: para
 msgid "hppa FIXME ( need more info )"
 msgstr ""
 
-#: using-d-i.xml:1487
+#: using-d-i.xml:1742
 #, no-c-format
 #. Tag: title
 msgid "Install the <command>Grub</command> Boot Loader on a Hard Disk"
 msgstr ""
 
-#: using-d-i.xml:1489
+#: using-d-i.xml:1744
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1495
+#: using-d-i.xml:1750
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1501
+#: using-d-i.xml:1756
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1515
+#: using-d-i.xml:1770
 #, no-c-format
 #. Tag: title
 msgid "Install the <command>LILO</command> Boot Loader on a Hard Disk"
 msgstr ""
 
-#: using-d-i.xml:1517
+#: using-d-i.xml:1772
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1527
+#: using-d-i.xml:1782
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1535
+#: using-d-i.xml:1790
 #, no-c-format
 #. Tag: para
 msgid "&d-i; presents you three choices where to install the <command>LILO</command> boot loader:"
 msgstr ""
 
-#: using-d-i.xml:1542
+#: using-d-i.xml:1797
 #, no-c-format
 #. Tag: term
 msgid "Master Boot Record (MBR)"
 msgstr ""
 
-#: using-d-i.xml:1542
+#: using-d-i.xml:1797
 #, no-c-format
 #. Tag: para
 msgid "This way the <command>LILO</command> will take complete control of the boot process."
 msgstr ""
 
-#: using-d-i.xml:1549
+#: using-d-i.xml:1804
 #, no-c-format
 #. Tag: term
 msgid "new Debian partition"
 msgstr ""
 
-#: using-d-i.xml:1549
+#: using-d-i.xml:1804
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1558
+#: using-d-i.xml:1813
 #, no-c-format
 #. Tag: term
 msgid "Other choice"
 msgstr ""
 
-#: using-d-i.xml:1558
+#: using-d-i.xml:1813
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1570
+#: using-d-i.xml:1825
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1587
+#: using-d-i.xml:1842
 #, no-c-format
 #. Tag: title
 msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk"
 msgstr ""
 
-#: using-d-i.xml:1589
+#: using-d-i.xml:1844
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1605
+#: using-d-i.xml:1860
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1617
+#: using-d-i.xml:1872
 #, no-c-format
 #. Tag: title
 msgid "Choose the correct partition!"
 msgstr ""
 
-#: using-d-i.xml:1619
+#: using-d-i.xml:1874
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1634
+#: using-d-i.xml:1889
 #, no-c-format
 #. Tag: title
 msgid "EFI Partition Contents"
 msgstr ""
 
-#: using-d-i.xml:1636
+#: using-d-i.xml:1891
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1658
+#: using-d-i.xml:1913
 #, no-c-format
 #. Tag: filename
 msgid "elilo.conf"
 msgstr ""
 
-#: using-d-i.xml:1659
+#: using-d-i.xml:1914
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1668
+#: using-d-i.xml:1923
 #, no-c-format
 #. Tag: filename
 msgid "elilo.efi"
 msgstr ""
 
-#: using-d-i.xml:1669
+#: using-d-i.xml:1924
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1679
+#: using-d-i.xml:1934
 #, no-c-format
 #. Tag: filename
 msgid "initrd.img"
 msgstr ""
 
-#: using-d-i.xml:1680
+#: using-d-i.xml:1935
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1692
+#: using-d-i.xml:1947
 #, no-c-format
 #. Tag: filename
 msgid "readme.txt"
 msgstr ""
 
-#: using-d-i.xml:1693
+#: using-d-i.xml:1948
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1703
+#: using-d-i.xml:1958
 #, no-c-format
 #. Tag: filename
 msgid "vmlinuz"
 msgstr ""
 
-#: using-d-i.xml:1704
+#: using-d-i.xml:1959
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1724
+#: using-d-i.xml:1979
 #, no-c-format
 #. Tag: title
 msgid "<command>arcboot</command>-installer"
 msgstr ""
 
-#: using-d-i.xml:1725
+#: using-d-i.xml:1980
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1394,61 +1604,61 @@ msgid ""
       "</screen></informalexample> on the firmware prompt, and then typing <command>boot</command>."
 msgstr ""
 
-#: using-d-i.xml:1744
+#: using-d-i.xml:1999
 #, no-c-format
 #. Tag: replaceable
 msgid "scsi"
 msgstr ""
 
-#: using-d-i.xml:1745
+#: using-d-i.xml:2000
 #, no-c-format
 #. Tag: para
 msgid "is the SCSI bus to be booted from, this is <userinput>0</userinput> for the onboard controllers"
 msgstr ""
 
-#: using-d-i.xml:1753
+#: using-d-i.xml:2008
 #, no-c-format
 #. Tag: replaceable
 msgid "disk"
 msgstr ""
 
-#: using-d-i.xml:1754
+#: using-d-i.xml:2009
 #, no-c-format
 #. Tag: para
 msgid "is the SCSI ID of the hard disk on which <command>arcboot</command> is installed"
 msgstr ""
 
-#: using-d-i.xml:1762 using-d-i.xml:1831
+#: using-d-i.xml:2017 using-d-i.xml:2086
 #, no-c-format
 #. Tag: replaceable
 msgid "partnr"
 msgstr ""
 
-#: using-d-i.xml:1763
+#: using-d-i.xml:2018
 #, no-c-format
 #. Tag: para
 msgid "is the number of the partition on which <filename>/etc/arcboot.conf</filename> resides"
 msgstr ""
 
-#: using-d-i.xml:1771
+#: using-d-i.xml:2026
 #, no-c-format
 #. Tag: replaceable
 msgid "config"
 msgstr ""
 
-#: using-d-i.xml:1772
+#: using-d-i.xml:2027
 #, no-c-format
 #. Tag: para
 msgid "is the name of the configuration entry in <filename>/etc/arcboot.conf</filename>, which is <quote>linux</quote> by default."
 msgstr ""
 
-#: using-d-i.xml:1793
+#: using-d-i.xml:2048
 #, no-c-format
 #. Tag: title
 msgid "<command>delo</command>-installer"
 msgstr ""
 
-#: using-d-i.xml:1794
+#: using-d-i.xml:2049
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1457,247 +1667,247 @@ msgid ""
       "</screen></informalexample> on the firmware prompt."
 msgstr ""
 
-#: using-d-i.xml:1813
+#: using-d-i.xml:2068
 #, no-c-format
 #. Tag: replaceable
 msgid "<replaceable>#</replaceable>"
 msgstr ""
 
-#: using-d-i.xml:1814
+#: using-d-i.xml:2069
 #, no-c-format
 #. Tag: para
 msgid "is the TurboChannel device to be booted from, on most DECstations this is <userinput>3</userinput> for the onboard controllers"
 msgstr ""
 
-#: using-d-i.xml:1822
+#: using-d-i.xml:2077
 #, no-c-format
 #. Tag: replaceable
 msgid "<replaceable>id</replaceable>"
 msgstr ""
 
-#: using-d-i.xml:1823
+#: using-d-i.xml:2078
 #, no-c-format
 #. Tag: para
 msgid "is the SCSI ID of the hard disk on which <command>DELO</command> is installed"
 msgstr ""
 
-#: using-d-i.xml:1832
+#: using-d-i.xml:2087
 #, no-c-format
 #. Tag: para
 msgid "is the number of the partition on which <filename>/etc/delo.conf</filename> resides"
 msgstr ""
 
-#: using-d-i.xml:1840
+#: using-d-i.xml:2095
 #, no-c-format
 #. Tag: replaceable
 msgid "name"
 msgstr ""
 
-#: using-d-i.xml:1841
+#: using-d-i.xml:2096
 #, no-c-format
 #. Tag: para
 msgid "is the name of the configuration entry in <filename>/etc/delo.conf</filename>, which is <quote>linux</quote> by default."
 msgstr ""
 
-#: using-d-i.xml:1851
+#: using-d-i.xml:2106
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1857
+#: using-d-i.xml:2112
 #, no-c-format
 #. Tag: screen
 msgid "<userinput>boot #/rz<replaceable>id</replaceable></userinput>"
 msgstr ""
 
-#: using-d-i.xml:1867
+#: using-d-i.xml:2122
 #, no-c-format
 #. Tag: title
 msgid "Install <command>Yaboot</command> on a Hard Disk"
 msgstr ""
 
-#: using-d-i.xml:1868
+#: using-d-i.xml:2123
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1886
+#: using-d-i.xml:2141
 #, no-c-format
 #. Tag: title
 msgid "Install <command>Quik</command> on a Hard Disk"
 msgstr ""
 
-#: using-d-i.xml:1887
+#: using-d-i.xml:2142
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1903
+#: using-d-i.xml:2158
 #, no-c-format
 #. Tag: title
 msgid "<command>zipl</command>-installer"
 msgstr ""
 
-#: using-d-i.xml:1904
+#: using-d-i.xml:2159
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1921
+#: using-d-i.xml:2176
 #, no-c-format
 #. Tag: title
 msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk"
 msgstr ""
 
-#: using-d-i.xml:1923
+#: using-d-i.xml:2178
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1948
+#: using-d-i.xml:2203
 #, no-c-format
 #. Tag: title
 msgid "Continue Without Boot Loader"
 msgstr ""
 
-#: using-d-i.xml:1950
+#: using-d-i.xml:2205
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1959
+#: using-d-i.xml:2214
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1976
+#: using-d-i.xml:2231
 #, no-c-format
 #. Tag: title
-msgid "Finishing the First Stage"
+msgid "Finishing the Installation"
 msgstr ""
 
-#: using-d-i.xml:1977
+#: using-d-i.xml:2232
 #, no-c-format
 #. Tag: para
-msgid "These are the last bits to do before rebooting to your new Debian. It mostly consists of tidying up after the &d-i;."
+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 ""
 
-#: using-d-i.xml:1989
+#: using-d-i.xml:2244
 #, no-c-format
 #. Tag: title
 msgid "Finish the Installation and Reboot"
 msgstr ""
 
-#: using-d-i.xml:1991
+#: using-d-i.xml:2246
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:1998
+#: using-d-i.xml:2253
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:2012
+#: using-d-i.xml:2267
 #, no-c-format
 #. Tag: title
 msgid "Miscellaneous"
 msgstr ""
 
-#: using-d-i.xml:2013
+#: using-d-i.xml:2268
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:2026
+#: using-d-i.xml:2281
 #, no-c-format
 #. Tag: title
 msgid "Saving the installation logs"
 msgstr ""
 
-#: using-d-i.xml:2028
+#: using-d-i.xml:2283
 #, no-c-format
 #. Tag: para
-msgid "If the installation is successful, the logfiles created during the installation process will be automatically saved to <filename>/var/log/debian-installer/</filename> on your new Debian system."
+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 ""
 
-#: using-d-i.xml:2035
+#: using-d-i.xml:2290
 #, no-c-format
 #. Tag: para
-msgid "Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu allows you to save the log files to a floppy disk<phrase condition=\"etch\">, network, hard disk, or other media</phrase>. 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."
+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 ""
 
-#: using-d-i.xml:2056
+#: using-d-i.xml:2310
 #, no-c-format
 #. Tag: title
 msgid "Using the Shell and Viewing the Logs"
 msgstr ""
 
-#: using-d-i.xml:2059
+#: using-d-i.xml:2313
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:2071
+#: using-d-i.xml:2325
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:2080
+#: using-d-i.xml:2334
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:2099
+#: using-d-i.xml:2353
 #, no-c-format
 #. Tag: title
 msgid "Installation Over the Network"
 msgstr ""
 
-#: using-d-i.xml:2101
+#: using-d-i.xml:2355
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:2111
+#: using-d-i.xml:2365
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:2124
+#: using-d-i.xml:2378
 #, no-c-format
 #. Tag: para
 msgid "For installations on &arch-title;, this is the default method after setting up the network."
 msgstr ""
 
-#: using-d-i.xml:2129
+#: using-d-i.xml:2383
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:2141
+#: using-d-i.xml:2395
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:2147
+#: using-d-i.xml:2401
 #, no-c-format
 #. Tag: para
 msgid ""
@@ -1706,37 +1916,37 @@ msgid ""
       "</screen></informalexample> Where <replaceable>install_host</replaceable> is either the name or IP address of the computer being installed. Before the actual login the fingerprint of the remote system will be displayed and you will have to confirm that it is correct."
 msgstr ""
 
-#: using-d-i.xml:2164
+#: using-d-i.xml:2418
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:2173
+#: using-d-i.xml:2427
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:2183
+#: using-d-i.xml:2437
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:2191
+#: using-d-i.xml:2445
 #, no-c-format
 #. Tag: para
 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 ""
 
-#: using-d-i.xml:2206
+#: using-d-i.xml:2460
 #, no-c-format
 #. Tag: title
 msgid "Running <command>base-config</command> From Within &d-i;"
 msgstr ""
 
-#: using-d-i.xml:2208
+#: using-d-i.xml:2462
 #, no-c-format
 #. Tag: para
 msgid "It is possible to configure the base system within the first stage installer (before rebooting from the hard drive), by running <command>base-config</command> in a <firstterm>chroot</firstterm> environment. This is mainly useful for testing the installer and should normally be avoided."
diff --git a/po/pot/welcome.pot b/po/pot/welcome.pot
index 49272871f..9e7e1ee3e 100644
--- a/po/pot/welcome.pot
+++ b/po/pot/welcome.pot
@@ -6,7 +6,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2005-12-03 10:28+0000\n"
+"POT-Creation-Date: 2006-01-03 19:55+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"
@@ -317,94 +317,88 @@ msgstr ""
 #: welcome.xml:443
 #, no-c-format
 #. Tag: para
-msgid "Perform the actual installation according to <xref linkend=\"d-i-intro\"/>. This involves choosing your language, configuring peripheral driver modules, configuring your network connection, so that remaining installation files can be obtained directly from a Debian server (if you are not installing from a CD), partitioning your hard drives and installation of minimal working system. (Some background about setting up the partitions for your Debian system is explained in <xref linkend=\"partitioning\"/>.)"
+msgid "Perform the actual installation according to <xref linkend=\"d-i-intro\"/>. This involves choosing your language, configuring peripheral driver modules, configuring your network connection, so that remaining installation files can be obtained directly from a Debian server (if you are not installing from a CD), partitioning your hard drives and installation of a base system, then selection and installation of tasks. (Some background about setting up the partitions for your Debian system is explained in <xref linkend=\"partitioning\"/>.)"
 msgstr ""
 
 #: welcome.xml:456
 #, no-c-format
 #. Tag: para
-msgid "Boot into your newly installed base system and run through some additional configuration tasks, from <xref linkend=\"boot-new\"/>."
+msgid "Boot into your newly installed base system, from <xref linkend=\"boot-new\"/>."
 msgstr ""
 
-#: welcome.xml:462
-#, no-c-format
-#. Tag: para
-msgid "Install additional software in <xref linkend=\"install-packages\"/>."
-msgstr ""
-
-#: welcome.xml:469
+#: welcome.xml:464
 #, no-c-format
 #. Tag: para
 msgid "Once you've got your system installed, you can read <xref linkend=\"post-install\"/>. That chapter explains where to look to find more information about Unix and Debian, and how to replace your kernel."
 msgstr ""
 
-#: welcome.xml:479
+#: welcome.xml:474
 #, no-c-format
 #. Tag: para
 msgid "Finally, information about this document and how to contribute to it may be found in <xref linkend=\"administrivia\"/>."
 msgstr ""
 
-#: welcome.xml:489
+#: welcome.xml:484
 #, no-c-format
 #. Tag: title
 msgid "Your Documentation Help is Welcome"
 msgstr ""
 
-#: welcome.xml:491
+#: welcome.xml:486
 #, no-c-format
 #. Tag: para
 msgid "Any help, suggestions, and especially, patches, are greatly appreciated. Working versions of this document can be found at <ulink url=\"&url-d-i-alioth-manual;\"></ulink>. There you will find a list of all the different architectures and languages for which this document is available."
 msgstr ""
 
-#: welcome.xml:498
+#: welcome.xml:493
 #, no-c-format
 #. Tag: para
 msgid "Source is also available publicly; look in <xref linkend=\"administrivia\"/> for more information concerning how to contribute. We welcome suggestions, comments, patches, and bug reports (use the package &d-i-manual; for bugs, but check first to see if the problem is already reported)."
 msgstr ""
 
-#: welcome.xml:514
+#: welcome.xml:509
 #, no-c-format
 #. Tag: title
 msgid "About Copyrights and Software Licenses"
 msgstr ""
 
-#: welcome.xml:517
+#: welcome.xml:512
 #, no-c-format
 #. Tag: para
 msgid "We're sure that you've read some of the licenses that come with most commercial software &mdash; they usually say that you can only use one copy of the software on a single computer. This system's license isn't like that at all. We encourage you to put a copy of on every computer in your school or place of business. Lend your installation media to your friends and help them install it on their computers! You can even make thousands of copies and <emphasis>sell</emphasis> them &mdash; albeit with a few restrictions. Your freedom to install and use the system comes directly from Debian being based on <emphasis>free software</emphasis>."
 msgstr ""
 
-#: welcome.xml:530
+#: welcome.xml:525
 #, no-c-format
 #. Tag: para
 msgid "Calling software <emphasis>free</emphasis> doesn't mean that the software isn't copyrighted, and it doesn't mean that CDs containing that software must be distributed at no charge. Free software, in part, means that the licenses of individual programs do not require you to pay for the privilege of distributing or using those programs. Free software also means that not only may anyone extend, adapt, and modify the software, but that they may distribute the results of their work as well."
 msgstr ""
 
-#: welcome.xml:541
+#: welcome.xml:536
 #, no-c-format
 #. Tag: para
 msgid "The Debian project, as a pragmatic concession to its users, does make some packages available that do not meet our criteria for being free. These packages are not part of the official distribution, however, and are only available from the <userinput>contrib</userinput> or <userinput>non-free</userinput> areas of Debian mirrors or on third-party CD-ROMs; see the <ulink url=\"&url-debian-faq;\">Debian FAQ</ulink>, under <quote>The Debian FTP archives</quote>, for more information about the layout and contents of the archives."
 msgstr ""
 
-#: welcome.xml:555
+#: welcome.xml:550
 #, no-c-format
 #. Tag: para
 msgid "Many of the programs in the system are licensed under the <emphasis>GNU</emphasis> <emphasis>General Public License</emphasis>, often simply referred to as <quote>the GPL</quote>. The GPL requires you to make the <emphasis>source code</emphasis> of the programs available whenever you distribute a binary copy of the program; that provision of the license ensures that any user will be able to modify the software. Because of this provision, the source code<footnote> <para> For information on how to locate, unpack, and build binaries from Debian source packages, see the <ulink url=\"&url-debian-faq;\">Debian FAQ</ulink>, under <quote>Basics of the Debian Package Management System</quote>. </para> </footnote> for all such programs is available in the Debian system."
 msgstr ""
 
-#: welcome.xml:574
+#: welcome.xml:569
 #, no-c-format
 #. Tag: para
 msgid "There are several other forms of copyright statements and software licenses used on the programs in Debian. You can find the copyrights and licenses for every package installed on your system by looking in the file <filename>/usr/share/doc/<replaceable>package-name</replaceable>/copyright </filename> once you've installed a package on your system."
 msgstr ""
 
-#: welcome.xml:584
+#: welcome.xml:579
 #, no-c-format
 #. Tag: para
 msgid "For more information about licenses and how Debian determines whether software is free enough to be included in the main distribution, see the <ulink url=\"&url-dfsg;\">Debian Free Software Guidelines</ulink>."
 msgstr ""
 
-#: welcome.xml:590
+#: welcome.xml:585
 #, no-c-format
 #. Tag: para
 msgid "The most important legal notice is that this software comes with <emphasis>no warranties</emphasis>. The programmers who have created this software have done so for the benefit of the community. No guarantee is made as to the suitability of the software for any given purpose. However, since the software is free, you are empowered to modify that software to suit your needs &mdash; and to enjoy the benefits of the changes made by others who have extended the software in this way."