diff options
Diffstat (limited to 'po/pot')
| -rw-r--r-- | po/pot/hardware.pot | 518 | ||||
| -rw-r--r-- | po/pot/install-methods.pot | 111 | ||||
| -rw-r--r-- | po/pot/partitioning.pot | 70 | ||||
| -rw-r--r-- | po/pot/post-install.pot | 126 | ||||
| -rw-r--r-- | po/pot/preseed.pot | 10 |
5 files changed, 423 insertions, 412 deletions
diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot index cdfc71440..470e29998 100644 --- a/po/pot/hardware.pot +++ b/po/pot/hardware.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-08-16 18:10+0000\n" +"POT-Creation-Date: 2006-08-18 17:32+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -303,13 +303,13 @@ msgid "DECstation" msgstr "" #. Tag: entry -#: hardware.xml:133 hardware.xml:1044 hardware.xml:1059 hardware.xml:1069 +#: hardware.xml:133 hardware.xml:1087 hardware.xml:1102 hardware.xml:1112 #, no-c-format msgid "r4k-kn04" msgstr "" #. Tag: entry -#: hardware.xml:135 hardware.xml:1039 hardware.xml:1049 hardware.xml:1054 hardware.xml:1064 +#: hardware.xml:135 hardware.xml:1082 hardware.xml:1092 hardware.xml:1097 hardware.xml:1107 #, no-c-format msgid "r3k-kn02" msgstr "" @@ -519,7 +519,7 @@ msgid "This is the first official release of &debian; for the &arch-title; archi msgstr "" #. Tag: title -#: hardware.xml:231 hardware.xml:690 hardware.xml:726 hardware.xml:802 hardware.xml:821 hardware.xml:864 hardware.xml:906 hardware.xml:974 hardware.xml:1133 hardware.xml:1579 +#: hardware.xml:231 hardware.xml:690 hardware.xml:726 hardware.xml:802 hardware.xml:821 hardware.xml:907 hardware.xml:949 hardware.xml:1017 hardware.xml:1176 hardware.xml:1622 #, no-c-format msgid "CPU, Main Boards, and Video Support" msgstr "" @@ -1641,7 +1641,7 @@ msgid "Complete information concerning supported peripherals can be found at <ul msgstr "" #. Tag: title -#: hardware.xml:699 hardware.xml:830 hardware.xml:947 +#: hardware.xml:699 hardware.xml:830 hardware.xml:990 #, no-c-format msgid "<title>CPU</title>" msgstr "" @@ -1715,209 +1715,221 @@ msgstr "" #. Tag: para #: hardware.xml:831 #, no-c-format -msgid "Nearly all x86-based processors are supported; this includes AMD and VIA (former Cyrix) processors as well. Also the new processors like Athlon XP and Intel P4 Xeon are supported. However, Linux will <emphasis>not</emphasis> run on 286 or earlier processors." +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-bits AMD and VIA (former Cyrix) processors, and new processors like the Athlon XP and Intel P4 Xeon." +msgstr "" + +#. Tag: para +#: hardware.xml:839 +#, no-c-format +msgid "If your system has a 64-bits AMD64, Intel EM64t or Intel Core 2 Duo processor, you will probably want to use the installer for the amd64 architecture instead of the installer for the (32-bits) i386 architecture." +msgstr "" + +#. Tag: para +#: hardware.xml:846 +#, no-c-format +msgid "However, Debian GNU/Linux &releasename; will <emphasis>not</emphasis> run on 386 or earlier processors. Despite the architecture name \"i386\", Debian Sarge has <emphasis>dropped support</emphasis> for actual 80386 processors (and their clones), which were supported by earlier releases<footnote> <para> We have long tried to avoid this, but in the end it was necessary due a unfortunate series of issues with the compiler and the kernel, starting with an bug in the C++ ABI provided by GCC. You should still be able to run Debian GNU/Linux on actual 80386 processors if you compile your own kernel and compile all packages from source, but that is beyond the scope of this manual. </para> </footnote>. (No version of Linux has ever supported the 286 or earlier chips in the series.) All i486 and later processors are still supported<footnote> <para> Many Debian packages will actually run slightly faster on modern computers as a positive side effect of dropping support for these old chips. The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the i386, introduced in 1986, did not have. Previously, these could not be easily used by most Debian packages; now they can. </para> </footnote>." msgstr "" #. Tag: title -#: hardware.xml:841 +#: hardware.xml:883 #, no-c-format msgid "I/O Bus" msgstr "" #. Tag: para -#: hardware.xml:842 +#: hardware.xml:884 #, 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, the Microchannel Architecture (MCA, used in IBM's PS/2 line), or VESA Local Bus (VLB, sometimes called the VL bus)." +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, the Microchannel Architecture (MCA, used in IBM's PS/2 line), 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:865 +#: hardware.xml:908 #, no-c-format msgid "Complete information concerning supported M68000 based (<emphasis>&architecture;</emphasis>) systems can be found at the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. This section merely outlines the basics." msgstr "" #. Tag: para -#: hardware.xml:872 +#: hardware.xml:915 #, no-c-format msgid "The &architecture; port of Linux runs on any 680x0 with a PMMU (Paged Memory Management Unit) and a FPU (floating-point unit). This includes the 68020 with an external 68851 PMMU, the 68030, and better, and excludes the <quote>EC</quote> line of 680x0 processors. See the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink> for complete details." msgstr "" #. Tag: para -#: hardware.xml:880 +#: hardware.xml:923 #, no-c-format msgid "There are four major supported <emphasis>&architecture;</emphasis> flavors: Amiga, Atari, Macintosh and VME machines. Amiga and Atari were the first two systems to which Linux was ported; in keeping, they are also the two most well-supported Debian ports. The Macintosh line is supported incompletely, both by Debian and by the Linux kernel; see <ulink url=\"&url-m68k-mac;\">Linux m68k for Macintosh</ulink> for project status and supported hardware. The BVM and Motorola single board VMEbus computers are the most recent addition to the list of machines supported by Debian. Ports to other &architecture; architectures, such as the Sun3 architecture and NeXT black box, are underway but not yet supported by Debian." msgstr "" #. Tag: para -#: hardware.xml:907 +#: hardware.xml:950 #, 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> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </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:948 +#: hardware.xml:991 #, 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. The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with two cores which are supported in SMP mode by this installer. Similarly, the BCM91480B evaluation board contains an SB1A 1480 chip with four cores which are supported in SMP mode." msgstr "" #. Tag: para -#: hardware.xml:958 +#: hardware.xml:1001 #, 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." msgstr "" #. Tag: para -#: hardware.xml:975 +#: hardware.xml:1018 #, no-c-format msgid "Debian on &arch-title; supports the following platforms: <itemizedlist> <listitem><para> DECstation: various models of the DECstation are supported. </para></listitem> <listitem><para> Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt Qube 2700 (Qube1), RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board from Broadcom based on the quad-core SB1A 1480 CPU. </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 -#: hardware.xml:1015 +#: hardware.xml:1058 #, no-c-format msgid "CPU/Machine types" msgstr "" #. Tag: para -#: hardware.xml:1017 +#: hardware.xml:1060 #, no-c-format msgid "Currently only DECstations with R3000 and R4000/R4400 CPUs are supported by the Debian installation system on little endian MIPS. The Debian installation system works on the following machines:" msgstr "" #. Tag: entry -#: hardware.xml:1029 +#: hardware.xml:1072 #, no-c-format msgid "System Type" msgstr "" #. Tag: entry -#: hardware.xml:1029 +#: hardware.xml:1072 #, no-c-format msgid "<entry>CPU</entry>" msgstr "" #. Tag: entry -#: hardware.xml:1029 +#: hardware.xml:1072 #, no-c-format msgid "Code-name" msgstr "" #. Tag: entry -#: hardware.xml:1030 +#: hardware.xml:1073 #, no-c-format msgid "Debian subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1036 +#: hardware.xml:1079 #, no-c-format msgid "DECstation 5000/1xx" msgstr "" #. Tag: entry -#: hardware.xml:1037 hardware.xml:1047 hardware.xml:1052 hardware.xml:1062 +#: hardware.xml:1080 hardware.xml:1090 hardware.xml:1095 hardware.xml:1105 #, no-c-format msgid "R3000" msgstr "" #. Tag: entry -#: hardware.xml:1038 hardware.xml:1043 +#: hardware.xml:1081 hardware.xml:1086 #, no-c-format msgid "3MIN" msgstr "" #. Tag: entry -#: hardware.xml:1041 +#: hardware.xml:1084 #, no-c-format msgid "DECstation 5000/150" msgstr "" #. Tag: entry -#: hardware.xml:1042 hardware.xml:1067 +#: hardware.xml:1085 hardware.xml:1110 #, no-c-format msgid "R4000" msgstr "" #. Tag: entry -#: hardware.xml:1046 +#: hardware.xml:1089 #, no-c-format msgid "DECstation 5000/200" msgstr "" #. Tag: entry -#: hardware.xml:1048 +#: hardware.xml:1091 #, no-c-format msgid "3MAX" msgstr "" #. Tag: entry -#: hardware.xml:1051 +#: hardware.xml:1094 #, no-c-format msgid "DECstation 5000/240" msgstr "" #. Tag: entry -#: hardware.xml:1053 hardware.xml:1058 +#: hardware.xml:1096 hardware.xml:1101 #, no-c-format msgid "3MAX+" msgstr "" #. Tag: entry -#: hardware.xml:1056 +#: hardware.xml:1099 #, no-c-format msgid "DECstation 5000/260" msgstr "" #. Tag: entry -#: hardware.xml:1057 +#: hardware.xml:1100 #, no-c-format msgid "R4400" msgstr "" #. Tag: entry -#: hardware.xml:1061 +#: hardware.xml:1104 #, no-c-format msgid "Personal DECstation 5000/xx" msgstr "" #. Tag: entry -#: hardware.xml:1063 hardware.xml:1068 +#: hardware.xml:1106 hardware.xml:1111 #, no-c-format msgid "Maxine" msgstr "" #. Tag: entry -#: hardware.xml:1066 +#: hardware.xml:1109 #, no-c-format msgid "Personal DECstation 5000/50" msgstr "" #. Tag: para -#: hardware.xml:1073 +#: hardware.xml:1116 #, no-c-format msgid "All Cobalt machines are supported. In the past, only machines with a serial console were supported (that is, all machines except for the Qube 2700, aka Qube1). However, installations are now also possible through SSH." msgstr "" #. Tag: para -#: hardware.xml:1080 +#: hardware.xml:1123 #, no-c-format msgid "The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with two cores which are supported in SMP mode by this installer. Similarly, the BCM91480B evaluation board contains an SB1A 1480 chip with four cores which are supported in SMP mode." msgstr "" #. Tag: title -#: hardware.xml:1090 +#: hardware.xml:1133 #, no-c-format msgid "Supported console options" msgstr "" #. Tag: para -#: hardware.xml:1091 +#: hardware.xml:1134 #, no-c-format msgid "A serial console is available on all supported DECstations (9600 bps, 8N1). To use the serial console, you have to boot the installer image with the <literal>console=ttyS</literal><replaceable>x</replaceable> kernel parameter (with <replaceable>x</replaceable> being the number of the serial port you have your terminal connected to — usually <literal>2</literal>, but <literal>0</literal> for the Personal DECstations). On 3MIN and 3MAX+ (DECstation 5000/1xx, 5000/240 and 5000/260) a local console is available with the PMAG-BA and the PMAGB-B graphics options." msgstr "" #. Tag: para -#: hardware.xml:1102 +#: hardware.xml:1145 #, no-c-format msgid "" "If you have a Linux system to use as serial terminal, an easy way is to run <command>cu</command><footnote> <para> In Woody this command was part of the <classname>uucp</classname> package, but in later releases it is available as a separate package. </para> </footnote> on it. Example: <informalexample><screen>\n" @@ -1926,1267 +1938,1267 @@ msgid "" msgstr "" #. Tag: para -#: hardware.xml:1120 +#: hardware.xml:1163 #, no-c-format msgid "Both Cobalt and Broadcom BCM91250A/BCM91480B use 115200 bps." msgstr "" #. Tag: para -#: hardware.xml:1134 +#: hardware.xml:1177 #, no-c-format msgid "There are four major supported <emphasis>&architecture;</emphasis> subarchitectures: PMac (Power-Macintosh or PowerMac), PReP, APUS (Amiga Power-UP System), and CHRP machines. Each subarchitecture has its own boot methods. In addition, there are four different kernel flavours, supporting different CPU variants." msgstr "" #. Tag: para -#: hardware.xml:1142 +#: hardware.xml:1185 #, no-c-format msgid "Ports to other <emphasis>&architecture;</emphasis> architectures, such as the Be-Box and MBX architecture, are underway but not yet supported by Debian. We may have a 64-bit port in the future." msgstr "" #. Tag: title -#: hardware.xml:1150 +#: hardware.xml:1193 #, no-c-format msgid "Kernel Flavours" msgstr "" #. Tag: para -#: hardware.xml:1152 +#: hardware.xml:1195 #, no-c-format msgid "There are four flavours of the powerpc kernel in Debian, based on the CPU type:" msgstr "" #. Tag: term -#: hardware.xml:1159 +#: hardware.xml:1202 #, no-c-format msgid "<term>powerpc</term>" msgstr "" #. Tag: para -#: hardware.xml:1160 +#: hardware.xml:1203 #, 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." msgstr "" #. Tag: term -#: hardware.xml:1170 +#: hardware.xml:1213 #, no-c-format msgid "power64" msgstr "" #. Tag: para -#: hardware.xml:1171 +#: hardware.xml:1214 #, no-c-format msgid "The power64 kernel flavour supports the following CPUs:" msgstr "" #. Tag: para -#: hardware.xml:1175 +#: hardware.xml:1218 #, 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." msgstr "" #. Tag: para -#: hardware.xml:1181 +#: hardware.xml:1224 #, 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." msgstr "" #. Tag: para -#: hardware.xml:1186 +#: hardware.xml:1229 #, no-c-format msgid "Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 architecture, and use this kernel flavour." msgstr "" #. Tag: term -#: hardware.xml:1195 +#: hardware.xml:1238 #, no-c-format msgid "<term>prep</term>" msgstr "" #. Tag: para -#: hardware.xml:1196 +#: hardware.xml:1239 #, no-c-format msgid "This kernel flavour supports the PReP subarchitecture." msgstr "" #. Tag: term -#: hardware.xml:1204 +#: hardware.xml:1247 #, no-c-format msgid "<term>apus</term>" msgstr "" #. Tag: para -#: hardware.xml:1205 +#: hardware.xml:1248 #, no-c-format msgid "This kernel flavour supports the Amiga Power-UP System, though it is currently disabled." msgstr "" #. Tag: title -#: hardware.xml:1218 +#: hardware.xml:1261 #, no-c-format msgid "Power Macintosh (pmac) subarchitecture" msgstr "" #. Tag: para -#: hardware.xml:1220 +#: hardware.xml:1263 #, 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." msgstr "" #. Tag: para -#: hardware.xml:1227 +#: hardware.xml:1270 #, 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." msgstr "" #. Tag: para -#: hardware.xml:1235 +#: hardware.xml:1278 #, 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." msgstr "" #. Tag: para -#: hardware.xml:1243 +#: hardware.xml:1286 #, 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>." msgstr "" #. Tag: entry -#: hardware.xml:1259 hardware.xml:1394 hardware.xml:1438 hardware.xml:1467 +#: hardware.xml:1302 hardware.xml:1437 hardware.xml:1481 hardware.xml:1510 #, no-c-format msgid "Model Name/Number" msgstr "" #. Tag: entry -#: hardware.xml:1260 +#: hardware.xml:1303 #, no-c-format msgid "Generation" msgstr "" #. Tag: entry -#: hardware.xml:1266 +#: hardware.xml:1309 #, no-c-format msgid "Apple" msgstr "" #. Tag: entry -#: hardware.xml:1267 +#: hardware.xml:1310 #, no-c-format msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "" #. Tag: entry -#: hardware.xml:1268 hardware.xml:1271 hardware.xml:1274 hardware.xml:1277 hardware.xml:1280 hardware.xml:1283 hardware.xml:1286 hardware.xml:1289 hardware.xml:1292 hardware.xml:1295 hardware.xml:1298 hardware.xml:1301 hardware.xml:1304 hardware.xml:1307 hardware.xml:1310 hardware.xml:1313 +#: hardware.xml:1311 hardware.xml:1314 hardware.xml:1317 hardware.xml:1320 hardware.xml:1323 hardware.xml:1326 hardware.xml:1329 hardware.xml:1332 hardware.xml:1335 hardware.xml:1338 hardware.xml:1341 hardware.xml:1344 hardware.xml:1347 hardware.xml:1350 hardware.xml:1353 hardware.xml:1356 #, no-c-format msgid "NewWorld" msgstr "" #. Tag: entry -#: hardware.xml:1270 +#: hardware.xml:1313 #, no-c-format msgid "iMac Summer 2000, Early 2001" msgstr "" #. Tag: entry -#: hardware.xml:1273 +#: hardware.xml:1316 #, no-c-format msgid "iMac G5" msgstr "" #. Tag: entry -#: hardware.xml:1276 +#: hardware.xml:1319 #, no-c-format msgid "iBook, iBook SE, iBook Dual USB" msgstr "" #. Tag: entry -#: hardware.xml:1279 +#: hardware.xml:1322 #, no-c-format msgid "iBook2" msgstr "" #. Tag: entry -#: hardware.xml:1282 +#: hardware.xml:1325 #, no-c-format msgid "iBook G4" msgstr "" #. Tag: entry -#: hardware.xml:1285 +#: hardware.xml:1328 #, no-c-format msgid "Power Macintosh Blue and White (B&W) G3" msgstr "" #. Tag: entry -#: hardware.xml:1288 +#: hardware.xml:1331 #, no-c-format msgid "Power Macintosh G4 PCI, AGP, Cube" msgstr "" #. Tag: entry -#: hardware.xml:1291 +#: hardware.xml:1334 #, no-c-format msgid "Power Macintosh G4 Gigabit Ethernet" msgstr "" #. Tag: entry -#: hardware.xml:1294 +#: hardware.xml:1337 #, no-c-format msgid "Power Macintosh G4 Digital Audio, Quicksilver" msgstr "" #. Tag: entry -#: hardware.xml:1297 +#: hardware.xml:1340 #, no-c-format msgid "Power Macintosh G5" msgstr "" #. Tag: entry -#: hardware.xml:1300 +#: hardware.xml:1343 #, no-c-format msgid "PowerBook G3 FireWire Pismo (2000)" msgstr "" #. Tag: entry -#: hardware.xml:1303 +#: hardware.xml:1346 #, no-c-format msgid "PowerBook G3 Lombard (1999)" msgstr "" #. Tag: entry -#: hardware.xml:1306 +#: hardware.xml:1349 #, no-c-format msgid "PowerBook G4 Titanium" msgstr "" #. Tag: entry -#: hardware.xml:1309 +#: hardware.xml:1352 #, no-c-format msgid "PowerBook G4 Aluminum" msgstr "" #. Tag: entry -#: hardware.xml:1312 +#: hardware.xml:1355 #, no-c-format msgid "Xserve G5" msgstr "" #. Tag: entry -#: hardware.xml:1315 +#: hardware.xml:1358 #, no-c-format msgid "Performa 4400, 54xx, 5500" msgstr "" #. Tag: entry -#: hardware.xml:1316 hardware.xml:1319 hardware.xml:1322 hardware.xml:1325 hardware.xml:1328 hardware.xml:1331 hardware.xml:1334 hardware.xml:1337 hardware.xml:1340 hardware.xml:1343 hardware.xml:1346 hardware.xml:1349 hardware.xml:1355 hardware.xml:1358 hardware.xml:1364 hardware.xml:1370 hardware.xml:1376 +#: hardware.xml:1359 hardware.xml:1362 hardware.xml:1365 hardware.xml:1368 hardware.xml:1371 hardware.xml:1374 hardware.xml:1377 hardware.xml:1380 hardware.xml:1383 hardware.xml:1386 hardware.xml:1389 hardware.xml:1392 hardware.xml:1398 hardware.xml:1401 hardware.xml:1407 hardware.xml:1413 hardware.xml:1419 #, no-c-format msgid "OldWorld" msgstr "" #. Tag: entry -#: hardware.xml:1318 +#: hardware.xml:1361 #, no-c-format msgid "Performa 6360, 6400, 6500" msgstr "" #. Tag: entry -#: hardware.xml:1321 +#: hardware.xml:1364 #, no-c-format msgid "Power Macintosh 4400, 5400" msgstr "" #. Tag: entry -#: hardware.xml:1324 +#: hardware.xml:1367 #, no-c-format msgid "Power Macintosh 7200, 7300, 7500, 7600" msgstr "" #. Tag: entry -#: hardware.xml:1327 +#: hardware.xml:1370 #, no-c-format msgid "Power Macintosh 8200, 8500, 8600" msgstr "" #. Tag: entry -#: hardware.xml:1330 +#: hardware.xml:1373 #, no-c-format msgid "Power Macintosh 9500, 9600" msgstr "" #. Tag: entry -#: hardware.xml:1333 +#: hardware.xml:1376 #, no-c-format msgid "Power Macintosh (Beige) G3 Minitower" msgstr "" #. Tag: entry -#: hardware.xml:1336 +#: hardware.xml:1379 #, no-c-format msgid "Power Macintosh (Beige) Desktop, All-in-One" msgstr "" #. Tag: entry -#: hardware.xml:1339 +#: hardware.xml:1382 #, no-c-format msgid "PowerBook 2400, 3400, 3500" msgstr "" #. Tag: entry -#: hardware.xml:1342 +#: hardware.xml:1385 #, no-c-format msgid "PowerBook G3 Wallstreet (1998)" msgstr "" #. Tag: entry -#: hardware.xml:1345 +#: hardware.xml:1388 #, no-c-format msgid "Twentieth Anniversary Macintosh" msgstr "" #. Tag: entry -#: hardware.xml:1348 +#: hardware.xml:1391 #, no-c-format msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" msgstr "" #. Tag: entry -#: hardware.xml:1353 +#: hardware.xml:1396 #, no-c-format msgid "Power Computing" msgstr "" #. Tag: entry -#: hardware.xml:1354 +#: hardware.xml:1397 #, no-c-format msgid "PowerBase, PowerTower / Pro, PowerWave" msgstr "" #. Tag: entry -#: hardware.xml:1357 +#: hardware.xml:1400 #, no-c-format msgid "PowerCenter / Pro, PowerCurve" msgstr "" #. Tag: entry -#: hardware.xml:1362 +#: hardware.xml:1405 #, no-c-format msgid "UMAX" msgstr "" #. Tag: entry -#: hardware.xml:1363 +#: hardware.xml:1406 #, no-c-format msgid "C500, C600, J700, S900" msgstr "" #. Tag: entry -#: hardware.xml:1368 +#: hardware.xml:1411 #, no-c-format msgid "<entry>APS</entry>" msgstr "" #. Tag: entry -#: hardware.xml:1369 +#: hardware.xml:1412 #, no-c-format msgid "APS Tech M*Power 604e/2000" msgstr "" #. Tag: entry -#: hardware.xml:1374 hardware.xml:1400 +#: hardware.xml:1417 hardware.xml:1443 #, no-c-format msgid "Motorola" msgstr "" #. Tag: entry -#: hardware.xml:1375 +#: hardware.xml:1418 #, no-c-format msgid "Starmax 3000, 4000, 5000, 5500" msgstr "" #. Tag: title -#: hardware.xml:1384 +#: hardware.xml:1427 #, no-c-format msgid "PReP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1401 +#: hardware.xml:1444 #, no-c-format msgid "Firepower, PowerStack Series E, PowerStack II" msgstr "" #. Tag: entry -#: hardware.xml:1403 +#: hardware.xml:1446 #, no-c-format msgid "MPC 7xx, 8xx" msgstr "" #. Tag: entry -#: hardware.xml:1405 +#: hardware.xml:1448 #, no-c-format msgid "MTX, MTX+" msgstr "" #. Tag: entry -#: hardware.xml:1407 +#: hardware.xml:1450 #, no-c-format msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" msgstr "" #. Tag: entry -#: hardware.xml:1409 +#: hardware.xml:1452 #, no-c-format msgid "MCP(N)750" msgstr "" #. Tag: entry -#: hardware.xml:1413 hardware.xml:1444 +#: hardware.xml:1456 hardware.xml:1487 #, no-c-format msgid "IBM RS/6000" msgstr "" #. Tag: entry -#: hardware.xml:1414 +#: hardware.xml:1457 #, no-c-format msgid "40P, 43P" msgstr "" #. Tag: entry -#: hardware.xml:1416 +#: hardware.xml:1459 #, no-c-format msgid "Power 830/850/860 (6070, 6050)" msgstr "" #. Tag: entry -#: hardware.xml:1418 +#: hardware.xml:1461 #, no-c-format msgid "6030, 7025, 7043" msgstr "" #. Tag: entry -#: hardware.xml:1420 +#: hardware.xml:1463 #, no-c-format msgid "p640" msgstr "" #. Tag: title -#: hardware.xml:1428 +#: hardware.xml:1471 #, no-c-format msgid "CHRP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1445 +#: hardware.xml:1488 #, no-c-format msgid "B50, 43P-150, 44P" msgstr "" #. Tag: entry -#: hardware.xml:1448 +#: hardware.xml:1491 #, no-c-format msgid "Genesi" msgstr "" #. Tag: entry -#: hardware.xml:1449 +#: hardware.xml:1492 #, no-c-format msgid "Pegasos I, Pegasos II" msgstr "" #. Tag: title -#: hardware.xml:1457 +#: hardware.xml:1500 #, no-c-format msgid "APUS subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:1473 +#: hardware.xml:1516 #, no-c-format msgid "Amiga Power-UP Systems (APUS)" msgstr "" #. Tag: entry -#: hardware.xml:1474 +#: hardware.xml:1517 #, no-c-format msgid "A1200, A3000, A4000" msgstr "" #. Tag: title -#: hardware.xml:1482 +#: hardware.xml:1525 #, no-c-format msgid "Nubus PowerMac subarchitecture (unsupported)" msgstr "" #. Tag: para -#: hardware.xml:1484 +#: hardware.xml:1527 #, 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>." msgstr "" #. Tag: title -#: hardware.xml:1521 +#: hardware.xml:1564 #, no-c-format msgid "Non-PowerPC Macs" msgstr "" #. Tag: para -#: hardware.xml:1523 +#: hardware.xml:1566 #, 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." msgstr "" #. Tag: para -#: hardware.xml:1532 +#: hardware.xml:1575 #, 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." msgstr "" #. Tag: para -#: hardware.xml:1540 +#: hardware.xml:1583 #, 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)." msgstr "" #. Tag: title -#: hardware.xml:1556 +#: hardware.xml:1599 #, no-c-format msgid "S/390 and zSeries machine types" msgstr "" #. Tag: para -#: hardware.xml:1557 +#: hardware.xml:1600 #, no-c-format -msgid "Complete information regarding supported S/390 and zSeries machines can be found in IBM's Redbook <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> in chapter 2.1 or at the <ulink url=\"http://oss.software.ibm.com/developerworks/opensource/linux390/documentation-2.4.shtml\">technical details web page</ulink> at <ulink url=\"http://oss.software.ibm.com/developerworks/opensource/linux390/index.shtml\">developerWorks</ulink>. In short, G5, Multiprise 3000, G6 and all zSeries are fully supported; Multiprise 2000, G3 and G4 machines are supported with IEEE floating point emulation and thus degraded performance." +msgid "Complete information regarding supported S/390 and zSeries machines can be found in IBM's Redbook <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: Distributions</ulink> in chapter 2.1 or at the <ulink url=\"http://www-128.ibm.com/developerworks/linux/linux390/index.html\">zSeries page at the developerWorks</ulink>. In short, G5, Multiprise 3000, G6 and all zSeries are fully supported; Multiprise 2000, G3 and G4 machines are supported with IEEE floating point emulation and thus degraded performance." msgstr "" #. Tag: para -#: hardware.xml:1580 +#: hardware.xml:1623 #, no-c-format msgid "Currently the <emphasis>&architecture;</emphasis> port supports several types of Sparc systems. The most common identifiers for Sparc systems are sun4, sun4c, sun4m, sun4d and sun4u. Currently we do not support very old sun4 hardware. However, the other systems are supported. Sun4d has been tested the least of these, so expect possible problems with regard to the kernel stability. Sun4c and Sun4m, the most common of the older Sparc hardware, includes such systems as SparcStation 1, 1+, IPC, IPX and the SparcStation LX, 5, 10, and 20, respectively. The UltraSPARC class systems fall under the sun4u identifier, and are supported using the sun4u set of install images. Some systems that fall under these supported identifiers are known to not be supported. Known unsupported systems are the AP1000 multicomputer and the Tadpole Sparcbook 1. See the <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARCProcessors FAQ</ulink> for complete information." msgstr "" #. Tag: title -#: hardware.xml:1600 +#: hardware.xml:1643 #, no-c-format msgid "Memory Configuration" msgstr "" #. Tag: para -#: hardware.xml:1601 +#: hardware.xml:1644 #, no-c-format msgid "Some older Sun workstations, notably the Sun IPX and Sun IPC have memory banks located at fixed locations in physical memory. Thus if the banks are not filled gaps will exist in the physical memory space. The Linux installation requires a contiguous memory block into which to load the kernel and the initial RAMdisk. If this is not available a <quote>Data Access Exception</quote> will result." msgstr "" #. Tag: para -#: hardware.xml:1610 +#: hardware.xml:1653 #, no-c-format msgid "Thus you must configure the memory so that the lowest memory block is contiguous for at least 8Mb. In the IPX and IPC cited above, memory banks are mapped in at 16Mb boundaries. In effect this means that you must have a sufficiently large SIMM in bank zero to hold the kernel and RAMdisk. In this case 4Mb is <emphasis>not</emphasis> sufficient." msgstr "" #. Tag: para -#: hardware.xml:1618 +#: hardware.xml:1661 #, no-c-format msgid "Example: In a Sun IPX you have a 16Mb SIMM and a 4Mb SIMM. There are four SIMM banks (0,1,2,3). [Bank zero is that furthest away from the SBUS connectors]. You must therefore install the 16Mb SIMM in bank 0; it is then recommended to install the 4Mb SIMM in bank 2." msgstr "" #. Tag: title -#: hardware.xml:1629 +#: hardware.xml:1672 #, no-c-format msgid "Graphics Configuration" msgstr "" #. Tag: para -#: hardware.xml:1630 +#: hardware.xml:1673 #, no-c-format msgid "Especially in the case of older Sun workstations, it is very common for there to be an onboard framebuffer which has been superseded (for example the bwtwo on a sun IPC), and an SBUS card containing a later probably accelerated buffer is then plugged in to an SBUS slot. Under Solaris/SunOS this causes no problems because both cards are initialized." msgstr "" #. Tag: para -#: hardware.xml:1639 +#: hardware.xml:1682 #, no-c-format msgid "However with Linux this can cause a problem, in that the boot PROM monitor may display its output on this additional card; however the linux kernel boot messages may then be directed to the original on board framebuffer, leaving <emphasis>no</emphasis> error messages on the screen, with the machine apparently stuck loading the RAMdisk." msgstr "" #. Tag: para -#: hardware.xml:1647 +#: hardware.xml:1690 #, no-c-format msgid "To avoid this problem, connect the monitor (if required) to the video card in the lowest numbered SBUS slot (on motherboard card counts as below external slots). Alternatively it is possible to use a serial console." msgstr "" #. Tag: title -#: hardware.xml:1659 +#: hardware.xml:1702 #, no-c-format msgid "Graphics Card" msgstr "" #. Tag: para -#: hardware.xml:1660 +#: hardware.xml:1703 #, no-c-format msgid "You should be using a VGA-compatible display interface for the console terminal. Nearly every modern display card is compatible with VGA. Ancient standards such CGA, MDA, or HGA should also work, assuming you do not require X11 support. Note that X11 is not used during the installation process described in this document." msgstr "" #. Tag: para -#: hardware.xml:1668 +#: hardware.xml:1711 #, no-c-format msgid "Debian's support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. Most AGP, PCI and PCIe video cards work under X.Org. Details on supported graphics buses, cards, monitors, and pointing devices can be found at <ulink url=\"&url-xorg;\"></ulink>. Debian &release; ships with X.Org version &x11ver;." msgstr "" #. Tag: para -#: hardware.xml:1677 +#: hardware.xml:1720 #, no-c-format msgid "The X.Org X11 window system is only supported on the SGI Indy and the O2. The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available." msgstr "" #. Tag: para -#: hardware.xml:1686 +#: hardware.xml:1729 #, no-c-format msgid "The X.Org X11 window system is supported on some DECstation models. The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI slots and support VGA emulation or Linux framebuffer on a selected range of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility listing</ulink> for Broadcom evaluation boards is available." msgstr "" #. Tag: title -#: hardware.xml:1697 +#: hardware.xml:1740 #, no-c-format msgid "Laptops" msgstr "" #. Tag: para -#: hardware.xml:1698 +#: hardware.xml:1741 #, no-c-format msgid "Laptops are also supported. Laptops are often specialized or contain proprietary hardware. To see if your particular laptop works well with GNU/Linux, see the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>" msgstr "" #. Tag: title -#: hardware.xml:1709 hardware.xml:1731 hardware.xml:1751 hardware.xml:1774 +#: hardware.xml:1752 hardware.xml:1774 hardware.xml:1794 hardware.xml:1817 #, no-c-format msgid "Multiple Processors" msgstr "" #. Tag: para -#: hardware.xml:1710 +#: hardware.xml:1753 #, no-c-format msgid "Multi-processor support — also called <quote>symmetric multi-processing</quote> or SMP — is available for this architecture. The standard Debian &release; kernel image was compiled with SMP support. This should not prevent installation, since the SMP kernel should boot on non-SMP systems; the kernel will simply cause a bit more overhead." msgstr "" #. Tag: para -#: hardware.xml:1718 +#: hardware.xml:1761 #, no-c-format msgid "In order to optimize the kernel for single CPU systems, you'll have to replace the standard Debian kernel. You can find a discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way you disable SMP is to deselect <quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> section of the kernel config." msgstr "" #. Tag: para -#: hardware.xml:1733 +#: hardware.xml:1776 #, no-c-format msgid "Multi-processor support — also called <quote>symmetric multi-processing</quote> or SMP — is available for this architecture. The standard Debian &release; kernel image was 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:1742 +#: hardware.xml:1785 #, no-c-format msgid "The 486 flavour of the Debian kernel image packages for &arch-title; is not compiled with SMP support." msgstr "" #. Tag: para -#: hardware.xml:1752 +#: hardware.xml:1795 #, no-c-format msgid "Multi-processor support — also called <quote>symmetric multi-processing</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 the first CPU." msgstr "" #. Tag: para -#: hardware.xml:1761 +#: hardware.xml:1804 #, no-c-format msgid "In order to take advantage of multiple processors, you'll have to replace the standard Debian kernel. 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." msgstr "" #. Tag: para -#: hardware.xml:1775 +#: hardware.xml:1818 #, no-c-format msgid "Multi-processor support — also called <quote>symmetric multi-processing</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:1785 +#: hardware.xml:1828 #, 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. You can also build your own customized kernel to support SMP. 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." msgstr "" #. Tag: title -#: hardware.xml:1806 +#: hardware.xml:1849 #, no-c-format msgid "Installation Media" msgstr "" #. Tag: para -#: hardware.xml:1808 +#: hardware.xml:1851 #, no-c-format msgid "This section will help you determine which different media types you can use to install Debian. For example, if you have a floppy disk drive on your machine, it can be used to install Debian. There is a whole chapter devoted media, <xref linkend=\"install-methods\"/>, which lists the advantages and disadvantages of each media type. You may want to refer back to this page once you reach that section." msgstr "" #. Tag: title -#: hardware.xml:1819 +#: hardware.xml:1862 #, no-c-format msgid "Floppies" msgstr "" #. Tag: para -#: hardware.xml:1820 +#: hardware.xml:1863 #, no-c-format msgid "In some cases, you'll have to do your first boot from floppy disks. Generally, all you will need is a high-density (1440 kilobytes) 3.5 inch floppy drive." msgstr "" #. Tag: para -#: hardware.xml:1826 +#: hardware.xml:1869 #, no-c-format msgid "For CHRP, floppy support is currently broken." msgstr "" #. Tag: title -#: hardware.xml:1833 +#: hardware.xml:1876 #, no-c-format msgid "CD-ROM/DVD-ROM" msgstr "" #. Tag: para -#: hardware.xml:1835 +#: hardware.xml:1878 #, no-c-format msgid "Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both CD-ROMs and DVD-ROMs, because both technologies are really the same from the operating system's point of view, except for some very old nonstandard CD-ROM drives which are neither SCSI nor IDE/ATAPI." msgstr "" #. Tag: para -#: hardware.xml:1842 +#: hardware.xml:1885 #, no-c-format msgid "CD-ROM based installation is supported for some architectures. On machines which support bootable CD-ROMs, you should be able to do a completely <phrase arch=\"not-s390\">floppy-less</phrase> <phrase arch=\"s390\">tape-less</phrase> installation. Even if your system doesn't support booting from a CD-ROM, you can use the CD-ROM in conjunction with the other techniques to install your system, once you've booted up by other means; see <xref linkend=\"boot-installer\"/>." msgstr "" #. Tag: para -#: hardware.xml:1854 +#: hardware.xml:1897 #, no-c-format msgid "Both SCSI and IDE/ATAPI CD-ROMs are supported. In addition, all non-standard CD interfaces supported by Linux are supported by the boot disks (such as Mitsumi and Matsushita drives). However, these models might require special boot parameters or other massaging to get them to work, and booting off these non-standard interfaces is unlikely. The <ulink url=\"&url-cd-howto;\">Linux CD-ROM HOWTO</ulink> contains in-depth information on using CD-ROMs with Linux." msgstr "" #. Tag: para -#: hardware.xml:1864 +#: hardware.xml:1907 #, no-c-format msgid "USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers." msgstr "" #. Tag: para -#: hardware.xml:1869 +#: hardware.xml:1912 #, no-c-format msgid "Both SCSI and IDE/ATAPI CD-ROMs are supported on &arch-title;, as long as the controller is supported by the SRM console. This rules out many add-on controller cards, but most integrated IDE and SCSI chips and controller cards that were provided by the manufacturer can be expected to work. To find out whether your device is supported from the SRM console, see the <ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink>." msgstr "" #. Tag: para -#: hardware.xml:1878 +#: hardware.xml:1921 #, no-c-format msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines. On RiscPCs, SCSI CD-ROMs are also supported." msgstr "" #. Tag: para -#: hardware.xml:1883 +#: hardware.xml:1926 #, no-c-format msgid "On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. To start the install, simply choose the <quote>System installation</quote> entry in the firmware. The Broadcom BCM91250A supports standard IDE devices, including CD-ROM drives, but CD images for this platform are currently not provided because the firmware doesn't recognize CD drives. In order to install Debian on an Broadcom BCM91480B evaluation board, you need an PCI IDE, SATA or SCSI card." msgstr "" #. Tag: para -#: hardware.xml:1898 +#: hardware.xml:1941 #, no-c-format msgid "On DECstations, 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." msgstr "" #. Tag: para -#: hardware.xml:1907 +#: hardware.xml:1950 #, no-c-format msgid "CD 1 contains the installer for the r3k-kn02 subarchitecture (the R3000-based DECstations 5000/1xx and 5000/240 as well as the R3000-based Personal DECstation models), CD 2 the installer for the r4k-kn04 subarchitecture (the R4x00-based DECstations 5000/150 and 5000/260 as well as the Personal DECstation 5000/50)." msgstr "" #. Tag: para -#: hardware.xml:1916 +#: hardware.xml:1959 #, no-c-format msgid "To boot from CD, issue the command <userinput>boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable></userinput> on the firmware prompt, where <replaceable>#</replaceable> is the number of the TurboChannel device from which to boot (3 on most DECstations) and <replaceable>id</replaceable> is the SCSI ID of the CD-ROM drive. If you need to pass additional parameters, they can optionally be appended with the following syntax:" msgstr "" #. Tag: userinput -#: hardware.xml:1928 +#: hardware.xml:1971 #, no-c-format msgid "boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> param1=value1 param2=value2 ..." msgstr "" #. Tag: title -#: hardware.xml:1935 +#: hardware.xml:1978 #, no-c-format msgid "Hard Disk" msgstr "" #. Tag: para -#: hardware.xml:1937 +#: hardware.xml:1980 #, no-c-format msgid "Booting the installation system directly from a hard disk is another option for many architectures. This will require some other operating system to load the installer onto the hard disk." msgstr "" #. Tag: para -#: hardware.xml:1943 +#: hardware.xml:1986 #, no-c-format msgid "In fact, installation from your local disk is the preferred installation technique for most &architecture; machines." msgstr "" #. Tag: para -#: hardware.xml:1948 +#: hardware.xml:1991 #, no-c-format msgid "Although the &arch-title; does not allow booting from SunOS (Solaris), you can install from a SunOS partition (UFS slices)." msgstr "" #. Tag: title -#: hardware.xml:1956 +#: hardware.xml:1999 #, no-c-format msgid "USB Memory Stick" msgstr "" #. Tag: para -#: hardware.xml:1958 +#: hardware.xml:2001 #, no-c-format msgid "Many Debian boxes need their floppy and/or CD-ROM drives only for setting up the system and for rescue purposes. If you operate some servers, you will probably already have thought about omitting those drives and using an USB memory stick for installing and (when necessary) for recovering the system. This is also useful for small systems which have no room for unnecessary drives." msgstr "" #. Tag: title -#: hardware.xml:1970 +#: hardware.xml:2013 #, no-c-format msgid "Network" msgstr "" #. Tag: para -#: hardware.xml:1972 +#: hardware.xml:2015 #, no-c-format msgid "You can also <emphasis>boot</emphasis> your system over the network. <phrase arch=\"mips\">This is the preferred installation technique for Mips.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:1978 +#: hardware.xml:2021 #, no-c-format msgid "Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option." msgstr "" #. Tag: para -#: hardware.xml:1983 +#: hardware.xml:2026 #, no-c-format msgid "After the operating system kernel is installed, you can install the rest of your system via any sort of network connection (including PPP after installation of the base system), via FTP or HTTP." msgstr "" #. Tag: title -#: hardware.xml:1992 +#: hardware.xml:2035 #, no-c-format msgid "Un*x or GNU system" msgstr "" #. Tag: para -#: hardware.xml:1994 +#: hardware.xml:2037 #, no-c-format msgid "If you are running another Unix-like system, you could use it to install &debian; without using the &d-i; described in the rest of the manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the <xref linkend=\"linux-upgrade\"/>." msgstr "" #. Tag: title -#: hardware.xml:2006 +#: hardware.xml:2049 #, no-c-format msgid "Supported Storage Systems" msgstr "" #. Tag: para -#: hardware.xml:2008 +#: hardware.xml:2051 #, no-c-format msgid "The Debian boot disks contain a kernel which is built to maximize the number of systems it runs on. Unfortunately, this makes for a larger kernel, which includes many drivers that won't be used for your machine (see <xref linkend=\"kernel-baking\"/> to learn how to build your own kernel). Support for the widest possible range of devices is desirable in general, to ensure that Debian can be installed on the widest array of hardware." msgstr "" #. Tag: para -#: hardware.xml:2018 +#: hardware.xml:2061 #, no-c-format msgid "Generally, the Debian installation system includes support for floppies, IDE drives, IDE floppies, parallel port IDE devices, SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS." msgstr "" #. Tag: para -#: hardware.xml:2025 +#: hardware.xml:2068 #, no-c-format msgid "Disk interfaces that emulate the <quote>AT</quote> hard disk interface — often called MFM, RLL, IDE, or ATA — are supported. Very old 8–bit hard disk controllers used in the IBM XT computer are supported only as a module. SCSI disk controllers from many different manufacturers are supported. See the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> for more details." msgstr "" #. Tag: para -#: hardware.xml:2035 +#: hardware.xml:2078 #, no-c-format msgid "Pretty much all storage systems supported by the Linux kernel are supported by the Debian installation system. Note that the current Linux kernel does not support floppies on the Macintosh at all, and the Debian installation system doesn't support floppies for Amigas. Also supported on the Atari is the Macintosh HFS system, and AFFS as a module. Macs support the Atari (FAT) file system. Amigas support the FAT file system, and HFS as a module." msgstr "" #. Tag: para -#: hardware.xml:2045 +#: hardware.xml:2088 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. The following SCSI drivers are supported in the default kernel: <itemizedlist> <listitem><para> Sparc ESP </para></listitem> <listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></listitem> </itemizedlist> IDE systems (such as the UltraSPARC 5) are also supported. See <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors FAQ</ulink> for more information on SPARC hardware supported by the Linux kernel." msgstr "" #. Tag: para -#: hardware.xml:2078 +#: hardware.xml:2121 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This includes both SCSI and IDE disks. Note, however, that on many systems, the SRM console is unable to boot from IDE drives, and the Jensen is unable to boot from floppies. (see <ulink url=\"&url-jensen-howto;\"></ulink> for more information on booting the Jensen)" msgstr "" #. Tag: para -#: hardware.xml:2087 +#: hardware.xml:2130 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support floppies on CHRP systems at all." msgstr "" #. Tag: para -#: hardware.xml:2093 +#: hardware.xml:2136 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support the floppy drive." msgstr "" #. Tag: para -#: hardware.xml:2099 +#: hardware.xml:2142 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system." msgstr "" #. Tag: para -#: hardware.xml:2104 +#: hardware.xml:2147 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This means that FBA and ECKD DASDs are supported with the old Linux disk layout (ldl) and the new common S/390 disk layout (cdl)." msgstr "" #. Tag: title -#: hardware.xml:2121 +#: hardware.xml:2164 #, no-c-format msgid "Peripherals and Other Hardware" msgstr "" #. Tag: para -#: hardware.xml:2122 +#: hardware.xml:2165 #, no-c-format msgid "Linux supports a large variety of hardware devices such as mice, printers, scanners, PCMCIA and USB devices. However, most of these devices are not required while installing the system." msgstr "" #. Tag: para -#: hardware.xml:2128 +#: hardware.xml:2171 #, no-c-format msgid "USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend=\"usb-keyboard-config\"/>)." msgstr "" #. Tag: para -#: hardware.xml:2134 +#: hardware.xml:2177 #, no-c-format msgid "Again, see the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> to determine whether your specific hardware is supported by Linux." msgstr "" #. Tag: para -#: hardware.xml:2140 +#: hardware.xml:2183 #, no-c-format msgid "Package installations from XPRAM and tape are not supported by this system. All packages that you want to install need to be available on a DASD or over the network using NFS, HTTP or FTP." msgstr "" #. Tag: para -#: hardware.xml:2146 +#: hardware.xml:2189 #, no-c-format msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation board features four 64 bit PCI slots." msgstr "" #. Tag: para -#: hardware.xml:2152 +#: hardware.xml:2195 #, no-c-format msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation board features four 64 bit PCI slots. The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot." msgstr "" #. Tag: title -#: hardware.xml:2162 +#: hardware.xml:2205 #, no-c-format msgid "Purchasing Hardware Specifically for GNU/Linux" msgstr "" #. Tag: para -#: hardware.xml:2164 +#: hardware.xml:2207 #, no-c-format msgid "There are several vendors, who ship systems with Debian or other distributions of GNU/Linux <ulink url=\"&url-pre-installed;\">pre-installed</ulink>. You might pay more for the privilege, but it does buy a level of peace of mind, since you can be sure that the hardware is well-supported by GNU/Linux." msgstr "" #. Tag: para -#: hardware.xml:2172 +#: hardware.xml:2215 #, no-c-format msgid "Unfortunately, it's quite rare to find any vendor shipping new &arch-title; machines at all." msgstr "" #. Tag: para -#: hardware.xml:2177 +#: hardware.xml:2220 #, no-c-format msgid "If you do have to buy a machine with Windows bundled, carefully read the software license that comes with Windows; you may be able to reject the license and obtain a rebate from your vendor. Searching the Internet for <quote>windows refund</quote> may get you some useful information to help with that." msgstr "" #. Tag: para -#: hardware.xml:2185 +#: hardware.xml:2228 #, no-c-format msgid "Whether or not you are purchasing a system with Linux bundled, or even a used system, it is still important to check that your hardware is supported by the Linux kernel. Check if your hardware is listed in the references found above. Let your salesperson (if any) know that you're shopping for a Linux system. Support Linux-friendly hardware vendors." msgstr "" #. Tag: title -#: hardware.xml:2196 +#: hardware.xml:2239 #, no-c-format msgid "Avoid Proprietary or Closed Hardware" msgstr "" #. Tag: para -#: hardware.xml:2197 +#: hardware.xml:2240 #, no-c-format msgid "Some hardware manufacturers simply won't tell us how to write drivers for their hardware. Others won't allow us access to the documentation without a non-disclosure agreement that would prevent us from releasing the Linux source code." msgstr "" #. Tag: para -#: hardware.xml:2204 +#: hardware.xml:2247 #, no-c-format msgid "Another example is the proprietary hardware in the older Macintosh line. In fact, no specifications or documentation have ever been released for any Macintosh hardware, most notably the ADB controller (used by the mouse and keyboard), the floppy controller, and all acceleration and CLUT manipulation of the video hardware (though we do now support CLUT manipulation on nearly all internal video chips). In a nutshell, this explains why the Macintosh Linux port lags behind other Linux ports." msgstr "" #. Tag: para -#: hardware.xml:2215 +#: hardware.xml:2258 #, no-c-format msgid "Since we haven't been granted access to the documentation on these devices, they simply won't work under Linux. You can help by asking the manufacturers of such hardware to release the documentation. If enough people ask, they will realize that the free software community is an important market." msgstr "" #. Tag: title -#: hardware.xml:2227 +#: hardware.xml:2270 #, no-c-format msgid "Windows-specific Hardware" msgstr "" #. Tag: para -#: hardware.xml:2228 +#: hardware.xml:2271 #, no-c-format msgid "A disturbing trend is the proliferation of Windows-specific modems and printers. In some cases these are specially designed to be operated by the Microsoft Windows operating system and bear the legend <quote>WinModem</quote> or <quote>Made especially for Windows-based computers</quote>. This is generally done by removing the embedded processors of the hardware and shifting the work they do over to a Windows driver that is run by your computer's main CPU. This strategy makes the hardware less expensive, but the savings are often <emphasis>not</emphasis> passed on to the user and this hardware may even be more expensive than equivalent devices that retain their embedded intelligence." msgstr "" #. Tag: para -#: hardware.xml:2241 +#: hardware.xml:2284 #, no-c-format msgid "You should avoid Windows-specific hardware for two reasons. The first is that the manufacturers do not generally make the resources available to write a Linux driver. Generally, the hardware and software interface to the device is proprietary, and documentation is not available without a non-disclosure agreement, if it is available at all. This precludes its being used for free software, since free software writers disclose the source code of their programs. The second reason is that when devices like these have had their embedded processors removed, the operating system must perform the work of the embedded processors, often at <emphasis>real-time</emphasis> priority, and thus the CPU is not available to run your programs while it is driving these devices. Since the typical Windows user does not multi-process as intensively as a Linux user, the manufacturers hope that the Windows user simply won't notice the burden this hardware places on their CPU. However, any multi-processing operating system, even Windows 2000 or XP, suffers from degraded performance when peripheral manufacturers skimp on the embedded processing power of their hardware." msgstr "" #. Tag: para -#: hardware.xml:2262 +#: hardware.xml:2305 #, no-c-format msgid "You can help improve this situation by encouraging these manufacturers to release the documentation and other resources necessary for us to program their hardware, but the best strategy is simply to avoid this sort of hardware until it is listed as working in the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>." msgstr "" #. Tag: title -#: hardware.xml:2275 +#: hardware.xml:2318 #, no-c-format msgid "Fake or <quote>Virtual</quote> Parity RAM" msgstr "" #. Tag: para -#: hardware.xml:2276 +#: hardware.xml:2319 #, no-c-format msgid "If you ask for Parity RAM in a computer store, you'll probably get <emphasis>virtual parity</emphasis> memory modules instead of <emphasis>true parity</emphasis> ones. Virtual parity SIMMs can often (but not always) be distinguished because they only have one more chip than an equivalent non-parity SIMM, and that one extra chip is smaller than all the others. Virtual-parity SIMMs work exactly like non-parity memory. They can't tell you when you have a single-bit RAM error the way true-parity SIMMs do in a motherboard that implements parity. Don't ever pay more for a virtual-parity SIMM than a non-parity one. Do expect to pay a little more for true-parity SIMMs, because you are actually buying one extra bit of memory for every 8 bits." msgstr "" #. Tag: para -#: hardware.xml:2291 +#: hardware.xml:2334 #, no-c-format msgid "If you want complete information on &arch-title; RAM issues, and what is the best RAM to buy, see the <ulink url=\"&url-pc-hw-faq;\">PC Hardware FAQ</ulink>." msgstr "" #. Tag: para -#: hardware.xml:2297 +#: hardware.xml:2340 #, no-c-format msgid "Most, if not all, Alpha systems require true-parity RAM." msgstr "" #. Tag: title -#: hardware.xml:2312 +#: hardware.xml:2355 #, no-c-format msgid "Memory and Disk Space Requirements" msgstr "" #. Tag: para -#: hardware.xml:2314 +#: hardware.xml:2357 #, no-c-format msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space. For a minimal console-based system (all standard packages), 250MB is required. If you want to install a reasonable amount of software, including the X Window System, and some development programs and libraries, you'll need at least 400MB. For a more or less complete desktop system, you'll need a few gigabytes." msgstr "" #. Tag: para -#: hardware.xml:2323 +#: hardware.xml:2366 #, no-c-format msgid "On the Amiga the size of FastRAM is relevant towards the total memory requirements. Also, using Zorro cards with 16-bit RAM is not supported; you'll need 32-bit RAM. The <command>amiboot</command> program can be used to disable 16-bit RAM; see the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. Recent kernels should disable 16-bit RAM automatically." msgstr "" #. Tag: para -#: hardware.xml:2332 +#: hardware.xml:2375 #, no-c-format msgid "On the Atari, both ST-RAM and Fast RAM (TT-RAM) are used by Linux. Many users have reported problems running the kernel itself in Fast RAM, so the Atari bootstrap will place the kernel in ST-RAM. The minimum requirement for ST-RAM is 2 MB. You will need an additional 12 MB or more of TT-RAM." msgstr "" #. Tag: para -#: hardware.xml:2340 +#: hardware.xml:2383 #, no-c-format msgid "On the Macintosh, care should be taken on machines with RAM-based video (RBV). The RAM segment at physical address 0 is used as screen memory, making the default load position for the kernel unavailable. The alternate RAM segment used for kernel and RAMdisk must be at least 4 MB." msgstr "" #. Tag: emphasis -#: hardware.xml:2350 +#: hardware.xml:2393 #, no-c-format msgid "FIXME: is this still true?" msgstr "" #. Tag: title -#: hardware.xml:2361 +#: hardware.xml:2404 #, no-c-format msgid "Network Connectivity Hardware" msgstr "" #. Tag: para -#: hardware.xml:2363 +#: hardware.xml:2406 #, no-c-format msgid "Most PCI and many older ISA network cards are supported. Some network interface cards are not supported by most Debian installation disks, such as AX.25 cards and protocols; NI16510 EtherBlaster cards; Schneider & Koch G16 cards; and the Zenith Z-Note built-in network card. Microchannel (MCA) network cards are not supported by the standard installation system, but see <ulink url=\"&url-linux-mca;\">Linux on MCA</ulink> for some (old) instructions. FDDI networks are also not supported by the installation disks, both cards and protocols." msgstr "" #. Tag: para -#: hardware.xml:2382 +#: hardware.xml:2425 #, no-c-format msgid "As for ISDN, the D-channel protocol for the (old) German 1TR6 is not supported; Spellcaster BRI ISDN boards are also not supported by the &d-i;." msgstr "" #. Tag: para -#: hardware.xml:2390 +#: hardware.xml:2433 #, no-c-format msgid "Any network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module. Again, see <ulink url=\"&url-m68k-faq;\"></ulink> for complete details." msgstr "" #. Tag: para -#: hardware.xml:2399 +#: hardware.xml:2442 #, no-c-format msgid "The following network interface cards (NICs) are supported from the bootable kernel directly:" msgstr "" #. Tag: para -#: hardware.xml:2405 +#: hardware.xml:2448 #, no-c-format msgid "Sun LANCE" msgstr "" #. Tag: para -#: hardware.xml:2411 +#: hardware.xml:2454 #, no-c-format msgid "Sun Happy Meal" msgstr "" #. Tag: para -#: hardware.xml:2419 +#: hardware.xml:2462 #, no-c-format msgid "The following network interface cards are supported as modules. They can be enabled once the drivers are installed during the setup. However, due to the magic of OpenPROM, you still should be able to boot from these devices:" msgstr "" #. Tag: para -#: hardware.xml:2427 +#: hardware.xml:2470 #, no-c-format msgid "Sun BigMAC" msgstr "" #. Tag: para -#: hardware.xml:2433 +#: hardware.xml:2476 #, no-c-format msgid "Sun QuadEthernet" msgstr "" #. Tag: para -#: hardware.xml:2438 +#: hardware.xml:2481 #, no-c-format msgid "MyriCOM Gigabit Ethernet" msgstr "" #. Tag: para -#: hardware.xml:2445 hardware.xml:2451 hardware.xml:2457 hardware.xml:2463 hardware.xml:2469 +#: hardware.xml:2488 hardware.xml:2494 hardware.xml:2500 hardware.xml:2506 hardware.xml:2512 #, no-c-format msgid "Any network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module." msgstr "" #. Tag: para -#: hardware.xml:2475 +#: hardware.xml:2518 #, no-c-format msgid "Due to kernel limitations only the onboard network interfaces on DECstations are supported, TurboChannel option network cards currently do not work." msgstr "" #. Tag: para -#: hardware.xml:2481 +#: hardware.xml:2524 #, no-c-format msgid "Any network interface card (NIC) supported by the Linux kernel is also be supported by the boot disks. All network drivers are compiled as modules so you need to load one first during the initial network setup. The list of supported network devices is:" msgstr "" #. Tag: para -#: hardware.xml:2489 +#: hardware.xml:2532 #, no-c-format msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" msgstr "" #. Tag: para -#: hardware.xml:2494 +#: hardware.xml:2537 #, no-c-format msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" msgstr "" #. Tag: para -#: hardware.xml:2499 +#: hardware.xml:2542 #, no-c-format msgid "Inter-User Communication Vehicle (IUCV) — available for VM guests only" msgstr "" #. Tag: para -#: hardware.xml:2504 +#: hardware.xml:2547 #, no-c-format msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" msgstr "" #. Tag: para -#: hardware.xml:2513 +#: hardware.xml:2556 #, no-c-format msgid "The following network interface cards are supported directly by the boot disks on Netwinder and CATS machines:" msgstr "" #. Tag: para -#: hardware.xml:2519 +#: hardware.xml:2562 #, no-c-format msgid "PCI-based NE2000" msgstr "" #. Tag: para -#: hardware.xml:2525 +#: hardware.xml:2568 #, no-c-format msgid "DECchip Tulip" msgstr "" #. Tag: para -#: hardware.xml:2532 +#: hardware.xml:2575 #, no-c-format msgid "The following network interface cards are supported directly by the boot disks on RiscPCs:" msgstr "" #. Tag: para -#: hardware.xml:2538 +#: hardware.xml:2581 #, no-c-format msgid "Ether1" msgstr "" #. Tag: para -#: hardware.xml:2543 +#: hardware.xml:2586 #, no-c-format msgid "Ether3" msgstr "" #. Tag: para -#: hardware.xml:2548 +#: hardware.xml:2591 #, no-c-format msgid "EtherH" msgstr "" #. Tag: para -#: hardware.xml:2555 +#: hardware.xml:2598 #, no-c-format msgid "If your card is mentioned in the lists above, the complete installation can be carried out from the network with no need for CD-ROMs or floppy disks." msgstr "" #. Tag: para -#: hardware.xml:2561 +#: hardware.xml:2604 #, no-c-format msgid "Any other network interface card (NIC) supported by the Linux kernel should also be supported by the boot disks. You may need to load your network driver as a module; this means that you will have to install the operating system kernel and modules using some other media." msgstr "" diff --git a/po/pot/install-methods.pot b/po/pot/install-methods.pot index 091205a38..4bd915dbd 100644 --- a/po/pot/install-methods.pot +++ b/po/pot/install-methods.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-08-16 18:10+0000\n" +"POT-Creation-Date: 2006-08-18 17:32+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -862,52 +862,29 @@ msgstr "" #. Tag: para #: install-methods.xml:1157 #, no-c-format -msgid "To setup RARP, you need to know the Ethernet address (a.k.a. the MAC address) of the client computers to be installed. If you don't know this information, you can <phrase arch=\"sparc\"> pick it off the initial OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the command <userinput>/sbin/ifconfig eth0</userinput>." +msgid "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC address) of the client computers to be installed. If you don't know this information, you can <phrase arch=\"sparc\"> pick it off the initial OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the command <userinput>/sbin/ifconfig eth0</userinput>." msgstr "" #. Tag: para #: install-methods.xml:1169 #, no-c-format -msgid "" - "On a RARP server system using a Linux 2.2.x kernel, you need to populate the kernel's RARP table. To do this, run the following commands: <informalexample><screen>\n" - "# <userinput>/sbin/rarp -s\n" - "<replaceable>client-hostname</replaceable>\n" - "<replaceable>client-enet-addr</replaceable></userinput>\n" - "\n" - "# <userinput>/usr/sbin/arp -s\n" - "<replaceable>client-ip</replaceable>\n" - "<replaceable>client-enet-addr</replaceable></userinput>\n" - "</screen></informalexample> If you get <informalexample><screen>\n" - "SIOCSRARP: Invalid argument\n" - "</screen></informalexample> you probably need to load the RARP kernel module or else recompile the kernel to support RARP. Try <userinput>modprobe rarp</userinput> and then try the <command>rarp</command> command again." -msgstr "" - -#. Tag: para -#: install-methods.xml:1185 -#, no-c-format -msgid "On a RARP server system using a Linux 2.4.x kernel, there is no RARP module, and you should instead use the <command>rarpd</command> program. The procedure is similar to that used under SunOS in the following paragraph." -msgstr "" - -#. Tag: para -#: install-methods.xml:1193 -#, no-c-format -msgid "Under SunOS, you need to ensure that the Ethernet hardware address for the client is listed in the <quote>ethers</quote> database (either in the <filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start the RARP daemon. In SunOS 4, issue the command (as root): <userinput>/usr/etc/rarpd -a</userinput>; in SunOS 5, use <userinput>/usr/sbin/rarpd -a</userinput>." +msgid "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, you use the <command>rarpd</command> program. You need to ensure that the Ethernet hardware address for the client is listed in the <quote>ethers</quote> database (either in the <filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start the RARP daemon. Issue the command (as root): <userinput>/usr/sbin/rarpd -a</userinput> on most Linux systems and SunOS 5 (Solaris 2), <userinput>/usr/sbin/in.rarpd -a</userinput> on some other Linux systems, or <userinput>/usr/etc/rarpd -a</userinput> in SunOS 4 (Solaris 1)." msgstr "" #. Tag: title -#: install-methods.xml:1212 +#: install-methods.xml:1191 #, no-c-format msgid "Setting up BOOTP server" msgstr "" #. Tag: para -#: install-methods.xml:1213 +#: install-methods.xml:1192 #, no-c-format msgid "There are two BOOTP servers available for GNU/Linux. The first is CMU <command>bootpd</command>. The other is actually a DHCP server: ISC <command>dhcpd</command>. In &debian; these are contained in the <classname>bootp</classname> and <classname>dhcp</classname> packages respectively." msgstr "" #. Tag: para -#: install-methods.xml:1221 +#: install-methods.xml:1200 #, no-c-format msgid "" "To use CMU <command>bootpd</command>, you must first uncomment (or add) the relevant line in <filename>/etc/inetd.conf</filename>. On &debian;, you can run <userinput>update-inetd --enable bootps</userinput>, then <userinput>/etc/init.d/inetd reload</userinput> to do so. Just in case your BOOTP server does not run Debian, the line in question should look like: <informalexample><screen>\n" @@ -924,19 +901,19 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1254 +#: install-methods.xml:1233 #, no-c-format msgid "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really easy, because it treats BOOTP clients as a moderately special case of DHCP clients. Some architectures require a complex configuration for booting clients via BOOTP. If yours is one of those, read the section <xref linkend=\"dhcpd\"/>. Otherwise, you will probably be able to get away with simply adding the <userinput>allow bootp</userinput> directive to the configuration block for the subnet containing the client, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcpd restart</userinput>." msgstr "" #. Tag: title -#: install-methods.xml:1275 +#: install-methods.xml:1254 #, no-c-format msgid "Setting up a DHCP server" msgstr "" #. Tag: para -#: install-methods.xml:1276 +#: install-methods.xml:1255 #, no-c-format msgid "" "One free software DHCP server is ISC <command>dhcpd</command>. In &debian;, this is available in the <classname>dhcp</classname> package. Here is a sample configuration file for it (usually <filename>/etc/dhcpd.conf</filename>): <informalexample><screen>\n" @@ -963,25 +940,25 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1288 +#: install-methods.xml:1267 #, no-c-format msgid "In this example, there is one server <replaceable>servername</replaceable> which performs all of the work of DHCP server, TFTP server, and network gateway. You will almost certainly need to change the domain-name options, as well as the server name and client hardware address. The <replaceable>filename</replaceable> option should be the name of the file which will be retrieved via TFTP." msgstr "" #. Tag: para -#: install-methods.xml:1298 +#: install-methods.xml:1277 #, no-c-format msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/dhcpd restart</userinput>." msgstr "" #. Tag: title -#: install-methods.xml:1306 +#: install-methods.xml:1285 #, no-c-format msgid "Enabling PXE Booting in the DHCP configuration" msgstr "" #. Tag: para -#: install-methods.xml:1307 +#: install-methods.xml:1286 #, no-c-format msgid "" "Here is another example for a <filename>dhcp.conf</filename> using the Pre-boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n" @@ -1016,13 +993,13 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1323 +#: install-methods.xml:1302 #, no-c-format msgid "Enabling the TFTP Server" msgstr "" #. Tag: para -#: install-methods.xml:1324 +#: install-methods.xml:1303 #, no-c-format msgid "" "To get the TFTP server ready to go, you should first make sure that <command>tftpd</command> is enabled. This is usually enabled by having something like the following line in <filename>/etc/inetd.conf</filename>: <informalexample><screen>\n" @@ -1031,13 +1008,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1335 +#: install-methods.xml:1314 #, no-c-format msgid "Look in that file and remember the directory which is used as the argument of <command>in.tftpd</command>; you'll need that below. The <userinput>-l</userinput> argument enables some versions of <command>in.tftpd</command> to log all requests to the system logs; this is useful for diagnosing boot errors. If you've had to change <filename>/etc/inetd.conf</filename>, you'll have to notify the running <command>inetd</command> process that the file has changed. On a Debian machine, run <userinput>/etc/init.d/inetd reload</userinput>; on other machines, find out the process ID for <command>inetd</command>, and run <userinput>kill -HUP <replaceable>inetd-pid</replaceable></userinput>." msgstr "" #. Tag: para -#: install-methods.xml:1349 +#: install-methods.xml:1328 #, no-c-format msgid "" "If you intend to install Debian on an SGI machine and your TFTP server is a GNU/Linux box running Linux 2.4, you'll need to set the following on your server: <informalexample><screen>\n" @@ -1048,85 +1025,85 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1371 +#: install-methods.xml:1350 #, no-c-format msgid "Move TFTP Images Into Place" msgstr "" #. Tag: para -#: install-methods.xml:1372 +#: install-methods.xml:1351 #, no-c-format msgid "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-files\"/>, in the <command>tftpd</command> boot image directory. Generally, this directory will be <filename>/tftpboot</filename>. You'll have to make a link from that file to the file which <command>tftpd</command> will use for booting a particular client. Unfortunately, the file name is determined by the TFTP client, and there are no strong standards." msgstr "" #. Tag: para -#: install-methods.xml:1382 +#: install-methods.xml:1361 #, no-c-format msgid "On NewWorld Power Macintosh machines, you will need to set up the <command>yaboot</command> boot loader as the TFTP boot image. <command>Yaboot</command> will then retrieve the kernel and RAMdisk images via TFTP itself. For net booting, use the <filename>yaboot-netboot.conf</filename>. Just rename this to <filename>yaboot.conf</filename> in the TFTP directory." msgstr "" #. Tag: para -#: install-methods.xml:1391 +#: install-methods.xml:1370 #, no-c-format msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/pxelinux.0</filename> to <command>tftpd</command> as the filename to boot." msgstr "" #. Tag: para -#: install-methods.xml:1399 +#: install-methods.xml:1378 #, no-c-format msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/debian-installer/ia64/elilo.efi</filename> to <command>tftpd</command> as the filename to boot." msgstr "" #. Tag: title -#: install-methods.xml:1411 +#: install-methods.xml:1390 #, no-c-format msgid "DECstation TFTP Images" msgstr "" #. Tag: para -#: install-methods.xml:1412 +#: install-methods.xml:1391 #, no-c-format msgid "For DECstations, there are tftpimage files for each subarchitecture, which contain both kernel and installer in one file. The naming convention is <filename><replaceable>subarchitecture</replaceable>/netboot-boot.img</filename>. Copy the tftpimage file you would like to use to <userinput>/tftpboot/tftpboot.img</userinput> if you work with the example BOOTP/DHCP setups described above." msgstr "" #. Tag: para -#: install-methods.xml:1422 +#: install-methods.xml:1401 #, no-c-format msgid "The DECstation firmware boots by TFTP with the command <userinput>boot <replaceable>#</replaceable>/tftp</userinput>, where <replaceable>#</replaceable> is the number of the TurboChannel device from which to boot. On most DECstations this is <quote>3</quote>. If the BOOTP/DHCP server does not supply the filename or you need to pass additional parameters, they can optionally be appended with the following syntax:" msgstr "" #. Tag: userinput -#: install-methods.xml:1434 +#: install-methods.xml:1413 #, no-c-format msgid "boot #/tftp/filename param1=value1 param2=value2 ..." msgstr "" #. Tag: para -#: install-methods.xml:1436 +#: install-methods.xml:1415 #, no-c-format msgid "Several DECstation firmware revisions show a problem with regard to net booting: the transfer starts, but after some time it stops with an <computeroutput>a.out err</computeroutput>. This can have several reasons: <orderedlist> <listitem><para> The firmware does not respond to ARP requests during a TFTP transfer. This leads to an ARP timeout and the transfer stops. The solution is to add the MAC address of the Ethernet card in the DECstation statically to the ARP table of the TFTP server. This is done by running <userinput>arp -s <replaceable>IP-address</replaceable> <replaceable>MAC-address</replaceable></userinput> as root on the machine acting as TFTP server. The MAC-address of the DECstation can be read out by entering <command>cnfg</command> at the DECstation firmware prompt. </para></listitem> <listitem><para> The firmware has a size limit on the files that can be booted by TFTP. </para></listitem> </orderedlist> There are also firmware revisions that cannot boot via TFTP at all. An overview about the different firmware revisions can be found at the NetBSD web pages: <ulink url=\"http://www.netbsd.org/Ports/pmax/board-list.html#proms\"></ulink>." msgstr "" #. Tag: title -#: install-methods.xml:1474 +#: install-methods.xml:1453 #, no-c-format msgid "Alpha TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1475 +#: install-methods.xml:1454 #, no-c-format msgid "On Alpha, you must specify the filename (as a relative path to the boot image directory) using the <userinput>-file</userinput> argument to the SRM <userinput>boot</userinput> command, or by setting the <userinput>BOOT_FILE</userinput> environment variable. Alternatively, the filename can be given via BOOTP (in ISC <command>dhcpd</command>, use the <userinput>filename</userinput> directive). Unlike Open Firmware, there is <emphasis>no default filename</emphasis> on SRM, so you <emphasis>must</emphasis> specify a filename by either one of these methods." msgstr "" #. Tag: title -#: install-methods.xml:1490 +#: install-methods.xml:1469 #, no-c-format msgid "SPARC TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1491 +#: install-methods.xml:1470 #, no-c-format msgid "" "Some SPARC architectures add the subarchitecture names, such as <quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename would be <filename>C0A80103.SUN4C</filename>. However, there are also subarchitectures where the file the client looks for is just <filename>client-ip-in-hex</filename>. An easy way to determine the hexadecimal code for the IP address is to enter the following command in a shell (assuming the machine's intended IP is 10.0.0.4). <informalexample><screen>\n" @@ -1135,79 +1112,79 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1507 +#: install-methods.xml:1486 #, no-c-format msgid "You can also force some sparc systems to look for a specific file name by adding it to the end of the OpenPROM boot command, such as <userinput>boot net my-sparc.image</userinput>. This must still reside in the directory that the TFTP server looks in." msgstr "" #. Tag: title -#: install-methods.xml:1518 +#: install-methods.xml:1497 #, no-c-format msgid "BVM/Motorola TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1519 +#: install-methods.xml:1498 #, no-c-format msgid "For BVM and Motorola VMEbus systems copy the files &bvme6000-tftp-files; to <filename>/tftpboot/</filename>." msgstr "" #. Tag: para -#: install-methods.xml:1524 +#: install-methods.xml:1503 #, no-c-format msgid "Next, configure your boot ROMs or BOOTP server to initially load the <filename>tftplilo.bvme</filename> or <filename>tftplilo.mvme</filename> files from the TFTP server. Refer to the <filename>tftplilo.txt</filename> file for your subarchitecture for additional system-specific configuration information." msgstr "" #. Tag: title -#: install-methods.xml:1536 +#: install-methods.xml:1515 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1537 +#: install-methods.xml:1516 #, no-c-format msgid "On SGI machines you can rely on the <command>bootpd</command> to supply the name of the TFTP file. It is given either as the <userinput>bf=</userinput> in <filename>/etc/bootptab</filename> or as the <userinput>filename=</userinput> option in <filename>/etc/dhcpd.conf</filename>." msgstr "" #. Tag: title -#: install-methods.xml:1549 +#: install-methods.xml:1528 #, no-c-format msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1550 +#: install-methods.xml:1529 #, no-c-format msgid "You don't have to configure DHCP in a special way because you'll pass the full path of the file to be loaded to CFE." msgstr "" #. Tag: title -#: install-methods.xml:1655 +#: install-methods.xml:1634 #, no-c-format msgid "Automatic Installation" msgstr "" #. Tag: para -#: install-methods.xml:1656 +#: install-methods.xml:1635 #, no-c-format msgid "For installing on multiple computers it's possible to do fully automatic installations. Debian packages intended for this include <classname>fai</classname> (which uses an install server), <classname>replicator</classname>, <classname>systemimager</classname>, <classname>autoinstall</classname>, and the Debian Installer itself." msgstr "" #. Tag: title -#: install-methods.xml:1669 +#: install-methods.xml:1648 #, no-c-format msgid "Automatic Installation Using the Debian Installer" msgstr "" #. Tag: para -#: install-methods.xml:1670 +#: install-methods.xml:1649 #, no-c-format msgid "The Debian Installer supports automating installs via preconfiguration files. A preconfiguration file can be loaded from the network or from removable media, and used to fill in answers to questions asked during the installation process." msgstr "" #. Tag: para -#: install-methods.xml:1677 +#: install-methods.xml:1656 #, no-c-format msgid "Full documentation on preseeding including a working example that you can edit is in <xref linkend=\"appendix-preseed\"/>." msgstr "" diff --git a/po/pot/partitioning.pot b/po/pot/partitioning.pot index 3076c2b7e..0897906e1 100644 --- a/po/pot/partitioning.pot +++ b/po/pot/partitioning.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-08-07 22:39+0000\n" +"POT-Creation-Date: 2006-08-18 17:32+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -656,7 +656,7 @@ msgid "One key point when partitioning for Mac type disks is that the swap parti msgstr "" #. Tag: title -#: partitioning.xml:617 partitioning.xml:677 partitioning.xml:701 partitioning.xml:798 partitioning.xml:912 partitioning.xml:989 +#: partitioning.xml:617 partitioning.xml:678 partitioning.xml:702 partitioning.xml:799 partitioning.xml:913 partitioning.xml:990 #, no-c-format msgid "Partitioning for &arch-title;" msgstr "" @@ -676,101 +676,101 @@ msgstr "" #. Tag: para #: partitioning.xml:636 #, no-c-format -msgid "Unless you wish to use the disk you are partitioning from Tru64 Unix or one of the free 4.4BSD-Lite derived operating systems (FreeBSD, OpenBSD, or NetBSD), it is suggested that you do <emphasis>not</emphasis> make the third partition contain the whole disk. This is not required by <command>aboot</command>, and in fact, it may lead to confusion since the <command>swriteboot</command> utility used to install <command>aboot</command> in the boot sector will complain about a partition overlapping with the boot block." +msgid "Unless you wish to use the disk you are partitioning from Tru64 Unix or one of the free 4.4BSD-Lite derived operating systems (FreeBSD, OpenBSD, or NetBSD), you should <emphasis>not</emphasis> create the third partition as a <quote>whole disk</quote> partition (i.e. with start and end sectors to span the whole disk), as this renders the disk incompatible with the tools used to make it bootable with aboot. This means that the disk configured by the installer for use as the Debian boot disk will be inaccessible to the operating systems mentioned earlier." msgstr "" #. Tag: para -#: partitioning.xml:647 +#: partitioning.xml:648 #, no-c-format msgid "Also, because <command>aboot</command> is written to the first few sectors of the disk (currently it occupies about 70 kilobytes, or 150 sectors), you <emphasis>must</emphasis> leave enough empty space at the beginning of the disk for it. In the past, it was suggested that you make a small partition at the beginning of the disk, to be left unformatted. For the same reason mentioned above, we now suggest that you do not do this on disks that will only be used by GNU/Linux. When using <command>partman</command>, a small partition will still be created for <command>aboot</command> for convenience reasons." msgstr "" #. Tag: para -#: partitioning.xml:659 +#: partitioning.xml:660 #, no-c-format msgid "For ARC installations, you should make a small FAT partition at the beginning of the disk to contain <command>MILO</command> and <command>linload.exe</command> — 5 megabytes should be sufficient, see <xref linkend=\"non-debian-partitioning\"/>. Unfortunately, making FAT file systems from the menu is not yet supported, so you'll have to do it manually from the shell using <command>mkdosfs</command> before attempting to install the boot loader." msgstr "" #. Tag: para -#: partitioning.xml:678 +#: partitioning.xml:679 #, no-c-format msgid "PALO, the HPPA boot loader, requires a partition of type <quote>F0</quote> somewhere in the first 2GB. This is where the boot loader and an optional kernel and RAMdisk will be stored, so make it big enough for that — at least 4Mb (I like 8–16MB). An additional requirement of the firmware is that the Linux kernel must reside within the first 2GB of the disk. This is typically achieved by making the root ext2 partition fit entirely within the first 2GB of the disk. Alternatively you can create a small ext2 partition near the start of the disk and mount that on <filename>/boot</filename>, since that is the directory where the Linux kernel(s) will be stored. <filename>/boot</filename> needs to be big enough to hold whatever kernels (and backups) you might wish to load; 25–50MB is generally sufficient." msgstr "" #. Tag: para -#: partitioning.xml:702 +#: partitioning.xml:703 #, no-c-format msgid "If you have an existing other operating system such as DOS or Windows and you want to preserve that operating system while installing Debian, you may need to resize its partition to free up space for the Debian installation. The installer supports resizing of both FAT and NTFS filesystems; when you get to the installer's partitioning step, select the option <guimenuitem>Manually edit partition table</guimenuitem> and then simply select an existing partition and change its size." msgstr "" #. Tag: para -#: partitioning.xml:712 +#: partitioning.xml:713 #, no-c-format msgid "The PC BIOS generally adds additional constraints for disk partitioning. There is a limit to how many <quote>primary</quote> and <quote>logical</quote> partitions a drive can contain. Additionally, with pre 1994–98 BIOSes, there are limits to where on the drive the BIOS can boot from. More information can be found in the <ulink url=\"&url-partition-howto;\">Linux Partition HOWTO</ulink> and the <ulink url=\"&url-phoenix-bios-faq-large-disk;\">Phoenix BIOS FAQ</ulink>, but this section will include a brief overview to help you plan most situations." msgstr "" #. Tag: para -#: partitioning.xml:723 +#: partitioning.xml:724 #, no-c-format msgid "<quote>Primary</quote> partitions are the original partitioning scheme for PC disks. However, there can only be four of them. To get past this limitation, <quote>extended</quote> and <quote>logical</quote> partitions were invented. By setting one of your primary partitions as an extended partition, you can subdivide all the space allocated to that partition into logical partitions. You can create up to 60 logical partitions per extended partition; however, you can only have one extended partition per drive." msgstr "" #. Tag: para -#: partitioning.xml:734 +#: partitioning.xml:735 #, no-c-format msgid "Linux limits the partitions per drive to 15 partitions for SCSI disks (3 usable primary partitions, 12 logical partitions), and 63 partitions on an IDE drive (3 usable primary partitions, 60 logical partitions). However the normal &debian; system provides only 20 devices for partitions, so you may not install on partitions higher than 20 unless you first manually create devices for those partitions." msgstr "" #. Tag: para -#: partitioning.xml:744 +#: partitioning.xml:745 #, no-c-format msgid "If you have a large IDE disk, and are using neither LBA addressing, nor overlay drivers (sometimes provided by hard disk manufacturers), then the boot partition (the partition containing your kernel image) must be placed within the first 1024 cylinders of your hard drive (usually around 524 megabytes, without BIOS translation)." msgstr "" #. Tag: para -#: partitioning.xml:752 +#: partitioning.xml:753 #, no-c-format msgid "This restriction doesn't apply if you have a BIOS newer than around 1995–98 (depending on the manufacturer) that supports the <quote>Enhanced Disk Drive Support Specification</quote>. Both Lilo, the Linux loader, and Debian's alternative <command>mbr</command> must use the BIOS to read the kernel from the disk into RAM. If the BIOS int 0x13 large disk access extensions are found to be present, they will be utilized. Otherwise, the legacy disk access interface is used as a fall-back, and it cannot be used to address any location on the disk higher than the 1023rd cylinder. Once Linux is booted, no matter what BIOS your computer has, these restrictions no longer apply, since Linux does not use the BIOS for disk access." msgstr "" #. Tag: para -#: partitioning.xml:766 +#: partitioning.xml:767 #, no-c-format msgid "If you have a large disk, you might have to use cylinder translation techniques, which you can set from your BIOS setup program, such as LBA (Logical Block Addressing) or CHS translation mode (<quote>Large</quote>). More information about issues with large disks can be found in the <ulink url=\"&url-large-disk-howto;\">Large Disk HOWTO</ulink>. If you are using a cylinder translation scheme, and the BIOS does not support the large disk access extensions, then your boot partition has to fit within the <emphasis>translated</emphasis> representation of the 1024th cylinder." msgstr "" #. Tag: para -#: partitioning.xml:778 +#: partitioning.xml:779 #, no-c-format msgid "The recommended way of accomplishing this is to create a small (25–50MB should suffice) partition at the beginning of the disk to be used as the boot partition, and then create whatever other partitions you wish to have, in the remaining area. This boot partition <emphasis>must</emphasis> be mounted on <filename>/boot</filename>, since that is the directory where the Linux kernel(s) will be stored. This configuration will work on any system, regardless of whether LBA or large disk CHS translation is used, and regardless of whether your BIOS supports the large disk access extensions." msgstr "" #. Tag: para -#: partitioning.xml:799 +#: partitioning.xml:800 #, no-c-format msgid "The <command>partman</command> disk partitioner is the default partitioning tool for the installer. It manages the set of partitions and their mount points to ensure that the disks and filesystems are properly configured for a successful installation. It actually uses <command>parted</command> to do the on-disk partitioning." msgstr "" #. Tag: title -#: partitioning.xml:811 +#: partitioning.xml:812 #, no-c-format msgid "EFI Recognized Formats" msgstr "" #. Tag: para -#: partitioning.xml:812 +#: partitioning.xml:813 #, no-c-format msgid "The IA64 EFI firmware supports two partition table (or disk label) formats, GPT and MS-DOS. MS-DOS, the format typically used on i386 PCs, is no longer recommended for IA64 systems. Although the installer also provides <command>cfdisk</command>, you should only use <ulink url=\"parted.txt\"> <command>parted</command></ulink> because only it can manage both GPT and MS-DOS tables correctly." msgstr "" #. Tag: para -#: partitioning.xml:824 +#: partitioning.xml:825 #, no-c-format msgid "The automatic partitioning recipes for <command>partman</command> allocate an EFI partition as the first partition on the disk. You can also set up the partition under the <guimenuitem>Guided partitioning</guimenuitem> from the main menu in a manner similar to setting up a <emphasis>swap</emphasis> partition." msgstr "" #. Tag: para -#: partitioning.xml:832 +#: partitioning.xml:833 #, no-c-format msgid "" "The <command>partman</command> partitioner will handle most disk layouts. For those rare cases where it is necessary to manually set up a disk, you can use the shell as described above and run the <command>parted</command> utility directly using its command line interface. Assuming that you want to erase your whole disk and create a GPT table and some partitions, then something similar to the following command sequence could be used: <informalexample><screen>\n" @@ -785,97 +785,97 @@ msgid "" msgstr "" #. Tag: title -#: partitioning.xml:857 +#: partitioning.xml:858 #, no-c-format msgid "Boot Loader Partition Requirements" msgstr "" #. Tag: para -#: partitioning.xml:858 +#: partitioning.xml:859 #, no-c-format msgid "ELILO, the ia64 boot loader, requires a partition containing a FAT file system with the <userinput>boot</userinput> flag set. The partition must be big enough to hold the boot loader and any kernels or RAMdisks you may wish to boot. A minimum size would be about 20MB, but if you expect to run with multiple kernels, then 128MB might be a better size." msgstr "" #. Tag: para -#: partitioning.xml:867 +#: partitioning.xml:868 #, no-c-format msgid "The EFI Boot Manager and the EFI Shell fully support the GPT table so the boot partition does not necessarily have to be the first partition or even on the same disk. This is convenient if you should forget to allocate the partition and only find out after you have formatted the other partitions on your disk(s). The <command>partman</command> partitioner checks for an EFI partition at the same time it checks for a properly set up <emphasis>root</emphasis> partition. This gives you an opportunity to correct the disk layout before the package install begins. The easiest way to correct this omission is to shrink the last partition of the disk to make enough free space for adding an EFI partition." msgstr "" #. Tag: para -#: partitioning.xml:882 +#: partitioning.xml:883 #, no-c-format msgid "It is strongly recommended that you allocate the EFI boot partition on the same disk as the <emphasis>root</emphasis> filesystem." msgstr "" #. Tag: title -#: partitioning.xml:890 +#: partitioning.xml:891 #, no-c-format msgid "EFI Diagnostic Partitions" msgstr "" #. Tag: para -#: partitioning.xml:891 +#: partitioning.xml:892 #, no-c-format msgid "The EFI firmware is significantly more sophisticated than the usual BIOS seen on most x86 PCs. Some system vendors take advantage of the ability of the EFI to access files and run programs from a hard disk filesystem to store diagnostics and EFI based system management utilities on the hard disk. This is a separate FAT format filesystem on the system disk. Consult the system documentation and accessories that come with the system for details. The easiest time to set up a diagnostics partition is at the same time you set up the EFI boot partition." msgstr "" #. Tag: para -#: partitioning.xml:913 +#: partitioning.xml:914 #, no-c-format msgid "SGI machines require an SGI disk label in order to make the system bootable from hard disk. It can be created in the fdisk expert menu. The thereby created volume header (partition number 9) should be at least 3MB large. If the volume header created is too small, you can simply delete partition number 9 and re-add it with a different size. Note that the volume header must start at sector 0." msgstr "" #. Tag: title -#: partitioning.xml:930 +#: partitioning.xml:931 #, no-c-format msgid "Partitioning Newer PowerMacs" msgstr "" #. Tag: para -#: partitioning.xml:931 +#: partitioning.xml:932 #, no-c-format msgid "If you are installing onto a NewWorld PowerMac you must create a special bootstrap partition to hold the boot loader. The size of this partition must be 800KB and its partition type must be <emphasis>Apple_Bootstrap</emphasis>. If the bootstrap partition is not created with the <emphasis>Apple_Bootstrap</emphasis> type your machine cannot be made bootable from the hard disk. This partition can easily be created by creating a new partition in <command>partman</command> and telling it to use it as a <quote>NewWorld boot partition</quote>, or in <command>mac-fdisk</command> using the <userinput>b</userinput> command." msgstr "" #. Tag: para -#: partitioning.xml:944 +#: partitioning.xml:945 #, no-c-format msgid "The special partition type Apple_Bootstrap is required to prevent MacOS from mounting and damaging the bootstrap partition, as there are special modifications made to it in order for OpenFirmware to boot it automatically." msgstr "" #. Tag: para -#: partitioning.xml:951 +#: partitioning.xml:952 #, no-c-format msgid "Note that the bootstrap partition is only meant to hold 3 very small files: the <command>yaboot</command> binary, its configuration <filename>yaboot.conf</filename>, and a first stage OpenFirmware loader <command>ofboot.b</command>. It need not and must not be mounted on your file system nor have kernels or anything else copied to it. The <command>ybin</command> and <command>mkofboot</command> utilities are used to manipulate this partition." msgstr "" #. Tag: para -#: partitioning.xml:961 +#: partitioning.xml:962 #, no-c-format msgid "In order for OpenFirmware to automatically boot &debian; the bootstrap partition should appear before other boot partitions on the disk, especially MacOS boot partitions. The bootstrap partition should be the first one you create. However, if you add a bootstrap partition later, you can use <command>mac-fdisk</command>'s <userinput>r</userinput> command to reorder the partition map so the bootstrap partition comes right after the map (which is always partition 1). It's the logical map order, not the physical address order, that counts." msgstr "" #. Tag: para -#: partitioning.xml:973 +#: partitioning.xml:974 #, no-c-format msgid "Apple disks normally have several small driver partitions. If you intend to dual boot your machine with MacOSX, you should retain these partitions and a small HFS partition (800k is the minimum size). That is because MacOSX, on every boot, offers to initialize any disks which do not have active MacOS partitions and driver partitions." msgstr "" #. Tag: para -#: partitioning.xml:990 +#: partitioning.xml:991 #, no-c-format msgid "Make sure you create a <quote>Sun disk label</quote> on your boot disk. This is the only kind of partition scheme that the OpenBoot PROM understands, and so it's the only scheme from which you can boot. The <keycap>s</keycap> key is used in <command>fdisk</command> to create Sun disk labels." msgstr "" #. Tag: para -#: partitioning.xml:998 +#: partitioning.xml:999 #, no-c-format msgid "Furthermore, on &arch-title; disks, make sure your first partition on your boot disk starts at cylinder 0. While this is required, it also means that the first partition will contain the partition table and the boot block, which are the first two sectors of the disk. You must <emphasis>not</emphasis> put swap on the first partition of the boot drive, since swap partitions do not preserve the first few sectors of the partition. You can put Ext2 or UFS partitions there; these will leave the partition table and the boot block alone." msgstr "" #. Tag: para -#: partitioning.xml:1009 +#: partitioning.xml:1010 #, no-c-format msgid "It is also advised that the third partition should be of type <quote>Whole disk</quote> (type 5), and contain the entire disk (from the first cylinder to the last). This is simply a convention of Sun disk labels, and helps the <command>SILO</command> boot loader keep its bearings." msgstr "" diff --git a/po/pot/post-install.pot b/po/pot/post-install.pot index 120fa6b0e..7f3872e2d 100644 --- a/po/pot/post-install.pot +++ b/po/pot/post-install.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-08-16 18:10+0000\n" +"POT-Creation-Date: 2006-08-18 17:32+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -23,113 +23,131 @@ msgstr "" #. Tag: title #: post-install.xml:13 #, no-c-format +msgid "Shutting down the system" +msgstr "" + +#. Tag: para +#: post-install.xml:15 +#, no-c-format +msgid "To shut down a running Linux system, you must not reboot with the reset switch on the front or back of your computer, or just turn off the computer. Linux should be shut down in a controlled manner, otherwise files might get lost and/or disk damage might occur. If you run a desktop environment, there is usually an option to <quote>log out</quote> available from the application menu that allows you to shutdown (or reboot) the system." +msgstr "" + +#. Tag: para +#: post-install.xml:25 +#, no-c-format +msgid "Alternatively you can press the key combination <keycombo> <keycap>Ctrl</keycap> <keycap>Alt</keycap> <keycap>Del</keycap> </keycombo> <phrase arch=\"powerpc;m68k\"> or <keycombo> <keycap>Control</keycap> <keycap>Shift</keycap> <keycap>Power</keycap> </keycombo> on Macintosh systems</phrase>. A last option is to log in as root and type one of the commands <command>poweroff</command>, <command>halt</command> or <command>shutdown -h now</command> if either of the key combinations do not work or you prefer to type commands; use <command>reboot</command> to reboot the system." +msgstr "" + +#. Tag: title +#: post-install.xml:46 +#, no-c-format msgid "If You Are New to Unix" msgstr "" #. Tag: para -#: post-install.xml:14 +#: post-install.xml:47 #, no-c-format msgid "If you are new to Unix, you probably should go out and buy some books and do some reading. A lot of valuable information can also be found in the <ulink url=\"&url-debian-reference;\">Debian Reference</ulink>. This <ulink url=\"&url-unix-faq;\">list of Unix FAQs</ulink> contains a number of UseNet documents which provide a nice historical reference." msgstr "" #. Tag: para -#: post-install.xml:22 +#: post-install.xml:55 #, no-c-format msgid "Linux is an implementation of Unix. The <ulink url=\"&url-ldp;\">Linux Documentation Project (LDP)</ulink> collects a number of HOWTOs and online books relating to Linux. Most of these documents can be installed locally; just install the <classname>doc-linux-html</classname> package (HTML versions) or the <classname>doc-linux-text</classname> package (ASCII versions), then look in <filename>/usr/share/doc/HOWTO</filename>. International versions of the LDP HOWTOs are also available as Debian packages." msgstr "" #. Tag: title -#: post-install.xml:43 +#: post-install.xml:76 #, no-c-format msgid "Orienting Yourself to Debian" msgstr "" #. Tag: para -#: post-install.xml:44 +#: post-install.xml:77 #, no-c-format msgid "Debian is a little different from other distributions. Even if you're familiar with Linux in other distributions, there are things you should know about Debian to help you to keep your system in a good, clean state. This chapter contains material to help you get oriented; it is not intended to be a tutorial for how to use Debian, but just a very brief glimpse of the system for the very rushed." msgstr "" #. Tag: title -#: post-install.xml:55 +#: post-install.xml:88 #, no-c-format msgid "Debian Packaging System" msgstr "" #. Tag: para -#: post-install.xml:56 +#: post-install.xml:89 #, no-c-format msgid "The most important concept to grasp is the Debian packaging system. In essence, large parts of your system should be considered under the control of the packaging system. These include: <itemizedlist> <listitem><para> <filename>/usr</filename> (excluding <filename>/usr/local</filename>) </para></listitem> <listitem><para> <filename>/var</filename> (you could make <filename>/var/local</filename> and be safe in there) </para></listitem> <listitem><para> <filename>/bin</filename> </para></listitem> <listitem><para> <filename>/sbin</filename> </para></listitem> <listitem><para> <filename>/lib</filename> </para></listitem> </itemizedlist> For instance, if you replace <filename>/usr/bin/perl</filename>, that will work, but then if you upgrade your <classname>perl</classname> package, the file you put there will be replaced. Experts can get around this by putting packages on <quote>hold</quote> in <command>aptitude</command>." msgstr "" #. Tag: para -#: post-install.xml:97 +#: post-install.xml:130 #, no-c-format msgid "One of the best installation methods is apt. You can use the command line version <command>apt-get</command> or full-screen text version <application>aptitude</application>. Note apt will also let you merge main, contrib, and non-free so you can have export-restricted packages as well as standard versions." msgstr "" #. Tag: title -#: post-install.xml:108 +#: post-install.xml:141 #, no-c-format msgid "Application Version Management" msgstr "" #. Tag: para -#: post-install.xml:109 +#: post-install.xml:142 #, no-c-format msgid "Alternative versions of applications are managed by update-alternatives. If you are maintaining multiple versions of your applications, read the update-alternatives man page." msgstr "" #. Tag: title -#: post-install.xml:119 +#: post-install.xml:152 #, no-c-format msgid "Cron Job Management" msgstr "" #. Tag: para -#: post-install.xml:120 +#: post-install.xml:153 #, no-c-format msgid "Any jobs under the purview of the system administrator should be in <filename>/etc</filename>, since they are configuration files. If you have a root cron job for daily, weekly, or monthly runs, put them in <filename>/etc/cron.{daily,weekly,monthly}</filename>. These are invoked from <filename>/etc/crontab</filename>, and will run in alphabetic order, which serializes them." msgstr "" #. Tag: para -#: post-install.xml:129 +#: post-install.xml:162 #, no-c-format msgid "On the other hand, if you have a cron job that (a) needs to run as a special user, or (b) needs to run at a special time or frequency, you can use either <filename>/etc/crontab</filename>, or, better yet, <filename>/etc/cron.d/whatever</filename>. These particular files also have an extra field that allows you to stipulate the user under which the cron job runs." msgstr "" #. Tag: para -#: post-install.xml:138 +#: post-install.xml:171 #, no-c-format msgid "In either case, you just edit the files and cron will notice them automatically. There is no need to run a special command. For more information see cron(8), crontab(5), and <filename>/usr/share/doc/cron/README.Debian</filename>." msgstr "" #. Tag: title -#: post-install.xml:155 +#: post-install.xml:188 #, no-c-format msgid "Reactivating DOS and Windows" msgstr "" #. Tag: para -#: post-install.xml:156 +#: post-install.xml:189 #, no-c-format msgid "After installing the base system and writing to the <emphasis>Master Boot Record</emphasis>, you will be able to boot Linux, but probably nothing else. This depends what you have chosen during the installation. This chapter will describe how you can reactivate your old systems so that you can also boot your DOS or Windows again." msgstr "" #. Tag: para -#: post-install.xml:164 +#: post-install.xml:197 #, no-c-format msgid "<command>LILO</command> is a boot manager with which you can also boot other operating systems than Linux, which complies to PC conventions. The boot manager is configured via <filename>/etc/lilo.conf</filename> file. Whenever you edited this file you have to run <command>lilo</command> afterwards. The reason for this is that the changes will take place only when you call the program." msgstr "" #. Tag: para -#: post-install.xml:174 +#: post-install.xml:207 #, no-c-format msgid "Important parts of the <filename>lilo.conf</filename> file are the lines containing the <userinput>image</userinput> and <userinput>other</userinput> keywords, as well as the lines following those. They can be used to describe a system which can be booted by <command>LILO</command>. Such a system can include a kernel (<userinput>image</userinput>), a root partition, additional kernel parameters, etc. as well as a configuration to boot another, non-Linux (<userinput>other</userinput>) operating system. These keywords can also be used more than once. The ordering of these systems within the configuration file is important because it determines which system will be booted automatically after, for instance, a timeout (<userinput>delay</userinput>) presuming <command>LILO</command> wasn't stopped by pressing the <keycap>shift</keycap> key." msgstr "" #. Tag: para -#: post-install.xml:190 +#: post-install.xml:223 #, no-c-format msgid "" "After a fresh install of Debian, just the current system is configured for booting with <command>LILO</command>. If you want to boot another Linux kernel, you have to edit the configuration file <filename>/etc/lilo.conf</filename> to add the following lines: <informalexample><screen>\n" @@ -138,211 +156,211 @@ msgid "" msgstr "" #. Tag: para -#: post-install.xml:210 +#: post-install.xml:243 #, no-c-format msgid "Notice that there are other boot loaders available in &debian;, such as GRUB (in <classname>grub</classname> package), CHOS (in <classname>chos</classname> package), Extended-IPL (in <classname>extipl</classname> package), loadlin (in <classname>loadlin</classname> package) etc." msgstr "" #. Tag: title -#: post-install.xml:225 +#: post-install.xml:258 #, no-c-format msgid "Further Reading and Information" msgstr "" #. Tag: para -#: post-install.xml:226 +#: post-install.xml:259 #, no-c-format msgid "If you need information about a particular program, you should first try <userinput>man <replaceable>program</replaceable></userinput>, or <userinput>info <replaceable>program</replaceable></userinput>." msgstr "" #. Tag: para -#: post-install.xml:232 +#: post-install.xml:265 #, no-c-format msgid "There is lots of useful documentation in <filename>/usr/share/doc</filename> as well. In particular, <filename>/usr/share/doc/HOWTO</filename> and <filename>/usr/share/doc/FAQ</filename> contain lots of interesting information. To submit bugs, look at <filename>/usr/share/doc/debian/bug*</filename>. To read about Debian-specific issues for particular programs, look at <filename>/usr/share/doc/(package name)/README.Debian</filename>." msgstr "" #. Tag: para -#: post-install.xml:243 +#: post-install.xml:276 #, no-c-format msgid "The <ulink url=\"http://www.debian.org/\">Debian web site</ulink> contains a large quantity of documentation about Debian. In particular, see the <ulink url=\"http://www.debian.org/doc/FAQ/\">Debian GNU/Linux FAQ</ulink> and the <ulink url=\"http://www.debian.org/doc/user-manuals#quick-reference\">Debian Reference</ulink>. An index of more Debian documentation is available from the <ulink url=\"http://www.debian.org/doc/ddp\">Debian Documentation Project</ulink>. The Debian community is self-supporting; to subscribe to one or more of the Debian mailing lists, see the <ulink url=\"http://www.debian.org/MailingLists/subscribe\"> Mail List Subscription</ulink> page. Last, but not least, the <ulink url=\"http://lists.debian.org/\">Debian Mailing List Archives</ulink> contain a wealth of information on Debian." msgstr "" #. Tag: para -#: post-install.xml:261 +#: post-install.xml:294 #, no-c-format msgid "A general source of information on GNU/Linux is the <ulink url=\"http://www.tldp.org/\">Linux Documentation Project</ulink>. There you will find the HOWTOs and pointers to other very valuable information on parts of a GNU/Linux system." msgstr "" #. Tag: title -#: post-install.xml:276 +#: post-install.xml:309 #, no-c-format msgid "Compiling a New Kernel" msgstr "" #. Tag: para -#: post-install.xml:277 +#: post-install.xml:310 #, no-c-format msgid "Why would someone want to compile a new kernel? It is often not necessary since the default kernel shipped with Debian handles most configurations. Also, Debian often offers several alternative kernels. So you may want to check first if there is an alternative kernel image package that better corresponds to your hardware. However, it can be useful to compile a new kernel in order to:" msgstr "" #. Tag: para -#: post-install.xml:287 +#: post-install.xml:320 #, no-c-format msgid "handle special hardware needs, or hardware conflicts with the pre-supplied kernels" msgstr "" #. Tag: para -#: post-install.xml:293 +#: post-install.xml:326 #, no-c-format msgid "use options of the kernel which are not supported in the pre-supplied kernels (such as high memory support)" msgstr "" #. Tag: para -#: post-install.xml:299 +#: post-install.xml:332 #, no-c-format msgid "optimize the kernel by removing useless drivers to speed up boot time" msgstr "" #. Tag: para -#: post-install.xml:304 +#: post-install.xml:337 #, no-c-format msgid "create a monolithic instead of a modularized kernel" msgstr "" #. Tag: para -#: post-install.xml:309 +#: post-install.xml:342 #, no-c-format msgid "run an updated or development kernel" msgstr "" #. Tag: para -#: post-install.xml:314 +#: post-install.xml:347 #, no-c-format msgid "learn more about linux kernels" msgstr "" #. Tag: title -#: post-install.xml:323 +#: post-install.xml:356 #, no-c-format msgid "Kernel Image Management" msgstr "" #. Tag: para -#: post-install.xml:324 +#: post-install.xml:357 #, no-c-format msgid "Don't be afraid to try compiling the kernel. It's fun and profitable." msgstr "" #. Tag: para -#: post-install.xml:328 +#: post-install.xml:361 #, no-c-format msgid "To compile a kernel the Debian way, you need some packages: <classname>fakeroot</classname>, <classname>kernel-package</classname>, <phrase condition=\"classic-kpkg\"><classname>kernel-source-&kernelversion;</classname> (the most recent version at the time of this writing)</phrase> <phrase condition=\"common-kpkg\"><classname>linux-source-2.6</classname></phrase> and a few others which are probably already installed (see <filename>/usr/share/doc/kernel-package/README.gz</filename> for the complete list)." msgstr "" #. Tag: para -#: post-install.xml:339 +#: post-install.xml:372 #, no-c-format msgid "This method will make a .deb of your kernel source, and, if you have non-standard modules, make a synchronized dependent .deb of those too. It's a better way to manage kernel images; <filename>/boot</filename> will hold the kernel, the System.map, and a log of the active config file for the build." msgstr "" #. Tag: para -#: post-install.xml:347 +#: post-install.xml:380 #, no-c-format msgid "Note that you don't <emphasis>have</emphasis> to compile your kernel the <quote>Debian way</quote>; but we find that using the packaging system to manage your kernel is actually safer and easier. In fact, you can get your kernel sources right from Linus instead of <phrase condition=\"classic-kpkg\"><classname>kernel-source-&kernelversion;</classname>,</phrase> <phrase condition=\"common-kpkg\"><classname>linux-source-2.6</classname>,</phrase> yet still use the <classname>kernel-package</classname> compilation method." msgstr "" #. Tag: para -#: post-install.xml:357 +#: post-install.xml:390 #, no-c-format msgid "Note that you'll find complete documentation on using <classname>kernel-package</classname> under <filename>/usr/share/doc/kernel-package</filename>. This section just contains a brief tutorial." msgstr "" #. Tag: para -#: post-install.xml:364 +#: post-install.xml:397 #, no-c-format msgid "Hereafter, we'll assume you have free rein over your machine and will extract your kernel source to somewhere in your home directory<footnote> <para> There are other locations where you can extract kernel sources and build your custom kernel, but this is easiest as it does not require special permissions. </para> </footnote>. We'll also assume that your kernel version is &kernelversion;. Make sure you are in the directory to where you want to unpack the kernel sources, extract them using <phrase condition=\"classic-kpkg\"><userinput>tar xjf /usr/src/kernel-source-&kernelversion;.tar.bz2</userinput></phrase> <phrase condition=\"common-kpkg\"><userinput>tar xjf /usr/src/linux-source-&kernelversion;.tar.bz2</userinput></phrase> and change to the directory <phrase condition=\"classic-kpkg\"><filename>kernel-source-&kernelversion;</filename></phrase> <phrase condition=\"common-kpkg\"><filename>linux-source-&kernelversion;</filename></phrase> that will have been created." msgstr "" #. Tag: para -#: post-install.xml:389 +#: post-install.xml:422 #, no-c-format msgid "Now, you can configure your kernel. Run <userinput>make xconfig</userinput> if X11 is installed, configured and being run; run <userinput>make menuconfig</userinput> otherwise (you'll need <classname>libncurses5-dev</classname> installed). Take the time to read the online help and choose carefully. When in doubt, it is typically better to include the device driver (the software which manages hardware peripherals, such as Ethernet cards, SCSI controllers, and so on) you are unsure about. Be careful: other options, not related to a specific hardware, should be left at the default value if you do not understand them. Do not forget to select <quote>Kernel module loader</quote> in <quote>Loadable module support</quote> (it is not selected by default). If not included, your Debian installation will experience problems." msgstr "" #. Tag: para -#: post-install.xml:404 +#: post-install.xml:437 #, no-c-format msgid "Clean the source tree and reset the <classname>kernel-package</classname> parameters. To do that, do <userinput>make-kpkg clean</userinput>." msgstr "" #. Tag: para -#: post-install.xml:409 +#: post-install.xml:442 #, no-c-format msgid "Now, compile the kernel: <userinput>fakeroot make-kpkg --initrd --revision=custom.1.0 kernel_image</userinput>. The version number of <quote>1.0</quote> can be changed at will; this is just a version number that you will use to track your kernel builds. Likewise, you can put any word you like in place of <quote>custom</quote> (e.g., a host name). Kernel compilation may take quite a while, depending on the power of your machine." msgstr "" #. Tag: para -#: post-install.xml:419 +#: post-install.xml:452 #, no-c-format msgid "Once the compilation is complete, you can install your custom kernel like any package. As root, do <phrase condition=\"classic-kpkg\"> <userinput>dpkg -i ../kernel-image-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. </phrase> <phrase condition=\"common-kpkg\"> <userinput>dpkg -i ../linux-image-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. </phrase> The <replaceable>subarchitecture</replaceable> part is an optional sub-architecture, <phrase arch=\"i386\"> such as <quote>686</quote>, </phrase> depending on what kernel options you set. <userinput>dpkg -i</userinput> will install the kernel, along with some other nice supporting files. For instance, the <filename>System.map</filename> will be properly installed (helpful for debugging kernel problems), and <filename>/boot/config-&kernelversion;</filename> will be installed, containing your current configuration set. Your new kernel package is also clever enough to automatically update your boot loader to use the new kernel. If you have created a modules package, <phrase condition=\"classic-kpkg\">e.g., if you have PCMCIA,</phrase> you'll need to install that package as well." msgstr "" #. Tag: para -#: post-install.xml:446 +#: post-install.xml:479 #, no-c-format msgid "It is time to reboot the system: read carefully any warning that the above step may have produced, then <userinput>shutdown -r now</userinput>." msgstr "" #. Tag: para -#: post-install.xml:451 +#: post-install.xml:484 #, no-c-format msgid "For more information on Debian kernels and kernel compilation, see the <ulink url=\"&url-kernel-handbook;\">Debian Linux Kernel Handbook</ulink>. For more information on <classname>kernel-package</classname>, read the fine documentation in <filename>/usr/share/doc/kernel-package</filename>." msgstr "" #. Tag: title -#: post-install.xml:467 +#: post-install.xml:500 #, no-c-format msgid "Recovering a Broken System" msgstr "" #. Tag: para -#: post-install.xml:468 +#: post-install.xml:501 #, no-c-format msgid "Sometimes, things go wrong, and the system you've carefully installed is no longer bootable. Perhaps the boot loader configuration broke while trying out a change, or perhaps a new kernel you installed won't boot, or perhaps cosmic rays hit your disk and flipped a bit in <filename>/sbin/init</filename>. Regardless of the cause, you'll need to have a system to work from while you fix it, and rescue mode can be useful for this." msgstr "" #. Tag: para -#: post-install.xml:478 +#: post-install.xml:511 #, no-c-format msgid "To access rescue mode, type <userinput>rescue</userinput> at the <prompt>boot:</prompt> prompt, or boot with the <userinput>rescue/enable=true</userinput> boot parameter. You'll be shown the first few screens of the installer, with a note in the corner of the display to indicate that this is rescue mode, not a full installation. Don't worry, your system is not about to be overwritten! Rescue mode simply takes advantage of the hardware detection facilities available in the installer to ensure that your disks, network devices, and so on are available to you while repairing your system." msgstr "" #. Tag: para -#: post-install.xml:493 +#: post-install.xml:526 #, no-c-format msgid "Instead of the partitioning tool, you should now be presented with a list of the partitions on your system, and asked to select one of them. Normally, you should select the partition containing the root file system that you need to repair. You may select partitions on RAID and LVM devices as well as those created directly on disks." msgstr "" #. Tag: para -#: post-install.xml:501 +#: post-install.xml:534 #, no-c-format msgid "If possible, the installer will now present you with a shell prompt in the file system you selected, which you can use to perform any necessary repairs. <phrase arch=\"x86\"> For example, if you need to reinstall the GRUB boot loader into the master boot record of the first hard disk, you could enter the command <userinput>grub-install '(hd0)'</userinput> to do so. </phrase>" msgstr "" #. Tag: para -#: post-install.xml:513 +#: post-install.xml:546 #, no-c-format msgid "If the installer cannot run a usable shell in the root file system you selected, perhaps because the file system is corrupt, then it will issue a warning and offer to give you a shell in the installer environment instead. You may not have as many tools available in this environment, but they will often be enough to repair your system anyway. The root file system you selected will be mounted on the <filename>/target</filename> directory." msgstr "" #. Tag: para -#: post-install.xml:522 +#: post-install.xml:555 #, no-c-format msgid "In either case, after you exit the shell, the system will reboot." msgstr "" #. Tag: para -#: post-install.xml:526 +#: post-install.xml:559 #, no-c-format msgid "Finally, note that repairing broken systems can be difficult, and this manual does not attempt to go into all the things that might have gone wrong or how to fix them. If you have problems, consult an expert." msgstr "" diff --git a/po/pot/preseed.pot b/po/pot/preseed.pot index b1db4d438..320632299 100644 --- a/po/pot/preseed.pot +++ b/po/pot/preseed.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-07-30 15:28+0000\n" +"POT-Creation-Date: 2006-08-18 17:32+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -681,6 +681,8 @@ msgid "" "d-i partman-auto/disk string /dev/discs/disc0/disc\n" "# Or, if you want to use LVM:\n" "#d-i partman-auto-lvm/disk string /dev/discs/disc0/disc\n" + "# Or, LVM with more than one disk:\n" + "#d-i partman-auto-lvm/disk string /dev/discs/disc0/disc /dev/discs/disc1/disc\n" "\n" "# You can choose from any of the predefined partitioning recipes.\n" "# Note: this must be preseeded with a localized (translated) value.\n" @@ -879,9 +881,11 @@ msgid "" "\n" "# Alternatively, if you want to install to a location other than the mbr,\n" "# uncomment and edit these lines:\n" - "#d-i grub-installer/bootdev string (hd0,0)\n" "#d-i grub-installer/only_debian boolean false\n" - "#d-i grub-installer/with_other_os boolean false" + "#d-i grub-installer/with_other_os boolean false\n" + "#d-i grub-installer/bootdev string (hd0,0)\n" + "# To install grub to multiple disks:\n" + "#d-i grub-installer/bootdev string (hd0,0) (hd1,0) (hd2,0)" msgstr "" #. Tag: title |