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

1 files changed, 43 insertions, 37 deletions

diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot
index df56a726c..9aaf25adb 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: 2007-10-22 00:09+0000\n"
+"POT-Creation-Date: 2008-05-02 00:09+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"
@@ -3008,215 +3008,221 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:2340
 #, no-c-format
-msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space. Note that these are really bare-minimum numbers. For more realistic figures, see <xref linkend=\"minimum-hardware-reqts\"/>."
+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:2346
+#: hardware.xml:2347
+#, no-c-format
+msgid "Installation on systems with less memory<footnote condition=\"gtk\"> <para> Installation images that support the graphical installer require more memory than images that support only the textual installer and should not be used on systems with less than &minimum-memory; of memory. If there is a choice between booting the regular and the graphical installer, the former should be selected. </para> </footnote> or disk space available may be possible but is only advised for experienced users."
+msgstr ""
+
+#. Tag: para
+#: hardware.xml:2364
 #, 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."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2355
+#: hardware.xml:2373
 #, 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."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2363
+#: hardware.xml:2381
 #, 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."
 msgstr ""
 
 #. Tag: emphasis
-#: hardware.xml:2373
+#: hardware.xml:2391
 #, no-c-format
 msgid "FIXME: is this still true?"
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:2384
+#: hardware.xml:2402
 #, no-c-format
 msgid "Network Connectivity Hardware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2385
+#: hardware.xml:2403
 #, 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>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2397
+#: hardware.xml:2415
 #, no-c-format
 msgid "This includes a lot of generic PCI cards (for systems that have PCI) and the following NICs from Sun:"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2403
+#: hardware.xml:2421
 #, no-c-format
 msgid "Sun LANCE"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2408
+#: hardware.xml:2426
 #, no-c-format
 msgid "Sun Happy Meal"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2413
+#: hardware.xml:2431
 #, no-c-format
 msgid "Sun BigMAC"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2418
+#: hardware.xml:2436
 #, no-c-format
 msgid "Sun QuadEthernet"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2423
+#: hardware.xml:2441
 #, no-c-format
 msgid "MyriCOM Gigabit Ethernet"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2430
+#: hardware.xml:2448
 #, no-c-format
 msgid "Due to kernel limitations only the onboard network interfaces on DECstations are supported, TurboChannel option network cards currently do not work."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2436
+#: hardware.xml:2454
 #, no-c-format
 msgid "The list of supported network devices is:"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2441
+#: hardware.xml:2459
 #, no-c-format
 msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2446
+#: hardware.xml:2464
 #, no-c-format
 msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2451
+#: hardware.xml:2469
 #, no-c-format
 msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2460
+#: hardware.xml:2478
 #, 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>."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2470
+#: hardware.xml:2488
 #, 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."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:2479
+#: hardware.xml:2497
 #, no-c-format
 msgid "Drivers Requiring Firmware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2480
+#: hardware.xml:2498
 #, 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."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2486
+#: hardware.xml:2504
 #, 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."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2497
+#: hardware.xml:2515
 #, 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."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:2509
+#: hardware.xml:2527
 #, no-c-format
 msgid "Wireless Network Cards"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2510
+#: hardware.xml:2528
 #, 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."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2517
+#: hardware.xml:2535
 #, 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."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2523
+#: hardware.xml:2541
 #, no-c-format
 msgid "In some cases the driver you need may not be available as a Debian package. You will then have to look if there is source code available in the internet and compile the driver yourself. How to do this is outside the scope of this manual. <phrase arch=\"x86\">If no Linux driver is available, your last resort is to use the <classname>ndiswrapper</classname> package, which allows you to use a Windows driver.</phrase>"
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:2537
+#: hardware.xml:2555
 #, no-c-format
 msgid "Known Issues for &arch-title;"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2538
+#: hardware.xml:2556
 #, no-c-format
 msgid "There are a couple of issues with specific network cards that are worth mentioning here."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:2545
+#: hardware.xml:2563
 #, no-c-format
 msgid "Conflict between tulip and dfme drivers"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2547
+#: hardware.xml:2565
 #, no-c-format
 msgid "There are various PCI network cards that have the same PCI identification, but are supported by related, but different drivers. Some cards work with the <literal>tulip</literal> driver, others with the <literal>dfme</literal> driver. Because they have the same identification, the kernel cannot distinguish between them and it is not certain which driver will be loaded. If this happens to be the wrong one, the NIC may not work, or work badly."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2557
+#: hardware.xml:2575
 #, no-c-format
 msgid "This is a common problem on Netra systems with a Davicom (DEC-Tulip compatible) NIC. In that case the <literal>tulip</literal> driver is probably the correct one. You can prevent this issue by blacklisting the wrong driver module as described in <xref linkend=\"module-blacklist\"/>."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2565
+#: hardware.xml:2583
 #, no-c-format
 msgid "An alternative solution during the installation is to switch to a shell and unload the wrong driver module using <userinput>modprobe -r <replaceable>module</replaceable></userinput> (or both, if they are both loaded). After that you can load the correct module using <userinput>modprobe <replaceable>module</replaceable></userinput>. Note that the wrong module may then still be loaded when the system is rebooted."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:2578
+#: hardware.xml:2596
 #, no-c-format
 msgid "Sun B100 blade"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2580
+#: hardware.xml:2598
 #, no-c-format
 msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems."
 msgstr ""