Update of POT and PO files for the manual

1 files changed, 34 insertions, 58 deletions

diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot
index beef411c2..a2fff05c3 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: 2006-12-12 21:17+0000\n"
+"POT-Creation-Date: 2006-12-25 19:53+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"
@@ -3006,223 +3006,199 @@ msgid "You can help improve this situation by encouraging these manufacturers to
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:2338
-#, no-c-format
-msgid "Fake or <quote>Virtual</quote> Parity RAM"
-msgstr ""
-
-#. Tag: para
-#: hardware.xml:2339
-#, no-c-format
-msgid "If you ask for Parity RAM in a computer store, you'll probably get <emphasis>virtual parity</emphasis> memory modules instead of <emphasis>true parity</emphasis> ones. Virtual parity SIMMs can often (but not always) be distinguished because they only have one more chip than an equivalent non-parity SIMM, and that one extra chip is smaller than all the others. Virtual-parity SIMMs work exactly like non-parity memory. They can't tell you when you have a single-bit RAM error the way true-parity SIMMs do in a motherboard that implements parity. Don't ever pay more for a virtual-parity SIMM than a non-parity one. Do expect to pay a little more for true-parity SIMMs, because you are actually buying one extra bit of memory for every 8 bits."
-msgstr ""
-
-#. Tag: para
-#: hardware.xml:2354
-#, no-c-format
-msgid "If you want complete information on &arch-title; RAM issues, and what is the best RAM to buy, see the <ulink url=\"&url-pc-hw-faq;\">PC Hardware FAQ</ulink>."
-msgstr ""
-
-#. Tag: para
-#: hardware.xml:2360
-#, no-c-format
-msgid "Most, if not all, Alpha systems require true-parity RAM."
-msgstr ""
-
-#. Tag: title
-#: hardware.xml:2375
+#: hardware.xml:2342
 #, no-c-format
 msgid "Memory and Disk Space Requirements"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2377
+#: hardware.xml:2344
 #, no-c-format
 msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space. For a minimal console-based system (all standard packages), 250MB is required. If you want to install a reasonable amount of software, including the X Window System, and some development programs and libraries, you'll need at least 400MB. For a more or less complete desktop system, you'll need a few gigabytes."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2386
+#: hardware.xml:2353
 #, 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:2395
+#: hardware.xml:2362
 #, 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:2403
+#: hardware.xml:2370
 #, 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:2413
+#: hardware.xml:2380
 #, no-c-format
 msgid "FIXME: is this still true?"
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:2424
+#: hardware.xml:2391
 #, no-c-format
 msgid "Network Connectivity Hardware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2426
+#: hardware.xml:2393
 #, no-c-format
 msgid "Most PCI and many older ISA network cards are supported. Some network interface cards are not supported by most Debian installation disks, such as AX.25 cards and protocols; NI16510 EtherBlaster cards; Schneider &amp; Koch G16 cards; and the Zenith Z-Note built-in network card. Microchannel (MCA) network cards are not supported by the standard installation system, but see <ulink url=\"&url-linux-mca;\">Linux on MCA</ulink> for some (old) instructions. FDDI networks are also not supported by the installation disks, both cards and protocols."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2445
+#: hardware.xml:2412
 #, 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;."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2453
+#: hardware.xml:2420
 #, no-c-format
 msgid "Any network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module. Again, see <ulink url=\"&url-m68k-faq;\"></ulink> for complete details."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2462
+#: hardware.xml:2429
 #, no-c-format
 msgid "The following network interface cards (NICs) are supported from the bootable kernel directly:"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2468
+#: hardware.xml:2435
 #, no-c-format
 msgid "Sun LANCE"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2474
+#: hardware.xml:2441
 #, no-c-format
 msgid "Sun Happy Meal"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2482
+#: hardware.xml:2449
 #, no-c-format
 msgid "The following network interface cards are supported as modules. They can be enabled once the drivers are installed during the setup. However, due to the magic of OpenPROM, you still should be able to boot from these devices:"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2490
+#: hardware.xml:2457
 #, no-c-format
 msgid "Sun BigMAC"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2496
+#: hardware.xml:2463
 #, no-c-format
 msgid "Sun QuadEthernet"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2501
+#: hardware.xml:2468
 #, no-c-format
 msgid "MyriCOM Gigabit Ethernet"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2508 hardware.xml:2514 hardware.xml:2520 hardware.xml:2526 hardware.xml:2532
+#: hardware.xml:2475 hardware.xml:2481 hardware.xml:2487 hardware.xml:2493 hardware.xml:2499
 #, no-c-format
 msgid "Any network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2538
+#: hardware.xml:2505
 #, 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:2544
+#: hardware.xml:2511
 #, no-c-format
 msgid "Any network interface card (NIC) supported by the Linux kernel is also be supported by the boot disks. All network drivers are compiled as modules so you need to load one first during the initial network setup. The list of supported network devices is:"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2552
+#: hardware.xml:2519
 #, no-c-format
 msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2557
+#: hardware.xml:2524
 #, no-c-format
 msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2562
+#: hardware.xml:2529
 #, no-c-format
 msgid "Inter-User Communication Vehicle (IUCV) &mdash; available for VM guests only"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2567
+#: hardware.xml:2534
 #, no-c-format
 msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2576
+#: hardware.xml:2543
 #, no-c-format
 msgid "The following network interface cards are supported directly by the boot disks on Netwinder and CATS machines:"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2582
+#: hardware.xml:2549
 #, no-c-format
 msgid "PCI-based NE2000"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2588
+#: hardware.xml:2555
 #, no-c-format
 msgid "DECchip Tulip"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2595
+#: hardware.xml:2562
 #, no-c-format
 msgid "The following network interface cards are supported directly by the boot disks on RiscPCs:"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2601
+#: hardware.xml:2568
 #, no-c-format
 msgid "Ether1"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2606
+#: hardware.xml:2573
 #, no-c-format
 msgid "Ether3"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2611
+#: hardware.xml:2578
 #, no-c-format
 msgid "EtherH"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2618
+#: hardware.xml:2585
 #, no-c-format
 msgid "If your card is mentioned in the lists above, the complete installation can be carried out from the network with no need for CD-ROMs or floppy disks."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2624
+#: hardware.xml:2591
 #, no-c-format
 msgid "Any other network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module; this means that you will have to install the operating system kernel and modules using some other media."
 msgstr ""