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

author: Felipe Augusto van de Wiel <faw@debian.org> 2008-10-05 00:08:06 +0000
committer: Felipe Augusto van de Wiel <faw@debian.org> 2008-10-05 00:08:06 +0000
commit: 2d5cb2b72b12f78d9775f4115c1ff1ae0c0a747c (patch)
tree: b3b6da52354f7939c4f365c9d854bd589c5c4c4b /po/pot
parent: d796c0b482621422867036216356369b6fde08a2 (diff)
download: installation-guide-2d5cb2b72b12f78d9775f4115c1ff1ae0c0a747c.zip
4 files changed, 1307 insertions, 1291 deletions
diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot
index 8c52dba38..3f9ddda02 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: 2008-07-04 00:09+0000\n"
+"POT-Creation-Date: 2008-10-05 00:05+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"
@@ -350,7 +350,7 @@ msgid "As on other architectures, you should install the newest available revisi
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:301 boot-installer.xml:1050 boot-installer.xml:1577 boot-installer.xml:2074 boot-installer.xml:2156 boot-installer.xml:2245 boot-installer.xml:2589 boot-installer.xml:2698
+#: boot-installer.xml:301 boot-installer.xml:1050 boot-installer.xml:1577 boot-installer.xml:2074 boot-installer.xml:2156 boot-installer.xml:2245 boot-installer.xml:2591 boot-installer.xml:2700
 #, no-c-format
 msgid "Booting with TFTP"
 msgstr ""
@@ -499,19 +499,19 @@ msgid "Booting from TFTP"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:468 boot-installer.xml:1056 boot-installer.xml:1595 boot-installer.xml:2080 boot-installer.xml:2595 boot-installer.xml:2704
+#: boot-installer.xml:468 boot-installer.xml:1056 boot-installer.xml:1595 boot-installer.xml:2080 boot-installer.xml:2597 boot-installer.xml:2706
 #, 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:473 boot-installer.xml:1061 boot-installer.xml:1600 boot-installer.xml:2085 boot-installer.xml:2600 boot-installer.xml:2709
+#: boot-installer.xml:473 boot-installer.xml:1061 boot-installer.xml:1600 boot-installer.xml:2085 boot-installer.xml:2602 boot-installer.xml:2711
 #, 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:478 boot-installer.xml:1066 boot-installer.xml:1605 boot-installer.xml:2090 boot-installer.xml:2605 boot-installer.xml:2714
+#: boot-installer.xml:478 boot-installer.xml:1066 boot-installer.xml:1605 boot-installer.xml:2090 boot-installer.xml:2607 boot-installer.xml:2716
 #, no-c-format
 msgid "The installation method to support network booting is described in <xref linkend=\"install-tftp\"/>."
 msgstr ""
@@ -580,25 +580,25 @@ msgid "Booting from CD-ROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1214 boot-installer.xml:2037 boot-installer.xml:2383 boot-installer.xml:2742
+#: boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1214 boot-installer.xml:2037 boot-installer.xml:2383 boot-installer.xml:2744
 #, 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:584 boot-installer.xml:754 boot-installer.xml:1225 boot-installer.xml:2048 boot-installer.xml:2394 boot-installer.xml:2753
+#: boot-installer.xml:584 boot-installer.xml:754 boot-installer.xml:1225 boot-installer.xml:2048 boot-installer.xml:2394 boot-installer.xml:2755
 #, 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:592 boot-installer.xml:762 boot-installer.xml:1233 boot-installer.xml:2056 boot-installer.xml:2402 boot-installer.xml:2761
+#: boot-installer.xml:592 boot-installer.xml:762 boot-installer.xml:1233 boot-installer.xml:2056 boot-installer.xml:2402 boot-installer.xml:2763
 #, 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:600 boot-installer.xml:770 boot-installer.xml:1241 boot-installer.xml:2064 boot-installer.xml:2410 boot-installer.xml:2769
+#: boot-installer.xml:600 boot-installer.xml:770 boot-installer.xml:1241 boot-installer.xml:2064 boot-installer.xml:2410 boot-installer.xml:2771
 #, no-c-format
 msgid "If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>."
 msgstr ""
@@ -679,7 +679,7 @@ msgid "There is <ulink url=\"http://www.everbesthk.com/8-download/sercomm/firmwa
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:737 boot-installer.xml:1208 boot-installer.xml:2025 boot-installer.xml:2377 boot-installer.xml:2736
+#: boot-installer.xml:737 boot-installer.xml:1208 boot-installer.xml:2025 boot-installer.xml:2377 boot-installer.xml:2738
 #, no-c-format
 msgid "Booting from a CD-ROM"
 msgstr ""
@@ -783,13 +783,13 @@ msgid "Let's assume you have prepared everything from <xref linkend=\"boot-dev-s
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:992 boot-installer.xml:2137 boot-installer.xml:2644
+#: boot-installer.xml:992 boot-installer.xml:2137 boot-installer.xml:2646
 #, no-c-format
 msgid "Booting from Floppies"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:993 boot-installer.xml:2652
+#: boot-installer.xml:993 boot-installer.xml:2654
 #, 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 ""
@@ -1563,7 +1563,7 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2203 boot-installer.xml:2307 boot-installer.xml:2804
+#: boot-installer.xml:2203 boot-installer.xml:2307 boot-installer.xml:2806
 #, no-c-format
 msgid "Boot Parameters"
 msgstr ""
@@ -1686,37 +1686,25 @@ msgid "Booting from Hard Disk"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2471
-#, no-c-format
-msgid "Booting CHRP from OpenFirmware"
-msgstr ""
-
-#. Tag: emphasis
-#: boot-installer.xml:2475
-#, no-c-format
-msgid "Not yet written."
-msgstr ""
-
-#. Tag: title
-#: boot-installer.xml:2480
+#: boot-installer.xml:2482
 #, no-c-format
 msgid "Booting OldWorld PowerMacs from MacOS"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2481
+#: boot-installer.xml:2483
 #, 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:2499
+#: boot-installer.xml:2501
 #, no-c-format
 msgid "Booting NewWorld Macs from OpenFirmware"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2500
+#: boot-installer.xml:2502
 #, 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"
@@ -1727,31 +1715,31 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:2532
+#: boot-installer.xml:2534
 #, no-c-format
 msgid "Booting from USB memory stick"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2533
+#: boot-installer.xml:2535
 #, no-c-format
 msgid "Currently, NewWorld PowerMac systems are known to support USB booting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2539
+#: boot-installer.xml:2541
 #, 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:2548
+#: boot-installer.xml:2550
 #, 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:2560
+#: boot-installer.xml:2562
 #, no-c-format
 msgid ""
       "Having worked out the device path, use a command like this to boot the installer: <informalexample><screen>\n"
@@ -1760,25 +1748,25 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2574
+#: boot-installer.xml:2576
 #, 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:2580
+#: boot-installer.xml:2582
 #, 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:2613
+#: boot-installer.xml:2615
 #, no-c-format
 msgid "Currently, PReP and New World PowerMac systems support netbooting."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2617
+#: boot-installer.xml:2619
 #, 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"
@@ -1791,85 +1779,85 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2645
+#: boot-installer.xml:2647
 #, 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:2657
+#: boot-installer.xml:2659
 #, 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:2663
+#: boot-installer.xml:2665
 #, 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:2670
+#: boot-installer.xml:2672
 #, 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:2681
+#: boot-installer.xml:2683
 #, no-c-format
 msgid "PowerPC Boot Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2682
+#: boot-installer.xml:2684
 #, 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:2722
+#: boot-installer.xml:2724
 #, 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."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2776
+#: boot-installer.xml:2778
 #, 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:2785
+#: boot-installer.xml:2787
 #, no-c-format
 msgid "IDPROM Messages"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2786
+#: boot-installer.xml:2788
 #, 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: para
-#: boot-installer.xml:2805
+#: boot-installer.xml:2807
 #, 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:2812
+#: boot-installer.xml:2814
 #, 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:2819
+#: boot-installer.xml:2821
 #, 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: para
-#: boot-installer.xml:2828
+#: boot-installer.xml:2830
 #, no-c-format
 msgid ""
       "When the kernel boots, a message <informalexample><screen>\n"
@@ -1878,499 +1866,499 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2844
+#: boot-installer.xml:2846
 #, 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:2856
+#: boot-installer.xml:2858
 #, 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:2867
+#: boot-installer.xml:2869
 #, no-c-format
 msgid "Debian Installer Parameters"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2868
+#: boot-installer.xml:2870
 #, 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:2881
+#: boot-installer.xml:2883
 #, 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:2893
+#: boot-installer.xml:2895
 #, no-c-format
 msgid "debconf/priority (priority)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2894
+#: boot-installer.xml:2896
 #, no-c-format
 msgid "This parameter sets the lowest priority of messages to be displayed."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2898
+#: boot-installer.xml:2900
 #, 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:2905
+#: boot-installer.xml:2907
 #, 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:2919
+#: boot-installer.xml:2921
 #, no-c-format
 msgid "DEBIAN_FRONTEND"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2920
+#: boot-installer.xml:2922
 #, 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. Generally, only the <userinput>newt</userinput> frontend is available on default install media. On architectures that support it, the graphical installer uses the <userinput>gtk</userinput> frontend."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:2949
+#: boot-installer.xml:2951
 #, no-c-format
 msgid "BOOT_DEBUG"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2950
+#: boot-installer.xml:2952
 #, 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:2959
+#: boot-installer.xml:2961
 #, no-c-format
 msgid "BOOT_DEBUG=0"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2960
+#: boot-installer.xml:2962
 #, no-c-format
 msgid "This is the default."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2964
+#: boot-installer.xml:2966
 #, no-c-format
 msgid "BOOT_DEBUG=1"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2965
+#: boot-installer.xml:2967
 #, no-c-format
 msgid "More verbose than usual."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2969
+#: boot-installer.xml:2971
 #, no-c-format
 msgid "BOOT_DEBUG=2"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2970
+#: boot-installer.xml:2972
 #, no-c-format
 msgid "Lots of debugging information."
 msgstr ""
 
 #. Tag: userinput
-#: boot-installer.xml:2974
+#: boot-installer.xml:2976
 #, no-c-format
 msgid "BOOT_DEBUG=3"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2975
+#: boot-installer.xml:2977
 #, 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:2989
+#: boot-installer.xml:2991
 #, no-c-format
 msgid "INSTALL_MEDIA_DEV"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:2990
+#: boot-installer.xml:2992
 #, 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:2996
+#: boot-installer.xml:2998
 #, 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:3006
+#: boot-installer.xml:3008
 #, no-c-format
 msgid "lowmem"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3007
+#: boot-installer.xml:3009
 #, 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:3017
+#: boot-installer.xml:3019
 #, no-c-format
 msgid "debian-installer/framebuffer (fb)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3018
+#: boot-installer.xml:3020
 #, no-c-format
 msgid "Some architectures use the kernel framebuffer to offer installation in a number of languages. If framebuffer causes a problem on your system you can disable the feature by the parameter <userinput>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:3027
+#: boot-installer.xml:3029
 #, no-c-format
 msgid "The <userinput>video=vga16:off</userinput> argument may also be used to disable the kernel's use of the framebuffer. Such problems have been reported on a Dell Inspiron with Mobile Radeon card."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3033
+#: boot-installer.xml:3035
 #, no-c-format
 msgid "Such problems have been reported on the Amiga 1200 and SE/30."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3037
+#: boot-installer.xml:3039
 #, no-c-format
 msgid "Such problems have been reported on hppa."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3041
+#: boot-installer.xml:3043
 #, 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:3055
+#: boot-installer.xml:3057
 #, no-c-format
 msgid "debian-installer/theme (theme)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3056
+#: boot-installer.xml:3058
 #, 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:3068 boot-installer.xml:3318
+#: boot-installer.xml:3070 boot-installer.xml:3320
 #, no-c-format
 msgid "netcfg/disable_dhcp"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3069
+#: boot-installer.xml:3071
 #, no-c-format
 msgid "By default, the &d-i; automatically probes for network configuration via DHCP. If the probe succeeds, you won't have a chance to review and change the obtained settings. You can get to the manual network setup only in case the DHCP probe fails."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3076
+#: boot-installer.xml:3078
 #, no-c-format
 msgid "If you have a DHCP server on your local network, but want to avoid it because e.g. it gives wrong answers, you can use the parameter <userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the network with DHCP and to enter the information manually."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3087
+#: boot-installer.xml:3089
 #, no-c-format
 msgid "hw-detect/start_pcmcia"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3088
+#: boot-installer.xml:3090
 #, 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:3098
+#: boot-installer.xml:3100
 #, no-c-format
 msgid "disk-detect/dmraid/enable (dmraid)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3099
+#: boot-installer.xml:3101
 #, 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:3110
+#: boot-installer.xml:3112
 #, no-c-format
 msgid "preseed/url (url)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3111
+#: boot-installer.xml:3113
 #, 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:3120
+#: boot-installer.xml:3122
 #, no-c-format
 msgid "preseed/file (file)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3121
+#: boot-installer.xml:3123
 #, 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:3130
+#: boot-installer.xml:3132
 #, no-c-format
 msgid "preseed/interactive"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3131
+#: boot-installer.xml:3133
 #, 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:3143
+#: boot-installer.xml:3145
 #, no-c-format
 msgid "auto-install/enable (auto)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3144
+#: boot-installer.xml:3146
 #, 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:3155
+#: boot-installer.xml:3157
 #, no-c-format
 msgid "finish-install/keep-consoles"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3156
+#: boot-installer.xml:3158
 #, 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:3167
+#: boot-installer.xml:3169
 #, no-c-format
 msgid "cdrom-detect/eject"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3168
+#: boot-installer.xml:3170
 #, 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:3177
+#: boot-installer.xml:3179
 #, 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:3188
+#: boot-installer.xml:3190
 #, no-c-format
 msgid "debian-installer/allow_unauthenticated"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3189
+#: boot-installer.xml:3191
 #, 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:3200
+#: boot-installer.xml:3202
 #, no-c-format
 msgid "ramdisk_size"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3201
+#: boot-installer.xml:3203
 #, 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:3211
+#: boot-installer.xml:3213
 #, no-c-format
 msgid "mouse/protocol"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3212
+#: boot-installer.xml:3214
 #, no-c-format
 msgid "For the gtk frontend (graphical installer), users can set the mouse protocol to be used by setting this parameter. Supported values are<footnote> <para> See the man page for <citerefentry><refentrytitle>directfbrc</refentrytitle> <manvolnum>5</manvolnum></citerefentry> for additional information. </para> </footnote>: <userinput>PS/2</userinput>, <userinput>IMPS/2</userinput>, <userinput>MS</userinput>, <userinput>MS3</userinput>, <userinput>MouseMan</userinput> and <userinput>MouseSystems</userinput>. In most cases the default protocol should work correctly."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3234
+#: boot-installer.xml:3236
 #, no-c-format
 msgid "mouse/device"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3235
+#: boot-installer.xml:3237
 #, no-c-format
 msgid "For the gtk frontend (graphical installer), users can specify the mouse device to be used by setting this parameter. This is mostly useful if the mouse is connected to a serial port (serial mouse). Example: <userinput>mouse/device=<replaceable>/dev/ttyS1</replaceable></userinput>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3246
+#: boot-installer.xml:3248
 #, no-c-format
 msgid "mouse/left"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3247
+#: boot-installer.xml:3249
 #, no-c-format
 msgid "For the gtk frontend (graphical installer), users can switch the mouse to left-handed operation by setting this parameter to <userinput>true</userinput>."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3256
+#: boot-installer.xml:3258
 #, no-c-format
 msgid "directfb/hw-accel"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3257
+#: boot-installer.xml:3259
 #, no-c-format
 msgid "For the gtk frontend (graphical installer), hardware acceleration in directfb is disabled by default. Set this parameter to <userinput>true</userinput> to enable it."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3267
+#: boot-installer.xml:3269
 #, no-c-format
 msgid "rescue/enable"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3268
+#: boot-installer.xml:3270
 #, 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:3279
+#: boot-installer.xml:3281
 #, no-c-format
 msgid "Using boot parameters to answer questions"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3280
+#: boot-installer.xml:3282
 #, 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:3292
+#: boot-installer.xml:3294
 #, no-c-format
 msgid "debian-installer/locale (locale)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3293
+#: boot-installer.xml:3295
 #, no-c-format
 msgid "Can be used to set both the language and country for the installation. This will only work if the locale is supported in Debian. For example, use <userinput>locale=de_CH</userinput> to select German as language and Switzerland as country."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3304
+#: boot-installer.xml:3306
 #, no-c-format
 msgid "anna/choose_modules (modules)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3305
+#: boot-installer.xml:3307
 #, 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:3319
+#: boot-installer.xml:3321
 #, no-c-format
 msgid "Set to <userinput>true</userinput> if you want to disable DHCP and instead force static network configuration."
 msgstr ""
 
 #. Tag: term
-#: boot-installer.xml:3328
+#: boot-installer.xml:3330
 #, no-c-format
 msgid "mirror/protocol (protocol)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3329
+#: boot-installer.xml:3331
 #, 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:3342
+#: boot-installer.xml:3344
 #, no-c-format
 msgid "tasksel:tasksel/first (tasks)"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3343
+#: boot-installer.xml:3345
 #, 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:3357
+#: boot-installer.xml:3359
 #, no-c-format
 msgid "Passing parameters to kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3358
+#: boot-installer.xml:3360
 #, 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:3371
+#: boot-installer.xml:3373
 #, 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:3378
+#: boot-installer.xml:3380
 #, no-c-format
 msgid ""
       "The syntax to use to set parameters for modules is: <informalexample><screen>\n"
@@ -2379,133 +2367,133 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:3388
+#: boot-installer.xml:3390
 #, no-c-format
 msgid "3c509.xcvr=3 3c509.irq=10"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3394
+#: boot-installer.xml:3396
 #, no-c-format
 msgid "Blacklisting kernel modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3395
+#: boot-installer.xml:3397
 #, 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:3404
+#: boot-installer.xml:3406
 #, 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:3412
+#: boot-installer.xml:3414
 #, 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:3429
+#: boot-installer.xml:3431
 #, no-c-format
 msgid "Troubleshooting the Installation Process"
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3434
+#: boot-installer.xml:3436
 #, no-c-format
 msgid "CD-ROM Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3435
+#: boot-installer.xml:3437
 #, 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:3442
+#: boot-installer.xml:3444
 #, no-c-format
 msgid "There are a many different possible causes for these problems. We can only list some common issues and provide general suggestions on how to deal with them. The rest is up to you."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3448
+#: boot-installer.xml:3450
 #, no-c-format
 msgid "There are two very simple things that you should try first."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3453
+#: boot-installer.xml:3455
 #, 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:3459
+#: boot-installer.xml:3461
 #, 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 older CD-ROM drives are known to be resolved in this way."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3469
+#: boot-installer.xml:3471
 #, 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:3475
+#: boot-installer.xml:3477
 #, 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:3483
+#: boot-installer.xml:3485
 #, no-c-format
 msgid "Common issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3486
+#: boot-installer.xml:3488
 #, 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:3492
+#: boot-installer.xml:3494
 #, no-c-format
 msgid "If your system boots correctly from the CD-ROM, it does not necessarily mean that Linux also supports the CD-ROM (or, more correctly, the controller that your CD-ROM drive is connected to)."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3499
+#: boot-installer.xml:3501
 #, no-c-format
 msgid "Some older CD-ROM drives do not work correctly if <quote>direct memory access</quote> (DMA) is enabled."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3510
+#: boot-installer.xml:3512
 #, no-c-format
 msgid "How to investigate and maybe solve issues"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3511
+#: boot-installer.xml:3513
 #, no-c-format
 msgid "If the CD-ROM fails to boot, try the suggestions listed below."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3516
+#: boot-installer.xml:3518
 #, no-c-format
 msgid "Check that your BIOS actually supports booting from CD-ROM (older systems possibly don't) and that your CD-ROM drive supports the media you are using."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3522
+#: boot-installer.xml:3524
 #, 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"
@@ -2515,7 +2503,7 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: boot-installer.xml:3535
+#: boot-installer.xml:3537
 #, no-c-format
 msgid ""
       "$ dd if=/dev/cdrom | \\\n"
@@ -2528,19 +2516,19 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3540
+#: boot-installer.xml:3542
 #, no-c-format
 msgid "If, after the installer has been booted successfully, the CD-ROM is not detected, sometimes simply trying again may solve the problem. If you have more than one CD-ROM drive, try changing the CD-ROM to the other drive. If that does not work or if the CD-ROM is recognized but there are errors when reading from it, try the suggestions listed below. Some basic knowledge of Linux is required for this. To execute any of the commands, you should first switch to the second virtual console (VT2) and activate the shell there."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3552
+#: boot-installer.xml:3554
 #, 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:3559
+#: boot-installer.xml:3561
 #, 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"
@@ -2553,13 +2541,13 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3573
+#: boot-installer.xml:3575
 #, no-c-format
 msgid "Check that there is a device node for your CD-ROM drive under <filename>/dev/</filename>. In the example above, this would be <filename>/dev/hdc</filename>. There should also be a <filename>/dev/cdroms/cdrom0</filename>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3581
+#: boot-installer.xml:3583
 #, 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"
@@ -2568,7 +2556,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3591
+#: boot-installer.xml:3593
 #, no-c-format
 msgid ""
       "Check if DMA is currently enabled: <informalexample><screen>\n"
@@ -2581,157 +2569,163 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3606
+#: boot-installer.xml:3608
 #, 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:3621
+#: boot-installer.xml:3623
 #, no-c-format
 msgid "Floppy Disk Reliability"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3623
+#: boot-installer.xml:3625
 #, 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:3628
+#: boot-installer.xml:3630
 #, 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:3637
+#: boot-installer.xml:3639
 #, 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:3646
+#: boot-installer.xml:3648
 #, 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:3652
+#: boot-installer.xml:3654
 #, 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:3658
+#: boot-installer.xml:3660
 #, 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:3667
+#: boot-installer.xml:3669
 #, no-c-format
 msgid "Boot Configuration"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3669
+#: boot-installer.xml:3671
 #, 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:3676
+#: boot-installer.xml:3678
 #, no-c-format
 msgid "Often, problems can be solved by removing add-ons and peripherals, and then trying booting again. <phrase arch=\"x86\">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3682
+#: boot-installer.xml:3684
 #, no-c-format
 msgid "If you have a large amount of memory installed in your machine, more than 512M, and the installer hangs when booting the kernel, you may need to include a boot argument to limit the amount of memory the kernel sees, such as <userinput>mem=512m</userinput>."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3693 boot-installer.xml:3777
+#: boot-installer.xml:3695 boot-installer.xml:3797
 #, no-c-format
 msgid "Common &arch-title; Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3694
+#: boot-installer.xml:3696
 #, 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:3699
+#: boot-installer.xml:3701
 #, no-c-format
 msgid "Some systems have floppies with <quote>inverted DCLs</quote>. If you receive errors reading from the floppy, even when you know the floppy is good, try the parameter <userinput>floppy=thinkpad</userinput>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3705
+#: boot-installer.xml:3707
 #, no-c-format
 msgid "On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk drivers), the IDE drive may not be properly recognized. Again, try it first without the parameters and see if the IDE drive is recognized properly. If not, determine your drive geometry (cylinders, heads, and sectors), and use the parameter <userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3714
+#: boot-installer.xml:3716
 #, no-c-format
 msgid "If you have a very old machine, and the kernel hangs after saying <computeroutput>Checking 'hlt' instruction...</computeroutput>, then you should try the <userinput>no-hlt</userinput> boot argument, which disables this test."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3721
+#: boot-installer.xml:3723
+#, no-c-format
+msgid "Some systems (especially laptops) that have a native resolution that is not a 4:3 ratio (i.e. not for example 800x600 or 1024x768) may have a blank display after the installer has been booted. In that case adding the boot parameter <userinput>vga=788</userinput><footnote> <para> The parameter <userinput>vga=788</userinput> will activate the VESA framebuffer with a resolution of 800x600. This will probably work, but may not be the optimal resolution for your system. A list of supported resulutions can be obtained by using <userinput>vga=ask</userinput>, but you should be aware that list may not be complete. </para> </footnote> may help. If that does not work, try adding the boot parameter <userinput>fb=false</userinput>."
+msgstr ""
+
+#. Tag: para
+#: boot-installer.xml:3741
 #, no-c-format
-msgid "If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter <userinput>fb=false video=vga16:off</userinput> to disable the framebuffer console. Only a reduced set of languages will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details."
+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:3735
+#: boot-installer.xml:3755
 #, no-c-format
 msgid "System Freeze During the PCMCIA Configuration Phase"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3736
+#: boot-installer.xml:3756
 #, no-c-format
 msgid "Some laptop models produced by Dell are known to crash when PCMCIA device detection tries to access some hardware addresses. Other laptops may display similar problems. If you experience such a problem and you don't need PCMCIA support during the installation, you can disable PCMCIA using the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can then configure PCMCIA after the installation is completed and exclude the resource range causing the problems."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3746
+#: boot-installer.xml:3766
 #, no-c-format
 msgid "Alternatively, you can boot the installer in expert mode. You will then be asked to enter the resource range options your hardware needs. For example, if you have one of the Dell laptops mentioned above, you should enter <userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list of some common resource range options in the <ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the commas, if any, when you enter this value in the installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3763
+#: boot-installer.xml:3783
 #, no-c-format
 msgid "System Freeze while Loading USB Modules"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3764
+#: boot-installer.xml:3784
 #, no-c-format
 msgid "The kernel normally tries to install USB modules and the USB keyboard driver in order to support some non-standard USB keyboards. However, there are some broken USB systems where the driver hangs on loading. A possible workaround may be disabling the USB controller in your mainboard BIOS setup. Another option is passing the <userinput>nousb</userinput> parameter at the boot prompt."
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3778
+#: boot-installer.xml:3798
 #, no-c-format
 msgid "There are some common installation problems that are worth mentioning."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3784
+#: boot-installer.xml:3804
 #, no-c-format
 msgid "Misdirected video output"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3785
+#: boot-installer.xml:3805
 #, 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"
@@ -2741,85 +2735,85 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3799
+#: boot-installer.xml:3819
 #, 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:3810
+#: boot-installer.xml:3830
 #, no-c-format
 msgid "Failure to Boot or Install from CD-ROM"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3811
+#: boot-installer.xml:3831
 #, 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:3817
+#: boot-installer.xml:3837
 #, no-c-format
 msgid "We recommend to install such systems by netbooting the installer."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3826
+#: boot-installer.xml:3846
 #, no-c-format
 msgid "Interpreting the Kernel Startup Messages"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3828
+#: boot-installer.xml:3848
 #, no-c-format
 msgid "During the boot sequence, you may see many messages in the form <computeroutput>can't find <replaceable>something</replaceable></computeroutput>, or <computeroutput><replaceable>something</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>something</replaceable></computeroutput>, or even <computeroutput>this driver release depends on <replaceable>something</replaceable></computeroutput>. Most of these messages are harmless. You see them because the kernel for the installation system is built to run on computers with many different peripheral devices. Obviously, no one computer will have every possible peripheral device, so the operating system may emit a few complaints while it looks for peripherals you don't own. You may also see the system pause for a while. This happens when it is waiting for a device to respond, and that device is not present on your system. If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later (see <xref linkend=\"kernel-baking\"/>)."
 msgstr ""
 
 #. Tag: title
-#: boot-installer.xml:3853
+#: boot-installer.xml:3873
 #, no-c-format
 msgid "Reporting Installation Problems"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3854
+#: boot-installer.xml:3874
 #, 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:3865
+#: boot-installer.xml:3885
 #, 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:3876
+#: boot-installer.xml:3896
 #, no-c-format
 msgid "Submitting Installation Reports"
 msgstr ""
 
 #. Tag: para
-#: boot-installer.xml:3877
+#: boot-installer.xml:3897
 #, 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:3884
+#: boot-installer.xml:3904
 #, 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:3890
+#: boot-installer.xml:3910
 #, 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:3900
+#: boot-installer.xml:3920
 #, 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/hardware.pot b/po/pot/hardware.pot
index 1bd77cd52..e97627d4d 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: 2008-09-28 00:09+0000\n"
+"POT-Creation-Date: 2008-10-05 00:05+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"
@@ -53,7 +53,7 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:42
 #, no-c-format
-msgid "Debian &release; supports twelve major architectures and several variations of each architecture known as <quote>flavors</quote>."
+msgid "Debian &release; supports eleven major architectures and several variations of each architecture known as <quote>flavors</quote>."
 msgstr ""
 
 #. Tag: entry
@@ -143,1735 +143,1723 @@ msgstr ""
 #. Tag: entry
 #: hardware.xml:86
 #, no-c-format
-msgid "Intel IOP32x"
+msgid "<entry>Versatile</entry>"
 msgstr ""
 
 #. Tag: entry
 #: hardware.xml:87
 #, no-c-format
-msgid "iop32x"
+msgid "versatile"
 msgstr ""
 
 #. Tag: entry
 #: hardware.xml:89
 #, no-c-format
-msgid "Intel IXP4xx"
+msgid "arm and armel"
 msgstr ""
 
 #. Tag: entry
 #: hardware.xml:90
 #, no-c-format
-msgid "ixp4xx"
+msgid "Intel IOP32x"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:92
+#: hardware.xml:91
 #, no-c-format
-msgid "Marvell Orion"
+msgid "iop32x"
 msgstr ""
 
 #. Tag: entry
 #: hardware.xml:93
 #, no-c-format
-msgid "orion5x"
+msgid "Intel IXP4xx"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:95
+#: hardware.xml:94
 #, no-c-format
-msgid "<entry>Versatile</entry>"
+msgid "ixp4xx"
 msgstr ""
 
 #. Tag: entry
 #: hardware.xml:96
 #, no-c-format
-msgid "versatile"
+msgid "Marvell Orion"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:100
+#: hardware.xml:97
 #, no-c-format
-msgid "HP PA-RISC"
+msgid "orion5x"
 msgstr ""
 
 #. Tag: entry
 #: hardware.xml:101
 #, no-c-format
-msgid "hppa"
+msgid "HP PA-RISC"
 msgstr ""
 
 #. Tag: entry
 #: hardware.xml:102
 #, no-c-format
-msgid "PA-RISC 1.1"
+msgid "hppa"
 msgstr ""
 
 #. Tag: entry
 #: hardware.xml:103
 #, no-c-format
+msgid "PA-RISC 1.1"
+msgstr ""
+
+#. Tag: entry
+#: hardware.xml:104
+#, no-c-format
 msgid "<entry>32</entry>"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:105
+#: hardware.xml:106
 #, no-c-format
 msgid "PA-RISC 2.0"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:106
+#: hardware.xml:107
 #, no-c-format
 msgid "<entry>64</entry>"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:110
+#: hardware.xml:111
 #, no-c-format
 msgid "Intel IA-64"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:111
+#: hardware.xml:112
 #, no-c-format
 msgid "ia64"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:117
+#: hardware.xml:118
 #, no-c-format
 msgid "MIPS (big endian)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:118
+#: hardware.xml:119
 #, no-c-format
 msgid "mips"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:119
+#: hardware.xml:120
 #, no-c-format
 msgid "SGI IP22 (Indy/Indigo 2)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:120
+#: hardware.xml:121
 #, no-c-format
 msgid "r4k-ip22"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:122
+#: hardware.xml:123
 #, no-c-format
 msgid "SGI IP32 (O2)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:123
+#: hardware.xml:124
 #, no-c-format
 msgid "r5k-ip32"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:125 hardware.xml:144
+#: hardware.xml:126 hardware.xml:145
 #, no-c-format
 msgid "MIPS Malta (32 bit)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:126 hardware.xml:145
+#: hardware.xml:127 hardware.xml:146
 #, no-c-format
 msgid "4kc-malta"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:128 hardware.xml:147
+#: hardware.xml:129 hardware.xml:148
 #, no-c-format
 msgid "MIPS Malta (64 bit)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:129 hardware.xml:148
+#: hardware.xml:130 hardware.xml:149
 #, no-c-format
 msgid "5kc-malta"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:131 hardware.xml:150
+#: hardware.xml:132 hardware.xml:151
 #, no-c-format
 msgid "Broadcom BCM91250A (SWARM)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:132 hardware.xml:151
+#: hardware.xml:133 hardware.xml:152
 #, no-c-format
 msgid "sb1-bcm91250a"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:134 hardware.xml:153
+#: hardware.xml:135 hardware.xml:154
 #, no-c-format
 msgid "Broadcom BCM91480B (BigSur)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:135 hardware.xml:154
+#: hardware.xml:136 hardware.xml:155
 #, no-c-format
 msgid "sb1a-bcm91480b"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:139
+#: hardware.xml:140
 #, no-c-format
 msgid "MIPS (little endian)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:140
+#: hardware.xml:141
 #, no-c-format
 msgid "mipsel"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:141
+#: hardware.xml:142
 #, no-c-format
 msgid "Cobalt"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:142
+#: hardware.xml:143
 #, no-c-format
 msgid "cobalt"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:158
+#: hardware.xml:159
 #, no-c-format
 msgid "Motorola 680x0"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:159
+#: hardware.xml:160
 #, no-c-format
 msgid "m68k"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:160
+#: hardware.xml:161
 #, no-c-format
 msgid "Atari"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:161
+#: hardware.xml:162
 #, no-c-format
 msgid "atari"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:163
+#: hardware.xml:164
 #, no-c-format
 msgid "Amiga"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:164
+#: hardware.xml:165
 #, no-c-format
 msgid "amiga"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:166
+#: hardware.xml:167
 #, no-c-format
 msgid "68k Macintosh"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:167
+#: hardware.xml:168
 #, no-c-format
 msgid "<entry>mac</entry>"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:169
+#: hardware.xml:170
 #, no-c-format
 msgid "<entry>VME</entry>"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:170
+#: hardware.xml:171
 #, no-c-format
 msgid "bvme6000"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:172
+#: hardware.xml:173
 #, no-c-format
 msgid "mvme147"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:174
+#: hardware.xml:175
 #, no-c-format
 msgid "mvme16x"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:178
-#, no-c-format
-msgid "IBM/Motorola PowerPC"
-msgstr ""
-
-#. Tag: entry
 #: hardware.xml:179
 #, no-c-format
-msgid "<entry>powerpc</entry>"
+msgid "IBM/Motorola PowerPC"
 msgstr ""
 
 #. Tag: entry
 #: hardware.xml:180
 #, no-c-format
-msgid "CHRP"
+msgid "<entry>powerpc</entry>"
 msgstr ""
 
 #. Tag: entry
 #: hardware.xml:181
 #, no-c-format
-msgid "chrp"
-msgstr ""
-
-#. Tag: entry
-#: hardware.xml:183
-#, no-c-format
 msgid "PowerMac"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:184
+#: hardware.xml:182
 #, no-c-format
 msgid "pmac"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:186
+#: hardware.xml:184
 #, no-c-format
 msgid "PReP"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:187
+#: hardware.xml:185
 #, no-c-format
-msgid "<entry>prep</entry>"
+msgid "prep"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:191
+#: hardware.xml:189
 #, no-c-format
 msgid "Sun SPARC"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:192
+#: hardware.xml:190
 #, no-c-format
 msgid "sparc"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:193
+#: hardware.xml:191
 #, no-c-format
 msgid "<entry>sun4u</entry>"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:194
+#: hardware.xml:192
 #, no-c-format
 msgid "sparc64"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:196
+#: hardware.xml:194
 #, no-c-format
 msgid "<entry>sun4v</entry>"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:200
+#: hardware.xml:198
 #, no-c-format
 msgid "IBM S/390"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:201
+#: hardware.xml:199
 #, no-c-format
 msgid "s390"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:202
+#: hardware.xml:200
 #, no-c-format
 msgid "IPL from VM-reader and DASD"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:203
+#: hardware.xml:201
 #, no-c-format
 msgid "generic"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:205
+#: hardware.xml:203
 #, no-c-format
 msgid "IPL from tape"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:206
+#: hardware.xml:204
 #, no-c-format
 msgid "tape"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:211
+#: hardware.xml:209
 #, no-c-format
 msgid "This document covers installation for the <emphasis>&arch-title;</emphasis> architecture. 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:219
+#: hardware.xml:217
 #, no-c-format
 msgid "This is the first official release of &debian; 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. 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:241 hardware.xml:700 hardware.xml:736 hardware.xml:840 hardware.xml:859 hardware.xml:944 hardware.xml:986 hardware.xml:1060 hardware.xml:1132
+#: hardware.xml:239 hardware.xml:698 hardware.xml:734 hardware.xml:838 hardware.xml:857 hardware.xml:939 hardware.xml:981 hardware.xml:1055 hardware.xml:1127
 #, no-c-format
 msgid "CPU, Main Boards, and Video Support"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:242
+#: hardware.xml:240
 #, no-c-format
 msgid "Complete information regarding supported DEC Alphas can be found at <ulink url=\"&url-alpha-howto;\">Linux Alpha HOWTO</ulink>. The purpose of this section is to describe the systems supported by the boot disks."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:249
+#: hardware.xml:247
 #, no-c-format
 msgid "Alpha machines are subdivided into different system types because there are a number of generations of motherboard and supporting chipsets. Different systems (<quote>sub-architectures</quote>) often have radically different engineering and capabilities. Therefore, the process of installing and, more to the point, booting, can vary from system to system."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:257
+#: hardware.xml:255
 #, no-c-format
 msgid "The following table lists the system types supported by the Debian installation system. The table also indicates the <emphasis>code name</emphasis> for these system types. You'll need to know this code name when you actually begin the installation process:"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:274
+#: hardware.xml:272
 #, no-c-format
 msgid "Hardware Type"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:275
+#: hardware.xml:273
 #, no-c-format
 msgid "Aliases"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:275
+#: hardware.xml:273
 #, no-c-format
 msgid "MILO image"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:281
+#: hardware.xml:279
 #, no-c-format
 msgid "ALCOR"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:282
+#: hardware.xml:280
 #, no-c-format
 msgid "AlphaStation 500 5/266.300"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:283
+#: hardware.xml:281
 #, no-c-format
 msgid "Maverick"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:284 hardware.xml:288 hardware.xml:292
+#: hardware.xml:282 hardware.xml:286 hardware.xml:290
 #, no-c-format
 msgid "alcor"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:286
+#: hardware.xml:284
 #, no-c-format
 msgid "AlphaStation 500 5/333...500"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:287
+#: hardware.xml:285
 #, no-c-format
 msgid "Bret"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:290
+#: hardware.xml:288
 #, no-c-format
 msgid "AlphaStation 600/266...300"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:291
+#: hardware.xml:289
 #, no-c-format
 msgid "Alcor"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:294
+#: hardware.xml:292
 #, no-c-format
 msgid "AlphaStation 600/300...433"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:295
+#: hardware.xml:293
 #, no-c-format
 msgid "<entry>XLT</entry>"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:296
+#: hardware.xml:294
 #, no-c-format
 msgid "<entry>xlt</entry>"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:300
+#: hardware.xml:298
 #, no-c-format
 msgid "BOOK1"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:301
+#: hardware.xml:299
 #, no-c-format
 msgid "AlphaBook1 (laptop)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:302
+#: hardware.xml:300
 #, no-c-format
 msgid "Alphabook1/Burns"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:303
+#: hardware.xml:301
 #, no-c-format
 msgid "book1"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:307
+#: hardware.xml:305
 #, no-c-format
 msgid "AVANTI"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:308
+#: hardware.xml:306
 #, no-c-format
 msgid "AlphaStation 200 4/100...166"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:309
+#: hardware.xml:307
 #, no-c-format
 msgid "Mustang"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:310 hardware.xml:314 hardware.xml:318 hardware.xml:322 hardware.xml:326 hardware.xml:330 hardware.xml:334 hardware.xml:338
+#: hardware.xml:308 hardware.xml:312 hardware.xml:316 hardware.xml:320 hardware.xml:324 hardware.xml:328 hardware.xml:332 hardware.xml:336
 #, no-c-format
 msgid "avanti"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:312
+#: hardware.xml:310
 #, no-c-format
 msgid "AlphaStation 200 4/233"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:313
+#: hardware.xml:311
 #, no-c-format
 msgid "Mustang+"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:316
+#: hardware.xml:314
 #, no-c-format
 msgid "AlphaStation 205 4/133...333"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:317
+#: hardware.xml:315
 #, no-c-format
 msgid "<entry>LX3</entry>"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:320
+#: hardware.xml:318
 #, no-c-format
 msgid "AlphaStation 250 4/300"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:321
+#: hardware.xml:319
 #, no-c-format
 msgid "<entry>M3+</entry>"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:324
+#: hardware.xml:322
 #, no-c-format
 msgid "AlphaStation 255 4/133...333"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:325
+#: hardware.xml:323
 #, no-c-format
 msgid "LX3+"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:328
+#: hardware.xml:326
 #, no-c-format
 msgid "AlphaStation 300 4/266"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:329
+#: hardware.xml:327
 #, no-c-format
 msgid "Melmac"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:332
+#: hardware.xml:330
 #, no-c-format
 msgid "AlphaStation 400 4/166"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:333
+#: hardware.xml:331
 #, no-c-format
 msgid "Chinet"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:336
+#: hardware.xml:334
 #, no-c-format
 msgid "AlphaStation 400 4/233...300"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:337
+#: hardware.xml:335
 #, no-c-format
 msgid "Avanti"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:342 hardware.xml:355 hardware.xml:356
+#: hardware.xml:340 hardware.xml:353 hardware.xml:354
 #, no-c-format
 msgid "EB164"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:343
+#: hardware.xml:341
 #, no-c-format
 msgid "AlphaPC164"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:344
+#: hardware.xml:342
 #, no-c-format
 msgid "PC164"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:345
+#: hardware.xml:343
 #, no-c-format
 msgid "pc164"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:347
+#: hardware.xml:345
 #, no-c-format
 msgid "AlphaPC164-LX"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:348
+#: hardware.xml:346
 #, no-c-format
 msgid "LX164"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:349
+#: hardware.xml:347
 #, no-c-format
 msgid "lx164"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:351
+#: hardware.xml:349
 #, no-c-format
 msgid "AlphaPC164-SX"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:352
+#: hardware.xml:350
 #, no-c-format
 msgid "SX164"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:353
+#: hardware.xml:351
 #, no-c-format
 msgid "sx164"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:357
+#: hardware.xml:355
 #, no-c-format
 msgid "eb164"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:361 hardware.xml:370 hardware.xml:371
+#: hardware.xml:359 hardware.xml:368 hardware.xml:369
 #, no-c-format
 msgid "EB64+"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:362
+#: hardware.xml:360
 #, no-c-format
 msgid "AlphaPC64"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:363 hardware.xml:367
+#: hardware.xml:361 hardware.xml:365
 #, no-c-format
 msgid "Cabriolet"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:364 hardware.xml:368
+#: hardware.xml:362 hardware.xml:366
 #, no-c-format
 msgid "cabriolet"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:366
+#: hardware.xml:364
 #, no-c-format
 msgid "AlphaPCI64"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:372
+#: hardware.xml:370
 #, no-c-format
 msgid "eb64p"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:376 hardware.xml:377 hardware.xml:378
+#: hardware.xml:374 hardware.xml:375 hardware.xml:376
 #, no-c-format
 msgid "EB66"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:379
+#: hardware.xml:377
 #, no-c-format
 msgid "eb66"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:381 hardware.xml:382
+#: hardware.xml:379 hardware.xml:380
 #, no-c-format
 msgid "EB66+"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:383
+#: hardware.xml:381
 #, no-c-format
 msgid "eb66p"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:387
+#: hardware.xml:385
 #, no-c-format
 msgid "JENSEN"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:388
+#: hardware.xml:386
 #, no-c-format
 msgid "DEC 2000 Model 300(S)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:389 hardware.xml:397
+#: hardware.xml:387 hardware.xml:395
 #, no-c-format
 msgid "Jensen"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:390 hardware.xml:394 hardware.xml:398 hardware.xml:459 hardware.xml:463 hardware.xml:481 hardware.xml:485 hardware.xml:489 hardware.xml:493 hardware.xml:497 hardware.xml:501 hardware.xml:505 hardware.xml:519 hardware.xml:523 hardware.xml:527 hardware.xml:531 hardware.xml:535 hardware.xml:569 hardware.xml:573 hardware.xml:577 hardware.xml:581 hardware.xml:595 hardware.xml:599 hardware.xml:603 hardware.xml:607 hardware.xml:614 hardware.xml:618 hardware.xml:622 hardware.xml:626 hardware.xml:630 hardware.xml:634 hardware.xml:638 hardware.xml:642 hardware.xml:646 hardware.xml:650 hardware.xml:654 hardware.xml:658 hardware.xml:662 hardware.xml:669 hardware.xml:673
+#: hardware.xml:388 hardware.xml:392 hardware.xml:396 hardware.xml:457 hardware.xml:461 hardware.xml:479 hardware.xml:483 hardware.xml:487 hardware.xml:491 hardware.xml:495 hardware.xml:499 hardware.xml:503 hardware.xml:517 hardware.xml:521 hardware.xml:525 hardware.xml:529 hardware.xml:533 hardware.xml:567 hardware.xml:571 hardware.xml:575 hardware.xml:579 hardware.xml:593 hardware.xml:597 hardware.xml:601 hardware.xml:605 hardware.xml:612 hardware.xml:616 hardware.xml:620 hardware.xml:624 hardware.xml:628 hardware.xml:632 hardware.xml:636 hardware.xml:640 hardware.xml:644 hardware.xml:648 hardware.xml:652 hardware.xml:656 hardware.xml:660 hardware.xml:667 hardware.xml:671
 #, no-c-format
 msgid "<entry>N/A</entry>"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:392
+#: hardware.xml:390
 #, no-c-format
 msgid "DEC 2000 Model 500"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:393
+#: hardware.xml:391
 #, no-c-format
 msgid "Culzen"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:396
+#: hardware.xml:394
 #, no-c-format
 msgid "DECpc 150"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:402
+#: hardware.xml:400
 #, no-c-format
 msgid "MIATA"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:403
+#: hardware.xml:401
 #, no-c-format
 msgid "Personal WorkStation 433a"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:404 hardware.xml:408 hardware.xml:412 hardware.xml:416 hardware.xml:420 hardware.xml:424 hardware.xml:428 hardware.xml:432
+#: hardware.xml:402 hardware.xml:406 hardware.xml:410 hardware.xml:414 hardware.xml:418 hardware.xml:422 hardware.xml:426 hardware.xml:430
 #, no-c-format
 msgid "Miata"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:405 hardware.xml:409 hardware.xml:413 hardware.xml:417 hardware.xml:421 hardware.xml:425 hardware.xml:429 hardware.xml:433
+#: hardware.xml:403 hardware.xml:407 hardware.xml:411 hardware.xml:415 hardware.xml:419 hardware.xml:423 hardware.xml:427 hardware.xml:431
 #, no-c-format
 msgid "miata"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:407
+#: hardware.xml:405
 #, no-c-format
 msgid "Personal WorkStation 433au"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:411
+#: hardware.xml:409
 #, no-c-format
 msgid "Personal WorkStation 466au"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:415
+#: hardware.xml:413
 #, no-c-format
 msgid "Personal WorkStation 500a"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:419
+#: hardware.xml:417
 #, no-c-format
 msgid "Personal WorkStation 500au"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:423
+#: hardware.xml:421
 #, no-c-format
 msgid "Personal WorkStation 550au"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:427
+#: hardware.xml:425
 #, no-c-format
 msgid "Personal WorkStation 600a"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:431
+#: hardware.xml:429
 #, no-c-format
 msgid "Personal WorkStation 600au"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:437
+#: hardware.xml:435
 #, no-c-format
 msgid "MIKASA"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:438
+#: hardware.xml:436
 #, no-c-format
 msgid "AlphaServer 1000 4/200"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:439
+#: hardware.xml:437
 #, no-c-format
 msgid "Mikasa"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:440 hardware.xml:444 hardware.xml:448 hardware.xml:452
+#: hardware.xml:438 hardware.xml:442 hardware.xml:446 hardware.xml:450
 #, no-c-format
 msgid "mikasa"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:442
+#: hardware.xml:440
 #, no-c-format
 msgid "AlphaServer 1000 4/233..266"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:443
+#: hardware.xml:441
 #, no-c-format
 msgid "Mikasa+"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:446 hardware.xml:450
+#: hardware.xml:444 hardware.xml:448
 #, no-c-format
 msgid "AlphaServer 1000 5/300"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:447
+#: hardware.xml:445
 #, no-c-format
 msgid "Mikasa-Pinnacle"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:451
+#: hardware.xml:449
 #, no-c-format
 msgid "Mikasa-Primo"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:456
+#: hardware.xml:454
 #, no-c-format
 msgid "NAUTILUS"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:457
+#: hardware.xml:455
 #, no-c-format
 msgid "UP1000"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:458
+#: hardware.xml:456
 #, no-c-format
 msgid "Nautilus"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:461
+#: hardware.xml:459
 #, no-c-format
 msgid "UP1100"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:462
+#: hardware.xml:460
 #, no-c-format
 msgid "Galaxy-Train/Nautilus Jr."
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:467
+#: hardware.xml:465
 #, no-c-format
 msgid "NONAME"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:468
+#: hardware.xml:466
 #, no-c-format
 msgid "AXPpci33"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:469
+#: hardware.xml:467
 #, no-c-format
 msgid "Noname"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:470 hardware.xml:474
+#: hardware.xml:468 hardware.xml:472
 #, no-c-format
 msgid "noname"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:472
+#: hardware.xml:470
 #, no-c-format
 msgid "<entry>UDB</entry>"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:473
+#: hardware.xml:471
 #, no-c-format
 msgid "Multia"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:478
+#: hardware.xml:476
 #, no-c-format
 msgid "NORITAKE"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:479
+#: hardware.xml:477
 #, no-c-format
 msgid "AlphaServer 1000A 4/233...266"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:480
+#: hardware.xml:478
 #, no-c-format
 msgid "Noritake"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:483
+#: hardware.xml:481
 #, no-c-format
 msgid "AlphaServer 1000A 5/300"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:484
+#: hardware.xml:482
 #, no-c-format
 msgid "Noritake-Pinnacle"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:487
+#: hardware.xml:485
 #, no-c-format
 msgid "AlphaServer 1000A 5/333...500"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:488
+#: hardware.xml:486
 #, no-c-format
 msgid "Noritake-Primo"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:491
+#: hardware.xml:489
 #, no-c-format
 msgid "AlphaServer 800 5/333...500"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:492 hardware.xml:500 hardware.xml:504
+#: hardware.xml:490 hardware.xml:498 hardware.xml:502
 #, no-c-format
 msgid "Corelle"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:495
+#: hardware.xml:493
 #, no-c-format
 msgid "AlphaStation 600 A"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:496
+#: hardware.xml:494
 #, no-c-format
 msgid "Alcor-Primo"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:499
+#: hardware.xml:497
 #, no-c-format
 msgid "Digital Server 3300"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:503
+#: hardware.xml:501
 #, no-c-format
 msgid "Digital Server 3300R"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:509
+#: hardware.xml:507
 #, no-c-format
 msgid "PLATFORM 2000"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:510 hardware.xml:511
+#: hardware.xml:508 hardware.xml:509
 #, no-c-format
 msgid "<entry>P2K</entry>"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:512
+#: hardware.xml:510
 #, no-c-format
 msgid "<entry>p2k</entry>"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:516
+#: hardware.xml:514
 #, no-c-format
 msgid "RAWHIDE"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:517
+#: hardware.xml:515
 #, no-c-format
 msgid "AlphaServer 1200 5/xxx"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:518 hardware.xml:530
+#: hardware.xml:516 hardware.xml:528
 #, no-c-format
 msgid "Tincup/DaVinci"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:521
+#: hardware.xml:519
 #, no-c-format
 msgid "AlphaServer 4000 5/xxx"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:522
+#: hardware.xml:520
 #, no-c-format
 msgid "Wrangler/Durango"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:525
+#: hardware.xml:523
 #, no-c-format
 msgid "AlphaServer 4100 5/xxx"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:526 hardware.xml:534
+#: hardware.xml:524 hardware.xml:532
 #, no-c-format
 msgid "Dodge"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:529
+#: hardware.xml:527
 #, no-c-format
 msgid "Digital Server 5300"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:533
+#: hardware.xml:531
 #, no-c-format
 msgid "Digital Server 7300"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:539
+#: hardware.xml:537
 #, no-c-format
 msgid "RUFFIAN"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:540
+#: hardware.xml:538
 #, no-c-format
 msgid "DeskStation AlphaPC164-UX"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:541 hardware.xml:545 hardware.xml:549 hardware.xml:553 hardware.xml:557 hardware.xml:561
+#: hardware.xml:539 hardware.xml:543 hardware.xml:547 hardware.xml:551 hardware.xml:555 hardware.xml:559
 #, no-c-format
 msgid "Ruffian"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:542 hardware.xml:546 hardware.xml:550 hardware.xml:554 hardware.xml:558 hardware.xml:562
+#: hardware.xml:540 hardware.xml:544 hardware.xml:548 hardware.xml:552 hardware.xml:556 hardware.xml:560
 #, no-c-format
 msgid "ruffian"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:544
+#: hardware.xml:542
 #, no-c-format
 msgid "DeskStation RPL164-2"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:548
+#: hardware.xml:546
 #, no-c-format
 msgid "DeskStation RPL164-4"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:552
+#: hardware.xml:550
 #, no-c-format
 msgid "DeskStation RPX164-2"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:556
+#: hardware.xml:554
 #, no-c-format
 msgid "DeskStation RPX164-4"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:560
+#: hardware.xml:558
 #, no-c-format
 msgid "Samsung AlphaPC164-BX"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:566
+#: hardware.xml:564
 #, no-c-format
 msgid "SABLE"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:567
+#: hardware.xml:565
 #, no-c-format
 msgid "AlphaServer 2000 4/xxx"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:568
+#: hardware.xml:566
 #, no-c-format
 msgid "Demi-Sable"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:571
+#: hardware.xml:569
 #, no-c-format
 msgid "AlphaServer 2000 5/xxx"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:572
+#: hardware.xml:570
 #, no-c-format
 msgid "Demi-Gamma-Sable"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:575
+#: hardware.xml:573
 #, no-c-format
 msgid "AlphaServer 2100 4/xxx"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:576
+#: hardware.xml:574
 #, no-c-format
 msgid "Sable"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:579
+#: hardware.xml:577
 #, no-c-format
 msgid "AlphaServer 2100 5/xxx"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:580
+#: hardware.xml:578
 #, no-c-format
 msgid "Gamma-Sable"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:585
+#: hardware.xml:583
 #, no-c-format
 msgid "TAKARA"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:586
+#: hardware.xml:584
 #, no-c-format
 msgid "21164 PICMG SBC"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:587
+#: hardware.xml:585
 #, no-c-format
 msgid "Takara"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:588
+#: hardware.xml:586
 #, no-c-format
 msgid "takara"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:592
+#: hardware.xml:590
 #, no-c-format
 msgid "TITAN"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:593
+#: hardware.xml:591
 #, no-c-format
 msgid "AlphaServer DS15"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:594
+#: hardware.xml:592
 #, no-c-format
 msgid "HyperBrick2"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:597
+#: hardware.xml:595
 #, no-c-format
 msgid "AlphaServer DS25"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:598
+#: hardware.xml:596
 #, no-c-format
 msgid "Granite"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:601
+#: hardware.xml:599
 #, no-c-format
 msgid "AlphaServer ES45"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:602
+#: hardware.xml:600
 #, no-c-format
 msgid "Privateer"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:605 hardware.xml:644 hardware.xml:648
+#: hardware.xml:603 hardware.xml:642 hardware.xml:646
 #, no-c-format
 msgid "UNKNOWN"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:606
+#: hardware.xml:604
 #, no-c-format
 msgid "Yukon"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:611
+#: hardware.xml:609
 #, no-c-format
 msgid "TSUNAMI"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:612
+#: hardware.xml:610
 #, no-c-format
 msgid "AlphaServer DS10"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:613 hardware.xml:661
+#: hardware.xml:611 hardware.xml:659
 #, no-c-format
 msgid "Webbrick"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:616
+#: hardware.xml:614
 #, no-c-format
 msgid "AlphaServer DS10L"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:617
+#: hardware.xml:615
 #, no-c-format
 msgid "Slate"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:620
+#: hardware.xml:618
 #, no-c-format
 msgid "AlphaServer DS20"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:621
+#: hardware.xml:619
 #, no-c-format
 msgid "Catamaran/Goldrush"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:624
+#: hardware.xml:622
 #, no-c-format
 msgid "AlphaServer DS20E"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:625
+#: hardware.xml:623
 #, no-c-format
 msgid "Goldrack"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:628
+#: hardware.xml:626
 #, no-c-format
 msgid "AlphaServer DS20L"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:629
+#: hardware.xml:627
 #, no-c-format
 msgid "Shark"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:632
+#: hardware.xml:630
 #, no-c-format
 msgid "AlphaServer ES40"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:633
+#: hardware.xml:631
 #, no-c-format
 msgid "Clipper"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:636 hardware.xml:637
+#: hardware.xml:634 hardware.xml:635
 #, no-c-format
 msgid "DP264"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:640
+#: hardware.xml:638
 #, no-c-format
 msgid "SMARTengine 21264 PCI/ISA SBC"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:641
+#: hardware.xml:639
 #, no-c-format
 msgid "Eiger"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:645
+#: hardware.xml:643
 #, no-c-format
 msgid "Warhol"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:649
+#: hardware.xml:647
 #, no-c-format
 msgid "Windjammer"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:652
+#: hardware.xml:650
 #, no-c-format
 msgid "UP2000"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:653
+#: hardware.xml:651
 #, no-c-format
 msgid "Swordfish"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:656
+#: hardware.xml:654
 #, no-c-format
 msgid "XP1000"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:657
+#: hardware.xml:655
 #, no-c-format
 msgid "Monet/Brisbane"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:660
+#: hardware.xml:658
 #, no-c-format
 msgid "XP900"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:666
+#: hardware.xml:664
 #, no-c-format
 msgid "WILDFIRE"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:667
+#: hardware.xml:665
 #, no-c-format
 msgid "AlphaServer GS160"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:668 hardware.xml:672
+#: hardware.xml:666 hardware.xml:670
 #, no-c-format
 msgid "Wildfire"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:671
+#: hardware.xml:669
 #, no-c-format
 msgid "AlphaServer GS320"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:677 hardware.xml:679
+#: hardware.xml:675 hardware.xml:677
 #, no-c-format
 msgid "<entry>XL</entry>"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:678
+#: hardware.xml:676
 #, no-c-format
 msgid "XL-233...266"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:680
+#: hardware.xml:678
 #, no-c-format
 msgid "<entry>xl</entry>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:685
+#: hardware.xml:683
 #, no-c-format
 msgid "It is believed that Debian &releasename; supports installing on all alpha sub-architectures with the exception of the ARC-only Ruffian and XL sub-architectures and the Titan subarchitecture, which requires a change to the kernel compile options."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:701 hardware.xml:860
+#: hardware.xml:699 hardware.xml:858
 #, 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:709 hardware.xml:868 hardware.xml:1033
+#: hardware.xml:707 hardware.xml:866 hardware.xml:1028
 #, no-c-format
 msgid "<title>CPU</title>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:710
+#: hardware.xml:708
 #, no-c-format
 msgid "Both AMD64 and Intel EM64T processors are supported."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:738
+#: hardware.xml:736
 #, 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:747
+#: hardware.xml:745
 #, 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:755
+#: hardware.xml:753
 #, no-c-format
 msgid "The supported platforms are:"
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:762
+#: hardware.xml:760
 #, no-c-format
 msgid "Netwinder"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:763
+#: hardware.xml:761
 #, no-c-format
 msgid "This is actually the name for the group of machines based upon the StrongARM 110 CPU and Intel 21285 Northbridge (also known as Footbridge). It comprises of machines like: Netwinder (possibly one of the most common ARM boxes), CATS (also known as the EB110ATX), EBSA 285 and Compaq personal server (cps, aka skiff)."
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:776
+#: hardware.xml:774
 #, no-c-format
 msgid "IOP32x"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:777
+#: hardware.xml:775
 #, 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:790
+#: hardware.xml:788
 #, no-c-format
 msgid "IXP4xx"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:791
+#: hardware.xml:789
 #, no-c-format
 msgid "The IXP4xx platform is based on Intel's XScale ARM core. Currently, only one IXP4xx based system is supported, the Linksys NSLU2. The Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) is a small device which allows you to easily provide storage via the network. It comes with an Ethernet connection and two USB ports to which hard drives can be connected. There is an external site with <ulink url=\"&url-arm-cyrius-nslu2;\">installation instructions</ulink>."
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:805
+#: hardware.xml:803
 #, no-c-format
 msgid "Orion5x"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:806
+#: hardware.xml:804
 #, 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-mv2120;\">HP mv2120</ulink>, <ulink url=\"&url-arm-cyrius-qnap;\">QNAP Turbo Station</ulink> (TS-109, TS-209 and TS-409)."
 msgstr ""
 
 #. Tag: term
-#: hardware.xml:821
+#: hardware.xml:819
 #, no-c-format
 msgid "<term>Versatile</term>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:822
+#: hardware.xml:820
 #, 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:841
+#: hardware.xml:839
 #, 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:869
+#: hardware.xml:867
 #, 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:877
+#: hardware.xml:874
 #, no-c-format
-msgid "If your system has a 64-bit processor from the AMD64 or Intel EM64T families, you will probably want to use the installer for the amd64 architecture instead of the installer for the (32-bit) i386 architecture."
+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:884
+#: hardware.xml:907
 #, 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>."
+msgid "If your system has a 64-bit processor from the AMD64 or Intel EM64T 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:921
+#: hardware.xml:916
 #, no-c-format
 msgid "I/O Bus"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:922
+#: hardware.xml:917
 #, 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, 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:945
+#: hardware.xml:940
 #, no-c-format
 msgid "Complete information concerning supported M68000 based (<emphasis>&architecture;</emphasis>) systems can be found at the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. This section merely outlines the basics."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:952
+#: hardware.xml:947
 #, no-c-format
 msgid "The &architecture; port of Linux runs on any 680x0 with a PMMU (Paged Memory Management Unit) and a FPU (floating-point unit). This includes the 68020 with an external 68851 PMMU, the 68030, and better, and excludes the <quote>EC</quote> line of 680x0 processors. See the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink> for complete details."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:960
+#: hardware.xml:955
 #, no-c-format
 msgid "There are four major supported <emphasis>&architecture;</emphasis> flavors: Amiga, Atari, Macintosh and VME machines. Amiga and Atari were the first two systems to which Linux was ported; in keeping, they are also the two most well-supported Debian ports. The Macintosh line is supported incompletely, both by Debian and by the Linux kernel; see <ulink url=\"&url-m68k-mac;\">Linux m68k for Macintosh</ulink> for project status and supported hardware. The BVM and Motorola single board VMEbus computers are the most recent addition to the list of machines supported by Debian. Ports to other &architecture; architectures, such as the Sun3 architecture and NeXT black box, are underway but not yet supported by Debian."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:987
+#: hardware.xml:982
 #, 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> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </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:1034
+#: hardware.xml:1029
 #, 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. The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with two cores which are supported in SMP mode by this installer. Similarly, the BCM91480B evaluation board contains an SB1A 1480 chip with four cores which are supported in SMP mode."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1044
+#: hardware.xml:1039
 #, 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:1061
+#: hardware.xml:1056
 #, 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 Qube 2700 (Qube1), 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> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </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:1102
+#: hardware.xml:1097
 #, no-c-format
 msgid "CPU/Machine types"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1104
+#: hardware.xml:1099
 #, no-c-format
 msgid "All MIPS based Cobalt machines are supported."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1108
+#: hardware.xml:1103
 #, no-c-format
 msgid "The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with two cores which are supported in SMP mode by this installer. Similarly, the BCM91480B evaluation board contains an SB1A 1480 chip with four cores which are supported in SMP mode."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1118
+#: hardware.xml:1113
 #, no-c-format
 msgid "Supported console options"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1119
+#: hardware.xml:1114
 #, no-c-format
 msgid "Both Cobalt and Broadcom BCM91250A/BCM91480B use 115200 bps."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1133
-#, no-c-format
-msgid "There are four major supported <emphasis>&architecture;</emphasis> subarchitectures: PMac (Power-Macintosh or PowerMac), PReP, APUS (Amiga Power-UP System), and CHRP machines. Each subarchitecture has its own boot methods. In addition, there are four different kernel flavours, supporting different CPU variants."
-msgstr ""
-
-#. Tag: para
-#: hardware.xml:1141
+#: hardware.xml:1128
 #, no-c-format
-msgid "Ports to other <emphasis>&architecture;</emphasis> architectures, such as the Be-Box and MBX architecture, are underway but not yet supported by Debian. We may have a 64-bit port in the future."
+msgid "For &debian; &release; only the PMac (Power-Macintosh or PowerMac) and PreP subarchitectures are supported."
 msgstr ""
 
 #. Tag: title
@@ -1883,7 +1871,7 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1151
 #, no-c-format
-msgid "There are four flavours of the powerpc kernel in Debian, based on the CPU type:"
+msgid "There are two flavours of the powerpc kernel in Debian, based on the CPU type:"
 msgstr ""
 
 #. Tag: term
@@ -1928,1197 +1916,1173 @@ msgstr ""
 msgid "Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 architecture, and use this kernel flavour."
 msgstr ""
 
-#. Tag: term
-#: hardware.xml:1194
-#, no-c-format
-msgid "<term>prep</term>"
-msgstr ""
-
-#. Tag: para
-#: hardware.xml:1195
-#, no-c-format
-msgid "This kernel flavour supports the PReP subarchitecture."
-msgstr ""
-
-#. Tag: term
-#: hardware.xml:1203
-#, no-c-format
-msgid "apus"
-msgstr ""
-
-#. Tag: para
-#: hardware.xml:1204
-#, no-c-format
-msgid "This kernel flavour supports the Amiga Power-UP System, though it is currently disabled."
-msgstr ""
-
 #. Tag: title
-#: hardware.xml:1217
+#: hardware.xml:1219
 #, no-c-format
 msgid "Power Macintosh (pmac) subarchitecture"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1219
+#: hardware.xml:1221
 #, 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:1226
+#: hardware.xml:1228
 #, 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:1234
+#: hardware.xml:1236
 #, 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:1242
+#: hardware.xml:1244
 #, 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:1258 hardware.xml:1393 hardware.xml:1437 hardware.xml:1466
+#: hardware.xml:1260 hardware.xml:1395 hardware.xml:1439 hardware.xml:1468
 #, no-c-format
 msgid "Model Name/Number"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1259
+#: hardware.xml:1261
 #, no-c-format
 msgid "Generation"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1265
+#: hardware.xml:1267
 #, no-c-format
 msgid "Apple"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1266
+#: hardware.xml:1268
 #, no-c-format
 msgid "iMac Bondi Blue, 5 Flavors, Slot Loading"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1267 hardware.xml:1270 hardware.xml:1273 hardware.xml:1276 hardware.xml:1279 hardware.xml:1282 hardware.xml:1285 hardware.xml:1288 hardware.xml:1291 hardware.xml:1294 hardware.xml:1297 hardware.xml:1300 hardware.xml:1303 hardware.xml:1306 hardware.xml:1309 hardware.xml:1312
+#: hardware.xml:1269 hardware.xml:1272 hardware.xml:1275 hardware.xml:1278 hardware.xml:1281 hardware.xml:1284 hardware.xml:1287 hardware.xml:1290 hardware.xml:1293 hardware.xml:1296 hardware.xml:1299 hardware.xml:1302 hardware.xml:1305 hardware.xml:1308 hardware.xml:1311 hardware.xml:1314
 #, no-c-format
 msgid "NewWorld"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1269
+#: hardware.xml:1271
 #, no-c-format
 msgid "iMac Summer 2000, Early 2001"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1272
+#: hardware.xml:1274
 #, no-c-format
 msgid "iMac G5"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1275
+#: hardware.xml:1277
 #, no-c-format
 msgid "iBook, iBook SE, iBook Dual USB"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1278
+#: hardware.xml:1280
 #, no-c-format
 msgid "iBook2"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1281
+#: hardware.xml:1283
 #, no-c-format
 msgid "iBook G4"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1284
+#: hardware.xml:1286
 #, no-c-format
 msgid "Power Macintosh Blue and White (B&amp;W) G3"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1287
+#: hardware.xml:1289
 #, no-c-format
 msgid "Power Macintosh G4 PCI, AGP, Cube"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1290
+#: hardware.xml:1292
 #, no-c-format
 msgid "Power Macintosh G4 Gigabit Ethernet"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1293
+#: hardware.xml:1295
 #, no-c-format
 msgid "Power Macintosh G4 Digital Audio, Quicksilver"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1296
+#: hardware.xml:1298
 #, no-c-format
 msgid "Power Macintosh G5"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1299
+#: hardware.xml:1301
 #, no-c-format
 msgid "PowerBook G3 FireWire Pismo (2000)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1302
+#: hardware.xml:1304
 #, no-c-format
 msgid "PowerBook G3 Lombard (1999)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1305
+#: hardware.xml:1307
 #, no-c-format
 msgid "PowerBook G4 Titanium"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1308
+#: hardware.xml:1310
 #, no-c-format
 msgid "PowerBook G4 Aluminum"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1311
+#: hardware.xml:1313
 #, no-c-format
 msgid "Xserve G5"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1314
+#: hardware.xml:1316
 #, no-c-format
 msgid "Performa 4400, 54xx, 5500"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1315 hardware.xml:1318 hardware.xml:1321 hardware.xml:1324 hardware.xml:1327 hardware.xml:1330 hardware.xml:1333 hardware.xml:1336 hardware.xml:1339 hardware.xml:1342 hardware.xml:1345 hardware.xml:1348 hardware.xml:1354 hardware.xml:1357 hardware.xml:1363 hardware.xml:1369 hardware.xml:1375
+#: hardware.xml:1317 hardware.xml:1320 hardware.xml:1323 hardware.xml:1326 hardware.xml:1329 hardware.xml:1332 hardware.xml:1335 hardware.xml:1338 hardware.xml:1341 hardware.xml:1344 hardware.xml:1347 hardware.xml:1350 hardware.xml:1356 hardware.xml:1359 hardware.xml:1365 hardware.xml:1371 hardware.xml:1377
 #, no-c-format
 msgid "OldWorld"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1317
+#: hardware.xml:1319
 #, no-c-format
 msgid "Performa 6360, 6400, 6500"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1320
+#: hardware.xml:1322
 #, no-c-format
 msgid "Power Macintosh 4400, 5400"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1323
+#: hardware.xml:1325
 #, no-c-format
 msgid "Power Macintosh 7200, 7300, 7500, 7600"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1326
+#: hardware.xml:1328
 #, no-c-format
 msgid "Power Macintosh 8200, 8500, 8600"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1329
+#: hardware.xml:1331
 #, no-c-format
 msgid "Power Macintosh 9500, 9600"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1332
+#: hardware.xml:1334
 #, no-c-format
 msgid "Power Macintosh (Beige) G3 Minitower"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1335
+#: hardware.xml:1337
 #, no-c-format
 msgid "Power Macintosh (Beige) Desktop, All-in-One"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1338
+#: hardware.xml:1340
 #, no-c-format
 msgid "PowerBook 2400, 3400, 3500"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1341
+#: hardware.xml:1343
 #, no-c-format
 msgid "PowerBook G3 Wallstreet (1998)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1344
+#: hardware.xml:1346
 #, no-c-format
 msgid "Twentieth Anniversary Macintosh"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1347
+#: hardware.xml:1349
 #, no-c-format
 msgid "Workgroup Server 7250, 7350, 8550, 9650, G3"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1352
+#: hardware.xml:1354
 #, no-c-format
 msgid "Power Computing"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1353
+#: hardware.xml:1355
 #, no-c-format
 msgid "PowerBase, PowerTower / Pro, PowerWave"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1356
+#: hardware.xml:1358
 #, no-c-format
 msgid "PowerCenter / Pro, PowerCurve"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1361
+#: hardware.xml:1363
 #, no-c-format
 msgid "UMAX"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1362
+#: hardware.xml:1364
 #, no-c-format
 msgid "C500, C600, J700, S900"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1367
+#: hardware.xml:1369
 #, no-c-format
 msgid "<entry>APS</entry>"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1368
+#: hardware.xml:1370
 #, no-c-format
 msgid "APS Tech M*Power 604e/2000"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1373 hardware.xml:1399
+#: hardware.xml:1375 hardware.xml:1401
 #, no-c-format
 msgid "Motorola"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1374
+#: hardware.xml:1376
 #, no-c-format
 msgid "Starmax 3000, 4000, 5000, 5500"
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1383
+#: hardware.xml:1385
 #, no-c-format
 msgid "PReP subarchitecture"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1400
+#: hardware.xml:1402
 #, no-c-format
 msgid "Firepower, PowerStack Series E, PowerStack II"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1402
+#: hardware.xml:1404
 #, no-c-format
 msgid "MPC 7xx, 8xx"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1404
+#: hardware.xml:1406
 #, no-c-format
 msgid "MTX, MTX+"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1406
+#: hardware.xml:1408
 #, no-c-format
 msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1408
+#: hardware.xml:1410
 #, no-c-format
 msgid "MCP(N)750"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1412 hardware.xml:1443
+#: hardware.xml:1414 hardware.xml:1445
 #, no-c-format
 msgid "IBM RS/6000"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1413
+#: hardware.xml:1415
 #, no-c-format
 msgid "40P, 43P"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1415
+#: hardware.xml:1417
 #, no-c-format
 msgid "Power 830/850/860 (6070, 6050)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1417
+#: hardware.xml:1419
 #, no-c-format
 msgid "6030, 7025, 7043"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1419
+#: hardware.xml:1421
 #, no-c-format
 msgid "p640"
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1427
+#: hardware.xml:1429
 #, no-c-format
-msgid "CHRP subarchitecture"
+msgid "CHRP subarchitecture (unsupported)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1444
+#: hardware.xml:1446
 #, no-c-format
 msgid "B50, 43P-150, 44P"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1447
+#: hardware.xml:1449
 #, no-c-format
 msgid "Genesi"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1448
+#: hardware.xml:1450
 #, no-c-format
 msgid "Pegasos I, Pegasos II"
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1456
+#: hardware.xml:1458
 #, no-c-format
-msgid "APUS subarchitecture"
+msgid "APUS subarchitecture (unsupported)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1472
+#: hardware.xml:1474
 #, no-c-format
 msgid "Amiga Power-UP Systems (APUS)"
 msgstr ""
 
 #. Tag: entry
-#: hardware.xml:1473
+#: hardware.xml:1475
 #, no-c-format
 msgid "A1200, A3000, A4000"
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1481
+#: hardware.xml:1483
 #, no-c-format
 msgid "Nubus PowerMac subarchitecture (unsupported)"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1483
+#: hardware.xml:1485
 #, 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:1520
+#: hardware.xml:1522
 #, no-c-format
 msgid "Non-PowerPC Macs"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1522
+#: hardware.xml:1524
 #, 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:1531
+#: hardware.xml:1533
 #, 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:1539
+#: hardware.xml:1541
 #, 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:1555
+#: hardware.xml:1557
 #, no-c-format
 msgid "S/390 and zSeries machine types"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1556
+#: hardware.xml:1558
 #, no-c-format
 msgid "Complete information regarding supported S/390 and zSeries machines can be found in IBM's Redbook <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> in chapter 2.1 or at the <ulink url=\"http://www-128.ibm.com/developerworks/linux/linux390/index.html\">zSeries page at the developerWorks</ulink>. In short, G5, Multiprise 3000, G6 and all zSeries are fully supported; Multiprise 2000, G3 and G4 machines are supported with IEEE floating point emulation and thus degraded performance."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1578
+#: hardware.xml:1580
 #, no-c-format
 msgid "CPU and Main Boards Support"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1579
+#: hardware.xml:1581
 #, 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:1590
+#: hardware.xml:1592
 #, no-c-format
 msgid "sun4, sun4c, sun4d, sun4m"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1592
+#: hardware.xml:1594
 #, 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:1599
+#: hardware.xml:1601
 #, 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:1609
+#: hardware.xml:1611
 #, no-c-format
 msgid "<term>sun4u</term>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1611
+#: hardware.xml:1613
 #, 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:1624
+#: hardware.xml:1626
 #, no-c-format
 msgid "<term>sun4v</term>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1626
+#: hardware.xml:1628
 #, 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:1637
+#: hardware.xml:1639
 #, 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:1646
-#, no-c-format
-msgid "Graphics Card Support"
-msgstr ""
-
-#. Tag: para
-#: hardware.xml:1647
-#, no-c-format
-msgid "You should be using a VGA-compatible display interface for the console terminal. Nearly every modern display card is compatible with VGA. Ancient standards such CGA, MDA, or HGA should also work, assuming you do not require X11 support. Note that X11 is not used during the installation process described in this document."
-msgstr ""
-
-#. Tag: para
-#: hardware.xml:1655
-#, no-c-format
-msgid "Debian's support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. Most AGP, PCI and PCIe video cards work under X.Org. Details on supported graphics buses, cards, monitors, 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:1664
-#, no-c-format
-msgid "The X.Org X Window System is only supported on the SGI Indy and the O2. The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available."
-msgstr ""
-
-#. Tag: para
-#: hardware.xml:1673
-#, no-c-format
-msgid "The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available."
-msgstr ""
-
-#. Tag: para
-#: hardware.xml:1680
-#, 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:1690
-#, 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:1707
+#: hardware.xml:1648
 #, no-c-format
 msgid "Laptops"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1708
+#: hardware.xml:1649
 #, no-c-format
-msgid "Laptops are also supported. Laptops are often specialized or contain proprietary hardware. To see if your particular laptop works well with GNU/Linux, see the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>"
+msgid "Laptops are also supported and nowadays most laptops work out of the box. In case a laptop contains specialized or proprietary hardware, some specific functions may 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:1719 hardware.xml:1741 hardware.xml:1761 hardware.xml:1784
+#: hardware.xml:1661 hardware.xml:1684 hardware.xml:1704 hardware.xml:1727
 #, no-c-format
 msgid "Multiple Processors"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1720
+#: hardware.xml:1662
 #, 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 was compiled with SMP support. This should not prevent installation, since the SMP kernel should boot on non-SMP systems; the kernel will simply cause a bit more overhead."
+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 SMP support. The standard kernel is also usable on non-SMP systems, but has a slight overhead which will cause a small reduction in performance. For normal system use this will hardly be noticable."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1728
+#: hardware.xml:1671
 #, no-c-format
 msgid "In order to optimize the kernel for single CPU systems, you'll have to replace the standard Debian kernel. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you disable SMP is to deselect <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1743
+#: hardware.xml:1686
 #, 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 was 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."
+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:1752
+#: hardware.xml:1695
 #, 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:1762
+#: hardware.xml:1705
 #, 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 the first CPU."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1771
+#: hardware.xml:1714
 #, no-c-format
 msgid "In order to take advantage of multiple processors, you'll have to replace the standard Debian kernel. 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."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1785
+#: hardware.xml:1728
 #, 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:1795
+#: hardware.xml:1738
 #, 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:1801
+#: hardware.xml:1744
 #, no-c-format
 msgid "You can also build your own customized kernel to support SMP. 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."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1818
+#: hardware.xml:1755
 #, no-c-format
-msgid "Installation Media"
+msgid "Graphics Card Support"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1820
+#: hardware.xml:1756
 #, no-c-format
-msgid "This section will help you determine which different media types you can use to install Debian. For example, if you have a floppy disk drive on your machine, it can be used 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."
+msgid "You should be using a VGA-compatible display interface for the console terminal. Nearly every modern display card is compatible with VGA. Ancient standards such CGA, MDA, or HGA should also work, assuming you do not require X11 support. Note that X11 is not used during the installation process described in this document."
 msgstr ""
 
-#. Tag: title
-#: hardware.xml:1831
+#. Tag: para
+#: hardware.xml:1764
 #, no-c-format
-msgid "Floppies"
+msgid "Debian's support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. Most AGP, PCI and PCIe video cards work under X.Org. Details on supported graphics buses, cards, monitors, 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:1832
+#: hardware.xml:1773
 #, 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."
+msgid "The X.Org X Window System is only supported on the SGI Indy and the O2. The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1838
+#: hardware.xml:1782
 #, no-c-format
-msgid "For CHRP, floppy support is currently broken."
+msgid "The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available."
+msgstr ""
+
+#. Tag: para
+#: hardware.xml:1789
+#, 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:1799
+#, 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:1845
+#: hardware.xml:1821
 #, no-c-format
-msgid "CD-ROM/DVD-ROM"
+msgid "Network Connectivity Hardware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1847
+#: hardware.xml:1822
 #, 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, except for some very old nonstandard CD-ROM drives which are neither SCSI nor IDE/ATAPI."
+msgid "Almost any network interface card (NIC) supported by the Linux kernel should also be supported by the installation system; modular drivers should normally be loaded automatically. <phrase arch=\"x86\">This includes most PCI and PCMCIA cards.</phrase> <phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase> <phrase arch=\"m68k\">Again, see <ulink url=\"&url-m68k-faq;\"></ulink> for complete details.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1854
+#: hardware.xml:1834
 #, no-c-format
-msgid "CD-ROM based installation is supported for some architectures. On machines which support bootable CD-ROMs, you should be able to do a completely <phrase arch=\"not-s390\">floppy-less</phrase> <phrase arch=\"s390\">tape-less</phrase> installation. Even if your system doesn't support booting from a CD-ROM, you can use the CD-ROM in conjunction with the other techniques to install your system, once you've booted up by other means; see <xref linkend=\"boot-installer\"/>."
+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:1866
+#: hardware.xml:1840
 #, no-c-format
-msgid "SCSI, SATA and IDE/ATAPI CD-ROMs are supported. The <ulink url=\"&url-cd-howto;\">Linux CD-ROM HOWTO</ulink> contains in-depth information on using CD-ROMs with Linux."
+msgid "Sun LANCE"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1872
+#: hardware.xml:1845
 #, no-c-format
-msgid "USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers."
+msgid "Sun Happy Meal"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1877
+#: hardware.xml:1850
 #, no-c-format
-msgid "Both SCSI and IDE/ATAPI CD-ROMs are supported on &arch-title;, as long as the controller is supported by the SRM console. This rules out many add-on controller cards, but most integrated IDE and SCSI chips and controller cards that were provided by the manufacturer can be expected to work. To find out whether your device is supported from the SRM console, see the <ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink>."
+msgid "Sun BigMAC"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1886
+#: hardware.xml:1855
 #, no-c-format
-msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines."
+msgid "Sun QuadEthernet"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1890
+#: hardware.xml:1860
 #, 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. The Broadcom BCM91250A supports standard IDE devices, including CD-ROM drives, but CD images for this platform are currently not provided because the firmware doesn't recognize CD drives. In order to install Debian on an Broadcom BCM91480B evaluation board, you need an PCI IDE, SATA or SCSI card."
+msgid "MyriCOM Gigabit Ethernet"
 msgstr ""
 
-#. Tag: title
-#: hardware.xml:1908
+#. Tag: para
+#: hardware.xml:1867
 #, no-c-format
-msgid "Hard Disk"
+msgid "The list of supported network devices is:"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1910
+#: hardware.xml:1872
 #, 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."
+msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1916
+#: hardware.xml:1877
 #, no-c-format
-msgid "In fact, installation from your local disk is the preferred installation technique for most &architecture; machines."
+msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1921
+#: hardware.xml:1882
 #, no-c-format
-msgid "Although the &arch-title; does not allow booting from SunOS (Solaris), you can install from a SunOS partition (UFS slices)."
+msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs"
 msgstr ""
 
-#. Tag: title
-#: hardware.xml:1929
+#. Tag: para
+#: hardware.xml:1891
 #, no-c-format
-msgid "USB Memory Stick"
+msgid "On &arch-title;, most built-in Ethernet devices are supported and modules for additional PCI and USB devices are provided. The major exception is the IXP4xx platform (featuring devices such as the Linksys NSLU2) which needs a proprietary microcode for the operation of its built-in Ethernet device. Unofficial images for Linksys NSLU2 with this proprietary microcode can be obtained from the <ulink url=\"&url-slug-firmware;\">Slug-Firmware site</ulink>."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1931
+#: hardware.xml:1901
 #, no-c-format
-msgid "Many Debian boxes need their floppy and/or CD-ROM drives only for setting up the system and for rescue purposes. If you operate some servers, you will probably already have thought about omitting those drives and using an USB memory stick for installing and (when necessary) for recovering the system. This is also useful for small systems which have no room for unnecessary drives."
+msgid "ISDN is supported, but not during the installation."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1943
+#: hardware.xml:1908
 #, no-c-format
-msgid "Network"
+msgid "Wireless Network Cards"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1945
+#: hardware.xml:1909
 #, 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."
+msgid "Wireless networking is in general supported as well and a growing number of wireless adapters is supported by the official Linux kernel, although many of them do require firmware to be loaded. Wireless NICs that are not supported by the official Linux kernel can generally be made to work under &debian;, but are not supported during the installation."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1955
+#: hardware.xml:1917
 #, no-c-format
-msgid "You can also <emphasis>boot</emphasis> the installation system over the network. <phrase arch=\"mips\">This is the preferred installation technique for &arch-title;.</phrase>"
+msgid "The use of wireless networking during installation is still under development and whether it will work depends on the type of adaptor and the configuration of your wireless access point. If there is no other NIC you can use during the installation, it is still possible to install &debian; using a full CD-ROM or DVD image. Use the same procedure as described above for NICs that require firmware."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1961
+#: hardware.xml:1926
 #, no-c-format
-msgid "Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option."
+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:1969
+#: hardware.xml:1940
 #, no-c-format
-msgid "Un*x or GNU system"
+msgid "Known Issues for &arch-title;"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1971
+#: hardware.xml:1941
 #, no-c-format
-msgid "If you are running another Unix-like system, you could use it to install &debian; 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\"/>."
+msgid "There are a couple of issues with specific network cards that are worth mentioning here."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1983
+#: hardware.xml:1948
 #, no-c-format
-msgid "Supported Storage Systems"
+msgid "Conflict between tulip and dfme drivers"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1985
+#: hardware.xml:1950
 #, no-c-format
-msgid "The Debian boot disks contain a kernel which is built to maximize the number of systems it runs on. Unfortunately, this makes for a larger kernel, which includes many drivers that won't be used for your machine (see <xref linkend=\"kernel-baking\"/> to learn how to build your own kernel). Support for the widest possible range of devices is desirable in general, to ensure that Debian can be installed on the widest array of hardware."
+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:1995
+#: hardware.xml:1960
 #, no-c-format
-msgid "Generally, the Debian installation system includes support for floppies, IDE (also known as PATA) drives, IDE floppies, parallel port IDE devices, SATA and SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS."
+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:2002
+#: hardware.xml:1968
 #, no-c-format
-msgid "Disk interfaces that emulate the <quote>AT</quote> hard disk interface &mdash; often called MFM, RLL, IDE, or PATA &mdash; are supported. SATA and SCSI disk controllers from many different manufacturers are supported. See the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> for more details."
+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: para
-#: hardware.xml:2010
+#. Tag: title
+#: hardware.xml:1981
 #, no-c-format
-msgid "Pretty much all storage systems supported by the Linux kernel are supported by the Debian installation system. Note that the current Linux kernel does not support floppies on the Macintosh at all, and the Debian installation system doesn't support floppies for Amigas. Also supported on the Atari is the Macintosh HFS system, and AFFS as a module. Macs support the Atari (FAT) file system. Amigas support the FAT file system, and HFS as a module."
+msgid "Sun B100 blade"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2020
+#: hardware.xml:1983
 #, 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."
+msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems."
 msgstr ""
 
-#. Tag: para
-#: hardware.xml:2053
+#. Tag: title
+#: hardware.xml:1998
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This includes both SCSI and IDE disks. Note, however, that on many systems, the SRM console is unable to boot from IDE drives, and the Jensen is unable to boot from floppies. (see <ulink url=\"&url-jensen-howto;\"></ulink> for more information on booting the Jensen)"
+msgid "Peripherals and Other Hardware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2062
+#: hardware.xml:1999
 #, 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."
+msgid "Linux 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:2068
+#: hardware.xml:2005
 #, 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."
+msgid "USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend=\"hardware-issues\"/>)."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2074
+#: hardware.xml:2011
 #, no-c-format
-msgid "Any storage system supported by the Linux kernel is also supported by the boot system."
+msgid "Again, see the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> to determine whether your specific hardware is supported by Linux."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2079
+#: hardware.xml:2017
 #, 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:2096
-#, no-c-format
-msgid "Peripherals and Other Hardware"
+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:2097
+#: hardware.xml:2023
 #, no-c-format
-msgid "Linux 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."
+msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation board features four 64 bit PCI slots."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2103
+#: hardware.xml:2029
 #, no-c-format
-msgid "USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend=\"hardware-issues\"/>)."
+msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation board features four 64 bit PCI slots. The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot."
 msgstr ""
 
-#. Tag: para
-#: hardware.xml:2109
+#. Tag: title
+#: hardware.xml:2043
 #, no-c-format
-msgid "Again, see the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> to determine whether your specific hardware is supported by Linux."
+msgid "Devices Requiring Firmware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2115
+#: hardware.xml:2044
 #, 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."
+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."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2121
+#: hardware.xml:2052
 #, no-c-format
-msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation board features four 64 bit PCI slots."
+msgid "In most cases firmware is non-free according to the criteria used by the &debian; 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; 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:2127
+#: hardware.xml:2061
 #, no-c-format
-msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation board features four 64 bit PCI slots. The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot."
+msgid "However, this does not mean that such hardware cannot be used during an installation. Starting with &debian; 5.0, &d-i; supports loading firmware files or packages containing firmware from a removable medium, such as a floppy disk or USB stick. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware files or packages during the installation."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:2137
+#: hardware.xml:2077
 #, no-c-format
 msgid "Purchasing Hardware Specifically for GNU/Linux"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2139
+#: hardware.xml:2079
 #, 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:2147
+#: hardware.xml:2087
 #, no-c-format
 msgid "Unfortunately, it's quite rare to find any vendor shipping new &arch-title; machines at all."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2152
+#: hardware.xml:2092
 #, 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:2160
+#: hardware.xml:2100
 #, no-c-format
 msgid "Whether or not you are purchasing a system with Linux bundled, or even a used system, it is still important to check that your hardware is supported by the Linux kernel. Check if your hardware is listed in the references found above. Let your salesperson (if any) know that you're shopping for a Linux system. Support Linux-friendly hardware vendors."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:2171
+#: hardware.xml:2111
 #, no-c-format
 msgid "Avoid Proprietary or Closed Hardware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2172
+#: hardware.xml:2112
 #, 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 Linux source code."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2179
+#: hardware.xml:2119
 #, no-c-format
 msgid "Another example is the proprietary hardware in the older Macintosh line. In fact, no specifications or documentation have ever been released for any Macintosh hardware, most notably the ADB controller (used by the mouse and keyboard), the floppy controller, and all acceleration and CLUT manipulation of the video hardware (though we do now support CLUT manipulation on nearly all internal video chips). In a nutshell, this explains why the Macintosh Linux port lags behind other Linux ports."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2190
+#: hardware.xml:2130
 #, no-c-format
 msgid "Since we haven't been granted access to the documentation on these devices, they simply won't work under Linux. You can help by asking the manufacturers of such hardware to release the documentation. If enough people ask, they will realize that the free software community is an important market."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:2202
+#: hardware.xml:2142
 #, no-c-format
 msgid "Windows-specific Hardware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2203
+#: hardware.xml:2143
 #, no-c-format
 msgid "A disturbing trend is the proliferation of Windows-specific modems and printers. In some cases these are specially designed to be operated by the Microsoft Windows operating system and bear the legend <quote>WinModem</quote> or <quote>Made especially for Windows-based computers</quote>. This is generally done by removing the embedded processors of the hardware and shifting the work they do over to a Windows driver that is run by your computer's main CPU. This strategy makes the hardware less expensive, but the savings are often <emphasis>not</emphasis> passed on to the user and this hardware may even be more expensive than equivalent devices that retain their embedded intelligence."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2216
+#: hardware.xml:2156
 #, no-c-format
 msgid "You should avoid Windows-specific hardware for two reasons. The first is that the manufacturers do not generally make the resources available to write a Linux driver. Generally, the hardware and software interface to the device is proprietary, and documentation is not available without a non-disclosure agreement, if it is available at all. This precludes it being used for free software, since free software writers disclose the source code of their programs. The second reason is that when devices like these have had their embedded processors removed, the operating system must perform the work of the embedded processors, often at <emphasis>real-time</emphasis> priority, and thus the CPU is not available to run your programs while it is driving these devices. Since the typical Windows user does not multi-process as intensively as a Linux user, the manufacturers hope that the Windows user simply won't notice the burden this hardware places on their CPU. However, any multi-processing operating system, even Windows 2000 or XP, suffers from degraded performance when peripheral manufacturers skimp on the embedded processing power of their hardware."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2237
+#: hardware.xml:2177
 #, no-c-format
 msgid "You can help improve this situation by encouraging these manufacturers to release the documentation and other resources necessary for us to program their hardware, but the best strategy is simply to avoid this sort of hardware until it is listed as working in the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:2254
+#: hardware.xml:2194
 #, no-c-format
-msgid "Memory and Disk Space Requirements"
+msgid "Installation Media"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2256
+#: hardware.xml:2196
 #, 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\"/>."
+msgid "This section will help you determine which different media types you can use to install Debian. For example, if you have a floppy disk drive on your machine, it can be used 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: para
-#: hardware.xml:2263
+#. Tag: title
+#: hardware.xml:2207
 #, 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."
+msgid "Floppies"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2280
+#: hardware.xml:2208
 #, no-c-format
-msgid "On the Amiga the size of FastRAM is relevant towards the total memory requirements. Also, using Zorro cards with 16-bit RAM is not supported; you'll need 32-bit RAM. The <command>amiboot</command> program can be used to disable 16-bit RAM; see the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. Recent kernels should disable 16-bit RAM automatically."
+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:2289
+#: hardware.xml:2214
 #, no-c-format
-msgid "On the Atari, both ST-RAM and Fast RAM (TT-RAM) are used by Linux. Many users have reported problems running the kernel itself in Fast RAM, so the Atari bootstrap will place the kernel in ST-RAM. The minimum requirement for ST-RAM is 2 MB. You will need an additional 12 MB or more of TT-RAM."
+msgid "For CHRP, floppy support is currently broken."
 msgstr ""
 
-#. Tag: para
-#: hardware.xml:2297
+#. Tag: title
+#: hardware.xml:2221
 #, no-c-format
-msgid "On the Macintosh, care should be taken on machines with RAM-based video (RBV). The RAM segment at physical address 0 is used as screen memory, making the default load position for the kernel unavailable. The alternate RAM segment used for kernel and RAMdisk must be at least 4 MB."
+msgid "CD-ROM/DVD-ROM"
 msgstr ""
 
-#. Tag: emphasis
-#: hardware.xml:2307
+#. Tag: para
+#: hardware.xml:2223
 #, no-c-format
-msgid "FIXME: is this still true?"
+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, except for some very old nonstandard CD-ROM drives which are neither SCSI nor IDE/ATAPI."
 msgstr ""
 
-#. Tag: title
-#: hardware.xml:2318
+#. Tag: para
+#: hardware.xml:2230
 #, no-c-format
-msgid "Network Connectivity Hardware"
+msgid "CD-ROM based installation is supported for some architectures. On machines which support bootable CD-ROMs, you should be able to do a completely <phrase arch=\"not-s390\">floppy-less</phrase> <phrase arch=\"s390\">tape-less</phrase> installation. Even if your system doesn't support booting from a CD-ROM, you can use the CD-ROM in conjunction with the other techniques to install your system, once you've booted up by other means; see <xref linkend=\"boot-installer\"/>."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2319
+#: hardware.xml:2242
 #, no-c-format
-msgid "Almost any network interface card (NIC) supported by the Linux kernel should also be supported by the installation system; modular drivers should normally be loaded automatically. <phrase arch=\"x86\">This includes most PCI and PCMCIA cards.</phrase> <phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase> <phrase arch=\"m68k\">Again, see <ulink url=\"&url-m68k-faq;\"></ulink> for complete details.</phrase>"
+msgid "SCSI, SATA and IDE/ATAPI CD-ROMs are supported. The <ulink url=\"&url-cd-howto;\">Linux CD-ROM HOWTO</ulink> contains in-depth information on using CD-ROMs with Linux."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2331
+#: hardware.xml:2248
 #, no-c-format
-msgid "This includes a lot of generic PCI cards (for systems that have PCI) and the following NICs from Sun:"
+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:2337
+#: hardware.xml:2253
 #, no-c-format
-msgid "Sun LANCE"
+msgid "Both SCSI and IDE/ATAPI CD-ROMs are supported on &arch-title;, as long as the controller is supported by the SRM console. This rules out many add-on controller cards, but most integrated IDE and SCSI chips and controller cards that were provided by the manufacturer can be expected to work. To find out whether your device is supported from the SRM console, see the <ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink>."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2342
+#: hardware.xml:2262
 #, no-c-format
-msgid "Sun Happy Meal"
+msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2347
+#: hardware.xml:2266
 #, no-c-format
-msgid "Sun BigMAC"
+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. The Broadcom BCM91250A supports standard IDE devices, including CD-ROM drives, but CD images for this platform are currently not provided because the firmware doesn't recognize CD drives. In order to install Debian on an Broadcom BCM91480B evaluation board, you need an PCI IDE, SATA or SCSI card."
+msgstr ""
+
+#. Tag: title
+#: hardware.xml:2284
+#, no-c-format
+msgid "Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2352
+#: hardware.xml:2286
 #, no-c-format
-msgid "Sun QuadEthernet"
+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."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2357
+#: hardware.xml:2292
 #, no-c-format
-msgid "MyriCOM Gigabit Ethernet"
+msgid "In fact, installation from your local disk is the preferred installation technique for most &architecture; machines."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2364
+#: hardware.xml:2297
 #, no-c-format
-msgid "The list of supported network devices is:"
+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:2305
+#, no-c-format
+msgid "USB Memory Stick"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2369
+#: hardware.xml:2307
 #, no-c-format
-msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)"
+msgid "Many Debian boxes need their floppy and/or CD-ROM drives only for setting up the system and for rescue purposes. If you operate some servers, you will probably already have thought about omitting those drives and using an USB memory stick for installing and (when necessary) for recovering the system. This is also useful for small systems which have no room for unnecessary drives."
+msgstr ""
+
+#. Tag: title
+#: hardware.xml:2319
+#, no-c-format
+msgid "Network"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2374
+#: hardware.xml:2321
 #, no-c-format
-msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)"
+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:2379
+#: hardware.xml:2331
 #, no-c-format
-msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs"
+msgid "You can also <emphasis>boot</emphasis> the installation system over the network. <phrase arch=\"mips\">This is the preferred installation technique for &arch-title;.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2388
+#: hardware.xml:2337
 #, no-c-format
-msgid "On &arch-title;, most built-in Ethernet devices are supported and modules for additional PCI and USB devices are provided. The major exception is the IXP4xx platform (featuring devices such as the Linksys NSLU2) which needs a proprietary microcode for the operation of its built-in Ethernet device. Unofficial images for Linksys NSLU2 with this proprietary microcode can be obtained from the <ulink url=\"&url-slug-firmware;\">Slug-Firmware site</ulink>."
+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:2345
+#, no-c-format
+msgid "Un*x or GNU system"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2398
+#: hardware.xml:2347
 #, no-c-format
-msgid "As for ISDN, the D-channel protocol for the (old) German 1TR6 is not supported; Spellcaster BRI ISDN boards are also not supported by the &d-i;. Using ISDN during the installation is not supported."
+msgid "If you are running another Unix-like system, you could use it to install &debian; 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\"/>."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:2407
+#: hardware.xml:2359
 #, no-c-format
-msgid "Drivers Requiring Firmware"
+msgid "Supported Storage Systems"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2408
+#: hardware.xml:2361
 #, no-c-format
-msgid "The installation system currently does not support retrieving firmware. This means that any network cards that use a driver that requires firmware to be loaded, is not supported by default."
+msgid "The Debian boot disks contain a kernel which is built to maximize the number of systems it runs on. Unfortunately, this makes for a larger kernel, which includes many drivers that won't be used for your machine (see <xref linkend=\"kernel-baking\"/> to learn how to build your own kernel). Support for the widest possible range of devices is desirable in general, to ensure that Debian can be installed on the widest array of hardware."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2414
+#: hardware.xml:2371
 #, no-c-format
-msgid "If there is no other NIC you can use during the installation, it is still possible to install &debian; 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. Note that the firmware may be packaged separately from the driver and may not be available in the <quote>main</quote> section of the &debian; archive."
+msgid "Generally, the Debian installation system includes support for floppies, IDE (also known as PATA) drives, IDE floppies, parallel port IDE devices, 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:2425
+#: hardware.xml:2378
 #, no-c-format
-msgid "If the driver itself <emphasis>is</emphasis> supported, you may also be able to use the NIC during installation by copying the firmware from some medium to <filename>/usr/lib/hotplug/firmware</filename>. Don't forget to also copy the firmware to that location for the installed system before the reboot at the end of the installation."
+msgid "Disk interfaces that emulate the <quote>AT</quote> hard disk interface &mdash; often called MFM, RLL, IDE, or PATA &mdash; are supported. SATA and SCSI disk controllers from many different manufacturers are supported. See the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> for more details."
 msgstr ""
 
-#. Tag: title
-#: hardware.xml:2437
+#. Tag: para
+#: hardware.xml:2386
 #, no-c-format
-msgid "Wireless Network Cards"
+msgid "Pretty much all storage systems supported by the Linux kernel are supported by the Debian installation system. Note that the current Linux kernel does not support floppies on the Macintosh at all, and the Debian installation system doesn't support floppies for Amigas. Also supported on the Atari is the Macintosh HFS system, and AFFS as a module. Macs support the Atari (FAT) file system. Amigas support the FAT file system, and HFS as a module."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2438
+#: hardware.xml:2396
 #, no-c-format
-msgid "Wireless NICs are in general supported as well, with one big proviso. A lot of wireless adapters require drivers that are either non-free or have not been accepted into the official Linux kernel. These NICs can generally be made to work under &debian;, but are not supported during the installation."
+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:2445
+#: hardware.xml:2429
 #, no-c-format
-msgid "If there is no other NIC you can use during the installation, it is still possible to install &debian; using a full CD-ROM or DVD image. Use the same procedure as described above for NICs that require firmware."
+msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This includes both SCSI and IDE disks. Note, however, that on many systems, the SRM console is unable to boot from IDE drives, and the Jensen is unable to boot from floppies. (see <ulink url=\"&url-jensen-howto;\"></ulink> for more information on booting the Jensen)"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2451
+#: hardware.xml:2438
 #, 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>"
+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: title
-#: hardware.xml:2465
+#. Tag: para
+#: hardware.xml:2444
 #, no-c-format
-msgid "Known Issues for &arch-title;"
+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:2466
+#: hardware.xml:2450
 #, no-c-format
-msgid "There are a couple of issues with specific network cards that are worth mentioning here."
+msgid "Any storage system supported by the Linux kernel is also supported by the boot system."
+msgstr ""
+
+#. Tag: para
+#: hardware.xml:2455
+#, 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:2473
+#: hardware.xml:2472
 #, no-c-format
-msgid "Conflict between tulip and dfme drivers"
+msgid "Memory and Disk Space Requirements"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2475
+#: hardware.xml:2474
 #, 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."
+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:2485
+#: hardware.xml:2481
 #, 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\"/>."
+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 ""
 
 #. Tag: para
-#: hardware.xml:2493
+#: hardware.xml:2498
 #, 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."
+msgid "On the Amiga the size of FastRAM is relevant towards the total memory requirements. Also, using Zorro cards with 16-bit RAM is not supported; you'll need 32-bit RAM. The <command>amiboot</command> program can be used to disable 16-bit RAM; see the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. Recent kernels should disable 16-bit RAM automatically."
 msgstr ""
 
-#. Tag: title
-#: hardware.xml:2506
+#. Tag: para
+#: hardware.xml:2507
 #, no-c-format
-msgid "Sun B100 blade"
+msgid "On the Atari, both ST-RAM and Fast RAM (TT-RAM) are used by Linux. Many users have reported problems running the kernel itself in Fast RAM, so the Atari bootstrap will place the kernel in ST-RAM. The minimum requirement for ST-RAM is 2 MB. You will need an additional 12 MB or more of TT-RAM."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2508
+#: hardware.xml:2515
 #, no-c-format
-msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems."
+msgid "On the Macintosh, care should be taken on machines with RAM-based video (RBV). The RAM segment at physical address 0 is used as screen memory, making the default load position for the kernel unavailable. The alternate RAM segment used for kernel and RAMdisk must be at least 4 MB."
+msgstr ""
+
+#. Tag: emphasis
+#: hardware.xml:2525
+#, no-c-format
+msgid "FIXME: is this still true?"
 msgstr ""
 
diff --git a/po/pot/preseed.pot b/po/pot/preseed.pot
index aca02e3fd..28554d5ec 100644
--- a/po/pot/preseed.pot
+++ b/po/pot/preseed.pot
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2008-09-28 00:09+0000\n"
+"POT-Creation-Date: 2008-10-05 00:05+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"
@@ -1002,17 +1002,11 @@ msgstr ""
 #. Tag: para
 #: preseed.xml:845
 #, no-c-format
-msgid "This type of automated partitioning is easy to get wrong. It is also a very new component that may still have some bugs or missing error handling. The responsibility to get the various recipes right (so they make sense and don't conflict) lies with the user. Check <filename>/var/log/syslog</filename> if you run into problems."
-msgstr ""
-
-#. Tag: para
-#: preseed.xml:853
-#, no-c-format
-msgid "Note that only RAID 0 and RAID 1 have been tested by the developers of the component. RAID 5 is untested. Advanced RAID setup with degraded arrays or spare devices has only been tested lightly."
+msgid "This type of automated partitioning is easy to get wrong. It is also functionality that receives relatively little testing from the developers of &d-i;. The responsibility to get the various recipes right (so they make sense and don't conflict) lies with the user. Check <filename>/var/log/syslog</filename> if you run into problems."
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:861
+#: preseed.xml:855
 #, no-c-format
 msgid ""
       "# NOTE: this option is of beta release quality and should be used carefully\n"
@@ -1063,19 +1057,19 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:866
+#: preseed.xml:860
 #, no-c-format
 msgid "Base system installation"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:867
+#: preseed.xml:861
 #, no-c-format
 msgid "There is actually not very much that can be preseeded for this stage of the installation. The only questions asked concern the installation of the kernel."
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:874
+#: preseed.xml:868
 #, no-c-format
 msgid ""
       "# Select the initramfs generator used to generate the initrd for 2.6 kernels.\n"
@@ -1087,25 +1081,25 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:879
+#: preseed.xml:873
 #, no-c-format
 msgid "Account setup"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:880
+#: preseed.xml:874
 #, no-c-format
 msgid "The password for the root account and name and password for a first regular user's account can be preseeded. For the passwords you can use either clear text values or MD5 <emphasis>hashes</emphasis>."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:887
+#: preseed.xml:881
 #, no-c-format
 msgid "Be aware that preseeding passwords is not completely secure as everyone with access to the preconfiguration file will have the knowledge of these passwords. Using MD5 hashes is considered slightly better in terms of security but it might also give a false sense of security as access to a MD5 hash allows for brute force attacks."
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:897
+#: preseed.xml:891
 #, no-c-format
 msgid ""
       "# Skip creation of a root account (normal user account will be able to\n"
@@ -1137,37 +1131,37 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:899
+#: preseed.xml:893
 #, no-c-format
 msgid "The <classname>passwd/root-password-crypted</classname> and <classname>passwd/user-password-crypted</classname> variables can also be preseeded with <quote>!</quote> as their value. In that case, the corresponding account is disabled. This may be convenient for the root account, provided of course that an alternative method is setup to allow administrative activities or root login (for instance by using SSH key authentication or <command>sudo</command>)."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:909
+#: preseed.xml:903
 #, no-c-format
 msgid "The following command can be used to generate an MD5 hash for a password:"
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:913
+#: preseed.xml:907
 #, no-c-format
 msgid "$ echo \"r00tme\" | mkpasswd -s -m md5"
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:919
+#: preseed.xml:913
 #, no-c-format
 msgid "Apt setup"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:920
+#: preseed.xml:914
 #, no-c-format
 msgid "Setup of the <filename>/etc/apt/sources.list</filename> and basic configuration options is fully automated based on your installation method and answers to earlier questions. You can optionally add other (local) repositories."
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:928
+#: preseed.xml:922
 #, no-c-format
 msgid ""
       "# You can choose to install non-free and contrib software.\n"
@@ -1199,97 +1193,97 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:933
+#: preseed.xml:927
 #, no-c-format
 msgid "Package selection"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:934
+#: preseed.xml:928
 #, no-c-format
 msgid "You can choose to install any combination of tasks that are available. Available tasks as of this writing include:"
 msgstr ""
 
 #. Tag: userinput
-#: preseed.xml:943
+#: preseed.xml:937
 #, no-c-format
 msgid "standard"
 msgstr ""
 
 #. Tag: userinput
-#: preseed.xml:946
+#: preseed.xml:940
 #, no-c-format
 msgid "desktop"
 msgstr ""
 
 #. Tag: userinput
-#: preseed.xml:949
+#: preseed.xml:943
 #, no-c-format
 msgid "gnome-desktop"
 msgstr ""
 
 #. Tag: userinput
-#: preseed.xml:952
+#: preseed.xml:946
 #, no-c-format
 msgid "kde-desktop"
 msgstr ""
 
 #. Tag: userinput
-#: preseed.xml:955
+#: preseed.xml:949
 #, no-c-format
 msgid "web-server"
 msgstr ""
 
 #. Tag: userinput
-#: preseed.xml:958
+#: preseed.xml:952
 #, no-c-format
 msgid "print-server"
 msgstr ""
 
 #. Tag: userinput
-#: preseed.xml:961
+#: preseed.xml:955
 #, no-c-format
 msgid "dns-server"
 msgstr ""
 
 #. Tag: userinput
-#: preseed.xml:964
+#: preseed.xml:958
 #, no-c-format
 msgid "file-server"
 msgstr ""
 
 #. Tag: userinput
-#: preseed.xml:967
+#: preseed.xml:961
 #, no-c-format
 msgid "mail-server"
 msgstr ""
 
 #. Tag: userinput
-#: preseed.xml:970
+#: preseed.xml:964
 #, no-c-format
 msgid "sql-database"
 msgstr ""
 
 #. Tag: userinput
-#: preseed.xml:973
+#: preseed.xml:967
 #, no-c-format
 msgid "laptop"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:977
+#: preseed.xml:971
 #, no-c-format
 msgid "You can also choose to install no tasks, and force the installation of a set of packages in some other way. We recommend always including the <userinput>standard</userinput> task."
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:983
+#: preseed.xml:977
 #, no-c-format
 msgid "If you want to install some individual packages in addition to packages installed by tasks, you can use the parameter <classname>pkgsel/include</classname>. The value of this parameter can be a list of packages separated by either commas or spaces, which allows it to be used easily on the kernel command line as well."
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:993
+#: preseed.xml:987
 #, no-c-format
 msgid ""
       "#tasksel tasksel/first multiselect standard, web-server\n"
@@ -1311,13 +1305,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:998
+#: preseed.xml:992
 #, no-c-format
 msgid "Boot loader installation"
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:1000
+#: preseed.xml:994
 #, no-c-format
 msgid ""
       "# Grub is the default boot loader (for x86). If you want lilo installed\n"
@@ -1351,19 +1345,19 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:1002
+#: preseed.xml:996
 #, no-c-format
 msgid "An MD5 hash for a password for <classname>grub</classname> can be generated using <command>grub-md5-crypt</command>, or using the command from the example in <xref linkend=\"preseed-account\"/>."
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:1012
+#: preseed.xml:1006
 #, no-c-format
 msgid "Finishing up the installation"
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:1014
+#: preseed.xml:1008
 #, no-c-format
 msgid ""
       "# During installations from serial console, the regular virtual consoles\n"
@@ -1386,51 +1380,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:1019
-#, no-c-format
-msgid "X configuration"
-msgstr ""
-
-#. Tag: para
-#: preseed.xml:1020
-#, no-c-format
-msgid "Preseeding Debian's X config is possible, but you probably need to know some details about the video hardware of the machine, since Debian's X configurator does not do fully automatic configuration of everything."
-msgstr ""
-
-#. Tag: screen
-#: preseed.xml:1028
-#, no-c-format
-msgid ""
-      "# X can detect the right driver for some cards, but if you're preseeding,\n"
-      "# you override whatever it chooses. Still, vesa will work most places.\n"
-      "#xserver-xorg xserver-xorg/config/device/driver select vesa\n"
-      "\n"
-      "# A caveat with mouse autodetection is that if it fails, X will retry it\n"
-      "# over and over. So if it's preseeded to be done, there is a possibility of\n"
-      "# an infinite loop if the mouse is not autodetected.\n"
-      "#xserver-xorg xserver-xorg/autodetect_mouse boolean true\n"
-      "\n"
-      "# Monitor autodetection is recommended.\n"
-      "xserver-xorg xserver-xorg/autodetect_monitor boolean true\n"
-      "# Uncomment if you have an LCD display.\n"
-      "#xserver-xorg xserver-xorg/config/monitor/lcd boolean true\n"
-      "# X has three configuration paths for the monitor. Here's how to preseed\n"
-      "# the \"medium\" path, which is always available. The \"simple\" path may not\n"
-      "# be available, and the \"advanced\" path asks too many questions.\n"
-      "xserver-xorg xserver-xorg/config/monitor/selection-method \\\n"
-      "       select medium\n"
-      "xserver-xorg xserver-xorg/config/monitor/mode-list \\\n"
-      "       select 1024x768 @ 60 Hz"
-msgstr ""
-
-#. Tag: title
-#: preseed.xml:1033
+#: preseed.xml:1013
 #, no-c-format
 msgid "Preseeding other packages"
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:1035
+#: preseed.xml:1015
 #, no-c-format
 msgid ""
       "# Depending on what software you choose to install, or if things go wrong\n"
@@ -1443,25 +1399,25 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:1042
+#: preseed.xml:1022
 #, no-c-format
 msgid "Advanced options"
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:1045
+#: preseed.xml:1025
 #, no-c-format
 msgid "Running custom commands during the installation"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:1046
+#: preseed.xml:1026
 #, no-c-format
 msgid "A very powerful and flexible option offered by the preconfiguration tools is the ability to run commands or scripts at certain points in the installation."
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:1054
+#: preseed.xml:1034
 #, no-c-format
 msgid ""
       "# d-i preseeding is inherently not secure. Nothing in the installer checks\n"
@@ -1483,13 +1439,13 @@ msgid ""
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:1059
+#: preseed.xml:1039
 #, no-c-format
 msgid "Using preseeding to change default values"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:1060
+#: preseed.xml:1040
 #, no-c-format
 msgid ""
       "It is possible to use preseeding to change the default answer for a question, but still have the question asked. To do this the <firstterm>seen</firstterm> flag must be reset to <quote>false</quote> after setting the value for a question. <informalexample><screen>\n"
@@ -1499,25 +1455,25 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:1074
+#: preseed.xml:1054
 #, no-c-format
 msgid "If you are preseeding using boot parameters, you can make the installer ask the corresponding question by using the <quote>?=</quote> operator, i.e. <userinput><replaceable>foo</replaceable>/<replaceable>bar</replaceable>?=<replaceable>value</replaceable></userinput>. This will of course only have effect for parameters that correspond to questions that are actually displayed during an installation and not for <quote>internal</quote> parameters."
 msgstr ""
 
 #. Tag: title
-#: preseed.xml:1089
+#: preseed.xml:1069
 #, no-c-format
 msgid "Chainloading preconfiguration files"
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:1090
+#: preseed.xml:1070
 #, no-c-format
 msgid "It is possible to include other preconfiguration files from a preconfiguration file. Any settings in those files will override pre-existing settings from files loaded earlier. This makes it possible to put, for example, general networking settings for your location in one file and more specific settings for certain configurations in other files."
 msgstr ""
 
 #. Tag: screen
-#: preseed.xml:1100
+#: preseed.xml:1080
 #, no-c-format
 msgid ""
       "# More than one file can be listed, separated by spaces; all will be\n"
@@ -1545,7 +1501,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: preseed.xml:1102
+#: preseed.xml:1082
 #, no-c-format
 msgid "It is also possible to chainload from the initrd or file preseeding phase, into network preseeding by setting preseed/url in the earlier files. This will cause network preseeding to be performed when the network comes up. You need to be careful when doing this, since there will be two distinct runs at preseeding, meaning for example that you get another chance to run the preseed/early command, the second one happening after the network comes up."
 msgstr ""
diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot
index e4ec37ae4..798ac9a6f 100644
--- a/po/pot/using-d-i.pot
+++ b/po/pot/using-d-i.pot
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2008-09-28 00:09+0000\n"
+"POT-Creation-Date: 2008-10-05 00:05+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"
@@ -458,254 +458,260 @@ msgstr ""
 msgid "You will notice that &d-i; performs <firstterm>hardware detection</firstterm> several times during this stage. The first time is targeted specifically at the hardware needed to load installer components (e.g. your CD-ROM or network card). As not all drivers may be available during this first run, hardware detection needs to be repeated later in the process."
 msgstr ""
 
+#. Tag: para
+#: using-d-i.xml:429
+#, no-c-format
+msgid "During hardware detection &d-i; checks if any of the drivers for the hardware devices in your system require firmware to be loaded. If any firmware is requested but unavailable, a dialog will be displayed that allows the missing firmware to be loaded from a removable medium. See <xref linkend=\"loading-firmware\"/> for further details."
+msgstr ""
+
 #. Tag: title
-#: using-d-i.xml:436
+#: using-d-i.xml:444
 #, no-c-format
 msgid "Check available memory / low memory mode"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:438
+#: using-d-i.xml:446
 #, no-c-format
 msgid "One of the first things &d-i; does, is to check available memory. If the available memory is limited, this component will make some changes in the installation process which hopefully will allow you to install &debian; on your system."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:445
+#: using-d-i.xml:453
 #, no-c-format
 msgid "The first measure taken to reduce memory consumption by the installer is to disable translations, which means that the installation can only be done in English. Of course, you can still localize the installed system after the installation has completed."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:452
+#: using-d-i.xml:460
 #, no-c-format
 msgid "If that is not sufficient, the installer will further reduce memory consumption by loading only those components essential to complete a basic installation. This reduces the functionality of the installation system. You will be given the opportunity to load additional components manually, but you should be aware that each component you select will use additional memory and thus may cause the installation to fail."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:461
+#: using-d-i.xml:469
 #, no-c-format
 msgid "If the installer runs in low memory mode, it is recommended to create a relatively large swap partition (64&ndash;128MB). The swap partition will be used as virtual memory and thus increases the amount of memory available to the system. The installer will activate the swap partition as early as possible in the installation process. Note that heavy use of swap will reduce performance of your system and may lead to high disk activity."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:471
+#: using-d-i.xml:479
 #, no-c-format
 msgid "Despite these measures, it is still possible that your system freezes, that unexpected errors occur or that processes are killed by the kernel because the system runs out of memory (which will result in <quote>Out of memory</quote> messages on VT4 and in the syslog)."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:478
+#: using-d-i.xml:486
 #, no-c-format
 msgid "For example, it has been reported that creating a big ext3 file system fails in low memory mode when there is insufficient swap space. If a larger swap doesn't help, try creating the file system as ext2 (which is an essential component of the installer) instead. It is possible to change an ext2 partition to ext3 after the installation."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:486
+#: using-d-i.xml:494
 #, no-c-format
 msgid "It is possible to force the installer to use a higher lowmem level than the one based on available memory by using the boot parameter <quote>lowmem</quote> as described in <xref linkend=\"installer-args\"/>."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:501
+#: using-d-i.xml:509
 #, no-c-format
 msgid "Selecting Localization Options"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:503
+#: using-d-i.xml:511
 #, no-c-format
 msgid "In most cases the first questions you will be asked concern the selection of localization options to be used both for the installation and for the installed system. The localization options consist of language, country and locales."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:510
+#: using-d-i.xml:518
 #, no-c-format
 msgid "The language you choose will be used for the rest of the installation process, provided a translation of the different dialogs is available. If no valid translation is available for the selected language, the installer will default to English."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:517
+#: using-d-i.xml:525
 #, no-c-format
 msgid "The selected country will be used later in the installation process to pick the default timezone and a Debian mirror appropriate for your geographic location. Language and country together will be used to set the default locale for your system and to help select your keyboard."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:524
+#: using-d-i.xml:532
 #, no-c-format
 msgid "You will first be asked to select your preferred language. The language names are listed in both English (left side) and in the language itself (right side); the names on the right side are also shown in the proper script for the language. The list is sorted on the English names. At the top of the list is an extra option that allows you to select the <quote>C</quote> locale instead of a language. Choosing the <quote>C</quote> locale will result in the installation proceding in English; the installed system will have no localization support as the <classname>locales</classname> package will not be installed."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:536
+#: using-d-i.xml:544
 #, no-c-format
 msgid "If you selected a language that is recognized as an official language for more than one country<footnote> <para> In technical terms: where multiple locales exist for that language with differing country codes. </para> </footnote>, you will be shown a list of only those countries. To select a country that is not in that list, choose <guimenuitem>Other</guimenuitem> (the last option). You will then be presented with a list of continents; selecting a continent will lead to a list of relevant countries on that continent."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:554
+#: using-d-i.xml:562
 #, no-c-format
 msgid "If the language has only one country associated with it, that country will be selected automatically. In that case it is only possible to select a different country by first lowering the debconf priority to medium, followed by revisiting the language selection option in the main menu of the installer."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:562
+#: using-d-i.xml:570
 #, no-c-format
 msgid "A default locale will be selected based on the selected language and country. If you are installing at medium or low priority, you will have the option of selecting a different default locale and of selecting additional locales to be generated for the installed system."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:577
+#: using-d-i.xml:585
 #, no-c-format
 msgid "Choosing a Keyboard"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:579
+#: using-d-i.xml:587
 #, no-c-format
 msgid "Keyboards are often tailored to the characters used in a language. Select a layout that conforms to the keyboard you are using, or select something close if the keyboard layout you want isn't represented. Once the system installation is complete, you'll be able to select a keyboard layout from a wider range of choices (run <command>kbdconfig</command> as root after you have completed the installation)."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:589
+#: using-d-i.xml:597
 #, no-c-format
 msgid "Move the highlight to the keyboard selection you desire and press &enterkey;. Use the arrow keys to move the highlight &mdash; they are in the same place in all national language keyboard layouts, so they are independent of the keyboard configuration. An 'extended' keyboard is one with <keycap>F1</keycap> through <keycap>F10</keycap> keys along the top row."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:598
+#: using-d-i.xml:606
 #, no-c-format
 msgid "There are two keyboard layouts for US keyboards; the qwerty/mac-usb-us (Apple USB) layout will place the Alt function on the <keycap>Command/Apple</keycap> key (in the keyboard position next to the <keycap>space</keycap> key similar to <keycap>Alt</keycap> on PC keyboards), while the qwerty/us (Standard) layout will place the Alt function on the <keycap>Option</keycap> key (engraved with 'alt' on most Mac keyboards). In other respects the two layouts are similar."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:628
+#: using-d-i.xml:636
 #, no-c-format
 msgid "Looking for the Debian Installer ISO Image"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:629
+#: using-d-i.xml:637
 #, no-c-format
 msgid "When installing via the <emphasis>hd-media</emphasis> method, there will be a moment where you need to find and mount the Debian Installer iso image in order to get the rest of the installation files. The component <command>iso-scan</command> does exactly this."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:636
+#: using-d-i.xml:644
 #, no-c-format
 msgid "At first, <command>iso-scan</command> automatically mounts all block devices (e.g. partitions) which have some known filesystem on them and sequentially searches for filenames ending with <filename>.iso</filename> (or <filename>.ISO</filename> for that matter). Beware that the first attempt scans only files in the root directory and in the first level of subdirectories (i.e. it finds <filename>/<replaceable>whatever</replaceable>.iso</filename>, <filename>/data/<replaceable>whatever</replaceable>.iso</filename>, but not <filename>/data/tmp/<replaceable>whatever</replaceable>.iso</filename>). After an iso image has been found, <command>iso-scan</command> checks its content to determine if the image is a valid Debian iso image or not. In the former case we are done, in the latter <command>iso-scan</command> seeks for another image."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:653
+#: using-d-i.xml:661
 #, no-c-format
 msgid "In case the previous attempt to find an installer iso image fails, <command>iso-scan</command> will ask you whether you would like to perform a more thorough search. This pass doesn't just look into the topmost directories, but really traverses whole filesystem."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:660
+#: using-d-i.xml:668
 #, no-c-format
 msgid "If <command>iso-scan</command> does not discover your installer iso image, reboot back to your original operating system and check if the image is named correctly (ending in <filename>.iso</filename>), if it is placed on a filesystem recognizable by &d-i;, and if it is not corrupted (verify the checksum). Experienced Unix users could do this without rebooting on the second console."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:681
+#: using-d-i.xml:689
 #, no-c-format
 msgid "Configuring the Network"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:683
+#: using-d-i.xml:691
 #, no-c-format
 msgid "As you enter this step, if the system detects that you have more than one network device, you'll be asked to choose which device will be your <emphasis>primary</emphasis> network interface, i.e. the one which you want to use for installation. The other interfaces won't be configured at this time. You may configure additional interfaces after installation is complete; see the <citerefentry> <refentrytitle>interfaces</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> man page."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:694
+#: using-d-i.xml:702
 #, no-c-format
 msgid "By default, &d-i; tries to configure your computer's network automatically via DHCP. If the DHCP probe succeeds, you are done. If the probe fails, it may be caused by many factors ranging from unplugged network cable, to a misconfigured DHCP setup. Or maybe you don't have a DHCP server in your local network at all. For further explanation, check the error messages on the fourth console. In any case, you will be asked if you want to retry, or if you want to perform a manual setup. DHCP servers are sometimes really slow in their responses, so if you are sure everything is in place, try again."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:706
+#: using-d-i.xml:714
 #, no-c-format
 msgid "The manual network setup in turn asks you a number of questions about your network, notably <computeroutput>IP address</computeroutput>, <computeroutput>Netmask</computeroutput>, <computeroutput>Gateway</computeroutput>, <computeroutput>Name server addresses</computeroutput>, and a <computeroutput>Hostname</computeroutput>. Moreover, if you have a wireless network interface, you will be asked to provide your <computeroutput>Wireless ESSID</computeroutput> and a <computeroutput>WEP key</computeroutput>. Fill in the answers from <xref linkend=\"needed-info\"/>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:720
+#: using-d-i.xml:728
 #, no-c-format
 msgid "Some technical details you might, or might not, find handy: the program assumes the network IP address is the bitwise-AND of your system's IP address and your netmask. The default broadcast address is calculated as the bitwise OR of your system's IP address with the bitwise negation of the netmask. It will also guess your gateway. If you can't find any of these answers, use the offered defaults &mdash; if necessary, you can change them by editing <filename>/etc/network/interfaces</filename> once the system has been installed."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:765
+#: using-d-i.xml:773
 #, no-c-format
 msgid "Configuring the Clock"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:767
+#: using-d-i.xml:775
 #, no-c-format
 msgid "The installer will first attempt to connect to a time server on the Internet (using the <firstterm>NTP</firstterm> protocol) in order to correctly set the system time. If this does not succeed, the installer will assume the time and date obtained from the system clock when the installation system was booted are correct. It is not possible to manually set the system time during the installation process."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:785
+#: using-d-i.xml:793
 #, no-c-format
 msgid "Depending on the location selected earlier in the installation process, you may be shown a list of timezones relevant for that location. If your location has only one time zone, you will not be asked anything and the system will assume that time zone."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:792
+#: using-d-i.xml:800
 #, no-c-format
 msgid "If for some reason you wish to set a time zone for the installed system that does <emphasis>not</emphasis> match the selected location, there are two options."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:803
+#: using-d-i.xml:811
 #, no-c-format
 msgid "The simplest option is to just select a different timezone after the installation has been completed and you've booted into the new system. The command to do this is:"
 msgstr ""
 
 #. Tag: screen
-#: using-d-i.xml:809
+#: using-d-i.xml:817
 #, no-c-format
 msgid "# dpkg-reconfigure tzdata"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:815
+#: using-d-i.xml:823
 #, no-c-format
 msgid "Alternatively, the time zone can be set at the very start of the installation by passing the parameter <userinput>time/zone=<replaceable>value</replaceable></userinput> when you boot the installation system. The value should of course be a valid time zone, for example <userinput>Europe/London</userinput> or <userinput>UTC</userinput>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:829
+#: using-d-i.xml:837
 #, no-c-format
 msgid "For automated installations the time zone can also be set using preseeding."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:842
+#: using-d-i.xml:850
 #, no-c-format
 msgid "Partitioning and Mount Point Selection"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:843
+#: using-d-i.xml:851
 #, no-c-format
 msgid "At this time, after hardware detection has been executed a final time, &d-i; should be at its full strength, customized for the user's needs and ready to do some real work. As the title of this section indicates, the main task of the next few components lies in partitioning your disks, creating filesystems, assigning mountpoints and optionally configuring closely related options like RAID, LVM or encrypted devices."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:864
+#: using-d-i.xml:872
 #, no-c-format
 msgid "If you are uncomfortable with partitioning, or just want to know more details, see <xref linkend=\"partitioning\"/>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:870
+#: using-d-i.xml:878
 #, no-c-format
 msgid ""
       "If a hard disk has previously used under Solaris, the partitioner may not detect the size of the drive correctly. Creating a new partition table does not fix this issue. What does help, is to <quote>zero</quote> the first few sectors of the drive: <informalexample><screen>\n"
@@ -714,163 +720,163 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:883
+#: using-d-i.xml:891
 #, no-c-format
 msgid "First you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive. This is also called <quote>guided</quote> partitioning. If you do not want to autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:893
+#: using-d-i.xml:901
 #, no-c-format
 msgid "Guided Partitioning"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:894
+#: using-d-i.xml:902
 #, no-c-format
 msgid "If you choose guided partitioning, you may have three options: to create partitions directly on the hard disk (classic method), or to create them using Logical Volume Management (LVM), or to create them using encrypted LVM<footnote> <para> The installer will encrypt the LVM volume group using a 256 bit AES key and makes use of the kernel's <quote>dm-crypt</quote> support. </para> </footnote>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:909
+#: using-d-i.xml:917
 #, no-c-format
 msgid "The option to use (encrypted) LVM may not be available on all architectures."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:914
+#: using-d-i.xml:922
 #, no-c-format
 msgid "When using LVM or encrypted LVM, the installer will create most partitions inside one big partition; the advantage of this method is that partitions inside this big partition can be resized relatively easily later. In the case of encrypted LVM the big partition will not be readable without knowing a special key phrase, thus providing extra security of your (personal) data."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:923
+#: using-d-i.xml:931
 #, no-c-format
 msgid "When using encrypted LVM, the installer will also automatically erase the disk by writing random data to it. This further improves security (as it makes it impossible to tell which parts of the disk are in use and also makes sure that any traces of previous installations are erased), but may take some time depending on the size of your disk."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:932
+#: using-d-i.xml:940
 #, no-c-format
 msgid "If you choose guided partitioning using LVM or encrypted LVM, some changes in the partition table will need to be written to the selected disk while LVM is being set up. These changes effectively erase all data that is currently on the selected hard disk and you will not be able to undo them later. However, the installer will ask you to confirm these changes before they are written to disk."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:942
+#: using-d-i.xml:950
 #, no-c-format
 msgid "If you choose guided partitioning (either classic or using (encrypted) LVM) for a whole disk, you will first be asked to select the disk you want to use. Check that all your disks are listed and, if you have several disks, make sure you select the correct one. The order they are listed in may differ from what you are used to. The size of the disks may help to identify them."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:951
+#: using-d-i.xml:959
 #, no-c-format
 msgid "Any data on the disk you select will eventually be lost, but you will always be asked to confirm any changes before they are written to the disk. If you have selected the classic method of partitioning, you will be able to undo any changes right until the end; when using (encrypted) LVM this is not possible."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:959
+#: using-d-i.xml:967
 #, no-c-format
 msgid "Next, you will be able to choose from the schemes listed in the table below. All schemes have their pros and cons, some of which are discussed in <xref linkend=\"partitioning\"/>. If you are unsure, choose the first one. Bear in mind that guided partitioning needs a certain minimal amount of free space to operate with. If you don't give it at least about 1GB of space (depends on chosen scheme), guided partitioning will fail."
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:975
+#: using-d-i.xml:983
 #, no-c-format
 msgid "Partitioning scheme"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:976
+#: using-d-i.xml:984
 #, no-c-format
 msgid "Minimum space"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:977
+#: using-d-i.xml:985
 #, no-c-format
 msgid "Created partitions"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:983
+#: using-d-i.xml:991
 #, no-c-format
 msgid "All files in one partition"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:984
+#: using-d-i.xml:992
 #, no-c-format
 msgid "600MB"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:985
+#: using-d-i.xml:993
 #, no-c-format
 msgid "<filename>/</filename>, swap"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:987
+#: using-d-i.xml:995
 #, no-c-format
 msgid "Separate /home partition"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:988
+#: using-d-i.xml:996
 #, no-c-format
 msgid "500MB"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:989
+#: using-d-i.xml:997
 #, no-c-format
 msgid "<filename>/</filename>, <filename>/home</filename>, swap"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:993
+#: using-d-i.xml:1001
 #, no-c-format
 msgid "Separate /home, /usr, /var and /tmp partitions"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:994
+#: using-d-i.xml:1002
 #, no-c-format
 msgid "<entry>1GB</entry>"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:995
+#: using-d-i.xml:1003
 #, no-c-format
 msgid "<filename>/</filename>, <filename>/home</filename>, <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1004
+#: using-d-i.xml:1012
 #, no-c-format
 msgid "If you choose guided partitioning using (encrypted) LVM, the installer will also create a separate <filename>/boot</filename> partition. The other partitions, including the swap partition, will be created inside the LVM partition."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1010
+#: using-d-i.xml:1018
 #, no-c-format
 msgid "If you choose guided partitioning for your IA-64 system, there will be an additional partition, formatted as a FAT16 bootable filesystem, for the EFI boot loader. There is also an additional menu item in the formatting menu to manually set up a partition as an EFI boot partition."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1018
+#: using-d-i.xml:1026
 #, no-c-format
 msgid "If you choose guided partitioning for your Alpha system, an additional, unformatted partition will be allocated at the beginning of your disk to reserve this space for the aboot boot loader."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1024
+#: using-d-i.xml:1032
 #, no-c-format
 msgid "After selecting a scheme, the next screen will show your new partition table, including information on whether and how partitions will be formatted and where they will be mounted."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1030
+#: using-d-i.xml:1038
 #, no-c-format
 msgid ""
       "The list of partitions might look like this: <informalexample><screen>\n"
@@ -893,601 +899,601 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1043
+#: using-d-i.xml:1051
 #, no-c-format
 msgid "This concludes the guided partitioning. If you are satisfied with the generated partition table, you can choose <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the menu to implement the new partition table (as described at the end of this section). If you are not happy, you can choose to <guimenuitem>Undo changes to partitions</guimenuitem> and run guided partitioning again, or modify the proposed changes as described below for manual partitioning."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:1057
+#: using-d-i.xml:1065
 #, no-c-format
 msgid "Manual Partitioning"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1058
+#: using-d-i.xml:1066
 #, no-c-format
 msgid "A similar screen to the one shown just above will be displayed if you choose manual partitioning except that your existing partition table will be shown and without the mount points. How to manually setup your partition table and the usage of partitions by your new Debian system will be covered in the remainder of this section."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1066
+#: using-d-i.xml:1074
 #, no-c-format
 msgid "If you select a pristine disk which has neither partitions nor free space on it, you will be asked if a new partition table should be created (this is needed so you can create new partitions). After this, a new line entitled <quote>FREE SPACE</quote> should appear in the table under the selected disk."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1074
+#: using-d-i.xml:1082
 #, no-c-format
 msgid "If you select some free space, you will have the opportunity to create a new partition. You will have to answer a quick series of questions about its size, type (primary or logical), and location (beginning or end of the free space). After this, you will be presented with a detailed overview of your new partition. The main setting is <guimenuitem>Use as:</guimenuitem>, which determines if the partition will have a file system on it, or be used for swap, software RAID, LVM, an encrypted file system, or not be used at all. Other settings include mountpoint, mount options, and bootable flag; which settings are shown depends on how the partition is to be used. If you don't like the preselected defaults, feel free to change them to your liking. E.g. by selecting the option <guimenuitem>Use as:</guimenuitem>, you can choose a different filesystem for this partition, including options to use the partition for swap, software RAID, LVM, or not use it at all. Another nice feature is the ability to copy data from an existing partition onto this one. When you are satisfied with your new partition, select <guimenuitem>Done setting up the partition</guimenuitem> and you will return to <command>partman</command>'s main screen."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1096
+#: using-d-i.xml:1104
 #, no-c-format
 msgid "If you decide you want to change something about your partition, simply select the partition, which will bring you to the partition configuration menu. This is the same screen as is used when creating a new partition, so you can change the same settings. One thing that may not be very obvious at a first glance is that you can resize the partition by selecting the item displaying the size of the partition. Filesystems known to work are at least fat16, fat32, ext2, ext3 and swap. This menu also allows you to delete a partition."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1107
+#: using-d-i.xml:1115
 #, no-c-format
 msgid "Be sure to create at least two partitions: one for the <emphasis>root</emphasis> filesystem (which must be mounted as <filename>/</filename>) and one for <emphasis>swap</emphasis>. If you forget to mount the root filesystem, <command>partman</command> won't let you continue until you correct this issue."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1115
+#: using-d-i.xml:1123
 #, no-c-format
 msgid "If you forget to select and format an EFI boot partition, <command>partman</command> will detect this and will not let you continue until you allocate one."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1121
+#: using-d-i.xml:1129
 #, no-c-format
 msgid "Capabilities of <command>partman</command> can be extended with installer modules, but are dependent on your system's architecture. So if you can't see all promised goodies, check if you have loaded all required modules (e.g. <filename>partman-ext3</filename>, <filename>partman-xfs</filename>, or <filename>partman-lvm</filename>)."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1129
+#: using-d-i.xml:1137
 #, no-c-format
 msgid "After you are satisfied with partitioning, select <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the partitioning menu. You will be presented with a summary of changes made to the disks and asked to confirm that the filesystems should be created as requested."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:1157
+#: using-d-i.xml:1165
 #, no-c-format
 msgid "Configuring Multidisk Devices (Software RAID)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1158
+#: using-d-i.xml:1166
 #, no-c-format
 msgid "If you have more than one harddrive<footnote><para> To be honest, you can construct MD device even from partitions residing on single physical drive, but that won't bring you anything useful. </para></footnote> in your computer, you can use <command>mdcfg</command> to setup your drives for increased performance and/or better reliability of your data. The result is called <firstterm>Multidisk Device</firstterm> (or after its most famous variant <firstterm>software RAID</firstterm>)."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1172
+#: using-d-i.xml:1180
 #, no-c-format
 msgid "MD is basically a bunch of partitions located on different disks and combined together to form a <emphasis>logical</emphasis> device. This device can then be used like an ordinary partition (i.e. in <command>partman</command> you can format it, assign a mountpoint, etc.)."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1180
+#: using-d-i.xml:1188
 #, no-c-format
 msgid "What benefits this brings depends on the type of MD device you are creating. Currently supported are: <variablelist> <varlistentry> <term>RAID0</term><listitem><para> Is mainly aimed at performance. RAID0 splits all incoming data into <firstterm>stripes</firstterm> and distributes them equally over each disk in the array. This can increase the speed of read/write operations, but when one of the disks fails, you will lose <emphasis>everything</emphasis> (part of the information is still on the healthy disk(s), the other part <emphasis>was</emphasis> on the failed disk). </para><para> The typical use for RAID0 is a partition for video editing. </para></listitem> </varlistentry> <varlistentry> <term>RAID1</term><listitem><para> Is suitable for setups where reliability is the first concern. It consists of several (usually two) equally-sized partitions where every partition contains exactly the same data. This essentially means three things. First, if one of your disks fails, you still have the data mirrored on the remaining disks. Second, you can use only a fraction of the available capacity (more precisely, it is the size of the smallest partition in the RAID). Third, file-reads are load-balanced among the disks, which can improve performance on a server, such as a file server, that tends to be loaded with more disk reads than writes. </para><para> Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para></listitem> </varlistentry> <varlistentry> <term>RAID5</term><listitem><para> Is a good compromise between speed, reliability and data redundancy. RAID5 splits all incoming data into stripes and distributes them equally on all but one disk (similar to RAID0). Unlike RAID0, RAID5 also computes <firstterm>parity</firstterm> information, which gets written on the remaining disk. The parity disk is not static (that would be called RAID4), but is changing periodically, so the parity information is distributed equally on all disks. When one of the disks fails, the missing part of information can be computed from remaining data and its parity. RAID5 must consist of at least three active partitions. Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para><para> As you can see, RAID5 has a similar degree of reliability to RAID1 while achieving less redundancy. On the other hand, it might be a bit slower on write operations than RAID0 due to computation of parity information. </para></listitem> </varlistentry> <varlistentry> <term>RAID6</term><listitem><para> Is similar to RAID5 except that it uses two parity devices instead of one. </para><para> A RAID6 array can survive up to two disk failures. </para></listitem> </varlistentry> <varlistentry> <term>RAID10</term><listitem><para> RAID10 combines striping (as in RAID0) and mirroring (as in RAID1). It creates <replaceable>n</replaceable> copies of incoming data and distributes them across the partitions so that none of the copies of the same data are on the same device. The default value of <replaceable>n</replaceable> is 2, but it can be set to something else in expert mode. The number of partitions used must be at least <replaceable>n</replaceable>. RAID10 has different layouts for distributing the copies. The default is near copies. Near copies have all of the copies at about the same offset on all of the disks. Far copies have the copies at different offsets on the disks. Offset copies copy the stripe, not the individual copies. </para><para> RAID10 can be used to achieve reliability and redundancy without the drawback of having to calculate parity. </para></listitem> </varlistentry> </variablelist> To sum it up:"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1294
+#: using-d-i.xml:1302
 #, no-c-format
 msgid "Type"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1295
+#: using-d-i.xml:1303
 #, no-c-format
 msgid "Minimum Devices"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1296
+#: using-d-i.xml:1304
 #, no-c-format
 msgid "Spare Device"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1297
+#: using-d-i.xml:1305
 #, no-c-format
 msgid "Survives disk failure?"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1298
+#: using-d-i.xml:1306
 #, no-c-format
 msgid "Available Space"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1304
+#: using-d-i.xml:1312
 #, no-c-format
 msgid "RAID0"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1305 using-d-i.xml:1313 using-d-i.xml:1343
+#: using-d-i.xml:1313 using-d-i.xml:1321 using-d-i.xml:1351
 #, no-c-format
 msgid "<entry>2</entry>"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1306 using-d-i.xml:1307
+#: using-d-i.xml:1314 using-d-i.xml:1315
 #, no-c-format
 msgid "<entry>no</entry>"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1308
+#: using-d-i.xml:1316
 #, no-c-format
 msgid "Size of the smallest partition multiplied by number of devices in RAID"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1312
+#: using-d-i.xml:1320
 #, no-c-format
 msgid "RAID1"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1314 using-d-i.xml:1322 using-d-i.xml:1333 using-d-i.xml:1344
+#: using-d-i.xml:1322 using-d-i.xml:1330 using-d-i.xml:1341 using-d-i.xml:1352
 #, no-c-format
 msgid "optional"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1315 using-d-i.xml:1323 using-d-i.xml:1334 using-d-i.xml:1345
+#: using-d-i.xml:1323 using-d-i.xml:1331 using-d-i.xml:1342 using-d-i.xml:1353
 #, no-c-format
 msgid "<entry>yes</entry>"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1316
+#: using-d-i.xml:1324
 #, no-c-format
 msgid "Size of the smallest partition in RAID"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1320
+#: using-d-i.xml:1328
 #, no-c-format
 msgid "RAID5"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1321
+#: using-d-i.xml:1329
 #, no-c-format
 msgid "<entry>3</entry>"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1324
+#: using-d-i.xml:1332
 #, no-c-format
 msgid "Size of the smallest partition multiplied by (number of devices in RAID minus one)"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1331
+#: using-d-i.xml:1339
 #, no-c-format
 msgid "RAID6"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1332
+#: using-d-i.xml:1340
 #, no-c-format
 msgid "<entry>4</entry>"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1335
+#: using-d-i.xml:1343
 #, no-c-format
 msgid "Size of the smallest partition multiplied by (number of devices in RAID minus two)"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1342
+#: using-d-i.xml:1350
 #, no-c-format
 msgid "RAID10"
 msgstr ""
 
 #. Tag: entry
-#: using-d-i.xml:1346
+#: using-d-i.xml:1354
 #, no-c-format
 msgid "Total of all partitions divided by the number of chunk copies (defaults to two)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1353
+#: using-d-i.xml:1361
 #, no-c-format
 msgid "If you want to know more about Software RAID, have a look at <ulink url=\"&url-software-raid-howto;\">Software RAID HOWTO</ulink>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1358
+#: using-d-i.xml:1366
 #, no-c-format
 msgid "To create a MD device, you need to have the desired partitions it should consist of marked for use in a RAID. (This is done in <command>partman</command> in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for RAID</guimenuitem> </menuchoice>.)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1367
+#: using-d-i.xml:1375
 #, no-c-format
 msgid "Make sure that the system can be booted with the partitioning scheme you are planning. In general it will be necessary to create a separate file system for <filename>/boot</filename> when using RAID for the root (<filename>/</filename>) file system. Most boot loaders <phrase arch=\"x86\">(including lilo and grub)</phrase> do support mirrored (not striped!) RAID1, so using for example RAID5 for <filename>/</filename> and RAID1 for <filename>/boot</filename> can be an option."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1379
+#: using-d-i.xml:1387
 #, no-c-format
 msgid "Support for MD is a relatively new addition to the installer. You may experience problems for some RAID levels and in combination with some bootloaders if you try to use MD for the root (<filename>/</filename>) file system. For experienced users, it may be possible to work around some of these problems by executing some configuration or installation steps manually from a shell."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1388
+#: using-d-i.xml:1396
 #, no-c-format
 msgid "Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> from the main <command>partman</command> menu. (The menu will only appear after you mark at least one partition for use as <guimenuitem>physical volume for RAID</guimenuitem>.) On the first screen of <command>mdcfg</command> simply select <guimenuitem>Create MD device</guimenuitem>. You will be presented with a list of supported types of MD devices, from which you should choose one (e.g. RAID1). What follows depends on the type of MD you selected."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1401
+#: using-d-i.xml:1409
 #, no-c-format
 msgid "RAID0 is simple &mdash; you will be issued with the list of available RAID partitions and your only task is to select the partitions which will form the MD."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1408
+#: using-d-i.xml:1416
 #, no-c-format
 msgid "RAID1 is a bit more tricky. First, you will be asked to enter the number of active devices and the number of spare devices which will form the MD. Next, you need to select from the list of available RAID partitions those that will be active and then those that will be spare. The count of selected partitions must be equal to the number provided few seconds ago. Don't worry. If you make a mistake and select different number of partitions, the &d-i; won't let you continue until you correct the issue."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1420
+#: using-d-i.xml:1428
 #, no-c-format
 msgid "RAID5 has a similar setup procedure as RAID1 with the exception that you need to use at least <emphasis>three</emphasis> active partitions."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1426
+#: using-d-i.xml:1434
 #, no-c-format
 msgid "RAID6 also has a similar setup procedure as RAID1 except that at least <emphasis>four</emphasis> active partitions are required."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1432
+#: using-d-i.xml:1440
 #, no-c-format
 msgid "RAID10 again has a similar setup procedure as RAID1 except in expert mode. In expert mode, &d-i; will ask you for the layout. The layout has two parts. The first part is the layout type. It is either <literal>n</literal> (for near copies), <literal>f</literal> (for far copies), or <literal>o</literal> (for offset copies). The second part is the number of copies to make of the data. There must be at least that many active devices so that all of the copies can be distributed onto different disks."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1446
+#: using-d-i.xml:1454
 #, no-c-format
 msgid "It is perfectly possible to have several types of MD at once. For example, if you have three 200 GB hard drives dedicated to MD, each containing two 100 GB partitions, you can combine the first partitions on all three disks into the RAID0 (fast 300 GB video editing partition) and use the other three partitions (2 active and 1 spare) for RAID1 (quite reliable 100 GB partition for <filename>/home</filename>)."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1455
+#: using-d-i.xml:1463
 #, no-c-format
 msgid "After you setup MD devices to your liking, you can <guimenuitem>Finish</guimenuitem> <command>mdcfg</command> to return back to the <command>partman</command> to create filesystems on your new MD devices and assign them the usual attributes like mountpoints."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:1470
+#: using-d-i.xml:1478
 #, no-c-format
 msgid "Configuring the Logical Volume Manager (LVM)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1471
+#: using-d-i.xml:1479
 #, no-c-format
 msgid "If you are working with computers at the level of system administrator or <quote>advanced</quote> user, you have surely seen the situation where some disk partition (usually the most important one) was short on space, while some other partition was grossly underused and you had to manage this situation with moving stuff around, symlinking, etc."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1479
+#: using-d-i.xml:1487
 #, no-c-format
 msgid "To avoid the described situation you can use Logical Volume Manager (LVM). Simply said, with LVM you can combine your partitions (<firstterm>physical volumes</firstterm> in LVM lingo) to form a virtual disk (so called <firstterm>volume group</firstterm>), which can then be divided into virtual partitions (<firstterm>logical volumes</firstterm>). The point is that logical volumes (and of course underlying volume groups) can span across several physical disks."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1489
+#: using-d-i.xml:1497
 #, no-c-format
 msgid "Now when you realize you need more space for your old 160GB <filename>/home</filename> partition, you can simply add a new 300GB disk to the computer, join it with your existing volume group and then resize the logical volume which holds your <filename>/home</filename> filesystem and voila &mdash; your users have some room again on their renewed 460GB partition. This example is of course a bit oversimplified. If you haven't read it yet, you should consult the <ulink url=\"&url-lvm-howto;\">LVM HOWTO</ulink>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1500
+#: using-d-i.xml:1508
 #, no-c-format
 msgid "LVM setup in &d-i; is quite simple and completely supported inside <command>partman</command>. First, you have to mark the partition(s) to be used as physical volumes for LVM. This is done in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for LVM</guimenuitem> </menuchoice>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1509
+#: using-d-i.xml:1517
 #, no-c-format
 msgid "When you return to the main <command>partman</command> screen, you will see a new option <guimenuitem>Configure the Logical Volume Manager</guimenuitem>. When you select that, you will first be asked to confirm pending changes to the partition table (if any) and after that the LVM configuration menu will be shown. Above the menu a summary of the LVM configuration is shown. The menu itself is context sensitive and only shows valid actions. The possible actions are:"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1520
+#: using-d-i.xml:1528
 #, no-c-format
 msgid "<guimenuitem>Display configuration details</guimenuitem>: shows LVM device structure, names and sizes of logical volumes and more"
 msgstr ""
 
 #. Tag: guimenuitem
-#: using-d-i.xml:1525
+#: using-d-i.xml:1533
 #, no-c-format
 msgid "Create volume group"
 msgstr ""
 
 #. Tag: guimenuitem
-#: using-d-i.xml:1528
+#: using-d-i.xml:1536
 #, no-c-format
 msgid "Create logical volume"
 msgstr ""
 
 #. Tag: guimenuitem
-#: using-d-i.xml:1531
+#: using-d-i.xml:1539
 #, no-c-format
 msgid "Delete volume group"
 msgstr ""
 
 #. Tag: guimenuitem
-#: using-d-i.xml:1534
+#: using-d-i.xml:1542
 #, no-c-format
 msgid "Delete logical volume"
 msgstr ""
 
 #. Tag: guimenuitem
-#: using-d-i.xml:1537
+#: using-d-i.xml:1545
 #, no-c-format
 msgid "Extend volume group"
 msgstr ""
 
 #. Tag: guimenuitem
-#: using-d-i.xml:1540
+#: using-d-i.xml:1548
 #, no-c-format
 msgid "Reduce volume group"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1542
+#: using-d-i.xml:1550
 #, no-c-format
 msgid "<guimenuitem>Finish</guimenuitem>: return to the main <command>partman</command> screen"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1548
+#: using-d-i.xml:1556
 #, no-c-format
 msgid "Use the options in that menu to first create a volume group and then create your logical volumes inside it."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1553
+#: using-d-i.xml:1561
 #, no-c-format
 msgid "After you return to the main <command>partman</command> screen, any created logical volumes will be displayed in the same way as ordinary partitions (and you should treat them as such)."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:1567
+#: using-d-i.xml:1575
 #, no-c-format
 msgid "Configuring Encrypted Volumes"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1568
+#: using-d-i.xml:1576
 #, no-c-format
 msgid "&d-i; allows you to set up encrypted partitions. Every file you write to such a partition is immediately saved to the device in encrypted form. Access to the encrypted data is granted only after entering the <firstterm>passphrase</firstterm> used when the encrypted partition was originally created. This feature is useful to protect sensitive data in case your laptop or hard drive gets stolen. The thief might get physical access to the hard drive, but without knowing the right passphrase, the data on the hard drive will look like random characters."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1580
+#: using-d-i.xml:1588
 #, no-c-format
 msgid "The two most important partitions to encrypt are: the home partition, where your private data resides, and the swap partition, where sensitive data might be stored temporarily during operation. Of course, nothing prevents you from encrypting any other partitions that might be of interest. For example <filename>/var</filename> where database servers, mail servers or print servers store their data, or <filename>/tmp</filename> which is used by various programs to store potentially interesting temporary files. Some people may even want to encrypt their whole system. The only exception is the <filename>/boot</filename> partition which must remain unencrypted, because currently there is no way to load the kernel from an encrypted partition."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1595
+#: using-d-i.xml:1603
 #, no-c-format
 msgid "Please note that the performance of encrypted partitions will be less than that of unencrypted ones because the data needs to be decrypted or encrypted for every read or write. The performance impact depends on your CPU speed, chosen cipher and a key length."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1602
+#: using-d-i.xml:1610
 #, no-c-format
 msgid "To use encryption, you have to create a new partition by selecting some free space in the main partitioning menu. Another option is to choose an existing partition (e.g. a regular partition, an LVM logical volume or a RAID volume). In the <guimenu>Partition settings</guimenu> menu, you need to select <guimenuitem>physical volume for encryption</guimenuitem> at the <menuchoice> <guimenu>Use as:</guimenu> </menuchoice> option. The menu will then change to include several cryptographic options for the partition."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1613
+#: using-d-i.xml:1621
 #, no-c-format
 msgid "&d-i; supports several encryption methods. The default method is <firstterm>dm-crypt</firstterm> (included in newer Linux kernels, able to host LVM physical volumes), the other is <firstterm>loop-AES</firstterm> (older, maintained separately from the Linux kernel tree). Unless you have compelling reasons to do otherwise, it is recommended to use the default."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1625
+#: using-d-i.xml:1633
 #, no-c-format
 msgid "First, let's have a look at the options available when you select <userinput>Device-mapper (dm-crypt)</userinput> as the encryption method. As always: when in doubt, use the defaults, because they have been carefully chosen with security in mind."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:1635
+#: using-d-i.xml:1643
 #, no-c-format
 msgid "Encryption: <userinput>aes</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1637
+#: using-d-i.xml:1645
 #, no-c-format
 msgid "This option lets you select the encryption algorithm (<firstterm>cipher</firstterm>) which will be used to encrypt the data on the partition. &d-i; currently supports the following block ciphers: <firstterm>aes</firstterm>, <firstterm>blowfish</firstterm>, <firstterm>serpent</firstterm>, and <firstterm>twofish</firstterm>. It is beyond the scope of this document to discuss the qualities of these different algorithms, however, it might help your decision to know that in 2000, <emphasis>AES</emphasis> was chosen by the American National Institute of Standards and Technology as the standard encryption algorithm for protecting sensitive information in the 21st century."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:1655
+#: using-d-i.xml:1663
 #, no-c-format
 msgid "Key size: <userinput>256</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1657
+#: using-d-i.xml:1665
 #, no-c-format
 msgid "Here you can specify the length of the encryption key. With a larger key size, the strength of the encryption is generally improved. On the other hand, increasing the length of the key usually has a negative impact on performance. Available key sizes vary depending on the cipher."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:1669
+#: using-d-i.xml:1677
 #, no-c-format
 msgid "IV algorithm: <userinput>cbc-essiv:sha256</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1671
+#: using-d-i.xml:1679
 #, no-c-format
 msgid "The <firstterm>Initialization Vector</firstterm> or <firstterm>IV</firstterm> algorithm is used in cryptography to ensure that applying the cipher on the same <firstterm>clear text</firstterm> data with the same key always produces a unique <firstterm>cipher text</firstterm>. The idea is to prevent the attacker from deducing information from repeated patterns in the encrypted data."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1681
+#: using-d-i.xml:1689
 #, no-c-format
 msgid "From the provided alternatives, the default <userinput>cbc-essiv:sha256</userinput> is currently the least vulnerable to known attacks. Use the other alternatives only when you need to ensure compatibility with some previously installed system that is not able to use newer algorithms."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:1693
+#: using-d-i.xml:1701
 #, no-c-format
 msgid "Encryption key: <userinput>Passphrase</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1695
+#: using-d-i.xml:1703
 #, no-c-format
 msgid "Here you can choose the type of the encryption key for this partition."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:1701
+#: using-d-i.xml:1709
 #, no-c-format
 msgid "Passphrase"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1702
+#: using-d-i.xml:1710
 #, no-c-format
 msgid "The encryption key will be computed<footnote> <para> Using a passphrase as the key currently means that the partition will be set up using <ulink url=\"&url-luks;\">LUKS</ulink>. </para></footnote> on the basis of a passphrase which you will be able to enter later in the process."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:1717 using-d-i.xml:1810
+#: using-d-i.xml:1725 using-d-i.xml:1818
 #, no-c-format
 msgid "Random key"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1718
+#: using-d-i.xml:1726
 #, no-c-format
 msgid "A new encryption key will be generated from random data each time you try to bring up the encrypted partition. In other words: on every shutdown the content of the partition will be lost as the key is deleted from memory. (Of course, you could try to guess the key with a brute force attack, but unless there is an unknown weakness in the cipher algorithm, it is not achievable in our lifetime.)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1727
+#: using-d-i.xml:1735
 #, no-c-format
 msgid "Random keys are useful for swap partitions because you do not need to bother yourself with remembering the passphrase or wiping sensitive information from the swap partition before shutting down your computer. However, it also means that you will <emphasis>not</emphasis> be able to use the <quote>suspend-to-disk</quote> functionality offered by newer Linux kernels as it will be impossible (during a subsequent boot) to recover the suspended data written to the swap partition."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:1746 using-d-i.xml:1823
+#: using-d-i.xml:1754 using-d-i.xml:1831
 #, no-c-format
 msgid "Erase data: <userinput>yes</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1748
+#: using-d-i.xml:1756
 #, no-c-format
 msgid "Determines whether the content of this partition should be overwritten with random data before setting up the encryption. This is recommended because it might otherwise be possible for an attacker to discern which parts of the partition are in use and which are not. In addition, this will make it harder to recover any leftover data from previous installations<footnote><para> It is believed that the guys from three-letter agencies can restore the data even after several rewrites of the magnetooptical media, though. </para></footnote>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1768
+#: using-d-i.xml:1776
 #, no-c-format
 msgid "If you select <menuchoice> <guimenu>Encryption method:</guimenu> <guimenuitem>Loopback (loop-AES)</guimenuitem> </menuchoice>, the menu changes to provide the following options:"
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:1777
+#: using-d-i.xml:1785
 #, no-c-format
 msgid "Encryption: <userinput>AES256</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1779
+#: using-d-i.xml:1787
 #, no-c-format
 msgid "For loop-AES, unlike dm-crypt, the options for cipher and key size are combined, so you can select both at the same time. Please see the above sections on ciphers and key sizes for further information."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:1789
+#: using-d-i.xml:1797
 #, no-c-format
 msgid "Encryption key: <userinput>Keyfile (GnuPG)</userinput>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1791
+#: using-d-i.xml:1799
 #, no-c-format
 msgid "Here you can select the type of the encryption key for this partition."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:1797
+#: using-d-i.xml:1805
 #, no-c-format
 msgid "Keyfile (GnuPG)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1798
+#: using-d-i.xml:1806
 #, no-c-format
 msgid "The encryption key will be generated from random data during the installation. Moreover this key will be encrypted with <application>GnuPG</application>, so to use it, you will need to enter the proper passphrase (you will be asked to provide one later in the process)."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1811
+#: using-d-i.xml:1819
 #, no-c-format
 msgid "Please see the section on random keys above."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1825
+#: using-d-i.xml:1833
 #, no-c-format
 msgid "Please see the the section on erasing data above."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1834
+#: using-d-i.xml:1842
 #, no-c-format
 msgid "After you have selected the desired parameters for your encrypted partitions, return back to the main partitioning menu. There should now be a new menu item called <guimenu>Configure encrypted volumes</guimenu>. After you select it, you will be asked to confirm the deletion of data on partitions marked to be erased and possibly other actions such as writing a new partition table. For large partitions this might take some time."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1844
+#: using-d-i.xml:1852
 #, no-c-format
 msgid "Next you will be asked to enter a passphrase for partitions configured to use one. Good passphrases should be longer than 8 characters, should be a mixture of letters, numbers and other characters and should not contain common dictionary words or information easily associable with you (such as birthdates, hobbies, pet names, names of family members or relatives, etc.)."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1853
+#: using-d-i.xml:1861
 #, no-c-format
 msgid "Before you input any passphrases, you should have made sure that your keyboard is configured correctly and generates the expected characters. If you are unsure, you can switch to the second virtual console and type some text at the prompt. This ensures that you won't be surprised later, e.g. by trying to input a passphrase using a qwerty keyboard layout when you used an azerty layout during the installation. This situation can have several causes. Maybe you switched to another keyboard layout during the installation, or the selected keyboard layout might not have been set up yet when entering the passphrase for the root file system."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1866
+#: using-d-i.xml:1874
 #, no-c-format
 msgid "If you selected to use methods other than a passphrase to create encryption keys, they will be generated now. Because the kernel may not have gathered a sufficient amount of entropy at this early stage of the installation, the process may take a long time. You can help speed up the process by generating entropy: e.g. by pressing random keys, or by switching to the shell on the second virtual console and generating some network and disk traffic (downloading some files, feeding big files into <filename>/dev/null</filename>, etc.). This will be repeated for each partition to be encrypted."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1882
+#: using-d-i.xml:1890
 #, no-c-format
 msgid ""
       "After returning to the main partitioning menu, you will see all encrypted volumes as additional partitions which can be configured in the same way as ordinary partitions. The following example shows two different volumes. The first one is encrypted via dm-crypt, the second one via loop-AES. <informalexample><screen>\n"
@@ -1500,607 +1506,607 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1895
+#: using-d-i.xml:1903
 #, no-c-format
 msgid "One thing to note here are the identifiers in parentheses (<replaceable>sda2_crypt</replaceable> and <replaceable>loop0</replaceable> in this case) and the mount points you assigned to each encrypted volume. You will need this information later when booting the new system. The differences between ordinary boot process and boot process with encryption involved will be covered later in <xref linkend=\"mount-encrypted-volumes\"/>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1905
+#: using-d-i.xml:1913
 #, no-c-format
 msgid "Once you are satisfied with the partitioning scheme, continue with the installation."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:1916
+#: using-d-i.xml:1924
 #, no-c-format
 msgid "Installing the Base System"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1917
+#: using-d-i.xml:1925
 #, no-c-format
 msgid "Although this stage is the least problematic, it consumes a significant fraction of the install because it downloads, verifies and unpacks the whole base system. If you have a slow computer or network connection, this could take some time."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1930
+#: using-d-i.xml:1938
 #, no-c-format
 msgid "During installation of the base system, package unpacking and setup messages are redirected to <userinput>tty4</userinput>. You can access this terminal by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo>; get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1939
+#: using-d-i.xml:1947
 #, no-c-format
 msgid "The unpack/setup messages generated during this phase are also saved in <filename>/var/log/syslog</filename>. You can check them there if the installation is performed over a serial console."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1945
+#: using-d-i.xml:1953
 #, no-c-format
 msgid "As part of the installation, a Linux kernel will be installed. At the default priority, the installer will choose one for you that best matches your hardware. In lower priority modes, you will be able to choose from a list of available kernels."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:1957
+#: using-d-i.xml:1965
 #, no-c-format
 msgid "Setting Up Users And Passwords"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1958
+#: using-d-i.xml:1966
 #, no-c-format
 msgid "After the base system has been installed, the installer will allow you to set up the <quote>root</quote> account and/or an account for the first user. Other user accounts can be created after the installation has been completed."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:1972
+#: using-d-i.xml:1980
 #, no-c-format
 msgid "Set the Root Password"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1976
+#: using-d-i.xml:1984
 #, no-c-format
 msgid "The <emphasis>root</emphasis> account is also called the <emphasis>super-user</emphasis>; it is a login that bypasses all security protection on your system. The root account should only be used to perform system administration, and only used for as short a time as possible."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1984
+#: using-d-i.xml:1992
 #, no-c-format
 msgid "Any password you create should contain at least 6 characters, and should contain both upper- and lower-case characters, as well as punctuation characters. Take extra care when setting your root password, since it is such a powerful account. Avoid dictionary words or use of any personal information which could be guessed."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:1992
+#: using-d-i.xml:2000
 #, no-c-format
 msgid "If anyone ever tells you they need your root password, be extremely wary. You should normally never give your root password out, unless you are administering a machine with more than one system administrator."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2002
+#: using-d-i.xml:2010
 #, no-c-format
 msgid "Create an Ordinary User"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2004
+#: using-d-i.xml:2012
 #, no-c-format
 msgid "The system will ask you whether you wish to create an ordinary user account at this point. This account should be your main personal log-in. You should <emphasis>not</emphasis> use the root account for daily use or as your personal login."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2013
+#: using-d-i.xml:2021
 #, no-c-format
 msgid "Why not? Well, one reason to avoid using root's privileges is that it is very easy to do irreparable damage as root. Another reason is that you might be tricked into running a <emphasis>Trojan-horse</emphasis> program &mdash; that is a program that takes advantage of your super-user powers to compromise the security of your system behind your back. Any good book on Unix system administration will cover this topic in more detail &mdash; consider reading one if it is new to you."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2023
+#: using-d-i.xml:2031
 #, no-c-format
 msgid "You will first be prompted for the user's full name. Then you'll be asked for a name for the user account; generally your first name or something similar will suffice and indeed will be the default. Finally, you will be prompted for a password for this account."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2030
+#: using-d-i.xml:2038
 #, no-c-format
 msgid "If at any point after installation you would like to create another account, use the <command>adduser</command> command."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2041
+#: using-d-i.xml:2049
 #, no-c-format
 msgid "Installing Additional Software"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2042
+#: using-d-i.xml:2050
 #, no-c-format
 msgid "At this point you have a usable but limited system. Most users will want to install additional software on the system to tune it to their needs, and the installer allows you do so. This step can take even longer than installing the base system if you have a slow computer or network connection."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2057
+#: using-d-i.xml:2065
 #, no-c-format
 msgid "Configuring apt"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2059
+#: using-d-i.xml:2067
 #, no-c-format
 msgid "One of the tools used to install packages on a &debian; system is a program called <command>apt-get</command>, from the <classname>apt</classname> package<footnote> <para> Note that the program which actually installs the packages is called <command>dpkg</command>. However, this program is more of a low-level tool. <command>apt-get</command> is a higher-level tool, which will invoke <command>dpkg</command> as appropriate. It knows how to retrieve packages from your CD, the network, or wherever. It is also able to automatically install other packages which are required to make the package you're trying to install work correctly. </para> </footnote>. Other front-ends for package management, like <command>aptitude</command> and <command>synaptic</command>, are also in use. These front-ends are recommended for new users, since they integrate some additional features (package searching and status checks) in a nice user interface. In fact, <command>aptitude</command> is now the recommended utility for package management."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2083
+#: using-d-i.xml:2091
 #, no-c-format
 msgid "<command>apt</command> must be configured so that it knows from where to retrieve packages. The results of this configuration are written to the file <filename>/etc/apt/sources.list</filename>. You can examine and edit this file to your liking after the installation is complete."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2090
+#: using-d-i.xml:2098
 #, no-c-format
 msgid "If you are installing at default priority, the installer will largely take care of the configuration automatically, based on the installation method you are using and possibly using choices made earlier in the installation. In most cases the installer will automatically add a security mirror and, if you are installing the stable distribution, a mirror for the <quote>volatile</quote> update service."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2099
+#: using-d-i.xml:2107
 #, no-c-format
 msgid "If you are installing at a lower priority (e.g. in expert mode), you will be able to make more decisions yourself. You can choose whether or not to use the security and/or volatile update services, and you can choose to add packages from the <quote>contrib</quote> and <quote>non-free</quote> sections of the archive."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2110
+#: using-d-i.xml:2118
 #, no-c-format
 msgid "Installing from more than one CD or DVD"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2112
+#: using-d-i.xml:2120
 #, no-c-format
 msgid "If you are installing from a CD or a DVD that is part of a larger set, the installer will ask if you want to scan additional CDs or DVDs. If you have additional CDs or DVDs available, you probably want to do this so the installer can use the packages included on them."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2119
+#: using-d-i.xml:2127
 #, no-c-format
 msgid "If you do not have any additional CDs or DVDs, that is no problem: using them is not required. If you also do not use a network mirror (as explained in the next section), it can mean that not all packages belonging to the tasks you select in the next step of the installation can be installed."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2127
+#: using-d-i.xml:2135
 #, no-c-format
 msgid "Packages are included on CDs (and DVDs) in the order of their popularity. This means that for most uses only the first CDs in a set are needed and that only very few people actually use any of the packages included on the last CDs in a set."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2134
+#: using-d-i.xml:2142
 #, no-c-format
 msgid "It also means that buying or downloading and burning a full CD set is just a waste of money as you'll never use most of them. In most cases you are better off getting only the first 3 to 8 CDs and installing any additional packages you may need from the Internet by using a mirror. The same goes for DVD sets: the first DVD, or maybe the first two DVDs will cover most needs."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2143
+#: using-d-i.xml:2151
 #, no-c-format
 msgid "A good rule of thumb is that for a regular desktop installation (using the GNOME desktop environment) only the first three CDs are needed. For the alternative desktop environments (KDE or Xfce), additional CDs are needed. The first DVD easily covers all three desktop environments."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2151
+#: using-d-i.xml:2159
 #, no-c-format
 msgid "If you do scan multiple CDs or DVDs, the installer will prompt you to exchange them when it needs packages from another CD/DVD than the one currently in the drive. Note that only CDs or DVDs that belong to the same set should be scanned. The order in which they are scanned does not really matter, but scanning them in ascending order will reduce the chance of mistakes."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2164
+#: using-d-i.xml:2172
 #, no-c-format
 msgid "Using a network mirror"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2166
+#: using-d-i.xml:2174
 #, no-c-format
 msgid "One question that will be asked during most installs is whether or not to use a network mirror as a source for packages. In most cases the default answer should be fine, but there are some exceptions."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2172
+#: using-d-i.xml:2180
 #, no-c-format
 msgid "If you are <emphasis>not</emphasis> installing from a full CD or DVD or using a full CD/DVD image, you really should use a network mirror as otherwise you will end up with only a very minimal system. However, if you have a limited Internet connection it is best <emphasis>not</emphasis> to select the <literal>desktop</literal> task in the next step of the installation."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2181
+#: using-d-i.xml:2189
 #, no-c-format
 msgid "If you are installing from a single full CD or using a full CD image, using a network mirror is not required, but is still strongly recommended because a single CD contains only a fairly limited number of packages. If you have a limited Internet connection it may still be best to <emphasis>not</emphasis> select a network mirror here, but to finish the installation using only what's available on the CD and selectively install additional packages after the installation (i.e. after you have rebooted into the new system)."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2192
+#: using-d-i.xml:2200
 #, no-c-format
 msgid "If you are installing from a DVD or using a DVD image, any packages needed during the installation should be present on the first DVD. The same is true if you have scanned multiple CDs as explained in the previous section. Use of a network mirror is optional."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2199
+#: using-d-i.xml:2207
 #, no-c-format
 msgid "One advantage of adding a network mirror is that updates that have occurred since the CD/DVD set was created and have been included in a point release, will become available for installation, thus extending the life of your CD/DVD set without compromising the security or stability of the installed system."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2206
+#: using-d-i.xml:2214
 #, no-c-format
 msgid "In summary: selecting a network mirror is generally a good idea, except if you do not have a good Internet connection. If the current version of a package is available from CD/DVD, the installer will always use that. The amount of data that will be downloaded if you do select a mirror thus depends on"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2215
+#: using-d-i.xml:2223
 #, no-c-format
 msgid "the tasks you select in the next step of the installation,"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2220
+#: using-d-i.xml:2228
 #, no-c-format
 msgid "which packages are needed for those tasks,"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2225
+#: using-d-i.xml:2233
 #, no-c-format
 msgid "which of those packages are present on the CDs or DVDs you have scanned, and"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2230
+#: using-d-i.xml:2238
 #, no-c-format
 msgid "whether any updated versions of packages included on the CDs or DVDs are available from a mirror (either a regular package mirror, or a mirror for security or volatile updates)."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2239
+#: using-d-i.xml:2247
 #, no-c-format
 msgid "Note that the last point means that, even if you choose not to use a network mirror, some packages may still be downloaded from the Internet if there is a security or volatile update available for them and those services have been configured."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2255
+#: using-d-i.xml:2263
 #, no-c-format
 msgid "Selecting and Installing Software"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2257
+#: using-d-i.xml:2265
 #, no-c-format
 msgid "During the installation process, you are given the opportunity to select additional software to install. Rather than picking individual software packages from the &num-of-distrib-pkgs; available packages, this stage of the installation process focuses on selecting and installing predefined collections of software to quickly set up your computer to perform various tasks."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2266
+#: using-d-i.xml:2274
 #, no-c-format
 msgid "So, you have the ability to choose <emphasis>tasks</emphasis> first, and then add on more individual packages later. These tasks loosely represent a number of different jobs or things you want to do with your computer, such as <quote>Desktop environment</quote>, <quote>Web server</quote>, or <quote>Print server</quote><footnote> <para> You should know that to present this list, the installer is merely invoking the <command>tasksel</command> program. It can be run at any time after installation to install more packages (or remove them), or you can use a more fine-grained tool such as <command>aptitude</command>. If you are looking for a specific single package, after installation is complete, simply run <userinput>aptitude install <replaceable>package</replaceable></userinput>, where <replaceable>package</replaceable> is the name of the package you are looking for. </para> </footnote>. <xref linkend=\"tasksel-size-list\"/> lists the space requirements for the available tasks."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2293
+#: using-d-i.xml:2301
 #, no-c-format
 msgid "Some tasks may be pre-selected based on the characteristics of the computer you are installing. If you disagree with these selections you can deselect them. You can even opt to install no tasks at all at this point."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2300
+#: using-d-i.xml:2308
 #, no-c-format
 msgid "Unless you are using the special KDE or Xfce CDs, the <quote>Desktop environment</quote> task will install the GNOME desktop environment."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2307
+#: using-d-i.xml:2315
 #, no-c-format
 msgid "It is not possible to interactively select a different desktop during the installation. However, it <emphasis>is</emphasis> possible to get &d-i; to install a KDE desktop environment instead of GNOME by using preseeding (see <xref linkend=\"preseed-pkgsel\"/>) or by adding the parameter <literal>desktop=kde</literal> at the boot prompt when starting the installer. Alternatively the more lightweight Xfce desktop environment can be selected by using <literal>desktop=xfce</literal>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2317
+#: using-d-i.xml:2325
 #, no-c-format
 msgid "Note that this will only work if the packages needed for KDE or Xfce are actually available. If you are installing using a single full CD image, they will need to be downloaded from a mirror as most needed packages are only included on later CDs; installing KDE or Xfce this way should work fine if you are using a DVD image or any other installation method."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2325
+#: using-d-i.xml:2333
 #, no-c-format
 msgid "The various server tasks will install software roughly as follows. DNS server: <classname>bind9</classname>; File server: <classname>samba</classname>, <classname>nfs</classname>; Mail server: <classname>exim4</classname>, <classname>spamassassin</classname>, <classname>uw-imap</classname>; Print server: <classname>cups</classname>; SQL database: <classname>postgresql</classname>; Web server: <classname>apache2</classname>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2337
+#: using-d-i.xml:2345
 #, no-c-format
 msgid "Once you've selected your tasks, select &BTN-CONT;. At this point, <command>aptitude</command> will install the packages that are part of the tasks you've selected."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2344
+#: using-d-i.xml:2352
 #, no-c-format
 msgid "In the standard user interface of the installer, you can use the space bar to toggle selection of a task."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2350
+#: using-d-i.xml:2358
 #, no-c-format
 msgid "You should be aware that especially the Desktop task is very large. Especially when installing from a normal CD-ROM in combination with a mirror for packages not on the CD-ROM, the installer may want to retrieve a lot of packages over the network. If you have a relatively slow Internet connection, this can take a long time. There is no option to cancel the installation of packages once it has started."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2359
+#: using-d-i.xml:2367
 #, no-c-format
 msgid "Even when packages are included on the CD-ROM, the installer may still retrieve them from the mirror if the version available on the mirror is more recent than the one included on the CD-ROM. If you are installing the stable distribution, this can happen after a point release (an update of the original stable release); if you are installing the testing distribution this will happen if you are using an older image."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2368
+#: using-d-i.xml:2376
 #, no-c-format
 msgid "Each package you selected with <command>tasksel</command> is downloaded, unpacked and then installed in turn by the <command>apt-get</command> and <command>dpkg</command> programs. If a particular program needs more information from the user, it will prompt you during this process."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2381
+#: using-d-i.xml:2389
 #, no-c-format
 msgid "Making Your System Bootable"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2383
+#: using-d-i.xml:2391
 #, no-c-format
 msgid "If you are installing a diskless workstation, obviously, booting off the local disk isn't a meaningful option, and this step will be skipped. <phrase arch=\"sparc\">You may wish to set OpenBoot to boot from the network by default; see <xref linkend=\"boot-dev-select-sun\"/>.</phrase>"
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2398
+#: using-d-i.xml:2406
 #, no-c-format
 msgid "Detecting other operating systems"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2400
+#: using-d-i.xml:2408
 #, no-c-format
 msgid "Before a boot loader is installed, the installer will attempt to probe for other operating systems which are installed on the machine. If it finds a supported operating system, you will be informed of this during the boot loader installation step, and the computer will be configured to boot this other operating system in addition to Debian."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2408
+#: using-d-i.xml:2416
 #, no-c-format
 msgid "Note that multiple operating systems booting on a single machine is still something of a black art. The automatic support for detecting and setting up boot loaders to boot other operating systems varies by architecture and even by subarchitecture. If it does not work you should consult your boot manager's documentation for more information."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2426
+#: using-d-i.xml:2434
 #, no-c-format
 msgid "Install <command>aboot</command> on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2427
+#: using-d-i.xml:2435
 #, no-c-format
 msgid "If you have booted from SRM and you select this option, the installer will write <command>aboot</command> to the first sector of the disk on which you installed Debian. Be <emphasis>very</emphasis> careful &mdash; it is <emphasis>not</emphasis> possible to boot multiple operating systems (e.g. GNU/Linux, Free/Open/NetBSD, OSF/1 a.k.a. Digital Unix a.k.a. Tru64 Unix, or OpenVMS) from the same disk. If you also have a different operating system installed on the disk where you have installed Debian, you will have to boot GNU/Linux from a floppy instead."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2447
+#: using-d-i.xml:2455
 #, no-c-format
 msgid "<command>palo</command>-installer"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2448
+#: using-d-i.xml:2456
 #, no-c-format
 msgid "The bootloader on PA-RISC is <quote>palo</quote>. <command>PALO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>PALO</command> allows you to boot any kernel image on your boot partition. This is because <command>PALO</command> can actually read Linux partitions."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2457
+#: using-d-i.xml:2465
 #, no-c-format
 msgid "hppa FIXME ( need more info )"
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2469
+#: using-d-i.xml:2477
 #, no-c-format
 msgid "Install the <command>Grub</command> Boot Loader on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2471
+#: using-d-i.xml:2479
 #, no-c-format
 msgid "The main &architecture; boot loader is called <quote>grub</quote>. Grub is a flexible and robust boot loader and a good default choice for new users and old hands alike."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2477
+#: using-d-i.xml:2485
 #, no-c-format
 msgid "By default, grub will be installed into the Master Boot Record (MBR), where it will take over complete control of the boot process. If you prefer, you can install it elsewhere. See the grub manual for complete information."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2483
+#: using-d-i.xml:2491
 #, no-c-format
 msgid "If you do not want to install grub, use the &BTN-GOBACK; button to get to the main menu, and from there select whatever bootloader you would like to use."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2496
+#: using-d-i.xml:2504
 #, no-c-format
 msgid "Install the <command>LILO</command> Boot Loader on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2498
+#: using-d-i.xml:2506
 #, no-c-format
 msgid "The second &architecture; boot loader is called <quote>LILO</quote>. It is an old complex program which offers lots of functionality, including DOS, Windows, and OS/2 boot management. Please carefully read the instructions in the directory <filename>/usr/share/doc/lilo/</filename> if you have special needs; also see the <ulink url=\"&url-lilo-howto;\">LILO mini-HOWTO</ulink>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2508
+#: using-d-i.xml:2516
 #, no-c-format
 msgid "Currently the LILO installation will only create menu entries for other operating systems if these can be <firstterm>chainloaded</firstterm>. This means you may have to manually add a menu entry for operating systems like GNU/Linux and GNU/Hurd after the installation."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2516
+#: using-d-i.xml:2524
 #, no-c-format
 msgid "&d-i; offers you three choices on where to install the <command>LILO</command> boot loader:"
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:2523
+#: using-d-i.xml:2531
 #, no-c-format
 msgid "Master Boot Record (MBR)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2523
+#: using-d-i.xml:2531
 #, no-c-format
 msgid "This way the <command>LILO</command> will take complete control of the boot process."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:2530
+#: using-d-i.xml:2538
 #, no-c-format
 msgid "new Debian partition"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2530
+#: using-d-i.xml:2538
 #, no-c-format
 msgid "Choose this if you want to use another boot manager. <command>LILO</command> will install itself at the beginning of the new Debian partition and it will serve as a secondary boot loader."
 msgstr ""
 
 #. Tag: term
-#: using-d-i.xml:2539
+#: using-d-i.xml:2547
 #, no-c-format
 msgid "Other choice"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2539
+#: using-d-i.xml:2547
 #, no-c-format
 msgid "Useful for advanced users who want to install <command>LILO</command> somewhere else. In this case you will be asked for desired location. You can use traditional device names such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2549
+#: using-d-i.xml:2557
 #, no-c-format
 msgid "If you can no longer boot into Windows 9x (or DOS) after this step, you'll need to use a Windows 9x (MS-DOS) boot disk and use the <userinput>fdisk /mbr</userinput> command to reinstall the MS-DOS master boot record &mdash; however, this means that you'll need to use some other way to get back into Debian!"
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2565
+#: using-d-i.xml:2573
 #, no-c-format
 msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2567
+#: using-d-i.xml:2575
 #, no-c-format
 msgid "The &architecture; boot loader is called <quote>elilo</quote>. It is modeled on the <quote>lilo</quote> boot loader for the x86 architecture and uses a similar configuration file. However, instead of writing an MBR or partition boot record to the disk, it copies the necessary files to a separate FAT formatted disk partition and modifies the <guimenuitem>EFI Boot Manager</guimenuitem> menu in the firmware to point to the files in the EFI partition. The <command>elilo</command> boot loader is really in two parts. The <filename>/usr/sbin/elilo</filename> command manages the partition and copies files into it. The <filename>elilo.efi</filename> program is copied into the EFI partition and then run by the <quote>EFI Boot Manager</quote> to do the actual work of loading and starting the Linux kernel."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2583
+#: using-d-i.xml:2591
 #, no-c-format
 msgid "The <quote>elilo</quote> configuration and installation is done as the last step of installing the packages of the base installation. &d-i; will present you with a list of potential disk partitions that it has found suitable for an EFI partition. Select the partition you set up earlier in the installation, typically a partition on the same disk that contains your <emphasis>root</emphasis> filesystem."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2595
+#: using-d-i.xml:2603
 #, no-c-format
 msgid "Choose the correct partition!"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2597
+#: using-d-i.xml:2605
 #, no-c-format
 msgid "The criteria for selecting a partition is that it is FAT format filesystem with its <emphasis>boot</emphasis> flag set. &d-i; may show multiple choices depending on what it finds from scanning all of the disks of the system including EFI partitions of other system disks and EFI diagnostic partitions. Remember, <command>elilo</command> may format the partition during the installation, erasing any previous contents!"
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2612
+#: using-d-i.xml:2620
 #, no-c-format
 msgid "EFI Partition Contents"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2614
+#: using-d-i.xml:2622
 #, no-c-format
 msgid "The EFI partition is a FAT filesystem format partition on one of the hard disks of the system, usually the same disk that contains the <emphasis>root</emphasis> filesystem. It is normally not mounted on a running system as it is only needed by the <quote>EFI Boot Manager</quote> to load the system and the installer part of the <command>elilo</command> writes to the filesystem directly. The <command>/usr/sbin/elilo</command> utility writes the following files into the <filename>efi/debian</filename> directory of the EFI partition during the installation. Note that the <quote>EFI Boot Manager</quote> would find these files using the path <filename>fs<replaceable>n</replaceable>:\\efi\\debian</filename>. There may be other files in this filesystem as well over time as the system is updated or re-configured."
 msgstr ""
 
 #. Tag: filename
-#: using-d-i.xml:2636
+#: using-d-i.xml:2644
 #, no-c-format
 msgid "elilo.conf"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2637
+#: using-d-i.xml:2645
 #, no-c-format
 msgid "This is the configuration file read by the boot loader when it starts. It is a copy of the <filename>/etc/elilo.conf</filename> with the filenames re-written to refer to files in the EFI partition."
 msgstr ""
 
 #. Tag: filename
-#: using-d-i.xml:2646
+#: using-d-i.xml:2654
 #, no-c-format
 msgid "elilo.efi"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2647
+#: using-d-i.xml:2655
 #, no-c-format
 msgid "This is the boot loader program that the <quote>EFI Boot Manager</quote> runs to boot the system. It is the program behind the <guimenuitem>Debian GNU/Linux</guimenuitem> menu item of the <quote>EFI Boot Manager</quote> command menu."
 msgstr ""
 
 #. Tag: filename
-#: using-d-i.xml:2657
+#: using-d-i.xml:2665
 #, no-c-format
 msgid "initrd.img"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2658
+#: using-d-i.xml:2666
 #, no-c-format
 msgid "This is the initial root filesystem used to boot the kernel. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard Debian installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/initrd.img</filename>."
 msgstr ""
 
 #. Tag: filename
-#: using-d-i.xml:2670
+#: using-d-i.xml:2678
 #, no-c-format
 msgid "readme.txt"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2671
+#: using-d-i.xml:2679
 #, no-c-format
 msgid "This is a small text file warning you that the contents of the directory are managed by the <command>elilo</command> and that any local changes would be lost at the next time <filename>/usr/sbin/elilo</filename> is run."
 msgstr ""
 
 #. Tag: filename
-#: using-d-i.xml:2681
+#: using-d-i.xml:2689
 #, no-c-format
 msgid "vmlinuz"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2682
+#: using-d-i.xml:2690
 #, no-c-format
 msgid "This is the compressed kernel itself. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard Debian installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/vmlinuz</filename>."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2702
+#: using-d-i.xml:2710
 #, no-c-format
 msgid "<command>arcboot</command>-installer"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2703
+#: using-d-i.xml:2711
 #, no-c-format
 msgid ""
       "The boot loader on SGI machines is <command>arcboot</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). Arcboot supports different configurations which are set up in <filename>/etc/arcboot.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After arcboot has been installed, the system can be booted from hard disk by setting some firmware environment variables entering <informalexample><screen>\n"
@@ -2113,289 +2119,289 @@ msgid ""
 msgstr ""
 
 #. Tag: replaceable
-#: using-d-i.xml:2722
+#: using-d-i.xml:2730
 #, no-c-format
 msgid "scsi"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2723
+#: using-d-i.xml:2731
 #, no-c-format
 msgid "is the SCSI bus to be booted from, this is <userinput>0</userinput> for the onboard controllers"
 msgstr ""
 
 #. Tag: replaceable
-#: using-d-i.xml:2731
+#: using-d-i.xml:2739
 #, no-c-format
 msgid "disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2732
+#: using-d-i.xml:2740
 #, no-c-format
 msgid "is the SCSI ID of the hard disk on which <command>arcboot</command> is installed"
 msgstr ""
 
 #. Tag: replaceable
-#: using-d-i.xml:2740
+#: using-d-i.xml:2748
 #, no-c-format
 msgid "partnr"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2741
+#: using-d-i.xml:2749
 #, no-c-format
 msgid "is the number of the partition on which <filename>/etc/arcboot.conf</filename> resides"
 msgstr ""
 
 #. Tag: replaceable
-#: using-d-i.xml:2749
+#: using-d-i.xml:2757
 #, no-c-format
 msgid "config"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2750
+#: using-d-i.xml:2758
 #, no-c-format
 msgid "is the name of the configuration entry in <filename>/etc/arcboot.conf</filename>, which is <quote>linux</quote> by default."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2771
+#: using-d-i.xml:2779
 #, no-c-format
 msgid "Install <command>Yaboot</command> on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2772
+#: using-d-i.xml:2780
 #, no-c-format
 msgid "Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as their boot loader. The installer will set up <command>yaboot</command> automatically, so all you need is a small 820k partition named <quote>bootstrap</quote> with type <emphasis>Apple_Bootstrap</emphasis> created back in the partitioning component. If this step completes successfully then your disk should now be bootable and OpenFirmware will be set to boot &debian;."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2790
+#: using-d-i.xml:2798
 #, no-c-format
 msgid "Install <command>Quik</command> on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2791
+#: using-d-i.xml:2799
 #, no-c-format
 msgid "The boot loader for OldWorld Power Macintosh machines is <command>quik</command>. You can also use it on CHRP. The installer will attempt to set up <command>quik</command> automatically. The setup has been known to work on 7200, 7300, and 7600 Powermacs, and on some Power Computing clones."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2807
+#: using-d-i.xml:2815
 #, no-c-format
 msgid "<command>zipl</command>-installer"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2808
+#: using-d-i.xml:2816
 #, no-c-format
 msgid "The boot loader on &arch-title; is <quote>zipl</quote>. <command>ZIPL</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. Please take a look at <quote>LINUX for &arch-title; Device Drivers and Installation Commands</quote> from IBM's developerWorks web site if you want to know more about <command>ZIPL</command>."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2825
+#: using-d-i.xml:2833
 #, no-c-format
 msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2827
+#: using-d-i.xml:2835
 #, no-c-format
 msgid "The standard &architecture; boot loader is called <quote>silo</quote>. It is documented in <filename>/usr/share/doc/silo/</filename>. <command>SILO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>SILO</command> allows you to boot any kernel image on your drive, even if it is not listed in <filename>/etc/silo.conf</filename>. This is because <command>SILO</command> can actually read Linux partitions. Also, <filename>/etc/silo.conf</filename> is read at boot time, so there is no need to rerun <command>silo</command> after installing a new kernel like you would with <command>LILO</command>. <command>SILO</command> can also read UFS partitions, which means it can boot SunOS/Solaris partitions as well. This is useful if you want to install GNU/Linux alongside an existing SunOS/Solaris install."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2852
+#: using-d-i.xml:2860
 #, no-c-format
 msgid "Continue Without Boot Loader"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2854
+#: using-d-i.xml:2862
 #, no-c-format
 msgid "This option can be used to complete the installation even when no boot loader is to be installed, either because the arch/subarch doesn't provide one, or because none is desired (e.g. you will use existing boot loader). <phrase arch=\"m68k\">This option is especially useful for Macintosh, Atari, and Amiga systems, where the original operating system must be maintained on the box and used to boot GNU/Linux.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2863
+#: using-d-i.xml:2871
 #, no-c-format
 msgid "If you plan to manually configure your bootloader, you should check the name of the installed kernel in <filename>/target/boot</filename>. You should also check that directory for the presence of an <firstterm>initrd</firstterm>; if one is present, you will probably have to instruct your bootloader to use it. Other information you will need are the disk and partition you selected for your <filename>/</filename> filesystem and, if you chose to install <filename>/boot</filename> on a separate partition, also your <filename>/boot</filename> filesystem."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2880
+#: using-d-i.xml:2888
 #, no-c-format
 msgid "Finishing the Installation"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2881
+#: using-d-i.xml:2889
 #, no-c-format
 msgid "This is the last step in the Debian installation process during which the installer will do any last minute tasks. It mostly consists of tidying up after the &d-i;."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2894
+#: using-d-i.xml:2902
 #, no-c-format
 msgid "Setting the System Clock"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2896
+#: using-d-i.xml:2904
 #, no-c-format
 msgid "The installer may ask you if the computer's clock is set to UTC. Normally this question is avoided if possible and the installer tries to work out whether the clock is set to UTC based on things like what other operating systems are installed."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2903
+#: using-d-i.xml:2911
 #, no-c-format
 msgid "In expert mode you will always be able to choose whether or not the clock is set to UTC. <phrase arch=\"m68k;powerpc\">Macintosh hardware clocks are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase> <phrase arch=\"x86\">Systems that (also) run Dos or Windows are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase>"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2914
+#: using-d-i.xml:2922
 #, no-c-format
 msgid "At this point &d-i; will also attempt to save the current time to the system's hardware clock. This will be done either in UTC or local time, depending on the selection that was just made."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2929
+#: using-d-i.xml:2937
 #, no-c-format
 msgid "Reboot the System"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2931
+#: using-d-i.xml:2939
 #, no-c-format
 msgid "You will be prompted to remove the boot media (CD, floppy, etc) that you used to boot the installer. After that the system will be rebooted into your new Debian system."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2937
+#: using-d-i.xml:2945
 #, no-c-format
 msgid "After a final prompt the system will be halted because rebooting is not supported on &arch-title;. You then need to IPL &debian; from the DASD which you selected for the root filesystem during the first steps of the installation."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2950
+#: using-d-i.xml:2958
 #, no-c-format
 msgid "Miscellaneous"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2951
+#: using-d-i.xml:2959
 #, no-c-format
 msgid "The components listed in this section are usually not involved in the installation process, but are waiting in the background to help the user in case something goes wrong."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2964
+#: using-d-i.xml:2972
 #, no-c-format
 msgid "Saving the installation logs"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2966
+#: using-d-i.xml:2974
 #, no-c-format
 msgid "If the installation is successful, the logfiles created during the installation process will be automatically saved to <filename>/var/log/installer/</filename> on your new Debian system."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2973
+#: using-d-i.xml:2981
 #, no-c-format
 msgid "Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu allows you to save the log files to a floppy disk, network, hard disk, or other media. This can be useful if you encounter fatal problems during the installation and wish to study the logs on another system or attach them to an installation report."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:2993
+#: using-d-i.xml:3001
 #, no-c-format
 msgid "Using the Shell and Viewing the Logs"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:2995
+#: using-d-i.xml:3003
 #, no-c-format
 msgid "There are several methods you can use to get a shell while running an installation. On most systems, and if you are not installing over serial console, the easiest method is to switch to the second <emphasis>virtual console</emphasis> by pressing <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo><footnote> <para> That is: press the <keycap>Alt</keycap> key on the left-hand side of the <keycap>space bar</keycap> and the <keycap>F2</keycap> function key at the same time. </para> </footnote> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap></keycombo>). Use <keycombo><keycap>Left Alt</keycap> <keycap>F1</keycap></keycombo> to switch back to installer itself."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3013
+#: using-d-i.xml:3021
 #, no-c-format
 msgid "For the graphical installer see also <xref linkend=\"gtk-using\"/>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3017
+#: using-d-i.xml:3025
 #, no-c-format
 msgid "If you cannot switch consoles, there is also an <guimenuitem>Execute a Shell</guimenuitem> item on the main menu that can be used to start a shell. You can get to the main menu from most dialogs by using the &BTN-GOBACK; button one or more times. Type <userinput>exit</userinput> to close the shell and return to the installer."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3025
+#: using-d-i.xml:3033
 #, no-c-format
 msgid "At this point you are booted from the RAM disk, and there is a limited set of Unix utilities available for your use. You can see what programs are available with the command <command>ls /bin /sbin /usr/bin /usr/sbin</command> and by typing <command>help</command>. The shell is a Bourne shell clone called <command>ash</command> and has some nice features like autocompletion and history."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3034
+#: using-d-i.xml:3042
 #, no-c-format
 msgid "To edit and view files, use the text editor <command>nano</command>. Log files for the installation system can be found in the <filename>/var/log</filename> directory."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3041
+#: using-d-i.xml:3049
 #, no-c-format
 msgid "Although you can do basically anything in a shell that the available commands allow you to do, the option to use a shell is really only there in case something goes wrong and for debugging."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3047
+#: using-d-i.xml:3055
 #, no-c-format
 msgid "Doing things manually from the shell may interfere with the installation process and result in errors or an incomplete installation. In particular, you should always use let the installer activate your swap partition and not do this yourself from a shell."
 msgstr ""
 
 #. Tag: title
-#: using-d-i.xml:3062
+#: using-d-i.xml:3070
 #, no-c-format
 msgid "Installation Over the Network"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3064
+#: using-d-i.xml:3072
 #, no-c-format
 msgid "One of the more interesting components is <firstterm>network-console</firstterm>. It allows you to do a large part of the installation over the network via SSH. The use of the network implies you will have to perform the first steps of the installation from the console, at least to the point of setting up the networking. (Although you can automate that part with <xref linkend=\"automatic-install\"/>.)"
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3074
+#: using-d-i.xml:3082
 #, no-c-format
 msgid "This component is not loaded into the main installation menu by default, so you have to explicitly ask for it. If you are installing from CD, you need to boot with medium priority or otherwise invoke the main installation menu and choose <guimenuitem>Load installer components from CD</guimenuitem> and from the list of additional components select <guimenuitem>network-console: Continue installation remotely using SSH</guimenuitem>. Successful load is indicated by a new menu entry called <guimenuitem>Continue installation remotely using SSH</guimenuitem>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3087
+#: using-d-i.xml:3095
 #, no-c-format
 msgid "For installations on &arch-title;, this is the default method after setting up the network."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3092
+#: using-d-i.xml:3100
 #, no-c-format
 msgid "<phrase arch=\"not-s390\">After selecting this new entry, you</phrase> <phrase arch=\"s390\">You</phrase> will be asked for a new password to be used for connecting to the installation system and for its confirmation. That's all. Now you should see a screen which instructs you to login remotely as the user <emphasis>installer</emphasis> with the password you just provided. Another important detail to notice on this screen is the fingerprint of this system. You need to transfer the fingerprint securely to the <quote>person who will continue the installation remotely</quote>."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3104
+#: using-d-i.xml:3112
 #, no-c-format
 msgid "Should you decide to continue with the installation locally, you can always press &enterkey;, which will bring you back to the main menu, where you can select another component."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3110
+#: using-d-i.xml:3118
 #, no-c-format
 msgid ""
       "Now let's switch to the other side of the wire. As a prerequisite, you need to configure your terminal for UTF-8 encoding, because that is what the installation system uses. If you do not, remote installation will be still possible, but you may encounter strange display artefacts like destroyed dialog borders or unreadable non-ascii characters. Establishing a connection with the installation system is as simple as typing: <informalexample><screen>\n"
@@ -2404,32 +2410,128 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3127
+#: using-d-i.xml:3135
 #, no-c-format
 msgid "The <command>ssh</command> server in the installer uses a default configuration that does not send keep-alive packets. In principle, a connection to the system being installed should be kept open indefinitely. However, in some situations &mdash; depending on your local network setup &mdash; the connection may be lost after some period of inactivity. One common case where this can happen is when there is some form of Network Address Translation (NAT) somewhere between the client and the system being installed. Depending on at which point of the installation the connection was lost, you may or may not be able to resume the installation after reconnecting."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3140
+#: using-d-i.xml:3148
 #, no-c-format
 msgid "You may be able to avoid the connection being dropped by adding the option <userinput>-o&nbsp;ServerAliveInterval=<replaceable>value</replaceable></userinput> when starting the <command>ssh</command> connection, or by adding that option in your <command>ssh</command> configuration file. Note however that in some cases adding this option may also <emphasis>cause</emphasis> a connection to be dropped (for example if keep-alive packets are sent during a brief network outage, from which <command>ssh</command> would otherwise have recovered), so it should only be used when needed."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3153
+#: using-d-i.xml:3161
 #, no-c-format
 msgid "If you install several computers in turn and they happen to have the same IP address or hostname, <command>ssh</command> will refuse to connect to such host. The reason is that it will have different fingerprint, which is usually a sign of a spoofing attack. If you are sure this is not the case, you will need to delete the relevant line from <filename>~/.ssh/known_hosts</filename><footnote> <para> The following command will remove an existing entry for a host: <command>ssh-keygen -R &lt;<replaceable>hostname</replaceable>|<replaceable>IP&nbsp;address</replaceable>&gt;</command>. </para> </footnote> and try again."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3169
+#: using-d-i.xml:3177
 #, no-c-format
 msgid "After the login you will be presented with an initial screen where you have two possibilities called <guimenuitem>Start menu</guimenuitem> and <guimenuitem>Start shell</guimenuitem>. The former brings you to the main installer menu, where you can continue with the installation as usual. The latter starts a shell from which you can examine and possibly fix the remote system. You should only start one SSH session for the installation menu, but may start multiple sessions for shells."
 msgstr ""
 
 #. Tag: para
-#: using-d-i.xml:3179
+#: using-d-i.xml:3187
 #, no-c-format
 msgid "After you have started the installation remotely over SSH, you should not go back to the installation session running on the local console. Doing so may corrupt the database that holds the configuration of the new system. This in turn may result in a failed installation or problems with the installed system."
 msgstr ""
 
+#. Tag: title
+#: using-d-i.xml:3207
+#, no-c-format
+msgid "Loading Missing Firmware"
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:3208
+#, no-c-format
+msgid "As described in <xref linkend=\"hardware-firmware\"/>, some devices require firmware to be loaded. In most cases the device will not work at all if the firmware is not available; sometimes basic functionality is not impaired if it is missing and the firmware is only needed to enable additional features."
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:3216
+#, no-c-format
+msgid "If a device driver requests firmware that is not available, &d-i; will display a dialog offering to load the missing firmware. If this option is selected, &d-i; will scan available devices for either loose firmware files or packages containing firmware. If found, the firmware will be copied to the correct location (<filename>/lib/firmware</filename>) and the driver module will be reloaded."
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:3226
+#, no-c-format
+msgid "Which devices are scanned and which file systems are supported depends on the architecture, the installation method and the stage of the installation. Especially during the early stages of the installation, loading the firmware is most likely to succeed from a FAT-formatted floppy disk or USB stick. <phrase arch=\"x86\">On i386 and amd64 firmware can also be loaded from an MMC or SD card.</phrase>"
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:3236
+#, no-c-format
+msgid "Note that it is possible to skip loading the firmware if you know the device will also function without it, or if the device is not needed during the installation."
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:3243
+#, no-c-format
+msgid "Support for loading firmware is still relatively basic and is likely to be improved in future releases of the installer. Currently &d-i; will for example not display any warning if you choose to load missing firmware, but the requested firmware is not found. Please <xref linkend=\"submit-bug\"/>report any issues you encounter."
+msgstr ""
+
+#. Tag: title
+#: using-d-i.xml:3253
+#, no-c-format
+msgid "Preparing a medium"
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:3254
+#, no-c-format
+msgid "Although in some cases the firmware can also be loaded from a partition on a hard disk, the most common method to load firmware will be from some removable medium such as a floppy disk or a USB stick. The firmware files or packages must be placed in either the root directory or a directory named <filename>/firmware</filename> of the file system on the medium. The recommended file system to use is FAT as that is most certain to be supported during the early stages of the installation."
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:3264
+#, no-c-format
+msgid "Tarballs containing current packages for the most common firmware are available from: <itemizedlist> <listitem><para> <ulink url=\"&url-firmware-tarballs;\"></ulink> </para></listitem> </itemizedlist> Just download the tarball for the correct release and unpack it to the file system on the medium."
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:3278
+#, no-c-format
+msgid "If the firmware you need is not included in the tarball, you can also download specific firmware packages from the (non-free section of the) archive. The following overview should list most available firmware packages but is not guaranteed to be complete and may also contain non-firmware packages:"
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:3292
+#, no-c-format
+msgid "It is also possible to copy individual firmware files to the medium. Loose firmware could be obtained for example from an already installed system or from a hardware vendor."
+msgstr ""
+
+#. Tag: title
+#: using-d-i.xml:3301
+#, no-c-format
+msgid "Firmware and the Installed System"
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:3302
+#, no-c-format
+msgid "Any firmware loaded during the installation will be copied automatically to the installed system. In most cases this will ensure that the device that requires the firmware will also work correctly after the system is rebooted into the installed system. However, if the installed system runs a different kernel version from the installer there is a slight chance that the firmware cannot be loaded due to version skew."
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:3311
+#, no-c-format
+msgid "If the firmware was loaded from a firmware package, &d-i; will also install this package for the installed system and will automatically add the non-free section of the package archive in APT's <filename>sources.list</filename>. This has the advantage that the firmware should be updated automatically if a new version becomes available."
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:3319
+#, no-c-format
+msgid "If loading the firmware was skipped during the installation, the relevant device will probably not work with the installed system until the firmware (package) is installed manually."
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:3326
+#, no-c-format
+msgid "If the firmware was loaded from loose firmware files, the firmware copied to the installed system will <emphasis>not</emphasis> be automatically updated unless the corresponding firmware package (if available) is installed after the installation is completed."
+msgstr ""
+
author	Felipe Augusto van de Wiel <faw@debian.org>	2008-10-05 00:08:06 +0000
committer	Felipe Augusto van de Wiel <faw@debian.org>	2008-10-05 00:08:06 +0000
commit	2d5cb2b72b12f78d9775f4115c1ff1ae0c0a747c (patch)
tree	b3b6da52354f7939c4f365c9d854bd589c5c4c4b /po/pot
parent	d796c0b482621422867036216356369b6fde08a2 (diff)
download	installation-guide-2d5cb2b72b12f78d9775f4115c1ff1ae0c0a747c.zip