d-i manual: update po|pot files after changings in en

8 files changed, 815 insertions, 789 deletions

diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot
index 91464668d..5878bb0d5 100644
--- a/po/pot/boot-installer.pot
+++ b/po/pot/boot-installer.pot
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2013-04-16 19:15+0000\n"
+"POT-Creation-Date: 2013-05-22 19:06+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"
@@ -45,19 +45,19 @@ msgid "Booting from TFTP"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:43 boot-installer.xml:586 boot-installer.xml:1127 boot-installer.xml:1650 boot-installer.xml:1759
+#: boot-installer.xml:43 boot-installer.xml:586 boot-installer.xml:1127 boot-installer.xml:1657 boot-installer.xml:1766
 #, no-c-format
 msgid "Booting from the network requires that you have a network connection and a TFTP network boot server (DHCP, RARP, or BOOTP)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:48 boot-installer.xml:591 boot-installer.xml:1132 boot-installer.xml:1655 boot-installer.xml:1764
+#: boot-installer.xml:48 boot-installer.xml:591 boot-installer.xml:1132 boot-installer.xml:1662 boot-installer.xml:1771
 #, no-c-format
 msgid "Older systems such as the 715 might require the use of an RBOOT server instead of a BOOTP server."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:53 boot-installer.xml:596 boot-installer.xml:1137 boot-installer.xml:1660 boot-installer.xml:1769
+#: boot-installer.xml:53 boot-installer.xml:596 boot-installer.xml:1137 boot-installer.xml:1667 boot-installer.xml:1776
 #, no-c-format
 msgid "The installation method to support network booting is described in <xref linkend=\"install-tftp\"/>."
 msgstr ""
@@ -69,25 +69,25 @@ msgid "Booting from CD-ROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:746 boot-installer.xml:1426 boot-installer.xml:1798
+#: boot-installer.xml:70 boot-installer.xml:248 boot-installer.xml:746 boot-installer.xml:1426 boot-installer.xml:1805
 #, no-c-format
 msgid "The easiest route for most people will be to use a set of &debian; CDs. If you have a CD set, and if your machine supports booting directly off the CD, great! Simply <phrase arch=\"x86\"> configure your system for booting off a CD as described in <xref linkend=\"boot-dev-select\"/>, </phrase> insert your CD, reboot, and proceed to the next chapter."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:757 boot-installer.xml:1437 boot-installer.xml:1809
+#: boot-installer.xml:81 boot-installer.xml:259 boot-installer.xml:757 boot-installer.xml:1437 boot-installer.xml:1816
 #, no-c-format
 msgid "Note that certain CD drives may require special drivers, and thus be inaccessible in the early installation stages. If it turns out the standard way of booting off a CD doesn't work for your hardware, revisit this chapter and read about alternate kernels and installation methods which may work for you."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:765 boot-installer.xml:1445 boot-installer.xml:1817
+#: boot-installer.xml:89 boot-installer.xml:267 boot-installer.xml:765 boot-installer.xml:1445 boot-installer.xml:1824
 #, no-c-format
 msgid "Even if you cannot boot from CD-ROM, you can probably install the &debian; system components and any packages you want from CD-ROM. Simply boot using a different 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 ""
 
 #. Tag: para
-#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:773 boot-installer.xml:1453 boot-installer.xml:1825
+#: boot-installer.xml:97 boot-installer.xml:275 boot-installer.xml:773 boot-installer.xml:1453 boot-installer.xml:1832
 #, no-c-format
 msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
 msgstr ""
@@ -216,7 +216,7 @@ msgid "The installer will now start as usual."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:242 boot-installer.xml:740 boot-installer.xml:1420 boot-installer.xml:1792
+#: boot-installer.xml:242 boot-installer.xml:740 boot-installer.xml:1420 boot-installer.xml:1799
 #, no-c-format
 msgid "Booting from a CD-ROM"
 msgstr ""
@@ -388,13 +388,13 @@ msgid "Let's assume you have prepared everything from <xref linkend=\"boot-dev-s
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:522 boot-installer.xml:1699
+#: boot-installer.xml:522 boot-installer.xml:1706
 #, no-c-format
 msgid "Booting from Floppies"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:523 boot-installer.xml:1707
+#: boot-installer.xml:523 boot-installer.xml:1714
 #, no-c-format
 msgid "You will have already downloaded the floppy images you needed and created floppies from the images in <xref linkend=\"create-floppy\"/>."
 msgstr ""
@@ -436,7 +436,7 @@ msgid "After booting from the boot floppy, the root floppy is requested. Insert
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:580 boot-installer.xml:1109 boot-installer.xml:1250 boot-installer.xml:1304 boot-installer.xml:1644 boot-installer.xml:1753
+#: boot-installer.xml:580 boot-installer.xml:1109 boot-installer.xml:1250 boot-installer.xml:1304 boot-installer.xml:1651 boot-installer.xml:1760
 #, no-c-format
 msgid "Booting with TFTP"
 msgstr ""
@@ -864,7 +864,7 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1274 boot-installer.xml:1341 boot-installer.xml:2031
+#: boot-installer.xml:1274 boot-installer.xml:1341 boot-installer.xml:2038
 #, no-c-format
 msgid "Boot Parameters"
 msgstr ""
@@ -1001,44 +1001,56 @@ msgstr ""
 msgid "boot cd install/pegasos"
 msgstr ""
 
+#. Tag: para
+#: boot-installer.xml:1499
+#, no-c-format
+msgid "On YDL Powerstation machine, pres <keycap>s</keycap> immediately after <quote>Press 's' to enter Open Firmware</quote> message, when SLOF prompt appears type"
+msgstr ""
+
+#. Tag: screen
+#: boot-installer.xml:1504
+#, no-c-format
+msgid "0 > boot cdrom"
+msgstr ""
+
 #. Tag: title
-#: boot-installer.xml:1503
+#: boot-installer.xml:1510
 #, no-c-format
 msgid "Booting from Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1509
+#: boot-installer.xml:1516
 #, no-c-format
 msgid "Booting from an existing operating system is often a convenient option; for some systems it is the only supported method of installation."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1515
+#: boot-installer.xml:1522
 #, no-c-format
 msgid "To boot the installer from hard disk, you will have already completed downloading and placing the needed files as described in <xref linkend=\"boot-drive-files\"/>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1535
+#: boot-installer.xml:1542
 #, no-c-format
 msgid "Booting OldWorld PowerMacs from MacOS"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1536
+#: boot-installer.xml:1543
 #, no-c-format
 msgid "If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to boot into the installation system. Double click the <guiicon>BootX</guiicon> application icon. Click on the <guibutton>Options</guibutton> button and select <guilabel>Use Specified RAM Disk</guilabel>. This will give you the chance to select the <filename>ramdisk.image.gz</filename> file. You may need to select the <guilabel>No Video Driver</guilabel> checkbox, depending on your hardware. Then click the <guibutton>Linux</guibutton> button to shut down MacOS and launch the installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1554
+#: boot-installer.xml:1561
 #, no-c-format
 msgid "Booting NewWorld Macs from OpenFirmware"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1555
+#: boot-installer.xml:1562
 #, no-c-format
 msgid ""
       "You will have already placed the <filename>vmlinux</filename>, <filename>initrd.gz</filename>, <filename>yaboot</filename>, and <filename>yaboot.conf</filename> files at the root level of your HFS partition in <xref linkend=\"files-newworld\"/>. You will now have to boot into OpenFirmware (see <xref linkend=\"invoking-openfirmware\"/>). At the prompt, type <informalexample><screen>\n"
@@ -1049,31 +1061,31 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1587
+#: boot-installer.xml:1594
 #, no-c-format
 msgid "Booting from USB memory stick"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1588
+#: boot-installer.xml:1595
 #, no-c-format
 msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1594
+#: boot-installer.xml:1601
 #, no-c-format
 msgid "Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/>. To boot a Macintosh system from a USB stick, you will need to use the Open Firmware prompt, since Open Firmware does not search USB storage devices by default. See <xref linkend=\"invoking-openfirmware\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1603
+#: boot-installer.xml:1610
 #, no-c-format
 msgid "You will need to work out where the USB storage device appears in the device tree, since at the moment <command>ofpath</command> cannot work that out automatically. Type <userinput>dev / ls</userinput> and <userinput>devalias</userinput> at the Open Firmware prompt to get a list of all known devices and device aliases. On the author's system with various types of USB stick, paths such as <filename>usb0/disk</filename>, <filename>usb0/hub/disk</filename>, <filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and <filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1615
+#: boot-installer.xml:1622
 #, no-c-format
 msgid ""
       "Having worked out the device path, use a command like this to boot the installer: <informalexample><screen>\n"
@@ -1082,25 +1094,25 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1629
+#: boot-installer.xml:1636
 #, no-c-format
 msgid "The system should now boot up, and you should be presented with the <prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, or just hit &enterkey;."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1635
+#: boot-installer.xml:1642
 #, no-c-format
 msgid "This boot method is new, and may be difficult to get to work on some NewWorld systems. If you have problems, please file an installation report, as explained in <xref linkend=\"submit-bug\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1668
+#: boot-installer.xml:1675
 #, no-c-format
 msgid "Currently, PReP and New World PowerMac systems support netbooting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1672
+#: boot-installer.xml:1679
 #, no-c-format
 msgid ""
       "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command <informalexample><screen>\n"
@@ -1113,739 +1125,739 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1700
+#: boot-installer.xml:1707
 #, no-c-format
 msgid "Booting from floppies is supported for &arch-title;, although it is generally only applicable for OldWorld systems. NewWorld systems are not equipped with floppy drives, and attached USB floppy drives are not supported for booting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1712
+#: boot-installer.xml:1719
 #, no-c-format
 msgid "To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it in floppy drive after shutting the system down, and before pressing the power-on button."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1718
+#: boot-installer.xml:1725
 #, no-c-format
 msgid "For those not familiar with Macintosh floppy operations: a floppy placed in the machine prior to boot will be the first priority for the system to boot from. A floppy without a valid boot system will be ejected, and the machine will then check for bootable hard disk partitions."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1725
+#: boot-installer.xml:1732
 #, no-c-format
 msgid "After booting, the <filename>root.bin</filename> floppy is requested. Insert the root floppy and press &enterkey;. The installer program is automatically launched after the root system has been loaded into memory."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1736
+#: boot-installer.xml:1743
 #, no-c-format
 msgid "PowerPC Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1737
+#: boot-installer.xml:1744
 #, no-c-format
 msgid "Many older Apple monitors used a 640x480 67Hz mode. If your video appears skewed on an older Apple monitor, try appending the boot argument <userinput>video=atyfb:vmode:6</userinput> , which will select that mode for most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to <userinput>video=aty128fb:vmode:6</userinput> ."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1777
+#: boot-installer.xml:1784
 #, no-c-format
 msgid "On machines with OpenBoot, simply enter the boot monitor on the machine which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use the command <userinput>boot net</userinput> to boot from a TFTP and RARP server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server. You can pass extra boot parameters to &d-i; at the end of the <userinput>boot</userinput> command."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1832
+#: boot-installer.xml:1839
 #, no-c-format
 msgid "Most OpenBoot versions support the <userinput>boot cdrom</userinput> command which is simply an alias to boot from the SCSI device on ID 6 (or the secondary master for IDE based systems)."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1841
+#: boot-installer.xml:1848
 #, no-c-format
 msgid "IDPROM Messages"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1842
+#: boot-installer.xml:1849
 #, no-c-format
 msgid "If you cannot boot because you get messages about a problem with <quote>IDPROM</quote>, then it's possible that your NVRAM battery, which holds configuration information for you firmware, has run out. See the <ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink> for more information."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1861
+#: boot-installer.xml:1868
 #, no-c-format
 msgid "Accessibility"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1862
+#: boot-installer.xml:1869
 #, no-c-format
 msgid "Some users may need specific support because of e.g. some visual impairment. <phrase arch=\"ia64;powerpc;x86\">USB braille displays are detected automatically (not serial displays connected via a serial-to-USB converter), but most other</phrase> <phrase arch=\"arm;hppa;mips;mipsel;sparc\">Most</phrase> accessibility features have to be enabled manually. <phrase arch=\"x86\">On machines that support it, the boot menu emits a beep when it is ready to receive keystrokes.</phrase> Some boot parameters can <phrase arch=\"x86\">then</phrase> be appended to enable accessibility features<phrase arch=\"x86\"> (see also <xref linkend=\"boot-screen\"/>)</phrase>. Note that on most architectures the boot loader interprets your keyboard as a QWERTY keyboard."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1882
+#: boot-installer.xml:1889
 #, no-c-format
 msgid "USB Braille Displays"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1883
+#: boot-installer.xml:1890
 #, no-c-format
 msgid "USB braille displays should be automatically detected. A textual version of the installer will then be automatically selected, and support for the braille display will be automatically installed on the target system. You can thus just press &enterkey; at the boot menu. Once <classname>brltty</classname> is started, you can choose a braille table by entering the preference menu. Documentation on key bindings for braille devices is available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> website</ulink>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1898
+#: boot-installer.xml:1905
 #, no-c-format
 msgid "Serial Braille Displays"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1899
+#: boot-installer.xml:1906
 #, no-c-format
 msgid "Serial braille displays cannot safely be automatically detected (since that may damage some of them). You thus need to append the <userinput>brltty=<replaceable>driver</replaceable>,<replaceable>port</replaceable>,<replaceable>table</replaceable></userinput> boot parameter to tell <classname>brltty</classname> which driver it should use. <replaceable>driver</replaceable> should be replaced by the two-letter driver code for your terminal (see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>). <replaceable>port</replaceable> should be replaced by the name of the serial port the display is connected to, <userinput>ttyS0</userinput> is the default, <userinput>ttyUSB0</userinput> can be typically used when using a serial-to-USB converter. <replaceable>table</replaceable> is the name of the braille table to be used (see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>); the English table is the default. Note that the table can be changed later by entering the preference menu. Documentation on key bindings for braille devices is available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> website</ulink>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1922 boot-installer.xml:2929
+#: boot-installer.xml:1929 boot-installer.xml:2936
 #, no-c-format
 msgid "Software Speech Synthesis"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1923
+#: boot-installer.xml:1930
 #, no-c-format
 msgid "Support for software speech synthesis is available on all installer images which have the graphical installer, i.e. all netinst, CD and DVD images, and the netboot gtk variant. It can be activated by selecting it in the boot menu by typing <userinput>s</userinput> &enterkey;. The textual version of the installer will then be automatically selected, and support for software speech synthesis will be automatically installed on the target system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1932
+#: boot-installer.xml:1939
 #, no-c-format
 msgid "The first question (language) is spoken in english, and the remainder of installation is spoken in the selected language (if available in <classname>espeak</classname>)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1938
+#: boot-installer.xml:1945
 #, no-c-format
 msgid "The default speech rate is quite slow. To make it faster, press <keycombo><keycap>CapsLock</keycap><keycap>6</keycap></keycombo>. To make it slower, press <keycombo><keycap>CapsLock</keycap><keycap>5</keycap></keycombo>. The default volume should be medium. To make it louder, press <keycombo><keycap>CapsLock</keycap><keycap>2</keycap></keycombo>. To make it quieter, press <keycombo><keycap>CapsLock</keycap><keycap>1</keycap></keycombo>. To get more details on the browsing shortcuts, see the <ulink url=\"&url-speakup-guide;\">Speakup guide</ulink>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1957
+#: boot-installer.xml:1964
 #, no-c-format
 msgid "Hardware Speech Synthesis"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1958
+#: boot-installer.xml:1965
 #, no-c-format
 msgid "Support for hardware speech synthesis devices is available on all installer images which have the graphical installer, i.e. all netinst, CD and DVD images, and the netboot gtk variant. You thus need to select a <quote>Graphical install</quote> entry in the boot menu."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1965
+#: boot-installer.xml:1972
 #, no-c-format
 msgid "Hardware speech synthesis devices cannot be automatically detected. You thus need to append the <userinput>speakup.synth=<replaceable>driver</replaceable></userinput> boot parameter to tell <classname>speakup</classname> which driver it should use. <replaceable>driver</replaceable> should be replaced by the driver code for your device (see <ulink url=\"&url-speakup-guide;\">driver code list</ulink>). The textual version of the installer will then be automatically selected, and support for the speech synthesis device will be automatically installed on the target system."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1980
+#: boot-installer.xml:1987
 #, no-c-format
 msgid "Board Devices"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1981
+#: boot-installer.xml:1988
 #, no-c-format
 msgid "Some accessibility devices are actual boards that are plugged inside the machine and that read text directly from the video memory. To get them to work framebuffer support must be disabled by using the <userinput arch=\"x86\">vga=normal</userinput> <userinput>fb=false</userinput> boot parameter. This will however reduce the number of available languages."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1989
+#: boot-installer.xml:1996
 #, no-c-format
 msgid "If desired a textual version of the bootloader can be activated before adding the boot parameter by typing <userinput>h</userinput> &enterkey;."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:1997
+#: boot-installer.xml:2004
 #, no-c-format
 msgid "High-Contrast Theme"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:1998
+#: boot-installer.xml:2005
 #, no-c-format
-msgid "For users with low vision, the installer can use a high-contrast theme that makes it more readable. To enable it, append the <userinput>theme=dark</userinput> boot parameter."
+msgid "For users with low vision, the installer can use a high-contrast color theme that makes it more readable. To enable it, append the <userinput>theme=dark</userinput> boot parameter."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2007
+#: boot-installer.xml:2014
 #, no-c-format
 msgid "Preseeding"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2008
+#: boot-installer.xml:2015
 #, no-c-format
 msgid "Alternatively, &debian; can be installed completely automatically by using preseeding. This is documented in <xref linkend=\"appendix-preseed\"/>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2016
+#: boot-installer.xml:2023
 #, no-c-format
 msgid "Accessibility of the installed system"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2017
+#: boot-installer.xml:2024
 #, no-c-format
 msgid "Documentation on accessibility of the installed system is available on the <ulink url=\"&url-debian-wiki-accessibility;\">Debian Accessibility wiki page</ulink>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2032
+#: boot-installer.xml:2039
 #, no-c-format
 msgid "Boot parameters are Linux kernel parameters which are generally used to make sure that peripherals are dealt with properly. For the most part, the kernel can auto-detect information about your peripherals. However, in some cases you'll have to help the kernel a bit."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2039
+#: boot-installer.xml:2046
 #, no-c-format
 msgid "If this is the first time you're booting the system, try the default boot parameters (i.e., don't try setting parameters) and see if it works correctly. It probably will. If not, you can reboot later and look for any special parameters that inform the system about your hardware."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2046
+#: boot-installer.xml:2053
 #, no-c-format
 msgid "Information on many boot parameters can be found in the <ulink url=\"http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, including tips for obscure hardware. This section contains only a sketch of the most salient parameters. Some common gotchas are included below in <xref linkend=\"boot-troubleshooting\"/>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2058
+#: boot-installer.xml:2065
 #, no-c-format
 msgid "Boot console"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2060
+#: boot-installer.xml:2067
 #, no-c-format
 msgid "If you are booting with a serial console, generally the kernel will autodetect this. If you have a videocard (framebuffer) and a keyboard also attached to the computer which you wish to boot via serial console, you may have to pass the <userinput>console=<replaceable>device</replaceable></userinput> argument to the kernel, where <replaceable>device</replaceable> is your serial device, which is usually something like <filename>ttyS0</filename>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2072
+#: boot-installer.xml:2079
 #, no-c-format
 msgid "You may need to specify parameters for the serial port, such as speed and parity, for instance <userinput>console=ttyS0,9600n8</userinput>; other typical speeds may be 57600 or 115200."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2078
+#: boot-installer.xml:2085
 #, no-c-format
 msgid "In order to ensure the terminal type used by the installer matches your terminal emulator, the parameter <userinput>TERM=<replaceable>type</replaceable></userinput> can be added. Note that the installer only supports the following terminal types: <literal>linux</literal>, <literal>bterm</literal>, <literal>ansi</literal>, <literal>vt102</literal> and <literal>dumb</literal>. The default for serial console in &d-i; is <userinput>vt102</userinput>. If you are using a virtualization tool which does not provide conversion into such terminals types itself, e.g. QEMU/KVM, you can start it inside a <command>screen</command> session. That will indeed perform translation into the <literal>screen</literal> terminal type, which is very close to <literal>vt102</literal>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2094
+#: boot-installer.xml:2101
 #, no-c-format
 msgid "For &arch-title; the serial devices are <filename>ttya</filename> or <filename>ttyb</filename>. Alternatively, set the <envar>input-device</envar> and <envar>output-device</envar> OpenPROM variables to <filename>ttya</filename>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2106
+#: boot-installer.xml:2113
 #, no-c-format
 msgid "&debian; Installer Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2107
+#: boot-installer.xml:2114
 #, no-c-format
 msgid "The installation system recognizes a few additional boot parameters<footnote> <para> With current kernels (2.6.9 or newer) you can use 32 command line options and 32 environment options. If these numbers are exceeded, the kernel will panic. </para> </footnote> which may be useful."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2120
+#: boot-installer.xml:2127
 #, no-c-format
 msgid "A number of parameters have a <quote>short form</quote> that helps avoid the limitations of the kernel command line options and makes entering the parameters easier. If a parameter has a short form, it will be listed in brackets behind the (normal) long form. Examples in this manual will normally use the short form too."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2132
+#: boot-installer.xml:2139
 #, no-c-format
 msgid "debconf/priority (priority)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2133
+#: boot-installer.xml:2140
 #, no-c-format
 msgid "This parameter sets the lowest priority of messages to be displayed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2137
+#: boot-installer.xml:2144
 #, no-c-format
 msgid "The default installation uses <userinput>priority=high</userinput>. This means that both high and critical priority messages are shown, but medium and low priority messages are skipped. If problems are encountered, the installer adjusts the priority as needed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2144
+#: boot-installer.xml:2151
 #, no-c-format
 msgid "If you add <userinput>priority=medium</userinput> as boot parameter, you will be shown the installation menu and gain more control over the installation. When <userinput>priority=low</userinput> is used, all messages are shown (this is equivalent to the <emphasis>expert</emphasis> boot method). With <userinput>priority=critical</userinput>, the installation system will display only critical messages and try to do the right thing without fuss."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2158
+#: boot-installer.xml:2165
 #, no-c-format
 msgid "DEBIAN_FRONTEND"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2159
+#: boot-installer.xml:2166
 #, no-c-format
 msgid "This boot parameter controls the type of user interface used for the installer. The current possible parameter settings are: <itemizedlist> <listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> </listitem> </itemizedlist> The default frontend is <userinput>DEBIAN_FRONTEND=newt</userinput>. <userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial console installs. Some specialized types of install media may only offer a limited selection of frontends, but the <userinput>newt</userinput> and <userinput>text</userinput> frontends are available on most default install media. On architectures that support it, the graphical installer uses the <userinput>gtk</userinput> frontend."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2190
+#: boot-installer.xml:2197
 #, no-c-format
 msgid "BOOT_DEBUG"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2191
+#: boot-installer.xml:2198
 #, no-c-format
 msgid "Setting this boot parameter to 2 will cause the installer's boot process to be verbosely logged. Setting it to 3 makes debug shells available at strategic points in the boot process. (Exit the shells to continue the boot process.)"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2200
+#: boot-installer.xml:2207
 #, no-c-format
 msgid "BOOT_DEBUG=0"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2201
+#: boot-installer.xml:2208
 #, no-c-format
 msgid "This is the default."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2205
+#: boot-installer.xml:2212
 #, no-c-format
 msgid "BOOT_DEBUG=1"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2206
+#: boot-installer.xml:2213
 #, no-c-format
 msgid "More verbose than usual."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2210
+#: boot-installer.xml:2217
 #, no-c-format
 msgid "BOOT_DEBUG=2"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2211
+#: boot-installer.xml:2218
 #, no-c-format
 msgid "Lots of debugging information."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2215
+#: boot-installer.xml:2222
 #, no-c-format
 msgid "BOOT_DEBUG=3"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2216
+#: boot-installer.xml:2223
 #, no-c-format
 msgid "Shells are run at various points in the boot process to allow detailed debugging. Exit the shell to continue the boot."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2230
+#: boot-installer.xml:2237
 #, no-c-format
 msgid "INSTALL_MEDIA_DEV"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2231
+#: boot-installer.xml:2238
 #, no-c-format
 msgid "The value of the parameter is the path to the device to load the &debian; installer from. For example, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2237
+#: boot-installer.xml:2244
 #, no-c-format
 msgid "The boot floppy, which normally scans all floppies it can to find the root floppy, can be overridden by this parameter to only look at the one device."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2248
+#: boot-installer.xml:2255
 #, no-c-format
 msgid "log_host"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2249
+#: boot-installer.xml:2256
 #, no-c-format
 msgid "log_port"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2250
+#: boot-installer.xml:2257
 #, no-c-format
 msgid "Causes the installer to send log messages to a remote syslog on the specified host and port as well as to a local file. If not specified, the port defaults to the standard syslog port 514."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2261
+#: boot-installer.xml:2268
 #, no-c-format
 msgid "lowmem"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2262
+#: boot-installer.xml:2269
 #, no-c-format
 msgid "Can be used to force the installer to a lowmem level higher than the one the installer sets by default based on available memory. Possible values are 1 and 2. See also <xref linkend=\"lowmem\"/>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2272
+#: boot-installer.xml:2279
 #, no-c-format
 msgid "noshell"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2273
+#: boot-installer.xml:2280
 #, no-c-format
 msgid "Prevents the installer from offering interactive shells on tty2 and tty3. Useful for unattended installations where physical security is limited."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2282
+#: boot-installer.xml:2289
 #, no-c-format
 msgid "debian-installer/framebuffer (fb)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2283
+#: boot-installer.xml:2290
 #, no-c-format
 msgid "Some architectures use the kernel framebuffer to offer installation in a number of languages. If framebuffer causes a problem on your system you can disable the feature using the parameter <userinput arch=\"x86\">vga=normal</userinput> <userinput>fb=false</userinput>. Problem symptoms are error messages about bterm or bogl, a blank screen, or a freeze within a few minutes after starting the install."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2292
+#: boot-installer.xml:2299
 #, no-c-format
 msgid "Such problems have been reported on hppa."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2296
+#: boot-installer.xml:2303
 #, no-c-format
 msgid "Because of display problems on some systems, framebuffer support is <emphasis>disabled by default</emphasis> for &arch-title;. This can result in ugly display on systems that do properly support the framebuffer, like those with ATI graphical cards. If you see display problems in the installer, you can try booting with parameter <userinput>debian-installer/framebuffer=true</userinput> or <userinput>fb=true</userinput> for short."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2310
+#: boot-installer.xml:2317
 #, no-c-format
 msgid "debian-installer/theme (theme)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2311
+#: boot-installer.xml:2318
 #, no-c-format
 msgid "A theme determines how the user interface of the installer looks (colors, icons, etc.). What themes are available differs per frontend. Currently both the newt and gtk frontends only have a <quote>dark</quote> theme that was designed for visually impaired users. Set the theme by booting with <userinput>theme=<replaceable>dark</replaceable></userinput>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2323 boot-installer.xml:2556
+#: boot-installer.xml:2330 boot-installer.xml:2563
 #, no-c-format
 msgid "netcfg/disable_autoconfig"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2324
+#: boot-installer.xml:2331
 #, no-c-format
 msgid "By default, the &d-i; automatically probes for network configuration via IPv6 autoconfiguration and DHCP. If the probe succeeds, you won't have a chance to review and change the obtained settings. You can get to the manual network setup only in case the automatic configuration fails."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2331
+#: boot-installer.xml:2338
 #, no-c-format
 msgid "If you have an IPv6 router or a DHCP server on your local network, but want to avoid them because e.g. they give wrong answers, you can use the parameter <userinput>netcfg/disable_autoconfig=true</userinput> to prevent any automatic configuration of the network (neither v4 nor v6) and to enter the information manually."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2342
+#: boot-installer.xml:2349
 #, no-c-format
 msgid "hw-detect/start_pcmcia"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2343
+#: boot-installer.xml:2350
 #, no-c-format
 msgid "Set to <userinput>false</userinput> to prevent starting PCMCIA services, if that causes problems. Some laptops are well known for this misbehavior."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2353
+#: boot-installer.xml:2360
 #, no-c-format
 msgid "disk-detect/dmraid/enable (dmraid)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2354
+#: boot-installer.xml:2361
 #, no-c-format
 msgid "Set to <userinput>true</userinput> to enable support for Serial ATA RAID (also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. Note that this support is currently experimental. Additional information can be found on the <ulink url=\"&url-d-i-wiki;\">&debian; Installer Wiki</ulink>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2365
+#: boot-installer.xml:2372
 #, no-c-format
 msgid "preseed/url (url)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2366
+#: boot-installer.xml:2373
 #, no-c-format
 msgid "Specify the url to a preconfiguration file to download and use for automating the install. See <xref linkend=\"automatic-install\"/>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2375
+#: boot-installer.xml:2382
 #, no-c-format
 msgid "preseed/file (file)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2376
+#: boot-installer.xml:2383
 #, no-c-format
 msgid "Specify the path to a preconfiguration file to load for automating the install. See <xref linkend=\"automatic-install\"/>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2385
+#: boot-installer.xml:2392
 #, no-c-format
 msgid "preseed/interactive"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2386
+#: boot-installer.xml:2393
 #, no-c-format
 msgid "Set to <userinput>true</userinput> to display questions even if they have been preseeded. Can be useful for testing or debugging a preconfiguration file. Note that this will have no effect on parameters that are passed as boot parameters, but for those a special syntax can be used. See <xref linkend=\"preseed-seenflag\"/> for details."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2398
+#: boot-installer.xml:2405
 #, no-c-format
 msgid "auto-install/enable (auto)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2399
+#: boot-installer.xml:2406
 #, no-c-format
 msgid "Delay questions that are normally asked before preseeding is possible until after the network is configured. See <xref linkend=\"preseed-auto\"/> for details about using this to automate installs."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2410
+#: boot-installer.xml:2417
 #, no-c-format
 msgid "finish-install/keep-consoles"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2411
+#: boot-installer.xml:2418
 #, no-c-format
 msgid "During installations from serial or management console, the regular virtual consoles (VT1 to VT6) are normally disabled in <filename>/etc/inittab</filename>. Set to <userinput>true</userinput> to prevent this."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2422
+#: boot-installer.xml:2429
 #, no-c-format
 msgid "cdrom-detect/eject"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2423
+#: boot-installer.xml:2430
 #, no-c-format
 msgid "By default, before rebooting, &d-i; automatically ejects the optical media used during the installation. This can be unnecessary if the system does not automatically boot off the CD. In some cases it may even be undesirable, for example if the optical drive cannot reinsert the media itself and the user is not there to do it manually. Many slot loading, slim-line, and caddy style drives cannot reload media automatically."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2432
+#: boot-installer.xml:2439
 #, no-c-format
 msgid "Set to <userinput>false</userinput> to disable automatic ejection, and be aware that you may need to ensure that the system does not automatically boot from the optical drive after the initial installation."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2443
+#: boot-installer.xml:2450
 #, no-c-format
 msgid "base-installer/install-recommends (recommends)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2444
+#: boot-installer.xml:2451
 #, no-c-format
 msgid "By setting this option to <userinput>false</userinput>, the package management system will be configured to not automatically install <quote>Recommends</quote>, both during the installation and for the installed system. See also <xref linkend=\"di-install-base\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2451
+#: boot-installer.xml:2458
 #, no-c-format
 msgid "Note that this option allows to have a leaner system, but can also result in features being missing that you might normally expect to be available. You may have to manually install some of the recommended packages to obtain the full functionality you want. This option should therefore only be used by very experienced users."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2463
+#: boot-installer.xml:2470
 #, no-c-format
 msgid "debian-installer/allow_unauthenticated"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2464
+#: boot-installer.xml:2471
 #, no-c-format
 msgid "By default the installer requires that repositories be authenticated using a known gpg key. Set to <userinput>true</userinput> to disable that authentication. <emphasis role=\"bold\">Warning: insecure, not recommended.</emphasis>"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2475
+#: boot-installer.xml:2482
 #, no-c-format
 msgid "ramdisk_size"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2476
+#: boot-installer.xml:2483
 #, no-c-format
 msgid "This parameter should already be set to a correct value where needed; set it only it you see errors during the boot that indicate the ramdisk could not be loaded completely. The value is in kB."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2486
+#: boot-installer.xml:2493
 #, no-c-format
 msgid "rescue/enable"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2487
+#: boot-installer.xml:2494
 #, no-c-format
 msgid "Set to <userinput>true</userinput> to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2500
+#: boot-installer.xml:2507
 #, no-c-format
 msgid "Using boot parameters to answer questions"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2501
+#: boot-installer.xml:2508
 #, no-c-format
 msgid "With some exceptions, a value can be set at the boot prompt for any question asked during the installation, though this is only really useful in specific cases. General instructions how to do this can be found in <xref linkend=\"preseed-bootparms\"/>. Some specific examples are listed below."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2513
+#: boot-installer.xml:2520
 #, no-c-format
 msgid "debian-installer/language (language)"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2514
+#: boot-installer.xml:2521
 #, no-c-format
 msgid "debian-installer/country (country)"
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2515
+#: boot-installer.xml:2522
 #, no-c-format
 msgid "debian-installer/locale (locale)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2516
+#: boot-installer.xml:2523
 #, no-c-format
 msgid "There are two ways to specify the language, country and locale to use for the installation and the installed system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2521
+#: boot-installer.xml:2528
 #, no-c-format
 msgid "The first and easiest is to pass only the parameter <literal>locale</literal>. Language and country will then be derived from its value. You can for example use <userinput>locale=de_CH</userinput> to select German as language and Switzerland as country (<literal>de_CH.UTF-8</literal> will be set as default locale for the installed system). Limitation is that not all possible combinations of language, country and locale can be achieved this way."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2530
+#: boot-installer.xml:2537
 #, no-c-format
 msgid "The second, more flexible option is to specify <literal>language</literal> and <literal>country</literal> separately. In this case <literal>locale</literal> can optionally be added to specify a specific default locale for the installed system. Example: <userinput>language=en country=DE locale=en_GB.UTF-8</userinput>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2542
+#: boot-installer.xml:2549
 #, no-c-format
 msgid "anna/choose_modules (modules)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2543
+#: boot-installer.xml:2550
 #, no-c-format
 msgid "Can be used to automatically load installer components that are not loaded by default. Examples of optional components that may be useful are <classname>openssh-client-udeb</classname> (so you can use <command>scp</command> during the installation)<phrase arch=\"not-s390\"> and <classname>ppp-udeb</classname> (see <xref linkend=\"pppoe\"/>)</phrase>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2557
+#: boot-installer.xml:2564
 #, no-c-format
 msgid "Set to <userinput>true</userinput> if you want to disable IPv6 autoconfiguration and DHCP and instead force static network configuration."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2566
+#: boot-installer.xml:2573
 #, no-c-format
 msgid "mirror/protocol (protocol)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2567
+#: boot-installer.xml:2574
 #, no-c-format
 msgid "By default the installer will use the http protocol to download files from &debian; mirrors and changing that to ftp is not possible during installations at normal priority. By setting this parameter to <userinput>ftp</userinput>, you can force the installer to use that protocol instead. Note that you cannot select an ftp mirror from a list, you have to enter the hostname manually."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2580
+#: boot-installer.xml:2587
 #, no-c-format
 msgid "tasksel:tasksel/first (tasks)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2581
+#: boot-installer.xml:2588
 #, no-c-format
 msgid "Can be used to select tasks that are not available from the interactive task list, such as the <literal>kde-desktop</literal> task. See <xref linkend=\"pkgsel\"/> for additional information."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2595
+#: boot-installer.xml:2602
 #, no-c-format
 msgid "Passing parameters to kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2596
+#: boot-installer.xml:2603
 #, no-c-format
 msgid "If drivers are compiled into the kernel, you can pass parameters to them as described in the kernel documentation. However, if drivers are compiled as modules and because kernel modules are loaded a bit differently during an installation than when booting an installed system, it is not possible to pass parameters to modules as you would normally do. Instead, you need to use a special syntax recognized by the installer which will then make sure that the parameters are saved in the proper configuration files and will thus be used when the modules are actually loaded. The parameters will also be propagated automatically to the configuration for the installed system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2609
+#: boot-installer.xml:2616
 #, no-c-format
 msgid "Note that it is now quite rare that parameters need to be passed to modules. In most cases the kernel will be able to probe the hardware present in a system and set good defaults that way. However, in some situations it may still be needed to set parameters manually."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2616
+#: boot-installer.xml:2623
 #, no-c-format
 msgid ""
       "The syntax to use to set parameters for modules is: <informalexample><screen>\n"
@@ -1854,127 +1866,127 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:2626
+#: boot-installer.xml:2633
 #, no-c-format
 msgid "3c509.xcvr=3 3c509.irq=10"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2632
+#: boot-installer.xml:2639
 #, no-c-format
 msgid "Blacklisting kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2633
+#: boot-installer.xml:2640
 #, no-c-format
 msgid "Sometimes it may be necessary to blacklist a module to prevent it from being loaded automatically by the kernel and udev. One reason could be that a particular module causes problems with your hardware. The kernel also sometimes lists two different drivers for the same device. This can cause the device to not work correctly if the drivers conflict or if the wrong driver is loaded first."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2642
+#: boot-installer.xml:2649
 #, no-c-format
 msgid "You can blacklist a module using the following syntax: <userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>. This will cause the module to be blacklisted in <filename>/etc/modprobe.d/blacklist.local</filename> both during the installation and for the installed system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2650
+#: boot-installer.xml:2657
 #, no-c-format
 msgid "Note that a module may still be loaded by the installation system itself. You can prevent that from happening by running the installation in expert mode and unselecting the module from the list of modules displayed during the hardware detection phases."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2666
+#: boot-installer.xml:2673
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2671
+#: boot-installer.xml:2678
 #, no-c-format
 msgid "CD-ROM Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2672
+#: boot-installer.xml:2679
 #, no-c-format
 msgid "Sometimes, especially with older CD-ROM drives, the installer may fail to boot from a CD-ROM. The installer may also &mdash; even after booting successfully from CD-ROM &mdash; fail to recognize the CD-ROM or return errors while reading from it during the installation."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2679
+#: boot-installer.xml:2686
 #, no-c-format
 msgid "There are many different possible causes for these problems. We can only list some common issues and provide general suggestions on how to deal with them. The rest is up to you."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2685
+#: boot-installer.xml:2692
 #, no-c-format
 msgid "There are two very simple things that you should try first."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2690
+#: boot-installer.xml:2697
 #, no-c-format
 msgid "If the CD-ROM does not boot, check that it was inserted correctly and that it is not dirty."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2696
+#: boot-installer.xml:2703
 #, no-c-format
 msgid "If the installer fails to recognize a CD-ROM, try just running the option <menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </menuchoice> a second time. Some DMA related issues with very old CD-ROM drives are known to be resolved in this way."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2706
+#: boot-installer.xml:2713
 #, no-c-format
 msgid "If this does not work, then try the suggestions in the subsections below. Most, but not all, suggestions discussed there are valid for both CD-ROM and DVD, but we'll use the term CD-ROM for simplicity."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2712
+#: boot-installer.xml:2719
 #, no-c-format
 msgid "If you cannot get the installation working from CD-ROM, try one of the other installation methods that are available."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2720
+#: boot-installer.xml:2727
 #, no-c-format
 msgid "Common issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2723
+#: boot-installer.xml:2730
 #, no-c-format
 msgid "Some older CD-ROM drives do not support reading from discs that were burned at high speeds using a modern CD writer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2740
+#: boot-installer.xml:2747
 #, no-c-format
 msgid "Some very old CD-ROM drives do not work correctly if <quote>direct memory access</quote> (DMA) is enabled for them."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2751
+#: boot-installer.xml:2758
 #, no-c-format
 msgid "How to investigate and maybe solve issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2752
+#: boot-installer.xml:2759
 #, no-c-format
 msgid "If the CD-ROM fails to boot, try the suggestions listed below."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2757
+#: boot-installer.xml:2764
 #, no-c-format
 msgid "Check that your BIOS actually supports booting from CD-ROM (only an issue for very old systems) and that CD booting is enabled in the BIOS."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2764
+#: boot-installer.xml:2771
 #, no-c-format
 msgid ""
       "If you downloaded an iso image, check that the md5sum of that image matches the one listed for the image in the <filename>MD5SUMS</filename> file that should be present in the same location as where you downloaded the image from. <informalexample><screen>\n"
@@ -1984,7 +1996,7 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:2777
+#: boot-installer.xml:2784
 #, no-c-format
 msgid ""
       "$ dd if=/dev/cdrom | \\\n"
@@ -1997,19 +2009,19 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2782
+#: boot-installer.xml:2789
 #, no-c-format
 msgid "If, after the installer has been booted successfully, the CD-ROM is not detected, sometimes simply trying again may solve the problem. If you have more than one CD-ROM drive, try changing the CD-ROM to the other drive. If that does not work or if the CD-ROM is recognized but there are errors when reading from it, try the suggestions listed below. Some basic knowledge of &arch-kernel; is required for this. To execute any of the commands, you should first switch to the second virtual console (VT2) and activate the shell there."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2794
+#: boot-installer.xml:2801
 #, no-c-format
 msgid "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> (use <command>nano</command> as editor) to check for any specific error messages. After that, also check the output of <command>dmesg</command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2801
+#: boot-installer.xml:2808
 #, no-c-format
 msgid ""
       "Check in the output of <command>dmesg</command> if your CD-ROM drive was recognized. You should see something like (the lines do not necessarily have to be consecutive): <informalexample><screen>\n"
@@ -2022,13 +2034,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2815
+#: boot-installer.xml:2822
 #, no-c-format
 msgid "Check that there is a device node for your CD-ROM drive under <filename>/dev/</filename>. In the example above, this would be <filename>/dev/hdc</filename>. There should also be a <filename>/dev/cdrom</filename>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2823
+#: boot-installer.xml:2830
 #, no-c-format
 msgid ""
       "Use the <command>mount</command> command to check if the CD-ROM is already mounted; if not, try mounting it manually: <informalexample><screen>\n"
@@ -2037,7 +2049,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2833
+#: boot-installer.xml:2840
 #, no-c-format
 msgid ""
       "Check if DMA is currently enabled: <informalexample><screen>\n"
@@ -2050,151 +2062,151 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2848
+#: boot-installer.xml:2855
 #, no-c-format
 msgid "If there are any problems during the installation, try checking the integrity of the CD-ROM using the option near the bottom of the installer's main menu. This option can also be used as a general test if the CD-ROM can be read reliably."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2863
+#: boot-installer.xml:2870
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2865
+#: boot-installer.xml:2872
 #, no-c-format
 msgid "The biggest problem for people using floppy disks to install &debian; seems to be floppy disk reliability."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2870
+#: boot-installer.xml:2877
 #, no-c-format
 msgid "The boot floppy is the floppy with the worst problems, because it is read by the hardware directly, before Linux boots. Often, the hardware doesn't read as reliably as the Linux floppy disk driver, and may just stop without printing an error message if it reads incorrect data. There can also be failures in the driver floppies, most of which indicate themselves with a flood of messages about disk I/O errors."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2879
+#: boot-installer.xml:2886
 #, no-c-format
 msgid "If you are having the installation stall at a particular floppy, the first thing you should do is write the image to a <emphasis>different</emphasis> floppy and see if that solves the problem. Simply reformatting the old floppy may not be sufficient, even if it appears that the floppy was reformatted and written with no errors. It is sometimes useful to try writing the floppy on a different system."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2888
+#: boot-installer.xml:2895
 #, no-c-format
 msgid "One user reports he had to write the images to floppy <emphasis>three</emphasis> times before one worked, and then everything was fine with the third floppy."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2894
+#: boot-installer.xml:2901
 #, no-c-format
 msgid "Normally you should not have to download a floppy image again, but if you are experiencing problems it is always useful to verify that the images were downloaded correctly by verifying their md5sums."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2900
+#: boot-installer.xml:2907
 #, no-c-format
 msgid "Other users have reported that simply rebooting a few times with the same floppy in the floppy drive can lead to a successful boot. This is all due to buggy hardware or firmware floppy drivers."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2909
+#: boot-installer.xml:2916
 #, no-c-format
 msgid "Boot Configuration"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2911
+#: boot-installer.xml:2918
 #, no-c-format
 msgid "If you have problems and the kernel hangs during the boot process, doesn't recognize peripherals you actually have, or drives are not recognized properly, the first thing to check is the boot parameters, as discussed in <xref linkend=\"boot-parms\"/>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2920
+#: boot-installer.xml:2927
 #, no-c-format
 msgid "In some cases, malfunctions can be caused by missing device firmware (see <xref linkend=\"hardware-firmware\"/> and <xref linkend=\"loading-firmware\"/>)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2931
+#: boot-installer.xml:2938
 #, no-c-format
 msgid "If software speech synthesis does not work, there is most probably an issue with your sound board, usually because either the driver for it is not included in the installer, or because it has unusual mixer level names which are set to muted by default. You should thus submit a bug report which includes the output of the following commands, run on the same machine from a Linux system which is known to have sound working (e.g., a live CD)."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2942
+#: boot-installer.xml:2949
 #, no-c-format
 msgid "dmesg"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2944
+#: boot-installer.xml:2951
 #, no-c-format
 msgid "lspci"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2946
+#: boot-installer.xml:2953
 #, no-c-format
 msgid "lsmod"
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2948
+#: boot-installer.xml:2955
 #, no-c-format
 msgid "amixer"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2956 boot-installer.xml:3067
+#: boot-installer.xml:2963 boot-installer.xml:3074
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2957
+#: boot-installer.xml:2964
 #, no-c-format
 msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3008
+#: boot-installer.xml:3015
 #, no-c-format
 msgid "If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter <userinput>fb=false</userinput> to disable the framebuffer console. Only a reduced set of languages will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3022
+#: boot-installer.xml:3029
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3023
+#: boot-installer.xml:3030
 #, no-c-format
 msgid "Some very old laptop models produced by Dell are known to crash when PCMCIA device detection tries to access some hardware addresses. Other laptops may display similar problems. If you experience such a problem and you don't need PCMCIA support during the installation, you can disable PCMCIA using the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can then configure PCMCIA after the installation is completed and exclude the resource range causing the problems."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3033
+#: boot-installer.xml:3040
 #, no-c-format
 msgid "Alternatively, you can boot the installer in expert mode. You will then be asked to enter the resource range options your hardware needs. For example, if you have one of the Dell laptops mentioned above, you should enter <userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list of some common resource range options in the <ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the commas, if any, when you enter this value in the installer."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3068
+#: boot-installer.xml:3075
 #, no-c-format
 msgid "There are some common installation problems that are worth mentioning."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3074
+#: boot-installer.xml:3081
 #, no-c-format
 msgid "Misdirected video output"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3075
+#: boot-installer.xml:3082
 #, no-c-format
 msgid ""
       "It is fairly common for &arch-title; to have two video cards in one machine, for example an ATI card and a Sun Creator 3D. In some cases, this may result in the video output getting misdirected soon after the system boots. In typical cases, the display will only show: <informalexample><screen>\n"
@@ -2204,85 +2216,85 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3089
+#: boot-installer.xml:3096
 #, no-c-format
 msgid "Note that you may also have to manually add this parameter to the silo configuration (edit <filename>/target/etc/silo.conf</filename> before rebooting) and, if you installed X11, modify the video driver in <filename>/etc/X11/xorg.conf</filename>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3100
+#: boot-installer.xml:3107
 #, no-c-format
 msgid "Failure to Boot or Install from CD-ROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3101
+#: boot-installer.xml:3108
 #, no-c-format
 msgid "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if they do boot, there may be inexplicable failures during the installation. Most problems have been reported with SunBlade systems."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3107
+#: boot-installer.xml:3114
 #, no-c-format
 msgid "We recommend to install such systems by netbooting the installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3116
+#: boot-installer.xml:3123
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3118
+#: boot-installer.xml:3125
 #, no-c-format
 msgid "During the boot sequence, you may see many messages in the form <computeroutput>can't find <replaceable>something</replaceable></computeroutput>, or <computeroutput><replaceable>something</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>something</replaceable></computeroutput>, or even <computeroutput>this driver release depends on <replaceable>something</replaceable></computeroutput>. Most of these messages are harmless. You see them because the kernel for the installation system is built to run on computers with many different peripheral devices. Obviously, no one computer will have every possible peripheral device, so the operating system may emit a few complaints while it looks for peripherals you don't own. You may also see the system pause for a while. This happens when it is waiting for a device to respond, and that device is not present on your system. If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later <phrase arch=\"linux-any\">(see <xref linkend=\"kernel-baking\"/>)</phrase>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3143
+#: boot-installer.xml:3150
 #, no-c-format
 msgid "Reporting Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3144
+#: boot-installer.xml:3151
 #, no-c-format
 msgid "If you get through the initial boot phase but cannot complete the install, the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them using a web browser. This information may provide clues as to what went wrong and how to fix it. If you are submitting a bug report, you may want to attach this information to the bug report."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3155
+#: boot-installer.xml:3162
 #, no-c-format
 msgid "Other pertinent installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/installer/</filename> after the computer has been booted into the installed system."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3166
+#: boot-installer.xml:3173
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3167
+#: boot-installer.xml:3174
 #, no-c-format
 msgid "If you still have problems, please submit an installation report. We also encourage installation reports to be sent even if the installation is successful, so that we can get as much information as possible on the largest number of hardware configurations."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3174
+#: boot-installer.xml:3181
 #, no-c-format
 msgid "Note that your installation report will be published in the Debian Bug Tracking System (BTS) and forwarded to a public mailing list. Make sure that you use an e-mail address that you do not mind being made public."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3180
+#: boot-installer.xml:3187
 #, no-c-format
 msgid "If you have a working &debian; system, the easiest way to send an installation report is to install the <classname>installation-report</classname> and <classname>reportbug</classname> packages (<command>aptitude install installation-report reportbug</command>), configure <classname>reportbug</classname> as explained in <xref linkend=\"mail-outgoing\"/>, and run the command <command>reportbug installation-reports</command>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3190
+#: boot-installer.xml:3197
 #, no-c-format
 msgid ""
       "Alternatively you can use this template when filling out installation reports, and file the report as a bug report against the <classname>installation-reports</classname> pseudo package, by sending it to <email>submit@bugs.debian.org</email>. <informalexample><screen>\n"
diff --git a/po/pot/boot-new.pot b/po/pot/boot-new.pot
index 91ac50c19..e56c2f178 100644
--- a/po/pot/boot-new.pot
+++ b/po/pot/boot-new.pot
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2013-04-16 19:15+0000\n"
+"POT-Creation-Date: 2013-05-22 19:06+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"
@@ -238,44 +238,41 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:282
 #, no-c-format
-msgid ""
-      "If any volume holding noncritical system files could not be mounted (<filename>/usr</filename> or <filename>/var</filename>), the system should still boot and you should be able to mount the volumes manually like in the previous case. However, you will also need to (re)start any services usually running in your default runlevel because it is very likely that they were not started. The easiest way to achieve this is by switching to the first runlevel and back by entering <informalexample><screen>\n"
-      "<prompt>#</prompt> <userinput>init 1</userinput>\n"
-      "</screen></informalexample> at the shell prompt and pressing <keycombo> <keycap>Control</keycap> <keycap>D</keycap> </keycombo> when asked for the root password."
+msgid "If any volume holding noncritical system files could not be mounted (<filename>/usr</filename> or <filename>/var</filename>), the system should still boot and you should be able to mount the volumes manually like in the previous case. However, you will also need to (re)start any services usually running in your default runlevel because it is very likely that they were not started. The easiest way is to just reboot the computer."
 msgstr ""
 
 #. Tag: title
-#: boot-new.xml:305
+#: boot-new.xml:300
 #, no-c-format
 msgid "Log In"
 msgstr ""
 
 #. Tag: para
-#: boot-new.xml:307
+#: boot-new.xml:302
 #, no-c-format
 msgid "Once your system boots, you'll be presented with the login prompt. Log in using the personal login and password you selected during the installation process. Your system is now ready for use."
 msgstr ""
 
 #. Tag: para
-#: boot-new.xml:313
+#: boot-new.xml:308
 #, no-c-format
 msgid "If you are a new user, you may want to explore the documentation which is already installed on your system as you start to use it. There are currently several documentation systems, work is proceeding on integrating the different types of documentation. Here are a few starting points."
 msgstr ""
 
 #. Tag: para
-#: boot-new.xml:321
+#: boot-new.xml:316
 #, no-c-format
 msgid "Documentation accompanying programs you have installed can be found in <filename>/usr/share/doc/</filename>, under a subdirectory named after the program (or, more precise, the &debian; package that contains the program). However, more extensive documentation is often packaged separately in special documentation packages that are mostly not installed by default. For example, documentation about the package management tool <command>apt</command> can be found in the packages <classname>apt-doc</classname> or <classname>apt-howto</classname>."
 msgstr ""
 
 #. Tag: para
-#: boot-new.xml:332
+#: boot-new.xml:327
 #, no-c-format
 msgid "In addition, there are some special folders within the <filename>/usr/share/doc/</filename> hierarchy. Linux HOWTOs are installed in <emphasis>.gz</emphasis> (compressed) format, in <filename>/usr/share/doc/HOWTO/en-txt/</filename>. After installing <classname>dhelp</classname>, you will find a browsable index of documentation in <filename>/usr/share/doc/HTML/index.html</filename>."
 msgstr ""
 
 #. Tag: para
-#: boot-new.xml:341
+#: boot-new.xml:336
 #, no-c-format
 msgid ""
       "One easy way to view these documents using a text based browser is to enter the following commands: <informalexample><screen>\n"
@@ -285,13 +282,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-new.xml:351
+#: boot-new.xml:346
 #, no-c-format
 msgid "If you have a graphical desktop environment installed, you can also use its web browser. Start the web browser from the application menu and enter <userinput>/usr/share/doc/</userinput> in the address bar."
 msgstr ""
 
 #. Tag: para
-#: boot-new.xml:357
+#: boot-new.xml:352
 #, no-c-format
 msgid "You can also type <userinput>info <replaceable>command</replaceable></userinput> or <userinput>man <replaceable>command</replaceable></userinput> to see documentation on most commands available at the command prompt. Typing <userinput>help</userinput> will display help on shell commands. And typing a command followed by <userinput>--help</userinput> will usually display a short summary of the command's usage. If a command's results scroll past the top of the screen, type <userinput>|&nbsp;more</userinput> after the command to cause the results to pause before scrolling past the top of the screen. To see a list of all commands available which begin with a certain letter, type the letter and then two tabs."
 msgstr ""
diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot
index 11ea563f2..8514ff317 100644
--- a/po/pot/hardware.pot
+++ b/po/pot/hardware.pot
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2013-04-16 19:15+0000\n"
+"POT-Creation-Date: 2013-05-22 19:06+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"
@@ -57,13 +57,13 @@ msgid "&debian; GNU/Linux &release; supports eleven major architectures and seve
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:53 hardware.xml:186
+#: hardware.xml:53 hardware.xml:180
 #, no-c-format
 msgid "Architecture"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:53 hardware.xml:186
+#: hardware.xml:53 hardware.xml:180
 #, no-c-format
 msgid "&debian; Designation"
 msgstr ""
@@ -81,7 +81,7 @@ msgid "Flavor"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:60 hardware.xml:192
+#: hardware.xml:60 hardware.xml:186
 #, no-c-format
 msgid "Intel x86-based"
 msgstr ""
@@ -93,7 +93,7 @@ msgid "i386"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:67 hardware.xml:197
+#: hardware.xml:67 hardware.xml:191
 #, no-c-format
 msgid "AMD64 &amp; Intel 64"
 msgstr ""
@@ -375,1459 +375,1477 @@ msgid "s390"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:157 hardware.xml:167
+#: hardware.xml:157 hardware.xml:164
 #, no-c-format
 msgid "IPL from VM-reader and DASD"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:158 hardware.xml:168
+#: hardware.xml:158 hardware.xml:165
 #, no-c-format
 msgid "generic"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:160 hardware.xml:170
-#, no-c-format
-msgid "IPL from tape"
-msgstr ""
-
-#. Tag: entry
-#: hardware.xml:161 hardware.xml:171
-#, no-c-format
-msgid "tape"
-msgstr ""
-
-#. Tag: entry
-#: hardware.xml:165
+#: hardware.xml:162
 #, no-c-format
 msgid "64bit IBM S/390"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:166
+#: hardware.xml:163
 #, no-c-format
 msgid "s390x"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:176
+#: hardware.xml:170
 #, no-c-format
 msgid "&debian; GNU/kFreeBSD &release; supports two architectures."
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:193
+#: hardware.xml:187
 #, no-c-format
 msgid "kfreebsd-i386"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:198
+#: hardware.xml:192
 #, no-c-format
 msgid "kfreebsd-amd64"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:203
+#: hardware.xml:197
 #, no-c-format
 msgid "This document covers installation for the <emphasis>&arch-title;</emphasis> architecture using the <emphasis>&arch-kernel;</emphasis> kernel. If you are looking for information on any of the other &debian;-supported architectures take a look at the <ulink url=\"http://www.debian.org/ports/\">&debian;-Ports</ulink> pages."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:213
+#: hardware.xml:207
 #, no-c-format
 msgid "The &arch-title; architecture only supports Intel Itanium processors and not the much more common 64-bit processors from the Intel 64 family (including e.g. the Pentium&nbsp;D and the Core2&nbsp;Duo). Those systems are supported by the <emphasis>amd64</emphasis> architecture or, if you prefer a 32-bit userland, the <emphasis>i386</emphasis> architecture."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:223
+#: hardware.xml:217
 #, no-c-format
 msgid "This is the first official release of &debian-gnu; for the &arch-title; architecture. We feel that it has proven itself sufficiently to be released. However, because it has not had the exposure (and hence testing by users) that some other architectures have had, you may encounter a few bugs. Use our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any problems; make sure to mention the fact that the bug is on the &arch-title; platform using the <emphasis>&arch-kernel;</emphasis> kernel. It can be necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink> as well."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:245
+#: hardware.xml:239
 #, no-c-format
 msgid "CPU Support"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:246
+#: hardware.xml:240
 #, no-c-format
 msgid "Both AMD64 and Intel 64 processors are supported."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:271 hardware.xml:362 hardware.xml:381 hardware.xml:464 hardware.xml:522 hardware.xml:575
+#: hardware.xml:265 hardware.xml:356 hardware.xml:375 hardware.xml:458 hardware.xml:516 hardware.xml:569
 #, no-c-format
 msgid "CPU, Main Boards, and Video Support"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:273
+#: hardware.xml:267
 #, no-c-format
 msgid "Each distinct ARM architecture requires its own kernel. Because of this the standard &debian; distribution only supports installation on a number of the most common platforms. The &debian; userland however may be used by <emphasis>any</emphasis> ARM CPU."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:282
+#: hardware.xml:276
 #, no-c-format
 msgid "Most ARM CPUs may be run in either endian mode (big or little). However, the majority of current system implementation uses little-endian mode. &debian; currently only supports little-endian ARM systems."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:290
+#: hardware.xml:284
 #, no-c-format
 msgid "The supported platforms are:"
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:297
+#: hardware.xml:291
 #, no-c-format
 msgid "IOP32x"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:298
+#: hardware.xml:292
 #, no-c-format
 msgid "Intel's I/O Processor (IOP) line is found in a number of products related to data storage and processing. &debian; currently supports the IOP32x platform, featuring the IOP 80219 and 32x chips commonly found in Network Attached Storage (NAS) devices. &debian; explicitly supports two such devices: the <ulink url=\"&url-arm-cyrius-glantank;\">GLAN Tank</ulink> from IO-Data and the <ulink url=\"&url-arm-cyrius-n2100;\">Thecus N2100</ulink>."
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:311
+#: hardware.xml:305
 #, no-c-format
 msgid "Kirkwood"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:312
+#: hardware.xml:306
 #, no-c-format
 msgid "Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. We currently support the following Kirkwood based devices: OpenRD (OpenRD-Base, OpenRD-Client and OpenRD-Ultimate), <ulink url=\"&url-arm-cyrius-sheevaplug;\">plug computers (SheevaPlug, GuruPlug and DreamPlug)</ulink>, <ulink url=\"&url-arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (all TS-11x, TS-21x and TS-41x models), and LaCie NASes (Network Space v2, Network Space Max v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2)."
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:328
+#: hardware.xml:322
 #, no-c-format
 msgid "Orion5x"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:329
+#: hardware.xml:323
 #, no-c-format
 msgid "Orion is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. There are many Network Attached Storage (NAS) devices on the market that are based on an Orion chip. We currently support the following Orion based devices: <ulink url=\"&url-arm-cyrius-kuroboxpro;\">Buffalo Kurobox</ulink>, <ulink url=\"&url-arm-cyrius-dns323;\">D-Link DNS-323</ulink> and <ulink url=\"&url-arm-cyrius-mv2120;\">HP mv2120</ulink>."
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:343
+#: hardware.xml:337
 #, no-c-format
 msgid "<term>Versatile</term>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:344
+#: hardware.xml:338
 #, no-c-format
 msgid "The Versatile platform is emulated by QEMU and is therefore a nice way to test and run &debian; on ARM if you don't have the hardware."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:363
+#: hardware.xml:357
 #, no-c-format
 msgid "There are two major support <emphasis>&architecture;</emphasis> flavors: PA-RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at 32-bit processors whereas the 2.0 architecture is targeted to the 64-bit processors. Some systems are able to run either kernel. In both cases, the userland is 32-bit. There is the possibility of a 64-bit userland in the future."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:382
+#: hardware.xml:376
 #, no-c-format
 msgid "Complete information concerning supported peripherals can be found at <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. This section merely outlines the basics."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:390 hardware.xml:499
+#: hardware.xml:384 hardware.xml:493
 #, no-c-format
 msgid "<title>CPU</title>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:391
+#: hardware.xml:385
 #, no-c-format
 msgid "Nearly all x86-based (IA-32) processors still in use in personal computers are supported, including all varieties of Intel's \"Pentium\" series. This also includes 32-bit AMD and VIA (former Cyrix) processors, and processors like the Athlon XP and Intel P4 Xeon."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:398
+#: hardware.xml:392
 #, no-c-format
 msgid "However, &debian; GNU/Linux &releasename; will <emphasis>not</emphasis> run on 386 or earlier processors. Despite the architecture name \"i386\", support for actual 80386 processors (and their clones) was dropped with the Sarge (r3.1) release of &debian;<footnote> <para> We have long tried to avoid this, but in the end it was necessary due a unfortunate series of issues with the compiler and the kernel, starting with an bug in the C++ ABI provided by GCC. You should still be able to run &debian; GNU/Linux on actual 80386 processors if you compile your own kernel and compile all packages from source, but that is beyond the scope of this manual. </para> </footnote>. (No version of Linux has ever supported the 286 or earlier chips in the series.) All i486 and later processors are still supported<footnote> <para> Many &debian; packages will actually run slightly faster on modern computers as a positive side effect of dropping support for these old chips. The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the i386, introduced in 1986, did not have. Previously, these could not be easily used by most &debian; packages; now they can. </para> </footnote>."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:431
+#: hardware.xml:425
 #, no-c-format
 msgid "If your system has a 64-bit processor from the AMD64 or Intel 64 families, you will probably want to use the installer for the amd64 architecture instead of the installer for the (32-bit) i386 architecture."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:440
+#: hardware.xml:434
 #, no-c-format
 msgid "I/O Bus"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:441
+#: hardware.xml:435
 #, no-c-format
 msgid "The system bus is the part of the motherboard which allows the CPU to communicate with peripherals such as storage devices. Your computer must use the ISA, EISA, PCI, PCIe, PCI-X, or VESA Local Bus (VLB, sometimes called the VL bus). Essentially all personal computers sold in recent years use one of these."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:465
+#: hardware.xml:459
 #, no-c-format
 msgid "&debian; on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> SGI IP22: this platform includes the SGI machines Indy, Indigo 2 and Challenge S. Since these machines are very similar, whenever this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. </para></listitem> <listitem><para> SGI IP32: this platform is generally known as SGI O2. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run &debian; on MIPS if you don't have the hardware. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the &debian; installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:500
+#: hardware.xml:494
 #, no-c-format
 msgid "On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and R5000 processors are supported by the &debian; installation system on big endian MIPS. On SGI IP32, currently only systems based on the R5000 are supported."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:506
+#: hardware.xml:500
 #, no-c-format
 msgid "Some MIPS machines can be operated in both big and little endian mode. For little endian MIPS, please read the documentation for the mipsel architecture."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:523
+#: hardware.xml:517
 #, no-c-format
 msgid "&debian; on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run &debian; on MIPS if you don't have the hardware. </para></listitem> </itemizedlist> Complete information regarding supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the &debian; installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-listname; mailing list</ulink>."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:551
+#: hardware.xml:545
 #, no-c-format
 msgid "CPU/Machine types"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:553
+#: hardware.xml:547
 #, no-c-format
 msgid "All MIPS based Cobalt machines are supported with the exception of the Qube 2700 (Qube 1)."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:561
+#: hardware.xml:555
 #, no-c-format
 msgid "Supported console options"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:562
+#: hardware.xml:556
 #, no-c-format
 msgid "Cobalt machines use 115200 bps."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:576
+#: hardware.xml:570
 #, no-c-format
 msgid "For &debian-gnu; &release; only the PMac (Power-Macintosh or PowerMac) and PreP subarchitectures are supported."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:597
+#: hardware.xml:591
 #, no-c-format
 msgid "Kernel Flavours"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:599
+#: hardware.xml:593
 #, no-c-format
 msgid "There are two flavours of the powerpc kernel in &debian;, based on the CPU type:"
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:606
+#: hardware.xml:600
 #, no-c-format
 msgid "<term>powerpc</term>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:607
+#: hardware.xml:601
 #, no-c-format
-msgid "Most systems use this kernel flavour, which supports the PowerPC 601, 603, 604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and including the one marketed as G4 use one of these processors."
+msgid "This kernel flavour supports the PowerPC 601, 603, 604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and including the one marketed as G4 use one of these processors."
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:617
+#: hardware.xml:611
+#, no-c-format
+msgid "powerpc-smp"
+msgstr ""
+
+#. Tag: para
+#: hardware.xml:612
+#, no-c-format
+msgid "All Apple PowerMac G4 SMP machines."
+msgstr ""
+
+#. Tag: term
+#: hardware.xml:620
 #, no-c-format
 msgid "power64"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:618
+#: hardware.xml:621
 #, no-c-format
 msgid "The power64 kernel flavour supports the following CPUs:"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:622
+#: hardware.xml:625
 #, no-c-format
 msgid "The POWER3 processor is used in older IBM 64-bit server systems: known models include the IntelliStation POWER Model 265, the pSeries 610 and 640, and the RS/6000 7044-170, 7043-260, and 7044-270."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:628
+#: hardware.xml:631
 #, no-c-format
 msgid "The POWER4 processor is used in more recent IBM 64-bit server systems: known models include the pSeries 615, 630, 650, 655, 670, and 690."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:633
+#: hardware.xml:636
 #, no-c-format
-msgid "Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 architecture, and use this kernel flavour."
+msgid "Systems using the PPC970 processor (Apple G5, YDL PowerStation, IBM Intellistation POWER 185) are also based on the POWER4 architecture, and use this kernel flavour."
+msgstr ""
+
+#. Tag: para
+#: hardware.xml:642
+#, no-c-format
+msgid "Newer IBM systems using POWER5, POWER6, and POWER7 processors."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:667
+#: hardware.xml:675
 #, no-c-format
 msgid "Power Macintosh (pmac) subarchitecture"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:669
+#: hardware.xml:677
 #, no-c-format
 msgid "Apple (and briefly a few other manufacturers &mdash; Power Computing, for example) made a series of Macintosh computers based on the PowerPC processor. For purposes of architecture support, they are categorized as NuBus (not supported by &debian;), OldWorld, and NewWorld."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:676
+#: hardware.xml:684
 #, no-c-format
 msgid "OldWorld systems are most Power Macintoshes with a floppy drive and a PCI bus. Most 603, 603e, 604, and 604e based Power Macintoshes are OldWorld machines. Those pre-iMac PowerPC models from Apple use a four digit naming scheme, except for the beige colored G3 systems, which are also OldWorld."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:684
+#: hardware.xml:692
 #, no-c-format
 msgid "The so called NewWorld PowerMacs are any PowerMacs in translucent colored plastic cases and later models. That includes all iMacs, iBooks, G4 systems, blue colored G3 systems, and most PowerBooks manufactured in and after 1999. The NewWorld PowerMacs are also known for using the <quote>ROM in RAM</quote> system for MacOS, and were manufactured from mid-1998 onwards."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:692
+#: hardware.xml:700
 #, no-c-format
 msgid "Specifications for Apple hardware are available at <ulink url=\"http://www.info.apple.com/support/applespec.html\">AppleSpec</ulink>, and, for older hardware, <ulink url=\"http://www.info.apple.com/support/applespec.legacy/index.html\">AppleSpec Legacy</ulink>."
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:708 hardware.xml:843 hardware.xml:887 hardware.xml:916
+#: hardware.xml:716 hardware.xml:851 hardware.xml:895 hardware.xml:928
 #, no-c-format
 msgid "Model Name/Number"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:709
+#: hardware.xml:717
 #, no-c-format
 msgid "Generation"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:715
+#: hardware.xml:723
 #, no-c-format
 msgid "Apple"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:716
+#: hardware.xml:724
 #, no-c-format
 msgid "iMac Bondi Blue, 5 Flavors, Slot Loading"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:717 hardware.xml:720 hardware.xml:723 hardware.xml:726 hardware.xml:729 hardware.xml:732 hardware.xml:735 hardware.xml:738 hardware.xml:741 hardware.xml:744 hardware.xml:747 hardware.xml:750 hardware.xml:753 hardware.xml:756 hardware.xml:759 hardware.xml:762
+#: hardware.xml:725 hardware.xml:728 hardware.xml:731 hardware.xml:734 hardware.xml:737 hardware.xml:740 hardware.xml:743 hardware.xml:746 hardware.xml:749 hardware.xml:752 hardware.xml:755 hardware.xml:758 hardware.xml:761 hardware.xml:764 hardware.xml:767 hardware.xml:770
 #, no-c-format
 msgid "NewWorld"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:719
+#: hardware.xml:727
 #, no-c-format
 msgid "iMac Summer 2000, Early 2001"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:722
+#: hardware.xml:730
 #, no-c-format
 msgid "iMac G5"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:725
+#: hardware.xml:733
 #, no-c-format
 msgid "iBook, iBook SE, iBook Dual USB"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:728
+#: hardware.xml:736
 #, no-c-format
 msgid "iBook2"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:731
+#: hardware.xml:739
 #, no-c-format
 msgid "iBook G4"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:734
+#: hardware.xml:742
 #, no-c-format
 msgid "Power Macintosh Blue and White (B&amp;W) G3"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:737
+#: hardware.xml:745
 #, no-c-format
 msgid "Power Macintosh G4 PCI, AGP, Cube"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:740
+#: hardware.xml:748
 #, no-c-format
 msgid "Power Macintosh G4 Gigabit Ethernet"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:743
+#: hardware.xml:751
 #, no-c-format
 msgid "Power Macintosh G4 Digital Audio, Quicksilver"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:746
+#: hardware.xml:754
 #, no-c-format
 msgid "Power Macintosh G5"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:749
+#: hardware.xml:757
 #, no-c-format
 msgid "PowerBook G3 FireWire Pismo (2000)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:752
+#: hardware.xml:760
 #, no-c-format
 msgid "PowerBook G3 Lombard (1999)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:755
+#: hardware.xml:763
 #, no-c-format
 msgid "PowerBook G4 Titanium"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:758
+#: hardware.xml:766
 #, no-c-format
 msgid "PowerBook G4 Aluminum"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:761
+#: hardware.xml:769
 #, no-c-format
 msgid "Xserve G5"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:764
+#: hardware.xml:772
 #, no-c-format
 msgid "Performa 4400, 54xx, 5500"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:765 hardware.xml:768 hardware.xml:771 hardware.xml:774 hardware.xml:777 hardware.xml:780 hardware.xml:783 hardware.xml:786 hardware.xml:789 hardware.xml:792 hardware.xml:795 hardware.xml:798 hardware.xml:804 hardware.xml:807 hardware.xml:813 hardware.xml:819 hardware.xml:825
+#: hardware.xml:773 hardware.xml:776 hardware.xml:779 hardware.xml:782 hardware.xml:785 hardware.xml:788 hardware.xml:791 hardware.xml:794 hardware.xml:797 hardware.xml:800 hardware.xml:803 hardware.xml:806 hardware.xml:812 hardware.xml:815 hardware.xml:821 hardware.xml:827 hardware.xml:833
 #, no-c-format
 msgid "OldWorld"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:767
+#: hardware.xml:775
 #, no-c-format
 msgid "Performa 6360, 6400, 6500"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:770
+#: hardware.xml:778
 #, no-c-format
 msgid "Power Macintosh 4400, 5400"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:773
+#: hardware.xml:781
 #, no-c-format
 msgid "Power Macintosh 7200, 7300, 7500, 7600"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:776
+#: hardware.xml:784
 #, no-c-format
 msgid "Power Macintosh 8200, 8500, 8600"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:779
+#: hardware.xml:787
 #, no-c-format
 msgid "Power Macintosh 9500, 9600"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:782
+#: hardware.xml:790
 #, no-c-format
 msgid "Power Macintosh (Beige) G3 Minitower"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:785
+#: hardware.xml:793
 #, no-c-format
 msgid "Power Macintosh (Beige) Desktop, All-in-One"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:788
+#: hardware.xml:796
 #, no-c-format
 msgid "PowerBook 2400, 3400, 3500"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:791
+#: hardware.xml:799
 #, no-c-format
 msgid "PowerBook G3 Wallstreet (1998)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:794
+#: hardware.xml:802
 #, no-c-format
 msgid "Twentieth Anniversary Macintosh"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:797
+#: hardware.xml:805
 #, no-c-format
 msgid "Workgroup Server 7250, 7350, 8550, 9650, G3"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:802
+#: hardware.xml:810
 #, no-c-format
 msgid "Power Computing"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:803
+#: hardware.xml:811
 #, no-c-format
 msgid "PowerBase, PowerTower / Pro, PowerWave"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:806
+#: hardware.xml:814
 #, no-c-format
 msgid "PowerCenter / Pro, PowerCurve"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:811
+#: hardware.xml:819
 #, no-c-format
 msgid "UMAX"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:812
+#: hardware.xml:820
 #, no-c-format
 msgid "C500, C600, J700, S900"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:817
+#: hardware.xml:825
 #, no-c-format
 msgid "<entry>APS</entry>"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:818
+#: hardware.xml:826
 #, no-c-format
 msgid "APS Tech M*Power 604e/2000"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:823 hardware.xml:849
+#: hardware.xml:831 hardware.xml:857
 #, no-c-format
 msgid "Motorola"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:824
+#: hardware.xml:832
 #, no-c-format
 msgid "Starmax 3000, 4000, 5000, 5500"
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:833
+#: hardware.xml:841
 #, no-c-format
 msgid "PReP subarchitecture"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:850
+#: hardware.xml:858
 #, no-c-format
 msgid "Firepower, PowerStack Series E, PowerStack II"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:852
+#: hardware.xml:860
 #, no-c-format
 msgid "MPC 7xx, 8xx"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:854
+#: hardware.xml:862
 #, no-c-format
 msgid "MTX, MTX+"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:856
+#: hardware.xml:864
 #, no-c-format
 msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:858
+#: hardware.xml:866
 #, no-c-format
 msgid "MCP(N)750"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:862 hardware.xml:893
+#: hardware.xml:870 hardware.xml:901
 #, no-c-format
 msgid "IBM RS/6000"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:863
+#: hardware.xml:871
 #, no-c-format
 msgid "40P, 43P"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:865
+#: hardware.xml:873
 #, no-c-format
 msgid "Power 830/850/860 (6070, 6050)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:867
+#: hardware.xml:875
 #, no-c-format
 msgid "6030, 7025, 7043"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:869
+#: hardware.xml:877
 #, no-c-format
 msgid "p640"
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:877
+#: hardware.xml:885
 #, no-c-format
-msgid "CHRP subarchitecture (unsupported)"
+msgid "CHRP subarchitecture"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:894
+#: hardware.xml:902
 #, no-c-format
 msgid "B50, 43P-150, 44P"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:897
+#: hardware.xml:905
 #, no-c-format
 msgid "Genesi"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:898
+#: hardware.xml:906
 #, no-c-format
 msgid "Pegasos I, Pegasos II"
 msgstr ""
 
+#. Tag: entry
+#: hardware.xml:909
+#, no-c-format
+msgid "Fixstars"
+msgstr ""
+
+#. Tag: entry
+#: hardware.xml:910
+#, no-c-format
+msgid "YDL PowerStation"
+msgstr ""
+
 #. Tag: title
-#: hardware.xml:906
+#: hardware.xml:918
 #, no-c-format
 msgid "APUS subarchitecture (unsupported)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:922
+#: hardware.xml:934
 #, no-c-format
 msgid "Amiga Power-UP Systems (APUS)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:923
+#: hardware.xml:935
 #, no-c-format
 msgid "A1200, A3000, A4000"
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:931
+#: hardware.xml:943
 #, no-c-format
 msgid "Nubus PowerMac subarchitecture (unsupported)"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:933
+#: hardware.xml:945
 #, no-c-format
 msgid "NuBus systems are not currently supported by &debian;/powerpc. The monolithic Linux/PPC kernel architecture does not have support for these machines; instead, one must use the MkLinux Mach microkernel, which &debian; does not yet support. These include the following: <itemizedlist> <listitem><para> Power Macintosh 6100, 7100, 8100 </para></listitem> <listitem><para> Performa 5200, 6200, 6300 </para></listitem> <listitem><para> Powerbook 1400, 2300, and 5300 </para></listitem> <listitem><para> Workgroup Server 6150, 8150, 9150 </para></listitem> </itemizedlist> A linux kernel for these machines and limited support is available at <ulink url=\"http://nubus-pmac.sourceforge.net/\"></ulink>."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:970
+#: hardware.xml:982
 #, no-c-format
 msgid "Non-PowerPC Macs"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:972
+#: hardware.xml:984
 #, no-c-format
 msgid "Macintosh computers using the 680x0 series of processors are <emphasis>not</emphasis> in the PowerPC family but are instead m68k machines. Those models start with <quote>Mac II</quote> series, go on to the <quote>LC</quote> family, then the Centris series, and culminate in the Quadras and Performas. These models usually have a Roman numeral or 3-digit model number such as Mac IIcx, LCIII or Quadra 950."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:981
+#: hardware.xml:993
 #, no-c-format
 msgid "This model range started with the Mac II (Mac II, IIx, IIcx, IIci, IIsi, IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, 550, 575, 580, 630), then the Mac TV, then the Centris (610, 650, 660AV), the Quadra (605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950), and finally the Performa 200-640CD."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:989
+#: hardware.xml:1001
 #, no-c-format
 msgid "In laptops, it started with the Mac Portable, then the PowerBook 100-190cs and the PowerBook Duo 210-550c (excluding PowerBook 500 which is Nubus, please see the section above)."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1005
+#: hardware.xml:1017
 #, no-c-format
 msgid "zSeries and System z machine types"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1006
+#: hardware.xml:1018
 #, no-c-format
 msgid "Since &debian; Squeeze, support for booting in ESA/390 mode was dropped. Your machine needs to support the z/Architecture, 64-bit support is mandatory. The userland of the s390 port is still compiled for ESA/390, though. All zSeries and System z hardware is fully supported. &arch-title; support software is included from the kernel 3.1 development stream. The most current information about IBM's Linux support can be found at the <ulink url=\"http://www.ibm.com/developerworks/linux/linux390/development_technical.html\"> Linux on <trademark class=\"registered\">System z</trademark> page on developerWorks</ulink>."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1023
+#: hardware.xml:1035
 #, no-c-format
 msgid "PAV and HyperPAV"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1024
+#: hardware.xml:1036
 #, no-c-format
 msgid "PAV and HyperPAV are supported transparently, multipathing is not needed to take advantage of these storage system features. Be sure to configure the devices during DASD device selection. The alias devices will not be offered neither for formatting, partitioning nor direct use."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1040
+#: hardware.xml:1052
 #, no-c-format
 msgid "CPU and Main Boards Support"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1041
+#: hardware.xml:1053
 #, no-c-format
 msgid "Sparc-based hardware is divided into a number of different subarchitectures, identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u or sun4v. The following list describes what machines they include and what level of support may be expected for each of them."
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:1052
+#: hardware.xml:1064
 #, no-c-format
 msgid "sun4, sun4c, sun4d, sun4m"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1054
+#: hardware.xml:1066
 #, no-c-format
 msgid "None of these 32-bit sparc subarchitectures (sparc32) is supported. For a complete list of machines belonging to these subarchitectures, please consult the <ulink url=\"http://en.wikipedia.org/wiki/SPARCstation\">Wikipedia SPARCstation page</ulink>."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1061
+#: hardware.xml:1073
 #, no-c-format
 msgid "The last &debian; release to support sparc32 was Etch, but even then only for sun4m systems. Support for the other 32-bits subarchitectures had already been discontinued after earlier releases."
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:1071
+#: hardware.xml:1083
 #, no-c-format
 msgid "<term>sun4u</term>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1073
+#: hardware.xml:1085
 #, no-c-format
 msgid "This subarchitecture includes all 64-bit machines (sparc64) based on the UltraSparc processor and its clones. Most of the machines are well supported, even though for some you may experience problems booting from CD due to firmware or bootloader bugs (this problem may be worked around by using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP configurations respectively."
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:1086
+#: hardware.xml:1098
 #, no-c-format
 msgid "<term>sun4v</term>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1088
+#: hardware.xml:1100
 #, no-c-format
 msgid "This is the newest addition to the Sparc family, which includes machines based on the Niagara multi-core CPUs. At the moment such CPUs are only available in T1000 and T2000 servers by Sun, and are well supported. Use the sparc64-smp kernel."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1099
+#: hardware.xml:1111
 #, no-c-format
 msgid "Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are not supported due to lack of support in the Linux kernel."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1108
+#: hardware.xml:1120
 #, no-c-format
 msgid "Laptops"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1109
+#: hardware.xml:1121
 #, no-c-format
 msgid "From a technical point of view, laptops are normal PCs, so all information regarding PC systems applies to laptops as well. Installations on laptops nowadays usually work out of the box, including things like automatically suspending the system on closing the lid and laptop specfic hardware buttons like those for disabling the wifi interfaces (<quote>airplane mode</quote>). Nonetheless sometimes the hardware vendors use specialized or proprietary hardware for some laptop-specific functions which might not be supported. To see if your particular laptop works well with GNU/Linux, see for example the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1126 hardware.xml:1146 hardware.xml:1174 hardware.xml:1197
+#: hardware.xml:1138 hardware.xml:1158 hardware.xml:1186 hardware.xml:1209
 #, no-c-format
 msgid "Multiple Processors"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1127
+#: hardware.xml:1139
 #, no-c-format
 msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture. Having multiple processors in a computer was originally only an issue for high-end server systems but has become quite common in recent years even for rather low-end desktop computers and laptops with the introduction of so called <quote>multi-core</quote> processors. These contain two or more processor units, called <quote>cores</quote>, in one physical chip."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1137
+#: hardware.xml:1149
 #, no-c-format
 msgid "The standard &debian; &release; kernel image has been compiled with SMP support. It is also usable on non-SMP systems without problems."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1148
+#: hardware.xml:1160
 #, no-c-format
 msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture. The standard &debian; &release; kernel image has been compiled with <firstterm>SMP-alternatives</firstterm> support. This means that the kernel will detect the number of processors (or processor cores) and will automatically deactivate SMP on uniprocessor systems."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1157
+#: hardware.xml:1169
 #, no-c-format
 msgid "Having multiple processors in a computer was originally only an issue for high-end server systems but has become quite common in recent years even for rather low-end desktop computers and laptops with the introduction of so called <quote>multi-core</quote> processors. These contain two or more processor units, called <quote>cores</quote>, in one physical chip."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1165
+#: hardware.xml:1177
 #, no-c-format
 msgid "The 486 flavour of the &debian; kernel image packages for &arch-title; is not compiled with SMP support."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1175
+#: hardware.xml:1187
 #, no-c-format
 msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture. However, the standard &debian; &release; kernel image does not support SMP. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use only the first CPU."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1184
+#: hardware.xml:1196
 #, no-c-format
 msgid "In order to take advantage of multiple processors, you'll have to replace the standard &debian; kernel.<phrase arch=\"linux-any\"> You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1198
+#: hardware.xml:1210
 #, no-c-format
 msgid "Multiprocessor support &mdash; also called <quote>symmetric multiprocessing</quote> or SMP &mdash; is available for this architecture, and is supported by a precompiled &debian; kernel image. Depending on your install media, this SMP-capable kernel may or may not be installed by default. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1208
+#: hardware.xml:1220
 #, no-c-format
 msgid "In order to take advantage of multiple processors, you should check to see if a kernel package that supports SMP is installed, and if not, choose an appropriate kernel package."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1214
+#: hardware.xml:1226
 #, no-c-format
 msgid "You can also build your own customized kernel to support SMP.<phrase arch=\"linux-any\"> You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you enable SMP is to select <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config.</phrase>"
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1225
+#: hardware.xml:1237
 #, no-c-format
 msgid "Graphics Card Support"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1226
+#: hardware.xml:1238
 #, no-c-format
 msgid "&debian;'s support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. On modern PCs, having a graphical display usually works out of the box. Whether advanced graphics card features such as 3D-hardware acceleration or hardware-accelerated video are available, depends on the actual graphics hardware used in the system and in some cases on the installation of additional <quote>firmware</quote> images (see <xref linkend=\"hardware-firmware\"/>). In very few cases there have been reports about hardware on which installation of additional graphics card firmware was required even for basic graphics support, but these have been rare exceptions."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1239
+#: hardware.xml:1251
 #, no-c-format
 msgid "Details on supported graphics cards and pointing devices can be found at <ulink url=\"&url-xorg;\"></ulink>. &debian; &release; ships with X.Org version &x11ver;."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1244
+#: hardware.xml:1256
 #, no-c-format
 msgid "The X.Org X Window System is only supported on the SGI Indy and the O2."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1249
+#: hardware.xml:1261
 #, no-c-format
 msgid "Most graphics options commonly found on Sparc-based machines are supported. X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards (glint driver). To use an Elite3D card with X.org you additionally need to install the <classname>afbinit</classname> package, and read the documentation included with it on how to activate the card."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1259
+#: hardware.xml:1271
 #, no-c-format
 msgid "It is not uncommon for a Sparc machine to have two graphics cards in a default configuration. In such a case there is a possibility that the Linux kernel will not direct its output to the card initially used by the firmware. The lack of output on the graphical console may then be mistaken for a hang (usually the last message seen on console is 'Booting Linux...'). One possible solution is to physically remove one of the video cards; another option is to disable one of the cards using a kernel boot parameter. Also, if graphical output is not required or desired, serial console may be used as an alternative. On some systems use of serial console can be activated automatically by disconnecting the keyboard before booting the system."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1281
+#: hardware.xml:1293
 #, no-c-format
 msgid "Network Connectivity Hardware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1282
+#: hardware.xml:1294
 #, no-c-format
 msgid "Almost any network interface card (NIC) supported by the &arch-kernel; kernel should also be supported by the installation system; drivers should normally be loaded automatically. <phrase arch=\"x86\">This includes most PCI/PCI-Express cards as well as PCMCIA/Express Cards on laptops.</phrase> <phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1292
+#: hardware.xml:1304
 #, no-c-format
 msgid "This includes a lot of generic PCI cards (for systems that have PCI) and the following NICs from Sun:"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1298
+#: hardware.xml:1310
 #, no-c-format
 msgid "Sun LANCE"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1303
+#: hardware.xml:1315
 #, no-c-format
 msgid "Sun Happy Meal"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1308
+#: hardware.xml:1320
 #, no-c-format
 msgid "Sun BigMAC"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1313
+#: hardware.xml:1325
 #, no-c-format
 msgid "Sun QuadEthernet"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1318
+#: hardware.xml:1330
 #, no-c-format
 msgid "MyriCOM Gigabit Ethernet"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1325
+#: hardware.xml:1337
 #, no-c-format
 msgid "The list of supported network devices is:"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1330
+#: hardware.xml:1342
 #, no-c-format
 msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1335
+#: hardware.xml:1347
 #, no-c-format
 msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1340
+#: hardware.xml:1352
 #, no-c-format
 msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1349
+#: hardware.xml:1361
 #, no-c-format
 msgid "On &arch-title;, most built-in Ethernet devices are supported and modules for additional PCI and USB devices are provided."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1354
+#: hardware.xml:1366
 #, no-c-format
 msgid "ISDN is supported, but not during the installation."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1361
+#: hardware.xml:1373
 #, no-c-format
 msgid "Wireless Network Cards"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1362
+#: hardware.xml:1374
 #, no-c-format
 msgid "Wireless networking is in general supported as well and a growing number of wireless adapters are supported by the official &arch-kernel; kernel, although many of them do require firmware to be loaded."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1369
+#: hardware.xml:1381
 #, no-c-format
 msgid "If firmware is needed, the installer will prompt you to load firmware. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware during the installation."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1374
+#: hardware.xml:1386
 #, no-c-format
 msgid "Wireless NICs that are not supported by the official &arch-kernel; kernel can generally be made to work under &debian-gnu;, but are not supported during the installation."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1379
+#: hardware.xml:1391
 #, no-c-format
 msgid "If there is a problem with wireless and there is no other NIC you can use during the installation, it is still possible to install &debian-gnu; using a full CD-ROM or DVD image. Select the option to not configure a network and install using only the packages available from the CD/DVD. You can then install the driver and firmware you need after the installation is completed (after the reboot) and configure your network manually."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1389
+#: hardware.xml:1401
 #, no-c-format
 msgid "In some cases the driver you need may not be available as a &debian; package. You will then have to look if there is source code available in the internet and compile the driver yourself. How to do this is outside the scope of this manual. <phrase arch=\"x86\">If no Linux driver is available, your last resort is to use the <classname>ndiswrapper</classname> package, which allows you to use a Windows driver.</phrase>"
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1403
+#: hardware.xml:1415
 #, no-c-format
 msgid "Known Issues for &arch-title;"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1404
+#: hardware.xml:1416
 #, no-c-format
 msgid "There are a couple of issues with specific network cards that are worth mentioning here."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1411
+#: hardware.xml:1423
 #, no-c-format
 msgid "Conflict between tulip and dfme drivers"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1413
+#: hardware.xml:1425
 #, no-c-format
 msgid "There are various PCI network cards that have the same PCI identification, but are supported by related, but different drivers. Some cards work with the <literal>tulip</literal> driver, others with the <literal>dfme</literal> driver. Because they have the same identification, the kernel cannot distinguish between them and it is not certain which driver will be loaded. If this happens to be the wrong one, the NIC may not work, or work badly."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1423
+#: hardware.xml:1435
 #, no-c-format
 msgid "This is a common problem on Netra systems with a Davicom (DEC-Tulip compatible) NIC. In that case the <literal>tulip</literal> driver is probably the correct one. You can prevent this issue by blacklisting the wrong driver module as described in <xref linkend=\"module-blacklist\"/>."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1431
+#: hardware.xml:1443
 #, no-c-format
 msgid "An alternative solution during the installation is to switch to a shell and unload the wrong driver module using <userinput>modprobe -r <replaceable>module</replaceable></userinput> (or both, if they are both loaded). After that you can load the correct module using <userinput>modprobe <replaceable>module</replaceable></userinput>. Note that the wrong module may then still be loaded when the system is rebooted."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1444
+#: hardware.xml:1456
 #, no-c-format
 msgid "Sun B100 blade"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1446
+#: hardware.xml:1458
 #, no-c-format
 msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1461
+#: hardware.xml:1473
 #, no-c-format
 msgid "Braille Displays"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1462
+#: hardware.xml:1474
 #, no-c-format
 msgid "Support for braille displays is determined by the underlying support found in <classname>brltty</classname>. Most displays work under <classname>brltty</classname>, connected via either a serial port, USB or bluetooth. Details on supported braille devices can be found on the <ulink url=\"&url-brltty;\"><classname>brltty</classname> website</ulink>. &debian-gnu; &release; ships with <classname>brltty</classname> version &brlttyver;."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1476
+#: hardware.xml:1488
 #, no-c-format
 msgid "Hardware Speech Synthesis"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1477
+#: hardware.xml:1489
 #, no-c-format
 msgid "Support for hardware speech synthesis devices is determined by the underlying support found in <classname>speakup</classname>. <classname>speakup</classname> only supports integrated boards and external devices connected to a serial port (no USB, serial-to-USB or PCI adapters are supported). Details on supported hardware speech synthesis devices can be found on the <ulink url=\"&url-speakup;\"><classname>speakup</classname> website</ulink>. &debian-gnu; &release; ships with <classname>speakup</classname> version &speakupver;."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1497
+#: hardware.xml:1509
 #, no-c-format
 msgid "Peripherals and Other Hardware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1498
+#: hardware.xml:1510
 #, no-c-format
 msgid "&arch-kernel; supports a large variety of hardware devices such as mice, printers, scanners, PCMCIA and USB devices. However, most of these devices are not required while installing the system."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1504
+#: hardware.xml:1516
 #, no-c-format
 msgid "USB hardware generally works fine. On some very old PC systems some USB keyboards may require additional configuration (see <xref linkend=\"hardware-issues\"/>). On modern PCs, USB keyboards and mice work without requiring any specific configuration."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1513
+#: hardware.xml:1525
 #, no-c-format
 msgid "Package installations from XPRAM and tape are not supported by this system. All packages that you want to install need to be available on a DASD or over the network using NFS, HTTP or FTP."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1519
+#: hardware.xml:1531
 #, no-c-format
 msgid "The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1531
+#: hardware.xml:1543
 #, no-c-format
 msgid "Devices Requiring Firmware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1532
+#: hardware.xml:1544
 #, no-c-format
 msgid "Besides the availability of a device driver, some hardware also requires so-called <firstterm>firmware</firstterm> or <firstterm>microcode</firstterm> to be loaded into the device before it can become operational. This is most common for network interface cards (especially wireless NICs), but for example some USB devices and even some hard disk controllers also require firmware. With many graphics cards, basic functionality is available without additional firmware, but the use of advanced features requires an appropriate firmware file to be installed in the system."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1543
+#: hardware.xml:1555
 #, no-c-format
 msgid "On many older devices which require firmware to work, the firmware file was permanently placed in an EEPROM/Flash chip on the device itself by the manufacturer. Nowadays most new devices do not have the firmware embedded this way anymore, so the firmware file must be uploaded into the device by the host operating system every time the system boots."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1551
+#: hardware.xml:1563
 #, no-c-format
 msgid "In most cases firmware is non-free according to the criteria used by the &debian-gnu; project and thus cannot be included in the main distribution or in the installation system. If the device driver itself is included in the distribution and if &debian-gnu; legally can distribute the firmware, it will often be available as a separate package from the non-free section of the archive."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1560
+#: hardware.xml:1572
 #, no-c-format
 msgid "However, this does not mean that such hardware cannot be used during an installation. Starting with &debian-gnu; 5.0, &d-i; supports loading firmware files or packages containing firmware from a removable medium, such as a USB stick. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware files or packages during the installation."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1569
+#: hardware.xml:1581
 #, no-c-format
 msgid "If the &d-i; prompts for a firmware file and you do not have this firmware file available or do not want to install a non-free firmware file on your system, you can try to proceed without loading the firmware. There are several cases where a driver prompts for additional firmware because it may be needed under certain circumstances, but the device does work without it on most systems (this e.g. happens with certain network cards using the tg3 driver)."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1586
+#: hardware.xml:1598
 #, no-c-format
 msgid "Purchasing Hardware Specifically for GNU/&arch-kernel;"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1588
+#: hardware.xml:1600
 #, no-c-format
 msgid "There are several vendors, who ship systems with &debian; or other distributions of GNU/Linux <ulink url=\"&url-pre-installed;\">pre-installed</ulink>. You might pay more for the privilege, but it does buy a level of peace of mind, since you can be sure that the hardware is well-supported by GNU/Linux."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1596
+#: hardware.xml:1608
 #, no-c-format
 msgid "If you do have to buy a machine with Windows bundled, carefully read the software license that comes with Windows; you may be able to reject the license and obtain a rebate from your vendor. Searching the Internet for <quote>windows refund</quote> may get you some useful information to help with that."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1604
+#: hardware.xml:1616
 #, no-c-format
 msgid "Whether or not you are purchasing a system with &arch-kernel; bundled, or even a used system, it is still important to check that your hardware is supported by the &arch-kernel; kernel. Check if your hardware is listed in the references found above. Let your salesperson (if any) know that you're shopping for a &arch-kernel; system. Support &arch-kernel;-friendly hardware vendors."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1615
+#: hardware.xml:1627
 #, no-c-format
 msgid "Avoid Proprietary or Closed Hardware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1616
+#: hardware.xml:1628
 #, no-c-format
 msgid "Some hardware manufacturers simply won't tell us how to write drivers for their hardware. Others won't allow us access to the documentation without a non-disclosure agreement that would prevent us from releasing the driver's source code, which is one of the central elements of free software. Since we haven't been granted access to usable documentation on these devices, they simply won't work under &arch-kernel;."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1626
+#: hardware.xml:1638
 #, no-c-format
 msgid "In many cases there are standards (or at least some de-facto standards) describing how an operating system and its device drivers communicate with a certain class of devices. All devices which comply to such a (de-facto-)standard can be used with a single generic device driver and no device-specific drivers are required. With some kinds of hardware (e.g. USB <quote>Human Interface Devices</quote>, i.e. keyboards, mice, etc., and USB mass storage devices like USB flash disks and memory card readers) this works very well and practically every device sold in the market is standards-compliant."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1638
+#: hardware.xml:1650
 #, no-c-format
 msgid "In other fields, among them e.g. printers, this is unfortunately not the case. While there are many printers which can be addressed via a small set of (de-facto-)standard control languages and therefore can be made to work without problems in any operating system, there are quite a few models which only understand proprietary control commands for which no usable documentation is available and therefore either cannot be used at all on free operating systems or can only be used with a vendor-supplied closed-source driver."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1649
+#: hardware.xml:1661
 #, no-c-format
 msgid "Even if there is a vendor-provided closed-source driver for such hardware when purchasing the device, the practical lifespan of the device is limited by driver availability. Nowadays product cycles have become short and it is not uncommon that a short time after a consumer device has ceased production, no driver updates get made available any more by the manufacturer. If the old closed-source driver does not work anymore after a system update, an otherwise perfectly working device becomes unusable due to lacking driver support and there is nothing that can be done in this case. You should therefore avoid buying closed hardware in the first place, regardless of the operating system you want to use it with."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1662
+#: hardware.xml:1674
 #, no-c-format
 msgid "You can help improve this situation by encouraging manufacturers of closed hardware to release the documentation and other resources necessary for us to provide free drivers for their hardware."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1677
+#: hardware.xml:1689
 #, no-c-format
 msgid "Installation Media"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1679
+#: hardware.xml:1691
 #, no-c-format
 msgid "This section will help you determine which different media types you can use to install &debian;. There is a whole chapter devoted to media, <xref linkend=\"install-methods\"/>, which lists the advantages and disadvantages of each media type. You may want to refer back to this page once you reach that section."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1689
+#: hardware.xml:1701
 #, no-c-format
 msgid "Floppies"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1690
+#: hardware.xml:1702
 #, no-c-format
 msgid "In some cases, you'll have to do your first boot from floppy disks. Generally, all you will need is a high-density (1440 kilobytes) 3.5 inch floppy drive."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1696
+#: hardware.xml:1708
 #, no-c-format
 msgid "For CHRP, floppy support is currently broken."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1703
+#: hardware.xml:1715
 #, no-c-format
 msgid "CD-ROM/DVD-ROM"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1705
+#: hardware.xml:1717
 #, no-c-format
 msgid "Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both CD-ROMs and DVD-ROMs, because both technologies are really the same from the operating system's point of view."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1711
+#: hardware.xml:1723
 #, no-c-format
 msgid "CD-ROM based installation is supported for most architectures."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1715
+#: hardware.xml:1727
 #, no-c-format
 msgid "On PCs SATA, IDE/ATAPI and SCSI CD-ROMs are supported."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1719
+#: hardware.xml:1731
 #, no-c-format
 msgid "USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1724
+#: hardware.xml:1736
 #, no-c-format
 msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1728
+#: hardware.xml:1740
 #, no-c-format
 msgid "On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. To start the install, simply choose the <quote>System installation</quote> entry in the firmware."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1742
+#: hardware.xml:1754
 #, no-c-format
 msgid "USB Memory Stick"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1744
+#: hardware.xml:1756
 #, no-c-format
 msgid "USB flash disks a.k.a. USB memory sticks have become a commonly used and cheap storage device. Most modern computer systems also allow booting the &d-i; from such a stick. Many modern computer systems, in particular netbooks and thin laptops, do not have a CD/DVD-ROM drive anymore at all and booting from USB media ist the standard way of installing a new operating system on them."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1756
+#: hardware.xml:1768
 #, no-c-format
 msgid "Network"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1758
+#: hardware.xml:1770
 #, no-c-format
 msgid "The network can be used during the installation to retrieve files needed for the installation. Whether the network is used or not depends on the installation method you choose and your answers to certain questions that will be asked during the installation. The installation system supports most types of network connections (including PPPoE, but not ISDN or PPP), via either HTTP or FTP. After the installation is completed, you can also configure your system to use ISDN and PPP."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1768
+#: hardware.xml:1780
 #, no-c-format
 msgid "You can also <emphasis>boot</emphasis> the installation system over the network without needing any local media like CDs/DVDs or USB sticks. If you already have a netboot-infrastructure available (i.e. you are already running DHCP and TFTP services in your network), this allows an easy and fast deployment of a large number of machines. Setting up the necessary infrastructure requires a certain level of technical experience, so this is not recommended for novice users. <phrase arch=\"mips;mipsel\">This is the preferred installation technique for &arch-title;.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1781
+#: hardware.xml:1793
 #, no-c-format
 msgid "Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1790
+#: hardware.xml:1802
 #, no-c-format
 msgid "Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1792
+#: hardware.xml:1804
 #, no-c-format
 msgid "Booting the installation system directly from a hard disk is another option for many architectures. This will require some other operating system to load the installer onto the hard disk. This method is only recommended for special cases when no other installation method is available."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1799
+#: hardware.xml:1811
 #, no-c-format
 msgid "Although the &arch-title; does not allow booting from SunOS (Solaris), you can install from a SunOS partition (UFS slices)."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1808
+#: hardware.xml:1820
 #, no-c-format
 msgid "Un*x or GNU system"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1810
+#: hardware.xml:1822
 #, no-c-format
 msgid "If you are running another Unix-like system, you could use it to install &debian-gnu; without using the &d-i; described in the rest of this manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the <xref linkend=\"linux-upgrade\"/>. This installation method is only recommended for advanced users when no other installation method is available."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1823
+#: hardware.xml:1835
 #, no-c-format
 msgid "Supported Storage Systems"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1825
+#: hardware.xml:1837
 #, no-c-format
 msgid "The &debian; installer contains a kernel which is built to maximize the number of systems it runs on."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1829
+#: hardware.xml:1841
 #, no-c-format
 msgid "Generally, the &debian; installation system includes support for IDE (also known as PATA) drives, SATA and SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1846
+#: hardware.xml:1858
 #, no-c-format
 msgid "Any storage system supported by the Linux kernel is also supported by the boot system. The following SCSI drivers are supported in the default kernel: <itemizedlist> <listitem><para> Sparc ESP </para></listitem> <listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></listitem> </itemizedlist> IDE systems (such as the UltraSPARC 5) are also supported. See <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors FAQ</ulink> for more information on SPARC hardware supported by the Linux kernel."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1879
+#: hardware.xml:1891
 #, no-c-format
 msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support floppies on CHRP systems at all."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1885
+#: hardware.xml:1897
 #, no-c-format
 msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support the floppy drive."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1891
+#: hardware.xml:1903
 #, no-c-format
 msgid "Any storage system supported by the Linux kernel is also supported by the boot system."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1896
+#: hardware.xml:1908
 #, no-c-format
 msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This means that FBA and ECKD DASDs are supported with the old Linux disk layout (ldl) and the new common S/390 disk layout (cdl)."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1913
+#: hardware.xml:1925
 #, no-c-format
 msgid "Memory and Disk Space Requirements"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1915
+#: hardware.xml:1927
 #, no-c-format
 msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space to perform a normal installation. Note that these are fairly minimal numbers. For more realistic figures, see <xref linkend=\"minimum-hardware-reqts\"/>."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1922
+#: hardware.xml:1934
 #, no-c-format
 msgid "Installation on systems with less memory<footnote condition=\"gtk\"> <para> Installation images that support the graphical installer require more memory than images that support only the textual installer and should not be used on systems with less than &minimum-memory; of memory. If there is a choice between booting the regular and the graphical installer, the former should be selected. </para> </footnote> or disk space available may be possible but is only advised for experienced users."
 msgstr ""
diff --git a/po/pot/install-methods.pot b/po/pot/install-methods.pot
index 1d1ad3d43..79909c870 100644
--- a/po/pot/install-methods.pot
+++ b/po/pot/install-methods.pot
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2013-04-16 19:15+0000\n"
+"POT-Creation-Date: 2013-05-22 19:06+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"
@@ -41,7 +41,7 @@ msgstr ""
 #. Tag: para
 #: install-methods.xml:38
 #, no-c-format
-msgid "If your machine doesn't support CD booting<phrase arch=\"x86\"> (only relevant on very old PC systems)</phrase>, but you do have a CD set, you can use an alternative strategy such as <phrase condition=\"supports-floppy-boot\">floppy disk,</phrase> <phrase arch=\"s390\">tape, emulated tape,</phrase> <phrase condition=\"bootable-disk\">hard disk,</phrase> <phrase condition=\"bootable-usb\">usb stick,</phrase> <phrase condition=\"supports-tftp\">net boot,</phrase> or manually loading the kernel from the CD to initially boot the system installer. The files you need for booting by another means are also on the CD; the &debian; network archive and CD folder organization are identical. So when archive file paths are given below for particular files you need for booting, look for those files in the same directories and subdirectories on your CD."
+msgid "If your machine doesn't support CD booting<phrase arch=\"x86\"> (only relevant on very old PC systems)</phrase>, but you do have a CD set, you can use an alternative strategy such as <phrase condition=\"supports-floppy-boot\">floppy disk,</phrase> <phrase arch=\"s390\">VM reader,</phrase> <phrase condition=\"bootable-disk\">hard disk,</phrase> <phrase condition=\"bootable-usb\">usb stick,</phrase> <phrase condition=\"supports-tftp\">net boot,</phrase> or manually loading the kernel from the CD to initially boot the system installer. The files you need for booting by another means are also on the CD; the &debian; network archive and CD folder organization are identical. So when archive file paths are given below for particular files you need for booting, look for those files in the same directories and subdirectories on your CD."
 msgstr ""
 
 #. Tag: para
@@ -53,7 +53,7 @@ msgstr ""
 #. Tag: para
 #: install-methods.xml:66
 #, no-c-format
-msgid "If you don't have a CD set, then you will need to download the installer system files and place them on the <phrase arch=\"s390\">installation tape</phrase> <phrase condition=\"supports-floppy-boot\">floppy disk or</phrase> <phrase condition=\"bootable-disk\">hard disk or</phrase> <phrase condition=\"bootable-usb\">usb stick or</phrase> <phrase condition=\"supports-tftp\">a connected computer</phrase> so they can be used to boot the installer."
+msgid "If you don't have a CD set, then you will need to download the installer system files and place them on the <phrase arch=\"s390\">VM minidisk</phrase> <phrase condition=\"supports-floppy-boot\">floppy disk or</phrase> <phrase condition=\"bootable-disk\">hard disk or</phrase> <phrase condition=\"bootable-usb\">usb stick or</phrase> <phrase condition=\"supports-tftp\">a connected computer</phrase> so they can be used to boot the installer."
 msgstr ""
 
 #. Tag: title
@@ -173,65 +173,53 @@ msgstr ""
 #. Tag: title
 #: install-methods.xml:244
 #, no-c-format
-msgid "Creating an IPL tape"
-msgstr ""
-
-#. Tag: para
-#: install-methods.xml:246
-#, no-c-format
-msgid "If you can't boot (IPL) from the CD-ROM and you are not using VM you need to create an IPL tape first. This is described in section 3.4.3 in the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> Redbook. The files you need to write to the tape are (in this order): <filename>kernel.debian</filename>, <filename>parmfile.debian</filename> and <filename>initrd.debian</filename>. The files can be downloaded from the <filename>tape</filename> sub-directory, see <xref linkend=\"where-files\"/>."
-msgstr ""
-
-#. Tag: title
-#: install-methods.xml:270
-#, no-c-format
 msgid "Creating Floppies from Disk Images"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:271
+#: install-methods.xml:245
 #, no-c-format
 msgid "Bootable floppy disks are generally used as a last resort to boot the installer on hardware that cannot boot from CD or by other means."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:276
+#: install-methods.xml:250
 #, no-c-format
 msgid "Booting the installer from floppy disk reportedly fails on Mac USB floppy drives."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:281
+#: install-methods.xml:255
 #, no-c-format
 msgid "Disk images are files containing the complete contents of a floppy disk in <emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</filename>, cannot simply be copied to floppy drives. A special program is used to write the image files to floppy disk in <emphasis>raw</emphasis> mode. This is required because these images are raw representations of the disk; it is required to do a <emphasis>sector copy</emphasis> of the data from the file onto the floppy."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:292
+#: install-methods.xml:266
 #, no-c-format
 msgid "There are different techniques for creating floppies from disk images. This section describes how to create floppies from disk images on different platforms."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:298
+#: install-methods.xml:272
 #, no-c-format
 msgid "Before you can create the floppies, you will first need to download them from one of the &debian; mirrors, as explained in <xref linkend=\"downloading-files\"/>. <phrase arch=\"i386\">If you already have an installation CD-ROM or DVD, the floppy images may also be included on the CD/DVD.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:306
+#: install-methods.xml:280
 #, no-c-format
 msgid "No matter which method you use to create your floppies, you should remember to flip the write-protect tab on the floppies once you have written them, to ensure they are not damaged unintentionally."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:314
+#: install-methods.xml:288
 #, no-c-format
 msgid "Writing Disk Images From a Linux or Unix System"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:315
+#: install-methods.xml:289
 #, no-c-format
 msgid ""
       "To write the floppy disk image files to the floppy disks, you will probably need root access to the system. Place a good, blank floppy in the floppy drive. Next, use the command <informalexample><screen>\n"
@@ -240,187 +228,187 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:336
+#: install-methods.xml:310
 #, no-c-format
 msgid "Some systems attempt to automatically mount a floppy disk when you place it in the drive. You might have to disable this feature before the workstation will allow you to write a floppy in <emphasis>raw mode</emphasis>. Unfortunately, how to accomplish this will vary based on your operating system. <phrase arch=\"sparc\"> On Solaris, you can work around volume management to get raw access to the floppy. First, make sure that the floppy is auto-mounted (using <command>volcheck</command> or the equivalent command in the file manager). Then use a <command>dd</command> command of the form given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/rdsk/<replaceable>floppy_name</replaceable></filename>, where <replaceable>floppy_name</replaceable> is the name the floppy disk was given when it was formatted (unnamed floppies default to the name <filename>unnamed_floppy</filename>). On other systems, ask your system administrator. </phrase>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:357
+#: install-methods.xml:331
 #, no-c-format
 msgid "If writing a floppy on powerpc Linux, you will need to eject it. The <command>eject</command> program handles this nicely; you might need to install it."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:375
+#: install-methods.xml:349
 #, no-c-format
 msgid "Writing Disk Images From DOS, Windows, or OS/2"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:377
+#: install-methods.xml:351
 #, no-c-format
 msgid "If you have access to an i386 or amd64 machine, you can use one of the following programs to copy images to floppies."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:382
+#: install-methods.xml:356
 #, no-c-format
 msgid "The <command>rawrite1</command> and <command>rawrite2</command> programs can be used under MS-DOS. To use these programs, first make sure that you are booted into DOS. Trying to use these programs from within a DOS box in Windows, or double-clicking on these programs from the Windows Explorer is <emphasis>not</emphasis> expected to work."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:390
+#: install-methods.xml:364
 #, no-c-format
 msgid "The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, ME, XP and probably later versions. To use it you will need to unpack diskio.dll in the same directory."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:396
+#: install-methods.xml:370
 #, no-c-format
 msgid "These tools can be found on the Official &debian; CD-ROMs under the <filename>/tools</filename> directory."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:409
+#: install-methods.xml:383
 #, no-c-format
 msgid "Writing Disk Images From MacOS"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:410
+#: install-methods.xml:384
 #, no-c-format
 msgid "An AppleScript, <application>Make &debian; Floppy</application>, is available for burning floppies from the provided disk image files. It can be downloaded from <ulink url=\"ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/debian-imac/MakeDebianFloppy.sit\"></ulink>. To use it, just unstuff it on your desktop, and then drag any floppy image file to it. You must have Applescript installed and enabled in your extensions manager. Disk Copy will ask you to confirm that you wish to erase the floppy and proceed to write the file image to it."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:421
+#: install-methods.xml:395
 #, no-c-format
 msgid "You can also use the MacOS utility <command>Disk Copy</command> directly, or the freeware utility <command>suntar</command>. The <filename>root.bin</filename> file is an example of a floppy image. Use one of the following methods to create a floppy from the floppy image with these utilities."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:432
+#: install-methods.xml:406
 #, no-c-format
 msgid "Writing Disk Images with <command>Disk Copy</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:433
+#: install-methods.xml:407
 #, no-c-format
 msgid "If you are creating the floppy image from files which were originally on the official &debian-gnu; CD, then the Type and Creator are already set correctly. The following <command>Creator-Changer</command> steps are only necessary if you downloaded the image files from a &debian; mirror."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:442
+#: install-methods.xml:416
 #, no-c-format
 msgid "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> and use it to open the <filename>root.bin</filename> file."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:449
+#: install-methods.xml:423
 #, no-c-format
 msgid "Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type to <userinput>DDim</userinput> (binary floppy image). The case is sensitive for these fields."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:456
+#: install-methods.xml:430
 #, no-c-format
 msgid "<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</userinput> to display the Finder information about the floppy image, and <quote>X</quote> the <userinput>File Locked</userinput> check box so that MacOS will be unable to remove the boot blocks if the image is accidentally mounted."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:465
+#: install-methods.xml:439
 #, no-c-format
 msgid "Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it will very likely be there already, otherwise try <ulink url=\"&url-powerpc-diskcopy;\"></ulink>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:472
+#: install-methods.xml:446
 #, no-c-format
 msgid "Run <command>Disk Copy</command>, and select <menuchoice> <guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> </menuchoice>, then select the <emphasis>locked</emphasis> image file from the resulting dialog. It will ask you to insert a floppy, then ask if you really want to erase it. When done it should eject the floppy."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:487
+#: install-methods.xml:461
 #, no-c-format
 msgid "Writing Disk Images with <command>suntar</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:491
+#: install-methods.xml:465
 #, no-c-format
 msgid "Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </ulink>. Start the <command>suntar</command> program and select <quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> menu."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:499
+#: install-methods.xml:473
 #, no-c-format
 msgid "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:505
+#: install-methods.xml:479
 #, no-c-format
 msgid "Select the <filename>root.bin</filename> file in the file-opening dialog."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:510
+#: install-methods.xml:484
 #, no-c-format
 msgid "After the floppy has been created successfully, select <menuchoice> <guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. If there are any errors writing the floppy, simply toss that floppy and try another."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:518
+#: install-methods.xml:492
 #, no-c-format
 msgid "Before using the floppy you created, <emphasis>set the write protect tab</emphasis>! Otherwise if you accidentally mount it in MacOS, MacOS will helpfully ruin it."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:537
+#: install-methods.xml:511
 #, no-c-format
 msgid "Preparing Files for USB Memory Stick Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:539
+#: install-methods.xml:513
 #, no-c-format
 msgid "To prepare the USB stick, you will need a system where GNU/Linux is already running and where USB is supported. With current GNU/Linux systems the USB stick should be automatically recognized when you insert it. If it is not you should check that the usb-storage kernel module is loaded. When the USB stick is inserted, it will be mapped to a device named <filename>/dev/sdX</filename>, where the <quote>X</quote> is a letter in the range a-z. You should be able to see to which device the USB stick was mapped by running the command <command>dmesg</command> after inserting it. To write to your stick, you may have to turn off its write protection switch."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:552
+#: install-methods.xml:526
 #, no-c-format
 msgid "The procedures described in this section will destroy anything already on the device! Make very sure that you use the correct device name for your USB stick. If you use the wrong device the result could be that all information on for example a hard disk could be lost."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:562
+#: install-methods.xml:536
 #, no-c-format
 msgid "Preparing a USB stick using a hybrid CD or DVD image"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:563
+#: install-methods.xml:537
 #, no-c-format
 msgid "Debian CD and DVD images can now be written directly a USB stick, which is a very easy way to make a bootable USB stick. Simply choose a CD or DVD image that will fit on your USB stick. See <xref linkend=\"official-cdrom\"/> to get a CD or DVD image."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:570
+#: install-methods.xml:544
 #, no-c-format
 msgid "Alternatively, for very small USB sticks, only a few megabytes in size, you can download the <filename>mini.iso</filename> image from the <filename>netboot</filename> directory (at the location mentioned in <xref linkend=\"where-files\"/>)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:577
+#: install-methods.xml:551
 #, no-c-format
 msgid "The CD or DVD image you choose should be written directly to the USB stick, overwriting its current contents. For example, when using an existing GNU/Linux system, the CD or DVD image file can be written to a USB stick as follows, after having made sure that the stick is unmounted:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:584
+#: install-methods.xml:558
 #, no-c-format
 msgid ""
       "<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/<replaceable>sdX</replaceable></userinput>\n"
@@ -428,25 +416,25 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:586
+#: install-methods.xml:560
 #, no-c-format
 msgid "Simply writing the CD or DVD image to USB like this should work fine for most users. The other options below are more complex, mainly for people with specialised needs."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:594
+#: install-methods.xml:568
 #, no-c-format
 msgid "The hybrid image on the stick does not occupy all the storage space, so it may be worth considering using the free space to hold firmware files or packages or any other files of your choice. This could be useful if you have only one stick or just want to keep everything you need on one device."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:602
+#: install-methods.xml:576
 #, no-c-format
 msgid "Create a second, FAT partition on the stick, mount the partition and copy or unpack the firmware onto it. For example:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:607
+#: install-methods.xml:581
 #, no-c-format
 msgid ""
       "# mount /dev/<replaceable>sdX2</replaceable> /mnt\n"
@@ -457,91 +445,91 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:609
+#: install-methods.xml:583
 #, no-c-format
 msgid "You might have written the <filename>mini.iso</filename> to the USB stick. In this case the second partition doesn't have to be created as, very nicely, it will already be present. Unplugging and replugging the USB stick should make the two partitions visible."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:623
+#: install-methods.xml:597
 #, no-c-format
 msgid "Manually copying files to the USB stick"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:624
+#: install-methods.xml:598
 #, no-c-format
 msgid "An alternative way to set up your USB stick is to manually copy the installer files, and also a CD image to it. Note that the USB stick should be at least 1 GB in size (smaller setups are possible if you follow <xref linkend=\"usb-copy-flexible\"/>)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:631
+#: install-methods.xml:605
 #, no-c-format
 msgid "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which contains all the installer files (including the kernel) <phrase arch=\"x86\">as well as <classname>syslinux</classname> and its configuration file</phrase> <phrase arch=\"powerpc\">as well as <classname>yaboot</classname> and its configuration file</phrase>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:640
+#: install-methods.xml:614
 #, no-c-format
 msgid "Note that, although convenient, this method does have one major disadvantage: the logical size of the device will be limited to 1 GB, even if the capacity of the USB stick is larger. You will need to repartition the USB stick and create new file systems to get its full capacity back if you ever want to use it for some different purpose."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:648
+#: install-methods.xml:622
 #, no-c-format
 msgid "To use this image simply extract it directly to your USB stick:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:652
+#: install-methods.xml:626
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX</replaceable>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:654
+#: install-methods.xml:628
 #, no-c-format
 msgid "Create a partition of type \"Apple_Bootstrap\" on your USB stick using <command>mac-fdisk</command>'s <userinput>C</userinput> command and extract the image directly to that:"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:660
+#: install-methods.xml:634
 #, no-c-format
 msgid "# zcat boot.img.gz &gt; /dev/<replaceable>sdX2</replaceable>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:662
+#: install-methods.xml:636
 #, no-c-format
 msgid "After that, mount the USB memory stick <phrase arch=\"x86\">(<userinput>mount /dev/<replaceable>sdX</replaceable> /mnt</userinput>),</phrase> <phrase arch=\"powerpc\">(<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>),</phrase> which will now have <phrase arch=\"x86\">a FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS filesystem</phrase> on it, and copy a &debian; ISO image (netinst or full CD) to it. Unmount the stick (<userinput>umount /mnt</userinput>) and you are done."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:679
+#: install-methods.xml:653
 #, no-c-format
 msgid "Manually copying files to the USB stick &mdash; the flexible way"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:680
+#: install-methods.xml:654
 #, no-c-format
 msgid "If you like more flexibility or just want to know what's going on, you should use the following method to put the files on your stick. One advantage of using this method is that &mdash; if the capacity of your USB stick is large enough &mdash; you have the option of copying a full CD ISO image to it."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:695 install-methods.xml:817
+#: install-methods.xml:669 install-methods.xml:791
 #, no-c-format
 msgid "Partitioning the USB stick"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:696
+#: install-methods.xml:670
 #, no-c-format
 msgid "We will show how to set up the memory stick to use the first partition, instead of the entire device."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:701
+#: install-methods.xml:675
 #, no-c-format
 msgid ""
       "Since most USB sticks come pre-configured with a single FAT16 partition, you probably won't have to repartition or reformat the stick. If you have to do that anyway, use <command>cfdisk</command> or any other partitioning tool to create a FAT16 partition<footnote> <para> Don't forget to set the <quote>bootable</quote> bootable flag. </para> </footnote>, install an MBR using: <informalexample><screen>\n"
@@ -552,13 +540,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:725
+#: install-methods.xml:699
 #, no-c-format
 msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. Although any boot loader (e.g. <classname>lilo</classname>) should work, it's convenient to use <classname>syslinux</classname>, since it uses a FAT16 partition and can be reconfigured by just editing a text file. Any operating system which supports the FAT file system can be used to make changes to the configuration of the boot loader."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:735
+#: install-methods.xml:709
 #, no-c-format
 msgid ""
       "To put <classname>syslinux</classname> on the FAT16 partition on your USB stick, install the <classname>syslinux</classname> and <classname>mtools</classname> packages on your system, and do: <informalexample><screen>\n"
@@ -567,19 +555,19 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:752 install-methods.xml:864
+#: install-methods.xml:726 install-methods.xml:838
 #, no-c-format
 msgid "Adding the installer image"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:753
+#: install-methods.xml:727
 #, no-c-format
 msgid "Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /mnt</userinput>) and copy the following installer image files to the stick: <itemizedlist> <listitem><para> <filename>vmlinuz</filename> or <filename>linux</filename> (kernel binary) </para></listitem> <listitem><para> <filename>initrd.gz</filename> (initial ramdisk image) </para></listitem> </itemizedlist> You can choose between either the regular version or the graphical version of the installer. The latter can be found in the <filename>gtk</filename> subdirectory. If you want to rename the files, please note that <classname>syslinux</classname> can only process DOS (8.3) file names."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:777
+#: install-methods.xml:751
 #, no-c-format
 msgid ""
       "Next you should create a <filename>syslinux.cfg</filename> configuration file, which at a bare minimum should contain the following two lines (change the name of the kernel binary to <quote><filename>linux</filename></quote> if you used a <filename>netboot</filename> image): <informalexample><screen>\n"
@@ -589,19 +577,19 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:789
+#: install-methods.xml:763
 #, no-c-format
 msgid "To enable the boot prompt to permit further parameter appending, add a <userinput>prompt 1</userinput> line."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:794 install-methods.xml:904
+#: install-methods.xml:768 install-methods.xml:878
 #, no-c-format
 msgid "If you used an <filename>hd-media</filename> image, you should now copy the ISO file of a &debian; ISO image<footnote> <para> You can use either a netinst or a full CD image (see <xref linkend=\"official-cdrom\"/>). Be sure to select one that fits. Note that the <quote>netboot <filename>mini.iso</filename></quote> image is not usable for this purpose. </para> </footnote> onto the stick. When you are done, unmount the USB memory stick (<userinput>umount /mnt</userinput>)."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:818
+#: install-methods.xml:792
 #, no-c-format
 msgid ""
       "Most USB sticks do not come pre-configured in such a way that Open Firmware can boot from them, so you will need to repartition the stick. On Mac systems, run <userinput>mac-fdisk /dev/<replaceable>sdX</replaceable></userinput>, initialise a new partition map using the <userinput>i</userinput> command, and create a new partition of type Apple_Bootstrap using the <userinput>C</userinput> command. (Note that the first \"partition\" will always be the partition map itself.) Then type <informalexample><screen>\n"
@@ -610,13 +598,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:835
+#: install-methods.xml:809
 #, no-c-format
 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 ""
 
 #. Tag: para
-#: install-methods.xml:844
+#: install-methods.xml:818
 #, no-c-format
 msgid ""
       "The normal <command>ybin</command> tool that comes with <command>yaboot</command> does not yet understand USB storage devices, so you will have to install <command>yaboot</command> by hand using the <classname>hfsutils</classname> tools. Type <informalexample><screen>\n"
@@ -629,37 +617,37 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:865
+#: install-methods.xml:839
 #, no-c-format
 msgid "Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>) and copy the following installer image files to the stick:"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:872
+#: install-methods.xml:846
 #, no-c-format
 msgid "<filename>vmlinux</filename> (kernel binary)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:877
+#: install-methods.xml:851
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (initial ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:882
+#: install-methods.xml:856
 #, no-c-format
 msgid "<filename>yaboot.conf</filename> (yaboot configuration file)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:887
+#: install-methods.xml:861
 #, no-c-format
 msgid "<filename>boot.msg</filename> (optional boot message)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:894
+#: install-methods.xml:868
 #, no-c-format
 msgid ""
       "The <filename>yaboot.conf</filename> configuration file should contain the following lines: <informalexample><screen>\n"
@@ -677,259 +665,259 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:932
+#: install-methods.xml:906
 #, no-c-format
 msgid "Preparing Files for Hard Disk Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:933
+#: install-methods.xml:907
 #, no-c-format
 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 ""
 
 #. Tag: para
-#: install-methods.xml:939
+#: install-methods.xml:913
 #, no-c-format
 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 ""
 
 #. Tag: para
-#: install-methods.xml:946
+#: install-methods.xml:920
 #, no-c-format
 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 ""
 
 #. Tag: para
-#: install-methods.xml:957
+#: install-methods.xml:931
 #, no-c-format
 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 ""
 
 #. Tag: title
-#: install-methods.xml:966
+#: install-methods.xml:940
 #, no-c-format
 msgid "Hard disk installer booting from Linux using <command>LILO</command> or <command>GRUB</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:968
+#: install-methods.xml:942
 #, no-c-format
 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 ""
 
 #. Tag: para
-#: install-methods.xml:974
+#: install-methods.xml:948
 #, no-c-format
 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 ""
 
 #. Tag: para
-#: install-methods.xml:980
+#: install-methods.xml:954
 #, no-c-format
 msgid "Copy the following files from the &debian; archives to a convenient location on your hard drive (note that LILO can not boot from files on an NTFS file system), for instance to <filename>/boot/newinstall/</filename>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:988
+#: install-methods.xml:962
 #, no-c-format
 msgid "<filename>vmlinuz</filename> (kernel binary)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:993
+#: install-methods.xml:967
 #, no-c-format
 msgid "<filename>initrd.gz</filename> (ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1000
+#: install-methods.xml:974
 #, no-c-format
 msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1010
+#: install-methods.xml:984
 #, no-c-format
 msgid "Hard disk installer booting from DOS using <command>loadlin</command>"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1011
+#: install-methods.xml:985
 #, no-c-format
 msgid "This section explains how to prepare your hard drive for booting the installer from DOS using <command>loadlin</command>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1016
+#: install-methods.xml:990
 #, no-c-format
 msgid "Copy the following directories from a &debian; CD image to <filename>c:\\</filename>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1021
+#: install-methods.xml:995
 #, no-c-format
 msgid "<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1026
+#: install-methods.xml:1000
 #, no-c-format
 msgid "<filename>/tools</filename> (loadlin tool)"
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1039
+#: install-methods.xml:1013
 #, no-c-format
 msgid "Hard Disk Installer Booting for OldWorld Macs"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1040
+#: install-methods.xml:1014
 #, no-c-format
 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 ""
 
 #. Tag: para
-#: install-methods.xml:1053
+#: install-methods.xml:1027
 #, no-c-format
 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 ""
 
 #. Tag: title
-#: install-methods.xml:1073
+#: install-methods.xml:1047
 #, no-c-format
 msgid "Hard Disk Installer Booting for NewWorld Macs"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1074
+#: install-methods.xml:1048
 #, no-c-format
 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 ""
 
 #. Tag: para
-#: install-methods.xml:1085
+#: install-methods.xml:1059
 #, no-c-format
 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 ""
 
 #. Tag: filename
-#: install-methods.xml:1095 install-methods.xml:1421
+#: install-methods.xml:1069 install-methods.xml:1395
 #, no-c-format
 msgid "vmlinux"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1100 install-methods.xml:1426
+#: install-methods.xml:1074 install-methods.xml:1400
 #, no-c-format
 msgid "initrd.gz"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1105 install-methods.xml:1431
+#: install-methods.xml:1079 install-methods.xml:1405
 #, no-c-format
 msgid "yaboot"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1110 install-methods.xml:1436
+#: install-methods.xml:1084 install-methods.xml:1410
 #, no-c-format
 msgid "yaboot.conf"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1115
+#: install-methods.xml:1089
 #, no-c-format
 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 <command>L</command> 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 ""
 
 #. Tag: para
-#: install-methods.xml:1123
+#: install-methods.xml:1097
 #, no-c-format
 msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1136
+#: install-methods.xml:1110
 #, no-c-format
 msgid "Preparing Files for TFTP Net Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1137
+#: install-methods.xml:1111
 #, no-c-format
 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 ""
 
 #. Tag: para
-#: install-methods.xml:1145
+#: install-methods.xml:1119
 #, no-c-format
 msgid "You need to set up a TFTP server, and for many machines a DHCP server<phrase condition=\"supports-rarp\">, or RARP server</phrase><phrase condition=\"supports-bootp\">, or BOOTP server</phrase>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1152
+#: install-methods.xml:1126
 #, no-c-format
 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> The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1166
+#: install-methods.xml:1140
 #, no-c-format
 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 ""
 
 #. Tag: para
-#: install-methods.xml:1172
+#: install-methods.xml:1146
 #, no-c-format
 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 ""
 
 #. Tag: para
-#: install-methods.xml:1177
+#: install-methods.xml:1151
 #, no-c-format
 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 ""
 
 #. Tag: para
-#: install-methods.xml:1185
+#: install-methods.xml:1159
 #, no-c-format
 msgid "For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. It's written by the same author as the <classname>syslinux</classname> bootloader and is therefore least likely to cause issues. A good alternative is <classname>atftpd</classname>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1201
+#: install-methods.xml:1175
 #, no-c-format
 msgid "Setting up RARP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1202
+#: install-methods.xml:1176
 #, no-c-format
 msgid "To set up 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>ip addr show dev eth0</userinput>."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1214
+#: install-methods.xml:1188
 #, no-c-format
 msgid "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, you use the <command>rarpd</command> program. 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. Issue the command (as root): <userinput>/usr/sbin/rarpd -a</userinput> on most Linux systems and SunOS 5 (Solaris 2), <userinput>/usr/sbin/in.rarpd -a</userinput> on some other Linux systems, or <userinput>/usr/etc/rarpd -a</userinput> in SunOS 4 (Solaris 1)."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1235
+#: install-methods.xml:1209
 #, no-c-format
 msgid "Setting up a DHCP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1236
+#: install-methods.xml:1210
 #, no-c-format
-msgid "One free software DHCP server is ISC <command>dhcpd</command>. For &debian-gnu;, the <classname>dhcp3-server</classname> package is recommended. Here is a sample configuration file for it (see <filename>/etc/dhcp3/dhcpd.conf</filename>):"
+msgid "One free software DHCP server is ISC <command>dhcpd</command>. For &debian-gnu;, the <classname>isc-dhcp-server</classname> package is recommended. Here is a sample configuration file for it (see <filename>/etc/dhcp/dhcpd.conf</filename>):"
 msgstr ""
 
 #. Tag: screen
-#: install-methods.xml:1243
+#: install-methods.xml:1217
 #, no-c-format
 msgid ""
       "option domain-name \"example.com\";\n"
@@ -954,25 +942,25 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1245
+#: install-methods.xml:1219
 #, no-c-format
 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 ""
 
 #. Tag: para
-#: install-methods.xml:1255
+#: install-methods.xml:1229
 #, no-c-format
-msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/dhcp3-server restart</userinput>."
+msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/isc-dhcp-server restart</userinput>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1263
+#: install-methods.xml:1237
 #, no-c-format
 msgid "Enabling PXE Booting in the DHCP configuration"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1264
+#: install-methods.xml:1238
 #, no-c-format
 msgid ""
       "Here is another example for a <filename>dhcp.conf</filename> using the Pre-boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n"
@@ -1007,19 +995,19 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1284
+#: install-methods.xml:1258
 #, no-c-format
 msgid "Setting up a BOOTP server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1285
+#: install-methods.xml:1259
 #, no-c-format
-msgid "There are two BOOTP servers available for GNU/Linux. The first is CMU <command>bootpd</command>. The other is actually a DHCP server: ISC <command>dhcpd</command>. In &debian-gnu; these are contained in the <classname>bootp</classname> and <classname>dhcp3-server</classname> packages respectively."
+msgid "There are two BOOTP servers available for GNU/Linux. The first is CMU <command>bootpd</command>. The other is actually a DHCP server: ISC <command>dhcpd</command>. In &debian-gnu; these are contained in the <classname>bootp</classname> and <classname>isc-dhcp-server</classname> packages respectively."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1293
+#: install-methods.xml:1267
 #, no-c-format
 msgid ""
       "To use CMU <command>bootpd</command>, you must first uncomment (or add) the relevant line in <filename>/etc/inetd.conf</filename>. On &debian-gnu;, you can run <userinput>update-inetd --enable bootps</userinput>, then <userinput>/etc/init.d/inetd reload</userinput> to do so. Just in case your BOOTP server does not run &debian;, the line in question should look like: <informalexample><screen>\n"
@@ -1036,43 +1024,43 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1326
+#: install-methods.xml:1300
 #, no-c-format
-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 in <filename>/etc/dhcp3/dhcpd.conf</filename>, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcp3-server restart</userinput>."
+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 in <filename>/etc/dhcp/dhcpd.conf</filename>, and restart <command>dhcpd</command> with <userinput>/etc/init.d/isc-dhcp-server restart</userinput>."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1345
+#: install-methods.xml:1319
 #, no-c-format
 msgid "Enabling the TFTP Server"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1346
+#: install-methods.xml:1320
 #, no-c-format
 msgid "To get the TFTP server ready to go, you should first make sure that <command>tftpd</command> is enabled."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1351
+#: install-methods.xml:1325
 #, no-c-format
 msgid "In the case of <classname>tftpd-hpa</classname> there are two ways the service can be run. It can be started on demand by the system's <classname>inetd</classname> daemon, or it can be set up to run as an independent daemon. Which of these methods is used is selected when the package is installed and can be changed by reconfiguring the package."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1360
+#: install-methods.xml:1334
 #, no-c-format
 msgid "Historically, TFTP servers used <filename>/tftpboot</filename> as directory to serve images from. However, &debian-gnu; packages may use other directories to comply with the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink>. For example, <classname>tftpd-hpa</classname> by default uses <filename>/srv/tftp</filename>. You may have to adjust the configuration examples in this section accordingly."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1370
+#: install-methods.xml:1344
 #, no-c-format
 msgid "All <command>in.tftpd</command> alternatives available in &debian; should log TFTP requests to the system logs by default. Some of them support a <userinput>-v</userinput> argument to increase verbosity. It is recommended to check these log messages in case of boot problems as they are a good starting point for diagnosing the cause of errors."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1378
+#: install-methods.xml:1352
 #, no-c-format
 msgid ""
       "If you intend to install &debian; on an SGI machine and your TFTP server is a GNU/Linux box running Linux 2.4, you'll need to set the following on your server: <informalexample><screen>\n"
@@ -1083,49 +1071,49 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1400
+#: install-methods.xml:1374
 #, no-c-format
 msgid "Move TFTP Images Into Place"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1401
+#: install-methods.xml:1375
 #, no-c-format
 msgid "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-files\"/>, in the <command>tftpd</command> boot image directory. You may 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 ""
 
 #. Tag: para
-#: install-methods.xml:1410
+#: install-methods.xml:1384
 #, no-c-format
 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. You will need to download the following files from the <filename>netboot/</filename> directory:"
 msgstr ""
 
 #. Tag: filename
-#: install-methods.xml:1441
+#: install-methods.xml:1415
 #, no-c-format
 msgid "boot.msg"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1446
+#: install-methods.xml:1420
 #, no-c-format
 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 ""
 
 #. Tag: para
-#: install-methods.xml:1454
+#: install-methods.xml:1428
 #, no-c-format
 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 ""
 
 #. Tag: title
-#: install-methods.xml:1466
+#: install-methods.xml:1440
 #, no-c-format
 msgid "SPARC TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1467
+#: install-methods.xml:1441
 #, no-c-format
 msgid ""
       "Some SPARC architectures add the subarchitecture names, such as <quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename would be <filename>C0A80103.SUN4C</filename>. However, there are also subarchitectures where the file the client looks for is just <filename>client-ip-in-hex</filename>. An easy way to determine the hexadecimal code for the IP address is to enter the following command in a shell (assuming the machine's intended IP is 10.0.0.4). <informalexample><screen>\n"
@@ -1134,55 +1122,55 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1483
+#: install-methods.xml:1457
 #, no-c-format
 msgid "If you've done all this correctly, giving the command <userinput>boot net</userinput> from the OpenPROM should load the image. If the image cannot be found, try checking the logs on your tftp server to see which image name is being requested."
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1490
+#: install-methods.xml:1464
 #, no-c-format
 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 ""
 
 #. Tag: title
-#: install-methods.xml:1501
+#: install-methods.xml:1475
 #, no-c-format
 msgid "SGI TFTP Booting"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1502
+#: install-methods.xml:1476
 #, no-c-format
 msgid "On SGI machines 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 ""
 
 #. Tag: title
-#: install-methods.xml:1610
+#: install-methods.xml:1584
 #, no-c-format
 msgid "Automatic Installation"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1611
+#: install-methods.xml:1585
 #, no-c-format
 msgid "For installing on multiple computers it's possible to do fully automatic installations. &debian; packages intended for this include <classname>fai-quickstart</classname> (which can use an install server) and the &debian; Installer itself. Have a look at the <ulink url=\"http://fai-project.org\">FAI home page</ulink> for detailed information."
 msgstr ""
 
 #. Tag: title
-#: install-methods.xml:1623
+#: install-methods.xml:1597
 #, no-c-format
 msgid "Automatic Installation Using the &debian; Installer"
 msgstr ""
 
 #. Tag: para
-#: install-methods.xml:1624
+#: install-methods.xml:1598
 #, no-c-format
 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 ""
 
 #. Tag: para
-#: install-methods.xml:1631
+#: install-methods.xml:1605
 #, no-c-format
 msgid "Full documentation on preseeding including a working example that you can edit is in <xref linkend=\"appendix-preseed\"/>."
 msgstr ""
diff --git a/po/pot/partitioning.pot b/po/pot/partitioning.pot
index fe19e5e1f..67ce2b0d3 100644
--- a/po/pot/partitioning.pot
+++ b/po/pot/partitioning.pot
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2013-04-16 19:15+0000\n"
+"POT-Creation-Date: 2013-05-22 19:06+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"
@@ -197,509 +197,521 @@ msgstr ""
 #. Tag: filename
 #: partitioning.xml:118
 #, no-c-format
-msgid "sbin"
+msgid "<filename>run</filename>"
 msgstr ""
 
 #. Tag: entry
 #: partitioning.xml:119
 #, no-c-format
-msgid "Essential system binaries"
+msgid "Run-time variable data"
 msgstr ""
 
 #. Tag: filename
 #: partitioning.xml:121
 #, no-c-format
-msgid "<filename>sys</filename>"
+msgid "sbin"
 msgstr ""
 
 #. Tag: entry
 #: partitioning.xml:122
 #, no-c-format
-msgid "Virtual directory for system information (2.6 kernels)"
+msgid "Essential system binaries"
 msgstr ""
 
 #. Tag: filename
 #: partitioning.xml:124
 #, no-c-format
-msgid "<filename>tmp</filename>"
+msgid "<filename>sys</filename>"
 msgstr ""
 
 #. Tag: entry
 #: partitioning.xml:125
 #, no-c-format
-msgid "Temporary files"
+msgid "Virtual directory for system information (2.6 kernels)"
 msgstr ""
 
 #. Tag: filename
 #: partitioning.xml:127
 #, no-c-format
-msgid "<filename>usr</filename>"
+msgid "<filename>tmp</filename>"
 msgstr ""
 
 #. Tag: entry
 #: partitioning.xml:128
 #, no-c-format
-msgid "Secondary hierarchy"
+msgid "Temporary files"
 msgstr ""
 
 #. Tag: filename
 #: partitioning.xml:130
 #, no-c-format
-msgid "<filename>var</filename>"
+msgid "<filename>usr</filename>"
 msgstr ""
 
 #. Tag: entry
 #: partitioning.xml:131
 #, no-c-format
-msgid "Variable data"
+msgid "Secondary hierarchy"
 msgstr ""
 
 #. Tag: filename
 #: partitioning.xml:133
 #, no-c-format
-msgid "<filename>srv</filename>"
+msgid "<filename>var</filename>"
 msgstr ""
 
 #. Tag: entry
 #: partitioning.xml:134
 #, no-c-format
-msgid "Data for services provided by the system"
+msgid "Variable data"
 msgstr ""
 
 #. Tag: filename
 #: partitioning.xml:136
 #, no-c-format
-msgid "<filename>opt</filename>"
+msgid "<filename>srv</filename>"
 msgstr ""
 
 #. Tag: entry
 #: partitioning.xml:137
 #, no-c-format
+msgid "Data for services provided by the system"
+msgstr ""
+
+#. Tag: filename
+#: partitioning.xml:139
+#, no-c-format
+msgid "<filename>opt</filename>"
+msgstr ""
+
+#. Tag: entry
+#: partitioning.xml:140
+#, no-c-format
 msgid "Add-on application software packages"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:142
+#: partitioning.xml:145
 #, no-c-format
 msgid "The following is a list of important considerations regarding directories and partitions. Note that disk usage varies widely given system configuration and specific usage patterns. The recommendations here are general guidelines and provide a starting point for partitioning."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:152
+#: partitioning.xml:155
 #, no-c-format
 msgid "The root partition <filename>/</filename> must always physically contain <filename>/etc</filename>, <filename>/bin</filename>, <filename>/sbin</filename>, <filename>/lib</filename> and <filename>/dev</filename>, otherwise you won't be able to boot. Typically 150&ndash;250MB is needed for the root partition."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:161
+#: partitioning.xml:164
 #, no-c-format
 msgid "<filename>/usr</filename>: contains all user programs (<filename>/usr/bin</filename>), libraries (<filename>/usr/lib</filename>), documentation (<filename>/usr/share/doc</filename>), etc. This is the part of the file system that generally takes up most space. You should provide at least 500MB of disk space. This amount should be increased depending on the number and type of packages you plan to install. A generous workstation or server installation should allow 4&ndash;6GB."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:174
+#: partitioning.xml:177
 #, no-c-format
 msgid "<filename>/var</filename>: variable data like news articles, e-mails, web sites, databases, the packaging system cache, etc. will be placed under this directory. The size of this directory depends greatly on the usage of your system, but for most people will be dictated by the package management tool's overhead. If you are going to do a full installation of just about everything &debian; has to offer, all in one session, setting aside 2 or 3 GB of space for <filename>/var</filename> should be sufficient. If you are going to install in pieces (that is to say, install services and utilities, followed by text stuff, then X, ...), you can get away with 300&ndash;500 MB. If hard drive space is at a premium and you don't plan on doing major system updates, you can get by with as little as 30 or 40 MB."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:190
+#: partitioning.xml:193
 #, no-c-format
 msgid "<filename>/tmp</filename>: temporary data created by programs will most likely go in this directory. 40&ndash;100MB should usually be enough. Some applications &mdash; including archive manipulators, CD/DVD authoring tools, and multimedia software &mdash; may use <filename>/tmp</filename> to temporarily store image files. If you plan to use such applications, you should adjust the space available in <filename>/tmp</filename> accordingly."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:201
+#: partitioning.xml:204
 #, no-c-format
 msgid "<filename>/home</filename>: every user will put his personal data into a subdirectory of this directory. Its size depends on how many users will be using the system and what files are to be stored in their directories. Depending on your planned usage you should reserve about 100MB for each user, but adapt this value to your needs. Reserve a lot more space if you plan to save a lot of multimedia files (pictures, MP3, movies) in your home directory."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:222
+#: partitioning.xml:225
 #, no-c-format
 msgid "Recommended Partitioning Scheme"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:223
+#: partitioning.xml:226
 #, no-c-format
 msgid "For new users, personal &debian; boxes, home systems, and other single-user setups, a single <filename>/</filename> partition (plus swap) is probably the easiest, simplest way to go. However, if your partition is larger than around 6GB, choose ext3 as your partition type. Ext2 partitions need periodic file system integrity checking, and this can cause delays during booting when the partition is large."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:232
+#: partitioning.xml:235
 #, no-c-format
 msgid "For multi-user systems or systems with lots of disk space, it's best to put <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, and <filename>/home</filename> each on their own partitions separate from the <filename>/</filename> partition."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:240
+#: partitioning.xml:243
 #, no-c-format
 msgid "You might need a separate <filename>/usr/local</filename> partition if you plan to install many programs that are not part of the &debian; distribution. If your machine will be a mail server, you might need to make <filename>/var/mail</filename> a separate partition. Often, putting <filename>/tmp</filename> on its own partition, for instance 20&ndash;50MB, is a good idea. If you are setting up a server with lots of user accounts, it's generally good to have a separate, large <filename>/home</filename> partition. In general, the partitioning situation varies from computer to computer depending on its uses."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:252
+#: partitioning.xml:255
 #, no-c-format
 msgid "For very complex systems, you should see the <ulink url=\"&url-multidisk-howto;\"> Multi Disk HOWTO</ulink>. This contains in-depth information, mostly of interest to ISPs and people setting up servers."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:259
+#: partitioning.xml:262
 #, no-c-format
 msgid "With respect to the issue of swap partition size, there are many views. One rule of thumb which works well is to use as much swap as you have system memory. It also shouldn't be smaller than 16MB, in most cases. Of course, there are exceptions to these rules. If you are trying to solve 10000 simultaneous equations on a machine with 256MB of memory, you may need a gigabyte (or more) of swap."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:268
+#: partitioning.xml:271
 #, no-c-format
 msgid "On some 32-bit architectures (m68k and PowerPC), the maximum size of a swap partition is 2GB. That should be enough for nearly any installation. However, if your swap requirements are this high, you should probably try to spread the swap across different disks (also called <quote>spindles</quote>) and, if possible, different SCSI or IDE channels. The kernel will balance swap usage between multiple swap partitions, giving better performance."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:278
+#: partitioning.xml:281
 #, no-c-format
 msgid "As an example, an older home machine might have 32MB of RAM and a 1.7GB IDE drive on <filename>/dev/hda</filename>. There might be a 500MB partition for another operating system on <filename>/dev/hda1</filename>, a 32MB swap partition on <filename>/dev/hda3</filename> and about 1.2GB on <filename>/dev/hda2</filename> as the Linux partition."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:287
+#: partitioning.xml:290
 #, no-c-format
 msgid "For an idea of the space taken by tasks you might be interested in adding after your system installation is complete, check <xref linkend=\"tasksel-size-list\"/>."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:303
+#: partitioning.xml:306
 #, no-c-format
 msgid "Device Names in Linux"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:304
+#: partitioning.xml:307
 #, no-c-format
 msgid "Linux disks and partition names may be different from other operating systems. You need to know the names that Linux uses when you create and mount partitions. Here's the basic naming scheme:"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:312
+#: partitioning.xml:315
 #, no-c-format
 msgid "The first floppy drive is named <filename>/dev/fd0</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:317
+#: partitioning.xml:320
 #, no-c-format
 msgid "The second floppy drive is named <filename>/dev/fd1</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:322
+#: partitioning.xml:325
 #, no-c-format
 msgid "The first SCSI disk (SCSI ID address-wise) is named <filename>/dev/sda</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:328
+#: partitioning.xml:331
 #, no-c-format
 msgid "The second SCSI disk (address-wise) is named <filename>/dev/sdb</filename>, and so on."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:334
+#: partitioning.xml:337
 #, no-c-format
 msgid "The first SCSI CD-ROM is named <filename>/dev/scd0</filename>, also known as <filename>/dev/sr0</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:340
+#: partitioning.xml:343
 #, no-c-format
 msgid "The master disk on IDE primary controller is named <filename>/dev/hda</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:346
+#: partitioning.xml:349
 #, no-c-format
 msgid "The slave disk on IDE primary controller is named <filename>/dev/hdb</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:352
+#: partitioning.xml:355
 #, no-c-format
 msgid "The master and slave disks of the secondary controller can be called <filename>/dev/hdc</filename> and <filename>/dev/hdd</filename>, respectively. Newer IDE controllers can actually have two channels, effectively acting like two controllers."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:363
+#: partitioning.xml:366
 #, no-c-format
 msgid "The first DASD device is named <filename>/dev/dasda</filename>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:369
+#: partitioning.xml:372
 #, no-c-format
 msgid "The second DASD device is named <filename>/dev/dasdb</filename>, and so on."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:377
+#: partitioning.xml:380
 #, no-c-format
 msgid "The partitions on each disk are represented by appending a decimal number to the disk name: <filename>sda1</filename> and <filename>sda2</filename> represent the first and second partitions of the first SCSI disk drive in your system."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:384
+#: partitioning.xml:387
 #, no-c-format
 msgid "Here is a real-life example. Let's assume you have a system with 2 SCSI disks, one at SCSI address 2 and the other at SCSI address 4. The first disk (at address 2) is then named <filename>sda</filename>, and the second <filename>sdb</filename>. If the <filename>sda</filename> drive has 3 partitions on it, these will be named <filename>sda1</filename>, <filename>sda2</filename>, and <filename>sda3</filename>. The same applies to the <filename>sdb</filename> disk and its partitions."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:395
+#: partitioning.xml:398
 #, no-c-format
 msgid "Note that if you have two SCSI host bus adapters (i.e., controllers), the order of the drives can get confusing. The best solution in this case is to watch the boot messages, assuming you know the drive models and/or capacities."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:402
+#: partitioning.xml:405
 #, no-c-format
 msgid "Linux represents the primary partitions as the drive name, plus the numbers 1 through 4. For example, the first primary partition on the first IDE drive is <filename>/dev/hda1</filename>. The logical partitions are numbered starting at 5, so the first logical partition on that same drive is <filename>/dev/hda5</filename>. Remember that the extended partition, that is, the primary partition holding the logical partitions, is not usable by itself. This applies to SCSI disks as well as IDE disks."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:413
+#: partitioning.xml:416
 #, no-c-format
 msgid "Sun disk partitions allow for 8 separate partitions (or slices). The third partition is usually (and is preferred to have) the <quote>Whole Disk</quote> partition. This partition references all of the sectors of the disk, and is used by the boot loader (either SILO, or Sun's)."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:420
+#: partitioning.xml:423
 #, no-c-format
 msgid "The partitions on each disk are represented by appending a decimal number to the disk name: <filename>dasda1</filename> and <filename>dasda2</filename> represent the first and second partitions of the first DASD device in your system."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:435
+#: partitioning.xml:438
 #, no-c-format
 msgid "&debian; Partitioning Programs"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:436
+#: partitioning.xml:439
 #, no-c-format
 msgid "Several varieties of partitioning programs have been adapted by &debian; developers to work on various types of hard disks and computer architectures. Following is a list of the program(s) applicable for your architecture."
 msgstr ""
 
 #. Tag: command
-#: partitioning.xml:448
+#: partitioning.xml:451
 #, no-c-format
 msgid "partman"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:449
+#: partitioning.xml:452
 #, no-c-format
 msgid "Recommended partitioning tool in &debian;. This Swiss army knife can also resize partitions, create filesystems <phrase arch=\"any-x86\"> (<quote>format</quote> in Windows speak)</phrase> and assign them to the mountpoints."
 msgstr ""
 
 #. Tag: command
-#: partitioning.xml:460
+#: partitioning.xml:463
 #, no-c-format
 msgid "fdisk"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:461
+#: partitioning.xml:464
 #, no-c-format
 msgid "The original Linux disk partitioner, good for gurus."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:465
+#: partitioning.xml:468
 #, no-c-format
 msgid "Be careful if you have existing FreeBSD partitions on your machine. The installation kernels include support for these partitions, but the way that <command>fdisk</command> represents them (or not) can make the device names differ. See the <ulink url=\"&url-linux-freebsd;\">Linux+FreeBSD HOWTO</ulink>."
 msgstr ""
 
 #. Tag: command
-#: partitioning.xml:477
+#: partitioning.xml:480
 #, no-c-format
 msgid "cfdisk"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:478
+#: partitioning.xml:481
 #, no-c-format
 msgid "A simple-to-use, full-screen disk partitioner for the rest of us."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:482
+#: partitioning.xml:485
 #, no-c-format
 msgid "Note that <command>cfdisk</command> doesn't understand FreeBSD partitions at all, and, again, device names may differ as a result."
 msgstr ""
 
 #. Tag: command
-#: partitioning.xml:491
+#: partitioning.xml:494
 #, no-c-format
 msgid "atari-fdisk"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:492
+#: partitioning.xml:495
 #, no-c-format
 msgid "Atari-aware version of <command>fdisk</command>."
 msgstr ""
 
 #. Tag: command
-#: partitioning.xml:500
+#: partitioning.xml:503
 #, no-c-format
 msgid "amiga-fdisk"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:501
+#: partitioning.xml:504
 #, no-c-format
 msgid "Amiga-aware version of <command>fdisk</command>."
 msgstr ""
 
 #. Tag: command
-#: partitioning.xml:509
+#: partitioning.xml:512
 #, no-c-format
 msgid "mac-fdisk"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:510
+#: partitioning.xml:513
 #, no-c-format
 msgid "Mac-aware version of <command>fdisk</command>."
 msgstr ""
 
 #. Tag: command
-#: partitioning.xml:518
+#: partitioning.xml:521
 #, no-c-format
 msgid "pmac-fdisk"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:519
+#: partitioning.xml:522
 #, no-c-format
 msgid "PowerMac-aware version of <command>fdisk</command>, also used by BVM and Motorola VMEbus systems."
 msgstr ""
 
 #. Tag: command
-#: partitioning.xml:528
+#: partitioning.xml:531
 #, no-c-format
 msgid "fdasd"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:529
+#: partitioning.xml:532
 #, no-c-format
 msgid "&arch-title; version of <command>fdisk</command>; Please read the fdasd manual page or chapter 13 in <ulink url=\"http://oss.software.ibm.com/developerworks/opensource/linux390/docu/l390dd08.pdf\"> Device Drivers and Installation Commands</ulink> for details."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:540
+#: partitioning.xml:543
 #, no-c-format
 msgid "One of these programs will be run by default when you select <guimenuitem>Partition disks</guimenuitem> (or similar). It may be possible to use a different partitioning tool from the command line on VT2, but this is not recommended."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:547
+#: partitioning.xml:550
 #, no-c-format
 msgid "Remember to mark your boot partition as <quote>Bootable</quote>."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:550
+#: partitioning.xml:553
 #, no-c-format
 msgid "One key point when partitioning for Mac type disks is that the swap partition is identified by its name; it must be named <quote>swap</quote>. All Mac linux partitions are the same partition type, Apple_UNIX_SRV2. Please read the fine manual. We also suggest reading the <ulink url=\"&url-mac-fdisk-tutorial;\">mac-fdisk Tutorial</ulink>, which includes steps you should take if you are sharing your disk with MacOS."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:566 partitioning.xml:590 partitioning.xml:686 partitioning.xml:800 partitioning.xml:877
+#: partitioning.xml:569 partitioning.xml:593 partitioning.xml:689 partitioning.xml:803 partitioning.xml:880
 #, no-c-format
 msgid "Partitioning for &arch-title;"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:567
+#: partitioning.xml:570
 #, no-c-format
 msgid "PALO, the HPPA boot loader, requires a partition of type <quote>F0</quote> somewhere in the first 2GB. This is where the boot loader and an optional kernel and RAMdisk will be stored, so make it big enough for that &mdash; at least 4Mb (I like 8&ndash;16MB). An additional requirement of the firmware is that the Linux kernel must reside within the first 2GB of the disk. This is typically achieved by making the root ext2 partition fit entirely within the first 2GB of the disk. Alternatively you can create a small ext2 partition near the start of the disk and mount that on <filename>/boot</filename>, since that is the directory where the Linux kernel(s) will be stored. <filename>/boot</filename> needs to be big enough to hold whatever kernels (and backups) you might wish to load; 25&ndash;50MB is generally sufficient."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:591
+#: partitioning.xml:594
 #, no-c-format
 msgid "If you have an existing other operating system such as DOS or Windows and you want to preserve that operating system while installing &debian;, you may need to resize its partition to free up space for the &debian; installation. The installer supports resizing of both FAT and NTFS filesystems; when you get to the installer's partitioning step, select the option <guimenuitem>Manual</guimenuitem> and then simply select an existing partition and change its size."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:601
+#: partitioning.xml:604
 #, no-c-format
 msgid "The PC BIOS generally adds additional constraints for disk partitioning. There is a limit to how many <quote>primary</quote> and <quote>logical</quote> partitions a drive can contain. Additionally, with pre 1994&ndash;98 BIOSes, there are limits to where on the drive the BIOS can boot from. More information can be found in the <ulink url=\"&url-partition-howto;\">Linux Partition HOWTO</ulink>, but this section will include a brief overview to help you plan most situations."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:611
+#: partitioning.xml:614
 #, no-c-format
 msgid "<quote>Primary</quote> partitions are the original partitioning scheme for PC disks. However, there can only be four of them. To get past this limitation, <quote>extended</quote> and <quote>logical</quote> partitions were invented. By setting one of your primary partitions as an extended partition, you can subdivide all the space allocated to that partition into logical partitions. You can create up to 60 logical partitions per extended partition; however, you can only have one extended partition per drive."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:622
+#: partitioning.xml:625
 #, no-c-format
 msgid "Linux limits the partitions per drive to 255 partitions for SCSI disks (3 usable primary partitions, 252 logical partitions), and 63 partitions on an IDE drive (3 usable primary partitions, 60 logical partitions). However the normal &debian-gnu; system provides only 20 devices for partitions, so you may not install on partitions higher than 20 unless you first manually create devices for those partitions."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:632
+#: partitioning.xml:635
 #, no-c-format
 msgid "If you have a large IDE disk, and are using neither LBA addressing, nor overlay drivers (sometimes provided by hard disk manufacturers), then the boot partition (the partition containing your kernel image) must be placed within the first 1024 cylinders of your hard drive (usually around 524 megabytes, without BIOS translation)."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:640
+#: partitioning.xml:643
 #, no-c-format
 msgid "This restriction doesn't apply if you have a BIOS newer than around 1995&ndash;98 (depending on the manufacturer) that supports the <quote>Enhanced Disk Drive Support Specification</quote>. Both Lilo, the Linux loader, and &debian;'s alternative <command>mbr</command> must use the BIOS to read the kernel from the disk into RAM. If the BIOS int 0x13 large disk access extensions are found to be present, they will be utilized. Otherwise, the legacy disk access interface is used as a fall-back, and it cannot be used to address any location on the disk higher than the 1023rd cylinder. Once &arch-kernel; is booted, no matter what BIOS your computer has, these restrictions no longer apply, since &arch-kernel; does not use the BIOS for disk access."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:654
+#: partitioning.xml:657
 #, no-c-format
 msgid "If you have a large disk, you might have to use cylinder translation techniques, which you can set from your BIOS setup program, such as LBA (Logical Block Addressing) or CHS translation mode (<quote>Large</quote>). More information about issues with large disks can be found in the <ulink url=\"&url-large-disk-howto;\">Large Disk HOWTO</ulink>. If you are using a cylinder translation scheme, and the BIOS does not support the large disk access extensions, then your boot partition has to fit within the <emphasis>translated</emphasis> representation of the 1024th cylinder."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:666
+#: partitioning.xml:669
 #, no-c-format
 msgid "The recommended way of accomplishing this is to create a small (25&ndash;50MB should suffice) partition at the beginning of the disk to be used as the boot partition, and then create whatever other partitions you wish to have, in the remaining area. This boot partition <emphasis>must</emphasis> be mounted on <filename>/boot</filename>, since that is the directory where the &arch-kernel; kernel(s) will be stored. This configuration will work on any system, regardless of whether LBA or large disk CHS translation is used, and regardless of whether your BIOS supports the large disk access extensions."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:687
+#: partitioning.xml:690
 #, no-c-format
 msgid "The <command>partman</command> disk partitioner is the default partitioning tool for the installer. It manages the set of partitions and their mount points to ensure that the disks and filesystems are properly configured for a successful installation. It actually uses <command>parted</command> to do the on-disk partitioning."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:699
+#: partitioning.xml:702
 #, no-c-format
 msgid "EFI Recognized Formats"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:700
+#: partitioning.xml:703
 #, no-c-format
 msgid "The IA-64 EFI firmware supports two partition table (or disk label) formats, GPT and MS-DOS. MS-DOS, the format typically used on i386 PCs, is no longer recommended for IA-64 systems. Although the installer also provides <command>cfdisk</command>, you should only use <ulink url=\"parted.txt\"> <command>parted</command></ulink> because only it can manage both GPT and MS-DOS tables correctly."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:712
+#: partitioning.xml:715
 #, no-c-format
 msgid "The automatic partitioning recipes for <command>partman</command> allocate an EFI partition as the first partition on the disk. You can also set up the partition under the <guimenuitem>Guided partitioning</guimenuitem> from the main menu in a manner similar to setting up a <emphasis>swap</emphasis> partition."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:720
+#: partitioning.xml:723
 #, no-c-format
 msgid ""
       "The <command>partman</command> partitioner will handle most disk layouts. For those rare cases where it is necessary to manually set up a disk, you can use the shell as described above and run the <command>parted</command> utility directly using its command line interface. Assuming that you want to erase your whole disk and create a GPT table and some partitions, then something similar to the following command sequence could be used: <informalexample><screen>\n"
@@ -714,97 +726,97 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:745
+#: partitioning.xml:748
 #, no-c-format
 msgid "Boot Loader Partition Requirements"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:746
+#: partitioning.xml:749
 #, no-c-format
 msgid "ELILO, the IA-64 boot loader, requires a partition containing a FAT file system with the <userinput>boot</userinput> flag set. The partition must be big enough to hold the boot loader and any kernels or RAMdisks you may wish to boot. A minimum size would be about 20MB, but if you expect to run with multiple kernels, then 128MB might be a better size."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:755
+#: partitioning.xml:758
 #, no-c-format
 msgid "The EFI Boot Manager and the EFI Shell fully support the GPT table so the boot partition does not necessarily have to be the first partition or even on the same disk. This is convenient if you should forget to allocate the partition and only find out after you have formatted the other partitions on your disk(s). The <command>partman</command> partitioner checks for an EFI partition at the same time it checks for a properly set up <emphasis>root</emphasis> partition. This gives you an opportunity to correct the disk layout before the package install begins. The easiest way to correct this omission is to shrink the last partition of the disk to make enough free space for adding an EFI partition."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:770
+#: partitioning.xml:773
 #, no-c-format
 msgid "It is strongly recommended that you allocate the EFI boot partition on the same disk as the <emphasis>root</emphasis> filesystem."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:778
+#: partitioning.xml:781
 #, no-c-format
 msgid "EFI Diagnostic Partitions"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:779
+#: partitioning.xml:782
 #, no-c-format
 msgid "The EFI firmware is significantly more sophisticated than the usual BIOS seen on most x86 PCs. Some system vendors take advantage of the ability of the EFI to access files and run programs from a hard disk filesystem to store diagnostics and EFI based system management utilities on the hard disk. This is a separate FAT format filesystem on the system disk. Consult the system documentation and accessories that come with the system for details. The easiest time to set up a diagnostics partition is at the same time you set up the EFI boot partition."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:801
+#: partitioning.xml:804
 #, no-c-format
 msgid "SGI machines require an SGI disk label in order to make the system bootable from hard disk. It can be created in the fdisk expert menu. The thereby created volume header (partition number 9) should be at least 3MB large. If the volume header created is too small, you can simply delete partition number 9 and re-add it with a different size. Note that the volume header must start at sector 0."
 msgstr ""
 
 #. Tag: title
-#: partitioning.xml:818
+#: partitioning.xml:821
 #, no-c-format
 msgid "Partitioning Newer PowerMacs"
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:819
+#: partitioning.xml:822
 #, no-c-format
 msgid "If you are installing onto a NewWorld PowerMac you must create a special bootstrap partition to hold the boot loader. The size of this partition must have at least 819200 bytes and its partition type must be <emphasis>Apple_Bootstrap</emphasis>. If the bootstrap partition is not created with the <emphasis>Apple_Bootstrap</emphasis> type your machine cannot be made bootable from the hard disk. This partition can easily be created by creating a new partition in <command>partman</command> and telling it to use it as a <quote>NewWorld boot partition</quote>, or in <command>mac-fdisk</command> using the <userinput>b</userinput> command."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:832
+#: partitioning.xml:835
 #, no-c-format
 msgid "The special partition type Apple_Bootstrap is required to prevent MacOS from mounting and damaging the bootstrap partition, as there are special modifications made to it in order for OpenFirmware to boot it automatically."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:839
+#: partitioning.xml:842
 #, no-c-format
 msgid "Note that the bootstrap partition is only meant to hold 3 very small files: the <command>yaboot</command> binary, its configuration <filename>yaboot.conf</filename>, and a first stage OpenFirmware loader <command>ofboot.b</command>. It need not and must not be mounted on your file system nor have kernels or anything else copied to it. The <command>ybin</command> and <command>mkofboot</command> utilities are used to manipulate this partition."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:849
+#: partitioning.xml:852
 #, no-c-format
 msgid "In order for OpenFirmware to automatically boot &debian-gnu; the bootstrap partition should appear before other boot partitions on the disk, especially MacOS boot partitions. The bootstrap partition should be the first one you create. However, if you add a bootstrap partition later, you can use <command>mac-fdisk</command>'s <userinput>r</userinput> command to reorder the partition map so the bootstrap partition comes right after the map (which is always partition 1). It's the logical map order, not the physical address order, that counts."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:861
+#: partitioning.xml:864
 #, no-c-format
 msgid "Apple disks normally have several small driver partitions. If you intend to dual boot your machine with MacOSX, you should retain these partitions and a small HFS partition (800k is the minimum size). That is because MacOSX, on every boot, offers to initialize any disks which do not have active MacOS partitions and driver partitions."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:878
+#: partitioning.xml:881
 #, no-c-format
 msgid "Make sure you create a <quote>Sun disk label</quote> on your boot disk. This is the only kind of partition scheme that the OpenBoot PROM understands, and so it's the only scheme from which you can boot. The <keycap>s</keycap> key is used in <command>fdisk</command> to create Sun disk labels."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:886
+#: partitioning.xml:889
 #, no-c-format
 msgid "Furthermore, on &arch-title; disks, make sure your first partition on your boot disk starts at cylinder 0. While this is required, it also means that the first partition will contain the partition table and the boot block, which are the first two sectors of the disk. You must <emphasis>not</emphasis> put swap on the first partition of the boot drive, since swap partitions do not preserve the first few sectors of the partition. You can put Ext2 or UFS partitions there; these will leave the partition table and the boot block alone."
 msgstr ""
 
 #. Tag: para
-#: partitioning.xml:897
+#: partitioning.xml:900
 #, no-c-format
 msgid "It is also advised that the third partition should be of type <quote>Whole disk</quote> (type 5), and contain the entire disk (from the first cylinder to the last). This is simply a convention of Sun disk labels, and helps the <command>SILO</command> boot loader keep its bearings."
 msgstr ""
diff --git a/po/pot/preparing.pot b/po/pot/preparing.pot
index 3e875838e..0ef9e4018 100644
--- a/po/pot/preparing.pot
+++ b/po/pot/preparing.pot
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2013-04-16 19:15+0000\n"
+"POT-Creation-Date: 2013-05-22 19:06+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"
@@ -1127,95 +1127,95 @@ msgstr ""
 #. Tag: para
 #: preparing.xml:1367
 #, no-c-format
-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."
+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. Boot media differs depending on the runtime mode. 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 ""
 
 #. Tag: para
-#: preparing.xml:1377
+#: preparing.xml:1376
 #, no-c-format
 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 to 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 to find it. Using both sources of information, you have to prepare your machine and the installation medium before you can perform a boot from it. When you see the welcome message in your client session, return to this document to go through the &debian;-specific installation steps."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1394
+#: preparing.xml:1393
 #, no-c-format
 msgid "Native and LPAR installations"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1395
+#: preparing.xml:1394
 #, no-c-format
 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 ""
 
 #. Tag: title
-#: preparing.xml:1409
+#: preparing.xml:1408
 #, no-c-format
 msgid "Installation as a VM guest"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1411
+#: preparing.xml:1410
 #, no-c-format
 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 ""
 
 #. Tag: para
-#: preparing.xml:1421
+#: preparing.xml:1420
 #, no-c-format
 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 (by specifying <userinput>BINARY</userinput> and <userinput>LOCSITE FIX 80</userinput> in your FTP client). <filename>parmfile.debian</filename> can be in either ASCII or EBCDIC format. A sample <filename>debian.exec</filename> script, which will punch the files in the proper order, is included with the images."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1438
+#: preparing.xml:1437
 #, no-c-format
 msgid "Setting up an installation server"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1440
+#: preparing.xml:1439
 #, no-c-format
 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 ""
 
 #. Tag: para
-#: preparing.xml:1448
+#: preparing.xml:1447
 #, no-c-format
 msgid "The installation server needs to copy the exact directory structure from any &debian-gnu; mirror, but 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 ""
 
 #. Tag: emphasis
-#: preparing.xml:1457
+#: preparing.xml:1456
 #, no-c-format
 msgid "FIXME: more information needed &mdash; from a Redbook?"
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1464
+#: preparing.xml:1463
 #, no-c-format
 msgid "Hardware Issues to Watch Out For"
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1467
+#: preparing.xml:1466
 #, no-c-format
 msgid "USB BIOS support and keyboards"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1468
+#: preparing.xml:1467
 #, no-c-format
 msgid "If you have no PS/2-style keyboard, but only a USB model, on some very old PCs you may need to enable legacy keyboard emulation in your BIOS setup to be able to use your keyboard in the bootloader menu, but this is not an issue for modern systems. If your keyboard does not work in the bootloader menu, consult your mainboard manual and look in the BIOS for <quote>Legacy keyboard emulation</quote> or <quote>USB keyboard support</quote> options."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1481
+#: preparing.xml:1480
 #, no-c-format
 msgid "Display-visibility on OldWorld Powermacs"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1483
+#: preparing.xml:1482
 #, no-c-format
 msgid "Some OldWorld Powermacs, most notably those with the <quote>control</quote> display driver, may not reliably produce a colormap under Linux when the display is configured for more than 256 colors. If you are experiencing such issues with your display after rebooting (you can sometimes see data on the monitor, but on other occasions cannot see anything) or, if the screen turns black after booting the installer instead of showing you the user interface, try changing your display settings under MacOS to use 256 colors instead of <quote>thousands</quote> or <quote>millions</quote>."
 msgstr ""
diff --git a/po/pot/preseed.pot b/po/pot/preseed.pot
index 00e96d181..5ca3765bd 100644
--- a/po/pot/preseed.pot
+++ b/po/pot/preseed.pot
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2013-04-21 17:45+0000\n"
+"POT-Creation-Date: 2013-05-22 19:06+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"
@@ -143,7 +143,7 @@ msgstr ""
 #. Tag: entry
 #: preseed.xml:108
 #, no-c-format
-msgid "generic/tape"
+msgid "generic"
 msgstr ""
 
 #. Tag: para
@@ -681,7 +681,7 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:558
 #, no-c-format
-msgid "It's also possible to use DHCP to specify a preconfiguration file to download from the network. DHCP allows specifying a filename. Normally this is a file to netboot, but if it appears to be an URL then installation media that support network preseeding will download the file from the URL and use it as a preconfiguration file. Here is an example of how to set it up in the dhcpd.conf for version 3 of the ISC DHCP server (the dhcp3-server &debian; package)."
+msgid "It's also possible to use DHCP to specify a preconfiguration file to download from the network. DHCP allows specifying a filename. Normally this is a file to netboot, but if it appears to be an URL then installation media that support network preseeding will download the file from the URL and use it as a preconfiguration file. Here is an example of how to set it up in the dhcpd.conf for version 3 of the ISC DHCP server (the isc-dhcp-server &debian; package)."
 msgstr ""
 
 #. Tag: screen
@@ -1427,9 +1427,8 @@ msgid ""
       "#d-i apt-setup/use_mirror boolean false\n"
       "# Select which update services to use; define the mirrors to be used.\n"
       "# Values shown below are the normal defaults.\n"
-      "#d-i apt-setup/services-select multiselect security, volatile\n"
+      "#d-i apt-setup/services-select multiselect security, updates\n"
       "#d-i apt-setup/security_host string security.debian.org\n"
-      "#d-i apt-setup/volatile_host string volatile.debian.org\n"
       "\n"
       "# Additional repositories, local[0-9] available\n"
       "#d-i apt-setup/local0/repository string \\\n"
diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot
index 732c2a478..74a62d175 100644
--- a/po/pot/using-d-i.pot
+++ b/po/pot/using-d-i.pot
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2013-04-21 17:45+0000\n"
+"POT-Creation-Date: 2013-05-22 19:06+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"
@@ -1910,13 +1910,13 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2329
 #, no-c-format
-msgid "If you are installing at default priority, the installer will largely take care of the configuration automatically, based on the installation method you are using and possibly using choices made earlier in the installation. In most cases the installer will automatically add a security mirror and, if you are installing the stable distribution, a mirror for the <quote>volatile</quote> update service."
+msgid "If you are installing at default priority, the installer will largely take care of the configuration automatically, based on the installation method you are using and possibly using choices made earlier in the installation. In most cases the installer will automatically add a security mirror and, if you are installing the stable distribution, a mirror for the <quote>stable-updates</quote> service."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2338
 #, no-c-format
-msgid "If you are installing at a lower priority (e.g. in expert mode), you will be able to make more decisions yourself. You can choose whether or not to use the security and/or volatile update services, and you can choose to add packages from the <quote>contrib</quote> and <quote>non-free</quote> sections of the archive."
+msgid "If you are installing at a lower priority (e.g. in expert mode), you will be able to make more decisions yourself. You can choose whether or not to use the security and/or stable-updates services, and you can choose to add packages from the <quote>contrib</quote> and <quote>non-free</quote> sections of the archive."
 msgstr ""
 
 #. Tag: title
@@ -2024,13 +2024,13 @@ msgstr ""
 #. Tag: para
 #: using-d-i.xml:2469
 #, no-c-format
-msgid "whether any updated versions of packages included on the CDs or DVDs are available from a mirror (either a regular package mirror, or a mirror for security or volatile updates)."
+msgid "whether any updated versions of packages included on the CDs or DVDs are available from a mirror (either a regular package mirror, or a mirror for security or stable-updates)."
 msgstr ""
 
 #. Tag: para
 #: using-d-i.xml:2478
 #, no-c-format
-msgid "Note that the last point means that, even if you choose not to use a network mirror, some packages may still be downloaded from the Internet if there is a security or volatile update available for them and those services have been configured."
+msgid "Note that the last point means that, even if you choose not to use a network mirror, some packages may still be downloaded from the Internet if there is a security or stable-updates update available for them and those services have been configured."
 msgstr ""
 
 #. Tag: title