diff options
| author | Holger Wansing <linux@wansing-online.de> | 2012-11-24 22:19:41 +0000 |
|---|---|---|
| committer | Holger Wansing <linux@wansing-online.de> | 2012-11-24 22:19:41 +0000 |
| commit | 34135d24396541ab382b27057b20afb92afc96e1 (patch) | |
| tree | c8327238a476f186fe9d40d4ffa9de418fe7d231 /po/ro/hardware.po | |
| parent | 258fa4da6502f390ea5abcfa2e25f35fa328db10 (diff) | |
| download | installation-guide-34135d24396541ab382b27057b20afb92afc96e1.zip | |
Update po and pot files:
M po/tl/administrivia.po
M po/tl/install-methods.po
M po/tl/partitioning.po
M po/tl/random-bits.po
M po/tl/gpl.po
M po/tl/preparing.po
M po/tl/preseed.po
M po/tl/post-install.po
M po/tl/boot-new.po
M po/tl/using-d-i.po
M po/tl/hardware.po
M po/tl/boot-installer.po
M po/tl/installation-howto.po
M po/ro/administrivia.po
M po/ro/install-methods.po
M po/ro/partitioning.po
M po/ro/random-bits.po
M po/ro/gpl.po
M po/ro/preparing.po
M po/ro/preseed.po
M po/ro/post-install.po
M po/ro/boot-new.po
M po/ro/hardware.po
M po/ro/boot-installer.po
M po/ro/installation-howto.po
M po/pt/install-methods.po
M po/pt/hardware.po
M po/pt/boot-installer.po
M po/da/install-methods.po
M po/da/partitioning.po
M po/da/random-bits.po
M po/da/gpl.po
M po/da/preparing.po
M po/da/preseed.po
M po/da/post-install.po
M po/da/using-d-i.po
M po/da/hardware.po
M po/da/boot-installer.po
M po/da/installation-howto.po
M po/ru/install-methods.po
M po/ru/boot-installer.po
M po/sv/install-methods.po
M po/sv/boot-installer.po
M po/ja/install-methods.po
M po/ja/boot-installer.po
M po/zh_TW/install-methods.po
M po/zh_TW/preseed.po
M po/zh_TW/boot-installer.po
M po/fi/install-methods.po
M po/fi/boot-installer.po
M po/el/install-methods.po
M po/el/boot-installer.po
M po/zh_CN/install-methods.po
M po/zh_CN/boot-installer.po
M po/pot/boot-installer.pot
M po/pot/install-methods.pot
M po/es/install-methods.po
M po/es/boot-installer.po
M po/ko/install-methods.po
M po/ko/boot-installer.po
M po/nl/administrivia.po
M po/nl/install-methods.po
M po/nl/partitioning.po
M po/nl/random-bits.po
M po/nl/gpl.po
M po/nl/preparing.po
M po/nl/preseed.po
M po/nl/post-install.po
M po/nl/boot-new.po
M po/nl/welcome.po
M po/nl/using-d-i.po
M po/nl/hardware.po
M po/nl/boot-installer.po
M po/nl/installation-howto.po
M po/nn/administrivia.po
M po/nn/install-methods.po
M po/nn/partitioning.po
M po/nn/random-bits.po
M po/nn/gpl.po
M po/nn/preparing.po
M po/nn/preseed.po
M po/nn/post-install.po
M po/nn/boot-new.po
M po/nn/welcome.po
M po/nn/using-d-i.po
M po/nn/hardware.po
M po/nn/boot-installer.po
M po/nn/installation-howto.po
M po/vi/install-methods.po
M po/vi/boot-installer.po
Diffstat (limited to 'po/ro/hardware.po')
| -rw-r--r-- | po/ro/hardware.po | 812 |
1 files changed, 694 insertions, 118 deletions
diff --git a/po/ro/hardware.po b/po/ro/hardware.po index c3e0c1251..96af36f01 100644 --- a/po/ro/hardware.po +++ b/po/ro/hardware.po @@ -9,6 +9,7 @@ msgstr "" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" +"Language: \n" "MIME-Version: 1.0\n" "Content-Type: application/x-xml2pot; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" @@ -22,7 +23,10 @@ msgstr "" #. Tag: para #: hardware.xml:7 #, no-c-format -msgid "This section contains information about what hardware you need to get started with &debian;. You will also find links to further information about hardware supported by GNU and &arch-kernel;." +msgid "" +"This section contains information about what hardware you need to get " +"started with &debian;. You will also find links to further information about " +"hardware supported by GNU and &arch-kernel;." msgstr "" #. Tag: title @@ -34,13 +38,23 @@ msgstr "" #. Tag: para #: hardware.xml:21 #, no-c-format -msgid "&debian; does not impose hardware requirements beyond the requirements of the Linux or kFreeBSD kernel and the GNU tool-sets. Therefore, any architecture or platform to which the Linux or kFreeBSD kernel, libc, <command>gcc</command>, etc. have been ported, and for which a &debian; port exists, can run &debian;. Please refer to the Ports pages at <ulink url=\"&url-ports;\"></ulink> for more details on &arch-title; architecture systems which have been tested with &debian-gnu;." +msgid "" +"&debian; does not impose hardware requirements beyond the requirements of " +"the Linux or kFreeBSD kernel and the GNU tool-sets. Therefore, any " +"architecture or platform to which the Linux or kFreeBSD kernel, libc, " +"<command>gcc</command>, etc. have been ported, and for which a &debian; port " +"exists, can run &debian;. Please refer to the Ports pages at <ulink url=" +"\"&url-ports;\"></ulink> for more details on &arch-title; architecture " +"systems which have been tested with &debian-gnu;." msgstr "" #. Tag: para #: hardware.xml:32 #, no-c-format -msgid "Rather than attempting to describe all the different hardware configurations which are supported for &arch-title;, this section contains general information and pointers to where additional information can be found." +msgid "" +"Rather than attempting to describe all the different hardware configurations " +"which are supported for &arch-title;, this section contains general " +"information and pointers to where additional information can be found." msgstr "" #. Tag: title @@ -52,7 +66,9 @@ msgstr "" #. Tag: para #: hardware.xml:42 #, no-c-format -msgid "&debian; GNU/Linux &release; supports eleven major architectures and several variations of each architecture known as <quote>flavors</quote>." +msgid "" +"&debian; GNU/Linux &release; supports eleven major architectures and several " +"variations of each architecture known as <quote>flavors</quote>." msgstr "" #. Tag: entry @@ -430,19 +446,38 @@ msgstr "" #. Tag: para #: hardware.xml:203 #, no-c-format -msgid "This document covers installation for the <emphasis>&arch-title;</emphasis> architecture using the <emphasis>&arch-kernel;</emphasis> kernel. 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." +msgid "" +"This document covers installation for the <emphasis>&arch-title;</emphasis> " +"architecture using the <emphasis>&arch-kernel;</emphasis> kernel. 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:213 #, no-c-format -msgid "The &arch-title; architecture only supports Intel Itanium processors and not the much more common 64-bit processors from the Intel 64 family (including e.g. the Pentium D and the Core2 Duo). Those systems are supported by the <emphasis>amd64</emphasis> architecture or, if you prefer a 32-bit userland, the <emphasis>i386</emphasis> architecture." +msgid "" +"The &arch-title; architecture only supports Intel Itanium processors and not " +"the much more common 64-bit processors from the Intel 64 family (including e." +"g. the Pentium D and the Core2 Duo). Those systems are supported " +"by the <emphasis>amd64</emphasis> architecture or, if you prefer a 32-bit " +"userland, the <emphasis>i386</emphasis> architecture." msgstr "" #. Tag: para #: hardware.xml:223 #, no-c-format -msgid "This is the first official release of &debian-gnu; 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 using the <emphasis>&arch-kernel;</emphasis> kernel. It can be necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink> as well." +msgid "" +"This is the first official release of &debian-gnu; 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 using the <emphasis>&arch-kernel;</emphasis> kernel. It can be " +"necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-" +"listname; mailing list</ulink> as well." msgstr "" #. Tag: title @@ -458,7 +493,8 @@ msgid "Both AMD64 and Intel 64 processors are supported." msgstr "" #. Tag: title -#: hardware.xml:271 hardware.xml:362 hardware.xml:381 hardware.xml:464 hardware.xml:522 hardware.xml:575 +#: hardware.xml:271 hardware.xml:362 hardware.xml:381 hardware.xml:464 +#: hardware.xml:522 hardware.xml:575 #, no-c-format msgid "CPU, Main Boards, and Video Support" msgstr "" @@ -466,13 +502,20 @@ msgstr "" #. Tag: para #: hardware.xml:273 #, 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." +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:282 #, 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." +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 @@ -490,7 +533,13 @@ msgstr "" #. Tag: para #: hardware.xml:298 #, 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>." +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 @@ -502,7 +551,15 @@ msgstr "" #. Tag: para #: hardware.xml:312 #, no-c-format -msgid "Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. We currently support the following Kirkwood based devices: OpenRD (OpenRD-Base, OpenRD-Client and OpenRD-Ultimate), <ulink url=\"&url-arm-cyrius-sheevaplug;\">plug computers (SheevaPlug, GuruPlug and DreamPlug)</ulink>, <ulink url=\"&url-arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (all TS-11x, TS-21x and TS-41x models), and LaCie NASes (Network Space v2, Network Space Max v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2)." +msgid "" +"Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM " +"CPU, Ethernet, SATA, USB, and other functionality in one chip. We currently " +"support the following Kirkwood based devices: OpenRD (OpenRD-Base, OpenRD-" +"Client and OpenRD-Ultimate), <ulink url=\"&url-arm-cyrius-sheevaplug;\">plug " +"computers (SheevaPlug, GuruPlug and DreamPlug)</ulink>, <ulink url=\"&url-" +"arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> (all TS-11x, TS-21x " +"and TS-41x models), and LaCie NASes (Network Space v2, Network Space Max v2, " +"Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2)." msgstr "" #. Tag: term @@ -514,7 +571,14 @@ msgstr "" #. Tag: para #: hardware.xml:329 #, 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-dns323;\">D-Link DNS-323</ulink> and <ulink url=\"&url-arm-cyrius-mv2120;\">HP mv2120</ulink>." +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-dns323;\">D-Link DNS-323</ulink> and <ulink url=\"&url-arm-" +"cyrius-mv2120;\">HP mv2120</ulink>." msgstr "" #. Tag: term @@ -526,19 +590,30 @@ msgstr "" #. Tag: para #: hardware.xml:344 #, 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." +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:363 #, 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." +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:382 #, 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." +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 @@ -550,19 +625,43 @@ msgstr "" #. Tag: para #: hardware.xml:391 #, 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." +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:398 #, 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 "" +"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:431 #, no-c-format -msgid "If your system has a 64-bit processor from the AMD64 or Intel 64 families, 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 64 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 @@ -574,31 +673,69 @@ msgstr "" #. Tag: para #: hardware.xml:441 #, 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, PCI-X, or VESA Local Bus (VLB, sometimes called the VL bus). Essentially all personal computers sold in recent years use one of these." +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, PCI-X, 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:465 #, 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> </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>." +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> </" +"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:500 #, 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." +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." msgstr "" #. Tag: para #: hardware.xml:506 #, 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." +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:523 #, 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 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> </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>." +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 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> </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 @@ -610,7 +747,9 @@ msgstr "" #. Tag: para #: hardware.xml:553 #, no-c-format -msgid "All MIPS based Cobalt machines are supported with the exception of the Qube 2700 (Qube 1)." +msgid "" +"All MIPS based Cobalt machines are supported with the exception of the Qube " +"2700 (Qube 1)." msgstr "" #. Tag: title @@ -628,7 +767,9 @@ msgstr "" #. Tag: para #: hardware.xml:576 #, no-c-format -msgid "For &debian-gnu; &release; only the PMac (Power-Macintosh or PowerMac) and PreP subarchitectures are supported." +msgid "" +"For &debian-gnu; &release; only the PMac (Power-Macintosh or PowerMac) and " +"PreP subarchitectures are supported." msgstr "" #. Tag: title @@ -640,7 +781,9 @@ msgstr "" #. Tag: para #: hardware.xml:599 #, no-c-format -msgid "There are two 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 @@ -652,7 +795,10 @@ msgstr "" #. Tag: para #: hardware.xml:607 #, no-c-format -msgid "Most systems use this kernel flavour, which supports the PowerPC 601, 603, 604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and including the one marketed as G4 use one of these processors." +msgid "" +"Most systems use this kernel flavour, which supports the PowerPC 601, 603, " +"604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and " +"including the one marketed as G4 use one of these processors." msgstr "" #. Tag: term @@ -670,19 +816,26 @@ msgstr "" #. Tag: para #: hardware.xml:622 #, no-c-format -msgid "The POWER3 processor is used in older IBM 64-bit server systems: known models include the IntelliStation POWER Model 265, the pSeries 610 and 640, and the RS/6000 7044-170, 7043-260, and 7044-270." +msgid "" +"The POWER3 processor is used in older IBM 64-bit server systems: known " +"models include the IntelliStation POWER Model 265, the pSeries 610 and 640, " +"and the RS/6000 7044-170, 7043-260, and 7044-270." msgstr "" #. Tag: para #: hardware.xml:628 #, no-c-format -msgid "The POWER4 processor is used in more recent IBM 64-bit server systems: known models include the pSeries 615, 630, 650, 655, 670, and 690." +msgid "" +"The POWER4 processor is used in more recent IBM 64-bit server systems: known " +"models include the pSeries 615, 630, 650, 655, 670, and 690." msgstr "" #. Tag: para #: hardware.xml:633 #, no-c-format -msgid "Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 architecture, and use this kernel flavour." +msgid "" +"Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 " +"architecture, and use this kernel flavour." msgstr "" #. Tag: title @@ -694,25 +847,42 @@ msgstr "" #. Tag: para #: hardware.xml:669 #, no-c-format -msgid "Apple (and briefly a few other manufacturers — 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." +msgid "" +"Apple (and briefly a few other manufacturers — 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:676 #, 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." +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:684 #, 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." +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:692 #, 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>." +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 @@ -740,7 +910,10 @@ msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "" #. Tag: entry -#: hardware.xml:717 hardware.xml:720 hardware.xml:723 hardware.xml:726 hardware.xml:729 hardware.xml:732 hardware.xml:735 hardware.xml:738 hardware.xml:741 hardware.xml:744 hardware.xml:747 hardware.xml:750 hardware.xml:753 hardware.xml:756 hardware.xml:759 hardware.xml:762 +#: hardware.xml:717 hardware.xml:720 hardware.xml:723 hardware.xml:726 +#: hardware.xml:729 hardware.xml:732 hardware.xml:735 hardware.xml:738 +#: hardware.xml:741 hardware.xml:744 hardware.xml:747 hardware.xml:750 +#: hardware.xml:753 hardware.xml:756 hardware.xml:759 hardware.xml:762 #, no-c-format msgid "NewWorld" msgstr "" @@ -842,7 +1015,11 @@ msgid "Performa 4400, 54xx, 5500" msgstr "" #. Tag: entry -#: hardware.xml:765 hardware.xml:768 hardware.xml:771 hardware.xml:774 hardware.xml:777 hardware.xml:780 hardware.xml:783 hardware.xml:786 hardware.xml:789 hardware.xml:792 hardware.xml:795 hardware.xml:798 hardware.xml:804 hardware.xml:807 hardware.xml:813 hardware.xml:819 hardware.xml:825 +#: hardware.xml:765 hardware.xml:768 hardware.xml:771 hardware.xml:774 +#: hardware.xml:777 hardware.xml:780 hardware.xml:783 hardware.xml:786 +#: hardware.xml:789 hardware.xml:792 hardware.xml:795 hardware.xml:798 +#: hardware.xml:804 hardware.xml:807 hardware.xml:813 hardware.xml:819 +#: hardware.xml:825 #, no-c-format msgid "OldWorld" msgstr "" @@ -1084,7 +1261,17 @@ msgstr "" #. Tag: para #: hardware.xml:933 #, 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>." +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 @@ -1096,19 +1283,33 @@ msgstr "" #. Tag: para #: hardware.xml:972 #, 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." +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:981 #, 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." +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:989 #, 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)." +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 @@ -1120,7 +1321,16 @@ msgstr "" #. Tag: para #: hardware.xml:1006 #, no-c-format -msgid "Since &debian; Squeeze, support for booting in ESA/390 mode was dropped. Your machine needs to support the z/Architecture, 64-bit support is mandatory. The userland of the s390 port is still compiled for ESA/390, though. All zSeries and System z hardware is fully supported. &arch-title; support software is included from the kernel 3.1 development stream. The most current information about IBM's Linux support can be found at the <ulink url=\"http://www.ibm.com/developerworks/linux/linux390/development_technical.html\"> Linux on <trademark class=\"registered\">System z</trademark> page on developerWorks</ulink>." +msgid "" +"Since &debian; Squeeze, support for booting in ESA/390 mode was dropped. " +"Your machine needs to support the z/Architecture, 64-bit support is " +"mandatory. The userland of the s390 port is still compiled for ESA/390, " +"though. All zSeries and System z hardware is fully supported. &arch-title; " +"support software is included from the kernel 3.1 development stream. The " +"most current information about IBM's Linux support can be found at the " +"<ulink url=\"http://www.ibm.com/developerworks/linux/linux390/" +"development_technical.html\"> Linux on <trademark class=\"registered" +"\">System z</trademark> page on developerWorks</ulink>." msgstr "" #. Tag: title @@ -1132,7 +1342,11 @@ msgstr "" #. Tag: para #: hardware.xml:1024 #, no-c-format -msgid "PAV and HyperPAV are supported transparently, multipathing is not needed to take advantage of these storage system features. Be sure to configure the devices during DASD device selection. The alias devices will not be offered neither for formatting, partitioning nor direct use." +msgid "" +"PAV and HyperPAV are supported transparently, multipathing is not needed to " +"take advantage of these storage system features. Be sure to configure the " +"devices during DASD device selection. The alias devices will not be offered " +"neither for formatting, partitioning nor direct use." msgstr "" #. Tag: title @@ -1144,7 +1358,11 @@ msgstr "" #. Tag: para #: hardware.xml:1041 #, 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." +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 @@ -1156,13 +1374,20 @@ msgstr "" #. Tag: para #: hardware.xml:1054 #, 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>." +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:1061 #, 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." +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 @@ -1174,7 +1399,13 @@ msgstr "" #. Tag: para #: hardware.xml:1073 #, 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." +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 @@ -1186,13 +1417,19 @@ msgstr "" #. Tag: para #: hardware.xml:1088 #, 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." +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:1099 #, 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." +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 @@ -1204,7 +1441,16 @@ msgstr "" #. Tag: para #: hardware.xml:1109 #, no-c-format -msgid "From a technical point of view, laptops are normal PCs, so all information regarding PC systems applies to laptops as well. Installations on laptops nowadays usually work out of the box, including things like automatically suspending the system on closing the lid and laptop specfic hardware buttons like those for disabling the wifi interfaces (<quote>airplane mode</quote>). Nonetheless sometimes the hardware vendors use specialized or proprietary hardware for some laptop-specific functions which might 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>." +msgid "" +"From a technical point of view, laptops are normal PCs, so all information " +"regarding PC systems applies to laptops as well. Installations on laptops " +"nowadays usually work out of the box, including things like automatically " +"suspending the system on closing the lid and laptop specfic hardware buttons " +"like those for disabling the wifi interfaces (<quote>airplane mode</quote>). " +"Nonetheless sometimes the hardware vendors use specialized or proprietary " +"hardware for some laptop-specific functions which might 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 @@ -1216,61 +1462,108 @@ msgstr "" #. Tag: para #: hardware.xml:1127 #, no-c-format -msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — is available for this architecture. Having multiple processors in a computer was originally only an issue for high-end server systems but has become quite common in recent years even for rather low-end desktop computers and laptops with the introduction of so called <quote>multi-core</quote> processors. These contain two or more processor units, called <quote>cores</quote>, in one physical chip." +msgid "" +"Multiprocessor support — also called <quote>symmetric multiprocessing</" +"quote> or SMP — is available for this architecture. Having multiple " +"processors in a computer was originally only an issue for high-end server " +"systems but has become quite common in recent years even for rather low-end " +"desktop computers and laptops with the introduction of so called " +"<quote>multi-core</quote> processors. These contain two or more processor " +"units, called <quote>cores</quote>, in one physical chip." msgstr "" #. Tag: para #: hardware.xml:1137 #, no-c-format -msgid "The standard &debian; &release; kernel image has been compiled with SMP support. It is also usable on non-SMP systems without problems." +msgid "" +"The standard &debian; &release; kernel image has been compiled with SMP " +"support. It is also usable on non-SMP systems without problems." msgstr "" #. Tag: para #: hardware.xml:1148 #, no-c-format -msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — 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." +msgid "" +"Multiprocessor support — also called <quote>symmetric multiprocessing</" +"quote> or SMP — 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:1157 #, no-c-format -msgid "Having multiple processors in a computer was originally only an issue for high-end server systems but has become quite common in recent years even for rather low-end desktop computers and laptops with the introduction of so called <quote>multi-core</quote> processors. These contain two or more processor units, called <quote>cores</quote>, in one physical chip." +msgid "" +"Having multiple processors in a computer was originally only an issue for " +"high-end server systems but has become quite common in recent years even for " +"rather low-end desktop computers and laptops with the introduction of so " +"called <quote>multi-core</quote> processors. These contain two or more " +"processor units, called <quote>cores</quote>, in one physical chip." msgstr "" #. Tag: para #: hardware.xml:1165 #, no-c-format -msgid "The 486 flavour of the &debian; kernel image packages for &arch-title; is not compiled with SMP support." +msgid "" +"The 486 flavour of the &debian; kernel image packages for &arch-title; is " +"not compiled with SMP support." msgstr "" #. Tag: para #: hardware.xml:1175 #, no-c-format -msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — 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 only the first CPU." +msgid "" +"Multiprocessor support — also called <quote>symmetric multiprocessing</" +"quote> or SMP — 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 only the first CPU." msgstr "" #. Tag: para #: hardware.xml:1184 #, no-c-format -msgid "In order to take advantage of multiple processors, you'll have to replace the standard &debian; kernel.<phrase arch=\"linux-any\"> 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.</phrase>" +msgid "" +"In order to take advantage of multiple processors, you'll have to replace " +"the standard &debian; kernel.<phrase arch=\"linux-any\"> 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.</phrase>" msgstr "" #. Tag: para #: hardware.xml:1198 #, no-c-format -msgid "Multiprocessor support — also called <quote>symmetric multiprocessing</quote> or SMP — 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." +msgid "" +"Multiprocessor support — also called <quote>symmetric multiprocessing</" +"quote> or SMP — 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:1208 #, 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." +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:1214 #, no-c-format -msgid "You can also build your own customized kernel to support SMP.<phrase arch=\"linux-any\"> 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.</phrase>" +msgid "" +"You can also build your own customized kernel to support SMP.<phrase arch=" +"\"linux-any\"> 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.</phrase>" msgstr "" #. Tag: title @@ -1282,13 +1575,26 @@ msgstr "" #. Tag: para #: hardware.xml:1226 #, no-c-format -msgid "&debian;'s support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. On modern PCs, having a graphical display usually works out of the box. Whether advanced graphics card features such as 3D-hardware acceleration or hardware-accelerated video are available, depends on the actual graphics hardware used in the system and in some cases on the installation of additional <quote>firmware</quote> images (see <xref linkend=\"hardware-firmware\"/>). In very few cases there have been reports about hardware on which installation of additional graphics card firmware was required even for basic graphics support, but these have been rare exceptions." +msgid "" +"&debian;'s support for graphical interfaces is determined by the underlying " +"support found in X.Org's X11 system. On modern PCs, having a graphical " +"display usually works out of the box. Whether advanced graphics card " +"features such as 3D-hardware acceleration or hardware-accelerated video are " +"available, depends on the actual graphics hardware used in the system and in " +"some cases on the installation of additional <quote>firmware</quote> images " +"(see <xref linkend=\"hardware-firmware\"/>). In very few cases there have " +"been reports about hardware on which installation of additional graphics " +"card firmware was required even for basic graphics support, but these have " +"been rare exceptions." msgstr "" #. Tag: para #: hardware.xml:1239 #, no-c-format -msgid "Details on supported graphics cards and pointing devices can be found at <ulink url=\"&url-xorg;\"></ulink>. &debian; &release; ships with X.Org version &x11ver;." +msgid "" +"Details on supported graphics cards and pointing devices can be found at " +"<ulink url=\"&url-xorg;\"></ulink>. &debian; &release; ships with X.Org " +"version &x11ver;." msgstr "" #. Tag: para @@ -1300,13 +1606,31 @@ msgstr "" #. Tag: para #: hardware.xml:1249 #, 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." +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:1259 #, 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." +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 @@ -1318,13 +1642,20 @@ msgstr "" #. Tag: para #: hardware.xml:1282 #, no-c-format -msgid "Almost any network interface card (NIC) supported by the &arch-kernel; kernel should also be supported by the installation system; drivers should normally be loaded automatically. <phrase arch=\"x86\">This includes most PCI/PCI-Express cards as well as PCMCIA/Express Cards on laptops.</phrase> <phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase>" +msgid "" +"Almost any network interface card (NIC) supported by the &arch-kernel; " +"kernel should also be supported by the installation system; drivers should " +"normally be loaded automatically. <phrase arch=\"x86\">This includes most " +"PCI/PCI-Express cards as well as PCMCIA/Express Cards on laptops.</phrase> " +"<phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase>" msgstr "" #. Tag: para #: hardware.xml:1292 #, no-c-format -msgid "This includes a lot of generic PCI cards (for systems that have PCI) and the following NICs from Sun:" +msgid "" +"This includes a lot of generic PCI cards (for systems that have PCI) and the " +"following NICs from Sun:" msgstr "" #. Tag: para @@ -1384,7 +1715,9 @@ msgstr "" #. Tag: para #: hardware.xml:1349 #, no-c-format -msgid "On &arch-title;, most built-in Ethernet devices are supported and modules for additional PCI and USB devices are provided." +msgid "" +"On &arch-title;, most built-in Ethernet devices are supported and modules " +"for additional PCI and USB devices are provided." msgstr "" #. Tag: para @@ -1402,31 +1735,52 @@ msgstr "" #. Tag: para #: hardware.xml:1362 #, no-c-format -msgid "Wireless networking is in general supported as well and a growing number of wireless adapters are supported by the official &arch-kernel; kernel, although many of them do require firmware to be loaded." +msgid "" +"Wireless networking is in general supported as well and a growing number of " +"wireless adapters are supported by the official &arch-kernel; kernel, " +"although many of them do require firmware to be loaded." msgstr "" #. Tag: para #: hardware.xml:1369 #, no-c-format -msgid "If firmware is needed, the installer will prompt you to load firmware. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware during the installation." +msgid "" +"If firmware is needed, the installer will prompt you to load firmware. See " +"<xref linkend=\"loading-firmware\"/> for detailed information on how to load " +"firmware during the installation." msgstr "" #. Tag: para #: hardware.xml:1374 #, no-c-format -msgid "Wireless NICs that are not supported by the official &arch-kernel; kernel can generally be made to work under &debian-gnu;, but are not supported during the installation." +msgid "" +"Wireless NICs that are not supported by the official &arch-kernel; kernel " +"can generally be made to work under &debian-gnu;, but are not supported " +"during the installation." msgstr "" #. Tag: para #: hardware.xml:1379 #, no-c-format -msgid "If there is a problem with wireless and there is no other NIC you can use during the installation, it is still possible to install &debian-gnu; 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." +msgid "" +"If there is a problem with wireless and there is no other NIC you can use " +"during the installation, it is still possible to install &debian-gnu; 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:1389 #, 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 "" +"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 @@ -1438,7 +1792,9 @@ msgstr "" #. Tag: para #: hardware.xml:1404 #, no-c-format -msgid "There are a couple of issues with specific network cards that are worth mentioning here." +msgid "" +"There are a couple of issues with specific network cards that are worth " +"mentioning here." msgstr "" #. Tag: title @@ -1450,19 +1806,35 @@ msgstr "" #. Tag: para #: hardware.xml:1413 #, 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 "" +"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:1423 #, 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 "" +"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:1431 #, 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 "" +"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 @@ -1474,7 +1846,9 @@ msgstr "" #. Tag: para #: hardware.xml:1446 #, no-c-format -msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems." +msgid "" +"The <literal>cassini</literal> network driver does not work with Sun B100 " +"blade systems." msgstr "" #. Tag: title @@ -1486,7 +1860,13 @@ msgstr "" #. Tag: para #: hardware.xml:1462 #, no-c-format -msgid "Support for braille displays is determined by the underlying support found in <classname>brltty</classname>. Most displays work under <classname>brltty</classname>, connected via either a serial port, USB or bluetooth. Details on supported braille devices can be found on the <ulink url=\"&url-brltty;\"><classname>brltty</classname> website</ulink>. &debian-gnu; &release; ships with <classname>brltty</classname> version &brlttyver;." +msgid "" +"Support for braille displays is determined by the underlying support found " +"in <classname>brltty</classname>. Most displays work under " +"<classname>brltty</classname>, connected via either a serial port, USB or " +"bluetooth. Details on supported braille devices can be found on the <ulink " +"url=\"&url-brltty;\"><classname>brltty</classname> website</ulink>. &debian-" +"gnu; &release; ships with <classname>brltty</classname> version &brlttyver;." msgstr "" #. Tag: title @@ -1498,7 +1878,15 @@ msgstr "" #. Tag: para #: hardware.xml:1477 #, no-c-format -msgid "Support for hardware speech synthesis devices is determined by the underlying support found in <classname>speakup</classname>. <classname>speakup</classname> only supports integrated boards and external devices connected to a serial port (no USB, serial-to-USB or PCI adapters are supported). Details on supported hardware speech synthesis devices can be found on the <ulink url=\"&url-speakup;\"><classname>speakup</classname> website</ulink>. &debian-gnu; &release; ships with <classname>speakup</classname> version &speakupver;." +msgid "" +"Support for hardware speech synthesis devices is determined by the " +"underlying support found in <classname>speakup</classname>. " +"<classname>speakup</classname> only supports integrated boards and external " +"devices connected to a serial port (no USB, serial-to-USB or PCI adapters " +"are supported). Details on supported hardware speech synthesis devices can " +"be found on the <ulink url=\"&url-speakup;\"><classname>speakup</classname> " +"website</ulink>. &debian-gnu; &release; ships with <classname>speakup</" +"classname> version &speakupver;." msgstr "" #. Tag: title @@ -1510,25 +1898,37 @@ msgstr "" #. Tag: para #: hardware.xml:1498 #, no-c-format -msgid "&arch-kernel; 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 "" +"&arch-kernel; 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:1504 #, no-c-format -msgid "USB hardware generally works fine. On some very old PC systems some USB keyboards may require additional configuration (see <xref linkend=\"hardware-issues\"/>). On modern PCs, USB keyboards and mice work without requiring any specific configuration." +msgid "" +"USB hardware generally works fine. On some very old PC systems some USB " +"keyboards may require additional configuration (see <xref linkend=\"hardware-" +"issues\"/>). On modern PCs, USB keyboards and mice work without requiring " +"any specific configuration." msgstr "" #. Tag: para #: hardware.xml:1513 #, 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 "" +"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:1519 #, no-c-format -msgid "The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot." +msgid "" +"The Cobalt RaQ has no support for additional devices but the Qube has one " +"PCI slot." msgstr "" #. Tag: title @@ -1540,31 +1940,63 @@ msgstr "" #. Tag: para #: hardware.xml:1532 #, 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. With many graphics cards, basic functionality is available without additional firmware, but the use of advanced features requires an appropriate firmware file to be installed in the system." +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. With many graphics cards, basic functionality is available without " +"additional firmware, but the use of advanced features requires an " +"appropriate firmware file to be installed in the system." msgstr "" #. Tag: para #: hardware.xml:1543 #, no-c-format -msgid "On many older devices which require firmware to work, the firmware file was permanently placed in an EEPROM/Flash chip on the device itself by the manufacturer. Nowadays most new devices do not have the firmware embedded this way anymore, so the firmware file must be uploaded into the device by the host operating system every time the system boots." +msgid "" +"On many older devices which require firmware to work, the firmware file was " +"permanently placed in an EEPROM/Flash chip on the device itself by the " +"manufacturer. Nowadays most new devices do not have the firmware embedded " +"this way anymore, so the firmware file must be uploaded into the device by " +"the host operating system every time the system boots." msgstr "" #. Tag: para #: hardware.xml:1551 #, no-c-format -msgid "In most cases firmware is non-free according to the criteria used by the &debian-gnu; 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-gnu; legally can distribute the firmware, it will often be available as a separate package from the non-free section of the archive." +msgid "" +"In most cases firmware is non-free according to the criteria used by the " +"&debian-gnu; 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-gnu; 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:1560 #, no-c-format -msgid "However, this does not mean that such hardware cannot be used during an installation. Starting with &debian-gnu; 5.0, &d-i; supports loading firmware files or packages containing firmware from a removable medium, such as a USB stick. See <xref linkend=\"loading-firmware\"/> for detailed information on how to load firmware files or packages during the installation." +msgid "" +"However, this does not mean that such hardware cannot be used during an " +"installation. Starting with &debian-gnu; 5.0, &d-i; supports loading " +"firmware files or packages containing firmware from a removable medium, such " +"as a USB stick. See <xref linkend=\"loading-firmware\"/> for detailed " +"information on how to load firmware files or packages during the " +"installation." msgstr "" #. Tag: para #: hardware.xml:1569 #, no-c-format -msgid "If the &d-i; prompts for a firmware file and you do not have this firmware file available or do not want to install a non-free firmware file on your system, you can try to proceed without loading the firmware. There are several cases where a driver prompts for additional firmware because it may be needed under certain circumstances, but the device does work without it on most systems (this e.g. happens with certain network cards using the tg3 driver)." +msgid "" +"If the &d-i; prompts for a firmware file and you do not have this firmware " +"file available or do not want to install a non-free firmware file on your " +"system, you can try to proceed without loading the firmware. There are " +"several cases where a driver prompts for additional firmware because it may " +"be needed under certain circumstances, but the device does work without it " +"on most systems (this e.g. happens with certain network cards using the tg3 " +"driver)." msgstr "" #. Tag: title @@ -1576,19 +2008,35 @@ msgstr "" #. Tag: para #: hardware.xml:1588 #, 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." +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:1596 #, 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." +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:1604 #, no-c-format -msgid "Whether or not you are purchasing a system with &arch-kernel; bundled, or even a used system, it is still important to check that your hardware is supported by the &arch-kernel; kernel. Check if your hardware is listed in the references found above. Let your salesperson (if any) know that you're shopping for a &arch-kernel; system. Support &arch-kernel;-friendly hardware vendors." +msgid "" +"Whether or not you are purchasing a system with &arch-kernel; bundled, or " +"even a used system, it is still important to check that your hardware is " +"supported by the &arch-kernel; kernel. Check if your hardware is listed in " +"the references found above. Let your salesperson (if any) know that you're " +"shopping for a &arch-kernel; system. Support &arch-kernel;-friendly hardware " +"vendors." msgstr "" #. Tag: title @@ -1600,31 +2048,67 @@ msgstr "" #. Tag: para #: hardware.xml:1616 #, 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 driver's source code, which is one of the central elements of free software. Since we haven't been granted access to usable documentation on these devices, they simply won't work under &arch-kernel;." +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 driver's " +"source code, which is one of the central elements of free software. Since we " +"haven't been granted access to usable documentation on these devices, they " +"simply won't work under &arch-kernel;." msgstr "" #. Tag: para #: hardware.xml:1626 #, no-c-format -msgid "In many cases there are standards (or at least some de-facto standards) describing how an operating system and its device drivers communicate with a certain class of devices. All devices which comply to such a (de-facto-)standard can be used with a single generic device driver and no device-specific drivers are required. With some kinds of hardware (e.g. USB <quote>Human Interface Devices</quote>, i.e. keyboards, mice, etc., and USB mass storage devices like USB flash disks and memory card readers) this works very well and practically every device sold in the market is standards-compliant." +msgid "" +"In many cases there are standards (or at least some de-facto standards) " +"describing how an operating system and its device drivers communicate with a " +"certain class of devices. All devices which comply to such a (de-facto-)" +"standard can be used with a single generic device driver and no device-" +"specific drivers are required. With some kinds of hardware (e.g. USB " +"<quote>Human Interface Devices</quote>, i.e. keyboards, mice, etc., and USB " +"mass storage devices like USB flash disks and memory card readers) this " +"works very well and practically every device sold in the market is standards-" +"compliant." msgstr "" #. Tag: para #: hardware.xml:1638 #, no-c-format -msgid "In other fields, among them e.g. printers, this is unfortunately not the case. While there are many printers which can be addressed via a small set of (de-facto-)standard control languages and therefore can be made to work without problems in any operating system, there are quite a few models which only understand proprietary control commands for which no usable documentation is available and therefore either cannot be used at all on free operating systems or can only be used with a vendor-supplied closed-source driver." +msgid "" +"In other fields, among them e.g. printers, this is unfortunately not the " +"case. While there are many printers which can be addressed via a small set " +"of (de-facto-)standard control languages and therefore can be made to work " +"without problems in any operating system, there are quite a few models which " +"only understand proprietary control commands for which no usable " +"documentation is available and therefore either cannot be used at all on " +"free operating systems or can only be used with a vendor-supplied closed-" +"source driver." msgstr "" #. Tag: para #: hardware.xml:1649 #, no-c-format -msgid "Even if there is a vendor-provided closed-source driver for such hardware when purchasing the device, the practical lifespan of the device is limited by driver availability. Nowadays product cycles have become short and it is not uncommon that a short time after a consumer device has ceased production, no driver updates get made available any more by the manufacturer. If the old closed-source driver does not work anymore after a system update, an otherwise perfectly working device becomes unusable due to lacking driver support and there is nothing that can be done in this case. You should therefore avoid buying closed hardware in the first place, regardless of the operating system you want to use it with." +msgid "" +"Even if there is a vendor-provided closed-source driver for such hardware " +"when purchasing the device, the practical lifespan of the device is limited " +"by driver availability. Nowadays product cycles have become short and it is " +"not uncommon that a short time after a consumer device has ceased " +"production, no driver updates get made available any more by the " +"manufacturer. If the old closed-source driver does not work anymore after a " +"system update, an otherwise perfectly working device becomes unusable due to " +"lacking driver support and there is nothing that can be done in this case. " +"You should therefore avoid buying closed hardware in the first place, " +"regardless of the operating system you want to use it with." msgstr "" #. Tag: para #: hardware.xml:1662 #, no-c-format -msgid "You can help improve this situation by encouraging manufacturers of closed hardware to release the documentation and other resources necessary for us to provide free drivers for their hardware." +msgid "" +"You can help improve this situation by encouraging manufacturers of closed " +"hardware to release the documentation and other resources necessary for us " +"to provide free drivers for their hardware." msgstr "" #. Tag: title @@ -1636,7 +2120,12 @@ msgstr "" #. Tag: para #: hardware.xml:1679 #, no-c-format -msgid "This section will help you determine which different media types you can use 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 "" +"This section will help you determine which different media types you can use " +"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 @@ -1648,7 +2137,10 @@ msgstr "" #. Tag: para #: hardware.xml:1690 #, 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 "" +"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 @@ -1666,7 +2158,10 @@ msgstr "" #. Tag: para #: hardware.xml:1705 #, 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." +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." msgstr "" #. Tag: para @@ -1684,7 +2179,9 @@ msgstr "" #. Tag: para #: hardware.xml:1719 #, 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 "" +"USB CD-ROM drives are also supported, as are FireWire devices that are " +"supported by the ohci1394 and sbp2 drivers." msgstr "" #. Tag: para @@ -1696,7 +2193,14 @@ msgstr "" #. Tag: para #: hardware.xml:1728 #, 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." +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." msgstr "" #. Tag: title @@ -1708,7 +2212,13 @@ msgstr "" #. Tag: para #: hardware.xml:1744 #, no-c-format -msgid "USB flash disks a.k.a. USB memory sticks have become a commonly used and cheap storage device. Most modern computer systems also allow booting the &d-i; from such a stick. Many modern computer systems, in particular netbooks and thin laptops, do not have a CD/DVD-ROM drive anymore at all and booting from USB media ist the standard way of installing a new operating system on them." +msgid "" +"USB flash disks a.k.a. USB memory sticks have become a commonly used and " +"cheap storage device. Most modern computer systems also allow booting the &d-" +"i; from such a stick. Many modern computer systems, in particular netbooks " +"and thin laptops, do not have a CD/DVD-ROM drive anymore at all and booting " +"from USB media ist the standard way of installing a new operating system on " +"them." msgstr "" #. Tag: title @@ -1720,19 +2230,36 @@ msgstr "" #. Tag: para #: hardware.xml:1758 #, 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 "" +"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:1768 #, no-c-format -msgid "You can also <emphasis>boot</emphasis> the installation system over the network without needing any local media like CDs/DVDs or USB sticks. If you already have a netboot-infrastructure available (i.e. you are already running DHCP and TFTP services in your network), this allows an easy and fast deployment of a large number of machines. Setting up the necessary infrastructure requires a certain level of technical experience, so this is not recommended for novice users. <phrase arch=\"mips;mipsel\">This is the preferred installation technique for &arch-title;.</phrase>" +msgid "" +"You can also <emphasis>boot</emphasis> the installation system over the " +"network without needing any local media like CDs/DVDs or USB sticks. If you " +"already have a netboot-infrastructure available (i.e. you are already " +"running DHCP and TFTP services in your network), this allows an easy and " +"fast deployment of a large number of machines. Setting up the necessary " +"infrastructure requires a certain level of technical experience, so this is " +"not recommended for novice users. <phrase arch=\"mips;mipsel\">This is the " +"preferred installation technique for &arch-title;.</phrase>" msgstr "" #. Tag: para #: hardware.xml:1781 #, 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 "" +"Diskless installation, using network booting from a local area network and " +"NFS-mounting of all local filesystems, is another option." msgstr "" #. Tag: title @@ -1744,13 +2271,19 @@ msgstr "" #. Tag: para #: hardware.xml:1792 #, 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. This method is only recommended for special cases when no other installation method is available." +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. This method is only recommended for " +"special cases when no other installation method is available." msgstr "" #. Tag: para #: hardware.xml:1799 #, 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 "" +"Although the &arch-title; does not allow booting from SunOS (Solaris), you " +"can install from a SunOS partition (UFS slices)." msgstr "" #. Tag: title @@ -1762,7 +2295,14 @@ msgstr "" #. Tag: para #: hardware.xml:1810 #, no-c-format -msgid "If you are running another Unix-like system, you could use it to install &debian-gnu; 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\"/>. This installation method is only recommended for advanced users when no other installation method is available." +msgid "" +"If you are running another Unix-like system, you could use it to install " +"&debian-gnu; 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\"/>. This " +"installation method is only recommended for advanced users when no other " +"installation method is available." msgstr "" #. Tag: title @@ -1774,43 +2314,69 @@ msgstr "" #. Tag: para #: hardware.xml:1825 #, no-c-format -msgid "The &debian; installer contains a kernel which is built to maximize the number of systems it runs on." +msgid "" +"The &debian; installer contains a kernel which is built to maximize the " +"number of systems it runs on." msgstr "" #. Tag: para #: hardware.xml:1829 #, no-c-format -msgid "Generally, the &debian; installation system includes support for IDE (also known as PATA) drives, SATA and SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS." +msgid "" +"Generally, the &debian; installation system includes support for IDE (also " +"known as PATA) drives, 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:1846 #, 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 "" +"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:1879 #, 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 "" +"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:1885 #, 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 "" +"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:1891 #, no-c-format -msgid "Any storage system supported by the Linux kernel is also supported by the boot system." +msgid "" +"Any storage system supported by the Linux kernel is also supported by the " +"boot system." msgstr "" #. Tag: para #: hardware.xml:1896 #, 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)." +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 @@ -1822,12 +2388,22 @@ msgstr "" #. Tag: para #: hardware.xml:1915 #, 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 "" +"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:1922 #, 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 "" +"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 "" - |