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

1 files changed, 80 insertions, 80 deletions

diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot
index 316855467..7801cbd83 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-31 03:15+0000\n"
+"POT-Creation-Date: 2007-01-01 11:02+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"
@@ -1745,19 +1745,19 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:853
 #, 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 new processors like the Athlon XP and Intel P4 Xeon."
+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:861
 #, no-c-format
-msgid "If your system has a 64-bit AMD64, Intel EM64T or Intel Core 2 Duo processor, you will probably want to use the installer for the amd64 architecture instead of the installer for the (32-bit) i386 architecture."
+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: para
 #: hardware.xml:868
 #, no-c-format
-msgid "However, Debian GNU/Linux &releasename; will <emphasis>not</emphasis> run on 386 or earlier processors. Despite the architecture name \"i386\", Debian Sarge has <emphasis>dropped support</emphasis> for actual 80386 processors (and their clones), which were supported by earlier releases<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 "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: title
@@ -2834,431 +2834,431 @@ msgstr ""
 #. Tag: para
 #: hardware.xml:2065
 #, no-c-format
-msgid "You can also <emphasis>boot</emphasis> your system over the network. <phrase arch=\"mips\">This is the preferred installation technique for Mips.</phrase>"
+msgid "The network can be used during the installtion 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 connection (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:2071
+#: hardware.xml:2075
 #, 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 "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:2076
+#: hardware.xml:2081
 #, no-c-format
-msgid "After the operating system kernel is installed, you can install the rest of your system via any sort of network connection (including PPP after installation of the base system), via FTP or HTTP."
+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:2085
+#: hardware.xml:2089
 #, no-c-format
 msgid "Un*x or GNU system"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2087
+#: hardware.xml:2091
 #, 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 the 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 "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:2099
+#: hardware.xml:2103
 #, no-c-format
 msgid "Supported Storage Systems"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2101
+#: hardware.xml:2105
 #, 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:2111
+#: hardware.xml:2115
 #, no-c-format
 msgid "Generally, the Debian installation system includes support for floppies, IDE drives, IDE floppies, parallel port IDE devices, 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:2118
+#: hardware.xml:2122
 #, no-c-format
 msgid "Disk interfaces that emulate the <quote>AT</quote> hard disk interface &mdash; often called MFM, RLL, IDE, or ATA &mdash; are supported. Very old 8&ndash;bit hard disk controllers used in the IBM XT computer are supported only as a module. 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:2128
+#: hardware.xml:2132
 #, 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:2138
+#: hardware.xml:2142
 #, 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:2171
+#: hardware.xml:2175
 #, 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:2180
+#: hardware.xml:2184
 #, 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:2186
+#: hardware.xml:2190
 #, 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:2192
+#: hardware.xml:2196
 #, no-c-format
 msgid "Any storage system supported by the Linux kernel is also supported by the boot system."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2197
+#: hardware.xml:2201
 #, 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:2214
+#: hardware.xml:2218
 #, no-c-format
 msgid "Peripherals and Other Hardware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2215
+#: hardware.xml:2219
 #, 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:2221
+#: hardware.xml:2225
 #, 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:2227
+#: hardware.xml:2231
 #, 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:2233
+#: hardware.xml:2237
 #, 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:2239
+#: hardware.xml:2243
 #, 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:2245
+#: hardware.xml:2249
 #, 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:2255
+#: hardware.xml:2259
 #, no-c-format
 msgid "Purchasing Hardware Specifically for GNU/Linux"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2257
+#: hardware.xml:2261
 #, 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:2265
+#: hardware.xml:2269
 #, 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:2270
+#: hardware.xml:2274
 #, 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:2278
+#: hardware.xml:2282
 #, 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:2289
+#: hardware.xml:2293
 #, no-c-format
 msgid "Avoid Proprietary or Closed Hardware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2290
+#: hardware.xml:2294
 #, 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:2297
+#: hardware.xml:2301
 #, 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:2308
+#: hardware.xml:2312
 #, 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:2320
+#: hardware.xml:2324
 #, no-c-format
 msgid "Windows-specific Hardware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2321
+#: hardware.xml:2325
 #, 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:2334
+#: hardware.xml:2338
 #, 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 its 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:2355
+#: hardware.xml:2359
 #, 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:2372
+#: hardware.xml:2376
 #, no-c-format
 msgid "Memory and Disk Space Requirements"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2374
+#: hardware.xml:2378
 #, 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."
+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\"/>."
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2383
+#: hardware.xml:2384
 #, 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:2392
+#: hardware.xml:2393
 #, 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:2400
+#: hardware.xml:2401
 #, 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:2410
+#: hardware.xml:2411
 #, no-c-format
 msgid "FIXME: is this still true?"
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:2421
+#: hardware.xml:2422
 #, no-c-format
 msgid "Network Connectivity Hardware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2422
+#: hardware.xml:2423
 #, 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:2434
+#: hardware.xml:2435
 #, 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:2440
+#: hardware.xml:2441
 #, no-c-format
 msgid "Sun LANCE"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2445
+#: hardware.xml:2446
 #, no-c-format
 msgid "Sun Happy Meal"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2450
+#: hardware.xml:2451
 #, no-c-format
 msgid "Sun BigMAC"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2455
+#: hardware.xml:2456
 #, no-c-format
 msgid "Sun QuadEthernet"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2460
+#: hardware.xml:2461
 #, no-c-format
 msgid "MyriCOM Gigabit Ethernet"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2467
+#: hardware.xml:2468
 #, 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:2473
+#: hardware.xml:2474
 #, no-c-format
 msgid "The list of supported network devices is:"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2478
+#: hardware.xml:2479
 #, no-c-format
 msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2483
+#: hardware.xml:2484
 #, no-c-format
 msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2488
+#: hardware.xml:2489
 #, no-c-format
 msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2497
+#: hardware.xml:2498
 #, 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:2507
+#: hardware.xml:2508
 #, 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:2516
+#: hardware.xml:2517
 #, no-c-format
 msgid "Drivers Requiring Firmware"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2517
+#: hardware.xml:2518
 #, 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:2523
+#: hardware.xml:2524
 #, 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:2534
+#: hardware.xml:2535
 #, 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:2546
+#: hardware.xml:2547
 #, no-c-format
 msgid "Wireless Network Cards"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2547
+#: hardware.xml:2548
 #, 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:2554
+#: hardware.xml:2555
 #, 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:2560
+#: hardware.xml:2561
 #, 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:2574
+#: hardware.xml:2575
 #, no-c-format
 msgid "Known Issues for &arch-title;"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2575
+#: hardware.xml:2576
 #, no-c-format
 msgid "There are a couple of issues with specific network cards that are worth mentioning here."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:2582
+#: hardware.xml:2583
 #, no-c-format
 msgid "Conflict between tulip and dfme drivers"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2584
+#: hardware.xml:2585
 #, 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:2594
+#: hardware.xml:2595
 #, 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. During the installation the solution 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>."
 msgstr ""
 
 #. Tag: title
-#: hardware.xml:2609
+#: hardware.xml:2610
 #, no-c-format
 msgid "Sun B100 blade"
 msgstr ""
 
 #. Tag: para
-#: hardware.xml:2611
+#: hardware.xml:2612
 #, no-c-format
 msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems."
 msgstr ""