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

1 files changed, 78 insertions, 78 deletions

diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot
index b8674cd59..e8ee06593 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-10-17 00:09+0000\n"
+"POT-Creation-Date: 2008-10-19 07:15+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"
@@ -2633,461 +2633,461 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:1918
 #, no-c-format
-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."
+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. Select the option to not configure a network and install using only the packages available from the CD/DVD. You can then install the driver and firmware you need after the installation is completed (after the reboot) and configure your network manually."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1927
+#: hardware.xml:1930
 #, 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:1941
+#: hardware.xml:1944
 #, no-c-format
 msgid "Known Issues for &arch-title;"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1942
+#: hardware.xml:1945
 #, no-c-format
 msgid "There are a couple of issues with specific network cards that are worth mentioning here."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1949
+#: hardware.xml:1952
 #, no-c-format
 msgid "Conflict between tulip and dfme drivers"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1951
+#: hardware.xml:1954
 #, 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:1961
+#: hardware.xml:1964
 #, 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:1969
+#: hardware.xml:1972
 #, 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:1982
+#: hardware.xml:1985
 #, no-c-format
 msgid "Sun B100 blade"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:1984
+#: hardware.xml:1987
 #, no-c-format
 msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:1999
+#: hardware.xml:2002
 #, no-c-format
 msgid "Peripherals and Other Hardware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2000
+#: hardware.xml:2003
 #, 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."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2006
+#: hardware.xml:2009
 #, no-c-format
 msgid "USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend=\"hardware-issues\"/>)."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2012
+#: hardware.xml:2015
 #, 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."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2018
+#: hardware.xml:2021
 #, no-c-format
 msgid "Package installations from XPRAM and tape are not supported by this system. All packages that you want to install need to be available on a DASD or over the network using NFS, HTTP or FTP."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2024
+#: hardware.xml:2027
 #, 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."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2030
+#: hardware.xml:2033
 #, 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."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:2044
+#: hardware.xml:2047
 #, no-c-format
 msgid "Devices Requiring Firmware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2045
+#: hardware.xml:2048
 #, no-c-format
 msgid "Besides the availability of a device driver, some hardware also requires so-called <firstterm>firmware</firstterm> or <firstterm>microcode</firstterm> to be loaded into the device before it can become operational. This is most common for network interface cards (especially wireless NICs), but for example some USB devices and even some hard disk controllers also require firmware."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2053
+#: hardware.xml:2056
 #, no-c-format
 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:2062
+#: hardware.xml:2065
 #, no-c-format
 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:2078
+#: hardware.xml:2081
 #, no-c-format
 msgid "Purchasing Hardware Specifically for GNU/Linux"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2080
+#: hardware.xml:2083
 #, 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:2088
+#: hardware.xml:2091
 #, 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:2093
+#: hardware.xml:2096
 #, 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:2101
+#: hardware.xml:2104
 #, 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:2112
+#: hardware.xml:2115
 #, no-c-format
 msgid "Avoid Proprietary or Closed Hardware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2113
+#: hardware.xml:2116
 #, 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:2120
+#: hardware.xml:2123
 #, 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:2131
+#: hardware.xml:2134
 #, 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:2143
+#: hardware.xml:2146
 #, no-c-format
 msgid "Windows-specific Hardware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2144
+#: hardware.xml:2147
 #, 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:2157
+#: hardware.xml:2160
 #, 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:2178
+#: hardware.xml:2181
 #, 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:2195
+#: hardware.xml:2198
 #, no-c-format
 msgid "Installation Media"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2197
+#: hardware.xml:2200
 #, 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."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:2208
+#: hardware.xml:2211
 #, no-c-format
 msgid "Floppies"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2209
+#: hardware.xml:2212
 #, no-c-format
 msgid "In some cases, you'll have to do your first boot from floppy disks. Generally, all you will need is a high-density (1440 kilobytes) 3.5 inch floppy drive."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2215
+#: hardware.xml:2218
 #, no-c-format
 msgid "For CHRP, floppy support is currently broken."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:2222
+#: hardware.xml:2225
 #, no-c-format
 msgid "CD-ROM/DVD-ROM"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2224
+#: hardware.xml:2227
 #, 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."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2231
+#: hardware.xml:2234
 #, 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\"/>."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2243
+#: hardware.xml:2246
 #, 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."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2249
+#: hardware.xml:2252
 #, no-c-format
 msgid "USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2254
+#: hardware.xml:2257
 #, 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>."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2263
+#: hardware.xml:2266
 #, no-c-format
 msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2267
+#: hardware.xml:2270
 #, 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."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:2285
+#: hardware.xml:2288
 #, no-c-format
 msgid "Hard Disk"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2287
+#: hardware.xml:2290
 #, 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."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2293
+#: hardware.xml:2296
 #, no-c-format
 msgid "In fact, installation from your local disk is the preferred installation technique for most &architecture; machines."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2298
+#: hardware.xml:2301
 #, no-c-format
 msgid "Although the &arch-title; does not allow booting from SunOS (Solaris), you can install from a SunOS partition (UFS slices)."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:2306
+#: hardware.xml:2309
 #, no-c-format
 msgid "USB Memory Stick"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2308
+#: hardware.xml:2311
 #, 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."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:2320
+#: hardware.xml:2323
 #, no-c-format
 msgid "Network"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2322
+#: hardware.xml:2325
 #, no-c-format
 msgid "The network can be used during the installation to retrieve files needed for the installation. Whether the network is used or not depends on the installation method you choose and your answers to certain questions that will be asked during the installation. The installation system supports most types of network connections (including PPPoE, but not ISDN or PPP), via either HTTP or FTP. After the installation is completed, you can also configure your system to use ISDN and PPP."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2332
+#: hardware.xml:2335
 #, 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>"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2338
+#: hardware.xml:2341
 #, no-c-format
 msgid "Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:2346
+#: hardware.xml:2349
 #, no-c-format
 msgid "Un*x or GNU system"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2348
+#: hardware.xml:2351
 #, 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\"/>."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:2360
+#: hardware.xml:2363
 #, no-c-format
 msgid "Supported Storage Systems"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2362
+#: hardware.xml:2365
 #, 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."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2372
+#: hardware.xml:2375
 #, 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."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2379
+#: hardware.xml:2382
 #, 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."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2387
+#: hardware.xml:2390
 #, 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."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2397
+#: hardware.xml:2400
 #, no-c-format
 msgid "Any storage system supported by the Linux kernel is also supported by the boot system. The following SCSI drivers are supported in the default kernel: <itemizedlist> <listitem><para> Sparc ESP </para></listitem> <listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></listitem> </itemizedlist> IDE systems (such as the UltraSPARC 5) are also supported. See <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors FAQ</ulink> for more information on SPARC hardware supported by the Linux kernel."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2430
+#: hardware.xml:2433
 #, 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)"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2439
+#: hardware.xml:2442
 #, no-c-format
 msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support floppies on CHRP systems at all."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2445
+#: hardware.xml:2448
 #, no-c-format
 msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support the floppy drive."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2451
+#: hardware.xml:2454
 #, no-c-format
 msgid "Any storage system supported by the Linux kernel is also supported by the boot system."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2456
+#: hardware.xml:2459
 #, 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:2476
 #, no-c-format
 msgid "Memory and Disk Space Requirements"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2475
+#: hardware.xml:2478
 #, no-c-format
 msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space to perform a normal installation. Note that these are fairly minimal numbers. For more realistic figures, see <xref linkend=\"minimum-hardware-reqts\"/>."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2482
+#: hardware.xml:2485
 #, 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:2499
+#: hardware.xml:2502
 #, 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:2508
+#: hardware.xml:2511
 #, 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:2516
+#: hardware.xml:2519
 #, 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:2526
+#: hardware.xml:2529
 #, no-c-format
 msgid "FIXME: is this still true?"
 msgstr ""